[Q] JB update and custom kernel - Nexus S Q&A, Help & Troubleshooting

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!!!

Related

Back to Honeycomb with Nandroid

I have a nandroid of my rooted honeycomb 3.2.1 install. If I want to flash the leaked stock ICS, is it possible to go back to the nandroid and then go back to stock recovery to install the leak?
I understand I can use the unrooting method but I'm just trying to understand this better and understand my options. I don't wish to go back to the stock images and lock the boot loader again just to flash the update and unlock and root again if I don't have to unless that is just the best way to do it.
crankerchick said:
I have a nandroid of my rooted honeycomb 3.2.1 install. If I want to flash the leaked stock ICS, is it possible to go back to the nandroid and then go back to stock recovery to install the leak?
I understand I can use the unrooting method but I'm just trying to understand this better and understand my options. I don't wish to go back to the stock images and lock the boot loader again just to flash the update and unlock and root again if I don't have to unless that is just the best way to do it.
Click to expand...
Click to collapse
I would really advise that you flash the most recent EOS wingray. Rom #36 and the GApps (Google System apps) package version 10. It seems to be more complete than the ota update, it's easier to flash and you preserve your root and recovery.
Thanks, nice to see someone offer a comparison of the two packages. I'm currently running EOS build 34 from the other night. I guess i was just curious about the stock update. I know there are still some things non-functional with eos and figured the stock rom would be completely functional minus whatever bugs. It does seem like a bit of work to flash it though, since the only thing i can seem to find on what to do is saying to unroot and relock using the moto stock files.
Seems like if im interested in trying a stock rom i shojld just wait for the ota and a rom made from it with root already.
I will miss the notification tray settings in eos if i go stock!
crankerchick said:
Thanks, nice to see someone offer a comparison of the two packages. I'm currently running EOS build 34 from the other night. I guess i was just curious about the stock update. I know there are still some things non-functional with eos and figured the stock rom would be completely functional minus whatever bugs. It does seem like a bit of work to flash it though, since the only thing i can seem to find on what to do is saying to unroot and relock using the moto stock files.
Seems like if im interested in trying a stock rom i shojld just wait for the ota and a rom made from it with root already.
I will miss the notification tray settings in eos if i go stock!
Click to expand...
Click to collapse
True, that.
EOS wingray version 36 with the version 10.1 GApps really fixed most of the remaining issues. There should be a new nightly and there is a new GApps 10.2 to flash today.

[Q] About flashing custom ROMs

