yashsingh1/xdaforums huggingface dataset:
[Nexus 5X General] DikStarrbuck:
Problems With rooting/Fastboot

I've been at this for a little bit and I dont know whats my issue.

So I've followed the steps as listed so far, but I am not seeing my device when I type "fastboot devices" when I put my phone into bootloader mode, but it seems to work under adb devices (after normal boot).

I thought the problem might be my firewall so I disabled that. I've uninstalled my google drivers and reinstalled them (from google driver site and Android SDK), and when the google drivers installed my phone shows up as "Android Composite ABD Interface" under type it says "Samsung". Not sure if any of that matters. When I connect my phone in bootloader mode it shows up as 'unknown device?'

Made sure USB/ADB debugging was on. So now I'm stuck. Any Advice?

I did search whats causing the issue, and I havent figured it out yet.
[Nexus 5X General] joetheshmo:
Check my post literally 4 posts above yours.
[Nexus 5X General] DikStarrbuck:
That worked, it just needs to be more clear it needed to be done while the phone was in Bootloader mode. I had tried that earlier, but didnt realize it needed to be done in bootloader.

---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------

Thanks!

Just realized I didnt thank you.
[Nexus 5X General] joetheshmo:
My bad. The quote was a post much earlier in this thread so out of context I see the confusion. Glad you got it working :)
[Nexus 5X General] Heisenberg:
This could all have something to do with you using a build from a different variant, that's a guess though.
[Nexus 5X General] redpill859:
right ok will go back to original build n wait for modified boot.img for that then cheers
[Nexus 5X General] mdrichards:
It's possible... My phone is currently rooted and still encrypted, but I didn't do it on purpose and am not sure what I did "wrong" do get it that way.

Edit: As I worked through this again, I see that I missed the step to format /data. After doing that my phone is no longer encrypted.

Also... it appears that you have the normal options to encrypt at the end of all this. So you can follow the guide and then encrypt afterwards. I'm not sure how I achieved root by not doing that step since TWRP can't interact with the encrypted partition, but I did confirm it with Titanium.
[Nexus 5X General] redpill859:
well done it rooted my phone yeay. i think it helped that i actually used the "flash" command for the twrp.img rather than "boot" duh (newbie). kept on build mdb8i but will switch back over to mda89e when/if a boot.img is available.

now trying to get viper4andriod working on the nexus 5x.
[Nexus 5X General] Ethan Allison:
I've found an issue with trying to return to stock using fastboot. If you're getting "couldn't allocate _________ bytes" or "failed to allocate ______ bytes", the normal solution is to extract the update.zip and manually flash each .img file. The problem is, once you get a system.img that's too big, it won't work. This looks like it's because of a bug with fastboot for Windows.

The easiest workaround for this is to use a Ubuntu-based live image. Get a spare USB drive and make a FAT32 partition. Then use this tool to install Lubuntu to your USB drive (or another one of your choice, but that worked for me). Reboot into your live environment and open a terminal. Run the following commands:

sudo add-apt-repository ppa:phablet-team/tools && sudo apt-get update

Then,

sudo apt-get install android-tools-adb android-tools-fastboot

Then, use the file browser tool to find the system.img on your Windows partition (it should auto-mount), and run fastboot from the terminal like you're used to.
[Nexus 5X General] dave2775:
When flashing twrp should I allow modifications or keep as read only when prompted?
[Nexus 5X General] mdrichards:
I didn't have that problem on Windows 10 with the current version tools.
[Nexus 5X General] Heisenberg:
How did you install adb/fastboot? That error ususally occurs when someone has used Minimal ADB to install it and the software is out of date.
[Nexus 5X General] evanp17:
All this talk about switching build numbers in order to root... How in the world do I do that? Just flash that factory image?

Sorry, new to nexus rooting... I'm on MDA89E.
[Nexus 5X General] redpill859:
yeah thats all i did, just reflash using MDB08I (google nexus 5x factory images) and then follow the tutorial on this page.......sorted
[Nexus 5X General] evanp17:
Awesome... are there any differences in the builds?
[Nexus 5X General] redpill859:
Tbh I'm not sure, I'd ask the more experienced member's about that cause my knowledge is a bit limited. The only issue I get is this message "error opening sys/class/backlight" in twrp. But the phone has been working smoothly since root without any errors.

If a modified boot.IMG for MDA89E becomes available then its likely I'll flash it back as I'd want to keep my phone as stable as I can.
[Nexus 5X General] btort1:
After 3 hours trying to figure out why it wasn't letting me fastboot system.img I installed full android sdk tools and a few things and it WORKED

