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
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
Hello
I bought a new Oppo A5 2020 and want to recovery my Titnaium Backups.
I search now 8-10 Hours to find a solution to root my phone, but no tutorial works.
I want to root my phone with Magisk and the right boot.img but i found only this file:
CPH1931_11_A.08_190905_cb4610de.ofp
I can not extract the ofp without some hardware parts.
Has anyone a idea how to root the Oppo A 2020 CPH1931
(CPH1931EX_11_A.08)
(CPH1931EX_11_A.13) <<- now aviable
Thank u so much
deadmeiker said:
Hello
I bought a new Oppo A5 2020 and want to recovery my Titnaium Backups.
I search now 8-10 Hours to find a solution to root my phone, but no tutorial works.
I want to root my phone with Magisk and the right boot.img but i found only this file:
CPH1931_11_A.08_190905_cb4610de.ofp
I can not extract the ofp without some hardware parts.
Has anyone a idea how to root the Oppo A 2020 CPH1931
(CPH1931EX_11_A.08)
(CPH1931EX_11_A.13) <<- now aviable
Thank u so much
Click to expand...
Click to collapse
Me too
me three
deadmeiker said:
Hello
I bought a new Oppo A5 2020 and want to recovery my Titnaium Backups.
I search now 8-10 Hours to find a solution to root my phone, but no tutorial works.
I want to root my phone with Magisk and the right boot.img but i found only this file:
CPH1931_11_A.08_190905_cb4610de.ofp
I can not extract the ofp without some hardware parts.
Has anyone a idea how to root the Oppo A 2020 CPH1931
(CPH1931EX_11_A.08)
(CPH1931EX_11_A.13) <<- now aviable
Thank u so much
Click to expand...
Click to collapse
Me four. I want to root my A5 2020
Can you boot into bootloader? Cause i can't stay in bootloader mode.
Me 5..
Setting - about phone - tap "version" 7 times
Additional option - developer option - oem unlock bootloader
Tried download ota
Extracted from phone manager.. and got boot.img
But magisk say its corrupted.. maybe it cant read it.. some says to use its recovery.img but i cant find it.. im a noob in rooting so i cant opt to experiment
Tried these things (3rd might be a possiible solution)
1.)
I tried using the OTA update which is a .ozip file, and needs a certain key to be usable (Needs to be decrypted to zip), key differs depending on the device
as for reference:
filedesc.com/en/file/ozip
tried tools such as
github.com/bkerler/oppo_ozip_decrypt
(But with no luck, A5 2020 isn't supported)
2.)
I found something on the web which is the CPH1931_11_A.08_190905_cb4610de.ofp
which i cannot decrypt to get the boot.img file
3.)
If your willing to take the risk, i found this
forum.gsmdevelopers.com/oppo-android-unified/84350-oppo-a5-2020-cph1931-dead-boot-alive-akshay-bhandare.html
which leads to the boot.img here (Just extract then you'll find boot.bin, change the file extension to boot.img (Just replace/rename .bin to .img))
mediafire.com/file/8kb8ilgz0mxaga3/OPPO_A5_2020%2528CPH1931_%2529DEAD_BOOT_ALIVE_BY_AKSHAY_BHANDARE.rar/file
(If link doesn't work anymore, ill upload the one I've downloaded already)
I tried patching this using Magisk and it works, but i haven't tried flashing it to A5 2020
Thank u so much[/QUOTE]
---------- Post added at 04:43 PM ---------- Previous post was at 04:17 PM ----------
KrisAmaba said:
1.)
I tried using the OTA update which is a .ozip file, and needs a certain key to be usable (Needs to be decrypted to zip), key differs depending on the device
as for reference:
filedesc.com/en/file/ozip
tried tools such as
github.com/bkerler/oppo_ozip_decrypt
(But with no luck, A5 2020 isn't supported)
2.)
I found something on the web which is the CPH1931_11_A.08_190905_cb4610de.ofp
which i cannot decrypt to get the boot.img file
3.)
If your willing to take the risk, i found this
forum.gsmdevelopers.com/oppo-android-unified/84350-oppo-a5-2020-cph1931-dead-boot-alive-akshay-bhandare.html
which leads to the boot.img here (Just extract then you'll find boot.bin, change the file extension to boot.img (Just replace/rename .bin to .img))
mediafire.com/file/8kb8ilgz0mxaga3/OPPO_A5_2020%2528CPH1931_%2529DEAD_BOOT_ALIVE_BY_AKSHAY_BHANDARE.rar/file
(If link doesn't work anymore, ill upload the one I've downloaded already)
I tried patching this using Magisk and it works, but i haven't tried flashing it to A5 2020
Click to expand...
Click to collapse
If your going to try the 3rd possible solution in rooting Oppo A5 2020
DISCLAIMER NOTICE
* I'm not responsible for bricked devices, dead SD cards or thermonuclear war.
* 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.
Here's what you need
Download ADB and Fastboot files and extract them in the C:/drive. (Windows/MAC)
getdroidtips.com/how-to-install-adb-and-fastboot-on-windows
Download and Install Oppo USB Drivers.
getdroidtips.com/download-oppo-usb-drivers/
Oppo A5 2020 (Boot.img)
mediafire.com/file/8kb8ilgz0mxaga3/OPPO_A5_2020%2528CPH1931_%2529DEAD_BOOT_ALIVE_BY_AKSHAY_BHANDARE.rar/file
Here are the steps:
(Steps to do on your Phone)
1. Download the boot.img (Originally boot.bin in the link given)
2. Download Latest Magisk Manager
github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
3. Launch Magisk Manager. When a popup appears asking to install Magisk, select INSTALL and choose install again.
4. Tap on “Patch Boot Image File”
5. Navigate to internal storage and select your phone’s boot image that you've downloaded earlier.
6. Wait for a couple of seconds. Magisk will start patching the boot image.
7. Once the boot image has been patched, copy the “patched_boot.img” from the internal storage and replace it in the ADB fastboot extracted ROM folder on your PC.
(Steps to do on your PC)
1. We assume that you have already downloaded the ADB & Fastboot tool from the link given above.
2. Now, extract the ADB fastboot tool, then move the patched boot image to the same folder.
3. Hold the Shift key and right-click on the mouse to open the command window/PowerShell.
4. Next, enter the following command:
Flash the “patched_boot.img” to install Magisk and root your Android device:
fastboot flash boot patched_boot.img
The flashing process will begin. Once done, run
fastboot reboot
5. Done, Open Magisk to see if it's successful
---------- Post added at 04:52 PM ---------- Previous post was at 04:43 PM ----------
KrisAmaba said:
If your going to try the 3rd possible solution in rooting Oppo A5 2020
DISCLAIMER NOTICE
* I'm not responsible for bricked devices, dead SD cards or thermonuclear war.
* 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.
Here's what you need
Download ADB and Fastboot files and extract them in the C:/drive. (Windows/MAC)
getdroidtips.com/how-to-install-adb-and-fastboot-on-windows
Download and Install Oppo USB Drivers.
getdroidtips.com/download-oppo-usb-drivers/
Oppo A5 2020 (Boot.img)
mediafire.com/file/8kb8ilgz0mxaga3/OPPO_A5_2020%2528CPH1931_%2529DEAD_BOOT_ALIVE_BY_AKSHAY_BHANDARE.rar/file
Here are the steps:
(Steps to do on your Phone)
1. Download the boot.img (Originally boot.bin in the link given)
2. Download Latest Magisk Manager
github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
3. Launch Magisk Manager. When a popup appears asking to install Magisk, select INSTALL and choose install again.
4. Tap on “Patch Boot Image File”
5. Navigate to internal storage and select your phone’s boot image that you've downloaded earlier.
6. Wait for a couple of seconds. Magisk will start patching the boot image.
7. Once the boot image has been patched, copy the “patched_boot.img” from the internal storage and replace it in the ADB fastboot extracted ROM folder on your PC.
(Steps to do on your PC)
1. We assume that you have already downloaded the ADB & Fastboot tool from the link given above.
2. Now, extract the ADB fastboot tool, then move the patched boot image to the same folder.
3. Hold the Shift key and right-click on the mouse to open the command window/PowerShell.
4. Next, enter the following command:
Flash the “patched_boot.img” to install Magisk and root your Android device:
fastboot flash boot patched_boot.img
The flashing process will begin. Once done, run
fastboot reboot
5. Done, Open Magisk to see if it's successful
Click to expand...
Click to collapse
Forgot to Mention, that before proceeding to the steps to do on your PC
you need to do this.
1. Setting - about phone - tap "version" 7 times (To unlock Developer Option)
2. Additional option - developer option - oem unlock bootloader
3. Additional option - developer option - allow USB Debugging
4. turn off device
5. Volume up + power button if logo appears, stop pressing
6. Connect to PC (then proceed to the given steps)
Anyone try this method?
jayaduana said:
Anyone try this method?
Click to expand...
Click to collapse
I bought this phone 24-1-2020. I wanna know to if anyone tried this method.
yes!it works...
Can more people (mainly the ones who allrdy did comment in this thread) confirm method 3 is working?
I updated to CPH1931EX_11_A.28. Do i need a patched boot.img of CPH1931EX_11_A.28 or can i use any boot.img of all versions?
I wanted to know if the boot.img for all versions is the same.
i.daniyal said:
yes!it works...
Click to expand...
Click to collapse
i dont know how u've managed it. i can't boot into fastboot, using vol down + power buttons or using adb reboot bootloader. can u tell me how to boot into fastboot?
Is your OPPO A5 2020 rooted now
jayaduana said:
i dont know how u've managed it. i can boot into fastboot, using vol down + power buttons or using adb reboot bootloader. can u tell me how to boot into fastboot?
Click to expand...
Click to collapse
Do i understand, you did try method 3 using the boot.img provided in the link?
You were able to patch the boot.img with magisk?
Did you flash the patched boot.img to phone successfully? If so, its safe to use the boot.img provided in the link?
Are you rooted now?
I really need root in order to get boldbeast call recording working properly with pie 9.
jayaduana said:
i dont know how u've managed it. i can't boot into fastboot, using vol down + power buttons or using adb reboot bootloader. can u tell me how to boot into fastboot?
Click to expand...
Click to collapse
Read the instructions carefully it's vol up ?
Typo
hotcold65 said:
Read the instructions carefully it's vol up
Click to expand...
Click to collapse
That has to be a typo, because for the OPPO A5 2020 its powerbutton + volume down
ron23ny said:
That has to be a typo, because for the OPPO A5 2020 its powerbutton + volume down
Click to expand...
Click to collapse
Yes, when use volume up, its keep restarting. When use volume down, its login to coloros recovery mode,not fastboot mode.
jayaduana said:
Yes, when use volume up, its keep restarting. When use volume down, its login to coloros recovery mode,not fastboot mode.
Click to expand...
Click to collapse
Can you please answer my questions in post #12, i really need to know if you rooted successfully.
i.daniyal said:
yes!it works...
Click to expand...
Click to collapse
Some guidance please, or was your answer just a prank?
Ok, i tried to get in fastboot mode with command adb reboot bootloader. I do get the fastboot logo screen for a second, but then it just loading the OS pie 9, like someone stated here before. I read in some sources, OPPO company disabled the fastboot mode for this phone, so you will not able to flash files using adb. I also read power + volume down = recovery mode (working) and power + volume up = fastboot mode (not working because company disabled this).
I use firmware CPH1931EX_11_A.28. Now the big question: does somebody know, if some older version of firmware has fastboot not disabled by company?
Seems for now, you can only root this phone by using hardware tools like miracle box and easy jtag pro.
gffg
ron23ny said:
Can more people (mainly the ones who allrdy did comment in this thread) confirm method 3 is working?
I updated to CPH1931EX_11_A.28. Do i need a patched boot.img of CPH1931EX_11_A.28 or can i use any boot.img of all versions?
I wanted to know if the boot.img for all versions is the same.
Click to expand...
Click to collapse
I also using CPH1931EX_11_A.28 and have exact same bootloader problem.
I manage to extract boot.img from 11_A.13 and 11_A.28 firmwares using "ubuntu ozip to zip" and files appear identical and patched successfully using Magisk. The boot.img provided in the link is not the same, I wouldn't use it.
Did you find out if some older version of firmware has fastboot not disabled by company?
Many thanks for taking time to read reply.
Sotirious said:
I also using CPH1931EX_11_A.28 and have exact same bootloader problem.
I manage to extract boot.img from 11_A.13 and 11_A.28 firmwares using "ubuntu ozip to zip" and files appear identical and patched successfully using Magisk. The boot.img provided in the link is not the same, I wouldn't use it.
Did you find out if some older version of firmware has fastboot not disabled by company?
Many thanks for taking time to read reply.
Click to expand...
Click to collapse
Still no luck. Fastboot is disabled.
Hello everyone, my phone is samsung note 10 plus, I have twrp installed and rooted with magisk, I'm on Android 9, I somehow lost root, have no idea how, I'm very careful not to allow updates or google to install something there might affect my root.
when I go to magisk I'm getting the image that I've attached, when I click on install magisk, download the zip file and try to install it I get an an error as show in the 2nd image, saying unsupported/unknown image forma. I've also attached the log file. Is there any way for me to fix this without flashing the rom and start from scratch? Can I repair it somehow, maybe with TWRP?
Thank you all in advance
you have boot.img of the device?
i thought you can only install magisk in 2 way by flashing boot.img unto magisk or flashing magisk.zip unto TWRP as recovery partition
#edit how did you install magisk in the beginning? thats how you will install it again
there a chance you will get your device brick if you install magisk wrong way (A/B partition) but since you already install it previously just reinstall it back
Hmmm, where should I have the boot. Img you mean as if I backed it up on my pc? Or I can download it and use it?
Now I'm confused :/
Before i explain i don't take responsibility for any damages caused on your device if you decided to follow my tutorial .
So basically there's 2 way to install Magisk
• Image Patching - Basically this is what most people do they find stock boot.img and recovery.img for there devices
1. Copy the Stock boot.img or recovery.img to your device
2. Download and install the latest Magisk Manager
If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
Press Install → Install → Select and Patch a File, and select your stock boot or recovery image file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Now pull the magisk_patched.img with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched boot.img or recovery.img to your device and reboot.
For most devices, here is the fastboot command:
fastboot flash boot magisk_patched.img or
fastboot flash recovery magisk_patched.img if you are patching a recovery image
Now you are rooted
•Custom Recovery - This is when you do not have Stock boot.img or recovery.img for your device
( High Chance Of Phone Getting Bricks )
1. Download and install the latest Magisk Manager
2. Download Magisk.zip (https://github.com/topjohnwu/Magisk/releases/) choose the Latest Release
3.Now reboot to recovery (TWRP, CWM ... ETC)
if you use stock recovery it should say "apply update via sdcard"
then just choose Magisk.zip
4. Now if you have TWRP just click Install and choose Magisk.zip
5. wait for the process
6. Now you are Rooted (hopefully xD :fingers-crossed
ineedroot69 said:
Before i explain i don't take responsibility for any damages caused on your device if you decided to follow my tutorial .
So basically there's 2 way to install Magisk
• Image Patching - Basically this is what most people do they find stock boot.img and recovery.img for there devices
1. Copy the Stock boot.img or recovery.img to your device
2. Download and install the latest Magisk Manager
If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
Press Install → Install → Select and Patch a File, and select your stock boot or recovery image file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Now pull the magisk_patched.img with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched boot.img or recovery.img to your device and reboot.
For most devices, here is the fastboot command:
fastboot flash boot magisk_patched.img or
fastboot flash recovery magisk_patched.img if you are patching a recovery image
Now you are rooted
•Custom Recovery - This is when you do not have Stock boot.img or recovery.img for your device
( High Chance Of Phone Getting Bricks )
1. Download and install the latest Magisk Manager
2. Download Magisk.zip (https://github.com/topjohnwu/Magisk/releases/) choose the Latest Release
3.Now reboot to recovery (TWRP, CWM ... ETC)
if you use stock recovery it should say "apply update via sdcard"
then just choose Magisk.zip
4. Now if you have TWRP just click Install and choose Magisk.zip
5. wait for the process
6. Now you are Rooted (hopefully xD :fingers-crossed
Click to expand...
Click to collapse
Thank you very much.
OK, I tried method 2 and didn't work. I downloaded my stock firmware and I have the image file, I can try the first one to place the image in the root of the phone, patch the file with magisk and reflesh it with Odin?
Will I lose all my stuff on the phone by doing this? Thank you
i remember using odin back in 2012 for my samsung galaxy y i didn't know people still using that thing
i search your device on google and it said samsung provide the kernel for it ( https://www.xda-developers.com/samsung-galaxy-note-10-kernel-source-code/amp/ ) thats a good start for rooting your device try looking for it
also visit https://forum.xda-developers.com/galaxy-note-10 it is dedicated section for your device model which means all threads and post are for your device model
ineedroot69 said:
i remember using odin back in 2012 for my samsung galaxy y i didn't know people still using that thing
i search your device on google and it said samsung provide the kernel for it ( https://www.xda-developers.com/samsung-galaxy-note-10-kernel-source-code/amp/ ) thats a good start for rooting your device try looking for it
also visit https://forum.xda-developers.com/galaxy-note-10 it is dedicated section for your device model which means all threads and post are for your device model
Click to expand...
Click to collapse
Im already rooted....
Im having issues how to fix the root as i somehow don't have it any more and i don't want to reflash my rom if I'll lose all my stuff on the phone. Im looking how to fix the root.
drazenm said:
Im already rooted....
Im having issues how to fix the root as i somehow don't have it any more and i don't want to reflash my rom if I'll lose all my stuff on the phone. Im looking how to fix the root.
Click to expand...
Click to collapse
He's just saying to re-root it... If you lost root it's more than likely gone and you'll have to do whatever you did to gain root in the beginning. I constantly backup all my apps, data, pictures and everything to my little USB OTG thumb drive and to my laptop. I do this daily because many times a factory reset is what has to happen depending on what's going on. You can grab a Samsung micro sdcard 128 GB for $18-$19 or so online or thumb drives like I have a SanDisk 128gb.. it was $14. Just some thoughts for moving ahead so you don't have to go through this again. Lots of good suggestions here. If I were you I'd hit the "thanks" button on whenever took time to stop and search for answers to your issue. That's what we do here on xda. I could care less about racking up "thanks" count just throwing that out there so that you know..
Good luck on getting her all fixed. The note 10 is a real gem!
Sent from my marlin using XDA Labs
flash713 said:
He's just saying to re-root it... If you lost root it's more than likely gone and you'll have to do whatever you did to gain root in the beginning. I constantly backup all my apps, data, pictures and everything to my little USB OTG thumb drive and to my laptop. I do this daily because many times a factory reset is what has to happen depending on what's going on. You can grab a Samsung micro sdcard 128 GB for $18-$19 or so online or thumb drives like I have a SanDisk 128gb.. it was $14. Just some thoughts for moving ahead so you don't have to go through this again. Lots of good suggestions here. If I were you I'd hit the "thanks" button on whenever took time to stop and search for answers to your issue. That's what we do here on xda. I could care less about racking up "thanks" count just throwing that out there so that you know..
Good luck on getting her all fixed. The note 10 is a real gem!
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
I can re root it, that's not the problem, i can do it with the patched magisk boot image through Odin, im asking if that's gonna wipe off everything on my phone. Because i can't backup certain things without titanium backup, and titanium requires root access. Thank you for your help and everyone's else's im well aware and grateful for the attempts, suggestions etc.
no it's not gonna wipe anything thats why magisk is called "systemless" . It will essentially modify the system without actually modifying it.
if you flash magisk_patched.zip nothing noticeable will happen except you will have root access
all your installed application will be there
also i notice this some people actually copy magisk_patched.zip thats really bad idea you need to let Magisk generate it.
For example you have 2 phones same model and same build version .
You generate magisk_patched.zip on the phone A
then decided to copy magisk_patched.zip into phone B ofcourse it will still works
but since you just copy it and didnt let magisk generate it . It would not make backup for boot or recovery partition
if you uninstall Magisk on your phone B .There is really high super ultra mega chance of your phone getting bricks. Also it would not revert any changes done on the period while Magisk is installed
ineedroot69 said:
no it's not gonna wipe anything thats why magisk is called "systemless" . It will essentially modify the system without actually modifying it.
if you flash magisk_patched.zip nothing noticeable will happen except you will have root access
all your installed application will be there
also i notice this some people actually copy magisk_patched.zip thats really bad idea you need to let Magisk generate it.
For example you have 2 phones same model and same build version .
You generate magisk_patched.zip on the phone A
then decided to copy magisk_patched.zip into phone B ofcourse it will still works
but since you just copy it and didnt let magisk generate it . It would not make backup for boot or recovery partition
if you uninstall Magisk on your phone B .There is really high super ultra mega chance of your phone getting bricks. Also it would not revert any changes done on the period while Magisk is installed
Click to expand...
Click to collapse
Thanks for the help, please correct me if im wrong.
Im supposed to copy the AP . md5 file to the root directory of my phone, patch it with magisk, get the patched file, copy it on the pc, connect phone to the pc, get it into download mode, flash the patched file with Odin and that should be it?
Or maybe i can do it with twrp?
Any suggestions?
drazenm said:
Any suggestions?
Click to expand...
Click to collapse
1. Install the latest Magisk Manager
2. In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
3. Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
4. Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck "Auto Reboot" in Options!
5. Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
6. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the S10 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
7. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
8. This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
9. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
10. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
11. Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
12. Voila! Enjoy Magisk
credit to @Magisk github
you can read the full tutorial here https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
ineedroot69 said:
1. Install the latest Magisk Manager
2. In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
3. Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
4. Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck "Auto Reboot" in Options!
5. Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
6. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the S10 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
7. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
8. This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
9. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
10. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
11. Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
12. Voila! Enjoy Magisk
credit to @Magisk github
you can read the full tutorial here https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
Click to expand...
Click to collapse
Thanks so much for your help, but i just want to get root back on my phone as i had it rooted already, i dont want to wipe off everything and lose my stuff. There are things that i can only backup with titanium backup, which i can't use now without root privileges :/ can i repair root somehow?
how did you lose your root anyway?
your Android OS updated?
you can try restoring apps with titanium backup but i don't think it will restore Magisk being installed again and gaining root access
ineedroot69 said:
how did you lose your root anyway?
your Android OS updated?
you can try restoring apps with titanium backup but i don't think it will restore Magisk being installed again and gaining root access
Click to expand...
Click to collapse
I didn't do the update, but something did mess up the root aa you can see on the photos that I've attached at the beginning of the topic. I just want to reroot my phone again but not to loose all my current stuff on it.
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
ineedroot69 said:
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
Click to expand...
Click to collapse
thank you for taking your time to help me out, i appreciate it.
here is the link to the firmware file:
https://androidfilehost.com/?fid=6006931924117937015
inside are these files:
AP_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_low_ship_meta_OS9.tar.md5
BL_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_low_ship.tar.md5
CP_N975FXXU1ASH5_CP13587367_CL16618471_QB25409313_REV01_user_low_ship.tar.md5
CSC_OMC_OXM_N975FOXM1ASH5_CL16618471_QB25349308_REV01_user_low_ship.tar.md5
HOME_CSC_OMC_OXM_N975FOXM1ASH5_CL16618471_QB25349308_REV01_user_low_ship.tar.md5
ineedroot69 said:
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
Click to expand...
Click to collapse
Any luck?
drazenm said:
Any luck?
Click to expand...
Click to collapse
sorry for late reply i'm kinda busy but to make it easier on my part (downloading 5GB file would take me 5 hours) can you just upload the following ?
AP_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_ low_ship_meta_OS9.tar.md5
BL_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_ low_ship.tar.md5
CP_N975FXXU1ASH5_CP13587367_CL16618471_QB25409313_ REV01_user_low_ship.tar.md5
Please read this guide fully before attempting to follow it. It requires some knowledge of how to use a Terminal and basic ADB/Fastboot operation. I don't think this guide is thorough enough for a person who's modifying their phone for the very first time. Feel free to ask for help though!
I am not reliable for any adverse effects this guide might have on your phone. If something breaks, that's your responsibility. However: if your phone doesn't boot anymore, but you can still get into fastboot, you should be able to flash the Stock Firmware OFP using the Realme Flash Tool. To get into fastboot, power off your phone, wait a few seconds, and hold power and volume down until you see the fastboot logo.
This guide was cobbled together using various other tutorials and my own attempts. I've used it on my RMX2075. It should also work for the RMX2076. The files Realme provides for the RMX2075 are named "RMX2076", so I assume they're the same device. I have no idea how the RMX2071 fits into this. Curiously, the TWRP version used here is intended for the RMX2071, although it works flawlessly on my RMX2075. However: if you're using it on an RMX2075/2076 TWRP thinks you're using an RMX2071, so it won't flash packages intended for the RMX2075/2076. Hence the following warning:
!!! YOU WON'T BE ABLE TO INSTALL OTA UPDATES AFTER INSTALLING TWRP !!!
If you attempt to install an OTA Update downloaded from within the Settings.app, the phone will reboot, TWRP will attempt to install the OTA Update and fail with an error. This does not break anything, it just doesn't update.
DOWNLOADS:
- Realme Flash Tool
- Stock Firmware OFP
- OTA Update OZIP
- TWRP 3.4.1b for RMX2071 by wzsx150 and LR. Team
Spoiler: further details
The licensing of this TWRP is pretty unclear, so I can't provide a download link. If you search for it Online, make sure to find a version that includes both "recovery.img" and "misc.bin"
- Realme DeepTesting App
- Magisk Manager by topjohnwu
- oppo ozip decrypt
PREPARATION:
- install ADB & Fastboot on your computer
- enable "USB debugging" on your phone
- install the oppo ozip decryption tool by following the instruction on the GitHub page
UNLOCKING
- follow the unlock instructions provided by the official Realme Tutorial
RESTORING AND UPDATING - if you're on firmware A42, skip this step
- follow the restore instructions provided by the official Realme Tutorial
- go to the Realme Software Update page, click on "How to update?" and follow the instructions
FLASH TWRP
- open a Terminal window and cd into the folder that holds recovery.img and misc.bin
cd /path/to/folder
- enter the following commands and hit enter after each
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash misc misc.bin
fastboot reboot recovery
- your phone should now reboot into TWRP
- enter your phones unlock code if you have one
- go to "Advanced" -> "Disable Replace TWRP"
- reboot phone
ROOTING
DO NOT use "Install Root" in TWRP, it'll "destroy" the bootloader and you'll have to flash the stock firmware
Follow this instead:
- decrypt the OTA .ozip using the oppo ozip decrypt tool (instructions on its GitHub page)
- unzip the resulting decrypted file
- copy "boot.img" onto your phone
- copy "/firmware-update/vbmeta.img" into a folder of your choice
- install Magisk Manager on your phone
- open Magisk Manager, tap on "Install" followed by "Select and Patch a File"
- select the "boot.img" you've previously copied onto your phone and let Magisk do its thing
- the patched "boot.img" is called "magisk_patched_XXXX.img" or something similar. Make note of the resulting file name which is specific to you.
- copy the patched "magisk_patched_XXXX.img" into the same folder that holds your "vbmeta.img"
- open a terminal and cd into the folder that holds the patched "boot.img" and "vbmeta.img"
- enter the following commands and hit enter after each
adb reboot bootloader
in the following step, replace "magisk_patched_XXXX.img" with whatever your patched "boot.img" is called
fastboot flash boot magisk_patched_XXXX.img/ICODE]
[ICODE]fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
- your phone should now be rooted
I have also uploaded the stock boot.img along with the rooted version as well as vbmeta.img here. They were created using the method described above with OTA update A42. I would recommend creating your own though, since this has a higher chance of success.
Another method to get the stock boot.img and vbmeta.img is creating a TWRP backup, renaming "boot.emmc.win" to "boot.img", and "vbmeta.emmc.win" to "vbmeta.img". I have NOT TESTED this method.
I don't know if this will work for Android 11 / ColorOS 2.0. My theory is that if you can get the RMX2076PU_11.C.16.ozip somewhere, you could just follow this guide using it instead of the A42 one. Again, I have NOT TESTED this method.
Unfortunately does not work with Android 11. The result is that the phone stays in the fastboot. The Realme flash tool doesn't work anymore. The phone is now bricked. Let's see if I can reach the service now. Isn't the first time they haven't answered. Now actually needs the MSM tool. But haven't found a working one yet.
corneo said:
Unfortunately does not work with Android 11. The result is that the phone stays in the fastboot. The Realme flash tool doesn't work anymore. The phone is now bricked. Let's see if I can reach the service now. Isn't the first time they haven't answered. Now actually needs the MSM tool. But haven't found a working one yet.
Click to expand...
Click to collapse
Android 11twrp brush Android 10, and then brush Android 10twrp, you can boot
can u using volte with stock ofp eu version?