Database Info

Desire s stuck after 2.3.5 update

i tried to update via phone (after the notification), but after green bar was full, my phone rebooted and stuck in white screen with htc logo... if i try to enter in recovery i see this
h*tp://i39.tinypic.com/xdxnc5.jpg
it seems to be s-off (i bought it used) ...what have i to do for make it work again??
tnx.. and sorry for my bad english

same problem here, help is needed!

A golden rule: never update OTA on a modified device (custom ROM even modified Stock one, custom Recovery, Revolutionary hboot!, etc.)
How to fix:
do not pull battery!
flash a custom recovery (e.g. 4EXT) with the fastboot command (search for a how-to)
reboot to recovery, wipe all partitions and install custom ROM

Ok, to late with the battery, have already pulled that one out!
I also have S-Off on my phone, really dont understand the how to fix a recovery??
And is it really neccessary to flash a new ROM for this?
An official release that screwes the phones up?

I think the general issue is that an 'Official' OTA upgrade should not screw up your phone - enough testing by HTC should make sure of that.
Hoever, if you have modified your phone (e.g. by rooting it, installing custom recovery etc) then you can not expect to blame HTC when their upgrade doesn't work as expected. They can't be held responsible for problems caused by modifications you make to the phone.

But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?

Akerhage said:
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Click to expand...
Click to collapse
The OTA flashes a new hboot also.
If you S-OFFed with Revolutionary your hboot has to be version 6.98.000x. This hboot has a protection and cannot be overwritten. This is the point where the update process is interrupted. The result is a bootloop, because the new system is incomplete.
If you can boot to bootloader (hboot) you should be able to flash a custom recovery with the fastboot command (in the 4EXT Recovery thread there is an attachement - a zip file that contains recovery.img). Extract the archive and flash it with this command from cmd (there is a guide how to make fastboot working in my signature):
Code:
fastboot flash recovery {path to file on your PC}/recovery.img
If this works reboot to recovery, wipe all partitions and flash a custom ROM. Then your phone should be working again.
Then if you want the OTA flash a 0.98.2000 hboot, then use the 1.47.401.4 RUU (if you are using European unbranded) or the corresponding for your brand/region to return back to complete Stock and S-ON. Then you will be prompted to update and you will have the latest OTA on your device

Okay, I have now fixed the 4EXT Recovery and it is working!
Do I have to put a new ROM on the SD-card or is there another way to install a ROM (from cmd with the ROM on the computer etc?)
I dont have an adapter to the SD-card, but maybe I can put the ROM on the sdcard with a command in cmd aswell?
What ROM do you recommend to use? (sense, no sense doesnt matter)
Edit: I did a backup as well, thinking that I should do that...

Can you link to zip file you used for recovery i have exactly same issue and same software versions as you have.

@ Mooler. First of follow the guide that was posted here regarding the adb-drivers.
After that download this: http://forum.xda-developers.com/attachment.php?attachmentid=631186&d=1308596026
Then install that one as described with the cmd-command.
After that just put a custom ROM or a shipped ROM on the SD-card, wipe data/cache and install the ROM you want. That solved the problem for me!
Good Luck and thanks for the help I got here! Xda always delivers

Damn this phone! After hours of fixing with this problem!
I managed great, installed new kernels, radios, ROMs etc. And the first thing I did was to drop it on the floor so the whole damn display cracked!

Thanks for both of you.
I managed to restore the phone quickly after i got the correct recovery file. 30 mins and custom ROM was up and running. Good bye official update.
Akerhage: sad to here, it really was hours of reading and trying before you get it right.

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

[Q] Paranoid noob question regarding S-off and previous Bootloader

I am wondering if I made any major changes or done anything wrong.
1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?
2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.
Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much

fashofasho said:
I am wondering if I made any major changes or done anything wrong.
1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?
2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.
Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much
Click to expand...
Click to collapse
when you did S-OFF in order to install Cyanogen JB first you had to flash the latest fw version and then the rom
the rom you tried to install requires the latest fw version
now are you still s-off?
what is now your hboot version?
what is your fw version?

I am wondering if I made any major changes or done anything wrong.
1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?
2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.
Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much
Click to expand...
Click to collapse
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.
2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)
Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.
If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.
If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!
Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.
It should not boot.
This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!
I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.

