[Q] Corrupt Bootloader - HTC Inspire 4G

I have the HTC Inspire 4G. I have a rooted stock rom from Bubby 323. My screen turned black when entering Clockwork recovery mode so I tried the Engineering S-Off method and when I flashed it said "Corrupt bootloader, do not turn off phone. Contact XDA" Does anyone have a suggestion on a fix? I have not turned off my phone since then. I used the one click S-Off method found here.

I had the same error and nearly crapped my pants thinking I bricked my phone. Its not really a big problem. Go to Menu>Settings>Applications>Manage apps and clear the data from Superuser. Reconnect your phone making sure you're on charge only, usb debugging. Run the Eng S-off tool and watch your phone as it attemps to push the data. Superuser should pop up asking to let the Eng tool have privs. Click allow and it should work fine. CWM has been working great for me ever since!

Ratman33 said:
I had the same error and nearly crapped my pants thinking I bricked my phone. Its not really a big problem. Go to Menu>Settings>Applications>Manage apps and clear the data from Superuser. Reconnect your phone making sure you're on charge only, usb debugging. Run the Eng S-off tool and watch your phone as it attemps to push the data. Superuser should pop up asking to let the Eng tool have privs. Click allow and it should work fine. CWM has been working great for me ever since!
Click to expand...
Click to collapse
You would think that if the program displayed a message telling you not to turn off your phone and check. XDA for a solution that he could have included the instructions you just gave.
Sent from my HTC Inspire 1G

RE-Corrupt Bootloader
Ratman33 said:
I had the same error and nearly crapped my pants thinking I bricked my phone. Its not really a big problem. Go to Menu>Settings>Applications>Manage apps and clear the data from Superuser. Reconnect your phone making sure you're on charge only, usb debugging. Run the Eng S-off tool and watch your phone as it attemps to push the data. Superuser should pop up asking to let the Eng tool have privs. Click allow and it should work fine. CWM has been working great for me ever since!
Click to expand...
Click to collapse
Thanks so much for the info. I did just as you said and it worked like as charm. I was worried for a while.

Ratman33 said:
I had the same error and nearly crapped my pants thinking I bricked my phone. Its not really a big problem. Go to Menu>Settings>Applications>Manage apps and clear the data from Superuser. Reconnect your phone making sure you're on charge only, usb debugging. Run the Eng S-off tool and watch your phone as it attemps to push the data. Superuser should pop up asking to let the Eng tool have privs. Click allow and it should work fine. CWM has been working great for me ever since!
Click to expand...
Click to collapse
Thanks so much for this, I nearly had a heart attack when the message came up saying my boot loader was corrupt.

Ratman33 said:
I had the same error and nearly crapped my pants thinking I bricked my phone. Its not really a big problem. Go to Menu>Settings>Applications>Manage apps and clear the data from Superuser. Reconnect your phone making sure you're on charge only, usb debugging. Run the Eng S-off tool and watch your phone as it attemps to push the data. Superuser should pop up asking to let the Eng tool have privs. Click allow and it should work fine. CWM has been working great for me ever since!
Click to expand...
Click to collapse
Sweet Mary.... I just bought my phone today, and about died when I got the DO NOT REBOOT message.... Thank you thank you thank you!!!!

Ratman33 said:
I had the same error and nearly crapped my pants thinking I bricked my phone. Its not really a big problem. Go to Menu>Settings>Applications>Manage apps and clear the data from Superuser. Reconnect your phone making sure you're on charge only, usb debugging. Run the Eng S-off tool and watch your phone as it attemps to push the data. Superuser should pop up asking to let the Eng tool have privs. Click allow and it should work fine. CWM has been working great for me ever since!
Click to expand...
Click to collapse
thanx so mush i almost died when it say DO NOT REBOOT YOUR PHONE

habanosrus said:
You would think that if the program displayed a message telling you not to turn off your phone and check. XDA for a solution that he could have included the instructions you just gave.
Sent from my HTC Inspire 1G
Click to expand...
Click to collapse
The instructions are in the thread for the UI........

HELP! Corrupt Bootloader, Do Not Reboot!
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)

rikrdoVe said:
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
You messed up your bootloaders by not paying attention to the big bold red letters in that thread. Go to the Ace Hack Kit thread and grab the link to the IRC room. Then tell them what you did and they should be able to help you out.

Related

Technical Think Tank for Bricked G1's

