Database Info

I seriously can't figure it out.

I've been tinkering with androids for well over a year now and have rooted unlocked and s-off'ed amongst other things many different devices. For some reason I'm having trouble flashing kernels to my s3. Yes I'm unlocked and yes I'm flashing aosp kernels to aosp roms and touchwiz kernels to touchwiz roms. The problem seems most persistent on aosp roms and yes I've also checked that they both had the same cm10 commits. The only kernel I could get to boot was clean kernel on beans custom. Other than that no other kernels will work. The device will boot then the screen will start glitching up and then eventually bootloop. I've also made sure to wipe dalvik and cache plus fix permissions. I've also tried just flashing the kernel after doing a full wipe and starting with a new rom and have root 66ed back to stock and re unlocked. Is there something I'm missing here? I'm getting frustrated as I love custom kernels. Oh and the latest combo I tried was liquid smooth rc3 and lean kernel 1.0. Thanks guys.
Sent from my SCH-I535 using xda app-developers app

did you try wiping cach, davik cach, and fix permissions AFTER flashing then reboot?
Ofc wipe cach and dalvik cache before also.

My usual process goes something like this
*Wipe Cache
*Wipe Dalvik
*Flash Kernel
*Wipe Cache & Dalvik again
*Fix Permissions
Works like a charm every time.
Samsung Galaxy S3

i have had the same trouble once...fixed it by flashing back to a stock kernel first.
try this:
wipe cache & dalvik
flash stock kernel.zip- http://db.tt/ceeDTAfz
flash custom kernel
reboot

Is that the stock cm10 kernel or touchwiz? Also yes I've tried wiping before and after and fixing permissions. So weird and its driving me nuts. I miss having awesome battery life
Sent from my SCH-I535 using xda developers app

sumredhed567 said:
Is that the stock cm10 kernel or touchwiz? Also yes I've tried wiping before and after and fixing permissions. So weird and its driving me nuts. I miss having awesome battery life
Sent from my SCH-I535 using xda developers app
Click to expand...
Click to collapse
stock kernel = stock TW kernel
Sent from my SCH-I535 using xda app-developers app

Tried flashing the stock kernel still same thing. It's so weird. It will begin to boot and then boot animation will start flickering or flashing then glitch up. With every kernel it's the same result.
Sent from my SCH-I535 using xda app-developers app

sumredhed567 said:
Tried flashing the stock kernel still same thing. It's so weird. It will begin to boot and then boot animation will start flickering or flashing then glitch up. With every kernel it's the same result.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
another thing you might try is formatting system in cwm.

droidstyle said:
another thing you might try is formatting system in cwm.
Click to expand...
Click to collapse
I've tried that a few times when doing a fresh rom install. I mean root66ing through odin should completely wipe everything. I just don't see what I'm missing. I've even tried using a different recovery and still the same. Could it just be something specific to my phone? I'm so freaking stumped!!

sumredhed567 said:
I've tried that a few times when doing a fresh rom install. I mean root66ing through odin should completely wipe everything. I just don't see what I'm missing. I've even tried using a different recovery and still the same. Could it just be something specific to my phone? I'm so freaking stumped!!
Click to expand...
Click to collapse
now when you odin back to stock, your booting into stock recovery after flashing the rom(root66) and doing a data wipe/factory reset correct? you said full wipe, but just want to be clear. it may be corrupted internal memory and might need to be reformatted.

I actually don't think I was wiping after I used Odin. I'll try that as soon as I get home. Though I have done plenty of factory data resets and system wipes, just not right after I odined. And you mentioned formatting how would I go about doing that?
Sent from my SCH-I535 using xda app-developers app

sumredhed567 said:
I actually don't think I was wiping after I used Odin. I'll try that as soon as I get home. Though I have done plenty of factory data resets and system wipes, just not right after I odined. And you mentioned formatting how would I go about doing that?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
follow section 6 of my guide...link in sig!

