Database Users

Flashed TWRP as boot.img / Now it only goes to recovery HELP ME!!!

Hi people...
Everything was going so smoothly... bootloader unlock... root... some nice root apps... free paid games... and my p8 lite was just feeling so good... until... I flashed twrp with flashify under the name of boot.img... Am I stupid or what?! Now I can only get 2 scenarios... when i turn on the phone it goes directly to twrp. In twrp i get the option to go the bootloader screen... If I choose system it goes back to twrp... I can't get it to start. I downloaded the official tar.gz from emui site but I dont know how can I install it. PLEASE HELP... What should I do in this case?! I miss my baby...
Thanks in advance

You have to restore stock recovery in fastboot mode.

arviit said:
You have to restore stock recovery in fastboot mode.
Click to expand...
Click to collapse
How do I do that?! If I wanted to wipe my phone completely and re-install the OS would be better to do it using twrp or stock recovery?
Thank you very much

Sorry, i misunderstood. If you flashed twrp as boot.img, reflash stock boot in fastboot mode.

flash stock boot.img in fastboot mode
and then flash twrp as recovery
will be like this
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery TWRP.img
fastboot reboot
use the boot.img from stock rom and twrp image you downloaded

Oh no!
Now I made some serious **** to my baby... guess now i'll have to send it to huawei to fix it. I made a full wipe like if it was format c: in computers... everything is gone (i didnt had any personal data) it doesnt have OS even. But when I still had twrp i tried to flash boot.img and recovery.img and now when i start it goes directly to bootloader screen but saying "please update system again" and where it used to say phone unlocked it now says (in red letters):
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
I was able to get to eRecovery with usb connected but when i choose to download e install the new version it gives me the message "wifi starting failed".
It also does not get any instuction with fastboot. but hi suite starts when I connect it. Strange?!
What do you think? Should I send it to huawei? Or is it possible for me to make it work again?
Also tried UPDATE.APP function and all give me fail message.
I'm going crazy!!!! But I love to mess around with android... To me this is the android essence. Fortunately I have a lumia for when my baby doesnt work.loooool
Thank you all

I don't understand why you don't use fastboot. Everybody told you to use it. In our phone situation, without custom kernel or rom, twrp is for experimentation and you cannot mix things.

arviit said:
I don't understand why you don't use fastboot. Everybody told you to use it. In our phone situation, without custom kernel or rom, twrp is for experimentation and you cannot mix things.
Click to expand...
Click to collapse
Well, you warned me... but sometimes i do these kind of *****... So, in this situation you think it's better to send it or is there way to fix this.
By the way, when I enter huawei eRecovery and I get the option to download the firmware through wifi and it says wifi starting failed, is there any way to make this work? And to fastboot do we need to open cmd as administrator to make it work? Because if Hi suite detects the phone I should also be able to fastboot it right?
Thanks for your patience

Just use fastboot aand flash everything
Recovery
Boot
Systme
Cust

jabonloco said:
flash stock boot.img in fastboot mode
and then flash twrp as recovery
will be like this
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery TWRP.img
fastboot reboot
use the boot.img from stock rom and twrp image you downloaded
Click to expand...
Click to collapse
hello I have p8 lite unlocked and rooted, yesterday I wanted to install the TWRP 2.8.7. but I was wrong and I installed twrp for the p8 and not p8 lite.
When I go into recovery mode my phone locks that read huawey, I tried with fastboot command to delete the wrong recovery and install the right of the p8 lite but the result does not change, my phone locks that read huawey
i think The commands that you wrote and that I have quoted are also fine for my case, it's' true?
i have version firmware b133 which boot.img from stock rom?

Try to reflash stock boot.img too.

arviit said:
Try to reflash stock boot.img too.
Click to expand...
Click to collapse
but Ido the extraction of the boot.img from the update version b133?

Hi everyone!!
First of all, thanks to everybody who helped me with this situation.
I now am using my baby again as if it was new. I wiped him completely as i stated before and it was as easy as finding the right firmware (136a) and using the vol down + vol up + power button technique. I put the UPDATE.APP file inside a folder named dload in sdcard using other phone (with my p8 was impossible). After that rebooted the device, pressed those 3 buttons and the instalation started successfully.
I just cant explain how happy i was. I stayed 3 days without it.
After that I have been messing with fastboot so thanks to everyone who made me realize that i didnt need to do all of this, but well, A full wipe is always welcome.
Is there any custom kernel on the way for overclock my baby?

