so heres the situation
running stock mra58k rooted with elementalX
encrypted
rooted with su2.46
can i just flash system.img from mra58n to upgrade then reroot?
darthchilli said:
can i just flash system.img from mra58n to upgrade then reroot?
Click to expand...
Click to collapse
Yes, that will work just fine. You may need a newer version of SuperSU to get proper root on marshmallow. The latest version is 2.52 (there is also a v2.56, but that's only for the "systemless" root method).
Face_Plant said:
Yes, that will work just fine. You may need a newer version of SuperSU to get proper root on marshmallow. The latest version is 2.52 (there is also a v2.56, but that's only for the "systemless" root method).
Click to expand...
Click to collapse
So if we are running a Kernel and rooted, this will work. I guess I am nervous to try flashing the new OTA because I don't want to have to setup programs again, but that isn't a huge deal.
haibane said:
So if we are running a Kernel and rooted, this will work. I guess I am nervous to try flashing the new OTA because I don't want to have to setup programs again, but that isn't a huge deal.
Click to expand...
Click to collapse
I've been using the same non-encrypted/no boot warning kernel on MRA58K, MRA58N, and MRA58R with no issues. I was rooted with the experimental "systemless" root method. I have flashed the system.img from both MRA58N and MRA58R without losing root or having to flash anything extra (like my kernel or SuperSU) or set up my phone again.
The only things you will have to redo (if you ever did any of these in the first place) are build.prop edits, redelete any system apps you removed, reinstall Busy box, and reinstall hosts files from ad blockers. All of your other data should remain unchanged.
Face_Plant said:
I've been using the same non-encrypted/no boot warning kernel on MRA58K, MRA58N, and MRA58R with no issues. I was rooted with the experimental "systemless" root method. I have flashed the system.img from both MRA58N and MRA58R without losing root or having to flash anything extra (like my kernel or SuperSU) or set up my phone again.
The only things you will have to redo (if you ever did any of these in the first place) are build.prop edits, redelete any system apps you removed, reinstall Busy box, and reinstall hosts files from ad blockers. All of your other data should remain unchanged.
Click to expand...
Click to collapse
So my follow up question. I am runing SuperSU 2.52. Would I have to do a clean install to update to the "systemless" after a OTA flash?
haibane said:
So my follow up question. I am runing SuperSU 2.52. Would I have to do a clean install to update to the "systemless" after a OTA flash?
Click to expand...
Click to collapse
You cannot flash an OTA if you are rooted.
danarama said:
You cannot flash an OTA if you are rooted.
Click to expand...
Click to collapse
Sorry I meant do a system.img flash. I assume it has the same result as doing a full OTA and then re-rooting/adding custom kernel.
Basically, I am just trying to get from mra58k with supersu 2.52 and franco kernel to mra58r with supersu 2.52 or 2.56 and franco kernel.
Obviouslly, I could probably just do a nandroid backup and go crazy on the phone to try and do whatever, but I wanted to see what the preferred method would be first.
haibane said:
Sorry I meant do a system.img flash. I assume it has the same result as doing a full OTA and then re-rooting/adding custom kernel.
Basically, I am just trying to get from mra58k with supersu 2.52 and franco kernel to mra58r with supersu 2.52 or 2.56 and franco kernel.
Obviouslly, I could probably just do a nandroid backup and go crazy on the phone to try and do whatever, but I wanted to see what the preferred method would be first.
Click to expand...
Click to collapse
I don't know what a full OTA is but no, an OTA is not the same as flashoing a system.img.
Process should be flash system.img and boot.img, boot to recovery, flash kernel and supersu. All good. Do not boot up to android before flashing kernel if you want to be unencrypted.
The reason for flashing the boot.img is that some kernels do not provide their own ramdisk, so it is always worth flashing the boot.img that comes in the factory image for the sake of wasting 3 seconds.
danarama said:
I don't know what a full OTA is but no, an OTA is not the same as flashoing a system.img.
Process should be flash system.img and boot.img, boot to recovery, flash kernel and supersu. All good. Do not boot up to android before flashing kernel if you want to be unencrypted.
The reason for flashing the boot.img is that some kernels do not provide their own ramdisk, so it is always worth flashing the boot.img that comes in the factory image for the sake of wasting 3 seconds.
Click to expand...
Click to collapse
Ah. That makes sense. I have been avoiding going unencrypted because well encryption brings security so why not lose a little processing to gain security. Anyhow, Thanks I'll try this method after my backup finishes.
Also not sure if you know the answer to this, but could I move to the systemless root variant after doing the system.img and boot.img flash? I would assume this would become possible because the system.img would clean anything done by the standard root.
haibane said:
Ah. That makes sense. I have been avoiding going unencrypted because well encryption brings security so why not lose a little processing to gain security. Anyhow, Thanks I'll try this method after my backup finishes.
Click to expand...
Click to collapse
No probs.
This is probably going to sound insane, but I am almost annoyed that the update appears to have worked flawlessly. I kind of wanted some sort of catastrophic failure. I've yet to have any bootloop etc...
haibane said:
This is probably going to sound insane...
Click to expand...
Click to collapse
yeah....
haibane said:
This is probably going to sound insane, but I am almost annoyed that the update appears to have worked flawlessly. I kind of wanted some sort of catastrophic failure. I've yet to have any bootloop etc...
Click to expand...
Click to collapse
Be careful what you wish for, you just might get it.
Related
Hello XDA,
Im quite sure this has already been asked on the forum but i couldn't find an answer.
I need some advise about my recently rooted Nexus 6. I want to fully enjoy from a custom recovery but i dont want to lose the option of receiving OTA updates to my phone.
What do you guys do so your nexus keeps getting the lastest of Android?
Can i use WugFresh's root toolkit to sideload OTA updates even when i have a custom recovery?
What other ways can i use to update Android?
Thanks,
No but you could use the tool kit to reload recovery and stock then take your OTA then reroot and reload TWRP.
And you can side load but it is important you understand exactly what you're doing. the kit does nothing more than you can from the command line it just tries to save you from yourself. it can be a help or hindrance. If you don't understand what's going on it will be the latter
Sent from my Benzo'd Google N6 on VZ
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Didgeridoohan said:
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
Agreed. OTA is overrated. If I was on T-Mobile or the factory image was not available. I would grab the radio and load what I wanted.
Now I am running the E radio and the i build on VZ
Sent from my Benzo'd Google N6 on VZ
Didgeridoohan said:
you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
what do you mean flashing directly?
Can i use Simple recovery switcher to eaisly switch to stock recovery without unrooting and get the OTA update?
torecdude said:
what do you mean flashing directly?
Can i use Simple recovery switcher to eaisly switch to stock recovery without unrooting and get the OTA update?
Click to expand...
Click to collapse
Click the link in my signature for more information on OTA updates. No modifications of any kind to system can be made for an OTA to flash successfully.
Didgeridoohan said:
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
Evolution_Freak said:
Click the link in my signature for more information on OTA updates. No modifications of any kind to system can be made for an OTA to flash successfully.
Click to expand...
Click to collapse
Thank you, your thread as helped me alot. But i didnt understand why did you posted OTA files that are flashable with TWRP altough we cant update lollipop with rooted devices?
Guess im going to have to unroot and flash stock recovery to OTA update directly from google or use a pure shamu rom.
Updating via OTA on a Nexus is an undesirable method IMO. As mentioned previously, if you download and flash the factory images, you avoid the potential update failures in an OTA from modified stock parameters. As for recovery, you don't need to flash a custom recovery, you can simply boot a custom recovery from the PC using fastboot and having the recovery image of choice in your platform tools.
fastboot boot name_of_recovery_image_here.img
I don't flash from the device any more. Keeps me out of trouble. Being connected to the PC helps remind me to move a copy of my backup to the PC before flashing.
torecdude said:
Thank you, your thread as helped me alot. But i didnt understand why did you posted OTA files that are flashable with TWRP altough we cant update lollipop with rooted devices?
Guess im going to have to unroot and flash stock recovery to OTA update directly from google or use a pure shamu rom.
Click to expand...
Click to collapse
I put the link to that thread in mine as a quick way for people who are rooted/unlocked and running a custom recovery to find. Those are not the "official" way of updating. They work because someone here put the time in to make them work for unlocked/rooted users. No, you can't use an "official" OTA process if you've altered your device but that method uses TWRP to flash just like you were flashing a custom ROM.
I'm glad my thread has helped you! Since I'm not a developer yet, it is my sole purpose here to help users with anything I can. So a comment like that is very reassuring that I'm on the right path.
I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.
Quick answer: Isn't going to happen.
Reason: Lollipop wont install OTA if you modify /system, because it is now written as a block, unlike previous versions of android.
IF you root, you have modified /system.
Consequence: you will not update by OTA while rooted. It will fail.
Possible workaround: You can however AFAIK, unroot and then take an OTA, but I'll let others confirm this, please don't take me saying it as factual.
Factory image flash: always works, but you have to await the release after the updates.
mad_rulzzz said:
I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.
Click to expand...
Click to collapse
FWIW: I would recommend that you:
1) Unlock bootloader
2) Decide if you want uncrypted kernel, or not (since it wipes data, just like unlocking bootloader).
3) Fastboot flash TWRP recovery.
4) Download SuperSU .zip and flash it in recovery.
5) Now, when a new OTA comes out, they usually show up here > http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493
6) You can download your current factory image here > https://developers.google.com/android/nexus/images
7) Unzip your current factory image. Fastboot flash the system.img and that will unroot and restore the stock recovery.
8) Fastboot flash the stock boot.img if you have a custom kernel (or an unencrypted stock kernel).
9) Relax and wait for the OTA.
RW-1 said:
Quick answer: Isn't going to happen.
Reason: Lollipop wont install OTA if you modify /system, because it is now written as a block, unlike previous versions of android.
IF you root, you have modified /system.
Consequence: you will not update by OTA while rooted. It will fail.
Possible workaround: You can however AFAIK, unroot and then take an OTA, but I'll let others confirm this, please don't take me saying it as factual.
Factory image flash: always works, but you have to await the release after the updates.
Click to expand...
Click to collapse
I knew about the OTA failing due to the system partition getting changed while rooting. I think what I was looking for what cam30era just explained!!!
mad_rulzzz said:
I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.
Click to expand...
Click to collapse
You can just update in fastboot without an OTA. Just flash the new bootloader, system and possibly the new boot.img in fastboot and reroot. Erase and flash cache.img afterwards. Thats how i do it at least.
mad_rulzzz said:
I knew about the OTA failing due to the system partition getting changed while rooting. I think what I was looking for what cam30era just explained!!!
Click to expand...
Click to collapse
What he just explained is what I said, unroot and take the OTA.... He listed how as well.
RW-1 said:
What he just explained is what I said, unroot and take the OTA.... He listed how as well.
Click to expand...
Click to collapse
Yup.
@rw_1 @cam30era thanks guys
I would do what gee2012 said.
From what I have seen the OTA and the images are released pretty close together.
Instead of flashing images to get back to stock and waiting for the OTA. and then re-rooting
Just download the image files from Google. Manually flash all the files EXCEPT user data if you want to keep your data.
Re-root.
You are now updated and don't have to wait for OTA.
Either way works so it depends on which you are happier with.
mad_rulzzz said:
@rw_1 @cam30era thanks guys
Click to expand...
Click to collapse
Welcome. And BTW: there's a button for that.
gee2012 said:
You can just update in fastboot without an OTA. Just flash the new bootloader, system and possibly the new boot.img in fastboot and reroot. Erase and flash cache.img afterwards. Thats how i do it at least.
Click to expand...
Click to collapse
Just to be sure I understood right:
If I don't care about app data or settings ( I have titanium backup),
1)I can just unlock the boot loader
2)Flash the latest factory image from [developers.google.com/android/nexus/images]
3)Root using chain fire's tool
And repeat the process when the factory image of the next version is uploaded by google.
one last thing... Does Google upload factory images after each OTA happens?
cam30era said:
Welcome. And BTW: there's a button for that.
Click to expand...
Click to collapse
My BAd!!
mad_rulzzz said:
If I don't care about app data or settings ( I have titanium backup),
1)Can I just unlock the boot loader
2)Flash the latest factory image from [developers.google.com/android/nexus/images]
3)Root using chain fire's tool
And repeat the process when the factory image of the next version is uploaded by google.
Does Google upload factory images after each OTA happens? i.e; If Nexus 6 receives an OTA to 5.2, will they upload the 5.2 factory image soon?
Click to expand...
Click to collapse
When you unlock the bootloader it will wipe the contents of your SD card. Make sure it is backed up on your PC.
Unfortunately, not every OTA gets published as a factory image. Most, but not all. Case in point: LMY47M.
cam30era said:
Unfortunately, not every OTA gets published as a factory image. Most, but not all. Case in point: LMY47M.
Click to expand...
Click to collapse
I noticed that.... But that build is only for T-Mobile users, I guess...
Minor Differences, for example; If you take the android builds for Indian phones they are required by law to display the SAR rating. So I wouldn't worry about LMY47M, unless they have changed something to fix the memory leaks.
mad_rulzzz said:
I noticed that.... But that build is only for T-Mobile users, I guess...
Minor Differences, for example; If you take the android builds for Indian phones they are required by law to display the SAR rating. So I wouldn't worry about LMY47M, unless they have changed something to fix the memory leaks.
Click to expand...
Click to collapse
Correct. M is intended for T-Mobile. My point, though, is that Google doesn't always, 100% of the time publish a factory image for every OTA.
Okay so I have the bootloader unlocked, rooted, twrp and running ex kernel. I had system update turned off in disable services but then the phone wasn't going into deep sleep was always running at 300 mhz. So to fix that, I turned system update back on ... great I get deep sleep back but now they released the update for stage fright and I get a message that it is downloaded and ready to install.... I tried the install even though I knew it would fail... it goes to twrp recovery. So how do I keep the system from trying to update? I know I could in theory flash the stock recovery let it update and flash back to twrp... maybe.. but I am hoping there is another route since I plan on flashing the M factory files when they come available...
Gage_Hero said:
Okay so I have the bootloader unlocked, rooted, twrp and running ex kernel. I had system update turned off in disable services but then the phone wasn't going into deep sleep was always running at 300 mhz. So to fix that, I turned system update back on ... great I get deep sleep back but now they released the update for stage fright and I get a message that it is downloaded and ready to install.... I tried the install even though I knew it would fail... it goes to twrp recovery. So how do I keep the system from trying to update? I know I could in theory flash the stock recovery let it update and flash back to twrp... maybe.. but I am hoping there is another route since I plan on flashing the M factory files when they come available...
Click to expand...
Click to collapse
or you can flash part of the factory.img, just system.img via fastboot, update and keep your data and be over it in 10-15 seconds.
simms22 said:
or you can flash part of the factory.img, just system.img via fastboot, update and keep your data and be over it in 10-15 seconds.
Click to expand...
Click to collapse
Thanks simms..... so just the system.img from the version I am currently running? Do I retain root, twrp and the same kernel or the kernel goes back to stock which I am guessing...
Gage_Hero said:
Thanks simms..... so just the system.img from the version I am currently running? Do I retain root, twrp and the same kernel or the kernel goes back to stock which I am guessing...
Click to expand...
Click to collapse
System.img from version you want to update to. Will lose root and anything else you added as system files. Just reflash the SU zip in TWRP to get root back.
Gage_Hero said:
Thanks simms..... so just the system.img from the version I am currently running? Do I retain root, twrp and the same kernel or the kernel goes back to stock which I am guessing...
Click to expand...
Click to collapse
prdog1 said:
System.img from version you want to update to. Will lose root and anything else you added as system files. Just reflash the SU zip in TWRP to get root back.
Click to expand...
Click to collapse
The easiest way to accomplish this is:
After you have fastboot flashed the system.img, take your hands off your PC keyboard and pick up your N6. Use the volume button to navigate to the "Recovery" option (in phones bootloader) and select it with the volume button. TWRP will boot. Then flash the SuperSU.zip and reboot system. Done.
Worked perfectly, system updated, regained root and no loss of data .... one happy camper.
Okay so after a couple of days the update shows back up now.... I flashed the system img as suggested, did the update, rebooted, added root back never lost data but the goofy notification for the same update showed back up yesterday night.
Which factory image did you use? If you didn't use the latest 5.1.1 (stagefright patches), you'll still get an OTA notification.
And on a side note: what version did you update from? If you didn't update from 5.1.1 to 5.1.1 (sounds silly right), you might not have the latest radio, bootloader and so on.
Gage_Hero said:
Okay so after a couple of days the update shows back up now.... I flashed the system img as suggested, did the update, rebooted, added root back never lost data but the goofy notification for the same update showed back up yesterday night.
Click to expand...
Click to collapse
Didgeridoohan said:
Which factory image did you use? If you didn't use the latest 5.1.1 (stagefright patches), you'll still get an OTA notification.
And on a side note: what version did you update from? If you didn't update from 5.1.1 to 5.1.1 (sounds silly right), you might not have the latest radio, bootloader and so on.
Click to expand...
Click to collapse
Yup. Need to be up to date, with the latest. Currently LMY48I for most of us. LYZ29J for TMO, and LVY48E for Fi.
cam30era said:
Yup. Need to be up to date, with the latest. Currently LMY48I for most of us. LYZ29J for TMO, and LVY48E for Fi.
Click to expand...
Click to collapse
Ok so what I did was I was on LMY47Z and just fastboot flashed the same file..... I am guessing that is not the way to do it... all files are from the same version bootloader, radio etc....
Gage_Hero said:
Ok so what I did was I was on LMY47Z and just fastboot flashed the same file..... I am guessing that is not the way to do it... all files are from the same version bootloader, radio etc....
Click to expand...
Click to collapse
If you fastboot flashed the system.img for LMY48I, that should have been sufficient. What carrier are you on?
cam30era said:
If you fastboot flashed the system.img for LMY48I, that should have been sufficient. What carrier are you on?
Click to expand...
Click to collapse
Sorry for the confusion, I flashed the LMY47Z file over top of the LMY47Z I didn't change versions at all which I think is where I went wrong.... I am on Telus in Canada. I thought I only needed to get to an unrooted system version.
Gage_Hero said:
Sorry for the confusion, I flashed the LMY47Z file over top of the LMY47Z I didn't change versions at all which I think is where I went wrong.... I am on Telus in Canada. I thought I only needed to get to an unrooted system version.
Click to expand...
Click to collapse
Aahh. Got it. Well, if you want the notifications to go away, you need to fastboot flash the latest system.img. Each time a new one comes out. For you, that would be LMY48I for now. And don't worry, you won't loose anything in the process.
Gage_Hero said:
Ok so what I did was I was on LMY47Z and just fastboot flashed the same file..... I am guessing that is not the way to do it... all files are from the same version bootloader, radio etc....
Click to expand...
Click to collapse
If you flash the file from the same version you are not going to have the update so you will continue to be notified. To stop the notification you need to use the 5.1.1 (LMY48I) or 5.1.1 (For T-Mobile ONLY) (LYZ28J) or 5.1.1 (For Project Fi ONLY) (LVY48E). These are the images that have the StageFright patch included. These images can be found at https://developers.google.com/android/nexus/images#shamu
alryder said:
If you flash the file from the same version you are not going to have the update so you will continue to be notified. To stop the notification you need to use the 5.1.1 (LMY48I) or 5.1.1 (For T-Mobile ONLY) (LYZ28J) or 5.1.1 (For Project Fi ONLY) (LVY48E). These are the images that have the StageFright patch included. These images can be found at https://developers.google.com/android/nexus/images#shamu
Click to expand...
Click to collapse
I flashed the system.img and radio.img from LMY48I all appear to be good now. Thanks for your help
Gage_Hero said:
Ok so what I did was I was on LMY47Z and just fastboot flashed the same file..... I am guessing that is not the way to do it... all files are from the same version bootloader, radio etc....
Click to expand...
Click to collapse
Flashing system.img LMY48i will update LMY47Z . The result is the same as unrooting, back to stock and install the OTA and root again.
NLBeev said:
Flashing system.img LMY48i will update LMY47Z . The result is the same as unrooting, back to stock and install the OTA and root again.
Click to expand...
Click to collapse
If fastboot flash the LMY48i there is no longer the option or need to OTA.
prdog1 said:
If fastboot flash the LMY48i there is no longer the option or need to OTA.
Click to expand...
Click to collapse
Yes that is correct. My post is unclear. I did the update twice. Flashed system.img and because the OTA was only 24 Mb I flashed LMY47Z again and updated through OTA.
The results were the same. Data was kept, but not the settings. Build.prop was overwritten.
DPI 560 again, my icons replaced by google default and Black Google Now launcher replaced by the ugly white one.
It is restored now, but need some hassle.
I've seen several posts for updating with data untouched. But settings are always touched.
Flashing M preview is more worse, because even the internal storage is wiped. So copy the nandroid backup to the PC first.
Sorry for the 'encrypted' previous post.
I hope this post is more usefull.
I'm a newbie and my phone is at Marshmallow 6.0.1, rooted with Nexus Root Toolkit su (with SuperSU 2.62)
later flashed twrp, now want to install ElementalX Kernel.
Do I need to unroot the system, and then flash the kernel with twrp?
thanks in advance.
The kernel is the boot.img. Just flash it via TWRP and it will automatically be present.
And why do you specifically want to install Elementalx? If you've got a working rooted phone, why continue to mess with it? Continual unnecessary tweaking is the sure way to end up with a glass-and-metal paperweight...
daddylok said:
I'm a newbie and my phone is at Marshmallow 6.0.1, rooted with Nexus Root Toolkit su (with SuperSU 2.62)
later flashed twrp, now want to install ElementalX Kernel.
Do I need to unroot the system, and then flash the kernel with twrp?
thanks in advance.
Click to expand...
Click to collapse
Better flash superSU2.65.zip (latest atm).
Not necessarily better. Versions after 2.62 have a number of comments across various threads saying that root doesn't work for them. 2.62 uses a different method from the later versions. 2.62 works fine for me and (from the silence in the forums) for most people, so upgrading to 2.64/2.65 is probably taking an unnecessary risk.
And again, why try to install a different kernel on a working rooted device? It makes no sense to me unless there's an amazing function that will make a discernable difference, and personally I don't believe that any kernel makes that much of a difference in real-life normal usage.
dahawthorne said:
personally I don't believe that any kernel makes that much of a difference in real-life normal usage.
Click to expand...
Click to collapse
Not something i'd agree with since CPU governors and I/O schedulers can make allot of difference to "real life normal usage", obviously this depends on what the developer impliments and user choice.
there are times that I'll run elementalx kernel, but I ALWAYS change the governor and scheduler. always. as I can't stand the way that its set up. personally, I always use ondemand with deadline :angel:
daddylok said:
I'm a newbie and my phone is at Marshmallow 6.0.1, rooted with Nexus Root Toolkit su (with SuperSU 2.62)
later flashed twrp, now want to install ElementalX Kernel.
Do I need to unroot the system, and then flash the kernel with twrp?
thanks in advance.
Click to expand...
Click to collapse
Wondering how you achieved root.I am unable using the stock kernel.TWRP installed just fine.Do you mind sharing your procedure?
Download SuperSU v2.62-3 (you can try later versions, but some people have reported that they don't work for them - v2.62 works fine for me and many others). http://forum.xda-developers.com/showpost.php?p=64161125
Copy the zip file to a folder in your Nexus 6 - say, Downloads, it doesn't really matter which one.
Boot into TWRP. Press Install. Navigate to the folder where the SuperSU zip file is and select it. Swipe in TWRP to install it. DO NOT accept any offer from TWRP to root your device (again) - you'll break it. Once installed, just reboot system. Done.
To install elementalx, just flash in recovery.
dahawthorne said:
And why do you specifically want to install Elementalx? If you've got a working rooted phone, why continue to mess with it? Continual unnecessary tweaking is the sure way to end up with a glass-and-metal paperweight...
Click to expand...
Click to collapse
Silliness. Why are you even on xda with that attitude? He probably wants to install it so he can use some of the added features and enhancements.
"Why are you even on xda with that attitude?" Ditto. We're all entitled to our opinions, and my opinion is that a lot of noobs do stuff just to see what happens, and the result is that they're in forums asking after the event "How do I fix this?" rather than "How do I do this?", and in both cases without any particular need or reason or understanding of what they want. And this is a typical thread - an admitted noob wants to install a specific kernel, and still hasn't said why (though he/she has thanked me, which I appreciate ). I think that to warn noobs about unnecessary tinkering is doing them a service - isn't that why we all respond to questions?
dahawthorne said:
Download SuperSU v2.62-3 (you can try later versions, but some people have reported that they don't work for them - v2.62 works fine for me and many others). http://forum.xda-developers.com/showpost.php?p=64161125
Copy the zip file to a folder in your Nexus 6 - say, Downloads, it doesn't really matter which one.
Boot into TWRP. Press Install. Navigate to the folder where the SuperSU zip file is and select it. Swipe in TWRP to install it. DO NOT accept any offer from TWRP to root your device (again) - you'll break it. Once installed, just reboot system. Done.
Click to expand...
Click to collapse
Thanks very much -so to be clear that was with the Stock kernel?
I am running 3.10.40-g557ba38
Trying to avoid a brick situation,sorry to be a bother..
Yes, stock kernel. As I understand it, the SuperSU backs up and replaces the stock kernel (as part of the boot image) and will restore it if you unroot. You just need to follow the instructions as written - it's exactly what I did on my stock 6.0.1 ROM.
Awesome thanks again.
dahawthorne said:
Yes, stock kernel. As I understand it, the SuperSU backs up and replaces the stock kernel (as part of the boot image) and will restore it if you unroot. You just need to follow the instructions as written - it's exactly what I did on my stock 6.0.1 ROM.
Click to expand...
Click to collapse
Thanks again-this worked out perfectly and I am running Cyanide which has made me very happy so far.REALLY fast and smooth.Everything working great so far.Loving my N6- who needs Samsung! I just had to edit the .xml file for the Music volume other than that the ROM seems about perfect.
I updated my N6 when I got it a few weeks ago, then unlocked loader, installed TWRP and rooted with NRT.
I am pretty darn happy with the way everything works as it is right now.
Yesterday, my phone downloaded the April update and prompted me to install it.
As I understand, you must flash factory and unroot to take the updates.
That said, is there any overwhelming reason to go through all that for (what seems) a minor update?
I am tempted to just wait for N to be finalized and flash the new image once available and "keep on keeping on."
A lot of you are worlds more experienced than I am and I am interested in your opinions.
Should I or shouldn't I?
TIA.
There are security updates... If you want them or not is up to you.
What I and many others do (rooted, TWRP, custom kernel) is to use the latest factory image and update by flashing individual parts of it through fastboot. In the update from march to april (MMB29V to MOB30D) I only flashed boot.img, radio.img and system.img. The rest was untouched or I didn't want to update it (i.e. custom recovery).
Check out this thread: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Follow that to set up your workspace and follow method 2 when flashing. Only flash the parts you want, but always leave out userdata.img unless you want to wipe your data. Also skip the factory reset in the end...
You will need to reroot when done, but that is just a matter of booting into TWRP (and that you should do anyway) and flashing the SuperSU zip.
nunjabusiness said:
... I am interested in your opinions...
Click to expand...
Click to collapse
There is a thread of Danvdh. He makes a Stock lite ROM after every update incl. root access.
Now you have TWRP you could monthly download and flash the new lite ROM.
NLBeev said:
There is a thread of Danvdh. He makes a Stock lite ROM after every update incl. root access.
Now you have TWRP you could monthly download and flash the new lite ROM.
Click to expand...
Click to collapse
Interesting idea. I am encrypted too, does that matter?
NLBeev said:
There is a thread of Danvdh. He makes a Stock lite ROM after every update incl. root access.
Now you have TWRP you could monthly download and flash the new lite ROM.
Click to expand...
Click to collapse
i am using Danvdh's Stock Lite ROM MMB29X. he has not updated to MOB30D. now say if i wanted MOB30D can i do the below steps?
flashing individual parts of it through fastboot
flashed boot.img, radio.img and system.img.
No reason at all.....its like saying you have some pirated version on Windows 10 and you would have to reinstall windows 8.1 to take a 19kb security patch. We have been running these OS with intentional security breaches (root) for many years..... Y start to worry about it now?
Additionally there will probably never again be a feature released that would necessitate such drastic measures. IMO.....sall incremental anymore.
so your opinion is to just roll with Danvdh's updates as they come?
iluvatrix said:
i am using Danvdh's Stock Lite ROM MMB29X. he has not updated to MOB30D. now say if i wanted MOB30D can i do the below steps?
flashing individual parts of it through fastboot
flashed boot.img, radio.img and system.img.
Click to expand...
Click to collapse
There only a few changes (bootloader, modem).
Better wait for the May update of Danvdh.
I think you can flash the new boot, radio and system. But that includes the bloatware that Danvdh will remove.