[GUIDE] OOS v4.0.3 ---> FLASH & ROOT STOCK -OR- CUSTOM ROM WITH EASE & CORRECTLY

[mr-cook]

Hi,

I'm trying to follow this guide and I've stuck on step 12.

When I try to sideload OO4.0.2. zip file I get error cannot read file.. Please could you help me....

You need to put the full extension to the file (ie... Home/john_doe/Android/oneplus...)

 

[ZiViky]

You need to put the full extension to the file (ie... Home/john_doe/Android/oneplus...)

Hi, Thank you. I have .zip in adb folder. I've tried with full path and same error : cannot read

I've even tried to download file 2nd time and same error.

 

[mr-cook]

Hi, Thank you. I have .zip in adb folder. I've tried with full path and same error : cannot read

I've even tried to download file 2nd time and same error.

I just do it by typing in the command- "adb sideload" then a space, then just drag the file into the command box to make sure I have the exact directory. (This in linux, but should work the same on Windows I would think).

 

[ZiViky]

Hi,

still same error.

When I write adb devices I get device name... so it is strange that I get read errror.

My reason to go through tutorial is that I have dm-verity error on 4.0.0.

 

[rahulgarg-ge]

Hi,

still same error.

When I write adb devices I get device name... so it is strange that I get read errror.

My reason to go through tutorial is that I have dm-verity error on 4.0.0.

I had the same problem but not able to find fix for it. I was on 4.0.1 so did a clean wipe from stock recovery and normal upgrade which changed the file system. After this I installed TWRP and FreedomOS

 

[ZiViky]

I had the same problem but not able to find fix for it. I was on 4.0.1 so did a clean wipe from stock recovery and normal upgrade which changed the file system. After this I installed TWRP and FreedomOS

Hi, thank you. I've done exactly the same. Phone notified that there is update OTA incremental but it failed to install. Then system proposed downloading full OTA.
This went fine and dm-verity message disappeared. Then I've installed official TWRP and latest SU.

Now it is working fine.


Thank you

 

[luutuananh]

Don't know why but I need to install Ubuntu myself to successful sideload the zip, hence I can't do it on Windows. Now I get the dm-verify message no longer.
Only the 4.0.2 zip has the problem, other zips work fine on Windows.

 

[p2001j]

Oneplus 3T

Does this work for Oneplus 3T ?

 

[dbabaev21]

SKIP

 

[dbabaev21]

I have unlocked the bootloader, and tried to sideload TWRP 3.0.3, and this looked ok, but it will not boot into TWRP recovery. I am on F2FS filesystem.

What can I do best now ?

Use a different TWRP. Blu_spark first and if it didn't work, use Unofficial.

hmm..So i do not have any option but to completely format the phone??

Pretty much. Make sure to back up personal data beforehand.

Hey there,

I was wondering, I'm on oos 4.0.1 and want to update to 4.0.2. Can i just flash stock recovery and then apply OTA in system? Or sideload it?
Will i loose any data doing this ?

Kindest regards.

Yeah, but sideload it. I think it won't touch your data. It might break your root.
Back up your data before giving it a try.

I tried the guides and did a complete format. But after that sideload did not work. Could not read zip. Then I flashed twrp via fastboot and then pushed the full rom zip and super su. Flashed the zips and reboot and am now on 4.0.2 now. But now the storage has become read only. How to change it to read - write mode so that I can copy files back. The DM-verity warning still comes up while booting up. The phone boots fine after that though.

Read FAQ #5 for dm-verity issue and FAQ #17 for (cannot read "image.zip").
The storage in read mode only, probably due to encryption. Use a different TWRP (v15 blu_spark or Unofficial) and decrypt your data. Follow Section B.

Hello, sorry for the question, but I have been reading around this thread and the Internet for a while but still have some doubts and don't want to risk to brick my phone or to put myself in a difficult situation whatsoever.
I have the OP3 with 3.2.8 stock, plus TWRP and Root. I received the OTA notification but I know that being rooted I cannot simply click on "update" or I'll be in trouble.
What I want is just to upgrade to official OOS 4.0.2 with TWRP and root, as I am now. Can you kindly suggest me the simplest way to achieve this?
I would prefer not to factory reset, if possible, but if it's recommended then ok.
Thank you for any hint

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk

Follow Section D. Reflash stock recovery, sideload the full (1.4Gb) OTA, boot to OS, reflash TWRP and root.
It will not touch your data.
I hope everything goes smooth.

Thanks for the great post. Is there a way to get XPOSED working in FreedomOS. Looks like 2.2 doesnt support it

It's not yet supported for Nougat. We will all know when it comes out.
If you want to use it, roll back to OOS v3.2.8

Hi,

I'm trying to follow this guide and I've stuck on step 12.

When I try to sideload OO4.0.2. zip file I get error cannot read file.. Please could you help me....

Read FAQ #4 and #17.

You need to put the full extension to the file (ie... Home/john_doe/Android/oneplus...)

Thank you for trying to help! I appreciate it!

Hi, Thank you. I have .zip in adb folder. I've tried with full path and same error : cannot read

I've even tried to download file 2nd time and same error.

Read FAQ #4 and #17. And redownload again (updated to official OnePlus website download page).

I just do it by typing in the command- "adb sideload" then a space, then just drag the file into the command box to make sure I have the exact directory. (This in linux, but should work the same on Windows I would think).

Thank you for trying to help! I appreciate it!

Hi,

still same error.

