Database Info

[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] How do I unbrick my phone?

So tonight I began the process of unlocking my phone and installing a custom ROM. I unlocked my phone successfully with the toolkit and was able to get into recovery and begin flashing my first ROM (Cyangogen 10 most recent nightly along with the Gapps). However on my first reboot after flashing the room, I started to realize something was awry when after 20-30 minutes it was still on a boot screen. I proceeded to try and reflash the ROM 2 more times with no real change in outcome. Whenever I tried booting out of recovery I would get a warning stopping me saying that no OS was installed, despite having clearly flashed a new ROM. Okay, so as a last ditch effort I went into the bootloader mode and enabled fastboot so that I could try the RUU - which of course failed despite 2-3 attempts at using the utility. After the RUU failures I also noticed that my SD card would no longer mount unless I manually formatted it - which I finally gave in to and was able to load another custom rom (Jellybam this time) which also would get stuck on the boot screen despite successfully flashing. So now I'm basically stuck in a limbo land where no custom ROM will boot into the OS and the RUU to take me back to stock has failed. Any suggestions on how to get out of this? (I've read in other places that you can use fastboot to flash files in the bootloader but my attempts at doings this have also been unsuccessful - if this is the route to go can anyone give me some specific instructions on how to do it?)
Thanks in advance guys.
Phone Specifics - AT&T HTC One X, 16gb running the 2.2 firmware on Android 4.04 before I got into all this nonsense.

Dissentire77 said:
So tonight I began the process of unlocking my phone and installing a custom ROM. I unlocked my phone successfully with the toolkit and was able to get into recovery and begin flashing my first ROM (Cyangogen 10 most recent nightly along with the Gapps). However on my first reboot after flashing the room, I started to realize something was awry when after 20-30 minutes it was still on a boot screen. I proceeded to try and reflash the ROM 2 more times with no real change in outcome. Whenever I tried booting out of recovery I would get a warning stopping me saying that no OS was installed, despite having clearly flashed a new ROM. Okay, so as a last ditch effort I went into the bootloader mode and enabled fastboot so that I could try the RUU - which of course failed despite 2-3 attempts at using the utility. After the RUU failures I also noticed that my SD card would no longer mount unless I manually formatted it - which I finally gave in to and was able to load another custom rom (Jellybam this time) which also would get stuck on the boot screen despite successfully flashing. So now I'm basically stuck in a limbo land where no custom ROM will boot into the OS and the RUU to take me back to stock has failed. Any suggestions on how to get out of this? (I've read in other places that you can use fastboot to flash files in the bootloader but my attempts at doings this have also been unsuccessful - if this is the route to go can anyone give me some specific instructions on how to do it?)
Thanks in advance guys.
Phone Specifics - AT&T HTC One X, 16gb running the 2.2 firmware on Android 4.04 before I got into all this nonsense.
Click to expand...
Click to collapse
You know you also have to relock the bootloader before you RUU Right?
and if your on hboot 1.14 you have to flash the boot img separately from the zip(in the folder you put fastboot,adb,etc.)

WhatTheAndroid? said:
You know you also have to relock the bootloader before you RUU Right?
and if your on hboot 1.14 you have to flash the boot img separately from the zip(in the folder you put fastboot,adb,etc.)
Click to expand...
Click to collapse
I was forgetting to relock the bootloader, thanks man. Was able to go back to stock, restart the process and am now rocking CM10. This is why I love XDA.

Dissentire77 said:
I was forgetting to relock the bootloader, thanks man. Was able to go back to stock, restart the process and am now rocking CM10. This is why I love XDA.
Click to expand...
Click to collapse
Sounds like a thanks button click is on order for WhatTheAndroids post to you
ViperXL 2.4.0 w/ElementalX 3.1 kernel

What went wrong?

