Database Info

(experts only) So many unanswered questions

easy to understand answers only
1.how chould i choose my flash file for example i have a i9100 i see flash files with letters behind the device name how do i choose the right on for my device (any device not just i9100)?
2.if my device is locked to a network for example at&t can i flash it with a normal flash file?
3.if my device was locked (unlocked) to a network for example at&t can i flash it with a normal flash file without harm to the device?
4.if my device became dead during flashing the device boot how can i fix it?
5.whats a kernal?
6.is it true if i flash my device with a unrooted flash it will be impossible to root it without flashing it with a rooted flash?
7. how to root any device not using SuperOneClick?
8.how can i unlock my android device for free?
9.any useful advice that i didnt ask for but might be useful?

cabloomi said:
easy to understand answers only
1.how chould i choose my flash file for example i have a i9100 i see flash files with letters behind the device name how do i choose the right on for my device (any device not just i9100)?
2.if my device is locked to a network for example at&t can i flash it with a normal flash file?
3.if my device was locked (unlocked) to a network for example at&t can i flash it with a normal flash file without harm to the device?
4.if my device became dead during flashing the device boot how can i fix it?
5.whats a kernal?
6.is it true if i flash my device with a unrooted flash it will be impossible to root it without flashing it with a rooted flash?
7. how to root any device not using SuperOneClick?
8.how can i unlock my android device for free?
9.any useful advice that i didnt ask for but might be useful?
Click to expand...
Click to collapse
1. Those don't really matter unless the letter(s) is apart of the device's name.
2. As long as it's for your device (or stated as compatible), then yes.
3. See #2
4. You could boot into recovery and flash a different rom. You could also boot into fastboot or download mode (depending on the device), and flash a rom as well.
5. See here: http://forum.xda-developers.com/showthread.php?t=1466228 (scroll down to "kernel").
6. I'm assuming by "flash" (the 2nd and last one) you mean "rom". If so, then no, it is not true unless the rom you flashed is not rootable.
7. The most common ways of rooting devices is using SuperOneClick, z4root, Gingerbreak, Universal Androot, and/or DooMLoRD's Easy Rooting Toolkit. Not all devices are rootable with the same method, so a custom device specific method would be needed.
8. Get the unlock code from your carrier or use a custom method (device specific) to do it.
9. Read here: http://forum.xda-developers.com/showthread.php?t=1466228 (it can help a lot).

thx you were so helpful, i took awhile to reply, but now i think im no longer a noob, thx to you , you were so very helpful

[ROOT] Root NVidia Shield Tablet - Lollipop (also locked bootloader)

Hi all,
The original credits for the root go to SuperPichu for the following post: http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
I simply "modified" his process, to make it even more "hassle free"
The process will wipe your data, so remember to backup it.
Besides, I'm not responsible if warranty voids or whatever. Just keep in mind that unlocking the FASTBOOT may void the warranty, as it will displayed when you will unlock it. The fastboot unlock procedure has been taken directly by the NVidia Developer's site, so they actually expect the users to do that - but what you will do next, it's all your responsability
So, the overall procedure looks like:
Download&Install the "Mini" ADB/Fastboot from here: http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 (remember to say yes to create the link on the desktop - it will be useful later)
Download&Install NVIDIA ADB Drivers from the official Nvidia site: http://developer.download.nvidia.com/mobile/shield/SHIELDTablet_WHQL_USB_driver.zip
Enable "Developer Mode" on the Nvidia Tablet (Settings -> About tablet -> Tap many times (5+) the "Build number" until the Developer Mode is activated
Developer Mode -> Enable USB Debugging
Copy the CWM image and SuperSU (rename it to supersu.zip) where you installed the Mini ADB/Fastboot (default: C:\Program Files\Minimal ADB and Fastboot)
Click the link created by the Mini ADB/Fastboot installation. It should open a DOS console already at the install folder.
(In the Windows console) Type "adb reboot bootloader"
From the rebooted tab, select "Load fastboot protocol" with Volume Keys and push the power switch to confirm
(In the Windows console) Type "fastboot oem unlock"
[ATTENTION: This step will wipe your device] Press the "Volume Down" button to select, with the "Power" button, the "Unlock bootloader" option on device
(In the Windows console) Type "fastboot flash recovery recovery.img"
On the tablet, select "recovery reboot"
You should be now on CWM. Simply select "install zip from file" -> install from sideload
In the console, type "adb sideload supersu.zip"
On CWM select "reboot system", CWM will ask to keep root => say yes
Enjoy your rooted tablet

Very nice! I wish there was a way to do this without installing custom recovery (so that we can accept ota updates). The Shield Portable is easier. Just unlock, and run the shield root image. It doesn't install Custom Recovery and is a very similar process to Chainfire's CF Auto Root methods.

wwjoshdew said:
Very nice! I wish there was a way to do this without installing custom recovery (so that we can accept ota updates). The Shield Portable is easier. Just unlock, and run the shield root image. It doesn't install Custom Recovery and is a very similar process to Chainfire's CF Auto Root methods.
Click to expand...
Click to collapse
Well first off I havent had any issues with ota updates on CWM (took kitkat otas). Second, if you really don't want a custom recovery why not just obtain root then flash back the stock recovery??

wwjoshdew said:
Very nice! I wish there was a way to do this without installing custom recovery (so that we can accept ota updates). The Shield Portable is easier. Just unlock, and run the shield root image. It doesn't install Custom Recovery and is a very similar process to Chainfire's CF Auto Root methods.
Click to expand...
Click to collapse
To be honest with you, I haven't updated yet - but the OTA seems to work (i.e. it's currently saying that my Firmware is up-to-date, no errors). Just wait a couple of weeks (NVIDIA released a firmware update every month until now :good: ) and I'll let you know if it works
Btw, even if I loose the the root/CWM, it's not a great deal to install it again

