Related
Hi I am new to the forum. I have an issue. I just bought the droid incredible on Tuesday. Today it started being weird. I believe it has the slcd screen. I was rooted, and used ninja morph to remove some bloat. It was great until I rebooted and I had lost the bloat and the HTC Sense and Gmail stuff didn’t work. So I thought I could just re-flash and get everything back no problem right; wrong. I tried several ROMs and nothing would flash. I then copied all the \system\app stuff from the clockwork mod update file. So I had everything back where it needs to be and nothing showed up in the app drawer. Titanium backup and rom manager have been no help. I then installed and loaded a 140MB PB1IMG.zip that was supposed to be an official leak. So I put it on my SD card, hboot, and great its working. Bad, It turned off not reboot. It turned off, black screen, nothing. If I remove the battery and charger then put the battery in and the charger I get the orange light. If I hold vol up and power I get the QUALCOMM 3 vibrating thing. IF I hold vol down and power nothing. If I just push the power it vibrates makes a clicking sound must have a drive inside and vibrates one more time followed by more clicking. Still black and nothing after that. I am leaving it on the charger tonight. If there is a shred of hope please share.
I did basically the same thing with my SLCD Incredible, with the same results.
Hmm....
Well, the only thing i can think of is maybe the slcd incredibles have different hardware, as some roms do not run, like cm6. My guess is you flashed a PB31IMG for a amoled inc, and as such, caused your problem. Of course, it could also be a number of other things, like a bad zip of some kind, but in the end, if you cannot access recovery / hboot, something went very wrong. Hopefully you didnt mod it too much, and i would try getting it replaced. That sounds like a brick to me... however, try removing the battery and letting it sit for a bit, and if that works, immediately flash a ruu in hboot, as that resets the phone completely, aside from s-off which vzw techs dont look at. Good luck.
mikerulez121 said:
Hmm....
Well, the only thing i can think of is maybe the slcd incredibles have different hardware, as some roms do not run, like cm6. My guess is you flashed a PB31IMG for a amoled inc, and as such, caused your problem. Of course, it could also be a number of other things, like a bad zip of some kind, but in the end, if you cannot access recovery / hboot, something went very wrong. Hopefully you didnt mod it too much, and i would try getting it replaced. That sounds like a brick to me... however, try removing the battery and letting it sit for a bit, and if that works, immediately flash a ruu in hboot, as that resets the phone completely, aside from s-off which vzw techs dont look at. Good luck.
Click to expand...
Click to collapse
Pretty much.
It seems we have a functional phone underneath a non-functional display. adb devices shows the phone in recovery when we turn it on. If only I could figure out how to flash a new kernel to it without being able to see what's going on...
So a question then... when in HBOOT, will RUU recognize the phone?
arache0n said:
So a question then... when in HBOOT, will RUU recognize the phone?
Click to expand...
Click to collapse
Possibly.. But even if, you need to make sure its an RUU for the slcd incredible, otherwise youll be back to square one. I find it odd that a different screen can cause these kinds of issues... Especially nothing in hboot. But theoretically, if the screen is just dead, you can use a microsd adapter to put a new pb31img on the sd, then boot into hboot, wait like 45 seconds to be safe, then hit the up arrow to start the update. then after like 5 min that hit up again. This should be enough for the phone to flash an RUU. but you need to get the timing right. I think its just best to replace it... As for the slcd issue, i think anyone with an SLCD Inc really should just stay put right now, as its becoming apparent that the 2 phones are different in some way, and things like this can happen... Hopefully Koush or one of the higher up devs can look into it..
I am more than willing to try and fix this thing. Where can I get a good RUU file to put on it?
tjamscad said:
I am more than willing to try and fix this thing. Where can I get a good RUU file to put on it?
Click to expand...
Click to collapse
Well thats the thing... I simply don't know if a slcd run was released. I hopefully a dev will look into this... for all we know its as simple as pushing a file in recovery. You can try that with a regular ruu and see if that helps
Sent from my Incredible using XDA App
Could try shipped roms. Even though its ran by different people I think its still legit.
But like mike said there may not be a ruu for slcd.
This really needs to be in Q&A not Development. All these questions do nothing but junk up this thread.
I just fixed this for my buddys INC.
** Please note: Make SURE you have the correct drivers installed. I used the modified Android ones.
1.) Download the Android SDK, and then fire up a command shell in the Tools directory
2.) Boot the Incredible into Recovery:
* Pull battery, then put back in
* Hold Power and Vol Down for 5 seconds
* Wait 20 seconds
* Hit Vol Down once
* Hit Power
* Wait 20 seconds
3.) Check to make sure that ADB can see it by typing adb devices into the command shell you opened earlier
4.) Type adb reboot oem-78 into the command shell. I let the phone sit for a few minutes.
5.) Run the RUU from Shipped-Roms, located here: shipped-roms.com/download.php?category=android&model=Incredible&fil e=RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Ra dio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_14 3351_signed.exe
Once the RUU finished running, my phone rebooted and my screen is alive!
Also posted this in Q&A
sorry, I thought this was a devolpment kinda thing. can you move it to Q&A?
FIXED http://forum.xda-developers.com/showthread.php?p=8960978&posted=1#post8960978
complete instructions
Thanks to arache0n and Jobehonda who helped me when I thought I had bricked my phone most of this is there work.
Hi guys, need some help if possible.
My phone is stuck on the bootloader screen and the up and down buttons are not working so I can choose the option to reboot the phone.
1- I was running MIUI for a while now and I was just listening to Music and suddenly the phone just rebooted and got stuck on the bootloader screen, this is what I tried so far, any help will be appreciated.
2- I tried removing the battery and booting into recovery and the Up and Down button still don't work so I couldn't pick up the option to reboot phone.
3- I ran the PB31IMG Stock zip to go back to stock and after doing the update when is time for the phone to reboot, instead of rebooting it goes back to the bootloader.
Thanks in advance.
If anybody know the command for the SDK to reboot the phone, I think that'll help too.
If the +/- volume buttons don't work at all, I think you're screwed. I don't know of another way to navigate the fastboot screen
Do you have S-off?
Can you load an ruu thru the pc? Not sure if that will help or not.
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.09.01
Guys thanks, I took my phone to Verizon to get a replacement since the phone was Bricked but after I order my replacement the freaking phone turned on again, now I have a choice to make, keep my original phone or keep the Refurbished one they're sending me, thanks again.
I did have S-off.
Well most likely the one you got sent to you is an SLCD model, and you probably have an AMOLED. IMO I would keep the AMOLED, but i'm not sure that you can keep it. I think you have to send in your original.
And since you can turn it on, make sure to flash S-ON and flash it back to stock.
g00s3y said:
Well most likely the one you got sent to you is an SLCD model, and you probably have an AMOLED. IMO I would keep the AMOLED, but i'm not sure that you can keep it. I think you have to send in your original.
And since you can turn it on, make sure to flash S-ON and flash it back to stock.
Click to expand...
Click to collapse
Thanks, I already flash the phone back to stock, I think the rep said I'll be getting the same phone with the AMOLED screen since that's what I got, we'll see when I get the phone tomorrow.
In the mean I'm gonna play with the original one, rooted again and see what happens after I install another Rom.
Just rooted my new DINC, got into the main screen. Went into Clockwork and flashed a nandroid from a different device. Now I cant even get back into CWM. If I hold down and power I get hboot, but anything after that gives me 5 vibrations and blinking green lights. wtf?>
I can actually see CWM for a second, then i get the errors. Is there a bootable CWM, like the NookColor?
DroidHam said:
I can actually see CWM for a second, then i get the errors. Is there a bootable CWM, like the NookColor?
Click to expand...
Click to collapse
not really that i know of
best bet is to ruu back to stock and start over
EDIT: first link i sent wont help you
http://d01.megashares.com/index.php?d01=CHoQD3B
put this on your sdcard, rename to PB31IMG.ZIP
boot into hboot, when it asks to apply the update, say yes
give that a shot
for future reference, nandroids from phones are not interchangeable
I dont know how to use ADB, and that tutorial assumes you can run zips via recovery, which I cant...
Isn't there a PMBTG113.zip or whatever file I can boot off of in recovery that will restore my phone to stock
DroidHam said:
Isn't there a PMBTG113.zip or whatever file I can boot off of in recovery that will restore my phone to stock
Click to expand...
Click to collapse
yea sorry, use the new link and destructions instructions i posted, should get ya running
damn, that link wont start the download
Do you have a micro sd card reader that you can put into your pc or laptop? You need to get that PB31IMG on the root of your card. Then get into hboot to flash.
Sent from my ADR6300 using XDA App
Yea, I put it onto the root, applied the PB31IMG and rebooted. Same fcking problem. WTF?!?!
DroidHam,
try pulling the battery, wait around 10 minutes, put the battery in and boot the phone. Yes, it is very important to wait for that long.
Post your results if it booted or not, i had the same issue.
Also let me know if this is a refurbished phone.
ya its a refurb...
I downloaded this:
build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG
Renamed it and it flashed. Then when I rebooted, it doesn't show me CWM anymore, just the HTC screen, a "popping, kind of electric noise", and then 5 vibrations and blank screen, with green blinking LED.
I downloaded the restore above, and renamed it. It doesn't allow me to flash it. It scans it, but never gives me the option to press up to flash.
Keep in mind, S-ON is now set, whereas it was S-Off before.
Previously I was seeing CWM for a split second then it would crash. I dont see CWM anymore but its still crashing at the same point.
If I copied a nandroid backup onto a different phone, it cant be COMPLETELY ****ed right? Just needs to be rebuilt somehow?
So when I put the battery back in in 10 minutes, should I reflash that RUU I mentioned above, or what?
Any ideas?? Going on day 3 w no phone......
Sent from my LogicPD Zoom2 using XDA App
DroidHam said:
Any ideas?? Going on day 3 w no phone......
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
I noticed you mentioned that while powering on you say you are holding down...down is diagnostic mode, you should be holding up to get to recovery.
After applying the ruu. Try re rooting
Sent from my ADR6300 using XDA App
How do I root if i can't get past hboot??!
Sent from my LogicPD Zoom2 using XDA App
I attempted to root a new Incredible for a friend and had the same thing happen a few days ago. I was able to create a nandroid backup via CWM recovery, and then flashed CM 6.1. CM then bootlooped when trying to boot for the first time. After this point I was unable to get into recovery. The screen would just go blank and would vibrate multiple times. At one point I did manage to succesfully get into CWM recovery without the screen going blank, but then recovery would not recognize the SD card. I restarted and was never able to get back into recovery.
I then attempted to flash a PB31IMG.ZIP from HBOOT that was supposed to restore it to factory state. At this point the phone when blank in the middle of flashing and would not do anything other than vibrate when I would attempt to power it on.
I told them the phone just inexplicably died and they exchanged it at the Verizon store. Everything went perfect with the replacement phone. I figured what happened was a one time thing, but after reading this I would definately be hesitant to root anyone elses Incredible.
Do all phones have hboot?? I don't wanna get screwed. But this was sent was Asurion.... i really need to fix this. There must be a way please!!!
Sent from my LogicPD Zoom2 using XDA App
Just got off work... do the battery pull, wait 10 min, then the start phone see what happens.
I'm not sure at what point you are with the RUU image at this point so take out your sd card just to be safe.
You are getting into the Qualcomm diagnostic mode, which is basically 5 buzzes and then the green light keeps flashing green correct?
I will be on and off for the next few hours to see your results.
DroidHam said:
ya its a refurb...
I downloaded this:
build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG
Renamed it and it flashed. Then when I rebooted, it doesn't show me CWM anymore, just the HTC screen, a "popping, kind of electric noise", and then 5 vibrations and blank screen, with green blinking LED.
I downloaded the restore above, and renamed it. It doesn't allow me to flash it. It scans it, but never gives me the option to press up to flash.
Keep in mind, S-ON is now set, whereas it was S-Off before.
Previously I was seeing CWM for a split second then it would crash. I dont see CWM anymore but its still crashing at the same point.
If I copied a nandroid backup onto a different phone, it cant be COMPLETELY ****ed right? Just needs to be rebuilt somehow?
So when I put the battery back in in 10 minutes, should I reflash that RUU I mentioned above, or what?
Click to expand...
Click to collapse
5 vibrate = defective usb plug/phone... time for nother refurb. theres a couple posts on it, happened to me.
I don't know much.. but I'm pretty sure this thread is in the wrong section. Mods should move this to Q&A or General...
Hi Guys, Idon't post too often as you can see, but I have had a great time rooting my Evo and learning from all the awesome members here. I do my research, and until now I have not run across a problem I could not fix on my own.
I am running CM7 nightly 26, and out of nowhere today, my phone rebooted and proceeded to get stuck in a boot loop. I am not surprised by that kind of thing at this point, but for the first time ever, I was not able to boot into recovery. If I select that option from the boot loader, I just get the white Evo 4G screen and it proceeds to boot loop.
Ok, I thought, maybe my recovery was corrupted somehow, so I pull the SD card and put Amon Ra 2.3 in the root directory and named it PC36IMG.zip and flashed it. No good. I still can't get into recovery.
I also tried downloading the stock (rooted) sprint ROM, putting on the root of my SD card and naming it PC36IMG.zip. After the bootloader detects it and the progress bar finishes, it says "Parsing PC36IMG.zip", and then it just takes me back to the bootloader main menu without an option to flash anything.
Also, is there a way to get S-ON back (with my only access being to the bootloader) in the event that I have to take it in? The alternative would be to drown it or smash it (as a last resort)
Any ideas? Thanks very much in advance for any help!
Westibone said:
Hi Guys, Idon't post too often as you can see, but I have had a great time rooting my Evo and learning from all the awesome members here. I do my research, and until now I have not run across a problem I could not fix on my own.
I am running CM7 nightly 26, and out of nowhere today, my phone rebooted and proceeded to get stuck in a boot loop. I am not surprised by that kind of thing at this point, but for the first time ever, I was not able to boot into recovery. If I select that option from the boot loader, I just get the white Evo 4G screen and it proceeds to boot loop.
Ok, I thought, maybe my recovery was corrupted somehow, so I pull the SD card and put Amon Ra 2.3 in the root directory and named it PC36IMG.zip and flashed it. No good. I still can't get into recovery.
I also tried downloading the stock (rooted) sprint ROM, putting on the root of my SD card and naming it PC36IMG.zip. After the bootloader detects it and the progress bar finishes, it says "Parsing PC36IMG.zip", and then it just takes me back to the bootloader main menu without an option to flash anything.
Also, is there a way to get S-ON back (with my only access being to the bootloader) in the event that I have to take it in? The alternative would be to drown it or smash it (as a last resort)
Any ideas? Thanks very much in advance for any help!
Click to expand...
Click to collapse
Many of us are racking our brains trying to figure out what is causing this situation. Everyone who are experiencing this were using CM7, like you, and it happened to of nowhere and for no known reason. I don't think anyone has figured out a workaround, but I could be wrong. I haven't ready through the forums today regarding this issue. Just know that you are not alone, my friend....
Well, it doesn't look too hopeful from what I have seen so far, but thanks for the support. It's good to know that I am not alone.
If you can still access the bootloader, you should still be able to run an RUU through fastboot.
It happened to me, I was one of the first on the forum it happened to, in January. Was never able to fix it, you could spend a loonnngggg time, and get no results. If you search for my threads you can see the ones I started about the subject.
Long story short, I was never able to fix the problem or get S-On. However by doing a battery pull while flashing a rom with a different radio, during the radio installation, I bricked my phone to the point that it wouldn't even turn on. So thats basically your only way out that I know of. You'll have to perform the battery pull upwards 20 times probably before you get the phone to fully brick.
I'm on CM7 nightlies. What are the HW specs of those having these problems? I thought it was due to CWM but there have been some on RA experiencing this too. Just wondering if this is more specific to the newer HW builds/hboots or occurs with all phones.
My Evo is hardware version 003 for what it's worth.
Westibone said:
My Evo is hardware version 003 for what it's worth.
Click to expand...
Click to collapse
When you select recovery, what happens?
I had same issue in Jan after flashing miui.
tried the suggestions on this thread..but nothing worked:
http://androidforums.com/evo-4g-support-troubleshooting/267018-struck-boot-loop.html
Had to replace my phone...that seems to be the only way out of this.
This is the reason I have stayed away from CM for so long. I keep seeing these horror stories about bootlooping, etc. I know its awesome when its running, but when it comes to the point where bricking your phone on purpose is a good thing, something is wrong For those that it has happened to above, did you get your new one and go back to CM (or any other AOSP rom)?
teh roxxorz said:
When you select recovery, what happens?
Click to expand...
Click to collapse
When I select recovery, it just goes back to the white Evo 4G screen and proceeds to boot loop. Over and over again
My God, another one. It's weird these seem to be happening more and more...
Westibone said:
When I select recovery, it just goes back to the white Evo 4G screen and proceeds to boot loop. Over and over again
Click to expand...
Click to collapse
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip Rename it to PC36IMg. Its 3.70 ruu, flash it in the bootloader, then re-root.
teh roxxorz said:
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip Rename it to PC36IMg. Its 3.70 ruu, flash it in the bootloader, then re-root.
Click to expand...
Click to collapse
Hopefully, your RUU will work. Others who have attempted to this this very thing still couldn't make it work. Me, k2buckley and others have yet to figure it out and believe me, we've tried everything within our experience range. A solution will be found, I have no doubt about that, but "when" is the question that I cannot answer.
teh roxxorz said:
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip Rename it to PC36IMg. Its 3.70 ruu, flash it in the bootloader, then re-root.
Click to expand...
Click to collapse
Don't know why this keeps happening dude. Just like all the other ones. I promise (unfortunately) that this guy isn't going to be able to recovery. Same as the others. THe RUU won't work, neither will the PC36IMG. I don't know why. THey may appear to complete successfully, but the result will still be hanging at the splash screen. That is my prediction, let's see his results. I hope I'm wrong, truly, I do.
k2buckley said:
Don't know why this keeps happening dude. Just like all the other ones. I promise (unfortunately) that this guy isn't going to be able to recovery. Same as the others. THe RUU won't work, neither will the PC36IMG. I don't know why. THey may appear to complete successfully, but the result will still be hanging at the splash screen. That is my prediction, let's see his results. I hope I'm wrong, truly, I do.
Click to expand...
Click to collapse
I hope you are too, but I have saved 1 person with the RUU, so I can hope to save more, but yea, I don't know what's causing this pandemic cuz I've been flashing the latest nightlies, reflashing my kernel, with no problems...I hope it works.
Same Here
Wow, what a coincidence, this just happend to me last night. I had just finished installing and flashing the new, SavagedZen(MOD)-RC1-Evo4G, Rom. Went to bed and sometime during the night the phone got stuck on restarting on the EVO white screen and turning off and on continusly. I have tried all the efforts of putting the stock ROM back on and everything else mentioned in this thread, but to no avail. Like you said, cant get into recovery or anything, just keeps looping through startin and stopping.
With all that is said so far on this thread, it looks like a new phone is the only way to fix this.
Westibone said:
Hi Guys, Idon't post too often as you can see, but I have had a great time rooting my Evo and learning from all the awesome members here. I do my research, and until now I have not run across a problem I could not fix on my own.
I am running CM7 nightly 26, and out of nowhere today, my phone rebooted and proceeded to get stuck in a boot loop. I am not surprised by that kind of thing at this point, but for the first time ever, I was not able to boot into recovery. If I select that option from the boot loader, I just get the white Evo 4G screen and it proceeds to boot loop.
Ok, I thought, maybe my recovery was corrupted somehow, so I pull the SD card and put Amon Ra 2.3 in the root directory and named it PC36IMG.zip and flashed it. No good. I still can't get into recovery.
I also tried downloading the stock (rooted) sprint ROM, putting on the root of my SD card and naming it PC36IMG.zip. After the bootloader detects it and the progress bar finishes, it says "Parsing PC36IMG.zip", and then it just takes me back to the bootloader main menu without an option to flash anything.
Also, is there a way to get S-ON back (with my only access being to the bootloader) in the event that I have to take it in? The alternative would be to drown it or smash it (as a last resort)
Any ideas? Thanks very much in advance for any help!
Click to expand...
Click to collapse
By some awkward chance, have you tried a full wipe, and then flash a sense rom?
teh roxxorz said:
I hope you are too, but I have saved 1 person with the RUU, so I can hope to save more, but yea, I don't know what's causing this pandemic cuz I've been flashing the latest nightlies, reflashing my kernel, with no problems...I hope it works.
Click to expand...
Click to collapse
There was actually one guy that I was able to help recover. (it was short lived though). After trying like 10 different RUU's, one of them had finally took. The phone booted up into a stock sense rom, and the kid was stoked. About 10 minutes after he was up again, his phone rebooted again. Stuck at the splash screen again (this was stock, and he still had s off, because we couldn't ever turn it on). I had him try flashing a recovery again, and low and behold it worked, and he flashed a sense rom. Things seemed fine, and I didn't hear back from him. A few days later, he PM'd be back, saying that it randomly rebooted again, and was stuck at the same splash screen loops. He ended up exchanging his phone. He was the ONLY one, out of quite a few that I've tried to assist through this problem, that was actually able to boot the phone again. Unfortunately, it wasn't stable for him, and then it ended up doing the same thing. Somehow, some way, I believe that the damage was already done, and he just got lucky to be able to squeeze a few extra days out of his Evo, but it was still a short lived recovery.
It's a very perplexing phenomenon that's going on here.
k2buckley said:
There was actually one guy that I was able to help recover. (it was short lived though). After trying like 10 different RUU's, one of them had finally took. The phone booted up into a stock sense rom, and the kid was stoked. About 10 minutes after he was up again, his phone rebooted again. Stuck at the splash screen again (this was stock, and he still had s off, because we couldn't ever turn it on). I had him try flashing a recovery again, and low and behold it worked, and he flashed a sense rom. Things seemed fine, and I didn't hear back from him. A few days later, he PM'd be back, saying that it randomly rebooted again, and was stuck at the same splash screen loops. He ended up exchanging his phone. He was the ONLY one, out of quite a few that I've tried to assist through this problem, that was actually able to boot the phone again. Unfortunately, it wasn't stable for him, and then it ended up doing the same thing. Somehow, some way, I believe that the damage was already done, and he just got lucky to be able to squeeze a few extra days out of his Evo, but it was still a short lived recovery.
It's a very perplexing phenomenon that's going on here.
Click to expand...
Click to collapse
I hope my case doesn't come back to haunt me. Seems like we got a T Virus of phone crashings going around...those already along their way [like you and I] are imune...the newer ones get sucked in. we haz to fix this soon-ishly.
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.