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.

{HELP} device is keep booting into recovey -- SOLVED --

To the Guru of this forum. After my last rom flashing my device is keeping booting into recovery :crying:. Is it briked ? If so my only hope is the unbricking project ? Thanks in advance.

What recovery are you running?
Can you use the power menu within recovery to boot into bootloader?
Also, please provide as much pertinent info as possible, ie: rom you flashed, firmware, s-off or s-on, locked or unlocked. With your description it's basically like saying, "my car makes a noise all the time. what is causing it?".

Its not bricked.If u can enter recovery
Sent from my HTC sensation

Sorry you are right:
What recovery are you running? 4Ext
Can you use the power menu within recovery to boot into bootloader? yes
The device is HTC unlocked with S-On.
Rom JBMIUI v4.1 2.8.31 R2.
HBOOT 1.27.0000
firmware 3.33.401.6
I've format everything but SD. Restored the most recent back up done today before flashing. Once it reboots HTC logo comes up once, black screen, HTC logo, 4Ext is coming up saying that smartflash it is set to update the boot partition on next system start asking if this should be removed.
I've downloaded and installed again PG58IMG *different files using bootloader
I've founded a 3.33.401.6-Unsecured-Boot.img,+Root+Busybox zip file that can be installed via recovery but it did not help.
At this point I need a bit of help to look into the right direction and I'm not sure that Unbrick_Pyramid is the right way.
Thanks again.

Try turning off smartflash and flash a 3.33 stock rom to see if it will boot.
What was your last working setup, and what were you trying to install?
Sent from my HTC Sensation 4G using Tapatalk 2

Hi. Manage to flash a stock 3.33.
It stopped to reboot straight into recovery.
Sits now on HTC logo now for about 10 mins. I plan to let him run for 1 hr and see what happens.
Was thinking to install CWM on the basis that could be a 4ext recovery issue, toughs?
GROGG88 said:
Try turning off smartflash and flash a 3.33 stock rom to see if it will boot.
What was your last working setup, and what were you trying to install?
Sent from my HTC Sensation 4G using Tapatalk 2
Click to expand...
Click to collapse

If you can install clockworkmod that may help.
Tge device isnt getting the message that it has already booted into recovery once. So something may be jacked up with 4ext.
Clockwork may bypass all that when it doesnt know what to do with that signal to run smartflash.
Worst case scenario...put a full pm58img containing a rom and recovery on the sf card and flash that through bootloader.
You should still be able to get to bootloader as the device looks for that option first.
Sent from my HTC Sensation using xda app-developers app

Hallo. Ok installed CWM. Can please direct me to a full pm58img as you mentioned ? Thx.
Skipjacks said:
If you can install clockworkmod that may help.
Tge device isnt getting the message that it has already booted into recovery once. So something may be jacked up with 4ext.
Clockwork may bypass all that when it doesnt know what to do with that signal to run smartflash.
Worst case scenario...put a full pm58img containing a rom and recovery on the sf card and flash that through bootloader.
You should still be able to get to bootloader as the device looks for that option first.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse

DiscreteTask said:
Hallo. Ok installed CWM. Can please direct me to a full pm58img as you mentioned ? Thx.
Click to expand...
Click to collapse
And did that help? Are you able to get into recovery without errors now? If so you should be able to flash a fresh version of any ROM.
Try that first. Get any ROM. Flash it. See if it boots.
If you have successfully replaced 4EXT I will bet a fresh flash of a ROM will now boot.
Also worth a shot is replacing or upgrading the firmware, as that could be what's sending the phone into recovery on each boot (though this is less likely that 4EXT just being broken)
Flash a firmware PM58IMG like 3.32 or 3.33 and see if that helps.
But for starters, put a fresh ROM on the SD card and flash it with CWM. (BE SURE IT'S A ROM THAT DOESN'T REQUIRE 4EXT!!)
Once you've got it all fixed you can switch back to 4EXT. I have a feeling it was just the copy you were running that got botched. The software itself is solid and stable. A new copy shoudl work fine now.

CWM v5.0.2.0 was installed fine.
3.33 firmware installed once again.
Using this I've installed ROM that I already did in the past w/o luck, they all sit on the HTC logo. Is like the initial boot sequence is broken. Is boot.img part of the firmware or ROM ?
Trying to download some additional ones.
Thanks,
Skipjacks said:
And did that help? Are you able to get into recovery without errors now? If so you should be able to flash a fresh
version of any ROM.
Try that first. Get any ROM. Flash it. See if it boots.
If you have successfully replaced 4EXT I will bet a fresh flash of a ROM will now boot.
Also worth a shot is replacing or upgrading the firmware, as that could be what's sending the phone into recovery on each boot (though this is less likely that 4EXT just being broken)
Flash a firmware PM58IMG like 3.32 or 3.33 and see if that helps.
But for starters, put a fresh ROM on the SD card and flash it with CWM. (BE SURE IT'S A ROM THAT DOESN'T REQUIRE 4EXT!!)
Once you've got it all fixed you can switch back to 4EXT. I have a feeling it was just the copy you were running that got botched. The software itself is solid and stable. A new copy shoudl work fine now.
Click to expand...
Click to collapse

