Unable to recover OxygenOS on Oneplus3 - OnePlus 3 Questions & Answers

Hello everyone,
This morning, I wanted to recover OxygenOS on my Oneplus3. I'm currently running Cyanogenmod 13.
I used the following guide: "[GUIDE] How to Unroot your OnePlus 3 / 3T and go back completely to stock" (Since I'm a newb, I can't post the link. But Google will get you there)
I booted into fastboot, issued the fastboot flash recovery recovery_op3.img and fastboot oem lock commands from my Linux termina, and rebooted in recovery mode.
In recovery mode, I then erased the cache and all that, selected the "Upgrade android from USB" and issued the adb sideload ota.zip command. This is where my problems began.
After running the command, I got the error "error: protocol fault (no status)". I tried to look this error up, but couldn't find useful information.
I started to panic a bit, fearing that my phone would be bricked. However, after booting back into fastboot mode, unlocking OEM, and rebooting, my phone would boot back into Cyanogenmod 13 (A clean install).
So now I don't have a bricked phone. However, I really would like to go back to OxygenOS, so my question is whether anyone knows how to solve my problem.
Summary:
Running Linux (Debian 8) on my PC;
Running Cyanogenmod13 on my Phone;
Want to recover OxygenOS, but adb sideload gave me "error: protocol fault (no status)";
Tried running the adb sideload command as root, however that did not work;
Can still use the Cyanogenmod13.

I've seen that error once before. I had to disconnect the phone, kill the ADB process, reconnect the phone and restart ADB to get it to work.
That worked for me. Hope that helps.
Sent from my OnePlus 3 using XDA Labs

Tybalt said:
I've seen that error once before. I had to disconnect the phone, kill the ADB process, reconnect the phone and restart ADB to get it to work.
That worked for me. Hope that helps.
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
Hey, thanks for responding.
I forgot to mention that I also tried killing the adb process several times, using the adb kill-server command and by killing the process sending SIGKILL.
Another thing I tried was using another Debian machine, which is my laptop. Still, those things did not solve my issue.

Never relock your boot loader, most bricks are due to relocking.
Flash twrp, flash oxygen os ,boot, enable everything,if you want complete stock, flash stock recovery ,flash oxygen os boot to complete stock os.

Backup youre working rom..
First, you need unlocked bootloader.
1.Flash twrp 3.0.4.1 or twrp-3.1.0 x v.26 blu_spark. Reboot to recovery.
2.Clean flash (wipe data-dalvik-system-cache) Oxygen OS, since you come from a custom rom. Flash SuperSu or Magisk, if you want root. Reflash recovery. Reboot to recovery.
If youre phone does not boot in recovery, press Power till phone vibrates. Press vol. down & choose:
1. Select Bootloader. Flash recovery from PC. Safest way to flash recovery.
or
2.Select recovery. Reflash recovery. Reboot recovery.
After you are sure that you got a working recovery reboot to system.

