I have installed CPU analyser, and with stock ROM I think the slowest it goes is 300mhz, WIth a modded ROM it slows down to 110mhz. So I'd like to use modded kernel with stock ROM (I've found no ROM's to be as quick or stable as stock)
Is it possible to have stock LK1 firmware, but with rafa's modded kernel? My procedure is
1) Recover LD1 firmware with ODIN
2) Reboot update LK1 in KIES
3) add super user. Boots, make calls etc
4) Apply kernel and modules. Boot and lost IEMI. I have tried restoring IEMI from my backup in galaxy toolbox, rebooted. But it still doesn't work.
Am I doing something wrong, or does the stock ROM not support modded kernel/modules in anyway?
Also if I do get it working, do I need some kind of CPU/battery saver or are the routines built into the kernel, no other apps are needed? I tried one app, it seems to work but it keeps on popping up with a message that it's using superuser priv, so it's quite annoying.
flash modules of kernel after flashing the kernel without rebooting in between!
this way u won't loose imei!!
whenever superuser permission message come up, there's an option below to remember the choice, click it and then message won't appear again!
ah so flash kernel, then modules without rebooting? I'm pretty sure a couple of guides say flash kernel, reboot (go straight back into recovery) then flash modules.
which specific (filename) kernel and modules to use with stock LK1 ROM?
201303051129-E3-boot.img
and
201303051129-modules
did that, emergency calls only! arggh
Try flashing modules after reboot.. Flashing modules should solve imei problem!
Sent from my GT-S5830i using xda app-developers app
Related
My question may be easy but I can't understand this...I had vr 2.1 and went to vr 2.3 by flashing the Rom through recovery mode.all ok.then I installed Ninphetamine kernel 2.0.2 but then I lost root access.is this normal or did I screw up something?after losing root I flashed with odin cf-root and now everything is ok but I prefer Ninphetamine...any help?
Sent from my GT-I9100 using XDA App
You probably need more than Ninphetamine's kernel to get root. (I have no clue about this) But Cognition uses the Ninphetamine kernels too and it works just fine. Maybe they're incompatible with VR?
The way I understand it (each phone manufacturer seems to be different) is that the kernel frequently blocks either access to root, or the installation of specific files.
To have root, you need the su executable, and an apk which allows applications to ask for root priviledges. Both of these are stored in /system, and are not part of the kernel. However, in order to install these, you either need to re-flash a ROM with them pre-installed, or install a kernel and other files over the top of your existing rom using ODIN.
Flashing a new kernel may remove recovery (CWM), but doesn't (as I understand it) affect root. Some kernels are incompatible with certain ROMs though (I'm still on the stock kernel)
Now you have root again, try re-installing the kernel (point CWM app at the zip file did it for me)
Hello,
Today I thought, let's try out ICS! Found this guide (can't post outer links, search for "android advices ICS Android 4.0.1 XXKP2 " in google), and used it to update my phone to ICS.
Well, after trying out the rom, I would like to go back to my MIUI backup, rooted it, installed clockworkmod recovery and booted up the recovery mode. The recovery said "can't mount /cache/*" for all cache folders. So I couldn't restore my backup.
After reading some stuff I installed a recovery through Odin. Worked like a charm, no alerts of mounting failures. Restored my backup, but when it was rebooting it gave an "Kernel Panic - Upload mode" screen. Couldn't do anything, so put the battery out and back in.
After this I installed ICS again with the same steps as in the guide. This worked! Rooted and installed recovery again, no problems so far. Tried a fresh install of MIUI but with the same problems.
So I can flash ICS but I can't flash any other rom, what can be the problem?
Every help and tips are welcome!
Thanks in advance!
Same thing happened to me last nite, kernel panic, and im panic too. This happened after flashing that cm9 coz i just wanna try and see how cm9 look like and i know im not going to stick with it, just for trying. Now im back to miui.
What i did is i flashed back to stock rom, root, then flash miui, or any rom that you want. Very simple.
Rom : MIUI ICS XGT 'EXTENDED'
Kernel : Xcell-69X
Modem : XXKP8
Sent from Galaxy SII
I have the same problem I guess, tried ICS, went back to stock which I was using. Got Kernel panic upload mode several times, solution for this was flashing an older 2.3.6 version.
After this no more kernel panics...
But I can't flash any custom roms anymore.
My phone's working luckily but it doesn't work like it's supposed to
Gepstra said:
I have the same problem I guess, tried ICS, went back to stock which I was using. Got Kernel panic upload mode several times, solution for this was flashing an older 2.3.6 version.
After this no more kernel panics...
But I can't flash any custom roms anymore.
My phone's working luckily but it doesn't work like it's supposed to
Click to expand...
Click to collapse
Thats not true my friend, you flash any custom rom. Nothing need to worry about.
Rom : samsung stock firmware
Kernel : stock kernel
Modem : stock modem
Sent from Galaxy SII
Gepstra said:
I have the same problem I guess, tried ICS, went back to stock which I was using. Got Kernel panic upload mode several times, solution for this was flashing an older 2.3.6 version.
After this no more kernel panics...
But I can't flash any custom roms anymore.
My phone's working luckily but it doesn't work like it's supposed to
Click to expand...
Click to collapse
Did you make sure to flash back the old GB bootloaders? Restoring a backup wont flash them back.
I tried following this:
http://forum.xda-developers.com/showthread.php?t=1580070
"INSTRUCTIONS" part:
* RECOVERY: FACTORY RESET IF YOU WERE USING ANOTHER ROM!
* RECOVERY: Install Rom: Download
* RECOVERY: Install Gapps, ALWAYS-EVEN FOR UPDATES: Download (find the latest one that carries the "jb" tag)
* RECOVERY: Wipe Cache Partition
* RECOVERY: Wipe Dalvik Cache
* Reboot and enjoy
Click to expand...
Click to collapse
did all the above, never forgot any of the 3 wipes/resets that were necessary.
used this rom file:
http://goo.im/devs/paranoidandroid/roms/i9100g
(latest one)
for my Galaxy Samsung S II GT-i9100g.
I had CWM and also had a rooted android 2.3.
first boot it showed me the normal samsung boot screen, for 45 minutes....
so I restarted and the phone gave me the same behaviour..
so I removed the battery to turn off the phone, and attempted to reinstall the whole thing, going through this process again from scratch
not forgetting any of the wipes etc...
now every time I boot it, it leads me to CWM instead of the normal boot screen and the expected paranoid rom eventually...
I followed this path because CM 10 failed me because upgrading from 2.3 to 4.x requires going through something that is called "stock" or as I think it actually is - google's /manufacturer's original firmware/rom production line thingy
and after that it needs me to re-enable root on that stock rom all over again. And only then I may attempt to install CM10...
so I picked paranoid instead, because in it's instructions is showed me no such constraint. heck it can't give me that constraint because there is no "stock" of android 3.x for smartphones
but then this issue happened... so I need your help.
I found similar search results but couldn't figure out their solutions or how whatever triggered that same problem (which isn't mentioned in those threads) is related to what I did to my phone... (so that I will not repeat the same mistake)
your help is much appreciated as I need it so so much!
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
gastonw said:
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
Click to expand...
Click to collapse
by "flash"ing you mean the option "install from a zip file" in CWM in recovery mod?
if I have some rom, the only way for me to install another would always be by going through that middle step of also installing a 'stock' rom as well?
there is no way around it?
installing a 'stock' rom, wouldn't it make me loose my root I have on the phone and force me to root it all over again before I can continue install anything at all?
thats the reason I wanted to try out the paranoid way of doing this instead of the CM10, because I have no interest in rooting my already rooted phone and I hoped that paranoid does not need me to go to stock first....
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
some questions
ONE QUICK IMPORTANT QUESTION BEFORE THE REST:
If I use mobile odin, will I be able to use it to install stock rom and also root it at the same time?
SECOND IMPORTANT QUESTION:
you said I could flash whatever I want and still have root, but my problem was not 'not having root', it was not having the flash process complete successfully... how do I attack that?
THIRD IMPORTANT... info... :
My "BUILD" version is "GINGERBREAD.XXKL5", isn't that a 'stock' one?
If you don't have a lot of time,
then the rest of this post is not as important as the 2 questions above...
gastonw said:
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
Click to expand...
Click to collapse
the saddest part is that I couldn't figure out most of what you just said
what is 'nandroid'? 'flashing'? do you mean like dd in linux? copying to the entire flash storage device?
'IMEI'? huh..? O_O
at the moment I was able to 'get back on my feet', I restored everything back to normal with manual copying of important parts of the CWM corrupted backup from this week, and old stuff for a CWM backup made few months ago.
now that I am at a 'normal' state.. I want to install paranoid or CM10 on my GT-I9100g.
which one of those 2 does not force me going through installing stock?
I have this fear of installing stock that it will take away my root and that I will have to use adb from command line to re-enable root afterwards, which I have bad experience with.
I need to know a few things before I attempt to install stock via CWM,
will installing stock disable my root? will installing stock disable my ability to load recovery boot menu CWM?
is 'root' an attribute or state that belongs to the running rom itself after boot has been completed and to that only?
or does it also belong to the state the device is at while in the recovery boot menu CWM ?
I tried messing around with ADB in the past to see if I could root devices via that way but it wasn't very successful so thats why I'm afraid of having to attempt it again.
bumpitybump
even though a year later, I would still love some replies
resurrecting my motivation to do this once again.
copy paste from my other post;
before flashing, you will need these;
-stock rom (get it from Sammobile, sign in and select your country and phone model)
-blazing kernel for recovery (search in XDA)
-custom rom (CM, PA, Supernexus...your choice)
-backup your data
-GApps (get the latest one)
-you must know what are you doing and dont flame/blame other member if something wrong
how to flash;
-make sure you are on latest stock rom (mine is JellyBean 4.1.2), if not like the OP, flash the latest stock rom using Odin;
*reboot your phone in Download Mode
*open Odin and in PDA option select your stock rom and then Start
*if done it will display Done and disconnect your phone, it will boot up
*if bootloop, reboot into Recovery Mode, and then wipe data and cache, and then reboot normally
-after updating your phone to latest stock rom, copy your custom rom, GApps, and Blazing kernel into external SD card, then reboot into Recovery Mode
-choose "apply update from external storage" and choose Blazing kernel, wait for it to finish update
-reboot normally, and then reboot back to Recovery Mode. this time you will notice that your recovery is different from the previous one
-select install zip > choose from external storage/sdcard 1 > and then choose your custom rom. then wait for it to finish update
-repeat the above step to install GApps, and after that reboot normally
-if bootloop, reboot back to Recovery Mode and then wipe data, cache and dalvik and then reboot
-done, now you are running on custom rom
Click to expand...
Click to collapse
and about the root, i believe that almost all custom rom rooted
Would the following work as a way to try out, for example Cyanogenmod 10. I am currently running a 4.1.2 install (pretty much stock just rooted/cwm via Philz as per the tutorial). I have a complete backup made via Philz recovery of this rom along with the kernel (which I believe is still stock from that) and efs.
1) Install a custom kernel (eg. dorimanx 9.x?) via the Philz recovery.
2) Install cm-10.2-20140102-NIGHTLY-i9100.zip.
3) To return to the original rom, reflash the original kernel (with whatever CWM is included in dorimanx) - then reflash the backed up rom via the same recovery?
I hope this is clear enough a question.
I believe you have to flash a stock rom through Odin, to return to complete stock. Just flashing a stock kernel isn't enough, and is surely not going to work (so don't do it).There are also tutorials how to remove the yellow triangle afterwards.
Please correct me if I'm wrong
Donnie Sins said:
I believe you have to flash a stock rom through Odin, to return to complete stock. Just flashing a stock kernel isn't enough, and is surely not going to work (so don't do it).There are also tutorials how to remove the yellow triangle afterwards.
Please correct me if I'm wrong
Click to expand...
Click to collapse
This is the part I'm most unsure of. Ideally I'm trying to figure out the process that lets me go from CM10.2 (and whatever recovery) to the point I am running the backed up rom rooted with PhilZ-cwm6-XWLSW-XEU-5.06.1-signed.zip again. Very confused on how to do so.
TopherBrink said:
This is the part I'm most unsure of. Ideally I'm trying to figure out the process that lets me go from CM10.2 (and whatever recovery) to the point I am running the backed up rom rooted with PhilZ-cwm6-XWLSW-XEU-5.06.1-signed.zip again. Very confused on how to do so.
Click to expand...
Click to collapse
Topher,
If you have rooted and cwm via philz, you already have a modified kernel installed. I believe the philz-cwm6 should be as close to stock kernel with the CWM incorporated. You don't need to add another kernel, because it will be replaced when you install the custom ROM. You should just be able to flash the cm10.2 via philz or via odin. You can then flash the dormanix kernel if you want - can't comment on that kernel - or if it has cwm included.
I would also suggest that you consider backing up you /efs folder (one with you imei information etc) prior to flashing any custom roms. People have been using hcKtool to do the backups and also an actual copy as well.
Depending on the custom rom, you may have connection problems with your network. So you may want to consider keeping a copy of your modem.bin file from your stock rom handy in case you need to flash onto the custom rom.
If you want to go back to stock, then you just need to flash the stock rom - you can check sammobile website for your stock rom or use the backup that you made.
I should point out that I have yet to do any of the above - I gathered this from reading the forums. Some more experienced forum users can add corrections. I rooted my phone a couple of months ago and now considering installing custom rom in the next couple of months.
Thanks.
if u flash a custom rom (cm10.2 for example), it already included kernel as well. so if u want to try out other custom kernel, i can flash it after you are done flashing a custom rom but make sure it is compatible with your android version. (u cant use custom kernel that not support android 4.3 with a custom rom running android 4.3)
I installed JellySnap about a week ago just to try it out and decided that I didnt like it. Alot of force closing of apps going on and that was just annoying. Also couldnt view any pictures in the messenger app or a third party messenger app without the apps force closing. "Google search has unfortuantely stopped." I got around that by installing a new launcher.
Anyway, whenever I go to install a new ROM the installations always abort immediately after the installation begins. I got a status 7 error with one of the roms. A thread I viewed a little earlier advised me to edit one of the scripts to remove the cert verification, alas, that did not help either. So I am at a loss as to what to do. I could have sworn that when I first installed JellySnap it actually went through and overwrote my CWM with an older version it had in its zip package. I could have sworn that I had an earlier version of CWM. The touch version. Now I have to use the volume and home buttons. Version 6.0.1.2-siyah.
Any ideas on how I can fix this and start installing some new roms? Ive tried the latest updates of cyanogenmod, revolution, omega and resurrectionremix so far.
Thanks
What kernel are you on? Try installing philz kernel and reboot recovery. I think that worked for me when I had similar problem a while ago.
Edit. You probably have Apolo kernel, if jellysnap has the option for Dori you could reinstall your ROM and choose Dori in aroma. Good luck.
Sent from my GT-I9100 using xda premium
Try flashing Stock room with odin (sammobile.com) and then flash the room you want
Sent from my TF101 using XDA Premium 4 mobile app
flash a new recovery . and reboot recovery ..you are done . happens with many custom ( kitkat in particular ) as these roms are still in development . flash a new recovery ( 6.0.4.5) reboot recovery and flash the new rom . no need to flash stock via odin or anything else . simple as that .
here's to help you - http://forum.xda-developers.com/galaxy-s2/general/cwm-kit-kat-compatible-t2546597