HTC Sensation blocked on Bootloader - HTC Sensation

Hello,
I have a HTC Sensation who is blocked on Bootloader. It is on S ON (HBOOT-1.17.0008).
It was bricked because I do a wrong S ON..
I followed this tuto: http://forum.xda-developers.com/showthread.php?t=1522351
and now I have acces to the bootloader.
Thanks

Up

If you have access to the bootloader, you can use a PB58IMG to install a stock ROM.

axox93 said:
Hello,
I have a HTC Sensation who is blocked on Bootloader. It is on S ON (HBOOT-1.17.0008).
It was bricked because I do a wrong S ON..
I followed this tuto: http://forum.xda-developers.com/showthread.php?t=1522351
and now I have acces to the bootloader.
Thanks
Click to expand...
Click to collapse
try this thread
http://forum.xda-developers.com/showthread.php?t=1469296
but read will next time plzzz

I tried to install a stock rom but it makes me 132 error.
Then, to make a recovery I also tried I receive this error message: FAILED (remote: verify signatures fail)
For PG58IMG, on reboot nothing changes.

up

Do HTC Dev unlock.
Take a stock Gingerbread PG58IMG and unzip it.
Use fastboot to flash system & boot images.

When I type fastboot oem get_identifier_token for unlock I receive this error message: ... INFO [ERR] Command error!
If you need more info of my htc :
INFOversion: 0.5
INFOversion-bootloader: 1.17.0008
INFOversion-baseband: 10.14.9035.01_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.45.163.4
INFOserialno: SH15YV801693
INFOimei: 356440045021423
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: VODAP203
INFObattery-status: good
INFObattery-voltage: 3800mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 3f6ba3d6
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.054s

axox93 said:
When I type fastboot oem get_identifier_token for unlock I receive this error message: ... INFO [ERR] Command error!
If you need more info of my htc :
INFOversion: 0.5
INFOversion-bootloader: 1.17.0008
INFOversion-baseband: 10.14.9035.01_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.45.163.4
INFOserialno: SH15YV801693
INFOimei: 356440045021423
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: VODAP203
INFObattery-status: good
INFObattery-voltage: 3800mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 3f6ba3d6
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.054s
Click to expand...
Click to collapse
finding RUU for you based on your cid is difficult
as you are on 1.17 HBOOT still then you can change your CID
so we will change the CID to europe unbranded one (HTC__001) or supecid which ever is sucess (note down your original CID)
and then will flash a EUROPE GB RUU (which will bring back your phone to complete life)
first to change cid
supercid:
fastboot oem writecid 11111111
if this is success then everything is fine...you can download any GB RUU version
(software version must be >= 1.45.163.4)
otherwise this should work
fastboot oem writecid HTC__001
then get the GB european RUU (again software version should be >= 1.45.163.4)
RUU threads
http://www.filefactory.com/f/c87a2330449af512/
http://www.shipped-roms.com/index.php?category=android&model=Pyramid
http://goo.im/stock/pyramid/ruu
if XE then get the RUU along this line " RUU_Pyramid_LE_hTC_" (LE represents xe phone)
if normal get something along this line "RUU_Pyramid_hTC_"
once you downloaded the RUU
keep the phone in fastboot mode..connect to pc and then
run the RUU then..everything should go smooth

Ah, problem there is your HBOOT is too old for HTC Dev unlock, it's the original shipping HBOOT, HTC updated it to work with their unlocking method.
Regarding your stock ROM installing, error 132 means the ROM isn't correct for your CID. This might cause a problem as I can't for the life of me find an SFR RUU anywhere.

Ganeshp : I have this message error :/
C:\adb>fastboot oem writecid 11111111
... INFO pyramid_init_sd, SD card already power on
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.167s]
finished. total time: 0.167s
C:\adb>fastboot oem writecid HTC__001
... INFO pyramid_init_sd, SD card already power on
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.170s]
finished. total time: 0.170s
Rusty! : I'll try to find a rom for my cid

