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.
Related
ok so i flashed cynogenmod 7 today and i decided that i really wasnt that into it. I want to flash back to stock and when i did it the progress bar flashed red halfway through and the screen went to HTC black and silver with triangle with exclamation points in them. I tried getting tot he bootloader screen but when i push power and volume down button it just stays on the htc with triangles screen. Please help!
Bump. I can't help you but I feel so bad when people are desperate for help and don't get it. So here's a bump to get it noticed
Sent from my Optimus V
96camarors said:
ok so i flashed cynogenmod 7 today and i decided that i really wasnt that into it. I want to flash back to stock and when i did it the progress bar flashed red halfway through and the screen went to HTC black and silver with triangle with exclamation points in them. I tried getting tot he bootloader screen but when i push power and volume down button it just stays on the htc with triangles screen. Please help!
Click to expand...
Click to collapse
Were you running an RUU when thus happened? Was that how you were getting back to stock? How long has it been on that screen? If your sure its stuck, and is idle, I would do a battery pull, and then see if you can get to the bootloader. If you can, try running the RUU again, but put the phone in fastbood mode when you run the RUU. See if a second time gets it.
Sent from my PC36100 using XDA App
k2buckley said:
Were you running an RUU when thus happened? Was that how you were getting back to stock? How long has it been on that screen? If your sure its stuck, and is idle, I would do a battery pull, and then see if you can get to the bootloader. If you can, try running the RUU again, but put the phone in fastbood mode when you run the RUU. See if a second time gets it.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I was running ruu and it failed. i have tried several times since including battery pulls and no luck. I keep trying to get to the bootloader but its stuck at that screen. It does not show up in my computer either when i plug it in but using an ruu still works.
When trying to get to bootloader, did you push power / volume down after phone was off? If not, pull battery. Put back in and then power/volume down.
You probably already did this but it sort of sounded like you tried getting to bootloader from the screen you were stuck on.
J
Bump
Sent from my PC36100 using XDA Premium App
The error i get when ruu fails is error 110 file open error. The rom update utility cannot open the requested files or the files are damaged. the ruu cannot continue with the update. Please get a complete ruu package and try again.
96camarors said:
I was running ruu and it failed. i have tried several times since including battery pulls and no luck. I keep trying to get to the bootloader but its stuck at that screen. It does not show up in my computer either when i plug it in but using an ruu still works.
Click to expand...
Click to collapse
When you shut your Evo off, and plug it into a wall (AC) plug, do you get a charging led? If you can still run an RUU, it sounds like maybe the one you are using is corrupt, or the wrong one all together. Do you know your bootloader version, software version, and radio versions? Likely you need to download the RUU that matches (or is very close to) your current versions.
I'm on the app, but would otherwise link you to a thread. In the dev section, search for "supersonic shipped roms", thread started by Esp28
Sent from my PC36100 using XDA App
ferfy67 said:
When trying to get to bootloader, did you push power / volume down after phone was off? If not, pull battery. Put back in and then power/volume down.
You probably already did this but it sort of sounded like you tried getting to bootloader from the screen you were stuck on.
J
Bump
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
yeah i did that and nothing just stays at the screen
k2buckley said:
When you shut your Evo off, and plug it into a wall (AC) plug, do you get a charging led? If you can still run an RUU, it sounds like maybe the one you are using is corrupt, or the wrong one all together. Do you know your bootloader version, software version, and radio versions? Likely you need to download the RUU that matches (or is very close to) your current versions.
I'm on the app, but would otherwise link you to a thread. In the dev section, search for "supersonic shipped roms", thread started by Esp28
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
i am currently trying to download the 3.7 ruu but it keeps canceling itself. i do get a chargin led when plugged into wall. radio is 2.15
96camarors said:
i am currently trying to download the 3.7 ruu but it keeps canceling itself. i do get a chargin led when plugged into wall. radio is 2.15
Click to expand...
Click to collapse
Charging led is good. Find a good copy of the 3.70 RUU, make sure its a good download, and run again. When I get home ill link you to my RUU copy in my dropbox if you haven't found one yet.
Sent from my PC36100 using XDA App
k2buckley said:
Charging led is good. Find a good copy of the 3.70 RUU, make sure its a good download, and run again. When I get home ill link you to my RUU copy in my dropbox if you haven't found one yet.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
i found one that works and i have 46min to go. i found a good step-by-step fix for my problem http://androidforums.com/evo-4g-support-troubleshooting/254695-black-error-screen-when-updating-rooted-phone-supersonic-ruu.html and i am praying that it works for me. and thank you for your help so far!
96camarors said:
i found one that works and i have 46min to go. i found a good step-by-step fix for my problem http://androidforums.com/evo-4g-sup...hen-updating-rooted-phone-supersonic-ruu.html and i am praying that it works for me. and thank you for your help so far!
Click to expand...
Click to collapse
Cool, your welcome. I bet the good RUU will work. And yes, the other thread looked good. Did u run unrevoked forever? If so, did u flash the s on tool before running RUU?
Sent from my PC36100 using XDA App
k2buckley said:
Cool, your welcome. I bet the good RUU will work. And yes, the other thread looked good. Did u run unrevoked forever? If so, did u flash the s on tool before running RUU?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
i didnt flash s on tool. and that was my problem, i am new to the evo world (just got it sunday) and i had motorola before so the rooting i am used to is way different than htc haha
You get it fixed yet?
Sent from my PC36100 using Tapatalk
96camarors said:
i didnt flash s on tool. and that was my problem, i am new to the evo world (just got it sunday) and i had motorola before so the rooting i am used to is way different than htc haha
Click to expand...
Click to collapse
Yea, the rooting world between different manufacturers differs greatly, apparently. The state you're currently in, you probably have no choice but to run the RUU again. Once you get it to successfully run, and you boot up, back to stock, you'll most likely still be S-off. Now, that's not necessarily bad, unless you're going to take your evo into sprint for any reason. If you leave it S off, if you ever want to reroot, all you'd have to do is flash a PC36IMG of a custom recovery, using the bootloader. At that point, you could flash a ROM or whatever. Also, if you do want to return it to S on, once the RUU completes and you can boot, flash a PC36IMG of a recovery, using the bootloader. At that point, flash the unrevoked S on tool, using recovery. Once you confirm that S is back to ON, then run the RUU again. Then you'll be back to stock, unrooted, S on.
RileyGrant said:
You get it fixed yet?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
not fixed yet 5min left on download
k2buckley said:
Yea, the rooting world between different manufacturers differs greatly, apparently. The state you're currently in, you probably have no choice but to run the RUU again. Once you get it to successfully run, and you boot up, back to stock, you'll most likely still be S-off. Now, that's not necessarily bad, unless you're going to take your evo into sprint for any reason. If you leave it S off, if you ever want to reroot, all you'd have to do is flash a PC36IMG of a custom recovery, using the bootloader. At that point, you could flash a ROM or whatever. Also, if you do want to return it to S on, once the RUU completes and you can boot, flash a PC36IMG of a recovery, using the bootloader. At that point, flash the unrevoked S on tool, using recovery. Once you confirm that S is back to ON, then run the RUU again. Then you'll be back to stock, unrooted, S on.
Click to expand...
Click to collapse
ok thanks for the advice. ill probly go back to stock for awhile until i get used to the phone. so if i leave s off then nothing bad while happen with the ruu while im sleeping? i really need to get to sleep asap, got a full day of classes tomorrow haha.
96camarors said:
not fixed yet 5min left on download
ok thanks for the advice. ill probly go back to stock for awhile until i get used to the phone. so if i leave s off then nothing bad while happen with the ruu while im sleeping? i really need to get to sleep asap, got a full day of classes tomorrow haha.
Click to expand...
Click to collapse
I'm confused, haha. Nothing bad will happen with the RUU when you're sleeping? I think you do need some sleep brotha! Once you successfully run the RUU, and return to stock, you'll most likely still be S off, since you didn't flash the S on tool. This mean's you'll be on a stock ROM, with S off, and no recovery. Nothing bad will happen by leaving it like this, so long as you don't take it to Sprint with S off. Now, if you do just plan on staying stock for a while, you may want to return to S-on, just in case any unpredictable catastrophic events occur, you're better off having S-on, in case you need to take it back to Sprint. You can always root again rather easily. So I guess my suggestion is to flash a recovery once you're up and running, flash the S on tool, and then run the RUU again. Just to be safe. If you want to root again, you know how
Edit: ^^^^All that is providing you get the RUU to run successfully, which I think you will. You just need a good copy of the right version. If that doesn't work, don't forget you have other options. Such as flashing an RUU as a PC36IMG from the bootloader. Also, you can run an RUU with fastboot. So there is a plan B and C if that doesn't work.
k2buckley said:
I'm confused, haha. Nothing bad will happen with the RUU when you're sleeping? I think you do need some sleep brotha! Once you successfully run the RUU, and return to stock, you'll most likely still be S off, since you didn't flash the S on tool. This mean's you'll be on a stock ROM, with S off, and no recovery. Nothing bad will happen by leaving it like this, so long as you don't take it to Sprint with S off. Now, if you do just plan on staying stock for a while, you may want to return to S-on, just in case any unpredictable catastrophic events occur, you're better off having S-on, in case you need to take it back to Sprint. You can always root again rather easily. So I guess my suggestion is to flash a recovery once you're up and running, flash the S on tool, and then run the RUU again. Just to be safe. If you want to root again, you know how
Edit: ^^^^All that is providing you get the RUU to run successfully, which I think you will. You just need a good copy of the right version. If that doesn't work, don't forget you have other options. Such as flashing an RUU as a PC36IMG from the bootloader. Also, you can run an RUU with fastboot. So there is a plan B and C if that doesn't work.
Click to expand...
Click to collapse
ok thank you very much. it worked. thanks for all your help!
96camarors said:
ok thank you very much. it worked. thanks for all your help!
Click to expand...
Click to collapse
Sweet, glad to hear it worked. Take care.
Oh yea, are you S on or S off? My guess is S off, if you did use unrevoked forever before.
k2buckley said:
Sweet, glad to hear it worked. Take care.
Oh yea, are you S on or S off? My guess is S off, if you did use unrevoked forever before.
Click to expand...
Click to collapse
Yes I am currently s off
So I just rooted using the latest unrevoked, but now my phone locks up after about 30 seconds or so, then vibrates 5 times. More troubling: It cannot see an SD card, will not mount or format.
Hoping someone can help me get back to stock.
I did not take the gingerbread OTA, FWIW.
OK, well ,the obvious first question is gonna be are you s-on or s-off.
Turn your phone on while holding the power button down to see what it says at the top when Hboot starts up.
HipKat said:
OK, well ,the obvious first question is gonna be are you s-on or s-off.
Turn your phone on while holding the power button down to see what it says at the top when Hboot starts up.
Click to expand...
Click to collapse
It says S-ON
dsf3g said:
It says S-ON
Click to expand...
Click to collapse
Boot into the bootloader, then select clear storage, then try to boot up normally.
OK, so I managed to flash PC36IMG.zip. So now I'm back to stock and the EVO runs fine without rebooting. Wheeew! I was already scanning eBay for a replacement, LOL! Only issue I have now is that my Evo does not recognize the SD Card (won't let me mount, format, nothing.) I'm seeing some threads on this sort of thing, but if anyone has a quick fix I'd love o hear it. I've got a 16 GB card full of music that's just sittin' there.
Oh, now this is bad: the battery does not seem to charge after restoring... at least the charging symbol is not coming on!
UPDATE: OK, the red light is coming on now when I plug in, but battery status shows "discharging." I don't know at this point whether it's charging or not.
OK, just verified. Phone isn't charging. Down to 50%. Shutting off so I'll have enough juice to fix ti when I figure our what needs to be done. I don't have a separate battery charger, so I'm SOL if I can't get this thing working again.
Any help would be much appreciated!
http://forum.xda-developers.com/showthread.php?t=695243
sd card fix. Also, turn the phone off as you have, but leave it plugged in charged over night and see what happens for now.
Make sure you have the hboot drivers downloaded, then install, then uninstall htc sync, enable usb debugging from applications > development, then run unrevoked again.
teh roxxorz said:
http://forum.xda-developers.com/showthread.php?t=695243
sd card fix. Also, turn the phone off as you have, but leave it plugged in charged over night and see what happens for now.
Make sure you have the hboot drivers downloaded, then install, then uninstall htc sync, enable usb debugging from applications > development, then run unrevoked again.
Click to expand...
Click to collapse
Thanks, I'll give it a try this weekend. Right now I've got a spare battery charger on order with Amazon. Should be in this Friday. Don't want to mess with anything until I can start with a fully charged battery.
You're S-On. There's nothing you can, or could have messed with, unless you don't have the new update on your phone, which was going to be my next question
HipKat said:
You're S-On. There's nothing you can, or could have messed with, unless you don't have the new update on your phone, which was going to be my next question
Click to expand...
Click to collapse
I don't have the new update on my phone. It's still showing Android 2.2 and I never approved the OTA.
One suggestion that seems to work for some people is to flash a new radio. I wonder if someone could help me with this:
1) What do I need to know choose the appropriate radio to flash?
2) Do I need to be rooted to do so, because it seems I'm not.
I'm browsing eBay for cheapie Oprimus S phones... please help me not have to buy a used $100 Optimus S because I murdered by Evo :-(
Yes, you need to be rooted to flash the radios fro ma zip file.
you don't to flash form PC36IMG.zip file, and there is the choice to do it either way.
I'm curious, you said in your OP that you rooted, and the phone went into maintenance mode (The vibrates 5 times thing is maintenance Mode).
Are you sure the root took? I would do this, reinstall HTC-Sync, then install just the program, not the drivers, and try Unrevoked again, make sure it goes through the root process and the flash of clockwork recovery.
If it boots up, then you're good.
From there, I would flash Amon Ra, as it's a better recovery, and then try a ROM.
Radios is the least important thing you can flash, and I'd save that for last, and make sure you know in detail what you're doing, when it comes to radio flashing.
HipKat said:
Yes, you need to be rooted to flash the radios fro ma zip file.
you don't to flash form PC36IMG.zip file, and there is the choice to do it either way.
I'm curious, you said in your OP that you rooted, and the phone went into maintenance mode (The vibrates 5 times thing is maintenance Mode).
Are you sure the root took? I would do this, reinstall HTC-Sync, then install just the program, not the drivers, and try Unrevoked again, make sure it goes through the root process and the flash of clockwork recovery.
If it boots up, then you're good.
From there, I would flash Amon Ra, as it's a better recovery, and then try a ROM.
Radios is the least important thing you can flash, and I'd save that for last, and make sure you know in detail what you're doing, when it comes to radio flashing.
Click to expand...
Click to collapse
I can't be sure I rooted. I'm just going by what Unrevoked reported. Superuser was installed, but the phone would die before I had much time to verify that I was actually rooted.
I've never installed HTC Sync, BTW. According to the unrevoked instructions you shouldn't have it installed on your PC because it causes problems.
OK, so I got home and the phone says battery is 100% charged. So that's good. It appears to charge when turned off, at least.
Sadly, it does not recognize USB at all. The computer beeps when I plug the phone in, but the phone shows no popups or anything.
I tried running "unrevoked" again, but unrevoked just kept waiting for me to plug in the phone. I did not install HTC Sync.
The phone does not recognize micro sd cards from within Android, but I can flash signed ROMs. I did that today, flashing what I think is a newer ROM than I had before, but alas it did me no good. The phone still does not see the micro SD card or realize that I'm plugged in and charging.
The ROM I sintalled this time was the third link on this page:
http://forum.xda-developers.com/showthread.php?t=884060
It corresponds to the software version I was running before running UNREVOKED the first time.
I'm getting pretty worried here. I don't see how I'm supposed to fix this phone if I cannot communicate via USB.
Installing HTC Sync will install the drivers on your computer, which you need for unrevoked to work, but then, you need to uninstall the program (not the drivers).
Ugh, now I've discovered another problem. With this latest stock ROM I've lost bluetooth!
I'm losing hope here. My last best hope seems to be to accept the Gingerbread OTA, and if that doesn't solve the problem throw myself on the mercy of our local Sprint repair store. Anyone know what their policy is on this?
Will they repair something like this for a fee if it's not under warranty? I imagine even completely brcked Evos can be repaired with a new motherboard, right?
Should I try telling them that the OTA screwed it up? Will they be able to tell what I've done to the phone?
At this point I just want to get back to stock. No longer interested in rooting. I need a cell phone just for daily living.
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!
Thanks to Calkulin, Dougpiston, and bwthor20 for this fix. It was too late for me, but hopefully not for you. My situation was, after flashing a rom, I was suddenly S-On without recovery. DO NOT FLASH THE RUU!!!!! Just follow this guide and you'll be good:
Thanks bwthor20 for telling me about this guide:
http://forum.xda-developers.com/showthread.php?t=695243
Now, go to the incredible version of this guide, thanks to Dougpiston:
http://pvillecomp.com/?page_id=33
These guides should get you fixed!
Cheers,
dmeadows013
That sucks man very interested in how that happened though, never seen a phone reset it self to s-on before. I think you would have to ruu to get s-off again, that is if you can ruu back to froyo. What rom are you on? Hope you figure something out.
cmlusco said:
That sucks man very interested in how that happened though, never seen a phone reset it self to s-on before. I think you would have to ruu to get s-off again, that is if you can ruu back to froyo. What rom are you on? Hope you figure something out.
Click to expand...
Click to collapse
Was attempting to run my very experimental port of the Vigor RUU. Strange because it showed the splash on my last test, but after moving /system/customize to /data/syscustomize, it did this. I'll try the Froyo RUU. I should've thought of that one. Thanks!
Why not flash an old RUU?
Could someone post the Froyo or Eclair PB31IMG? I can't seem to find it...
Official froyo 2.2 PB31IMG.zip
http://dinc.does-it.net/stock_froyo/PB31IMG.zip
cmlusco said:
Official froyo 2.2 PB31IMG.zip
http://dinc.does-it.net/stock_froyo/PB31IMG.zip
Click to expand...
Click to collapse
Thanks! Your the man!
There is another thread on here where a guy had the same thing happen to him. Tried to flash a rom then the black screen and 5 vibes. He also lost s-off. I wonder whats going on.
cmlusco said:
There is another thread on here where a guy had the same thing happen to him. Tried to flash a rom then the black screen and 5 vibes. He also lost s-off. I wonder whats going on.
Click to expand...
Click to collapse
Hmmmm... That might be it. I'll try to port it again, and see if I get the same result. If I do, that's probably the problem lol
Alright, got the PB31IMG flashed. Problem is, after flashing, it just did the 5 vibe again... Back in HBOOT
dmeadows013 said:
Alright, got the PB31IMG flashed. Problem is, after flashing, it just did the 5 vibe again... Back in HBOOT
Click to expand...
Click to collapse
Very strange not sure, if you cant get an ruu to work my guess is some sort of hardware failure.
I would try an ruu exe from your pc.
cmlusco said:
Very strange not sure, if you cant get an ruu to work my guess is some sort of hardware failure.
I would try an ruu exe from your pc.
Click to expand...
Click to collapse
Yeah. I'm probably gonna just take it into the Verizon store. There is no way they'll find out I was rooted, as I am now S-ON. I'll see what they say.
Here is the fix!
This happened to me yesterday after installing MIUI. All was working, but when I tried to switch the camera to store on the SD card, it said it wasn't available. Tried to mount/unmount with no luck. Rebooted, and I had the same thing, five vibrations, then just a flashing green LED. A battery pull and either the charger or USB plugged in a PC, and it would boot to recovery. Still couldn't read the SD Card, so no restore. Lots of Googles later I found the fix...right here on XDA. Found a LOT of threads that pretty much said that there is no recovery.
Read On...
http://forum.xda-developers.com/showthread.php?t=695243
LEAVE THE USB CABLE PLUGGED IN TO YOUR PC FOR ALL OF THIS!
After the SD fix, I could use CWM to restore a known good backup, then copied the two files over to my SD Card and used a terminal app on the phone to run the commands listed in the link. A reboot, and I was back in business. S-OFF was back too. Odd...
dmeadows013 said:
Yeah. I'm probably gonna just take it into the Verizon store. There is no way they'll find out I was rooted, as I am now S-ON. I'll see what they say.
Click to expand...
Click to collapse
Worth a try, you might get lucky.
dmeadows013 said:
Yeah. I'm probably gonna just take it into the Verizon store. There is no way they'll find out I was rooted, as I am now S-ON. I'll see what they say.
Click to expand...
Click to collapse
I wouldn't. With a USB cable plugged in to the phone and PC, you can get into hboot with a battery pull and powering on while holding volume down. This doesn't seem to work every time, so unplug, remove the battery, then try again. After getting into hboot, you can go to recovery and see CWM if you have it installed.
bwthor20 said:
I wouldn't. With a USB cable plugged in to the phone and PC, you can get into hboot with a battery pull and powering on while holding volume down. This doesn't seem to work every time, so unplug, remove the battery, then try again. After getting into hboot, you can go to recovery and see CWM if you have it installed.
Click to expand...
Click to collapse
I can get into HBOOT without being plugged in, just using the normal way. Clicked recovery, booted to the splash and then the black screen and 5 vibes. Anyway, I have installed the RUU, so it would have the stock recovery anyway.
CWM Version
dmeadows013 said:
I can get into HBOOT without being plugged in, just using the normal way. Clicked recovery, booted to the splash and then the black screen and 5 vibes. Anyway, I have installed the RUU, so it would have the stock recovery anyway.
Click to expand...
Click to collapse
Try booting with it plugged in to the PC. I could boot that way, and use it, but as soon as I unplugged the USB, it would go to a black screen and 5 vibrations.
bwthor20 said:
Try booting with it plugged in to the PC. I could boot that way, and use it, but as soon as I unplugged the USB, it would go to a black screen and 5 vibrations.
Click to expand...
Click to collapse
Well that seemed to work... I plugged it in, and it booted up to the DROID Screen. Then, I unplugged, and black screen vibes. I think I had the same thing as you, but I just had the stock recovery instead because of the RUU. How did you end up fixing the plugged in problem? I'll check out the thread you posted. Thanks man, your a lifesaver.
dmeadows013 said:
Well that seemed to work... I plugged it in, and it booted up to the DROID Screen. Then, I unplugged, and black screen vibes. I think I had the same thing as you, but I just had the stock recovery instead because of the RUU. How did you end up fixing the plugged in problem? I'll check out the thread you posted. Thanks man, your a lifesaver.
Click to expand...
Click to collapse
It is the second part of the sequence in the link I posted in the previous thread. Check to see if you can mount your SD Card. If not, you will need to do the first part so you can load the two files on it used in the second part.
bwthor20 said:
It is the second part of the sequence in the link I posted in the previous thread. Check to see if you can mount your SD Card. If not, you will need to do the first part so you can load the two files on it used in the second part.
Click to expand...
Click to collapse
Alright, got the SD fixed. Not sure how I will get the USB fix, as I do not have root. Also, for some reason, unRevoked cannot find my phone. Neither will ADB
Long story short my friend gave me a T mobile HTC G2 because it didn't turn on. I opened the phone to find the part where the battery connects to the phone came off the mother board so i solder it back on put the phone back together and turned it on. It booted up normal and came to the lock screen nothing worked the touch wasn't responding so i push power button to turn screen off and then again to turn it back on and the screen worked. I tried guessing his pattern five time and it didnt work it asked me to sign in to my Google account when the screen came up the phone rebooted and it kept doing it every time i turned it on. So i looked on xda how to restore it tried it and im not sure if it restored or not but it strated boot looping. I tried the flashing the pc10img.zip from the root of the sd card it usually says something like version to new or to old or something it didn't work. My phone is not rooted and i don't think usb debugging is on. Any info you guys want just ask. What can i do? How can i fix it? Please help
I'm going to take a guess, that if the battery connection to the motherboard 'broke off', then it's possible you have other physical issues such as the ribbon cable connecting the screen/digitizer to the rest of the phone.
If it were me I would have sent the phone into HTC for hardware warranty (which you can't do now since you soldered it.).
Can you provide some specific information about the phone, can you get into the boot loader, and if so what exact information do you have there? (USB debugging would be easily turned on under system settings, if you can get into it via the screen).
kbeezie said:
I'm going to take a guess, that if the battery connection to the motherboard 'broke off', then it's possible you have other physical issues such as the ribbon cable connecting the screen/digitizer to the rest of the phone.
If it were me I would have sent the phone into HTC for hardware warranty (which you can't do now since you soldered it.).
Can you provide some specific information about the phone, can you get into the boot loader, and if so what exact information do you have there? (USB debugging would be easily turned on under system settings, if you can get into it via the screen).
Click to expand...
Click to collapse
Thanks for replying i don't think anything else is wrong with the phone all the cables were fine. To begin with warranty was already finished. "Yes", i can get into the boot loader/H boot. I can turn on usb debugging because the phone doesn't boot all the way in to android. When you say information what exactly are you looking for?
helstonrampersad said:
Thanks for replying i don't think anything else is wrong with the phone all the cables were fine. To begin with warranty was already finished. "Yes", i can get into the boot loader/H boot. I can turn on usb debugging because the phone doesn't boot all the way in to android. When you say information what exactly are you looking for?
Click to expand...
Click to collapse
Mainly the info that shows up on hboot, and which recovery you have (or 'had') so that might be able to advise some additional steps.
helstonrampersad said:
Long story short my friend gave me a T mobile HTC G2 because it didn't turn on. I opened the phone to find the part where the battery connects to the phone came off the mother board so i solder it back on put the phone back together and turned it on. It booted up normal and came to the lock screen nothing worked the touch wasn't responding so i push power button to turn screen off and then again to turn it back on and the screen worked. I tried guessing his pattern five time and it didnt work it asked me to sign in to my Google account when the screen came up the phone rebooted and it kept doing it every time i turned it on. So i looked on xda how to restore it tried it and im not sure if it restored or not but it strated boot looping. I tried the flashing the pc10img.zip from the root of the sd card it usually says something like version to new or to old or something it didn't work. My phone is not rooted and i don't think usb debugging is on. Any info you guys want just ask. What can i do? How can i fix it? Please help
Click to expand...
Click to collapse
when you first had the phone it won't boot right? but when you tried fixing the battery connection thingy (sorry I don't know whats it called )
it booted and ran again?
have you tried doing a factory reset?
Power button+volume rocker down (volume down button) to boot into bootloader mode then do a factory reset maybe that would work ?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
OR
or sending the phone to HTC would help bud but you have to pay them for that if they get to fix it you got yourself a new toy!
kbeezie said:
Mainly the info that shows up on hboot, and which recovery you have (or 'had') so that might be able to advise some additional steps.
Click to expand...
Click to collapse
This is the boot loader screen that i see
VISION PVT SHIP S-ON
HBOOT-0.82.0000
MICROP-26.13.04.19_M
eMMC-boot
Apr 13 211, 14:51:54
Im pretty sure the phone was never rootded before
The Android Manual said:
when you first had the phone it won't boot right? but when you tried fixing the battery connection thingy (sorry I don't know whats it called )
it booted and ran again?
have you tried doing a factory reset?
Power button+volume rocker down (volume down button) to boot into bootloader mode then do a factory reset maybe that would work ?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
OR
or sending the phone to HTC would help bud but you have to pay them for that if they get to fix it you got yourself a new toy!
Click to expand...
Click to collapse
Its ok im not certain of what its called either but just to be sure its the part where the battery touches and it has metal prongs like. As for trying to restore it, i already tried didnt work it boot loops when i try that.
I don;t know what to do
helstonrampersad said:
Its ok im not certain of what its called either but just to be sure its the part where the battery touches and it has metal prongs like. As for trying to restore it, i already tried didnt work it boot loops when i try that.
Click to expand...
Click to collapse
ryin
sorry bro I'm no dev so I don't know that much when you were tryin to flash the "stock rom" did you flash the one for the G2 or the Desire Z?
The Android Manual said:
ryin
sorry bro I'm no dev so I don't know that much when you were tryin to flash the "stock rom" did you flash the one for the G2 or the Desire Z?
Click to expand...
Click to collapse
I still appreciate your help bro and i was trying to flash the stock rom for the g2, i made sure of it.
helstonrampersad said:
I still appreciate your help bro and i was trying to flash the stock rom for the g2, i made sure of it.
Click to expand...
Click to collapse
Would probably have to stick to the original Stock RUU update since you're S-ON (would need S-OFF for any kind of custom recovery, kernel, unsigned packages, etc), so would have to use a signed full package from T-Mobile, I don't know much bout that because I usually have my phones rooted and away from stock as fast as I can.
What stock rom did you find before? links?
kbeezie said:
Would probably have to stick to the original Stock RUU update since you're S-ON (would need S-OFF for any kind of custom recovery, kernel, unsigned packages, etc), so would have to use a signed full package from T-Mobile, I don't know much bout that because I usually have my phones rooted and away from stock as fast as I can.
What stock rom did you find before? links?
Click to expand...
Click to collapse
http://shipped-roms.com/index.php?category=android&model=Vision
Thats is the above link i used and i used all the ones that start with "PC10" I rename them to PC10IMG.zip so the phone can recognize it and it did. The only problem is that after it tries to install is say something along the lines of version is older or newer since i tried multiple packages. One package was going through the process and after that it didn't do anything, it didnt say failed or reboot or anything like that. Ive been trying to fix this for like a week and a half now. Ive even flashed custom PC10IMG.zip to see if it could help but nothing the furthest ive gotten is the phone boots for like 2 seconds the screen is blurry and the shuts off and there is an orange light in top right that wasn't lighting up before. Here are the links for the custom packages
http://forum.xda-developers.com/showpost.php?p=10583834&postcount=33
http://forum.xda-developers.com/showpost.php?p=10966727&postcount=63
Cant thank you enough for helping me this is really frustrating
kbeezie said:
Would probably have to stick to the original Stock RUU update since you're S-ON (would need S-OFF for any kind of custom recovery, kernel, unsigned packages, etc), so would have to use a signed full package from T-Mobile, I don't know much bout that because I usually have my phones rooted and away from stock as fast as I can.
What stock rom did you find before? links?
Click to expand...
Click to collapse
If what i explained above is not what you were referring to then let me know your way
helstonrampersad said:
If what i explained above is not what you were referring to then let me know your way
Click to expand...
Click to collapse
You would have to much it to your exact carrier/phone, Just flashing whatever you get your hands on can be very very risky.
For example for me being on T-Mobile with a T-Mobile branded G2, I would grab PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from http://forum.xda-developers.com/showthread.php?t=971109
(noting the *.15 is the original radio my device was shipped with, though I've upgraded to the newer *.19)
I of course have no intention to returning to complete stock, but it's usually the only course of action for most people stuck with S-ON (and then would look into exploiting/unlocking/rooting again from there).
kbeezie said:
You would have to much it to your exact carrier/phone, Just flashing whatever you get your hands on can be very very risky.
For example for me being on T-Mobile with a T-Mobile branded G2, I would grab PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from http://forum.xda-developers.com/showthread.php?t=971109
(noting the *.15 is the original radio my device was shipped with, though I've upgraded to the newer *.19)
I of course have no intention to returning to complete stock, but it's usually the only course of action for most people stuck with S-ON (and then would look into exploiting/unlocking/rooting again from there).
Click to expand...
Click to collapse
I know it can be risky but im desperate for a fix. Ill try the package you linked. I download it and rename it to PC10IMG.zip? Ill get back after im done if you have any other suggestion please let me know.
kbeezie said:
You would have to much it to your exact carrier/phone, Just flashing whatever you get your hands on can be very very risky.
For example for me being on T-Mobile with a T-Mobile branded G2, I would grab PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from http://forum.xda-developers.com/showthread.php?t=971109
(noting the *.15 is the original radio my device was shipped with, though I've upgraded to the newer *.19)
I of course have no intention to returning to complete stock, but it's usually the only course of action for most people stuck with S-ON (and then would look into exploiting/unlocking/rooting again from there).
Click to expand...
Click to collapse
Im confused on which one to flash I have a T-Mobile HTC G2 which one will i flash?
choose the latest one for the g2, reading your thread I feel you will have little luck with this. try logging onto freenode #g2root, you'll get real time help here
Sent from my HTC Vision using xda premium
demkantor said:
choose the latest one for the g2, reading your thread I feel you will have little luck with this. try logging onto freenode #g2root, you'll get real time help here
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I am new to XDA how can i do that?
helstonrampersad said:
I am new to XDA how can i do that?
Click to expand...
Click to collapse
I'm new so I can't post links, but copy and paste this url: http://webchat.freenode.net/?channels=g2root
EDIT - Oh, I can post links.
eboy_gb said:
I'm new so I can't post links, but copy and paste this url: http://webchat.freenode.net/?channels=g2root
EDIT - Oh, I can post links.
Click to expand...
Click to collapse
Though ideally using an actual IRC client will work much nicer than a web chat one.
Same problem, but desire z S-ON
Hey guys.
I have the same problem with the boot loop /semi brick. Expect I never had any problem before, with the phone. I have tried taking out the sd card, starting it agian. I have tried without simcard. I have tried to flash the ROM with RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed
via Hboot Fastboot USB PLUG mode (which was the only mode the aplication was progressing in until it want to restart the phone in bootloader), but the phone frezzes and the aplication on the computer just keep working, without progress.
The factory reset just frezzes the phone.
The only thing reali seem to not frezze the phone is the revocery option. Here the phone react with restart showing a image of a phone with two green arrows bent around, over the phone. then it turns off the display and vibrate 4-5 times, og stays turn off not reacting to anything other then taking out the battery and you can start the phone once again.
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-26.10.04.19_M
eMMC-boot
Apr 11 2011, 23:36:27
Have no idea but the version of android. I know that usb debugging is NOT on Any hjelp is a big help. I'm a noob, And I have been searching for 3 days for a solution, so I just hope you can help my, otherwise it is going for a repair at the place I bought it.
Thanks