null0seven said:
Backup youre working rom..
First, you need unlocked bootloader.
1.Flash twrp 3.0.4.1 or twrp-3.1.0 x v.26 blu_spark. Reboot to recovery.
2.Clean flash (wipe data-dalvik-system-cache) Oxygen OS, since you come from a custom rom. Flash SuperSu or Magisk, if you want root. Reflash recovery. Reboot to recovery.
If youre phone does not boot in recovery, press Power till phone vibrates. Press vol. down & choose:
1. Select Bootloader. Flash recovery from PC. Safest way to flash recovery.
or
2.Select recovery. Reflash recovery. Reboot recovery.
After you are sure that you got a working recovery reboot to system.
Click to expand...
Click to collapse
Thanks for responding.
Since I don't understand everything yet, I will spend this evening looking up everything in detail, before I start giving it another try. Do you perhaps know of a tutorial about this specific situation? I don't want to bother you by questioning everything you stated in your instructions. They seem clear enough to be able to be looked up on Google :laugh:
drmuruga said:
Never relock your boot loader, most bricks are due to relocking.
Flash twrp, flash oxygen os ,boot, enable everything,if you want complete stock, flash stock recovery ,flash oxygen os boot to complete stock os.
Click to expand...
Click to collapse
Thanks for responding.
By the steps after "if you want complete stock", do you mean that I should keep the bootloader unlocked, and then perform the same steps as in the tutorial that I used?
EDIT:
@ null0seven: I found these steps online as I was looking up some things you said (I don't have much time since I will celebrate eastern with my family today)
Rooted Users or users with ROMs other than OxygenOS having new bootloader (Official CM 13,CM 13 Based ROMs dated later than 04 June 2016,H2OS Marshmallow)​
Step 1 :- Download the OxygenOS 3.0.2 full zip from the top of the post.
Step 2 :- Boot into TWRP.Wipe Dalvik,System,Data and Cache.After that,flash OxygenOS 3.0.2.
Step 3 :- [OPTIONAL] Flash SuperSU from here :- https://www.androidfilehost.com/?fid=24459283995297946
Step 4 -> Reboot System.
Of course, this is about an old version of OxygenOS. But it looks the same as you said.
I think this, combined with your instructions, will make it a bit clearer. Still one question: What do you mean exactly by flashing?

dvbeck
https://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733

Related

[HELP GUIDE] - Can't flash TWRP on Oxygen OS 3.2.1

Today I have faced a strange situation, I installed TWRP (after unlocking the bootloader) on my OP3 as soon as I received the device then I flashed custom ROM by @Grarak http://forum.xda-developers.com/oneplus-3/development/rom-unofficial-cyanogenmod-13-t3399089.
After using for some days I decided to give Oxygen OS another try, so I wiped the cache,data,system and Flashed full OTA provided by @namanbhalla https://forums.oneplus.net/threads/...ficial-oxygen-os-roms-and-ota-updates.450783/
Every thing went smooth but after starting up I wasn't able to goto twrp, for some strange reason twrp was automatically replaced with stock recovery. OK, I decided to reflash twrp, but bang! after so many flashing I wasn't able to boot into twrp, still there was stock recovery.
Solution:
1) fastboot oem unlock (re run even if it says already unlocked)
2) fastboot flash recovery twrp-3.0.2-0-oneplus3.img
now TWRP is installed.
I not Android Developer and cant guarantee above will work and wont harm your device. Try at your own risk.
that is all not needed, i have had this happen to me multiple times reflashing Stock and Stock recovery replaces TWRP, all u have to do is boot up to fastboot mode and flash TWRP, do not reboot, use Power + Vol + and when the Unlocked bootloader screen comes up press the VOL key and click recovery and TWRP is back. no need to do the unlock bootloader again, unless u unchecked it, just make sure it is checked when flashing the Stock rom again or u can just use flashify if u rooted stock before the recovery got replaced somehow, i have even had this happen on FreedomOS 3.2.1

help: my phone keep booting into twrp recvery

hey'
every time i boot my phone it bootloop into recavery
what to do?
mega unbrick guide...
timrock7 said:
mega unbrick guide...
Click to expand...
Click to collapse
but in the guide it's you see nothig but a black screen i have recavery https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
it hapen when i exedantly press the istall update of the ota (i had OxygenOS 4.0 and i perss on the update of 4.0.3)
You should never install an update through the phone's update setting while using a custom recovery. The updates are designed to work with the stock recovery only.
If you can still boot into and use TWRP, use it to flash the full ROM of OOS 4.0.3.
If you can't boot into TWRP, try to see if fastboot works and manually sideload a working ROM in.
Otherwise, you're going to have to use the unbrick guide. Your phone doesn't have to be completely bricked to use it. It simply reverts the phone to a truly factory-fresh state (relocks bootloader, wipes everything, etc. - At least method 2 does anyways).
I got stuck in the same situation some time ago, and in order to solve it I had to flash the stock recovery, let it restart, it tried to update (and failed) and then it booted to system again. Hopefully that way you can avoid installing everything again. Once the device boots you can try to update with the stock recovery and revert to twrp if you want.

Unbricking after a hard brick not working out.

So my OP3 got bricked and I used @Naman Bhalla guide to unbrick my phone using the second method which flashes an old OOS after unbrick. I was successful in unbricking my phone, however once the phone restarts after the unbrick tool it gets stuck in the OOS boot animation (The rotating O animation) and then it reboots and this continues.
I've tried,
1) Sideloading another Stock ROM (OOS 5.0.1.) via stock recovery: Just rebricks my phone
2) Flashing TWRP 3.1.0-0 and tried to install zip for 5.0.1 : TWRP does't recognize phone, (ERROR 7, This ROM is for OnePlus 3, This device is " ") and thus it doesn't flash.
3) Tried upgrading TWRP to 3.2.1. : could'nt do it - Lost recovery, phone just restarts to a black screen with white notification light.
4) Tried flashing OOS 4.5.1 (Nougat) via TWRP 3.1.: Does't boot up. Doesn't even go to the animation and restarts after OnePlus Logo.
Yes, I was stupid enough to not have done a nandroid backup. Desperately need help.
yawarkhalid said:
So my OP3 got bricked and I used @Naman Bhalla guide to unbrick my phone using the second method which flashes an old OOS after unbrick. I was successful in unbricking my phone, however once the phone restarts after the unbrick tool it gets stuck in the OOS boot animation (The rotating O animation) and then it reboots and this continues.
I've tried,
1) Sideloading another Stock ROM (OOS 5.0.1.) via stock recovery: Just rebricks my phone
2) Flashing TWRP 3.1.0-0 and tried to install zip for 5.0.1 : TWRP does't recognize phone, (ERROR 7, This ROM is for OnePlus 3, This device is " ") and thus it doesn't flash.
3) Tried upgrading TWRP to 3.2.1. : could'nt do it - Lost recovery, phone just restarts to a black screen with white notification light.
4) Tried flashing OOS 4.5.1 (Nougat) via TWRP 3.1.: Does't boot up. Doesn't even go to the animation and restarts after OnePlus Logo.
Yes, I was stupid enough to not have done a nandroid backup. Desperately need help.
Click to expand...
Click to collapse
Try with eng.stk's TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Item 5 in the list.
tnsmani said:
Try with eng.stk's TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Item 5 in the list.
Click to expand...
Click to collapse
Gave this a shot. Not booting up again. Goes to blank screen with white notification light.
Update: I've even tried rooting phone and flashing custom rom: Doesn't even go to animation
I've also tried method 1, erased the system via fastboot and reflashed the official OOS 3.1.2. zip file via adb sideload. Still the same result on official zip.
yawarkhalid said:
Update: I've even tried rooting phone and flashing custom rom: Doesn't even go to animation
I've also tried method 1, erased the system via fastboot and reflashed the official OOS 3.1.2. zip file via adb sideload. Still the same result on official zip.
Click to expand...
Click to collapse
If Method 2 doesn't work, Method 1 will definitely not work.
After flashing TWRP, are you able to boot to it (without flashing any ROM)? Flashing OOS or Open Beta will overwrite TWRP. So try this: wipe everything and flash TWRP, boot to TWRP and flash ROM and again TWRP, then flash Magisk and boot to system.
When you get white LED, hold power button for 7 to 10 seconds, it will switch off. Then press power button again and you will boot to the options menu to choose bootloader, recovery etc. You may not have to use Method 2 every time if this works for you.
tnsmani said:
If Method 2 doesn't work, Method 1 will definitely not work.
After flashing TWRP, are you able to boot to it (without flashing any ROM)? Flashing OOS or Open Beta will overwrite TWRP. So try this: wipe everything and flash TWRP, boot to TWRP and flash ROM and again TWRP, then flash Magisk and boot to system.
When you get white LED, hold power button for 7 to 10 seconds, it will switch off. Then press power button again and you will boot to the options menu to choose bootloader, recovery etc. You may not have to use Method 2 every time if this works for you.
Click to expand...
Click to collapse
Hey thanks for the help. Will give this a shot now. Can you tell me what method I should use to flash magisk?
Also, I am able to access TWRP but when flashing a rom via TWRP it gives me error 7 i.e. can't install this since because it is for OnePlus 3 this device is " ". Also, with method 2 I already have a stock rom installed, I've tried wiping system via fastboot and sideloading another ROM too, that doesn't work.
yawarkhalid said:
Hey thanks for the help. Will give this a shot now. Can you tell me what method I should use to flash magisk?
Also, I am able to access TWRP but when flashing a rom via TWRP it gives me error 7 i.e. can't install this since because it is for OnePlus 3 this device is " ". Also, with method 2 I already have a stock rom installed, I've tried wiping system via fastboot and sideloading another ROM too, that doesn't work.
Click to expand...
Click to collapse
Magisk to be flashed through TWRP.
If you know how, remove this first line from the updater script and then flash it: getprop("ro.build.product") == "OnePlus3" || abort("This package is for "OnePlus3" devices; this is a "" + getprop("ro.build.product") + ""."); This is what is preventing TWRP from flashing the ROM. Removing this line will result in no checks for device type while flashing the ROM.
tnsmani said:
Magisk to be flashed through TWRP.
If you know how, remove this first line from the updater script and then flash it: getprop("ro.build.product") == "OnePlus3" || abort("This package is for "OnePlus3" devices; this is a "" + getprop("ro.build.product") + ""."); This is what is preventing TWRP from flashing the ROM. Removing this line will result in no checks for device type while flashing the ROM.
Click to expand...
Click to collapse
Hi, already did that, still is't flashing.
Lastly, I managed to lock my bootloader now somehow by running the 3.0.8 version of the MSMTool. Now I have no working OS, A locked bootloader and no way to flash TWRP. I should should throw my phone in the garbage now. Shouldnt I? :crying:
yawarkhalid said:
Hi, already did that, still is't flashing.
Lastly, I managed to lock my bootloader now somehow by running the 3.0.8 version of the MSMTool. Now I have no working OS, A locked bootloader and no way to flash TWRP. I should should throw my phone in the garbage now. Shouldnt I? :crying:
Click to expand...
Click to collapse
NEVER GIVE UP, atleast not so soon. Contact OnePlus and ask them for a remote session, they may be able to restore it.
Though you are not able to flash TWRP, you can boot TWRP by using the adb command "fastboot boot twrp.img" and then play with it. Place the TWRP within the adb folder while trying this. (Replace twrp.img with the name of your TWRP or rename your TWRP as twrp.img)
Either you have encryption issues or you have a hardware issue if you are not able to flash anything successfully.
This is the end of my knowledge.
Take a look here:
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
or here:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
jeffrey268 said:
Take a look here:
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
or here:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
Click to expand...
Click to collapse
ummm thanks jeffery. But that tool is exactly what i've been using and what isn't working for me in ways i mentioned above. Thanks though.
tnsmani said:
NEVER GIVE UP, atleast not so soon. Contact OnePlus and ask them for a remote session, they may be able to restore it.
Though you are not able to flash TWRP, you can boot TWRP by using the adb command "fastboot boot twrp.img" and then play with it. Place the TWRP within the adb folder while trying this. (Replace twrp.img with the name of your TWRP or rename your TWRP as twrp.img)
Either you have encryption issues or you have a hardware issue if you are not able to flash anything successfully.
This is the end of my knowledge.
Click to expand...
Click to collapse
Gives me the error, "Unlock device to use this command"
I am able to flash rom via MSMTool, it even dash charges and all. But I can't boot into the system. It gets stuck in OOS animation while booting. Been at it for 3 days. Can it really be a hardware issue if my bootloader and recovery both are working?
Lastly, do you have any way I could unlock the bootloader without system permissions?
Putting an end to this madness. after 4 days in front of my laptop. Had a remote session with a OnePlus tech support team. Discarding my phone unfortunately. Thinking of shifting to a Xiaomi Redmi Note 5 Pro since I can't afford a OnePlus 5T anymore. Thanks to everyone who helped. This thread can be closed now.

