Database Users

P9 lite custom rom setup troubles + softbrick

Hi everyone,
i hope someone has time to help me on this. I had some experience with flashing custom roms with Lenovo a6000 and some Samsung phones, but it seems there's some things that are different with p9 Lite (L21), or some things i don't understand.
First things first, i've followed steps on how to install LineageOS (LineageOS-14.1-20171228-hi6250-UNOFFICIAL-HassanMirza01) over stock Nougat rom (B381), so i've unlocked the bootloader, flashed Revolution recovery via fastboot, and then installed the rom, gapps, magisk... What happened after installing magisk is a sudden restart, and after that, i got stuck at the LineageOS boot logo (i've let it work for over an hour until i gave up)... Thinking magisk was a problem, i also tried SuperSU, but had the same situation - restart before it finnished. Afterwards i've tried flashing EliteTWRP and after success, i've flashed the Omni-7.1.2-20171201-hi6250-HOMEMADE-HassanMirza01.zip, which also got stuck at the Omni boot logo, but i was able to do installation both with magisk and then again with supersu. Reading through XDA gave me some suggestions, one of them being to format userdata, which gave me a message that the command is not allowed.
Then i made a huge mistake of accidentally formatting internal dalvik+cache+data+system+INTERNAL STORAGE via recovery... After that, the Omni boot logo stopped showing, and i've been trying to repair it since then.
What i've tried so far is:
- fastboot flash boot, recovery (stock), system:
from what i've read there's also a CUST.img that i need to flash, but when i extract update.app that i had installed before all this, it doesn't contain it. I've tried flashing cust.img from another package, but it gives an error.
- after flashing boot, recovery and system.img, i've tried copying various update.app versions to dload on sdcard, then forcing update via pwr+volup+voldown, but every single one gives me "Software install failed - incompatibility with current version - please download the correct update package"... the same happens with downgrade package update.app.
It seems that only B381 update.app, when copied to sdcard and executed in the same way, gives a somewhat different message, instead of "incompatibility with current ver..." it says "Get help from http:..."
- adb shell dd if=/external_sd/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo // re-locked my bootloader
- i can unlock the bootloader and install twrp again via fastboot oem unlock *************** and fastboot flash recovery
- i've also tried unbricking options via P9 Lite Toolkit app, no success.
- HiSuite recovery option says device is not supported for system recovery
Any suggestions ?

hexahive said:
Hi everyone,
i hope someone has time to help me on this. I had some experience with flashing custom roms with Lenovo a6000 and some Samsung phones, but it seems there's some things that are different with p9 Lite (L21), or some things i don't understand.
First things first, i've followed steps on how to install LineageOS (LineageOS-14.1-20171228-hi6250-UNOFFICIAL-HassanMirza01) over stock Nougat rom (B381), so i've unlocked the bootloader, flashed Revolution recovery via fastboot, and then installed the rom, gapps, magisk... What happened after installing magisk is a sudden restart, and after that, i got stuck at the LineageOS boot logo (i've let it work for over an hour until i gave up)... Thinking magisk was a problem, i also tried SuperSU, but had the same situation - restart before it finnished. Afterwards i've tried flashing EliteTWRP and after success, i've flashed the Omni-7.1.2-20171201-hi6250-HOMEMADE-HassanMirza01.zip, which also got stuck at the Omni boot logo, but i was able to do installation both with magisk and then again with supersu. Reading through XDA gave me some suggestions, one of them being to format userdata, which gave me a message that the command is not allowed.
Then i made a huge mistake of accidentally formatting internal dalvik+cache+data+system+INTERNAL STORAGE via recovery... After that, the Omni boot logo stopped showing, and i've been trying to repair it since then.
What i've tried so far is:
- fastboot flash boot, recovery (stock), system:
from what i've read there's also a CUST.img that i need to flash, but when i extract update.app that i had installed before all this, it doesn't contain it. I've tried flashing cust.img from another package, but it gives an error.
- after flashing boot, recovery and system.img, i've tried copying various update.app versions to dload on sdcard, then forcing update via pwr+volup+voldown, but every single one gives me "Software install failed - incompatibility with current version - please download the correct update package"... the same happens with downgrade package update.app.
It seems that only B381 update.app, when copied to sdcard and executed in the same way, gives a somewhat different message, instead of "incompatibility with current ver..." it says "Get help from http:..."
- adb shell dd if=/external_sd/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo // re-locked my bootloader
- i can unlock the bootloader and install twrp again via fastboot oem unlock *************** and fastboot flash recovery
- i've also tried unbricking options via P9 Lite Toolkit app, no success.
- HiSuite recovery option says device is not supported for system recovery
Any suggestions ?
Click to expand...
Click to collapse
http://www.meticulus.co.vu/p/hi6250-custom-rom-installation.html

Thanks.
I've managed to revert to stock by following one thread here on XDA. What I did was install L21C432oemInfo-DS.zip, then wipe everything via TWRP, and finally copy the L21C432B130 update app to dload folder on sd card, then the setup went without any problems.
I am now doing a full backup via Meticulus TWRP before i do anything.
There's one thing i dont understand about AOSP and RessurectionRMX roms, it says they're EMUI5 based - does that mean i'd have to update to EMUI5 based stock rom before i try installing it (prerequisites don't mention anything emui related) or that simply means the rom contains EMUI5 ?

hexahive said:
Thanks.
I've managed to revert to stock by following one thread here on XDA. What I did was install L21C432oemInfo-DS.zip, then wipe everything via TWRP, and finally copy the L21C432B130 update app to dload folder on sd card, then the setup went without any problems.
I am now doing a full backup via Meticulus TWRP before i do anything.
There's one thing i dont understand about AOSP and RessurectionRMX roms, it says they're EMUI5 based - does that mean i'd have to update to EMUI5 based stock rom before i try installing it (prerequisites don't mention anything emui related) or that simply means the rom contains EMUI5 ?
Click to expand...
Click to collapse
You must already be on EMUI 5 to install EMUI5 based ROMs.

