Develop Bugs

[Q] G2 stuck at HTC screen.

Hey guys, I tried to perma root my wife's G2 last night using Visionary+ r14 but when it tried to reboot it doesn't get past the green and white "HTC" screen, so now I have a couple of questions.
I bought this phone from someone off of Craigslist and it was working great until I tried to root it so it is technically out of warranty do you think I can get it replaced since everything is still stock?
Also I tried to apply the HTC OTA update to fix it and I still have the problem, is there anything I can do to repair this phone? Thanks in advance guys and mahalo!

Okay pull your battery out and put it back in..after dat press power button and volume down button until you get to the recovery screen and do a factory reset..
Sent from my HTC Vision using XDA App

Thanks for the reply jboiii15. I did a factory reset before I flashed the OTA update and I have factory reset several times but still no go. I appreciate you taking the time to help me out.

Did you try this? http://forum.xda-developers.com/showthread.php?t=842495

aznsnake666 said:
Did you try this? http://forum.xda-developers.com/showthread.php?t=842495
Click to expand...
Click to collapse
I haven't tried it because I can't get ADB to work with the phone the way it is, Fastboot works but ADB just shows nothing there while I'm in recovery or the boot screen. Thank you also for the reply. My wife is pissed lol.

Try to extract the ROM from the official RUU and rename it to PC10IMG.zip. Put this on the root of your SD card and boot into bootloader and leave it to work. This should solve your problem Fingers Crossed
JD

do you have s-off??

I don't have S-OFF as I just started the rooting procedure when it decided to take a dump on me, after this I don't think my wife will want me to root any more of her phones although I know she'll miss it after having a rooted G1 running CM and a rooted Slide running Chromatic. Good thing I didn't sell her Slide yet lol.
I'll try to find information on the PC10IMG.zip method now and see what can be done.
Thank you guys for all the help, I really appreciate it all.

itsmekeoni said:
I don't have S-OFF as I just started the rooting procedure when it decided to take a dump on me, after this I don't think my wife will want me to root any more of her phones although I know she'll miss it after having a rooted G1 running CM and a rooted Slide running Chromatic. Good thing I didn't sell her Slide yet lol.
I'll try to find information on the PC10IMG.zip method now and see what can be done.
Thank you guys for all the help, I really appreciate it all.
Click to expand...
Click to collapse
I think the rooting process has corrupted your kernel or rom, it is rare to get a brick from just the visionary process, but i know there has at least been one that this has happened to.
Report back to tell us if the extracted ROM worked for you, there is still hope;')
JD

Oh man this is just getting worse lol. I had the phone sitting here plugged into my laptop while the phone was in the Hboot screen where you can select Fastboot, Recovery and so on. All of a sudden my here Windows give off the noise as if something was connected or disconnected from my computer and I see the screen shut off on the G2 with a red light blinking. Now the phone doesn't power on and the red light blinks while the phone is plugged into the computer but doesn't power on.
As I was typing this the red light came on solid as if it is charging now, maybe it doesn't charge while in that screen and the battery just died I dunno, strange.

JupiterDroid said:
I think the rooting process has corrupted your kernel or rom, it is rare to get a brick from just the visionary process, but i know there has at least been one that this has happened to.
Report back to tell us if the extracted ROM worked for you, there is still hope;')
JD
Click to expand...
Click to collapse
Well I called T-Mobile and they are sending out a new phone, I'm unsure if I should still mess with it or not. I did flash the TMOUSA OTA update and that didn't help, I didn't unpack it to see if it contained a new Kernel but I'm sure it had a new system.img, still think it is one of those that is messed up?
I'm having a hard time finding the things to get the PC10IMG.zip going, work is calling me in different directions and my A.D.D is kicking in lol.

try this http://forum.xda-developers.com/showthread.php?t=855764 i had the same problem like you, steviewevie told me to do it, if you have problem to connect your g2 with sdk download pda net, it works for me and now i have my g2 back with the new root... just do what it said on that link believe me works...
P.D. I am a androidnoober always have a iphone and this was my first time using sdk adb or whatever name is and I did it

