Database Develop

Hydrogen OS 2.5.1 to Oxygen OS 3.5

Hi everyone,
I literally just got the Chinese version of the oneplus 3T (A3010) and I want to move from Hydrogen OS 2.5.1 to Oxygen OS 3.5 official with OTA. Does anyone have the file or instructions how to do this? I found instructions for the oneplus 3 but not sure with this model. I'm sure any help would help out a lot of people who are gonna ask this question.
Also will this unlock the bootloader? Just curious about it affecting android pay.
Thank you!:laugh:

logansrun24 said:
Hi everyone,
I literally just got the Chinese version of the oneplus 3T (A3010) and I want to move from Hydrogen OS 2.5.1 to Oxygen OS 3.5 official with OTA. Does anyone have the file or instructions how to do this? I found instructions for the oneplus 3 but not sure with this model. I'm sure any help would help out a lot of people who are gonna ask this question.
Also will this unlock the bootloader? Just curious about it affecting android pay.
Thank you!:laugh:
Click to expand...
Click to collapse
Wanna do me a favor and grab a nandroid backup of your rom before you kill it? I actually want h2os
Aside from that, you should theoretically be able to: ("Official" guide https://forums.oneplus.net/threads/...oid-efs-backup-and-more.475142/#post-15431571)
Unlock the bootloader
Flash TWRP
Flash dm-verity
Flash OOS 3.5.3 from the ROM page, I have a mirror too (http://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015) mirror on pg 2.
and you'll be set, you can flash the original recovery if it's available on the OnePlus page as well and relock to go back to full stock just English version
PS: Since there is no stock recovery image available yet, maybe will have to run TWRP temporarily, rip the recovery off and then proceed? I dunno

Thanks for your quick reply! I was hoping more along the lines of the adb Sideload method and keep the bootloader locked for now though. If I go the root method sure I can share the nandroid backup.
PS the rom looks really similar to the oxygen rom, so far it looks like only the launcher is different. I guess this is part of the plan to merge the two.

Well you can try flashing the image straight. It's a stock image anyways so it could work.

logansrun24 said:
Thanks for your quick reply! I was hoping more along the lines of the adb Sideload method and keep the bootloader locked for now though. If I go the root method sure I can share the nandroid backup.
PS the rom looks really similar to the oxygen rom, so far it looks like only the launcher is different. I guess this is part of the plan to merge the two.
Click to expand...
Click to collapse
Basically what I meant was to do the opposite of what is suggested here http://forum.xda-developers.com/oneplus-3t/how-to/rom-h2os-2-5-oneplus-3t-released-t3511443 but with the 3.5.3 ROM

Help needed with android pay and OOS clean install
I'm in a similar situation with a chinese bought OnePlus 3G from Lazada.sg that came with Hydrogen OS. I've managed to install TWRP but because I'm completely new, got stuck and instead managed to install OOS 3.5 (now 4.## from the official website) using adb sideload.
I do have 2 questions:
1) My internet connection drops occasionally even though my WiFi is still connected, is that an issue because I might not have installed it correctly? Would a clean flash solve it?
2) I understand android pay is disabled when you unlock bootloader but even after that, will it be possible to wipe the phone clean and do a fresh install of the lastest OOS and the phone will pretty much be like the international version, with android pay re-enabled?
I believe you can use Sultanxda's patch as another way around, but it sounds complicated as hell for a new person, so I'll continue digging around while waiting for a reply.
Thank you, and any advice will be greatly appreciated.

Questions about TWRP/ROM/ etc

Hello, I'm new to the Xiaomi world and I still have trouble understanding some terms ...
I am currently waiting for the necessary 168 hours before I can unlock my bootloader.
I would like to know what are the differences between orangefox and twrp, which one to choose?
What are the differences between global and eu?
I think I'm in global because I'm in 10.3.2.0
If I root my phone will I be able to update without removing everything?
Thank you in advance.

