urgent help with htc sensation :( - HTC Sensation

Hi, i have a htc sensation with the following details its S-on , htc dev relocked bootloader because of going to stock ..
INFOversion: 0.5
INFOversion-bootloader: 1.27.0000
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.53 (before flashing the ruu it shoes 1.24.0)
INFOserialno: SH19WV803357
INFOimei: 3583..............
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 3784mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.484s
i had cm9 installed on it but it was eating a lot of battery i switched to other versions.. i tried other cm 10 ,10.1 and 10.2 , ciper 3.12, 1.6.3, and hd revoloution 7.5 i gues.. and it all started after flashing the viper rom ..
i installed various roms .. and i always did smartflash enabled before installing my rom, and then fastboot the img file to it.. but after removing the viper 3.1.2 rom .. i got stuck in serious bootlop..
I flashed other roms but still bootloop..
now i tried to go back to stock following this guide here http://forum.xda-developers.com/showthread.php?t=1672425 i flased the RUU for my HTC_001 RUU file name is ((RUU-Pyramid-ICS-hTC-Europe-3.33.401.53-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-280871-signed)) .. but even with this RUU file i get bootloop..
HTC screen comes and then the htc splash screen and it reboots .. and it continues.. " .. (before flashing i did fast oem lock thing)
i am stuck with this phone here need a working one again .. please help me .. i dont want to spent extra 1000buks here.. already spent 4.5k(rupes) to get this mobile from my last one .. which was a htc desire c (screen prob) .. now please help me get this thing working
i am already having sleepless nights

no one here to help

dxbboy said:
no one here to help
Click to expand...
Click to collapse
I`m a noob but, heck...erase everything from root of your SD card...some files can force loop cycle (when you are in bootloader)

Can you boot into Fastboot and Recovery ?

silentvisitor said:
Can you boot into Fastboot and Recovery ?
Click to expand...
Click to collapse
as i tried to go back to the stock ... i had to locked my boatloader.. but yes i can get into fastboot but when i go into recovery i see blackscreen with mobile pic in center with an arrow above it + a bar loading at the bottom with a sdcard like sign..

At this point to get your phone operational I would download the appropriate RUU for your phone and reimage it to get it working again.
I know you flashed the 3.33 RUU. What I mean is try the 3.32 RUU
Sent from my HTC One using xda app-developers app

Kohr-Ah said:
At this point to get your phone operational I would download the appropriate RUU for your phone and reimage it to get it working again.
I know you flashed the 3.33 RUU. What I mean is try the 3.32 RUU
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
yes i am currently downloading the 3.32.401.1 RUu to give it a try .. as my cid is htc_001 and wwe :xx.xx.401.x
do i have to flash a new rom after this or with this RUU the phone will boot ? :S
i relocked the bootloader for RUU ..but when type my token number in htc dev it gives error now lets just wait to see what this RUU does

dxbboy said:
yes i am currently downloading the 3.32.401.1 RUu to give it a try .. as my cid is htc_001 and wwe :xx.xx.401.x
do i have to flash a new rom after this or with this RUU the phone will boot ? :S
i relocked the bootloader for RUU ..but when type my token number in htc dev it gives error now lets just wait to see what this RUU does
Click to expand...
Click to collapse
see if it will boot

i tried RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed
but it gave error 140 bootloader version error and on my device it shows ruu main version is older update fail

dxbboy said:
i tried RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed
but it gave error 140 bootloader version error and on my device it shows ruu main version is older update fail
Click to expand...
Click to collapse
What about reunlocking the bootloader (Can always relock it right?),then run the 3.33 RUU again or flasha cyanogenmod rom again and see if it boots?
Usually boot loops are simple. Like wiping dalvik and cache solves it but that is on a rom basis not a stock RUU Basis.

Kohr-Ah said:
What about reunlocking the bootloader (Can always relock it right?),then run the 3.33 RUU again or flasha cyanogenmod rom again and see if it boots?
Usually boot loops are simple. Like wiping dalvik and cache solves it but that is on a rom basis not a stock RUU Basis.
Click to expand...
Click to collapse
about reunlocking .. i visited the htc dev site.. i entered my token number.. it gave error ..that i cannot be unblocked blabla.. how do i reunlock it ? locking is ya its done with a single command... plus
i wanted to know if i flashh 3.33RUU which i did earlier, do i have to flash a rom just after this or does the RUU have a rom inside the exe, i am asking because when you go to temp folder you see a rom.zip file which many ppl suggest to flash via fastboot if normal ruu flash isnt working ?

i am trying to flash the rom.zip from 3.32 now .. hope it doesnt give the bootloader error here
nops its a negative result
C:\Documents and Settings\Muffi\Desktop\ADB_Fastboot_Windows>fastboot flash zip
rom.zip
sending 'zip' (430184 KB)... OKAY [ 63.031s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 141.625s
((FAILED (remote: 43 main version check fail)
Your device is S-ON & you are trying to use an RUU that has software number less than your current software number.))
i guess the error is there because i flashed the 3.33 RUU ?? am i stuck with it .. how to start this phonee(

dxbboy said:
i am trying to flash the rom.zip from 3.32 now .. hope it doesnt give the bootloader error here
nops its a negative result
C:\Documents and Settings\Muffi\Desktop\ADB_Fastboot_Windows>fastboot flash zip
rom.zip
sending 'zip' (430184 KB)... OKAY [ 63.031s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 141.625s
((FAILED (remote: 43 main version check fail)
Your device is S-ON & you are trying to use an RUU that has software number less than your current software number.))
i guess the error is there because i flashed the 3.33 RUU ?? am i stuck with it .. how to start this phonee(
Click to expand...
Click to collapse
the ruu.exe contains a rom.zip too
extract the one from 3.33 and flash it manually from bootloader or via fastboot command

tried that already, thats why you are seeing the firmware in my log as 3.33.. but i notiches the baseband is unavailable.. might that be a problem ?

none of the given instruction helps :S what should i do ? i flashed the 3.33 rom from RUU + from fastboot just after RUU still the bootlop, it reaches htc splash and restarts .. n goes on n on n on..
UPDATE : i relocked my bootloader via htc dev, i installed 4ext again .. i cleard factory reset, cache dvlkcache, format partition expt sdcard... this time i installed ((rmk-pyramid-stock_ics_3.32.401.3-v1)) with the smartflash enabled .. i installed, booted back to fastboot , flashed the boot.img.. and it still get stuck on the htc splash screen .. a tone come and it restarts .. ..
Update 2 : i installed cm-10.2-20130929-Sultan-pyramid , flasht boot.. now cyanagebnod circles spins and its booted .. i didnt receive a bootloop yet but inside the settings it shows unknown baseband and i dont have my phone signals
update 3 : still those bootloops as i can sometime bootup.. i am going to try to get S-off using juopunutbear ..

dxbboy said:
none of the given instruction helps :S what should i do ? i flashed the 3.33 rom from RUU + from fastboot just after RUU still the bootlop, it reaches htc splash and restarts .. n goes on n on n on..
UPDATE : i relocked my bootloader via htc dev, i installed 4ext again .. i cleard factory reset, cache dvlkcache, format partition expt sdcard... this time i installed ((rmk-pyramid-stock_ics_3.32.401.3-v1)) with the smartflash enabled .. i installed, booted back to fastboot , flashed the boot.img.. and it still get stuck on the htc splash screen .. a tone come and it restarts .. ..
Update 2 : i installed cm-10.2-20130929-Sultan-pyramid , flasht boot.. now cyanagebnod circles spins and its booted .. i didnt receive a bootloop yet but inside the settings it shows unknown baseband and i dont have my phone signals
update 3 : still those bootloops as i can sometime bootup.. i am going to try to get S-off using juopunutbear ..
Click to expand...
Click to collapse
for S-OFF you need the stock rom.link in my signature.i don't know if it works with other rom
and something else.when you are enabling smartflash don't flash after that the boot.img
you are doing the same step twice

just downloaded the file from your signature.. Sensation_3.33.401.53_deodexed : flashed it ok it booted after a couple of heartbeating bootlops ..first time it took alot of time to load.but it booted atleast but then again stuck there with bootloop, and now i got my signals again.. but bootloop is killing me .. 20,.30 times bootlop then a single start then again bootloop
+ i wanted to know ,, if the joupnutbear will work on 3.33 ?

any way .. couldnt get though the process.. just got fedup.. so gave it in a market to repair.. hope they fix it

no that guy in the market was a noob .. he just installed the stock that i installed earlier and send the mob back... ill have to do it ... i wana ask .. how can i run jupunetbear if i cant bootup.. alot of bootloping is there

hey mate... .. i was able to make it s-off using the jp windows guide.. but i still have those loops.. some time.. like , 3, 4 times a day ..

Related

[Q] HBoot 1.18.000 problems

I'm stuck
I got my Sensation back from repairs with 1.18 and pressed on and rooted. I now run rooted stock 2.3 with S-On but unlocked using HTC method (Revolutionary didn't work for some reason) and ClockWorkMod with SuperCID
This is where the problems started
I can't get S-Off
I have tried everything I can find (literally been on this for hours). I've tried:
Revolutionary 0.4pre4 (which fails to gain root - possibly because I've already got root)
HTCSuperTool (v3 of which appears to be broken, btw)
Downloading various firmwares and flashing them (using the PG58img.zip/bootloader method)
I've even tried running the RUU exe and pulling the rom.zip, renaming that and dropping that in the SD card
Running the RUU (both the latest T-Mobile UK and the latest ICS version)
The weird thing is that it reads the PG58img.zip files, loads them, starts to parse them then goes back to bootloader and doesn't read them again unless I reboot the bootloader
Update: Re-locked the bootloader and still can't run the RUU for ICS
Any ideas?
Anyone? Please help!
I've just been through all this after getting my phone back from repair. Mine came back with t-mobile branded rom version 1.50.110.2 and wouldnt s-off with revolutionary. Luckily the phone still had supercid so i flashed RUU_Pyramid_HTC_Europe_1.50.401.1_R_Radio_10.58.9035.00U_10.15.9035.02_2_release_228602_signed.exe and revolutionary finally worked. You can read my thread here http://forum.xda-developers.com/showthread.php?t=1538324
Thank you, I'll try that (if I can ever get a slot on the FileFactory download server...)
I've got a 1.17 hboot.img from Kohr-Ar (used in one of the PG58IMG.zips), could I use fastboot flash hboot hboot.img to flash that or would i be left with a brick?
Ok, got the ROM and tried to flash but I forgot that I put the CID back to the T-Mobile CID. Now, I can't change the CID, I always get:
>fastbooot oem writecid 11111111
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) pyramid_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.079s]
finished. total time: 1.080s
Any ideas now?
pnlrogue1 said:
Ok, got the ROM and tried to flash but I forgot that I put the CID back to the T-Mobile CID. Now, I can't change the CID, I always get:
>fastbooot oem writecid 11111111
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) pyramid_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.079s]
finished. total time: 1.080s
Any ideas now?
Click to expand...
Click to collapse
did u find any solution , i am exactly in same situation i also did exactly same thing now stuck
Try to run ruu ???
Sent from my HTC Sensation 4G using xda premium
Afraid not. I tried all sorts of things - best I can say is do NOT try to flash your bootloader using the fastboot method - found that out the hard way...
I think flashing an alternative ROM may help but I'm not sure. Maybe contact the devs of Revolutionary - it just wants a way of skipping the Zerging Root stage in V0.5...
Find my post and do it step by step run ruu then change cid
Sent from my HTC Sensation 4G using xda premium

Sensation woes - stuck in bootloader (no Android boot, no Recovery)

Hi,
Like, it seems, plenty of others, I messed up my phone by trying a custom ROM and then screwing up the "return-to-stock".
I have a T-Mo UK Sensation which was running GB 2.3.4 until I put Android Revolution HD 6.5.5 XE on it.
Basically I fell into the S-ON trap, and bricked the device. Wouldn't power on at all.
With help from Dexter from the unbrick project, I have managed to get the phone to load into Bootloader, but it won't load the Android OS, nor will it go into recovery.
I think the usual next step is to use latest RUU to flash a new ROM. Thing is, my phone is now S-ON and thinks it's a T-Mo UK phone again (CID T-MOB005, I think). And T-Mo UK's last released upgrade is ancient (RUU_Pyramid_TMO_UK_1.34.110.1). So there isn't a ROM that is new enough AND compatible with my CID number. I asked Football and he suggested he could get RUU_Pyramid_TMO_UK_1.50.110.2, but even that sounds like it'll be too old (I'm guessing it probably doesn't have HBOOT 1.27)
Could anyone advise if there's a way I can get my phone back?
Bootloader text as folows:
Code:
*** LOCKED ***
*** Security Warning ***
Pyramid PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17.33.34
Then the usual Vol Up, Vol Down instructions, and
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
If I go into Bootloader these options change to:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
But if I choose Recovery, it just reboots to Bootloader.
Would be really grateful if anyone can help me. I'm not v popular at home having spent hours trying to fix this mess (and getting pretty stressed about it!)
jezash said:
Hi,
Like, it seems, plenty of others, I messed up my phone by trying a custom ROM and then screwing up the "return-to-stock".
I have a T-Mo UK Sensation which was running GB 2.3.4 until I put Android Revolution HD 6.5.5 XE on it.
Basically I fell into the S-ON trap, and bricked the device. Wouldn't power on at all.
With help from Dexter from the unbrick project, I have managed to get the phone to load into Bootloader, but it won't load the Android OS, nor will it go into recovery.
I think the usual next step is to use latest RUU to flash a new ROM. Thing is, my phone is now S-ON and thinks it's a T-Mo UK phone again (CID T-MOB005, I think). And T-Mo UK's last released upgrade is ancient (RUU_Pyramid_TMO_UK_1.34.110.1). So there isn't a ROM that is new enough AND compatible with my CID number. I asked Football and he suggested he could get RUU_Pyramid_TMO_UK_1.50.110.2, but even that sounds like it'll be too old (I'm guessing it probably doesn't have HBOOT 1.27)
Could anyone advise if there's a way I can get my phone back?
Bootloader text as folows:
Code:
*** LOCKED ***
*** Security Warning ***
Pyramid PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17.33.34
Then the usual Vol Up, Vol Down instructions, and
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
If I go into Bootloader these options change to:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
But if I choose Recovery, it just reboots to Bootloader.
Would be really grateful if anyone can help me. I'm not v popular at home having spent hours trying to fix this mess (and getting pretty stressed about it!)
Click to expand...
Click to collapse
Hi,
I am not sure where exactly you want to end up.
But if you wanted to get an ICS ROM on your phone,try THIS THREAD
thanks for the suggestion. At the moment I just want a working phone. Don't really mind if it's ICS or not.
Just gone through the HTC Dev procedure. Was sceptical as adb devices didn't return any connected devices. But it got the code and I was able to get the token via email.
I sent the command fastboot flash unlocktoken Unlock_code.bin and it appeared to succeed. However, I didn't see the message in Step 13. The phone still shows bootloader and it still says ***Locked***.
The Step 13 message looks like an android OS thing - I wonder if I can't see it unless I can boot to Android?
Anyway, I pressed onto the section about flashing a recovery. Again, no device shows up in adb devices.
When I tried to flash the 4EXT recovery, I got an error message:
sending 'recovery' (6116 KB)... OKAY [ 1.507s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.298s
Does this mean that the unlock hasn't actually worked then?
jezash said:
thanks for the suggestion. At the moment I just want a working phone. Don't really mind if it's ICS or not.
Just gone through the HTC Dev procedure. Was sceptical as adb devices didn't return any connected devices. But it got the code and I was able to get the token via email.
I sent the command fastboot flash unlocktoken Unlock_code.bin and it appeared to succeed. However, I didn't see the message in Step 13. The phone still shows bootloader and it still says ***Locked***.
The Step 13 message looks like an android OS thing - I wonder if I can't see it unless I can boot to Android?
Anyway, I pressed onto the section about flashing a recovery. Again, no device shows up in adb devices.
When I tried to flash the 4EXT recovery, I got an error message:
sending 'recovery' (6116 KB)... OKAY [ 1.507s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.298s
Does this mean that the unlock hasn't actually worked then?
Click to expand...
Click to collapse
Hi,
Have you got the necessary drivers installed to use ADB.
Try using THIS TOOLKIT
It has the drivers,and an unlock section.
first of all confirm your CID
fastboot getvar cid command will give you cid
if its supercid (unlikely) or any other which has ICS ROM for it ..then you are lucky
other wise try the HTCdev method again...no need to get the unlock_code again
just use the one you got previously ...then reboot and see..hopefully it works
hi, thanks for various suggestions.
have tried the HTCDEV method a couple of times without success. I never see the Confirmation Screen shown in step 13 on the HTCDEV bootloader unlock procedure.
Definitely have the HTC drivers installed, have previously used adb successfully from this PC. Plugged in my old HD2 (running Android) and adb devices finds it ok.
Checked my CID as suggested, it's T-MOB005.
Tried downloading the toolkit suggested by malybru and didn't get any further - I think it just does the same thing (runs the HTCDEV unlock process).
One thing that's odd. I tried flashing 4EXT Recovery from command prompt. A "loading" bar showed up on the right side of the screen of the phone like it was working, but then I get the "signature verify fail" shown above.
I guess I can't use Revolutionary S-OFF as I can't boot to Android.
What can I do? Should I try this: http://forum.xda-developers.com/showthread.php?t=1469296 - Edit - actually it seems like that still needs the HTC DEV unlock to work ... which seems to be my problem :-(
have tried the HTCDEV unlock method quite a few times now. In the command prompt it appears to work successfully, but I never get the Android-like confirmation screen (I think this must be because my phone will not currently boot to Android).
As I think I need to unlock before I can flash anything else, I am stuck. :-(
Does anyone have a suggestion for another way to unlock it?
Given that T-Mobile UK have not given any date for releasing ICS, I have no notion of when I can fix my phone. Hence considering sending for repair - presumably replacing CPU or something would fix it? Any idea how much this would cost? (Using my old HD2 running a somewhat unstable version of Android is starting to drive me crazy).
jezash said:
Given that T-Mobile UK have not given any date for releasing ICS, I have no notion of when I can fix my phone. Hence considering sending for repair - presumably replacing CPU or something would fix it? Any idea how much this would cost? (Using my old HD2 running a somewhat unstable version of Android is starting to drive me crazy).
Click to expand...
Click to collapse
Can you pop in the irc? We can do some last tries before you send it for repairs
Sent from my pyramid.. Through blazing fast sonic waves
hi ganesh - am in the IRC now. only for the next 15 minutes or so. if you think there is something remaining that is worth trying i can come back tomorrow.
thanks for your reply.
jezash said:
hi ganesh - am in the IRC now. only for the next 15 minutes or so. if you think there is something remaining that is worth trying i can come back tomorrow.
thanks for your reply.
Click to expand...
Click to collapse
EDIT:based on these values ..seems like something can be done..remember ..this is all to avoid extra money to get it repaired
can you post some more details?
fastboot getvar all (except IMEI and SERIAL NO )
Hi Ganesh,
Thanks for your reply. Here are the details from my phone:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.27.0000
INFOversion-baseband: 11.22.3504.07_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.34.206.1
INFOserialno:
INFOimei:
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: T-MOB005
INFObattery-status: good
INFObattery-voltage: 4032mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.480s
Cheers
now that we know that the stock rom flashed .(before brick)
get the 1.50 RUU and try to RUN it
how you do that
phone in fastboot ...connect it to pc and run the RUU.exe
if it still dint worked
then extract the rom.zip form RUU
http://www.htcsensationforum.com/htc-sensation-rooting/how-to-extract-rom-zip-from-ruu/
then keep the rom.zip in adb folder and flash it manually
manual flash steps
1.fastboot erase cache (if its failing ...ignore it)
2.fastboot oem rebootRUU (black screen with silver HTC)
3.fastboot flash zip rom.zip (pastebin the output if failed)
4.fastboot reboot-bootloader (check the bootloader there ..changed or not )
hi ganesh,
latest rom available that i can find (for t-mo uk) is 1.34. That ok?
cheers
EDIT: ok, so trying to run the RUU, it looks like it's going ok, starts sending the ROM to the phone, and then aborts with a ERROR [155]: UNKNOWN ERROR.
Will try the manual steps you gave.
jezash said:
hi ganesh,
latest rom available that i can find (for t-mo uk) is 1.34. That ok?
cheers
Click to expand...
Click to collapse
yes try that first if it fails (both ways )
get the updated RUU
I asked Football and he suggested he could get RUU_Pyramid_TMO_UK_1.50.110.2
Click to expand...
Click to collapse
from football ^
and use that and repeat the rom flash again
hi ganesh,
ok, here's what came back when i tried to flash manually.
C:\adb>fastboot flash zip rom.zip
sending 'zip' (381007 KB)... OKAY [ 51.085s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
FAILED (remote: 44 hboot version check fail)
finished. total time: 103.934s
EDIT:
when I disconnected USB from phone, it also displayed error message: Hboot version is older / Update fail!
will contact football again as you suggested.
2nd EDIT:
my bootloader displays HBOOT-1.27.0000 ... isn't the problem still that even 1.50 has an older HBOOT than this, and hence the rom flash fails?
jezash said:
hi ganesh,
ok, here's what came back when i tried to flash manually.
C:\adb>fastboot flash zip rom.zip
sending 'zip' (381007 KB)... OKAY [ 51.085s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
FAILED (remote: 44 hboot version check fail)
finished. total time: 103.934s
EDIT:
when I disconnected USB from phone, it also displayed error message: Hboot version is older / Update fail!
will contact football again as you suggested.
Click to expand...
Click to collapse
yeah thats expected ...can you try one more thing ..can you just remove the hboot.nb0 file from the rom.zip (have a copy of it somewhere safe ..so that you can add later when required)
EDIT: also you need to edit the android-info.txt file ..change the HBOOT inside with te one you have i.e. 1.27.0000 then make the zip again then try flashing it sorry my bad there wont be HBOOT in the android-info.txt ..just cidnum ,modelid etc etc
then do the flash of rom.zip again
weird. I couldn't find that file in the rom.
the contents are as shown here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT - oh, duh, the longer file name that ends as you said. sorry. will try now.
ok, tried this. unzipped, removed the hboot_Pyramid_8x60_1.17.0011_20110602_signedbyaa.nb0 file, rezipped. followed the four manual flash steps that you suggested, and got the following message in cmd:
C:\adb>fastboot flash zip rom.zip
sending 'zip' (375099 KB)... OKAY [ 50.217s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 100.357s
Football can get me a TMO-UK RUU 1.50. There is a cost, apparently. Hence wondering if there's a reason why 1.50 should work when 1.34 doesn't, give - if i understand correctly - that neither is HBOOT 1.27.

HTC Sensation XE stock on HTC Logo

So my Sensation XE is not Rooted neither S-off ed... I unlocked the boot loader by htc Dev. I installed ClockWorkMod and did a backup. I tyied to installe a fireware and now when i press the power button, the screen gets stuck at the white screen with the HTC text. I restored from CWM, but still the same...And when i try to install a ROM it's say aborted.
I tried to flashboot with the boot.img of the ROM, doesn't work. I try to install a RUU ROM for my phone, it's gives me ERROR. Finally i tried to supercid my HTC with "fastboot oem writecid 11111111 " but looks like my bootloader wont let me supercid because it's gives me
"C:\Android>fastboot oem writecid 11111111
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) pyramid_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.121s]
finished. total time: 1.121s"
Anyone knows what i can do??Do i have to find RUU for my cid (HTC_203) so I can flash anything??
Were you on gingerbread? If so you will need to flash an ICS rom and then flash the boot. IMG or install 4ext recovery and use smart flash. I'm on my phone so I can't link you to the firmware thread but you should be able to find it if you go to the reference thread in the Android development section.
Sent from my HTC Sensation 4G using xda app-developers app
Yes you need the correct firmware for the Rom, example: ics or 4.0.3 roms run on firmware 3.32,or 3.33 ( the newest version) anything Gingerbread runs on a different firmware. So if you flashed a ICS firmware you need a ICS Rom. Also read the guide to flashing roms with S On. You can find it here I'll include link for you. This guide will help you out. http://forum.xda-developers.com/showthread.php?t=1631861
Sent from my HTC Sensation 4G using xda premium
I tried to flashboot with the boot.img of the ROM, doesn't work
Click to expand...
Click to collapse
what do you mean by that ?
what error you got ?
when you flash a rom while being SON ..you need to flash the boot.img separately if you are using CWM recovery
to flash the boot.img pf the rom separately
first connect your phone to pc from bootloader (phone should read fastboot usb after this)
then copy the boot.img to the adb/fastboot folder (the folder where you have adb.exe and fastboot.exe)
then open command window there (if windows hold shift + right click ->open command window here)
then type this command
fastboot flash boot boot.img
then reboot using
fastboot reboot
it should boot
also check the guide linked by realisis
Thanks a lot guys i followed the instructions of the thread u given to me and it did works I thinks my CMW Recovery wasn't working properly.
thanks for thi this thread itry

Trying to flash stock rom via RUU - Error [155]

I'm stuck in a bootloop / soft brick and would like to go back to stock rom / RUU
Phone is: HTC One S - UK - Vodafone
I'm tried using:
RUU_Ville_U_Vodafone_UK_1.78.161.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258386_signed
RUU_Ville_U_Vodafone_UK_1.53.161.3_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251482_signed
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
Always getting the same error message:
ERROR(155): UNKNOWN ERROR
The ROM Update Utility cannot update your Androidphone
Please get the correct ROM Update Utiility and try again
Pretty obvious what I should do
But cant seem to be able to locate the correct RUU file
Any idea?
Many thanks
Cedric
What is your current software version?
You can change your CID to HTC__001 and then flash unbranded 2.31 (the one you already have)
Did you relock your bootloader?
Sent from my HTC One S using xda premium
Yes I did, Thank you
mikeyinid said:
Did you relock your bootloader?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
cid: VODAP001
Could you pleaase confirm how to change my CID?
Tried fastboot oem writecid HTC__001 and that blocked bootloader...
Thank you!
Error message
C:\fastboot oem writecid HTC__001
...
(bootloader) ville_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) 902910 902E20
FAILED (status read failed (Too many links))
finished. total time: 1.271s
Since I posted this morning
I also tried to change CID via adb shell but it doesnt work - error message = error: device not found
And I allowed USB debugging + fastboot recognise USB connection
Any idea? really lost now!!
Thank you very much
usaff22 said:
What is your current software version?
You can change your CID to HTC__001 and then flash unbranded 2.31 (the one you already have)
Click to expand...
Click to collapse
Any luck? Haven't any progress...
Many thanks
cplessier said:
Any luck? Haven't any progress...
Many thanks
Click to expand...
Click to collapse
I had a similar problem with my orange branded one s but got it up and running by doing the following :
unlock bootloader
install twrp recovery
boot into recovery (must be in recovery not bootloader or adb shell will not work)
change orange cid to generic cid http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
flash stock recovery
relock bootloader
install latest european ruu
Hope this helps
I managed to change the CID to Super CID
But still getting Error 155 when trying to install RUU
Any other idea?
Many thanks
cplessier said:
I managed to change the CID to Super CID
But still getting Error 155 when trying to install RUU
Any other idea?
Many thanks
Click to expand...
Click to collapse
If your sure the cid was sucessfully changed (i used HTC_001) and you flashed stock recovery then relocked bootloader im all out of ideas. thats what worked for me.
cplessier said:
I managed to change the CID to Super CID
But still getting Error 155 when trying to install RUU
Any other idea?
Many thanks
Click to expand...
Click to collapse
What is error 155?
usaff22 said:
What is error 155?
Click to expand...
Click to collapse
Error 155 gets when either your bootloader is locked or u r using the wrong RUU
If you updated to jelly bean , sense 4+ and then rooted your ONE S and then installed other roms like CM10, etc, you will get error 155 if you try to use any RUU. Thats because your hboot is updated when upgrading to sense 4+,JB.
Thus to revert back to stock....
1. get stock ICS Sense 4.1 ROM,
2. flash stock recovery.
3. Use OTA update to jelly bean,Sense 4+.
4. Factory reset your phone to remove any non-stock stuff from the ROM.
5. you have STOCK Sense 4+!!
6. then if you want you can relock boot loader .( but I havent tried it, might cause problem)
Your hboot won't be updated unless it's a ota or a ruu am I right eg I was on 4.04 then rooted and installed trickdroid but I am still on the hboot that came with 4.04 ruu.
Sent from my HTC One S using xda premium
Same problem: Error 155: Unknown Error
I'm on Vodafone IE.
Successfully changed CID to HTC__001, restored stock, relocked bootloader and I can't install any RUU, tried
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed
Any ideas?
OK
managed to update with
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
cplessier said:
I'm stuck in a bootloop / soft brick and would like to go back to stock rom / RUU
Phone is: HTC One S - UK - Vodafone
I'm tried using:
RUU_Ville_U_Vodafone_UK_1.78.161.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258386_signed
RUU_Ville_U_Vodafone_UK_1.53.161.3_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251482_signed
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
Always getting the same error message:
ERROR(155): UNKNOWN ERROR
The ROM Update Utility cannot update your Androidphone
Please get the correct ROM Update Utiility and try again
Pretty obvious what I should do
But cant seem to be able to locate the correct RUU file
Any idea?
Many thanks
Cedric
Click to expand...
Click to collapse
Wipe everything.Should be able to flash CyanogenMod 10. After that, change back the CID to VODAP001 (mmcblk0p4 and build.prop).

HTC One ME - no rom - twrp recovery installed - bootloader unlocked - s-on

Hi:
I have pretty much explained my position in header. so i rooted my htc one me m9ew and on restart it went to bootloop. i flashed recovery from there. now even if i try to flash any rom its still on bootloop. keeping in mind my bootloader is unlocked and S-ON. what should i do? any way to keep this phone alive?
Try Htc Ruu or the software from Htc i thinknit might be emergency flash but theirs something like that
king786 said:
Try Htc Ruu or the software from Htc i thinknit might be emergency flash but theirs something like that
Click to expand...
Click to collapse
Thanks King:
I have managed to install custom ROM basically designed for HTC One M9+ since there is no custom rom for htc one ME edition. this new clean slate rom gives no signal and very buggy. in short i cant run normal phone operations on this rom. i tried installing RUU from htc_fastboot but it gives error 19 and i am unable to flash. i have tried many sources for this RUU file but in vain. any suitable suggestions to make this phone operational will be highly appreciated.
One more thing, do i need to relock bootloader to flash firmware???? getting following error:
(bootloader) HOSD CL#549681
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAILED (remote: 19: fail to flash via downloadzip)
zuhairqadir said:
Thanks King:
I have managed to install custom ROM basically designed for HTC One M9+ since there is no custom rom for htc one ME edition. this new clean slate rom gives no signal and very buggy. in short i cant run normal phone operations on this rom. i tried installing RUU from htc_fastboot but it gives error 19 and i am unable to flash. i have tried many sources for this RUU file but in vain. any suitable suggestions to make this phone operational will be highly appreciated.
Click to expand...
Click to collapse
Try installing something through recovery another functional rom might not be what u want but get that running and then do what u are trying or try its recovery menu.
One of those should work if not try to look for a solution in one of the threads must be something here
I have managed to install RUU its working perfect but just there is no signals and no imei in OS, however, i can see it in boot menu. any advice?

Categories

Resources