Evo keeps boot looping...Need a little help - EVO 4G Q&A, Help & Troubleshooting

This boot looping issue is not like the normal ones (I have googled,as well as checked here...I am a noob,but know how to search)
I am running CWM v3.0.0.5
Energy ROM
And Aggressive Freedom (Was running More freedom prior,but still the same issue occured)
It does not matter which rom i am running ( have tried about 5 now)...after a few days my phone will lock up no matter what i am doing and then reboot,except it gets stuck in a boot loop...If I do a battery pull and fire it back up...no problem it boots up like nothing ever happened...and after a few days it will do it again so on and so forth. This has not always happened, it started occurring around 3 months ago. Can anyone help me as to rectify this issue?
Also when i flash a new rom i do a factory wipe/reset,run gruesome format all 3 times,clear cache,as well as dalvik cache..and THEN i will flash the rom over.
Any help would be GREATLY appreciated. its not a GIANT pain but it just wants to happen at odd times which sucks lol

Kernel
Have you tried installing a different kernel trough Recovery?
Edit: Sorry, didn't read your post carefully enough. Have you tried a stock kernel?

No i have not tried a stock kernel. Figured with aggressive/more freedom it would be a little more lenient on the battery life.

Look in this post: http://forum.xda-developers.com/showthread.php?t=708502
Since I don't own an EVO, I'm not sure if this is a good one. Try it at your own risk.

Do a search in the development section for a stock kernel also maybe download set CPU to try one of the governors sounds like phone does not like over clocking they all run a little different.

Rammv said:
Do a search in the development section for a stock kernel also maybe download set CPU to try one of the governors sounds like phone does not like over clocking they all run a little different.
Click to expand...
Click to collapse
Thats the problem i was having also,my phone could'nt be overclocked over 113600 MHz or it would start locking up and giving me random reboots,try dropping your level.Ondemand profile works great with my phone,others seem to give me problems.

busted GPS receiver
My wife's Evo did the same thing and we spent a total of 6 hours at the [carrier] store trying to get them to replace it. The store is cement and cinder blocks so there is no GPS signal inside. The phone easily passes their "complete" diagnostic.
Finally, I became irate and pleaded the store manager to get in my car with me. Before we got out of the parking lot, the phone began rebooting.
Turns out, their "complete" diagnostic doesn't test the GPS receiver in any way. He knew this, but I had to point it out to him.

My phone is underclocked with the kernel i am running UNLESS the roms i use some how over clock them, SetCPU does not work for me. And my GPS is always turned off because i try to conserve the battery life.

I will go ahead and see if i run the stock kernel...or one that comes with the rom instead of using Aggressive or More freedom kernel and see how that one fairs out.

htc evo boot loop
i was using my htc evo fine today, it was on 2.3 ota when i rooted it with revolution, it was half way flashed to boost, it already had the NV items and the Nam files, on the front said boost mobile, after i rooted i put a Speedy Shift rom, to make it have the internet pass through like the shift, so today i decided to finish flashing it to boost, after i put the nv and nam files again, i restated the phone, and from there it just keep doin a endless reboot, i could only go in the hboot, i tryed the pc36img, Amon ra, Ruu, and rerooting with revolution but it doesnt read the phone on fastboot, any help?
S- Off
HBoot - 6.16.1002
Radio - 2.15.00.0000

Related

