I'm sure there is a similar thread out there, but this is a weird situation.
To start i want to say I have never flashed a rom or messed with my OS in any way. I was using my htc one m7 as it ran out of battery, it wasn't updating or anything, but ever since, it boots straight to the bootloader screen. The problem is that none of the normal options here (fastboot, revovery, factory reset etc) do anything other than bring me back to the bootloader screen, or sometimes do nothing at all.
I also cannot take any of the advice in other threads for similar topics because when its plugged into my laptop it makes the plugged in/ unplugged noises but never gets recognized at all.
It seems bricked but I definitely haven't done anything to warrant it.
Can you select recovery and and perform factory reset?
---------- Post added at 11:50 PM ---------- Previous post was at 11:49 PM ----------
Nvmd. See what you are saying now. I am kind of in the same boat at the moment.
---------- Post added at 11:51 PM ---------- Previous post was at 11:50 PM ----------
The only difference is that I can't even get to the bootloader screen. I am stuck on the silver htc screen with exclamation marks in the corners. Have you tried running the RUU that matches your hboot version? Do you have a Sprint m7?
It's an AT&T one. Its not being recognized by my laptop either so I'm not sure if its still possible to run the RUU.
bradwig said:
I'm sure there is a similar thread out there, but this is a weird situation.
To start i want to say I have never flashed a rom or messed with my OS in any way. I was using my htc one m7 as it ran out of battery, it wasn't updating or anything, but ever since, it boots straight to the bootloader screen. The problem is that none of the normal options here (fastboot, revovery, factory reset etc) do anything other than bring me back to the bootloader screen, or sometimes do nothing at all.
I also cannot take any of the advice in other threads for similar topics because when its plugged into my laptop it makes the plugged in/ unplugged noises but never gets recognized at all.
It seems bricked but I definitely haven't done anything to warrant it.
Click to expand...
Click to collapse
when you plug it into the pc and here the sound check device manager. Do you see anything like QHSUSB_DLOAD ? if so you'll need this
http://forum.xda-developers.com/showthread.php?t=2770684
---------- Post added at 05:18 PM ---------- Previous post was at 05:16 PM ----------
MarkBell said:
Can you select recovery and and perform factory reset?
---------- Post added at 11:50 PM ---------- Previous post was at 11:49 PM ----------
Nvmd. See what you are saying now. I am kind of in the same boat at the moment.
---------- Post added at 11:51 PM ---------- Previous post was at 11:50 PM ----------
The only difference is that I can't even get to the bootloader screen. I am stuck on the silver htc screen with exclamation marks in the corners. Have you tried running the RUU that matches your hboot version? Do you have a Sprint m7?
Click to expand...
Click to collapse
How you doing my old friend
to get out of the RUU mode try and hold volume up and power for about 30 seconds then try and get in the bootloader
If it doesn't work use the RUU again
Sprint 5.xx RUU
http://forum.xda-developers.com/showthread.php?t=2795856
clsA said:
when you plug it into the pc and here the sound check device manager. Do you see anything like QHSUSB_DLOAD ? if so you'll need this
http://forum.xda-developers.com/showthread.php?t=2770684
---------- Post added at 05:18 PM ---------- Previous post was at 05:16 PM ----------
How you doing my old friend
to get out of the RUU mode try and hold volume up and power for about 30 seconds then try and get in the bootloader
If it doesn't work use the RUU again
Sprint 5.xx RUU
http://forum.xda-developers.com/showthread.php?t=2795856
Click to expand...
Click to collapse
I don't see anything when I plug it in other than the noise. Otherwise its unrecognized
bradwig said:
I don't see anything when I plug it in other than the noise. Otherwise its unrecognized
Click to expand...
Click to collapse
something should appear in device manager ..that's what the sound is, the driver initializing
clsA said:
something should appear in device manager ..that's what the sound is, the driver initializing
Click to expand...
Click to collapse
It is actually under device manager, its listed as "android 1.0"
bradwig said:
It is actually under device manager, its listed as "android 1.0"
Click to expand...
Click to collapse
Then the PC sees the phone
what phone do you have ? do you remember any of the information on the boot screen ?
clsA said:
Then the PC sees the phone
what phone do you have ? do you remember any of the information on the boot screen ?
Click to expand...
Click to collapse
It only says HTC and then goes to the android bootloader screen. I was just at an AT&T store and the guy thinks the recovery is either gone or damaged which is why nothing on the bootloader screen seems to work. apparently i need to root it and make a custom recovery but I have no idea how.
bradwig said:
It only says HTC and then goes to the android bootloader screen. I was just at an AT&T store and the guy thinks the recovery is either gone or damaged which is why nothing on the bootloader screen seems to work. apparently i need to root it and make a custom recovery but I have no idea how.
Click to expand...
Click to collapse
fastboot getvar all
Remove imei and serial number and post here
Or find out software version of your phone (like 6.12.1540.1 for US dev edition) then find firmware for that no @ xda and flash firmware
Related
Hi,
I had Nik 4.5 Custom ROM on my phone and recently I my USB port stopped functioning. To revert to S-on and claim warranty, I tried to revert to stock ROM and flashed Froyo ROM (as that was the only Indian ROM available for download on the forum). I think I made the mistake of downgrading the radio and now my phone is bricked. Any suggestions to make it work again? If I take it to HTC service centre will my they be able to detect any s-off mischief that I committed and can they fix the phone and the USB port?
Thanks in advance.
Sidd
first of all there is no indian rom availabe in the forum its a ota update.....didnt u noticed that..?????
---------- Post added at 08:11 AM ---------- Previous post was at 08:10 AM ----------
can u just give a brief description of ur mobile along with the exact current status like what steps u followed ...and are u able to go into the bootloader or the recovery atleast..???
rhlmhrtr said:
first of all there is no indian rom availabe in the forum its a ota update.....didnt u noticed that..?????
Click to expand...
Click to collapse
I downloaded the ROM PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip from Goo Manager website:
http://goo.im/stock/vivo/ruu
---------- Post added at 08:11 AM ---------- Previous post was at 08:10 AM ----------
rhlmhrtr said:
can u just give a brief description of ur mobile along with the exact current status like what steps u followed ...and are u able to go into the bootloader or the recovery atleast..???
Click to expand...
Click to collapse
I followed the following steps:
1. I downloaded the ROM
2. Renamed it as PG32IMG.zip and placed it in the Root of the SD Card
3. Switched off the phone and took out SD card and then put it back again
4. Rebooted the phone in fastboot and updated the zip file. The update was completed successfully.
5. Followed the on screen instruction and rebooted the phone.
As this point the phone was not powering on. I double checked if the battery wasn't charged. I also used my charged spare battery (I use it since, my phone doesnt charge from USB port).
I assume the phone is bricked now... Any help would be appreciated.
siddroid said:
I downloaded the ROM PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip from Goo Manager website:
http://goo.im/stock/vivo/ruu
---------- Post added at 08:11 AM ---------- Previous post was at 08:10 AM ----------
I followed the following steps:
1. I downloaded the ROM
2. Renamed it as PG32IMG.zip and placed it in the Root of the SD Card
3. Switched off the phone and took out SD card and then put it back again
4. Rebooted the phone in fastboot and updated the zip file. The update was completed successfully.
5. Followed the on screen instruction and rebooted the phone.
As this point the phone was not powering on. I double checked if the battery wasn't charged. I also used my charged spare battery (I use it since, my phone doesnt charge from USB port).
I assume the phone is bricked now... Any help would be appreciated.
Click to expand...
Click to collapse
Yes, what you flashed was an old Froyo based RUU. If you had been running Gingerbread then you had a Gingerbread radio and that radio cannot be downgraded back to Froyo. By running this RUU you have radio bricked your phone.
try if u can boot into the bootloader by poweron and volume down button even if that is not possible then sorry bro i guess then we cant help u..
rhlmhrtr said:
try if u can boot into the bootloader by poweron and volume down button even if that is not possible then sorry bro i guess then we cant help u..
Click to expand...
Click to collapse
Yes I tried that already but it doesnt work. Can it be fixed at HTC service centre?
siddroid said:
Yes I tried that already but it doesnt work. Can it be fixed at HTC service centre?
Click to expand...
Click to collapse
I don't know any other purpose for the service centre, but yes... they do fix phones.
The service centre fixed my bricked phone free of charge! They replaced the PCB and some other hardware which they did not disclose. Of course I had to escalate the matter to HTC escalation department and they were really
Kind in getting it fixed although it was out of warranty. I love HTC!
Sent from my HTC Incredible S using XDA
I bought an HTC one on the weekend. I bought the Bell version since it was $50 cheaper than the Rogers one so while I was waiting for my unlock code, I unlocked the bootloader, rooted it and flashed CM10.1.
When I received my unlock code from HTCOnlineUnlock.com, it wouldn't work and they said if I was using a custom ROM, that was likely the problem.
So I downloaded the original Bell M7 rom from the bugsy lawson website, booted into CWM and tried to install it.
It hung on "running bug_fix1" for a long time. So I reset it and now it will not turn on.
I've tried holding the power button, holding down vol+power, but nothing happens. No flashing buttons at the bottom, no LED at the top.
When I plug the phone into my computer via USB, HTC sync manager opens, and the device shows up in windows device manager under Android USB Devices / My HTC, but does not show up as a drive under My Computer.
Any suggestions??
Just a heads up unlock codes usually only work on sense roms...but lemme see your problem again gimme a sec
---------- Post added at 05:36 PM ---------- Previous post was at 05:35 PM ----------
Does fastboot or adb detect the device??
a box of kittens said:
Just a heads up unlock codes usually only work on sense roms...but lemme see your problem again gimme a sec
---------- Post added at 05:36 PM ---------- Previous post was at 05:35 PM ----------
Does fastboot or adb detect the device??
Click to expand...
Click to collapse
Thanks for the help! I've been pulling my hair out over here.
No doesnt look like either detect the device. I've attached a picture.
I had the same problem but with the phone charging. I unplug and before I turn it on there was no way to turn until I connect via usb to the pc
Maybe @18th.abn has some insight if the computer can detect the phone.. sorry for calling on you hehe
leniador said:
I had the same problem but with the phone charging. I unplug and before I turn it on there was no way to turn until I connect via usb to the pc
Click to expand...
Click to collapse
I just cycled through usb/charging/unplugged twice. The second time I went through and tried it unplugged it booted up.
a box of kittens said:
Maybe @18th.abn has some insight if the computer can detect the phone.. sorry for calling on you hehe
Click to expand...
Click to collapse
Thanks for all the help, I appreciate it!
I was on LiquidsSmooths ROM and wanted to go back to CM12 so I flashed an old nightly I had used before03082015, so I flashed the ROM then gapps then wiped dalvik, then reboot. My phone went into a black screen and that's it...when I connect to the PC the PC makes a sound like it recognizes it, but nothing.Any suggestions????
Thank you all for your info and help, I ended up sending it in to Motorola, and they have replaced it at no cost. I am just thankful that i am able to get back to the Nexus!!!!
Jess813 said:
I was on LiquidsSmooths ROM and wanted to go back to CM12 so I flashed an old nightly I had used before03082015, so I flashed the ROM then gapps then wiped dalvik, then reboot. My phone went into a black screen and that's it...when I connect to the PC the PC makes a sound like it recognizes it, but nothing.Any suggestions????
Click to expand...
Click to collapse
Have you tried to get into bootloader mode and is the phone visible in device manager?
Yup you are bricked check your device manager. We already have a thread on this.
Yeah device manager shows nothing. Wow ... That's crazy I've been doing this for years, is not like it was a file that I hadn't used before.
Jess813 said:
I was on LiquidsSmooths ROM and wanted to go back to CM12 so I flashed an old nightly I had used before03082015, so I flashed the ROM then gapps then wiped dalvik, then reboot. My phone went into a black screen and that's it...when I connect to the PC the PC makes a sound like it recognizes it, but nothing.Any suggestions????
Click to expand...
Click to collapse
long press the power button for about 20 seconds. after about 3-4 seconds, press volume down as well. this should reboot your device into the bootloader. try it.
Jess813 said:
Yeah device manager shows nothing. Wow ... That's crazy I've been doing this for years, is not like it was a file that I hadn't used before.
Click to expand...
Click to collapse
it only says this when it trys to install drivers "A request for the USB device descriptor failed"
simms22 said:
long press the power button for about 20 seconds. after about 3-4 seconds, press volume down as well. this should reboot your device into the bootloader. try it.
Click to expand...
Click to collapse
While being connected to a pc?
gee2012 said:
Have you tried to get into bootloader mode and is the phone visible in device manager?
Click to expand...
Click to collapse
In device manager it shows up as QHSUSB_BULK....
Sorry for this happening to you bro. I know the feeling I was also having major problems with update but eventually got it up and running . Good luck to you and every one else that's unfortunately bricked there n6's it ashame that this is happening to so many folks
beachbum40 said:
Sorry for this happening to you bro. I know the feeling I was also having major problems with update but eventually got it up and running . Good luck to you and every one else that's unfortunately bricked there n6's it ashame that this is happening to so many folks
Click to expand...
Click to collapse
how u get yours fixed?
I just used this .http://forum.xda-developers.com/showthread.php?t=2954008I used the method 2 part flashed everything one by one but the problems I was getting was system package not found and image not found in flash all scripts but method 2 got me going.
---------- Post added at 01:30 AM ---------- Previous post was at 01:27 AM ----------
I'm sorry no I didn't use his guide that was giving me wayyy to many issues this is the guide that saved me.http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865
beachbum40 said:
Sorry for this happening to you bro. I know the feeling I was also having major problems with update but eventually got it up and running . Good luck to you and every one else that's unfortunately bricked there n6's it ashame that this is happening to so many folks
Click to expand...
Click to collapse
beachbum40 said:
I just used this .http://forum.xda-developers.com/showthread.php?t=2954008I used the method 2 part flashed everything one by one but the problems I was getting was system package not found and image not found in flash all scripts but method 2 got me going.
---------- Post added at 01:30 AM ---------- Previous post was at 01:27 AM ----------
I'm sorry no I didn't use his guide that was giving me wayyy to many issues this is the guide that saved me.http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865
Click to expand...
Click to collapse
Was your phone hard bricked? Like you coukdnt get into fastboot? or recovery?
Jess813 said:
Was your phone hard bricked? Like you coukdnt get into fastboot? or recovery?
Click to expand...
Click to collapse
Fortunately I was still able to get into boot loader on my device and fastboot manually all the images but I'm seeing a lot of folks not being able too.
---------- Post added at 01:42 AM ---------- Previous post was at 01:41 AM ----------
beachbum40 said:
Fortunately I was still able to get into boot loader on my device and fastboot manually all the images but I'm seeing a lot of folks not being able too.
Click to expand...
Click to collapse
To answer you first question no it wasn't hard bricked thankfully
---------- Post added at 01:46 AM ---------- Previous post was at 01:42 AM ----------
Sounds like your partitions got locked up or corrupted I'm still searching for fixes for the problem just in case it happens next time I have to do an update
I had to rma I'm waiting on new device. Lost everything
Created an RMA and shipped it out today , will hope for the best, will update.
Just got notification that its been replaced and sent back!!! Woot Woot!!
They sent me an all new device, box and new power plug and everything.
coldconfession13 said:
They sent me an all new device, box and new power plug and everything.
Click to expand...
Click to collapse
Was yours unbranded ? Mine arrives tomorrow and I'm wondering if they ate going to send me an unbranded Nexus as mine was AT&T branded and unlocked to work on T-Mobile. I hope I don't have to unlock it again, it was a PAIN to do so.
Unbranded.
Sent from my Nexus 6 using Tapatalk
coldconfession13 said:
Unbranded.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
But you got an all new box and charger ? I hope I get the same, brand new device too? As in new Imei #?
My Sony Xperia z1s just decided to bootloop today for no apparent reason. May be an issue with the 5.0 version it runs? It powers on, shows the Sony screen, then the screen goes blank (black screen, backlit) before going completely to black, then back to the Sony screen again. I'm having a hard time getting Command Prompt to read it, and with this sh***y locked bootloader, I feel like my hands are tied. The phone is rooted, and on stock ROM of course. I'm used to my Huawei and flashing ROMs, fixing soft bricking and whatnot, but it's a factory unlocked device, not this Sony-Tmobile locked carrier crap. I'm less familiar with dealing with this sort of thing. I've already tried pressing down the red button next to the SIM, no dice. I've hard reset using Vol+ and power. Pretty much the extent of what I've done, other than swearing at it. I just want this thing working again, I'm so tired of having to deal with it. First its horrid touchscreen, now this. Running PC Companion seems to be suggested in a lot of places, but would that even work correctly for a rooted phone? I'm open for any suggestions on what to try at this point.
Did you flashed any ftf file using flashmode
---------- Post added at 12:33 AM ---------- Previous post was at 12:31 AM ----------
zombunny said:
My Sony Xperia z1s just decided to bootloop today for no apparent reason. May be an issue with the 5.0 version it runs? It powers on, shows the Sony screen, then the screen goes blank (black screen, backlit) before going completely to black, then back to the Sony screen again. I'm having a hard time getting Command Prompt to read it, and with this sh***y locked bootloader, I feel like my hands are tied. The phone is rooted, and on stock ROM of course. I'm used to my Huawei and flashing ROMs, fixing soft bricking and whatnot, but it's a factory unlocked device, not this Sony-Tmobile locked carrier crap. I'm less familiar with dealing with this sort of thing. I've already tried pressing down the red button next to the SIM, no dice. I've hard reset using Vol+ and power. Pretty much the extent of what I've done, other than swearing at it. I just want this thing working again, I'm so tired of having to deal with it. First its horrid touchscreen, now this. Running PC Companion seems to be suggested in a lot of places, but would that even work correctly for a rooted phone? I'm open for any suggestions on what to try at this point.
Click to expand...
Click to collapse
Did you flashed any ftf file using flashmode
abdo.war said:
Did you flashed any ftf file using flashmode
---------- Post added at 12:33 AM ---------- Previous post was at 12:31 AM ----------
Did you flashed any ftf file using flashmode
Click to expand...
Click to collapse
I have not. Been afraid to touch it, don't want to make things worse until someone who knows more than me says what my first step should be. Not sure if it's even working correctly, the flashmode led flickers on and off quickly before it goes completely off.
U can use Flashtool without being afraid
I use it always without any error
And yea no problems with led flickers
But be sure to install your drivers on pc before flashing
---------- Post added at 11:17 PM ---------- Previous post was at 11:16 PM ----------
abdo.war said:
Did you flashed any ftf file using flashmode
---------- Post added at 12:33 AM ---------- Previous post was at 12:31 AM ----------
Did you flashed any ftf file using flashmode
Click to expand...
Click to collapse
Don't worry it's safe
abdo.war said:
U can use Flashtool without being afraid
I use it always without any error
And yea no problems with led flickers
But be sure to install your drivers on pc before flashing
---------- Post added at 11:17 PM ---------- Previous post was at 11:16 PM ----------
Don't worry it's safe
Click to expand...
Click to collapse
Been attempting to use it, but it doesn't appear to be working (I have a locked bootloader). Keeps saying 'no loader found for this device'. I've gotten all the drivers that I know of that I'd need for this, for my computer as well as the flashtool drivers (flashmode, fastboot, and common drivers for Rhine board). The phone is stock + locked bootloader, I'm really feeling this thing is headed for the garbage. :/
Hello, I have been reading about this error and everywhere it says it's hard bricked but the phone can enter download mode it's just not recognized by the PC, is the phone dead or is there a way to fix it? Thanks in advance
Search the forum I've seen this thread recently
And start flashing the right files for your phone
i did search for hours and I couldn't find other answer than phone bricked :/ is there a way to make the pc recognize the phone? I installed the drivers as well
http://lgg4unbrick.blogspot.ca/2017/01/unbrick-lg-g4-h811-9008-qualcomm.html?m=1
Don't go backwards this time when flashing firmware on your phone. Has to be recent not older than what you had before
Try that
---------- Post added at 05:50 AM ---------- Previous post was at 05:15 AM ----------
https://forum.xda-developers.com/g4/help/unbrick-lg-g4-h811-9008-qualcomm-t3456417
I think we are having miscommunication issues, the phone can enter download mode just fine, it's just that it's not recognized, it appears like qhsusb_bulk
Yes...it is hard bricked from flashing wrong files that why it appears like so
Follow the guide
Very few posters respond on this board if it already has been posted. I'm posting you what I found by searching
Try LG G4 XDA forum
zeratos said:
I think we are having miscommunication issues, the phone can enter download mode just fine, it's just that it's not recognized, it appears like qhsusb_bulk
Click to expand...
Click to collapse
This is 99 % a driver issue
Sent from my LG-H815 using XDA Labs