I was pulling my hair out for a few hours last night trying to get my phone back to a functional state. Fortunately I was able to do so, but I have no idea what caused all of my problems. Here's what happened:
I was running CM10 on my HOX (from this thread) for awhile now. I was having a few issues with it that were annoying but I didn't want to change the ROM and have to restore everything. I then got a notification for an update to CM10.1 so I downloaded that and installed it. During this process I decided to do a Factory Reset in TWRP.
Once I was booted back into CM10.1 I was having all sorts of strange issues, but the biggest one was that I was unable to connect to my cell network and it kept prompting me to restart. I decided I would just install another ROM so I downloaded CleanROM JL Beta 1 (here) and the Bulletproof-1.0 kernel (here).
I booted into TWPR and proceeded to wipe everything (i.e. clicked all of the buttons under the 'Wipe' menu). I've done this before and haven't had any problems. I then proceeded to install the kernel. It went through the installer fine without any issues. When I tried to install CleanROM JL Beta 1 in TWRP it just kept giving me an error and wouldn't bring up the installer.
I went back and forth trying to install multiple ROMs and every single one would give me an error. I thought I was screwed because I couldn't install an OS on the phone. I also went ahead and installed the stock kernel hoping that would fix the problem but it didn't. I eventually decided on finding the RUU to get me back to bone stock.
I downloaded the 2.20 RUU and relocked my bootloader. I went through the RUU process and everything is fine now, except the fact that I have a stock, bloated phone again.
Was it the kernel that messed me up? I installed it after I wiped everything and I'm not sure if I was supposed to do it that way. I'd like to get back to something stable again but I am not sure if I am able to since I relocked my bootloader and installed the 2.20 RUU. Any help is much appreciated, thanks!
NEW ISSUE #1: I just tried to install the 4.1 OTA update from AT&T. I donwloaded the update and proceeded to install it, but after it restarted everything on my phone was erased and it was set back to factory default on 4.0.1. Now when I check for updates it tells me there are nor updates, the server is full, or 'HtcDm has stopped'. What the hell happened there?
NEW ISSUE #2: I went ahead and tried the OTA update again and now my phone won't turn on and shows no status LED light when plugged in. Back to Best Buy it goes. I need a Nexus...

If you are S-on, did you remember to extract and flash boot.img seperately for each of the ROMs you tried?
Now combo of CleanROM JL and Bulletproof should have worked fine. Don't know what happened there. How did you flash Bulletproof? Using recovery or fastboot?

redpoint73 said:
If you are S-on, did you remember to extract and flash boot.img seperately for each of the ROMs you tried?
Now combo of CleanROM JL and Bulletproof should have worked fine. Don't know what happened there. How did you flash Bulletproof? Using recovery or fastboot?
Click to expand...
Click to collapse
I am S-ON and I did not flash the boot.img via fastboot at first, but then tried that after the ROM wouldn't install. I flashed the Bulletproof-1.0 kernel via TWRP.

afrat said:
I am S-ON and I did not flash the boot.img via fastboot at first, but then tried that after the ROM wouldn't install. I flashed the Bulletproof-1.0 kernel via TWRP.
Click to expand...
Click to collapse
You can't flash kernels in recovery with hboot 1.14 and S-on.
Not sure what you mean by "after the ROM wouldn't install" (the exact sequence of ROM flashing versus flashing boot.img using fastboot). But what you are describing is sounding like ROM-kernel mismatches.

redpoint73 said:
You can't flash kernels in recovery with hboot 1.14 and S-on.
Not sure what you mean by "after the ROM wouldn't install" (the exact sequence of ROM flashing versus flashing boot.img using fastboot). But what you are describing is sounding like ROM-kernel mismatches.
Click to expand...
Click to collapse
I followed the instructions given in the Bulletproof-1.0 post that said to install the zip via TWRP. I did that and everything went fine. I then tried installing CleanROM JL Beta immediately after and it would just give me the zip error.
What I mean by "after the ROM wouldn't install" was after it wouldn't install via TWRP. I then went back and extracted the boot.img, flashed it with fastboot, then went back into TWRP to try and install it again. That didn't work.

redpoint73 said:
You can't flash kernels in recovery with hboot 1.14 and S-on.
Not sure what you mean by "after the ROM wouldn't install" (the exact sequence of ROM flashing versus flashing boot.img using fastboot). But what you are describing is sounding like ROM-kernel mismatches.
Click to expand...
Click to collapse
In op it says he flashed kernel then rom, the rom would have overwritten the kernel flash if thats the order he did it in wouldn't it have? Im thinking it was a bad Cleanrom download he was trying to flash since it gave an error in recovery when he tried to flash it and wouldn't load it at all. Or maybe a bad TWRP image? Just guessing here.

