Develop Bugs

all Roms lead to random reboots

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

[Q] Boot loop issues on various ROM's

I don't know what to do. I'm having this issue with a couple ROM's.
First happened after installing the latest version of Baked Snack (2.3 - EB13-based). Flashed according to instructions, ran fine for a few days, started acting a little laggy one day so I shut it down and started it back up. Once it started back up, it started boot looping. Only thing that worked was to wipe and start over.
I thought it might be a no-journaling data corruption thing, so I decided to try the journaled version of midnight 5.1 (which I think is based off of Bonsa 4.0.1). Used odin to go back to stock, rooted with cw3.0.0.6/ext4, etc. flashed ROM according to instructions. Again worked great for a few days, then after shutting my phone down tonight and restarting it a few minutes later, boot loops. Reverting to an earlier nandroid backup worked, and I'm assuming wiping and reflashing would work, but I gotta get to the bottom of this.
What's baffling to me is that everything works fine for a few days. I'm shutting the phone down normally, I'm not doing anything strange before shutting down. In both cases I was using setCPU, but with very conservative settings (200min 1000max, conservative or on demand). I can't think of what else I may be doing to cause these problems.
Anyone else run into this?

rsage said:
I don't know what to do. I'm having this issue with a couple ROM's.
First happened after installing the latest version of Baked Snack (2.3 - EB13-based). Flashed according to instructions, ran fine for a few days, started acting a little laggy one day so I shut it down and started it back up. Once it started back up, it started boot looping. Only thing that worked was to wipe and start over.
I thought it might be a no-journaling data corruption thing, so I decided to try the journaled version of midnight 5.1 (which I think is based off of Bonsa 4.0.1). Used odin to go back to stock, rooted with cw3.0.0.6/ext4, etc. flashed ROM according to instructions. Again worked great for a few days, then after shutting my phone down tonight and restarting it a few minutes later, boot loops. Reverting to an earlier nandroid backup worked, and I'm assuming wiping and reflashing would work, but I gotta get to the bottom of this.
What's baffling to me is that everything works fine for a few days. I'm shutting the phone down normally, I'm not doing anything strange before shutting down. In both cases I was using setCPU, but with very conservative settings (200min 1000max, conservative or on demand). I can't think of what else I may be doing to cause these problems.
Anyone else run into this?
Click to expand...
Click to collapse
Sounds like you got everything covered. The only thing I can think of is do you have a lot of apps on your SD card? Could be the card is starting to get corrupted. Backup everything on the card to a computer and reformat the card and restore the data.

kennyglass123 said:
Sounds like you got everything covered. The only thing I can think of is do you have a lot of apps on your SD card? Could be the card is starting to get corrupted. Backup everything on the card to a computer and reformat the card and restore the data.
Click to expand...
Click to collapse
Thanks I'll try that. The first time, I did have a ton of apps on the sd card. Second time, I didn't really reinstall many apps because I was a little gunshy from what happened, then it happened again anyway. I'll try this tonight.

rsage said:
Thanks I'll try that. The first time, I did have a ton of apps on the sd card. Second time, I didn't really reinstall many apps because I was a little gunshy from what happened, then it happened again anyway. I'll try this tonight.
Click to expand...
Click to collapse
Formatting your SD card is always a good step when ROMs don't seem to flash right.
Also, Baked Snack is not/will never be supported here.

k0nane said:
Formatting your SD card is always a good step when ROMs don't seem to flash right.
Also, Baked Snack is not/will never be supported here.
Click to expand...
Click to collapse
Thanks k0nane, reformatting as I type this, hopefully this works as I'm out of ideas.
And yes, wasn't asking for support for BS, but for a general issue I'm having with all ROM's at the moment. From now on if I ever have to refer to that ROM, I will call it "the ROM that shall not be named"...

rsage said:
Thanks k0nane, reformatting as I type this, hopefully this works as I'm out of ideas.
And yes, wasn't asking for support for BS, but for a general issue I'm having with all ROM's at the moment. From now on if I ever have to refer to that ROM, I will call it "the ROM that shall not be named"...
Click to expand...
Click to collapse
While you are working on your phone, if you are going to stick with midNIGHT, I suggest you move to 5.2, 5.1 was a little goofy for some and 5.2 seems to have fixed any issues it had.

budderocks said:
While you are working on your phone, if you are going to stick with midNIGHT, I suggest you move to 5.2, 5.1 was a little goofy for some and 5.2 seems to have fixed any issues it had.
Click to expand...
Click to collapse
I'd love to, but the 5.2 update is only available for the no journaling version

rsage said:
I'd love to, but the 5.2 update is only available for the no journaling version
Click to expand...
Click to collapse
You are in luck, it is updated now. I believe he is uploading it as I type this
Sent from my SPH-D700 using XDA App

budderocks said:
You are in luck, it is updated now. I believe he is uploading it as I type this
Click to expand...
Click to collapse
Yep, XDA thread not updated yet but I see the upload on his site, thanks for the heads up! Hopefully the card reformat and ROM update will resolve the situation.

[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.

Undo ICS leaked firmware

Is there a way to undo the leaked ICS firmware I've flashed? I've been hit with the post viper CM10 lag that seems to be going around and I thought I'd try everything to get rid of it.

Have you tried chilly's super wipe? There is a thread for it.
Sent from my Incredible 2 using xda app-developers app

Same here. I super wiped two days ago and formatted my sd card. I thought I had it and my phone ran fine for a day. I charged it over night and when I took it off the charger, it was shot again today. When it actually boots, I can't get past the unlock screen. It holds there for about a minute before going into a boot loop. I didn't even think of the ics firmware. Maybe I'll try going back to stock tomorrow and then reflashing cm10.
Sent from my A500 using xda app-developers app

I don't know if it's the firmware or not, but I thought it was worth a shot. I have used chilly's wipe and I have gotten the huge lag since then. I'm running his PAC rom now and I used his wipe twice before I installed. I've also v6 supercharged so I'm waiting to see if it happens again. Is there a copy of the old firmware that is flashable like the new one?

Baloeb said:
I don't know if it's the firmware or not, but I thought it was worth a shot. I have used chilly's wipe and I have gotten the huge lag since then. I'm running his PAC rom now and I used his wipe twice before I installed. I've also v6 supercharged so I'm waiting to see if it happens again. Is there a copy of the old firmware that is flashable like the new one?
Click to expand...
Click to collapse
There at threads for different ruu's. I'm not sure which one you need. Search through those. Also, when your phone starts lagging try connecting to a computer in adb I think, someone posted that that fixed theirs temporarily. I think they narrowed it down to the SD card being bad and with it connected it dismounts the SD card and doesn't have the problem. That might help.
Sent from my Incredible 2 using xda app-developers app

NeverSeparate said:
There at threads for different ruu's. I'm not sure which one you need. Search through those. Also, when your phone starts lagging try connecting to a computer in adb I think, someone posted that that fixed theirs temporarily. I think they narrowed it down to the SD card being bad and with it connected it dismounts the SD card and doesn't have the problem. That might help.
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I'll give that a shot next time. Usually I just pull the battery and install cm7 so I have a working phone.

Okay, 1st you need to return to stock:
http://forum.xda-developers.com/showthread.php?t=1599767
After this process you need to flash cwm and superuser:
I believe this thread http://forum.xda-developers.com/showthread.php?t=1751796 has all the files (including adb) set up in one .zip under "TACOROOT"
Or just download them from here:
https://dl.dropbox.com/u/77740451/recovery-clockwork-5.0.2.0-vivow.img
https://dl.dropbox.com/u/77740451/Superuser-3.0.7-efgh-signed.zip
This is what I did to remove the firmware. I didn't have the lag, but I was hoping to solve camera issues.

SkinnyT said:
Same here. I super wiped two days ago and formatted my sd card. I thought I had it and my phone ran fine for a day. I charged it over night and when I took it off the charger, it was shot again today. When it actually boots, I can't get past the unlock screen. It holds there for about a minute before going into a boot loop. I didn't even think of the ics firmware. Maybe I'll try going back to stock tomorrow and then reflashing cm10.
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
Just a quick note...When I was running CM10 I would get the boot loops at the lock screen, but if I just let it alone, it would loop 2-3 times and then settle in. It took a while, and I avoided rebooting my phone at all costs, but have you just let it sit for about 10 minutes to see if it pulls out of the boot loop? Mine usually came out in less than 5, but you never know. After it booted up it settled down and ran fine. I've never used the Venom rom or super wipe though, so ymmv.

gtdtm said:
Just a quick note...When I was running CM10 I would get the boot loops at the lock screen, but if I just let it alone, it would loop 2-3 times and then settle in. It took a while, and I avoided rebooting my phone at all costs, but have you just let it sit for about 10 minutes to see if it pulls out of the boot loop? Mine usually came out in less than 5, but you never know. After it booted up it settled down and ran fine. I've never used the Venom rom or super wipe though, so ymmv.
Click to expand...
Click to collapse
Mine doesn't boot loop, it runs great for a few days then starts to lag so bad it's unusable.

Baloeb said:
Mine doesn't boot loop, it runs great for a few days then starts to lag so bad it's unusable.
Click to expand...
Click to collapse
Some have reported that it's linked to a usb / sdcard / storage issue. Lag starts after connecting.
Sent from PAC-land

[Q] Moar 2.4

i installed the new moar. clean install. now it runs fine. battery life is great. but i have a big issue. for some reason it sometimes just goes to the bootloader and freezes up. have to gett back into recovery and reflash to get passed the bootloader again. done this mutiiple times so far. not running anything crazy either just some texts and phone calls. please if there a way to fix or something im not doing. please let me know. thanks.

yotaking said:
i installed the new moar. clean install. now it runs fine. battery life is great. but i have a big issue. for some reason it sometimes just goes to the bootloader and freezes up. have to gett back into recovery and reflash to get passed the bootloader again. done this mutiiple times so far. not running anything crazy either just some texts and phone calls. please if there a way to fix or something im not doing. please let me know. thanks.
Click to expand...
Click to collapse
What do you mean it goes into the bootloader. Need some specifics of precisely what you mean. And what do you mean by bootloader, are you talking about recovery or download mode?
Sent from my SPH-L710 using Tapatalk 2

GiantJay said:
What do you mean it goes into the bootloader. Need some specifics of precisely what you mean. And what do you mean by bootloader, are you talking about recovery or download mode?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
I believe they means the boot animation. Unless I'm mistaken, they're getting stuck in a bootloop. I'm really interested in which Kernel option they chose when installing it. I'd say that choosing a different one would fix the bootloop issues (I tried the optimized stock one recently and that seemed to work well).
I'd suggest that the next time it happens go into recovery and clear cache and dalvik cache. Reboot phone and see if that fixes the problem (give the phone time to boot up after clearing cache). If that doesn't work, you can try fixing permissions in Recovery (I doubt that'd fix a bootloop, but it might be worth trying).
Finally if none of the above work, I'd try downloading the MOAR rom again, but double-check md5 sums to make sure it's a good download. When installing it, start with the stock kernel and see if it occurs again.