yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Original Android Development] mskip:
Jusdging from the google article *HERE* that message was introduced with Android M and purely means that the operating system on your device has changed from the one that came originally on your device. It does say that you can flash the latest google image to your device but it doesn't say if that will get rid of the message.

One thing I wouldn't recommend is locking the bootloader. If the phone won't boot up and you have a locked bootloader then you are stuffed. Have you flashed the stock image via the Toolkit and selected to format userdata during the flash process? I would think that would get rid of any warning as it puts your device back to a full stock state. I don't think it has anything to do with unlocking the bootloader but I could be wrong. I will have to do some trials on my Nexus 5 and try to recreate the message so I can work on how to get rid of it.

The article does say that the warning should disappear after 10 seconds or you can just press the power button to get rid of it so I wouldn't think its a major problem.

Mark.
[Nexus 5X Original Android Development] Andeh23:
That's a fair point about the locked bootloader. I was mostly concerned with being able to still receive OTAs when I'm too busy/lazy to play around with tools. I had flashed a stock image (not the one my device came with), but I did the no-encrypt option and don't recall if I selected to format userdata. That may have been the culprit. I'm in the process now of flashing the oldest available stock image, with encryption, and a format userdata. I figure that after that I should be fine, and can test my ability to receive OTAs then.

Edit: OTA worked, so I'm happy now. I haven't tried relocking to see if the red "device corrupted" warning is there, but I don't care at this point.
[Nexus 5X Original Android Development] MurdocZero:
Yes I probably meant fastboot. I used the fastboot -w update image but with the -w removed so it doesn't wipe my phone. Like I said that method always worked for my N4. However I haven't updated any of fastboot/adb stuff in a long while so that might be why it didn't play well with the bigger system.img for the n5x. Anyway the toolkit worked perfectly. Thanks for the info!
[Nexus 5X Original Android Development] RTNDO128:
How can you flash vendor.img using your toolkit? What I'm trying to accomplish is upgrading from MDB08I to MDB08M using the MDB08M factory image. I have extracted the system, vendor, and cache images and need to flash them.
[Nexus 5X Original Android Development] mskip:
Put your image files in the "put_img_files_to_flash_here\Nexus5X" folder and then select option 11 from the main menu. It should be self explanatory after that.

Mark.
[Nexus 5X Original Android Development] RTNDO128:
Mark,

That's what I tried doing earlier but there's no vendor partition to select from the list under option 11. See my attached screenshot.
[Nexus 5X Original Android Development] mskip:
If you haven't already sorted this out I have fixed the problem and uploaded a new module file.

Make sure the Toolkit is closed. Run ToolkitClean.exe and select the Nexus 5X to clean the module files. Start the Toolkit and select the Nexus 5X to download the new module files and the vendor partition should now show in the list of partitions to flash to.

Mark.
[Nexus 5X Original Android Development] RTNDO128:
Thanks, I'll check it out!

Edit: Just updated the application and the option to flash the vendor partition is there. Thanks for your work, I just donated.
[Nexus 5X Original Android Development] munozyoshi:
Hey guys, I wanted to ask a silly question. Haven't done any kind of rooting since my last Nexus phone, the Galaxy Nexus. Since then I've been using Galaxy phones. Couldn't stand it so came back to the 5X. I wanted to simply decrypt the device. I was able to do it and the phone is a lot more snappy! I keep getting a message in the beginning of boot that says the phone is corrupt. I assume its because of the encryption being disabled? I left root and locked the bootloader again.

I also noticed when I plug in my phone to a computer I can't get it to show to transfer files. I have to enable debugging so it shows up. Not a huge problem, but wanted to know if that's normal.

---------- Post added at 10:53 AM ---------- Previous post was at 10:19 AM ----------

Just did a restore out of curiosity. I flashed stock recovery, stock factory image, and locked the bootloader. The red corruption alert went away, so the phone is back to stock. However, the phone still doesn't show up on my computer. (even when selecting file transfer mode through the notification bar). Only way the phone shows up is by enabling debugging mode. Anybody have any info on this?

