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

Recovery after firmware upgrade?

okay my friend told me that i need to install a custom recovery after i flash a new firmware. but everything i am reading about 3.32 says that i only need to flash new firmware. delete the img file off root and flash new rom. Is the custom recovery already unlocked? am i going to need to use ADB to install the new rom or 4ext? thanks for your feed back
I am S off
Rooted
I have super CID
and i am currently on 3.24 firmware

MacTheRipperr said:
okay my friend told me that i need to install a custom recovery after i flash a new firmware. but everything i am reading about 3.32 says that i only need to flash new firmware. delete the img file off root and flash new rom. Is the custom recovery already unlocked? am i going to need to use ADB to install the new rom or 4ext? thanks for your feed back
I am S off
Rooted
I have super CID
and i am currently on 3.24 firmware
Click to expand...
Click to collapse
Do you have 4ext recovery already installed ???

yeah i already have 4 ext installed right now. but i don't know if i am going to have to reinstall it after i flash 3.32 am i going to have to use ADB? or am i good just flashing firmware and then flashing rom like regular?

MacTheRipperr said:
yeah i already have 4 ext installed right now. but i don't know if i am going to have to reinstall it after i flash 3.32 am i going to have to use ADB? or am i good just flashing firmware and then flashing rom like regular?
Click to expand...
Click to collapse
You will not have to flash a new recovery after flashing the new firmware Mac... but I do think that when you go the flash a new custom rom from here I would wipe the phone (ie) super wipe or use the builtin one in 4ext under (wipe and format) use wipe everything but SDcard.....

Thank you for the help and patience. Much abliged.

MacTheRipperr said:
Thank you for the help and patience. Much abliged.
Click to expand...
Click to collapse
no problem, just one thing, if you have super wipe only use it with sense roms not AOSP roms, and if you are using any of the new sense 4 roms like OrDroid or Insertcoin that is builtin the rom when you install too, just read everything very carefully because of the installer (ie) Aroma installler.....

