Database Develop

MI3 Bricked COMPLETELY after update cm13 (system partition has unexpected contents)

Hi. I had miui7 running on my Mi3 and I wanted to run cm13. I used cm12 before but went back to stock miui7.
But I needed to update baseband to update to cm13 so i used the cm13update.zip from jrizzoli.github.io/dotfiles/ and it had TWRP (modified maybe?) as the recovery and I easily installed CM13 after that. Later I updated via OTA several times and it went fine until the last time when it would not boot anymore and would stay stuck in bootloop or if i went to recovery, it would start installing the last cm13 update and then end with error 7 and would give system partition has unexpected contents error.
I tried to do EVERYTHING I could to make the phone show ANYTHING other than the cm13 updating in recovery screen or the ANNOYING cm13 logo. NOTHING worked.
I tried using miflash to flash old kitkat 4.3 rom, 4.4 rom (would give partition error but i replaced the flash_all.bat from a tutorial to bypass the partition erro) and the latest 6.0 chinese developer rom and it would finish successfully within under 100 seconds and would either go back to the cm13 bootloop or go to recovery and update cm13.
I tried QPST and emmc download with 4.4 rom and it would end with no error and go right back to bootlogo. tried flashing that rom with miflash and it would end within 80 seconds and go back to boot logo.
I tried QFIL with the latest miui8 chinese dev one with firehose and it would fail when it would go near userdata. dont remember the exact error but it was something like cannot divide by zero.
The ONLY time i could flash a different recovery is when i would use the same cm13update.zip and replace the recovery.img with another img such as cwm or mi stock recovery. when i used cwm, it would also try to install cm13 and fail as well.
I tried taking the battery off and shorting the two points which made it easier to get into EDL mode to try to use QPST with no luck.
among so many tries I booted to cm13 a few times. never could it go to homescreen though. once it would not go past the password lockscreen even if i put in the proper password and another time it would but ALL the apps would crash and i would not be able to even swipe the home screens.
sometimes when i tried flashing the cwm ota roms that was in the phone previously or the latest cm14 with otg usb, i would get
INSTALL ZIP SUCCESSFUL on top of twrp but the whole screen would fill up with red writing which said
Error opening : 'data/data/cyanogenmod.platform' (no such file or directory)
and the same thing about every app that was there on the phone.
i do not care about my files theyre all backed up. I just want to use the phone again. Any help is appreciated. thanks.

bump

Hello there, I can make and upload twrp backup of miui v8 dev version. Have you tried to restore a backup?
You'll have to make new partition for this backup ( there are so many threads like "extend partition mi3" or smth like that)
http://en.miui.com/thread-99430-1-1.html

Tried the ones from this thread?
http://forum.xda-developers.com/xia...instruction-to-restore-mi4-mi3-t3279927/page5

TWRP stopped working on OP3t after 4.5.1 update?

I noticed a couple of weeks ago after updating to OOS 4.5.1 that the phone no longer asked for my decryption password at boot time. It just boots through to the system and asks for the the password at first boot, making it appear that storage is no longer encrypted. The bigger problem, though, is that TWRP doesn't ask for a password anymore either - it just goes straight to the TWRP splash screen and never goes farther. I'm running version 3.1.1-0 of TWRP - not the BlueSpark version, but it has worked up to now, and newer versions caused me no end of problems in the past that corrupted my partitions and forced me to reflash the entire phone.
Should I reflash TWRP - this version or a newer one? I've seen the BlueSpark one recommended, but I don't want to kill the phone by causing encryption problems. I've had this phone almost a year and have had problems with the encryption scheme at virtually every OS upgrade I've done. I'm tired of doing full wipes and going back to Marshmallow. Advice?
**UPDATE** After reading some other posts, I realized I might just not be waiting long enough for TWRP to boot, so I gave it time. After about 10 minutes, I got the TWRP menu and had full access to all my files. This is good news and bad news - since I never provided a decryption password, my disk is apparently unencrypted, although I don't know when that would have happened. So I can do a nandroid backup and proceed with the Oreo update, but I still have the issue of how to restore encryption. Again, advice?

I had another problem - TWRP didn't accept my password, but I could boot to OS with the same pass. Unfortunately full data wipe was needed.
PS Marshmallow is kind of deprecated nowadays

I had a similar problem when I tried to update to 4.5.0. I could get into TWRP but I couldn't mount system, so I couldn't take a backup. Turned out the file system was corrupted. It would boot and run anyway, but recovery was useless. I eventually bricked the phone and restored using the utility that rewrites the original factory image, which is Marshmallow. As soon as the phone connects to the network, it applies the latest patch, so Marshmallow doesn't last long, but it's really nice to have a fail-safe way to restore the phone from any problem.