Maybe add in the OP that mini adb installs cause these problems :good: I wasted 3-4 hours trying over and over to flash that damn system image :crying:
[Nexus 5X General] Heisenberg:
Good idea, I'll add that info.
[Nexus 5X General] xyverz:
This was new to me. I guess gone are the days of unlocking before booting up for the first time, 'eh?

I did notice after I'd unlocked that I now get a security warning message due to unlocking the bootloader. I wonder if this is going to cause problems with the OTA updates?
[Nexus 5X General] mlj11:
[MENTION=4153349]Heisenberg[/MENTION]

Could you mention in the OP how to / whether it's possible to have encryption after rooting, and what the consequences of encryption vs non-encryption are?

I'm not sure where to find a definitive answer on this.
[Nexus 5X General] Heisenberg:
Theoretically that should be possible, as only /data is encrypted, and SuperSU resides in the /system partition. The only reason we've needed to disable encryption is so that TWRP can actually read the /data partition in order to install the SuperSU zip which resides on it. Once this has been achieved I see no reason why you couldn't encrypt again. Keep in mind though that once you're encrypted TWRP becomes essentially useless as it'll no longer have access to the /data partition. This means no installing, no making backups, nothing to do with the /data partition at all. As for the benefits of encryption, the only real benefit is obviously security. Some people claim that decryption yields better read/write times, but I've seen the results of some testing of encrypted read/write vs decrypted read/write, the difference is minuscule and negligible.
[Nexus 5X General] dave2775:
So in other words if your still encrypted there is no way to nandroid?
[Nexus 5X General] MrCDWJR:
Everything worked like a charm for me!
[Nexus 5X General] jackdubl:
Right, not until twrp team figures out how to decrypt.
[Nexus 5X General] remo0073:
Temper flag

Don't know if already asked:

Does the Nexus 5X has a "temper flag" similar to "old" Nexus 5?

Is it possible to reset it to return completely stock (for warranty)?

(see similar situation for Nexus 5 in this tread by [MENTION=4346614]abaaaabbbb63[/MENTION])
[Nexus 5X General] AtField:
I tried to search here on xda but I didnt find anything. I already rooted my nexus 5x, and if I try the command fastboot oem device-info it shows the following results:

device tampered: false

device unlocked: true

off-mode-charge:true

display panel:

If your device (or anyone else's device) is not rooted and want to try the same command and post here the results maybe we will discover something!

Edit: theoretically since i'm rooted tampered flag should be true, not false. I'm 99% confident that if i unroot and block the bootloader the tamper flag remains false instead the device unlocked flag goes back to false.
[Nexus 5X General] remo0073:
I'm not rooted yet but I can't run Fastboot because this week end I'm not at home so I can't verify "device-info" command.

I will be able to do it next Monday

Thanks for your help!

Inviato dal mio Nexus 5X utilizzando Tapatalk
[Nexus 5X General] tacofromhell:
Flash twrp

Format user data

Flash rom or kernel with disabled force encryption. I think systemless root works as well

Boot phone
[Nexus 5X General] remo0073:
"fastboot oem unlock" or "fastboot flash unlock"

Don't know if already asked

Which is the right Fastboot command to unlock Nexus 5X bootloader

fastboot oem unlock

or

fastboot flash unlock
[Nexus 5X General] SlimSnoopOS:
Read post #1, section #1 entitled "How to Unlock Your Bootloader"
[Nexus 5X General] remo0073:
I already read post #1 but in many articles they said that there is a new command to unlock bootloader for new nexus devices (fastboot flash unlock)

so I would like to know if there is a difference between the two different commands
[Nexus 5X General] SlimSnoopOS:
Nexus 5X can use both commands. Nexus 6P requires "fastboot flashing unlock." There is no difference for the end user as both commands ultimately allow one to flash radio, bootloader, system, vendor, and boot .img files.
[Nexus 5X General] RusherDude:
Guys, I am also having problems with the USB drivers for fastboot.

I've done as the first post says and I did everything you guys said the last pages, and I'm still in the same situation (on a machine using old win XP this time).

In bootloader mode, the N5X appears as "Android", in details I see it appears with the string:

USB\VID_18D1&PID_D00D\<ID>

I've tried to manually install the "Android" device with the drivers from the Android SDK (sdk1\extras\google\usb_driver) and no dice, it doesn't accept any drivers for this device.

So I opened the supposed drivers file (android_winusb.inf) and I noticed that inside there there is no info for Nexus 5X, only for Nexus One, S, 7, Q and such devices.

Also:

DriverVer = 08/28/2014,11.0.0000.00000 <- 2014?

These are the usb drivers that the SDK downloaded..

Anyone else had this problem where the own drivers downloaded from the SDK arent accepted?

I noticed that also in Recovery sideload mode, adb works but it is recognized as a "Google Galaxy Nexus ADB Interface".. is this usual?

I don't know why this is being such a nightmare on a N5X, when it was 1 minute on the Nexus 5.........................

I just tried to use these drivers for my Nexus 5 on the bootloader, and immediatelly the devices was recognized as "Android Bootloader Interface" and later as a device and fastboot worked, but in the Nexus 5X is still is found as a "Android" not as an "Android Bootloader Interface"...
[Nexus 5X General] SlimSnoopOS:
Are you using SDK Tools 24.4.1 and Platform Tools 23.1?
[Nexus 5X General] RusherDude:
Yes, I am using...

Android SDK Tools 24.4.1

Android SDK Platform Tools 23.1

Android Support Library 23.2

Google USB Driver 11

(The last version of everything I find on the SDK Manager)

Thanks!
[Nexus 5X General] SlimSnoopOS:
Hmm, might need some other input as I use OSX. Regarding your steps, have you followed this process to force the driver install?

Edit: All while in the bootloader mode.
[Nexus 5X General] RusherDude:
Those steps is what I had to do to connect normally the device via ADB (Android Bridge Composite or so) and it worked, but now for fastboot it appears as "Android" device per se and that doesn't work anymore :(

When I select "use disk" and I select the .inf inside the usb_drivers folder, it just say that there is no sofware there for any hardware or something like that (the usual message when you don't select anything valid).

Thanks for your time!
[Nexus 5X General] Darke5tShad0w:
Try what I said here for someone else.

http://xdaforums.com/showpost.php?p=65367022&postcount=1555
[Nexus 5X General] RusherDude:
The problem is that on Windows XP, "Google" is not on the list of vendors to select :(. On Windows XP, when you first select "Don't search, I will select the driver to install", you get a menu with "Select the kind of hardware and press next", in which there are different categories (like devices) but nothing is found on any of them at all. You can also check "Show all the devices" where you get a list of vendors on the left and models on the right, but neither Google or LG are on the list. On this screen is where we also got the "Use Disk" option, but when in that option you try to select the usb drivers from google or the .inf file, it just doesnt work :(

And yes to clarify, The device is connected via USB and is on Bootloader mode. Appears as "other devices" - "Android". The fun part if that when I tried to connect via fastboot my Nexus 5, it was automatically detected as "Android Bootloader interface" as you say this will show up on the devices admin.

What a damn headache.

Thanks a lot for the help!
[Nexus 5X General] Darke5tShad0w:
Oh, I don't have any xp machines ready to test with anymore. I'll see if i can get install it on an old laptop later to test.

You could try downloading Ubuntu and running it from a live environment from a cd or usb to get passed this issue for now. Adb is already built in, just launch the terminal and type the commands.
[Nexus 5X General] RusherDude:
Not a bad idea for a test, adb is built in? interesting. Is fastboot built in too?

Btw, I am finding in some google post that people recommends installing the "LG Drivers" for Nexus 5x, "LG-Mobile-Driver_v3.14.1.zip". I don't remember having to install any LG drivers for the Nexus 5, maybe im skipping this for the N5X? or it is not necessary at all?

Thanks a lot for the support! very appreciated :fingers-crossed:
[Nexus 5X General] Darke5tShad0w:
The only thing I had to was manually select the fastboot drivers.

Yip everything is built in and ready to go.
[Nexus 5X General] RusherDude:
Thanks! I've tried with ubuntu live cd and in 15mins I had unlocked bootloader and such, its not pre-built into Ubuntu (you got to enable "Universal" I think it was option in settings and the use apt-get), but it works (you need to use sudo for fastboot, if anyone is trying and it gives a "no permission" error).

However, I'd like to get a solution for fastboot working in WinXP since having to boot into this live Cd everytime I need to use fasboot (every monthly update or even more..)... kinda sux :(

Thanks a ton for your help! :good:

PS: TRWP doesn't seem to stick on the N5X, at least the first 2 times.. is this common in this device?
[Nexus 5X General] Darke5tShad0w:
Thanks for correcting me, Its always apart of my install so I had not realized. :o

Sorry! I totally forgot to tell you this!

Glad you finally got there!

Not that im aware it should stick the first time.

Im currently installing XP in a VM, I would prefer to try on my other laptop but its unavailable at the moment.
[Nexus 5X General] RusherDude:
No problem haha, you helped enough :laugh::laugh:

For some reason it failed to stick first 2 times o.O, but well, it sticked finally so doesn't matter. I also remember that my N5 started having sticking problems since 6.0.1 came out so maybe this is just random.

Thanks a lot!! I wish you find a solution for winXP, im tired of trying everything :crying::crying:
[Nexus 5X General] Darke5tShad0w:
Came up against the same issue, Tried all my best and I couldn't over come it for you. (This was in a virtual machine).

Maybe XP isn't compatible with that part of the 5X?

Maybe contact google and ask or you could try a dual boot with ubuntu. Easy to do and you only need to switch to it for 5mins once a month.

Edit:

Maybe check this out

http://xdaforums.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
[Nexus 5X General] RusherDude:
It would be retarded for google to support ADB and not Fasboot... kinda half-assed drivers stuff.

Where should Google be contacted about this? Honestly I don't have any idea of what section of Google should be contacted and where :(.

Ubuntu dual boot is an option yes but needing to change SO to use fasbot is terrible considering I can adb -.-

About toolkits, I don't use em, problems assured :P

Thanks a lot!
[Nexus 5X General] Darke5tShad0w:
Im not sure, maybe search 5x support in google?

Yes it would be a terrible idea for them to do that.

Yes thats why i didn't suggest a toolkit earlier but I thought it might install the fastboot drivers.
[Nexus 5X General] qu4nd:
So, since a format userdata shouldn't be needed in TWRP 3, how is decryption ensured? Some kind of TWRP voodoo? [emoji16]
[Nexus 5X General] tacofromhell:
Who said format userdata wasn't needed to decrypt?
[Nexus 5X General] qu4nd:
I misunderstood the op I guess.

It says:

But that means you don't need to decrypt for TWRP, not that you don't need it for decryption, doesn't it? Sorry for confusion ^^
[Nexus 5X General] SlimSnoopOS:
You are misinterpreting what is written. Initial versions of TWRP 2.8 could not read the internal storage so formatting userdata was necessary in order for TWRP to work. This is no longer the case, so you can be encrypted and use TWRP as intended.

If you want to decrypt, then yes you need to format internal storage in TWRP or fastboot format userdata. Flash a kernel which disables "force encrypt" next, of course or root.
[Nexus 5X General] qu4nd:
Yep, makes way more sense now ^^ I'll have to look for a kernel now ;)
[Nexus 5X General] fire7777777:
guys which version of supersu can i flash? i have MMB29Q
[Nexus 5X General] joetheshmo:
Current system root is 2.65
[Nexus 5X General] blackangel10:
...

hi guys, im the only one that after had unlocked the bootloader can't flash the twrp or do anything else becouse from prompt "adb devices" doesnt show my 5x from bootloader mode.... if i start my android if i'll type this command my phone code will show !! :eek:

im running win10x64, i've tried the sdk google drivers..clockwork generic ones...and many others everytime with the same results...

can someone help me to found it this mistery?? :)
[Nexus 5X General] joetheshmo:
Did you try manually adding the driver while your phone is booted into bootloader? I've answered this question a few times in this thread. You'll need to use device manager and point it to the SDK drivers
[Nexus 5X General] fire7777777:
Thanks

Inviato dal mio Nexus 5X utilizzando Tapatalk

---------- Post added at 11:35 AM ---------- Previous post was at 11:33 AM ----------

How can i wipe cache and dalvin? In the recovery fail, it tell me that unable to mount somelike as that, i have stock rom and elementalx as kernel mmh

Inviato dal mio Nexus 5X utilizzando Tapatalk

---------- Post added at 11:35 AM ---------- Previous post was at 11:35 AM ----------

Twrp as recovery mmh

Inviato dal mio Nexus 5X utilizzando Tapatalk
[Nexus 5X General] qu4nd:
I would suggest you to share the exact error message with us...
[Nexus 5X General] berndblb:
That's working as intended. You use fastboot in bootloader, adb in Android or recovery.

Try "fastboot devices"
[Nexus 5X General] blackangel10:
ill try as you wrote here...

in another forum someone reply me its normale that i cant see in bootloader the adb device...:eek:
[Nexus 5X General] joetheshmo:
That's because you will use the command fastboot devices
[Nexus 5X General] blackangel10:
hi, fastboot devices in bootloader mode its working!

i've asked this question becouse in many guides i had read that adb devices have to work also in bootloader mode...

anyway...thanks for your time!:)
[Nexus 5X General] sasank360:
Hello everyone. I flashed twrp on my nexus 5x, following this thread. Everything is working great. :)

However I noticed something. When I choose backup in twrp, in the list of partitions to backup,

I have system (about 1gb) and system image (3gb :eek:). Then vendor and Vendor Image.

Do we have to backup the images of system and vendors ?? or backing up the partitions is sufficient.

Any ideas ? Thanks in advance. :)

