Develop Bugs

[Q] Stuck HTC Boot screen

Friend sent me his phone after trying to update to CM and it's getting stuck on the HTC White boot screen. Not sure if it is rooted or not, but was in the processes of rooting when it broke.
Phone is:
HTCDev unlocked
S-On
HBOOT-0.98.0000
RAIDO-1.09.01.0312
Phone will not:
Boot into recovery - HTC White screen
Boot normally - HTC White screen
Update with stock RUU - Bar on the right side fills up and goes back to normal bootloader screen.
Update new recovery - States it takes it but gets stuck on HTC white screen.
ADB Will not show device with "adb devices"
"fastboot oem lock" "FAILED (status read failed (Unknown error)) - "fastboot devices" does find device.
Factory reset - locks up bootloader.
"fastboot clear cache" runs for 30+ minutes phone is unresponsive.
That is about the only information I have any one got any ideas besides use it for a personal safety device and throw it at people?

TheHeffNerr said:
Friend sent me his phone after trying to update to CM and it's getting stuck on the HTC White boot screen. Not sure if it is rooted or not, but was in the processes of rooting when it broke.
Phone is:
HTCDev unlocked
S-On
HBOOT-0.98.0000
RAIDO-1.09.01.0312
Phone will not:
Boot into recovery - HTC White screen
Boot normally - HTC White screen
Update with stock RUU - Bar on the right side fills up and goes back to normal bootloader screen.
Update new recovery - States it takes it but gets stuck on HTC white screen.
ADB Will not show device with "adb devices"
"fastboot oem lock" "FAILED (status read failed (Unknown error)) - "fastboot devices" does find device.
Factory reset - locks up bootloader.
"fastboot clear cache" runs for 30+ minutes phone is unresponsive.
That is about the only information I have any one got any ideas besides use it for a personal safety device and throw it at people?
Click to expand...
Click to collapse
Not exactly sure because I didn't use the HTC DevUnlucky/Unlock, but you can try to S-Off with this: http://forum.xda-developers.com/showpost.php?p=28290187&postcount=2 and see if you can flash a custom rom after gaining S-Off. If you have tried that you will have to wait on someone with a little more experience can help you.

ThePhantom97 said:
Not exactly sure because I didn't use the HTC DevUnlucky/Unlock, but you can try to S-Off with this: http://forum.xda-developers.com/showpost.php?p=28290187&postcount=2 and see if you can flash a custom rom after gaining S-Off. If you have tried that you will have to wait on someone with a little more experience can help you.
Click to expand...
Click to collapse
Oops forgot to put that in there. I've tried the revo s-off but as far as I know the device needs to boot into android to take it. It just sits there waiting for device when I run it. And that needs HBOOT 97 and I'm unable to downgrade
TACOROOT needs ADB and I can't connect with ADB

TheHeffNerr said:
Oops forgot to put that in there. I've tried the revo s-off but as far as I know the device needs to boot into android to take it. It just sits there waiting for device when I run it. And that needs HBOOT 97 and I'm unable to downgrade
TACOROOT needs ADB and I can't connect with ADB
Click to expand...
Click to collapse
Ah, sorry m8, you will have to wait on one of the other more knowledgeable guys jump on to give better advise.

All good, thanks for giving it a shot. If it would lock again stock RUU might work... but no this device hates me lol.

ThePhantom97 said:
Ah, sorry m8, you will have to wait on one of the other more knowledgeable guys jump on to give better advise.
Click to expand...
Click to collapse
Any ideas?

I'm no expert but try re downloading the ruu with the hboot 97 and try it again if you haven't already maybe it was a bad download. I remember when I downgraded mine I tried 3 different files before I got it to work. If you can't find any other ruu flies I'll look on my PC tomorrow and see if I still have the one I got to work and if you're transferring the file to the sd card from a PC leave off the
.zip or it will name it .zip.zip
Sent from my Incredible 2 using xda app-developers app

I think because I can't relock the boot loader it won't let me flash a RUU. But if you could upload the one you got to work that would be amazing none that I find work even with redownloading them
ps I hate that spider....

