Related
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.
This is going to sound really crazy because im in panic mode right now! Let me start by telling you guys i never do dumb things like this but it happened. Im in the kitchen and im putting a bag of kettle corn in the microwave, at the same time my phone is in my hand. I had multiple people talking to me at the same time so i really wasnt focusing on anything atm. I downloaded the latest radio(from the leak) img to see what all the fuss was about and thought maybe id give it a run to test out signal/battery life. While im in the kitchen with my phone in my hand and grabbing my hot popcorn out the microwave, as im flashing the PC36IMG in hboot the bag was hot and i dropped my phone on the floor. I know this sounds dumb but it happened. Here comes the sad part; i keep my phone naked and only wear a screen protector so it hit the ground and battery and back came apart. Ive NEVER dropped my phone before (ever) and its not damaged but just a nick at the top. Ok this is getting long i know but im very frustrated so heres the icing on the cake; the battery popped out while i was updating the radio and now its stuck on the splash screen. Cant get to recovery now or my rom. I know this was very careless and i and usually dont ask for help but im stuck. I tried almost everything i can think of; try updating radio again( didnt work). Im basically stuck with a brick and it still says s-off so i cant take to sprint. What should i do guys?
I got it this past xmas, its 0004, and has 2.10 bootloader. Thanks in advance
Sorry bro, sad story. Hope you get it up and running
Sent from my PC36100 using XDA Premium App
Oh my boy Dirk........ Damn son! Have you tried to put amon back on there yet? That sucks man. I've heard that's the only real way to brick is if you pull the battery while flashing a radio
Sent from "The EVO" using XDA Premium
jayharper08 said:
Oh my boy Dirk........ Damn son! Have you tried to put amon back on there yet? That sucks man. I've heard that's the only real way to brick is if you pull the battery while flashing a radio
Sent from "The EVO" using XDA Premium
Click to expand...
Click to collapse
Dude im heatbroken right now, my luck is terrible lately. My 1 year old 46 inch tv just went out the other day with no sign of life. Glad i had best buy blk tie they replaced it but still ive been getting crapped on these past 2 weeks.
dirkyd3rk said:
Dude im heatbroken right now, my luck is terrible lately. My 1 year old 46 inch tv just went out the other day with no sign of life. Glad i had best buy blk tie they replaced it but still ive been getting crapped on these past 2 weeks.
Click to expand...
Click to collapse
Yea I remember you saying that the other day. Be careful man, they say it cones in 3's :/ If it still says s-off I would get that RA recovery img file and see if it will recover, or the clockwork, whichever you had.
Sent from "The EVO" using XDA Premium
jayharper08 said:
Yea I remember you saying that the other day. Be careful man, they say it cones in 3's :/ If it still says s-off I would get that RA recovery img file and see if it will recover, or the clockwork, whichever you had.
Edit: Let me know if you need it and ill kick Wifey off the computer and post it.
Sent from "The EVO" using XDA Premium
Click to expand...
Click to collapse
Sorry. I qouted myself instead of editing, lol.
Sent from "The EVO" using XDA Premium
jayharper08 said:
Sorry. I qouted myself instead of editing, lol.
Sent from "The EVO" using XDA Premium
Click to expand...
Click to collapse
thanks bro nice idea, i was using the amon ra 2.3 so ill see if the hboot version will work i guess.
can you gedt to the bootloader? (hold volume down and power will phone is booting)
is so, do so, then try to run the ruu from here,
http://forum.xda-developers.com/showthread.php?t=836728
DomSim said:
can you gedt to the bootloader? (hold volume down and power will phone is booting)
is so, do so, then try to run the ruu from here,
http://forum.xda-developers.com/showthread.php?t=836728
Click to expand...
Click to collapse
yeah the only place it will go is bootloader. Since its a 0004 i dont think my fastboot works if im not mistaken right? How would i run the ruu in bootloader, hboot usb, or fastboot? I have the 370.1 ruu already on my comp. Right now im downloading the PC36IMG version of the 3.70 so i can see if it will flash in bootloader. Ive tried to update the recovery again but it wont seem to read the update.zips(ive even removed the .zip part also). I have 3 micro sds right in front of me and every time i take them out the phone and put them in my micro slot on my lappy it keeps asking me to format them as if the phone is corrupting them 0_o FML
Wish I can help man! Good luck on that man I know it'll boot soon
Sent from my PC36100 using XDA App
dirkyd3rk said:
yeah the only place it will go is bootloader. Since its a 0004 i dont think my fastboot works if im not mistaken right? How would i run the ruu in bootloader, hboot usb, or fastboot? I have the 370.1 ruu already on my comp. Right now im downloading the PC36IMG version of the 3.70 so i can see if it will flash in bootloader. Ive tried to update the recovery again but it wont seem to read the update.zips(ive even removed the .zip part also). I have 3 micro sds right in front of me and every time i take them out the phone and put them in my micro slot on my lappy it keeps asking me to format them as if the phone is corrupting them 0_o FML
Click to expand...
Click to collapse
If you can get to the bootloader, I highly doubt your phone is bricked. Hopefully, you have the contents of your SD card backed up. I suggest, re-doing EVERYTHING! I would start with the SD card. Re-partition and re-format the card. Download a fresh copy of whatever rom you want to use and a fresh download of the PC36IMG.zip for amon_RA. You can get that from my signature. Flash the recovery from the bootloader first but before you attempt to do so, look at the top of the screen and see if you're still S-OFF. After flashing the recovery, flash the rom. If that doesn't work, follow the instructions HERE.
posting & replying via the XDA Premium app.
Aww derk that blows man
Although from everything I've read about bricks over the last couple years it seems that if you can get into fastboot or recovery then all hope is not lost, yet.
Worst case scenario you get a new one from Asurion for $100.. Unless you don't have insurance, in which case I'll have no choice but to slap you and say "what's wrong with you Sally??"
If your phone turns on it should be alright. You may want to try flashing the PC36IMG over usb instead in case your sd card got jacked up.
just put it in fastboot mode and use:
fastboot oem rebootRUU
fastboot flash zip PC36IMG.zip
dirkyd3rk said:
yeah the only place it will go is bootloader. Since its a 0004 i dont think my fastboot works if im not mistaken right? How would i run the ruu in bootloader, hboot usb, or fastboot? I have the 370.1 ruu already on my comp. Right now im downloading the PC36IMG version of the 3.70 so i can see if it will flash in bootloader. Ive tried to update the recovery again but it wont seem to read the update.zips(ive even removed the .zip part also). I have 3 micro sds right in front of me and every time i take them out the phone and put them in my micro slot on my lappy it keeps asking me to format them as if the phone is corrupting them 0_o FML
Click to expand...
Click to collapse
yeah hboot usb. it should show "hboot usb plug" after you select it and connect to your pc. make sure it installs drivers correctly. i cannot remember if the drivers come from htc sync or android sdk though. once it shows "hboot usb plug" then run the ruu and it should detect your phone and go. this will wipe everything and return you to stock though so be prepared to redo everything
Dirk, as Doug and Haus said, you shouldn't be bricked. If you can get to the bootloader, you *should* be able to fix.
Sent from my PC36100 using XDA App
Let me first start off by saying thanks to all you guys for responding so fast and helping me out! I tried to use my 5 thanks for the day and dish one out to each of you . Ok after 2 hours of panic i got this thing back up and running *wipes sweat off head* Some kind of way my sd card and usb got jacked up and thats why bootloader wouldnt read any PC36IMG.zips i had on it. It took me about an hour to realize my usb/sdcard was borked lol. I followed calkulins guide to restore my sdcard and usb which worked! None of the latest ruu's would work 3.70, 3.30 and i didnt (and still dont) understand why they didnt. So it took me another 30 mins to get fastboot to work (painful steps lol) and after it finally decided to work. I went ahead and downloaded the 3.29 ruu and out of the other 3 i had this one magically worked! I did have insurance by the way @neb! Thanks again guys!
Moral of the story, never flash a radio while "walking" with a hot bag of kettle corn...(facepalm)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thought that was you
jayharper08 said:
Thought that was you
Click to expand...
Click to collapse
Lmfao that's pretty much how I look and feel atm
Sent from my PC36100 using XDA Premium App
Lol. Glad you got back homie.
Sent from "The EVO" using XDA Premium
I've been unable to find any help via Google on how to fix my problem.
I was installing a ROM through Rom Manager when it got stuck on the HTC screen. I had to pull the battery out. I'm able to get into the boot by holding down the volume down button and power, but selecting Recovery only sends to me the HTC screen to get stuck again. I used an app called Nandroid to create a backup on my SD card earlier.
I admit, I'm fairly new to all this (probably why this happened in the first place =/) so if you can explain how to fix my problem in layman's terms that would be great.
By the way, when I'm in the boot menu it says S-Off. I figured saying this now would skip a question later on. Also, when I first get into the boot menu it (very) briefly says something about pg32diag.zip or pg32img.zip not being found.
Use your volume keys to navigate to "recovery" then tap the power button. This will boot you into recovery and you can wipe your data, cache, and reload your ROM or load your nandroid backup
I don't suppose you have adb setup on your cpu do u. the adb reboot recovery command will kick you right to recovery
by the way don't worry about it checking for the pd img and saying not found its suppossed to do that
Sent from my ADR6350 using xda premium
Same problem... Kinda...
I have almost the same problem. I was installing the Revolution HD rom, and i knew that the first boot was long, so I waited it out. I even went for like a 20 minutes run and my droid incredible 2 was still stuck on the HTC screen. So I pulled the battery. I still cant boot into the rom. However, I can get into the bootloader, but when trying to access recovery mode, my phone is stuck on that stupid HTC screen again... What do I do..?
If I were in your situation, I would probably try to backup and flash recovery again.
But PLEASE don't take my word for it. I would hate for you to brick your phone on my hunch. Wait for someone to chime in that has more experience unless you're as foolish as I am
But it wont allow me to return into recovery...
EDIT:
Now the phone will not boot at all. The battery has lost its charge. I'm guessing the white HTC screen does not allow the phone to charge, which makes no sense becasue I had the phone plugged in the whole time.
How about "factory Reset"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i tried to boot into both. But both resulted in just the small vibration and the flashing of the HTC screen, which remained frozen on the screen until i pulled the battery. To make sure i waited about 20 minutes for each to fully "load", but it shouldnt take 20 minutes to boot into recovery, right...?
Damn. I would give it twice that. Then I don't know what to tell ya. ADB sounds like a good idea, but I never use it and wouldn't have a clue.
Good luck.
Sent from my Incredible 2 HD using xda premium
Stuck with the same issue
TheAtheistReverend said:
Damn. I would give it twice that. Then I don't know what to tell ya. ADB sounds like a good idea, but I never use it and wouldn't have a clue.
Good luck.
Sent from my Incredible 2 HD using xda premium
Click to expand...
Click to collapse
Hi Guys.... I am also stuck with the same issue when i went being a **** installing desire hd rom on my dinc 2 by mistake.
Please help.
---------- Post added at 05:30 PM ---------- Previous post was at 05:22 PM ----------
AppleTechies said:
But it wont allow me to return into recovery...
EDIT:
Now the phone will not boot at all. The battery has lost its charge. I'm guessing the white HTC screen does not allow the phone to charge, which makes no sense becasue I had the phone plugged in the whole time.
Click to expand...
Click to collapse
Did you get any solution mate?
I am also facing the same issue.
Bad ROM
It seems like this problem is caused by installing roms not for the Droid incredible 2. I tried installing a incredible s rom on my device, hoping it would work. It didn't. I also tried to use ADB to boot into recovery or directly flash a new rom from the command line. Neither worked because my computer wouldn't recognize the device. I ended up taking a rooted phone back to the Verizon store. I played dumb, and the idiot didn't hit the correct keys to boot up into the bootloader. I managed to get a new phone
However, your best bet is to try and use ADB to boot into recovery or directly flash new, correct rom. See if your computer recognizes your phone...
timsdinc2
Had same problem and reboot recovery works!
Back from the dead, another White Screen
Okay, I know this is resurrecting a long-dormant thread, but it describes EXACTLY the problem I'm having.
I rooted my phone last year with the "Root Your DInc2 Tutorial" - http://forum.xda-developers.com/showthread.php?p=16671031 process, ran CM7 with no problems until early June when it began bootlooping. I believe the latest OTA was the culprit, but I still have S-OFF.
Initially I found the Back To Stock 2.3.4 RUU and used that since I absolutely had to have my phone working (was on a business trip). However, every few days the OTA would get pushed again, and I'd have to reflash the BTS RUU.
I finally had the chance to successfully re-run the "Root Your DInc2 Tutorial" method a few days ago, but I cannot access RECOVERY or FACTORY RESET from the bootloader- it goes to the white HTC screen from both. Using "adb reboot recovery" does the same thing.
At that time, I ran the Revolutionary.io tool. It of course mocked me for already having S-OFF, and offered to flash CWM. I also used the manual method from the tutorial. adb reports writing the recovery, but it doesn't seem to have any effect.
Every time I reboot into the bootloader, it checks for and does not find the PG32DIAG and PG32IMG files.
Is there something simple I'm missing? I have flashed back to 2.3.3, then to 2.3.4, then back to 2.3.3. I have tried flashing several different versions of CWM, 4EXT, and even Amon Ra recoveries. I've tried multiple methods, looked through multiple threads, but still cannot access the recovery.
One I have NOT tried yet is the TacoRoot method - http://forum.xda-developers.com/showthread.php?t=1726134&page=5 , because I have read that it's riskier. Before I go that route, I'd like to hear from anyone who's successfully solved this problem, or anyone with any ideas. I'm pretty disgusted with the stock Sense and Verizon bullcrap. What am I doing wrong here?
tangobar said:
Okay, I know this is resurrecting a long-dormant thread, but it describes EXACTLY the problem I'm having.
I rooted my phone last year with the "Root Your DInc2 Tutorial" - http://forum.xda-developers.com/showthread.php?p=16671031 process, ran CM7 with no problems until early June when it began bootlooping. I believe the latest OTA was the culprit, but I still have S-OFF.
Initially I found the Back To Stock 2.3.4 RUU and used that since I absolutely had to have my phone working (was on a business trip). However, every few days the OTA would get pushed again, and I'd have to reflash the BTS RUU.
I finally had the chance to successfully re-run the "Root Your DInc2 Tutorial" method a few days ago, but I cannot access RECOVERY or FACTORY RESET from the bootloader- it goes to the white HTC screen from both. Using "adb reboot recovery" does the same thing.
At that time, I ran the Revolutionary.io tool. It of course mocked me for already having S-OFF, and offered to flash CWM. I also used the manual method from the tutorial. adb reports writing the recovery, but it doesn't seem to have any effect.
Every time I reboot into the bootloader, it checks for and does not find the PG32DIAG and PG32IMG files.
Is there something simple I'm missing? I have flashed back to 2.3.3, then to 2.3.4, then back to 2.3.3. I have tried flashing several different versions of CWM, 4EXT, and even Amon Ra recoveries. I've tried multiple methods, looked through multiple threads, but still cannot access the recovery.
One I have NOT tried yet is the TacoRoot method - http://forum.xda-developers.com/showthread.php?t=1726134&page=5 , because I have read that it's riskier. Before I go that route, I'd like to hear from anyone who's successfully solved this problem, or anyone with any ideas. I'm pretty disgusted with the stock Sense and Verizon bullcrap. What am I doing wrong here?
Click to expand...
Click to collapse
S-OFF is permanant, no need to do it again. Try flashing this RUU, rename it to PG32IMG.zip, put it in the root of your sdcard and boot into bootloader, when it checks, it'll find that and flash it for you, then you can just use a rooted stock ROM, there's a few out there.
prototype7 said:
S-OFF is permanant, no need to do it again. Try flashing this RUU, rename it to PG32IMG.zip, put it in the root of your sdcard and boot into bootloader, when it checks, it'll find that and flash it for you, then you can just use a rooted stock ROM, there's a few out there.
Click to expand...
Click to collapse
That's one of the RUU's I've already tried flashing a few times- I can't recall if it's 2.3.3 or 2.3.4. I'm currently on RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip In every case, the update skips updating the bootloader. The RUU's work fine after flashing except that I cannot load a recovery to achieve root and install a ROM, make a nandroid, or perform a Factory Reset- trying to select those from the bootloader causes an immediate reboot that then stalls on the white HTC screen.
Any ideas on how to get recovery to work? Do I have a corrupted bootloader? is there any way to fix that, or is this phone crippled?
tangobar said:
That's one of the RUU's I've already tried flashing a few times- I can't recall if it's 2.3.3 or 2.3.4. I'm currently on RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip In every case, the update skips updating the bootloader. The RUU's work fine after flashing except that I cannot load a recovery to achieve root and install a ROM, make a nandroid, or perform a Factory Reset- trying to select those from the bootloader causes an immediate reboot that then stalls on the white HTC screen.
Any ideas on how to get recovery to work? Do I have a corrupted bootloader? is there any way to fix that, or is this phone crippled?
Click to expand...
Click to collapse
Flash a recovery with fastboot?
Sent from my Incredible 2 using Tapatalk 2 Beta-5
prototype7 said:
Flash a recovery with fastboot?
I've renamed the RUU to PG32IMG.zip, put it on the root of the SD, then booted into the bootloader. When the bootloader comes up, it searches for the PG32, finds it, and asks if I would like to apply the update. VOL UP for yes, and it begins extracting. Skips the "Bootloader" step and one or two others I can't remember right now, I do believe the ones labeled "TP" or such. Then reboot, remove the PG32IMG.zip file, and boot into bootloader. At that point, it looks for PG32DIAG and PG32IMG, doesn't find them, and then when I try to go to RECOVERY or FACTORY RESET, it immediately displays the white HTC screen.
The only time I've done anything different was when following the "Root your DInc2 Tutorial" method, where I used both the hack-vivow.cmd and manually entering the commands via adb. And even then, the result was exactly the same- I cannot get to RECOVERY or FACTORY RESET- all I get is the white HTC screen when I select those options.
I've really tried to do everything I can find that seems like it won't totally brick the phone before I came asking for help. I've learned a fair bit, so it's been a worthwhile effort, but I want to have some actual success, you know? As I said, the only thing I have not tried is Tacoroot- I've heard it's more risky and I wanted to see if I had missed anything before jumping into that. I'm also worried that if I DO have something corrupted, it might interfere with the Taco-ing.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Before, I help. You are still s-off
Sent from my Incredible 2 using xda app-developers app
sjpritch25 said:
Before, I help. You are still s-off
Click to expand...
Click to collapse
Thanks for the reply! I do still have S-OFF. Here's what I have as a header on the bootloader:
-Revolutionary-
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-1.09.01.622
eMMC-boot
apr 1 2011, 18:34:39
I have checked with a rootcheck app and confirmed that I do not have root access.
tangobar said:
Thanks for the reply! I do still have S-OFF. Here's what I have as a header on the bootloader:
-Revolutionary-
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-1.09.01.622
eMMC-boot
apr 1 2011, 18:34:39
I have checked with a rootcheck app and confirmed that I do not have root access.
Click to expand...
Click to collapse
Can you use ROM Manager to flash CWM? Or flash 4EXT with the app? You won't have root until you flash the su binary, which you need recovery working to do.
I had MIUI on this Desire (it's my dads) but it have some bugs so I wanted to return it to defaults. I downloaded the RUU_Brav2_UK_1.20.207.1_Radio_32.36.00.28U_4.06 .00.02_2_release_124865.exe file from this thread. During the install on my pc, an error occurred. Something like certain files couldn't be written. Now when I power on the phone I get a HTC logo with 4 hazard signs <!> on each corner. Even trying to get into recovery holding power and volume down does nothing.
All I want to do it return it to normal. Any ideas?
X82X said:
I had MIUI on this Desire (it's my dads) but it have some bugs so I wanted to return it to defaults.
Click to expand...
Click to collapse
Thats not the way to handle bugs
X82X said:
RUU_Brav2_UK_1.20.207.1_Radio_32.36.00.28U_4.06 .00.02_2_release_124865.exe
Click to expand...
Click to collapse
Woah there Nele, thats android 2.1. Why would you do that?
X82X said:
During the install on my pc, an error occurred. Something like certain files couldn't be written.
Click to expand...
Click to collapse
What certain files? Please be explicit
X82X said:
Now when I power on the phone I get a HTC logo with 4 hazard signs <!> on each corner. Even trying to get into recovery holding power and volume down does nothing.
Click to expand...
Click to collapse
Other than flashing a rom, did you do anything else?
What does ALL the information on your HBOOT say?
The error message mentioned about unable to copy files. But the dialogue closed and I didnt have the information. Only thing I got as I said is the HTC logo with the 4 exclamation points around each corner of the screen.
My phone or computer isnt giving me anymore information, at least, I don't know how to access anymore. Only thing I know is power+vol down but that no longer works.
Edit: Here is the error message in fact:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OK well, assuming you are on o2 UK, the one you want is this one:
http://shipped-roms.com/download.ph...00.32U_5.09.05.30_2_release_144166_signed.exe
Now what you need to do is pull, the battery out. Reinsert the battery. Hold Back and press power to turn on. This will put you into fastboot mode. This would normally be a white screen that says fastboot, but now it will be the screen with the 4 /!\'s on it.
Now connect the USB cable, wait at least 5 seconds and then run the new RUU.
Let me know.
Edit, You definitely didn't s-off or change the hboot or anything did you?
I did exactly as you advised. Still getting the exact same error as the image above.
In regards to S-off. I'm worried by your words. The phone did originally have S-off with the MIUI. So now I'm worried I owe my dad a new phone..
Did it have the cm 7 hboot?
Sent from my HTC Desire using Tapatalk
I dont know..but I will go with no since I don't know what that truly is. All I ever did was root it using the instructions on this forum, then install MIUI. Then I went to this.
If you were willing to start a new thread you should also be willing to read an existing one. Read my troubleshooting guide.
hmm well. Your tutorial talks about:
S-OFF
[STEP1]- download "Bravo Stock" from Alpharev
[STEP2]- download Android Flasher
[STEP3]- use android flasher to flash "Bravo Stock"
[STEP4]- run the RUU again and wait for it to finish
Click to expand...
Click to collapse
How do I flash this bravo stock? It's an iso and the programme doesnt like it. Does it go in bootloader? I dunno.
And the gold card method requires me to enable debugging in the menu which I can't do since I'm stuck in RUU mode.
X82X said:
hmm well. Your tutorial talks about:
How do I flash this bravo stock? It's an iso and the programme doesnt like it. Does it go in bootloader? I dunno.
And the gold card method requires me to enable debugging in the menu which I can't do since I'm stuck in RUU mode.
Click to expand...
Click to collapse
Were you even S-OFF? if you weren't then there's no need/ possibility of playing about with the hboot.
Trust me, everything is there. You just need to read it, problem with goldcard? look in the goldcard section.
Or if you're lazy you could risk using the 2.3 RUU.
The phone was S-OFF before this DUU. The flasher programme in the tutorial doesn't like the iso file to flash it to either.
What iso file? There should be no ISO. fIle
Sent from my HTC Desire using Tapatalk
Sorry, forget ISO, I was looking at something else.
Here are the stages I've done thus far.
Downloaded bravo_alphaspl.img
Ran AndroidFlasher, put bravo_alphaspl.img into the bootloader area.
Ticked box saying I'm already in fastboot.
click flash.
Then I get this:
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
Here is all the information I have, in case someone has a fix.
My desire was on MIUI. I then tried another rom, which I didn't like too much either. I foolishly decided to use a wrong stock file and ended up locking my phone into RUU. My phone is now S-ON. I've tried all suggestions in this thread and I went over the troubleshooting thread.
The goldcard tutorial blew my mind, but I tried anyway and fell on the first hurdle when the ReadCID programme doesn't work (Win 7 x64). And I have the right framework installed.
At the moment the phone is a paperweight and I will have to find him an another phone on ebay, since it was my stupidity which bricked this.
If anyone knows a simple way of fixing this, please let me know. Yeah I said simple, because although I have messed with roms, I still know NOTHING. Look at my previous posts in this thread, I clearly don't know what I'm doing which is no wonder I bricked it.
In case this is bricked for life I'm off now to find a phone on ebay. Not an android phone as I'm sure you will agree, for a 65 year old man, who knows NOTHING about android phones, he will never use it to a fraction of its potential.
I hope someone will find a solution, then I can at least sell this on ebay to recoup my losses. But until then, its time to spend money I don't have.
Thanks in advance.
Can you boot into hboot / fastboot?
Im not sure how to find out. All that happens is when I power on the phone I'm stuck in RUU mode. Androidflasher does interact with it, but throws up errors. Complaining that my phone is S-ON so cannot continue.
Your question does not help me at all. So turn off your phone. Now press and hold first volume down (alternative: back) button and then power button. Do you get a white screen with three androids at the bottom after a few seconds?
All I get is the HTC logo on a black background with 4 /!\ around each corner.
If I plug in a usb cable and remove it, the screen turns white with the following information:
BRAVO PVT4 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANE-SYNT0101
RADIO-5.09.05.30_2
AUG 10 2010,17:52:18
RUU
Click to expand...
Click to collapse
Holding down those buttons does nothing and still results in the same screen.
All you can do is ruu from fastboot screen.
Best bet is using the 2.3.3 one. When / if it fails, go for warranty repair.
Record where.it fails
Sent from my HTC Desire using Tapatalk
Is there a link to this 2.33 one? Ones ive tried so far were wrongly RUU_Brav2_UK_1.20.207.1_Radio_32.36.00.28U_4.06.00.02_2_release_124865 and then RUU_Bravo_Froy2_UK_2.14.207.1_Radio_32.44.00.32U_5.09.05.30_2_release_144166_signed. Neither which works.
I have searched high and low for an answer to my problem for the past 5 hours. Haven't found a solution or guide on XDA or anywhere else that can help, so I am making this post as my last effort.
I bought an unlocked GSM Galaxy Nexus off of ebay knowing that it was stuck in a boot loop. I figured it could be fixed. I may be wrong.
I AM ON A MAC The pictures have Windows but I am running Parallels and it sucks.
--------
Ok, so here is my problem lies, when turning the device on normally I get this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get this for a few seconds, then it goes away, vibrates, and comes back ..... over and over.
I can get to both Odin mode and Fastboot:
This is no problem.
I even managed to get CWM on the phone and to come up:
My issue now is that I can't get ADB to work .. Wugs ToolKit won't work ... Galaxy Nexus ToolKit wont work ... nothing.
I can't be 100% sure that USB Debugging is enabled as I can't get past the Google Logo.
Is there anything that can be done to save this phone ... or is it a fancy paperweight?
I have an N4, I just bought this because the seller had no clue how to fix it, and it was a good deal. (not to mention I was planning to use it as a dev device for apps and such)
Thanks everyone!!!
Use the terminal on the Mac. I also have a Mac. Let me find u the files needed for adb and fast boot for macs.
Sent From My Miui Powered Galaxy Nexus
---------- Post added at 10:46 PM ---------- Previous post was at 10:42 PM ----------
OK. This was the guide I used when I first got my nexus s 4g but I also used it for my galaxy nexus. Follow the instructions and make sure u use the correct files for your phone. forum.xda-developers.com/showthread.php?t=1129759
Sent From My Miui Powered Galaxy Nexus
Well crap .... after trying to use Fastboot (as ADB doesn't seem to want to recognize my device) I am stuck at the Google logo with the unlocked padlock.
I can still get in to CWM Recovery and Fastboot, but I am 100% lost on what to do now. I can not find a solution anywhere that works
clay_cauley said:
Well crap .... after trying to use Fastboot (as ADB doesn't seem to want to recognize my device) I am stuck at the Google logo with the unlocked padlock.
I can still get in to CWM Recovery and Fastboot, but I am 100% lost on what to do now. I can not find a solution anywhere that works
Click to expand...
Click to collapse
Did you try using anther pc? Maybe windows can manage this out.. I don't know what else to suggest..
Sent from my Galaxy Nexus
Jar3112 said:
Did you try using anther pc? Maybe windows can manage this out.. I don't know what else to suggest..
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Unfortunately so ---- Windows XP and Windows 7 both ... I may try again tomorrow : /
Ok, so here is my status now ---
Flashed stock image using Odin. Said it was completed and successful. Gave a big "PASS" message.
Rebooted phone, and watched the Google logo bootloop for 30mins.
On the plus side, my phone is now getting recognized as an ADB Interface --- but only in Fastboot. When I enter Stock Recovery or CWM Recovery, I can no longer use adb.
1 step closer, or totally effed?
clay_cauley said:
Ok, so here is my status now ---
Flashed stock image using Odin. Said it was completed and successful. Gave a big "PASS" message.
Rebooted phone, and watched the Google logo bootloop for 30mins.
On the plus side, my phone is now getting recognized as an ADB Interface --- but only in Fastboot. When I enter Stock Recovery or CWM Recovery, I can no longer use adb.
1 step closer, or totally effed?
Click to expand...
Click to collapse
Flash the image, bootloader and radio and that should get you booted
Same Problem
jaymazz13 said:
Flash the image, bootloader and radio and that should get you booted
Click to expand...
Click to collapse
So I just had this happen to me over lunch, after an hour of trying to re-flash stock image, bootloader, and radios, i'm still getting the Google boot up screen. I too can get into flashboot, but I can not get into recovery... Suggestions?
Sorry, I know this threads a little old, but it was the same problem I am having, wasn't sure if anyone found a solution.
Thanks in advance...
marker2002 said:
So I just had this happen to me over lunch, after an hour of trying to re-flash stock image, bootloader, and radios, i'm still getting the Google boot up screen. I too can get into flashboot, but I can not get into recovery... Suggestions?
Sorry, I know this threads a little old, but it was the same problem I am having, wasn't sure if anyone found a solution.
Thanks in advance...
Click to expand...
Click to collapse
Does ur computer recognize ur device when u plug it in?
Sent from my HTC6435LVW using xda app-developers app
jaymazz13 said:
Does ur computer recognize ur device when u plug it in?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yes it does, but only in fast boot.
Other things I found:
-My battery is full. When I plug it in it shows it's charging then shows me battery life, shows full.
-When I turn it on, it gets stuck at Google screen
-When I go into fastboot my computer recognizes it, but after flashing anything to it, it just continues to be stuck on the Google start-up screen
Update since I've written this post... when I plug it in, it wont go past the 'showing that it's charging screen" I have to wait till it shows battery status before I can go into fast boot, and now it wont even do that... neat. Headed home, then i'll swap batteries and try it all again.
marker2002 said:
Yes it does, but only in fast boot.
Other things I found:
-My battery is full. When I plug it in it shows it's charging then shows me battery life, shows full.
-When I turn it on, it gets stuck at Google screen
-When I go into fastboot my computer recognizes it, but after flashing anything to it, it just continues to be stuck on the Google start-up screen
Update since I've written this post... when I plug it in, it wont go past the 'showing that it's charging screen" I have to wait till it shows battery status before I can go into fast boot, and now it wont even do that... neat. Headed home, then i'll swap batteries and try it all again.
Click to expand...
Click to collapse
any updates?
hi clay_cauley .. I have the same problem..did y find any worked solution??
RiotSauce said:
any updates?
Click to expand...
Click to collapse
Hi all, I have the same issue I'll try all the above even though half of it sounds half Chinese to me XD (not a developer, heh).
Cheers,