DiscreteTask said:
CWM v5.0.2.0 was installed fine.
3.33 firmware installed once again.
Using this I've installed ROM that I already did in the past w/o luck, they all sit on the HTC logo. Is like the initial boot sequence is broken. Is boot.img part of the firmware or ROM ?
Trying to download some additional ones.
Thanks,
Click to expand...
Click to collapse
The more details you give, the better the answers will be. Don't consider any detail too small.
What do you mean you installed ROM's that you had done in the past? Do you mean you are trying to restore a backup made with 4EXT?
That won't work. You need to flash a fresh version of the ROM after wiping.
Also, CWM won't install some ROM's that you may have used in the past. What ROM are you trying to install?
The HTC logo that first pops up when you hit the power button is part of the firmware.
Make sure you do a full wipe of everything but the SD card from within CWM. Get whatever's causing the problem off that way. Then flash a fresh install of a ROM from scratch.

Hi.
I did not use any backup only fresh ROMs: ARHD, Elegantia, but also stock ROMs I could find.
I've tried also some PG58IMG with ROM included.
Cheers.
Skipjacks said:
The more details you give, the better the answers will be. Don't consider any detail too small.
What do you mean you installed ROM's that you had done in the past? Do you mean you are trying to restore a backup made with 4EXT?
That won't work. You need to flash a fresh version of the ROM after wiping.
Also, CWM won't install some ROM's that you may have used in the past. What ROM are you trying to install?
The HTC logo that first pops up when you hit the power button is part of the firmware.
Make sure you do a full wipe of everything but the SD card from within CWM. Get whatever's causing the problem off that way. Then flash a fresh install of a ROM from scratch.
Click to expand...
Click to collapse

Arhd and elegencia wont work with cwm. So there is your isdue. Try cm9 or 10 to see if you can boot one of those.
Sent from my HTC Sensation using xda app-developers app

Hallo, after trying all option the following did work for me:
- re-lock bootloader via fastboot oem lock
- apply stock ROM founded in this list http://forum.xda-developers.com/showthread.php?t=1074559
- rebooted fine
I guess that HTC RUU had some superpower and erase and installed whatever file(s) were corrupted.
Now I'm on stock 3.6 - fw 3.33.401.106 - radio 11.76A.3504.00UU_11.24A.3504.31_M
HBOOT 1.29 - S-ON - Relocked.
Standard Recovery.
Now I'm reading how to return my device to S-OFF w/o damaging it again.
Many thanks to skipjacks & groog88 :good:
Skipjacks said:
Arhd and elegencia wont work with cwm. So there is your isdue. Try cm9 or 10 to see if you can boot one of those.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse

[Q] SD card appears as only 48MB. how come?

Hi, seems like my One S's sdcard partition has corrupted. been using TWRP 2.500 and recently upadted to 2.6.30 to use the new Maximus Rom. During the rom installation, I wiped the sdcard sectrion by mistake so I couldn't get to flash the zip file, then, I've tried multiple times of recovery.img flashings via RUU mode or on the bootloader screen. Finally when I got the TWRP recovery mode again, it says the sdcard folder only accepts 48 MB so I cannot push any custom roms since they are bigger than 500MB... Any ideas? Should I send it to the repair shops? Please Help!! Thank you!
FYI, my phone was
Tampered, Unlocked, S-off
also, when I press mount button on TWRP, this list appears
Cache
Data
Internal SDcard
System
USB-OTG
but I select Internal SD, the computer says the removable disk has only 48MB of available space.(I wiped it multiple times!)

puwa said:
Hi, seems like my One S's sdcard partition has corrupted. been using TWRP 2.500 and recently upadted to 2.6.30 to use the new Maximus Rom. During the rom installation, I wiped the sdcard sectrion by mistake so I couldn't get to flash the zip file, then, I've tried multiple times of recovery.img flashings via RUU mode or on the bootloader screen. Finally when I got the TWRP recovery mode again, it says the sdcard folder only accepts 48 MB so I cannot push any custom roms since they are bigger than 500MB... Any ideas? Should I send it to the repair shops? Please Help!! Thank you!
FYI, my phone was
Tampered, Unlocked, S-off
also, when I press mount button on TWRP, this list appears
Cache
Data
Internal SDcard
System
USB-OTG
but I select Internal SD, the computer says the removable disk has only 48MB of available space.(I wiped it multiple times!)
Click to expand...
Click to collapse
Omg. Why the people dont read op before they are going to flash new Rom. Just follow the instructions.
Sent from my HTC One S

