Database Develop

OnePlus 3T - A3010 - Can I Sideload the OOS 4.0.2 directly?

OnePlus 3T - A3010 - Can I Sideload the OOS 4.0.2 directly?
I'm about to receive my OnePlus 3T A3010 from gearbest, can i update it directly to OOS 4.0.2 by sideloading it with ADB?
Regards!

dbamaro said:
OnePlus 3T - A3010 - Can I Sideload the OOS 4.0.2 directly?
I'm about to receive my OnePlus 3T A3010 from gearbest, can i update it directly to OOS 4.0.2 by sideloading it with ADB?
Regards!
Click to expand...
Click to collapse
At one point when I decided to go "full stock" and I was trying to install stock OOS 4.0.0. on a "clean phone" (all data wiped) through ADB as officially supported on stock recovery, but could not find ADB version which would not fail. Too bad oneplus themselves do not provide more (working ADB version and so on) on this or at least provide some sort of FAQ on how to deal with that 47% error , considering that they do support adb sideload as such (http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_3.5.4/)
Connect your device to PC/Mac, run following command in command prompt / terminal
For Windows: “adb sideload <filename>”
For Mac/Linux: “./adb sideload <filename>”
Click to expand...
Click to collapse
^^^^^^^
bull****
There where 2 outcomes with various ADB versions I tested:
1. Either the install would reach 47% and then fail; or
2. Some adb version would simply not read the file (.zip ROM), so the install would not start at all.
If you want to upgrade OOS 4.0.2. from OOS 3.5.1.-3.5.3., which your phone probably will be running, just use VPN (Germany) and you will get OTA update to OOS 4.0.2 straight way. My friend just did that today in similar circumstances

jemeljsh said:
At one point when I decided to go "full stock" and I was trying to install stock OOS 4.0.0 , but could not find ADB version which would not fail.
There where 2 outcomes with various ADB versions I tested:
1. Either the install would reach 47% and then fail; or
2. Some adb version would simply not read the file (.zip ROM), so the install would not start at all.
If you want to upgrade OOS 4.0.2. from OOS 3.5.1.-3.5.3., which your phone probably will be running, just use VPN (Germany) and you will get OTA update to OOS 4.0.2 straight way. My friend just did that today in similar circumstances
Click to expand...
Click to collapse
Did you tried the "install from SD" on the recevery?

dbamaro said:
OnePlus 3T - A3010 - Can I Sideload the OOS 4.0.2 directly?
I'm about to receive my OnePlus 3T A3010 from gearbest, can i update it directly to OOS 4.0.2 by sideloading it with ADB?
Regards!
Click to expand...
Click to collapse
dbamaro said:
Did you tried the "install from SD" on the recevery?
Click to expand...
Click to collapse
That would not work in my case, since I was trying to go completely stock, meaning I wiped all data, flashed back stock recovery and did the OEM lock. So at that point my phone was completely empty (+ with no options to push files onto into besides ADB sideload) and ready for clean stock OOS 4.0.0. but since ADB options failed I simply used the brick recovery tool, which got me back to stock OOS 3.5.1. which then allows you to get to whatever's the latest through OTA updates. Its a longer process but same result. Well almost the same, since if you could do a full wipe and then install OOS 4.0.2. you would skip installing OOS 3.5.1. and every OTA in between. Less flashing, but as I said, the adb options and fails, so you have to go the long way to the brick tool.

