so i thought id take it upon myself to download the latest aokp jb build 3 and flashed it over aokp m6 after i did a full wipe and it installed perfectly but i rebooted my phone to check something and when i did it bootlooped i panicked cause i couldn't restore a backup or get it running again i got REALLY LUCKY and for some reason i was able to get my backup to restore after countless times of trying so now I'm back on m6 i fear of going back to aokp jb until i know it's safe to go from aokp m6 to aokp jb i can't brick another phone has any had this problem or i was just unlucky or what
Sent from my Galaxy Nexus using xda app-developers app
Try to wipe all data and reflash the rom,(including cache+dalvik cache) because every time you flash a rom with a different version of Android this procedure should be done to avoid problems like this
Wipe/Factory Reset
Wipe everything/factory reset and reflash rom and gapps. This will fix your issues. Good Luck!!
I wiped everything the first time im sorta scared to go through it again to see if it will work cause when i flashed it ran perfectly but i noticed when i was trying to change my softkey icons rom control kept force closing for some reason so that's when i rebooted and then i got the boot loop
Sent from my Galaxy Nexus using xda app-developers app
dont complain about issues if you dirty flash roms.
if you have problems with a dirty flash, wipe and then reflash.
Zepius said:
dont complain about issues if you dirty flash roms.
if you have problems with a dirty flash, wipe and then reflash.
Click to expand...
Click to collapse
I flashed everything perfect i wiped everything before i flashed the Rom so i didnt dirty flash ive been flashing roms since the first droid so i know how to flash unfortunately flashing this build of aokp didn't go to well for me
Sent from my Galaxy Nexus using xda app-developers app
I'm confused you flashed over M6 and didn't dirty flash? AOKP always recommends a full wipe. I flashed Build 3 last night, clean without a single issue. As for bricking, it's a Nexus. Kinda hard.
Sent from my Nexus 7
masully84 said:
I'm confused you flashed over M6 and didn't dirty flash? AOKP always recommends a full wipe. I flashed Build 3 last night, clean without a single issue.
Sent from my Nexus 7
Click to expand...
Click to collapse
I didnt flash directly over m6 without wipeing everything first before flashing the new aokp jb b3 i think thats where people getting alil confused
Sent from my Galaxy Nexus using xda app-developers app
jave16 said:
so i thought id take it upon myself to download the latest aokp jb build 3 and flashed it over aokp m6 and it installed perfectly
Click to expand...
Click to collapse
you said you just flashed it over.
Zepius said:
you said you just flashed it over.
Click to expand...
Click to collapse
My mistake i was trying to say coming from m6 i flashed from that to aokp jb after i wiped everything first
Sent from my Galaxy Nexus using xda app-developers app
Factory reset
Wipe cache
Wipe dalvic cache
Format system
Flash build 3
Flash gapps
Fix permissions
Reboot
Related
I was wondering if the radio could be the cause of this i upgraded to the fc04 /fc05 radios,i was under the impression that the framework was upgraded but not sure if i should flash back to the fa02 radios. I know stock radios have been a culprit in the past and was wondering if this still was the case . any input would be greatly appreciated. thanks in advance.Im on verizon lte by the way.
recovery, wipe cache/dalvik
if that doesnt do it:
recovery, format /system, reflash rom+gapps
if that still doesnt solve it
recovery, wipe data/factory reset, format /system, reflash rom+gapps
did you update radios with fastboot?
Yes to updating the radios, but I guess I'm wondering if the new radios are what are causing this I did a full wipe and actually a full restore. Right now I'm on the 5/10 will wait to get home to try new nightly in case I need the computer again.
Sent from my Galaxy Nexus using xda premium
jmk4412 said:
Yes to updating the radios, but I guess I'm wondering if the new radios are what are causing this I did a full wipe and actually a full restore. Right now I'm on the 5/10 will wait to get home to try new nightly in case I need the computer again.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Not likely
Sent from my Transformer Prime TF201
The first three or four roms I ever flashed on my G-Nex got caught in the bootloop after flashing with ROM manager. Turned out I was missing the wipe cache/dalvik step, and the same zips have since all worked fine.
OK well I'm getting ready to flash the latest nightly I'll let y'all know if I boot loop again. Thanks.
Sent from my Galaxy Nexus using xda premium
Before this I was in gummy toro ..then the first day that vicious jb roms out I manage to flash jb roms.. and its working.. then I try to flash different jb roms and it stock in Google animation..did everything clean flash delete all..then flash jb roms and again boot loop.. I unbrick my nexus using g.n. toolkit v7 back to stock..then set up everything then I try to flash a jb roms again yet again stock in boot loop.. any help pls... thanks in advance.
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
Before this I was in gummy toro ..then the first day that vicious jb roms out I manage to flash jb roms.. and its working.. then I try to flash different jb roms and it stock in Google animation..did everything clean flash delete all..then flash jb roms and again boot loop.. I unbrick my nexus using g.n. toolkit v7 back to stock..then set up everything then I try to flash a jb roms again yet again stock in boot loop.. any help pls... thanks in advance.
Click to expand...
Click to collapse
What are you using to flash? ADB, ClockworkMod Recovery? My rule for ROMS has been: download to phone and ensure download was completed successfully, reboot to CWM recovery, wipe cache, wipe Dalvik, install ROM, wipe Dalvik again, reboot.
If you can provide any more info regarding your process I can try and help you out.
Which galaxy nexus version is yours? Which Roms did you install? Did all three wipes?
Sent from my Galaxy Nexus using xda app-developers app
@ooddiittyy,
I'm using the one from gnex toolkit v7(clockwork mod touch recovery) I did wipe data /factory reset 3times,wipe cache and wipe dalvik and I also format system,cache and data..reboot and stock in boot loop.. I did that to 3jb roms and same thing happens..so I restore to ics.and this time boot up well. This is the first time I've in counter something like this..been flashing since vibrant.
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
I'm using the one from gnex toolkit v7(clockwork mod touch recovery)
Click to expand...
Click to collapse
this makes me die a little inside.
also, cwm touch is known to have issues with flashing stuff.
Oh.. so I think I should use rom manager.. to flash vicious-toro v3..
Sent from my Galaxy Nexus using XDA Premium App
Coming from gummy toro I manage to flash liquid vicious toro v1to v3 with no problem..then vanirbean rom and when I flash [email protected]_jelly that when its all started...I can flash ics rom and I can restore..but I can't flash jb roms..
Sent from my Galaxy Nexus using XDA Premium App
Try re downloading the rom again if its stuck at the Google animation let it sit for 5 to 15 minutes. It should boot up on its own. If not then there's something else wrong. But when I'm stuck at the Google logo with any jb rom I just let it sit. And eventually it boots up fine.
Sent from my Galaxy Nexus using xda premium
Thanks for the reply..I just flash it again I'm using 2 different jb rom and 2 different kernel..still stock in boot loop..I've waited for 30mins each in boot loop..before I had the vicious rom for almost a week then try different rom and this is what I got.. hayzz...
Sent from my Galaxy Nexus using XDA Premium App
did you change out your recovery to the regular cwm?
@zepius . Yep I did.. get it from from manager...
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
Thanks for the reply..I just flash it again I'm using 2 different jb rom and 2 different kernel..still stock in boot loop..I've waited for 30mins each in boot loop..before I had the vicious rom for almost a week then try different rom and this is what I got.. hayzz...
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
OK. Hmm. Go into recovery wipe everything 3x data/cache/dalvik cache flash the rom (don't flash a kernel) just the rom go back and reboot system now and see if that helps.
Edit: make sure u have over 50% battery before doing this.
Sent from my Galaxy Nexus using xda premium
I did that last night..wipe 3× everything.. did flash just rom, then rom with kernel, and also I did try wipe just cache and dalvik.. and also I did try format system, cache and data...
Edit: this is the first time it happen to me..even though I unbrick ,luck bootl. Factory reset .. its so weird...
Sent from my Galaxy Nexus using XDA Premium App
hey all,
not to highjack this thread, but I'm suddenly having the same issue.
I was on VanirBEAN v7 with the Popcorn Kernel that came with it.
I then flashed Franco's latest (384 GPU version).
Had no problems until last night when I let the phone run the battery all the way out and die completely. I let it charge for a bit, then tried booting and I'm stuck at the Google logo or get a reboot during the boot animation, depending on what I'm doing.
So here's what I've tried. All of these come with a wipe/cache/Davlik inbetween:
flash Vicious Toro JB V3 (stays on Google logo)
flash VanirBEAN v7 (reboots at VanirBEAN animation)
flash AOKP build 37 (reboots on the TeamKang animation)
selectively restore boot and system for AOKP 37 from a previous stable backup (reboots at the Android boot animation since in the ROM I had it set to not show the TeamKang boot animation)
I'm really at a loss right now. I'm trying a full restore on the backup I did before installing my first JB ROM.
edit: tried a full restore and i'm getting "Error while restoring /data!"... ugh.
Is my only choice to try Wugfresh's toolkit and restore stock and relock?
No one tried to fix permissions?
3x wipes, superwipe scripts..
That's not gonna help. If you wiped it once, it isn't there anymore.
I used wugfresh to back from fresh start and still if I flash jb rom I'm stock in jb rom.. done with 3 different jb rom. Same on all of them.. and yes I also did fix permission... I also did about mount and unmount regarding the system,cache and data... I'm tired of flashing and waiting in boot loop so I restore to ics gummy. I hope someone can help us with this...
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
I used wugfresh to back from fresh start and still if I flash jb rom I'm stock in jb rom.. done with 3 different jb rom. Same on all of them.. and yes I also did fix permission... I also did about mount and unmount regarding the system,cache and data... I'm tired of flashing and waiting in boot loop so I restore to ics gummy. I hope someone can help us with this...
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
I suppose you could try reinstalling the bootloader, or using one of the recent JB bootloaders and see if that helps. I can't think of a good reason why this should be happening based on what you've described, however. I assume you've checked obvious stuff like the MD5 sums on all your downloaded ROMs, etc?
Hi everybody!
I have identical issue, I did all possible, now I´m close to give it up. Yes, I checked all downloaded files by MD5 sums, I tried latest CWM, latest TWRP, gnex-JB-bootloader (…lc03). Today I tried also “Super_Wipe_Lite_Nexus”, but I can´t jump boot animation. I´m flashing roms long time, but this magic never happened. What else we should try to clear/delete?
Sorry for the noob question. I searched but i couldn't find the answer I'm looking for. Here's the deal...i have had alot of rooted phones but i just rooted my own phone for the first time,obviously the GNex. I used the toolkit i found on here and it went great. I am using TWRP recovery cause it was recommended by AOKP and when i flashed there new Jb ROM i noticed how twrp is set up a lot different then CWM. I found out that i had to factory wipe before flashing. So getting to my question. When i flash the update do i do that same wipe or do i wipe cache,davlik and/or system? Also i gotta do a back up first right? Then with gapps is it the same steps as flashing the update? If someone can show me the way that would be great. Thanks.
Sent from my Galaxy Nexus using xda app-developers app
1. Backup current ROM
2. Wipe
3. Flash new ROM
4. Flash GAPPs (if required)
5. Reboot
Well, for updating purpose you've only to wipe cache and dalvik (but i think it's not mandatory for all the rom) then you straight flash the rom and gapps (everytime both) then you reboot and you're good to go! And backup is always welcome!
[email protected] said:
Well, for updating purpose you've only to wipe cache and dalvik (but i think it's not mandatory for all the rom) then you straight flash the rom and gapps (everytime both) then you reboot and you're good to go! And backup is always welcome!
Click to expand...
Click to collapse
Thank you. I wasn't sure exactly what to wipe........my ass i know, but still learning this stuff.
Sent from my Galaxy Nexus using xda app-developers app
EddyOS said:
1. Backup current ROM
2. Wipe
3. Flash new ROM
4. Flash GAPPs (if required)
5. Reboot
Click to expand...
Click to collapse
If you're staying on the same rom with just an update you probably don't have to wipe unless you have issues upon reboot but otherwise you probably always should.
so i got an update notification from goo saying my rom and gapps have an update (aokp jb 4.2 mr1 build 2) so i flashed em and i got my stock reboot screen then every google app foreclosing over and over but rom still there. what the hell????
This is for sprint ain't it?!!?
Sent from my Galaxy Nexus using xda app-developers app
elliot2112 said:
This is for sprint ain't it?!!?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Toro would be Verizon.
sent from my Google Galaxy Nexus
bk201doesntexist said:
Toro would be Verizon.
sent from my Google Galaxy Nexus
Click to expand...
Click to collapse
well what happened here then? i looked on aokp and its not there. its the one i have now build 1. im really confused. the new gapps update is 20120429. it must be wrong if everything google was foreclosing. so what did goo.im give me?
ok it is build 2 on aokp. so gapps must be the same one i have been using? because this new one everything was foreclosing.
Better off doing updates manually and not using an app to do it for you
elliot2112 said:
well what happened here then? i looked on aokp and its not there. its the one i have now build 1. im really confused. the new gapps update is 20120429. it must be wrong if everything google was foreclosing. so what did goo.im give me?
Click to expand...
Click to collapse
From the date I think you flashed a gapps for jb 4.1 on a 4.2 ROM. Pretty sure that the 4.2 gapps is dated 12/12/12.
EddyOS said:
Better off doing updates manually and not using an app to do it for you
Click to expand...
Click to collapse
ya thats what im about to do now.
i went and downloaded build 2 straight from aokp and flashed that with same gapps for build 1 cause that hasnt changed on there site. my boot animation is the stock nexus logo instead of that pink unicorn with the gears. i figured it still wasnt working but everything seems to be running normal.....actually really fricken smooth and snappier. thanks for all your input everybody!
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.
Hey guys between this two builds i want to know what's the difference?? Cause i really don't see it. Maybe some tweaks or settings?
Can you guys explain to me which one is better and why?
daworship said:
Hey guys between this two builds i want to know what's the difference?? Cause i really don't see it. Maybe some tweaks or settings?
Can you guys explain to me which one is better and why?
Click to expand...
Click to collapse
Whichever one works better for you. There are different customizations for each ROM, but it's up to you to decide which one works better for your needs.
Sent from my Samsung SGH-T989D using xda premium
I keep getting stuck in a boot loop with all the updates of 10.1 Nightly, the only one I didn't get looped in was the original. I even did a full wipe and everything, help anyone?
kvarug01 said:
I keep getting stuck in a boot loop with all the updates of 10.1 Nightly, the only one I didn't get looped in was the original. I even did a full wipe and everything, help anyone?
Click to expand...
Click to collapse
I never have that issue even with dirty flash. Have you tried to wipe system, data, everything? I think you can try to Odin back to stock, then root it and start everything fresh. Sometimes the old files are still left over and mess up your phone.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Alarmmy said:
I never have that issue even with dirty flash. Have you tried to wipe system, data, everything? I think you can try to Odin back to stock, then root it and start everything fresh. Sometimes the old files are still left over and mess up your phone.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
The sad thing is, that's all I've been doing. Using Odin and keep going back to stock, update to ICS with Kies, and then hope to try and run another version of the ROM, and still no luck. It's quite frustrating. And yeah, I wiped system, data, everything. Did a full on wipe.
Also, has anyone have been getting call issues? Like you sound muzzled to your callers?
kvarug01 said:
Also, has anyone have been getting call issues? Like you sound muzzled to your callers?
Click to expand...
Click to collapse
Here is solution for your issue:
1. Upgrade recovery, or switch to TWRP.
2. Clean flash rom again.
3. Flash the newest radio UVLI4, or LI1.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Download darkside super wipe.zip ...flash it and then flash your rom+gapps... Hit thanks
Sent from my SGH-I897 using xda premium
sam.balia1012 said:
Download darkside super wipe.zip ...flash it and then flash your rom+gapps... Hit thanks
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
DO NOT do that if you are on the latest TWRP or CWM 6.+ cause Darkside super wipe was discontinued. For AOKP and CM 10.1 Nightly I just did a data/partition wipe and flash gapps.