Database Develop

Update p9 lite nougat ota "s ​​no officials

I was given a link. cronociclope Senior Member
I tested it. 100 for 100 on :cyclops:
It is necessary to return or to be emu 4. (MM).
Have the unlock code. (Bootloader).
Have downloaded the full firmware (2 files) Full-ota-mf-pv that twrp can install.
And have downloaded the firmware update, full full-ota-mf (no pv). (3 files).
pc+ winzip+ twrp (chinois), carteSD,
regard
https://www.youtube.com/watch?v=oTBvz71l4s0&t=1s
So on the pc, with winzip. Because with winrar for me it does not want to transfer large volumes. :
_ Downloaded a firmware emui 5. Full-ota-mf-pv for your device (it's a firmware in two files, which twrp for MM can install).
_______ update.zip and datafull hw-eu.zip
Uploaded emui update 5. Full-ota-mf not written pv and that does not share ota. But we want it. : (this is a firmware in three files).
________update.zip, public file and data hw-eu.zip
_ Open the update file of the pv version and delete the update.app, then open the update of the no pv version, and transfer update.app in the pv version.
Do the same thing with the datafull file hw-eu and data hw-eu.
In the public zip, there is a data folder with the product and system files.
In the zip data hw-eu, there is a data folder with the cust and version.
We can also transfer them.
In the zip data full hw-eu to data / hw_init :cyclops:
_copy your two new .zip files onto the SD card.
_start the phone in recovery twrp MM.
_ Go to wipe, advanced wipe, check all except well-sure sd card, and wipe to wipe.
_allez to install, installed both zip, it will show you two errors ignore them.
_allez to reboot, reboot system.

Hello
in the public zip, there is a data folder with the product and system files.
In the zip data hw-eu, there is a data folder with the cust and version.
We can also transfer them.
In the zip data full hw-eu to data / hw_init

regard
2017.09.20 VNS-L21C432B382 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97161/f1/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97161/f1/full/filelist.xml

B383 was released on Firmware Finder.
Install the OTA one (mb version).

Johnny TDN said:
B383 was released on Firmware Finder.
Install the OTA one (mb version).
Click to expand...
Click to collapse
yes, full-ota-mf
2017.09.21 VNS-L21C432B383 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97303/f1/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97303/f1/full/filelist.xml
and
your pkg install full-ota-mf-pv vns-l21c432b371
2017.03.21 VNS-L21C432B371 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v89798/f2/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v89798/f2/full/filelist.xml

got an ota update b383.
failed at 32%
gg huawei

Johnny TDN said:
got an ota update b383.
failed at 32%
gg huawei
Click to expand...
Click to collapse
strange 32%
with this method, I can even install p10 lite.
can be checked, the update.app that is the good you place in the update.zip
go to wipe before installing update.zip edit this seems important.

2017.08.30 VNS-L31C432B390 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97199/f1/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97199/f1/full/update.zip

If I am rooted and I have TWRP, can I install the update?

I installed update without come back in mm and without reset phone by this steps:
1)flash Hassan twrp recovery
2)download the 3 update file
3)extract update.app from update.zip and from update_full_VNS-L11_hw_eu.zip.
4)With Huawei update extractor extract the image file (system boot vendor cust version misc) from the two update.app and flash It with recovery. The product Image is not falshable, you have to extract this with ext4imageview
5)do a wipe cache and davilk and flash magisk zip to root. Install magisk manager (with the new update b391 i have some problem with supersu)
6)copy the file extract from product Image and data file extract from update_full_VNS-L11_hw_eu.zip and data_full_pubblic.zip in /data and in /product partition with solid Explorer with root permission.
Reboot
It's ok
http://oi63.tinypic.com/29cncx4.jpg

Paolo83 said:
I installed update without come back in mm and without reset phone by this steps:
1)flash Hassan twrp recovery
2)download the 3 update file
3)extract update.app from update.zip and from update_full_VNS-L11_hw_eu.zip.
4)With Huawei update extractor extract the image file (system boot vendor cust version) from the two update.app and flash It with recovery. The product Image is not falshable, you have to extract this with ext4imageview
5)do a wipe cache and davilk and flash magisk zip to root. Install magisk manager (with the new update b391 i have some problem with supersu)
6)copy the file extract from product Image and data file extract from update_full_VNS-L11_hw_eu.zip and data_full_pubblic.zip in /data and in /product partition with solid Explorer with root permission.
It's ok
Click to expand...
Click to collapse
Hello
Hello
ALSO Product.img of update.zip?
Because, he does not want, that's why, I always go to MM.
bad reading sorry,

