Database Info

[Q] recovery

Hi Guys,
Got a bit of a problem, got a sensation xe and tonight i did the s-off and rooted then tried to put a new rom on but it just bootlooped so went to recovery and did a restore and all was ok,
rooted it again and put the PG58IMG back on did the update then it just went as far as the beats logo and looped.
i tried to get into recovery but it wouldnt go and just kept saying no image or wrong image every time i tried, i read some similar threads to this and so eventually i took out the sd card and then got back into recovery but doing a restore didnt work,
took the sd card out and using the pc deleted the PG58IMG which i thought might be causing the problem, tried recovery and it started again but on rebooting it just bootloops again, can anybody help me?

Need to know exactly what you did at the time of flashing? What steps have you done and what ROM?
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium

start
Ok i followed the guide on here....http://forum.xda-developers.com/showthread.php?t=1192300 got s-off and root.
tried to super cid and couldnt get it done anyway got s-off and rooted put the PG58IMG in root updated and then took it out of root then tried to put the darkforest sensation xe ics 3.2.1 rom on, got bootloop then went to recovery and did a restore, everything was then ok.
Checked the phone and it was unrooted so did another complete backup looked to see what might be wrong and i thought i had put the wrong PG58IMG on so i went and put what i thought was the right PG58IMG on updated it and then rebooted and it went into a bootloop.
Tried to do a recovery but would not allow it it just kept running through "no image" then "wrong image" then "no image" and so on.
Tried to get into recovery but wouldnt move down so after reading a similar thread i pulled the sim and got into recovery selected the first of the two restore options and it was restoring from cwd rebooted and it started on a bootloop again going to the beats logo this time.
Thank for your help btw.

Forgot to add it was the revolution system. Thanks for any help!

highlander1v said:
Ok i followed the guide on here....http://forum.xda-developers.com/showthread.php?t=1192300 got s-off and root.
tried to super cid and couldnt get it done anyway got s-off and rooted put the PG58IMG in root updated and then took it out of root then tried to put the darkforest sensation xe ics 3.2.1 rom on, got bootloop then went to recovery and did a restore, everything was then ok.
Click to expand...
Click to collapse
To install ICS roms you need an additional step. Before installing the rom you should supercid and install the new ICS firmware. You can find the link on the second line of darkforest sensation xe ics 3.2.1.
If don't want to supercid follow the instruction here and download the firmware package for your CID (3.24, revolutionary or normal).
Install the new firmware.
Remove the PG58IMG from your sd card
Install the ICS rom.
highlander1v said:
Checked the phone and it was unrooted so did another complete backup looked to see what might be wrong and i thought i had put the wrong PG58IMG
Click to expand...
Click to collapse
You don't root with PG58IMG, that's for the custom recovery. Have you installed the su-2.3.6.3-ef-signed.zip file from the guide?

Hi, yes i have the su-2.3.6.3-ef-signed.zip installed and have removed the PG58IMG from the sd card, but as i say the thing is just boot looping after the beats logo and i would like to find out the next steps to get things back to normal?

Thanks grandelama can you tell me my next move to get back to normal and out of bootloop?

What ROM do you currently have on your phone that doesn't boot? Stock or Darkforest or something else? I'm not sure what rom you restored from the backup... If you restored the Darkforest rom and didn't install the correct firmware as Grandelama said, it will get stuck in a bootloop. If you did install the firmware, try reinstalling the Darkforest rom.
Otherwise, to get your phone working, just do a full wipe in recovery and try to install any gingerbread based rom, for example Android Revolution HD 3.6.13 from here. It should install fine and get your phone to a working condition. Then you can try to get superCID and install the firmware if you want to use ICS roms.
If you have Clockworkmod working and are going to install custom roms anyway, you don't need to worry about installing the su-2.3.6.3-ef-signed.zip file, since all those custom roms are already rooted.

If you have completed without errors the points 1, 2 and 3 of the guide, and you can use Clockworkmod recovery you are now ready to install any NON ICS rom like Android Revolution HD 3.6.13.
Run the superwipe script in Android revolution HD thread, install the 3.6.13 rom and you should boot up allright
If you want to use an ICS rom your missing a step (new firmware) and you need to follow the instructions I gave you in the last post.

Ok thanks guys, i'll try that and let you know how i get on.

Dr Madman i tried the dark forest rom but it wouldnt load so went into recovery and went back to the original stock gingerbread then thinking i had put the wrong 58img changed it and updated but it just bootloaded so did a cwm restore and it still bootloads.

