Develop Bugs

Bricked HTC One

I have my One s-off and the other day I flashed the stock 4.3/Sense 5.0 ROM and the stock recovery thinking I would be fine to accept the OTA. Yesterday the OTA came and I accepted the download and told it to install. It got 3/4 done with the install and then threw the red exclamation mark inside of a triangle. I can not boot my phone past the HTC screen and I do not have a custom recovery installed. I can boot into the bootloader, but when I try fastboot commands my computer just says waiting for device indefinitely and makes no noise when I plug my phone in, which leads me to believe the computer isn't recognizing it. I tried preforming a factory reset, but that did not solve anything. Oddly enough, I had my phone turned off overnight, but this morning at 7am it turned itself back on and sat at the HTC screen. I had an alarm set for 7am so this gave me hope as it still remembers that.
Any advice would be much appreciated!

Same situation here. Kitkat OTA bricked my Verizon HTC one. I'm S-off/unlocked with base rom. I can get to bootloader and can run fastboot, but can't seem to be able to find RUU for Verizon HTC one. Anyone can help?

smallwei said:
Same situation here. Kitkat OTA bricked my Verizon HTC one. I'm S-off/unlocked with base rom. I can get to bootloader and can run fastboot, but can't seem to be able to find RUU for Verizon HTC one. Anyone can help?
Click to expand...
Click to collapse
I was able to get my computer to recognize my phone, flash TWRP through fastboot, and then boot into TWRP to sideload the stock 4.4.2/Sense 5.5 ROM.

Banished Angel said:
I was able to get my computer to recognize my phone, flash TWRP through fastboot, and then boot into TWRP to sideload the stock 4.4.2/Sense 5.5 ROM.
Click to expand...
Click to collapse
How did you sideload the ROM? (I have CWM recovrey... should I change to TWRP?) Can you help me out with steps you took? Thanks much!
---------- Post added at 06:53 PM ---------- Previous post was at 06:34 PM ----------
smallwei said:
How did you sideload the ROM? (I have CWM recovrey... should I change to TWRP?) Can you help me out with steps you took? Thanks much!
Click to expand...
Click to collapse
I think I got it. Here is the instruction for sideloading. Going to give it a shot now. Thanks much!
http://forum.xda-developers.com/showthread.php?t=2317986

first off. this is not a brick. Brick means the phone is a brick screen doesn't turn on cant do anything if you can get to hboot you have a chance.
im guessing it loaded everything onto you phone but hboot and the system itself. what you can do is this.
fastboot flash recovery *.img
(* cwm, twrp, phils)
fastboot reboot-bootloader
enter recovery
if you can get in recovery, flash a rom that is 4.4.2 only (in case some or all the firmware was installed)
if you cant get into recovery you will need to return the bootloader to lock status and run the RUU

I put my phone in a nice black screen of death bootloop. All because of CWMR. After 1 hr of pulling my hair out trying to get back to bootloader, I managed and flashed TWRP. After that, everything was easy as pie. I think that is the last time I use CWMR.

adb push
Dont forget that both recovery will allow adb push if you can get there.. Just adb push your zip to your m7.. On liunx it looks something like this....
Code:
[email protected] ~ $ adb devices
List of devices attached
FA395S900356 recovery
[email protected] ~ $ adb push test.zip /sdcard/0/
5358 KB/s (183834805 bytes in 33.504s)
[email protected] ~ $

zalez said:
I put my phone in a nice black screen of death bootloop. All because of CWMR. After 1 hr of pulling my hair out trying to get back to bootloader, I managed and flashed TWRP. After that, everything was easy as pie. I think that is the last time I use CWMR.
Click to expand...
Click to collapse
yeah, my One didnt like CWMR at all from day one. :crying:

Had the same issue yesterday. As described. I just a thread I posted in help just yesterday, and pulled the error from manually flashing the ota .zip with via stock recovery.
I had no solution, and just waited for Santod and flashed.
Now I also got the black screen. You can get back to boot loader, not easily, but you can.
if I have helped you please press the thanks button.

[Q] HELP!! Deleted OS!!