Thanks AndroidNoober, I've seen that link in my search for an answer to my problem. One of the issues that is making this harder is that after the phone "bricked" it lost ADB connectivity. I've tried it on two computers that have a properly working ADB (I test it with my N1 and 3G Slide) and it used to work with the G2 but now I can't get it to see the phone, I've heard Recovery has ADB blocked.

semi bricked attempting permaroot
i attempted permaroot and semi bricked my phone. will not boot past htc screen. i can't get adb to work. i am trying to get pdanet installed but it keeps getting stuck on installing on phone. can it install while phone is in recovery mode? i have had no sucess trying to figure this out on my own and phone is not covered with a warranty
i have gotten the phone to read an update.zip file.
it is reading the pc10img.zip as well.
now i just have to get past the htc screen.
i do have s-on as i had just started the process.
any help would be appreciated

Remove root with Broken screen

So the screen of my g2 is all black, and Tmobile has allowed me to do a warranty exchange of the phone, it is s off and clock work recovery with a OTA non rooted file system (did a factory reset in clock work so my personal info wouldnt still be there, but did a back up before so i can still restore. i dont believe i had usb debugging enabled). Can someone help me to get it back to s-on with normal recovery... I have been trying to think how to do it, but cant figure it out. I have another g2 that i do all the same steps with. Any help is appreciated.

Dont worry about it. If your screen is broken they cant see it either! They will wipe the phone replace the screen and give it to someone with a loose hinge. If you still want help did you try to use adb? Does it connect?
Sent from my HTC Vision using XDA App

shortlived said:
Dont worry about it. If your screen is broken they cant see it either! They will wipe the phone replace the screen and give it to someone with a loose hinge. If you still want help did you try to use adb? Does it connect?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
That's stupid. They can tell by diagnosing the phone when they plug it in. They are going to see whether or not you have the factory rom
Sent from my T-Mobile G2 using XDA App

It is not looking like it is going to connect, but if you are pretty sure that they arent gonna look, i wont even sweat it.

I think this thread might work:
http://forum.xda-developers.com/showthread.php?t=835971
But it might be tricky getting past the first step without a screen... but fastboot and adb usually solve most problems...
What hboot do you have installed? Did you install the hboot-eng.img when you rooted?
My theory is that you can use fastboot to flash the parts of the rom, in the right order. Again, this is just my theory and I've never tried this.
http://forum.xda-developers.com/showthread.php?t=838484
The stock ROM has all the parts on it, but it flashes hboot first, which does version checking and will fail when it tries to install the later parts. If you extract the system, recovery, boot images out of the stock rom, you can use fastboot flash {partition} to restore these, then use fastboot flash hboot {hboot} to restore the bootloader. I don't think there will be any way to verify that this works without a screen*.
*While you are at it, you might be able to use the new G2 to backup a rom with debugging enabled and then flash the system.img (and maybe userdata.img) to the broken one, so that you can verify that everything worked.
Hopefully, someone who knows more about flashing that I do can verify if this has a shot at working or not.
Disclaimer: I have no idea if this will work or not. Flash at your own peril.

i have the s-off eng hboot. clock work recovery and i have stock rom installed, i was kind of thinking i could use something to restore the recovery to stock, and somehow flash original hboot, but i really have no idea to actualy do this.

is there any way that i can hex edit the partition on the other phone do a nandroid, then restore the nandroid on the broken phone, then use hboot to flash the ota update and get the hboot and recovery back to original?

Throw it against the wall until it doesn't connect anymore or turn on. Problem solved.

I'm not sure if this will work anymore... I tried to flash the .img parts from a nandroid backup and it seems to get hung up. My terminal has been "sending system.img" for the last 10 minutes. I wonder if this has something to do with how the bootloader was patched to get root?

DJAeroX26 said:
That's stupid. They can tell by diagnosing the phone when they plug it in. They are going to see whether or not you have the factory rom
Click to expand...
Click to collapse
You really think T-Mobile are going to plug in and do diagnosis on a phone with a broken screen ? We're talking about a phone carrier, not HTC themselves

