Database Develop

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

Moto G5S Plus is soft bricked

I flashed the Pixel Experience 8.1 rom and it worked fine. Now when i flashed the PE rom 9.0 it gave an error showing my storage as 0MB. I managed to fix that, but now when I'm flashing the same PE 8.1 rom, my phone is running into a boot loop. Please help me

Boot into TWRP, wipe everything. Then perform factory reset in TWRP. After that, copy a ROM using PC or otg to device, and flash.

aFoxWhoIsNice said:
Boot into TWRP, wipe everything. Then perform factory reset in TWRP. After that, copy a ROM using PC or otg to device, and flash.
Click to expand...
Click to collapse
I tried that but its not working. I tried flashing other rom too. Its the same issue

_royston_fernandes said:
I tried that but its not working. I tried flashing other rom too. Its the same issue
Click to expand...
Click to collapse
If that's the case, then connect it to your PC, and use fastboot to go back to stock ROM. If you want help go to our telegram group https://t.me/g5splus

I know I'm kinda late but I'm here to help people with the same problem. I force rebooted during a twrp backup (cause I'm dumb) and it caused a softbrick. The recovery was stuck on the start screen and Android also didn't boot. I used the fastboot command fastboot flash boot boot.img to reflash the boot image and boom it worked. I don't know why it got destroyed during a backup but yeah, hope it helped.

[SOLVED] Mi A2 boot loop after TWRP restore

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.

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.

Moto G7+ Flashing Lineage fails -> Touch doesn't work anymore - Brick?

Hello guys!
Yesterday I tried to flash the newest Lineage-built to my new G7+ (XT1965-3, bought in Germany via Amazon), but something went wrong and now I'm afraid, I bricked my phone.
It's not my first flash of Lineage, as I did this in the past already on some older Phones (SII, SIII, S5), but it's the first time, that I have a major issue.
So I followed all the steps on the Lineage-Wiki (on Win10).
After flashing the recovery (the lineage-recovery, not TWRP) I wasn't able to enter the recovery-mode, so the phone booted to StockRom. And probably this was the problem: As it didn't react to VolumeDown+Power, I reflashed the recovery a second time. After that the touch-screen is not working any more.
I am able to enter the recovery-mode and I can boot to Stock-Rom, but in both modes the phone does not react to touch, so I can only use the Volume- and Power-Buttons.
Probably I made more mistakes after that: I thought, that a factory-reset would help, but It didn't. I also relocked the bootloader, but as I saw, that it also did not bring any solution, I unlocked it a second time.
Conclusion: I have a brand new phone, with lineage-recovery, an unlocked bootloader but without touch working.
I also tried to flash Lineage, but the sideload got stuck at 47%. So Lineage is not installed and it boots into Stock, where I can not get any further without touch.
Has anyone any idea, what could be the issue and how I can fix it? I would like to start from scratch, but I don't know, what is the exact problem and if i can for example return to stock recovery.
Thank you!
---- EDIT ----
If it helps: I am able to boot TWRP via "fastboot boot twrp-xxx.img". And in TWRP the touch works!
I could flash lineage directly via TWRP from external sd-card, but i am afraid that after that I won't be able to return if something goes wron.

probably your best bet is to go right back to stock using the LMSA tool and starting fresh. I've seen others encounter similar issues on different devices and always the cleaneast solution was just to role back everything and start over.

Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.

joglxv said:
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
Click to expand...
Click to collapse
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.

digitaljeff said:
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
Click to expand...
Click to collapse
I'm having a similar problem. At first touch was fubar but I was able to return to stock using LMSA and now touch works. I can load TWRP with fastboot and even install a custom ROM and TWRP, but installing any custom ROM results in a boot loop during the finding and installing updates part of the phone setup during first boot. I'm tried Evolution X which I was running previously(for about a month, and then a boot loop started yesterday), PixelOS 10, and AncientOS, but all result in the boot loop on first boot after connecting to wifi.

Fixed
I fixed this somehow by manually flashing the latest stock firmware to slot a, and then extracting the evolution x Rom and manually extracting the IMG files inside and manually fastboot flashing those to slot b. I then set b as the active slot and booted up, patched the boot image with magisk, flashed that, and everything works. Not sure why twrp wouldn't do the trick.

Finally had the time to install Lineage. Now everything works.
I followed the instructions someone posted in the [ROM][OFFICIAL] LineageOS 17.1 [nightlies]-thread and the instructions of the lineage-wiki:
1. fastboot boot TWRP
2. sideload the copy-partitions.zip from lineage-wiki
3. factory reset via TWRP (wipe cache, dalvik and data)
4. sideload lineage
5. reboot bootloader
6. fastboot boot TWRP
7. sideload magisk
8. reboot system
Had a little bootloop the first time rebooting the system, but that was because I forgot to wipe data-partition in step 3. Wiping data and rebooting did it for me.
So I have a working Lineage17.1 with root via Magisk.
Thank you for the help!

I had exactly the same problem like you had. Bought a brand new moto g7 plus and after recovery flash, Touchscreen was not working anymore. I could manage to go back to the bootloader, sideloaded TWRP, but side loading lineage worked for me then. It seemed to be stuck on 47 percent, but this seems to be a normal issue, the file was there and after installing, touchscreen worked normally.