Related
So in this guide or tutorial i'll show you how to patch boot.img so it doesn't fails to boot.
what you'll need
Python (We're using a python script to unpack/repack)
This python script https://github.com/liudongmiao/bootimg
Text editor (notepad++) for windows is a good thing
Patience
Now if you have python installed navigate to the folder where your bootimg.py & boot.img exist
now open cmd or terminal depending on what system you're using. and enter:
python bootimg.py --extract-bootimg
python bootimh.py --extract-ramdisk
Now we need to disable dm-verity and such
To disable system check change: ro,barrier=1 wait,verify > ro,barrier=1 wait
it is recommended to do this to all partitions u want to be able to modify later.
now you can also remove dm-verity executable and is not needed and it most likely will cause your boot.img to fail.
There's probably need to patch se policy file as well so you could use phh zip to do this.
And thats it. Post 2 is to add superuser access but it'll be later
How to swap from phh to chainfire supersu
Open init.environ.rc and add
export PATH /su/bin:/sbin:/vendor/bin:/system/sbin:/system/bin:/su/xbin:/system/xbin
Above bootlogo
Now download the two zips and extract su folder to root of ramdisk
And the sbin to sbin folder but don't remove any files!
Now if u have trouble with remount system as rw you need to edit the fstab and remove the verify on its partition. Now just repack ramdisk and then repack boot and you should be done
LastStandingDroid said:
So in this guide or tutorial i'll show you how to patch boot.img so it doesn't fails to boot.
what you'll need
Python (We're using a python script to unpack/repack)
This python script https://github.com/liudongmiao/bootimg
Text editor (notepad++) for windows is a good thing
Patience
Now if you have python installed navigate to the folder where your bootimg.py & boot.img exist
now open cmd or terminal depending on what system you're using. and enter:
python bootimg.py --extract-bootimg
python bootimh.py --extract-ramdisk
Now we need to disable dm-verity and such
To disable system check change: ro,barrier=1 wait,verify > ro,barrier=1 wait
it is recommended to do this to all partitions u want to be able to modify later.
now you can also remove dm-verity executable and is not needed and it most likely will cause your boot.img to fail.
There's probably need to patch se policy file as well so you could use phh zip to do this.
And thats it. Post 2 is to add superuser access but it'll be later
Click to expand...
Click to collapse
Sorry, which tool do you use in order to extract boot img from UPDATE.APP?
And after unpack and repack ramdisk and boot is it normale that the new boot.img is smaller than the "original" boot.img?
Thanks, I'm trying to patch honor 5c boot image in order to root it.
Huawei Firmware Extractor will unpack the UPDATE.APP.
LastStandingDroid said:
So in this guide or tutorial i'll show you how to patch boot.img so it doesn't fails to boot.
what you'll need
Python (We're using a python script to unpack/repack)
This python script https://github.com/liudongmiao/bootimg
Text editor (notepad++) for windows is a good thing
Patience
Now if you have python installed navigate to the folder where your bootimg.py & boot.img exist
now open cmd or terminal depending on what system you're using. and enter:
python bootimg.py --extract-bootimg
python bootimh.py --extract-ramdisk
Now we need to disable dm-verity and such
To disable system check change: ro,barrier=1 wait,verify > ro,barrier=1 wait
it is recommended to do this to all partitions u want to be able to modify later.
now you can also remove dm-verity executable and is not needed and it most likely will cause your boot.img to fail.
There's probably need to patch se policy file as well so you could use phh zip to do this.
And thats it. Post 2 is to add superuser access but it'll be later
Click to expand...
Click to collapse
In which file we have to edit this line "ro,barrier=1 wait,verify > ro,barrier=1 wait". I have infinix smart 5 x657b. I extracted the boot file and from some instructions on google, I opened fstab file. But there is nothing like that line.
hassansuriya said:
In which file we have to edit this line "ro,barrier=1 wait,verify > ro,barrier=1 wait". I have infinix smart 5 x657b. I extracted the boot file and from some instructions on google, I opened fstab file. But there is nothing like that line.
Click to expand...
Click to collapse
There is a way to remove dm-verity and forceencrypt by just flashing a file in twrp.
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
CHECK_123 said:
There is a way to remove dm-verity and forceencrypt by just flashing a file in twrp.
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
Click to expand...
Click to collapse
but there is not any version of twrp recovery for my device. From where should I download it?
hassansuriya said:
but there is not any version of twrp recovery for my device. From where should I download it?
Click to expand...
Click to collapse
I found this "auto twrp recovery porter"
Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek
If you wish to root your Mediatek Android phone, we'd dropped a guide on rooting using Magisk and stock boot.img at https://www.hovatek.com/forum/thread-21427.html , no custom recovery is required. Se
forum.hovatek.com
I dont know if it would work, you should try
You may have to sign up to get the andorid 9 and 10 version of the tool
mod edit - content removed
thread closed
I think VPN method is not safety.
You should replace hosts file with twrp.
Modified system can boot with locked bootloader.
parduscix said:
I think VPN method is not safety.
You should replace hosts file with twrp.
Modified system can boot with locked bootloader.
Click to expand...
Click to collapse
This juat filters and your method can also be tried
This is for those who are unable to uninstall Newer KingRoot using old Methods like SuperSUMe Free and old terminal emulator method by Mr.W0lf and waiting to uninstall Newer Kingroot versions.... or want to remove Kingo ROOT in a simple way.
Features:-
-Removes Kingroot v5.x (tested on latest v5.3.7-197), Kingo ROOT
-Removes all files of King(o)root in whole device
-Installs SuperSU-v2.82-SR5 to /system without custom-recovery and force system even on 6.0+
-No need of manual updating of su binary
-Installs latest Busybox to /system/xbin
Requirements:-
==> Terminal Emulator
==> Below attached ZIP
Procedure:-
To uninstall completely the script deletes files multiple times.
Optionally Untick KingRoot in Settings App->Security->Device administrators->KingRoot
Method 1:-
1.Make a folder with name mrw in internal storage
Extract this zip in that mrw folder
2.Download Terminal Emulator and run following commands
Bash:
su
sh /sdcard/mrw/root.sh
3.After succeeded with Green text type following
Bash:
sh /sdcard/mrw/root.sh
After this, your device will reboot by installing SuperSU
If your device not rebooted, then try executing root.sh for 5 times...
If still not rebooted then try other method
4.After booted open Terminal Emulator app and type following
Bash:
su
sh /sdcard/mrw/root.sh
Method 2 :- by uninstalling KingRoot manually
Root again with KingRoot
and follow below procedure
1.Type
Bash:
su
in Terminal Emulator and go to KingRoot app
Tap on 3 dot and
choose settings and
choose remove root, untick keep backup option and unroot
Note:- If your device rebooted at time of unrooting, this method will not work
2.Go to Terminal Emulator and type following
Bash:
sh /sdcard/mrw/root.sh
Your device will reboot after that and rooted with SuperSU
Method 3 :- by using older version of KingRoot
Requires :- Android Version less than 5.0
1.Unintall Kingroot by going to KingRoot app
Tap on 3 dot and
choose settings and
choose remove root, tick keep backup option and unroot
2.Install older version of KingRoot eg v4.5.0 from apkmirror
and root with it
3.Follow Method 1
Method 4 :- by using Kingo ROOT instead of KingRoot
1. Probably your device will lose root of KingRoot after following above methods, so root your device with Kingo ROOT.
2.Follow Method 1
Method 5 :- by using Magisk Manager
Requires :- 1)Android Version greter than or equal to 5.0
2)Unlocked bootloader (else your device will soft brick)
1.Reroot with KingRoot
2.Install Magisk Manager
install Magisk by connecting to internet
and tap on install option
and choose Direct Install(Recommended)
3.Go to Terminal Emulator and type following
Bash:
su
and go to Kingroot app
4.Uninstall Kingroot as said in Method 2
5.Go to Terminal Emulator and type following
Bash:
sh /sdcard/mrw/root.sh
reboot your mobile, after reboot
Bash:
su
sh /sdcard/mrw/root.sh
Method 6 :- by using SuperSU Me pro
If replacing Kingroot with SuperSU method from above doesn't work for you
You can try SuperSU Me by @gatesjunior
Which will remove all Kingroot apps installed in your device
Download and install Super-Sume Pro apps
Forum link: http://forum.xda-developers.com/general/paid-software/supersu-please-t3110954
Thats it...!
Thanks to @Mr.W0lf for this
If you want to create issue or suggest file edit through pull requests
Source:- https://github.com/HemanthJabalpuri/Replace_KingRoot_with_SuperSU
SHA1 of v5.zip:- 5cb2508180a4edc12316acfd4cb0fb59ad4dd402
Donate:- https://www.paypal.me/hemanthjabalpuri
Enjoy !
Test zip for testers:-https://github.com/HemanthJabalpuri/Replace_KingRoot_with_SuperSU/archive/master.zip
Testers:-
People who has custom recovery and know some basic things about restoring nandroid backup and get out of soft brick can test by following procedure....
-Root with SuperSU by flashing super.zip in recovery....
-Go to settings of SuperSU and choose switch super user and reboot...
-Install latest Kingroot.apk from apkmirror....
-Install and select fix now below Root Auth Error
It will root with Kingroot...
Test the zip by following procedure in first post....
Send the root.log in /sdcard/mrw folder... by making a post in this thread
Developers:-
For app devlopers who want to make this as an app can see some source examples from
==> https://github.com/inX95/RmKingroot
==> https://github.com/EliteTutorials/Open-King-Remover
Kingroot FAQ:-
https://forum.xda-developers.com/an...ot-tool-android-2-x-5-0-t3107461/post60829420
All questions about SuperSU:-
https://forum.xda-developers.com/an...ot-tool-android-2-x-5-0-t3107461/post61857510
What are another easy ways to replace?
Note:- Need unlocked bootloader
-Search Custom Recovery(TWRP, CWM, PhilZ , etc) for your particular mobile
-Flash that recovery.img with app like Flashify, Rashr, Kernel Adiutor, ROM Installer, Root Essentials etc
-Boot into custom recovery and Flash SuperSU.zip or Magisk.zip
-Reboot and Enjoy.....
All about ROOTING
How to Root Any Device
How to Root Your Android
Best One Click Root Methods
Best Root Apps for Android
Best Apps for Rooted Android Devices
How to do Everything on Your Phone
XDA’s Top Picks for Everything
Older Versions:-
v4:- Changelog, Source ZIP
v3:-Changelog, Source ZIP
v2:- Changelog, Source ZIP
v1:- Initial, Source ZIP
Who use Kingoroot or superSU in 2019 just use magisk more simple and more efficiency...
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
black_file said:
Who use Kingoroot or superSU in 2019 just use magisk more simple and more efficiency...
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
Click to expand...
Click to collapse
Yes, but many old devices does not have custom recoveries and also many people who use those devices does not have a PC to flash patched boot.img... and also some devices does not have firmware available too....
Many device's bootloader also locked...
If we install magisk then it will definitely soft brick..
since on a bootloader locked mobile tweaking recovery or boot partition will get result like brick
Thats why some people stick with King(o) root.....
Terminal Emulator app is another app or its BusyBox?
AndroPhobia said:
Terminal Emulator app is another app or its BusyBox?
Click to expand...
Click to collapse
Another app
Should i install busy box in xbin or bin?
AndroPhobia said:
Should i install busy box in xbin or bin?
Click to expand...
Click to collapse
Both of them will work
Done Twice and worked in a M4 SS4452 Android 5.1.1
Thanks
AndroPhobia said:
Done Twice and worked in a M4 SS4452 Android 5.1.1
Thanks
Click to expand...
Click to collapse
Hey thanks
I made a test branch in github for advanced users which contain 4 methods of replacing root and also contain Magisk flashing...
https://github.com/HemanthJabalpuri/Replace_KingRoot_with_SuperSU/archive/v3-Magisk.zip
at https://github.com/HemanthJabalpuri/Replace_KingRoot_with_SuperSU/tree/test
Older Versions:-
are available in 4th post
Updated to v4
Changes:-
-Replaced with Stericson 1.30.1 Busybox
-Fixed Arch Detection
-Try to fix force closes of KingRoot when removing by installing older version of KingRoot(v4.5.0)
-Fixed 64bit devices not rebooting after replace
-Removes debuggerd too
-More logging info
Full Changelog here
This update is NOT tested...
If you are tester not having KingRoot installed then see 2nd post for info..
Update v5-test:-
This update does not have any zip.
All the files are embedded in script file.
Just place root.sh somewhere and execute.
Those files are extracted at the time of usage in execution.
If you want to extract only files to see what are they, then execute
Code:
root.sh -x all
will extract files in working directory.
https://www.mediafire.com/file/9ir3fzipfsouimm/root.sh
If you are a tester and want to test this, then see 2nd post for details.
Anyone tried any of this on OnePlus 6T (A6013)?
I'd like to say thank you it works on my BOOX Max Carta, Android 4.4.4
fishman8 said:
I'd like to say thank you it works on my BOOX Max Carta, Android 4.4.4
Click to expand...
Click to collapse
Can you please telegram me at
https://t.me/HemanthJabalpuri
Thanks
Thanks worked for my Z1 Compact at Android 5.1.1.
it is not working well as I found
Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/showthread.php?t=2073775
The first method was developed by osm0sis and removes magisk and all modules.
1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking 8mg
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work. Dot files are hidden files so if your root explorer can't see hidden files, run the "Remove disable_magisk" bat file in ADB.
1. Same as above but use the overlay.dcoreonly1.zip
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
****************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode in case you bootloop due to flashing a bad module and TWRP is not enough.
Once in fastboot:
fastboot boot image-newpixel2.img
You will boot with root but modules disabled. If something additional is needed, once booted to core-only, unzip the attached zip onto your pc where you can run ADB/fastboot and run the bat file. It will push .disable_magisk to your cache folder so that your modules will be disabled even after a reboot (zip says crosshatch but will work on any phone)
Boot image uploaded 11-24-19
https://www.androidfilehost.com/?fid=4349826312261644460
Custom Rom Xperia Z3CTW SGP611 Build 23.5.A.1.291_1290-4947_R2D By Mux
if you have questions or need files just PM me on XDA and i will try to help where i can...
the reason i made this tut is because there is almost no roms for this device available...
(not Responsible for any damages to device or peripherals through the process since there is always a chance something happens **but i had my device in almost every state and with the tools mentioned u should be able to revive it ** )
Included in this ROM (for you to build)
- Passes Saftynet
- Rooted with Magisk 20.4 (magisk hide working)
- Custom Kernel For Booting System and TWRP (made with rootkernel_v4.51_Windows_Linux.zip)
- Sony Ric Disabled / Enabled Depends on Rootkernel Config
- Netflix working
- Kernel can be set to Permissive via Terminal command.
- TWRP 3.0.2 (from Rootkernel_4.5.1)
- Remoteplay only works with Ric enabled and magisk uninstalled (make 2 boot.img for swapping in twrp)(due to sony device)
Apps i sugest u dl on ur rooted device
- FX File explorer
- Terminal for Android
- Netflix
- Vanced Manager
- Busybox (if needed)
IMPORTANT!! This Tutorial Ignores TA Partition So if you want to save them google How to Backup TA for SGP611 Before Following this Tutorial (some functionality can be regained through DRM opt in RootKernel
A Tutorial to Reproduce (*Do not Worry the Harder You Try The easier it gets)
1. Install Drivers for Fastboot and ADB in Device Manager for your device
- Boot Device to Fastboot by pressing Vol+ while Pluging USB Cable to PC Blue led indicates Fastboot Mode
- Go to Device Manager and Install Driver for S1boot
- Verify Driver installed Correctly
2. Install Flashtool Xperifirm, Flashtool Emma from Sony, Xperia Companion, copy Platform-tools folder to C:
(if u need any files PM)
3. Unlock Your Bootloader following instruction on Sony Developer Website (not going in to Details) *read warning above
before this
4. Download FTF firmware file With Flashtool Xperifirm For Your Device in My Case SGP611_23.5.A.1.291_1290-4947_R2D
By selecting XF Button in Flashtool after Closing xperifirm Flashtool will convert the files and they will be stored to
%user%\.flashTool\firmwares
5. Extract Kernel.sin Using 7zip or winrar from SGP611_23.5.A.1.291_1290-4947_R2D.ftf for patching boot.img
6. Open Flashtool and go to Tools menu select Sin Editor search and select the Kernel.sin Previously Extracted and press Extract
Data this will Create Kernel.elf
7. Go to RootKernelv4.51 Folder and copy the Kernel.elf there open CMD in address bar to folder and enter the command
(rootkernel kernel.elf boot.img) Select the option u like by Pressing y I selected all Options because I don’t have TA Backup
this will create a file Boot.img which is your Custom Boot Image if you want Recovery make Shure to say y when asked about
TWRP
8. Open PRFcreator and select all options click on the … for ftf and load the SGP611_23.5.A.1.291_1290-4947_R2D.ftf file
downloaded in step 3 click on the … for SuperSU and select the Magisk_20.4.zip set all check marks and create Flashable Zip
Zip is found in PRFcreator folder (this is your stock firmware zip)
9. Copy all files listed into a folder on your Internal storage
- Flashable-prerooted-signed.zip (created with PRFcreator)
- Moded Boot.img (Created with Rootkernelv4.51)
- Disable_ric_file.zip (if not moded in Boot.img)
- Magisk_20.4.zip (for Flashing Magisk After Flashing Boot.img)
10. Boot Phone in to Fastboot mode, Run CMD in address bar of Platform-tools folder, and Flash twrp 2.8.7.0 (yes will be
updated after Flashing Boot.img) by entering this command in ( Fastboot flash boot twrp-2.8.7.0-scorpion_windy.img )(**this
flashed to boot because u dont have recovery befor flashing the moded boot.img and this will be changed back by flashing
the stock ftf downloaded**)
if successful Unplug and boot tab it should boot to Teamwin TWRP recovery
11. In TWRP go to WIPE, Advanced Wipe, (Wipe: Cache, Dalvik-Cache, and System,)
before Flashing the Firmware Files
12. On main screen TWRP go to INSTALL and Install files following order
- Flashable-prerooted-signed.zip
- Moded Boot.img (by selecting flash image button at the bottom in TWRP)
- Disable_ric_file.zip
- Magisk_20.4.zip
13. Reboot to System Buy yourself a beer and Enjoy
where are the files ?