[Q] Sensation not turning on after crash+bootloader unlock

[Sverrebob]

So, where to start?

I'll start with my broken screen:

1 -new screen ordered (complete assembled LED+digitizer)
2 -installed the new screen, put phone back together and turned ON
3 -phone immidiately went into bootloop!
4 -did some google research and found this site and figured out how to get into bootloader (vol down+pwr)
5 -bootloader works fine, but left it on too long with phone not on charger (battery might have died?) phone not turning on and red LED blink while in charger
6 -ordered new battery, it arrived today. Phone got back on and into bootloader.
7 -unlocked bootloader by using the HTCDEV com site, and their method. worked fine!
8 -then turning phone back on after a failed restart after the bootloader unlock, and it wont turn on taking me back to stage 5

The phone was connected via usb during the bootloader unlock and the restart after. But I never got it back on

There is one thing I am curious about aswell - the phone get very hot around the SD-card slot and it smells warm electronics. I dont know if this is normal but I cant say I noticed this before when the phone was working. I am very sure that I re-assembled the phone correctly after replacing the LED+digitizer as both these parts came to me already assembled.So only thing I did was removing the screen case with the LED and digitizer and replacing it with the new one.

I really hope anyone have ANY input on this as I would really like to get my phone back on and working so I can root it.

 

[ahsan64]

So, where to start?

I'll start with my broken screen:

1 -new screen ordered (complete assembled LED+digitizer)
2 -installed the new screen, put phone back together and turned ON
3 -phone immidiately went into bootloop!
4 -did some google research and found this site and figured out how to get into bootloader (vol down+pwr)
5 -bootloader works fine, but left it on too long with phone not on charger (battery might have died?) phone not turning on and red LED blink while in charger
6 -ordered new battery, it arrived today. Phone got back on and into bootloader.
7 -unlocked bootloader by using the HTCDEV com site, and their method. worked fine!
8 -then turning phone back on after a failed restart after the bootloader unlock, and it wont turn on taking me back to stage 5

The phone was connected via usb during the bootloader unlock and the restart after. But I never got it back on

There is one thing I am curious about aswell - the phone get very hot around the SD-card slot and it smells warm electronics. I dont know if this is normal but I cant say I noticed this before when the phone was working. I am very sure that I re-assembled the phone correctly after replacing the LED+digitizer as both these parts came to me already assembled.So only thing I did was removing the screen case with the LED and digitizer and replacing it with the new one.

I really hope anyone have ANY input on this as I would really like to get my phone back on and working so I can root it.

Pull out the battery then place again and after that try to go into bootloader ..
Also phone showing red light while charging ?

 

[Sverrebob]

Pull out the battery then place again and after that try to go into bootloader ..
Also phone showing red light while charging ?

