yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Q&A, Help & Troubleshooting] tudy77:
I recently bought a Nexus 6P and I just rooted it a few days ago. I have been reading about how it is less safe now that the bootloader is unlocked, so I figured I could encrypt my phone for more securities! I don't want ro re-lock since unlocking will wipe my data all over again.

So I went into Settings->Encrypt phone and started the encryption process. It first showed a green outline of an Android, then it started the boot animation. It stayed there for about half an hour and it was clearly not encrypting (not getting hot or anything) so I just rebooted (I have a backup, that's why I'm so bold :) ) and it just normally rebooted to a working phone with nothing encrypted. Tried it again, same result.

I'm running Marshmallow 6.0.1 MMB29M with TWRP, SuperSU (I'm pretty sure it's systemless) and Xposed. I'm not sure what kernel I flashed when I rooted (that is the boot.img, right?).

Is this a bug? Is it a feature? I would like to be able to encrypt my phone; does anyone have any ideas on how to achieve this, now that TWRP can decrypt stuff?

Thanks!
[Nexus 6P Q&A, Help & Troubleshooting] thodibhen:
I have the same issue with a HTC One M8 running Marshmallow 6.0 and systemless root. I've had this phone encrypted in the past but that was with standard root. Seems like systemless root and something to do with the modification of the boot image has something to do with encryption breaking.

Glad I made a nandroid before starting also, just incase.
[Nexus 6P Q&A, Help & Troubleshooting] tudy77:
I got it to work

So I just flashed the latest 6.0.1 (MMB29P) system, boot, etc. partitions because of the January security update. I folllowed Heisenberg's guide, point 10. I then had to reflash TWRP and then install SuperSU and Xposed again, because they were gone.

What this did was re-encrypt the phone, but with the default password. This basically offers no protection, with the added benefit of processor overhead. Yay :) I noticed this because it said the phone is encrypted, in Settings->Security even though it did not ask for a password at boot-time or in TWRP.

What you need to do is to remove any security you set up (just set the lockscreen unlock to "None") and then re-add it. When the phone asks if you want it to require the password at startup, say yes. It will then change the encryption password to your custom one and voila, your phone is now encrypted and uses your password/pin/pattern/whatev.
[Nexus 6P Q&A, Help & Troubleshooting] PhyscoAssassinx:
Question, is the default password: "default_password" lowercase and all? Im on the same boat you were, about to do this just to get encryption back but i want to be 100% sure of the steps lol
[Nexus 6P Q&A, Help & Troubleshooting] tudy77:
Well that's what I read here, but I never actually typed it anywhere because, from what I understand, it gets completed automatically by TWRP or Android of it is the default one.
[Nexus 6P Q&A, Help & Troubleshooting] PhyscoAssassinx:
so i dont type anything just hit enter?
[Nexus 6P Q&A, Help & Troubleshooting] tudy77:
I was not prompted to type anything
[Nexus 6P Android Development] Rapscallion16:
Link To Main Thread

About

The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!

Download

WinDroid Toolkit

Changelog

Check out this document for current and past changelogs.

Supported Devices

Check out this spreadsheet for a list of currently supported devices.

Device not supported? Make a request here!

Contribute

Check out the source code on GitHub here.

Disclaimers

Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.

I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.
[Nexus 6P Android Development] Rapscallion16:
Reserved

Reserved.
[Nexus 6P Android Development] Chord_Hugo87:
hmmm does not work for 6.0.1 mm29bn
[Nexus 6P Android Development] Rapscallion16:
WinDroid Toolkit v3.0 Is Now Out!

WinDroid Toolkit v3.0 has been released! It's a huge update with a material redesign, major recode and support for 43 new devices!

You can out more specific changes in the changelog here.

You can download the new update here.

All versions before v3.0 will not have their files updated anymore since I've moved from hosting on BasketBuild to Amazon S3. Please update to v3.0 to ensure you're getting the latest recovery and root files!
[Android One (First-Generation) Cross-Device Genera] abadyal007:
Hii guys i have download ota zip for 6.0.1 but when i install it on twrp recovery it shows error 7 ..