ImEraaz said:
Hello, I'm new to the Xiaomi world and I still have trouble understanding some terms ...
I am currently waiting for the necessary 168 hours before I can unlock my bootloader.
I would like to know what are the differences between orangefox and twrp, which one to choose?
What are the differences between global and eu?
I think I'm in global because I'm in 10.3.2.0
If I root my phone will I be able to update without removing everything?
Thank you in advance.
Click to expand...
Click to collapse
TWRP is very customisable and as such there are many different versions. Orange Fox is just a very heavily customised version of TWRP. It has a number of additional features over vanilla TWRP, some of which are specific to Xiaomi devices. However there are other versions of TWRP that also have been customised with additional features that are Xiaomi specific, it's just that these other versions are still very much recognisable as a version of TWRP as they keep the same UI design.
I don't think anyone is really sure what differences, if any, there are between the global and EU ROMs, at least from a functionality point of view. It might just be ad delivery and data collection differences, due to the EU having stricter laws around data protection and such things.
If you root you won't be able to use OTA. If you do you will lose root. You will need to manually update by installing the latest recovery ROM followed by Magisk again. (I assume that will be your root solution)

Just use either recovery for now. The only difference is the interface imo. F2fs support is still bad in recovery.
Use miui.eu, it's the same but stripped down and without ads.
Sure, as long as it's a compatible update.
-
I do recommend you backup your Android 9 partitions before flashing. I wiped and installed 10 and cannot go back.

Thank you guys for the infos, I think I'll go with classic TWRP and install the xiaomi.eu rom and then for the root I would reinstall it with each update this is not a problem

Orangefox has the ability to surviving OTA updates if prepared well.
Sent from my Mi 9T Pro using Tapatalk

ImEraaz said:
Thank you guys for the infos, I think I'll go with classic TWRP and install the xiaomi.eu rom and then for the root I would reinstall it with each update this is not a problem
Click to expand...
Click to collapse
If you go with the xiaomi.eu ROM then Magisk will automatically install itself when you update.

Cool Thanks.
And for the TWRP the best actually is the unofficial one from @mauronofrio or there is an official for android p ? Is the last on twrp.me will work ? Thanks

Robbo.5000 said:
[…] followed by Magisk again. (I assume that will be your root solution)
Click to expand...
Click to collapse
Robbo.5000 said:
If you go with the xiaomi.eu ROM then Magisk will automatically install itself when you update.
Click to expand...
Click to collapse
If Magisk is a rooting solution, and if Xiaomi.eu ROM installs Magisk automatically, does it mean If I install Xiaomi.eu ROM, I have no other choice but to root my phone, therefore I won't be able to use OTA updates and will have to update manually each time there is a new ROM ?

Thordelan said:
If Magisk is a rooting solution, and if Xiaomi.eu ROM installs Magisk automatically, does it mean If I install Xiaomi.eu ROM, I have no other choice but to root my phone, therefore I won't be able to use OTA updates and will have to update manually each time there is a new ROM ?
Click to expand...
Click to collapse
I tried to find infos on xiaomi.eu and I don't think magisk is automatically installed

Thordelan said:
If Magisk is a rooting solution, and if Xiaomi.eu ROM installs Magisk automatically, does it mean If I install Xiaomi.eu ROM, I have no other choice but to root my phone, therefore I won't be able to use OTA updates and will have to update manually each time there is a new ROM ?
Click to expand...
Click to collapse
No.
Magisk will automatically install itself if you have already installed it.
This is common behaviour for things like Magisk and GApps. If they've been installed on a custom ROM, they will automatically reinstall themselves when you update that ROM.
Xiaomi.eu does not come with Magisk pre-installed.
You are also confusing OTA updating a rooted phone with an official ROM and with a Xiaomi.eu ROM.
Xiaomi.eu is a custom ROM and so updating it is more like other typical custom ROMs.

[STOCK] Stable realmeUI/Android 10 ROM for RMX1991

Hi folks,
What we used as beta ROM is now published as official stable release known as version RMX1991_11.C.12 for Chinese model of Realme X2.
Probably anyone can upgrade the phone now in any possible way.

The bad news is FP stops working as soon as you patch vbmeta for disabling AVB...

The good news is that there's no verification of system partition. You can leave vbmeta untouched and modify whatever you want except boot.

yakovpol said:
The good news is that there's no verification of system partition. You can leave vbmeta untouched and modify whatever you want except boot.
Click to expand...
Click to collapse
Then, you will not loose fingerprint?

AlAneed said:
Then, you will not loose fingerprint?
Click to expand...
Click to collapse
Exactly

yakovpol said:
Exactly
Click to expand...
Click to collapse
Magisk can be installed and we still have the fingerprint working?

