Database Info

Double reboot-loop after succesfull boot.img

Hey guys,
I can really use your help - I thought this would be relatively easy but boy was I wrong.
I started with an HTC Sensation (locked / unrooted / S-ON / ICS) with HBOOT 1.27
What did I do to end up where I am now?
1. http://forum.xda-developers.com/showthread.php?t=1497404 - I followed all the steps top left to unlock the bootloader, which succeeded. Only to find out I needed to S-OFF the device differently.
2. http://forum.xda-developers.com/showthread.php?t=1614617 - I followed this guide, but did nothing with step 2 (I didn't have a superuser application and couldn't get root because I didn't have any custom abilities since the device was S-ON still). Device was succesfully S-OFF.
3. Here I installed JuopunutBear HBOOT-1.27.1111
4. Then I flashed CWM Recovery 6.0.0.3 for the pyramid by following these instructions: http://www.androidauthority.com/sensation-clockworkmod-recovery-6-0-0-3-custom-recovery-105930/ and removed the PG58IMG.zip file again.
5. Now I booted the CWM Recovery with a fully empty Micro-SD card (already formatted from previous use in same device). I do a factory reset and wipe all cache (including dalvik/battery stats). I then install January 9 '13 release (Bruce AOKP) and then GAPPS latest version for 4.1.2 - succesful.
6 Here I think I am done, reboot ... HTC white screen ... reboot ... HTC white screen ... CWM Recovery. What the ... happens everytime. After some searching people said because my phone was unlocked (HTCDev method) before installing custom ROM I should install boot.img manually. Did that (yes I used the boot.img from Bruce his zip) using fastboot flash boot boot.img - succes (so it said).
7. Step 6 changed nothing ... and here I am stuck .... please help me to get into my favourite mod!
Extra information: Version-Main = 1.24.401.1, full JuopunutBear intro screen info:
=JuopunutBear=
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1111
eMMC-boot
Jan 13 2012, 17:33:34
Please help me continue and make it run. I have a feeling maybe something in the root steps or whatever - but this process is not as easy as many users here make it seem. Sifting through the info ... I was surprised I got this far :silly: ...

SensationProblem said:
Hey guys,
I can really use your help - I thought this would be relatively easy but boy was I wrong.
I started with an HTC Sensation (locked / unrooted / S-ON / ICS) with HBOOT 1.27
What did I do to end up where I am now?
1. http://forum.xda-developers.com/showthread.php?t=1497404 - I followed all the steps top left to unlock the bootloader, which succeeded. Only to find out I needed to S-OFF the device differently.
2. http://forum.xda-developers.com/showthread.php?t=1614617 - I followed this guide, but did nothing with step 2 (I didn't have a superuser application and couldn't get root because I didn't have any custom abilities since the device was S-ON still). Device was succesfully S-OFF.
3. Here I installed JuopunutBear HBOOT-1.27.1111
4. Then I flashed CWM Recovery 6.0.0.3 for the pyramid by following these instructions: http://www.androidauthority.com/sensation-clockworkmod-recovery-6-0-0-3-custom-recovery-105930/ and removed the PG58IMG.zip file again.
5. Now I booted the CWM Recovery with a fully empty Micro-SD card (already formatted from previous use in same device). I do a factory reset and wipe all cache (including dalvik/battery stats). I then install January 9 '13 release (Bruce AOKP) and then GAPPS latest version for 4.1.2 - succesful.
6 Here I think I am done, reboot ... HTC white screen ... reboot ... HTC white screen ... CWM Recovery. What the ... happens everytime. After some searching people said because my phone was unlocked (HTCDev method) before installing custom ROM I should install boot.img manually. Did that (yes I used the boot.img from Bruce his zip) using fastboot flash boot boot.img - succes (so it said).
7. Step 6 changed nothing ... and here I am stuck .... please help me to get into my favourite mod!
Extra information: Version-Main = 1.24.401.1, full JuopunutBear intro screen info:
=JuopunutBear=
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1111
eMMC-boot
Jan 13 2012, 17:33:34
Please help me continue and make it run. I have a feeling maybe something in the root steps or whatever - but this process is not as easy as many users here make it seem. Sifting through the info ... I was surprised I got this far :silly: ...
Click to expand...
Click to collapse
Hi,
Did you root your phone?
Look HERE

