Related
Hello,
I was trying to flash a new Rom onto my phone (Superfly) and installed the .zip file from clockwork, however, when I try to boot the phone, it sticks at the Mytouch slide screen.
I cant load into the card nor the phone.
Is there any way to reverse this?
Thanks in advance!
Hopefully you made a backup. You should still be able to boot into recovery and restore your backup or even flash a new rom.
sandpaperback said:
Hopefully you made a backup. You should still be able to boot into recovery and restore your backup or even flash a new rom.
Click to expand...
Click to collapse
The problem the OP and myself are having is that we cant load Clockwork recovery, and I think its cause when we flashed the new rom, it did away with USB debugging mode, and now we cant get back into the OS to select it again. I too am stuck in this loop, and I might just have to bite the bullet and bring it in to tmo and tell em it just stopped working for no reason...
dion20 said:
The problem the OP and myself are having is that we cant load Clockwork recovery, and I think its cause when we flashed the new rom, it did away with USB debugging mode, and now we cant get back into the OS to select it again. I too am stuck in this loop, and I might just have to bite the bullet and bring it in to tmo and tell em it just stopped working for no reason...
Click to expand...
Click to collapse
The USB debugging option means nothing while booted in to recovery. If you haven't flashed the engineering rom before you will need to redo the loop/ota.zip/update.zip spoof to get back in to clockwork.
I did do a nandroid backup, but the phone magically can not find it now. And It took forever to get to work, but I was finally able to get back into clockwork and tried to install another a different rom (Kanged CM6 ROM) but ended with the same results of sticking on the mytouch slide startup screen. Frustrating, because it probably took about 3 hours to get back into clockwork!
Any other suggestions???
wipe everything on the phone, find the thread that walks you through that
cursexcore said:
I did do a nandroid backup, but the phone magically can not find it now. And It took forever to get to work, but I was finally able to get back into clockwork and tried to install another a different rom (Kanged CM6 ROM) but ended with the same results of sticking on the mytouch slide startup screen. Frustrating, because it probably took about 3 hours to get back into clockwork!
Any other suggestions???
Click to expand...
Click to collapse
As was noted previously, if you haven't flashed the ESPRIMG rom, you're basically looking at re-rooting your phone every time you want to install a different rom. This means going through the whole process again and again and again.
falken98 said:
The USB debugging option means nothing while booted in to recovery. If you haven't flashed the engineering rom before you will need to redo the loop/ota.zip/update.zip spoof to get back in to clockwork.
Click to expand...
Click to collapse
thats weird, cause before I could get into clockwork after 2 tries max, not I tried repeatedly for 10 mins and it didnt work, so I should just keep tryin to get into clock work then?
Yes, keep trying. And when you do, please flash the engineering rom and keep the proper update.zip on your card! It will save you a lot of trouble in the long run.
sandpaperback said:
Yes, keep trying. And when you do, please flash the engineering rom and keep the proper update.zip on your card! It will save you a lot of trouble in the long run.
Click to expand...
Click to collapse
will do, theres alot of assumptions around here tho, and newbs to android are kinda expected to know things without them being stated in the threads..
Now I know theres something that makes it so I dont have to go thru the pain of rooting to get into clockwork I'm def gna use it..
what method should I use? Ive been doing the following and no luck so far
1 - cd to android sdk tools folder
2 - vol down + power for recovery
3 - highlight recovery
4 - run loop in cmd
5 - plug usb into phone
6 - plug usb into pc, and before it changes to HBOOT from USB i hit power to select recovery
7 - adb devices sees it as an offline device for a few cycles, then it disappears.
after step 7 I've tried running update.zip
unplugging and plugging back in
ctrl+c to stop the script when its offline
unplug when its noticed as an offline device
whats the best way to get into it now?
======
EDIT - finally got it into recovery, i loaded up htc's recover with it plugged it to the pc so it loaded up HBOOT from USB
normally your are not bricked if:
1. you can boot into recovery
2. you can not boot into recovery yet you can boot into bootloader [HOLD (power + volume down) to boot]
Don't worry I got a black/blank screen of death the other day for flashing the wrong boot.img fortunately I was able to boot into bootloader and start from scratch using the ESPRIMG.zip
dion20 said:
will do, theres alot of assumptions around here tho, and newbs to android are kinda expected to know things without them being stated in the threads..
Click to expand...
Click to collapse
I agree to an extent, but if you take the time to read through things thoroughly (as in every post in the How To Root or Engineering Build or even Rom Bible thread), you'll be okay. This is my first Android device as well. I put off rooting for a solid couple of weeks while I read through everything I could. I was completely paranoid about bricking my phone. Eventually, I went for it. Even then I had a couple hiccups along the way (including have to re-root two more times), but all the information is here.
So an update:
I went to a Tmobile retail store to see if I could do a direct swap and am having a new phone sent out to me. I will definately take all the replies into consideration when starting the root process on my new one! My final question is, since I am afraid Tmobile will not find my phone valid to be replaced under warranty due to it being rooted, is there any way to unroot and go back to stock? I have googled it, but cannot find anything specific for the slide...
Thanks!
cursexcore said:
[blah blah blah....] My final question is, since I am afraid Tmobile will not find my phone valid to be replaced under warranty due to it being rooted, is there any way to unroot and go back to stock? I have googled it, but cannot find anything specific for the slide...
Thanks!
Click to expand...
Click to collapse
My question: did u search here?
http://forum.xda-developers.com/forumdisplay.php?f=660
And found items about the champion build and this little file named ESPRIMG.zip?
U can also check out the ROM BIBLE stickie post.
u can try this:
http://forum.xda-developers.com/showthread.php?t=713507
or you can try this:
http://forum.xda-developers.com/showthread.php?t=713507
now if you really searched you would of found your own question:
http://forum.xda-developers.com/showthread.php?t=744709&highlight=unroot
cursexcore said:
So an update:
I went to a Tmobile retail store to see if I could do a direct swap and am having a new phone sent out to me. I will definately take all the replies into consideration when starting the root process on my new one! My final question is, since I am afraid Tmobile will not find my phone valid to be replaced under warranty due to it being rooted, is there any way to unroot and go back to stock? I have googled it, but cannot find anything specific for the slide...
Thanks!
Click to expand...
Click to collapse
I had the same problem you did, and fixed my phone, so its possible. refer to my post on the first page and then refer to this post and use the mirror that Wes himself posted.
http://forum.xda-developers.com/showpost.php?p=7001053&postcount=7
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
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
jenic said:
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
Click to expand...
Click to collapse
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
RMarkwald said:
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
Click to expand...
Click to collapse
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
jenic said:
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
Click to expand...
Click to collapse
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Your concise post is most appreciated. I will do as you instruct and post results back here when finished.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Hit an unfortunate snag right away. fastboot (nor adb) is detecting the device. Screen is showing XC SHIP S-OFF as it should, it is in FASTBOOT USB mode and my computer detects the USB itself just fine.
dmesg output:
[346853.772041] usb 2-6: new high speed USB device using ehci_hcd and address 17
[346853.922917] usb 2-6: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
Thank you though that was a great suggestion! (Was very hopeful for a second there
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
RMarkwald said:
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
Click to expand...
Click to collapse
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
RMarkwald said:
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
Click to expand...
Click to collapse
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
cf9182 said:
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
jenic said:
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
Click to expand...
Click to collapse
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
jaba14 said:
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
Click to expand...
Click to collapse
That was definitely a laugh. Thank you I will see if I can get it replaced! I've been kinda just ignoring the fact that I do not have a phone all this time... Thankfully I had setup the phone to forward calls to google voice. It has been a lifesaver.
Sounds like there weren't any ideas in Q&A for this one, and I haven't seen much in terms of not being able to access recovery, so here goes...
I was happily using CM7, and while reading through a Diablo III news page (hopefully it comes out soon ), my phone rebooted into a boot loop. Weird, but I figured at worst I would wipe data and reinstall a ROM. Unfortunately, I can't get into recovery any longer.
If I boot the phone normally, I see the white HTC splash screen for a few seconds, then it reboots. I can use HBOOT fine, but as soon as I try to reboot normally / boot into recovery / boot into Restore Factory Defaults, my phone will reset. Let me clarify...
Pull and replace battery
Boot into HBOOT (volume down + power)
Select Recovery
Phone reboots and reaches CWM Recovery 3 for about 1/2 second, not long enough for me to click anything
Phone reboots into boot loop
I've used HBOOT to flash to CWM Recovery 3.0.0.8, downgraded to the stock radio, run the 2.2 RUU. I'm still running up against the same boot loop problem.
I wouldn't be surprised if it was a hardware problem, but I'm anxious to hear if anyone has ideas to try first. Additionally, is there any way to restore to S-ON through HBOOT in case I need to bring this into a Verizon store? I have fastboot.exe that can recognize the device over USB while the device is in HBOOT, maybe this will help?
Thanks!
Current state: Ran 2.2 RUU, S-OFF, HBOOT-0.92.0000, AMOLED, 2.15.00.07.28 radio
Thanks again.
Had this exact issue while running cm7. First couple of from when it was crackflashers. I couldn't find anything to help or fix it. I got a new dinc because I can't afford to be without for long.
Good luck dude.
Sent from my ADR6300 using Tapatalk
Thanks for the note. Maybe my fate will be the same. Did you get any sympathy from Verizon?
Doesn't sound like there are even any suggestions using fastboot, lol. [crickets chirping]
Can you flash cwm 2.5.x and try? Not sure if it will help but worth a shot?
sent from a phone
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into bootloader (volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
hope that helps
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
popasmurfn23 said:
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
You are correct.
popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
phaze one said:
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
Click to expand...
Click to collapse
Thanks for the replies.
I tried this method to flash back to the stock 2.2 image before I started this thread. That's what I meant by "I've used HBOOT to ... run the 2.2 RUU." The stock image seemed to install properly in HBOOT. I have evidence that it successfully went back to stock, since I get the original ! triangle graphic instead of CWM when I try to enter recovery from HBOOT. However, I only see the graphic pop up for a brief second before it reboots again. Trying to boot into recovery or the ROM itself still result in a reboot.
I cannot achieve S-ON without having access to recovery, at least there's no way that I've found to do it through HBOOT.
Any other thoughts? I think it's a hardware problem. It appears the phone is back to stock (except it's still S-OFF), but everything outside of HBOOT causes a boot loop. I stopped in at Verizon this afternoon and they'll be sending a new phone to arrive by Tuesday. At this point, it'd be nice to try all avenues of repair for the future benefit of others that run into this problem.
Probably bad memory chips on the phone. Since it happened all of a sudden during normal use it usually indicates hardware failure.
That is pretty much what I determined. Bad hardware. Sorry for your trouble but is nice to know I'm not the only person to ever have this. Also nice to know I didn't miss something that could've brought it back to life.
I filed an insurance claim. Figured since I have had it for years and never used it I'd take advantage.
Sent from my ADR6300 using Tapatalk
You can boot your phone like regular right? Just let it launch up or do you get loops?
Nevermind i see what ur saying. when i was flashing incorrect kernals i would get the same behavior from my phone. So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
If that doesn't work, (I'm assuming that you can boot the phone normally at this point) try re-rooting with the Unrevoked tool.
Then use Rom Manager to flash a newer Recovery (be sure to check Erase Previous Recovery under Settings). If that still doesn't work, I'll see about packaging an RUU in a PB31IMG.zip with a valid version of CWM as the recovery.img within that zip. I'm not sure about the practicality of this final option, but if it comes down to it, I'll attempt to package that up for you.
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Sent via my Incredible CM7 Gingerbread sorcery.
Crans said:
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Click to expand...
Click to collapse
This would work if he could access CWM Recovery, but he can't, thus the issue.
I wonder if he could mount something from within hboot and replace the binary code for the recovery image with a bunch of zeroes and then try flashing another through hboot again.
Sent via my Incredible CM7 Gingerbread sorcery.
I was JUST about to post the same topic when I came across this. I have done the stock image restore, restored BACK to hboot 0.92, back to the most current INC radio, and have tried flashing CW3.0 and Amon_RA. Everything flashes fine but the boot loop continues and if I try to enter recovery, it lasts maybe one full second before rebooting again. The only thing that I can think of that would create this situation for me was that earlier I was trying to update the PRL via *228 on MIUI but the dialpad never popped up so I hung up.
popasmurfn23 said:
So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
Click to expand...
Click to collapse
I'll take another crack at it, but I don't think I had gotten the wrong image. No worries though, it's easy enough to try again using the link on page 1 directly. Can't hurt, right ;-)
RegnierD said:
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
Click to expand...
Click to collapse
Sure. Once again, worth a shot.
RegnierD said:
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Click to expand...
Click to collapse
Thanks for the sympathy . Like I mentioned, I visited the Verizon store and a new one is on its way... doesn't that mean that it doesn't matter (other than for science sake) whether this gets S-On or even fixed?
[waiting for flash of build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
It just seems unlikely that this is a problem with flashing the wrong recovery, or the wrong stock image, since booting into recovery and booting normally both exhibit the same behavior. If I could boot normally into recovery but not boot into a stock image, I would suspect that I had flashed the wrong image. Since both have the same problem, I think it might be something else.
[finished flashing build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
Same behavior. White htc Incredible splash screen -> darkness for a second (presumably while the ROM tries to boot) -> reboot.
Alternatively, HBOOT -> Recovery -> White htc Incredible screen -> Triangle / ! error screen for a half second -> reboot.
[finished flashing CWM 2.5.0.5]
Same behavior:
HBOOT -> Recovery -> White htc Incredible screen -> CWM recovery 2.5.0.5 for a half second (this confirms that it flashed properly) -> reboot.
i ask as i updated my radio last night for the 1st time in aaages and the phone turns on etc as you'd expect. since then though (this morning) i've had random reboots. i've got recovery images of different roms and both do the same.
i tried a clean install of a new rom and it reboots while installing, i try to install again and this time it gets to the "press on the droid" option when it reboots again.
tommo123 said:
i ask as i updated my radio last night for the 1st time in aaages and the phone turns on etc as you'd expect. since then though (this morning) i've had random reboots. i've got recovery images of different roms and both do the same.
i tried a clean install of a new rom and it reboots while installing, i try to install again and this time it gets to the "press on the droid" option when it reboots again.
Click to expand...
Click to collapse
Weird..did u try flashing a different radio?
not yet. in work for a while longer. the only other thing i can see it being, is the kernels in the rom i'm using now, using too little voltage.
might try flashing a different kernel
I have had this problem before & as has been suggested a different radio did solve the problem. Hope it turns out something as simple for you.
As a last resort try wiping and flashing an RUU, that will replace the kernel, radio and rom
yea, had a thought on doing that too. grabbed 2 of em (not sure which i need) but today it's not rebooting
ok, somethings gone real wrong now. cant do anything more than go into fastboot. recovery causes a reboot with 7 vibrations on the boot screen and it wont go past it. i can go into fastboot/fastboot usb and that's it.
how do you flash a ruu now? i found a guide but it refers to downloading .zip images and putting em on an sdcard? i could only see .exe ruus
Just run the ruu exe while your phone is connected in fastboot. Do you have the ruu that was originally on the phone?
Sent from my HTC Desire using Tapatalk
trying it now. got the ruu downloaded. tried it before but got some funky errors
phones doing some funky stuff at the mo. if this works (i hope) then i can use unrevoked and then alpharev to get root/s-off later again yea?
ta mate
Yeah, you can do that.
Sent from my HTC Desire using Tapatalk
coolio.
worked. now booted up. wonder what the hell happened though!
Dunno but I guess you're relieved
Sent from my HTC Desire using Tapatalk
i am, but tried 2 pcs and my netbook, installed usb drivers off their site but just cant get unrevoked working for my desire.
off to try the old goldcard method
odd, even the goldcard tool didnt work. did a year or so ago when i 1st rooted. had to go old school on this thing.
edit
and after several tries, alpharev doesnt work
cant make the phone reboot when it needs to. worked last time with opendesire with no probs at all. no joy with oxygen though, or the default sense rom
ok, thanks to the forum, i've got opendesire installed now and i think somethings up. after an install (clean) it locked. hard. 3 finger salute didn't reboot the phone and had to pull the batt out (other roms caused reboots instead). i decided to take the sim out - and nothing. no more locks/reboots at all.
i'm gonna try the sim in another phone tonight and see what happens.
something very off with this phone.
tommo123 said:
ok, thanks to the forum, i've got opendesire installed now and i think somethings up. after an install (clean) it locked. hard. 3 finger salute didn't reboot the phone and had to pull the batt out (other roms caused reboots instead). i decided to take the sim out - and nothing. no more locks/reboots at all.
i'm gonna try the sim in another phone tonight and see what happens.
something very off with this phone.
Click to expand...
Click to collapse
I had this problem after I flashed a radio. I ended up sending it back to O2 due to a corrupt radio/cpu stack on the actual device.