Please explain to me how do I put SOLVED in this thread as my problem is already solved...
Thanks

siul_lasc said:
Hi everyone!!
First of all, thanks to everybody who helped me with this situation.
I now am using my baby again as if it was new. I wiped him completely as i stated before and it was as easy as finding the right firmware (136a) and using the vol down + vol up + power button technique. I put the UPDATE.APP file inside a folder named dload in sdcard using other phone (with my p8 was impossible). After that rebooted the device, pressed those 3 buttons and the instalation started successfully.
I just cant explain how happy i was. I stayed 3 days without it.
After that I have been messing with fastboot so thanks to everyone who made me realize that i didnt need to do all of this, but well, A full wipe is always welcome.
Is there any custom kernel on the way for overclock my baby?
Click to expand...
Click to collapse
I also have same problem. Now i am going to try this. thank you very much.
---------- Post added at 02:22 PM ---------- Previous post was at 01:53 PM ----------
siul_lasc said:
Hi everyone!!
First of all, thanks to everybody who helped me with this situation.
I now am using my baby again as if it was new. I wiped him completely as i stated before and it was as easy as finding the right firmware (136a) and using the vol down + vol up + power button technique. I put the UPDATE.APP file inside a folder named dload in sdcard using other phone (with my p8 was impossible). After that rebooted the device, pressed those 3 buttons and the instalation started successfully.
I just cant explain how happy i was. I stayed 3 days without it.
After that I have been messing with fastboot so thanks to everyone who made me realize that i didnt need to do all of this, but well, A full wipe is always welcome.
Is there any custom kernel on the way for overclock my baby?
Click to expand...
Click to collapse
Yeah finally my phone is working now thanks to you I searched many treads and forums but i cant find a solution. But finally i got an easy solution Thank you again bro.. Good Luck !!!:good::good::good::good::good::good::good:

Just download your firmware version, use huawei extractor to extract boot.img,cust.img,recovery.img and system.img
After that,download mininal adb fastboot copy you files into fastboot folder , enter fastboot mode on your phone and from fastboot folder,open cmd and type these commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
After this your phone will boot normally. Once you've done this, copy update.app to your sdcard or internal and install it by local update. Once you've done all this,your phone is fine.

May I know how do you wipe your internal storage? and what if after wiping, im unable to get into recovery mode? does it mean phone is not usable anymore?

SOLUTION
Hello. I'm the bigest mess on androids but i know that flashing stock recovery can remove any TWRP/CWR. If its too powerfull flash stock boot and run fastboot -w.(fastboot -w erases all PERSONAL data)

Guys Help me in this
guys help me
http://forum.xda-developers.com/honor-7/help/stock-emui-recovery-image-lost-twrp-t3442021

thank you !!
VladHD said:
Just download your firmware version, use huawei extractor to extract boot.img,cust.img,recovery.img and system.img
After that,download mininal adb fastboot copy you files into fastboot folder , enter fastboot mode on your phone and from fastboot folder,open cmd and type these commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
After this your phone will boot normally. Once you've done this, copy update.app to your sdcard or internal and install it by local update. Once you've done all this,your phone is fine.
Click to expand...
Click to collapse
After days of searching the internet i couldnt find any working solution. then i tried the local update without flashing al those .img's. ( didnt work )
Now after flashing al those .img's my phone works again but its a whole different phone. Only problem is when i try to update him with the update.app file it won't go any further then 5%.
If you know why this happens let me know
Further i wanna thank you one last time .. thank you

fastboot flashable boot.img

Hi !
I might have erased the boot partion. I still got the unlocked bootloader screen, and can still get in fastboot, but that's it. I can't boot in TWRP. I've tried to flash the boot.img from the stock zip, but it doesn't work... anyway to fix this ? It's the A2017G model. All i need is to get into TWRP.

Exnocte said:
Hi !
I might have erased the boot partion. I still got the unlocked bootloader screen, and can still get in fastboot, but that's it. I can't boot in TWRP. I've tried to flash the boot.img from the stock zip, but it doesn't work... anyway to fix this ? It's the A2017G model. All i need is to get into TWRP.
Click to expand...
Click to collapse
can't you flash recovery? I think someone made a flashable TWRP somewhere

