Database Develop

Marshmallow builds comparison

Hi, everybody.
Sorry if I post this thread in wrong section.
Howewer I hope that this thread would be an aid for thus want to try the different beta builds of our phone.
Ok. So.
1. Dual SIM B170 --- B188 --- (possible 190 or 194) --- B524 --- B550.
- all is fluent.
2. Single SIM B171 --- B525
- all is fluent
- howewer this build cannot upgrade to B550
- seems that developpement freeze at beta build stage (waiting for final build)
- oh, and surprise: You CAN use dual SIM. Yes its true, i flashed over dual sim model (so i guess that this works only on Dual Sim models)
3. Chinese firmware B535 (--- exist the beta build 551, but that doesnt leaked)
- all is fluent
BUT. The BIG difference between these builds is that the Chinese firmware come with MANY more functions, than the others: SmartCare, Camera modes, Barcodes in Messaging, Yellow Pages in Dialer, and so Many others (maybe I would collect them for the whole list)
So I use the Chinese build. With little tweak is wery well usable. You have little areas with chinese options (for example you must change the keyboard from chinese to huawei swype), but it isnt annoying.
Oh, and if you register an huawei account on chinese site, well, you have many other possibilities from this build.
I recommend this build over the others.
P.S. I would make a voting for those builds too but i dont know how (maybe the moderators...)

i have got b150... can i go for b170?

tamaskurti said:
BUT. The BIG difference between these builds is that the Chinese firmware come with MANY more functions, than the others: SmartCare, Camera modes, Barcodes in Messaging, Yellow Pages in Dialer, and so Many others (maybe I would collect them for the whole list)
So I use the Chinese build. With little tweak is wery well usable. You have little areas with chinese options (for example you must change the keyboard from chinese to huawei swype), but it isnt annoying.
Oh, and if you register an huawei account on chinese site, well, you have many other possibilities from this build.
I recommend this build over the others.
P.S. I would make a voting for those builds too but i dont know how (maybe the moderators...)
Click to expand...
Click to collapse
I've read that some are using the chinese version, but i couldn't found info how to get it.
All HowTos und firmware links lead to C432B550 or C432B524 in the end.
Could you post details how to get the chines beta on an european phone?

Norikio said:
I've read that some are using the chinese version, but i couldn't found info how to get it.
All HowTos und firmware links lead to C432B550 or C432B524 in the end.
Could you post details how to get the chines beta on an european phone?
Click to expand...
Click to collapse
Hm. I was sure that was here on xda, but anyway. I would quote.
Hello,
Finally we get EMUI 4.0 on P8 Lite. Few days ago I decided to change the location of my phone ALE-L21 because China goes beta test of 6.0 but with Chinese firmware installed on the B230 on ALE-UL00. And today the new Android 6.0 was successfully installed on my phone!
Cheers
FIRST and foremost you need change the location!!! to
unicomelectric/cn
To install OTA(EMUI 4.0) update is necessary to change your location and the Chinese version of the software B230
So here the OTA B535
Just put update.zip(1.1GB) into dload folder on your SDCard or internal memory!!! Then install as local update!
Guide how to install EMUI 4.0 Android 6.0 ALE-UL00C00B535 on device ALE-L21(P8 Lite)
Requirements
1.Unlocked bootloader
2. Rooted device
How to Change Region of Your Huawei Honor 4C [Root]
You can change the region of your Huawei Honor 4C and gain the ability to flash firmware from other countries by a few tweaks to the files that hold country settings. This step-by-step tutorial will guide you through the entire process and provide you with the files required.
Huawei Honor 4C
1. Requirements
Full root access
ES File Explorer (Root Explorer is not recommended at all!)
Backup of your current stock recovery and custom recovery
Full Nandroid backup of all partitions
OEM Info File (download here)
Warning: Although you might find this tempting, there’s a high chance that you’ll brick your phone in the process. That’s why you’re strongly advised to keep a handy nandroid backup. We hold no responsibility for any kind of damage caused during or after this procedure. You proceed entirely at your own risk!
2. Procedure
Step 1: First of all, find out your current vendor/country info. One way to do this is by dialing *#*#2846579#*#* – from the menu that pops up go to Network Information > Vendor/Country Info. Some of the vendors/countries are:
hw/spcseas – Malaysia
unicomelectric/cn – China
hw/meafnaf – Pakistan
mts/by – Belarus
Step 2: Now that you know your region information, open ES File Explorer and turn “Root Explorer” on from the menu in the sidebar. Select “/” (device) from the bar above and go to “Data”. Open custom.bin using the ES Note Editor. You’ll see the same vendor and country information in this file as you previously saw in engineering mode. Clear the text and insert the text corresponding to the region you wanna shift to. For example, if I were moving from Pakistan to Malaysia, I’d clear “hw/meafnaf” from custom.bin and insert “hw/spcseas” instead.
When you’re done, save the file and make sure its permissions are set to rw-rw-rw in its properties.
Step 3: Now download the OEM Info package from above and extract it. Inside the oeminfo folder, take the oeminfo file of the country you’re shifting to and copy it to [/device]/dev/block/hi_mci.0/by-name/. Replace the file that’s already present in by-name folder. I repeat – replace the file – don’t delete it! Make sure you’re doing this only through ES File Explorer. Make sure this file has rwx rwx rwx permissions.
Step 4: Finally, if you’ve done everything right, reboot your phone and check your vendor and country info again by dialing *#*#2846579#*#* in the dialer.
Step 5: Now you should be able to flash any firmware from the region you now have. In case you’re seeing “balong” in Settings > Update as your version number it means that you now won’t be able to receive any online updates. You don’t really need to worry about it. Simply download the firmware and flash it through the forced SD upgrade method (you know the one – Vol up + Vol down + Power).
______________________________________________________________________
Change location on your device to unicomelectric/cn
a) Copy file oeminfo to internal memory or SD Card
b) Replace oeminfo on path /dev/block/platform/hi_mci.0/by-name with downloaded one. Reboot
Instalation procedure
a) Downgrade to B052(fastboot) make wipe!
b) Install B230(fastboot) Make two wipe!!!
c) Install B535 as local update(put the update.zip on dload folder in internal memory) make wipe!
DONE!
PS: sokkoban was the autor (look at his label):
h t t p : / / huaweip8lite.blogspot . ro

