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

heavy_metal_man · Nov 3, 2013 at 4:58 PM

Sverrebob said:
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

Code:

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.

Code:

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

Code:

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

Hey pal

sorry ive taken so long ive been researching. i think it may be your internal partitions are messed up. since your s-on your pretty much stuck unless we can get a ruu to run for you. within the rom.zip you have extracted there should be a text file called android info i believe. check and see if your cid is within this txt file, also check and see if your hboot version is higher than the one within your rom.zip file. if your phones is higher it wont flash it. also, when you try to flash it, try issuing the commands

Code:

fastboot oem rebootRUU

fastboot flash zip rom.zip

fastboot flash zip rom.zip

fastboot reboot

assuming that the zip you have is still called rom.zip, your bootloader is locked and your bootloader is not higher than the one in the rom.zip

the second flash command is after the first one finishes saying it needs to be flushed, or reflushed. give this a bash and i will keep on hunting for you

if on the other hand your hboot versions wont play ball or the cid is off we shall have to find you a newer/correct one

Sverrebob · Nov 1, 2013 16 0 0

heavy_metal_man said:
Hey pal sorry ive taken so long ive been researching. i think it may be your internal partitions are messed up. since your s-on your pretty much stuck unless we can get a ruu to run for you. within the rom.zip you have extracted there should be a text file called android info i believe. check and see if your cid is within this txt file, also check and see if your hboot version is higher than the one within your rom.zip file. if your phones is higher it wont flash it. also, when you try to flash it, try issuing the commands

Code:

fastboot oem rebootRUU fastboot flash zip rom.zip fastboot flash zip rom.zip fastboot reboot

assuming that the zip you have is still called rom.zip, your bootloader is locked and your bootloader is not higher than the one in the rom.zip

the second flash command is after the first one finishes saying it needs to be flushed, or reflushed. give this a bash and i will keep on hunting for you if on the other hand your hboot versions wont play ball or the cid is off we shall have to find you a newer/correct one

Okay I really appreciate the help man

This is from the android_info.txt inside my rom.zip

Code:

modelid: PG5813000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016
mainver: 3.33.401.53
hbootpreupdate:12
DelCache:1

so the cid and mainver are the same as on my phone. It's says nothing about the hboot version as far as I can see. Unless you mean a file inside the rom.zip that is named < hboot_8x60_1.27.0000_20120113_signedbyaa.nb0 > ? This is the same as my hboot version (1.27)

I've run the fastboot commands you posted, got me into a black screen with silver "HTC" and then a large wall of text appeared also a green bar filling up on my phone's screen. Once the first < fastboot flash zip rom.zip > was done I issued the next one and fairly the same wall of text came, only with a few different changes... see below

Code:

(bootloader) [RUU]WP,system,96
(bootloader) [RUU]WP,system,98
(bootloader) [RUU]WP,system,100
(bootloader) start image[sp1] unzipping & flushing... 
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) start image[sbl2] unzipping & flushing...
this is just 5% of all the text btw!
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,73
(bootloader) [RUU]WP,radio,100
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
OKAY [416.100s]
finished. total time: 473.652s

< fastboot reboot > rebooted the phone and splash screen appeared, staying there for 20-30s then going black and repeating the same splash screen. this has been going on for 5 minutes now. I assume this means it didnt work

heavy_metal_man · Nov 3, 2013 at 5:47 PM

Sverrebob said:
Okay I really appreciate the help man

This is from the android_info.txt inside my rom.zip

Code:

modelid: PG5813000 cidnum: HTC__001 cidnum: HTC__E11 cidnum: HTC__N34 cidnum: HTC__203 cidnum: HTC__102 cidnum: HTC__405 cidnum: HTC__Y13 cidnum: HTC__A07 cidnum: HTC__304 cidnum: HTC__032 cidnum: HTC__016 mainver: 3.33.401.53 hbootpreupdate:12 DelCache:1

so the cid and mainver are the same as on my phone. It's says nothing about the hboot version as far as I can see. Unless you mean a file inside the rom.zip that is named < hboot_8x60_1.27.0000_20120113_signedbyaa.nb0 > ? This is the same as my hboot version (1.27)

I've run the fastboot commands you posted, got me into a black screen with silver "HTC" and then a large wall of text appeared also a green bar filling up on my phone's screen. Once the first < fastboot flash zip rom.zip > was done I issued the next one and fairly the same wall of text came, only with a few different changes... see below

Code:

(bootloader) [RUU]WP,system,96 (bootloader) [RUU]WP,system,98 (bootloader) [RUU]WP,system,100 (bootloader) start image[sp1] unzipping & flushing... (bootloader) [RUU]UZ,sbl1,0 (bootloader) [RUU]UZ,sbl1,100 (bootloader) signature checking... (bootloader) start image[sbl2] unzipping & flushing... this is just 5% of all the text btw! (bootloader) [RUU]WP,radio,0 (bootloader) [RUU]WP,radio,73 (bootloader) [RUU]WP,radio,100 (bootloader) start image[rcdata] unzipping & flushing... (bootloader) [RUU]UZ,rcdata,0 (bootloader) [RUU]WP,rcdata,0 OKAY [416.100s] finished. total time: 473.652s

< fastboot reboot > rebooted the phone and splash screen appeared, staying there for 20-30s then going black and repeating the same splash screen. this has been going on for 5 minutes now. I assume this means it didnt work

well it means the update worked

its very much looking like a hardware issue now :/

Sverrebob · Nov 1, 2013 16 0 0

heavy_metal_man said:
well it means the update worked its very much looking like a hardware issue now :/

I totally agree

btw I noticed something, if you look at my above post of the android_info.txt it says the hbootpreupdate is 12 , and this paste below is from my phone when I run a < fastboot getvar all > it seems my phone has the hbootpreupdate set to 11. Has this anything to say?

Code:

C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.53
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxx
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4114mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
[B](bootloader) hbootpreupdate: 11[/B]
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.495s

heavy_metal_man · Nov 3, 2013 at 5:59 PM

Sverrebob said:

I totally agree

btw I noticed something, if you look at my above post of the android_info.txt it says the hbootpreupdate is 12 , and this paste below is from my phone when I run a < fastboot getvar all > it seems my phone has the hbootpreupdate set to 11. Has this anything to say?

Code:

C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.53
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxx
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4114mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
[B](bootloader) hbootpreupdate: 11[/B]
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.495s

its possible that the phone is ignoring the hboot pre update from the rom.zip as it may not need it. tbh we are starting to move out of my depth. did the phone definitely work bar the dead screen before you acquired it? do you know how it came to be broken? i mean like if it was ran over before you got it it may well be ram damage :/

Sverrebob · Nov 1, 2013 16 0 0

heavy_metal_man said:
its possible that the phone is ignoring the hboot pre update from the rom.zip as it may not need it. tbh we are starting to move out of my depth. did the phone definitely work bar the dead screen before you acquired it? do you know how it came to be broken? i mean like if it was ran over before you got it it may well be ram damage :/

The phone was working just fine before I replaced the screen, and it was only the digitizer glass that was shattered. I ordered the LCD+digitizer because according to many it was far more easier to replace those two rather than just the digitizer. That was because I didnt have to disassemble that much. I should of just kept the phone as it was with a shattered digitizer glass, the touch was OK and I could see what was on the screen.

Now it seems like I have to try and get a new sensation, hopefully I can find one with a broken screen so I can get it cheap.

heavy_metal_man · Nov 3, 2013 at 6:15 PM

Sverrebob said:
The phone was working just fine before I replaced the screen, and it was only the digitizer glass that was shattered. I ordered the LCD+digitizer because according to many it was far more easier to replace those two rather than just the digitizer. That was because I didnt have to disassemble that much. I should of just kept the phone as it was with a shattered digitizer glass, the touch was OK and I could see what was on the screen.

Now it seems like I have to try and get a new sensation, hopefully I can find one with a broken screen so I can get it cheap.

Seems like it pal :/ sorry we couldnt get it going again like. always feels like a waste when they die like this eh?

Sverrebob · Nov 1, 2013 16 0 0

heavy_metal_man said:
Seems like it pal :/ sorry we couldnt get it going again like. always feels like a waste when they die like this eh?

I know, it sucks

But the help I have recieved here have been outstanding tho. I will certainly come back here when I get a new phone

heavy_metal_man · Nov 3, 2013 at 6:27 PM

Sverrebob said:
I know, it sucks

But the help I have recieved here have been outstanding tho. I will certainly come back here when I get a new phone

I help when i can

we all tend to share the love here, common goals and all that

welcome to xda developers pal

Top Devices

New Devices

Topics

Search

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

heavy_metal_man

Senior Member

Sverrebob

Member

heavy_metal_man

Senior Member

Sverrebob

Member

heavy_metal_man

Senior Member

Sverrebob

Member

heavy_metal_man

Senior Member

Sverrebob

Member

heavy_metal_man

Senior Member

New posts