Choose an username... said:
can't you flash recovery? I think someone made a flashable TWRP somewhere
Click to expand...
Click to collapse
I've tried to flash TWRP several time, but it won't boot...

Exnocte said:
I've tried to flash TWRP several time, but it won't boot...
Click to expand...
Click to collapse
you can try getting into EDL and using MiFlash to flash one of the zips on the Russian page 4pda. Go to the debrick page (the one with the phone carnage pictures inside), find the links for the chinese full recovery package. it will get you to the 4pda page. from there find a package that suits your needs (there is one with aboot and fbop) and flaah with MiFlash
Otherwise download the full B10 recovery package and flash it with MiFlash. you won't lose data but it might conflict if you were on Nougat

I'm in this situation for some days...
No EDL, No recovery, only fastboot and FTU modes are accessible.
And we can't flash via Miflash. It sees the phone only in fastboot mode, and can't flash it.
 @op : 2 ways to recover :
- Test points method to force EDL and flash via miflash
- Return to ZTE
If any1 has other solutions ...
FYI : My tests so far :
- Flash boot / reboot / flash recovery : Stuck on ZTE logo, red led on permanently
- Hot load recovery (fastboot boot twrp.img): Command unknown
- Format userdata/cache : No work
- Flash via Miflash in fastboot : "Can't find Eraseall except Data.bat"
- Change drivers by some others one : No luck

Sn8K said:
I'm in this situation for some days...
No EDL, No recovery, only fastboot and FTU modes are accessible.
And we can't flash via Miflash. It sees the phone only in fastboot mode, and can't flash it.
@op : 2 ways to recover :
- Test points method to force EDL and flash via miflash
- Return to ZTE
If any1 has other solutions ...
FYI : My tests so far :
- Flash boot / reboot / flash recovery : Stuck on ZTE logo, red led on permanently
- Hot load recovery (fastboot boot twrp.img): Command unknown
- Format userdata/cache : No work
- Flash via Miflash in fastboot : "Can't find Eraseall except Data.bat"
- Change drivers by some others one : No luck
Click to expand...
Click to collapse
I don't know what you mean with FTU mode, but if FTM is meant you should be able to send a "reboot edl" command to activate the EDL mode.

tron1 said:
I don't know what you mean with FTU mode, but if FTM is meant you should be able to send a "reboot edl" command to activate the EDL mode.
Click to expand...
Click to collapse
Humm ... Early morning for me ... i meant DFU. Vol+ & - while powering the phone Result on a black screen, and driver is recognized as Handset Diagnostic Driver (DFU COm port x)
Ind in that kind of brick, FTM is not accessible either.

tron1 said:
I don't know what you mean with FTU mode, but if FTM is meant you should be able to send a "reboot edl" command to activate the EDL mode.
Click to expand...
Click to collapse
Yeah that pretty much sums it up. If you get ZTE handset diagnostic driver on Ports COM&LPT you'll have to take your device apart and use the test point. If it is recognized as Qualcomm HS-USB QDLoader 9008 it means that you're on EDL. I'd reccomend trying to use miflash like i described, if it doesn't work return it or take it apart

Maybe a bit late for a reply, but I was able to get out of a similar situation (from DFU) by holding power and volume down for a long time. That got me to FTM and then I could reboot into edl via "adb reboot edl". Then I used the Axon7toolkit to flash fastboot and from there I could get to twrp and back in business. Any questions, let me know.

@Piet : How long for the PWR+DWN ? I've tried for something like 40/45 seconds, without success.

Sn8K said:
@Piet : How long for the PWR+DWN ? I've tried for something like 40/45 seconds, without success.
Click to expand...
Click to collapse
From what I read you have to let the device discharge totally, then you can get ftm. I had my battery fully charged when i bricked so i just did the 4th categ unbricking process

X720 bricked, kind of ;)

