Database Info

[ROOT] Samsung galaxy J2 Prime - G532G (G532GDXU1APL1)

Hi
I created root method for the last version of samsung J2 Prime G532G - G532GDXU1APL1.
It based on modified stock recovery with custom keys (mine), which allow to install a special zip that signed with those keys.
This method include's a patched boot.img (sepolicy), in order the root work properly. (this is normal system root - not systemless, and from Android 6.0 or samsung 5.1.1 and above need also pathed boot)
The phone must be with G532GDXU1APL1 version, or it wont work.
It can be downloaded from here
G532GDXU1APL1
Instructions:
Download this file, and extract it to some folder.
G532GDXU1APL1_root_by_avicohh
Open odin and flash the .tar file inside the folder (In AP).
This file contains the custom recovery, a patched boot, and an empty cache.img in order the phone will restart to recovery after flashing.
In recovery choose "Apply update from ADB".
Run the .bat script file from the "SuperSU sideload installer" folder.
Wait until it finish, the phone will restart automatically with SuperSU inside.
Good luck!
Credits:
@Chainfire for SuperSU
@osm0sis for AIK
P.S. (for devs)
This method can be modified to another build / device, by patching the sepolicy inside boot.img (see here), and replacing the res / keys file inside the recovery.img with my keys. (Attached)
You can unpack and repack boot and recovery images with this tool. (It recomanded to this on linux in order to keep the files permissions)
The stock recovery doesn't support the standart SuperSU installer bacause it bash script, so i wrote another one in Edify. (this zip should work on any device with android 5.11 - 6.0.1 and armv7)

I am waiting new method root for G532G (G532GDXU1APL1)
Now..
great work ,,thanks bro .......I 'm so happy .....

Manual instruction recovery_custom_keys.7z ??? thank
---------- Post added at 02:11 PM ---------- Previous post was at 02:07 PM ----------
avicohh said:
Hi
I created root method for the last version of samsung J2 Prime G532G - G532GDXU1APL1.
It based on modified stock recovery with custom keys (mine), which allow to install a special zip that signed with those keys.
This method include's a patched boot.img (sepolicy), in order the root work properly. (this is normal system root - not systemless, and from Android 6.0 or samsung 5.1.1 and above need also pathed boot)
The phone must be with G532GDXU1APL1 version, or it wont work.
It can be downloaded from here
G532GDXU1APL1
Instructions:
Download this file, and extract it to some folder.
G532GDXU1APL1_root_by_avicohh
Open odin and flash the .tar file inside the folder (In AP).
This file contains the custom recovery, a patched boot, and an empty cache.img in order the phone will restart to recovery after flashing.
In recovery choose "Apply update from ADB".
Run the .bat script file from the "SuperSU sideload installer" folder.
Wait until it finish, the phone will restart automatically with SuperSU inside.
Good luck!
Credits:
@Chainfire for SuperSU
@osm0sis for AIK
P.S. (for devs)
This method can be modified to another build / device, by patching the sepolicy inside boot.img (see here), and replacing the res / keys file inside the recovery.img with my keys. (Attached)
You can unpack and repack boot and recovery images with this tool. (It recomanded to this on linux in order to keep the files permissions)
The stock recovery doesn't support the standart SuperSU installer bacause it bash script, so i wrote another one in Edify. (this zip should work on any device with android 5.11 - 6.0.1 and armv7)
Click to expand...
Click to collapse
recovery_custom_keys.7z hướng dẫn tay ??? cảm tạ

I don't understand, what instructions?

ask something
this root files include custom recovery?

Yes, but no TWRP. Modified stock recovery.

not only G532GDXU1APL1
Not only G532GDXU1APL1 is working but also G532GDXU1AQA4 is rooted smoothly i have tested on my device. So thanks a lot.:fingers-crossed:

Brother. Can you explain to me ste by step to root sm-g532g on aq4 firmware? Please
:fingers-crossed:
bolda.mia said:
Not only G532GDXU1APL1 is working but also G532GDXU1AQA4 is rooted smoothly i have tested on my device. So thanks a lot.:fingers-crossed:
Click to expand...
Click to collapse

