Related
Hi everyone,
I'm having an issue with my 7 pro (1911). This is my 1st Oneplus as I used a Mi 5 before, the flash procedure was much easier without this A/B mess.
So I somehow messed up a new install of pixel experience with blu_spark kernel and twrp and found myself with the qualcomm crash error. Trying to get back into fastboot with the button combination (was able to save it once in it) the phone restarts and got stuck in edl mode. I noticed it's recognized as 9008 in the PC so I said okey this is nothing I'll just use the MSMTool to get it back on again.
Went through the xda Mega thead procedure, had no problem getting the phone to connect to the tool, however, first unexpected thing I encounter is the fact it stops with a SHA256 doesn't match error, and fails to send op2.img. I verified the ops file to make sure it has no errors and it was good. I then checked "disable sha256" box and it goes normally with the flash this time. Except in the end instead of restarting into the system it restarts into edl mode again and if the cable is still attached starts flashing again. This loop keeps going on forever.
I checked everywhere the only other thing I found that hints at a possible solution was doing an SMT download (based on this thread from OP6). Having an EFS backup already in one of my TWRP backups I went ahead with the procedure. Everything goes normally with the sha256 box disabled. it takes longer than upgrade mode (it flashes also to b slot), it finishes fine till the end. I disconnect the phone to boot it but it's still stuck in EDL mode!!! pressing any combination of button only keeps restarting the phone in EDL; when connected to the pc you see it going off then on in device manager.
The only idea I have left is waiting for battery to die, which could take forever and I have no idea if that'll work
Things I tried/used :
Qualcomm drivers are the latest from microsoft server v2.1.2.2. Tried some other ones but no change.
Pressing any combination of buttons (up + down + power, up + power, down + power) for multiple minutes doesn't change anything (it only hurts your fingers lol)
Before the issue the phone was at around 40%, I don't think the problem was battery charge, but I still tried connecting to official charger for some time but no boot.
I tried using multiple cables, ports (usb 3 and 2 from front of pc), tried on a laptop with both usb 2 and 3, all give me the same results, sha256 fails, without the check it flashes but no boot or response.
I redownloaded the MSMTool multiple times from both the Mega thread and newer one with oos 10 images, even the chinese image, all of them give the exact same issue. The only one that didn't work was the TMobile image, saying it's the wrong image (tried it just to be sure my phone wasn't originally a TMO converted, as it's 2nd hand).
Tried starting a normal flash in MSMTool and leaving it on that loop (flash, finish, restart again in EDL, flash...) all night but still found it flashing in the morning, never booted to system.
I found some people in the forums having the same symptomes (but quite rare compared to others), only 2 said they found a solution:
OP7P (this guy fixed the issue by charging his phone) https://forum.xda-developers.com/showpost.php?p=80329855&postcount=83
OP6T (this guy discharged his phone completely then connected it and it booted) https://forum.xda-developers.com/showpost.php?p=79079192&postcount=5
OP7 https://forum.xda-developers.com/showpost.php?p=81183765&postcount=41
OP7 https://forum.xda-developers.com/showpost.php?p=81185793&postcount=43
OP6 https://forum.xda-developers.com/showpost.php?p=81308571&postcount=88
OP6 https://forum.xda-developers.com/showpost.php?p=79445923&postcount=203
I'm making this thread maybe someone who had the same issue can show me how he solved it, or if not and my last resort works (complete battery discharge) hopefully stays as a helpful history to someone else.
Thanks.
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post
Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post
Click to expand...
Click to collapse
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
ANY NEWS>?
i also have an OP6T
used MsmDownloadTool V4.0_factory_mcl_op1_patched
with
rev_OverSeas_181226_1920_release_disable_OTA-BLOCK_Signed_fp1812260627_cve2018-12-01_ufs_9.0.11
and
fajita_41_O.18_181226.ops
phone was stock.
Proceeded to flash custom rom etc.
Now since then i decided i wanted stock again to try new custom rom etc. and,
i booted twrp and just wiped everything like a mad man.
i have had this happen before.
Currently, it will and can boot into any mode such as fastboot recovery(TWRP) edl and device state/secureboot are both unlocked/enabled
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
from there i booted twrp
(was my reccovery still)
mind that i wiped everything like a mad man and i lost my ADB AND FASTBOOT AND AS WELL AS MY EDL MODE PRIVILEGES(2 PCs, a couple cables tried and the phone is still not being recognized in any of the mentioned modes ), and after doing what i mention if you can get into fastboot mode you may be in luck, however if you can get back into any other mode.(Or fastboot flash a stock rom, adb sideload etc)
im still here waiting my usb otg type c because the usb wont recognize with the adapter to micro usb. Now ive never had a usb otg type c adapter before, but i know i could never get the micro usb (universal) to adapt my otg with a, "type C" type adapter and see the storage device(usb) being recognized by android. So i will reply when it arrives and i can attempt to flash stock again via otg twrp with oos zip. (THIS HAS TO BE AN A10 ISSUE WITH TWRP BEING FAIRLY RECENT IN RELEASES AND CAUSING IT TO NOT BE RECOGNIZED AFTER PERFORMING A, "FULL WIPE")
hopefully the otg for usb c is going to be recognized by twrp still.
if all else fails and your still under contract warranty, just light the **** on fire and run it over and pay the $40 deductable and take it as a $40 lesson and have them send you a new one(or upgrade depending on eligibility etc.)
---------- Post added at 10:06 PM ---------- Previous post was at 10:00 PM ----------
billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
agree
im using a tmoblie variant with msm from above
---------- Post added at 10:27 PM ---------- Previous post was at 10:06 PM ----------
https://twitter.com/NTAuthority/status/1115496145051164672
billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
No still stuck in EDL mode.
Johndoesmoked said:
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
Click to expand...
Click to collapse
I don't know if you saw my last comment but I had even opened the phone up to disconnect the battery ribbon, hoping that would get it out of EDL but it didn't. However I didn't do the trick with the buttons when connecting it, I'll try this after disconnecting the battery. Also if that didn't work I'll leave it on rubber bands like you said, nothing to lose anyway. Thanks for the tips. I'll let you know what's up.
How did you know when the phone was dead while on rubber bands, do you verify if it still gets detected on the PC ?
Yeah i had did the rubberbands for a lil more than couple days and like i said i let it sit for about a day without the bands on after i had a good 20+ hours with em on then reapplied bands for about 20 hours.my phone was completely discharged during that process( OP6T).
Upon doing this i lost access to my recovery img.
Phone only boots fastboot (even if i choose recovery, it was previously working)
So now i still cant recognize in fastboot or edl.
GOT my OTG type c and put oos on usb, but as i said now my twrp isnt booting, so i shouldnt have depleted the battery as now i have no possible recovery access modes . Aside from that, im trying to figure out more info on the device and will reply in a day with what i may come to find out.
My phone did get detected because it started up as soon as i plugged into pc.
battery seems un-accessible but may have to take this apart.
I am figuring this out and i will get back to you. I need more tech assistance from a friend in the repair industry to disassemble without destroying it tomorrow or sometime friday.
This is going to have to be some sort of an intricate process to diagnose this supposed "HARD BRICK"
:Have to correct myself
talked to my brody at tmobile to see wassup with the warrenty etc.
basically its not covered under warrenty when you mess with software, blah blah i figured anyway, and he basically advises (OR more so "i didnt tell you anything like that!"- laughing) to literally run it over with your car or just smash the screen, and file the claim without issue...
BUT THE ISSUE IS ITS GONN COST YOU $99 to get a new OP6T via Assurant
your device might be the same, or even more costly,
i would prefer to avoid all costs, spending more money, not trying to..
Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
Click to expand...
Click to collapse
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro
Lefren said:
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro
Click to expand...
Click to collapse
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol
thedeadfish59 said:
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol
Click to expand...
Click to collapse
Yeah so sad, probably the internal memory has a slight % chance it gets corrupted or something...
Since my story in the OP I bought a used 1913 that's a bit cheaper coz of external scratches and took its motherboard for my cleaner original phone. It's been working like a charm since.
hi everyone last night i plug my phone for charging after a while i came back and see crash dump mode i switch off the and try to unbrick via msm tool 1st attempt everything fine auto reboot after progress complete it stuck in oneplus logo after that i tried to redo all thing now i faced this error on MSM TOOL PLEASE HELP ME I CHANGED THE CABLE USB PORTS DRIVER REINSTALL BUT STUCK AT THIS POINT. when i uncheck sha256 downloading start but it does not stop again and phone did not auto reboot help please
My op 6 recently just decided to die? I was using it normally and locked then turned it back one and it crashed going into "Qualcomm Crashdump Mode" with no error message.
I tried re-flashing stock, lineageOS and then found the "Qualcomm MSM tool" which was supposed to fix everything... but it didn't.
So now my op6 is bricked? and has a locked bootloader
Can anyone help? Maybe lol?
ThatHumanTho said:
My op 6 recently just decided to die? I was using it normally and locked then turned it back one and it crashed going into "Qualcomm Crashdump Mode" with no error message.
I tried re-flashing stock, lineageOS and then found the "Qualcomm MSM tool" which was supposed to fix everything... but it didn't.
So now my op6 is bricked? and has a locked bootloader
Can anyone help? Maybe lol?
Click to expand...
Click to collapse
It's hardware issue and cannot be fixed by software. Motherboard replacement might fix the issue. Anyway here is the message from some telegram channels like Evolution X:
"If your phone has gotten the qualcomm crashdump mode screen, please follow these steps:
1. DO NOT REBOOT YOUR PHONE
2. Put your phone in the freezer for 15~20 minutes or until it feels like an ice cube (yes, I'm serious)
3. If you are rooted, reboot your phone ONLY ONCE back to the rom. If you are not rooted then reboot your phone ONLY ONCE to recovery.
4. Using TWRP or a root file manager such as Fx, navigate to /sys/fs/pstore and copy all files to /sdcard/. REBOOTING MORE THAN ONCE WILL DELETE THESE FILES.
Send console-ramoops and/or pmsg-ramoops log files to us."
I personally do not recommend this because I didn't test it yet because my phone does not experience crashdump. It's for you to decide. Here is the message link for your reference.
tiga016 said:
It's hardware issue and cannot be fixed by software. Motherboard replacement might fix the issue. Anyway here is the message from some telegram channels like Evolution X:
"If your phone has gotten the qualcomm crashdump mode screen, please follow these steps:
1. DO NOT REBOOT YOUR PHONE
2. Put your phone in the freezer for 15~20 minutes or until it feels like an ice cube (yes, I'm serious)
3. If you are rooted, reboot your phone ONLY ONCE back to the rom. If you are not rooted then reboot your phone ONLY ONCE to recovery.
4. Using TWRP or a root file manager such as Fx, navigate to /sys/fs/pstore and copy all files to /sdcard/. REBOOTING MORE THAN ONCE WILL DELETE THESE FILES.
Send console-ramoops and/or pmsg-ramoops log files to us."
I personally do not recommend this because I didn't test it yet because my phone does not experience crashdump. It's for you to decide. Here is the message link for your reference.
Click to expand...
Click to collapse
Thanks for the reply, I will try this as a last resort, but I've already rebooted my phone many times and I can't boot into OOS..
tiga016 said:
2. Put your phone in the freezer for 15~20 minutes or until it feels like an ice cube (yes, I'm serious)
Click to expand...
Click to collapse
Good God, please don't do this.
Putting your phone in the freezer and thawing it out will create a ton of condensation in the mainboard that's extremely difficult to get rid of & dry (it may take several weeks to months). Powering on the device while it's still wet like this can and most probably will short the circuits on the board, making the problem even worse.
OP, if the problem is software, it should be solvable with the MSM Tool.
Else if it's hardware, then the safest solution would be taking it to a certified service center and get the board replaced entirely.
adeklipse said:
Good God, please don't do this.
Putting your phone in the freezer and thawing it out will create a ton of condensation in the mainboard that's extremely difficult to get rid of & dry (it may take several weeks to months). Powering on the device while it's still wet like this can and most probably will short the circuits on the board, making the problem even worse.
OP, if the problem is software, it should be solvable with the MSM Tool.
Else if it's hardware, then the safest solution would be taking it to a certified service center and get the board replaced entirely.
Click to expand...
Click to collapse
The same thing happened to me about a year ago. After completing the msm tool procedure my phone got stuck in a permanent bootloop w/ the bootloader locked of course. I suggest using the msm tool sparingly as this happened to me after about the tenth time I used it.
First of all thanks to the contributors here for pulling together the user guides for unbricking the phone. I am in a rather weird situation. While trying to flash my hard-bricked onePlus 6 - I think the battery was low, and the download did not complete fully. Since then, I have recharged the phone but the download gets stuck on this error: Firehose GetUSInfo Failed
I think my phone does not power-off fully somehow. I keep holding the powerbutton for over a minute, but the minute I connect the phone to my PC, it gets recognized immediately with the correct Qualcomm 9008 port. So the drivers are correct, and the PC recognizes the phone correctly.
Any idea how to switch off the phone fully, and then how to get past the 'Firehose GetUSInfo Failed' error?
Thanks in advance!
bro izi fix, i get this before and oneplus agen in jordan cant fix it so i fix it by myself, now im going to sleep pls send me a msg on telegram ( @NotReal0 ) i will learn you how to fix it but pls tomorrow u go to any pro dev shot ask them to get you the imei partation EFC that file have imei number and mac address you will need it for real
just send me a msg so i can help you step by step
( i dont need your money )
ThatHumanTho said:
My op 6 recently just decided to die? I was using it normally and locked then turned it back one and it crashed going into "Qualcomm Crashdump Mode" with no error message.
I tried re-flashing stock, lineageOS and then found the "Qualcomm MSM tool" which was supposed to fix everything... but it didn't.
So now my op6 is bricked? and has a locked bootloader
Can anyone help? Maybe lol?
Click to expand...
Click to collapse
Hey guys,
Recently after a software update my OP 8 started to crash and after that it would restart itself up. One day it just decided not to do it again, power button did nothing and it just wouldn't boot at all. I thought that the phone was dead, but after a couple of weeks I decided to connect the phone to my computer and after a "low battery warning" it boot up. When booting up, after a while it did the same thing as before, it crashed and decided to restart itself up. I did a factory reset and the same thing happened when I got to the android set up screen.
The same day, I decided that I needed to change the ROM since there could be a problem with it. While trying to unlock the bootloader I realized that I need a code from T Mobile (which I'm solicited and still waiting on), I decided to turn the phone off (so that it didn't restart or crashed) and wait for the code to get to me.
The next day, I tried to boot up the phone and it didn't. When connected to my pc i saw that it was recognized as a QCBulk (something like that), I learned about Qualcomm EDL, downloaded drivers and the phone is kinda talking to my pc. Now, I have used MSM tool to install new firmware but after installing the phone doesn't boot back up but stays on the same EDL mode.
So I need some advice,
1. I thought of waiting on the battery to run out and maybe the phone would get out of EDL mode that way.
2. Keep trying to flash different OOS roms via MSM tool and hope that the phone boots back up afterwards.
3. Using QFIL (one of Qualcomm tools) install need firmware. Problem is, I need a .efl or .mbn file which should be included in the firmware but can't find anywhere.
Please help me guys,
I just bought the phone and I miss it
THANKS!
I would think MSM tool is your only hope. Are you using the MSM tool for the tmobile version?
Did you fix your problem yet? @Gipsydanger120
I can give you the .efl firehose for the device if you want it, but it's almost useless cuz you can only use it with partition manager thats all.
L0ND0NB0Y said:
I can give you the .efl firehose for the device if you want it, but it's almost useless cuz you can only use it with partition manager thats all.
Click to expand...
Click to collapse
I would appreciate if you could give me the .efl file. I can use QFIL to flash it. Maybe that works cause I haven't been able to make it work, I'm still in EDL mode
Gipsydanger120 said:
I would appreciate if you could give me the .efl file. I can use QFIL to flash it. Maybe that works cause I haven't been able to make it work, I'm still in EDL mode
Click to expand...
Click to collapse
Alright I'll give it to you as soon as I get home
There you go @Gipsydanger120 !
Report back how it goes @Gipsydanger120
L0ND0NB0Y said:
Report back how it goes @Gipsydanger120
Click to expand...
Click to collapse
Thank you very much, I'll let you know if it works
trinidude4 said:
I would think MSM tool is your only hope. Are you using the MSM tool for the tmobile version?
Click to expand...
Click to collapse
Yes, I'm but it's no help. After installing, the phone disconnects and then goes back into EDL mode. I can tell since my pc makes a noise every time something connects/disconnects. I thought auto-reboot in MSM would help, but it doesn't.
L0ND0NB0Y said:
Report back how it goes @Gipsydanger120
Click to expand...
Click to collapse
So I tried to use QFIL with the efl file along side the "firmware" that i downloaded from OnePlus site, but it looks like I need some other type of file. I was following a tutorial and they mentioned that the firmware usually came with this efl file and maybe an XML file too.
So my conclusion is that I need other type of files too be able to use QFIL.
Any advice? Or am I missing something?
Gipsydanger120 said:
Yes, I'm but it's no help. After installing, the phone disconnects and then goes back into EDL mode. I can tell since my pc makes a noise every time something connects/disconnects. I thought auto-reboot in MSM would help, but it doesn't.
Click to expand...
Click to collapse
You know you could force restart the phone out of EDL mode by disconnecting USB holding all buttons at once for about 10 or 12 secs the phone should boot, but if there is a problem with a partition the phone will reboot once again to EDL. If it does reboot to EDL again, your last option would be a SMT download which will 100% make it boot but you will lose your IMEI and widevine certificates. It's a problem to solve another problem.
Gipsydanger120 said:
So I tried to use QFIL with the efl file along side the "firmware" that i downloaded from OnePlus site, but it looks like I need some other type of file. I was following a tutorial and they mentioned that the firmware usually came with this efl file and maybe an XML file too.
So my conclusion is that I need other type of files too be able to use QFIL.
Any advice? Or am I missing something?
Click to expand...
Click to collapse
That's what I was referring above to "it's almost useless", you won't be able to flash it with qfil unless you have the rawprogram.xml and patch.xml for EACH LUN, so that's 5 pairs of xml files.
L0ND0NB0Y said:
You know you could force restart the phone out of EDL mode by disconnecting USB holding all buttons at once for about 10 or 12 secs the phone should boot, but if there is a problem with a partition the phone will reboot once again to EDL. If it does reboot to EDL again, your last option would be a SMT download which will 100% make it boot but you will lose your IMEI and widevine certificates. It's a problem to solve another problem.
Click to expand...
Click to collapse
I've tried to get it out of EDL but i can't. Any key combination doesn't work, that's the main problem.
What's wrong about losing my IMEI? I can probably live without widevine certificates, but what about IMEI?
L0ND0NB0Y said:
That's what I was referring above to "it's almost useless", you won't be able to flash it with qfil unless you have the rawprogram.xml and patch.xml for EACH LUN, so that's 5 pairs of xml files.
Click to expand...
Click to collapse
And after you create the xmls and arrange them in folders with firmware files you are going to realize that QFIL can't flash the files for some reason and all your work have gone.
L0ND0NB0Y said:
That's what I was referring above to "it's almost useless", you won't be able to flash it with qfil unless you have the rawprogram.xml and patch.xml for EACH LUN, so that's 5 pairs of xml files.
Click to expand...
Click to collapse
Dang, and do you have any idea where can I get all that? It really sucks that I can't find anything for this phone.
Gipsydanger120 said:
I've tried to get it out of EDL but i can't. Any key combination doesn't work, that's the main problem.
What's wrong about losing my IMEI? I can probably live without widevine certificates, but what about IMEI?
Click to expand...
Click to collapse
No signal, no data!!!
and most important you will lose the ability of flashing the unlock_token cuz it's gonna say "Verify failed" obviously because of the null imei.
Gipsydanger120 said:
Dang, and do you have any idea where can I get all that? It really sucks that I can't find anything for this phone.
Click to expand...
Click to collapse
Dude, I spent nights creating them I have them but QFIL won't flash our phones idk maybe because of secure boot.
L0ND0NB0Y said:
No signal, no data!!!
and most important you will lose the ability of flashing the unlock_token cuz it's gonna say "Verify failed" obviously because of the null imei.
Click to expand...
Click to collapse
Hmm is it possible to get another IMEI? What if I already have the unlock_token? I'm guessing it won't even work since it doesn't have the IMEI anymore
L0ND0NB0Y said:
Dude, I spent nights creating them I have them but QFIL won't flash our phones idk maybe because of secure boot.
Click to expand...
Click to collapse
Man that sucks! I don't even know how my phone got so messed up in the first place.
I have an OP 9 LE 2115 Global in USA
I was on LOS 19.
I had some issues and wanted to revert back to stock OOS 11.
First I tried via Recovery to flash Stock ROM OOS 11, but I had an error regarding the system version being too old and it didn't complete. The phone would no longer boot to OS.
I got the MSMDownloadTool from here: https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_9/Global_LE25AA/R/
I used the tool successfully and got my phone booting to OS again.
But now my power button IMMEDIATELY turns off the phone whenever pressed, and does this kind of CRT TV shutdown, where the screen phases out vertically with colors.
This happens in recovery/fastboot menus as well, most of the time, and makes booting into recovery/fastboot *almost* impossible, as when I let go of the power button it turns off, and when I select and option with the power button it shuts off.
Any information would be so helpful! Thank you fine knowledgeable people of XDA.
For anyone to help, we need to know which model you have and which version of msm tool did you use?
Updated my original post. My apologies for the lack of important details.
Also I got a TWRP recovery successfully installed, so I have a recovery again.
I found this article that explains how to install each part individually via fastboot
Do you think this would help with my errors of non-existent partitions?
How to Unbrick OnePlus 9/Pro via Fastboot Commands
In this comprehensive guide, we will show you the steps to unbrick the OnePlus 9 and 9 Pro devices via Fastboot Commands.
www.droidwin.com
I'm tempted to try, but if anyone could chime in first?
Still having this issue, has anyone ever even heard of this problem?
wakeeshi said:
Still having this issue, has anyone ever even heard of this problem?
Click to expand...
Click to collapse
This sounds like a hardware problem. If just after msm the phone does this, hardware it is then.
Thank you for the reply.
Do you have any more information or an idea on how to fix it? Or are you implying I may have caused permanent damage?
wakeeshi said:
Thank you for the reply.
Do you have any more information or an idea on how to fix it? Or are you implying I may have caused permanent damage?
Click to expand...
Click to collapse
Flash with msm again. If problem persist after first time setup, hardware problem.
MrSteelX said:
Flash with msm again. If problem persist after first time setup, hardware problem.
Click to expand...
Click to collapse
I have flashed with MSM a couple more times and same thing.
But for example, I got it to boot without the issue again, and everything works as normal, but as soon as I turn the phone off or it dies, I will struggle to get a boot that works properly.
I end up fiddling with the holding the volume buttons and power buttons in different combinations and eventually it works. I'm not sure if that's just random, or if I'm actually causing it.
If I can have a completely working boot, where the power/sleep button functions as normal, it seems like it's a firmware, data issue. Could you elaborate?
Thank you!
Hoping to bump this and try to get some help. My GPS also has failed to get a fix in this kerfuffle. (this is one of the reasons I was originally resetting to stock from LineageOS 19). Any advice?
Hardware problem and the fact it is 100% repeatable is a sign of hardware problem.
So for the last three months I've been using my rooted phone with the Pixel Experience ROM, and today I decided to switch back to the stock rom. I first tried to uninstall Magisk, but when I checked the app it was already uninstalled, which I think was a bit strange. Then I downloaded the global 14.0.1 MIUI and tried to flash it via recovery mode using adb, and it failed at the end of the flashing process. So I went to try to install it using fastboot, but after using the command fastboot devices, my phone was not listed. Then I went to the recovery mode again (I was using orange fox when doing so) and tried to reboot into fastboot mode. Doing so didn't change anything when using the command to list the devices, but MiFlash had it listed, so I tried using it. I selected the rom, and selected the "clean and lock" IIRC, it started to flash and said it finished without any errors, however my phone showed some errors that I can't remember now. I tried to reboot the phone, and it went back to recovery mode, so I tried to flash it again. In this time, I tried to stop the flashing process by removing the usb because I thought I should look for the errors first, and then I remembered that I shouldn't do it (I have a very bad short term memory), so I tried to put the usb back and flashing it again. This time the Miflash showed an error, and I realized I was using the flash command while in recovery mode, not fastboot (I accidentaly pressed "adb" in the recovery), so I tried to reboot my phone to change it and it turned off. There's no more battery charging screen, fastboot or recovery. After a lot of research, I found out that my phone is in ETL mode, it shows in the device manager on my pc and also shows in the miflash as "COM3" or "COM4".
Can someone please help me? I tried so many things so far, and I still don't want to send it to repair
If you selected clean and lock and it finished, that means you locked your bootloader, and with locked bootloader, you can't flash anything. And you also yanked usb out of your phone in the middle of flashing process? My bet, you screwed up partition or two, and now your phone is in EDL, my man... Just take it to a service centre, before it's completely destoryed
When I was writing the thread I was wondering how could I be that stupid. I think I'll really need to send It to a service center.
seiguisage said:
When I was writing the thread I was wondering how could I be that stupid. I think I'll really need to send It to a service center.
Click to expand...
Click to collapse
I would be surprised if they would be of any help, except maybe to ask you to change the motherboard completely.
TheMystic said:
I would be surprised if they would be of any help, except maybe to ask you to change the motherboard completely.
Click to expand...
Click to collapse
So probably It really is just a paperweight now
seiguisage said:
So probably It really is just a paperweight now
Click to expand...
Click to collapse
If it shows signs of life, you may be able to resuscitate it. But I doubt an official service centre would be of any help here, except as stated above.
Just do some more research. You may find a way. All the best.
TheMystic said:
If it shows signs of life, you may be able to resuscitate it. But I doubt an official service centre would be of any help here, except as stated above.
Just do some more research. You may find a way. All the best.
Click to expand...
Click to collapse
Since my gf gave me her old Mi 9 I think I'll make this a new hobby lol
TheMystic said:
I would be surprised if they would be of any help, except maybe to ask you to change the motherboard completely.
Click to expand...
Click to collapse
What are you talking about. if he has access to EDL mode he can fix everything. Even if your UFS was completely wiped and had no partitions. EDL is a completely separate thing. However you can't reflash the software using EDL because only service centers have the authorisation to do that (some people have that access too, and you can reflash your phone if you pay them). Another way to do it is open the phone up, and short some pins to get access to unauthorised EDL.
TheMystic said:
If it shows signs of life, you may be able to resuscitate it.
Click to expand...
Click to collapse
Yeah, mouth-to-usb always helps.