Database Info

How do I downgrade VollaOS?

I'm looking for advice on downgrading the OS on my phone, as the performance used to be better. I've been struggling for days here, knowing very little about Android phones a week ago.
I have a Volla, which is a modified Gigaset GS290 (MediaTek chipset). I've been trying out a number of flash tools but am always getting stuck.
Last one I tried was MTKClient. I can get it to detect the phone, but it stops part way in the command line:
Preloader - CPU: MT6763(Helio P23)
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212000
Preloader - Var1: 0x7f
Preloader - Disabling Watchdog...
Preloader - HW code: 0x690
Preloader - Target config: 0x0
Preloader - SBC enabled: False
Preloader - SLA enabled: False
Preloader - DAA enabled: False
Preloader - SWJTAG enabled: False
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: False
Preloader - Mem write auth: False
Preloader - Cmd 0xC8 blocked: False
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca01
Preloader - SW Ver: 0x1
Preloader - ME_ID: A472FAA544E08CAF5B46DBB8xxxxxxxxx
Preloader - SOC_ID: AD6EA35C43EBBF6EA20446713F9B9EEEB3CF6409F1CF667F11E1287xxxxxxxxx
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
I'm at a loss at this point.

I was able to downgrade from VollaOS 11 to 10 successfully, but it was quite difficult with the tools available. I gave up on MTKClient. For the benefit of others who want to do this, I’ll outline the steps I used. Special thanks for Volla Developer Community on Telegram for offering some suggestions.
I connected my Volla phone via USB to a Windows 10 PC and went through these steps.
1) Install Android SDK
2) Install MediaTek VCOM USB drivers
3) Download VollaOS 10
4) Allow USB debugging
5) Try ADB sideloading
6) Unlock bootloader
7) Allow USB debugging again
8) Install custom TWRP recovery
9) Remove device check from ZIP
10) Sideload OS from TWRP
11) Reboot the system from TWRP
1) Install Android SDK
You need two Command Line programs on your PC called ADB and Fastboot to make changes on your phone. These are included in the official Android SDK ‘Android Studio’ and are in the ‘platform-tools’ folder, which installed at this location by default:
Code:
C:\Users\user\AppData\Local\Android\Sdk\platform-tools
2) Install MediaTek VCOM USB drivers
The Volla phone’s CPU (a modified Gigabit GS290) is a MT6763V (aka Helio P23). Windows needs the right drivers to interact with a MediaTek based device. I found a set called "Windows 10 x64 MTK USB Drivers.inf”. Some sites will include installers with the drivers, but I installed “MTK USB Port” manually by selecting “Add legacy hardware” in the Device Manager. Lots of good YouTube tutorials how to do that step by step.
3) Download VollaOS 10
Get it from this repository here
Now that there’s 3 different Volla phones, be mindful of project names in the filenames that match your phone.
Code:
Volla = yggdrasil
Volla X = yggdrasilx
Volla 22 = mimameid
4) Allow USB debugging
First, unhide the Developer Menu on your phone. Navigate here and tap it 7 times:
Code:
Settings > About phone > Build number
A new menu will appear here:
Code:
Settings > System > Developer options
In this menu, turn on "USB debugging”. You may be prompted to allow it and trust the connected computer.
Now run the Command Line from the ‘platform-tools’ folder and check your devices are communicating
Code:
>adb devices
You should see a devices serial number
5) Try ADB sideloading
This is worth trying next, because the proceeding step wipes your phone completely. It didn’t work for me because of 2 errors:
Code:
Error 21: “Failed to verify whole signature”
E3004: "This package is for "[device]" devices; this is a “GS290”
Reboot the phone into maintenance mode by holding power + vol up
Select ‘recovery’ from the menu by pressing vol up, and confirm it with vol down
Select Advanced>Apply Update> from ADB
From the command line run:
Code:
>adb sideload volla-10.0-20220430-release-k63v2_64_bsp-signed.zip
This is where I got error 21. To get around this I needed to use the custom recovery TWRP, and to install that I had to unlock the bootloader, which wipes the entire phone.
6) Unlock bootloader
With the phone’s system running normally, reboot into fastboot from the command line on your PC:
Code:
>adb reboot bootloader
Then
Code:
>fastboot flashing unlock
Press volume up on your phone to confirm
7) Allow USB debugging again
Since your phone has done a factory reset you have to run through step 4 again to continue to run the debugging tools
8) Install custom TWRP recovery
Download a version of TWRP that works with Android 10, and put a copy in your platform-tools folder. I used twrp-3.5.0-10.0.img. Reboot into fastboot from the Command Line:
Code:
>adb reboot bootloader
Once the screen turns on with ‘Fastboot mode’ at the bottom, run:
Code:
>fastboot flash recovery twrp-3.5.0-10.0-GS290.img
If your PC reports all OK, then:
Code:
>fastboot reboot recovery
Your phone should reboot into TWRP.
9) Remove device check from ZIP
This is to get around Error 3004. Unzip your VollaOS package on your PC and find this file:
Code:
volla-10.0\META-INF\com\google\android\updater-script
Remove the following line and resave the file:
Code:
(!less_than_int(1651017058, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Tue Apr 26 23:50:58 UTC 2022) over newer build (" + getprop("ro.build.date") + ").");
Re-zip and then copy altered file onto a FAT32 formatted USB-C drive
10) Sideload OS from TWRP
Connect your USB Drive to your phone. Press ‘Install’ and choose your ZIP file on your USB.
11) Reboot the system from TWRP
When you reboot your phone it will prompt you to wipe your phone again because of corrupted files, but it should behave normally after that.
Note about TWRP: I tried for days to get TWRP to stay installed on the phone permanently, but it was always overridden by the Android 10 stock recovery when the system rebooted. I believe the way to circumvent this is to remove or rename the file /system/recovery-from-boot.p, but I couldn’t figure out how to get root permissions to alter this. One should be able to do this from TWRP, but the file remained hidden, nor did TWRP alter the ROM files as it was supposed to keep it installed. It’s annoying I can’t get it to stick, but I can load it again using step 8. Also, ‘fastboot boot twrp.img’ doesn’t work as it should either.