malybru said:
Hi,
Did you root your phone?
Look HERE
Click to expand...
Click to collapse
Root is a userspace level thing that shouldn't affect the installations of ROMs, plus all ROMs (except for stock ROMs) come pre-rooted. SensationProblem, I suggest you install the TWRP recovery from here: http://techerrata.com/file/twrp2/pyramid/openrecovery-twrp-2.4.1.0-pyramid.img
Flash this using fastboot. This is the command to flash it:
Code:
fastboot flash recovery openrecovery-twrp-2.4.1.0-pyramid.img
After it completes successfully, reboot the bootloader then after it reboots back into the bootloader select the bootloader option then just enter the recovery from there. In the recovery, go to Wipe and wipe the Cache, Dalvik Cache, Factory Reset, and System, then flash Bruce's CM10.

android1234567 said:
Root is a userspace level thing that shouldn't affect the installations of ROMs, plus all ROMs (except for stock ROMs) come pre-rooted. SensationProblem, I suggest you install the TWRP recovery from here.
Flash this using fastboot. This is the command to flash it:
Code:
fastboot flash recovery openrecovery-twrp-2.4.1.0-pyramid.img
After it completes successfully, reboot the bootloader then after it reboots back into the bootloader select the bootloader option then just enter the recovery from there. In the recovery, go to Wipe and wipe the Cache, Dalvik Cache, Factory Reset, and System, then flash Bruce's CM10.
Click to expand...
Click to collapse
Dude that worked, thank you so much (want to give kudo's - can't find button). Can you maybe shortly explain to me why it worked? Because as I can understand it now it was because of something in the CWM Recovery that was messing things up?

SensationProblem said:
Dude that worked, thank you so much (want to give kudo's - can't find button). Can you maybe shortly explain to me why it worked? Because as I can understand it now it was because of something in the CWM Recovery that was messing things up?
Click to expand...
Click to collapse
The current version of CWM for the Sensation is extremely old and, as a result, does not support the installation of Jelly Bean ROMs.

[Q] Stupid mistake - now stuck in boot loop