PTP mode also doesn't work, I hear windows do a noise like it detected the device, but doesn't show up in file explorer.
[Nexus 5X Original Android Development] baka2x:
Nevermind. I found the new superuser thread.
[Nexus 5X Original Android Development] mochamoo:
I have a 6p, my partner a 5x. Returning the 5x in order to take advantage of the $80 sale. Current one is totally stock and locked. With the new one I am thinking of unlocking and rooting it right out of the box. If using TWRP then I don't need to worry about decrypting it right? Or should I do it anyhow?

The 5x will be mostly stock. Rooting mainly for adaway and backups.
[Nexus 5X Original Android Development] mskip:
TWRP now supports decrypting in recovery on the Nexus 5X and Nexus 6P so you will not need to decrypt your device before rooting it. If you want to then its totally up to you but its not required (I personally do though).

Mark.
[Nexus 5X Original Android Development] mskip:
The boot image is modified to allow decryption. This is what the system picks up but the message only shows at boot up and is not a threat to the system operation. IF you want the device decrypted or rooted then its a small price to pay.

Usb debugging needs to be enabled to allow communication with your pc. Yes it is normal.

Mark.
[Nexus 5X Original Android Development] mskip:
Now working on adding 6.0.1 support for the Nexus 5X and adding the systemless root method by chainfire. Hopefully I can finish it before I go to sleep but if not it will definitely be done tomorrow.

Mark.
[Nexus 5X Original Android Development] MultiKoopa:
I am having this same issue. Is it because I'm on Windows 10? :\
[Nexus 5X Original Android Development] mskip:
Which issue?

Mark.
[Nexus 5X Original Android Development] mskip:
DEVICE MODULE V1.0.7 UPDATE AVAILABLE FOR ALL USERS (PRO AND PUBLIC)

Changelog:

+Added Support [including stable root] for Android 6.0.1 MMB29K

+Added 6.0.1 MMB29K stock image to download/flash directly from Toolkit

+Added SuperSU systemless root method for rooting without having to flash a patched boot image first

+Added description of each root method in the root selection screen to explain the differences and make it easier to decide which to choose

+Made some changes and improvements to the config module code

Pro users can just start the Toolkit as normal. After you have selected your device you will be notified there is an update available and can auto update. SIMPLE.

Non Pro users have a few extra steps.

FIRSTLY DOWNLOAD THE LATEST TOOLKIT FROM *HERE* (UPDATED 09TH DEC 2015 TO 1.4.4) TO ENABLE THE SUPERSU SYSTEMLESS ROOT METHOD TO WORK PROPERLY. IF THIS IS NOT DONE THERE WILL BE ERRORS.

1. Exit the Toolkit if it is open.

2. Run ToolkitClean.exe from the intallation folder (or the Start Menu)

3. Select the device from the list

4. Type ‘y’ or ‘yes’ (without the quotes) to delete the existing module files and settings for the device

5. Restart the Toolkit, select the device and new module files will be downloaded/installed

If you download the new module files without installing the updated Toolkit then you will be prompted to update to the latest version after selecting your device.

If you want to donate to the Nexus 5X project please do it through the Toolkit (after selecting the device at startup) so you get the right code fast.

Enjoy, Mark.
[Nexus 5X Original Android Development] crispy1:
I checked the FAQ but couldn't find this answer. On Nexus 5x, can I use the toolkit to root & install SU but leave stock recovery so I can continue to get OTAs from Google?
[Nexus 5X Original Android Development] mskip:
Modern OTA's now check the complete system blob so if the standard root method is used then OTA will break (even if the custom recovery is booted rather than flashed). You can use the SuperSU systemless root method included in the Toolkit to root and you should then still be able to take OTA updates. All the root methods boot the custom recovery image so the stock image is left untouched, unless you select the ALLINONE option which will flash TWRP to the device.

Mark.
[Nexus 5X Original Android Development] crispy1:
One more question... If I use the systemless root method so I can still get OTAs, will the next OTA break root? Then I just redo root with the toolkit?
[Nexus 5X Original Android Development] mskip:
You can still get OTA's as the system is not modified (as long as you don't flash custom recovery), the OTA will break root but you can reroot after.

Mark.
[Nexus 5X Original Android Development] crispy1:
OK, really, this is the LAST question (maybe). Just got Pro version. Simple.

