Develop Bugs

Help rooting....stuck looping....

Having a problem here. Today I got a refurbished dinc, and tried to root w/ unrev. 3.2 and it went all the way through the process up to the point where it says waiting on reboot (could take 5 mins.) After that U.R said it lost its connection with the phone and rebooted. since then its been stuck in boot loops. S-off was never achieved and clockwork wasn't installed. I've tried resets and a 2.2 pb13img and nothing can stop the loops. Once in a while of random resets and fumbling around in the stock recovery it will boot to the phone program screen to call *228. It reboots and loops right after it goes to mount storage. I've tried taking out the card thinking it might be that.
It's a amoled screen.
I've rooted before and have no issues on my other dinc.
Plz help.
Sent from my ADR6300 using XDA App

riley614 said:
Having a problem here. Today I got a refurbished dinc, and tried to root w/ unrev. 3.2 and it went all the way through the process up to the point where it says waiting on reboot (could take 5 mins.) After that U.R said it lost its connection with the phone and rebooted. since then its been stuck in boot loops. S-off was never achieved and clockwork wasn't installed. I've tried resets and a 2.2 pb13img and nothing can stop the loops. Once in a while of random resets and fumbling around in the stock recovery it will boot to the phone program screen to call *228. It reboots and loops right after it goes to mount storage. I've tried taking out the card thinking it might be that.
It's a amoled screen.
I've rooted before and have no issues on my other dinc.
Plz help.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
What is your HBOOT version?

Hboot 0.92
Radio 2.15.00.07.28
Clockwork 2.5.1.2
Un.Rev. 3
Un.Rev. Forever
Incredibly re-engineered 2.2
Update -
Managed to get Un.Rev. to install with cw. And installed a Rom. Now I still get random reboots. Everything will be fine...ill update and install a bunch of apps. and I can use the phone for a while. Then all of a sudden it reboots over and over. To get it to stop, I have to re-do everything. Wipe cache, wipe dalvik, wipe battery stats, data/factory reset. I get an error after dalvik clear though "can't mount /dev/block/mmeblk12 (file exists)"
That puts me to square one.
Everything will be ok and then.....reboots...randomly at different points. sometimes right away and some times after an hour or two. No real pattern. I have a gut feeling it has to do with onboard memory?

Are you overclocking? What kernel are you using?
Try installing a different kernel, make sure it is a sense based kernel as you are using a sense based rom.
You can pick one from here - http://forum.xda-developers.com/showthread.php?t=866736

No I'm not over clocking. And I'm using the kernel that came with the Rom.
I do, however, seem to remember reading something about dincs overheating and rebooting until they cool. Maybe this is the case with mine.

I had the exact same issue when i received my refurbished phone. It is not uncommon that these issues - and others, will occur. Even before rooting i was having the issue.
I did notice that it will happen when i pushed the phone a bit, like talking and trying to download something from the market at the same time.
My suggestion is to unroot, everything stock, test the phone and see if it happens again. The Verizon representative tried to reset the phone and it started boot looping right in front him! And then they order another refurbished phone, which also had issues. Long story short, they gave me a new phone after i begged. (thank u VZ local store, which btw i sent a few customers your way )
According to some inside people i talked to, the 3rd party companies (or individuals) that fix these phones do a terrible job at it and the Verizon stores see quite a few people everyday with similar issues. I have no way of verifying this, just what i was told.

riley614 said:
No I'm not over clocking. And I'm using the kernel that came with the Rom.
I do, however, seem to remember reading something about dincs overheating and rebooting until they cool. Maybe this is the case with mine.
Click to expand...
Click to collapse
I would still try another kernel first, HeyItsLou or Ziggy IMO. If you still have the problems then, flash back to complete stock and take it to Verizon.

Yea, ill give that a try. If I have no luck, ill send it back. After unrooting of course.
Sent from my ADR6300 using XDA App

Riley, were you able to fix it? I'm really interested in some analysis of the problem and investigating issues with refurbished phones boot looping. Someone else just posted a similar problem.

Nah. No luck here. Still randomly looping. Nothing seems to have an effect in when it why it loops. It'll loop even w/o any apps installed.Even after a "fresh" install of a rom and system wipe.
Gonna send it back.

riley614 said:
Nah. No luck here. Still randomly looping. Nothing seems to have an effect in when it why it loops. It'll loop even w/o any apps installed.Even after a "fresh" install of a rom and system wipe.
Gonna send it back.
Click to expand...
Click to collapse
Sorry to hear that, as i said i had the same issue and i had to get another one. if you get a second "lemon" refurb go to Verizon and talk to a manager. They might do an out of the box replacement and put it in the system as defective under warranty. Good luck.

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] VZW Galaxy Nexus Randomly wiping SD memory

