No matter what ROM I'm on, or the compatible custom kernel I try to flash with whatever ROM I'm using at that time, I am still yet to have a successful flash of a kernel without rebooting the device only to have to pull my battery because it boots the first screen and then goes black and flashes the red LED, forcing me to restore to a backup I made prior.
I am running the most updated version of Liquidsmooth, and the most updated versions of CWM/TWRP. Any suggestions or possible causes? I always wipe cache/dalvik and fix permissions like I previously read was required in other threads.Thanks in advance!
StayingSober said:
No matter what ROM I'm on, or the compatible custom kernel I try to flash with whatever ROM I'm using at that time, I am still yet to have a successful flash of a kernel without rebooting the device only to have to pull my battery because it boots the first screen and then goes black and flashes the red LED, forcing me to restore to a backup I made prior.
I am running the most updated version of Liquidsmooth, and the most updated versions of CWM/TWRP. Any suggestions or possible causes? I always wipe cache/dalvik and fix permissions like I previously read was required in other threads.Thanks in advance!
Click to expand...
Click to collapse
What kernels did you flashed? And with what ROM?
If you are on liquid 2.2 I believe it need a aosp 3.4 kernel. I know the latest BMS kernel works. But the latest KT747 will not work unless you are using a new nightly of liquid 2.3. Be sure to wipe cache and dalvik cache after flashing but before rebooting.
Sent from my SCH-I535 using xda app-developers app
jmxc23 said:
What kernels did you flashed? And with what ROM?
Click to expand...
Click to collapse
Basically tried flashing any compatible kernel with the ROM I was running at the time. For example yesterday I tried flashing the KT747 kernel for Jellybean with the current ROM I'm running, which is the most recent Liquidsmooth 4.2.2 ROM. Still no success
Here is the latest liquid...
Nightly Builds 04/29/13 for d2att, d2spr, d2tmo, and d2vzw available on GooInsideMe
http://goo.im/devs/liquidsmooth/nightly/042913 These Builds Are Very STABLE!
View changes & bug fixes made to our source code here http://github.com/LiquidSmooth
This is quoted from liquid0624 in the liquid smooth thread.
Sent from my SCH-I535 using xda app-developers app
redKrome said:
If you are on liquid 2.2 I believe it need a aosp 3.4 kernel. I know the latest BMS kernel works. But the latest KT747 will not work unless you are using a new nightly of liquid 2.3. Be sure to wipe cache and dalvik cache after flashing but before rebooting.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Sorry for taking forever to reply, I originally posted this on my lunch break and am finally out of work to reply freely. Anyways, I tried what you said, and downloaded the BMS 3.4 kernel that states is compatible with the version of Liquidsmooth 4.2.2 I am running. Let's just say I yet again had to restore twice once because it did exactly what I stated above, where it gives me the splash screen saying it's running the custom kernel and doesn't boot any further after the Galaxy S3 screen. The first time, I flashed it and then wiped cache/dalvik and fixed permissions before booting up like everyone says you need to do after flashing a kernel, no success.
Then, I read in the kernel's thread that there is no need to do that for this most up to date release, it says you just have to flash the kernel and reboot like with any other zip file. Well that didn't work either, and was forced to restore a backup a second time! What could the problem be?! I'm using the most updated version of TWRP, I'm on the most updated nightly of the Liquidsmooth ROM, I'm using a highly confirmed working and compatible kernel, and following the directions to the T! When it comes to flashing a different ROM, modem, rpm, backup, etc. I have no problem whatsoever. But trying to flash a kernel has never been successful for me so far
Any help from anyone else? It's frustrating that I've never been able to flash any kernels to any ROM I've ever run
Sent from my Samsung SCH-I535 running Liquidsmooth 4.2.2
Im no expert on any of this but this is what i would do. Odin back to stock ROM and reroot and unlock bootloader. Id do this cause i would want a clean slate so i know there is no previous kernel/rom files that may be effecting something. Make a new nandroid backup then reflash the rom ya want to use. Once booted up and everything is running, restart the phone and boot into recovery. Wipe the dalvik and cache like normal then flash the kernel. Hopefully that would take care of the problem.
Only other thing i can think of is to maybe wipe data/factory reset like 2 or 3 times and wipe the caches again and reinstall your current rom. Then flash the kernel. Other than that im out of ideas. Hopefully someone can get your problem solved!
Sent from my SCH-I535 using xda premium
Related
Im running Oxygen 2.3.2 with whatever kernel came with that. I've been trying to flash Glados v2.2, it flashes properly in CWM but then, while rebooting, my phone gets stuck in the google boot screen, does anyone know how I can get it to boot properly?
FirePoncho86 said:
Im running Oxygen 2.3.2 with whatever kernel came with that. I've been trying to flash Glados v2.2, it flashes properly in CWM but then, while rebooting, my phone gets stuck in the google boot screen, does anyone know how I can get it to boot properly?
Click to expand...
Click to collapse
Flash another kernel instead. AFAIK, Oxygen 2.3.2 is Gingerbread-based ROM and GLaDOS v2.x is an Ice Cream Sandwich-based kernel. It will never boots.
I just tried Netarchy 1.40...same results
Sent from my Nexus S using XDA App
FirePoncho86 said:
I just tried Netarchy 1.40...same results
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Is that a kernel for GB? If so try to wipe cache and dalvik cache before flashing.
First check the post where you're downloading the kernel from and make sure it works with your phone model/version. Oxygen is a GB rom so use a kernel for GB.
To flash just put the kernel file on your root directory of your SD and boot into clockwork. After that wipe cache, go into advanced and wipe dalvik, and then flash the kernel. There shouldn't be any problems after that.
OH and don't forget that the first boot always takes long so have some patience!
I just flashed the 8/15 version of PA and was wondering if i have to completely wipe everything just to update to 8/18?
It is always recommended to do so to avoid any problems. But you can flash without the wipes and if you run into many issues, wipe and reflash
Sent from my sweet & buttery Infuse
I just flashed the pa jb update without wiping anything and it caused a world of problems for me I had to wipe and and start fresh to have a smoothly running phone again !!! Hope that helps
Sent from my SGH-I997 using xda premium
Flashing Paranoid
stevenk007 said:
I just flashed the 8/15 version of PA and was wondering if i have to completely wipe everything just to update to 8/18?
Click to expand...
Click to collapse
You should not have to wipe data, just wipe cache and dalvik cache. However it is a better chance of no force closes or other problems if you do wipe everything between upgrades.
following the question above about upgrading, do I also need to reflash the kernel too?
Yes you would have to flash the OC kernel again.
Sent from my sweet & buttery Infuse
digitalsunshine said:
following the question above about upgrading, do I also need to reflash the kernel too?
Click to expand...
Click to collapse
Or, you can just replace the boot.img from the PA zip with the one from OC kenel zip file (i.e. extract all the files on your PC, replace the file, re-zip, and flash as per-norm).
So I've tried Paranoid, Phantom builds, and Slim Bean and each one I can't install custom kernels. I've tried full wipes on all, checked the md5, and redownloaded. And by wiping I mean I formatted system. Each time I do it I get crazy bootloops and I'm seriously stumped. Any help?
You're supposed to wipe dalvik cache and cache before flashing a kernel. Wiping the system isn't ever suggested for kernels.
Sent from my SCH-I535 using xda app-developers app
sumredhed567 said:
So I've tried Paranoid, Phantom builds, and Slim Bean and each one I can't install custom kernels. I've tried full wipes on all, checked the md5, and redownloaded. And by wiping I mean I formatted system. Each time I do it I get crazy bootloops and I'm seriously stumped. Any help?
Click to expand...
Click to collapse
You are probably dealing with an issue of merged vs unmerged code. A ROM might be updated and the kernel might not be or vice versa. Non aosp devices with custom kernels have constant code changes.
Sent from my Galaxy Nexus using Tapatalk 2
Also make sure the kernels ur flashing are aosp kernels (not touchwiz kernels)
Sent from a SYNERGIZED GalaxySIII
When going from one ROM to another (ie. AOKP to CM10), is it only necessary to do a "clean" wipe, or are other steps recommended, such as reverting to stock first? I used to have a Droid 2 and people used to recommend that, but I don't know if it's necessary with this phone.
Also, what exactly does a "clean" wipe entail? I've seen multiple explanations. This guide suggests that you need only wipe data/factory reset and format system. Other people mention things like wiping cache and dalvik cache from recovery. Is there any sort of consensus on this?
Lastly, is it necessary to do these "clean" wipes when flashing a new nightly or new build, or does this simply vary depending on the ROM in question?
Thanks.
If you change ROMs most people recommend doing a data wipe.
Clean wipe is wiping data. If you wipe data, /cache is wiped too, so any subsequent cache wiping is unnecessary.
It is not necessary to wipe data when flashing a nightly or updated build.
When going from one Rom to another or one base to another (4.1 to 4.1.2) a full wipe is recommended that's system, data, cache. Nightly builds are usually safe to flash on top of each other unless otherwise noted. Biggest advice I can give is if you don't do a full wipe and encounter bugs you should go back and do a full wipe to ensure its the dirty wipe that caused it.
Neverendingxsin said:
When going from one Rom to another or one base to another (4.1 to 4.1.2) a full wipe is recommended that's system, data, cache. Nightly builds are usually safe to flash on top of each other unless otherwise noted. Biggest advice I can give is if you don't do a full wipe and encounter bugs you should go back and do a full wipe to ensure its the dirty wipe that caused it.
Click to expand...
Click to collapse
+1 its just not worth it.. Full wipe
Also when changing roms if the rom you are running has a custom kernel and the new rom uses a stock kernel but doesnt flash it then you will wanna make sure you flash a working kernel too
Sent from my SCH-I535 using xda app-developers app
x714x said:
Also when changing roms if the rom you are running has a custom kernel and the new rom uses a stock kernel but doesnt flash it then you will wanna make sure you flash a working kernel too
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Ha, I have made this mistake before.
x714x said:
Also when changing roms if the rom you are running has a custom kernel and the new rom uses a stock kernel but doesnt flash it then you will wanna make sure you flash a working kernel too
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
How can I verify this? It looks like AOKP has a custom kernel; what are the extra steps I need to take if I want to go to CM10 or back to stock?
Quacker said:
How can I verify this? It looks like AOKP has a custom kernel; what are the extra steps I need to take if I want to go to CM10 or back to stock?
Click to expand...
Click to collapse
If you're on AOSP (which includes CM10 and AOKP) then you'll need to reflash an ICS Touchwiz Kernel to go back to stock. You can go from CM10 to AOKP on the same kernel, depending on the merges. Sometimes new merges make it so an older kernel won't boot, etc.
Okay so i ran synergy rom for a bit, loved it and worked good.
I tried flashing CS SG3 ROM
I couldn't get it to boot all the way up, i tried everything odin back to stock and retried, wiping system , everything.
still couldn't get it to boot all the way up so i gave up and ended up going to GALAXY MOD It worked perfectly and i loved it.
But today I tried flashing release 15, it also will not boot up. But when going and flashing release 14.1 again it works perfectly.. does anyone know what my issue is or how to fix it? I'm so confused... do they have something similar that could possibly be the issue?
Galaxy mof has problems booting on its newest release if you want to flash rls15 be sure to use cwm touch recovery and pick developer's choice not custom
If you do choose custom be sure to put force gpu rendering.
Sent from my SCH-I535 using xda app-developers app
GoonAssJuan said:
Galaxy mof has problems booting on its newest release if you want to flash rls15 be sure to use cwm touch recovery and pick developer's choice not custom
If you do choose custom be sure to put force gpu rendering.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Oh okay. I will be trying this. thank you.
The only thing I can think of is not wipeing?
You can always try a dirtyy flash between ROMs. But if it doesn't fully boot.
Try wiping cache and dalvik cache.
You can also fix permission just to be safe.
Also. Maybe make sure you are on latest CWM? or TWRP.
sent from that young galaxy on clean ROM!
barrackOBAMA said:
The only thing I can think of is not wipeing?
You can always try a dirtyy flash between ROMs. But if it doesn't fully boot.
Try wiping cache and dalvik cache.
You can also fix permission just to be safe.
Also. Maybe make sure you are on latest CWM? or TWRP.
sent from that young galaxy on clean ROM!
Click to expand...
Click to collapse
I've tried this. lol