Develop Bugs

[Q] Recovering from unusual boot loop

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.

[Q] Bricked if I cannot reach recovery?

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.

[Q] OMG! Accidentally Formatted system data!

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!

GN not starting

hi,
i need help my GN is not starting after I flashed a theme all i can just get into clock mode recovery even i didn't have any back up or any restore point it just shows google logo when i start. Please helppppppppppppppppppp pleaseeeeeee
thankzzz
now i am stuck on below attachment please help thnkzz so much for all reply till now

since you didn't do a Android your basically screwed so all you data is gone you only hope is to transfer a file through fastboot(can you even do that?) Or boot to Odin mode and flash a stock image
Sent from my Galaxy Nexus using XDA App

GSM or LTE Gnex? What ROM were you running?

Golden rule: Do a backup before doing anything to your phone!
Now all you can do is to download EXACTLY same ROM as you were using by now, wipe cache/dalvik-cache, flash this ROM once again and hope that i'll boot. If it won't you'll have to wipe /data is well.

Sleuth255 said:
GSM or LTE Gnex? What ROM were you running?
Click to expand...
Click to collapse
HI
its gsm i tried to flashed the same rom but still the same only i can access is to recovery

cordell507 said:
since you didn't do a Android your basically screwed so all you data is gone you only hope is to transfer a file through fastboot(can you even do that?) Or boot to Odin mode and flash a stock image
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
tnkz bro but i am new to android please help how to do it with Odin

well since you can boot into recovery try searching in your sdcard folders if youve left a ROM .zip there laying around and if this is the case just flash it and youre back on track

nonione said:
well since you can boot into recovery try searching in your sdcard folders if youve left a ROM .zip there laying around and if this is the case just flash it and youre back on track
Click to expand...
Click to collapse
unfortunatly i delete system file and data file also in recovery i tried to flash the zip update but no result helpppppppppppppppp

salym said:
unfortunatly i delete system file and data file also in recovery i tried to flash the zip update but no result helpppppppppppppppp
Click to expand...
Click to collapse
This will help you get back to stock
http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my GNex {GSM} T-Mobile

Change your spark plugs.
Sent from my Nexus in Texas.

spaceman860 said:
This will help you get back to stock
http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my GNex {GSM} T-Mobile
Click to expand...
Click to collapse
Hi bro i tired with Odin but stops on userdata any help thnkzzzz

salym said:
hi,
i need help my GN is not starting after I flashed a theme all i can just get into clock mode recovery even i didn't have any back up or any restore point it just shows google logo when i start. Please helppppppppppppppppppp pleaseeeeeee
thankzzz
Click to expand...
Click to collapse
i am stuck on this now please help

ouch... softbrick.
put your phone down.
take a deep breath or two.
If you are old enough, grab a beer and relax for a bit. Think calming thoughts.
Now, start learning about how to mod your GNex. We can help.
Here's your First assignment:
find out if you still have a bootloader by booting into fastboot mode. Report back with your findings and a screenshot!

Sleuth255 said:
ouch... softbrick.
put your phone down.
take a deep breath or two.
If you are old enough, grab a beer and relax for a bit. Think calming thoughts.
Now, start learning about how to mod your GNex. We can help.
Here's your First assignment:
find out if you still have a bootloader by booting into fastboot mode. Report back with your findings and a screenshot!
Click to expand...
Click to collapse
Still have a bootloader? Are you serious? You need to learn how to use an android device as well.
To the OP: Do a factory reset in Clockwork and go to mounts
and format /system. Flash the ROM zip. Profit.

Absolutely serious. Have you been reading this thread? The OP needs to start at ground zero and stop just trying every tool he/she sees. My purpose was to get this person to do some research and I was establishing a knowledge baseline. One plan I was considering was to help the OP install the GNex toolkit then locate stock images and obtain a working build. Your cryptic one liner bit should prove vastly more useful to this guy though. I'll let you have at it and go back to my dev work. lol at least this post was a good way to make sure gapps/root capabilities are properly cooked into my latest test build ....
Sent from my Full AOSP on Toro using xda premium

Sleuth255 said:
ouch... softbrick.
put your phone down.
take a deep breath or two.
If you are old enough, grab a beer and relax for a bit. Think calming thoughts.
Now, start learning about how to mod your GNex. We can help.
Here's your First assignment:
find out if you still have a bootloader by booting into fastboot mode. Report back with your findings and a screenshot!
Click to expand...
Click to collapse
U r right i am not good in android but i tried to be and this happens, meanwhile nothing shows after i start the device it shows the !!!! mark with device the PC logo,this happens due to ODin actually the SUMSUNG ADB interface shows ! mark because i cant debug from device even no bootloader works any more thnkz for replying