EVO stuck on bootloader no recovery tried several PC36IMG none help :((

Well I could not get out the bootloader and bootloop after running the stock ruu.exe and updating several recovery images PC36img none of em work so I had to go to sprint to order a new one. I really want to come back to MYN ROm when I get my new Evo..But I do not want to brick it again. The only dilemma is I really do not have the total idea of what made my phone just crash force close android and start bootlooping.
I used the unrevoked one click root method and the unrevoked forever to nand unlock it. I was flashing several different kernels at first. When I saw still no improvement in battery life I went to start off flashing Fresh, then AVA then Myn. I had got a force close to with AVA rom and bootloop but i was able to get into recovery and to the splash screen. I wished I had pay attention to what kernel I flashed which was 24hrs before my phone crashed same thing happened when I flashed Myn's rom. However, I was getting crazy bootloops when I first used the battery tweak and after I saw the battery drain I tried a different kernel. At first i was wiping both cache in between but since so many kernels even the stock kernel was giving me a loop at the splash screen (where myn warm 2.2. would come up) I started wiping less just to finally get a kernel which would be stable. The last kernel I flashed I remember was netarchy 4.1.8 cfs fresh compatible around saturday 3pm and around 3am the phone just crashed android crashed and the worst bootloop started happening.
So can anyone give me some feedback please that has their device running smooth with this Rom and/or have had this issue before? Do you recommend unrevoked forever? Does anyone may think its due to flashing so many kernels?
Are you paying for the new phoneor is the warranty taking fare of it.
I'm new to to android scene, but it seems like you shot first and asked questions later... approach could have cost you a new phone.
Anyways have you given up on your old phone. I'm sure there's ways to fix.
What recovery version do you have?
Depending on what recovery you have, you should have usb access still, if so drop a another rom in there and flash via recovery.
Sent from my PC36100 using XDA App
you more then likely didnt actually brick that phone. i would wager if you had asked and tried a few more things that you could have gotten it to work. If the phone boots at all and goes to a boatloader or fastboot then it is 99.999% of the time not bricked and can be fixed.
for example (and you may have tried) the only PC36IMG that normally works most of the time is the original eng bootloader in toasts old root method. if you tried any others most have them dont seem to rewrite everything to get it working.
as far as what caused it there is no way of knowing with the information you provided. I have run the rom and it has been stable. I doubt it was flashing so much as myself and many others flash daily with out problems.
At a lost but luckily I did not have to pay for a new phone
omegasun18 said:
you more then likely didnt actually brick that phone. i would wager if you had asked and tried a few more things that you could have gotten it to work. If the phone boots at all and goes to a boatloader or fastboot then it is 99.999% of the time not bricked and can be fixed.
for example (and you may have tried) the only PC36IMG that normally works most of the time is the original eng bootloader in toasts old root method. if you tried any others most have them dont seem to rewrite everything to get it working.
as far as what caused it there is no way of knowing with the information you provided. I have run the rom and it has been stable. I doubt it was flashing so much as myself and many others flash daily with out problems.
Click to expand...
Click to collapse
I agree I do not think i bricked it but I have tried so many PC36IMG and different bootloaders I am now way more familiar with android and recovery than before lol. I saw your posts in another thread about a guy with the same issue flintr i think but the toast 2 eng still was not working however those were the first i was trying it may work now since I'm sure I was using a different hboot the 97 version then.
I am not sure if there is anyway its going to work now since even though it still says im Ship S-off I have tried running the stock ruu. I tried the fastboot and i flashed an older hboot to get my fastboot commands..so i ran the command fastboot flash recovery recovery-1.8ra. img but it still would not get into recovery i really do not have any idea what happened.
I really think somehow my kernel is affecting everything. I tried to flash a kernel through fastboot and i was getting error it could also be though i do not have the right format for my kernel file.
potna said:
Are you paying for the new phoneor is the warranty taking fare of it.
I'm new to to android scene, but it seems like you shot first and asked questions later... approach could have cost you a new phone.
Anyways have you given up on your old phone. I'm sure there's ways to fix.
What recovery version do you have?
Depending on what recovery you have, you should have usb access still, if so drop a another rom in there and flash via recovery.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I can't get into recovery..as soon as i select recovery it starts bootlooping.
I'm not paying for the new phone I went to a small sprint store so they just looked at it tried to clear data in bootloader and then ordered me a new phone.
Fair enough, sometimes a fresh start can be good. Good luck
Sent from my PC36100 using XDA App

Answers to common questions about SyndicateROM Frozen

This is a guide I’ve put together from my (in)experience with flashing ACS. It mainly comes from the replies of k0nane and theimpaler747 in the SyndicateROM thread. However, since there’s so many pages that can be tricky to search for idiots like me who just throw up random posts for others to solve their problems, I thought it would be good to summarize it along with anything I happened to notice from flashing a couple of Epics. Consider it the FIBI guide.
Step 1: Read all posts by k0nane on page 1 of the SyndicateROM thread before doing a damn thing! http://forum.xda-developers.com/showthread.php?t=976194
Instructions for CWM are in this thread: http://forum.xda-developers.com/showthread.php?t=897612
Useful hotkeys:
Download mode - Hold down 1 on the keyboard when you power on the phone
Recovery mode - Hold Volume down+camera+power to power on the phone
Reset phone - Hold volume up+camera+power. This generally works when the phone is completely locked up.
Flashing:
When going between versions of ACS, check their notes to see if you need to do anything other than flash. You can go between some versions without wiping or losing anything. You can also flash between standard and fully loaded without wiping or losing anything.
Sdcard doesn’t mount in CWM, but shows up in Android - Format the sdcard in Android.
Boot hangs on the Samsung screen – Redownload, format your SD card and reflash
Boot screen flashed between different things – Wipe cache & data 3x and reflash
Journaling:
Enable journaling – In CWM, go to backup and restore. Backup, then restore using that backup. Journaling enabled!
Make it so you don’t need journaling – Keep a copy of the ROM on your phone at all times. Should you ever have data corruption, jump into CWM and flash the ROM again. It’s quick, no wipes needed.
If you restore a backup made in CWM and want to have non-journaled again – Flash the ROM after restoring.
Other issues:
FC in a specific app – Go into manage applications and clear data for that app
FC in several apps – In CWM > Advanced, try fixing permissions. Can also clear caches, and if that doesn’t work, reflash the ROM.
If you have any major issues that seem unresolved, Odin everything back to stock with EB13, format your sdcard in android, re-download everything, re-install CWM, re-read all of k0nane’s posts on page 1 and try again.
If you want ads back – Install adfree from market and hit revert
If your phone is freezing often - Flash either the vision kernel found here: http://forum.xda-developers.com/showthread.php?t=1012136 or the Twilight 1.0.4 kernel found here: http://forum.xda-developers.com/showpost.php?p=12504067&postcount=5904. I haven't had the freezing issues, but I'd recommend trying the vision kernel first as it has some other potential benefits.
Recommended tweaks and add ons:
Fugutweaks – This will smooth out a few random things on the phone. I’ve noticed more responsiveness on the lock screen and icons on my homescreen. Small, but nice. Install the ZIP in CWM, file can be found here: http://forum.xda-developers.com/showthread.php?t=981125
Impaled Keyboard – Makes the keyboard less likely to skip keys. Still have some, but they’ve gone down a lot. I use the Speed Demon Edition, still had a fair amount of dropped keys with standard one. Install the ZIP in CWM, file can be found here: http://forum.xda-developers.com/showthread.php?t=1025533&page=18
SetCPU – Handles scaling the CPU and overclocking. Use ondemand setting for smooth performance. If you have issues when the phone is idle or it doesn’t wake up properly, set minimum CPU to 200Mhz. Free for XDA members, APK can be found here: http://forum.xda-developers.com/showthread.php?t=505419
Battery Calibration – If you want to calibrate your battery without going into CWM, grab the app from this thread: http://forum.xda-developers.com/showthread.php?t=1024867. It’s now available from the Android Market.
Vision Kernel – Pretty much Twilight + gives you 1.4Ghz and Voodoo colour which improves balance when brightness is at 100%. Flash in CWM, wipe dalvik. Kernel can be found here: http://forum.xda-developers.com/showthread.php?t=1012136
And a final note that I'm now about 10 hours into testing... if you are using fully loaded and want better battery life, really try standard. It very easy to switch, it flashes over fully loaded with no wipes or data loss, the only thing you lose is that it resets your homescreens. But really, this is day 1 of it for me and 10 hours in I'm at 62% battery remaining. Usually by this time I'd be around 20%.
Great info! I recently installed the newest SyndicateROM 1.1.0 on my Epic and the only trouble I had was with the included Twilight 1.1.0 kernel. My phone kept freezing and I would have to pull the battery to reboot.
This is an issue that has been documented with the ROM and is said to be caused by the kernel and its adjustments to voltage and overclocking, not all phones handle this well.
To fix the issue I flashed the Twilight 1.0.4 kernel, as suggested by k0nane, and I am about a day into testing without any freezing issues. The only problem is that the Twilight 1.0.4 kernel has a known issue with video recording and it does not work.
Let me say that the performance increase from installing SyndicateROM and ext4 are well worth the trouble.
Have you tried the vision kernel? That might fix your freezing without breaking video recording.
is your brightness at 100%??? what was the difference between standard and fully loaded again??
VeNoM vZ said:
is your brightness at 100%??? what was the difference between standard and fully loaded again??
Click to expand...
Click to collapse
What does the brightness have to do with anything? And for the differences, here's from the SyndicateROM thread:
k0nane said:
SyndicateROM Standard includes LauncherPro. All Samsung and Sprint bloatware are completely gone!
SyndicateROM Fully Loaded - the choice of ACS team lead rjmjr69 - features TouchWiz instead of LauncherPro, and adds in Social Network Sync, Facebook, BuddiesNow, Program Monitor, and the stock live wallpapers. All the rest of the bloat is still gone!
Click to expand...
Click to collapse
Catalyst Shift said:
What does the brightness have to do with anything? And for the differences, here's from the SyndicateROM thread:
Click to expand...
Click to collapse
The brightness for battery life.
No, brightness is not at 100%. I generally use 0-25%, though I'll kick it to 100% when viewing photos or when I'm outside. Even with the lower brightness setting, I'd always have to recharge in the afternoon. I'm still doing a lot of testing for ways of having the battery last longer, today is longest it's ever gone for. I'll be adding more information when I feel like I've got a solid way of having it all setup.
OP, could you add the freezes and "terrible battery life" solutions? Namely, flash the kernel in the second post or VisionKernel. It's the most annoying one to answer multiple times daily.
Thanks much for this! Hopefully people read it.
I want to get the battery situation on my phone sorted out before adding it to the list. I was having pretty bad battery life, but switching to standard and removing gallery has made my phone last all day for the first time ever. I want to do some experiments between setcpu options, juicedefender and the vision kernel to see what works best. Hopefully by this weekend I'll have a more detailed idea as to how to get better battery life.
But for now, anyone having battery issues my current setup is using ACS standard and replacing gallery with quickpic. This has doubled my battery life.
Hey wassup everyone, first time writer long time viewer, and first let me say thanks to all the great people that have provided us with great roms for the epic and the syndicate team as well, Im currently using a Epic 4G with sindicate rom freeze 1.1.0 and i must say its awesome, aside from my battery dying really quickly when im runing it at 1.3ghz its actually great, usually i end up operatig it at 800mhz to actually save some battery life last me for 3 days at a time, and when i have it pluged in or show off my awesome epic i raise it back upto 1.3ghz, big difference cuz when i raise it up there my battery drains rather quickly like 3 percent a minute or so.....
well anyways now that, thats says, I have CWM 3..0.5 with syndicaterom twilight 1.1.0 and ive been sucessful at loading custom boot animation, but one thing is that im having trouble is loading the animation with sound? any idea onhow i can od that?, what are the steps, cuz so far ive been using root explorer to transfer and change bootanimation to load up on my screen, but i have no idea where to put the sound or how to even get it to load with the bootanimation any one have any ideas? please help, i do all his trought my phone, put the bootanimation on my sd and work from there and trasfer it to the system/media, most bootanimation that do have sound on them say to put it on the system/custimization/resources but i look every where and the syndicate rom doesnt have that archieve just the system/media, how can i load the sound into my boot? and how can i change the power off animation as wll?
Maybe someone should make a wiki "Trouble shooting guide" formatted like the ones found in the back pages of user manuals..
This might.. just maybe (crosses fingers) alleviate the never ending repeating of questions in the main sfr thread
Catalyst Shift said:
Have you tried the vision kernel? That might fix your freezing without breaking video recording.
Click to expand...
Click to collapse
Just tested Vision kernel 1.1 and ran into countless issues. My phone would not open camera, gallery, or music apps. And after that debacle I didnt even bother to find out if any other apps were misbehaving.
The first sign of trouble came when I installed a fresh version of SyndicateROM 1.1.0 and then flashed Vision kernel 1.1. The phone booted-up fine but when I went to shut down it immediately froze and I had to pull the battery.
Im going to stay on Twilight 1.0.4 kernel for a while until I find something else.
I have tested Twilight 1.0.4 kernel for about a day or two and have not had any problems so far. I even overclocked with SetCPU to 1.2GHz without any issues.
tmspyder said:
Maybe someone should make a wiki "Trouble shooting guide" formatted like the ones found in the back pages of user manuals.
Click to expand...
Click to collapse
I would be more than happy to contribute my experiences if this gets up and running. PM me with any updates to the "SyndicateROM [TSG] WiKi"
Please Help a Novice
I have installed this ROM, followed the directions and thought I did everything right. But when I rebooted the phone, I just get the Clockwork Recovery screen. Have I bricked my phone? How do I recover? Please please please help...Haven't even had my phone for a day...
By the way, the error I'm getting is:
ClockworkMod Recovery v2.5.1.0
E:Can't open /cache/recovery/log
I backed up before I installed this ROM, and Restore brings me back to this same screen / message
mercerma said:
I have installed this ROM, followed the directions and thought I did everything right. But when I rebooted the phone, I just get the Clockwork Recovery screen.
Click to expand...
Click to collapse
Please elaborate on the steps that you took to install the ROM and CWM.
What version of CWM are you running?
What modem do you have installed (...DK28, EB13, EC05)?
Have you transfered the SyndicateROM 1.1.0 onto your SD card before you installed CWM?
Did you wipe data, cache, and dalvik cache at least three times each before installing the .zip?
Your phone most likely is not bricked, that is a very hard to task to achieve. Worst case scenario you may have to do a clean wipe with odin and flash the stock ROM to start the process over. We can try to help you with any issues you may have but in the mean time try searching to the forum to find answers to these questions.
Hey, great idea for the thread.
Something I learned:
I was having AWFUL freezing problems. Tried all the fixes (vision kernel, old twilight) to no avail. If these don't fix your problems, try Genocide Kernel (on these forums). Solved my problems.
Catalyst Shift said:
But really, this is day 1 of it for me and 10 hours in I'm at 62% battery remaining. Usually by this time I'd be around 20%.
Click to expand...
Click to collapse
Ok, so im thinking of switching to the standard edition of he rom cuz im currently using the fully loaded added the 1.0 kernel vision on it to get the 1.4ghz, and its pretty smooth its stable at times so im keeping it at 1.3 for now until its set more stable..... however when u said that ure at 10 hours and u still have 62% whats the speed u have ure epic set at and whats the brightness?
Nolyrics2 said:
Just tested Vision kernel 1.1 and ran into countless issues. My phone would not open camera, gallery, or music apps. And after that debacle I didnt even bother to find out if any other apps were misbehaving.
Click to expand...
Click to collapse
Fix permissions in CWM/etc.
Kernels cannot cause that. It's that simple.
Nolyrics2 said:
Please elaborate on the steps that you took to install the ROM and CWM.
What version of CWM are you running?
What modem do you have installed (...DK28, EB13, EC05)?
Have you transfered the SyndicateROM 1.1.0 onto your SD card before you installed CWM?
Did you wipe data, cache, and dalvik cache at least three times each before installing the .zip?
Your phone most likely is not bricked, that is a very hard to task to achieve. Worst case scenario you may have to do a clean wipe with odin and flash the stock ROM to start the process over. We can try to help you with any issues you may have but in the mean time try searching to the forum to find answers to these questions.
Click to expand...
Click to collapse
I used the one step root process I found here to install CWM 2.5.1.0. I then downloaded the ROM, copied it to my SDcard, then used CWM to install the zip from my sdcard.
I don't know what modem I have, is there a way to check with my phone in it's current state?
I installed CWM previous to transferring the rom to my sd card
I did not the first time, but per instructions on the page where I downloaded the ROM, I reformatted my sd card, redownloaded the ROM, wiped everything 3x's and tried to reinstall. Same result. I keep getting the error on just about everything I do that states "E:Can't open /cash/recovery/log"
And thank you for your advise, any more would be greatly appriciated. I did search the forum, but there is so much information, hard to find what I really want, especially as a novice. I plan to not be a novice for long thanks to xda!
mercerma said:
I used the one step root process I found here to install CWM 2.5.1.0. I then downloaded the ROM, copied it to my SDcard, then used CWM to install the zip from my sdcard.
I don't know what modem I have, is there a way to check with my phone in it's current state?
Click to expand...
Click to collapse
I could probably answer that question, im still a noob, but from what i know u need to install CWM version 3.0.5/6 in order for u to run does roms, thats why ure having trouble flashing it, since Syndicate roms are EXT4 Base Roms anything lower then CWM3 wont support since they are RFS files, go here and follow the steps
http://forum.xda-developers.com/showthread.php?t=976194
download the CWM3 and root it again, u can run the CWM Root over the previous 1 so dont worry, i did it that way and i had no problems what so ever, as to check to see what modem u had, go to settings, about phone, under base band version check to see if the last 4 letters says EB13, or DK28, or if u have the ECO5 which is the newest stock base update that came out.
Also its best to know if ure phone is from stock, or if u updated from any of the first 2 version updates, EB or DK, if u where like me that waited for the update and stayed at Eclair then updated when the ECO5 OTA came out then u should be fine....
Just incase u are from a update of EB or DK here is the link for does 2 versions of CWM3
http://forum.xda-developers.com/showthread.php?t=897612
if im wrong then someone please correct me im still a noob learning.
EDIT: just noticed that u said ure phone is messed at that point, umm u can try to do a factory reset then restart ure phone see if that fixes the problem, then try follow the steps above, if that doesnt work, u will have to download odin, which is also in that link and reflash back to stock, everything is there so if u follow does instrunctions u wont have a problem.....its actually pretty easy.....

[Q] Evo bricked ?

I'm hoping I did not brick this thing because I literally just got it replaced because of screen issues and a blown speaker and broken usb port. Anyway, got the replacement home and wasted no time to use unrevoked 3 on it. Worked great. installed Fresh Evo Rom 4, installed perfect. Tested - working fine. Then I tried installing the Radio, Wimax, NV, and PRI updates. Radio and Wimax installed correctly. Went to install the NV and PRI updates and it just said installation aborted ( I was driving to pick up dinner for the family so I just let it run for a few minutes then checked on it). I then decided to just restart and start putting in my contacts and stuff. It restarted to a screen with a box and what looks like a droid jumping out of it. Removed the battery and tried again after a minute or so, same thing. Tried the VOL - and Power method to boot into Hboot, same screen. Removed my SD card per some instructions on here , same screen. Replaced the battery with another one I had per some people getting the same issue here , same thing. Frustrated I ate dinner and came back to it. Now it wont turn on at all. No charging LED light at all. Tried both batteries, one red and one black, no go. Doesnt boot at all and doesnt look like its charging. Am I royally f*kt ? Anyone have any ideas for me to try ?
From what you said...yes....I guess its time to plead ignorance and get another replacement
Sent from my nightly EVO
So what went wrong ? I've done this same method about 6 other times with my previous phone and friends phones with absolutely no problems. Any insight so this doesn't happen again ? I'm on my way through traffic to a sprint store to pick up another one and want to root it but not brick this guy too.
My guess would be that it was either interrupted or a bad install...I really couldn't tell you though
Sent from my nightly EVO
tayden812 said:
I'm hoping I did not brick this thing because I literally just got it replaced because of screen issues and a blown speaker and broken usb port. Anyway, got the replacement home and wasted no time to use unrevoked 3 on it. Worked great. installed Fresh Evo Rom 4, installed perfect. Tested - working fine. Then I tried installing the Radio, Wimax, NV, and PRI updates. Radio and Wimax installed correctly. Went to install the NV and PRI updates and it just said installation aborted ( I was driving to pick up dinner for the family so I just let it run for a few minutes then checked on it). I then decided to just restart and start putting in my contacts and stuff. It restarted to a screen with a box and what looks like a droid jumping out of it. Removed the battery and tried again after a minute or so, same thing. Tried the VOL - and Power method to boot into Hboot, same screen. Removed my SD card per some instructions on here , same screen. Replaced the battery with another one I had per some people getting the same issue here , same thing. Frustrated I ate dinner and came back to it. Now it wont turn on at all. No charging LED light at all. Tried both batteries, one red and one black, no go. Doesnt boot at all and doesnt look like its charging. Am I royally f*kt ? Anyone have any ideas for me to try ?
Click to expand...
Click to collapse
Whenever you flash a radio, NV, or PRI or something like that, when you first flash it, it then tells you that you need to reboot to complete the installation. When it reboots, you will see that odd screen, which will either be an arrow facing down with a phone, an arrow with a box, or some kind of a droid guy with a box or something. That is very important to not pull the battery during that phase (it's when it's actually writing the radio, or pri, or whatever), otherwise a brick is the result, 99% of the time. Never pull the battery during any kind of a radio flash whatsoever. As far as why it told you that the installation was aborted, I've got no idea on that one. Maybe the file you were trying to flash was corrupted, or something to that nature.
If you're sure the battery is charged up, yet you get no LED light when the phone is powered down and plugged in, the phone won't boot to the bootloader, and seems completely unresponsive, then you are most likely indeed bricked. Sorry for the bad news. Don't pull the battery during any kind of a flash, especially a radio, pri, wimax, hboot, recovery flash etc. Battery pull during flashing of important things = bad idea.
EDIT: after thinking about it for a few minutes, after you updated your radio and wimax (which you said updated successfully), did you complete the installation by rebooting? After you flashed the radio, did you reboot, and see the black screen with an arrow coming out of a box, or something like that (that screen varies based upon your hboot version or recovery version)? If not, and you just tried flashing all of them, one after the other, without rebooting inbetween each one...then that may be why the installation of the pri aborted. Then when you went to reboot, it tried to finish the installation of the radio and wimax (which if you didnt reboot initially after selecting to flash, those installations would not have been complete, so as soon as you tried to reboot, it'd have tried to finish writing the radio image, which appears to be where you pulled the battery out)
If I remember right, that screen is part of the radio update. After it flashes, when you reboot you will see that screen. You're supposed to wait until it finishes and it should send you back to the recovery screen. After that you can reboot into the rom.
I'm scratching my head though because you said the installation aborted. Maybe part of it flashed successfully but the rest didn't?
EDIT: Didn't see that the radio flashed successfully. If you can still get to that screen, letting it run it's course should eventually solve the problem.
EDIT 2: K2buckley beat me to the punch. At least I know I was right and not giving you wrong info. Sometimes it takes pulling the battery 20 or so times to actually brick the phone, so hopefully you can still recover.
My Evo + xda Premium App = This post.
Thanx for the quick responses. After the radio and wimax update it went back to the install from zip screen in clockwork. From there I ran the other update. I let it sit on that installation aborted screen as I was driving. I ran in , grabbed dinner, came back within 5 minutes and it was still on that screen. Thats when I figured I'd just put contacts and stuff after I remove the battery. Still didnt work. If I indeed "bricked" this phone, is there any way ANYONE can fix it ? HTC or otherwise ? BTW - I already bought a new phone. Just scared to root and stuff now. I mainly want root to put in ROMS that have better battery life. Although now I have 3 batteries for it because of this brick lol.
tayden812 said:
Thanx for the quick responses. After the radio and wimax update it went back to the install from zip screen in clockwork. From there I ran the other update. I let it sit on that installation aborted screen as I was driving. I ran in , grabbed dinner, came back within 5 minutes and it was still on that screen. Thats when I figured I'd just put contacts and stuff after I remove the battery. Still didnt work. If I indeed "bricked" this phone, is there any way ANYONE can fix it ? HTC or otherwise ? BTW - I already bought a new phone. Just scared to root and stuff now. I mainly want root to put in ROMS that have better battery life. Although now I have 3 batteries for it because of this brick lol.
Click to expand...
Click to collapse
Unfortunately, if its bricked there's nothing that can be done. Since it doesn't turn on, sprint wont be able to tell it was rooted. Just be sure your SD card is "clean", and take it to sprint. See what they say about it. I'd just tell them it wont turn on. Still under 1 yr warranty...
Sent from my PC36100 using XDA App
Great idea. Never even crossed my mind to take it back. I know if they know its rooted they wont touch it which is why I was hesitant to take it back. I'm gonna try that tomorrow, thanks.
BTW - Any suggestions as to a ROM and kernel for absolutely the best battery life without sacrificing any of the Evo's stock options ?
Again, thanks for all the help guys.

[Q] Constant Reboots...

Hello everyone. I have not been too particularly active here mainly because I have had no real reason to post. I give thanks when needed, but don't really post. Well, now I am having an issue that I genuinely cannot figure out. I recently dropped my phone and the digitizer cracked big-time. When I went to replace it, the connector for the ribbon cable broke. So instead of buying a new logic board, I just decided to buy a new Evo. However, I couldn't afford the approx. $600 for the "without a contract" price. So I went to a local Sprint dealer in my town and bought a factory refurbished Evo. Here is where the problems start.
I have been having reboots constant with this phone. I knew that there were some issues with the Evo randomly rebooting, but I have never seen something like this. It happens about every minute or so. Sometimes sooner. Sometimes I luck out and it doesn't reboot for a few hours. I notice that it does not reboot at all while it is in recovery, which is a great thing. I have tried multiple different ROMs and each one does it. I am completely out of ideas. I don't necessarily want to take it back, mainly because returning it to stock would be a pain. However, it is looking like I have to. Does anyone have any idea? It is obvious that it is not a bootloop, because I am able to actually get into the launcher. However, within a minute, it reboots. Can old radios cause it to reboot like this? It did this even with stock unrooted.
If any information is needed, please let me know. I really want to get this working without returning.
Thanks
StompySan
EDIT: It would seem that flashing my Nandroid backup of stock rooted seems to stop the rebooting issues. Could the ROMs I am installing be conflicting with the radios, causing it to reboot?
If I were you, without unrooting, I would flash the RUU for your phone. Then flash the pc36img for Amon Ra.
Before all that, I'd also back up your SD Card, then reformat it, so you are basically starting from scratch. A good idea, before you restore everything to your SD Card, but after you flash Amon Ra, is to partition it for EXT3. ( http://themikmik.com/showthread.php?5669-GUIDE-TUTORIAL-Apps2SD-Guide&highlight=partition+sdcard )
A lot of the ROMS now will take advantage of that. Once that's done, you can restore your SD Card backup to your phone.
Then I'd make a nandroid of that stock/rooted ROM, so you can always go back to it if you need to. When I nandroid, I backup everything except cache.
Figure out which ROM you want, put it on your card along with DT A2SD and the kernel you want to use. Make sure it's a kernel for the type of ROM you want, either AOSP or Sense. Personally, I keep the best rated kernel for each on mine.
Go to Wipe in Recovery and wipe everything, EVERYTHING, except the SD Card, then flash your ROM, and in the same recovery session, flash DT A2SD.
Let it boot up and let it settle in before you do anything. For me, that means once the screen shuts itself off.
Back to recovery, wipe Cache and Dalvik-Cache, then flash your kernel, reboot and let it settle in again.
THEN setup your Google accounts and preferences.
For me, I'd go back to recovery and nandroid that setup, before you've restored your apps, and make another nandroid, so you have one of your ROM's Base.
Then, reboot and see if the problem is fixed. If it is, restore your apps and see how it goes. If it starts rebooting, you know it's in your apps, so you can go back to the nandroid you made and start form there, installing a few apps at a time
Thanks for your reply HipKat.
I followed your tutorial step-by-step. However, after flashing A2SD and rebooting, it bootlooped (not like what I was getting, but an actual no boot logo bootloop). I am assuming that the ROM that I flashed didn't like the A2SD. So I restarted the tutorial, skipping the part where you flash the A2SD script. It seems like it is doing great now! I have no clue what I was doing wrong. I was using CWM. Maybe that was the problem. Could it have not been wiping it properly?
Thanks again for the quick response!
1.There are some roms that provides a CPU speed of 1.2G. With those roms and setcpu installed manually by myself, my evo rebooted just like yours. I don't know why, too.
But after I wipe everything(as HipKat said) and flash other rom, my evo 4g works just fine.
2. Before flashing new roms, wipe everything is absolutely required, otherwise strange problems will keep coming out.
What I comprehend is that flash roms on phone is like upgrading OS on your computer, you can't run windows7 with XP's configuration, right?
Hey HipKat, I've noticed that you advise people to wipe everything but the SD card in Amon Ra. You may want to note that wiping battery stats is only good if you have a full battery and plan on calibrating properly. If you wipe battery stats at 70%, your phone won't charge past 70% (thinking that it's full) unless you use an sbc kernel. Just something to keep in mind.
I'm not knocking your directions, you help a lot of people out. It's just something to think about.
Sent from my PC36100 using Tapatalk
plainjane said:
Hey HipKat, I've noticed that you advise people to wipe everything but the SD card in Amon Ra. You may want to note that wiping battery stats is only good if you have a full battery and plan on calibrating properly. If you wipe battery stats at 70%, your phone won't charge past 70% (thinking that it's full) unless you use an sbc kernel. Just something to keep in mind.
I'm not knocking your directions, you help a lot of people out. It's just something to think about.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
You're right! I keep overlooking that because I never flash unless I'm fully charged.
My mistake on those posts. Thanks!
I was still getting reboots after doing all of that. I thought it went away, but it didnt.
79x1 said:
1.There are some roms that provides a CPU speed of 1.2G. With those roms and setcpu installed manually by myself, my evo rebooted just like yours. I don't know why, too.
But after I wipe everything(as HipKat said) and flash other rom, my evo 4g works just fine.
Click to expand...
Click to collapse
This has to be it. I changed the speed to 1.15GHz in SetCPU and it has not done it since. Thanks!
EDIT: Well, it was OK, but it has started again. I have no clue why it is doing it again...
Maybe you should try some classic roms that don't require app2sd, like kings' kinged kingdom.
Before I partition my sd card, with shooter E3D and synerge, my evo also sometimes reboot, but not so frequently as yours.
And the CPU speed should be below 998MHz on my device (HW version:004)! Set your cpu frequency lower first, then try some other roms.
79x1 said:
And the CPU speed should be below 998MHz on my device (HW version:004)! Set your cpu frequency lower first, then try some other roms.
Click to expand...
Click to collapse
It doesn't matter what speed I set it to. I had it at 998 before and it still rebooted.
79x1 said:
Maybe you should try some classic roms that don't require app2sd, like kings' kinged kingdom.
Before I partition my sd card, with shooter E3D and synerge, my evo also sometimes reboot, but not so frequently as yours
Click to expand...
Click to collapse
I am going to flash Synergy real quick. I have already tried the following:
EVOlvedROM r3chargeD
Cyanogenmod
Are there any other ROMs I should try?
EDIT: I recorded a video of exactly what it is doing. I am currently encoding it. I will throw a YouTube link up soon.
Kings' Alliance is the steadiest rom i've ever used, without sense 3.0 though. If you don't mind you could try this:
http://forum.xda-developers.com/showthread.php?t=1180048
Here is the video of the rebooting problem. Sorry it is so long. It seems like the one time I want it to reboot it took forever for it to. lol.
79x1 said:
Kings' Alliance is the steadiest rom i've ever used, without sense 3.0 though. If you don't mind you could try this:
http://forum.xda-developers.com/show....php?t=1180048
Click to expand...
Click to collapse
I will try this ROM later tonight. I probably won't be able to reply tomorrow, because I have to work from 10AM to 10PM (I hate long days, lol), but will reply as soon as possible.
MIUI, for the win, man!
OK, I can pretty much confirm that it is a hardware problem. I have tried every ROM I can think of. It always seem to restart when it tries to turn on the Mobile access. If it is connected to WiFi, it will not reboot. The moment it is disconnected, it starts. However, I know it is not because of a bad radio flash. I have tried re-flashing the radios and it still doesn't work. I have restored it completely back to stock (while keeping S-Off, naturally) and it still does it. So, I am going to be returning it tomorrow. However, I have one real quick question. I know how to unroot, but I am not sure on how to achieve S-On with the Revolutionary root. Can you just flash the Unrevoked S-On zip with this root, or is there a different method? I wasn't able to find anything out on this.
Thanks again for all of your help. I really can't believe how quick people on here replied.
It isn't your hardware, I had a similar issue on my phone, it wouldn't go past the evo screen (for hours), I updated my firmware and it worked.
Clear caches, flash this rom (supersonic_4.24.651.1_odexed-signed2 google it), it will update your firmware, then flash the rom you want on top of it
stompysan said:
OK, I can pretty much confirm that it is a hardware problem. I have tried every ROM I can think of. It always seem to restart when it tries to turn on the Mobile access. If it is connected to WiFi, it will not reboot. The moment it is disconnected, it starts. However, I know it is not because of a bad radio flash. I have tried re-flashing the radios and it still doesn't work. I have restored it completely back to stock (while keeping S-Off, naturally) and it still does it. So, I am going to be returning it tomorrow. However, I have one real quick question. I know how to unroot, but I am not sure on how to achieve S-On with the Revolutionary root. Can you just flash the Unrevoked S-On zip with this root, or is there a different method? I wasn't able to find anything out on this.
Thanks again for all of your help. I really can't believe how quick people on here replied.
Click to expand...
Click to collapse
You can flash S-On.zip directly from the recovery, I suggest you try out the method I mentioned in the previous post, before you go doing something drastic.
prometh1us said:
It isn't your hardware, I had a similar issue on my phone, it wouldn't go past the evo screen (for hours), I updated my firmware and it worked.
Clear caches, flash this rom (supersonic_4.24.651.1_odexed-signed2 google it), it will update your firmware, then flash the rom you want on top of it
Click to expand...
Click to collapse
Nonono, it goes past the Evo screen. It goes past the standard boot logo. However, once you are in the lockscreen, and it tries to connect to 3G, it reboots. It is not a standard no boot logo bootloop.
stompysan said:
Nonono, it goes past the Evo screen. It goes past the standard boot logo. However, once you are in the lockscreen, and it tries to connect to 3G, it reboots. It is not a standard no boot logo bootloop.
Click to expand...
Click to collapse
If you're gonna trade it in, you don't need to unroot. Chances are no one will ever know, as long as you have a stock ROM on there.
HipKat said:
If you're gonna trade it in, you don't need to unroot. Chances are no one will ever know, as long as you have a stock ROM on there.
Click to expand...
Click to collapse
Yeah. That's what I was reading. Plus, I rooted with Revolutionary, which doesn't have a method to enable S-On.
Last night I flashed the latest stock ROM. As soon as it booted up and got to the lockscreen, it restarted. I can't see it not being a hardware problem. I am going to return it today. Hopefully they don't notice that it is S-Off. Any suggestions on what to say if they do?
same issue
i have an old evo that is doing the same thing, i flashed the original ruu and it still does it. i just reported it lost.

[Q] Bricked GNex, tried everything, Flashing ROMS, Odin, Omap, nothing works.

TL;DR; version on the bottom.
Hi everyone. I'm long time user of xda, though I rarely post, because I've always found the solution for my android problems until today.
I've bricked many phones in the past and always managed to get them back up working, including my Galaxy Nexus that has been bricked easly over 10 times... possibly over 15.
Anyway, yesterday I was testing some Kitkat 4.4 stuff on my phone. my daily ROM as been paranoid android for a long time. since they were on 2.8 or something.
First I installed nexus 5 launcher on my gnexus because I really wanted to test the new google experience thing.
Then I thought it was a bit slow, and decided to install a full 4.4 ROM. ended up deciding I couldn't miss some of the paranoid android features and flashed my paranoid android rom back (3.99 RC2), installed the GEL (google experience launcher) installed xposed framework and put my device the way it was pretty much.
To make GEL a bit more faster and fluid I decided to overclock a bit (I've overclocked alot in the past up to 1900+ Mhz and never had problems though I know it's not healthy for the phone.)
I've overclocked it to about 1500... I just wanted to see how it would work and then turn it back to normal again.
I got distracted for some reason and forgot to turn it off (and I think it might have been that... something burned inside or something...)
At night I was checking something on the browser, and then the phone suddenly reboots, which happened in the past several times (people that flash alot should know).
the phone started boot looping on google logo and from my previous bricks I knew it was bricked and I did what I usually do.
Went to recovery mode, wiped everything expect internal storage, dalvik cashe, system, cashe and data.
tried flashing paranoid android and gapps, didn't work. Then proceeded to flashing stock rom, didn't work either.
From that point and from my previous bricks, I knew it was something more serious than just rom.
So then I did a odin flash, and I thought it would be fine after because odin never failed me before. I did odin flash, it did the google logo boot, and then started the boot animation from the stock rom and after 3 seconds looped google logo again followed by the stock nexus bootanimation (before it only looped the google logo boot).
I searched a bit on xda, and found this thing called OMAP (I used this post http://forum.xda-developers.com/showthread.php?t=2146790), which apparently is something you do when your phone has no software at all (for people that somehow mess their bootloaders and/or downloading modes )from what I understood.
I tried it out, it kind of worked I believe though I found odd that my device kept reconnecting to my pc as "omap4460 usb device" every 3 seconds.
After that I did a odin flash again and didn't work.
After all this I'm thinking that the problem is not software but hardware because of that little overclock I did and forgot to undo.
Any help would be appreciated.
TL;DR; Version:
Was running paranoid android 3.99 RC2, installed the new GEL (google experience launcher);
Overclocked a bit to make GEL faster but intended to put the clock speeds to normal after;
Forgot to set the clock speeds to normal (though I'm not 100% sure that's what messed my device);
At night while using the browser the device rebooted and got stuck in google logo bootloop.
wiped everything except internal storage and flashed paranoid android, didn't work, flashed stock rom, didn't work either;
Did a odin flash, device appeared to boot, at least got over google logo boot, and started the stock bootanimation, but kept looping that.
Did OMAP (I don't know the right term for this... OMAP flashing? I don't think that's correct)thing to see if would fix the phone, then odin flash again but didn't work.
Any help would be appreciated
How do you did the OMAP Flash works? My problem is little same, but i cant enter to download, recovery or fastboot mode, and I read the OMAP can help me, but when I star the process of OMAP my GN don't change anything, and in the OMAP says the process is finish :C!
Do you know something about this? :C
make sure your pc can detect ur device.. as omap ( if not try plugged off your battery)
1. run the omap4460_tuna.bat
2. plug in ur phone without battery..
3. when, the mapflash detect a device, plug-in the battery.
4. your gnex will go to bootloader page..
5. then can restore anything thru odin or nexus toolkit
try this step first..
sorry for my bad english
galaxy nexus i9250
How did u get into 1.9Ghz+ clock, the Ezekeel's Glados for 4.2.2 only had that much of clock speed step (though Np could'nt handle that), and Trinity had only till 1.8Ghz max !
did u try the original fastboot google stock JWR66Y image flashing by erasing all partitions and then re-flashing ??
Though this one looks like a very serious issue....
Bl4ckB1rd7 said:
How do you did the OMAP Flash works? My problem is little same, but i cant enter to download, recovery or fastboot mode, and I read the OMAP can help me, but when I star the process of OMAP my GN don't change anything, and in the OMAP says the process is finish :C!
Do you know something about this? :C
Click to expand...
Click to collapse
The omap only use is to get the bootloader back in case you mess it up somehow (which was stupid in my case since mine was working to begin with but I did it anyway).
Follow exactly what is in that link and after that you should have your bootloader back..
After you do it you should be able to get into fastboot and download mode and then, odin flash your phone and get it back operational.
Ashtrix said:
How did u get into 1.9Ghz+ clock, the Ezekeel's Glados for 4.2.2 only had that much of clock speed step (though Np could'nt handle that), and Trinity had only till 1.8Ghz max !
did u try the original fastboot google stock JWR66Y image flashing by erasing all partitions and then re-flashing ??
Though this one looks like a very serious issue....
Click to expand...
Click to collapse
it was a long time ago, about 6 months, maybe more, with one of Experimental Ak kernels... it was called ak pirate or something I believe.
It couldn't handle that speed for too long though. I never tested it to the limit because whenver I thought the phone was getting way too hot I put it back on normal values inb4 it became a toaster powered by android lol.
Anyway, imo gnex clock speed won't afftect too much your performance... what I needed on it was more ram, not really speed.

Categories

Resources