Friends--I'm not a noob, but I'm confused.
I just updated by phone to the newest image by fastboot flashing vendor, system, boot.
how, in this situation, do i obtain root? Or is that impossible if I am on 6.0.1?
Sorry...still trying to conceptually understand the root situation in marshmallow.
After that, I flashed chainfire's latest SuperSu 2.60 in TWRP and it auto-patched the files for root. Now I'm on systemless root and on the newest firmware.
Sent from my Nexus 6P using Tapatalk
caifan said:
After that, I flashed chainfire's latest SuperSu 2.60 in TWRP and it auto-patched the files for root. Now I'm on systemless root and on the newest firmware.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Can you tell me how to update trough fastboot without erasing everything? I mean, what are the commands? Thank you in advance.
GKti22 said:
Can you tell me how to update trough fastboot without erasing everything? I mean, what are the commands? Thank you in advance.
Click to expand...
Click to collapse
These are the commands https://i.imgur.com/P3QOfxU.png
If only there was a guide for you. Please check the general forum.
"i'm not a noob"
yet you do not know how to perform a basic search
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
FOR THE MAGIC SEE ITEM #9!!
caifan said:
After that, I flashed chainfire's latest SuperSu 2.60 in TWRP and it auto-patched the files for root. Now I'm on systemless root and on the newest firmware.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I did the same, but it causes the camera not to work since it installs a 6.0.0 kernel. Plus, I lost root and had to reflash SuperSu in TWRP every time I rebooted.
geoff5093 said:
I did the same, but it causes the camera not to work since it installs a 6.0.0 kernel. Plus, I lost root and had to reflash SuperSu in TWRP every time I rebooted.
Click to expand...
Click to collapse
Same here camera just shows shutter icon but no screen. This is most probably because of we're flashing 6.0.0's k modified image not latest kernel with modifications. We hope chain fire updates kernel asap
OsmDroid said:
Same here camera just shows shutter icon but no screen. This is most probably because of we're flashing 6.0.0's k modified image not latest kernel with modifications. We hope chain fire updates kernel asap
Click to expand...
Click to collapse
this. you cannot use the 6.0.0 kernel on the 6.0.1 build.
SuperSU 2.61 which is sytemless works fine on the stock 6.0.1 kernel.
I flashed the latest update last night via fastboot. let the phone boot up, then flashed 2.61 SuperSU (did not install a modified boot.img). this morning i installed elementalx which was updated for 6.0.1
Last week I finally unlocked my bootloader, rooted using BETA-SuperSU-v2.52.zip. Could I get some help/instructions on how to flash the new 6.0.1 and retain my root (as well as making sure my camera works)? I just want to make sure I don't brick my phone.
steveo17 said:
this. you cannot use the 6.0.0 kernel on the 6.0.1 build.
SuperSU 2.61 which is sytemless works fine on the stock 6.0.1 kernel.
I flashed the latest update last night via fastboot. let the phone boot up, then flashed 2.61 SuperSU (did not install a modified boot.img). this morning i installed elementalx which was updated for 6.0.1
Click to expand...
Click to collapse
Do you confirm that systemless root works on stock kernel without any problems of camera or loosing root after reboot or any such ?! It it works flawless then i am ready to install some stuff on 6.0.1
---------- Post added at 09:06 PM ---------- Previous post was at 08:54 PM ----------
steveo17 said:
this. you cannot use the 6.0.0 kernel on the 6.0.1 build.
SuperSU 2.61 which is sytemless works fine on the stock 6.0.1 kernel.
I flashed the latest update last night via fastboot. let the phone boot up, then flashed 2.61 SuperSU (did not install a modified boot.img). this morning i installed elementalx which was updated for 6.0.1
Click to expand...
Click to collapse
OsmDroid said:
Do you confirm that systemless root works on stock kernel without any problems of camera or loosing root after reboot or any such ?! It it works flawless then i am ready to install some stuff on 6.0.1
Click to expand...
Click to collapse
Fk i was searching for proper method for perfect root and chain fire gave it since he released 2.61 all i had to do is to just read whole post. Even Chainfire confirms
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
steveo17 said:
this. you cannot use the 6.0.0 kernel on the 6.0.1 build.
SuperSU 2.61 which is sytemless works fine on the stock 6.0.1 kernel.
I flashed the latest update last night via fastboot. let the phone boot up, then flashed 2.61 SuperSU (did not install a modified boot.img). this morning i installed elementalx which was updated for 6.0.1
Click to expand...
Click to collapse
*dumbass question*
DO you lose any data doing so ?
I want to update to 6.0.1 +root but I'm lazy af if I need to reinstall all my ****
kauemelhado said:
*dumbass question*
DO you lose any data doing so ?
I want to update to 6.0.1 +root but I'm lazy af if I need to reinstall all my ****
Click to expand...
Click to collapse
no, you do not lose any data via fastboot so long as you do not flash the data portion.
---------- Post added at 12:35 PM ---------- Previous post was at 12:35 PM ----------
OsmDroid said:
Do you confirm that systemless root works on stock kernel without any problems of camera or loosing root after reboot or any such ?! It it works flawless then i am ready to install some stuff on 6.0.1
---------- Post added at 09:06 PM ---------- Previous post was at 08:54 PM ----------
Fk i was searching for proper method for perfect root and chain fire gave it since he released 2.61 all i had to do is to just read whole post. Even Chainfire confirms
]
Click to expand...
Click to collapse
yes, i simply installed supersu 2.61 after updating to 6.0.1 and it worked flawlessly
steveo17 said:
no, you do not lose any data via fastboot so long as you do not flash the data portion.
---------- Post added at 12:35 PM ---------- Previous post was at 12:35 PM ----------
yes, i simply installed supersu 2.61 after updating to 6.0.1 and it worked flawlessly
Click to expand...
Click to collapse
So,
If I need to instal the update + root + ex kernel...
First I'll flash de update without the data partition (via adb), then I'll flash the kernel and then supersu 2.61, right? :silly:
kauemelhado said:
So,
If I need to instal the update + root + ex kernel...
First I'll flash de update without the data partition (via adb), then I'll flash the kernel and then supersu 2.61, right? :silly:
Click to expand...
Click to collapse
no. see below
1. The update will be flashed via Fastboot via these steps
These steps assume the files are in C:\angler\images, but you can also drag and drop into terminal or command prompt.
If you have not done this before, be careful to do these exactly as follows or else you will have to factory reset (and lose data).
also, you will download the factory image, extract once, and then extract the zip within it to find the cache, recovery, system, vendor, etc...)
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
2. Flash TWRP via Fastboot
Fastboot flash recovery "TWRP"
3. Reboot to Recovery
4. Install SuperSU 2.61
5. Install ElementalX
6. Install Xposed
steveo17 said:
no. see below
1. The update will be flashed via Fastboot via these steps
These steps assume the files are in C:\angler\images, but you can also drag and drop into terminal or command prompt.
If you have not done this before, be careful to do these exactly as follows or else you will have to factory reset (and lose data).
also, you will download the factory image, extract once, and then extract the zip within it to find the cache, recovery, system, vendor, etc...)
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
2. Flash TWRP via Fastboot
Fastboot flash recovery "TWRP"
3. Reboot to Recovery
4. Install SuperSU 2.61
5. Install ElementalX
6. Install Xposed
Click to expand...
Click to collapse
Hmm, so I need to re-flash TWRP =(
Thank you bro :victory::good:
kauemelhado said:
Hmm, so I need to re-flash TWRP =(
Thank you bro :victory::good:
Click to expand...
Click to collapse
honestly i am not sure if the factory recovery needs to be flashed, i just did because that's what people said worked in the past.
only takes a few seconds to flash TWRP again
steveo17 said:
honestly i am not sure if the factory recovery needs to be flashed, i just did because that's what people said worked in the past.
only takes a few seconds to flash TWRP again
Click to expand...
Click to collapse
Better safe than sorry, right? hehehe
Thank you!!
If you have encryption disabled, will flashing 6.0.1 change it to encrypted?
ShaunWinSC said:
If you have encryption disabled, will flashing 6.0.1 change it to encrypted?
Click to expand...
Click to collapse
I had some difficulty coming from stock, rooted and unencrypted. I manually flashed the images then went straight into twrp and flashed su 2.61. Using this method I was still unencrypted but I lost root upon every reboot. I then reflashed the images and booted into system before flashing supersu. During that boot it encrypted my data partition. I then flashed twrp then supersu 2.61 and now my root sticks. I don't know if the issue was being unencrypted but just wanted to give a heads up and hopefully someone else can chime in.
Related
***For US LTE Tablet***
Here is a .zip you can flash to update to 5.0.1 from 5.0. The OTA was pulled from my device which I factory reset to 4.4.4. It will remove root and it will reflash the stock recovery, but it will NOT relock your bootloader. Make backups! Flash at your own risk! I am not responsible for any damage that occurs.
The reason why the new 5.0.1 OTA does not flash for rooted users is a sha1 hash is generated from the system partition. If it doesn't match what the hash should be from the factory, it fails out. Removing these checks will break your device because of the new differential update method employed, which is why these sha1 hashes are so important. The .zip I have is a standard update (not differential) and can be flashed with any recovery you want
Here is a link:
https://drive.google.com/file/d/0B_iRndxSfhpXRjBXY3FXUG1tNDA/view?usp=sharing
Thanks for your explanation! Any chance for providing the same zip for eu lte?
So is this a modified zip or is it just the full version from nvidia's server?
The rest of the world - LTE - version of the 5.0.1 update is here:
http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_un_do-full_ota-29082_493.9700.zip
Flashed fine with ClockworkMod Recovery.
If you were rooted, you need to re-root afterwards.
any zip for wifi only tablet?
Adrixan said:
The rest of the world version of the 5.0.1 update is here:
http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_un_do-full_ota-29082_493.9700.zip
Flashed fine with ClockworkMod Recovery.
If you were rooted, you need to re-root afterwards.
Click to expand...
Click to collapse
I need a little help how to flash via CWM and if i flash it will my data be erased? Plus how to reroot once i update? I have root and unlocked bootloader running 5.0
What do you have to do to root after installing this?
RollWii said:
I need a little help how to flash via CWM and if i flash it will my data be erased? Plus how to reroot once i update? I have root and unlocked bootloader running 5.0
Click to expand...
Click to collapse
It did not reset my tablet, just like an OTA update should.
You will lose root and the custom recovery though.
To get it back, just follow the fine guide in the forum again: http://forum.xda-developers.com/shield-tablet/development/recovery-cwm-recovery-nvidia-shield-t2848064
---------- Post added at 07:44 AM ---------- Previous post was at 07:43 AM ----------
TheCrowing said:
What do you have to do to root after installing this?
Click to expand...
Click to collapse
You just have to reinstall the custom recovery as detailed in the forum thread: http://forum.xda-developers.com/shield-tablet/development/recovery-cwm-recovery-nvidia-shield-t2848064 and from there flash SuperSU again.
Adrixan said:
It did not reset my tablet, just like an OTA update should.
You will lose root and the custom recovery though.
To get it back, just follow the fine guide in the forum again: http://forum.xda-developers.com/shield-tablet/development/recovery-cwm-recovery-nvidia-shield-t2848064
---------- Post added at 07:44 AM ---------- Previous post was at 07:43 AM ----------
You just have to reinstall the custom recovery as detailed in the forum thread: http://forum.xda-developers.com/shield-tablet/development/recovery-cwm-recovery-nvidia-shield-t2848064 and from there flash SuperSU again.
Click to expand...
Click to collapse
So basically all i need to do is
1) install cwm again since i updated to lollipop and have root
2) downlaod the update and install via cwm
3) reroot using the root.img etc etc and flash super su etc etc
4) reinstall cwm
Am i going the right path?
RollWii said:
So basically all i need to do is
1) install cwm again since i updated to lollipop and have root
2) downlaod the update and install via cwm
3) reroot using the root.img etc etc and flash super su etc etc
4) reinstall cwm
Am i going the right path?
Click to expand...
Click to collapse
What I did:
I WAS on 5.0 already! I don't know, if you can go directly from a KitKat release to 5.0.1!
1) Reboot recovery and flash zip like any other
2) Reboot normally, root will be lost. Don't restore root, when CWM asks you to.
3) reboot into fastboot mode
4) fastboot flash recovery recovery.img with the recovery.img from the thread, mentioned above
5) boot into recovery mode
6) flash the SuperSU update zip
7) reboot again, when cwm asks to fix root access, select yes this time
8) have a rooted shield on 5.0.1
Adrixan said:
What I did:
I WAS on 5.0 already! I don't know, if you can go directly from a KitKat release to 5.0.1!
1) Reboot recovery and flash zip like any other
2) Reboot normally, root will be lost. Don't restore root, when CWM asks you to.
3) reboot into fastboot mode
4) fastboot flash recovery recovery.img with the recovery.img from the thread, mentioned above
5) boot into recovery mode
6) flash the SuperSU update zip
7) reboot again, when cwm asks to fix root access, select yes this time
8) have a rooted shield on 5.0.1
Click to expand...
Click to collapse
Ok so its the same process like when i updated from kitkat to lollipop. One last question do i need to use the boot.img again?
RollWii said:
Ok so its the same process like when i updated from kitkat to lollipop. One last question do i need to use the boot.img again?
Click to expand...
Click to collapse
I never came into a situation, where i had to use some extra boot.img.
When I got my shield recently, I directly updated to 5.0 before rooting and only did the update to 5.0.1 with a previously rooted device.
So, I'd assume, if you are on 5.0 rooted, my instructions should work for you.
And careful, as mentioned above, my link is for the Rest of the world LTE version! (not us!)
Adrixan said:
I never came into a situation, where i had to use some extra boot.img.
When I got my shield recently, I directly updated to 5.0 before rooting and only did the update to 5.0.1 with a previously rooted device.
So, I'd assume, if you are on 5.0 rooted, my instructions should work for you.
And careful, as mentioned above, my link is for the Rest of the world LTE version! (not us!)
Click to expand...
Click to collapse
Oh good that you mentionedim using US Unlocked LTE so your file wont work on mine?
RollWii said:
Oh good that you mentionedim using US Unlocked LTE so your file wont work on mine?
Click to expand...
Click to collapse
No, but the File from the guy, who started this thread should work for the U.S. LTE version following the same instructions as I just gave.
How long should it be sitting at the NVIDIA screen after flashing the update?
It went after a couple minutes.
Adrixan said:
What I did:
I WAS on 5.0 already! I don't know, if you can go directly from a KitKat release to 5.0.1!
1) Reboot recovery and flash zip like any other
2) Reboot normally, root will be lost. Don't restore root, when CWM asks you to.
3) reboot into fastboot mode
4) fastboot flash recovery recovery.img with the recovery.img from the thread, mentioned above
5) boot into recovery mode
6) flash the SuperSU update zip
7) reboot again, when cwm asks to fix root access, select yes this time
8) have a rooted shield on 5.0.1
Click to expand...
Click to collapse
sorry but i forgot how to flash the SUperSU update.zip how and where can i find it again?
The hot new security update is live, and you maybe want some root love without flashing custom kernel.
(Stock Image here : https://developers.google.com/android/nexus/images#volantis)
Handy modified root compatible boot image for the latest stock image MRA58N. Pure stock kernel modified from the stock images.
You have two choices:
The traditional root in system, which breaks OTA functionality.
(It's more stable now)
New "systemless" approach, which means the root stuffs are only in DATA and BOOT, the system will stay intact and it will accept OTAs.
(Note that this method is still in beta stage according to CF)
Instructions:
System:
Unzip system-root.zip, flash the boot.img through fastboot
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the one above), if you've rooted with other methods, please re-flash your system back to pure stock
Unzip systemless-root.zip, flash the boot.img through fastboot
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
When a new OTA appears I can just apply it and it will work? Do I keep root or do I have to reroot it again?
Are the attached zip files for the wifi model only?
I have this Kernel:
3.10.40-g909db78
[email protected] #1
Fri Aug 28 21:16:30 UTC 2015
Is this a stock one?
And with method shall I use to get rooted MRA58N?
Jeltel said:
When a new OTA appears I can just apply it and it will work? Do I keep root or do I have to reroot it again?
Click to expand...
Click to collapse
You can revert to stock boot and stock recovery to apply OTA
corkiejp said:
Are the attached zip files for the wifi model only?
Click to expand...
Click to collapse
Yes, I can make a LTE compatible version though.
sejmand said:
I have this Kernel:
3.10.40-g909db78
[email protected] #1
Fri Aug 28 21:16:30 UTC 2015
Is this a stock one?
And with method shall I use to get rooted MRA58N?
Click to expand...
Click to collapse
Yes, and yes
topjohnwu said:
You can revert to stock boot and stock recovery to apply OTA
Yes, I can make a LTE compatible version though.
Yes, and yes
Click to expand...
Click to collapse
A LTE compatible version would be great!!!
topjohnwu said:
You can revert to stock boot and stock recovery to apply OTA
Click to expand...
Click to collapse
So that's a no
I flashed factory image MRA58N (system gets encrypted, because it wasn't under MRA58K)
then twrp
then systemless-root (boot.img)
then superuser 2.56.....
EVERYTHING WORKS FINE:
encrypted with root!
how to flash boot.img (command for flashing)
topjohnwu said:
The hot new security update is live, and you maybe want some root love without flashing custom kernel.
(Stock Image here : https://developers.google.com/android/nexus/images#volantis)
Handy modified root compatible boot image for the latest stock image MRA58N. Pure stock kernel modified from the stock images.
You have two choices:
The traditional root in system, which breaks OTA functionality.
(It's more stable now)
New "systemless" approach, which means the root stuffs are only in DATA and BOOT, the system will stay intact and it will accept OTAs.
(Note that this method is still in beta stage according to CF)
Instructions:
System:
Unzip system-root.zip, flash the boot.img through fastboot
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the one above), if you've rooted with other methods, please re-flash your system back to pure stock
Unzip systemless-root.zip, flash the boot.img through fastboot
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
Click to expand...
Click to collapse
how to flash boot.img for system less (partition ?)
Lightnyboy said:
how to flash boot.img for system less (partition ?)
Click to expand...
Click to collapse
Unzip systemless-root.zip which will give you a "boot.img" file.
Then while in fastboot
"fastboot flash boot boot.img"
Anyone have the boot files for LTE yet?
Nice. Could you add the link to CF original post in systemless root.
thebrainkafka said:
Nice. Could you add the link to CF original post in systemless root.
Click to expand...
Click to collapse
topjohnwu said:
[*]Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
[*]Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
Click to expand...
Click to collapse
Already linked? Click on "this thread" above!
Updated for LTE... Sorry for the late update.
Also looks like rovo89 just put up xposed for marshmallow in his xposed for lollipop thread. Yes!
xposed marshmallow
topjohnwu said:
Updated for LTE... Sorry for the late update.
Click to expand...
Click to collapse
Thanks for the modified boot images for LTE, I linked back here from my thread in Q&A forum.
have problems getting it to work...
am on MRA58N stock.
My exact steps.
adb reboot bootloader
Device reboots to bootloader.
fastboot flash boot boot.img (extracted from volantisg-mra58n-boot-systemless.zip)
fastboot boot twrp.img (extracted from https://dl.twrp.me/flounder/twrp-2.8.7.1-flounder.img)
From here, I manage to get into TWRP but they are asking for a PIN. I had to cancel and mounted an external USB storage and manage to flash SuperSU-v2.56-20151030013730.zip successfully. Rebooting after and not installing the the SuperSU that TWRP prompts.
After rebooting, I still don't have root. What did I do wrong?
madbat99 said:
Also looks like rovo89 just put up xposed for marshmallow in his xposed for lollipop thread. Yes!
xposed marshmallow
Click to expand...
Click to collapse
I haven't run N version yet as my N9 is finally working without lags/reboots. But, the lure of the close all recent apps button (and very successful experience with xposed/gravity box on N5 after a year) in GB was too great. It works beautifully!
This may seem off-topic, but since root is required, maybe readers can allow exception.
Sent from my Nexus 9 using Tapatalk
chesterchen said:
have problems getting it to work...
am on MRA58N stock.
My exact steps.
adb reboot bootloader
Device reboots to bootloader.
fastboot flash boot boot.img (extracted from volantisg-mra58n-boot-systemless.zip)
fastboot boot twrp.img (extracted from https://dl.twrp.me/flounder/twrp-2.8.7.1-flounder.img)
From here, I manage to get into TWRP but they are asking for a PIN. I had to cancel and mounted an external USB storage and manage to flash SuperSU-v2.56-20151030013730.zip successfully. Rebooting after and not installing the the SuperSU that TWRP prompts.
After rebooting, I still don't have root. What did I do wrong?
Click to expand...
Click to collapse
You don't need to extract twrp.img, you should flash the full image "twrp-2.8.7.1-flounder.img".
That version should not ask for PIN anymore.
Note: system-less is still experimental
If I want to switch from the systemless root to regular system modified root, are there specific cleanup actions to take?
Thanks!
maximumentropy said:
If I want to switch from the systemless root to regular system modified root, are there specific cleanup actions to take?
Thanks!
Click to expand...
Click to collapse
Reflash the stock image then you're good
Please post below when you got the OTA and what carrier you're on!
I always love to watch how the OTA's hit peoples devices. From where they're located to what carrier they're on, its interesting to see who gets it first and sadly last.
I am stock, MDB08L 6.0.0, T-Mobile US. The wait begins.
Here we go again! People *****ing about updates!
Hahaha [emoji23]
Sent from my Nexus 5X using Tapatalk
Updated via fastboot. Root + xposed work just fine
mymusicathome said:
Updated via fastboot. Root + xposed work just fine
Click to expand...
Click to collapse
Which type of root and which boot image are you using?
mymusicathome said:
Updated via fastboot. Root + xposed work just fine
Click to expand...
Click to collapse
Did you wipe your data of did you just flash the system?
kbbeer said:
Which type of root and which boot image are you using?
Click to expand...
Click to collapse
Chainfire systemless boot+root
Alaris said:
Did you wipe your data of did you just flash the system?
Click to expand...
Click to collapse
Nope. Flashed everything but userdata
Thinking about manually flashing this since I'm rooted on the modified boot.img.
What steps do I need to take? Unroot then flash everything then reflash modified boot then reroot?
Flash bootloader, radio, boot, cache, system, vendor and then systemless root boot. No need to unroot. Flashing the OEM boot might not be needed but I do it anyway. I boot into Android and then boot to recovery and flash superuser
good 6.0.1 factory image flash-all install
Sent from my Nexus 5X using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
antiseen said:
Thinking about manually flashing this since I'm rooted on the modified boot.img.
What steps do I need to take? Unroot then flash everything then reflash modified boot then reroot?
Click to expand...
Click to collapse
I flashed using the flash-all.bat script. Deleted "-w" from the script to get rid of the data wipe. Reinstalled TWRP and re-rooted using the traditional root method. I used the modified boot image for MDB08M.
windows8k said:
good 6.0.1 factory image flash-all install
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Niceeee
ING3NIEUR said:
I flashed using the flash-all.bat script. Deleted "-w" from the script to get rid of the data wipe. Reinstalled TWRP and re-rooted using the traditional root method. I used the modified boot image for MDB08M.
Click to expand...
Click to collapse
How did you get the flash-all.bat script to work? It never did for me.. Do you have to get bootloader unlocked?
Encrypted11 said:
How did you get the flash-all.bat script to work? It never did for me.. Do you have to get bootloader unlocked?
Click to expand...
Click to collapse
Yes. Beware, doing so will wipe your phone.
Sent from my Nexus 5X using Tapatalk
Encrypted11 said:
How did you get the flash-all.bat script to work? It never did for me.. Do you have to get bootloader unlocked?
Click to expand...
Click to collapse
Bootloader must be unlocked. It's even in the flashing instructions on the Factory Images download page.
---------- Post added at 06:38 PM ---------- Previous post was at 06:29 PM ----------
PiousInquisitor said:
Yes. Beware, doing so will wipe your phone.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
No wipe if you delete "-w" from the script.
PiousInquisitor said:
Here we go again! People *****ing about updates!
Click to expand...
Click to collapse
He wasn't *****ing at all.
I'm on Telus but I bought it from the google store so carrier-free. no OTA yet, currently on build MDB08L. Please hurry googs, I want the new emoji
ING3NIEUR said:
Bootloader must be unlocked. It's even in the flashing instructions on the Factory Images download page.
---------- Post added at 06:38 PM ---------- Previous post was at 06:29 PM ----------
No wipe if you delete "-w" from the script.
Click to expand...
Click to collapse
I was warning him about unlocking the bootloader.
Just updated via fastboot and regular root using BETA SuperSU 2.52 with the modified boot.img from the MDB08I/MDB08M builds and everything was working well but I just now noticed my camera shows a black screen. Rebooting didn't help so I'm wiping cache in TWRP and if that doesn't work going to redownload and reflash the images.
Edit: Seems to be an issue with using the old modified boot image from MDB08I/MDB08M for root from Chainfire, exploring now....
Edit 2: Just loaded the boot.img from the MMB29K build but now it seems like I'm in a bootloop. Going to reflash everything again to confirm it's the modified boot.img from MDB08I/MDB08M causing the camera not to work.
Edit 3: Reflashed System and Boot from MMB29K build which obviously removes system root but the Camera is working again. Looks like we will need a modified boot.img from the MMB29K build for system root to work.
ING3NIEUR said:
I flashed using the flash-all.bat script. Deleted "-w" from the script to get rid of the data wipe. Reinstalled TWRP and re-rooted using the traditional root method. I used the modified boot image for MDB08M.
Click to expand...
Click to collapse
I manually flashed everything, but essentially the same process. I also used the 8m modified boot.img
I haven't done a factory reset yet but I would love to avoid it if possible.
I went to take a picture of the wife's newly decorated Christmas tree and the stock camera fails to fully start. It behaves as if it can not use the hardware. When I look at the back there is a small red light/laser that refuses to go out unless the phone is rebooted.
I've rebooted the phone a few times and tried Manual Camera and a couple others .. same behavior.
The phone is running 6.0.1 and is rooted.
Anyone seeing this and have any ideas?
Are you using the stock kernel
I am having the same problem. I flashed with the factory image and the camera won't work in any apps. Stock camera, Snapchat, Instagram, etc. Flashlight had not been working from the Quick Settings tiles, but it did work after wiping cache and dalvik in TWRP.
I saw someone mention on reddit that it can be an issue with using NRT to flash (I didn't use it) and something about vendor.img. I reflashed vendor.img and it didn't change anything.
SuperSmashedBro said:
Are you using the stock kernel
Click to expand...
Click to collapse
Yep. With the exception of being rooted and using a few utils like root explorer and recently ... nothing special. I did just notice Google Play Services *****ed and said there was an error but it wasn't specific about the error. I did bounce the cache for Google Play Services after seeing that.
Nothing odd about this phone ... it's been top notch for the last month.
fury683 said:
I am having the same problem. I flashed with the factory image and the camera won't work in any apps. Stock camera, Snapchat, Instagram, etc. Flashlight had not been working from the Quick Settings tiles, but it did work after wiping cache and dalvik in TWRP.
I saw someone mention on reddit that it can be an issue with using NRT to flash (I didn't use it) and something about vendor.img. I reflashed vendor.img and it didn't change anything.
Click to expand...
Click to collapse
I wonder if it's the vendor.img that caused this. Hmm.. I wonder if the vendor.img from 6.0 would sort it. hmm.
aergern said:
I wonder if it's the vendor.img that caused this. Hmm.. I wonder if the vendor.img from 6.0 would sort it. hmm.
Click to expand...
Click to collapse
I am trying a reflash of the factory image again. Will try out the camera upon first boot before proceeding with TWRP/root/Xposed. It's optimizing my apps right now, I'll let you know in a minute.
---------- Post added at 08:49 PM ---------- Previous post was at 08:45 PM ----------
Full reflash (without wiping userdata) with factory image seems to have worked... Now to try proceeding one step at a time with TWRP/root/Xposed to see if it breaks again.
fury683 said:
I am trying a reflash of the factory image again. Will try out the camera upon first boot before proceeding with TWRP/root/Xposed. It's optimizing my apps right now, I'll let you know in a minute.
Click to expand...
Click to collapse
Yeah, I tried flashing the 6.0 vendor.img and Manual Camera started and I got visual but it froze. I did get a complaint that something was wrong with my system. So I'm trying the 6.0.1 vendor.img. Let me know what you find.
I had this issue on 6.0 when I was trying to do systemless root. I was given boot.img options that were modified (L, M and N) L didn't allow root, N borked the camera, M worked. I would think it's the boot.img
aergern said:
Yeah, I tried flashing the 6.0 vendor.img and Manual Camera started and I got visual but it froze. I did get a complaint that something was wrong with my system. So I'm trying the 6.0.1 vendor.img. Let me know what you find.
Click to expand...
Click to collapse
No dice. Reflashing the 6.0.1 vendor.img did squat. I'll wait.
darkamikaze said:
I had this issue on 6.0 when I was trying to do systemless root. I was given boot.img options that were modified (L, M and N) L didn't allow root, N borked the camera, M worked. I would think it's the boot.img
Click to expand...
Click to collapse
So reflashing the system.img and waiting for Chainfire to make a new boot image could be the solution. That kinda sucks but it could be the only solution.
darkamikaze said:
I had this issue on 6.0 when I was trying to do systemless root. I was given boot.img options that were modified (L, M and N) L didn't allow root, N borked the camera, M worked. I would think it's the boot.img
Click to expand...
Click to collapse
I am using the "traditional" root method and used the angler-mdb08k-boot.zip by Chainfire, which is what I have used before.
fury683 said:
I am using the "traditional" root method and used the angler-mdb08k-boot.zip by Chainfire, which is what I have used before.
Click to expand...
Click to collapse
Same here. Using the same root method each time with my Nexus 6 was never an issue.
Damn. hmm.
Using a 6.0 boot.img or kernel will break the camera on 6.0.1. You can use the new supersu 2.61 on the new 6.0.1 update and root works fine and so does the camera
edd247 said:
Using a 6.0 boot.img or kernel will break the camera on 6.0.1. You can use the new supersu 2.61 on the new 6.0.1 update and root works fine and so does the camera
Click to expand...
Click to collapse
Oh. So just flash supersu 2.61 instead of using the boot.img and supersu 2.5x method. Good. I'll give that a whirl.
I just used the 2.61 systemless root and it appears to be working OK. I just flashed Xposed and am rebooting (optimizing apps for the 3rd time tonight...). Process is pretty painless.
Flash factory image (my batch file was modified to NOT wipe userdata (-w removed))
Flash TWRP
Install SuperSU 2.61 from TWRP --- DO NOT INSTALL ROOT FROM TWRP IF/WHEN IT ASKS
---------- Post added at 09:31 PM ---------- Previous post was at 09:19 PM ----------
Xposed installed and it all seems to work OK.
fury683 said:
I just used the 2.61 systemless root and it appears to be working OK. I just flashed Xposed and am rebooting (optimizing apps for the 3rd time tonight...). Process is pretty painless.
Flash factory image (my batch file was modified to NOT wipe userdata (-w removed))
Flash TWRP
Install SuperSU 2.61 from TWRP --- DO NOT INSTALL ROOT FROM TWRP IF/WHEN IT ASKS
---------- Post added at 09:31 PM ---------- Previous post was at 09:19 PM ----------
Xposed installed and it all seems to work OK.
Click to expand...
Click to collapse
I just erased and reflashed each partition except userdata so it's doing it's thing. Once it's back up then I'll just use 2.61 and be done with it.
Thanks. Just hope I don't have to look at the boot animation much longer ...
Anyone try the modified MMB29N boot.img thats on the Unlock/Root/Flash Guide to see if it breaks the camera while rooting traditionally?
fury683 said:
I just used the 2.61 systemless root and it appears to be working OK. I just flashed Xposed and am rebooting (optimizing apps for the 3rd time tonight...). Process is pretty painless.
Flash factory image (my batch file was modified to NOT wipe userdata (-w removed))
Flash TWRP
Install SuperSU 2.61 from TWRP --- DO NOT INSTALL ROOT FROM TWRP IF/WHEN IT ASKS
---------- Post added at 09:31 PM ---------- Previous post was at 09:19 PM ----------
Xposed installed and it all seems to work OK.
Click to expand...
Click to collapse
I did this ...
fastboot erase system
fastboot erase cache
fastboot erase boot
fastboot erase vendor
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot reboot
Seems to be stuck at the bootloader animation ... so far .. 20 minutes? I shouldn't have to wipe userdata .. right?
captainwahid said:
Anyone try the modified MMB29N boot.img thats on the Unlock/Root/Flash Guide to see if it breaks the camera while rooting traditionally?
Click to expand...
Click to collapse
I used the only Angler boot.img in the list and it worked to root but the camera was screwed.
this one? http://forum.xda-developers.com/showpost.php?p=64004628&postcount=1195
Edit: Obsolete now. Twrp 3.0.2.1 is Out.
For now TWRP cant decrypt Android Ns vendor images so you cant flash SuperSU. So why not flash back old vendor to root the device and reflashing the NRD90M Vendor?
It works great. I root my clean install from factory image Android 7.0 NRD90M:
1. Flash the just released NRD90M via Fastboot
2. Reboot and set up your device.
3. Reboot to fastboot and flash vendor_mob30w.img by entering: fastboot flash vendor vendor_mob30w.img
4. Boot TWRP 3.0.2.0 temporary by entering: fastboot boot twrp-3.0.2-0-flounder.img
5. In TWRP copy UPDATE-SuperSU-v2.76-20160630161323.zip to your device and install it.
5.1 If you want to use adaway flash also AdAway_systemless_hosts_v2.zip.
6. Go back - back - back and reboot your device to fastboot.
7. Reflash the original vendor vendor_nrd90m.img by entering: fastboot flash vendor vendor_nrd90m.img
8. Reboot your device. Its rooted!
Extract the vendor files from the factory images or take these just extracted files from my google drive:
Download vendor_mob30w
Download vendor_nrd90m
Even though TWRP can not decrypt nexus 9 nougat.
As the final release is out, TWRP will probably be updated for it soon.
You could still use it to flash supersu from OTG or sideloading the zip. Without changing vendor image.
Alternatively there is CFAR method.
corkiejp said:
Even though TWRP can not decrypt nexus 9 nougat.
As the final release is out, TWRP will probably be updated for it soon.
You could still use it to flash supersu from OTG or sideloading the zip. Without changing vendor image.
Alternatively there is CFAR method.
Click to expand...
Click to collapse
Is that one system less?
edit: nevermind this
osnapitsjoey said:
Is that one system less?
Click to expand...
Click to collapse
Yes CFAR is systemless.
If you were not a very smart man and encrypted your device during the install will this method work? Does it allow you to take monthly security updates still?
corkiejp said:
Even though TWRP can not decrypt nexus 9 nougat.
As the final release is out, TWRP will probably be updated for it soon.
You could still use it to flash supersu from OTG or sideloading the zip. Without changing vendor image.
Alternatively there is CFAR method.
Click to expand...
Click to collapse
I don't know if what I did was right, but without changing vendor image my N9 got boot loop at TWRP welcome screen. TWRP could only run properly after flashing old vendor image.
GialanG said:
I don't know if what I did was right, but without changing vendor image my N9 got boot loop at TWRP welcome screen. TWRP could only run properly after flashing old vendor image.
Click to expand...
Click to collapse
It will bootloop and eventually load. At least that is what it did on the previews. Haven't tested on final release.
You still can not modify/read encrypted data partition, hence OTG or sideloading of zips.
Edit:- Just tested and it eventually loads.
twrp-3.0.2-1-flounder.img now available supports encrypted Nexus 9
twrp-3.0.2-1-flounder.img now available supports encrypted Nexus 9.
corkiejp said:
twrp-3.0.2-1-flounder.img now available supports encrypted Nexus 9.
Click to expand...
Click to collapse
Cool, thanks ! Is there also a way to decrypt the tablet ?
TheLonelyCyborg said:
Cool, thanks ! Is there also a way to decrypt the tablet ?
Click to expand...
Click to collapse
Make sure you have flashed latest supersu.zip which has encryption flag disabled.
Then format your data partition.
For future updates make sure to flash supersu again before booting your tablet other wise it will re-encrypt.
---------- Post added at 01:44 PM ---------- Previous post was at 01:33 PM ----------
@Donald Nice Maybe you should update the first post, now that a working TWRP is available for encrypted Nexus 9.
corkiejp said:
Make sure you have flashed latest supersu.zip which has encryption flag disabled.
Then format your data partition.
For future updates make sure to flash supersu again before booting your tablet other wise it will re-encrypt.
---------- Post added at 01:44 PM ---------- Previous post was at 01:33 PM ----------
@Donald Nice Maybe you should update the first post, now that a working TWRP is available for encrypted Nexus 9.
Click to expand...
Click to collapse
Thanks @corkiejp it worked like a charm !
Can you please update this guide?
Sent from my Nexus 9 using Tapatalk
Twrp bootloop
I stupidly updated my nexus 9 (wi-fi) to nougat which I think is awful. I flashed it via wugfresh as it was unlocked and rooted. Flashed back to 6.0.1. Trying to install twrp 3.0.2.1. It bootloops but eventually loads. I added a pin as it was the only way I could decrypt, I get the partition decrypted and then it bootloops again. Haven't been able to root. Now running 6.0.1 no root trying to install twrp 3.0.2.1. Should I just use 3.0.2.0?
lawlor059 said:
I stupidly updated my nexus 9 (wi-fi) to nougat which I think is awful. I flashed it via wugfresh as it was unlocked and rooted. Flashed back to 6.0.1. Trying to install twrp 3.0.2.1. It bootloops but eventually loads. I added a pin as it was the only way I could decrypt, I get the partition decrypted and then it bootloops again. Haven't been able to root. Now running 6.0.1 no root trying to install twrp 3.0.2.1. Should I just use 3.0.2.0?
Click to expand...
Click to collapse
Use 3.0.2-0 for Marshmallow! 3.02-1 is for nougat only.
corkiejp said:
Use 3.0.2-0 for Marshmallow! 3.02-1 is for nougat only.
Click to expand...
Click to collapse
3.0.2-1 works perfectly fine for marshmallow.
dictionary said:
3.0.2-1 works perfectly fine for marshmallow.
Click to expand...
Click to collapse
Thanks @corkiejp. @dictionary I couldn't get into the recovery with 3.0.2.1. Entering the decrypt code would just cause it to loop again. Ignoring the decrypt code I could get into the recovery but with nothing mounted it's useless. It will install successfully but nothing can be done with it.