Database Users

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!

OP5 won't accept flashed recoveries

Hello everyone.
I can't flash any recovery via fastboot, I can only flash two recovery files one is the original twrp and second is the original op5 recovery. those cannot install the new ota.
If I try to flash any other recovery file, it enters the qualcomm boot recovery mode, white led and nothing else on phone and a qual 9008 port on pc.
What should I do? My brain kinda melted, so I might forgot to add more infos.

SweetyVolty said:
Hello everyone.
I can't flash any recovery via fastboot, I can only flash two recovery files one is the original twrp and second is the original op5 recovery. those cannot install the new ota.
If I try to flash any other recovery file, it enters the qualcomm boot recovery mode, white led and nothing else on phone and a qual 9008 port on pc.
What should I do? My brain kinda melted, so I might forgot to add more infos.
Click to expand...
Click to collapse
The questions you need to answer:
Is your bootloader unlocked?
Do you have a custom recovery installed?
Is your storage encryped?
What's your actual rom?
What do you want to do(installing ota from android ota menu isn't working for you or why you don't use that method)?
Please give EXACT file names of the files you're trying to flash!

Is your bootloader unlocked? Yes, although I locked then unlocked again for trying.
Do you have a custom recovery installed? yes, I tried both
Is your storage encryped? probably no, I wiped everything but before it wasn't necessary to enter a unlock code or fingerprint etc.
What's your actual rom? It was on oreo, now I don't have a rom lol
What do you want to do(installing ota from android ota menu isn't working for you or why you don't use that method)?
Installing from Ota wasn't successful, sideload does not work, installing custom recoveries result in qualcomm boot (black screen with white led)
only twrp working is this untouched twrp but it has not able to flash the new pie.. https://twrp.me/oneplus/oneplus5.html
twrp from the clockworkmod not able to boot.
My intent is to flash new pie and root. I can't able to flash the pie's original beta recovery too. https://oxygenos.oneplus.net.s3.amazonaws.com/recovery.img

Also I can't mount vendor too I don't know if this causes the problem or not....

SweetyVolty said:
Also I can't mount vendor too I don't know if this causes the problem or not....
Click to expand...
Click to collapse
Ok, so it seems you have an old Oreo stock oos rom before without vendor partition and trying to flash an pie rom and pie recovery, but still on Oreo firmware that's not possible cause newer recoveries need pie firmware which comes along with oos pie roms and you're missing the vendor partition which comes with 5.1.4.
Your starting point is the same as mentioned here https://forum.xda-developers.com/oneplus-5/help/qa-help-thread-newbies-post-t3624656/post79251968
OOS 5.1.4 then you have a vendor partition, then you can install one of those stock Pie oos roms.
You can install oos 5.1.4 with stock recovery or with siankatabg's or with this one
https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk
Then you just need to follow the instructions for the stock oos or beta rom.
If you have any concerns or further questions, please feel free to ask here

[A2017U] 2 Versions of TWRP while reverting back to stock??

Hello
I followed Oki's guide to LOS 15.1 Official and it completed successfully. However, on testing the ROM for few days I felt I am missing Dolby Atmos more than I should so decided to go back to stock(I know we can install Magisk and Dolby Oreo package but am a lil skeptical of the stability as I have read of all sorts of issues about it here + GPAY is finnicky even with the Hide Props module)
So, I followed this guide to return to Stock AFTER I deleted the /vendor partition using the Treble Party tool :
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Now, I cannot get into the system at all. I am stuck with the "unlocked bootloader" screen on every boot and of the available options, I can Reboot, Get to recovery(TWRP), power off and restart only.
If I choose recovery I am going back to a different version of TWRP(3.1.x i guess) from when I had while using Oki's Guide(3.3 I think).
Luckily, EDL is still working so I can go back to LOS 15.1 using Oki's guide but my questions are:
1. Why do I see 2 different TWRPs even though I installed only one(Oki TWRP Labs Mod)?
2. How do I fix this and get back to stock?