Hi. Looks like I fkced my phone. Was using Darkobas twrp, flashed this room and it boot-looped at the beginning (phone was turning on and off on the "Coolpad" screen). I can enter the recovery however can't transfer roms into the card. While pushing big files with ADB push (it takes few minutes) it randomly stops responding/hangs in the middle of a transfer. Tried multiple times and it stops randomly ( I've wiped/formatted whole storage )
I managed to flash another recovery 3.1.0.0 but still I need to push some rom to see if I can flash it. After PC reboot it stopped detecting my phone...
Fastboot is not working, power + vol down goes to black screen / turning off the phone.
Tool_all_in_one does not detect my phone. In fact I do not see it in Windows Device Manager. Tried different usb 3/2 ports
Commands in console like fastboot oem device info gives:
< waiting for any device >
adb reboot bootloader gives:
adb server version (39) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
It's done guys?

Update: somehow managed to restore connection, so phone is visible in Device Manager as "Android Composite ADB Interface" .
Managed to push AICP ROM with adb but can't see it on sdcard. Usually, it was in the main directory, now nothing is there.

Adb sideload? It still seems to me like youre having connection issues w/the pc. Tried rebooting to fastboot from twrp menu?

1 - Enter Twrp Recovery
2 - Wipe -> Format Data then type "yes". This command gonna wipe your internal storage behold.
3 - After this reboot recovery and go to mount then enable mtp.
4 - Transfer rom file.And after a clean wipe flash it.
That rom have bootloader and some modem file that can bring up some issue mate.And those files belongs to Changer not to our beast.
Both device very very familiar but its different product anyway you can't trust it.
I RECOMMEND ALL OF PEOPLE GONNA FLASH ROM please first check the firmware files .If there, then clean it and wipe from the updater-script.
For an alternative you can flash your stock firmware files from QFİL but it's risky too.

Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries, I managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?

Thes1ev said:
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Click to expand...
Click to collapse
Make sure you are not using a USB hub, or extension cable. Also make sure you are plugged directly into the PC motherboard, not one of the front ports. I had transfers stalling and it was my USB extension cable.

Thes1ev said:
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries, I managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Click to expand...
Click to collapse
Sure, you need to flash the firmware files, download 23s from the official site, and fastboot flash all the files, that'll return you to stock fastboot, splash, etc.
Follow this guide (no need to format data, and flash system again, just the files in firmware update folder).
https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-manually-upgrade-firmware-t3609786

trizex said:
Sure, you need to flash the firmware files, download 23s from the official site, and fastboot flash all the files, that'll return you to stock fastboot, splash, etc.
Follow this guide (no need to format data, and flash system again, just the files in firmware update folder).
https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-manually-upgrade-firmware-t3609786
Click to expand...
Click to collapse
Can't flash anything using fastboot - "fastboot flash xxx.img" gives me: < waiting for any device > and nothing happens.
At the moment trying to flash stock 23s but it's hanging on "Patching system image unconditionally" for 5+ minutes already.
This JUI fcked bootloader in my phone somehow. It's blocked/can't be replaced or no idea what's going on here.
Edit: so ye after 20+ minutes of "Patching system image unconditionally" looks like I'm unable to flash stock 23s using TWRP 3.1.0.0.
Probably it wants to replace this fkn JUI bootloader and freeze there.

Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda

trizex said:
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
Click to expand...
Click to collapse
Yap, was flashing official stock 23s from this site via twrp.
Okay today gonna try Alba ROM as you suggested.

trizex said:
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
Click to expand...
Click to collapse
That helped, thanks a lot!

Is there any solution to restore Leeco bootloader? I just cant flash anything because device is unknown during fastboot mode. Tried to uninstall and reinstall driver but no luck.
I am stuck with coolpad bootloader which is not recognised from my pc. Serves me right because i didnt check the zip of jui which i flashed that had another bootloader, fml.
If any kind soul has any info on that please say it, thanks.

testreaper said:
Is there any solution to restore Leeco bootloader? I just cant flash anything because device is unknown during fastboot mode. Tried to uninstall and reinstall driver but no luck.
I am stuck with coolpad bootloader which is not recognised from my pc. Serves me right because i didnt check the zip of jui which i flashed that had another bootloader, fml.
If any kind soul has any info on that please say it, thanks.
Click to expand...
Click to collapse
That is litterally what this whole topic was about? See my responses, if you still have access to twrp (dont see why wouldnt you), you can use it to flash a 23s "stock" rom through it (such a package will contain, among others, the leeco bootloader etc)
---------- Post added at 08:00 PM ---------- Previous post was at 07:59 PM ----------
Thes1ev said:
That helped, thanks a lot!
Click to expand...
Click to collapse
Youre welcome, everything back to normal?