I started this thread as a constructive and positive place for those of us that have recently lost our G1's or ADP's. I am going to document all my settings, Radio version, Firmware, Build info, etc here and hopefully reverse engineer this issue until I have an answer. If anyone has any hardware engineering information on this device it would be greatly appreciated. I'm even willing to host a private forum from my site to work on this.
Thanks everyone for your continued hard work and Haykuro, you're still the man!
-JFv1.43 RC9 firmware (just did this one update, not the radio update)
-1 GB micro SD which was deliverd with the phone
-Google's Developers Edition
-rooted
-sim ulocked
-almost fully loaded about 80 % battery
-everything went fine, the update went fine, restarting, and then no response and always and always the same android screen,
now im trying to crash it by low battery, not by just take the battery out, maybe this'll work (but I dont think so)
don't know anything else
Partioned Fat32/EXT2 1GB SDcard from t-mobile
Flashed RC29 via Bootloader .NBH file
Rooted with RC29
Updated to RC33
Flashed Hard SPL
Flashed JF v1.5 ADP Lucid MOD - did APPs2SD and Dalvik2SD
Flash 2.22.19.26I Radio
Flashed Grafitti Citrus Theme JFv1.50 Beta
Flashed H Special SPL with battery at 89% - saw it update, rebooted on its own, saw the chip with the arrow on it and it rebooted. once after that it hanged. I waited 5 minutes and then took the battery out. Got my sdcard reader, renamed the jf v1.5 to update to reflash like instructed. powered the phone with home+power and got nothing but a hang on t-mobile G1 screen.
Both phones were done the same. One phone bricked and one phone flashed the SPL.
I wonder if the Dream responds to goldcards like other HTC phones do...
That's how we fixed our Heralds, which is how the Elf's got their fix, etc.
ivanmmj said:
I wonder if the Dream responds to goldcards like other HTC phones do...
That's how we fixed our Heralds, which is how the Elf's got their fix, etc.
Click to expand...
Click to collapse
Goldcard as in a specialized SIM?
d474rpr said:
Goldcard as in a specialized SIM?
Click to expand...
Click to collapse
Goldcards as in a specialized SD card
d474rpr said:
Goldcard as in a specialized SIM?
Click to expand...
Click to collapse
You convert a SD card into a Goldcard and the phone will read it and allow the phone to flash ANY NBH file, regardless of CID, etc etc.
MosquitoD4K said:
-JFv1.43 RC9 firmware (just did this one update, not the radio update)
-1 GB micro SD which was deliverd with the phone
-Google's Developers Edition
-rooted
-sim ulocked
-almost fully loaded about 80 % battery
-everything went fine, the update went fine, restarting, and then no response and always and always the same android screen,
now im trying to crash it by low battery, not by just take the battery out, maybe this'll work (but I dont think so)
don't know anything else
Click to expand...
Click to collapse
This has happened to me many times when I didn't wipe (the PHONE ). Take the battery out, place back in and hold Home + Power to get into menu. Type alt + w to wipe, afterwards, alt + s to apply update.zip from sdcard, then Home+Back to restart. The first time loading, it can take up to ten minutes to get past the Android screen (mine took 7-10 minutes), so be patient.
Post back with any results.
ivanmmj said:
You convert a SD card into a Goldcard and the phone will read it and allow the phone to flash ANY NBH file, regardless of CID, etc etc.
Click to expand...
Click to collapse
that wont work i just read the write up. In order for the goldcard to work, the g1 has to go into fastboot, which none of our devices can go into fastboot nor recovery. I even formatted a sdcard to start the process but when i got to the fastboot i was so disappointed.
One detail, when i flashed the new spl I was doing something else and when i check my phone it back to recovery utility windows itself ,it was in 15 20 minute, after that i reinstalle jf1.5 and all worked ok
what this means. if you are flashing your phone and before these process finishes your take out you battery, you can bricking you phone. take patience and wait.
Good luck
ps:i change the final text for sir*mez
sir*mez said:
that wont work i just read the write up. In order for the goldcard to work, the g1 has to go into fastboot, which none of our devices can go into fastboot nor recovery. I even formatted a sdcard to start the process but when i got to the fastboot i was so disappointed.
Click to expand...
Click to collapse
satru said:
One detail, when i flashed the new spl I was doing something else and when i check my phone it back to recovery utility windows itself ,it was in 15 20 minute, after that i reinstalle jf1.5 and all worked ok
what this means. if you are flashing your phone and before these process finishes your take out you battery, you and only you bricking you phone. take patience and wait.
Good luck
Click to expand...
Click to collapse
this happened to the one that bricked.
Flashed H Special SPL with battery at 89% - saw it update, rebooted on its own, saw the chip with the arrow on it and it rebooted. once after that it hanged. I waited 5 minutes and then took the battery out. Got my sdcard reader, renamed the jf v1.5 to update to reflash like instructed. powered the phone with home+power and got nothing but a hang on t-mobile G1 screen.
Both phones were done the same. One phone bricked and one phone flashed the SPL. So yes I guess I bricked one phone but a miracle happened with the other one. the one that flashed properly went into the recovery on its own right after the boot, but not in no 15-20 min wait like you said. you sure need to stop the blaming. i am not blaming anyone for my bricked phone, im just trying to find a solution. you are going to get this locked because of the bickering.
hey sir*mes was no my intentions blaming to anyone , i only want to say that all need to give more time to flash before take out the battery. only that.
i will do something for you , i will change the text, happy?
Good luck
sir*mez said:
this happened to the one that bricked.
Flashed H Special SPL with battery at 89% - saw it update, rebooted on its own, saw the chip with the arrow on it and it rebooted. once after that it hanged. I waited 5 minutes and then took the battery out. Got my sdcard reader, renamed the jf v1.5 to update to reflash like instructed. powered the phone with home+power and got nothing but a hang on t-mobile G1 screen.
Both phones were done the same. One phone bricked and one phone flashed the SPL. So yes I guess I bricked one phone but a miracle happened with the other one. the one that flashed properly went into the recovery on its own right after the boot, but not in no 15-20 min wait like you said. you sure need to stop the blaming. i am not blaming anyone im just trying to find a solution. you are going to get this locked because of the bickering.
Click to expand...
Click to collapse
sir*mez said:
that wont work i just read the write up. In order for the goldcard to work, the g1 has to go into fastboot, which none of our devices can go into fastboot nor recovery. I even formatted a sdcard to start the process but when i got to the fastboot i was so disappointed.
Click to expand...
Click to collapse
So what harm would it do to try? From what I remember the goldcard on herald was supposed to get us into the bootloader even when we couldn't normally.
Let me be perfectly clear, those of us with the issue of a bricked device from loading the SPL from Haykuro are experiencing an actual case of being bricked.
Read carefully.
The phone WILL NOT turn on!!!!
We are looking for a solution that runs as far back as actually burning the SPL image directly to the phone's memory. I am even willing to try a hardware to hardware method to accomplish this.
I know the phone is still somewhat responsive because my laptop detects the USB connection to the phone but it will not recognize the device.. obviously because the communication is broken since the phone is dead. The power LED will turn on but only after I remove the battery first. Once I press the POWER key the LED turns off and will not light again until I remove and replace the battery.
Solutions that we are trying:
GoldCard method.
Looks like a couple of us have tried this but since fastboot can't see the device then we can't use this method unless someone knows something super seceret.
Crashing the device by allowing the battery to fully discharge. Unlikely but trying anyway.
Any other ideas?????
Thanks everyone for helping thus far!
neoobs said:
So what harm would it do to try? From what I remember the goldcard on herald was supposed to get us into the bootloader even when we couldn't normally.
Click to expand...
Click to collapse
I tried it and so far no luck...
neoobs said:
So what harm would it do to try? From what I remember the goldcard on herald was supposed to get us into the bootloader even when we couldn't normally.
Click to expand...
Click to collapse
ok but the phone wont go into bootloader. which is what im trying to get it to do. if i get it to bootloader i know i can fix it. even if it went to the recovery i could fix it. but I get nothing.
in order to create a goldcard for the dream it has to read the sdcard off fastboot which i cant get into.
d474rpr said:
Let me be perfectly clear, those of us with the issue of a bricked device from loading the SPL from Haykuro are experiencing an actual case of being bricked.
Read carefully.
The phone WILL NOT turn on!!!!
We are looking for a solution that runs as far back as actually burning the SPL image directly to the phone's memory. I am even willing to try a hardware to hardware method to accomplish this.
I know the phone is still somewhat responsive because my laptop detects the USB connection to the phone but it will not recognize the device.. obviously because the communication is broken since the phone is dead. The power LED will turn on but only after I remove the battery first. Once I press the POWER key the LED turns off and will not light again until I remove and replace the battery.
Solutions that we are trying:
GoldCard method.
Looks like a couple of us have tried this but since fastboot can't see the device then we can't use this method unless someone knows something super seceret.
Crashing the device by allowing the battery to fully discharge. Unlikely but trying anyway.
Any other ideas?????
Thanks everyone for helping thus far!
Click to expand...
Click to collapse
Are you saying your screen doesn't turn on?
neoobs said:
Are you saying your screen doesn't turn on?
Click to expand...
Click to collapse
No, I'm saying it doesn't turn on.
d474rpr said:
No, I'm saying it doesn't turn on.
Click to expand...
Click to collapse
The same happens on Heralds when the imgfs is messed up. To fix it, we force it to go into the bootloader mode and it does turn on. I wonder if it's something similar.
I meantioned in the big main topic an idea though I dont think anyone saw it.
In the past for other phones I was able to make recoveries using the computer while it was in the boot loop.
Anyone with the brick, try to see what happens when you do this:
adb remount
After the "T-Mobile G1" screen shows up. See if it says mount sucessful. I would try though it does not stay on the screen too long for me, not only that it might work for me just because it continues fine so its inconclusive.
If you get lucky and it says remount successful, you could try this:
adb shell recovery
I am not sure of the commands to follow from there, but it might allow you to flash a different update.zip file from the command line. If you get lucky like that, look up the commands and see how that might go. There has to be a way to communicate to the hardware when that screen comes up. Its good that that screen comes up, because it means its not 'fried' so to speak, it just has a misconfigured loader which doesnt have the correct set of instructions (good point about the different types of boards, thats most likely the issue) for THAT board. I would go back to the one that worked previously.

