Hi guys, I have a xt1032 with CM11 Snapshot.
I have the stock kernel and wanted to try FAUX kernel because it seems to be awesome!
But I have some doubts..
How can I backup the stock kernel and restore it if the FAUX kernel fails, without losing everything on the phone?
And to install it I have to download, put into the phone and flash using recovery? Or do I have to do some wipes?
So in case of brick I'm covered.
By the way... what kind of wipes can I do with TWRP that don't delete me any of my stuff (photos, apk's, ...)? Because I know that there are some system wipes that delete everything...
I hope you can help me with these questions!!
Thank you!!
1. Dont backup just the kernel, backup the whole Rom
2. Faux kernel doesnt work in CM. Maybe try Pink kernel instead or furnace or Render Kernel
3. To install a kernel you need to wipe cache and dalvik cache.
4. By wiping cache and dalvik cache you dont lose your data.
5. Always remember that you are responsible for any damage on your phone and noone else
6. If you get a bootloop then restore your backup
7 If your phone doesnt turn on at all and you dont even get into bootloader then i think you are game over
8. As you use CM i think you have already known some of the things .
9. Happy flashing
Thanks for your quick reply!
Last question ( for The moment ), doing a backup with twrp do I get a full ROM and kernel backup?
Solved!
I have installed the Pink Kernel and it works awesome! Just backed up the whole ROM and flashed it without any fear.
Thank you very much for the answers.
Bye!
Related
Hello,
I flashed CWM and did a full system backup/system wipe/cache wipe then installed xboarders 1.2.2 rom for the first time. I'm rooted! woohoo! I want to install eaglesblood new rom now. My question is when installing a new rom is it recommended to do a full backup or is one time enough? Thank you for any help as I am a newbie at this.
I always keep at least one or 2 backups of setups that I know work. That way if I screw something up while tinkering with my phone I always have a working backup to fall back on.
So yes, its recommended to keep a good backup on hand. You don't necessarily need to backup every time though. I just make sure I backup my texts before I flash anything. I hate losing those.
What you DO NEED to do EVERY TIME you flash between completely different roms is do a full wipe before you flash the new rom. If you're only updating to a new version of the same rom then a full wipe isn't necessary.
G2X CM7
Thanks for your help! Also, when doing a full wipe do I need to do a dalvik wipe as well in the advanced settings in CWM?
Sarchie1982 said:
Thanks for your help! Also, when doing a full wipe do I need to do a dalvik wipe as well in the advanced settings in CWM?
Click to expand...
Click to collapse
I always do. It certainly wont hurt anything if you do. Just remember the first boot after clearing dalvik cache usually takes a little longer than normal because the phone has to rebuild the dalvik cache. Don't panic if it takes a few minutes even to boot. After the first time it wont take as long.
G2X CM7
This is a flashable zip that simply returns your kernel and wireless.ko to stock GB 2.3.3 as delivered by LG in the update. This is for people who have played around with custom kernels and wish to go back to stock for whatever reason. Caveat: I have not tried the zip myself but one user has reported he has used it with success. This is a simple flash that simply replaces the boot.img and wireless.ko with the files from stock, so you should have no problems with it.
Disclaimer: I am not responsible if you brick your phone, void your warranty, or any other pain or suffering you may experience as the result of flashing this kernel.
Note: Always wipe the Dalvik Cache when flashing a new kernel. If you don't unintended consequences (i.e., boot stuck on LG logo or boot loop) may result. The first boot after flashing will take around five minutes or so. Please be patient and don't report your phone is bricked while it is still booting and rebuilding the Dalvik Cache, which takes several minutes depending on how many apps are installed.
Please report back any success or failures here.
Enjoy!
Attachments:
P999-GB-Kernel-Stock.zip (4.26 MB)
MD5: 52b1f38ff846082aed99bf8ac7fdb756
Reserved for future use by the OP.
This has been needed for a while. Thanks!
Thanks
Sent from my LG-P999 using xda premium
I was wondering if there was away to revert back. Thanks alot. Hey i got a question I am still a noob and I just stsarted changing kernels but Have been flashing for a while. I asked whast needs to be done before I flash and was told to wipe cache but nothing else is needed. I am haveing a problem with the new EB 2.1 and trinity kernels. When I do a hard boot to fix data it reboots twice the second one being a normal boot so I still dont have data. Should I try to wipoe dalvik and cache would that fix it if no do you have any suggestions?
Charlie
mojorisin7178 said:
I was wondering if there was away to revert back. Thanks alot. Hey i got a question I am still a noob and I just stsarted changing kernels but Have been flashing for a while. I asked whast needs to be done before I flash and was told to wipe cache but nothing else is needed. I am haveing a problem with the new EB 2.1 and trinity kernels. When I do a hard boot to fix data it reboots twice the second one being a normal boot so I still dont have data. Should I try to wipoe dalvik and cache would that fix it if no do you have any suggestions?
Charlie
Click to expand...
Click to collapse
This thread is for the stock kernel. Please post your question in the EB 2.1 and Trinity Kernel threads.
This is useful thanks, wish we had one for cm7.....
ONLY the D. Cache should be cleared right?
SyntekSystems said:
ONLY the D. Cache should be cleared right?
Click to expand...
Click to collapse
Yes. The Dalvik Cache is the crucial thing you need to clear when you flash any system file, kernel, etc. If you don't a bootloop or stuck boot is a likely result. If you flash a different rom then you should wipe the system also to be safe.
reason is because I've been clearing the Cache partition as well, I'm not sure if I was suppose to do that, lol.
SyntekSystems said:
reason is because I've been clearing the Cache partition as well, I'm not sure if I was suppose to do that, lol.
Click to expand...
Click to collapse
No reason to clear normal cache. In fact, if you use Rom Manager, that will delete the recovery it flashed as that is where it keeps it.
Hi all,
I've recently tried to update the Matr1x kernel to the 9.0 CFS version on my already installed NSCollab 1.0.50 mod. Unfortunately, this didn't seem to go so well, because my Nexus S (i9023) entered an infinite reboot loop. I was a bit surprised since a lot of people seemed to have no problems with this kernel, and even though I'm new to this stuff, I tried to follow all the guides & tutorials around.
Anyways, here's what I did:
- I downloaded the kernel on my phone from this forum;
- I used ROM Manager, selecting the "Install ROM from SD Card" option;
- I let the "Wipe Dalvik Cache" option enabled.
Once I experienced the reboots, I dropped into recovery and tried to re-wipe the cache & the dalvik cache several times, with no luck. I then proceeded to restore the backup I made before doing this...
Did I do something wrong or stupid?
try flashing the rom(gapps if needed) then the kernel, then reboot.
simms22 said:
try flashing the rom(gapps if needed) then the kernel, then reboot.
Click to expand...
Click to collapse
Does this mean I have to wipe my data again?
I've never used ROM Manager to flash anything (I prefer to be hands-on and do it myself), but if you told ROM Manager to install a ROM from zip and fed it a kernel file, I can't see how that can possibly have a positive outcome hahaha.
Go into CWM, do a factory reset/full wipe and reinstall NSCollab 1.0.50. Once you've installed that, you can immediately install a custom kernel. Reboot, wait for it (the first boot always takes longer) and you should be fine.
Greetz
PS: Remember to always make backups with Titanium Backup, or even Nandroid backups if you're not sure about the actions you're about to do.
mux_ said:
Does this mean I have to wipe my data again?
Click to expand...
Click to collapse
no. go to recovery(dont use rom manager), flash your rom(and gapps), flash the kernel, reboot.
Well, since my system was still fully functional (as I said, I had done a backup from ROM Manager previously and restored it), I tried the manual method first; that is dropping into recovery, wiping dalvik cache, and using 'install zip from sdcard'.
Everything went just fine, and I'm running the Matr1x 9.0 CFS kernel without any issue for now!
Thanks a lot for the help.
Sorry if this has been covered way too many times but I want to make sure.
I have rooted my phone that was running 3.20.502.52 with the AAHK so now I'm on the version it sent me back to and I have done nothing since. I am getting ready to switch to the Jellytime R29 ROM. I know to make a Nandroid backup but I was a little concerned about getting back to the state my phone is right now should anything go wrong or if I don't like it, go back. It seems that I can't just restore my Nandroid through CWM without flashing a different kernel since I'd be coming from a JB ROM.
My current setup is:
Android: 2.3.3
Sense: 2.1
Kernel: 2.6.35.10-gd2564fb
Software 2.47.502.7
So, in order use my Nandroid in case the Jellytime messes up, do I simply have to do a factory reset, and wipe cache, and dalvik-cache (this is considered a "full" wipe, yes?) and then flash a compatible kernel then restore my backup? And if so, can I find that exact kernel somewhere to flash or is there another one you guys can recommend me to use in my situation? OR, can I just straight up restore the Nandroid since the backup should cover the kernel too?
Sorry I'm a newb. I'm trying to learn. All help is greatly appreciated. I'm hoping to flash Jellytime as soon as I know how to recover from it.
1. Welcome!
2. The kernel is included in the backup. You also don't need to wipe anything; just restore the nandroid. Make sure you use a fully updated recovery; make sure using ROM Manager for CWM or the 4ext Updater or Play Store app for 4ext.
3. A full wipe is system, data, and cache. Dalvik is already included if you wipe those. A factory reset only wipes data and cache, leaving system unwiped. In 4ext just choose "wipe all partitions except sdcard."
Alright. I already flashed Jellytime a while ago and so far I see no reason for wanting to go back although I did a quadrant standards test and scored lower than stock. Not sure why, but either way, this was a nice first ROM. What I wiped in cwm was the reset, cache, and dalvic. So far everything is working if I missed anything.
Didn't know wiping wasn't necessary for using backups. Must of missed that in my reading. Thanks though. I'll become less of a newb over time.
Hey Guys, Monday evening, i guess, i'm gonna receive my Nexus 5 32GB White... Well my question is:
After unlocking and rooting, I want to install Catclysm Rom + Franco.Kernel If i delete the Boot.img file inside the zip of cataclysm rom and replace it with the franco's img will it work?? will i have Cataclysm and franco.kernel at the first boot?? So i don't have to reboot again to flash the kernel
Thank you guys for your help
p.s.: In future when cataclysm will get another update, do i have to wipe evrything or just cache and dalvik?? (Before flashing i'll delete the boot.img file inside the zip so i won't loose the kernel)
p.p.s.:Maybe i'm crazy but i need to know these little things xD
Hi,
Yes you can replace the boot.img inside the zip before flashing the rom..., but is it too hard to flash it separately?
With a rom update you can make a dirty flash (only cache partition+Dalvik cache) but if there is a new base it is recommended to do a full wipe to avoid some weird behaviors, bugs, etc... In any case if you do a dirty flash and you have some issues, you'll be good to do a full wipe.
Sometimes the dev recommend to do a full wipe...
For me it's always a full wipe, always begin with a fresh intallation so I'm pretty sure that all will be fine. It makes time to setup again the rom but...
viking37 said:
Hi,
Yes you can replace the boot.img inside the zip before flashing the rom..., but is it too hard to flash it separately?
With a rom update you can make a dirty flash (only cache partition+Dalvik cache) but if there is a new base it is recommended to do a full wipe to avoid some weird behaviors, bugs, etc... In any case if you do a dirty flash and you have some issues, you'll be good to do a full wipe.
Sometimes the dev recommend to do a full wipe...
For me it's always a full wipe, always begin with a fresh intallation so I'm pretty sure that all will be fine. It makes time to setup again the rom but...
Click to expand...
Click to collapse
Really thank you man, you solved all my questions I know it's not hard to flash the kernel separately but i'm lazy xD
Oh just another question if i want to upgrade my kernel, do i have to do a full wipe??
Enri1196 said:
Oh just another question if i want to upgrade my kernel, do i have to do a full wipe??
Click to expand...
Click to collapse
Re,
Nope... no wipe needed (not even Dalvik/cache partition), just flash and enjoy.
viking37 said:
Re,
Nope... no wipe needed (not even Dalvik/cache partition), just flash and enjoy.
Click to expand...
Click to collapse
Again thank you, i also pressed the thanks:good: button for all your other answers