I'm still not sure just what to do next because i'm afraid i might make things worse.
I went into recovery then to backup and restore and then restore and this time restored the second image that was there in CWM it went thru all the recovery, asked to reboot and when i did it still keeps bootlooping.
Why is CWM not getting me back to stock?
Grandelama i'm certain i did what you suggested in your first post but got bootloop after that and CWM got me back but it hasnt worked this time!
Dr Madman,, i could do a wipedata/factory rest wipe cache partition and install Android Revolution HD 3.6.13 because its on the sd card but to be honest i'm just to frightened to at the moment, basically i wanted to go to restore and have it back as stock but it wont! and now i'm not sure which way to go?

highlander1v said:
Grandelama i'm certain i did what you suggested in your first post but got bootloop after that and CWM got me back but it hasnt worked this time!
Click to expand...
Click to collapse
If you did what I suggested you have installed the 3.24 firmware for ICS roms, am I right?
Can you tell which exact version did you install? Where did you download it from? The one from the Kohr-Ah thread...mike1986's version or what?
If you installed mike1986's version without Supercid first you will bootloop with both ICS and Gingerbread roms.

yes
Yes i am certain i did but not sure which one, heads all over the place with this, anyway i will check and get back to you.
Thanks.

Grandelama i think? this is the one i used......DOWNLOAD 3.24 Revolutionary: http://goo.gl/82UpA
MD5: 74e67609f67c3ad6ab94cdb89f19f2fa
Is there a way to find out for sure for you?
Thanks

Do you still have on your pc the zip package you used? If that's the case you can find the md5 of your file and with that you can know which firmware package you installed.
Maybe it's a stupid question, but can you tell me which is exactly your CID? What is the output you get with "fastboot getvar cid"? Are 100% you sure you installed exactly the firmware package for your CID?

Grandelama, firstly thanks for your help, i have a hero that i have rooted and had at least a dozen different roms on from 1.6 thru to 2.3 never had a problem but its been a while and this xe is it seems more complicated, either that or my brains going (more likely) anyway the CID is HTC--001 and the MID is pg5813001.
I will look and see what i have and let you know.
The phone i take it is not yet bricked??? so i really dont want to do anything to screw that up(unless its too late?)
I ran restore and got back to normal, should have left it at that but didnt and cant understand why it wont work this time, i thought thats what it was for.
Anyway i will get back to you with what info i have and thanks again

no, not now 100 sure!
Htc driver 3.0.0.007
v4.3.233.pub.odex.zip
revolutionary -0.4pre4
su-2.3.63-efgh-
darkforest sensation xe ics 3.2.1
PG58IMG
Android revolution hd sensation 3.6.13
This is what else i have plus i have a xe backup folder on the pc if this is of any use ?

is this what you are asking for?
http://forum.xda-developers.com/attachment.php?attachmentid=874000&stc=1&d=1327610186

highlander1v said:
Grandelama, firstly thanks for your help, i have a hero that i have rooted and had at least a dozen different roms on from 1.6 thru to 2.3 never had a problem but its been a while and this xe is it seems more complicated, either that or my brains going (more likely) anyway the CID is HTC--001 and the MID is pg5813001.
I will look and see what i have and let you know.
The phone i take it is not yet bricked??? so i really dont want to do anything to screw that up(unless its too late?)
I ran restore and got back to normal, should have left it at that but didnt and cant understand why it wont work this time, i thought thats what it was for.
Anyway i will get back to you with what info i have and thanks again
Click to expand...
Click to collapse
Hi,
i had the exact same problem and yesterday i solved it. I tried to flash the latest InsertCoin ICS ROM and failed to first install the new Firmware. When i realized this, i did it but forgot to check the CID, wich was not in the FW-zip.. so.. my phone just bootlooped, came to the splashscreen the rebooted. Your phone is not bricked.
This is what i did to solve it:
First i got Super-CID wich you can read about in this thread: [Guide] to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on .. it took me about 30 sec to get Super-CID, its very easy if you just read the text.
Then i flashed the new Firmware (3.24.401.1 RUU) that you can find here [DEV] HTC Sensation & HTC Sensation XE firmware | Partitions Info | [22.01.2012]
After that i just flashed the ROM like before and voila, it worked.
Hope it helped some.

{HELP} device is keep booting into recovey -- SOLVED --

To the Guru of this forum. After my last rom flashing my device is keeping booting into recovery :crying:. Is it briked ? If so my only hope is the unbricking project ? Thanks in advance.

What recovery are you running?
Can you use the power menu within recovery to boot into bootloader?
Also, please provide as much pertinent info as possible, ie: rom you flashed, firmware, s-off or s-on, locked or unlocked. With your description it's basically like saying, "my car makes a noise all the time. what is causing it?".

Its not bricked.If u can enter recovery
Sent from my HTC sensation

