Database Develop

How to Install 4.2 images, keep root and all data

**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!

[Root] Root and TWRP for R

Disclaimer: If you are not comfortable with using Fastboot and ADB and editing system files than this guide might not be for you. At this point this is what I have to offer.
Click here for the unofficial twrp image - Latest version as of 12/27/14
So getting right into it.
1. Turn on ADB mode on the watch by going to about and tapping the build info 7 times.
2. Download ADB and Fastboot utilties
3. Plug the watch into the computer and your phone should vibrate and ask you to accept the computers fingerprint, tick the check box to always allow and hit ok
4. Open up a command prompt or terminal inside of where the ADB utilities are located and enter
Code:
adb reboot bootloader
This next step will wipe your data!
5. Now you should be in fastboot, go ahead and on the terminal use the next code and follow prompts to unlock
Code:
fastboot oem unlock
6. Now after you re-set up your watch again you will need to do step 1 and 3 again.
Please do not skip step 6!
7. Go ahead and issue
Code:
adb reboot bootloader
8. Flash unofficial twrp, make sure the recovery image file is in the same location as fastboot than issue
Code:
fastboot flash recovery YOURIMGNAMEHERE.img
9. Upon successfully doing that you should have twrp installed
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB use the proper name of what you downloaded. Issue
Code:
adb push SUPERSUNAMEHERE.zip /sdcard/
11. Issue
Code:
adb reboot recovery
12. than using the very tiny TWRP and somewhat messed up go ahead and use it to install the supersu.zip under the folder /sdcard
13. Enjoy root and twrp.
I will make this guide into a much easier Java program in the very near future to make it easier to use.
This was typed up pretty fast and it is kinda hacky, I will work on a bat script and a shell script if we have enough osx users here. I'm sure someone will come along and make this better if I don't get around to it.
Credits:
Dees-Troy for his TWRP support for dory our fish brother device which worked on our device
Chainfire for all his hard work these many years

Q: ADB complains there is no device listed.
A: Install universal ADB drivers and then go to device manager and under the device with a yellow warning icon go to update driver, Browse my computer, let me pick from list of device drivers, than Google ADB interface. If it still complains turn off debugging, than turn it back on, revoke authorization, then disable and re-enable again.

One more just in case.

Great work!!
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?

hatefuel19 said:
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?
Click to expand...
Click to collapse
The latest supersu is version 2.36 dated 11.27.2014. 1.94 is well over a year old, you need to update for sure that is why you are force closing.

I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!

hatefuel19 said:
I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!
Click to expand...
Click to collapse
I'm here to help! I'm working on adding other mods to my other thread right now I'm working on getting busybox working.

Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
---------- Post added at 09:31 PM ---------- Previous post was at 09:28 PM ----------
jimmydigital00 said:
Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
Click to expand...
Click to collapse
Disregard I did it again and for some reason it worked. Maybe I need to reboot first.

Recovery
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?

adamrobles said:
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?
Click to expand...
Click to collapse
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app

reflashed
tonu42 said:
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.

adamrobles said:
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.
Click to expand...
Click to collapse
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.

tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
Thank you for that information, I stopped the download of the dump.
Downloading the stock recovery now.
---------- Post added at 02:24 PM ---------- Previous post was at 02:10 PM ----------
tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
I must have skipped a step...
installed stock recovery
booted into the watch system
enabled adb debugging
reboot to bootloader
install your recovery image
rebooted
pushed supersu
rebooted to twrp
installed supersu
rebooted to system
adb shell - verified root!
You are awesome! Thank you for taking the time to help me!

HYPE for 5.0.1
'm Hype! can't wait to flash the first 5.0.1 system dump on this as stated by +Darek Ross we MAY be receiving update as early as today!

I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...

zvieratko said:
I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...
Click to expand...
Click to collapse
My guide is setup like the one you put there. In order to get adb working again you need to re setup the watch step 6. Read the instructions carefully. I'll post a batch script later to simplify this.
Sent from my A0001 using XDA Free mobile app

Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there

zvieratko said:
Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there
Click to expand...
Click to collapse
By default debugging is disabled, I'm not sure how you were able to issue an ADB command on step 7 with out first performing step 6.

Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)

zvieratko said:
Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)
Click to expand...
Click to collapse
Ah I see, yea the guide is written as the absolute minimum to work right now. Like I said later today I'll try to post a script that automates all of this, its much easier.

Decrypt OxygenOS without losing data

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??

Soft bricked phone? Can't install recovery and can't install a rom

Okay so I got my oneplus 3t today and I updated it to Nougat via the ota file all good so far. I then decided that I wanted to install a custom rom so I downloaded twrp supersu etc everything needed to root and install the rom. Here's where it went wrong in knowingly I downloaded the wrong twrp flashed it and it would just hang at the flash screen for twrp. Anyway after hours of trying to install a recovery I managed to get a stock one to semi work, now it turns out I don't know how I did it but my phone won't even boot it just turns on and goes straight to fastboot mode. I managed to get a stock recovery semi working but it won't let me install the stock rom from internal storage and I've tried updating through adb and it will hang at a random percentage for a good 20 mins and then just fail. Really need some help here it would be great, thanks

