Related
I have been rooted for a while now and had bakedsnack 1.4 installed for about 2 months now. Everything was stable until a few days ago when it started rebooting randomly then much more often so I decided it was to time to update...went for Ava v9. After reseting factory defaults, wiping cache, wiping dalvik, I installed the rom. Immediate infinite loop reboot, tried this rom 2 more times then the newest baked snack then the plain rooted stock. All are infinite reboot loops...I have wiped numerous times now and can't seem to find a problem, I have updated my radios and everything trying to fix this to no avail. I could really use some help...here is a catlog of my bootup and 2 of the infinite reboots after a clean install.
pastebin.com/jBub3Upf
Also using amon-ra recovery and my root is full nand unlock.
same thing is happening to me. plz help. ava v9 running both stock kernel and kings 10 cfs. plz help. plz. i have the exact same problem. plz. i am bagging you. plz.
plz.
dk
Have you guys tried running a stock PC36IMG? That is the first thing I would try if I was in your shoes.
link to file: http://forum.xda-developers.com/showthread.php?t=791019
_MetalHead_ said:
Have you guys tried running a stock PC36IMG? That is the first thing I would try if I was in your shoes.
link to file: http://forum.xda-developers.com/showthread.php?t=791019
Click to expand...
Click to collapse
i have tried unrooting and rerooting, but not flashing a stock pc36img.zip. thanks for the link. megafileupload is wired do you mind sending me a mirror? i will post results. if that doesnt work, i am unrooting nd trying again. if that still doesnt work, i am bricked
dkdude36 said:
i have tried unrooting and rerooting, but not flashing a stock pc36img.zip. thanks for the link. megafileupload is wired do you mind sending me a mirror? i will post results. if that doesnt work, i am unrooting nd trying again. if that still doesnt work, i am bricked
Click to expand...
Click to collapse
devs, i'm not sure you get how serious this problem is, and how badly it needs fixing. i reboot any time i open a network connection. for example, when i boot up, even before htc sense loads, i reboot. i cannot stay up for more than 15 seconds. i have forcefully deleted all apps that even remotely might require data, and still somehow, i sync to my voicemail. boot up, pull down lock, reboot, stuck. plz help me i want to be able to use my phone.
dkdude36 said:
i have tried unrooting and rerooting, but not flashing a stock pc36img.zip. thanks for the link. megafileupload is wired do you mind sending me a mirror? i will post results. if that doesnt work, i am unrooting nd trying again. if that still doesnt work, i am bricked
Click to expand...
Click to collapse
Have you been able to get it downloaded? I just tried to dl it from megaupload again and it worked no prob.
Downloading it now, will try it out. Thanks!
download went fine. about to push and flash. wish me luck... i just want my evo back waaaaa
flashed it. first try, boot failed because of a pu fail. stuck in bootloader. tried agian, and worked fine. my phone is rebooting as we speak. lets see if it worked...
and the big question: should i stick with ava v9 or what other rom should i try? i have never tried fresh, and cyanogen is too unstable for me. i have pretty much only tried ava, omj, and cm. plz recommend the must tries etc. i'm not asking you to choose for me, just tell me what to try.
dk
SHOOT IT STILL WONT WORK! i booted just fine, and was able to set up just the google account. the second i hit finish for the google account only and it tried to sync contacts, reboot. please help me knowledgable people!
EDIT: once i rebooted, i dragged down unlock screen and BAM! reboot... sad me i just want my evo back
dkdude36 said:
flashed it. first try, boot failed because of a pu fail. stuck in bootloader. tried agian, and worked fine. my phone is rebooting as we speak. lets see if it worked...
and the big question: should i stick with ava v9 or what other rom should i try? i have never tried fresh, and cyanogen is too unstable for me. i have pretty much only tried ava, omj, and cm. plz recommend the must tries etc. i'm not asking you to choose for me, just tell me what to try.
dk
Click to expand...
Click to collapse
I had the EXACT same problem as you. Was the PU fail next to the boot line during the update? If so, then I think you've got bad blocks in your boot partition and I hate to say it but you might not be able to flash any custom kernels anymore. Once I finally got mine booted, the only kernel that worked was a stock one. I was able to flash Fresh, but HAD to keep the kernel stock. I ended up calling Asurion and filed a claim. Got my new evo today and am having no issues.
SHOOT IT STILL WONT WORK! i booted just fine, and was able to set up just the google account. the second i hit finish for the google account only and it tried to sync contacts, reboot. please help me knowledgable people!
EDIT: once i rebooted, i dragged down unlock screen and BAM! reboot... sad me i just want my evo back
Click to expand...
Click to collapse
That sucks man. Do what I did, file an insurance claim and get a new phone. They ship it out next day.
same problem I'm having:
http://forum.xda-developers.com/showthread.php?t=808280
ok i think i finally have it. but now, what rom to use? please tell me. i might be going with the cm nightlies. but plz give your opinion. thanks for the stock pc...zip. tweetqit, thanks for letting me overrun your thread..ha
TO GET IT TO WORK, ONCE YOU ARE STUCK IN BOOTLOADER, JUST RE-UPDATE AND THE BAD BLOCKS WILL GO AWAY. OR AT LEAST THAT WORKED FOR ME.
Yup, failed for me the first time but worked the second. My phone was never the same after I went through that ordeal. No custom kernels worked, terribly sluggish performance, constant reboots. That's why I said f*ck it and had Asurion send me a new one.
dkdude36 said:
ok i think i finally have it. but now, what rom to use? please tell me. i might be going with the cm nightlies. but plz give your opinion. thanks for the stock pc...zip. tweetqit, thanks for letting me overrun your thread..ha
TO GET IT TO WORK, ONCE YOU ARE STUCK IN BOOTLOADER, JUST RE-UPDATE AND THE BAD BLOCKS WILL GO AWAY. OR AT LEAST THAT WORKED FOR ME.
Click to expand...
Click to collapse
what'd you do? what exactly did it fix? everything?
On first try, boot: fail-PU. I guess this is a common problem? pretty lame. Will post after I try again.
Ok so now that, that failed..how do I try it again? when I reboot into recovery it just checks the PC36IMG.ZIP and dumps me back to the bootloader without asking me to install it...
I've done what I think dkdude36 did [install PC36IMG] and did get PU fail, and now i'm stuck in HBOOT/BOOTLOADER as expected. Now I only have the few options in bootloader and don't know what to do. I've rebooted and gotten the bootloops then wen't back into bootloader and it loads PC36IMG but it doesn't give me the option to update again. Am I supposed to do something in order for it to give me that option again? If so, what? As of now, I'm stuck and am bricked (hopefully not permanently).
Tweeqit2 said:
Ok so now that, that failed..how do I try it again? when I reboot into recovery it just checks the PC36IMG.ZIP and dumps me back to the bootloader without asking me to install it...
Click to expand...
Click to collapse
what if we run:
fastboot erase boot
fastboot erase recovery
what will happen? will it prompt me to update with PC36IMG.zip as it did the first time?
Hey everyone,
Hopefully someone can help me with this situation. I haven't been able to find relevant information yet.
I'm currently running a Rooted Incredible with the latest Virtuous ROM. I'm trying to flash back to the stock .17 kernel from HTC, but ANY kernel I flash onto it causes the screen to load up as far as the red eye, stall and then reboot causing a constant loop. The only way I can get beyond this so far is just flashing my recovery image. I've installed from ROM manager and checked to wipe data/cache (backed up before of course!) and have even booted into recovery manually and flashed from the download folder and the actual zip file. Before that I've wiped data and dalvik cache. I can't figure out what I'm missing here. Any suggestions??? I hope I haven't crippled my Droid by doin this.
DL the new stock kernel to pc mount card to pc put the new kernel somewhere you'll remember then reinstall sdcard and try flashing the kernel that way if you haven't already
Sent from my ADR6300 using XDA App
Hypcrsy said:
Hey everyone,
Hopefully someone can help me with this situation. I haven't been able to find relevant information yet.
I'm currently running a Rooted Incredible with the latest Virtuous ROM. I'm trying to flash back to the stock .17 kernel from HTC, but ANY kernel I flash onto it causes the screen to load up as far as the red eye, stall and then reboot causing a constant loop. The only way I can get beyond this so far is just flashing my recovery image. I've installed from ROM manager and checked to wipe data/cache (backed up before of course!) and have even booted into recovery manually and flashed from the download folder and the actual zip file. Before that I've wiped data and dalvik cache. I can't figure out what I'm missing here. Any suggestions??? I hope I haven't crippled my Droid by doin this.
Click to expand...
Click to collapse
You should not be wiping data when flashing a new kernel.
How does that differ from flashing it from recovery if I may ask? I figured I had done everything properly and even after just going to recovery, wiping dalvik, wiping data then flashing I keep getting the issue.
I'm actually at work at the moment and don't have access to my PC to download it. But I'll give it a shot when I get home. Luckily flashing my recovery image works just fine, I'm just stumped why now it wants to cause me grief.
Hypcrsy said:
How does that differ from flashing it from recovery if I may ask? I figured I had done everything properly and even after just going to recovery, wiping dalvik, wiping data then flashing I keep getting the issue.
I'm actually at work at the moment and don't have access to my PC to download it. But I'll give it a shot when I get home. Luckily flashing my recovery image works just fine, I'm just stumped why now it wants to cause me grief.
Click to expand...
Click to collapse
At the most, you should be wiping dalvik. You should not be wiping data when flashing a kernel. Doing so will result in the self-inflicted grief you're experiencing.
najaboy said:
You should not be wiping data when flashing a new kernel.
Click to expand...
Click to collapse
Sorry I just saw this post immediately after I replied. I thought wiping data applied for both flashing ROMS and kernels.
najaboy said:
At the most, you should be wiping dalvik. You should not be wiping data when flashing a kernel. Doing so will result in the self-inflicted grief you're experiencing.
Click to expand...
Click to collapse
^This. Only wipe dalvik, not data.
Ok I'll give it a shot while I'm here. I was flashing over to the new edition of Kings and it just became incredibly unstable when interacting with SetCPU, so I was just going to go back to the stock HTC one, that's when I got the first constant bootloop. I'll give it a shot and let you guys know what happens. Thanks for the feedback.
Yeah the reload worked this time, I don't know why it was giving me such an issue when I could have sworn it was working ok every other time I've done it before. Any reasons why I'd be getting such a hard time from Kings Kernel 6? I've seen so many rave reviews with it but everytime I have it on my phone it lasts me about ten minutes and then goes back to that same constant boot cycle.
Hypcrsy said:
Yeah the reload worked this time, I don't know why it was giving me such an issue when I could have sworn it was working ok every other time I've done it before. Any reasons why I'd be getting such a hard time from Kings Kernel 6? I've seen so many rave reviews with it but everytime I have it on my phone it lasts me about ten minutes and then goes back to that same constant boot cycle.
Click to expand...
Click to collapse
thats weird anyone else having that problem? haven't tried 6 yet
Sent from my ADR6300 using XDA App
You only need to wipe dalvik if going to and from one with HAVS, but it doesn't hurt to be safe.
Sent from my ADR6300 using XDA App
Thanks for the assistance everyone. I finally got the darn thing stable. But I'm still curious about the kings kernel 6. I was stoked to try it because I was hoping it would be stable. I was having that instability issue with 5. Anyone else know what I'm talking about???
Sent from my rooted Droid Incredible!!
Hypcrsy said:
Thanks for the assistance everyone. I finally got the darn thing stable. But I'm still curious about the kings kernel 6. I was stoked to try it because I was hoping it would be stable. I was having that instability issue with 5. Anyone else know what I'm talking about???
Sent from my rooted Droid Incredible!!
Click to expand...
Click to collapse
Not exactly. I was running 5 on SkyRaider 3.3.2 for a while, then all of a sudden I started having horrible lag while unlocking the phone and for about 7-10 seconds afterwards. Is this what you're referencing? When I switched to BFS6, I didn't have the problem. But the problem did kick in a while after install of 5 (few weeks), I didn't have 6 that long. 6 seemed pretty solid. Give 6 a shot, if you don't like it, just flash something else. Nandroid just to be safe, too.
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS4.
Yeah I always nandroid just in case when I do any serious modification, but I was experiencing the same issue with 6 as I was with 5. Just checking the different limits with SetCPU, anytime I went over 1.1 for overclocking the phone would stay on for about 15-20 seconds and then reboot, get as far as the red eye and then reboot again. That was as far as I ever got with his kernels which is unfortunate.
When testing SetCPU and overclocking, make sure you don't have set on boot enabled.
Sent from my ADR6300 using XDA App
Thanks I'll give it a shot later on.
recently, my phone has just started a habit of randomly rebooting. i was using myn rls5 with net kernel 4.3.2, but i decided to try something different in an attempt to stop the problem, so i went to mikfroyo with its default kernel. right after i startthe phone and it gets to the homescreen, it starts restarting again. i cleared data and cache between roms, and im using clockworkmod 3.0.0.5
You should always perform a full wipe, to include factory/data, when flashing a new rom.
teh roxxorz said:
You should always perform a full wipe, to include factory/data, when flashing a new rom.
Click to expand...
Click to collapse
i did. every time
ryohei47 said:
i did. every time
Click to expand...
Click to collapse
Also, the dalvik, under advanced? And not flashing a kernel with it?
I found out that Clockwork never cleared Dalvik for me. I changed to AR and after clearing the dalvik I stopped getting reboots or bootloops. Maybe your phone doesn't like the new Clockwork...
Shigster said:
I found out that Clockwork never cleared Dalvik for me. I changed to AR and after clearing the dalvik I stopped getting reboots or bootloops. Maybe your phone doesn't like the new Clockwork...
Click to expand...
Click to collapse
that could be it. everytime i install RA though, it complains and doesnt boot into recovery correctly
oohhh. that sucks. try unrooting or using a stock rom for a while. if it keeps rebooting when you browse the web, play games, anything that works the phone, then there is nothing you can do. the phone is fried. wait until it is bad enough that you can do it whenever you want by firing up a game and playing for a few minutes. then bring to the sprint store and they will replace. hah why do i have to be the person who brings the bad news?
again, try unrooting first. you can even leave s-off to re root easily. if you have no reboots, then the problem can be fixed.
i feel so bad giving this news... hah
My phone recently started doing this. Doesn't matter what ROM I'm on, doesn't matter if I un-root with a factory RUU or re-root, doesn't matter what recovery I use, doesn't matter if I completely format my SD card or boot without one. It got to the point I had to take it to Sprint and have them order me a new one.
It would randomly reboot and then go into a bootloop that not even a factory reset would cure, just decides when to stop bootlooping on its own and occasionally works.
ryohei47 said:
that could be it. everytime i install RA though, it complains and doesnt boot into recovery correctly
Click to expand...
Click to collapse
If you're using ROM Manager, don't! Download the PC36IMG.zip file from amon's thread and place it on the root of your SD card. Shutdown your device. While pressing the down arrow key, press the power button. You will then enter the bootloader screen. After a few seconds, a few lines of text will appear and the bootloader will automatically detect the. PC36IMG.zip file and prompt you to install it. Follow the prompts to install. The installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. The recovery version will be listed at the bottom of the screen. Go to the wipe menu and wipe EVERYTHING except the SD card itself then go to the flash menu and flash whatever rom you wish to flash.
Posting & replying via the XDA Premium app
awesomeindeed said:
My phone recently started doing this. Doesn't matter what ROM I'm on, doesn't matter if I un-root with a factory RUU or re-root, doesn't matter what recovery I use, doesn't matter if I completely format my SD card or boot without one. It got to the point I had to take it to Sprint and have them order me a new one.
It would randomly reboot and then go into a bootloop that not even a factory reset would cure, just decides when to stop bootlooping on its own and occasionally works.
Click to expand...
Click to collapse
Were you one of the unlucky ones who were using CM7 when the bootlooping began?
Posting & replying via the XDA Premium app
dougjamal said:
Were you one of the unlucky ones who were using CM7 when the bootlooping began?
Posting & replying via the XDA Premium app
Click to expand...
Click to collapse
No, I had already moved away from CM7 when it began. It started out of nowhere and just got worse on a daily basis.
I had also never used Unrevoked. I rooted with toast's original root method way back last August or so and was using the .76 ENG bootloader.
I had similar issues, in terms of both posts, and it got to the point that I just got it replaced from Sprint. It just progressively got worse no matter what was done. Has happened to others ... sounds like the phone might just be going.
=(
sent from my
My new phone arrived today. It's a refurb. HW 0003. Made it about 2 hours without a random reboot. Made it about another 4 before doing it again. This sucks.
awesomeindeed said:
My new phone arrived today. It's a refurb. HW 0003. Made it about 2 hours without a random reboot. Made it about another 4 before doing it again. This sucks.
Click to expand...
Click to collapse
Damn, that sucks. Is that stock, before u even rooted it? I would just take it right back to Sprint.
Sent from my PC36100 using XDA App
k2buckley said:
Damn, that sucks. Is that stock, before u even rooted it? I would just take it right back to Sprint.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yep, stock. Only apps installed are GoSMS and XDA. I guess I'll give it a factory reset and see if that fixes it, or else it's going back.
awesomeindeed said:
My new phone arrived today. It's a refurb. HW 0003. Made it about 2 hours without a random reboot. Made it about another 4 before doing it again. This sucks.
Click to expand...
Click to collapse
umm... might have been one of the 2 i got with that problem... srry!
i just hate unrooting, the whole process will end up taking a few hours. im probably gonna unroot, and if the basics work, i'll just stick with some simple z4 root and call it a day. any other options? cause htis is already my second phone, not exactly crazy about getting a third.
ryohei47 said:
i just hate unrooting, the whole process will end up taking a few hours. im probably gonna unroot, and if the basics work, i'll just stick with some simple z4 root and call it a day. any other options? cause htis is already my second phone, not exactly crazy about getting a third.
Click to expand...
Click to collapse
Unrooting take like 5 minutes...flash s-on tool, then the 5 minutes to run the ruu, then another 5 minutes to re-root.
ryohei47 said:
recently, my phone has just started a habit of randomly rebooting. i was using myn rls5 with net kernel 4.3.2, but i decided to try something different in an attempt to stop the problem, so i went to mikfroyo with its default kernel. right after i startthe phone and it gets to the homescreen, it starts restarting again. i cleared data and cache between roms, and im using clockworkmod 3.0.0.5
Click to expand...
Click to collapse
My phone never has random reboots. Never. And I have a list of roms as long as my arm that I have flashed.
HipKat said:
My phone never has random reboots. Never. And I have a list of roms as long as my arm that I have flashed.
Click to expand...
Click to collapse
There are a bunch of bad EVOs floating around. If you have this problem, you're more likely to get one of these as a refurb as they are the ones they get back. They'll replace the display, etc. But its the mobo that is probably the issue, and they don't replace that. They probably just make sure that it boots up and can make a call..
Sent from my PC36100 using Tapatalk
hey, new user here, don't know if this has come up before but i did a search and haven't found anything that has the same particulars as i do.
recently my phone hasn't been responding to power button or home button wake up, intermittently. freezes up sometimes and some apps force close more than usual. then the other day, my phone died on me (full battery discharge) and when i finally got around to charging it, it charged fully but it wouldn't turn on past the Samsung boot logo, and gets real hot while doing so.
Also, the samsung boot logo appears before the AT&T splash screen tone starts.
im running stock Rooted 4.1.2 with the latest perseus kernel version.
any suggestions? i havent made a nandroid in a couple weeks, so my preferred route would be without a data wipe.
i can still access CWM recovery, btw.
well damn wheres the help?
I would download the stock rom and flash it again. If that doesnt work, custom rom time. I honestly cant see this problem getting fixed without a data wipe though good luck and keep me posted.
Sent from my X501_USA_Cricket using Tapatalk 2
With the non-response issues you describe, and the fact that you are seeing multiple force closes on the device....start with a wipe of the cache and dalvik cache in recovery.
It sounds as if the device is having cache file management issues, and trouble within the file structure.
While I dont think you have any hardware issues, it does sound like the software is suffering for one reason or another, and a base cleaning of the caches may help.
If no improvement is seen after cache cleaning, then we move to the data next.
I realize you want to keep your data intact, but if corruption has occured, you will have no choice but to factory restore the device and test again.
Try the cache cleaning first, then boot and test....
Beyond that...as the above poster states...a fresh install may be needed....g
Before a data wipe try reinstalling the kernel, and also try dirty flashing the Rom.
Not sure I would recommend a dirty flash to him. Plenty of times the result for users has been bad. Though as stated above yours, It does appear to be a file system error. He is probably right and I should have thought about wiping the dalvic cache first.
Sent from my X501_USA_Cricket using Tapatalk 2
i was afraid this would happen....
tried wiping both caches with no new results.
ive read that dirty flash has had mixed results. if i can at least get the OS booted so that i could backup what i need to, that would be a good thing.
im thinking its a kernel issue, since the phone gets real hot while stuck on the samsung screen. could i be right?
thanks guys:good:
i also tried reinstalling the kernel through cwm recovery, nothing new
FIXED
did a data/factory reset from recovery. it kept everything! thank god for cloud backups. Google is the JOINT!! i even kept my kernel and root, and at&t backed up my texts and calls....thanks everybody for the help, i really appreciate it!
its still kinna hot though...turned it off to let it cool down and see what happens when i start it back up....will keep posted if anything
Great. Know I didnt help too much but glad you got it worked out. :thumbup:
Sent from my X501_USA_Cricket using Tapatalk 2
DroidOblivion said:
did a data/factory reset from recovery.
Click to expand...
Click to collapse
Great news ....
Data corruption is so very easy to get.
As we mix and match pieces of code, those issues do arise.
Sadly, the causes are often elusive.
But the plan "B" wipe generally does the trick, as is the case here.
Happy flashing....g
So the last few times I've flashed some roms I've noticed the phone would get hung up on the clear cache and wipe option in CWM. Eventually it would (maybe 5 mins) do it's thing and be fine. As of today, no bueno. All I can do is go into CWM. It won't do anything without locking up after that point. If I just do a regular reboot, it's stuck on the HTC screen. Now I get the attached error messages in CWM.
UPDATE- It's currently acting like it is restoring one of my backups, they usually take an hour.
aviris said:
So the last few times I've flashed some roms I've noticed the phone would get hung up on the clear cache and wipe option in CWM. Eventually it would (maybe 5 mins) do it's thing and be fine. As of today, no bueno. All I can do is go into CWM. It won't do anything without locking up after that point. If I just do a regular reboot, it's stuck on the HTC screen. Now I get the attached error messages in CWM.
UPDATE- It's currently acting like it is restoring one of my backups, they usually take an hour.
Click to expand...
Click to collapse
If it takes an hour to restore a back up you should maybe look at TWRP...5-7 minutes tops. I'm not sure it's always like that with CWM, but it maybe be something for you to check out.
Sent from my HTC6500LVW using Tapatalk
Twrp is definitley much faster at backing up and restoring. I would try reflashing cwm or flash twrp and see if that solves the issue.
Happen to have a link? I'm a creature of habit and really hate changing things but CWM has really not been doing well lately.
aviris said:
Happen to have a link? I'm a creature of habit and really hate changing things but CWM has really not been doing well lately.
Click to expand...
Click to collapse
Someone else posted about the same issue as yours in the cwm thread...
Try this..
http://forum.xda-developers.com/showthread.php?t=2416431
Sent from my Nexus 7 using Tapatalk