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.

Myns Warm 2.2 RLS 5 Freeze at Unlock.

Is anyone else having this problem? Every time I wake my phone up, it freezes then about 30 seconds later, Sense force closes on me. I thought it was the phone so I took it back. But even my new phone is having the same problem. Could it be an issue with the kernal?

saw somewhere to clear the cache. did that. worked for about an hour. then went back to freezing. i know a lot of you use warm. i need some help. because it is my absolute favorite ROM, but this problem is quite irritating

Try a different kernel.

what would be a recommended kernal for this ROM?

happened to me and i did calkulins format all

The recommended kernels are right on Myn's thread. I use the Net SBC kernel and its awesome! Fast, consistent and great battery!

If just changing the kernel doesn't do it, as one of the other guys said, flash calks format all, then reflash the rom and start fresh. That should handle it for you.
sent from my supersonic

damn. I was hoping you wouldnt say I had to reflash. but ill give it a shot. thanks guys.

kennethbring said:
damn. I was hoping you wouldnt say I had to reflash. but ill give it a shot. thanks guys.
Click to expand...
Click to collapse
Did changing the kernel not work? If not, you could try just wiping cache and davlik, then reflash rls5 without wiping data or flashing calks format all. See if that fixes it. If Not, then do the full wipe, flash calks formatall.zip, then reflash rom. Good luck.
sent from my supersonic

I haven't tried just switching kernels. I'll do that now. And if that doesn't work, time to pull out the ole dusty titanium backup.

okay. so i flashed a new kernal. the net sbc one. and cleared the cache and dalvik. and when i rebooted it, the screen was a greenish tint for about 5 minutes. its gone away since then. but is this normal?

kennethbring said:
okay. so i flashed a new kernal. the net sbc one. and cleared the cache and dalvik. and when i rebooted it, the screen was a greenish tint for about 5 minutes. its gone away since then. but is this normal?
Click to expand...
Click to collapse
I have never noticed anything of the such. Did it happen just that once, or does it persist after a reboot? If it's okay, I would say it was a fluke thing. I didn't have good luck with the SBC kernels, and the controversey on them was enough for me to stop using it. I like the kernel in my sig.

kennethbring said:
okay. so i flashed a new kernal. the net sbc one. and cleared the cache and dalvik. and when i rebooted it, the screen was a greenish tint for about 5 minutes. its gone away since then. but is this normal?
Click to expand...
Click to collapse
Flash myn and don't change the kernel. the default kernel works great. make sure you have updated your radio/pri/wimax before u flash the rom.
Also, are you undervolting? I had a problem where i undervoltd too much and it would freeze for a bit after i unlocked. as soon as i got rid of undervolt, everything was fine.
the stock rom (minus any apps you dont want) is very solid....i use the **** out of my phone and myn's RLS5 is one of the most fast and stable sense roms i've used.

I don't thinck so.
Sent from my evil evo!!

tried a couple different kernals (including the stock that is included with warm) and im still having the freezing problem.
as far as undervolting goes, i dont mess with the cpu. i dont see a need to. so i know thats not the problem.
so is my only choice now to format all and reflash the ROM?
and also, since i flashed a new kernal, my adobe flash hasnt been working. every time i go to a website that uses flash, the internet app just force closes. is this an issue with the kernal? or something else?

Undervolting is built into many custom kernels.
I personally use netarchy-toastmod cfs havs more aggressive no sbc on Myns RLS 5. I don't seem to have the freeze on unlock but my phone had the Adobe flash problem until I updated it through the market.
At first I thought it was the kernel, but I've used the stock HTC, ziggys, and netarchy and still it would close the browser with no indication, when there was flash content. Maybe its a memory issue? It still closes every once in a while, but not as much as it did before the update.
I also downloaded adfree from the market as Myns RLS 5 has an outdated hosts file slowing down the internet in general until updated. Just download, hit revert, then update.
I occasionally get a freeze in sense tho, maybe once or twice a day, lasts about 3 seconds. Doesn't bother me, this kernels gets me 14+ hours as a medium user and is quite snappy otherwise.

Im using the same kernal as you. And I uses Calkulins format all. And I'm still getting the freeze at unlock. It only seems to happen when my phone sleeps for a long period of time (45 min+). But it is really annoying. I dont know if this could affect it at all, but I'm using the old version of Clockwork to flash everything. I'm not familiar with edify and all that. Its really irritating because Myns rom is the only one I like enough to consider rooting my phone worth it. Is there anything else I can try?

ive been looking over the forums and havent found anything pertaining to this. does anyone know anything else to try?

kennethbring said:
Im using the same kernal as you. And I uses Calkulins format all. And I'm still getting the freeze at unlock. It only seems to happen when my phone sleeps for a long period of time (45 min+). But it is really annoying. I dont know if this could affect it at all, but I'm using the old version of Clockwork to flash everything. I'm not familiar with edify and all that. Its really irritating because Myns rom is the only one I like enough to consider rooting my phone worth it. Is there anything else I can try?
Click to expand...
Click to collapse
Stop using Clockwork. That's the first suggestion. Then use the format all and flash the rom again. don't change anything on the rom. use that for a day or 2. if you still have problems, go back to the stock sprint rom. if you STILL have an issue, unroot and take your device back.