trizex said:
Youre welcome, everything back to normal?
Click to expand...
Click to collapse
Yeah, I got rid of this JUBU bootloader after flashing stock-like rom. Also thanks to this there is no more strange noise during the boot sequence.

Thes1ev said:
Yeah, I got rid of this JUBU bootloader after flashing stock-like rom. Also thanks to this there is no more strange noise during the boot sequence.
Click to expand...
Click to collapse
Ya, I heard that squeeling too, when booting, and in fastboot mode

Thes1ev thank you so much pal, i flashed 2 different 23s with all wipes and they gave me errors but your rom installed perfectly.

QFIL to Leeco le pro 3 (Lex722)

Hello everyone!
my problem is the next: I tried install a rom of MIUI but fail in my device, after, I tried to install differents roms but nothing work, just showed me the logo Leeco and no more, no avance from the logo.
But I still had recovery with TWRP and I thinked I can install official rom 26s, It was my error.
Now follow with the same problem but now I not have recovery mode (show me recovery with logo Leeco but it instantly turns off ) and bootloader is block.
My only hope, is QFIL to recover recovery mode o any rom, Does anyone have it or tell me how to create one?..
Please anybody will can help me, I have this problem 3 days ago.
Sorry for my bad english, I am learning.
PS. I tried with post of tora33 but no work
FlashOne2.0\le_zl1_qfil_ufs\prog_ufs_firehose_8996_ddr.elf"
22:00:34: ERROR: function: rx_data:247 Error occurred while reading from COM port
22:00:34: ERROR: function: sahara_main:854 Sahara protocol error
22:00:34: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse

Are you sure you got Qualcomm drivers installed and your phone is in 9008 mode? Also try rebooting and re-enter 9008 mode. But the biggest problem that there is no qfil restoration files for x722 if I remember correctly, chances to boot with x720 ones are quite low.

Does your fastboot work volume and power down same time??
Sent from my LEX727 using xda premium
---------- Post added at 11:09 AM ---------- Previous post was at 10:53 AM ----------
worked on the phone i got off amazon. thanks!
[quote name="wpbear" post=71566961]This works on lastest USA update Stock (21s).
Have ADB/Fasboot tools on your computer
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device
Put emmc_appsboot.mbn from this zip (Download: x727-5.8.019s_bootloader-unlock.zip) in your adb directory on your PC
Put twrp.img from this zip (Download: TWRP) in your adb directory on your PC
On PC open admin CMD prompt
go into fastboot mode on phone (hold power and VOL -)
on PC type:
fastboot devices
fastboot flash aboot emmc_appsboot.mbn
after flash force reboot using Power button. It will ask for a password, just ignore it and reboot back to fastboot by forcing power down then reboot to fastboot (hold power and VOL -)
on PC type:
fastboot devices
fastboot oem unlock-go
fastboot flash recovery twrp.img
boot into twrp (force power down, then hold POWER and VOL +)
TWRP will boot, choose modify system. Choose wipe - then swipe to factory reset, when that is done - then advacned then format data
In TWRP ensure MTP is enabled. In Windows File Explorer the phone should be visibile. Drag and Drop your new ROM.zip, gapps.zip, SU.zip etc...
In TWRP INSTALL new ROM and other zips; choose wipe/dalvik/cache
If you unlock bootloader push power off until it goes off then put it back into fastboot flash twrp .img them power off again power on when phone vibrate volume down you see stock recovery then twrp.
Reboot System.
DONE![/QUOTE]
Sent from my LEX727 using xda premium

voron00 said:
Are you sure you got Qualcomm drivers installed and your phone is in 9008 mode? Also try rebooting and re-enter 9008 mode. But the biggest problem that there is no qfil restoration files for x722 if I remember correctly, chances to boot with x720 ones are quite low.
Click to expand...
Click to collapse
Yeah, that is the problem, I have the drivers and my computer recognize it, the problem, always show the error sahara.
And flash in fastboot no work because bootloader is block and not let me to do flash of anything.
Someone know how to create a qfil? I am developer and I could try but I not found tutorial how to do and I do not have it clear.

