Database Info

A whole lot of problems with Xperia J - please read

Yesterday, I started unlocking my bootloader on Xperia J ST26i in order to eventually finish with installing ParanoidAndroid 3. It all went successful until I got to the last step of rooting the device. This - http://forum.xda-developers.com/showthread.php?t=2183737 - is the method I used. I was confused when I got to step 16, because the kernel I copied for flash didn't show up. So, I'd finish with two choices after shutting the phone down, having exited CWM Recovery. I would either open CWM again, after seeing LEDs glowing purple/blue in order to press Volume down key to enter CWM - or to ignore and finish seeing grayscreen. Luckily, I was able to find a JB 4.1.2 kernel for my rooted Xperia J, so I put it and flashed it instead of the ICS kernel provided on the thread I referred to. That solved the problem. I had JB 4.1.2 installed and rooted with ROM Manager installed along with SuperSU app. The next step I was going to do was to install a ClockWork Recovery, I hesitated installing PA3 directly without a recovery image. Ironically, CW Recovery is what really made all the problems now. Searching on Google I found a way to boot directly to ClockWork Recovery, I pressed and held the buttons for initiating it but I ended up with literally no way to normally boot the phone. So, I couldn't turn on the phone except in fastboot mode. In fastboot, I whiped all the data, reset to defaults, reinstalled the boot.img and JB kernel, however after all the resets and whipping anything that, according to many sites and devs, should make the phone function again...it failed. After a dozen times of taking out the battery, button combos I ended up not being able to access neither fastboot mode with CWM showing all those options for whipping, installing etc. Only phone's upper LED was working and it blinked red so I recharged the phone, then it was all the same but it'd blink green. After another hour of trying to turn on the phone in any mode, nothing good happened. When I held the power button, it vibrated but after a minute or so only green LED activated. Then I downloaded recovery exit zips that I'd install if ever got to CWM again. I tried once again to directly boot into CWM recovering by holding the power button down and both sides of volume rocker. It blinked light blue, then green and later blue. Device flasher couldn't read the phone, so I opened flash mode. It read it, but any installation of boots or kernels failed because of the phone that either disconnected or simply failed. There was no way for me to put more files on Internal Storage or SD Card, only those LEDs started behaving the way I described. After another twenty times of battery removing, 10 second and 30 s waiting, button combos, anything I could find on Google, nothing changed. Except, suddenly, the computer is able to link with the phone after holding power button for boot that only activated the green/blue/violet LED. Still, no response from flashing program, still failed to enter fastboot, CWM, direct CWM Recovery etc. But, now when my phone is, let's say, turned on with green or blue light, I can access SD Card and Internal Storage via Windows Explorer. Just below the hard drives, I can see my phone. Great? No, it's not Xperia J as it should be, PC detects Xperia Tipo. I also noted that it's mistaken SD Card for Internal Storage... Let's see what happens when I remove SD card from the device. Please help...

Bricked
And yes, this means it's bricked. Can't boot into CWM or anything. It's only good as a storage unit, energy consuming or as a brick. I got this phone in January so please don't tell me it's irreversibly hard bricked.

dave96m said:
And yes, this means it's bricked. Can't boot into CWM or anything. It's only good as a storage unit, energy consuming or as a brick. I got this phone in January so please don't tell me it's irreversibly hard bricked.
Click to expand...
Click to collapse
Okay, so first calm down. Any sign of life means it's not hard bricked but just soft bricked.
1st download flashtool: link
2. download ur stock ftf link
3. flash it with flashtool
and u should be fine again, back to stock with a fresh phone.

Can't fastboot device - remember: button combos don't work
I've also found some solutions for more severe soft-bricking, by the way. Anyway, how to make phone open fastboot? I've said it's unresponsive to all of the button combo commands. Though, I tried one more time.
Opened the flashtool... Held volume up and plugged in the USB cable...
17/009/2013 22:09:51 - INFO - <- This level is successfully initialized
17/009/2013 22:09:51 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
17/009/2013 22:09:51 - INFO - You can drag and drop ftf files here to start flashing them
17/009/2013 22:09:57 - INFO - Device disconnected
17/010/2013 22:10:12 - INFO - Device connected with USB debugging off
17/010/2013 22:10:12 - INFO - For 2011 devices line, be sure you are not in MTP mode
Immediately, upper LED started glowing green, then it turned itself off after a minute. The phone is still connected.

Remember to pull up battery (and pull in of course ) than go to flashtool, fastboot PWR + Vol Up.

Solved
http://forum.xda-developers.com/showthread.php?p=41506173#post41506174 See my last post, scroll down. Thanks for help, guys

sony xperia j - alarm problem
Hi guys,
I bought Sony Xperia J and 2 months ago I upgraded the Android to the latest version 4.1.2 (Jelly Bean).
After the upgrade the Alarm on the phone does not go off, it starts to ring (the alarm) only when I press the button to unlock the phone, I've read somewhere that when the screen is off the clock is not refreshes properly or something like that.
Can you please, help me?
Regards

Lol I know that feel bro.... It happened to me few days ago but no worries i just flashed the firmware using flashtool whenever i failed. Now i'm happy with my CM10 with vengeance kernel... its not the phone that's causing the problem its up to us how we handle it and i didnt find PA3 that interesting it was too laggy for me...

