I am sorry if this topic is discussed somewhere already... I could not find it..
My Oneplus 3t is rooted and running RR ROM.
I am trying to install latest RR custom ROM (2/11/17).
But before it is required firmware to be updated to 4.0.3.
I am trying to use adb sideload for that... but getting "Zip signature verification failed!" message.
Not sure what I am doing wrong..
Steps:
1. Go to TWRP > Advanced > ADB Sideload
2. In Windows: adb sideload OnePlus3T_4.0.3_firmware.zip
3. It is processing but then I am getting "Zip signature verification failed!".
Thanks.
In TWRP, go to Settings and turn off signature verification. Also, you don't have to use adb sideload in TWRP. You can just flash it like any other zip.
Sent from my OnePlus 3T using XDA Labs
dustin_b said:
In TWRP, go to Settings and turn off signature verification. Also, you don't have to use adb sideload in TWRP. You can just flash it like any other zip.
Click to expand...
Click to collapse
After this twrp and root is still there?
realkeule said:
After this twrp and root is still there?
Click to expand...
Click to collapse
TWRP should still be there. As for root, I don't know. I'm assuming your just flashing the firmware zip and not the actual OTA. It depends on if it includes the boot.img or not.
Sent from my OnePlus 3T using XDA Labs
dustin_b said:
In TWRP, go to Settings and turn off signature verification. Also, you don't have to use adb sideload in TWRP. You can just flash it like any other zip.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thank you. I worked fine.
Root is still there.
On RR, the root is built-in, so flashing OnePlus 3T firmware will not affect it.
On the latest versions of Resurrection Remix, the instructions say to first flash the newest firmware (link below) and then the RR ROM.
https://www.androidfilehost.com/?fid=529152257862702435
Related
Hello i need help. I was on OOS 4.0. Like to update to 4.0.1 with clean System. So i boot to TWRP and make fullwipe(format:data/system/cache-dalvik cache)
After flash the 4.0.1 twrp says no os install. Ihave test another rom from this side https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015 but no way.
After that i flash stock recovery (fastboot) and stock rom via adb sideload but after 46% the installation failed (3 times).
Sorry for bad english and thanks for all
I read somewhere that TWRP is not compatible with the OSS 4.0 or higher and that's why you get errors when trying to install them. So, to make it work you gotta install the newest and beta version of TWRP...
Here you go, as I already said, it's a beta version, I'm not 100% sure if it'll work...
https://build.nethunter.com/test-builds/twrp/oneplus/twrp-3.0.3-1-beta1-oneplus3t.img
enzzo28 said:
I read somewhere that TWRP is not compatible with the OSS 4.0 or higher and that's why you get errors when trying to install them. So, to make it work you gotta install the newest and beta version of TWRP...
Here you go, as I already said, it's a beta version, I'm not 100% sure if it'll work...
https://build.nethunter.com/test-builds/twrp/oneplus/twrp-3.0.3-1-beta1-oneplus3t.img
Click to expand...
Click to collapse
I installed OSS 4.0 without issues on TWRP 3.0.3.
It sounds more like a bad download to me. Try to redownload the file and flash it again.
RL77LUC said:
I installed OSS 4.0 without issues on TWRP 3.0.3.
It sounds more like a bad download to me. Try to redownload the file and flash it again.
Click to expand...
Click to collapse
Could you install it?
There's a way to flash the 36MB OTA file in TWRP without downloading the full 4.0.1 zip.
I think the OTA fails and gets stuck because of SuperSU or Magisk modifies the boot.img
So, you could try this:
1. Dirty flash the full 4.0 zip
2. Flash 4.0.1
3. Flash SuperSU/Magisk
Sent from my OnePlus 3T using XDA Labs
enzzo28 said:
Could you install it?
There's a way to flash the 36MB OTA file in TWRP without downloading the full 4.0.1 zip.
I think the OTA fails and gets stuck because of SuperSU or Magisk modifies the boot.img
So, you could try this:
1. Dirty flash the full 4.0 zip
2. Flash 4.0.1
3. Flash SuperSU/Magisk
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
TWRP can't install partial OTA updates.
It can install full 4.0 ZIP, but AFAIK, it can't install partial updates.
RL77LUC said:
TWRP can't install partial OTA updates.
It can install full 4.0 ZIP, but AFAIK, it can't install partial updates.
Click to expand...
Click to collapse
Have you tried reading solutions about the last OTA on other XDA's posts?
I've been reading just to spend time and they have found a lot of solutions to some errors with TWRP
Sent from my OnePlus 3T using XDA Labs
enzzo28 said:
Have you tried reading solutions about the last OTA on other XDA's posts?
I've been reading just to spend time and they have found a lot of solutions to some errors with TWRP
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Not really, as I moved to LineageOS.
I just wanted to say that 4.0 worked fine for me , so his error shouldn't be because of that.
RL77LUC said:
Not really, as I moved to LineageOS.
I just wanted to say that 4.0 worked fine for me , so his error shouldn't be because of that.
Click to expand...
Click to collapse
Alright man, it's great that you've found a way to install another rom ✌?
Sent from my OnePlus 3T using XDA Labs
Hey
So my op3t is back in live.
OS is 3.5.4 bootloader unlock.
Twrp is installed but not working (is the beta for 4.0.1)...
First I will working Twrp for nano backup.
Then root on the last official os
What the best way for me I don't will brick my device second time
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Hi folks,
I'm considering taking my OP3T from 4.1.6 to the just released 4.1.7, more to get rid of the nag notification than anything else. But I want to double check the process since this will be my first update since I got the phone.
I have TWRP and Magisk root.
Would the process be to download the entire full package, not just the OTA, flash it from TWRP, then reflash TWRP and Magisk before booting? Or would I need to flash via fastboot based on what is available?
I will make a TWRP backup of the whole thing and copy it to PC before starting anything, but would rather not klutz around.
Is there an update guide that spells it out for the case of being rooted and TWRP enabled?
Thanks
Sent from my ONEPLUS A3000 using Tapatalk
OTA will be enough, just copy the ota zip to the phone and then flash it via TWRP, reflash Magisk and boot the system. No need for full package or TWRP reflash.
przemcio510 said:
OTA will be enough, just copy the ota zip to the phone and then flash it via TWRP, reflash Magisk and boot the system. No need for full package or TWRP reflash.
Click to expand...
Click to collapse
Ok thanks! I hear wiping cache is also good plan while I'm in TWRP. Thank you!
Sent from my ONEPLUS A3000 using Tapatalk
Frankenscript said:
Ok thanks! I hear wiping cache is also good plan while I'm in TWRP. Thank you!
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Yes, forgot to mention about it
I think you should download the complete OS zip. Have a look at the thread below in OnePlus forum.
[Guide] How to update rooted stock rom to 4.1.7 without loosing root? https://forums.oneplus.net/threads/...ock-rom-to-4-1-7-without-loosing-root.610565/
przemcio510 said:
OTA will be enough, just copy the ota zip to the phone and then flash it via TWRP, reflash Magisk and boot the system. No need for full package or TWRP reflash.
Click to expand...
Click to collapse
Nope,
You are wrong.
For rooted systems, you need to flash the whole 1.4gb Rom.
Also, for the OP, no need to reflash TWRP. It won't be affected by the flashing of the rom.
Unleashed by ONEPLUS 3T rooted
RASTAVIPER said:
Nope,
You are wrong.
For rooted systems, you need to flash the whole 1.4gb Rom.
Also, for the OP, no need to reflash TWRP. It won't be affected by the flashing of the rom.
Unleashed by ONEPLUS 3T rooted
Click to expand...
Click to collapse
So, flash the whole ROM (which apparently doesn't include recovery since that's a separate download) in TWRP, then Magisk, then clear cache/dalvik?
Sent from my ONEPLUS A3000 using Tapatalk
RASTAVIPER said:
For rooted systems, you need to flash the whole 1.4gb Rom
Click to expand...
Click to collapse
Oh, didn't notice the downloads from oneplus.net are 1,4GB in size
Frankenscript said:
So, flash the whole ROM (which apparently doesn't include recovery since that's a separate download) in TWRP, then Magisk, then clear cache/dalvik?
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Exactly!
This is how I did it too.
Unleashed by ONEPLUS 3T rooted
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery nd super su root but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
mannulko said:
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery nd super su root but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
Click to expand...
Click to collapse
For starters, posting the same question in four different threads is something you shouldn't do. You could have just used the Q&A thread too ask for help.
To fix your phone, reflash the full 5.0.2 zip, if you have it. Otherwise, flash the full 5.0.1 zip, reboot your phone (you'll lose TWRP, but that's ok), then flash the 5.0.2 OTA. That should bring your phone back to normal 5.0.2.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
For starters, posting the same question in four different threads is something you shouldn't do. You could have just used the Q&A thread too ask for help.
To fix your phone, reflash the full 5.0.2 zip, if you have it. Otherwise, flash the full 5.0.1 zip, reboot your phone (you'll lose TWRP, but that's ok), then flash the 5.0.2 OTA. That should bring your phone back to normal 5.0.2.
Click to expand...
Click to collapse
Thanks bro my phone is now working I followed your steps.thanks
Now I want to install root pls guide me ND give me links to compatible twrp recovery ND root files
mannulko said:
Thanks bro my phone is now working I followed your steps.thanks
Now I want to install root pls guide me ND give me links to compatible twrp recovery ND root files
Click to expand...
Click to collapse
TWRP: Try using the latest official TWRP (unified for 3 and 3T) from https://dl.twrp.me/oneplus3/
Or the Blu Spark v8.61 TWRP from https://forum.xda-developers.com/on...vice-development/kernel-t3404970/post67463496
For root, use the latest Magisk (you can find it for yourself).
Sent from my OnePlus3T using XDA Labs
BillGoss said:
TWRP: Try using the latest official TWRP (unified for 3 and 3T) from https://dl.twrp.me/oneplus3/
Or the Blu Spark v8.61 TWRP from https://forum.xda-developers.com/on...vice-development/kernel-t3404970/post67463496
For root, use the latest Magisk (you can find it for yourself).
Click to expand...
Click to collapse
Thanks
I want to know which version of magisk is compatible with op3t 5.0.2
mannulko said:
Thanks
I want to know which version of magisk is compatible with op3t 5.0.2
Click to expand...
Click to collapse
The latest
Sent from my OnePlus3T using XDA Labs
BillGoss said:
The latest
Click to expand...
Click to collapse
I am going to use twrp-3.2.1-0-oneplus3.img ns magisk 16.0.zip
Pls confirm if it's ok for OnePlus 3T
mannulko said:
I am going to use twrp-3.2.1-0-oneplus3.img ns magisk 16.0.zip
Pls confirm if it's ok for OnePlus 3T
Click to expand...
Click to collapse
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Click to expand...
Click to collapse
One more thing after installing twrp recovery should I take back up on twrp ND then flash magisk?
mannulko said:
One more thing after installing twrp recovery should I take back up on twrp ND then flash magisk?
Click to expand...
Click to collapse
Yes, always make backups
mannulko said:
One more thing after installing twrp recovery should I take back up on twrp ND then flash magisk?
Click to expand...
Click to collapse
You should always make a TWRP backup before flashing any mods (root, custom ROM, etc.). This is a good basic rule of thumb for any Android device.
The fact that you started this thread trying root, failed, and had no backup to restore, should have made the answer to this question obvious. Always try to learn from your experiences!
Hey, all!
Had a notification this morning for the new Magisk Manager (6.1) and Magisk (18.0) release. I downloaded both and rebooted the phone (OnePlus 2), updating from 17.3 to 18.0 directly, which had no errors during the install. Now upon startup it hangs on the splash screen. I can get into recovery (TWRP) and I have tried to flash the latest Magisk Uninstaller but I'm greeted with an ERROR 1: Error Installing zip file '/sdcard/...' - Unable to unpack boot.img
Any help here? Thanks in advance!
SpikyAndroid3 said:
Hey, all!
Had a notification this morning for the new Magisk Manager (6.1) and Magisk (18.0) release. I downloaded both and rebooted the phone (OnePlus 2), updating from 17.3 to 18.0 directly, which had no errors during the install. Now upon startup it hangs on the splash screen. I can get into recovery (TWRP) and I have tried to flash the latest Magisk Uninstaller but I'm greeted with an ERROR 1: Error Installing zip file '/sdcard/...' - Unable to unpack boot.img
Any help here? Thanks in advance!
Click to expand...
Click to collapse
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk
DarkSJ1998 said:
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
Thanks for the response, just about to do a dirty flash of the stock ROM. My memory doesn't serve me well, is it best to wipe Cache as well as Dalvik Cache, or just Dalvik Cache?
The recovery also stays as is, right?
Hello,
The same for me from 17.3 to 18.
I'm on Nexus 6 with stock ROM.
SpikyAndroid3 said:
Thanks for the response, just about to do a dirty flash of the stock ROM. My memory doesn't serve me well, is it best to wipe Cache as well as Dalvik Cache, or just Dalvik Cache?
The recovery also stays as is, right?
Click to expand...
Click to collapse
Yep the recovery should stay as it is. I would recommend wiping both Dalvik Cache & Cache. Also, do keep fastboot handy. TWRP survival really depends on the device. For my device (OnePlus 3T), the OOS overrides TWRP if no root solution is used or patched boot.img isn't used.
Sent from my #FlagshipKiller3T using Tapatalk
---------- Post added at 01:08 AM ---------- Previous post was at 12:55 AM ----------
StreamingMT said:
Hello,
The same for me from 17.3 to 18.
I'm on Nexus 6 with stock ROM.
Click to expand...
Click to collapse
Weird :/
Did you check the Magisk release thread for people facing similar issues? I'm still on v17.3.
I'm really reluctant to move to v18.0 after reading such things... Moreover, I always wait for feedbacks before trying out things that play with the boot.img's & stuff, because I already got /data partition of my last device corrupted [emoji52]
Sent from my #FlagshipKiller3T using Tapatalk
DarkSJ1998 said:
Yep the recovery should stay as it is. I would recommend wiping both Dalvik Cache & Cache. Also, do keep fastboot handy. TWRP survival really depends on the device. For my device (OnePlus 3T), the OOS overrides TWRP if no root solution is used or patched boot.img isn't used.
Click to expand...
Click to collapse
Alrighty! Just went ahead and did the flash and it successfully reboots! Tried to reboot into recovery to flash Magisk 17.3 and lo and behold TWRP is still there
Guess I'll wait until there has been an update or patch of some sorts if @StreamingMT is also getting this issue, maybe there are others too. Thanks for the help @DarkSJ1998
I will try to remember that @DarkSJ1998.
I was excited to have a new update, just got reckless...
Anyways, I replied to the official thread about the details, just search through it. I just restored my phone to the way it used to...
All my saves... Gone to trash.
SpikyAndroid3 said:
Hey, all!
Had a notification this morning for the new Magisk Manager (6.1) and Magisk (18.0) release. I downloaded both and rebooted the phone (OnePlus 2), updating from 17.3 to 18.0 directly, which had no errors during the install. Now upon startup it hangs on the splash screen. I can get into recovery (TWRP) and I have tried to flash the latest Magisk Uninstaller but I'm greeted with an ERROR 1: Error Installing zip file '/sdcard/...' - Unable to unpack boot.img
Any help here? Thanks in advance!
Click to expand...
Click to collapse
I had the same bootloop issue when I was reinstalling H2OS beta 21 in my OnePlus 5 today. I got it to boot again with Magisk 18.0 after:
1. Dirty flashing ROM. Now this is important Did not flash Magisk (yet).
2. Rebooting to Bootloader (fastboot) in TWRP (since no root, now stock recovery will reinstall).
3. Fastboot flashed TWRP. Booted to Recovery mode from Fastboot menu.
4. Flashed Magisk 18.0 in TWRP. Now this is important Only flashed Magisk, nothing else.
5. Rebooted to Recovery again instead of System to flash other stuff.
6. Rebooted system.
If course YMMV. The important thing was to not try to flash Magisk while flashing ROM.
Same here on a mi max 2, updated manager and magisk directly from app, now stuck in bootloop. im downloading my rom as im typing to restore stock boot image. will flash v17.1 instead.
I have 1 plus 5 with official H2OS and Magisk 17.1.
Today when after installed Magick 18 and reboot, it stuck at startup.
I try to flash TWRP using adb, but it give me error:
E:\Program Files\Android\platform-tools>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
E:\Program Files\Android\platform-tools>adb kill-server
E:\Program Files\Android\platform-tools>
Click to expand...
Click to collapse
I too am having with latest magisk 18.0 my device is redimi 4x, on trying to update via magisk manager crashes with an error report, installed update using twrp now i get a error popup at start and magisk manger still shows am on 17.1 and tells to update, which crashes the app on trying
tmicrd68 said:
I had the same bootloop issue when I was reinstalling H2OS beta 21 in my OnePlus 5 today. I got it to boot again with Magisk 18.0 after:
1. Dirty flashing ROM. Now this is important Did not flash Magisk (yet).
2. Rebooting to Bootloader (fastboot) in TWRP (since no root, now stock recovery will reinstall).
3. Fastboot flashed TWRP. Booted to Recovery mode from Fastboot menu.
4. Flashed Magisk 18.0 in TWRP. Now this is important Only flashed Magisk, nothing else.
5. Rebooted to Recovery again instead of System to flash other stuff.
6. Rebooted system.
If course YMMV. The important thing was to not try to flash Magisk while flashing ROM.
Click to expand...
Click to collapse
Using Xiaomi Mi Max
Using your method and it work just took afew for it to boot back up :good:
netsonic said:
I have 1 plus 5 with official H2OS and Magisk 17.1.
Today when after installed Magick 18 and reboot, it stuck at startup.
I try to flash TWRP using adb, but it give me error:
Code:
E:\Program Files\Android\platform-tools>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
E:\Program Files\Android\platform-tools>adb kill-server
Click to expand...
Click to collapse
Try 'Revoking USB Debugging' and restart the adb server. Then reinstate its authorization by plugging it back in with USB Debugging enabled. And just to check, make sure you run cmd as administrator, and ensure MTP is on.
huzeifa88 said:
I too am having with latest magisk 18.0 my device is redimi 4x, on trying to update via magisk manager crashes with an error report, installed update using twrp now i get a error popup at start and magisk manger still shows am on 17.1 and tells to update, which crashes the app on trying
Click to expand...
Click to collapse
Try flashing the uninstaller which you can get here. Then reinstall/reflash Magisk with a previous version that worked for you.
DarkSJ1998 said:
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?
otraver said:
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?
Click to expand...
Click to collapse
I guess it's possible, but I'm not sure about that.... You can backup/restore boot.img from TWRP but I don't know if you can do this also... Do check it on the Internet.
Sent from my #FlagshipKiller3T using Tapatalk
DarkSJ1998 said:
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
DarkSJ1998 said:
I guess it's possible, but I'm not sure about that.... You can backup/restore boot.img from TWRP but I don't know if you can do this also... Do check it on the Internet.
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
Don't work.
The cellular boot but stops in the Miui Screen with the unlocked symbol
I tried a dirty install of the rom but don't work
I need to install a clean global stock rom to boot correctly.
otraver said:
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?
Click to expand...
Click to collapse
Actually, Magisk does a backup of stock boot.img before patching it, which lies stored in /data as ".img.gz.zip". Haven't looked for how to restore it yet; however, assuming it's a flashable zip, it can be restored via TWRP. Should check Magisk release OP to be sure...
Sent from my Moto Z2 Play using XDA Labs
The Analog Kid said:
Actually, Magisk does a backup of stock boot.img before patching it, which lies stored in /data as ".img.gz.zip". Haven't looked for how to restore it yet; however, assuming it's a flashable zip, it can be restored via TWRP. Should check Magisk release OP to be sure...
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
Doesn't look like a flashable zip too me. It stores a *.img file in it, which I think is flashable as an image from TWRP. But, I'm not 100% sure about it.
Great discovery though dude there
Sent from my #FlagshipKiller3T using Tapatalk
otraver said:
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?
Click to expand...
Click to collapse
Hello, I do this with my Nexus 6, it's OK. Flash again Magisk (v17 not 18 for me) and all is OK for me.
Boot loop for me too after upgrading from v17 to v18 . I'm on Nexus 6. Any official information about this bug?
Fixed by installing TWRP then restored backup through TWRP and selected only boot image. I guess TWRP or me saved backup at some point, don't remember exactly. Will have to use v17 for now.
Hi everyone,
I need a link for th OP3T stock recovery. All old threads point to OnePlus website which does not provide the stock recovery anymore.
Currently on TWRP and want to return the phone to full stock.
TIA
weapons777 said:
Hi everyone,
I need a link for th OP3T stock recovery. All old threads point to OnePlus website which does not provide the stock recovery anymore.
Currently on TWRP and want to return the phone to full stock.
TIA
Click to expand...
Click to collapse
If you install OOS and nothing else and reboot your phone, it will automatically install stock recovery and encrypt your phone (of its not encrypted).
So, you don't need to manually install stock recovery.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
If you install OOS and nothing else and reboot your phone, it will automatically install stock recovery and encrypt your phone (of its not encrypted).
So, you don't need to manually install stock recovery.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Hi, thank you very much for your reply.
I have installed the latest OOS 9.0.5 downloaded from OnePlus support site. Everything is working fine but TWRP remains installed as the default recovery. I want to go completely back to stock and get rid of the DM-VERITY messages at boot.
weapons777 said:
Hi, thank you very much for your reply.
I have installed the latest OOS 9.0.5 downloaded from OnePlus support site. Everything is working fine but TWRP remains installed as the default recovery. I want to go completely back to stock and get rid of the DM-VERITY messages at boot.
Click to expand...
Click to collapse
You're not using Magisk or a custom kernel or a patched boot image are you? Because any of those will prevent the stock recovery from being installed.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
You're not using Magisk or a custom kernel or a patched boot image are you? Because any of those will prevent the stock recovery from being installed.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I wiped and formatted everything from TWRP and then installed the OOS zip. Phone is back to stock except for the recovery.
weapons777 said:
I wiped and formatted everything from TWRP and then installed the OOS zip. Phone is back to stock except for the recovery.
Click to expand...
Click to collapse
Very weird.
Here's a copy of the recovery https://www.dropbox.com/s/kvdtwt8gdxiu24s/recovery_op3t.img
Md5: bd21e3036f11584e94a68f7d85977653
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Very weird.
Here's a copy of the recovery https://www.dropbox.com/s/kvdtwt8gdxiu24s/recovery_op3t.img
Md5: bd21e3036f11584e94a68f7d85977653
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Great! Thank you very much. I am finally back to stock recovery with the file you provided.
Cheers! :good: