flash back to stock before flashing new rom - Captivate General

Does it really matter to flash back to stock before i install a new rom. I know that it is recommened but is there really any drawback of just flashing over the current rom?

If you just updating the Custom Rom with a newer version of it don't think there huge deal not going to Stock 1st still might need to Wipe Data and Cache. But if you going to totally new Custom Rom I think I would go to Stock 1st.

rg400smarttowel said:
Does it really matter to flash back to stock before i install a new rom. I know that it is recommened but is there really any drawback of just flashing over the current rom?
Click to expand...
Click to collapse
You know, if the ROM author recommends you flash back to stock then you should probably follow that recommendation...

In my experience, it's just better to flash to stock. The ROM creator might say it's fine to flash over a previous ROM, but it seems like most of the problems people have are caused by flashing over an existing custom ROM and are fixed by flashing back to stock then flashing the new ROM.
Just my 2 cents!

pmd5700 said:
In my experience, it's just better to flash to stock. The ROM creator might say it's fine to flash over a previous ROM, but it seems like most of the problems people have are caused by flashing over an existing custom ROM and are fixed by flashing back to stock then flashing the new ROM.
Just my 2 cents!
Click to expand...
Click to collapse
Yup. It seems very hit or miss when just flashing over a rom so I always flash stock first. Look in any rom thread and you'll see countless posts of people flashing over their existing roms and experiencing force closes and other issues. I even flash stock when upgrading an existing rom. This may be overkill, but I've never had issues doing it this way.

I always do, even if it is just an update to the same ROM. The main reason is that if I end up really liking this new ROM or update, I want to make sure that it is as clean an install as I can do, so I don't have to re-do it later just work clean up a mess.

Related

[Q] JB update and custom kernel