Now i have a error 140 : error of bootloader with this rom
RUU_Pyramid_Vodafone_FR_1.27.163.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_191976_signed

Annoyingly, whilst you have the right CID, your mainver is newer than that ROM, you need to find one that's 1.45.163.4 or newer

Rom Vodafone_FR newer than 1.45.163.4 if I understand.
I put a research
EDIT: It seems that there is only updated to version 1.45.163.4 has higher and no roms :/

Yep that's correct, you could always try getting it repaired under warranty... I can't find a suitable RUU anywhere

Unfortunately I do not have the invoice so I can not go into collateral :/

I bought a faulty phone on Tuesday from a random advert. On Wednesday I called HTC's warranty service to tell them the fault, on Thursday they picked it up and (according to their tracker) they're repairing it today.
I sure as hell didn't have a receipt for it

can you check the cid once more?
fastboot getvar cid

I am in France, perhaps it's not the same, he did not want
C:\adb>fastboot getvar cid
cid: VODAP203
finished. total time: 0.006s

axox93 said:
I am in France, perhaps it's not the same, he did not want
C:\adb>fastboot getvar cid
cid: VODAP203
finished. total time: 0.006s
Click to expand...
Click to collapse
ask Football for the RUU...he is the OP in pyramid shipped rom collection thread
give him all the details mainly your cid(country and carrier) and software version
i believe he can get one as long as it is GB

Related

help with s-on

Can someone please help, I'm truly stuck here.
I have followed the guide here..
http://forum.xda-developers.com/show....php?t=1460713
I have managed to remove the revolutionary logo, and all was good. I then attempted to install the following RUU...
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release_177977_signed
Went through all the prompts but the program "hung" at the sending screen. After around an hour I pulled the usb cable, yay the phone still boots. However I was still at the old HBOOT (cant remember the numbers 6.0.0002 or something ) and with the custom rom.
Though this might be a problem with the RUU... NAY.
I have since tried he following..
RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed
RUU_Saga_O2_UK_1.31.206.1_Radio_20.28b.30.0805U_38 .03.02.14_M_release_178935_signed
All with the same results.
So I downgraded the hboot manually to 0.98.0002 and tried them all again. Still no luck.
The reason I have tried the different RUU is that it was originally from carphone warehouse. Their phones are generally unbranded so assumed it would be a standard euro ruu.
Please help.
I really don't get what the problem is. Removing the "Revolutionary" logo isn't the same as being S-ON. But check out the link below to see if it helps.
forum.xda-developers.com/showthread.php?t=1549636
@pttynan
PLease run the fastboot command "fastboot getvar all" remember to remove your imei and serial from your post.
Then I will direct you to a solution
foX2delta said:
@pttynan
PLease run the fastboot command "fastboot getvar all" remember to remove your imei and serial from your post.
Then I will direct you to a solution
Click to expand...
Click to collapse
Hi Fox2delta. The command gives the following.
INFOversion: 0.5
INFOversion-bootloader: 0.98.2000
INFOversion-baseband: 38.03.02.11
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.28.401.1
INFOserialno: HT13Jxxxxxxxx
INFOimei: 3550670xxxxxxxxx
INFOproduct: saga
INFOplatform: HBOOT-7230
INFOmodelid: PG8810000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 4136mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: ENG
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 7b851d36
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.031s
Dont suppose anyone has any thoughts on this? Carphone flat out refused to touch it once the noticed S-OFF

[Q] Weird Problem With HTC Sensation XE

Hello guys
I have a problem with my HTC Sensation XE.
I jtag'ed the phone with RIFF Jtag box (changed IMEI, s-off'ed and rewrote boot). After that the phone started to reset itself over and over. After that by using RIFF box, I erased, rewrote boot and tried 5 or 6 different RUU's.
Now, I can open the phone (it vibrates and I can hear HTC opening voice) but the screen is completely black. I tried to send a call to this device and it received the call but I could not answer the call. So everything but screen looks like working.
Screen problem occured after jtag so I think it is not a hardware issue but I am not sure.
I am searching for 3 weeks now but I could not find a satisfactory answer. Can you help me to fix this problem. Any ideas? suggestions? Is there something that I might do wrong?
Thanks for your answers and sorry for my bad English and terminology.
kmrock said:
Hello guys
I have a problem with my HTC Sensation XE.
I jtag'ed the phone with RIFF Jtag box (changed IMEI, s-off'ed and rewrote boot). After that the phone started to reset itself over and over. After that by using RIFF box, I erased, rewrote boot and tried 5 or 6 different RUU's.
Now, I can open the phone (it vibrates and I can hear HTC opening voice) but the screen is completely black. I tried to send a call to this device and it received the call but I could not answer the call. So everything but screen looks like working.
Screen problem occured after jtag so I think it is not a hardware issue but I am not sure.
I am searching for 3 weeks now but I could not find a satisfactory answer. Can you help me to fix this problem. Any ideas? suggestions? Is there something that I might do wrong?
Thanks for your answers and sorry for my bad English and terminology.
Click to expand...
Click to collapse
hmm you did some advanced stuff ...pushing boot and other files using jtag ...can you now go into bootloader ? also there too the screen is blank ?
if you can go to bootloader ..why not try running ruu manually? (not jtag this time )
ganeshp said:
hmm you did some advanced stuff ...pushing boot and other files using jtag ...can you now go into bootloader ? also there too the screen is blank ?
if you can go to bootloader ..why not try running ruu manually? (not jtag this time )
Click to expand...
Click to collapse
Hello, first of all, thanks for your answer.
Unfortunately now same black screen appears in the bootloader screen. Before erase operation I could go into the bootloader but after erase, I can not see the screen.
kmrock said:
Hello, first of all, thanks for your answer.
Unfortunately now same black screen appears in the bootloader screen. Before erase operation I could go into the bootloader but after erase, I can not see the screen.
Click to expand...
Click to collapse
Looks like some important partition got wiped.. So ruu flash is best choice
Can you confirm that the device in bootloader
By typing this command in the command prompt from your adb folder (assuming that you have adb/fastboot setup)
And you need to connect your device to pc though
fastboot devices
(the phone serial number should be shown)
If it's working fine
Can you post the complete output of the following command too?
fastboot getvar all ( except imei and serial number)
Then we can see what state your current device is in and can determine which RUU to run
Sent from my pyramid.. Through blazing fast sonic waves
kmrock said:
Hello, first of all, thanks for your answer.
Unfortunately now same black screen appears in the bootloader screen. Before erase operation I could go into the bootloader but after erase, I can not see the screen.
Click to expand...
Click to collapse
Did you JTAG it yourself? if so when you reassembled the phone did you make sure that the 2 cables you had to disconnect from the cpu mainboard were properly reconnected?
Jonny said:
Did you JTAG it yourself? if so when you reassembled the phone did you make sure that the 2 cables you had to disconnect from the cpu mainboard were properly reconnected?
Click to expand...
Click to collapse
Yes, check this.
It doesn't sound like you flashed any partitions that shouldn't have been touched / would affect the display. And if so, it sounds like it'd be a partition not included in RUUs.
Hello everybody, thanks for your answers.
Jonny said:
Did you JTAG it yourself? if so when you reassembled the phone did you make sure that the 2 cables you had to disconnect from the cpu mainboard were properly reconnected?
Click to expand...
Click to collapse
Yes I JTAGd it myself (with the owner of the RIFF BOX with me). I double checked all the cables and sockets and everything seems fine.
ganeshp said:
Looks like some important partition got wiped.. So ruu flash is best choice
Can you confirm that the device in bootloader
By typing this command in the command prompt from your adb folder (assuming that you have adb/fastboot setup)
And you need to connect your device to pc though
fastboot devices
(the phone serial number should be shown)
If it's working fine
Can you post the complete output of the following command too?
fastboot getvar all ( except imei and serial number)
Then we can see what state your current device is in and can determine which RUU to run
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
Here is the output:
Code:
C:\Windows\system32>fastboot devices
************ fastboot
C:\Windows\system32>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.27.0000
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.32.401.105
INFOserialno: ************
INFOimei: ***************
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG58*****
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 4201mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.505s
Thanks for your help.
kmrock said:
Hello everybody, thanks for your answers.
Yes I JTAGd it myself (with the owner of the RIFF BOX with me). I double checked all the cables and sockets and everything seems fine.
Here is the output:
Code:
C:\Windows\system32>fastboot devices
************ fastboot
C:\Windows\system32>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.27.0000
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.32.401.105
INFOserialno: ************
INFOimei: ***************
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG58*****
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 4201mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.505s
Thanks for your help.
Click to expand...
Click to collapse
ok the HTC__032 is of east europe
so try this RUU
(run the ruu on pc with phone connected in bootloader mode (check using fastboot devices))
http://www.filefactory.com/file/70cre7fl6rol/n/RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105_R2_Radio_11.69.3504.00U_11.22.3504.07_M_release_253443_signed.exe
if cid failed error came
then change the cid to HTC__001 (two underscores remember)
fastboot oem writecid HTC__001
fastboot reboot-bootloader
fastboot getvar cid (verify the cid from the output of this command)
then run the same RUU again
Hello
I downloaded the file and installed it successfully (no cid failed error)
However same behavior continues. Here is the fastboot getvar all output:
Code:
C:\Windows\system32>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.29.0000
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.32.401.105
INFOserialno: -------------
INFOimei: ---------------
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG58*****
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 4213mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 705f86f6
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Any ideas? suggestions?
Thanks
kmrock said:
Hello
I downloaded the file and installed it successfully (no cid failed error)
However same behavior continues. Here is the fastboot getvar all output:
Code:
C:\Windows\system32>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.29.0000
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.32.401.105
INFOserialno: -------------
INFOimei: ---------------
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG58*****
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 4213mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 705f86f6
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Any ideas? suggestions?
Thanks
Click to expand...
Click to collapse
If ruu didn't solved the problem then the digitizer connections were not made proper... Or hardware issue
Sent from my pyramid.. Through blazing fast sonic waves
ganeshp said:
If ruu didn't solved the problem then the digitizer connections were not made proper... Or hardware issue
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
Thanks for your efforts. I disassembled and looked through all sockets and hardware but everything looks fine. If I insert a sim card and start the device it opens. Also it receives calls and reflects to the volume buttons. But whatever I did with touchscreen, I could not get a reaction. So both screen and digitizer won't work.
Thanks for your answers.