Ive already taken it back once. So, I know its not the phone. But I tried switching ROM's and they all freeze. So its not just a problem with Warm. I clear the cache, dalvik, full wipe and format all before every flash. But, as I said, every ROM I flash still freezes. I tried Fresh, MIUI, Warm, Sprint Lovers, and Elite. I switched to Amon Ra as well to see if maybe the problem was the recovery I was using, but still, the same problem. I dont download many apps. So, I'm pretty sure its not something I'm downloading from the market or anything. I've tried everything. So, at this point, I'm considering unrooting and going back to stock. Any last chance efforts I should try?

[Q] ROM/Theme/Mod Flashing Issues

I was wondering if anyone could help me out please. I've tried searching the forums, but I haven't been able to find my exact issue. Basically, I feel as if my phone seems to have increasing issues with flashing through Clockwork Recovery; here's the details:
I originally rooted my phone using the Odin flash method. I flashed the Juggernaut available at the time, wiping data/factory, cache, dalvik, and battery stats through clockwork first, and letting it chill for 15 minutes with the first boot. I follow the same steps each time I flash another rom ( I've read that I should also wipe /system, but Juggernaut seems to do that itself, so I haven't ). A month and a half ago, I wanted to add a few things, so I wiped, then flashed the latest Juggernaut, rebooted, let it settle,and then flashed the ICS Ultimate Theme, no wipe, then after another settle, flashed the Pdroid zip ( no wipe ) I made with the v1.27 auto-patcher. Everything seemed to work flawlessly for a month or so, then I started having issues that just kept getting worse: phone freezing while installing market apps then unfreezing, camera lagging, random freeze & reboots, etc. I tried fix permissions, and no luck. I wiped and tried reflashing everything the way I had, and the phone kept freezing after the faux kernel loading screen. Installing Juggernaut or another rom by itself, or a nandroid restore, is the only thing that got it past boot. Not even themes flashed over roms that they're made for get past boot. I restored my phone to stock using this method, wiped both SD cards, and re-rooted then flashed Juggernaut again, but this time I used clockwork's wipes and darkside's super wipe before flashing, but I still can't flash anything but the rom itself without a boot loop, even with fix permissions. I had a similar issue on my old mytouch Espresso; consecutive flashes seemed to almost eat away at my phone and make things worse, but that phone also had hardware issues. I'm using a new MicroSD since then. Also, if it means anything, I tried flashing the new clockwork touch from the zip on these forums after these issues started, and it never took, however, flashing through Rom Manager's after I purchased it worked fine.
Sorry about the long post, but I wanted to detail everything I've tried that I could think of before bothering anyone here. Does anyone know what could be the issue? I would really appreciate some help, because this issue is really frustrating, and I have no idea what's causing it.

Could someone help me with this please? I can try and get a log cat if needed. I'm just really hoping to get to the bottom of these issues.

I will be glad to help you out!
One big problem I see is that your not using Darkside Superwipe before flashing new roms.
So I would highly recommend you flash Darkside Superwipe first (clears all cache, partitions, ect very very thorughly) Better option than manually clearing cache and all that in clockwork mod.
Try Darkside Superwipe install the rom and see if you get any problems.
Here's how to use it if you dont know how to:

techfanatic9 said:
I will be glad to help you out!
One big problem I see is that your not using Darkside Superwipe before flashing new roms.
So I would highly recommend you flash Darkside Superwipe first (clears all cache, partitions, ect very very thorughly) Better option than manually clearing cache and all that in clockwork mod.
Try Darkside Superwipe install the rom and see if you get any problems.
Here's how to use it if you dont know how to:
Click to expand...
Click to collapse
I'd like to point out that he does in fact use tdjs super wipe.
OP: have you tried other ROMs or kernels. In my past experiences, faux kernel did not meet my expectations so I moved along to another one. Give my configuration a go (refer to my signature) and let me know of the problem persists
Sent from my Galaxy Nexus using Tapatalk 2

Thanks for the replies!
techfanatic9 - I originally just wiped through clockwork ( before darkside superwipe was standard ), but now I use that too, and I'm still having those issues. I watched through the entire video just in case, and I'm doing it just like they say to.
iLeopard - I have tried Digital Warfare, but I still have the same issue when flashing things over it ( ICS Theme and/or PDroid ), even if it's supposed to be compatible, though I haven't tried kernels yet. I'll give your sig's setup a try and report back.
Meanwhile, could anything else be the issue? As you can probably tell, I've tried almost every mistake I could think of, and since my last phone had the same issue, a similar hardware issue seems unlikely.

All right, I've been running that ROM and kernel combo for a few days now. I don't seem to have any issues when I just flash the ROM and kernel, but I get stuck at the boot screen if I try to flash something else on top of it. Also, when I try to restore my text message backups through Gosms ( around 9800 texts that I want to keep ), the phone freezes halfway through the restore, and from that point on, the phone will freeze 5-10 minutes after rebooting, unless I reflash. I make sure I don't have the phone running and I leave it alone while restoring, and it doesn't help. I've only had this gosms issue since my flashing issue, and sometimes it restores fine.
Does anyone know what could be causing that?

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

[Q] HELP! my note 2 wont boot past samsung logo!

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