Related
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!!!
Hi,
I have followed everything in this thread http://forum.xda-developers.com/showthread.php?t=1837863
I have backups nandroid ready and wasn't too sure, if I dont like this build then i could restore back to stock using CWM? or Odin.
I felt that I need to wait for reply to comfirm before flashing this cyanogenMOD 10.
Thanks!
LeonKnight12 said:
Hi,
I have followed everything in this thread http://forum.xda-developers.com/showthread.php?t=1837863
I have backups nandroid ready and wasn't too sure, if I dont like this build then i could restore back to stock using CWM? or Odin.
I felt that I need to wait for reply to comfirm before flashing this cyanogenMOD 10.
Thanks!
Click to expand...
Click to collapse
IF my memory serves me right, with an unlocked bootloader, you can recover to a TW rom but I think its needs to either have the kernel built into it OR you need to somehow flash to a TW kernel. I say this because I think that if your kernel is still an AOSP one, then the device will not boot up.
some roms already come with a kernel for their rom so I think in most cases, with CWM 6.0.1.x, you could restore a TW nandroid.
If you want to restore a backup of a TouchWiz rom you have then just use the EZ Recovery app to flash the hybrid (CWM/Kexec) recovery...reboot to recovery and restore your nandroid. Simple process!
Once the Dev's building TW roms start using the non-kexec flashing method then you will be able to restore using the normal CWM recovery. Just like you said, you can also use ODIN to restore to stock but it's a pain because you have to root all over again. Just know you have a few options.
Ok thanks everyone!
So good
Fwiw... I've been switching back and forth between Synergy and CM for a couple days now (flashing multiple times) and cwm touch works for synergy but u need new cwm for CM10.
Hope this helps.
Can I flash back to TW from the 2.3.3.0 recovery or would I need to revert back to the previous TWRP.
Sent from my SCH-I535 using xda premium
nativesmiley said:
Can I flash back to TW from the 2.3.3.0 recovery or would I need to revert back to the previous TWRP.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
You come back to TW at your own risk. This where most bricks happen. Best practice is to Odin back to stock and then come back to TW. Luckily you survived CM so far but flashing back to TW could cause a problem. If you don't want to Odin first wipe all partitions till raw and give it a shot.
ok just to clarify....Say I was on Synergy then flashed CM 10.1 now I decided I wanted to come back to Synergy. I would need to Odin back to stock, then flash Synergy? I just couldn't flash Synergy from Cm 10.1? Is this true for CM10 as well? What about flashing my nandroid backup instead of Odin back to stock?
Thanks
Rudy_Ruettiger said:
ok just to clarify....Say I was on Synergy then flashed CM 10.1 now I decided I wanted to come back to Synergy. I would need to Odin back to stock, then flash Synergy? I just couldn't flash Synergy from Cm 10.1? Is this true for CM10 as well? What about flashing my nandroid backup instead of Odin back to stock?
Thanks
Click to expand...
Click to collapse
you do take the risk anytime you flash anything. HOWEVER, i have SYNERGY, MIUI, and CM10.1 along with Liquid (4.2) on my phone. YOU will have problems with finding your files, as 4.2 will create the 0 folder, and it may look like you have lost files. TWRP 2.3.3 does an excellent job of finding back-ups, or just scroll to find the TWRP folder to find your backups.
Gallery also has been known to "lose" pictures. IMO, they are still there, just have to find them. i've actually opened gallery and had it be empty, but a quick close, and then re-open and they show up. Sort of like it has to find them.
YMMV, make backups of everything, and flash away! just know what chances you are setting yourself up for, and be prepared.
edit: AND... i'm not responsible for anything YOU do to your phone... yada yada yada...
just thought i had to throw that out as well...
:cyclops:
goldsmitht said:
you do take the risk anytime you flash anything. HOWEVER, i have SYNERGY, MIUI, and CM10.1 along with Liquid (4.2) on my phone. YOU will have problems with finding your files, as 4.2 will create the 0 folder, and it may look like you have lost files. TWRP 2.3.3 does an excellent job of finding back-ups, or just scroll to find the TWRP folder to find your backups.
Gallery also has been known to "lose" pictures. IMO, they are still there, just have to find them. i've actually opened gallery and had it be empty, but a quick close, and then re-open and they show up. Sort of like it has to find them.
YMMV, make backups of everything, and flash away! just know what chances you are setting yourself up for, and be prepared.
edit: AND... i'm not responsible for anything YOU do to your phone... yada yada yada...
just thought i had to throw that out as well...
:cyclops:
Click to expand...
Click to collapse
so i can use 2.3.3 to flash between TW and CM right? the last time i went back to TW was when i was on 2.3.2.3 and they were say i had to revert back to the recovery before 2.3.2.3. and with that i never had problems flashing between both ROMs. i just want to know if i can flash between TW and CM with 2.3.3 and not revert back to old recoveries.
nativesmiley said:
so i can use 2.3.3 to flash between TW and CM right? the last time i went back to TW was when i was on 2.3.2.3 and they were say i had to revert back to the recovery before 2.3.2.3. and with that i never had problems flashing between both ROMs. i just want to know if i can flash between TW and CM with 2.3.3 and not revert back to old recoveries.
Click to expand...
Click to collapse
Stay on TWRP 2.3.3. I've been using TWRP 2.3.3 just fine while flashing multiple Beans JB TW builds. Not sure what issues others had but it works fine for me. Also, if you intend to install 4.2 AOSP in the future then you'll have to update TWRP again anyway if you downgraded it.
nativesmiley said:
so i can use 2.3.3 to flash between TW and CM right? the last time i went back to TW was when i was on 2.3.2.3 and they were say i had to revert back to the recovery before 2.3.2.3. and with that i never had problems flashing between both ROMs. i just want to know if i can flash between TW and CM with 2.3.3 and not revert back to old recoveries.
Click to expand...
Click to collapse
yes, you can use TWRP 2.3.3 to flash old backups made with any version TWRP. with no problems.
however, you can NOT flash old backups made with CWM. different system and will definitely NOT work.
:cyclops:
thank you very much guys! appreciate the input!
what is the proper way to flash between TW and CM (10.1) so I dont get stuck in roaming mode again?
Yea I am about to do this to correct me if I am wrong please but we are suppose to Odin back to 4.0.4 stock coming from 10.1 then up grade to stock JB from there
Sent from my SCH-I535 using xda app-developers app
Nopi45 said:
Yea I am about to do this to correct me if I am wrong please but we are suppose to Odin back to 4.0.4 stock coming from 10.1 then up grade to stock JB from there
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
know that if you go the ODIN route, you will have to re-root and re-unlock your bootloader.
if you have the MOST up to date recover (CWM OR TWRP - I prefer TWRP 2.3.3) and you have a backup made of a TW ROM, and are on 10.1 currently, then just clear dalvic, cache, and restore your TW ROM.
however, if you do not have one, then would suggest factory reset and then clean install of TW.
there are always "chances" of issues, mainly the 0 folder, but i've been flashing back and forth between MIUI bV, Synergy, and CM10.1 and only problem i had was when my mobile network got switched, and i had to go back in and change to RUIM/SIM. and that was the only thing.
just know what you are doing and know where to go to get answers to help fix things that may go wrong.
and, "insert legal comments here"... no one is responsible for what YOU do to YOUR phone, except YOU.
:cyclops:
The only bad experiences I've had going from 4.2 to TW is when I only briefly installed 4.2 but didn't get data working. That left me with no data in TW. So I had to odin back to stock then re-root, unlock bootloader and flash.
will i be able to go from CM 10.1 to AOKP 4.2.1 without any issue?
Rudy_Ruettiger said:
will i be able to go from CM 10.1 to AOKP 4.2.1 without any issue?
Click to expand...
Click to collapse
I haven't had a problem going from one 4.2 AOSP rom to another. YMMV tho. Just flash a nandroid before you do it just in case.
My HOX was running stock rooted ICS and I did a TWRP backup and flashed [ROM ][22 MAR][UrDroid][HTC One X AT&T][Stock][JB][OTA][Odexed] EVITA 3.18.502.6 using the AROMA installer which had a kernel included. Now I am trying to restore the backup, while the process shows as successful, the phone does not pass the HTC screen, it goes black where the AT&T logo is supposed to come in.
I have to reflash the JB rom to get the phone working again. However, this rom is not stable, I keep getting random crashes or reboots, so I wish to revert to stock
Any idea why this is happening and how I can fix it?
Thanks in advance.
rohangiase said:
My HOX was running stock rooted ICS and I did a TWRP backup and flashed [ROM ][22 MAR][UrDroid][HTC One X AT&T][Stock][JB][OTA][Odexed] EVITA 3.18.502.6 using the AROMA installer which had a kernel included. Now I am trying to restore the backup, while the process shows as successful, the phone does not pass the HTC screen, it goes black where the AT&T logo is supposed to come in.
I have to reflash the JB rom to get the phone working again. However, this rom is not stable, I keep getting random crashes or reboots, so I wish to revert to stock
Any idea why this is happening and how I can fix it?
Thanks in advance.
Click to expand...
Click to collapse
What hboot do you have? If you have hboot 1.14 or newer and are not s-off, you'll need to pull the kernel from the ICS rom and flash it via fastboot.
Great! I just need to track down the stock ICS kernel because I think my phone came with version 2.20.
Any idea where I can locate it?
Thanks.
rohangiase said:
Great! I just need to track down the stock ICS kernel because I think my phone came with version 2.20.
Any idea where I can locate it?
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1671237
Custom ROMs -> Stock Rooted (Odexed/De-Odexed)
Grab any of the ICS ones and it should do the trick. If your TWRP backup backed up boot, you should also be able to pull it from the backup (\sdcard\TWRP\backups\etc.), but I've never done this before and don't have a backup handy on my phone, so I wouldn't be able to tell you exactly where you'd need to look to find it. Shouldn't be too complicated though if you poke around?
Hi guys,
Looking for some advice.
I previously had my phone rooted on 4.2 and everything was working great. For some reason I decided to install the OTA 4.3 update before reading here what it did. Before that though, I did a full backup through CWM.
Anyway, I'm now having trouble re-installing CWM to get back into recovery mode and go back to my backup.
When I try flashing it through Odin, it says Failed, and it seems like the phone blocked it because it is a recovery system.
Currently, when I boot up, I get the Custom logo, and when I try to go into recovery mode, it gets blocked and says it's unauthorized software, so I don't think I really installed the update right.
So, is there anyway to get CWM back on the phone to revert to my backup, or is there a way to flash the whole backup from a PC? The file is still intact on my SD card.
Thanks!
phlass said:
Hi guys,
Looking for some advice.
I previously had my phone rooted on 4.2 and everything was working great. For some reason I decided to install the OTA 4.3 update before reading here what it did. Before that though, I did a full backup through CWM.
Anyway, I'm now having trouble re-installing CWM to get back into recovery mode and go back to my backup.
When I try flashing it through Odin, it says Failed, and it seems like the phone blocked it because it is a recovery system.
Currently, when I boot up, I get the Custom logo, and when I try to go into recovery mode, it gets blocked and says it's unauthorized software, so I don't think I really installed the update right.
So, is there anyway to get CWM back on the phone to revert to my backup, or is there a way to flash the whole backup from a PC? The file is still intact on my SD card.
Thanks!
Click to expand...
Click to collapse
There is currently no way for you to flash CWM onto your S3 now that you have TW 4.3 VRUMCL1 update. If you want root, you will need to use Saferoot. If you wish to flash custom roms, you are currently only able to flash custom TW 4.3 roms via the use of SafeStrap. With Safestrap installed, you will be using a customized version of TWRP. Any and all of your CWM backups are incompatible and wasting storage space. Links to everything I just mentioned are contained in our TW 4.3 discussion thread.
Note that when you use Saferoot to gain root access, the tool is in the S4 section however it states that there is nothing in the tool itself that is S4 specific and that it should work on other 4.3 devices. It does work. Search in the discussion thread or in Saferoot thread to see confirmation.
Edit: to work around the Yellow triangle issue, you'll want to use ThePagel's soft brick thread.
Edit #2: Also, being that you are on TW 4.3 update, you absolutely can not downgrade your firmware using pre-existing Odin stock images. You can only use the official, VRUCML1 tar that is about 1 GB.
SlimSnoopOS said:
There is currently no way for you to flash CWM onto your S3 now that you have TW 4.3 VRUMCL1 update. If you want root, you will need to use Saferoot. If you wish to flash custom roms, you are currently only able to flash custom TW 4.3 roms via the use of SafeStrap. With Safestrap installed, you will be using a customized version of TWRP. Any and all of your CWM backups are incompatible and wasting storage space. Links to everything I just mentioned are contained in our TW 4.3 discussion thread.
Note that when you use Saferoot to gain root access, the tool is in the S4 section however it states that there is nothing in the tool itself that is S4 specific and that it should work on other 4.3 devices. It does work. Search in the discussion thread or in Saferoot thread to see confirmation.
Edit: to work around the Yellow triangle issue, you'll want to use ThePagel's soft brick thread.
Edit #2: Also, being that you are on TW 4.3 update, you absolutely can not downgrade your firmware using pre-existing Odin stock images. You can only use the official, VRUCML1 tar that is about 1 GB.
Click to expand...
Click to collapse
Ok great. Thanks for the help.
phlass said:
Ok great. Thanks for the help.
Click to expand...
Click to collapse
Don't hesitate to post back if you're stuck or need a little more clarification