tominozh said:
Omg. Why the people dont read op before they are going to flash new Rom. Just follow the instructions.
Sent from my HTC One S
Click to expand...
Click to collapse
Could you please tell me at least it's repairable or not? I want your help..
Also, I wonder what part I missed so it happened...hmm

puwa said:
Could you please tell me at least it's repairable or not? I want your help..
Also, I wonder what part I missed so it happened...hmm
Click to expand...
Click to collapse
Yes, don't sweat it. It is repairable.
It's hard for my to tell what you missed, because you didn't write what you did. So just follow installation instructions in the first post of maximus Rom. (flash new firmware, modified recovery, then Rom).
Sent from my HTC One S

tominozh said:
Yes, don't sweat it. It is repairable.
It's hard for my to tell what you missed, because you didn't write what you did. So just follow installation instructions in the first post of maximus Rom. (flash new firmware, modified recovery, then Rom).
Sent from my HTC One S
Click to expand...
Click to collapse
thank you! so, for flashing a new firmware, what would be a good firmware to start? any recommendations? i tried the firmware.zip in the install kit but not worked. same 48MB limit on the /sdcard/. any ideas?
:laugh:

Just follow this. It worked for almost all of us..
http://forum.xda-developers.com/showthread.php?p=45621060

gelo01 said:
Just follow this. It worked for almost all of us..
http://forum.xda-developers.com/showthread.php?p=45621060
Click to expand...
Click to collapse
GRT!! Thanks so much for saving my LIFE!!

gelo01 said:
Just follow this. It worked for almost all of us..
http://forum.xda-developers.com/showthread.php?p=45621060
Click to expand...
Click to collapse
All of these steps work for me except flashing the recovery as a ZIP. I get the wrong CID error (code 42 if i remember correctly). Thing is, I flash the .img directly usign fastboot flash recovery and that works but then the install process says, in android, transfer ROM. At this point, I don't have access to the SD card and the ROM is not in my sd card (it was wiped anyway?)
*EDIT*
Ok I changed my CID to 1111111 and now it works to flash the firmware. I still get partitions errors it seems though.
What I did is flash the stock recovery, clear storage, factory reset, reflashed the firmware given in Maximus thread, then the TWRP given and still, I get problems with my sdcard not mounting?

