Related
Hey Guys
I really could need a good Advise. In the past my USB-Port was broken, so i repaired it with a new one, anyway i wasnt careful enough - i pulled of the Volume-Rockers' Connector. There are no contacts left on the Mainboard, so i cant easily install some new Volume Rockers.
Well that wasnt a big Problem for me so far, i just used a Volume-Widget instead. But unfortunately my Device is now stucking within a Bootloop.
Due to the missing Volume-Rocker, i cant access Fastboot or Recovery. I tried to access the Device with the GNex-Toolkit but it wont let me install the Drivers, i guess the Driver crashes within the Bootloop. Letting the Device Boot while connected via USB, wont recognize it as ADB-Device.
I am owning a Galaxy S4 now, but i would like to repair the GNex, so that my Gilfriend might use it. Any chance to access Fastboot Mode or Recovery without the Volume Rockers on a Bootlooping Device?
I allready downloaded the OMAPFlash_tuna Package and managed it to install the OMAP 4440 Driver (it is giving me 2 Seconds to install them when i plug in the powered-off Device). After a few attempts the Omap-Flash Bat-File was running properly. But the Device is still stuck in its Bootloop. Any Advices would be really great.
Best regards
apsis said:
Hey Guys
I really could need a good Advise. In the past my USB-Port was broken, so i repaired it with a new one, anyway i wasnt careful enough - i pulled of the Volume-Rockers' Connector. There are no contacts left on the Mainboard, so i cant easily install some new Volume Rockers.
Well that wasnt a big Problem for me so far, i just used a Volume-Widget instead. But unfortunately my Device is now stucking within a Bootloop.
Due to the missing Volume-Rocker, i cant access Fastboot or Recovery. I tried to access the Device with the GNex-Toolkit but it wont let me install the Drivers, i guess the Driver crashes within the Bootloop. Letting the Device Boot while connected via USB, wont recognize it as ADB-Device.
I am owning a Galaxy S4 now, but i would like to repair the GNex, so that my Gilfriend might use it. Any chance to access Fastboot Mode or Recovery without the Volume Rockers on a Bootlooping Device?
I allready downloaded the OMAPFlash_tuna Package and managed it to install the OMAP 4440 Driver (it is giving me 2 Seconds to install them when i plug in the powered-off Device). After a few attempts the Omap-Flash Bat-File was running properly. But the Device is still stuck in its Bootloop. Any Advices would be really great.
Best regards
Click to expand...
Click to collapse
i dont see a way to boot into fastboot mode without volume keys or adb
i suggest to get a usb jig and flash stock via odin
samersh72 said:
i dont see a way to boot into fastboot mode without volume keys or adb
i suggest to get a usb jig and flash stock via odin
Click to expand...
Click to collapse
Thanks mate, i really appreciate your Help. I'm sorry that im just answering so late, but i was waiting for my USB jig to arrive. I didnt knew that there is this Option with the USB Jig, i just want to let you know that everything went well, and my Galaxy Nexus is finally back to life.
Thanks for your fast reponse :good
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.
Hi guys, this might sound really really stupid but i wanted to flash my phone back to stock and i accidentally flashed in the nexus 5 file instead of the 5x ones and now i cant enter recovery mode. Windows cant seem to detect the phone either (USB device not recognized).
Anyway around this? Thank you
fireymint said:
Hi guys, this might sound really really stupid but i wanted to flash my phone back to stock and i accidentally flashed in the nexus 5 file instead of the 5x ones and now i cant enter recovery mode. Windows cant seem to detect the phone either (USB device not recognized).
Anyway around this? Thank you
Click to expand...
Click to collapse
This should work for you. If it does, post back here and in that thread.
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Check device manager. A lot of times I would have to manually point my computer to install the driver.
PiousInquisitor said:
This should work for you. If it does, post back here and in that thread.
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Click to expand...
Click to collapse
It does not work.
I did exactly the same thing with fireymint. The N5X never boot and is always black screen since the bootloader is bad. But PC can recognize it as QHSUSB_BULK and drive it as Qualcomm HS-USB QDLoader 9008. I believe some tools can flash correct bootloader in that mode.
Till now, this post http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301 provides a solution to the most similar situation of Nexus 5. But it is not for Nexus 5x. Perhaps, the only thing we can do is cross fingers and waiting for some guru who can provide rightful tools.
fireymint said:
Hi guys, this might sound really really stupid but i wanted to flash my phone back to stock and i accidentally flashed in the nexus 5 file instead of the 5x ones and now i cant enter recovery mode. Windows cant seem to detect the phone either (USB device not recognized).
Anyway around this? Thank you
Click to expand...
Click to collapse
What happens when you hold the power+vol up+vol down keys down simultaneously for a few secs? Are you able to get into fastboot mode at all?
If not, as others stated above, the bootloader is corrupt. You could try to change your USB driver and use the LGUP tool mentioned in thread links above - but those processes are proprietary and not well documented (and may still be dependent on a functional bootloader). At the end of the day, it's probably worth contacting LG or Google support and asking if they can repair/reflash the device. This might be covered under warranty, and if not, they may only charge a small fee for the service. The frustration it would save you in trying to bring a "hard" bricked device back to life is substantial.
fireymint said:
Hi guys, this might sound really really stupid but i wanted to flash my phone back to stock and i accidentally flashed in the nexus 5 file instead of the 5x ones and now i cant enter recovery mode. Windows cant seem to detect the phone either (USB device not recognized).
Anyway around this? Thank you
Click to expand...
Click to collapse
Same problem.
Now can you fix.
I believe your phone should be able to load "Download Mode" with a bad bootloader, but I have no way to try that. Download mode is when you hold Vol Up + Power. Then you should be using the tools from second post.
Also there I see, that they only have files for a 32GB model, if yours is 16GB, the guide will not work! I am waiting for my USB A -> C cable to arrive, after that I think I may be able to provide the files they need to compile the files you will need for a 16 GB Nexus 5X. Other that that, you can always send it in for warranty. If nothing works for you, nothing will work for them, so they just might replace it.
hey guys. i havent messed with this in a while but i did the usual stuff then flashed hell fire o it a couple years ago and it boot looped on me. so i finally got around to playing with it and using my factory cable it goes right into bootloader but my computer has no clue its even plugged in. cable is fine ive used it in the passed to unbrick a couple motorollas and it goes straight to loader from power off. i have all the drivers including every sdk package but i cant figure this out? if i power off and reboot without cable it just freezes at the helfire loading screen but never goes further. so it isnt really looping actually. either way i cant get it recognized by my laptop (win 7 x64) not even with a standard data cable which i verified with gs6 is working. anyone have any advice on how to get a working fastboot connection with this or am i just sol? thanks
ps. i have stock bootloader 1st gen fire but i believe it has twrp though i cant remember the version and i cant get into it. adb doesnt recognize it, device manager shows nothing the computer does nothing when i plug it in regardless the cable. very strange. any and all help is appreciated. thanks guys!
dannyHD2 said:
hey guys. i havent messed with this in a while but i did the usual stuff then flashed hell fire o it a couple years ago and it boot looped on me. so i finally got around to playing with it and using my factory cable it goes right into bootloader but my computer has no clue its even plugged in. cable is fine ive used it in the passed to unbrick a couple motorollas and it goes straight to loader from power off. i have all the drivers including every sdk package but i cant figure this out? if i power off and reboot without cable it just freezes at the helfire loading screen but never goes further. so it isnt really looping actually. either way i cant get it recognized by my laptop (win 7 x64) not even with a standard data cable which i verified with gs6 is working. anyone have any advice on how to get a working fastboot connection with this or am i just sol? thanks
ps. i have stock bootloader 1st gen fire but i believe it has twrp though i cant remember the version and i cant get into it. adb doesnt recognize it, device manager shows nothing the computer does nothing when i plug it in regardless the cable. very strange. any and all help is appreciated. thanks guys!
Click to expand...
Click to collapse
twrp doesn't work with stock bootloader
custom Roms should not work with stock bootloader
what is on bootloader screen?
So, here's the deal with this phone. It's sat untouched for many many years. The original owner can't remember why she got rid of it (family friend). So I volunteered to take it, and turn it into an emulator device. However, it was made clear as to why she got rid of it. The phone is stuck in a gnarly boot loop. The boot loop is, Sony Ericsson screen lit up, and then goes to an unlit version of the logo. After a while, the phone will restart repeat. The phone will get into flash mode (green light) and will not continue the loop but stays on the unlit version of Sony Ericcson. I've gotten it into fastboot once, maybe twice, but I can't remember exactly how I did it (holding menu doesn't work)
I have installed the drivers for the phone, however, the phone is listed as:
E:\
Device Type: Portal Device
Manufacturer: SEMC
Location: on Volume
The drivers that it is apparently using is wpdfs.inf
Things I have tried to correct this issue.
-The Xperia app (tells me to enter flashmode in its own way and never does anything after)
-Flashing using "FlashTool"
It sees a phone but just says.
"19/025/2018 22:25:46 - INFO - Device connected with USB debugging off
19/025/2018 22:25:46 - INFO - For 2011 devices line, be sure you are not in MTP mode"
I've attempted using a fastboot method but nothing substantial as fastboot rarely happens.
Accessing the device through ADB (ADB shows not devices connected
Accessing the device through FastBoot (FastBoot shows "waiting for devices")
I have crawled through dozens of pages worth of information, similar questions, similar problems and come up short. Any advice would be super helpful.
Will provide images, and further information if requested. Thanks for your time.
I'm not familiar with the at version. Also maybe its already stated in the post and I miss it, did u try flashmode on flashtools and flash stock TFT?this is the first thing you wanna do in case of problems. For fastboot if I remember correctly you have to push search button and not the menu button, but I haven't my xplay with me.
inaroom said:
I'm not familiar with the at version. Also maybe its already stated in the post and I miss it, did u try flashmode on flashtools and flash stock TFT?this is the first thing you wanna do in case of problems. For fastboot if I remember correctly you have to push search button and not the menu button, but I haven't my xplay with me.
Click to expand...
Click to collapse
Hey, I did try flashing the stock firmware, the version is the AT&T version from the US. The problem with attempting to flash is Flashtool doesn't detect the phone. It sees that there's a phone plugged in, but flashing is impossible because it can't find the phone. I figured it must've been a driver issue, so I scoured the web to find drivers but only could find the 800a drivers, so I went ahead and attempted those, but not to no avail.
My next attempt to bring out Windows 7 and attempt to install the drivers on Windows 7, instead of 10. Just been a bit slow, and feeling a bit dejected on the whole project.
Disenfranchised said:
Hey, I did try flashing the stock firmware, the version is the AT&T version from the US. The problem with attempting to flash is Flashtool doesn't detect the phone. It sees that there's a phone plugged in, but flashing is impossible because it can't find the phone. I figured it must've been a driver issue, so I scoured the web to find drivers but only could find the 800a drivers, so I went ahead and attempted those, but not to no avail.
My next attempt to bring out Windows 7 and attempt to install the drivers on Windows 7, instead of 10. Just been a bit slow, and feeling a bit dejected on the whole project.
Click to expand...
Click to collapse
to install flashtools drivers in win 10 you need to disable uac but maybe you already did that. make sure the adb drivers are fully and correctly installe. have you tried flashing a kernel in fastboot mode by pushing the search button? also i would try to install r800i or r800a drivers. then i would suggest to make a little bit of search (i know you already did a lot...) to ensure that you can flash r800i or r800a firmware on your r800at and also try that route. i´m sorry i can´t help you more but i´m in europe and never worked on a r800at..
Hey, dont worry about it. This post is basically a hail mary for a phone that super old. I haven't tried flashing in fast boot because I have only ever gotten in fast boot once or twice. Fast boot is menu key correct? Cause I see conflict information all over the place.
i´m pretty sure it´s the search button for fastboot mode
Do you need a new battery?
Hi Disenfranchised,
I recently got out my old r800i GSM which was regularly being flung across the lounge by my kids, attached a charging cable and I had exactly the same boot loop issues as yours, but only as long as the phone was being charged. I ended up biting the bullet and buying a new battery and the phone started up. I ended up flashing Gin2Kat and it has been working well other than occasionally reverting back to the same behaviour for about an hour if the battery was completely discharged. The funny thing is when i finally manage to boot the phone at the right point during the boot loop cycle, the battery is only at 2%, meaning during the boot loop the battery is charging for maybe only a fraction of the on-off cycle.
It's a bit of an outlay (my battery was about GBP £10 - ebay). I now play SNES games on this every day during my commute. There are a few quibbles - the audio out port doesn't work (bluetooth audio works) and I get a wifi error but I ended up using Gin2Kat's apk installer to install my apps from micro-sd.
Anyway, it's a bit of a risk but see how it goes.
Fuzzy