Database Info

Method for 100% factory restore, unrooted.

This is for those of you that may need warranty work, exchanges whatever. It may or may not be an issue but im sure many of you have noticed that clockwork will pop up whenever the phone is powered off with a usb connection present. Which in most cases would be an immediate red flag for those of you needing work done. This will completely restore your phone and remove the clockwork recovery flash.
Update: I no long have an Aria to try this with but if you guys are running into issues try this as well.
winsettr said:
I'd like to suggest that you update the first post to include a link with the last 2.1 RUU, seeing as the 2.2 RUU breaks the ability of future rooting (for now). I have uploaded what I believe is the updated RUU 09142010 to MegaUpload, linked below. Just thought this might help
http://www.megaupload.com/?d=XXYBORR6
Click to expand...
Click to collapse
1.) Download ATT Original Shipped ROM file from here:
http://www.htc.com/us/support/aria-att/downloads/
2.) Disconnect USB connection to phone.
3.) Power down phone
4.) Boot into Fastboot Menu (hold trackpad on start)
5.) Insert USB
6.) confirm that the phone shows "FASTBOOT USB"
7.) Run downloaded exe file
8.) Process will take a few min at the end you should have a 100% restored and unrooted phone.
It may seem self explanatory now but I was running into issues getting the HTC tool to communicate with the phone and it would fail whenever trying to send the phone into the bootloader. Thought I would just save you guys the headache.

thanks for your solution. was thinking about unrooting my phone and exchanging my aria for a samsung captative...

thanks man. doubt i'll do this, but i might need this just incase ATT and HTC actually come through with a stable update to froyo 2.2 within the next couple months.

I think it will be safe to assume that said 2.2 ROM will begin floating around in a rooted form not before too long, and will be flashable via recovery.

this is great info to have. great work.

???
has anyone actually tried this? because my pc dosent recognize phone when i try

bred904= said:
has anyone actually tried this? because my pc dosent recognize phone when i try
Click to expand...
Click to collapse
install Android SDK USB drivers first

??
i think i did... i installed something from google called android-sdk. and when i connect my phone in bootloader i can see fastboot change to fastboot usb and my pc says driver successfully installed. but when i run the .exe file it never sees my phone. also htc sync wont connect and neither will droid explorer. thanks

i agree with bred, can't seem to restore the original rom. it doesn't recognize it during the process

I have tried this method on 2 computers and the exe can NEVER find my phone.
I have installed the SDK USB drivers, my computer sees the Android 1.0 device and sees it as the HTC booloader. And I see FASTBOOT and FASTBOOT USB when unplugged/plugged.
----UPDATE 2010-07-23----
After further research I was able to determine that even with the device NOT in FASTBOOT mode, that adb couldn't see it, so I thought it might be a driver issue.
I've gotten my computer to recognize the device when it's booted normally. But when put the device in FASTBOOT or the BOOTLOADER, adb can't recognize it and I can't get the recover exe to recognize the device, regardless of mode.
I have the latest clockwork recovery installed and I would like to get everything back to factory to exchange for a captivate.

theres no way to do a nandroid backup or anything like that? curious because i was going to take mine back tomorrow to exchange for the captivate as well. i bought mine from radioshack so i might try my luck and just return it rooted . i did the trade in program with them with my iphone and it was jailbroken and they still accepted it. i dont think i would try that with at&t though... worse comes to worse just return it and say it was like that when you got it! maybe an at&t employee messed around with it before you bought it. they cant prove it was you.

Can anyone confirm this works? Just in case. This might be something I will need to do quick fast and in a hurry in the morning. And I'm hoping that if it comes down to this I won't have any issues.
Sent from my HTC Liberty using XDA App

I have been thoroughly unsuccessful in getting this method to work.
I have tried it on 3 different computers and I can never get the HTC OriginalShipRom.exe to find my phone.
I have tried following the instructions to the letter, I have also tried plugging in while booting the phone into various menus (HBOOT, FASTBOOT, and regular booting), which was advice given to me in the IRC room.
I'm plugging the phone in right after I click "Next" on the "Plug your phone into the usb port" right as it shows the "Verifying data on your PDA" window. I have tried with the phone in HBOOT, FASTBOOT, and while booting the phone, none of these seem to work.
I've also tried it with just plugging the phone in and running the exe. Nothing seems to work. People in the IRC channel are claiming successful factory restores, but I can't seem to get it to work.
So can someone please update the first post with more thorough instructions? Because those instructions don't seem to work.

