Database Users

5.0.1 OTA for ROOTED Shield Tablets (DL Provided)

***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?

MotoX OTA Update - XT1060 Blur_Version.212.166.3.ghost_verizon.Verizon.en.US .zip

Edit: The attached zip in post #2 in a minor update the original 4.4.4 release for XT1060 FXZ. Below are the instructions. This is NOT the Full 4.4.4 OTA update.
Instructions to flash
1.) Move zip file from /cache folder to /sdcard folder if you received OTA (Zip file in 2nd post if you do not have it.)
2.) To be safe, disable xposed framework (if you have it running).
3.) Reboot into bootloader
4.) Use mfastboot to flash stock recovery (if not running it)
mfastboot flash recovery recovery.img
Click to expand...
Click to collapse
5.) Boot into recovery from bootloader
6.) Hold Power + Up Button to get recovery menu.
7.) Flash zip file from sdcard.
8.) When complete reboot, then boot into bootloader.
9.) Use mfastboot to flash custom recovery (aka twrp)
mfastboot flash recovery <twrp file name>.img
Click to expand...
Click to collapse
10.) Reboot and enable xposed framework.
11.) Done.
Another suggestion by @KidJoe
After mfastboot flash recovery <recoveryyouwant>.img its long been suggested to do a mfastboot reboot-bootloader then go into recovery, before doing anything else.
We've seen many instances where skipping the reboot-bootloader and enter recovery giving symptoms like the flash of recovery didn't work... (i.e. "old" recovery was still on the phone)
Click to expand...
Click to collapse

just received the update as well but haven't installed

Zip attached.

Maintenance update.

Maintenance update. Does not break root.

911 bug fix, as mentioned in three other threads

WhammyDroid said:
Zip attached.
Click to expand...
Click to collapse
You flash this through RSD lite? I couldn't flash it through my TWRP recovery on my Moto X Developer Edition.
Cindy

cindylike24 said:
You flash this through RSD lite? I couldn't flash it through my TWRP recovery on my Moto X Developer Edition.
Cindy
Click to expand...
Click to collapse
I believe you have to have stock recovery to flash.

dannyxiii said:
I believe you have to have stock recovery to flash.
Click to expand...
Click to collapse
Well then, I'll have to put this on my to do list for when I get home tonight. No biggie.
Cindy

It's far, far more than a 911 bug fix ... there's 2500 lines in the updater script, touching dozens (if not hundreds) of app and files.

Does this require removal of root/xposed or just needs stock recovery?

TheDave1022 said:
Does this require removal of root/xposed or just needs stock recovery?
Click to expand...
Click to collapse
I generally disable xposed and flash stock recovery but root should be fine. Anyone have a copy of the stock recovery? I'm on the dev edition. OTA's are so infrequent on this device that I forget where I stash the stock recovery all the time.

I got the notification last night, and hid it this morning (turned off notifications for the Moto Updater app). I am on an XT1060 Moto Maker, with an unlocked bootloader. In the past I've flashed /system and /recovery to update (from 4.4.2 to 4.4.4) with the OTA, then reflashed TWRP and flashed SuperSU from there. Do I need to do all that, or just stock recovery?
I do have Xposed, Cerberus and App Ops installed as System Apps, I believe.

I found the recovery for myself at the following link:
http://motofirmware.center/files/file/47-vzw_xt1060_444-kxa2112-l126_cfc_1ffxmlzip/
Might help someone else...You can verify your build by going to About phone. I had Build number KXA21.12-L1.26

Maverick0984 said:
I found the recovery for myself at the following link:
http://motofirmware.center/files/file/47-vzw_xt1060_444-kxa2112-l126_cfc_1ffxmlzip/
Might help someone else...You can verify your build by going to About phone. I had Build number KXA21.12-L1.26
Click to expand...
Click to collapse
That's the exact model number on my phone! Thank you for putting this link up there!!
Cindy

For some reason, I cannot use either mfastboot or fastboot to flash the stock recovery. When flashing it, I get the android icon with the red triangle.
Its been a while since I have had to flash back to stock recovery. What am I missing? I have the stock recoverystored for the last official FXZ.