[Q] Problems installing firmware

Hello, sry if this has already been askedbut I'm a noob so... Untill now I had cyanogenmod 7.1 on my sensation and i wanted to switch to OpenSensation but I needed to install the latest firmware for that! So I tried doing what they said on theandroidsoul.com/how-to-flash-pg58img-zip-ics-firmware-on-htc-sensation/ but had no success. Now every time i try to start the phone it just gets stuck at the cyanogenmod9 boot animation! I tried restoring from NANDroid backup but then it gets stuck on the cyanogenmod7 boot animation!
If anyone could help me fix this I'd be very grateful!
EDIT: I also can't install cyanogenmod 7.1 again!
mankiboss said:
Hello, sry if this has already been askedbut I'm a noob so... Untill now I had cyanogenmod 7.1 on my sensation and i wanted to switch to OpenSensation but I needed to install the latest firmware for that! So I tried doing what they said on theandroidsoul.com/how-to-flash-pg58img-zip-ics-firmware-on-htc-sensation/ but had no success. Now every time i try to start the phone it just gets stuck at the cyanogenmod9 boot animation! I tried restoring from NANDroid backup but then it gets stuck on the cyanogenmod7 boot animation!
If anyone could help me fix this I'd be very grateful!
Click to expand...
Click to collapse
more details please
complete HBOOT details
also if you have adb/fastboot installed
then post the output of this command except imei and serial number
fastboot getvar all
once you post the output
then we can guide you further
S-OFF, HBOOT-1.27.1100, RADIO-10.14.9035.01_M
C:\Users\Roncevic\Downloads\ADB_Fastboot_Windows>fastboot getvar all
< waiting for device >
INFOversion: 0.5
INFOversion-bootloader: 1.27.1100
INFOversion-baseband: 10.14.9035.01_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.45.531.1
INFOserialno:
INFOimei:
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: HTC__032
INFObattery-status: low
INFObattery-voltage: 3497mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.491s
C:\Users\Roncevic\Downloads\ADB_Fastboot_Windows>
mankiboss said:
S-OFF, HBOOT-1.27.1100, RADIO-10.14.9035.01_M
C:\Users\Roncevic\Downloads\ADB_Fastboot_Windows>fastboot getvar all
< waiting for device >
INFOversion: 0.5
INFOversion-bootloader: 1.27.1100
INFOversion-baseband: 10.14.9035.01_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.45.531.1
INFOserialno:
INFOimei:
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: HTC__032
INFObattery-status: low
INFObattery-voltage: 3497mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.491s
C:\Users\Roncevic\Downloads\ADB_Fastboot_Windows>
Click to expand...
Click to collapse
thanks that explains what caused the problem
I'll try to explain it briefly
now typically our sensation can be broken into three parts like (it may not be 100% correct but its an analogy to explain the firmware things)
hardware/device ---------------->>> firmware(HBOOT + radio) --------------------->>>ROM (ICS/GB)
so for it to run properly
you need to have GB firmware for GB rom (GB- ginger bread)
or ICS firmware for ICS rom
otherwise it wont work
now in your case
you hboot is 1.27.1100 (ICS one) but the radio is still of GB one (10.14.xx)
and
from "INFOversion-main: 1.45.531.1" this we can say that you are running a GB os ..and i think its cm7.1 that you restored
now you might have understood why you are looping
your firmware upgrade is half complete ( 1 part is of ICS one and other is of GB one)
and you are running GB rom..which wont work
so now you have two ways out
1.to have cm9 (ICS rom)
you need to properly flash the 3.32 firmware first (ICS compatible)
that you can find it here (get the universal 3.32 firmware )
universal firmwares
then flash the cm9 via recovery ..voila you are done
(for safe side you can check you flashed fw properly or not ...hboot should be 1.27.xx and radio should be 11.xx )
2.to have back the cm7.1 (GB rom)
here you need to flash the GB firmware
get the universal 1.17 firmware from the above linked thread and flash it
(verify the 1.17 firmware by looking at hboot (1.17.xx) and radio (10.xx))
then restore you cm7.1 backup ..and you are done again
NOTE: remember to remove the PG58IMG zip file from sdcard after flashing otherwise you cant go into bootloader/fastboot
What he said do that as well you might want to get supercid it makes things easier...
Swyped From My Sensation.
I tried doing what you said but i it says wrong CID and sometimes battery voltage too low! If i really got the wrong file how can i put the right file on the SD card with fastboot or sth and do I need to change the battery? thx
mankiboss said:
I tried doing what you said but i it says wrong CID and sometimes battery voltage too low! If i really got the wrong file how can i put the right file on the SD card with fastboot or sth and do I need to change the battery? thx
Click to expand...
Click to collapse
get the 3.32 universal firmware (NON TMOUS) one and flash it
if you want gingerbread rom flash the 1.17 universal firmware (NON TMOUS one)
firmware thread
that should solve your wrong cid problem
if it still persists
then do a supercid
commands to supercid
1.fastboot getvar cid (store/remember your original cid)
2.fastboot oem writecid 11111111 (eight ones)
3.fastboot reboot-bootloader
4.fastboot getvar cid (verify your cid now)
I did the superCID but it still says battery voltage too low. Do I have to change the battery?
mankiboss said:
I did the superCID but it still says battery voltage too low. Do I have to change the battery?
Click to expand...
Click to collapse
of course you need to charge the battery
if while doing firmware upgrade ..your phone got switched off ..due to less battery ..it can potentially lead to a brick
ALWAYS when flashing a firmware ..you need to have enough battery (atleast 40-50% imho)