TWRP fails to flash ROM (error 7) and asks for a password.

OK, so I totally ****ed up somewhere while trying to wipe and flash stock while I could only see half my screen. I now have a fully working screen but no system.
Current situation is if trying to boot phone normally I get stuck on ZTE logo.
If I press volume keys during boot I get to here; https://puu.sh/z7YQa/8de2adc04e.jpg
Selecting recovery takes me to TWRP which immediately asks for a password (that I never set up).
If I attempt to flash RR (which was previously installed) I get error 7. (Lineage OS has the same response) https://puu.sh/z81cA/6371d882cc.jpg
I can successfully flash the latest TWRP (twrp-3.2.1-0-ailsa_ii.img).
I've also tried flashing A2017_N_Modem.zip and ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip which appear to complete successfully.
TWRP ADB Sideload seems to work and my PC can see the phone (adb devices but I've not tried anything with that yet for fear of ****ing up further.
Code:
C:\Users\Fish\Downloads\ADB>adb devices
List of devices attached
e33edd51 sideload

MrGodMan said:
OK, so I totally ****ed up somewhere while trying to wipe and flash stock while I could only see half my screen. I now have a fully working screen but no system.
Current situation is if trying to boot phone normally I get stuck on ZTE logo.
If I press volume keys during boot I get to here; https://puu.sh/z7YQa/8de2adc04e.jpg
Selecting recovery takes me to TWRP which immediately asks for a password (that I never set up).
If I attempt to flash RR (which was previously installed) I get error 7. (Lineage OS has the same response) https://puu.sh/z81cA/6371d882cc.jpg
I can successfully flash the latest TWRP (twrp-3.2.1-0-ailsa_ii.img).
I've also tried flashing A2017_N_Modem.zip and ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip which appear to complete successfully.
TWRP ADB Sideload seems to work and my PC can see the phone (adb devices but I've not tried anything with that yet for fear of ****ing up further.
Click to expand...
Click to collapse
Look, you have an A2017G, right? Error 7 is caused by not flashing the universal bootloader. The password is because you forgot to flash magisk or supersu on the last rom's first boot.
Download 3 things: raystef66's TWRP flashable B09 bootstack and stocksystem zips (from the download center or the dedicated thread, but make sure that it's the TWRP flashable ones) and Magisk 15.2. Install the BOOTSTACK, then the ROM, then Magisk. After that go to Wipe, and FORMAT DATA (not wipe!). You'll lose your internal storage.

Choose an username... said:
Look, you have an A2017G, right? Error 7 is caused by not flashing the universal bootloader. The password is because you forgot to flash magisk or supersu on the last rom's first boot.
Download 3 things: raystef66's TWRP flashable B09 bootstack and stocksystem zips (from the download center or the dedicated thread, but make sure that it's the TWRP flashable ones) and Magisk 15.2. Install the BOOTSTACK, then the ROM, then Magisk. After that go to Wipe, and FORMAT DATA (not wipe!). You'll lose your internal storage.
Click to expand...
Click to collapse
Thank you so much. Got that all done nicely and have a working stock ROM.
How would I now get from here back to RR?