[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.

[HOW-TO] Revert to Stock ROM JB for user with new HBOOT

Hi to All,
I want to share my experience about revert to stock for users that have new HBOOT, unlocked bootloader and custom recovery; can't execute official RUU. ( This method i think is more safe that downgrade HBOOT )
Step ONE:
Install this custom ROM: MaximuS ROM ( read the thread for instruction about installation of this ROM )
( this ROM allow you to receive the message of OTA JB update, if you know another ROM that receive this message you can use as well i think )
Step TWO:
install the stock recovery of HTC One S via fastboot ( after flashing recovery erase cache )
Step THREE:
Reboot your phone in system, configure the rom for first use, go to settings, information, software update and press check now for update.
You'll receive the message for an update, download and install, and now you have stock JB ROM. after reboot you can do a reset ( go to setting => backup and restore ) to clean the application migrated from previous ROM ( MaximuS )
I hope this can help someone else.
p.s. Sorry for my English!

Thanks bro for this, but my problem is not resolved because this rom couldn't install on my HTC One S, i dont know why... Log show me: MD5 files not found

CybulPL said:
Thanks bro for this, but my problem is not resolved because this rom couldn't install on my HTC One S, i dont know why... Log show me: MD5 files not found
Click to expand...
Click to collapse
Witch recovery are you using at the moment? I installed this ROM ( MaximuS ) with Team Win Recovery ( TWRP ) v2.3.3.0 and it's works for me.
( after flashing ROM from recovery remember to flash boot.img by fastboot )

Maverick87Shaka said:
Witch recovery are you using at the moment? I installed this ROM ( MaximuS ) with Team Win Recovery ( TWRP ) v2.3.3.0 and it's works for me.
( after flashing ROM from recovery remember to flash boot.img by fastboot )
Click to expand...
Click to collapse
I use TWRP and CWM and the same. My mate told me that i have unmount 1 and 2 partition in recovery but i don't know how.

Hi everyone,
thanks a lot, this saved my ass ... I had upgraded my stock ICS to stock JB and then tried to go back to stock ICS with a CWM backup - with the result that I had a brick booting only to a black screen.
I still had access to CWM recovery and so could install the Maximus 2.5 ROM and also the update to stock JB ran through just fine.
I did a factory reset afterwards, is it 100% sure that I now have a pure stock JB or could there be some leftovers from the Maximus 2.5 ROM?
Cheers,
Tim

tim_h said:
Hi everyone,
I still had access to CWM recovery and so could install the Maximus 2.5 ROM and also the update to stock JB ran through just fine.
I did a factory reset afterwards, is it 100% sure that I now have a pure stock JB or could there be some leftovers from the Maximus 2.5 ROM?
Cheers,
Tim
Click to expand...
Click to collapse
Yes you have a stock JB, because with factory reset you've removed all extra application that there is inside MaximuS v.2.5.
All other unneeded file or executable ( like root executable and all other script in /system ect. ) was removed during installation of new ROM.
Remember just that you need to revert to stock to give your phone back to HTC for guarantee, I thinks you must leave on it the stock recovery.
tim_h said:
Hi everyone,
thanks a lot, this saved my ass ... I had upgraded my stock ICS to stock JB and then tried to go back to stock ICS with a CWM backup - with the result that I had a brick booting only to a black screen.
Cheers,
Tim
Click to expand...
Click to collapse
It's happened because from recovery the system was unable to flash the boot partition. So after you did the CWM restore, you have all the phone with ICS android, but JB kernel, this cause your black screen after boot!!!
If you have the boot.img ( with suitable kernel of your old ROM ) to flash after you did the CWM recovery, you can get back to your BACKUP without any problem.
Also if you don't have the exactly boot.img of your previous ROM of the backup, you can flash any boot.img by fastboot of ICS kernel and this is should be enough to keep your backup running again.

Thanks very much for the additional explanations. I do have the boot.img of my original CWM backup, so should be able to restore it via fastboot. Great!
But first I have to send in my phone to have the USB port fixed under warranty.

Holy ****, is working, thanks man...

zujko said:
Wait to see if i understood, i have now Custom ( Virtuous Ville+ RC-1) JB ROM, with hboot 2.15.0000... unlocked, root, twrp
1.install maximuS V2.5, wipe..
2. flash boot.img with fastboot
3.Check update for JB, and flash new update JB?
And that's it?
I guess we have to make relock bootloader, after flash ICS?
Tnx
Click to expand...
Click to collapse
You just forgot in the list to install the HTC Stock recovery before check the message of update, so:
1 => Wipe and install MaximuS V2.5 ROM
2 => flash with fastboot boot.img of MaximuS V2.5 ROM
3 => flash stock HTC Recovery via fastboot ( fastboot flash recovery ville_recovery_signed.img , then fastboot erase cache ) or get it from One_S_All-In-One_Kit_v1.0
4 => start the phone and check for the JB update
5 => after JB installation do a factory reset to clean up the ROM from the extra application that MaximuS ROM have.
You don't need to relock your bootloader, you just need to install the stock recovery, that's enough.

Hmm, wait, why need install stock recovery?
This JB will be working with custom twrp?
EDIT: I got it

I did it! I unmounted first 3 partitions in TWRP and installation successful.

I am on stock Rom now and used HTC offical update to get to jb...do u think I will have trouble rooting again?
Sent from my HTC One S using xda premium

k1llacanon said:
I am on stock Rom now and used HTC offical update to get to jb...do u think I will have trouble rooting again?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I will let you know if I can get it working and flashed it will be rooted in seconds just need stock recovery.

Rooted without a problem, recommend the attached superuser app.

Maverick87Shaka said:
You just forgot in the list to install the HTC Stock recovery before check the message of update, so:
1 => Wipe and install MaximuS V2.5 ROM
2 => flash with fastboot boot.img of MaximuS V2.5 ROM
3 => flash stock HTC Recovery via fastboot ( fastboot flash recovery ville_recovery_signed.img , then fastboot erase cache ) or get it from One_S_All-In-One_Kit_v1.0
4 => start the phone and check for the JB update
5 => after JB installation do a factory reset to clean up the ROM from the extra application that MaximuS ROM have.
You don't need to relock your bootloader, you just need to install the stock recovery, that's enough.
Click to expand...
Click to collapse
Will this work on a T-Mobile HOS with CID HTC__001?
I have followed all the steps from above
- installed the rom
- installed the stock recovery
- then I was able to start the update but when it finished downloading .. I was told that the HTC software on my device has been modified and please revert back and try the update again and it would not preform the update.
What am I doing wrong?
Thanks in Advance

Hi once more,
after going back to pure stock JB this way, can I relock the bootloader to get "RELOCKED" instead of "UNLOCKED/TAMPERED"? (That would be good for sending in my phone under warranty.) Or will the phone stop booting if I relock the bootloader?
As far as I understood, the "canonical" way to get "RELOCKED" would be to lock the bootloader and install the RUU, but since there is no RUU for the unbranded JB yet and downgrading with an older RUU is not possible, I cannot do this.
Cheers,
Tim

tim_h said:
Hi once more,
after going back to pure stock JB this way, can I relock the bootloader to get "RELOCKED" instead of "UNLOCKED/TAMPERED"? (That would be good for sending in my phone under warranty.) Or will the phone stop booting if I relock the bootloader?
Cheers,
Tim
Click to expand...
Click to collapse
You can do Relock bootloader, i think it will boot to system without problem(?)

blah blah blah said:
Will this work on a T-Mobile HOS with CID HTC__001?
I have followed all the steps from above
- installed the rom
- installed the stock recovery
- then I was able to start the update but when it finished downloading .. I was told that the HTC software on my device has been modified and please revert back and try the update again and it would not preform the update.
What am I doing wrong?
Thanks in Advance
Click to expand...
Click to collapse
+ 1
Sent from my HTC One S using xda app-developers app

The only word of caution that I think needs to be shared on almost all threads related to JB updates is to make sure you DO NOT have SuperCID... There have been numerous reports of phones bricking with the OTA JB update with a SuperCID... So if you had previously SuperCID your phone with 11111111, definately change it to something else.

AKToronto said:
The only word of caution that I think needs to be shared on almost all threads related to JB updates is to make sure you DO NOT have SuperCID... There have been numerous reports of phones bricking with the OTA JB update with a SuperCID... So if you had previously SuperCID your phone with 11111111, definately change it to something else.
Click to expand...
Click to collapse
I had to go supercid to run the euro ruu and changed it to HTC__001. Ota still didn't work
Sent from my HTC One S using xda app-developers app

back up/restore

I have h-boot 1.14 withe twrp recovery, I backed up my phone with a previous rom i had and my question is would I have to install the image again after i restore the phone or should the phone restore without any problems.

cal4877 said:
I have h-boot 1.14 withe twrp recovery, I backed up my phone with a previous rom i had and my question is would I have to install the image again after i restore the phone or should the phone restore without any problems.
Click to expand...
Click to collapse
Most of the time yes you will have to install the boot .img manually coming from a different base or Rom... But say if you're on viper and your back up is the same base sense Rom you probably wouldn't have to reflash it... But if coming from cm10 or anything else yes

a box of kittens said:
Most of the time yes you will have to install the boot .img manually coming from a different base or Rom... But say if you're on viper and your back up is the same base sense Rom you probably wouldn't have to reflash it... But if coming from cm10 or anything else yes
Click to expand...
Click to collapse
Awesome thanks man, also im currently running nocturnals dirty rom I believe this is a AOKP rom, now if i want to flash another AOKP or any other CM10 base rom wouldnt the image be the same? or the i have to flash another image of the rom aswell?

cal4877 said:
Awesome thanks man, also im currently running nocturnals dirty rom I believe this is a AOKP rom, now if i want to flash another AOKP or any other CM10 base rom wouldnt the image be the same? or the i have to flash another image of the rom aswell?
Click to expand...
Click to collapse
Be safe and flash it

Is it necessary to reflash rom before restore or can you just fastboot flash boot.IMG and just restore backup?
Sent from my One X using xda premium

I believe you have to flash boot. IMG and than restore according to the comments up there

I just wish we had to option to downgrade the software/hboot without going thru all those steps listed, I remeber i had the htc inspire and you will be able to downgrade hboot by choosing a downgraded version of Ruuu files.

cal4877 said:
I just wish we had to option to downgrade the software/hboot without going thru all those steps listed, I remeber i had the htc inspire and you will be able to downgrade hboot by choosing a downgraded version of Ruuu files.
Click to expand...
Click to collapse
Yeah I loved the inspire that's what got me into android... But I got my phone on hboot 1.09 I've never done the downgrade process but I heard it can be pretty simple