Chisetdel31260 said:
Hello
ALSO Product?
Click to expand...
Click to collapse
We are not able ti flash product with this recovery, we can try to ask information to Hassan. The solution is to extract product.img with Android ICS JB EXT4 imagefile unpacker and copy the folder in /product with solid Explorer and root permission. It replace the file with the correct attribute. You have to use this metod to copy data folder

Paolo83 said:
We are not able ti flash product with this recovery, we can try to ask information to Hassan. The solution is to extract product.img with Android ICS JB EXT4 imagefile unpacker and copy the folder in /product with solid Explorer and root permission. It replace the file with the correct attribute. You have to use this metod to copy data folder
Click to expand...
Click to collapse
I've already asked him to hassan and he added to install twrp product image, but its not working.
I tried to copy pasted already with a file explorer, but every time, things break. (either with force close parameters, or force close camera, or boot-animation disappears and becomes android).
there is always something wrong.
Yes, we leave from MM everything is ok, clean.

You have to use solid Explorer It works!! With this procedure In five minutes I upgrade to last version

Managed to update to b382.
Seems stable and somehow, the battery is much better o^o

go
time to download, c432b390.
And to transfer everything in the b370 zip, then to go back to c432b160, I installed it correctly.
so this version is emu 5.0.1, patch September 1, version kernel 25 aug and baseband 286.
as you can see.

Updated to b382 vns-l21.
Problem : No notifications on Hangouts. I must go to my friend's chat in order to see the notification.

I have a question for @Chisetdel31260 or @Paolo83 or for whom I can answer it.
Is it still unclear if it is necessary or not the data_full public, which contains this .zip? And how can I add it without errors? Thanks to whoever can guide me :angel:

Doble_f said:
I have a question for @Chisetdel31260 or @Paolo83 or for whom I can answer it.
Is it still unclear if it is necessary or not the data_full public, which contains this .zip? And how can I add it without errors? Thanks to whoever can guide me :angel:
Click to expand...
Click to collapse
Hello
yes, I add it.
you just have to open the folder data / hw_init /
sorry,
for my bad English.
yet I do a great deal of effort.
for that google translator, does not blow up the planet.

Hi Chisetdel, I share this video, which includes the files OEMinfo.zip, Update.zip and Update_data_full.zip modified and ready to install via TWRP directly from EMUI 4.1 for the L21 (C432B382/EMUI 5.0.1) and L23 (C605B372/EMUI 5.0.1): here
Greetings

Found: BLA 9.0.0 Android Pie