jemeljsh said:
That would not work in my case, since I was trying to go completely stock, meaning I wiped all data, flashed back stock recovery and did the OEM lock. So at that point my phone was completely empty (+ with no options to push files onto into besides ADB sideload) and ready for clean stock OOS 4.0.0. but since ADB options failed I simply used the brick recovery tool, which got me back to stock OOS 3.5.1. which then allows you to get to whatever's the latest through OTA updates. Its a longer process but same result. Well almost the same, since if you could do a full wipe and then install OOS 4.0.2. you would skip installing OOS 3.5.1. and every OTA in between. Less flashing, but as I said, the adb options and fails, so you have to go the long way to the brick tool.
Click to expand...
Click to collapse
I just did it yesterday. My plan was to go to complete stock and see the stability/battery life. I bought OP3T only 4 days before, so didn't have too much information.
What I did was, wiped everything from TWRP that I was using, went to bootloader mode, flashed stock recovery for Nougat, sideloaded 4.0.2 full zip, took some time but it was finally done. Without restarting went to bootloader mode again, and locked the bootloader.
All is cool for now, BUT, there is one sh***y message that some freaking service started in enforcing mode or something.
Will try doing certain things with next build to get rid of that message.

jemeljsh said:
That would not work in my case, since I was trying to go completely stock, meaning I wiped all data, flashed back stock recovery and did the OEM lock. So at that point my phone was completely empty (+ with no options to push files onto into besides ADB sideload) and ready for clean stock OOS 4.0.0. but since ADB options failed I simply used the brick recovery tool, which got me back to stock OOS 3.5.1. which then allows you to get to whatever's the latest through OTA updates. Its a longer process but same result. Well almost the same, since if you could do a full wipe and then install OOS 4.0.2. you would skip installing OOS 3.5.1. and every OTA in between. Less flashing, but as I said, the adb options and fails, so you have to go the long way to the brick tool.
Click to expand...
Click to collapse
Where can I find this unbrick tool?

dbamaro said:
Where can I find this unbrick tool?
Click to expand...
Click to collapse
Works like a charm:
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
but you don't need it at this point, since your about to receive OP3T is complete stock anyways and it will update to 4.0.2. through OTA today

bricked onepus 3t, stuck at 47%....
I was on LineageOS ROM and wanted to return to the stock rom. From twrp, I installed the stock recovery like described on the oneplus 3t page. The upload/sideload of the stock ROM always aborted at 47%.
For me, the following solution worked und unbricked my oneplus 3t:
Operating system: Ubuntu Linux 16.04
TWRP: 3.1.1.-2
ROM: OnePlus3TOxygen_28_OTA_031_all_1708311655_e9f1f038d04044d9.zip (This is the OpenBeta 14)
1) Booted the oneplus 3t into the stock recovery
2) Booted from the stock recovery into the bootloader, there is an item in the menu that does this, I think it was under "Advanced..."
3) Unplugged usb cable and re-plugged it. Without doing this, my oneplus 3t was not recognized properly (see 4).
4) with "fastboot devices" I got sure that the device is recognized properly
5) followed the instructions here https://twrp.me/oneplus/oneplus3t.html to install twrp
6) booted the device into the new recovery (twrp)
7) copied the stock rom to the device via usb cable using file-manager (nautilus)... (in twrp, you can access /sdstorage/ via usb)
8) installed the stock rom
Altough twrp warned me that no os was installed, my oneplus 3t rebooted successfully into the stock rom. The stock rom replaced twrp with the stock recovery by itself.
Done! Maybe this helps someone.

dm verity (red)

I want do clean install so I evrything wipe expect user data. And there problems started. I haven't installed twrp, this warning shows up and i can't root device on 4.0.2 and 4.1.6. Aslo i can't install roms by sideload (?)
I tried full wipe data - don't work. I was looking in the forum Oneplus any tutorial didin't work.
I tried this tutorial https://forum.xda-developers.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094 to remove warning. It works but after update from 4.0.2 to 4.1.6 warning screen again came back. It started after updating 4.1.6 to 4.1.7.
If you can slowe this problem I will be grateful. And i sorry for my engilsh

Wronko said:
I want do clean install so I evrything wipe expect user data.
Click to expand...
Click to collapse
If you want a "clean" install, user data is the most important thing to wipe; as it is the mostly likely thing to cause problem (on a new ROM, etc.).
Not related to the other issues you mentioned. But important to note, anyway.
Wronko said:
I haven't installed twrp, this warning shows up and i can't root device on 4.0.2 and 4.1.6. Aslo i can't install roms by sideload (?)
Click to expand...
Click to collapse
I'm confused. If you haven't installed TWRP, how you are trying to root? You need TWRP, in order to root.
Also, sideload can be more problematic than just flashing a ROM in TWRP. My suggestion, would be to stop messing around, and just flash TWRP.