when android with red triangle appears, press vol up for 3 seconds and you will be given option to flash from sd card.

Well, this has locked me out of re-flashing custom recovery, which - of course - means there's nothing that can be done beyond that.
Any version of TWRP up to, and including, the latest flashes without error ... but when you boot, it's still got stock recovery on it.
So no way to root, apply supersu, or do anything.
---------- Post added 3rd June 2015 at 12:04 AM ---------- Previous post was 2nd June 2015 at 11:37 PM ----------
Anyone got the fxz for this yet?

Ok, figured this out ...
(was able to back down to the original 4.4.4 w/rsd-lite and regain TWRP and develop these steps)
So the following can be done to upgrade to this new version, and retain TWRP (plus you have the new recovery later on for 5.1 when it comes along ...)
First, the presumption here is you are unlocked. If you are not, none of this will work.
Also, you will need RSD-Lite installed and operational.
Download :
https://dl.dropboxusercontent.com/u...RIZON_4.4.4_KXA21.12-L1.26-3_cid2_1FF.xml.zip
https://dl.dropboxusercontent.com/u...4.4.4_KXA21.12-L1.26-3/twrp-2.8.6.0-ghost.img
https://dl.dropboxusercontent.com/u/22067374/GHOST_VERIZON_4.4.4_KXA21.12-L1.26-3/servicefile.xml
Unpack the GHOST zip file, and overwrite the "servicefile.xml" in the unpacked folder w/the one you downloaded, then copy the twrp .img in there.
Fire up RSD-Lite, put your phone in fastboot, and apply this update by loading the servicefile.xml as the update.
It will update everything, installing the TWRP instead of the new stock recovery.
Note: you can delete the twrp line in servicefile.xml if you wish to retain your existing custom recovery.
When done, you should reboot, update, and be up and running with the new 4.4.4 and TWRP ... so easy path back to root via TWRP.

FYI... its already confirmed that you do NOT have to disable Xposed... All you need is stock recovery.
See -> http://forum.xda-developers.com/moto-x/moto-x-qa/ota-custom-recovery-t3124492

How to root LP 5.1.1 with New system-less SuperSU 2.6.X

Hi all,
I just finished testing the new method of rooting using new SuperSU system-less and it's working well on my P600. I don't have other device to test it on, but if you guys could test it out on your device and report back, that would be nice.
Here how to root using new SuperSU system-less app:
Prep:
1) Download Odin 3.09 http://odindownload.com/Samsung-Odin/#.Vm3AglE1I-Q
2) Download SuperSu version 2.6.2 to your SDcard here http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
3) Download TWRP 2.8.7.0 tar file to your PC here https://dl.twrp.me/lt03wifiue/ (you must use Spen to navigate, touch won't work)
For P605 - Please use twrp-2.8.7.0-lt03ltexx-4.4.img.tar version here https://dl.twrp.me/lt03ltexx/
4) Download the full stock 5.1.1 firmware by download this tool to your PC from here http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Then use the tool to download 5.1.1 rom (very fast download). set model=sm-p600, region=XAR, put a check in "Auto" and "Decrypte automatically"
Execcution:
1) Use Odin to flash full factory rom 5.1.1 to your device with "Auto Reboot" checked. If you already using 5.1.1 with root, you can just flash over your current one. Your data will be preserved. It's not nessessary to flash the full firmware but it's easier and less confuse. Once completed your device will reboot. Now boot back to download mode.
2) Use Odin to flash TWRP 2.8.7.0 with "Auto Reboot" UNchecked. Once completed. Hold Vol up+Home+power buttons to boot to TWRP recovery(do not let your device boot up). It will take a while so just wait. You also will see a red message warning about SEdroid security..blah blah...just ignore it. If you want TWRP touch, you can flash this version zip (can't flash through ODIN) before proceed. https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03wifi
3) Once in TWRP, flash the SuperSU 2.6.1 system-less. Becareful here, after hit REBOOT, If TWRP offered to root, DO NOT DO IT (You will bootloop if you miss this step). Hit on "do not install". Your device will reboot. Done!! This SuperSU will patch your kernel and install root. Once completed boot up and enjoy. Your system is now rooted with TWRP installed. Pretty nice!!
EDIT: You also need to disable "Security change" pop up by remove or use Titanium to disable "Security policy updates" and "SecurityLogAgent". I heard report that if you don't your device may bootloop later on.

