Related
Hi to hall.
I bought an HTC Sensation with HBOOT 1.17. I've rooted it with the Official LEAK ROM, Sense 3.5 "2.08.401.1_stock_rooted_signed-v0.3.zip" ad S-OFF it.
Unfortunately I had to follow the procedure of S-ON to send back the phone in technical assistance.
Now I have my phone with display repaired, but the assistance have upgrated my HBOOT in new version 1.19.
These are bootloader informations:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.19.0000
eMMC-boot
Sep 6 2011,19:13:20
If i try the S-OFF with the revolutionary.io site it tell me tath the 1.19 is not supported.
How can i have the permanent root and the S-OFF?
Thank's and merry christmas to everybody.
can't you run RUU to reflash hboot to early version you use it to flash the revolutionary.io hboot back to stock
I'm a newbie, have you a guide or an how-to url?
Tanks
Sent from my HTC Sensation Z710e using XDA App
UP!
Nobody knows a solution to my problem?
You could try to flash back to hboot 1.17, check http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22.
Just place the file (it must be called PG58IMG.zip) on the root folder of your sd-card, triple check md5 and then boot into bootloader to flash it.
If that works use should be able to S-Off.
Edit: Here are the same instructions (it's about firmware flashing but it's the same method, my reference is also mentioned there)
Edit2: I think Madenssblade is talking about flashing back to an earlier STOCK rom, see here, you can try that if the above does not work
Thank's a lot!
A question, if i launch the downgrade, it will destroy all my data?
If you flash the new ROM, yes (but not the data on your sdcard).
If you succeed in flashing the new hboot, no.
Good luck, I don't know if this all works given your device is S-ON, but it's worth a try (your HBOOT says unlocked).
A small update.
Yesterday i installed the app 4EXT Recovery Control and i noticed with surprise that i still root; perhaps it was sleeping in the state.
I cannot yet find a guide to give the S-OFF at HBOOT 1.19 .
ziopippo said:
I'm a newbie, have you a guide or an how-to url?
Tanks
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Hi, try to downgrade your firmware. I am not sure but it may work. Try the following.
A. Downgrading the firmware
Visit this thread. Download v1.17 firmware . Are u having superCID? If so then you can download any v1.17 firmware else choose that firmware file which includes your CID. If you are not sure about your CID follow that same thread to find it.
Flash the firmware by the following method.
1. place Firmware PG58IMG.zip (v1.17) on the root of your sdcard.
2. Remove the battery.
3. Wait a minute.
4. Put the battery.
5.Press power+ volume- key together.
6.Phone will boot into bootloader.
7.Follow the instruction on your phone screen.
If the firmware downgrade successfull then Perform Revolutionary method to make your device S-OFF. If this method does not work try flashing an RUU.
B. Flashing an older RUU (HBOOT 1.17 )
Find a suitable RUU from here.
If RUU Flashing fails, boot into bootloader. Then retry to flash the RUU.
Then try to follow Revolutionary method.
musarraf172 said:
Hi, try to downgrade your firmware. I am not sure but it may work. Try the following.
A. Downgrading the firmware
Visit this thread. Download v1.17 firmware . Are u having superCID? If so then you can download any v1.17 firmware else choose that firmware file which includes your CID. If you are not sure about your CID follow that same thread to find it.
Flash the firmware by the following method.
1. place Firmware PG58IMG.zip (v1.17) on the root of your sdcard.
2. Remove the battery.
3. Wait a minute.
4. Put the battery.
5.Press power+ volume- key together.
6.Phone will boot into bootloader.
7.Follow the instruction on your phone screen.
If the firmware downgrade successfull then Perform Revolutionary method to make your device S-OFF. If this method does not work try flashing an RUU.
B. Flashing an older RUU (HBOOT 1.17 )
Find a suitable RUU from here.
If RUU Flashing fails, boot into bootloader. Then retry to flash the RUU.
Then try to follow Revolutionary method.
Click to expand...
Click to collapse
I have tried this process several times but my HTC says "Parsing PG58IMG.zip"
could this be because i am S-ON? i am trying to downgrade from 1.23
slimldj said:
I have tried this process several times but my HTC says "Parsing PG58IMG.zip"
could this be because i am S-ON? i am trying to downgrade from 1.23
Click to expand...
Click to collapse
Did you try Flashing an RUU?
Sent from my HTC Sensation using Tapatalk
musarraf172 said:
Did you try Flashing an RUU?
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
yes. but when i try to, the phone enters the "black htc screen" and after a couple of minutes i get error 155 from the RUU saying i should get the corrent ROM Update utility.
i dont know whats wrong
Also i have tried to get the rom.zip from the temp folder of my computer sourced from the RUU. changed the name to P......zip so that bootloader can flash. it just ends up saying "parsing P........zip"
slimldj said:
yes. but when i try to, the phone enters the "black htc screen" and after a couple of minutes i get error 155 from the RUU saying i should get the corrent ROM Update utility.
i dont know whats wrong
Also i have tried to get the rom.zip from the temp folder of my computer sourced from the RUU. changed the name to P......zip so that bootloader can flash. it just ends up saying "parsing P........zip"
Click to expand...
Click to collapse
As I said earlier , be in bootloader mode first. Then flash RUU. Error 155 should go off.
musarraf172 said:
As I said earlier , be in bootloader mode first. Then flash RUU. Error 155 should go off.
Click to expand...
Click to collapse
tried that as well.. as soon as the RUU says sending, i see the error again... 155
slimldj said:
tried that as well.. as soon as the RUU says sending, i see the error again... 155
Click to expand...
Click to collapse
Hope surely the following posts will help you.
http://forum.xda-developers.com/showthread.php?t=1469296
http://forum.xda-developers.com/showthread.php?t=1478828
musarraf172 said:
Hope surely the following posts will help you.
http://forum.xda-developers.com/showthread.php?t=1469296
http://forum.xda-developers.com/showthread.php?t=1478828
Click to expand...
Click to collapse
hello excuse the disorder but having the same problem on and hboot 1.19 s-on can not flash a stock ruu wanted to ask if you found a way to put s-off.
My hboot version is 1.23, s-on. My phone can't install PG58IMG.zip, bootloader always shows no image or wrong image, i tried different zip file but non of them works. I know this has a close relationship with s on. But what can i do? I would appriciate if you could give me some advice.
Problem is my phone can't boot into system,
pmbldc said:
My hboot version is 1.23, s-on. My phone can't install PG58IMG.zip, bootloader always shows no image or wrong image, i tried different zip file but non of them works. I know this has a close relationship with s on. But what can i do? I would appriciate if you could give me some advice.
Click to expand...
Click to collapse
Hi,
What exactly are you trying to do?
malybru said:
Hi,
What exactly are you trying to do?
Click to expand...
Click to collapse
My phone can't boot into system and now s-on, so i want to do something to make it work
pmbldc said:
My phone can't boot into system and now s-on, so i want to do something to make it work
Click to expand...
Click to collapse
Hi,
Were you s-off before?
What did you flash to make you s-on?
Last night I unlocked the bootloader n been having the same problem but mind say S-on n I don't know what's next
Sent from my HTC Sensation 4G using XDA App
? im at a lost here little more detail
what did you use to unlock bootloader?
where you ever s-off?
where you rooted?
why did you flash the IMG.zip?
if you unlocked it then go to fastboot and make your CID 11111
and hopefully that will get you back on where you wanted to do?
cant give much help unless you give some details on what was your state of phoen before and what you wanted to do with it
ilostchild said:
? im at a lost here little more detail
what did you use to unlock bootloader?
where you ever s-off?
where you rooted?
why did you flash the IMG.zip?
if you unlocked it then go to fastboot and make your CID 11111
and hopefully that will get you back on where you wanted to do?
cant give much help unless you give some details on what was your state of phoen before and what you wanted to do with it
Click to expand...
Click to collapse
I have similar problem, hboot 1.20, was S-OFF, flashed orig RUU ICS,changed CID to HTC___001 than I made stupid mistake and changed back to S-ON (wanted to send my phone to the shop, problems with reception and sound quality) now only ROM that my phone accepts is LeeDroid 5.01, cant change cid to supercid via fastboot some error SMART_IO.CRD not found on sdcard. Tried to flash orig RUU (1.45, 1.29, ICS etc.) error 155 when hboot is locked and error 132 signarure error when relocked. Also tried changing android-info.txt to my cid and mid no luck, tried flashing via RUU and bootloader no luck.
Any help would be appreciated
malybru said:
Hi,
Were you s-off before?
What did you flash to make you s-on?
Click to expand...
Click to collapse
Sorry to reply so late.
Previously, my phone was eng s-off and got super cid.
After i flash ICS firmware, bootloader was then locked.
After that i did some stupid things, the bootloader turned into "locked", "security warning" and s-on. I succeeded to unlock bootloader by htcdev and get rid of "security warning", at that time i can boot into recovery normally and wipe or flash roms. But it just can't boot into system. I tried fastboot commands to flash but failed just because "it is not allowed in the remote devices".
i tried PG58IMG files but the bootloader shows no image or wrong image.
Can you give me some advice? Thank you very much
ilostchild said:
? im at a lost here little more detail
what did you use to unlock bootloader?
where you ever s-off?
where you rooted?
why did you flash the IMG.zip?
if you unlocked it then go to fastboot and make your CID 11111
and hopefully that will get you back on where you wanted to do?
cant give much help unless you give some details on what was your state of phoen before and what you wanted to do with it
Click to expand...
Click to collapse
My phone had been rooted and end s-off before things happened.
i flash IMG.zip to try to flash a rom( Somebody post that ICS rom can be flash by IMG.zip) or fix the bootloader problem. It's almost the only way to flash a rom for me
I checked the cid and it is still 11111111(Got super cid before) although bootloader is s-on.
Now the state of the bootloader is
1, unlocked
2,s-on
3,cid is 11111111
4,can boot into recovery
5,can't install PG58IMG.zip
6,fastboot command can't write anyting
7,if flash some rom, phone will be stuck at the splash screen which seems splash partition is writable
Thank you!
greenhtc982 said:
I have similar problem, hboot 1.20, was S-OFF, flashed orig RUU ICS,changed CID to HTC___001 than I made stupid mistake and changed back to S-ON (wanted to send my phone to the shop, problems with reception and sound quality) now only ROM that my phone accepts is LeeDroid 5.01, cant change cid to supercid via fastboot some error SMART_IO.CRD not found on sdcard. Tried to flash orig RUU (1.45, 1.29, ICS etc.) error 155 when hboot is locked and error 132 signarure error when relocked. Also tried changing android-info.txt to my cid and mid no luck, tried flashing via RUU and bootloader no luck.
Any help would be appreciated
Click to expand...
Click to collapse
i don't know how to do either, but during solving my problem, i found something may be useful. If you want to unlock bootloader you can try htcdev. This can't s-off but just unlock bootloader.
And since your hboot is 1.20, you can try the zip file attached by this link http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22.
Because my hboot is 1.23 and isn't supported according to the above link, i didn't know whether it will help or not. You can take it into consideration
Hope you can solve your problem
ok find hboot 1.17 PD58IMG.zip, your truly not s-on, format your sdcard, then place the img in sdcard, and boot into bootloader, and you should be able run fastboot commands, you should still have custom recovery right?
ilostchild said:
ok find hboot 1.17 PD58IMG.zip, your truly not s-on, format your sdcard, then place the img in sdcard, and boot into bootloader, and you should be able run fastboot commands, you should still have custom recovery right?
Click to expand...
Click to collapse
I format the sdcard in fat32 format and place img that revert to hboot 1.17 in sdcard. Reboot into bootloader, but it shows "no image or wrong image".
I also try fastboot command but i don't know the command format. Would you give me an example please? Just a fastboot command to install img no matter s-on or s-off. Such as "fastboot flash hboot hboot.img".
My device is now s-on.
pmbldc said:
i don't know how to do either, but during solving my problem, i found something may be useful. If you want to unlock bootloader you can try htcdev. This can't s-off but just unlock bootloader.
And since your hboot is 1.20, you can try the zip file attached by this link http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22.
Because my hboot is 1.23 and isn't supported according to the above link, i didn't know whether it will help or not. You can take it into consideration
Hope you can solve your problem
Click to expand...
Click to collapse
Thanks for the link, but i tried that already, I've read whole bunch of treads and tried everything i can think off but nothing seems to work. Problem is S-on and with hboot 1.20 locked or unlocked i cant flash any rom except leedroid.
greenhtc982 said:
Thanks for the link, but i tried that already, I've read whole bunch of treads and tried everything i can think off but nothing seems to work. Problem is S-on and with hboot 1.20 locked or unlocked i cant flash any rom except leedroid.
Click to expand...
Click to collapse
You mean you can flash leedroid now, don't you?
Can you boot into system？
pmbldc said:
You mean you can flash leedroid now, don't you?
Can you boot into system？
Click to expand...
Click to collapse
Yes its working, but i would like to flash other ROM's
Same Problem
Hi, I can't flash PG85IMG.zip wither except that I have S-Off??
I S-offed my device via htcdev.com(as Revolutionary IO method didn't work for me). I flashed CWM 5.0.0.8.
To supercid my sensation, I followed the guide on this link :
http://forum.xda-developers.com/showthread.php?t=1192300
When I try to do the the SuperCID part of it, I get this:
C:\adb>fastboot oem writecid 11111111
... INFOvreg_set: request is duplicated id 14
INFO pyramid_init_sd, SD card power on ok
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 [ 1.081s]
finished. total time: 1.082s
Yes, my phone is detected when I type "adb devices".
Yes, I'm rooted. When i downloaded root checker app from playstore and checked it.. it said "Rooted".
Please help. Thank you in advance.
vipulnj said:
I S-offed my device via htcdev.com(as Revolutionary IO method didn't work for me). I flashed CWM 5.0.0.8.
To supercid my sensation, I followed the guide on this link :
http://forum.xda-developers.com/showthread.php?t=1192300
When I try to do the the SuperCID part of it, I get this:
C:\adb>fastboot oem writecid 11111111
... INFOvreg_set: request is duplicated id 14
INFO pyramid_init_sd, SD card power on ok
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 [ 1.081s]
finished. total time: 1.082s
Yes, my phone is detected when I type "adb devices".
Yes, I'm rooted. When i downloaded root checker app from playstore and checked it.. it said "Rooted".
Please help. Thank you in advance.
Click to expand...
Click to collapse
Using htcdev method to unlock your phone doesn't give you complete unlock solution it prevents fastboot commands that's why you are unable to supercid your device using fastboot command.
Using HTC unlocked bootloader you can still flash roms but you can only flash roms which are having stock kernel as option like ARHD. any other kernel will not be accepted by bootloader
Sent from my HTC Sensation XE with Beats Audio using xda premium
So what can i do next?
ganeshp said:
Using htcdev method to unlock your phone doesn't give you complete unlock solution it prevents fastboot commands that's why you are unable to supercid your device using fastboot command.
Using HTC unlocked bootloader you can still flash roms but you can only flash roms which are having stock kernel as option like ARHD. any other kernel will not be accepted by bootloader
Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
Thank you ganeshp. So what can i do next? Can I do something through the terminal emulator?
vipulnj said:
Thank you ganeshp. So what can i do next? Can I do something through the terminal emulator?
Click to expand...
Click to collapse
I got a method which can be done through adb shell or terminal emulator
But I haven't tried it myself but the comments are showing lot if success so try at your own risk and follow the steps carefully
Here is the link
h-t-t-p://www.simply-android.com/discussion/1600/how-to-super-cid-for-sensation/p1
(remove "-" between http)
Sent from my HTC Sensation XE with Beats Audio using xda premium
Link broken!
Yes Ganesh! Even I just was looking at the same. But the multiupload link is broken. Any idea how I can get to download this file? Please help! I think I am close to this.
Thanks a lot!
vipulnj said:
Yes Ganesh! Even I just was looking at the same. But the multiupload link is broken. Any idea how I can get to download this file? Please help! I think I am close to this.
Thanks a lot!
Click to expand...
Click to collapse
Yeah I came to know that too.
I'm just trying something and verifying it
I'll give you an update in few minutes
Edit1:
Can you first verify your CID and MID and post it here
type "fastboot getvar cid" and "fastboot getvar mid"
these commands will work as they are doing just reads
Edit2:
Can you give me small info?
Type
"dd if=/dev/block/mmcblk0p16 of=/sdcard/mmcblk0p16_bkp"
Without quotes on terminal emulator after typing su
(Be careful while using dd command its extremely low level command and its quite risky(may brick the device if typed wrongly)
so double check the command before pressing enter
Also this command will just read the block so it might pose no problem but be cautious just in case)
And send the mmcblk0p16_bkp (will be at sdcard root once you type the command) through private message to me/or post it here if its fine with you
Sent from my HTC Sensation XE with Beats Audio using xda premium
Exactly the same problem HELP! I want Sense 4 ORDROID and it just won't flash because the firmware won't flash because i cant supercid! The problem is the same! Because i used the HTCDEV method
Sorry can't help you in this case.
I've confirmed with devs .
No one for sure knows where/which partition the cid is stored.
So modifying the partition won't do and its pretty dangerous which might brick your device.
So we can't change cid without fastboot command.
I'll dig further and will let you know if I got any leads
---------- Post added at 10:35 PM ---------- Previous post was at 10:12 PM ----------
guys are you sure you are soff
i mean when you unlocked your boot loader using htcdev the bootloader reads unlocked ...but wont change s-on to s-off
so double check the s-off and if you are s-off then you guys have
a big chance to completely unlock your boot loader and also get supercid
so if you guys are soff then flash the latest firmware package again
then you'll get both soff and supercid
here is the firmware thread
firmware thread
"Revolutionary did not work for me...." = not s-off.
sent from HTC Pyramid using Tapatalk 2
stringer7 said:
"Revolutionary did not work for me...." = not s-off.
sent from HTC Pyramid using Tapatalk 2
Click to expand...
Click to collapse
yeah i know but i just want to here from them just to make sure
someone might try revolutionary to get the bootloader unlocked (or not )
You are clearly **unlocked** but still S-ON.
Use Revolutionary to S-OFF and then supercid devices.
Beta key is case sensitive so be sure to digit it correctly (usually this is the main reason why it doesn't work at first attempt).
kualmente said:
You are clearly **unlocked** but still S-ON.
Use Revolutionary to S-OFF and then supercid devices.
Beta key is case sensitive so be sure to digit it correctly (usually this is the main reason why it doesn't work at first attempt).
Click to expand...
Click to collapse
Revolutionary does not work because i have HBOOT 1.27.0000 and that is not surported. WOW! just checked i do indeed have s-on! how do i turn it off? Is there anyway to downgrade HBOOT?
Zd0s said:
Revolutionary does not work because i have HBOOT 1.27.0000 and that is not surported. WOW! just checked i do indeed have s-on! how do i turn it off?
Click to expand...
Click to collapse
You cannot. As you said actually Revolutionary doesn't support Hboot 1.27
Zd0s said:
Revolutionary does not work because i have HBOOT 1.27.0000 and that is not surported. WOW! just checked i do indeed have s-on! how do i turn it off? Is there anyway to downgrade HBOOT?
Click to expand...
Click to collapse
revolutionary does two things
1.unlock your bootloader completely (unlike HTCdev which unlocks partly)
2.S-off your device
Right now you are out of luck
but there 2 promising developments happening which might get s-off on hboot 1.27
here are the threads
be sure to follow them by subscribing to them (they might come with solution anytime)
1.http://forum.xda-developers.com/showthread.php?t=1573577
2.http://forum.xda-developers.com/showthread.php?t=1522351
Thanks everyone for your help! I will subcribe to those threads and wait patiently
Zd0s said:
Thanks everyone for your help! I will subcribe to those threads and wait patiently
Click to expand...
Click to collapse
There is actually a button to say thanks
Actually i've learned a lot too while finding answers to your questions
ganeshp said:
There is actually a button to say thanks
Actually i've learned a lot too while finding answers to your questions
Click to expand...
Click to collapse
Sorry forgot!
Done Now B)
ganeshp said:
Sorry can't help you in this case.
I've confirmed with devs .
No one for sure knows where/which partition the cid is stored.
So modifying the partition won't do and its pretty dangerous which might brick your device.
So we can't change cid without fastboot command.
I'll dig further and will let you know if I got any leads
---------- Post added at 10:35 PM ---------- Previous post was at 10:12 PM ----------
guys are you sure you are soff
i mean when you unlocked your boot loader using htcdev the bootloader reads unlocked ...but wont change s-on to s-off
so double check the s-off and if you are s-off then you guys have
a big chance to completely unlock your boot loader and also get supercid
so if you guys are soff then flash the latest firmware package again
then you'll get both soff and supercid
here is the firmware thread
firmware thread
Click to expand...
Click to collapse
Sorry, I was new to this actually. I only unlocked the bootloader. I was/am still S-ON.. Anyway to get to S-off? Or suppose I get an official OTA update from HTC (which I think I will get though I have unlocked my bootloader), will everything be back to how it was when I bought it?? So that I can start everything afresh with Revolutionary method. I am not going to htc dev method again!
Please help.
Thank you!
vipulnj said:
Sorry, I was new to this actually. I only unlocked the bootloader. I was/am still S-ON.. Anyway to get to S-off? Or suppose I get an official OTA update from HTC (which I think I will get though I have unlocked my bootloader), will everything be back to how it was when I bought it?? So that I can start everything afresh with Revolutionary method. I am not going to htc dev method again!
Please help.
Thank you!
Click to expand...
Click to collapse
1.you want get SOFF ->right now you are out of luck
just wait for 2 promising tools which claim to downgrade your HBOOT ...i've mentioned them in my previous posts and subscribe to them
2.If you want to flash a custom rom....then you still have a chance ...but only couple of roms though
(you did have custom recovery flashed right....CWM i guess)
if your option is 2 let me know ill guide you through further steps
Option 2!
ganeshp said:
1.you want get SOFF ->right now you are out of luck
just wait for 2 promising tools which claim to downgrade your HBOOT ...i've mentioned them in my previous posts and subscribe to them
2.If you want to flash a custom rom....then you still have a chance ...but only couple of roms though
(you did have custom recovery flashed right....CWM i guess)
if your option is 2 let me know ill guide you through further steps
Click to expand...
Click to collapse
Yeah, i do have Clock Work Mod 5.0.2.0 now.. Option 2 agreed!
What is the next step?
Thanks for help.
Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred
fdavidson said:
Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred
Click to expand...
Click to collapse
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )
ganeshp said:
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )
Click to expand...
Click to collapse
Thanks ganeshp for the quick answer. I am pretty confident about the RUU as it is the same one I originally ran to move from custom ICS ROM to stock 2.3.4 ROM.
For Revolutionary, even in fastboot, it is stuck in "Waiting for devices..." I think it is because it issues "adb devices" command and expects some answer before carrying on to the bootloader. I would need it to skip this step. Are there any argument to revolutionary to do that?
Fred
A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred
fdavidson said:
A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred
Click to expand...
Click to collapse
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID
Jonny said:
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID
Click to expand...
Click to collapse
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly change for my device, i.e. PG5810000), would the CID affect anything?
Fred
fdavidson said:
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly chance for my device, i.e. PG5810000), would the CID affect anything?
Fred
Click to expand...
Click to collapse
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place
dublinz said:
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place
Click to expand...
Click to collapse
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred
fdavidson said:
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred
Click to expand...
Click to collapse
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred
fdavidson said:
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred
Click to expand...
Click to collapse
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery
ganeshp said:
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery
Click to expand...
Click to collapse
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
edit: i just read your first post
so you can not use revolutionary
fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
ahh even that got stuck huh ...try revolutionary again ..with phone boot-looping or when stuck at splash screen ..if revolutionary finds the device all good ..otherwise all doors closed
rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
he tried revolutionary already ..and he currently didnt have a booting rom ..so it might not work
rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
That was my original attempt but it looks like revolutionary expects the phone to be fully booted so it can set it himself in bootloader/fastboot through adb command. Since I can get into fastboot myself, If I could skip that part from revolutionary and have it do the next steps, I think I'd get a successful S-OFF. Any idea on how to do that?
Fred
wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary
ganeshp said:
wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary
Click to expand...
Click to collapse
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.
fdavidson said:
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.
Click to expand...
Click to collapse
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )
ganeshp said:
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )
Click to expand...
Click to collapse
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.
fdavidson said:
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.
Click to expand...
Click to collapse
then im out of ideas
one last try
try changing cid
fastboot oem writecid HTC__001
then
fastboot reboot-bootloader
then verify it
fastboot getvar cid
EDIT: if this worked then ..immediately flash the european unbranded 3.33 rom
Im trying to install a rom on my sensation with hboot 1.27 so far i have dev unlocked it and rooted it Also a few hours ago i also managed. To complete the Juopunutbear s-off method. with it asking me would i like to installJuopunutbear Hboot to witch i said yes. And that brings us to my current problem, I cant seem to install cwm I put the PG58IMG File on the sd card an booted into hboot but The file loads up and then fails telling me "Model Id Incorrect update fail press power to reboot." Also after using juopunutbear. To s-off my phone the bootloader. Now says Locked instead. Of unlocked is this normal?
THANKS
Lostmymind904 said:
Im trying to install a rom on my sensation with hboot 1.27 so far i have dev unlocked it and rooted it Also a few hours ago i also managed. To complete the Juopunutbear s-off method. with it asking me would i like to installJuopunutbear Hboot to witch i said yes. And that brings us to my current problem, I cant seem to install cwm I put the PG58IMG File on the sd card an booted into hboot but The file loads up and then fails telling me "Model Id Incorrect update fail press power to reboot." Also after using juopunutbear. To s-off my phone the bootloader. Now says Locked instead. Of unlocked is this normal?
THANKS
Click to expand...
Click to collapse
Check the md5 sum of the PG58IMG File.
Lostmymind904 said:
Im trying to install a rom on my sensation with hboot 1.27 so far i have dev unlocked it and rooted it Also a few hours ago i also managed. To complete the Juopunutbear s-off method. with it asking me would i like to installJuopunutbear Hboot to witch i said yes. And that brings us to my current problem, I cant seem to install cwm I put the PG58IMG File on the sd card an booted into hboot but The file loads up and then fails telling me "Model Id Incorrect update fail press power to reboot." Also after using juopunutbear. To s-off my phone the bootloader. Now says Locked instead. Of unlocked is this normal?
THANKS
Click to expand...
Click to collapse
Hi,
Look HERE
2. Flashing a recovery
Flash 4 EXT
The "Locked" just restricts the fastboot commands available to you.
If this is a problem ,look HERE
Second post,and apply this:
HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100)
DO NOT GO TO HTC TO UNLOCK YOUR PHONE WHILE YOU ARE S-OFF.
EfrainTrejo said:
Check the md5 sum of the PG58IMG File.
Click to expand...
Click to collapse
malybru said:
Hi,
Look HERE
2. Flashing a recovery
Flash 4 EXT
The "Locked" just restricts the fastboot commands available to you.
If this is a problem ,look HERE
Second post,and apply this:
HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100)
DO NOT GO TO HTC TO UNLOCK YOUR PHONE WHILE YOU ARE S-OFF.
Click to expand...
Click to collapse
I tried to flash recovery but it didn't work it tells me " writing recovery FAILED (Remote not allowed)" and the md5 is correct so no problems there
Lostmymind904 said:
I tried to flash recovery but it didn't work it tells me " writing recovery FAILED (Remote not allowed)" and the md5 is correct so no problems there
Click to expand...
Click to collapse
You have to flash the patched hboot first add suggested by @malybru . after that then you won't have a problem flashing a recovery.
Sent from my Ouya
AndroidSupporter318 said:
You have to flash the patched hboot first add suggested by @malybru . after that then you won't have a problem flashing a recovery.
Sent from my Ouya
Click to expand...
Click to collapse
I was unable to flash the hboot i would just get an error. I fixed my problem about 30 seconds ago by supercid the phone which allowed me to flash Juopunutbear Hboot and then recovery took me 8 hours to figure it out but i was determined.