I managed to find the thread, it's a bit messy because the Opening Post is deleted and i had to find all the filse cluttered over the thread.
Installation went quite smooth, but i'm a little bit worried because Model Number says hi6210sft, but that's something i can probably fix inside the build.prop.
so thanks tamaskurti for the info.

You guys think the best firmware is the chineese one ? I have all the files downloaded on my laptop but I doubt in installing it

look at:
h t t p : / / forum.xda-developers.com / p8lite / general / ale-ul00-t3339897

Honestly, i am disappointed with b550 official europe build.
I was on chinese b535 build, witch its beta, howewer, it has lot more functions than the europe builds. I wait for the final marshmallow build from chinese market, because, their rom is more ellaborated than the others. Sorry, huawei europe, but in comparison with chinese market, the final build seems for me that an early beta or alpha build.

Is there a way to get the Chinese version camera app to our phones (meaning official MM update)?

Black Shark 3 Global Android 11

Hello Shark's,
I have managed to get the link for downloading Android 11 OTA.
https://ota-oversea-1256119282.file.myqcloud.com/KLE-H0/20210904132110-klein-deltaota_MK-R-H0_2021-02-02_c0b9b6c8fc.zip
You can update the phone to MR0 from MP4 or MP3 by following the steps below.
1) Copy the downloaded file to Phone Storage
2) Create a new folder called ota on the root of the storage
3) Inside ota folder copy the downloaded zip file
4) Rename the zip to update.zip
5) Go to dialer
6) Enter *#*#1027#*#* code. Thanks to wertus33333
7) Press Local Update and Wait.
In order to Root the Shark 3 with Global Android 11 follow the steps below.
Perquisites
1) Unlocked Bootloader. Follow this guide.
Rooting Black Shark 3 / 3 Pro the Correct & Easy Way - BL Unlocking, TWRP & OTA Fix
Rooting Black Shark 3 / 3 Pro the Correct & Easy Way - BL Unlocking, TWRP & OTA Fix Greetings fellow Black Shark users! This guide is made for Black Shark 3 Pro Global version, but in theory it should work with any version if the bootloader is...
forum.xda-developers.com
2) Platform tools on Windows or Mac
3) Basic Knowledge and confidence
* All data will be erased so backup before you do anything.
Steps
1) Download this file and extract it.
https://ota-oversea-1256119282.file.myqcloud.com/KLE-H0/20210904132110-klein-deltaota_MK-R-H0_2021-02-02_c0b9b6c8fc.zip
2) Use Payload dumper by ssssut to extract the boot.img from Payload.bin
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
3) Patch boot.img using Magisk.
4) Go to Fastboot
5) Flash the patched boot.img using
fastboot flash boot boot.img
6) Done

if you don't have stock recovery with the exact same version with your ROM (exp. MP4 ROM with MP4 recovery), the 1027 method won't work, it will give error 20 or something.

slashyuz6 said:
if you don't have stock recovery with the exact same version with your ROM (exp. MP4 ROM with MP4 recovery), the 1027 method won't work, it will give error 20 or something.
Click to expand...
Click to collapse
True it won't work but I have solution for that as well but I am afraid the firmware is paid so I won't be able to share here.

Hey man thanks for the sharing this, i was wondering i have the KLEN2110261CN00MR3, it this rom the global one or the CN00MR0?
Thanks in advance

can you share boot.img of S00MR0 ?

Can someone extract boot and recovery?

arjun_m4 said:
Hello Shark's,
I have managed to get the link for downloading Android 11 OTA.
https://ota-oversea-1256119282.file.myqcloud.com/KLE-H0/20210904132110-klein-deltaota_MK-R-H0_2021-02-02_c0b9b6c8fc.zip
You can update the phone to MR0 from MP4 or MP3 by following the steps below.
1) Copy the downloaded file to Phone Storage
2) Create a new folder called ota on the root of the storage
3) Inside ota folder copy the downloaded zip file
4) Rename the zip to update.zip
5) Go to dialer
6) Enter *#*#1027#*#* code. Thanks to wertus33333
7) Press Local Update and Wait.
In order to Root the Shark 3 with Global Android 11 follow the steps below.
Perquisites
1) Unlocked Bootloader. Follow this guide.
Rooting Black Shark 3 / 3 Pro the Correct & Easy Way - BL Unlocking, TWRP & OTA Fix
Rooting Black Shark 3 / 3 Pro the Correct & Easy Way - BL Unlocking, TWRP & OTA Fix Greetings fellow Black Shark users! This guide is made for Black Shark 3 Pro Global version, but in theory it should work with any version if the bootloader is...
forum.xda-developers.com
2) Platform tools on Windows or Mac
3) Basic Knowledge and confidence
* All data will be erased so backup before you do anything.
Steps
1) Download this file and extract it.
https://ota-oversea-1256119282.file.myqcloud.com/KLE-H0/20210904132110-klein-deltaota_MK-R-H0_2021-02-02_c0b9b6c8fc.zip
2) Use Payload dumper by ssssut to extract the boot.img from Payload.bin
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
3) Patch boot.img using Magisk.
4) Go to Fastboot
5) Flash the patched boot.img using
fastboot flash boot boot.img
6) Done
Click to expand...
Click to collapse
この方法でboot.imgを抽出しようとしましたが、データが0KBでルートできません。
Mod Edit: English Translation Below
I tried to extract boot.img this way, but the data is 0KB and cannot be rooted.

@natsume.port
Spoiler: English / 英語
Hi! I see that you're new here. Welcome to XDA! Please note that XDA is an international forum, and hence only English is permitted to be used across the website.
The above is as per the Forum Rules:
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
Click to expand...
Click to collapse
As a courtesy, I've added the English translation to your post. Going forward, kindly use English to post/reply on the forum.
Regards,
shadowstep
Forum Moderator
Spoiler: Japanese / 日本
こんにちは！ あなたはここで新しいようです。 XDAへようこそ！ XDAは国際フォーラムであるため、Webサイト全体での使用は英語のみに許可されていることに注意してください。
上記はフォーラムルールによるものです。
4。英語を使用してください。
国籍が違うので、英語が上手に話せるわけではないので、ぜひお試しください。 本当に英語で投稿できない場合は、オンライン翻訳者を使用してください。 英語の翻訳の下に、元のメッセージを自国語で自由に含めることができます。 （このルールは、投稿、プロファイルエントリ、および署名を対象としています）。 次のことを試すことができます:- https://translate.google.com/またはhttps://www.babelfish.com/または、いずれかを使用してください。
Click to expand...
Click to collapse
礼儀として、私はあなたの投稿に英語の翻訳を追加しました。 今後は、英語を使用してフォーラムに投稿/返信してください。
よろしく、
shadowstep
フォーラムモデレーター

The update has arrived.

Oh my God! I used the payload dumper to dump recovery.IMG flashed it, then re locked the phone, so I could update it with the OTA. However, afterwards it wouldn't boot, so I unlocked it, and now I'm locked out of my own phone. It says I have to activate it and asks for a password to an account I don't recognize. I've tried everything I can think of I've watched every YouTube video that that deals with this issue sort of, most of which I can't understand and most of them that I can understand are fake. Any thoughts on that? Looks like I'm going to have to buy a new phone.

fayherwingnut said:
Oh my God! I used the payload dumper to dump recovery.IMG flashed it, then re locked the phone, so I could update it with the OTA. However, afterwards it wouldn't boot, so I unlocked it, and now I'm locked out of my own phone. It says I have to activate it and asks for a password to an account I don't recognize. I've tried everything I can think of I've watched every YouTube video that that deals with this issue sort of, most of which I can't understand and most of them that I can understand are fake. Any thoughts on that? Looks like I'm going to have to buy a new phone.
I think Your talking about Mi Account. There is paid service to unlock it.
Click to expand...
Click to collapse

How To Guide [Guide] MIUI Battery Optimization Whitelist - MIUI 12

