Hi guy's here's a short and simple guide on how to patch your own boot.img with Magisk.
Recommended to patch your own image read this
Grab the latest Platform Tools HERE
Code:
1. Download a stock Oxygen OS ROM Zip from [URL="https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156267635"]Here[/URL] Or the general section of XDA many users post links to the latest builds.
2. Download [URL="https://androidfilehost.com/?fid=818070582850510260"]payload_dumper-win64.zip[/URL] And extract/copy it to Desktop.
3. Extract your payload.bin from the stock rom zip and copy it into the payload_input folder.
4. Run the payload_dumper exe.
5. When it's finished open the payload_output folder and copy the boot.img to Desktop keep it there as a backup.
6. Copy the same boot.img to your internal storage on your phone.
7. Install the magisk manager APK from here: [URL="https://github.com/topjohnwu/Magisk"]Magisk Manager[/URL]
8. Open Magisk Manager choose install and select "Select and Patch a file" Or if you wish to use beta release go to settings > Update Channel and switch to beta and then back to Install "Select And Patch A File"
9. Navigate to where you copied your boot.img on the phone.
10. Once it's patched you'll have an magisk_patched.img on your phone in the the Downloads folder.
11. Copy that image to your fastboot folder on your PC and flash it with fastboot flash boot magisk_patched.img
Done!
As always I'm not responsible for any issues your device might have or if your cat sets on fire.
Credits:
topjohnwu for Magisk/Manger
geminids14 for payload_dumper-win64
Nice, that is what we need .. Thanks Liam
How can i load twrp? Fastboot boot command, didnt work
DevrimSeven60 said:
How can i load twrp? Fastboot boot command, didnt work
Click to expand...
Click to collapse
Ask in the TWRP thread
Not working for me get a error file is to large to download when try to flash
dajumper said:
Not working for me get a error file is to large to download when try to flash
Click to expand...
Click to collapse
You're on OB1? It worked fine for me I flashed it multiple times already
I think I know the issue try updating your fastboot files from here: https://developer.android.com/studio/releases/platform-tools
liam_davenport said:
You're on OB1? It worked fine for me I flashed it multiple times already
I think I know the issue try updating your fastboot files from here: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Still the same
Im already rooted with bootimg having lat pie release. Is it possible to flash Android Q on top of last pie release and be rooted? Again I am rooted with magisk, not having twrp.
To update I always flash full updat from local, not reboot, install magisk to other slot and I was ready to go.
Will this work with Q update?
Not working for me. Both sims dissapear and phone keeps FC.
pister said:
Not working for me. Both sims dissapear and phone keeps FC.
Click to expand...
Click to collapse
Issue is on your end, I've flashed this multiple times no issue.
Working perfectly here I've clean flashed and redownloaded from the link and flashed. I've noticed sometime magisk causes sims to not show on boot before reboot the device and they should show again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I see that when I root, both IMEIs disappears. Very strange
Sent from my [device_name] using XDA-Developers Legacy app
error 1 (or 7 kinstalldeviceopenerror) with 52 and 3.3.1-4 ???
what are the proper steps to cleanflash
pister said:
I see that when I root, both IMEIs disappears. Very strange
Click to expand...
Click to collapse
Mine both show. Not sure why yours have disappeared
liam_davenport said:
Mine both show. Not sure why yours have disappeared
Click to expand...
Click to collapse
Don't know. Tried to root by myself and the same happened
Sent from my [device_name] using XDA-Developers Legacy app
NateDev said:
error 1 (or 7 kinstalldeviceopenerror) with 52 and 3.3.1-4 ???
what are the proper steps to cleanflash
Click to expand...
Click to collapse
If you have twrp already you don't need this I posted this for people that want root without using twrp, Just flash magisk 19.4 in twrp
There is a few guides in this forum section with all info you need on how to flash etc
Weird.. Flashing patched file would always result in bootloop. Restore to boot. IMG fixed it
mgear356 said:
Weird.. Flashing patched file would always result in bootloop. Restore to boot. IMG fixed it
Click to expand...
Click to collapse
You flashed it on Open beta 1?
liam_davenport said:
You flashed it on Open beta 1?
Click to expand...
Click to collapse
Yup open beta 1
Great thanks!
But can we update OTA to B2 with this?
@liam_davenport I'm sorry for the noob question, I just got my OP 7 Pro and never used one before, also, I've been away from everything root related for a long time.
Do I need to unlock the bootloader first in order to do this?
Related
Originally posted by Koushik Dutta on Google+:
I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes: update from 09.05.11
Fix the fact that some users were loosing root access with 5.0.1.0
Fix menu bug Even if you select no during wipe dalvik cache, it still says it wipes it (it is not actually wiping it, it is just a display bug)
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!
Click to expand...
Click to collapse
To flash recovery for Nexus S, download recovery and place it into your sdk tools folder. Reboot into bootloader and execute:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
ill try
Sent from my Google Nexus S using XDA Premium App
I'm on it!
Or you can directly flash it from Rom Manager
You can also just put it on SD and flash from terminal then reboot.
Edit- before someone asks
su(press enter)
flash_image recovery /sdcard/5014cw.img(press enter)
reboot recovery(press enter)
Obviously the sdcard/* is whatever you rename the file
sent from my nexus s on a kang from simms
zadnica said:
Originally posted by Koushik Dutta on Google+:
To flash recovery for Nexus S, download recovery and place it into your sdk tools folder. Reboot into bootloader and execute:
Code:
fastboot flash recovery recovery-clockwork-5.0.1.0-crespo.img
Click to expand...
Click to collapse
I wish I would have seen this BEFORE I updated. It kept taking me to bootloader screen!!!!! But I unistalled and installed and finally got it to work!
Sent from my Nexus S using Tapatalk
Hey guys,
Everytime I restore from a backup through Rom Manager with the new recovery, I lose root. Right now, I'm stuck at work and cannot flash a rom, theme, battery mod, etc. I'll go back to 4.0.1.4 as soon as I go home
Am I the only one?
Edit: Found a solution==> Reboot into Recovery, flash su.zip again, and it's all good now!
f.
suhas_sm said:
Or you can directly flash it from Rom Manager
Click to expand...
Click to collapse
doesn't work for me..
I always recommend not using rom manager for anything flashing related, most problems occur for people when they're using rom manager and get fixed when done through recovery or in this case terminal/adb
RevengeITA said:
doesn't work for me..
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms
sinik420 said:
I always recommend not using rom manager for anything flashing related, most problems occur for people when they're using rom manager and get fixed when done through recovery or in this case terminal/adb
Click to expand...
Click to collapse
Code:
fastboot flash recovery recovery-clockwork-5.0.1.0-crespo.img
I prefer my previous post using terminal
zadnica said:
Code:
fastboot flash recovery recovery-clockwork-5.0.1.0-crespo.img
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms
When i try to flash this through android terminal i get a whole bunch of errors saying that its out of memory. Any solutions? I also tried using rom manager and ended up with no recovery instead of a new version
It took me two or three tries through terminal
Robin_216 said:
When i try to flash this through android terminal i get a whole bunch of errors saying that its out of memory. Any solutions? I also tried using rom manager and ended up with no recovery instead of a new version
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms
Robin_216 said:
When i try to flash this through android terminal i get a whole bunch of errors saying that its out of memory. Any solutions? I also tried using rom manager and ended up with no recovery instead of a new version
Click to expand...
Click to collapse
What the errors?
Worked like a charm thanks
Backups are significantly faster, thanks. (Flashed using fastboot)
zadnica said:
What the errors?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These are the errors that appear. I however managed to flash it with rom manager after some tries so it works now.
Sent from my Nexus S using XDA App
Robin_216 said:
These are the errors that appear. I however managed to flash it with rom manager after some tries so it works now.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I had the same issue. What helped for me was (in Terminal) :
su
mount -o rw,remount /dev/block/mtdblock3 /system
chmod 755 /system/bin/flash_image (wait for a minute)
(Reboot if the next step didn't work)
flash_image recovery /sdcard/RECOVERY.img
Click to expand...
Click to collapse
If I use the latest one, can I boot into recovery by using Rom manager? Will Rom manager detect my latest clockworkmod?
Accidentally sent from my Nexus S using XDA Premium App
Strangely, *immediately* after flashing the new recovery, I have begun to experience the Nexus S Google Voice Search bug. In the two months I've had the phone, this never happened - not even once.
This was with a two week old CM nightly, and a Matrix kernel.
Regardless - I'm hoping we'll start to see 2.3.6 kernels/roms come out soon which will fix it permanently. I'm just shocked that this issue popped up immediately after flashing the updated Clockwork.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THIS IS A PROXY THREAD Creator and Maintainer is pershoot
This is CWM for the ASUS Transformer Pad (TF701T – Macallan).
-You must be unlocked (use ASUS’s unlock tool to perform this)
-You must be on 10.26.1.18 bootloader (updating to ASUS’s latest 4.3 release will install this)
For complete Info and Download: VISIT HERE
***Once there, check out the Recent Entries on the right side of the page for latest updates***
-Unlock your device using the ASUS Unlock tool.
-Boot in once and execute: adb reboot bootloader
Fastboot:
To boot the recovery:
fastboot boot recovery.img
To permanently flash the recovery:
fastboot flash recovery recovery.img
Source:
https://github.com/pershoot/android_device_asus_tf701t
https://github.com/pershoot/android_kernel_asus_tf701t
https://github.com/CyanogenMod/android_bootable_recovery
Creator and Maintainer:
@pershoot
Video Tutorial
Video Tutorial Thanks @wwjoshdew
Ah just saw screenies. Nice job pershoot.
Why is the version still 6.0.4.6?
CWM 6.0.4.7
OP Updated
Feb/2 OP updated
Small question: my device is on 10.26.1.17. Updating to the latest official 4.3 will definitely wipe the CWM recovery, and probably will make some of the apps not running any more (not mentioning loosing root, etc..)
Is it possible to install the CWM on such a ROM version (10.26.1.17) ? I've just tested booting it and booting (and using it as a backup) works.
I was on 6.0.4.6 and i used flashify to update. Worked fine.
hetzbh said:
Small question: my device is on 10.26.1.17. Updating to the latest official 4.3 will definitely wipe the CWM recovery, and probably will make some of the apps not running any more (not mentioning loosing root, etc..)
Is it possible to install the CWM on such a ROM version (10.26.1.17) ? I've just tested booting it and booting (and using it as a backup) works.
Click to expand...
Click to collapse
Both cromix and cm11 will require the latest bootloader to eliminate compatibility issues it is recommended to flash to the latest asus firmware
Sent from my SGH-T889 using XDA Premium 4 mobile app
@AngryDinosaur - I made a video on how to install Custom Recovery on your Transformer Pad TF701T!
http://www.youtube.com/watch?v=3IBN1YkBp3g
wwjoshdew said:
@AngryDinosaur - I made a video on how to install Custom Recovery on your Transformer Pad TF701T!
http://www.youtube.com/watch?v=3IBN1YkBp3g
Click to expand...
Click to collapse
included in the post alongside the screenshots. Thanks a lot!!!
OP updated 2/16, installation video tutorial included. Thanks to @wwjoshdew
recovery updated with baseline build and sorted dock sd card functionality and usbdisk functionality.
@pershoot I'd love for this recovery to include touch screen drivers. That way at least aroma could use the touch screen. Any ideas how to compile with the standard drivers included?
sbdags said:
@pershoot I'd love for this recovery to include touch screen drivers. That way at least aroma could use the touch screen. Any ideas how to compile with the standard drivers included?
Click to expand...
Click to collapse
i'll look in to it...
I'm getting a weird error I've never seen before trying to flash something with fastboot. :
fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
error: cannot load 'recovery.img' : No error
Any ideas?
lortay78 said:
I'm getting a weird error I've never seen before trying to flash something with fastboot. :
fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
error: cannot load 'recovery.img' : No error
Any ideas?
Click to expand...
Click to collapse
Make sure recovery.img is in the same folder as fastboot and you are running the cmd prompt from that folder.
sbdags said:
Make sure recovery.img is in the same folder as fastboot and you are running the cmd prompt from that folder.
Click to expand...
Click to collapse
Duh, I have platform-tools in my path so I can run them from anywhere. I forgot to cd to the directory. Thanks for airing out my brain fart.
lortay78 said:
Duh, I have platform-tools in my path so I can run them from anywhere. I forgot to cd to the directory. Thanks for airing out my brain fart.
Click to expand...
Click to collapse
Very common mistake that happens to the best of us
updated.
Hi,
I spent hours trying to get this to work before discovering there are two missing steps in the OP's instructions.
There's a shell script that calls an application that restores the stock boot loader on every boot.
You have to delete it.
Steps:
1. Root.
2. Install Root Explorer.
3. Go into /etc
4. Delete install_recovery.sh
5. Go into /system
6. Delete recovery-from-boot.p
You have to delete the files. You can't just rename them or change the extension because the system actually searches the filesystem for a file whose contents matches an MD5 hash and will find it if you rename it.
After you do this, THEN follow OP's instructions.
DISCLAIMER: I AM NOT RESPONSIBLE FOR WHAT MAY HAPPEN TO YOUR DEVICE, DO THIS AT YOUR OWN RISK.
Before I start: everything I'm going to post here, I learned from this thread: https://forum.xda-developers.com/maven-3/help/zte-maven-3-z835-root-t3705687/page9
VERSION OF MAGISK FLASHEAD v17.1 (Unfortunately no one has flashed version v18.1)
What we need (they will be in the links at the end):
-ZPST for AT&T (with this program we are going to flash the modified boot.img)
-Drivers: QDLoader, ZTE AndroidUSB and ZTE_V889F (in case the previous Zte driver does not work).
-Modified boot.img that are already flashed with Magisk, only the following versions are available:
-Z835V2.0.0B10
-Z835V2.0.0B12
-Z835V1.0.0B13
-Magisk Manager version compatible with v17.1
EVERYTHING YOU NEED IS IN A LINK AT THE END OF THE POST.
Let's get started.
I recommend to do a hard reset before starting, however, in one of my devices I did it having data and applications installed, if you have used kingroot or any other software in your phone, erase all trace of it so you do not have problems.
We download all the contents of the folder, install all drivers included, and the ZPST for AT&T.
Starting to flash:
WE NEED AT LEAST 50-60% of Battery
Turn off the phone and turn on pressing Vol Down + Power Button, the phone will start in FTM mode.
Open ZPST for AT&T and select version Z835
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING, remove the usim and sd card
Once inside the software we proceed to connect the cell phone.
1. You will see if the phone was recognized by the com port.
2. Download, this is where we will enter to download the firmware
3. You will see your information imei and so on.
This is how it will look once connected (Let's go to the download tab)
1. Let's select the firmware (it has to be the same as the cell phone otherwise it can corrupt the imei)
2. We chose where to keep a small log to check if everything went well.
3. HIT THE DOWNLOAD BUTTON!!!!!
WARNING: wait for the device to restart at least 2 or 3 times, one of them will be in FTM mode again, so do not panic, it will take a while in 3% or 5%.
When the phone starts normally, if you did a hard reset configure everything again, otherwise, we will proceed to install the magisk.
DO NOT INSERT THE SD CARD YET!
Magisk asks if I want to update to the latest version, press NO THANKS.
Proceed to uninstall
Now let's install the version of magisk manager we downloaded (com.topjohnwu.magisk_6.1.0-165_minAPI21(nodpi)_apkmirror.com.apk)
When the installation is finished we enter Magisk and this will ask us if we want to upgrade to the latest version, PRESS NO!
Now we will see that magisk is installed correctly.
We see that we can use all its functions.
We will proceed to verify if we have root access.
Download root checker
And Voila!
MEGA link: https://mega.nz/#F!ud8VwKRJ!-cJr7EJyhb1PkziNx5KvLQ
with this can you uninstall original system's apps such as device help, google apps? install recovery and titanium backup? I need to remove a lot of bloatware/default apps that is taking memory from the device
nvizync said:
Root
Click to expand...
Click to collapse
Nice work! This confirms that the bootloader is unlocked, which means we can then use just the firehose to flash these files. I will work on writing something up for that.
deadman96385 said:
Nice work! This confirms that the bootloader is unlocked, which means we can then use just the firehose to flash these files. I will work on writing something up for that.
Click to expand...
Click to collapse
Would love to see that, thanks for the reply! :good:
rickastillo said:
with this can you uninstall original system's apps such as device help, google apps? install recovery and titanium backup? I need to remove a lot of bloatware/default apps that is taking memory from the device
Click to expand...
Click to collapse
You can install titanium backup, twrp is not possible at this point, no one has done it yet, you can delete system apps through adb, using
Code:
adb shell pm uninstall -k --user 0 packagename
But i haven't figured out yet how to get rw permission on system/apps so i can delete system apk's.
@nvizync You should thank me for my boot.img mod of -Z835V2.0.0B10 (Magisk 17.1)
my boot.img mod of:
-Z835V1.0.0B13 (Magisk 18.1) Link: https://mega.nz/#F!88IiFapI!6Peah7woOOaIhusfYCAEcw
-Z835V2.0.0B10 (Magisk 18.1) link: https://mega.nz/#F!V4pAVIYQ!19tWE7_xk_aQtyiu050Y7A
-Z835V2.0.0B12 (Magisk 18.1) Link: https://mega.nz/#F!9lBVkQAZ!WqnRvYa4qcw5MgRxhp1hcA
Thanks for your detailed flash root tutorial
Alijosekt said:
@nvizync You should thank me for my boot.img mod of -Z835V2.0.0B10 (Magisk 17.1)
my boot.img mod of:
-Z835V2.0.0B10 (Magisk 18.1) link: https://mega.nz/#F!V4pAVIYQ!19tWE7_xk_aQtyiu050Y7A
-Z835V2.0.0B12 (Magisk 18.1) Link: https://mega.nz/#F!9lBVkQAZ!WqnRvYa4qcw5MgRxhp1hcA
Thanks for your detailed flash root guide
Click to expand...
Click to collapse
I totally forgot it, yeah, you deserve most of the credit, I linked the original thread, but I'm planning including all the credits.
@nvizync Look what I got! https://github.com/TwrpBuilderTests/android_device_zte_z835/releases/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-13
Some brave who flashes it?
Alijosekt said:
@nvizync Look what I got! https://github.com/TwrpBuilderTests...s/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-13
Some brave who flashes it?
Click to expand...
Click to collapse
Ok my way
nvizync said:
Ok my way
Click to expand...
Click to collapse
not boot twrp
Alijosekt said:
not boot twrp
Click to expand...
Click to collapse
Did you tried it
Alijosekt said:
@nvizync Look what I got! https://github.com/TwrpBuilderTests/android_device_zte_z835/releases/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-13
Some brave who flashes it?
Click to expand...
Click to collapse
I tried to flash it, but instead, I just got a bootloop, and I can't access the recovery mode anymore, I should flash the original recovery and see if it works.
nvizync said:
I tried to flash it, but instead, I just got a bootloop, and I can't access the recovery mode anymore, I should flash the original recovery and see if it works.
Click to expand...
Click to collapse
Done, i managed to enter in normal mode and use flashify to flash stock recovery.img.
Hi, I'm stuck at the first step. The ZPST download fails with the message that it can't find the file: sbl1.mbn Any thoughts?
penn462 said:
Hi, I'm stuck at the first step. The ZPST download fails with the message that it can't find the file: sbl1.mbn Any thoughts?
Click to expand...
Click to collapse
Are you using the custom boot.img listed in mega's folder?
nvizync said:
Are you using the custom boot.img listed in mega's folder?
Click to expand...
Click to collapse
Yes. I'm using the folder "Boot Mod Z835V1.0.0B13"
penn462 said:
Yes. I'm using the folder "Boot Mod Z835V1.0.0B13"
Click to expand...
Click to collapse
Thats odd, try this: download another folder B12 or B10, and just paste the B13 boot.img, maybe that could work, one of the devices i rooted was B13.
Well, I tried what you suggested, and now I get "download failed" and "failed to change mode before downloading firmware" It seems to be stuck in FTM. I guess it's bricked?
---------- Post added at 06:52 PM ---------- Previous post was at 06:48 PM ----------
Update: not bricked. Gonna try again.
penn462 said:
Well, I tried what you suggested, and now I get "download failed" and "failed to change mode before downloading firmware" It seems to be stuck in FTM. I guess it's bricked?
Click to expand...
Click to collapse
Fear not, that happened to me also, just keep in ftm and make a stock boot.img flash, provided in the mega folder. Paste the boot stock image inside the b13 folder
Placed stock boot.img into B13 folder in place of custom boot.img. The process failure point is now back to the missing sbl1.mbn problem. I can get the phone to start, however, so it's not bricked. Whew!
Hello,
I'm trying to patch my boot image without using Magisk App.(via PC) Is there any way to do this?
This is because everytime I do security update every month, I have to:
1. Download factory image
2. Unzip and get boot.img
3. Put boot.img in my phone
4. Patch boot.img with Magisk App
5. Move boot_patched.img to my pc and flash via fastboot
I find this very unefficient, and I want to automate 1~4 by just doing all the process in my PC.
Why wouldn't you install your update and before re-booting the phone go to the Magisk app and let it do the patching for you with "Direct Install" (or "Install to Inactive Slot" if you have device with dual partition)?
Andrologic said:
Why wouldn't you install your update and before re-booting the phone go to the Magisk app and let it do the patching for you with "Direct Install" (or "Install to Inactive Slot" if you have device with dual partition)?
Click to expand...
Click to collapse
@Andrologic This is because I root for VoLTE(Voice over LTE) patch and after that, I assume that I cannot update my phone via OTA. Long ago I tried updating with OTA and for as long as I remember it failed. Ever since that happened, I usually unroot first, do an update with either sideload or OTA or factory image(very often), root again with all the steps above, and so on..
If that's what you really need, just do what Magisk does. It's all on GitHub:
https://github.com/topjohnwu/Magisk/blob/master/scripts/boot_patch.sh
Didgeridoohan said:
If that's what you really need, just do what Magisk does. It's all on GitHub:
https://github.com/topjohnwu/Magisk/blob/master/scripts/boot_patch.sh
Click to expand...
Click to collapse
Ah, this was what I was looking for. Thank you.
@Didgeridoohan Do you happen to know where I can get the essential magiskinit and magiskboot binary?
From magisk v22.0 I see that magisk core and magisk manager got merged into one, and now I can't find the latest executable. (x86 too)
They're in the /lib/x86 and folder inside the .apk. If I remember correctly it should just be a matter of renaming them to magiskinit and magiskboot respectively.
Didgeridoohan said:
They're in the /lib/x86 and folder inside the .apk. If I remember correctly it should just be a matter of renaming them to magiskinit and magiskboot respectively.
Click to expand...
Click to collapse
You are talking about these "lib<binaryname>.so" files right?
Yup
Didgeridoohan said:
Yup
Click to expand...
Click to collapse
Thank you for the answer. I really appreciate it.
After update, make a boot.img backup via twrp (copy in twrp folder and rename to boot.img) patch via Magisk and flash new patched boot.img.
Os. I do not like a new method too.
Thank you guys, with these ideas I have been able to write a bash script to automate the whole process of downloading the latest build of lineageos, patch it on the phone using magisk (using adb shell), and flash it in fastboot mode, without needing any user intervention whatsoever.
Sathors said:
Thank you guys, with these ideas I have been able to write a bash script to automate the whole process of downloading the latest build of lineageos, patch it on the phone using magisk (using adb shell), and flash it in fastboot mode, without needing any user intervention whatsoever.
Click to expand...
Click to collapse
Can you share your script?
Hey @eyal1izhaki , sorry for the late reply.
You can find the script I am using here: https://github.com/NicolasWebDev/reinstall-magisk-on-lineageos
If you find any problem or have a suggestion, please tell me!
Oh nice, I tried to run boot_patch.sh on my Ubuntu, didn't go well.. I'll try to run it on my samsung phone as you did.
In not running lineageos but it should be the same process.
Thanks for the script
eyal1izhaki said:
Oh nice, I tried to run boot_patch.sh on my Ubuntu, didn't go well.. I'll try to run it on my samsung phone as you did.
In not running lineageos but it should be the same process.
Thanks for the script
Click to expand...
Click to collapse
https://github.com/Taewan-P/crosshatch-magisk-generator
This is my automation script FYI.
It's mostly close to an automation workflow though...
Also, you should not use the x86 binaries to patch a boot img of an aarch64 device. Flashing the mispatched img will make you boot loop the device.
i have a big dum dum poopy brain i dont know how to do anything will one of you big brain gentlemen please tell me how to patch the boot.img file with the script you guys are talking about and which app do i use and where do i use it and how do i use it. i can't use magisk because it gets stuck on the splash screen with the logo so i'm trying to patch the boot.img file without it. also will it be a problem that the boot.img file has .lz4 at the end (boot.img.lz4). aight thanks im gonna try elongating my neck by tying it to a fan with a rope.
Hi. I am sorry for bumping this thread but I am finding a solution for patching multi-model boot to add Magisk root without a phone.
Will this be possible?
I read the @Sathors script but he pushes the boot file to the android system to patch it. Can this step work on any phone or must on the exact model of the boot.img
Hi @Tungtata . If you look at the boot_patch.sh script in Magisk (https://github.com/topjohnwu/Magisk/blob/master/scripts/boot_patch.sh), in the header it says the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So it seems that to work it needs the corresponding binaries, scripts and files. Maybe you can find all of these files in the Magisk repo, maybe not, in my case it seemed too much hassle to try and find out, knowing that it is working when done on the phone.
But if you really need to do that, then here is a path you can follow.
As for needing the exact phone model to patch the boot image, I don't think so because the script in itself is generic, but it depends on the other files it requires. Anyway, doing a real-life test should be quick.
Hi, sorry but I don't know English well, I was wondering if you could give me the download link of the TWRP for this phone, thanks ......
Redmi Note10 5G EEA
Frankie1975 said:
Hi, sorry but I don't know English well, I was wondering if you could give me the download link of the TWRP for this phone, thanks ......
Redmi Note10 5G EEA
Click to expand...
Click to collapse
Here:
https://forum.xda-developers.com/t/unofficial-twrp-camellia-camellian.4304717/
sorry not run....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Frankie1975 said:
sorry not run....
Click to expand...
Click to collapse
Why install the twrp since there is currently no flashed custom rom and there won't be any soon because of the mediatek soc which is little or not developed.
Have you unlocked the bootloader?
Frankie1975 said:
sorry not run....
Click to expand...
Click to collapse
There is no [recovery] partition on this phone.
yes i unlocked it, how do i recover the partition?
Frankie1975 said:
yes i unlocked it, how do i recover the partition?
Click to expand...
Click to collapse
this is A/B device it doesn't have recovery partition
Frankie1975 said:
yes i unlocked it, how do i recover the partition?
Click to expand...
Click to collapse
Reboot the phone to fastboot (Power + Vol Down)
Connect the phone to the computer using an USB cable (Preferred to use original cable that came with the phone)
Extract the fastboot files and open CMD/Terminal there.
Paste the twrp.img in the same folder.
Type' fastboot boot twrp.img' without the apostrophes.
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP.
But why?(Again).
If it is to change rom version use this tool:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
not running
Frankie1975 said:
not running
View attachment 5609485
Click to expand...
Click to collapse
https://www.droidwin.com/fix-status-read-failed-too-many-links/
changed drivers
changed cable
but it gives me the same two errors as before, even if I only write to the boot partition ....
Frankie1975 said:
changed drivers
changed cable
but it gives me the same two errors as before, even if I only write to the boot partition ....
Click to expand...
Click to collapse
Again why would you want to install the TWRP?
I am Italian and know little English I have no reference guides for your procedure ....
Frankie1975 said:
I am Italian and know little English I have no reference guides for your procedure ....
Click to expand...
Click to collapse
use google trad https://translate.google.fr/?sl=it&tl=en&op=translate
too dangerous .... with the twrp I finished the job, only the magicsk is missing, and I finished the root ..
Frankie1975 said:
too dangerous .... with the twrp I finished the job, only the magicsk is missing, and I finished the root ..
Click to expand...
Click to collapse
No need Twrp to root
and how do you install the magisk?
Frankie1975 said:
and how do you install the magisk?
Click to expand...
Click to collapse
1. Find or redownload the TGZ file for your current ROM
2. Browse inside the zip file and find boot.img under the images folder
3. Copy this file to a temporary location in your PC first, and then transfer it to your phone
4. Install the desired version of Magisk app (V23?)
5. Run the app and choose Install under Magisk
6. Choose Select and Patch a File, then select the boot.img that was transferred earlier
7. A process will run and create a new .img file in the same folder where the original one was
8. Transfer the new file to your PC in the same directory where fastboot.exe is located
9. Open a command prompt window in that same directory
10. Reboot your phone to fastboot mode and connect to PC, USB2.0 port. Check for connection by running command fastboot devices.
11. Run the command fastboot flash boot_ab magiskXXXX.img
Once it's completed, run command fastboot reboot and the phone should boot and be rooted.
thanks for the support, but I have ascertained that I have problems with USB 3.0 I think that's all the problem, I'm very close to the solution, sorry but I leave your guide alone, if I have problems I will opt for your advice. Now I try the "fastboot boot twrp.img" with USB 2.0, then I say hello
Frankie1975 said:
thanks for the support, but I have ascertained that I have problems with USB 3.0 I think that's all the problem, I'm very close to the solution, sorry but I leave your guide alone, if I have problems I will opt for your advice. Now I try the "fastboot boot twrp.img" with USB 2.0, then I say hello
Click to expand...
Click to collapse
Usb 3 is not recommended, I already told you on a previous post.