With systemless root, will Android Pay still work? Hire did this root approach affect encryption?
[Nexus 5X Original Android Development] raZr87:
Could someone pls tell me where i can find the Systemless Root Option in Toolkit menu ? been searching for over an hour and cant find it.

Thanks in advance

EDIT: Or isn´t this possible for newest version 6.0.1 ? Cant find the option to do it in Toolkit ?!
[Nexus 5X Original Android Development] mskip:
Just follow any of the rooting options (4,1 4,2 4,3) and it will lead you to the root method options (after asking if you want to push the file or use openrecoveryscript method). For Android 6+ you will be given a choice of SuperSU Beta or SuperSU systemless.

Also which version of the Nexus 5X module are you using? The latest version is 1.0.7 which you need to be using to have the systemless root option. Follow the upgrade info if you are using an older version.

Mark.
[Nexus 5X Original Android Development] mskip:
I don't know if Android Pay will still work as I have never used it (not available in england). Try it.

Encryption isn't affected by rooting.

Mark.
[Nexus 5X Original Android Development] jeweettoch:
FIX BELOW:

Hi Mark, first of all, thanks for this great tool.

I managed to root my nexus 5x, but i can't get into WTRP anymore. It only worked the first time while rooting. Now everytime i try to get into Recovery it hangs on the "your device can't be checked for corruption" screen. But before i tried options 5 and 6 from the tool I saw the "android robot laying on the ground with the red exclamation mark" screen.

With option 5 i had the "remote: dtb not found" error right after booting.

With option 6 i had the "device (null) not found" error right after booting.

Any suggestions how to fix this? Thanks.

EDIT: FIXED IT by installing flashify from play store. Flashing a custom rom as we speak :)
[Nexus 5X Original Android Development] mskip:
Im glad you fixed your problem.

I think you may have selected the wrong device at startup (maybe the Nexus 5 instead of the 5X). The only custom recovery available on the Nexus 5X is TWRP so it would have been impossible to select of flash clockworkmod as shown in your screenshot. This would also account for the problems with recovery. You could confirm this by restarting the Toolkit and the last selected device would be shown at the bottom.

Mark.
[Nexus 5X Original Android Development] Criton30:
Working great, thanks.
[Nexus 5X Original Android Development] insang-droid:
I used this tool kit to root and install recovery. But when I try to boot in to recovery I get the stock recovery.. What does that mean? It reverted back to stock? Did I make a wrong selection in one of the steps
[Nexus 5X Original Android Development] mskip:
Select option 5 to rename the stock recovery restore files. This will stop the stock recovery being reflashed on a reboot.

Mark.
[Nexus 5X Original Android Development] frewys:
Truly looking forward to the MMB29P update :good:
[Nexus 5X Original Android Development] mskip:
Device Module Auto Update Available for Pro version

Changelog:

Nexus 5X update [V1.0.8] 05TH JAN 2016

+Added Support [including systemless root] for Android 6.0.1 MMB29P

+Added 6.0.1 MMB29P stock image to download/flash directly from Toolkit

+Updated checksum file for verifying stock image download

If you don’t have the pro version you can download the Toolkit from http://www.skipsoft.net/?page_id=1069 and donate to the device module at http://www.skipsoft.net/?page_id=703 or directly through the Toolkit. Enter your activation code when received and autoupdate to the latest version.

Public updates will be made available soon. I am in the middle of updating the Samsung device modules (long overdue) and had to stop to update the Nexus modules for the latest builds.

Mark.
[Nexus 5X Original Android Development] frewys:
Such a great tool. Worth donating. Thanks ?
[Nexus 5X Original Android Development] Jason_MCG:
I'm using a Macbook. I install the drivers manually. Can I use the toolkit to root my device as easily as I could on a PC? Sorry for the question but in my experience, something that seems to good to be true when it comes to rooting usually is.

Edit: Nevermind. Seems it's an .exe file.
[Nexus 5X Original Android Development] RTwoD2:
MSkip just wanted to give you a heads up, I encountered an issue but am unsure if it was user error, something else I did, or the Toolkit.

Used (awesome) Toolkit to unlock, dencrypt, and systemless root. Root was achieved.

Then did the build prop edit to unlock tethering. According to the thread it hasn't effected anyone's Android Pay.

