Related
I read these forums for a couple of days before I rooted, and have read them again for this problem for about 6 hours. I am unable to figure out what my situation is, and I'd like your help. Bear with me here...
I had successfully rooted my phone and loaded Cyanogen before the Google C&D (not sure of exact version number). For some unknown reason, my phone suddenly refused to accept phone calls and would send them to voicemail. I checked and rechecked all my settings, even disabling my voicemail altogether. I also noticed that many menu items also changed at this time. My send button no longer brought up the dialer, and my home button stopped bringing the phone to the home screen. Holding the power button only yielded options for reboot and power off. Airplane mode could only be accessed through the settings menu. I decided that I should unroot the phone and start fresh with Cyanogen's new instructions.
I downloaded sappimg.nbh and followed the directions here: http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
This was successful, and when I booted again, it brought me to the screen that you get before you activate the phone. Now, I don't have a data plan, so I was unable to activate the phone with my google account. I decided I would go ahead and reroot the phone and follow the new Cyanogen directions using the original factory image first, then installing the new Cyanogen update on top of it to keep the original google apps. Here is where I discovered the problem: Holding HOME and POWER to get to recovery boot brings me to the very terrifying screen with the triangle/exclamation mark on it. At this point, while I realize there are still actions I can take, I want to make sure that this is ok before I do anything. I don't want to brick my phone, and I am already unable to get to the recovery boot.
Info:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.006 (SAPP30000)
CPLD-10
RADIO-2.22.19.261
fishscale said:
I read these forums for a couple of days before I rooted, and have read them again for this problem for about 6 hours. I am unable to figure out what my situation is, and I'd like your help. Bear with me here...
I had successfully rooted my phone and loaded Cyanogen before the Google C&D (not sure of exact version number). For some unknown reason, my phone suddenly refused to accept phone calls and would send them to voicemail. I checked and rechecked all my settings, even disabling my voicemail altogether. I also noticed that many menu items also changed at this time. My send button no longer brought up the dialer, and my home button stopped bringing the phone to the home screen. Holding the power button only yielded options for reboot and power off. Airplane mode could only be accessed through the settings menu. I decided that I should unroot the phone and start fresh with Cyanogen's new instructions.
I downloaded sappimg.nbh and followed the directions here: http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
This was successful, and when I booted again, it brought me to the screen that you get before you activate the phone. Now, I don't have a data plan, so I was unable to activate the phone with my google account. I decided I would go ahead and reroot the phone and follow the new Cyanogen directions using the original factory image first, then installing the new Cyanogen update on top of it to keep the original google apps. Here is where I discovered the problem: Holding HOME and POWER to get to recovery boot brings me to the very terrifying screen with the triangle/exclamation mark on it. At this point, while I realize there are still actions I can take, I want to make sure that this is ok before I do anything. I don't want to brick my phone, and I am already unable to get to the recovery boot.
Info:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.006 (SAPP30000)
CPLD-10
RADIO-2.22.19.261
Click to expand...
Click to collapse
you can't really brick your phone when flashing a rom, well you can, but you have to try really hard. The same thing happened to me the first time. You can flash the recovery again using fastboot, if you had an engineers spl. Since you still have the perfect spl, you will more than likely have to do the one click root again. Just reboot the phone, and you will have the stock donut rom. Downgrade to cupcake, then do the unlockr's method again.
As tazz mentioned, this is no problem - by flashing the sappimg.nbh you also flashed the recovery and lost your root.
As this is the cupcake sappimg, what you need to do now is to go on with activation, then flash the recovery again using the 1 click method and go on from there.
If you do not have a data plan, try bypassing the google activation described here
flash recovery again if u can go into fastboot mode
I believe that I have cupcake (1.5), not donut.
So, if I understand correctly, unrooting the phone means I lose the ability to go into recovery boot using HOME + POWER. I am still able to go into fastboot when pressing BACK + POWER or VOL DOWN + POWER. However, I am not clear on whether or not I will be able to flash recovery using fastboot this way. If I just load a recovery .img file on the sdcard, will I be able to use fastboot to flash it? I was under the impression that I would only be able to do this if I could use recovery boot. Also, since I most likely do not have an engineers SPL, will this work? And finally, how do I check the SPL?
I should clarify when I say check the SPL. I mean, how can I be certain that the SPL I load won't brick my phone? As far as I know, uploading a new hboot is a good way to brick it, no?
u need to root your phone again.. when u installed the SAPPIMG.nbh u unrooted your phone.. now u need to root again.. being able to fast boot doesn't mean u have root.. a unrooted phone can access fast boot...
Got it working!
I was doing it correctly, I was just unable to get it to root at first. Took 3 tries, then I was able to boot into recovery mode. Thanks for all your help!
Dear forum,
I kind of hesitated to start a thread for my problem, but after a long time I still haven't found a solution. I have contacted HTC (no answer yet), but hope to resolve my problem in meanwhile instead of waiting 1 month+ for a replacement.
I got the -by now familiar- freeze, and after rebooting it would go beyond the HTC logo, then stay stuck in a backlit black screen mode. Tried removing the battery, sim card, sd card etc. Then decided to boot into recovery (vol down + power) which worked, but any option would freeze the phone, like factory reset which I tried first.
Right now, the phone already freezes at the carrier logo, and I can't even get into recovery again (vol down + power). The phone won't respond to the key presses, and eventially boot and freeze at the carrier logo. The weird thing is that before, after a lot of trying and re-inserting the battery, it would eventually boot and work just fine for about 1 in 10 tries.
Does anyone have any ideas what I could try? Any help would be greatly appreciated!
edit: Okay, after a while I finally managed to get into HBoot again! Now what should I do to get my phone resetted/fixed? I guess it's not possible for me to flash another ROM or something as i'm not rooted. Details shown are: S-OFF, HBOOT 98.0002
can you get into recovery from bootloader?
Seems like I now consistently can boot into HBOOT. When I choose recovery, it will reboot, show the carrier logo, show the green logo with circular arrows, and then switch to the phone logo with a red exclamation mark for two seconds. Then, it shuts off. Also, when I tried that just now, it buzzed for like 6 times very fast after turning off.
On the second try, exactly the same happened: red exclamation mark, screen off, +- 6 fast buzzes.
After doing that, it doesn't respond to vol down+power or power at all. After reinserting the battery, I can get back into HBOOT
edit: it didn't want to boot into HBOOT, but now it does again. Anyhow, chosing recovery is still green logo, red logo, screen off and some buzzes. The phone doesn't show up in "adb devices" neither.
Whatever you are going to do; do not root your device as it will void your warrenty.
Is there anything else i can try doing? The situation so far:
-normal boot just stays stuck into carrier logo
-hboot->recovery gives a reboot, green logo, switch to red logo, screen off and +- 6 fast buzzes, then nothing. Needs battery reinsertion to be able to respond to vol down + power again
-hboot->factory reset just freezes on the same screen, no response, needs battery removal
-noshow in adb devices (update: show in fastboot!)
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
maxxur said:
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
Click to expand...
Click to collapse
Slow down maxxur, wait for this quesstion to be out there for long enough for someone to answer it.
Dont go on a battery pulling spree, coz that is the first and most tempting response on a frozen phone. But i hope you know what that can do to this phone...
Give the xda community some time to figure this out. Hold your ground till then. Need to go in to the theatre now. Will get back in the evening and try to figure this out.
Try running the RUU while in the fastboot menu (usb mode). Also my suggestion is not to make the process more complicated by downgrading - just reflash 1.47...
Thanks for the response guys
The RUU I found was 1.37. Could you point me to a 1.47 RUU for the 3UK network?
Also, running that RUU when in Fastboot USB mode is what I tried. The info on the RUU shows that it hangs indefinitely at "rebooting bootloader". That is expected, as when I try to manually reboot bootloader in my fastboot menu, my phone will also freeze.
I'm wondering if running a different recovery image could be of any help? Last night I tried running CWM recovery to see my options, by entering "fastboot boot recovery.img" but i'd get a "remote: not allow" error.
Have not noticed that you are not rooted!
Why don't you try the revolutionary tool? If you have luck it will restore your bootloader if it is broken (keep in mind that is not the best option because it will break you warranty). Then you will just need to flash an eng hboot and run the RUU, or better try some custom ROM
But in my opinion the best option for you is to go for a replacement rather to try yourself, since you dont have any custom software on it it has to be covered by your warranty (probably it is a faulty device to go like this from nothing).
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
maxxur said:
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
Click to expand...
Click to collapse
Of course you can if you are eager to try this. When you run the RUU, even when there is no phone connected there is a folder in your C: drive created (I assume that you are using Windows). Open your Windows Explorer and search for the rom.zip. When you have it copy it somewhere and close the RUU screen. Then if you open the RUU all the *.img files are there. You can try flashing the stock recovery or hboot or whatewer using the fastboot command. But I have to say again the best option for you is to bring the phone for a repair before you end up with something irreversible and void your warranty.
Thanks for keeping me sane on what to do with my problem Mentally, I came to the point where I'd go flash CWM recovery on my phone and try to flash that RUU rom from there, but you helped me get around that thought and now I made arrangements for HTC to come and pick it up. I'll keep you guys posted!
PS: you've got to love our desire s community, it's the best.
Cheered too early
Now HTC suddenly responds that while entering my phone in their warranty service thingy and the phone seemed to be 3G UK branded, they told me they "can't" do repairs for those.
Seriously, HTC is trying to troll me saying the inner hardware could differ between a UK and a Belgian Desire S?? Could this be true in any way?? :/
Maybe some parts are cheaper but with the same parameters...but I thought that when you have a branded phone you should seek your warrancy support from the carrier's office?!?
Sent from my HTC Desire S
Options for solution!
Option 1: Copy rom.zip (from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed) to your sd rename it to PG88IMG.zip and let m boot into hboot.
If option 1 is not ok try option 2.
Option 2: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU then after that run ruu RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed.
If option 2 not OK then there is option 3.
Option 3: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU after that run in dos/terminal fastboot flash zip rom.zip (extracted from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed)
Let me know if one of these option worked for you if not I can help you with reflashing your hboot again.
NikMel,
Thank you so much for the tips. Currently I'm trying the first HBOOT + .ZIP method. It detected it, asked me to update and is now showing a pink "Updating" sign. How long should this normally take? I have a strong feeling it simply froze again, and it really turns out to be a hardware problem.
Is that updating next to radio?
If yes it will take realy long so wait!!
Hello all, im fairly new to 'rooting' world and wish my first post wasn't on this, however, i'm not too sure where else to look for help! I believe my phone may be lost, but thought I'd ask before giving up completely. I was running ARHD 3.6.7 rom on my HTC Sensation. rooted, everything working like a charm, til last nite... I d/l and flash the ARHD 3.6.7 Hard Version Brightness Tweak from this post... http://forum.xda-developers.com/showthread.php?t=1350580. However, instead of going into recovery, I used rom manager ( I've read at times not to use this for certain things, so guessing this is one of em..noob mistake that may cost me my phone). While in rom manager, the following 2 options were checked, which I think is where I went wrong, 1) wipe data and cache 2) wipe dalvik cache. When my phone rebooted, the old 'android' boot image was showing instead of the 'Beats Audio' from the ARHD Rom. This is where I am at. The phone seems to be stuck at reloading this image over and over. I can not boot into recovery by holding the down volume and power. Any help would be greatly appreciated. Thanks
Chase79 said:
Hello all, im fairly new to 'rooting' world and wish my first post wasn't on this, however, i'm not too sure where else to look for help! I believe my phone may be lost, but thought I'd ask before giving up completely. I was running ARHD 3.6.7 rom on my HTC Sensation. rooted, everything working like a charm, til last nite... I d/l and flash the ARHD 3.6.7 Hard Version Brightness Tweak from this post... http://forum.xda-developers.com/showthread.php?t=1350580. However, instead of going into recovery, I used rom manager ( I've read at times not to use this for certain things, so guessing this is one of em..noob mistake that may cost me my phone). While in rom manager, the following 2 options were checked, which I think is where I went wrong, 1) wipe data and cache 2) wipe dalvik cache. When my phone rebooted, the old 'android' boot image was showing instead of the 'Beats Audio' from the ARHD Rom. This is where I am at. The phone seems to be stuck at reloading this image over and over. I can not boot into recovery by holding the down volume and power. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Sholdn't have wiped anything when installing a mod, you need to open your recovery and reinstall ARHD ..if you don't have the .zip on your sdcard then just take it out of the phone and put it into the computer and copy over a .zip
you need to wipe everything before installing the ROM so user the super wipe
All can be found here..
http://forum.xda-developers.com/showthread.php?t=1098849
Friend I doubt you're bricked. Id say you had a bad install. I'd reinstall and is be happy to walk you through it. So good news is you're not bricked.
Sent from my HTC Sensation 4G using XDA App
Ok, not bricked is great! However, I do have another question. I have a pretty good uderstanding of what to do once in recovery, my question is ' how do I get there?' When I hold the down volume and power buttons, I still boot to the android screen which I am currently stuck on. I have the zip files I need on my sd card, just can't get to em... Is there another way to get into recovery to wipe and reinstall? Again, thx for the help, this is most definitely a learning experience
Chase79 said:
Ok, not bricked is great! However, I do have another question. I have a pretty good uderstanding of what to do once in recovery, my question is ' how do I get there?' When I hold the down volume and power buttons, I still boot to the android screen which I am currently stuck on. I have the zip files I need on my sd card, just can't get to em... Is there another way to get into recovery to wipe and reinstall? Again, thx for the help, this is most definitely a learning experience
Click to expand...
Click to collapse
HAve you tried pulling the battery out, then turning on to recovery
I have tried pulling the battery out, pulling the sd card out, seems like no matter, still loads to android screen. While at this screen, if i hold down power, nothing, phones stays on, if i hold down vol down + power, phone reboots to same screen. Seems like getting into recovery is my real problem...
ARHD doesn't recommend the use of Rom manager if you carefuly read the flashing instructions .further than that I had a problem like that in the past with my HTC desire ,what I did was to follow the unrevoked once again and did everything from the begining eventualy I got the recovery mode and flashed my new rom.maybe be if u follow a similar procedure by reinstalling the revolutionary kit will give u the desired outcome... Maybe sounds a bit odd but it worked for me .I don't think u have anything to lose if u try .your phone isn't bricked though by any means so no worries. Good luck maye
Sent from my HTC Sensation using xda premium
Chase79 said:
While at this screen, if i hold down power, nothing, phones stays on, if i hold down vol down + power, phone reboots to same screen.
Click to expand...
Click to collapse
Do you mean you're pressing volume down and power while your phone is already on ?
K, agreed, nothing to loose, gonna give that a go.. I am having detection issues. When I connect to pc, the device 'android phone' is recognized, but I can't access any files, HTC sync, fastboot for example saying no device connected, please check connection. I assume because the phone will not go past the boot screen? Anyhow, gonna try your suggestion. Thanks!
Mercvtio said:
Do you mean you're pressing volume down and power while your phone is already on ?
Click to expand...
Click to collapse
Yes, I have done both. While the phone is off, I have pressed vol down and power with no luck. I have also tried it while the phone was on (trying anything at that point). Still only going to android boot image.
Is there another way to enter recovery if vol down + power while phone is off doesnt work?
HALLELUJA..... Reboot into recovery successful! Not sure why, but after numerous attempt, I got it. Thx for all the quick replies. Wiping and reflashing now!!
Hey chase. Good job and have a look at coredroid Rom. Beautiful and fast. 2nd charge and at 20 hours at 49% battery left with moderate use.
Sent from my HTC Sensation 4G using XDA App
I'm having this same issue, I have used super-wipe and tried reflashing no change. still sits at the 'beats audio' flash screen. When I first tried to root the phone I believe i flashed the wrong radio zip but the hboot is version 1.23.0000 radio version is 10.14.9035.01_M whenever i try to reflash hboot or radio zips i get errors usually (status 7). It still boots into hboot and recovery just fine, but I'm not sure whats wrong or how exactly to fix it, any help would be appreciated. If you need any more information just ask. Thanks
messbarger said:
I'm having this same issue, I have used super-wipe and tried reflashing no change. still sits at the 'beats audio' flash screen. When I first tried to root the phone I believe i flashed the wrong radio zip but the hboot is version 1.23.0000 radio version is 10.14.9035.01_M whenever i try to reflash hboot or radio zips i get errors usually (status 7). It still boots into hboot and recovery just fine, but I'm not sure whats wrong or how exactly to fix it, any help would be appreciated. If you need any more information just ask. Thanks
Click to expand...
Click to collapse
Did you flash an ICS rom without installing the ICS firmware first?
If this is the case, take out your sd card, copy over the ICS firmware to the root of the sd card, boot into the bootloader, and it'll walk you through updating the firmware.
it says
model id incorrect
update fail!
press <power> to reboot.
i think the radio i tried to flash was for a different phone maybe, but it was in a tutorial to root and install arhd the tutorial said you have to update the radio to use ics. any ideas?
"model id incorrect" <- you need to super CID your phone.
Do you have adb running on your computer?
my bad guys i had supercid i hadnt changed it to 11111111 did that re-wiping and flashing now thanks for the help
Problem Solution
adamgaltress said:
Sholdn't have wiped anything when installing a mod, you need to open your recovery and reinstall ARHD ..if you don't have the .zip on your sdcard then just take it out of the phone and put it into the computer and copy over a .zip
you need to wipe everything before installing the ROM so user the super wipe
All can be found here..
http://forum.xda-developers.com/showthread.php?t=1098849
Click to expand...
Click to collapse
Follow these instructions and you will get your phone back - Had the same problem and this fixed it first time
Its been a while since this last post and I have had same problem today, 2012 March,..Using Htc super tool, while phone is off, and connected to usb cable, open htc super tool, and hit 4, it will cycle and press continue until it auotmatically boots the phone into recovery screen. Hope this helps it worked for me.
HTC Sensation Stuck at boot screen..Bricked?
I had the same issue and I was able to restore and get back to my old version.
As mentioned in
HTML:
http://forum.xda-developers.com/showthread.php?t=1192300
I followed everything, but still I cant flash my device correctly.
Here are my details.
I tried to flash ARHD 6.5.3 XE
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMMC-boot
Jun 2 2011, 22:31:39
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
Please Help!!
I have an Inspire 4G and i was trying to put ENG-OFF following this steps: http://forum.xda-developers.com/showthread.php?t=855403 to run "Desire HD s easy-off.exe" gave me "Bootloader is Corrupt. DO NOT REBOOT!" (He went out alone) and I could not take him with anything, you connect to the charger and nothing, the PC and nothing, as 20 minutes after i had pressed the power button turned on the cel with the white screen and vibrating continuously approx 8min, the problem is that in the beginning it takes too ... Now every time I reboot so, and if I discharge the battery will be useless because I do not grab power when connected to the charger or the pc .....
- I can not enter the bootloader, I managed to do with the "Super Tool V3" and the recovery reinstall the ROM, I thought it would end the problem but stayed the same, takes too long to start and does not grasp the power of the charger ... .
What can i do? What is it?
If I noticed that the bootloader says "ENG-OFF" and if you step back to ENG-ON?
I greatly appreciate (and have no idea how) that can help me please .....
(sorry about my english)
You have a newer version Inspire that came preloaded with Gingerbread. I believe trying to achieve Eng-off has flashed a previous bootloader that is incompatible with your phone. Since you say you can't get to your bootloader then you will need to install the stock ATT gingerbread ROM using your PC. Get it here: http://dl4.htc.com/RUU_Ace_Gingerbr...60.25_26.10.04.03_M_release_200368_signed.exe You will then have to re-root using the Hack Kit.
rikrdoVe said:
Please Help!!
I have an Inspire 4G and i was trying to put ENG-OFF following this steps: http://forum.xda-developers.com/showthread.php?t=855403 to run "Desire HD s easy-off.exe" gave me "Bootloader is Corrupt. DO NOT REBOOT!" (He went out alone) and I could not take him with anything, you connect to the charger and nothing, the PC and nothing, as 20 minutes after i had pressed the power button turned on the cel with the white screen and vibrating continuously approx 8min, the problem is that in the beginning it takes too ... Now every time I reboot so, and if I discharge the battery will be useless because I do not grab power when connected to the charger or the pc .....
- I can not enter the bootloader, I managed to do with the "Super Tool V3" and the recovery reinstall the ROM, I thought it would end the problem but stayed the same, takes too long to start and does not grasp the power of the charger ... .
What can i do? What is it?
If I noticed that the bootloader says "ENG-OFF" and if you step back to ENG-ON?
I greatly appreciate (and have no idea how) that can help me please .....
(sorry about my english)
Click to expand...
Click to collapse
Maybe u missed the part where it said that it was not compatible with GB shipped devices. You have definetely messed your bootloader. You need to fix that first. Hit the Hack Kit IRC channel and we will lend you a hand.
http://webchat.freenode.net/?channels=#aahkSupport
Mora ntoChni
Agoattamer said:
You have a newer version Inspire that came preloaded with Gingerbread. I believe trying to achieve Eng-off has flashed a previous bootloader that is incompatible with your phone. Since you say you can't get to your bootloader then you will need to install the stock ATT gingerbread ROM using your PC. You will then have to re-root using the Hack Kit.
Click to expand...
Click to collapse
Well, i flashed via RUU with PD98IMG.zip from bootloader, i can enter to hboot only with "Super Tool V·" but Vol down + Power doesnt work..
But i'm still with the same problem, it takes 20 minutes to start...
Any other option?
Agoattamer said:
You have a newer version Inspire that came preloaded with Gingerbread. I believe trying to achieve Eng-off has flashed a previous bootloader that is incompatible with your phone. Since you say you can't get to your bootloader then you will need to install the stock ATT gingerbread ROM using your PC. You will then have to re-root using the Hack Kit.
Click to expand...
Click to collapse
Well, i flashed via RUU with PD98IMG.zip from bootloader, i can enter to hboot only with "Super Tool V·" but Vol down + Power doesnt work..
But i'm still with the same problem, it takes 20 minutes to start...
Any other option?