GabeyC said:
All of these steps work for me except flashing the recovery as a ZIP. I get the wrong CID error (code 42 if i remember correctly). Thing is, I flash the .img directly usign fastboot flash recovery and that works but then the install process says, in android, transfer ROM. At this point, I don't have access to the SD card and the ROM is not in my sd card (it was wiped anyway?)
*EDIT*
Ok I changed my CID to 1111111 and now it works to flash the firmware. I still get partitions errors it seems though.
What I did is flash the stock recovery, clear storage, factory reset, reflashed the firmware given in Maximus thread, then the TWRP given and still, I get problems with my sdcard not mounting?
Click to expand...
Click to collapse
if you are talking about mounting usb storage in recovery, then no, you cannot do that on Maximus HD rom. (it's a modified TWRP to work on the new firmware)
You can sideload in TWRP or ADB push the rom to your sdcard.
I would give you a link to a page describing it, but search is unavailable right now, have to try later.
But just search that thread with keyword sideload. There you will find the exact commands to load the rom onto your sdcard.

tivofool said:
if you are talking about mounting usb storage in recovery, then no, you cannot do that on Maximus HD rom. (it's a modified TWRP to work on the new firmware)
You can sideload in TWRP or ADB push the rom to your sdcard.
I would give you a link to a page describing it, but search is unavailable right now, have to try later.
But just search that thread with keyword sideload. There you will find the exact commands to load the rom onto your sdcard.
Click to expand...
Click to collapse
Yea, that's exactly what I ended up doing... it's not clear on any thread though...
Thanks
I went back to CM, didn't like maximus so much and it didn't fix my EDGE only problem so

It went back to 48mb
Hi i had the same problem with my htc one s.So i paniced and for some reason i put s-on(I deleted the os from the pc using mount storage) I managed to fix it by installing the recovery as zip. Then i tried to adb sideload a rom but it didn't work. So i went to boot loader then to fast boot and did fastboot flash zip Energyrom.zip. That gave me an error so i went back to recovery to try to side load the rom again, but my sdcard went back to 48mb.I reflashed the recovery (the one from install package) same thing . What do i do????? I need help asap i want my phone back (IM ONLY 12) Please reply asap.

cyberusman said:
Hi i had the same problem with my htc one s.So i paniced and for some reason i put s-on(I deleted the os from the pc using mount storage) I managed to fix it by installing the recovery as zip. Then i tried to adb sideload a rom but it didn't work. So i went to boot loader then to fast boot and did fastboot flash zip Energyrom.zip. That gave me an error so i went back to recovery to try to side load the rom again, but my sdcard went back to 48mb.I reflashed the recovery (the one from install package) same thing . What do i do????? I need help asap i want my phone back (IM ONLY 12) Please reply asap.
Click to expand...
Click to collapse
I think the easiest way is to flash the stock recovery and then do a sdcard wipe then a factory reset.
After that, you go through the process as described in the maximus rom thread, you will have to flash with sideload. That should work afterward

I am doomed
Hi guys,
Yesterday I decided to try MaximusROM 10.0.0 HD on my HTC One S, which is s-OFF and with superCID. The problem is: I didn't flashed first the rom as it was said, and I just used the Installation Package, installing directly the firmware.zip and the modified recovery. I tried to follow the steps written before, but now my phone works with the stock rom but it says that there are only 48mb in sd card, and that means that I can't even take photos, because I have no memory left. I found out that my phone, when is booted up, in settings says that I have 15,96GB of space for applications. What can I do?

GabeyC said:
I think the easiest way is to flash the stock recovery and then do a sdcard wipe then a factory reset.
After that, you go through the process as described in the maximus rom thread, you will have to flash with sideload. That should work afterward
Click to expand...
Click to collapse
I think I need to to that process my sdcard appears to be 10 gig only. Do you have a link for stock recovery? mine is S4.

48 mb storage = new 3.16 firmware
fix = flash custom 2.6.1 twrp
Sent from my HTC One S using XDA Premium 4 mobile app

lost sd card 48mb
Hi I have big problem with my HTC one s I decided to install maximus hd but I need super cid and s-off facepalm metod everything I do original cid cange to 1111111... Get s-off acses and and install Rom then firmware and when Rom but Rom loads very slowly and sometimes
Black screen and not won't load Rom. And I decided to back s-on and back to original CID HTC_111 and install tricdroid beta 10.0 and then my sdcard 48mb. I try everything flash stock recovery delete all data and wipe but still 48mb try changing a few recovery cmrecovery all types and Twrp recovery but work one prefect Twrp 2.6.1.0 this recovery show me 12gb but I installed Rom on pc 48 I try again flash firmware from maximus hd but failed bicose I change my cid and back to s-on then. I try to go to s-off and change my cid to 11111111.
Noting happen my cid still htc_111 I can't do s-off my hboot is 2.16.0000 I read this forums I find many solutions but no-one don't help my. Try install three roms trickdroid magiobeta and source v14 still 48 I just want get my sd card please somebody. I try many thing relock boot loader try with ruu but still 48

help
dcvc said:
Hi I have big problem with my HTC one s I decided to install maximus hd but I need super cid and s-off facepalm metod everything I do original cid cange to 1111111... Get s-off acses and and install Rom then firmware and when Rom but Rom loads very slowly and sometimes
Black screen and not won't load Rom. And I decided to back s-on and back to original CID HTC_111 and install tricdroid beta 10.0 and then my sdcard 48mb. I try everything flash stock recovery delete all data and wipe but still 48mb try changing a few recovery cmrecovery all types and Twrp recovery but work one prefect Twrp 2.6.1.0 this recovery show me 12gb but I installed Rom on pc 48 I try again flash firmware from maximus hd but failed bicose I change my cid and back to s-on then. I try to go to s-off and change my cid to 11111111.
Noting happen my cid still htc_111 I can't do s-off my hboot is 2.16.0000 I read this forums I find many solutions but no-one don't help my. Try install three roms trickdroid magiobeta and source v14 still 48 I just want get my sd card please somebody. I try many thing relock boot loader try with ruu but still 48
Click to expand...
Click to collapse
Someone may be help me with this trouble :crying::crying::crying::crying::crying::crying::crying::crying::crying:
:crying::crying::crying::crying::crying::crying: Thanks for the help :crying::crying::crying::crying::crying:

same here what should we do i have managed to install magiorom but windows shows only 48mb all i want is to get back to stock but i messed up my cid i am on roger001 but i cannot find a correct rom as i have mi mid pj4010000 please help me get back to stock