zeckAlexs said:
Yeah, that is the problem, I have the drivers and my computer recognize it, the problem, always show the error sahara.
And flash in fastboot no work because bootloader is block and not let me to do flash of anything.
Someone know how to create a qfil? I am developer and I could try but I not found tutorial how to do and I do not have it clear.
Click to expand...
Click to collapse
Every so often the same questions and the same answers.
You should read more. The X722 subforum is for something.
There is no qfil for X722, and there are no magic solutions of X720 / X727. This is an X722, it is locked and NOTHING of X720 / X727 is going to fix it.
Read this:
https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Greetings.

How do people keep ending up with bricks? Guess I'll have to find a mod to contact them about stickying a thread about the x722 here about stock 26s. It's a bad idea. Never update your x722 to stock 26s, because your bootloader will get locked when you try to flash TWRP. The only way to get out of 26s is to flash Batyan's 01D ROM (in the x722 Development section here), and then unlock your bootloader and flash TWRP. Flashing TWRP over stock 26s will cause a permanent brick because there's absolutely no QFIL file available for this device. Even in China.

sk8223 said:
How do people keep ending up with bricks? Guess I'll have to find a mod to contact them about stickying a thread about the x722 here about stock 26s. It's a bad idea. Never update your x722 to stock 26s, because your bootloader will get locked. The only way to get out of 26s is to flash Batyan's 01D ROM (in the x722 Development section here), and then unlock your bootloader and flash TWRP. Flashing TWRP over stock 26s will cause a permanent brick because there's absolutely no QFIL file available for this device. Even in China.
Click to expand...
Click to collapse
You know I don't really know how they keep doing it but I seen a lot new ones getting this phone and not really studying how to do this stuff and their not paying attention to what model this have this a solid phone.
Sent from my LEX720 using xda premium

This is true ?
https://dc5.androidfilehost.com/dl/...40/818070582850488404/le_zl1_qfil_ufs_fix.zip

paiktaras said:
This is true ?
https://dc5.androidfilehost.com/dl/...40/818070582850488404/le_zl1_qfil_ufs_fix.zip
Click to expand...
Click to collapse
ZL1 its x720/x727 not x722, it's a fix for ppl thata not work the normal qfil rom.

[OP6T] fastboot erase persist

Hello ALL!
I normally don't message much because usually I can find most of my problems can be fixed by searching threads online. However, this particular case for me has been exhausting because through trial and error I have been unsuccessful in getting my 6T to boot into any rom normally.
I went from a stock T-Mobile to International version to LOS. The reason I did what I did was because I could get a IMEI or SIM to register on LOS. That worked fine on OOS 9.0.11. but as soon a I flash the latest LOS, no sim, bootloader, or IMEI detection.
I was rooted and unlocked. Now I am neither.
While on LOS, someone on another forum suggested to erase the persist partition and reflash to get the sim imei back so the phone would get service, when the phone rebooted it still didn't work and then the second time it rebooted it always gets stuck on the boot screen and never boots into the OS.
I tried to repair and reflash but was unsuccessful.
Since doing all of that, Ive reflashed using msm tool and although that was successful for OOS 9.0.11 and T-Mobile stock rom. It gets stuck on the boot screens for both.
I flashed LOS on A & B so I don't have a stock recovery.
I can't ADB anymore. I can only seem to connect via FASTBOOT but cannot seem to flash anything because the BOOTLOADER is now LOCKED.
How can I get this phone back to its original state? What ever the persist partition is. Removing it had made the phone non-bootable.
What can I do to fix? I greatly appreciate any help to get the phone operational again.
Thank you all!

https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
- Go to the thread linked above and download the latest OOS (.13) stable.
- Download latest Magisk.
- Have the latest TWRP .img downloaded and on-hand, you will use a few times as well as the installer .zip.
- Be sure to have adb/fastboot installed.
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
- Put your phone into fastboot mode (reboot to bootloader).
- Go to the folder you downloaded in the first step and run the "flash all.bat".
- Ignore errors. If it's get stuck for more than 45 seconds, just hit enter to keep it going.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP.
- In TWRP, go to Reboot and changed the boot partition to the one NOT CURRENTLY enabled. In other words, switch boot partitions.
- Reboot bootloader.
- Go to the folder you downloaded in the first step and run the "flash all.bat" again.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP again.
- Move Magisk installer and TWRP installer from steps two and three onto the internal memory of your device.
- Flash TWRP, reboot recovery to make sure it sticks.
- Flash Magisk for root.
- Wipe dalvik and reboot system.
You will have the latest stable OOS on both partitions at this point! I literally just did this yesterday. Good luck!

