Develop Bugs

[Q] HTC EVO SHUTS OFF AND LIGHT BLINKs

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Aye aye cappy, someone should be around.

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

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

[Q] i can't get my phone unbricked

hey
i am trying the whole day to fix my phone. but i guess it is almost imposible :/
i can't get in recovery mode (nothing happens) and can't turn in on (only vibrates once, black screen)
i have been told to download to download
OTA_Bravo_Froyo_HTC_WWE_2.29.405.5-2.29.405.2_releasedauhl6jhok5cmdm6.zip
and rename it to PB99IMG.zip and put it on sd, which i did, but how can i flash it if my recovery mod can't start up?
please help?
ANY suggestions???? please heeelp! :/

It would be helpful it you told us what you did to get your phone into this state.
Can you get into fastboot? (power on while pressing back-button)

Tillus said:
It would be helpful it you told us what you did to get your phone into this state.
Click to expand...
Click to collapse
i installed
RUU_Bravo_HTC_Europe_1.15.405.1_Radio_32.30.00.28U _4.05.00.11_release_121684.exe
via fastbooth
do you know what to do... please say yes

Tillus said:
It would be helpful it you told us what you did to get your phone into this state.
Can you get into fastboot? (power on while pressing back-button)
Click to expand...
Click to collapse
no i can't get into fast boot... ://

I suggest you read the notice from jcase... I'm guessing you were runiing gb?
Sent from my ADR6400L using XDA Premium App

you ruu was too old - this version doesn't have the required drivers for SLCD.
That means, you phone probably does work, but the screen is black.
I don't know how to solve this (probably by flashing the newer RUU, Version 2.29....) exactly, but hopefully this gives you a clue where to look for a fix.
There were many people experiencing this after Froyo was available. They did the ota-update, then noticed, that it wasn't possible to root with the new bootloader (Version 0.93ish) at that time, which was installed along with the froyo-ota, so they tried to downgrade back to 2.1 and ended up where you are. (bootoader .80 instead of .83ish).

Richpopski123 said:
I suggest you read the notice from jcase... I'm guessing you were runiing gb?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
jcase??
i had this rom
http://forum.xda-developers.com/showthread.php?t=1040121
which didn't work and because of it i couldn't restore any of my previous roms. that is why i had to flash a rom from my computer fastbooth
have u any suggestions what should i do?

Tillus said:
you ruu was too old - this version doesn't have the required drivers for SLCD.
That means, you phone probably does work, but the screen is black.
I don't know how to solve this (probably by flashing the newer RUU, Version 2.21....) exactly, but hopefully this gives you a clue where to look for a fix.
There where many people experiencing this after Froyo was available. They did the ota-update, then noticed, that it wasn't possible to root with the new bootloader (Version 0.93ish) at that time, which was installed along with the froyo-ota, so they tried to downgrade back to 2.1 and ended up where you are. (bootoader .80 instead of .83ish).
Click to expand...
Click to collapse
yes... that makes sense. but does really no one have any clue what to do?? i worked the whole summer for this phone and now is gone

http://forum.xda-developers.com/showthread.php?t=748498
Probably the easiest and safest way ist to boot into fastboot although you don't see it and flash the newsest ruu,
so:
1) make sure, phone is off (i.e. pull battery and put back in)
2) push and hold "back" and hit power.
3) wait 30 seconds or so, to be on the safe side
4) connect phone to pc via usb
5) run RUU on PC, version 2.29.405... (RUU, not OTA!)
And make sure to have some juice in your battery

Here you can get the RUU:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
Its on >>Shipped Roms<< , 7th from top.
btw. am I assuming correctly that your phone is unbranded?
btw2: Do it all on your own risk. I'm trying to help, but I dont want to be held resposible, if something goes wrong, so maybe wait for someone else to confirm

Tillus said:
Here you can get the RUU:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
Its on >>Shipped Roms<< , 7th from top.
btw. am I assuming correctly that your phone is unbranded?
btw2: Do it all on your own risk. I'm trying to help, but I dont want to be held resposible, if something goes wrong, so maybe wait for someone else to confirm
Click to expand...
Click to collapse
how do i know that?
can u please stick with me... i will try to do that now
i apriciate your help... i think that nothink worse can be done to my phone, so i will try

