Hello people,
I have an OnePlus 3T, which does not start the OS. I can open Fastboot Mode or TWRP. I do not even know which OS is installed (I think stock rom, but do not know). When I boot into Fastboot, I get the dm-verity notification "Phone is unlocked and cannot be trusted". When I boot into system, it stops at the black "Powered by android" Screen (very first screen).
When I connect my phone to the PC and open the internal storage, it shows only the "TWRP" folder.
So what Information do I have so far (with my amateur knowledge):
adb shell getprop ...
ro.build.version.release: 6.0.1
ro.build.version.sdk: 23
ro.build.display.id: omni_oneplus3-eng 6.0.1 MOB31K eng.jc.20170208.012427 test-keys
ro.modversion: OmniROM-6.0.1-20170208-oneplus3-HOMEMADE
ro.twrp.version: 3.0.4-1
When I start the bootloader:
Product_Name - msm8996
Variant - MTP UFS
Bootloader Version -
Baseband Version -
Serial Number - *****
Secure Boot - enabled
Device State - unlocked
I tried to reflash the original recovery => device did not start in recovery anymore => reflashed twrp
I tried to flash the stock ROM => did not work (with this Error 7)
So my first question: Which OS do I have? Really Marshmallow 6.0.1?
Second: Do you need more infos?
Third and most important: How to repair this mess?
What do I want: A stable, rooted ROM. It can be the stock ROM, but also a custom, I do not care right now.
I read that this unlocked-notification appears because I have the wrong kernel? Is that true? Which one do I need?
Thank you very much for your help.
Use ADB Sideload to Sideload a ROM onto the phone since you have TWRP working. It's not a huge problem, and it's easily solvable.
*OR* you can use the Unbrick tool to solve your problem.
thes3usa said:
Use ADB Sideload to Sideload a ROM onto the phone since you have TWRP working. It's not a huge problem, and it's easily solvable.
*OR* you can use the Unbrick tool to solve your problem.
Click to expand...
Click to collapse
Thank you for your reply.
Okay so it is not important which system I run right now? And what about this kernel thing?
I can just flash it with sideload (e.g. https://forum.xda-developers.com/on...pment/rom-kernel-resurrectionremix-n-t3524715) and finished? Rooted and particularly working?
Sorry for the questions but I am a little nervous
elchico92 said:
Thank you for your reply.
Okay so it is not important which system I run right now? And what about this kernel thing?
I can just flash it with sideload (e.g. https://forum.xda-developers.com/on...pment/rom-kernel-resurrectionremix-n-t3524715) and finished? Rooted and particularly working?
Sorry for the questions but I am a little nervous
Click to expand...
Click to collapse
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
thes3usa said:
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
Click to expand...
Click to collapse
So first this one (downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_21/), then this (androidfilehost.com/?w=files&flid=131965 - latest)?
Thanks again!
PS: Sorry I cannot post links yet.
elchico92 said:
So first this one (downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_21/), then this (androidfilehost.com/?w=files&flid=131965 - latest)?
Thanks again!
PS: Sorry I cannot post links yet.
Click to expand...
Click to collapse
Nope, that's the complete stock Zip. Unless you want to install OOS, that's not the one to Sideload.
Download the FW only from here: https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166
And then Sideload it, reboot back to recovery, and then Sideload the ROM.
elchico92 said:
When I connect my phone to the PC and open the internal storage, it shows only the "TWRP" folder.
Click to expand...
Click to collapse
What is in the TWRP folder, anything? The TWRP folder would normally only be created, if a backup was created. You can possibly just boot TWRP, select the RESTORE option, select the backup from the TWRP folder, and get the phone up and running again.
Another possibility, if you aren't that up on adb commands (sideload, etc.), since you can access the internal storage, just download a ROM or fill stock ROM zip onto your PC, then just drag/copy to internal storage. Then boot TWRP, select INSTALL, pick the file, and flash it.
What is the background of the device, how do you not know the OS version? Did you receive it this way, or fixing it for a friend or something?
---------- Post added at 09:19 AM ---------- Previous post was at 09:12 AM ----------
elchico92 said:
When I boot into Fastboot, I get the dm-verity notification "Phone is unlocked and cannot be trusted".
I read that this unlocked-notification appears because I have the wrong kernel? Is that true? Which one do I need?
Click to expand...
Click to collapse
That isn't the dm-verity notification. The dm-verity notification screen is similar, but says "dm-verity is not started in enforcing mode".
What you described is the bootloader unlocked warning screen. The bootloader unlocked warning screen is expected and normal (in fact, unavoidable) if the bootloader is unlocked. And unlocked bootloader is required for TWRP, flashing custom ROMs, etc.
dm-verity warning screen is in fact normal, as well, if you have TWRP installed. That one can be disabled by a couple different methods. But it's only purpose is to notify a "average" user that the system has been modified. For XDA users that are intentionally modifying their phones (TWRP, root, etc.) the warning is pretty meaningless. Under certain conditions, dm-verity will prevent the phone from booting. But TWRP and root in themselves, will normally not do that.
Neither warning means you have the wrong kernel, necessarily. And unless you (or someone else) tried to flash a kernel, there really isn't any reason to believe that.
---------- Post added at 09:29 AM ---------- Previous post was at 09:19 AM ----------
elchico92 said:
I tried to reflash the original recovery => device did not start in recovery anymore => reflashed twrp
Click to expand...
Click to collapse
Flashing stock recovery will (by definition) replace TWRP with stock recovery. You probably have recovery, just the stock one (not TWRP) which is fairly useless in your case (can't flash custom ROMs, root, etc.).
elchico92 said:
I tried to flash the stock ROM => did not work (with this Error 7)
Click to expand...
Click to collapse
Can't really troubleshoot this, unless you tell us what file exactly (file name) and where you got it from. "Stock ROM" is far too vague, and can literally mean a dozen or more different things.
Also, what version TWRP?
Using a TWRP version which does not support Oreo is one reason for Error 7. Or you may have tried a file intended for the 3, not the 3T. So these details need to be provided, before we can figure out what went wrong.
elchico92 said:
What do I want: A stable, rooted ROM. It can be the stock ROM, but also a custom, I do not care right now.
Click to expand...
Click to collapse
You kind of need to decide which of those you want. Otherwise, there are just too many options for us to give.
Yet another option (in addition to those given) would be to flash the full stock OOS zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Then before rebooting, flash Magisk to root, and you should be all set. The full zip will put you on a fully stock baseline (including firmware). Which, if you aren't sure if you want stock, beta or custom ROM, is not a bad place to be; you can see what the "stock" condition is, before messing with things like custom ROMs. But again, it's totally subjective and a matter of personal preference, and you really do need to decide for yourself what is best for you (as an individual) at this time.
thes3usa said:
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
Click to expand...
Click to collapse
Why not just sideload stock ROM which includes the firmware? Make life easier
przemcio510 said:
Why not just sideload stock ROM which includes the firmware? Make life easier
Click to expand...
Click to collapse
Yeah, that is a good option, among many. As I mentioned, there are just too many options since the original poster hasn't even decided stock or custom ROM.
przemcio510 said:
Why not just sideload stock ROM which includes the firmware? Make life easier
Click to expand...
Click to collapse
Since OP hasn't mentioned whether he wants to use a stock or custom ROM. So I gave him the link for the latest FW, in case he wants to use a recently updated custom ROM without needing to download the whole Stock zip.
Done!
Thanks a lot. The phone is working again.
I have flashed with adb sideload the firmware and the ResurrectionRemix-Rom (Nougat) and then via TWRP the gapps.
So I hope, everthing will be fine now.
answers:
- TWRP-folder: yeah I created one because I thought, maybe to restore will fix anything
- I tried to flash with TWRP a ROM, but it says "Error 7", which means: wrong ROM => but I am sure, it was the right one
- background: it was the phone of a friend of mine => he never heard anything about ROMs etc
The thread can be closed.
elchico92 said:
- I tried to flash with TWRP a ROM, but it says "Error 7", which means: wrong ROM => but I am sure, it was the right one
Click to expand...
Click to collapse
I already offered to troubleshoot this error for your, but you never supplied the requested info. Don't assume it is the "right one" next time, but rather, give exact file names, version numbers, and let us verify. Mistakes happen, and it always is good to have another set of eyes look at the specifics.
---------- Post added at 09:58 AM ---------- Previous post was at 09:56 AM ----------
elchico92 said:
The thread can be closed.
Click to expand...
Click to collapse
Threads on xda don't get closed, just because you solved your current issue. Others may have a similar problem, and may want to ask questions, etc.
I'm stuck in Fastboot Mode & TWRP without OS
I everyone,
Like the title say I'm totally stuck, I don't know what to do ....
I've got a OnePlus 3T few years ago, and the first thing i did at the installation was to encrypt the phone with an option of oxygen OS, and after that i unlock the oem and add root access.
But when oneplus release a major update, there was issues with phone encrypted and unlock, for that I never could make an update of the OS, so I did try to install the lastest lineage os recently, and add an "error 7".
After reading a lot of stuff and try a lot of manupilations, i'm now totally stuck with only access to the fastboot, twrp, and the recovery of oneplus.
If someone here could help me, you will be very gratefull because i can't afford to buy a new phone for the moment... thank's
slykereven said:
I everyone,
Like the title say I'm totally stuck, I don't know what to do ....
I've got a OnePlus 3T few years ago, and the first thing i did at the installation was to encrypt the phone with an option of oxygen OS, and after that i unlock the oem and add root access.
But when oneplus release a major update, there was issues with phone encrypted and unlock, for that I never could make an update of the OS, so I did try to install the lastest lineage os recently, and add an "error 7".
After reading a lot of stuff and try a lot of manupilations, i'm now totally stuck with only access to the fastboot, twrp, and the recovery of oneplus.
If someone here could help me, you will be very gratefull because i can't afford to buy a new phone for the moment... thank's
Click to expand...
Click to collapse
This should get you back to OOS:
In TWRP:
1. Do a factory reset
2. Flash OOS 9.0.6 full rom
3. Flash this modified firmware (to avoid the issue 9.0.6 with encrypted+unlocked) https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (see https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055)
4. Reboot
This should leave you with a clean install of OOS 9.0.6 and an encrypted phone with the stock recovery (TWRP gets replaced when you boot stock OOS).
From that point you can do what you want.
Sent from my OnePlus 3T using XDA Labs
Resolved
OK, that's a little crazy but it's working, i've got a one plus 3T A3003, but i had to install Stable9.0.3+Firmware+Modem_OnePlus3.zip and not the one for the 3T ..... then install the last lineage os 17, and everything seems to work for now !!!
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
BillGoss said:
This should get you back to OOS:
In TWRP:
1. Do a factory reset
2. Flash OOS 9.0.6 full rom
3. Flash this modified firmware (to avoid the issue 9.0.6 with encrypted+unlocked) https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (see https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055)
4. Reboot
This should leave you with a clean install of OOS 9.0.6 and an encrypted phone with the stock recovery (TWRP gets replaced when you boot stock OOS).
From that point you can do what you want.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Hi, thank's for your help, i didn't see your answer before and i have resolved the issue with other method
Related
Hi everybody,
I have a probleme with my OP3T.
I have upgraded the OS from 3.5.4 to 4, but I don't succed to root the phone, mainly because of the TWRP (flash with 3.0.3.0) that doesn't access to the SD card (twrp asks a password I don't have, so that stay encrypted).
When I try to follow this guide, I always have an error with the recovery stock (recovery downloaded from the oneplus support) during the sideload step (I also try to dowload the rom with twrp, but no success...)
So my question:
Does someone can help me to come back to 3.5.4 until twrp is supported by 4.0 ?
Thank you very much
I'm in the same boat. When sideloading 3.5.3 ota it fails after approximately 45%.
I had the same problem. Steps I did in order to make phone functional:
If you don't have TWRP, you have to install it.
Then, you should wipe your phone entirely from TWRP (Factory Reset, Format Data, Advanced Wipe->Dalvik/ART;System;Data;Internal Storage).
Reset the phone and enter TWRP once again.
Copy the official ZIP with OOS 3.5.x ROM into phone's memory, then flash it.
Flash SuperSU, otherwise your phone won't boot.
I don't take any responsibility, in case you mess something up with your phone.
Okay, my solution was to: 1. boot up in fastboot mode 2. Disable encryption by opening a command prompt in administrater mode and type fastboot format userdata. 3. Install 3.5.3 from Twrp.
Not ideal to disable encryption but now I got a working phone
---------- Post added at 04:59 PM ---------- Previous post was at 04:54 PM ----------
djseban2 said:
I had the same problem. Steps I did in order to make phone functional:
If you don't have TWRP, you have to install it.
Then, you should wipe your phone entirely from TWRP (Factory Reset, Format Data, Advanced Wipe->Dalvik/ART;System;Data;Internal Storage).
Reset the phone and enter TWRP once again.
Copy the official ZIP with OOS 3.5.x ROM into phone's memory, then flash it.
Flash SuperSU, otherwise your phone won't boot.
I don't take any responsibility, in case you mess something up with your phone.
Click to expand...
Click to collapse
Thx. I might have forgotten to reset the phone after wipe, before installing 3.5.4 which is why it wouldn't install even from twrp. My solution worked though - encrypting it again will be for another day. Sick of geeking
So once you have working 3.5.3/4 can you return it to stock - I mean by relocking bootloader and reflashing stock recovery? So then to receive 4.0 via OTA?
Thanks
white43 said:
So once you have working 3.5.3/4 can you return it to stock - I mean by relocking bootloader and reflashing stock recovery? So then to receive 4.0 via OTA?
Thanks
Click to expand...
Click to collapse
Yes, it's entirely possible, but what's the point? You can flash stock recovery->lock bootloader->sideload OOS 4.0, and you are stock . From what I've read, not everyone got 4.0 through OTA yet.
Do you have to be on a specific version of twrp to do this? I cant flash 3.5.4 back using the latest twrp (3031)
EDIT
Never mind all OK, was just begin inpatient
white43 said:
So once you have working 3.5.3/4 can you return it to stock - I mean by relocking bootloader and reflashing stock recovery? So then to receive 4.0 via OTA?
Thanks
Click to expand...
Click to collapse
Do you have a link for the stock 3.5.X recovery? Link from O+ download section won't work..
They provide the so-called Oxygen Stock REC for OP3T here: downloads.oneplus.net/
But I always got different MD5 after downloading the img they provided.
spida_singh said:
Do you have to be on a specific version of twrp to do this? I cant flash 3.5.4 back using the latest twrp (3031)
EDIT
Never mind all OK, was just begin inpatient
Click to expand...
Click to collapse
Hey I am in same boat, does TWRP version matters to return from 4.0.2 to 3.5.3.
I have TWRP(3031) and SU 2.79. I want to revert for battery as well xposed.
uttam.ace said:
Hey I am in same boat, does TWRP version matters to return from 4.0.2 to 3.5.3.
I have TWRP(3031) and SU 2.79. I want to revert for battery as well xposed.
Click to expand...
Click to collapse
It will work with 3.0.3-1 TWRP but you have to flash the ROM twice because of filesystem and put the files twice on the internal memory. Reboot recovery twice forced.
I think TWRP 3.0.4.0 should work better but I do not used it on my phone to restore from 4.0.2 to 3.5.4 so you could try and let us know
---------- Post added at 06:35 PM ---------- Previous post was at 06:32 PM ----------
https://forums.oneplus.net/threads/how-to-restore-to-3-5-4-from-4-0-2-on-op3t.493963/
I made this but you can flash it at your own risk.
To me it worked.
And another tutorial I found but not tried is here https://forum.xda-developers.com/showpost.php?p=70310185&postcount=308
Oneplus 3T downgrade bootloader locked
Hello everyone!
I have a OP3T locked by frp and android nougat oxygen 4.0.3. Is there any solution to downgrade the android to oxygen 3.x??
Thank you guys,
Cheers!
spida_singh said:
Do you have to be on a specific version of twrp to do this? I cant flash 3.5.4 back using the latest twrp (3031)
EDIT
Never mind all OK, was just begin inpatient
Click to expand...
Click to collapse
I tried using TWRP 3.0.4.1,
I was able to flash. thing is, while flashing zip in twrp, it won't show any progress for 2-10 minutes.
then it will show finished flashing
---------- Post added at 07:12 PM ---------- Previous post was at 07:07 PM ----------
I want to share my experience,
Latest TWRP 3.0.4.1 made all difficulty easy,
I was in oxyzen os 4.1.6.
then tried sideload, it fails,
then installed TWRp and flash 3.5.4 via TWRP, (have to flash data,system,cache,internal storage) before flashing,
then it just booted, no issue
Hello, I've softbricked a fair amount of phones and tablets in my time but I must admit never had this show up. After flashing Twrp and a dm-verity thingy, I received this shiny new error on my new 1+3t. While I'm assuming it's a straightforward fix such as:
Booting into Twrp and flashing stock 4.x Oxygen os and the stock recovery to bring phone back to where I started.
My question is, can't I just go straight about flashing a rom? I.e freedom rom, or is it advisable to just try start again?
And is me flashing stock os then recovery got to work?
Everything is still stock there is no root. All I have done is:
Code:
fastboot > oemunlock > reboot > fastboot flash Twrp > Twrp boot > Twrp > swiped to Modify > flashed dm-verity.
I did receive a password request first time round but after I rebooted phone it wasn't there again.
Thank you for helping in advance.
Archtects said:
Hello, I've softbricked a fair amount of phones and tablets in my time but I must admit never had this show up. After flashing Twrp and a dm-verity thingy, I received this shiny new error on my new 1+3t. While I'm assuming it's a straightforward fix such as:
Booting into Twrp and flashing stock 4.x Oxygen os and the stock recovery to bring phone back to where I started.
My question is, can't I just go straight about flashing a rom? I.e freedom rom, or is it advisable to just try start again?
And is me flashing stock os then recovery got to work?
Everything is still stock there is no root. All I have done is:
Code:
fastboot > oemunlock > reboot > fastboot flash Twrp > Twrp boot > Twrp > swiped to Modify > flashed dm-verity.
I did receive a password request first time round but after I rebooted phone it wasn't there again.
Thank you for helping in advance.
Click to expand...
Click to collapse
You had to flash supersu or Magisk after the process to disable force encryption also make sure your are on the nougat supported twrp 3.0.4-1 or later
You can flash any rom if you have an unlocked bootloader and a working twrp
Sent from my Funk Tuned 3T
Funk Wizard said:
You had to flash supersu or Magisk after the process to disable force encryption also make sure your are on the nougat supported twrp 3.0.4-1 or later
You can flash any rom if you have an unlocked bootloader and a working twrp
Click to expand...
Click to collapse
thanks I think that's where I went wrong. I should have flashed Magisk. The guide says so but I only intended to flash a rom. Eh. I'll see if I can flash Magisk. All is not lost. I'll update once I get home. I'm annoyed with my self lol.
-101 xda points
Archtects said:
thanks I think that's where I went wrong. I should have flashed Magisk. The guide says so but I only intended to flash a rom. Eh. I'll see if I can flash Magisk. All is not lost. I'll update once I get home. I'm annoyed with my self lol.
-101 xda points
Click to expand...
Click to collapse
No prob buddy, let me know if you get stuck anywhere :fingers-crossed:
Sent from my OnePlus 3T using XDA Labs
Funk Wizard said:
No prob buddy, let me know if you get stuck anywhere :fingers-crossed:
Click to expand...
Click to collapse
I will do, hopefully it be fine. I'll try different thing if stuff doesn't work and I'll post back what I did incase anyone else has similar problem .
Twrp doesn't see any internal storage what so ever. So Ive flashed stock recovery from fastboot and going to attempt to sideload the stock OS. fingers-crossed
Funk Wizard said:
No prob buddy, let me know if you get stuck anywhere :fingers-crossed:
Click to expand...
Click to collapse
Thanks for your help im back to a working phone!
For anyone who get stuck!
1) download op3t stock recovery and the oxygen OS from oneplus website
2) boot into fastboot.
3) with your pc get up Adb and:
Code:
fastboot flash recovery stock.img
Fastboot boot stock.img
[\CODE]
4) Once you boot into recovery navigate to install from adb.
5) in cmd again on pc type
[CODE] adb sideload filename.zip
[\CODE]
6) then reboot :). You can leave it here if you want.
So I'm back on stock. With Magisk installed. Only dm-verity still come up which I'm not keen on. But I guess I can live with it. But I'm stuck with a bunch of system apps I can't get rid of? I've tried titanium backup, and link2sd my go to but nothing any ideas? Anyone now how to get rid?
Archtects said:
So I'm back on stock. With Magisk installed. Only dm-verity still come up which I'm not keen on. But I guess I can live with it. But I'm stuck with a bunch of system apps I can't get rid of? I've tried titanium backup, and link2sd my go to but nothing any ideas? Anyone now how to get rid?
Click to expand...
Click to collapse
I can recommend OOS Aroma Debloater Credits: @siankatabg :good:
Funk Wizard said:
I can recommend OOS Aroma Debloater Credits: @siankatabg :good:
Click to expand...
Click to collapse
Cheers I found the zip you. Mentioned after I posted the question, worked sort of lol. Some still won't go but it's got rid of a fair chunk an dive just frozen any I don't want.
Today, after i installed the latest OOS 5.0.1 with Android O 8.0, i decided to root my device.
After successfully unlocking the bootloader, i flashed the TWRP Recovery and flashed the SuperSU zip, i was stuck on the 1+ Boot logo. I tried fixing the contents through advanced options of TWRP recovery and still no luck. I also tried wiping my cache, data, dalvik etc...
So far i tried:
Installed stock recovery via fastboot, then adb sideload. My device was recognized when typing ADB Devices but when i tried to adb sideload ota.zip i got the cannot read *...zip* error. Then i tried everything i could find, my devices are installed correctly, i also tried the Large Address Awarness program and still no luck.
Then i flashed TWRP again through fastboot and try to do the same through TWRP's sideload. Still no luck
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still no luck
I ran out of ideas.... What can i do?
Thanks in advance
First of all, why didn't you make a TWRP backup of the stock ROM before trying to root? This is best practice before trying any mods (root, flashing ROMs) for reasons which are probably now obvious. I'm always surprised at how many folks skip this step.
Maybe you planned ahead of time to use the stock recovery image, if you had to. But since it wasn't on the phone when you need it, you're running into the problem of getting it on there now.
Yiannis75 said:
i flashed the TWRP Recovery and flashed the SuperSU zip
Click to expand...
Click to collapse
What version TWRP, and what version SuperSU?
Honestly, I would recommend Magisk for root, over SuperSU. I've seen a number of folks have problems with recent version SuperSU on this device. And Magisk has a lot of really cool, useful features. I'm normally not one to recommend one method over another. Especially since SuperSU was so tried and true for so long. But at this point, I see no benefit of using SuperSU, but many benefits to Magisk. And seemingly less problems rooting with Magisk. My recommendation would be current version Magisk, which is v16.0.
Yiannis75 said:
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still
Click to expand...
Click to collapse
First of all, make sure you are using the "full" update zip (which will be >1 GB) and not the partial OTA "patch". You can get the full zip from here (Post #2): https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Since you have TWRP installed, boot into TWRP. You should be able to see your internal storage on your computer, just like it's a thumb drive. Just drag/copy and drop the full OTA zip onto the phone's internal storage. Then just flash the zip in TWRP.
The internal storage should be selected to "Mount" in TWRP by default. But if you can't see internal storage on your computer, make sure it's selected in the TWRP "Mount" section.
Yiannis75 said:
Today, after i installed the latest OOS 5.0.1 with Android O 8.0, i decided to root my device.
After successfully unlocking the bootloader, i flashed the TWRP Recovery and flashed the SuperSU zip, i was stuck on the 1+ Boot logo. I tried fixing the contents through advanced options of TWRP recovery and still no luck. I also tried wiping my cache, data, dalvik etc...
So far i tried:
Installed stock recovery via fastboot, then adb sideload. My device was recognized when typing ADB Devices but when i tried to adb sideload ota.zip i got the cannot read *...zip* error. Then i tried everything i could find, my devices are installed correctly, i also tried the Large Address Awarness program and still no luck.
Then i flashed TWRP again through fastboot and try to do the same through TWRP's sideload. Still no luck
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still no luck
I ran out of ideas.... What can i do?
Thanks in advance
Click to expand...
Click to collapse
Which exact version of TWRP did you install?
Are you Greek btw?
Unleashed by my rooted OP3T on 8.0
RASTAVIPER said:
Which exact version of TWRP did you install?
Are you Greek btw?
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
I believe i used TWRP 3.2.1-0... the very latest
And yeah am cypriot
Yiannis75 said:
I believe i used TWRP 3.2.1-0... the very latest
Click to expand...
Click to collapse
You can verify by booting to TWRP. It says version number on the splash screen.
Did you look at, or try my recommendations in my last response?
redpoint73 said:
First of all, why didn't you make a TWRP backup of the stock ROM before trying to root? This is best practice before trying any mods (root, flashing ROMs) for reasons which are probably now obvious. I'm always surprised at how many folks skip this step.
Maybe you planned ahead of time to use the stock recovery image, if you had to. But since it wasn't on the phone when you need it, you're running into the problem of getting it on there now.
What version TWRP, and what version SuperSU?
Honestly, I would recommend Magisk for root, over SuperSU. I've seen a number of folks have problems with recent version SuperSU on this device. And Magisk has a lot of really cool, useful features. I'm normally not one to recommend one method over another. Especially since SuperSU was so tried and true for so long. But at this point, I see no benefit of using SuperSU, but many benefits to Magisk. And seemingly less problems rooting with Magisk. My recommendation would be current version Magisk, which is v16.0.
First of all, make sure you are using the "full" update zip (which will be >1 GB) and not the partial OTA "patch". You can get the full zip from here (Post #2): https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Since you have TWRP installed, boot into TWRP. You should be able to see your internal storage on your computer, just like it's a thumb drive. Just drag/copy and drop the full OTA zip onto the phone's internal storage. Then just flash the zip in TWRP.
The internal storage should be selected to "Mount" in TWRP by default. But if you can't see internal storage on your computer, make sure it's selected in the TWRP "Mount" section.
Click to expand...
Click to collapse
I did make a nandroid backup from TWRP i just didnt restore it because i thought it was TWRP’s issue due to dm-variety... my bad but whatever
Yeah i have read about Magisk i just didnt investigate enough to know exactly what it is was so i thought it would be better to go for SuperSU because thats what i used on every android device i has... my bad aswell here
About the full update zip.. i’ll try that because i think i was trying to sidelod the ota patch which was 1.6gb...(but still, is the “cannot read xxx.zip” related with what zip file do i sideload? Whatever ill try it when i get home
And also i have already tried the mount feature of twrp recovery but my device just wouldnt show up on my computer.... I will try again later when i have the time and i will contact you if i need any help(if thats ok ofcourse) ...thanks in advance
Yiannis75 said:
I did make a nandroid backup from TWRP i just didnt restore it because i thought it was TWRP’s issue due to dm-variety... my bad but whatever
Click to expand...
Click to collapse
TWRP and root shouldn't normally trip DM-verity (make the phone not boot).
I don't think it will hurt anything at this point to restore the backup you made. You're already trying to flash stock recovery, anyway (which is not that different).
If the restore is successful (phone boots to OS), then just flash Magisk and be done with it!
Yiannis75 said:
Yeah i have read about Magisk i just didnt investigate enough to know exactly what it is was so i thought it would be better to go for SuperSU because thats what i used on every android device i has... my bad aswell here
Click to expand...
Click to collapse
I wouldn't say it's "your bad". Magisk is just a suggestion or recommendation. Some folks have had success with SuperSU. But also seems like a lot more folks than usual, having problems (like no boot) with SuperSU than I'm used to seeing. And as I mentioned, I don't see any benefit of SuperSU (over Magisk) at this point. I was slow to change as well. But after trying Magisk, there has been no going back for me since. So therefore, the suggestion.
You didn't mention what version SuperSU, but 2.82 SR5 is recommended. It's in beta now, so if you used the "stable" 2.82 version, that might be the problem right there.
Yiannis75 said:
About the full update zip.. i’ll try that because i think i was trying to sidelod the ota patch which was 1.6gb...(but still, is the “cannot read xxx.zip” related with what zip file do i sideload? Whatever ill try it when i get home
Click to expand...
Click to collapse
If it was 1.6GB, than it was the full update (at least one of them). I typed ">1 GB" so any OTA zip for this device greater than 1 GB should be okay. It's the OTA zips that are less than 1 GB that you need to watch out for, as it is not a full update, just a partial "patch" (don't flash on a modded device with TWRP or you will soft brick!).
I don't personally use sideload. While I see the convenience, I find it a bit messy. I've seen folks have problems with sideload, when simply putting the ROM on the phone and flashing with TWRP works fine (so in those cases sideload itself was the point of failure).
Now of course, getting the ROM on the phone is the problem, in your case.
Yiannis75 said:
And also i have already tried the mount feature of twrp recovery but my device just wouldnt show up on my computer.... I will try again later when i have the time and i will contact you if i need any help(if thats ok ofcourse)
Click to expand...
Click to collapse
Just post to this thread, and I'll see it. That is the best way to contact me. Good luck!
Yiannis75 said:
I believe i used TWRP 3.2.1-0... the very latest
And yeah am cypriot
Click to expand...
Click to collapse
Inta mou laleis??
Coming to Cyprus soon bro!
About your issue, use TWRP bluespark 8.61, just to be sure.
Never had issues with this version.
Unleashed by my rooted OP3T on 8.0
redpoint73 said:
TWRP and root shouldn't normally trip DM-verity (make the phone not boot).
I don't think it will hurt anything at this point to restore the backup you made. You're already trying to flash stock recovery, anyway (which is not that different).
If the restore is successful (phone boots to OS), then just flash Magisk and be done with it!
I wouldn't say it's "your bad". Magisk is just a suggestion or recommendation. Some folks have had success with SuperSU. But also seems like a lot more folks than usual, having problems (like no boot) with SuperSU than I'm used to seeing. And as I mentioned, I don't see any benefit of SuperSU (over Magisk) at this point. I was slow to change as well. But after trying Magisk, there has been no going back for me since. So therefore, the suggestion.
You didn't mention what version SuperSU, but 2.82 SR5 is recommended. It's in beta now, so if you used the "stable" 2.82 version, that might be the problem right there.
If it was 1.6GB, than it was the full update (at least one of them). I typed ">1 GB" so any OTA zip for this device greater than 1 GB should be okay. It's the OTA zips that are less than 1 GB that you need to watch out for, as it is not a full update, just a partial "patch" (don't flash on a modded device with TWRP or you will soft brick!).
I don't personally use sideload. While I see the convenience, I find it a bit messy. I've seen folks have problems with sideload, when simply putting the ROM on the phone and flashing with TWRP works fine (so in those cases sideload itself was the point of failure).
Now of course, getting the ROM on the phone is the problem, in your case.
Just post to this thread, and I'll see it. That is the best way to contact me. Good luck!
Click to expand...
Click to collapse
So, got home fixed the drivers so that my pc could recognize my device while on TWRP recovery, flashed the zip file through TWRP and it worked like a charm
Thanks for all the help bro
Help pls
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) 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:
Help pls
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) 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
just like me, if u flash oos 5.0.2 from twrp u will be just fine. Just flash magisk instead of supersu like i did and all will be working just fine
mannulko said:
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) 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
If posting on a thread, related to your issue; it would make sense to actually read the responses in the thread. Since your question is already answered.
In short, you need to use SuperSU 2.82 SR5. The "stable" version 2.82 won't work, and will result in no boot. Or use Magisk 16.0.
If the phone still won't boot after (only) flashing the proper version SuperSU or Magisk; then flash the full stock update file using TWRP. Then flash the right version SuperSU or Magisk.
So as I go over the custom roms available in the development section I cannot help but notice how many users state that the rom is causing random reboots. It is usually due to said user flashing the custom rom over a beta OOS version instead of the latest stable build as the OP instructions usually indicate. The reboots are hardly caused by the rom itself. I am putting together this guide to help users go from beta back to stable. This will allow a clean install of the custom rom and usability as it is intended.
This can also be used to just go back to stable from beta if you want to run the stable OOS.
There are 2 ways to do this. One is via TWRP if that is what you prefer or you can also use the MSM tool to flash back to the latest stable. Both ways will wipe and format your internal data. This is due to the mismatch in security patches between beta and stable. So be sure to make a backup of your internal storage if there is stuff there that you need. You have been warned.
NOTE: Highly recommended to use a computer to make things easier. If you do not have a computer available, use the TWRP method listed below to get back to stable OOS. Once OOS boots, you can download your custom rom of choice using your phone and install it.
Here are the links for the latest MSM tool and latest stable zip if you want to use the TWRP method:
Latest MSM Tool
Latest stable OOS to flash in TWRP
TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here.
If you want to run a custom rom, reboot to TWRP, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. If no PC is available, download your rom and needed files like twrp, magisk etc. using OOS stable first. Then you can reboot to recovery and follow the installation steps provided by your rom developer on their page.
Steps for MSM:
Download the latest MSM tool with link from above. Boot phone to EDL either by powering off the phone then holding Vol + and - with Power or my preferred way via adb by typing adb reboot edl. Plug in phone once in EDL and let MSM do its thing. If you are not sure how to use MSM, the link for the MSM tool outlines the steps. Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here. Note, your bootloader is locked. You will need to do an oem unlock to install twrp and magisk if you want root or to install a custom kernel.
If you want to run a custom rom or root your phone, get to the settings screen.. you can skip setting up your phone so just hit skip on all the prompts for set up. Go to settings, enable developer options. Make sure OEM unlock is selected and USB debugging is selected. Once you do that, do adb reboot bootloader. Then do the following:
fastboot oem unlock
It will reboot the phone. Skip through the set up again and go back to settings. Enable developer options and enabled USB debugging. Then run adb reboot bootloader. In the bootloader, do the following:
fastboot boot <twrp.img> (replace this with the actual file name)
From there, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. Follow the installation steps provided by your rom developer on their page.
i am on OpenBeta9,can i use the Twrp Method for a downgrade to the Stable 9.0.13?
Gesendet von meinem xXx_NoLimits_6.0 on ONEPLUS 6T mit Tapatalk
MarcoG: said:
i am on OpenBeta9,can i use the Twrp Method for a downgrade to the Stable 9.0.13?
Click to expand...
Click to collapse
Given the problems with rolling back security patches I wondered the same thing. However, assuming we wiped everything including system it should work. Having said that, when I previously tried rolling back to the latest stable from beta, when I fastboot flashed everything to both slots, I could never get it to boot and was able to flash beta and get it running again.
ultyrunner said:
Given the problems with rolling back security patches I wondered the same thing. However, assuming we wiped everything including system it should work. Having said that, when I previously tried rolling back to the latest stable from beta, when I fastboot flashed everything to both slots, I could never get it to boot and was able to flash beta and get it running again.
Click to expand...
Click to collapse
I'd like to see a resolution to this ^
This should not be this complicated any time I my base whether it beta or stable I never met to do all of this...
It's super simple to go back to whatever oos version you want without the need of msm tool and all this extra stuff.... I've went from beta to stable and back to beta several times no issues... And you are going to have to format data no matter what if you are changing oos versions and don't want to run into an encryption problem.
You can just back everything up
Boot to fastboot
Fastboot format userdata
Fastboot boot twrp. img
Transfer needed files. (oos, twrp)
Flash oos + twrp
Reboot recovery (make sure the slot changed)
Flash oos + twrp
Reboot system make sure it boots up right
Now you can go flash the rom you want
Causical said:
I'd like to see a resolution to this ^
Click to expand...
Click to collapse
I can verify the TWRP steps outlined above (in the OP, not the comment with Fastboot) worked perfectly for me. Did everything in exactly the same order. Was on beta 8 and went to 9.0.13 without a hitch.
se7ensde said:
This should not be this complicated any time I my base whether it beta or stable I never met to do all of this...
It's super simple to go back to whatever oos version you want without the need of msm tool and all this extra stuff.... I've went from beta to stable and back to beta several times no issues... And you are going to have to format data no matter what if you are changing oos versions and don't want to run into an encryption problem.
You can just back everything up
Boot to fastboot
Fastboot format userdata
Fastboot boot twrp. img
Transfer needed files. (oos, twrp)
Flash oos + twrp
Reboot recovery (make sure the slot changed)
Flash oos + twrp
Reboot system make sure it boots up right
Now you can go flash the rom you want
Click to expand...
Click to collapse
what about directy through TWRP? can I just replace fastboot with TWRP in your instructions or does Formatting userdata erase internal files (ie: TWRP, Magisk, etc... I'm only asking because I've only ever updated to the latest OOS and I'm just curious for future possible future tinkering)
---------- Post added at 12:38 AM ---------- Previous post was at 12:34 AM ----------
ultyrunner said:
I can verify the TWRP steps outlined above (in the OP, not the comment with Fastboot) worked perfectly for me. Did everything in exactly the same order. Was on beta 8 and went to 9.0.13 without a hitch.
Click to expand...
Click to collapse
Awesome, you sir are THEE man. Please get a job with XDA or something
Causical said:
Awesome, you sir are THEE man. Please get a job with XDA or something
Click to expand...
Click to collapse
Um ... OK ... ?
Causical said:
what about directy through TWRP? can I just replace fastboot with TWRP in your instructions or does Formatting userdata erase internal files (ie: TWRP, Magisk, etc... I'm only asking because I've only ever updated to the latest OOS and I'm just curious for future possible future tinkering)
---------- Post added at 12:38 AM ---------- Previous post was at 12:34 AM ----------
Awesome, you sir are THEE man. Please get a job with XDA or something
Click to expand...
Click to collapse
Yeah sure you can mix up the steps or skip whatever you want..
se7ensde said:
Yeah sure you can mix up the steps or skip whatever you want..
Click to expand...
Click to collapse
LOL, yeah. I was kind of surprised with the smart-ass comment, but then again lots of people on here don't follow instructions, do things out of order and then wonder what went wrong or why they suddenly have a $700 paper weight. Given how much chatter there's been about the MSM tool (not an option on Mac) or needing to fastboot flash individual images (which didn't work for me), I was surprised how easy moving back to stable completely via TWRP is. I'm used flashing Nexus and older Samsung devices, which used to be dead-simple.
ultyrunner said:
LOL, yeah. I was kind of surprised with the smart-ass comment, but then again lots of people on here don't follow instructions, do things out of order and then wonder what went wrong or why they suddenly have a $700 paper weight. Given how much chatter there's been about the MSM tool (not an option on Mac) or needing to fastboot flash individual images (which didn't work for me), I was surprised how easy moving back to stable completely via TWRP is. I'm used flashing Nexus and older Samsung devices, which used to be dead-simple.
Click to expand...
Click to collapse
You were probably surprised with the smart ass comment because it wasn't a smart ass comment Sgt. Dillweed (that was a little smart ass)...I don't generally give a thanks to someone to be a smart ass, but nice to know where your head's at.
Causical said:
You were probably surprised with the smart ass comment because it wasn't a smart ass comment Sgt. Dillweed (that was a little smart ass)...I don't generally give a thanks to someone to be a smart ass, but nice to know where your head's at.
Click to expand...
Click to collapse
Nope. I was surprised because ...
Awesome, you sir are THEE man. Please get a job with XDA or something
Click to expand...
Click to collapse
... is definitely smart-ass, and seems odd after receiving a like. If you don't see that in the tone, I'm afraid I can't help you.
I think THAT may be more indicative of where your head's at. But ... carry on and you keep on doing you, bud.
ultyrunner said:
Nope. I was surprised because ...
... is definitely smart-ass, and seems odd after receiving a like. If you don't see that in the tone, I'm afraid I can't help you.
I think THAT may be more indicative of where your head's at. But ... carry on and you keep on doing you, bud.
Click to expand...
Click to collapse
Cool I'm glad you can explain the "tone" and characteristics of my own words to me. I'll remember to try and not be so nice towards you next time, at least if I really be a **** it won't be mistaken.
I WAS originally thrilled by your simple and to the point response, but since you decided to twist my words and make yourself look like a jack ass... well nicely done, is all I have to say ?
Words of a Wise Guy: "hmmm seems odd after receiving a like..."
Huh, just think about that one for a second.
Causical said:
Cool I'm glad you can explain the "tone" and characteristics of my own words to me.
Click to expand...
Click to collapse
Clearly someone has to, because you can't understand that everyone isn't inside your head to hear the little voices that define 'polite' for you. Anyway, you're on the ignore list now.
ultyrunner said:
Clearly someone has to, because you can't understand that everyone isn't inside your head to hear the little voices that define 'polite' for you. Anyway, you're on the ignore list now.
Click to expand...
Click to collapse
Oooo scary...I guess I'll take my "like" or thanks back whatever you call it.
the.emilio said:
So as I go over the custom roms available in the development section I cannot help but notice how many users state that the rom is causing random reboots. It is usually due to said user flashing the custom rom over a beta OOS version instead of the latest stable build as the OP instructions usually indicate. The reboots are hardly caused by the rom itself. I am putting together this guide to help users go from beta back to stable. This will allow a clean install of the custom rom and usability as it is intended.
This can also be used to just go back to stable from beta if you want to run the stable OOS.
There are 2 ways to do this. One is via TWRP if that is what you prefer or you can also use the MSM tool to flash back to the latest stable. Both ways will wipe and format your internal data. This is due to the mismatch in security patches between beta and stable. So be sure to make a backup of your internal storage if there is stuff there that you need. You have been warned.
NOTE: Highly recommended to use a computer to make things easier. If you do not have a computer available, use the TWRP method listed below to get back to stable OOS. Once OOS boots, you can download your custom rom of choice using your phone and install it.
Here are the links for the latest MSM tool and latest stable zip if you want to use the TWRP method:
Latest MSM Tool
Latest stable OOS to flash in TWRP
TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here.
If you want to run a custom rom, reboot to TWRP, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. If no PC is available, download your rom and needed files like twrp, magisk etc. using OOS stable first. Then you can reboot to recovery and follow the installation steps provided by your rom developer on their page.
Steps for MSM:
Download the latest MSM tool with link from above. Boot phone to EDL either by powering off the phone then holding Vol + and - with Power or my preferred way via adb by typing adb reboot edl. Plug in phone once in EDL and let MSM do its thing. If you are not sure how to use MSM, the link for the MSM tool outlines the steps. Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here. Note, your bootloader is locked. You will need to do an oem unlock to install twrp and magisk if you want root or to install a custom kernel.
If you want to run a custom rom or root your phone, get to the settings screen.. you can skip setting up your phone so just hit skip on all the prompts for set up. Go to settings, enable developer options. Make sure OEM unlock is selected and USB debugging is selected. Once you do that, do adb reboot bootloader. Then do the following:
fastboot oem unlock
It will reboot the phone. Skip through the set up again and go back to settings. Enable developer options and enabled USB debugging. Then run adb reboot bootloader. In the bootloader, do the following:
fastboot boot <twrp.img> (replace this with the actual file name)
From there, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. Follow the installation steps provided by your rom developer on their page.
Click to expand...
Click to collapse
Thank you it works[emoji16]
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
se7ensde said:
Fastboot format userdata
Click to expand...
Click to collapse
What is formatted? The complete internal sdcard?
TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Will this work if I'm on beta14 with July security patch, and I want to flash back to stable . 15 with June security patch? I'm using TWRP 3.3.1-6. I ask because I would like to flash back to stable but will not have access to my laptop for a week or two, so I'd like to do it right through twrp if at all possible
Ryano89 said:
TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Will this work if I'm on beta14 with July security patch, and I want to flash back to stable . 15 with June security patch? I'm using TWRP 3.3.1-6. I ask because I would like to flash back to stable but will not have access to my laptop for a week or two, so I'd like to do it right through twrp if at all possible
Click to expand...
Click to collapse
Yes.
Mannan Qamar said:
Yes.
Click to expand...
Click to collapse
Thanks, I only ask because I see a lot of disagreement about it on different threads. Some say you can do it, other's say you can't do it if you are flashing back to an older security patch. It's not urgent for me so I might just wait until I have access to my laptop again, but I was hoping to do it now. Won't format completely erase the device?
There maybe a number of reasons to go back to the stock ROM. We do not discuss them here
But what to do if you flashed something, wanting to go back to stock, and did not brick your Realme X2 yet? Here is super quick howto guide. There are other possible ways and sequences to perform the task, but the one listed below is tested.
The same procedure applys for a case when you want to downgrade you phone (when its bootloader unlocked). Say, current custom ROMs are based on ColorOS 6.1/Android 9 vendor contents but you have realmeUI/Android 10 already. In order to try one of those custom ROMs you should downgrade to the latest Android 9 stock firmware first.
The essential part of the customized phone is custom recovery. Currently Realme OZIP file does not contain stock recovery inside. It is being generated as explained below, in the post #2, see EDIT3. It means you need to find somewere PROPER stock recovery corresponding to your ROM to put it back. See Realme X2 stock recovery links below, post #2, EDIT4.
Which stock recovery to use? The one for your model and which version is not newer than the ROM version you are flashing. For example, you need A.17 stock ROM for CN model (RMX1991). Then any recovery of A.12, A.14, A.16, A.17 for RMX1991 will work for you.
Download and unzip the stock recovery partition image from the next post, this will be a file like rmx1991-sde20-stock_recovery.img.
Download stock ROM ozip file (for example, from here). Put it to a SD card with a filesystem which supports files more than 2GB (ext4 works fine. Stock recovery, but not ColorOS, supports it). Put the SD card into the phone.
Start (reboot) phone into fastboot mode
From a computer perform fastboot flash recovery rmx1991-sde20-stock_recovery.img
From the fastboot mode by means of volume buttons select 'Recovery mode' and push Power button
From the stock recovery select language needed (there are three only), then 'Install from storage device', then 'From SD card', tap the OZIP file with your ROM
When the update process is done, phone reboots. Most likely, it will not be able to boot normally because you need to wipe out data. Either help the phone with keeping Vol Down button pressed during reboot, or it will boot recovery by itself. Now wipe data (confirm by entering random 4-digit code), select 'Format data'. Phone will reboot
Here it is. Enjoy (or sell your Realme X2 with its shiny stock experience...
If you want to lock bootloader after all above mentioned steps (you have to make them all unless you wanna get a brick ), boot fastboot mode, perform fastboot flashing lock. This will wipe your data again. Then optionally lock 'OEM Unlock' option in 'Developer Options'. Even further, you can install In-DepthTest.apk and sign out from In-Depth Test program.
2022-12-25 EDIT: For downgrade from Android 11 to 10 read this post
I have found out that in fact stock recovery does not exist as a prebuilt file It is being created by the script /system/bin/install-recovery.sh on a basis of stock boot partition and a patch file /system/recovery-from-boot.p
It means in theory you can recreate stock recovery having only Realme ozip file.
EDIT1 The command to do it in Linux shell is
Code:
bspatch boot.img selfmade_stock_recovery.img recovery-from-boot.p
Cool! Tested.
EDIT2. For the current moment when unlocked bootloader breaks fingerprint sensor: as soon as the bootloader is locked again, fingerprint starts functioning as it should.
EDIT3 Becomes clear that each ROM release has its own stock recovery which is generated automatically on the basis of boot.img and recovery-from-boot.p . Not only boot.img is being changed each release, but recovery-from-boot.p is changing as well. If the wrong stock recovery is installed, you might not be able to decrypt data and connect to WiFi from within recovery. Seemingly it may bring you serious problems if locking back bootloader (thus bricking the device). Good thing (as I understood, but not checked yet) is that after flashing stock ROM with a help of a stock recovery next reboot should replace your stock recovery with an up-to-date version of it. So to be on a safe side make sure that you rebooted to system and that your recovery reflashed by the system before you lock bootloader.
EDIT4 In order to combine everything in one place:
Stock recoveries for RMX1991 (China version): here
Stock recoveries for RMX1992 (India version): here
Stock recoveries for RMX1993 (Euro version): here
EDIT5 In later ROM releases patch and script files are relocated into vendor partition, they are /bin/oppo-install-recovery.sh and /recovery-from-boot.p there.
EDIT6 Please note that the method above is working with officially downloaded ROMs from realme support site (read here why).
So this method works if you brick your phone trying to install a global rom to china variant..
Hi,
does only works with SDcard insert.
Because the internal storage is decrypted.
And it does not work on X2.
But why?
Installation failed?
This method will bring back my FP working again right?
Can you please confirm this method https://boycracked.com/2019/10/26/official-realme-x2-rmx1991-stock-rom/
SkyeJace said:
This method will bring back my FP working again right?
Click to expand...
Click to collapse
You have to lock bootloader for this. See the very last part of the howto, post #1
AldRezaine said:
Can you please confirm this method https://boycracked.com/2019/10/26/official-realme-x2-rmx1991-stock-rom/
Click to expand...
Click to collapse
The site provides generalized instructions for everything
As for Realme X2, there are two methods claimed, one is for ozip file, another for ofp file; last one is not yet publicly available somewhere (the link is replaced by the Coming soon promise).
If you find there something certain regarding ozip procedure for Realme X2, give me the link, please. I couldn't
why I back to stock rom, apps i uninstalled it is don't auto reinstall?
hello guys, how can i get the 1993ex stock recovery? i screwd up big time !
hammerheading said:
hello guys, how can i get the 1993ex stock recovery? i screwd up big time !
Click to expand...
Click to collapse
Read the post #2 in this thread, it contains ample info needed for this. If you are requesting ready-to-flash stock recovery file, you should tell the version of the ROM you are going to flash and powerful word please to it
BaDuc said:
why I back to stock rom, apps i uninstalled it is don't auto reinstall?
Click to expand...
Click to collapse
I am not 100% sure I understand you right. If you are about some stock apps missing after wiping the userdata partition, this is true: some of the apps were preinstalled onto data space (some of them are Weather app, One-Tap Lockscreen). I could find only some of them in a form of apk files.
yakovpol said:
Read the post #2 in this thread, it contains ample info needed for this. If you are requesting ready-to-flash stock recovery file, you should tell the version of the ROM you are going to flash and powerful word please to it
Click to expand...
Click to collapse
Thanks a lot for the attention. I tryed to recreate the recovery but with no success because i dont know the proper method, it's a bit over my android skills as i can only root unlock bl and do some minor stuff and GSI is a new thing for me. AS for the version it is the a17 of the 1993ex(eu).
yakovpol said:
I am not 100% sure I understand you right. If you are about some stock apps missing after wiping the userdata partition, this is true: some of the apps were preinstalled onto data space (some of them are Weather app, One-Tap Lockscreen). I could find only some of them in a form of apk files.
Click to expand...
Click to collapse
yes, right my mind, including my Breeno is faulty, and now I can't click to setting Breeno in the settings, do you have apk of app, can you send me?
hammerheading said:
Thanks a lot for the attention. I tryed to recreate the recovery but with no success because i dont know the proper method, it's a bit over my android skills as i can only root unlock bl and do some minor stuff and GSI is a new thing for me. AS for the version it is the a17 of the 1993ex(eu).
Click to expand...
Click to collapse
For the moment I have one for the EU A.16 version only, look here. Eventually A.17 will be added there too.
BaDuc said:
yes, right my mind, including my Breeno is faulty, and now I can't click to setting Breeno in the settings, do you have apk of app, can you send me?
Click to expand...
Click to collapse
Those I have are uploaded to here.
yakovpol said:
Those I have are uploaded to here.
Click to expand...
Click to collapse
thanks you very much
yakovpol said:
For the moment I have one for the EU A.16 version only, look here. Eventually A.17 will be added there too.
Click to expand...
Click to collapse
Thank you so much, that did the trick!! i was able to flash the a17 and the phone is working fine now . But i'm not trully satisfied, i can't find a away to flash a GSI rom successfully, but that's another topic ... Thank you again and keep up the good work !
can u plsss provide stock recovery for realme x2 rmx1992, i bricked my phone trying to install stock os since 2 days, cant find a way..if some has the recovery pls provide it. im able to boot to twrp, bootloader is unloced and with the other recoveries im not able to intsall the stock rom.pls help.
Can send me 1992 stcok recovery file ozip please.