Database Info

[Q] stuck on htc logo after installing custom rom

my desire s is unlocked and on hboot 2.00.002, i flash a custom rom. and the phone works perfectly but everytime i reboot my phone i got stuck on htc logo. but when i connect my phone to the computer and flash the boot.img it boots normally. did i do something wrong or what? please help me

I understand you corretly, that you flash boot.img and phone boots to rom? And after reboot stuck on logo?

tyrone128 said:
my desire s is unlocked and on hboot 2.00.002, i flash a custom rom. and the phone works perfectly but everytime i reboot my phone i got stuck on htc logo. but when i connect my phone to the computer and flash the boot.img it boots normally. did i do something wrong or what? please help me
Click to expand...
Click to collapse
Are you serious? It's written so often here that even the lazy guys should have gotten it.
If you unlocked via HTCdev you need to flash the boot.img of your desired ROM each time you have flashed a new ROM.
Sent by my fingers to your head.

eyahl said:
Are you serious? It's written so often here that even the lazy guys should have gotten it.
If you unlocked via HTCdev you need to flash the boot.img of your desired ROM each time you have flashed a new ROM.
Sent by my fingers to your head.
Click to expand...
Click to collapse
i know that if you are unlocked by htcdev and you install a custom rom you must flash the boot.img to boot, does it also apply on every reboot but not flashing custom rom?

Nope, not on every reboot. Just everytime you flash a new rom you need to flash the boot.img

shrome99 said:
Nope, not on every reboot. Just everytime you flash a new rom you need to flash the boot.img
Click to expand...
Click to collapse
how come everytime i reboot my phone it gets stuck on htc logo? but if i boot into fastboot and flash the boot.img it all goes well.

hmm... never heard of that issue before. What ROM are you using?

shrome99 said:
hmm... never heard of that issue before. What ROM are you using?
Click to expand...
Click to collapse
endymion, and when i restore my stock backup using ext4 recovery i also get stuck on htc white screen

I too have the same proble. Stuck at HTC logo everytime i reboot. I have to flash boot.img. I had unlocked via HTCDEV.com
I dont have this problem with CM9 ICS, but I have this problem with Primo-S-2.1, Primo-S 3.0 ICS and Saga 3D v5.1.0.
Do any one have a solution..
PROXUSER do you know why.

Very strange, unheard of before, after every reboot? did you clear dalvik and cache partition before flash of ROM?
If you HTCdev then after every nee ROM flash you must flash boot.img
Swyped from my Desire S using XDA Premium

If you restore an old nandroid backup after flashing on a new ROM do you also have to reflash boot.img separately, or does 4EXT recovery take care of that?

yes, you have to flash it

MarcovitchZA said:
If you restore an old nandroid backup after flashing on a new ROM do you also have to reflash boot.img separately, or does 4EXT recovery take care of that?
Click to expand...
Click to collapse
I'd say that 4EXT would take care of it?
draghiciandrei said:
yes, you have to flash it
Click to expand...
Click to collapse
Are you sure? surely if you restore a nandroid backup then that should contain the correctly restored boot partition and therefore you shouldn't need to reflash boot.img seperatley!?

Bobbyaju said:
I too have the same proble. Stuck at HTC logo everytime i reboot. I have to flash boot.img. I had unlocked via HTCDEV.com
I dont have this problem with CM9 ICS, but I have this problem with Primo-S-2.1, Primo-S 3.0 ICS and Saga 3D v5.1.0.
Do any one have a solution..
PROXUSER do you know why.
Click to expand...
Click to collapse
ben_pyett said:
Very strange, unheard of before, after every reboot? did you clear dalvik and cache partition before flash of ROM?
If you HTCdev then after every nee ROM flash you must flash boot.img
Swyped from my Desire S using XDA Premium
Click to expand...
Click to collapse
Every time i Format data, then clear cache, clear Dalvik and then install custom rom. Still i have to fastboot boot.img everu time i reboot my phone

Ben, what you said is correct in case of S-Off phones. But for those that are HTC unlocked, the boot partition is not writable from Recovery, and is only accessible for modification via fastboot. So for S-Off users, recovery can restore boot partition, whereas for S-On HTCDevil unlocked bootloaders, the boot.img has to to flashed manually via fastboot every single time when flashing a new ROM, or restoring a previously backed up nandroid.
Hope that explains it.

enigmaamit said:
Ben
Hope that explains it.
Click to expand...
Click to collapse
It certainly does, appreciate it, horrible HTCdev and nasty s on devices
Swyped from my Desire S using XDA Premium

Bobbyaju said:
Every time i Format data, then clear cache, clear Dalvik and then install custom rom. Still i have to fastboot boot.img every time i reboot my phone
Click to expand...
Click to collapse
enigmaamit said:
Ben, what you said is correct in case of S-Off phones. But for those that are HTC unlocked, the boot partition is not writable from Recovery, and is only accessible for modification via fastboot. So for S-Off users, recovery can restore boot partition, whereas for S-On HTCDevil unlocked bootloaders, the boot.img has to to flashed manually via fastboot every single time when flashing a new ROM, or restoring a previously backed up nandroid.
Hope that explains it.
Click to expand...
Click to collapse
Ya i got you but why do i have to fastboot boot.img every time i reboot my device in the same rom-Primos v3.0 or Saga3D5.0.1 (not while installing a new custom rom).
I dont have to fastboot boot.img everytime to reboot when iam on CM9 rom.

Bobbyaju said:
Ya i got you but why do i have to fastboot boot.img every time i reboot my device in the same rom-Primos v3.0 or Saga3D5.0.1 (not while installing a new custom rom).
I dont have to fastboot boot.img everytime to reboot when iam on CM9 rom.
Click to expand...
Click to collapse
No, you don't have to flash the boot.img everytime you simply reboot... The flashing only needs to be done when changing a ROM, as the kernel has to be matched to the ROM you are flashing. For simply rebooting, this is unnecessary.

ben_pyett said:
I'd say that 4EXT would take care of it?
Are you sure? surely if you restore a nandroid backup then that should contain the correctly restored boot partition and therefore you shouldn't need to reflash boot.img seperatley!?
Click to expand...
Click to collapse
The boot.img needs also to be flashed with fastboot after a restore.
The recovery has no permission to write to the boot partition, because of this it doesn't matter if you restore or flash a new one, but the backup contains the right boot.img, recovery can read but can't write to boot.
Gesendet von meinem Desire S mit Tapatalk

write boot.img every reboot
i have the same problem.after every simple reboot phone need to write boot.img from fastboot.
also i havnt problem with cm9

[Q] problem flashing ICS roms

I'm having problems flashing my Desire S with ICS based roms. GB roms work fine, but any ICS rom I flash gets stuck on boot on a lit up black screen. I have tried a variety of roms, flashed both on CWM and 4EXT but the issue persists. Is there some kind of special procedure for ICS roms ?

Did you
1. Wipe all partitions except SD
2. Wipe dalvik + cache
Edit : And the procedures same for flashing ics and gb roms, unless the OP specifically tells you to do otherwise

I did all possible wipes and It's still the same. Any more ideas ?

tomkow4 said:
I did all possible wipes and It's still the same. Any more ideas ?
Click to expand...
Click to collapse
did u u unlock with HTCDEV.com ? if u did just flash the boot.img inside the rom you want if u never then either the rom takes a long time to boot or your not doing the wipe properly
give me some specs of your phone

Ok, I'll run through my process. I did unlock my phone via HTCDEV, then rooted it via SuperOneClick (meaning I still have HBoot 2.00.0002 and S-ON), then flashed it by flashboot with CWM, now I have 4EXT. What I always did whas do a wipe data/factory reset and flashed. Now inspired by vodka69er I did that and clear dalvik, cache, format all but sd - and then flashed - still the same.

tomkow4 said:
Ok, I'll run through my process. I did unlock my phone via HTCDEV, then rooted it via SuperOneClick (meaning I still have HBoot 2.00.0002 and S-ON), then flashed it by flashboot with CWM, now I have 4EXT. What I always did whas do a wipe data/factory reset and flashed. Now inspired by vodka69er I did that and clear dalvik, cache, format all but sd - and then flashed - still the same.
Click to expand...
Click to collapse
If you unlocked via htcdev you need to extract the boot.img from your desired ROM. After flashing the ROM you need to flash the boot.img manually via adb. You have to do this each time you flash a new ROM.
Sent by my fingers to your head.

He's been able to flash the gb based roms , only trouble with the ics ones. That means he already knows to flash the boot img separately(unlocked with htcdev) or am I missing something

Vodka69er said:
He's been able to flash the gb based roms , only trouble with the ics ones. That means he already knows to flash the boot img separately(unlocked with htcdev) or am I missing something
Click to expand...
Click to collapse
This. Exactly. I mean I have a MIUI GB rom so, I guess it's not about flashing a rom but trouble with ICS ones. So I figured that those must have something different about them or have a specific prerequisite. Others have flashed their D S's, so I'm kind of lost.