did you see any provider logo during startup? Or any preinstalled apps or bookmarks which point into a provider's direction? Where did you buy it? And did you need a goldcard for rooting?
if you answer is no on every question, you're probably not branded.
Did you write down the version number before you did anything to your phone (when you have a .405. in your version number, your phone is definitely not branded).
Edit: but I really recommend to read the linked thread. My device is unbranded amoled so I never did any of this myself (apart from running a RUU), so always think twice before following my steps

Tillus said:
did you see any provider logo during startup? Or any preinstalled apps or bookmarks which point into a provider's direction? Where did you buy it? And did you need a goldcard for rooting?
if you answer is no on every question, you're probably not branded.
Did you write down the version number before you did anything to your phone (when you have a .405. in your version number, your phone is definitely not branded).
Edit: but I really recommend to read the linked thread. My device is unbranded amoled so I never did any of this myself (apart from running a RUU), so always think twice before following my steps
Click to expand...
Click to collapse
i hope its not branded
do i need to click od hold power button?

like you do, when you power on. The important part is to hold "back" while powering on

Tillus said:
like you do, when you power on. The important part is to hold "back" while powering on
Click to expand...
Click to collapse
do i have to hold down like 30 sec? no right?
i think this won't work
if i go to the sotre and give the device back... what would be a good excuse for phone not working?

jann32 said:
do i have to hold down like 30 sec? no right?
Click to expand...
Click to collapse
no. You have booted into recovery before, didn't you? Now you do the same but use "back" instead of vol- , because you want to boot into fastboot.
All I wanted to say with this 30 seconds is to give it some time to boot into fastboot, thats all. Press and hold "back", press "power", release power, wait 3 seconds, release "back", wait 10 seconds and plug in usb, start ruu.
Thats all I wanted to say with my previous post. Sry, if it was confusing

Tillus said:
no. You have booted into recovery before, didn't you? Now you do the same but use "back" instead of vol- , because you want to boot into fastboot.
All I wanted to say with this 30 seconds is to give it some time to boot into fastboot, thats all.
Click to expand...
Click to collapse
will try again
will the phone vibrate?
YES YES YES its upadatinjg.... hope this works
...my screen is back... but hopefully it finishes correctly... and doesn't go black again
what will happen if the phone is branded?
can i unbrand it?posebly not? cause its bricked ight? :/

no.
10charrrrr
If it is branded, you get a cid-error, so ruu wont finish. But your phone probably isn't branded, otherwise you would have come across problems during flashing custom roms or/or radios (-->goldcard). And because this doesn't seem to be the case, your device is not branded.
When the RUU is done, you phone is completely back to stock and you can do whatever you like to it...

Tillus said:
no.
10charrrrr
Click to expand...
Click to collapse
my phone works!!
i can not tell u how greatfull i am
THANK U

thank u for sticking with me again

Desire un-responsive - Please Help

I've seen a couple of threads such as this with no real solution.
I've been happily using my Desire for months without changing roms or whatever (CM7 and s-off) until last night I opened my Dolphin browser and before it loaded the homepage it froze, totally un-responsive. I took the battery out, and to my horror, it was still totally un-responsive. Wouldn't respond to pressing the power button, pressing volume down+power, charger, or usb.
The battery at the time was about 50%, I've had the battery in and out about 100 times now, trying things like leaving the battery out and then trying again, keeping it on 'charge' for a while and trying to get it booted, with no response at all.
This was until an hour ago, I hopefully tried to boot the phone after the battery, sim and sd card had been out for a while and I got a vibration, and then it hung on the flash screen. I had to remove the battery, then tried to boot again with no response, so I left it a while again, put the battery in and got to the bootloader, thought I'd get into recovery and try a nandroid or something, only when I selected recovery it hung on the slash screen again.
Does anyone have any ideas what this is, or how this could be fixed? Damn I hate not being able to use my previously awesome phone!
I apologise for the long post, I'm just trying to give a good explanation of things. I just couldn't see the problem being my battery, only the day before the problem I was telling my friend how great the battery life on my phone is, and that he should give rooting a go and use CM7, this probably hasn't swayed his decision to root his phone.