Can anyone one upload ota zip that can i install on my device my device is karbonn sparkle v...

Please help....
[Android One (First-Generation) Cross-Device Genera] Sachin:
Yo, just flash universal zip of 6.0.1
[Android One (First-Generation) Cross-Device Genera] abadyal007:
Yes i did that to...bt it didn't work...
[Android One (First-Generation) Cross-Device Genera] yash sharma100:
first rtell if your device is stock or rooted and on a custom recovery?

if rooted , then download 6.0.1 stock rom, if not rooted, then just wait for ota update..
[Android One (First-Generation) Cross-Device Genera] naturist:
Error 7 is usually cause of modified system files. Did you removed some system apps or installed xposed framework? If yes, the easiest way to install the ota is flash the full rom. The universal ota is already available which can be flashed in any Android one (Sprout 4) phone.

You can download the files from here:

http://xdaforums.com/showpost.php?p=64733678&postcount=238
[Android One (First-Generation) Cross-Device Genera] rajputmiles:
Faced the same problem.

I was on stock rom with twrp. Flashed thunderzap 3.5 kernal and then Super Su. No other modifications was done on my side(no system app remove and no xposed). Tried flashing 6.0.1 ota. Failed. So I think that's the kernal problem. I'm not sure though. Do we require original kernal for flashing ota in mm...

Edit update. I was wrong. Tried flashing 6.0.1 ota with official kernal too. Failed again with twrp. Then flashed with cwm, again failed error code 7 again. Let me try it with official recovery. Wait for results...
[Android One (First-Generation) Cross-Device Genera] rajputmiles:
Found the problem. It is related to the user release keys and build props. Our phone should have 6.0/MRA58N or M. But it has 4.4.4/KPW53 user release keys. See the attachment. So I searched Google. See this forum

http://xdaforums.com/oneplus-one/help/failed-zip-update-instalation-via-twrp-t3137841

It is for one plus one. But they faced the same issue. Any solution found please report.
[Android One (First-Generation) Cross-Device Genera] rajputmiles:
Found the solution.

Ota doesn't install because the recovery have wrong fingerprint of build no. The solution is very simple. Reflash 6.0 ota and do clean install. Don't flash recoevery or kernal. Now your default recovery os changed to stock again. Now download next mra58n ota. Don't download universal ota's as they might fail via stock recovery. Download device specific ota's.

And now if your build no. is mra58n then you can flash 6.0.1 ota file (75.6mb). Screenshots of successful install attached after facing same problem. Now on stock with jan patch installed too..
[General Questions and Answers] cries11:
Hello guys.

Guys can you help me find an cust rom for my lenovo a269i?
[General Questions and Answers] mohit kushwah:
GETTING SAME PROBLEM DUDE if are found than plz send me
[Shield Android TV Android Development] Rapscallion16:
Link To Main Thread

About

The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!

Download

WinDroid Toolkit

Changelog

Check out this document for current and past changelogs.

Supported Devices

Check out this spreadsheet for a list of currently supported devices.

Device not supported? Make a request here!

Contribute

Check out the source code on GitHub here.

Disclaimers

Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.

I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.
[Shield Android TV Android Development] Rapscallion16:
Reserved

Reserved.
[Shield Android TV Android Development] Lockdo6307:
I Alway love simple tools makes flashing a breeze. Thanks
[Shield Android TV Android Development] Oijkn:
Hi, thank you for this great tool but someone can confirm or proof that works good with Nvidia Shield TV, please ? Because idon't want to brick it...

Thank you !
[Shield Android TV Android Development] Globel:
did not work for me
[Shield Android TV Android Development] Oijkn:
Thank you for your feedback !

Regards.

Envoyé de mon D5803
[Shield Android TV Android Development] alero5752:
Will this wipe the current ROM back to new installation? I've used WinDroid a few months ago to root my Moto X Style (Pure) and I recall it wiping my ROM to a fresh installation. Just asking because it took me a while to install all of the current Apps and Kodi add-ons.