Hi,
If you can get into fastboot mode then the best recourse is through there. Hope you properly OEM unlocked your device.
First of all, you MUST have the latest adb/fastboot binaries and FOR SURE have the correct drivers.
Follow the links on this XDA article to download the latest adb and fastboot binaries: https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads
This is the link for the Windows binary: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract all the contents of the zip file in a folder on your PC.
Then, also make sure to have THE CORRECT twrp, 3.0.2.0 or 3.0.3.0. This is the link but currently it is down: https://twrp.me/devices/oneplus3t.html
Download THE IMAGE, NOT FLASHABLE ZIP and put it in the same folder as the android platform tools above.
Finally, download the latest complete 3T firmware from OnePlus from this link: http://downloads.oneplus.net/devices/oneplus-3t/
I STRONGLY recommend not to use an update zip, even a full ROM update zip as that one might not include certain firmware images.
Put THE ZIP on the same folder as the others, DO NOT EXTRACT ANYTHING.
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
After that, enter TWRP's Wipe menu and wipe system, data and cache.
Finally, use TWRP's Advanced menu and enter adb sideload mode. Once there slide that slider to the right to enable adb mode and return to your PC and enter the following command in the command prompt:
adb sideload OnePlus3TOxygen_28_OTA_029_all_1612131737_17e7161d2b234949.zip (assuming you downloaded the 3.5.4 binary from OnePlus).
TWRP should properly flash the OnePlus ROM and hopefully, return you to proper function. You can then update back to Nougat.
Hope that helped!

Yeah that sorted it thanks a lot

Use the emergency tool for OP3T and start from scratch:
https://forums.oneplus.net/threads/unbrick-guide-oneplus-3t.481214/

@KeyperOS
I'm trying to follow this guide, but did you miss something out here?
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
Click to expand...
Click to collapse
Once I do "fastboot boot twrp" and get a success, then what?
Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own.
If so, how do I do this?
Thanks,

jackmacbunton said:
Yeah that sorted it thanks a lot
Click to expand...
Click to collapse
Glad that sorted it out
PugRallye said:
@KeyperOSI'm trying to follow this guide, but did you miss something out here?
Once I do "fastboot boot twrp" and get a success, then what? Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own. If so, how do I do this? Thanks,
Click to expand...
Click to collapse
My instructions while detailed are not step-by-step. I expect the person reading them to have their PC configured correctly and at least a vague idea of what they're doing.
So, assuming you put the correct TWRP image (my command uses the name of the image for TWRP 3.0.3.0, you MUST alter it to reflect the actual image's filename if it's not that) on the same folder as the fastboot binary then yeah, the command
fastboot boot twrp-3.0.3-0-oneplus3t.img
should have made your phone reboot and enter into the TWRP image that you had on your PC.
If it didn't then you did sth else wrong before that.
Either you didn't OEM unlock your phone when you still could or you didn't use the android platform tools that I linked or you don't have the correct ADB drivers installed on your PC.
Start from there.
Hope that helped!

Thanks for your help @KeyperOS - I know where I went wrong...
To save some time, when I tried to reboot into TWRP, I typed "fastboot boot " then I dragged and dropped the TWRP img file onto that line in the cmd window (rather than typing the filename manually) - when you do that, it appears to include the full path to the img - it was that that was causing the problem.
When I typed the TWRP filename manually, it worked.
The only thing that caught me out was after I'd installed the ROM (via adb sideload) I tried to reboot the device from TWRP recovery - this seemed to just hang. In the end I just powered off the phone using the power key, then powered it back up as per usual.
Checked that the phone booted to the first of the setup screens, then powered off/booted into fastboot mode, relocked the bootloader and it seems to be OK.
I'm now back on 3.5.4 again, which was what I was trying to do...
4.0.0/1 had felt a bit laggy, and I'd sensed some issues with wifi and BT, I can now run 3.5.4 and see how it compares - was I just imagining it?
Thanks again for the guide and your help - I really appreciated it

@PugRallye
Windows' command prompt has an autocomplete feature. If you want it to add the name of a file, type a couple letters and then present TAB, it's gonna complete the filename itself and if it's the wrong file you can keep tapping tab to cycle through all the options.
Really glad it worked out Btw [emoji4]
In my experience, 3.5.4 was great but 4.0 is a step up in both battery life, which IME is amazing and features, with it I almost didn't need root and certainly don't need xposed which was a first.

[How-To] Install Oreo OTA! [T-Mobile]

