Database Users

I can' get it to boot properly. Help me please!

A friend of mine gave me this phone after unexpected self shutdown. The phone was in a boot loop. At this point where I am right now I think I tried everything I can. I have read various guides and tutorials how to bring this phone back to life and nothing works for me. I suppose that there is some damage on mainboard but till I losse this phone I want to be sure. So the situation looks like this. Since the bootloader in locked and there is no working OS I am not able to unlock the bootloader. (If I am wrong here tell me please because I can't find a solution "how to unlock bootloader without having working OS"). The only metode to flash this phone in this state is to use QFIL. Flashing through fastboot fails everytime - booloader locked -> no *.img flashing. So I have 4 various versions of stock ROM for this phone and after flashing via QFIL the phone doesn't boot. It end with 3 possible ways. 1'st way - clasic bootloop. 2'nd way - frozen on loading screen. 3'rd way - black screen with blue LED, USB diagnostics state, 9006 port opened, no chance to flash because of closed QD port 9008. After this I have to erase every single one of the partitions made through flashing. Then I am able again to flash with QFIL.
I have no idea where is the problem here or what am I doing wrong. I tested the internal memory with a partitioning program in search of bad sectors -> 100% OK. Filled the whole memory with zero's and then formated it. It didn't help. Are every of my stock ROMs broken or is this phone realy damaged? Dear XDA community help me please! I have no clue what can I still try.

Tried ZUI QPST image or CM one?

ankurpandeyvns said:
Tried ZUI QPST image or CM one?
Click to expand...
Click to collapse
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?

kotex said:
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?
Click to expand...
Click to collapse
I just recommend you downloading this https://drive.google.com/open?id=0B7zm16vLHfdBVi1lWlMwelBBdXc . It's ZUI 2.0.49 for qfil, hope it works for you.

kotex said:
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?
Click to expand...
Click to collapse
Download the CM QFIL image from my video. It should work.

ankurpandeyvns said:
Download the CM QFIL image from my video. It should work.
Click to expand...
Click to collapse
Already tried your copy. To be honest tried it many times in every way I could. The phone is now sitting for over 3h frozen on loading screen. It is never going to boot or tell me that this is normal... Ereased the whole internal memory by delting every existing partition and then flashed it via QFIL. Also tried to format the whole memory in ext4. Same result. Like I said the phone is laying right now for over 3h on the same CYANOGEN screen with some graphical artifacts.
Borja Viera said:
I just recommend you downloading this https://drive.google.com/open?id=0B7zm16vLHfdBVi1lWlMwelBBdXc . It's ZUI 2.0.49 for qfil, hope it works for you.
Click to expand...
Click to collapse
OMG This room booted normaly. Thank you some much my friend! You made my day. It is a step forward. However all connections aren't working. I can't find "OEM unlocking" under Developer Options. I want to unlock the Bootloader as soon as possible so I will be able to put TWRP recovery and then flash it with any available CustomROM

kotex said:
Already tried your copy. To be honest tried it many times in every way I could. The phone is now sitting for over 3h frozen on loading screen. It is never going to boot or tell me that this is normal... Ereased the whole internal memory by delting every existing partition and then flashed it via QFIL. Also tried to format the whole memory in ext4. Same result. Like I said the phone is laying right now for over 3h on the same CYANOGEN screen with some graphical artifacts.
Click to expand...
Click to collapse
What's the result after flashing ZUI 2.5.330 image?

ankurpandeyvns said:
What's the result after flashing ZUI 2.5.330 image?
Click to expand...
Click to collapse
Many hours frozen on black screen with blue led. 9008 QD port blocked. 9006 USB Diagnostics port opened. No chance to flash until all partitions are erased and the port is reset. Otherwise I need to try getting to the 9008 port by puting the USB cable while holding the "Vol Up" button and then flash it agin with QFIL.

kotex said:
Many hours frozen on black screen with blue led. 9008 QD port blocked. 9006 USB Diagnostics port opened. No chance to flash until all partitions are erased and the port is reset. Otherwise I need to try getting to the 9008 port by puting the USB cable while holding the "Vol Up" button and then flash it agin with QFIL.
Click to expand...
Click to collapse
Got successful in flashing?

ankurpandeyvns said:
Got successful in flashing?
Click to expand...
Click to collapse
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?

kotex said:
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?
Click to expand...
Click to collapse
If you're still in warranty, the best bet will be to get it replaced. Because it seems like a serious issue in the hardware.

kotex said:
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?
Click to expand...
Click to collapse
Do you have any telegram account, we could make things faster if we communicate that way.

ankurpandeyvns said:
If you're still in warranty, the best bet will be to get it replaced. Because it seems like a serious issue in the hardware.
Click to expand...
Click to collapse
Asked my firend about it. The phone is like 1 month old. He was making some pictures and the phone suddenly died and got to boot loop. He bought it new on ebay. Shipped from China. He already made some research about the warranty before he gave it to me. He made some calls and emails to customer service here in Germany and they told him that he has to send the phone back to China. No warranty in Germany. It is not worth to send it back to China because of duty tax on the way to China. They send him this phone on some special shipping method to avoid this taxes and stay with profitable shipping price. But if you need to send it back they won;t help you at all. And the dispatch price is a no-go.
Since I have decent experience with electronics and flashing various smartphones he gave it to me with a though that I will be able to bring it back to life.
I already said when I started this topic that I suppose that this phone has some damage on the mainboard because of the weird behaviour. I just want to be sure about that and try everything I can before I tell him that he wasted his money by buying this phone.
I want to thank you for your support! If you have some ideas what could I still try I will gladly listen.

kotex said:
Asked my firend about it. The phone is like 1 month old. He was making some pictures and the phone suddenly died and got to boot loop. He bought it new on ebay. Shipped from China. He already made some research about the warranty before he gave it to me. He made some calls and emails to customer service here in Germany and they told him that he has to send the phone back to China. No warranty in Germany. It is not worth to send it back to China because of duty tax on the way to China. They send him this phone on some special shipping method to avoid this taxes and stay with profitable shipping price. But if you need to send it back they won;t help you at all. And the dispatch price is a no-go.
Since I have decent experience with electronics and flashing various smartphones he gave it to me with a though that I will be able to bring it back to life.
I already said when I started this topic that I suppose that this phone has some damage on the mainboard because of the weird behaviour. I just want to be sure about that and try everything I can before I tell him that he wasted his money by buying this phone.
I want to thank you for your support! If you have some ideas what could I still try I will gladly listen.
Click to expand...
Click to collapse
If you have telegram, drop a message @ankurpandeyvns

Soft Brick, A2017G, Bootloader unlocked, Stock Recovery

(or is it hard brick)
Hi,
A2017G
Started with marshmallow,
Unlocked bootloader
attempted to install Slim7
seemed to work but with some possible errors, (wouldn't sync with google... retrospect I should have looked elsewhere before...)
attempted in install stock rom
using
ZTE_A2017GV1.2.0B04_BootStack_by_tron1.zip
ZTE_A2017GV1.2.0B04_Stock_System_by_tron1.zip
which wouldn't boot
So I tried reinstall Slim7
then stock again,
then, like the noob that I am, I removed twrp with
ZTE_A2017GV1.2.0B04_Full_Stock_Reverter_by_tron1.zip
which installs stock recovery
so, now I have a stock rom that won't boot,
an unlocked bootloader
and stock recovery
Not sure what to do from here
thanks in advance for any assistance.

I can abd sideload and update from SD card, but everything I have fails signature verification.
edit: so frustrating trying to find that 1 zip

Dizzee said:
(or is it hard brick)
Hi,
A2017G
Started with marshmallow,
Unlocked bootloader
attempted to install Slim7
seemed to work but with some possible errors, (wouldn't sync with google... retrospect I should have looked elsewhere before...)
attempted in install stock rom
using
ZTE_A2017GV1.2.0B04_BootStack_by_tron1.zip
ZTE_A2017GV1.2.0B04_Stock_System_by_tron1.zip
which wouldn't boot
So I tried reinstall Slim7
then stock again,
then, like the noob that I am, I removed twrp with
ZTE_A2017GV1.2.0B04_Full_Stock_Reverter_by_tron1.zip
which installs stock recovery
so, now I have a stock rom that won't boot,
an unlocked bootloader
and stock recovery
Not sure what to do from here
thanks in advance for any assistance.
Click to expand...
Click to collapse
Just use MiFlash, that one's guaranteed to work. Read my DFU unbrick guide to know how to use it. Just skip the part where you have to disassemble the phone, since you can get to EDL mode by (with the phone off and the USB cable connected to the PC) holding both volume buttons and inserting the USB-C cable to the phone.

I did read your guide, was, hoping to avoid dismantling it...
I tried pressing all 3 buttons.
Am I understanding the procedure correctly:
[phone switched off] + usb-C cable connected to PC only
MiFlash running at this point??
Hold both volume keys in and in insert Cable to Phone
at this point is the phone supposed to switch on?
At no point am I supposed to press the power button?
fyi: I will try different combinations, is great to have a solution, thank you.
Ah.... ok... so, the phone will display nothing, rely on the sound of PC and/or the device manager check and/or hit refresh on miflash
Fyi to anyone, if you have axon7toolkit installed and thus can't install a second version of MiFlash, open up the toolkit and hit 7 (unlock bootloader) to fire up MiFlash... or just go to C:\XiaoMi\XiaoMiFlash
the FULL_EDL file I have produces a couldn't find script Error when loading into MiFlash
so far when attempting to flash all zips
I have started MiFlash with admin
unzipped FULL_EDL file to a folder in root C:\ and ensured there are no spaces in address.
Every time / Every file produces couldn't find script error when loaded into MiFlash
when I attempt to flash the file it says cannot receive hello packet and then times out with an error
Tried disabling anti-virus/firewall, still same error
upgraded MiFlash to 2017.4.24.0 ( older 2016 is included with axon7toolkit), this removes the couldn't find script error, but still not receiving a hello packet, gunna fiddle with the phone as I'm pretty sure the error is coming from there
YES!
rebooted phone, turned off, restarted into EDL, flashed the stock rom from zte site... is in chinese... but it works. Thank you Thank you
so adventure over, after all that I am back to 6.0.1...

Dizzee said:
I did read your guide, was, hoping to avoid dismantling it...
I tried pressing all 3 buttons.
Am I understanding the procedure correctly:
[phone switched off] + usb-C cable connected to PC only
MiFlash running at this point??
Hold both volume keys in and in insert Cable to Phone
at this point is the phone supposed to switch on?
At no point am I supposed to press the power button?
fyi: I will try different combinations, is great to have a solution, thank you.
Ah.... ok... so, the phone will display nothing, rely on the sound of PC and/or the device manager check and/or hit refresh on miflash
Fyi to anyone, if you have axon7toolkit installed and thus can't install a second version of MiFlash, open up the toolkit and hit 7 (unlock bootloader) to fire up MiFlash... or just go to C:\XiaoMi\XiaoMiFlash
the FULL_EDL file I have produces a couldn't find script Error when loading into MiFlash
so far when attempting to flash all zips
I have started MiFlash with admin
unzipped FULL_EDL file to a folder in root C:\ and ensured there are no spaces in address.
Every time / Every file produces couldn't find script error when loaded into MiFlash
when I attempt to flash the file it says cannot receive hello packet and then times out with an error
Tried disabling anti-virus/firewall, still same error
upgraded MiFlash to 2017.4.24.0 ( older 2016 is included with axon7toolkit), this removes the couldn't find script error, but still not receiving a hello packet, gunna fiddle with the phone as I'm pretty sure the error is coming from there
YES!
rebooted phone, turned off, restarted into EDL, flashed the stock rom from zte site... is in chinese... but it works. Thank you Thank you
so adventure over, after all that I am back to 6.0.1...
Click to expand...
Click to collapse
What? It's in chinese?
Can you tell me the name of the file you used? Do you still have cell signal?

Choose an username... said:
What? It's in chinese?
Can you tell me the name of the file you used? Do you still have cell signal?
Click to expand...
Click to collapse
I got it from here: http://www.ztedevice.com/support
selected:- United Kingdom > Mobile Phone > Axon 7
it offers a file "AXON 7(ZTE A2017G) SD card software package(328540B2634ZTE A2017GV1.0.0B11)"
which hints at being compatible with A2017G... but is A2017V and is chinese, although you can change the language in settings there is still plenty here and there, plus chinese bloatware
and No, I didn't get cell signal.
I've gone back to Marshmellow, I will try again, didn't think it would be so different/difficult... Although wow at MiFlash.

FFS!!!! Relocked bootloader and bricked it!!! there should be a warning!
you gotta laugh,
I am a bit livid, I know the guides come with disclaimers, however, you'd think it would be an obvious important warning to make... DO NOT RELOCK YOUR PHONE.
FFS!

Dizzee said:
FFS!!!! Relocked bootloader and bricked it!!! there should be a warning!
you gotta laugh,
I am a bit livid, I know the guides come with disclaimers, however, you'd think it would be an obvious important warning to make... DO NOT RELOCK YOUR PHONE.
FFS!
Click to expand...
Click to collapse
Good lord...
You probably wiped out both IMEIs, now you relock out of the blue... Go to my DFU unbrick guide and stop doing dumb stuff :silly:

Choose an username... said:
Good lord...
You probably wiped out both IMEIs, now you relock out of the blue... Go to my DFU unbrick guide and stop doing dumb stuff :silly:
Click to expand...
Click to collapse
... after I finally got it working again (thanks for the assist), I thought relocking it was just making it secure again. I been rooting/unrooting and swapping out roms since the galaxy s2, who'd think you can't unlock and relock... I do think there should be warnings as it is too easy a mistake to make... lmao stop doing dumb stuff you start first
My phone is insured so I'm not overly fussed, but others will be less fortunate.

hello everywone...i have a troble to...my phone is A2017GV1.2.0B04 like this in post.
I bay this phone whit broken screen, i change the screen and try sim card but the phone is locked Whit google account... When I try my sim to test microphone, the phone it's work OK, but I unlock google account whit add tools and after that my phone don't have a service.
Phone tells no service or turned off airplane mode...what is not true... I can change the 4g/3g/2g connection to only 3g or something else... Wi-Fi and everything else work great but no service... The phone see what operator is on sim but no service... Somebody to help me please and tell me some tutorials how to fix?
I by this phone from Denmark and now I'm in Serbia... Eny help please
Thanks anyway Dragan
---------- Post added at 08:30 PM ---------- Previous post was at 08:27 PM ----------
Mistake,whit adb tools...

Hard bricked

Hello members,
(This is my last try to save my device)
What happened?
I wanted to flash stock rom and by error I double clicked on Flash_factory in the the fastboot folder.
The device booted into fastboot and never came back. It went to edl mode (coz led was blinking) I flashed the fastboot rom but I guess in the 2nd half the Mi flash tool showed the error as TIME OUT.
In device manager, phone is detected as Qualcomm 900E so tried to install drivers (9008) after disabling signature enforcing but it showed that windows can't verify the driver.
Went to Mi service center they said it's a water damage (3 month ago it happened but the device was working fine until now) so the service center didn't do any real efforts to fix it.
What are my options! Any help will be appreciated.
P.s no edl or Fastboot.

iamshivendu said:
Hello members,
(This is my last try to save my device)
What happened?
I wanted to flash stock rom and by error I double clicked on Flash_factory in the the fastboot folder.
The device booted into fastboot and never came back. It went to edl mode (coz led was blinking) I flashed the fastboot rom but I guess in the 2nd half the Mi flash tool showed the error as TIME OUT.
In device manager, phone is detected as Qualcomm 900E so tried to install drivers (9008) after disabling signature enforcing but it showed that windows can't verify the driver.
Went to Mi service center they said it's a water damage (3 month ago it happened but the device was working fine until now) so the service center didn't do any real efforts to fix it.
What are my options! Any help will be appreciated.
P.s no edl/Fastboot now.
Click to expand...
Click to collapse
Fastboot flashing is the safest method to flash your device. Download stock rom files from official website and flash each file separately via fastboot.
Sent from my [device_name] using XDA-Developers Legacy app

nikhel said:
Fastboot flashing is the safest method to flash your device. Download stock rom files from official website and flash each file separately via fastboot.
Click to expand...
Click to collapse
I mean to say i have no access to flastboot nor edl mode.

iamshivendu said:
I mean to say i have no access to flastboot nor edl mode.
Click to expand...
Click to collapse
Search about Deep Flashing.
Sent from my [device_name] using XDA-Developers Legacy app

nikhel said:
Search about Deep Flashing.
Click to expand...
Click to collapse
Okay

Power cycle the phone by pressing power button for 10-15 sec after that phone will become 9008
But since your phone is completely wiped out by factory command your imei is destroyed

emprazol said:
Power cycle the phone by pressing power button for 10-15 sec after that phone will becom 9008
But since your phone is completly wiped out but factory command your imei is destroyd
Click to expand...
Click to collapse
Can i restore my imei?

iamshivendu said:
Can i restore my imei?
Click to expand...
Click to collapse
yes you can but you must active diag port first then find a qcn and edit it with your imei and restore with qpst
its complicated i think its better to visit a technician

Fatal Error (Bricked) - System is destroyed

Hi!
I tried to flash a Stock Rom (June) via Myflash, and after the process the phone booted into a message saying "System is destroyed", The bootloader was locked after that and myflash couldn't flash the phone again.
I did the testpoint and finally myflash is recognizing the phone as a COM device, i flashed a lot of stock roms but with all im facing the same problem, after the flash, the phone stays in black screen and only vibrates when i press the power button.
If i try to connect the phone into the pc, the phone starts vibrating but nothing else happen.
I tried with the unbrick tool by cosmic dan and with the QFIL app, and everytime that a flash is successful, the phone again only vibrates when i try to power on.
Do you guys know, which rom do i need for this kind of flash? do i have other solution? (Colombia doesnt have an official Xiaomi store so i cannot take it there. to fix it)
Thanks

maybe your EMMC is faulty
i don't know if there is a free tool for this but when a customer phone comes with such this problem i will erase whole EMMC with MEDUSA PRO and flash it again to be sure that there is no problem but EMMC

emprazol said:
maybe your EMMC is faulty
i don't know if there is a free tool for this but when a customer phone comes with such this problem i will erase whole EMMC with MEDUSA PRO and flash it again to be sure that there is no problem but EMMC
Click to expand...
Click to collapse
I will try with this one, "EMMCDLTOOL" that it seems to be free and do the same thing as the Medusa Pro
Thank you for your reply, really.

I tried to erase the EMMC and that didn't work. So i'm still locked and with a black screen with vibration.

Strange, maybe partitions got corrupted, but I dont know how to fix them back.

TrueMS said:
Strange, maybe partitions got corrupted, but I don't know how to fix them back.
Click to expand...
Click to collapse
I was thinking the same thing... And i'm right now searching how to built the partitions again...

i had the same problem and i used the TOOL ALL IN ONE to unlock the boot loader and access the twrp erease all data systeam internal everything and than i used miflash tool to flash the latest stock frimware and i fixed my mi a1 im not that good with the English but i think you will understand me if not contact me

nenad96 said:
i had the same problem and i used the TOOL ALL IN ONE to unlock the boot loader and access the twrp erease all data systeam internal everything and than i used miflash tool to flash the latest stock frimware and i fixed my mi a1 im not that good with the English but i think you will understand me if not contact me
Click to expand...
Click to collapse
hey, I'm having the same difficulty, maybe I'll try this method.
Do I have to be with Active Debugging Mode? because mine is not and I can not change it.

Hard Bricked 6T (No TWRP, OEM locked, MSM not working)

Hello dear community,
I've been playing with my 6t for a long time, hundreds of custom roms, kernels, etc..
Lastly I went to official oxygen 10. I tried to install twrp via fastboot but every time I tried to push the files, I would get a error. I reinstalled drivers, tried different ports, different tools..
I got mad and blindly followed some article where someone suggested putting "persist" in the fastboot command, I tried it, I thought it is some kind of "force push" the file and that is how I probably corrupted persist partition. DUMB
Phone not booting of course and I went to restore it with Msmdownload tool.
It did not fixed it.
I tried different versions of msm, I tried going to Hydrogen, tried different USB ports, tried type C ports, different PCs...
No luck, phone is stuck at bootloop, with no TWRP and bootlocked.
I read somewhere that Msmdownload tool is not flashing persist partition and I assume that is the reason why my phone can't be restored.
Fastboot commands are not working anymore and EDL mode is probably the only possible way to communicate with the device.
I live in Montenegro and I can't send phone to oneplus to repair it.
I searched the threads and noticed that some users with similar problem eventually succeed to restore the phone by flashing it with Msm multiple times. I am still trying to do it but no luck.
I would really appreciate help from dev mastermind.
Thank you!

If your bootloader is locked again, i think it is not possible to use Msn tool. I think the only way is to send it for repair if you can't boot the phone.
But maybe i'm wrong and someone else know the sollution.

Deurklink73 said:
If your bootloader is locked again, i think it is not possible to use Msn tool. I think the only way is to send it for repair if you can't boot the phone.
Click to expand...
Click to collapse
Thank you for response, but I think that msmdowload tool is made mainly to be able to flash even locked bootloaders, although I am not 100% sure...

Papagaj said:
Thank you for response, but I think that msmdowload tool is made mainly to be able to flash even locked bootloaders, although I am not 100% sure...
Click to expand...
Click to collapse
You are correct. Msm tool will work on locked bootloader.

Man that sucks. Seems like you might be screwed. I screwed up a couple times getting to A10 but I was able to get msm tool to work for me. You are using it while your phone is powered off, correct?

Try different version of android with msm tool. Like try using the Android 10 msm tool then try the Android 9 msm tool

GeekMcLeod said:
You are using it while your phone is powered off, correct?
Click to expand...
Click to collapse
Hi GeekMcLeod, That's right, I boot it in bootloader mode, select "turn off" just to be sure that phone is shut down. And then I hold volume up and volume down together and plug the cable so it goes in EDL mode. Windows recognize it just as Qualcomm HS-USB QDLoader 9008, and that is all right I think.
Then I start MSMdownload tool and it flashes everything in around 200 seconds. I leave phone pluged in while it try to boots, but it never boot up. I left it for 45 minutes but still nothing...

jamescable said:
Try different version of android with msm tool. Like try using the Android 10 msm tool then try the Android 9 msm tool
Click to expand...
Click to collapse
I tried several versions. I was hoping to find Android 10 tool for oneplus 6t but it is still not available.

Papagaj said:
Hi GeekMcLeod, That's right, I boot it in bootloader mode, select "turn off" just to be sure that phone is shut down. And then I hold volume up and volume down together and plug the cable so it goes in EDL mode. Windows recognize it just as Qualcomm HS-USB QDLoader 9008, and that is all right I think.
Then I start MSMdownload tool and it flashes everything in around 200 seconds. I leave phone pluged in while it try to boots, but it never boot up. I left it for 45 minutes but still nothing...
Click to expand...
Click to collapse
Sounds like a driver problem to me. Try gathering a few (by Google, OnePlus, perhaps even Samsung) and keep trying different ones. I had to do this on my OnePlus One years ago. Then suddenly I found one that worked and I could revive it back from the dead. Not saying that it would work for you but it might. In my case it was a Qualcomm tool. If you still end up with nothing but dead ends today, I'd initiate a chat with OnePlus on this page (select your country at the bottom of the page first).
Wrapped with delicious Fajita [emoji896]

The only solution is to use smt mode inside msmdownloadtool, which will restore persist partition, but with some disadvantages.
Be aware that you WILL LOSE YOUR IMEIs and WIDEVINE L1, use it at your own risk.
If you decide to do it (remember you WILL LOSE YOUR IMEIs and WIDEVINE L1!) follow this:
1.- Run MSMDownloadTool.
2.- Click on Verify and wait till it says "MD5 Check OK!".
3.- Then click on SMT Mode.
4.- Then click on Start like you would normally do with upgrade mode.
5.- The you need to enter as password "te123" and select your phone's capacity.
6.- If it says something like "Port disabled by user", go to the top left corner and click on "SMT", "COM Setup" and check everything, then click on the left button, and retry steps 4-5.
7.- When the process finishes the phone won't reboot, so you'll need to hold VolumeUP+Power until it powers on, then wait around 5 minutes and your phone will be back to life!!
8.- If you have an IMEI backup, just follow this guide (https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789) (I don't know if this is the correct way to post links)
I hope you get your phone fixed.

Papagaj said:
Hi GeekMcLeod, That's right, I boot it in bootloader mode, select "turn off" just to be sure that phone is shut down. And then I hold volume up and volume down together and plug the cable so it goes in EDL mode. Windows recognize it just as Qualcomm HS-USB QDLoader 9008, and that is all right I think.
Then I start MSMdownload tool and it flashes everything in around 200 seconds. I leave phone pluged in while it try to boots, but it never boot up. I left it for 45 minutes but still nothing...
Click to expand...
Click to collapse
Don't go to edl mode. Just have your phone powered off and use msm tool. I used it a couple times while getting to A10 and I only ever had to power my phone off.

amt911 said:
The only solution is to use smt mode inside msmdownloadtool, which will restore persist partition, but with some disadvantages.
Be aware that you WILL LOSE YOUR IMEIs and WIDEVINE L1, use it at your own risk.
If you decide to do it (remember you WILL LOSE YOUR IMEIs and WIDEVINE L1!) follow this:
1.- Run MSMDownloadTool.
2.- Click on Verify and wait till it says "MD5 Check OK!".
3.- Then click on SMT Mode.
4.- Then click on Start like you would normally do with upgrade mode.
5.- The you need to enter as password "te123" and select your phone's capacity.
6.- If it says something like "Port disabled by user", go to the top left corner and click on "SMT", "COM Setup" and check everything, then click on the left button, and retry steps 4-5.
7.- When the process finishes the phone won't reboot, so you'll need to hold VolumeUP+Power until it powers on, then wait around 5 minutes and your phone will be back to life!!
8.- If you have an IMEI backup, just follow this guide (https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789) (I don't know if this is the correct way to post links)
I hope you get your phone fixed.
Click to expand...
Click to collapse
@Papagaj do this....thats the only fix....I purposely wipe persist for to test something and I did that to recover from the boot loop.. persist store sensor information that vital to getting phone to boot....that's why it not booting..kernel is look for the sensor info but can't find it

Timmmmaaahh said:
Sounds like a driver problem to me. Try gathering a few (by Google, OnePlus, perhaps even Samsung) and keep trying different ones. I had to do this on my OnePlus One years ago. Then suddenly I found one that worked and I could revive it back from the dead.]
Click to expand...
Click to collapse
Timmmmaaahh I am so glad to see you on my thread! I learned fundamentals of flashing on your guides back in Bacon days, and never bricked it even once! But this A/B partitions really gave me headaches....
It is highly likely that drivers are causing problem, I tried to flash it with msm tool on fresh windows where I let it to automatically download required drivers and the msm progress appear to be same as when I used drivers which are recommended by msmtool developer. I will try several more and will be back with results within few hours.
amt911 said:
The only solution is to use smt mode inside msmdownloadtool, which will restore persist partition, but with some disadvantages.
Be aware that you WILL LOSE YOUR IMEIs and WIDEVINE L1, use it at your own risk.
8.- If you have an IMEI backup, just follow this guide
Click to expand...
Click to collapse
Is there a way to backup IMEI and WIDEVINE L1 at this moment? I think it is highly unlikely because functionality is limited to EDL only....
Or is there a way I can restore it later if I manage to fix a device with smt mode?
GeekMcLeod said:
Don't go to edl mode. Just have your phone powered off and use msm tool. I used it a couple times while getting to A10 and I only ever had to power my phone off.
Click to expand...
Click to collapse
How do you mean? I can't get phone connected with msm tool if it is not in EDL mode.. It is not recognized when in stock recovery, bootloader or trying to boot up OS, that is only three states this phone can be at the moment.

Papagaj said:
Timmmmaaahh I am so glad to see you on my thread! I learned fundamentals of flashing on your guides back in Bacon days, and never bricked it even once! But this A/B partitions really gave me headaches....
It is highly likely that drivers are causing problem, I tried to flash it with msm tool on fresh windows where I let it to automatically download required drivers and the msm progress appear to be same as when I used drivers which are recommended by msmtool developer. I will try several more and will be back with results within few hours.
Is there a way to backup IMEI and WIDEVINE L1 at this moment? I think it is highly unlikely because functionality is limited to EDL only....
Or is there a way I can restore it later if I manage to fix a device with smt mode?
How do you mean? I can't get phone connected with msm tool if it is not in EDL mode.. It is not recognized when in stock recovery, bootloader or trying to boot up OS, that is only three states this phone can be at the moment.
Click to expand...
Click to collapse
Nope....just rewrite you IMEI with a Qualcomm tool..quite a few available

Papagaj said:
How do you mean? I can't get phone connected with msm tool if it is not in EDL mode.. It is not recognized when in stock recovery, bootloader or trying to boot up OS, that is only three states this phone can be at the moment.
Click to expand...
Click to collapse
Oh. The few times I used it I just powered off my phone and connected it to my computer. Started msm tool and it did its thing.

Papagaj said:
this A/B partitions really gave me headaches
Click to expand...
Click to collapse
You and me both! ? lol...

I recently got stuck in a weird bootloop thing with a, what i think was, corrupted boot.img. Try finding a stock android boot.img, boot to fastboot, and run the command fastboot flash boot <boot.img> on both partition A and B. If you can't find a stock boot.img, i managed to find one and can link to a download.

All right, here is the situation.
I finally managed to boot up the phone. amt911 gave working instructions on post #10. Thank you bro, you are awesome, and Thank you Tech_Savvy for confirming the method, you are badass who deletes partitions just for fun!
All right I got the phone booted up but as amt911 mentioned, I lost my IMEI numbers, without IMEI numbers you can't dial numbers, receive calls or use mobile data.
BACKUP IMEI NUMBERS FOLKS, you never know when the partitions will screw you over!
I was dumb one without backup and I had to contact Oneplus support for help. I was suprised how quickly I got into communications with one of the assistants.. in less than 10 seconds.
They ask you to do full reset via stock recovery and some other basic troubleshoots, after nothing, obviously, fix the missing IMEI they will arrange remote session to get your phone fixed.
You have to persist on remote session as some of assistants told me that I have to send the phone to repair.
Before they arrange session for you, you need to show them "proof of the purchase" ALSO KEEP THAT FOLKS I lost mine long time ago but luckily I found photo of invoice I took when I bought phone, phew*
I didnt have it at first when I contacted them and they say there is nothing they can do without a proof! DON'T STEAL PHONES FOLKS and then ask for support...
They will contact me for session within 48 hours and I will share the experience here.
Thank you again people!

JTVivian said:
I recently got stuck in a weird bootloop thing with a, what i think was, corrupted boot.img. Try finding a stock android boot.img, boot to fastboot, and run the command fastboot flash boot <boot.img> on both partition A and B. If you can't find a stock boot.img, i managed to find one and can link to a download.
Click to expand...
Click to collapse
Thank you JTVivian for helpful suggestion, but that method would not work. When your bootloader is locked, fastboot commands are useless, you can't flash anything.

Papagaj said:
Thank you JTVivian for helpful suggestion, but that method would not work. When your bootloader is locked, fastboot commands are useless, you can't flash anything.
Click to expand...
Click to collapse
Ah you're right, i wasn't sure if that was the case but i thought i'd throw out the suggestion anyways.