eraste said:
In op it says he flashed kernel then rom, the rom would have overwritten the kernel flash if thats the order he did it in wouldn't it have? Im thinking it was a bad Cleanrom download he was trying to flash since it gave an error in recovery when he tried to flash it and wouldn't load it at all. Or maybe a bad TWRP image? Just guessing here.
Click to expand...
Click to collapse
I also tried installing multiple other ROMs, all giving me the same zip error in TWRP. I forgot to mention that before I installed CM10.1 I downloaded GooManager and that's what kept prompting me to install the CM10.1 version. I also installed the latest TWRP through GooManager as that was what was recommended in the TWRP post as the best way to do so.

afrat said:
I followed the instructions given in the Bulletproof-1.0 post that said to install the zip via TWRP. I did that and everything went fine.
Click to expand...
Click to collapse
If you keep reading on the Bulletproof instructions, you will see:
hboot 1.14+ and S-ON:
The installer includes a method to flash the boot.img for S-ON devices using hboot 1.14 or higher;
however, some people still have difficulties. If it doesn't work:
1. extract boot.img from the zip, reboot to bootloader and do:
fastboot flash boot boot.img​
---------- Post added at 04:26 PM ---------- Previous post was at 04:21 PM ----------
eraste said:
In op it says he flashed kernel then rom, the rom would have overwritten the kernel flash if thats the order he did it in wouldn't it have?
Click to expand...
Click to collapse
With hboot<1.14, or with S-on yes. But in his case no. For hboot 1.14 and higher and S-on, you can flash the kernel before or after the ROM, it doesn't matter since the kernel can't be flashed from recovery.
---------- Post added at 04:29 PM ---------- Previous post was at 04:26 PM ----------
afrat said:
I also tried installing multiple other ROMs, all giving me the same zip error in TWRP. I forgot to mention that before I installed CM10.1 I downloaded GooManager and that's what kept prompting me to install the CM10.1 version. I also installed the latest TWRP through GooManager as that was what was recommended in the TWRP post as the best way to do so.
Click to expand...
Click to collapse
What version of TWRP? The latest build has some serious problems. zip errors for multiple ROMs is making me think its TWRP that is causing you the headache, for the most part.

redpoint73 said:
What version of TWRP? The latest build has some serious problems. zip errors for multiple ROMs is making me think its TWRP that is causing you the headache, for the most part.
Click to expand...
Click to collapse
I'm not sure. If I did the RUU, does that mean I lost the custom recovery (TWRP) that I've installed as well?

I just tried to install the 4.1 OTA update from AT&T. I donwloaded the update and proceeded to install it, but after it restarted everything on my phone was erased and it was set back to factory default on 4.0.1. Now when I check for updates it tells me there are nor updates, the server is full, or 'HtcDm has stopped'. What the hell happened there?

I went ahead and tried the OTA update again and now my phone won't turn on and shows no status LED light when plugged in. Back to Best Buy it goes. I need a Nexus...

afrat said:
I went ahead and tried the OTA update again and now my phone won't turn on and shows no status LED light when plugged in. Back to Best Buy it goes. I need a Nexus...
Click to expand...
Click to collapse
Ok. Wierd. You think the ota bricked your phone? It wont power on in any way? No recovery or anything?
Note 2 ftw

eraste said:
Ok. Wierd. You think the ota bricked your phone? It wont power on in any way? No recovery or anything?
Note 2 ftw
Click to expand...
Click to collapse
It's completely dead. It's quite alright though, Best Buy said they will replace it for me. Gotta love that insurance!

afrat said:
It's completely dead. It's quite alright though, Best Buy said they will replace it for me. Gotta love that insurance!
Click to expand...
Click to collapse
Thats good. But if this did cause the brick knowing what it was would help others! So you were completely stock on the 2.20 ruu then tried to install the OTA right?
Did you have supercid?

