Database Info

[Q] Phone can't boot after kernel flash

Hello,
So I have a rooted HTC Desire S with Hboot 2.00.0002, unlocked bootloader and 4ext touch recovery. After a couple of failed attempts of flashing the MIUI rom and nandroid restoring it, I lost the ability to connect to 3G after the fourth attempt. So, I tried to flash a new kernel on it to see if it would solve anything. It didn't, whenever I boot up my phone it hangs on the HTC logo, then reboots a little while in 4ext recovery mode.
From here I again tried to nandroid restore, but with no luck.
How do I get my phone back to working? (what I had before was rooted stock rom)
I have tried these two kernels: http://bit.ly/ozxbWr (HTC-Kernel-2.6.35.10) and the Reaper 3.0 kernel (http://forum.xda-developers.com/showthread.php?t=1433816).
Thanks.

Alright, found the problem. For future Googlers here is how I fixed it.
So, first I downloaded a custom rom for my phone, MIUI. I placed the zip on my micro-SD card (I have a converter so it will fit into my laptop) and booted into 4EXT recovery. I guess you can use ClockworkMod Recorvery aswell.
In here I picked "choose from SD-card" and picked my .zip file and installed it.
After installation you boot into the bootloader (Volume Down + Power button) and go into fastboot. While in fastboot you plugin your USB-cable.
Set up ADB and Fastboot with this guide http://forum.xda-developers.com/showthread.php?t=1272595
Now go back to where you downloaded the custom rom to and extract the boot.img file to the folder where adb.exe and fastboot.exe is.
Upon up a cmd in your folder where adb.exe and fastboot.exe is in (Use Shift+Right click, pick "Open cmd here").
Now write exactly the following
Code:
fastboot flash boot boot.img
.
Press Enter and let it do it's job. When it's done you can unplug the USB cable and restart the phone as normally. The phone will now function again.

Did you unlock your phone with HTCDEV? If so then it is extremely well documented that you have to flash to kernel separately.

SimonTS said:
Did you unlock your phone with HTCDEV? If so then it is extremely well documented that you have to flash to kernel separately.
Click to expand...
Click to collapse
And even more so now
Impressed that someone actually resolved their own issue, let this hopefully be a lesson to the crowd
Swyped from my DesireS

The guide for doing this is here: http://forum.xda-developers.com/showthread.php?t=1525100

Thread closed

HTC Desire S issue

Hello all,
A friend has a HTC Desire S. He tried to install some stuff on it like new rom, HBOOT, etc. Now the phone can boot only with power and VOL DOWN. I can enter also in recovery but from there I can't install new rom to boot in it. Also HBOOT is ver. 2.00.xx not sure the last digits and there is S-ON also.
Any idea how can I fix it?
Thank you in advance.

Is the recovery CWM or 4EXT? What happens when you try to install a new rom?

If you're S-ON you have to flash the boot.img with fastboot after flashing your ROM :
Code:
fastboot flash boot boot.img
Extract it from your ROM zip and put it in the platform-tools folder of the SDK. Go in this folder then Shift+Left click --> open prompt command here
Then write the code above. Of course you need to plug the phone in fastboot mode before doing that :silly:

Hello,
thanks for the answers. I was able to handle this. Mainly the issue was that Windows 8 won't detect the phone at all. I have other computer with Win7 and I made the all the needed there.
Here is what I have used: http://forum.xda-developers.com/showthread.php?t=1525100
Now everything is working.
Thank you all.

