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
Related
I'm aware of the issues associated with CM6 RC3, but when I installed 6.0.1 today, I booted, the touchscreen was non-responsive, but the scroll wheel allowed me to reboot.
Initially, I forgot to install the stock htc kernel over the hydrakernel I had for Sense (#2), so I put that on. When I rebooted, my screen was responsive, but I noticed a lot of page tearing, and my "SD Card is damaged. May require a format" or some such nonsense.
I'd like to try CyanogenMod but thats a major issue to me. I followed the wiki guide to a T, so its not like it could have been install issue. I reverted to Virtuous 2.2 for the time being, so I find it hard to believe my SD card is damaged, especially since Virtuous doesn't come up with the error.
Any thoughts or ideas that could fix this? Anyone experience similar issues? Thanks in advance.
You should be using the CM6 kernel only. I'd guess that's the source of your woes.
Sent from my Incredible using XDA App
@rmaccr
Only use the kernal that comes with the rom. CM6 is very picky when it comes to custom kernals. I tried to flash hydra and kingx kernals and no go. Just use the original kernal and u should be good.
Sent from my Incredible using XDA App
Make sure you're wiping data/factory reset and wiping the cache partition in Recovery before you install a different ROM.
There's also an alternate kernal you can flash if the stock CM6 kernel is giving you problems - search the RC3 thread to find it.
Thank you for all of your feedback. I'll have to do some thread searching to find that kernel. I assumed that may be the issue.
rmaccamr said:
Thank you for all of your feedback. I'll have to do some thread searching to find that kernel. I assumed that may be the issue.
Click to expand...
Click to collapse
Just reflash the rom and it will include the kernel. Just make sure you have set cpu or some other app to underclock your processor if need be. It's clocked at 1.15 and that gives my phone a bootlooping and crashing party.
Sent from my Incredible using Tapatalk.
rmaccamr said:
I'm aware of the issues associated with CM6 RC3, but when I installed 6.0.1 today, I booted, the touchscreen was non-responsive, but the scroll wheel allowed me to reboot.
Initially, I forgot to install the stock htc kernel over the hydrakernel I had for Sense (#2), so I put that on. When I rebooted, my screen was responsive, but I noticed a lot of page tearing, and my "SD Card is damaged. May require a format" or some such nonsense.
I'd like to try CyanogenMod but thats a major issue to me. I followed the wiki guide to a T, so its not like it could have been install issue. I reverted to Virtuous 2.2 for the time being, so I find it hard to believe my SD card is damaged, especially since Virtuous doesn't come up with the error.
Any thoughts or ideas that could fix this? Anyone experience similar issues? Thanks in advance.
Click to expand...
Click to collapse
Its not the SDCard that requires formatting. It is the internal phone storage. If you view it via Astro, it should appear ok.
whewstoosae said:
Just reflash the rom and it will include the kernel. Just make sure you have set cpu or some other app to underclock your processor if need be. It's clocked at 1.15 and that gives my phone a bootlooping and crashing party.
Sent from my Incredible using Tapatalk.
Click to expand...
Click to collapse
I thought 6.01 was clocked to normal speed and if you wanted the overclocking you just get 6.0 instead.
bippy_b said:
I thought 6.01 was clocked to normal speed and if you wanted the overclocking you just get 6.0 instead.
Click to expand...
Click to collapse
I think that 6.0.1 is defaulted to 1GHz, but you can o/c it if you want to with SetCPU or similar.
The kernel that comes with cm6.0.1 is already great. i get the best battery life i have ever had on my incredible. It can be overclocked to 1.15ghz
When I downloaded it defaulted to 1.15 so I guess YMMV.
Sent from my Incredible using Tapatalk.
rmaccamr said:
Thank you for all of your feedback. I'll have to do some thread searching to find that kernel. I assumed that may be the issue.
Click to expand...
Click to collapse
Slow down and read everything over a bit better.
Hydra and King usually state somewhere SPECIFICALLY that they DON'T work with/support CM6. You don't need to find any kernel, just WIPE your device properly ( wipe data/cache/dalvik) before you flash it. Once flashed don't try any kernels.
Also understand there are known issues with it. One is that BT music streaming doesn't work at all. The other is that the OS doesn't scan the built in 8gb of memory. The third one is that you may experience a random reboot or suddenly get a black screen and unresponsive phone when using wifi. It may happen in 30 minutes, it may take 12 hours. It may not happen at all. It's not even close perfect yet.
The only issue I have seen so far is random reboots and yesterday when I booted up my Phone all my widgets were brown boxes and said they were not compatible, a reboot fixed that.
Android Version 2.2
Model Number - Incredible
Baseband - 2.15.00.07.28
Kernel Version - 2.6.32.15......koush
Mod Version Cyanogen 6.0.1
When you mount your phone via usb mass storage it is mounting more than just the /sdcard/ and /emmc/(internal storage)
It is mounting /data/ and /system
If you're running Windows it will ask you to format these partition's b/c it cannot read them. Do not format them because you will then have issues mounting those partitions and you would have to RUU/PB31IMG.zip
I have already seen this happen to more than two people.
AndroidBruce said:
When you mount your phone via usb mass storage it is mounting more than just the /sdcard/ and /emmc/(internal storage)
It is mounting /data/ and /system
If you're running Windows it will ask you to format these partition's b/c it cannot read them. Do not format them because you will then have issues mounting those partitions and you would have to RUU/PB31IMG.zip
I have already seen this happen to more than two people.
Click to expand...
Click to collapse
Thanks for the pro-tip, I could see myself having done this.
I've had multiple lock ups and reboots but the first day was good.
Sent from my Incredible using XDA App
seanmcd72 said:
third one is that you may experience a random reboot or suddenly get a black screen and unresponsive phone when using wifi.
Click to expand...
Click to collapse
Gah, that's still happening with 6.0.1? I was hoping that would be fixed since the official source drop from HTC.
I'd really like to give an AOSP ROM a good run on my Inc, but that's a deal killer for me.
Thanks for the heads up though.
ardax said:
Gah, that's still happening with 6.0.1? I was hoping that would be fixed since the official source drop from HTC.
I'd really like to give an AOSP ROM a good run on my Inc, but that's a deal killer for me.
Thanks for the heads up though.
Click to expand...
Click to collapse
I have had NO reboots at all since putting 6.0.1 on 2 days ago - and I connect to Wifi at least 50% of the time. Today, I moved toward overclocking, but for the past 2 days I have been running stock speed
ncwildcat said:
I have had NO reboots at all since putting 6.0.1 on 2 days ago - and I connect to Wifi at least 50% of the time. Today, I moved toward overclocking, but for the past 2 days I have been running stock speed
Click to expand...
Click to collapse
I was also fine for over a day. Then today I have had to lockups, where the screen was black and only a bat pull fixed it plus one random reboot.
jratzo said:
I was also fine for over a day. Then today I have had to lockups, where the screen was black and only a bat pull fixed it plus one random reboot.
Click to expand...
Click to collapse
Exactly what I experienced. I went half a day with it seeming perfect, then out of the blue I pick up the phone and it's just off and nothing I do will get it to come on. It's either pull the battery or wait several minutes and suddenly it finally reboots on it's own. It doesn't happen to everyone, but it happens to enough people to say it is a definite unresolved issue. It's very good otherwise, as soon as these little issues are cleared up It will be the ROM for me.
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.
So here's the situation and this is literally the 3RD time this phone has done this. I'll be on a ROM on my rooted unlocked galaxy nexus, and randomly I'll be opening my texts or contacts or something and my phone will reboot. No big deal right? But then it just boot loops. Endlessly. If I try to restore a nandroid from a different ROM, it'll get almost done then won't be able to restore /data. I know it's not a bad nandroid backup cuz I switch back and forth between them all the time. I can't flash any rom, it'll be a boot loop, can't restore a nandroid,so I always have to end up flashing a stock image and start from scratch again.
I've seen this problem before after it happened the first time and found that flashing stock img fix. I have two questions: Why does it do this randomly every month? It's like my bootloader goes MIA or something for no reason. What would cause it to do this and literally, almost once every 30 days?
Second question: Is this a stable phone? I'm coming from the nearly unbrickable Captivate and I've done some crazy stuff to that phone and always managed to recover it, a couple times when it shouldn't have even worked at all. But yet this thing breaks down almost every month. Didn't flash anything new, didn't flash anything incompatible, nothing. Everything was running smooth. Then all of a sudden reboot, boot loop, backups dead, roms on SD card are useless.
Can someone please fill me in on what's going on with this? lol this is my 5th rooted android phone, not a developer or a themer or anything, but I know quite a bit about what would cause a phone to do whatever. Any insight would be great. Thanks guys!
Wich roms are you trying? Wich rooting methods? Wich flashing method? Are you using adb and fastboot?
Edit: does the issue happens on stock?
So far my phone its rock solid stable and buttery smooth fast after 3/4 months
Galaxy Nexus AOKP m5 Franco kernel m3
It first happened on liquid rom. I rooted via Samsung gnex toolkit. It happened again on gummy 1.2.0 honestly I wasn't on stock long enough to see how stock ran lol I don't use adb or fastboot often. Just to root and recently, to flash a stock image every time this happens
Sent from my Galaxy Nexus using XDA
I'd try rooting properly by using fast boot and flashing a superuser.zip. It may be that the toolkit is not working properly and you have a bad recovery. Something is wrong if this is happening. Its not too hard...
Sent From My Sprint Galaxy Nexus via XDA Premium
I recently have spent a decent amount of time trying to get my inc2 to boot JB without extreme lag(maxed out CPU). I've ran JB quite a few times until one day I overclocked to 1.5GHz and my phone boot looped and could never get JB or ICS to run properly. Its been reported that over clocking over 1.3GHz can break the partition on your phone and even lose root. If u have similar problems this is what I did -
Put the stock ruu GB 2.3.4 on the root SD card as pg32img.zip
Boot into boot loader and click vol up to accept update.
you are now on the latest stock gb without root but s-off will b preserved
download super one click and htc drivers to gain root.
reboot
I flashed twrp thru goo manager cuz that it's what I prefer. Wipe and flashed dkstunna's build 3 with 4.2 gapps and boom BACK TO FAST JB in under 30 min.
hope this helps someone! hit thanks if it did
next I hope to help on the main thread one day, Ive flashed almost every ics jb Rom and would luv to help
Sent from an incredibly running JB inc2
Can anyone verify this works? Not that I doubt you OP, just wondering if this has worked for anyone else?
Quick question.
I have been rooted for so long I've almost forgotten how it is done but I don't remember Super One Click supporting the DInc2. Does this mean it does root 2.3.4?
yes super one click works for inc2, and yes it will root 2.3.4. s off is the hard part on 2.3.4 if ur not already, so be s-off. I'm sure this will work differently for everyone cuz god knows why ics jb stopped working right in the first place. I bet kernel source would fix this too...
Well,
Tried it, and it didn't do the trick.
Still no JB for me.
Frustrating!
I'm running PA for months now and it hasn't locked up or lagged. I came from Venom before. I wiped everything except SD card, installed CM10 10/3, booted, flash PA, booted, flashed gapps and kernel. It booted up just fine for me.
I also flashed the firmware in the Venom thread. I don't use v6supercharger, 1024MHz smartassv2, and I undervolt -50.
TheAtheistReverend said:
Well,
Tried it, and it didn't do the trick.
Still no JB for me.
Frustrating!
Click to expand...
Click to collapse
I was in a bit of a panic cause i was using viper, went to aeroevans 11/13 jb, it worked for about 6 hours and then the massive lag and boot loops started. I couldn't flash any ics/jb aosp rom, I tried mimicry, dkstunna, and aeroevean's cm9/10. all non usable, crazy lag and boot loops. viper seemed to flash fine though.
I did try the solution in this thread and it didn't seem to work so I reflashed viper formatting using aroma. I let it boot and settle. then i formated all partitions in 4ext and reinstalled viper without formatting in aroma and i let it boot and settle, finally i reformatted all partitions in 4ext, installed aeroevan's 11/13 with latest jb gapps and all has been great for the past few days. fingers crossed.
I have tried just about everything. I can't think of anything else to try. I wish we knew why some phones were doing this.
The first thing I remember not going as usual on my phone was MIUI was not installing properly. It would hang on "updating boot" during install. I couldn't for the life of me get it any farther than that. The next thing was a JB NAND wouldn't boot properly, and then it was all down hill.
Back on the same bull**** of bootlooping on cm10. There should be a warning on the viper thread to not install it if you ever want to use another rom.
I don't know why but I'm not having any problems after viper...
I'm so fresh you can suck my nits...
None of us know the answer and that's the only common denominator. I'm just lucky that Miui works or i'd be sol
Uhh so yeah, tried this and it didn't work. Never had any problems with the phone before I got rid of ViperInc. I was on the latest firmware, every ROM flash was a totally clean one, followed the instructions in the OP and CM10 Global is just sitting here bootlooping. I know the dev isn't responsible for what happens to our phones, but multiple cases of the same seemingly unsolvable problem says there's something wrong with that ROM, imho. ****ing bogus.
Does anyone know if.the devs will try n make a fix or maybe implement one in the next build?
Sent from my HTC Droid Incredible 2 using xda app-developers app
chillybean said:
Does anyone know if.the devs will try n make a fix or maybe implement one in the next build?
Sent from my HTC Droid Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
It's not the cm10 devs' problem
Didn't say it was cm10s dev problem its the viper dev problem ..its an awesome.Rom but when some problem as bad as this with many ppl affected ..in my opinion I think the team should at least help ..when ppl start seeing this they aren't gonna want to flash this Rom...then there would be no point in developing it unless for the ppl that WANT to stay on sense...all I asked was if the team was aware n if they plan on a fix or a disclaimer that this Rom may poison your phone so it does happen to anyone else ..no need to be a smartassv2 lol I'm just asking and I'm sure a lot of ppl are too
Sent from my HTC Droid Incredible 2 using xda app-developers app
after getting JB to work for awhile I decided to flash the .312 radio, booted and 5 min later I get jelly beans to the face... now I'm stuck on viper again. I tried multiple times to recreate whatever fixed it the first time and I get nothing. I remember reading somewhere awhile back that going stock s-on then going s-off root might solve the problem
chillybean said:
Didn't say it was cm10s dev problem its the viper dev problem ..its an awesome.Rom but when some problem as bad as this with many ppl affected ..in my opinion I think the team should at least help ..when ppl start seeing this they aren't gonna want to flash this Rom...then there would be no point in developing it unless for the ppl that WANT to stay on sense...all I asked was if the team was aware n if they plan on a fix or a disclaimer that this Rom may poison your phone so it does happen to anyone else ..no need to be a smartassv2 lol I'm just asking and I'm sure a lot of ppl are too
Sent from my HTC Droid Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I don't think it is ViperROM dev's problem, nor is their responsibility to help. They make it very clear they hold no responsibility for what happens to your device when you flash their ROM. They are also not making any money from the free rom they put out for us to enjoy, so their is no driving force really behind their desire for "fans" if you will.
That being said, it would be nice if they could help and did. Has anyone directly, and nicely asked Nitsuj or any of the Viper team for help?
fen0m said:
after getting JB to work for awhile I decided to flash the .312 radio, booted and 5 min later I get jelly beans to the face... now I'm stuck on viper again. I tried multiple times to recreate whatever fixed it the first time and I get nothing. I remember reading somewhere awhile back that going stock s-on then going s-off root might solve the problem
Click to expand...
Click to collapse
Doubt it. I went all the way except for S-off and re-rooted but it still will not load any JB rom I try. But by all means, it might be worth trying if you're so motivated. Seems like some things work for some, but not for others at this point.
Just got back onto CM10. Was on Viper, did full wipe x2, formatted partitions to ext3 in 4ext Recovery, fix permissions, then formatted cache.
Then...here's the weird part....since Mimicry was the only non GB Rom I could get to at least boot, I tried a clean flash of it. Used only the baseline items in the Aroma installer (only things I installed were the jb animations, trebuchet, v6, and daemon). Booted into Mimicry and let it settle without signing in to Google. Profit!
Next phase was a full wipe x2, flash newest CM10, flash GApps, then format cache.....double profit! Hopefully this will hold up. Will report back once its had time to fully settle.
Sent from my Incredible 2 using xda premium
Sry didn't mean to say it like that but I know its not their responsibility..I just asked if they try to figure this out..I'm gonna try this mimicry method...I hope I profit like twice
Sent from my HTC Droid Incredible 2 using xda app-developers app
I wouldn't call it a method really....I think I may have just gotten lucky
Sent from my Incredible 2 using xda premium
Is there a way to undo the leaked ICS firmware I've flashed? I've been hit with the post viper CM10 lag that seems to be going around and I thought I'd try everything to get rid of it.
Have you tried chilly's super wipe? There is a thread for it.
Sent from my Incredible 2 using xda app-developers app
Same here. I super wiped two days ago and formatted my sd card. I thought I had it and my phone ran fine for a day. I charged it over night and when I took it off the charger, it was shot again today. When it actually boots, I can't get past the unlock screen. It holds there for about a minute before going into a boot loop. I didn't even think of the ics firmware. Maybe I'll try going back to stock tomorrow and then reflashing cm10.
Sent from my A500 using xda app-developers app
I don't know if it's the firmware or not, but I thought it was worth a shot. I have used chilly's wipe and I have gotten the huge lag since then. I'm running his PAC rom now and I used his wipe twice before I installed. I've also v6 supercharged so I'm waiting to see if it happens again. Is there a copy of the old firmware that is flashable like the new one?
Baloeb said:
I don't know if it's the firmware or not, but I thought it was worth a shot. I have used chilly's wipe and I have gotten the huge lag since then. I'm running his PAC rom now and I used his wipe twice before I installed. I've also v6 supercharged so I'm waiting to see if it happens again. Is there a copy of the old firmware that is flashable like the new one?
Click to expand...
Click to collapse
There at threads for different ruu's. I'm not sure which one you need. Search through those. Also, when your phone starts lagging try connecting to a computer in adb I think, someone posted that that fixed theirs temporarily. I think they narrowed it down to the SD card being bad and with it connected it dismounts the SD card and doesn't have the problem. That might help.
Sent from my Incredible 2 using xda app-developers app
NeverSeparate said:
There at threads for different ruu's. I'm not sure which one you need. Search through those. Also, when your phone starts lagging try connecting to a computer in adb I think, someone posted that that fixed theirs temporarily. I think they narrowed it down to the SD card being bad and with it connected it dismounts the SD card and doesn't have the problem. That might help.
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I'll give that a shot next time. Usually I just pull the battery and install cm7 so I have a working phone.
Okay, 1st you need to return to stock:
http://forum.xda-developers.com/showthread.php?t=1599767
After this process you need to flash cwm and superuser:
I believe this thread http://forum.xda-developers.com/showthread.php?t=1751796 has all the files (including adb) set up in one .zip under "TACOROOT"
Or just download them from here:
https://dl.dropbox.com/u/77740451/recovery-clockwork-5.0.2.0-vivow.img
https://dl.dropbox.com/u/77740451/Superuser-3.0.7-efgh-signed.zip
This is what I did to remove the firmware. I didn't have the lag, but I was hoping to solve camera issues.
SkinnyT said:
Same here. I super wiped two days ago and formatted my sd card. I thought I had it and my phone ran fine for a day. I charged it over night and when I took it off the charger, it was shot again today. When it actually boots, I can't get past the unlock screen. It holds there for about a minute before going into a boot loop. I didn't even think of the ics firmware. Maybe I'll try going back to stock tomorrow and then reflashing cm10.
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
Just a quick note...When I was running CM10 I would get the boot loops at the lock screen, but if I just let it alone, it would loop 2-3 times and then settle in. It took a while, and I avoided rebooting my phone at all costs, but have you just let it sit for about 10 minutes to see if it pulls out of the boot loop? Mine usually came out in less than 5, but you never know. After it booted up it settled down and ran fine. I've never used the Venom rom or super wipe though, so ymmv.
gtdtm said:
Just a quick note...When I was running CM10 I would get the boot loops at the lock screen, but if I just let it alone, it would loop 2-3 times and then settle in. It took a while, and I avoided rebooting my phone at all costs, but have you just let it sit for about 10 minutes to see if it pulls out of the boot loop? Mine usually came out in less than 5, but you never know. After it booted up it settled down and ran fine. I've never used the Venom rom or super wipe though, so ymmv.
Click to expand...
Click to collapse
Mine doesn't boot loop, it runs great for a few days then starts to lag so bad it's unusable.
Baloeb said:
Mine doesn't boot loop, it runs great for a few days then starts to lag so bad it's unusable.
Click to expand...
Click to collapse
Some have reported that it's linked to a usb / sdcard / storage issue. Lag starts after connecting.
Sent from PAC-land