Guys
I need help with my S3
Device can't boot..
Samsung Logo loop...
E:failed to mount /efs (Invalid argument)
# Manual Mode #
-- Appling Multi-CSC...
Applied the CSC-code : Unknow
Succefuly applied multi-CSC.
Where does the error message come from?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
kar3ka said:
Guys
I need help with my S3
Device can't boot..
Samsung Logo loop...
E:failed to mount /efs (Invalid argument)
# Manual Mode #
-- Appling Multi-CSC...
Applied the CSC-code : Unknow
Succefuly applied multi-CSC.
Click to expand...
Click to collapse
Thanks to BaDaB!ng505
Must odin back to original rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drivedevice must be rooted
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device*when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)reboot in recovery wipedata factory reset...done
factorymode: http://forum.xda-developers.com/attachment.php?attachmentid=1772304&d=1362190578
Now you can back up your efs.tar(for 8000 user only)
Reboot and everthing should be back to normal
Dont Think About What To Do Just Hit The THANK Button
---------- Post added at 10:00 AM ---------- Previous post was at 09:59 AM ----------
But I didnt find for the s3 I am going do not download for the n8000
Dont Think About What To Do Just Hit The THANK Button
big thanks !!!
problem solved
kar3ka said:
big thanks !!!
problem solved
Click to expand...
Click to collapse
You are welcome I am here to help you.
I am not asking for Donations to help you find solutions I am just asking for a little click on the Thanks Button
hi,
I can't get pass the last command to mount it. it says can't find /dev/block/mmcblk0p3 in /etc/fstab
any ideas?
very think, unbridled my sgs3.
dear friend, my phone was bricked and the only tutorial that really worked was this here. but adbshell used to enter another command was desperate required. even more thanks.
Lalssa said:
Thanks to BaDaB!ng505
Must odin back to original rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drivedevice must be rooted
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device*when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)reboot in recovery wipedata factory reset...done
factorymode: http://forum.xda-developers.com/attachment.php?attachmentid=1772304&d=1362190578
Now you can back up your efs.tar(for 8000 user only)
Reboot and everthing should be back to normal
Dont Think About What To Do Just Hit The THANK Button
---------- Post added at 10:00 AM ---------- Previous post was at 09:59 AM ----------
But I didnt find for the s3 I am going do not download for the n8000
Dont Think About What To Do Just Hit The THANK Button
Click to expand...
Click to collapse
i need a help , i got this on the last step: can't find /dev/block/mmcblk0p3 in /etc/fstab
Lalssa said:
Thanks to BaDaB!ng505
Must odin back to original rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drivedevice must be rooted
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
Click to expand...
Click to collapse
big thanks !!!
Related
I thought I'd bricked my NT but it would appear that it is actually alive because it turns up with adb and I can get shell and then issue command su, but what I can't do is replace the old build.prop because file system is not writable. How do I remount it to be writeable from a shell please?
Thanks!
CelticWebSolutions said:
I thought I'd bricked my NT but it would appear that it is actually alive because it turns up with adb and I can get shell and then issue command su, but what I can't do is replace the old build.prop because file system is not writable. How do I remount it to be writeable from a shell please?
Thanks!
Click to expand...
Click to collapse
mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /system
Type mount to verify rw, make your changes
mount -o ro,remount -t ext4 /dev/block/mmcblk0p8 /system
Type mount to verify ro
Thank you!
hwong96 said:
mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /system
Type mount to verify rw, make your changes .....
Click to expand...
Click to collapse
I don't have this tablet but a phone with similar problem.
this does not work for me, although I have ROOTED phone MTK6572, android 4.2.2 ;
"/ root" gets RW, but "/system" stays RO.
I get this message:
error
"the item "system" is read only"
I have tried many apps in phone (remount system RW, FX file expl. ....), and mtkdroid-tools and ADB shell in PC.
I have tried many similar version of that command, too, inc. busybox remount. non of those work.
any ideas, what to try next?
what file or thing or item and where I need to change to get this remounting system to RW done?
it is ext4, and remountable.
I have SuperSU in phone but can't update its binaries: /system stays RO, what ever I try...
I can't change audios, anything in /system.
very annoying...
Jack_Rover said:
I don't have this tablet but a phone with similar problem.
this does not work for me, although I have ROOTED phone MTK6572, android 4.2.2 ;
"/ root" gets RW, but "/system" stays RO.
I get this message:
error
"the item "system" is read only"
I have tried many apps in phone (remount system RW, FX file expl. ....), and mtkdroid-tools and ADB shell in PC.
I have tried many similar version of that command, too, inc. busybox remount. non of those work.
any ideas, what to try next?
what file or thing or item and where I need to change to get this remounting system to RW done?
it is ext4, and remountable.
I have SuperSU in phone but can't update its binaries: /system stays RO, what ever I try...
I can't change audios, anything in /system.
very annoying...
Click to expand...
Click to collapse
I understand your frustration, however, you should try to post your question to the MTK6572 or Samsung S4 thread. Anyway, since you have asked I'll answer. The mount point for /system is different on each phone model. There is no one standard /system mount point. On the Nook Tablet and Nook Color it is mmcblk0p8. On your device it is different, so the command you tried will not work.
You need to find out what the /system mount point is for your phone.
Open terminal from phone and type su.
Press enter.
At the # prompt type cat /proc/mtd
Press enter.
Look at the output on the screen and see what the mount point is for /system.
A the the # prompt type mount -o rw,remount -t ext4 /dev/block/enteryoursystemmountpointhere /system
Note: replace enteryourmountpointhere with your mount point from the previous step.
Change /system to ro when done. Hope this works for you.
Also download root checker app to ensure you rooted properly.
hwong96 said:
I understand your frustration, however, you should try to post your question to the MTK6572 or Samsung S4 thread. ......
Click to expand...
Click to collapse
thanks for your responce.
with that "cat ..." I got : "no such file or dir"...
I know already that my mnt point is (did try already these earlier):
mount -o rw,remount /dev/block/mmcblk0p4 system
mount -o remount,rw -t ext4 /[email protected] /system
but no success, " system read only" stays, and no change.
Jack_Rover said:
thanks for your responce.
with that "cat ..." I got : "no such file or dir"...
I know already that my mnt point is (did try already these earlier):
mount -o rw,remount /dev/block/mmcblk0p4 system
mount -o remount,rw -t ext4 /[email protected] /system
but no success, " system read only" stays, and no change.
Click to expand...
Click to collapse
Did you use the root checker app to verify for proper root?
hwong96 said:
Did you use the root checker app to verify for proper root?
Click to expand...
Click to collapse
yes.
I have many apps (e.g. FX, ATools, TitaniumBup, busybox, ES, mount /system rw, SD maid, root expl., adbd insec., rootAppDel, a.s.o.) that use root rights, and phone's superSU gives the rights to them.
AT:s terminal has # prompt, so it must be root. (?)
adbd insecure's current status = binary: insecure; usb debugging: enabled.
I have earlier version SU's binaries working ok, but updating SU made this binary-update-issue: " binary update failure" and so SU-app won't open (it closes after failing binary update), though otherwise it works ok (and worked earlier until I did let G-play to update it, silly me!).
somehow my /system has been "open" i.e. RW earlier, since busybox and superSU has been installed, but now it is "stuck" to that RO-status. "/" opens, but "/system" not.
MTK Droid Root & Tools v2.5.3 (from here xdadevs) gets root shell ok, but fails when trying to install SU, busybox a.s.o. ("read-only system") - and it "crashes".
maybe kernel related? or boot loader, or .... what?
-----
btw, my apologises, that I wrote this issue to this thread, but I found my "problem" here with the search, and after posting I realized that this is "tablet area..."
so this part can be moved to better place by those who know best where to - though not to trash, anyway....
Jack_Rover said:
yes.
I have many apps (e.g. FX, ATools, TitaniumBup, busybox, ES, mount /system rw, SD maid, root expl., adbd insec., rootAppDel, a.s.o.) that use root rights, and phone's superSU gives the rights to them.
AT:s terminal has # prompt, so it must be root. (?)
adbd insecure's current status = binary: insecure; usb debugging: enabled.
I have earlier version SU's binaries working ok, but updating SU made this binary-update-issue: " binary update failure" and so SU-app won't open (it closes after failing binary update), though otherwise it works ok (and worked earlier until I did let G-play to update it, silly me!).
somehow my /system has been "open" i.e. RW earlier, since busybox and superSU has been installed, but now it is "stuck" to that RO-status. "/" opens, but "/system" not.
MTK Droid Root & Tools v2.5.3 (from here xdadevs) gets root shell ok, but fails when trying to install SU, busybox a.s.o. ("read-only system") - and it "crashes".
maybe kernel related? or boot loader, or .... what?
-----
btw, my apologises, that I wrote this issue to this thread, but I found my "problem" here with the search, and after posting I realized that this is "tablet area..."
so this part can be moved to better place by those who know best where to - though not to trash, anyway....
Click to expand...
Click to collapse
Don't know what else to suggest, except maybe contact Chainfire on G+.
.
I've backup efs for samsung gs3 i9305 by efs pro v1.2.6 and i tried restor efs , but after restar mobile it not work,stands on the logo samsung
when entering a Recovery This image shows
http://imageshack.us/f/809/photookc.jpg/
Is there a way to push efs file to mobile I've copied efs the way Root Explorer program and tried, but to no avail for the entry way to efs to the device
I tried with the pc suit for Andorad when entering recovry mode I see all files system for mobil, but when you try to push efs appears that not enough space
http://imageshack.us/f/688/95833739.png/
http://imageshack.us/f/547/42574038.png/
Any help or thought about push file efs to phone. to restore life for mobil and I do not know if there was frimware of three files Will addresses the issue.
thanks
sorry for bad english
Wrong section, post in the 9305 QA
Glebun said:
Wrong section, post in the 9305 QA
Click to expand...
Click to collapse
Hit Thanks if I deserve it >
U dont
---------- Post added at 09:20 PM ---------- Previous post was at 09:03 PM ----------
nabel_sweed said:
I've backup efs for samsung gs3 i9305 by efs pro v1.2.6 and i tried restor efs , but after restar mobile it not work,stands on the logo samsung
when entering a Recovery This image shows
Is there a way to push efs file to mobile I've copied efs the way Root Explorer program and tried, but to no avail for the entry way to efs to the device
I tried with the pc suit for Andorad when entering recovry mode I see all files system for mobil, but when you try to push efs appears that not enough space
Uploaded with ImageShack.us
Any help or thought about push file efs to phone. to restore life for mobil and I do not know if there was frimware of three files Will addresses the issue.
thanks
sorry for bad english
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------------------
Sorry but u in serious problems i had exact same problem and struggled in several days to sort it out
U efs dir is corrupted for sure - u should have made a fresh backup before starting any flashing
This is with no doubt the most complicated dir on our phone, and if u dont have a 100% working backup before starting messing around theres absolutely NO way to restore it - I was lucky i now a guy with a SPT box he hardcoded my modem bin file and imei, and then copy imei folder 1 file after another, then set permissions right with efspro - and then network/imei came back - but this way i cant ever change modem file again has to use the patched one (and it must be flashed through spt box not odin/heimdal it wont work then)
This means i ever cant flash a rom with aroma installer, because it forces u to choose another modem file
Sorry but without a spt patched modem u wont ever be able to use network again
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
TO ALL OF YOU OUT THERE !!!! MAKE A BACKUP OF EFS FOLDER WITH KTOOL AND KEEP IT A SAFE PLACE - JUST IN CASE
Glebun said:
Wrong section, post in the 9305 QA
Click to expand...
Click to collapse
Sorry to put the question on the location inappropriate please amendment of supervision.
spoonymoon said:
Hit Thanks if I deserve it >
U dont
---------- Post added at 09:20 PM ---------- Previous post was at 09:03 PM ----------
---------------------------------------------------------------------------------------------------------------------------
Sorry but u in serious problems i had exact same problem and struggled in several days to sort it out
U efs dir is corrupted for sure - u should have made a fresh backup before starting any flashing
This is with no doubt the most complicated dir on our phone, and if u dont have a 100% working backup before starting messing around theres absolutely NO way to restore it - I was lucky i now a guy with a SPT box he hardcoded my modem bin file and imei, and then copy imei folder 1 file after another, then set permissions right with efspro - and then network/imei came back - but this way i cant ever change modem file again has to use the patched one (and it must be flashed through spt box not odin/heimdal it wont work then)
This means i ever cant flash a rom with aroma installer, because it forces u to choose another modem file
Sorry but without a spt patched modem u wont ever be able to use network again
Thanks for the reply and assistance
So the solution you think with box spt.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
TO ALL OF YOU OUT THERE !!!! MAKE A BACKUP OF EFS FOLDER WITH KTOOL AND KEEP IT A SAFE PLACE - JUST IN CASE
Click to expand...
Click to collapse
Have a look here >http://forum.xda-developers.com/showthread.php?t=1896470
Best thing u can do is follow this guide, and send for repair saying it happend during kies update they wont/cant charge u then :silly:
http://forum.xda-developers.com/showthread.php?t=1846451
And yes spt box did the trick, but they are hard to get around, and sertenly not easy to use
One more thing if youre to play around with a spt DONT use windows 8 it has a lot of new low level security crap build in that makes spt box fail !! use 7
spoonymoon said:
Have a look here >http://forum.xda-developers.com/showthread.php?t=1896470
Best thing u can do is follow this guide, and send for repair saying it happend during kies update they wont/cant charge u then :silly:
http://forum.xda-developers.com/showthread.php?t=1846451
And yes spt box did the trick, but they are hard to get around, and sertenly not easy to use
One more thing if youre to play around with a spt DONT use windows 8 it has a lot of new low level security crap build in that makes spt box fail !! use 7
Click to expand...
Click to collapse
Thank you very much I follow the instructions
i used the following commands to do so manually in terminal
Code:
mke2fs / dev/block/mmcblk0p3
mount-w-t ext4 / dev/block/mmcblk0p3 / efs
Then restart the Mobile and it work normal and i copy efs with program Root exploer and returned everything in its natural form
hi help please my phone GS3 i9300 international ver
when im trying to re mount efs with code in cmd manually my phone path not shown in device on my computer and when start it stuck on Samsung logo but i can enter recovery mode and download mode when i enter recovery mode error msg (E:\failed to mount efs (invalid argument)) i flash this roms I9300XXELL5_I9300OJVELL2_KSA nothing change.
advice plz
bricked s3
i bricked my s3 (hard brick, not soft as you are reporting), i sent mine off to mobiletechvideos.com and got it back within a week. HIGHLY recommended. don't know if you can fix your soft brick or not, but you may need JTAG repair like i did. i didn't have the hardware to perform the JTAG myself, but i had the software. needless to say, it was cheaper to send it off to be fixed than to report it to my insurance or to buy the hardware. hope this helps!
nabel_sweed said:
Thank you very much I follow the instructions
i used the following commands to do so manually in terminal
Code:
mke2fs / dev/block/mmcblk0p3
mount-w-t ext4 / dev/block/mmcblk0p3 / efs
Then restart the Mobile and it work normal and i copy efs with program Root exploer and returned everything in its natural form
Click to expand...
Click to collapse
Hello, I've got the same problem here.
I managed to ODIN flash a stock I9300XXDLJ4_I9300PHEDLI1_PHE ROM with CWM root.
It keeps giving me this 'E: failed to mount /efs (Invalid argument)' error.
then I got in with ADB SHELL and executed:
mke2fs / dev/block/mmcblk0p3
sh: mke2fs: not found
I investigated a bit and found out that it's a busybox command, so as I only can ADB do things, (doesn't boot), i pushed the busybox_android binary to my S3 and now when I execute the mke2fs command through:
./busybox_android mke2fs /dev/block/mmcblk0p3
I get
./busybox_android mke2fs /dev/block/mmcblk0p3
Segmentation fault
Any ideas?
Thank you in advance.
Flash a stock rom via Odin .
jje
JJEgan said:
Flash a stock rom via Odin .
jje
Click to expand...
Click to collapse
I already did that but phone won't boot up. Is there any special recommendation/procedure to fix this?
I flashed a stock I9300XXDLJ4_I9300PHEDLI1_PHE ROM with CWM root.
In the Galaxy Note N7000 we had 'full wipe stock ROMs', I wonder if there is anything similar in the S3...
Thank you in advance.
We finally fixed it. I'll post the solution in case it can help anyone else...
The S3 got stuck in the Samsung logo screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When entering the recovery it gave us this error "E: failed to mount /efs (Invalid argument)"
As we already know, the /efs folder contains all the personalized information of the mobile (IMEI number, carrier lock, etc). So if we like to play with ROMs, we should be aware of this detail and make several backups of this VERY IMPORTANT folder, and preferably store them out of the mobile, in the computer for example.
in case we mess up the /efs folder, we are likely to have no other solution than bringing it to the authorized Samsung dealer for repair. No one is going to lend us the EFS backup from their mobile, as doing that we would likely clone their IMEI -which is, BTW, unlegal.
So we first flashed with PC-ODIN a STOCK ROM (I9300XXDLJ4_I9300PHEDLI1_PHE). We tried different ones (one file, 4 files) and none of them solved our problem as the problem was with the /efs partition and I don't think any ROM will touch that...
After flashing the ROM we also flashed Chainfire's CF-Root (CF-Auto-Root-m0-m0xx-gti9300)
We boot up the mobile in recovery mode (Volume UP + Power + Home), we connected to the PC through ADB SHELL.
Our first surprise, trying to partition:
#mke2fs / dev/block/mmcblk0p3
sh: mke2fs: not found
It seems that mke2fs is a command provided by busybox, and it's not present in the stock ROM.I downloaded a precompiled busybox version from busybox.net and pushed it in the S3
Code:
PC> adb shell mkdir /data/busybox
PC> adb push busybox /data/busybox
PC> adb shell
$su
#cd /data/busybox
#chmod 775 busybox
#./busybox --install
once installed we could use mke2fs command properly:
Code:
# busybox mke2fs /dev/block/mmcblk0p3
busybox mke2fs /dev/block/mmcblk0p3
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
5136 inodes, 20480 blocks
1024 blocks (5%) reserved for the super user
First data block=1
Maximum filesystem blocks=262144
3 block groups
8192 blocks per group, 8192 fragments per group
1712 inodes per group
Superblock backups stored on blocks:
8193
and after that mounting the partition in the /efs folder
Code:
#busybox mount -w -t ext4 /dev/block/mmcblk0p3 /efs
busybox mount -w -t ext4 /dev/block/mmcblk0p3 /efs
With the EFS folder fixed, we ADB PUSHED the backup of ur efs folder (efs.tar), we unpackaged it (busybox tar xfv efs.tar) and moved it's content to the newly fixed /efs folder.
Reboot and ready to go:
ptolomeo said:
Code:
#busybox mount -w -t ext4 /dev/block/mmcblk0p3 /efs
busybox mount -w -t ext4 /dev/block/mmcblk0p3 /efs
Click to expand...
Click to collapse
I did everything as told but after that command I get this:
mount: mounting /dev/block/mmcblk0p3 on /efs failed: file too large
Rockwell_ said:
I did everything as told but after that command I get this:
mount: mounting /dev/block/mmcblk0p3 on /efs failed: file too large
Click to expand...
Click to collapse
You're on luck.
In the Spanish forum where I also posted the solution (www.htcmania.com/showthread.php?t=541264), another guy came with the same problem. In his case, he was using latest busybux v.20 which he downloaded from busybox.net instead of using the one I provided (v.19).
http://www.nobutaka.es/web/files/S3.zip
We substituted v.20 with v.19 and it worked instantly.
Hope it works for you.
Offtopic, but how did you manage to mess up EFS at first.
I am asking, so taht I can avoid it in future.
eggman89 said:
Offtopic, but how did you manage to mess up EFS at first.
I am asking, so taht I can avoid it in future.
Click to expand...
Click to collapse
I didn't mess the EFS. I don't even have a S3 (I have a Note N7000) .
My friend claims that he also didn't do anything at all. The S3 just drained the battery and then it didnt boot any more.
Hope it helps.
My conclusion: if you own an S3 do a backup of the EFS folder.
ptolomeo said:
You're on luck.
In the Spanish forum where I also posted the solution (www.htcmania.com/showthread.php?t=541264), another guy came with the same problem. In his case, he was using latest busybux v.20 which he downloaded from busybox.net instead of using the one I provided (v.19).
http://www.nobutaka.es/web/files/S3.zip
We substituted v.20 with v.19 and it worked instantly.
Hope it works for you.
Click to expand...
Click to collapse
Ok, I see. Thanks.
Now I get error after ./busybox --install
busybox: /bin/[: No such file or directory
edit: Got it working after removing the new busybox and mkdir /bin
Now the only problem is restoring efsbackup.tar. I have two different backups. Others size is over 6MB and other is 5.3MB. Should I do something with the .img files? I tried to push the smaller one in to phone and unpacked it in /efs folder. Still no IMEI.
Bricked S3
Hi guys. I am a new member of xda developers. i brought a galaxy s3 2 months back, and it was fine until yesterday. suddenly found it stuck on the samsung logo screen. I took it to a dealer, and got the answer that the imei is null, and can't do anything but to change the board for 300 USD.
Also i am getting the following error: failed to mount /efs (invalid argument) when pressing menu, volume up and power buttons.
Please help me, .:crying::crying::crying::crying:
LebAndroider said:
Hi guys. I am a new member of xda developers. i brought a galaxy s3 2 months back, and it was fine until yesterday. suddenly found it stuck on the samsung logo screen. I took it to a dealer, and got the answer that the imei is null, and can't do anything but to change the board for 300 USD.
Also i am getting the following error: failed to mount /efs (invalid argument) when pressing menu, volume up and power buttons.
Please help me, .:crying::crying::crying::crying:
Click to expand...
Click to collapse
So, did you read any of the previous messages? I'm guessing not...
Please take the time and trouble to read the messages on a thread before posting.
Now stop :crying: :crying: :crying: and start READING!
Permission denied
PC> adb shell mkdir /data/busybox
PC> adb push busybox /data/busybox
PC> adb shell
$su
#cd /data/busybox
#chmod 775 busybox
#./busybox --install[/CODE]
Please help me...Iam stuck on the first line. When i try "adb shell mkdir /data/busybox"...it states cannot create directory data /busybox: Permission denied. What am i supposed to do? I flashed with the stock ROM and chainfire auto root from the above links. Earlier i had another stock ROM installed and with that i tried everything and got stuck in the last step while trying to mount efs. It stated" file too large to mount". I downloaded the busybox version from the links stated in this thread. Iam desperate. Pls help!!!! What should i do now??
A friend just gave me a Lenovo A560 which won't boot at all. I can enter recovery mode, tried reseting with no use but it seems to have problems with mounting block devices.
Code:
E:failed to mount block devices /dev/block/mmcblk1p1
E:remount block devices /dev/block/mmcblk1
E:failed to mount /sdcard (No such file or directory)
E:failed to mount block devices /dev/block/mmcblk1
E:remount block devices /dev/block/mmcblk1
E:failed to mount /sdcard (No such file or directory)
E:volume for path [/cache]
Any help would be apreciated, I am willing to try any experiments to sort it out.
solution
andymatr1x said:
A friend just gave me a Lenovo A560 which won't boot at all. I can enter recovery mode, tried reseting with no use but it seems to have problems with mounting block devices.
Code:
E:failed to mount block devices /dev/block/mmcblk1p1
E:remount block devices /dev/block/mmcblk1
E:failed to mount /sdcard (No such file or directory)
E:failed to mount block devices /dev/block/mmcblk1
E:remount block devices /dev/block/mmcblk1
E:failed to mount /sdcard (No such file or directory)
E:volume for path [/cache]
Any help would be apreciated, I am willing to try any experiments to sort it out.
Click to expand...
Click to collapse
Hi. I just managed to fixed problem wont boot yesterday on my A560. Unfortunately when I running recovery mode and trying to flash other ROM, it shows exactly what you write above. However below is what I did to make my phone pass Lenovo logo:
1. Download official rom in needrom website.
2. Extract the file.
3. Put the extracted file(system.img,recovery.img,cache.img,boot.img,userdata.img) inside folder you installed ADB. For me is C:\android
4. Remove battery from your phone for 5 seconds, put is inside back, hold both volume buttons along with plugging USB cable. Your phone will only show Lenovo logo(fastboot mode)
5. Run cmd.exe, type cd C:\android and press enter.
6. Copy below code:
fastboot erase system
fastboot erase recovery
fastboot erase cache
fastboot erase boot
fastboot erase userdata
paste it then press enter.
6.After it finished, copy:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor userdata.img
and press enter.
7. Copy:
fastboot reboot
and press enter.
8. This should reboot your phone back and enter the new flash official ROM.
Forgive for my bad English and please let me know if these works for you
Thank you very much for dedicating your time to help me. I really apreciate your help. I succeded earlier in installing the custom rom from the website you provided above and it works well. Cheers
my modem partition shows as protected in flashfire.im guessing its read only? how would i mount it as r/w in adb.I have root and busybox. the mmc block is /dev/block/mmcblk0p1
adb shell
su
# # mount -o remount,rw /dev/block/mmcblk0p1?
i've tried that command, i dont know if its correct it give no errors but its still read only
Sorry
But have you found a way to mount modem partition
What is the command for it?
I accidentally erased all by flash tool
And now SIM not working
Even after flashing stock rom
I have Lenovo phab plus
And I could only install twrp recovery and root
But the recovery can't mount
It returns to default again after restart
jass65 said:
my modem partition shows as protected in flashfire.im guessing its read only? how would i mount it as r/w in adb.I have root and busybox. the mmc block is /dev/block/mmcblk0p1
adb shell
su
# # mount -o remount,rw /dev/block/mmcblk0p1?
i've tried that command, i dont know if its correct it give no errors but its still read only
Click to expand...
Click to collapse
You need insecure ADB to do that, which requires ROM modification. Or do it in TWRP, which is insecure by default.
Insecure ADB is enabled by "adb root" on your PC.
Also, when remounting, you should specify the mount point - not the block device. E.g. /modem. You can check "mount" command to find the existing mount point.
Boot into TWRP and run:
adb shell mount -o rw,remount /modem or /firmware
But you may get errors as this partition is probably write-protected. You'd need to modify your fstab to make it always read-writeable
The best way to modify is to dump the partition and modify within Linux then reflash to the device
=== Moto G Power (2020) XT2041-4-SS FIRMWARE: Android 10 "SOFIA_RETAIL_QPMS30.80-109-5" ===
1)
systemrw_1.32 (./makesysrw.sh size=50) => error code 73 (either way auto or manual)
2)
sysrw_repair_v1.32 (USB stick Ubuntu Mate 21.4) => Successfully created patched super image at /media/ubuntu-mate/Drive-C/sysrw_repair/img/super_fixed.bin
3)
"fastboot flash super super_fixed.bin" (in FASTBOOTD) => was sent 8 sparses SUPER out of 8, no errors
4)
restarted phone => OK
5)
adb shell
su
mount -o remount,rw /
mount -o remount,rw /system
mount -o remount,rw /product
mount -o remount,rw /vendor
6)
weird things started appear...
build.prop 0 Kb and copying saved earlier file build.prop to /system does not help it stays empty... I could change permissions in properties but it didn't help build.prop empty and nothing I could do... I repeated system rw remount but now I started getting bad returns like "mount: '/system' not in /proc/mounts" as I never flashed rw super image...
7)
flashed super image again in FASTBOOTD => same results: build.prop empty and nothing you can do with it
8)
flashed super image again now just in BOOTLOADER but weirdly in bootloader there were only 6 sparses SUPER out of 6 (in FASTBOOTD there were 8 sparses out of 8) => same results: build.prop empty and nothing you can do with it
9)
flashed and restored my FIRMWARE: SOFIA_RETAIL_QPMS30.80-109-5 (without erasing: boot, recovery, metadata and user data partitions) phone is fine but ROOT the same RO
-----------------------------------------
P.S. I was afraid to flash SUPER to slots A and B like:
fastboot flash super_a super_fixed.bin
fastboot flash super_b super_fixed.bin
and I didn't do it even though I remember some guy mentioned that it helped with two slots...
I didn't take a chance... I just got my phone back after being dead bricked from Motorola service... in the bricked phone i had perfect touch screen in TWRP (3.5.0_10) damn! in the phone of the same model they send me back TWRP touch screen does not work... (looks like the different drivers are set for the touch screen)
I've run into the same issue with the Self-Erasing Build.prop. Did you ever find a work-around? Maybe patching the build.prop on pc in SUPER and reflashing the Patched.Super.img would work?