Related
This is for real, folks. The first working custom recovery for Asus ZenPad 8.0 Z380M and a method to flash it under a locked bootloader. This took quite a bit of work to make, partly due to having to find a way to bypass the locked bootloader. And because of a kernel configuration issue that limited the size of the initial ramdisk, which took some serious effort to weed out. @lss1977 helped to port it to this device. And of course, credits to TeamWin for TWRP.
In addition to this thread, the current Z300M/Z301M TWRP thread and the the old Z300M recovery/rooting thread may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the other.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)*
MediaTek VCOM drivers (available through Windows Update)
Z380M scatter file, attached
Recovery image, attached
Z380M preloader file (optional), available inside the stock firmware download
ZenPad Z380M tablet upgraded to Android N
* If you prefer to use a more recent SP Flash Tool, check out the special image file below.
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 8.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image (twrp-3.2.1-0-z380m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z380m.img
Once inside TWRP, flash twrp-3.2.1-0-z380m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
(Updated February 3, 2018: updated kernel to firmware 5.3.18; up-to-date TWRP 3.2.1 sources)
SP Flash Tool v5.1532
Z380M Scatter file for all storage sizes (right click, Save link as...)
Recovery image
Signed image for Flash Tool only -- may be flashed with recent SP Flash Tool versions -- DO NOT INSTALL USING ANY OTHER METHOD -- tested with SPFT 5.1736.
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Nice one now lets get some custom roms done.
Has anyone installed this yet? I see the file has been downloaded a few times. Any feedback is welcome.
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
The way I did it was to edit the init.rc file inside the boot ramdisk and comment out the service block that calls install_recovery.sh. I used the MTK boot image unpack/repack tools. I don't know, it seems like changing anything on the system partition will break OTA updates because of dm-verity. Because that depends on verifying each block of the file system. I have never even mounted the system as R/W in recovery.
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
PxYra said:
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
Click to expand...
Click to collapse
OK, I added the scatter file as a download. It was a pain in the ass to copy & paste. (But it did work.)
Problem fixed downloaded new version of flashtool 5.16 and scatter working
Ok I installed TWRP on Z380M P00A, and wanna say to other
1. Use VCOM drivers only from splash tool official site
2. To install VCOM drivers first need enter chinese recovery tablet, then in windows device manager you see USB device, install manualy drivers (don forget in windows disable driver signature)
3. Use only SP-Flash-Tool-v5.1532.00, newer or older version not properly working with this phone
Ok, thanks for the update, PxYra. Just to let you know, there are signed versions of VCOM drivers floating around so you don't need to mess with signature enforcement. Here's one: https://www.androidfilehost.com/?fid=24591000424943663. They are also updated by Windows so you can just let Windows Update install them.
Thanks for your work.
Flashing procedure works only with "MTK_AllInOne_DA.bin" method for me. But this is OK!
(Updated May 6, 2017: added kernel from firmware 5.3.7, source code cleanup)
Click to expand...
Click to collapse
is it possible to get the older versions? I need Android 6.x, because of xposed-Framework for my Zenpad 8.0 Z380M.
Greets Freisei
Hey freisei...
I never posted a version for Android 6. There was just one based on the 5.3.6 kernel, practically the same as the current one. That's why I didn't keep it. I could try to build one for you if you want, but I can't test it of course. Does this recovery not boot at all on the old firmware?
It's strange that the DA_PL.bin method didn't work for you. What happened when you tried it? I suppose the old preloader doesn't allow it(?).
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:05 PM ----------
Can anyone help me? after selecting recovery img, pressing download and inserting usb cable, nothing happens. Thanks in advance
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Pires_7 said:
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Click to expand...
Click to collapse
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Pires_7 said:
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
Click to expand...
Click to collapse
Nope, no chance.
diplomatic said:
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Nope, no chance.
Click to expand...
Click to collapse
Ok. I made some real s*it, I think I deleted every partition except recovery. Can you provide me a twrp backup or some way around my problem?
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
diplomatic said:
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
Click to expand...
Click to collapse
i was able to extract system.new.dat from stock firmware zip, but it extracts to a system folder. How do I flash this through sp flash tool?
OK, the system folder you don't need. It should have produced a system.img file also. That's the file you need to flash. Just select it for the system partition row in the partition list and then Download. Hopefully that will be enough.
EDIT: I just looked at the script, and realized the system.img.img file gets deleted in the process. So what you need to do is start the extraction, then after it makes system.img.img, when it starts extracting individual files, hit Ctrl+C. Then you'll end up with the img file.
Thank you very much! it works! YOU are the BEST!
please tell me, in your scatter file, address partition_name: frp (0x80a5000) is correct? if i format this partition (frp), google account remove?
Has anyone been able to figure out how to root the Alcatel idealXTRA (5059r)? I have been able to make a modded boot image with Magisk but I can not flash it to my phone because I need a DA file for SP Flash Tool specifically for this phone
I've been able to unlock the bootloader with Android "Tool all in one" which i found on here sometime ago. Actually have gotten a "successful" flash thru adb bootloader but with no effect on the device. I've tried a variety of tools, you'll need MtkDroidTools (Mediatek specific tool) and a host of other things and pherhaps you'll have some luck. I however did not. It appears that this specific device and its hardware are simply beyond my skills in rooting which are extensive so I question the viability of the exercise all together. That being said I still devote multiple hours a month attempting.
SUCCESS!!
The DA file your speaking of is actually located in the SP Tool folders : \SP_Flash_Tool_v5.1904_Win\\MTK_AllInOne_DA.bin
Disclaimer this method is finicky at best but on my device has worked, I take no responsibility for bricked/destroyed devices nor voided warranties. This simply resembles the method I used to successfully root my Alcatel 5059r Device nothing more
Alright I'm going to do a small write up with links for you. I'm assuming you have your bootloader unlocked and Magisk rooting is sufficient bc if its not well your not going to be able to root this device. First we need stock firmware, magisk manager 7.0, and the flashing tool that works with this phones MediaTek CPU.
HTML:
https://alcatelfirmware.com/alcatel-onetouch-ideal-xtra-5059r
Here you'll find both the stock firmware and the SP Flash Tool for this particular hardware.
You'll also need the latest Magisk Manager app on your phone(great idea for after you root if you've saved it on your SD as well as its the first thing you want to install after). You can find that on XDA or Github or a simple google search.
In short you need to patch the stock firmwares boot.img with Magisk Manager in order to gain root.
Once you've downloaded your Firmware, Tool, and .apk of Magisk Manager extract the boot.img from the stock firmware .zip/.rar then move it a storage path somewhere you can find it on your device. THEN DELETE THE BOOT.IMG THAT REMAINS IN THE .ZIP FOLDER
Start magisk manager and you'll probably get a big red X on Magisk 18.1, press it and install > patch boot image, select the stock boot.img we extracted to your pc then moved to your device.
With the Patch_boot.img move it off your devices storage back onto windows. Then add it back into the .zip/.rar Stock Firmware folder. Now we have a complete set of stock firmware flashed with Magisk 18.1 and ready to go!
Now you have a properly rooted boot.img now onto the flash
SP Flash Tool is a finicky tool at best, I always got error codes but was successful. Start off by shutting off your phone and unplugging the USB if your connected.
Extract the patched stock firmware .zip/.rar
Extract SP Flash tool, and run the flashtool.exe
From here you can follow the basic instructions on the website I posted
If you need an Auth file run a search here in XDA and you'll find a nice little .zip with an Auth file in it that works.
Your Scatter file is in the stock firmware, Auth file above.
With your phone still off & disconnected and your 3 drop boxes on the SP Flash Tool full and looking like the guide on the website. Press download. Attach your phone to USB and hit Volume up or down. Here is kind of the tricky part and trust me error codes don't necessarily mean there was any error. I ended up using the windows chimes to tell when the device was picked up, it disconnects pretty quickly but in between connection/disconnect chimes you have enough time to hit download again and you should get a Red Line on the bottom of SP tool saying 100% Completed, although probably with an error code. I did this routine of flashing in between chimes probably 10 times.
Reboot and yes your phone has been wiped, first thing you'll want to do is reinstall magisk manager and with any luck you should have green checks beside both boxes.
Proofs
https://forum.xda-developers.com/picture.php?albumid=15313&pictureid=58444
https://forum.xda-developers.com/picture.php?albumid=15313&pictureid=58445
Rooted with magisk and built twrp
deleted
Well in case anyone wants to work on this I'm uploading TWRP
deleted
deleted
Deleted
deleted
Can't seem to get root to work on gsi
deleted
Here's some good stuff and how I got recovery and LOS 16 on alcatel idealxtra 5059r
https://forum.xda-developers.com/an...16-alcatel-t3933004/post79586479#post79586479
LgPWN'd said:
Here's some good stuff and how I got recovery and LOS 16 on alcatel idealxtra 5059r
https://forum.xda-developers.com/an...16-alcatel-t3933004/post79586479#post79586479
Click to expand...
Click to collapse
EVEN BETTER LOOK AT OUR TELEGRAM GROUP
https://t.me/Android_General_Chat
ROMS
TOOLS
RECOVERIES
ROOT LIVES THERE
come join in the fun
INFINIX HOT S 3 ROOTING PROCEDURE WITH LOCKED BOOTLOADER
Things You must First Do
1. Install Qualcomm drivers for your PC
2. Learn how to remove the device back cover:
3. Learn how to boot the device to EDL mode :
4. Learn how to backup your device full firmware with a box like miracle box or cracked version :
5. Learn how to flash firmware with QFIL tool version 2.0.1.9 :
PROCEDURE 1
1. Get hold of your device full stock firmware. Some build numbers do not have stock firmware especially my Hot S3 build number do not have correct stock firmware.
2. Install latest official magisk manager apk.
3. Copy stock boot.img to your device internal storage.
4. Launch magisk manager app, select install magisk 18.1v or any version that will appear, there will be an options select patch boot.img. Now locate where you stored your boot.img. After patch magisk will show you the location of the patched bootimg.
5. Copy the patched boot.img into the device firmware folder. Remove the original boot.img from the firmware folder and save it somewhere and rename the patched boot.img to boot.img.
6. Now launch the QFIL tool and flash using the previous procedure.
7. After successful flash, boot to the device recovery (Volume up + power button) wipe partition and factory wipe, then power off and reboot.
8. After reboot update Google play store and services sign into your account successfully to have a recognize certify device. Install magisk manager apk. Launch magisk manager app, update and install any other updates that will pop up. Every installed thing in magisk will show green.
9. Reboot. The device successfully rooted.
NOTE:
1. Those who have their correct official firmware and have tested and working correctly, there will be firehose file, patch0 file, rawprogram0 files, NON-HLOS file. These are the necessary files for the flashing.
2. Those who don't have the correct stock firmware use the backup firmware from the miracle and rename these files as;
boot= boot.img
Cache= cache.img
dummy= dummy.img
misc= misc.img
persist= persist.img
recovery= recovery.img
splash= splash.img
system= system.img
userdata= userdata.img
aboot= emmc_appsboot.mbn
Modem=NON-HLOS bin
The rest of the files add .mbn to it end.
You need:
patch0.xml
rawprogram0.xml
prog_emmc_firehose_8937_ddr.mbn
if you don't have these files I will upload my full prepared stock firmware so that you take all the necessary files from it into yours and flash.
But if you have any downloaded stock HOT S 3 firmware with only one system and vendor inside you can use it.
3. Those who have their stock firmware, if the system and vendor in the folder is in multiple form meaning more than one ( system and vendor are in parts) you can't use QFIL tool to flash, it require different flash tool. Use your backup firmware.
4. If any find things difficult I will upload my stock firmware so that all builds can use to create their own stock firmware.
Thank you.
5. After every flash try to remove battery cable and replace for some seconds when the device cover is opened.
6. At a point where the device refuse to boot or power off, long press power button to power off or reboot.
7. Do not be in haste, take your time to follow all these procedures to avoid the device going dead. Because a device does not go dead in my hands. It may brick but when you use good and required flash files everything will be okay.
With ease, convenience and future developments for the device I have created Facebook group for that because some informations are hard to come by. I have posted a lot of help in different forums, nobody seems to help, so this how far I have gone. Now trying to Port custom recovery like twrp for the device even though bootloader is locked.
Procedure 2
1. Follow procedure 1 to backup device
2. Patch boot.img with magisk manager
3. Copy patched image rename as boot.img into backup folder.
4. Flash only the patched boot.img by any supported tool.
5. Reboot device install magisk manager apk reboot and update magisk done.
Those who have already rooted or gone far with the device can join the facebook group or provide me better links. Thanks
Facebook Group Link: https://www.facebook.com/groups/324251668449205/
CREDITS
Thanks to XDA for creating this wonderful platform
The best App ever magisk
The best tool ever Miracle box
Hamenth Jabalpuri my best friend XDA Senior Member
Thanks to everyone.
CAUTION
If any want to use this information in his site, don't forget to credit XDA.
TWRP LINK
https://forum.xda-developers.com/android/development/unofficial-twrp-infinix-hot-s3-x573-t4064705
Skyhuppa said:
Hamenth Jabalpuri my best friend XDA Senior Member
Click to expand...
Click to collapse
Thank you too for sharing this.....
Great tutorial thx
i can't get into edl mode
i used the shorting method via the back cover.. the device was blinking... was detected in device manager but when i clicked on port inside miracle box... nothing happened
i am trying to dump the firmware
Skyhuppa said:
INFINIX HOT S 3 ROOTING PROCEDURE WITH LOCKED BOOTLOADER
Click to expand...
Click to collapse
aus7een said:
i used the shorting method via the back cover.. the device was blinking... was detected in device manager but when i clicked on port inside miracle box... nothing happened
i am trying to dump the firmware
Skyhuppa said:
INFINIX HOT S 3 ROOTING PROCEDURE WITH LOCKED BOOTLOADER
Click to expand...
Click to collapse
I'm not getting your device blinking well but;
1. Make sure your device driver 9008 in edl mode installed well. When you open device manager you must see driver 9008 for your device. Download driver
https://www.allmobitools.com/download/Qualcomm_HS_USB_QDLoader_9008_Driver_Download.zip
2. If you are using windows 10 make sure you disable driver signature before installing any driver on your computer
3. Make sure you disconnect and reconnect battery cable on the board before and after every connection.
4. Use the miracle tutorial when you see driver Qloader 9008 in device manager after connecting device.
5. You must connect the two edl points well. Poor connection boot to battery charge.
6. Use miracle 2.82 version
Click to expand...
Click to collapse
did you have TWRP for infinix hot s3?
Nice well done thanks for sharing
agnitoya said:
did you have TWRP for infinix hot s3?
Click to expand...
Click to collapse
Not yet unless bootloader is fully unlocked.
Flash???
which file should i flash it,becouse i dont have the file... and almost all my frimware have .bak at the end so which flasher i should use,QFIL or others? heres the link of the pic of it
Nthn_Knt said:
which file should i flash it,becouse i dont have the file... and almost all my frimware have .bak at the end so which flasher i should use,QFIL or others? heres the link of the pic of it
Click to expand...
Click to collapse
Where did you get the .bak firmware files? Qfil can't flash such firmware. Use mobilsea tool or emmc tool.
Skyhuppa said:
INFINIX HOT S 3 ROOTING PROCEDURE WITH LOCKED BOOTLOADER
Things You must First Do
1. Install Qualcomm drivers for your PC
2. Learn how to remove the device back cover:
3. Learn how to boot the device to EDL mode :
4. Learn how to backup your device full firmware with a box like miracle box or cracked version :
5. Learn how to flash firmware with QFIL tool version 2.0.1.9 :
PROCEDURE 1
1. Get hold of your device full stock firmware. Some build numbers do not have stock firmware especially my Hot S3 build number do not have correct stock firmware.
2. Install latest official magisk manager apk.
3. Copy stock boot.img to your device internal storage.
4. Launch magisk manager app, select install magisk 18.1v or any version that will appear, there will be an options select patch boot.img. Now locate where you stored your boot.img. After patch magisk will show you the location of the patched bootimg.
5. Copy the patched boot.img into the device firmware folder. Remove the original boot.img from the firmware folder and save it somewhere and rename the patched boot.img to boot.img.
6. Now launch the QFIL tool and flash using the previous procedure.
7. After successful flash, boot to the device recovery (Volume up + power button) wipe partition and factory wipe, then power off and reboot.
8. After reboot update Google play store and services sign into your account successfully to have a recognize certify device. Install magisk manager apk. Launch magisk manager app, update and install any other updates that will pop up. Every installed thing in magisk will show green.
9. Reboot. The device successfully rooted.
NOTE:
1. Those who have their correct official firmware and have tested and working correctly, there will be firehose file, patch0 file, rawprogram0 files, NON-HLOS file. These are the necessary files for the flashing.
2. Those who don't have the correct stock firmware use the backup firmware from the miracle and rename these files as;
boot= boot.img
Cache= cache.img
dummy= dummy.img
misc= misc.img
persist= persist.img
recovery= recovery.img
splash= splash.img
system= system.img
userdata= userdata.img
aboot= emmc_appsboot.mbn
Modem=NON-HLOS bin
The rest of the files add .mbn to it end.
You need:
patch0.xml
rawprogram0.xml
prog_emmc_firehose_8937_ddr.mbn
if you don't have these files I will upload my full prepared stock firmware so that you take all the necessary files from it into yours and flash.
But if you have any downloaded stock HOT S 3 firmware with only one system and vendor inside you can use it.
3. Those who have their stock firmware, if the system and vendor in the folder is in multiple form meaning more than one ( system and vendor are in parts) you can't use QFIL tool to flash, it require different flash tool. Use your backup firmware.
4. If any find things difficult I will upload my stock firmware so that all builds can use to create their own stock firmware.
Thank you.
5. After every flash try to remove battery cable and replace for some seconds when the device cover is opened.
6. At a point where the device refuse to boot or power off, long press power button to power off or reboot.
7. Do not be in haste, take your time to follow all these procedures to avoid the device going dead. Because a device does not go dead in my hands. It may brick but when you use good and required flash files everything will be okay.
With ease, convenience and future developments for the device I have created Facebook group for that because some informations are hard to come by. I have posted a lot of help in different forums, nobody seems to help, so this how far I have gone. Now trying to Port custom recovery like twrp for the device even though bootloader is locked.
Procedure 2
1. Follow procedure 1 to backup device
2. Patch boot.img with magisk manager
3. Copy patched image rename as boot.img into backup folder.
4. Flash only the patched boot.img by any supported tool.
5. Reboot device install magisk manager apk reboot and update magisk done.
Those who have already rooted or gone far with the device can join the facebook group or provide me better links. Thanks
Facebook Group Link: https://www.facebook.com/groups/324251668449205/
CREDITS
Thanks to XDA for creating this wonderful platform
The best App ever magisk
The best tool ever Miracle box
Hamenth Jabalpuri my best friend XDA Senior Member
Thanks to everyone.
CAUTION
If any want to use this information in his site, don't forget to credit XDA.
Click to expand...
Click to collapse
TWRP LINK
https://forum.xda-developers.com/android/development/unofficial-twrp-infinix-hot-s3-x573-t4064705
[noob]
I'm rooting for the first time so please bare with me and I want to be sure before I start.
1. Unlock OEM
2. Open odin and enter download mode
3. Add twrp in AP and click start
4. Hold button combination to enter twrp
(now the confusing part, what all do i need to install from sd card)
5. Install no-verify-opt...zip
6. Install RMM bypass (few videos/guides suggest to install few don't i dont understand)
7. Finally magisk
Now when and how do I install Alexis rom?
Please clarify regarding RMM bypass.
Also there are multiple version and sources for RMM and no verify zip files is there any official source? What do these two do?
Device : G960F
BackToAndroid said:
[noob]
I'm rooting for the first time so please bare with me and I want to be sure before I start.
1. Unlock OEM
2. Open odin and enter download mode
3. Add twrp in AP and click start
4. Hold button combination to enter twrp
(now the confusing part, what all do i need to install from sd card)
5. Install no-verify-opt...zip
6. Install RMM bypass (few videos/guides suggest to install few don't i dont understand)
7. Finally magisk
Now when and how do I install Alexis rom?
Please clarify regarding RMM bypass.
Also there are multiple version and sources for RMM and no verify zip files is there any official source? What do these two do?
Device : G960F
Click to expand...
Click to collapse
Very basically:
RMM Bypass zip - Prevents bootloader from re-locking itself when rebooting.
Download latest version ( v3 ) from here. Won't hurt your phone whether needed or not.
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
No-verity ziip - stops re-encryption when rebooting.
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
On Android Q I used this Multi disable zip instead of no-verity zip.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
May have to re-name the zip to add ' quota ' to file name.
For installing twrp use this guide
https://forum.xda-developers.com/ga...cross-device-development/twrp-exynos-t3763464
On the order of flashing, for me personally, I would get twrp working first ( with the above files ). ie: install twrp, install files, reboot to system, reboot into twrp then do a backup ( especially EFS partition ).
Flashing custom rom you will have to check in thread guide but generally requires wiping ( not format ) some partitions then install the rom
Then flash magisk.
All done using twrp.
I normally do all this in stages and backup before going on to next stage.
After a couple of months of deep research I have managed to find a solution to unlock bootloader and root our SMAO15F device.
1st step: If your on android 10 it's possible to unlock bootloader even if our device has that option by default.
Fortunately with the newly released of official android 11 we are able to do so all you gotta do is you have to jump to android 11 if you're still on android Q then proceed to the unlocking method.
2nd step: after bootloader unlock download this .tar file (patched boot image for android 11 samsung sma015f).
Final process: Go to download mode, open latest odin and import the attached file with the AP button, phone will automatically restart after the process or restart it manually if not,
voila our samsung a01 is now rooted without twrp. Now we just have to wait for someone to make a custom twrp for our device or wait for official twrp or kindly please let me know if there is.
Credits: to that russian guide for the patched boot file for android11 (sma015f)
Cool bro!, but, how i'm unlock the bootloader for A01?
ROOT WITH MAGISK 23 WORKING 100% ON ANDROID 11 JUST UPGRADE UNLOCK BOOTLOADER AND FOLLOW THE INSTALLATION GUIDE https://topjohnwu.github.io/Magisk/install.html
Kaik Ricardo said:
Cool bro!, but, how i'm unlock the bootloader for A01?
Click to expand...
Click to collapse
Vol+ and Vol - and plug the usb cable then long press vol+
Hello,
Finally, I can unlock the bootloader, flash twrp and root my Samsung Galaxy A01 (a01q) (SM-A015M).
All I need is just update to Android 11 and then I can unlock the bootloader and flash the magisk patched boot.img together the patched vbmeta.img.
I can flash TWRP using the image file "TWRP_3.5.2_A015F.img" sent by @tariqa
How To Root Samsung A01 (a015f/DS)
Hello, I want to ask how to root samsung galaxy a01 (a015f) , i want to instal f.lux for better blue light filter, Thanks!
forum.xda-developers.com
Thank you very much
1. Unlock your bootloader enter in download mode Vol+ + Vol- + USB conected to pc (Keep in mind that by doing this you will lose your files, it is advisable to make a backup of your photos, music, etc.)
2. Once you start your cell phone install magisk manager, Choosing the boot.img file of your rom into the app (Tip: Only!!! If your model is SM-A015M Android 11 I leave you my own modified boot.img to flash:
File on MEGA
mega.nz
Otherwise, you can download the firmware (3.79 gb) and extract the boot.img from the firmware of your model SM-A015 M / F ... Android 10, Android 11... etc. And No need for pc
https://samfrew.com/model/SM-A015M/
3. The image will begin to flash
4. When it restarts you will have Root on the cell phone!
------------------------------------------------------------------------------------------------------------------------------------------------
Extra: If you need the custom recovery I give you the link with my TWRP which is installed through the Odin program on a PC (this step does not delete your files)
File on MEGA
mega.nz
Keep in mind that to install TWRP you must deactivate the DM-VERITY & FORCEENCRYPT DISABLER I leave it in a link:
Zackptg5 - Android
zackptg5.com
This is a module that can be installed via magisk, which is necessary to decrypt the system ... so once TWRP is installed, it is advisable to uninstall it via Magisk to avoid R / W errors
Marti_Fajardo said:
After a couple of months of deep research I have managed to find a solution to unlock bootloader and root our SMAO15F device.
1st step: If your on android 10 it's possible to unlock bootloader even if our device has that option by default.
Fortunately with the newly released of official android 11 we are able to do so all you gotta do is you have to jump to android 11 if you're still on android Q then proceed to the unlocking method.
2nd step: after bootloader unlock download this .tar file (patched boot image for android 11 samsung sma015f).
Final process: Go to download mode, open latest odin and import the attached file with the AP button, phone will automatically restart after the process or restart it manually if not,
voila our samsung a01 is now rooted without twrp. Now we just have to wait for someone to make a custom twrp for our device or wait for official twrp or kindly please let me know if there is.
Credits: to that russian guide for the patched boot file for android11 (sma015f)
Click to expand...
Click to collapse
after flashing the AP, the phone won't boot and says can't load android system.
edit: i patched my own AP with Magisk and it worked.
So i managed to upgrade my samsung a01m/ds to android 11 & i had unlocked the bootloader. Afterwards i had use the magisk rooting process, then flashed a boot.img that i had extracted from firmware (if needed i will upload) then the phone restated and took like 7 minutes to start, having said that i setup my device but upon doing so i noticed i was not able to use wifi but i had mobile data , managed to get in and install root checker pro and i had root but there was root( will leave an image ) but i didn't enjoy the fact that the wifi was not working, my hotspot wasn't working. i never managed to install TWRP becuase i was tampering a little more and trip my knox. it's been like 2 months since it trip and the OEM UNLOCKING in developer options is yet to be visible so i can unlock the oem and start a fesh.
Marti_Fajardo said:
After a couple of months of deep research I have managed to find a solution to unlock bootloader and root our SMAO15F device.
1st step: If your on android 10 it's possible to unlock bootloader even if our device has that option by default.
Fortunately with the newly released of official android 11 we are able to do so all you gotta do is you have to jump to android 11 if you're still on android Q then proceed to the unlocking method.
2nd step: after bootloader unlock download this .tar file (patched boot image for android 11 samsung sma015f).
Final process: Go to download mode, open latest odin and import the attached file with the AP button, phone will automatically restart after the process or restart it manually if not,
voila our samsung a01 is now rooted without twrp. Now we just have to wait for someone to make a custom twrp for our device or wait for official twrp or kindly please let me know if there is.
Credits: to that russian guide for the patched boot file for android11 (sma015f)
Click to expand...
Click to collapse
I managed to root my phone using this method but after I rooted, my wifi was stuck at turning on. I would then restore it to its stock firmware to have the wifi back and it did, but then I rooted again and wifi got stuck again. How do I fix this problem?
Johnmarr said:
I managed to root my phone using this method but after I rooted, my wifi was stuck at turning on. I would then restore it to its stock firmware to have the wifi back and it did, but then I rooted again and wifi got stuck again. How do I fix this problem?
Click to expand...
Click to collapse
Did you try to enable or disable MAC randomizing?
how
VD171 said:
Did you try to enable or disable MAC randomizing?
Click to expand...
Click to collapse
How do I enable or disable mac randomizing?