FYI, as soon as you root or modify a stock 5.x.x (Lollipop) image, you'll no longer be able to accept OTA anymore without first flashing back to stock (this applies to all devices - although you might be able to manually flash a new update) - I guess we'll find out once 5.0.1 is released for the Shield...
Sent from my SHIELD Tablet using XDA Free mobile app

An Droid said:
FYI, as soon as you root or modify a stock 5.x.x (Lollipop) image, you'll no longer be able to accept OTA anymore without first flashing back to stock (this applies to all devices - although you might be able to manually flash a new update) - I guess we'll find out once 5.0.1 is released for the Shield...
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Good to know. ?But we should be able to flash the ota zips via recovery and flash super su and possibly recovery (locked bootloaders, ota can overwrite recovery) just like we did to update to lolli. I usually see zips before I see the ota anyways.

sandrodjay said:
Just keep in mind that unlocking the FASTBOOT may void the warranty, as it will displayed when you will unlock it.
Click to expand...
Click to collapse
I have contacted NVIDIA today, asking steps to move back to Kitkat. I was given instructions to unlock the bootloader, and was assured it will not void the warranty. The assistant was being meticulous regarding this, since she asked around for her colleagues' advice before giving me the information.
So if I ever need to send in for warranty, all I have to do is reflash the factory image to get rid of the root and I'll be all set. If they make a fuss about me having an unlocked bootloader, I'll have a chat transcript to back me up. You guys may want to do the same too.

Thank you worked great!

An Droid said:
FYI, as soon as you root or modify a stock 5.x.x (Lollipop) image, you'll no longer be able to accept OTA anymore without first flashing back to stock (this applies to all devices - although you might be able to manually flash a new update) - I guess we'll find out once 5.0.1 is released for the Shield...
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Just took 5.0.1 (wasn't rooted or anything). So I was thinking if I flash the CWM, then do a stock backup, then proceeed to root I should be able to restore the backup when a new OTA comes out since it will be unrooted and stock. Then I can update, install recovery if needed, make another unrooted stock backup, for the next time then reroot, right?

Should work, but after restoring your stock backup you will need the stock Recovery too to update ota.

Hi
There is no need to flash the custom recovery if you don't want to. Just do a fastboot boot recovery <recovery.img>. I did that because i didn't want to change to another recovery.
After the reboot you will revert to stock recovery.
\Sorenjul

Just to make sure, if you unlock the bootloader through "fastboot oem unlock" theres no way to reverse it in case need to send in for warranty repair, just like samsung devices with the stupid KNOX e-fuse? Or you can just revert everything (flash stock image/recovery and then fastboot oem lock)?

eurominican said:
Just to make sure, if you unlock the bootloader through "fastboot oem unlock" theres no way to reverse it in case need to send in for warranty repair, just like samsung devices with the stupid KNOX e-fuse? Or you can just revert everything (flash stock image/recovery and then fastboot oem lock)?
Click to expand...
Click to collapse
Unlocking the bootloader doesn't void the warranty (and even if it did, they would still be able to figure out if you've unlocked it before, even after relocking)