My main reason for wanting to root is to sideload Greenify and AdAway so that Nvidia TV will run more smoothly. Any ideas?
[Shield Android TV Android Development] Rapscallion16:
Yes, unlocking the bootloader, which is required to root, will wipe the ROM.
[Shield Android TV Android Development] maxal:
Is it not just like a factory reset, it will erase all your data so it will be like starting from new again but with a unlocked bootloader.
[Shield Android TV Android Development] Crowland:
Thank you for your kit. Please did you ever make a flashing guide as stated in the main thread ?
[Shield Android TV Android Development] daweeze02:
So no one got this to work?
[Shield Android TV Android Development] Rapscallion16:
It should be working fine. The toolkit uses this method to unlock and root, and it's seems people had success with it.
[Shield Android TV Android Development] daweeze02:
okay I have my bootlader done already, I will run it now for root and report back

---------- Post added at 01:37 AM ---------- Previous post was at 12:54 AM ----------

Not sure but it says offline the entire time but if I run adb devices I see the serial number of my shield

---------- Post added at 02:02 AM ---------- Previous post was at 01:37 AM ----------

I tried the nvidia drivers and the universal ones. Both work with adb manually but with the tool it will only see my shield in fastboot. The funny thing is I can root it manually if I just had a damn wired mouse hahaha
[Shield Android TV Android Development] cpucpr:
does this work for anyone?
[Shield Android TV Android Development] Rapscallion16:
WinDroid Toolkit v3.0 Is Now Out!

WinDroid Toolkit v3.0 has been released! It's a huge update with a material redesign, major recode and support for 43 new devices!

You can out more specific changes in the changelog here.

You can download the new update here.

All versions before v3.0 will not have their files updated anymore since I've moved from hosting on BasketBuild to Amazon S3. Please update to v3.0 to ensure you're getting the latest recovery and root files!
[Shield Android TV Android Development] visitor29:
not works for me, offline shows me but cmd works
[Shield Android TV Android Development] Rapscallion16:
That's odd. Sometimes when multiple instances of ADB are running the toolkit has a hard time recognizing devices. Go into Task Manager and end any adb.exe or fastboot.exe processes you see running then see if the toolkit will recognize your device.
[Shield Android TV Android Development] visitor29:
i tried like you advice but nothing , tried also v2.6

win 10 64bit - nstv

but from cmd recognize without problems?!
[Shield Android TV Android Development] duanim:
Thetering a recovery like the amazon fire tablet maybe an option. go to amazon FT forums in xd developers
[Shield Android TV Android Development] HeXDeMoN:
I echo what everyone else says I cant get it to detected my device even though I can still run cmds manually through command prompt
[Shield Android TV Android Development] sikkie:
+1

Same issue, not detecting Shield TV Pro in Windroid toolkit (Offline message).

CMD works just fine.

Using the official NVidia driver (SHIELD_Family_WHQL_USB_driver_201506).
[Shield Android TV Android Development] acidspider:
can anyone confirm working on android tv 3.0 marshmallow 6.0?
[Shield Android TV Android Development] mastertech007:
Is this tool dead or still working?
[Shield Android TV Android Development] savagepagan:
I'm guessing this does not work with the 500gb Pro model?
[Shield Android TV Android Development] shawly:
Still won't work with version 3.1, adb devices shows the device but WinDroid still says it's offline.
[Shield Android TV Android Development] HUYI:
it's a shame that this is no longer supported, would have made the process to root this devil device slightly easier.
[Shield Android TV Android Development] Ichijoe:
Is there such an executable that could help those with only a 4k TV get 'round the messy TWRP Black Screen SuperSU install?
[Shield Android TV Android Development] Emmeci:
so, no there is any support now?
[Shield Android TV Android Development] Desibouy:
It's been like 3 months now since the last comment, has this improved and now working?

Thanks
[Shield Android TV Android Development] jonsharky:
Hi guys and gals,

2015 Shield TV stuck in APX mode (flashed wrong rom) -- can't access fastboot -- help?
[Shield Android TV Android Development] illiam1:
Im not sure what this tool does