Namaste friends! Today we will learn how to remove Xiaomi's apps from Android's native battery optimization function also known as 'Doze' and how to optimize the whole MIUI further more for acute battery and performance optimization too.​
Note: Please continue on your own risk. I will never be held responsible for anything you cause to your device. As I've never experienced any minor / major issues after the process explained here in this post. So, proceed on your own risk.
This process is extensively tried and tested multiple times with multiple MIUI release versions on a same single device running a global version of MIUI 12.5 and so. The device underwent in this process is Redmi 9 Power (India). Let's not waste time for modding our device to our own need.
Requirements: A Xiaomi device having root and unlocked bootloader with a custom recovery (TWRP/else) installed on it. A good root file manager, in my case it is MixPlorer.
Let's begin​
Clean flash your ROM (Recovery or Fastboot, make sure the bootloader is unlocked after the flash) .
Reboot to recovery and flash Magisk Pathed Boot.img of the ROM you just flashed.
Format and reboot to system.
After boot, proceed with installing Magisk apk followed by MixPlorer.
Launch MixPlorer > goto /root folder > grant root (Magisk PopUp) .
Go to /system/xbin and delete all files in there. (these files do something at device boot-up and patch something before the lock screen appears) .
Again in /system/etc/sysconfig delete the xmls that include 'Xiaomi app names' with "allow-in-power-save" tag. You can also rename the xml file extention to anything other than xml that will also work like they are deleted or not there. ( XMLs like - miui core, miui-whitelist, power save config etc. Please open the xmls and verify before modifying the same )
Now head to /system/etc/permission, delete XMLs with "Facebook" names. You can also review some more XMLs in there as I found and patched some more XMLs including "allow-in-power-save" followed by mi apps.
If supported, go to /product/etc/sysconfig and rename google.xml to google.bak for gms to be optimised on next reboot.
Now debloat: Delete apps and their corresponding files in the same folder where apps are. Do not delete the folder only delete the apk and its dll or odex / vdex files. ( Never delete Find device, Mi account, Security etc.)
Now when done, reboot to recovery > format data > reboot to system.
to be continued...

How To Guide (Guide) Rooting, payload dumper, magisk_patched guides NE2213

