Database Info

Stuck with 1.33.009 after an attempted unroot of T-Mobile MyTouch

I have a T-Mobile MyTouch I purchased on Friday, which had an SPL of 1.33.006 (SAP30000). I followed the instructions in the following thread to unroot my phone:
http://forum.xda-developers.com/showthread.php?t=547133
I would have posted in the original thread, but the couple of times I've seen my issue come up, there are no answers given (or, sometimes it's "did you follow the instructions exactly?") so I didn't want to get it lost if others have the same problem. I've tried the instructions step by step (took me a while to get the GoldCard done because of a couple of inaccuracies in the instructions), but now it seems that I'm stuck with a 1.33.0009 (SAPP30000) SPL and need to install 32A ROM's - I can't seem to get it to 1.33.0005 no mater how many times I follow the instructions. And it also seems that I can't revert to a 32B situation, nor can I unroot the phone based on the last series of instructions in the Original Thread.
Has anyone else had this problem and if so, how did you fix it? Or is it unfixable? I'd like to be able to install 32B Hero ROM as only a couple of the 32A ones will install on my phone, and it's hard to tell what might be causing the slowdown (the lack of memory, or just the ROM itself). I now have Amon_RA's RAv1.2.1H ROM installed, and it works great, but it's the Hero ones I'd like to get.
Note that my main reason for unrooting was to tether the phone, but for now that goal has been set aside until I can determine how to proceed from here (although I might just give Azilink a try anyway while waiting for this to be resolved).
Any help would be appreciated.

I'm not sure if we had the same problem. I followed the instruction in installing the spl it says turn off after installing the spl.
- Once the recovery is booted wait a while
- Apply the update.zip (you are now flashing the 1.33.2005 SPL)
- Once the SPL is flashed you have to power off your device and boot it again in fastboot mode. <--I did not follow this line
after the flashing I pressed restart and let it do it's thing until a couple of restart/flashing and stucked with the vodafone bootscreen thats the time I removed my battery (just be sure it's done flashing) then go to fastboot you should see .0005 let me know if it works I'm pretty sure that's what happened to me
P.S. I believe you want to root you phone to tether right? not unroot?

jrherras said:
I'm not sure if we had the same problem. I followed the instruction in installing the spl it says turn off after installing the spl.
- Once the recovery is booted wait a while
- Apply the update.zip (you are now flashing the 1.33.2005 SPL)
- Once the SPL is flashed you have to power off your device and boot it again in fastboot mode. <--I did not followed this line
after the flashing I pressed restart and let it do it's thing until a couple of restart/flashing and stucked with the vodafone bootscreen thats the time I removed my battery (just be sure it's done flashing) then go to fastboot you should see .0005 let me know if it works I'm pretty sure that's what happened to me
Click to expand...
Click to collapse
Hey jrherras,
Thanks for that tip. I'll give it a try tonight (while possibly getting other suggestions along the way). I think I MAY have tried that, but I don't remember at which stage this happened. One time it said on the screen to reboot using the "Home+Power" reset (hard reset, I think), and re-flash the update. So I tried and got the same results.
So, just to be clear, what you're saying is at the third step above, instead of powering off the phone (by removing the battery), just choose the "reset device" option at the top of the recovery menu? Or are you suggesting to do the "Home+Power" reset? And it seems that you may have also re-flashed the SPL update a couple more times as well?

courtmagician said:
Hey jrherras,
Thanks for that tip. I'll give it a try tonight (while possibly getting other suggestions along the way). I think I MAY have tried that, but I don't remember at which stage this happened. One time it said on the screen to reboot using the "Home+Power" reset (hard reset, I think), and re-flash the update. So I tried and got the same results.
So, just to be clear, what you're saying is at the third step above, instead of powering off the phone (by removing the battery), just choose the "reset device" option at the top of the recovery menu? Or are you suggesting to do the "Home+Power" reset? And it seems that you may have also re-flashed the SPL update a couple more times as well?
Click to expand...
Click to collapse
Yes I flashed couple of times and thought I'm stucked at .0009 SPL until I decided to restart not turn off.
I pressed the 1st selection from the recovery which is "Restart device" and let it flash it self. If I'm not mistaken once you pressed restart you will see a flashing in progress and after a couple of restart when your stucked in the vodafone logo and no more flashing in progress that's the time you remove the battery to turn off After that you should have .0005 SPL pm me if it worked since I don't browse too much