savoirtous said:
Hello
I followed Oki's guide to LOS 15.1 Official and it completed successfully. However, on testing the ROM for few days I felt I am missing Dolby Atmos more than I should so decided to go back to stock(I know we can install Magisk and Dolby Oreo package but am a lil skeptical of the stability as I have read of all sorts of issues about it here + GPAY is finnicky even with the Hide Props module)
So, I followed this guide to return to Stock AFTER I deleted the /vendor partition using the Treble Party tool :
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Now, I cannot get into the system at all. I am stuck with the "unlocked bootloader" screen on every boot and of the available options, I can Reboot, Get to recovery(TWRP), power off and restart only.
If I choose recovery I am going back to a different version of TWRP(3.1.x i guess) from when I had while using Oki's Guide(3.3 I think).
Luckily, EDL is still working so I can go back to LOS 15.1 using Oki's guide but my questions are:
1. Why do I see 2 different TWRPs even though I installed only one(Oki TWRP Labs Mod)?
2. How do I fix this and get back to stock?
Click to expand...
Click to collapse
well, you're wrong. You installed TWRP 3.1.x unknowingly, because it comes on the stock files that Draken added there.
Have you ever tried Viper4Android? IMO it's way superior to Dolby at least for headphones. I'd say you should try a Pie GSI like aex or havoc or kmni (you'll only lose VoLTE with gsi's) with Speedy 6.2 and baddar rc1.1
If EDL is working, why not just flash a full stock EDL file? That is probably what you should have done from the start.
But I think you may be able to boot the rom you already have installed if you format your data partition (format, not wipe). Try that before doi g anything else, sometimes the system fails to boot and hangs but formatting data fixes it

Thanks so much for your response
I was not aware that Draken had included TWRP in the Stock Files already. I will try using Viper and GSIs before I go back to stock.
PS: I have seen a lot of your responses throughout the Q&A thread and they have been very informative in understanding all possible implications of any action on our device. Thanks for it as well!

Stuck in fastboot after flashing TWRP (Mi 9T)

First of all why did this happen, presumably I wasn't doing anything wrong or uninformed. I just unlocked the bootloader successfully, afterward as many threads claimed I flashed twrp-3.3.1-2-davinci-fix, and now it simply wont boot neither to system nor twrp. Why did this happen?
Does anyone know how to fix this? Thank you!
Mi 9T (M1903F10G)

Did you try to power off and then turn back on holding power and volume up? I had this issue yesterday but doing the vol up and power got me to twrp then did format and it booted up

cmlucht said:
Did you try to power off and then turn back on holding power and volume up? I had this issue yesterday but doing the vol up and power got me to TWRP then did format and it booted up
Click to expand...
Click to collapse
Thank you for your reply. You can't even power off, it will simply bootloop forever into fastboot. Nonetheless I managed to fix it by flashing fastboot ROM using MIFlash, but man, didn't expect root solutions to be this complicated, unstable, and outdated for our beloved Mi 9T. I simply want to achieve root in the stock rom, and wasted 7 hours yesterday and still got nowhere. I come from a classic LG G2, when things were much simple and straight forward back then. You can stop reading here, but now I had to:
Wait 1 week for bootloader unlock.
Flash TWRP, which soft bricked my phone right away. Why on earth, a recovery image provided in many reliable tutorials from multiple sources cause soft-brick in the second step is beyond my comprehension. I am still genuinely curious why did this happen, and why such a broken image is still circulating here?
Then I had to inform myself all about Anti Rollback, in order to prevent it happening, and concluded that MiFlash is safe, so I got MiFlash and a fastboot rom.
Apparently Mi Flash is terribly buggy and kept showing .net error exceptions because a "LOG" folder was missing in root folder, so let's waste one hour scratching our heads what the hell is happening because the developer missed a simple MkDir line during development.
After creating LOG folder, and installing drivers, couldn't flash any fastboot ROM because my 9T antiroll back number is 1 while fastboot rom ARB index was 0.
Then it appears that this error has actually nothing to do with ARB, but it is because I had to a) start MiFlash from C:\, b) remove name spaces in target address and c) shorten fastboot ROM folder name. So I had to get all these 3 variables right in order to resurrect my phone. MiFlash terrible programming didn't stop at step 4) but it extends into showing entirely confusing ARB errors that have nothing to with the real problem, rather petty programming bugs such as folder naming.
Finally managed to boot up 9T, and we're back at square one.
Afterward successfully flashed mauronofrio TWRP including vbmeta and got recovery working.
I decided to try out few custom ROMs since all my data were erased anyway, but it appears my system was encrypted and TWRP showed encrypted alphanumeric characters, so I had to format data in order to flash files.
Now every-time I flash stock ROM .zip I lose TWRP, and every-time I reflash mauronofrio TWRP I end up in recovery bootloop, and so I can't manage to have both at same time in order to move with the Magisk flash.
10 steps and 7 hours later and still got nowhere, just risked bricking my phone.
Now we have to deal with
a) bootloader wait,
b) twrp encryption mess,
c) anti roll back risk,
d) buggy MiFlash
e) safety net measures
f) no custom ROMs that are pre-rooted and simple
g) dependency of stock ROM files - meaning you can't wipe everything including system and just flash custom ROM .zips, like I used to do with 5 android phones before this one. Now you are somehow dependent on original ROM files which probably means you will have to base install stock MI before you flash anything Xiaomi.EU, Evolution X, PixelExperience etc.​ When did things get so complicated? It seems every year new limitations are introduced and the sheer combination to get them all right give headaches.
Anyway, all I want is to install latest stock ROM from TWRP and keep TWRP so I can also flash Magisk. In other words, how to simply have a rooted stock?