[HELP] Mate SE in TWRP bootloop after installing openkirin lineageOS beta 4

Mate SE, installed TWRP 3.2.1-0 Pretorian80 Edition then installed openKirin lineageOS beta 4. Went to do a factory reset and now TWRP starts on startup but does not get past the loading page. Tried rebooting into bootloader, using the button combo or adb reboot bootloader only brings TWRP back up with the same issue. Any ideas?
From what I understand, you need to flash lineage via fastboot. Did you do that??
coolchris305 said:
From what I understand, you need to flash lineage via fastboot. Did you do that??
Click to expand...
Click to collapse
Yeah I launched the bootloader and used fastboot to flash it. The flash went through fine, then it rebooted and asked if I wanted to factory reset the device and I selected yes. Now it won't shut off, it only reboots into TWRP's loading page and sits there.
I should mention I have access to some ADB commands now but rebooting into bootloader won't work.
EDIT: got it working, just had to time rebooting it and plugging it in and holding vol- and power correctly, took me 30 or so tries, fml
JakeBuck said:
Yeah I launched the bootloader and used fastboot to flash it. The flash went through fine, then it rebooted and asked if I wanted to factory reset the device and I selected yes. Now it won't shut off, it only reboots into TWRP's loading page and sits there.
I should mention I have access to some ADB commands now but rebooting into bootloader won't work.
EDIT: got it working, just had to time rebooting it and plugging it in and holding vol- and power correctly, took me 30 or so tries, fml
Click to expand...
Click to collapse
Directly from OpenKirin's install guide:
"TWRP and other custom recoveries are not supported! Please ensure you have your device’s stock recovery installed. If you install the ROM with a custom recovery, we cannot assist you with any issues which may arise."
olswede said:
Directly from OpenKirin's install guide:
"TWRP and other custom recoveries are not supported! Please ensure you have your device’s stock recovery installed. If you install the ROM with a custom recovery, we cannot assist you with any issues which may arise."
Click to expand...
Click to collapse
Yeah....I skipped over the sentence saying "please ensure you have your device's stock recovery installed" and thought installing it via fastboot without using TWRP it would be fine. It was not. IMO they should make the warning more dire.
All fixed and working now, thanks for your input.
How did you get it fixed?

Unable to boot into TWRP recovery (twrp-3.2.3-1 dumpling/OOS 9.0.3 Pie)