[Q] Bootloop & no recovery

Hi guys, i have been trying to restore my phone in the last ten days. It was stock, until someday it went in a bootloop. I changed the battery because i left it in a drawer for a while. I have tried everything i could find on the net, but nothing worked. At the moment, i don' t remember what i flashed lately, but it' s stuck in the white HTC screen with the green logo.
I tried ruu and now it shows:
Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
eMMC-boot
Jan 13 2012
When in fastboot :C:\adb>fastboot getvar all i get this:
INFOversion: 0.5
INFOversion-bootloader: 1.27.1100
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.106
INFOserialno: SH16WV805444
INFOimei: 358313040178522
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 3812mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
It cannot get in recovery.
Any ideas which way should i go? Or should i just give up and move to WP8 with a Nokia ?
Any help will be appreciated.
Jonnyvla said:
Hi guys, i have been trying to restore my phone in the last ten days. It was stock, until someday it went in a bootloop. I changed the battery because i left it in a drawer for a while. I have tried everything i could find on the net, but nothing worked. At the moment, i don' t remember what i flashed lately, but it' s stuck in the white HTC screen with the green logo.
I tried ruu and now it shows:
Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
eMMC-boot
Jan 13 2012
C:\adb>fastboot oem unlock
... INFO[ERR] Command error !!!
OKAY [ 0.022s]
finished. total time: 0.022s
C:\adb>m2sd cmdalvik enable
'm2sd' is not recognized as an internal or external command,
operable program or batch file.
When in fastboot :C:\adb>fastboot getvar all i get this:
INFOversion: 0.5
INFOversion-bootloader: 1.27.1100
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.106
INFOserialno: SH16WV805444
INFOimei: 358313040178522
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 3812mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
C:\adb>
It cannot get in recovery.
Any ideas which way should i go? Or should i just give up and move to WP8 with a Nokia ?
Any help will be appreciated.
Click to expand...
Click to collapse
from bootloader if you choose recovery what does it show you?
Hi rzr86,
thank you for the quick reply. It goes again to the white screen with the green HTC logo. I tried flashing 4ext recovery from a thread in here through adb, but it does the same thing. Shows the white screen HTC and then boots again & again...
Jonnyvla said:
Hi rzr86,
thank you for the quick reply. It goes again to the white screen with the green HTC logo. I tried flashing 4ext recovery from a thread in here through adb, but it does the same thing. Shows the white screen HTC and then boots again & again...
Click to expand...
Click to collapse
try to flash a different recovery such as cwm or twrp
I tried flashing CWM, i got this in adb and when i tried to get in recovery mode i saw again the white screen, just like before.
C:\adb>fastboot flash recovery cwm-4.0.1.4-pyramid.img
sending 'recovery' (4724 KB)... OKAY [ 1.229s]
writing 'recovery'... OKAY [ 5.102s]
finished. total time: 6.334s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 3.273s]
finished. total time: 3.273s
In Hboot i get this message:
HBOOT
SD Checking...
Loading...[PG58DIAG.zip]
No image!
Loading...[PG58DIAG.nbh]
No image or wrong image!
Loading...[PG58IMG.zip]
No image!
Loading...[PG58IMG.nbh]
No image or wrong image!
Loading...[PG58IMG.tar]
No image!
Loading...[PG58IMG.aes]
No image!
Loading...[PG58IMG.enc]
I flashed Twrp recovery and when i try to get in i go back to the bootloop!
My SDcard is now formated, because i lost the last one and bought a new one 8GB.
Any hint which way i should follow?
Jonnyvla said:
I tried flashing CWM, i got this in adb and when i tried to get in recovery mode i saw again the white screen, just like before.
C:\adb>fastboot flash recovery cwm-4.0.1.4-pyramid.img
sending 'recovery' (4724 KB)... OKAY [ 1.229s]
writing 'recovery'... OKAY [ 5.102s]
finished. total time: 6.334s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 3.273s]
finished. total time: 3.273s
In Hboot i get this message:
HBOOT
SD Checking...
Loading...[PG58DIAG.zip]
No image!
Loading...[PG58DIAG.nbh]
No image or wrong image!
Loading...[PG58IMG.zip]
No image!
Loading...[PG58IMG.nbh]
No image or wrong image!
Loading...[PG58IMG.tar]
No image!
Loading...[PG58IMG.aes]
No image!
Loading...[PG58IMG.enc]
I flashed Twrp recovery and when i try to get in i go back to the bootloop!
My SDcard is now formated, because i lost the last one and bought a new one 8GB.
Any hint which way i should follow?
Click to expand...
Click to collapse
try to use a ruu.exe
http://fileom.com/v8xia7c0mn02/RUU_....24A.3504.31_M_release_266172_signed.exe.html
see here on how to use it
http://forum.xda-developers.com/showthread.php?t=1672425
don't worry you will remain on S-OFF

