Factory Reset Taking Too Long in TWRP - Nexus 7 Q&A, Help & Troubleshooting

Hello,
I have been trying to flash android 5.1.1 factory image onto my Nexus 7 (nakasi-grouper). It is unlocked and I have the factory image zip file pushed onto the /sdcard/ folder using adb. But when it tried to install it, it gives me an error message saying:
Error: Unable to mount /data /cache /system ( i am unable to mount System/Cache/Data from TWRP either)
I have tried multiple methods going through different threads form your website (which is awesome btw! ), but everything fails.
Flashing through fastboot and Nexus Tool kit (Wugs) from PC , gets interrupted at Failed to write boot-loader -- writing system...... and the device switches off automatically. And when i turn it on again, the process fails.
Finally I have tried to factory reset it, it took a whole night but it is still stuck at: Formatting Cache using make_ext4fs function. I am considerably new to android and I have no clue how to proceed from here. Any help is much appreciated!

Related

[Q] Cant get Rom Installed - img file not on device

I have an unlocked rooted nexus 10. I downloaded the rom file and google tools to the device. I restarted into recovery mode and cleared system, and all caches. Well since I'm stupid the rom img is not on the device and I'm stuck with no OS to boot into. I tried to reflash the stock Rom through my macbook from this link "nexus10root.com/nexus-10-unroot/how-to-unrootunbrick-nexus-10-factory-firmware/" and I get this error - error ERROR: usb_write failed with status e00002be FAILED (data transfer failure (No such file or directory))" when it tries to install the system. Is there anything else I can do? My guess is that it is not in USB debug mode since I tried a factory reset. Thanks in advance

[HELP!] Failed CM flash & now wont mount /system

EDIT: SOLVED. Sorry, please ignore
I am using TWRP, I factory reset fine.
I then lined up 3 zip files to flash. CM10.1, Gapps and Cerberus
The screen turned off while flashing and I panicked. It wouldnt turn on again. I'm thinking it was because of the screen off delay.
I panicked and pushed all of the buttons several times but couldn't get the screen to turn on again.
Now I've turned off the screen off delay and now I'm trying to re install CM but it keeps getting the following
E: Unable to mount ' /system '
I can still access TWRP recovery and Download.
Is there any way to restore the partitions?
--------------------------------------------------------
Edit from here on:
I was able to recover the partitions by downloading this following PIT file:
http://d-h.st/v7C
I used it with ODIN, I put my phone in download mode and put pushed the PIT file onto my phone, which fixed the partitions. From there I was able to just install CM10.1 like normal

Reboot problem - Failed to mount cache (Boot loop)

