Database Info

{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] Stuck at boot loader, reboots to recovery

Hi all,
I'm trying to help a friend update his Sensation to bruce2728's CM10 beta. I started from scratch on an updated-to-4.0.3 device with this phone and have done a fair amount of research. So far, I have done the following:
1.) Unlocked my boot loader via HTCDev
2.) flashed a custom recovery via fastboot - it's CWM-based 6.0.0.0. I can boot into recovery and back up the ROM and restore it
3.) Rooted with the CWM-flashable SuperSU 0.9.6 and verified root.
4.) used the JuopunutBear method to enable S-OFF. This is verified by booting to the boot loader, it says S-OFF and hboot version 1.27.1111
5.) Flashed a custom ROM
And #4 is where I run into problem.s I started with the CM10 beta mentioned above. It seems to install OK, and then I install G-apps, wipe data/cache, and reboot. I get to an htc logo and then it goes black and boots into recovery automatically. Tried wiping /system along with another wipe of data/cache and same result.
Thinking I had a bad download, I re-downloaded. Same results
Well maybe his Sensation is screwy, I wonder, so I grab the official CM9.1 release. Exact same procedure, exact same results.
So now I'm wondering, what can I do? Right now it's back to running the stock but rooted ROM. So it's not the end of the world. Just trying to figure out what I did wrong or what I can do to fix it. Should I get the official 5.0.2.0 or touch 5.8.0.9? I see both of those on the ClockworkMod ROM manager website, and I own ROM Manager Premium, so I can do all that if need be. Thanks in advance.

You might want to try 4ext recovery it is probably the most used recovery for the sensation. Then wipe every thing except sd . Then flash the ROM then gapps. But make sure you have a working nandroid first.
Sent from my HTC Sensation using xda app-developers app

I do have a working Nandroid. I'll check into 4EXT, as well. Thanks for the assist.

Will you think less of me if I pay $2.82 for the automated installer? :lol:
No, I'm not going that route, just wondering.
edit 10:01pm Central - that did it. Booted into bruce2728's CM10 beta. Sweet!

[Q] 1.85 rooted to scottsrom JB rooted

Ok, I know this is probably already all documented somewhere, but the problem is, there is also lots of out of date info, and I'm not sure how to tell which info is current, and which isn't. This is my first Android phone, so I'm not completely up to speed on the meanings of everything.
I have an AT&T (evita) HOX. Its on 1.8.5 stock, and is rooted. I also set supercid some time ago, in preparation for unlocking it. I didn't proceed with the unlock at that time because I wasn't yet comfortable that everything I wanted backed up was backed up, and everything said unlock would wipe all user data.
I believe I have backup under control now, and I'd like to get to where I can put the "Scottsroms" rooted JB on, and do whatever I need to ensure that I can keep root. I want to stay as close to stock as possible, but with root, and that seems to be the best path for that.
I've been doing a bit of reading (including stuff linked from the rollup thread) and I have some questions I haven't been able to answer.
- Do I need to unlock the BL in order to get S-off? Or, if I S-off, do I not need to unlock the bootloader?
- I see the note about htc blocking supercid unlocking and using all 2's instead - is this still valid?
- I had read CWM didn't support this phone, but now I see something that contradicts that.
Basically, while I understand that there are no guarantees, I'd like to at least avoid doing things that are KNOWN not to work.
FWIW, I am a long time linux user. I have the Android sdk installed with adb and fastboot programs... I'm very comfortable at the command line.
If anyone can suggest what the recommended procedure is, which steps I need, which I should avoid, which info is current, which is out of date, I'd be very thankful.
If more info from me is needed, just let me know...