Hi all,
Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself
Please read the process before committing to proceeding, so you know what's required and what you should and shouldn't use!
Stock and patched images are UK/ EU NE2213 but the guides are universal and could be used on multiple devices.
NOTE:
For these guides the versions used are:
Stable, Canary or BETA depending on firmware, simply change the channel in Magisk settings then select install / update:
NE2213_11_A.12
Magisk Manager v24.3 (24300) Stable
NE2213_11_A.13
Magisk Manager v24.3 (24300) Stable
NE2213_11_A.14
Magisk Manager v25 (25000) Stable this version retains root after a restart, more stable version over previous iterations.
NE2213_11_A.16
Magisk Manager v25.2 (25200) Stable
NE2213_11_C_20
Magisk Manager v25.2 (25200) Stable
NE2213_11_C_21
Magisk Manager v25.2 (25200) Stable
NE2213_13.1.0.520 (EX01)
Magisk Manager v26.1 (25200) Stable
Oxygen OS NE2213_13.1.0.521 (EX01)
Magisk Manager v26.1 Stable
1st
Extracting a boot.img using Fastboot Enhance
Pre-requisites
A device with a working version of magisk manager installed, simply change the channel to the version outlined in the list above relevant to your firmware then select install / update:
A Windows 10 computer / laptop
A full update downloaded firmware zip for your model (recommend oxygen updater)
Payload dumper program for Windows.
An unlocked bootloader.
The local System Update Installer : normal local system update will not allow a reboot during installation, the one I've linked will.
Process
On your computer
1. Download and copy the fastboot enhance folder to your desktop or a location of your choosing.
Download from here: https://github.com/libxzr/FastbootEnhance/releases
2. Download the firmware of your choice (always use full zips, not incremental) and open it using Winrar or a similar zip program, extract the file called payload.bin to a folder of your choosing.
3. Run the program FastbootEnhance.exe, a window will appear, click Payload Dumper, then click browse and point to the payload.bin file, the contents of that payload.bin will now be shown, bare in mind you'll need to check the box "Allow incremental" even if it's a full zip
4. One of the files will be called boot.img, this is the file we'll be patching, click extract then copy this to your phone, root of storage which is called /sdcard.
On your phone
5. Open up Magisk and click Install / Update, if you don't see update then change channel, do this by changing the channel in magisk settings, it'll then show the install/ update buttons.
6. Select "Select and Patch a file" it'll open up a file browser, navigate to the boot.img you copied earlier and select it, allow it to complete (this will output a file called "magisk_patched" which will be output into the Downloads folder)
You now have a patched boot.img ready to boot or flash to either slot with fastboot or boot via fastboot.
I would recommend booting as this is risk free, if it's a bad image for whatever reason and you choose to flash then your phone will bootloop.
NOTE** Some people have noticed that an already patched boot.img when flashed can fail and cause a boot loop when flashed, so if you have downloaded a magisk_patched img from somewhere else then you WILL need to re-patch it on your own device preferably using the afore mentioned magisk manager based on what firmware it's from.
If you intend to follow the guide below with your own patched img then you shouldn't need to patch it twice but it won't hurt if you do.
2nd
Update from XX stable to XX+ stable whilst retaining root
Guide
**NOTE- Although this may work, the system may be unstable, especially when changing bases, eg: Android 11-12 or 12-13, so if you encounter strange behaviour then a factory wipe is advised.
1. Download the relevant firmware for your device via oxygen updater
2. Open Magisk and remove all the modules you have installed, then reboot
**NOTE- At this point I tend to copy out the whole firmware to my computer, incase I need it in the future, the boot img and patched boot img are at the foot of this guide, I'll always upload the latest firmware as soon as it comes out for the UK/EU model
3. Install the OnePlus local install apk listed below in downloads. Click the cog and select "Local Upgrade" the file should be listed on screen, if not then move the file to the root of your phones storage.
4. Click install and allow it to go through the process
**NOTE- DO NOT REBOOT AT THIS POINT YOU WILL LOSE THE ABILITY TO PATCH ON THE FLY, SIMPLY BACK OUT OF THE SCREEN WHICH SAYS "INSTALLATION COMPLETED. RESTART TO EXPERIENCE NEW FEATURES"
5. Open up magisk and click install (you may see two install buttons, top one is magisk and the bottom is magisk manager, we need the top one)
6. You'll be faced with a screen that has several options, you want to select "Install to Inactive slot (After OTA)" then select "LET'S GO" once complete click reboot.
7. Once your phones booted back up your system / files should all remain as they were and you should have root access.
You can now install all your modules again so long as they're compatible with the firmware you've just updated to.
3rd
Rooting using fastboot commands
Method 1
Booting the patched image
1. Obtain a patched boot image for your device variant preferably using payload dumper or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - The above suggested downloads are for the EU / UK variant- if you have another model / firmware please use that instead, If you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager to avoid a bootloop, if you still get a bootloop it's best to obtain one yourself using the guide at the top of this post.
2. Reboot your phone to fastboot
and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img)
Your phone should now boot automatically, you should now be rooted but we need to make this permanent, if you were to reboot you would lose root.
4. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings and install the update, the buttons should then show.
5. Select Direct install (recommended) then click ok.
6. Allow magisk to permanently root your device then click reboot.
You should now boot and remain rooted.
Method 2
Flashing to both slots
1. Obtain a patched boot img for your device variant or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - Again the above suggested downloads are for the EU/ UK variant- if you have another model / firmware please use that instead, if you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager, to avoid a bootloop
2. Reboot your phone to fastboot and connect to your computer.
Command: adb reboot bootloader
3. Open a command prompt on your computer and navigate to your ADB/fastboot folder.
4. Type the following.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
fastboot reboot
Press enter
6. Your phone should now boot, open magisk and verify you're rooted.
Troubleshooting
If flashing succeeds but you don't have root and you've followed all the instructions, you may have some magisk modules still active, try performing the following.
1. Connect your phone to your computer.
2. Reboot the phone, then during the boot animation enter this command via ADB.
adb wait-for-device shell magisk --remove-modules
3. Allow to boot, modules will be removed and root should then be active.
If there is no magisk install / update buttons.
1. Make sure you have granted permission to magisk in settings / apps / magisk / permissions
2. Make sure that the update channel is on canary, then force close magisk and then re-open
3. If it still doesn't work then update magisk using canary
4. Last method to check would be to change to the beta channel in magisk settings, then install it.
Or change the update channel, install the version on offer, then change back to canary, install and you should be good to go.
Window's version
Windows 7 will not work with fastboot, please use Windows 10
USB
Use USB 2.0 not 3.0 or 3.1
ADB
These are the files i use for ADB (in the below list) tested these on fresh installs of windows on several windows machines, all win 10
Place them into the root of C so it reads C:\ADB much easier to navigate to that way.
Bootloader unlock
Boot to the bootloader with adb reboot bootloader
type fastboot flashing unlock
Agree to unlock - allow to boot.
If you can't see the device using ADB
Make sure USB Debugging is turned on
Connect your cable to your phone and computer, when asked what you want your phone to do, click on transfer files, a driver will be installed.
After this reconnect your phone and it'll prompt you with a disclaimer with a check box, check the box and click ok, ADB / Fastboot should now work.
Files:
Local System update APK, this must be used as the local OnePlus 10 Pro one will not allow a reboot during the installation, so you cannot install the Magisk boot image during an upgrade, the android 13 local update apk is also required for rolling back to android 12.
Android 13 local update apk
3.27 MB folder on MEGA
mega.nz
Android 12 local update apk
3.27 MB folder on MEGA
mega.nz
ADB Files for Windows 10:
7.69 MB folder on MEGA
5 files
mega.nz
Payload dumper program for Windows-
https://mega.nz/folder/vU00FZDa#PIEfjl5w5wonyNAwHW3FBQ
Oxygen OS NE2213_11_A.12 Stock boot image
0 byte folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.12 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.13 Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.13 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.14 Stock boot image
384 MB folder on MEGA
2 files
mega.nz
Oxygen OS NE2213_11_A.14 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.16 Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.16 Patched boot image
192 MB folder on MEGA
mega.nz
Android 13
Oxygen OS NE2213_11_C_20 Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_C_20 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_C_21 Stock boot image https://mega.nz/folder/LNVxTDYA#yly9xpjFjQhe4De_jqyzbw
Oxygen OS NE2213_11_C_21 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.520 (EX01) Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.520 (EX01) Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.521 (EX01) Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.521 (EX01) Patched boot image
192 MB folder on MEGA
mega.nz

