One of my N6s has a little trouble doing ADB.
When it's in stock, the phone will only accept ADB commands and show up in ADB Devices when the USB mode is set to MIDI. It doesn't work with ADB in MTP mode. But in MTP mode, I can drop files to the phone from Windows File Manager, but no ADB. In TWRP recovery mode, with MTP on I can't drop files to the phone. In TWRP, if I disable MTP, the phone no longer shows up in Windows. That's the background on this phone.
I'm trying to flash Pure Nexus, GApps, Magisk, and Franco Kernel to this phone without encrypting it.
As a starter step, I have flashed stock and TWRP to it without rebooting to the stock ROM (which would encrypt the phone).
(Note I know many people say encryption doesn't matter for better performance. Let's not get distracted by that discussion here. I'm trying to see if I can flash this custom setup without encrypting.)
I now need to get the Zips for PN, GApps, Magisk, and Franco onto the phone but am unable to use adb push command or Windows File Manager to drop those files.
So it has fresh stock and TWRP on it. Now when the phone is in TWRP, and I try to "adb push ROM.zip" I get an error: failed to get feature set: no devices/emulators found If I try adb devices it returns a blank list.
So while TWRP is on the phone i don't know other ways to push the Zips over to a folder on the phone.
In Windows File Manager I can see the device Nexus 6 and inside of that is Internal Storage. If I try to drop files to Internal Storage using Windows, it processes for a long time and hangs.
In Windows File Manager I cannot create a new folder on the phone when it's in TWRP mode.
In TWRP, Mount, the default boxes checked are Data and Cache. Others aren't checked.
Is there some other trick to getting those Zips onto the phone without booting the phone into Stock, thus encrypting the data? Thanks
wittier said:
One of my N6s has a little trouble doing ADB.
When it's in stock, the phone will only accept ADB commands and show up in ADB Devices when the USB mode is set to MIDI. It doesn't work with ADB in MTP mode. But in MTP mode, I can drop files to the phone from Windows File Manager, but no ADB. In TWRP recovery mode, with MTP on I can't drop files to the phone. In TWRP, if I disable MTP, the phone no longer shows up in Windows. That's the background on this phone.
I'm trying to flash Pure Nexus, GApps, Magisk, and Franco Kernel to this phone without encrypting it.
As a starter step, I have flashed stock and TWRP to it without rebooting to the stock ROM (which would encrypt the phone).
(Note I know many people say encryption doesn't matter for better performance. Let's not get distracted by that discussion here. I'm trying to see if I can flash this custom setup without encrypting.)
I now need to get the Zips for PN, GApps, Magisk, and Franco onto the phone but am unable to use adb push command or Windows File Manager to drop those files.
So it has fresh stock and TWRP on it. Now when the phone is in TWRP, and I try to "adb push ROM.zip" I get an error: failed to get feature set: no devices/emulators found If I try adb devices it returns a blank list.
So while TWRP is on the phone i don't know other ways to push the Zips over to a folder on the phone.
In Windows File Manager I can see the device Nexus 6 and inside of that is Internal Storage. If I try to drop files to Internal Storage using Windows, it processes for a long time and hangs.
In Windows File Manager I cannot create a new folder on the phone when it's in TWRP mode.
In TWRP, Mount, the default boxes checked are Data and Cache. Others aren't checked.
Is there some other trick to getting those Zips onto the phone without booting the phone into Stock, thus encrypting the data? Thanks
Click to expand...
Click to collapse
SUCCESS
Update: with some manipulation in TWRP, I was able to get a file system I could see and drop files to from Windows.
After flashing stock, and TWRP, and booting to TWRP (without ever booting to system/stock, which would have encrypted phone) i did the following.
I'm trying to remember all the steps but I think that Wiping the data and cache partitions via TWRP was the key, and required before I could move zips over to the phone.
I dropped the Pure Nexus, GApps, and Magisk onto the phone and then flashed them in that order via TWRP
Rebooted to system.
It installed and set up under Pure Nexus. It's reloading my apps from my Google account.
I checked Settings, Security and the phone is not encrypted.
I haven't yet checked on the GApps and Magisk. I assume I can install Franco Kernel from the Franco Manager app that I bought.
When you can't transfer files from PC to the N6:
Remove the drivers of the PC and let Windows search for the latest drivers.
Check on https://dl.twrp.me if you have the latest version of TWRP.
NLBeev said:
When you can't transfer files from PC to the N6:
Remove the drivers of the PC and let Windows search for the latest drivers.
Check on https://dl.twrp.me if you have the latest version of TWRP.
Click to expand...
Click to collapse
thanks. it is the latest TWRP.
I fixed it, see above, it wasn't the drivers on the PC.
The PC works with my other N6. This N6 has issues.
The workaround of wiping in TWRP fixed it. I don't know yet if I'd have to do the same wipe with my better N6. Will find out soon.
wittier said:
... I don't know yet if I'd have to do the same wipe with my better N6. Will find out soon.
Click to expand...
Click to collapse
Updating TWRP to the latest version is a good practice.
wittier said:
SUCCESS
Update: with some manipulation in TWRP, I was able to get a file system I could see and drop files to from Windows.
After flashing stock, and TWRP, and booting to TWRP (without ever booting to system/stock, which would have encrypted phone) i did the following.
I'm trying to remember all the steps but I think that Wiping the data and cache partitions via TWRP was the key, and required before I could move zips over to the phone.
I dropped the Pure Nexus, GApps, and Magisk onto the phone and then flashed them in that order via TWRP
Rebooted to system.
It installed and set up under Pure Nexus. It's reloading my apps from my Google account.
I checked Settings, Security and the phone is not encrypted.
I haven't yet checked on the GApps and Magisk. I assume I can install Franco Kernel from the Franco Manager app that I bought.
Click to expand...
Click to collapse
I updated my other N6 last night.
After flashing stock ROM and TWRP and booting to TWRP only, I didn't have to wipe before I could push files to the phone.
The other phone is more difficult.
Related
**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..
jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.
mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options
You have .bat file in the package.
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions
I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?
I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app
mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app
can I install image-nakasi-jop40c.zip directly without upgrading bootloader?
Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.
Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!
I had the SD card issue where it wasn't seeing all my files. Recovery mode would see files I could not locate within the os.
What I did:
Backed up my contents. Always have a nandroid backup!
Downloaded and md5sum checked Trickdroid 8.0.0
Booted into recovery, wiped phone. Formatted all partitions.
My next plan of action was to adb push trickdroid. This failed, its not seeing my sdcard partion. I have attempted to format /sdcard. It returns no errors. I got to mount /sdcard, It fails to find the directory.
When I boot into fastboot (Thinking at the very worst I could relock my device nad flash an RUU)
It does not see any devices. I have verified multiple times that I am using the correct driver. I have removed all drivers from the system, attempted to use htc sync, uninstalled that, used the Naked Drivers, uninstalled those (still no device in fastboot), installed the ADB Driver installer (found using the search button). Still, no devices in fastboot.
If someone could point me in the right direction I would greatly appreciate it. I have been using adb and flashing devices for a number of years and have not yet encountered a problem like this.
-Erik
voltage88 said:
I had the SD card issue where it wasn't seeing all my files. Recovery mode would see files I could not locate within the os.
What I did:
Backed up my contents. Always have a nandroid backup!
Downloaded and md5sum checked Trickdroid 8.0.0
Booted into recovery, wiped phone. Formatted all partitions.
My next plan of action was to adb push trickdroid. This failed, its not seeing my sdcard partion. I have attempted to format /sdcard. It returns no errors. I got to mount /sdcard, It fails to find the directory.
When I boot into fastboot (Thinking at the very worst I could relock my device nad flash an RUU)
It does not see any devices. I have verified multiple times that I am using the correct driver. I have removed all drivers from the system, attempted to use htc sync, uninstalled that, used the Naked Drivers, uninstalled those (still no device in fastboot), installed the ADB Driver installer (found using the search button). Still, no devices in fastboot.
If someone could point me in the right direction I would greatly appreciate it. I have been using adb and flashing devices for a number of years and have not yet encountered a problem like this.
-Erik
Click to expand...
Click to collapse
I fixed it!!! Anyone that has a similiar issue. This is what I did.
In a previous thread, I saw that 4.2 will redo the sd card structure. After some research, it was recommended to change the path to /data/media/0. I was then attempting to do the command as follows 'adb push Trickdroid_8.0.0.zip /data/media/0' (without tick marks)
The file was pushing as it should (no progress bar) however, it would fail at the very end saying it was unable to locate the directory.
After seeing adb fail in that manner, I knew my sdcard was not mapped to the above path. What I did was boot into recovery, go to mounts and storage, mount my sdcard. Go back to the first menu now.....From here, select advance, and view log. It will tell you where your sdcard is being mapped to. Simply push your zip file to this directory and success! I have a working phone again.
Fastboot still doesn't recognize my device however. I'd be more then happy to be educated as to what I may have done wrong.
Just thought I'd share, might help someone. This is for Nexus 7 previously bootloader unlocked and rooted (and whatever else, like xposed) going from 4.4.4 to 5. If you're not on 4.4.4 and bootloader unlocked get there first. Obviously you need usb debugging on.
You also need some form of adb and fastboot. I used Minimal ADB from here:
http://forum.xda-developers.com/showthread.php?t=2317790
What I Did:
- Got the Lollipop OTA from the links posted everywhere by now, including the second sticky here in General.
Put a copy in the adb/fasboot folder in Windows, and renamed the file to updatelollipop.zip to make it easier to handle.
Tried old style of updating: Uninstall Xposed, flash Xposed Disabler, flash OTA zip from custom recovery. Failed. Tried again, failed again.
But this was expected, as I'd read that the way lollipop updates is different from all previous updates and will fail at the slightest discrepancy in system partition.
So, need clean system.
- Got the Stock 4.4.4 firmware from Google: https://developers.google.com/android/nexus/images
Inside the firmware file found the system.img and recovery.img images.
Put these two files in the same folder as minimal adb and fastboot.
- Got into bootloader.
if powered off hold power and volume down keys. if booted up in Minimal ADB command prompt window type:
adb reboot bootloader
- flashed stock system and recovery
fastboot flash system system.img
fastboot flash recovery recovery.img
- Got into stock recovery
In bootloader, scrolled to select recovery, then with "No Command" showing held power and clicked volume up.
Select apply update from adb. Screen says to type adb sideload update from computer.
Ran into a hiccup. ADB would not recognize my N7. typing "adb devices" returned empty result. Booted up into Android, computer and adb recognized device fine. typed adb reboot bootloader, and in bootloader adb no go.
So while connected to computer in bootloader mode, went into Device Manager in Windows. Sure enough there was unknown device called grouper. Promptly update the driver. I used driver files from the Wugfresh toolkit I had installed. The device was recognized as Google Galaxy Nexus ADB device. Didn't matter to me as long as it was recognized as ADB. If you want official drivers you can get them from Asus here: http://support.asus.com/Download.aspx?SLanguage=en&m=Nexus+7&p=28&s=2
- Back into ADB sideload screen in N7 stock recovery.
typed adb sideload updatelollipop.zip
Let the ADB push the file, then stock recovery did the update. no issues. back in recovery might as well erase cache partition.
Root then. Could use Wugfresh NRT but decided to go manual.
UPDATE: As of SuperSU 2.27 Beta, flashing SuperSU from custom recovery is enough to gain root on Lollipop 5.0. Root kernel is no longer needed!
Old fashioned root failed works now: get the latest twrp recovery (copied it into adb folder, renamed it to twrprecovery.img), get the latest superSU (put it anywhere in N7 internal storage), flash the latter with the former:
In command prompt, typed fastboot boot twrprecovery.img
this temp booted twrp. promptly went to install, found superSU zip, flashed it.
Booted into Android, Lollipop looks nice, but No Root.
Again, not surprised, had already read lollipop needs modified kernel for root. Looked in the Wugfresh NRT files, had two candidates, modified boot img and root kernel img. not sure the difference, but the two files had different file sizes, and I had read somewhere that modified kernel would keep most of the security features of stock kernel, only modifying permissions needed for root, so decided to go with the kernel img file. Copied it over to adb fastboot folder, renamed it rootboot.img
- got back into bootloader. in command prompt typed
fastboot flash boot rootboot.img
Rebooted into Android, had root! Great. Notice didn't need to flash superSU a second time.
To check if root works fine, just open superSU app. If it opens fine then you're good. Root apps will ask for root, and granting will work fine, but that doesn't mean the apps will be able to use root for the simple reason that they might need to be updated. for example, es file manager asked for root, was granted, but root directories showed empty. clearly needs an update. Tried Total Commander, gave root, worked fine. So apps ability to use root in lollipop will vary based on their need to be updated to work.
thanks as always to Wugfresh and Chainfire.
"Unknown Device" when USB Debugging On
Speaking of root apps needing update, one app that needed updating if you use it, is Adbd Insecure. Why am I singling it out? Because it had me running around in circles trying to figure out why Windows was claiming my N7 was an Unknown Device.
Thing is, I installed adbd insecure long ago set on auto start, and it's useful for when it's needed, but I had completely forgotten about it now when trying to figure out the driver issue. Turning off USB debugging Windows happily recognized MTP, but who wants debugging off, it's a bad idea.
After twirling in circles finally decided to check if Windows would recognize bootloader and recovery mode. Sure enough, everything was good there. Rebooted into Android and noticed ADB was recognized briefly upon startup before it went away. That got me suspicious which led me to the culprit. So, yeah, save yourself some trouble and update that app, if you have it running.
Currently irate because I already typed all this then hit enter to be told I can only register once from this ip.
Any way...
Rooted vs98027a Android 4.4.2 via Stump Root
Used AutoRec which installed TWRP 2.7.00
Backed up Stock Rom
Mount button is missing
Rebooted into Stock to transfer backup to PC and place "cm-12-20150603-NIGHTLY-vs980.zip" as well as Lp gapps.
Rebooted back into TWRP
Wiped, then Installed the CM Nightly, wiped cache and rebooted.
Stuck in LG Boot loop.
Use buttons to boot back into TWRP, open Restore and It's just a blank navigation window.
TWRP just became ****ing worthless
Tried to wipe and possibly install same CM again. Still boot looping.
Tried getting to download mode, but it reboots before installing driver.
I have not a clue as to what to do next.
I can't get it to mount.
ADB Sideload Fails.
Terminal Command lets me select a blank navigation window.
And my original file structure is in like sdcard/0/0/0/0/0/0/0/0/ etc.
Please help, or at least redeem CM and TWRP's value somehow, because this is bs.
I sort of fixed it.
Restore showed up blank, because within the many /0/0/0/0/0/0/0/0 a new TWRP folder would be made or course containing nothing.
I also learned the adb is this magnificent goddess that can do things even when your phone can't.
Throughout further reading I glimpsed upon something about "loki" files that aren't compatible with specific versions of twrp or something. So If you've also been through this and still feel brave enough to flash a custom, then make sure you get the newest version of twrp...
As for the Restore issue, assuming you have a backup saved on pc, wipe everything then adb push the whole file (TWRP/BACKUPS/BLAHBLAH/BLAUGHESDIHF) to /sdcard/.... then it should show up in restore, if it doesn't then use file manager to place it in the right TWRP directory... You can also use the file manager to move the restore folder to the "correct" twrp folder if you don't have it backed up.
Hello there!
Today, after a bit of tinkering around I managed to get my OnePlus 3 in a decrypted state without losing data!
However, this is NOT a method where your data will remain on the phone, it requires you to copy a backup to your PC and then copy everything back + fix permissions. In this guide you'll completely wipe/reset your phone prior to restoring everything.
FAQ:
Q: Why do I need an undecrypted phone?
A: So far (as of today, 06.07.2016) multiboot will not work on encrypted phones. That's probably the only reason why you'll ever want to decrypt your phone.
Q: Will updating the ROM force encryption again?
A: If you're using OxygenOS (or another encryption forcing ROM), yes. However if you flash the Full ROM ZIP and immediately after that SuperSU (DO NOT USE SYSTEMLESS OR IT WILL ENCRYPT AGAIN!!!) WITHOUT REBOOTING it'll not encrypt the device again. (Thanks to @JumboMan)
Q: I've followed your guide but my phone got encrypted again!
A: You've probably used the Systemless SuperSU version which does indeed not prevent your device from being encrypted again. Use the normal version available HERE.
You'll need:
A PC (obviously)
Unlocked OnePlus 3 (will probably work on other OnePlus phones, not tested!)
TWRP Recovery (follow THIS LINK for a guide)
About 50 GB of free space on your PC (depends on how much data you have on the phone)
ADB and Fastboot drivers installed on your PC (to get those connect your OP3 to your PC, as storage choose MTP, open the emulated OnePlus CD-Drive and install those drivers)
(Optional) 15 Seconds ADB Installer
A bit of time, roughly 30 minutes to 1 hour
!!!DISCLAIMER!!!
I'M NOT RESPONSIBLE FOR ANYTHING YOU'RE ABOUT TO DO HERE, THIS GUIDE IS PURELY WRITTEN "OUT OF MY HEAD" AND I CANNOT CONFIRM ANY OF THE FOLLOWING STEPS ANYMORE!!!!
ONLY DO THIS IF YOU KNOW HOW TO RECOVER FROM A HALF-INSTALLED OR COMPLETELY WIPED SYSTEM!!!
How To:
READ AND ACKNOWLEDGE THE DISCLAIMER ABOVE!
Done? Are you really sure? ... Okay!
If you don't need your data backed up simply start at Step 10 and ignore the restore parts after that.
Still on OxygenOS (or any other ROM) make sure you've enabled ADB in Developer Options and connected + allowed your PC at least one time, else ADB in TWRP will not work.
If you have Titanium Backup, create a backup of all your apps before starting. Just in case, you never know...
Once done boot into TWRP (see above for an installation guide)
Create a normal TWRP backup
Type in "adb devices" to check if you're allowed to use ADB inside TWRP. If it says "unauthorized" refer to Step 1 again.
Once done open up a CMD on your PC and cd to the directory you want all your backup-files to be (or navigate via Windows Explorer to the folder, hold "Shift", right-click and choose "Open command window here...")
Type in "adb pull /data/media" and wait. Depending on the size this can take a few minutes.
After that's done make sure all your files are here and ADB is not reporting any skipped files.
Checked all your files? Okay!
In TWRP choose "Reboot" and "Bootloader". This will put your phone into Fatboot mode.
Type in "fastboot devices" to check if your phone is recognized. If not go into device manager, find the Google Bootloader drivers and install those.
NOW IS YOUR LAST CHANCE TO MAKE SURE EVERYTHING'S BACKED UP AND THERE!
Next type in "fastboot format userdata" and hit enter. This will completely wipe your device.
Boot back into TWRP by using the volume rocker and the Power Button.
ADB is probably not working now (will only report "unauthorized"), MTP however still works. Copy the TWRP folder we backed up earlier onto the device again.
Once copying finished restore the backup and reboot into recovery again. You're now able to use ADB due to the adbpub.key being present again. (You could've done this earlier but it's easier that way.)
Copy the rest back onto the device with "adb push / /data/media". (I'm not really sure if this command is right, beware!)
Now type "adb shell chown -R media_rw:media_rw /data/media" to fix issues later in the ROM.
You're basically finished now! Simply reboot and wait till it boots up again. If you're getting stuck at a "Wrong PIN" or "Wrong Pattern" screen SEE THIS COMMENT I made in another thread.
Finished!
As said, I'm not sure if I forgot something here or not. However I think I got everything covered
Thank you. This was a much needed guide for all of us
Sent from my ONEPLUS A3003 using Tapatalk
Nice
Noob questions: is the decrypted OS faster? Performances of the phone are the same? What about updates (any update will crypt it again?
Thanks for any feedback!
Sent from my OnePlus3 using XDA Labs
IlD4nX said:
Noob questions: is the decrypted OS faster? Performances of the phone are the same? What about updates (any update will crypt it again?
Thanks for any feedback!
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Performance is about the same.
I have no idea if updates will crypt it again, I think not tho? Not sure.
ota updates might encrypt it again if you're on stock. depending if there's a new kernel. the kernel I think forces encryption. so we need a modified boot img to disable forced encryptions. or use a custom kernel that disables force encryption.
If you're on a custom rom based on aosp/cm. most of them doesn't force encryption. so there's no need to worry.
Sent from the moon and back
Thanks for the guide, will this wipe my internal storage?
daavid1995 said:
Thanks for the guide, will this wipe my internal storage?
Click to expand...
Click to collapse
Yes, however the guide shows you how to get a backup of ALL your files before anything gets wiped.
Ajo, und servus aus Österreich
IlD4nX said:
Noob questions: is the decrypted OS faster? Performances of the phone are the same? What about updates (any update will crypt it again?
Thanks for any feedback!
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Yes. updates will encrypt data again.
if you want to remain non encrypted after update then following procedure.
1. download full rom zip (not ota zip)
2.flash full update zip
3.without rebooting after flashing update just flash SuperSU zip. SuperSU will patch your boot img to remain in non encrypted state.
Proof- myself tried it on 3.2.0 update and it works without any problem
JumboMan said:
Yes. updates will encrypt data again.
if you want to remain non encrypted after update then following procedure.
1. download full rom zip (not ota zip)
2.flash full update zip
3.without rebooting after flashing update just flash SuperSU zip. SuperSU will patch your boot img to remain in non encrypted state.
Proof- myself tried it on 3.2.0 update and it works without any problem
Click to expand...
Click to collapse
Added to the OP Thanks for testing!
Thanks, i will try
Dere haha :fingers-crossed::good:
EpicLPer said:
Yes, however the guide shows you how to get a backup of ALL your files before anything gets wiped.
Ajo, und servus aus Österreich
Click to expand...
Click to collapse
maybe stupid questions, but not clear for me:
is there a negative point decrypting the phone or are there any risks?
will decrypting have an effect on the security of the phone?
odooo said:
maybe stupid questions, but not clear for me:
is there a negative point decrypting the phone or are there any risks?
will decrypting have an effect on the security of the phone?
Click to expand...
Click to collapse
As long as you're not an "international searched criminal" where the FBI tries to break into your phone then, no
I'd say it is a bit less secure but who cares, anyone who wants access to your phone somehow gets it anyways, TWRP isn't helping here either since anyone can simply boot into recovery and recover all files from there nonetheless.
Decryption risks are only when you're not good at backing up your data, else there are no risks of doing so.
@EpicLPer:
17. Copy the rest back onto the device with "adb push / /data/media". (I'm not really sure if this command is right, beware!)
Click to expand...
Click to collapse
"adb push / /data/media" doesnt work for me. Can somebody help? I restored the TWRP-Backup and only need to copy the rest on the device.
Edit: I did it in another way, copied all files manually.
Can someons dcrypt this
IzpG+nubzE2m3krvbos0lVDLANkIkiekZt209MYU12Vzny8WNOS7o4JGNoVAm41e/44IYPHmh
0Y7NnLW1JghbWJwbzL1WIpQw7nkzQoH9dEwvTiloTg5BI1u9TYRExzLGQEDUqN2hjq1G5cn
CqDmYoQnMs2bMiuajZweq9ZDC7gLruq6dse0L96gzZFoC/33lF0h1mEh7SBgW3FrcsjhRQ==
Sent from my SM-N910P using XDA-Developers mobile app
Worked, Thanks
How can I check if my device is decrypted or encrypted?
odooo said:
How can I check if my device is decrypted or encrypted?
Click to expand...
Click to collapse
Go to Settings > Device Security and check if it says encrypted or if it gives you the option to encrypt. If second, you know it's decrypted.
Can somebody do some benchmarks? I am really curious whether it makes a difference or not.
from what I've heard it makes a big difference in sequential rw speeds, which are actually pretty important on android.
Will it wipe my rom too?? Or just internal storage??
---------- Post added at 04:03 PM ---------- Previous post was at 03:31 PM ----------
EpicLPer said:
Hello there!
Today, after a bit of tinkering around I managed to get my OnePlus 3 in a decrypted state without losing data!
However, this is NOT a method where your data will remain on the phone, it requires you to copy a backup to your PC and then copy everything back + fix permissions. In this guide you'll completely wipe/reset your phone prior to restoring everything.
FAQ:
Q: Why do I need an undecrypted phone?
A: So far (as of today, 06.07.2016) multiboot will not work on encrypted phones. That's probably the only reason why you'll ever want to decrypt your phone.
Q: Will updating the ROM force encryption again?
A: If you're using OxygenOS (or another encryption forcing ROM), yes. However if you flash the Full ROM ZIP and immediately after that SuperSU WITHOUT REBOOTING it'll not encrypt the device again. (Thanks to @JumboMan)
You'll need:
A PC (obviously)
Unlocked OnePlus 3 (will probably work on other OnePlus phones, not tested!)
TWRP Recovery (follow THIS LINK for a guide)
About 50 GB of free space on your PC (depends on how much data you have on the phone)
ADB and Fastboot drivers installed on your PC (to get those connect your OP3 to your PC, as storage choose MTP, open the emulated OnePlus CD-Drive and install those drivers)
(Optional) 15 Seconds ADB Installer
A bit of time, roughly 30 minutes to 1 hour
!!!DISCLAIMER!!!
I'M NOT RESPONSIBLE FOR ANYTHING YOU'RE ABOUT TO DO HERE, THIS GUIDE IS PURELY WRITTEN "OUT OF MY HEAD" AND I CANNOT CONFIRM ANY OF THE FOLLOWING STEPS ANYMORE!!!!
ONLY DO THIS IF YOU KNOW HOW TO RECOVER FROM A HALF-INSTALLED OR COMPLETELY WIPED SYSTEM!!!
How To:
READ AND ACKNOWLEDGE THE DISCLAIMER ABOVE!
Done? Are you really sure? ... Okay!
If you don't need your data backed up simply start at Step 10 and ignore the restore parts after that.
Still on OxygenOS (or any other ROM) make sure you've enabled ADB in Developer Options and connected + allowed your PC at least one time, else ADB in TWRP will not work.
If you have Titanium Backup, create a backup of all your apps before starting. Just in case, you never know...
Once done boot into TWRP (see above for an installation guide)
Create a normal TWRP backup
Type in "adb devices" to check if you're allowed to use ADB inside TWRP. If it says "unauthorized" refer to Step 1 again.
Once done open up a CMD on your PC and cd to the directory you want all your backup-files to be (or navigate via Windows Explorer to the folder, hold "Shift", right-click and choose "Open command window here...")
Type in "adb pull /data/media" and wait. Depending on the size this can take a few minutes.
After that's done make sure all your files are here and ADB is not reporting any skipped files.
Checked all your files? Okay!
In TWRP choose "Reboot" and "Bootloader". This will put your phone into Fatboot mode.
Type in "fastboot devices" to check if your phone is recognized. If not go into device manager, find the Google Bootloader drivers and install those.
NOW IS YOUR LAST CHANCE TO MAKE SURE EVERYTHING'S BACKED UP AND THERE!
Next type in "fastboot format userdata" and hit enter. This will completely wipe your device.
Boot back into TWRP by using the volume rocker and the Power Button.
ADB is probably not working now (will only report "unauthorized"), MTP however still works. Copy the TWRP folder we backed up earlier onto the device again.
Once copying finished restore the backup and reboot into recovery again. You're now able to use ADB due to the adbpub.key being present again. (You could've done this earlier but it's easier that way.)
Copy the rest back onto the device with "adb push / /data/media". (I'm not really sure if this command is right, beware!)
Now type "adb shell chown -R media_rw:media_rw /data/media" to fix issues later in the ROM.
You're basically finished now! Simply reboot and wait till it boots up again. If you're getting stuck at a "Wrong PIN" or "Wrong Pattern" screen SEE THIS COMMENT I made in another thread.
Finished!
As said, I'm not sure if I forgot something here or not. However I think I got everything covered
Click to expand...
Click to collapse
Will it wipe my rom too?? Or just internal storage??