@joshndroid made his own version of twrp 2.8.7 which has full touch support/recognition (not just the s-pen). Here is the link:
https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03wifi Maybe could you put this version in the OP as another option instead of the official twrp?

Guys, a question. Can i use the exynos version of TWRP, ie- lt03wifiue, on my SM-P601, which is also the exynos one, but with 3G support.?
Thanks.

mosimchah said:
@joshndroid made his own version of twrp 2.8.7 which has full touch support/recognition (not just the s-pen). Here is the link:
https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03wifi Maybe could you put this version in the OP as another option instead of the official twrp?
Click to expand...
Click to collapse
I don't think he made one for Odin.
Sent from my SM-P600 using Tapatalk

amey2606 said:
Guys, a question. Can i use the exynos version of TWRP, ie- lt03wifiue, on my SM-P601, which is also the exynos one, but with 3G support.?
Thanks.
Click to expand...
Click to collapse
Yes
Sent from my SM-P600 using Tapatalk

buhohitr said:
I don't think he made one for Odin.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Good point, I didn't notice that, however we could flash the official twrp with odin, and then we could flash joshndroid's twrp from the official twrp. So could you add that to the op?

mosimchah said:
Good point, I didn't notice that, however we could flash the official twrp with odin, and then we could flash joshndroid's twrp from the official twrp. So could you add that to the op?
Click to expand...
Click to collapse
Added to OP. Thanks

Ok
Root is present (supersu) seem to work but, don't work with some apps

murigny64 said:
Ok
Root is present (supersu) seem to work but, don't work with some apps
Click to expand...
Click to collapse
Give me a few so I can test them out

murigny64 said:
Ok
Root is present (supersu) seem to work but, don't work with some apps
Click to expand...
Click to collapse
Did you install supersu from the playstore and did it ask to update binaries? I can't remember when I did mine if it asked or not. I don't have any su issues with mine.

Flash firm doj3 with odin
Reboot in bootloader
Flash twrp with odin
Reboot in twrp
Flash supersu 2.61
Reboot.
Kernel seem to be patched (red warning message), Supersu app is present with no binarie update needed.
Reboot in twrp and Flash xposed wanam mod
Result:
Titanium Backup: ok
Rebooter app: nok
Freeze after 2 mins: have to hard reboot, again and again.
So, I flash again with odin and use the old method (boot patched)

how do i uninstall twrp?

tahrang said:
how do i uninstall twrp?
Click to expand...
Click to collapse
Flash a different recovery, either with twrp or odin. Why do you want to remove twrp?

Done and completed
twrp not working correctly, it did previously, but after the update, it doesn't.
---------- Post added at 09:40 PM ---------- Previous post was at 09:15 PM ----------
buhohitr said:
Hi all,
I just finished testing the new method of rooting using new SuperSU system-less and it's working well on my P600. I don't have other device to test it on, but if you guys could test it out on your device and report back, that would be nice.
Here how to root using new SuperSU system-less app:
Prep:
1) Download SuperSu version 2.6.1 to your SDcard here http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
2) Download TWRP 2.8.7.0 tar file to your PC here https://dl.twrp.me/lt03wifiue/ (you must use Spen to navigate, touch won't work)
3) Download the full stock 5.1.1 firmware by download this tool to your PC from here http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Then use the tool to download 5.1.1 rom (very fast download). set model=sm-p600, region=XAR, put a check in "Auto" and "Decrypte automatically"
Execcution:
1) Use Odin to flash full factory rom 5.1.1 to your device with "Auto Reboot" checked. If you already using 5.1.1 with root, you can just flash over your current one. Your data will be preserved. It's not nessessary to flash the full firmware but it's easier and less confuse. Once completed your device will reboot. Now boot back to download mode.
2) Use Odin to flash TWRP 2.8.7.0. Once completed. Hold Vol up+Home+power buttons to boot to TWRP recovery(do not let your device boot up). It will take a while so just wait. You also will see a red message warning about SEdroid security..blah blah...just ignore it. If you want TWRP touch, you can flash this version zip (can't flash through ODIN) before proceed. https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03wifi
3) Once in TWRP, flash the SuperSU 2.6.1 system-less. Becareful here, If TWRP offered to root, DO NOT DO IT. This SuperSU will patch your kernel and install root. Once completed boot up and enjoy. Your system is now rooted with TWRP installed. Pretty nice!!
Click to expand...
Click to collapse
HELP!
yes I'm screaming, sorry.
I followed these instructions, and now my note is stuck in loop - starts with samsung galaxy note 10.1 2014 logo, goes to samsung logo and restarts.
Please, please help
thanks
Now it is stuck on samsung logo, and doesnot go any further.
Ok, now I'm starting the whole thing again. hopefully, this will go better
third time is the charm! succeeded.