Hey Guys,
somehow, I seem to be too dumb to install TWRP to my new dumpling. I did the following:
- run the official updates (9.0.3 Pie)
- unlock the bootloader using adb
- successfully flash the latest TWRP recovery (twrp-3.2.3-1 dumpling from their HP)
So far, no problems at all. Then I booted directly into recovery, so it won't be overwritten again: I tried unplug + Power/Volume Down, command "fastboot reboot recovery" and selecting recovery from the menu. But everytime I end up with the beautiful stock recovery, I never even saw the TWRP interface.
Any suggestions ? Any help would be much appreciated!!
My only idea: The latest TWRP is from 08/2018, maybe its not compatible to Pie ?!
_Kingo said:
Hey Guys,
somehow, I seem to be too dumb to install TWRP to my new dumpling. I did the following:
- run the official updates (9.0.3 Pie)
- unlock the bootloader using adb
- successfully flash the latest TWRP recovery (twrp-3.2.3-1 dumpling from their HP)
So far, no problems at all. Then I booted directly into recovery, so it won't be overwritten again: I tried unplug + Power/Volume Down, command "fastboot reboot recovery" and selecting recovery from the menu. But everytime I end up with the beautiful stock recovery, I never even saw the TWRP interface.
Any suggestions ? Any help would be much appreciated!!
My only idea: The latest TWRP is from 08/2018, maybe its not compatible to Pie ?!
Click to expand...
Click to collapse
hi dude, to stay on TWRP you have to flash MAGISK, if not TWRP will always be overwritten by the StockRecovery!!
flash TWRP
reboot into TWRP
flash Magisk within TWRP
reboot system
happy flashing!
nicorvienne said:
hi dude, to stay on TWRP you have to flash MAGISK, if not TWRP will always be overwritten by the StockRecovery!!
flash TWRP
reboot into TWRP
flash Magisk within TWRP
reboot system
happy flashing!
Click to expand...
Click to collapse
Hi, thanks, but I think you did not understand my problem: I can't reboot into TWRP. Instead I end up in stock, no matter what I do...
_Kingo said:
Hi, thanks, but I think you did not understand my problem: I can't reboot into TWRP. Instead I end up in stock, no matter what I do...
Click to expand...
Click to collapse
hi dude, sorry - now i got you
# after flashed TWRP unplug your device and reboot directly into the bootloader-mode (‘Volume Up’ + ‘Power’ button altogether) and navigate to 'Recovery' or
# fastboot boot 'recovery.img'
i recommend flashing twrp-3.2.3-x_blu_spark_v9.91_treble-op5_op5t.img : https://github.com/engstk/android_device_oneplus_cheeseburger/releases
SOLVED
I tried the 9.x recovery from this thread:
https://forum.xda-developers.com/oneplus-5t/development/recovery-twrp-3-2-1-0-oreo-8-0-8-1-t3729673
works like a charm!
I thougth, the official TWRP site would be the best source, but well... lesson learnt. Anyway, thanks for trying to help, nicorvienne
_Kingo said:
Hey Guys,
somehow, I seem to be too dumb to install TWRP to my new dumpling. I did the following:
- run the official updates (9.0.3 Pie)
- unlock the bootloader using adb
- successfully flash the latest TWRP recovery (twrp-3.2.3-1 dumpling from their HP)
So far, no problems at all. Then I booted directly into recovery, so it won't be overwritten again: I tried unplug + Power/Volume Down, command "fastboot reboot recovery" and selecting recovery from the menu. But everytime I end up with the beautiful stock recovery, I never even saw the TWRP interface.
Any suggestions ? Any help would be much appreciated!!
My only idea: The latest TWRP is from 08/2018, maybe its not compatible to Pie ?!
Click to expand...
Click to collapse
try this.
https://forum.xda-developers.com/oneplus-5t/development/root-install-twrp-xposed-framework-t3910141
Newbie needs help twrp
I am having the same problem and I have tried everything I unlock bootloader and flash TWRP successfully except I can never get into TWRP I try the key combo I tried to use the fastboot command all it does is it brings me back to fastboot mode how can I get to twrp with my new OnePlus 5T
[email protected] said:
I am having the same problem and I have tried everything I unlock bootloader and flash TWRP successfully except I can never get into TWRP I try the key combo I tried to use the fastboot command all it does is it brings me back to fastboot mode how can I get to twrp with my new OnePlus 5T
Click to expand...
Click to collapse
try to flash an older version of twrp through "ADB minimal fast boot".
I use Twrp and am not using Magisk or rooted.

Categories

Resources