Sorry you are right:
What recovery are you running? 4Ext
Can you use the power menu within recovery to boot into bootloader? yes
The device is HTC unlocked with S-On.
Rom JBMIUI v4.1 2.8.31 R2.
HBOOT 1.27.0000
firmware 3.33.401.6
I've format everything but SD. Restored the most recent back up done today before flashing. Once it reboots HTC logo comes up once, black screen, HTC logo, 4Ext is coming up saying that smartflash it is set to update the boot partition on next system start asking if this should be removed.
I've downloaded and installed again PG58IMG *different files using bootloader
I've founded a 3.33.401.6-Unsecured-Boot.img,+Root+Busybox zip file that can be installed via recovery but it did not help.
At this point I need a bit of help to look into the right direction and I'm not sure that Unbrick_Pyramid is the right way.
Thanks again.

Try turning off smartflash and flash a 3.33 stock rom to see if it will boot.
What was your last working setup, and what were you trying to install?
Sent from my HTC Sensation 4G using Tapatalk 2

Hi. Manage to flash a stock 3.33.
It stopped to reboot straight into recovery.
Sits now on HTC logo now for about 10 mins. I plan to let him run for 1 hr and see what happens.
Was thinking to install CWM on the basis that could be a 4ext recovery issue, toughs?
GROGG88 said:
Try turning off smartflash and flash a 3.33 stock rom to see if it will boot.
What was your last working setup, and what were you trying to install?
Sent from my HTC Sensation 4G using Tapatalk 2
Click to expand...
Click to collapse

If you can install clockworkmod that may help.
Tge device isnt getting the message that it has already booted into recovery once. So something may be jacked up with 4ext.
Clockwork may bypass all that when it doesnt know what to do with that signal to run smartflash.
Worst case scenario...put a full pm58img containing a rom and recovery on the sf card and flash that through bootloader.
You should still be able to get to bootloader as the device looks for that option first.
Sent from my HTC Sensation using xda app-developers app

Hallo. Ok installed CWM. Can please direct me to a full pm58img as you mentioned ? Thx.
Skipjacks said:
If you can install clockworkmod that may help.
Tge device isnt getting the message that it has already booted into recovery once. So something may be jacked up with 4ext.
Clockwork may bypass all that when it doesnt know what to do with that signal to run smartflash.
Worst case scenario...put a full pm58img containing a rom and recovery on the sf card and flash that through bootloader.
You should still be able to get to bootloader as the device looks for that option first.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse

DiscreteTask said:
Hallo. Ok installed CWM. Can please direct me to a full pm58img as you mentioned ? Thx.
Click to expand...
Click to collapse
And did that help? Are you able to get into recovery without errors now? If so you should be able to flash a fresh version of any ROM.
Try that first. Get any ROM. Flash it. See if it boots.
If you have successfully replaced 4EXT I will bet a fresh flash of a ROM will now boot.
Also worth a shot is replacing or upgrading the firmware, as that could be what's sending the phone into recovery on each boot (though this is less likely that 4EXT just being broken)
Flash a firmware PM58IMG like 3.32 or 3.33 and see if that helps.
But for starters, put a fresh ROM on the SD card and flash it with CWM. (BE SURE IT'S A ROM THAT DOESN'T REQUIRE 4EXT!!)
Once you've got it all fixed you can switch back to 4EXT. I have a feeling it was just the copy you were running that got botched. The software itself is solid and stable. A new copy shoudl work fine now.

CWM v5.0.2.0 was installed fine.
3.33 firmware installed once again.
Using this I've installed ROM that I already did in the past w/o luck, they all sit on the HTC logo. Is like the initial boot sequence is broken. Is boot.img part of the firmware or ROM ?
Trying to download some additional ones.
Thanks,
Skipjacks said:
And did that help? Are you able to get into recovery without errors now? If so you should be able to flash a fresh
version of any ROM.
Try that first. Get any ROM. Flash it. See if it boots.
If you have successfully replaced 4EXT I will bet a fresh flash of a ROM will now boot.
Also worth a shot is replacing or upgrading the firmware, as that could be what's sending the phone into recovery on each boot (though this is less likely that 4EXT just being broken)
Flash a firmware PM58IMG like 3.32 or 3.33 and see if that helps.
But for starters, put a fresh ROM on the SD card and flash it with CWM. (BE SURE IT'S A ROM THAT DOESN'T REQUIRE 4EXT!!)
Once you've got it all fixed you can switch back to 4EXT. I have a feeling it was just the copy you were running that got botched. The software itself is solid and stable. A new copy shoudl work fine now.
Click to expand...
Click to collapse