Can someone please hepl me out with this. this is the second time this has happened in as many weeks. I'm running Liquid ICS 1.4 Rom and have the touch clockworkmod recovery installed on my GNEX. Just recently though, I'll unlock it and go into recovery to make a backup and when its done making a backup, my SD card is totally formatted. I've all pics and media now twice in the last two weeks. Luckily, after the first time last week I started making copies of all my pics but this is still terrible and annoying. Has anyone ever had this happen or know a solution.
Thanks

Try a different recovery, or a different ROM, that is WRONG!
And to be honest, I've never heard of such a thing.. Sorry, dude, but I think your GNexus doesn't like LIquid ICS...

familyguy59 said:
Try a different recovery, or a different ROM, that is WRONG!
And to be honest, I've never heard of such a thing.. Sorry, dude, but I think your GNexus doesn't like LIquid ICS...
Click to expand...
Click to collapse
It isn't the rom if it does it in recovery.
Sent from my Galaxy Nexus using xda premium

joshnichols189 said:
It isn't the rom if it does it in recovery.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
try twrp recovery. it has more options and is better/less buggy than cwm(in my opinion).

Well, I've come to this conclusion after a long night of experimenting and testing. Its definitly CWM and not Liquid. However, The problem with the memory wipe only occurs when I have my phone plugged into my work PC and I try to create a nandroid via the CWM app and not the recovery. Another weird thing is that after my SD memory would essentially become corrupt, my camera would not store pictures.
What I did last night was totally took my phone back to stock, removed SU, and locked the bootloader. I then got the 4.0.4 update pushed to me from verizon. After that was done updating, I re-rooted the phone and started up CWM. I had a nandroid from a few days ago that I figured I'd give a shot. It ran perfectly and I had restored my phone. Then, without my phone being plugged into anything, I rebooted into recovery and ran a backup. Worked fine. So, so far so good. Hopefully its just my work PC not talking nice with my phone because my home PC didnt cause any issues with my phone while it was plugged in.

JB roms suddenly not working?

I'm just going to throw this out there for anyone who may know the answer, after searching for the last 3 days, I'm not finding anyone else having the same problem, so I'm thinking it may be something I did. Here's the issue.
I'm a confirmed flash-a-holic, and flash new roms or backups probably 2-3 times per week. I haven't tried any of the JB roms until recently, but dove in just before Nit's Viper Rom became available for ICS. I had installed the JB "global" rom, and had it working(ish), and then changed to the viper mod, then installed Aeroevan's "unofficial JB" when the 10/25 update on Goo.im came available. The install went smoothly and it worked great for about a day, then tanked big time when I tried to change the launcher from Trebuchet to Nova (I can't even guess why THAT had anything to do with it). It started lagging big time and then boot looping. Now, upon trying to wipe everything (factory reset/cache/dalvik/all partitions but sd), I get nothing but boot loops and NONE of the JB roms will install. From my reading, I know others get boot loops, but after a sequence, finally get into setup. Mine will too after 5-6 boot loops minimum, but the screen freezes on the initial setup screen and it's completely unusable (touch screen unresponsive). I don't get why that is when I HAD it installed the other day and it was very responsive (using Aeroevan's JB mod). I WAS using the 4EXT recovery when I started doing all of this, then switched recoveries to the most recent TWRP, and it allowed me to install Aeroevan's JB mod, and even start the setup, but very soon started lagging and then the boot loops again. At this point, I'm sortof at a loss, and the only thing I can think of is that maybe I should NOT have been wiping the sd partitions and SHOULD have only been wiping cache/dalvik/factory reset. At the moment, anyway all ICS mods are flashing/running just fine (currently on Nit's Vipermod and really liking it btw), but if anyone knows where I went astray, I'd appreciate any pointers. Thanks all, this is by far the best forum I have been a part of!

http://forum.xda-developers.com/showthread.php?t=1805773&page=117

Oh boy..... Be sure and post back if you find a solution, glad I'm not the only one! I thought I did this to myself... which I guess I sortof did if you get technical.
Sent from my Dinc2 using Tapatalk

I had the same problem but was told to flash new radio and it stopped bootlooping and everything went back to normal....

auberry05 said:
I had the same problem but was told to flash new radio and it stopped bootlooping and everything went back to normal....
Click to expand...
Click to collapse
Which radio did you flash?

Ok, I made headway by reverting TWRP recovery back to 4ext's newest recovery, restored my oldest original stock GB backup with ext3 partitions which was originally a CWM recovery. I let it run after install for about 10 minutes without updating anything, then 4Ext wiped data, cache/dalvik, system. I then reformatted all partitions back to 4ext and then wiped everything again even fixing permissions. Then I tried a fresh install to Aeroevan's unofficial CM10 from 10/25 and gapps from 10/11. Install went smoothly and booted first time with no boot loops. I'm using it right now and I'm back in the butter again..... for now at least. If I take a turn for the worst, I'll post back.
Ok, well, scratch that, I am having the same problems a couple of other guys are having in the cm10 dev thread. I'm only able to run sense roms, original stock, UKBII, etc, no ICS or JB roms work, incredibly laggy and bootlooping endlessly. I have never had this much trouble flashing roms, I do it all the time. Sadly, it started when I flashed the viper rom, and I don't even have a copy of it to re-flash now since I wiped my card and it wasn't backed up on my computer (I think I must've downloaded it from my phone). I have spent WAY too much time on this, so am now relegated to only lurking here until someone can find a solution that's not just "firing down the well" like I've been doing since this started.