Always perform a full/mega wipe as:
1) Wipe data/factory reset
2) Wipe cache partition
3) Wipe dalvik cache
4) In mounts/storage section wipe /system
5) wipe /data
6) wipe /cache
7) wipe /preload
Then flash new ROM.
For flashing a kernel, please perform steps 2 and 3.

General ROM installation questions

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.

[Q ] Switching from Embryo 6.9 to any other TW ROM

Hello guys,
So I wanted to switch from Embryo 6.9 to other TW ROMs to try them out but I am running into wierd issue.
When I try to do a clean install of Stock Kanged or the untouched TW Jellybean Odex ROM, they do get flashed without errors, but when the load up, apps for PLAYSTORE and PHONE are missing and I get costant FC for android.process and system ui. On top of that, I cant even access the settings.
This seems to be the case, regardless of which ever Rom that I flash. And if I flash EMBRYO ROM again, that works fine.
I am getting a feeling that EMBRYO Roms are changing the file system / structure (whatever it is that it does - im not that technical lol) and because of that only EMBRYO is able to be flashed and works but others get messed up.
Can anyone tell me if there its any way to correct things out or do I have to Odin my device to stock and start from scratch?
Thanks
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Are you flashing gapps after flashing the ROM?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

I was thinking the same thing but its not mentioned anywhere in the ops for those roms, to flash gapps.. (may be i have missed it but i cant find that anywhere)
Plus the phone app shouldnt be a part of gapps neither should the settings be force closing because of that... may be if someone has switched from embryo to those other stock roms, they can shed a better light at this.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

If you are clean wipe (/system /data /cache /preload) you should not be having any problems:
* Any serious ROM (full wipe) should do that for you, to account for user error.
* Or look into what recovery you are using.
Did you flash my untouched UCLL3 leak/UCLK4 leak? Try that, if that works you would need to bang the ROM developer..And yes, there are many who have switched to and from Embryo..

mohan_kr said:
If you are clean wipe (/system /data /cache /preload) you should not be having any problems:
* Any serious ROM (full wipe) should do that for you, to account for user error.
* Or look into what recovery you are using.
Did you flash my untouched UCLL3 leak/UCLK4 leak? Try that, if that works you would need to bang the ROM developer..And yes, there are many who have switched to and from Embryo..
Click to expand...
Click to collapse
Thanks mohan.
I have tried a clean wipe but i will doubt everything i have tried and start from scratch again with what u recommended and see what happens.
Btw i do love embryo but the RR sometimes are resulting in wakelocks for some reason and if i dont pay attention to it when im at work then the battery drain kinda kills it lol.. but it is an awesome still.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

mohan_kr said:
If you are clean wipe (/system /data /cache /preload) you should not be having any problems:
* Any serious ROM (full wipe) should do that for you, to account for user error.
* Or look into what recovery you are using.
Did you flash my untouched UCLL3 leak/UCLK4 leak? Try that, if that works you would need to bang the ROM developer..And yes, there are many who have switched to and from Embryo..
Click to expand...
Click to collapse
+1
Agree with the bold text.

[Q] Help flashing custom kernels, never had one successful flash...

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

[Q] About GAPPS

Hey there everyone,
I decided to make a new topic since my other thread had a way other issue. I want to have a custom rom of AOKP on my HTC one x. I've downloaded the file, installed CWM etc. Now my question is what Gapps do I need? Is it rom specific? I know that AOKP runs on android 4.2.2.
Do I need CyanogenMod 10.1.x 4.2.2 Gapps?

Pmage0wns said:
Hey there everyone,
I decided to make a new topic since my other thread had a way other issue. I want to have a custom rom of AOKP on my HTC one x. I've downloaded the file, installed CWM etc. Now my question is what Gapps do I need? Is it rom specific? I know that AOKP runs on android 4.2.2.
Do I need CyanogenMod 10.1.x 4.2.2 Gapps?
Click to expand...
Click to collapse
Most roms will have a link to the proper Gapps package within OP but yes, if it's a 4.2.2 rom, the cm 4.2.2 gapps should work fine.

