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 !
Related
I'm trying to flash a splash screen but I'm getting the following error..
writing 'evosplash1'... FAILED <remote: not allowed>
Any ideas?
you dont normally flash a splash screen ussually you have a file named evosplash1.rgb565 (see if when you open the zip file you have this)
you then place that file in your android sdk/tools directory.
Boot into fastboot and in adb enter the command
fastboot flash splash1 evosplash1.rgb565
once done reboot the phone and you shoudl be set.
_Cooze_ said:
I'm trying to flash a splash screen but I'm getting the following error..
writing 'evosplash1'... FAILED <remote: not allowed>
Any ideas?
Click to expand...
Click to collapse
It's likely you have hboot 0.79, and you need to have hboot .76
when you boot into bootloader, look across the top couple lines, it says something like hboot or eng boot and then the number.
if you have .79 that's why you're getting that error.
Do a search for "splash" there's a lot of threads about this exact issue and how to go from eng boot .79 to .76
Or, click here: http://forum.xda-developers.com/showthread.php?t=752832&highlight=engineering+hboot
or here: http://forum.xda-developers.com/showthread.php?t=769841&highlight=splash
There was actually a good bit of people last night who were also running into this, though we all worked together to figure it out about the hboot version, and now i'm rocking a better then stock splash screen.
tomh1979 said:
There was actually a good bit of people last night who were also running into this, though we all worked together to figure it out about the hboot version, and now i'm rocking a better then stock splash screen.
Click to expand...
Click to collapse
Yeah, I can't even get my computer to recognize my phone while in bootloader.
ADB works fine while in the os, but when i boot into bootloader, no devices show up...it's driving me nuts.
glad to see it finally worked for you guys though.
PLEASE, HELP!!!
I HAD:
OXIGEN 2.1.6, AlphaRev Sense HBOOT S-OFF
after attempt to repair the speaker in service center of HTC, my Desire hangs on splash screen. (nothing was repaired, changed etc., but as far as I understand, they tried to flash something)
SO, NOW I HAVE:
Desire of the same phisical condition, but:
If normally to boot - I've seen only splash screen.
If to boot into bootloader - it's started, fastboot working, but option RECOVERY doesn't work - if to choose it, phone goes to reboot and hangs on splash screen again.
I tried to root the phone again, but step2 doesnt work, because "device not found" (although all the drivers are installed and are working normally)
After that 1st step of rooting, the normal boot goes directly to bootloader.
I tried to re-flash Recovery with fastboot-windows, but got the error:
FAILED (remote: siignature verify fail)
So, as far as I understand, phone not dead yet, but I can't call it alive as well.
PLEASE, help!
I do have more or less the same problem!! in my case I take out the battery for some minutes, put it back again and hopefully the phone turns on normally, but as soon as I turn WIFI on or watch a video it turns off by itself and wouldn't reboot again.
I posted a help demand on a topic called CDMA Desire fully flashed to Cricket!! wait for tha answer with me if you want, these guys seem to know what they're talking about and we'll see what to do..
AndrewMe said:
PLEASE, HELP!!!
I HAD:
OXIGEN 2.1.6, AlphaRev Sense HBOOT S-OFF
after attempt to repair the speaker in service center of HTC, my Desire hangs on splash screen. (nothing was repaired, changed etc., but as far as I understand, they tried to flash something)
SO, NOW I HAVE:
Desire of the same phisical condition, but:
If normally to boot - I've seen only splash screen.
If to boot into bootloader - it's started, fastboot working, but option RECOVERY doesn't work - if to choose it, phone goes to reboot and hangs on splash screen again.
I tried to root the phone again, but step2 doesnt work, because "device not found" (although all the drivers are installed and are working normally)
After that 1st step of rooting, the normal boot goes directly to bootloader.
I tried to re-flash Recovery with fastboot-windows, but got the error:
FAILED (remote: siignature verify fail)
So, as far as I understand, phone not dead yet, but I can't call it alive as well.
PLEASE, help!
Click to expand...
Click to collapse
Please do not post the SAME problem in two different forums.
Ok, but can you help us out here!!??? can you also check my post on the other subject and see if you know what to do??
HTC_DeSiRe_83 said:
Ok, but can you help us out here!!??? can you also check my post on the other subject and see if you know what to do??
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=15819219&postcount=6
I followed your instructions, I flashed the phone but still getting the same problem ( cam not working and it's not a SD Card matter and more seriously the phone reboots bu itself)... any ideas what to do??
thanks
HTC_DeSiRe_83 said:
I followed your instructions, I flashed the phone but still getting the same problem ( cam not working and it's not a SD Card matter and more seriously the phone reboots bu itself)... any ideas what to do??
thanks
Click to expand...
Click to collapse
Seems to be a hardware issue. Give htc a ring.
So... I am gone try and put my question in this post as detailed as I can... And I really hope that someone can help...
I have an HTC Wildfire S (Marvel, bought in Denmark) that had 2.2.1, I wanted to use ICS on it and so I started researching for a good ICS ROM. My phone had the below,
Marvel S HTC Europe
HBoot 1.09.0099
2.26.401.3 Radio 47.23e.35.3038H 7.57.39.10M
I decided to flash the below ROM,
Paranoid Android pa_marvel-1.6a-beta1-24AUG2012-142650
My steps were the following,
1. Went on HTCDEV.com and unlocked the bootloader
2. I downloaded the necessary SDK files on a folder on C drive (adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll & fastboot.exe) I then used the following command to flash a recovery “fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img”, this was a ClockWorkMod official recovery.
3. When I tried to access the recovery it seems that it was ok but I had a black screen with the tactile buttons switched on for about a minute and then it booted... I research in XDA and I found a solution... the following.... http://forum.xda-developers.com/showthread.php?t=1781105 it is a small jave software that enables you PC screen to display your htc screen when it is black to actually see what is happening... this saved me!!!!!! Thanks to “rajanand”....
4. After I managed to see my recovery on my PC screen I flashed Paranoid Android... doing always the norm of Wiping Data, Cache and Dalvik first.
5. When I tried booting I only got the HTC White Screen logo and nothing else... (PANIC!!!) I assumed there was something wrong with the ROM.
6. I then flashed CM9 from Alquez... doing always the norm of Wiping Data, Cache and Dalvik first.
7. When I tried booting I only got the HTC White Screen logo and nothing else... (PANIC AGAIN!!!)
8. I then decided to put it back to its original state by running the official RUU of the phone by downloading it from here http://forum.xda-developers.com/showthread.php?t=1074445
9. When I run the RUU, but first I relocked the bootloader with the following command in the bootloader “fastboot OEM Lock”, (RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed), the phone got an error 140, meaning that my bootloader was a higher version... and the is not other RUU which is higher than this... so I was a bit stuck and confused as to how this happened.
10. I WAS REALLY NERVOUS...
11. I then read a post from someone, I can’t remember saying that only EQDKP ROMs worked for him.
12. I unlocked the bootloader again using the same key when I unlocked it the first time. Keep it.
13. And I flashed the following, [Drk_mod]EQDKPv4.9_multi_deodexed_mhr.zip, and finally my phone booted in the ROM and it is currently working...
See below a screen shot from the Java program and my cwd... it seems that this ROM things a bit different when flashing things or is this a misunderstanding...
Can anyone explain why NO OTHER ROM is working?
Last night i try to install the Android Revolution rom for HTC one x, and Now It turned to one chaos,
The AR rom got installed, I try to open it up and it got stuck, then I reinstall it, and then it didn't go well, somehow it got stuck until no battery and now it also by mistake got locked.
There's a way to get out from the bootloader with the msg in the top "SECURITY WARNING - RELOCKED",
How I can unlock it again ?
dablogmusic said:
Last night i try to install the Android Revolution rom for HTC one x, and Now It turned to one chaos,
The AR rom got installed, I try to open it up and it got stuck, then I reinstall it, and then it didn't go well, somehow it got stuck until no battery and now it also by mistake got locked.
There's a way to get out from the bootloader with the msg in the top "SECURITY WARNING - RELOCKED",
How I can unlock it again ?
Click to expand...
Click to collapse
Reflash the unlock code you got from HTC.
1)Put the phone in fastboot mode and connect it to the computer.
2) place the unlock_code.bin in your fastboot folder.
3) open cmd. Navigate to your fastboot folder
4) use this command -
fastboot flash unlocktoken Unlock_code.bin
5) your phone should be unlocked
P.S.- you need the battery to be above 30% to unlock the bootloader. So charge it first.
Sent from my HTC One X using xda app-developers app
Hello All,
I am looking for some advice to get my phone working again.
I have a modified bootloader and S-Off.
When choose the recovery option in the bootloader it goes back to HBOOT after showing a brief android screen that mentions something about a development build. The phone does try to boot but gets stuck on the HTC logo screen. From what I can tell I have no OS installed and no longer have a recovery. I am also unable to get abd working since i cant enable usb debugging etc.
Any tips?
Thanks,
Matt
Were you doing something to the phone that led to this condition? If so, list those steps in as much detail as possible.
-AxeCain said:
Hello All,
I am looking for some advice to get my phone working again.
I have a modified bootloader and S-Off.
When choose the recovery option in the bootloader it goes back to HBOOT after showing a brief android screen that mentions something about a development build. The phone does try to boot but gets stuck on the HTC logo screen. From what I can tell I have no OS installed and no longer have a recovery. I am also unable to get abd working since i cant enable usb debugging etc.
Click to expand...
Click to collapse
ADB only works within the Android operating system, however, as you noted, you have no OS. Instead, what you need is fastboot - which, if you can get HBOOT to come up, you have. There are several "kits" with fastboot versions, or you can download the full SDK, which will have it. It is similar to ADB, but operates at the bootloader level instead.
1) Since you are S-off, and presumably bootloader unlocked, just flash a new recovery from fastboot. From there, install a new ROM/nandroid from your SD card.
2) If you aren't bootloader unlocked, boot (rather than install) TWRP, and use the ADB bridge mode to manually reset the lock state using Scotty's thread. Then go back to #1
3) Or, if you haven't altered your CID/MID, just re-run an RUU and put it all back to a known state. (assuming there is an RUU for your CID/MID)
These aren't detailed instructions, but there are several threads relating to each tip in the forum.