Hi guys so I've managed to accidentally bricked my phone and I've been trying to find a way to fix it for days. It's driving me NUTS!!!
So I was trying to install the Harman Kardon feature on my phone buy unlocking it but failed to turn the S-Off. I was following a couple of youtube videos which told me to go to TWRP and wipe all my memory and forgetting to inform the viewers to back everything up until after the video. It's still my fault but my phone is stuck on the logo screen when I try to turn it on which means I deleted the OS. PLEASE HELP!!!
My phone is in this status right now
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1/19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 2 2014,00:28:44.0
My computer won't even recognize my phone when its connected to my pc. I absolutely love this phone and if I can fix it, that'll be ****ing out of this world.

Unlock bootloader using your Unlock_code.bin from htc.
Flash custom recovery
Root
Flash rom
Done!!
clown6198 said:
Hi guys so I've managed to accidentally bricked my phone and I've been trying to find a way to fix it for days. It's driving me NUTS!!!
So I was trying to install the Harman Kardon feature on my phone buy unlocking it but failed to turn the S-Off. I was following a couple of youtube videos which told me to go to TWRP and wipe all my memory and forgetting to inform the viewers to back everything up until after the video. It's still my fault but my phone is stuck on the logo screen when I try to turn it on which means I deleted the OS. PLEASE HELP!!!
My phone is in this status right now
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1/19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 2 2014,00:28:44.0
My computer won't even recognize my phone when its connected to my pc. I absolutely love this phone and if I can fix it, that'll be ****ing out of this world.
Click to expand...
Click to collapse

stathis95194 said:
Unlock bootloader using your Unlock_code.bin from htc.
Flash custom recovery
Root
Flash rom
Done!!
Click to expand...
Click to collapse
I got the code and everything but when I connect my phone to the pc. It just makes a noise saying it's connected but I can't do anything.

clown6198 said:
I got the code and everything but when I connect my phone to the pc. It just makes a noise saying it's connected but I can't do anything.
Click to expand...
Click to collapse
so what's the output of:
adb devices
Edit: You don't have an OS so adb won't work. Try fastboot devices

Yet another user stuck because they followed a tutorial or video guide, instead of taking the time to learn, read, and really understand the steps and concepts. This is exactly why I discourage such tutorials or YouTube guides (and Toolkits as well), as they leave you completely unequipped to recover if you have a problem, leaving your buddies at XDA to clean up the mess.
YouTube video or not, you shouldn't be doing anything you don't understand, and you shouldn't be wiping anything if you don't understand what the result will be.
You will need to troubleshoot the USB connectivity issue first. From there, unlock the bootloader again, install custom recovery and flash a ROM (as stathis95194 has already stated).

stathis95194 said:
so what's the output of:
adb devices
Edit: You don't have an OS so adb won't work. Try fastboot devices
Click to expand...
Click to collapse
So I managed to Unlock my phone again through fastboot via cmd and I have twrp installed. I have no idea how to flash a ROM. If you can help me with that, I'll be forever in your dept

clown6198 said:
So I managed to Unlock my phone again through fastboot via cmd and I have twrp installed. I have no idea how to flash a ROM. If you can help me with that, I'll be forever in your dept
Click to expand...
Click to collapse
Either adb push the desired ROM file to the phone's memory, or put a ROM on a removable SD using a card reader (connected to your computer). Then boot into TWRP, select Install, and find the ROM file and flash it.

redpoint73 said:
Either adb push the desired ROM file to the phone's memory, or put a ROM on a removable SD using a card reader (connected to your computer). Then boot into TWRP, select Install, and find the ROM file and flash it.
Click to expand...
Click to collapse
will this work even with the S-ON?

clown6198 said:
will this work even with the S-ON?
Click to expand...
Click to collapse
Of course. I wouldn't be telling you to do it, otherwise.

redpoint73 said:
Of course. I wouldn't be telling you to do it, otherwise.
Click to expand...
Click to collapse
sorry, so I did send you a message saying if fixed this problem but I guess it didnt. I managed to put a rom in my phone through cmd and I swiped install and goes through the whole installing process. But when I reboot my phone after the installation, it's still stuck in the HTC logo and when I go back to the bootloader, the OS is still empty. What do I do!!!