Megadave123 said:
Ok, I know this is probably already all documented somewhere, but the problem is, there is also lots of out of date info, and I'm not sure how to tell which info is current, and which isn't. This is my first Android phone, so I'm not completely up to speed on the meanings of everything.
I have an AT&T (evita) HOX. Its on 1.8.5 stock, and is rooted. I also set supercid some time ago, in preparation for unlocking it. I didn't proceed with the unlock at that time because I wasn't yet comfortable that everything I wanted backed up was backed up, and everything said unlock would wipe all user data.
I believe I have backup under control now, and I'd like to get to where I can put the "Scottsroms" rooted JB on, and do whatever I need to ensure that I can keep root. I want to stay as close to stock as possible, but with root, and that seems to be the best path for that.
I've been doing a bit of reading (including stuff linked from the rollup thread) and I have some questions I haven't been able to answer.
- Do I need to unlock the BL in order to get S-off? Or, if I S-off, do I not need to unlock the bootloader?
- I see the note about htc blocking supercid unlocking and using all 2's instead - is this still valid?
- I had read CWM didn't support this phone, but now I see something that contradicts that.
Basically, while I understand that there are no guarantees, I'd like to at least avoid doing things that are KNOWN not to work.
FWIW, I am a long time linux user. I have the Android sdk installed with adb and fastboot programs... I'm very comfortable at the command line.
If anyone can suggest what the recommended procedure is, which steps I need, which I should avoid, which info is current, which is out of date, I'd be very thankful.
If more info from me is needed, just let me know...
Click to expand...
Click to collapse
Finish unlocking bootloader
Flash recovery twrp 2.3.3.1 or lower being higher versions have mount and wipe bugs.
Backup your current Rom via recovery.
Copy Rom of choice to sd card
Wipe everything except sd card. Wipe cache,dalvik, system, factory reset.
Flash Rom.
If you are on hboot 1.14 or higher you will need to extract boot.img from Rom.zip and flash via fastboot, flash boot boot.img
Good luck
Sent from my HTC One X using xda app-developers app

31ken31 said:
Finish unlocking bootloader
Flash recovery twrp 2.3.3.1 or lower being higher versions have mount and wipe bugs.
Backup your current Rom via recovery.
Copy Rom of choice to sd card
Wipe everything but sd card, cache,dalvik, system, factory reset.
Flash Rom. If you are on hboot 1.14 or higher you will need to extract boot.img from Rom.zip and flash via fastboot, flash boot boot.img
Good luck
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Regarding unlocking - can I do it with supercid set, or do I need to change to all 2's ?
Should I do s-off?
I'm on whatever versions of everything are stock for a device shipped with 1.85 - ok, the bootloader screen says hboot is 1.09.0000
I'll search around but are there docs on the specific steps for flashing roms?
BTW, thanks for the quick reply...

Hit install from recovery pick Rom and flash.. don't worry about s-off being on hboot 1.09 u can flash whatever from recovery. Htcdev has 1111111 blocked I think if it is use all 2's
Sent from my HTC One X using xda app-developers app

FWIW supercid seemed to work for unlock just fine...

31ken31 said:
Flash recovery twrp 2.3.3.1 or lower being higher versions have mount and wipe bugs.
Click to expand...
Click to collapse
Ok, looking for a bit of an expansion on this, and possibly some second opinions?
Looks like TWRP is up to 2.5.0.0 now, and the changelog shows a number of bugfixes since 2.3.x
Goomanager puts 2.5.0.0 on by default, I installed ROM Manager and it puts CWM..
The rollup page on the HOX says CWM officially supports it now..
The ROM I want says CWM "not supported" - I'm wondering if that is a holdover from when CWM didnt support HOX..

Megadave123 said:
Ok, looking for a bit of an expansion on this, and possibly some second opinions?
Looks like TWRP is up to 2.5.0.0 now, and the changelog shows a number of bugfixes since 2.3.x
Goomanager puts 2.5.0.0 on by default, I installed ROM Manager and it puts CWM..
The rollup page on the HOX says CWM officially supports it now..
The ROM I want says CWM "not supported" - I'm wondering if that is a holdover from when CWM didnt support HOX..
Click to expand...
Click to collapse
It's says bugs fixed but it's not fixed.. I don't recommend cwm for this device. Go to twrp website and download 2.3.3.1 and flash it
Sent from my HTC One X using xda app-developers app

[Q] Custom Roms not working

Hello, long time reader, first time poster. I know about rooting, and installing roms and all that good stuff (had a galaxy s2 but odin bricked it). So I'm new to the sensation, and it's quite different from my previous device. My problem is that when I install a custom rom, the phone will boot and all about after about 30 seconds will freeze and restart.
Okay so these are the steps that I followed:
-Used the KGS Utility and chose "s-off"
-Followed all the prompts everything worked out fine.
-Following that I used it to install a custom recovery.
-Followed the prompts everything worked fine.
-Then I used Revolutionary CWM to flash SuperUser.
-App was there on reboot.
-Then I downloaded the AOKP "Initiate Your Swagger"[4.1.2] Rom
-Put it on my SD card and flashed it (after wiping and backing up)
-When the phone boots the setup wizard starts.
-I follow the prompt and when it gets to "Just a sec" the phone freezes then restarts.
Don't know what the problem is here.
I get the same problem when trying to flash CM10. The phone will boot, but then after 20-30 seconds will reboot.

