I have seen multiple users here and on Rootzwiki state that they can't run AOSP ROMS. All the users can run a Sense ROM with no problem, but as soon as they load an AOSP ROM they get freezes.
Edit:
In recovery, be sure to do a full wipe of data, cache, and dalvik cache. It is also recommended that you format your system partition as well. Then install ROM.
If you choose to format the SD card, be sure to back up your important files first.
If you still experience problems running AOSP ROMs (CM7, Liquid, OMFGB, Pool Party) share your results.
i was tested different rom's and i've never had an issue flashing AOSP roms. I flashed a few ruu and sense rom.
sjpritch25 said:
i was tested different rom's and i've never had an issue flashing AOSP roms. I flashed a few ruu and sense rom.
Click to expand...
Click to collapse
I haven't had the issue myself, but I've seen a handful that have. No one has figured it out yet.
Edit: if you experienced this it may help to figure it out
JAS_21 said:
I haven't had the issue myself, but I've seen a handful that have. No one has figured it out yet.
Click to expand...
Click to collapse
Its a myth.
I don't see a reason why it wouldn't work.
Sent from my Incredible 2 using xda premium
xHoLyx said:
Its a myth.
I don't see a reason why it wouldn't work.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
I've seen more than one user with the issue. One is a long time forum member.
xHoLyx said:
Its a myth.
I don't see a reason why it wouldn't work.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Definitely not a myth. I had issues with aosp roms not mounting data or cache properly. However, newest cyanogen fixed it. Were trying to figure out where the problem stemmed from
I am having this issue. I was actually running CM7 nightly (with Tiamat) when the problem started. I plugged my phone into my stereo before I went to bed and listened to an album. When I woke up, the screen would not turn on. I rebooted and was stuck in boot loop. I tried to wipe the caches, but got stuck in boot loop. I then upgraded to the most current nightly (with a full wipe), but the phone suffered from the sluggish performance and screen issue.
I have flashed just about every ROM listed in the dev section. Prior to having the issue, I was running MIUI. Prior to that, I was running Newts Incredible 2 HD.
I do NOT have this issue with TSM Pool Party or the past week or so of CM7 nightlies.
I do have this issue with the AOSP Liquid Rom, OMGB, OMFGB.
All sense ROMS work.
I was running andrev_oc when this happened. No overclocking, but did have screen on and screen off profiles.
I have attempted to flash with CWM and 4ext recoveries. Even when converted to ext4, I still have the issue.
Sorry for all the info. I just tried to give as much detail as possible.
Hope this helps,
Matt
Thank you. If anyone else is having, or had this issue let us know what ROM you noticed the issue on, and what you were running prior.
Also, if anyone has a fix it can be posted here.
I have seen this as well. It happened to me when I flash 9.30 MIUI because I was bored. The next morning I restored my cm7 backup and it worked just fine until the screen went off and I would have to pull the battery to boot it back up. Did this several times until I remembered seeing this issue. After several wipes and restores the problem stayed. I finially just flashed a nightly #91 believe I was on 87 before and it has worked fine since. Not sure what was the problem or why it worked flashing a different nightly but I was glad it did.
dch921 said:
I have seen this as well. It happened to me when I flash 9.30 MIUI because I was bored. The next morning I restored my cm7 backup and it worked just fine until the screen went off and I would have to pull the battery to boot it back up. Did this several times until I remembered seeing this issue. After several wipes and restores the problem stayed. I finially just flashed a nightly #91 believe I was on 87 before and it has worked fine since. Not sure what was the problem or why it worked flashing a different nightly but I was glad it did.
Click to expand...
Click to collapse
Were you running a sense ROM before Miui?
I switched from newts Inc hd to liquid, and I had all kinds of problems with the SD card not mounting properly. I ran miui a long time ago with no problems.
Sent from my mobile typewriter.
Went from newts hd to liquid as well, tried restoring my cm7 backup and ran into lockups, reboots, and data lose. Any possibility liquid rom is behind this somehow indirectly? No shot at liquid, just maybe some corrupt files?
Sent from my Incredible 2 HD using xda premium
ftmaniac948 said:
Went from newts hd to liquid as well, tried restoring my cm7 backup and ran into lockups, reboots, and data lose. Any possibility liquid rom is behind this somehow indirectly? No shot at liquid, just maybe some corrupt files?
Sent from my Incredible 2 HD using xda premium
Click to expand...
Click to collapse
No, other AOSP ROMs were having same problem. It seems that data and cache don't mount properly after running certain ROMS.
It's starting to look like everyone that had problems with AOSP lockups had been running Inc2 HD prior. I'm not saying Newts ROM caused the issue, since I don't know the cause, but hopefully this can help someone to figure out the problem
Is there a fix? I am running liquid now with no problem. If the system doesn't mount properly when I try to switch, can I just wipe or format system and try to restore a backup or load another rom?
stelv said:
Is there a fix? I am running liquid now with no problem. If the system doesn't mount properly when I try to switch, can I just wipe or format system and try to restore a backup or load another rom?
Click to expand...
Click to collapse
No, you should be fine.
Most people have no problems. This is for people experiencing random lockups and freezes, not just wit Liquid, but other AOSP ROMs also
JAS_21 said:
It's starting to look like everyone that had problems with AOSP lockups had been running Inc2 HD prior. I'm not saying Newts ROM caused the issue, since I don't know the cause, but hopefully this can help someone to figure out the problem
Click to expand...
Click to collapse
Iv been using newts hd rom for a long time now, and never experienced problems with it before
Sent from my Incredible 2 HD using xda premium
For me it was data and cache that didn't mount properly. But try the newest cyanogen and see, its the only one that worked for me
ftmaniac948 said:
Iv been using newts hd rom for a long time now, and never experienced problems with it before
Sent from my Incredible 2 HD using xda premium
Click to expand...
Click to collapse
I'm not saying that his ROM isn't running right, but it seems that people are having issues going from that ROM to an AOSP ROM.
Edit: There may be nothing wrong with his ROM, but maybe something is being left behind or not formatted after flashing the AOSP ROM.
Could Newts rom being formatted to Ext4 cause issues when flashing back to a Aosp rom? I've ran Newts Inc2HD and flashed back to Omfgb, but I've been using Ext4 for a while now for my system/data/cache file system (since switching to 4ext recovery). After flashing back, my Aosp rom ran fine. But my backup of Omfgb was already formatted to run on Ext4. Now if my backup was formatted to run on Ext3 for the data/cache, I would think this may cause issues if I don't reformat before flashing a new rom... Just a thought anyway.
Related
I'm running the latest version of Clockworkmod which looks like it is most likely my problem for constant force closes on all my apps but i'm wondering if i can downgrade clockworkmod version to fix this if rom manager and all my other apps keep force closing? Any suggestions would be VERY appreciated. Sorry if this is posted somewhere else also I tried a search but didn't see any solutions.
I think you and I might have the same problem going on. All of my apps are force closing, but I am not sure if mine has to do with clock work mod or not. I still have not found a solution to my problem.
This may seem obvious to you and I apologize if it does but, did you wipe data and cache prior to flashing MIUI? I was running it recently without any issues at all. And I keep the latest version of CWM. It's an excellent rom. Smooth as butter.
Edit: I was running MIUI 1.2.19 with invisiblek, #28, by the way.
Sent from my ADR6300 using XDA App
There is some speculation that CWM3 isn't wiping as well as CWM2 did... I can certainly confirm that it does not seem to clean everything out for a new MIUI install. On MIUI forums you can find a script to wipe everything first, or you can just open the "mounts" section and manually format /boot and /system. This seems to do the trick.
igknighted said:
There is some speculation that CWM3 isn't wiping as well as CWM2 did... I can certainly confirm that it does not seem to clean everything out for a new MIUI install. On MIUI forums you can find a script to wipe everything first, or you can just open the "mounts" section and manually format /boot and /system. This seems to do the trick.
Click to expand...
Click to collapse
I can't say I've had any issues, personally but, I've definitely seen several comments about this around the forums. I plan on flashing back to MIUI soon. Just to be safe, I'll be looking for that script before I do it. Thanks for the heads up.
Sent from my ADR6300 using XDA App
The way I solved my mass force close issue was to do a factory reset and then flash the rom I wanted. Maybe that will solve your problem also?
I ended up just uninstalling and reinstalling an app a couple times and it started working just fine, another question though. What's the best version of miui? And also what are the miui ports for? New to this Rom but its pretty seemless
Sent from my ADR6300 using XDA App
Alright so this is odd, just updated to 1.1.28.1 version and none of my apps whether from the market or SD card will work on the first install, I must uninstall then reinstall for them to work. Anyone else have this going on? I guess its not a HUGE deal but still just weird
Sent from my HTC Incredible using XDA App
It seems likely that cwr 3 is a pos that is causing all these issues. I have started manually wiping everything needed to be wiped in mounts and my problems went away. Another alternative is to go back to cwr 2.5
Sent from my desire z inc port.
slong427 said:
I ended up just uninstalling and reinstalling an app a couple times and it started working just fine, another question though. What's the best version of miui? And also what are the miui ports for? New to this Rom but its pretty seemless
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
MIUI Ports are the current versions of MIUI. The person who was creating the Inc builds used to be NIX, but when he passed the torch to Warttack, they needed to call it something different in ROM Manager (different packager, different section I guess). So basically, you should always be using the latest in MIUI Ports.
Everything is force closing on my nook color cm7 SD card. I am not much of a techie...any help would be appreciated. thank you.
Try fix permissions in ROM manager. You should post this in the nook color forum though.
Sent from my ADR6300 using XDA App
Hi, my Evo is a launch one (HW002). Ive been running Magnus ROM for the last month, but today I decided to give Virus's ROM a try, and after download and 3 wipes of the usual suspects (cache, dalvik, data) plus the Format All zip, I flashed my ROM but when I came back I was stuck on a boot loop. So I nand back to Magnus again, and then decide to flash Kings 2.3 Sense ROM, and also had a boot loop! This has never happened before, and I was able to nand back to Magnus..... is there something wrong with my phone, that is not letting me flash ANY new ROM at all???
Well I don't own eco but I think u should format data and stuff before flashing and go back to stock and start all over and also I would never try a rom with the name virus smh
Sent from my SGH-T959 using XDA Premium App
Droga said:
Hi, my Evo is a launch one (HW002). Ive been running Magnus ROM for the last month, but today I decided to give Virus's ROM a try, and after download and 3 wipes of the usual suspects (cache, dalvik, data) plus the Format All zip, I flashed my ROM but when I came back I was stuck on a boot loop. So I nand back to Magnus again, and then decide to flash Kings 2.3 Sense ROM, and also had a boot loop! This has never happened before, and I was able to nand back to Magnus..... is there something wrong with my phone, that is not letting me flash ANY new ROM at all???
Click to expand...
Click to collapse
What recovery are you using to flash the rom? Clockwork or Amon ra? What radios are you on? Which Virus rom were you trying to flash? I've never had trouble.trying.to boot any of his.roms, they are usually solid.
Sent from my PC36100 using XDA App
k2buckley said:
What recovery are you using to flash the rom? Clockwork or Amon ra? What radios are you on? Which Virus rom were you trying to flash? I've never had trouble.trying.to boot any of his.roms, they are usually solid.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Amons recovery, latest radio and newest Virus 2.3 ROM. Ive never had trouble flashing ANY ROM before, and all of a sudden my phone is acting up. At least it is letting nand back to my previous ROM.
Droga said:
Amons recovery, latest radio and newest Virus 2.3 ROM. Ive never had trouble flashing ANY ROM before, and all of a sudden my phone is acting up. At least it is letting nand back to my previous ROM.
Click to expand...
Click to collapse
Hmm, that's odd. Are you sure the files you're trying to flash aren't corrupted? You said you did a full wipe, including a format all, so an improper wipe is ruled out. I unfortunately don't have a lot to suggest. I think if that was happening to me, I would first try reflashing my recovery, and then try wiping and flashing again.
Sent from my PC36100 using XDA App
k2buckley said:
Hmm, that's odd. Are you sure the files you're trying to flash aren't corrupted? You said you did a full wipe, including a format all, so an improper wipe is ruled out. I unfortunately don't have a lot to suggest. I think if that was happening to me, I would first try reflashing my recovery, and then try wiping and flashing again.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Already tried that, no go.
I guess Im stuck with my ROM for the time being....
Droga said:
Already tried that, no go.
I guess Im stuck with my ROM for the time being....
Click to expand...
Click to collapse
I wish I had more to try suggesting for you. Its odd that both of the roms you tried flashing were sense based 2.3 roms. I wonder if you're phone doesn't like the kernel that comes cooked into those roms. I think virus's 2.3 rom uses the same kernel as the 2.3 king's rom. Perhaps after you flash the rom, you could power off the phone, take out the sd card, and try booting it without the sd card in it. I've heard of weird booting issues being caused by an issue with the sd card. It certainly couldn't hurt anything to try it, but I would think that if that was the issue, you'd have trouble booting any rom. I'd still try it though.
k2buckley said:
I wish I had more to try suggesting for you. Its odd that both of the roms you tried flashing were sense based 2.3 roms. I wonder if you're phone doesn't like the kernel that comes cooked into those roms. I think virus's 2.3 rom uses the same kernel as the 2.3 king's rom. Perhaps after you flash the rom, you could power off the phone, take out the sd card, and try booting it without the sd card in it. I've heard of weird booting issues being caused by an issue with the sd card. It certainly couldn't hurt anything to try it, but I would think that if that was the issue, you'd have trouble booting any rom. I'd still try it though.
Click to expand...
Click to collapse
If his phone doesn't like the stock kernel, I'd recommend flashing a custom kernel in the same session, after wiping the cache and dalvik after he flashes the rom.
teh roxxorz said:
If his phone doesn't like the stock kernel, I'd recommend flashing a custom kernel in the same session, after wiping the cache and dalvik after he flashes the rom.
Click to expand...
Click to collapse
Right, which is definitely what I'd normally suggest. However, since he's trying to use the new Sense 2.3 roms, there arent really any custom kernels for those roms yet. Some people have reported success with Netarchy's, but it breaks the camera app. Other people reported loops with netarchy. Basically, there arent any custom kernels for any 2.3 GB + sense roms yet, so his kernel switching is limited. He could try another one, and may have it work, as some other people had reported. But his camera won't work!
k2buckley said:
Righ, which is definitely what I'd normally suggest. However, since he's trying to use the new Sense 2.3 roms, there arent really any custom kernels for those roms yet. Some people have reported success with Netarchy's, but it breaks the camera app. Other people reported loops with netarchy. Basically, there arent any custom kernels for any 2.3 GB + sense roms yet, so his kernel switching is limited. He could try another one, and may have it work, as some other people had reported. But his camera won't work!
Click to expand...
Click to collapse
I had already tried another ROM ( Myn's Warm Z) just to see if it is the kernels and the Sense 2.3 combination, but that didnt give me any problems at all. So Im guessing it is the kernel included in those ROMS. I will try your suggestions, though, just to see if they actually make a difference. Thanks for the kind help.
k2buckley said:
Right, which is definitely what I'd normally suggest. However, since he's trying to use the new Sense 2.3 roms, there arent really any custom kernels for those roms yet. Some people have reported success with Netarchy's, but it breaks the camera app. Other people reported loops with netarchy. Basically, there arent any custom kernels for any 2.3 GB + sense roms yet, so his kernel switching is limited. He could try another one, and may have it work, as some other people had reported. But his camera won't work!
Click to expand...
Click to collapse
True...but from what I've heard [haven't flashed it] but some have reported success with stock kernel 15, and it not breaking anything, so he could try that...
teh roxxorz said:
True...but from what I've heard [haven't flashed it] but some have reported success with stock kernel 15, and it not breaking anything, so he could try that...
Click to expand...
Click to collapse
This is true.
Hey OP, you catching this? Lol. Try flashing the stock HTC 15 kernel right after you flash the rom, but before you boot. See if that makes any difference.
This is why teamwork wins.
teh roxxorz said:
True...but from what I've heard [haven't flashed it] but some have reported success with stock kernel 15, and it not breaking anything, so he could try that...
Click to expand...
Click to collapse
k2buckley said:
This is true.
Hey OP, you catching this? Lol. Try flashing the stock HTC 15 kernel right after you flash the rom, but before you boot. See if that makes any difference.
Click to expand...
Click to collapse
I will do this and come back with results in a while.
Muy Bien amigo.
I'll be floating around.
teh roxxorz said:
This is why teamwork wins.
Click to expand...
Click to collapse
Always true!
Hopefully the different kernel helps him out!
Tried stock kernel #15: no go.
Thanks for the help, though!
Droga said:
Tried stock kernel #15: no go.
Thanks for the help, though!
Click to expand...
Click to collapse
Damn. That sucks. I'm not sure what would be causing that. You wiped, you tried a different kernel, your radios and PRI are updated, you tried booting without the SD card in place. I'm not sure what'd send you to bootloops. Did you happen to try updating to the most recently leaked radio? The one that was in the dump from the leaked gingerbread rom? Although I doubt that'd make any difference, but you never know. I flashed it the other day, and it works just as good as all the other ones. I never really notice a major difference from changing radios. But the leaked one does work.
Droga said:
Tried stock kernel #15: no go.
Thanks for the help, though!
Click to expand...
Click to collapse
Sorry man.
teh roxxorz said:
Sorry man.
Click to expand...
Click to collapse
No worries. I was able to install a new custom ROM just now (Kings R3) and it installed just fine. I will try again to install the other ROMS just to see if it will work today.
I am currently running EvoKings GB RC3 and loving it. But since I can't leave well enough alone, I want to update to the RC4.
I just have a couple of questions concerning this ROM.... I see where he mentions its based on CM7... is it based on CM7 7.0.0.0 or CM 7 7.0.2.1?
Also will I need to do the GPS fix again and update PRL, as I assume I have to wipe dalvik/cache to update from RC3 to RC4 (as it seems its more than just an update)?
Speaking of the GPS fix, when I did it, I was on RC3 of the EvoKings GB rom, and this is the steps I followed:
Booted into recovery
Made a Nandroid backup
Wiped All Data
Flashed into a backup sense rom I have (Mikfroyo 4.6)
Performed GPS fix and updated PRL
Booted back into recovery
Performed Nandroid restore (no data wipe)
Back into RC3
Was that correct... that I dont do a data wipe and just do a nandroid restore? I have been reading so many conflicting reports on this. My assumtion was to always wipe data before doing a restore.
Thanks everyone.
First of all, if you're updating a current rom, them all you should have to do is wipe cache & dalvik and then flash the updated rom. As for not wiping data, no, it isn't necessary, however, I'm one of the people who do especially if I'm changing roms. I don't want any remnants of the previous rom.
posting & replying via the XDA Premium app.
dougjamal said:
First of all, if you're updating a current rom, them all you should have to do is wipe cache & dalvik and then flash the updated rom. As for not wiping data, no, it isn't necessary, however, I'm one of the people who do especially if I'm changing roms. I don't want any remnants of the previous rom.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Ok cool, thanks. When doing the GPS fix, is the info stored somewhere else, which is why it doesnt get removed when doing a wipe of stuff?
Trying to figure that out... since yeah I am worried about having some type of conflict when switching from a sense to an AOSP rom. I havent had any issues so far with RC3 doing that, minus some issues with the screen not coming on with a button press while playing music.. but not sure if thats just something with the ROM itself or the GPS fix.
I am not sure where the gps fix is stored, but there should be no conflicts. I have switched between AOSP and Sense tons many times since I did the fix and have never had any problems.
Sent from my Infected Evo using Tapatalk Pro!
whiterider13 said:
I am not sure where the gps fix is stored, but there should be no conflicts. I have switched between AOSP and Sense tons many times since I did the fix and have never had any problems.
Sent from my Infected Evo using Tapatalk Pro!
Click to expand...
Click to collapse
+1.....I've never had to apply a GPS fix and I, too, have switched between AOSP and Sense numerous times. As a matter of fact, my current rom is Salvage-Mod and the GPS works as it should and I still didn't have to apply a fix.
posting & replying via the XDA Premium app.
I had to do the gps fix when I first switched to cm7 rc2. Since then I have never had to redo it nor have I had any issues.
Sent from my b3 Infected Evo using Tapatalk Pro!
whiterider13 said:
I had to do the gps fix when I first switched to cm7 rc2. Since then I have never had to redo it nor have I had any issues.
Sent from my b3 Infected Evo using Tapatalk Pro!
Click to expand...
Click to collapse
Thank you both, thats what I wanted to hear. I havent wanted to switch roms because I got the GPS working and I didnt want to switch roms and have it broke again. Thank you!
No prob man, just glad I could help.
Sent from my b3 Infected Evo using Tapatalk Pro!
What build of CM 7 is this rom built off of?
Hello forum,
I recently switched from CM7 because I was having some issue with random resets and FCing with Maps that slow down and shut off my phone. I flashed to the New Fresh ROM to try it out. That worked fine, but I missed the pull down notification bar. I tried Salvage-Zen but got stuck in a boot-loop and then I tried Salvage. I got past the boot screen but when the Android pops up even though I click I can't go any further. Does anybody know of a possible solution?
Few suggestions: Are you wiping properly, do you have the latest recovery (amon ra or clockwork), are you flashing gapps, did you update to all the latest radios/wimax/prl?
Why don't you try to flash decks aosp rom!
http://forum.xda-developers.com/showthread.php?t=1078558
Sent from my PC36100
jjchdc said:
Hello forum,
I recently switched from CM7 because I was having some issue with random resets and FCing with Maps that slow down and shut off my phone. I flashed to the New Fresh ROM to try it out. That worked fine, but I missed the pull down notification bar. I tried Salvage-Zen but got stuck in a boot-loop and then I tried Salvage. I got past the boot screen but when the Android pops up even though I click I can't go any further. Does anybody know of a possible solution?
Click to expand...
Click to collapse
do you do a clean wipe before flashing roms or are you just installing one on top of the other. I would suggest looking for Caulkins format all zip and run it prior to flashing a rom
Same problem on friends phone just use amon RA wipe everything twice and flash and be patient with the white evo 4 g screen it may take a while there.
Sent from my PC36100 using XDA Premium App
I'm wiping completely using both Clockwork and Amon but its still a no go and I flash falls when using aosp. I'll try that Rom and report the results.
Sent from my PC36100 using XDA App
playya said:
do you do a clean wipe before flashing roms or are you just installing one on top of the other. I would suggest looking for Caulkins format all zip and run it prior to flashing a rom
Click to expand...
Click to collapse
The format all was just what I needed. Thank you very much!
Hey fellow gnex community! I recently left stock rom due to freezes and random reboots. I've tried out various rom and kernel combinations this week such as xylon/AK, Purity/AK, AOKP/franco/lean, CM10.1/trinity/franco, Rasbean/trinity, PA/lean/franco/trinity/AK and Xenon.
The problem is they all freeze and reboot constantly after 2 minutes of use. I never changed the kernel settings and this is only happening on 4.2.1 roms. My favorite rom/kernel combo would be purity/AK, Xylon/AK but they freeze, wifi disconnects and never connects back and reboots constantly.
So the question is why is this happening to my phone recently and are there specific kernel settings that will stabilize the roms or is it just my phone?
Any help would be great,
thanks.
I haven't had that problem before, and I have flashed several roms (though not a custom kernel in a while)
Faulty hardware perhaps?
Sent from my Transformer Pad TF300T using Tapatalk HD
Lord Yurij said:
I haven't had that problem before, and I have flashed several roms (though not a custom kernel in a while)
Faulty hardware perhaps?
Sent from my Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
but this never happened on 4.1, 4.0.4 etc. That's what's worrying me.
4.2.1 isn't exactly highly regarded for its stability....
I reccomend going back to a good 4.1.2 rom. You aret missing anything anyway
nav200 said:
but this never happened on 4.1, 4.0.4 etc. That's what's worrying me.
Click to expand...
Click to collapse
I would do a full wipe and fastboot flash the stock images from Google to see if this helps. Mind you, your internal memory will be wiped so back up all of your photos etc..
crixley said:
4.2.1 isn't exactly highly regarded for its stability....
I reccomend going back to a good 4.1.2 rom. You aret missing anything anyway
Click to expand...
Click to collapse
but I heard people change the kernel settings and the phone will become smoother/stable? I really love some of the features from 4.2.1 that's the reason I'm a bit hesitant to go back to 4.1.2
Try a full wipe, and fast boot a stock image on and proceed from there.
Sent from my A100 using xda app-developers app
plznote said:
Try a full wipe, and fast boot a stock image on and proceed from there.
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
I've done that twice already and usually wipe after it freezes but then still happens
Are you sure you know how to flash? Not trying to offend but it saves a lot of time if your a noob.
I currently wipe dalvik cache 3x, cache 3x, and factory reset 3x in twrp. I read somewhere its safer to wipe like this or use super wipe scripts or w.e
I am running the latest rasbeanjelly with latest rasbean gapps and latest lean kernel. I haven't had any resets and haven't tweak anything. May I also add that when I do get errors with roms normally when I flash extra mods I always go back to recovery and hit fix permissions. Idk why but it does solve some issues.
Good luck
Sent from a slice of Galaxy Nexus with some Rasbean Jelly!
lol. Ya I've been flashing roms for like a year and it's only recently these issues are popping up. I do pretty much what everyone does - wipe data, wipe cache, wipe dalvik, flash rom, flash gapps and flash kernel. I never use mods so nothing to worry about there.
Try flashing rom and gapps only without a custom kernel.
If you've fully formatted your drive, have updated recovery, and are positive you have good downloads then your problem is most likely hardware related
Try the kernel cleaner script before flashing/changing between kernels.
It's a cwm flashable .zip.
Alright will do as suggested
How about fastboot flashing the stock rom's .img-es? (Galaxy Nexus ToolKit is the easiest way to do it)
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Alright so it seems like the rom HumberOS with built in kernel did the job. Been using the phone for about 4 hours non stop and no freezes or reboots so far. Finally something stable for my phone! Thanks for the help everyone!
update: After a day without any hiccups on the humber os rom, my phone finally froze and rebooted. Since I was using cwm, I decided to see if twrp would solve the problem. I restored my phone to stock and started from scratch by installing twrp. Then I decided to give PA a try and to my surprise no reboots or freezes at all but will have to wait a day to confirm.
nav200 said:
update: After a day without any hiccups on the humber os rom, my phone finally froze and rebooted. Since I was using cwm, I decided to see if twrp would solve the problem. I restored my phone to stock and started from scratch by installing twrp. Then I decided to give PA a try and to my surprise no reboots or freezes at all but will have to wait a day to confirm.
Click to expand...
Click to collapse
You did restore the factory images by running the update script included in the package right? This will make sure all data is up to date.. Fastboot erase all partitions first as well..
Sdobron said:
You did restore the factory images by running the update script included in the package right? This will make sure all data is up to date.. Fastboot erase all partitions first as well..
Click to expand...
Click to collapse
yup did all that and everything seems to be going fine so far
So... what would be causing the problem you think?
You installed TWRP and PA both at the same as I can read in the previous posts?
So that way we will never know if it's a recovery problem, or ROM problem...
Well, as long as your device doesn't freeze and/or reboot we should be happy I guess.