Help
Anyone else not able to download supersu.zip the page wont load

Granger77 said:
Anyone else not able to download supersu.zip the page wont load
Click to expand...
Click to collapse
NM sorry just went it opened instantly, maybe to much traffic

eurominican said:
Just to make sure, if you unlock the bootloader through "fastboot oem unlock" theres no way to reverse it in case need to send in for warranty repair, just like samsung devices with the stupid KNOX e-fuse? Or you can just revert everything (flash stock image/recovery and then fastboot oem lock)?
Click to expand...
Click to collapse
Ofcourse you can relock and go to 99.999% stock. 99.9% bacause after un- & relock there will be a little sign which shows nvidia that your bootloader was unlocked but you can't remove it. But as far as i know it doesn't void your warranty!

root method LTE compatible
Hello,
I'm expecting a 32GB tablet (LTE/4G device) soon. Does your ROOT method work for the LTE model, or is it just for the 16GB (wifi only) device ?
Thank you.

Driver issues
I cant for the life of me get my win 7 64bit pc to install the drivers I've tried uninstall and going through manually with the naked driver method and it still says the device doesnt need it his tutorial is for win 8 am I missing something, I'm losing my mind over here I want this thing rooted so bad I'm losing sleep, and google has been useless

cyraxx84 said:
Ofcourse you can relock and go to 99.999% stock. 99.9% bacause after un- & relock there will be a little sign which shows nvidia that your bootloader was unlocked but you can't remove it. But as far as i know it doesn't void your warranty!
Click to expand...
Click to collapse
Ty for info and reply.
Bogdacutu said:
Unlocking the bootloader doesn't void the warranty (and even if it did, they would still be able to figure out if you've unlocked it before, even after relocking)
Click to expand...
Click to collapse
Got it. Thanks!
oleg77 said:
Hello,
I'm expecting a 32GB tablet (LTE/4G device) soon. Does your ROOT method work for the LTE model, or is it just for the 16GB (wifi only) device ?
Thank you.
Click to expand...
Click to collapse
Same here. I got mine on sale with the controlller. I suspect its the same on both wifi only and LTE version.

Can i follow this guide to unlock and root 5.0.1?

[Guide] how to update mate 7 without getting error in recovery {update failed}

This guide is for all those who are getting error while updating their mate 7 manually either by local update option or by 3 buttons combo option.
here we go: ( for eg. consider mt7-tl10 model imternation version currently on any firmware and you want to install b123 firmware )
1. Extract recovery from new update.app to be installed i.e. b123 firmware.
2. flash it in fastboot mode.
3. now try to update using any of the option either local update or 3 buttons, it will run smoothly and you are done.
basically first we have to install recovery of the new version we want to install.
same can be followed to easily update to lollipop firmware.
hope this might help someone

Thanks - I was wondering what I was doing wrong since I can't update anymore either OTA, or local update or three fingers method, I constantly get the message "software update failed" and I am stuck with KingUser.apk ...
Can I ask I few more questions (I have changed ROMs in other mobile phones but not on the Mate 7)...
1) Do I need to unlock my bootloader to flash anything (I assume yes, my phone is still unlocked) ?
2) Do I need to use the Huawei Extractor (this one: http://forum.xda-developers.com/showthread.php?t=2433454)?
3) The name of the recovery is recovery.img (I guess so)?
Thanks a lot,
Paolo

Anubis1965 said:
Thanks - I was wondering what I was doing wrong since I can't update anymore either OTA, or local update or three fingers method, I constantly get the message "software update failed" and I am stuck with KingUser.apk ...
Can I ask I few more questions (I have changed ROMs in other mobile phones but not on the Mate 7)...
1) Do I need to unlock my bootloader to flash anything (I assume yes, my phone is still unlocked) ?
2) Do I need to use the Huawei Extractor (this one: http://forum.xda-developers.com/showthread.php?t=2433454)?
3) The name of the recovery is recovery.img (I guess so)?
Thanks a lot,
Paolo
Click to expand...
Click to collapse
1. Yes bootloader needs to be unlocked .
2. Yes, huawei extractor is required.
3. Yes it is recovery.img. You have to flash it in fastboot mode