*facepalm*
OP, you are holding it wrong.
I can think of at least 2 ways to recover from a situation like this. Both are well described in these forums (search works 99% of the time).
....
Oh come on, you don't have the zip of the last rom you flashed, get another one, hey, its free right? **** we dont know nothing about but we'll flash it anyways!
Man...If you have cwm recovery, you're safe. No need to go messing with fastboot (forget odin) just yet. Now stop wasting everybody's time and learn to help yourself.
Here's a few tags to get you started:
cwm, recovery, adb, bootloader, fastboot

bk201doesntexist said:
*facepalm*
OP, you are holding it wrong.
I can think of at least 2 ways to recover from a situation like this. Both are well described in these forums (search works 99% of the time).
....
Oh come on, you don't have the zip of the last rom you flashed, get another one, hey, its free right? **** we dont know nothing about but we'll flash it anyways!
Man...If you have cwm recovery, you're safe. No need to go messing with fastboot (forget odin) just yet. Now stop wasting everybody's time and learn to help yourself.
Here's a few tags to get you started:
cwm, recovery, adb, bootloader, fastboot
Click to expand...
Click to collapse
i tried more than one day on this issue its only starts with !!! mark on it nothing else, i have attached the pic i cant access any bootloader or any cwm or any thing all i did with Odin and stuck to attached pic even i start the device its shows the same pic.
http://www.youtube.com/watch?v=WdM2M8Nz6QQ this I used on Odin
thnkzz

As I suspected earlier, it appears that the OP may have trashed his bootloader partition when he tried using Odin to flash the 4.0.2 factory image (which includes a bootloader). At one point he had CWM but not any more since he can't boot to the recovery partition.
Another possibility is that the Odin tool itself places the device in this mode and it can't be manually reverted by starting up in fastboot mode. Looking at the picture, it literally appears that the phone is saying that a flashing operation is half finished but the phone has lost the PC connection... This would be a lot like what I've experienced with iPhones.
In either case, I can deduce that Odin is the tool to use to clear this softbrick.
Hopefully, it'll be flame-off now Sdobron. Perhaps you might want to help out here since I'm not up to speed on the Odin tool myself and would like to learn more about it.
@salym: I know this may be redundant but I need to establish your problem baseline empirically. Once again, can you verify that when you hold vol down/vol up then press power that you get the image you posted?

Use Fastboot!
Dude, it looks like your problem is with crappy boot sector.
While turning on your phone, hold both volume up and volume down buttons, and long press power button untill you feel single vibrate feedback.
Then connect your phone to the computer via USB, and if it doesn't detect drivers, google "samsung android usb driver". Additionally you can install PDANet application (X64 or x86 depending on you system).
THen download Fastboot - there are plenty of instructions how to flash it, and flash stock images (that come with radio, boot sector, rom itself, etc) - there are also plenty of discussions about how to do it. PM if you have any other questions!

[Q] S-off vs Unlocked bootloader

So I am new here and want to root my EVO. Ive spent a few hours now reading and have hit a roadblock (I think.) I went to the READ FIRST thread and found out that since my hboot version is 2.18 I need to unlock the bootloader via HTC. that is done. the next step appears to be following a link to another site to get my phone to S-off. However the first readme section of that post says I dont need s-off just to get sprints bloatware off of my phone, which is a big reason I'm here in the first place. I went back to the origional thread here and the next step appears to be a nandroid backup - but my phone wont run it. I get a red triangle, which google claims is because the phone isnt s-off...
3 questions
1) do i need a backup of the stock setup before I go forward, and if so how do I get it to work?
2) do I need s-off. All I want is to flash a ROM without sprints software. At least for now.
3) If i skip the stock backup, what happens when I need to take the phone back to sprint?
I'm sure this has been asked a gazillion times, and I'm sorry. Just seem to be in a loop of need backup first, but need to flash a rom to be able to backup...
The phone is already unlocked, and the HTC unlock wipes it, so im not concerned about data - its already gone.

Sounds like u need to flash a recovery first. I recommend smelkusmod amonra. Just look for it in the dev section. If u want to flash it being unlocked s on, u will need to download flash image GUI from the play store.
Sent from my PC36100 using Tapatalk 2