Glad to see you here bro with the 10 Pro and helpful guide's!!
Cheers

galaxys said:
Glad to see you here bro with the 10 Pro and helpful guide's!!
Cheers
Click to expand...
Click to collapse
Slowly coming around to this phone mate, we desperately need a few custom ROMs..
EvoX on this would be phenomenal.
Nudge nudge @AnierinB

UPDATE: First patched boot image is up, using the latest stable Magisk v24.3 (24300)

dladz said:
Slowly coming around to this phone mate, we desperately need a few custom ROMs..
EvoX on this would be phenomenal.
Nudge nudge @AnierinB
Click to expand...
Click to collapse
Yeh, it's early but hopefully a few Developer's will get this badboy device!

Thank you thank you THAAAANK YOOOOUUUU

meowmeowpewpew said:
Thank you thank you THAAAANK YOOOOUUUU
Click to expand...
Click to collapse
Lol welcome mate

meowmeowpewpew said:
Thank you thank you THAAAANK YOOOOUUUU
Click to expand...
Click to collapse
I honestly hope so..
I'm having a few issues isolating the correct files to make the center clock Magisk mod, but that's in the works. Will have it done soon hopefully.
OnePlus thought it would be a good idea to get rid of OPSystemUI.apk in place of systemui.apk so maybe more in line with stock android. But we'll see

@galaxys as if my prayers were answered, joined the Evo X TG group and there is now a OnePlus 10 group so it's in the works, seriously hope it's AnierinB, he did so well with the 8 pro.
Literally cannot wait

dladz said:
@galaxys as if my prayers were answered, joined the Evo X TG group and there is now a OnePlus 10 group so it's in the works, seriously hope it's AnierinB, he did so well with the 8 pro.
Literally cannot wait
Click to expand...
Click to collapse
Hey that's great news and something to definitely look forward to!
Cheers

Very happy to see guides! Nice, thank you so much !

dladz said:
@galaxys as if my prayers were answered, joined the Evo X TG group and there is now a OnePlus 10 group so it's in the works, seriously hope it's AnierinB, he did so well with the 8 pro.
Literally cannot wait
Click to expand...
Click to collapse
I cannot find that Evo X 10 Pro channel, have you got a link?

kouzelnik3 said:
I cannot find that Evo X 10 Pro channel, have you got a link?
Click to expand...
Click to collapse
If you have telegram just search for evo x up the top, you'll see the main channel.
The the other is in that, i'm just in the middle of something, i'll send it once i'm done.

kouzelnik3 said:
I cannot find that Evo X 10 Pro channel, have you got a link?
Click to expand...
Click to collapse
Evolution X - OnePlus 10 Series
Telegram: Contact @EvolutionXOnePlus10
t.me

Macke93 said:
Evolution X - OnePlus 10 Series
Telegram: Contact @EvolutionXOnePlus10
t.me
Click to expand...
Click to collapse
Oh I've found it.

Hello All,
Very many thanks for your guide. It really helped me root my OP 10 PRO
I was wondering if it is possible to flash my OP ColorOS with OxygenOS EU/UK version you have uploaded?
I copied the 02b0d1b2508744e3a41115aeb274cccf.zip to the root folder and I tried installing via Oxygen Updater using the automatic method, but it fails every time.
If I try installing it manually, I have to download the Oxygen Updater via oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk.zip and rename to .apk. - I then launch System Update , click on settings and it says 'Move installation package into root directory' (which it is).
Have I missed a step?

kouzelnik3 said:
Oh I've found it.
Click to expand...
Click to collapse
Ah was just about to post it mate.
Glad you found it, it's only new but that fact that it's here is brilliant . I'm hoping AnierinB is the dev who makes the rom for the 10.

