Related
Sorry about double posting, but I am getting desperate (posted on Q&A).
Can't find an answer to this on google or xda. Didn't know if I should post this in General or Q&A.
I have been using my Incredible since it came out. I quickly learned about rooting, roms, s-off... with no problems. I have been running Skyraider almost from the beginning.
Here is the problem: A few days ago, I noticed on the SR thread that there were updates for the radio and hboot. So, I went ahead and flashed them. Almost immediately I started noticing the screen becoming unresponsive. After a minute or two I did a battery pull, rebooted, and again after a little while, freeze and reboot. I also noticed that even when the phone is awake but screen off, it would wake itself up. The rebooting and freezing makes it impossible to use my phone.
I tried everything I could think of:
Nandroid restore (obviously didn't work since this doesn't effect hboot or radio).
Reinstalled fresh SR Rom wiping everything, including dalvik, and did factory reset.
Finally, I downgraded back to the hboot and radio versions I had before, still no effect. (Baseband version 2.15.00.07.28, hboot .79 ).
I tried installing another ROM (Uncommon sense) to make sure it wasn't a ROM issue, ..same problem.
Please, any help would be much appreciated. I don't know what my next step should be.
PS, I am not overclocking, just using stock kernel.
Sent from my ADR6300 using XDA App
try downgrading to completely stock 2.1 then see if it keeps doing it...otherwise I'd say that maybe you did something wrong installing a file and it's bricked...that's what it sounds like anyways
Sent from my ADR6300 using XDA App
pete_kowalski83 said:
try downgrading to completely stock 2.1 then see if it keeps doing it...otherwise I'd say that maybe you did something wrong installing a file and it's bricked...that's what it sounds like anyways
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Today it's running a bit better. I'll keep testing it, if it continues to crash, I will take your suggestion and go back to 2.1 and start over.
Just a thought: are you restoring your stuff via Titanium? If so, you may be restoring a bad / incompatible system instruction. You might try this: Do a master reset and restore your important apps (not data) one at a time to check performance. Install data later (also individually) as needed.
HTH!
rfarrah said:
Just a thought: are you restoring your stuff via Titanium? If so, you may be restoring a bad / incompatible system instruction. You might try this: Do a master reset and restore your important apps (not data) one at a time to check performance. Install data later (also individually) as needed.
HTH!
Click to expand...
Click to collapse
I did use Titanium (apps & data, but not system). I am currently testing Uncommon Sense Rom. Been running fine last 2 days. Idk why.
Sent from my ADR6300 using XDA App
Hey everyone,
Hopefully someone can help me with this situation. I haven't been able to find relevant information yet.
I'm currently running a Rooted Incredible with the latest Virtuous ROM. I'm trying to flash back to the stock .17 kernel from HTC, but ANY kernel I flash onto it causes the screen to load up as far as the red eye, stall and then reboot causing a constant loop. The only way I can get beyond this so far is just flashing my recovery image. I've installed from ROM manager and checked to wipe data/cache (backed up before of course!) and have even booted into recovery manually and flashed from the download folder and the actual zip file. Before that I've wiped data and dalvik cache. I can't figure out what I'm missing here. Any suggestions??? I hope I haven't crippled my Droid by doin this.
DL the new stock kernel to pc mount card to pc put the new kernel somewhere you'll remember then reinstall sdcard and try flashing the kernel that way if you haven't already
Sent from my ADR6300 using XDA App
Hypcrsy said:
Hey everyone,
Hopefully someone can help me with this situation. I haven't been able to find relevant information yet.
I'm currently running a Rooted Incredible with the latest Virtuous ROM. I'm trying to flash back to the stock .17 kernel from HTC, but ANY kernel I flash onto it causes the screen to load up as far as the red eye, stall and then reboot causing a constant loop. The only way I can get beyond this so far is just flashing my recovery image. I've installed from ROM manager and checked to wipe data/cache (backed up before of course!) and have even booted into recovery manually and flashed from the download folder and the actual zip file. Before that I've wiped data and dalvik cache. I can't figure out what I'm missing here. Any suggestions??? I hope I haven't crippled my Droid by doin this.
Click to expand...
Click to collapse
You should not be wiping data when flashing a new kernel.
How does that differ from flashing it from recovery if I may ask? I figured I had done everything properly and even after just going to recovery, wiping dalvik, wiping data then flashing I keep getting the issue.
I'm actually at work at the moment and don't have access to my PC to download it. But I'll give it a shot when I get home. Luckily flashing my recovery image works just fine, I'm just stumped why now it wants to cause me grief.
Hypcrsy said:
How does that differ from flashing it from recovery if I may ask? I figured I had done everything properly and even after just going to recovery, wiping dalvik, wiping data then flashing I keep getting the issue.
I'm actually at work at the moment and don't have access to my PC to download it. But I'll give it a shot when I get home. Luckily flashing my recovery image works just fine, I'm just stumped why now it wants to cause me grief.
Click to expand...
Click to collapse
At the most, you should be wiping dalvik. You should not be wiping data when flashing a kernel. Doing so will result in the self-inflicted grief you're experiencing.
najaboy said:
You should not be wiping data when flashing a new kernel.
Click to expand...
Click to collapse
Sorry I just saw this post immediately after I replied. I thought wiping data applied for both flashing ROMS and kernels.
najaboy said:
At the most, you should be wiping dalvik. You should not be wiping data when flashing a kernel. Doing so will result in the self-inflicted grief you're experiencing.
Click to expand...
Click to collapse
^This. Only wipe dalvik, not data.
Ok I'll give it a shot while I'm here. I was flashing over to the new edition of Kings and it just became incredibly unstable when interacting with SetCPU, so I was just going to go back to the stock HTC one, that's when I got the first constant bootloop. I'll give it a shot and let you guys know what happens. Thanks for the feedback.
Yeah the reload worked this time, I don't know why it was giving me such an issue when I could have sworn it was working ok every other time I've done it before. Any reasons why I'd be getting such a hard time from Kings Kernel 6? I've seen so many rave reviews with it but everytime I have it on my phone it lasts me about ten minutes and then goes back to that same constant boot cycle.
Hypcrsy said:
Yeah the reload worked this time, I don't know why it was giving me such an issue when I could have sworn it was working ok every other time I've done it before. Any reasons why I'd be getting such a hard time from Kings Kernel 6? I've seen so many rave reviews with it but everytime I have it on my phone it lasts me about ten minutes and then goes back to that same constant boot cycle.
Click to expand...
Click to collapse
thats weird anyone else having that problem? haven't tried 6 yet
Sent from my ADR6300 using XDA App
You only need to wipe dalvik if going to and from one with HAVS, but it doesn't hurt to be safe.
Sent from my ADR6300 using XDA App
Thanks for the assistance everyone. I finally got the darn thing stable. But I'm still curious about the kings kernel 6. I was stoked to try it because I was hoping it would be stable. I was having that instability issue with 5. Anyone else know what I'm talking about???
Sent from my rooted Droid Incredible!!
Hypcrsy said:
Thanks for the assistance everyone. I finally got the darn thing stable. But I'm still curious about the kings kernel 6. I was stoked to try it because I was hoping it would be stable. I was having that instability issue with 5. Anyone else know what I'm talking about???
Sent from my rooted Droid Incredible!!
Click to expand...
Click to collapse
Not exactly. I was running 5 on SkyRaider 3.3.2 for a while, then all of a sudden I started having horrible lag while unlocking the phone and for about 7-10 seconds afterwards. Is this what you're referencing? When I switched to BFS6, I didn't have the problem. But the problem did kick in a while after install of 5 (few weeks), I didn't have 6 that long. 6 seemed pretty solid. Give 6 a shot, if you don't like it, just flash something else. Nandroid just to be safe, too.
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS4.
Yeah I always nandroid just in case when I do any serious modification, but I was experiencing the same issue with 6 as I was with 5. Just checking the different limits with SetCPU, anytime I went over 1.1 for overclocking the phone would stay on for about 15-20 seconds and then reboot, get as far as the red eye and then reboot again. That was as far as I ever got with his kernels which is unfortunate.
When testing SetCPU and overclocking, make sure you don't have set on boot enabled.
Sent from my ADR6300 using XDA App
Thanks I'll give it a shot later on.
Running Synergy RLS1 my phone app (com.android.phone) keeps not responding apparently so I get the popup for wait or force close. If i reboot it fixes it for a while but it keeps happening. Im worried im missing calls or texts. And what if theres an emergency and I cant make a call lol. Is this a Synergy issue or what? PS I tried fixing permissions.
You have proper version of hboot and at least a 2.1.x radio?
Sent from my ADR6300 using XDA Premium App
To be honest, I have no clue. How can I find out and is that something I can fix without reflashing/wiping/etc.?
Boot into hboot menu; device off, hold volume DOWN and power until booted into white screen. Hboot version is listed at the top. Use volume button to navigate and power button to select. Radio version ; Settings, About Phone, software information, look at the baseband version, that's the radio.
Sent from my ADR6300 using XDA Premium App
Hboot 0.92.0000
Radio 2.15.00.07.28
Hmm, which version of CWM does the thread say is required, and are those versions of hboot and radio acceptable per the thread?
Got ample space on the sd?
Sent from my ADR6300 using XDA Premium App
What clockworkmod recovery version are you using and what was your rom installation procedure?
ive been using rls1 since it was released and this just started happening the other day. i think it may have something to do with Faceniff. I remember it starting sometime around installing and using that app
Do you know what a clockworkmod is Paintboarder? Its a recovery system and you can find out easily what version you are running by using Rom Manager in your app drawer, and just look under recovery, and it says current recovery: Clockworkmod ?.?.?.?
Hope that helps you if you dont already know. And maybe your getting FC's because you didnt do a clean wipe and install. Did you try fixing permissions?
im completely aware what clockworkmod is. im not that much of a noob. im running 3.0.0.8. like i said. my installation process couldnt be the issue since i have been running without issues since the release of rls1
the issue is seeming to have receded a little since removing Faceniff. That doesnt mean it doesnt still happen. It does. And btw read the OP. I did try fixing permissions.
My bad, didnt mean to downgrade you just wanted to be sure. Well im running Synergy RLS1 right now and i havent experienced that issue. If it were me i would just try reflashing it. So far it is an amazing ROM.
Sorry man i guess i looked past that part about the fixing permissions.
flashed a different radio i saw in someones signature. seems to be working fine now. also i had the 3G and 1X connectivity issues and the solution in the ROM thread fixed it.
I'm using the older incredible without slcd and have had no issues, wonder if that connectivity issue is tied to that in any way? Guys with the newer incredible vs. Old
Dink sporting Synergy RLS1. Xda app.
Mods and not wiping seem to cause pretty much every error with FCs that I run into. Only time I get them reintroduced it seems is if I freeze/remove something that's needed by another program or if I restore data for certain programs (which were backed up under another ROM).
I have RLS 1 installed too and it ran fine for about 6 days before I started getting fc's. I was rebooting at least once a day the first 6 days then I didn't reboot for 2 days and started getting fc's. So I started rebooting daily again and I don't seem to have any more problems.
Hi,
I am currently running Android Revolution HD 5.1.7 on my DHD
I was just wondering with the new 6.1.1 version out, to upgrade to it,
do I simply download the file and just flash that to the device or must I first wipe my device? Or some other way?
Thanks for any help!
P.s Really sorry if this has already been asked but I had a quick search and couldn't see anything to this specific situation!
Back up all your data then flash the superwipe script, then flash the ROM, restore data
Sent from my HTC Desire HD using Tapatalk
Thanks alot,
Also once I have flashed the rom to the phone,
Can I remove the file from my SD Card to free up some space?
Its something I have been unsure about from the first time I flashed my phone,
But I should imagine you can??
**UPDATE**
I have succesfully installed Android Revolution HD 6.1.1
But I am getting an awful lot of Force Closes now,
1 in particularly when i try to go on "People" (contacts) it instantly force closes!
Another is SuperUser, and there are a few more than insantly FC as soon as I try to Open them!
Razza12003 said:
Can I remove the file from my SD Card to free up some space?
**UPDATE**
I have succesfully installed Android Revolution HD 6.1.1
But I am getting an awful lot of Force Closes now,
1 in particularly when i try to go on "People" (contacts) it instantly force closes!
Another is SuperUser, and there are a few more than insantly FC as soon as I try to Open them!
Click to expand...
Click to collapse
1. You can but I would recommend that you keep a copy of a stable ROM on your sd card just in case you have to reinstall for some reason.
2. It seems like the ROM is corrupted.
Did you superwipe before you installed the ROM?
If you have:Check the md5 checksum of the rom you downloaded. It should be the same as the one posted under the ROM download link in the ARHD thread. If its the same you can try superwiping and reinstalling the rom.
If you havent: Download the superwipe script from the first page in the ARHD thread, superwipe and reinstall the ROM.
Also make sure to backup your phone data before superwiping because everything will be lost. Also don't install any mods untill your device has completed the first boot after installing the ROM.
to be honest i had issues with arhd 6.1.1 when i flashed it too. not the same as yours but constant. not everybody seems to have them though and others say it has something to do with the overclock daemon. i believe there´s a patch for it though on the 6.1.1 developers thread.
i didnt bother though i just moved on to virtuous unity 2.39 and have had no problems, really smooth sense 3.0 rom. i´ve been planning to try out a non sense rom next but i really like this rom so i´ve been putting it off for a while now. i even put the beats audio patch on it a few days ago and i gotta say its pretty good even on stock htc headphones
planing to update to arhd6.1.1 too, but have ardh3.3 and clockwork 3.0.0.6. which clockwork is ok (mean which of the newest)?
I did use superwipe and i checked the md5 and it was all good!
I re-flashed the rom and now its ok
I have found out what was causing it!
It starts happening again every time I install google+ 2.0
The new version of the app that has recently been leaked on androidpolice
(Would include a link but im not allowed yet)
And the reason it did it straight from the start the first time is because, before
doing anything else, I restored all my app via Titanium Backup!
If anyone else has this issue or could try to install the app and see if it happens
to them or could figure out how to fix it, it would be great!
(Don't worry about installing it, uninstalling it stop the force closes straight away)
did you try just restoring just the app, but clean without the user data. i did that first time i flashed a rom and it caused all sorts of problems. so i reflashed and restored the apps one by one but just the app, no user data, and stopped having problems
Lewelynn said:
Also make sure to backup your phone data before superwiping because everything will be lost.
Click to expand...
Click to collapse
Hi,
My first post
Any idea does this superwiper clean the radio as well? Does the order matter - first wipe, then rom and finally radio?
ponk2k said:
did you try just restoring just the app, but clean without the user data. i did that first time i flashed a rom and it caused all sorts of problems. so i reflashed and restored the apps one by one but just the app, no user data, and stopped having problems
Click to expand...
Click to collapse
Yes i tried restoring just the app, that caused fc's too!
As did re-downloading the app!
jms-xda said:
Hi,
My first post
Any idea does this superwiper clean the radio as well? Does the order matter - first wipe, then rom and finally radio?
Click to expand...
Click to collapse
Superwipe doesn't effect the radio, and yeah that order you said is the way I went about it, but I also think you can do radio before rom too!
Update from 5.1 to 6.1
Maybe I haven't looked hard enough or maybe I am simply too tired...
Are there any specific steps from updating ARHD from 5.1 to 6.1? I can't seem to find any info about it.
Also, flashing the 6.1 over the 5.1 will it reset the way my screens/widgets are set while on 5.1?
Thanks.
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