Hi guys,
I'm seeking your help in assisting me getting my tablet works again. It's Nexus 7 2012 with last updated Android version 5.1.1 (LMY47V). The problem started when the tablet suddenly restarted and the loading intro (that appears after Google's logo) didn't change for long time. I entered the recovery mode and tried to wipe cache partition unfortunately which made my problem worse! upon reboot I only get the Google logo repeatedly with no change!
The recovery logs are as follow:
E: failed to mount /cache (invalid argument)
E: Can't mount / cache/recovery/log
E: Can't open / cache/recovery/log
I've searched on the forum and found an opinion that I should download the Android Image from the developers.google website and unzip till I find a cache.img file, but it wasn't there after I've extracted the image zip file.
I've important data that I need to retrieve from the tablet. What should I do? Taking into consideration that I didn't unroot the tablet but I did make the undebugging step before (working with pdaNet).
Thank you very much in advance!
Support
Can anyone help??

How to root a S8 G950F Exynos with failed integrity verification without wipe ?

Dear all,
I tried since yesterday to root my S8 Exynos (G950F). My phone is crypted and when I try to root with magisk via TWRP, I have errors to access to datas. When the system boot, I have the error unable to restart your phone. the integrity verification has failed....
Then via TWRP and the shell, I made a copy of the userdata partition on my computer (the crypted partition), then I wiped my phone, I flashed the DM Verify Disabler and then Magisk via TWRP, until then, no problem, I was root but with an empty phone.
There, I uploaded my copy of userdata partition into my S8, I boot the system and always the same error of integrity verification failed...
Now, my phone works always good (I flash the stock ROM via ODIN) but I haven't yet the root.
Is there a way to root the S8 without lost the datas ? A kind of APK or something else ?
Kind regards,
Lau
lolo1410 said:
Dear all,
I tried since yesterday to root my S8 Exynos (G950F). My phone is crypted and when I try to root with magisk via TWRP, I have errors to access to datas. When the system boot, I have the error unable to restart your phone. the integrity verification has failed....
Then via TWRP and the shell, I made a copy of the userdata partition on my computer (the crypted partition), then I wiped my phone, I flashed the DM Verify Disabler and then Magisk via TWRP, until then, no problem, I was root but with an empty phone.
There, I uploaded my copy of userdata partition into my S8, I boot the system and always the same error of integrity verification failed...
Now, my phone works always good (I flash the stock ROM via ODIN) but I haven't yet the root.
Is there a way to root the S8 without lost the datas ? A kind of APK or something else ?
Kind regards,
Lau
Click to expand...
Click to collapse
You need to reflash twrp in odin and boot into recovery (TWRP) before the phone boots the system. Id uncheck auto reset in odin and when its done flashing twrp again boot right into it. From there you want to select to keep the system read only, and then flash the DM Verity Disabler. After thats done flashing, your phone should boot up normally without seeing the integrity failed message. Its important that you boot right into twrp (recovery) after odin flashes it, if not you need to reflash twrp in odin until you successfully get into recovery before it boots your system.
I just tried 2 times this procedure, when I flash the no-verity-opt-encrypt-5.1, I have several error messages like Failed to mount '/data' (Invalid argument) or Unable to recreate /data/media folder or Unable to mount storage and Unable to mount /data/media/TWRP/.twrps.
When I boot up the phone, I have the same error of integrity failed message and I have to flash a stock system and boot img
lolo1410 said:
I just tried 2 times this procedure, when I flash the no-verity-opt-encrypt-5.1, I have several error messages like Failed to mount '/data' (Invalid argument) or Unable to recreate /data/media folder or Unable to mount storage and Unable to mount /data/media/TWRP/.twrps.
When I boot up the phone, I have the same error of integrity failed message and I have to flash a stock system and boot img
Click to expand...
Click to collapse
You have to wipe data otherwise it won't boot, there's no way round this unfortunately
lolo1410 said:
I just tried 2 times this procedure, when I flash the no-verity-opt-encrypt-5.1, I have several error messages like Failed to mount '/data' (Invalid argument) or Unable to recreate /data/media folder or Unable to mount storage and Unable to mount /data/media/TWRP/.twrps.
When I boot up the phone, I have the same error of integrity failed message and I have to flash a stock system and boot img
Click to expand...
Click to collapse
Previous poster is correct. Wipe>Format data>yes> in twrp then you should be good to go.

[BUG][SOLVED][WORKAROUND] TWRP starts with no menu, runs script, crashes, repeat (Axon 7 mini)

Hello,
im new to this Forum. I try my best to give all the information i have.
What happened?
I tried to install the project /e/ os on my axon 7 mini. First I unlocked my phone with tuliptool in edl mode. I found the twrp recovery-image for my device in this guide (https://www.getdroidtips.com/root-twrp-zte-axon-7-mini-magisk/#Download-Files) flashed it with tuliptool to the recovery partition and it worked. But it broke my stock android rom. I only can boot intro twrp - i cant boot android (only shows zte android title screen). Then i installed the unofficial /e/ port for my device with twrp and it worked. Then i thought i could unroot my phone with tuliptool (i dont know why atm i thougt it will be a good idea) so i ran tupliptool lock unlock and my device was locked again. Now i only can access twrp so i undo the locking. After wiping the data partition with twrp, /e/ startet again. Then i thought that wiping the data partition would solve the issiue with not loading /e/ while locked, therefore i gave it an other try. Locking my phone again, wiping partition with twrp and... nothing. So i gave up and wanted to use my phone again so i unlocked it again.
Whats the problem?
Now I only can access twrp, but it wont show the menu. It just autostarts a script and there are no buttons. The script failes after ~10 seconds and the device crashes (error message below). It trys to boot up but fails, so it loads into recovery -> starts twrp -> runs this script -> crashes and so on. Now i cant do anything. It reboots all the time.
What can I do?
As said, twrp starts but with no menu. I have access to edl mode so i rewrote the recovery partition. This does not change anything. I can access my device with adb while it loads twrp. I have a time window about 10-15 seconds until it reboots. Fastboot does not work. (Not available or locked on Axon 7 mini?) If i try "adb reboot bootloader" my phone just reboots into android (well it did before flashing, now its stuck in the loop.) From searching this forum i think i should reformat the partitions, but i dont know how because i dont have access to the twrp menu. If you need more informations like a dump or something, tell me how to do it.
The Error:
As i dont know how i could dump it from my phone to my PC, i had to manual type the Error here...
$Begin
Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details...
...done
Unable to mount storage
Successfully decrypted with default password.
Updating partition details...
...done
Unable to mount storage
Unable to mount '/data' (Invalid argument)
Full SELinux support is present.
wipe_data_via_recovery
Unable to mount /data/media/TWRP/.twrps
Running Recovery Commands
Failed to mount '/data' (Invalid argument)
Formatting Cache using make_ext4fs...
Done processing script file
Failed to mount '/data' (Invalid argument)
Failed to mount '/data' (Invalid argument)
$end
This runs fast until "Done processing script file". There it waits for ~3 Seconds. Then the last two lines show up and it crashes immediately.
Ok i found a solution - it worked for me but i dont know why. Its not intuitive but hey, its a workaround.
The problem was twrp couldnt startup anymore because the data partition was currupted (not confirmed, but i guess it was currupted). If you follow any guide, they tell you to go to wipe data inside of twrp and wipe (and reformat) the partition. This wont work in this case, because the corrupted partition causes twrp to crash. Its the script in the post above.
To fix this i used adb while twrp was starting up
Code:
adb shell recovery --wipe_data
This alone wouldnt solve the issue, but it will buy some time. After twrp loads again, you will see the main menu of twrp for a couple of seconds. The time you have on the menu is very limited (5 seconds max) before the script that will crash twrp starts executing. In this time window i managed to set twrp to write mode and initiated the wipe of /data. If you get this far, both scrips (wipe data and open recovery script) will execute, the screen will switch between both of them very fast. After a few seconds it will crash again, but the wipe data script could reformat the data partition properly. After this twrp will work like normal.
I don't know if this problem is specific to my device or model. I dont know if this is recreatable. Im glad i fixed it after five long days, im not willing to sacrifice my device again. I dont know if this is a twrp bug or what happened exactly. If anyone had a clue or needs more informations i will provide them. At least I found a workaround.

Categories

Resources