Then checked into Android Pay, check failed. I have root but there is no SU folder in my root directory, its in xbin. Disabled SU from app. Reinstall binary update fails, but I still have root. Should it not be in Xbin and did the Toolkit put it there or did I pick the wrong option? I'm being told SU should be in the root directory in-between storage and sys.
[Nexus 5X Original Android Development] insang-droid:
OK perfect.. So I did that, but when doing this it prevents me from taking the OTA. So I"m trying to revert the process manually. I found this on your website.

Use ES File Manager or Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit.

I found the /system/recovery-from-boot.p.bak and renamed it,

but I can't find the /system/etc/install-recovery.sh ???

does the toolkit delete this file? I mean I can flash the stock recovery and take the OTA.. but I'd still like to know if this process is reversible.
[Nexus 5X Original Android Development] mskip:
Yes the systemless method should put itself in the /SU folder. The SuperSU systemless zip performs a number of checks when it installs so im guessing it put itself in the xbin folder for some reason.

Did you install systemless root on a clean system or had you previously rooted?

If you are having problems then I would advise making a backup of your installed apps/data then flash the latest build (formatting userdata on the way) then try rooting again and see what happens. If you don't want to wipe your device then just try running the root procedure again and see if that fixes anything.

Mark.
[Nexus 5X Original Android Development] mskip:
If you make any change to the system partition (rooting, renaming recovery restore files) then it will break the OTA process. If you renamed the recovery-from-boot.p.bak file then im assuming you have rooted. If you rooted with the systemless method then it will not interfere with OTA but any other root method will require you to flash a stock system image to allow future OTA's.

The Toolkit does not rename the install-recovery.sh if the device is rooted as SuperSU uses that file (so the toolkit does not touch it). You also need to flash back the stock recovery image if you have flashed twrp. Do your reversing and see if the OTA will go on. It will soon tell you if it won't.

MArk.
[Nexus 5X Original Android Development] mskip:
Device Module Auto Update Available

This has been a special round of updates for the latest google monthly updates and does not affect my commitment to updating the Samsung modules with the latest builds and procedures.

02ND FEB 2016

+Added Support [including systemless root] for Android 6.0.1 MMB29Q

+Added Android 6.0.1 MMB29Q stock image to download/flash directly from Toolkit

+Updated checksum file for verifying stock image download

+Minor updates and bug fixes

29TH JAN 2016

+Reconfigured root routines for a more logical [easier to follow] flow

+Added alternative locations to push file to if root/push file fails [automatic]

+Fixed some bugs when booting to various modes

+Updated/Added some more text to root routines to make it easier to understand

+Added a refresh screen option on build selection screen for plugging in device

+Updated the Any Build option to work correctly with any Android version/Build

If you want to donate to a device project to receive the pro updates please do it through the Toolkit (after selecting the device at startup) so you get the right code fast. Alternatively you can go to http://www.skipsoft.net/?page_id=703 and select the device you wish to activate.

Enjoy, Mark.
[Nexus 5X Original Android Development] yanleites:
Hi.

Can I decrypt on the Android N with this tool?

The phone is now encrypted....

Thank you!
[Nexus 5X Original Android Development] Doctorimpossible:
For some reason I can't seem to be able to make a nandroid using TWRP 3.0.0. or 2.8.7 (the version that comes with the toolkit). I boot into TWRP and but the option still says disabled; boot into TWRP. I tried flashing the set version of TWRP and then trying it but that didn't help. I've tried 2 different computers and used the check drivers feature. Nothing has worked.
[Nexus 5X Original Android Development] breizhim:
Thank you so much for this usefull tool. I have the PRO version for my Nexus 5X. Since last update (1st march, build MHC19J), TWRP 2.8.7.2 seems to be unable to decrypt the device. I didn't find yet a way to resolve this problem. So my device still unrooted since 2 hours (i'm dying ^^).
[Nexus 5X Original Android Development] mochamoo:
Install the updated TWRP. This will fix your problem.