mobilityguy said:
I had a similar problem when I tried to update to 4.5.0. I could get into TWRP but I couldn't mount system, so I couldn't take a backup. Turned out the file system was corrupted. It would boot and run anyway, but recovery was useless. I eventually bricked the phone and restored using the utility that rewrites the original factory image, which is Marshmallow. As soon as the phone connects to the network, it applies the latest patch, so Marshmallow doesn't last long, but it's really nice to have a fail-safe way to restore the phone from any problem.
Click to expand...
Click to collapse
Did you tried removing password protection from rom ...

P20 - Need help!

So, I've been toying around with my P20 pro - I tried a few project treble ROMS out (ofcourse had a TWRP backup before this) and then decided to restore from backup.
All was well, and I found there was an update.zip for a newer firmware that i flashed in TWRP using HuRUpdater, stupidly realising there were other files I was meant to flash. The phone is all messed up when it boots (wrong words in settings menu, etc etc) and I decide i'll be fine - i'll just go into twrp and restore from my backup again. I go into TWRP, restore from backup (EVERYTHING was backed up) and then reboot... it freezes on the huawei splash and reboots into TWRP but now TWRP won't even load!! It just sits on the splash screen - I've tried reflashing twrp - but still the same it hangs on splash screen. I can get into fastboot mode but that's about it. I can't remember what firmware I was on anyway so can't use FunkyHuawei unbrick tool..
Oh, I've tried flashing a system.img I have but it just keeps kicking me into the endless TWRP splash screen. Scared I've really messed up - got this phone about a week ago... lol.
edit: I've now got into TWRP - but my system backup is encrypted along with everything else!!
Is anyone able to provide me with the following:
A stock system.img for CLT_L29
A stock recovery.img for CLT_L29
..A SOLUTION

you can try via funkyhuawei or the dload method if you can access twrp and push the files to sdcard/dload

This thread has been resolved! I managed to restore my device by extracting the stock recovery from a ROM before flashing to my device - wiping it and then using the FunkyHuawei eRecovery method which initially didn't work for me.
Back up and running better than ever - and rooted of course.
@admin please close

Bootloop after twrp restore - twrp-3.2.3-1-payton.img

Summary:
1. Flash factory image onto phone successfully
2. Install twrp and make a backup
3. Restore backup after reboot and I'm stuck in a bootloop
I have a new fi Moto x4 running Android 8.1 that I'm attempting to set up. I've reset this phone a bunch of times so here is the standards process:
1. Flash factory firmware as shown in this thread:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
I'm using: PAYTON_FI_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2. After flashing, start up the phone and it works fine.
3. Reboot into the bootloader and boot to twrp using: fastboot boot twrp-3.2.3-1-payton.img
4. Copy in the twrp install file using: adb push twrp-installer-payton-3.2.3-1.zip /sdcard
5. Install the zip via the twrp Install function
6. Reboot the phone into the bootloader then start recovery
7. Use the twrp Backup function to create a backup of the Boot, Data and System partitions on Internal Storage (plenty of space).
8. Reboot the phone into the bootloader then start recover
9. Use the twrp Restore function to restore the backup. Finishes fine.
10. Reboot phone to system but the load won't finish. Phone just alternates between the Android One and the Motorola splash screens. Left it for an hour at one point just to be sure. No love.
Things I have tried:
1. Using twrp via fastboot boot and a hard install
2. Making backups to the internal and external memory cards
3. Changing the partitions in the backup
4. Wiping everything except the external sim card before performing a restore
If anyone has any thoughts I would love to here them.
Thank you!

I'm having a similar problem and found this old thread. I am on stock pie rooted and made a twrp backup this morning so that I could try flashing some custom ROMs. After successfully installing a custom ROM I attempted to restore the backup and return to stock but just get bootloop. I am able to get back to to twrp and the phone will boot after a factory reset, but even if I just restore data I get bootloop. I'm wondering what I am doing wrong with restoring the backup. Any thoughts? Thanks.

I have the same problem as you are. After I finished install all applications, I made a backup with twrp-3.2.3-1-payton. Then next day I restore it from the backup, after finished backup, it goes to bootloop forever. My version is OPWS28.46.21.12, I download stock rom OPW28.46-13 but afraid to flash this rom since it is the lower version might be break the phone if not backward compatible. Then I search the web and found your message and follow this side fund a higher version of the stock rom OPWS28.46-21-14. I download it and flash it. After flashing complete and boot up, it saying new OTA update available, I don't want to update the rom since I want my phone rom version is same as the stock rom I have downloaded into my PC just in case in the future I accidentally doing something wrong I can flash back the stock rom without worrying the backward compatibility problem.