The following instructions came directly from the HTC webiste for restoring the original state of the phone.
1. Download and save the HTC Aria™ Original Software to your PC.
2. Power your device off.
3. Connect your device to your PC via the data USB cable.
4. On the device, press and hold the Volume Down and Power Button until you get the bootloader screen (a white screen with 3 Androids on the bottom).
5. Press the Power Button once to enter FastBoot mode.
6. Locate the HTC Aria™ Original Software that you downloaded and double-click on the file to launch the RUU Wizard.
7. Follow all of the RUU Wizard instructions shown on your PC.
8. Once the update is complete, click Finish in the RUU Wizard and the device will reboot.
9. Once the device reboots it will run through the Customization Process; this must be allowed to complete.
10. Once the Customization process is complete, the device is then ready for use.
I hope this helps. I haven't tried it yet, but would like to know if this works in case I need to do this as well.

OutsiderWV said:
The following instructions came directly from the HTC webiste for restoring the original state of the phone.
1. Download and save the HTC Aria™ Original Software to your PC.
2. Power your device off.
3. Connect your device to your PC via the data USB cable.
4. On the device, press and hold the Volume Down and Power Button until you get the bootloader screen (a white screen with 3 Androids on the bottom).
5. Press the Power Button once to enter FastBoot mode.
6. Locate the HTC Aria™ Original Software that you downloaded and double-click on the file to launch the RUU Wizard.
7. Follow all of the RUU Wizard instructions shown on your PC.
8. Once the update is complete, click Finish in the RUU Wizard and the device will reboot.
9. Once the device reboots it will run through the Customization Process; this must be allowed to complete.
10. Once the Customization process is complete, the device is then ready for use.
I hope this helps. I haven't tried it yet, but would like to know if this works in case I need to do this as well.
Click to expand...
Click to collapse
My problem is with step 3. The second I plug my powered down Aria into the computer via USB, it powers on and goes directly into Clockwork.
If I boot the device into FASTBOOT, then plug it in, and then run the exe, it says it can't locate the device.

If you had flashed the unrevoked clock work you will not be able to plug your phone into the computer while its turned off. Your best bet is to boot into fastboot then plug in your phone. And try to do this under linux since there is no need for drivers.
Sent from my HTC Liberty using XDA App

farquep said:
If you had flashed the unrevoked clock work you will not be able to plug your phone into the computer while its turned off. Your best bet is to boot into fastboot then plug in your phone. And try to do this under linux since there is no need for drivers.
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
Hi farquep, can you give me instruction on how to use linux what's the command line?? thanx

If you do it under linux, just download the file and run it like any other program in any other operating system. Although you will have to let the file run as an executable under permissions. I don't know if you need to install WINE which will emulate windows programs. There should be no need for terminal scripts.
Sent from my HTC Liberty using XDA App

Doesnt recognize my device at all. If I'm returning to insurance company, should I even bother taking off clockwork? I already have the replacement.
EDIT:
Update:
Just worked for me. I had to install aria_shipped_rooted_signed.zip first then HTCAriaOriginalShipROM.exe recognized the phone.

SysAdmNj wrote:
> I had to install aria_shipped_rooted_signed.zip first
perhaps that can be added to the original instructions.
the archive can be downloaded from here

[Q] Corrupt Bootloader

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.

"Communications with phone unexpectedly interrupted" error: Revolutionary

I saw a similar issue in the EVO 3D forum, but nothing that helped my situation.
I run revolutionary on windows vista and everything seems to be working fine until it restarts and goes into bootloader, then revolutionary gives the error that "communications with phone unexpectedly interrupted. Press (almost) any key to exit." I have tried many times and still the error. I have left it at charge only, ive set it to HTC sync, and I have tried it with turning fast reboot off. Still not working. Any help would be greatly appreciated! Thank in advance.

It's normal. Remove the phone, reboot it and run Revo again. It'll fail each time it tries to reboot but running it again does the stages one at a time. It'll eventually say you have root and do you want to install CWM

It happened with me many time....(NOTE: Do "DISABLE Fastboot" & "ENABLE Debuggin").
Try it again. When it boots into bootloader, you will eventually see on top "S-OFF" and the name "Revolutionary" as well. My Hboot version was totally different from the one mentioned on the "Guide to S-Off,Root,Flash CWM Recovery", But I did Root and flashed few ROM's till now. As soon as you instal CWM, install ROM Manager, Update the CWM and reboot into recovery and make a BACKUP(To be on safeside,as it was useful for me)
Good Luck.

