Related
Ok, so I was trying to get my Evo running on the Verizon network, and ended up messing with some NV items that I probably shouldn't have. Long story short it's stuck in a boot loop. I can get to the bootloader just fine, but recovery is a no-go. Also, I was able to do an RUU flash from fastboot, but that didn't fix the boot loop. What should I do?! Please help me!
Sounds like you took a big step and should not have. Next why would you want to go to Verizon? you can not use 4g over there. i think there is a post here or on another android site on getting your phone out of a boot loop with no recovery. Search is your friend
http://lmgtfy.com/?q=stuck+in+boot+loop+without+recovery+android+evo
I found a solution to this exact problem.
Flintr said:
Ok, so I was trying to get my Evo running on the Verizon network, and ended up messing with some NV items that I probably shouldn't have. Long story short it's stuck in a boot loop. I can get to the bootloader just fine, but recovery is a no-go. Also, I was able to do an RUU flash from fastboot, but that didn't fix the boot loop. What should I do?! Please help me!
Click to expand...
Click to collapse
I found a solution to this exact problem after I wrote some nv items from a boost phone. no recovery, evo 4g boot loop over and over till the battery dies and only fastboot commands work. dont even think about saying flashing the boot or system images to fix this thats a no no, it will not work although it wont break the phone either. If anyone is in this same awful position and cant find a fix just pm me or reply to this post and i'll write a full tutorial of what i did. I just dont wanna waste my time and there might be an answer out there already. All i know is that I could'nt find one anywhere and I am literally a part of every mobile forum you can think of. Anyone interested?
marley183rd said:
I found a solution to this exact problem after I wrote some nv items from a boost phone. no recovery, evo 4g boot loop over and over till the battery dies and only fastboot commands work. dont even think about saying flashing the boot or system images to fix this thats a no no, it will not work although it wont break the phone either. If anyone is in this same awful position and cant find a fix just pm me or reply to this post and i'll write a full tutorial of what i did. I just dont wanna waste my time and there might be an answer out there already. All i know is that I could'nt find one anywhere and I am literally a part of every mobile forum you can think of. Anyone interested?
Click to expand...
Click to collapse
i REALLY COULD USE YOUR HELP
need help
I have the same problem, i used a tp2 as a donor, everytihng qorked but data, after copying the needed nv items(CDMA WS 2.7) and still didnt work i copied ALL available items from tp2 to the evo OOOOUCH , now i am at the endless boot loops , the only thing working is fastboot but not adb. i flash all types of roms with no luck, please tell us what you did to get it back running, you help will be appriciated
Need help
I have the same problem, i used a tp2 as a donor, everytihng qorked but data, after copying the needed nv items(CDMA WS 2.7) and still didnt work i copied ALL available items from tp2 to the evo OOOOUCH , now i am at the endless boot loops , the only thing working is fastboot but not adb. i flash all types of roms with no luck, please tell us what you did to get it back running, you help will be appriciated
Please refer to the post below for a fix. This will in no way help you if you started having reboots and then a bootloop while running CM7. It is meant to fix issues that come from corrupted NV items only.
http://forum.xda-developers.com/showpost.php?p=16133086&postcount=54
I am experiencing the boot loop issue also. Really weird, all I have done is root via UnRevoked, use Rom Manager to install CM 6.1.2, and been running this ROM exclusively. I have never overclocked, or even installed or used any task killers in CM 6... I started noticing a couple weeks ago some odd force closes and sync issues with gmail that would come and go. Then, my phone would reboot every once in a while. Sometimes when I was using it, most of the time while it was just sitting on the counter. Then one day it just started the boot loop. Vibrate, white HTC Evo screen for a few seconds, then dark again, over and over. I can't boot into recovery, and have tried a bunch of recovery images (they unpack and update succeeds but attempting to boot to recovery just starts the loop again). I thought about unrooting and bringing the phone back to the store but the instructions I found for unrooting require me to at least get into recovery.... At the time I rooted (Sept '10) I had all the latest OTA... any advice for me to try?
S-OFF
HBOOT-2.10.0001
RADIO 2.15.00.11.19
I made a writeup
Please refer to the post below for a fix. This will in no way help you if you started having reboots and then a bootloop while running CM7. It is meant to fix issues that come from corrupted NV items only.
http://forum.xda-developers.com/showpost.php?p=16133086&postcount=54needed files.
Update
So I never could fix this issue, although I got some really great suggestions and learned a lot from cutthroatamft.
Ended up just deciding to completely brick the phone (in case the Sprint tech might check my bootloader screen for S-OFF). To do this, I just removed the battery while I was flashing an engineering image (while it was updating the radio). After that, not only would the phone not power on at all, but the charging LED wouldn't even light up when plugged in to a power source. They gave me a refurbed Evo.
Haha, I was able to fix my Evo (dont remember what I did) but I have since sold it.
dwreck_ said:
So I never could fix this issue, although I got some really great suggestions and learned a lot from cutthroatamft.
Ended up just deciding to completely brick the phone (in case the Sprint tech might check my bootloader screen for S-OFF). To do this, I just removed the battery while I was flashing an engineering image (while it was updating the radio). After that, not only would the phone not power on at all, but the charging LED wouldn't even light up when plugged in to a power source. They gave me a refurbed Evo.
Click to expand...
Click to collapse
Do you mind pointing me to the image you flashed? I just pulled the battery while flashing a radio, but i'm still booting haha.
You should find it fairly easy if you search Google for eng-pc36img.zip
Looks like the first link.
Sent from my Evo using XDA App
I wish I could, but honestly it's been so long that I dont have any idea.
Thanks cutthroat.
dwreck, at what point did you pull?
I've pulled it twice while it was updating Radio_V2, with the red bar about 1/3 of the way, and nothing about my phone seems to change.
Did you pull a little later? Or did you pull during Radio_Cust? That thing is hard to catch, it updates quickly.
My friend says it took him about a hundred times to fully brick his Evo. Just keep trying I suppose.
Sent from my Evo using XDA App
Sprint was backordered on Evo's. It might take me more than a week to get another one, and it's still 35 bucks. Cutthroat or dwreck, do either of you guys know if it would be safe for me to send my Evo into HTC? I did the battery pull (it took about 20 tries) and the phone doesn't turn on, no led or anything. Will htc know it's rooted regardless?
You should be fine to send it to HTC, my friend has gotten two replaced that exact way. He had no issues with them finding out his were rooted.
Sent from my Evo using XDA App
pthr3e said:
i REALLY COULD USE YOUR HELP
Click to expand...
Click to collapse
Please refer to the post below for a fix. This will in no way help you if you started having reboots and then a bootloop while running CM7. It is meant to fix issues that come from corrupted NV items only.
http://forum.xda-developers.com/showpost.php?p=16133086&postcount=54
I'd just like to take a sec to give props to cutthroat. His guide is GREAT if you've screwed up your NV files (unfortunately that wasn't my problem). Anyways I appreciate you helping me out even after that.
Hi guys, I rooted my phone using z4root. I used titanium back up and set set to factory thing. and then i used one click lag fix the newest version and did one click lag fix v1+ and as soon as i did that my phone rebooted. but ive waited for more than 5 minutes and my screen is still black. and four bottom keys are lit. and galaxy s logo and sprint logo did show up but its still black....
so i read some things on forums and it said just take out battery and re insert it
and turn on. i did that and is still black.
omg. did i just brick my phone? i dont know what to do.
help!
The lag fix IS NOT for the Epic, I repeat IS NOT for the Epic. Odin your phone back to stock and start again.
how do i odin back?
You need to learn to search in the future, but here you go
http://forum.xda-developers.com/showthread.php?t=853209&highlight=ODIn
my epic 4g is 2.1 eclair does this matter?
No
Also don't make useless polls
sorry i was new and didnt know what that was
and thanks for your help
No problem, just remember to search before you flash/install anything that doesn't say it's for the Epic because I'm sure you don't want to have to go through this again.
sorry but whats the difference between ODEX version and DEOdexed version?
That would've been a perfect question to search to find the answer on, but the only difference is that DEODEX is if you want to install themes
i didnt do the odin thing but i did recovery thing and my phone became alive again. i did factory reset thing.. thank you. thank you!
Hello all, I am starting a new thread because the search is down and google is failing me.
I just updated to the newest radios with the combo zip in fastboot. no errors but upon completion i opted to reboot, shows android with box and arrow.
Am I officially bricked?
I can no longer access hboot, recovery, nothing.
plugging it into usb while hitting power or while android guy is up doesn't register anything on my pc.
any help is appreciated while the search function is down. ( already pricing another one )
for reference i was running cm7 stable with stock cm7 kernel, and was on Radio_2.15.00.09.01.
civicsr2cool said:
Hello all, I am starting a new thread because the search is down and google is failing me.
I just updated to the newest radios with the combo zip in fastboot. no errors but upon completion i opted to reboot, shows android with box and arrow.
Am I officially bricked?
I can no longer access hboot, recovery, nothing.
plugging it into usb while hitting power or while android guy is up doesn't register anything on my pc.
any help is appreciated while the search function is down. ( already pricing another one )
for reference i was running cm7 stable with stock cm7 kernel, and was on Radio_2.15.00.09.01.
Click to expand...
Click to collapse
If it completed successfully there shouldn't be any issue.
So when you turn it on it will boot to an android with a box and an arrow and just stay there forever?
If you can't access your bootloader or anything then it is likely you're bricked.
mattykinsx said:
If it completed successfully there shouldn't be any issue.
So when you turn it on it will boot to an android with a box and an arrow and just stay there forever?
If you can't access your bootloader or anything then it is likely you're bricked.
Click to expand...
Click to collapse
thats correct it boots directly to the android and box and arrow..
no search results for an evo jtag either
civicsr2cool said:
thats correct it boots directly to the android and box and arrow..
no search results for an evo jtag either
Click to expand...
Click to collapse
And pressing the volume down button while powering on yields the same result?
When you flash a radio that screen is the update screen don't battery pull let it run its course.
Sent from my PC36100 using Tapatalk
NVM all is well, i let it set for a few minutes. im ignorant i guess. thank you all for the help, you saved the day!
As Khilbron said, That is the screen that you see when it is updating the radio. It takes a while. Let if finish. Pulling the battery while it is flashing the radio is one of the only ways that you can truly brick your Evo. As long as you see that screen when the Evo powers up you may still be ok. Just let it finish. If you get nothing at all when the Evo powers up, just a black screen, then you are likely toast.
m20120 said:
As Khilbron said, That is the screen that you see when it is updating the radio. It takes a while. Let if finish. Pulling the battery while it is flashing the radio is one of the only ways that you can truly brick your Evo. As long as you see that screen when the Evo powers up you may still be ok. Just let it finish. If you get nothing at all when the Evo powers up, just a black screen, then you are likely toast.
Click to expand...
Click to collapse
thanks man. got it all figured out now. mods plz delete.
for anyone that may find this thread with a similar problem in the future. here is solution that worked in the radio thread.
http://forum.xda-developers.com/showpost.php?p=17041666&postcount=2668
civicsr2cool said:
thanks man. got it all figured out now. mods plz delete.
Click to expand...
Click to collapse
Have more patience.
That's why I asked if it "just stay there forever?"
mattykinsx said:
Have more patience.
That's why I asked if it "just stay there forever?"
Click to expand...
Click to collapse
i was ignorant and kinda thought to myself duh, but i guess not lol
I am glad that it worked out for you. I will have to admit that I kind of freaked out the first time I flashed the radio when I saw that screen but I did not touch it and it finished while I was googling to find out what was happening. I have no idea what HTC was thinking putting up a screen like that... why not any text along with the graphic? It would save many bricked evos.
So today I was minding my own business, riding the subway and listening to some music when my Galaxy Nexus decides to reboot itself. After this, it gets into a reboot loop (never getting past the Google logo).
I tried restarting the phone into fastboot mode and using the recovery option, but I end up getting the icon of the android on its back, chest plate open and a red exclamation triangle thing coming out of it. I assume this is bad
A little back story... this is the GSM/Euro Galaxy Nexus. I've been using it for close to 6 months most likely and have never rooted/unlocked it. In actuality, I don't think I've ever done anything with it out of the ordinary (like I have in the past with other android devices). In fact, I don't know if I ever even plugged it into my PC via USB before (thus no drivers, may have never set it to USB debugging enabled).
Is there anything I can do here? I tried looking at a few options (Such as the WugFresh Galaxy Nexus Root Toolkit, which has a Stock resetting option), but since I never enabled USB debugging and installed drivers before the phone decided to go and brick itself, I don't know if I'm actually stuck...
What do you think? Is there an option I have not yet considered? Or am I going to try and convince Samsung to honor my warranty or something?
Moved to Q&A, please pay attention next time where you are opening a new discussion
When you see the android on its back you have to hold vol. up + power to enter the options.
There you can wipe data and reboot to see if it will boot up again.
If that doesn't work you can try flashing the stock images. Those will require you setting up fastboot on your computer. There are many guides on how to do all of that.
Good luck.
If you can get into Fastboot mode just fine, then hook it up to your computer and flash the stock images. It'll revert you back to stock fresh and you can go from there.
We also need to teach people how to debug at basic level at least. If we just teach them how to solve it without caring about what went wrong... they've got the phone might as well learn a few things more.
And yea, i know most couldn't care less. Also, this is no brick - this word very much starts to annoy me when it is incorrectly used and that seems to be getting typical around here. Most likely wiping data/factory reset from stock recovery will allow op to boot up again.
i had the same happening to me under stock. after quite some time it went into a bootloop out of the blue.
this:
bk201doesntexist said:
Most likely wiping data/factory reset from stock recovery will allow op to boot up again.
Click to expand...
Click to collapse
solved it. my data was gone, but at least the phone worked.
then i decided to root and use a custom rom and it never ever happened again.
bk201doesntexist said:
We also need to teach people how to debug at basic level at least. If we just teach them how to solve it without caring about what went wrong... they've got the phone might as well learn a few things more.
And yea, i know most couldn't care less. Also, this is no brick - this word very much starts to annoy me when it is incorrectly used and that seems to be getting typical around here. Most likely wiping data/factory reset from stock recovery will allow op to boot up again.
Click to expand...
Click to collapse
Sure we do but as long as :
1. people start threads that suggest they bricked their phone and
2. all they had to do is Google some around to discover that what they see is a stock recovery and
3. discover what they can do to solve their problems (like most of us do to solve our problems)
I think they couldn't care less about debugging... How sad as it may be.
If you discover problems with a device that is sold as much as the GN it is highly unlikely that you were the first to have that problem. If you are: just post away.
Well, I´ve recently done the most stupid thing in my life, my phone was running fine and I decided to flash another HBOOT, ofc. my phone got stuck on "HTC LOGO" screen.
At this part I would normally pull out the battery, restart in recovery/bootloader but I have one problem, my VOLUME button DOESNT WORK, because I´m a retard and the wires (or how ever you can call it) are cut off(dont ask me why, pls), so its not working, so I cant boot into recovery, or bootloader, im f*cking stuck in "HTC LOGO" screen with no clues.
So my question is, is there some workaround? I mean, are there other combos? Using the 4 buttons on the bottom? All I need is to connect the phone to the pc, so i can somehow control it.
Or do I really have to go to the store and let them fix it up?
Thanks.
Sincerely, F*cking retard.
saker10 said:
Well, I´ve recently done the most stupid thing in my life, my phone was running fine and I decided to flash another HBOOT, ofc. my phone got stuck on "HTC LOGO" screen.
At this part I would normally pull out the battery, restart in recovery/bootloader but I have one problem, my VOLUME button DOESNT WORK, because I´m a retard and the wires (or how ever you can call it) are cut off, so its not working, so I cant boot into recovery, or bootloader, im f*cking stuck in "HTC LOGO" screen with no clues.
So my question is, is there some workaround? I mean, are there other combos? Using the 4 buttons on the bottom? All I need is to connect the phone to the pc, so i can somehow control it.
Or do I really have to go to the store and let them fix it up?
Thanks.
Sincerely, F*cking retard.
Click to expand...
Click to collapse
Hello, Mr. F*cking retard
To get in fastboot mode (pretty much bootloader), hold powerbutton+backbutton.
When installing a hboot, you need to:
1. Backup your current rom.
2. Boot in fastboot.
3. If needed, flash downgrader.
4. Flash new hboot.
5. Restore backup.
With respect, The Guy with a weird username.
Mr. YouAreMyHeroAndIWillLoveYouForRestOfMyLife
You just saved my day, i succesfully rebooted, flashed another hboot, rebooted, everything is working smooth.
I owe you a beer.
Many Thanks !
Mr.F*cking Retard.
saker10 said:
Mr. YouAreMyHeroAndIWillLoveYouForRestOfMyLife
You just saved my day, i succesfully rebooted, flashed another hboot, rebooted, everything is working smooth.
I owe you a beer.
Many Thanks !
Mr.F*cking Retard.
Click to expand...
Click to collapse
Do remember to give a thanks! when someone helps you.
DigginGraves said:
Do remember to give a thanks! when someone helps you.
Click to expand...
Click to collapse
I forgot mista. Im sorry.
Fixed.