eraste said:
Thats good. But if this did cause the brick knowing what it was would help others! So you were completely stock on the 2.20 ruu then tried to install the OTA right?
Did you have supercid?
Click to expand...
Click to collapse
I was completely stock from the 2.20 RUU and then tried applying the OTA update. I started to OTA update once and it rebooted my phone a few times only to have it reset to factory settings with 4.0.4. I then checked multiple times by bumping my clock forward to get the update again (I am assuming the servers were busy which is what was giving me errors). I was able to get the update to download again and then began installing it for a second time. This time is sat on the screen with the refresh icon over the phone with the status bar underneath for a few minutes, then restarted three times with just the phone icon on it, and then powered off completely, never to turn on again.
I did have supercid, at least I think I did, I can't remember exactly what I did to obtain root/unlocked bootloader/custom roms back when I first started messing with it.

afrat said:
I was completely stock from the 2.20 RUU and then tried applying the OTA update. I started to OTA update once and it rebooted my phone a few times only to have it reset to factory settings with 4.0.4. I then checked multiple times by bumping my clock forward to get the update again (I am assuming the servers were busy which is what was giving me errors). I was able to get the update to download again and then began installing it for a second time. This time is sat on the screen with the refresh icon over the phone with the status bar underneath for a few minutes, then restarted three times with just the phone icon on it, and then powered off completely, never to turn on again.
I did have supercid, at least I think I did, I can't remember exactly what I did to obtain root/unlocked bootloader/custom roms back when I first started messing with it.
Click to expand...
Click to collapse
Strange. Really strange.

eraste said:
Strange. Really strange.
Click to expand...
Click to collapse
It is indeed. I am wondering if all my random flashing attempts at different kernels and boot.img files and ROMs just messed something up. I thought that doing the RUU replaced EVERYTHING I could have done to my phone, minus the unlocked bootloader, so maybe it was just a messed up OTA file.
Regardless, I am very glad I got the BB insurance plan. I can have my device completely replaced multiple times during the 2-year plan and there is no deductible or rate increase, it's crazy.

I seem to recall that some people who took the OTA with supercid on earlier JB updates reported getting bricked.

afrat said:
It is indeed. I am wondering if all my random flashing attempts at different kernels and boot.img files and ROMs just messed something up. I thought that doing the RUU replaced EVERYTHING I could have done to my phone, minus the unlocked bootloader, so maybe it was just a messed up OTA file.
Regardless, I am very glad I got the BB insurance plan. I can have my device completely replaced multiple times during the 2-year plan and there is no deductible or rate increase, it's crazy.
Click to expand...
Click to collapse
Yes ruu would have put you back to stock with the exception of supercid that would have stayed.
iElvis said:
I seem to recall that some people who took the OTA with supercid on earlier JB updates reported getting bricked.
Click to expand...
Click to collapse
Me to this was my initial thought super cid was the culprit!

eraste said:
Me too this was my initial thought super cid was the culprit!
Click to expand...
Click to collapse
But some others insisted that it couldn't have been the issue. SuperCID is supposed to allow flashing of any updates regardless of CID restrictions.

[Q] Custom Roms not working

Hello, long time reader, first time poster. I know about rooting, and installing roms and all that good stuff (had a galaxy s2 but odin bricked it). So I'm new to the sensation, and it's quite different from my previous device. My problem is that when I install a custom rom, the phone will boot and all about after about 30 seconds will freeze and restart.
Okay so these are the steps that I followed:
-Used the KGS Utility and chose "s-off"
-Followed all the prompts everything worked out fine.
-Following that I used it to install a custom recovery.
-Followed the prompts everything worked fine.
-Then I used Revolutionary CWM to flash SuperUser.
-App was there on reboot.
-Then I downloaded the AOKP "Initiate Your Swagger"[4.1.2] Rom
-Put it on my SD card and flashed it (after wiping and backing up)
-When the phone boots the setup wizard starts.
-I follow the prompt and when it gets to "Just a sec" the phone freezes then restarts.
Don't know what the problem is here.
I get the same problem when trying to flash CM10. The phone will boot, but then after 20-30 seconds will reboot.

kojimin said:
Hello, long time reader, first time poster. I know about rooting, and installing roms and all that good stuff (had a galaxy s2 but odin bricked it). So I'm new to the sensation, and it's quite different from my previous device. My problem is that when I install a custom rom, the phone will boot and all about after about 30 seconds will freeze and restart. I also noticed that there is no signal in custom roms either. Don't know what I'm doing wrong here. I used an all in one tool to do s-off, and install a custom recovery. Then I rooted it. Then I started trying to install custom roms but they don't seem to work. What am I doing wrong?
Click to expand...
Click to collapse
Be VERY specific and give a step by step detail of what you are doing to install. Give WAY more detail than you have. And put the detail in a list, not a giant paragraph.
Then we'll look at it and see what's missing.