Pmage0wns said:
Hey there everyone,
I decided to make a new topic since my other thread had a way other issue. I want to have a custom rom of AOKP on my HTC one x. I've downloaded the file, installed CWM etc. Now my question is what Gapps do I need? Is it rom specific? I know that AOKP runs on android 4.2.2.
Do I need CyanogenMod 10.1.x4.2.2 Gapps?
Click to expand...
Click to collapse
I believe you do if you flash the wrong version of GAPPS it can boot loop you.
Nexus 4 CyanogenMod 10.1.0RC2

exad said:
Most roms will have a link to the proper Gapps package within OP but yes, if it's a 4.2.2 rom, the cm 4.2.2 gapps should work fine.
Click to expand...
Click to collapse
Ah yes, http://forum.xda-developers.com/showthread.php?t=2052610 This first linked me to an enormous site with alot of Gapps which confused me. But once I scrolled down to check I could still find the Gapps that were reccomended for that build.
Excuse me for my impatience Carry on!

How do I perform a FULL wipe though?

Pmage0wns said:
How do I perform a FULL wipe though?
Click to expand...
Click to collapse
Reboot into recovery, do a factory reset, wipe /system/, and (optional) wipe the sdcard. Just remember that if you wipe the sdcard you will be wiping the zip files you were going to flash. So, you might want to do that part AFTER installing the Rom and gapps.
Sent from my HTC One X using xda app-developers app

A Full wipe consists of wiping: Cache, dalvik cache, system and factory reset in recovery.
TWRP 2.4+ seems to have issues wiping so if you get error messages or bootloops after doing a full wipe and flashing a new ROM, this could be why. TWRP version of choice is 2.3.3.1
Installing the wrong GAPPS will typically create Force closes when you boot up or try to launch and apps within GAPPS. I've never seen flashing the wrong gapps cause bootloops.

Shiizzzzzz, I flash every gapp package under the sun for every aosp Rom there is for the XL lol... My favorites are midnight gapps... Worked perfect on all roms.
Sent from my HTC One XL using Tapatalk 2

exad said:
A Full wipe consists of wiping: Cache, dalvik cache, system and factory reset in recovery.
Click to expand...
Click to collapse
I keep seeing advice like this on the boards, but doesn't the factory reset wipe both /data and /cache? I honestly want to know so I don't give people bad advice.
Regardless, good call on the twrp version.
Sent from my HTC One X using xda app-developers app

Duckman5 said:
I keep seeing advice like this on the boards, but doesn't the factory reset wipe both /data and /cache? I honestly want to know so I don't give people bad advice.
Regardless, good call on the twrp version.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes but redundancy never hurt anyone. Also, when you take into account the issues with both cwm and twrp across multiple devices, it's best to be overly cautious than not cautious enough. Sometimes I wipe it all twice just to ease my mind. If you read on Tweamwin's site, they also say that most ROM installs wipe the system partition so you should never have to wipe it, but I think we all know that's BS.
TWRP, CWM, ROMS, MODS, these are all developed by random people I don't know, who also have no part in the original manufacture/design of my device. Better to be safe than sorry, I always say.

Fair enough. I guess when you are dealing with stuff that could seriously mess up an expensive device a little caution can't hurt.
Sent from my HTC One X using xda app-developers app

exad said:
Yes but redundancy never hurt anyone. Also, when you take into account the issues with both cwm and twrp across multiple devices, it's best to be overly cautious than not cautious enough. Sometimes I wipe it all twice just to ease my mind. If you read on Tweamwin's site, they also say that most ROM installs wipe the system partition so you should never have to wipe it, but I think we all know that's BS.
TWRP, CWM, ROMS, MODS, these are all developed by random people I don't know, who also have no part in the original manufacture/design of my device. Better to be safe than sorry, I always say.
Click to expand...
Click to collapse
I agree 100%
I always do double wipes of everything before flashing something. And I wipe cache/dalvik after the flash too. I expect that's the reason I never have issues after booting my phone up.
Sent from my One XL using XDA Premium