help needed my htc sv wont unlockboot loader

hello brother.s
i hope every one oky
i have htc one sv
wont unlockboot loader
cant go to recovery
still
hung to fastbootmode
i tried with correct bin file
but cant unlock
C:\android>
C:\android>fastboot getvar cid
cid: HTC__J15
finished. total time: 0.002s
C:\android>fastboot getvar mid
mid: PL8010000
finished. total time: 0.002s
C:\android>
C:\android>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 2.21.0000
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.11.415.10
INFOversion-misc: PVT SHIP S-ON
INFOserialno: HT313TP04107
INFOimei: ****************************
INFOmeid:
INFOproduct: k2_ul
INFOplatform: HBOOT-8930
INFOmodelid: PL8010000
INFOcidnum: HTC__J15
INFObattery-status: good
INFObattery-voltage: 3761mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-2bb255c2
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.140s
C:\android>help me please thanx
regards
Same problem !!!
Hi all !!
Hope someone can help me too i'm lost with this device !!
It stuck in bootloader with "LOCKED" Status
K2_UL PVT SHIP S-ON RL
HBOOT-2.00.000
eMMC-boot
Mar 14 2013,22:10:43:-1
i tried to unlock bootloadder with htcdev with the correct unlock_code.bin but when the phone reboots it returns to fastboot screen
pleaaaase HEEELP !!
Did u slove u prob
Sent from my DROID RAZR HD using XDA Free mobile app
MGBsystem said:
Hi all !!
Hope someone can help me too i'm lost with this device !!
It stuck in bootloader with "LOCKED" Status
K2_UL PVT SHIP S-ON RL
HBOOT-2.00.000
eMMC-boot
Mar 14 2013,22:10:43:-1
i tried to unlock bootloadder with htcdev with the correct unlock_code.bin but when the phone reboots it returns to fastboot screen
pleaaaase HEEELP !!
Click to expand...
Click to collapse
nokia alkng said:
Did u slove u prob
Sent from my DROID RAZR HD using XDA Free mobile app
Click to expand...
Click to collapse
Go to HTCdev.com and complete the Unlock my bootloader procedure again to get a new Unlock_code.bin.
If you've already done that and it didn't help then you need to flash the correct firmware to refresh your hboot then it should unlock just fine. :good:
@nokia alkng also I noticed this in your Getvar
Code:
INFOversion-baseband: N/A
again flashing the firmware may fix that but if not then there's a hardware problem with the baseband processor.
Danny201281 said:
Go to HTCdev.com and complete the Unlock my bootloader procedure again to get a new Unlock_code.bin.
If you've already done that and it didn't help then you need to flash the correct firmware to refresh your hboot then it should unlock just fine. :good:
@nokia alkng also I noticed this in your Getvar
Code:
INFOversion-baseband: N/A
again flashing the firmware may fix that but if not then there's a hardware problem with the baseband processor.
Click to expand...
Click to collapse
thanx aloot to replay
can u try to gave me that firmware
i will be happy
thanx advance

Categories

Resources