I didn't experience any of such problems that you have, but still listen to the man's advice. Install CM10. It speeds up your device, gives you options, frees your Android. My friend knows the feeling of switching from iPhone to Nexus 4 and he's like he's enlightened or something, well once again, the feeling is the same if you switch from stock Android to CM or Paranoid. I suggest you install CM because Paranoid made me a lot of problems when installing even though I did everything right, and people claim that CM is more stable...
http://forum.xda-developers.com/showthread.php?t=1997251

Nexus 5 HARD BRICKED ( wont come on )

i was trying to flash android L through root toolkit ( wug fresh )
but i got an errors saying max download limit ????? bytes
then i just unplugged the phone from the computer and like an idiot
and now it wont come on
when i plug it in charge it doesnt show anything aswell
Please Help how can fix ? I Bought this with my own pocket money brand new from play store for £300
:crying: :crying: :crying:

you know that the "max download size" thing is just a WARNING message, in fact a lot of phones displays it for all operations(being all operations all fastboot flash operations), on the n5 it only shows when installing recovery (afaik).
anyway, see if it really wont come on, my phone was like that, but in fact it was in qualcomm´s QD-LOADER 9008 (i had to install some drivers for it to show up on pc). if your phone does get detected(even if as an unknown device)then you have some hope, if not - too bad you are mostly screwed.
Check your device manager

opssemnik said:
in fact a lot of phones displays it for all operations(being all operations all fastboot flash operations), on the n5 it only shows when installing recovery (afaik).
Click to expand...
Click to collapse
It showed for every fastboot flash I did just a few days ago. I don't recall that warning showing up back when I flashed 4.4.4 and prior. I think it's a change with the new bootloader.

Have you tried to use Google recovery that flashes stock ROM on your device ?
I had made a very bad thing with my N5, which resulted in a bootloop, two hours after receiving the N5 and I was almost crying. Download a stock recovery from android dev site. A Nexus is unbrekable

shiva-x said:
Have you tried to use Google recovery that flashes stock ROM on your device ?
I had made a very bad thing with my N5, which resulted in a bootloop, two hours after receiving the N5 and I was almost crying. Download a stock recovery from android dev site. A Nexus is unbrekable
Click to expand...
Click to collapse
Wrong...

Google- said:
i was trying to flash android L through root toolkit ( wug fresh )
but i got an errors saying max download limit ????? bytes
then i just unplugged the phone from the computer and like an idiot
and now it wont come on
when i plug it in charge it doesnt show anything aswell
Please Help how can fix ? I Bought this with my own pocket money brand new from play store for £300
:crying: :crying: :crying:
Click to expand...
Click to collapse
Tried a forced reboot? (Power + volume down button for bout 15 seconds).
Seems like the go-to solution but I see no one asked you yet.
Do this while connected to a charger.

Also try booting into the secondary bootloader by pressing volume up , down and power simultaneous.

Noob + Toolkit = Leathal combo
Try to learn fastboot and adb so you have control over whats happening and don`t use toolkits.

gee2012 said:
Noob + Toolkit = Leathal combo
Try to learn fastboot and adb so you have control over whats happening and don`t use toolkits.
Click to expand...
Click to collapse
Agree , but it should still be salvageable - assuming the incomplete firmware didn't cause hardware damage.

Is there any solution found? I ran into the same situation. I installed CM 11S and that prompted me an error which was unable to read the binary input file. I then reinstalled the firmware and did a reboot Now, it's hard bricked. Won't boot at all.
How do I power my N5 back?

nirmal212 said:
Is there any solution found? I ran into the same situation. I installed CM 11S and that prompted me an error which was unable to read the binary input file. I then reinstalled the firmware and did a reboot Now, it's hard bricked. Won't boot at all.
How do I power my N5 back?
Click to expand...
Click to collapse
any new device showing up in the device manager when you connect your phone to your pc?

bitdomo said:
any new device showing up in the device manager when you connect your phone to your pc?
Click to expand...
Click to collapse
It's showing up as "QHSUSB_BULK". Then I tried to install the qualcomm driver. Now nothing is showing up.

nirmal212 said:
It's showing up as "QHSUSB_BULK". Then I tried to install the qualcomm driver. Now nothing is showing up.
Click to expand...
Click to collapse
press and hold volume_down+volume_up+power keys until you see it again. It should take 20-25 seconds. Try to fix the drivers (turning off dirver signature enforcement helps a lot) to show Qualcomm HSUSB QDLoader 9008 device then follow my guide here

bitdomo said:
press and hold volume_down+volume_up+power keys until you see it again. It should take 20-25 seconds. Try to fix the drivers (turning off dirver signature enforcement helps a lot) to show Qualcomm HSUSB QDLoader 9008 device then follow my guide here
Click to expand...
Click to collapse
Can I perform this action even if my device is not started? I tried all the button options and still the device won't power on.

[Help] Super Hard Brick - Stuck in EDL and no button response at all + SHA256 fail

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

[Resolved] Leagoo T5c stuck at "Powered by Android" after "failed" attempt to install Android 11

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.

[OnePlus 6] Possibly soft bricked?

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