Related
Hi there! First of all I don't speak english very well.
My Galaxy Nexus hard bricked yesterday.
tl;dr no boot animation, no recovery mode, no download mode, no response from computer.
I thought it had just a low battery level, I found it turned off. So I tried to recharge it but it gave no signals, no battery icon, nothing.
After an all night long recharge I tried to turn it on, to enter in download mode or in recovery mode but nothing works. I also tried to connect it with my computer with and without battery, no response, no "OMAP" device found, no sound from Windows for plugging it in, nothing.
I found this thread here in xda, many people has been redirected to it and found their solution to the brick problem.
I tried to follow all the steps but when I plug in the phone and start the .bat file nothing happens, just stuck on "Waiting for device".
The phone is unlocked and rooted. I'm running AOKP JB-MR1 Build 2 and Franco Kernel for a month, never had problems with them, never installed other ROMs after that.
What should I do now? Should I try to do something or just bring it to a support center? The phone is still in warranty, there would be any problem because it has a non-stock ROM?
I've red about a jig to force the Odin mode, should I buy it? (I found this one)
Thanks for the help.
Have you tried booting into Odin mode
ntb81 said:
Have you tried booting into Odin mode
Click to expand...
Click to collapse
Yes, it doesn't work.
have you your warranty on it?
return it and get a new one
It's hard bricked and a JTAG unit may force it into download mode, if you send it in for warranty, chances are it won't be accepted as it was obviously tampered with and they would find out that your bootloader is unlocked and charge you more money than the device is actually worth to fix it.
I don't understand how it could of bricked if nothing has changed on the phone for a month or longer. Nothing was flashed recently so how can you hard brick the phone?
Beauenheim said:
It's hard bricked and a JTAG unit may force it into download mode, if you send it in for warranty, chances are it won't be accepted as it was obviously tampered with and they would find out that your bootloader is unlocked and charge you more money than the device is actually worth to fix it.
Click to expand...
Click to collapse
Yeah, that's why I'm not sure to send it in for warranty. So have I to try with a JTAG first?
[bman123] said:
I don't understand how it could of bricked if nothing has changed on the phone for a month or longer. Nothing was flashed recently so how can you hard brick the phone?
Click to expand...
Click to collapse
I'm not understanding that too, I don't know what happened. Suddendly it stopped working. Maybe is just a battery problem, I'll try to use another one before bringing it to the shop where I bought it.
same happened to me, but I have an untouched phone with stock android. it worked well for over an year until today.
I see a lot of people having same issue, but they say that when connected to PC over USB the phone is recognized as OMAP.
for me the PC doesn't do anything...
any help? thanks
---------- Post added at 06:12 AM ---------- Previous post was at 06:02 AM ----------
galiganu said:
same happened to me, but I have an untouched phone with stock android. it worked well for over an year until today.
I see a lot of people having same issue, but they say that when connected to PC over USB the phone is recognized as OMAP.
for me the PC doesn't do anything...
any help? thanks
Click to expand...
Click to collapse
so right after I wrote that I plugged my phone into USB of my PC without battery. when I inserted the battery it started showing me the battery sign and I could started the phone. 3 minutes later it went black again, but the trick didnt work again.
any ideas? thanks
Try This !!
Arrange a 4 ohm resistor and try to attach it in ur usb plug port of phone ..it 'll force the phon eto go in download mode or say Fastboot mode.
then follow a tutorial to flash any rom..
its quite easy else ping me !!
Tech.Nik said:
Arrange a 4 ohm resistor and try to attach it in ur usb plug port of phone ..it 'll force the phon eto go in download mode or say Fastboot mode.
then follow a tutorial to flash any rom..
its quite easy else ping me !!
Click to expand...
Click to collapse
Please could you explain a bit more how to go about this? I have a Verizon Galaxy Nexus in a somewhat similar condition. This one is recognised as an OMAP 4430 device. I downloaded OMAP Flasher, installed drivers and tried to bring it back to life but after running the batch file I get this error: Operation FAILED (Remote: : Driver init error 0x00FF8080 - MMC CONFIG FAILURE). Can the resistor trick work on this and if yes, how can I go about it? I am not faint-hearted; I think I can handle it if given the right instructions.
After I tried everything i could from the internet, I went to a shop and tested to see if the USB is broken - and indeed it was. I replaced the USB component of the phone and after that it started.
Thanks guys
galiganu said:
After I tried everything i could from the internet, I went to a shop and tested to see if the USB is broken - and indeed it was. I replaced the USB component of the phone and after that it started.
Thanks guys
Click to expand...
Click to collapse
Yeah, the faulty USB port is a very common issue.
Okay, so recently installed the 4.4.2 OTA on my completely stock nexus 7 (unrooted, bootloader still locked).
Tried connecting to my PC via bluetooth (for headset) and noticed that it wasnt working (was working on 4.4), so decided that maybe a reboot would fix the problem.
And now the tablet doesn't boot. Completely unresponsive, no charging icon etc. either. Tried holding down the power button, power and +/- vol for 20+ secs to no avail. Connecting the tablet to my laptop makes windows update search for the QHSUSB_DLOAD driver. From what I've read this is supposed to be some sort of hardbrick?
I left the tablet completely stock and haven't done any tinkering except use the Wugfresh toolkit to do a backup (which only needed USB debugging on). Also the battery was definitely 60%+ before I attempted rebooting.
Help please? This is completely out of the blue seeing as I never even unlocked the bootloader or anything?
Please help!
See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582
mdamaged said:
See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?
crash91 said:
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?
Click to expand...
Click to collapse
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.
mdamaged said:
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.
Click to expand...
Click to collapse
I'll update this tomorrow morning, thanks for your help!
crash91 said:
I'll update this tomorrow morning, thanks for your help!
Click to expand...
Click to collapse
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.
mdamaged said:
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.
Click to expand...
Click to collapse
Alright so still no dice. Warranty is out of the question because I bought an imported version off eBay before it was officially available on Google play here in India.
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.
crash91 said:
(...)
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.
Click to expand...
Click to collapse
Yeah, I don't know much about that either, sorry, I'm not going to be much help there.
Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?
crash91 said:
Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?
Click to expand...
Click to collapse
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs
malikmoreni said:
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs
Click to expand...
Click to collapse
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.
crash91 said:
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.
Click to expand...
Click to collapse
Try using the Qualcomm product support Tool google "QPST" for download links
malikmoreni said:
Try using the Qualcomm product support Tool google "QPST" for download links
Click to expand...
Click to collapse
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!
crash91 said:
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!
Click to expand...
Click to collapse
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
Click to expand...
Click to collapse
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?
malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?
Click to expand...
Click to collapse
That's exactly the thing, it doesnt get into fastboot mode or anything, I assume you need a working bootloader to be able to boot fastboot? If it was in fastboot I would have attempted this already.
Anyway the seller says that the item is covered under a 1 year international warranty, thats my only chance now I guess....
The thing that concerns me is that I was completely stock, locked bootloader and unrooted. Only installed the official OTA updates (no sideloading either).
For those who are interested - I finally had time to drop by the service centre. They replaced the battery and motherboard (it was under warranty). I was expecting them to do some magic with QPST or something though.
The same has just happened to me, but I'm out of luck, the warranty has expired.
Did anyone have managed to fix it with the QPST drivers?
thanks.
Fyi, http://www.androidpolice.com/2015/0...rate-not-likely-a-result-of-firmware-updates/
Last night, whilst trying to flash all the phones in our house with their respective Nexus factory images, I inadvertently ended up running the flash-all.bat for a Nexus 5 (hammerhead) onto a Nexus 5X (bullhead) by mistake. It got as far as flashing the radio and bootloader, and rebooted the phone.
And now the phone won't turn on at all.
Can't get into fastboot mode with key combination (I'm assuming because the bootloader for the Nexus 5 was flashed mistakenly).
When plugged into a computer, it shows up in Windows Device Manager as QHSUSB_BULK.
ADB and FASTBOOT won't see the phone at all.
Can anyone help? I've tried looking online for this but the only hits I'm getting are specifically for other phones, not the Nexus 5X. A lot of the steps to resolve seem to be extremely specific to those phones (i.e. - there's a thread here about the Nexus 5 but the restore file is only for the Nexus 5).
oscillik said:
Last night, whilst trying to flash all the phones in our house with their respective Nexus factory images, I inadvertently ended up running the flash-all.bat for a Nexus 5 (hammerhead) onto a Nexus 5X (bullhead) by mistake. It got as far as flashing the radio and bootloader, and rebooted the phone.
And now the phone won't turn on at all.
Can't get into fastboot mode with key combination (I'm assuming because the bootloader for the Nexus 5 was flashed mistakenly).
When plugged into a computer, it shows up in Windows Device Manager as QHSUSB_BULK.
ADB and FASTBOOT won't see the phone at all.
Can anyone help? I've tried looking online for this but the only hits I'm getting are specifically for other phones, not the Nexus 5X. A lot of the steps to resolve seem to be extremely specific to those phones (i.e. - there's a thread here about the Nexus 5 but the restore file is only for the Nexus 5).
Click to expand...
Click to collapse
Well, that happens when you flashed the wrong bootloader image.
I remember reading about there being multiple modes with QHSUSB_BULK? Some seems to require images signed with keys from Qualcomm...
Can you take a screenshot in Windows device manager? Also try getting the USB VID and PID if possible?
alvinhochun said:
Well, that happens when you flashed the wrong bootloader image.
I remember reading about there being multiple modes with QHSUSB_BULK? Some seems to require images signed with keys from Qualcomm...
Can you take a screenshot in Windows device manager? Also try getting the USB VID and PID if possible?
Click to expand...
Click to collapse
Yeah, this is likely going to be an expensive lesson in making sure I don't have multiple factory image folders sitting on my drive, ready for flashing onto the various Nexus phones I have to 'administer' for my family and friends!
From what I've been able to gather, I had already come to the conclusion that it may be salvageable, providing I can get access to the appropriate partition image files from Qualcomm and the appropriate tool to flash it, and instructions! I've seen as much for the Nexus 5, but nothing for the Nexus 5X.
I can try and get some screenshots later tonight, and even boot up a Linux box to get some more info.
Perhaps there is an easier way...
There should be a "backup" bootloader partition (in fact, I just checked my 5X and there is one).
Perhaps try holding all buttons to get it to use the backup bootloader? But first you need to get out of the QHSUSB_BULK mode.
Reference thread for N5: http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
And then if you managed to boot the backup bootloader you should be able to just use fastboot to flash the bootloader again.
Edit: Now that I think about it, it may be bricked on even earlier boot stages since I think the bootloader image contains them as well. Probably still worth a try but I guess your chances are pretty low...
alvinhochun said:
Perhaps there is an easier way...
There should be a "backup" bootloader partition (in fact, I just checked my 5X and there is one).
Perhaps try holding all buttons to get it to use the backup bootloader? But first you need to get out of the QHSUSB_BULK mode.
Reference thread for N5: http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
And then if you managed to boot the backup bootloader you should be able to just use fastboot to flash the bootloader again.
Edit: Now that I think about it, it may be bricked on even earlier boot stages since I think the bootloader image contains them as well. Probably still worth a try but I guess your chances are pretty low...
Click to expand...
Click to collapse
Thanks for that extra info, I didn't know there was a backup bootloader (shall have to check my Nexus 6P as well!).
Unfortunately I can't get the phone out of QHUSB_BULK mode at all, so hopes are incredibly thin.
I appreciate your extra info on this!
oscillik said:
Thanks for that extra info, I didn't know there was a backup bootloader (shall have to check my Nexus 6P as well!).
Unfortunately I can't get the phone out of QHUSB_BULK mode at all, so hopes are incredibly thin.
I appreciate your extra info on this!
Click to expand...
Click to collapse
What if you hold the power button for a few seconds? Like more than 10 seconds? I think it should reboot the phone.
alvinhochun said:
What if you hold the power button for a few seconds? Like more than 10 seconds? I think it should reboot the phone.
Click to expand...
Click to collapse
If it reboots the phone, I'm not getting any feedback from the device whatsoever of that happening. Nothing appears on the screen, no vibration, no sound. Even if I do that while it's plugged into the computer, I don't get the Windows 'disconnect / reconnect' USB device sound (if you get what I mean?) to denote that a device has been unplugged/replugged back in - which is what I would expect to happen if I power cycled the phone whilst it's connected to the computer.
Hi,
I am dealing with the EXACT same situation. Did you find any solution to this? I wanted to sell my 5X in order to purchase 6P and when the buyer came I wanted to un-root the phone and write back the original recovery image. Anyway, I ended writing the bootloader also, but from my wife's Nexus 5 (hammerhead) and not from 5X
Same problem. Tried a lot of qualcomm tools and the lg flash tool with tot file. Doesnt work.
bricked
Hey brother, I am sorry to say you are screwed. I just did the same thing to my phone two weeks ago. It seems without the bootloader the phone will not react at all and yes the flash-all script flashs bootloader first then restarts but once the nexus 5 bootlader is flashed the phone cant start the bootloader.
here is my thread i started with some responses but its all bad news
http://forum.xda-developers.com/nexus-5x/help/hard-bricked-phone-t3278033
There is a plus side for you that is not for me. I have called google and was 100% honest with them as to what happend. They told me they would not warranty me out a new phone since its my fault. However they did say because it is a software issue LG should be able to fix the issue. I already started the RMA process and my phone should be arrivng at LG on monday (two days from now) so hopefully they cover it under warranty or charge me something small to just flash the proper bootloader.
I will report back to my orignal thread and this one for others as I am betting as time passes a lot of original nexus 5 owners who upgrade and are used to flashing a lot will also make the same careless mistake.
Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.
That's great news! I wonder if the repairing was done by changing the motherboard or they've been able to re-write the eMMC chip. Anyway, take good care of it
P.S. Did you told them that you wrongfully wrote the firmware from another phone or they didn't asked? I wonder if this could be considered that you void your warranty or not.
anjelika said:
That's great news! I wonder if the repairing was done by changing the motherboard or they've been able to re-write the eMMC chip. Anyway, take good care of it
P.S. Did you told them that you wrongfully wrote the firmware from another phone or they didn't asked? I wonder if this could be considered that you void your warranty or not.
Click to expand...
Click to collapse
They told the truth and everything worked in their favor: http://forum.xda-developers.com/showthread.php?t=3278033
Sent from my Nexus 5X using Tapatalk
the bulk mode is the qhusb 9008 mode. With the right files a unbrick is possible. Unbricked my G3 also from 9008 last week.
But the prob is to get the right files.
I get the files for the flex2. So iam try if i could rewrite those files.
I dont want to send it to lg, its funny so solve it with my own hands -
konsolen said:
the bulk mode is the qhusb 9008 mode. With the right files a unbrick is possible. Unbricked my G3 also from 9008 last week.
But the prob is to get the right files.
I get the files for the flex2. So iam try if i could rewrite those files.
I dont want to send it to lg, its funny so solve it with my own hands -
Click to expand...
Click to collapse
pardon me , did you have solve it ? my 5x have this problem for a week , i can't find the file , what i find is boardiag (N5) and blank flash (n6)
Hy Apayah,
Yes i did. I tried many things, but i get the effect with otg. Found an older thread in which the people write to boot a smartphone over sdcard to recovery. I made my own sdcard. The card in a usb sd adapter and with otg to smartphone.
Then flashed with the lg tool, i thin it was lg tool.
The imei i restored with a dfu cdma software.
But i dont have this nexus anymore because i go with the old.nexus 5 again and sell the 5x.
regards
konsolen said:
Hy Apayah,
Yes i did. I tried many things, but i get the effect with otg. Found an older thread in which the people write to boot a smartphone over sdcard to recovery. I made my own sdcard. The card in a usb sd adapter and with otg to smartphone.
Then flashed with the lg tool, i thin it was lg tool.
The imei i restored with a dfu cdma software.
But i dont have this nexus anymore because i go with the old.nexus 5 again and sell the 5x.
regards
Click to expand...
Click to collapse
thanks for reply , it's so hard to find OTG with C type in indonesia and LG in here must to check it not sure they can fix it .
Did some tested if this method works for N5x?
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
konsolen said:
Hy Apayah,
Yes i did. I tried many things, but i get the effect with otg. Found an older thread in which the people write to boot a smartphone over sdcard to recovery. I made my own sdcard. The card in a usb sd adapter and with otg to smartphone.
Then flashed with the lg tool, i thin it was lg tool.
The imei i restored with a dfu cdma software.
But i dont have this nexus anymore because i go with the old.nexus 5 again and sell the 5x.
regards
Click to expand...
Click to collapse
Hi I have this issue on my H791. I do have a USB C OTG cable. Are you saying you were able to point the LG Tool to the file on the SD card through the OTG cable/PC, then flash? Can you elaborate or point me to the thread in reference? I backed up my EFS partition before all this happened, so my IMEI is still intact on a backup. Thanks.
oscillik said:
Thanks for that extra info, I didn't know there was a backup bootloader (shall have to check my Nexus 6P as well!).
Unfortunately I can't get the phone out of QHUSB_BULK mode at all, so hopes are incredibly thin.
I appreciate your extra info on this!
Click to expand...
Click to collapse
I found a way off QHSUSB_BULK that worked for me--with rubber bands. To invoke either boot loader when stuck like this I needed to drain the battery completely, and I figured that would take a very long time without the screen even turning on.
I noticed that if I held in any of the volume keys + power while connected to my PC that the phone was in reality rebooting every 30 seconds--it would come and go from Device Manager. So I grabbed three rubber bands and wrapped them around the phone at each of the 3 buttons and pressed them in.
After a few hours the phone was completely dead and I could power it back on with a brief charge. Into the bootloader it went and I'm back in business.
I was doing some experiment with DriveDroid and now I am in big mess.
I think I messed up with drivedroid settings and I was not able to see my phone (oneplus 3 rooted LOS 15.1 ) on my computers.
I have tried different computers but all cant detect my phone.
I have tried drivedroid wizard, different usb systems, different usb settings and no luck.
I have tried uninstalling the drivedroid and still no luck.
The phone was going in charging mode only. Its was not going to MTP mode so I can see the phone internal storage in computer
I have tried to do factory reset also but no luck.
Now I mistakenly wiped data partition also and now the phone is with
No OS
No USB detection on phone while in TWRP
No OTG detection
No any ROM.zip file in phone memory.
When I am on TWRP and connect my phone in computer I am seeing same error message and cant see my phone interenal storage.
Now what to do? Any way to flash ROM ?
I am in big mess, and I dont want to spend money on new phone as of now
I hope someone will be my angle and suggest me something to recover and save me from this mess...
Crying out loud now...
Hi, i think you can use adb sideload with twrp
Uruloki64 said:
Hi, i think you can use adb sideload with twrp
Click to expand...
Click to collapse
Phone is not recognized in computer while in twrp mode so it is not able to connct to adb via USB.
Just get os flashed at OnePlus service center.
I did something same in my previous Samsung phone. I took it to service center and told em that it's not booting up and I don't know the reason. They flashed the firmware from scratch, charged me 250 INR and my phone was back to being normal.
aj141 said:
Just get os flashed at OnePlus service center.
I did something same in my previous Samsung phone. I took it to service center and told em that it's not booting up and I don't know the reason. They flashed the firmware from scratch, charged me 250 INR and my phone was back to being normal.
Click to expand...
Click to collapse
Ya.. going there tomorrow. Lets see what they say about it.
amit3880 said:
Ya.. going there tomorrow. Lets see what they say about it.
Click to expand...
Click to collapse
have u tried hard bricked tool for OP3? if not then try it
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Hayatzada said:
have u tried hard bricked tool for OP3? if not then try it
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
I am not able to follow this as phone is not even coming in USB mode. So its actually soft bricked because can go to twrp and fastboot mode and booting up without OS but USB is not able to detect on my computer.
now the service center guys saying I need to change the motherboard which I dont think is the issue, mother board is not going gone for sure as I can boot up in twrp and fastboot mode. its just may be the usb host controller gone.
Cant decide if I should go ahead with mother board replacement at cost of 10k INR ( phone cost was 28K INR) .
amit3880 said:
I am not able to follow this as phone is not even coming in USB mode. So its actually soft bricked because can go to twrp and fastboot mode and booting up without OS but USB is not able to detect on my computer.
now the service center guys saying I need to change the motherboard which I dont think is the issue, mother board is not going gone for sure as I can boot up in twrp and fastboot mode. its just may be the usb host controller gone.
Cant decide if I should go ahead with mother board replacement at cost of 10k INR ( phone cost was 28K INR) .
Click to expand...
Click to collapse
If you use the Method 2 of the Unbrick Guide, you don't need normal adb/usb mode recognition. Follow that guide scrupulously and step by step. Don't skip any and don't rush.
tnsmani said:
If you use the Method 2 of the Unbrick Guide, you don't need normal adb/usb mode recognition. Follow that guide scrupulously and step by step. Don't skip any and don't rush.
Click to expand...
Click to collapse
We are giving an advice of 10K InR in free and he is not even interested according to his opinion,
Hayatzada said:
We are giving an advice of 10K InR in free and he is not even interested according to his opinion,
Click to expand...
Click to collapse
I even tried that but somehow it is not even recognized as QHUSB_BULK device.
believe me I have tried all things to revive the phone but its not hard brick in my opinion, it can boot into twrp but the when I connect the phone in computer it shows the error message I shown as attachment in my first post.
yes, I have tried 2 different computers and few usb cables.
amit3880 said:
I even tried that but somehow it is not even recognized as QHUSB_BULK device.
believe me I have tried all things to revive the phone but its not hard brick in my opinion, it can boot into twrp but the when I connect the phone in computer it shows the error message I shown as attachment in my first post.
yes, I have tried 2 different computers and few usb cables.
Click to expand...
Click to collapse
Your phone need not be hardbricked to use the Guide. It will work even on a normal perfectly working phone. If your phone is not recognised while following the Guide, it only means one of two things: either it is a hardware fault or you are not following the Guide properly.
amit3880 said:
I even tried that but somehow it is not even recognized as QHUSB_BULK device.
believe me I have tried all things to revive the phone but its not hard brick in my opinion, it can boot into twrp but the when I connect the phone in computer it shows the error message I shown as attachment in my first post.
yes, I have tried 2 different computers and few usb cables.
Click to expand...
Click to collapse
reviewed post
tnsmani said:
Your phone need not be hardbricked to use the Guide. It will work even on a normal perfectly working phone. If your phone is not recognised while following the Guide, it only means one of two things: either it is a hardware fault or you are not following the Guide properly.
Click to expand...
Click to collapse
tried to follow the unbrick guide on windows 10 but phone is not seen as QSBULK device in device manager.
I am going to try on windows 7 as few post said that windows 7 would be better for unbricking than windows 10.
finger crossed, right now flashing windows 7 live iso on USB.
so finally I am declaring my op3 as hardware failure as one of my other phone (yureka) easily identified as 9008 mode in my computer but my op3 is not. so all drivers are installed correctly but somehow my op3's usb hub is failed.
i guess time to move on..
thank you everyone for spending time to help me. it really is supportive and encouraging...
amit3880 said:
so finally I am declaring my op3 as hardware failure as one of my other phone (yureka) easily identified as 9008 mode in my computer but my op3 is not. so all drivers are installed correctly but somehow my op3's usb hub is failed.
i guess time to move on..
thank you everyone for spending time to help me. it really is supportive and encouraging...
Click to expand...
Click to collapse
So sorry about that .... Sad news
@Ammit3880
have you tried plugging in a usb in you phone trough the usb OTG cable? see if twrp recognizes the usb. and just put the needed files on there. maybe windows is just breing ignorant as always
BADA 187 said:
@Ammit3880
have you tried plugging in a usb in you phone trough the usb OTG cable? see if twrp recognizes the usb. and just put the needed files on there. maybe windows is just breing ignorant as always
Click to expand...
Click to collapse
ya.. tried all the ways including various OTG cabel/dongle,, various OS windows 7/8/8.1/10 all the way..
nothing working...
amit3880 said:
ya.. tried all the ways including various OTG cabel/dongle,, various OS windows 7/8/8.1/10 all the way..
nothing working...
Click to expand...
Click to collapse
damn sorry to hear man.
BADA 187 said:
damn sorry to hear man.
Click to expand...
Click to collapse
Got 6T yesterday.... .. Yay!!
Couldnt find other phone competative in the price range.
Time to change the xda signature...
Although I bought 6T now and am kind of happy with that, but I am still missing my oneplus 3 and want to experiment on getting it revived.
By any chance someone can help me answering my doubts.. I would be greatful..
1. Is it ok to replace oneplus3's motherboard with oneplus 3t motherboard ? If by any chance i get any resell op3 or op3t in dirt cheap price I want to know if its ok to use 3T's motherboard.
2. Is there any way I can turn on the wifi from within TWRP and so I can connect to phone via adb over wifi/tcpip ??
Thank you all in advance.
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
I did that to an HTC U11 once - Never got it recovered, had to toss it...
Never dared relock a bootloader since...
I had the same thing happen to me.
The only thing that worked for me is to boot recovery and wipe system. Good luck
Jhoopes517 said:
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
Click to expand...
Click to collapse
i have the same problem let me know if you figure out a way around this !
For all of you having this issue, simply use the msm for your respective device by unplugging your phone, select power off, enter edl mode with cable plugged in and run the tool. I know another solution, but please PM me if this one doesn't work.
I had this issue as well, but you better not have messed with the sensitive partitions without a backup, otherwise there's no way to repair it.
razercortex said:
For all of you having this issue, simply use the msm for your respective device by unplugging your phone, select power off, enter edl mode with cable plugged in and run the tool. I know another solution, but please PM me if this one doesn't work.
Click to expand...
Click to collapse
i cannot figure out how to run the msm tool properly it always throws an error message
KidSudo6969 said:
i cannot figure out how to run the msm tool properly it always throws an error message
Click to expand...
Click to collapse
what is the error message? Maybe you dont have the correct one.
Jhoopes517 said:
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
Click to expand...
Click to collapse
Here is the msm tool
This was fixed via MSM. But I had another issue come up where MSM doesn't work.
Jhoopes517 said:
This was fixed via MSM. But I had another issue come up where MSM doesn't work.
Click to expand...
Click to collapse
What do you mean doesnt work? What did it do?
its not responding at all. no boot loop, no logo, no nothing. just a blackscreen no matter how long i charge it or hold the buttons down.
Aleena1217 said:
its not responding at all. no boot loop, no logo, no nothing. just a blackscreen no matter how long i charge it or hold the buttons down.
Click to expand...
Click to collapse
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
ekin_strops said:
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
Click to expand...
Click to collapse
after installing driver it recognized it in EDL mode. Im also JUST seeing that this is for the 9 and not the 9 pro. im guessing thats the issue? ii cant believe i missed that
Aleena1217 said:
after installing driver it recognized it in EDL mode. Im also JUST seeing that this is for the 9 and not the 9 pro. im guessing thats the issue? ii cant believe i missed that
Click to expand...
Click to collapse
Yes, it's for the Pro, but the procedure is the same. A good thing is that EDL works. Now just grab the MSM Tool for your model and flash it.
ekin_strops said:
Yes, it's for the Pro, but the procedure is the same. A good thing is that EDL works. Now just grab the MSM Tool for your model and flash it.
Click to expand...
Click to collapse
thank you so much. msm is downloading now. while I have you, do you have a link for the 9 pro conversion files? id really like to get that xpan update finally...
ekin_strops said:
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
Click to expand...
Click to collapse
im sorry i just realized i jumped in the middle of a different thread. This happened while trying to flash tmobile oneplus 9 pro to global firmware and after trying to enter recovery mode. Im guessing it happened because the files are for one plus 9, so im looking for the files for a 9 pro conversion but only am finding msm tool downloads for conversion instead of flashbin files.
Aleena1217 said:
im sorry i just realized i jumped in the middle of a different thread. This happened while trying to flash tmobile oneplus 9 pro to global firmware and after trying to enter recovery mode. Im guessing it happened because the files are for one plus 9, so im looking for the files for a 9 pro conversion but only am finding msm tool downloads for conversion instead of flashbin files.
Click to expand...
Click to collapse
Before I jump to conclusions, could you explain exactly which model you have and what is your goal?
ekin_strops said:
Before I jump to conclusions, could you explain exactly which model you have and what is your goal?
Click to expand...
Click to collapse
i have the le 2127 from tmobile because i didnt know any better. i dont want to root or do anything crazy. I just want to be able to flash to global or eu firmware so i can upgrade as oneplus releases the updates and not be a year behind on tmobiles schedule. I have the sim and bootloader unlocked successfully. I started to flash to the one plus 9 firmware because i somehow missed that it did not say pro. So now my phone in unresponsive except for QDL 9008 mode. MSM tool recognizes it and begins to update it but then gets a param preload "device not image match" message in red and stops. So once i figure out how to get past that and get this set to factory, i want to properly flash it to global or eu, whichever is available, and upgrade it to the latest version.
Aleena1217 said:
i have the le 2127 from tmobile because i didnt know any better. i dont want to root or do anything crazy. I just want to be able to flash to global or eu firmware so i can upgrade as oneplus releases the updates and not be a year behind on tmobiles schedule. I have the sim and bootloader unlocked successfully. I started to flash to the one plus 9 firmware because i somehow missed that it did not say pro. So now my phone in unresponsive except for QDL 9008 mode. MSM tool recognizes it and begins to update it but then gets a param preload "device not image match" message in red and stops. So once i figure out how to get past that and get this set to factory, i want to properly flash it to global or eu, whichever is available, and upgrade it to the latest version.
Click to expand...
Click to collapse
Are you getting the mismatch on the global/eu MSM or are you trying to flash back to stock T-Mobile? You're getting a mismatch because you're most likely using the wrong version of a firmware (msm).