Related
I had the Iphone rom and romupdated it with the 8310 raio only rom. Now it only flashes the splashscreen and it turns off. I can't even activesync it to reflash the rom. What can I do??? Please help.
jacknjill said:
I had the Iphone rom and romupdated it with the 8310 raio only rom. Now it only flashes the splashscreen and it turns off. I can't even activesync it to reflash the rom. What can I do??? Please help.
Click to expand...
Click to collapse
can you still get to bootloader?
No more bootloader screen, just a blank white screen.
I had the bootloader screen b4 and tried to reflash it, even though flash was successful, it still turns off after splash screen. So I tried one of the Qtech bootloader roms and flash that, now it's worse than before. I only get a blank white screen when I load the bootloader.
jacknjill said:
No more bootloader screen, just a blank white screen.
I had the bootloader screen b4 and tried to reflash it, even though flash was successful, it still turns off after splash screen. So I tried one of the Qtech bootloader roms and flash that, now it's worse than before. I only get a blank white screen when I load the bootloader.
Click to expand...
Click to collapse
i also got the problem with my sda, it also happened while flashing, do u already found a solution
Guys, are you speek about one subj? Bootloader mode is activated when you start your device with camera button pressed. There is NO white screen - in bootloader mode OS is NOT loading at all! But - you can start re-flashing process as usual
If it works, I recommend you to flash back your native ROM and then check the device. If everything is fine - you know what to do If not - let's continue thread...
And one more thing - are you sure, that your SDA is based on Tornado platform? AFFAIN SDA has two reincarnations - one of them is based on Typhoon platform, other one - on Tornado one. There are a LOT of cases, when people flased Tornado ROM to the first one and had a dead device after it Be VERY carefull!!! And read this thread http://forum.xda-developers.com/showthread.php?t=288498
ZlydenGL said:
Guys, are you speek about one subj? Bootloader mode is activated when you start your device with camera button pressed. There is NO white screen - in bootloader mode OS is NOT loading at all! But - you can start re-flashing process as usual
If it works, I recommend you to flash back your native ROM and then check the device. If everything is fine - you know what to do If not - let's continue thread...
And one more thing - are you sure, that your SDA is based on Tornado platform? AFFAIN SDA has two reincarnations - one of them is based on Typhoon platform, other one - on Tornado one. There are a LOT of cases, when people flased Tornado ROM to the first one and had a dead device after it Be VERY carefull!!! And read this thread http://forum.xda-developers.com/showthread.php?t=288498
Click to expand...
Click to collapse
so in this case, it seems like it's mine, just got a white screen and no bootloader mode
I would be lucky if I can still get into bootloader mode which means there is life left. Now, all I get is a white screen on the Tornado( it's a T-mobile SDA-silver color with bump). I am looking to see if the dealer would be able to revive it. I got a MDA now
About get into bootloader there's enough hints from peoples above. Simply hold camera button while you press the power button, and soon you will see a three color stripped screen, without normal booting splash like "DOPOD". Then you'll be able to flash as you like with RUU of MTTY.
I'm just guessing you've been flashed a Radio version over 02.00.09. As I know, you have to upgrade your IPL version to 2.00 as well as a SPL upgrade to version 2.00.00, for the new RADIO to work. Just a hint you may not noticed.
there's nothing you can do. I had similar experience, went to bunch of services, no one could fix it.
Some one can repair it by "change the code lib", I don't know how to say it in english. But apparantly someone in my city can do it without touch your phone.
ccl13 said:
Some one can repair it by "change the code lib", I don't know how to say it in english. But apparantly someone in my city can do it without touch your phone.
Click to expand...
Click to collapse
That means I have to wait till next year when I head to Guangzhou to do it then.
hi,
Ive recently rooted my phone with no problems using the ace hack kit. i tried flashing the newest andriod revolution hd rom and was having problems with the superuser app force closing and the phone wasnt giving me root privledges. i decided to try and reroot the phone using the ace hack kit. (i realize this was my mistake). it stopped in the middle of the process. so i had to pull the battery. when i tried turning the phone back on the screen was black for about 6 or 7 mins. no vibrations or leds to indicate the phone was on. then the htc white screen comes on and the phone vibrates for 2 or 3 minutes straight and proceeds to come on. Ive tried to flash other roms using cwm recovery and itll load what ever rom i choose but i cant get into the hboot or anything and it does the the black screen everytime along with the vibration. is there anyway to fix this? ive tried over and over to boot into recovery through usb but it doesnt work.
so ive done a little research, could this be a eMMC problem? if so is it fixable... And if not would replacing the hboot help?
You've got a bad or corrupt hboot. The wrong hboot (ENG hboot included in a short-lived version of the hack kit on the newest run of Inspires) or a corrupt hboot from an interrupted hack kit run.
Thanks for the help. I tried replacing the eng hboot with the link provided on freenode and it work.
After a failed attempt at running the ace hack kit (could only get into hboot), and an ever worse failed attempt at restoring to a stock rom (my stupid mistake), I am seeing the same signature as jbryancs.
Would you share the link and instructions for replacing the hboot? Any assistance is much appreciated.
wleven said:
After a failed attempt at running the ace hack kit (could only get into hboot), and an ever worse failed attempt at restoring to a stock rom (my stupid mistake), I am seeing the same signature as jbryancs.
Would you share the link and instructions for replacing the hboot? Any assistance is much appreciated.
Click to expand...
Click to collapse
really? so jumping into the IRC channel is not your best move as instructed to the OP?
I was hoping not to disturb the IRC, but I will jump in tomorrow. Just for background, here's a rough list of what I've done and what I'm seeing now.
Setup: Linux Mint 11 (Ubuntu Derivative) Clean Install for ACE Hack Kit, WinXP for the rest.
1. Ran ACE Hack Kit first time -> stalled early in process
2. Rebooted phone and everything appeared normal
3. Rac ACE Hack Kit second time -> completed process, but noticed some errors/warnings along the way
4. Rebooted phone and it would be stuck at the white HTC logo screen
5. Rebooted to hboot, but none of the options there would restore the phone.
6. Downloaded original ACE firmware and copied ZIP to SD card. It recognized this and performed install, in all appearances successfully until the reboot.
7. On reboot, the phone appeared completely dead. Later discovered that it would spring to life after ~7mins, vibrate 2-3 min, and then boot into Froyo
Phase II
1. Downloaded gingerbread RUU from HTC and ran it. Gets stuck on "Waiting for bootloader"
2. Thought perhaps hboot was corrupted, so ran instructions here "wiki.cyanogenmod.com/wiki/HTC_Ace:_Rooting_%26_CyanogenMod" to install hboot-eng and clockworkmod
3. This did not fix the booting (still wait 7mins, vibrate 2-3), but I do have root now, as verified through su root on the phone's terminal console.
4. Tried the RUU again, stuck on "Waiting for bootloader"
5. Noticed that if I had the phone USB connected to the PC when power cycling, it would come to a black HTC screen after about 7mins. In this mode, the phone seems to connect in Android bootloader interface.
6. Tried the RUU again, and this time it makes it past "Waiting for bootloader", but hangs (no error message) on "Sending". I've left it for nearly an hour with no change -- just keeps showing the black HTC screen.
I still can't get the phone into HBOOT (using the volume down + power method).
Hello,
Could someone tell me if there's an enclosure or a solution to this problem?
I've searched a few forums, and it appear to me that the conclusion is the old (ENG) HBOOT is incompatible with newer hardware.
Thanks.
hchao said:
Hello,
Could someone tell me if there's an enclosure or a solution to this problem?
I've searched a few forums, and it appear to me that the conclusion is the old (ENG) HBOOT is incompatible with newer hardware.
Thanks.
Click to expand...
Click to collapse
You will have to flash the original RUU again and then try to root the cell with the Hack Kit. You can find the original RUU in the general section or go to the htc site and just run the .exe update from fastboot. Let your cell reboot (it will take about 30 minutes) and then flash it.
jbryancs said:
hi,
Ive recently rooted my phone with no problems using the ace hack kit. i tried flashing the newest andriod revolution hd rom and was having problems with the superuser app force closing and the phone wasnt giving me root privledges. i decided to try and reroot the phone using the ace hack kit. (i realize this was my mistake). it stopped in the middle of the process. so i had to pull the battery. when i tried turning the phone back on the screen was black for about 6 or 7 mins. no vibrations or leds to indicate the phone was on. then the htc white screen comes on and the phone vibrates for 2 or 3 minutes straight and proceeds to come on. Ive tried to flash other roms using cwm recovery and itll load what ever rom i choose but i cant get into the hboot or anything and it does the the black screen everytime along with the vibration. is there anyway to fix this? ive tried over and over to boot into recovery through usb but it doesnt work.
so ive done a little research, could this be a eMMC problem? if so is it fixable... And if not would replacing the hboot help?
Click to expand...
Click to collapse
I am having this same problem I have searched and searched and this post was the only one that had the same issue could someone please help me out on this and post the fix. Thanks
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
Hi,
I need some help. I have 2 EVO's with similar problems, but different symptoms.
It all started when I tried to flash them to Boost using CDMA workshop! I know I should of stopped when i messed up the first one, but I'm a slow learner, and, I was successful with an EVO Shift, but the EVO 4G is a lot harder. Anyway, I now have 2 semi bricked phones and need some help.
The first one is stuck in the white screen bootloop, it comes on and shows HTC EVO 4G, goes black for a few seconds and then starts again. It has,
HBOOT 2.10.0001
RADIO 2.15.00.11.19
I have tried flashing a PC36img.zip from the sd card and I ran RUU image version 3.70.651.1, via USB cable which went through the entire process. The RUU says, Congratulations. Your ROM update has been completed. Your phone is now ready for use. At which time it goes straight back into bootloop.
The second phone has a black screen with htc in the middle and a triangle in each corner, it just sits in this state. It has,
HBOOT 2.16.0001
RADIO 2.15.00.85.02
When i run the RUU, it says if the phone has the 4 triangles, it means the RUU failed and rerun the RUU, which I have done with the same result.
I'm figuring I messed up something deeper than the RUU fixes, I realize i got way out of my depth on these 2 phones, the shift went so easily, I thought these would be the same.
I have read many forums and tried everything that has been suggested, with no positive results, any help would be greatly appreciated.
Hello,
I just got my sensation yesterday, and tried to s-off and install recovery today.
My phone is hboot 1.27 and s-on, on official HTC ICS firmware.
I was trying to use the "HTC Sensation/XE/4G Super Utility (AIO) by kgs1992" utility, to do s-off,
I downloaded the ControlBearRelease_pyramid_ICS_WIN_NOHTCDEV file and extract to tool foilder. But later I got stuck after it told me to do a post step 5:
5 - Connect phone over USB with debugging enabled
Should be on by default but if not, go to Settings > Develop Option > USB Debugging
6 - Run Juopunutbear S-OFF
Let this run through it's normal procedure, you will see some prompts on your phones screen about X application being granted superuser permissions, this is normal. After about 15-30 seconds your phone will reboot and boot to the Juopunutbear screen (I believe it's a recovery like loader). DO NOT UNPLUG YOUR USB CABLE!
Click to expand...
Click to collapse
My sensation rebooted, and got stuck in a gray screen with status bar, no any "some prompts on your phones screen..." shown.
After about 20 minutes, I decided to unplug USB and see what happened.
Now phone will boot, but will show a gray screen with status bar only.
I can boot into the hboot menu, but I don't know what I can do.
Can anyone give me some hints how to save my phone?
tennyleaz said:
Hello,
I just got my sensation yesterday, and tried to s-off and install recovery today.
My phone is hboot 1.27 and s-on, on official HTC ICS firmware.
I was trying to use the "HTC Sensation/XE/4G Super Utility (AIO) by kgs1992" utility, to do s-off,
I downloaded the ControlBearRelease_pyramid_ICS_WIN_NOHTCDEV file and extract to tool foilder. But later I got stuck after it told me to do a post step 5:
My sensation rebooted, and got stuck in a gray screen with status bar, no any "some prompts on your phones screen..." shown.
After about 20 minutes, I decided to unplug USB and see what happened.
Now phone will boot, but will show a gray screen with status bar only.
I can boot into the hboot menu, but I don't know what I can do.
Can anyone give me some hints how to save my phone?
Click to expand...
Click to collapse
Hi,
I suggest you copy/paste this post onto KGS thread,to see if he can help.
tennyleaz said:
Hello,
I just got my sensation yesterday, and tried to s-off and install recovery today.
My phone is hboot 1.27 and s-on, on official HTC ICS firmware.
I was trying to use the "HTC Sensation/XE/4G Super Utility (AIO) by kgs1992" utility, to do s-off,
I downloaded the ControlBearRelease_pyramid_ICS_WIN_NOHTCDEV file and extract to tool foilder. But later I got stuck after it told me to do a post step 5:
My sensation rebooted, and got stuck in a gray screen with status bar, no any "some prompts on your phones screen..." shown.
After about 20 minutes, I decided to unplug USB and see what happened.
Now phone will boot, but will show a gray screen with status bar only.
I can boot into the hboot menu, but I don't know what I can do.
Can anyone give me some hints how to save my phone?
Click to expand...
Click to collapse
Rare... but I don't think you have bricked your phone I use the revolutionary.io app to convert the phone s-off. I suppose that you didn't install any recovery, but I believe that you can do S-OFF using this method.
I hope the problem fixed when done... :S
Have you tried running an RUU?