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
Related
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
Hello all..
my name is daniel, i have an H9L. My H9L has been rooted and installed TWRP. I want to install a ROM called LineAgeOS, before that I have backed up the data. and I started to reset my H9L, when I wanted to install a ROM there was a problem, because the difference in my processor failed to install the ROM. and I hit it wrong, I restarted my H9L, now my H9L is on without a stock ROM, and it is strange that my TWRP is not working, just stuck in the TEAMWIN logo, can anyone help me to restore my H9L the original state, my H9L only works in the FASTBOOT MODE state, I tried to flash my H9L with ADB DRIVER but failed, I tried to flash with MICRO SD and made the dload folder but failed at 5%, what have I confused, is there anyone here who can help my problem, THANK YOU.
DjPangau said:
Hello all..
my name is daniel, i have an H9L. My H9L has been rooted and installed TWRP. I want to install a ROM called LineAgeOS, before that I have backed up the data. and I started to reset my H9L, when I wanted to install a ROM there was a problem, because the difference in my processor failed to install the ROM. and I hit it wrong, I restarted my H9L, now my H9L is on without a stock ROM, and it is strange that my TWRP is not working, just stuck in the TEAMWIN logo, can anyone help me to restore my H9L the original state, my H9L only works in the FASTBOOT MODE state, I tried to flash my H9L with ADB DRIVER but failed, I tried to flash with MICRO SD and made the dload folder but failed at 5%, what have I confused, is there anyone here who can help my problem, THANK YOU.
Click to expand...
Click to collapse
Have you tried Erecovery to restore stock?
On the bootloader unlocked warning screen press and hold volume+ for 3 secs.
Needs to use WiFi.
Try yo reflash twrp in fastboot mode. The command is fastboot flash recovery_ramdisdisk twrp. Img
Before you have to put twrp. img in the adb folder
I'm experiencing the same problem after trying to root my h9l through twrp the mistake I made is that I flashed the image in a wrong partition.
I can only access a fastboot mode with frp and phone unlocked, it cannot even display a charging screen. Once plugged it keeps on rebooting and hangs on error screen,
I have tried to flash kernel,ramdisk, recover_ramdisk and system images all on their respective partition, the flashing went well, but the phone didn't respond.
I've tried to flash boot.IMG (some one posted for h9l,) into Boot partition, but it revealed an error.
Any one please help what should I do to brings by device back to lite
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.
EDIT: Solved.
My Mi A2 is unlocked, rooted (Magisk), stock FW V10.0.7.0 (via OTA), not encrypted (Disable-Force-Encryption-Treble.zip)
I wanted to update to V10.0.8.0, so I booted to TWRP and performed a full backup.
After that, I loaded the original boot.img to both boot_a and boot_b, then reboot.
Then the phone auto restarted while showing Android One logo (not showing running color bar yet)
I panicked (1). I booted to TWRP and did a full restore. While restoring Firmware, there was a red error line:
"ExtractTarFork() process ended with error=255"
I pretended nothing happened and reboot. Phone was still unable to boot past the Android One screen.
I panicked (2). Then I flashed the original firmware V10.0.7.0 using official Xiaomi fastboot image (except user data). Phone was still unable to boot past the Android One screen.
I've try some other (stupid/crazy) things except for erasing user data, but phone is still unable to boot now.
Please let me know what I have done wrong, and any possible way to recover the phone without erasing user data.
Solved:
I flashed the original fastboot image, install the Disable-Force-Encryption-Treble.zip and the phone can boot up again.
After flashing the latest TWRP 3.3.1 image file from TWRP 3.2.3 and upon reboot I got an error "Could not do normal boot" and it took me to ODIN mode. Thinking maybe it was a corrupt file I flashed the .tar file from Odin and it successfully completed and rebooted into the system. Okay great. So I tried to boot into recovery from the system and it took me back to the same error. Tried several times to flash recovery from Odin and each time it completes successfully, boots into the system. Everything looks great and works - until I try to boot into recovery. Tried powering down completely and giving it a few minutes but the same thing happens when I power up. the only way I can get back into the system is to flash the TWRP tar file again from Odin and let it boot the system upon finishing.
I have searched the forums and the web without finding any solution that doesn't include going back completely to stock. In those cases the system was corrupted as well. Not really wanting to do that since everything works except booting to recovery. Any suggestions?
Update - I was finally able to download XAR-T813XXS2BSJ3_T813XAR2BSA2-20191016 and install it so I currently have the latest stock I can find for my T813. I have not tried to install TWRP yet on this version. I am a little leery to do so at this point since I've had no luck on any previous attempt.
Well, SSDD! No matter what version TWRP I flash, when I try to boot into recovery I get "Recovery Booting....Could not do normal boot" and it takes me to download mode (Odin Mode). I give up. I guess I am doomed to using a stock tablet and all of my previous apps and set up is no longer accessible. If by some miracle somebody has a fix I'm all ears.
Update - Finally was able to root with CF-Auto-Root through Odin. While it is not my root method of choice it is the only way I can root since TWRP will not load for me. At least I can get to my TB backups and restore most of my apps. Also, I can get rid of the bloat that pure stock sticks on the tablet. If I hadn't just bought a new laptop, I would seriously consider replacing this tablet.