Database Develop

[Q] Boot loop on Bootloader unlocked screen

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!!

Encryption Unsuccessful

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.

Stuck on TWRP after attempted restore

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

Question Bootloop to recovery after Odin Flash

I'm having a strange issue when flashing updates and magisk on my s21 ultra
When I try to flash an update with odin I'm using "HOME_CSC" as I want to keep the data on the device. However it results in a boot loop to recovery where I have 3 options
1. Restart the phone
2. Factory reset
3. Check logs
Restarting the phone just restarts it and boots to the same menu.
Only way to fix it is to do factory rest or flash normal CSC, but that wipes my data so I want to avoid it.
I've checked the logs and saw an error saying
Unable to set property "ro.boottime.init.mount.cache to" "3"
I've tried wiping cache in recovery as well, but that didn't help.
I also have the same issue when I flash magisk boot image with odin. it bootloops to recovery, and the only way to fix it is to do factory reset. Surprisingly the device is still rooted after the reset.

Have the same problem here, anyone here who have a solution for this?

Question How do i get Stock recovery to not replace TWRP when rebooting???

Tried a bunch of things to make the TWRP installation persistent, but it just goes back to MIUI recovery when i reboot from the system.
I'm using TWRP 3.5.2 by Nebrassy.
USB debugging turned on
Correct drivers installed
fastboot devices work Using minimal ADB and fastboot
I have the file renamed as TWRP.img.
Steps i followed:
fastboot boot "TWRP.img" - Correctly boots into TWRP
install the TWRP image to the recovery partition - Happens with no errors
Reboot to system - No errors there as well
Reboot to recovery - Goes back to MIUI recovery.
Can someone please tell me what i should do?
PS: Tried with TWRP 3.6.0 as well just now. Same issue.

Helhound0 said:
Tried a bunch of things to make the TWRP installation persistent, but it just goes back to MIUI recovery when i reboot from the system.
I'm using TWRP 3.5.2 by Nebrassy.
USB debugging turned on
Correct drivers installed
fastboot devices work Using minimal ADB and fastboot
I have the file renamed as TWRP.img.
Steps i followed:
fastboot boot "TWRP.img" - Correctly boots into TWRP
install the TWRP image to the recovery partition - Happens with no errors
Reboot to system - No errors there as well
Reboot to recovery - Goes back to MIUI recovery.
Can someone please tell me what i should do?
PS: Tried with TWRP 3.6.0 as well just now. Same issue.
Click to expand...
Click to collapse
Try again to flash TWRP dirty and if it's started don't boot with software. You have to boot TWRP again by pressing volume + and power button until you'll get vibration , afterwards you'll be in TWRP again, clear dalvik and cache and restart system via TWRP menu

Laptapper said:
Try again to flash TWRP dirty and if it's started don't boot with software. You have to boot TWRP again by pressing volume + and power button until you'll get vibration , afterwards you'll be in TWRP again, clear dalvik and cache and restart system via TWRP menu
Click to expand...
Click to collapse
Sorry mate that didn't work. Still going back to stock recovery...

Since i didn't find a solution to make the installation presistant, i went ahead and flashed Elixir with the temporarily booted TWRP. Then wiped cache and dalvik, flashed the TWRP image, formatted data and then rebooted. Now it works.
Edit: This method did something to my recovery. I can boot to system and recovery fine but TWRP isn't able to mount the data partition. So i'm not able to flash anything or root the device anymore.
I tried formatting data, no luck.
Then tried repairing the data partition. No luck.
Changed the file system to EX2 and then EX4... Nothing.
Anyone know a solution for this?

Helhound0 said:
Sorry mate that didn't work. Still going back to stock recovery...
Click to expand...
Click to collapse
Then you've got to do a flash with stock ROM and miflash via pc

Laptapper said:
Then you've got to do a flash with stock ROM and miflash via pc
Click to expand...
Click to collapse
Would that re-lock the bootloader? And if so do i have to wait 7 more days for it to be unlocked?

I used the Disable-Dm-Verity-Zip directly in TWRP after installation. Worked without a problem.

romuser87 said:
I used the Disable-Dm-Verity-Zip directly in TWRP after installation. Worked without a problem.
Click to expand...
Click to collapse
I read that somewhere too but that didn't help me at all... Maybe i have a bad zip file..
Can you share the zip you flashed?
Also, any idea how i could get this fixed:
Helhound0 said:
Since i didn't find a solution to make the installation presistant, i went ahead and flashed Elixir with the temporarily booted TWRP. Then wiped cache and dalvik, flashed the TWRP image, formatted data and then rebooted. Now it works.
Edit: This method did something to my recovery. I can boot to system and recovery fine but TWRP isn't able to mount the data partition. So i'm not able to flash anything or root the device anymore.
I tried formatting data, no luck.
Then tried repairing the data partition. No luck.
Changed the file system to EX2 and then EX4... Nothing.
Anyone know a solution for this?
Click to expand...
Click to collapse

Helhound0 said:
I read that somewhere too but that didn't help me at all... Maybe i have a bad zip file..
Can you share the zip you flashed?
Also, any idea how i could get this fixed:
Click to expand...
Click to collapse
The attached file worked for me

Helhound0 said:
Would that re-lock the bootloader? And if so do i have to wait 7 more days for it to be unlocked?
Click to expand...
Click to collapse
1. With MiFlash there is an option at the bottom of the screen to lock bootloader. Just make sure it is NOT checked, and you will be safe to use MiFlash without relocking bootloader.
2. When installing TWRP for first time, it is essential that your first reboot is straight back to TWRP - then it becomes persistent, and future reboots to recovery will be to TWRP. If you do not do the first reboot back to TWRP, the stock MIUI ROM recovery reinstalls itself.

HiQual said:
1. With MiFlash there is an option at the bottom of the screen to lock bootloader. Just make sure it is NOT checked, and you will be safe to use MiFlash without relocking bootloader.
2. When installing TWRP for first time, it is essential that your first reboot is straight back to TWRP - then it becomes persistent, and future reboots to recovery will be to TWRP. If you do not do the first reboot back to TWRP, the stock MIUI ROM recovery reinstalls itself.
Click to expand...
Click to collapse
The first ever twrp install i did, i rebooted to system by mistake but i reflashed twrp and made sure to reboot to recovery.... That was the second try. I think i may have tried at least two dozen times since that but it just kept booting back to stock recovery...
I think I'll run with this until the end of Jan and then redo everything from scratch...

Helhound0 said:
Since i didn't find a solution to make the installation presistant, i went ahead and flashed Elixir with the temporarily booted TWRP. Then wiped cache and dalvik, flashed the TWRP image, formatted data and then rebooted. Now it works.
Edit: This method did something to my recovery. I can boot to system and recovery fine but TWRP isn't able to mount the data partition. So i'm not able to flash anything or root the device anymore.
I tried formatting data, no luck.
Then tried repairing the data partition. No luck.
Changed the file system to EX2 and then EX4... Nothing.
Anyone know a solution for this?
Click to expand...
Click to collapse
I'm stuck at this stage. Have you found any solution yet?