Hi everyone!
I am fairly new with android and I just rooted my transformer last night. I was also able to install a custom ROM, revolver 3.11.1 (Honeycomb).
If I want to flash an ICS ROM (Revolver, Android Revolution or Codename), from a custom HC ROM, do I have to do anything else? Or can I just flash it straight away?
Based on what I've read, if ever I wish to downgrade back to honeycomb, I would not just flash a honeycomb ROM. I have found a few guides on how to downgrade back to Honeycomb from ICS. Is this correct?
Since you have cwm, It's as simple as going into recovery and flashing your desired custom rom.
Normal procedure (to avoid conflicts/problems) is to wipe and/or format before flashing a new rom.
A good tool to have is the superwipe lite script found in the Revolution HD thread. (I personally use that instead of the wipe option that is in CWM).
Oh...and you can also backup your current ROM and state by using the backup function in CWM BEFORE you wipe/format. Just in case you don't like the new rom and want to revert.
FYI...if you go ICS and want to restore your HC rom...a restore then a reflash of the HC Rom is needed.
Thanks for the reply!
Just to clarify, once I flash an ICS custom ROM and didn't like it, I can't just flash back to a HC custom rom or stock HC rom. Is this correct?
ragnaboy2010 said:
Thanks for the reply!
Just to clarify, once I flash an ICS custom ROM and didn't like it, I can't just flash back to a HC custom rom or stock HC rom. Is this correct?
Click to expand...
Click to collapse
Yup. Even if you use the restore function...you need to flash that particular HC ROM over the restore. (Because the backup doesn't backup the kernel...so if you don't flash the HC rom...the ICS kernel is still there...and you won't be able to boot)
sorry to hijack the thread but my question is similar so i dun want to start a new one
I am currently on revolver 3.11 as well and thinking to update to a ICS custom rom
I am using the blade OC kernel at the moment. I just want to ask if the new rom comes with the ICS kernel or do I need to look for an ICS kernel to put it manually?
Also, I just want to check that Ti Backup does not back up downloaded data right?
Thanks a million
strikeraj said:
sorry to hijack the thread but my question is similar so i dun want to start a new one
I am currently on revolver 3.11 as well and thinking to update to a ICS custom rom
I am using the blade OC kernel at the moment. I just want to ask if the new rom comes with the ICS kernel or do I need to look for an ICS kernel to put it manually?
Also, I just want to check that Ti Backup does not back up downloaded data right?
Thanks a million
Click to expand...
Click to collapse
Everything is included when you flash one of the available ICS ROM.
There is no custom ICS kernel right now anyway as Asus have not released the kernel source.

Rooted stock rom ICS 4.0.4 but...

Let's say I want to flash a rom and made a backup thru CWM of my stock rom will I be able to keep root if I flash it back to the stock rom ?
II'm doing this cause I care most about no auto brightness issue than the actual advantage to go with a custom rom.
Thanks
Why don't you just root your stock ROM then? You need to be rooted to flash CWM recovery anyways..
rener78 said:
Let's say I want to flash a rom and made a backup thru CWM of my stock rom will I be able to keep root if I flash it back to the stock rom ?
Click to expand...
Click to collapse
If your ROM is already rooted, and you're restoring it from CWM, yes. If you're using fastboot to re-flash the stock ROM, no, you'll have to re-root it.
I'm kind of confused about what you're asking, though. Can you give more specific details? Are you going to flash a different ROM and try to flash the stock ROM, or parts of it, on top of the new ROM? I wouldn't do that unless you're very sure of what you're doing.

[Q] Restoring through CWM to stock

hi,i am using stock rom running 4.0.4,i had it rooted too and now i had two queries
1)Is rom manager compatible with Atrix 2??
im asking this because when i open it, it shows u need to install CWM recovery...but no option in that responds...not even intall cwm (1st option in menu)....so i installed CWM using atrix boot strapper app and now still rom manager is not detecting CWM..please help
2)after installing CWM, i had backup my present stock rom..so if i flash a new rom now will that CWM and back up still exist??(because we will wipe data which will remove everyhting right??)
for suppose if i flash jelly bean rom and if i dont like it...can i restore my previous stock rom without bricking my device??
thanks for u r help
vdpraneeth said:
hi,i am using stock rom running 4.0.4,i had it rooted too and now i had two queries
1)Is rom manager compatible with Atrix 2??
im asking this because when i open it, it shows u need to install CWM recovery...but no option in that responds...not even intall cwm (1st option in menu)....so i installed CWM using atrix boot strapper app and now still rom manager is not detecting CWM..please help
2)after installing CWM, i had backup my present stock rom..so if i flash a new rom now will that CWM and back up still exist??(because we will wipe data which will remove everyhting right??)
for suppose if i flash jelly bean rom and if i dont like it...can i restore my previous stock rom without bricking my device??
thanks for u r help
Click to expand...
Click to collapse
1) Rom manager is not compatible with Atrix 2. I would not use it. Why do you need it anyway??
You can use Atrix Bootstrapper to go into CWM recovery . Rest can be done there. Or you can use Boot Menu Manager.
2)Of course! it will still be there! the backup is saved on your SD Card. So as long as you don't format your SD Card. It will be there.
NHS2008 said:
1) Rom manager is not compatible with Atrix 2. I would not use it. Why do you need it anyway??
You can use Atrix Bootstrapper to go into CWM recovery . Rest can be done there. Or you can use Boot Menu Manager.
2)Of course! it will still be there! the backup is saved on your SD Card. So as long as you don't format your SD Card. It will be there.
Click to expand...
Click to collapse
Rom Manager does work with Atrix2. If you're on Stock ICS, you can install CWM on every boot, then flash the Bionic recovery through Rom Manager. That will allow you to use the 1 touch backup in RM, just hit backup rom and everything does what it's supposed to.
Here is the CWM on every boot for Stock ICS.
NHS2008 said:
1) Rom manager is not compatible with Atrix 2. I would not use it. Why do you need it anyway??
You can use Atrix Bootstrapper to go into CWM recovery . Rest can be done there. Or you can use Boot Menu Manager.
2)Of course! it will still be there! the backup is saved on your SD Card. So as long as you don't format your SD Card. It will be there.
Click to expand...
Click to collapse
2)will the CWM recovery exist after flashing new rom or i need to install it again??
when i restore to stock fom JB, it means downgrading the firmware right??
so will there be a chance of bricking or is it same to restore anytime from any version??
vdpraneeth said:
2)will the CWM recovery exist after flashing new rom or i need to install it again??
when i restore to stock fom JB, it means downgrading the firmware right??
so will there be a chance of bricking or is it same to restore anytime from any version??
Click to expand...
Click to collapse
No, your Recovery will be wiped after you flash a new rom, but you can install it again and restore your ROM.
But when restoring a rom, make sure you ARE ON THE ROM you are restoring.
E.g. If you flash JB and want Stock ICS back with your backup. First flash the Stock ICS from RSD and then restore your backup from CWM on it.
Or Vice-Versa.
@41rw4lk, Thanks for rectifying that. I did not bother with Rom Manager much.
NHS2008 said:
No, your Recovery will be wiped after you flash a new rom, but you can install it again and restore your ROM.
But when restoring a rom, make sure you ARE ON THE ROM you are restoring.
E.g. If you flash JB and want Stock ICS back with your backup. First flash the Stock ICS from RSD and then restore your backup from CWM on it.
Or Vice-Versa.
@41rw4lk, Thanks for rectifying that. I did not bother with Rom Manager much.
Click to expand...
Click to collapse
but downgrading to stock ICS from JB will brick my mobile right??
is there any problem if im not on the rom im restoring??
(im a newbie and i dont know much..even not found these after searching a lot..thats the reason im asking all these)
41rw4lk said:
Rom Manager does work with Atrix2. If you're on Stock ICS, you can install CWM on every boot, then flash the Bionic recovery through Rom Manager. That will allow you to use the 1 touch backup in RM, just hit backup rom and everything does what it's supposed to.
Here is the CWM on every boot for Stock ICS.
Click to expand...
Click to collapse
how is it possible to flash bionic recovery through RM...all the menu options are disabled for me there even after CWM installed through bootstrap
vdpraneeth said:
2)will the CWM recovery exist after flashing new rom or i need to install it again??
when i restore to stock fom JB, it means downgrading the firmware right??
so will there be a chance of bricking or is it same to restore anytime from any version??
Click to expand...
Click to collapse
I don't think any recovery exist after flashing a new rom. We have a locked bootloader, so we can't replace the stock recovery.img, all of our recoveries hijack the boot process to work. CM10 and PA I believe have a built in recovery, and that's about as close as you'll get to having a recovery exist after flashing a rom.
As far as restoring from JB, I believe you can downgrade to ICS, but you'll have to look at the JB thread to be certain. I'm on AT&T so I haven't had an opportunity to try JB (officially). CM10 is based on JB, but for our phone with the locked bootloader, it's more of a pseudo experience and is based on our ICS framework.
As for bricking, there is always a chance to brick, that's part of the mod game, but if you read and pay attention to what you have and what you're doing, you'll be alright.
vdpraneeth said:
but downgrading to stock ICS from JB will brick my mobile right??
is there any problem if im not on the rom im restoring??
(im a newbie and i dont know much..even not found these after searching a lot..thats the reason im asking all these)
Click to expand...
Click to collapse
UNLESS you have AT&T phone you should be just fine with ref lashing the ICS.
YES. there is a big problem if you are not on a ROM you are restoring.
Its like you are trying to comlete your jigsaw puzzle by putting pieces from some another jigsaw puzzle.
vdpraneeth said:
how is it possible to flash bionic recovery through RM...all the menu options are disabled for me there even after CWM installed through bootstrap
Click to expand...
Click to collapse
You need to use the CWM on every boot setup, the Atrix2Bootstrap alone won't do.
41rw4lk said:
You need to use the CWM on every boot setup, the Atrix2Bootstrap alone won't do.
Click to expand...
Click to collapse
yes...my phone is an AT&T version...though im using it with IDEA.....
so if i install CWM on every boot,then rom manager will detect it and work right??
vdpraneeth said:
yes...my phone is an AT&T version...though im using it with IDEA.....
so if i install CWM on every boot,then rom manager will detect it and work right??
Click to expand...
Click to collapse
Yes. I will say though, if you're on an AT&T branded phone with AT&T firmware, do NOT try to flash the new JB FXZ. It doesn't matter who your carrier is, it matters what firmware your phone is using. So, if you're on AT&T then you need to make sure that the things you flash are for AT&T, or else you will brick and that will be then end of that.
41rw4lk said:
Yes. I will say though, if you're on an AT&T branded phone with AT&T firmware, do NOT try to flash the new JB FXZ. It doesn't matter who your carrier is, it matters what firmware your phone is using. So, if you're on AT&T then you need to make sure that the things you flash are for AT&T, or else you will brick and that will be then end of that.
Click to expand...
Click to collapse
thanks a lot...
what are the ROMS avaialble for us???
can i reflash stock ICS from any of those ROMS safely??
thank you
vdpraneeth said:
thanks a lot...
what are the ROMS avaialble for us???
can i reflash stock ICS from any of those ROMS safely??
thank you
Click to expand...
Click to collapse
CM10
PA
Numa
MIUI (had battery issues, but I think they got it all worked out)
there's a few, you'll just have to look. Most of the time, if something is not meant for AT&T, the devs will post in the description that it isn't compatible. If you want stock ICS back at anytime, you can do yourself a favor and make a backup of your stock ICS all setup the way you like it, so you can restore if needed. If all else fails, there is an Official ICS FXZ that will get you back to stock ICS.
41rw4lk said:
CM10
PA
Numa
MIUI (had battery issues, but I think they got it all worked out)
there's a few, you'll just have to look. Most of the time, if something is not meant for AT&T, the devs will post in the description that it isn't compatible. If you want stock ICS back at anytime, you can do yourself a favor and make a backup of your stock ICS all setup the way you like it, so you can restore if needed. If all else fails, there is an Official ICS FXZ that will get you back to stock ICS.
Click to expand...
Click to collapse
my main question is :
will downgrade to ICS cause brick??
how do i create my own backup for stock ICS??
vdpraneeth said:
my main question is :
will downgrade to ICS cause brick??
how do i create my own backup for stock ICS??
Click to expand...
Click to collapse
You're killing me smalls. You're on ICS already, you're not downgrading anything, nor can you downgrade ie. Gingerbread. There is no Official JB for AT&T, so that's not an issue. CM10 is a JB based rom built on an ICS frame, (for our phone at least), and again, you're not downgrading.
To make a back up, boot in to CWM or whatever recovery you're using (not stock), and click backup. You might hit up the noob thread to get an idea of the terminology and basics for our device. Not trying to be rude, but you're running yourself in circles. You got to walk before you can run.

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.

Categories

Resources