Guys and Girls, I need your help.
I consider myself to be relatively experienced at rooting the EVO, adb, flashing, and etc.. However, I am completely stuck and am hopeful someone can help me out. This morning when I tried put my EVO into recovery (Amon 1.8) it went into a boot loop. After a few minutes I tried booting into recovery again with the same result. And, even when I try booting normally it still just goes into a boot loop.
Not being able to boot the phone either normally or into recovery means adb is out of the question so, I tried the next best thing I could think of which was to reflash the rooted PC36IMG zip from toast's part two. (I used a card reader to put the zip file on the sd card) My understanding is that this should have reflashed damn near everything including the radio (albeit downgraded), bootloader, recovery, etc. etc. However, once again whether I try a normal boot or booting into recovery it just goes into a loop.
I haven't done anything different than usual in the past few days except for the fact that I did flash Fresh 3.4 last night only to change my mind and go back to Zippee's Desire HD ROM.
I am open to all ideas at this point since I am nearly out new ones.
I take it you can boot into bootloader since you tried to flash the pc36img... Have you thought about reflashing amon ra via fastboot? If not how about trying a different pc36img? There's one floating around in development of the 3.29 ota. Hope you can get this figured out!
I tried flashing a variety of PC3IMG zips around to no avail as well as just trying to flash a different recovery. The flashing is always successful I just can't get the phone to boot.
Since my first post I have even tried unrooting with the RUU.exe from HTC through fastboot. It too is successful and I get a confirmation but still boot loop. I think the phone is toast. Generally, not a big deal but Sprint's Customer Service stinks.
you said ADB is out of the question, but when you are boot looping, you can still adb, once the splash screen passes and you get into the boot animation, adb is accessible.
The phone never got as far as the boot animation. It would get to the splash screen and immediately loop again. That said, at this point I think it is a hardware issue anyway because even after successfully running multiple versions of the RUU.exe from HTC, it still didn't boot.
Multiple techs have looked at it and tried everything under the sun to get it to work to no avail. So, they ordered me another one which unfortunately, won't be here until Monday.
I don't know about anyone else here but four days waiting for another phone is lousy customer service in my book.
okolowicz said:
I don't know about anyone else here but four days waiting for another phone is lousy customer service in my book.
Click to expand...
Click to collapse
So you're accusing sprint of lousy customer service for something that is out of their control? It has to be mailed/delivered/shipped to the store location for you to pick up. As far as I know, sprint (like every other business in the world) has to use a company that delivers mail/parcels (ups, fedex, dhl, usps) and there delivery schedules are not controlled by sprint or you. I bet you would still whine if they told you it would be shipped directly to your door. I don't know about anyone else but whining about a company who just did there best to take care of you, their customer, makes you a lousy customer.
Happened to me.. did you data wipe before flashing?
Sent from my PC36100 using XDA App
Related
Hey all. Running CM6.1 172 nightly. Launch day evo rooted with toasts 2 part.
Flashed zendroid last night. Booted and ran great, good scores on quadrant etc. Smooth as butta.
Rebooted to do a backup of the new setup. Boot loop, about 1 seconds on the splash screen each time. Not sure if its of relevance but its the fastest boot loop I've seen (day one g1 owner). Went to recovery to restore, and....boot loop after selecting recovery.
So I figure recovery image went bad somehow. Fastboot flash AmonRa1.8. Attempted to reboot into recovery. Aaaannddd....boot loops.
Does anyone have any ideas on where I should go next? I can get into bootloader. Had to do plenty of "repair" with the G1, but this is the first issue I've ran into with my Evo since launch day.
Cliffs: CM6.1. Flash zendroid. Runs fine. I reboot. Boot loops. Attempt to enter recovery. Boot loops. Fastboot flash recovery. Loop loop loop. No recovery, cant get into the operating system so no ADB.
Any help would be GREATLY appreciated. Thanks in advance.
Edit: Just tried flashing PC36IMG.zip from toasts part 2. Still cant get past splash screen. Grrrr. It did however change my splash screen so I would guess it flashed fine. But it still looped after rebooting.
That sucks. Hopefully someone else will chime in. I've never had anything like that happen, but from reading through xda, I've seen this happen to other people. Now I've never had to do it, so don't know the steps. But I think you can take your sd card out, and mount it in your pc. Load a stock RUU onto your sd card, then put the card back in the phone, and flash it from hboot. Then you'll be totally stock and have to start over, but I think that's what you should search about doing. I wish you luck, and hope someone who knows more than I can help more, or inform you of another way.
Sent from my PC36100 using XDA App
k2buckley said:
That sucks. Hopefully someone else will chime in. I've never had anything like that happen, but from reading through xda, I've seen this happen to other people. Now I've never had to do it, so don't know the steps. But I think you can take your sd card out, and mount it in your pc. Load a stock RUU onto your sd card, then put the card back in the phone, and flash it from hboot. Then you'll be totally stock and have to start over, but I think that's what you should search about doing. I wish you luck, and hope someone who knows more than I can help more, or inform you of another way.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Hey thanks for lookin man. Yeah my next move is gonna be flashing a stock unrooted img see if I can get into Android. I already tried reflashing toasts 2nd pc36img.zip (launch day evo rooted with toast 2 part). Thanks for your input tho.
i would say unroot is your best option
Ok so it has happened to me finally.
I was installing a rom. It was unsuccessful so i restored my last backup.
It restored and upon reboot i got 5 vibrates and black screen.
i can get to hboot and hboot usb
hboot ver 92
radio 78
I have tried a couple pb31img. they install all with ok and then 5 vibrate no boot.
I can get to recovery and flash update.zip. 5 vibrates no boot.
I have a replacement on the way.
But i really want to fix it! any ideas?
sorry wrong place mods please move to q&a
/10 characters
Try reformatting your memory card to FAT32 and then put the PB31IMG.zip to the root and try again.
reformat suggestion
did that. only two files on card are pb31img and update.zip. freshly formatted fat32
This is in the wrong section.
But to answer your question, RUU.
Also, root voids warranty. So if they happen to look into it and see that your device is rooted, you'll likely get charged the $100 insurance deductable. Unless you don't have the insurance.. then you'll end up paying the full $549 or whatever it is.
Sent from my ADR6300 using XDA App
un-root and get a refurb. happened twice to me allready/
stoffelck said:
Ok so it has happened to me finally.
I was installing a rom. It was unsuccessful so i restored my last backup.
It restored and upon reboot i got 5 vibrates and black screen.
i can get to hboot and hboot usb
hboot ver 92
radio 78
I have tried a couple pb31img. they install all with ok and then 5 vibrate no boot.
I can get to recovery and flash update.zip. 5 vibrates no boot.
I have a replacement on the way.
But i really want to fix it! any ideas?
Click to expand...
Click to collapse
I've had this happen before. I'm not sure why the nandroid restore would fail, but it may have been because of a near-full SD card. I was stuck at hboot for a while, but couldn't get into recovery. I tried to enter recovery like 30 times and it worked once so I wiped and installed my rom.
i can get into recovery but it is the stock recovery. can only flash update.zip. if i had a rom could i rename it update.zip?
stoffelck said:
i can get into recovery but it is the stock recovery. can only flash update.zip. if i had a rom could i rename it update.zip?
Click to expand...
Click to collapse
no, root is needed for any rom other than HTC
also, then phone will boot if you have it plugged in. get a refurb, ask for over night delivery, they never say no.
stoffelck said:
Ok so it has happened to me finally.
I was installing a rom. It was unsuccessful so i restored my last backup.
It restored and upon reboot i got 5 vibrates and black screen.
i can get to hboot and hboot usb
hboot ver 92
radio 78
I have tried a couple pb31img. they install all with ok and then 5 vibrate no boot.
I can get to recovery and flash update.zip. 5 vibrates no boot.
I have a replacement on the way.
But i really want to fix it! any ideas?
Click to expand...
Click to collapse
I have the same trouble. This happened Monday afternoon after backing up via clockworkmod, full wipe, and flashing cm_inc_full-0.zip. 5 buzzes and green LED flash at boot after the white splash screen.
Previously, I had S-OFF, but after the buzzing, hboot shows S-ON.
I can get the phone to boot completely if I have it connected to my computer, but as soon as I disconnect the cable, the display blacks out, 5 buzzes and green LED flash.
I have flashed the latest Verizon stock PB31IMG (build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip) and it is successful, but the phone still behaves the same. Trying to flash older stock Verizon firmware does not work, because hboot knows it is older, and refuses to install.
I cannot get adb to recognize the phone, no matter what I do, but fastboot sees the phone at hboot. RUU also does not work, it never sees the phone. Unrevoked starts to run, but quickly stops with a communication error.
From what I have read on this forum and others, this issue is happening quite frequently in the last few days.
I tried the "old school" method for rooting, by running a adb shell loop and trying the eject sd card method. That did not work.
Does anyone have any suggestions as to try?
Alpha Maven said:
I have the same trouble. This happened Monday afternoon after backing up via clockworkmod, full wipe, and flashing cm_inc_full-0.zip. 5 buzzes and green LED flash at boot after the white splash screen.
Previously, I had S-OFF, but after the buzzing, hboot shows S-ON.
I can get the phone to boot completely if I have it connected to my computer, but as soon as I disconnect the cable, the display blacks out, 5 buzzes and green LED flash.
I have flashed the latest Verizon stock PB31IMG (build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip) and it is successful, but the phone still behaves the same. Trying to flash older stock Verizon firmware does not work, because hboot knows it is older, and refuses to install.
I cannot get adb to recognize the phone, no matter what I do, but fastboot sees the phone at hboot. RUU also does not work, it never sees the phone. Unrevoked starts to run, but quickly stops with a communication error.
From what I have read on this forum and others, this issue is happening quite frequently in the last few days.
I tried the "old school" method for rooting, by running a adb shell loop and trying the eject sd card method. That did not work.
Does anyone have any suggestions as to try?
Click to expand...
Click to collapse
yea, un-root, s-on and get a refurb.
It might be helpful to know which ROM(s) were being flashed when this happened, to see if there is any consistency.
i had been flashing the #XX-inc-cm7src-syko-eng packages before I flashed cm_inc_full-0.zip
I am having this same problem, to the letter. I had been running Skyraider and wanted to try MIUI. However, I was only preparing to flash a new rom. I hadn't even put the rom on the sd card yet. It was giving me issues getting into clockwork and when I finally managed to get in, it wouldn't backup. I reformatted my sd card and tried again; it said it succeeded doing the nandroid backup and when I rebooted it started doing the 5 vibration no boot thing. I never actually even loaded a rom, all I did was a nandroid backup, which I can't find on my sd card now so it apparently failed despite the message.
I messed with this for a day and managed to get the stock november OTA loaded with s-on via timely connection and disconnection to my pc, so I shouldn't have a warranty issue. I took it into the verizon store and they overnight shipped me a refurb. Unfortunately, it was evening when I went in so it could apparently take until monday
In the meantime, I can still use it if I turn it on while connected to my pc and disconnect as soon as I see the "quietly brilliant" screen. If you wait until it boots all the way in it will usually shut down vibrating when you disconnect it. Hope that helps someone that just needs the phone to work for a bit. Would love to know if someone finds out what is happening and if there is a way to fix it.
Don't know if this helps but I had been having issues with my phone frequently telling me the sd card was mounted read only leading into this, but it would usually fix itself if I tapped the icon that popped up. I also had lost the ability to unmount the sd card prior to this, and the phone would no longer work as a mass storage device when connected to the pc. I thought it was a problem with Skyraider but now I'm not so sure. Don't know if others are also experiencing this, but even now that I got it running on stock and into the os the 8gb internal phone storage and my sd card no longer register.
This basing on the info I have gather from people smarter then myself...
5 vibs = qualcomm download mode. From what i have been able to gather a simple batt pull should resolve the issue.
The way you get into this download mode is by pressing the vol+/- at the same time. Kinda explains the reason it is becoming so frequent.
I have no proof to back this up but give it shot.
Okay, so do you have CWM at this point?
CWM?
Sent from my ADR6300 using XDA App
I s-offed, rooted & put cm7 stable on a friends Incredible. He got to messing with ROM Manager. I'm not sure what he tried to flash, but it screwed this phone up big time. He said something about a kernel & also about an update to recovery. I told him not to mess with it, but i guess he doesn't pay attention.
Here's what it doing. Boot loops on white HTC splash screen. Boot loader won't recognize any PB31IMG.img's. It scans to where it finds the .img, but does nothing. It boots to clockwork recovery, but if you select any of the options, it goes to a blank screen with just the clockwork background image. I get the remote:not allowed error when trying to flash recovery through fastboot even though it still says s-off.
What I've tried. Loading several PB31IMG's with no results, including the one with the same radio. I've also tried every recovery pb31img except stock. Nothing happens. Tried doing an ruu, but since the phone won't boot to the os, it never sees the phone as attached even in hboot. I have the hboot drivers installed. I've tried running the unrevoked reflash_package again, but it won't recognize it in hboot either. I think you have to start from the ROM for the software to work.
I'm guessing i am going to have to fix it with some adb or fastboot commands, but i would need some guidance here. I have it set up, but i have no idea on what commands to use. I have searched & read these forums & can't find anyone with a similar problem.
If anyone has any ideas or knows what to do, let me know. If you need bootloader info, let me know. I told him I would try to fix it, but no promises. I have never seen anything like this and have semi bricked many devices. The post about it not recognizing the ruu images baffles me. I owned an evo 4g, which is very similar to the incredible, so I'm not completely unfamiliar with the way it works. Any help would be appreciated. Thanks guys.
EDIT: NVMD! I figured out you have to use the trackpad to select anything in recovery instead of Power button. Sorry to waste your time. Have a great day!
CM powered EVO 3D, enough said.
I have an unlocked and rooted e973 running stock 4.1.2 (E97320e). I have somehow managed to flash both TWRP and CWM as a custom recovery, and now cannot access recovery mode at all. I know this because ROM Manger shows both under the "Recovery Already Installed" section. I can boot normally and access download mode with no issues, but if I am trying to get into recovery mode I always get a black screen that shows the LG logo and says "secure booting error! cause : boot certification verify". If I use ROM Manager or GooManager to reboot to recovery I always get a warning pop-up "unfortunately com.lg.hiddenmenu has stopped" before it reboots to that secure booting error screen.
So I'm really not sure how to fix this, I just want to start trying some different ROMs, but need to get the custom recovery sorted out first. Should I just follow this guide for unbricking? How about doing a factory reset (booting with power and volume down)? Will being rooted/unlocked matter for doing a factory reset? Would it even clean up the mess I have made of the recovery? I guess I am just looking for a way to wipe everything completely clean and start fresh since I have all my important stuff backed up. I should note I got this phone unlocked and discovered a "NOT FOR SALE" engraved into the side after peeling all the stickers off.
Thanks in advance for any advice.
edit: I decided I might try fastboot erase recovery, only to discover I cannot access the bootloader or fastboot mode. adb reboot bootloader just reboots the phone like normal and starting in fastboot mode by holding volume down and power just takes me to the factory reset screen. Any ideas?
edit: Tried to use TeenyBin, but LGNPST doesn't detect my device ("no port connected") even when it is properly connected in download mode.
Not to be that guy, but its been stated several times to use FreeGee to install custom recovery. Mainly because even if you do install it correctly som other way, your bootloader would be locked and if you install something then, you get a soft brick (in a good scenario). Make sure you have root and grab FreeGee from the market and let it install.
Also, why would you keep a phone that says "NOT FOR SALE"? I wouldnt touch it with a stick and send it back wherever you got it from.
wargreymon89 said:
Not to be that guy, but its been stated several times to use FreeGee to install custom recovery. Mainly because even if you do install it correctly som other way, your bootloader would be locked and if you install something then, you get a soft brick (in a good scenario). Make sure you have root and grab FreeGee from the market and let it install.
Also, why would you keep a phone that says "NOT FOR SALE"? I wouldnt touch it with a stick and send it back wherever you got it from.
Click to expand...
Click to collapse
I bought it at cost from a guy on Kijiji (Canada's craigslist equivalent) brand new. He claimed he had a bunch of them because his company was going to use them but then last minute they decided to go with blackberry so he had to sell them. I didn't realize it had the not for sale until i was home and peeled all the stickers off, and since it worked fine with my existing SIM I just kept it.
Anyways, I will give freegee a shot and see if that can fix the problem. I have been looking through many different resources and threads and never saw it mentioned to use freegee to install a custom recovery, but I guess it's worth a shot. Thanks!
edit: It worked! I can now finally get into TWRP 2.5.0. Thanks again for the reply!
xerockz said:
I bought it at cost from a guy on Kijiji (Canada's craigslist equivalent) brand new. He claimed he had a bunch of them because his company was going to use them but then last minute they decided to go with blackberry so he had to sell them. I didn't realize it had the not for sale until i was home and peeled all the stickers off, and since it worked fine with my existing SIM I just kept it.
Anyways, I will give freegee a shot and see if that can fix the problem. I have been looking through many different resources and threads and never saw it mentioned to use freegee to install a custom recovery, but I guess it's worth a shot. Thanks!
edit: It worked! I can now finally get into TWRP 2.5.0. Thanks again for the reply!
Click to expand...
Click to collapse
Good thing it worked. Hope you got it for a very good price or I would go nuts on the seller But as long as you are happy with it. We finally have a few roms to try so good luck finding one that fits you.
For some reason my phone isn't booting up all the way to the rom/OS. It gets stuck on the boot animation and goes on forever and hasn't been able to boot up since yesterday, when my powered off at 20% battery, which is something normal for my phone. I was rooted and on android 4.3/MK4, but when I put it to charge and tried booting it back up, the phone would boot up, but would get stuck on the boot animation, going on forever. It wouldn't freeze it would just continue to play the animation. I tried removing the battery, factory wiping it, and installing a new rom, which I found out was for a different baseband. When i finished installing it it still wouldn't boot up all the way through.:crying: I then tried installing the previous rom, and still no good. After all that I installed a stock firmware using odin, hoping it would work. I installed the 4.4.2 NE2 firmware, which isn't for my phone but watching zedomax's video, he said to download the latest build date, which is what I did. Well, downloaded it and flashed it through Odin with a PASS and everything going good. Although, when it was rebooting-even after a factory and cache wipe-it still wouldn't boot up. I tried installing other firmwares aswell, but still no luck. I'm just waiting for it to finally boot up, so if anyone can help me out, I WOULD GREATLY APPRECIATE IT, otherwise, anything is going to help at this point. Since I flashed the firmware, I now have a stock recovery and rom(I hope). I've been through these types of situations, but not to this point.. :crying:
It seems odds, but you may want to try a new battery. I recently went through a total disaster with my device and it ultimately was the battery. You may want to try booting with it connected to the a/c wall charger. It may give you an indication.
Have you tried the quick fix posted? My phone did the same thing when i had the stock recovery it showed error mounting efs folder. I noticed after installing clockwork that error didnt show up. It was still the same problem though. Wouldnt hurt to check it out. I got my note two from a friend who described the issue starting the same way you said happend to yours. The phone had never been rooted though. Good luck to you in trying to fix it.
Sent from my SM-T217S using XDA Free mobile app