Hello,
I have a problem and I hope this is the right place for help.
I try my best to explain everything.
So I tried to root my OnePlus 3T.
Everything was going good. I installed TWRP and was able to use it.
Next I wanted to flash no-verity-opt-encrypt-5.1.zip.
I messed something up and wiped all my cache and my data.
I didn't noticed it at this point, so I tried to install SuperSU.
I don't know, if it was successful, but I guess not.
Then I restarted my phone and I stuck in bootloading. It was an endless loading until, my battery was empty.
I charged my phone up and was able to start TWRP.
Now I have my OnePlus 3T without an OS installed.
I downloaded the OS from OnePlus and tried to put it on my connected phone with the ADB Sideload, but my phone can't install ADB Sideload. So I can't put the OS on my phone to install it.
I don't know what to do and how I can put my OS on my phone.
One Idear was to put it on a USB Stick which fits in my phone, but I don't know.
I hope, someone can help me.
Sorry for my bad english, btw.
Boot into twrp and connect the phone to your notebook. If you can copy the OOS Rom to your phone, just flash it.
If not, you have to use the unbrick guide, just follow it and your phone should be alright again.
Boot into TWRP recovery and connect op3t to PC and move os to internal memory. Flash os from TWRP....
Sent from my ONEPLUS A3003 using Tapatalk
faffaz said:
Boot into TWRP recovery and connect op3t to PC and move os to internal memory. Flash os from TWRP....
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Do EXACTLY as this guy said. I had the EXACT same problem. I was doing a root, accidentally wiped everything including the OS, and thought I was ****ed. A little while later I went to the OnePlus website, downloaded the latest available OS and copied it over to my phone's internal memory while it was booted into TWRP. I then flashed it via TWRP and was good as new. Don't panic and you should be fine.
If adb sideload is not working. Then you can follow this method. Download adb tools from Google. Then their is a option of push the rom in the adb tools. Just keep the phone connected to notebook in twrp mode and then via that software push the rom into the internal of phone. Then just flash manually. It's done. I did this, as the same thing happened with me some days ago.
Nicky Carts said:
Do EXACTLY as this guy said. I had the EXACT same problem. I was doing a root, accidentally wiped everything including the OS, and thought I was ****ed. A little while later I went to the OnePlus website, downloaded the latest available OS and copied it over to my phone's internal memory while it was booted into TWRP. I then flashed it via TWRP and was good as new. Don't panic and you should be fine.
Click to expand...
Click to collapse
It doesn't working. I don't have my phone's internal memory, when I click on my OP3T and I can't copy the OS just on my phone.
It said that this folder is empy.
Is there a way to get into my root folders on my pc?
Vaibhunk786 said:
If adb sideload is not working. Then you can follow this method. Download adb tools from Google. Then their is a option of push the rom in the adb tools. Just keep the phone connected to notebook in twrp mode and then via that software push the rom into the internal of phone. Then just flash manually. It's done. I did this, as the same thing happened with me some days ago.
Click to expand...
Click to collapse
Okay, connected my OP3T with my computer and started my cmd and went to the adb folder.
It found my device when I typed in: adb devices.
then I tried to sideload the OS but it said:
"loading: 'OnePlus3TOxygen.zp'
* cannot read 'OnePlus3TOxygen.zip' *
I don't know, what I did wrong.
Fun4Jan said:
Okay, connected my OP3T with my computer and started my cmd and went to the adb folder.
It found my device when I typed in: adb devices.
then I tried to sideload the OS but it said:
"loading: 'OnePlus3TOxygen.zp'
* cannot read 'OnePlus3TOxygen.zip' *
I don't know, what I did wrong.
Click to expand...
Click to collapse
Don't use cmd, I told you to use a software named adb tools. Easily available on google. Search it.. Then follow the procedure. Just make sure that your phone is booted into twrp.
It is really not as easy as everyone says to root your phone. I had to do tons of research and it took a long time and the community was not helpful over at OnePlus and it was hard to find much good information here. And that is strange considering my past experiences at XDA. But, this is what I came up with and I should probably write a thread:
Use this video to guide you with your common sense: https://www.youtube.com/watch?v=KZaajUEybNM
Do not use the links provided in the video; instead use these links. That video is for another OnePlus device; the techniques are good but the files are bad. Simple substitution is all that is necessary and you can easily follow the directions with some commons sense.
Use this version of TWRP: https://dl.twrp.me/oneplus3t/
Get SuperSu here: https://download.chainfire.eu/696/supersu/
Get Android Studio here: https://developer.android.com/studio/index.html#Other
I just got my device and this totally worked for me. I hope this fixes your problem.
Are you solve this problem now?
And my advice for u :
[pre]please don't use SuperSU,it is insecurity on new Android version.Maybe you can use phh's or LineageOS root zip.NOT AD!
[1]Reflash twrp with fastboot.
[2]Flash root zip what I said(mokee rom support inner root).
[3]Flash rom(maybe you can use Mokee or LineageOS or Slimrom or OxygenOS and so on)
[4]flash gapps with nano or pico.
If this not solve problem,please try to flash factory image with MsmDownloadTool.
I hope my advice can help you.
Fun4Jan said:
Okay, connected my OP3T with my computer and started my cmd and went to the adb folder.
It found my device when I typed in: adb devices.
then I tried to sideload the OS but it said:
"loading: 'OnePlus3TOxygen.zp'
* cannot read 'OnePlus3TOxygen.zip' *
I don't know, what I did wrong.
Click to expand...
Click to collapse
if you device is getting recognized when adb devices is typed
just do this CMD: adb push (drag and drop the file you want to push onto the cmd line) /sdcard/
Fun4Jan said:
It doesn't working. I don't have my phone's internal memory, when I click on my OP3T and I can't copy the OS just on my phone.
It said that this folder is empy.
Is there a way to get into my root folders on my pc?
Click to expand...
Click to collapse
When this happens, it means DATA partition is unmounted. You have to mount it in twrp. If you still can't see the internal storage with your pc then wipe everything, including internal storage and reboot into twrp and you should be able to see it this time.
M4CH0 said:
Are you solve this problem now?
And my advice for u :
[pre]please don't use SuperSU,it is insecurity on new Android version.Maybe you can use phh's or LineageOS root zip.NOT AD!
[1]Reflash twrp with fastboot.
[2]Flash root zip what I said(mokee rom support inner root).
[3]Flash rom(maybe you can use Mokee or LineageOS or Slimrom or OxygenOS and so on)
[4]flash gapps with nano or pico.
If this not solve problem,please try to flash factory image with MsmDownloadTool.
I hope my advice can help you.
Click to expand...
Click to collapse
Thanks for your help.
I must say, that I didn't tried it.
I downloaded the original Recovery from OnePlus and flashed it on my OP3t.
I went to the original recovery modus and used ADB sideload to install the normal OS.
Now it's not rooted but it works fine now.
Yeah that's really good.
Related
Hi, I know this is going to sound so stupid but I need help ASAP.
I was fooling around with installing different ROM's for my HTC One, I tried the Google Edition for a while and decided it wasn't for me as I lost the TV remote. I then tried to re-flash the Android Revolution HD 12 I had on before and it wouldn't flash. I thought a wipe would work but now I've succeeded in ending up with a TWRP recovery that works fine but no software whatsoever to flash or boot to. The phone says 'No OS Installed'
Every time I turn off the phone it also says that it doesn't appear to be rooted, do I want to install supersu? The phone says 'unlocked' with CID 11111111
I have totally fallen into the idiot trap, too much confidence and ambition, zero skill and talent.
NailFace said:
Hi, I know this is going to sound so stupid but I need help ASAP.
I was fooling around with installing different ROM's for my HTC One, I tried the Google Edition for a while and decided it wasn't for me as I lost the TV remote. I then tried to re-flash the Android Revolution HD 12 I had on before and it wouldn't flash. I thought a wipe would work but now I've succeeded in ending up with a TWRP recovery that works fine but no software whatsoever to flash or boot to. The phone says 'No OS Installed'
Every time I turn off the phone it also says that it doesn't appear to be rooted, do I want to install supersu? The phone says 'unlocked' with CID 11111111
I have totally fallen into the idiot trap, too much confidence and ambition, zero skill and talent.
Click to expand...
Click to collapse
You should be able to use this toolkit to install SU and also to sideload a rom zip from your PC to the phone to reinstall your ROM of choice. Sounds like you wiped your data partition entirely. Since you have S-off and Super CID you should have no problems loading another rom. Just have to use one of the creative ways to get it on the phone (sideload, USB-OTG adapter, etc.)
http://forum.xda-developers.com/showthread.php?t=2242635
crushalot said:
You should be able to use this toolkit to install SU and also to sideload a rom zip from your PC to the phone to reinstall your ROM of choice. Sounds like you wiped your data partition entirely. Since you have S-off and Super CID you should have no problems loading another rom. Just have to use one of the creative ways to get it on the phone (sideload, USB-OTG adapter, etc.)
http://forum.xda-developers.com/showthread.php?t=2242635
Click to expand...
Click to collapse
Thanks for your reply,
could you do a step by step guide for me please, I don't have an USB-OTG adaptor.
I cannot install the program, it says its not supported by my OS (im on Windows 8)
NailFace said:
Thanks for your reply,
could you do a step by step guide for me please, I don't have an USB-OTG adaptor.
Click to expand...
Click to collapse
The steps should be here in the guide:
http://forum.xda-developers.com/showthread.php?t=2325853
Also here for sideload:
http://forum.xda-developers.com/showthread.php?t=2318497
crushalot said:
The steps should be here in the guide:
http://forum.xda-developers.com/showthread.php?t=2325853
Also here for sideload:
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
I really need a more step by step guide, I've ****ed things up already so I think I need a baby walk through
NailFace said:
I really need a more step by step guide, I've ****ed things up already so I think I need a baby walk through
Click to expand...
Click to collapse
Well the easiest way to do a sideload is using the All in One tool. Do you have access to any other PC that have Windows 7 or XP? I don't have a win 8 system to try to assist with compatibility mode with the one.exe tool.
If no other PC options are available then we will have to go the long way which will involve installing ADB like in this guide: (Under Installation section - It has 5 steps for installing ADB)
http://forum.xda-developers.com/showthread.php?t=1427008
Once ADB is installed we can use these steps from the sideload guide that I posted:
Make Sure HTC Drivers are installed and ADB is already working
1. Reboot into TWRP
2. in TWRP, Hit advanced and find Sideload
3. Swipe to start Sideload
4. Open a CMD Prompt window and Change Directories to where your adb.exe is
5. type adb devices and it should show your device connected and say sideload
6. Your ZIP file should already be in your adb folder - See Example Below
7. You are now ready to push the zip.....
8. type adb sideload nameofzip.zip <------------See Example Below
9. Wait until it says 100% and reboot back into recovery to flash the ROM
10. If hitting power does not make the screen come one, type adb reboot recovery
11. if adb reboot recovery does not work, hold power and volume down until it reboots to fastboot then go to recovery
crushalot said:
Well the easiest way to do a sideload is using the All in One tool. Do you have access to any other PC that have Windows 7 or XP? I don't have a win 8 system to try to assist with compatibility mode with the one.exe tool.
If no other PC options are available then we will have to go the long way which will involve installing ADB like in this guide: (Under Installation section - It has 5 steps for installing ADB)
http://forum.xda-developers.com/showthread.php?t=1427008
Once ADB is installed we can use these steps from the sideload guide that I posted:
Make Sure HTC Drivers are installed and ADB is already working
1. Reboot into TWRP
2. in TWRP, Hit advanced and find Sideload
3. Swipe to start Sideload
4. Open a CMD Prompt window and Change Directories to where your adb.exe is
5. type adb devices and it should show your device connected and say sideload
6. Your ZIP file should already be in your adb folder - See Example Below
7. You are now ready to push the zip.....
8. type adb sideload nameofzip.zip <------------See Example Below
9. Wait until it says 100% and reboot back into recovery to flash the ROM
10. If hitting power does not make the screen come one, type adb reboot recovery
11. if adb reboot recovery does not work, hold power and volume down until it reboots to fastboot then go to recovery
Click to expand...
Click to collapse
I owe you a beer, thank you very much. Everything working now.
I've made a mistake,
I've wiped all with twrp:
system,
boot,
cache,
internal storage
So I've no OS and no flashable zip in the device.
I've tried to use ADB sideload, but i'm not able to use. I've drivers installed in the pc, but mobile phone is not recognised (other driver missing???).
Fastboot is working and the device is recognized.
Is it possible to flash a rom via fastboot, in this current status?
Or how to make it working the ADB shell? what is missing??
Thank you all.
Please save my phone!
eternasparta said:
I've made a mistake,
I've wiped all with twrp:
system,
boot,
cache,
internal storage
So I've no OS and no flashable zip in the device.
I've tried to use ADB sideload, but i'm not able to use. I've drivers installed in the pc, but mobile phone is not recognised (other driver missing???).
Fastboot is working and the device is recognized.
Is it possible to flash a rom via fastboot, in this current status?
Or how to make it working the ADB shell? what is missing??
Thank you all.
Please save my phone!
Click to expand...
Click to collapse
hi there,
have you even bothered looking, or searching?? pretty much every thread has the info you need.
if you had bothered looking at the the Frequently Asked Question sticky including page 3
you would have your answer
or any of the other Q&A thread, for example: http://forum.xda-developers.com/showpost.php?p=52396849&postcount=11
Sounds like you need to download the right drivers for Windows and adb push a rom zip on over. If your having no luck with Windows, load up a live cd or usb of Ubuntu and install adb there.
Good luck and happy searching.
it is possible to flash a ROM/ RUU via fastboot but you should install the right ADB to your PC. other way, mount your storage via TWRP, copy your ROM to your storage, then flash it.
zigyna said:
it is possible to flash a ROM/ RUU via fastboot but you should install the right ADB to your PC. other way, mount your storage via TWRP, copy your ROM to your storage, then flash it.
Click to expand...
Click to collapse
thank you all.
I've obviously seen the faq, but nothing was working.
however, ad have you said I've to install the right ADB on my pc. In fact adb was not working because drivers was not working.
I've resolved doing the following.
Remove manually drivers from windows, install manually drivers, restart windows :good:
:good::good::good: adb now is working
Thank you for the support
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??
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.
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.