Hey jrherras,
Thanks again for that info. I'll give it a try later on and update both this thread and you once I see if it does or doesn't work.
~CM

Seems that the extra reboot did the trick. I had misread the "Home+Back" to reboot as "Home+Power", and that's where my confusion set in (although the instructions in the original thread were not clear on this step). Right now, I'm flashing a 32B ROM and seeing how it goes.
Thank you very much for your help.

Evo Shift Stuck In Boot Loop Please Help!

Hello,
I have an Evo Shift stuck in the boot loop. As soon as I put the battery in all it does is reset itself to the screen with the white background and green "HTC" logo, and will keep restarting until the battery dies.
If I hold volume down and turn it on, it does go into the bootloader, but picking ANYTHING, such as recovery or factory reset, does nothing but sending it back to the HTC screen.
I have tried flashing the RUU.exe (2.27.651.2) through Fastboot USB and it completed successfully, but it just restarts right back to the HTC screen. I have also put PG06img that I found on here on the root of my card, and it will never load it up.
Are there any other solutions anyone can think of? They would be much appreciated. I see a lot of these threads for regular Evos, but not for Shifts.
The only other thing I really know about the phone is that it is:
S-On
Hboot- 0.98.0001
Radio- 1.08.00.0506
Thank you so much for all of your help!

Seems to me you aren't rooted and that's more than likely your problem, boot into fastboot and use the ruu application for gingerbread.
Sent from my PG06100 using Tapatalk

Rooster85 said:
Seems to me you aren't rooted and that's more than likely your problem, boot into fastboot and use the ruu application for gingerbread.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
While I am pretty sure I am not rooted, if you are talking about the early RUU release; 1.17.651.1, the application starts and then ends up failing in the beginning of the process. Is this what you are talking about? The drivers should be all good, the application starts to flash and then dies though. Thanks!