use screencast, its simple to use and puts your screen on your pc..I have used it several times for issues such as this.

how do i install it if i dont have usb debugging enabled.

bobsfoot said:
how do i install it if i dont have usb debugging enabled.
Click to expand...
Click to collapse
hmmm...wait 1, will research it

Of course they can tell if its rooted my point is they wont care to take the time. I am no authority for sure but i will ask this... have you seen one single person who has been denied because they rooted they're phone?
Sent from my HTC Vision using XDA App

I was in a similar situation as you but with a Desire Z, Somehow the screen decided to give up on me so have sent it back to where I bought it from in the UK.
I am fairly sure the RUU changes it to s-on doesn't it? I just ran the RUU and sent it back after screencasting to do a backup of my rom. Still unsure as to what the end result will be with my phone however.

so today the new phone comes, should i just fastboot a new recovery then do a ruu update to put s on, and leave the phone broke and be like no idea, or is there a way to edit the partition version in fast boot?
or do i leave it alone, and just hope they dont care.

They wont care.

steviewevie said:
You really think T-Mobile are going to plug in and do diagnosis on a phone with a broken screen ? We're talking about a phone carrier, not HTC themselves
Click to expand...
Click to collapse
I'm just saying, I work in retail and usually when someone brings something back to exchange when there is a problem...I thouroughly check to make sure if the problem was the user's fault, then i deny the return. They do lose money even if it is a warranty exchange
Sent from my T-Mobile G2 using XDA App

[Q] HTC EVO SHUTS OFF AND LIGHT BLINKs

hey guys i am having an issue with my gf new evo i bought from craigslist and i am hoping its something software based so i can fix it....so here is the details....
My gf recently lost her evo and no insurance so i went on to craigslist to buy one so when i get the phone it looks nice...legit you know....so anyways i get home and get to craking....so when i started first thing i did was opened the recovery and to my suprise the evo S-off and i was like wahhhttt....anyways so i proceded to rooting it with UnrEVOked and did everthing great so i decided to flash the old rom she had on her old phone cause she liked it so i did and short story long got her phone back to normal...until recently the phonw will randomly reboot when were using it with phone calls or NAV or just music or to many things at once and full battery and will reboot try to turn on then ....IT VIBRATES 4...5 times and shuts off and the LED blinks green every second.....the only way i could turn it on is taking the batter off for a few minutes then reinserting batter and BOOM back on like nothing happend....so i need so help please....did a full wipe of everything and reinstalled rom and nothing....OHHH and it came with stock batter and two non stock!!... PLEASE HELP SHES NAGGING TO MUCH LOL

I don't know for sure but I've read that changing your kernel might fix it
Sent from my PC36100 using XDA App

KaL-EL3038 said:
hey guys i am having an issue with my gf new evo i bought from craigslist and i am hoping its something software based so i can fix it....so here is the details....
My gf recently lost her evo and no insurance so i went on to craigslist to buy one so when i get the phone it looks nice...legit you know....so anyways i get home and get to craking....so when i started first thing i did was opened the recovery and to my suprise the evo S-off and i was like wahhhttt....anyways so i proceded to rooting it with UnrEVOked and did everthing great so i decided to flash the old rom she had on her old phone cause she liked it so i did and short story long got her phone back to normal...until recently the phonw will randomly reboot when were using it with phone calls or NAV or just music or to many things at once and full battery and will reboot try to turn on then ....IT VIBRATES 4...5 times and shuts off and the LED blinks green every second.....the only way i could turn it on is taking the batter off for a few minutes then reinserting batter and BOOM back on like nothing happend....so i need so help please....did a full wipe of everything and reinstalled rom and nothing....OHHH and it came with stock batter and two non stock!!... PLEASE HELP SHES NAGGING TO MUCH LOL
Click to expand...
Click to collapse
Hmm. Any time I ever see anyone reporting what you're describing, I've never seen a solution. What I would try though, is to unroot it, by turning S back to On, and then running an RUU. See if it will run stable while on a stock ROM. If so, try rooting again. If it is still doing the same thing after running RUU, with S on, I would take it Sprint. The phone is still under warranty, and if it turns out to be hardware related, you should be able to have Sprint do something for you.
RUU: http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
I also attatched the Unrevoked S on tool. Flash the Unrevoked S on tool in recovery. Confirm that S is on. (what bootloader are you on? If its the Eng .76 bootloader, you don't need the S on tool, in which case you'd just run the RUU). Once S is on, run the RUU, to flash you back to stock. You want to run the RUU that matches your bootloader version, software version, and radio versions the closest. That will take you back to stock, and then you can see how the phone performs.
And it kind of sounds like the phone may have had some issues before. It was obviously rooted, since it was already S off when you purchased it. Who knows what type of issues it had prior to you obtaining it..