[GUIDE] One Click How to Root the Aria with Unrevoked 3.21

I first want to thank everyone at UnrEVOked for what they've done. I'm posting this because there aren't any really detailed instructions. Its an easy enough root, but I know I've been there before and even the simplest things can be tough if things aren't laid out. So here's a step by step tutorial.
Due to some bugs, Unrevoked 3.2 was taken down shortly after being released, but the updated version is now LIVE! So obviously we're going to bring you a video tutorial on how to do it! Thanks to the guys at Unrevoked for giving us this simple solution to rooting the HTC Aria.
LINK TO VIDEO WALKTHROUGH FOR HOW TO ROOT THE ARIA
◄●REQUIRED DOWNLOADS●►
EVERYONE: Unrevoked3. Download the version for your OS.
WINDOWS USERS: unrEVOked modified USB driver
◄●How to Install HBOOT Drivers (Windows Users ONLY)●►
If you're using Windows, you're going to have to install the HBOOT drivers first. You can follow this video tutorial:
How to Install HBOOT Drivers
and follow along with these written instructions provided by the Unrevoked team:
Download the unrEVOked modified USB driver and expand it somewhere you will remember.
Turn off your phone, then boot it into the HBOOT menu by holding power and volume down.
On your phone, you will have to select HBOOT USB at that menu by pressing volume down four times, then power. Wait until the screen flashes through an “SD Checking” message before pressing buttons; otherwise, the phone will ignore keypresses.
Connect the phone to your Windows machine with a USB cable and wait for the phone to say HBOOT USB PLUG on screen.
Open Device Manager.
Click Start, then right click on Computer, then click Properties, then click Device Manager.
Under Other devices, you should now see the Android 1.0 device.
Right click on Android 1.0 and click Update Driver Software:
Click on Browse my computer for driver software.
Click on Browse and select the Android USB Driver folder on on your computer, click ok, then click next.
You should get a status bar indicating that the driver is installing. If you get any warnings, just click Ok.
Your driver should install.
Click Close and make sure Android Bootloader Interface is listed under Android Phone.
◄●Instructions●►
Make sure you downloaded Unrevoked3 for your OS.
If you're on Windows, make sure you "uninstall HTC Sync or any other program that might talk to the phone over USB (doubletwist, etc). They will cause problems" (Unrevoked.com).
Plug your phone into your computer with USB.
Drag down from the notification bar on your phone and select "Charge Only" and "Remember this"
Make sure your phone has USB Debugging turned on by going to Menu>>Settings>>Applications>>Development and checking USB debugging.
Run the Reflash application that you downloaded.
Unrevoked will run its processes. Follow the few instructions it gives and thats it!
You're now rooted!
kopimi said:
If you're stuck on "Waiting for Device", INSTALL HTC Sync, but do NOT run it.
HTC Sync will load the necessary ADB drivers onto your computer, but so long as you do not let the process run while you are trying to run unrEVOked3, it will NOT interfere. Knowing this would have saved me quite a lot of time, so hopefully someone else reads this and they can salvage their sanity
Also, if you're stuck on "Waiting for Root", go ahead and restart your Android while its connected to the USB. It took me one reboot for the root to go into effect, and right after that, unrEVOked3 finished.
Click to expand...
Click to collapse
Great guide, would have really helped me last night while I was pulling my hair out haha. One thing you may want to add to the OP:
If you're stuck on "Waiting for Device", INSTALL HTC Sync, but do NOT run it.
HTC Sync will load the necessary ADB drivers onto your computer, but so long as you do not let the process run while you are trying to run unrEVOked3, it will NOT interfere. Knowing this would have saved me quite a lot of time, so hopefully someone else reads this and they can salvage their sanity
Also, if you're stuck on "Waiting for Root", go ahead and restart your Android while its connected to the USB. It took me one reboot for the root to go into effect, and right after that, unrEVOked3 finished.
kopimi said:
Great guide, would have really helped me last night while I was pulling my hair out haha. One thing you may want to add to the OP:
If you're stuck on "Waiting for Device", INSTALL HTC Sync, but do NOT run it.
HTC Sync will load the necessary ADB drivers onto your computer, but so long as you do not let the process run while you are trying to run unrEVOked3, it will NOT interfere. Knowing this would have saved me quite a lot of time, so hopefully someone else reads this and they can salvage their sanity
Also, if you're stuck on "Waiting for Root", go ahead and restart your Android while its connected to the USB. It took me one reboot for the root to go into effect, and right after that, unrEVOked3 finished.
Click to expand...
Click to collapse
Thanks man Added to the OP
PS - Others have asked elsewhere if it flashes a custom recovery. Yes, it flashes Clockwork
I rooted my girlfriend's Aria with this and I see SuperUser Permissions (as you would with a root) but when I go to Android SDK and type "adb shell" I get a $ back instead of a 2. I also typed su and got back a permissions denied. I am also unable to do "adb remount" due to permissions. Is there any way around this?
Thanks
-Mike
LTD36 said:
I rooted my girlfriend's Aria with this and I see SuperUser Permissions (as you would with a root) but when I go to Android SDK and type "adb shell" I get a $ back instead of a 2. I also typed su and got back a permissions denied. I am also unable to do "adb remount" due to permissions. Is there any way around this?
Thanks
-Mike
Click to expand...
Click to collapse
You need to give the adb shell SuperUser permission, too. Load the SuperUser app and then make a adb shell connection while the SuperUser screen is up. Then when you type su at the $ prompt, the SuperUser app will give you the Allow/Deny prompt.
Regards,
Tom
tpbklake said:
You need to give the adb shell SuperUser permission, too. Load the SuperUser app and then make a adb shell connection while the SuperUser screen is up. Then when you type su at the $ prompt, the SuperUser app will give you the Allow/Deny prompt.
Regards,
Tom
Click to expand...
Click to collapse
Thanks for helping out and replying to that. I've been swamped with other stuff lately.
I just tried this and can't seem to get it to work. Can anybody help me out? I'm sure that I've done something wrong. I finally got unrEVOked to recognize my Aria, however when I clicked "Ok" (to root it when the message popped up) it said "Failed to push recovery. Terminating." What did I forget to do??
Nevermind... I got it to work finally.
Still shows S-ON
Freak said:
Still shows S-ON
Click to expand...
Click to collapse
Unrevoked 3.21 does not turn S-OFF on the Aria; that is only for a few CDMA phones like the EVO, Incredible, Hero and CDMA Desire.
Regards,
Tom
tpbklake said:
Unrevoked 3.21 does not turn S-OFF on the Aria; that is only for a few CDMA phones like the EVO, Incredible, Hero and CDMA Desire.
Regards,
Tom
Click to expand...
Click to collapse
Yeah don't worry about not having S-OFF, its not something necessary for a rooted phone. As long as you've got Superuser, you're set and rooted.
Sorry for my noobiness on the Aria, but what does using unrevoked to root it do for the Aria?
Sent from my HTC Liberty using XDA App
Still unable to install applications with the phone rooted
Hi, I followed the instructions, after I got the "done" message, i went to nandroid option made a backup, when it was finished i restarted the phone.
I´m trying to use Astro to install Sygic on the phone but I always get the same message.... you phone is blocked.
I see the little ninja in apps... what else is missing? what is wrong?
Thanks for your help...
I´m about to give up and sell this phone
The day i got the phone I upgraded it to the latest firmware available in HTC web page, is that the ugly part of the story?
-------------------------------------------------------
I solved this issue by istalling a custom image.
Last night I istalled the liberated_aria_ddx_R012_signed, I have to say that everythign is going perfect, no problems so far.
But everytime I plug the cable and the phone is off, it starts in recovery mode, so i have to select reboot.
Before flashing the image, I formated the SD card, wiped data, cache and dalvik cache.
If I turn on the phone it starts normally, It´s just happening when I plug the usb cable or the charger.
I also made other test, I plugged the phone when it was on, then I turned it off (with the cable plugged), when it finished the turning off process it automatically started again in the clockwork recovery mode.
Could you please tell me how to solve this?... this is my first Android phone, I donñt want it to start in recovery mode when I just want to charge it.
Thanks in advance
Phone needs to be on while charging. You no longer have to turn equipment off to get a full charge. If you charge while it's off it will go into recovery mode.
echodun said:
Phone needs to be on while charging. You no longer have to turn equipment off to get a full charge. If you charge while it's off it will go into recovery mode.
Click to expand...
Click to collapse
Thanks for your prompt answer.
Is there any way to change it?, i´d like it to work as usual, you plug it you get the green battery charging... that way it is impossible to make misstakes, for the next time i need to get in to recovery mode i would push pwer + volume-.
maybe by applying a mod.zip using clockwork?
0ptimus82 said:
Thanks for your prompt answer.
Is there any way to change it?, i´d like it to work as usual, you plug it you get the green battery charging... that way it is impossible to make misstakes, for the next time i need to get in to recovery mode i would push pwer + volume-.
maybe by applying a mod.zip using clockwork?
Click to expand...
Click to collapse
No way that I know of. It's on my Cyangenmod ROM too. Maybe a product of using the Unrevoked method of rooting. When I plug mine in to the computer charging cable I get a red light for charging and then screen goes off in about 10 secs. Not a big deal to me although it through me for a loop at first too.
echodun said:
No way that I know of. It's on my Cyangenmod ROM too. Maybe a product of using the Unrevoked method of rooting. When I plug mine in to the computer charging cable I get a red light for charging and then screen goes off in about 10 secs. Not a big deal to me although it through me for a loop at first too.
Click to expand...
Click to collapse
I know... it´s not a problem, it´s just that it´s not the way it happened for some years ago since i´ve had a cell phone .
So, the only way to avoid it is to uninstall clockwork recovery?
Cracked my screen on my rooted aria after my camera stopped working and I had filed for a warranty replacement. Was so happy with the original phone that I took the $300 hit they would apply if I sent the bad phone back with physical damage...I decided to keep the new phone and ATT will allow me to pay them in several installments with my monthly bill..
I promptly used your instructions to root this new phone. Took me all of 5 minutes.
Great job.
You can replace the glass on an Aria for a lot less than $300.