stevoh84 said:
I've seen a couple of threads such as this with no real solution.
I've been happily using my Desire for months without changing roms or whatever (CM7 and s-off) until last night I opened my Dolphin browser and before it loaded the homepage it froze, totally un-responsive. I took the battery out, and to my horror, it was still totally un-responsive. Wouldn't respond to pressing the power button, pressing volume down+power, charger, or usb.
The battery at the time was about 50%, I've had the battery in and out about 100 times now, trying things like leaving the battery out and then trying again, keeping it on 'charge' for a while and trying to get it booted, with no response at all.
This was until an hour ago, I hopefully tried to boot the phone after the battery, sim and sd card had been out for a while and I got a vibration, and then it hung on the flash screen. I had to remove the battery, then tried to boot again with no response, so I left it a while again, put the battery in and got to the bootloader, thought I'd get into recovery and try a nandroid or something, only when I selected recovery it hung on the slash screen again.
Does anyone have any ideas what this is, or how this could be fixed? Damn I hate not being able to use my previously awesome phone!
I apologise for the long post, I'm just trying to give a good explanation of things. I just couldn't see the problem being my battery, only the day before the problem I was telling my friend how great the battery life on my phone is, and that he should give rooting a go and use CM7, this probably hasn't swayed his decision to root his phone.
Click to expand...
Click to collapse
did you try rebooting it without sdcard?

If you manage to get it running , try to flash a shipped ROM - it should unroot you and fix any software problems . Try taking it back to your carrier as that sounds more like a hardware problem.

you are stuck on HTC screen are you not? Then this is the exact same situation is it not?
bortak's Troubleshooting Guide said:
S-ON
"I'm S-ON, I can't boot recovery, and my phone doesn't boot "
This is a bit of a worse situation, as you cannot flash system critical parts such as the recovery image and just restore a backup. This unfortunately means that you will lose all of your data when you attempt to fix the phone.
[STEP1]- Make sure that you have a goldcard. If not, create one from the tutorial.
[STEP2]- Battery pull. Hold the BACK button and the POWER button to boot into FASTBOOT mode.
[STEP3]- Download the latest WWE RUU from here
[STEP4]- Run the RUU and wait for completion WARNING: DO NOT, BY ANY CIRCUMSTANCES INTERRUPT THE PROCESS - THIS WILL MORE THAN LIKELY END UP WITH A BRICKED PHONE - NOT EVEN IF GOD HIMSELF TELLS YOU TO DO SO, OR IF THE US PRESIDENT THREATENS YOU WITH THERMO-NUCLEAR WAR
[STEP5]- Once the phone is booted, you are now returned completely to stock. You will need to re-root again, and I'd recommend S-OFF
Click to expand...
Click to collapse
P.S. Remember to read disclaimer on the thread.

kmaq said:
did you try rebooting it without sdcard?
Click to expand...
Click to collapse
I have tried booting without sdcard with no luck.

Walter1115 said:
If you manage to get it running , try to flash a shipped ROM - it should unroot you and fix any software problems . Try taking it back to your carrier as that sounds more like a hardware problem.
Click to expand...
Click to collapse
I would love to try that, only I can't boot the phone at all, not even into recovery.
bortak said:
you are stuck on HTC screen are you not? Then this is the exact same situation is it not?
P.S. Remember to read disclaimer on the thread.
Click to expand...
Click to collapse
I've changed the HTC screen to a Google one, but yes, formally the HTC screen.
I will try and get to the bootloader/fastbootagain, only I have not been able to get to that today. I'm going to download an RUU, and try and flash it, although I'm not sure how if I can't get into recovery? Any help there?

stevoh84 said:
I would love to try that, only I can't boot the phone at all, not even into recovery.
I've changed the HTC screen to a Google one, but yes, formally the HTC screen.
I will try and get to the bootloader/fastbootagain, only I have not been able to get to that today. I'm going to download an RUU, and try and flash it, although I'm not sure how if I can't get into recovery? Any help there?
Click to expand...
Click to collapse
[STEP2]- Battery pull. Hold the BACK button and the POWER button to boot into FASTBOOT mode.
Click to expand...
Click to collapse
you don't need recovery