Skipjacks said:
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.
2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)
Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.
If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.
If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!
Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.
It should not boot.
This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!
I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.
Click to expand...
Click to collapse
i got confused
.i think your answer is going for fashofasho

Skipjacks said:
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.
2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)
Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.
If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.
If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!
Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.
It should not boot.
This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!
I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.
Click to expand...
Click to collapse
Thanks for the reply. Okay so here is where I am currently at. I haven't done anything since I reflashed stock ROM throguh RUU after the fail cyanogen flash. On this stock ROM whenever I load into bootloader it still says s-off 1.17 but I did lose my clockworkmod. So according to your instructions I should either clockworkmod again or 4ext now, that's okay right? If so, going to flash firmware then cyanogen!! Or is there a problem that I have s-off but not recovery.
P.s. there is no point in running revolutionary and have it s-off again when I already have it right, just thought it might be necessary to make things fresh

If you have a bootable phone right now this is easy as you may not need adb or fast boot or anything.
First off you will need to install 4ext. Get the app from the Play Store. Then run it and let it install its recovery module. (You may need to be rooted to do thus, which your stock rom is not. Im not sure if you can flash the recovery without root or not because Ive never tried without root. If so, then you will have to install Superuser via fastboot I think. You any guide for rooting to get instructions on this. Its easy.)
You may also find a way to install 4ext recovery via flashing from bootloader, but you will have to search for that. You MAY even be able to install it with the firmware upgrade. You will have to see if that is an available option.
Get your firmware from this thread...
forum.xda-developers.com/showthread.php?t=1459767
Follow the instructions to update. Once you have 3.3x firmware and 4ext simply boot to recovery, do a full wipe, and flash cm10 (make sure cm10 is on your sd card. You can download it from your currently working gingerbread rom so you have it available)
You have like 15-20 minutes worth of work to do, so its not a monumental obstacle to overcome. It just seems like alot
Sent from my HTC Sensation using xda app-developers app

Skipjacks said:
If you have a bootable phone right now this is easy as you may not need adb or fast boot or anything.
First off you will need to install 4ext. Get the app from the Play Store. Then run it and let it install its recovery module. (You may need to be rooted to do thus, which your stock rom is not. Im not sure if you can flash the recovery without root or not because Ive never tried without root. If so, then you will have to install Superuser via fastboot I think. You any guide for rooting to get instructions on this. Its easy.)
You may also find a way to install 4ext recovery via flashing from bootloader, but you will have to search for that. You MAY even be able to install it with the firmware upgrade. You will have to see if that is an available option.
Get your firmware from this thread...
forum.xda-developers.com/showthread.php?t=1459767
Follow the instructions to update. Once you have 3.3x firmware and 4ext simply boot to recovery, do a full wipe, and flash cm10 (make sure cm10 is on your sd card. You can download it from your currently working gingerbread rom so you have it available)
You have like 15-20 minutes worth of work to do, so its not a monumental obstacle to overcome. It just seems like alot
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
I am not rooted but am S-off. So my next step would be to root. I am suppose to have Clockworkmod to root AND 4EXT after right? Its not one or the other? I keep reading that people recommend 4ext is better than CWM but in order to root su-2.3.6.3-ef-signed.zip I need CWM first correct?

fashofasho said:
I am not rooted but am S-off. So my next step would be to root. I am suppose to have Clockworkmod to root AND 4EXT after right? Its not one or the other? I keep reading that people recommend 4ext is better than CWM but in order to root su-2.3.6.3-ef-signed.zip I need CWM first correct?
Click to expand...
Click to collapse
flash su-2.3.6.3-ef-signed.zip first and then install 4ext recovery