DiscreteTask said:
CWM v5.0.2.0 was installed fine.
3.33 firmware installed once again.
Using this I've installed ROM that I already did in the past w/o luck, they all sit on the HTC logo. Is like the initial boot sequence is broken. Is boot.img part of the firmware or ROM ?
Trying to download some additional ones.
Thanks,
Click to expand...
Click to collapse
The more details you give, the better the answers will be. Don't consider any detail too small.
What do you mean you installed ROM's that you had done in the past? Do you mean you are trying to restore a backup made with 4EXT?
That won't work. You need to flash a fresh version of the ROM after wiping.
Also, CWM won't install some ROM's that you may have used in the past. What ROM are you trying to install?
The HTC logo that first pops up when you hit the power button is part of the firmware.
Make sure you do a full wipe of everything but the SD card from within CWM. Get whatever's causing the problem off that way. Then flash a fresh install of a ROM from scratch.

Hi.
I did not use any backup only fresh ROMs: ARHD, Elegantia, but also stock ROMs I could find.
I've tried also some PG58IMG with ROM included.
Cheers.
Skipjacks said:
The more details you give, the better the answers will be. Don't consider any detail too small.
What do you mean you installed ROM's that you had done in the past? Do you mean you are trying to restore a backup made with 4EXT?
That won't work. You need to flash a fresh version of the ROM after wiping.
Also, CWM won't install some ROM's that you may have used in the past. What ROM are you trying to install?
The HTC logo that first pops up when you hit the power button is part of the firmware.
Make sure you do a full wipe of everything but the SD card from within CWM. Get whatever's causing the problem off that way. Then flash a fresh install of a ROM from scratch.
Click to expand...
Click to collapse

Arhd and elegencia wont work with cwm. So there is your isdue. Try cm9 or 10 to see if you can boot one of those.
Sent from my HTC Sensation using xda app-developers app

Hallo, after trying all option the following did work for me:
- re-lock bootloader via fastboot oem lock
- apply stock ROM founded in this list http://forum.xda-developers.com/showthread.php?t=1074559
- rebooted fine
I guess that HTC RUU had some superpower and erase and installed whatever file(s) were corrupted.
Now I'm on stock 3.6 - fw 3.33.401.106 - radio 11.76A.3504.00UU_11.24A.3504.31_M
HBOOT 1.29 - S-ON - Relocked.
Standard Recovery.
Now I'm reading how to return my device to S-OFF w/o damaging it again.
Many thanks to skipjacks & groog88 :good:
Skipjacks said:
Arhd and elegencia wont work with cwm. So there is your isdue. Try cm9 or 10 to see if you can boot one of those.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse

[Q] Paranoid noob question regarding S-off and previous Bootloader

I am wondering if I made any major changes or done anything wrong.
1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?
2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.
Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much

fashofasho said:
I am wondering if I made any major changes or done anything wrong.
1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?
2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.
Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much
Click to expand...
Click to collapse
when you did S-OFF in order to install Cyanogen JB first you had to flash the latest fw version and then the rom
the rom you tried to install requires the latest fw version
now are you still s-off?
what is now your hboot version?
what is your fw version?

I am wondering if I made any major changes or done anything wrong.
1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?
2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.
Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much
Click to expand...
Click to collapse
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.
2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)
Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.
If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.
If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!
Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.
It should not boot.
This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!
I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.

Skipjacks said:
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.
2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)
Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.
If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.
If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!
Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.
It should not boot.
This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!
I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.
Click to expand...
Click to collapse
i got confused
.i think your answer is going for fashofasho

Skipjacks said:
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.
2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)
Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.
If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.
If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!
Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.
It should not boot.
This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!
I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.
Click to expand...
Click to collapse
Thanks for the reply. Okay so here is where I am currently at. I haven't done anything since I reflashed stock ROM throguh RUU after the fail cyanogen flash. On this stock ROM whenever I load into bootloader it still says s-off 1.17 but I did lose my clockworkmod. So according to your instructions I should either clockworkmod again or 4ext now, that's okay right? If so, going to flash firmware then cyanogen!! Or is there a problem that I have s-off but not recovery.
P.s. there is no point in running revolutionary and have it s-off again when I already have it right, just thought it might be necessary to make things fresh

If you have a bootable phone right now this is easy as you may not need adb or fast boot or anything.
First off you will need to install 4ext. Get the app from the Play Store. Then run it and let it install its recovery module. (You may need to be rooted to do thus, which your stock rom is not. Im not sure if you can flash the recovery without root or not because Ive never tried without root. If so, then you will have to install Superuser via fastboot I think. You any guide for rooting to get instructions on this. Its easy.)
You may also find a way to install 4ext recovery via flashing from bootloader, but you will have to search for that. You MAY even be able to install it with the firmware upgrade. You will have to see if that is an available option.
Get your firmware from this thread...
forum.xda-developers.com/showthread.php?t=1459767
Follow the instructions to update. Once you have 3.3x firmware and 4ext simply boot to recovery, do a full wipe, and flash cm10 (make sure cm10 is on your sd card. You can download it from your currently working gingerbread rom so you have it available)
You have like 15-20 minutes worth of work to do, so its not a monumental obstacle to overcome. It just seems like alot
Sent from my HTC Sensation using xda app-developers app

