As a OnePlus 9 user who likes to root their phone mainly to allow Network Signal Guru to work (as well as a few other root things like AdAway) I had been trying to extract the boot.img the same way as I had done with a OnePlus 7T using Payload Dumper for Windows. However it looks like Payload Dumper has issues with extracting xx.img files (including boot.img) if the payload.bin file is bigger than 4.3 GB in size. So I've been looking to see if another method was possible that would work for our OnePlus 9 ROMs that are above this file size. As I use Linux Mint as my usual desktop OS & only fall back onto Windows for stuff that'll only run on that OS, I went to have a look to see if something could be done under Linux. Turns out there is an old thread elsewhere on XDA that almost nearly provides what is needed for this, and I thought I would gives details here that should work for the time of this post (March 2023).
This not only extracts the boot.img to patch in Magisk, but also extracts other xx.img files as well.
I'm using Linux Mint 21.1, but I'd assume that this will also work for similar Ubuntu builds or anything that is based on Debian.
Obligatory disclaimer: The following instructions I'm giving below have worked well for me several times in the past, however I am in no way responsible for screwing up or damaging your phone if you try and follow what I've written below. In extreme cases, a bad flash may require using the OnePlus MSM tool to completely reflash your phone. Back up anything important first before doing any of the following!
1. You will need to ensure that you have downloaded packages to be able to do adb & fastboot from the command line. You can check by running the following commands - if it's already installed with the latest versions, the terminal interface will let you know...
Code:
sudo apt install adb
Code:
sudo apt install fastboot
2. You will need to go to your software manager in LM21.1 and install both Python 3 & the Python Protobuf compiler. Just search for "Python 3" & "Protobuf-compiler" in the software manager and the first option for each search is what you should need - if they are not installed, install them.
3. Create a read/writable directory that will hold your ROM that you've just downloaded & other files that I'll mention soon. I just use a folder calls "ROM" in my Downloads folder (e.g. /home/lawhec/Downloads/ROM ), but you can choose wherever you want that suits you.
4. If you have not done so already, make sure you have the FULL package of your OnePlus 9 ROM downloaded. As of right now (March 2023) it seems the best way is to download the package using the Oxygen Updater app which is available on Google Play - more info available at oxygenupdater.com - just download the ROM to your phone and transfer it on to your computer into the folder you've created for it.
5. Download and save the following two Python scripts/files ("Right click" & "Save Link As") into the folder you have just created for your ROM (all credit to Gregory Cyxx at github.com/cyxx )...
https://raw.githubusercontent.com/c...payload/master/extract_android_ota_payload.py
https://raw.githubusercontent.com/cyxx/extract_android_ota_payload/master/update_metadata_pb2.py
6. Make sure in your file browser (Nemo in my case as it is the default for LM21.1 Cinammon, yours may differ) the window is open in the ROM folder that contains the two Python scripts above that you've just downloaded as well as a ROM package (ZIP file) you've downloaded (in my case from Oxygen Updater mentioned in step 3). Create a new folder for the extracted images to be written to - in my case I just call the folder "output" which is located at "/home/lawhec/Downloads/ROM/output" but again you can call it what you wish.
7. After you've created your output folder, in your ROM directory in the file manager window right-click on your mouse in a white or free space and select "Open in Terminal" - a command terminal will pop up defaulting to your directory.
8. In the command terminal, type the following command and press enter/return...
Code:
sudo python3 extract_android_ota_payload.py <<Your ROM.zip>> <<Your Output Directory>>
...for example, in my case the command would be either...
Code:
sudo python3 extract_android_ota_payload.py LE2113_11_F-75.zip output
...or for handiness you can type "sudo python3 extract_android_ota_payload.py " (remember to leave a space) and simply drag the ROM zip file to the command terminal, press space and then drag the output foler to the terminal line, which will look like in my case...
Code:
sudo python3 extract_android_ota_payload.py '/home/lawhec/Downloads/ROM/LE2113_11_F-75.zip' '/home/lawhec/Downloads/ROM/output'
...this will now run the python script you downloaded earlier that will begin extracting the ROM you've specified and will output all relevant xx.img files into your output folder, including the one we want, "boot.img" - there is no need to extract paylod.bin beforehand, the script will automatically do this for you. Once all xx.img files have been extracted the script will stop, depending on your computer this will take anything from 1-5 minutes, maybe longer on some very old or low spec'd computers - but just let it run its course. Once it is done you can then close the terminal window.
9. Now with the boot.img we've extracted, transfer this file on to your phone (the Downloads folder is usually a good choice). Now open Magisk and patch the boot.img file - once this has been completed, it'll generate a patched boot.img file named something like "magisk_patched-25200_12345.img" - copy and paste this patched boot image back on to your computer (into the folder you've been using will be fine here).
10. If your OnePlus 9 phone is connected to your computer via USB cable, disconnect it now. Then shutdown your phone into a power-off state then reboot it into fastboot mode - this can be done by holding down the volume up & down buttons, then holding down the power button and keep holding down all three buttons until you feel a vibration from your phone. Your OnePlus 9 should then boot into fastboot mode.
11. Now reconnect your OnePlus 9 to your computer via the USB cable and then open up a new display terminal (preferably by right-clicking in the file window of the directory where you saved your Magisk patched boot.img file). Enter the following...
Code:
fastboot devices
...you should then get a line featuring a block of numbers that should match the serial number that is displayed on your phone's display, followed by "fastboot", for example...
Code:
85f53405 fastboot
...if you get anything else, double check your connections at try again - if more than one device is displayed, disconnect the and try again to make sure that only one device is listed. It might also be the case that you don't have the proper drivers installed on your computer for your phone though in my case LM21.1 automatically recognises my phone, so I'm not of any direct help here I'm afraid for this, sorry.
12. Now you will be flashing your patched boot.img to your phone - this is where things can be a little nervous though as long as you do everything right nothing should really go wrong. Type the following into the command terminal, assuming you did so by opening a command terminal from the folder your Magisk Patched boot.img file is located...
Code:
fastboot flash boot <<Magisk Patched boot.img>>
...for example in my case the command line would be...
Code:
fastboot flash boot magisk_patched-25200_12345.img
...otherwise you will need to provide the location of where your patched boot.img is, so in this case...
Code:
fastboot flash boot '/home/lawhec/Downloads/ROM/magisk_patched-25200_12345.img'
...either way, your phone will now be in the process of getting its boot image replaced with the one patched by Magisk. This should take no more than a few seconds and that should be it done! You can then close the terminal window again.
13. Once you've patched the boot image, disconnect the phone from the USB cable to the computer and make sure that the screen on your mobile says "START" in green at the top, if it doesn't, use the volume keys to change this. Then just simply press the power button and your phone will now reboot, this can take a little bit longer than before as your phone's firmware has changed so give it time - (however if it takes longer than 10 minutes or so you might have a problem here) - once your home screen becomes available, give it a few seconds once you've entered before selecting the Magisk app. Once you've done this, Magisk should say that it is installed however to double check, use an app that requires root permissions either to work (e.g. Network Signal Guru) or to do additional things, like a simple root checker app that you can download from wherever you download your apps. If everything is good, then you've rooted your OnePlus 9!
Notes: This process will probably work for other firmware packages for various phones where the boot.img can be extracted to be patched by Magisk and then flashed via fastboot (assuming the bootloader is unlocked) which includes the OnePlus 7T's stock firmware, but I can give no guarantees for this. Once again, try at your own risk.
I would suggest to boot the magisk patched image and then doing a direct install from the app instead of flashing it directly. This way you can use the "Restore images" feature in the Magisk app that can be useful when doing incremental update.
Thank You for thinking of Us Linux Users !
Attempted to update to LOS 20 via ADB, and now my touch screen will not work. All the remedies here require a Windows system for the MSM tool, which I do not have...
barguybrady said:
Thank You for thinking of Us Linux Users !
Attempted to update to LOS 20 via ADB, and now my touch screen will not work. All the remedies here require a Windows system for the MSM tool, which I do not have...
Click to expand...
Click to collapse
You have a computer you can install windows on another partition it's not like you don't have the ability to use msm
stez827 said:
You have a computer you can install windows on another partition it's not like you don't have the ability to use msm
Click to expand...
Click to collapse
no comment
barguybrady said:
Yup.
Just gonna spend another 4 or 5 hours prepping a drive to somehow install windows just to fix a phone.
Maybe - No....
Click to expand...
Click to collapse
It does not take that long as a Linux user who has had to install for that exact reason it took maybe an hour or 2
lawhec said:
As a OnePlus 9 user who likes to root their phone mainly to allow Network Signal Guru to work (as well as a few other root things like AdAway) I had been trying to extract the boot.img the same way as I had done with a OnePlus 7T using Payload Dumper for Windows. However it looks like Payload Dumper has issues with extracting xx.img files (including boot.img) if the payload.bin file is bigger than 4.3 GB in size. So I've been looking to see if another method was possible that would work for our OnePlus 9 ROMs that are above this file size. As I use Linux Mint as my usual desktop OS & only fall back onto Windows for stuff that'll only run on that OS, I went to have a look to see if something could be done under Linux. Turns out there is an old thread elsewhere on XDA that almost nearly provides what is needed for this, and I thought I would gives details here that should work for the time of this post (March 2023).
This not only extracts the boot.img to patch in Magisk, but also extracts other xx.img files as well.
I'm using Linux Mint 21.1, but I'd assume that this will also work for similar Ubuntu builds or anything that is based on Debian.
Obligatory disclaimer: The following instructions I'm giving below have worked well for me several times in the past, however I am in no way responsible for screwing up or damaging your phone if you try and follow what I've written below. In extreme cases, a bad flash may require using the OnePlus MSM tool to completely reflash your phone. Back up anything important first before doing any of the following!
1. You will need to ensure that you have downloaded packages to be able to do adb & fastboot from the command line. You can check by running the following commands - if it's already installed with the latest versions, the terminal interface will let you know...
Code:
sudo apt install adb
Code:
sudo apt install fastboot
2. You will need to go to your software manager in LM21.1 and install both Python 3 & the Python Protobuf compiler. Just search for "Python 3" & "Protobuf-compiler" in the software manager and the first option for each search is what you should need - if they are not installed, install them.
3. Create a read/writable directory that will hold your ROM that you've just downloaded & other files that I'll mention soon. I just use a folder calls "ROM" in my Downloads folder (e.g. /home/lawhec/Downloads/ROM ), but you can choose wherever you want that suits you.
4. If you have not done so already, make sure you have the FULL package of your OnePlus 9 ROM downloaded. As of right now (March 2023) it seems the best way is to download the package using the Oxygen Updater app which is available on Google Play - more info available at oxygenupdater.com - just download the ROM to your phone and transfer it on to your computer into the folder you've created for it.
5. Download and save the following two Python scripts/files ("Right click" & "Save Link As") into the folder you have just created for your ROM (all credit to Gregory Cyxx at github.com/cyxx )...
https://raw.githubusercontent.com/c...payload/master/extract_android_ota_payload.py
https://raw.githubusercontent.com/cyxx/extract_android_ota_payload/master/update_metadata_pb2.py
6. Make sure in your file browser (Nemo in my case as it is the default for LM21.1 Cinammon, yours may differ) the window is open in the ROM folder that contains the two Python scripts above that you've just downloaded as well as a ROM package (ZIP file) you've downloaded (in my case from Oxygen Updater mentioned in step 3). Create a new folder for the extracted images to be written to - in my case I just call the folder "output" which is located at "/home/lawhec/Downloads/ROM/output" but again you can call it what you wish.
7. After you've created your output folder, in your ROM directory in the file manager window right-click on your mouse in a white or free space and select "Open in Terminal" - a command terminal will pop up defaulting to your directory.
8. In the command terminal, type the following command and press enter/return...
Code:
sudo python3 extract_android_ota_payload.py <<Your ROM.zip>> <<Your Output Directory>>
...for example, in my case the command would be either...
Code:
sudo python3 extract_android_ota_payload.py LE2113_11_F-75.zip output
...or for handiness you can type "sudo python3 extract_android_ota_payload.py " (remember to leave a space) and simply drag the ROM zip file to the command terminal, press space and then drag the output foler to the terminal line, which will look like in my case...
Code:
sudo python3 extract_android_ota_payload.py '/home/lawhec/Downloads/ROM/LE2113_11_F-75.zip' '/home/lawhec/Downloads/ROM/output'
...this will now run the python script you downloaded earlier that will begin extracting the ROM you've specified and will output all relevant xx.img files into your output folder, including the one we want, "boot.img" - there is no need to extract paylod.bin beforehand, the script will automatically do this for you. Once all xx.img files have been extracted the script will stop, depending on your computer this will take anything from 1-5 minutes, maybe longer on some very old or low spec'd computers - but just let it run its course. Once it is done you can then close the terminal window.
9. Now with the boot.img we've extracted, transfer this file on to your phone (the Downloads folder is usually a good choice). Now open Magisk and patch the boot.img file - once this has been completed, it'll generate a patched boot.img file named something like "magisk_patched-25200_12345.img" - copy and paste this patched boot image back on to your computer (into the folder you've been using will be fine here).
10. If your OnePlus 9 phone is connected to your computer via USB cable, disconnect it now. Then shutdown your phone into a power-off state then reboot it into fastboot mode - this can be done by holding down the volume up & down buttons, then holding down the power button and keep holding down all three buttons until you feel a vibration from your phone. Your OnePlus 9 should then boot into fastboot mode.
11. Now reconnect your OnePlus 9 to your computer via the USB cable and then open up a new display terminal (preferably by right-clicking in the file window of the directory where you saved your Magisk patched boot.img file). Enter the following...
Code:
fastboot devices
...you should then get a line featuring a block of numbers that should match the serial number that is displayed on your phone's display, followed by "fastboot", for example...
Code:
85f53405 fastboot
...if you get anything else, double check your connections at try again - if more than one device is displayed, disconnect the and try again to make sure that only one device is listed. It might also be the case that you don't have the proper drivers installed on your computer for your phone though in my case LM21.1 automatically recognises my phone, so I'm not of any direct help here I'm afraid for this, sorry.
12. Now you will be flashing your patched boot.img to your phone - this is where things can be a little nervous though as long as you do everything right nothing should really go wrong. Type the following into the command terminal, assuming you did so by opening a command terminal from the folder your Magisk Patched boot.img file is located...
Code:
fastboot flash boot <<Magisk Patched boot.img>>
...for example in my case the command line would be...
Code:
fastboot flash boot magisk_patched-25200_12345.img
...otherwise you will need to provide the location of where your patched boot.img is, so in this case...
Code:
fastboot flash boot '/home/lawhec/Downloads/ROM/magisk_patched-25200_12345.img'
...either way, your phone will now be in the process of getting its boot image replaced with the one patched by Magisk. This should take no more than a few seconds and that should be it done! You can then close the terminal window again.
13. Once you've patched the boot image, disconnect the phone from the USB cable to the computer and make sure that the screen on your mobile says "START" in green at the top, if it doesn't, use the volume keys to change this. Then just simply press the power button and your phone will now reboot, this can take a little bit longer than before as your phone's firmware has changed so give it time - (however if it takes longer than 10 minutes or so you might have a problem here) - once your home screen becomes available, give it a few seconds once you've entered before selecting the Magisk app. Once you've done this, Magisk should say that it is installed however to double check, use an app that requires root permissions either to work (e.g. Network Signal Guru) or to do additional things, like a simple root checker app that you can download from wherever you download your apps. If everything is good, then you've rooted your OnePlus 9!
Notes: This process will probably work for other firmware packages for various phones where the boot.img can be extracted to be patched by Magisk and then flashed via fastboot (assuming the bootloader is unlocked) which includes the OnePlus 7T's stock firmware, but I can give no guarantees for this. Once again, try at your own risk.
Click to expand...
Click to collapse
If Using the t-Mobile Variant - LE2117 - we are Unable to Install any OTA Updates with OxygenUpdater, and are promptly warned of this limitation upon install. Nevertheless, I forged ahead and,
Following this Method, I downloaded a LE2115_11_F.17.zip, and proceeded to use your helpful .py scripts to extract the boot.img file, and Flash it - promptly sending me to a Qualcomm CrashDump mode.
Having a chance to MSM back to "stock" LE2117 - 11.2.2.2 LE54CB, I am wondering if I should just let the t-Mobile Update, through "Settings >> System >> System update" to Update the Stock ( bloated !? ) OS with all that are available,
Then attempt to Extract a boot.img and Magisk patch it ?
Any Advice?
TIA
Related
Hello. Has anyone rooted the Ulefone Power 6 yet? Im looking to have TWRP installed onto my new Power 6. My goal is to figure out a way to add user profiles, as it currently does not have them activated. I read online that you could edit the .prop to have any android activate the user profiles, but i cannot do this without my phone being rooted. Thanks in advance.
Start Here
Dvalin21 said:
Start Here
Click to expand...
Click to collapse
Sorry, This is for the original Ulefone Power, not the Power 6. Different phones. The instructions didn't lead me to anything useful. I have since update my phone to the latest firmware via the stock update app. I still haven't found a successful way to root the Power 6. There is this thread (https://www.getdroidtips.com/root-ulefone-power-6/), but the ADB commands to not work, and does not fastboot my phone to install the patched image. But either way, the instructions do not include a TWRP, so Im back to square one. HELP!
How to root Ulefone Power 6 (Build Power_6_SF1_V07) Updated 9/22/2019
OK. It was tough, but I finally found a way to root the Ulefone Power 6. I still haven't figured out a way to install TWRP, but that's because i have to build a custom recovery, and that's too advanced for me. So, anyone is welcomed to help out with building a custom recovery for TWRP. As for the root, This is what you will need:
Pre-Requirements:
Device battery charged up to 50%.
Developer Options enabled with OEM Unlocking and USB Debugging enabled
Remember to take a full backup of device data (Internal Storage, SMS), it will get formatted.
A Windows or Mac PC/Laptop is necessary to flash Magisk
A USB cable to connect your device with your PC
Download Links:
Download Minimal ADB Fastboot 1.4.3 (Portable). Extract it to your desktop.
It's best to give administrator privileges to the tools before you use them. To give them admin privileges:
Right click on adb.exe and select "Properties" at the bottom of the menu. Click on the "Compatability" Tab and check the "Run this program as an Administrator" box. Click on the "Apply" button and then the "OK" button to close the properties window.
Repeat the same process for the "cmd-here.exe" and the "fastboot.exe" files.
Ulefone USB Drivers. Extract it to your desktop and make sure you install the drivers.
MTK USB Drivers. Extract it to your desktop and make sure you install the drivers.
Latest Ulefone Power 6 Stock ROM. Or you could make a back up yourself. (latest rom as of 2/25/20 is GQ3081SF1_M860B1_Ulefone_20190921_V07(Non-EU) ).Extract it to your desktop.
MTK SP Multi Port Download Tool. This will be used to flash the most recent Ulefone rom on your device. Extract it to your desktop.
Download Magisk Manager
After downloading the Stock ROM (will be a .ZIP file), extract it to your PC.
Connect your device via USB cable
Find the "boot.img" file inside the Stock Rom folder you just extracted and copy only the "boot.img" file to your devices storage.
Copy Magisk Manager.apk to your devices storage
Using your device, install Magisk Manager
Open the Magisk Manager on your device.
Select "Install" from the first option next to "Magisk is not installed" and again select install.
Now, tap on "Select and Patch a File".
Go to your devices storage where you have copied the "boot.img" file earlier and select it.
Magisk will start patching the boot image.
Once the boot image is patched, Magisk will save the image on your "Download" folder located on your devices storage.
Locate the patched image (magisk_patched.img) and copy the "magisk_patched.img" to your PC. Make sure the patched image (magisk_patched.img) is inside the same folder as the extracted ADB and Fastboot tool folder on your desktop.
Open/run MTK SP Multi Port Download Tool
Click on File from the Menu located at the top right and select "Open Download Agent File"
Locate and select "MTK_ALLInOne_DA.bin", located in the same folder as the MTK SP Multi Port Download Tool folder.
Press the "Open buton" to select the file and close the window.
Now, click on the "Scatter File" button located at the top left.
Locate and select the XXXXXXXX_scatter.txt file located inside the extracted Ulefone Power 6 Stock Rom folder.
Press the "Open buton" to select the file and close the window.
Now, tick the "BootRom+PreLoader COM Sel All" check box located under the "scatter file" button.
Now, Click on the "Scan" button located at the bottom right.
Select Yes from the pop up window
Now, power off you device and disconnect your device from your PC by removing the USB cable from your device.
Now, reconnect the USB cable to your device while it is powered off.
MTK SP Multi Port Download Tool should detect your device and a green bar should appear confirming the connection with the words "Scan Success!" to the left of the green bar.
Press the "Stop all" button located at the bottom right
Disconnect and reconnect your device from your PC
Uncheck the "BootRom+PreLoader COM Sel All" box and check only the line with the green bar.
Click on the tiny "Start" button located to the right of the green bar.
You can confirm the flash was successful when the words "PASS" is visible to the right of the tiny "Start" & "Stop" buttons
Once the flashing is complete, you can close MTK SP Multi Port Download Tool and power on your device.
Configure your device to get to the home screen (skipping as many options as you can. You will have to format one more time) and enable Developer Options, OEM Unlocking and USB Debugging again.
Make sure your device is connected to your PC.
Now, you need to open up a command window (cmd window) inside the Minimal ADB Fastboot 1.4.3 (Portable) folder. To do this, open the "cmd-here.exe" file.
Next, enter the following command in the cmd window:
adb devices
(this command will confirm your device is connected to your PC via ADB )
Your device will show a pop up window asking for permission to connect via ADB. Click on the "Always Trust This Device" and Accept the connection
If successful, you should see the word "Device" to the right of your devices name on the list that the cmd window created.
Next, enter the following command:
adb reboot-bootloader
(This command will boot your device into fastboot/bootloader mode. It will turn off and the device will have a black lit screen)
Check that your device is connected to your pc by entering the following command:
fastboot devices
(this command will confirm your device is connected to your PC via fastboot/bootloader mode ) If successful, you should see the word "Device" to the right of your devices name on the list that the cmd window created.
Next, enter the following command:
fastboot flashing unlock
(if nothing happens, press the Volume up+ on your phone to start the unlocking of the bootloader)
(this will unlock your bootloader)
Next, enter the following command:
fastboot getvar unlocked
(this will confirm you have unlocked your bootloader. It will say "unlocked: yes")
Next, enter the following command:
fastboot flash boot magisk_patched.img
(This will replace your stock image with the patched image you created using Magisk Manager)
Next, enter the following command to reboot your phone:
fastboot reboot
Install magisk manager using your file manager. Make sure to follow directions when it asks you to give special permissions to install.
Open Magisk Manager and click on "OK" when it starts up and asks you for "additional setup".
Congratulations! Your device is rooted.
Extra notes:
If you come across a red watermark with the Chinese words and "Tee Keys" and/or "Google Keys" on the top right of your devices screen, this is how you fix it.
make sure your device is turned on and connected to your PC.
Open "cmd-here.exe" located in the Minimal ADB Fastboot 1.4.3 (Portable) folder.
Next, enter the following command:
adb shell pm uninstall -k --user 0 com.mediatek.factorymode
(This command will not do anything at the moment, but will remove the watermark after you reboot your device)
Next, enter the following command to reboot your device:
adb reboot
The watermark should be removed when your device restarts again.
ENJOY!
19Henry83 said:
OK. It was tough, but I finally found a way to root the Ulefone Power 6. I still haven't figured out a way to install TWRP, but that's because i have to build a custom recovery, and that's too advanced for me. So, anyone is welcomed to help out with building a custom recovery for TWRP. As for the root, This is what you will need:
. . . . .
. . . . . . . . . . .
. . . . . . . . . . . . . . .
ENJOY!
Click to expand...
Click to collapse
Thanks a heap for all these instructions, would not have been able to do this without them.
Just a few extra pieces of information for anyone else caryring out the above steps:
- If you your stock ROM doesn't have a file manager in order to open/execute the MagiskManager APK file then using Chrome to download the APK file will allow you to execute it.
- in the SP Multi Port Tool, after checking the line with the green bar and clicking start you'll notice the time in seconds counting next to the start button. At this point you may need to unplug your USB cable and replug it in order for the SP Multi Port Tool to detect the devices and actually start properly
- If the SP Multi Port Tool requires a checksum.ini file you can follow the instructions on the hovatek site (Google 'checksum.ini generatemediatek hovatek' I'm a new user so can't post links):
Note there is a download link for the CheckSum_Gen.zip file which will require you to register for an account on the hovatek website. You can create a junk/throw away account with a fake email as it doesn't require email confirmation. Also all of the files inside the CheckSum_Gen.zip folder need to be placed inside of the stock ROM folder where the scatter file is located.
- The watermark can only be removed after the MagiskManager carries out its additional setup and after root access is complete.
Still hoping to find a compatible TWRP recovery. If anyone builds one please let us know!
Hi, 19Henry83
I did try your method and it works great. I rooted my Power 6. The thing is I did this in hope to fix a freezing touchscreen issue. Touch screen frezzes and I need to lock/unlock my phone constantly to fix it. Now I'm convinced this is not a software issue and I will return the phone to the seller. So I wanted to get back to the original firmware. When I do that however there is still that red watermark and my IMEI is deleted. Is there any way to get back to the factory software and not have the red watermark, as I assume it will void my warranty.
I Need help please ,, I need the TWRP Recovery, Tool / Utility for the Ulefone Power 6, I have looked for it in many web pages and I cannot find it, all the ones I find have the same name "3.3.1 Power 6" and not It works for me when I install them, I get the same recovery that I had when I try to enter
jiroscop said:
Hi, 19Henry83
I did try your method and it works great. I rooted my Power 6. The thing is I did this in hope to fix a freezing touchscreen issue. Touch screen frezzes and I need to lock/unlock my phone constantly to fix it. Now I'm convinced this is not a software issue and I will return the phone to the seller. So I wanted to get back to the original firmware. When I do that however there is still that red watermark and my IMEI is deleted. Is there any way to get back to the factory software and not have the red watermark, as I assume it will void my warranty.
Click to expand...
Click to collapse
Hello Jiroscop. I had the same problem and only noticed after i read your post. Now, a couple months later, i managed to use an IMEI changer to insert my IMEI found on my original box where my phone came in. It should have two IMEIs. I don't know if i can explain on this forum. Try researching it on your own and get back to me if you cannot find a way to fix your phone.
NOTE: you will need your original IMEI's, changing the IMEI's with anything other than the original ones will brick your phone.
The factory images are up my friends. Go pick what you need :good:
https://support.google.com/pixelphone/thread/24852169?hl=en
Added bonus: Here is a link to the January stock boot and magisk patched boot.img's
This is for the global build #QQ1B.200105.004 :good:
https://drive.google.com/file/d/1Dgh7w0r4ZzPZ7qOePhfADjPuLp-K84yO/view?usp=drivesdk
PS: I used stable magisk 20.2 to patch the boot.img
Dey Up Bruv...
Im downloading mine already <3
OTA is only 12MB.
Only 1st january, not 5th?
can confirm Jan update works with magisk root and ed_xposed. Thanks for updating us with the update availability!
Badger50 said:
The factory images are up my friends. Go pick what you need :good:
https://support.google.com/pixelphone/thread/24852169?hl=en
Added bonus: Here is a link to the January stock boot and magisk patched boot.img's
This is for the global build #QQ1B.200105.004 :good:
https://drive.google.com/file/d/1Dgh7w0r4ZzPZ7qOePhfADjPuLp-K84yO/view?usp=drivesdk
PS: I used stable magisk 20.2 to patch the boot.img
Click to expand...
Click to collapse
Hi, and thx.
But can u share a small how-to, for updating, step by step? Just wanna be sure that I on the right way.
lapapunk said:
Hi, and thx.
But can u share a small how-to, for updating, step by step? Just wanna be sure that I on the right way.
Click to expand...
Click to collapse
In a nutshell: This is how I do it. Others MMV
1. Make sure platform-tools are up to date. The latest is 29.0.6. And use a USB A to USB C cable.
2. Download factory image, extract it, extract the image.zip, move boot.img to your phones internal storage.
3. Disable all magisk modules and substratum themes, remove face ID and reboot.
4. Patch the stock boot.img, and move the patched.img to your pc platform-tools folder, then turn phone off.
5. Move all your necessary factory image files to your platform-tools folder: bootloader, radio, the still zipped image.zip and the flash-all.bat file for Windows machines. Using notepad or whatever, edit the flash-all.bat file and remove the -w from the script, leaving a single space between the remaining words, save your edit.
6. Put phone in bootloader mode, and plug it into your pc. Open a command prompt {See 6A} on your platform-tools folder, type in: fastboot devices. If your device is recognized with it's ID, your good to go. Then, what I do is go into my platform-tools folder and double click the flash-all.bat file to start the process. Let it finish, and let your device boot up.
6A. For Win 10 users. Open a command prompt by typing "cmd" in the search box, then open the prompt. You'll see C:\Users\<your name> with the flashing cursor. Then type "cd" then hit the space bar. Then drag and drop your completed platform-tools folder in the command line, and let it populate. Then hit enter, and now you can issue your fastboot commands :good:
7. Once it boots ok with the update, turn phone off, and go into bootloader mode. Connect to pc, and fastboot the patched boot.img to both slots with..
fastboot flash boot magisk_patched.img --slot=all
And let it boot up with root.
8. Then start enabling your magisk modules a couple at a time. Be warned, sometimes, not all magisk modules play nicely with monthly updates, so take it slow. Luckily, January is cool with the @Tulsadiver mods, and the Active Edge mods from what I've seen.
9. And there ya go. Ok....so it was a little bigger than a nutshell!
When doing the above flashing use an A to C, not the supplied cable. If you're already in a flash failure with the supplied cable grab an A to C and flash again without doing a factory reset or taking any other actions to try and get it up; this will usually get it booting as if the first flash was successful.
Edit... I know you would have put it in there if you'd remembered Badg, it's hard to remember every little speed bump when whipping up a set of instructions like that.
@Badger50
Ok, thx.
But what about this guide? On my pixel 2xl this method worked great. Will it work on 4xl?
Badger50 said:
In a nutshell: This is how I do it. Others MMV
1. Make sure platform-tools are up to date. The latest is 29.0.5. And use a USB A to USB C cable.
2. Download factory image, extract it, extract the image.zip, move boot.img to your phones internal storage.
3. Disable all magisk modules and substratum themes, remove face ID and reboot.
4. Patch the stock boot.img, and move the patched.img to your pc platform-tools folder, then turn phone off.
5. Move all your necessary factory image files to your platform-tools folder: bootloader, radio, the still zipped image.zip and the flash-all.bat file for Windows machines. Using notepad or whatever, edit the flash-all.bat file and remove the -w from the script, leaving a single space between the remaining words, save your edit.
6. Put phone in bootloader mode, and plug it into your pc. Open a command prompt on your platform-tools folder, type in: fastboot devices. If your device is recognized with it's ID, your good to go. Then, what I do is go into my platform-tools folder and double click the flash-all.bat file to start the process. Let it finish, and let your device boot up.
7. Once it boots ok with the update, turn phone off, and go into bootloader mode. Connect to pc, and fastboot the patched boot.img to both slots with..
fastboot flash boot magisk_patched.img --slot=all
And let it boot up with root.
8. Then start enabling your magisk modules a couple at a time. Be warned, sometimes, not all magisk modules play nicely with monthly updates, so take it slow. Luckily, January is cool with the @Tulsadiver mods, and the Active Edge mods from what I've seen.
9. And there ya go. Ok....so it was a little bigger than a nutshell!
Click to expand...
Click to collapse
You're an absolute legend mate, thanks!!
lapapunk said:
@Badger50
Ok, thx.
But what about this guide? On my pixel 2xl this method worked great. Will it work on 4xl?
Click to expand...
Click to collapse
Nothing wrong with that either. It was written by Mr. Magisk himself. However, that is mostly for OTA's that I never use. I prefer updating by factory images :good:
krabman said:
When doing the above flashing use an A to C, not the supplied cable. If you're already in a flash failure with the supplied cable grab an A to C and flash again without doing a factory reset or taking any other actions to try and get it up; this will usually get it booting as if the first flash was successful.
Edit... I know you would have put it in there if you'd remembered Badg, it's hard to remember every little speed bump when whipping up a set of instructions like that.
Click to expand...
Click to collapse
Many thanks for reminding me of probably the biggest bug-a-boo problem plaguing the pixel line when it comes to updating or data transfer. Which is why I have several different cables! The P2XL was a great teacher for sure :good:
Do we flash global for TMobile?
Some_Ghost said:
Do we flash global for TMobile?
Click to expand...
Click to collapse
According to Google....yes :good:
After the January update, I no longer have call screening (automatic or otherwise). Not sure if related to being a GSuite user or not. Ugh...
Badger50 said:
In a nutshell: This is how I do it. Others MMV
1. Make sure platform-tools are up to date. The latest is 29.0.5. And use a USB A to USB C cable.
2. Download factory image, extract it, extract the image.zip, move boot.img to your phones internal storage.
3. Disable all magisk modules and substratum themes, remove face ID and reboot.
4. Patch the stock boot.img, and move the patched.img to your pc platform-tools folder, then turn phone off.
5. Move all your necessary factory image files to your platform-tools folder: bootloader, radio, the still zipped image.zip and the flash-all.bat file for Windows machines. Using notepad or whatever, edit the flash-all.bat file and remove the -w from the script, leaving a single space between the remaining words, save your edit.
6. Put phone in bootloader mode, and plug it into your pc. Open a command prompt on your platform-tools folder, type in: fastboot devices. If your device is recognized with it's ID, your good to go. Then, what I do is go into my platform-tools folder and double click the flash-all.bat file to start the process. Let it finish, and let your device boot up.
7. Once it boots ok with the update, turn phone off, and go into bootloader mode. Connect to pc, and fastboot the patched boot.img to both slots with..
fastboot flash boot magisk_patched.img --slot=all
And let it boot up with root.
8. Then start enabling your magisk modules a couple at a time. Be warned, sometimes, not all magisk modules play nicely with monthly updates, so take it slow. Luckily, January is cool with the @Tulsadiver mods, and the Active Edge mods from what I've seen.
9. And there ya go. Ok....so it was a little bigger than a nutshell!
Click to expand...
Click to collapse
you are a great help and i wish i could take you out for a beer or 5
Badger50 said:
In a nutshell: This is how I do it. Others MMV
1. Make sure platform-tools are up to date. The latest is 29.0.5. And use a USB A to USB C cable.
2. Download factory image, extract it, extract the image.zip, move boot.img to your phones internal storage.
3. Disable all magisk modules and substratum themes, remove face ID and reboot.
4. Patch the stock boot.img, and move the patched.img to your pc platform-tools folder, then turn phone off.
5. Move all your necessary factory image files to your platform-tools folder: bootloader, radio, the still zipped image.zip and the flash-all.bat file for Windows machines. Using notepad or whatever, edit the flash-all.bat file and remove the -w from the script, leaving a single space between the remaining words, save your edit.
6. Put phone in bootloader mode, and plug it into your pc. Open a command prompt on your platform-tools folder, type in: fastboot devices. If your device is recognized with it's ID, your good to go. Then, what I do is go into my platform-tools folder and double click the flash-all.bat file to start the process. Let it finish, and let your device boot up.
7. Once it boots ok with the update, turn phone off, and go into bootloader mode. Connect to pc, and fastboot the patched boot.img to both slots with..
fastboot flash boot magisk_patched.img --slot=all
And let it boot up with root.
8. Then start enabling your magisk modules a couple at a time. Be warned, sometimes, not all magisk modules play nicely with monthly updates, so take it slow. Luckily, January is cool with the @Tulsadiver mods, and the Active Edge mods from what I've seen.
9. And there ya go. Ok....so it was a little bigger than a nutshell!
Click to expand...
Click to collapse
What should I do when the cmd window comes to "fastboot: error: failed to extract 'android-info.txt': iteration ended" as shown in the attachment.
And the process stops.
howardfok said:
What should I do when the cmd window comes to "fastboot: error: failed to extract 'android-info.txt': iteration ended" as shown in the attachment.
And the process stops.
Click to expand...
Click to collapse
Hard to say exactly since i've never seen that error. Did you follow my guide to the letter?
Is this the first time this has happened?
Are you using power shell commands?
Are your platform-tools up to date?
Have you tied different USB A to USB C cables and ports?
More info would be helpful :good:
Badger50 said:
Hard to say exactly since i've never seen that error. Did you follow my guide to the letter?
Is this the first time this has happened?
Are you using power shell commands?
Are your platform-tools up to date?
Have you tied different USB A to USB C cables and ports?
More info would be helpful :good:
Click to expand...
Click to collapse
Yes, I followed your guide and the cmd window worded well at the previous procedure and showed several [ok] but stuck at this point.
I doubled clicked 'flash-all.bat' file rather than used power shell.
The platform-tools is up to date since it was downloaded today.
I have not tried another cable. The cable may work well because I used this to unlock bootloader and root the device last month.
BTW, should I re-zip the replaced boot.img (Patch from Magisk) and other .img files (from the full image) to get a new zip file before flashing?
howardfok said:
Yes, I followed your guide and the cmd window worded well at the previous procedure and showed several [ok] but stuck at this point.
I doubled clicked 'flash-all.bat' file rather than used power shell.
The platform-tools is up to date since it was downloaded today.
I have not tried another cable. The cable may work well because I used this to unlock bootloader and root the device last month.
BTW, should I re-zip the replaced boot.img (Patch from Magisk) and other .img files (from the full image) to get a new zip file before flashing?
Click to expand...
Click to collapse
I would try a different cable and port first.
Don't worry about the patched boot.img until you have a successful flash of the factory image, and your phone boots up first. The secondary image.zip within the factory image definitely needs to remain zipped and in your platform-tools tools folder. The installation script needs to extract it so it can be flashed. This may be why your getting the error if this is the case.
First I want to say that I'm not a developer nor in any way an expert and I'm sure that will be apparent as you read my post. I was able to root my Voyager III tablet by reading and following the work of people like diplomatic and topjohnwu, and using the products of their work. I looked everywhere for a specific root method for this little tablet but could never find one. The fact is there has always been a method since topjohnwu's Magisk_Manager's ability to patch stock boot images and re-pack them for use in your specific MTK-based phone or tablet. It just hasn't been obvious that the RCT6973W43MD Android 7.0 was a candidate for that root process...at least not to me. In any case, this is what I did to achieve root. But first...
**Do these steps at your own risk. They worked for me but I won't be responsible for any damage you do to your phone or tablet**
Unlock Bootloader
1. In your tablet, enable Developer Options by going to Settings> About Tablet> Build number. Press "Build number" 7 times to reveal "Developer options." Press Back button to see and enter "Developer options." Enable "OEM Unlock." While you're there, enable "USB Debugging," disable "Automatic system updates" and "Verify apps over USB." Also make sure "Install Apps from Unknown Sources" is enabled.
2. Using adb, after your device is recognized, type:
adb reboot fastboot
fastboot flash oem unlock
fastboot reboot
Your bootloader should now be unlocked. On your boot screen it will say, "Orange State." (never try to re-lock the bootloader because that will put your device into "red state" which is very bad. You've been warned!)
Extract Your Tablet's Boot.img file using MTK-su
1. You need the boot.img file of your specific ROM to allow Magisk_Manager to patch it...in order that Magisk may be installed as superuser. What better place to get that file than your own device? Use diplomatic's MTK-su exploit to gain temporary superuser access to your tablet's root file system. Your boot.img file can be found in /dev.
2. Still superuser under MTK-su, copy the boot.img file to your sd card in at least two locations. The reason for this is to make sure you can easily find it later when you've left MTK-su's root shell. Something like this should work...
cd /dev
cp bootimg /storage/emulated/0
cp bootimg /storage/emulated/0/Download
**Note** In /dev your boot.img file is named "bootimg". When you copy (paste) it to your sd card it will appear as "boot.img".
Patch Your Tablet's Boot.img file with Magisk_Manager
1. Download Magisk_Manager v7.5.1 apk and install on your tablet. Patch your boot.img file. Press Install . Install> "Select and Patch a file". Navigate to your boot.img file and select it. Wait a few seconds for the patching to start and note the location of the newly patched boot image named magisk_patched.img. Flashing this personalized boot image will allow you to install Magisk v20.4.
2. Now using adb and MTK-su again, start a root shell and find the magisk_patched.img file and copy it also in at least two places to make it easy to find and later transfer to your desktop. My experience was that I copied it to my sd card but couldn't find it when i left the root shell and tried to get it onto my desktop. The point is that you want the file in a directory that your desktop file manager can access. I'm a noob so I made a few copies of it.
At this point it might also be a good idea to review topjohnwu's Magisk boot-patching thread here to glean any information that may apply to the Voyager 3, although that tablet is not mentioned by name
3. On your computer using adb fastboot:
adb reboot fastboot
fastboot flash boot /path/to/magisk_patched.img
fastboot reboot
4. Download Magisk.20.4.zip and install it from your tablet's recovery or via adb. You should now be rooted and the Manager app should show both Magisk_Manager and Magisk superuser installed. I know there's probably easier ways to do this, and lots of shortcuts, but this is what worked for me.
akonobi said:
First I want to say that I'm not a developer nor in any way an expert and I'm sure that will be apparent as you read my post. I was able to root my Voyager III tablet by reading and following the work of people like diplomatic and topjohnwu, and using the products of their work. I looked everywhere for a specific root method for this little tablet but could never find one. The fact is there has always been a method since topjohnwu's Magisk_Manager's ability to patch stock boot images and re-pack them for use in your specific MTK-based phone or tablet. It just hasn't been obvious that the RCT6973W43MD Android 7.0 was a candidate for that root process...at least not to me. In any case, this is what I did to achieve root. But first...
**Do these steps at your own risk. They worked for me but I won't be responsible for any damage you do to your phone or tablet**
Unlock Bootloader
1. In your tablet, enable Developer Options by going to Settings> About Tablet> Build number. Press "Build number" 7 times to reveal "Developer options." Press Back button to see and enter "Developer options." Enable "OEM Unlock." While you're there, enable "USB Debugging," disable "Automatic system updates" and "Verify apps over USB."
2. Using adb, after your device is recognized, type:
adb reboot fastboot
fastboot flash oem unlock
fastboot reboot
Your bootloader should now be unlocked. On your boot screen it will say, "Orange State." (never try to re-lock the bootloader because that will put your device into "red state" which is very bad. You've been warned!)
Extract Your Tablet's Boot.img file using MTK-su
1. You need the boot.img file of your specific ROM to allow Magisk_Manager to patch it...in order that Magisk may be installed as superuser. What better place to get that file than your own device? Use diplomatic's MTK-su exploit to gain temporary superuser access to your tablet's root file system. Your boot.img file can be found in /dev.
2. Still superuser under MTK-su, copy the boot.img file to your sdcard in at least two locations. The reason for this is to make sure you can easily find it later when you've left MTK-su's root shell. Something like this should work...
cd /dev
cp bootimg /storage/emulated/0
cp bootimg /storage/emulated/0/Download
**Note** In /dev your boot.img file is named "bootimg". When you copy (paste) it to your sd card it will appear as "boot.img".
Patch Your Tablet's Boot.img file with Magisk_Manager
1. Download Magisk_Manager v7.5.1 apk and install on your tablet. Patch your boot.img file. Press Install . Install> "Select and Patch a file". Navigate to your boot.img file and select it. Wait a few seconds for the patching to start and note the location of the newly patched boot image named magisk_patched.img. Flashing this personalized boot image will allow you to install Magisk v20.4.
2. Now using adb and MTK-su again, start a root shell and find the magisk_patched.img file and copy it also in at least two places to make it easy to find and later transfer to your desktop. My experience was that I copied it to my sd card but couldn't find it when i left the root shell and tried to get it onto my desktop. The point is that you want the file in a directory that your desktop file manager can access. I'm a noob so I made a few copies of it.
At this point it might also be a good idea to review topjohnwu's Magisk boot-patching thread here to glean any information that may apply to the Voyager 3, although that tablet is not mentioned by name.
3. On your computer using adb fastboot:
adb reboot fastboot
fastboot flash boot /path/to/magisk_patched.img
fastboot reboot
4. Download Magisk.20.4.zip and install it from your tablet's recovery or via adb. You should now be rooted and the Manager app should show both Magisk_Manager and Magisk superuser installed. I know there's probably easier ways to do this, and lots of shortcuts, but this is what worked for me.
Click to expand...
Click to collapse
I know the above is not as clear as I would like to make it, and I invite others to refine the method so that people can easily follow it. But the fact is that it works. I've duplicated it after mistakenly factory-resetting my device. I tested it using Fx File Explorer which now has been granted superuser powers. I'll post photos soon to prove root status. Again please feel free to add to, detract from, or in any way help to make my explanation more accurate and concise. Of course all credit goes to the guys who made the tools I used, @topjohnwu and @diplomatic.
The overall thrust of what I've tried to describe is 1) patch your own boot.img file with Magisk_Manager and flash it to your bootloader and 2) load Magisk superuser app in the now friendlier boot environment to obtain root. That's it.
I've been doing taxes lately...years of taxes, but I finally read up on posting images so here. Not exactly like I wanted them to post, but it does the job.
Also it is very important that you do not upgrade MagiskSU within MagiskManager. Flash any updates through your recovery. If by chance you try updating through MagiskManager your root will be gone and if in bootloop you will have to wipe device and start again with the step of extracting your boot.img.
Also, remember to check which processor your tablet has before you try modifying it. RCA came out with many, many confusingly similar part numbers. Only some of them have MTK processors with others being (at the very least) Intel or Rockchip.
Thread Closed Per OP Request
Don't work,
I give up
Thanks in advanced. All comments can help!
I have a tablet I can depure via USB and where I can root the tablet. But if I connect to the internet, the "registration and password" of university program enters and is saved (even after formatting it is stuck on this screen) blocking the tablet, I believe that after the internet loads, it installs this locking program ... What would be the name of this type of application? I'd like to know, how remove this app, to If connect in internet, we can block (and try install TWRP via internet with TWRP Management)...
C.Modica said:
Hello everyone !
I've been trying to resolve this issue for weeks. I have a tablet that I can't unlock (it's super hard, it's like Dark Souls of tablets). Well let's start.
He has a program that blocks asking for password and user (this a old from a university), where you request access via wireless or 2G/3G. without it you can't access it, so I believe I have to change his firmware instaled in, but I'm having a hard time to make it.
• Let's go to basic product information:
The chip is a RK3066 (same from TV BOX based on rockchip).
The model is YPY L1050 from POSITIVO (it's from Brazil).
- Software and Items
I have the drivers installed (correctly);
I have adb installed;
I have SD_Card;
I have acess from PC;
The tablet is unroot;
• Back to the items:
So, the good news is that I have the same tablet model, unlocked (with another type of ROM that I am unaware of). That works normally, without problems. Well, I saw a procedure that basically it is possible to extract this image from the good tablet, to the locked tablet. I did that, I ended up extracting a series of .img files from the unlocked tablet: boot, cache, kernel, system, etc... ok.
• Trying a extract from unlock same tablet:
I try transfer the copied files from "good unlock tablet" (extrated with AndroidTool), and put in (with the same tool) in the lock tablet... There is a problem, even before starting the operation, I have the error "Test Device Fail ", in the last is not possible to transfer files via USB (I can only do commands like" ResetDevice ", or export the images from the blocked tablet via AndroidTool... and yes I have the drivers instaled, commands like adb sideloader in the fastboot works).
• Trying a firmware found in internet:
Well, I tryed to download the firmware found on the internet corresponding to the device model, but unfortunately I have the same error as above. I download the .img firware original and using the RKBatchTool and have the same error (the operation don't start, give "Test Device Fail" in "Upgrade" and "Restore").
I believe that both operations do not accept transferring via USB.
PS: The tablet unlocked the command of "TestDevice" works fine.
• What I was thinking of doing:
1 - I think I need to take the all .img(s) files extracted from the unlocked device, put it in a single image (.img), put it in a SD_Card and in the "fastboot" take the option "update rkimage from external storage". But I don't know how to do this. (I try search for it);
2 - Somehow being able to do "apply update from external storage", maybe doing the same procedure above with an "update.img", but I also don't know how to do that (put all img. files together in the form of a one update.img).
3 - Have anothers options, like "apply update from ADB", the PC response this conection with tablet, (I can see the device with ''adb device'' cmds in sideload mode in PC). The problem is that I don't know how I'm going to send the .img file, if I send it inside a .zip (I even tried that, send all the .img files inside a .zip to see if it works. The tablet arrives to read the files but in the end the operation aborts). So my knowledge is lacking in this part.
4 - Another would be such a "ROM Dump." I'd like to do a "ROM dump" with an SD card, I even researched it on the internet but I didn't find this procedure to rockchip (only for Amlogic).
With SD Card:
There was a youtube that managed to unlock a tablet like that, but it was a previous model that I'd like to unlock (and different version of firmware, android etc). His method was to put a bootable sd_card, but he doesn't explain how he does it (he only gives the file done) and looking at the files internally, I just think they were converted to linux formats (system.tar.gz, userdata.tar.gz, some .sh .so files, and a bootenv.img, uImage etc) and with completely different names from .img... It is a pity that it is not for my Tablet model .
Well, that's it in the end, I need to change the firmware and I don't know how to do it.
PS: I tried other operations/methods as well, but I will not comment so that this post doesn't get big.
Thanks in advanced. All comments can help!
Click to expand...
Click to collapse
Instead of trying to package the .img files into one file, you should try flashing each .img individually via fastboot using commands with the following structure:
fastboot flash <name of partition> <name of partition.img>
The following commands are examples.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
You will need to use a separate command for each individual .img.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Instead of trying to package the .img files into one file, you should try flashing each .img individually via fastboot using commands with the following structure:
fastboot flash <name of partition> <name of partition.img>
The following commands are examples.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
You will need to use a separate command for each individual .img.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Hi, thanks for the reply. Well I can make it via adb sideload? I can't use the command "adb reboot fastboot". Because this command "adb reboot fastboot" only turns off the tablet don't restarting into fastboot/download mode (just turns off). But If I manually enter on the bootloader, I can access the adb sideload option, where the adb install on computer can detects the device via the "adb devices command" with sideload.
C.Modica said:
Hi, thanks for the reply. Well I can make it via adb sideload? I can't use the command "adb reboot fastboot". Because this command "adb reboot fastboot" only turns off the tablet don't restarting into fastboot/download mode (just turns off). But If I manually enter on the bootloader, I can access the adb sideload option, where the adb install on computer can detects the device via the "adb devices command" with sideload.
Click to expand...
Click to collapse
It isn't going to work via adb unless the device is rooted and then it won't be via adb sideload, it would be done by using dd commands to dd the .img files directly to their partitions.
Sent from my SM-S767VL using Tapatalk
I just found a solution. It requires some tinkering, though.
I had to use a machine running windows 7, because that's the only OS that the drivers worked.
Download the firmware for the Ypy L1050F here: https://www.stockrom.net/2018/07/l1050.html
It comes with the drivers, the ROM, and a tool called RKBatchtool 1.8
You'll have to decompress everything, open RKBatchtool and choose the firmware that is in the ROM folder (Not the DEMO one).
Now comes the tricky part: You gotta undo the 3 screws aroud the tablet, then pry it open with your fingers(remember to remove microSD and SIM first, to avoid breaking stuff!). I recommend startind by the side with the usb, hdmi and power ports to get some leverage. The back cover should pop right off. Then you have to locate the NAND chip in it. Should be a Micron one with 48 pins. The small circle at one of the corners of the chip represents pin 1. Plug your usb cable to the tablet. With the tablet TURNED OFF, use a SIM removal tool or very fine tip metallic screwdriver to short pins 17 and 18 on the NAND chip and plug the power jack into the tablet. RKBatchtool should show that a device was connected. You can release the screwdriver now and just click the "Upgrade" button in RKBatchtool. Now this is very important: DO NOT UNPLUG your tablet until everything is done. It'll tell you when it's done uploading the firmware and checking it. Enjoy your new usable tablet!
I scoured the internet and found this procedure being used for TV Boxes with the same RK3066 SoC. AFAIK, nobody else managed to do it so far, so spread the word.
You are awesome. Broke the internet! I will follow your procedures to try to unlock it. Many thanks again xmas for you.
[edit] don't work
PrefaceLuckily, it looks like Infinix is following the general trend of Android root solutions being more straightforward than in the recent past. Besides the usual spiel about your warranty being voided, and the annoying chirp each time you boot your phone, this hopefully won't present any problems for you if you do end up rooting your phone.
Notices
Still, I'm not responsible for anything bad that will happen to your phone if you do this, and there's no support guaranteed either from me or your OEM/support centre.
There's quite a few steps to this, and naturally you're gonna need a few more things to setup before you even start.
Your phone's data will be reset, please backup everything you'd like to keep before rooting your phone (now and in general).
You do need to know some things already, mainly what ADB and Fastboot are, and how to keep your working environment clean and straightforward.
Please do review all the tools you're working with, be sure that you personally trust all the software you're running.
And last but not least, you won't be able to update your phone through OTA updates anymore unless you go back to stock firmware.
The process
Make an environment for easy access:
Setup ADB and Fastboot (either as a local executable or a global environment variable to that executable).
Setup an easy to access directory with the Google Fastboot driver in it.
Grab your firmware's boot.img file, or grab the one attached to this post, or from here (and skip to the preliminary work section):
1. Download your phone's current ROM.
2. Extract it, as it should be a simple .zip file.
3. Look for the file of the same name (boot.img).
4. Copy it to your phone's storage, anywhere works.
Install the Magisk APK (from their Github).
Once it's installed, Magisk's app frontend allows you to patch your stock boot.img with itself, the gist of it is:
Click on Install within the app, in the "Magisk" section of the main menu.
Click "Select and patch a file", a file selection menu will show up, select the stock boot.img, then start the installation.
Magisk should spit out a patched boot.img named in the format of magisk_patched_[random_strings].img, in your phone's /sdcard/Download/ directory.
Copy that back into our working directory, and rename it to magisk_patched.img for easier usage.
Now, let's do some preliminary work, in any order, really:
Have Powershell or CMD open in the directory of all your tools, alongside the patched image.
Click to expand...
Click to collapse
From here on out, if you have to use adb as a command, and it's not a global environment variable, use ./adb while in the working directory instead, the same goes for fastboot.
Click to expand...
Click to collapse
Make sure that the adb daemon (adbd) is properly detecting your phone:
Enable developer options.
Enable ADB debugging.
Run adb devices to start the server daemon for ADB, and see if ADB detects your phone.
Authorize your PC for ADB debugging if it prompts you to.
Click to expand...
Click to collapse
Infinix's implementation of Fastboot will exit back out of itself and into normal boot after 60 seconds of inactivity, which makes this a tad annoying, although you can simply send it any input to reset that timer.
Click to expand...
Click to collapse
Let's start:
Restart the phone into Fastboot, adb reboot bootloader loader, it'll take a second, the phone is slow.
Unlock flashing 3rd party software, fastboot flashing unlock, the phone will prompt you on the screen to confirm doing this. Yes, this will void your warranty.
Flash magisk_patched.img to both A and B virtual partitions, fastboot flash boot_a magisk_patched.img and then fastboot flash boot_b magisk_patched.img.
That should be it! fastboot reboot to boot normally!
Be sure to also run the Magisk app so it finishes setting itself up, with another reboot, naturally.
TechnicalitiesThe Infinix Hot 30 Play does have a dedicated vbmeta partition, it's advised that you also flash it alongside flashing the patched boot.img for Verified Boot, but that's not necessary if you don't want to tinker with your super partition's crypto keys.
Thank yous- topjohnwu for their work on Magisk.
- ansh_/ and their post/guide on rooting the Infinix Hot 11, that I used originally.
Addendum
Using fastboot with MediaTek SoCs will be a bit of a pain as their driver availibilty is limited, if it doesn't get installed by Windows automatically, you have a few options:
Grab the Google's Pixel driver, and install it in realtime during fastboot.
Try to install the VCOM driver from a source you trust.
For grabbing the Google one, you'll have to:
Extract the driver somewhere easy to access.
Open Windows' Device Manager.
Plug in your phone during fastboot to your Windows PC.
Replace the "Unknown" entry for your phone with the Google driver in device manager, within the 60 second window it stays open in.
Note that you'll have to do this every time you go into fastboot.