koker93 said:
So I am new here and want to root my EVO. Ive spent a few hours now reading and have hit a roadblock (I think.) I went to the READ FIRST thread and found out that since my hboot version is 2.18 I need to unlock the bootloader via HTC. that is done. the next step appears to be following a link to another site to get my phone to S-off. However the first readme section of that post says I dont need s-off just to get sprints bloatware off of my phone, which is a big reason I'm here in the first place. I went back to the origional thread here and the next step appears to be a nandroid backup - but my phone wont run it. I get a red triangle, which google claims is because the phone isnt s-off...
3 questions
1) do i need a backup of the stock setup before I go forward, and if so how do I get it to work?
2) do I need s-off. All I want is to flash a ROM without sprints software. At least for now.
3) If i skip the stock backup, what happens when I need to take the phone back to sprint?
I'm sure this has been asked a gazillion times, and I'm sorry. Just seem to be in a loop of need backup first, but need to flash a rom to be able to backup...
The phone is already unlocked, and the HTC unlock wipes it, so im not concerned about data - its already gone.
Click to expand...
Click to collapse
You don't need S-OFF, but what you do need is a custom recovery. That's how you flash Superuser and get root user access.
That thread you speak of gives you a couple of methods for flashing a custom recovery. Try those, or search around for a few guides that give you the specifics.
If you need any additional help, feel free to ask.

How do I know if I am rooted?
Go into Bootloader. If you see S-OFF at the top, you are fully rooted.
I am rooted now. What can I do?
FIRST MAKE A NANDROID BACKUP! ALWAYS DO THIS BEFORE YOU FLASH SOMETHING. THESE ARE BIG FILES SO TRANSFER THEM TO YOUR COMPUTER TO SAVE SPACE ON YOUR SD!
Click to expand...
Click to collapse
Thats from the read first thread. Thats where I'm stuck. According to what I've read I am rooted and should now make a backup. But the backup wont run. So if I skip the stock backup (or run it later and I'm just not understanding) can I still get the phone back to where it is now? I read a couple years ago about rooting that you needed a backup of YOUR phone to revert to stock and take in the phone, not just a backup of any phone.

koker93 said:
Thats from the read first thread. Thats where I'm stuck. According to what I've read I am rooted and should now make a backup. But the backup wont run. So if I skip the stock backup (or run it later and I'm just not understanding) can I still get the phone back to where it is now? I read a couple years ago about rooting that you needed a backup of YOUR phone to revert to stock and take in the phone, not just a backup of any phone.
Click to expand...
Click to collapse
Are you trying to back up from recovery?

Yes, but without flashing anything yet.
Sent from my PC36100 using XDA

koker93 said:
Yes, but without flashing anything yet.
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
Then I don't understand why you wouldn't be able to make a nandroid. You have an SD card in the device, correct? What error message are you getting?

Yes, there is an SD card in. It shows a phone with a green sync and then after a few seconds that changes to a phone with a red triangle and an explanation point. If i hit power, vol up, and vol down at the same time twice it goes into recovery but says it could not create some e drive folder and backup is not listed as an option. I can get the exact directory its upset about, but ill obviously have to reboot a few times, I'm not at home right now.
Sent from my PC36100 using XDA

koker93 said:
Yes, there is an SD card in. It shows a phone with a green sync and then after a few seconds that changes to a phone with a red triangle and an explanation point. If i hit power, vol up, and vol down at the same time twice it goes into recovery but says it could not create some e drive folder and backup is not listed as an option. I can get the exact directory its upset about, but ill obviously have to reboot a few times, I'm not at home right now.
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
That is the stock recovery. Again, as was said earlier, you need to flash a custom recovery in order to perform the next step in your process.

So i went and downloaded Amand ra's custom recovery. No dice. bootloader says
Main version is older
Update Failed
Do you want to reboot device?

Try reopening the command prompt from the folder where you unlocked the bootloader from on your computer. Download and place the attachment inside that folder. Connect your phone to your computer. Boot into your bootloader, then click on FASTBOOT, not RECOVERY. The bootloader should now read FASTBOOT USB in red. Then type the command:
fastboot flash recovery recovery.img
then reboot the phone and see if you can get into RECOVERY.

That appears to have done the trick. doing the much talked about nandroid backup now. I'll be back when i have 20 questions about the eventual ROM install

Thanks for the help guys. I successfully backed up my phone, flashed nitrous, repartitioned my SD card, flashed it again, and am having a fun time fooling around. And then realized much later that the backup was only on the SD card. The SD card I wiped so I could partition it...oops
Looks like there are stock Roms anyway so I'm not too worried about future Sprint support.
Thanks again.
Sent from my PC36100 using XDA