Thanks. Ill keep trying and hopefully itll work eventually like you guys said.

First upgrade to Windows 7 But yeah, like the other 2 two guys said, just keep trying
Sent from my HTC Sensation Z710e using Tapatalk

ok ive continued trying over and over again and still nothing at all. its still stuck at the first part. i have usb debugging on and fast restart off. whats the better way to have the connection, charge only or htc sync cuz ive seen both

icepikk said:
ok ive continued trying over and over again and still nothing at all. its still stuck at the first part. i have usb debugging on and fast restart off. whats the better way to have the connection, charge only or htc sync cuz ive seen both
Click to expand...
Click to collapse
HTC sync was the only way it worked for me, on the the third loss of communication it worked, s off. As others stated, keep trying, it works.
Sent from my HTC Sensation 4G using Tapatalk

Please Make Sure you have HTC Sync uninstalled and Droid Explorer uninstalled.
Did you check the Post #2 of http://forum.xda-developers.com/showthread.php?t=1192300

icepikk said:
ok ive continued trying over and over again and still nothing at all. its still stuck at the first part. i have usb debugging on and fast restart off. whats the better way to have the connection, charge only or htc sync cuz ive seen both
Click to expand...
Click to collapse
Try putting it to charge only, fastboot off and debugging on.
Try it 2-3 times.. eventually it gives s-off. Then you can install recovery by booting the phone & putting PGxx.zip on your sdcard. Then turn off the phone and boot to bootloader (Vol - and power) press vol + when it asks for update.

I had the same problem on the 3VO. When I disabled the fastboot option it worked!!

I was having this problem, USB debug on and fast boot off. No number of resets would cure it.
This is how I solved it, in case anyone is having the same problem:
The application reset the phone a second time, at which point it would get the error, I was left in the boot menu with S-On and a sad expression on my face.
During the first reboot into the boot menu, I quickly selected 'FASTBOOT USB' (I think it was vol down once, then power button). It then started processing the ZIP file before the application could reboot it a second time.
The application will still get the same error, however on your phone, you will now have S-Off.
Disclaimer: I have no idea what I'm doing, as evidenced by my post count of 1. It seems to work fine, but my phone may explode in 30 minutes time, I have no idea.

press power key
when it asks for the fastboot second time, just press the power key once and u will get the s-off

after s-off...how can we push recovery and flash su zip...for root...

sorry guys, but I just can't get this to work. I'm having the exact same issue
as, well a lot of people. "Communications with phone unexpectedly interrupted"
I got a brand spanking new Sensation. (if that could be part of the problem)
I've scowered the internet for a solution and tried just about anything I can find.
- Phone is set to USB debugging.
- fastboot is off
- set to charge only
- sync is uninstalled
- all drivers are installed
I've tried every possible combination of the above as well.
I've tried "when it asks for the fastboot second time, just press the power key once and u will get the s-off"
for the "Try it 2-3 times.. eventually it gives s-off" I just completed my 25th try,
and still no luck.
What the f**k is going on here? I'm no noble prize winner, but I've done
way trickier stuff than this.
any ideas?
Thanks guys,

I think this error message only applies to 1.17.0008 only...I did it successfully only by following this:
1. Disable Fastboot
2. Enable USB Debugging
3. Whenever the message says "waiting for..." unplug the usb fast...after the phone reboots...plug it back it...it will load a few seconds then it will say "waiting for fastboot etc." and keep repeating it (unplug USB wait for reboot before plug back in) till "waiting for fastboot (once moar)" and you will see S-OFF!!!

Hello Guys,
I solved this issue when I rooted my HTC desire using Unrevoked..
every time the desire rebooted, then the unrevoked said that " Communications with phone unexpectedly interrupted "
What I did is that,
- Phone is set to USB debugging.
- I couldn't find (fastboot) in my mobile, I just forgot about it.
- set the mobile to sync only when connected with usb cable.
- HTC sync is uninstalled from my computer.
- my computer recognize the device when it connected with usb cable otherwise you need to download some drivers (google it).
- then I connected my desire to the computer using the usb cable and start the unrevoked software.
- the unrevoked works and download some files then said that waiting for device to reboot. my device is rebooted.. when the logo of HTC started to appear in my mobile and just before the mobile completely works after rebooting, I have unplugged the usb cable from the desire..
- the unrevoked software still saying that "waiting for the device to reboot and it may take few mintues" !!
- when the desire is completely works and ready to use I have plugged it again to the computer and choose sync mode in very fast way before the unrevoked software detect it.
- then the unrevoked software start to download some files on the deasire and reboot it again for the second time and said that " waiting for device to reboot" .. in same way in have unplugged the usb cable after the HTC logo appears before it completely start and plug it again when the desire is completely working and ready to use and to respond.
- then the unrevoked software downloaded more files and said that " Done successfully" .
When I used this method, I have rooted and flashed my htc desire mobile and It is working fine. I just installed some custom roms on my mobile from the sd card using ClockworkMod Recovery v2.5.0.7 and it is working great..
I hope this will help somebody getting same problem.
Greeting from Saudi Arabia.
Mkman

