I got my new Nexus 7 2013 the other day and tried to root it.
I successfully unlocked it and installed TWRP but when I enter TWRP it seem to not be able to mount any partition
HTML:
E:Unable to mount '/system'
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Unable to mount storage
I can't flash any zip and I can't do anything in the recovery, I'm using the latest TWRP version.
I tried installing android 5.0.2 and 5.1.1 and install TWRP but I keep getting the same error no matter the android version
tomer007 said:
I got my new Nexus 7 2013 the other day and tried to root it.
I successfully unlocked it and installed TWRP but when I enter TWRP it seem to not be able to mount any partition
HTML:
E:Unable to mount '/system'
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Unable to mount storage
I can't flash any zip and I can't do anything in the recovery, I'm using the latest TWRP version.
I tried installing android 5.0.2 and 5.1.1 and install TWRP but I keep getting the same error no matter the android version
Click to expand...
Click to collapse
Been there, there's a whole thread about this. You have to use a modified twrp (multiirom version here: https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img).
You may also be getting a message 'no os installed' when you try to boot. It freaked me out at first.
Here's the thread, multirom twrp info near end: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
Thanks!
Downloading now.
Why is this happening?
Yes!
It worked!
It's a mystery to me why the regular twrp doesn't work. I'm just happy there's a solution.
I can't even get that version of twrp to install using the wugfresh nrt. Every time I try the regular one it reboots into twrp and it shows 0mb available and can't see any files and when I say reboot system it says no OS. It still reboots fine. Tried the multirom version suggested above and it doesn't even get that far.....
Sent from my Nexus 7 using Tapatalk
The multirom twrp installed fine for me via adb (there's an advantage to not having a pc I can install the toolkit on ☺).
If you can still boot into something, you should be able to install the multirom twrp using TWRP Manager or Flashify from the Play Store, I did that after I had everything running (and installed the regular twrp to see if it would work on mm, it didn't, so I had to reinstall multirom twrp).
Related
Hi! I found many threads like this, but none of them fixed my problem so I need your help. Yesterday my Nexus device turned off when I launched Chrome. After this it stuck at Google logo. I tried to enter recovery mode but it can't. Can launch bootloader. The device is rooted and unlocked. Working on KitKat. "Back to stock" option in Nexus Root Toolkit doesn't work. Any ideas what to do?
p.s. When I try to enter recovery mode from bootloader, it just reboot and stuck at Google logo again.
Update: I tried to erase boot partiotion (with cmd) but it stuck
Use the nexus root toolkit and flash stock ROM and and kernel with a factory image. If you want to keep your data, flash cwm recovery temporarily and make a backup. Save the backup to your computer before flashing stock.
Sent from my Nexus 7 using xda app-developers app
datallboy said:
Use the nexus root toolkit and flash stock ROM and and kernel with a factory image. If you want to keep your data, flash cwm recovery temporarily and make a backup. Save the backup to your computer before flashing stock.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Like I said, I tried "Back to stock" but didn't work.
You should still be able to get into boot loader mode, yes? Hold down power and volume down buttons? Use the flash-all.bat in the factory image.
Did you flash anything? Kernels, Roms, mods etc? It won't go into a bootloop for no reason, unless you deleted the boot partition or something. Do a full wipe in recovery, reboot. If nothing, try flashing stock, or a different ROM in custom recovery.
Sent from my Nexus 7 using xda app-developers app
datallboy said:
You should still be able to get into boot loader mode, yes? Hold down power and volume down buttons? Use the flash-all.bat in the factory image.
Did you flash anything? Kernels, Roms, mods etc? It won't go into a bootloop for no reason, unless you deleted the boot partition or something. Do a full wipe in recovery, reboot. If nothing, try flashing stock, or a different ROM in custom recovery.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I can enter the bootloader. When I try to enter recovery from bootloader it restarts and stuck at google logo again. Also combination for recovery menu doesn't work (Power button + Vol up). Also I tried to boot/flash stock and custom recovery using SkipSoft software, but didn't work too. Tried flash-all.bat and cmd flashboot, too.
I still don't know what happen. I was using Chrome and bam* restart and stuck at Google logo.
I just booted a custom recovery with SkipSoft Android Toolkit and tried to wipe all data, but it failed:
Updating partition details ...
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E: Unable to set emmc bootloader message.
E: Unable to mount '/system'
E: Unable to mount '/system'
E: Unable to mount '/system'
E: Unable to mount '/system'
Formatting Cache using make_ext4fs function.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
ClockworkMod Recovery also gives errors:
Error mounting /system
(I/O error)
I think the memory is gone...
I just got a new (refurbished?) S3 from ATT's insurance program (never doing that again...For the price of the insurance and the deductible I could've gotten a very clean used one.) I tried rooting it with CF-auto-root onto 4.3 which worked well for me on the now dead S3 I had that had an OTA upgrade, but it didn't root. Now a reboot to recovery always runs CF-auto-root. I'm sure that the same thing keeping the phone from rooting is keeping CF-auto-root from restoring the bootloader, but I have no idea what that is and how to fix it.
Any ideas? Is this a KNOX issue?
Using I747UCUEMJB with Oct '13 build.
bozob said:
I just got a new (refurbished?) S3 from ATT's insurance program (never doing that again...For the price of the insurance and the deductible I could've gotten a very clean used one.) I tried rooting it with CF-auto-root onto 4.3 which worked well for me on the now dead S3 I had that had an OTA upgrade, but it didn't root. Now a reboot to recovery always runs CF-auto-root. I'm sure that the same thing keeping the phone from rooting is keeping CF-auto-root from restoring the bootloader, but I have no idea what that is and how to fix it.
Any ideas? Is this a KNOX issue?
Using I747UCUEMJB with Oct '13 build.
Click to expand...
Click to collapse
Install GOOMANAGER from Google Play and install the custom recovery from within the app to fix this problem.
petenatas said:
Install GOOMANAGER from Google Play and install the custom recovery from within the app to fix this problem.
Click to expand...
Click to collapse
Thanks for the response.
GOOMANAGER won't work. It requires that the device be rooted first, but CF-auto-root was never able to root the phone. I think the same thing that is keeping it from rewriting the recovery after rooting the device is also keeping it from rooting the device and loading the SuperSU binary.
Is there something new on this S3 that is making this phone non-rootable? Or am I just missing something?
bozob said:
Thanks for the response.
GOOMANAGER won't work. It requires that the device be rooted first, but CF-auto-root was never able to root the phone. I think the same thing that is keeping it from rewriting the recovery after rooting the device is also keeping it from rooting the device and loading the SuperSU binary.
Is there something new on this S3 that is making this phone non-rootable? Or am I just missing something?
Click to expand...
Click to collapse
Did you try to flash the recovery image through the bootloader with adb?
petenatas said:
Did you try to flash the recovery image through the bootloader with adb?
Click to expand...
Click to collapse
I just loaded TWRP 2.7.0.0. I tried to look through the files (I loaded a zip of SuperSU yesterday onto the phone) but when I look at the text screen I see the following.
E: Unable to find partition size for '/boot'
E: Primary block device '/dev/block/mmcblk0p15' for mount point '/data' is not present.
Unable to mount '/data'
Unable to recreate /data/media folder.
Unable to find partition size for '/recovery'
Updating Partition details....
Unable to mount '/system'
Would TWRP's "Fix Permissions" solve this? I'm hesitant to use it without finding out more about "Fix Permissions", but I can't seem to find any detail on it.
...
Unable to mount /data/media during GUI startup
Full SELinux support is present
...
Finished running boot script.
Unable to mount 'cache'
Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
Would TWRP's "Fix Permissions" solve this? I'm hesitant to use it without finding out more about "Fix Permissions", but I can't seem to find any detail on it.
bozob said:
I just loaded TWRP 2.7.0.0. I tried to look through the files (I loaded a zip of SuperSU yesterday onto the phone) but when I look at the text screen I see the following.
E: Unable to find partition size for '/boot'
E: Primary block device '/dev/block/mmcblk0p15' for mount point '/data' is not present.
Unable to mount '/data'
Unable to recreate /data/media folder.
Unable to find partition size for '/recovery'
Updating Partition details....
Unable to mount '/system'
Would TWRP's "Fix Permissions" solve this? I'm hesitant to use it without finding out more about "Fix Permissions", but I can't seem to find any detail on it.
...
Unable to mount /data/media during GUI startup
Full SELinux support is present
...
Finished running boot script.
Unable to mount 'cache'
Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
Would TWRP's "Fix Permissions" solve this? I'm hesitant to use it without finding out more about "Fix Permissions", but I can't seem to find any detail on it.
Click to expand...
Click to collapse
OK...I tried "Fix Permissions" and it didn't change a thing.
Still can't get TWRP to mount anything. Probably this is because of the same problem keeping CF-auto-root from working.
I've installed adb and can shell into the phone when it is in it's normal OS. But there is no SU command available.
But now I'm lost as to how to go about gaining root access and I haven't been able to locate anything similar to my problem online.
I'm now looking for suggestions from someone who might know more about this than I do.
Hi,
i have an LG G4 INT. Unlocked Bootloader. TWRP latest installed.
As rom i use 7HD 7.4.
Everything works fine!
Now i wanted to backup the partitions (before installing xposed), i enter TWRP, click backup, slide, then:
E: unable to mount /system
Number of partitions to bacup: 4
Total size of all data: 10134MB
Backup folder......
.
.
.
E: unable to mount /system
Before reboot inTWRP, i get a message "No os installed..........".
But the device works fine!
Also reinstalling 7HD rom (without wipe!) does not work, same error....
Any idea?
Thanks
No one an idea?
Same issue
Ive had the same issue when i wasnt on the latest recovery. Try to upgrade it easily by: https://dl.twrp.me/h815/twrp-2.8.7.0-h815.img.html using this img file. At your TWRP hit install, and browse for imgages...
Flash, reboot and its done
Hi all,
After spending all my morning looking at various solutions I've resulted in opening a new thread.
I was trying to install a stock rom this morning however was stuck in a bootloop on the LG logo.
Trying to go back into recovery resulted in a black screen after the TWRP logo.
I was attempting to re-install TWRP to see if that would fix the problem however I only managed to get into Download Mode (is this the same screen as the Bootloader?) and adb/fastboot couldn't find the device.
Magically, TWRP boots up now however in the log it states the following:
Code:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount /data
E: Unable to recreate /data/media folder
E: Unable to mount storage
E: Unable to mount /data/media during GUI startup
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
If anyone can point me in the right direction in how to resolve this I would be grateful.
Regards,
Ash
AshleyNG2 said:
Hi all,
After spending all my morning looking at various solutions I've resulted in opening a new thread.
I was trying to install a stock rom this morning however was stuck in a bootloop on the LG logo.
Trying to go back into recovery resulted in a black screen after the TWRP logo.
I was attempting to re-install TWRP to see if that would fix the problem however I only managed to get into Download Mode (is this the same screen as the Bootloader?) and adb/fastboot couldn't find the device.
Magically, TWRP boots up now however in the log it states the following:
Code:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount /data
E: Unable to recreate /data/media folder
E: Unable to mount storage
E: Unable to mount /data/media during GUI startup
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
If anyone can point me in the right direction in how to resolve this I would be grateful.
Regards,
Ash
Click to expand...
Click to collapse
Looks like you trying to install stock Rom, Given the account you used a flashable zip. It didnt install all the way. and now your stuck with a messed up unstable device......
If you can get into TWRP, wipe everything at least 2 times.. Then install a Flashable ROM/gapps ect..
If you cant get into TWRP and only into Download mode.. Then you will have to flash stock kdz file...............
you can find all types of guides on that around here............
Eliminater74 said:
Looks like you trying to install stock Rom, Given the account you used a flashable zip. It didnt install all the way. and now your stuck with a messed up unstable device......
Click to expand...
Click to collapse
Thanks for your response, once I got into TWRP I couldn't wipe anything as it couldn't mount any partition nor could I flash anything from the external sd.
When I plugged it in there was no internal memory so I decided to use the TOT restore method to go back to stock which was successful and now I've got my custom stock rom back on.
Hi Guys,
i flashed my phone with Cyanogenmod a few month ago and everything worked
fine. But when i start the phone now, its stuck on cyanogenmod boot logo.
Safestrap 4.01 ( TWRP v2.7.1.0)
I can get into safestrap but i cant install, restore or flash a new rom.
It seems like i cant write on the internal memory anymore.
Error:
E: unable to mount /datamedia
E:unable to mount /data
E:unable to mount internal storage
E: unable to mount datamedia/media/0/ during gui startup
E: unable to mount datamedia/media/0/TRWP/.twrps when trying to read settings file.
Any Idea what i have to do?
I have the same problem
Firephony said:
i flashed my phone with Cyanogenmod a few month ago and everything worked
fine. But when i start the phone now, its stuck on cyanogenmod boot logo.
Click to expand...
Click to collapse
I am not shure, that the root is the same, but I got stuck the same after updating from my original CM from 2016-2 to any newer version.
In my case a swipe (reset to factory defaults) in safestrap helped.
Good luck