bwpoersch said:
Ok, I made headway by reverting TWRP recovery back to 4ext's newest recovery, restored my oldest original stock GB backup with ext3 partitions which was originally a CWM recovery. I let it run after install for about 10 minutes without updating anything, then 4Ext wiped data, cache/dalvik, system. I then reformatted all partitions back to 4ext and then wiped everything again even fixing permissions. Then I tried a fresh install to Aeroevan's unofficial CM10 from 10/25 and gapps from 10/11. Install went smoothly and booted first time with no boot loops. I'm using it right now and I'm back in the butter again..... for now at least. If I take a turn for the worst, I'll post back.
Ok, well, scratch that, I am having the same problems a couple of other guys are having in the cm10 dev thread. I'm only able to run sense roms, original stock, UKBII, etc, no ICS or JB roms work, incredibly laggy and bootlooping endlessly. I have never had this much trouble flashing roms, I do it all the time. Sadly, it started when I flashed the viper rom, and I don't even have a copy of it to re-flash now since I wiped my card and it wasn't backed up on my computer (I think I must've downloaded it from my phone). I have spent WAY too much time on this, so am now relegated to only lurking here until someone can find a solution that's not just "firing down the well" like I've been doing since this started.
Click to expand...
Click to collapse
On follow-up, I read mixed opinions about the wisdom of using TiBu on restores, assuming I'm able to ever recover this my thinking is that one could use TiBu to restore apps ONLY and NO data and that would/should not cause a problem (assuming you're restoring a backup from within your installed ROM's file structure .i.e., JB/ICS/GB)? Also, I use My Backup Pro to restore call/MMS/texts only, that oughta be safe too shouldn't it?

I had a similar issue last night. never had problems flashing from viper to cm10 till yesterday. I've flashed back and forth about 3 times until I flashed the leaked 4.2 camera with sphere camera on aero cm10 Halloween build. I was playing around with the sphere camera and attempted to get it to actually finish loading the pics together by overclocking to 1.4mhz and I ended up pulling the battery. it boot looped very slow and laggy after. I did a full wipe, fresh install of aeros cm10 from twrp and got the same thing. So I recovered viper Rom from twrp , booted, then did a full wipe and install of cm10 and still boot loops laggy. I did not have the overclock settings "set at boot" ticked when I put it to 1.4mhz. odd indeed
sent by the viper

So... I was having no issues until today's huge headache. I was on cm10 10-25 and it worked great. Dirty flashed to 31 and it all went to hell. Slowed to a crawl so restarted to recovery to fix permission. Restarted and it kept restarting. I got some failure message when it would boot. Don't recall what it was.
I then tried 3 different recoveries and also full wipes and fresh flashes of 3 different roms. Same loop result basically. Finally an old recovery worked and I'm on a month old mrom version now. Soo... any thoughts on what the heck happened? I did nothing out of the ordinary. I was worried I somehow bricked but obviously not since I'm sending this on my phone. Kinda freaked to do anything right now... any thoughts or help/ideas?
PS... I just use the basic cwm and only cwm for my recoveries.
Sent from my Incredible 2 using xda app-developers app

Ukb wont boot here.
Sent from my HTC_Amaze_4G

so I got aeros 10/31 build to boot after taking 10 min to finish the start up set-up. it was extremely laggy, it would random restart a few times. I played around with over clocking then under clocking but the cpu was maxed out 24/7. I'm assuming this is what is causing the extreme lag. I changed the governor to on demand and it started to act normal and not lag out. so I used it for awhile then I decided to change the cpu governor back to smartassv2 and then I was back to lag and the cpu was maxxed again... can't recreate the scenario cuz it doesn't boot now...
my conclusion is it has to due with the kernel and cpu governors on JB. I've tried aeros jb 12, 13,14,and 15 kernel and also Evans kernel with no luck on getting the cpu not to b maxed out... hope this helps solve the issue
Sent by the viper