samcrac said:
While I am pretty sure I am not rooted, if you are talking about the early RUU release; 1.17.651.1, the application starts and then ends up failing in the beginning of the process. Is this what you are talking about? The drivers should be all good, the application starts to flash and then dies though. Thanks!
Click to expand...
Click to collapse
Use the new RUU. But make sure your SD card is formatted to a FAT32 partition. (Stock 2gig sd card and some other store boughts are not)
You can format on your computer and then place the RUU on the root of sd card again
(Bootloader won't recognize the ruu zip if not partitioned)
Sent from my Supreme Shift

notsointeresting said:
Use the new RUU. But make sure your SD card is formatted to a FAT32 partition. (Stock 2gig sd card and some other store boughts are not)
You can format on your computer and then place the RUU on the root of sd card again
(Bootloader won't recognize the ruu zip if not partitioned)
Click to expand...
Click to collapse
Ok, I just did this, everything updated fine and all completeted on the bootloader. It then said "press power to reboot." I did so, and went right back into the same boot loop. Any other ideas. I figured running this, and the RUU.exe on the computer were the sure fire ways to get this thing working again???

samcrac said:
Ok, I just did this, everything updated fine and all completeted on the bootloader. It then said "press power to reboot." I did so, and went right back into the same boot loop. Any other ideas. I figured running this, and the RUU.exe on the computer were the sure fire ways to get this thing working again???
Click to expand...
Click to collapse
So just a little information.
you said your not rooted?
So that means you have no ability to flash anything because you have no custom recovery and the bootloader isnt unlocked (S-on)
So what DID you do before it bootlooped? there had to have been something you were trying to do.
Not trying to blame anything on you at all just want to make sure we are helping the most accurate way possible

notsointeresting said:
So just a little information.
you said your not rooted?
So that means you have no ability to flash anything because you have no custom recovery and the bootloader isnt unlocked (S-on)
So what DID you do before it bootlooped? there had to have been something you were trying to do.
Not trying to blame anything on you at all just want to make sure we are helping the most accurate way possible
Click to expand...
Click to collapse
No I hear ya. I was sold the phone fairly cheap and was told "all you need to do is to reinstall the RUU, that is all that is wrong." Obviously I was skeptical, but when I checked everything out, everything looked good, and again, for the price, I knew it was a gamble. That being said, I'm sure something was tried in order to modify the phone and this is how it got like this.
I have soft bricked my old Evo 4g a handful of times and an RUU or Rom flash would always solve the problem.
Anyway, there is no custom recovery, and I'm pretty sure theres no root because it is still "S-ON," I am just trying to see if anyone here has any more info before it goes in for repair.
The only last thing I would guess you MIGHT be able to do is to install a custom recovery, but is there ANY way to do this by just being in the bootloader and using FASTBOOT USB? Any more help is greatly appreciated. Thanks!

samcrac said:
No I hear ya. I was sold the phone fairly cheap and was told "all you need to do is to reinstall the RUU, that is all that is wrong." Obviously I was skeptical, but when I checked everything out, everything looked good, and again, for the price, I knew it was a gamble. That being said, I'm sure something was tried in order to modify the phone and this is how it got like this.
I have soft bricked my old Evo 4g a handful of times and an RUU or Rom flash would always solve the problem.
Anyway, there is no custom recovery, and I'm pretty sure theres no root because it is still "S-ON," I am just trying to see if anyone here has any more info before it goes in for repair.
The only last thing I would guess you MIGHT be able to do is to install a custom recovery, but is there ANY way to do this by just being in the bootloader and using FASTBOOT USB? Any more help is greatly appreciated. Thanks!
Click to expand...
Click to collapse
It shouldn't have a custom recovery if it shows s-on.
I don't see why the RUU wouldn't work.
Honestly it doesn't sound like a softbrick- sounds like its just bricked (Which ive only heard of 1 Shift getting bricked completley)

notsointeresting said:
It shouldn't have a custom recovery if it shows s-on.
I don't see why the RUU wouldn't work.
Honestly it doesn't sound like a softbrick- sounds like its just bricked (Which ive only heard of 1 Shift getting bricked completley)
Click to expand...
Click to collapse
Make it 2! Thanks for your help though!!!

Also Stuck In A Bootloop
samcrac said:
Hello,
I have an Evo Shift stuck in the boot loop. As soon as I put the battery in all it does is reset itself to the screen with the white background and green "HTC" logo, and will keep restarting until the battery dies.
If I hold volume down and turn it on, it does go into the bootloader, but picking ANYTHING, such as recovery or factory reset, does nothing but sending it back to the HTC screen.
I have tried flashing the RUU.exe (2.27.651.2) through Fastboot USB and it completed successfully, but it just restarts right back to the HTC screen. I have also put PG06IMG that I found on here on the root of my card, and it will load it up (I'll see the blue loading bar and then the brown loading bar in the top right hand corner of the screen), but it then checks it again, and then goes back to the original screen for the bootloader.
Are there any other solutions anyone can think of? They would be much appreciated. I see a lot of these threads for regular Evos, but not for Shifts.
The only other thing I really know about the phone is that it is:
S-On
Hboot- 0.98.0001
Radio- 1.08.00.0506
Thank you so much for all of your help!
Click to expand...
Click to collapse
I'm trying to resolve a very similar problem as him, but I know of the history of my phone (since I'm the only owner), so hopefully an answer for me can assist him also.
The Story: One day, I'm playing Uno HD (downloaded from Android Market). I toss out a Draw 4, and then I see: "Google Infrastructure Failure" and a Triangle with an exclamation mark. I reset the phone, and it starts up fine. Then a few hours later, my phone randomly restarts itself into the bootloader screen after trying to reload the home screen (because the memory manager is overly aggressive).
I see no HTC Screen. It goes straight to the bootloader without any input. If I plug it to the charger from an off state, the amber light comes on, and 10 seconds later, bootloader screen. With a battery, it appears automatically after 45 seconds.
Fastboot can read my memory card just fine. It's already been re-formatted as FAT32 in my pitiful attempt to try to repair it. It's checked and read a PG06IMG file I placed on the SD Card's root, went through the entire process of reading it, but it doesn't ask me if I want to upgrade. It takes me back to the original screen. (Maybe I'm loading the wrong file).
Recovery and Factory Reset immediately restarts the bootloader after showing me the skateboarding android splash screen.
I've also tried to flash the newest stock RUU for it. (2.76.651.4), but after the RUU sends the command to start up in bootloader mode, the phone shuts off. Thus giving me the connection error.
(Maybe if someone could rewrite the .exe file to not send out the command to begin loading as if it was in the bootloader screen, it could work. I'd pay for that.)
Other Stuff:
ROM: Stock Sprint Gingerbread OTA ROM. I've been living the vanilla life. No root access. No funny stuff. Just a stock phone with apps (Third Blade, Uno HD, ASTRO File Manager, ect...)
Directly from bootloader screen:
SPEEDY XA SHIP S-ON
HBOOT-0.98.0001
RADIO-1.08.00.0506
eMMC-boot
April 11 2011, 22:32:34
Is there a way we can flash a file from the SD Card which will turn off the security and/or temp/perm root it? (forgive my noobness for such a question)
EDIT: I'm referring to a way that's outside of the adb push method. My device can't be found, and the device won't get past the bootloader screen, so that method doesn't help me too much. However, I do have the ADK Installed and the ADB Command Line works fine.

Ok .. HERE'S THE SOLUTION:
First off all if your S- ON it means you are NOT rooted
If you get stuck in a bootloop .. don't worry it can be fixed.
What you need to do is download PG06IMG.ZIP and place it on your sd card, you can access your sd card by going into recovery then mount section, then usb. This will allow you to move the file from your computer to the root of your sd card.
Once you do this be sure you back up any info you don't want to lose. Once you have the file in place, go back to fastboot ( hold vol down and power) it will read file and when it asks you to update press vol up. It will take a few minutes to update this will revert your phone back to stock but if you have an old recovery it will not do a full restore, it will only update the rom.
Once you get your phone back to working, I recommend updating your recovery by downloading Rom Manager and flashing the latest clockwork recovery. This problem happens usually due to an old recovery.
One other thing you can try if you do NOT want to reset your phone, you can try flashing a new kernal.
Sent from my PG06100 using Tapatalk

RUU won't work if your stuck in bootloop ..
Sent from my PG06100 using Tapatalk

If you want to root your phone use visionary to temp root then use shift rr .. you can then flash a custom recovery which is essential to avoid this from happening again
flylike2kites said:
I'm trying to resolve a very similar problem as him, but I know of the history of my phone (since I'm the only owner), so hopefully an answer for me can assist him also.
The Story: One day, I'm playing Uno HD (downloaded from Android Market). I toss out a Draw 4, and then I see: "Google Infrastructure Failure" and a Triangle with an exclamation mark. I reset the phone, and it starts up fine. Then a few hours later, my phone randomly restarts itself into the bootloader screen after trying to reload the home screen (because the memory manager is overly aggressive).
I see no HTC Screen. It goes straight to the bootloader without any input. If I plug it to the charger from an off state, the amber light comes on, and 10 seconds later, bootloader screen. With a battery, it appears automatically after 45 seconds.
Fastboot can read my memory card just fine. It's already been re-formatted as FAT32 in my pitiful attempt to try to repair it. It's checked and read a PG06IMG file I placed on the SD Card's root, went through the entire process of reading it, but it doesn't ask me if I want to upgrade. It takes me back to the original screen. (Maybe I'm loading the wrong file).
Recovery and Factory Reset immediately restarts the bootloader after showing me the skateboarding android splash screen.
I've also tried to flash the newest stock RUU for it. (2.76.651.4), but after the RUU sends the command to start up in bootloader mode, the phone shuts off. Thus giving me the connection error.
(Maybe if someone could rewrite the .exe file to not send out the command to begin loading as if it was in the bootloader screen, it could work. I'd pay for that.)
Other Stuff:
ROM: Stock Sprint Gingerbread OTA ROM. I've been living the vanilla life. No root access. No funny stuff. Just a stock phone with apps (Third Blade, Uno HD, ASTRO File Manager, ect...)
Directly from bootloader screen:
SPEEDY XA SHIP S-ON
HBOOT-0.98.0001
RADIO-1.08.00.0506
eMMC-boot
April 11 2011, 22:32:34
Is there a way we can flash a file from the SD Card which will turn off the security and/or temp/perm root it? (forgive my noobness for such a question)
EDIT: I'm referring to a way that's outside of the adb push method. My device can't be found, and the device won't get past the bootloader screen, so that method doesn't help me too much. However, I do have the ADK Installed and the ADB Command Line works fine.
Click to expand...
Click to collapse
Sent from my PG06100 using Tapatalk

Also if your phone can't be found its b/c you need to put it into diag mode .. ##DATA .. if you need more help google
tech-9 said:
If you want to root your phone use visionary to temp root then use shift rr .. you can then flash a custom recovery which is essential to avoid this from happening again
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Sent from my PG06100 using Tapatalk

For the thread starter, the person that sold you the phone probably tried writing to the system partition with s-on. Since you can get to the bootloader, see if you can get into recovery. If you can, recovery can be seen in adb, even the stock recovery. From there, gingerbread root, plenty of guides out there, make sure you flash the misc.img, download the froyo downgrade zip (that pgimg09.zip or something like that, just search for it, but not with the numbers I just gave, those are made up.)
From there either flash the gingerbread zip or ruu, and goon with a unrooted life. Or follow one of the many guides to froyo root, and live the life of the rooted. Your choice.
For the second person with a similar issue, the same method will work for you (assuming you can get to recovery), gingerroot, froyo downgrade, and since you like being unrooted, just ruu or zip back to gingerbread.
Solution found enjoy, and just think, if root hadn't been discovered for gingerbread, you would be screwed right now, make sure to thank otaking.

I have the same boot loop problem. I tried using the PG06IMG.zip file and fastboot/bootloader screen says I have the wrong image. It's most likely because it's for 2.2 and I have 2.3. I also don't have any recovery. Is there a PG06IMG.zip for 2.3 or the like?

similar problem here
i'm fairly certain i tried recovery with the wrong or corrupt or incomplete PG06IMG.zip on my first attempt. i got the right one from here http://forum.xda-developers.com/showthread.php?t=1255474
i ran it, says update installed, but when i reboot i still get the loop
from bootloader
SPEEDY XE SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot
Nov 15 2010, 13:19:54

zdavidzz said:
i'm fairly certain i tried recovery with the wrong or corrupt or incomplete PG06IMG.zip on my first attempt. i got the right one from here http://forum.xda-developers.com/showthread.php?t=1255474
i ran it, says update installed, but when i reboot i still get the loop
from bootloader
SPEEDY XE SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot
Nov 15 2010, 13:19:54
Click to expand...
Click to collapse
Try downloading the zip again and re run it. Possibly a bad download?
Sent from my PG06100 using Tapatalk

also adb is telling me device not found. i think i might have to factory reset. is that crazy?
---------- Post added at 01:31 PM ---------- Previous post was at 01:27 PM ----------
and... that didn't help

i'm downloading the zip again right now.
since i have s-on, will i be able to install it though?
i can get the file on the root of the sdcard with an adapter since i can't push from adb. and i can't temp root the phone because if i try a normal reboot i get this stupid boot loop. is there a way to get s-off through hboot on the phone?
i don't know why i didn't notice that first file was messed up, it was only 6MB.

[Q] [URGENT] Accidentally Factory Reset/HBOOT Phone... Files still there o_O

I saw somewhere for some tutorial to get into HBOOT to see if you have an S-ON or S-OFF phone. Then I thought I read you can get that by holding the power and volume-down. I did that, and it brings me to the screen that I saw when I first bought my phone a few months ago. I turned it off and back on, and I still get that. I went through it, and now it just looks like a brand new phone (even after multiple restarts)
I was really upset, but then I plug it into my computer and enabled USB Mass Storage, and browsed the files on my computer. It looks as though all my files are still there :O My SD card is perfectly in-tact too...
Is there any way to get it back to the way it was without having to sync with Google then try to put in all my information and stuff again? Is this like temporary or is there a recovery feature or something? I'm kinda freaking out right now, please help me!!

Try holding power and volume down a bit longer after the boot screen appears. See if that brings you to recovery.
Sent from my LG-P999 using XDA App

Do you have stock recovery or Clockworkmod installed? It sounds like you have stock recovery and if you bootup with volume down + power the stock recovery does a factory reset of the phone. There is no way to get it back to how it was unless you did a backup of your NAND in Clockworkmod recovery. You just have to start over from scratch as the phone is now back to square one. BTW, the hboot thing is not for our phone. Where did you see that thread? My Nexus One can do that but my G2X cannot. As far as I know, we cannot get into hboot on this device. Only recovery and software download modes (like fastboot but not same as fastboot on other devices). Also, LG never locks their bootloaders as a matter of company policy. So S-OFF is set at the factory.

As others have said, you just did a factory reset on your phone which resets all settings and user data and apps to its factory condition. A factory reset doesn't touch your sdcard so that's why those files are still there. With stock recovery there is no way to go back to the way your phone as set up. If any apps or settings were backed up to Google's servers then those should sync back to your phone. If not then you just need to start from scratch.
jboxer mentioned clockworkmod recovery. I think everyone here would recommend you install that to replace stock recovery. One of its features is the ability to create a FULL backup of your phone including all system apps, user-installed apps, settings, messages, etc. Think of it as a snapshot of your system that you can revert back to at any point. If you're interested check out tga gunmann's one-click recovery flasher thread in the development section. Read thoroughly any instructions and don't hesitate to ask for help if you get stuck.

jboxer said:
Do you have stock recovery or Clockworkmod installed? It sounds like you have stock recovery and if you bootup with volume down + power the stock recovery does a factory reset of the phone. There is no way to get it back to how it was unless you did a backup of your NAND in Clockworkmod recovery. You just have to start over from scratch as the phone is now back to square one. BTW, the hboot thing is not for our phone. Where did you see that thread? My Nexus One can do that but my G2X cannot. As far as I know, we cannot get into hboot on this device. Only recovery and software download modes (like fastboot but not same as fastboot on other devices). Also, LG never locks their bootloaders as a matter of company policy. So S-OFF is set at the factory.
Click to expand...
Click to collapse
is it 100% that G2x comes unlocked from factory???

akaSurfer said:
is it 100% that G2x comes unlocked from factory???
Click to expand...
Click to collapse
The bootloader is unlocked. I'm assuming you're thinking of being SIM unlocked.
Sent from my amazing G2X running Bionic Reloaded v1.2.1

Bootloader unlocked always on any LG phone. LG company policy is to never lock a bootloader.
Sim locked from the factory. You need an unlock code to use a sim from another carrier. I sell them cheap and they are even cheaper on eBay. Once sim unlocked it is permanent and you never do it again.

[Q] Problems of engineering menu HBOOT HTC Inspire 4G

Has bought from the USA of HTC Inspite 4g (AT&T). Wanted to receive Root, S-OFF, Rom manager with ClockworkMod. Has started to do to change an insertion. Has received goldcard. After an overload phone has started to change an insertion. This process proceeded 2 hours (in the end of process there was a black screen). I have decided to overload phone. Has stopped process. After that problems have begun. Root, S-OFF, Clockworkmod I have received. But after reboot of phone it does not work about 10 minutes. 5 minutes at it absolutely black screen, then the white screen with an inscription of HTC simultaneously work 3 minutes the motor, loading of 2 minutes then begins. Process of switching-on or reboot of phone proceeds 10 minutes. Tried to replace an insertion once again. After that changes nothing. Did before setting of an insertion full surep wipe. It has not helped. I still have a problem. I want to enter into engineering menu HBOOT. I push down+power. I wait for 5 minutes (phone so is overloaded). I enter in HBOOT, but thus buttons (volume up and down, power) any more do not work. As to me to receive normal phone. I can not HBOOT make in it recovery. Where to me to take for HTC INspire 4G (AT&T) PD98IMG.zip. Also help me with the instruction. How to apply this file in RECOVERY.

I'm having a hard time with your English (or is it just fed into google translate?).
It looks like you installed the ENG hboot on a later model device that is incompatible.
You need to get it to boot (it will eventually) and put the newer hboot back on it. You can do this through ADB from a console. Here are the instructions:
http://paste.pocoo.org/show/495273/

@ Gene Poole
I had a hard time with his English too, but I understand exactly what he is saying because I did the same thing. I will try to re-explain it and hopefully someone can help us out.
In a nutshell, it sounds like we both flashed an Engineering HBoot starting with a stock US ATT Inspire 4G that came with Gingerbread. Specifically, what I did was I followed a guide on Cyanogenmod's wiki for the Inspire 4G which gave direction to downgrade to Froyo, root, and setup to use eng hboot. This apparently was a huge mistake. After the downgrade, when rebooting or powering on the phone, nothing would happen for a long time (black screen for 5 - 10 minutes, i.e. phone was off), then, screen would turn on with white background and HTC logo and phone would vibrate non-stop for several minutes, and eventually, phone would turn on. After the downgrade and making it to the home screen, I copied CM7 zip on to the SD card and rebooted into recovery via adb. Same exact weird process happened with phone being off for several minutes, then vibrating, then eventually i made it to cwm recovery. After installing CM7 and rebooting, same crazy startup process and made it into CM7 home screen.
I was hoping once CM7 was installed that the crazy startup process would disappear but it didn't. I saw afterwards in a CM forum that this happened to someone else and they had asked if the wiki could be updated to point to the Ace hack kit guide to rooting the Inspire 4g (which mentions that eng hboot shouldn't be used with the phone I had as configured). I then rebooted into bootloader via adb and after crazy startup and fastboot did not work at all (fastboot devices returned nothing). Further still, no buttons work in hboot at all (Vol Up, Vol Down, Power).
At this point, I could still get into the phone, but I wanted to try to undo everything I did and start over using the Ace hack kit. I then tried to use the Ace hack kit to unroot the phone by using the ATT GB RUU. The process seemed to go pretty far, but after a reboot, the phone never came back, and that's where I am currently. If I start the phone, it does crazy startup but never fully boots...stays on white HTC screen forever...which means I can't use adb (to my knowledge). I was able to get to hboot by putting elastics around volume down button and waiting a very long time, but it looks like hboot is still the eng hboot because none of the buttons work and I can't use fastboot. I was hoping that as part of RUU flashing that hboot would be restored to original one. I put the RUU (PD98IMG.img) on SD card, but again I can't get to it because buttons don't work.
So, it sounds like spv4 above is in a very similar boat. I have no idea what else to try. Only thing I can think of is if it's possible to somehow modify an RUU to start automatically when getting to hboot without any user input.
If anyone has any suggestions, I am more than willing to try anything. Thanks very much.
EDIT: So, as I was typing this post earlier, I had been "sitting" in hboot the whole time. When I was done, I looked at phone and PD98IMG.zip was been applied to phone automatically! Don't know if this was common knowledge or not, but everything updated OK. When it was done, hitting the power button to reboot didn't work, but I just removed battery and when putting it back in, phone booted normally back to what looks like stock RUU. Hopefully this info helps someone else.

JayB059 said:
@ Gene Poole
EDIT: So, as I was typing this post earlier, I had been "sitting" in hboot the whole time. When I was done, I looked at phone and PD98IMG.zip was been applied to phone automatically! Don't know if this was common knowledge or not, but everything updated OK. When it was done, hitting the power button to reboot didn't work, but I just removed battery and when putting it back in, phone booted normally back to what looks like stock RUU. Hopefully this info helps someone else.
Click to expand...
Click to collapse
Great! Glad you got it back, but you could have saved a lot of time.
The main problem is that the ENG hboot (or pre-GB hboots) doesn't recognize something in the hardware of the new phones. The end result is that the hboot runs at about 50x slower. It eventually gets booted, and once booted to an OS (either the main OS or the recovery OS) it runs fine since hboot has exited and passed control to the OS. So anytime hboot is in control, things crawl at a snail's pace.
Because the OS runs fine and hboot has exited, it is possible to overwrite the hboot partition from the booted OS. That's what you are doing in the instructions that I posted a few posts back. Once the correct hboot is installed, all is fine.
I agree that someone needs to update the cyanogenmod wiki. It's way out of date.

I'm currently experiencing the same problem.
I followed the instructions on how to downgrade using a goldcard, successfully rooted and i also flashed TrickDroid on it, but every time i turn the device on i have to hold the power button for 20 seconds and wait 10 minutes till the HTC logo appears, then it takes 2 minutes vibrating and i seriously can't deal with this.
can you please tell me how to fix this?

Revolver95 said:
I'm currently experiencing the same problem.
I followed the instructions on how to downgrade using a goldcard, successfully rooted and i also flashed TrickDroid on it, but every time i turn the device on i have to hold the power button for 20 seconds and wait 10 minutes till the HTC logo appears, then it takes 2 minutes vibrating and i seriously can't deal with this.
can you please tell me how to fix this?
Click to expand...
Click to collapse
Find the fix in the guide in my signature....you need to have basic knowledge of adb commands. If you need further help just let me know. :good:

Moved to Q & A section.
Sent from my Galaxy Nexus using Tapatalk 2

[Q] Help please! Unrooted phone stuck in a boot loop!

Hello, friends at XDA!
My dad has a MyTouch 4G Slide. I didn't want to root it because, ironically, I wanted him to have better support and not end up with a bunch of questions from T-Mobile, should he ever need support. I'm now regretting that decision; his future devices will be rooted out of the box...
The phone, in its current state, will get as far as the splash screen. It will sit there for about 20 seconds, and then turn the screen off. After another ten seconds or so, the phone goes back to the splash screen again.
I can get myself into the bootloader, which is still S-ON. That works reliably, but it's still a bit of a dead end. It checks for a baseband update on the phone, and upon not finding an applicable file on the SD card, spits me back into the fastboot menu. Naturally, I went for the recovery environment. I was able to get to it last night, but even that was a bit shallow in that I got to the red triangle screen, but no menu options were presented. Still, I figured that the recovery environment would allow me to run Unrevoked or similar, but when I came home the phone was camping out on the "waiting for device..." screen, to no avail.
My goal was to root in order to install a recovery environment; I know that ClockWorkMod and TWRP both allow for data to be backed up from within the recovery environment. There are call logs and contacts (no, they're not synced with Exchange or Google) that would be greatly appreciated if I could recover before I perform a factory reset as T-Mobile has instructed me to do.
Is there a way I can flash a recovery environment onto this phone using only the access provided by the phone's search for a baseband update from the bootloader?
Thank you for your time and assistance in this matter.
Joey

Unfortunately no, if you can't boot to os and have stock recovery then you have no adb access which means chances of recovering any data is nil
The red triangle is stock recovery, some combo of buttons (like volume up and down) will bring you options but I forget which ones
Hopefully a factory reset will bring your phone a live as you need to get to the os just to unlock your bootloader so you can flash a custom recovery and root the phone
Sent from my Nexus 4 using xda premium

I always root my phone so I'm not sure but,
You can try to start the device by pressing the power and volume - key at the same time.
Then connect to the pc and try the toolkit.
Maybe others can comment if this wil work.
Sent from my HTC One X using xda app-developers app

No Solution
Hey guys,
by some miracle I managed to get the phone working JUST long enough to run a MyBackup Pro task on it; T-Mobile performed a warranty swap on the phone. There was no consistent solution to it though, but thanks for the input everyone.
Joey