bortak said:
you don't need recovery
Click to expand...
Click to collapse
Made a noob error there and didn't have the udb plugged in. Got fastboot up, and downloading an RUU, will let you know how I get on, thanks for the help.
Would you advise, running my previous nandroid, once I get up and running again?

stevoh84 said:
Made a noob error there and didn't have the udb plugged in. Got fastboot up, and downloading an RUU, will let you know how I get on, thanks for the help.
Would you advise, running my previous nandroid, once I get up and running again?
Click to expand...
Click to collapse
up to you, doesn't make a difference

Thanks for the help, unfortunately when I got the RUU downloaded and the bootloader downgrader I now can't get the phone into fastboot! Rather gutted, as I could get it there the other day, now I may have to accept defeat!

What happens when you try to get to fastboot mode? How do you do it? Try to boot into hboot, then press power button and you should be in fastboot mode.

stevoh84 said:
Thanks for the help, unfortunately when I got the RUU downloaded and the bootloader downgrader I now can't get the phone into fastboot! Rather gutted, as I could get it there the other day, now I may have to accept defeat!
Click to expand...
Click to collapse
NEVER accept defeat with Android. Try my guide for help.

MatDrOiD said:
What happens when you try to get to fastboot mode? How do you do it? Try to boot into hboot, then press power button and you should be in fastboot mode.
Click to expand...
Click to collapse
I can't get into any sort of boot mode, I've tried leaving it for days and trying the button sequences, I've tried having it plugged in for a day, and then trying, with no luck!
bortak said:
NEVER accept defeat with Android. Try my guide for help.
Click to expand...
Click to collapse
I will have a look, I will try anything really! just need some more ideas....

bortak said:
NEVER accept defeat with Android. Try my guide for help.
Click to expand...
Click to collapse
I may have to accept defeat, but I don't think I will be blaming Android, more than likely a drop of the phone in the past that has taken it's toll or something.
Sadly nothing in the contents of your quite excellent guide jumped out at me as relating to my problem.
But, thanks for helping and your advice.

stevoh84 said:
I may have to accept defeat, but I don't think I will be blaming Android, more than likely a drop of the phone in the past that has taken it's toll or something.
Sadly nothing in the contents of your quite excellent guide jumped out at me as relating to my problem.
But, thanks for helping and your advice.
Click to expand...
Click to collapse
Ahh well that's a shame, get HTC to fix it for you

bortak said:
Ahh well that's a shame, get HTC to fix it for you
Click to expand...
Click to collapse
I have been onto them. The response from HTC was amazing, after detailing in an email my phone is dead, won't respond and won't turn on.
I was told, 'while the phone is on, remove the battery and sim and perform a soft reset, if this fails, perform a factory reset, through settings'
I replied asking them how much it will be for them to fix it, they haven't replied! Maybe they don't do weekend!
So if I send it off to them, are they going to frown upon me for fiddling with the phone and rooting etc?