What do i do when i already have the spanish firmware? Do i need to flash it again with the 5.1.1 code XAR? Or can i flash TWRP with Odin now.?

vuurvlinder said:
What do i do when i already have the spanish firmware? Do i need to flash it again with the 5.1.1 code XAR? Or can i flash TWRP with Odin now.?
Click to expand...
Click to collapse
I flashed the xar update, even though i already had the spanish one, plus i was rooted. then i flashed twrp and supersu like in the post above.
thanks
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
murigny64 said:
Flash firm doj3 with odin
Reboot in bootloader
Flash twrp with odin
Reboot in twrp
Flash supersu 2.61
Reboot.
Kernel seem to be patched (red warning message), Supersu app is present with no binarie update needed.
Reboot in twrp and Flash xposed wanam mod
Result:
Titanium Backup: ok
Rebooter app: nok
Freeze after 2 mins: have to hard reboot, again and again.
So, I flash again with odin and use the old method (boot patched)
Click to expand...
Click to collapse
did you get the wanam again after the old method? if so, please tell me how.
thanks

Hmm - I've Odin'd the new XAR v.5.1.1 just fine, but when I try to Odin TWRP 2.8.7/6/3, they all fail in Odin 3.09. I've tried multiple times with same result. Any suggestions?

Michael in ATL said:
Hmm - I've Odin'd the new XAR v.5.1.1 just fine, but when I try to Odin TWRP 2.8.7/6/3, they all fail in Odin 3.09. I've tried multiple times with same result. Any suggestions?
Click to expand...
Click to collapse
Did you boot up after Odin XAR 5.1.1? boot up then boot down to Odin download mode and try again.

Not able to Odin TWRP
buhohitr said:
Did you boot up after Odin XAR 5.1.1? boot up then boot down to Odin download mode and try again.
Click to expand...
Click to collapse
I sure did, and should've been clearer. I'm running 5.1.1 XAR that I Odin'd yesterday. USB debugging is enabled, and Odin tries/fails when trying to load up to 4 versions of TWRP that I've tried. Further, I get corrupted firmware after it tries, and have to reinstall v5.1.1 (if that tells those much smarter than I anything)

Michael in ATL said:
I sure did, and should've been clearer. I'm running 5.1.1 XAR that I Odin'd yesterday. USB debugging is enabled, and Odin tries/fails when trying to load up to 4 versions of TWRP that I've tried. Further, I get corrupted firmware after it tries, and have to reinstall v5.1.1 (if that tells those much smarter than I anything)
Click to expand...
Click to collapse
Can you try to boot int recovery to see if you can access stock recovery? Possible you need to do format storage?

[RECOVERY][ROOT] N910T/T3 6.0.1 PE3 - How to Root (Systemless & System Mode) / TWRP