[Q&A] [Firmware Update] For AOSP ROMS-3.4 KERNEL-NEW OFFICIAL CM NIGHTLIES [27June]

[Q&A] [Firmware Update] For AOSP ROMS-3.4 KERNEL-NEW OFFICIAL CM NIGHTLIES [27June]
Q&A for [Firmware Update] For AOSP ROMS-3.4 KERNEL-NEW OFFICIAL CM NIGHTLIES [27June]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Firmware Update] For AOSP ROMS-3.4 KERNEL-NEW OFFICIAL CM NIGHTLIES [27June]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

LIONS1 said:
When 1st time the new 3.4 kernel released many users had several issues with booting this amazing kernel or had boot loop,
You need this firmware update so you
can install new official CM nightly
so here is what you should do to enjoy it :
I will not be held responsible for your phone do at your own risk
1. First of all backup everything you need .
2. Download This :
2.1 A. For unbranded international devices & full package :
http://www.mediafire.com/?mc1mh05p669hspm
(Include Fastboot , Recovery , ADB , updated Firmware 2.15.0000, everything you'll need)
2.1 B. Here this link contains both firmware for international & T-Mobile devices :
https://www.dropbox.com/sh/ehihpbjf0shqgio/qu3vhYYDWe
2.2 For T-Mobile devices
You have to use T-Mobile firmware.zip from 2nd link replace it with my firmware.zip in the 1st file (A) and continue the steps.
2.3 Then extract it (The A-file) .
Hold Shift then right click on the folder and choose " Open Command Window Here " .
3. Boot into HBoot . Choose fastboot . in command Window type
"fastboot oem lock".
your phone will be locked .
4. Firmware (including HBoot , Boot , Recovery, Radio, every firmware partition needed for this new kernel... ).
Boot into HBoot again . Choose fastboot . in command Window type :
"fastboot oem rebootRUU".
after you are seeing HTC Screen then type :
"fastboot flash zip firmware.zip".
first time it get ERROR .
type again :
"fastboot flash zip firmware.zip".
now it should work and getting installed .
after install it does not reset use this command :
"fastboot reboot"
Or you have to reset by keeping power for some seconds .
5. unlock your phone again via the HTC Unlocking tool (HTC Dev site).
If you have the Unlock_code.bin file you received
originally, copy it into the working directory that you
have been using, return your phone to fastboot, and
issue the following command:
"fastboot flash unlocktoken Unlock_code.bin"
Your will be warned that you are voiding your warranty.
Select Yes or OK and continue. When the phone reboots
to the boatloader, it will announce that it has been
tampered with and is unlocked,
Note : Unlocking your bootloader will wipe your personal which is just data data partition not your internal SD .
6. Open command window again . type :
"fastboot flash recovery recovery.img".
this will install the latest TWRP Recovery .
Some users reported that this recovery.img in my package (A) is some how corrupted so download the latest TWRP RECOVERY and fastboot flash it don't use the one in my zip file
Get the latest TWRP recovery here http://goo.im/devs/OpenRecovery/ville
7. boot in recovery . for the first time it does not boot .
boot another time in recovery . it should work now .
8. Install The NEW CM KERNEL- WITCH IS IN YOUR ROM ZIP - IN FASTBOOT MODE THEN INSTALL The ROM IN TWRP RECOVERY after 3x full wipe .
9. Enjoy your CM 10.1 based ROM -3.4 KERNEL.
Please hit thanks button if this helped you
Hope you all enjoy the new amazing kernel with amazing new ROMS with it,
Thanks to all devs behind this great work
If your device is S-OFF you can just skip the relock & unlock steps And you won't lose any data by this way if you're running stock and just wanna upgrade the firmware but even with this I'd recommend to have backup before
Ps: check 2nd post
Tip: I'd recommend :
1.First if you don't want to risk TRY to run your device official JB RUU if you get errors with that try to get official JB update from the ota then the last way to get firmware update is to use my method here .
2.Get S-OFF and Super-CID if you get errors r with flashing the firmware.zip otherwise no need for that.
People to thank:
HTC
CyanogenMode team
@intervigil
@$droyd$
@BehradGH
@ron_e
@mo976
EVERYONE ELSE I FORGET.
Click to expand...
Click to collapse
pls the dropbox site to download download the t-mobile fireware is not working can u pls send me the firmware
[email protected]

[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root

[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root
THIS GUIDE IS NOW DEPRECATED. THERE IS NO NEED ANYMORE TO GO THROUGH THE UPDATING PROCESS AS THERE IS A FULL NOUGAT FACTORY IMAGE AVAILABLE (Build NPH25.200-22). FIRMWARE AVAILABLE HERE: https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 BE SURE TO THANK @acejavelin FOR TRACKING DOWN THE FIRMWARE PACKAGE FOR US.
Notes:
-YOU ATTEMPT THIS AT YOUR OWN RISK IF YOU FLASHED ANY FIRMWARE PREVIOUSLY NOT FOR THE XT1575 US VERSION
-This guide will have 2 parts. 1 for those that kept their systems read only/systemless, and 1 for those that did not.
-Whether you live booted TWRP or Installed TWRP, if you chose to allow system modifications your OTA will likely fail (you'll need part 2).
-Restoring a TWRP backup will not work and will cause an OTA to fail due to having to allow system write access in TWRP - You Need Part 2.
-This guide assumes you have basic ADB knowledge and already know what fastboot is and how it works.
-Thanks to @gokart2 for the OTA and @acejavelin for the return to stock guides
Part 1: Those That Tweaked Systemlessly Currently On 24.49-18-16 (Will only work if you kept TWRP read only/used systemless root):
1: Disable & Remove systemless Xposed within Magisk Manager and all other Magisk modules. Reboot and wait for Art cache to rebuild.
2: Remove any adblock hosts within your adblock app if installed, or any other root level system altering apps like Greenify (don't worry, you'll get them back).
3: Remove Magisk by booting into TWRP and flashing the current Magisk Removal zip. Reboot.
4: For systemless SuperSu you need to consult their thread as I do not use it. (I'll update this if someone knows the correct process).
5: ADB reboot bootloader and fastboot flash the stock recovery. Latest MM recovery links at the bottom of this post. (rename file to recovery.img).
6: Move the OTA Blur_Version.24.231.16.clark_retus.retus.en.US.zip to the root of your internal sd card (NOT in a folder). File links at the bottom of the post. Thanks @gokart2
7: ADB reboot recovery, when "no command" is listed, hold power + tap volume up then release to access recovery options. Choose "apply update from phone storage". Choose the file and wait for the flash. It's a large update so be patient (about 10-20min). Choose reboot manually in recovery after flash succeeds. Enjoy Nougat!
8: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly.
Part 2: Those That Have Done Everything - TWRP Write Access, Custom Roms, On Older Firmware, Etc (XT1572 Build Flashers Do This At Their Own Risk):
1: Flash the latest full factory image available (24.49-18-8) available here: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110. Thank @acejavelin for the thread while your at it. Follow the directions in that guide, it's well detailed and accurate - however read my notes just below first:
NOTES:
-Omit the "fastboot oem lock begin" & "fastboot oem lock" commands to remain bootloader unlocked.
-Omit the "fastboot erase userdata" command if you want to dirty flash and keep all of your data. I recommend clean, you can always root & restore each apps data with Titanium after the Playstore installs everything.
-The "fastboot oem fb_mode_set" instead of "fastboot oem lock begin" & "fastboot oem fb_mode_clear" instead of "fastboot oem lock" I've found to be unnecessary if staying unlocked. Your choice.
-The "fastboot flash partition gpt.bin" & "fastboot flash bootloader bootloader.img" commands will likely fail due to version mismatches. This is ok.
-The "fastboot flash modem NON-HLOS.bin" tends to fail too. For this, just run the command again until it succeeds.
2: After flashing 24.49-18-8 take the OTA to 24.49-18-16. Reboot. OTA zip provided below if you prefer to sideload.
3: Either install the 7.0 OTA the normal way via the update center or just side load it using the directions above. I recommend side loading due to the file size being very close to 1GB.
4: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly!
For Xposed, See My Guide Here: https://forum.xda-developers.com/showpost.php?p=74014516&postcount=96
Stock MM 24.49-18-16 Recovery: https://mega.nz/#!aZpC2RzQ!Fy3GTo_XYPjB1lwuHffCUUERuvnsyvON3kS8kMJ9Cm8
Stock MM 24.49-18-16 Recovery Mirror: https://drive.google.com/file/d/0BxxRfNko9QDKNS1NdnAyZVp6dVU/view?usp=sharing
24.49-18-8 OTA to 24.49-18-16: https://mega.nz/#!yZx2FLzR!cWfKIAYe5VyuadLI55UNHJvwWU98CXUi1g0DO1pDoKg
NPH25.200-22 OTA: https://mega.nz/#!HVhWWLxK!h-8G3vO3Sye_YwypyIJyWb2_79Ow34vNiDnMl2Q8uJg
NPH25.200-22 OTA Mirror: https://drive.google.com/file/d/0B3gPYUZ4nRLwOHJKQnNYczNEMHc/view?usp=sharing
MD5 for NPH25.200-22 OTA: 74d1a4b135200661cc4efd248f99ce33
Stock 7.0 NPH25.200-22 Recovery: https://mega.nz/#!TNoHQAjI!5U2w4p_G7pHlW6Mak7LqFR_PeWUDpSLc7S3OiUs_Qf8

Alrighty. I got back to stock 6.0 with the 18-16 update. I couldn't get the OTA via the system update, so I tried doing it via ADB. That threw up a "status 7 error". I then copied the file to my internal storage and selected update via SD Card in recovery. It hung on "Patching System Files" for a while, but in the end it moved on and worked fine. Thanks for the awesome guide!

Thread updated with downloads for the 24.49-18-8 OTA to 24.49-18-16 zip.
I exctracted the 7.0 Stock recovery to replace if you decide to flash TWRP and want to go back to the stock recovery for future updates (HAHAHA yeah right!). Download link in OP. The 7.0 Recovery is different than the MM recovery. They are not interchangeable. Don't flash the 7.0 recovery on MM.

Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?

Bwangster12 said:
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Click to expand...
Click to collapse
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.

annoyingduck said:
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
Click to expand...
Click to collapse
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?

hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?

Here's the recovery before the 7.0 one, just incase.. Was bored. Ok, I won't lie....didn't see u posted the 7.0 recovery....lol.:good::highfive:

Bwangster12 said:
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
Click to expand...
Click to collapse
Yup. TWRP flashes and works, magisk v14 works, and so far systemless xposed api24 is working.
EsteBandido4444 said:
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Click to expand...
Click to collapse
What is everyone's fascination with relocking the bootloader? You do not need to relock your bootloader. You cannot relock the bootloader unless all your system partitions match. Use my part 2 section. Read the notes, skip the bootloader lock commands. Leave your bootloader unlocked, get up and running on nougat, then you can issue the lock commands if you really want a locked bootloader.

How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
EDIT nevermind didn't read lol

Amp699435 said:
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
Click to expand...
Click to collapse
Copy the file to the root of your internal storage. Reboot into recovery. Hold power = volume up & release to access menu options. Choose apply update from storage. Select the OTA.zip package and let it install. (Directions are clearly written in OP.)

Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.

GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
Click to expand...
Click to collapse
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.

annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?

GrandAdmiral said:
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
Click to expand...
Click to collapse
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...

annoyingduck said:
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
Click to expand...
Click to collapse
Gotcha. I know I'm going to root again, but I've never used Magisk before so I wasn't sure of that piece.

annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
I am running Dirty Unicorns right now and when i looked up what I'm on in fastboot, it showed MPSH24.49-18-16. Would I just follow part 2 and use MPSH24.49-18-8 or something? I thought I had to use at least the version I'm on or newer.

GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.[/QUOTE
Your issue is that TWRP has modified your
System, any restoring of the stock rom will fail to update. So yes, you'll need to go through part 2 and downgrade and work your way back up.
Click to expand...
Click to collapse

I downloaded the zip (it took a while).
Restored to stock like 3 different ways but still hit a road block. I went the adb sideload route but got status error 7 because my build fingerprint wasn't correct. I tried searching for the right build I need, but I'm not an expert and couldn't find the right set of files that I was sure I knew how to restore. I ended up restoring my AICP backup.
If somebody could PM me and give me a hand (messaging through Hangouts or something) that would be AWESOME!
I'm planning trying to snag an XL 2 pre-order next week, but until then the less headache the better! Plus stock Nougat looks better on a Swappa listing

Trying to sideload via recovery 24.49-18-16 but I keep getting "("unexpected contents:EMMC:/dev/block/bootdevice/by-name/boot...". I've also tried installing from the phone but the same error appears in recovery. Any ideas?