Skipjacks said:
If you have a bootable phone right now this is easy as you may not need adb or fast boot or anything.
First off you will need to install 4ext. Get the app from the Play Store. Then run it and let it install its recovery module. (You may need to be rooted to do thus, which your stock rom is not. Im not sure if you can flash the recovery without root or not because Ive never tried without root. If so, then you will have to install Superuser via fastboot I think. You any guide for rooting to get instructions on this. Its easy.)
You may also find a way to install 4ext recovery via flashing from bootloader, but you will have to search for that. You MAY even be able to install it with the firmware upgrade. You will have to see if that is an available option.
Get your firmware from this thread...
forum.xda-developers.com/showthread.php?t=1459767
Follow the instructions to update. Once you have 3.3x firmware and 4ext simply boot to recovery, do a full wipe, and flash cm10 (make sure cm10 is on your sd card. You can download it from your currently working gingerbread rom so you have it available)
You have like 15-20 minutes worth of work to do, so its not a monumental obstacle to overcome. It just seems like alot
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
I am not rooted but am S-off. So my next step would be to root. I am suppose to have Clockworkmod to root AND 4EXT after right? Its not one or the other? I keep reading that people recommend 4ext is better than CWM but in order to root su-2.3.6.3-ef-signed.zip I need CWM first correct?

fashofasho said:
I am not rooted but am S-off. So my next step would be to root. I am suppose to have Clockworkmod to root AND 4EXT after right? Its not one or the other? I keep reading that people recommend 4ext is better than CWM but in order to root su-2.3.6.3-ef-signed.zip I need CWM first correct?
Click to expand...
Click to collapse
flash su-2.3.6.3-ef-signed.zip first and then install 4ext recovery