[RECOVERY][ROOT] N910T/T3 6.0.1 PE3 - How to Root (Systemless & System Mode) / TWRP
This is really simple but I'm guessing people are still wondering.
Download TWRP
Download SuperSU 2.76 Systemless (for Stock Kernels) or Download SuperSU 2.76 SystemMode (Permissive Kernel Required)
*Optional* Download a Permissive Kernel like BeastMode (only needed for System Mode SuperSu)
Download Odin
Put the SuperSU on your SD Card / Internal Storage
*Optional* Put Custom Kernel on SD Card (Optional, Only required if using SuperSu SystemMode)
Reboot into Download Mode
Flash TWRP in Odin
Boot into TWRP
Flash SuperSU
Enjoy!
For details on how to flash with Odin, flash with TWRP please see other threads or use Google.
Additional Downloads:
-N910T PE3 Stock Recovery
Additional Info:
NetFlix:
Some users have reported that NetFlix would not connect after rooting. There is no need to do this if you do not have any problems with NetFlix.
-Delete /system/vendor/lib/liboemcrypto.so and reboot.
------------------------------------------------------
Thanks of course to Chainfire & Teamwin
Also Thanks to freeza.

Cool. Thanks. it's same for all other mm roms too.

Is this Systemless root?

So if we already have a rooted device with TWRP installed, and assuming we already were able to flash 6.0.1 to the device, then the only step required is:
Download SuperSU
Flash SuperSU via TWRP
Is that right?
Sent from my SM-N910T3 using XDA-Developers mobile app