Thanks so much!!!
k2buckley said:
Hmm. Any time I ever see anyone reporting what you're describing, I've never seen a solution. What I would try though, is to unroot it, by turning S back to On, and then running an RUU. See if it will run stable while on a stock ROM. If so, try rooting again. If it is still doing the same thing after running RUU, with S on, I would take it Sprint. The phone is still under warranty, and if it turns out to be hardware related, you should be able to have Sprint do something for you.
RUU: http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
I also attatched the Unrevoked S on tool. Flash the Unrevoked S on tool in recovery. Confirm that S is on. (what bootloader are you on? If its the Eng .76 bootloader, you don't need the S on tool, in which case you'd just run the RUU). Once S is on, run the RUU, to flash you back to stock. You want to run the RUU that matches your bootloader version, software version, and radio versions the closest. That will take you back to stock, and then you can see how the phone performs.
And it kind of sounds like the phone may have had some issues before. It was obviously rooted, since it was already S off when you purchased it. Who knows what type of issues it had prior to you obtaining it..
Click to expand...
Click to collapse
Mohawka said:
I don't know for sure but I've read that changing your kernel might fix it
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
ok well thanks so much for your guys help...i take it there has been many reports before regarding this i was thinking it was the BATTERYS and my second gues was the kernel lol hahah so ill try the kernel first if you think that will help k2buckley and then ill will go all out i am not sure which booatloader i have cause i am using wifi tether to write this but as soon as i found out ill report back and again thanks so much

KaL-EL3038 said:
ok well thanks so much for your guys help...i take it there has been many reports before regarding this i was thinking it was the BATTERYS and my second gues was the kernel lol hahah so ill try the kernel first if you think that will help k2buckley and then ill will go all out i am not sure which booatloader i have cause i am using wifi tether to write this but as soon as i found out ill report back and again thanks so much
Click to expand...
Click to collapse
I don't suspect that changing the kernel will have any affect on your situation. Sometimes a kernel can cause the phone to reboot, but your phone isn't just rebooting. I believe that the 5 vibrates, followed by a black screen and a blinking led, means that the phone is pushing itself into diagnositc mode, for whatever reason. I am not sure what causes this. The only way to get out is to pull the battery out, and i believe you need to eithe be sure you're usb cable is unplugged (or is it be sure that it's plugged in..... I don't recall) Then reboot. Sorry I don't remember the exact specifics, as I've never had to do it, but I've seen it mentioned around here. If you search xHausx's posts, I know he has given instructions on how to attempt recovering from that situation a few times, but I don't usually see it successful, and people end up attempting to run an RUU, if you can keep the phone on long enough. If you do resort to running the RUU, I'd try running it from fastboot mode, which you select from the bootloader.

