AOKP Jellybean

JSM9872

Super Moderator
Staff member
Premium Member
Joined
Dec 21, 2010
Messages
12,820
Reaction score
279
Location
Pennsylvania...
Current Phone Model
Galaxy S22+
Try it without the kernel.

Do the wipes (system, data, cache, dalvik), flash ROM, flash Gapps. Reboot into ROM. See if she boots up that way.

*Edit* You don't need to flash the JB Bootloader every time either. Once is sufficient, it won't go away until you change it.

Good call. Missed the part about the kernel.

"Don't Panic!"
Tapatalk 2_NEXUS 7
 

dezymond

Tech Support Mod
Staff member
Premium Member
Joined
Nov 11, 2009
Messages
12,049
Reaction score
1,479
Location
Bay Area, California
Current Phone Model
Google Pixel
Did you check the md5 sums after you downloaded them?

Nexus using Droid Forums
 
Joined
Dec 20, 2011
Messages
833
Reaction score
10
Try it without the kernel.

Do the wipes (system, data, cache, dalvik), flash ROM, flash Gapps. Reboot into ROM. See if she boots up that way.

*Edit* You don't need to flash the JB Bootloader every time either. Once is sufficient, it won't go away until you change it.

ok, just did it without flashing a kernel, still on the google screen. i'll give it a few minutes....:icon_eek: lol
 

sbenson

Silver Member
Joined
Jan 19, 2011
Messages
2,369
Reaction score
61
Location
Virginia/DC Metro Area
hmmmm? what's that lol

View attachment 53510

You are slowly killing me. Md5 is for verifying your downloads. What you are most likely encountering is a corrupt download.

If you download roms directly to your phone, try this: MD5 Checker.

If you download your roms to your computer, then transfer them to your phone, try this: MD5 Checker.

You can usually find the md5 hash code in the OP of the rom you are downloading. The developer will ALWAYS provide one. Copy this code into the MD5 Checker, then load up your rom and let it verify. If it matches, your good to go, flash away. If it doesn't match, you have a corrupt download, re-download.
 
Top