Related
Is it possible to pull out the kernel from JT's CM7 and then flash it?
I can't seem to find it in the CM7 rom package, and not even sure if it is possible. Somebody mentioned that it should be titled kernel_update, as that is usually the case, but I can't seem to find that.
I am on the OTB, and I would like to try out the original kernel.
One more thing, in case the kernel cannot be extracted, if I wipe cache and dalvik and then reinstall the rom with no data wipe will I be good? I've never installed a rom without data wipe and I just want to be sure that installing a rom twice on top of itself won't make it have some problems or bog down. If it will, I guess I can just bite the bullet and wipe everything and reinstall to get the kernel.
I reflashed the rom after a cache and dalvik wipe and everything is working great.
AlgorithmX said:
I reflashed the rom after a cache and dalvik wipe and everything is working great.
Click to expand...
Click to collapse
I'll give it a shot.
Couple people posted that they thought the included kernel had less hangs than OTB. Anybody have a similar experience?
They are both great kernels but I had to reflash the rom because my phone got stuck in headset mode after the latest voodoo control plus update. I think JT's currently has a few more gpio fixes.
I think your best bet would be to reflash the rom without wiping anything. You would get the original kernel while keeping your settings and data. If you were so technically inclined I believe the kernel is in the boot.img file in the zip but it is above me to try to make that its own flashable file.
When I first got my Optimus V it'd been, and still is, my first android phone. I jumped in ass first and followed a guide to put Clockwork Recovery and aospcmod on my phone. I've been reading up on Bumblebee and Xionia recovery and want to try that out.
The only problem that I am faced with is I don't know how to change recoveries, how to wipe, backup, and install a new rom & kernel. Any help, much appreciated.
FatalIll said:
When I first got my Optimus V it'd been, and still is, my first android phone. I jumped in ass first and followed a guide to put Clockwork Recovery and aospcmod on my phone. I've been reading up on Bumblebee and Xionia recovery and want to try that out.
The only problem that I am faced with is I don't know how to change recoveries, how to wipe, backup, and install a new rom & kernel. Any help, much appreciated.
Click to expand...
Click to collapse
afaik you can flash the new recovery in recovery
all the wiping is done in recovery. there should a an option to wipe data, dalvik cache, etc.
theres an option to make a nand backup in recovery too but remember that backups from one recovery are probably not compatible with another recovery.
your rom should have specific instructions on how to flash it, but this is the general scope:
download the file (on your phone, or on your computer and then transfer it to your phone)
place it in at the root of your sdcard (directory /sdcard)
boot into recovery and wipe data, dalvik cache, etc
flash rom (it comes with a kernel, you can flash your own kernel later)
done (first boot might take a while, dont worry)
of course as i said, this is kinda the general thing. check the instructions for your rom
Hey guys!!!
New galaxy S2 owner. I have done some searching in these forums and the threads answered many of my questions. However, I still have some newbie questions that I found unanswered. Please excuse me if my questions have been answered before but I got tired of searching
Here is the deal:
Yesterday, I flashed a CF Root with Odin3. Then used CWM to flash a wanamlite firmware. The firmware was great but I didn't like that it still had TW. So I dl'ed another firmware to the internal SD card and flashed again using CWM. I then flashed a couple of other ROMS and I noticed that after the first wanamlite flash, the new ROMs were unstable with many error messages that some OS processes have stopped etc.
I got back home, flashed to stock with Odin3 and the phone got stuck at the second samsung logo. I followed some community steps (thanks XDA) like disabling all kies processes from TM, wiping data/cache, then boot in DL mode and flash the stock ROM using Odin3 which worked.
I then Flashed a CF Root again and used CWM to flash a Spike Pure ICS ROM v5 which was great but I get occasional error messages like 'gallery stopped' or some other error message when I try to set contact photos. It just lags, blackscreen then comes back with the 'Unfortunately, the process had stopped'.
My questions: is this because of the previously flashed firmware that this is happening or is it that those ICS ROMs have these issues commonly? Did anyone have this experience before? What do you advice before flashing to a new ROM going back to stock or going straight from the current? Doesn't Odin3 technically wipe everything back to stock?
WIPE WIPE WIPE.
Go into recovery. Data/factory reset.
Advanced, Wipe dalvic cache. Mounts and storage, format system. Its a standard procedure going from one OS to another OS. You can then either flash a firmware zip from recovery or an .tar file from Odin.
Then to be on the safe side factory reset once again.
Sent from my GT-I9100 using Tapatalk 2
Wich fw do you have?
Make a deep clean with odin an flash on the latest ics version (lp9 is a good one)..then flash (if you want) a custom rom..
My experience with custom roms: one of the best rom samsung based (ics 4.0.3) is the foxhound greyfox v2..if you want a pure ics rom flash the omega aokp rom (ics 4.0.4)..
Try then to change kernel..siyah is the best for both roms..
P.s. sorry for my bad english
Sent from my GT-I9100 using Tapatalk 2
After LP7 should be staple enough for daily use .However you are using custom roms and you should read carefully each roms thread before flashing .
You are probably suffering from flashing multiple roms and leaving bits behind as well = clean wipe .
jje.
Can someone give me a clear full wipe procedure? I always wiped data/factory rest/wiuped chaceh and dalvik... but what else? a step by step procedure would be helpful!!
I currently have Spike Pure ICS v 5.
What do you mean by Odin3 'deep clean'?
OJ77 said:
Can someone give me a clear full wipe procedure? I always wiped data/factory rest/wiuped chaceh and dalvik... but what else? a step by step procedure would be helpful!!
Click to expand...
Click to collapse
Read my last post..
Sent from my GT-I9100 using Tapatalk 2
so:
1. Recovery mode > format user data > wipe cache > clear dalvik > format system (from moutns and storage)
2. Download mode > flash stock ROM using odin 3
Did I get it right? Was there something i didn't wipe?
Before you flash a new rom, make sure you answer the requirements.Some ICS roms need to be flashed in specific way.
The way of doing a full wipe is you go in Clockwork mode, wipe data/factory reset, you wipe cache partition, then go to advanced wipe Dalvik and Battery stats, then go in mounts and storage ( i think ) and you wipe the cache from there, but nothing else in mounts and storage.If you wipe anything else there's a high percent of bricking your phone.If this doesnt help you, I doubt that anyone could give you any clearer instructions.
Good luck.
DONT FORMAT SYSTEM.
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Followed by root and custom rom if you so wish .
jje
OK im confused now... do I format system directory in mounts and storage or no?
OJ77 said:
OK im confused now... do I format system directory in mounts and storage or no?
Click to expand...
Click to collapse
i always do personally.
I got tempted and formatted system/cache/data but now i cannot flash from my internal sd card.. I get errors and 'installation aborted' if i try to do it from CWM... does that mean formatting those 3 means Odin3 is the only way? Cus I'm not home and I don't have odin3 on me.... LOL!
OJ77 said:
I got tempted and formatted system/cache/data but now i cannot flash from my internal sd card..
Did you format sd card and totally wipe the lot = nothing on the phone .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
At this point you have no OS on the phone nor kernel rooted nor CWM .
Hence
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Click to expand...
Click to collapse
JJ, you really need to learn how to quote you know, makes your posts so confusing to read sometimes
skimminstones said:
JJ, you really need to learn how to quote you know, makes your posts so confusing to read sometimes
Click to expand...
Click to collapse
Agree must try better .
Habit from replying to emails i guess .
jje
Thanks...
I did a 'full wipe' by doing t his:
1. Boot into CWM: wipe data, wipe cache, wipe dalvik, wipe battery stats, wipe system/data/cache from mounts.
2. Reboot into DL mode, flash stock ROM using Odin3.
3. Repeat step 1
4. flashed spike ICS v 7.3 using CWM. Stable so far.
Thank you!
imho: the most stable ics release is the stock official, but with some.battery issues, my suggestion: stay on gingerbread, find a custom kernel to suits your need,
GT-I9100, official 2.3.6, hardcore's Speedmod
budi.hermawan said:
imho: the most stable ics release is the stock official, but with some.battery issues, my suggestion: stay on gingerbread, find a custom kernel to suits your need,
GT-I9100, official 2.3.6, hardcore's Speedmod
Click to expand...
Click to collapse
I agree! I don't like ICS because is still unstable! My battery lasts very short with ICS and the phone overheats.
Moreover I hate the browser! I mean, The Galax S2 with GB still has the smoother browser of all the smartphones out there, and Samsung with ICS update messed it up! Now is laggy with micro stutters! Don't understand why!
OJ77 said:
The firmware was great but I didn't like that it still had TW.
Click to expand...
Click to collapse
You didn't need to go through all that trouble just because you didn't want TW (which I also hate, btw).
You could simply have installed another launcher (such as Go Launcher EX, ADW, etc) from Play Store and, since you were already rooted, uninstalled TW using Titanium Backup afterwards. It has to be in that sequence (install new then uninstall old).
this way you can have whatever ROM + kernel combination you like, and still use whatever launcher you prefer.
Hi
I am new on the SGS2 though i have one Android Tablet.
I have been reading a lot and there is something i have not been able to find.
I want to root, , install CMW and install this custom ROM: Dynamic
http://forum.xda-developers.com/showthread.php?t=1582217
1.- Do i need to install first the CF-ROOT kernel matching my actual Firm to make the root or can i install the Siyah kernel at this will make the root anyway?
2.- If i install the CF-root using ODIN, do i need to install an specific kernel for that ROM? Or most kernels work with most rom?
Thanks.
I suggest you flashing the cf-root kernel with odin then you can install your custom rom from the modified recovery mode flashing the .zip file of the rom.
You can flash the siyah kernel after that, because generally custom roms mount a custom kernel which supports CWM (Clock Work Mod, the custom recovery).
If i helped u, press thanks.
if you are on ics you should be good flashing siyah but most of us here started with cf root
darkpollo said:
Hi
I am new on the SGS2 though i have one Android Tablet.
I have been reading a lot and there is something i have not been able to find.
I want to root, , install CMW and install this custom ROM: Dynamic
http://forum.xda-developers.com/showthread.php?t=1582217
1.- Do i need to install first the CF-ROOT kernel matching my actual Firm to make the root or can i install the Siyah kernel at this will make the root anyway?
2.- If i install the CF-root using ODIN, do i need to install an specific kernel for that ROM? Or most kernels work with most rom?
Thanks.
Click to expand...
Click to collapse
1/ follow the install notes stated for that rom also siyah kernel if flashed thru odin will give you root and install cwm/superuser
2/if you install cf root again follow install notes within that thread and it does say best to use same cf as your stock kernel or find one close to it to match
i prefer to use siyah less hassle but each to there own and everyone has there own choice
Thank you all.
I decided to go safe and try with CF-Root. Now i am rooted and i have installed the rom using the CWM.
Do you recommend to change the kernel again? I think that the rom has its own kernel but i am not sure.
Also something weird happen (little off topic), after wipe and reinstall the rom, i have some apps installed by default, some of them where on the old ROM.
I thought that all the apps will be deleted with the installation of the new rom.
Not sure how to fix it.
Thanks again
Apps will only be deleted by doing a full wipe in cwm. And you dont need to flash another kernel if you only want the root feature.. i think all the custom roms use a rooted kernel... some use cf-root, some siyah, some speedmod etc...
Well, i really prefer to use the features offered by other kernels. I was not sure if i can change the kernel keeping the Roms or if i need to reinstall everything afterwards.
How do i make a Full Wipe? most of the apps are bloatware and i do not want them.
Thanks
im also a noob and i use siyah without changing much
just OC to 1400 and choosing en demand for governor
darkpollo said:
Well, i really prefer to use the features offered by other kernels. I was not sure if i can change the kernel keeping the Roms or if i need to reinstall everything afterwards.
How do i make a Full Wipe? most of the apps are bloatware and i do not want them.
Thanks
Click to expand...
Click to collapse
You must go in the custom recovery and press "Data wipe/factory reset", so you wil have only the system apps, but you must start the phone configuration again.
U can flash another kernel if you want, there's no problem with the rom, but remember to do a dalvik wipe.
If youre thinking about to flash a new kernel, i would prefer to flash the kernel first (now) and then do a full wipe and dalvik wipe. Otherwise youre doing some work twice...
And if youre yet haveing some "bloatware" (e.g. from a provider branded firmware) after wipeing, you can delete them (be careful with system apps) with root explorer... (in "\system\app" folder....
darkpollo said:
Thank you all.
I decided to go safe and try with CF-Root. Now i am rooted and i have installed the rom using the CWM.
Do you recommend to change the kernel again? I think that the rom has its own kernel but i am not sure.
Also something weird happen (little off topic), after wipe and reinstall the rom, i have some apps installed by default, some of them where on the old ROM.
I thought that all the apps will be deleted with the installation of the new rom.
Not sure how to fix it.
Thanks again
Click to expand...
Click to collapse
If your happy with the results you get form using CF then by all means stay with it otherwise follow the thread in which your rom is based on users will often leave feedback on there selected kernels and setups like my signature for example check im sure theres users within your choosen thread with the same
I can advise using the kernel cleaning script after changing to another kernel. http://forum.xda-developers.com/showthread.php?t=1363738
This will prevent problems that left behind files from the old kernel can cause.
After flashing the file/script install the desired kernel
Thank you to everyone!
Ubbabubba said:
You must go in the custom recovery and press "Data wipe/factory reset", so you wil have only the system apps, but you must start the phone configuration again.
U can flash another kernel if you want, there's no problem with the rom, but remember to do a dalvik wipe.
Click to expand...
Click to collapse
I did the Data wipe/factory reset and everything as per the instructions:
*For a clean installation and no problem
- Download the ROM and put it on your S2.
- Go to Recovery
- Wipe data factory reset, wipe cache.
- In Advance: wipe dalvik cache and wipe battery stats.
- In mount and storage - format data , system and cache
- Install the zip file and you will get the CWM install completed message.
- Select Reboot Now and let the phone boot up to an Android setup screen.
- If there are Update, download it, put it on the phone, go to recovery and install it. Don't do wipes.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1582217
glowfinger said:
If youre thinking about to flash a new kernel, i would prefer to flash the kernel first (now) and then do a full wipe and dalvik wipe. Otherwise youre doing some work twice...
Click to expand...
Click to collapse
I think i am going to make it more than twice.
I will go to other kernel to try them. The battery on CF is not as good as i would like.
glowfinger said:
And if youre yet haveing some "bloatware" (e.g. from a provider branded firmware) after wipeing, you can delete them (be careful with system apps) with root explorer... (in "\system\app" folder....
Click to expand...
Click to collapse
That is the strange thing. I am not using any branded firmware, i came from one, but i thought everything was to be erased after the wipes and formats.
Spunkynitro said:
I can advise using the kernel cleaning script after changing to another kernel. http://forum.xda-developers.com/showthread.php?t=1363738
This will prevent problems that left behind files from the old kernel can cause.
After flashing the file/script install the desired kernel
Click to expand...
Click to collapse
I will use this on my next try this weekend.
If i do not understand wrong this is what i need to do:
Review the rom to find a kernel that suits it.
Use the kernel cleaning script
Install the new kernel.
Follow the instructions to flash the desired ROM with all the wipes and formats required.
Anything else?
Lately i'm experiencing problems with flashing custom roms (i.e. UltimaROM , Xperianze, whatever)
What i did is:
1: flash the latest CWM , touch and non -touch with Odin
2: download ROM of choice , copy to internal SD-card
3: reboot recovery, fact-reset, wipe cache + dalvik
4: flash rom ( with aroma installer )
5: boot phone
with booting it keeps hanging on the Samsung i9300 logo txt. It doesnt matter which rom i flash. it always keeps hanging.
I've tried alternative methods like flashing TWRP and do the same as above but again, no success. I also tried factory-reset after flash, cache wipe etc. no success.
The weirdest thing is: when i try to flash CM or MIUI ( current running MIUI ) , it works like a charm, but normal "custom" roms are not approved it seems.
does anyone have a suggestion for me what to do? or explain what i am doing wrong , or even better, can explain why CM-based ROMS work?
Have you checked the MD5 of your downloaded ROMs when they are on your SD card? Format system, data and pre-load before flashing? Tried flashing an alternative kernel/radio before you boot the first time?
If only stock based ROMs are a problem then it maybe something that is unique to them, probably a direct hardware hit via the kernel.
Try returning completely to stock to test, flashing Samsung's vanilla EMB5 via Odin - including stock recovery and full wipe. If that doesn't work then you may have a hardware issue that CM or MIUI doesn't use.
yeah good idea to return to stock and try all over again.
to your other questions: no i didnt flash another kernel after i flashed the custom rom. i've tried with several kernels which options were given to me in aroma installer ( boeffla, syah, stock )
md5: did that
format system and data: nope. kinda relied on the fact-reset + cache/dalvik
what do u mean with pre-load?
if I were you I would format data & system again manually after the fac. reset thing, or even more clean use the mega wipe flashable zip to have a clean slate to start from (it will format anything but the ext. sd-card). Then flash the rom from your ext. sd-card and see how it goes.
additional possibly helpful hints
hi there,
i'm not entirely sure if this will help you but generally speaking i came made a few observations about the fact that some people, mostly repeatingly the same users, encounter problems with their custom roms and/or flashing them, while others don't, albeit they are using the same devices.
i my selfe use 3 different devices, all rooted and running on pac 4.3, always lates nightly, as there are GT-N7100 - GT-I9100 - Nexus 4
not to the point
a) other than most other users i usually clean cache and dalvik cache as well before and after flashing the new rom and/or new nightly
and never encountrer any problems except those which everybody, using the same rom and nightly encounters.
b) whenever i flash an totally different rom and/or upgrade and/or downgrade to another level of android os, i.e. from 4.2.2 to 4.3, i perform
a clean install, including not only a factory reset, but as well a format sd-card, format cache and format system etc., again i cannot proof
which of these steps make a or the differnce but however, i never have problems others than thosw which everyone has with a version.
c) when using cusome kernels and due to the fact that some roms come with a kernel included, as well as with a custom recovery included,
it is strongly recommended not to forget to flas the kernel again after each flashing the new rom. one good example ist dorimanx kernel
for GT-I9100 which will not boot into recovery and reluctantly boot at all after a new flash of a pac nightly without reflashing the kernel.
d) try to fix permissions on reboot instead of doing it from recovery. one reason is that not every recovery has this option and further i
found that when fixing permissions before the first boot after flashing a new rom, there might be bootloops, albeit i cannot explain exactly
why that should, but however, sometimes it's better to be on the safe sid.
e) try to run whether the lastes version of custom recovery for your device, and or the use the included custom recovery of the rom or the
kernel. this again is one thing that can help to avoid some unexpected and hard to explain bootproblems and/or fc's etc.
hope that i could give you some new ideas how to avoid trouble while using custom roms and other hacks
magnamentis said:
try to fix permissions on reboot instead of doing it from recovery. one reason is that not every recovery has this option and further i
found that when fixing permissions before the first boot after flashing a new rom, there might be bootloops, albeit i cannot explain exactly
Click to expand...
Click to collapse
Fix permissions was removed because its useless. All permissions are set when flashing by way of updater-script. Fix permissions via recovery "guesses" the permissions which causes issues...
If permissions need fixing, then the updater-script is poor which means you should probably avoid flashing it.
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Fix permissions was removed because its useless. All permissions are set when flashing by way of updater-script. Fix permissions via recovery "guesses" the permissions which causes issues...
If permissions need fixing, then the updater-script is poor which means you should probably avoid flashing it.
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
thanks for the explanation which makes totally sense, so my feeling which i could not explain was right always better to learn exactly why than just guessing
no thanks button found in your post however, so i want to thank you this way.
regards