..Cory.. said:
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
- Go to the thread linked above and download the latest OOS (.13) stable.
- Download latest Magisk.
- Have the latest TWRP .img downloaded and on-hand, you will use a few times as well as the installer .zip.
- Be sure to have adb/fastboot installed.
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
- Put your phone into fastboot mode (reboot to bootloader).
- Go to the folder you downloaded in the first step and run the "flash all.bat".
- Ignore errors. If it's get stuck for more than 45 seconds, just hit enter to keep it going.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP.
- In TWRP, go to Reboot and changed the boot partition to the one NOT CURRENTLY enabled. In other words, switch boot partitions.
- Reboot bootloader.
- Go to the folder you downloaded in the first step and run the "flash all.bat" again.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP again.
- Move Magisk installer and TWRP installer from steps two and three onto the internal memory of your device.
- Flash TWRP, reboot recovery to make sure it sticks.
- Flash Magisk for root.
- Wipe dalvik and reboot system.
You will have the latest stable OOS on both partitions at this point! I literally just did this yesterday. Good luck!
Click to expand...
Click to collapse
Thank you but how can I flash if my bootloader is locked? Everything I try fails.

I guess the real question is: How can I get the phone to turn on OEM UNLOCK so I can fastboot unlock the Bootloader if it wont boot up the OS?

Is there a way to fix it via the msmdownload tool? Custom file maybe? I've tried the files 9.0.11 & 12 OOS files and all I get is the boot screen white ball logo circling the red ball - stuck in loop and same with stock t-mobile rom.

My friend, sounds like you need to restore your EFS partitions
... I'm trying to figure out how the hell you successfully flashed MSM tool in EDL mode and not have ALL your partitions restored. That tool is supposed to literally write the phone as it came out of the box. Also I think there are different MSM tools for each device respectively, you did use the T-Mobile one right?

Causical said:
My friend, sounds like you need to restore your EFS partitions
... I'm trying to figure out how the hell you successfully flashed MSM tool in EDL mode and not have ALL your partitions restored. That tool is supposed to literally write the phone as it came out of the box. Also I think there are different MSM tools for each device respectively, you did use the T-Mobile one right?
Click to expand...
Click to collapse
My thoughts exactly. So, when it was on LOS I erased the persist partition and that really messed things up. So yes, how can I restore the partition back with a locked bootloader? Every time I've used MSM tool it fixes everything. This time no such luck. I flashed 9.0.11 & 12 and then I did the T-Mobile version. All only boot to the boot screen and hang. In doing so, I wasn't thinking if that failed and it locks the bootloader, then what? I saw an old video somewhere on a oneplus 2 or 3 where the person used the msm tool 3.0 and fixed a bricked locked bootloader phone. Similar to the fastboot method of reformatting. In the msm tool folder he had all the image files for all the partitions not sure if that the same thing as msm tool 4.0 with just one ops image file?
Anyway, is there a way to unlock the bootloader without booting into the OS? Or a way to restore the partitions via msm tool?

defcondoc said:
My thoughts exactly. So, when it was on LOS I erased the persist partition and that really messed things up. So yes, how can I restore the partition back with a locked bootloader? Every time I've used MSM tool it fixes everything. This time no such luck. I flashed 9.0.11 & 12 and then I did the T-Mobile version. All only boot to the boot screen and hang. In doing so, I wasn't thinking if that failed and it locks the bootloader, then what? I saw an old video somewhere on a oneplus 2 or 3 where the person used the msm tool 3.0 and fixed a bricked locked bootloader phone. Similar to the fastboot method of reformatting. In the msm tool folder he had all the image files for all the partitions not sure if that the same thing as msm tool 4.0 with just one ops image file?
Anyway, is there a way to unlock the bootloader without booting into the OS? Or a way to restore the partitions via msm tool?
Click to expand...
Click to collapse
Try this and tell me if it works.

Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.

_Masked_ said:
Try this and tell me if it works.
Click to expand...
Click to collapse
Yes, I did try that. That is what I just flashed with the msm tool. Gets stuck on the OOS boot animation.