[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

[Q] HTC Desire Bricked/Dead

Hey all,
I have a HTC Desire (PB99200) which won't switch on, recognise a charger/ connection to a PC or enter recovery etc. This was failed update, think I used the wrong RRU as I didn't know about the different versions SLCD/AMOLED.
So as far as I know the device is dead in the water, what I want to know is can it be salvaged?
I'm basically a noob but any help would be greatful

bortak's troubleshooting guide stickied to the top of Q&A, point [5]
If that RUU doesn't work, I recommend find and flash the 2.3.3 GB RUU from shipped ROMs

Thanks for your reply but point 5 doesn't open as page cannot be displayed.
I'm also not sure if u have read my post but it did say it was not being detected by my PC or anything else which would make reflashing stock rom impossible

robbiejuk08 said:
Thanks for your reply but point 5 doesn't open as page cannot be displayed.
I'm also not sure if u have read my post but it did say it was not being detected by my PC or anything else which would make reflashing stock rom impossible
Click to expand...
Click to collapse
Mite sound like a stupid question, but did u try pulling battery out for a min then put back in then try getting into bootloader(volume down + power)

jmcclue said:
Mite sound like a stupid question, but did u try pulling battery out for a min then put back in then try getting into bootloader(volume down + power)
Click to expand...
Click to collapse
Did this and still nothing, even the RRU software can't see it

robbiejuk08 said:
Did this and still nothing, even the RRU software can't see it
Click to expand...
Click to collapse
The only options i can think of is a phone repair shop that has jtag, maybe they can save it but ud probably get a new motherboard off ebay for bout 15 quid which would be cheaper.

jmcclue said:
The only options i can think of is a phone repair shop that has jtag, maybe they can save it but ud probably get a new motherboard off ebay for bout 15 quid which would be cheaper.
Click to expand...
Click to collapse
I might be tempted to do just that, its a shame cos I know the hardware is fine.
Not sure what the price would be to take it to a repair shop here in the UK. Thanks anyway

robbiejuk08 said:
I might be tempted to do just that, its a shame cos I know the hardware is fine.
Not sure what the price would be to take it to a repair shop here in the UK. Thanks anyway
Click to expand...
Click to collapse
Sorry I read your post too quickly
So nothing comes up on screen at all when you try to get to bootloader?
I'm trying to remember whether bootloader is actually 'there', but just not visible if you flashed an SLCD RUU on an AMOLED desire or vice versa.
If it's actually there, then it may be possible to flash the RUU via PB99IMG.zip method, not tried it this way blind but worth a shot before you take it for repair.
- Try the 2.3.3 RUU from here (thanks to @jmcclue)
- Put the zip as it is on the root of the sdcard (not inside any folder), then attempt to boot to bootloader (vol down + power)
- Wait at least 30 seconds - 1 minute for it to scan and load the file, then press volume up to accept the RUU.
- Wait for it to flash, pray that it works!
Also have a look here, you're following this procedure without the screen basically.

Reread my original post in full

robbiejuk08 said:
Reread my original post in full
Click to expand...
Click to collapse
I have [emoji6]
It still comes down to flashing wrong RUU.
Was the device working beforehand ie charging?
Flashing the ruu should not break the usb port so i believe it's still charging even though doesn't look like it.
The software should still turn on, just not the screen.
Therefore the above method has a chance of working as long as you have a card reader to copy the PB99IMG.zip to the root of the sdcard. The video explains what it should look like. Plug it in to ac charger after booting to bootloader to ensure it doesn't die while flashing
Anyway no harm in giving it a go. Nothing to lose by trying it!

eddiehk6 said:
I have [emoji6]
It still comes down to flashing wrong RUU.
Was the device working beforehand ie charging?
Flashing the ruu should not break the usb port so i believe it's still charging even though doesn't look like it.
The software should still turn on, just not the screen.
Therefore the above method has a chance of working as long as you have a card reader to copy the PB99IMG.zip to the root of the sdcard. The video explains what it should look like. Plug it in to ac charger after booting to bootloader to ensure it doesn't die while flashing
Anyway no harm in giving it a go. Nothing to lose by trying it!
Click to expand...
Click to collapse
The phone was working/charging fine before I screwed up the RUU. I am following the instructions you have me and the YouTube video as well but there is no way of knowing if this will work or what its even doing if anything. all I can do it wait through a process I am unsure is working
Since the problem started, it doesn't charge, switch on, respond to PC connection nothing.

robbiejuk08 said:
The phone was working/charging fine before I screwed up the RUU. I am following the instructions you have me and the YouTube video as well but there is no way of knowing if this will work or what its even doing if anything. all I can do it wait through a process I am unsure is working
Since the problem started, it doesn't charge, switch on, respond to PC connection nothing.
Click to expand...
Click to collapse
So if it was working fine before, I doubt the RUU has broken the charging capability.
The only way I guess is to try the PB99IMG.zip watching the video at the same time plus waiting a few seconds longer just in case. Think you have to press volume up or power at the end to reboot can't remember, or battery pull and hope it turns on afterwards.
No guarantee it will work, though I've seen many people in these forums recover 'black screen after ruu' issue. Still worth exhausting this method before repair