MrGodMan said:
Thank you so much. Got that all done nicely and have a working stock ROM.
How would I now get from here back to RR?
Click to expand...
Click to collapse
Reading instructions is a start :laugh:
For real now: Get the ROM, the B15 universal bootloader (from the Lineage thread), get the latest modem file from the download center (B09 now for example), Magisk 15.2, GApps zip (unless you'll go microG) and be sure that you are on the latest TWRP or update to it.
Flash the bootloader and modem file (you'll have to install the modem as image i think). After you flash the bootloader your phone model becomes 'axon7' instead of 'ailsa_ii'; most custom roms use this to know whether you flashed it or not; and the region will be A2017U which is normal (it is based off of B15 for the U, don't panic). After that, flash the ROM and Magisk and GApps.

Choose an username... said:
Reading instructions is a start :laugh:
For real now: Get the ROM, the B15 universal bootloader (from the Lineage thread), get the latest modem file from the download center (B09 now for example), Magisk 15.2, GApps zip (unless you'll go microG) and be sure that you are on the latest TWRP or update to it.
Flash the bootloader and modem file (you'll have to install the modem as image i think). After you flash the bootloader your phone model becomes 'axon7' instead of 'ailsa_ii'; most custom roms use this to know whether you flashed it or not; and the region will be A2017U which is normal (it is based off of B15 for the U, don't panic). After that, flash the ROM and Magisk and GApps.
Click to expand...
Click to collapse
Perfection.
Everything works!

How do I install OS in MOTO G4 Plus(Andriod) without using fastboot and TWRP?

I've tried to upgrade the rom in MOTO G4 Plus using TWRP version of 3.2.1.0 and during installation process I wiped out the existing android 7.0.1 without backup(understood the cost of backups now). As I faced error while installing android 9.0.1 with error 255 code because of TWRP some upgrade issue couldn't complete the installation process successfully.
I tried multiple ways to upgrade TWRP which was not successful and even fastboot commands aren't working now. Whenever I try fastboot + combinational command like devices and etc it goes into an infinite loop with an error code iterator not found. After a good amount of search found about ADB and happily can connect to my device using ADB now. Then started trying with multiple options like adb side load after reading multiple forum answers and posts I did pushed a rom to scared/data/media after reading this forum NEED HELP: Accidentally deleted OS in TWRP/Cant install Rom which was successfully pushed but didn't do any thing nor I couldn't understand what to do after pushing it.
Then started search again to install stock rom in any different ways before coming here and stumbled at this question which is similar did read the question and included forum post in it to go start the process when I did download stock rom stock rom download couldn't find any flashall.sh file to start the process
Now I'm stuck and couldn't find better place to find a working solution for this situation. Can somebody help me? What can I do while my phone is in this state?

can someone please help me out from this situation

Do you still have access to TWRP on your device? If so, what ROM did you push to your device? You might like to try with a TWRP flashable like the stock ROM Oreo flashable https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367 and follow the instructions to install it (i.e. push to your device, or copy to an SD card, then tap install in TWRP to flash it to your device). This TWRP flashable should work on your TWRP version since it's 32 bit.
The stock ROM download would still require fastboot, so I'm not sure why your fastboot is not working. What fastboot are you using (is it minimal ADB/fastboot or the Google ADB) and have you downloaded/installed the Motorola USB drivers as well? https://support.motorola.com/us/en/drivers
(As you probably found out, error 255 when flashing custom Oreo or Pie ROMs means that your TWRP is 32 bit, whereas the custom ROM requires a 64 bit TWRP. What 64 bit TWRP are you flashing that are not successful, and how are you flashing the 64 bit TWRP, via fastboot or in TWRP?)

echo92 said:
Do you still have access to TWRP on your device? If so, what ROM did you push to your device? You might like to try with a TWRP flashable like the stock ROM Oreo flashable https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367 and follow the instructions to install it (i.e. push to your device, or copy to an SD card, then tap install in TWRP to flash it to your device). This TWRP flashable should work on your TWRP version since it's 32 bit.
The stock ROM download would still require fastboot, so I'm not sure why your fastboot is not working. What fastboot are you using (is it minimal ADB/fastboot or the Google ADB) and have you downloaded/installed the Motorola USB drivers as well? https://support.motorola.com/us/en/drivers
(As you probably found out, error 255 when flashing custom Oreo or Pie ROMs means that your TWRP is 32 bit, whereas the custom ROM requires a 64 bit TWRP. What 64 bit TWRP are you flashing that are not successful, and how are you flashing the 64 bit TWRP, via fastboot or in TWRP?)
Click to expand...
Click to collapse
HI Echo92,
Thanks a ton and you are really awesome. It worked and I'm really thankful to you again Echo.
For the later questions:
I haven't been using the 64bit TWRP for flashing this Custom Pie ROM which was my mistake. I was using 32bit and doing on TWRP directly. What version of TWRP should I use in order to install the Custom Pie ROM I've mentioned in this reply Echo? Could you please share the link or help me with the version.
Thanks a ton and ahead again Echo.

chintu008 said:
HI Echo92,
Thanks a ton and you are really awesome. It worked and I'm really thankful to you again Echo.
For the later questions:
I haven't been using the 64bit TWRP for flashing this Custom Pie ROM which was my mistake. I was using 32bit and doing on TWRP directly. What version of TWRP should I use in order to install the Custom Pie ROM I've mentioned in this reply Echo? Could you please share the link or help me with the version.
Thanks a ton and ahead again Echo.
Click to expand...
Click to collapse
Try https://forum.xda-developers.com/mo...t/recovery-team-win-recovery-project-t3842903 or https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206
Both are 64 bit TWRP recoveries. You should be able to download them to your device, then install them via your existing TWRP recovery. Reboot to recovery then flash the 64 bit custom ROM and the relevant 64 bit (arm64) GApps package.

echo92 said:
Try https://forum.xda-developers.com/mo...t/recovery-team-win-recovery-project-t3842903 or https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206
Both are 64 bit TWRP recoveries. You should be able to download them to your device, then install them via your existing TWRP recovery. Reboot to recovery then flash the 64 bit custom ROM and the relevant 64 bit (arm64) GApps package.
Click to expand...
Click to collapse
I Tried to install both TWRP with fastboot but unfortunately my fastboot is not yet working Echo. It is looping infinite times when I tried any commands with fastboot.

chintu008 said:
I Tried to install both TWRP with fastboot but unfortunately my fastboot is not yet working Echo. It is looping infinite times when I tried any commands with fastboot.
Click to expand...
Click to collapse
As I mentioned, did you try to flash the recovery whilst booted into TWRP, instead of using fastboot? You should be able to install the zip then reboot to the recovery, then you should have 64 bit TWRP.
From presently installed TWRP on the device:
* Copy the .img file to your phone and reboot to recovery
* Tap Install > Choose Flash Image > Navigate to the path where you copied the .img file and choose it.
* Choose Recovery Partition
* After the install being successful, go to home and tap Reboot > Reboot Recovery.
At this point, twrp should greet you and after you allow modifications, do whatever you want to.*
Click to expand...
Click to collapse
Credit to https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206

[HELP] Flashing OP6T

After reading so many guides and going through ROM threads, I've been left confused on how to flash my 6T with different ROMs and the best way of doing it without bricking the device.
Currently I am on rooted OOS 10.3.4 running Cleanslate Kernel. (TWRP 3.4.0)
So can anybody help me with these questions for which I am UNABLE to find any answers.?
1. What Fastboot Rom should I flash on my device if I cant find 10.3.4 fastboot. Can I flash 10.3.3 and proceed? Also, can I flash fastboot roms via TWRP without the need of turning on my PC.
2. A lot of people are suggesting downgrading TWRP to 3.3.x. How do I downgrade it? By merely running the .img file in the fastboot mode and flashing the zip?
3. Does TWRP 3.3.x have that AB partition thing where we have to flash everything TWICE to get the roms on both the slots? Or just a single swipe to install would do?

1. Use the SourceForge Link on the Fastboot Thread, even 10.3.5 is there. If you want though you can use 10.3.3
2. Just run the 3.3.1-32 installer from 3.4.x. I removed 3.4.x from my LOS Guide as it caused so many problems. The installer for -32 works properly and will still install in both slots. No need to do the install "ramdisk method."
3. No matter which version you choose your phone will still have a A/B partitions. You can't (well shouldn't) have OOS and an AOSP rom on each. Both partitions need to have the same type of ROM. It can cause weird problems if they are different. This is why on the initial install you flash the ROM twice. When you update your ROM, you only flash it once.
My Installing Lineage Guide works for many other custom ROMs, you might look through it. There is also a Cliff Notes version in Post 2 if you want something a bit shorter.

[Help] I can no longer access wifi after flashing TWRP

So i've exhausted almost every xda thread I can find, and finally decided to make a post myself. This is maybe the 6th or 7th time I've had to MSM tool my phone because I softbricked and could only access bootloader. I'm a newbie so you may need to go in detail in what I should do. All help is very appreciated.
I'm trying to flash a new ROM to my phone, the one in question is the latest nightly build of LineageOS: lineage-17.1-20200806-nightly-fajita-signed.zip, the ROM itself works fine, however, flashing TWRP after flashing this rom (even if I wipe dalvik/cache) I no longer am able to access wifi). I've flashed stock and started over about 5-6 times (from the very very beginning, including unlocking the bootloader) and I'll always end up with a wifi issue or a bootloop.
I've tried multiple different versions of twrp, including the unofficial 3.3.1-32 Q unofficial builds from this guide and both 3.4.0-0 and 3.4.0-1 from the official website, both leading me to the same results. (the unofficial build wouldn't decrypt, so I failed with that one).
I'll go through the steps I do in detail, and if anyone sees an issue with my process, please correct me.
1- enabled developer options
2- enabled usb debugging and oem unlocking in developer options
3- booted into bootloader with
Code:
adb reboot bootloader
4- checked to see if phone is connected and unlocked the bootloader with
Code:
fastboot oem unlock
5- set up my phone again, enabled dev options, and enabled usb debugging again.
6- booted into bootloader again
7- typed this into the terminal to temporarily boot TWRP
Code:
fastboot boot <recovery_twrp>.img
7.5- flash copy-partitions.zip from the LineageOS install guide
8- went to advanced>adb sideload>swiped then went on adb terminal to sideload TWRP installer
Code:
adb sideload <twrp-installer>.zip
9- went to menu>reboot>recovery
10- after rebooting went to wipe>factory reset slide>swiped slider
11- went back to menu>advanced>adb sideload>swiped then went on adb terminal to sideload (while checking wipe cache/dalvik)
Code:
adb sideload <lineageOS-rom-nightly>.zip
12- tapped reboot system
this is where things begin to go wrong:
- i notice that I can't boot into lineageOS, lineageOS claims android data is corrupted and needs to factory reset
- factory reset phone
- boots up fine, go through set up process (wifi works right now, only problem I notice is that within build settings, it shows a completely different phone number on my SIM card rather than the phone number I actually have, but it doesn't look broken or corrupted), enable usb debugging again, boot into bootloader
- type
Code:
fastboot boot <recovery-twrp>.img
- twrp loads up fine
- go to menu>advanced>adb sideload>swipe to begin sideload then type
Code:
adb sideload <twrp_installer>.zip
- reboot system
- boot process takes forever, (restarts 3-4 times) phone feels sluggish, and wifi will no longer work (data works fine)
- i give up and I MSM tool my phone.
I genuinely think this is because of TWRP, I read through a few xda threads claiming that the official 3.4.x builds had many issues, and therefore would reccomend using 3.3.x builds. I tried both from the official website and the unofficial TWRP by mauronofrio, where i get decryption problems on both of them. only 3.4.0-x TWRP builds would get me as far as flashing the rom. I've tried this process on both android 10.3.0 and 10.3.5
I genuinely would like some help. this phone is my daily driver and not being able to use TWRP (let alone properly flash a ROM) is a big problem that destroys what I loved about my phone in the first place. Thanks in advance.

I'm assuming this is not a TMobile 6T. With that assumption.
Try my LOS install guide. Note I couldn't get the 10.3.5. fastboot ROM to work. However if you are already on 10.3.5 stock, you are fine, just go with it. I updated manually to 10.3.5 using TWRP, and then used the latest weekly build and everything has been fine. Just go straight to the TWRP step. Other wise use the 10.3.4 fastboot rom. Cliff notes version in the second post.

https://forum.xda-developers.com/on...ash-magisk-t4022157/post81248271#post81248271
Follow this thread. If you're losing WiFi in stock from flashing twrp, there's way to prevent it

Extreme_Ninja2099 said:
https://forum.xda-developers.com/on...ash-magisk-t4022157/post81248271#post81248271
Follow this thread. If you're losing WiFi in stock from flashing twrp, there's way to prevent it
Click to expand...
Click to collapse
Im not rooted, im coming from unrooted 10.3.5

OhioYJ said:
I'm assuming this is not a TMobile 6T. With that assumption.
Try my LOS install guide. Note I couldn't get the 10.3.5. fastboot ROM to work. However if you are already on 10.3.5 stock, you are fine, just go with it. I updated manually to 10.3.5 using TWRP, and then used the latest weekly build and everything has been fine. Just go straight to the TWRP step. Other wise use the 10.3.4 fastboot rom. Cliff notes version in the second post.
Click to expand...
Click to collapse
this worked!! thank you so much for such a great guide!
I did one thing differently though, instead of using the fastboot rom or running it through scripts, I used the copy-partitions.zip file available on LineageOS' fajita install guide to make both partitions appear the same. I realized my mistake when I didn't flash the rom twice, as that's mandatory when it comes to A/B partitioned phones
Everything works smoothly! thanks!