ROOT Mediatek devices [ New Method ][ Works for IMEI erased phones too! ]

Guide for flashing GSI on mediatek devices is uploaded- checkout [ Works on IMEI erased phones too! ]
This method is for mediatek chipset devices only
Spoiler: Jump to rooting
Open python directory and open mtkclient folder inside it
Run cmd inside mtkclient folder by typing cmd inside address bar of file explorer and press Enter
Turn off your phone and connect to PC with usb cable while holding Vol up and Vol down together
Run these commands inside cmd one by one
python mtk r boot,vbmeta boot.img,vbmeta.img
python mtk reset
Your phone will reboot now
There will two files created inside mtkclient folder called boot.img and vbmeta.img
Copy boot.img file to your phone
Download this masigk app only and install on phone
Open magisk and patch the boot.img file, a new file will be created inside Downloads folder named magisk_patched.img
Rename this file to boot.patched and copy it to your PC
Move this file into mtkclient folder inside python directory and replace old boot.img
Open cmd inside mtkclient folder by typing cmd inside address bar of file manager and press Enter
Now run the following command inside cmd
python mtk w boot,vbmeta boot.patched,vbmeta.img.empty
Turn off your phone and connect to PC with usb cable while holding Vol up and Vol down together
python mtk reset
Your phone will reboot now
Your device is rooted now ╰(*°▽°*)╯
Spoiler: Rooting files for devices on C.12 [ RMX2117 ]
Rooting files for devices on C.12: Download here
Place the downloaded files into mtkclient folder inside python directory and execute
python mtk w boot,vbmeta boot.patched,vbmeta.img.empty
python mtk reset
Prerequisite :
1. Mediatek drivers
Extract the zip and open Driver folder
Run the exe files, after the installation process is complete restart your PC
To check if drivers were installed and are working, turn off your phone and connect it to PC using USB Cable while holding both volume up and down buttons
There will be a prompt sound if device is connected
If your device still isn't detected, open MTK_USB_All_v1.0.8 folder and run MTK_USB_All_v1.0.8.exe
After the installation process is complete, restart your PC
2. Python Download and install python.
Go to python directory
Search python in start menu, right click python and click on open file location, again right click on python and click open file location | This is the python directory.
Open cmd inside it by typing cmd at the address bar of file explorer and press Enter
Inside cmd exectue following commands one by one
Thanks Bjoern Kerler
git clone https://github.com/bkerler/mtkclient
cd mtkclient
pip3 install -r requirements.txt
3. Unlocked Bootloader [ User data will be formatted ]
Turn off your phone
Open mtkclient folder inside python directory and open cmd inside folder by typing cmd inside address bar of file manager
Now run below command
python mtk e metadata,userdata,md_udc
Connect phone to PC with USB Cable while holding Vol+ and Vol- together
Now run below commands one by one
python mtk da seccfg unlock
python mtk reset
After the script completes, disconnect phone and reboot by holding power button
Your device's bootloader is unlcoked now ╰(*°▽°*)╯
Note: Bootloader can't be used whatsoever but 'unlocked bootloader' is a requirement before flashing any partition to your phone
Now comes actual rooting part
Open python directory and open mtkclient folder inside it
Run cmd inside mtkclient folder by typing cmd inside address bar of file explorer and press Enter
Turn off your phone and connect to PC with usb cable while holding Vol up and Vol down together
Run these commands inside cmd one by one
python mtk r boot,vbmeta boot.img,vbmeta.img
python mtk reset
Your phone will reboot now
There will two files created inside mtkclient folder called boot.img and vbmeta.img
Copy boot.img file to your phone
Download this masigk app only and install on phone
Open magisk and patch the boot.img file, a new file will be created inside Downloads folder named magisk_patched.img
Rename this file to boot.patched and copy it to your PC
Move this file into mtkclient folder inside python directory and replace old boot.img
Open cmd inside mtkclient folder by typing cmd inside address bar of file manager and press Enter
Now run the following command inside cmd
python mtk w boot,vbmeta boot.patched,vbmeta.img.empty
Turn off your phone and connect to PC with usb cable while holding Vol up and Vol down together
python mtk reset
Your phone will reboot now
Your device is rooted now ╰(*°▽°*)╯
Rooting files for devices on C.12: Download here
Place the downloaded files into mtkclient folder inside python directory and execute
python mtk w boot,vbmeta boot.patched,vbmeta.img.empty
python mtk reset