AussieMikey said:
I think this error message only applies to 1.17.0008 only...I did it successfully only by following this:
1. Disable Fastboot
2. Enable USB Debugging
3. Whenever the message says "waiting for..." unplug the usb fast...after the phone reboots...plug it back it...it will load a few seconds then it will say "waiting for fastboot etc." and keep repeating it (unplug USB wait for reboot before plug back in) till "waiting for fastboot (once moar)" and you will see S-OFF!!!
Click to expand...
Click to collapse
Thanks alot.I was same problem and done that way....

AussieMikey said:
I think this error message only applies to 1.17.0008 only...I did it successfully only by following this:
1. Disable Fastboot
2. Enable USB Debugging
3. Whenever the message says "waiting for..." unplug the usb fast...after the phone reboots...plug it back it...it will load a few seconds then it will say "waiting for fastboot etc." and keep repeating it (unplug USB wait for reboot before plug back in) till "waiting for fastboot (once moar)" and you will see S-OFF!!!
Click to expand...
Click to collapse
It applies to Hboot 1:18.0000 as well. However in my case, no amount of plugging and unplugging will fix the problem...
Edit: Solved by running on Win 7, outside of the VM where I usually do my phone stuff with adb installed ect... So not sure if adb was the issue or that the VM is WinXP. Anyway, seems clean install of drivers without adb installed fixed it.

try to install adb, it works
When I was rooting and s-off an htc desire on linux using revolution. It fails every time on "waiting for fastboot...", then exit with "communication with phone unexpe...".
I have adb installed with android sdk. however, i haven't started the daemon. The last time I use "adb devices" to check the connected device, this also enables the adb daemon. Then everything just goes well and i get s-off.
Remember to install adb and start it by executing "adb devices"

icepikk said:
I saw a similar issue in the EVO 3D forum, but nothing that helped my situation.
I run revolutionary on windows vista and everything seems to be working fine until it restarts and goes into bootloader, then revolutionary gives the error that "communications with phone unexpectedly interrupted. Press (almost) any key to exit." I have tried many times and still the error. I have left it at charge only, ive set it to HTC sync, and I have tried it with turning fast reboot off. Still not working. Any help would be greatly appreciated! Thank in advance.
Click to expand...
Click to collapse
i had same issue when i was using a VM windows machine, once i tried with a physical win machine it worked like a charm.

lg mytouch c800 bricked?

hi im pretty new here a friend of mine gave me her lg c800 mytouch to try and fix it for her.. not sure what she did she said she rooted the phone and the root was successful but i have a good idea that she doesnt know what she was doing..i will post a pic of the error screen im getting. but it says
E:Cant find misc
E:cant find misc
Finding update package...
E:unknown volume for path [sd:/download/adb_fastboot_and_other_tools.Zip]
E:Cant mount SDCARD:/download/adb_fastboot_and_other_tools.zip
Installation aborted
facory reset failed
restart factory reset..
now im far from a pro at this i know a lil more about computers and Ios devices..but ive rooted a few phones and to me it looks like she unzipped adb fastboot on her phone from her sd card??
ive tried holding F..A..vol down..and power..Nothing..
ive tried volume up .volume down and power still nothing..
BUT if i hold E..vol UP and power it brings me to a white screen that says S/W update
the big problem is the phone wont stay on long enough to do anything on the computer it stays on 3 sec. then reboots to same screen (computer says phone is unplugged) then phone just keeps restarting.
but the phone WILL stay on when i put it on the S/W update screen..but computer wont recognize the phone at all on that screen
ive tried the adb and fastboot commands but the phone wont stay recognized..it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
well thanks ahead of time if anyone has any input or solution
and hopefully all this will make sense to someone lol
i think this pic will work.. if not ill try again

any ideas please?? or am i completely out of luck?

When you say:
delilah25 said:
it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
Click to expand...
Click to collapse
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?