Can you post what you see on your bootloader
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!

*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT - 2.00.0002
Radio - 3822.10.08.04_M
eMMC - boot
Aug 22 2011, 15:22:13

@op
I know that this is covering old ground, but I've not seen an actual answer
Have you ever used 'fastboot flash boot NAME.IMG' command?
Swyped from my DesireS

http://www.androidauthority.com/desire-s-root-s-off-hboot-2-00-0002-superoneclick-74470/ - this is the guide I followed.
On a side note, I did a full wipe of everything I could and still no luck with ICS roms. I think I'll leave it alone.

You still didn't answer the question that I asked in the above post, the guide that you have doesn't cater for separately flashing the boot , which is what you need to do. The guide only tells you gore to instal recovery and root
Which (as people have been saying) means that i suspect that your ICS installs have no kernels and therefore don't/can't boot
What ROM are you running now?
As after wiping all nothing should boot, unless CWM wipe all doesn't wipe boot?
Swyped from my DesireS

ben_pyett said:
You still didn't answer the question that I asked in the above post, the guide that you have doesn't cater for separately flashing the boot , which is what you need to do. The guide only tells you gore to instal recovery and root
Which (as people have been saying) means that i suspect that your ICS installs have no kernels and therefore don't/can't boot
What ROM are you running now?
As after wiping all nothing should boot, unless CWM wipe all doesn't wipe boot?
Swyped from my DesireS
Click to expand...
Click to collapse
To answer directly - I don't remeber/don't think so. But honestly didn't care much since my roms ran. Right now I'm on MIUI.
But the remark on the kernel got me thinking - I don't really know how to approach this, should I find some kernel and flash it?

