Related
Hello.
I'm pretty sure i bricked my HTC desire yesterday when trying to flash LeeDroids Mod. My phone hangs at the three green HTC letters and it has been like this the whole night. I've tried taking out the battery and things like that but it still hangs. Even when triyng to do a recovery. So i searched the forum to find out how to unbrick the phone and i found a nice thread that explains how to get acces to the SD again and then how to unbrick the USB connection. But I havent been able to try this out yet since i cannot find out how to enter commands when in fastboot. I know I need to be connected with a USB-cable to the PC, but what else do I have to do?
Hope someone can help 'cause I would really love to have my HTC Desire working again so that i can try out more cool FroYo mods from this lovely forum.
- Czepluch
czepluch said:
Hello.
I'm pretty sure i bricked my HTC desire yesterday when trying to flash LeeDroids Mod. My phone hangs at the three green HTC letters and it has been like this the whole night. I've tried taking out the battery and things like that but it still hangs. Even when triyng to do a recovery. So i searched the forum to find out how to unbrick the phone and i found a nice thread that explains how to get acces to the SD again and then how to unbrick the USB connection. But I havent been able to try this out yet since i cannot find out how to enter commands when in fastboot. I know I need to be connected with a USB-cable to the PC, but what else do I have to do?
Hope someone can help 'cause I would really love to have my HTC Desire working again so that i can try out more cool FroYo mods from this lovely forum.
- Czepluch
Click to expand...
Click to collapse
you have to use adb, google the android sdk and start there
All you need to do is boot into FASTBOOT, plug in your USB and run an RUU to get back to stock (assumg one is available for your phone) and then root again, had to do it myself the other day
you do not have to do ANY of this
if you are using clockworkmod or any custom recovery then there is the option to mount USB storage in which you can put on a backup or any other rom onto your sd card, unmount usb storage, and flash it, all in one.
cgrec92 said:
you do not have to do ANY of this
if you are using clockworkmod or any custom recovery then there is the option to mount USB storage in which you can put on a backup or any other rom onto your sd card, unmount usb storage, and flash it, all in one.
Click to expand...
Click to collapse
How do I do that when my phone doesnt boot? As i wrote in the first post it is stock at the 3 green HTC letters. I was using clockworkmod to flash, but as I wrote i cannot boot into andoid atm.
@AndroHero: Can you please give me a link or something? I have tried a lot of things, but i doesnt seem to work, so I would like to be certain that the link and guide im using is right.
czepluch said:
How do I do that when my phone doesnt boot? As i wrote in the first post it is stock at the 3 green HTC letters. I was using clockworkmod to flash, but as I wrote i cannot boot into andoid atm.
@AndroHero: Can you please give me a link or something? I have tried a lot of things, but i doesnt seem to work, so I would like to be certain that the link and guide im using is right.
Click to expand...
Click to collapse
Do you have the fake-flash zip file renamed as update.zip and at the root of your SDCard?
dnlgee said:
Do you have the fake-flash zip file renamed as update.zip and at the root of your SDCard?
Click to expand...
Click to collapse
yes i do
czepluch said:
yes i do
Click to expand...
Click to collapse
Have you booted the phone while holding the volume down and then selecting recovery, then when recovery boots, press volume up and power then select "apply update.zip" ?
The problem is that when i choose recovery it freezes aswell. The screen with the phone and the little red triangle freezes, so i cannot choose recovery.
EddyOS said:
All you need to do is boot into FASTBOOT, plug in your USB and run an RUU to get back to stock (assumg one is available for your phone) and then root again, had to do it myself the other day
Click to expand...
Click to collapse
So do what I said here...to get into FASTBOOT hold back and power it on
What is RUU?
Edit: Maybe I need someone to make a step by step noob guide? Im totally lost. Ive flashed my Desire lots of times before and ive never had a single problem, but right now i really dont know what to do and how to do?
If you're asking questions about RUU's then maybe rooting wasn't for you. It's basic stuff. You need a grasp of the basics before trying something advanced!
Basically it's the official ROM file from HTC/your phone vendor...
Okay. Thanks. I thought that RUU was something like that but I just couldnt see how i should be able to acces any files right now. As i wrote before the phone freezes at the picture of a phone with the red triangle, and i am not able to get any further that that. I would really appreciate if anyone could tell me how and what to do next?
I had the same problem a few days ago. For me it worked to just go through the rooting process again, you can find the steps on modaco (just step 1 of r6), I can't link them at the moment I'm at work and it seems I can't open modaco from here.
Anyways if you follow step 1 you can access the recovery again and the phone will boot past the HTC logo screen.
Also these steps are well documented on modaco.
Try this first since it will save you the step of running the RUU, which I wasn't able to (somehow the software complained my battery was below 30%, which it wasn't)
Good luck hope this solves it for you.
czepluch said:
Okay. Thanks. I thought that RUU was something like that but I just couldnt see how i should be able to acces any files right now. As i wrote before the phone freezes at the picture of a phone with the red triangle, and i am not able to get any further that that. I would really appreciate if anyone could tell me how and what to do next?
Click to expand...
Click to collapse
You don't need to go into recovery! boot into FASTBOOT and then leave it at that. Plug the phone in and it will then say FASTBOOT USB. Then run the RUU your phone came with originally. You don't need to go anywhere near Recovery
I am pretty certain that ive found a solution now. I deserve a fist in the nuts for being so stupid not to press volume up + power when trying to get into recovery mode. But fortunately dnlgee asked if i had remembered this. Now that ive gotten this far i should be able to solve the rest. I will however return if im still unable to solve it.
czepluch said:
I am pretty certain that ive found a solution now. I deserve a fist in the nuts for being so stupid not to press volume up + power when trying to get into recovery mode. But fortunately dnlgee asked if i had remembered this. Now that ive gotten this far i should be able to solve the rest. I will however return if im still unable to solve it.
Click to expand...
Click to collapse
Ah I missed that part, I couldn't access recovery either. Only thing left working was fastboot for me. All other options would hang on the HTC logo screen.
So before everyone yells because of my inability to search the forum, please understand that not only have i searched this forum, but just about every other one. And if someone finds a thread with an answer to my question than i will admit defeat and have myself stoned and crucified.
I will greatly appreciate anyone's and everyone's help.
History in cliffnotes
Rooted with Unrevoked about a month ago, since then been running CM 6.
Have been happy with just using stock CM 6 and nothing else, haven't flashed any other kernels, radios, or for that matter roms.
Have always had problems with random reboots but didn't care.
Last night my phone appeared to have the desire to random reboot, and on start up got into a boot loop, just HTC splash boot loop. I can get into bootloader but if i try to go to recovery it is just more boot loops.
I'm running mac OS X however i eventually just tried running RUU on my roommates computer but to no avail, mostly, i think, because my phone can't boot into a state where its recognized by the program or sync, etc...
The real problem
As of now i've gone as far as basically completely unrooting, using a pc36img that i found through you guys here
So if you guys have any ideas, at this point, i'm completely willing to try them because, this was completely random that it happened, and i really am at a complete loss as to what to do besides buy a new phone.
i love you all in a masculine plutonic way. thanks.
well you could always re-root with unrevoked. all it needs is bootloader mode to root it and then once its done, flash a rooted rom on it, then proceed to unroot.
EDIT:
btw, i am a mac user too and unrevoked works great. if it fails, run it again. and no need to use an ruu, look up a thread in our development section titled shpped roms and they have pc36img versions of the ruu. you will be able to root with your mac and unroot all on the device. unrevoked has an s-on zip on their web page. to unroot it, flash the s-on zip then run the pc36img zip from the base of your sd card. thats all!
EDIT#2:
YOU CAN ALWAYS FLASH A RECOVERY VIA BOOTLOADER ALSO AND FLASH A ROM. LET ME KNOW WHICH RECOVERY YOU PREFFER, I GOT BOTH CLOCKWORKMOD AND RA.
EDIT#3: LOL, Sorry i didnt see that you mentioned a pc36img to unroot.
why dont you just download download the recovery img of amon_ra 2.2.1 in pc36img format and run it from boot loader. done, problem solved.
if that doesnt work download caukulins format all zip and run it and them reload your recovery and rom
t3project said:
why dont you just download download the recovery img of amon_ra 2.2.1 in pc36img format and run it from boot loader. done, problem solved.
if that doesnt work download caukulins format all zip and run it and them reload your recovery and rom
Click to expand...
Click to collapse
I am not trying to thread jack, but i too am having the same problem. I am not a noob at flashing and I am stuck at the white Evo screen and it just reboots when I click on recovery from the boot loader.
I too have flashed the recovery image from amen ra and it flashed ok, but each time I reboot and try to get into recovery it just reboots, so that did not fix getting into recovery.
The problem with the above suggestion is that you need to be able to boot into a recovery to use Caukulins format all zip, and if you can't get into recovery it does no good.
If anyone has any other suggestions please let the both of us know!
Well since you can't get into recovery, we suggested to flash a recovery in pc36img.zip format in bootloader mode.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!
paulieb81 said:
I am not trying to thread jack, but i too am having the same problem. I am not a noob at flashing and I am stuck at the white Evo screen and it just reboots when I click on recovery from the boot loader.
I too have flashed the recovery image from amen ra and it flashed ok, but each time I reboot and try to get into recovery it just reboots, so that did not fix getting into recovery.
The problem with the above suggestion is that you need to be able to boot into a recovery to use Caukulins format all zip, and if you can't get into recovery it does no good.
If anyone has any other suggestions please let the both of us know!
Click to expand...
Click to collapse
thats why i said flash a recovery in pc36img format first. more specifically this:
http://forum.xda-developers.com/attachment.php?attachmentid=483320&d=1294435056
rename to pc36img.zip and boot into bootloader
t3project said:
thats why i said flash a recovery in pc36img format first. more specifically this:
http://forum.xda-developers.com/attachment.php?attachmentid=483320&d=1294435056
rename to pc36img.zip and boot into bootloader
Click to expand...
Click to collapse
If you read my message you will see that I DID flash a recovery, that same one you just linked, and it flashed ok, but when i restart and choose to enter the recovery the phone just reboots again!
Did you solve this?
Yes I did, I went back to the store and had them replace the phone. I could not get it to boot into recovery for some reason.
I dont know what causes this, but this is like the 10th person on a CM rom that's had this exact scenario. Its weird how it happens out of the blue, and then RUU and pc36img just don't work. Very strange. I was just trying to help a guy the other day in this exact scenario. Nothing would get him out of the splash screen. No RUU, PC36IMG of recovery OR a factory ROM, fastboot RUU didn't work. Nothing. Just bricked at the bootloader somehow. I always thought if you could get to the bootloader then you could recovery, but lately there have been quite a few of this exact scenario, and each one was on the same rom. I would love to know what causes this, when the phone is just sitting there, and then goes into a bootloop out of the blue, and then this is the result. It's leaving me frightened to run CM, seriously. What on earth could be causing this type of thing?
Sent from my PC36100 using XDA App
heppened to me too and since then ive seen at least 5 cases of this exact same problem from cm7 roms. so far no one has found a way to fix it that has been posted here. we have all had to have our phones replaced.
ChacocII said:
heppened to me too and since then ive seen at least 5 cases of this exact same problem from cm7 roms. so far no one has found a way to fix it that has been posted here. we have all had to have our phones replaced.
Click to expand...
Click to collapse
Did they give you any problems about s-off being visible in the bootloader when you got your phone replaced? I'm to that point of taking it back with the EXACT same problem but I didn't know if it was an issue. (or is there any trick to get s-on back without being able to load into recovery i.e. a fastboot command?)
i was worried about the s-off as well because i also was unable to change that. all i could find for that was the s-on tool but since u cant actually flash anything, had to leave it s-off. i even tried a battery pull during the radio update on a pc36img so that they wouldnt be able to get to bootloader but i couldnt even brick it. i live more than 50 miles from a sprint store so they didnt make me drive to a sprint store. they sent me a replacement and i mailed my evo back. on the paperwork for the new phone they said i could still be charged 75 dollars for a recoverable phone and 125 for an unrecoverable phone. it was probably 2 weeks ago or so when i sent my old broken evo back and i havent been billed yet so i dont know what if anything they will charge. when i talked to the sprint tech on the phone i told him it was rooted because i knew they would see the s-off and i didnt want to get screwed when i sent them my broken phone and they said "u rooted, ur problem" but he said he would still replace it and he did.
k2buckley said:
I dont know what causes this, but this is like the 10th person on a CM rom that's had this exact scenario. Its weird how it happens out of the blue, and then RUU and pc36img just don't work. Very strange. I was just trying to help a guy the other day in this exact scenario. Nothing would get him out of the splash screen. No RUU, PC36IMG of recovery OR a factory ROM, fastboot RUU didn't work. Nothing. Just bricked at the bootloader somehow. I always thought if you could get to the bootloader then you could recovery, but lately there have been quite a few of this exact scenario, and each one was on the same rom. I would love to know what causes this, when the phone is just sitting there, and then goes into a bootloop out of the blue, and then this is the result. It's leaving me frightened to run CM, seriously. What on earth could be causing this type of thing?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm in the same boat buckley. I don't get it?! I did run cm for a couple days but I was always looking at my phone wondering if something was going to happen. Almost gave myself a panic attack so I just went back to sense, lol.
ChacocII said:
heppened to me too and since then ive seen at least 5 cases of this exact same problem from cm7 roms. so far no one has found a way to fix it that has been posted here. we have all had to have our phones replaced.
Click to expand...
Click to collapse
And I just wanted to say, that although you've seen 5, and I've seen around 10, and that does suck, that the fact is, that this is an EXTREMELY low percentage of CM users that are experiencing this problem. With that noted, it's still enough for me to use a different rom, at least until someone can at least figure out what caused that to happen. I am just extremely curious, as to what the actual malfunction with the device is, when this sort of things happens. And why it seems to only be happening on CM. (at least from the reports I've seen around here)
Add me to the list of people with this problem. I think I'm going to try my chances at the Sprint store. They've been good to me so far.
k2buckley said:
I dont know what causes this, but this is like the 10th person on a CM rom that's had this exact scenario. Its weird how it happens out of the blue, and then RUU and pc36img just don't work. Very strange. I was just trying to help a guy the other day in this exact scenario. Nothing would get him out of the splash screen. No RUU, PC36IMG of recovery OR a factory ROM, fastboot RUU didn't work. Nothing. Just bricked at the bootloader somehow. I always thought if you could get to the bootloader then you could recovery, but lately there have been quite a few of this exact scenario, and each one was on the same rom. I would love to know what causes this, when the phone is just sitting there, and then goes into a bootloop out of the blue, and then this is the result. It's leaving me frightened to run CM, seriously. What on earth could be causing this type of thing?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
It has nothing to do with CM. It is clearly a hardware problem. It has happened on other roms, but more likely to happen to someone using CM as it is the most used Rom.
Sent from my PC36100 using XDA Premium App
Sorry to open this again, but I'm having the same issue. I'm actually on the HTC Sensation, but I'm posting this here because after hours of searching, this is the ONLY place that seemed to address this seriously.
The reboots began even on the original stock rom. I bought it from a guy on Craigslist, but I'm fairly certain it was the original stock rom, with S-off, unrooted, etc. I thought flashing other roms would help, but they haven't.
Here's my furthest observations thus far:
I have actually found a way to get out of this incessant boot loop. As you said, even recovery is impossible. I was so confused when everyone kept telling me to just go into bootloader mode and go to recovery. I can always get into bootloader mode, but recovery, as you guys said, is pointless, because it just boot loops.
However! I have found that if I leave the battery out for an extended period of time, maybe an hour to several hours later, upon inserting the battery back in, I'm able to load up correctly. But that doesn't last long. Usually I only get one chance. If I use that chance to go into recovery mode the next time it'll just boot loop again.
So now I really think it's something to do with the battery, because when I leave it out for a while, I can finally boot up the phone or get into recovery. I do know that HTC has that lame battery problem of boot looping when the battery is low, so do you guys think that it could be related to the battery stats? When my next "battery-free shift" is over, I'm going to try charging the phone and wiping battery stats.
Sometimes the other way I can get out of the boot loop is to charge the phone fully until it's green, so I'm just not sure. This is insane... any input at all would be greatly appreciated..
jkxklutz said:
Sorry to open this again, but I'm having the same issue. I'm actually on the HTC Sensation, but I'm posting this here because after hours of searching, this is the ONLY place that seemed to address this seriously.
The reboots began even on the original stock rom. I bought it from a guy on Craigslist, but I'm fairly certain it was the original stock rom, with S-off, unrooted, etc. I thought flashing other roms would help, but they haven't.
Here's my furthest observations thus far:
I have actually found a way to get out of this incessant boot loop. As you said, even recovery is impossible. I was so confused when everyone kept telling me to just go into bootloader mode and go to recovery. I can always get into bootloader mode, but recovery, as you guys said, is pointless, because it just boot loops.
However! I have found that if I leave the battery out for an extended period of time, maybe an hour to several hours later, upon inserting the battery back in, I'm able to load up correctly. But that doesn't last long. Usually I only get one chance. If I use that chance to go into recovery mode the next time it'll just boot loop again.
So now I really think it's something to do with the battery, because when I leave it out for a while, I can finally boot up the phone or get into recovery. I do know that HTC has that lame battery problem of boot looping when the battery is low, so do you guys think that it could be related to the battery stats? When my next "battery-free shift" is over, I'm going to try charging the phone and wiping battery stats.
Sometimes the other way I can get out of the boot loop is to charge the phone fully until it's green, so I'm just not sure. This is insane... any input at all would be greatly appreciated..
Click to expand...
Click to collapse
If its anything like the evo you might want to try and wipe cache and dalvik cache when you get into recovery let it boot back up if that doesn't work try to fix permission if that doesn't work wipe battery stats when your phone is at 100% using battery calibration app and if none of that works do a full wipe and flash a new ROM or unroot and run the ruu of the stock ROM .
Sorry I know nothing about that phone so IDK if any of that will work for you just trying to help and those are pretty much the steps I would take.
Sent from my PC36100 using XDA App
Happened to me
Hey guys this happened to me and i was running cm and sense roms i have had alot of experience with this and its an actual glitch that causes the os to stack on each other and confuse the boot the only way to fix is to wipe the entire phone back to stock if that dosent work call sprint and they gladly replace ur phone due to manufacture defect its been happening to unrooted phones also from the updatesnot being installed properly phone needs to be wiped every time u do a new rom
I thought I had it all figured. Root, with Clockwork Recovery, Rom Manager. Nothing could go wrong. Now I am stuck at the splash screen with no Clockwork Recovery.
I searched fourum after forum to find a solution, but mine seems to be different. Just so you know I am 21, and a freelance computer technician so I am not afraid of the command line
What have I done to my device:
=Originally it had 2.1
=I rooted the phone via exploid method
=I installed CyanogenMod 6.1.1
+My computer only recognized my phone in HBoot mode, I think usb debugging is turned off though because I cannot acces my sd while it is in my phone.
I do have a microsd card reader
+I tried Esprimg.zip updates. It works .but I still cannot get into recovery mode.
For extra precaution, I backed up all of my sd card data on my pc.
Symptoms and problems:
+I am stuck at the white My tough slide 3g splash screen.
Holding up and power for at least 30 seconds does not get me in recovery mode. All I see is the white My tough slide 3g splash screen. No Black screen with a triangle(Biggest Problem)
+Holding down and power does get me into the HBoot.
+The recovery option will make the Mytouch slide reboot, but it will freeze at the splash screen.
+The clear storage option executed, but it did not solve my problems.
+I have also removed the battery, sim, and sd card.
Summuaray-
I need to get Into Recovery mode, but when I press up and power it does not work. I only see a white.I never though there would be a day where I could not get into recovery.
Also, I constantly charge the device so it wont turn off during an update.
Do you have S-OFF? If you do it should not be hard to recover.
If you don't I can't think of any other method now. But just to make sure which Esprimg.zip method did you tried? Because that should work in the first place.
Mine says S-On
Esprimg.zip
I used my microsd card reader to put esprimg.zip on the sd card. Boot the device while holding down and power. I let the phone check for the esprimg.zip and then the update was successful.
Conclusion:
I hold up and power and i cannot access recovery mode.
Possible causes:
By doing the clear storage, would that change my device to s-on. Honestly I never noticed s-on until now. However, I was able to root and get clockword mod 6.1.1 and it ran smoothly for a weeks.
darko4 said:
By doing the clear storage, would that change my device to s-on.
Click to expand...
Click to collapse
No. Only by flashing another bootloader will you get S-ON back. You probably did not have S-OFF before anyways but FYI Esprimg.zip does flash the bootloader so you're stuck on S-ON for now.
If the Esprimg.zip update method was successful it should have flashed back the stock recovery for you. I can't think of anything that could go wrong at this point except that u have a bad or corrupted Esprimg.zip. Did you use the champion build or the ENG build? If me I'd try to download it again and give it another go.
Good luck!
Ok so Esprimg.zip may be bad, and pretty much that is my only saviour;ok I understand.
I was using Esprimg.zip from other guides. Those were 137 mb
This time I used the one from here.
HOW-TO * Flash the Eng-Release to the Slide *6/15/2010
http://forum.xda-developers.com/showthread.php?t=703076
I am going to assume this the the eng build. It was 137.1 mb.
If this does not work the I guess I have to go champion build.
------------------------------------------------------------------
Failed
Champion build esprimg.zip is next.
A few more ideas.
manually install the recovery using fastboot.
troubleshooting without simcard?
My spl s-on so would that be possible?
Is there a way to maybe re root?
I read in one post that a guy sold it on ebay..i would hate to do that with just a month of ownership. would Htc make a warranty request even though I bought it used. Besides you only see bootloader and hboot spl s-on so how could they tell?
So you reach the screen where it asked you whether you want to install the update, you choose "yes" and it goes on to flash everything, radio, bootloader, yada yada, and it fails to boot?
Basically with S-OFF you can boot into fastboot and run
fastboot flash recovery recovery.img
in this case recovery img is CWM recovery. With S-ON fastboot flash is disable so it's not possible.
EDIT: If you do have the champion build on it's basically stock.
I have this exact same issue right now, I've tried the champion and engineering builds of ESPRIMG but with no success. I can't think of anything else that would be causing this in the first place, which is making it so difficult to troubleshoot. The only difference is that I was using CM7 instead of 6, but the exact same thing is going on. I have tried everything that the OP has with no luck. The only possible cause I can think of is that something was somehow corrupted while the phone was on and sitting on my table...because when I picked it back up, it was off and when I tried to boot, I got splash screen... Any other ideas?? I'm all out and just sitting here waiting for some genius light bulb to go off....attic's kinda dusty though..
With S-ON fastboot flash is disable so it's not possible.
So basically these are my options
esprimg.zip (if that does not work then use different)
Hboot clear memory,
with S-ON I have limited option
and keep it charged.
Although with fastboot and s-on is there something I could do?
Would rerooting be an option
darko4 said:
Would rerooting be an option
Click to expand...
Click to collapse
I don't see a root method in the forum that does not involve booting into a usable system.
Wait, you guys were able to flash the esprimg.zip right? Because in the guide when it says it requires root it's for flashing the mtd0.img first before rebooting into HBoot. Since you don't have a working system you cannot do that and if HBoot refuse to take your esprimg.zip then you need to do the Goldcard method. Otherwise I don't see why having root will make a difference.
So at this stage of the game I should do this..
1.get on my knees
2.put my hands together.
3.and just pray?
ok all jokes aside. Continue to try Esprimg.zip and update(all are successful but I still get splash)
I can't change my recovery since I have s-on
and no way of getting s off since i cant get in the phone, not even recovery,just h boot
So in a sense i have a lovely soft bricked mytouch 3g slide.
Later I might compose a list of the programs i had on the device, but i doubt that would make a difference. I appreciate the help and assistance, I am going to click the thank button for you gents.
In the mean while i got a tmobile comet for 136 one day shipping..No rooting on this one cause finals are coming and I do not have time to troubleshoot for hours. I love android cause of custom roms, but not being able to get in recovery mode...ah say no more. I am going to be one of those people who just downloads free software and complain to phone carriers about OTA.
Same here. I held off rooting and all until my exams were over because I know I'm going to go all the way until I get S-OFF.
I know many discourage S-OFF because it can potentially brick during the process but if you do read up and follow instructions very carefully it is really not that risky. And it'll be very useful in situations like this.
I'm sorry to hear you have a soft-brick. Maybe a dev will stumble upon and provides new insights but I afraid this is all we have in the forum for now.
to be honest i skimmed through the post, and im sure you did try this but just want to ask have you tried the official RUU update to see if you can get things back up running that way?
yeah I understand following directions carefully, but when you follow all of directions and get it working,and make backups, but then you turn the phone off and then turn it on. Then all of this happens.
ah let me stop my whining and download more esprimg.zip .
I just want to know what caused it. was it an application, cause if that is the case then I want to know so no one else get hurt.
(one interesting note, avg antivirus said my device was infected with viruses. It said with the apps, I did not clean it. i uninstalled avg. I presumed it was a false alarm cause the phone is rooted with applications with high privileged) Oh well
---------------------------------------------------------------------------------------------------------------------------------------------------
oh well. back to the esprimg.zip
never tried RUU, if it comes in a esprimg.zip then i guess i can try. if not then i do not know how to use it with mine in its current state
S on (so no advanced fast boot options
Hboot only
no recovery.
clear memory
only productive thing is successful esprimg.zip updates
its the official update to froyo, and need HTCsync and the RUU from htc how the installs procces goes i dont really know, but im sure there is a RUU update that you can use to update via bootloader,
ok i got htc sync
and the official exe.
my pc only detects the device in hboot. The device will read usb hboot.
1 might fiddle around for 20 mins to see whats what.
.
If it was like a esmprimg.zip then it would seem more feasible.
goood luck hope you get your phone back up and running
well a week ago it finally booted. I felt that it was a fluke so I pressed the power button to reboot. I tried to turn it back on then it was stuck at the splash screen.
I am now starting to think it is a hardware problem. Either way the unrooted tmobile comet,yes it is small, is doing wonders. The battery life is way better then a iphone 3g.
Just remember guys, if you get an android phone, make sure it is a popular one. That way you are more likely to get support because of the bigger fan base. Oh well it was fun while it lasted. The only thing I hate is that i could have gotten an xbox 360 for the same price. oh well, thanks for the assistance. i will lets you know any further updates.
Alright. For starters, xda has been VERY VERY helpful to me over the past few months and I thank everyone who has ever contributed to a question or a discussion I have read. That being said, this is my first post. I watched the newb video, read many forums (both xda and others), google searched, read some more threads, kept reading threads, tried some methods described in some threads, bookmarked some interesting threads for if my phone ever works again, and read some more threads.
I am not saying the answer is not already out there, I am saying I have reached my resourcefulness cap.
Anyway, to the root of the problem: I'm not entirely new to rooting, and am comfortable using recovery and hboot to flash roms. I also had a nandroid backup! for SOME SILLY reason, while in my clockworkmod recovery this morning (maybe slightly due to being half asleep which is why I now recommend being fully awake before entering hboot or recovery or rom manager....etc) I formatted the system on my phone. I THINK.
My phone will now load up to display the bootloader, and go into recovery mode, and flash roms, but when I flash a rom, nothing changes. If I boot my phone up, it will show a notification bar at the top like usual, a stock wallpaper, and that is IT! it will show a message notification and missed call icon since I have them, but the touch screen will not work. The rosie buttons at the bottom do not show up (i.e. phone button or all aps button) no apps appear, no clocks except for in the notification bar... hardkeys have no effect (home button search button menu or back) and volume keys will not work. The lock button will only lock and unlock the screen, not power off or reboot or anything. If plugged in at this point, it is charger only.
So, I can take the micro sd card out and put files on it from my PC via a microsd-usb converter thing...
I have tried putting new roms on the sd and flashing them from recovery, no effect. Tried the RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe program, it always says that my phone has below 30% battery and will not continue (this is not the case as I have two batteries both have been fully charged because the phone will still charge them...)
And I have tried putting PC36IMG.zip files on my sd card to no avail.
I am thinking that the system was wiped because it seems like there is no boot image on the phones internal memory itself. I am currently looking for a way to place a boot image on the sd card to possibly flash it or some sort of update.zip so that my bootloader will ask me to update upon reading it.
Sorry for the long post, and ask any questions I will answer as best I can.
I am posting preemptively to the boot image adventure so that if it does not work, maybe I can have some help finding a solution by then.
I was going to take my evo to the sprint store since it is under warranty but if they go into recovery they will see clockworkmod recovery.
Thanks to all for any form of guidance!
I did just notice in my Bootloader menu (HBOOT-2.10.0001) that it says Supersonice evt2-3 **** S-ON
I don't know how because I thought it was a requirement that it says S-OFF to be rooted and flash roms, but I have definitely flashed roms before and gained su access to applications and such. BUT since it says S-ON would it then be covered by the warranty if it is not rooted?
Thanks again.
I you want to flash a boot image, you can take the boot.img from an RUU for the firmware you are, place it in your adb tools folder, then flash it using the commands:
fastboot flash boot boot.img
fastboot reboot
I'm not sure how to identify what firmware I am. Unless your talking about the Hboot version? and also, I can't place anything in any folder except onto my sd card. I have no access other than that to the phone. On the sd card there are no files except for what I put on there.
...aaand not to mention I don't know what adb is exactly...
Does your phone still go to clockwork when you go to recovery?
Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!
Timeconsumer10 said:
Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!
Click to expand...
Click to collapse
Welcome, but yes, you do need to have had usb debugging enabled, so we'll see how that goes.
SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.
Timeconsumer10 said:
SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.
Click to expand...
Click to collapse
Lol, it'd take you 200,000 days since you can only thank 5 times a day Though glad you're rooted now.
shortydoggg said:
Does your phone still go to clockwork when you go to recovery?
Click to expand...
Click to collapse
Yes it still goes to clockwork because its rooted.. now my screen legitimately does not work in certain areas of the screen (not responding to touch) so I'm going to try and get it stock stock stock unrooted and go for warranty replacement. Any ideas please let me know. Currently trying RUU Supersonic...
So, I got an ERROR [110] message from the RUU package its a file open error... :/ now i dont know what is up. Says I need a complete RUU package. Looking for another one or another option now.
If i boot phone normally now it just goes to a black screen with "htc" in the middle and "!" in a triangle in all four corners. Can't do anything from that screen.
If I boot into bootloader once where it says SHIP S-OFF at the top and instead of recovery and all those options it just says RUU but you cant do anything there... :/ I now, however cannot even get to the bootloader screen.
Could they tell it is rooted?
Maybe I could say I finally decided to do sprints OTA update that I've been denying for a while and this is the result.
Anyone agree disagree?
COCLUSION!
So. Since it has just the HTC logo and four error icons one in each corner... I took it into a sprint repair store. It would not boot into bootloader as a hard reset, so the guys at the store were stumped. They had actually never seen this before =). They asked me if I rooted it and all so I just played dumb. I told em I didn't know what that really was. They kinna explained it and I told em I didn't even have a computer (not a lie actually I sold mine and now use my dads or gfs lol). The logo on the screen was an oooold htc logo from like hero or so. So they just put it in the system as a wont even turn on type of thing and gave me a new phone since I was under warranty =) gonna see if I can live without root juuust for a little bit because work and school are gonna keep me busy for a while. I am certain to return though!
Can't wait to see what the devs can do by then!
Thanks to all for the help!
Hello Im Terry
Well this is far from my first root and flashing roms to phones....
i recently got a lg g2 sprint device 4.2.2, and of course i came here to root it, now the root was simple went through fine using a method i found here on the site... after this i wanted to put a different rom on it... well i installed twrp recovery, then i was trying to boot up into recovery, it wouldnt work at all whatsoever, wether i tried turning the phone off and holding the power and volume down button, releasing when screen turns on for a second then pushing them both again... this would just load the normal sprint screen, so i would try through the twrp program to reboot into recovery and the exact same thing happened.....so i googled it and i found this method to "supposably" fix it...
teamw.in /project/twrp2/197 <----- sorry about the space there but the forum wouldnt let me post the link and i cant describe what i did to cause my problem if i cant post this link.
i used the method here with the file for sprint phones.
now after doing this i tried to reboot into recovery mode using the power and volume down method, still nothing, so then i tried through the twrp program, well what happens is a screen comes up, which when ive searched this its only people that cant get past this screen and there phone is soft bricked.... [470] fastboot mode started and on the line under that it says [520] udc_start()
this is a black screen and it stays there.... now i found a file here that a guy put on the phone to help get wifi working, which i can be happy with the phone if i cant figure out how to put a rom on the phone if i can atleast be able to tether my phone since that is one of the main reasons i root, well when i tried to flash this file using the twrp program with the phone on it rebooted to the black screen with fastboot and udc_start
so basically i cant get into recovery mode at all, and i havent been able to this entire time, i could never even get to the initial sprint option to erase all settings holding those 2 buttons down.
now obviously i want to fix this, i want to figure out how to get into recovery mode. and i just got this phone from sprint 2 days ago so it already has the sprint spark update, im not sure if that what might be causing all of this if its incompatible with sprint spark or not... i know the 1 rom i looked into said it was incompatible with it, but i didnt see anything with the others....
so after figuring out how to get into recovery mode and fix my recovery mode can someone please tell me which of the roms that are currently out for my phone are compatible with sprint spark if any. thanks so much and i hope somebody can help me. have a great day and take care
well just a quick update, i uninstalled and reinstalled twrp now this is what i get when trying to boot into recovery from the app
[470] fast mode started
520 udc_start()
690 - reset -
700 -port change-
890 STALL GET_DESCRIPTOR 128 6 1006 0 18
60710 fastboot: processing commands
Trippinshrumes said:
Hello Im Terry
Well this is far from my first root and flashing roms to phones....
i recently got a lg g2 sprint device 4.2.2, and of course i came here to root it, now the root was simple went through fine using a method i found here on the site... after this i wanted to put a different rom on it... well i installed twrp recovery, then i was trying to boot up into recovery, it wouldnt work at all whatsoever, wether i tried turning the phone off and holding the power and volume down button, releasing when screen turns on for a second then pushing them both again... this would just load the normal sprint screen, so i would try through the twrp program to reboot into recovery and the exact same thing happened.....so i googled it and i found this method to "supposably" fix it...
teamw.in /project/twrp2/197 <----- sorry about the space there but the forum wouldnt let me post the link and i cant describe what i did to cause my problem if i cant post this link.
i used the method here with the file for sprint phones.
now after doing this i tried to reboot into recovery mode using the power and volume down method, still nothing, so then i tried through the twrp program, well what happens is a screen comes up, which when ive searched this its only people that cant get past this screen and there phone is soft bricked.... [470] fastboot mode started and on the line under that it says [520] udc_start()
this is a black screen and it stays there.... now i found a file here that a guy put on the phone to help get wifi working, which i can be happy with the phone if i cant figure out how to put a rom on the phone if i can atleast be able to tether my phone since that is one of the main reasons i root, well when i tried to flash this file using the twrp program with the phone on it rebooted to the black screen with fastboot and udc_start
so basically i cant get into recovery mode at all, and i havent been able to this entire time, i could never even get to the initial sprint option to erase all settings holding those 2 buttons down.
now obviously i want to fix this, i want to figure out how to get into recovery mode. and i just got this phone from sprint 2 days ago so it already has the sprint spark update, im not sure if that what might be causing all of this if its incompatible with sprint spark or not... i know the 1 rom i looked into said it was incompatible with it, but i didnt see anything with the others....
so after figuring out how to get into recovery mode and fix my recovery mode can someone please tell me which of the roms that are currently out for my phone are compatible with sprint spark if any. thanks so much and i hope somebody can help me. have a great day and take care
Click to expand...
Click to collapse
Since your phone is only new, have you tried calling the tech support of Sprint? Or have you tried going to Sprint store to help you out with that?
to the post above me... yea that sounds like a great idea, hey sprint can you help me root my phone so i can tether without you charging me? thanks guys!... can you please not troll? if you're not going to help you dont have to respond. Thanks!
so i followed this post now, what i didnt do was patch loki on the newer vza firmware.... so i followed this thread here which is supposed to fix that... and yet im still having the same thing, btw as i posted the change in commands before its because i had my phone plugged into my computer that it showed me that.
forum.xda-developers.com/showthread.php?t=2522965
im not sure what im doing wrong here, but as i go through this i will surely document it incase someone else runs into the same problem in the future.
thanks for any help in advance
i made a mistake when i was doing this.... after everything when it says to use flashify to find the file... it wants you to find what is now the updated twrp 2.6.3.3 version and flash that as the last step... this is now complete. if anyone else runs into this in the future hopefully you dont do something slightly stupid like i did. thanks again xda developers cuz your all some genius ass people with all this info here
Trippinshrumes said:
well just a quick update, i uninstalled and reinstalled twrp now this is what i get when trying to boot into recovery from the app
[470] fast mode started
520 udc_start()
690 - reset -
700 -port change-
890 STALL GET_DESCRIPTOR 128 6 1006 0 18
60710 fastboot: processing commands
Click to expand...
Click to collapse
Turns out you have to downgrade your ABOOT, I had the same problem .. ...
http://forum.xda-developers.com/showthread.php?t=2627765
Follow those instructions to downgrade to zv7-aboot.img, then use FLASHIFY to flash the TWRP recovery image .. ...
also, the problem i was having with booting into recovery is i just have to hold the power and volume down buttons till i get the recovery menu.... not let go when the light comes on like a bunch of things say....
also if anyone knows, it says the d3rp g2 rom doesnt work on spark that it will guaranteed brick my device, now i have it fully backed up and i could just do a test run and see... although i dont feel like having to mess with that....
has anyone successfully flashed d3rp to the spark version? and if that is incompatible none of the other roms mention anything about it.... so if someone could tell me which roms do work on the spark version i would appreciate that...
also +1 to the guy that offered help after i figured it out. i appreciate it!