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.
Related
Guide to rooting infocus Epic 1 (for windows) for build 00.
This method is only tested on build 00IN_1_360 only. If you are on the older build, first update your phone to build 00IN_1_360 then proceed. Check Build number in settings->about phone.
Proceed at your own risk, I will not be help responsible if your phone bricks, Your warranty will be void after this. Also all phone data will be lost including data on internal memory like photos, etc after these steps so take necessary backups.
Prepare your system
1. Extract and Install MTK Driver Auto Installer v5.1632 (google it)
2. Install Phone F Driver (from phone CD-emulation/driver folder upon connecting your phone)
3. Minimal ADB and Fastboot installer v.1.4.2 (from xda)
4. Download latest SuperSU flashable zip file from here
5. Download twrp-3.0.3-0-epic1-noveritynoencrypt.zip from here, extract in the folder where you have installed adb and fastboot
6. Download noencryptnoverty_boot.zip from attachments and extract to folder where you have installed adb and fastboot
Steps to root:
1. Enable Developer options in phone settings (goto phone settings -> about phone -> tap build number 7 times)
1a. Enable OEM unlock
1b. Enable USB Debugging
2. Connect phone to computer, wait for hardware to auto install
3. open cmd as administrator
3a. goto the directory where adb and fastboot is installed
4. type command:
4a.
adb reboot bootloader
(Wait for phone to come in fastboot)
4b.
fastboot OEM unlock
(press vol up key on phone)
4c.
fastboot flash boot noveritynoencrypt.img
4d.
fastboot flash recovery recovery.img
4e.
fastboot reboot
You will get an phone orange state prompt, do not worry its normal. Phone may reboot once or twice. Wait for phone to normal bootup.
5. open cmd and type command
5e.
adb reboot recovery
Phone will reboot in recovery i.e. TWRP
6. Tap on Keep system read-only. Do not swipe to allow modifications. If TWRP asks for password, don't enter any press back.
7a. Tap Wipe -> Format Data. Come out to main menu, then click reboot and then recovery to restart recovery.
7b. Tap Wipe -> Advanced Wipe -> Select Dalvik /ART, Cache, Data and Internal Storage. This is important step, as these partitions are encrypted at the moment, so if you flash anything the phone rom may corrupt.
8. Come out and then Tap Reboot -> System
9. Once the phone is back, turn off the phone. Then power on with vol up key pressed to boot into TWRP
10. Tap Backup, select all partitions, select phone storage (SD card preferred) and take backup (optional step but highly recommended )
11. Now tap install, goto the location where you had copied SuperSU zip file, flash it.
Congratulations your Phone is rooted. Reboot, see SuperSU icon in app drawer.
Many thanks to @mujammil786 for providing stock files and @Bornstud for testing twrp builds
Special thanks to our devs @DespairFactor for modifying boot.img to disable Encryption and Verity and @kirito9 for creating TWRP for our device. Without their help, it wouldn’t have been possible.
MODS
(Take backup of your ROM/Data before applying any mods)
Viper4Android (Advanced Sound Enhancement)
Hugely Customizable and better than MaxxAudio or Dolby Atmos IMHO
Now working on our device Infocus Epic 1
Need to flash the 2 attached files via TWRP before installing the official app from HERE. Although latest version v2.5.0.5 also works, but i personally prefer v2.4.0.1 (busybox required)
(Note the attached files are not my work, they are picked from here and here. Say thanks to original contributors.)
Good V4A profile: HERE
Extract it to ViPER4Android Directory in internal Storage
Xposed
Needs no introduction. Every android enthusiast should know what it is. Anyway if you are new, xposed opens limitless ROM customization(s) and useful features via 100s of its modules.
Installation:
1. Flash framework xposed-v87-sdk23-arm64.zip from HERE via TWRP. Reboot after installation will take long time (~10 - 15 minutes)
2. Install app XposedInstaller_3.1.1.apk from HERE
Restoring phone back through SUT
If you are stuck somewhere or want to restore the phone factory state (like for when giving to repair), you can restore the phone back via SUT
Link for build 1280: https://firmwarefile.com/infocus-epic-1
Also dont turn off your phone as suggested in sut readme file. It only works when your phone is on. Check below vid for more instructions
https://m.youtube.com/watch?v=eV_cId5fC9E
Reduce battery consumption & phone temperature
Found an interesting thread, mod works on our device also
https://forum.xda-developers.com/red...tings-t3687897
I have tried both flavor 1 and flavor 2 over the past week. Results with flavor 1 were positive in the beginning but for some reason standby drain shot up after 3-4 days, not sure what the reason was.
On flavor 2, I have just disabled MTK perfservice by setting
ro.mtk_perfservice_support = 0 in build.prop
Yes this limits the a72 core to 1.5ghz, but i have noticed phone is heating less and need for charging the phone has reduced. I haven't noticed much drop in performance either, but that might be as I don't use intensive apps.
Mafioso said:
I've managed to unpack nb0 file through a688 tool, however its only successful in unpacking few files before it crashes with some array size error, but the good thing is I was able to extract the scatter file for this phone before it happened.
Anyway, I was hopeful that I would be able to make backup of Stock ROM and Recovery through it via spflash tools however as it turns out, spflash tool is giving me error while doing readback BROM ERROR: STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003)
Not sure how to fix it, i've updated my drivers as well as i'm using latest version of spflash tool (SP_Flash_Tool_v5.1628_Win)
Attaching scatter file.
Click to expand...
Click to collapse
From where uve downloaded the stock firmware
Romeotamizh said:
From where uve downloaded the stock firmware
Click to expand...
Click to collapse
http://firmwarefile.com/infocus-epic-1
Mafioso said:
http://firmwarefile.com/infocus-epic-1
Click to expand...
Click to collapse
Oh
---------- Post added at 08:17 AM ---------- Previous post was at 08:17 AM ----------
Romeotamizh said:
Oh
Click to expand...
Click to collapse
Look in other sites bro for img files
Romeotamizh said:
Oh
---------- Post added at 08:17 AM ---------- Previous post was at 08:17 AM ----------
Look in other sites bro for img files
Click to expand...
Click to collapse
Hmm yaa, but at the moment no sites with for .img file for this phone. All sites point to this image only. Let's hope somebody posts. Thanks!
Mafioso said:
Hmm yaa, but at the moment no sites with for .img file for this phone. All sites point to this image only. Let's hope somebody posts. Thanks!
Click to expand...
Click to collapse
Ooh bro I'm happy to help but seriously i Duno about these kind of extensions hope u understand
Mafioso said:
I'm trying to root Infocus Epic 1, its a good budget phone with decent specs. Availability is only in India, not sure other regions. Anyway I'm having hard time to root it, since not much support is available. But so far, I have tried below things:
1. Tried to root with Kingroot, doesn't work .Probably because it is very new version of Marshmallow with Oct'16 patch level and kernel dated in dec 16.
2. Tried to generate scatter file via MTK Droid tool v2.5.3, after enable USB debugging in phone. The phone get detected in the tool, however create scatter file option in block map is disabled I've read somewhere, it might be due to MTK6797 (Helios x20) is quite new and is not yet fully supported by tool yet. Not sure if its true though. But if I can generate scatter file, I can extract phone's stock recovery via SPFlash tool readback to try a hand at porting twrp/cwm with some help..
3. Downloaded stock Infocus Epic 1 firmware in hope for recovering stock recovery.img or MTK scatter file, however on unpacking the firmware package, I found it contains unknown image file of nb0 extension which is it to be flashed via SUT Tool. Not sure how to unpack this file
Any more ideas, how can i atleast start with my quest to root/put custom recovery on this phone ? @Romeotamizh Pls help.
Click to expand...
Click to collapse
I can give u stock recovery of epic 1..
mujammil786 said:
I can give u stock recovery of epic 1..
Click to expand...
Click to collapse
how bro, are you able to get it via SPFlash tool readback option or are you able to unpack the nb0 file ?
Anyway you should post it here, somebody else might pick it up and build twrp for it. At the moment, I'm stuck with SPFlash tool unable to readback my phone as stated above , doubt i would be able to flash anything to test
Mafioso said:
how bro, are you able to get it via SPFlash tool readback option or are you able to unpack the nb0 file ?
Anyway you should post it here, somebody else might pick it up and build twrp for it. At the moment, I'm stuck with SPFlash tool unable to readback my phone as stated above , doubt i would be able to flash anything to test
Click to expand...
Click to collapse
I was able to extract it from last update zip
---------- Post added at 04:45 PM ---------- Previous post was at 04:33 PM ----------
Epic 1 stock recovery
https://drive.google.com/file/d/0B4FNo4vddleCNmpwcS1hS3FLam8/view?usp=drivesdk
mujammil786 said:
I was able to extract it from last update zip
Click to expand...
Click to collapse
ok I see, please post it here. I can update it in the first post. Might be useful for anyone willing to develop for this phone.
Also did you try to read-back the phone via SPFlash tool ? I'm running into issues, but maybe i'm not doing something correctly. Might be you will have better luck.
Mafioso said:
ok I see, please post it here. I can update it in the first post. Might be useful for anyone willing to develop for this phone.
Also did you try to read-back the phone via SPFlash tool ? I'm running into issues, but maybe i'm not doing something correctly. Might be you will have better luck.
Click to expand...
Click to collapse
Well i tried but i got ctrl device error ,btw i have uploaded stock recovery
mujammil786 said:
Well i tried but i got ctrl device error ,btw i have uploaded stock recovery
Click to expand...
Click to collapse
thanks, updated first post.
Mafioso said:
thanks, updated first post.
Click to expand...
Click to collapse
Thanks let's hope for best
I like this phone and the only thing lacking is Root, Hope someone will do it
I hope so too. However, it seems its not that straight forward anymore i.e. communicating with SPFlash tool on newer MTK chipsets. I was going through guides for LeTV x620 (also with MT6797), not sure but it seems they require authentication file now for the process, which might not be available for our phone.
I already tried all the other download agents like DA_PL.bin, DA_PL_High.bin, DA_BR.bin in flash tool through which this LeTV is able to communicate, it's same error for us with all.
Also other curious thing, I was unable to run any fastboot commands on this phone. The phone gets detected in fastboot when put in fastboot mode (vol - + power) i.e. I get output on fastboot devices.
However If i try to run any commands like fastboot oem get-bootinfo or fastboot oem device-info I get error message remote command unknown
Mafioso said:
I hope so too. However, it seems its not that straight forward anymore i.e. communicating with SPFlash tool on newer MTK chipsets. I was going through guides for LeTV x620 (also with MT6797), not sure but it seems they require authentication file now for the process, which might not be available for our phone.
I already tried all the other download agents like DA_PL.bin, DA_PL_High.bin, DA_BR.bin in flash tool through which this LeTV is able to communicate, it's same error for us with all.
Also other curious thing, I was unable to run any fastboot commands on this phone. The phone gets detected in fastboot when put in fastboot mode (vol - + power) i.e. I get output on fastboot devices.
However If i try to run any commands like fastboot oem get-bootinfo or fastboot oem device-info I get error message remote command unknown
Click to expand...
Click to collapse
My device does not get detect in fastboot can u show me screen shot of command u are trying....
mujammil786 said:
My device does not get detect in fastboot can u show me screen shot of command u are trying....
Click to expand...
Click to collapse
If it's not detected maybe its related to your drivers. I've installed the following drivers
1. Try installing the Phone F Driver (from phone CD-emulation upon connecting)
2. MTK Driver Auto Installer v5.1632.00 (you can get from needrom)
3. Minimal ADB and Fastboot installer v.1.4.2 (from xda)
Run cmd as administrator:
adb reboot bootloader
When phone reboots in fastboot mode
fastboot devices
You should see your phone being detected from above.
Mafioso said:
If it's not detected maybe its related to your drivers. I've installed the following drivers
1. Try installing the Phone F Driver (from phone CD-emulation upon connecting)
2. MTK Driver Auto Installer v5.1632.00 (you can get from needrom)
3. Minimal ADB and Fastboot installer v.1.4.2 (from xda)
Run cmd as administrator:
adb reboot bootloader
When phone reboots in fastboot mode
fastboot devices
You should see your phone being detected from above.
Click to expand...
Click to collapse
Ok will try thanx
bootloder get unlocked and locked too
ok so phone get detected in fastboot mode:victory: .was able to lock and unlock boot loader but without custom recovery it is no useful for us.
unlocked bootloader.
tried flashing Vernee_Apollo_Lite_P6(same spec. as epic 1) twrp recovery.
flashing done but after flashing phone refused to boot.
flashed stock recovery from update zip.
locked bootloader.
phone booted but erased internal memory after boot.
---------- Post added at 11:47 AM ---------- Previous post was at 11:44 AM ----------
do you know any guide for making twrp and i think phone will not boot if it detect any change in system partition i think
Hi everyone,
This is what I have done to root my Teclast T8 with Magisk (based on this chineese forum: http://tieba.baidu.com/p/5449087481)
1-First download the official firmware from Needrom.com (You need to register): https://www.needrom.com/download/teclast-t8-e8c1/
2-Go to the Firmware folder and copy the “boot.img” file to the root directory of your tablet
3-Download and install MagiskManager on the tablet, click on Install, then choose to patch the boot image file. Choose the boot.img you’ve just uploaded to your tablet and it will start to automatically patch it.
Then go into the File Manager and go to the MagiskManager folder and find the “patch_boot.img“ and copy it to the root directory (without copying it to the root directory, you can not find the file from your pc…), then sends the file from the tablet to your computer.
4-For me the method with SP Flash Tool don’t work, because it says the scatter file is wrong (don’t know why…)
So i have to do it with adb and unlock the bootloader first:
-connect the tablet to pc, (first you have to enable OEM unlocking and USB debugging in Developer options)
-reboot the tablet in fastboot mode, hold buttons “power+Vol +” at startup, choose fastboot mode with Vol+ button, valid with Vol-
- open a command prompt in adb folder, then “fastboot devices”, then “fastboot oem unlock”, it should say “OKAY, finished”
Your bootloader is now unlock.
-then copy the “patched_boot.img” in the adb folder and tap in command prompt “fastboot flash boot patched_boot.img”, then “fastboot reboot”.
Your tablet should be rooted.
I think you can relock bootloader after... don't try yet.
PS: This is my first thread, so be indulgent ?
Don’t ask me technical questions because I am not a developer , just a simple user …
Hope this will help.
If someone find a way to find and flash a TWRP or how to install Xposed, please tell me, thx.
Rooted using same method but SP Flash Tools worked in my tablet.
Waiting for a TWRP ....
Yes, can confirm that method works for root.
Also tried the T10 TWRP and it's not working on the T8, just a black screen.
Don't need TWRP yet, some bugs in the ROM are more annoying than that
hi all
somebody tried the new rom v1.10 on needrom ??
marinero57 said:
hi all
somebody tried the new rom v1.10 on needrom ??
Click to expand...
Click to collapse
Hi guys i jus download v1.10 rom but have no idea how to flash, everything in chinesse... even recovery, how do you flash? the tablet have a TelcastOTA apk installed, this have a local update option allow to load firmware from sd, anyone used this app? what files should i put in SD?
thanks in advance
HI quick question what rom have u installed in ur T8, mine came with 1.01, i see in needrom have 3 versions: 1.06. 1.08, 1.10, have u updated to any of these?
Thanks
Polo19 said:
Hi everyone,
This is what I have done to root my Teclast T8 with Magisk (based on this chineese forum: http://tieba.baidu.com/p/5449087481)
1-First download the official firmware from Needrom.com (You need to register): https://www.needrom.com/download/teclast-t8-e8c1/
2-Go to the Firmware folder and copy the “boot.img” file to the root directory of your tablet
3-Download and install MagiskManager on the tablet, click on Install, then choose to patch the boot image file. Choose the boot.img you’ve just uploaded to your tablet and it will start to automatically patch it.
Then go into the File Manager and go to the MagiskManager folder and find the “patch_boot.img“ and copy it to the root directory (without copying it to the root directory, you can not find the file from your pc…), then sends the file from the tablet to your computer.
4-For me the method with SP Flash Tool don’t work, because it says the scatter file is wrong (don’t know why…)
So i have to do it with adb and unlock the bootloader first:
-connect the tablet to pc, (first you have to enable OEM unlocking and USB debugging in Developer options)
-reboot the tablet in fastboot mode, hold buttons “power+Vol +” at startup, choose fastboot mode with Vol+ button, valid with Vol-
- open a command prompt in adb folder, then “fastboot devices”, then “fastboot oem unlock”, it should say “OKAY, finished”
Your bootloader is now unlock.
-then copy the “patched_boot.img” in the adb folder and tap in command prompt “fastboot flash boot patched_boot.img”, then “fastboot reboot”.
Your tablet should be rooted.
I think you can relock bootloader after... don't try yet.
PS: This is my first thread, so be indulgent
Don’t ask me technical questions because I am not a developer , just a simple user …
Hope this will help.
If someone find a way to find and flash a TWRP or how to install Xposed, please tell me, thx.
Click to expand...
Click to collapse
Flashing ROM with SP flashtool - Teclast Master T8 (E8C1)
Fossxp13 said:
Hi guys i jus download v1.10 rom but have no idea how to flash, everything in chinesse... even recovery, how do you flash? the tablet have a TelcastOTA apk installed, this have a local update option allow to load firmware from sd, anyone used this app? what files should i put in SD?
thanks in advance
Click to expand...
Click to collapse
Hi! I haven't used in built update app so I'll try to explain how to update using flashtool. Follow the steps with your device disconnected from the pc and take into account your files will be erased.
First of all, I recommend you to install ADB and fastboot drivers: 15 seconds ADB Installer
As OP said download the rom from NeedRom and unzip it: You will have three folders:
升级工具, which contains flashtool
固件程序, with the rom
驱动程序, with the drivers
Rename all of them as flashtool, rom and drivers, for example. If you don't, you may have troubles launching flashtool or loading the scatter file.
Launch flashtool as administrator (升级程序, you could rename it too), if you get the message "The scatter file cannot found, please make sure the file exist before download" ignore it. In flashtool make sure MTK_AllInOne_DA.bin is selected as Download-Agent and select the scatter file inside rom folder as Scatter-loading file. Choose firmware upgrade from the list and click the Download button (the one with the green arrow).
Finally, switch off your device and connect it to your pc. Flashtool should do the rest, wait untill "Download Ok" message is displayed. Close flashtool, disconnect your device and switch it on.
IF your computer doesn't load needed drivers automatically, flashtool won't start the process as expected. You will need to open device manager on windows, right click on your device - update driver - choose manually - browse "inf" folder inside drivers folder (choose x86 or x64 according to your OS).
Hope it works! Good luck.
Prevent Brick and Xposed for Teclast Master T8 (E8C1)
Polo19 said:
OP
Click to expand...
Click to collapse
Hi Polo19!
Thanks for your post, I rooted my tablet following it! But since I encountered some issues in the process I wanted to share my experience.
IMPORTANT: For a few hours I thought I hard bricked my device, so I hope I could help somebody.
When patching boot.img with MagiskManager IF the app automatically tics "Keep force encryption" choose "Keep dm-verify" aswell!
I don't know why but this was the only way to make it work on my device, I kept getting a encryption error after flashing the patched boot.img, despite the fact that I have never encrypted my device.
After getting that error I tried to flash the clean rom again, but flashtool gave an error and the tablet completely died! Well, it seemed so.
It's pretty stupid but the only way to make it work again was pushing the reset button on the top right corner of the tablet for a few seconds and flashing the rom again.
About Magisk: use the OFFICIAL MAGISK XDA THREAD to download it, as https://magiskmanager.com/ is NOT the official website.
In step 3, I couldn't find the patched_boot.img file even after moving it to the root directory. So I had to (let the patched_boot.img file in the default directory):
Install ADB drivers in the computer: https://forum.xda-developers.com/showthread.php?t=2588979
Enable USB debugging in developer options in the tablet, connect it to the computer and accept the connection.
Open command prompt / powershell: "shift + right click" wherever you want to copy the patched_boot.img and open cmd or power shell.
Run the command:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
In step 4: you won't encounter that problem if you rename downloaded folders and get rid of chinese characters. Simply open flashtool, choose the scatter file, untick all options except boot and change the default boot.img with the patched one (I renamed it to boot.img, I don't know if it's necessary)
Xposed: you can install xposed using MagiskManager.
Install Xposed Installer for Magisk, go to download tab in MagiskManager and install Xposed SDK24 (for android 7.0) and reboot
Sources:
15 SECONDS ADB INSTALLER
MAGISK
SYSTEMLESS XPOSED
CHINESE FORUM
Just need TWRP and I'm happy.
There's a chinese TWRP but it's not working decently.
Rotiaiso said:
Hi Polo19!
Thanks for your post, I rooted my tablet following it! But since I encountered some issues in the process I wanted to share my experience.
IMPORTANT: For a few hours I thought I hard bricked my device, so I hope I could help somebody.
When patching boot.img with MagiskManager IF the app automatically tics "Keep force encryption" choose "Keep dm-verify" aswell!
I don't know why but this was the only way to make it work on my device, I kept getting a encryption error after flashing the patched boot.img, despite the fact that I have never encrypted my device.
After getting that error I tried to flash the clean rom again, but flashtool gave an error and the tablet completely died! Well, it seemed so.
It's pretty stupid but the only way to make it work again was pushing the reset button on the top right corner of the tablet for a few seconds and flashing the rom again.
About Magisk: use the OFFICIAL MAGISK XDA THREAD to download it, as https://magiskmanager.com/ is NOT the official website.
In step 3, I couldn't find the patched_boot.img file even after moving it to the root directory. So I had to (let the patched_boot.img file in the default directory):
Install ADB drivers in the computer: https://forum.xda-developers.com/showthread.php?t=2588979
Enable USB debugging in developer options in the tablet, connect it to the computer and accept the connection.
Open command prompt / powershell: "shift + right click" wherever you want to copy the patched_boot.img and open cmd or power shell.
Run the command:
In step 4: you won't encounter that problem if you rename downloaded folders and get rid of chinese characters. Simply open flashtool, choose the scatter file, untick all options except boot and change the default boot.img with the patched one (I renamed it to boot.img, I don't know if it's necessary)
Xposed: you can install xposed using MagiskManager.
Install Xposed Installer for Magisk, go to download tab in MagiskManager and install Xposed SDK24 (for android 7.0) and reboot
Sources:
15 SECONDS ADB INSTALLER
MAGISK
SYSTEMLESS XPOSED
CHINESE FORUM
Click to expand...
Click to collapse
Yes, i also install Xposed using MagiskManager and it works. Now i am able to use all fonctions of Greenify, Amplify, Powernap and get a pretty decent standby batterylife.
marinero57 said:
hi all
somebody tried the new rom v1.10 on needrom ??
Click to expand...
Click to collapse
Hi, I tried to follow the procedure but in ROM 1.10 doesn't work
---------- Post added at 01:37 PM ---------- Previous post was at 12:44 PM ----------
With the news roms doesn't work...
What is the rom that was working this WA??
Thanks!
I just did this to a tablet that had OTA'd the 1.10 - using the 1.10's downloaded boot and latest Magisk Manager 5.5.4 / Magisk 15.3 beta
OEM Unlock, patching boot image and patched boot image flashing worked
BUT - the included Magisk Manager does not launch after installing upon reboot...
HOWEVER - V5.5.3 of the manager did work.
$ adb -s 0123456789ABCDEF install MagiskManager-v5.5.3.apk
Success
$ adb -s 0123456789ABCDEF shell
t8_e8c1:/ $ su
t8_e8c1:/ #
Notes
1. Tablet is wiped
2. Boot delay of 5 seconds is added with "can't be trusted" warning in white text
3. Fails safetynet
Letting MagiskManager update itself to 554 also worked - so I think my method of just installing the apk from the Magisk zip's common folder was wrong.
Kerrnel said:
I just did this to a tablet that had OTA'd the 1.10 - using the 1.10's downloaded boot and latest Magisk Manager 5.5.4 / Magisk 15.3 beta
OEM Unlock, patching boot image and patched boot image flashing worked
BUT - the included Magisk Manager does not launch after installing upon reboot...
HOWEVER - V5.5.3 of the manager did work.
$ adb -s 0123456789ABCDEF install *************-v5.5.3.apk
Success
$ adb -s 0123456789ABCDEF shell
t8_e8c1:/ $ su
t8_e8c1:/ #
Notes
1. Tablet is wiped
2. Boot delay of 5 seconds is added with "can't be trusted" warning in white text
3. Fails safetynet
Letting ************* update itself to 554 also worked - so I think my method of just installing the apk from the Magisk zip's common folder was wrong.
Click to expand...
Click to collapse
Hi,
My T8 arrived yesterday and I've used OTA to update to 1.10.
Is the sptools method working with 1.10 or do I need to use this process?
Also where to the numbers 0123456789ABCDEF come from in the instructions I've quoted?
Thank is advance
i have the ota 1.10 update and the rooting was successful. magisk and xposed working flawlessly.
another point:
i have closed the bootloader after flashing the patched boot.img with "fastboot oem lock".
the device boot up is faster and the warning "...5 seconds" is gone.
now, i wait for twrp.
You dont need to unlock bootloader.
Just flash patched_boot with flash tool.
Zaphodb69 said:
Hi,
My T8 arrived yesterday and I've used OTA to update to 1.10.
Is the sptools method working with 1.10 or do I need to use this process?
Also where to the numbers 0123456789ABCDEF come from in the instructions I've quoted?
Thank is advance
Click to expand...
Click to collapse
I had multiple devices attached to the PC.
No -s ABC... needed if you only have the one.
Sent from my T8(E8C1) using Tapatalk
The suggested worked for me. I will also mention that you must be connected to the internet to patch the boot.img file with magisk manager (otherwise, the option will not be presented in the magisk manager GUI).
Were there made any changes for the fingerprint? Soimebody mentioned, it isn´t that good. Maybe the last updates change something...
Requirements / Downloads
Honor 10 view BKL-09 with unlocked bootloader (I not tested in other version)
Minimal ADB & Fastboot
Patched Recovery_Ramdisk BKL
Rooting your device
1. Unzip Minimal ADB & Fastboot to any folder of your PC
2. Download the patched file for your device and copy it to Minimal ADB & Fastboot folder.
3. Start your smartphone in fastboot mode pressing [Vol-]+[Power] and connect it to your PC.
4. Open a Powershell window in your Minimal ADB & Fastboot folder by [Shift]+[Rightclick].
5. Flash the Recovery_Ramdisk:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
Adjusting Magisk Manager and patching files by yourself
1. Download Magisk Manager canary build to your phone and install.
2. Change in Magisk settings the update channel to "custom" inserting this URL. https://t2m.io/wuAFCrwO
Magisk Manager now will find the canary builds.
3. Check "force encryption" and "AVB 2.0" boxes.
To patch yourself recovery_ramdisk:
4.a) Patch your *.img, that you have copied in any folder to your smartphone by pressing "Install" --> "Install" --> "Patch boot image" in Magisk Manager.
ORIGINAL RECOVERY_RAMDISK BKL-09 PIE version 9.0.0.162 C432
5. Transfer the patched file (You will find it in your download folder of your smartphone. It will be called "patched_boot.img".) to your PC, start Smartphone in fastboot mode and flash:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
(You must adapt the file name to the real name of your file, e.g. patched_boot.img)
To actualize Magisk:
4.b) Choose in Magisk Manager: "Install" --> "Install" --> "Direct Install (Recommended)" --> Restart
Thanks
Thanks a lot for this great guide!
Hello, will this also be on my bkl-l09c432? I have rom
blazios said:
Hello, will this also be on my bkl-l09c432? I have rom
Click to expand...
Click to collapse
If your device is on pie ?, yes
What should I use twrp?
blazios said:
What should I use twrp?
Click to expand...
Click to collapse
OP never mentioned anything about twrp. That is not needed
I Have same version as you Android Pie and everythin firmware and region... But no matter how i try i get UNABLE TO UNPACK BOOT IMAGE... Instalation failed... why is that? i have TWRP installed... and everything as is your phone firmware and version 9.0.0.162 C432...
BlueMan_86 said:
I Have same version as you Android Pie and everythin firmware and region... But no matter how i try i get UNABLE TO UNPACK BOOT IMAGE... Instalation failed... why is that? i have TWRP installed... and everything as is your phone firmware and version 9.0.0.162 C432...
Click to expand...
Click to collapse
Flash in bootloader mode. Not in twrp.
Android pie not work with twrp for now.
I am on ROOTED EMUI 8.0 (BKL-L09 8.0.0.130). How do I update to pie and then root? First unroot than update than root? or just update and root with the instructions in post#1?
Sadly it does not work for me. Tried it with your patches bootimage and with my own. Flashing the ramdisk works fine but after restart I don't have root.
I dont need Magisk installed if I use the pre patches bootimage right? Nevertheless I tried with Magisk installed and without. In the Huawei Mate Forum I read that one might need to shutdown the phone after flashing and then to start it with Volume Up and Power Button pressed. But this also does not work. Or any Idea how exactly to start with this Key combination?
Any other suggestions?
Today I updated from OREO with root to PIE same version as you have in pictures 9.0.0.162(C432E4R1P9). Tried both steps (with your patched file and me patching file) to root my phone but even I always got OK in fastboot mode I still have no root
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
resdano said:
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
Click to expand...
Click to collapse
I get the same error
any advise ?
Worked like a breeze for me. Shoutout to @ante0 and @shashank1320 who kept their calm in guiding me through and suggesting me this method.
@ante0 made things easier for me and it worked excellently for me. The steps are-
Download and install Magisk canary builds from the mentioned link. Change in Magisk settings the update channel to "custom" inserting*this*URL.*https://t2m.io/wuAFCrwO
Magisk Manager now will find the canary builds.
Check "force encryption" and "AVB 2.0" boxes.
Transfer stock recovery ramdisk to phone, open Magisk Mnager and hit install - > patch boot image, select recovery_ramdisk.img. Take patched_boot.img from /sdcard/Download/ and transfer to computer, reboot to fastboot and flash patched_boot.img to recovery_ramdisk. Unplug USB, holv vol up + power to reboot to recovery, which will now boot phone with Magisk. If you reboot and don't hold vol up it will boot to system without root.
---------- Post added at 02:08 PM ---------- Previous post was at 02:01 PM ----------
Huge thanks @fabio84
Finally have root privileges on Pie.
resdano said:
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
Click to expand...
Click to collapse
davidsiv said:
I get the same error
any advise ?
Click to expand...
Click to collapse
Emui9 doesn't have a ramdisk partition. You flash to recovery_ramdisk, then when you reboot hold volume up to get to recovery (unplug USB as it will take you to erecovery if you have it plugged in).
This is the only way to get root on Emui9, currently.
It will not boot to recovery, it will boot to system with Magisk.
Not flash ramdisk. Need flash recovery_ramdisk!
worked, thanks
fabio84 said:
Not flash ramdisk. Need flash recovery_ramdisk!
Click to expand...
Click to collapse
@ante0 has been helping me get root access and we still are working on it.
@fabio84 did you by a chance experience issues in using root applications especially root explorer or root Uninstaller? For some reason they won't just work for me, just titanium and root checker works. On further scrutinising, I found the su binary files missing probably why the applications won't load for me. Any help?
ankan1993 said:
@ante0 has been helping me get root access and we still are working on it.
@fabio84 did you by a chance experience issues in using root applications especially root explorer or root Uninstaller? For some reason they won't just work for me, just titanium and root checker works. On further scrutinising, I found the su binary files missing probably why the applications won't load for me. Any help?
Click to expand...
Click to collapse
Update: @ante0 helped me yet again to figure it out. Apparently was because of pie's aggressive background restrictions. Root is now working full fledgedly. Thanks everyone. Big cheers to @ante0
Hello,
It finally worked for me. Thank you so much!
ante0 said:
Emui9 doesn't have a ramdisk partition. You flash to recovery_ramdisk, then when you reboot hold volume up to get to recovery (unplug USB as it will take you to erecovery if you have it plugged in).
This is the only way to get root on Emui9, currently.
It will not boot to recovery, it will boot to system with Magisk.
Click to expand...
Click to collapse
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
Hello everyone hope you are all keeping well.
Since I believe that many of you don't know about this, I've decided to share the steps I've done in order to root the OP 11R ( ACE 2 )
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
1 - Unlock the bootloader (if you haven't done it already...beware that this will erase all of your user data). To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
adb devices
adb reboot bootloader
(so your phone will reboot into fastboot mode)
fastboot flashing unlock
(device should now unlock)
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
2 - Download OP 11R stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your devices internal memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...you never know if you will need to use it again in the future...to restore the stock boot.img, aka revert to stock...)
Indian Boot.img A_0.8 - download
3 - Download latest Magisk Manager from HERE and install it on your phone
4 - Open Magisk Manager App and press:
Install
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
5 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
6 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
7 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
8 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
Why title says NORD 2T?
firoz3321 said:
Why title says NORD 2T?
Click to expand...
Click to collapse
MB ... typo
Thank you for detailed steps.
Is there any benefit with KernelSU over this method ?
I always used Magisk on OP8, but recently saw an article for OP11 with Kernel SU.
Also is there MSM tool support to recover softbriked device ?
firoz3321 said:
Thank you for detailed steps.
Is there any benefit with KernelSU over this method ?
I always used Magisk on OP8, but recently saw an article for OP11 with Kernel SU.
Also is there MSM tool support to recover softbriked device ?
Click to expand...
Click to collapse
Sorry but there is no msm tool available for new OnePlus devices. + You can use Fastboot enhance tool from github to recover softbrick , magisk is always recommended for rooting because of ease of steps and simple to use
Hello, thanks for the detailed instructions. Today I updated to A. 10, and unfortunately lost my root access. Without the root cannot extract the boot image. If you're already updated and have a backup of A. 10 boot, can you please share?
saifsohel said:
Hello, thanks for the detailed instructions. Today I updated to A. 10, and unfortunately lost my root access. Without the root cannot extract the boot image. If you're already updated and have a backup of A. 10 boot, can you please share?
Click to expand...
Click to collapse
i didn't got the update yet ... + oxygen updater also showing A.08. i will update this post soon as I got update
shiki_senpai said:
i didn't got the update yet ... + oxygen updater also showing A.08. i will update this post soon as I got update
Click to expand...
Click to collapse
Then remember to take a backup of the boot before rebooting. I messed up big time.
Thanks for the detailed information man. Can I know if bootloader unlock decreases widevine L1 to L3? As this was case with my OP6