Hope I created new thread in right path. As by title, I found nothing about this 7'' tablet . I tried to unlock the bootloader with the command:
fastboot oem unlock-go
but it returns:
failed (remote: unknown command)
Meanwhile, I found nothing about a TWRP for this device. Are there chances that something will be developed? Is it a question of time? Thanks in advance.
i have the same problem. No one help us?
im trying to root mine so i can get the proximity sensor locked. I am building a tablet install in my RX8, using this tablet. However as soon as I pop it in the housing the screen has a mind of its own, sometimes it works sometimes it makes me want to smash it up
Systemlessly Root Lenovo Tab 4 7 TB-7504X
Hello all!!?
Here I will guide you to root Lenovo Tab 4 7 TB-7504X with the chipset MT8735B and Android version 7.0 that also systemlessly!! So let's get tuned into the Step by Step Guide...?
Firstly, I am not responsible for any kind of demage caused to your phone!!
Actually there are two methords of doing so...
Moving on to first one (Simplest),
You need to download latest version of MTK Easy Su v1.0.6 and the Magisk Manager specifically v7.1.1 I will provide link for both of them below...
Install both of them...
Now Firstly open the MTK Easy Su apk and just tap on 'Activate Bootless Root' if it says 'Exit value 0' in the Log section that means you have Root access on your phone...
Note:- Don't try to update Magisk or Magisk Masnager or Set environment for modules to work properly in Magisk Manager, else you will brick your phone
- Don't update Magisk Manager Directly from the apk
- The following process is done on lock bootloader so be carefull.
- You will have to Open the MTK Easy Su apk and tap on 'Activate Bootless Root' each and every time you Reboot your phone...
Pros:-
- Systemless Root
Cons:-
-Will not be able to Update Magisk Manager or Migisk itself
- Will not be able to install Magisk Modules
Second Method:-
For this to work on your phone you need couple of apks and Files...I will provide all the links at the end of this post...
Again, I am not responsible for any kind of demage caused to your phone!!
- Firstly, You need to download an apk named 'init.d Scripts Support' and also need to know your phone's architecture i.e 32 bit or 64 bit if you don't know just download any apk like CPU-Z or anything like that and note your phone's architecture...
- Now, you need to create an folder named 'init.d' in your phone's internal storage and again create another folder named 'bin' inside the 'init.d' folder
Now, you need to move some files in these folders to gain Root access...So let's move on...
- Firstly, Unzip all the Files...
- Open folder named 'magisk-boot' and copy the file named 'magisk-boot.sh' and paste it in 'init.d' folder
- Moving on to next file, then open folder named 'mtk-su_r22' then open the folder based on your phone's architecture i.e 'arm' or 'arm64' (For 32 bit architecture open 'arm' & For 64 bit architecture open 'arm64') and copy the file named 'mtk-su' and just paste the file inside the 'bin' folder of 'init.d' folder
- Moving on to last file to copy, open the folder named 'Magisk-20.4', then open folder named 'arm' there you will find 3 files here, we are just conserned about 2 files named 'magiskinit' & 'magiskinit64'. Just copy one of the two files based on your architecture (If 32 bit then copy 'magiskinit' & if 64 bit just copy 'magiskinit64') and paste it in 'bin' folder of 'init.d' folder. The one who have 64 bit architecture need to make a small change in the file 'magiskinit64' we just copied to 'bin' folder. Just rename the file and remove '64' written behind the file name.
Now your 90% of work has been completed!!
Now install the latest version of 'Magisk Manager' currently v7.5.1 is the latest.
- Now open 'init.d scripts support' apk and check the 'Run scripts at boot time' option.
- Then set 'Execution delay' to 'No delay'
- Now tap on 'Selected folder' and just locate the 'init.d' folder and select it.
Note:- Please let be the option 'Try to acquire root privileges' Uncheked!!
Lastly Reboot your phone and after Rebooting open the 'init.d scripts support' apk and just tap on 'Run scripts now' it will show 1 File selected and then it will Show 1 File Executed'!!
Then just tap 'Show last execution results' (You may need to watch an add every 24 hours) and if it shows 'client: launching new main daemon process' at the very least of the execution results...Congratulations!! Now you have got Systemless Root on your Lenovo Tab 7 TB-7504X successfully!!
Note:-
- Don't Mess around things you don't know on a locked bootloader or you would brick your device
- Don't update Magisk via the apk itself
- Be Carefull while installing Magisk Madules on a locked bootloader
- You will have to Run the init.d scripts support apk each and every time you reboot your phone to have root access enabled
You can search on YouTube for 'How to root Lenovo Tab 7 TB-7504X' (Second Method) the video is recently made by me
Channel's Name:- Tricky Everything
Sorry For the poor video and audio quality
If You Like the video please Like,Share, Subscribe and Comment...
Important Note:-
You can update the files Needed to have root access (basically Magisk itself) just be sure to place the correct file in the correct location and with the correct name!!
Files Needed to Root (First Method):-
MTK Easy Su v1.0.6 apk
Magisk Manager v7.1.1 apk
Files Needed (Second Method):-
MTK su_r22.zip (latest version)
Latest Magisk-boot.zip
Magisk-20.4.zip
Magisk Manager-v7.5.1 apk
RidhamSai said:
Systemlessly Root Lenovo Tab 4 7 TB-7504X
Hello all!!?
Here I will guide you to root Lenovo Tab 4 7 TB-7504X with the chipset MT8735B and Android version 7.0 that also systemlessly!! So let's get tuned into the Step by Step Guide...?
Firstly, I am not responsible for any kind of demage caused to your phone!!
Actually there are two methords of doing so...
Moving on to first one (Simplest),
You need to download latest version of MTK Easy Su v1.0.6 and the Magisk Manager specifically v7.1.1 I will provide link for both of them below...
Install both of them...
Now Firstly open the MTK Easy Su apk and just tap on 'Activate Bootless Root' if it says 'Exit value 0' in the Log section that means you have Root access on your phone...
Note:- Don't try to update Magisk or Magisk Masnager or Set environment for modules to work properly in Magisk Manager, else you will brick your phone
- Don't update Magisk Manager Directly from the apk
- The following process is done on lock bootloader so be carefull.
- You will have to Open the MTK Easy Su apk and tap on 'Activate Bootless Root' each and every time you Reboot your phone...
Pros:-
- Systemless Root
Cons:-
-Will not be able to Update Magisk Manager or Migisk itself
- Will not be able to install Magisk Modules
Second Method:-
For this to work on your phone you need couple of apks and Files...I will provide all the links at the end of this post...
Again, I am not responsible for any kind of demage caused to your phone!!
- Firstly, You need to download an apk named 'init.d Scripts Support' and also need to know your phone's architecture i.e 32 bit or 64 bit if you don't know just download any apk like CPU-Z or anything like that and note your phone's architecture...
- Now, you need to create an folder named 'init.d' in your phone's internal storage and again create another folder named 'bin' inside the 'init.d' folder
Now, you need to move some files in these folders to gain Root access...So let's move on...
- Firstly, Unzip all the Files...
- Open folder named 'magisk-boot' and copy the file named 'magisk-boot.sh' and paste it in 'init.d' folder
- Moving on to next file, then open folder named 'mtk-su_r22' then open the folder based on your phone's architecture i.e 'arm' or 'arm64' (For 32 bit architecture open 'arm' & For 64 bit architecture open 'arm64') and copy the file named 'mtk-su' and just paste the file inside the 'bin' folder of 'init.d' folder
- Moving on to last file to copy, open the folder named 'Magisk-20.4', then open folder named 'arm' there you will find 3 files here, we are just conserned about 2 files named 'magiskinit' & 'magiskinit64'. Just copy one of the two files based on your architecture (If 32 bit then copy 'magiskinit' & if 64 bit just copy 'magiskinit64') and paste it in 'bin' folder of 'init.d' folder. The one who have 64 bit architecture need to make a small change in the file 'magiskinit64' we just copied to 'bin' folder. Just rename the file and remove '64' written behind the file name.
Now your 90% of work has been completed!!
Now install the latest version of 'Magisk Manager' currently v7.5.1 is the latest.
- Now open 'init.d scripts support' apk and check the 'Run scripts at boot time' option.
- Then set 'Execution delay' to 'No delay'
- Now tap on 'Selected folder' and just locate the 'init.d' folder and select it.
Note:- Please let be the option 'Try to acquire root privileges' Uncheked!!
Lastly Reboot your phone and after Rebooting open the 'init.d scripts support' apk and just tap on 'Run scripts now' it will show 1 File selected and then it will Show 1 File Executed'!!
Then just tap 'Show last execution results' (You may need to watch an add every 24 hours) and if it shows 'client: launching new main daemon process' at the very least of the execution results...Congratulations!! Now you have got Systemless Root on your Lenovo Tab 7 TB-7504X successfully!!
Note:-
- Don't Mess around things you don't know on a locked bootloader or you would brick your device
- Don't update Magisk via the apk itself
- Be Carefull while installing Magisk Madules on a locked bootloader
- You will have to Run the init.d scripts support apk each and every time you reboot your phone to have root access enabled
You can search on YouTube for 'How to root Lenovo Tab 7 TB-7504X' (Second Method) the video is recently made by me
Channel's Name:- Tricky Everything
Sorry For the poor video and audio quality
If You Like the video please Like,Share, Subscribe and Comment...
Important Note:-
You can update the files Needed to have root access (basically Magisk itself) just be sure to place the correct file in the correct location and with the correct name!!
Files Needed to Root (First Method):-
MTK Easy Su v1.0.6 apk
Magisk Manager v7.1.1 apk
Files Needed (Second Method):-
MTK su_r22.zip (latest version)
Latest Magisk-boot.zip
Magisk-20.4.zip
Magisk Manager-v7.5.1 apk
Click to expand...
Click to collapse
i dont see any link bro
Related
Good evening ladies and gentleman.
I have HTC Titan I (x310e) with developer unlock and I was unable install and launch Julien Schapman apps - Advanced Config Tool and RegistryEditor. I was looking for a solution and today I have that.
We have to (my movie):
1. Download xap files:
- Advanced Config Tool - http://www.touchxperience.com/forum/viewtopic.php?f=11&t=890 (working good only version 1.5.0.0 to install in settings)
- RegistryEditor - http://www.touchxperience.com/forum/viewtopic.php?f=20&t=593 (working good only version 1.1.0.0)
2. Rename extension from *.xap to *.zip.
3. Open these with system (Win7) support (not 7zip, WinRAR, etc.).
4. Cut file: WMAppManifest.xml and paste in other folder.
5. Open that file with system text editor (right click and select edit).
6. Remove line with text: "INTEROPSERVICES" and save the changes.
7. Copy this file to zip folder with app.
8. Change it back to a *.xap extension and now we can deploy him.
Enjoy
EDIT
SORRRY APP LAUNCH BUT NOT WORKING. I LOOKING FOR NEXT METHOD.
it is not possible. Interop is what is required to make the app work. So without it you can install it but it wont work hence there is no way to do what you want currently
Relatedly, this fact has been known for... ever since the Mago betas came out, I think? So, probably about half the lifetime of the OS. I guess when things are that old, it's easier to "discover" stuff that doesn't work than read the old threads.
Your phone is interop-locked. You can only install or run apps without ID_CAP_INTEROPSERVICES, unless those apps come from the Marketplace. As a general rule, if an app requests ID_CAP_INTEROPSERVICES (or other capabilities), that's because it's using it for something...
Budniu said:
Good evening ladies and gentleman.
I have HTC Titan I (x310e) with developer unlock and I was unable install and launch Julien Schapman apps - Advanced Config Tool and RegistryEditor. I was looking for a solution and today I have that.
We have to (my movie):
1. Download xap files:
- Advanced Config Tool - http://www.touchxperience.com/forum/viewtopic.php?f=11&t=890 (working good only version 1.5.0.0 to install in settings)
- RegistryEditor - http://www.touchxperience.com/forum/viewtopic.php?f=20&t=593 (working good only version 1.1.0.0)
2. Rename extension from *.xap to *.zip.
3. Open these with system (Win7) support (not 7zip, WinRAR, etc.).
4. Cut file: WMAppManifest.xml and paste in other folder.
5. Open that file with system text editor (right click and select edit).
6. Remove line with text: "INTEROPSERVICES" and save the changes.
7. Copy this file to zip folder with app.
8. Change it back to a *.xap extension and now we can deploy him.
Enjoy
EDIT
SORRRY APP LAUNCH BUT NOT WORKING. I LOOKING FOR NEXT METHOD.
Click to expand...
Click to collapse
Followed the method to insall Advanced Config. Now how can I uninstall it? Since I have 3 unsigned app limit, so I cant afford to waste a slot on an app that highly desirable but not useful.
elixir_pr said:
Followed the method to insall Advanced Config. Now how can I uninstall it? Since I have 3 unsigned app limit, so I cant afford to waste a slot on an app that highly desirable but not useful.
Click to expand...
Click to collapse
You can try to install ORIGINAL Advanced Config Tool file - you get error but uninstall actual version from the system.
I found details here
http://forum.xda-developers.com/showpost.php?p=30946303
But many many things are unanswered
Requisites:
1. XUltimate or any other similar tool which can pull all the Apk's and Framework's from the phone.
2. Rom Kitchen (Link On OP)
3. Zip utilities.
4. Deodex Empty Shell zip. (Deodex_Cwm_Shell .zip - 236 KB)
5. Windows (Cygwin) or Linux ( I won't go into technicalities)
How:
1. Pull all the Apk's and Framwork's along with the .odex files.
2. Rename the folder with the Apk's as "app"
3. Rename the folder with the Framework's as "framework"
4. Create a folder called Deodex_Cwm. (You can choose your name).
5. Inside the Deodex_Cwm folder, create another folder called system.
6. Copy the app and framework folder with the apk's and framework's into system.
7. In the case of ION, I found that there is a file "playstationcertified.odex", rename it to "com.playstation.playstationcertified.odex".
7. Zip the Deodex_Cwm folder.
8. Copy this zip into "original_update" folder inside Rom_Kitchen folder.
9. Run the menu script.
10. From menu select "0 - ADVANCED OPTIONS", then select "24 - Miscellaneous options / Plugin scripts".
11. Now select "(4) Batch_Deodex"
12. Press Enter to continue.
13. Press Enter Again to continue.
14. Press Enter Again to continue.
15. Press Enter Again to continue.
16. Now the Deodexing process will start. It will show a message when the process ends.
17. Rom_Kitchen creates a WORKING_mmddyy_hhmmss folder for processing the files.
18. Once the processing is done, the files are moved to batch_mmddyy_hhmmss.
19. Open the Deodex Empty Shell zip (do not extract). drag and drop the app and framework folders from the batch_mmddyy_hhmmss into the system folder inside the opened zip.
20. You also change the Text inside the updater script in the folder "META-INF/com/google/android" inside the open zip. Use notepad++ under windows, under linux you can use any editor.
21. Now close the zip and copy it to the external sd card in the phone and flash it using CWM Recovery.
Click to expand...
Click to collapse
Requisites No 5. Windows (Cygwin) or Linux ( I won't go into technicalities) , and then is is use of this Windows (Cygwin) ? i cant find anything with it in above 21 options. what is this , this thing is listed in Requisite and then there is no use of it? even Cygwin name is not used any where after Requisites No 5.
in how to. 9. Run the menu script.
What is Menu script ? there is no menu script in Rom_Kitchen folder, it is just a file with name menu ( without extension)
Writer give link to downloads on page http://forum.xda-developers.com/showthread.php?t=1863052
i download file for my xperia ion, but now what ? what is use of it on Above 21 how to options?
waqasazfar said:
I found details here
http://forum.xda-developers.com/showpost.php?p=30946303
But many many things are unanswered
Requisites No 5. Windows (Cygwin) or Linux ( I won't go into technicalities) , and then is is use of this Windows (Cygwin) ? i cant find anything with it in above 21 options. what is this , this thing is listed in Requisite and then there is no use of it? even Cygwin name is not used any where after Requisites No 5.
in how to. 9. Run the menu script.
What is Menu script ? there is no menu script in Rom_Kitchen folder, it is just a file with name menu ( without extension)
Writer give link to downloads on page http://forum.xda-developers.com/showthread.php?t=1863052
i download file for my xperia ion, but now what ? what is use of it on Above 21 how to options?
Click to expand...
Click to collapse
Post your question under Ion dev. deodex thread.
Sent from my Ion* using Tapatalk 2
waqasazfar said:
I found details here
http://forum.xda-developers.com/showpost.php?p=30946303
But many many things are unanswered
Requisites No 5. Windows (Cygwin) or Linux ( I won't go into technicalities) , and then is is use of this Windows (Cygwin) ? i cant find anything with it in above 21 options. what is this , this thing is listed in Requisite and then there is no use of it? even Cygwin name is not used any where after Requisites No 5.
Rom Kitchen Requires Linux. So either use Linux as OS or install Cygwin under Windows. How to use Linux/Cygwin is beyond the scope of the tutorial.
in how to. 9. Run the menu script.
What is Menu script ? there is no menu script in Rom_Kitchen folder, it is just a file with name menu ( without extension)
to run menu, type the following in command prompt.
chmod +x menu (required only once to make menu executable script)
./menu
Writer give link to downloads on page http://forum.xda-developers.com/showthread.php?t=1863052
i download file for my xperia ion, but now what ? what is use of it on Above 21 how to options?
It is for you to download Cygwin
Click to expand...
Click to collapse
Answers under your question.
Thankyou
ganeshbiyer said:
Answers under your question.
Click to expand...
Click to collapse
Thankyou.
I am not responsable of any damage in your phoneHi i have create this aow.wim images with ROOT bin and uncheked not to used BT and GSM in android apps but I cant copy it so system32/aow.wim
Can someone test it and put how to copy the image to pohne and most important if it works and if it is rooted you need to install SuperSU or others apps but bins are there...
Install route WINDOWS/System32/aow
Download:
http://www.mediafire.com/download/n68tle0kzd29b3e/aow.wim
For now i am tired of thinking i will try next day if i got time for it to copy to phone and try iif it works
This most likely won't work. The aow.wim on the system has extra headers that have Android-specific metadata attached to it. I see that you most likely just copied the contents out of it and then created a NEW wim, as it's impossible to commit changes to the aow.wim that comes with the update due to it complaining about WIMBoot.
snickler said:
This most likely won't work. The aow.wim on the system has extra headers that have Android-specific metadata attached to it. I see that you most likely just copied the contents out of it and then created a NEW wim, as it's impossible to commit changes to the aow.wim that comes with the update due to it complaining about WIMBoot.
Click to expand...
Click to collapse
I run dism comands and one ofgf them was create image from folder that was the previously one extract from phone and mod and it give me ok and the aow.wim image but now i dont know how to put it in system32 to try it
werty100 said:
I run dism comands and one ofgf them was create image from folder that was the previously one extract from phone and mod and it give me ok and the aow.wim image but now i dont know how to put it in system32 to try it
Click to expand...
Click to collapse
I not 100% sure if i'm correct in saying this but I don't think there is actually any method of putting the new aow.wim into the AOW folder, as using MTP or the built in file explorer either returns Permission error on unknown error respectively and @snickler has found that you cannot write to that directory using his SFTP method.
Plus @ADeltaX has managed to get root 2/3 working but project astoria doesnt allow two apps to overlay each so you cannot grant root access as there is no superSU pop-up. So he is working on modding superSU.
Just turn off "Protection against false touches" or smth like that in SuperSU (Settings)
I was curious to know to how xposed framework can be installed on the Huawei GX8 so I went through different sites to find at least an easy way to do that but honestly i didn't find any easy steps. They are more or less complicated depending on the individual attempting the procedure. ok
It is advised to take complete backup before deodexing so that you can replace the deodexed apps with the odexed backups in case you face some Apps crashing. Deodexing is important in order to make xposed framework install successfully and use some modules as well.
Warning: You attempt this procedure at your own risk, bare in mind that I will not be held responsible if you brick your device for attempting this procedure.
Prerequisites:
Rooted device.
Fully functional TWRP recovery or any other recovery with File manager support.
Backup all your data & apps.
Download this APP for deodexing:https://docs.google.com/uc?id=0BwSanb5zBfFiaHN5MGV2ZnFqcVU&export=download
Deodexing the ROM:
Step 1: Extract the BatchAPKTool to your preferred location.
Step 2: Open BatchAPKTool.exe. Set Language to English when prompted.
Step 3: The tool will now ask you to chose task.
Step 4: Type 83 and set smali version to smali-2.1.2.jar by entering 2. Now type 84 and set Android API level to 21 (Android 5.0), 22 (Android 5.1.1) or 23 (Android 6.0). This value must match with the firmware you have currently installed on your device.
Step 5: Now connect your device to PC. Make sure USB Debugging Mode is enabled and necessary Huawei Drivers are installed.
Step 6: In BatchAPKTool window, type 13 and then enter 4. This will pull all files from /system/app , /system/framework , /system/priv-app from your device. This may take some time so wait patiently. (You might also do it manually using Root Explorer)
Step 7: Once it’s done press Enter to return to main BatchAPKTool Menu.
Step 8: We’ll now deodex the apps. Enter 01 in the tool. It will now ask you for your ARM version. Enter “arm” and press Enter. Wait for the process to be completed.
Step 9: In the directory where you have extracted BatchAPKTool, you’ll find three folders named _priv-app, _app and _framework. Remove the underscore from the folder names so that they are now priv-app, app and framework respectively.
Step 10: Create a new SYSTEM FOLDER and name it DEODEXED SYSTEM and copy those three folders inside it. Now copy the System folder to your SD card or Internal Memory.
Replacing Odexed Apps with Deodexed Apps:
1: Boot your device into recovery and backup System partition
2: Using the built in file manager in recovery, delete the app, framework and priv-app folders from your system partition.
VERY IMPORTANT: Make sure that in twrp in the "Mount" section the "Only mount system read-only" is unchecked in order to copy the files to system.
3: Now copy the app, framework and priv-app folders from system folder (which we copied to SD card or Internal) and paste them to the SYSTEM partition i.e. /system/
4: When done, reboot your device. First boot will be extremely long. Might take 20-30 minutes so be patient.
ALTERNATE METHOD:
NOTE: It may not be possible to copy files from one folder to another in recovery mode, so this is what i did...
1. Create a NEW FOLDER in your internal memory and name it ORIGINAL SYSTEM.
2. Copy PRIV-APP, APP and FRAMEWORK from the ORIGINAL SYSTEM FOLDER and paste it in the ORIGINAL SYSTEM FOLDER in the memory of your device.
3. Now copy the THREE files in the DEODEXED SYSTEM FOLDER to the ORIGINAL SYSTEM FOLDER in the root of your device.
4. Your device will reboot immediately the files are copied. The boot may take 20-30 minutes so be PATIENT..
Installing Xposed Framework.
1. Go to the official thread and download the latest version(xposed-v86-sdk23-arm64) for Marshmallow
2. Download the apk and the uninstaller arm zip just in case anything goes sideways you can flash the uninstaller to unistall xposed framework.
3. Install the apk file and flash the v80-sdk23-arm zip in recovery. Again device might take 20-30 minutes to boot.
4. For Android 6.0:
Open build.prop
add these lines ro.config.hwtheme=0
ro.config.hw_theme=0
For Android 5.0-5.1.1:
Open local.prop (in system/emui/base/prop/local.prop)
add these lines ro.config.hwtheme=0
ro.config.hw_theme=0
The commands is to ACTIVATE the framework.
Thanks to mfbcool for the guide and Rockchip for Batch tool.
OK I have successfully installed xposed installer and some xposed modules, however some of the modules seem not to be working.
Partially working modules....
N-ify
Not working.......
Gravitybox
Lockscreen Mods
Qs tiles per row
xnotifications
Working.......
YouTube Adaway
Greenify
Maxlock
Flat Style Bar Indicators
Jit Screen On
Has anyone tried this method and had some success .....?
Ok. I'm now on cyanogenmod so I will be releasing xposed modules that are working perfectly on the rom. Stay tuned.
Its been a while. Yeah, have been busy with school and work.
Ok, here's a list of xposed modules working flawlessly with cyanogenmod.....
Gravitybox MM
Flat Style Bar Indicators
Android N-ify
Blurred System Ui MM
ifont
Youtube adaway
Maxlock
USB for Marshmallow
Adblock
Greenify
The list will be updated with time. If I helped you in any way, don't forget to hit the like button... Thanks
Sent from my HUAWEI GX8 using XDA Labs
Good joob BRO
bro i have LAG after install xposed its work 100% but there is some lag in apps
Ahmed-Iraq said:
bro i have LAG after install xposed its work 100% but there is some lag in apps
Click to expand...
Click to collapse
Sorry for the late reply....which apps are you experiencing lags with???
Sent from my Nexus 6 using Tapatalk
1. To extract the image collection from your downloaded rom :
Download Payload Dumper from here (It's a zip file but it's not flashable) to your computer
Extract the zip file to a folder, make it a folder you can use regularly because this is the default tool you would use from now on
Download the rom version you want to root
Unzip the rom to a folder, you will find a file within it called payload.bin
Copy and paste that file into the "payload_input" folder within the Payload Dumper folder you created
Execute the payload_dumper.exe file within Payload Dumper folder, you will not have to specify any options as it always extracts from any payload.bin file in payload_input and outputs the image files to payload_output.
Leave the extraction to be completed, the program will automatically close itself once it's completed
Your extracted .img files will be shown within the payload_output folder
2. If you need to root the boot image you extracted :
Copy the boot.img file from the payload_output folder to a folder on your phone storage (Best to name it appropriately if you will be doing this regularly)
Download and Install the latest Magisk apk from the release site (Accept any prompt to allow install from external source)
Launch the app and then choose Install under the top "Magisk" section
Choose Select and Patch a File then browse to where you copied the boot.img on your storage
Magisk will then apply root to the boot image you specified, Your rooted image file will be output to your phone's Download folder : /sdcard/Download
You don't need to keep the default filename of the rooted image file so you can rename it appropriately for the rom version after you copy it to your computer, just ensure to keep the .img file extension
If you rename the rooted boot image, try not to use spaces in the filename, rather use _ or - as spaces make it more difficult to use in a command window although when you start typing the filename you can use TAB to autocomplete it, always ensure the filename shows .img as the extension and at the end of any commandline
3. If you need to use your rooted boot image to apply root to your phone :
Install the drivers from the mounted drive you should get when connecting the phone to your computer
On Windows you should then have a folder in C:\Program Files (x86)\OnePlus USB Drivers\Android with the platform tools (ADB.exe and Fastboot.exe) you will need, you can obviously copy the content from that folder somewhere else if you wish.
Connect your phone to your computer
Copy your rooted boot image to the folder that has adb.exe and fastboot.exe
Open a command window on your computer by right clicking in that folder and choosing Open command window here
In the command window, Type or copy/paste the command ADB devices and press enter
If you see a prompt on your phone to allow the computer connection then accept it, better still, tell it to allow from now on also.
You should see a string of characters shown in the command window, if you don't see that, then try another cable or re-install your drivers and reboot the computer.
Reboot your phone into Fastboot either by using ADB on your computer ( ADB Reboot Fastboot ) or by enabling Advanced reboot in your developer options in settings and then hold down the power button and use the 3 dot menu on the top right and choosing "Bootloader"
In the command window type Fastboot Boot <filename.img> i.e. Fastboot Boot rooted_boot.img and press enter
You should see a couple of lines in the command window telling you it's copying over to the phone, don't worry it's not being flashed or replacing your existing installed boot image
The phone should then restart and boot using the image from your computer, it will be a slightly slower boot than usual, your existing unlock method should still work
Launch the Magisk app, it should already have root access because the boot image you've used is already rooted
Go to Install under the top Magisk section
Choose Direct Install (Recommended)
Magisk will then apply root access to the boot image on the actual phone
You will be prompted to reboot the phone on the bottom right, do this to complete the process
You don't need the phone connected to your computer anymore as the installed boot image on the phone should now have root access
You can check for root either using any app which requires root or by using an app like Root Checker
Remember to empty the contents of payload_input and payload_output once you have finished, leaving them ready for any future rom versions
4. To retain root access after ROM/OTA update :
Install the update either from Oxygen Updater or from Settings > System > System updates
DO NOT REBOOT when prompted
Go to the Magisk app
Go to Install under the top Magisk section
Choose Install to Inactive Slot (After OTA)
Magisk will apply root to the newly installed boot image for the next version
Reboot when prompted by the Magisk app
The phone should reboot into the updated version with root already applied
Very nice write up! Hopefully many will read this and follow instructions. Too many threads being created with issues because they never bother to read.
Quick question as this is my first OnePlus device.
Will I lose root after a system update and will have to it all over again?
Levi4cyber said:
Quick question as this is my first OnePlus device.
Will I lose root after a system update and will have to it all over again?
Click to expand...
Click to collapse
Just added a new section to my original post for this.
Does flashing magisk change anything in encryption?
Does it wipe anything?
How do I get my ROM to extract the boot img?
Levi4cyber said:
Does flashing magisk change anything in encryption?
Does it wipe anything?
Click to expand...
Click to collapse
No and No
Levi4cyber said:
How do I get my ROM to extract the boot img?
Click to expand...
Click to collapse
Read the first post.
djsubterrain said:
Read the first post.
Click to expand...
Click to collapse
I'm asking where to get my ROM file, in order I should be able to extract the boot img?
A link? Somewhere on my phone?
Levi4cyber said:
I'm asking where to get my ROM file, in order I should be able to extract the boot img?
A link? Somewhere on my phone?
Click to expand...
Click to collapse
It's pinned at the top of the entire forum :
[OnePlus 9 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
They're also posted on OnePlus's site (eventually) :
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
Make sure the version matches the one you're using
I updated to latest version 11.2.4.4.LE15AA
Since there's nowhere to download the OTA package and extract the boot img, can I use the boot img of a lower version - 11.2.2.2 ?
Levi4cyber said:
I updated to latest version 11.2.4.4.LE15AA
Since there's nowhere to download the OTA package and extract the boot img, can I use the boot img of a lower version - 11.2.2.2 ?
Click to expand...
Click to collapse
No, definitely not.
Try Oxygen Updater in advanced mode, it should let you download the full rom.
If you were already rooted though, you should've been able to retain it by following the last section in my original post.
If not, then follow the first 2 sections
djsubterrain said:
No, definitely not.
Try Oxygen Updater in advanced mode, it should let you download the full rom
Click to expand...
Click to collapse
Since I'm completely new to OP, is Oxygen updater an app (if yes, is it this; https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater)? Or is it built into the phone?
Levi4cyber said:
Since I'm completely new to OP, is Oxygen updater an app (if yes, is it this; https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater)? Or is it built into the phone?
Click to expand...
Click to collapse
I've linked it, it's not a default app
djsubterrain said:
No, definitely not.
Try Oxygen Updater in advanced mode, it should let you download the full rom.
If you were already rooted though, you should've been able to retain it by following the last section in my original post.
If not, then follow the first 2 sections
Click to expand...
Click to collapse
In the oxygen updater app, if I select "full update" in update method it only gives me version 11.2.2.2., if I select "incremental update", it lets me download 11.2.4.4, and when I unzipped it I have a file payload.bin (it's only 105MB).
Should I use that? Or do I need a full OTA package to extract the boot IMG?
Levi4cyber said:
In the oxygen updater app, if I select "full update" in update method it only gives me version 11.2.2.2., if I select "incremental update", it lets me download 11.2.4.4, and when I unzipped it I have a file payload.bin (it's only 105MB).
Should I use that? Or do I need a full OTA package to extract the boot IMG?
Click to expand...
Click to collapse
Are you choosing the correct OnePlus 9 Pro? It'll show you different variants under the model lookup.
To be honest, If I get the update pushed via OnePlus I always copy/paste it somewhere else cos I think it gets deleted once the upgrade is done.
If you extract the payload.bin and it shows a boot.img then that should suffice. I think it should be around 105MB (I'm on my work PC at the moment so can't check)
Thanks. I'm on the T-Mobile version of the OnePlus 9 Pro, technically my phone is currently on "11.2.2.2.LE5ACB" and the one on OnePlus's support site is "11.2.2.2.LE15AA". I'm not sure the difference but I assume T-Mobile bloatware. Hopefully they didn't do anything else to make the phone work "slightly better" on their network.
I'm not sure if the boot.img I extracted from 11.2.2.2.LE15AA will work with my currently-installed "11.2.2.2.LE5ACB"; any ideas?
Might be better to create a boot.img from my existing version and patch that. Do you know the dd command for me to just create the boot.img from my existing partition? In the past with other phones I've done something like "dd if=/dev/block/mmcblk0 of=/storage/sdcard1/boot.img bs=4096 count=4096 skip=7552" or "dd if=/dev/block/bootdevice/by-name/boot of=boot.img" but I don't know which partition on the OnePlus 9 Pro to image. Any ideas?
--- Update 1 ---
Code:
OnePlus9ProTMO:/ $ ls -l /dev/block/bootdevice/by-name/*boot*
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/boot_a -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/boot_b -> /dev/block/sde43
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/vendor_boot_a -> /dev/block/sde28
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/vendor_boot_b -> /dev/block/sde55
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/vm-bootsys_a -> /dev/block/sde24
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/vm-bootsys_b -> /dev/block/sde51
Then looking at my active mounts I saw this:
Code:
OnePlus9ProTMO:/ $ mount | egrep "sde16|sde43|sde28|sde55|sde24|sde51"
/dev/block/sde51 on /vendor/vm-system type ext4 (ro,seclabel,nosuid,nodev,relatime)
Which indicates that I'm on the "b" side. So I would want to create a boot.img from `/dev/block/bootdevice/by-name/vendor_boot_b` potentially. So this command "should" work, right?
Code:
dd if=/dev/block/bootdevice/by-name/vendor_boot_b of=/sdcard/Download/stock_boot.img
I might try that instead of the boot.img I extracted from 11.2.2.2.LE5ACB since it doesn't technically line up with the T-Mobile supplied ROM version.
--- Update 2 ---
Yeah, that didn't work.Turns out dd needs to be elevated to do its thing. Got a "Permission denied" when i tried to create the image. So yeah, ironically I need root to run said command and that's why I was trying to run the command, to get the boot.img to root. lol. oh well.
Thank you very detailed.
When I click on the payload_pumper.exe file, the cmd window flashes and nothing else happens.
glitchsys said:
Turns out dd needs to be elevated to do its thing.
Click to expand...
Click to collapse
Try watching this, man, I think this is exactly what you are missing:
Code:
https://www.youtube.com/watch?v=DyUainEJwLM