Just do the instruction in the first post.

Hei avicoh
avicohh said:
just do the instruction in the first post.
Click to expand...
Click to collapse
sometimes i have an error when daemon start in cmd, maybe my pc's problem? I used win7 64 bit

Upload log

Log is here
avicohh said:
Upload log
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HELP ME

I ALSO USE STOCK FIRMWARE THAT U GIVE ABOVE G532GDXU1APL1 ,
sometimes there is a messege in CMD that saying ADB out of date :/

I believe it something in your computer.
Try another one.

avicohh said:
Upload log
Click to expand...
Click to collapse
avicohh said:
I believe it something in your computer.
Try another one.
Click to expand...
Click to collapse
another one??????

alfanjawa8 said:
I ALSO USE STOCK FIRMWARE THAT U GIVE ABOVE G532GDXU1APL1 ,
sometimes there is a messege in CMD that saying ADB out of date :/
Click to expand...
Click to collapse
@avicohh WHY SUPERUSER CANNOT BE READ?

Try with another computer.

I my god it is now ask for password, and i have no z2x box to unlock it :/

So maybe @bolda.mia is wrong.
The reason the device ask for password is because the custom boot is based on G532GDXU1APL1 and you have a newer system version. (I think is something related to storage encryption, I don't know exactly)
That's why I said this method should work only on G532GDXU1APL1.
Anyway​, flash the stock version back. I believe it will fix the problem even without wipe.

before root, I already flash to lower version brother
avicohh said:
so maybe @bolda.mia is wrong.
The reason the device ask for password is because the custom boot is based on g532gdxu1apl1 and you have a newer system version. (i think is something related to storage encryption, i don't know exactly)
that's why i said this method should work only on g532gdxu1apl1.
Anyway​, flash the stock version back. I believe it will fix the problem even without wipe.
Click to expand...
Click to collapse
i know exactly, that i already flashing with the lower rom such as pl1 pk3 etc. And the result is same, ask for password my brother!

[ROOT] Install Magisk on ZC551KL Guide "FINALLY"

This is a messy post, do as you please with it. I am not responisble for ang damage to your device. Additionally, I dont take any credits for any of this, I just put everything together here.
Tags zc551kl Asus Zenfone 3 Laser z01bdc
Tools Needed:
Asus Bootloacker Unlock Tool - http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZC551KL/UnlockTool_Android_M_0706_signed1.apk
You current boot.img version which can be downloaded from here [Its packaged in the update file]- https://www.asus.com/us/Phone/ZenFone-3-Laser-ZC551KL/HelpDesk_BIOS/
ADB and Fastboot from here [Credits to Snoop05] - https://www.dropbox.com/s/mcxw0yy3jvydupd/adb-setup-1.4.3.exe?dl=0
Magisk Manager - https://tiny.cc/latestmanager
Prep:
Install the Asus Unlocker on your phone and unlock it.
Install Magisk Manager on your phone but dont run it yet.
Enable USB Degugging on your phone.
Install ABD and Fastboot on your PC. It will be installed to c:/adb/
Download the update that matches your phone version to your pc. [Mine was version "WW-32.40.106.41"]
Open the update file on your pc with your favorite zip manager and extract the boot.img .
Put the boot.img onto your phones internal storage.
Follow this guide [Credits to Dhananjay @ thecustomandroid.com]
» Non-rooted devices
Magisk 14.0 introduces a new and neat method to install on non-rooted Android devices. This new process doesn’t require your device to be rooted, nor does it require a custom recovery like TWRP. But for this method to work, your device must have the stock boot.
But for this method to work, your device must have the stock boot.img dump placed in the internal storage.
Make sure that you enable USB debugging and setup ADB access first, you will need it later in the guide.
Download Magisk Manager 5.3.0: Link
When the APK has been downloaded, use a file manager to install it. Now run the app from the app drawer.
Go to the app settings and tap on “Patched Boot Output Format”. You can select “.img.tar” if you will be using ODIN to flash the file or else simply select “.img” for the rest of the devices.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Go back to the app main screen and tap on the “Install” button. Go to INSTALL > PATCH BOOT IMAGE FILE.
Navigate through the storage and select the stock boot.img file. As soon as you select the stock boot.img file, the app will download the installer to patch the image.
Once the process is complete, you can tap on the “CLOSE” button.
Your new and patched boot image now include root and support for modules. So the last step is to grab this boot file and flash it your device via fastboot or ODIN (Depending on the output format you chose in step #4).
Connect your device to the PC via USB cable and navigate to the Magisk Manager folder inside the storage. Your “patched_boot.img” file will be present right there. So copy it to your PC.
Move the “patched_boot.img” file to C:/adb folder. And type in the following command to boot your phone into bootloader/fastboot mode:
adb reboot bootloader
Once your phone enters the bootloader/fastboot mode, enter the command to flash the file:
fastboot flash boot patched_boot.img
Finally, reboot your device:
fastboot reboot
That’s all, you have just installed one of the most trending mod out there and especially on your non-rooted device without any need of a custom recovery. Isn’t it great? Tinker around with the app and see what all things you could do.

I can confirm this is working! Thank you!

Reporting working on Android O (8.0), I download update from Asus and patch boot image. Thanks

kamo84 said:
Reporting working on Android O (8.0), I download update from Asus and patch boot image. Thanks
Click to expand...
Click to collapse
I know it's been some time since this was discussed, but I am trying to go through this process. Can you confirm that you unlocked the bootloader on 8.0 with the Asus tool? Or did you install magisk without unlocking the bootloader (if that's possible)?
thanks

I don't think the unlocker tool works anymore.

Root Infinix Note 8

Anyone know how to do it?

Either by Magisk or by SuperSU.
More info here:
How to Root Infinix Note 8 Without PC & Via Magisk
Are you waiting to Root Infinix Note 8 Smartphone? Follow our tutorial to guide you through the process to gain Superuser privileges without TWRP Recovery
www.thenextdroid.com

jwoegerbauer said:
Either by Magisk or by SuperSU.
More info here:
How to Root Infinix Note 8 Without PC & Via Magisk
Are you waiting to Root Infinix Note 8 Smartphone? Follow our tutorial to guide you through the process to gain Superuser privileges without TWRP Recovery
www.thenextdroid.com
Click to expand...
Click to collapse
I try everything its not working, even using kingoroot pc

first...did you unlock the bootloader?how to unlock bootloader on infinix note 8 ?

kalingkx said:
first...did you unlock the bootloader?how to unlock bootloader on infinix note 8 ?
Click to expand...
Click to collapse
Yeah we must unlock bootloader frist. But there is no driver for infinix note 8 to connect fastboost

Amazdd said:
Yeah we must unlock bootloader frist. But there is no driver for infinix note 8 to connect fastboost
Click to expand...
Click to collapse
The Infinix Note 8 is based on Mediatek Helio G80 chipset, hence you must install Android USB Driver suitable for this chipset.
More info here:
Download MTK USB All Drivers for Windows (Official MediaTek Drivers)
Download the latest version of MTK USB All Drivers (MediaTek Driver) to connect any MediaTek Device with the Windows Computer.
androidmtk.com

up..pls. help .,anyone know how to root infinix note 8?

do it your own risk..im not responsible for any happening to your unit...
Back Up....Back up!
activate OEM unlocking in Developers Option and use this file to unlock.
https://dropmb.com/u7agJ
Disable DMverity or flash the IN8 with empty vbmeta(img) before rooting!!!! to prevent bootlop....
then use magisk manager to root, google the procedure......
install magisk apk to IN8
copy boot.img from your back up firmware to IN8 (or get from hovatek)
now patch this boot.img using magisk.
copy the patched boot.img to the folder of the extracted file i attached and flash it in fastboot mode..
Reboot....
and your done..
credits to :
magisk manager devs.
root cheker devs.
Hope this help ...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

is there an easy solution for Rooting the device?

kalingkx said:
do it your own risk..im not responsible for any happening to your unit...
Back Up....Back up!
activate OEM unlocking in Developers Option and use this file to unlock.
https://dropmb.com/u7agJ
Disable DMverity or flash the IN8 with empty vbmeta(img) before rooting!!!! to prevent bootlop....
then use magisk manager to root, google the procedure......
install magisk apk to IN8
copy boot.img from your back up to IN8 (or get from hovatek)
now patch this boot.img using magisk.
copy the patched boot.img to the folder of the extracted file i attached and flash it in fastboot mode..
and your done..
credits to :
magisk manager devs.
root cheker devs.
Hope this help ...
View attachment 5283257
Click to expand...
Click to collapse
Wow, but scare'd to do it

yes it is risky...i exprienced some bootloops and deadboot while rooting my IN8 til i got that procedure, but no worries, if i have GSM tools that will revived it,

kalingkx said:
do it your own risk..im not responsible for any happening to your unit...
Back Up....Back up!
activate OEM unlocking in Developers Option and use this file to unlock.
https://dropmb.com/u7agJ
Disable DMverity or flash the IN8 with empty vbmeta(img) before rooting!!!! to prevent bootlop....
then use magisk manager to root, google the procedure......
install magisk apk to IN8
copy boot.img from your back up to IN8 (or get from hovatek)
now patch this boot.img using magisk.
copy the patched boot.img to the folder of the extracted file i attached and flash it in fastboot mode..
and your done..
credits to :
magisk manager devs.
root cheker devs.
Hope this help ...
View attachment 5283257
Click to expand...
Click to collapse
Can you share the empty
kalingkx said:
do it your own risk..im not responsible for any happening to your unit...
Back Up....Back up!
activate OEM unlocking in Developers Option and use this file to unlock.
https://dropmb.com/u7agJ
Disable DMverity or flash the IN8 with empty vbmeta(img) before rooting!!!! to prevent bootlop....
then use magisk manager to root, google the procedure......
install magisk apk to IN8
copy boot.img from your back up to IN8 (or get from hovatek)
now patch this boot.img using magisk.
copy the patched boot.img to the folder of the extracted file i attached and flash it in fastboot mode..
and your done..
credits to :
magisk manager devs.
root cheker devs.
Hope this help ...
View attachment 5283257
Click to expand...
Click to collapse
Can you please share the infinix note 8 empty vbmeta(img)

here

kalingkx said:
here
Click to expand...
Click to collapse
Thank you
kalingkx said:
here
Click to expand...
Click to collapse
Thank you

kalingkx said:
here
Click to expand...
Click to collapse
Hi,
Can I use the same vbmeta.img for Infinix Note 8i? Please help? Struggling to find any solution here.

Well, just putting it here. If anyone wonder where's the TWRP for this particular device, here it is: https://forum.xda-developers.com/t/unofficial-twrp-3-6-1-for-infinix-note-8-x692.4441931/

リェンーゆく said:
Well, just putting it here. If anyone wonder where's the TWRP for this particular device, here it is: https://forum.xda-developers.com/t/unofficial-twrp-3-6-1-for-infinix-note-8-x692.4441931/
Click to expand...
Click to collapse
Òwó i try not to be dumb but, is it need the same version of recovery file? Like boot img does?

Amazdd said:
Òwó i try not to be dumb but, is it need the same version of recovery file? Like boot img does?
Click to expand...
Click to collapse
You don't need to. However if you use newer boot kernel and you've formatted the /data partition on that kernel, it will became unreadable in TWRP. This is sadly an intended behaviour of F2FS. You need to unmount the /data partition before quitting TWRP to avoid corruption.
If your boot kernel is older (or the same), those won't happen and you still can access the /data partition normally

how to make normal again help me

Help!!! my lenovo tab a10-30(tb2x30l) has been bricked!

Hey, This is my first post, hope it goes well
What happened was,
-->I installed a custom rom(LineageOS) with the help of twrp recovery installed from xda(link below) and I have succesfully installed the rom and also intalled root with it
-->Later, after further use of the new rom, ,it was uncomfortable. It was not as fast and compactable as the original rom so I decided to revert back to the official and original rom.
-->But This is where I made a big mistake, I was to try to clear the data and try if the custom rom fixed but instead, I wiped up the whole rom and no backup!!!
-->Now, I cannot go into recovery mode, bootloader and whichever vol+ and vo- and power, all combinations boot me to twrp.
-->luckyly, the adb sideload is working and it is not detected in the lenovo downloader software for me to flash.
Any help? Please help me.
Thanks
TWRP - https://forum.xda-developers.com/t/recovery-lenovo-tab-a10-30f-l-twrp-2-x.3442588/
BTW - I'm on windows 11

Look inside here:
How to use ADB sideload in TWRP recovery to flash and copy zip files.
ADB sideload feature of TWRP recovery can be used to flash zip files directly from PC to android phone , how to use ADB sideload feature.
latestechnews.com

jwoegerbauer said:
Look inside here:
How to use ADB sideload in TWRP recovery to flash and copy zip files.
ADB sideload feature of TWRP recovery can be used to flash zip files directly from PC to android phone , how to use ADB sideload feature.
latestechnews.com
Click to expand...
Click to collapse
Hi,
Thanks for replying.
I tried what you've mentioned but no luck.
BTW, I did not find the stock rom zip anywhere, so I am using the lineage os custom ROM.
It boots me back into the twrp.(100% done)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I am Also Unable to boot into the bootloader.
All I have is A working and functioning TWRP and an sdcard for flashing files

CsData said:
Hi,
Thanks for replying.
I tried what you've mentioned but no luck.
BTW, I did not find the stock rom zip anywhere, so I am using the lineage os custom ROM.
It boots me back into the twrp.(100% done)
View attachment 5440137
Click to expand...
Click to collapse
That's an ADB issue.
ADB sideload's progress indicator only shows 100% if transferred size is 2.2 times of ZIP-file size.

Hi, I have waited till 100%
Below are the videos related to it.(3 videos)
https://drive.google.com/drive/folders/1M3Zk3CgQWvU4mNmIpn2HyAhLPfaV4lFJ?usp=sharing

Try making a flashable zip of your stock rom
[GUIDE]How to extract a Firmware and make a flashable ZIP
In this guide I will show you how to build a flashable zip from Stock Firmware. It's my first guide on XDA so please leave feedbacks and comment it below! :) What you need: 1.A stock ROM of your device 2.Cygwin Kitchen-See HERE for seting it up...
forum.xda-developers.com

I'm unable to find the stock rom with the required folders.
Please help me find one

CsData said:
I'm unable to find the stock rom with the required folders.
Please help me find one
Click to expand...
Click to collapse
What files are present there? You may have to extract them to get an .img file

I have a rar file which I extracted, there is no folder present.
These are the files present

Someone, Please help me to flash the stock rom or even any rom.
I just want to get the tablet working in any android. Doesent matter and I want to get rid of TWRP.
Even if I flash using adb sideload or eve using TWRP install zip, it boots me back into TWRP again even tough it is a successful Installation.
Thanks for your help

Look inside here

He
jwoegerbauer said:
Look inside here
Click to expand...
Click to collapse
Hi, Thanks for the quick reply
I'm unable to download the file
It takes me to this tab

Checked it: Link given above is working as expected.

Hi,
I think you did not get me.
You can watch the video below for your reference.
Link - https://drive.google.com/drive/folders/1ye9hNjzIJJGnxelvv0lK3lgmqjZA2m7v?usp=sharing

Correct.
Search for suitable Stock ROM at your own.

I've searched for over 3 days but no luck.
All I get is the rar file and inside that, firmware folder, drivers and software for flashing it.
If I get the tab into bootloader, I can flash but it does not allow me to go into boot loader, stock recovery.
All it does is to take me back to TWRP.
I have aldready installed around 7-9 stock roms but no zip file with meta inf folder, boot.img, system.img and the other required files.

Please Help

So I searched the WEB for tablet's Stock ROM and found it within seconds.
Lenovo_Tab_2_TB2-X30L_USR_S000031_160720
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
You flash it either via ADB Sideload method or via Lenovo Downloader Tool.

Hi,
Even I had found the same one.
But how do I flash it via adb sideload?
The problem is, in the zip file, there is drives, firmware and another folder.
Thanks for replying

Question Inofficial TWRP or boot.img?

Is anybody already working on an inofficial TWRP release or extracting a boot.img?
In an other thread @garylawwd mentioned that a patched vbmeta is missing?
I actually don't know anything about it, but how can I help

I am waiting for any update to download where I can extract using Python boot.img. Root needed on this device.

Riski3Run said:
I am waiting for any update to download where I can extract using Python boot.img. Root needed on this device.
Click to expand...
Click to collapse
Checkout my post here. I suppose you proceed with caution as the device can easily get bricked but yeah at least I enjoyed root! I am now looking for the full factory rom to restore back my phone using SP Flash. Anyone share it...

I was able to unzip CPH2399_11_A.09.zip using Python 3.7 entire payload.bin file.
There is a lot of files
What do we need to root?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Riski3Run is it possible to mirror the extracted files for me. I am unable to extract all the images as shown above
For root just patch the boot image and flash it on the active slot.
As a safegauard DO NOT patch the boot image on the inactive slot which I did and hence soft bricking my phone. That way if the device fails to boot then just switch to the inactive slot. What's better you extracted the full dump...

nielsync said:
Riski3Run is it possible to mirror the extracted files for me. I am unable to extract all the images as shown above
For root just patch the boot image and flash it on the active slot.
As a safegauard DO NOT patch the boot image on the inactive slot which I did and hence soft bricking my phone. That way if the device fails to boot then just switch to the inactive slot. What's better you extracted the full dump...
Click to expand...
Click to collapse
Let me know which files exactly you need.

Riski3Run said:
Let me know which files exactly you need.
Click to expand...
Click to collapse
If you could archive and upload all of them I'd be more than grateful. I could only extract as seen below

nielsync said:
If you could archive and upload all of them I'd be more than grateful. I could only extract as seen below
View attachment 5652615
Click to expand...
Click to collapse
Hello
CPH2399_11.A.09
FILE_HASH=yi8kVt017kbkOb17J4IzKVjtRtUgMAlgJIDN5cENJCk=
FILE_SIZE=4379426191
METADATA_HASH=xQROsSak1v7qKP37VejsrLkSoXddfHzHdYWBOaETPU8=
METADATA_SIZE=169161
oplus_separate_soft=21881
oplus_update_engine_verify_disable=0
security_patch_vendor=2022-05-05
ota_target_version=CPH2399_11.A.09_0090_202205181235
oplus_rom_version=V12.1
security_patch=2022-05-05
Here it is:
payload_output.zip
drive.google.com
Let me know when you fix your phone and gtell me how to ROOT it step by step.
Won't to brick my phone

Riski3Run said:
Hello
CPH2399_11.A.09
FILE_HASH=yi8kVt017kbkOb17J4IzKVjtRtUgMAlgJIDN5cENJCk=
FILE_SIZE=4379426191
METADATA_HASH=xQROsSak1v7qKP37VejsrLkSoXddfHzHdYWBOaETPU8=
METADATA_SIZE=169161
oplus_separate_soft=21881
oplus_update_engine_verify_disable=0
security_patch_vendor=2022-05-05
ota_target_version=CPH2399_11.A.09_0090_202205181235
oplus_rom_version=V12.1
security_patch=2022-05-05
Here it is:
payload_output.zip
drive.google.com
Let me know when you fix your phone and gtell me how to ROOT it step by step.
Won't to brick my phone
Click to expand...
Click to collapse
Thanks I used your upload to revive my phone. Thank you so much
For root, patch the boot.img using the Magisk app and then flash the patched boot.img in fastboot and you'll be good to go.
When you get an OTA don't patch the inactive slot in Magisk app because that's what caused me to soft brick. Instead extract the boot.img like you did from the OTA payload.bin and manually patch it in Magisk and then flash as usual:
fastboot flash boot patched_boot.img

Ok I understand and always Root this way. But my question is if we still need also vbmeta.img patched? Another user mentioned this... I think this is important.

Well I actually didn't! And neither did I disable verified boot in a command but was able to boot without any issue. See below:

Everything works there? Busy box etc?
I noticed that phone only after unlocking bootloader is not certified already in Google Store...which basically means "invisible" Netflix and other apps.

nielsync said:
Thanks I used your upload to revive my phone. Thank you so much
For root, patch the boot.img using the Magisk app and then flash the patched boot.img in fastboot and you'll be good to go.
When you get an OTA don't patch the inactive slot in Magisk app because that's what caused me to soft brick. Instead extract the boot.img like you did from the OTA payload.bin and manually patch it in Magisk and then flash as usual:
fastboot flash boot patched_boot.img
Click to expand...
Click to collapse
Thanks for the info.
Do we need check the active slot before flashing the patched boot from the fastboot to avoid soft brick?
Like running this command:
fastboot getvar current-slot
and then applying
fastboot flash boot_a magisk_patched.img
or
fastboot flash boot_b magisk_patched.img
Depending on the results?

Also I am getting this error from Google Pay after unlocking the bootloader but the phone is not rooted yet.
Planning to root and hide magisk from all google services, google pay and see if this error disappears.
Anyone else having this issue?

Riski3Run said:
Hello
CPH2399_11.A.09
FILE_HASH=yi8kVt017kbkOb17J4IzKVjtRtUgMAlgJIDN5cENJCk=
FILE_SIZE=4379426191
METADATA_HASH=xQROsSak1v7qKP37VejsrLkSoXddfHzHdYWBOaETPU8=
METADATA_SIZE=169161
oplus_separate_soft=21881
oplus_update_engine_verify_disable=0
security_patch_vendor=2022-05-05
ota_target_version=CPH2399_11.A.09_0090_202205181235
oplus_rom_version=V12.1
security_patch=2022-05-05
Here it is:
payload_output.zip
drive.google.com
Let me know when you fix your phone and gtell me how to ROOT it step by step.
Won't to brick my phone
Click to expand...
Click to collapse
Hope this isn't considered as necrobumping lol I'm trying to compile the TWRP recovery for this device but when I try to extract payload.bin file, I get this error. May I ask you how you extracted those files? Thanks

luke! said:
Hope this isn't considered as necrobumping lol I'm trying to compile the TWRP recovery for this device but when I try to extract payload.bin file, I get this error. May I ask you how you extracted those files? Thanks
Click to expand...
Click to collapse
I have installed Python 3.7.4 on PC, then paste payload.bin into certain folder (I think it was payload.bin input) and then run command (can't remember which one exactly) and after all files has been extended into payload.bin output.
There's a lot of guides to do that.

I uploaded before entire payload.bin folder where you can download all at once if needed.

Riski3Run said:
I uploaded before entire payload.bin folder where you can download all at once if needed.
Click to expand...
Click to collapse
Unfortunately the link you shared doesn't work anymore :/

luke! said:
Unfortunately the link you shared doesn't work anymore :/
Click to expand...
Click to collapse
I can share it if you want but within 6 days coz now I am on vacation 5000km from home.

luke! said:
Hope this isn't considered as necrobumping lol I'm trying to compile the TWRP recovery for this device but when I try to extract payload.bin file, I get this error. May I ask you how you extracted those files? Thanks
Click to expand...
Click to collapse
You asked on a different thread how I extracted the boot.img. Well you can extract all image with the tool I linked to you in that thread. Here is the tool for extracting all images