If the person is htc dev unlock they need to flash a kernal via fastboot for the phone to boot. That's more than likely the reason they are bootlooping. There is a thread in android development about how to flash via htc dev unlock. I would have them read that and proceed.

TheHeffNerr said:
Friend sent me his phone after trying to update to CM and it's getting stuck on the HTC White boot screen. Not sure if it is rooted or not, but was in the processes of rooting when it broke.
Phone is:
HTCDev unlocked
S-On
HBOOT-0.98.0000
RAIDO-1.09.01.0312
Phone will not:
Boot into recovery - HTC White screen
Boot normally - HTC White screen
Update with stock RUU - Bar on the right side fills up and goes back to normal bootloader screen.
Update new recovery - States it takes it but gets stuck on HTC white screen.
ADB Will not show device with "adb devices"
"fastboot oem lock" "FAILED (status read failed (Unknown error)) - "fastboot devices" does find device.
Factory reset - locks up bootloader.
"fastboot clear cache" runs for 30+ minutes phone is unresponsive.
That is about the only information I have any one got any ideas besides use it for a personal safety device and throw it at people?
Click to expand...
Click to collapse
go to bootloader and flash your kernel (stock kernel/custom kernel )
you can get it from your rom.zip
the command would be
fastboot flash boot boot.img
hehehehe i answered after 3 years ! im sure youve solved the problem !

[Q][NOOB] Please help me unbrick my PRIMOC

First post here, please excuse my ignorance. This is a Virgin Mobile HTC One V. I never rooted a phone before, and was just trying to do a basic rooting, and somehow got into trouble. I would like to return the phone to stock and start over.
Right now the phone boots itself into bootloader, and shows me this:
Relocked
Security warning
PRIMOC PVT SHIP S-ON RL
HBOOT-1.57.0000
RADIO-1.00.00.0928
eMMC-boot
Jun 18 2012, 10:22:43
I am able to do this: fastboot getvar cid. The response is this: cid: SPCS_002.
I am also able to do this: fastboot devices. The response is this: FA2AKX405758 fastboot.
I have attempted to use this RUU:
RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed.exe
It gives me error 170, USB connection error (even though I have installed the HTC drivers). I relocked the phone in an attempt to get that RUU to work, but it didn't help. I also tried to extract the rom.zip from the RUU.exe (by finding it in a temp folder, as described on another XDA thread), but the rom.zip acts corrupt. Various zip programs refuse to open it.
Before relocking the phone (in an attempt to get the RUU to work) I tried this:
fastboot flash boot boot.img
I did that with various boot.img files I found via threads here. This just created various problems. One result was that I was in a bootloop. Another result was that I booted to the screen that said "this build is for development purposes only do not distribute outside of htc without written permission." And it would hang there.
Now my condition is that I boot directly to bootloader.
Starting from the beginning: I unlocked the phone using the unlock bootloader procedure at htcdev. No problem. Then I figured I should do a backup right away, so I installed CM Recovery. Right away I knew I had a problem because it did not run correctly. It would present a menu. Then I would select "backup and restore." It would present a splash screen (with the hat) and just hang there. When I pressed power, it would return to the menu. That's when I started trying various other things.
I never got as far as doing anything with superboot or superuser, which is what I thought I was going to do after doing the backup.
I have read a zillion threads here, and tried various things from those threads, but I'm afraid that without specific help I'm just going to make it worse. I'm pulling my hair out, so I hope someone here can help me while I still have a few left. Thanks!

OK, I have made some progress but I'm still pretty stuck.
I have been able to solve two problems I had before. Before when I ran the RUU, it gave me a USB error. And I could not extract recovery.img from the RUU. I solved both those problems by moving to a different PC.
So now I can run the RUU, and it gives me a bunch of progress messages I didn't see before, but at the end it tells me this:
"Error 155, unknown error. The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
So then I tried the procedure described here:
http://forum.xda-developers.com/showpost.php?p=27301573
I unlocked the phone again, and I did this:
fastboot flash recovery recovery_signed.img
I did that using the img file I extracted from the RUU. Then I relocked the bootloader, and I ran the RUU again. But it gave me the exact same error (155).
What should I try next? I notice that the RUU also contains these img files:
system.img
radio.img
boot_signed.img
Should I try flashing those?
Any ideas would be greatly appreciated!
Edit: One more thing. When I ran the RUU, at the end the phone said this:
RUU
Hboot version is older!
Update Fail!

