search has not been my friend these days - Long story short, I eneded up with a new to me evo 4g. I replaced the screen and started her up. A few freezes and I did a factory data reset from the settings menu. Decided to root.
used the supertool method here :http://www.goodandevo.net/2011/12/new-htc-evo-rooting-method-now-available-htc-supertool.html
ran step 1(prep) and had success.
ran step 2 (attempt root) and it was unsucessful - I figured it was because I didn't have an sd card in, so powered down
re-ran step one and phone froze.
Half the time I could get to the bootloader, so I tried an RUU. Went to fastboot usb, had it registered with the computer as and HTC... and ran the ruu. Either my windoze machine froze or the phone did. It failed.
Now I can get to the bootloader 1 out of 25 tries. Otherwise the screen stays blank. Then the buttons don't work every other time I do get in. I have to leave the battery out about an hour(?) or more for a chance at success. IF the buttons work, it stays active for about 3 minutes. Then the phone freezes.
The phone does have charging lights on it, but that's about it.
What can I do here?
Somewhat of an update. If I wait long enough- like 3.5 to 4 hours, I get one shot at the bootloader screen. I tried to ruu with a 4.56? stock rom, but had issues again. then i saw a friends phone who had 4.53. So I'll try that in the morning. Crossing my fingers here.
wasilvers said:
Somewhat of an update. If I wait long enough- like 3.5 to 4 hours, I get one shot at the bootloader screen. I tried to ruu with a 4.56? stock rom, but had issues again. then i saw a friends phone who had 4.53. So I'll try that in the morning. Crossing my fingers here.
Click to expand...
Click to collapse
If your phone comes on and you see lights its not bricked. Once you cant get it to do anything then thats when you worry. I would find one of the the PC36IMG.zip files and when you get it to go into bootloader you can install the zip.
Does your bootloader say unlocked? Also I am confused because the methods on here for rooting is quite easy and have been established for some time now. Why would you try a relatively new method and especially something of the xda grid.
Dowload the PC36img file from this thread and go from there..
Yeah, getting to the bootloader is the problem. I manged 2x last night. Sat overnight and no lights or beeps or vibrations, but it charges (confirmed batt was charged on my friends evo).
I tried a pc36img file, several actually, but it wouldn't load them. S-on is listed in the bootloader - since I never actually got it rooted.
IF S-ON is in the bootloader, will it load a pc36img file?
Can I install the PC36... file on the removable sdcard, and it should recognize it and install it? It just reads the card, examines the file and goes to the normal bootloader screen. That's why I was trying RUU files.
playya said:
Also I am confused because the methods on here for rooting is quite easy and have been established for some time now. Why would you try a relatively new method and especially something of the xda grid.
Click to expand...
Click to collapse
If I recall, I was forwarded there by an xda thread. It's my fault for not checking my build first and making sure it was an acceptible root method for it. This phone is a year old, I assumed the method would work - I was wrong - and am now paying the price for the assumption.
wasilvers said:
Yeah, getting to the bootloader is the problem. I manged 2x last night. Sat overnight and no lights or beeps or vibrations, but it charges (confirmed batt was charged on my friends evo).
I tried a pc36img file, several actually, but it wouldn't load them. S-on is listed in the bootloader - since I never actually got it rooted.
IF S-ON is in the bootloader, will it load a pc36img file?
Can I install the PC36... file on the removable sdcard, and it should recognize it and install it? It just reads the card, examines the file and goes to the normal bootloader screen. That's why I was trying RUU files.
Click to expand...
Click to collapse
Yes. I believe you can install a signed stock ruu directly from HBOOT even with s-on. install the sd card with the ruu.zip directly on the root of the sd card (name must be pc36img.zip). When HBoot loads, it will scan the sdcard and find the zip and automatically run it. format the micro sd card first... maybe its corrupted or something.
Update
Update:
All options were a nogo- I got a pc36(whatever) file to read and a progress bar that paused (paused till the battery went dead). No RUU file would work. I read that some of the memory modules must have been written bad in the root and it would need jtag service. So I'm putting the screen on ebay and cutting my losses.
Moral of the story: Stick with XDA - search under your operating system, don't be lazy like me.
Now I am root shy, only rooted one phone in the last 2 weeks, and none for my friends. Glad this was mine and not a friends - that's probably why I got lazy.
Related
I have officialy given up on repairing my phone. Looks like it's not possible to fix this thing. Just spent the better part of 3 pays (4hours of sleep a night) trying to get my phone fixed. My sister bought this EVO through some work deal and gave me it on Christmas. I rooted it that night, and bricked it 30mins later, because of the newer partition scheme it is currently impossible to get this phone back working...
This is what I have now. A EVO 4G that boots normally to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
A Vol Down + Power Boot boots to this screen. ftp://eto.homeip.net/shared/IMAG0004.jpg
I can also navigate to this screen. ftp://eto.homeip.net/shared/IMAG0005.jpg
Because of the S-OFF it is obvious to those in the know that I rooted my phone.
I'm just wondering if you guys think this scenaro will work.
_________________________________________________________________
Walk into a Sprint Repair Store, tell them my sister just bought the phone new (about a week ago) and gave it to me as a X-Mas gift. I chose to do the latest OTA-Update, and after it stopped booting and only went to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
Where I'd have to pull the battery to turn it off.
They will probably try VolDown+Power and might comment on S-OFF (which I will say I don't know what that is).
Hope they give me a new/refurbished EVO for free or less then $50.
===============================
Questions
* Should I go to a Sprint Store I've never been to? (There are stores within 20miles of me) (Closest knows I root phones, then other I've been into a bunch of times and may have given up on me)
* Should I get the receipt from my sister, who I don't want to tell I rooted/bricked phone
* Call ahead of time and see what they say on the phone?
* Also please give me suggestions of anything that will help
BTW
* Am well within 30days of buying phone, though I'm not sure if my sister bought it through Sprint or not (Think she did though)
* I have pin/name/number on account and can easily activate a different phone they give me.
* Would rather not tell my sister or even get the receipt from her room to keep her from suspecting anything, but can if need be
Thanks for your suggestions, wanted to get this done by the end of the week before I head back down to San Luis Obispo for college. (Where there are fewer Sprint Stores to spam)
I don't know what the policy is.... most likely, as soon as they see where you're at, the tech will figure out that you were trying to root your phone, and you'll be SOL.
Have you tried booting your phone via ADB? Maybe you can go into recovery via adb shell and see if you can go from there....
if you can get it to power up all is not lost, try pushing AMON's recovery via fastboot
Fastboot
Copy recovery-RA-evo-v1.8.0.img in your android-sdk-windows\tools\ folder
Boot your phone into fastboot mode
fastboot devices(press enter) (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-evo-v1.8.0.img(press enter)
Since your phone turns on and you can boot into fastboot. Bricked would mean nothing happens period. There's still hope. Try this thread: http://forum.xda-developers.com/showthread.php?t=780141. There's a video walk-through showing you how to unroot and return to s-on. Then you may be able to start over.
Good Luck!
-kp
Edit: Try GMan's suggestion above 1st.
Sorry guys, itried all that stuff yesterday for several hours in the irc.
*adb doesn't recognize device (if you can help me with this that would be great)
*fastboot works but always gives
Code:
writing 'recovery'... FAILED (remote:image update error)
*flashes in hboot except for Radio_V2 always give
Code:
Parsing...[SD ZIP]
[1] RECOVERY - Fail-PU
Partition update fail!
Update Fail!
It's all in the opening post of the first thread I linked. Wanted to keep that thread about fixing my phone, and this one about getting it back to Sprint / HTC. Thanks
Do you have TEP on this device? If so, and you were to accidentally drop your phone in a very deep lake, river or ocean, you would be covered for loss with a $100 deductible. You can add TEP in the first 30 days, if you don't already have it.
indagroove said:
Do you have TEP on this device? If so, and you were to accidentally drop your phone in a very deep lake, river or ocean, you would be covered for loss with a $100 deductible. You can add TEP in the first 30 days, if you don't already have it.
Click to expand...
Click to collapse
Sprint Insurance right? I don't... I might do that but that's my last resort.
josh4trunks said:
Sorry guys, itried all that stuff yesterday for several hours in the irc.
*adb doesn't recognize device (if you can help me with this that would be great)
*fastboot works but always gives
Code:
writing 'recovery'... FAILED (remote:image update error)
*flashes in hboot except for Radio_V2 always give
Code:
Parsing...[SD ZIP]
[1] RECOVERY - Fail-PU
Partition update fail!
Update Fail!
It's all in the opening post of the first thread I linked. Wanted to keep that thread about fixing my phone, and this one about getting it back to Sprint / HTC. Thanks
Click to expand...
Click to collapse
If you can boot into the hboot just run a ruu and restore the factory Rom, if all fail pm me your number and I will walk you thru it
Sent from my PC36100 using XDA App
shameless bump - completely changed opening post
I could be completely wrong but it's my understanding that, as long as you can get into the hboot, all hope is not lost. I thought I had bricked my wife's Evo when I was rooting it last week.
What worked for me was:
1. Take the SD card out and put it in a PC.
2. Clear out all files on the root of the SD card. (Not sure if this is needed but it's what I did. I left the folders in place though.)
3. Download the appropriate stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=838448 (Thanks xHausx!!)
4. Rename the ROM to PC36IMG.zip and place it on the root of the SD card.
5. Place SD card back in the phone and boot into hboot.
6. Your phone should detect the PC36IMG.zip and take forever to load it before asking you if you want to install. Say yes to the install and let it reboot after the install.
This brought my wife's phone back to stock so I could attempt the root again. My wife's phone is a white 0004 that came stock with 3.30.651.3 on it. I downloaded the 3.30.651.2_PC36IMG.zip from the site above and it worked just fine.
This is what worked for me but results may very. I'm still a nOOb with this, having just came from a Pre, you may want to wait till someone else comfirms that the above will work...
Hope this helps!
haplo1818 said:
I could be completely wrong but it's my understanding that, as long as you can get into the hboot, all hope is not lost. I thought I had bricked my wife's Evo when I was rooting it last week. What worked for me was:
1. Take the SD card out and put it in a PC.
2. Clear out all files on the root of the SD card. (Not sure if this is needed but it's what I did. I left the folders in place though.
3. Download the appropriate stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=838448 (Thanks xHausx!!)
4. Rename the ROM to PC36IMG.zip and place it on the root of the SD card.
5. Place SD card back in the phone and boot into hboot.
6. Your phone should detect the PC36IMG.zip and take forever to load it before asking you if you want to install. Say yes to the install and let it reboot after the install.
This brought my wife's phone back to stock so I could attempt the root again. My wife's phone is a white 0004 that came stock with 3.30.651.3 on it. I downloaded the 3.30.651.2_PC36IMG.zip from the site above and it worked just fine.
This is what worked for me but results may very. I'm still a nOOb with this, having just came from a Pre, you may want to wait till someone else comfirms that the above will work...
Hope this helps!
Click to expand...
Click to collapse
Tried this multiple time with different PC36IMG.zip, always get Failed-PU
Partition Update Error, I might try the 3.30 version though just to make sure.
Won't like my opinion but, you knew the risks of rooting. If you can't fix your phone then you should add the insurance and suck up the deductible fee. You don't deserve (or anyone for that matter) a free replacement for ****ing up your phone. It sucks but that's the risk. They'll normally have you one the next day.
Your phone is definitely not bricked and is fixable. Do you have adb drivers installed on your PC? If not find them and install them then try this: http://forum.xda-developers.com/showthread.php?t=829045?
Since you are already s-off you won't have to do all the steps, but by reading the entire OP you could figure out where to start and what to do. Just to be on the safe side you may want to start at the beginning using HBOOT USB from this screen you posted ftp://eto.homeip.net/shared/IMAG0004.jpg and start completely over. you are not bricked. Just hang in there and someone here will get you hooked up. You are in the right place my friend.
Evo's are really not that easy to fully brick.
I know whats wrong with your phone problem is i don't know how to exactly fix it! When you tried to root it after taking the OTA or upgrading the HBOOT you messed up the partition table thats why you can't flash a rom what you need to do is try to run a ruu back to stock and then try to reroot but untill you get the partition table fixed you have a phone that is nand unlocked and can't flash any rom the ruu rewrites the partition table if your phone came with 3.70 then use that ruu but if you took the ota then run the 3.30 should work don't do a PC36IMG run the RUU in fastboot usb mode
Have you tried using a different SD card? Is it possible that something is corrupt with it? I also hear that you need to have at least 1GB of free space on the card when your trying to flash it.....
Let me just say myself and this guy stayed up late last night working on this phone trying every possible root/unroot method you can think of.
The pc he is using has adb drivers installed but the computer wont recognize his device as a adb device. Fastboot on renders certain commands and we tried all with various recoveries. I hit up a dev and we went thru different things and cant seem to figure this one out
As I told the Josh it can not be bricked because we get the bootloader and fastboot screen, I think its not even the partition but the recovery. Also he has a modified hboot by someone on xda (josh please post the link) which I believe that pc36img is whats causing all the problems.
If anyone could help it would be appreciated!!
Jbcarrera said:
I know whats wrong with your phone problem is i don't know how to exactly fix it! When you tried to root it after taking the OTA or upgrading the HBOOT you messed up the partition table thats why you can't flash a rom what you need to do is try to run a ruu back to stock and then try to reroot but untill you get the partition table fixed you have a phone that is nand unlocked and can't flash any rom the ruu rewrites the partition table if your phone came with 3.70 then use that ruu but if you took the ota then run the 3.30 should work don't do a PC36IMG run the RUU in fastboot usb mode
Click to expand...
Click to collapse
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
craigbailey1986 said:
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
Click to expand...
Click to collapse
I'm sure he thought you needed the engineering SPL to be able to flash roms. When I rooted mine back in June with toast's method, that was the way to do it. I rooted my girl's new Evo last month using Unrevoked, and I also downgraded the hboot because I thought I had to in order to flash a custom rom. Fortunately, I was able to do so with no issues.
Cleared all the caches?
craigbailey1986 said:
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
Click to expand...
Click to collapse
The partition table is screwed but there has to be a way to reset it I knew that method was risky told my friends to stay away from it
Sent from my EVO at the edge of hell
I've been ROM-hopping, trying Synergy, Alliance, Myn, and several others. On the last one, MikG 2.3, I had it loaded up and working fine. I started installing apps from the Android Market. That, too, was going fine, until it suddenly rebooted in the middle of an app download/install.
It went to the white screen with HTC EVO 4G on it, and then went black, then back to the white screen, over and over.
Six hours later, I'm still stuck in the loop. To make matters worse, I accidentally lost root (I see "S-ON" at the top). So now I'm stuck without root until GB is rooted successfully, which hopefully isn't tooooo far off in the future.
But that's the least of my concerns. I would be extremely happy with a stock install of any sort at this point, but I can't get anything to load. No recovery, no ROMs, but I can get into HBOOT so I'm able to try to load any PC36IMG.zip files. The last one I tried was the "PC36IMG_SuperSonic_GB_Sprint_WWE_4.24.651.1_Radio_2.15.00.05.02_NV_2.15_release_199233_signed.zip" (renamed to just PC36IMG.zip, of course). It appears to load just fine and in the end says "Update Complete... Do you want to reboot device?"
I choose yes, it reboots... and we're back in the loop. I have no idea what to do or try at this point. Any help anyone can provide would be greatly appreciated! My next step is to take it to the Sprint store, but that's over an hour away and will have to wait till the weekend.
Thanks everyone!! If you need any more information, let me know. Believe me, I'll be monitoring this thread closely!
/Kevin
I'm sure uve heard this before and prob won't work but worth a try....try reformatting ur SD card and then flashing the file in bootliader again. Could be a corrupt SD card
Papa Smurf151 said:
I'm sure uve heard this before and prob won't work but worth a try....try reformatting ur SD card and then flashing the file in bootliader again. Could be a corrupt SD card
Click to expand...
Click to collapse
Yeah, I tried. I have several SD cards of varying sizes (4GB, 8GB, and my primary 16GB). Formatted the 4- and 8GB ones and tried from each, but no go. Thanks for the try though!
/Kevin
Reset phone to recovery (stock), choose fastboot. Plug in USB to computer.
Look for the correct ruu exe file and ruu it via exe method
trim81 said:
Reset phone to recovery (stock), choose fastboot. Plug in USB to computer.
Look for the correct ruu exe file and ruu it via exe method
Click to expand...
Click to collapse
Just did it and the process went well, said it was successful... but it's still stuck in the same loop. I'm thinking the phone is beyond repair. Thanks for trying, though. It really looked like it might work for a second.
/Kevin
what was the app?
That's what I want to know and how do you get accidentally to S-On?
Put the phone in a refrigerator ... as crazy as it sounds, it might be the infamous overheating issue.
Put in refrigerator, for about 5min
The app was "Kid Zone" (Zoodles), but I'm not blaming the app by any means. I've used it for a long time, it's highly-rated in the market, etc. I'm sure it's just a coincidence.
As far as getting back to S-ON, I think it must have been when I flashed the stock recovery. I was flashing so many things out of desperation that I can't swear to that, but I'm pretty sure that's what did it. Now that it looks like I'm heading to the Sprint store tomorrow, I guess it's a GOOD thing it's back to S-ON. Heh.
Pretty sure it's not heat-related. My phone was off all night (since it's not usable) in an air conditioned room, so it's cool to the touch. I tried the RUU process again with the same results. (I'm not sticking it in the refrigerator, because I'm afraid of activating the water-damage sensor -- I don't want any excuses from Sprint when I bring it in tomorrow!)
Appreciate the help!!
/Kevin
That sucks, but tbh, I have yet to see one case of anyone at Sprint checking a bootloader to see if a phone is S-On. MOF, I bet if it doesn't boot at all, or is a stock ROM , they wouldn't even know the difference.
HipKat said:
That sucks, but tbh, I have yet to see one case of anyone at Sprint checking a bootloader to see if a phone is S-On. MOF, I bet if it doesn't boot at all, or is a stock ROM , they wouldn't even know the difference.
Click to expand...
Click to collapse
I hear ya. I haven't run into any techs at my local stores that are knowledgeable about this kind of stuff. (I know others have, so you never know, but I have yet to see one.)
/Kevin
To conclude this: I went to the Sprint store today where they assured me they would reload the software but it would take 1.5 hours. I came back 1.5 hours later... and they handed me a new (refurb) EVO. They said they weren't able to load anything on the phone.
So, no surprise with the outcome there. I was fairly certain they were going to have to replace the EVO, and they did.
Thanks to everyone who tried to help, but it was just beyond help!
/Kevin
I had that same problem with my phone back in November. Continues boot loop. Finally, having boot loop for 8hrs, I took it to Sprint and they replaced my phone. They called it a power cycle issue. $35 new refurbished phone works well. Never had a problem since.
I've searched and searched but I think the answer is no. I had an earlier post, but now I know the only way will be through fastboot since it is s-on so no point in putting any PC36IMG file on the root of the sd card. There was an unbrick program that seemed to connect, but I don't think it did anything, but it seemed to access the phone since it showed the phone in the C prompt. Just wondering if there is anything out there like "Evo_Brickfix" that uses fastboot. Thanks
Edit: I found a one click fast boot fix for bootlooping another android phone. I wonder if it can be adapted for the evo or maybe it is made for rooted phone that have s-off
I was just told, that, if you can get into flashboot, then you can do anything.
Like usb toggle and use an RUU file from your pc.
Sent from my PC36100 using Tapatalk
eggsack said:
I was just told, that, if you can get into flashboot, then you can do anything.
Like usb toggle and use an RUU file from your pc.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
If you mean fastboot then that would be great. I'll have to read up or look for someone going over how to use RUU. Thanks
eggsack said:
I was just told, that, if you can get into flashboot, then you can do anything.
Like usb toggle and use an RUU file from your pc.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Ok so I searched and found an RUU exe file that actually put a different new stock ROM, but it still boot loops. When I'm in the bootloader I can see that the HBOOT is updated from .79 to 2.4 and the date has changed to 2011 versus 2010 so I know it RUUed in just fine. Now I just need an RUU file that will fix the recovery or something besides the ROM?
Edit: ok after I took battery out and boot it up this morning 8 hrs ago it didn't boot loop as of now isn't boot looping. So maybe it needed to power down and whatever was boot looping needed to reset. Maybe while it's working I should s-off it. Does anyone know what will root it with newer ROM? It is dated August 2011 SuperSonic_GB_Sprint_WWE_4.24.651.1_Radio_2.15.00.05.02_NV_2.15_release_199233_signed. Is there even a ROOT for it now. I'll google to see.
It started bootlooping again =(. I went ahead and use REVOLUTIONARY to s-off it and install a recovery. I put the same ROM I have on my evo, Kings Shooter something something, but then it looped even worse, so I put another ROM that was only 200mb versus 333mb. It is Team Nocturnal 4.54 something something and is working fine so far. Maybe my Kings Shooter is corrupted since I've moved it around from computer to computer. I can't imagine how a different rom would fix the bootloop, but maybe when you load another rom it fixes whatever is corrupt and causing the phone to go into looping. Something else I noticed, when I would leave the phone with no battery for hours, it would then boot up fine and run for a lil bit then boot again and get worse. So maybe it loaded something into memory that when left with no battery wasn't present to start with but after being powered, then stayed on. In fact, when it is boot looping, all I needed to do was put the battery back in and it would start again without me even having to press the on button. Oh, well hopefully it is working fine now. But in case anyone searches and finds this thread they can see my specific problem and solution and maybe it can help someone else.
I know you guys have seen this over, and over. 1st post from a noob.
I've been through the forum since lunchtime, using the search function, but I just cant make the damn thing fire up.
I rooted it with AAHK, worked brilliantly, then I put the ICS ROM onto it, worked fine apart from the camera, which I was expecting, but after trying numerous camera apps, I couldn't get it to work, SO
I re ran AAHK to put Froyo back onto it, from where I could take the HTC system update and reinstall Gingerbread while I waited for further developments for the camera.
Phone was nicely plugged in and AAHK was running away, but the doorbell rang, I got up to answer it and my daughter saw my phone and decided to play Angry Birds. Unplugging the phone.
She got angry Daddy instead.
I can boot into recovery mode (which is something I guess) but how do I get it back up and running.
On the recovery screen I have the following text:-
ACE PUT SHIP S-OFF RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26. 03.02.26_M
Apr 12 2011, 00.55.45
Then the instructions for selecting, then the menu. Recovery gives me the red triangle, reset takes me to the HTC screen, then a green circley thing, then HTC, then ....
I tried running an RUU install, but my computer doesnt recognise the phone and I can't make that work either.
AM I looking at it meeting with a 'terrible accident' or is it recoverable?
SD card was wiped. My bad there.
It seems that fortune favours the brave. Seems I'm uploading a RUU now. I ought to be able to get some sleep soon.
Well It's great that you managed to get it going again. On a side note, before this mess happened, if you wanted something more stable, you should have just flashed another ROM, maybe something with gingerbread. Cyanogenmod is a great rom to get into root stuff too.
I'm not sure what you mean by rerunning AAHK? AAHK does allow you to remove root if you're on a supported stock rom. but I don't recall it being able to put you back onto a stock rom from another ROM. You would have to apply an update package from HTC (making you lose root and most of you're info too).
BTW, that screen which you call recovery is actually the bootloader screen, from there you can choose what you want to boot into.
Unfortunately I don't really know how to help you from here, there's only so far I can go on the technical side before I FC and reboot. Other then telling you where you went wrong (and probably know by now), I can't tell you how to go right. Woot woot for constructive criticism. :victory:
For your first post, try downloading the htc drivers (htc sync) to your computer.
Second post: uploading?
Sent from a dream.
nickliv said:
I know you guys have seen this over, and over. 1st post from a noob.
I've been through the forum since lunchtime, using the search function, but I just cant make the damn thing fire up.
I rooted it with AAHK, worked brilliantly, then I put the ICS ROM onto it, worked fine apart from the camera, which I was expecting, but after trying numerous camera apps, I couldn't get it to work, SO
I re ran AAHK to put Froyo back onto it, from where I could take the HTC system update and reinstall Gingerbread while I waited for further developments for the camera.
Phone was nicely plugged in and AAHK was running away, but the doorbell rang, I got up to answer it and my daughter saw my phone and decided to play Angry Birds. Unplugging the phone.
She got angry Daddy instead.
I can boot into recovery mode (which is something I guess) but how do I get it back up and running.
On the recovery screen I have the following text:-
ACE PUT SHIP S-OFF RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26. 03.02.26_M
Apr 12 2011, 00.55.45
Then the instructions for selecting, then the menu. Recovery gives me the red triangle, reset takes me to the HTC screen, then a green circley thing, then HTC, then ....
I tried running an RUU install, but my computer doesnt recognise the phone and I can't make that work either.
AM I looking at it meeting with a 'terrible accident' or is it recoverable?
SD card was wiped. My bad there.
Click to expand...
Click to collapse
your computer wont be able to recognize ur phone whatever u do...U will have to install the RUU (PD98IMG) from fastboot (Make sure not to flash a Froyo RUU on a phone shipped with gingerbread).. i am sure u knw how to flash the RUU using PD98IMG from fastboot, just do it and everything will be fine and u will return to stock and u will also loose root,so u will have to root it again.
I re rooted it, as I am, as we all know, a noob, I thought that would put Froyo back on it, (Like I did when I rooted it first) and then I could simply take it on over to Gingerbread with the system update tool.
Ultimately, the bootloader worked, and I now have a fully working phone.
Thanks to you all for your replies, you're making a man whois old enough to know better understand a little more with each one.
Oh yeah, I could get into the bootloader screen by turning power on and holding the VOL - button. When I pressed power on and help the VOL + button, it buzzed 4 times, and the orange notification light just flashed, nothing else.
Doesn't really matter, it works, it's back to how it was, and I know where I went wrong, ish.
although the issue is resolved, must important thing when something goes wrong: Don't panic! (Hitchikers Guide refrence there
Happened to me when I rooted my friends inspire 4G (he saw that AAHK says it was done on the phone and decided to unplug it straight away) just come the the forums
It's always the forums....
Sent from my Desire HD using xda premium
Evening all,
I have a DHD that is stuck in HBOOT/FASTBOOT, or at least that and the stock recovery program is all I can get to.
I tried an AAHK, and it basically tried to do a downgrade and has left the phone with no data, still at s-on, and I can't find an operator RUU(three uk) to flash it back to a useable state.
Is there a three RUU available?
I'm running around in circles as I can't make a gold card, due to not having another DHD available to retrieve the MMC2. All I need is a goldcard and then I can flash a WWE, but I cant find anywhere to make one without the phone or a similar one.
I dont think it turned the microsd properly into a gc, before it tried to downgrade. Is their anyway I can test to see if the memory card has been successfully goldcarded?
Any help would be greatly appreciated.
Thanks
James
This might help
http://forum.xda-developers.com/showthread.php?p=29203392
Sent from a dream.
Teichopsia said:
This might help
http://forum.xda-developers.com/showthread.php?p=29203392
Sent from a dream.
Click to expand...
Click to collapse
Mine has a lot of those symptoms to be honest. If I vol down/power to get to Hboot, it sits there with no keys being able to be pressed, just highlighted blue FASTBOOT and not even checking for files on memory card
If I just turn it on, it sits at the three splash screen, which i assume is the equivalent of the HTC one for branded phones.
I have now turned it on and left it on as per those linked threads, in the hopes the sd is a proper gold card and it is just slow. Fingers crossed.
Thanks for the pointer
James
There are many threads for your problem, do a search, check what it might be. I believe in the second page of that link has another link, check it out. Find out what is wrong before trying anything. If you have any questions, let us know what are the symptoms, what you have done and so on.
Sent from a dream.
Teichopsia said:
There are many threads for your problem, do a search, check what it might be. I believe in the second page of that link has another link, check it out. Find out what is wrong before trying anything. If you have any questions, let us know what are the symptoms, what you have done and so on.
Sent from a dream.
Click to expand...
Click to collapse
Well what I did, was follow the AAHK instructions, cleaned up my environment etc, went through the install. When it asked to do the downgrade, I said yes, then it asked about wiping and was I sure, so I said yes. It then rebooted the phone and it is now as it is. I pulled the battery and tried vol-down/power, which brings up HBOOT, but it doesnt let me do anything, vol keys and power do not work and it doesnt start looking for image files.
From that thread, it was mentioned it just could be going very slow, and people have just left it overnight. This is what I have done now, and will see if it has accessed the files on the memory card and downgraded properly in the morning.
Thanks
James
Have you tried looking for the RUU here?
Last I remember when aahk downgrades, you will be asked to reboot to basic recovery twice
Panic over, thankfully! Not my phone, you see!
It was so easy to root my S2 and the X10 before that, and the iP3G before that(and custom winmo, and nokia etc etc), I said give it to me, i'll sort you out with some ICS rom action.
Then it all went wrong as explained in my previous posts.
2 days later, i finally found the H3G RUU I needed to get an system on it. Silly branded phones. Took 4 hours to download as it was on a throttled download service(my 100MB leased line usually eats 300MB in seconds, but not this time)
So long story short, into FASTBOOT USB, ran the RUU and it completed and put froyo on the phone, and as a happy coincidence it was at a level that didn't need a downgrade, so AAHK ran through like a trooper, busybox installed and hey presto, ENG S-OFF. IceColdSandwich installed through cwm and one happy mate, who then proceeded to ring his wife and tell her to rent a film, as he would be tinkering with the phone all night lol
It was getting to the point I was going to have to give him my S2, and as I've just taken possession of a Sony SmartWatch, I didn't want to do that!!
Thank for everyone's help and pointers, not sure what went wrong the first time(probably a memory card/incompatibility/goldcard problem), but all sorted now.
James