kojimin said:
Hello, long time reader, first time poster. I know about rooting, and installing roms and all that good stuff (had a galaxy s2 but odin bricked it). So I'm new to the sensation, and it's quite different from my previous device. My problem is that when I install a custom rom, the phone will boot and all about after about 30 seconds will freeze and restart. I also noticed that there is no signal in custom roms either. Don't know what I'm doing wrong here. I used an all in one tool to do s-off, and install a custom recovery. Then I rooted it. Then I started trying to install custom roms but they don't seem to work. What am I doing wrong?
Click to expand...
Click to collapse
Be VERY specific and give a step by step detail of what you are doing to install. Give WAY more detail than you have. And put the detail in a list, not a giant paragraph.
Then we'll look at it and see what's missing.

Skipjacks said:
Be VERY specific and give a step by step detail of what you are doing to install. Give WAY more detail than you have. And put the detail in a list, not a giant paragraph.
Then we'll look at it and see what's missing.
Click to expand...
Click to collapse
Sorry about that. Edited my first post. I hope that is enough.

When you say it boots for 20 seconds, what exaclty for you mean.
Does it just replay the boot animation over and over? Or does it actually bring you to a home screen with the status bar and everything for 20 seconds before the reboot? That's a very important difference in diagnosing this one.
Also try installing 4EXT recovery. CWM has been known to cause weirdness with AOSP roms. Plus you may have an older version of CWM thatcan't properly install the newer roms. If you used a .zip in bootloader to flash CWM yuou probably had an older version. I have a special place in my heart for CWM too, but 4EXT is just so much better for the Sensation. (Different recoveries ar ebetter or worse on different devices.)
If you properly installed superuser on your stock rom that you have a nandroid backup for, installing 4EXT is super easy. Just restore the nandroid, which should boot up without problems, download the 4EXT app from the play store, and use the app to install teh latest version of the recovery. No need for ADB or flashing in bootloader. Then try a full wipe and fresh install of AOKP from 4EXT.

Skipjacks said:
When you say it boots for 20 seconds, what exaclty for you mean.
Does it just replay the boot animation over and over? Or does it actually bring you to a home screen with the status bar and everything for 20 seconds before the reboot? That's a very important difference in diagnosing this one.
Also try installing 4EXT recovery. CWM has been known to cause weirdness with AOSP roms. Plus you may have an older version of CWM thatcan't properly install the newer roms. If you used a .zip in bootloader to flash CWM yuou probably had an older version. I have a special place in my heart for CWM too, but 4EXT is just so much better for the Sensation. (Different recoveries ar ebetter or worse on different devices.)
If you properly installed superuser on your stock rom that you have a nandroid backup for, installing 4EXT is super easy. Just restore the nandroid, which should boot up without problems, download the 4EXT app from the play store, and use the app to install teh latest version of the recovery. No need for ADB or flashing in bootloader. Then try a full wipe and fresh install of AOKP from 4EXT.
Click to expand...
Click to collapse
It boots up to the homescreen (with no signal) then it reboots.
I will try 4EXT and post my results. Thanks for your help thus far!
EDIT: Tryed installing 4EXT now when I try to boot into recovery it shows the HTC spash screen, then it reboots back the homescreen. So I think my recovery is gone.
EDIT 2: So I got the 4EXT recovery installed. But the ROMs are giving me the same issues (no change). I also noticed as before, when the custom roms boot there isn't any cellular signal.

kojimin said:
It boots up to the homescreen (with no signal) then it reboots.
I will try 4EXT and post my results. Thanks for your help thus far!
EDIT: Tryed installing 4EXT now when I try to boot into recovery it shows the HTC spash screen, then it reboots back the homescreen. So I think my recovery is gone.
EDIT 2: So I got the 4EXT recovery installed. But the ROMs are giving me the same issues (no change). I also noticed as before, when the custom roms boot there isn't any cellular signal.
Click to expand...
Click to collapse
Update the firmware.. You are on gingerbread firmware (revolutionary soff worked for you means you are on GB) and it won't work on ics/jb roms
Check the firmware thread by kohr-ah in sensation development section and flash universal 3.33 firmware
It will solve your rom problems
Sent from my HTC Sensation 4G using xda premium

ganeshp said:
Update the firmware.. You are on gingerbread firmware (revolutionary soff worked for you means you are on GB) and it won't work on ics/jb roms
Check the firmware thread by kohr-ah in sensation development section and flash universal 3.33 firmware
It will solve your rom problems
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
it was the firmware! I just updated to 3.33, and 4.1.2 "Initiate your swagger" booted up completely. Thanks for your help :good:

Awesome reply mate :
Sent from my HTC Sensation XE with Beats Audio using xda premium

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