On your pc you need to open the ICS ROM zip file and take out a file called boot.img
After flashing the Rom you must then use the fastboot command from your PC, as you did when you flashed your recovery.
You must then issue the command 'fastboot flash boot boot.img'
see below for the full instructions
HappyEmu said:
If you unzip your ROM's Zip-file (the one you want to flash, you'll find a file called "boot.img". Move it into the same folder as your adb and fastboot executables (Android SDK) and flash it using fastboot.
To be a little more specific:
1. Extract boot.img from ICS rom zip file and move it in the same folder as your fastboot.exe (Android SDK) on your PC
2. Flash the ICS Rom as usual from recovery (don't forget to first perform the full wipe/format including the boot partition)
3. Boot into fastboot mode, connect your phone to your PC and flash boot.img using fastboot
Code:
fastboot flash boot $pathToYourBootIMG\boot.img
4. Reboot
Click to expand...
Click to collapse
Swyped from my DesireS

Your GB room worked as they were running on the stock kernel
ICS won't work this way.
As Ben has mentioned you need to flash the boot.img
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!

eyahl said:
If you unlocked via htcdev you need to extract the boot.img from your desired ROM. After flashing the ROM you need to flash the boot.img manually via adb. You have to do this each time you flash a new ROM.
Sent by my fingers to your head.
Click to expand...
Click to collapse
*Bump*
Sent by my fingers to your head.

suku_patel_22 said:
Your GB room worked as they were running on the stock kernel
ICS won't work this way.
As Ben has mentioned you need to flash the boot.img
Click to expand...
Click to collapse
4EXT seems to flash the kernel upon installation of specific roms, but I still did it manually and ... nothing. It still goes into a coma upon boot. Maybe I'll do a video of what I'm doing when I get back from work, cause now I'm having problems with some other roms - they freeze on bootscreen. Maybe it has something to do with my phone being S-ON?

tomkow4 said:
4EXT seems to flash the kernel upon installation of specific roms, but I still did it manually and ... nothing. It still goes into a coma upon boot. Maybe I'll do a video of what I'm doing when I get back from work, cause now I'm having problems with some other roms - they freeze on bootscreen. Maybe it has something to do with my phone being S-ON?
Click to expand...
Click to collapse
I suspect that you're suffering the problem on other ROMS now as you're wiping the boot partition and therefore have no kernel.
[Q] How long do you wait on boot? you must be patient as first boot can take a while (although not longer than 10minutes).
A video would be a great way of showing the problem...Try to capture everything....
Your bootloader screen....
All the partition wipes
The Rom flash
The fastboot boot.img flash
and then what happens after...

Kind of noobish on my end, but as I was making the video - and did everything according to protocol just as earlier - it worked . I flashed BlackICE 5.5. Christ. Thanks anyway for the patience guys (I assume )

[S4] Flashing from CM10 to TrickDroid 7.1 does not work

Hey Guys,
yesterday I wanted to revert my ROM from CM10 to TrickDroid 7.1. In TWRP 2.2.1 I wiped caches and did a factory reset and then flashed TD 7.1 following torxx's instructions (wipe, install ROM, flash boot.img with his boot flash script, let the ROM boot). After the reboot the phone hang. The startup sound came through but then no further action for about 7 Minutes.
Was that too little time waiting? Or is there any other issue interfering the boot process after reverting from Android 4.1.1 to 4.0.4 Sense?
If anyone can help is much appreciated. Even if I look stupid afterwords
Burkhard

herzbert said:
Hey Guys,
yesterday I wanted to revert my ROM from CM10 to TrickDroid 7.1. In TWRP 2.2.1 I wiped caches and did a factory reset and then flashed TD 7.1 following torxx's instructions (wipe, install ROM, flash boot.img with his boot flash script, let the ROM boot). After the reboot the phone hang. The startup sound came through but then no further action for about 7 Minutes.
Was that too little time waiting? Or is there any other issue interfering the boot process after reverting from Android 4.1.1 to 4.0.4 Sense?
If anyone can help is much appreciated. Even if I look stupid afterwords
Burkhard
Click to expand...
Click to collapse
Perhaps your hboot does not allow flashing or boot.img? Have you tried the fastboot method of flashing boot.img? How about reverting to a nandroid of a sense based ROM, then flashing TD?

el_smurfo said:
Perhaps your hboot does not allow flashing or boot.img? Have you tried the fastboot method of flashing boot.img? How about reverting to a nandroid of a sense based ROM, then flashing TD?
Click to expand...
Click to collapse
Prior to CM10 I was on latest stock ROM. Before that I had custom ROMs. HBoot on my phone after the OTA update is 1.14. Flashing the boot image of CM10 was no problem.
In order to use the phone I reinstalled CM10 and it works.
The boot images were flashed within fastboot. I do not know any other way to flash a boot image.
I dont have a nandroid backup.

Checked MD5?

torxx said:
Checked MD5?
Click to expand...
Click to collapse
They correspond.
If nothing else helps I will try to install the latest RUU and then flash a ROM. But I wanna circumvent the relock and unlock procedure.
Btw: Did anybody notice that the unlock code changes after an update of HBoot? Nobody mentioned that when the new base was released.

Same here... But fine now
herzbert said:
They correspond.
If nothing else helps I will try to install the latest RUU and then flash a ROM. But I wanna circumvent the relock and unlock procedure.
Btw: Did anybody notice that the unlock code changes after an update of HBoot? Nobody mentioned that when the new base was released.
Click to expand...
Click to collapse
Hey there,
I was having the same problems as you messioned. I flashed the boot.img through fastboot myself and some how it then worked Did not have an problems with flashing the boot.img before. But maybe its worth a try.

Of course you need to use fastboot!!

Did not try yet to flash the RUU. There was an update of CM10 yesterday. The heavy battery drain is gone with this update and there is no urgent need to go back to TrickDroid right now.

herzbert said:
Prior to CM10 I was on latest stock ROM. Before that I had custom ROMs. HBoot on my phone after the OTA update is 1.14. Flashing the boot image of CM10 was no problem.
In order to use the phone I reinstalled CM10 and it works.
The boot images were flashed within fastboot. I do not know any other way to flash a boot image.
I dont have a nandroid backup.
Click to expand...
Click to collapse
HBoot 1.14 is the problem. Anything above 1.09 needs special steps to flash unlike simply flashing with twrp as with 1.09 and below.
Sent from my HTC VLE_U using Xparent SkyBlue Tapatalk 2

LikeaG2root said:
HBoot 1.14 is the problem. Anything above 1.09 needs special steps to flash unlike simply flashing with twrp as with 1.09 and below.
Alright, so, what are these special steps? Can you tell? If its not flashing the within recovery and push the boot.img via fastboot to the phone I would be very interested. My previous HBoot version was 1.13. Flashing ROMs was never a big deal. Also not going to CM9 and back to sense based ROMs.
Click to expand...
Click to collapse

I am on hboot 1.14 and it worked via fastboot. Like you mentioned yourself you reinstalled CM10 and it booted, therefore your previous flash of the boot.img didn't work. So just flash the boot.img via bootloader and fastboot and you should be good...

HighRoIIer said:
I am on hboot 1.14 and it worked via fastboot. Like you mentioned yourself you reinstalled CM10 and it booted, therefore your previous flash of the boot.img didn't work. So just flash the boot.img via bootloader and fastboot and you should be good...
Click to expand...
Click to collapse
I did also flash the boot.img via fastboot. Why do you say that anyway? Is there another method to flash a boot.img?

you didn't mention wiping System as part of the full wipe--needs done

Partially solved
rugmankc said:
you didn't mention wiping System as part of the full wipe--needs done
Click to expand...
Click to collapse
Right, I did not mention it because system is wiped by TWRP during flashing the ROM. So there was no need to wipe it seperately. But maybe my mistake was not to wipe data and the new "asec" folder messed things up.
I'll never know because yesterday I did a complete wipe including the SDCard. Afterwards I was able to install TrickDroid flawlessly.
Thank you all for your efforts.

[Q] Some problem with custom rom BricK BeaTZ.

Hi everyone here.
I am a user of ATT HOX, after I rooted it I downloaded BricK BeaTs rom and use twrp 2.3.10 to flash the rom and gapps
After I compeleted the steps and rebooted it, it got stop with the boot scene...
I try to just install the rom, and it can work...
Who can tell me how can I install the gapps?
What is the correct way to install the rom and gapps?

Did you flash boot.img in fastboot before flashing the rom like the 100 threads here with your same problem say to do?

did you flash boot.img in fastboot?

That's the golden question nowadays lol

lucentworld said:
Hi everyone here.
I am a user of ATT HOX, after I rooted it I downloaded BricK BeaTs rom and use twrp 2.3.10 to flash the rom and gapps
After I compeleted the steps and rebooted it, it got stop with the boot scene...
I try to just install the rom, and it can work...
Who can tell me how can I install the gapps?
What is the correct way to install the rom and gapps?
Click to expand...
Click to collapse
First do a full wipe, format System and Factory Reset from inside of recovery
Extract the boot.img from the ROM, and put it in the same folder as fastboot.exe
in command prompt, navigate to where fastboot is (e.g.) cd "C:\android" and then type fastboot flash boot boot.img
If you get stuck at waiting for device, reboot your phone into the boot loader and click 'fastboot' from inside of the boot loader this takes place on your phone. Then try fastboot flash boot boot.img again.
Once that succeeds, flash the ROM, flash GAPPS and reboot.

lucentworld said:
Hi everyone here.
I am a user of ATT HOX, after I rooted it I downloaded BricK BeaTs rom and use twrp 2.3.10 to flash the rom and gapps
After I compeleted the steps and rebooted it, it got stop with the boot scene...
I try to just install the rom, and it can work...
Who can tell me how can I install the gapps?
What is the correct way to install the rom and gapps?
Click to expand...
Click to collapse
one more time to make sure: did you flash boot.img in fastboot?

Soft Bricked One-X

Hi I unlocked my bootloader and flashed TWRP recovery, factory reset and wiped cache, and then proceeded to flash CM10 latest nightly. My phone is now stuck in bootloop, I have tried reflashing CM10 and another rom and still bootlooping. Has anyone else had this problem? How can I get a rom to successfully flash or return to stock? Thank you for your help

Crazed47 said:
Hi I unlocked my bootloader and flashed TWRP recovery, factory reset and wiped cache, and then proceeded to flash CM10 latest nightly. My phone is now stuck in bootloop, I have tried reflashing CM10 and another rom and still bootlooping. Has anyone else had this problem? How can I get a rom to successfully flash or return to stock? Thank you for your help
Click to expand...
Click to collapse
First off, Do you have to US version, or the international version? Also, what's your hboot version?
If you have to international, wrong place to be.
If you have the US, with hboot 1.14, you have to flash the boot.img through fastboot. Then install the .zip from recovery.

US version and hboot 1.14.0002

Crazed47 said:
US version and hboot 1.14.0002
Click to expand...
Click to collapse
open the .zip for CM10, extract the boot.img. put it in the folder where fastboot is. Copy the .zip for CM10 to your sd card. flash the boot.img from fastboot. go into TWRP and install the .zip. You should be fine.
You might note that CM10 is a recent release so it's still a little buggy. If you don't get past the counter clockwise rotating boot screen. DONT PANIC. Just try flashing another rom, the same way i told you too.

Myrder said:
open the .zip for CM10, extract the boot.img. put it in the folder where fastboot is. Copy the .zip for CM10 to your sd card. flash the boot.img from fastboot. go into TWRP and install the .zip. You should be fine.
You might note that CM10 is a recent release so it's still a little buggy. If you don't get past the counter clockwise rotating boot screen. DONT PANIC. Just try flashing another rom, the same way i told you too.
Click to expand...
Click to collapse
thank you problem solved!

Glad I could help.