Causical said:
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
Click to expand...
Click to collapse
Looks like the MSM tool. I'm going to give 9.0.13 a try but I'm thinking I may have the same problem.

Causical said:
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
Click to expand...
Click to collapse
Tried 9.0.13. Still gets stuck on OOS boot animation screen. There's got to be something to flash to fix this.

So you're booting EDL mode then flashing the MSM tool that exactly matches the way your phone came stock? At this point I would discontinue trying to convert it to international or upgrade the OS to a more recent version or any of that. I would focus on strictly flashing it to exactly the way you bought it.

Causical said:
So you're booting EDL mode then flashing the MSM tool that exactly matches the way your phone came stock? At this point I would discontinue trying to convert it to international or upgrade the OS to a more recent version or any of that. I would focus on strictly flashing it to exactly the way you bought it.
Click to expand...
Click to collapse
Yes. I did flash the stock T-Mobile ROM via the MSM tool. Freezes at the pink T-Mobile boot screen. Pretty sure the partitions need to be fixed but I thought the MSM tool would do that? I guess not. Is there a more advanced MSM tool where I can see what's being partitioned or is the MSM tool not doing any partitioning and that's why the phone is having the boot problem?

defcondoc said:
Yes. I did flash the stock T-Mobile ROM via the MSM tool. Freezes at the pink T-Mobile boot screen. Pretty sure the partitions need to be fixed but I thought the MSM tool would do that? I guess not. Is there a more advanced MSM tool where I can see what's being partitioned or is the MSM tool not doing any partitioning and that's why the phone is having the boot problem?
Click to expand...
Click to collapse
I know this is a stupid question but have you tried a factory reset in recovery mode? I know its a stupid question but I did not see it asked or noted.

Scott said:
I know this is a stupid question but have you tried a factory reset in recovery mode? I know its a stupid question but I did not see it asked or noted.
Click to expand...
Click to collapse
No stupid questions and I don't mind repeating answers to questions. I have tried that, but it does nothing. I get wipe cache or reboot to fastboot or reboot to recovery. When I choose system wipe, it takes 1 second to finish. It reboots and it gets stuck on the boot screen. Ever since persist partition was deleted it just freezes on startup and now that the bootloader is locked I cant seem to get anything to work. MSM tool I thought was supposed to fix this sort of thing but it has failed. Someone must know a way to get back into the OS so I can turn on OEM Unlock.

How do you know your bootloader is locked?

Causical said:
How do you know your bootloader is locked?
Click to expand...
Click to collapse
Fastboot says bootloader is locked. Shows it on the fastboot screen. Wont let me transfer any files from pc to phone. I can start the transfer process but it fails.

defcondoc said:
Fastboot says bootloader is locked. Shows it on the fastboot screen. Wont let me transfer any files from pc to phone. I can start the transfer process but it fails.
Click to expand...
Click to collapse
So you're able to enter EDL mode with a locked bootloader? How do you know your computer is seeing your device in EDL mode?
I'm going to place this here for myself for now. I'm just trying to understand your situation a little better, but this is just for later.... maybe, depending on your answer. https://forum.xda-developers.com/an...how-to-reboot-to-edl-fastboot-t3394292/page12
ALSO; If you don't mind can you link the thread that contains the original discussion where your problem began?

Causical said:
So you're able to enter EDL mode with a locked bootloader? How do you know your computer is seeing your device in EDL mode?
I'm going to place this here for myself for now. I'm just trying to understand your situation a little better, but this is just for later.... maybe, depending on your answer. https://forum.xda-developers.com/an...how-to-reboot-to-edl-fastboot-t3394292/page12
ALSO; If you don't mind can you link the thread that contains the original discussion where your problem began?
Click to expand...
Click to collapse
The point of EDL is to get around any restrictions or issues with the device, so yes, you can boot to EDL while locked. Your link will not help much because he can already get to EDL. Not to mention he will have no ADB access. Whatever he does, he has to fix it in EDL.
OP: Are you up and running yet? I am willing to try copying out my partition and sending to you.
Let me know...
---------- Post added at 08:12 PM ---------- Previous post was at 08:08 PM ----------
Wait, I just realized that my persist.img would not work because he has no way to flash it.
Nevermind.