When I write adb devices I get device name... so it is strange that I get read errror.

My reason to go through tutorial is that I have dm-verity error on 4.0.0.

See FAQ #5 for dm-verity error.

I had the same problem but not able to find fix for it. I was on 4.0.1 so did a clean wipe from stock recovery and normal upgrade which changed the file system. After this I installed TWRP and FreedomOS

Read FAQ #4 and #17.

Hi, thank you. I've done exactly the same. Phone notified that there is update OTA incremental but it failed to install. Then system proposed downloading full OTA.
This went fine and dm-verity message disappeared. Then I've installed official TWRP and latest SU.

Now it is working fine.


Thank you

Awesome! Good to know!

Don't know why but I need to install Ubuntu myself to successful sideload the zip, hence I can't do it on Windows. Now I get the dm-verify message no longer.
Only the 4.0.2 zip has the problem, other zips work fine on Windows.

Good to know that it works in Ubuntu.
Read FAQ #4 and #17.

Does this work for Oneplus 3T ?

Yes, read "DISCLAIMER & IMPORTANT" Section.

 

[TNSMANI]

@dbabaev21

FAQ #5 needs to be updated. Only one command ie. the 'enable' command needs to be executed.

Tested and working fine.

 

[dbabaev21]

@dbabaev21

FAQ #5 needs to be updated. Only one command ie. the 'enable' command needs to be executed.

Tested and working fine.

Thank you!
I will update.

 

[Raainman]

I went for 3.0.4-0 (not officially released yet)

I'm on stock OOS 4.0.2 with unlocked bootloader (double check if you have unlocked this under developer options)

First I copied chainfire super su to the phone
https://download.chainfire.eu/supersu-stable

Then went into fastboot (power down, and then volume up+power button) and I used fastboot to flash recovery from windows

fastboot flash recovery twrp-3.0.4-0-oneplus3.img

Then used the up/down keys to select recovery and went into TWRP (which worked this time) TWRP was able to decrypt without an issue using the pin I setup before.

Then installed the above downloaded supersu, and then rebooted.

SuperSU rebooted the phone an extra time (scary!) and then I ended up in a fully working encrypted and rooted OOS 4.0.2.

If you have unlocked bootloader, then yes.
Use Section D from #13.
That's all you need to do.
Make sure you're on F2FS file system (check in DiskInfo app).

Use a different TWRP. Blu_spark first and if it didn't work, use Unofficial.

 

[dbabaev21]

I went for 3.0.4-0 (not officially released yet)

I'm on stock OOS 4.0.2 with unlocked bootloader (double check if you have unlocked this under developer options)

First I copied chainfire super su to the phone
https://download.chainfire.eu/supersu-stable

Then went into fastboot (power down, and then volume up+power button) and I used fastboot to flash recovery from windows

fastboot flash recovery twrp-3.0.4-0-oneplus3.img

Then used the up/down keys to select recovery and went into TWRP (which worked this time) TWRP was able to decrypt without an issue using the pin I setup before.

Then installed the above downloaded supersu, and then rebooted.

SuperSU rebooted the phone an extra time (scary!) and then I ended up in a fully working encrypted and rooted OOS 4.0.2.

Use a different TWRP. Blu_spark first and if it didn't work, use Unofficial.

So, using Unreleased TWRP v3.0.4-0 solved your issue. Great!
I've read in here: https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391 , that people encountering issues with Nougat can use the unreleased version.

 

[bellasghi64]

I have a question, i followed the passages to delete dm verity until point 10. I'm already on 4.0.2, do i need to sideload it again to delete dm verity?

 

[dbabaev21]

I have a question, i followed the passages to delete dm verity until point 10. I'm already on 4.0.2, do i need to sideload it again to delete dm verity?

It will reset your OS.
But, if you're already on OOS v4.0.2, then read FAQ #5.
If it didn't work, then you'll have to flash OOS v4.0.2

Good luck!

 

[bellasghi64]

It will reset your OS.
But, if you're already on OOS v4.0.2, then read FAQ #5.
If it didn't work, then you'll have to flash OOS v4.0.2

Good luck!

I'm already on stock recovery and the message didn't disappear, i even tried to type in fastboot: fastboot oem disable_dm_verity
fastboot oem enable_dm_verity, but it still didn't work. Do you think i need to go back to 4.0.1 and try to sideload 4.0.2?

 

[dbabaev21]

I'm already on stock recovery and the message didn't disappear, i even tried to type in fastboot: fastboot oem disable_dm_verity
fastboot oem enable_dm_verity, but it still didn't work. Do you think i need to go back to 4.0.1 and try to sideload 4.0.2?

You can try.
I suggest redoing Section A, and make sure to wipe your data (Backup your data beforehand).

 

[abalam]

I'm already on stock recovery and the message didn't disappear, i even tried to type in fastboot: fastboot oem disable_dm_verity
fastboot oem enable_dm_verity, but it still didn't work. Do you think i need to go back to 4.0.1 and try to sideload 4.0.2?

You must type only fastboot oem disable_dm_verity and not both

 

[bellasghi64]

You can try.
I suggest redoing Section A, and make sure to wipe your data (Backup your data beforehand).

If i just flash again 4.0.2 over 4.0.2 what do you think is going to happen? Will it wipe everything or just do nothing?

---------- Post added at 09:20 PM ---------- Previous post was at 09:20 PM ----------

You must type only fastboot oem disable_dm_verity and not both

This still didn't work