* I wanted to write that After installing update 4.1.6 as well as on the factory as a TWRP warning appears.
*On TWRP can't root device, TWRP think the su ZIP archives od broken.
*And TWRP by bluetooth Spark can't decrypt device (my old password od bot working )
Device works fine by In addition to the aforementioned problems

Hi,
As I have to send back my 3T for RMA, I spendt almost two nights with reading lots of guides about how to remove that red warning. The usual methods (flashing 4.0.2 FW and trying "dm_verity_disable/enable" with fastboot or reboot with "enforce_dm_verity", etc..) did not work at all. I ended up by this way:
- With 4.1.6 ROM flash TWRP (boot into bootloader, "fastboot flash recovery <filename>"
- In bootloader "fastboot format userdata" (this will remove encryption)
- Reboot to recovery (don't let the OS boot, otherwise you can start again)
- Flash SuperSU 2.79 (don't ask why, I guess this is needed for the encryption removal as well)
- Reboot to OS, check that encrytion is removed (in security settings, at the bottom you should see "Encrypt phone" instead of "Phone encrypted")
- Reboot recovery, flash OOS 3.5.4
- Reboot to OS, now the red warning should be removed
- Encrypt your phone (optional, if you like that way)
- Download 4.1.6 OOS image on the phone and use System update in the settings with local update to get back to 4.1.6
You should have 4.1.6 now without the red warning. If you want to get rid of the orange warning as well, you can flash the stock recovery and lock the bootloader back.
After that my phone was like an original one... With leaving some of these steps out, I always got failed..
I wrote this by memory (performed that yesterday), so it's possible I forgot something, but feel free to write a PM and I try to help. Of course the process will wipe all your data, so backup everything you need...

ilyr73 said:
Hi,
As I have to send back my 3T for RMA, I spendt almost two nights with reading lots of guides about how to remove that red warning. The usual methods (flashing 4.0.2 FW and trying "dm_verity_disable/enable" with fastboot or reboot with "enforce_dm_verity", etc..) did not work at all. I ended up by this way:
- With 4.1.6 ROM flash TWRP (boot into bootloader, "fastboot flash recovery <filename>"
- In bootloader "fastboot format userdata" (this will remove encryption)
- Reboot to recovery (don't let the OS boot, otherwise you can start again)
- Flash SuperSU 2.79 (don't ask why, I guess this is needed for the encryption removal as well)
- Reboot to OS, check that encrytion is removed (in security settings, at the bottom you should see "Encrypt phone" instead of "Phone encrypted")
- Reboot recovery, flash OOS 3.5.4
- Reboot to OS, now the red warning should be removed
- Encrypt your phone (optional, if you like that way)
- Download 4.1.6 OOS image on the phone and use System update in the settings with local update to get back to 4.1.6
You should have 4.1.6 now without the red warning. If you want to get rid of the orange warning as well, you can flash the stock recovery and lock the bootloader back.
After that my phone was like an original one... With leaving some of these steps out, I always got failed..
I wrote this by memory (performed that yesterday), so it's possible I forgot something, but feel free to write a PM and I try to help. Of course the process will wipe all your data, so backup everything you need...
Click to expand...
Click to collapse
Can you link for your SuperSU zip and TWRP?

Wronko said:
Can you link for your SuperSU zip and TWRP?
Click to expand...
Click to collapse
TWRP for Oneplus 3T
SuperSU 2.79 for Oneplus 3T

After flashing su zip I want to check if I have encrypted phone and boot frozen.
So I go to recovery and install 4.1.6 rom and i get information "Error opening: '/data/system/ndebugsocet' no such file or directory"
Again something went wrong
Edit: Somehow I just install 4.0.2 (again bootloop), and stock recovery (i booted to recovery 2 times and on second try recovery ask me for password(?) so i wiped device). Everything was fine expect dm verity. At this point I give up. So having everything stock i just use ota (4.0.2>4.1.6) and this was probobly the key for success.
In the evening I will try root my device and see if everything is good.

Wronko said:
After flashing su zip I want to check if I have encrypted phone and boot frozen.
So I go to recovery and install 4.1.6 rom and i get information "Error opening: '/data/system/ndebugsocet' no such file or directory"
Again something went wrong
Edit: Somehow I just install 4.0.2 (again bootloop), and stock recovery (i booted to recovery 2 times and on second try recovery ask me for password(?) so i wiped device). Everything was fine expect dm verity. At this point I give up. So having everything stock i just use ota (4.0.2>4.1.6) and this was probobly the key for success.
In the evening I will try root my device and see if everything is good.
Click to expand...
Click to collapse
Have you flashed TWRP and 3.5.4 first? Have you used bootloader with "fastboot format userdata" before flashing supersu (remembering that after this, normal boot should not start before supersu is flashed)?
Also I am not sure if flashing 3.5.4 image will update the firmware as well, but for safety, you might try to flash that as well: Oneplus 3T Firmware collection

I didn't flash 3.5.4 at all, just 4.0.2. I used "fastboot format userdata" in bootloader. And then there was a problem (boot loop.). And after that i booted into recovery(I had then stock) asked me for password )At this point I did not have any) so I wiped my device again (recovery suggest it). The device turned on normally, but still i had dm verity. Finally I updated by OTA to 4.1.6 and dm verity screen was gone.
At this point I install TWRP and rooted, without any problem.
So i think fix for this situation was going back to full stock and use OTA. (Again sorry for my English, I trying my best)

How to update to Oreo from Magisk rooted stock rom OOS 4.5.1?

Can anyone help me with the steps to update to Android Oreo (OOS 5) from OOS 4.5.1 retaining root?
Below are the current setup of my phone
Rooted - Yes (Magisk version 14.0)
Recovery - TWRP version 3.1.1-2
Current Rom - Stock OOS 4.5.1
I haven't had any problems in updating earlier but now when I try to flash the full oreo rom from TWRP, I am getting error 7.
Below are the steps I followed.
Downloaded the full OTA zip.
Rebooted to recovery.
Unistalled Magisk.
Tried to flash the Oreo OTA zip. At this point TWRP showed error 7.
Reinstalled Magisk and rebooted to system.
Phone is working fine.

you need to use latest twrp for oreo, for example blue spark version, search for it on xda...

Follow this guide here:
https://forums.oneplus.net/threads/how-to-install-oos-5-0-over-rooted-4-5-1.684519/#post-17134194
It's exactly what you need.

All Oreo ROM threads clearly state under the "Instructions" heading, that you need either AkhilNarangs Modified TWRP or Blu_Sparks TWRP V50. Using stock TWRP would result in an error.
If the error may still persist, try flashing a different firmware.

Just to get some more clarity.
I have the original OTA full zip. Should I download the zip file from your thread?
Can I install the custom version of TWRP using the official TWRP app? I am bit confused on how to install it.
Is it important that I should use Magisk 14.3 or will v 14 have the same effect?

Hey there,
I can tell you how I have done it yesterday (successfully).
1. Update TWRP - I prefer blu sparks version 8.52 (Link: https://forum.xda-developers.com/devdb/project/dl/?id=27225); you can do it by using your installed TWRP Version (Install .img)
2. Dirty flash OOS 4.5.1 again (to remove root / magisk) - once finished DO NOT reboot into system, reboot into Recovery/TWRP to verify the new version and afterwards to system
3. flash OOS 5.0 (Oreo) - dirty flash is okay
4. flash magisk Version 14.3
These are the steps I have followed yesterday and all is running perfect and without any problems.
BR

Which recovery is mentioned in this linked discussion resp. in the linked download? Is it blu_spark TWRP?
Regards
Clark

This worked perfectly for me.

Glad to hear that everything is good ?

I did the same and I was suddenly encrypted and no chance to get my data back. Still forcing clean my phone because I cannot format the device. I get always an error message in TWRP like: unable to format to remove encryption
I go crazy...

Enter recovery and wipe data and then cache.
Then reflash the rom and probably you will be good to go.

No sim card after twrp restore

I have a oneplus 3t and am on OOS 4.0.3 and decided to upgrade to OOS 5.0. I downloaded the ROM, took a backup and then clean wiped my phone. Then I tried installing the ROM but it failed. So I decided to restore my backup from USB OTG. While restore failed and it showed error 255 while restoring data, so I wiped again and then restored everything except data. The phone rebooted and everything is fine except the phone is not detecting my sim card. I have tried restoring again and rebooting but it didn't work. I am using twrp 3.1.1
Please give a solution or tell me which ROM version to flash to solve this problem.

Just follow this guide to get back to factory default. And then try OTA update with the default recovery instead of TWRP.
https://www.google.se/amp/s/forum.x...ck-unbrick-tutorial-oneplus-3t-t3515306/page1

You need a special TWRP in order to upgrade to Android Oreo. Just google for Oneplus3 Oreo TWRP and theres a OnePlus-Forum Thread where you can download the TWRP that is needed for the Oreo Upgrade. Your Backup should work without Problems after you installed Oreo

just install bluSpark TWRP v8.61 from
https://forum.xda-developers.com/devdb/project/dl/?id=27655
and download official 5.0.1 ROM zip file from oneplus official site.
then you can proceed. You can use Magisk 15.3 after ROM installation for root access.
Make sure to reboot TWRP once after wiping everything from TWRP otherwise you may lose TWRP where stock recovery may take place.

Having trouble with TWRP error 1 "Cannot mount /system"

Hello, everyone!
I hope anyone can help me.
Yesterday I assisted with rooting and flashing a Mi 9 T Pro with Xiaomi.eu firmware.
Here are the steps which were done:
1. Unlocking bootloader via MiFlash Tool.
2. Flashing TWRP (this one: https://androidfilehost.com/?fid=6006931924117906979)
3. First trouble: It only booted once into TWRP with "fastboot boot recovery xxx.img, after formatting data and a restart of TWRP it refused to get access again, neither with a command nor with hardware keys. It was stuck in fastboot.
4. With the MiFlash Tool I reverted to the stock global (this one: http://bigota.d.miui.com/V10.3.1.0....M_20190805.0000.00_9.0_global_135788d537.tgz)
5. After successfully flashing the stock ROM, I downloaded and flashed this TWRP: https://www.androidfilehost.com/?fid=1899786940962577905
6. Flashing this version of TWRP went perfectly fine.
7. In TWRP I formatted data again. I restarted TWRP and copied the following files to storage:
ROM: https://androidfilehost.com/?fid=1899786940962578113
Magisk 19.2.zip
Disable_dm verity_ForceEncrypt
8. I wiped Dalvik, cache, system and data.
9. I flashed ROM - it went through without problems
10. I tried to flash the dm verity, then an error occurred (please see the attached picture).
Can you please tell me what I'm doing wrong? Root is mandatory for me, I definitely need it.
I'm looking forward to your input and your help, it's very appreciated!

try to unmount system then flash it again

SkipperRyujin said:
try to unmount system then flash it again
Click to expand...
Click to collapse
Thanks for your input. I tried that, unfortunately this didn't work.
But I found the solution a few minutes ago:
I downloaded TWRP 3.3.1-13 (one version newer) and flashed it inside of my old TWRP. I rebooted to recovery again and then flashed Magisk without problems.
(The dm verity still refuses to install but the phone is booting and running.)

Well, it always work for me, or simply reboot recovery also work. Try wzsx twrp, it has remove DM verity & forced encryption remover in advanced menu