Hi guys.
So after developing an audio bug on Lineage OS 15.1 (a story for another day) I decided to restore one of my old backups via TWRP (unofficial decrypt-friendly version).
I press restore, get some sort of error about mounting /system and then on reboot I get a message asking me to factory reset which takes me to TWRP. Not too surprised by this point because the Huawei bootloader is quirky.
However, when I go into TWRP, it simply gets stuck on the loading screen endlessly. I left it for several hours and it didn't budge. Rebooted several times.
I tried reflashing TWRP via fastboot, no dice, same result. I flashed the official recovery too. That loads fine, but obviously I can't restore with that because it doesn't support encryption.
So I'm a bit stuck here. I've read somewhere that it takes ages to load when you have plenty in the data and cache folders, which I do, but I really don't want to wipe because I have a full week of precious holiday photos and videos I wasn't able to back up (No access to a PC at the time).
Any advice?
Not sure how to fix the TWRP restore problem, but have you tried connecting to your PC while in TWRP? If I remember correctly, it'll allow you to connect to a computer so you could access your storage and backup the files you need.
frost_icewind said:
Not sure how to fix the TWRP restore problem, but have you tried connecting to your PC while in TWRP? If I remember correctly, it'll allow you to connect to a computer so you could access your storage and backup the files you need.
Click to expand...
Click to collapse
Problem is that everything is encrypted, so even if it does show up it will be gobbledygook (nonsense).
Lesson to learn from this: always backup before trying to update ROM or flash something new.
I guess what you can do is to try to flash Lineage again and see if you can make that boot.
mrabcx said:
Lesson to learn from this: always backup before trying to update ROM or flash something new.
I guess what you can do is to try to flash Lineage again and see if you can make that boot.
Click to expand...
Click to collapse
Yeah, there's a few reasons that happened. Usually I autobackup everything but I had been away from wifi for a week. I backed stuff up via Titanium but obviously that got encrypted too. Restores also have never given me problems in the past so I didn't expect anything to go wrong (still not sure what did).
Anyway, I'm not sure how to flash lineage without TWRP, especially with everything encrypted. To have any chance of getting it to work I'm guessing I'd need to flash it the same way I did originally, which was with everything decrypted which makes the issue moot. Maybe I'm wrong though.
Try flashing a treble rom via fastboot. Then wipe data and cache.
fastboot flash system "GSI. img"
fastboot erase userdata
fastboot erase cache
fastboot reboot
side_flip15 said:
Try flashing a treble rom via fastboot. Then wipe data and cache.
fastboot flash system "GSI. img"
fastboot erase userdata
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Thanks, but I'm trying to prevent loss of data. I'd probably just use e-recovery if I don't mind losing data and want to reset to start again from scratch.
Erasing userdata and cache is just factory reset. It won't wipe your internal storage which where your photos are kept.
Ok, turns out once I chose the "download latest firmware and stock recovery" from erecovery it didn't wipe the internal sd data!
Everything is still there and I can access it now from the huawei stock ROM even though I came from lineage OS. It thankfully does not reset the encryption keys or the pattern lock, so you'll be just fine once you do a system boot and go through the regular setup process.
I recommend this approach because it's pretty hassle free.
Armand Bernard said:
Ok, turns out once I chose the "download latest firmware and stock recovery" from erecovery it didn't wipe the internal sd data!
Everything is still there and I can access it now from the huawei stock ROM even though I came from lineage OS. It thankfully does not reset the encryption keys or the pattern lock, so you'll be just fine once you do a system boot and go through the regular setup process.
I recommend this approach because it's pretty hassle free.
Click to expand...
Click to collapse
Glad you found a way to keep your files, mate
Related
Hi All,
I have the VZW DE and was having trouble deleting files when connecting my phone to Ubuntu (when I tried to delete a file, my phone would reboot). I figured I corrupted some files and had a nandroid backup from a few days ago. So I rebooted into TWRP and did a restore of the backup (system, data, and boot). But now when I reboot, my phone is stuck in a boot loop on the bootloader unlock screen. It will stay on for about 30 seconds, the phone will power down and then back to the bootloader unlock screen . I have no choice but to go back into TWRP.
I tried all that I could, I wiped then restored, same thing. I even had a back up from a few weeks ago but same results. Strange thing is, every time I go back into TWRP and click the Mount button, System mount is always unchecked even when I check it and reboot (same thing happens, stuck on bootloader unlock screen and will have to go back into TWRP)
Any ideas whats happening? I thought the restore would work perfectly but has completely stopped me from getting back on my phone.
Thanks guys!
atomus12 said:
Hi All,
I have the VZW DE and was having trouble deleting files when connecting my phone to Ubuntu (when I tried to delete a file, my phone would reboot). I figured I corrupted some files and had a nandroid backup from a few days ago. So I rebooted into TWRP and did a restore of the backup (system, data, and boot). But now when I reboot, my phone is stuck in a boot loop on the bootloader unlock screen. It will stay on for about 30 seconds, the phone will power down and then back to the bootloader unlock screen . I have no choice but to go back into TWRP.
I tried all that I could, I wiped then restored, same thing. I even had a back up from a few weeks ago but same results. Strange thing is, every time I go back into TWRP and click the Mount button, System mount is always unchecked even when I check it and reboot (same thing happens, stuck on bootloader unlock screen and will have to go back into TWRP)
Any ideas whats happening? I thought the restore would work perfectly but has completely stopped me from getting back on my phone.
Thanks guys!
Click to expand...
Click to collapse
what FW are you on? what twrp version are you using? did you try wiping cache and dalvik before and after restoring your back up?
jayboyyyy said:
what FW are you on? what twrp version are you using? did you try wiping cache and dalvik before and after restoring your back up?
Click to expand...
Click to collapse
Sorry about the delay. Thanks for your response jay!
If by FW you mean firmware, I'm on Verizon's 139.15.1_ghost. I just recently flashed twrp version 2.6.3.1 to prep for 4.4 and it flashed successfully. I wiped cache and dalvik before and after (always like to be on the safe side haha).
I tried a few other methods, like wiping the system and restoring, and wiping system, flashing the flashable zip 139.15.1 and restoring just data from the backup, etc.
I'm thinking about just RSDing my phone with the latest firmware (140.45.5_ghost) and start from scratch. Is that tool available for Linux?
atomus12 said:
Sorry about the delay. Thanks for your response jay!
If by FW you mean firmware, I'm on Verizon's 139.15.1_ghost. I just recently flashed twrp version 2.6.3.1 to prep for 4.4 and it flashed successfully. I wiped cache and dalvik before and after (always like to be on the safe side haha).
I tried a few other methods, like wiping the system and restoring, and wiping system, flashing the flashable zip 139.15.1 and restoring just data from the backup, etc.
I'm thinking about just RSDing my phone with the latest firmware (140.45.5_ghost) and start from scratch. Is that tool available for Linux?
Click to expand...
Click to collapse
thats your problem. you flashed twrp for 4.4 but you weren't on 4.4. I don't believe that twrp is backwards compatible. what you need to do is flash your old twrp back to the recovery. then restore your backup. then flash the stock recovery and system images. then take the ota. then flash the new twrp, then boot phone, say you wnat root. then create another back up of that twrp.
jayboyyyy said:
thats your problem. you flashed twrp for 4.4 but you weren't on 4.4. I don't believe that twrp is backwards compatible. what you need to do is flash your old twrp back to the recovery. then restore your backup. then flash the stock recovery and system images. then take the ota. then flash the new twrp, then boot phone, say you wnat root. then create another back up of that twrp.
Click to expand...
Click to collapse
Never even thought about that! I will try those steps as soon as I get home today!
Thanks jay!!
So I just recently received a new (to me) Nexus 6. Going through the process of unlocking the bootloader I forgot to do the command "fasboot reboot". I then installed TWRP and then booted into it. From there I rebooted the system and was brought to a screen that says encryption unsuccessful. I hit the reset button which brought me to twrp and asked for a password. I typed in "default_password", it did it's thing and rebooted to the same "encryption unsuccesful". I tried searching XDA as well as Google to no avail. When searching Google I found some threads for other devices but I didn't want to get into a worse situation than I'm already in so I thought I'd ask here before trying anything else. Any help would be greatly appreciated!
Update: I flashed the stock image (manually as the flash-all didn't work) and I was able to get the phone to boot up into Android. But whenever I reset the device it gives me the "Your device is corrupt" screen before booting into the system. And it seems like whenever I try to flash supersu or anything I'll get that message and then it just goes to a black screen and never boots into Android. I even tried to restore a TWRP backup and it still just went to the corrupt screen and then black. I was only able to get it to boot into Android after reflashing the stock images again. Is this a problem with the hardware or is there something I can do to fix it?
Edit: I've also noticed under internal storage it's only showing 23 GB available but this is the 64 GB model.
Prozart said:
Update: I flashed the stock image (manually a.
Click to expand...
Click to collapse
Did you format/wipe the system, data and caches - a complete factory reset ?
There are several things going on here.
1. Your device is corrupt message: This is a normal message that appears whenever you attempt to customize the device. It may also appear if there is an issue with the internal storage in general.
2. SuperSU: What version? You should be using the latest (2.76) or you risk having a bootloop.
3. TWRP: What version? Latest is 3.0.2-0. Older versions will offer to flash SuperSU. Don't accept the offer or you will enter a bootloop.
4. Internal storage: When you flashed the stock ROM you also flashed the userdata image in it, which caused you to lose half your storage. Simply wipe internal storage in TWRP to fix.
Your first thing is to fix your internal storage, which should be done through TWRP. From there, you will need to do a complete factory reset, as the failed encryption is the main reason you're getting a corrupt device warning. After the factory reset, restore the stock image, but do not flash userdata.img.
Thanks guys! Doing the factory data reset in stock recovery fixed it for me. It took about 30 minutes to complete, but now I've got root, twrp, and custom ROM and kernel with no issues.
Hello,
I have always been on root but somehow something changed.
Since I tried to flash the newest stable stock (5.0.1), nothing works anymore.
No matter if I flash dm-verity disabler, supersu or magisk, dm-verity gets triggered everytime and my phone just says "decryption unsuccessfull" and won't boot.
I've tried everything to fix this, including: different versions of supersu/magisk, reflashing TWRP recovery, even going completely back to stock, locking the bootloader and everything.
Also I read somewhere that you can flash dm-verity disabler and wipe data to completely remove the encryption, but TWRP showed an error message, something like "failed to wipe, cannot mount /data".
In the end I got stuck with no ROM and I couldn't even access stock recovery anymore because it had the weird password bug, so I had to use the unbrick tool to get it working again.
Can someone tell me what I'm doing wrong?
I have always been on root since the early Nexus 5 days, but now I feel really stupid because I must be missing something obvious, so thank you in advance for any help.
Cheers
What rom are you trying to install and what magisk version are you trying to flash over your preferred rom?
If by chance you are trying to flash OpenBeta 21, I have yet to avoid my data getting encrpyted when trying to flash. And personally, I must have been doing something incorrect ever since I got the phone, because almost every time I've flashed a stock OxygenOS ROM I have triggered encrpytion. In my situation it never seemed to matter if I flashed Magisk, SuperSU, a custom kernel, or even just a modified boot.img along with the disable encryption file... I don't know the steps you're taking, but what I do is this: once I get the "Encryption Unsuccessful" message when trying to boot, I just reboot to fastboot and type "fastboot format userdata". And since flashing stock OxygenOS usually overwrites TWRP with the stock recovery despite my best efforts to avoid it, I tend to go ahead and flash TWRP while I'm booted into fastboot. After, I boot into TWRP; at which point encryption has been removed, yet the total amount of storage available to me is less than 30GB (I have the 128GB model.) You have to go to Wipe, then hit the button on the bottom-right, "Format." Type "yes" in the box and format data. That restores my device back to 111GB free of 113GB. I then transfer over and flash Magisk and whatever other mods I wanted. After that my device is no longer encrypted and works just how I want it to. Hope that helps with your issue.
What rom are you trying to install and what magisk version are you trying to flash over your preferred rom?
Click to expand...
Click to collapse
The newest stock ROM, so this/.
Magisk is also just the newest version (15.3).
go to Wipe, then hit the button on the bottom-right, "Format." Type "yes" in the box and format data.
Click to expand...
Click to collapse
When I tried to do that, it just told me "cannot mount /data" and wipe failed...
kaeptn1 said:
The newest stock ROM, so this/.
Magisk is also just the newest version (15.3).
When I tried to do that, it just told me "cannot mount /data" and wipe failed...
Click to expand...
Click to collapse
If you're not using Blu Spark 8.61 TWRP, then I suggest you install it and try again.
If all else fails, do as @lordcheeto03 suggested and format userdata in fastboot - but note that this will completely wipe your data, including internal storage. Then install TWRP, then flash 5.0.1 and anything else you want.
Sent from my OnePlus3T using XDA Labs
kaeptn1 said:
When I tried to do that, it just told me "cannot mount /data" and wipe failed...
Click to expand...
Click to collapse
If you're getting the encryption unsuccessful error, I don't think you format data in that manner, you gotta use fastboot and fastboot format userdata to remove encryption THEN boot into TWRP to do that.
So this happened, first time unlocking my phone, installed TWRP and everything good, now I wiped all of the phone and I can't flash any ROMs since TWRP can't decrypt the phone either I can't find a way to revert recovery and system to the original state.
Tried Flashing various versions of TWRP, none seem to work.
Tried the vbmeta-patcher
Formated the whole device.
Tried both MiToolUnlock and Tool All in One
Also, after flashing any version of TWRP and booting, it always goes back to the previous version (unofficial 3.3.1-25 by Mauronofrio)
I don't know what else to do. Any help?
fverdeja said:
So this happened, first time unlocking my phone, installed TWRP and everything good, now I wiped all of the phone and I can't flash any ROMs since TWRP can't decrypt the phone either I can't find a way to revert recovery and system to the original state.
Tried Flashing various versions of TWRP, none seem to work.
Tried the vbmeta-patcher
Formated the whole device.
Tried both MiToolUnlock and Tool All in One
Also, after flashing any version of TWRP and booting, it always goes back to the previous version (unofficial 3.3.1-25 by Mauronofrio)
I don't know what else to do. Any help?
Click to expand...
Click to collapse
Try flashing the correct fastboot ROM for your phone, using the Mi Flash Tool.
Then don't wipe everything in future. Stick with wiping just cache, dalvik and data. It's very rare you will need to wipe anything else.
Try this tool to erase and decrypt your internal storage
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Than install rom using usb otg.
Since I never had a problem with an update in years, and I'm also a very stupid person, I didn't backup my data before my latest custom rom (Pixel Experience Plus) update.
I got the notification for the November security patch updates, and I downloaded the zip as usual. For the actual installation I usually reboot my Mi 9T Pro into TWRP, flash both the OS update and Magisk, etc. and reboot. Everything seemed to go smoothly as usual: TWRP asked me to input my unlock sequence, then the usual stuff. Problem is, when I tapped 'Reboot system', it didn't reboot normally: it went into Recovery mode again, and from that moment on there's been no way to do otherwise. But now TWRP doesn't ask me the unlock sequence anymore and looks like there's no way to access the data. I tried injecting the recovery from fastboot, I wiped everything except internal storage (I don't give a damn about the OS anymore at this point); I also tried to reinstall the same old rom from OTG after wiping System, but nothing. Whatever I do, it always boots up in Recovery, and it doesn't ask me the unlock sequence. I know my stuff is still there, it's just that the contents of sdcard aren't accessible and look like random alphanumeric sequences from the TWRP file manager. And yes, that's the whole point of encryption, but I was used to TWRP asking me to unlock/decrypt so in the worst case scenario I would be able to access my data and copy via OTG. But now, with the system unable to boot and the recovery not decrypting my stuff, I'm starting to losing hope. I'm sure here on XDA there are much smarter / knowledgeable people than me, and I hope somebody can help me find a way to break the cycle and return in possession of the data that I stupidly didn't backup.
Any help would be greatly appreciated!
Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.
V0latyle said:
Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.
Click to expand...
Click to collapse
I think I tried both. I say 'I think' since my knowledge could fail here.
I tried re-flashing the TWRP img from OTG, nothing changed.
I successfully sideloaded the OS through ADB, but I'm still stuck.
Should I try both? (In which order)?
Thanks a lot.