Develop Bugs

Boot loop in jb roms

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?

[Q] Question!!! "codename 3.6.6 rom" and "leankernel 1.7"

Hello
I am using codename 3.6.6 rom now
I was trying to flash leankernel 1.7 which was released today
However, after I flash it, my phone didn't turn on
I did wipe cache, dalvic cashe, and fix permision after I flashed
please help me! I want to install a new kernel
Or please recomend me some good kernels
Thank you

Need a kernel that's compatible with the older version of the ROMs. There are new fixes in the cm code that will screw things up if you flash a newer kernel. You need to go in and wipe system and try to reflash cna ROM and home for the best. Otherwise you need to wipe everything (data,system,cache) and start over.
Read a little more in the kernel section before applying. If did make a back up then you're in luck.
Sent from my SGH-T999 using xda premium

mt3g said:
Need a kernel that's compatible with the older version of the ROMs. There are new fixes in the cm code that will screw things up if you flash a newer kernel. You need to go in and wipe system and try to reflash cna ROM and home for the best. Otherwise you need to wipe everything (data,system,cache) and start over.
Read a little more in the kernel section before applying. If did make a back up then you're in luck.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
yes I made back up
maybe codename is not the aosp based..
I cant flash any kernels
Thank you for your help

If you bothered to read it states that 1.5+ boots most recent version of CM10.