Lynxy0 said:
Hello All,
Very many thanks for your guide. It really helped me root my OP 10 PRO
I was wondering if it is possible to flash my OP ColorOS with OxygenOS EU/UK version you have uploaded?
I copied the 02b0d1b2508744e3a41115aeb274cccf.zip to the root folder and I tried installing via Oxygen Updater using the automatic method, but it fails every time.
If I try installing it manually, I have to download the Oxygen Updater via oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk.zip and rename to .apk. - I then launch System Update , click on settings and it says 'Move installation package into root directory' (which it is).
Have I missed a step?
Click to expand...
Click to collapse
Honestly mate i'm not sure, you're essentially changing region.
Have you looked into fastboot enhanced?
You can obtain the firmware from oxygen updater (it's 4.15GB the one i uploaded is only the boot image and patched boot image)
Then copy it to your computer and allow it to flash to your phone.
This isn't without risk mate and i've not done this before myself.

dladz said:
Ah was just about to post it mate.
Glad you found it, it's only new but that fact that it's here is brilliant . I'm hoping AnierinB is the dev who makes the rom for the 10.
Click to expand...
Click to collapse
I am hoping too, because in this state oxygen os in this device is bad. Yeah, it is quite new, but hey, it is halfly baked. And not only evo x, but other ROMs I hope will come.

dladz said:
Honestly mate i'm not sure, you're essentially changing region.
Have you looked into fastboot enhanced?
You can obtain the firmware from oxygen updater (it's 4.15GB the one i uploaded is only the boot image and patched boot image)
Then copy it to your computer and allow it to flash to your phone.
This isn't without risk mate and i've not done this before myself.
Click to expand...
Click to collapse
Thanks for your swift reply. I will wait until there is a verified method. For now, I will tread lightly with the rooted version hehe

Question Twrp on samsung a33

Ive been searching for ages and still havent found how to install twrp on my a33, is it even possible? Im trying to root my a33 with magisk but i need twrp. Im stuck and i dont know what to do

I've rooted through Odin by following this post https://forum.xda-developers.com/t/are-these-rooting-guides-for-the-samsung-a33-5g-good.4475163/ but I'm waiting for TWRP to install custom rom too...

ive rooted my phone with magisk by using odin and a patched ap file by magisk, i installed my official software back because magisk kind of slowed down my devices, but now im waiting for twrp so i can install lineage os

Is TWRP the onl way to install lineage OS?

yes i guess

Dryfty said:
ive rooted my phone with magisk by using odin and a patched ap file by magisk, i installed my official software back because magisk kind of slowed down my devices, but now im waiting for twrp so i can install lineage os
Click to expand...
Click to collapse
how do you want to install Lineage OS? There is still not version of Lineage for A33

you can only get lineage on a33 if you have twrp but a33 doesnt "support" twrp

Dryfty said:
you can only get lineage on a33 if you have twrp but a33 doesnt "support" twrp
Click to expand...
Click to collapse
there is an experimental version of TWRP working, I am using it

Arcangel3 said:
there is an experimental version of TWRP working, I am using it
Click to expand...
Click to collapse
on the a33? can you explain how to install it

Dryfty said:
on the a33? can you explain how to install it
Click to expand...
Click to collapse
attached to you here. Bear in mind it is experimental, but it might work
EDIT: deleting it because it is unstable version, a stable version will be released soon by @Zillion (no pressure )

Arcangel3 said:
attached to you here. Bear in mind it is experimental, but it might work
Click to expand...
Click to collapse
Hey, thanks for sharing! Could you say what's the best custom ROM for this device for the moment? Or where is the list of ROMs? thanks!

vovaxxxx said:
Hey, thanks for sharing! Could you say what's the best custom ROM for this device for the moment? Or where is the list of ROMs? thanks!
Click to expand...
Click to collapse
there is none yet.
But some poeple said that stock ROM for A33 is good enough to not need a custom ROM.

Arcangel3 said:
attached to you here. Bear in mind it is experimental, but it might work
Click to expand...
Click to collapse
Give credits to the guy that made it

Zillion said:
Give credits to the guy that made it
Click to expand...
Click to collapse
I am not sure who made it, was it you? hehe

Dryfty said:
Ive been searching for ages and still havent found how to install twrp on my a33, is it even possible? Im trying to root my a33 with magisk but i need twrp. Im stuck and i dont know what to do
Click to expand...
Click to collapse
bro try this way to root
I want to root my A12 but it not work for my phone.please send me a latest version for A127FXXU7BVI1 isBaseband version
I want to root my A12 but it not work for my phone.please send me a latest version for A127FXXU7BVI1 isBaseband version
forum.xda-developers.com

Arcangel3 said:
I am not sure who made it, was it you? hehe
Click to expand...
Click to collapse
Yup, it got its reasons to not be released.

Zillion said:
Yup, it got its reasons to not be released.
Click to expand...
Click to collapse
should I delete it?
Do we have any better version now?

@Zillion any progress with a relesable version???

Arcangel3 said:
@Zillion any progress with a relesable version???
Click to expand...
Click to collapse
I don't own A33 and I don't know how to make any progress on this :c

I managed to get the Lineage OS "Light" GSI version by AndyYan https://forum.xda-developers.com/t/gsi-13-lineageos-20-light.4509315/ and it works well, but the process to install it is pretty involved and if you do anything wrong, you can easily soft-brick your phone. This process should also work for other gsi roms
First Download the Latest Version of Lineage OS "Light", of which the download link can be found in the thread above or here https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-light/ (There are three versions, vS "Vanilla with Superuser installed" vN "Non-SU Vanilla" and gN "Non-SU with GApps") If you want root, I suggest choosing one of the Non-SU versions and patching the stock AP tar with Magisk before starting this process as the Superuser version provides you a generic superuser app and installing magisk with it greets you with a abnormal state message every time you launch the Magisk Manager.
Second: Unpack the downloaded tar file using 7zip if on windows or with the tar command on linux, and then rename the unpacked .img file to system.img
Third: Get the stock firmware for your device using samloader or some other Samsung firmware downloader and unpack the archive file you get to a directory
Fourth: Unpack the AP tar file, you should get a bunch of files in .img.lz4 format.
Fifth: Find the super.img.lz4 file and decompress it using https://github.com/lz4/lz4/releases and this command
Code:
lz4.exe -d super.img.lz4 super.img
From this point onwards you are better off on linux (I've only tested this on Ubuntu WSL so far), if you're on windows 10+, I suggest enabling Windows Subsystem for Linux and downloading and running the Ubuntu distro from the Microsoft store, you can google how to do that.
Sixth: Within Linux (Ubuntu in my case), install the "android-platform-system-core" package using your preferred package manager (I know that package is available on Ubuntu, but I haven't researched whether any other linux distro has that package available). The main thing we want from that package is the shell script "simg2img" as the super.img is currently sparsed (compressed using the Android Sparse image format).
Seventh: If you already did the steps so far in Linux, just go to whatever directory you have the super.img stored, otherwise if you did everything in windows and have a Ubuntu WSL distro ready, you can copy the super.img directly into the ubuntu distro by going into file explorer and scrolling all the way to the bottom of the navigation pane till you see Linux, of which you can expand to find a Ubuntu network share folder, expand that and drag and drop the super.img into your root folder, as well as the system.img file (renamed gsi rom file).
Eighth: Unsparse the super.img using the command:
Code:
simg2img super.img *whatever*.img
This will give you a raw disk image of super.img that's about 9-10 gb. You can name the output file to whatever you want as long as you can discern which img is which, in fact after running the command you can delete the original as you no longer need it.
From here is where the process gets a bit tricky and I fully recommend reading through this guide: https://forum.xda-developers.com/t/...are-binary-3-may.4053065/page-4#post-82241115
Ignore the fact that the thread is for the Galaxy a51 as the steps work for the a33 as well. When you get to the point where you've unpacked the Super.img, copy the GSI system.img over the stock one.
Now the part that can easily cause you to mess up is that when repacking super.img, you have to get the size of each file, including the unsparsed super.img and input the size in bytes of each file in place of what is given in the long command used to repack the image. The numbers you have to change are as follows:
--device super:4294967296 (Change to the file size of super.img)
--group main:4293513600 (Calculate the sum of the size of each of the .img files that were contained in the super.img, minus product.img as that's not needed)
--partition vendor:readonly:342155264:main (Change to the byte size of your vendor.img, same goes for system, odm and vendor_dlkm. Not sure if vendor_dlkm is required as it's not shown in the guide, but just to be safe, I'd recommend adding that in the same format as shown above for vendor just change vendor to vendor_dlkm)
File sizes can be acquired using the command:
Code:
ls -l
Another thing to note is that all of the file sizes must be divisible by 512 as that's the block size the img uses, if they all are, then you're good to go, if one or more aren't you're probably dealing with a corrupt file or that one of the img files is sparsed or compressed in some way. Once you've confirmed the file sizes are good, run the command. You can ignore the "Invalid sparse file format at header magic" message as it doesn't seem to mean anything bad for the process. You don't have to worry if the sparsed image file size is divisible by 512 as it more than like won't be evenly divisible as the file is compressed now.
Once that's done you can take the new modified super.img (make sure it's named that) out of the linux distro and back to windows.
Recompress the super.img back into super.img.lz4 using the command:
Code:
lz4.exe -B6 --content-size super.img super.img.lz4
Now package the super.img.lz4 file with all of the other files from the AP back into a tar file, I suggest using the tar-md5-script-tool.zip from this thread https://forum.xda-developers.com/t/...sing-odin-without-twrp-phh-lineageos.4114435/
At this point, you can skip to step 24 on that guide and continue from there to install the custom rom, just remember to use super.img.lz4 instead of system.img.ext4.lz4, also ignore the .ext4 part, I think that's a device specific thing and the a33 from what I know doesn't have that.
Once you're done and you've booted up after flashing with ODIN, you should be greeted with the lovely Lineage OS Boot Screen
Bare in mind this is a barebones rom and many features may not work as intended since it's an unofficial build of Lineage OS and is intended to work with many devices without too many issues.