Your mistake is to not use Official TWRP instead of an old TWRP version...

Micdu70 said:
Your mistake is to not use Official TWRP instead of an old TWRP version...
Click to expand...
Click to collapse
Thanks for your reply! Yes, that must have been it. Those outdated tutorials should be removed.
Now I flashed miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM through latest TWRP, but it removed TWRP. When I reflash latest TWRP then it ends up in bootloop.
EDIT: Ended up reflashing all over again using MiFlash. Now the only problem remaining is which version of Magisk is compatible with miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM?

What are you flashing with? I am now using xiaomitools v2 and it installed twrp and magisk with no problems.
I flashed the EU custom stable, I was global but I wanted to compare the 2 and I like the EU better.
I came from a non rootable lg g7.
I have not flashed custom ROMs since my old Galaxy note days.

cmlucht said:
What are you flashing with? I am now using xiaomitools v2 and it installed twrp and magisk with no problems.
I flashed the EU custom stable, I was global but I wanted to compare the 2 and I like the EU better.
I came from a non rootable lg g7.
I have not flashed custom ROMs since my old Galaxy note days.
Click to expand...
Click to collapse
Never heard of XiaomiTools v2, it seems like a great alternative. I used buggy MiFlash to flash fastboot ROM, flashed TWRP, then got a bootloop, formatted data from TWRP and flashed Magisk. It seems everything is working fine now, but in the future I'll make sure to check XiaomiTools v2.
I never used stock ROMs in any of my past phones, first thing I did when I bought a new phone is unlock bootloader and install Lineage or Cyanogenmod back in the days. But somehow I like MIUI so all I needed was root.
It is hard to believe that there are actually phones that have no root at all.

blackmatrix64 said:
Thank you for your reply. You can't even power off, it will simply bootloop forever into fastboot. Nonetheless I managed to fix it by flashing fastboot ROM using MIFlash, but man, didn't expect root solutions to be this complicated, unstable, and outdated for our beloved Mi 9T. I simply want to achieve root in the stock rom, and wasted 7 hours yesterday and still got nowhere. I come from a classic LG G2, when things were much simple and straight forward back then. You can stop reading here, but now I had to:
Wait 1 week for bootloader unlock.
Flash TWRP, which soft bricked my phone right away. Why on earth, a recovery image provided in many reliable tutorials from multiple sources cause soft-brick in the second step is beyond my comprehension. I am still genuinely curious why did this happen, and why such a broken image is still circulating here?
Then I had to inform myself all about Anti Rollback, in order to prevent it happening, and concluded that MiFlash is safe, so I got MiFlash and a fastboot rom.
Apparently Mi Flash is terribly buggy and kept showing .net error exceptions because a "LOG" folder was missing in root folder, so let's waste one hour scratching our heads what the hell is happening because the developer missed a simple MkDir line during development.
After creating LOG folder, and installing drivers, couldn't flash any fastboot ROM because my 9T antiroll back number is 1 while fastboot rom ARB index was 0.
Then it appears that this error has actually nothing to do with ARB, but it is because I had to a) start MiFlash from C:\, b) remove name spaces in target address and c) shorten fastboot ROM folder name. So I had to get all these 3 variables right in order to resurrect my phone. MiFlash terrible programming didn't stop at step 4) but it extends into showing entirely confusing ARB errors that have nothing to with the real problem, rather petty programming bugs such as folder naming.
Finally managed to boot up 9T, and we're back at square one.
Afterward successfully flashed mauronofrio TWRP including vbmeta and got recovery working.
I decided to try out few custom ROMs since all my data were erased anyway, but it appears my system was encrypted and TWRP showed encrypted alphanumeric characters, so I had to format data in order to flash files.
Now every-time I flash stock ROM .zip I lose TWRP, and every-time I reflash mauronofrio TWRP I end up in recovery bootloop, and so I can't manage to have both at same time in order to move with the Magisk flash.
10 steps and 7 hours later and still got nowhere, just risked bricking my phone.
Now we have to deal with
a) bootloader wait,
b) twrp encryption mess,
c) anti roll back risk,
d) buggy MiFlash
e) safety net measures
f) no custom ROMs that are pre-rooted and simple
g) dependency of stock ROM files - meaning you can't wipe everything including system and just flash custom ROM .zips, like I used to do with 5 android phones before this one. Now you are somehow dependent on original ROM files which probably means you will have to base install stock MI before you flash anything Xiaomi.EU, Evolution X, PixelExperience etc.​ When did things get so complicated? It seems every year new limitations are introduced and the sheer combination to get them all right give headaches.
Anyway, all I want is to install latest stock ROM from TWRP and keep TWRP so I can also flash Magisk. In other words, how to simply have a rooted stock?
Click to expand...
Click to collapse
Hey, I'm facing the same issue you faced here. Waited 7 days to unlock bootloader, after unlocking it, flashed a twrp i found on one of the youtube tutorials. Immediate bootloop. Im fairly new to all of this, and dont understand what certain words even mean tbh. Do you mind guiding me in fixing my phone? Any help would be really appreciated. Thank you.