OK, the next thing I tried is the method described here:
http://forum.xda-developers.com/showthread.php?t=1674226
I extracted rom.zip from the RUU, and I renamed it PK76IMG.zip, and I put it on the sdcard, and then I rebooted the phone. The phone found that file and tried to install it, but in the end it gave me the same error message: "Hboot Version is older." On that same screen I see that my current Hboot is 1.57.0000. I guess the RUU contains an older Hboot?
Anyway, that's the same error I get when I run the RUU as an exe.
I notice a couple of people in that thread reported the same problem (Hboot is older), but it's not clear how or if they got around this.
Any ideas?

OK, so here's the next stage in this saga.
Looking around, it seems that there is no RUU for this phone, because I have Hboot 1.57.0000 and radio 1.00.00.0928. I have noticed that people with those specs cannot find a RUU that works, but they have been able to get the phone working with RhythmicRom. I see that discussed here:
http://forum.xda-developers.com/showthread.php?t=2147407
So what I'm trying to do now is install RhythmicRom, but I'm having trouble doing that, I guess because I don't have CM Recovery installed, so the standard recovery is running instead.
I have placed RhythmicRom_v1.4.zip on my sdcard. I am able to boot into bootloader, and I have done factory reset. In the bootloader, I can select Recovery and I see a screen that indicates the phone is looking for something (green circle containing green arrow pointing down, and with a progress bar at the bottom, and an icon of an sdcard). But I guess it doesn't find what it's looking for, and then I see the screen with the red triangle/exclamation mark.
I'm thinking that maybe it will work if on the sdcard I rename RhythmicRom_v1.4.zip to whatever the phone is looking for. Maybe I should rename it to PK76IMG.zip? Just a guess.
Many thanks in advance.

OK, that sort of almost worked. On the sdcard, I renamed RhythmicRom_v1.4.zip to PK76IMG.zip. I booted into bootloader, and it looked like the phone found that file, and loaded it. Then I did this:
fastboot flash boot boot.img
With the boot.img that was inside RhythmicRom_v1.4.zip. Then I rebooted. Now the phone gets to the red animated Virgin Mobile splash screen with the annoying audio. That seems like a good sign, since I haven't seen that in a while. But instead of continuing to boot, then I see the white HTC screen that says "this build is for development purposes only do not distribute outside of htc without written permission." And then it continues to loop between those two screens, so I am stuck in a bootloop. Although I found I was able to interrupt it and get back to the bootloader.
Not sure what to try next. Any suggestions?

Wow, I can't believe you haven't had a single reply.
Ok. First of all.... Use TeamWinRecoveryProject
( TWRP ) as your recovery img
So easy to use
Use fastboot the flash
fastboot flash recovery recovery.img
Then boot into your new touch screen recovery
Now click wipe
Cashe,Dalvick,Factory Reset, System
In that order. It makes sure every thing is wiped thoroughly.
Now navigate to where the Rom is you would like to use and flash it in recovery.
After It's flashed click the wipe cashe/dalvick
Then click home,reboot,bootloader.
Once in bootloader, flash the kernel/bootimg
fastboot flash boot boot.img
After the boot.img is finished,
fastboot reboot
Victory and enjoy the awesomeness of custom ROMs!

P.S. don't forget to unlock your bootloader again. First and foremost
fastboot flash unlocktoken Unlock_code.bin

