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
Hello,
I'm sorry if this is a retype of a thread but i didn't found one. I've searched far and wide with no success.
Before i dig into the unbricking thread and reinstalling everything i just wanted to ask if this happend to anyone and if there is a simple solution for it.
I have zenfone 2 551ml with ressurection remix Remix nougat 7.1.2_r2
The phone is still working but i have no recovery. One day (dont ask me why) i wanted to update twrp just by flashing another twrp image in the twrp recovery. It didnt get updated but after i rebooted the phone, the next time there was no more recovery. I tried to flash it via fastboot with fastboot flash recovery command but still nothing. The device is detected both in adb and in fastboot.
Any ideas?
Thank you
I solved it
The thing is that i had to flash the stock recovery. Than i could sideload stock rom and now i continue.
Hi,
After booting to twrp. It asks for a password.i am not sure what to do about it. Can anyone help?
Same problem bro. I have posted the same question but i saw yours late. Hope the mods forgive me for posting a duplicate question. Btw, try the things i have done in my post (see my profile). And also, is your method of recreating the problem different than mine? (Check my latest post)
If you searched and read some threads you would see that MIUI Pie update is not compatible with latest TWRP. You have to use orangefox or custom TWRP.
https://androidfilehost.com/?fid=6006931924117884758
Solved it- https://forum.xda-developers.com/redmi-note-5-pro/help/boot-twrp-official-pie-update-t3937270
I have another problem. My bootloader is unlocked (no root).
After PIE update, when I try to boot twrp with fastboot method and "fastboot boot twrp.img" in CMD everything is ok, but phone doesn't boot in TWRP, just stuck on MI logo.... I've tried with 5 different TWRP images, even for Pie miui, but without success...
Just touch "cancel" when TWRP asks for a password, then install Magisk, nothing hard, nothing unsupported, just a simple button.
Your rom now pie, then you should install recovery pie too.. Orangefox 9.02
Hey all,
i had an older version of twrp recovery, and tried to flash the new one from here:
https://eu.dl.twrp.me/dumpling/
i opened poweshell from adb folder as usual while device is on fastboot mode, and used the command: fastboot flash recovery twrp-3.3.1-0-dumpling.img
It said "wrting...finished" in powshelll, but when entered recovery - nada, black screen of death.
then i tried flashing older version of twrp in the same way - and still go the same outcome =\
I currenly dont have ROM as well - so practically the phone is uselss. please guys, i need you're help!
Flash stock recovery and stock FW via ADB. If that doesn't work, try one of the dozen recovery tools on this forum.
Tried to flash OrangeFox and BluSpark recoveries, same issue =\
im running out of ideas here guys =(
Just managed to install stock recovery, and downloaded latest 9.0.10 OTA from here:
https://forum.xda-developers.com/oneplus-5t/how-to/official-oxygenos-4-7-2-7-1-1-ota-t3709265
used LAA on adb.exe, and ran "adb sideload OOS.zip" while OTA zip is inside adb folder.
gives me "cannot read" error in powershell.
can someone tell me WTF is going on? how tf its even possible????
I've unlocked my Bootloader and all via beta-test program from DCUnlocker. I wanted to install TWRP & Magisk and I have following every step available from sir Supersonic's guide, but whenever I opened recovery, it always shows stock recovery (eRecovery) even though my CMD states that the flash recovery was succesfull and I never let my phone boot up in order not to replace the TWRP just like any android devices normal recovery procedures.
https://imgur.com/rOdXWSR
can someone find a solution of this problem?