post-mortem said:
When you say:
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?
Click to expand...
Click to collapse
Yes In Adb device list it shows the phone and then says recovery..but after that I don't have enough time to type any other commands ..the phone is also recognized in "my computer" as removable device then when the phone restarts seconds later it says device unplugged ..and just keeps restarting on its own till I remove the battery...I just read on the forum in a post that Adb will recognize the phone if it's off but I remove the battery and put it back in and plug in USB and phone turns on and keeps restarting won't even let me turn it off!! I'm losing patience with this thing lol
But I don't get why the error mentions fastboot? Not my phone so if it's not fixable I don't really care but I'm just the stuborn type when it comes to fixing electronics ..again thanks ahead of time to anyone that helps cuz I'm completely lost on this one

Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.

i have the same problem
post-mortem said:
Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.
Click to expand...
Click to collapse
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:

diabolus ae said:
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:
Click to expand...
Click to collapse
Normally, if you want to flash a custom recovery through fastboot, people will tell you to run 2 commands:
fastboot flash recovery nameofimagefile.img
fastboot reboot recovery
Since you don't have time to execute those 2 commands, you can tell it to just boot from the .img file, without flashing over your current recovery. (This is actually proper form, as you can test if the .img file works properly without damaging your existing recovery.) The way you do that is to 1st copy a recovery .img file to the root of your SD card, then execute the following 1 command:
fastboot boot nameofimagefile.img
Since you only have ~3 seconds, type the command in, and wait for the right instant to hit enter on the keyboard. If the command is successfully sent to the phone, it will reboot into that .img.
See if that works for you. Good luck.

RUU Error 171 Stuck on waiting for boot loader

As the title says, RUU attempts booting my phone but it never comes back on. Even selecting restart boot loader in fastboot or a command it doesn't power itself back on. I have read through other forums and nothing has worked for me yet.
EDIT: I should probably clarify fastboot usb WORKS. Ruu must see my phone considering it detects the ROM version and turns the phone off in attempt to reboot. Anything that I do that requires a reboot doesn't work. I have tried unlocking the bootloader again, everything is fine until it comes to rebooting then I must turn the phone on myself and nothing changes...... IT DOESN'T REBOOT ITSELF therefore seemingly nothing wants to work. And the HTC boot screen is gone??
More background information: http://forum.xda-developers.com/showthread.php?p=39046436#post39046436

What we're your steps exactly? Did you relock your bootloader

a box of kittens said:
What we're your steps exactly? Did you relock your bootloader
Click to expand...
Click to collapse
Yes I did through fast boot with the oem lock command. I've tried installing RUU with a Windows 7 laptop (has HTC sync software) and Windows 8 desktop (basic drivers). Both failed, tried using Windows XP/Vista in compatibility modes and running as an admin with the same results.

Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.

iElvis said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
Click to expand...
Click to collapse
No luck. And I believe it does see the phone in the beginning of the installation. It makes it reboot to the boot loader and that's where it loses the connection. The phone just isn't booting itself back up. I appreciate the reply, if you have anymore ideas please let me know.

Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?

iElvis said:
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
Click to expand...
Click to collapse
Re-downloaded RUU and still no go. And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.

Does anybody else have some more ideas?

Okkoto said:
And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Click to expand...
Click to collapse
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.

redpoint73 said:
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
Click to expand...
Click to collapse
Fastboot does see it but adb does not. And what I mean by rebooting the phone in my last post is RUU attempts rebooting it from the boot loader which does turn the phone off but it stays turned off. I've used other commands to reboot the phone from the fastboot screen and those too turn off the phone then again it doesn't come back on like a reboot should do.

I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.

Okkoto said:
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Click to expand...
Click to collapse
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.

DvineLord said:
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
Click to expand...
Click to collapse
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.

i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.

Okkoto said:
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
Click to expand...
Click to collapse
when you say it shows connected through fastboot what do you mean?
how are you getting the device into fastboot - through recovery??
oh, and what was on your device before you tried loading the RUU?

kkm68 said:
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Click to expand...
Click to collapse
Yes this + if you're on a usb3 port try usb2. Also make sure you're using the cable that came with the phone as I understand other cables may cause issues like this. Also, avoid using a hub or usb extension.

Solution to error 171
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!

diegoyabishh said:
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
Click to expand...
Click to collapse
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.

jondon156 said:
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
Click to expand...
Click to collapse
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita

Heisenberg said:
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Click to expand...
Click to collapse
hi all..
facing same problem with HTC Desire 816 n 4g... have anyone got any solution??
plz pass it..
thank you