Hi all,
I'm sorry about my stupid question but I really don't know nothing about that . I had rooted and flashed my NS and installed the matr1x kernel (very good btw), and now I knew that JB will be available to NS. My question is, need I back to stock kernel to receive the update?
Thanks
Sent from my Nexus S using xda app-developers app
Gnng
You have to understand that installing an OTA (official update) on a rooted device regardless of what kernel can cause problems, as it did with my Nexus S before. I suggest you make a NANDroid backup at all times before you install any ROMs, official or Custom. You can also use Titanium backup and others.
There's still a slight while until the new JB 4.1 comes out. It's suggested that you install a Custom JB 4.1 ROM for your Nexus S as though you don't cause any problems. I think it's OK if you do it with the kernel pre-installed. But people always install the Custom ROM THEN they install the Kernel, I think installing a new ROM always overwrites the kernel, if it comes with it.
EDIT:
In short, wait for the JB Custom ROM and you don't have to revert back to stock kernel, when you do the update it will automatically overwrite. Most Custom ROMs come with Stock/ordinary kernels. So then the user can flash whatever kernel they like in your case, matr1x.
Wish you the best of luck, and I am waiting for the Nexus S JB to come out as soon as possible
Ota binary patches the boot image iirc. So it can get all messed up.
Sent from my Samsung Epic 4G using Tapatalk 2
Yeah, what he said!
MДЯCЦSДИT said:
Ota binary patches the boot image iirc. So it can get all messed up.
Click to expand...
Click to collapse
andezzat,
Thank you very much for the help.
andezzat said:
Gnng
You have to understand that installing an OTA (official update) on a rooted device regardless of what kernel can cause problems, as it did with my Nexus S before. I suggest you make a NANDroid backup at all times before you install any ROMs, official or Custom. You can also use Titanium backup and others.
Click to expand...
Click to collapse
I didn't any backup before flashing a new kernel :crying:, so what can I do now if I want my stock kernel back?? What's a NANDroid (I know that is a tool but how can I do it?) ? Is Titanium bkp easily?
There's still a slight while until the new JB 4.1 comes out. It's suggested that you install a Custom JB 4.1 ROM for your Nexus S as though you don't cause any problems. I think it's OK if you do it with the kernel pre-installed. But people always install the Custom ROM THEN they install the Kernel, I think installing a new ROM always overwrites the kernel, if it comes with it.
Click to expand...
Click to collapse
I prefer wait for stock JB Rom and probaby I'll , but, can I already find some JB ROM?
In short, wait for the JB Custom ROM and you don't have to revert back to stock kernel, when you do the update it will automatically overwrite. Most Custom ROMs come with Stock/ordinary kernels. So then the user can flash whatever kernel they like in your case, matr1x.
Click to expand...
Click to collapse
I don't need to remove the kernel even unroot my cell, alright?
Thank you!!
Gnng said:
I didn't any backup before flashing a new kernel :crying:, so what can I do now if I want my stock kernel back?? What's a NANDroid (I know that is a tool but how can I do it?) ? Is Titanium bkp easily?
Click to expand...
Click to collapse
A NANDroid backup is a internal memory backup. You can create one by booting into Recovery (Power off your phone and Hold Power and Down on your volume buttons.) If you rooted your phone and unlocked your bootloader (that's what you had to do to flash a new kernel), you should be able to load ClockworkMod or TeamWin Recovery and do a backup of your phone.
Gnng said:
I prefer wait for stock JB Rom and probaby I'll , but, can I already find some JB ROM?
Click to expand...
Click to collapse
There's one rom but it's a port from the SDK and the amount of major bugs is high so it's not recommended but you could try another custom rom meanwhile, I can't go back to stock after trying custom roms, like AOKP and Cyanogenmod 9. Make sure you backup your apps and some settings (not everything will be compatible between stock and custom so pay close attention to which system setting you'll backup) with Titanium Backup.
To sum it all up for you
There's a Jelly Bean release which is unstable and has no sound, and will not be fixed until the REAL version comes out.
NANDroid backs up the whole internal memory on the phone including the system, it can be done from clockworkmod recovery.
Titanium backup, backs up specific settings and information that you choose, available from the playstore.
You don't need to unroot or go back to a STOCK kernel in order to flash a CUSTOM ROM. DO not however flash a STOCK rom after rooting, as at times that can cause problems.
If you want to go back to a STOCK ROM after rooting a device, there's a way, check this guide
http://forum.xda-developers.com/showthread.php?t=1063664
and choose your Nexus S model: To acquire model, go to Settings - About - Baseband version. if it says I9023 at the start that's your Nexus S's model
Choose one of the Fastboot Stock ROMs and use the Fastboot method to flash the ROM. That is a good way to go back to STOCK ROM if anything bad happens
By the way you should expect the new OTA official 4.1 update for the Nexus S to be on your model's page.
NOTE: Using Fastboot to flash a ROM is very clean. However this will delete all your data and if you do everything correctly will lock your bootloader and unroot your phone. So use Fastboot only when you really feel the need to.
Cheers
and stay tuned for Jelly Bean :victory:
andezzat said:
To sum it all up for you
You don't need to unroot or go back to a STOCK kernel in order to flash a CUSTOM ROM. DO not however flash a STOCK rom after rooting, as at times that can cause problems.
Click to expand...
Click to collapse
That means, when I receive the official 4.1 update notification, I should unroot my phone first and just install it after?
Gnng said:
That means, when I receive the official 4.1 update notification, I should unroot my phone first and just install it after?
Click to expand...
Click to collapse
OK first off, do not install the update using the system update method from about, as that is a 100% stuff up if you're still rooted or on a Custom ROM.
However to update I think flashing a stock ROM but USING Clockworkmod works fine!
Someone please confirm, as I am not 100% sure
However what I am sure about is that if you run into any troubles installing your STOCK ROM using Fastboot is very very good and clean, however there are 2 things:
1. You will wipe everything COMPLETELY
2. You need the ROM to be in a fastboot format kind of way for you to flash it
There's a guide and everything for fastboot.
---------- Post added at 12:35 AM ---------- Previous post was at 12:33 AM ----------
Personally I will wait for a custom ROM for 4.1 if it doesn't take too long as that's guaranteed and will obviously be faster and safer to install on a ROOTED device.
Someone still confirm if installing Stock ROM while over Custom ROM while ROOTED through CWM is OK or not!?
Hummm, ok...
I'm already using the Stock ROM, I just flashed a new kernel, and I prefer install the stock kernel and unroot my phone. Just to let it clean.
After I install the JB official update, maybe I flash and root again, depends of Google :laugh:
Do you know where can I download a trust official 4.0.4 kernel from the forums? My phone is a Nexus S I9020AUCKJ1, Version Number: IMM76D
Thanks!!!

SGS4G Android 2.2 rec 3e. Do I have to flash kernel and modem before flashing custom?

Phone is rooted, CWM installed latest, recovery e3 does not check signatures.
Can I just create nandroid backup, wipe phone and install this one rom for example?
AjvarXX said:
Phone is rooted, CWM installed latest, recovery e3 does not check signatures.
Can I just create nandroid backup, wipe phone and install this one rom for example?
Click to expand...
Click to collapse
Yep.. You take a backup, wipe cache,data and dalvik cache. You are ready to flash your custom rom.. But while changing kernels you gotta flash your stock rom+stock kernel then root then flash new kernel then the custom rom.
haridevil99 said:
Yep.. You take a backup, wipe cache,data and dalvik cache. You are ready to flash your custom rom.. But while changing kernels you gotta flash your stock rom+stock kernel then root then flash new kernel then the custom rom.
Click to expand...
Click to collapse
Appreciate. So I now will backup and wipe everything and then update it with kies mini. And then will ask more about custom stuff, am I doing right?
The problem about SGS4G is that it is WAY TOO MUCH information about it as well as kernels, mods, articles and you are lost because some of them conflicts with other.
P.S. I spent a week for going into Android stuff and Galaxy S.
AjvarXX said:
Appreciate. So I now will backup and wipe everything and then update it with kies mini. And then will ask more about custom stuff, am I doing right?
The problem about SGS4G is that it is WAY TOO MUCH information about it as well as kernels, mods, articles and you are lost because some of them conflicts with other.
P.S. I spent a week for going into Android stuff and Galaxy S.
Click to expand...
Click to collapse
Well.. If you were talking bout updating your stock rom using kies... I dont see any use of that if you are going to flash a custom rom. Its just mere waste of time.
haridevil99 said:
Well.. If you were talking bout updating your stock rom using kies... I dont see any use of that if you are going to flash a custom rom. Its just mere waste of time.
Click to expand...
Click to collapse
it's because 2.2 version is so hard for modding that I didn't risk to update from it.
Now I have modded kernel on stock 2.3.6. And thinking about what ROM to use.
Here is a link I found recently and it is so very helpful! http://forum.xda-developers.com/showthread.php?t=1470716
AjvarXX said:
it's because 2.2 version is so hard for modding that I didn't risk to update from it.
Now I have modded kernel on stock 2.3.6. And thinking about what ROM to use.
Here is a link I found recently and it is so very helpful! http://forum.xda-developers.com/showthread.php?t=1470716
Click to expand...
Click to collapse
The guide seems good enough but a bit more complicated that it should be. Anyway here are two tips or info for you. First, whatever you do, have Odin and Stock Firmware ready to flash coz when everything else fails, Odin to the rescue and also flash stock firmware (Rom+kernel) whenever you change kernel as changing kernels without doing so removes root access and you cant apply root update on a custom kernel unless it has pre root access. Second, you dont need any kind of manager to flash firmwares and updates. CWM is a replacement to all. But its all your choice.

need some guidance

Random Shut Down on stock 2.3.6
hey everyone, i wanted to ask, i've been using the stock 2.3.6, it randomnly just shuts down for no apparent reason... anyone know what's what? i've rooted with cwm and all... just hoping maybe a much better, stable and reliable 2.3.6 would suffice?
Trying clean wipe(data,cache,dalvik) and flash stock again.
Make sure you have backed up your present ROM via cwm.
If problem persist try using a custom ROM ,since you have already rooted (custom ROMs have a lot more added functionality and better battery life)
Soul reaper said:
Trying clean wipe(data,cache,dalvik) and flash stock again.
Make sure you have backed up your present ROM via cwm.
If problem persist try using a custom ROM ,since you have already rooted (custom ROMs have a lot more added functionality and better battery life)
Click to expand...
Click to collapse
will do, thanks for replying mate

[q] Upgrading from Custom 4.4.4 Rom to Custom 5.0 Rom

Hello folks, how are you? I'm sorry if this is a duplicate post, but I've been searching for a clear answer to this and haven't found one.
I'm currently on a Nexus 5 running a custom 4.4.4 rom based on Purity. While I've no problems with this rom, I'm kinda itching to try 5.0. However, I'm not entirely clear on the upgrade path. I've read that to go to 5, I'd have to revert to stock, upgrade to 5.0 stock, THEN install a custom rom after that, but that sounds like quite a few steps.
Now if that's what I have to do, that's fine, but I'm curious if I can simply flash a new 5.0 rom after doing a wipe like I would with any other rom, or do I have do do anything different like flashing radios or revert to stock or anything along those lines.
Therefore, if some could just simply lay out what I best course of action is, that would be wonderful. Thank you for your time.
Hopefully I've covered all your options
http://forum.xda-developers.com/showthread.php?t=2947144
It doesn't cover wipes but do take the usual titanium backup and be prepared to.wipe.
Ahhh, so it looks like:
Method 5 (You are rooted 4.4.x with custom recovery)
1. Flash from recovery, an existing packages ROM.zip
2. Flash from recovery, a flashable custom boot.img (@Chainfire for basic root, @sykopompos for full permissive mode)
3. Flash from recovery, SuperSU (Please note BETA 2.27+ May mean you do not need a modified boot.img)
You can get the boot.img's and SuperSU from here: [ROM] N5 Lollipop + Stock IMG Mirrors & More! (by @vomer)
You can get a ROM.zip from here: [ROM] [STOCK] Android 5.0 LRX21O - Stock/Flashable (11/12/14) )by @bigxie
Click to expand...
Click to collapse
Is probably the best way for me to go! Awesome, thank you!!!
Just to ease your mind a bit, I was just like you.
I too have came from Purity 4.4.4 , I upgraded to cataclysm because I too was itching for the new Lollipop update.
The way I approached this flash is like I've always had, I moved the zip into the storage and using the latest TWRP recovery I just flashed the rom and everything worked buttery smooth.
Hope things go well for you.
MrFishiz said:
Just to ease your mind a bit, I was just like you.
I too have came from Purity 4.4.4 , I upgraded to cataclysm because I too was itching for the new Lollipop update.
The way I approached this flash is like I've always had, I moved the zip into the storage and using the latest TWRP recovery I just flashed the rom and everything worked buttery smooth.
Hope things go well for you.
Click to expand...
Click to collapse
Ohhh, do you mean this Cataclysm?
http://forum.xda-developers.com/google-nexus-5/orig-development/rom-cataclysm-nexus-5-t2518660
Yea that's the one, it's a very nice ROM, very customizable and very stable.
MrFishiz said:
Yea that's the one, it's a very nice ROM, very customizable and very stable.
Click to expand...
Click to collapse
Sweet, and you didn't have to fudge with radios or anything of the sort?
Brian Rubin said:
Sweet, and you didn't have to fudge with radios or anything of the sort?
Click to expand...
Click to collapse
Well, the author explains that he included gapps and root into the build itself, but he also said that the rom does not update the radio. I didn't get any signal problems if that's what you mean but when you think about it I don't think that any rom includes a radio in it aha that's always a separate update.
If you do want to update your radio to the latest version, visit this link:
http://forum.xda-developers.com/google-nexus-5/general/rom-n5-l-developer-preview-t2796003
MrFishiz said:
Yea that's the one, it's a very nice ROM, very customizable and very stable.
Click to expand...
Click to collapse
Right on all counts. I did what'cha said, wiped (a few times, to be sure), flashed, and waited during the long reboot. Now it's working swimmingly, and I LOVE IT. Very fast, very stable, now I just gotta get used to some of Lollipop's idiosyncrasies. Thanks folks!

Need a few qiuck tips. Regarding rooting and flashing

I am about to flash my nexus 5 device.
I was wondering.. if i unlock the bootloader and install a custom recovery plus create a backup.. that means ill have basicly a backup on my phone of a factory ROM and kernel right ?
So If i play around with custom roms and Kernels does that mean if I want to go back to stock kernel or/and ROM I can just recover my backup files from ,for example, CWM ?
And also if anyone here knows... how big difference can a kernel for battery life extension make ?
Then..
If I want to flash both.. Custom ROM and Kernel.. Rom comes first ? And if after that .. lets say I have flashed Cyanogenmod , and I have decided to change ROMs , Do I have to flash factory ROM ? Or I can just factory reset and Flash ir over the Cyanogenmod ?
For example.. for elementalX kernel I read this line... "You should only flash ElementalX over the kernel that came with your ROM!!!" I assume that means I do flash the ROM first... and what if I want to change Kernels later on? I re-flash the factory kernel ? And how do I do that?
For now that would be it
Thanks
Yes, installing a custom recovery (I recommend TWRP) allows you to create a backup of the existing ROM for restoration at a later point in time if you don't like the phone's existing ROM. Restoring TWRP backups have always worked except for me except in a couple of situations where I could not boot the restored ROM without first doing a factory wipe of the data and cache partitions.
I can't comment on custom kernels except to say that everyone uses their phone in different ways and getting the best battery life and performance may require a lot of tweaking. You could just try different kernels to see which one suits your needs.
You can restore the ROM's original kernel by extracting the kernel from the original ROM and flashing it. Alternatively, you could dirty flash the over the existing ROM. For example, if you are running CM12.1 2015-12-30 with a custom kernel and you want to go back to CM12.1 2015-12-30 without the custom kernel, you could just re-flash the entire CM12.1 2015-12-30 ROM again.
audit13 said:
Yes, installing a custom recovery (I recommend TWRP) allows you to create a backup of the existing ROM for restoration at a later point in time if you don't like the phone's existing ROM. Restoring TWRP backups have always worked except for me except in a couple of situations where I could not boot the restored ROM without first doing a factory wipe of the data and cache partitions.
I can't comment on custom kernels except to say that everyone uses their phone in different ways and getting the best battery life and performance may require a lot of tweaking. You could just try different kernels to see which one suits your needs.
You can restore the ROM's original kernel by extracting the kernel from the original ROM and flashing it. Alternatively, you could dirty flash the over the existing ROM. For example, if you are running CM12.1 2015-12-30 with a custom kernel and you want to go back to CM12.1 2015-12-30 without the custom kernel, you could just re-flash the entire CM12.1 2015-12-30 ROM again.
Click to expand...
Click to collapse
Thanks!
What advantages does TWRP has over CWM ? And also does it recover other files as well or just the system ones ?
And I guess its safer to just extract the original ROMs kernel.. Just how do i do that ?
TWRP is well supported and features a simple touch interface. TWRP will recover the system and data files.
Not necessarily safer to flash just the kernel rather than the entire ROM. It also saves time and effort because, if the kernel is not extracted and compiled for flashing in recovery, it could cause the phone to bootloop.
I've never extracted the kernel myself but this may help: https://www.youtube.com/watch?v=rLhprnOF6-U
audit13 said:
TWRP is well supported and features a simple touch interface. TWRP will recover the system and data files.
Not necessarily safer to flash just the kernel rather than the entire ROM. It also saves time and effort because, if the kernel is not extracted and compiled for flashing in recovery, it could cause the phone to bootloop.
I've never extracted the kernel myself but this may help:
Click to expand...
Click to collapse
Thanks!
So.. If, lets say, I flash cyanogenmod. Then Flash custom kernel. In order to change other kernel which is also custom , I should first flash the factory ROM which will have kernel on it ? And then reflash the ROM and then flash the new kernel ?
Im sorry , I also read a lot about this and somewhere on the way got really confused , haha.
Let's assume you flash CM version 1 and then you flash custom kernel "Kernel A". If you want to try another custom kernel named "Kernel B", you could just flash "Kernel B" over "Kernel A". If the developer of "Kernel B" cays it must be flashed over CM's original kernal, you could still flash "Kernel B" over "Kernel A" and hope it works. If it doesn't work, you could dirty flash CM version 1 over the existing ROM, then flash "Kernel B".
audit13 said:
Let's assume you flash CM version 1 and then you flash custom kernel "Kernel A". If you want to try another custom kernel named "Kernel B", you could just flash "Kernel B" over "Kernel A". If the developer of "Kernel B" cays it must be flashed over CM's original kernal, you could still flash "Kernel B" over "Kernel A" and hope it works. If it doesn't work, you could dirty flash CM version 1 over the existing ROM, then flash "Kernel B".
Click to expand...
Click to collapse
Thank you. Made things much clearer. Dirty flash means just flashing over the existing custom ROM and Kernel right?
And also.. What about if i have CM and Kernel B ... But i want to go change to ParanoidAndroid and still keep the Kernel B? This ROM would remove the Kernel and I would have to re flash ir right?
And also if I am just switching around ROMs only.. I can just flash them one over another? Perhaps a factory reset is healthy in between though.
Dirty flash means flashing over the existing ROM without wiping the system in recovery.
Flashing any ROM over an existing ROM will replace the system and kernel. If you want to change ROMs altogether, you'd flash PA and then flash Kernel B.
When changing ROMs, I always recommend a full wipe (i.e. system, data, cache).
audit13 said:
Dirty flash means flashing over the existing ROM without wiping the system in recovery.
Flashing any ROM over an existing ROM will replace the system and kernel. If you want to change ROMs altogether, you'd flash PA and then flash Kernel B.
When changing ROMs, I always recommend a full wipe (i.e. system, data, cache).
Click to expand...
Click to collapse
Alright. And just one last thing that I got a bit confused of..
When I root and install a custom ROM, I am not going to receive OTAs. If I just flash the newest custom ROM does that work as an update? Or the newest ROM can ble flashed over the newest android? If so... How do I exactly get the newest updates manually? I have to flash to factory ROM and then somehow flash the update? By far thats how I understood it.
rihz said:
Alright. And just one last thing that I got a bit confused of..
When I root and install a custom ROM, I am not going to receive OTAs. If I just flash the newest custom ROM does that work as an update? Or the newest ROM can ble flashed over the newest android? If so... How do I exactly get the newest updates manually? I have to flash to factory ROM and then somehow flash the update? By far thats how I understood it.
Click to expand...
Click to collapse
Depends on which rom, but updates to custom roms generally can just be flashed over. Not sure of the MM jump, but from KK to LP, it worked fine so far. Whatever you do read the instructions of the rom and kernel builders. You get lucky sometimes and can dirty flash things that should not be dirty flashed, but if there are issues, there are instructions on the rom or kernel page how to start again.
If you are factory modified and want a factory image you need to flash in fastboot. If on a custom rom, well, like I said follow their advice. Make sure to backup with recovery and save on computer before doing anything.
wangdaning said:
Depends on which rom, but updates to custom roms generally can just be flashed over. Not sure of the MM jump, but from KK to LP, it worked fine so far. Whatever you do read the instructions of the rom and kernel builders. You get lucky sometimes and can dirty flash things that should not be dirty flashed, but if there are issues, there are instructions on the rom or kernel page how to start again.
If you are factory modified and want a factory image you need to flash in fastboot. If on a custom rom, well, like I said follow their advice. Make sure to backup with recovery and save on computer before doing anything.
Click to expand...
Click to collapse
Okay, thanks!
And Happy New year to you all!

Categories

Resources