Honestly, I would just install Philz recovery instead of TWRP and try to either install the ROM zip directly (after a full wipe), or sideload the ROM zip from your PC.

clown6198 said:
sorry, so I did send you a message saying if fixed this problem but I guess it didnt. I managed to put a rom in my phone through cmd and I swiped install and goes through the whole installing process. But when I reboot my phone after the installation, it's still stuck in the HTC logo and when I go back to the bootloader, the OS is still empty. What do I do!!!
Click to expand...
Click to collapse
Hmm. It looks like you're on the old radio. If that's the case and you downloaded a ROM based off of the 2.x firmware, you'll get a solid 10 minute boot time. Find a ROM for your device that is based off of the 1.x firmware and download that. To get your device out of the bootloop and back into boot loader/recovery, hold power and volume up for quite some time until the screen shuts off. Then, hold power down while the screen is black and you'll be in the boot loader. From there you can use the arrow keys to select recovery. Of it isn't there, first select fastboot or hboot and look for it there. You should be in recovery, now you can go ahead and push the file to your phone. Ensuring it is a sense ROM based off of the 1.x firmware, go to wipe and do the standard swipe to wipe (will erase app data not pictures or downloads), then go into install and select your ROM and swipe. Be patient while your device turns on for the initial boot, it might take a while but your phone should be functional after that.