Hello, I just found this in the firmware finder app:
(Sadly I can't test this, I have a mate 10 lite)

GedeonTaylor said:
Hello, I just found this in the firmware finder app:
(Sadly I can't test this, I have a mate 10 lite)
Click to expand...
Click to collapse
It's Mate 20 (early beta) firmware. Sadly System is not extractable, so can't explore much. It has 2 system, one contains the folder structure for everything, but only 'app' and 'framework' in system. The other can be unpacked, but I'm guessing it's encrypted. It's only 500mb but 4.x GB unpacked and can't be mounted.
Interesting though, they have unified custs, so it's all included in the same update. And ramdisk/boot is now part of /system rather than its own ramdisk partition.
Do not flash this, you will likely brick badly

Cannot find ramdisk/boot.img from Update.zip

I recently bricked my EVA-AL00 from installing Magisk and I'm using Tecalote's post (https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389) to resolve it.
I downloaded the update zip file (first result on https://pro-teammt.ru/firmware-database/?firmware_model=eva-al00&firmware_page=0), extracted, then used the Extractor software to extract UPDATE.APP. However, the Extractor tool did not show either ramdisk.img or boot.img. Only files are: CURVER.img, EFI.img, PACKAGE_TYPE.img, SHA256RSA.img, VERLIST.img, VERSION.img, crc.img and cust.img.
Could someone please help me find the right file?

george.tian said:
I recently bricked my EVA-AL00 from installing Magisk and I'm using Tecalote's post (https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389) to resolve it.
I downloaded the update zip file (first result on https://pro-teammt.ru/firmware-database/?firmware_model=eva-al00&firmware_page=0), extracted, then used the Extractor software to extract UPDATE.APP. However, the Extractor tool did not show either ramdisk.img or boot.img. Only files are: CURVER.img, EFI.img, PACKAGE_TYPE.img, SHA256RSA.img, VERLIST.img, VERSION.img, crc.img and cust.img.
Could someone please help me find the right file?
Click to expand...
Click to collapse
It must be FullOTA-MF, not OTA-MF, you must first unzip update.zip and then open update.app by Huawei Update Extractor.
You can also download b540 FullOTA from Firmware Finder, see eg
https://forum.xda-developers.com/showpost.php?p=78511904&postcount=1261
IMO, would be better to obtain support if you asked through HWOTA7 thread
Anyway, on my Mega, there are various stock kernels, ramdisks, etc from b535, b539 and b540, including b540 ramdisk patched for Magisk v18.
I've been using it and several other users and it worked fine
https://mega.nz/#F!JwkVyRya!Rb7OUE0z3PEpXBRxGOM-vQ
However, if you recived OTA Patch02 for b540, you will need to patch/install Magisk by checking both Preserving Encryption and Preserving AVB - for b535, b539 and b540 before Patch02, Preserving AVB was not needed. (only Preserve Encryption)
I'm currently back on b535, but with OTA Patch02, you can find on my Mega also its patched ramdisk, but again, because of Patch02, it was needed now to check also Preserve AVB.
If you are already on b540 with Patch02, I"m not sure if its stock ramdisk is the same as for b540 before Patch02 (probably yes, because OTA Patch02 was only few MB)
You can also extract ramdisk from your currently installed firmware directly from Oreo TWRP, go to Advanced, Terminal and use the command
Code:
dd if=/dev/block/bootdevice/by-name/ramdisk of=/external_sd/ramdisk.img
Extracted ramdisk.img will be saved to external SD card.
You can do the same from TWRP also for kernel and system - however, not for data partition (since TWRP lacks support to read encrypted data partition)

Hey please I'm looking for boot _recovery_crc.img

Eteon x said:
Hey please I'm looking for boot _recovery_crc.img
Click to expand...
Click to collapse
Hi there,
Without information about which device you have (model number, Android version, build number, custom version) it is not possible to give you a suitable tip.
It would also be helpful to know why you need a specific image.
Up to Android 7 there was a boot.img and a recovery.img, as well as a recovery2.img.
From Android 8 on there was no longer a boot.img, but instead the ramdisk.img. And for the recovery the so-called recovery_ramdisk.img.
Both images are different for each firmware, which is why precise information is necessary. The images can be extracted from the Update.App.
To do this, the firmware suitable for the device must be downloaded.
A xxx.crc.img is meaningless because it's just a checksum and not an image to flash!

Tecalote said:
Hi there,
Without information about which device you have (model number, Android version, build number, custom version) it is not possible to give you a suitable tip.
It would also be helpful to know why you need a specific image.
Up to Android 7 there was a boot.img and a recovery.img, as well as a recovery2.img.
From Android 8 on there was no longer a boot.img, but instead the ramdisk.img. And for the recovery the so-called recovery_ramdisk.img.
Both images are different for each firmware, which is why precise information is necessary. The images can be extracted from the Update.App.
To do this, the firmware suitable for the device must be downloaded.
A xxx.crc.img is meaningless because it's just a checksum and not an image to flash!
Click to expand...
Click to collapse
I was trying to flash an XML file from a board firmware using IDT and it's showing me that

Eteon x said:
I was trying to flash an XML file from a board firmware using IDT and it's showing me that
Click to expand...
Click to collapse
Your Screenshot shows a Huawei p10 VTR Board firmware.
But this Thread is for P9, not for P10.
Is your device a Huawei P10?
Please ask in the Huawei P10 Forum.
I can't help you with IDT flashing method.
I worked for such cases only with ChimeraTool and sometimes with DC Phoenix. (Both are paid Services)

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.