AlAneed said:
Magisk can be installed and we still have the fingerprint working?
Click to expand...
Click to collapse
No, Magisk is patching boot, which will require you to disable verification by means of vbmeta. You can try system-based methods like one of SuperSU.

yakovpol said:
No, Magisk is patching boot, which will require you to disable verification by means of vbmeta. You can try system-based methods like one of SuperSU.
Click to expand...
Click to collapse
but in order to fix twrp replace issue vbmeta verification is needed to be disabled right??

I will try to search for it. Is it just a normal app to install from Play store? or requires other method?
One more thing, TWRP working with it or no?
Thanks
---------- Post added 10th April 2020 at 12:36 AM ---------- Previous post was 9th April 2020 at 11:38 PM ----------
I guess I am not able to understand how to do root? I searched for system base root in the web with no luck
Would you mind explaining how to do root without Magisk?

osamanazim said:
but in order to fix twrp replace issue vbmeta verification is needed to be disabled right??
Click to expand...
Click to collapse
No. At least a few last CN ROM versions are insensitive to recovery replacement. You can keep stock vbmeta and flash custom recovery. But recovery will be replaced when you boot system, i.e. you flash custom recovery for single and immediate use

yakovpol said:
No. At least a few last CN ROM versions are insensitive to recovery replacement. You can keep stock vbmeta and flash custom recovery. But recovery will be replaced when you boot system, i.e. you flash custom recovery for single and immediate use
Click to expand...
Click to collapse
Will i lose any file if i update from color os 6.1 to realme ui or i need to backup first?

Mikelsteven said:
Will i lose any file if i update from color os 6.1 to realme ui or i need to backup first?
Click to expand...
Click to collapse
Backup is a nice thing. I would always insist on creating backup.
I successfully switched onto realmeUI without losing data. As I understand, you have to do it from A.17 (for CN device). My path was A.16 -> C.02, but now many are suggested to upgrade from A.17 straight to C.12.

yakovpol said:
Backup is a nice thing. I would always insist on creating backup.
I successfully switched onto realmeUI without losing data. As I understand, you have to do it from A.17 (for CN device). My path was A.16 -> C.02, but now many are suggested to upgrade from A.17 straight to C.12.
Click to expand...
Click to collapse
Thanks man. I don't know what reliable backup method i can use on an unrooted phone. I'm on A17 so i guess it's safe to upgrade without backup. Again, have u experienced any bug so far on realme ui?

Mikelsteven said:
Thanks man. I don't know what reliable backup method i can use on an unrooted phone. I'm on A17 so i guess it's safe to upgrade without backup. Again, have u experienced any bug so far on realme ui?
Click to expand...
Click to collapse
Put some labour on searching through Internet please. So you will be sure if to update or not
To me it works just fine.

Mikelsteven said:
Thanks man. I don't know what reliable backup method i can use on an unrooted phone. I'm on A17 so i guess it's safe to upgrade without backup. Again, have u experienced any bug so far on realme ui?
Click to expand...
Click to collapse
Black Screen problems while playing COD Mobile. Iit is a common problem on sobre Android 10 upgraded devices.
But all the rest of software running and working smoothly.

can someone please confirm if the feature of Waze returning to top during voice call is working? i have the globalized version by mettis and it doesn't work there (have CN device)

Question is root working on MIUI 13?

I am on the china model M2102K1C with the global rom installed. I rooted using the following method https://forum.xda-developers.com/t/...irmware-download-needed.4301241/post-85282829 which meant not overwriting the recovery and only booting thru the twrp file in my adb folder. This made it possible to get OTAs.
I just got the update available for download message and before I install it I would like to be sure I can re root using the same method and that the twrp version still works on miui 13.
the reason i want to check first is that i remember using other phones that sometimes a major update had necessitated an update for twrp to work with it.

you can root on miui 13 by patching the boot.img , like on all android 12 releases. Due to non working twrp on a12.
So if you want a working TWRP you cant update.. After update to miui 13 it will be a12.
use this link for info: https://xiaomi.eu/community/threads/howto-magisk-install-without-twrp.64511/#post-643958

marcel112 said:
you can root on miui 13 by patching the boot.img , like on all android 12 releases. Due to non working twrp on a12.
So if you want a working TWRP you cant update.. After update to miui 13 it will be a12.
use this link for info: https://xiaomi.eu/community/threads/howto-magisk-install-without-twrp.64511/#post-643958
Click to expand...
Click to collapse
thanks I have rooted several other phones on A12. I might wait until I research a bit more on this one as its my first Xiaomi phone. I was hoping the TWRP made for android 11 would still work on A12. ...or if i can hold off wait until there is a twrp for this phone compatible with A12.