*DON'T FLASH BACK TO NOUGAT IF YOU ENJOY USING YOUR PHONE*
Ok guys ive made my return and im happy to bring the oreo ota with me.!
Steps to install if your on a rom.
1. Use this flash all link Here
2. After finished and setup your going to need a pc and sideload knowledge
3. Download these ota files
Latest August https://drive.google.com/file/d/1OhWZPTWcuo7zRu9bjiezjKEZxreOk6v7/view OREO
4. Get your phone into recovery mode.
4.a the file is gonna have a lot of letters please do not rename or it wont work
4.b before you get into recovery you will see a dead Android. This IS normal. Your going to want to hold power and push volume up. It's a split second kinda thing. Not something you guys forever. Hot that a few times if it doesn't work the first time.
5 your going to want to go to in recovery to apply update via adb for the August one
6. run the command adb sideload (now drag the file to the command prompt and press enter)
7 if all good you will see a verifiying update the step 1/2 when you see that your fine.
8 Let it do its thing and at the end you may see and error about a drive disregard that.
9 now follow steps 4-7 again but with Oreo ota
10 reboot your system and now you should have oreo!
If your stock locked and never been cocked you can try to install the same method above without using the flash all and if it works congrats if not unlock your bootloader and use the method above.
if any help is needed contact me @ [email protected]
HOW TO ROOT
1. DOWNLOAD THIS. https://drive.google.com/file/d/1zz3Fl9m4-_ozWW1U3ww_e6K_cHPPEMSv/view?usp=drivesdk
2. FASTBOOT BOOT OR FLASH IT RUNNING "FASTBOOT BOOT /PATH/TO/BOOT.IMG" OR FASTBOOT FLASH /PATH/TO/BOOT.IMG
3. REBOOT AND PROFIT.
TWRP 3.2.1-0 Bootable and Permanent
Bootable Fastboot boot this *ONLY FOR OREO*
*Permanent is broken* Use boot able
Unencryption for oreo
Encryption Remover *FOR OREO ONLY*
*Must format then flash*
OREO FLASH ALL OREO *YOU CAN ONLY FLASH THIS AFTER YOU HAVE TAKEN THE OTA* *IF YOU FLASH THIS AND YOU HAVENT AND YOUR PHONE BLOWS UP PLEASE VIDEO IT SO I CAN POST IT ON HERE AND SHOW WHAT NOT TO DO*
Thank to @XirXes for the ota files

There is no root available as of yet we need a boot image to get root once there is one we will have roms and root coming.

Screenies
Here you go

Installation went smooth. thanks for the OTA.

now towait for the root and all will be set

wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?

Amd4life said:
wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?
Click to expand...
Click to collapse
No. As of right now Oreo starts you clean when you do this

Amd4life said:
wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?
Click to expand...
Click to collapse
I recommend (from experience) not trying that.

Making a test twrp real quick

Damn...thanks for your work

joemossjr said:
Making a test twrp real quick
Click to expand...
Click to collapse
Looking to this!
Oreo build is almost as fastest as the Flash [emoji3][emoji16]
Sent from my Moto Z (2) using Tapatalk

Thanks, @joemossjr ! It installed for me too. In my case, for some reason, I had to rename it to update.zip before adb sideload would work, but I'm not sure why. Oreo, yayyyy!

can someone please pull a system backup not image? i have a twrp that you can boot not flash and pull the stuff

where's the TWRP, so only use a fastboot flash boot image.zip?

joemossjr said:
can someone please pull a system backup not image? i have a twrp that you can boot not flash and pull the stuff
Click to expand...
Click to collapse
I could, do you have the TWRP link?
---------- Post added at 12:55 PM ---------- Previous post was at 12:47 PM ----------
What I wanted to do was boot slot _b rooted 7.1.1 and copy slot _a stock Oreo, but it nagged me about potentially bricking in fastboot after fastboot set_active _b (i.e., due to invalid bootloader, etc.). A bootable TWRP straight to recovery would solve the issue. All I wanted to do was get a copy of Oreo boot_a, but adb as non-root user does not have permission to dd copy /dev/block/bootdevice/by-name/boot_a . So, yay for bootable TWRP!

@jhofseth please write me on hagnouts

please message me on hangouts people who want to help [email protected]

When you brick and have to go to a leaked 8.0 image

Unable to flash update
For whatever reason i'm unable to flash the update, and i'm currently left with a soft-bricked device. When trying to flash the update via recovery gives me
Code:
E:failed to unmount /
E:failed to set up expected mounts for install; aborting
failed to open driver control: no such file or directory
installation aborted
also when selecting install from ADB it says
Code:
Supported API: 3
stopping adbd...
failed to open driver control: no such file or directory
failed to open driver control: no such file or directory
is there something i can do to remedy this??
forgot to mention that yes i did install the first package and properly executed the flashall command from the first zip folder, and i did try sideloading the second package as it was and as an update.zip file to no success.

Shiro12 said:
For whatever reason i'm unable to flash the update, and i'm currently left with a soft-bricked device. When trying to flash the update via recovery gives me
also when selecting install from ADB it says
is there something i can do to remedy this??
forgot to mention that yes i did install the first package and properly executed the flashall command from the first zip folder, and i did try sideloading the second package as it was and as an update.zip file to no success.
Click to expand...
Click to collapse
Do you go completely stock?