Related
hi,
in this thread
http://forum.xda-developers.com/showthread.php?t=1401633
it references the kernel by imoseyon. i would like to download that kernel so i have it in case i want to come back to it later while i try a franco kernel. but when i go to imoseyon git files, there are so many files, i don't know where to find it.
if i hit the download button, the file it wants to download is like 120megs. seems like kernel zip files are usually like 4 or 5 megs so 120mb doesn't seem right.
anyone know how i can get the CWM install ready kernel?
thanks
Unzip the rom and take the boot.img out.
This is the kernel, you can flash it using fastboot.
thanks. these look to be the commands to do that
adb reboot bootloader
fastboot flash boot boot.img
http://rootzwiki.com/topic/13299-kernel-leankernel-minimalistic-kernel-171-12012/
Google is your friend.
Edit: If you go to his git, you download his source and all the associated repos. That's why it's 120mb. Download it from rootzwiki there. Those ones are CWM-flashable.
glhelinski said:
thanks. these look to be the commands to do that
adb reboot bootloader
fastboot flash boot boot.img
Click to expand...
Click to collapse
This may not be enough as often kernel requires some suplement files to be stored in /system. CWM flashable bundles of leankernel are the best way to go. Main development goes on rootzwiki, head there for this kernel. 0.6.6 uses leankernel 1.7.1 I believe
thanks to both of you. good info. google is definitely a friend...rootzwiki password resets are not
Coming from a T-bolt, I got in the habit of wiping data, cache, and dalvik cache every time I threw a new rom on.
If I'm going from 0.6.5 to 0.6.6 do I need to wipe ANYTHING? I've heard no, but it just feels weird flashing a rom straight over an existing rom.
Thanks in advance for your help!
Seedster said:
Coming from a T-bolt, I got in the habit of wiping data, cache, and dalvik cache every time I threw a new rom on.
If I'm going from 0.6.5 to 0.6.6 do I need to wipe ANYTHING? I've heard no, but it just feels weird flashing a rom straight over an existing rom.
Thanks in advance for your help!
Click to expand...
Click to collapse
Nope, don't wipe anything
Sent from my Galaxy Nexus using xda premium
I've never used an AOSP ROM before, but now I am currently on AOKP. When I want to update to a newer version, do I still need to flash gapps after flashing the update? I assume I have to reflash the kernel as well if I use one different than the one included with the ROM?
You need to flash GApps straight away after if you are wiping your device. You also need to reflash the kernel of choice after. Good luck.
jd1001 said:
You need to flash GApps straight away after if you are wiping your device. You also need to reflash the kernel of choice after. Good luck.
Click to expand...
Click to collapse
Only wiping I would do would be cache and dalvik since I am merely upgrading the ROM version, eg nightly 19 to nightly 20. Would that still involve flashing gapps?
edgeicator said:
Only wiping I would do would be cache and dalvik since I am merely upgrading the ROM version, eg nightly 19 to nightly 20. Would that still involve flashing gapps?
Click to expand...
Click to collapse
Yes
10char.
You shouldn't have to reflash GAPPS if you are just updating..
2 separate answers. Anyone else want to chime in?
You have to ref lash the kernel because flashing a rom flashes the from kernel. I've never had to flash gapps on any device if going from an old build of a rom to a new one unless specifically stated.
Sent from my Galaxy Nexus using xda premium
edgeicator said:
2 separate answers. Anyone else want to chime in?
Click to expand...
Click to collapse
Just think about it. It depends on how you flash and if you flash an update.zip if that zip wipes existing data or just adds to it.
For a sure answer you would need to say what method is used and how the update edify script in the zip looks like.
Now for someone how knows the rom you're talking about in detail and what files are provided there might be a clearer answer, but not every poster does know such details^^
The answer is no, if you just update a rom without wipe, you dont need to flash gapps. This type of rom update keeps all your data in tact anyway so of course no need to flash extra.
I am currently running Leedroid and I sometimes switch to Paranoid Android just to see how things are developing there. Great rom but I cant do without sense camera and like the decent weather app with all its animations.
Back to reason, sorry, I cant change my kernel on neither rom. Just gets stuck on boot animation/loop. Knew problem because I used to be able to change kernels but now just cant. Any idea's to why. Much appreciated - I feel handicapped...
Well, did you repack the kernels AND flash modules?
tomascus said:
Well, did you repack the kernels AND flash modules?
Click to expand...
Click to collapse
Cheers for quick response. :good:Yes, as I said I used to be able to try different kernels but just stopped last dozen attempts. Have tried repacking boot image several times, via online repacker but had no joy. Am i doing something wrong.
veroby said:
Cheers for quick response. :good:Yes, as I said I used to be able to try different kernels but just stopped last dozen attempts. Have tried repacking boot image several times, via online repacker but had no joy. Am i doing something wrong.
Click to expand...
Click to collapse
You put the original boot.img in the source img, correct?
Then repacked, flashed the kernel, erased cache and then rebooted to recovery to flash modules?
tomascus said:
You put the original boot.img in the source img, correct?
Then repacked, flashed the kernel, erased cache and then rebooted to recovery to flash modules?
Click to expand...
Click to collapse
Correct. I have tried erasing cache via command line and I have tried erasing cache via cwm as well. Still no joy
Actually because of desperation I have tried everything in different orders as well. Example- flashing boot image before after flashing kernel. Still doesnt boot and eventually after long wait just loops. This problem is with both roms.
Stock kernel works right?
tomascus said:
Stock kernel works right?
Click to expand...
Click to collapse
Yeap, have had to restore to backups everytime. And they function fine but even tho I am a believer in "if it aint broke don't fix it", I cant help but try and fix wat aint broke. If you know what i mean.....
veroby said:
Yeap, have had to restore to backups everytime. And they function fine but even tho I am a believer in "if it aint broke don't fix it", I cant help but try and fix wat aint broke. If you know what i mean.....
Click to expand...
Click to collapse
Maybe a dumb answer, but i had the same problem. Do you flash in the right order? Do you flash your kernel before or after your rom flash? And you're flashing using fastboot?
KaiseRRUby said:
Maybe a dumb answer, but i had the same problem. Do you flash in the right order? Do you flash your kernel before or after your rom flash? And you're flashing using fastboot?
Click to expand...
Click to collapse
No not dumb, i really appreciate attempt in help. As to right order, have tried right order, fastboot flash boot boot.img with repack and original image to kernel but nothing is working. Just will not allow change kernel. Have tried re-flashing boot image after flash kernel as well. Have tried erasing cache partition with wiping dalvik cache together but no go. Have tried erasing nothing but still boot loop. Any ideas:crying:
veroby said:
No not dumb, i really appreciate attempt in help. As to right order, have tried right order, fastboot flash boot boot.img with repack and original image to kernel but nothing is working. Just will not allow change kernel. Have tried re-flashing boot image after flash kernel as well. Have tried erasing cache partition with wiping dalvik cache together but no go. Have tried erasing nothing but still boot loop. Any ideas:crying:
Click to expand...
Click to collapse
So this is your order:
- Backup
- full wipe
- flash rom
- flash kernel
- flash modules
- restart
?
doesn't matter what order you flash the boot.img, as long as you flash the modules after you flash the ROM.
btw, try another ROM.
ARHD 11.1 jellybean smooth and sense camera full package
tomascus said:
doesn't matter what order you flash the boot.img, as long as you flash the modules after you flash the ROM.
btw, try another ROM.
Click to expand...
Click to collapse
Ok here's what I did, full wipe, Flashed knew copy of Leedroid ( i know you said try another rom but hadnt thought it to be necessary because I was having same problem with Leedroid and Paranoid Android jellybean), kinda custom the rom a little with mods and tweaks. Got a bit ahead of myself because I then fastboot faux kernel boot image and flashed the modules. Gutted BOOt-LooPED...:crying:
Have gone back to my backup Leedroid. At least I know its not the full wipe. Any more ideas welcome.
Forgot to mention I did not repack the boot image until after boot loop. Still did not work.
KaiseRRUby said:
So this is your order:
- Backup
- full wipe
- flash rom
- flash kernel
- flash modules
- restart
?
Click to expand...
Click to collapse
Ok here's what I did, full wipe, Flashed knew copy of Leedroid, kinda custom the rom a little with mods and tweaks. Got a bit ahead of myself because I then fastboot faux kernel boot image and flashed the modules. Gutted BOOt-LooPED...
Have gone back to my backup Leedroid. At least I know its not the full wipe. Any more ideas welcome.
Forgot to mention I did not repack the boot image until after boot loop. Still did not work.
veroby said:
Ok here's what I did, full wipe, Flashed knew copy of Leedroid, kinda custom the rom a little with mods and tweaks. Got a bit ahead of myself because I then fastboot faux kernel boot image and flashed the modules. Gutted BOOt-LooPED...
Have gone back to my backup Leedroid. At least I know its not the full wipe. Any more ideas welcome.
Forgot to mention I did not repack the boot image until after boot loop. Still did not work.
Click to expand...
Click to collapse
Well, the best way to do it as far as i know is:
-boot.img flash (the one included in rom)
-wipe
-flash rom
-reboot
-wait for 10 minutes
-rebooten (full reboot again)
-reboot to fastboot
-boot.img flashen (custom kernel)
-modules flashen (custom kernel)
That 's how things work by me, you can try this?
KaiseRRUby said:
Well, the best way to do it as far as i know is:
-boot.img flash (the one included in rom)
-wipe
-flash rom
-reboot
-wait for 10 minutes
-rebooten (full reboot again)
-reboot to fastboot
-boot.img flashen (custom kernel)
-modules flashen (custom kernel)
That 's how things work by me, you can try this?
Click to expand...
Click to collapse
Yeah understand, I used to be able to just fastboot flash kernel boot image, flash kernel modules via cwm and bobs ya uncle. Done. But no more. Guess I'll have to wait until i jump ship and update firmware to 1.28 for JB roms and re-format or something. Cheers anyways..
I have never flashed any kernels, just custom roms. From what I have read it goes down the same way, just flash the zip from SD in recovery and wipe cache. Correct?
Also, if I want to go back to stock kernel can I flash back to a JOP40C ( this one http://forum.xda-developers.com/showthread.php?t=1992483 ) even though my build is JOP40D ?
Robert00001 said:
I have never flashed any kernels, just custom roms. From what I have read it goes down the same way, just flash the zip from SD in recovery and wipe cache. Correct?
Also, if I want to go back to stock kernel can I flash back to a JOP40C ( this one http://forum.xda-developers.com/showthread.php?t=1992483 ) even though my build is JOP40D ?
Click to expand...
Click to collapse
just flash it in your recovery(if its a flashable zip). dont wipe a single thing, dalvik and cache have nothing to do with kernels. worst case scenario, it doesnt boot. then just reflash your rom in your recovery to fix it.
simms22 said:
just flash it in your recovery(if its a flashable zip). dont wipe a single thing, dalvik and cache have nothing to do with kernels. worst case scenario, it doesnt boot. then just reflash your rom in your recovery to fix it.
Click to expand...
Click to collapse
Ok thanks. Yes its a flashable zip, im going for the franco kernel.
Robert00001 said:
Ok thanks. Yes its a flashable zip, im going for the franco kernel.
Click to expand...
Click to collapse
franco is a good kernel. but most his kernels are in a img form, need fastboot for that. if its a zip, then flash it in your recovery, dont wipe a thing.
simms22 said:
franco is a good kernel. but most his kernels are in a img form, need fastboot for that. if its a zip, then flash it in your recovery, dont wipe a thing.
Click to expand...
Click to collapse
Yes I am sure this is a flashable zip. I found the img files and the zip files on the franco thread.
What about going back to stock? I just want to know if something goes wrong. Does flashing my rom get me the stock kernel back?
Robert00001 said:
Yes I am sure this is a flashable zip. I found the img files and the zip files on the franco thread.
What about going back to stock? I just want to know if something goes wrong. Does flashing my rom get me the stock kernel back?
Click to expand...
Click to collapse
It gets you whatever kernel was originally in the ROM.
063_XOBX said:
It gets you whatever kernel was originally in the ROM.
Click to expand...
Click to collapse
Okay thanks for the replies.
Robert00001 said:
Ok thanks. Yes its a flashable zip, im going for the franco kernel.
Click to expand...
Click to collapse
Even the .IMG files are easy enough to handle, OK so perhaps it might cost you a little money but within the Franco app (I don't know about others as not tried them) but you can simply just choose to restore a .IMG kernel file be it stock (which I have a copy of if you wanted it?) So you can swap and change as you wanted and the plus side of flashing this way is that you avoid the long reboot time dues to catch building again due to ram disk changes. I really think this is the best way of flashing kernels and certainly the easiest way if you wanted to carry on back to the OTA update route from Google.
For instance, I'm running stock takju rom 4.2.1 rom with Franco kernel and I have the stock boot loader and baseband and recovery and to install an OTA I just need to delete just one file and restore back to stock kernel that OTA update will install without troubles
Sent from my Galaxy Nexus
I tried flashing two different roms (synergy and chemistry) on my sprint galaxy s3. It turns on but then wont go past the "galaxy s III" logo. I just restored my backup and all is well but I really want to get multi window on this thing so I could really use some help as to what is not letting me boot up all the way. The last thing i messed around with rooting was my DroidX and with that it really mattered a lot which version of android you were flashing from. I have 4.1.2 the most recent update. Is that why these roms are not working? Any help would be much appreciated I am very excited to get a killer rom on this bad boy.
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
CNexus said:
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
Click to expand...
Click to collapse
I boot into recovery after i put the rom on to my sd card. Then wipe the factory data, cache partition, and delvik cache. I do those steps twice, then install the rom. The install seems to go fine, it always says successful at the end, it just wont go past that screen. Does it mater which version of clockworkmod I use?
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
CNexus said:
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
Click to expand...
Click to collapse
Thank you so much for your quick response. As far as I can tell, I am wiping everything I should be. I use clockwork recovery mod version: and the choices it gives you are: Wipe data/factory reset, wipe cache partition, and wipe dalvik cache. From all the instructional threads I've read, those are the only things you need to clear out before the install. My clockwork version is v5.5.0.4 which i think might be really old. Could that be my issue? Does it matter how I rooted it? I just tryed to put jellybomb v14 on it and it didn't even give me the galaxy s III logo. Luckily it booted back into recovery though. I really don't want to hard brick this thing.
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
A-Shin said:
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
Click to expand...
Click to collapse
clockworkmod v5.5.0.4
cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
Make the switch to TWRP v2.3.1.0 (newer ones I've heard have problems) but you will be thanking me later. It's way easier and much better than CWM... just an FYI for ya!
cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
I suggest trying a flash with TWRP. If you are unsure how to install TWRP, just download the Goomanager app, then choose install Open Recovery Script. But, before you install or change anything, look around a bit on how to install it. Make sure you follow directions step by step. After you have installed TWRP, try flashing again. Good luck!
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
cchrisrollins said:
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
Click to expand...
Click to collapse
Samsung bootloaders come unlocked by default, so yes
Easiest way to switch is to download Goo manager from the Play Store and have it install TWRP for you
Generally speaking, CWM is great on most devices, but for the S3 it's TWRP that's the best and easiest to use
And when flashing new roms, make sure to always format system, it prevents corrupted files from showing up because you would be installing the new system right on top of the old one if you don't
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you made a nandroid backup in TWRP (I'd recommend to put it on the external memory, but that's just me), you should be good to try any ROM you want (only Sprint ROMS). Just follow CNexus's post (linked for posterity). Wipe system as well as factory reset, cache, and dalvik, prior to installing the ROM.
cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you've already rooted, re-rooting isn't going to fix anything, so no need to go there.
As previously explained and detailed, do a full system wipe, and you'll be good to go.
Thank you guys so much for your very quick responses, thank you for bearing with my noobishness too haha. I am going to tryn reflash jellybomb tonight, I'll post on this thread how it goes (hopefully good).
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
cchrisrollins said:
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
Click to expand...
Click to collapse
It took me like 4-5 months to personally figure out that the problem was the kernel. You need to flash a kernel right after you flash the ROM. Either the stock kernels or better kernels like Anthrax will do. I know that for jellybomb, there's a kernel included in the Rom but for some reason,it got stuck on the gs 3 logo if I didn't flash another kernel.
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
cchrisrollins said:
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
No prob, just hit dat thanks button do you know where to get the kernels?
Zin0 said:
No prob, just hit dat thanks button do you know where to get the kernels?
Click to expand...
Click to collapse
I tryed the KT47 AOSP Jellbean kernel after flashing jelly bomb and it did the same thing it did before, black screen after flashing the samsung logo
Now I did go into fix permissions and it did say failed, is that abnormal?
This is my exact procces:
1. boot into TWRP
2. factory reset
3. system wipe
4. cache wipe
5. Dalvik wipe
6. Install from external SD: jellybomb v14
7. Wipe cache/Dalvik
8. Install Kt47 kernel
9. Wipe cache/Dalvik
Anything wrong there?