I'm not sure what I did wrong but I'm sure it's my fault.
Here goes.
I had an HTC One S (that I rooted using Hassoon's tool ver. 3.3.1). I go rid of it.
Now I got another one for my cousin. We decided to root it and flash a custom ROM.
I followed the steps in the tool up to where you flash your own recovery (which I did; TeamWin latest version from site).
While the phone rebooted we went and got CM10 (the monthly) and GAPPS.
The phone then started up but for some reason a warning came up saying we didn't have root and we had to finish installing SuperUser. We did. The phone rebooted. We put the new ROM and GAPPS in the internal storage.
Rebooted to recovery. Wiped everything except the internal memory (we did not back up) and installed the new rom. Now the phone is stuck on the HTC splash screen.
I tried following another thread here and fear I may have made things worse for myself. I downloaded the latest tool from Hassoon and ran the command "fastboot oem lock" in an attempt to maybe return back to a stock rom or something where we can UN-brick this phone.
Anyway I'm in over my head.. please help.
Here's the info.
***TAMPERED***
***RELOCKED***
VLE PVT SHIP S-ON RL
HBOOT-1.14.0005
RADIO-1.11T.50.02.22
OpenDSP-v29.1.0.45.0622
eMMC-boot
Nov 21 2012, 12:17:41

You needed to flash the kernel for the new rom you installed.

hasoon2000 said:
You needed to flash the kernel for the new rom you installed.
Click to expand...
Click to collapse
did it resolved the problem?

hasoon2000 said:
You needed to flash the kernel for the new rom you installed.
Click to expand...
Click to collapse
Forgive me for being "slow" but..
Doesn't CyanogenMod 10.1 come with it's own Kernel?
If not then I may need a link directly to a kernel that I can download and then flash (I looked on the cyanogenmod website and the only thing I could find was how to build the Kernel in Linux).

Ysleiro said:
Forgive me for being "slow" but..
Doesn't CyanogenMod 10.1 come with it's own Kernel?
If not then I may need a link directly to a kernel that I can download and then flash (I looked on the cyanogenmod website and the only thing I could find was how to build the Kernel in Linux).
Click to expand...
Click to collapse
S-ON devices with HBOOT version of 1.13 or higher do not allow kernels to be flashed through recovery. So even though you have flashed the ROM, the kernel will not have been flashed. You'll need to extract the boot.img from the ROM zip file manually, boot the phone into fastboot mode then use the command:
fastboot flash boot boot.img
This will flash the kernel manually.

djsubtronic said:
S-ON devices with HBOOT version of 1.13 or higher do not allow kernels to be flashed through recovery. So even though you have flashed the ROM, the kernel will not have been flashed. You'll need to extract the boot.img from the ROM zip file manually, boot the phone into fastboot mode then use the command:
fastboot flash boot boot.img
This will flash the kernel manually.
Click to expand...
Click to collapse
MUCH APPRECIATED. Solved!
I will be donating to the both of you for your commitment to the community.

[Q]Rogers One X Stuck in Bootloop

Hello all. So a friend of mine handed me his One X today and from what I gathered he was unable to flash CM after unlocking the bootloader and flashing CWM recovery. I figured I would give it a shot since I am familiar with flashing roms etc but wow what a difference it is for HTC devices!
I've spent the past 2 or 3 hours browsing this subforum however I feel like I could be just misinforming myself. The phone is a Rogers HTC One X the firmware version it was running I am unsure of as its currently stuck in bootloop. I've attached a screenshot below of the current fastboot menu. As it seems the bootloader is indeed unlocked however it is still s-on and stock recovery. If someone would be kind enough as to point me in the right direction of how to gain root and flash a recovery I would be super grateful. Feel free to PM me as well.
Thanks for your time.

What is the full filename of the ROM you're trying to flash? Also, the phone is s-on so you would need to flash the boot.img via fastboot to get it to boot.
Sent from my Evita

timmaaa said:
What is the full filename of the ROM you're trying to flash? Also, the phone is s-on so you would need to flash the boot.img via fastboot to get it to boot.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply. From what I was told he flashed the latest CM nightlies for Evita through CWM. Although now it appears to have the stock recovery.
So as far as gaining root and flashing a recovery, since the bootloader is unlocked can I not simply flash a recovery through fastboot and then flash a rom with SU like CM?

Yeah you can, use TWRP recovery instead of CWM though. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you have TWRP on the phone. Go into it, wipe cache/dalvik/factory reset/system, then install the ROM and gapps. Like I said though you'll need to flash the boot.img via fastboot afterwards. So once you've installed the ROM reboot to bootloader, grab the boot.img from the ROM zip and flash it using this command:
Code:
fastboot flash boot boot.img
Once that's completed you should be able to reboot into the ROM. Please note though that some of the latest CM ROMs have a few bugs, including booting problems.
Sent from my Evita

Hey thanks again timaaa for the fast reply! I've successfully booted into CM now after flashing the boot.img. Regarding the bootloader should I be concerned with s-on? Will I run into trouble down the road because I do not have s-off?

Cool, glad you got it booted. In my opinion getting s-off would be a good idea. The benefits include the following:
Not needing to flash the boot.img from a ROM/kernel through fastboot anymore.
Being able to flash radios (s-on restricts this on phones with a hboot equal to or greater than 1.14).
Being able to change hboot freely (or just remove the red warning text from the startup screen).
Being able to change CID if needed.
Being able to flash the required firmware package which is required to run current Sense 5 ROMs.
In order to get s-off you first need SuperCID though, the hex edit method will be the best to use. Here's a link:
http://forum.xda-developers.com/showthread.php?t=2212737
Once you have SuperCID you can go ahead and get s-off here:
http://forum.xda-developers.com/showthread.php?t=2155071
Both processes are pretty quick and simple, and the benefits are great.
Sent from my Evita

[Q] Please help phone has no OS

Okay so here is what happened i unlocked my bootloader and rooted my phone using the all in one toolkit, i tried to flash a custom ROM using the GooManager app. This is where things went wrong. After flashing the ROM my phone shut off and would only turn on to the HTC Quietly Brilliant page at the beginning of the boot cycle, i made a backup but dont know how to find it. I somehow managed to wipe the entire phone and now i have no operating system. I had TWRP installed but cannot access it because i relocked the phone. Is there anyway to get this thing working again? any help would be much appreciated
here is what my fastboot screen reads:
***TAMPERED***
***RELOCKED***
EVITA PVT SHIP S-ON RL
HBOOT- 2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012,18:37:14:-1
FASTBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN

brenntard said:
Okay so here is what happened i unlocked my bootloader and rooted my phone using the all in one toolkit, i tried to flash a custom ROM using the GooManager app. This is where things went wrong. After flashing the ROM my phone shut off and would only turn on to the HTC Quietly Brilliant page at the beginning of the boot cycle, i made a backup but dont know how to find it. I somehow managed to wipe the entire phone and now i have no operating system. I had TWRP installed but cannot access it because i relocked the phone. Is there anyway to get this thing working again? any help would be much appreciated
here is what my fastboot screen reads:
***TAMPERED***
***RELOCKED***
EVITA PVT SHIP S-ON RL
HBOOT- 2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012,18:37:14:-1
FASTBOOT
to previous item
to next item
to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Click to expand...
Click to collapse
Since you are s-on, you need to fastboot flash boot boot.IMG from the ROM you want to use. While you're at it you may as well just s-off your device. It will make things simpler in the end. You're going to have to unlock the boot loader again to flash the boot image though. You will also want to flash recovery again via fastboot.
Sent from my One X using XDA Premium 4 mobile app

Black!Jack said:
Since you are s-on, you need to fastboot flash boot boot.IMG from the ROM you want to use. While you're at it you may as well just s-off your device. It will make things simpler in the end. You're going to have to unlock the boot loader again to flash the boot image though. You will also want to flash recovery again via fastboot.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you so much for the response...i have a couple questions. I am fairly new to android and these are the first real problems i have run into that i havent been able to solve on my own. how do i "fastboot flash boot boot.IMG"? i just want to use the stock ROM or CM10 which ever will get my phone running again. I have unlocked to bootloader again and now have access to TWRP

brenntard said:
Thank you so much for the response...i have a couple questions. I am fairly new to android and these are the first real problems i have run into that i havent been able to solve on my own. how do i "fastboot flash boot boot.IMG"? i just want to use the stock ROM or CM10 which ever will get my phone running again. I have unlocked to bootloader again and now have access to TWRP
Click to expand...
Click to collapse
Take a look at this thread
http://forum.xda-developers.com/showthread.php?t=2136172
It will answer many of the questions that you have and provides links to appropriate tools.
You should definitely s-off your device now. Just look for the question in the thread I linked for more detail. Bookmark it as well, or add it to your favorites, as it will provide a great reference point for future use.
Once you have s-off, you will just have to flash any ROM you want from recovery. It will make your life way easier.
If someone helps you, just hit the thanks button, or thumbs up from the xda app.
Sent from my One X using XDA Premium 4 mobile app

Black!Jack said:
Take a look at this thread
http://forum.xda-developers.com/showthread.php?t=2136172
It will answer many of the questions that you have and provides links to appropriate tools.
You should definitely s-off your device now. Just look for the question in the thread I linked for more detail. Bookmark it as well, or add it to your favorites, as it will provide a great reference point for future use.
Once you have s-off, you will just have to flash any ROM you want from recovery. It will make your life way easier.
If someone helps you, just hit the thanks button, or thumbs up from the xda app.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In the rumrunner instructions to s-off my device it says i need to have fast boot unchecked in settings. I am pretty sure i have it checked but there is no way for me to tell for sure...since i dont have an OS installed is this an issue?

brenntard said:
In the rumrunner instructions to s-off my device it says i need to have fast boot unchecked in settings. I am pretty sure i have it checked but there is no way for me to tell for sure...since i dont have an OS installed is this an issue?
Click to expand...
Click to collapse
You need to get a ROM booting brute trying s-off. Don't use Goo Manager to install ROMs, install manually through TWRP recovery. Once you've installed the ROM reboot to the bootloader and flash the boot.img. Here's how to flash the boot.img.
Extract the boot.img from the ROM zip and copy it into your fastboot folder on your pc. After you've flashed the ROM and/or gapps, reboot to bootloader and connect your phone, make sure it says fastboot on your phone screen. Then you can issue the following command:
Code:
fastboot flash boot boot.img
Now you can reboot your phone into the ROM.
Sent from my Evita.

timmaaa said:
You need to get a ROM booting brute trying s-off. Don't use Goo Manager to install ROMs, install manually through TWRP recovery. Once you've installed the ROM reboot to the bootloader and flash the boot.img. Here's how to flash the boot.img.
Extract the boot.img from the ROM zip and copy it into your fastboot folder on your pc. After you've flashed the ROM and/or gapps, reboot to bootloader and connect your phone, make sure it says fastboot on your phone screen. Then you can issue the following command:
Code:
fastboot flash boot boot.img
Now you can reboot your phone into the ROM.
Sent from my Evita.
Click to expand...
Click to collapse
Okay I was able to flash the boot.img but can't figure out how to flash the rom.. Should I do it through recovery? Or through a fast boot command prompt like the one used to flash the boot.img

timmaaa said:
You need to get a ROM booting brute trying s-off. Don't use Goo Manager to install ROMs, install manually through TWRP recovery. Once you've installed the ROM reboot to the bootloader and flash the boot.img. Here's how to flash the boot.img.
Extract the boot.img from the ROM zip and copy it into your fastboot folder on your pc. After you've flashed the ROM and/or gapps, reboot to bootloader and connect your phone, make sure it says fastboot on your phone screen. Then you can issue the following command:
Code:
fastboot flash boot boot.img
Now you can reboot your phone into the ROM.
Sent from my Evita.
Click to expand...
Click to collapse
This may go with out saying but when I'm in recovery and hit the reboot button and try to select "system" it comes up with a message telling me I have no OS installed and asks if I want to continue anyway..

Use the wipe menu in TWRP to do a full wipe (cache/dalvik/factory reset/system). Then use the install option to the install the ROM (and gapps if it's an aosp ROM). Then reboot to bootloader and flash the boot.img with fastboot. Then reboot your phone.
Sent from my Evita.

timmaaa said:
Use the wipe menu in TWRP to do a full wipe (cache/dalvik/factory reset/system). Then use the install option to the install the ROM (and gapps if it's an aosp ROM). Then reboot to bootloader and flash the boot.img with fastboot. Then reboot your phone.
Sent from my Evita.
Click to expand...
Click to collapse
How do i get the ROM onto my phone? that might be a stupid question but i am stumped

brenntard said:
How do i get the ROM onto my phone? that might be a stupid question but i am stumped
Click to expand...
Click to collapse
Mount your sdcard through TWRP. You should then be able to drag and drop the file from your computer to your sdcard. It should go without saying that your phone needs to be connected to your computer.
Sent from my One X using XDA Premium 4 mobile app

Black!Jack said:
Mount your sdcard through TWRP. You should then be able to drag and drop the file from your computer to your sdcard. It should go without saying that your phone needs to be connected to your computer.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i cant mount my sd card, i can put a little x by cache data and system but not sd card...

timmaaa said:
Use the wipe menu in TWRP to do a full wipe (cache/dalvik/factory reset/system). Then use the install option to the install the ROM (and gapps if it's an aosp ROM). Then reboot to bootloader and flash the boot.img with fastboot. Then reboot your phone.
Sent from my Evita.
Click to expand...
Click to collapse
i was unable to do a wipe of my phone. in twrp i went to wipe and "swipe to factory reset" it ran through and came back as failed..

Try to format your sd then (from recovery)
Gesendet von meinem Xperia Neo V mit Tapatalk 2

What ROM did you flash with Goo Manager?
You mount the sd card by going into the mount menu, then using the mount usb storage option.
Sent from my Evita.

[Q] Desire S bricked by not downgrading Hboot?

Hi all!
First of all: I know. I am a dumbass for not doing a backup. (and several other things)
Second: Thank you for your time! I really appreciate it- thats why I tried for two days to solve the problem by searching the internet for guides to restore my phone and not stealing your time.
If you just want to help me - skip the first part ("The story"). I just had to write it down, because I am that desperate and hopeless...
The story
Beside my Nexus 5 I wanted a spare phone to go outdoors and have a nice small phone - other than the huuuuuuge Nexus.
My last phones were the HTC Sensation, a Desire GSM and the Wildfire. So I decided to get a Desire S and do what I did to all my phones and tablets yet: root it.
Because I had the dumb idea that rooting a couple of phones makes me an expert I skipped the "reading guides"-part and jumped right to the "beeing an idiot"-part and downloaded the Revoked-tool.
After I got the TWRP-recovery I also skipped the "making a backup"-part and that is where my disaster began....
The problem
I tried to root my phone, but I did not reverse the Hboot. So now my phone IS NOT s-off, but I've got a working recovery installed and I can get into Fastboot and the Bootloader.
But because my partitions are wiped I can neither boot normally nore can I install a custom recovery (because of the "s-on").
My phone has got an O2-branding, so I can't install the normal Android 4.0 RUU. Neither works the O2 RUU. I suppose, because it still is the Android 2.4 - Version ( the name of the file is "RUU_Saga_O2_UK_1.31.206.1_Radio_20.28b.30.0805U_38.03.02.14_M_release_178935_signed.exe") and it does not work with my phone....
Is there any chance to get a working Desire S again?
Thabks for your time....

u have stock recover. and u have (i suppose) an unlocked bootloader.
have u tried flashing the recovery through fastboot command ?
fastboot flash recovery recovery.img
download TWRP or 4EXT touch zip file - then unpack it and copy the recovery.img inside it to fastboot or android-tools folder
open cmd there (preferably with admin rights)
and run that command.
if it is able to flash a custom recovery, then u can try to flash a rom.
u might need to check if u have a sony or hitachi screen panel though (but that should have been before u tried rooting, i think)

Hi rht_sg,
thanks for your answer!
Right. My Bootloader is unlocked.
The problem is the "S-ON" I think.
I've got a recory installed, but I can not intall any custom ROM because of the "S-ON"-Mode.
Here the important things I have foregotten in my first post:
In FASTBOOT my phone says:
"
SAGA PVT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.19.00.110
eMMC-boot
"
...and my recovery is TWRP v2.4.0.0

You can install a custom rom without being s-off, but you have to flash the boot.img (from the rom) manually in fastboot after installing the rom in recovery (fastboot flash boot boot.img).
I would recommend updating your recovery to either twrp 2.7 (from the thread in this forum) or the latest 4ext touch. One reason being that older recoveries fail when trying to flash kit-kat roms (error 7).
To update your recovery while still s-on, use fastboot (fastboot flash recovery recovery.img)

Thanks!
That solved it. - Now I could install a custom ROM again.
Now I follow your advice to flash the latest recovery.