Develop Bugs

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.

unsuccessful root

hey guys i bought this evo off ebay for 100 bucks. the guy tried to root but failed. which made the evo a "soft brick"
S-ON so its not actually rooted its still stock
hboot-2.16.0001
radio-2.15.00.05.02
when i tried to boot normally by just pressing the power button it come to the screen saying evo 4g then it goes black and comes back to the evo 4g screen. its in a loop
i tried this guide from another forum
http://forums.androidcentral.com/ht...568-how-unbrick-your-soft-bricked-evo-4g.html
unfortuneately it did not work.
this is my first android device. but i did flash/root lots of winmo phones which is kind of a similar process.
so any ideas that could help me out to try to get this workinng again?
thanks alot

you can't root your phone yet. and since you have s-on you might want to take it in. have your tried and pull the battery and boot up?

ocnbrze said:
you can't root your phone yet. and since you have s-on you might want to take it in. have your tried and pull the battery and boot up?
Click to expand...
Click to collapse
im not necessarily looking to root just trying to get it out of the loop..i might take it in tomorrow.
how can i boot without a battery??? i doint understand

well pull the battery out to stop the bootloop then put it back in and reboot

tried that now and its not working..I guess ill just go to the sprint store tomorrow.

You'll need to flash the RUU to restore it. Do you know what he tried to get it like that? It sounds like he was able to do something even if he couldn't finish it

xHausx said:
You'll need to flash the RUU to restore it. Do you know what he tried to get it like that? It sounds like he was able to do something even if he couldn't finish it
Click to expand...
Click to collapse
no i dont know but i can ask him.. i cant ruu through the computer so i put the pc36img on the sd and tried that way multiple times and its installs everything but then doesnt boot

when i try to re flash it from the sd card everything goes fine. i can even flash to a different radio software but the when it actually tries to boot it just loops.
so u think it might be hardware?????

just run the ruu

I had insurance on mine and dropped it in the bath on purpose....they replaced it
Sent from my PC36100 using XDA App

vabeachfc3s said:
just run the ruu
Click to expand...
Click to collapse
it doesnt go past the htv evo 4g screen. so how should i connect it??? via hboot??

i kinda forgot about this i still didnt solve this problem.
does anybody have any ideas on what i should do??

afgomar said:
i kinda forgot about this i still didnt solve this problem.
does anybody have any ideas on what i should do??
Click to expand...
Click to collapse
IDK if this will help but you can check out this thread on how to root 2.3 .
http://forum.xda-developers.com/showthread.php?t=1218386
Sent from my PC36100 using XDA App

linsalata28 said:
IDK if this will help but you can check out this thread on how to root 2.3 .
http://forum.xda-developers.com/showthread.php?t=1218386
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
yeah ive already gone through that thread...the problem is i can't get past the boot loader and the computer can not recognize the device.
btw its s-on so its not rooted which makes things even harder.

afgomar said:
yeah ive already gone through that thread...the problem is i can't get past the boot loader and the computer can not recognize the device.
btw its s-on so its not rooted which makes things even harder.
Click to expand...
Click to collapse
Yeah sorry I didn't know if you saw that. I have no idea how to fix that problem sorry.
Sent from my PC36100 using XDA App

Boot into HBoot. Run an official RUU like this one: http://goo-inside.me/supersonic/ruu/RUU_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15.00.07.28_NV_1.40_release_140444_signed.exe. Then go to www.revolutionary.io and download and run the utility. Install the recovery and congratulations you're rooted. I hope this helps you.

nickelghandi said:
Boot into HBoot. Run an official RUU like this one: http://goo-inside.me/supersonic/ruu/RUU_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15.00.07.28_NV_1.40_release_140444_signed.exe. Then go to www.revolutionary.io and download and run the utility. Install the recovery and congratulations you're rooted. I hope this helps you.
Click to expand...
Click to collapse
so when i run the ruu it doesnt work because it cant recognized the phone. thats my main problem.
does you evo get recognized by the computer when its in hboot/bootloader???
I might have a bad usb port on the phone. (its not the laptop cuz its brand new)

afgomar said:
so when i run the ruu it doesnt work because it cant recognized the phone. thats my main problem.
does you evo get recognized by the computer when its in hboot/bootloader???
I might have a bad usb port on the phone. (its not the laptop cuz its brand new)
Click to expand...
Click to collapse
Try running the ruu from fastboot, it should recognize it then. Fastboot is the first option in hboot.
Sent from my Evo + MIUI using Tapatalk!

plainjane said:
Try running the ruu from fastboot, it should recognize it then. Fastboot is the first option in hboot.
Sent from my Evo + MIUI using Tapatalk!
Click to expand...
Click to collapse
okay so i booted into hboot then clicked on fastboot while i am plugged in via usb. then ran the ruu and it still does not recognize the device.

afgomar said:
okay so i booted into hboot then clicked on fastboot while i am plugged in via usb. then ran the ruu and it still does not recognize the device.
Click to expand...
Click to collapse
Actually heading out, but make sure you have the drivers installed, and I think you need htc sync installed while running the RUU; so try that.

[SOLVED] How to fix 5 Vibrate S-ON

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

[q] htc g2 not rooted semi bricked boot looping please help

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