Related
Maybe this has been solved before but so far I haven't found a solution to my OPO Hardbrick and I really need of your help. I tried flashing resurrection remix to my OPO and I guess it went wrong, I tried restoring my backup and it didn't work so I decided to factory reset it which deleted the rom. Now, I have used several tool kits and they all seem to have not worked, it only removed my custom recovery (TWRP) and replaced it with the Cyanogen Recovery, now my phone doesn't even turn on, its all black and vibrates, I am able to use the tool kits using the volume up and power button, but no fastboot, any solutions? Thank you so much
Ok, first step is not to panic and don't do crazy stuff and go over logically. There is no help in starting to flash stuff when your pc doesn't properly connect to your phone.
Does your pc recognize the phone when you insert the USB port after you placed it in the vol+ and power on mode (fastboot)? If yes the device should be seen in the device manager as a android or usb thing.
Check with skipsoft toolkit if you see the device with adb. Do you see any number?
Don't panic here is the solution
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Juan_Cuen said:
Maybe this has been solved before but so far I haven't found a solution to my OPO Hardbrick and I really need of your help. I tried flashing resurrection remix to my OPO and I guess it went wrong, I tried restoring my backup and it didn't work so I decided to factory reset it which deleted the rom. Now, I have used several tool kits and they all seem to have not worked, it only removed my custom recovery (TWRP) and replaced it with the Cyanogen Recovery, now my phone doesn't even turn on, its all black and vibrates, I am able to use the tool kits using the volume up and power button, but no fastboot, any solutions? Thank you so much
Click to expand...
Click to collapse
Like the other people are saying, don't worry, it's probaly not that big of a deal. I had this before. Try booting into fastboot mode and reflash TWRP recovery using the method showcased in this video: https://www.youtube.com/watch?v=KZaajUEybNM (you need to skip through it a little). Make sure you have all the proper drivers installed on your computer.
The phone doesn't go into fastboot, but it is recognized by my computer as QU something with a q, with the qualcomm drivers, I have managed to only let it be recognized via tool kits, It doesn't go into fastboot or anything. I have tried the ColorOS toolkit but apparently its more succesful if I try it on an XP computer. Whenever I hold the power and Volume Up the Phone vibrates and is recognized by the tool kit
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
I've bricked my OnePlus 7 pro.. how to go on edl and flash ROM..
The MSM tool should work eventually, the one time I used it, it took ages to get it working.
A few tips:
1] Use the official cable that came with your phone
2] Follow a guide like this (The certificate part is very important, it won't work without it), ensure you have the latest drivers (I've just exported my current ones from the phone here for you to download, Windows and Mac drivers are in there)
3] Make sure your computer sees the device when you press both vol up+down + power and lists it as the "QUSB_BULK_CID..." device, if your computer does not do that then the phone is not in the correct mode and the tool won't see it so won't show the entry to flash the stock rom(i.e. When it says "connected"), this part took me a while for the computer to list it properly.
4] Keep trying and don't give up, you should eventually see the MSM tool recognise the phone properly, as I said, it took me ages to get it working.
5] When the tool does start (and it will, I promise...eventually), leave it to do it's thing and leave the phone for a while to set itself up, you will, obviously, lose whatever you had on the phone because the tool will put it back to completely stock.
6] If I remember correctly, once the tool has finished the install the phone will reboot itself and will do an initial setup again.
7] Good luck and don't give up hope, I didn't think it was working at all either but it did eventually.
If you need to install an OS on your phone, follow this method.
https://forum.xda-developers.com/one...tboot-t3972469
This will get you back to factory settings, unlocked bootloader. This was and is the only method that works for me. Good luck!
Thank you
It finally worked. Turned off the phone completely, then pressed and hold volume up & down button for 5 seconds and then plugged in the usb cable to phone while holding the volume buttons. It recognised the phone and started flashing the file.
Thank you once again
Actually, let me add this that that the phone needs to be connected to a USB 2 port and not 3.0 for the qualcomm download mode to work and eventually for MSM to recognize your phone..
djsubterrain said:
The MSM tool should work eventually, the one time I used it, it took ages to get it working.
A few tips:
1] Use the official cable that came with your phone
2] Follow a guide like this (The certificate part is very important, it won't work without it), ensure you have the latest drivers (I've just exported my current ones from the phone here for you to download, Windows and Mac drivers are in there)
3] Make sure your computer sees the device when you press both vol up+down + power and lists it as the "QUSB_BULK_CID..." device, if your computer does not do that then the phone is not in the correct mode and the tool won't see it so won't show the entry to flash the stock rom(i.e. When it says "connected"), this part took me a while for the computer to list it properly.
4] Keep trying and don't give up, you should eventually see the MSM tool recognise the phone properly, as I said, it took me ages to get it working.
5] When the tool does start (and it will, I promise...eventually), leave it to do it's thing and leave the phone for a while to set itself up, you will, obviously, lose whatever you had on the phone because the tool will put it back to completely stock.
6] If I remember correctly, once the tool has finished the install the phone will reboot itself and will do an initial setup again.
7] Good luck and don't give up hope, I didn't think it was working at all either but it did eventually.
Click to expand...
Click to collapse
Bro.. can you help me with a guide to get miui 12 rom port on oneplus 7 pro.. i've tried doing it but my phone was stuck in loop.. i get confused with the installation process and kind a mess the Partitions.
Sunil2735 said:
Bro.. can you help me with a guide to get miui 12 rom port on oneplus 7 pro.. i've tried doing it but my phone was stuck in loop.. i get confused with the installation process and kind a mess the Partitions.
Click to expand...
Click to collapse
Hi, where do you get the ported miui 12 ? I am interested..
I wish someone make the MIUI12 Rom for OnePlus 7Pro. I've been waiting too.
I waiting ios14 ported op7pro, and Samsung Touchwiz sounds good to op7pro too
Maybe you can try this and let me know if it works on the OnePlus 7 Pro I found it on Google so I haven't checked it yet.
https://sourceforge.net/projects/miui-12-stable-ports/files/MI_Globe/
Leagoo T5c stuck at "Powered by Android" after "failed" attempt to install Android 11
Hi everyone,
I'm ready to say a thousand times "Mea culpa", but as I explained over and over in this very forum, I'm a noob when it comes to Android.
Android 11 was released yesterday, and yes, I downloaded an image for my phone, or what I thought would be a suitable image for my phone (got the arm64-v7a version), yes, I used TWRP to install it (as system image, not boot or any of the other options, because it seemed like the logical choice at the time), and yes, when the phone restarted, I was (and still am) stuck at the "Powered by Android" screen, and nothing happens.
(I didn't get any error message when in TWRP while installing the Android 11 image, though, no warning whatsoever.)
Even booting in recovery mode by pressing the Power, Volume Up and Volume Down buttons simultaneously won't work. The phone just restarts.
I thought I could save the day by flashing a stock ROM with the flashing tool provided by Leagoo, but since the phone won't shutdown, just restart over and over, the flashing tool is useless.
I juggled with the Windows drivers for the phone, hopping from one (ADB bootloader, etc...) to the next, no effect.
I wish I could open the phone and remove the battery, then put if back in, but that's impossible, because I don't have the tools it requires, so that option is out the window.
I'm open to suggestions that won't entail using this phone as a paperweight or a projectile to keep the demons at bay, though at the moment, I really don't see what purpose it could serve other than that.
Battery life isn't stellar on this device, so I suppose I could wait until it dies on me, then try to flash a stock ROM, but isn't there another way to revive the phone and start from scratch.
***I promise I won't try to upgrade Android again on this phone!***
I'd just rooted the phone, last Sunday, and everything was going fine.
I feel stupid like you wouldn't believe, but right now, I really need your help.
SOLVED: I somehow (and miraculously) managed to flash a stock ROM on the phone and I'm now in the process of setting it up as new.
A few pointers:
- On this phone, pressing Power/Volume Up/Volume Down will reboot the device; if you want to shut it down, you have to press Power and Volume Down only, and then sometimes it'll reboot anyway...
- I had to download and install either the generic USB drivers from here, or the Unisoc drivers from here to get Windows to recognize the phone. Maybe it was a problem with my phone, and the generic Google drivers will suffice in other people's phones.
You must use the UPGRADEDOWNLOAD_R17.17.2001 tool (the latest version available from here, at least), load the .pac you'll have downloaded prior to using the tool (unzip/unrar it as it'll most probably come in a compressed format) while the phone is unplugged and preferably turned off.
Load the .pac file in the flashing tool, plug your phone in the USB port, and click on the Download button. As soon as the tool clears the "Boot" stage in the Steps column, you're good to go, as it's the bootloader that causes the issues here.
The rest of the ROM install should proceed without a hitch. It should take about 10 to 15 minutes in all, then your phone will be turned off. First boot after a ROM flashing can take several minutes, but as soon as you see the Leagoo logo on-screen, it means you're home-free.
Hi,
So was running the android 12 c.15 (EU)version, and then tried to update to c.16 while keeping my root, via magisk, I most likely did one of the steps wrong and now the phone is bricked.
It happened to me before while I was running android 11, and I fixed it with MSM toolkit, however, for some reason now it doesn't find my device (tried admin mode).
The only why for me to shut off the device is goes into fastboot mode and then choose turn off. Im not sure if the device goes into EDL mode, as im pushing but volume buttons (without the power button, I know). when I connect the device to the computer there is the sound pop up, but it doesnt show in the MSM.
The only thing I can think of it is because im using :
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
and the links there are only going back to android 11 11.0.7 something...it is possible that a new version of MSM needs to come out in order to use it?
saar17 said:
Hi,
So was running the android 12 c.15 (EU)version, and then tried to update to c.16 while keeping my root, via magisk, I most likely did one of the steps wrong and now the phone is bricked.
It happened to me before while I was running android 11, and I fixed it with MSM toolkit, however, for some reason now it doesn't find my device (tried admin mode).
The only why for me to shut off the device is goes into fastboot mode and then choose turn off. Im not sure if the device goes into EDL mode, as im pushing but volume buttons (without the power button, I know). when I connect the device to the computer there is the sound pop up, but it doesnt show in the MSM.
The only thing I can think of it is because im using :
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
and the links there are only going back to android 11 11.0.7 something...it is possible that a new version of MSM needs to come out in order to use it?
Click to expand...
Click to collapse
Try reinstalling the Qualcomm device driver.