f4phantomii said:
So if we already have a rooted device with TWRP installed, and assuming we already were able to flash 6.0.1 to the device, then the only step required is:
Download SuperSU
Flash SuperSU via TWRP
Is that right?
Sent from my SM-N910T3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Your prior rooted device needs to be rerooted. Download SuperSu to phone. Download TWRP to computer. Odin TWRP. Once TWRP is flashed, boot to TWRP and install Supersu [at least that's what I did.]

But since I already have TWRP installed as recovery, do I need to re-install it via Odin?
Unless flashing 6.0.1 overwrites the recovery?
Otherwise just flashing SuperSU should re-root.
Sent from my SM-N910T3 using XDA-Developers mobile app

f4phantomii said:
But since I already have TWRP installed as recovery, do I need to re-install it via Odin?
Unless flashing 6.0.1 overwrites the recovery?
Otherwise just flashing SuperSU should re-root.
Click to expand...
Click to collapse
Odin flashing MM will overwrite your recovery.

Got it. Thanks fo clarifying that.
Sent from my SM-N910T3 using XDA-Developers mobile app

Question, have rooted and jail broke many but not this 910T yet. I am on non-root 5.1.1, should I take the OTA 6.0.1 and then follow the above instructions or download 6.0.1 from samsung and install via Odin and then start following these instructions? Would perfer to take over the air so I dont have to reset up everything.
Thanks in advance and I cant fn wait to start using Adfree again!

I downloaded via Kies. Didn't have to setup a thing after.
Sent from my SM-N910T using XDA-Developers mobile app

I'm impressed we got this being 1.90 generations old. I usually feel forgotten and abandoned by now. Thanks T-Mo. Now please don't F us on the Note 6/7 bootloader!

Bubba Fett said:
I'm impressed we got this being 1.90 generations old. I usually feel forgotten and abandoned by now. Thanks T-Mo. Now please don't F us on the Note 6/7 bootloader!
Click to expand...
Click to collapse
Agreed.

Anybody know if editing the platform.xml still works for SD card writing? And with the update I am getting the stupid -504 error in google play store trying to install Titanium backup......I might have to reflash ugh.
Edit*****
I fixed my issue

Bubba Fett said:
I'm impressed we got this being 1.90 generations old. I usually feel forgotten and abandoned by now. Thanks T-Mo. Now please don't F us on the Note 6/7 bootloader!
Click to expand...
Click to collapse
They will.

Man I hope not. We did a lot of *****in! Looks like HTC is gonna do the next nexus and should be on par with the N7 but I really don't want to do that. There is no way any phone can compare with the same phone rooted and custom. We will see.

Any ideas, stock non rooted 5.1 updated via OTA to 6.0.1, flashed latest TWRP 3.2.0 successfully (USB Deb enabled, R/L disabled) and still boots into stock recovery? What am I doing wrong?
SM-N910T
---------- Post added at 02:39 AM ---------- Previous post was at 01:41 AM ----------
Found a work around from another post:
'm trying to install TWRP, but it keeps getting overwritten. After installing, I can initially boot into TWRP, but after doing a system reboot, it goes back to stock recovery. What am I doing wrong?
Here's the steps I take:
Open Odin, check AP and load twrp image (3.0.0)
Connect phone and wait for Added!
Uncheck Auto Reboot
Click Start and wait to finish.
I then have to take out the battery to turn the phone off (I had to do it this way because leaving Auto Reboot checked would cause the same issue as below). I then boot directly into recovery and TWRP loads as expected. Everything looks fine, and I can do a recovery reboot back to TWRP. However, if I do a system reboot and let Android load, then shutdown and boot into recovery again, I'm back to stock.
Sprint SM-N910P
Android 5.1.1
http://androidforums.com/threads/twrp-keeps-getting-overwritten.1003988/

richard75013 said:
Any ideas, stock non rooted 5.1 updated via OTA to 6.0.1, flashed latest TWRP 3.2.0 successfully (USB Deb enabled, R/L disabled) and still boots into stock recovery? What am I doing wrong?
SM-N910T
---------- Post added at 02:39 AM ---------- Previous post was at 01:41 AM ----------
Found a work around from another post:
'm trying to install TWRP, but it keeps getting overwritten. After installing, I can initially boot into TWRP, but after doing a system reboot, it goes back to stock recovery. What am I doing wrong?
Here's the steps I take:
Open Odin, check AP and load twrp image (3.0.0)
Connect phone and wait for Added!
Uncheck Auto Reboot
Click Start and wait to finish.
I then have to take out the battery to turn the phone off (I had to do it this way because leaving Auto Reboot checked would cause the same issue as below). I then boot directly into recovery and TWRP loads as expected. Everything looks fine, and I can do a recovery reboot back to TWRP. However, if I do a system reboot and let Android load, then shutdown and boot into recovery again, I'm back to stock.
Sprint SM-N910P
Android 5.1.1
http://androidforums.com/threads/twrp-keeps-getting-overwritten.1003988/
Click to expand...
Click to collapse
I'm having the same issue however I can't get into TWRP period... I pushed MM and TWRP 3.0.2 from ODIN 3.07. During reboot it rw's the MM recovery

Has anyone flashed the new 6.0 MM BL and CP vs Flashfire?

The G.O.A.T. said:
I'm having the same issue however I can't get into TWRP period... I pushed MM and TWRP 3.0.2 from ODIN 3.07. During reboot it rw's the MM recovery
Click to expand...
Click to collapse
richard75013 said:
Any ideas, stock non rooted 5.1 updated via OTA to 6.0.1, flashed latest TWRP 3.2.0 successfully (USB Deb enabled, R/L disabled) and still boots into stock recovery? What am I doing wrong?
SM-N910T
---------- Post added at 02:39 AM ---------- Previous post was at 01:41 AM ----------
Found a work around from another post:
'm trying to install TWRP, but it keeps getting overwritten. After installing, I can initially boot into TWRP, but after doing a system reboot, it goes back to stock recovery. What am I doing wrong?
Here's the steps I take:
Open Odin, check AP and load twrp image (3.0.0)
Connect phone and wait for Added!
Uncheck Auto Reboot
Click Start and wait to finish.
I then have to take out the battery to turn the phone off (I had to do it this way because leaving Auto Reboot checked would cause the same issue as below). I then boot directly into recovery and TWRP loads as expected. Everything looks fine, and I can do a recovery reboot back to TWRP. However, if I do a system reboot and let Android load, then shutdown and boot into recovery again, I'm back to stock.
Sprint SM-N910P
Android 5.1.1
http://androidforums.com/threads/twrp-keeps-getting-overwritten.1003988/
Click to expand...
Click to collapse
Perhaps try wiping everything...
System, Data, Internal Storage.
Then flash the Odin MM tar.
Then start the process in the thread.
I personally did the process after a SmartSwitch update and it worked from just doing what I listed in the OP.

DeeXii said:
Perhaps try wiping everything...
System, Data, Internal Storage.
Then flash the Odin MM tar.
Then start the process in the thread.
I personally did the process after a SmartSwitch update and it worked from just doing what I listed in the OP.
Click to expand...
Click to collapse
Yeah idk... It just worked this time. IF I was to say what I did different I booted into recovery first it started with applying update or something then crashed because no update was there, then showed stock MM recovery I then. Shutdown and went into download mode and did the OP.
It work!!!
Doing a new backup now

Android Pie 9.0 root possible ??

Hi guys, I had read many posts about rooting essential phone. But those articles aren't mention if it is suitable for android Pie version. Is there anyone knows how to root my essential phone with Pie 9.0 ??

See this thread.

prabs99 said:
See this thread.
Click to expand...
Click to collapse
Thanks for your reply. I had read this thread. But in step 4. Once you're in TWRP, install the stock boot image and then the Magisk zip.
I wonder which boot image I should install, cause both NMJ32F & NMJ20D are not same as android P build number which is "PPR1.1806.10.091".
I will appreciate for your help.:laugh:

Download the BTS (Back to Stock) file from this thread. Extract the stockboot image from the zip file. Now you flash that file from TWRP.
eric672913 said:
Thanks for your reply. I had read this thread. But in step 4. Once you're in TWRP, install the stock boot image and then the Magisk zip.
I wonder which boot image I should install, cause both NMJ32F & NMJ20D are not same as android P build number which is "PPR1.1806.10.091".
I will appreciate for your help.:laugh:
Click to expand...
Click to collapse
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
Try this for just the boot image.
prabs99 said:
Download the BTS (Back to Stock) file from this thread. Extract the stockboot image from the zip file. Now you flash that file from TWRP.
Click to expand...
Click to collapse

prabs99 said:
Download the BTS (Back to Stock) file from this thread. Extract the stockboot image from the zip file. Now you flash that file from TWRP.
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
Try this for just the boot image.
Click to expand...
Click to collapse
Got it , I will try this. Thanks so much:laugh:

eric672913 said:
Got it , I will try this. Thanks so much[emoji23]
Click to expand...
Click to collapse
Try but fail and get boot loop [emoji27] . Reboot to bootloader and flash twrp, then get into TWRP recovery , flash Magisk then boot img. Anything wrong?
Sent from my [device_name] using XDA-Developers Legacy app

eric672913 said:
Try but fail and get boot loop [emoji27] . Reboot to bootloader and flash twrp, then get into TWRP recovery , flash Magisk then boot img. Anything wrong?
Click to expand...
Click to collapse
Your doing the order wrong.
When you get into TWRP, flash the boot.img that matches the current build you are on, then flash the magisk zip, then reboot.

NaterTots said:
Your doing the order wrong.
When you get into TWRP, flash the boot.img that matches the current build you are on, then flash the magisk zip, then reboot.
Click to expand...
Click to collapse
I just got a new unrooted phone and took the Pie OTA. Just to be sure I understand you, in my case, I already have the correct boot.img and can go ahead and flash TWRP, then Magisk just like on old phones, right?

jwinstonsf said:
I just got a new unrooted phone and took the Pie OTA. Just to be sure I understand you, in my case, I already have the correct boot.img and can go ahead and flash TWRP, then Magisk just like on old phones, right?
Click to expand...
Click to collapse
That's not what I wrote
First go into settings and make sure you have the build that ends with 091.
Then from either the BTS zip you downloaded, or from the Root guide thread, make sure you have the boot.img that is tagged 091. (Personally I've been using the boot.img's that are uploaded in the OP of the Guide to root thread)
Then, go through the fastboot process to install TWRP,
boot into TWRP,
then install the boot.img,
then flash the magisk zip.
Reboot profit.
You have to flash the boot.img for the current build your running Everytime you want to flash something through TWRP.

NaterTots said:
That's not what I wrote
First go into settings and make sure you have the build that ends with 091.
Then from either the BTS zip you downloaded, or from the Root guide thread, make sure you have the boot.img that is tagged 091. (Personally I've been using the boot.img's that are uploaded in the OP of the Guide to root thread)
Then, go through the fastboot process to install TWRP,
boot into TWRP,
then install the boot.img,
then flash the magisk zip.
Reboot profit.
You have to flash the boot.img for the current build your running Everytime you want to flash something through TWRP.
Click to expand...
Click to collapse
I am already in 091. When flash image "boot.img" via TWRP, there are two check options : boot partion & system partion, which one should I check? Many thanks
Sent from my [device_name] using XDA-Developers Legacy app

eric672913 said:
I am already in 091. When flash image "boot.img" via TWRP, there are two check options : boot partion & system partion, which one should I check? Many thanks
Click to expand...
Click to collapse
Boot.img

eric672913 said:
I am already in 091. When flash image "boot.img" via TWRP, there are two check options : boot partion & system partion, which one should I check? Many thanks
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Boot image should go to the boot partition.

Click on link, Download essentials zip
Reboot to bootloader
Flash twp img
Boot to recovery
Once in twrp, flash pie img first "boot partition"
Then magisk zip and well-being If you want app timer/dashboard
Reboot device
(When rebooting, press "do not install" twrp as system app)
Contains latest ph1 update boot img and latest twrp.
https://drive.google.com/file/d/1R8wMO2ELfOsjRXYfPP6_100J6OCmRshd/view
When installing Magisk zip, Sideload it.

manr1mg said:
Click on link, Download essentials zip
Reboot to bootloader
Flash twp img
Boot to recovery
Once in twrp, flash pie img first "boot partition"
Then magisk zip and well-being If you want app timer/dashboard
Reboot device
(When rebooting, press "do not install" twrp as system app)
Contains latest ph1 update boot img and latest twrp.
https://drive.google.com/file/d/1R8wMO2ELfOsjRXYfPP6_100J6OCmRshd/view
Click to expand...
Click to collapse
Thanks for your help. As I follow the steps , I got some errors when install Magisk & well-being which encloses screen shot in attached file. Anything wrong ??

eric672913 said:
Thanks for your help. As I follow the steps , I got some errors when install Magisk & well-being which encloses screen shot in attached file. Anything wrong ??
Click to expand...
Click to collapse
Im sorry for the inconveniences but for some reason when installing Magisk, I had to Sideload it. I'll see how come but for now just Sideload Magisk after you flash boot img, that should do the trick.

After you flash twrp, go into twrp, install boot.img, MAYBE make sure system is mounted THEN install magisk. I've read some of the red errors happen regardless so I'd just fire up the phone afterwords and see if it works.

eric672913 said:
Thanks for your help. As I follow the steps , I got some errors when install Magisk & well-being which encloses screen shot in attached file. Anything wrong ??
Click to expand...
Click to collapse
you are flashing the boot image as system image and not as boot. I made that mistake too. Im pretty sure your phone doesnt boot to system after flashing magisk correct? Flash stock image again, go to twrp and when flashing boot image make sure you flash it to boot, not system.

luisoman2000 said:
you are flashing the boot image as system image and not as boot. I made that mistake too. Im pretty sure your phone doesnt boot to system after flashing magisk correct? Flash stock image again, go to twrp and when flashing boot image make sure you flash it to boot, not system.
Click to expand...
Click to collapse
Thanks for your reply. I am sure that I check "boot" when flashing stock img. Now I had try the following two ways:
1. when get into TWRP, I mount system first. and then install stock img, and then magisk. there's no error.
2. using sideload, fist sideload magisk, and reboot to bootloader , and then flash stock img, there's no error.
when I restart phone. No magisk apk installed. quite werid. Need your help.

manr1mg said:
Im sorry for the inconveniences but for some reason when installing Magisk, I had to Sideload it. I'll see how come but for now just Sideload Magisk after you flash boot img, that should do the trick.
Click to expand...
Click to collapse
Now I had try the following two ways:
1. when get into TWRP, I mount system first. and then install stock img, and then magisk. there's no error.
2. using sideload, fist sideload magisk, and reboot to bootloader , and then flash stock img, there's no error.
when I restart phone. No magisk apk installed. quite werid. Need your help.:fingers-crossed:

Painful thread to read.