why are you linking your own github? why alpha build?

aIecxs said:
why are you linking your own github? why alpha build?
Click to expand...
Click to collapse
its patched magisk for mediatek devices, using other version of magisk for patching boot file results in bootloop

hm.. I have Xiaomi Redmi 6 it doesn't boot-loop. but I have other issue. will try...
nope! same issue as on any magisk. but this one does not even give root. Do not link that apk without note what exactly is "patched" - it's not recommended!
Code:
cereus:/ $ su
No daemon is currently running!

aIecxs said:
hm.. I have Xiaomi Redmi 6 it doesn't boot-loop. but I have other issue. will try...
nope! same issue as on any magisk. but this one does not even give root. Do not link that apk without note what exactly is "patched" - it's not recommended!
Code:
cereus:/ $ su
No daemon is currently running!
Click to expand...
Click to collapse
You have missed something, it definitely works and the issue you have mentioned isn't related to this thread, if its caused by magisk then try other rooting solutions.

I just proofed that (outdated) patched alpha apk isn't working for my mediatek device (doesn't give root), furthermore the official stable apk doesn't boot-loop my mediatek device.
https://github.com/topjohnwu/Magisk
yes, my linked issue is unrelated. but you can find magisk logs there, proof that canary is working.
So if Magisk boot-loop for you, obviously you are the one who has missed something (maybe checkbox for preserving encryption?)

Did you tried with steps mentioned in this thread ?
If yes then, if you read this command,
Code:
python mtk w boot,vbmeta boot.patched,vbmeta.img.empty
Here the boot.img is named boot.patched to avoid unpatched boot image to be flashed on device
Did you renamed patched boot.img as boot.patched ?

my bootloader is unlocked already, so I just flashed magisk_patched_23001.img from fastboot. as you can see in post #4 su respond with No daemon is currently running! so obviously magisk is somehow present.
Maybe I should delete /data/adb next time trying older Magisk. but baseband unknown occurred regardless of su daemon was not running, therefore I have no interest in this v23 alpha build anyway.
But thx for trying to help me

aIecxs said:
my bootloader is unlocked already, so I just flashed magisk_patched_23001.img from fastboot. as you can see in post #4 su respond with No daemon is currently running! so obviously magisk is somehow present.
Maybe I should delete /data/adb next time trying older Magisk. but baseband unknown occurred regardless of su daemon was not running, therefore I have no interest in this v23 alpha build anyway.
But thx for trying to help me
Click to expand...
Click to collapse
you can easily fix unknown baseband using twrp

you mean patching fstab with nvram nvdata nvcfg? how can I do this systemless? or do you mean I should patch twrp.fstab? thought that is only used for recovery mode.

aIecxs said:
you mean patching fstab with nvram nvdata nvcfg? how can I do this systemless? or do you mean I should patch twrp.fstab? thought that is only used for recovery mode.
Click to expand...
Click to collapse
You need to delete a certain files in a directory in root file system it works well in android 10 and above

what? magisk is systemless-root method. I won't touch anything inside system partition for sure (I would just use Magisk systemless REPLACE function if you tell me what exactly files must deleted?) But my baseband is working fine on normal boot, just when booted into Magisk baseband disappears. Have you even read my issue on github (linked in post #4)?

Bro i know what circumstances you have here regarding magisk, but why are u using alpha build if you can use the normal apk? And what android are yoi?
Regarding in unknown baseband you can try this method to fix it android 9 and up root/nvdata/nvram then delete all files inside for android 8 and lower root/nvram delete all files inside

I am using latest magisk. what is root/nvram? do you mean (rootdir) / namely /nvram? that is just a mountpoint for nvram partition. why should I delete nvram partition, as I stated baseband is working? please read the github issue first...
https://github.com/topjohnwu/Magisk/issues/6570

aIecxs said:
I am using latest magisk. what is root/nvram? do you mean (rootdir) / namely /nvram? that is just a mountpoint for nvram partition. why should I delete nvram partition, as I stated baseband is working? please read the github issue first...
https://github.com/topjohnwu/Magisk/issues/6570
Click to expand...
Click to collapse
Look bro your phone has dm-verity right and you know how it works right? I meant to delete the files inside thay folder you cant easily delete partition in twrp file manager you know that is only the mount point but not the actual partition thos files might be duplicate or blocking something that might be the cause of the error in baseband if you delete that files inside it moght fix your phone and u dont need to worry if you have dm verity its ok because it will restore your deleted files in root folder