t-bob said:
I'm having a similar problem and found this old thread. I am on stock pie rooted and made a twrp backup this morning so that I could try flashing some custom ROMs. After successfully installing a custom ROM I attempted to restore the backup and return to stock but just get bootloop. I am able to get back to to twrp and the phone will boot after a factory reset, but even if I just restore data I get bootloop. I'm wondering what I am doing wrong with restoring the backup. Any thoughts? Thanks.
Click to expand...
Click to collapse
I'm a bit slow on the response - but my first thought is manually flash stock rom over your restore without wiping data

I'm able flash the latest stock rom of FI_9.0_PPWS29.69-26-4 and reinstall twrp-3.2.3-1-payton. Then I restore data only that backup from previous rom, I get bootloop again after restore the data only from TWRP. The I reflash FI_9.0_PPWS29.69-26-4 again, install twrp and root it with Magisk. Restore data from cloud google drive automatically. And this time is successfully without bootloop.

X4 1900-1 Android One boot hangs after TWRP restore

After unlockling bootloader and rooting my spare (Blue) X4 XT1900-1 with Magisk (patched boot.img), I attempted to restore /data via TWRP (3.3.1-0 payton) from a backup taken from my other daily driver X4 (Black). Both phones are identical Android One versions on the same build PPWS29.69-39-6-2 Nov. 1 patch. This initially failed with extractTarFork() process ended with ERROR: 255. I am booting TWRP via fastboot, as I am trying to keep the phones as close to stock as possible while having root.
Apparently some of the data.ext4.win00x files in the may have been corrupt or incomplete—I had copied them from the black X4 to my PC via wifi.
I re-copied the Black X4 backup to the Blue X4 folder on SD via PC and did another restore, wiping data & cache. It completed successfully according to TWRP. This time the phone initially went into a bootloop. I tried restoring a TWRP backup taken from Blue X4 just prior to flashing /data, that resulted in the phone hanging on the Android One splash screen but not bootlooping per se. I can get the phone into fastboot, recovery and boot TWRP via fastboot. I’ve tried various wipe and restore protocols, factory reset, flashing the stock unpatched boot.emmc.win, All yield the same Android One hang. Finally tried switching from slot A to slot B (the phone recently had several updates), that gave Error changing bootloader boot slot to B. However, hitting the Back button then shows Current Slot: B. Rebooting, still hangs on Android One. Back in TWRP, changing back to slot A in TWRP gives same error message: Error changing bootloader boot slot to A.
I saw a thread of similar issues with TWRP 3.2.3-1 from 2018, but no definitive fix short of factory flash and no working way to restore only /data.
https://forum.xda-developers.com/moto-x4/help/bootloop-restore-twrp-3-2-3-1-payton-img-t3853419
No mention of TWRP 3.3.1-0 having same issues.
Wondering if the bootloader is somehow borked? Any suggestions on a fix would be great. If I could find a recent X4 factory Pie firmware to flash would that get it working again?
One thing I am unclear on is which, if any, partitions should be mounted/unmounted while TWRP restoring. I’ve done the /data partition migration before on identical devices running MM and below with no issues. This is my first soft brick in 30 or more device unlockings, rootings and ROM flashings the past 7 years. Very humbling.
TWRP log from one of the attempts attached.

Other than Pie on the X4 having 2 sets of partitions and you maybe restoring it to the wrong one, no idea.

Factory FW flash solved boot hang
KrisM22 said:
Other than Pie on the X4 having 2 sets of partitions and you maybe restoring it to the wrong one, no idea.
Click to expand...
Click to collapse
I checked that carefully before restoring, chose the active slot.
Tonight I flashed the latest factory FW and all is good, phone updating now.
The TWRP restore problem is worrisome (what good is a backup you can't restore?) Anyone else out there had bootloops after restoring a TWRP backup on the X4? I've seen posts about similar problems from 2017-2018 on several devices, but I would hope that whatever the problem was has been sorted out.

redwoodie said:
I checked that carefully before restoring, chose the active slot.
Tonight I flashed the latest factory FW and all is good, phone updating now.
The TWRP restore problem is worrisome (what good is a backup you can't restore?) Anyone else out there had bootloops after restoring a TWRP backup on the X4? I've seen posts about similar problems from 2017-2018 on several devices, but I would hope that whatever the problem was has been sorted out.
Click to expand...
Click to collapse
Glad you got it back! Dunno about TWRP - maybe a pre or early Treble problem? Scary!
EDIT: I wonder if maybe stuff like that won't really be sorted for a couple more releases when most folks will be on a full Treble.