Bootloop (S-ON/No Recovery) :(

Hello,
I have a big problem with my old HTC Sensation.
I tried nearly everything out of other topics, but nothing worked....
The story: Suddenly my Sensation rebooted and from then on it is stuck in an endless bootloop.
The bad thing is, that it was stock/S-ON at this moment.
Informations about the phone:
***UNLOCKED***
Pyramid PVT Ship S-ON RL
HBOOT: 1.27.0000
Radio: 11.24A.3504.31_M
-> I am able to install RUUs (3.33), but after installation i am still in the bootloop
-> I am able to unlock/relock the bootloader
-> I can install a recovery via fastboot, but can't boot into it => bootloop
Maybe you have got a hint to bring the Sensation back to life.
Thank you!

Since your bootloader is unlocked, you can use fastboot to do stuff. Most of the HTC Sensations have a HBOOT version that causes bootloops when flashing roms because their kernel doesn't seem to install properly when flashing roms. The ROM should consist of a file inside the zip, usualy in the kernel folder or in the root of the zip that is called boot.img. That is the kernel. First of all, you need to download the tools that have the fastboot and drivers included. Then unzip all of the contents into a folder. Run and install the drivers that that have come in the folder. Then go into the fastboot and adb folder. Shift rightclick onto the empty space of the folder and click open command window here. Then boot your phone into bootloader mode. You can do this using power button and volume down while your phone is off. Once youre in fastboot mode, navigate to fastboot using up and down volume keys. Then press the power button. Plug in your phone to your computer using your HTC sync cable. Then in the adb and fastboot folder, copy your roms boot.img into the folder. Then in the command window, type 'fastboot flash boot boot.img' without the quotation marks. It should say sending and then writing. The process should take no longer than 20 seconds. Once done, restart your phone. Wolla, your rom should now be working properly!

kevinspl2000 said:
Since your bootloader is unlocked, you can use fastboot to do stuff. Most of the HTC Sensations have a HBOOT version that causes bootloops when flashing roms because their kernel doesn't seem to install properly when flashing roms. The ROM should consist of a file inside the zip, usualy in the kernel folder or in the root of the zip that is called boot.img. That is the kernel. First of all, you need to download the tools that have the fastboot and drivers included. Then unzip all of the contents into a folder. Run and install the drivers that that have come in the folder. Then go into the fastboot and adb folder. Shift rightclick onto the empty space of the folder and click open command window here. Then boot your phone into bootloader mode. You can do this using power button and volume down while your phone is off. Once youre in fastboot mode, navigate to fastboot using up and down volume keys. Then press the power button. Plug in your phone to your computer using your HTC sync cable. Then in the adb and fastboot folder, copy your roms boot.img into the folder. Then in the command window, type 'fastboot flash boot boot.img' without the quotation marks. It should say sending and then writing. The process should take no longer than 20 seconds. Once done, restart your phone. Wolla, your rom should now be working properly!
Click to expand...
Click to collapse
actually he can't even boot to the recovery in order to flash any rom
so what's the point of flashing the boot.img manually?

You can use Sensation all in one kit v3 to unlock boot loader, read this thread for more detail
http://forum.xda-developers.com/showthread.php?t=1497404
after unlocking boot loader, then go to this thread to download 4EXT recovery then use kit to flash recovery, remember to download image file, not zip file
http://forum.xda-developers.com/showthread.php?t=1377759
boot to recovery, then enable smart flash and flash any cook ROM you want. Remenber to wipe everything after having enable smart flash then flash cook ROM
good luck

stripeqn said:
Remenber to wipe everything after having enable smart flash then flash cook ROM
good luck
Click to expand...
Click to collapse
actually first has to wipe and then enable smartflash

Thank you for your ideas!
But unfortunattly i tried most of the things.
@ kevinspl2000
I think normaly the RUU would also install the Boot Image.
But I also tried to manualy flash the boot.img out of the RUU via fastboot, but no success.
I am not able to flash a Custom ROM, because of no Recovery...
@stripeqn
The point is that I am not able to boot to Recovery...
I can flash the Recovery via fastboot, but I am not able to boot into it.
I tried different versions of CWMR and 4EXT but no success...
When I click on recovery, it just shows the HTC Logo and bootloop again

BrainyTheKing said:
Thank you for your ideas!
But unfortunattly i tried most of the things.
@ kevinspl2000
I think normaly the RUU would also install the Boot Image.
But I also tried to manualy flash the boot.img out of the RUU via fastboot, but no success.
I am not able to flash a Custom ROM, because of no Recovery...
@stripeqn
The point is that I am not able to boot to Recovery...
I can flash the Recovery via fastboot, but I am not able to boot into it.
I tried different versions of CWMR and 4EXT but no success...
When I click on recovery, it just shows the HTC Logo and bootloop again
Click to expand...
Click to collapse
I think I have a solution. When I installed my custom recovery at first, I also got bootloops when trying to go into the recovery. What I did, is I refalshed the recovery, and then did fastboot erase cache. It wipes all of the cache, and fixed my bootloop before. Try that and see how we get on...

kevinspl2000 said:
I think I have a solution. When I installed my custom recovery at first, I also got bootloops when trying to go into the recovery. What I did, is I refalshed the recovery, and then did fastboot erase cache. It wipes all of the cache, and fixed my bootloop before. Try that and see how we get on...
Click to expand...
Click to collapse
I erased the cache before and after flashing recovery.
No success ...

[Q] Boot loop after failed boot.img replacement

Edit: solution to the problem in post #4
I have accidentally replaced my boot.img with fastboot - now the phone is stuck in a boot loop/freeze
the bootloader is unlocked
it is S-ON
it is an unlocked (not branded phone)
running twrp 2.6.0.0
both adb and fastboot appear to work
the phone is not rooted (that was where the problem started...)
I have access to hboot and recovery, but that is it​
I have erased everything (cache, system, dalvik, sd) several times and tried a number of suggestions found on other threads describing similar problems.
I can't get access to the SD card from a PC, and fastboot flash or adb push both fail to transfer a stock RUU (JmzM4StockRootedDeOdex-WWE-1.22.401.1.zip) to the phone.
I have replace the kernel (and flashed the appropriate boot.img with it) to get out of the boot loop.
Any suggestion would be greatly appreciated! gettting desperate now...
Thanks, K
----------
the recovery screen reads:
***TAMPERED***
***UNLOCKED***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.22.40e.00.07
OpenDSP-v15.2.0268.0819
OS-1.40.401.1
eMMC-boot 1024MB

ilchkai said:
I have accidentally replaced my boot.img with fastboot - now the phone is stuck in a boot loop/freeze
the bootloader is unlocked
it is S-ON
it is an unlocked (not branded phone)
running twrp 2.6.0.0
both adb and fastboot appear to work
the phone is not rooted (that was where the problem started...)
I have access to hboot and recovery, but that is it​
I have erased everything (cache, system, dalvik, sd) several times and tried a number of suggestions found on other threads describing similar problems.
I can't get access to the SD card from a PC, and fastboot flash or adb push both fail to transfer a stock RUU (JmzM4StockRootedDeOdex-WWE-1.22.401.1.zip) to the phone.
I have replace the kernel (and flashed the appropriate boot.img with it) to get out of the boot loop.
Any suggestion would be greatly appreciated! gettting desperate now...
Thanks, K
----------
the recovery screen reads:
***TAMPERED***
***UNLOCKED***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.22.40e.00.07
OpenDSP-v15.2.0268.0819
OS-1.40.401.1
eMMC-boot 1024MB
Click to expand...
Click to collapse
Hi! If you still need help, PM me and we'll get it sorted, no problem.....

nelvinchi said:
Hi! If you still need help, PM me and we'll get it sorted, no problem.....
Click to expand...
Click to collapse
excellent - thanks, pm sent

Here is the solution to the above problem, no guarantees – just thought I share it here if anyone else is in the same predicament… I was walked through this by nelvinchi - many thanks for that !!!!
(n.b. I can't post urls yet as I am a noobie here, so that you will need to find the required files in the forum somewhere - maybe someone can leave links to the appropriate files in a post below)
Required files:
1. ABD (get the smaller version from the forum)
-> download this and extract to a folder called c:\adb\
2. Updated Super SU "UPDATE-SuperSU-v1.86.zip"
3. Rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
-> SuperSU and Rom, into the same folder as above (c:\adb\)
(4. TeamWinRecoveryProject recovery, here version 2.6.0.0)​
Procedure:
[NB.: I had access to bootloader (unlocked) & recovery (twrp 2.6.0.0); the phone was S-ON]
Open a command prompt from the folder (shift+right click somewhere in the window and choose “open command window here”, or WIN+R and enter cmd and press enter and navigate to the folder where the files and adb are located)
Boot phone to recovery
Go to the mount menu, check system and data [data was not selectable, thus I had to: Go to wipe menu, Format data, Type yes, after that reboot to recovery, and mount menu, check system and data…]
Back to main menu
Plug your phone into computer (mine was plugged in all along, so no worries)
In the cmd prompt (on PC) type: adb devices [phone should be found and indicated by the serial number and the status, in this case it should say recovery after the number – proceed if phone is found]
Type: adb push Stock2.12.401.1Deodex(tr1gg3r84).zip /sdcard/
[there is no indication of progress when pushing, just be patient – it will take a few minutes. And, just in case – if you need to interrupt/cancel the push process it can be done with Ctrl+c]
Type: adb push UPDATE-SuperSU-v1.86.zip /sdcard/
On the phone, in recovery, Go to install
Choose the NEW rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
Choose add more zips and add the SuperSU zip
Confirm flash
When done, DON'T reboot, go back, reboot menu, reboot recovery
On the PC, open the ROM zip, and extract boot.img to the folder (c:\adb\) [this will need you to have 7zip or Winrar or similar installed on your computer]
Reboot menu and select Reboot bootloader
Select fastboot (fastboot should be indicated by fastboot USB)
On the PC type fastboot flash boot boot.img
Choose bootloader, then recovery
In recovery: Go to wipe, Advanced wipe, Check cache and dalvik, and wipe!
Go to Reboot menu, and Reboot system
Now, don't panic – it will take some time to do its thing… the phone should be fine after that and normal setup process should start.
!!! Massive thanks to nelvinchi, who walked me through this process!!!

Links
A little late, but:
SuperSU: http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip?retrieve_file=1
Stock Flashable zip: https://mega.co.nz/#!8d0jhQTS!N2V5KTty4spxzNOwU-43vzqd3BF_ektVbH_TuHec26c
TWRP: http://forum.xda-developers.com/showthread.php?t=2418938
ADB: http://forum.xda-developers.com/showthread.php?p=42407269 (i think you ment this one, right?)
Yaaay, fixed my mini. Thx for these instructions!
:laugh:

ilchkai said:
Here is the solution to the above problem, no guarantees – just thought I share it here if anyone else is in the same predicament… I was walked through this by nelvinchi - many thanks for that !!!!
(n.b. I can't post urls yet as I am a noobie here, so that you will need to find the required files in the forum somewhere - maybe someone can leave links to the appropriate files in a post below)
Required files:
1. ABD (get the smaller version from the forum)
-> download this and extract to a folder called c:\adb\
2. Updated Super SU "UPDATE-SuperSU-v1.86.zip"
3. Rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
-> SuperSU and Rom, into the same folder as above (c:\adb\)
(4. TeamWinRecoveryProject recovery, here version 2.6.0.0)​
Procedure:
[NB.: I had access to bootloader (unlocked) & recovery (twrp 2.6.0.0); the phone was S-ON]
Open a command prompt from the folder (shift+right click somewhere in the window and choose “open command window here”, or WIN+R and enter cmd and press enter and navigate to the folder where the files and adb are located)
Boot phone to recovery
Go to the mount menu, check system and data [data was not selectable, thus I had to: Go to wipe menu, Format data, Type yes, after that reboot to recovery, and mount menu, check system and data…]
Back to main menu
Plug your phone into computer (mine was plugged in all along, so no worries)
In the cmd prompt (on PC) type: adb devices [phone should be found and indicated by the serial number and the status, in this case it should say recovery after the number – proceed if phone is found]
Type: adb push Stock2.12.401.1Deodex(tr1gg3r84).zip /sdcard/
[there is no indication of progress when pushing, just be patient – it will take a few minutes. And, just in case – if you need to interrupt/cancel the push process it can be done with Ctrl+c]
Type: adb push UPDATE-SuperSU-v1.86.zip /sdcard/
On the phone, in recovery, Go to install
Choose the NEW rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
Choose add more zips and add the SuperSU zip
Confirm flash
When done, DON'T reboot, go back, reboot menu, reboot recovery
On the PC, open the ROM zip, and extract boot.img to the folder (c:\adb\) [this will need you to have 7zip or Winrar or similar installed on your computer]
Reboot menu and select Reboot bootloader
Select fastboot (fastboot should be indicated by fastboot USB)
On the PC type fastboot flash boot boot.img
Choose bootloader, then recovery
In recovery: Go to wipe, Advanced wipe, Check cache and dalvik, and wipe!
Go to Reboot menu, and Reboot system
Now, don't panic – it will take some time to do its thing… the phone should be fine after that and normal setup process should start.
!!! Massive thanks to nelvinchi, who walked me through this process!!!
Click to expand...
Click to collapse
I followed these instrutions to a T but im still getting boot loopat the HTC screen
I am Unlocked bootloader
S-Off
cid-CWS__001
hboot 2.19.0000
radio 1.19.40d.00.14
any suggestion?

please help
romy134 said:
I followed these instrutions to a T but im still getting boot loopat the HTC screen
I am Unlocked bootloader
S-Off
cid-CWS__001
hboot 2.19.0000
radio 1.19.40d.00.14
any suggestion?
Click to expand...
Click to collapse
I'm having the same problem.
I've followed those instructions over and over with different roms but TWRP always tells me that there is no OS installed when I do the final reboot. I am stuck at the white HTC screen and can't get any rom to load up. Please help.
This is what my bootloader says:
--TAMPERED--
--UNLOCKED--
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.25.40G.00.19
OPENDSP-V19.2.0268.0927
OS-3.10.502.3
eMMC-boot 1024mb
I can flash recoveries and boot.img. ADB works to push roms into /sdcard/, can also sideload. I'm suspecting my filesystem/ partition data is all screwed but but can't figure out why Roms won't load.
I got the phone yesterday and it was untouched, stock. I tried to follow this guide (http://forum.xda-developers.com/showthread.php?t=2789272) to get it rooted and install a custom rom. I got stuck at getting S-OFF. rumrunner was giving me the "Fatal: download latest package" error. I also could not get su in the shell to try firewater. At this point I was reading that people had luck getting S-OFF after installing JmzM4StockRootedOdex-WWE-1.22.401.1 custom rom and kernel. I tried to do that but I wasn't sure what I was doing and ended up with no OS and a bootloop at the white HTC screen. I have a bit of Android experience from messing with the HP touchpad tablet but I'm rusty and this phone has me beat right now.
Thanks for your help.

...
try replacing TWRP with an older version (mine was 2.6.0.0) and reset/clear/delete/format everything from there and restart the process outlined above
and apparently S-Off is pointless and very risky on this model, there is no reason to do it - it will just cause problems
good luck and I hope some else who has actual knowledge about this will get back to you

ilchkai said:
try replacing TWRP with an older version (mine was 2.6.0.0) and reset/clear/delete/format everything from there and restart the process outlined above
and apparently S-Off is pointless and very risky on this model, there is no reason to do it - it will just cause problems
good luck and I hope some else who has actual knowledge about this will get back to you
Click to expand...
Click to collapse
Thanks.. I've been using TWRP 2.7.1.0 because I read that I have the newer partion scheme with HBOOT 2.22 but I'm not really sure.
When I try TWRP 2.7.1.1 ADB doesn't work and I get a different /sdcard/ than in 2.7.1.0. Not sure what's going on there either.
The only reason I tried S-off is because I blindly followed that guide on how to get the HTC one mini up to date and that was the 2nd step. I should have skipped it and paid more attention to the custom rom flashing aspect.
I'll try TWRP 2.6.0.0 as I don't have many other options at this point.. I also tried to use CWM recovery but it couldnt flash a rom either.
Thanks for your input.

Can't access recovery

A friend has given me his Desire S to fix what I originally thought was just a stuck power button that prevented it from starting up. But the button is now fixes and I've been trying the last few days to get it to start up.
What I have tried so far is to enter Recovery mode, but upon choosing it, the phone would just go to the HTC logo screen, fibrate once and then fibrate agian after a second or two for a few times and the screen would go blank. The same happens with normal bootup. It also seems that the phone is still running with the blank screen because I have to pull the battery to startup again.
I then tried to use the latest RUU (Android 4.0) from HTC but the phone is not recognized by the computer (I think it is because it didn't startup enough to be able to present itself to the computer). So I unlocked it and used fastboot (from Ubuntu as OS) to flash the recovery (recovery_signed.img) and boot (boot_signed.img) from the RUU. With this recovery and normal startup would remain at the HTC screen and wouldn't go blank as before - still fibrates a few times.
I also tried to rename the rom.zip to PG88IMG.zip and putting it on a SD and the bootloader does detect it, but presents the normal boot screen afterwards (I think it complains about it being incorrect - the display is too quick for me to see the error).
Now I also have a Desire S and made a backup of it before I installed a custom ROM. So I also tried the recovery.img that I have from this backup, but then recovery is stuck on the blank screen again.
Is there anything that I did wrong, missed or may not have tried yet? And how can I go about to fix it?
PHONE DETAILS (from bootloader screen)
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot

The PG88IMG wont work coz ur s-on. Ul need to extract the zip file and put the recovery.img in ur fastboot folder and then flash it from fastboot, volume down + power then select select fastboot then plug ur phone into pc and open a fastboot command window and type
fastboot flash recovery recovery.img
Also a ruu u run from fastboot and u need to relock ur bootloader.
(i dunno how all this is done using ubuntu but thats how on windows so im sure ul know or figure it out)

Ok, didn't know that I needed S-OFF for PG88IMG - thanks for pointing that out . I did flash the recovery (paragraph 3), it is just named `recovery_signed.img` and not 'recovery.img` - I assume that there isn't a difference between the two?
Do I open the RUU while in fastboot on the phone (after relocking) or do I run it from a fastboot command?
(On Ubuntu fastboot is installed as a program so I can call it after I CD to the extracted rom folder and I assume it is working since I didn't get any errors)

Pieter2627 said:
Ok, didn't know that I needed S-OFF for PG88IMG - thanks for pointing that out . I did flash the recovery (paragraph 3), it is just named `recovery_signed.img` and not 'recovery.img` - I assume that there isn't a difference between the two?
Click to expand...
Click to collapse
Well it depends, could be 4ext recovery, CWM, or TWRP. But as far as the name, could be called peterpan.img and it wouldnt matter haha
Pieter2627 said:
Do I open the RUU while in fastboot on the phone (after relocking) or do I run it from a fastboot command?
Click to expand...
Click to collapse
Yh boot ur phone into fastboot, connect it to pc, relock bootloader and then run ruu. The ruu should be exe file so just double click it to run.

Ok, relocked it and went into fastboot mode and then opened the RUU, but was not recognized. Then followed this (droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/) since I used Win 8.1 for the RUU and it flashed successfully.
But it is still stuck on the HTC screen - gave it 30 minutes for the first boot after flash. Recovery is also still stuck, so I reflashed and same issue.
Radio is now 3831.19.00.110