thanks again
k2buckley said:
I don't suspect that changing the kernel will have any affect on your situation. Sometimes a kernel can cause the phone to reboot, but your phone isn't just rebooting. I believe that the 5 vibrates, followed by a black screen and a blinking led, means that the phone is pushing itself into diagnositc mode, for whatever reason. I am not sure what causes this. The only way to get out is to pull the battery out, and i believe you need to eithe be sure you're usb cable is unplugged (or is it be sure that it's plugged in..... I don't recall) Then reboot. Sorry I don't remember the exact specifics, as I've never had to do it, but I've seen it mentioned around here. If you search xHausx's posts, I know he has given instructions on how to attempt recovering from that situation a few times, but I don't usually see it successful, and people end up attempting to run an RUU, if you can keep the phone on long enough. If you do resort to running the RUU, I'd try running it from fastboot mode, which you select from the bootloader.
Click to expand...
Click to collapse
thanks alot man i gladly appreciate it i see there is other threads going on about this some all which are somewhat the same and some that are exactly the same i am experiencing....so i will take the RUU as my last step if that does not work what else can i do....insurance claim right??? oh and i am having dificulty on choosing the right pcimg or ruu ive never had to do this before so i dont know which one to chosse out of all the ones in the thread you posted?

KaL-EL3038 said:
thanks alot man i gladly appreciate it i see there is other threads going on about this some all which are somewhat the same and some that are exactly the same i am experiencing....so i will take the RUU as my last step if that does not work what else can i do....insurance claim right??? oh and i am having dificulty on choosing the right pcimg or ruu ive never had to do this before so i dont know which one to chosse out of all the ones in the thread you posted?
Click to expand...
Click to collapse
You said you can still get to the OS for a limited amount of time right? See if you can get to menu>settings>about phone>software information. Get all the info there, (PRI, Baseband/radio, Software version (3.70? 3.30?, etc) Just record everything on that page down. Then boot to your bootloader. What's the hboot version? (2.02, 2.10, .97, .93, .76, etc etc.) Report back with that info. Most likely though, you'll need to run the most recent one (first on the page in that thread I sent you, which is 3.70 software)

k2buckley said:
You said you can still get to the OS for a limited amount of time right? See if you can get to menu>settings>about phone>software information. Get all the info there, (PRI, Baseband/radio, Software version (3.70? 3.30?, etc) Just record everything on that page down. Then boot to your bootloader. What's the hboot version? (2.02, 2.10, .97, .93, .76, etc etc.) Report back with that info. Most likely though, you'll need to run the most recent one (first on the page in that thread I sent you, which is 3.70 software)
Click to expand...
Click to collapse
yeah u see i am able to keep the phone one for a while....like example yesterday i was using it to tether to my PS3 no problem but when i open like a new app or sometimes even a phone call it reboots at first i thought it was like the batteries were over heating but now that ive seen this happen to other people i see that not the case...so back to the point here is the info
Baseband-2.15.00.11.19
kernel-2.6.32.17 -gee557fd/[email protected]#15
build- Myns TwoPointTwo rls5
Software Version-3.70.651.1
Webkit-3.1
PRI version-1.90_003
PRL version-60677
Hardware version-0003
HBOOT-0.93.0000
Radio-2.15.00.11.19
and there you go that all i need to get right?

KaL-EL3038 said:
yeah u see i am able to keep the phone one for a while....like example yesterday i was using it to tether to my PS3 no problem but when i open like a new app or sometimes even a phone call it reboots at first i thought it was like the batteries were over heating but now that ive seen this happen to other people i see that not the case...so back to the point here is the info
Baseband-2.15.00.11.19
kernel-2.6.32.17 -gee557fd/[email protected]-2#15
build- Myns TwoPointTwo rls5
Software Version-3.70.651.1
Webkit-3.1
PRI version-1.90_003
PRL version-60677
Hardware version-0003
HBOOT-0.93.0000
Radio-2.15.00.11.19
and there you go that all i need to get right?
Click to expand...
Click to collapse
Yup. That's all. Your software and radios are the latest, but your hboot isn't. I would try the newest 3.70 RUU first. If that gives you any trouble, try the 3.30 RUU, or even 3.29. Its just because your hboot is older that I'm not a hundred percent sure.
Sent from my PC36100 using XDA App

k2buckley said:
Yup. That's all. Your software and radios are the latest, but your hboot isn't. I would try the newest 3.70 RUU first. If that gives you any trouble, try the 3.30 RUU, or even 3.29. Its just because your hboot is older that I'm not a hundred percent sure.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
so do i just download the RUU and not the pcimg??? or both??

KaL-EL3038 said:
so do i just download the RUU and not the pcimg??? or both??
Click to expand...
Click to collapse
Either one you want. They are two separate methods of running the RUU. If you download the actual RUU, it's a .exe that runs from your computer, while the phone is plugged in Via USB. You need HTC Sync installed to run the RUU.
PC36IMG, is a file that you put on your sd card, and then boot to your bootloader. If the PC36IMG is on the main directory of your sd card, and it's named exactly PC36IMG, then when you boot to the bootloader, it will prompt you to update after a few seconds. Just wait for it to ask, then select volume up to say yes. That will then run the 'ruu' from your phone. Either method will acheive the exact same results. Personally, I think it's easier to use the PC36IMG, but they are both easy to do.

k2buckley said:
Either one you want. They are two separate methods of running the RUU. If you download the actual RUU, it's a .exe that runs from your computer, while the phone is plugged in Via USB. You need HTC Sync installed to run the RUU.
PC36IMG, is a file that you put on your sd card, and then boot to your bootloader. If the PC36IMG is on the main directory of your sd card, and it's named exactly PC36IMG, then when you boot to the bootloader, it was prompt you to update after a few seconds. Just wait for it to ask, then select volume up to say yes. That will then run the 'ruu' from your phone. Either method will acheive the exact same results. Personally, I think it's easier to use the PC36IMG, but they are both easy to do.
Click to expand...
Click to collapse
yeah i think i will personally use the pc36img cause i dont want to mess with HTC sync i heard its a pain in the butt!! lol and thanks man i will report back to see what happends ok!

KaL-EL3038 said:
yeah i think i will personally use the pc36img cause i dont want to mess with HTC sync i heard its a pain in the butt!! lol and thanks man i will report back to see what happends ok!
Click to expand...
Click to collapse
cool, sounds good. And just don't forget to turn it back to S on, by flashing the unrevoked s on tool, before you run the RUU(or PC36IMG). Good luck with it!

k2buckley said:
cool, sounds good. And just don't forget to turn it back to S on, by flashing the unrevoked s on tool, before you run the RUU(or PC36IMG). Good luck with it!
Click to expand...
Click to collapse
ohhhh snap thanks man luckly i came back and read this also am i suppose to unzip the pcimg on to the root of my sdcard?

KaL-EL3038 said:
ohhhh snap thanks man luckly i came back and read this also am i suppose to unzip the pcimg on to the root of my sdcard?
Click to expand...
Click to collapse
No, just leave it as is, unzipped. Boot into the bootloader, let it scan, then apply the update and reboot, you'll be all set.

KaL-EL3038 said:
ohhhh snap thanks man luckly i came back and read this also am i suppose to unzip the pcimg on to the root of my sdcard?
Click to expand...
Click to collapse
And just to be more clear, you only need to run the Unrevoked S on tool if you have any point used Unrevoked-Forever. If you are on the .76 Eng Bootloader, you don't need to run it, in which case you'd just skip right to running the RUU.
Edit: And as teh roxx said, leave the PC36IMG zipped, and on the main directory of your sd card. Named exactly PC36IMG.

k2buckley said:
And just to be more clear, you only need to run the Unrevoked S on tool if you have any point used Unrevoked-Forever. If you are on the .76 Eng Bootloader, you don't need to run it, in which case you'd just skip right to running the RUU.
Edit: And as teh roxx said, leave the PC36IMG zipped, and on the main directory of your sd card. Named exactly PC36IMG.
Click to expand...
Click to collapse
thanks so much guys i will report back to see if this help ok and i have bootloader .96 so i think i have to run S-On tool..

Aye aye cappy, someone should be around.

Darn itttt
teh roxxorz said:
Aye aye cappy, someone should be around.
Click to expand...
Click to collapse
HUUHHHH ????? lol
KaL-EL3038 said:
thanks so much guys i will report back to see if this help ok and i have bootloader .96 so i think i have to run S-On tool..
Click to expand...
Click to collapse
On another note....Here are my results guys...
well ok first thing i did was format my sd card so i wouldnt run into any problems with that....then i continued to placing the zip file of S-ON tool on to the root of the sdcard Flashed it with clockwork and after it did its handy work i rebooted on to Bootloader and confirmed S-On.....so then i place the PC136img on the root of my sd card and it scanned it and i fallowed what told of me to do....so as soon it was done it asked me to reboot!!so as i clicked up to say yes it rebooted...now here is there the fun begins...when i first rebooted it went into a boot loop of turning on to HTC EVO screen then turning off And HTC EVO screen over and over again so it was turning on and off by itself....so i decided to reflash PC136 IMG all over again cause i thought something went wrong....so it completed everything again i rebooted and this time it did an HTC EVO Screen on and off thing again .....but this time i decided to take out the battery leave it out for a little and put it back on.....and as i was putting it back on i turned it on and this screen with a phone laying down with arrows going in a circle kind of like a recycle came on and stayed on so i took of the battery...and reflashed PC136 IMG again....so then i rebooted again and The darn HTC EVO screen on and off again.....so this time i took out battery again and waited for like five minutes...put it back on and the PHONE LAYING DOWN WITH ARROWS AGAIN CAME ON and i let it sit for a while and phone came on....so i was like YEAHHHHH worked welll after fully charging phone and trying to Repeat the same process i would do to get the PHONE OFF WITH ORANGE LIGHTS FLASHING....well that did not happen.....butttttttt HERE is the new thing it does the same process i would do to make that happen i do it again .....and to my suprise phone still turns off but this time its not PHONE ORANGE LIGHTS.....ITS HTC EVO SCREEN BOOT LOOP.....so now what guys.....

KaL-EL3038 said:
HUUHHHH ????? lol
On another note....Here are my results guys...
well ok first thing i did was format my sd card so i wouldnt run into any problems with that....then i continued to placing the zip file of S-ON tool on to the root of the sdcard Flashed it with clockwork and after it did its handy work i rebooted on to Bootloader and confirmed S-On.....so then i place the PC136img on the root of my sd card and it scanned it and i fallowed what told of me to do....so as soon it was done it asked me to reboot!!so as i clicked up to say yes it rebooted...now here is there the fun begins...when i first rebooted it went into a boot loop of turning on to HTC EVO screen then turning off And HTC EVO screen over and over again so it was turning on and off by itself....so i decided to reflash PC136 IMG all over again cause i thought something went wrong....so it completed everything again i rebooted and this time it did an HTC EVO Screen on and off thing again .....but this time i decided to take out the battery leave it out for a little and put it back on.....and as i was putting it back on i turned it on and this screen with a phone laying down with arrows going in a circle kind of like a recycle came on and stayed on so i took of the battery...and reflashed PC136 IMG again....so then i rebooted again and The darn HTC EVO screen on and off again.....so this time i took out battery again and waited for like five minutes...put it back on and the PHONE LAYING DOWN WITH ARROWS AGAIN CAME ON and i let it sit for a while and phone came on....so i was like YEAHHHHH worked welll after fully charging phone and trying to Repeat the same process i would do to get the PHONE OFF WITH ORANGE LIGHTS FLASHING....well that did not happen.....butttttttt HERE is the new thing it does the same process i would do to make that happen i do it again .....and to my suprise phone still turns off but this time its not PHONE ORANGE LIGHTS.....ITS HTC EVO SCREEN BOOT LOOP.....so now what guys.....
Click to expand...
Click to collapse
When the phone coming on with the arrows comes on, you need to let that finish. That's a part of the process of running the ruu/PC36IMG. When it comes to that screen, let it sit there for a bit (could be a few minutes), and don't pull the battery unless you're positive that it's stuck there.
Also, which RUU are you trying? I forget which one you went with. Perhaps try a different one as well. You may be having trouble due to the wrong RUU. Did you try downloading a different one yet?
Also, remember that there was something wrong with you're phone to begin with. It is entirely possible that there is some sort of hardware problem with it, since it was giving you the black screen with the blinking led before. The important thing here is that you got S on. That way you can at least take it in to Sprint, and not have to worry. Just be sure that if you take it in, to take your SD card out before taking it in, so they don't see any root related stuff on the card.

[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!

Constant bootloop

My Incredible is in a bootloop. I have gone back to stock. The phone will work for a few minutes then just reboot non-stop. I did a factory reset and that did not help.
I can't keep the phone on long enough to do anything. The irony in all of this is that it started to do this 2 weeks after I became eligable for an upgrade...
Smells fishy...now I either wait for Incredible 4G or get the Rezound.
[email protected] Verizon...

Do you have a recovery on the phone still or did you get rid of it when returning to stock? I'm not sure I've heard of this before but if you post the status of your hboot that might be able to help someone help you.
and personally between the two I would go with the Incredible 4G but that's just me being loyal to HTC i guess.

Recovery is gone/does not work. I'll post the HBOOT version later, don't have the phone atm.

binaryhat said:
Recovery is gone/does not work. I'll post the HBOOT version later, don't have the phone atm.
Click to expand...
Click to collapse
Post hboot version, s-on or off, and current android version.

cmlusco said:
Post hboot version, s-on or off, and current android version.
Click to expand...
Click to collapse
Will do tomorrow...left the phone at work.

S-off
HBOOT-0.92
Radio-2.15.00.07.28
Stock Android

I know it sounds very round-about but you may need to flash CWM back on to the phone so you can flash unrevoked's s-on tool, I don't know for sure that this is what is causing the problem but you want s-on when you are in stock, especially if you plan on giving the phone to Verizon- if it has been messed with they won't want to handle it because they will say it is not their problem. (I have heard that Verizon has admitted to not checking very carefully, but it can't hurt to be careful yourself)

How can I flash CWM if I can't keep the phone on for more than a minute?

sounds like your kinda having the same problem i am having. the difference is my is s-on. i can get to hboot but when i try to go to recovery from there it comes up with a bunch of errors. and mine just bootloops at the droid eye.

that is a very valid point. It still can't hurt to try, I remember when I rooted my phone, it didn't take all that long to flash CWM.
You also might want to consider booting into safe mode to see if that keeps in on longer, I am copying and pasting these instructions from technipages.com because xda won't let me post links until they trust me more or something:
Sometimes services and apps you install on your HTC Droid Incredible can interfere with its functionality. If you’ve reached a point where the phone freezes at startup or malfunctions in a way that you can’t remove the problem, Safe Mode is the answer. Booting in Safe Mode will load only software and drivers from factory defaults. This should allow you access to remove whatever ails your smartphone.
1. Turn the device off. If the power button doesn’t do the trick, remove and replace the battery.
2. Power the device on.
3. When the logo appears, press and hold the Menu button.
4. Continue holding the Menu button until you see the home screen.
The words Safe Mode should appear in the lower left corner if you performed the steps correctly.
Click to expand...
Click to collapse
I apologize if you don't have any luck, but I am only trying to help

I'll try safe mode (should have) and see if that works.

binaryhat said:
I'll try safe mode (should have) and see if that works.
Click to expand...
Click to collapse
Does the phone shut off when your in hboot too? You need to do as sugested and flash cwm thru hboot, and then see if you can access recovery long enough to wipe everything in mounts and storrage except sd and emmc, then flash superuser, and a rom.

scoobntaz1996 said:
sounds like your kinda having the same problem i am having. the difference is my is s-on. i can get to hboot but when i try to go to recovery from there it comes up with a bunch of errors. and mine just bootloops at the droid eye.
Click to expand...
Click to collapse
Whats your hboot and android version? Have you tried an ruu?
EDIT: Nevermind i forgot i was allready talking to you in the other thread.