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
Hi to all,
Been here for a while and every time i log here in XDA (O3D forum), I always see new people bricking their newly bought O3D (stuck on LG Screen..., rebooting only to cwm recovery.., etc..etc..). If you got into a situation just do the search thing before posting a new topic which is already been posted because our forum (O3D Community) is still small so searching wouldn’t be a problem and there’s no need for a dig yet when reading all the topics posted here. All i can say is for all the people who just bought O3D always remember this "If it aint broke then don’t fix it" you will just end up voiding your warranty,
if there’s an update don’t try to push it on your warranted device, try to check first if the update is applicable to your device (country or region) because we all know that LG only released O3D in Europe so if you are in that place and check that your devices have an update, go grab it, but when it fails always call LG Europe (because you have a warranted device and they will assist you) and explain to them that you are experiencing difficulties in updating your unit, and for everyone else who is not in Europe (like me were my unit is not warranted)be very careful if you want to forcefully push that update to your unit (v10b, v10d or even cwm 4.0.0.9) because me i already bricked my device 3 times were i end up booting only in LG and nothing follows, the other is booting only to CWM again and again, and the last one is after unbricking the device and setting everything then when rebooting the unit it will end up stuck at the LG original android recovery system <3e>menu.
Note: Do this procedure at your own risk, i repeat "AT YOUR OWN RISK", its your unit so its your responsibility, you've been warned, i myself grab that risk and now I’m happy with my unbricked O3D (v10d July, 8, 2011 with fully working CWM 4.0.0.9), all the tools we need are here at XDA so there will be no problem getting those tools.
Ok enough about nonsense(hahaha), lets go down to business. As what the Title says, here we go.
Requirements:
This method will only work in WINDOWS XP MACHINE, i have tried it in Vista and Windows 7 but it will just hung.
I assume that all the necessary drivers are already installed from your machine because without them you can’t bricked your O3D. If by any means you don’t have it, just grab it from http://www.lg.com/uk/support/mc-support/mobile-phone-support.jsp and click the download link save it then run it after installing, it will run automatically, then do the following:
1. Go to Customer Support ---> Application, Manual & USB Driver Download.
2. Enter you IMEI then click the Search button.
3. After Searching, it will list two files form the File List, double click any of those file (me, i choose the file with divX converter)
4. After downloading, it will extract its content to C:\LGP920
5. Go to this directory C:\LGP920\USB_Driver, and double click LGUnitedMobileDriver_S4981MAN33AP22_ML_WHQL_Ver_3.3
6. Let it finish then if it ask to restart your pc, do it.
7. Optionally you can install the LGPCSuite, it can be found in c:\LGP920\LGPCSuite\, just double click the LG_PCSuiteIV_Setup.exe and follow the instruction.
Now that we have installed the drivers for O3D, we can move on to the next instruction.
Make sure to follow the instruction carefully and proceed if you know what your doing.
I have edited nikhil4186 and victortangocharlie post (Original thread: http://forum.xda-developers.com/showthread.php?t=1060121)
1. Detach all other peripherals from your PC. Exit all running applications on your PC especially other PC suites if any. Also exit running programs from the notification bar on the desktop. (Also uninstall Nokia or other phone drivers & microsoft visual ++ runtime environments - not an essential step.)
2. [IMPORTANT] Disable 'LGE Virtual Modem' in PC's Device Manager. (In your Windows operating system, go to Control Panel > System > Hardware > Device Manager > Modems > Right click on LGE Virtual Modem and click Disable.).
3. Remove the Micro SD from your O3D.
4. Download the KDZ rom v10b_00 posted by Fab985 : http://forum.xda-developers.com/showthread.php?t=1155874
(v10d_00 is already available but this method is only tested with the v10b_00 rom, so if you wanna try your luck, its up to you)
5. Download the KDZ updater - http://forum.xda-developers.com/showpost.php?p=8651505&postcount=1
6. Extract it, then run the msxml.msi
7. Now the next step will be crucial because you need a full battery (for safety of course if you don’t want your unit to die while in the middle of the unbricking process) and you will put your unit in emergency mode (by pressing the power button and the volume up button), here’s how you will do it.
Case A. (This is my Case)
If your O3D can boot but only in CWM, charge it (me, i charge mine for 3hours in cwm), you wont see a charging status but you will feel your battery getting warmer.
Case B. (Never happen to me)
If your unit is just stuck at LG logo, try to charge it too and see if your battery is getting warmer, if not, better find another way to charge your battery or a friend who has O3D and borrow the battery.
Once everything is ok proceed to step 8.
8. Open Device Manager and under Modems check if you really disable the LGE Virtual Modem, if it is already disabled don’t close Device Manager, we will need it on the next step. Make sure you can see your Device Manager window and your modems devices are expanded (were you can see the disabled LGE Virtual Modem)
(THIS IS THE TRICKY PART AND YOUR O3D WILL JUST STAY BLACK SCREEN)
9. Plug your USB cable to your pc and then plug it to your phone then enter Emergency MODE (power button plus volume up button) This step is very tricky (me, i tried it several times before it detect my O3D as LG USB modem).
First when your pc detects your O3D, it will detect as OMAP4 then it will look for its drivers, just cancel it, then another device will be detected, if you successfully entered Emergency mode, your O3D will be detected as LG USB Modem, this modem should stay, if it disappear then you failed to enter the emergency mode correctly, try it again before continuing to the next step.
10. Run KDZ_FW_UPD.exe from the extracted folder.
11. Put the following settings:
Type : 3GQCT PhoneMode : DIAG
12. Under the KDZ File, choose the KDZ file you've downloaded from Fab985 post (v10b_00)
13. Press the Launch software update. (this part will take time because it will extract the kdz file into cab file, it took me 15 to 20 mins before it proceed to the updating process)
14. Once updating has started you will encounter this message:
CDMA: wPrama = 2004, IParam = 1
Model Dll Msg Not Found(2004, 1)
This message will come out from 1 to 100 counts:
CDMA: wPrama = 2004, IParam = 1
Model Dll Msg Not Found(2004, 1)
CDMA: wPrama = 2004, IParam = 2
Model Dll Msg Not Found(2004, 2)
And so on till:
CDMA: wPrama = 2004, IParam = 100
Model Dll Msg Not Found(2004, 100)
(Note: This message is case to case because i experienced diff counts then the LG USB MODEM disappear from the device manager list, first attempt count 64 then LG USB Modem disappear from the list, the kdz flasher stops from count 64, waited up to 10 minutes but nothing happens so tried it again from the enter emergency mode step, second attempt count 76 LG USB modem disappear but after a while kdz flasher still continues up to 100 counts then it stop there, waited for 5 minutes nothing happens so decided to remove my device and turn it on and viola it booted to LG original Android system recovery <3e>)
15. After you reach the 100 counts, the process is done, the LG USB modem from the Device manager will be gone, but don’t remove yet your phone to reboot it, try to wait up to 5 minutes before disconnecting your phone.
16. Turn on your O3D, if it boots in LG original android recovery, just choose the wipe data/factory reset, then reboot system now. Then if it is successfully booted to android continue to setup your device but after the initial setup, don’t install or do anything yet, reboot your device again then see if it will reboot back to android, if yes, you’re done, your O3D is again alive and don’t bricked it again, if not proceed to step 17.
17. If it comes back again to recovery after booting then wipe data/factory reset, wipe cache partition then reboot system now.
18. Turn on your O3D, then if it is successfully booted to android continue to setup your device but after the initial setup, don’t install or do anything yet, reboot your device again then see if it will reboot back to android, if yes, you’re done, your O3D is again alive and don’t bricked it again, if not proceed to step 19.
19. If it comes back again to recovery after booting then wipe data/factory reset, wipe cache partition, and lastly wipe nv dynamic partition then reboot system now. (this part resolve my rebooting issue)
20. Turn on your O3D, then if it is successfully booted to android continue to setup your device but after the initial setup, don’t install or do anything yet, reboot your device again then see if it will reboot back to android, if yes, you’re done, your O3D is again alive and don’t bricked it again, if not I guess it’s the end of the line for now.
Sorry for this very long instruction. If it helps you I don’t have a beer fund because I’m not a dev. but a simple hit with thanks will do.....
TIPS NOT RELATED TO UNBRICKING:
Rooting:
Run SuperOneClick as Administrator, before clicking Root, click first the Driver Check and if no problem has been detected, no more settings is required just click the Root button then wait until it says done or finish.
ClockWorkMod:
After rooting, download rom manager from the market, after the install run it and tap Flash ClockworkMod Recovery (4.0.0.9), once successful you may now backup your current rom before you mess again with it, since I installed cwm in my O3D I never use the buttons to boot with it(power button plus volume down button), I always use the menu's with the rom manager to boot into or backup or restore or flash in CWM.
Upgrading:
For safety purposes, if you have a warranted device and then an update pops out, always do a fresh start, what I mean is if you already rooted your device and installed CWM, better removed it first before updating your O3D so when things goes wrong from your update process you can always call LG for it to be fix eliminating the needs to post something like “Help I brick my O3D and I can’t bring it to LG because I installed CWM blah blah blah etc.. etc…”, got the point so be responsible.
For the Mod: Sir if my post will violate something feel free to removed this post. more power XDA!!!!!
Many thanks to the following:
Aremcee
Renegade_Rules
Fab985
ik911
nikhil4186
victortangocharlie
and everyone here at XDA....
thanks for the info but does not work with clockwork installed and update over phone and stuck at firmware updating screen people.. waiting for a solution still
wuper said:
thanks for the info but does not work with clockwork installed and update over phone and stuck at firmware updating screen people.. waiting for a solution still
Click to expand...
Click to collapse
Did you follow the whole step, I know its a long process and it work with me, just follow everything and when you are in step 9 were you need to enter emergency mode,its a tricky step,make sure LG Mobile update is not running completely,open your pc device manager and expand the modems,try to remove the battery then press volume up and power button, put the usb cable then put back the battery,it will vibrate then your xp machine will detect it as omap4 device just cancel it but don't de-press the volume up and power button,then after a while it will vibrate again check if you see LG usb modem in the device manager,once you saw it and it stays,it means you successfully entered emergency mode then that will be the time you will run the kdz flasher and follow the succeeding steps.
Sent from my unbricked LG-P920 using XDA Premium App
bro I tried it with lg mobile modem disabled lg virtual modem disabled both are not disabled both are disabled but none of them make sense. Model Dll Msg Not Found(2001, 0)
is written and lg mobile driver gone but the phone does not reboot both 10d and 10b tried I restarted manually and it opens with fw update screen
I also get a "Get Chip Type error" when kdz reads phone information
Renegade_Rulez, you have the same problem did u try these methods?
wuper said:
I also get a "Get Chip Type error" when kdz reads phone information
Renegade_Rulez, you have the same problem did u try these methods?
Click to expand...
Click to collapse
I have bricked my phone numerous times, and in many imaginative ways. The above instructions are pretty much what I do whenever it gets stuck in some non-functional mode.
I tried this way like 30 times during the last week, I just got back from holiday and I just tried it on a Win XP machine and it's always the same it flashes and it never reboots, V10B/D doesn't matter... After flashing I manually power it on, and only get the Firmware update screen and it hangs there forever... I called LG today waiting for a replacement.
@aremcee
Sir thanks for confirming that this method really works.
@wuper @renegade_rulez
Are you doing it in xp machine, if you run it in Windows 7 the process will just fail. Only disable the LG virtual modem from your pc device manager and completely exit LG PcSuite and LG Mobile update. Make sure your xp machine detects your O3D as LG USB MODEM and not omap4 device, the detected LG usb modem should stay in your device manager under modem and it should be enable then you can now start kdz flasher. Will try to investigate what causing your O3D not to flash using the kdz flasher and if I have time will upload a video on how to properly enter emergency mode.
@all
Thanks for reading this, if you have a question just post it here and will try to answer it back as knowledgeable as I can.
Sent from my unbricked LG-P920 using XDA Premium App
if you can try this and make the phone work that means we are doing sth wrong:
1) install clockwork via rom manager
2) install update via settings telephone software update
3) after installing this update the phone stuck at clockwork recovery and all reboot is turning to this screen
4) flash 10b or 10d through kdz or lg mobile, it will stuck at firmware update screen as picture shown as attached
we try as u said on xp machine several times and device manager opened lg usb modem was there till the process finished after that it get lost and I waited 5 minutes and exit kdz and start manually, nothing..
(the attachment picture is turkish, it is written firmware is updating above and the phone will restart after finishing firmware update below)
PS_U_A_John stated in other topic he can flash a phone that is clockwork installed, that shows clockwork is not the problem, I think clockwork and our installed phone update and after flashed kdz rom are colliding each other and phone could not restart.
wuper said:
if you can try this and make the phone work that means we are doing sth wrong:
1) install clockwork via rom manager
2) install update via settings telephone software update
3) after installing this update the phone stuck at clockwork recovery and all reboot is turning to this screen
4) flash 10b or 10d through kdz or lg mobile, it will stuck at firmware update screen as picture shown as attached
we try as u said on xp machine several times and device manager opened lg usb modem was there till the process finished after that it get lost and I waited 5 minutes and exit kdz and start manually, nothing..
(the attachment picture is turkish, it is written firmware is updating above and the phone will restart after finishing firmware update below)
PS_U_A_John stated in other topic he can flash a phone that is clockwork installed, that shows clockwork is not the problem, I think clockwork and our installed phone update and after flashed kdz rom are colliding each other and phone could not restart.
Click to expand...
Click to collapse
Hi wuper,
Can you try after flashing then turn on your device to recovery by pressing volume down + power button, or remove your battery then put it back while pressing those buttons, will it go to android recovery system <3e>?, if yes try to wipe everything then reboot. let me know. thanks.
Like wuper just told, mine is the same... It's not fixable in that way. Again this morning I tried on my XP pc and it's always the same. Just called LG again they will replace it within 24h we will see
update:
You cannot get into the recovery system, holding power + volume down the phone will power on and off again, releasing power when it boots and keeping volume down pressed gets the Firmware update screen.
same for me cannot enter recovery
Hi, I had a bricked optimus 3d, after the installing the cwm recovery I couldn't turn it on, it would always go into the cwm recovery, no mater how I turned it on.
So I followed your "how to" on an xp pc, and I was able to flash the v10b fw.
Everything went like you described it: the counter reached the 100, I waited about 6minutes after that to turn it on, after that it would go straight to the android factory recovery (the one with the blue letters), and to phone won't boot up.
So I made a factory reset, than reboot, but nothint happened, then factory reset and wipe cache partition, than reboot, but I was still getting the recovery.
Then I made a factory reset, wipe cache partition and wipe nv dynamic partition, and then reboot, but the phone instead of rebooting turned itself off.
I turned it on, but it said, that the battery was almost empty, and needs a recharge (strange, because it was fully charged).
I pluged it on the charger, and the sign of a totaly empty battery was showed.
I left it for a couple of hours and the hole night, but the empty battery sign was still there.
I tried to turn on the phone, it booted up normaly, everything was ok, the phone was working again, but the battery was completely empty.
I bought 2 original replacement batterys, but the result is still the same.
So, can someone help me what went wrong, why does any battery work?
Why won't they charge?
I think that it has something to do with the last item I wiped, the nv dynamic partition, because after that the phone hasn't rebooted, but turned off.
What sould I do?
And no, unfortunately I don't have warranty on my phone.
Zirowe said:
Hi, I had a bricked optimus 3d, after the installing the cwm recovery I couldn't turn it on, it would always go into the cwm recovery, no mater how I turned it on.
So I followed your "how to" on an xp pc, and I was able to flash the v10b fw.
Everything went like you described it: the counter reached the 100, I waited about 6minutes after that to turn it on, after that it would go straight to the android factory recovery (the one with the blue letters), and to phone won't boot up.
So I made a factory reset, than reboot, but nothint happened, then factory reset and wipe cache partition, than reboot, but I was still getting the recovery.
Then I made a factory reset, wipe cache partition and wipe nv dynamic partition, and then reboot, but the phone instead of rebooting turned itself off.
I turned it on, but it said, that the battery was almost empty, and needs a recharge (strange, because it was fully charged).
I pluged it on the charger, and the sign of a totaly empty battery was showed.
I left it for a couple of hours and the hole night, but the empty battery sign was still there.
I tried to turn on the phone, it booted up normaly, everything was ok, the phone was working again, but the battery was completely empty.
I bought 2 original replacement batterys, but the result is still the same.
So, can someone help me what went wrong, why does any battery work?
Why won't they charge?
I think that it has something to do with the last item I wiped, the nv dynamic partition, because after that the phone hasn't rebooted, but turned off.
What sould I do?
And no, unfortunately I don't have warranty on my phone.
Click to expand...
Click to collapse
Hi Zirowe,
Hmm thats strange, you and dnardz have the same problem, wiping the nv dynamic partition solved my rebooting issues and didnt experience this battery not charging problem, try to root your phone and install clockwork recovery 4.0.0.9 then reboot to cwm and full wipe your O3D including the battery stats, then charge your phone again and see if it is charging(maybe two hours), if it still doesn't work, download the v101d cmw rom by PUAJohn and restore it. Let me know
Zirowe said:
Hi, I had a bricked optimus 3d, after the installing the cwm recovery I couldn't turn it on, it would always go into the cwm recovery, no mater how I turned it on.
So I followed your "how to" on an xp pc, and I was able to flash the v10b fw.
Everything went like you described it: the counter reached the 100, I waited about 6minutes after that to turn it on, after that it would go straight to the android factory recovery (the one with the blue letters), and to phone won't boot up.
So I made a factory reset, than reboot, but nothint happened, then factory reset and wipe cache partition, than reboot, but I was still getting the recovery.
Then I made a factory reset, wipe cache partition and wipe nv dynamic partition, and then reboot, but the phone instead of rebooting turned itself off.
I turned it on, but it said, that the battery was almost empty, and needs a recharge (strange, because it was fully charged).
I pluged it on the charger, and the sign of a totaly empty battery was showed.
I left it for a couple of hours and the hole night, but the empty battery sign was still there.
I tried to turn on the phone, it booted up normaly, everything was ok, the phone was working again, but the battery was completely empty.
I bought 2 original replacement batterys, but the result is still the same.
So, can someone help me what went wrong, why does any battery work?
Why won't they charge?
I think that it has something to do with the last item I wiped, the nv dynamic partition, because after that the phone hasn't rebooted, but turned off.
What sould I do?
And no, unfortunately I don't have warranty on my phone.
Click to expand...
Click to collapse
try deleting batterystats.bin then rebooting.
Thank you, I will try it.
Will try it too..thanks Johnance17.
hefonthefjords said:
try deleting batterystats.bin then rebooting.
Click to expand...
Click to collapse
I've tried, but no luck, unfortunately, everything is the same..
hi,
It's strange what happens to you.
Have you tried this?
-Turn device off
-Take out batery
-Wait 5 min
-Re-insert battery
-do a hard-reset
-boot up device completly
-Turn device off
-plug-in charger (NOT USB-PC)
-Wait 1 hour
sorry I do not see much solution
It didn't work on mine also...restoring 10d and erasing battery stats..
I have spent the last couple of weeks reading up on rooting using adb. I successfully rooted my thunderbolt last night using two youtube videos by nat3mil. Everything went fairly smooth and I am now rooted but then I screwed myself.
I wanted to download a faster sense based rom using rom manager. I first tried lightningsense 1.8 or something like that. I rebooted and the phone wouldn't go past thre phone activation step of the phone setup. I thoughtt something was wrong with the rom, or I had to delete the old rom, so I backed up to the original rooted rom and then downloaded a cynogenmod7 rom and went back and deleted the first rom off of my card completely.
Cm7 booted fine, but I soon realized that I have no service. Data or net. I used googlr and the search function and found out that I also need to upgrade the radio seperately? From what I gather, I need to flash the mr2 radio only and not an entire ruu. Can someone confirm this for me and possibly point me in the direction of a downloadable file containing only the radio that I need? I don't have access to an adb equiped computer for a few days and the only two roms on me sd card require a radio that I don't have on my card.
Thanks for the help. I'm new to adb & obviously over looked a step or command.
without installing adb
Our computer is still in storage from moving. But I do have access to a computer close by. Just don't need to install adb unless absolutely nessesary. Once I find a downloadable file, I hook phone to conputer as disk drive, then move file to the root of my sd card and just reboot the phone using volume up+power?
I'm assuming that it's not possible to download the file directly to my wife's phone then put her sd card in my phone and flash it without a computer due to the fact that a computer is required in order to move the file to the ROOT of the phone?
The file needs to be on the root of the sdcard not the phone. You could do what you said with your wifes phone and swap the sdcard or you could use WiFi on you Thunderbolt to d/l. Radio links will be in the thunderbolt dev section or loonatiks sticky in q&a has a link to a page with a good list. Sounds like you need a MR2 or newer radio.
Sent from my HTC Thunderbolt
So the file doesn't need to be renamed? So leave the mr2 in the file name & flash from bootloader/recovery, search for file on SD card, probably in dcim or download folders and select file that says mr2 by pressing power button?
Just tried:
Installing update.....
Installation aborted.
Any suggestions?
It needs to be renamed to PG05IMG.zip
Oh yeah and you do NOT flash that from recovery. Bootloader and recovery are not the same thing. Thats why you got installation aborted. Power down the phone completely. Pull battery and then put it back in. Hold volume down plus power untill the white bootloader screen appears. You may have to scroll to bootloader with the volume keys and select by tapping the power button. Once there it will automatically find the PG05IMG.zip and ask you to press volume up to update. When its done it will say press power to reboot. Then when the phone boots you should be good.
Sent from my HTC Thunderbolt
i had been powering on while holding volume- and it was taking me to the white screen. i tried pressing the power button there and it quickly flashed to another screen and tried to flash a pg file and didn't work. the proccess happens so quickly that i can barely catch that it is a pgo5 file that doesn't work before it takes me back to the first white screen.
since that didn't work, i guess i misinpreted some misinformation from another site that said to flash radios from the CWMRecovery menue, so form the white screen I scroll down to recovery and hit power and it brings me to CWMRecovery v5.0.1.0. tried flashing from there several files, and all say unseccessful or aborted. I must have F*ed something up really good now, because in my fiddling around in CWMRv5, now no matter which of the restored roms i tried to flash (shows flashed successfully), when i reboot, they all take me back to the HTC screen and stays there. doesn't even attempt to load phone's menue or get to language/activation steps.
i thought that wipe data/factory reset from the CWMRv5 menue would take me back to the original rooted ROM, or at worste case, take me all the way back to the unrooted factory phone. Tried that, same thing, HTC menue for over 15 min straight and still nothing.
When turning on by holding power & volume- :...
When turning here is what i see on a white screen with three skateboarding droids on the bottom:
....................................................
MECHa XD ENG S-OFF
HBOOT-1.04.2000 (PG0510000)
MICROP-/
RADIO-1.16.00.0402w_1
eMMC-boot
Feb 23 2001,20:36:02
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
SYSTEM INFO
IMAGE CRC
........................................................................
would selecting the factory reset do anything useful, or would it be the same as selecting factory reset from CWMRv5 (which appeared to flash fine, but no results)?
First of all to get restore to work go to this thread and download CWR version 4.x.x. Version 5 is borked right now and won't restore.
If you download the file to a windows pc that is set up to NOT show file extensions(.exe, .zip, .bat, etc) leave out the .zip but make sure it is PG05IMG.zip EXACTLY (0 = zero) Put that on the root of the sdcard *not in any folders* and boot to the bootloader per usual. When you get there *STOP* *WAIT* don't touch.anything. In the list that says recovery, fastboot, etc if bootloader is not on the list you are already there and it will find the file. Sometimes it loads into fastboot first so you have to select bootloader manually. If bootloader isn't on the list you are already there. In the bootloader it should find the file and ask you to press vol up to update. This will get you a working Clockwork Recovery so you can restore backups.
This same process applies for radios.
If it is not finding the file you have it named wrong somehow. Most common mistakes are PG05IMG.zip.zip (because of hidden file extensions in Windows) or PG05IMG .zip (note the space before the .zip.) It IS case sensitive.
Edit: I forgot to mention if it does that check so quick you barley see it **it is not finding the file** There is a problem somewhere in the name or it is not on the *root* of the sdcard.
Sent from my HTC Thunderbolt
I've been having this problem for the past 2 days and has came to the point where I'm running out of clues.
The phone has been previously rooted with Acekit and flashed with MIUI. But since the ROM gave me problems (the phone would randomly restart on me), I decided to flash another ROM instead.
I tried CoreDroid, flashed it, it wasn't functioning correctly, so I switched to the newest MIUI version availiable, everything worked fine but for some reason...there's no sound when I call someone.
I figured I should probably reroot the phone again. So I downloaded the Acekit, ran it through, when it got the point where the White HTC screen popped up, it just got stuck there for like an hour.
I popped the battery, tried booting by Vol Down + Power, I get teh white HTC screen stuck on me.
I tried installing the stock AT&T mod, it wouldn't go through.
I tried rerooting it again, it'd eventually stop, my guess is that I'm not able to go to USB debugging. So I'm stuck here.
I did my research over this forum and on google, but unforunately it hasn't helped me too much.
Is there anything I can do just to get a functioning mod running? I just want the stock ROM at this point. If someone can help me it'd be much appreciated.
If you did your research and read the effen manual for the hack kit you wouldn't have tried to root your phone again with the hack kit.
Unfortunately I have never done this nor would I because I know better. I know I have seen answers to your problem before on the forum. Maybe it was a sticky in the General forum. If that doesn't help then enter the IRC channel like you were told in the hack kit thread and get the help needed.
Use genes s on tool to return to stock and then root again with aahk.
^
I'm assuming this is what you're talking about. I'm downloading the PD98IMG.zip right now and will be working on it.
http://forum.xda-developers.com/showthread.php?t=1208507&highlight=gene
I followed the instructions:
Code:
Do a nandroid and/or Titanium backup! It never hurts!
While still in ClockWorkMod recovery, do a "Factory Reset/Wipe Data". This is necessary if you've got an ext4 cache or CM7 dalvik-cache on /cache. If not it will cause boot hang after installation. EXT4 cache will not work with this tool. If your recovery has ext4, be sure you format the cache to EXT3.
Download from the URL below, copy to the SD card and rename to "PD98IMG.zip"
Reboot to HBOOT: Shutdown completely (disconnect USB if connected and pull battery if necessary) then while holding down the VOL-DOWN key, press the POWER key for about half a second. The phone should boot into HBOOT, check the PD98IMG.zip for consistency, then prompt you to install. Select VOL-UP to install.
Once installed, HBOOT will prompt you to reboot by pressing the POWER button. Do this.
The operating system in this tool is a stripped down CM6 install with only the minimum features necessary to run an apk. The apk for the tool will run after the HTC splash screen, then prompt you through the process. Depending on the speed of your SD card, the last step, copying the RUU to the SD card, may take several minutes.
Once successfully completed, the phone will automatically reboot to HBOOT and begin the process of installing the RUU. The only thing you have to do at this point is acknowledge the prompt to install by pressing VOL-UP. (Note: the RUU install may skip a couple of images during the install but this is normal.)
Once the RUU is installed, press POWER to reboot and your phone should be in 100% factory out-of-box condition.
I went into HBoot,
It automatically went to
Code:
SD Checking...
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nbh]
No image or wrong zipped image!
Loading...[PD98IMG.zip]
Wrong zipped image!
Loading...[PD98IMG.nbh]
No image or wrong image!
And then just went back without prompting me anything.
I basically am not able to reach to step 5
Make sure its on the root of your sd card, meaning not in a folder. Also make sure you didn't name it pd98img.zip.zip. if naming in windows the file extension could be hidden leaving you with the double zip. Basically its supposed to be a zipped file named pd98img.
turns out the downloaded file was corrupted. I downloaded again and it worked. Thanks guys!
I bought a HTC One S for T-Mobile USA. Has been working flawlessly. Today I got an OTA and my world is now upside down. I have spent 5 hours trying countless things to get my phone back up to no avail.
my phone stats:
hboot 1.09.0000
radio 0.16.31501s.16_2
open dsp-v28.1.0.32.0504
emmc-boot apr 2 2012,21:08:24
UNLOCKED
TAMPERED
How do I get back to square one and turn this phone back into something usable?
It has something called TWRP 2.1.7 installed on it and I have tried fastboot and a host of other things to remove it. I have even tried the thread on sending your phone back to stock but I can't access RUU because it won't load the driver. I have never rooted this phone nor do I believe USB Debugging was turned on before I accepted the OTA. I can communicate via fastboot in the command shell via a usb cable. The PC wont mound the SD card so I can't copy a new image and reboot this thing on a different rom and then send it back to stock.
I am about ready to throw it away because i can't seem to get a .zip file to it so it will run again (for putting a working build on it). There are no images to boot to. Somehow that got wiped and no backup was done. I don't give a poop if the data is whiped. Its all backed up via dropbox and exchange. I just want it up and running so i can use RUU and send it back to stock.
Any help would be appreciated.
Scuba_Luv said:
I bought a HTC One S for T-Mobile USA. Has been working flawlessly. Today I got an OTA and my world is now upside down. I have spent 5 hours trying countless things to get my phone back up to no avail.
my phone stats:
hboot 1.09.0000
radio 0.16.31501s.16_2
open dsp-v28.1.0.32.0504
emmc-boot apr 2 2012,21:08:24
UNLOCKED
TAMPERED
How do I get back to square one and turn this phone back into something usable?
It has something called TWRP 2.1.7 installed on it and I have tried fastboot and a host of other things to remove it. I have even tried the thread on sending your phone back to stock but I can't access RUU because it won't load the driver. I have never rooted this phone nor do I believe USB Debugging was turned on before I accepted the OTA. I can communicate via fastboot in the command shell via a usb cable. The PC wont mound the SD card so I can't copy a new image and reboot this thing on a different rom and then send it back to stock.
I am about ready to throw it away because i can't seem to get a .zip file to it so it will run again (for putting a working build on it). There are no images to boot to. Somehow that got wiped and no backup was done. I don't give a poop if the data is whiped. Its all backed up via dropbox and exchange. I just want it up and running so i can use RUU and send it back to stock.
Any help would be appreciated.
Click to expand...
Click to collapse
I hate to tell you this but if you never unlocked or rooted your phone, somebody did. Your device is unlocked and running a custom recovery therefore you cannot accept over the air updates and that is your problem. You did not buy your phone that way from T-Mobile so what did you really do to get to this point?
Behold_this said:
I hate to tell you this but if you never unlocked and rooted your phone, somebody did. Your device is unlocked and running a custom recovery therefore you cannot accept over the air updates and that is your problem. You did not buy your phone that way from T-Mobile so what did you really do to get to this point?
Click to expand...
Click to collapse
I never said I bought it as OEM. I also never thought to ask the guy I got it from if he rooted it or unlocked it.
Relocking the boot loader then running an RUU should fix the issue. Once you do that enter the recovery and wipe everything/factory reset.
Then if you are trying to run a custom ROM you should be able to mount your SD card and push one to the phone.
Sent from my HTC One S using xda premium
beats4x said:
Relocking the boot loader then running an RUU should fix the issue. Once you do that enter the recovery and wipe everything/factory reset.
Then if you are trying to run a custom ROM you should be able to mount your SD card and push one to the phone.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Great reply however I am short on knowledge on how to do what you have recommended. I don't know how to relock the boot loader nor can I run RUU because I can't get the driver installed. Any help would be awesome. Thank in advance. Sorry I'm a noob at this.
In the dev section there is an all in one toolkit that will execute the correct scripts for you. Download it, then run it. You may also need the HTC sync drivers installed on your computer.
Once you see that the bootloader is locked run the ruu.
And don't apologize for being a noob, I am too lol. We all need help to get started.
Sent from my HTC One S using xda premium
If you install HTC sync to your pc it should install the driver's you need. Then install the one s tool kit in developers section to relock. Then run ruu.
Also, anything you see in blue text is what you'll need to type, or copy/paste, to avoid any quote confusion.
Files You Need:
T-Mobile USA RUU file (mirror) - it's about 563 mb, and worth saving once you download it.
Extremely Important: If you're on another carrier you'll need a different RUU file - DO NOT try and run this RUU file, it could really screw you up. Go to this link to find the right RUU file.
HTC Drivers (mirror) - You probably already have the drivers installed if you're needing this thread, but just in case...
ADB / Fastboot (mirror) - same as the drivers, but again, just in case...
Initial Setup:
Again, some of this might be redundant as you might already have this setup if you rooted/unlocked.
Install the HTC drivers if you haven't already
Unzip the adbfastboot.zip file to your desktop (anywhere, but I find it easiest to get to it on the desktop for my habits)
Getting into the bootloader (hboot):
If you're stuck in a boot loop, pull the batt... oh wait, we can't do that here. To perform a hard reset, hold down the power button for 10 seconds - in the process you'll see the softkeys start blinking, then it should reset. As soon as it starts to reset, release power, and hold down the volume-down button - hold it until hboot pops up (white screen, colored text).
If you're phone is fully powered off (make sure "fastboot" is disabled - settings > power), hold the volume-down key and while holding it, press and hold power for a few seconds. You can probably release the power button, just make sure you keep holding volume-down - after probably 3-5 seconds (maybe a bit more), hboot should come up.
If the phone is on and you're plugged in to your computer, make sure "usb debugging is enabled" (settings > developer options), shift+right-click the adbfastboot directory on your desktop (or wherever you put it), choose "open command window here", and in the prompt that comes up, input adb reboot bootloader.
Restoring:
Once you're in hboot, make sure you select Fastboot (if you don't see it, you're in Fastboot already). In the command prompt referenced above, input fastboot oem lock. This will relock your bootloader in order to allow the RUU to run. Historically this has been necessary for an RUU to run, but I haven't actually tested it without relocking on the One S, and assumed based on previous HTC devices that this would continue to be the case. Edit: thanks rbrookstx for confirming that re-locking is necessary
Your phone will reboot when it relocks - follow the steps above to get back into hboot.
Once you're back in hboot, make sure you're in Fastboot, and open / run the RUU file. It'll go through some initial prompts, then it should start. It takes about 10-15 minutes, maybe less, depending on your computer.
Once it's done, it'll simply go back into hboot - reboot, and you're good to go.
A couple of notes:
When you unlocked and flashed a custom recovery (if you did that), hboot probably said "tampered with" and when it booted up, it probably had a red message under the "HTC" logo about being a developer only device. That should be gone now. It should boot up clean, and hboot should simply say "relocked", with no tampered message.
Until a better solution comes out, once you unlock the bootloader with HTC's official method, it can never be locked the way it was from the factory. "Relocked" is the best you can do.
Click to expand...
Click to collapse
This is what worked. I had to search the internet for this stuff but the HTC driver, the fast boot and the RUU with a matching or higher radio number all made it work out.