tensux said:
thanks I have rooted several other phones on A12. I might wait until I research a bit more on this one as its my first Xiaomi phone. I was hoping the TWRP made for android 11 would still work on A12. ...or if i can hold off wait until there is a twrp for this phone compatible with A12.
Click to expand...
Click to collapse
idk, i know there are working a12 twrp for mi 10 and 10 pro, but i dont know when and if it will come for 11 ultra. and when it will come... there are no twrp files for yet... if it is only for root, just use pathed boot.img.... its really easy

marcel112 said:
idk, i know there are working a12 twrp for mi 10 and 10 pro, but i dont know when and if it will come for 11 ultra. and when it will come... there are no twrp files for yet... if it is only for root, just use pathed boot.img.... its really easy
Click to expand...
Click to collapse
thanks I know I am going to end up trying it. with the other phones I was more familiar with fixing a soft brick, so that's why I am nervous about it. I already started the upgrade haha.

its nearly impossible to brick this device( i am told, lol)
You can allways reflash using miflash to stock, just be aware off untick lock

marcel112 said:
its nearly impossible to brick this device( i am told, lol)
You can allways reflash using miflash to stock, just be aware off untick lock
Click to expand...
Click to collapse
uggh looks like I am going to need to learn how to use miflash. im not sure what i did. I didnt flash anything but rebooted to system from fastboot, and now the screen is blank. My laptop recognizes enough to beep when i plug and unplug the usb cord, but adb does not see it.

read this https://forum.xda-developers.com/t/global-miui-13-link-added-awesome-update.4410931/post-86528887
adn this https://forum.xda-developers.com/t/new-to-mi-11-ultra-with-rom-problems.4411617/post-86527355

tensux said:
uggh looks like I am going to need to learn how to use miflash. im not sure what i did. I didnt flash anything but rebooted to system from fastboot, and now the screen is blank. My laptop recognizes enough to beep when i plug and unplug the usb cord, but adb does not see it.
Click to expand...
Click to collapse
For some reason it is losing sanity when you have an open BL and twrp etc installed and trying to update to miui13. Just make sure you have a backup.

I have never used MiFlash before. I believe my computer does see the phone. I was on miui_STARGlobal_V13.0.2.0.SKAMIXM_eecc15ab63_12.0. I am not finding a global fastboot rom for A12 (only the full rom).
The previous versions 12.58 does have a fastboot rom available. Using other phones it was not always possible to downgrade. Would it be possible to flash 12.5.8 on this, or will I need to flash the china version of A12 that has a fastboot rom available?

marcel112 said:
you can root on miui 13 by patching the boot.img , like on all android 12 releases. Due to non working twrp on a12.
So if you want a working TWRP you cant update.. After update to miui 13 it will be a12.
use this link for info: https://xiaomi.eu/community/threads/howto-magisk-install-without-twrp.64511/#post-643958
Click to expand...
Click to collapse
Problem is you can use watever boot img or the one from the specific fastboot rom? because I updated to global 13.0.2 and there is no fastboot version available yet and so no boot img

xNAPx said:
Problem is you can use watever boot img or the one from the specific fastboot rom? because I updated to global 13.0.2 and there is no fastboot version available yet and so no boot img
Click to expand...
Click to collapse
also stuck on this issue, do you know which boot image source we use now? i am also on 13,0,2 global and need root...

There is, take a look at the "beta" thread, it has all you need for A13 rooting

munky-head said:
There is, take a look at the "beta" thread, it has all you need for A13 rooting
Click to expand...
Click to collapse
thanks, but can you be a bit more specific, ive been rooting my every android but this is my first Xioami ever so i am new to this.... which beta thread - a beta firmware - higher version which i download and extract to get the boot.img?
thanks

Yes. Whatever version you have installed, you can find a suitable root image from the link:
xdroms
Download xdroms for free. None
sourceforge.net
Then, it's a matter of typing fastboot flash boot rooted_boot.img and fastboot boot rooted_boot.img (with rooted_boot being whatever image you're running).
I'm currently running the latest Global Stable version, so the root I flashed was [ROOT]miui_STARIDGlobal_V13.0.2.0.SKAIDXM_8e7ececfcf_12.0_by_XD

