Hello,
I tried looking everywhere for the stock (default) 2.3.3. kernel (i don't want to flash an entire rom) if anyone know where i can find a link ,i would be most thankful.
thank you.
Goes in Q&A section I think.
Try Q & A thread
Sent from my LG-P999 using xda premium
crazy_agent said:
Hello,
I tried looking everywhere for the stock (default) 2.3.3. kernel (i don't want to flash an entire rom) if anyone know where i can find a link ,i would be most thankful.
thank you.
Click to expand...
Click to collapse
Did you do a backup of the rom before changing the kernel. It is contained in the boot.img in the backup. Just use one of the flashable zips that flash the kernel and replace the boot.img and wireless.ko files from an original nandroid with the one in the flashable zip (ones I looked at the boot.img as in the kernel subdirectory). wireless.ko goes in /system/lib/modules directory. Just use 7-zip and open archive. Delete the boot.img and paste in the one you want. Cloese out 7-zip and then you have a flashable zip with the stock kernel. I have attached the boot.img from the stock GB rom. Make sure you unzip the file and remove the boot.img. Do not try to flash this zip. It won't work.
I went ahead and made a flashable zip to restore the stock GB kernel. A big caveat here is that I have not tested it out myself as I am currently already rocking the stock kernel. If you are a brave soul you can try it out. Based on my experience it should work with no problems. If it does work please report back here and I will make a new thread in the development section. Many people have been looking for this, including myself. Once I venture out to another kernel to overclock, I wanted to have a way to restore to stock if I needed it. For now I am sticking with the stock kernel as I find the phone fast enough as it is.
Make sure you clear the Dalvik cache before rebooting or you might hang during boot or get a boot loop. The first boot will take several minutes due to Dalvik cache being rebuilt.
jboxer said:
I went ahead and made a flashable zip to restore the stock GB kernel. A big caveat here is that I have not tested it out myself as I am currently already rocking the stock kernel. If you are a brave soul you can try it out. Based on my experience it should work with no problems. If it does work please report back here and I will make a new thread in the development section. Many people have been looking for this, including myself. Once I venture out to another kernel to overclock, I wanted to have a way to restore to stock if I needed it. For now I am sticking with the stock kernel as I find the phone fast enough as it is.
Make sure you clear the Dalvik cache before rebooting or you might hang during boot or get a boot loop. The first boot will take several minutes due to Dalvik cache being rebuilt.
Click to expand...
Click to collapse
If this works it should def go in the dev section, unless it's already there.
Mister Hat said:
If this works it should def go in the dev section, unless it's already there.
Click to expand...
Click to collapse
I will post a thread in the development section once somebody confirms it works. I am pretty confident it will work. Using the same method that is used to flash custom kernels, but I used the boot.img and wireless.ko from the stock GB rom flash.
jboxer said:
I went ahead and made a flashable zip to restore the stock GB kernel. A big caveat here is that I have not tested it out myself as I am currently already rocking the stock kernel. If you are a brave soul you can try it out. Based on my experience it should work with no problems. If it does work please report back here and I will make a new thread in the development section. Many people have been looking for this, including myself. Once I venture out to another kernel to overclock, I wanted to have a way to restore to stock if I needed it. For now I am sticking with the stock kernel as I find the phone fast enough as it is.
Make sure you clear the Dalvik cache before rebooting or you might hang during boot or get a boot loop. The first boot will take several minutes due to Dalvik cache being rebuilt.
Click to expand...
Click to collapse
Not sure if I done anything wrong but here are the steps that i did:
- clear cache
- clear Dalvik cache
- flashed the zip file
- reboot
All I got was a black screen. I waited for about 15 mins but still black screen.
saotua said:
Not sure if I done anything wrong but here are the steps that i did:
- clear cache
- clear Dalvik cache
- flashed the zip file
- reboot
All I got was a black screen. I waited for about 15 mins but still black screen.
Click to expand...
Click to collapse
Did you flash it over the stock GB 2.3.3 rom? This is the original kernel and ony compatible with the stock rom. If you are running another rom that would result in a black screen due to incompatibility issues.
I'm using Xboarder's Stock Tweaked OTA Gingerbread build v1.2.2. I don't have the original stock rom. (stupid me, i didn't backup the stock rom before flashed another rom )
Edit: I tried again and it works beautiful. Thank you.
Thank you.
thank you all for your help.
Related
Hi All
Finally plucked up the courage to register and ask a question after lurking for the good part of 2 years.
I've an i9020A and have flashed CyanogenMod 9 v4.0.3 v1.0 which is great, however I wanted to try Steve Garon's kernel which just wont take.
I reboot into Recovery, wipe Dalvik Cache a couple of times, install Steve's kernel which apparently flashes no problem.
I reboot and get the optimising Android applications screen then check my kernel under settings.
It is still the original KalimochoAz kernel and I cannot turn on my wireless.
Now this has happened previously when trying to also update my kernel under CDTDroid's AndroidMe 1.2 which I could only fix by restoring back to 1.1.
Any idea on what may be wrong here guys?
Appreciation in advance.
Lally
Have you tried just flashing again? A bad flash often results in wifi not working and may be the cause of the about page showing the old kernel. Remember to wipe dalvik cache again, too.
Thanks for the reply Harbb, do you mean a re flash of the Kernel or ROM? If Kernel then yeah I have done, same scenario. I'll also try a re download of the Kernel to see if that improves anything but this is much akin to me trying to update from Speedy3 to Speedy4 under AndroidMe 1.2 which was unsuccessful.
Just the kernel, as you've already tried. Just remember to do a NANDroid backup (CWM --> backup & restore --> backup) when you have a stable, working ROM. Can save you alot of trouble if you don't have a relatively recent one.
Also, are you using CWM 5.0.2.0? And could it be that your phone isn't particularly happy about the 1100mhz OC with Steve Garon's kernel?
I'd suggest updating CWM recovery to the latest version.
Sent from my Nexus S using xda premium
Cheers for the help guys.
Yes, using 5.0.2.0, but something is not right cause I just tried to flash CWR again from within Rom Manager (4.8.1.3) and it gets to around 95% and the app gives 'Rom Manager is not responding.
Looks like I'll have to try a complete wipe and reflash.
Will report back the results.
Forget rom manager all together.
Download the recovery you want to use.
Flash it via fastboot
flash kernel.
I'd do what albundy said - flash a new recovery through fastboot and make sure the bootloader is unlocked (vol. up + power --> bootloader: unlocked)
Ok, downloaded CM9 1.1, redownloaded Steves kernel, reinstalled recovery from fastboot.
Wiped and formatted everything twice then installed from scratch.
So far everything is good, still getting errors on Superuser, but installing again via recovery seems to fix that issue.
Cheers chaps.
Good to know Lally, happy you got it sorted out.
Cheers Harbb, the test will be when I want to change the kernel again I suppose, one complete wipe and install a day is enough
Hi,
I tried several kernels for JB. Air, Matrix. None of them worked for me. After flashing it, it won't boot the system and turn off the device. I currently use JellyBelly 1.5. Any idea? Is it ROM bug? Thanks!
devcager said:
Hi,
I tried several kernels for JB. Air, Matrix. None of them worked for me. After flashing it, it won't boot the system and turn off the device. I currently use JellyBelly 1.5. Any idea? Is it ROM bug? Thanks!
Click to expand...
Click to collapse
I can't use Adam's Jelly Belly rom, as I have a NS4g, but I do follow his work. I believe that his rom comes with Thalamus kernel, and if you want to flash a different kernel, there is a file which needs to be deleted before doing so. There was quite a discussion about all this in his thread in the development forum. That's where you can figure it out ... good luck!
same for me
Hey i also tried to flash thalamus kernel but my phone didnt start it was hanged up on the boot screen. I am using Nexus S i9023 SCLD version stock rom 4.1.1 build JRO03E and it is rooted.
Can anyone please help me and also which other kernels are supported on stock rom.
There's a script you must delete in the init.d to use another kernel in Jelly Belly 0.1.5
Otherwise, your phone will poweroff
panks_4ever said:
Hey i also tried to flash thalamus kernel but my phone didnt start it was hanged up on the boot screen. I am using Nexus S i9023 SCLD version stock rom 4.1.1 build JRO03E and it is rooted.
Can anyone please help me and also which other kernels are supported on stock rom.
Click to expand...
Click to collapse
i have also a i9023 and i have allredy flashed bedalus kernel, thalamus and air kernel also matrix and vta2 worked for me..
i use JRO03E DX stock ROM..never had a problem
S.R.
(I use stock JB with Air #153, and got i9023. No OC, no NSTools, yet. I have no problem.)
On stock:
Try to do a factory reset/wipe data, or reflash the OS from scratch using factory images. And right after flashing the rom, flash the kernel. Even before installing any apps.
On JBelly:
For this, I think the Thalamus kernel is the best, the rom is come with it, so they made for each other If this kernel works with it, i think it is unnecessary to switch to another kernel right now.
Because JB kernels are not final yet, are "immature", there can be compatibility issues, collisions between (certain functions of) roms and kernels.
After a 2 or 3 releases, both on rom and kernel side, there will be more complete and stable versions.
Have you tried to fix permissions ?
Go to /etc/init.d/ folder and delete a file called 'kernel'. You can read it first if you want.
This is basically a hack that AdamG added to avoid everyone changing kernels and reporting problems about the ROM. He only allows thalamus kernel.
Can please provide me detailed steps of how to flash a thalamus kernel on stock jb because i think the procedure is wrong. I did the following steps:
1. Reboot into recovery( I am using Clockwork Mod recovery touch 6.0.1.0)
2. Wipe Cache partition
3. Wipe Dalvik cache
4. Install the kernel zip file
And after i tried restarting my phone but it hanged up on the boot screen.
Please someone advise me the correct steps if this is wrong
. Thanks in advance
Sent from my Nexus S using xda app-developers app
panks_4ever said:
1. Reboot into recovery( I am using Clockwork Mod recovery touch 6.0.1.0)
2. Wipe Cache partition
3. Wipe Dalvik cache
4. Install the kernel zip file
Click to expand...
Click to collapse
I think the cache partition wipe is your problem. You shouldn't have to wipe anything if you're flashing _thalamus' kernel on stock JB. Just flash and reboot. I've done it plenty of times without problems.
devcager said:
Hi,
I tried several kernels for JB. Air, Matrix. None of them worked for me. After flashing it, it won't boot the system and turn off the device. I currently use JellyBelly 1.5. Any idea? Is it ROM bug? Thanks!
Click to expand...
Click to collapse
To not have to deal with third party kernel support there is /system/etc/init.d/00kernel that simply powers off your phone if you flash another kernel.
Flash the rom to boot it, delete the file, then flash any kernel you want as you usually would.
charchuck said:
I think the cache partition wipe is your problem. You shouldn't have to wipe anything if you're flashing _thalamus' kernel on stock JB. Just flash and reboot. I've done it plenty of times without problems.
Click to expand...
Click to collapse
wipe is not needed...
but fix permissions should be done...but I´m not sure thats required for all kernel.
S.R.
so this are the final steps...
shivasrage said:
wipe is not needed...
but fix permissions should be done...but I´m not sure thats required for all kernel.
S.R.
Click to expand...
Click to collapse
Firstly, thanks for replying. I need to do the folloing steps (just to confirm because its better to do so and also i dont want to again restore a backup)
1. Reboot into recovery
2. Wipe Dalvik Cache
3. Install the kernel zip file
4. Fix Permissions
or 3. Fix Permissions, and then
4. Install kernel zip file
Please advise the correct steps and thanks in advance.
(I know i am getting a bit more concerned because i had it twice and i am not able to flash the same. So, I am trying to get a correct way and this the best place to ask. XDA rocksssssss<3<3<3)
panks_4ever said:
Firstly, thanks for replying. I need to do the folloing steps (just to confirm because its better to do so and also i dont want to again restore a backup)
1. Reboot into recovery
2. Wipe Dalvik Cache
3. Install the kernel zip file
4. Fix Permissions
or 3. Fix Permissions, and then
4. Install kernel zip file
Please advise the correct steps and thanks in advance.
(I know i am getting a bit more concerned because i had it twice and i am not able to flash the same. So, I am trying to get a correct way and this the best place to ask. XDA rocksssssss<3<3<3)
Click to expand...
Click to collapse
There's no need for all that... flash jellybelly latest version, boot with the original kernel and delete /system/etc/init.d/00kernel with Rom Toolbox or Root explorer. After that you can flash the kernel that you want. Mind that this will only work for version 0.1.5.1, versions after that one will probably have a framework check to prevent flashing 3rd party kernels because the dev of jellybelly doesn't want to be disturbed with bugs caused by other kernels then not the Thalamus one.
---------- Post added at 08:55 AM ---------- Previous post was at 08:34 AM ----------
Checked. Version 1.0.0 only allows Thalamus kernel to be flashed. A framework check doesn't allow 3rd party kernels to be fixed so either you stick to the stock kernel of jellybelly or get another ROM so you can use other Kernels.
Panks_4ever
What I always do.. (phone i9023 X-JB Stock).
1. flash kernel zip
2. wipe cache
3. wipe dalvik
4. fix permissions
i only know that thalamus kernel don´t need any wipe...also i don´t know if this procedure is right or not
and i don´t won´t discuss about i only can report what worked for me so try it or not its your decision....
S.R.
thank you
shivasrage said:
Panks_4ever
What I always do.. (phone i9023 X-JB Stock).
1. flash kernel zip
2. wipe cache
3. wipe dalvik
4. fix permissions
i only know that thalamus kernel don´t need any wipe...also i don´t know if this procedure is right or not
and i don´t won´t discuss about i only can report what worked for me so try it or not its your decision....
S.R.
Click to expand...
Click to collapse
DeuXGod said:
There's no need for all that... flash jellybelly latest version, boot with the original kernel and delete /system/etc/init.d/00kernel with Rom Toolbox or Root explorer. After that you can flash the kernel that you want. Mind that this will only work for version 0.1.5.1, versions after that one will probably have a framework check to prevent flashing 3rd party kernels because the dev of jellybelly doesn't want to be disturbed with bugs caused by other kernels then not the Thalamus one.
---------- Post added at 08:55 AM ---------- Previous post was at 08:34 AM ----------
Checked. Version 1.0.0 only allows Thalamus kernel to be flashed. A framework check doesn't allow 3rd party kernels to be fixed so either you stick to the stock kernel of jellybelly or get another ROM so you can use other Kernels.
Click to expand...
Click to collapse
Thank you shivasrage and DeuXGod. I am surely goona try out this, i am being eagerly waiting to flash a custom kernel because as compared to ICS i feel JB is eating up more battery. Thank you so much:good:
I'm having a problem flashing marmite 4.4 to the newest miui build (2.9.7).
Basically in cwm recovery and flashed the kernel.
Will say "ununderstandable message 3" and "lid is licked"
Reboot the device and it will get stuck on the miui boot screen.
Tried installing both the "stock OTA" and "All other ROM" version of marmite.
Same message comes up.
Already tried performing a full wipe (actual full restore, format system, format boot), reload the ROM.
Tried wipe cache and dalvic (even though it is not needed)
Just wondering if there is something incompatible or not.
I was able to flash air kernel without issues.
I haven't tried an older version of marmite yet, but will try later.
I'm not blaming marmite, it could be miui as well, or it could be just me.
I'm certain I'm flashing correctly.
I read bedalus' marmite post and saw 2 others with this issue (not same version of kernel or ROM).
The suggestion was that they didn't use the correct kernel for ROM.
I would assume miui would not be categorized as "stock OTA", so I tried "all other ROM" version first"
Am I doing something wrong?
There is a new version 4.5 the message you get I believe is like a joke. It does show however that the installation was successful.
Never experienced boot loops flashing his kernels.
Sent from my Nexus S
Actually, I downloaded that one just now to try and same issue.
It will just stall at the miui (ROM) boot screen.
I am trying some other stuff right now as well.
Really want to use this kernel. :good:
I'll report back later.
Thanks for the help.
Good luck. His kernel offers great speed and stability!
Sent from my Nexus S
For marmite 4.5, did a full wipe again, even formatted the SD partition.
So flashed miui 2.9.7.
Booted to the ROM.
Made sure things seem normal in the ROM.
Restarted just to be sure.
Boot back to recovery.
Flashed marmite 4.5
And it is stuck on the miui loading screen again.
Only thing I haven't tried this time is to fix permissions. (didn't wipe cache or dalvic either)
I'll try it again. :laugh:
Since I formatted the SD partition, it should rule out that it was something on the SD card right?
It's time consuming to copy things back to the NS.
I'll try an older version of marmite afterwards and then an older version of miui.
It should tell me what is causing the lock up by then. I think. :silly:
.... yes I have a lot of time ....
I forgot to mention one thing.
I'm flashing the official Chinese version of miui 2.9.7.
Wonder if that's the cause.
I guess I will download the US or UK version to try as well.
Well if your phone boots with original kernel, it must be kernel related. There's no need to wipe anything before flashing a kernel. Just flash it. It could be that the Chinese rom is different from the others, but that's a guess I'm no expert on compatability.
Sent from my Nexus S
kwibis said:
Well if your phone boots with original kernel, it must be kernel related. There's no need to wipe anything before flashing a kernel. Just flash it. It could be that the Chinese rom is different from the others, but that's a guess I'm no expert on compatability.
Sent from my Nexus S
Click to expand...
Click to collapse
Took some time to test, but sort of found my answer.
It's the official Chinese miui that's causing the issue.
Well at least some component in the ROM.
I tested with the MIUI UK (miuiandroid) version 2.9.7 and it installed like a charm.
Before flashing the UK version, I tested with earlier versions of marmite (4.3 and 3.5) on the Chinese 2.9.7.
All failed at the ROM boot screen.
I should check with the miuiandroid team and see what they changed that made it different.
When I was testing I did a full wipe, installed ROM, booted ROM, boot to recovery and flashed the kernel.
I didn't even wipe cache or dalvic (which is not needed anyways).
I had to do a full wipe because the ROM just wouldn't boot back up afterwards.
I'm tempted to test with an earlier version of the official Chinese miui and see if it makes any difference.
... too much time and/or no life ... :laugh:
Lol, well it's good you found your answer So its not a waste lf time as you learn from this
Sent from my Nexus S
If you flash air kernel, and if it worked, I guess marmite's boot.img type can cause a problem.
Sent from my Nexus S using Tapatalk 2
Articudos said:
If you flash air kernel, and if it worked, I guess marmite's boot.img type can cause a problem.
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Not sure what the boot.img type is, but I'll look it up. Thanks.
I posted on miuiandroid forums and someone replied saying that the Chinese version is odexed and not busyboxed.
UK and US version is definitely deodexed, I downloaded them and checked. I haven't found out how to check busybox.
I have a few choices.
1. I can use the UK or US version, since I was able to flash marmite on them... easy way out.
2. Find out how to deodex the ROM and, I guess, how to add busybox (?)... I get to learn more stuff.
3. Use a way faster ROM (eg. Paranoid Android - great ROM by the way!) and flash marmite on it as well... but really want to use miui again.
Thanks guys for your help though. Really appreciate the information. :good:
Glad you found a solution
I brought my phone to stock. Installed a rom. Fine. Went back into CWM recovery. Every time I reboot the phone (power button or in recovery) it returns to recovery.
I brought my phone back to stock again. Installed another rom. Went back to TWRP. Again, I can't reboot the system, only return to recovery.
Is there a way to fix this, or can I never use recovery after installing a rom?
{I'm sure this question has probably been asked before, but I've been searching for hours and can't find a fix.)
Did you wipe data & caches? What did you flash and how? Cwm, heimdall or Odin? Sgh-t959v under battery?
Find lumin30's guides. They/he will steer you straight.
Sent from my SGH-T959V using xda app-developers app
t1op said:
I brought my phone to stock. Installed a rom. Fine. Went back into CWM recovery. Every time I reboot the phone (power button or in recovery) it returns to recovery.
I brought my phone back to stock again. Installed another rom. Went back to TWRP. Again, I can't reboot the system, only return to recovery.
Is there a way to fix this, or can I never use recovery after installing a rom?
{I'm sure this question has probably been asked before, but I've been searching for hours and can't find a fix.)
Click to expand...
Click to collapse
This would occur for me when I had installed an incompatiable kernel with the ROM I am trying to install. I would fix this problem by either looking at the thread for a compatiable kernel if it does not come with one, or if it is an ICS ROM, Team Acid's ICS Kernel works fine. I think Team Acid's ICS kernel is included in their unofficial AOKP release if you have that downloaded. I hoped this help!
WayTooGosu said:
This would occur for me when I had installed an incompatiable kernel with the ROM I am trying to install. I would fix this problem by either looking at the thread for a compatiable kernel if it does not come with one, or if it is an ICS ROM, Team Acid's ICS Kernel works fine. I think Team Acid's ICS kernel is included in their unofficial AOKP release if you have that downloaded. I hoped this help!
Click to expand...
Click to collapse
All of our ROM's have kernels. It is the kernel you flash from that makes a difference. And once you flash the ROM, the kernel that is packaged with the ROM replaces the kernel you previously had/flashed from. However, the OP of the ROM's usually specify what you need to do to flash the ROM.
lumin30 said:
All of our ROM's have kernels. It is the kernel you flash from that makes a difference. And once you flash the ROM, the kernel that is packaged with the ROM replaces the kernel you previously had/flashed from. However, the OP of the ROM's usually specify what you need to do to flash the ROM.
Click to expand...
Click to collapse
Ah I see. But my point was that some ROMs state that the user must be on an ICS ROM/Kernel to flash this. I guess I wasn't very clear as I am new here and lack understanding.
champ1919 said:
Did you wipe data & caches? What did you flash and how? Cwm, heimdall or Odin? Sgh-t959v under battery?
Find lumin30's guides. They/he will steer you straight.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
I used Odin to return to stock. I used Super One Click to root. I used root explorer modify the recovery to allow me to boot into "CWM final for Froyo". That much each and every time.
The first time I installed
[TFQ - 30/12/2012]X.A.O.K[Kanged - Xperia Style]
That is an ICS rom. Installed fine with a new CWM.
The second time I installed the same.
The third time I installed
ROM-MTD-TWRP-ICS-4.x-Audiophile
That is another ICS rom. Installed fine with TWRP.
Each and every time, when returning to recovery to flash more, I got stuck. I can't boot to anything except recovery.
My brother suggested that the problem is using the Volume up and down and power button ("three finger salute") to return to recovery instead of from OS power down menu.
For a fourth time I started over again. Now, using the reboot>recovery, everything works fine.
One thing, you need to have ginger bread bootloaders. So, when you say Odin back to stock, are you referring to kj6?
You could cut down some of the work by using Odin to flash a kernel with recovery & root in it. Antonx & drhonk both have kernels that will do that with odin.
I flash bhundven's cm9 Rom before jumping to any of the others(and wipe between). I believe some of the Rom authors have that in their instructions.
Sent from my SGH-T959V using xda app-developers app
Yeah... GB bootloaders, not Froyo. Your return to stock should be a return to GB stock, not Froyo... and your return to stock can be a return to a rooted stock. If you want to make your life less painful.
It's about MTD to BML, not really about the base version. You just don't want to wipe out what allows later stuff to actually work properly...
Thanks for the advice. I haven't used custom roms very much. Trying to figure out which ones to choose was difficult. I started on stock Gingerbread, but everything I encountered in searching indicated that I needed to go back to Froyo to get CWM then go from there. ...Perhaps I kept running into very old instructions? In any case, should I need to go back to stock again some day, I'll try to figure out which GB roms I could use, including root and custom recovery.
I guess the solution to my problem is: 1) flash back to Froyo or Gingerbread; 2) after flashing an ICS+ rom, only go to recovery from OS reboot menu (never "three finger salute").
I'm actually surprised that people don't run into this problem more often, enough to create a sticky about it. I'm sure I'd still be pulling my hair out if my brother hadn't run into the problem on his Fascinate a year ago.
On mine, the 3 finger boot to recovery works fine. Then again, I haven't been on Froyo since Samsung and TMo said to stop using Froyo back in November (October?) 2011 with the official 2.3.6 update. And the only boot-loops I have, whether recovery is booted through the menu or salute, are when I flash something invalid.
Theraze said:
On mine, the 3 finger boot to recovery works fine. Then again, I haven't been on Froyo since Samsung and TMo said to stop using Froyo back in November (October?) 2011 with the official 2.3.6 update. And the only boot-loops I have, whether recovery is booted through the menu or salute, are when I flash something invalid.
Click to expand...
Click to collapse
Interesting... Perhaps if I went back to a gingerbread stock then upgraded to ICS the problem wouldn't occur?
I'll have to try that the next time I might need to return to stock.
Hello,
First I just want to say thank you to the mods for running a great forum and to the devs for keeping this device current.
I just struggled over a period of days with this issue.
The end result being, that you need to go to CM9 BEFORE you try JellyBean or later!
Just hope this helps someone else who missed that instruction.
Thanks devs/mods/everyone for keeping this device alive!!!! :good::good::good:
*EDIT* correction... i THINK you need to go CM9 Before trying something else
Not all ICS ROMs require CM9, but you must have at least CWM5 recovery to be able to flash CM9 or these ROMs. Follow ROMs' OP instructions.
I personally tested HebMIUI flash over Stock GB with CWM5 (Basic with a twist kernel) without going through CM9.
Hi,
I have managed to put on a kernel that's not working. Is there a way to revert back to the original kernel? I do have a nandroid backup, but re-installing that didn't put on the old kernel.
I am using Liquidsmooth ROM. Any help would be appreciated.
Thanks.
if you can boot into the rom use flashimagegui, if not do the normal fastboot the boot.img then do it again with flashimagegui to get the modules.
what kernel did you try to flash? the only kernel that will work with new liquidsmooth is cm10.1_vz-oc-linaro.3.zip. it contains modules, if you aren't s-off then you need to flash boot.img in fastboot then flash again in recovery for the modules.
DvineLord said:
if you can boot into the rom use flashimagegui, if not do the normal fastboot the boot.img then do it again with flashimagegui to get the modules.
what kernel did you try to flash? the only kernel that will work with new liquidsmooth is cm10.1_vz-oc-linaro.3.zip. it contains modules, if you aren't s-off then you need to flash boot.img in fastboot then flash again in recovery for the modules.
Click to expand...
Click to collapse
I did exactly that, presuming that it was working... But I have been facing issues. The phone restarts every once in a while and I have managed to get to this condition after multiple wipes and restoring a backup. Anyways I don't know what the issue is I was just wondering how to revert back to the original kernel.
im running Liquid-JB-v2.1-RC2-evita.zip and cm10.1_vz-oc-linaro.3.zip. there seem to be some general issues with the rom that present as basically glitching and gets worse overtime atleast for me. im pretty sure it isnt related to the kernel. but to revert kernel just load the liquidsmooth zip into flashimagegui and itll pull the needed files, let it wipe cache and dalvik then reboot.
DvineLord said:
im running Liquid-JB-v2.1-RC2-evita.zip and cm10.1_vz-oc-linaro.3.zip. there seem to be some general issues with the rom that present as basically glitching and gets worse overtime atleast for me. im pretty sure it isnt related to the kernel. but to revert kernel just load the liquidsmooth zip into flashimagegui and itll pull the needed files, let it wipe cache and dalvik then reboot.
Click to expand...
Click to collapse
I do not have s-off does the flashimagegui works even without it?
strommer666 said:
I do not have s-off does the flashimagegui works even without it?
Click to expand...
Click to collapse
yes, Flash Image GUI
you should also s-off your phone it will make life ALOT easier and the process is simple take like 2 minutes.
DvineLord said:
yes, Flash Image GUI
you should also s-off your phone it will make life ALOT easier and the process is simple take like 2 minutes.
Click to expand...
Click to collapse
Thanks I'll make sure I do that..
also new stable build of liquidsmooth just got released. you should flash it. imma flash it with a clean full wipe. but you should s-off first so you dont have to flash boot.img separately every rom.
DvineLord said:
also new stable build of liquidsmooth just got released. you should flash it. imma flash it with a clean full wipe. but you should s-off first so you dont have to flash boot.img separately every rom.
Click to expand...
Click to collapse
Ya, I saw the new version wanted to try that which is why I wanted to got to the old kernel version. I had tried installing it with the linaro kernel but it gets stuck on the boot screen.
Update: - I installed the flash gui image, then extracted and installed the kernel , factory reset the phone, then installed the latest liquid smooth build. But it is still not going ahead of the boot animation.
Update 3 :- Got the old kernel back. Did a restore. Working fine now . But still for some reason I cannot install the new ROM yet.
strommer666 said:
Ya, I saw the new version wanted to try that which is why I wanted to got to the old kernel version. I had tried installing it with the linaro kernel but it gets stuck on the boot screen.
Update: - I installed the flash gui image, then extracted and installed the kernel , factory reset the phone, then installed the latest liquid smooth build. But it is still not going ahead of the boot animation.
Update 3 :- Got the old kernel back. Did a restore. Working fine now . But still for some reason I cannot install the new ROM yet.
Click to expand...
Click to collapse
you need everything. you don't need to extract the kernel. just load the whole zip file.
DvineLord said:
you need everything. you don't need to extract the kernel. just load the whole zip file.
Click to expand...
Click to collapse
I did load the full file and the flash gui image extracted the kernel. The thing is I have the kernel now, but still I can't seem to be able to install the new version of the LiquidSmooth build. I am doing a nandroid backup of this thing and try installing it again.
well new liquidsmooth is nice, im using cwm now as recovery since ive had tons of issues with twrp since version 2.2.2.0