[Q] Desire S - Market suicide

Hi guys.
After two weeks without wifi, yesterday, my phone decide to update about 20 apps from market. When Beautiful Widgets were downloading, phone suddenly froze and I had to remove my battery after 10 minutes. When it booted again, Angry Birds started to update and phone froze again. So I removed my battery once again and when it booted up, I turned my net connection offline to prevent downloading. As soon as I did so, I canceled all market downloads and turned connection online again. Market started updating on its own and phone froze during night.
So I decided to removed battery once again this morning and when I put it back in, put it back in, phone froze after "Quietly Brilliant" logo with black screen.
It was suitable for factory reset from bootloader. So I did factory reset and same story repeated, except for this, it was a loading loop, HTC Quietly Brilliant and sound which comes with it over and over again.
So in the end, I tried to do the "recovery" option which did no good and again factory reset, but this time, bootloader froze and nothing happened. This is final state of my phone.
So after boring story, there is a question. Is there any way I can do software flash / reset without phone (via USB etc?) before I send it back to HTC for repair?
Device is S ON and never been rooted. I also removed SIM and memory card with no effect.
Thanks a lot!
You should take hope from the fact that you are able to still enter bootloader and perform full reset
Also the fact that you are still s-on means that you should still be covered under warranty
I believe that you should be able to re flash your original rom via your pc using RUU, check to see if your original is in the rom sticky thread within the dev section and if so start downloading
Sent from my HTC Desire S using XDA Premium App
You may well have a hardware problem, in which case I would advise you send it for repair rather than trying to root and invalidating your warranty.
Hey, thx for reply.
I have no experiences in this but I guess I only need to know this things:
RUU - Stands for ROM Upgrade Utility. What soft should I use?
Also, all I can see in bootloader is following:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.11_M
eMMC-boot
Mar 10 2011,14:58:38 (<wtf?)
and then just classic boot menu with options like FASTBOOT etc.
Therefore I cant figure out, which ROM is mine in that thread. Also, is there any option to flash ROM from memory card? Does it have to be signed?
Only limitation is warranty which I dont wanna lose. Thx.
InfernalByte said:
You may well have a hardware problem, in which case I would advise you send it for repair rather than trying to root and invalidating your warranty.
Click to expand...
Click to collapse
See the statement above, I will not do anything to invalidate the warranty.
Yesterday, after attempting the "Update all" for the first time (well, not exactly) the phone froze just as yours did & started encountering the same issues. After coming here to seek assistance, this thread was the first I laid eyes upon.
My case in somewhat more detail, after freezing during the "Update all", I performed a soft reset by removing the battery as well, booted up fine, but as soon as everything was loaded the market tried to continue where it left off (which is updating Opera Mobile @ 98%) and the result was another freeze. I was quickly able to deduct that the update were to be the issue & turned off connectivity. Now, at the present state, Opera Mobile update is still under notifications (at 98% complete but "paused"), as soon as I re-enable either WiFi or 3G it continues & crashes. I cleared all caches & reset all Market applications & rebooted to no avail.
Hard reset was next on my list, but see-ing how the situation got worse for your device hereafter, I am holding it off for now. Is it possible to have market updates, that are ongoing, canceled? Bear in mind that I cant enter Market since it requires connectivity.
Weird stuff.
Yes, when your phone is turned on (connection on), open your Market app, press menu button and select "My apps". You should see all downloading apps now. Hold your finger on each and wait until menu pops up. Select cancel download. You have to be quick tho.
If I were you, I would not do any software reset, my phone is pretty much bricked now, as it freezes on nearly every bootloader option.
Numline1 said:
Yes, when your phone is turned on (connection on), open your Market app, press menu button and select "My apps". You should see all downloading apps now. Hold your finger on each and wait until menu pops up. Select cancel download. You have to be quick tho.
If I were you, I would not do any software reset, my phone is pretty much bricked now, as it freezes on nearly every bootloader option.
Click to expand...
Click to collapse
Thanks! That did the trick, was able to remove everything due to be updated.
Strangely, though, I wasn't able to finish loading the market before it resumed the Opera update. This time, however, instead of crashing it was able to complete it (contrary to the last 10+ attempts yesterday), thus there is a chance it wouldn't have crashed at all. In any case, keeping distance from the Market seems like a valid idea for now.
Reading your thread might've helped to avoid my device turning into a brick, I appreciate it.
Well, update to my current status:
Im still in hboot. Device was recognized as "Android 1.0" in my Windows, so I had to install ADB driver. It is now connected as Android Composite ADB Interface".
I can't get any further, since RUU says my phone is not connected to PC.
Any advices please?
PS: When I choose "Recovery" in hboot, it shows HTC logo for a while, then icon of mobile phone with green sign shows and after few secs, screen turns off and phone vibrate for a few times and disconnects from PC.
//When I connect it in Fastboot, it shows as "MyHTC" in Windows.
Numline1 said:
PS: When I choose "Recovery" in hboot, it shows HTC logo for a while, then icon of mobile phone with green sign shows and after few secs, screen turns off and phone vibrate for a few times and disconnects from PC.
Click to expand...
Click to collapse
Afraid, that I'm well out of my depth with all that, hopefully someone else with more knowledge will post...or else it's warranty return. best of luck
Np, thx for trying, maybe someone else will know
//Update: In Fastboot mode, my device is recognized by RUU!!! Trying to update right now!!!
As you've never been rooted or S-off, and the phone has developed its own fault. I'd return it!
Well, so far, no luck. RUU stuck at "Rebooting to bootloader" and phone is frozen.
InfernalByte said:
As you've never been rooted or S-off, and the phone has developed its own fault. I'd return it!
Click to expand...
Click to collapse
Im willing to do that first thing tommorow, but Im trying to fix it today, as it is sunday and I have day off.
Numline1 said:
Well, so far, no luck. RUU stuck at "Rebooting to bootloader" and phone is frozen.
Im willing to do that first thing tommorow, but Im trying to fix it today, as it is sunday and I have day off.
Click to expand...
Click to collapse
Good luck
(....10 Chars...)
Ok, update about my phone so far:
RUU was not sucessful, for some reason there's still freeze in certain HBOOT actions, like when I select "Factory reset" or when RUU is trying to get phone from fastboot to bootloader.
So I extracted rom.zip from my RUU and now I'm backing up my memory card using my old phone. I'm willing to rename it to update.zip and try to flash it.
Any advices about this?
Numline1 said:
Ok, update about my phone so far:
RUU was not sucessful, for some reason there's still freeze in certain HBOOT actions, like when I select "Factory reset" or when RUU is trying to get phone from fastboot to bootloader.
So I extracted rom.zip from my RUU and now I'm backing up my memory card using my old phone. I'm willing to rename it to update.zip and try to flash it.
Any advices about this?
Click to expand...
Click to collapse
Update.zip will not work, if your determined to try something push a new SPL via fastboot commander, even thought your not S-off if things aren't working maybe the CID check wont check either.
Below will only work if your phone is not branded or you have a goldcard.
Alternatively unzip your RUU on your PC in one of the files called {squigly brackets and a lot of numbers673652435364849483763} you'll find a .zip called rom.zip rename this PB99IMG and put the file into the root directory of your SD card, and boot into Hboot. Just answer yes to any questions. This is the way HTC Tech folk themselves serve an RUU.
Yea, I actually extracted it using advanced system monitor from microsoft, this file was in temp folder. That's where my rom.zip was. Anyway, isn't it PB88IMG.zip? I think DS is checking for this one. Thx.
//Edit: I mean PB88IMG.img
//Edit2: It's PG88IMG.zip It's now updating, don't know if it works yet, still at BOOTLOADER update with status "Updating".
Ok, I think this is my last post, since I no longer know what else to do. When Im trying to flash PG88IMG, it stops at [1]BOOTLOADER - Updating.
For more than one hour. There's something wrong with it and I will claim my warranty, which will be funny, since Im in Slovakia, phone was bought from Amazon with 3 year warranty from SquareTrade and they claim, they may just return money in some cases, which will result in buying a new phone = more than 2 weeks...
Numline1 said:
they may just return money in some cases, which will result in buying a new phone = more than 2 weeks...
Click to expand...
Click to collapse
O, bugger!
question is if they do give you the money, will you buy another DS? and if not what would you consider instead? Sensation?
Yea, can't say yet, since I don't know. I just discovered, there may be a chance they will cover my repair costs when I email them all the service documentation from service center.
But if they do, I'd like to stay with HTC, I paid something about 377L for the phone, so I may buy something better now.
Anyway, thanks a lot for help guys, if you come with some new ideas about how to fix it, do not hesitate to tell me I'll be sending it to them first thing tommorow.

