Related
How to Achieve Permanent Root and S-Off:
To get permanent root, you need to S-Off. So lets start with that first. This process will NOT wipe your device. It also works for OS X users. This guide will work on software version 1.55.605.2 (which as of 04/19/2014 is the latest OTA) and below.
--- S-OFF Instructions ---First, you'll need to download adb, enable its use and setup debugging.
adb is part of the android SDK. You can download it here (OS X users must scroll down and download the OS X version). It does not need to be installed, just unzip it into its own folder. You can also download a zip that contain only adb and fastboot.
once you have adb, you'll need to download the drive for your M8, which can be had from HTC's driver page:
http://www.htc.com/us/software/htc-sync-manager/.
Then install it. It will install the driver necessary for adb to work. After the installation is finished, uninstall HTC Sync immediately (do this regardless of whether or not you need it; you can reinstall it later if you still want it). This will leave the driver package installed, but remove HTC sync.
Now, back to the phone. Disable all security you have on, including PINs, Pattern Locks, passwords, etc. If you have an exchange forced security policy, you will need to disable the account. You can readd it later.
Enable access to developer options. Jump into the Settings. Then you’re going to scroll down to the bottom and tap on ‘About’, next tap on ‘Software Information’. Now you’ll need to tap on ‘More’, which will give you a new menu. Now just tap on the build number 9 times and you’ll enable Developer options.
Go into developer options menu and enable USB Debugging.
Next, go to Security page and enable "Unknown sources".
Now install weaksauce from here:
http://forum.xda-developers.com/showthread.php?t=2699089
If you followed the directions correctly, you should have SuperSU installed and root access. (You can use superuser as well).
Plug in your phone into your computer. Its best to use the factory cable provided with the phone. Use a USB 2.0 type port if possible (USB3.0 ports typically have a blue tab; I have personally used a USB 3.0 Device on Windows 8.1u to perform this without any problems, but your mileage may vary).
Your phone will ask if you if you trust your computer (RSA). Choose "Always Allow".
Ensure adb is working by opening a command prompt (terminal on OS X), navigate to the adt-bundle-[XXXXX]/sdk/platform-tools and typing "adb devices" without quotes. Your phone should show up. Ensure the working directory is the directory that adb is in. Otherwise, transferring firewater may fail. On Windows, you can shift-right-click inside the folder adb is in and click open command prompt to open a cmd in that directory.
Now go download firewater from here:
http://firewater-soff.com/instructions/ Make sure to use the weaksauce method (second method). Do NOT use the temproot method.
The firewater file should be called "firewater" without any quotes or extensions (like .bin). Ensure your browser did not partially download or corrupt it.** Make sure its in the same folder as adb. Then follow directions on the firewater site. Be aware the yes/no prompt is case sensitive, so make sure to answer it with an uppercase Y as in "Yes" not "yes". During the process, you will need to enable adb shell to get root. Make sure your phone screen is on so you can see the root request. Grant it and the S-Off process will continue. Otherwise, it will hang there and eventually time out. Sometimes, the process will fail and the phone will reboot. This is okay. Just restart the process. It can sometimes take multiple tries.
When completely successfully, you now have S-OFF. Your phone's bootloader is also unlocked in the process; you do NOT need to perform any additional steps to unlock the bootloader. However, you do not have permanent root. The root that weaksuace provides goes away on reboot and must be reapplied again on startup.
**The filesize seems to vary depending on what OS/browser is used to download it. It should be around 4,519,496 (on disk) in size. If you can't execute firewater, try redownloading it.
Getting permanent root:
-Flash a custom recovery and flash a zip with su.
-[Optional] Return to stock recovery This option is for people who don't want a custom recovery.
Be aware, once rooted and S-Off'ed, you do NOT need the kernel module that enables system write access*. All system changes will survive hard reboots (adb reboot).
-- Recovery Rooting: --
Move the supersu zip onto your internal sdcard. It can be downloaded here:
http://forum.xda-developers.com/showthread.php?t=1538053
You can use Superuser as well. Its your preference, but this guide uses SuperSU.
Uninstall weaksauce. It's no longer needed.
Uninstall SuperSU. It will be reinstalled when you flash the supersu zip. If you have SuperSU Pro installed, you can leave that in place, as that app only holds a key.
From adb, type:
adb reboot bootloader
Flash a custom recovery. CWM and TWRP are available. Use the fastboot method. Follow the directions here:
TWRP - http://teamw.in/project/twrp2/226
CWM - http://forum.xda-developers.com/showthread.php?t=2708520
Reboot into Recovery
Flash the supersu zip you downloaded.
Reboot and you're done. You have s-off and permanent root.
You can delete the downloaded supersu zip off your internal sdcard; its not longer needed.
-- Manual Root --Perform all steps noted in section "Recovery Rooting" above.
-Download the stock recovery:
http://forum.xda-developers.com/showthread.php?t=2723112
-Ensure the stock recovery img file is in the same folder as fastboot.
-Run the following command from command line: "fastboot flash recovery stockrecovery.img" without the quotes.
-Wait for the process to finish
-Reboot the phone. You now have the stock recovery along with root. With the stock recovery installed, you can now accept OTAs provided you haven't modified/deleted any stock system files. Any new OTAs you take will remove any files/folders you added to the system partition and will remove your root. However, with S-off, this can be undone. If you lost loot after taking an OTA, simply start from the beginning of the section "Recovery Rooting".
-- Common Tweaks --
All of these are optional and are NOT required. However, you may find some benefit to them.-- Wifi Tether Enabled --This is unnecessary if you are on a More Everything plan or are paying for hotspot/tethering. You can force enable the native tethering application:
http://forum.xda-developers.com/showthread.php?t=2708548
-- Device Wipe after ten attempts --I really dislike this "feature". Here is how to disable it. This works regardless if you enabled the security or its mandated by an exchange policy.
I use Root Explorer to make this change, but you can use any text editor. Make sure to mount system as R/W. Root explorer can do this from within the app.
Edit this file:
/system/customize/ACC/default.xml
change this:
Code:
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">10</item>
to this
Code:
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">0</item>
Reboot and its disabled.
-- Power Saver Mode --Enable "Power Saver" mode using these directions. It's disabled and hidden by default.
http://forum.xda-developers.com/showthread.php?t=2701909
-- *Unsecured Kernel --By default, the stock kernel prevents write access to /system. S-off and root should allow you to makes changes to system. However, some people have reported difficulties using ROM toolbox and other mods (like changing boot animations). In some cases, these issues can be resolved by flashing an insecure kernel:
http://forum.xda-developers.com/showthread.php?t=2708686
-- HTC Sense Broswer --The stock ROM now includes Chrome as the default browser and omits the Sense Browser. Users who prefer the Sense Browser can download it here:
http://forum.xda-developers.com/showthread.php?t=2708597
-- HTC Flashlight --The stock HTC flashlight app.
http://forum.xda-developers.com/showthread.php?t=2697025
-- Disable HTC Sync Virtual CDROM --This disables the virtual CD-ROM from mounting.
http://forum.xda-developers.com/showthread.php?t=2709386
-- Donations --Don't forget to donate to the developers involved in getting you here. Donations for firecracker go to [email protected] (paypal). Donations for weaksuace go to [email protected] (paypal). If I missed anyone, let me know.
FAQBeen getting some interesting PMs. Here is some of the popular questions.
Do I need a Java card for this?
No. You just need a PC/Mac, a USB 2.0 cable and the M8. Since a public S-off method is now available, that method is obsolete and its not recommended anymore.
Do I have to change or reset my CID?
No, that is only necessary for people who s-off'ed via a Javacard.
Do I need to do any of this if I S-off'ed via Javacard?
No, this method ends with the same result.
Can I reverse this and return to completely stock?
Yes, absolutely none of the stuff done here is permanent. You can unroot, relock the bootloader, and S-On as many times as you want. You can flash an HTC RUU to return to completely stock in one go. Note: Be careful with S-On'ing a device. If you S-On a device via a newer RUU and that RUU has no known exploits, you may not be able to S-Off again until an exploit is found.
Do I need to unlock my bootloader after this?
No, the firewater exploit will S-Off and unlock your bootloader.
Will this work on a Mac?
Yes, please read the directions more carefully.
Will this work on USB 3.0 ports as that is all I have?
Usually. On OS X, I've had success using a USB 3.0 port (since recent MBPs only include USB 3). On Windows, the answer seems to be maybe, depending on your OS. Your best bet would be to try on a Windows 8,8.1,8.1u1 machine as that OS includes native support for USB 3.0; that way you aren't relying on vendor specific driver support like on Win7 or below. I have personally done this exploit on USB3 on a Surface Pro.
Will this brick my phone?
There is always a chance, but I have honestly never heard of such a thing happening. Worst case is usually a full reset of the phone.
Will this wipe/format the external SDcard?
No.
How do I flash this via ODIN?
This has absolutely nothing to do with ODIN. That is for Samsung devices. You should not even have ODIN running when do any part of this guide.
How to I convert to a Google Play edition ROM?
Wait for a developer to make one. I will post a link here if/when that happens.
See here:
http://forum.xda-developers.com/showthread.php?t=2716306
Does this affect Google Wallet or ISIS?
Yes and no. Google wallet works just fine. ISIS will detect its rooted and refuse to work. You'll need to shield root from ISIS to use it. Directions on how to do that can be found via google.
Will this work on non-Verizon HTC M8's?
Yes, though you will need to use a different recovery.
Will this unlock my device for other carriers?
No....because your device is already unlocked in its stock form. AWS band rules force Verizon to keep all their LTE devices unlocked.
Will this jailbreak my device?
No. Wrong type of phone.
I can get red triangle exclamation mark with a black screen. How do I fix this?
You are in the stock recovery. Hold power and volume up and you will get a menu. You can choose reboot system now to get out of there.
appreciate the write up. ill check back here when i find a reason to unlock it
Has anyone done it yet? It's just sitting at "adb wait-for-device push firewater /data/local/tmp" for at least 5 minutes now.
sfreemanoh said:
Has anyone done it yet? It's just sitting at "adb wait-for-device push firewater /data/local/tmp" for at least 5 minutes now.
Click to expand...
Click to collapse
I have done everything mentioned in this guide. And it works just fine.
Make sure you are connected via USB2. Also make sure your phone is on and unlocked (as in, no security PIN, pattern, password etc.). Is USB debugging on?
When you type "adb devices" from command prompt, is your device listed?
Yeah, nvm, it's fine now. When I first connected it via debugging, I didn't hit the "Always allow" option on my phone, so after the adb reboot it wasn't allowed to reconnect. Just had to disable debugging and re-enable it, it's all set now.
sfreemanoh said:
Yeah, nvm, it's fine now. When I first connected it via debugging, I didn't hit the "Always allow" option on my phone, so after the adb reboot it wasn't allowed to reconnect. Just had to disable debugging and re-enable it, it's all set now.
Click to expand...
Click to collapse
Cool. I'll add that to the guide.
I have not had time to thank and will.
At work and going to hook it up when I get home this morning so I hope no one screws with you guys and gets it pulled.
Very much appreciate all the work they put into it.
Thank you very much for the dummy proof write up
These guys around here are getting to good.
Thank you thank you thank you.
Worked Perfect! Thank you guys!
thank you so much! now i can sleep at night knowing that verizon doesn't have control of my device anymore haha!!
Im happy to see that s-off was achieved and Im going to unlock my phone right now
but quick question, I'm new to this s-off stuff so I don't know how it works entirely.
But once we unlock the bootloader
is there any way to lock it again in case we need to send the phone to HTC?
sorry for the noob question but just a question that popped into mind.
So I don't quite understand. I am S-off with the Unofficial CMWR from InvisibleK and I flashed SuperSU zip v1.94. Do I need the system write access kernel module to write to system or no?
Great guide by the way. Thanks
I have been trying for the past hour, but I cannot get adb to connect. Am I missing a step?
I downloaded the htc synch, installed the drivers, uninstalled synch. I already had weaksauce root. I downloaded sdk, extracted the bundle. I downloaded firewater, moved it to the same folder with adb.
Everytime I try to run adb it just scrolls and then closes almost immediately. I thought it was my java at first. I updated that. The computer says I'm connected through HTC drivers. I'm debugged/unknown sources...
Running windows 8.1 64bit. I don't know what else to do at this point.
blacknet101 said:
Im happy to see that s-off was achieved and Im going to unlock my phone right now
but quick question, I'm new to this s-off stuff so I don't know how it works entirely.
But once we unlock the bootloader
is there any way to lock it again in case we need to send the phone to HTC?
sorry for the noob question but just a question that popped into mind.
Click to expand...
Click to collapse
Absolutely. Everything in this guide can be reversed. You can return everything back to stock via an RUU.
nicholi2789 said:
So I don't quite understand. I am S-off with the Unofficial CMWR from InvisibleK and I flashed SuperSU zip v1.94. Do I need the system write access kernel module to write to system or no?
Great guide by the way. Thanks
Click to expand...
Click to collapse
You do not. I have modified and added a few system files and they have persisted through several hard reboots.
MultiDev said:
Absolutely. Everything in this guide can be reversed. You can return everything back to stock via an RUU.
Click to expand...
Click to collapse
Hmmm! Thanks for the reply buddy! may i ask? Where can we find these RUU files? In case we need to go back to Stock?
JelloB said:
I have been trying for the past hour, but I cannot get adb to connect. Am I missing a step?
I downloaded the htc synch, installed the drivers, uninstalled synch. I already had weaksauce root. I downloaded sdk, extracted the bundle. I downloaded firewater, moved it to the same folder with adb.
Everytime I try to run adb it just scrolls and then closes almost immediately. I thought it was my java at first. I updated that. The computer says I'm connected through HTC drivers.
Running windows 8.1 64bit. I don't know what else to do at this point.
Click to expand...
Click to collapse
Java has nothing to do with adb. You don't need it installed to any of this guide.
You need to use adb from a shell. On, windows, you need to open a command prompt. Type "cmd" with the start screen open and hit enter. Then at the prompt, use the "cd" command to navigate to the correct directory where adb is located.
When i run the "adb wait-for-device push firewater /data/local/tmp" command it come back with "failed to copy 'firewater' to '\data\local\tmp': Read-only file system". I'm lost. I have root access and everything.
MultiDev said:
Java has nothing to do with adb. You don't need it installed to any of this guide.
You need to use adb from a shell. On, windows, you need to open a command prompt. Type "cmd" with the start screen open and hit enter. Then at the prompt, use the "cd" command to navigate to the correct directory where adb is located.
Click to expand...
Click to collapse
I knew I was missing something simple. It's been a while since I've used adb. Will try now...thanks.
trying to modify the default.xml to get rid of the 10 try's and wipe pattern lock and it doesn't appear I have access to read write from it still... trying with the ES note editor when going to the file with ES File Explorer. I've ran the wp_mod.ko as directed and I haven't rebooted.
I'm wondering if I'm missing something, or maybe there's a better way to do it via command line?
blacknet101 said:
Hmmm! Thanks for the reply buddy! may i ask? Where can we find these RUU files? In case we need to go back to Stock?
Click to expand...
Click to collapse
They are available from HTC. I'll have to find the exact links. Also, many android sites will host them too.
Slimfast35 said:
When i run the "adb wait-for-device push firewater /data/local/tmp" command it come back with "failed to copy 'firewater' to '\data\local\tmp': Read-only file system". I'm lost. I have root access and everything.
Click to expand...
Click to collapse
You need root access to write there, shell does not normally have access. Beaware that weaksauce takes a minute or two before after a restart before enabling root again. So wait till you have access again before trying it.
meest said:
trying to modify the default.xml to get rid of the 10 try's and wipe pattern lock and it doesn't appear I have access to read write from it still... trying with the ES note editor when going to the file with ES File Explorer. I've ran the wp_mod.ko as directed and I haven't rebooted.
I'm wondering if I'm missing something, or maybe there's a better way to do it via command line?
Click to expand...
Click to collapse
You do not need the kernal module actually; I have removed that from the guide. I haven't used ES Note before, but no matter what, you must mount system as R/W before you can change anything. Its by default R/O or Read Only. Root explorer has a button that auto mounts it and then you can make your edit.
Here is how to have separate passwords for boot and screen in Lollipop encrypted devices.
There are two apps available to change encryption password in Android with encrypted data partition. Unfortunately neither works in Lollipop. Cryptfs fails to obtain root permission, although granted and another one returns errors. That leaves only adb shell commands:
1. Encrypt your lollipop with a password or pin you can live with. The phone will restart and prompt for password/pin
2. Enable USB debugging in Developer Options.
3. Allow Root access to apps and ADB.
4. Connect your device to a PC (Linux)
5. Start terminal and enter: adb shell
6. Next, enter: su
7. Pick a long password for boot, then convert it into a hex by using many online converters. Lollipop won't accept straight password.
8. Enter the following on computer terminal: vdc cryptfs changepw password "here paste your hexed password without quotes." You need the word password in the command before the hexed password
9. In about 10 seconds you should have a response 200 0 0, which means success. Any 1s in the last two digits would mean error. Your phone won't reboot during this operation, you will still have your original screen lock pin/password/pattern, but when you reboot, you would enter the new actual password (not the hexed one)
That's it. Now you have a long password for your boot and shorter one for your screen lock.
Info
Can i use Windows 7?
This guide is more or less exactly the same what was already written down on the official page over here.
You should better note that this was only tested on CyanogenMod based OS, on STock or AOKP roms that may not works or can fail/damage the data. See this comment.
Can i use Windows 7?
Click to expand...
Click to collapse
Yes, see point 4.
"This guide is more or less exactly the same what was already written down on the official page over here.
You should better note that this was only tested on CyanogenMod based OS, on STock or AOKP roms that may not works or can fail/damage the data. See this comment."
"already written down here"
Except that his app can only change password, as opposed to do encryption from scratch; and it does not work on lollipop for 3 reasons: it does not see the phone as rooted; it requires straight password, as opposed to the hexed one; and his command, while valid for kitkat, won't work on lollipop where you need to put cryptfs enablecrypto inplace password <hexed password>..
"You should better note that this was only tested on CyanogenMod based OS, on STock or AOKP roms"
Everything posted on XDA may not work or inflict damage. And by the way, do you know of any roms other than those you listed? AOSP? This will also work on AOSP, because those commands are hardcoded in Lollipop source...
It works for me, but i think that in 10 seconds only password needed to boot can change, not disk level encryption.
ultrasound1991 said:
It works for me, but i think that in 10 seconds only password needed to boot can change, not disk level encryption.
Click to expand...
Click to collapse
That's how it works. You only change the password. If you want to use long password from scratch, there is a different procedure:
1. Install your favorite lp rom
2. Set a short screen password
3. Repeat steps 2-7 in the OP
4. Then type this on your computer terminal: vdc cryptfs enablecrypto inplace password <hexed password> and press Enter
Your phone will start encrypting and in a few reboots you will get a prompt to enter your actual password.
optimumpro said:
That's how it works. You only change the password. If you want to use long password from scratch, there is a different procedure:
1. Install your favorite lp rom
2. Set a short screen password
3. Repeat steps 2-7 in the OP
4. Then type this on your computer terminal: vdc cryptfs enablecrypto inplace password <hexed password> and press Enter
Your phone will start encrypting and in a few reboots you will get a prompt to enter your actual password.
Click to expand...
Click to collapse
I did this. Now i have unlock pattern to unlock screen, and long password at boot.
Bu are you sure that this metod change disk encryption?
ultrasound1991 said:
I did this. Now i have unlock pattern to unlock screen, and long password at boot.
Bu are you sure that this metod change disk encryption?
Click to expand...
Click to collapse
If you did that on already encrypted phone, that won't change the encryption. The procedure in post #6 was for unencrypted device.
So, if you want to do everything from scratch and you alaready have encryption, you should go into recovery (TWRP) and when you are prompted for password, press cancel, then wipe system only; then wipe data only, then wipe cache. Then restore your rom. At that point, your data will be unencrypted. Then follow #6...
optimumpro said:
If you did that on already encrypted phone, that won't change the encryption. The procedure in post #6 was for unencrypted device.
So, if you want to do everything from scratch and you alaready have encryption, you should go into recovery (TWRP) and when you are prompted for password, press cancel, then wipe system only; then wipe data only, then wipe cache. Then restore your rom. At that point, your data will be unencrypted. Then follow #6...
Click to expand...
Click to collapse
Also, keep in mind that if you ever change your screen pin/paswr/pattern, that will automatically change your boot password. So after changing screen things, don't reboot and do change password via adb (that won't change the encryption, but only the boot password).
Except that his app can only change password, as opposed to do encryption from scratch; and it does not work on lollipop for 3 reasons: it does not see the phone as rooted; it requires straight password, as opposed to the hexed one; and his command, while valid for kitkat, won't work on lollipop where you need to put cryptfs enablecrypto inplace password <hexed password>..
Click to expand...
Click to collapse
Seems you not looked at this given readme/project, it is also explained for lollipop only systems and mentioned how to deal with the supolicy problem, but okay. But nice try.
Everything posted on XDA may not work or inflict damage. And by the way, do you know of any roms other than those you listed? AOSP? This will also work on AOSP, because those commands are hardcoded in Lollipop source...
Click to expand...
Click to collapse
Wrong, AOSP != STOCK, or not always but okay if you want to hold on your wrong statements, okay. Show me proof that an old S2 use the same AOSP source, you can't because there are some changes made by OEM, and not only because of the driver. But okay.
CHEF-KOCH said:
Seems you not looked at this given readme/project, it is also explained for lollipop only systems and mentioned how to deal with the supolicy problem, but okay. But nice try.
Wrong, AOSP != STOCK, or not always but okay if you want to hold on your wrong statements, okay. Show me proof that an old S2 use the same AOSP source, you can't because there are some changes made by OEM, and not only because of the driver. But okay.
Click to expand...
Click to collapse
This is just another example of facts disconnected from arguments and arguments not related to the subject of the thread. What are you trying to argue here? That my guide is wrong? That it is not working, but it is and not only for me. Just look at other posts in this thread. Are you not happy that I didn't warn that people's devices can be bricked? But everyone knows that whatever is posted on XDA is risky and can break your device. What does old S2 have to do with the guide for encrypting data on Lollipop?
I will tell you what the purpose of your argument is: you just want to show again and again what a fine expert you are, that you are better than other fine experts (who say things now that you figured out many years ago) and how stupid and ignorant the rest of the crowd here is. LOL.
This is why I say our communication is not productive. I stop here...
Thanks @optimumpro.
I encrypted nine different devices with AOSP Based ROM and encryption works.
Devices cannot be bricked during encryption process.
A device is bricked when bootloader is damaged.
Encryption process doesn't encrypt bootloader.
This guide isn't dangerous.
Each person is responsible for his actions.
...
7. Enter the following on computer terminal: vdc cryptfs changepw password "here paste your hexed password without quotes." You need the word password in the command before the hexed password
8. In about 10 seconds you should have a response 200 0 0, which means success. Any 1s in the last two digits would mean error. Your phone won't reboot during this operation, you will still have your original screen lock pin/password/pattern, but when you reboot, you would enter the new actual password (not the hexed one)
...
Click to expand...
Click to collapse
I can confirm that this process works on the Moto E (2nd Gen) GSM Global (XT1505) running 5.0.2. I was able to successfully set a different encryption password than screen lock. Here are a couple notes about my experience:
1) When I executed the cryptfs command, I did not receive any response in the adb shell. I didn't get the 200 0 0 - I didn't get anything. However, the change was successfully made and the device booted fine using the new password.
2) I had trouble getting the device to do the initial encryption. As part of my setup process I had unlocked the bootloader, rooted, then added SU. My next step was to encrypt. However, when I used the Settings -> Security -> Encrypt Phone option, the device would briefly flash the "android gear" icon, then the screen would go blank and the phone would hang. A reboot would bring the device back to life, but it would not be encrypted. I tried doing it via command line, again without success.
After quite a bit of time spent troubleshooting, the solution was to unroot the phone. I used the unroot option in the SU app. Once unrooted, the standard encryption process worked. After encryption, I re-rooted and added SU, and everything worked fine. Though I don't know the cause, it seems that having root/SU interferes with the encryption process.
Many thanks to the OP. :good:
What are you trying to argue here? That my guide is wrong? That it is not working, but it is and not only for me. Just look at other posts in this thread. Are you not happy that I didn't warn that people's devices can be bricked? But everyone knows that whatever is posted on XDA is risky and can break your device. What does old S2 have to do with the guide for encrypting data on Lollipop?
Click to expand...
Click to collapse
You have better just posted the url from the original source. I did that for you now.
This is why I say our communication is not productive. I stop here...
Click to expand...
Click to collapse
Yep, but re-quoting the same stuff what was written now 1 year in an GitHub is more productive.
OnePlus One CM12S YNG1TAS17L?
I have a OnePlus one now running the YNG1TAS17L build of CyanogenMod 12S.
I attempted to change the (boot encryption) password via the vdc cryptfs changepw password... method, to no effect.
Then I tried the cryptfs app (which has been updated with experimental Lollipop support) and it broke the encryption. (Wipe, restore from Titaniumbackup, clean up the mess, pick up the pieces...)
Does anyone have experience specifically with OnePlus One YNG1TAS17L successfully changing the (boot encryption) password, please?
I'd really rather avoid another half-day long wipe, rebuild, restore, clean up cycle... :-}
thanks,
libove said:
I have a OnePlus one now running the YNG1TAS17L build of CyanogenMod 12S.
I attempted to change the (boot encryption) password via the vdc cryptfs changepw password... method, to no effect.
Then I tried the cryptfs app (which has been updated with experimental Lollipop support) and it broke the encryption. (Wipe, restore from Titaniumbackup, clean up the mess, pick up the pieces...)
Does anyone have experience specifically with OnePlus One YNG1TAS17L successfully changing the (boot encryption) password, please?
I'd really rather avoid another half-day long wipe, rebuild, restore, clean up cycle... :-}
thanks,
Click to expand...
Click to collapse
Try to do encryption from scratch via adb. Also, you might want to untick deny root during boot in Supersu just while you are encrypting.
optimumpro said:
Try to do encryption from scratch via adb. Also, you might want to untick deny root during boot in Supersu just while you are encrypting.
Click to expand...
Click to collapse
Double-negatives, ho! "Untick deny root" -> "Tick Enable su during boot", yes? What process exactly might be requesting root during boot, when SuperSU might not be able to interactively prompt the user and so even though root would not be summarily denied, it's quite likely that the user wouldn't respond in time to grant root? We'd need to run that process ahead of time so that the user could reliably grant that permission and SuperSU could remember it.
Aside, it's kind of hard to do encryption from scratch when it's already encrypted the conventional way, since Google in its infinite wisdom has never implemented a way to decrypt storage....
So I really do need a tried, proven, true way to change the encryption boot password please - channeling Yoda, I must do or do not, there is no try
thanks,
libove said:
Double-negatives, ho! "Untick deny root" -> "Tick Enable su during boot", yes? What process exactly might be requesting root during boot, when SuperSU might not be able to interactively prompt the user and so even though root would not be summarily denied, it's quite likely that the user wouldn't respond in time to grant root? We'd need to run that process ahead of time so that the user could reliably grant that permission and SuperSU could remember it.
Aside, it's kind of hard to do encryption from scratch when it's already encrypted the conventional way, since Google in its infinite wisdom has never implemented a way to decrypt storage....
So I really do need a tried, proven, true way to change the encryption boot password please - channeling Yoda, I must do or do not, there is no try
thanks,
Click to expand...
Click to collapse
Let's start from the end: this is a proven to work way to encrypt data or change password on lollipop. Just look up the thread for multiple confirmations of success. You just haven't succeeded for various reasons (could be tens of them). You could have missed/messed a step; your root app may have interfered. Did you read a post here where another user said he had to unroot the phone to encrypt it. There is no user interaction during boot, hence Supersu offers you an option to deny all root requests. That may prevent adb access or the normal operation of vold (utility that does encryption).
If you were talking about external sd card, Google has nothing to do (no support whatsoever) with encryption. If your external card is encrypted, this was implemented by the device manufacturer. If your Oneplus was encrypted during manufacturing, you are out of luck as to disabling encryption. Also, a word of caution on using hardware crypto modules: they are all closed source and done by known "cooperators/volunteers" with three letter agencies. On all my roms I disable hardware crypto modules and hardware based key generation in kernel. I also throw out Selinux: just don't trust the bank to bank robbers.
It is not hard at all to do encryption from scratch. In fact, it is a more preferable way for security reasons (encryption with a short screen pin is weak, even if you later change the boot password, since encryption won't change, just the password).
Cryptfs app has never worked for me and nothing has been updated on authors Github since December 2014. That version positively does NOT work on lollipop. In addition, the author, I think, has an inflated view of his expertise in Android.
To sum up, you have to try again. You also need to run logcat or better dmesg during encryption, as there is no other way to find out what goes wrong there.
vdc command not found
Hi there, I just tried to follow the steps in the first post (Nexus 4 running CM12) and I got this result:
# vdc cryptfs changepw password [redacted]
No command 'vdc' found, did you mean:
Command 'tdc' from package 'tdc' (universe)
Command 'gdc' from package 'gdc' (universe)
Command 'vdr' from package 'vdr' (universe)
Command 'vlc' from package 'vlc-nox' (universe)
Command 'sdc' from package 'hpsockd' (universe)
Command 'vdu' from package 'util-vserver' (universe)
Command 'dc' from package 'dc' (main)
vdc: command not found
Is there a package I'm missing? I'm running the latest version of Linux Mint but I'm very far from being an expert.
thanks!
yhvo2gt9 said:
Hi there, I just tried to follow the steps in the first post (Nexus 4 running CM12) and I got this result:
# vdc cryptfs changepw password [redacted]
No command 'vdc' found, did you mean:
Command 'tdc' from package 'tdc' (universe)
Command 'gdc' from package 'gdc' (universe)
Command 'vdr' from package 'vdr' (universe)
Command 'vlc' from package 'vlc-nox' (universe)
Command 'sdc' from package 'hpsockd' (universe)
Command 'vdu' from package 'util-vserver' (universe)
Command 'dc' from package 'dc' (main)
vdc: command not found
Is there a package I'm missing? I'm running the latest version of Linux Mint but I'm very far from being an expert.
thanks!
Click to expand...
Click to collapse
The above indicates that your computer has no connection to your phone and you are getting responses from your Linux Mint, which obviously has no idea what vdc is. Follow your terminal screen when you do adb shell and su. After adb, your prompt should change if it works. And after su, you should get su rights on the phone and not on the computer. If after su, you get a prompt to enter your administrative password, that's a sure indication you are communicating with Linux, as opposed to Android.
Go to package manager on your PC and search for adb, install it. Then on the phone, you must enable usb debugging and allow root access to adb.
Hello,
I have Oneplus One 64 gb variant, yesterday my nephew somehow changed my phone's lock pattern and now my phone is locked. USB debugging was disabled at that time. I am not able to get into my phone through any means. I have lot of important data in my phone and don't want to hard reset my device. I found a solution online to get usb debugging on through adb , but I am a ultra noob and don't understand how that has to be done. please dumb it down so that I can save my precious data and unlock my phone when debugging gets enabled. Also I don't have any custom recovery installed on my phone.
This is what is mentioned in the solution.
"Instructions
1. You should try your pattern-cracking software (or whatsoever the genre it has) from inside the Stock Recovery to see whether it works with the former's environment (ADB shell available there or not).
2.Since I would never try step 1., I would do the following:
-For Jellybean 4.2.1:
1. Boot into Recovery and mount Data partition.
2. Open a shell on PC and type:
adb pull /data/property/persist.sys.usb.config ~/
Repace ~/ with home directory of your OS.
3. Open that file in a text editor and you would possibly see mtp written there. Change it to mtp,adb.
Note that sometimes Android doesn't understand the text file changes if the line terminator is "DOS Terminators" which Notepad would probably do on Windows (mine is Linux so no issue here).
In that case, I would suggest not using adb pull but doing:
adb shell
echo 'mtp,adb' > /data/property/persist.sys.usb.config
You may verify that the echo command overwrote the file by using:
adb pull /data/property/persist.sys.usb.config ~/
and seeing the file's content in some text editor.
4. Unmount Data and reboot into Android OS. USB Debugging would probably be enabled.
-For Lollipop 5.0:
JB 4.2.1 users can also follow this method if the previous one didn't work for them.
1. Boot into Recovery and mount Data partition.
2. Repeat step 2 and 3 used in JB 4.2.1 method.
3. We need to tweak some parameters in settings.db. Type:
adb pull /data/data/com.android.providers.settings/databases/settings.db ~/
4. Back it up at some other location too, and open the file in an SQLITE editor. I'm running Linux and DB Browser for SQLite works well. It's also available for Windows OS/OSX.
5. In the global table, change the value for:
adb_enabled to 1
development_settings_enabled to 1
6. Check that verifier_verify_adb_installs is set to 1 in the global table.
7. Check that as default, in the secure table:
adb_notify is 1
adb_port is -1
These checks in step 6 and 7 are not necessary but should be done so that troubleshooting becomes rather easy if the solution doesn't work for you.
8. Save the changes in settings.db and copy it back into Android by typing:
adb shell
rm /data/data/com.android.providers.settings/databases/settings.db
exit
adb push ~/settings.db /data/data/com.android.providers.settings/databases/
That delete (rm) command is not necessary since adb push should overwrite the file, but I executed it for my peace of mind.
8. Unmount Data and reboot into Android OS. ADB probably would be enabled.
source:- https://android.stackexchange.com/questions/112040/how-to-enable-usb-debugging-in-android-if-forgotten-pattern-for-screen-unlock"
Please help me understand this code and be a life saver.
Thanks in advance..
You are stuck, I'm afraid. You won't be able to run any script on stock recovery, but you can't flash a custom recovery without unlocking the bootloader which will wipe your data.
What's more, your phone should be encrypted (if it's running 6.0 or higher), which means you'll need to know the pattern to decrypt after a reboot.
If you can't figure out the pattern, there's nothing you can really do.
jisoo said:
You are stuck, I'm afraid. You won't be able to run any script on stock recovery, but you can't flash a custom recovery without unlocking the bootloader which will wipe your data.
What's more, your phone should be encrypted (if it's running 6.0 or higher), which means you'll need to know the pattern to decrypt after a reboot.
If you can't figure out the pattern, there's nothing you can really do.
Click to expand...
Click to collapse
Is there any way I can create backup of the data in these conditions?
Dush123 said:
Is there any way I can create backup of the data in these conditions?
Click to expand...
Click to collapse
Unfortunately for you in this case, there isn't.
From a general security perspective, if there was it would mean the pattern lock and encryption can be bypassed, which would be very bad.
jisoo said:
Unfortunately for you in this case, there isn't.
From a general security perspective, if there was it would mean the pattern lock and encryption can be bypassed, which would be very bad.
Click to expand...
Click to collapse
Ohk. Then it seems I don't have any option but to hard reset my device.
Thanks anyways
HI! Is there anything I can do for my pattern locked Moto E4 Plus? Details I've posted in this thread.
https://forum.xda-developers.com/showthread.php?t=2620456&page=13
How to root Asus Z010D without no power and volume button And it has no OEM unlock option(I think administrator not allowing)Hope for a solution
Since this phone is running Android 6 all you have to do is to replace ( restricted ) Toybox by ( non-restricted ) Toybox v0.8.5 what has SU applet implemented.
It's NOT required device's bootloader got unlocked before: it all can be done via a series of ADB commands.
jwoegerbauer said:
Since this phone is running Android 6 all you have to do is to replace ( restricted ) Toybox by ( non-restricted ) Toybox v0.8.5 what has SU applet implemented.
It's NOT required device's bootloader got unlocked before: it all can be done via a series of ADB commands.
Click to expand...
Click to collapse
Explain me please...and wdym by Toybox, where can I get it?
Toybox combines many common Linux command line utilities together into a single BSD-licensed executable.
Toybox binaries are available here:
Index of /toybox/bin
landley.net
jwoegerbauer said:
Toybox combines many common Linux command line utilities together into a single BSD-licensed executable.
Toybox binaries are available here:
Index of /toybox/bin
landley.net
Click to expand...
Click to collapse
Can we use busybox instead of toybox? will it work in asus z010d
What sense will it make to install Busybox ( a 3rd party binary ) in parallel to already pre-installed Toybox what results in disabling Toybox?
jwoegerbauer said:
What sense will it make to install Busybox ( a 3rd party binary ) in parallel to already pre-installed Toybox what results in disabling Toybox?
Click to expand...
Click to collapse
I understand...can u help me with commands to root plz
Maalutty said:
How to root Asus Z010D without no power and volume button And it has no OEM unlock option(I think administrator not allowing)Hope for a solution
Click to expand...
Click to collapse
Can anyone help me unlock bootloader of asus z010d
As already said: To root a phone's Android IT'S NOT REQUIRED TO UNLOCK PHONE'S BOOTLOADER.
jwoegerbauer said:
As already said: To root a phone's Android IT'S NOT REQUIRED TO UNLOCK PHONE'S BOOTLOADER.
Click to expand...
Click to collapse
Then how can I reach to twrp recovery? I cannot install supersu zip from recovery plz help me
Wondering why you intend to flash TWRP and SuperSU? All not needed to root a phone's Android, IMO.
jwoegerbauer said:
Wondering why you intend to flash TWRP and SuperSU? All not needed to root a phone's Android, IMO.
Click to expand...
Click to collapse
Kingoroot, kingroot such apps can't root my phone so I chose rooting through supersu or magisk...if you are aware of any other pls help me
Do what you think is right.
jwoegerbauer said:
Do what you think is right.
Click to expand...
Click to collapse
But are you sure that if I replace my toybox, I can root my phone without unlocking bootloader? Plz reply me
Maalutty said:
How to root Asus Z010D without no power and volume button And it has no OEM unlock option(I think administrator not allowing)Hope for a solution
Click to expand...
Click to collapse
Error:invalid boot image
Asus Z010d ZC550KL
During flashing twrp, it shows failed
Without an unlocked bootloader you can't flash system related images.
xXx yYy said:
Without an unlocked bootloader you can't flash system related images.
Click to expand...
Click to collapse
But when I try to unlock booltloader by unlock device tool, it says,
"An unknown error occurs, which may be a network connection issue"
Even if I connect to a network connection .Any solution?
Discussion thread for the 2023 Walmart ONN Google TV.
Link to an OTA https://android.googleapis.com/packages/ota-api/package/7f458c58073555f202dda7c4f0cd90b149ef98e1.zip
for those who dont care to root but still want to de-bloat and change launcher.
That's a great video. I haven't "supercharged" any of mine yet, but I'll get to it (someday) lol.
I have the new onn. 2023 model 4k GTV Box and notice that the following file does not exist: android.hardware.usb.host.xml in /system/etc/permissions.
I'm not sure but i think missing that file might be keeping my device from seeing a new air remote (RF Mode) i have that has backlighting, 3 media keys, 0-9 keypad, Del key, Voice and supports bluetooth (working) and a 2.4g RF dongle that comes with it (dongle not working). A Windows PC detects the donglee and installs drivers for it.
2 usb keyboards i have tested work on the onn with no problems. I found out about this because I heard that a RF remote might solve some issues relating to audio compared to bluetooth mode. I have tried this:
C:\adb>adb kill-server
C:\adb>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>adb usb
restarting in USB mode
C:\adb>adb devices
List of devices attached
GUSA2310018722 device
C:\adb>adb remount
/system/bin/sh: /system/bin/remount: inaccessible or not found
C:\adb> adb push android.hardware.usb.host.xml /system/etc/permissions
failed to copy 'android.hardware.usb.host.xml' to '/system/etc/permissions/andro
id.hardware.usb.host.xml': couldn't create file: Read-only file system
7 KB/s (119 bytes in 0.015s)
C:\adb>
Click to expand...
Click to collapse
Note that GUSA2310018722 is the onn serial number, and the adb utility with the xml file came from this site (about a different device):
USB Host Mode (Android)
nutsaboutnets.com
Is there some way to copy or install this xml file without rooting my device (never done a root before)? I did confirm the file does not exist with adblink2 and it's GUI File manager. Any help would be great.
hello all
So as far as root goes it is possible. There is a merg request waiting for it to be looked at and approved to be put into Magisk. I've read that topjohnwu the maintainer of Magisk doesn't really want to support multi-ramdisk. The other way to do it would be to manually patch it via the command line.
treypop said:
The other way to do it would be to manually patch it via the command line.
Click to expand...
Click to collapse
What command line did you use that worked? I was only able to get it to work using third party tools for lz4 and cpio, and a hex editor. But not using the magisk script directly. So, if you could list your command line...
unlocking bootloader kills widevine L1?
ziddey said:
unlocking bootloader kills widevine L1?
Click to expand...
Click to collapse
It does not.
Functioner said:
What command line did you use that worked? I was only able to get it to work using third party tools for lz4 and cpio, and a hex editor. But not using the magisk script directly. So, if you could list your command line...
Click to expand...
Click to collapse
I was referring to what you said in the onn android tv thread where you said you can manually patch it with the command line
Finally found one in stock. I'm assuming the bootloader can't be unlocked for ~3-4 days? Currently greyed out in developer options with "Connect to the internet or contact your carrier"
ziddey said:
Finally found one in stock. I'm assuming the bootloader can't be unlocked for ~3-4 days? Currently greyed out in developer options with "Connect to the internet or contact your carrier"
Click to expand...
Click to collapse
Setting the OEM unlocking toggle in developer options isn't required to unlock the bootloader. Just using the standard fastboot commands will work
Using fastboot to unlock the bootloader will erase everything
whats the adb code to root it? dont want t wait for a what if secnario for magisk to be updated. thx.
Just picked one of these up yesterday thinking it was the old model back in stock. It's cool that this new one supports AV1 I just hope the issues with the remote are gone.
BTK19 said:
Setting the OEM unlocking toggle in developer options isn't required to unlock the bootloader. Just using the standard fastboot commands will work
Using fastboot to unlock the bootloader will erase everything
Click to expand...
Click to collapse
What's the point in unlocking the bootloader without root? What can be achieved?
YoXDAyy said:
Just picked one of these up yesterday thinking it was the old model back in stock. It's cool that this new one supports AV1 I just hope the issues with the remote are gone.
What's the point in unlocking the bootloader without root? What can be achieved?
Click to expand...
Click to collapse
I didn't say there was a point in it i just said it could be done
treypop said:
So as far as root goes it is possible. There is a merg request waiting for it to be looked at and approved to be put into Magisk. I've read that topjohnwu the maintainer of Magisk doesn't really want to support multi-ramdisk. The other way to do it would be to manually patch it via the command line.
Click to expand...
Click to collapse
So then extracting the boot.img from the above posted ota .zip and patching it in magisk and then flashing the patched boot.img with fastboot isn't an option?
talksickisil said:
So then extracting the boot.img from the above posted ota .zip and patching it in magisk and then flashing the patched boot.img with fastboot isn't an option?
Click to expand...
Click to collapse
No it is not an option. You have to patch it through something like a custom recovery.
Fastboot works on the new "onn google tv" device for flashing, so long as the bootloader is unlocked.
Though for magisk use, the boot partition is not involved. Rather, it is the vendor_boot partition.
The wait on root for this device is not because of flashing. The wait is for some version of magisk to automatically handle patching a supplied vendor_boot image. The root already works, it's the patching that is missing.
Functioner said:
Fastboot works on the new "onn google tv" device for flashing, so long as the bootloader is unlocked.
Though for magisk use, the boot partition is not involved. Rather, it is the vendor_boot partition.
The wait on root for this device is not because of flashing. The wait is for some version of magisk to automatically handle patching a supplied vendor_boot image. The root already works, it's the patching that is missing.
Click to expand...
Click to collapse
Are you able to unpack, patch, and repack it manually? If so, can you provide some details on the steps? Thanks.