It asked me to download missing drivers on first startup it says downloading. I left it for 20 min before I forced stop the tool. I restarted skipped driver download selected shield as my device loaded twrp and began to flash with this tool. Let it run for 10 min. It does something but not what it claims its doing. So tool is not for me
[Shield Android TV Android Development] Jackie393:
i will try it :)
[Shield Android TV Android Development] Neuken6969:
Another dead thread ...
[Shield Android TV Android Development] ldeveraux:
It was, until you decided to revive it for some reason! Did you have a question about the sw or an issue? Or just wanted to point out that some threads just go silent of their own volition?
[Shield Android TV Android Development] Neuken6969:
The software doesn't work
[Shield Android TV Android Development] ldeveraux:
Look, if you don't want to provide any information as to what may be wrong, you're not going to receive any help.
[Shield Android TV Android Development] Neuken6969:
App shows offline, i have multiple versions of platform tools, put the app in each folder, says adb is missing and won't let me download anything,
[Shield Android TV Android Development] ldeveraux:
That still makes no sense. Can you run adb from a command line? If not you need to add it to your path.

https://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378

I haven't used this app in years, so not completely familiar with how it works. Run as Admin?
[Shield Android TV Android Development] Neuken6969:
Ty for the link, just finally got my tube after some research. android user and want to root and maybe ROM this so I can tweak it and make it better, I think I'm mdarcy but not real good info about it
[ONE Q&A, Help & Troubleshooting] saar_netzer:
Hi All,

It took me about a week to resolve this after following all the guides I could find on the Internet, using all the various tools out there and nothing worked.

I will begin describing the situation.

I have totally wiped my device, including system and OS, don't ask me why, I don't have the answer to that :silly:

What I have realized next is that the TWRP recovery is gone and all I have is a stock Cyanogenmod recovery.

Then I have found out that the bootloader is locked and I am unable to flash a new recovery.

Also, adb, require the user to approve on first connection via a message on the handset screen, however, in Stock Cyanogenmod recovery, no message appeared.

So, how do I get out of this?

At first, I have tried to make a brick from it, as in the described situation above, it was not a software brick, nor hardware brick - I call it "The Limbo state".

eventually, I have used adb version 1.0.32, it was able to access the handset via sideload update and managed to sideload "cm-11.0-XNPH22R-bacon-signed.zip" as an update (both will be linked to this post at the bottom).

So, how this was done:

1. download adb 1.0.32

2. download cm-11.0-XNPH22R-bacon-signed.zip

3. boot the handset into Cyanogenmod Stock Recovery

4. Connect the handset to the computer (I used Windows 7)

5. open cmd.exe as an administrator and cd to the location where you have extracted adb

6. On the handset go to Update-> via sideload

7. run the following commands:

7.1 adb devices (you should see your device ID and next to it it should show "sideload"

7.2 adb update <path to where cm-11.0-XNPH22R-bacon-signed.zip is located>

8. What you will see next on the handset, is that the package is being uploaded and the update begins. This phase took about 25 minutes to complete so be patient, as at some times it looked stuck but it is running.

9. When completed, I was able to reboot the handset into working state, then was able to load SuperSU and TWRP to go with the regular process of upgrading to a newer CM version ROM.

Hope you will find this helpful.

I still can't post an external link for the cm-11.0-XNPH22R-bacon-signed.zip - so you can PM me to get the link to download it.
[OnePlus X Android Development] Rapscallion16:
Link To Main Thread

About

The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!

Download

WinDroid Toolkit

Changelog

Check out this document for current and past changelogs.

Supported Devices

Check out this spreadsheet for a list of currently supported devices.

Device not supported? Make a request here!

Contribute

Check out the source code on GitHub here.

Disclaimers

Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.

I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.
[OnePlus X Android Development] Rapscallion16:
Reserved

Reserved.
[OnePlus X Android Development] saurabh40629:
Nice info, also update the pre requisite. If sdk or adb shell is required?I see, its mentioned in the original thread, you can update the same here.
[OnePlus X Android Development] parasthakur37:
[MENTION=4485224]WindyCityRockr[/MENTION] seems like a very important handy tool, thanks for this.

Wanted to know that I'm on CM12.1 and afaik there isn't a way to unlock the bootloader. Can this pretty toolkit of yours still unlock it?
[OnePlus X Android Development] The "A" Factor:
Good work!

Also Add an option to backup the EFS Partition (which has imei) and store it on PC (preferably in encrypted format). Then again an option to restore it .
[OnePlus X Android Development] saurabh40629:
You don't have any toggle in developer option like OOS but it is already unlocked, otherwise you wouldm't be able to flash other zip.
[OnePlus X Android Development] parasthakur37:
No it isn't. Because when I try to do anything from fastboot it says it's locked. I need to get past that so that it works.
[OnePlus X Android Development] saurabh40629:
May I know what you are trying to do?
[OnePlus X Android Development] s8freak:
http://xdaforums.com/showthread.php?t=3242830 This thread will tell you how to unlock your bootloader it's extremely easy to do just follow the OP. It literally took me less than 3 minutes to unlock mine.

"No soup for you!"

Sent from my Smokin E1005 Rockin Mokee Rom
[OnePlus X Android Development] parasthakur37:
Mate, I'm on cm12.1 and that guide is for OxygenOS, I guess the soup smells..
[OnePlus X Android Development] s8freak:
My bad I missed where you said you were on Cm 12.1. I was trying to help you there was no call to be rude "mate"

"No soup for you!"

Sent from my Smokin E1005 Rockin Mokee Rom
[OnePlus X Android Development] mohammedtabish:
bro u are on cm12.1 and u dinot unlocked bootloader?? what?? so how u installed twrp and flashed cm12.1??
[OnePlus X Android Development] Kenshiro79:
Also unlocks the bootloader?
[OnePlus X Android Development] Forged1ntuition:
Any way to donate to the devs?
[OnePlus X Android Development] parasthakur37:
This is the problem.

Obviously I unlocked it and flashed twrp and then installed cm12.1.

After installing cm12.1 it shows that the bl is locked.

And afaik there's no way to unlock it because there's no option in cm's dev options.
[OnePlus X Android Development] taaeem:
Since you still have TWRP backup CM flash any Oxygen OS version and enable the OEM unlock option and unlock your bootloader again
[OnePlus X Android Development] knauji:
I used windroid to unlock the bootloader before you supported OPX^^ Nice to see it here now!! thanks!
[OnePlus X Android Development] Rapscallion16:
WinDroid Toolkit v3.0 Is Now Out!

WinDroid Toolkit v3.0 has been released! It's a huge update with a material redesign, major recode and support for 43 new devices!

You can out more specific changes in the changelog here.

You can download the new update here.

All versions before v3.0 will not have their files updated anymore since I've moved from hosting on BasketBuild to Amazon S3. Please update to v3.0 to ensure you're getting the latest recovery and root files!
[OnePlus X Android Development] raj102:
Not able to install twrb with this app. Plz help. Windriod is showing device rebooting and device is in fastboot mode forever....
[OnePlus X Android Development] Aquaservice:
Good job

Enviado desde mi ONE E1003 mediante Tapatalk
[OnePlus X Android Development] motherninja:
Same here... Before OPX I successfully unlocked the Moto G 2013 (falcon), but on OPX it is hanging on Fastboot Mode forever after I clicked on Get Unlock Key. Any workaround to fix this issue? Guess I have to try manual way to unlock mine :laugh:
[OnePlus X Android Development] prabhat.singh.836:
i did similar mistake to get ota updates. my nandroid backup didn't worked either.

what i did,

1.flashed twrp

2.wiped everything using twrp.

3.fastboot oem lock - >blunder

tried to flash stock recovery and failed.

tried to use fastboot oem unlock and failed even if status shown as success.

u need to be on stock recovery to unlock bootloader.

what solved my problem,

1.twrp->flashed cm13 on locked bootloader.

2.copied stock recovery and oos 2.2.0 downloaded from oneplus official page to internal memory.

3.twrp->flashed stock recovery.

4.flashed stock os using stock recovery.

ota worked.

you can try to unlock bootloader if you want to after flashing stock recovery.
[OnePlus X Android Development] electrofryed:
Looks awesome. Has anyone seen a Linux version of this?