[Q] my htc sensation will not boot

I have a Htc Sensation running on the Tmobile network
i decided to go with a different rom and tried to install the rom from COREDROID SENSATION XE & 4G v5.1.
after installing it was stock on the boot screen.
I tried to SCID and install PG58DOAG.
at this point my phone will not boot.
I can get into the the recovery mode after i select "recovery" it goes to a screen with a red triangle and an exclamation mark.
I the volume up and power and the try to install a update...but non has worked
can get one help??
download this file http://www.filefactory.com/file/c19...00U_10.14.9035.01_M_release_223976_signed.exe
and run it with your phone plugged in your pc, it should do a stock recovery on your phone.
I faced the same issue with another ROM.
The only way I found to reboot was to reinstall the firmware while connected via USB with the PC.
And after that, I reinstalled the ROM.
I couldnt even boot.
primekrieger said:
I couldnt even boot.
Click to expand...
Click to collapse
Okay, first off stop digging up multiple 1 and 2 year old threads to post about your problem.
Second, be MUCH more specific about what the issue is. What happened before it stopped booting? Was it dropped or something or was it working fine?
Is it rooted?
Is it S-Off?
Skipjacks said:
Okay, first off stop digging up multiple 1 and 2 year old threads to post about your problem.
Second, be MUCH more specific about what the issue is. What happened before it stopped booting? Was it dropped or something or was it working fine?
Is it rooted?
Is it S-Off?
Click to expand...
Click to collapse
Sorry about that.
Here are the full details:
I have a Sensation XE, it was running ARHD 7.2, rooted, Bootloader Unlocked, S-OFF
I was playing subway surfers when all of a sudden the phone froze, no buttons nothing worked. After a while it itself restarted and got stuck on the white HTC boot screen. When it didnt progress for some minutes, I removed the battery, reinserted it and tried turning it on. But nothing, no signs of life were shown. Even on connecting the wall charger there was no charging LED.
Only thing is that windows can detect it as QHSUSB_DLOAD or something.
I checked out the Unbricking Sensation forum at: http://forum.xda-developers.com/show....php?t=1522351
but they say it works only for devices bricked while turning to S-ON, but as I mentioned mine is S-OFF. So, can I still use their method or is there some alternative?
Thanks
primekrieger said:
Sorry about that.
Here are the full details:
I have a Sensation XE, it was running ARHD 7.2, rooted, Bootloader Unlocked, S-OFF
I was playing subway surfers when all of a sudden the phone froze, no buttons nothing worked. After a while it itself restarted and got stuck on the white HTC boot screen. When it didnt progress for some minutes, I removed the battery, reinserted it and tried turning it on. But nothing, no signs of life were shown. Even on connecting the wall charger there was no charging LED.
Only thing is that windows can detect it as QHSUSB_DLOAD or something.
I checked out the Unbricking Sensation forum at: http://forum.xda-developers.com/show....php?t=1522351
but they say it works only for devices bricked while turning to S-ON, but as I mentioned mine is S-OFF. So, can I still use their method or is there some alternative?
Thanks
Click to expand...
Click to collapse
Can you get into recovery?
Sent from your phone. You should be careful where you leave that thing.
Skipjacks said:
Can you get into recovery?
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
No, I can't get to recovery. The phone doesn't start up at all. But windows detects something like QHSUSB_DLOAD when connecting through usb.
primekrieger said:
No, I can't get to recovery. The phone doesn't start up at all. But windows detects something like QHSUSB_DLOAD when connecting through usb.
Click to expand...
Click to collapse
Is the battery charging when you connect it to USB like that? If so I'd say to try an ruu to return it to completely stock. You will lose all user data on the internal memory when doing this. And it will return the phone to s-on and stock ROM. You will have to start over.
Do a search for ruu and you should find the thread that walks you through the process. Its really easy. You basically just run an .exe file from windows and it does everything else.
Sent from your phone. You should be careful where you leave that thing.
Skipjacks said:
Is the battery charging when you connect it to USB like that? If so I'd say to try an ruu to return it to completely stock. You will lose all user data on the internal memory when doing this. And it will return the phone to s-on and stock ROM. You will have to start over.
Do a search for ruu and you should find the thread that walks you through the process. Its really easy. You basically just run an .exe file from windows and it does everything else.
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
No, the charging LED doesnt glow.
Phone is detected on USB connection after i remove the battery. And moreover windows doesnt detect it as a phone i think.
PS: Losing data, S-OFF, ROM is not a concern. I just want it working, bought it just 6 months ago :crying:
primekrieger said:
No, the charging LED doesnt glow.
Phone is detected on USB connection after i remove the battery. And moreover windows doesnt detect it as a phone i think.
PS: Losing data, S-OFF, ROM is not a concern. I just want it working, bought it just 6 months ago :crying:
Click to expand...
Click to collapse
Do you have access to another battery just to make sure your battery isn't fried? If there is physical damage to the battery it will neither charge nor will it power on.
Also, try doing the ruu thing anyway. Worst its going to do is not work.
Sent from your phone. You should be careful where you leave that thing.
Skipjacks said:
Do you have access to another battery just to make sure your battery isn't fried? If there is physical damage to the battery it will neither charge nor will it power on.
Also, try doing the ruu thing anyway. Worst its going to do is not work.
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
As you said I searched for RUU for my phone, but now the problem is I can't decide what RUU to download since the phone wont start and therefore I can't see software number or CID.
primekrieger said:
As you said I searched for RUU for my phone, but now the problem is I can't decide what RUU to download since the phone wont start and therefore I can't see software number or CID.
Click to expand...
Click to collapse
from bootloader connect the device in the pc via usb(it should say fastboot usb)
open a cmd in the folder where you have adb and fastboot files and do these commands
fastboot getvar version-main
fastboot getvar cid
rzr86 said:
from bootloader connect the device in the pc via usb(it should say fastboot usb)
open a cmd in the folder where you have adb and fastboot files and do these commands
fastboot getvar version-main
fastboot getvar cid
Click to expand...
Click to collapse
Hi there!
Even my device is facing similar sort of problems. Although the situation is not as bad as the op,but still the phone is still just a paperweight.
Now what I did- unlocked bootloader via HTC dev site( HBOOT Ver 1.27)
Decided to S-off by J.Bear method.
Everyhting went fine untill the phone restarted. Controlbear no longer recognised the device. It said check your drivers.
That was the time when everything messed up.
Now the phone would no longer boot ahead of the white HTC bootscreen. And sometimes it even powers on directly to recovery(even when i'm not pressing volume down).
And one more strange thing happening.."adb devices" command doesn't show any devices listed although i can check the firmware and cid version(via fastboot command). And the device is showing up in device manager(my HTC). But adb commands are not working.
Am i missing something?
Any help would be much appreciated.
walkermoon said:
Hi there!
Even my device is facing similar sort of problems. Although the situation is not as bad as the op,but still the phone is still just a paperweight.
Now what I did- unlocked bootloader via HTC dev site( HBOOT Ver 1.27)
Decided to S-off by J.Bear method.
Everyhting went fine untill the phone restarted. Controlbear no longer recognised the device. It said check your drivers.
That was the time when everything messed up.
Now the phone would no longer boot ahead of the white HTC bootscreen. And sometimes it even powers on directly to recovery(even when i'm not pressing volume down).
And one more strange thing happening.."adb devices" command doesn't show any devices listed although i can check the firmware and cid version(via fastboot command). And the device is showing up in device manager(my HTC). But adb commands are not working.
Am i missing something?
Any help would be much appreciated.
Click to expand...
Click to collapse
probably your hboot get locked after S-OFF.that's why adb commands don't work(i think)
check your bootloader details
if now you have S-OFF and locked hboot flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
it will give you also patched hboot which is unlocked
follow the instructions to the letter(important)
and before flashing check md5 sums(important)
rzr86 said:
probably your hboot get locked after S-OFF.that's why adb commands don't work(i think)
check your bootloader details
if now you have S-OFF and locked hboot flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
it will give you also patched hboot which is unlocked
follow the instructions to the letter(important)
and before flashing check md5 sums(important)
Click to expand...
Click to collapse
Appreciate your concern.
But the thing is my device is still S On. The JBear method didn't finish. It messed up in between.
I'm attaching a pic. Give a look.
walkermoon said:
Appreciate your concern.
But the thing is my device is still S On. The JBear method didn't finish. It messed up in between.
I'm attaching a pic. Give a look.
Click to expand...
Click to collapse
hmm,
probably you need to use the temproot remove.bat file to remove temproot
check for troubleshooting in this thread
http://forum.xda-developers.com/showthread.php?t=1661631
also refer you issue there
ganeshp will help you further
or you can install 4ext recovery
enable smartflash from it and flash a custom rom

Please HELP! Bootloader is Corrupt. DO NOT REBOOT!

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?

Categories

Resources