wtoj34 said:
Hmm. It looks like you're on the old radio. If that's the case and you downloaded a ROM based off of the 2.x firmware, you'll get a solid 10 minute boot time.
Click to expand...
Click to collapse
That was my initial thought as well (long boot time due to outdated 1.xx firmware) but the hboot and radio number given in post #1 indicate that OP seems to be on 2.xx firmware.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
clown6198 said:
sorry, so I did send you a message saying if fixed this problem but I guess it didnt. I managed to put a rom in my phone through cmd and I swiped install and goes through the whole installing process. But when I reboot my phone after the installation, it's still stuck in the HTC logo and when I go back to the bootloader, the OS is still empty. What do I do!!!
Click to expand...
Click to collapse
What ROM did you try?
How long did you wait for the phone to boot? First boot after flashing a ROM will take a while, maybe 5 minutes or so.
OS not indicated on the bootloader screen doesn't mean anything (doesn't necessarily indicate a problem with the OS not installed). Its a known bug, and might be blank even if the OS is present.
As previous replies suggest, try a different ROM or another recovery (Philz/CWM).
Also, make sure you do the default wipe in TWRP (which wipes Dalvik, cache, and data) before flashing any ROM (and likewise in CWM). Other partitions do not need to be wiped (in particular, don't wipe Internal Storage, as you will lose the ROM you just pushed to the phone), but failure to wipe data in itself can cause failure to boot.

redpoint73 said:
That was my initial thought as well (long boot time due to outdated 1.xx firmware) but the hboot and radio number given in post #1 indicate that OP seems to be on 2.xx firmware.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
What ROM did you try?
How long did you wait for the phone to boot? First boot after flashing a ROM will take a while, maybe 5 minutes or so.
OS not indicated on the bootloader screen doesn't mean anything (doesn't necessarily indicate a problem with the OS not installed). Its a known bug, and might be blank even if the OS is present.
As previous replies suggest, try a different ROM or another recovery (Philz/CWM).
Also, make sure you do the default wipe in TWRP (which wipes Dalvik, cache, and data) before flashing any ROM (and likewise in CWM). Other partitions do not need to be wiped (in particular, don't wipe Internal Storage, as you will lose the ROM you just pushed to the phone), but failure to wipe data in itself can cause failure to boot.
Click to expand...
Click to collapse
Hi so Im in TWRP. I pushed a ROM called Android_Revolution_HD-One_M8_11.1 which is supposedly the closest rom to a stock one. I tried flashing the ROM many times, Im in the process of flashing it again after whiping like you said. The result is the same. After the installation, the phone goes back into TWRP for a slip second and the screen just phases out and turns off. After that, I have to reboot the phone into bootloader again. No luck in getting the OS started. If you guys can recommend me a ROM to try out that's based off of 1.x like the PHILZ one with a link. that'll be awesome
Thanks,
clown6198

clown6198 said:
After the installation, the phone goes back into TWRP for a slip second and the screen just phases out and turns off. After that, I have to reboot the phone into bootloader again. No luck in getting the OS started. If you guys can recommend me a ROM to try out that's based off of 1.x like the PHILZ one with a link. that'll be awesome
Click to expand...
Click to collapse
I don't think the ROM being 1.x based versus 2.x is your issue. The radio number and hboot number you listed in Post #1 indicate you are on firmware compatible with 2.x ROMs. Being on outdated firmware doesn't cause the issue you describe, anyway. With outdated firmware, the ROM will still boot but just stalls for a long time (10 minutes) on the HTC screen before booting properly.
PhilZ is a recovery, not a ROM. You can find it (and a great many other useful things) on this thread sticky at the top of the General section:
http://forum.xda-developers.com/showthread.php?t=2694600
I'd try adb wipe cache, then flash TWRP again, or install Philz CWM recovery. Then try to flash the ROM again.
You can also try to download the ROM again to make sure it wasn't corrupted during download. The adb push went okay with no errors?
You can also try one of the stock backups from the collection (adb push to phone and Restore using the appropriate recovery TWRP or PhilZ): http://forum.xda-developers.com/showthread.php?t=2701376
We're getting very close, hang in there.

redpoint73 said:
That was my initial thought as well (long boot time due to outdated 1.xx firmware) but the hboot and radio number given in post #1 indicate that OP seems to be on 2.xx firmware.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
What ROM did you try?
How long did you wait for the phone to boot? First boot after flashing a ROM will take a while, maybe 5 minutes or so.
OS not indicated on the bootloader screen doesn't mean anything (doesn't necessarily indicate a problem with the OS not installed). Its a known bug, and might be blank even if the OS is present.
As previous replies suggest, try a different ROM or another recovery (Philz/CWM).
Also, make sure you do the default wipe in TWRP (which wipes Dalvik, cache, and data) before flashing any ROM (and likewise in CWM). Other partitions do not need to be wiped (in particular, don't wipe Internal Storage, as you will lose the ROM you just pushed to the phone), but failure to wipe data in itself can cause failure to boot.
Click to expand...
Click to collapse
redpoint73 said:
I don't think the ROM being 1.x based versus 2.x is your issue. The radio number and hboot number you listed in Post #1 indicate you are on firmware compatible with 2.x ROMs. Being on outdated firmware doesn't cause the issue you describe, anyway. With outdated firmware, the ROM will still boot but just stalls for a long time (10 minutes) on the HTC screen before booting properly.
PhilZ is a recovery, not a ROM. You can find it (and a great many other useful things) on this thread sticky at the top of the General section:
http://forum.xda-developers.com/showthread.php?t=2694600
I'd try adb wipe cache, then flash TWRP again, or install Philz CWM recovery. Then try to flash the ROM again.
You can also try to download the ROM again to make sure it wasn't corrupted during download. The adb push went okay with no errors?
You can also try one of the stock backups from the collection (adb push to phone and Restore using the appropriate recovery TWRP or PhilZ): http://forum.xda-developers.com/showthread.php?t=2701376
We're getting very close, hang in there.
Click to expand...
Click to collapse
ahahaha THANK you so much!!!! I got the phone to work but now the problem is, I cant get the sound to work when Im playing music. I installed the harman kardon software and I cant get the music to work at all

clown6198 said:
I installed the harman kardon software and I cant get the music to work at all
Click to expand...
Click to collapse
I believe you need appropriate firmware in order to run the HK mod. Not sure where this is discussed, but I've seen it mentioned a few times. Try searching the thread where you go the HK mod.
Just curious, what steps did you take exactly, to get the booted?

redpoint73 said:
I believe you need appropriate firmware in order to run the HK mod. Not sure where this is discussed, but I've seen it mentioned a few times. Try searching the thread where you go the HK mod.
Just curious, what steps did you take exactly, to get the booted?
Click to expand...
Click to collapse
Damn. Apparently I need to get s-off in order for the harman kardon to work. Just need to uninstall harman kardon now... But yea sorry all I needed was to flash the rom. I didn't know the booting was going to take 5 mins and over. I thought that I was just stuck on the HTC logo. all I needed was to be patient ahaha Thanks a lot guys

[Q] reflashing bootloader 2013 LTE

Hi all, my nexus is a very poorly little thing at the moment. Bootloops on the google screen on start and can't get to recovery from the bootloader. I have tried flashing with a stock rom but it is still bootlooping. I'm assuming the next step is to try flashing the bootloader, something I'm very scared of doing without being absolutely sure that I'm not about to turn my critically ill nexus into a completely dead nexus. Could anyone give me the exact commands I need to use to do this?

cthulhu_tentacles said:
Hi all, my nexus is a very poorly little thing at the moment. Bootloops on the google screen on start and can't get to recovery from the bootloader. I have tried flashing with a stock rom but it is still bootlooping. I'm assuming the next step is to try flashing the bootloader, something I'm very scared of doing without being absolutely sure that I'm not about to turn my critically ill nexus into a completely dead nexus. Could anyone give me the exact commands I need to use to do this?
Click to expand...
Click to collapse
I think all you need to do is reflash the recovery. Your bootloader may be fine. Did you accidentally erase your recovery partition? What were you doing when you first saw the problem?

DroidIt! said:
I think all you need to do is reflash the recovery. Your bootloader may be fine. Did you accidentally erase your recovery partition? What were you doing when you first saw the problem?
Click to expand...
Click to collapse
I didn't do anything unusual. Went to sleep. Woke up in the morning and it was frozen. Gave it a long press on the power key and has been stuck ever since. Just tried the one-click restore here http://forum.xda-developers.com/showthread.php?t=2381582 and it is still bootlooping after that.

OK, I'd download a recovery to your computer and fast boot flash it that way. I've not used that tool, but I did the same once. I accidentally erased my recovery partition. So I just redownloaded the latest twrp .IMG and did fast boot flash recovery and all was fine. That's what I'd suggest for a start.
---------- Post added at 10:13 PM ---------- Previous post was at 10:10 PM ----------
Ah I see, that tool wipes your entire device. So I'd go here https://developers.google.com/android/nexus/images and download the latest factory image. While in your boot loader, connect to your computer and run the .bat file from the download. That all return you to stock. Be patient it takes some time, but that should solve your issue.

Thanks, giving it a shot now

Yep, download, unzip, connect to computer while in bootloader, and double click the .bat file. It will go through a series of flashings. It's restoring everything to factory. Just leave it plugged in until it starts to boot up. ?

OMG,i am so lost!

tried to get OTA 5.0.1 today. woudn't take. I have (had)rooted,s-off,bootloader unlocked. Now i somehow wiped everything off.No OS, no recovery. No idea how to begin again. Screen is on white with HTC logo and Powered by android showing. won't power down. Any ideas?

Try holding volume up with power button down for ten seconds.
---------- Post added at 03:47 PM ---------- Previous post was at 03:46 PM ----------
Are you sure you wiped everything, or are you just assuming this based on the screen you are seeing?

update
ok, i held power up/power for 20 seconds, then power down/power and got into twrp recovery. there is NOTHING else on the phone. No OS at all. what's the best way to proceed? PC wont pickup device,so adb cmd prompt isn't working. thanks

stlsports said:
ok, i held power up/power for 20 seconds, then power down/power and got into twrp recovery. there is NOTHING else on the phone. No OS at all. what's the best way to proceed? PC wont pickup device,so adb cmd prompt isn't working. thanks
Click to expand...
Click to collapse
What I would do is pop out my MicsoSD card, back everything up on it then download my original OS I WAS running before I blew it up onto the SD card and attempt to flash it. From there I'd hit up this thread http://forum.xda-developers.com/showthread.php?t=2714456 to see if I could glean how to return back to stock. I'm sure someone will yell at me if you shouldn't do it, not that am I saying you should do that, I'm just saying what I'd do.

i was able to get lollipop dream on my sd card and flash it. WHEW! but, i really want stock rooted lollipop. i actually enjoy sense 6.0 a little bit. gonna keep at it..
thanks.
Theoriginalgiga said:
What I would do is pop out my MicsoSD card, back everything up on it then download my original OS I WAS running before I blew it up onto the SD card and attempt to flash it. From there I'd hit up this thread http://forum.xda-developers.com/showthread.php?t=2714456 to see if I could glean how to return back to stock. I'm sure someone will yell at me if you shouldn't do it, not that am I saying you should do that, I'm just saying what I'd do.
Click to expand...
Click to collapse

stlsports said:
i was able to get lollipop dream on my sd card and flash it. WHEW! but, i really want stock rooted lollipop. i actually enjoy sense 6.0 a little bit. gonna keep at it..
thanks.
Click to expand...
Click to collapse
Well now that you're up and running, you can go through the process of flashing the old stock rom (not the lollipop rom), unroot and restore the stock BL, then take the OTA update and I believe you should be able to reroot if you wanted to.

Theoriginalgiga said:
Well now that you're up and running, you can go through the process of flashing the old stock rom (not the lollipop rom), unroot and restore the stock BL, then take the OTA update and I believe you should be able to reroot if you wanted to.
Click to expand...
Click to collapse
couldn't he just flash the most current RUU?

deepsouth06 said:
couldn't he just flash the most current RUU?
Click to expand...
Click to collapse
Maybe, I'm not sure. I was able to because I was coming from just the stock rom rooted with xposed on it I know that at the least BL needs to be stock and match the version of stock ROM you nandroided back on. If you're using RUU I don't think unrooting is important. Whether or not you have to lock the BL I'm not aware of myself but it's an easy process. Below is what I did.
Being on a rooted stock ROM running xposed I downloaded drivers, BL that matched my ROM, ADB/fastboot current RUU I was on and latest RUU.
I was on 4.4.4, I verified the version of my ROM and got the matching BL. I've heard rumors that mismatching BL/ROM will cause an error.
FIRST I booted into my custom recovery and did a back up. Better safe than sorry right?
booted into fastboot and installed the recovery using fastboot flash recovery {recoveryname}.img
locked BL using "fastboot oem lock" rebooted my phone into the OS then fired up the latest[/B ]RUU and let it run and it ran just fine.
I then unlocked my BL again and installed the latest version of TWRP, reinstalled root and my apps. phone runs really well. I need to start going through and freezing apps but hey we skip those things at 2am don't we?
Mind you I have S-off on my phone and I didn't mess with S-off at all.
I would surmise that if you're experiencing getting the latest RUU to install that you might want to make sure your BL and rom number match and if that doesn't work try flashing the RUU that you're currently running and then the latest RUU.
I consulted this list to verify my version I was running, I happened to be running at the time 3.32.531.2 so I hunted for that BL.
https://support.t-mobile.com/docs/DOC-10366

[ATT] Probably bricked my device

So the old ROM I was on (a super outdated Android Revolution) needed to be updated because my battery was draining a lot and I figured I would update everything. Apparently I flashed a bad or wrong version of TWRP, so I can't get into recovery. It just sits there trying to get into recovery but it keeps failing. Then I tried using MultiRom recovery and installing that through the app in the play store. Now my phone won't go into recovery and just boot loops. I can get into the HBOOT menu but I can't get into recovery or boot the device at all. Does anyone have any ideas to get a working recovery or working ROM? I already backed up my pictures and videos and stuff, but I forgot to transfer my titaniumbackup files I've been trying to look around and see how to fix it but I don't want to do something that will cause more damage than I've already done. I did all this to update my firmware so that I can use the newer ROMs. Anyway if anyone has any ideas I'm all ears.
Thanks in advance.

You didn't mention whether or not you are S-off and/or bootloader unlocked.
Since you already have a custom ROM, you must have unlocked your bootloader at some point, so if it is STILL unlocked, just reflash the correct recovery from fastboot. If it is not, unlock it with HTCdev first, then reflash the correct recovery.
Alternately, if you just want the phone fixed, you can always re-run the AT&T RUU - though that will trash any files you have on the phone.

Yeah that's what I did yesterday thanks for the response!