PS :: I have 16gb variant, so when i include system image (3gb), I occupies a huge chunk of storage on phone. :(

I will upload screenshot or pic soon.
[Nexus 5X General] Mawth:
Stick with the TWRP backup defaults: Boot; System; Data. To restore the system, there's no need to backup the others like System Image; Vendor; Vendor Image. The defaults do the job.
[Nexus 5X General] sasank360:
Thanks for quick reply. Thats what i ended up doing. :)

System, boot, data, cache, efs. Thanks again. Cheers. :good:
[Nexus 5X General] qu4nd:
There's usually no need to back up cache. And you're fine with efs if you back it up separately once and keep that backup.
[Nexus 5X General] jlmcr87:
TWRP is not working with the latest March update,it ask for a password. Can´t root the phone.........
[Nexus 5X General] SlimSnoopOS:
What happens when you type: default_password

Also which factory image are you on? We have two.

Edit: Idk if there's a simple solution. Reading the comments section of Android Police's March Nexus post, someone thinks something is blocking decryption in TWRP in MHC19J. They used MMB29V and were able to decrypt in TWRP again.
[Nexus 5X General] rydare:
Same issue here. Can't mount user storage even after switching to password unlock (password isn't accepted). I rooted by mounting a flash drive connected via OTG cable.
[Nexus 5X General] AJ:
yep , with march update i get a message when the device boots saying there is an internal problem with your device ,