Russell, thank you for your response. After 24 hours with over 100 views and zero replies, I figured that meant that I had already done the proper steps, and there wasn't some obvious solution I was missing. Although I can see now that I should have tried TWRP. It couldn't have made things worse, and maybe it would have worked better for me than CM Recovery (which seemed to fail as soon as I installed it).
Another key thing was when I figured out that there is no RUU for my specs (because there was an OTA that installed a newer hboot and radio). I like the idea of trying different custom ROMs, but I don't like the idea of never being able to go back to stock, since I would expect that all the custom ROMs have some quirks that I might find unacceptable. But I notice that you have the same hboot and radio, and I assume you have a backup of your stock ROM, so maybe you could have helped me with that.
Anyway, at literally the exact moment that you were posting your comment, I was standing at the UPS counter handing them the phone. If the phone had been working, we would have heard it buzzing inside the box as your email came in! The phone is heading to the HTC repair facility in Houston. They told me they would unbrick it for me for less than $35. I haven't seen anyone else report this, so maybe I was misled and it's too good to be true? We'll see. I don't like being without the phone for a week, but $35 seems like a cheap price to clean up the mess I made.
Anyway, thanks again for speaking up.

Check out the CDMA development thread
Whenever you get your phone back.....
Good luck

I see the thread you're talking about. I just did the download (might as well have it handy). Thank you.

Hope it helped or helps in some way
:beer:
---------- Post added at 02:40 AM ---------- Previous post was at 02:35 AM ----------
I gave you a thanks for first download

Similar problem
Hi,
I had a similar problem. Following this thread I have successfully "unbricked" my phone. My main concern though is activating my phone on VM, which I'm unable to do as I can't go back to stock. I bought the phone as is from craigslist. Any suggestions?
Edit: Internet seems to work though. No go on phone calls or texts, when trying to call this is what I get(Audio):"Account couldn't be verified"

Visit the HTC one v CDMA thread I have a stock rooted Rom there for the taking

Yes, here's the link to that thread:
http://forum.xda-developers.com/showthread.php?t=2321904
It would be interesting to hear if your rom works for cellphoneman.

[Q] Bootlooping with CMRecovery?

I was getting ready to install MIUI v5 when this happened. I was on an older version of Paranoid Android, I'm not too sure which one but it's not the most recent 4.3 one. I tried to boot into clockworkrecovery mod, but now I'm just getting a boot loop. I see the Google symbol with the unlocked lock at the bottom, and then it goes to the Clockwork logo for like 3 seconds. At the bottom it shows the version number, v6.0.4.3, but then it starts to boot again. Right before the logo disappears, the whole screen gets brighter for a split second. How can I fix this?
Any help is much appreciated
Thanks,
jjjnmk

jjjnmk said:
I was getting ready to install MIUI v5 when this happened. I was on an older version of Paranoid Android, I'm not too sure which one but it's not the most recent 4.3 one. I tried to boot into clockworkrecovery mod, but now I'm just getting a boot loop. I see the Google symbol with the unlocked lock at the bottom, and then it goes to the Clockwork logo for like 3 seconds. At the bottom it shows the version number, v6.0.4.3, but then it starts to boot again. Right before the logo disappears, the whole screen gets brighter for a split second. How can I fix this?
Any help is much appreciated
Thanks,
jjjnmk
Click to expand...
Click to collapse
Try flashing recovery again via fastboot
Code:
fastboot flash recovery recovery.img

RajatPatel said:
Try flashing recovery again via fastboot
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I've been looking into that, but I don't have the proper drivers installed on the computer I have with me (which I know is really really dumb). Is there a way to install the drivers even if my phone can only get to fastboot?

jjjnmk said:
I've been looking into that, but I don't have the proper drivers installed on the computer I have with me (which I know is really really dumb). Is there a way to install the drivers even if my phone can only get to fastboot?
Click to expand...
Click to collapse
If you don't know driver stuff, use GNex Root Toolkit. It will guide you to install adb/fastboot drivers.
http://forum.xda-developers.com/showthread.php?t=2208865
http://www.androidrootz.com/2012/08/how-to-get-install-correct-driver-for.html
For basic stuff take a look at this, it's worth to bookmark the following link for future reference:
http://forum.xda-developers.com/showthread.php?t=1828061

Noob Alert: Nexus stuck at 'Google' screen