I let the phone cool down (it get's very hot very fast!) and removed battery and replaced it again, phone ON and in bootloader now, thanks

The heat issue still remains tho, I wonder if this might be the source of this unstable situation with the phone not turning back on and then suddenly after a cooldown it does... any thoughts?


EDIT: Yes when this problem occurs the red LED blinks "on long" "off long" while the phone is in charger.

 

[ahsan64]

I let the phone cool down (it get's very hot very fast!) and removed battery and replaced it again, phone ON and in bootloader now, thanks

The heat issue still remains tho, I wonder if this might be the source of this unstable situation with the phone not turning back on and then suddenly after a cooldown it does... any thoughts?

Are you using Stock Rom or Custom Rom ..

The heat issue is normal but sometime it's due to overclocking 2d/3d GPU ..

 

[Sverrebob]

Are you using Stock Rom or Custom Rom ..

The heat issue is normal but sometime it's due to overclocking 2d/3d GPU ..

The phone is completely stock except the replaced screen. I encountered the bootloop after replacing the screen and it's been like that since...

 

[ahsan64]

The phone is completely stock except the replaced screen. I encountered the bootloop after replacing the screen and it's been like that since...

Two methods:
1: Follow this GUIDE if phone Hboot is 1.27 or 1.29 and flash any custom Rom .
NOTE: You can skip step 2(S-OFF PART) in above guide
2: Or just find official RUU and install it and see if phone boots ..

 

[Sverrebob]

Two methods:
1: Follow this GUIDE if phone Hboot is 1.27 or 1.29 and flash any custom Rom .
NOTE: You can skip step 2(S-OFF PART) in above guide
2: Or just find official RUU and install it and see if phone boots ..

Ok I will try this thanks!

Just got the phone back on and into bootloader, had to let it cool off again to get it on. I feel somewhat connected to the other thread in this forum - "Dead sensation" ...

 

[Sverrebob]

Update :

I cant seem to access the sd card when I have my phone in Fastboot usb mode and since my rom is f**ked I cant boot into the phone either.
Also recovery fails, probably due to fastboot still active, any way to turn that off when I cant get past bootloader?
And if anyone know how I can access the sd card from phone on my PC I would appreciate it :/

De-assembled my phone again just to recheck all connectors etc, all seems just fine... really confused on whats up with this phone now :/

 

[rzr86]

Update :

I cant seem to access the sd card when I have my phone in Fastboot usb mode and since my rom is f**ked I cant boot into the phone either.
Also recovery fails, probably due to fastboot still active, any way to turn that off when I cant get past bootloader?
And if anyone know how I can access the sd card from phone on my PC I would appreciate it :/

De-assembled my phone again just to recheck all connectors etc, all seems just fine... really confused on whats up with this phone now :/

it would be better to use a ruu.exe and see how it goes then
http://forum.xda-developers.com/showthread.php?t=1672425

 

[Sverrebob]

my bootloader reads as follows:

***relocked***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012,17:33:34

my cid is HTC__Y13 and my version-main is 3.33.401.53
using this info I can only find this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M

I dont know if this is correct, I dont see anything resembling my cid in there.

note: bootloader is relocked using

fastboot oem lock

as the http://forum.xda-developers.com/showthread.php?t=1672425 guide says. Following that guide now but is confused on the RUU to get. Gonna try with the RUU I have downloaded now and I'll let you know how it goes...

 

[Sverrebob]

my bootloader reads as follows:

***relocked***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012,17:33:34

my cid is HTC__Y13 and my version-main is 3.33.401.53
using this info I can only find this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M

I dont know if this is correct, I dont see anything resembling my cid in there.

note: bootloader is relocked using

fastboot oem lock

as the http://forum.xda-developers.com/showthread.php?t=1672425 guide says. Following that guide now but is confused on the RUU to get. Gonna try with the RUU I have downloaded now and I'll let you know how it goes...

Ok I completed the exe RUU file and it told me it was completed, STILL I only get green HTC logo and bootloop. Entering bootloader the pgone tells me the battery voltage is too low, will this prevent the phone from booting normally?
I have it on FASTBOOT AC now and hope it will charge, then I'll try to restart the phone and see if I can boot it.

 

[rzr86]

Ok I completed the exe RUU file and it told me it was completed, STILL I only get green HTC logo and bootloop. Entering bootloader the pgone tells me the battery voltage is too low, will this prevent the phone from booting normally?
I have it on FASTBOOT AC now and hope it will charge, then I'll try to restart the phone and see if I can boot it.

after charge use the command to reboot from bootloader if it fails normally
fastboot reboot

 

[Sverrebob]

after charge use the command to reboot from bootloader if it fails normally
fastboot reboot

Tried that several times already, same thing happens, white screen with green HTC , goes into the usual bootloop.
Recovery from bootloader menu also end up the same way as above.
Factory reset aswell.

Also, every time I get into bootloader it does this check you can see on this screenshot here

Any inputs on this, or is this normal when the SD card is empty?
During the white bootloop screen with green HTC the SD card does get recogniced by my PC and shows up in explorer briefly before phone reboots again, so it cant be the SD card reader can it?

I consider myself pretty much advanced when it comes to techology and I have been reading up on all this stuff around phones and what you can do with them. I feel I have gotten a pretty basic understanding so far, and from my point I really does not see why my phone wont behave normal.

It kinda cooks down to some hardware fail, atleast in my opinion? I'm really at my wits end here

 

[heavy_metal_man]

Tried that several times already, same thing happens, white screen with green HTC , goes into the usual bootloop.
Recovery from bootloader menu also end up the same way as above.
Factory reset aswell.

Also, every time I get into bootloader it does this check you can see on this screenshot here

Any inputs on this, or is this normal when the SD card is empty?
During the white bootloop screen with green HTC the SD card does get recogniced by my PC and shows up in explorer briefly before phone reboots again, so it cant be the SD card reader can it?

I consider myself pretty much advanced when it comes to techology and I have been reading up on all this stuff around phones and what you can do with them. I feel I have gotten a pretty basic understanding so far, and from my point I really does not see why my phone wont behave normal.

It kinda cooks down to some hardware fail, at least in my opinion? I'm really at my wits end here

Hi, gonna try help out
firstly, your screen shot. that will always happen when you boot into the bootloader with an sd card in the phone. doesnt matter whats on it, it will always check it for those files if it detects it. its not an issue
Second, when you try to boot into recovery, does it ever make it? or does it always sit at the splash screen. ( the white background with the green htc letters.)

thirdly, if you are willing to unlock your bootloader again can you place the attached recovery.img and place it into your adb/fastboot folder, and then when in fastboot usb issue the command fastboot boot recovery.img , hopefully it will boot into 4ext recovery temporarily, and allow you to try get some system information. (assuming your new touch screen works ) you may get some warnings if/when 4ext boots up. make a note of all of them and reply to here please

 

[Sverrebob]

Hi, gonna try help out
firstly, your screen shot. that will always happen when you boot into the bootloader with an sd card in the phone. doesnt matter whats on it, it will always check it for those files if it detects it. its not an issue
Second, when you try to boot into recovery, does it ever make it? or does it always sit at the splash screen. ( the white background with the green htc letters.)

thirdly, if you are willing to unlock your bootloader again can you place the attached recovery.img and place it into your adb/fastboot folder, and then when in fastboot usb issue the command fastboot boot recovery.img , hopefully it will boot into 4ext recovery temporarily, and allow you to try get some system information. (assuming your new touch screen works ) you may get some warnings if/when 4ext boots up. make a note of all of them and reply to here please

I appreciate the reply

It have never gotten into recovery, it always stuck at the "splash screen" and have done so with both 4EXT and CWM.

thirdly: I unlocked the bootloader and put your attached recovery.img into the fastboot folder, ran the command with phone in "fastboot usb" and ended up on splash screen as always, it stays there for a few seconds then it goes black. It seems like the phone is rebooting but the screen remains black. I do, however, get the well-known sound of an usb device beeing attached and removed again, with a few seconds silence in between. Screen remains black. To solve this mysterious "bootloop" I remove the USB cable, gives it half a minute and do the vol-down pwr button method and then I am back in the bootloader again.

Just for fun I have tried the recovery menu in bootloader with the phone not connected to usb, same splash screen here. It just seems that my phone really dont want the recovery to work :/

 

[Sverrebob]

extra info: figured out that the screen went black after one splash screen due to me pressing vol-down. It apparently does 3 reboots showing splash screen, then a couple mysterious black screen reboots and then another splash screen reboot three times... I have stopped this weird cycle now to save my poor battery, but it seems that it would just have continiued this behavior of 3 splash screen reboots - 2 black - 3 splash and so on...

weird!

ALSO; this is the response from fastboot command I get when trying to boot the recovery from there:

C:\android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [  1.493s]
booting...
OKAY [  0.002s]
finished. total time: 1.495s

 

[rzr86]

extra info: figured out that the screen went black after one splash screen due to me pressing vol-down. It apparently does 3 reboots showing splash screen, then a couple mysterious black screen reboots and then another splash screen reboot three times... I have stopped this weird cycle now to save my poor battery, but it seems that it would just have continiued this behavior of 3 splash screen reboots - 2 black - 3 splash and so on...

weird!

ALSO; this is the response from fastboot command I get when trying to boot the recovery from there:

C:\android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [  1.493s]
booting...
OKAY [  0.002s]
finished. total time: 1.495s

did you try to boot into safe mode?
once you will see the splash screen hold volume down until it gets you to the safe mode
see if it works

 

[Sverrebob]

did you try to boot into safe mode?
once you will see the splash screen hold volume down until it gets you to the safe mode
see if it works

Thank you for the tip, unfortunately it didnt seem to work
I pressed volume down as soon as the splash screen appeared after I executed the <fastboot boot recovery.img> and it just hang there for a few seconds then the phone rebooted and I ended up in the bootloader again.

 

[heavy_metal_man]

Hmmm. This is very strange indeed. My theory is that your internal partitioning may be messed up, so when the phone tries to boot things are not in the right place. But that doesn't explain why it won't fastboot boot, as fastboot boot should boot the .IMG into the ram and not attempt to flash it. It may well be down to a hardware fault. If your ruu ran without any errors then it should have fixed any partition errors. You could try extracting the boot.IMG from the ruu and use the fastboot boot boot.IMG command and see if that gets you any farther.

Also when your phone goes into the black after the splash screen, can you keep it connected to the PC and issue the command adb devices for me just a hunch I have

Sent from my Nexus 7 using Tapatalk 4

 

[Sverrebob]

Hmmm. This is very strange indeed. My theory is that your internal partitioning may be messed up, so when the phone tries to boot things are not in the right place. But that doesn't explain why it won't fastboot boot, as fastboot boot should boot the .IMG into the ram and not attempt to flash it. It may well be down to a hardware fault. If your ruu ran without any errors then it should have fixed any partition errors. You could try extracting the boot.IMG from the ruu and use the fastboot boot boot.IMG command and see if that gets you any farther.

Also when your phone goes into the black after the splash screen, can you keep it connected to the PC and issue the command adb devices for me just a hunch I have

Sent from my Nexus 7 using Tapatalk 4

So get this, tried to <fastboot boot recovery.img> again in order to obtain this black screen and do your <adb devices> and nothing! It's like the phone heard you and decided to "behave".....
It did 10 perfectly normal reboots with the splash screen every time, and the 4th and 5th time it even vibrated once...!

This whole charade is almost a little funny to me now, but clown phone or not, I'm not giving it up yet

I managed to google how-to extract the boot.img file from the RUU exe, it was a rather tidious operation
I found a very well explained guide on it here; https://sites.google.com/site/androidbyyorzua/home/tutorials/extracting-rom-files-from-htc-ruu

And not suprisingly all I got out of it was a error msg

C:\android>fastboot boot boot.img
creating boot image...
creating boot image - 3868672 bytes
downloading 'boot.img'...
OKAY [  0.984s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 0.999s

Something wrong with my phones RAM maybe?

EDIT: I tried the fastboot command to flash the rom.zip and this is how it went.

C:\android>fastboot flash zip rom.zip
sending 'zip' (436283 KB)...
OKAY [ 57.499s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: not allowed)
finished. total time: 57.819s

Tried it again with bootloader RELOCKED and it took alot more time and was slightly different, but still same error msg

C:\android>fastboot flash zip rom.zip
sending 'zip' (436283 KB)...
OKAY [ 57.685s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: not allowed)
finished. total time: 134.679s