any body gets this ?
[Nexus 5X General] rydare:
I had this issue until I installed SuperSU, ElementalX, and Xposed. I also cleared cache and after doing this it went away. Not sure exactly which step did it, but I'd try clearing your cache as a first step.
[Nexus 5X General] AJ:
here is an explanation :

https://www.reddit.com/r/nexus5x/com...ij/601_mhc19j/
[Nexus 5X General] bobby janow:
Were you able to get systemless root that way? I mean could you type the echo commands in adb shell then install SuperSU from the OTG?
[Nexus 5X General] rydare:
Yes I was able to flash systemless SuperSU, ElementalX kernel and Xposed just from having the files on the OTG connected flash drive. Since only user storage is encrypted it wasn't an issue. I also saw a workaround where you could place the files in /cache and install using TWRP from there, or you can push files using ADB apparently. I had an OTG adaptor so this was the easiest course of action for me.
[Nexus 5X General] bobby janow:
Took your advice and just flashed the J image. Installed TWRP 3.0 and got the pin code request. Cancelled it, mounted OTG, flashed SuperSU 2.68, and Osmosis busybox. Rebooted and all looks great. Restoring from Titanium now and Android Pay still works. Thanks much.
[Nexus 5X General] KANGOD:
[Solved] Which version of SuperSU should I flash?

Update: Solved. I shall use the zip version.

--------------------------------------------------------------------

Thanks, but which version of SuperSU should I flash?

I'm some a newbie now, let's clarify my question:

In the SuperSU Stable thread, there are Google Play's apk version and [http://download.chainfire.eu/supersu-stable]'s zip version.

The zip version is marked as "TWRP / FlashFire installable ZIP", so is it "the version of SuperSU that TWRP offers"? In section 2 and section 6, you motioned that the TWRP-offered SuperSU has bug. Should I get an apk version to flash?
[Nexus 5X General] SlimSnoopOS:
You can use SuperSU 2.65 to install in TWRP. TWRP 2.8 offers to install an incompatible SuperSU, TWRP 3.0 does not offer to install SuperSU at all.
[Nexus 5X General] KANGOD:
That is it. I used TWRP 3.0.0 and didn't come up with a TWRP-offered SuperSU, so I was confused with the bold attention.
[Nexus 5X General] bluey45:
Just FYI.

I noticed I had this issue too flashing the J version of the update.

I was going to do the sideload, but noticed that TWRP released a new update 3.0.0.1. I installed this version and it fixes the decryption issue when it asks you for the pattern login at the beginning.

https://dl.twrp.me/bullhead/

You can then put in your pattern and be able to install Super SU. I rebooted and all is working.