You're over engineering this. You don't need to root your current ROM first. That's an extra step since you're s-off.
If you are s-off it's really simple to get 4EXT recovery.
First, download this and put it on the root directory of your SD Card (meaning not in a folder, just on the SD Card. Do not rename it)
http://d-h.st/qnm
I got this download link from here...
http://forum.xda-developers.com/showthread.php?p=21989107
Click Thanks for Joaquinf in that thread. He made the 4EXT zip that's flashable through the bootloader.
That is 4EXT made into a zip file that's flashable via the bootloader, which you can do when you are S-off.
So put that file on the SD card, power the phone off, pull the battery out for a second and put it back in (this stops fastboot so you can get back to the bootloader). Then hold volume down and power at the same time. You have to hit both buttons at the same time. If it goes to the splash screen, pull the battery and try again.
When the bootloader loads up it will immediately find the PM58IMG.zip file. It will ask you if you want to install the update. Say yes by hitting volume up I think (it will tell you how to say yes)
Put the phone down and don't touch it until it tells you it's done. Should just take a second. But seriously don't touch it. Leave it alone.
If that works, you've just flashed 4EXT. You can check it by pulling the SD card out (so it doesn't try to flash the PM58IMG again) and rebooting to the bootloader and selecting 'recovery' from the menu. 4EXT should boot up.
This entire process so far shouldn't take more than 3 minutes total. It just sounds like a lot.
To see this detailed out by someone else in case you want to check what I'm saying, read steps 4 and 5 of the first post in this thread.
http://forum.xda-developers.com/showpost.php?p=21989063&postcount=1
Give the author 'thanks' again because he's awesome and deserves it.
Now you've got 4EXT installed. Great. You're 1/3rd of the way home.
Now you need to update your firmware. Delete the PM58IMG.zip file you used to flash 4EXT off the SD card (use a card reader or boot the phone up and delete it, whatever works. You can also use 4EXT as a card reader now too by choosing USB storage from inside 4EXT. It will give you access toteh SD card on your computer now)
Now get new Firmware from this thread.
http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
try the 3.33 firmware universal. First download link in post 2 of the thread above.
CHECK THE MD5 SUM!!!! I'M NOT PLAYING AROUND HERE!!! You are worried about bricking your phone, this is where you can do it if the firmware .zip is bad.
Put that PM58IMG file on your SD and flash it in the bootloader the same way you flashed 4EXT recovery a minute ago. (If you're still in 4EXT recovery you can use it's power menu to reboot into bootloader easily.)
This will take a minute. The phone will shut off and go black in the middle of this process. Your heart will skip a beat. Relax. It'll come back on. Again, put the phone down and walk away while it does it's thing and don't touch it until it says it's done.
Delete the PM58IMG file from your SD card.
You are now 2/3 of the way there. Your phone WILL NOT boot up right now because your ROM is not compatible with your firmware. Relax. That's supposed to happen.
Now you can flash CM10. Make sure you have the CM10.zip file on your SD card nad GApps. (Bruce has Gapps in his downloads page). Delete the PM58IMG firmware file from your SD card (that's important)
Pull the battery again so you can get back into bootloader. Get into bootloader (power + volume down)
Select Recovery
4EXT should boot up.
Go to the Wipe menu. Wipe all partitions except SD card. (Old ROM is now gone)
Go back to the main menu.
Install from SD
Find the CM10.zip file you should have downloaded and put onto the SD card. Flash it.
This will take about 3 minutes. 4EXT will flash it and ask if you want to reboot. You do not yet. Not you need to flash Gapps the same way you flashed the ROM.
When that's done, now you can reboot. You shoudl see the CyanogenMod boot animation after the splash screen. Give it a few minutes to boot up this first time. Once it boots, set it up the way you like it. If you enjoy it, donate a few bucks to the developer, Bruce.
You don't have to root CM10. It's already rooted when you boot it up the first time.

[Q] HTC Boot Loop and no signal using recovery

Hello All,
I will start this thread with the obligatory "Im new to rooting...." sentence but over the last 2 or so weeks have been doing my research between multiple sites (including this one), getting frustrated at how many "How to...but before you do" guides there are out there adn you tube videos but have finally managed to perm root and S-Off my UK Vodafone HTC Sensation.
I have flashed clockwork recovery without a hitch and managed to download the Cynaogen Rom without to much difficulty.
The problem:
While looking for overclocking ROMs, decided that the Virtuous Sensation ROM might be the one for me.
While doing further research, I discovered that I would need to flash the new PG58IMG.zip Firmware before the ROM would work. To do this, I would potentially be required to SuperCID, which I also did.
SuperCID complete and Firmeware flashed (and then removed from the SD card) I wiped the phone (several times following instructions on this site) and then installed the Virtuous ROM.
Now I get stuck on boot loop with the blue "V" showing for a about a second and then restarting.
Following some further internet checking, I found it may be a bad download of the ROM so downloaded again but the same thing happened. I also downloaded a different Virtuous ROM to confirm it was the Virtuous Sensation ROM that was corrupt but the other ROM got stuck on boot loop, albeit, the blue "V" now shoed for about 5 seconds.
I decided to load a recovery and revert back to the Cynaogen ROM except......sometimes its stuck on boot loop and other times it loads but I have no network coverage.
I have two questions:
Why did the new Virtuous ROM not work with the recommended firmware?
and
How can I restore my phone? I am guessing this problem may be the new firmware but I have read that this one works with Gingerbread and ICS?
Any help would be appreciated...preferably in a non "PHD in IT required" way.
Thanks in advance if anyone can help.

mostly it might be because of Firmware
what firmware you installed (my guess is 3.24 as you said works for both ICS and GB )
but i suggest you to use 3.33 firmware for ICS or above roms and 1.17 For GB roms
here is the firmware thread

OK, just tried flashing the ICS firmware (thanks for reply) from the link you posted, wiped the phone, cache etc and reinstalled ROM.
I get stuck on boot loop but the blue "v" does load for a little longer now.
From doing some more reading I have seen people saying to check MD5 match. Would someone mind explaining what ths is and how to do it?

OK, ignore the MD5 thing, i searched and found and its a match for all downloads.
ROM is an MD5 match also.
Tried all firmware and still stuck on boot loop.....
One thing I have noticed is that when I load usig the vol down + power, it sates that the 58IMG is "no image or wrong image"....could this be anything to do with it?

ssjghost said:
OK, ignore the MD5 thing, i searched and found and its a match for all downloads.
ROM is an MD5 match also.
Tried all firmware and still stuck on boot loop.....
One thing I have noticed is that when I load usig the vol down + power, it sates that the 58IMG is "no image or wrong image"....could this be anything to do with it?
Click to expand...
Click to collapse
That's generic bootloader function... So its common.. The searching for PG58IMG thing...
Now the best and most effective way is to first cleanup everything usig ruu.. Search for "ruu guide and info" thread by kgs1992 in sensation general section... Use that.. Find the proper ruu and flash it.. Check whether the stock rom(ruu) is flashing or not..If flashing then flash custom recovery and flash your custom rom again
Sent from my HTC Sensation using xda premium

Question
I have checked through a few forums and just want to clarify something before I go down the RUU route:
Will flashing the RUU to stock mean I lose S-Off or perm root? You say I will have to flash a custom recovery image again so I guess that means flashing clockworkmod through HBoot but will I then be expected to flash further firmware?
Thanks, Ill give the RUU thing a go.
I tried all the firmware with te Virtuous ROM and nothing worked but then one of the bottom firmware donloads (3.24 I think, cant remember know following multiple downloads) and booted the recovery.
Now I have signal again!
Thanks for advice, I will try the RUU thing....
Cheers

ssjghost said:
Question
I have checked through a few forums and just want to clarify something before I go down the RUU route:
Will flashing the RUU to stock mean I lose S-Off or perm root? You say I will have to flash a custom recovery image again so I guess that means flashing clockworkmod through HBoot but will I then be expected to flash further firmware?
Thanks, Ill give the RUU thing a go.
I tried all the firmware with te Virtuous ROM and nothing worked but then one of the bottom firmware donloads (3.24 I think, cant remember know following multiple downloads) and booted the recovery.
Now I have signal again!
Thanks for advice, I will try the RUU thing....
Cheers
Click to expand...
Click to collapse
RUU means everything to stock except SOFF ..so you would lose custom recovery, perm root .but the best part is as you still have SOFF ..you can just flash a custom recovery again ..and flash su zip for perm root again ..done voila
and SOFF means ..yes you can flash any firmware

Thanks for all you help mate, in the end i found Cyanogen 10 ROM which does everything I want so followed all instructions and works fine now.
Thanks again for being patient with a nub......much appreciated!:laugh::laugh::laugh::laugh:

Android Revolution HD 7.3

Hey guys,
Having some problems with this ROM. I downloaded the ZIP, used Titanium backup to back it all up, and flashed the Rom with no problems at all...got through all the screens and whatnot, and upon launching for the first time it's stuck on the "Beats Audio" screen. Not really sure why or what happened. I'm coming from MIUI ROM and haven't had issues with flashing any other ROM before.
One thing I noticed is on the HD 7.3 first page there is a firmware update that you apparently need before you flash the ROM but all links are 404/not found.
Wondering if any of you pros can offer a hand?
-Cain

Cainsmoker said:
Hey guys,
Having some problems with this ROM. I downloaded the ZIP, used Titanium backup to back it all up, and flashed the Rom with no problems at all...got through all the screens and whatnot, and upon launching for the first time it's stuck on the "Beats Audio" screen. Not really sure why or what happened. I'm coming from MIUI ROM and haven't had issues with flashing any other ROM before.
One thing I noticed is on the HD 7.3 first page there is a firmware update that you apparently need before you flash the ROM but all links are 404/not found.
Wondering if any of you pros can offer a hand?
-Cain
Click to expand...
Click to collapse
post the output of this command
fastboot getvar all
don't show your imei and serial number
and what recovery do you have?

rzr86 said:
post the output of this command
fastboot getvar all
don't show your imei and serial number
and what recovery do you have?
Click to expand...
Click to collapse
In looking at my Hboot, it's old as sin....I'm using Revolutionary Hboot 1.17.1111 and Radio 10.14.9035.01_M
I run clockwork recovery mod v5.0.2.0 as well. This could be an issue causing the problem. I've been using the MIUI ROM for probably 2 years or so because I enjoyed it but I'm ready for a change. Apparently my phone doesn't agree. lol.
You want me to connect via USB and run the cmd prompt for the getvar command and let you know what it says?

Cainsmoker said:
In looking at my Hboot, it's old as sin....I'm using Revolutionary Hboot 1.17.1111 and Radio 10.14.9035.01_M
I run clockwork recovery mod v5.0.2.0 as well. This could be an issue causing the problem. I've been using the MIUI ROM for probably 2 years or so because I enjoyed it but I'm ready for a change. Apparently my phone doesn't agree. lol.
You want me to connect via USB and run the cmd prompt for the getvar command and let you know what it says?
Click to expand...
Click to collapse
there is no need to do it now
you gave me exactly what i need
you still have gb firmware that's why you can't boot ARHD 7.3(ics rom)
see this thread
http://forum.xda-developers.com/showthread.php?t=1459767
flash 3.33 universal
follow the instructions to the letter
and before flashing check md5 sums(important)

The speedy reply is much appreciated.
I'll go ahead and update the firmware and see where that lands me. I figured it could have been a problem from the get go but in the original thread for the HD 7.3 Rom the firmware link has been removed (likely since it was from 2011)
Thanks for the point in the right direction Rzr, and I'll let you know how it goes!
rzr86 said:
there is no need to do it now
you gave me exactly what i need
you still have gb firmware that's why you can't boot ARHD 7.3(ics rom)
see this thread
http://forum.xda-developers.com/showthread.php?t=1459767
flash 3.33 universal
follow the instructions to the letter
and before flashing check md5 sums(important)
Click to expand...
Click to collapse

Hmmm....the firmware update didn't work.
I can verify that I'm on the firmware 3.3, Hboot is 1.27.1100, Radio is 11.24A.3504.31_M.
Each time Hboot is run it asks if I want to start the update. If I select yes, I've got 9 on screen options that it runs through and tells me "Update complete. Press power to reboot" The only way to do anything at all is to take out the SD card so it does not try to load up the firmware zip
Pushing power reboots the phone on an endless boot loop. Regardless of what ROM is being used (I also downloaded cyanogenmod) I can not make it past the spash screen.
Could it be that I'm just flashing the ROM incorrectly? To my knowledge I've followed instructions for both and have backed up my phone and it's contents and done everything from a factory reset/wipe to wiping the dalvik cache, etc. I didn't have this many problems rooting my phone and putting on MIUI to begin with and have flashed ROMS before with no trouble....not really sure where I'm going wrong on this one.
Anyway, I'll await your reply.
Thank you!
-Cain
Update: awww frick. So now it looks like this will be more difficult....I hope you like a challenge. I can now no longer get into my phone. It appears that it's soft bricked. I have tried going to a clockwork mod recovery from my first MIUI in 2012, it goes through the entire process of factory resetting restoring the boot image, system and data information. It asks for a reboot which I do. It goes to the white HTC splash screen and the MIUI initializes and goes black immediately. There doesn't seem to be a way to get my phone connected to my computer to get into the SD card to troubleshoot from inside the phone. Hopefully one of you guys has the answer for me. Is there any way to get into it via bootloader usb?

Cainsmoker said:
Hmmm....the firmware update didn't work.
I can verify that I'm on the firmware 3.3, Hboot is 1.27.1100, Radio is 11.24A.3504.31_M.
Each time Hboot is run it asks if I want to start the update. If I select yes, I've got 9 on screen options that it runs through and tells me "Update complete. Press power to reboot" The only way to do anything at all is to take out the SD card so it does not try to load up the firmware zip
Pushing power reboots the phone on an endless boot loop. Regardless of what ROM is being used (I also downloaded cyanogenmod) I can not make it past the spash screen.
Could it be that I'm just flashing the ROM incorrectly? To my knowledge I've followed instructions for both and have backed up my phone and it's contents and done everything from a factory reset/wipe to wiping the dalvik cache, etc. I didn't have this many problems rooting my phone and putting on MIUI to begin with and have flashed ROMS before with no trouble....not really sure where I'm going wrong on this one.
Anyway, I'll await your reply.
Thank you!
-Cain
Update: awww frick. So now it looks like this will be more difficult....I hope you like a challenge. I can now no longer get into my phone. It appears that it's soft bricked. I have tried going to a clockwork mod recovery from my first MIUI in 2012, it goes through the entire process of factory resetting restoring the boot image, system and data information. It asks for a reboot which I do. It goes to the white HTC splash screen and the MIUI initializes and goes black immediately. There doesn't seem to be a way to get my phone connected to my computer to get into the SD card to troubleshoot from inside the phone. Hopefully one of you guys has the answer for me. Is there any way to get into it via bootloader usb?
Click to expand...
Click to collapse
remove the pg58img.zip from your sdcard so it won't scan and identify any pg58img.zip file
and don't restore your miui rom because probably is a gb one and now you have an ics firmware installed
just download an ics or jb rom
put it on your sdcard
full wipe from recovery
flash the rom
done

rzr86 said:
remove the pg58img.zip from your sdcard so it won't scan and identify any pg58img.zip file
and don't restore your miui rom because probably is a gb one and now you have an ics firmware installed
just download an ics or jb rom
put it on your sdcard
full wipe from recovery
flash the rom
done
Click to expand...
Click to collapse
With the phone being in a boot loop I can't get it detected by my computer to remove/add anything from the SD card. I do have the HD 7.3 ROM on and the Gapps that's required but it never makes it past the "beats audio" splash screen. I have no idea what's going on with it but will try any suggestions you've got up your sleeve.

Ahhhhh....I've gotten a fix for this!
I was unable to do anything because of the update zip which wanted me to update every time bootloader was initiated. By keeping my case off I removed my SD card to be able to boot in recovery and then put the SD card back in to load the HD 7.3 zip from the card. This seemed to take care of the problem.
Thanks for the help Rzr