http://xdaforums.com/show...&postcount=704
[Nexus 5X Original Android Development] mosespce:
Whats wrong with servers terrible transfer ;(
[Nexus 5X Original Android Development] breizhim:
I was unable to open your link, but i found the version 3.0.0.1 of TWRP. It works. Thank you for the advice.
[Nexus 5X Original Android Development] hilla_killa:
I have had my 5x for a while am a complete noob to this used to odin and Samsung. But im ready to flash recovery can tgis backup my phone before i unlock bootloader on stock unrooted. Dont wanna lose everything thanks
[Nexus 5X Original Android Development] jdaclutch:
think I just bricked my phone cuz a bad usb port during sideloading ota.zip. is this tool able to help me force to unlock bootloader? cuz I can't boot up the device and select Device corrupted, enable oem unlock. any help would be appreciated
[Nexus 5X Original Android Development] seugene:
Nexus 5X comes with USB type C cable, but my laptop only has type A jacks, so I guess in order to use the Toolkit, I need to get either an extra cable, or an adaptor.

But then I see that these adaptors or cables can apparently burn your laptop's USB ports, because the phone may try to pull 3A current, which the ports cannot support. See http://www.androidpolice.com/2016/0...ous-on-paper-it-allegedly-fried-his-hardware/.

So, how do I chose the adaptor or the cable to buy? Is an adaptor or a cable better, or no difference?

I only need these cables when using the Toolkit, because otherwise, my file transfer is all wireless. Can the Toolkit talk to the phone wirelessly, like through Bluetooth or something? I doubt it, but I thought I'd ask.
[Nexus 5X Original Android Development] mskip:
I appologise that I have taken soo long with the March updates. Family emergencies and a car crash to deal with took my time away from other things. March updates are now being rolled out to all Nexus devices and April updates will be completed within 2 days of the images being released by google (usually within the first week of the month). I understand peoples frustrations after paying for pro versions but I assure those people that it's worth it. I have also spent more time testing than normal because I wanted to make sure twrp 3 was fully compatible and would not mess things up. That's all.

---

AUTOUPDATE AVAILABLE FOR NEXUS 5X DEVICE MODULE 1.1.2 [PRO ONLY]

Changelog:

+Added Support [including root,systemless root] for Android 6.0.1 MMB29V, MHC19J

+Added above stock images to download/flash directly from Toolkit

+Updated checksum file for verifying stock image download

+Updated TWRP custom recovery to 3.0.0.1 for standard and openrecoveryscript use

+Enabled ALLINONE and openrecoveryscript options for public testing

+Made some changes to root procedures and reboot procedures

I updated public (free) versions a few weeks ago. Someone was supposed to post that in here but they didn't, sorry. It is 1.1.1 for now but I will update it to the latest once I have completed some more updates and added the Samsung Galaxy S7 modules to the Toolkit.

To update to 1.1.1, Non Pro users have a few steps (if you have already downloaded previous versions).

1. Exit the Toolkit if it is open.

2. Run ToolkitClean.exe from the installation folder (or the Start Menu)

3. Select your device from the list

4. Type ‘y’ or ‘yes’ (without the quotes) to delete the existing module files and settings for the device

5. Restart the Toolkit, select the device and new module files will be downloaded/installed

If you download the new module files without installing the updated Toolkit then you will be prompted to update to the latest version after selecting your device.

If you want to donate to a device project please do it through the Toolkit (after selecting the device at startup) or from the link at http://www.skipsoft.net/?page_id=703 so you get the right code fast.

Enjoy, Mark.
[Nexus 5X Original Android Development] JoaoVr:
Using your tool! Many thanks! Helped a lot!
[Nexus 5X Original Android Development] mskip:
AUTOUPDATE AVAILABLE FOR NEXUS 5X DEVICE MODULE 1.1.3 [PRO ONLY]

Changelog:

+Google April Updates

+Added Support [including root,systemless root] for Android 6.0.1 MHC19Q

+Added above stock images to download/flash directly from Toolkit

+Updated checksum file for verifying stock image download

+Updated TWRP custom recovery to 3.0.2.0 for standard and openrecoveryscript use

+Minor updates and bug fixes

I will update the current version to public once I have added the Samsung Galaxy S7 and S7 Edge modules to the Toolkit.

If you want to donate to a device project please do it through the Toolkit (after selecting the device at startup) or from the link at http://www.skipsoft.net/?page_id=703 so you get the right code fast.

Enjoy, Mark.