I looked into updating my 2013 Nexus 7 to Android L yesterday and hit a couple snags. I was using a guide over on nexus7root, mainly for the files and command lines.
I used Nexus Root Toolkit to get the proper drivers installed and to unlock the bootloader. Then I got on with installed L. Command Prompt got stuck at 'Erasing user data' for about an hour. Not a lot I could do but turn it off and try again. It doesn't want to get past that point. I give up for the evening and just try to turn the tablet back on. It gets stuck with 'Google' written on the screen and an unlocked padlock at the bottom. Won't go any further. I go back to NRT and select 'Flash stock and unroot' with 'Soft bricked/bootloop' selected. It whizzes through a little too quickly and my Nexus is still displaying the recovery screen. NRT says it might not have worked and to select 'Force flash mode' and try again. I do that but still no luck.
The tablet will now only display 2 screens: Google with unlocked padlock, or recovery.
Any ideas on what to try next?
Thanks in advance

CasuallyDressed said:
I looked into updating my 2013 Nexus 7 to Android L yesterday and hit a couple snags. I was using a guide over on nexus7root, mainly for the files and command lines.
I used Nexus Root Toolkit to get the proper drivers installed and to unlock the bootloader. Then I got on with installed L. Command Prompt got stuck at 'Erasing user data' for about an hour. Not a lot I could do but turn it off and try again. It doesn't want to get past that point. I give up for the evening and just try to turn the tablet back on. It gets stuck with 'Google' written on the screen and an unlocked padlock at the bottom. Won't go any further. I go back to NRT and select 'Flash stock and unroot' with 'Soft bricked/bootloop' selected. It whizzes through a little too quickly and my Nexus is still displaying the recovery screen. NRT says it might not have worked and to select 'Force flash mode' and try again. I do that but still no luck.
The tablet will now only display 2 screens: Google with unlocked padlock, or recovery.
Any ideas on what to try next?
Thanks in advance
Click to expand...
Click to collapse
You have 2 choices.
1) Start from square 1 and try to install L again using the instructions you have or other instructions that can be found right here on XDA (i wouldnt because you arent installing the actual OTA but rather the developer version which has bugs and such and you will end up having to do number 2 when L comes out anyways.)
2) unbrick your device by reflashing it to stock. there are plenty of ways to do this, look for unbricking on the forums here and you should be ok.
Just a tip for the next time you decide to flash anything if you ever do, make a backup of your entire stock system before doing so, you can do this in the recovery that you install before flashing the new rom. It makes unbricking quite a bit easier.

metalblaster said:
You have 2 choices.
1) Start from square 1 and try to install L again using the instructions you have or other instructions that can be found right here on XDA (i wouldnt because you arent installing the actual OTA but rather the developer version which has bugs and such and you will end up having to do number 2 when L comes out anyways.)
2) unbrick your device by reflashing it to stock. there are plenty of ways to do this, look for unbricking on the forums here and you should be ok.
Just a tip for the next time you decide to flash anything if you ever do, make a backup of your entire stock system before doing so, you can do this in the recovery that you install before flashing the new rom. It makes unbricking quite a bit easier.
Click to expand...
Click to collapse
1) I can't update using the instructions as it hangs at 'Erasing user data'.
2) I've tried to unbrick and flash back to stock using NRT but it just goes back to FlashBoot and never finishes.

Dunno if I'm allowed to, but...
BUMP!!