You're over engineering this. You don't need to root your current ROM first. That's an extra step since you're s-off.
If you are s-off it's really simple to get 4EXT recovery.
First, download this and put it on the root directory of your SD Card (meaning not in a folder, just on the SD Card. Do not rename it)
http://d-h.st/qnm
I got this download link from here...
http://forum.xda-developers.com/showthread.php?p=21989107
Click Thanks for Joaquinf in that thread. He made the 4EXT zip that's flashable through the bootloader.
That is 4EXT made into a zip file that's flashable via the bootloader, which you can do when you are S-off.
So put that file on the SD card, power the phone off, pull the battery out for a second and put it back in (this stops fastboot so you can get back to the bootloader). Then hold volume down and power at the same time. You have to hit both buttons at the same time. If it goes to the splash screen, pull the battery and try again.
When the bootloader loads up it will immediately find the PM58IMG.zip file. It will ask you if you want to install the update. Say yes by hitting volume up I think (it will tell you how to say yes)
Put the phone down and don't touch it until it tells you it's done. Should just take a second. But seriously don't touch it. Leave it alone.
If that works, you've just flashed 4EXT. You can check it by pulling the SD card out (so it doesn't try to flash the PM58IMG again) and rebooting to the bootloader and selecting 'recovery' from the menu. 4EXT should boot up.
This entire process so far shouldn't take more than 3 minutes total. It just sounds like a lot.
To see this detailed out by someone else in case you want to check what I'm saying, read steps 4 and 5 of the first post in this thread.
http://forum.xda-developers.com/showpost.php?p=21989063&postcount=1
Give the author 'thanks' again because he's awesome and deserves it.
Now you've got 4EXT installed. Great. You're 1/3rd of the way home.
Now you need to update your firmware. Delete the PM58IMG.zip file you used to flash 4EXT off the SD card (use a card reader or boot the phone up and delete it, whatever works. You can also use 4EXT as a card reader now too by choosing USB storage from inside 4EXT. It will give you access toteh SD card on your computer now)
Now get new Firmware from this thread.
http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
try the 3.33 firmware universal. First download link in post 2 of the thread above.
CHECK THE MD5 SUM!!!! I'M NOT PLAYING AROUND HERE!!! You are worried about bricking your phone, this is where you can do it if the firmware .zip is bad.
Put that PM58IMG file on your SD and flash it in the bootloader the same way you flashed 4EXT recovery a minute ago. (If you're still in 4EXT recovery you can use it's power menu to reboot into bootloader easily.)
This will take a minute. The phone will shut off and go black in the middle of this process. Your heart will skip a beat. Relax. It'll come back on. Again, put the phone down and walk away while it does it's thing and don't touch it until it says it's done.
Delete the PM58IMG file from your SD card.
You are now 2/3 of the way there. Your phone WILL NOT boot up right now because your ROM is not compatible with your firmware. Relax. That's supposed to happen.
Now you can flash CM10. Make sure you have the CM10.zip file on your SD card nad GApps. (Bruce has Gapps in his downloads page). Delete the PM58IMG firmware file from your SD card (that's important)
Pull the battery again so you can get back into bootloader. Get into bootloader (power + volume down)
Select Recovery
4EXT should boot up.
Go to the Wipe menu. Wipe all partitions except SD card. (Old ROM is now gone)
Go back to the main menu.
Install from SD
Find the CM10.zip file you should have downloaded and put onto the SD card. Flash it.
This will take about 3 minutes. 4EXT will flash it and ask if you want to reboot. You do not yet. Not you need to flash Gapps the same way you flashed the ROM.
When that's done, now you can reboot. You shoudl see the CyanogenMod boot animation after the splash screen. Give it a few minutes to boot up this first time. Once it boots, set it up the way you like it. If you enjoy it, donate a few bucks to the developer, Bruce.
You don't have to root CM10. It's already rooted when you boot it up the first time.

Android Revolution HD 7.3

Hey guys,
Having some problems with this ROM. I downloaded the ZIP, used Titanium backup to back it all up, and flashed the Rom with no problems at all...got through all the screens and whatnot, and upon launching for the first time it's stuck on the "Beats Audio" screen. Not really sure why or what happened. I'm coming from MIUI ROM and haven't had issues with flashing any other ROM before.
One thing I noticed is on the HD 7.3 first page there is a firmware update that you apparently need before you flash the ROM but all links are 404/not found.
Wondering if any of you pros can offer a hand?
-Cain

Cainsmoker said:
Hey guys,
Having some problems with this ROM. I downloaded the ZIP, used Titanium backup to back it all up, and flashed the Rom with no problems at all...got through all the screens and whatnot, and upon launching for the first time it's stuck on the "Beats Audio" screen. Not really sure why or what happened. I'm coming from MIUI ROM and haven't had issues with flashing any other ROM before.
One thing I noticed is on the HD 7.3 first page there is a firmware update that you apparently need before you flash the ROM but all links are 404/not found.
Wondering if any of you pros can offer a hand?
-Cain
Click to expand...
Click to collapse
post the output of this command
fastboot getvar all
don't show your imei and serial number
and what recovery do you have?

rzr86 said:
post the output of this command
fastboot getvar all
don't show your imei and serial number
and what recovery do you have?
Click to expand...
Click to collapse
In looking at my Hboot, it's old as sin....I'm using Revolutionary Hboot 1.17.1111 and Radio 10.14.9035.01_M
I run clockwork recovery mod v5.0.2.0 as well. This could be an issue causing the problem. I've been using the MIUI ROM for probably 2 years or so because I enjoyed it but I'm ready for a change. Apparently my phone doesn't agree. lol.
You want me to connect via USB and run the cmd prompt for the getvar command and let you know what it says?

Cainsmoker said:
In looking at my Hboot, it's old as sin....I'm using Revolutionary Hboot 1.17.1111 and Radio 10.14.9035.01_M
I run clockwork recovery mod v5.0.2.0 as well. This could be an issue causing the problem. I've been using the MIUI ROM for probably 2 years or so because I enjoyed it but I'm ready for a change. Apparently my phone doesn't agree. lol.
You want me to connect via USB and run the cmd prompt for the getvar command and let you know what it says?
Click to expand...
Click to collapse
there is no need to do it now
you gave me exactly what i need
you still have gb firmware that's why you can't boot ARHD 7.3(ics rom)
see this thread
http://forum.xda-developers.com/showthread.php?t=1459767
flash 3.33 universal
follow the instructions to the letter
and before flashing check md5 sums(important)

The speedy reply is much appreciated.
I'll go ahead and update the firmware and see where that lands me. I figured it could have been a problem from the get go but in the original thread for the HD 7.3 Rom the firmware link has been removed (likely since it was from 2011)
Thanks for the point in the right direction Rzr, and I'll let you know how it goes!
rzr86 said:
there is no need to do it now
you gave me exactly what i need
you still have gb firmware that's why you can't boot ARHD 7.3(ics rom)
see this thread
http://forum.xda-developers.com/showthread.php?t=1459767
flash 3.33 universal
follow the instructions to the letter
and before flashing check md5 sums(important)
Click to expand...
Click to collapse

Hmmm....the firmware update didn't work.
I can verify that I'm on the firmware 3.3, Hboot is 1.27.1100, Radio is 11.24A.3504.31_M.
Each time Hboot is run it asks if I want to start the update. If I select yes, I've got 9 on screen options that it runs through and tells me "Update complete. Press power to reboot" The only way to do anything at all is to take out the SD card so it does not try to load up the firmware zip
Pushing power reboots the phone on an endless boot loop. Regardless of what ROM is being used (I also downloaded cyanogenmod) I can not make it past the spash screen.
Could it be that I'm just flashing the ROM incorrectly? To my knowledge I've followed instructions for both and have backed up my phone and it's contents and done everything from a factory reset/wipe to wiping the dalvik cache, etc. I didn't have this many problems rooting my phone and putting on MIUI to begin with and have flashed ROMS before with no trouble....not really sure where I'm going wrong on this one.
Anyway, I'll await your reply.
Thank you!
-Cain
Update: awww frick. So now it looks like this will be more difficult....I hope you like a challenge. I can now no longer get into my phone. It appears that it's soft bricked. I have tried going to a clockwork mod recovery from my first MIUI in 2012, it goes through the entire process of factory resetting restoring the boot image, system and data information. It asks for a reboot which I do. It goes to the white HTC splash screen and the MIUI initializes and goes black immediately. There doesn't seem to be a way to get my phone connected to my computer to get into the SD card to troubleshoot from inside the phone. Hopefully one of you guys has the answer for me. Is there any way to get into it via bootloader usb?

Cainsmoker said:
Hmmm....the firmware update didn't work.
I can verify that I'm on the firmware 3.3, Hboot is 1.27.1100, Radio is 11.24A.3504.31_M.
Each time Hboot is run it asks if I want to start the update. If I select yes, I've got 9 on screen options that it runs through and tells me "Update complete. Press power to reboot" The only way to do anything at all is to take out the SD card so it does not try to load up the firmware zip
Pushing power reboots the phone on an endless boot loop. Regardless of what ROM is being used (I also downloaded cyanogenmod) I can not make it past the spash screen.
Could it be that I'm just flashing the ROM incorrectly? To my knowledge I've followed instructions for both and have backed up my phone and it's contents and done everything from a factory reset/wipe to wiping the dalvik cache, etc. I didn't have this many problems rooting my phone and putting on MIUI to begin with and have flashed ROMS before with no trouble....not really sure where I'm going wrong on this one.
Anyway, I'll await your reply.
Thank you!
-Cain
Update: awww frick. So now it looks like this will be more difficult....I hope you like a challenge. I can now no longer get into my phone. It appears that it's soft bricked. I have tried going to a clockwork mod recovery from my first MIUI in 2012, it goes through the entire process of factory resetting restoring the boot image, system and data information. It asks for a reboot which I do. It goes to the white HTC splash screen and the MIUI initializes and goes black immediately. There doesn't seem to be a way to get my phone connected to my computer to get into the SD card to troubleshoot from inside the phone. Hopefully one of you guys has the answer for me. Is there any way to get into it via bootloader usb?
Click to expand...
Click to collapse
remove the pg58img.zip from your sdcard so it won't scan and identify any pg58img.zip file
and don't restore your miui rom because probably is a gb one and now you have an ics firmware installed
just download an ics or jb rom
put it on your sdcard
full wipe from recovery
flash the rom
done

rzr86 said:
remove the pg58img.zip from your sdcard so it won't scan and identify any pg58img.zip file
and don't restore your miui rom because probably is a gb one and now you have an ics firmware installed
just download an ics or jb rom
put it on your sdcard
full wipe from recovery
flash the rom
done
Click to expand...
Click to collapse
With the phone being in a boot loop I can't get it detected by my computer to remove/add anything from the SD card. I do have the HD 7.3 ROM on and the Gapps that's required but it never makes it past the "beats audio" splash screen. I have no idea what's going on with it but will try any suggestions you've got up your sleeve.

Ahhhhh....I've gotten a fix for this!
I was unable to do anything because of the update zip which wanted me to update every time bootloader was initiated. By keeping my case off I removed my SD card to be able to boot in recovery and then put the SD card back in to load the HD 7.3 zip from the card. This seemed to take care of the problem.
Thanks for the help Rzr

Need help getting to sense 6

So a few months ago I switched to CyanogenMod 11 while I was on sense 5. Well Cyan has started running really slow and not even the updates have fixed this. I have cwm installed, s-off, and my boatloader unlocked. Could someone tell me how exactly I go about flashing a sense 6 ROM? I'd greatly appreciate the help. Thanks !

Bump: anyone ?
Sent from my One Mini using XDA Free mobile app

Socrats said:
Bump: anyone ?
Sent from my One Mini using XDA Free mobile app
Click to expand...
Click to collapse
This is a good guide. You can probably start at step 3. Before you start, you should copy a sense 6 rom to your sd card. Also, in case your sd card gets wiped during the process, you should make sure you are able to push a rom to your phone from recovery (either ADB push or OTG device).
http://forum.xda-developers.com/showthread.php?t=2789272
Obviously, you should back everything up before you begin. If you're on older firmware your phone will probably be wiped completely.
Here are some good sense 6 ROMs:
http://forum.xda-developers.com/showthread.php?t=2753784
http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921
http://forum.xda-developers.com/htc-one-mini/development/rom-liberty-rom-sixth-sense-t2875292

Thanks bro ! I'll try this when I get home and let you know how it works.
Sent from my One Mini using XDA Free mobile app

jollywhitefoot said:
This is a good guide. You can probably start at step 3. Before you start, you should copy a sense 6 rom to your sd card. Also, in case your sd card gets wiped during the process, you should make sure you are able to push a rom to your phone from recovery (either ADB push or OTG device).
http://forum.xda-developers.com/showthread.php?t=2789272
Obviously, you should back everything up before you begin. If you're on older firmware your phone will probably be wiped completely.
Here are some good sense 6 ROMs:
http://forum.xda-developers.com/showthread.php?t=2753784
http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921
http://forum.xda-developers.com/htc-one-mini/development/rom-liberty-rom-sixth-sense-t2875292
Click to expand...
Click to collapse
Quick question, I'm going to flash the insert coin rom, but can I do this if my phone's boot loader is unlocked even without s-off? Also my phone currently has cwm installed for recovery, is it possible to just install twrp using the guide you posted even if I have cwm? Sorry for all of the questions lol. Thanks in advance.

Socrats said:
Quick question, I'm going to flash the insert coin rom, but can I do this if my phone's boot loader is unlocked even without s-off? Also my phone currently has cwm installed for recovery, is it possible to just install twrp using the guide you posted even if I have cwm? Sorry for all of the questions lol. Thanks in advance.
Click to expand...
Click to collapse
Boot loader unlocked is good.
You can't upgrade to sense 6 firmware unless you're s-off. But I thought you were already s-off? Have you ever been s-off? What firmware are you on now? Hboot and radio versions from boot loader.
Yes. Installing twrp 2.7.1.1 will replace the cwm recovery.
I can't stress enough...make a backup in recovery. And copy that backup and anything else you don't want to lose to your computer. It's very possible that your phone can be completely wiped during the process.
I'd also make sure that adb worked from recovery. In the event you can't boot your device into os (which means you won't be able to drag and drop the Rom to your device), you'll have to use adb commands to push the Rom to your device. You can test this by flashing twrp 2.7.1.1, then enter recovery. Then from your computer, in adb folder in a command prompt, type "adb devices". This should return your device serial number.

jollywhitefoot said:
Boot loader unlocked is good.
You can't upgrade to sense 6 firmware unless you're s-off. But I thought you were already s-off? Have you ever been s-off? What firmware are you on now? Hboot and radio versions from boot loader.
Yes. Installing twrp 2.7.1.1 will replace the cwm recovery.
I can't stress enough...make a backup in recovery. And copy that backup and anything else you don't want to lose to your computer. It's very possible that your phone can be completely wiped during the process.
I'd also make sure that adb worked from recovery. In the event you can't boot your device into os (which means you won't be able to drag and drop the Rom to your device), you'll have to use adb commands to push the Rom to your device. You can test this by flashing twrp 2.7.1.1, then enter recovery. Then from your computer, in adb folder in a command prompt, type "adb devices". This should return your device serial number.
Click to expand...
Click to collapse
No I'm not s-off, every method I've tried has failed. It's actually something I've been having trouble with. My phone is rooted, and every method has failed. I just tried firewater about 20 mins ago and it failed saying my phone isn't supported. This isn't my first time trying either.

Socrats said:
No I'm not s-off, every method I've tried has failed. It's actually something I've been having trouble with. My phone is rooted, and every method has failed. I just tried firewater about 20 mins ago and it failed saying my phone isn't supported. This isn't my first time trying either.
Click to expand...
Click to collapse
What firmware?

My firmware is 1.25.40g

Socrats said:
My firmware is 1.25.40g
Click to expand...
Click to collapse
That's just radio...what's hboot? 2.22?

jollywhitefoot said:
That's just radio...what's hboot? 2.22?
Click to expand...
Click to collapse
Oh lol, yes my hboot is 2.22

Socrats said:
Oh lol, yes my hboot is 2.22
Click to expand...
Click to collapse
You should be on the new partition layout, and should be able to flash a sense 6 rom without updating firmware.
Insert Coin might work, but i'm not positive about that. This stock one should definitely work: http://forum.xda-developers.com/showthread.php?t=2791725
I flashed this one when i was s-on, on hboot 2.22 and radio 1.25 without any problems. Once you're on that ROM, you can probably get s-off with Rumrunner if you want.
Here's the path I took when my device was in the state yours is in (S-On, hboot 2.22 & Radio 1.25)
- Flash TWRP 2.1.1.1 recovery
- make a full backup from TWRP
- test adb* from recovery (specifically: make sure "adb devices" returns your serial number, and that you can use "adb push <nameofROM.zip>" to your sdcard)**
- reboot into OS
- Copy the backup you just made (twrp folder on sdcard) and all other files that you don't want to lose to your computer (make sure to leave the TWRP backup on your sdcard in case you need to restore)
- Copy the sense 6 rom to your device
- Reboot into recovery
- Wipe your device*** (once you do this, your phone will not boot until you flash a working rom, or restore the backup you just made)
- Go to "Install" and find your rom's zip file on the sdcard, select it and swipe to flash ****
- After your ROM has flashed, if you don't get any errors, you can reboot your device
- That should be it...you will see a white screen with HTC on it for a little while while (sometimes as long a 5 or more minutes...or at least it seems that way sometimes) the installation finalizes (but there's no progress bar, so you just need to be patient here).
* here is more information on setting up adb if you need it: http://techbeasts.com/2013/08/26/how-to-install-adb-fastboot-drivers-on-your-windows-pc-guide/
** this is not an essential step IF EVERYTHING GOES PERFECTLY, but, IF flashing a rom fails and you can't boot into OS and your sdcard gets wiped out and you your backup is no longer on the device, adb can save your bacon, because you can't drag and drop files from your computer to your device when the device is in recovery. Bottom line is, it's smart to make sure that you can transfer files to your device from recovery in case of disaster.
*** I prefer to wipe the device manually (wipe > advanced wipe > select DAVLIK CACHE, CACHE, DATA, & SYSTEM <do not select internal storage>
**** some ROMs use an installed called "Aroma" that steps through the installation process and lets you choose mods as you go. If the ROM you install has aroma, you will get wipe options. Make sure to select Do not wipe because you just wiped everything above. If your ROM doesn't have aroma, you will just see the installation log flashing in the terminal window).
That's all I can think of...hope this helps and everything goes smoothly.
EDIT: If all of this works and you're able to flash the stock sense 6 ROM i linked to above and want to try a newer stock rom or maybe even insert coin, just follow the steps above again. But i would probably start with the rom i linked to because i KNOW that one will work with your current config

jollywhitefoot said:
You should be on the new partition layout, and should be able to flash a sense 6 rom without updating firmware.
Insert Coin might work, but i'm not positive about that. This stock one should definitely work: http://forum.xda-developers.com/showthread.php?t=2791725
I flashed this one when i was s-on, on hboot 2.22 and radio 1.25 without any problems. Once you're on that ROM, you can probably get s-off with Rumrunner if you want.
Here's the path I took when my device was in the state yours is in (S-On, hboot 2.22 & Radio 1.25)
- Flash TWRP 2.1.1.1 recovery
- make a full backup from TWRP
- test adb* from recovery (specifically: make sure "adb devices" returns your serial number, and that you can use "adb push <nameofROM.zip>" to your sdcard)**
- reboot into OS
- Copy the backup you just made (twrp folder on sdcard) and all other files that you don't want to lose to your computer (make sure to leave the TWRP backup on your sdcard in case you need to restore)
- Copy the sense 6 rom to your device
- Reboot into recovery
- Wipe your device*** (once you do this, your phone will not boot until you flash a working rom, or restore the backup you just made)
- Go to "Install" and find your rom's zip file on the sdcard, select it and swipe to flash ****
- After your ROM has flashed, if you don't get any errors, you can reboot your device
- That should be it...you will see a white screen with HTC on it for a little while while (sometimes as long a 5 or more minutes...or at least it seems that way sometimes) the installation finalizes (but there's no progress bar, so you just need to be patient here).
* here is more information on setting up adb if you need it: http://techbeasts.com/2013/08/26/how-to-install-adb-fastboot-drivers-on-your-windows-pc-guide/
** this is not an essential step IF EVERYTHING GOES PERFECTLY, but, IF flashing a rom fails and you can't boot into OS and your sdcard gets wiped out and you your backup is no longer on the device, adb can save your bacon, because you can't drag and drop files from your computer to your device when the device is in recovery. Bottom line is, it's smart to make sure that you can transfer files to your device from recovery in case of disaster.
*** I prefer to wipe the device manually (wipe > advanced wipe > select DAVLIK CACHE, CACHE, DATA, & SYSTEM <do not select internal storage>
**** some ROMs use an installed called "Aroma" that steps through the installation process and lets you choose mods as you go. If the ROM you install has aroma, you will get wipe options. Make sure to select Do not wipe because you just wiped everything above. If your ROM doesn't have aroma, you will just see the installation log flashing in the terminal window).
That's all I can think of...hope this helps and everything goes smoothly.
EDIT: If all of this works and you're able to flash the stock sense 6 ROM i linked to above and want to try a newer stock rom or maybe even insert coin, just follow the steps above again. But i would probably start with the rom i linked to because i KNOW that one will work with your current config
Click to expand...
Click to collapse
Ok I'm about to give it a shot, thanks!