munky-head said:
Yes. Whatever version you have installed, you can find a suitable root image from the link:
xdroms
Download xdroms for free. None
sourceforge.net
Then, it's a matter of typing fastboot flash boot rooted_boot.img and fastboot boot rooted_boot.img (with rooted_boot being whatever image you're running).
I'm currently running the latest Global Stable version, so the root I flashed was [ROOT]miui_STARIDGlobal_V13.0.2.0.SKAIDXM_8e7ececfcf_12.0_by_XD
Click to expand...
Click to collapse
There is also [ROOT]miui_STARGlobal_V13.0.2.0.SKAMIXM_eecc15ab63_12.0_by_XD.7z
Which one is best for the latest Global stable 13.0.2.0? It also says [Root], what does it mean? It is already rooted? As far as I know with the fastboot method you need to patch the boot.img via magisk first and than flash it via adb

It's a pre-patched boot.img file

So we just need to flash it, but which one of the two?

tensux said:
thanks I have rooted several other phones on A12. I might wait until I research a bit more on this one as its my first Xiaomi phone. I was hoping the TWRP made for android 11 would still work on A12. ...or if i can hold off wait until there is a twrp for this phone compatible with A12.
Click to expand...
Click to collapse
I wait to for the TWRP and im happy for that, Miu 12.5.20 is rock stable... All i want for my phone

xNAPx said:
So we just need to flash it, but which one of the two?
Click to expand...
Click to collapse
you got it working?

General [IMG] Boot + magisk patched boot images

Hi, I have decided to gather boot images and magisk patched images to one thread for now. I will try to edit this thread to be up-to-date. You can let me know what could you want next or if anything is wrong etc.
Stock boot.img files (direct links): ​
EU NE2213_11_A.12​
Stock boot.img - link
EU NE2213_11_A.10​
Stock boot.img - link
​Magisk patched boot.img are here a file that can be downloaded (I am using magisk canary usually, but in Magisk, you can change the channel from the canary to stable etc.) - names as the versions come. ​
Below this there are those magisk patched files which you just flash (or boot and then flash directly from the Magisk app) via fastboot ​

Reserved

Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?

HessNL said:
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
Click to expand...
Click to collapse
Apparently not. I have patched that stock boot via magisk, then via fastboot boot <patchedimage.img> booted (and also tested if it actually boots) and when it booted, via magisk app I did "Direct install (recommended)", rebooted and done.

Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it

Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.

HessNL said:
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Click to expand...
Click to collapse
Yes, because this is probably and currently the most secure option to root it as we haven't got twrp available yet.
BuBbLeFIZzY said:
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
Click to expand...
Click to collapse
That's not that you have it early. The phone itself is early in spite of rooting and doing things like rooting, custom recoveries, ROMs etc. I currently can't find boot img for your model, but once I do, I will post it here for you with patched one.

Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future

fozzy056 said:
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
Click to expand...
Click to collapse
You're really welcome, I wanted to unite those currently quite hard rooting stuff!
And yes, I can't wait to see twrp too!

Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.

GeekMcLeod said:
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
Click to expand...
Click to collapse
Not yet unfortunately. Or I don't know about it yet. :/

kouzelnik3 said:
Not yet unfortunately. Or I don't know about it yet. :/
Click to expand...
Click to collapse
Yeah.. I googled a lot last night once I got my phone trying to find it to root it. I need me that extra bit of customization.
Is there a way I can get it from my phone?

what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this

Johnstan725 said:
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Click to expand...
Click to collapse
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone

Johnstan725 said:
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Click to expand...
Click to collapse
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.

g96818 said:
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
Click to expand...
Click to collapse
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?

Johnstan725 said:
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Click to expand...
Click to collapse
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.

g96818 said:
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
Click to expand...
Click to collapse
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?

Johnstan725 said:
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Click to expand...
Click to collapse
Hmmm. Well you should be fine if you patched the boot and let magisk do the install. I only suggested wiping since you said you flashed the img from the bootloader.
You might run into the same problem I have with the 9RT. I too upgraded from color to oos and couldn’t update at all, even though I rooted from the magisk app. I had to wait for someone to make a fastboot rom. I had no problems updating color following my method, but not oos after switching. Hopefully that’s not the case for you.