fen0m said:
so I got aeros 10/31 build to boot after taking 10 min to finish the start up set-up. it was extremely laggy, it would random restart a few times. I played around with over clocking then under clocking but the cpu was maxed out 24/7. I'm assuming this is what is causing the extreme lag. I changed the governor to on demand and it started to act normal and not lag out. so I used it for awhile then I decided to change the cpu governor back to smartassv2 and then I was back to lag and the cpu was maxxed again... can't recreate the scenario cuz it doesn't boot now...
my conclusion is it has to due with the kernel and cpu governors on JB. I've tried aeros jb 12, 13,14,and 15 kernel and also Evans kernel with no luck on getting the cpu not to b maxed out... hope this helps solve the issue
Sent by the viper
Click to expand...
Click to collapse
Someone just threw down on the info. Sounds like I will be flashing the latest mrom. Not gonna repeat the horror of my recent cm10 fiasco. Thanks for this.
Sent from my Incredible 2 using xda app-developers app

Unfortunately I too am finding it near impossible to flash any ICS/JB ROM. The closest I've gotten is the Google sign-in on Andromadus Mimicry, but that practically slows to a halt when signing in. As of now I'm on Condemned CM7 and I must say I REALLY miss Google Music.
Sent from my Incredible 2 using xda premium

jtsrtr13 said:
Unfortunately I too am finding it near impossible to flash any ICS/JB ROM. The closest I've gotten is the Google sign-in on Andromadus Mimicry, but that practically slows to a halt when signing in. As of now I'm on Condemned CM7 and I must say I REALLY miss Google Music.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Try installing 4ext recovery. Format system, data, cache to ext3 like 3 times. Flash tunnas global cm10 rom
Sent from my Incredible 2 using xda app-developers app

Baby mamas INC 2 has been having same issues. I have to believe it had something to do with her being on the ICS leak from back in September with the 320 radio. I went as far as to getting back to compete stock with s-off. Got back to 2.3.3, got CWM and root. Hopefully I can try getting her phone back on CM9-10 cuz she really misses it and we were having EXACT problems stated above. Boot loops, touch screen not responsive, wallpaper would change out of nowhere, lock screen would be black with nothing but hardware buttons lighting up. Thank GOD for these devs and their work to get back to stock or I would have thrown this POS out the window lol.
Sent from my MB865 using xda premium

A2Trip said:
Baby mamas INC 2 has been having same issues. I have to believe it had something to do with her being on the ICS leak from back in September with the 320 radio. I went as far as to getting back to compete stock with s-off. Got back to 2.3.3, got CWM and root. Hopefully I can try getting her phone back on CM9-10 cuz she really misses it and we were having EXACT problems stated above. Boot loops, touch screen not responsive, wallpaper would change out of nowhere, lock screen would be black with nothing but hardware buttons lighting up. Thank GOD for these devs and their work to get back to stock or I would have thrown this POS out the window lol.
Click to expand...
Click to collapse
I did the revert a while back for some other issues and didn't have any trouble getting aeroevan's CM10 up and running. I haven't had any issues with it other than the persistent bugs which are no problem for me. I don't think these issues have anything to do with the radio, but with the way the stuff is getting flashed. You might try a different recovery. I have had success with TWRP and CWM (as installed from ROM Manager, not touch) restored from a backup for me, but I didn't install using CWM.

ericsdeadinside said:
Try installing 4ext recovery. Format system, data, cache to ext3 like 3 times. Flash tunnas global cm10 rom
Click to expand...
Click to collapse
Did these things ....even Stunna's CM10 was laggy beyond belief. Back to gb.....again.
Sent from my Incredible 2 using xda premium

Don't know what to tell you. I switched to 4ext ran CDMA miui for a week and I was able to flash cm10 with no issues.
Sent from my Incredible 2 using xda app-developers app

jtsrtr13 said:
Did these things ....even Stunna's CM10 was laggy beyond belief. Back to gb.....again.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
+1... seems like only Sence ROMs have been working on my girls Inc. 2. Viper seems fine for now... But her phone must literately hate CM9 and 10...7 works fine too. Not quite sure why these issues have been going on to few of us but I'm almost certain it will not be solved... On the move...
Sent from my MB865 using xda premium

hey guys I fixed my Inc 2 with jb ics lag/ boot looping issues.
check it out
http://forum.xda-developers.com/showthread.php?t=1987051
Sent from an incredibly running JB inc2