Skipjacks said:
Be VERY specific and give a step by step detail of what you are doing to install. Give WAY more detail than you have. And put the detail in a list, not a giant paragraph.
Then we'll look at it and see what's missing.
Click to expand...
Click to collapse
Sorry about that. Edited my first post. I hope that is enough.

When you say it boots for 20 seconds, what exaclty for you mean.
Does it just replay the boot animation over and over? Or does it actually bring you to a home screen with the status bar and everything for 20 seconds before the reboot? That's a very important difference in diagnosing this one.
Also try installing 4EXT recovery. CWM has been known to cause weirdness with AOSP roms. Plus you may have an older version of CWM thatcan't properly install the newer roms. If you used a .zip in bootloader to flash CWM yuou probably had an older version. I have a special place in my heart for CWM too, but 4EXT is just so much better for the Sensation. (Different recoveries ar ebetter or worse on different devices.)
If you properly installed superuser on your stock rom that you have a nandroid backup for, installing 4EXT is super easy. Just restore the nandroid, which should boot up without problems, download the 4EXT app from the play store, and use the app to install teh latest version of the recovery. No need for ADB or flashing in bootloader. Then try a full wipe and fresh install of AOKP from 4EXT.

Skipjacks said:
When you say it boots for 20 seconds, what exaclty for you mean.
Does it just replay the boot animation over and over? Or does it actually bring you to a home screen with the status bar and everything for 20 seconds before the reboot? That's a very important difference in diagnosing this one.
Also try installing 4EXT recovery. CWM has been known to cause weirdness with AOSP roms. Plus you may have an older version of CWM thatcan't properly install the newer roms. If you used a .zip in bootloader to flash CWM yuou probably had an older version. I have a special place in my heart for CWM too, but 4EXT is just so much better for the Sensation. (Different recoveries ar ebetter or worse on different devices.)
If you properly installed superuser on your stock rom that you have a nandroid backup for, installing 4EXT is super easy. Just restore the nandroid, which should boot up without problems, download the 4EXT app from the play store, and use the app to install teh latest version of the recovery. No need for ADB or flashing in bootloader. Then try a full wipe and fresh install of AOKP from 4EXT.
Click to expand...
Click to collapse
It boots up to the homescreen (with no signal) then it reboots.
I will try 4EXT and post my results. Thanks for your help thus far!
EDIT: Tryed installing 4EXT now when I try to boot into recovery it shows the HTC spash screen, then it reboots back the homescreen. So I think my recovery is gone.
EDIT 2: So I got the 4EXT recovery installed. But the ROMs are giving me the same issues (no change). I also noticed as before, when the custom roms boot there isn't any cellular signal.

kojimin said:
It boots up to the homescreen (with no signal) then it reboots.
I will try 4EXT and post my results. Thanks for your help thus far!
EDIT: Tryed installing 4EXT now when I try to boot into recovery it shows the HTC spash screen, then it reboots back the homescreen. So I think my recovery is gone.
EDIT 2: So I got the 4EXT recovery installed. But the ROMs are giving me the same issues (no change). I also noticed as before, when the custom roms boot there isn't any cellular signal.
Click to expand...
Click to collapse
Update the firmware.. You are on gingerbread firmware (revolutionary soff worked for you means you are on GB) and it won't work on ics/jb roms
Check the firmware thread by kohr-ah in sensation development section and flash universal 3.33 firmware
It will solve your rom problems
Sent from my HTC Sensation 4G using xda premium

ganeshp said:
Update the firmware.. You are on gingerbread firmware (revolutionary soff worked for you means you are on GB) and it won't work on ics/jb roms
Check the firmware thread by kohr-ah in sensation development section and flash universal 3.33 firmware
It will solve your rom problems
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
it was the firmware! I just updated to 3.33, and 4.1.2 "Initiate your swagger" booted up completely. Thanks for your help :good:

Awesome reply mate :
Sent from my HTC Sensation XE with Beats Audio using xda premium

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