Anonymous V said:
Look bro your phone has dm-verity right and you know how it works right? I meant to delete the files inside thay folder you cant easily delete partition in twrp file manager you know that is only the mount point but not the actual partition thos files might be duplicate or blocking something that might be the cause of the error in baseband if you delete that files inside it moght fix your phone and u dont need to worry if you have dm verity its ok because it will restore your deleted files in root folder
You know im just suggesting you a solution just try it might help
Click to expand...
Click to collapse
.

I just installed mentioned drivers and python .​
After that I cloned the github repo mentioned in tutorial.​
Then I did execute cmd in mtkclient folder.​
​Now I am stucked on this step where I have to connect my phone through USB with pressing vol+ & vol- buttons.
Just give me some idea about how to get through this error,
please suggest me solutions for this error.

Please help me with the preloader error.
While Pressing Vol+ with Vol- Buttons the Handshake failed error pops on screen.
Please Help me to fix this error.
I just want to unlock the bootloader of my rmx2117.

Please specify Android version of your phone. If drivers are installed correctly, there must COM port displayed in Device Manger on your PC

and most important, device must powered off for the handshake. if you miss it, it will powered on by usb (which is too late)

DOOGEE S59 pro unlocking bootloader issue

Hello.
I have a DOOGEE S59 pro phone and i tried a bunch of times to unlock its bootloader, but it didn't work.
I've already done these things:
I've installed the USB driver and the MediaTek driver from https://gsmusbdriver.com/
I've enabled "OEM unlocking" and "USB debugging" in the developper options
I've ran the CMD prompt in the platform-tools folder (which is placed in the C: drive) and run this code:
PS C:\Program Files\platform-tools> adb devices
List of devices attached
S59PROEEA0000026105 device
PS C:\Program Files\platform-tools> adb reboot bootloader (now the phone shows " =>FASTBOOT mode . . . ")
PS C:\Program Files\platform-tools> adb devices
List of devices attached
(My phone isn't listed anymore)
PS C:\Program Files\platform-tools> fastboot oem unlock
< waiting for any device >
And this is it. I can't do anything else. When I hold the power button + the volume up key I can return to normal mode, but what can I do to unlock the bootloader? I wanted to root my phone and flash some magisk modules after that, but the situation is like I said. Can somebody help me?

Since the phone is using a MediaTek chipset you can try using MTKclient, after downloading the zip completely power off your phone and open a terminal inside the 2nd folder of the unzipped zip file, the run the command python mtk da seccfg unlock after you did that hold the button combination for fastboot mode so long until the screen goes fully black and mtkclient should try unlocking the bootloader. Tried and tested on my Xiaomi Redmi 9 because I didn't want to factory reset.

.

xinthenoob said:
Since the phone is using a MediaTek chipset you can try using MTKclient, after downloading the zip completely power off your phone and open a terminal inside the 2nd folder of the unzipped zip file, the run the command python mtk da seccfg unlock after you did that hold the button combination for fastboot mode so long until the screen goes fully black and mtkclient should try unlocking the bootloader. Tried and tested on my Xiaomi Redmi 9 because I didn't want to factory reset.
Click to expand...
Click to collapse
Thank you, I'll try that and I'll tell you if it works.

KakoFed said:
Thank you, I'll try that and I'll tell you if it works.
Click to expand...
Click to collapse
I completely forgot 2 more things!
1. You need to have python installed (during the install when you see a button that says "Add to PATH" check it)
2. After opening the terminal run pip install -r requirements.txt

xinthenoob said:
I completely forgot 2 more things!
1. You need to have python installed (during the install when you see a button that says "Add to PATH" check it)
2. After opening the terminal run pip install -r requirements.txt[
[/QUOTE]
Click to expand...
Click to collapse
I've just installed python, but I don't see the "Add to PATH" button. When I try to type that command, it says 'pip' is not recognized as an internal or external command,
operable program or batch file.
What should I do?
And also, which version of python do I have to install?

xinthenoob said:
I completely forgot 2 more things!
1. You need to have python installed (during the install when you see a button that says "Add to PATH" check it)
2. After opening the terminal run pip install -r requirements.txt
Click to expand...
Click to collapse
I also tried to open a command prompt in the mtkclient folder itself, and it said that:
pip : The term 'pip' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the s
pelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ pip install -r requirements.txt
+ ~~~
+ CategoryInfo : ObjectNotFound: (pip:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

xinthenoob said:
I completely forgot 2 more things!
1. You need to have python installed (during the install when you see a button that says "Add to PATH" check it)
2. After opening the terminal run pip install -r requirements.txt
Click to expand...
Click to collapse
Alright, I don't know what have I done, but it totally worked! Thank you so much!

KakoFed said:
I've just installed python, but I don't see the "Add to PATH" button. When I try to type that command, it says 'pip' is not recognized as an internal or external command,
operable program or batch file.
What should I do?
And also, which version of python do I have to install?
Click to expand...
Click to collapse
It should be somewhere also don't use PowerShell, it's weird sometimes

xinthenoob said:
It should be somewhere also don't use PowerShell, it's weird sometimes
Click to expand...
Click to collapse
Hi, it's me again.
I unlocked the bootloader successfully, but now I am trying to root my phone using magisk. I patched a boot.img file from the Doogee s59 pro firmware and I tried to flash it via ADB, but it didn't work. I went into the fastboot mode (it is saying "fastbootd" actually), and I typed
fastboot devices
That worked, my phone was listed, but after that I tried to flash the patched boot.img file using this command:
fastboot flash boot <the file directory>
And also
fastboot boot <the file directory>
And it didn't work, it said:
warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 33554432).
sending 'boot' (32768 kb) failed (write to device failed (no link)) fastboot: error: command failed
Something like this.
What am I doing wrong?
Please help

KakoFed said:
Hi, it's me again.
I unlocked the bootloader successfully, but now I am trying to root my phone using magisk. I patched a boot.img file from the Doogee s59 pro firmware and I tried to flash it via ADB, but it didn't work. I went into the fastboot mode (it is saying "fastbootd" actually), and I typed
fastboot devices
That worked, my phone was listed, but after that I tried to flash the patched boot.img file using this command:
fastboot flash boot <the file directory>
And also
fastboot boot <the file directory>
And it didn't work, it said:
warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 33554432).
sending 'boot' (32768 kb) failed (write to device failed (no link)) fastboot: error: command failed
Something like this.
What am I doing wrong?
Please help
Click to expand...
Click to collapse
You can flash the boot using mtkclient once again, first back up boot and vbmeta using python mtk r boot,vbmeta boot.img,vbmeta.img then transfer the patched boot to your PC and rename it boot.patched after doing that you can flash it onto your phone using python mtk w boot,vbmeta boot.patched,vbmeta.img.empty. Making a backup of those two is VERY important Incase something goes wrong.
Also I think it's because your phone has a integrity check, if you really want to flash it using fastboot I could find a fix

xinthenoob said:
You can flash the boot using mtkclient once again, first back up boot and vbmeta using python mtk r boot,vbmeta boot.img,vbmeta.img then transfer the patched boot to your PC and rename it boot.patched after doing that you can flash it onto your phone using python mtk w boot,vbmeta boot.patched,vbmeta.img.empty. Making a backup of those two is VERY important Incase something goes wrong.
Also I think it's because your phone has a integrity check, if you really want to flash it using fastboot I could find a fix
Click to expand...
Click to collapse
Thanks, I'll try it, but in case something goes wrong, how do I use the backup files?
And also, could I install magisk modules after that?

KakoFed said:
Thanks, I'll try it, but in case something goes wrong, how do I use the backup files?
And also, could I install magisk modules after that?
Click to expand...
Click to collapse
Same way you flashed the patched files, always include the vbmeta.img.empty if you're flashing anything but the vbmeta.
If everything goes as planned, absolutely! I'm using energize protection as an ad blocker and it's working great.

xinthenoob said:
Same way you flashed the patched files, always include the vbmeta.img.empty if you're flashing anything but the vbmeta.
If everything goes as planned, absolutely! I'm using energize protection as an ad blocker and it's working great.
Click to expand...
Click to collapse
Ok, thanks, I'll try everything of that later

.

xinthenoob said:
Same way you flashed the patched files, always include the vbmeta.img.empty if you're flashing anything but the vbmeta.
If everything goes as planned, absolutely! I'm using energize protection as an ad blocker and it's working great.
Click to expand...
Click to collapse
Hi, I have a problem AGAIN. When I flashed the boot.patched file, it was almost ok, until I saw that my bluetooth and WiFi connections stoped working after the flash. There was this window opening again and again that the Bluetooth app still stops working. I had to flash the normal boot.img file for it to work.
How can I solve this problem? I still want to root my phone

xinthenoob said:
Same way you flashed the patched files, always include the vbmeta.img.empty if you're flashing anything but the vbmeta.
If everything goes as planned, absolutely! I'm using energize protection as an ad blocker and it's working great.
Click to expand...
Click to collapse
ACTUALLY NEVER MIND
I found a solution myself, it was the boot.img file that I think was the problem. I patched the boot.img file again but this time I patched that one that I backuped with MTKclient.
Thank you so much for your help, you were really helpful for me

KakoFed said:
ACTUALLY NEVER MIND
I found a solution myself, it was the boot.img file that I think was the problem. I patched the boot.img file again but this time I patched that one that I backuped with MTKclient.
Thank you so much for your help, you were really helpful for me
Click to expand...
Click to collapse
Sorry I caught the flu and was out for a while but I'm glad you found a way

Infinix zero 5g 2023 TURBO X6815C (bootloader unlock/root/system-r/w) Ant-Man and the Wasp: Quantumania Edition

root infinix XOS 12 (Android 12)
Infinix Zero 5G Ant-Man and the Wasp: Quantumania Edition
Easy unlock
1. Enable developer options and turn on/allow OEM unlocking and enable USB debugging
2. Reboot to fastoot
Code:
Code:
adb reboot bootloader
3. Unlock bootloader via fastboot (you will be prompted to accept yes with volume up on phone.
Code:
fastboot flashing unlock
4. Setup and install MTK client Linux (fallow guide)
[GUIDE] [MTK] How to use MTKClient and set it up!
So most of you probably don't know what mtkclient is. It is basically an exploit which is used to boot any (mtk) phone into BROM mode (basically EDL for mtk) I am writing this guide especially for the RM6785 community. This tool is very useful...
forum.xda-developers.com
4. backup all partitions with MTKClient/MTKTool GUI (launch the mtk_GUI with su/root)
in mtk_GUI
Go to,
Read Partition(s) Tab and tick all boxes to be read/backup the partitions except data partition (internal storage)
Now you should have a backup of your files/.bin
5. copy boot_a.bin to your phone internal for magisk patching manually on phone
(Time of writing latest)
https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk
6. Rename (magisk renames the default .bin)
patched_boot_a.img to patched_boot_a.bin
7. Copy patched boot_a back to your computer/home folder.
8. flashing.
From fresh started Android reboot to fastboot.
Code:
adb reboot bootloader
DO THE NEXT 2 STEPS AT THE SAME TIME IN FASTBOOT.
(Fastboot commands)
Code: terminal
Code:
fastboot flash boot_a /path/to/patched_boot_a.bin
Code2: (disable verity/secure boot) use vbmeta_a.bin that you backed up from you're phone.
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a /path/to/vbmeta_a.bin
AFTER flashing above you should now have root
############## system r/w#############
If you want system R/W writable (full root) fallow next steps.
1. go to system r/w website and get this version tested here.
Official SYSTEM-RW v1.41 by lebigmac for Samsung Galaxy S23 Ultra and other devices
lebigmac's software
lebigmac
www.systemrw.com
Link to file above
11.21 MB file on MEGA
mega.nz
This must be run on the phone!
Step 1
Decompress (7zip) SYSTEM-RW_v1.41.zip to this directory on device. sysrw_1.41
Code:
/data/local/tmp
Step 2 in Android terminal type
Code:
Code:
su
cd /data/local/tmp/sysrw_1.41
chmod +x sysrw
./sysrw
This will build the new patched r/w super.bin in /data/local/tmp/sysrw_1.41/IMG
Use file explorer (fx-file explorer) to copy patched_super.bin to phones internal/storage and then copy to computer to flash with fastboot.
Step 3
Code:
On computer/PC with adb and fastboot flash super. (Should be around 8gb file)
Code:
Code:
sudo adb reboot bootloader
sudo fastboot flash super /path/to/patched_super.bin
sudo fastboot reboot
########################
Enjoy system r/w[/code]

Lposed

CPU Demensity 1080, can play most emulators (dolphin/athersx2) at 30-60 FPS,a really powerful gaming phone

Phone
Infinix Zero 5G Ant-Man and the Wasp Quantumania Edition

Any help please

Can elaborate this please. Im stuck at this step

Mtk-client has a user interface see photo
Step4 in mtk_GUI
Go to,
Read Partition(s) Tab and tick all boxes to be read/backup the partitions except data partition (internal storage)
Now you should have a backup of your files/.bin

Still can not change SELinux to permissive or install.... some madgisk modules..?? Assuming because the boot is reed only, wish system r/w worked on boot to as it contains the kennel..

Hi what version is your device? Is it v810? I was wondering if your device can boot into BROM mode.

Build number:
X6815C-H777A-S-GL-221010V451
Should work on
X6815
X6815B
And to get into BROM mode (to my understanding) on any mediatek CPU/phone simply power the device off with no USB connected...
Launch mtk_GUI with root, and it will ask to hold volume up or down while connecting the USB from a powered off state (try different button combinations)
Mtk _GUI is touchy!... with how it connects it usually takes me 2-3 attempts of rebooting and powering off my phone to get it connect/recognize in brom mode
(Might be worth noting)
If your Linux sysctl.conf has these security JIT settings
net.core.bpf_jit_harden=2
kernel.unprivileged_bpf_disabled=1
kernel.kexec_load_disabled=1
Or more...
mtk client will not recognize your devices... Simply move sysctrl.conf temporarily and reboot your Linux machine and try again

notreal456789 said:
Build number:
X6815C-H777A-S-GL-221010V451
Should work on
X6815
X6815B
And to get into BROM mode (to my understanding) on any mediatek CPU/phone simply power the device off with no USB connected...
Launch mtk_GUI with root, and it will ask to hold volume up or down while connecting the USB from a powered off state (try different button combinations)
Mtk _GUI is touchy!... with how it connects it usually takes me 2-3 attempts of rebooting and powering off my phone to get it connect/recognize in brom mode
(Might be worth noting)
If your Linux sysctl.conf has these security JIT settings
net.core.bpf_jit_harden=2
kernel.unprivileged_bpf_disabled=1
kernel.kexec_load_disabled=1
Or more...
mtk client will not recognize your devices... Simply move sysctrl.conf temporarily and reboot your Linux machine and try again
Click to expand...
Click to collapse
Damn sadly im on v810 now and it doesn't enter into BROM mode anymore or maybe am i doing something wrong but idk. I hope infinix will enable it again

Hnojohn said:
Damn sadly im on v810 now and it doesn't enter into BROM mode anymore or maybe am i doing something wrong but idk. I hope infinix will enable it again
Click to expand...
Click to collapse
This is why I don't update things, also it could be the setup Maby I'll post a Linux.iso with mtk client setup correctly

I still use Android apps from 2008 that still work on Android 12 fine

[GUIDE] Here's how to unlock the bootloader of Nokia 5.3.

Code:
#/usr/bin/env python3
from hct_principle import permission, content
print('''
Your warranty is void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
''')
if content.repost('other_content_farm_website_or_tech_forum'):
if not permission:
print('Please DM me for permission')
raise Exception('RepostNotAllowedException')
Recently I got a prototype OS backup from a Nokia 5.3 engineering sample unit that contains ABL image with bootloader unlock capability.
Later I found it can be used on retail unit, but flashing it can be tough depends on Android OS version installed on your phone.
{
"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"
}
Case 1: If you already have Android 11 or 12 installed
I'm sure that's the mostly seen situation for Nokia 5.3 users. Unfortunately to do this, you'll have to open up the phone and have Qualcomm EDL driver installed, or consider to use bkerler's live DVD on your PC (prepare a spare USB drive).
1. Clone and download this repository, or just boot into LiveDVD mentioned in README. Install it according to README.
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
Also download prototype ABL and attached firehose programmer from here:
Click here to download Prototype ABL
SHA256 checksum of ABL image: C8021967F91908BBE30C4534AA2174B72FB18A204F73BB96561A3F8A17140F0E
If you see error code 00000101, please use industrial standard web browser like Google Chrome.
2. Power off your phone.
3. Follow this video to disassemble the phone, until 4:40. Make sure you have motherboard exposed and battery DISCONNECTED. Please ask an experienced technician for help if you're not familiar with phone disassembly procedure.
4. (Skip this step if you're using Linux) Change EDL port driver according to README.md of edl toolkit said, and reconnect the phone after driver changed.
5. Execute these commands to backup original ABL and write prototype ABL.
For Windows, you should be able to see Qualcomm EDL Port in Device Manager.
For Linux, you'll have to use lsusb command to check if your phone is listed.
:
Code:
./edl r abl_a,abl_b abl_a.bin,abl_b.bin --loader=/home/your_user_name/Download/prog_emmc_firehose_Sm6125_ddr.elf
./edl w abl_a /home/your_user_name/Download/CAP-abl.elf --loader=/home/your_user_name/Download/prog_emmc_firehose_Sm6125_ddr.elf
./edl w abl_b /home/your_user_name/Download/CAP-abl.elf --loader=/home/your_user_name/Download/prog_emmc_firehose_Sm6125_ddr.elf
After executed and waiting for connection, attach a side of your USB cable on your phone, then use a tweezer to short the test point indicated below. While shorting test point with tweezers, connect it to PC. You may need to repeat this when you execute next 2 commands.
6. Disconnect the phone, reattach the battery and reassemble the phone. Your phone should boot right into Fastboot mode.
7. Execute these commands to perform bootloader unlock:
Code:
fastboot flashing unlock_critical
(confirm unlock on your phone)
fastboot oem unlock-go
(confirm unlock on your phone again)
8. Once bootloader unlock confirmed, execute this command to check if unlock successful:
Code:
fastboot oem device-info
If both unlock state are indicated as True, you can restore the ABL back to retail (if you don't then phone will not boot to normal OS), wipe userdata and reboot:
Code:
fastboot flash abl_a abl_a.bin
fastboot flash abl_b abl_b.bin
fastboot -w reboot
9. If your phone had initial release of Android 12 that bricked the phone after factory reset, unbrick the phone by following this procedure.
10. Enjoy your bootloader unlocked Nokia 5.3 and have fun for hacking.
Watch this video in case you still don't understand:
Case 2: If you know someone who can provide remote phone flash service for you
I can help when the phone has Android 10 installed, but it's pretty rare nowadays, at least it's difficult to find outside China mainland.
However in this case you don't need to disassemble the phone, you'll just need to reinstall stock firmware after bootloader unlock.
1. Grant service permission. I know how the service permission granting works under initial release of Android 10, which I can't disclose here (also how I confirmed bootloader unlock method working).
If you know someone who can flash a recent Nokia phone for you, Then it will work under Android 11 or 12. When you request such service, ask him not to reboot your phone after the procedure completes.
2. Execute these commands to perform bootloader unlock:
Code:
fastboot flash abl CAP-abl.elf
fastboot reboot-bootloader
fastboot flashing unlock_critical
(confirm unlock on your phone)
fastboot oem unlock-go
(confirm unlock on your phone again)
3. Flash stock ABL image and wipe userdata. Stock image from Android 12 release is attached below - extract it before flashing, or it will brick your phone and you'll have to use EDL method to revive it.
It may break OTA functionality, so use with care.
Code:
fastboot flash abl CAP-340A-abl.elf
fastboot -w reboot

I waited a long time, but do not leave this status

thiago92nr said:
I waited a long time, but do not leave this status
Click to expand...
Click to collapse
1. In case that happens, check if your laptop only has USB 3.x port. If yes, try to execute the command before connecting the phone to PC.
2. Execute the command under /home/your_user_name instead of /opt/edl to prevent permission issue.

Worked perfectly. I was able to unbrick my Nokia 5.3 by flashing the stock rom with Fastboot after unlocking the bootloader.

Regarding to stock firmware installation after bootloader unlock.
I'm sure you can obtain a stock ROM somewhere, for example the one I obtained has filename "HMDSW_TA-1229-340A-0-00WW-B01_user_devicekit.zip". (However it can be used on non TA-1229 models like TA-1234)
HMDSW_TA-1229-340A-0-00WW-B01_user_devicekit.zip | by Hikari Calyx for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
DO NOT USE MINIMAL ADB AND FASTBOOT! DELETE IT BEFORE YOU PROCEED!
These are possible locations of Minimal ADB and Fastboot:
Code:
C:\adb
C:\Program Files (x86)\Minimal ADB and Fastboot
C:\Program Files\Minimal ADB and Fastboot
C:\Windows\system32
Delete these 4 files: adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll, fastboot.exe
Extract the firmware package twice and you'll see a batch file named "sm6125_fastboot_all_images.bat". Right click on it and remove the second line (adb reboot bootloader) - since you're already in fastboot mode.
Then, extract Platform Tools from following websites and place files along with firmware files: https://developer.android.com/studio/releases/platform-tools
Make sure fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll are placed altogether with firmware files, then double click "sm6125_fastboot_all_images.bat" to reinstall stock firmware.
As for macOS and Linux, you've probably noticed the existence of Captain_download_mac.sh and Captain_download_ubuntu.sh. Edit them and execute it under terminal.

Hello, do you mind to make a video how to do those steps? It's quite confusing especially for the 1st step and the 6th step.

xmichaxb7 said:
Hello, do you mind to make a video how to do those steps? It's quite confusing especially for the 1st step and the 6th step.
Click to expand...
Click to collapse
I'll have to wait few days to weeks for another Nokia 5.3 test unit's arrival.

hikari_calyx said:
I'll have to wait few days to weeks for another Nokia 5.3 test unit's arrival.
Click to expand...
Click to collapse
Oh, alright. I guess I must wait patiently. My Nokia 5.3 has a problem with the NFC on A12. It just keeps detecting my E-Money card like every 1 second or 0.5 second. So, I hopefully will be able to downgrade to A11 after I unlock the bootloader.

hikari_calyx said:
1. In case that happens, check if your laptop only has USB 3.x port. If yes, try to execute the command before connecting the phone to PC.
2. Execute the command under /home/your_user_name instead of /opt/edl to prevent permission issue.
Click to expand...
Click to collapse
I tried this after facing the same issue as @thiago92nr with no success still stuck on mode detected Sahara.
I used the live CD to try unlocking the bootloader and still no luck

pingusp said:
I tried this after facing the same issue as @thiago92nr with no success still stuck on mode detected Sahara.
I used the live CD to try unlocking the bootloader and still no luck
Click to expand...
Click to collapse
Type the command and press enter before connecting the device, then connect. it worked for me like this

I'll give it a go thanks

thiago92nr said:
Type the command and press enter before connecting the device, then connect. it worked for me like this
Click to expand...
Click to collapse
@thiago92nr I have another eorr.edl.py: No such file or directory

pingusp said:
@thiago92nr I have another eorr.edl.py: No such file or directory
Click to expand...
Click to collapse
remove the .py extension

Tried that and it's giving me this error @thiago92nr

Hey everyone I'm stuck on this part with no idea on what to do

pingusp said:
Hey everyone I'm stuck on this part with no idea on what to do
Click to expand...
Click to collapse
try this command
edl printgpt --loader=/home/user/Download/prog_emmc_firehose_Sm6125_ddr.elf
Then this one for Abl flash a and b
edl r abl_a abl_a.bin --memory=emmc --loader=/home/user/Download/prog_emmc_firehose_Sm6125_ddr.elf

Before I do this should I download all 3 files or the one with the prototype abl

thiago92nr said:
try this command
edl printgpt --loader=/home/user/Download/prog_emmc_firehose_Sm6125_ddr.elf
Then this one for Abl flash a and b
edl r abl_a abl_a.bin --memory=emmc --loader=/home/user/Download/prog_emmc_firehose_Sm6125_ddr.elf
Click to expand...
Click to collapse
Tried it same message
Apparently it could be due to pkhash does match the device pkhash or hardware doesn't match loader

some indan dude can unluck it without disassembling the Device! thats interesting he gives 20$ for that but i wanna know how its possible????

I think he might use hickari calyx bootloader unlock method or the hmd device toolkit