blackmatrix64 said:
Never heard of XiaomiTools v2, it seems like a great alternative. I used buggy MiFlash to flash fastboot ROM, flashed TWRP, then got a bootloop, formatted data from TWRP and flashed Magisk. It seems everything is working fine now, but in the future I'll make sure to check XiaomiTools v2.
I never used stock ROMs in any of my past phones, first thing I did when I bought a new phone is unlock bootloader and install Lineage or Cyanogenmod back in the days. But somehow I like MIUI so all I needed was root.
It is hard to believe that there are actually phones that have no root at all.
Click to expand...
Click to collapse
i miss the Cyanogenmod days

Why am I unable to flash a custom ROM?

Hi there,
I am using a OnePlus 8 Pro on Oxygen OS 11, Global variant. I have been working on this for at least 10 hours now. I bought the OnePlus 8 Pro orginally running Oxygen OS 12, and when I flashed the recovery (TWRP) for the first time to two slots via this explanation
, I bricked the phone so the only tool accessible to me was fastboot.
Hmm okay, I'll just use MSM tool (https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/) to revert back to oxygen OS so I can continue my mission.
I am trying to install the latest CRDROID from their official website after follow their instructions on here. I get as far as being in fastboot mode with the OEM unlocked, and then I try to flash the recovery they provided. It doesn't work. When I select boot into recovery, I get sent back to fastboot, however, when I flashed the original recovery img for Oxygen OS 11 I took from the payload dumper, it loads fine.
OKAY so now I am thinking that perhaps there is a problem with the recovery provided. That is fine so I choose to use TWRP to flash the custom ROM. Thankfully, it does work, and I am able to load into it through recovery, however when I tried to flash the rom through ABD sideload, from the PC whilst in TWRP, it doesn't load! It gets halfway and stops. I tried this several times to no avail.
I choose to then (after having bricked the phone several times by now and having to revert to factory settings with MSM tool), try to flash the custom ROM from the internal storage of the phone via TWRP. That still does not work. I have also tried this with Project Elixir. No success.
I don't know what to do guys. I have followed the instructions provided, but I don't understand why the phone is not accepting other custom recoveries or allowing me to flash a custom ROM.
All help is very much appreciate.

You have to make sure that you are on OOS11 on BOTH slots.
What i would do now:
Use MSM Tool to go to 11.0.4.4.
Boot the phone and flash 11.0.11.11 via local upgrade TWICE (to ensure its on both slots)
Follow the instructions of CRDROID etc.
Edit: Dont use TWRP on Android12 now.
Read this carefully before you do anything: https://forum.xda-developers.com/t/...ro-8t-9r-with-oxygenos-12-coloros-12.4426167/

josephxdaForum said:
Hi there,
I am using a OnePlus 8 Pro on Oxygen OS 11, Global variant. I have been working on this for at least 10 hours now. I bought the OnePlus 8 Pro orginally running Oxygen OS 12, and when I flashed the recovery (TWRP) for the first time to two slots via this explanation
, I bricked the phone so the only tool accessible to me was fastboot.
Hmm okay, I'll just use MSM tool (https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/) to revert back to oxygen OS so I can continue my mission.
I am trying to install the latest CRDROID from their official website after follow their instructions on here. I get as far as being in fastboot mode with the OEM unlocked, and then I try to flash the recovery they provided. It doesn't work. When I select boot into recovery, I get sent back to fastboot, however, when I flashed the original recovery img for Oxygen OS 11 I took from the payload dumper, it loads fine.
OKAY so now I am thinking that perhaps there is a problem with the recovery provided. That is fine so I choose to use TWRP to flash the custom ROM. Thankfully, it does work, and I am able to load into it through recovery, however when I tried to flash the rom through ABD sideload, from the PC whilst in TWRP, it doesn't load! It gets halfway and stops. I tried this several times to no avail.
I choose to then (after having bricked the phone several times by now and having to revert to factory settings with MSM tool), try to flash the custom ROM from the internal storage of the phone via TWRP. That still does not work. I have also tried this with Project Elixir. No success.
I don't know what to do guys. I have followed the instructions provided, but I don't understand why the phone is not accepting other custom recoveries or allowing me to flash a custom ROM.
All help is very much appreciate.
Click to expand...
Click to collapse
And just do payload dump and flash .img in fastboot ROM installer