[Q]Kernel compatibility for [ROM] [AOSP] » LIQUIDSMOOTH » JellyBean [4.1.2] RC 9 [HER

I am having a hard time finding a compatible Kernel for [ROM] [AOSP] » LIQUIDSMOOTH » JellyBean [4.1.2] RC 9 [HERCULES]
-GS2 T-Mobile T989
I tried flashing [KERNEL]OC/UV up to 1.83GHz h0tcakez JB | 3.0.49 For Hercules
Firstly, I am getting confused which one to use, but I tried each one anyway.
--They all result in BootLoop--
I have seen people have it as a kernel, but I can't seem to figure it out.
If anyone can help me, Thank you in advance
T-mobile Galaxy S2 T989
LIQUIDSMOOTH RC9 JELLYBEAN 4.1.2
CWM 5.0.2.7
- I have tried 6.0.1.9 CWM, seemed buggy for me.
- Also used TWRP, it works great but same results with the bootloop after flashing [h0tcakez Kernel]

Flash kko-t989 or hotcakes aosp kernel. Wipe dalvik , wipe cache then reboot. Try sk8erwitskils cwm recovery its in the thread for development
Sent from my SGH-T989 using Tapatalk

richardlibeau said:
Flash kko-t989 or hotcakes aosp kernel. Wipe dalvik , wipe cache then reboot. Try sk8erwitskils cwm recovery its in the thread for development
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I can't find the sk8terwitskills cwm recovery. But I have tried to flash and wipe dalv/cache still getting the bootloop.

Its aosp so either should work.
Can you get to your recovery?
I have always had to use the darksidecachewipe zip after flashing with cwm recovery.
Twrp does NOT require the use of cache wipe scripts.
Try getting the darksidecahewipe onto your device, and run it from recovery after you flash.
I soft bricked a phone the other day with the hotcakes kernel because I didn't make sure I was running a post-oct14 build of cm10. So make sure you meet all criteria for installation.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

ctrlaltdeln said:
Its aosp so either should work.
Can you get to your recovery?
I have always had to use the darksidecachewipe zip after flashing with cwm recovery.
Twrp does NOT require the use of cache wipe scripts.
Try getting the darksidecahewipe onto your device, and run it from recovery after you flash.
I soft bricked a phone the other day with the hotcakes kernel because I didn't make sure I was running a post-oct14 build of cm10. So make sure you meet all criteria for installation.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Tried everything, not working, What build are you using? Maybe Ill try it. Please

Update your recovery to latest TWRP or CWM. If your flashing properly and still having issues then that's all it could be.
Sent from my SAMSUNG-SGH-T989 using xda premium

I've used these kernels on various JB ROMs
KKO
http://db.tt/uEx0aED4
Hotcakez
http://db.tt/pB0nkMik

Base Firmware
Would it matter if I started at a 4.0.3 Firmware or a 4.0.4 firmware Stock? I have been flashing from 4.0.3 Stock firmware

I'm running the stable release of cm10. I've tried lots of ROMs and I find I always go back to cm10.
The liquid ROM is cm10 based so anything that will work with cm10 should work with liquid ROM.
Try flashing cm10 stable from scratch. Full wipes. Follow instructions on cyanogenmod install instructions page.
Backup.!!! If still on cwm,...........use darksidesuperwipe to factory reset device. I like to flash radio then cm10 then DScachewipe and reboot. Wait at least 10mins after first boot.
Then I like to reboot, and flash gapps then kernel, then DScachewipe.
In my opinion, definitely get onto twrp. No need to DScachewipe before reboot. Also nicer UI.
After cm10 is running good, flash till your hearts content.
Although I think you will find cm10 to be an excellent daily driver.
Good luck.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

PACman ROM

Hey guys, recently i tried to switch from cm10(stable) to PACman ROM. Unfortunately, it never works. I always get "flash aborted". When I flashed cm10, I flashed the at&t version and it works fine, and the PACman I'm trying to flash is the tmo one. Should i try the at&t PACman instead? Please help me guys
Oh BTW, I'm on wind if that helps
Thanks to all that help or attempt to!
Sent from my GT-N8010 using xda app-developers app

why don't you wipe? or maybe its your recovery?

mt3g said:
why don't you wipe? or maybe its your recovery?
Click to expand...
Click to collapse
I did the wipedata, cache and dalvik, i wiped everything needed, i followed all standard directions for flashing new ROMs, but nothing works. And oh, im using CWM recovery and on rom manager it says im at the latest version, so everything is up to date and everything should work but it doesnt:crying:

I had same issue too. It never worked for me if I switch from CM to PACMAN ROM. But I had it working if I flash stock ROM first then flash PACman. Any stock based ROM should work. Its a pain but you should try it. Also I used TWRP and I always wipe system too not just cache, delvik, and data. Just make sure you have nandroid. Good luck.
Edit: also I never flash PACman ROM and gapps together. Flash ROM let it boot once and go back to recovery to flash gapps..
Sent from my SGH-T999 using xda premium

myowin said:
I had same issue too. It never worked for me if I switch from CM to PACMAN ROM. But I had it working if I flash stock ROM first then flash PACman. Any stock based ROM should work. Its a pain but you should try it. Also I used TWRP and I always wipe system too not just cache, delvik, and data. Just make sure you have nandroid. Good luck.
Edit: also I never flash PACman ROM and gapps together. Flash ROM let it boot once and go back to recovery to flash gapps..
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Hey, thanks for the advice, ill try flashing back to my stock then flash PACman, hopefully that works
And also, could you teach me how to flash TWRP? Ive been meaning to replace CWM with TWRP but im kinda iffy on how to do it. Do i put the .zip on my sd and flash it through CWM and then bam, ill have TWRP?

Jaz-Crahh said:
Hey, thanks for the advice, ill try flashing back to my stock then flash PACman, hopefully that works
And also, could you teach me how to flash TWRP? Ive been meaning to replace CWM with TWRP but im kinda iffy on how to do it. Do i put the .zip on my sd and flash it through CWM and then bam, ill have TWRP?
Click to expand...
Click to collapse
Install it with goo manager.
Sent from my SGH-T999 using Tapatalk 2

Error 7

Hi guys how come evertime I try to install a custom rom its gives me the Error 7 (Status 7 Error). Have anyone encountered this before? How do I fix it? I tried updating my CWM but still, nothing works, I tried to install Cyanogenmod 10.1 and DarthStalker but it gives me that error. Help please, Thanks in advance :thumbup:

What version of CWM are you using? Number, please.
Do you currently have a ROM on the phone? If you go into About phone from the system settings, what phone model does it say you have?

Its says I have SGH-T999
Sent from my SGH-T999 using xda app-developers app

Are you updating CWM with ROM Manager?
Factory reset, wipe cache, and you should be able to install any ROM without any issues.
Sent from my SGH-T999 using xda app-developers app

Yes I updated my CWM using Rom Manager
Sent from my SGH-T999 using xda app-developers app

I've had this happen many many times. Check the MD5. Its more than likely a bad download. Try re downloading it again.
Try transferring the download from PC to your phone. And try to flash again.
Sent from my SGH-T999 running Chihuahua v1 ROM

re: error 7 issues
CooLoL1999 said:
Hi guys how come evertime I try to install a custom rom its gives me the Error 7 (Status 7 Error). Have anyone encountered this before? How do I fix it? I tried updating my CWM but still, nothing works, I tried to install Cyanogenmod 10.1 and DarthStalker but it gives me that error. Help please, Thanks in advance :thumbup:
Click to expand...
Click to collapse
Most likely you tried to flash some rom which was not 100% compatible with your phone.
If you can get into CWM or TWRP recovery just do a factory reset/wipe cache/wipe dalvik cache.
Do NOT wipe or format SYSTEM . This should allow your phone to boot completly.
Be sure NOT to try flashing the same rom which gave you the error 7.
If you are still having problems then continue reading...
If you have a cwm/twrp backup (nandroid) of your previous rom go back into cwm or twrp
and restore your nandroid backup.
If you don't have a nandroid backup but you do have a proper zip file custom rom saved to your sdcard
then you can flash the rom making sure you first do a factory reset/wipe cache/dalvik and system.
After that you can start over again but be sure to make a nandroid backup first.
If you still have problems after doing the above you will need to ODIN flash the stock-rooted
Samsung Galaxy S3 T999 Jellybean v4.1.1 firmware.
P.S. You would NEVER get an ERROR 7 if you would only flash stock based "Samsung Galaxy S3 T999 Jellybean v4.1.1 custom roms"
instead of those CM/AOKP/AOSP or Ported roms.
Good Luck!

CooLoL1999 said:
Hi guys how come evertime I try to install a custom rom its gives me the Error 7 (Status 7 Error). Have anyone encountered this before? How do I fix it? I tried updating my CWM but still, nothing works, I tried to install Cyanogenmod 10.1 and DarthStalker but it gives me that error. Help please, Thanks in advance :thumbup:
Click to expand...
Click to collapse
First of all, make sure that you redownload the ROM, check that the MD5's match, and that you are indeed on the latest CWM recovery.
Secondly, I've heard of these status 7 errors, even when on the latest CWM recovery. There's times when installing certain ROMs where these errors occur, which usually happens when the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing and this portion of the script are called “asserts”. with this it prevents you from accidentally flashing a ROM intended for a different model.
Normally you can fix the issue by installing TWRP recovery but there's another possible solution for this if the TWRP method doesn't solve it but take some serious precaution. You need to be very careful and do this at your own risk.
Follow this step by step guide
http://highonandroid.com/android-roms/how-to-fix-status-7-error-with-cwm-recovery-on-rooted-android/
Following this will remove the asserts thus removing protection upon flashing the wrong ROM. Do if you choose to follow this make absolutely sure that the ROM you're flashing is for the T999.
Sent from my SGH-T999 using xda premium
---------- Post added at 01:57 AM ---------- Previous post was at 01:40 AM ----------
Status 7 errors can very well still occur through CWM recovery on stock based ROMs.. It mostly all depends on the ROMs updater script and if the dev accidentally made an error within that, which is why the asserts would normally correct that error by forcing the ROM to be flashed regardless.
Sent from my SGH-T999 using xda premium

Everyone, Thanks for helping me out, I flash back to stock firmware, I found out that I rooted my phone the wrong way (Qbking's Video). I tried rerooting but I used a different method and updated CWM, now works completely fine, Thanks for all your help!! :thumbup::thumbup:
Sent from my SGH-T999 using xda app-developers app