Okay I have made this thread after seeing a lot of people facing issues for rooting and unrooting. First of all this is not my work. @jashancheema and others should be credited. This guide is only for Oreo users.
Rooting:
1. Download adb and fastboot drivers on your PC.
OR
Download Platform Tools and extract the contents to a folder
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2. Enable developer options on your phone
Settings>System>About Phone>Tap on Build Number 5 to 6 times until a message appears "You are a developer" (It may ask for your PIN/Password if any)
3. Go back to your developer options>Enable OEM Unlock>Enable USB Debugging>Disable Automatic Updates
4. Download patched boot image
For Dec patch https://www.androidfilehost.com/?fid=962157660013069123
For Jan patch https://www.androidfilehost.com/?fid=962157660013071407
and place the patched_boot.img file after extracting to the platform tools folder.
5. By holding Shift button, Right click on an empty space in the platform tools folder> Open Command prompt (Open Windows Power Shell if you are using Win 10)
6. Connect your phone to PC via Usb cable
7. Type in CMD adb devices (OR ./adb devices if you are on Win 10) Your device will be shown.
8. Disconnect from USB cable and shut down your phone.
9. Download and install latest magisk manager apk on your phone.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
10. Press volume down+Power button simultaneously until you see fastboot screen.
11. Connect your device to your PC via cable and enter the commands on CMD
Code:
fastboot devices
Code:
fastboot oem unlock
Code:
fastboot boot patched_boot.img
(Use ./fastboot..... if you're on Win 10)
12. Your device will be booted. Go to magisk manager and click on Install using direct method. Reboot once again and you will be rooted.
UNROOTING
So far, according to me, the best method to unroot is to install stock rom.
1. Download miflash tool and install it on your PC.
http://api.bbs.miui.com/url/MiFlash
2. Download the latest stock rom (Jan Patch Stable) and extract it on your PC
http://en.miui.com/download-333.html
3. Uninstall all the magisk modules and reboot.
4. Uninstall magisk completely and reboot.
5. Connect the phone in fastboot mode to PC and flash the stock rom via miflash. Remember to check the "save data" option.
You will be unrooted.
It appears this guide has already been posted here:
https://forum.xda-developers.com/showpost.php?p=75040045&postcount=1
Please search before posting to avoid duplicate topics.
Thread closed.
This is a guide for a permanent full root with Magisk for the Alcatel PulseMix 5085C (Cricket). This guide assumes you somewhat know what your doing and are able to get yourself adb, fastboot, drivers, etc. Linux recommend but not required.
For an easy temporary root use MediaTek Easy Root - https://github.com/JunioJsv/mediatek-easy-root/releases
Enable Developer Options
Settings -> About phone -> Tap "Build number" 7 times
Enable OEM Unlocking
Settings -> Developer options -> OEM unlocking (enable)
Enable USB Debugging
Settings -> Developer options -> USB debugging (enable)
Whenever an ADB window pops up on your phone, allow it.
Open a terminal or prompt that has access to adb and fastboot.
Reboot to Fastboot
Code:
adb reboot bootloader
Unlock the Bootloader
Warning: This will factory reset your phone!
Code:
fastboot oem unlock
Press Vol+ when prompted
It will take some time for this first boot.
Enable Developer Options and USB Debugging again
Get a Root Shell
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
You need the arm64 version of mtk-su, copy it to the folder your terminal is open in.
Code:
adb push mtk-su /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 755 mtk-su
./mtk-su
Dump your boot.img
TYPE CAREFULLY!
Code:
dd if=/dev/block/mmcblk0p25 of=/sdcard/mmcblk0p25.bin
Install Magisk Manager
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Patch boot.img with Magisk Manager
Magisk Manager -> INSTALL (top button) -> INSTALL -> Select and Patch a File
Select mmcblk0p25.bin in the file picker
Copy magisk_patched.img from the Download folder on your phone to the folder your terminal is open in.
Reboot to Fastboot
Code:
reboot bootloader
Boot with Magisk enabled boot.img
Code:
fastboot boot magisk_patched.img
Open Magisk Manager, and if it says installed, everything worked. The final step is to actually install Magisk
Magisk Manager -> INSTALL (top button) -> INSTALL -> Direct Install (Recommended)
This device seems to be effected by a known Magisk bug that prevents modules from being installed. Looking at the log, we see:
Code:
E Magisk : execve /sbin/.magisk/busybox/busybox failed with 26: Text file busy
To fix this, download busybox-arm64 from here https://github.com/Magisk-Modules-Repo/busybox-ndk
Place it in /sbin/.magisk/busybox/, rename it to "unzip", and set it's permissions to executable. Lastly, install the busybox module and reboot.
I also have a mostly working TWRP
https://drive.google.com/open?id=12U-H9wD9zFUfraIy5h2LrYnlJaj_bnqu
It's made by swapping files between the stock recovery and one from another device. We have the MT6738 SoC, only in two phones afaict and no development progress has been made. Seems like the stock rom is built as MT6755, so I picked a recovery from a phone with that SoC.
Backing up all partitions works. I tested it by flashing custom zips and my entire system partition. Backing up system as an image does not work, as well as wiping dalvik cache.
Universal DM-Verity/ForceEncrypt Disabler works great on this device. Just need to wipe data after flashing if you don't want it encrypted.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Seems like Alcatel did not post source for this device, but it looks like they might have for a similar device the REVVL, which has the same SoC. Edit: It does, and there is indeed kernel source for this device.
--------------------------------------------------
SP Flash Tool does not work with this device. I ordered another motherboard for hardware testing. I'm hoping I can locate emmc clk so it can be pulled low(effectively disabling the emmc to prevent preloader from loading) and force the phone into bootrom mode. It then should allow us to recover from bricks similar to preloader's download mode.
To recover from a brick currently, preloader and lk must be intact. Preloader has special commands that allow you to select from various boot modes as detailed here
http://www.lieberbiber.de/2015/07/04...and-preloader/
The Fire 7 version of the amonet chain has a working example of this
https://github.com/chaosmaster/amonet
Edit "FACTFACT" to "FASTBOOT" in boot-fastboot.sh and execute it in a Linux shell. You can enter download mode by powering off the device, insert the USB cable, and then hold power for several seconds.
For other potential devs, this device is part of the Helio P10 family
https://forum.xda-developers.com/android/general/mediatek-helio-p10-development-porting-t3664416
Custom roms are very rare for this platform, but I was able to find one
https://forum.xda-developers.com/elephone-p9000
I imagine Mediatek has dropped support so we will probably be stuck on nougat for the foreseeable future.
Here is a full TWRP backup of my device, excluding data
https://drive.google.com/file/d/1SmO2Zxi9KCqTPU4Q5-SEtg_HoqukWSdJ/view?usp=sharing
A-Team Digital Solutions
Exclusive Release
Alcatel PulseMix: 5085C
-Package Contents-
-Magisk Root
-TWRP 3.4.0-0 Custom Recovery
-Boot Nag Fix(Device Has Been Unlocked & Can't Be Trusted)
-CricketRom v0.01(Custom Stock)
-Instructions-
-Enable USB Debugging & OEM Unlock in Developer Options
-Unlock Bootloader(Not Covered Here)
-Run Flasher.bat from Windows
-Follow On-Screen Prompts
-Boot TWRP
-Format Data
-Factory Reset
-Reboot
-Downloads-
-5085C-Root_Recovery_Rom_Package
https://drive.google.com/file/d/148vSfofT4LO3HHspAo2g9cnCUO8VNmPI/view?usp=sharing
-Alcatel Stock Rom Flasher/Unbricker
https://drive.google.com/file/d/1A3mbOB61hY8ykuSasdvY7ibCUJXcearC/view?usp=sharing
-OpenGapps
https://opengapps.org/
Hello, guys
first i read the diff between soft/hard brick, and i think i'm in the soft case, cause i can get in recovery menu.
adb dont see the phone at all,
fastboot can, but not 'fastboot oem unlock' , neither 'fastboot boot recover.img' works. Actually command prompt wait there for ever, untin the PC kernel ( linux deb 11), break fastboot usb connection, with a reason of connection timeout. this timeout is after 30minutes ....
i manage to backup user data for the recovery menu, in 3 files 2x2G 1x1.7G ( i think because of fat ),
but the revcovery menu fail to [ wipe data/factory reset ]. Strange ? Any ideas?
here is the model f the tablet,
==> /var/log/syslog <==
Nov 6 20:12:48 localhost kernel: [1024828.830129] usb 5-2: New USB device found, idVendor=0bb4, idProduct=0c01, bcdDevice= 1.00
Nov 6 20:12:48 localhost kernel: [1024828.830135] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 6 20:12:48 localhost kernel: [1024828.830138] usb 5-2: Product: Android
Nov 6 20:12:48 localhost kernel: [1024828.830140] usb 5-2: Manufacturer: MediaTek
Nov 6 20:12:48 localhost kernel: [1024828.830142] usb 5-2: SerialNumber: mt6582_phone
#---------------------------------------------------------------------------------------------------
# ID 0bb4:0c01 HTC (High Tech Computer Corp.) Dream / ADP1 / G1 / Magic / Tattoo / FP1
#---------------------------------------------------------------------------------------------------
# Android system recovery (3e)
# A7-30DC_S0000129_150831_ROW
#---------------------------------------------------------------------------------------------------
1. To successfully run ADB and/or Fastboot commands you need to have installed on computer the "Android USB Driver" provided by device's manufacturer.
2. ADB only will work if it got enabled on Android device.
jwoegerbauer said:
1. To successfully run ADB and/or Fastboot commands you need to have installed on computer the "Android USB Driver" provided by device's manufacturer.
2. ADB only will work if it got enabled on Android device.
Click to expand...
Click to collapse
i know, everythinks works just fine, with other android devices.
( i'm using linux by the way )
My problem right now is,
why the stock recovery fail to wipe/factory reset ?
no fastboot or adb
The tablet stuck in he lenovo logo on boot for ever,
so adb dont have any way in this stage
I try 'update cache from ADB' just to see if adb can see it, but no
when 'fastboot boot recovery.img'
the phone (tablet), report get some bytes
but nothing else
when 'fastboot oem unlock', nothing happens, both the phone and the terminal
i use this links for recovery images:
https://forum.xda-developers.com/attachments/recovery_p780_cwm_6-0-1-5-7z.2840100/
https://forum.xda-developers.com/attachments/p780_recovery_twrp_2-6-3-0-zip.2840101
any pins on hardware, to triger factory reset .... ?
DISCLAIMER* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* 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.
* Your warranty will be void if you tamper with any part of your device / software.
IMPORTANT:This method works only upto c.20 patch.
PRE REQUIREMENTS:
Python 3.9 and Git (Please make sure to add Python and Git to PATH. An option to add them to PATH will be available in the installer)
mtk client (Get it from here)
SDK Platform tools (Get it from here)
Patience
USB debugging and OEM unlock should be enabled in developer options
LET'S BEGIN!
STEPS:1. Open Command Prompt in any location and type
git clone https://github.com/bkerler/mtkclient
cd mtkclient
pip3 install -r requirements.txt
2. Dump boot and vbmeta partitions by typing the below code
Spoiler: Show Code
python mtk r boot,vbmeta,vbmeta_system,vbmeta_vendor boot.img,vbmeta.img,vbmeta_system.img,vbmeta_vendor.img
Type the above code, then press Enter and insert the USB cable into your device by simultaneously pressing vol up and down buttons. If It doesn't work try again until it does
3. Patch the boot.img in Magisk manager and save the patched boot back to Platform tools folder and rename it to boot.img. Copy vbmeta,vbmeta_system and vbmeta_vendor as well to Platform tools folder
4. Unlock the Bootloader
Execute the below commands:
Spoiler: Show Code
python mtk e metadata,userdata,md_udc
python mtk da seccfg unlock
NOTE THAT AFTER EXECUTING EACH COMMANDS YOU MIGHT HAVE TO RECONNECT YOUR DEVICE. YOU CAN ALSO PERFORM THIS STEP USING THE MTK CLIENT GUI. FOR THAT FOLLOW THE BELOW STEPS
In a command prompt window opened in mtk client folder type
python mtk_gui
Once you are in the GUI connect your device by inserting usb cable and pressing vol up and down buttons simultaneously. Once the device is recognised few tabs will show up. Head over to the erase tab and Erase metadata, userdata and md_udc partitions. Then press the Unlock bootloader button.
Reboot the device now. You should see an orange state warning during start up.
5. Reboot back to fastboot
To do this open a command prompt window in Platform Tools folder and execute
Spoiler: Show code
adb reboot fastboot
6. Flash the patched boot.img and vbmeta
Move the patched boot.img, vbmeta_system and vbmeta_vendor to platform tools folder. Execute the below commands in a command prompt window opened in Platform tools folder
Spoiler: Show code
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
fastboot flash boot boot.img
fastboot reboot
THAT'S IT! NOW YOU SUCCESSFULLY HAVE ROOT IN YOUR OPPO A54
Press the like button if this guide was useful to you!
Nice
John. P. John said:
Nice
Click to expand...
Click to collapse
Any plans to unlock?
Thank you for the guide, it's not easy but I will try in my A54 5G
Cni said:
Thank you for the guide, it's not easy but I will try in my A54 5G
Click to expand...
Click to collapse
Oppo A54 5G iirc has a Snapdragon. This method is for mediatek devices only.
does this work with the cph2211?
I cant get it to show up in the program.
ZipTies said:
does this work with the cph2211?
I cant get it to show up in the program.
Click to expand...
Click to collapse
What exactly is the issue. Most people miss the part about installing UsbDk driver. It's mentioned in mtkclient page
Johannj22 said:
What exactly is the issue. Most people miss the part about installing UsbDk driver. It's mentioned in mtkclient page
Click to expand...
Click to collapse
yep I got it working, completely missed the driver
ZipTies said:
yep I got it working, completely missed the driver
Click to expand...
Click to collapse
Nice. Also try it at your own risk cause some devices have their fastboot broken after unlocking
Johannj22 said:
Nice. Also try it at your own risk cause some devices have their fastboot broken after unlocking
Click to expand...
Click to collapse
Sir help me please send me tutorial step by step...
Deepjatt7 said:
Sir help me please send me tutorial step by step...
Click to expand...
Click to collapse
This thread itself is a step by step tutorial.
Sir can u send me video tutorial oppo a54 (CPH 2239)
This is the error i get.
C:\Windows\System32\mtkclient>python mtk r boot,vbmeta,vbmeta_system,vbmeta_vendor boot.img,vbmeta.img,vbmeta_system.img,vbmeta_vendor.img
MTK Flash/Exploit Client V1.55 (c) B.Kerler 2018-2022
usb_class
usb_class - [LIB]: ←[31mCouldn't get device configuration.←[0m
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Traceback (most recent call last):
File "C:\Windows\System32\mtkclient\mtk", line 698, in <module>
mtk = Main(args).run()
File "C:\Windows\System32\mtkclient\mtkclient\Library\mtk_main.py", line 518, in run
mtk = da_handler.configure_da(mtk, preloader)
File "C:\Windows\System32\mtkclient\mtkclient\Library\mtk_da_cmd.py", line 78, in configure_da
mtk.preloader.init()
File "C:\Windows\System32\mtkclient\mtkclient\Library\mtk_preloader.py", line 160, in init
self.mtk.port.close()
File "C:\Windows\System32\mtkclient\mtkclient\Library\usblib.py", line 356, in close
time.sleep(2)
KeyboardInterrupt
^C
C:\Windows\System32\mtkclient>
ayyu3m said:
This is the error i get.
C:\Windows\System32\mtkclient>python mtk r boot,vbmeta,vbmeta_system,vbmeta_vendor boot.img,vbmeta.img,vbmeta_system.img,vbmeta_vendor.img
MTK Flash/Exploit Client V1.55 (c) B.Kerler 2018-2022
usb_class
usb_class - [LIB]: ←[31mCouldn't get device configuration.←[0m
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Traceback (most recent call last):
File "C:\Windows\System32\mtkclient\mtk", line 698, in <module>
mtk = Main(args).run()
File "C:\Windows\System32\mtkclient\mtkclient\Library\mtk_main.py", line 518, in run
mtk = da_handler.configure_da(mtk, preloader)
File "C:\Windows\System32\mtkclient\mtkclient\Library\mtk_da_cmd.py", line 78, in configure_da
mtk.preloader.init()
File "C:\Windows\System32\mtkclient\mtkclient\Library\mtk_preloader.py", line 160, in init
self.mtk.port.close()
File "C:\Windows\System32\mtkclient\mtkclient\Library\usblib.py", line 356, in close
time.sleep(2)
KeyboardInterrupt
^C
C:\Windows\System32\mtkclient>
Click to expand...
Click to collapse
Restart the device.. Power if off and try again. Make sure the UsbDK driver is installed
Also I recommend performing a downgrade before unlocking. Some users reported that the unlocking was not successful in Android 11
Okay, noob here.
I installed python 3.9.10
And GIT, i entered all commands and EVERYTHING worked until STEP 2.
This point is not really good explained, what does the "spoiler code" mean? Where do i enter this?
What exactly has to be done for STEP 2? "press enter and connect the device" press enter where? what?
If i enter this "phython could not be found bla bla, windows store".
But it worked before, doesnt matter if im in the mtkclient directory or not, same error.
Jayk0b said:
Okay, noob here.
I installed python 3.9.10
And GIT, i entered all commands and EVERYTHING worked until STEP 2.
This point is not really good explained, what does the "spoiler code" mean? Where do i enter this?
What exactly has to be done for STEP 2? "press enter and connect the device" press enter where? what?
If i enter this "phython could not be found bla bla, windows store".
But it worked before, doesnt matter if im in the mtkclient directory or not, same error.
Click to expand...
Click to collapse
In Step 2 you are just dumping boot and vbmeta partitions. If the command prompt says python could not be found.. it means Python wasn't added to PATH while installation. By "Press enter" I meant type the commands and press enter in the command prompt
Johannj22 said:
Also I recommend performing a downgrade before unlocking. Some users reported that the unlocking was not successful in Android 11
Click to expand...
Click to collapse
my oppo is currently in latest version a11 , also successfully done step 4 without any errors . after step 4 theres an warning while booting and it says dm verity corrupted. unsafe etc. i pressed power button once and it booted fine, but when i did step 5-6 it shows bootloader not unlock and wont flash. what do i do now? should i downgrade ? if so should i lockbootloader first then flash stock a10? thanks in advance
Android_0000017 said:
my oppo is currently in latest version a11 , also successfully done step 4 without any errors . after step 4 theres an warning while booting and it says dm verity corrupted. unsafe etc. i pressed power button once and it booted fine, but when i did step 5-6 it shows bootloader not unlock and wont flash. what do i do now? should i downgrade ? if so should i lockbootloader first then flash stock a10? thanks in advance
Click to expand...
Click to collapse
Yes this is the exact issue users had been reporting. You can get stock rom file from here. Use oppo-decrypt (here) and extract the .ofp file of stock firmware to some folder. Use bypass_utility (here) to disable security otherwise we can't flash the rom using sp flash tool. Once security disabled flash the firmware using sp flash tool. While flashing make sure "opporeserve2" is unticked.
Johannj22 said:
Yes this is the exact issue users had been reporting. You can get stock rom file from here. Use oppo-decrypt (here) and extract the .ofp file of stock firmware to some folder. Use bypass_utility (here) to disable security otherwise we can't flash the rom using sp flash tool. Once security disabled flash the firmware using sp flash tool. While flashing make sure "opporeserve2" is unticked.
Click to expand...
Click to collapse
thank you very much for your contribution/help, i successfully unlocked my bootloader and installed magisk with no problems.
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