metalblaster said:
Just a tip for the next time you decide to flash anything if you ever do, make a backup of your entire stock system before doing so, you can do this in the recovery that you install before flashing the new rom. It makes unbricking quite a bit easier.
Click to expand...
Click to collapse
You're absolutely right! Always, always make a backup/nandroid before flashing a different rom. But if you don't and like to live dangerously you should at least have the sdk installed and know how to use adb/fastboot! One thing though about restoring a backup, it does not restore the bootloader. Android L uses bootloader version 4.04 and KitKat uses 4.02. The first L preview used the same bootloader as KK but the new preview does not. I have no idea what kind of bugs or worse would result from restoring a KK nandroid onto the 4.04 bootloader. Maybe nothing but I purposely didn't try to find out if it would cause any problems. Couple nights ago I checked out the preview for maybe an hour then went back to 4.4.4. I flashed the 4.4.4 factory image using a modified flash_all batch file then restored on top of that. I guess I could have instead fastboot flashed the bootloader then went straight into recovery to install my backup. Just something to think about, bootloader versions.
CasuallyDressed said:
1) I can't update using the instructions as it hangs at 'Erasing user data'.
2) I've tried to unbrick and flash back to stock using NRT but it just goes back to FlashBoot and never finishes.
Click to expand...
Click to collapse
You said previously "The tablet will now only display 2 screens: Google with unlocked padlock, or recovery." Unlocked padlock means your bootloader is unlocked and your device now can have images flashed to it. Recovery or bootloader screen? You need to be able to get into the bootloader screen. Press and hold the volume down button, while still holding down the volume button press the power button for a few seconds release the power button and it should go into the bootloader screen. There are a couple toolkits that might help, Wug"s and One-Click Restore come to mind. I've never used them so I wouldn't be any help as far as they go. I can try to help if you want to use the sdk. Do you have the android sdk installed?

i had the same problem , i tried one click restore and it works fine

Wow don'T!!!!
CasuallyDressed said:
I looked into updating my 2013 Nexus 7 to Android L yesterday and hit a couple snags. I was using a guide over on nexus7root, mainly for the files and command lines.
I used Nexus Root Toolkit to get the proper drivers installed and to unlock the bootloader. Then I got on with installed L. Command Prompt got stuck at 'Erasing user data' for about an hour. Not a lot I could do but turn it off and try again. It doesn't want to get past that point. I give up for the evening and just try to turn the tablet back on. It gets stuck with 'Google' written on the screen and an unlocked padlock at the bottom. Won't go any further. I go back to NRT and select 'Flash stock and unroot' with 'Soft bricked/bootloop' selected. It whizzes through a little too quickly and my Nexus is still displaying the recovery screen. NRT says it might not have worked and to select 'Force flash mode' and try again. I do that but still no luck.
The tablet will now only display 2 screens: Google with unlocked padlock, or recovery.
Any ideas on what to try next?
Thanks in advance
Click to expand...
Click to collapse
Don't delete your user data before backing it up!
See WugFreshs Threads on XDA!

So I used ATGAdmin's guide here: http://forum.xda-developers.com/showthread.php?t=2381582
Used "Dead_Nexus7.bat" and it fixed me right up. Plus, I love the "Look you dumb motherf**kers" attitude he has in his video.
I appear to be all sorted anyway! Thanks to those who suggested 'One Click Restore', it set me on the right path.

M8 appears bricked no rom or recovery menu

Tried to remove cynagenmod from my htc and return to stock android settings and messed up somewhere along the line, on powering on my phone it loads straight into the boot loader, navigating to >HBOOT then pressing >RECOVERY makes the HTC logo appear for a moment before returning to the first bootloader screen.
[software status modified, re locked, security warning, M8-UL PVT SHIP S-ON]
The rom has been deleted along with recovery, I am not an expert in using fastboot tried using it for a bit and had no success also tried installing htc sync manager to see if it would help but the installer for the sync manager would crash my computer every time (windows 10). Looking for some help as what to do not sure if it can be fixed or should I bin it thanks.

I would RUU if it was me in your position.

bigmacattack said:
Tried to remove cynagenmod from my htc and return to stock android settings and messed up somewhere along the line
Click to expand...
Click to collapse
To properly troubleshoot where you went wrong, and how to solve it, you will need to describe the exact steps of how you tried to return to stock.
It seems you wiped things in recovery, expecting that to return you to stock? If so, that isn't the case as you now know, without flashing a ROM, TWRP backup, etc.
Similarly, relocking the bootloader renders the phone unable to boot, and wipes the phone; as it expects RUU to be run. But you haven't explained if you were trying to run an RUU, which one, details of your phone version, etc.