{
"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"
}
NFO:
This Method does not need Root or Custom Recovery
You must have a Stock Boot Image Dump and you also have to be able to flash the patched Boot Image via Fastboot Mode
Requirements:
• ADB and Fastboot on your PC (for example Tiny ADB & Fastboot) [Thread]
•.Stock boot.img of your Device (extract File from Factory Image)
• Magisk Manager [Thread]
• Internet connection
• Bootloader unlocked [Thread]
• Developer Options > USB Debugging [Thread]
Patching the Stock boot.img:
1. Copy the Stock boot.img to your Phone's internal Storage
2. Install Magisk Manager
3. Launch Magisk Manager App
4. If prompted to install Magisk select "No Thanks"
5. Press Install > Install > Patch Boot Image File and select your Stock boot.img
6. Magisk Manager should begin downloading the Magisk.zip file used for patching
7. Once download is complete Magisk Manager will automatically patch the Boot File
Flashing the patched boot.img:
1. Install Tiny ADB & Fastboot
2. Connect the Phone to the PC via USB Cord
3. Copy the patched_boot.img from your Phone's internal Storage to C:\Program Files (x86)\Tiny ADB and Fastboot\
4. Unlock the Bootloader
5. Enable USB Debugging
6. Open Tiny ADB and Fastboot
7. Boot into Fastboot Mode, type:
Code:
adb reboot bootloader
8. Flash the patched_boot.img, type:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
9. Open Magisk Manager and verify Root
10. Enjoy
K3V1991 said:
NFO:
This Method does not need Root or Custom Recovery
You must have a Stock Boot Image Dump and you also have to be able to flash the patched Boot Image via Fastboot Mode
Requirements:
1. ADB and Fastboot on your PC (for example Minimal ADB and Fastboot) [Thread]
2. Stock boot.img of your Device (extract File from Factory Image)
3. Magisk Manager [Thread]
4. Internet connection
5. Bootloader unlocked [Thread]
6. Developer Options > USB Debugging [Thread]
Patching the Stock boot.img:
1. Copy the Stock boot.img to your Phone's internal Storage
2. Install Magisk Manager
3. Launch Magisk Manager App
4. If prompted to install Magisk select "No Thanks"
5. Press Install > Install > Patch Boot Image File and select your Stock boot.img
6. Magisk Manager should begin downloading the Magisk.zip file used for patching
7. Once download is complete Magisk Manager will automatically patch the Boot File
Flashing the patched boot.img:
1. Install Minimal ADB and Fastboot
2. Connect the Phone to the PC via USB Cord
3. Copy the patched_boot.img from your Phone's internal Storage to C:\Program Files (x86)\Minimal ADB and Fastboot\
4. Unlock the Bootloader
5. Enable USB Debugging
6. Open Minimal ADB and Fastboot
7. Boot into Fastboot Mode, type:
Code:
adb reboot bootloader
7. Flash the patched_boot.img
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
8. Open Magisk Manager and verify Root
9. Enjoy
___
Click to expand...
Click to collapse
I know I can try this method and see what happens and then report back if needed, but I don't think that this is a thing safe enough to test, so I'll ask before I try: is this for any LG G6 version? Does it work on the H870S (Dual SIMs version)?
P.S: I don't think that this version even has the possibility to unlock the bootloader
Also, isn't a phone that has an unlockable bootloader also rootable?
Mohammad Jebreeni said:
I know I can try this method and see what happens and then report back if needed, but I don't think that this is a thing safe enough to test, so I'll ask before I try: is this for any LG G6 version? Does it work on the H870S (Dual SIMs version)?
P.S: I don't think that this version even has the possibility to unlock the bootloader
Also, isn't a phone that has an unlockable bootloader also rootable?
Click to expand...
Click to collapse
Only for H870, H872 & US997
Please file Stock boot.img?
My device: G6 H872 _H87220d
K3V1991 said:
Only for H870, H872 & US997
Click to expand...
Click to collapse
By saying H870, that means any H870 (like one from Central America) or just the same EU H870 that is listed on the LG Developers page?
CAlbertSM said:
By saying H870, that means any H870 (like one from Central America) or just the same EU H870 that is listed on the LG Developers page?
Click to expand...
Click to collapse
The unlockable G6's
Does this wipe the phone?
EndlessAbyss said:
Does this wipe the phone?
Click to expand...
Click to collapse
Fastboot OEM Unlock will Factory Reset the Phone
K3V1991 said:
Only for H870, H872 & US997
Click to expand...
Click to collapse
Will this work on T-Mobile version of LG G6(H872 TM)? Are you sure it will not do any damage to the phone like hard brick?
Imran5320xm said:
Will this work on T-Mobile version of LG G6(H872 TM)? Are you sure it will not do any damage to the phone like hard brick?
Click to expand...
Click to collapse
This does not work on H872 period.
You will get
writing 'boot'...
FAILED (remote: unknown command)
Does this work on the H871?
Hi, i did exactly what you explain in your post on my h870 with V30b-EUR and all worked fine. My phone is now rooted an i'm very happy. Thank you very much for your wonderfull work
leonlelion said:
Hi, i did exactly what you explain in your post on my h870 with V30b-EUR and all worked fine. My phone is now rooted an i'm very happy. Thank you very much for your wonderfull work
Click to expand...
Click to collapse
Could you tell me how did you get the boot.img file? @leonlelion
--Edit--
Nevermind I found it and rooted my device (H870-V30B-EUR) succesfully. If anyone needs it it's inside the ZIP file: https://forum.xda-developers.com/lg-g6/development/rom-lg-h870-eu-30b-rom-t4007979
leonlelion said:
Hi, i did exactly what you explain in your post on my h870 with V30b-EUR and all worked fine. My phone is now rooted an i'm very happy. Thank you very much for your wonderfull work
Click to expand...
Click to collapse
Me too !! :good:
The simplest, best method!
The simplest, best method! The boot.img I got it from this archive: https://drive.google.com/file/d/1Xxoa2KdcoPTPriZL1IZh056J9rQ7NFiV/view?usp=sharing . My phone: H870 with V30b.
Does this work with H872?
I am interested if this will work on my h870s since i am one of the lucky ones who got 'official' bootloader unlock key, and my bootloader is unlocked now. And if it does when i flash this will i be able to safely modify system files.
Thanks a lot! root easy and fast, I used the boot.img file above, fortunately I had an unlocked bootloader
Would anyone know where to find the boot.img for the US997?
Do you have a modem i could just flash with this h873?
Related
The day of the N is upon us!
In typical developer preview tradition since lollipop - I will try and keep this thread up to date with the latest and greatest
Factory Images:
NPC56P
Factory Image Mirror:
https://www.androidfilehost.com/?w=files&flid=51765
To do a dirty flash official factory image files on marshmallow:
- Open flash-all.sh or flash-all.bat in a text editor (depending on which you use)
- Change fastboot -w update image-angler-npc56p.zip to fastboot update image-angler-npc56p.zip
- Run flash-all script
Click to expand...
Click to collapse
Flashables:
Preview 3: http://forum.xda-developers.com/showpost.php?p=66949607&postcount=1423
OTAs:
To sideload OTA via ADB:
On Windows: adb sideload android.zip
On Mac/Linux: ./adb sideload android.zip
Click to expand...
Click to collapse
Google's Preview page: https://developer.android.com/preview/download.html
Google IMG files (manual installation):
Instructions:
A clean install is highly recommended when coming from 5.x.x to "M"
DOES NOT wipe your SD card.
via flashable file:
- Boot into recovery (TWRP/CWM)
- Un-mount /system in TWRP/CWM
- Wipe: system, data, dalvik and cache
- Flash bootloader (optional - only needed if new)
- Flash ROM (be patient - takes a while)
- Flash SuperSU (optional)
- Flash radio (optional - only needed if new)
- Reboot (first boot takes a while)
Click to expand...
Click to collapse
via fastboot (manual installation):
SYSTEM PREP (skip if you already have fastboot/adb setup):
Let's setup ADB and fastboot
Windows:
- Automated: http://forum.xda-developers.com/showthread.php?t=2588979 (follow the steps in the software)
- Manual Method:
Download this file and extract the folder called "adb" to your C: drive. Your path should look like this:
Code:
C:\adb\
You will need to open a command prompt window using this method:
Code:
- Go to the C:\adb\ folder
- hold down SHIFT key and RIGHT-CLICK
- select "Open command window here".
In order to use ADB & Fastboot from anywhere - use the following steps to setup windows environment variables:
Navigate to & click on Start > Right-Click on Computer > click on Advance System Settings >
Click on Environment Variables (under the advanced tab) > Click on New (User Variables) >
Variables Name: ADB (Or anything you want) Variables Value: ;C:\adb (this is the Path of my adb.exe file)
{
"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"
}
Mac & Linux:
Install ADB & fastboot using: this file
1. Extract the downloaded zip to your desktop
2. Open Terminal and type in:
Code:
su
cd Desktop/Android/ (note: Android is the directory extracted from zip file)
3. Now type
Code:
./ADB-Install-Mac.sh
Note: By using the method above, your adb and fastboot files are stored at this location on your Mac: /usr/bin/
----
Now that you're setup, let's do the flashing:
Boot into TWRP to wipe cache, dalvik, data (not internal storage/SD) and system.
Reboot to bootloader and flash the following:
fastboot flash bootloader <insert bootloader img name>
fastboot reboot-bootloader
fastboot flash radio <insert radio img name>
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img // OR // fastboot flash boot <insert name of unecrypt boot.img>
fastboot flash cache cache.img
fastboot reboot
After you finish the above - reboot in to recovery (TWRP/CWM) and factory reset - then reboot
Click to expand...
Click to collapse
-------
FAQ
Disclaimer & Copyrights:
I test everything before I share - thus I know they work as intended. However, please proceed at your own risk as I do not take any liability for your devices.
Please do not copy contents of this guide without explicit permission from me. I like to maintain a set standard and quality of the information I share.
Please refrain from posting mirrors as I like to track downloads - I primarily use AndroidFileHost and they mirror files on multiple servers automatically.
Stay tuned!
that was quick. FIRST
abbz123 said:
that was quick. FIRST
Click to expand...
Click to collapse
as is tradition
Waiting for flashable zip, thanks!
Th3PorTuGa said:
Waiting for flashable zip, thanks!
Click to expand...
Click to collapse
lots of investigation needed first
looks like I'll be flashing this weekend.
btw the first link says "shamu" ?
hmillos said:
looks like I'll be flashing this weekend.
btw the first link says "shamu" ?
Click to expand...
Click to collapse
fixed, it was a typo
@vomer Your link in the OP is for Shamu. It should be Angler.
El Daddy said:
@vomer Your link in the OP is for Shamu. It should be Angler.
Click to expand...
Click to collapse
has been fixed already
If I follow this method, and make a TWRP backup before fastboot flashing everything, is it possible to restore the backup? Also do I loose my photos on the device etc with this method?
Some preview shots showing quick reply & split screen view: http://imgur.com/a/b4O6L
andresantos said:
If I follow this method, and make a TWRP backup before fastboot flashing everything, is it possible to restore the backup? Also do I loose my photos on the device etc with this method?
Click to expand...
Click to collapse
you should be able to restore the full twrp backup - however, do not use the flash all script in this case. Flash the images manually
Wait, is this a preview of N, as in Android 7?
so cool ! Thanks for this
floepie said:
Wait, is this a preview of N, as in Android 7?
Click to expand...
Click to collapse
yes
Btw before anybody ask
New Radio and Bootloader work also with M
vomer said:
you should be able to restore the full twrp backup - however, do not use the flash all script in this case. Flash the images manually
Click to expand...
Click to collapse
Thanks for the info. Which partitions should I backup thenm? Also bootloader and vendor etc? I will prepare for losing everything but most likely I won't be sticking with the version and would save much time if TWRP restore would work accordingly.
Btw, how stable does the preview seem? Does it look like you could possibly use it as a daily driver?
I dirty flashed and it worked so... But hey I know what I'm getting into.
Sent from my Nexus 6P using Tapatalk
Tylog said:
yes
Btw before anybody ask
New Radio and Bootloader work also with M
Click to expand...
Click to collapse
I'd be curious to see if this radio fixes any of the weird LTE/Signal hang issues the 6P has had the past few months..
N Beta Program OTA link: https://android.googleapis.com/pack...aeae3556.signed-signed-angler-ota-2659757.zip
I'm just going to wait for the flashable zip
Hello guys,
{
"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"
}
Lenovo K6 Power k33a42 is a new device released by lenovo on Dec 16, as many of you have bought this phone i would like to share how this phone can be rooted and how we can install twrp on this phone
UNLOCKING BOOT-LOADER :
Unlocking your Android phones bootloader is the first step to rooting and flashing custom ROMs
WARNING: UNLOCKING YOUR BOOTLOADER VOIDS YOUR WARRANTY.PROCEED AT YOUR OWN RISK.
NOTE: Unlocking the bootloader will Wipe/ factory reset your device, and will delete all personal data from your device such as apps, photos, messages, and settings.
INSTRUCTIONS:
1) Download the View attachment K33a42_bootloader_unlock.zip and View attachment drivers.zip zip archive attached here
2) On your device, turn on USB debugging and allow OEMunlocking
if there is no developer options in settings - go to the " Settings -> Device Info " and click on the item " Build number " until the display shows that " you became a developer
go back to the device's main Settings menu and go to Developer options tick "OEM unlocking " and " USB debugging'
when you connect for the first time using debugging via USB you will need to confirm the RSA fingerprint key to trust the PC
3) Extract the Unlock bootloader zip to any directory
4) Connect the device (K33a42) to a PC via USB-cable.
5. Go to the extracted directory and execute Unlock_Bootloader.bat and expect to complete the unlock process.
after the process is completed the boot loader will be unlocked.
INSTALLING TWRP :
1) Extract the folder View attachment TWRP.zip archive to any drive.
2)On your phone, turn on USB debugging (drivers for ADB must be installed).
Connect your phone to a PC via usb-cable
3) You have 2 options either you can try the TWRP (only run one time) or else you can replace the stock recovery with twrp
Use accordingly
run Flash-TWRP.bat (replace stock recovery) or
run Run-TWRP.bat (for one time only).
4) Wait for the phone to boot into TWRP.
You can now disconnect the usb-cord.
Installation is finished.
and also at the starting of the twrp recovery the language will be in Russian because the creator in SevenMaxs from lenovo-forums.ru (I'am looking forward to modify default lang to english)
here is the video which shows how to do so
https://www.youtube.com/watch?v=KOhR92EKD7A
* In the stock firmware Secure Boot is enabled by default , so any changes made to the system partiton lead to a bootloop. Therefore, when you first start TWRP set the system mode to Read Only !
So in order to proceed we need to disable the secure booting in the kernel
Now to disable Secure Boot verification in the boot.img
1. Extract boot.img using twrp backup of boot partition
(you can use android image kitchen for extracting)
2. Make changes in the ramdisk \ default.prop file
change the following line:
ro.secure = 1
to
ro.secure = 0
3. repacked boot.img and flash into the device using twrp.
I know this part may be tough for some uses hence voila i have the secure boot disabled boot image , flash this to boot partition using twrp
ROOTING
Flashing SuperSU zip via TWRP Recovery
Download and transfer the View attachment SuperSU-v2.79-201612051815.zip zip file attached here to your device’s storage.
Boot your device into TWRP recovery.
Tap on Install and select the SuperSU zip file that you transferred to your device in Step 1.
After selecting the .zip file, do Swipe to Confirm Flash on the bottom of screen to begin the flashing process.
Once SuperSU is flashed, you’ll get Reboot System option, select it.
Congratulations! Your device should be rooted now. Look for the SuperSU app in app drawer.
INSTALLING XPOSED
1)Install the xposed installer from playstore
2)Open the installer, and tap the ‘Install/Update’ button. Don’t worry if the app seems stuck here; just give it time and it will eventually show you a Superuser request, which you should make sure to grant and click reboot
Almost all the modules should work on stock rom as it is close to Aosp
modules which i can confirm to work are
: Android N-ify
; Gravitybox
: Bootmanager
:fingers-crossed:
All the credit goes to SevenMaxs
for creating the recovery
and for his guides for proper installation
orginal forum thread
please thank him :fingers-crossed::fingers-crossed:
Thank you
Thankzz.
Sent from my CAM-L21 using Tapatalk
When i try to flash SuperSU-v2.79-201612051815.zip, it says that is corrupt. What can i do ?
Plzz, fix it
Sent from my CAM-L21 using Tapatalk
I found another SuperSU, that worked for me: https://www.androidfilehost.com/?fid=385035244224405790
Thank you again ArjunrambZ and SevenMaxs!
LoverOfLife said:
When i try to flash SuperSU-v2.79-201612051815.zip, it says that is corrupt. What can i do ?
Click to expand...
Click to collapse
i will take a look at the zip, may be upload problem, well any super su zip will work,, this was thw one that i tried
Sent from my VIBE K6 Power using XDA Labs
LoverOfLife said:
Thank you
Click to expand...
Click to collapse
taweng7 said:
Thankzz.
Click to expand...
Click to collapse
taweng7 said:
Plzz, fix it
Click to expand...
Click to collapse
will uplpad today
also the secure boot disabled boot img also
:laugh:
Sent from my VIBE K6 Power using XDA Labs
I'll add adb/fastboot instruction for those who don't use Windows:
Of course you have to enable developer options, adb debug, oem unlocking
UNLOCK:
> adb reboot bootloader
> fastboot oem device-info
> fastboot oem unlock-go
(and... yes you can lock it back with fastboot oem lock)
TWRP:
> fastboot flash recovery /path/to/your/twrp.img
> fastboot oem reboot-recovery
BOOT.IMG:
> fastboot flash boot /path/to/your/ro.secure=0/boot.img
> fastboot reboot
P.S. (to manipulate your boot.img and change the default.prop file under linux you can use abootimg)
ilfastidio said:
I'll add adb/fastboot instruction for those who don't use Windows:
Of course you have to enable developer options, adb debug, oem unlocking
UNLOCK:
> adb reboot bootloader
> fastboot oem device-info
> fastboot oem unlock-go
(and... yes you can lock it back with fastboot oem lock)
TWRP:
> fastboot flash recovery /path/to/your/twrp.img
> fastboot oem reboot-recovery
BOOT.IMG:
> fastboot flash boot /path/to/your/ro.secure=0/boot.img
> fastboot reboot
P.S. (to manipulate your boot.img and change the default.prop file under linux you can use abootimg)
Click to expand...
Click to collapse
you seems to be working on linux, do u have the sources synced on ur pc?
meanwhile i will update the thread to include these to the topic
Sent from my VIBE K6 Power using XDA Labs
ArjunrambZ said:
you seems to be working on linux, do u have the sources synced on ur pc?
meanwhile i will update the thread to include these to the topic
Click to expand...
Click to collapse
I only work on linux. Windows is evil.
I have a big question: why in the default.prop of the russian TWRP.img there is ro.secure=1 ?????
It should be set to 0.
I guess that's why I bricked exactly after flashing Supersu from TWRP...
ilfastidio said:
I only work on linux. Windows is evil.
I have a big question: why in the default.prop of the russian TWRP.img there is ro.secure=1 ?????
It should be set to 0.
I guess that's why I bricked exactly after flashing Supersu from TWRP...
Click to expand...
Click to collapse
as far as i know.. having ro.secure enabled on recovery wont have any effect as we aren't changing anything withrespect to recovery.. but when we change something in system partition with a secure boot enabled kernel we get boot loops
Sent from my VIBE K6 Power using XDA Labs
ArjunrambZ said:
as far as i know.. having ro.secure enabled on recovery wont have any effect as we aren't changing anything withrespect to recovery.. but when we change something in system partition with a secure boot enabled kernel we get boot loops
Click to expand...
Click to collapse
Certainly I'm wrong, but I keep on not understanding. When you are in recovery mode you are loading the kernel inside the recovery and, of course, the default.prop inside the recovery.
That means that you flashed, or are going to flash, a boot.img with ro.secure=0 but running a recovery with ro.secure=1
From recovery you can manipulate system... but with a r0.secure=1 . I don't see a sense in this. But I'm a donkey.
I checked other official releases of twrp, and they all have ro.secure=0 in the default.prop
ilfastidio said:
Certainly I'm wrong, but I keep on not understanding. When you are in recovery mode you are loading the kernel inside the recovery and, of course, the default.prop inside the recovery.
That means that you flashed, or are going to flash, a boot.img with ro.secure=0 but running a recovery with ro.secure=1
From recovery you can manipulate system... but with a r0.secure=1 . I don't see a sense in this. But I'm a donkey.
I checked other official releases of twrp, and they all have ro.secure=0 in the default.prop
Click to expand...
Click to collapse
okay, firstly im also ain't any expert, but i get your point
i dont know why secure boot was enabled in recovery
but when i tried the procedure as explained in the thread i didnt get bootloop ( keeping secure boot in recovery) hence i came to the conclusion that it may not be valid.,, and i may be completely wrong here, if some one could clarify if would be better
Sent from my VIBE K6 Power using XDA Labs
Rooting panasonic eluga note 32GB ROM
Please provide rooting mothod for panasonic eluga note
amnv said:
Please provide rooting mothod for panasonic eluga note
Click to expand...
Click to collapse
sorry i dont have the device
Sent from my VIBE K6 Power using XDA Labs
ArjunrambZ said:
sorry i dont have the device
Sent from my VIBE K6 Power using XDA Labs
Click to expand...
Click to collapse
Its ok brother.. Thanks
My wifi is not working can someone help me? I did this process and after that it's not working
foRgaK said:
My wifi is not working can someone help me? I did this process and after that it's not working
Click to expand...
Click to collapse
i havent experienced this issue
but if u can attach a log file of turning on tbw wifi ,we can help
Sent from my VIBE K6 Power using XDA Labs
I am not responsible if your device gets bricked or gets any other damage.Proceed on your own caution.
This is only for Huawei GR5 mini & P9 lite.
This might not work on EMUI 5.0
If you want to install a custom recovery then follow these steps:
At first you need proper drivers on your device
# Download ADB drivers on your pc and unzip it to any drive:
https://mega.nz/#!pfplUJ5J
#You need to have TWRP recovery file.Link is below:
https://mega.nz/#!tLAUEDqI
#Supersu.zip file :
https://mega.nz/#!BKI3XYQL
You also need to unlock your bootloader to flash a custom recovery image.
-To unlock your bootloader first you need to get your Unlock Bootloader code.So go to:
https://emui.huawei.com/en/plugin.php?id=unlock&mod=unlock&action=apply
-Login with your Huawei ID.If you don't have one then create it.
-Click on Download tab at the top of the screen.You will be redirected to a new window.Select Unlock Bootloader tab below the search tab.
-Agree to the agreement.Provide all the information and copy the bootloader code to a file on your pc.
Unlocking Bootloader
Be aware that after you boot unlock your device it will do a factory reset.So do a backup using HiSuite.You should Know how to do that :good:
-First allow USB debugging mode in developer options.Also allow the device to be OEM unlocked in developer options.
-Go to the adb folder that you downloaded from above link and unzipped .Press shift and right click your mouse.You should see Open command window here option.Select it.Connect your device to the pc
-Type
Code:
adb devices
This should show your device Id.If your device is not detected try installing proper drivers.
-If your device is detected then type
Code:
adb reboot bootloader
This will boot your device to a window with white background and android like logo.
-Type
Code:
fastboot oem unlock 2222222222222222
Here replace 2222222222222222 with your boot unlock code.
-The device will prompt you to abort the process unless you don't want to.Select Unlock bootloader Anyway
Now your device will factory reset itself and you will have your bootloader Unlocked.Now you can flash TWRP recovery
Flash TWRP recovery
-Download and Extract TWRP from the link provided above
-Put TWRP.img file in the adb folder.Connect your device to pc.
-Type
Code:
adb reboot bootloader
This will boot your device in fastboot.
In fastboot,if your device is unlocked it will show phone unlocked FRP unlocked in red letters.
-Now type
Code:
fastboot flash recovery TWRP.img
-
Code:
fastboot reboot-bootloader
Now remove the usb connector from pc and press the power button till your device turns off.Just as it turns off Hold the power button + Vol. Up button at the same time till your device loads bootloader.This will boot your device into TWRP recovery.
Congratulations!!:laugh:
Change your language
Now if the language is in chinese or any other language follow these steps:
-Go to Settings marked by red in the main menu:
{
"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"
}
-Go to Language tab also marked by red:
-Select English
If you want to revert to stock recovery then you can just flash STOCK.img file
Root your device
To root your device you need supersu.zip file
Download it from link provided above.
-Copy the SuperSu.zip file to your sdcard.
-Boot into TWRP. (Power + Vol. Up)
-Select Install.
-Find supersu.zip file and select it.
-Swipe to confirm.
You are now rooted.
If you want to install custom roms,visit these pages:
https://forum.xda-developers.com/huawei-p9lite/development/unofficial-huawei-p9-lite-t3540493/page12#post71806235
https://forum.xda-developers.com/huawei-p9lite/development/6-0-1-aospa-paranoid-android-huawei-p9-t3544790
http://www.meticulus.co.vu/p/downloads_2.html
You know some root method for the GT3 or is the same as the GR5 mini method
Enviado desde mi HUAWEI NMO-L23 usando XDA Forums Pro.
rmoso said:
You know some root method for the GT3 or is the same as the GR5 mini method
Enviado desde mi HUAWEI NMO-L23 usando XDA Forums Pro.
Click to expand...
Click to collapse
Might be same.You can try at your own risk
ashishkafle said:
Might be same.You can try at your own risk
Click to expand...
Click to collapse
key MEGA ? are you kidding me ?
Huawei Gr5 mini, can not install supersu?
ashishkafle said:
I am not responsible if your device gets bricked or gets any other damage.Proceed on your own caution.
This is only for Huawei GR5 mini & P9 lite.
This might not work on EMUI 5.0
If you want to install a custom recovery then follow these steps:
At first you need proper drivers on your device
# Download ADB drivers on your pc and unzip it to any drive:
https://mega.nz/#!pfplUJ5J
#You need to have TWRP recovery file.Link is below:
https://mega.nz/#!tLAUEDqI
#Supersu.zip file :
https://mega.nz/#!BKI3XYQL
You also need to unlock your bootloader to flash a custom recovery image.
-To unlock your bootloader first you need to get your Unlock Bootloader code.So go to:
https://emui.huawei.com/en/plugin.php?id=unlock&mod=unlock&action=apply
-Login with your Huawei ID.If you don't have one then create it.
-Click on Download tab at the top of the screen.You will be redirected to a new window.Select Unlock Bootloader tab below the search tab.
-Agree to the agreement.Provide all the information and copy the bootloader code to a file on your pc.
Unlocking Bootloader
Be aware that after you boot unlock your device it will do a factory reset.So do a backup using HiSuite.You should Know how to do that :good:
-First allow USB debugging mode in developer options.Also allow the device to be OEM unlocked in developer options.
-Go to the adb folder that you downloaded from above link and unzipped .Press shift and right click your mouse.You should see Open command window here option.Select it.Connect your device to the pc
-Type
Code:
adb devices
This should show your device Id.If your device is not detected try installing proper drivers.
-If your device is detected then type
Code:
adb reboot bootloader
This will boot your device to a window with white background and android like logo.
-Type
Code:
fastboot oem unlock 2222222222222222
Here replace 2222222222222222 with your boot unlock code.
-The device will prompt you to abort the process unless you don't want to.Select Unlock bootloader Anyway
Now your device will factory reset itself and you will have your bootloader Unlocked.Now you can flash TWRP recovery
Flash TWRP recovery
-Download and Extract TWRP from the link provided above
-Put TWRP.img file in the adb folder.Connect your device to pc.
-Type
Code:
adb reboot bootloader
This will boot your device in fastboot.
In fastboot,if your device is unlocked it will show phone unlocked FRP unlocked in red letters.
-Now type
Code:
fastboot flash recovery TWRP.img
-
Code:
fastboot reboot-bootloader
Now remove the usb connector from pc and press the power button till your device turns off.Just as it turns off Hold the power button + Vol. Up button at the same time till your device loads bootloader.This will boot your device into TWRP recovery.
Congratulations!!:laugh:
Change your language
Now if the language is in chinese or any other language follow these steps:
-Go to Settings marked by red in the main menu:
-Go to Language tab also marked by red:
-Select English
If you want to revert to stock recovery then you can just flash STOCK.img file
Root your device
To root your device you need supersu.zip file
Download it from link provided above.
-Copy the SuperSu.zip file to your sdcard.
-Boot into TWRP. (Power + Vol. Up)
-Select Install.
-Find supersu.zip file and select it.
-Swipe to confirm.
You are now rooted.
If you want to install custom roms,visit these pages:
https://forum.xda-developers.com/huawei-p9lite/development/unofficial-huawei-p9-lite-t3540493/page12#post71806235
https://forum.xda-developers.com/huawei-p9lite/development/6-0-1-aospa-paranoid-android-huawei-p9-t3544790
http://www.meticulus.co.vu/p/downloads_2.html
Click to expand...
Click to collapse
I have unlock bootloader, completed install twpr, so after instal Supersu, reboot my phone, so Supersu icon dont appear on my screen.
Can you help me?
Whats is the download link decryption key please
steve gats said:
Whats is the download link decryption key please
Click to expand...
Click to collapse
For adb : https://mega.nz/#!pfplUJ5J!DxhLg8Qng3pAn8hdIRW-Afkpe46kC9z5F3daDJO6CDM
For stock recovery image : https://mega.nz/#!5OQF0CjK!-hVldwybHDasBXSx5JdDpXtR1X7weQbo3z0PNW5XtLc
Supersu : https://mega.nz/#!BKI3XYQL!sagih6787ZyJouGQCH0XiCkLopfskkZD88o1YM0OcfM
TWRP : https://mega.nz/#!tLAUEDqI!c6n1GF3aaf0HYshVg_YtUWrk-60z8LcIuX0Vwe-Ajeg
Hoang Hieu said:
I have unlock bootloader, completed install twpr, so after instal Supersu, reboot my phone, so Supersu icon dont appear on my screen.
Can you help me?
Click to expand...
Click to collapse
SuperSu isn't listed in menu list or what? You won't see a superSu logo when the device boots.
ashishkafle said:
For adb : https://mega.nz/#!pfplUJ5J!DxhLg8Qng3pAn8hdIRW-Afkpe46kC9z5F3daDJO6CDM
For stock recovery image : https://mega.nz/#!5OQF0CjK!-hVldwybHDasBXSx5JdDpXtR1X7weQbo3z0PNW5XtLc
Supersu : https://mega.nz/#!BKI3XYQL!sagih6787ZyJouGQCH0XiCkLopfskkZD88o1YM0OcfM
TWRP : https://mega.nz/#!tLAUEDqI!c6n1GF3aaf0HYshVg_YtUWrk-60z8LcIuX0Vwe-Ajeg
Click to expand...
Click to collapse
Can you upload them again please.
Thank you
Solution below.
For those with the same device, I was able to successfully root + pass safetynet, without TWRP or custom recovery. Since this device isn't yet on the forums I thought I should share my findings.
At the time of rooting, I was currently updated to the newest version available (10) and did this through the regular OTA updates.
Preparations
1. Download Magisk Manager Beta from https://magiskmanager.com/magisk-beta/
2. Download the stock firmware for your tablet from https://mirrors.lolinet.com/firmware/lenovo/Yoga_Smart_Tab/YT-X705F/
3. Download kdrag0n's SafetyNet Fix from: https://github.com/kdrag0n/safetynet-fix/releases
Edit: looks like I missed a step, thanks for the feedback! Point 4 has been corrected to include instructions on how to unlock the bootloader specifically.
4. Unlock your bootloader, instructions on how to enable USB debugging which is needed, can be found here: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html, from there you can open your command prompt, navigate to the directory where you have your fastboot and ADB stored, and type "adb devices" to confirm your device is found (a serial number will display on success) - next type "adb reboot bootloader" to force your tablet to restart into it, finally type "fastboot oem unlock-go" to unlock the bootloader. This voids your warranty.
-- end of edit.
5. Enable USB debugging through developer options (go to settings->about->find build # and tap a handful of times until it says you are a developer.
6. Plug the tablet into your PC, and set the default option to Charge only, or go to file transfer mode and enable USB debugging over file transfer.
Steps
1. Unzip the firmware, there should be a folder called Maincode, in it contains "boot.img" as well as adb/fastboot.
2. Copy the boot.img and Magisk apk to the tablet.
3. Install Magisk
4. Tap on "Install" or "Update" beside Magisk in the app and follow the prompts.
5. You will be asked to select a file, select the boot.img you copied earlier.
6. This will generate a file (it will tell you the path) of a patched boot image.
7. Reboot, and copy the patched boot image to the "Maincode" folder from the tablet.
8. In command prompt, type adb devices and make sure your serial number is shown. If not, review the preparations.
9. Type adb reboot bootloader and you'll see a cute little Tux (penguin)
10. Type fastboot devices and ensure your device is shown, if not then it could be bad drivers on your PC or a crappy USB cable. Check device manager on your computer and make sure you see Lenovo ADB. You may have to force it to install it, or you may see a yellow exclaimation mark - right click on the device and force it to install the Lenovo Bootloader option.
11. Next, in the "Maincode" folder where you put the patched image, rename the old "boot.img" to "stock_boot.img" and the patched version to "boot.img"
12. Back in the command prompt, type fastboot flash boot boot.img
13. Reboot by typing fastboot reboot.
Magisk should now be installed, and your tablet should be rooted. Next, you'll want to go into Magisk and do the following:
Steps:
1. Click on the modules button (bottom of the screen, far right option) and at the top you're given an option to install from storage.
2. Navigate to the SafetyNet Fix zip file and select it, then proceed.
3. You will be given the option to reboot - do this. The first time it may go into recovery, but rebooting brings you back to the home screen.
4. Go back to Magisk, click on the gear at the top right - there is an option to hide Magisk from the system, do this and name it whatever you'd like (just not Magisk) - wait a moment, as the app will restart after it installs.
You can check to make sure you pass SafetyNet in the Magisk (now renamed) app, and root status by downloading one of the countless root checking apps on Google Play Store.
Could you let me know a clear way to unlock the bootloader on the Yoga Tab YT-X705F? The instructions you've provided don't point to anything helpful beyond activating USB Debugging.
"4. Unlock your bootloader, instructions: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html - do not proceed beyond where it starts talking about TWRP."
I'm looking to root my tablet but cannot as trying to find info on unlocking the bootloader is proving difficult.
Thanks in advance
Bobmat34 said:
Could you let me know a clear way to unlock the bootloader on the Yoga Tab YT-X705F? The instructions you've provided don't point to anything helpful beyond activating USB Debugging.
"4. Unlock your bootloader, instructions: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html - do not proceed beyond where it starts talking about TWRP."
I'm looking to root my tablet but cannot as trying to find info on unlocking the bootloader is proving difficult.
Thanks in advance
Click to expand...
Click to collapse
Thanks for pointing that out! - I've updated my notes above, but if your familiar with fastboot the command is simply "fastboot oem unlock-go", no unlock code needed for these guys. It will wipe your device and void your warranty though, in case you're not already aware.
Cheers!
Thanks for this rooting guide! I was able to root my YT-X705F
Here some comments/hints:
- At first make sure your downloading the right stock firmware. I've tried a different one which results into a boot loop. One way to find out the right version is to start into the recovery mode. In the header you will find the right version. In my case it was YT-X705F_S001130_210508_ROW
- Make sure you have actually unlocked the boot loader. "fastboot flash x y.img" worked, so I didn't recognized that the boot loader was not unlocked. This was reason for "fastboot boot y.img" shows errors "FAILED (status read failed (Too many links))".
- The extracted stock firmware have no "Mainfolder". All files, including boot.img and recovery.img, contained in the root directory of the ZIP file.
- After installing Magisk app (v23.0) it shows me: Installed: N/A, Ramdisk: No, A/B: No, SAR: Yes. According to this Magisk installation guide you have to patch the recovery image instead of the boot.
{
"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"
}
- Patching the recovery image was fine with Magisk. No errors was shown. Please note I used the recovery.img
After this I was able to boot the patched image without flashing it:
After "fastboot boot patched_recovery.img" nothing happens. The tablet keeps showing me the Linux Tux image. I have to disconnect the USB cable and then I booted into system.
*Upd. never mind, I download the official rom file from lenovo\
Crap. I patched the boot image with Magisk, and by the time I flashed it - the system got updated from S001133 to S001135, and I'm getting a bootloop. Can someone maybe upload original boot img from S001135?
Or what else can I do? the update isn't on the mirror server yet https://mirrors.lolinet.com/firmware/lenovo/Yoga_Smart_Tab/YT-X705F/
Rooting was successful! Thanks for the guide. Since I cannot find any section in the forum for the YT-x705 tablet, I thought I can have a follow up question in here. The reason I rooted was because alexa app keeps getting removed after each reboot. I rooted as I wanted to convert it into a system app.
So far, I've been unsuccessful . I have tried with the systemizer module and titanium backup. Anyone have any idea how we can retain alexa app after a reboot? Interestingly enough, titanium backup shows alexa as frozen after I install alexa from playstore, despite it appearing in my app launcher. I am unable to unfreeze it. Alexa is then removed after I reboot.
Quick question: What do i do if i don't have a "MainCode" folder, on the tablet or in the extracted folder.
or is that just the folder with the maincode, in it?
Thanks, looks like a good guide!
Jim
you're just going into the zip file from step 2 where the boot.img file is. I just followed all these instructions and got my yoga rooted.
ugh...I don't have a device that I can root for a couple of years... and it feels like I'm a complete noob, now!
when i try to flash the boot image I'm getting: FAILED (remote: Partition flashing is not allowed)
When i run fastboot oem device-info i get this:
PS C:\Users\Jim\Downloads\YT-X705F_S001135_210909_ROW (1)> ./fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.007s]
Finished. Total time: 0.010s
So i don't think i am unlocked. even after following the steps. I've got Developer options, Debugging is obviously working, OEM Unlocking is toggled on.
I feel like on my phones we had to run an adb or fastboot command, and then the device would reboot and reset it and it would then be unlocked.
Am i missing something?
Thanks again!!
Jim
p.s. and once i get it working, what roms can i flash? any of the "yoga" roms? or do i need to look at something specific like the 3 or 4?
answered my own question!
i had to run: fastboot oem unlock-go
the device rebooted and reset
now i get this:
PS C:\Users\Jim\Downloads\YT-X705F_S001135_210909_ROW (1)> ./fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.007s]
Now on to the next step!
So anyone know what ROMs i should use and how best to install them, i don't think we have a working TWRP, do we?
... after crash of my booting Android 10 system last stock rom my yt-x705F 210909 can't be rooted anymore!
i use some app and this app ask for busybox .... so crash !!!
i reset tablet by system recovery .
"wipe data/ factory reset"
after restart my tablet is working again.
Bootloader is still open
also develover mode is working USB Debugging etc.
but no rooting alowed by patching root img .. see next
now i try to install stock rom NEW but some error
"apply update from external storage " get error
same is from "Apply update from ADB" abd sideload file.img
are this zip files from this server corrupt? mirros lolinet ?
i use magisk 25.2 i try all option with hook on recovery also vbmeta
patch both boot.img and recovery.img
after patch one of these img device runs into the bootloader , tux start up.
if i patch stock boot.img device booting normal but NO ROOT
also twrp can't no flash only option "fastboot boot twrp.img"
"fastboot boot flash recovery twrp.img" not working
if i use twrp by "fastboot boot twrp.img" zip stockrom makes also error
someone knows about RESCUE and SMART ASSISTENT" LMSA Tool ?
any suggestion
how is this working ?
go on settings > about tablet > push a view times on Hardware-Version
NEW Firmware update YT_X705F_S001137_220721_ROW for yoga
what's new?
looserintheend said:
NEW Firmware update YT_X705F_S001137_220721_ROW for yoga
what's new?
Click to expand...
Click to collapse
Know where can I find this firmware?
Hi all,
At my work we are using an android tablet and I need to install root on it. The tablet is a SkyDroid H16. The weird thing is that "adb root" works fine and I can remount /system and add files, but apps cannot see that there is root.
How can I install su and use it.
There is no TWRP for it and the stock image is also not public.
Senna-chan said:
Hi all,
At my work we are using an android tablet and I need to install root on it. The tablet is a SkyDroid H16. The weird thing is that "adb root" works fine and I can remount /system and add files, but apps cannot see that there is root.
How can I install su and use it.
There is no TWRP for it and the stock image is also not public.
Click to expand...
Click to collapse
Root Android Devices without TWRP RecoveryTo root your device without TWRP Recovery, you need to perform two steps. Firstly, the device needs to be booted using the patched boot image file. In the next step, this boot image file will be permanently flashed using the Magisk Manager app. Don’t forget to have a look at the ‘Prerequisites’ section below, before beginning with the process. Droidwin and its members wouldn’t be held responsible in case of a thermonuclear war, your alarm doesn’t wake you up, or if anything happens to your device and data by performing the below steps.
Prerequisites
Download and install the Magisk Manager APK file on your device: Magisk App [from version 22 onwards, it is known as Magisk App and has both the Magisk ZIP and Manager APK file bundled together].
Next up, check if your device has ramdisk or not. For that, launch the Magisk app and refer to the section under Magisk, if it says YES, then you are good to proceed ahead (see below image). On the other hand, if it says NO, then you will have to head over to our alternative guide: Install Magisk in Recovery and Root Android [No Ramdisk].
{
"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"
}
The bootloader of your device should be unlocked. Have a look at our guide on how to do so.
Enable the ‘USB Debugging’ option. Go to ‘Settings’ -> ‘About Phone -> Tap on Build Number 7 times -> Go back to Settings -> Developer Options -> Toggle on the USB Debugging’ switch.
Although rooting is going to wipe your data, still, it is recommended to make a complete backup of all your data.
Keep your device appropriately charged, at least to a minimum recommended level of 50%
Install ADB and Fastboot Tool for entering Fastboot commands.
Also, download and install the USB Drivers for your device. This helps in successfully connecting your device to the PC.
STEP 1: Get Stock Boot.img File from Stock ROM
To begin with, you will have to extract the stock boot.img file. And as opposed to earlier times, the process is a little bit more complicated nowadays. You cannot simply extract the firmware and get the required partition files (such as vbmeta.img, system.img, boot.img, etc). The reason is that many OEMs packs the ROM’s IMG files inside an encrypted package. For example, OnePlus has these files inside payload.bin, Realme, and Oppo have their files inside the OZIP format, and so on. In that case, you may refer to our below guides to get the stock boot.img file:
Now that you have got hold of the stock boot image file, it’s time to patch it via Magisk and flash it via Fastboot Commands. We have listed the steps for both the older as well as the newer build of Magisk Manager. As far as the difference between them goes, it’s just some UI tweaks here and there, the underlying functionality remains the same. The below update is only for devices running Android 11. If your device isn’t running that version, then you may directly head on to STEP 2A/2B.
UPDATE 1 [FOR ANDROID 11 USERS ONLY]: Quite a few Android 11 users are facing issues while patching the stock boot.img file via Magisk manager. Well, I have found the fix to this issue, please refer to our detailed guide on the same: Fix Magisk patched boot.img issue while Rooting Android 11. If you wish to save a click, then here’s the explanation in short:
You have to install the Magisk Canary build instead of the stable and then change the update channel to Canary from within the app itself. Once you have done the said change, you may then proceed with the below steps to patch the stock boot image file using Magisk and flash it via Fastboot commands. [END OF UPDATE 1]
STEP 2A- Patch the Stock Boot Image File using Older Magisk
Download the stock firmware for your device.
Extract the boot.img file from it.
Transfer it to the device’s internal storage.
Install the Magisk Manager App on your device.
Open it. Tap on the first ‘Install‘ button, next to Magisk status.
In the next menu, again chose ‘Install‘.
Now select ‘Select and Patch a File‘.
Navigate to internal storage and select the stock boot.img file that you extracted earlier.
Let Magisk do the patching process. When it’s done, copy this patched boot.img file, named as magisk_patched.img, from your device (will be present under Internal Storage > Downloads) to PC where you have installed the ADB and Fastboot Tools (inside the platform-tools folder).
How to Update Magisk ZIP and Magisk Manager (without TWRP)
Disable DM-Verity or Android Verified Boot without TWRP
Fix Magisk Module Bootloop without TWRP Recovery
How to Root Android Devices Without TWRP Recovery
STEP 2B: Patch Stock Boot Image File using Newer Magisk
Launch the Magisk Manager app on your Pixel device.
Then tap on the Install button situated next to Magisk.
From the Method section, choose Select and Patch a file.
Browse to the extracted boot.img file and select it.
Then tap on the Let’s Go option situated at the top right.
Magisk will now load the boot.img file and will patch it accordingly. Once that is done, you would get the Download Complete message.
The patched boot image file will be saved in Internal Storage > Downloads. The name of the file will be magisk_patched.img.
Now that you have patched the stock boot.img file, it’s time to flash it onto your device and hence obtain root without TWRP. There are two different methods through which you could do this. This patched boot.img file could either be flashed via Fastboot or through Magisk. It is highly recommended that you proceed with the Fastboot Method. Only in case, if you face any issues, then you should proceed with the Magisk Method. The reason being the fact via the Magisk method, we will be using the DIrect Install feature, which seems to be absent in most devices. Hence to avoid any confusion, you should try the Fastboot Method. If you face any error, then only proceed with the Magisk method to root your Android device without TWRP.
STEP 3A- Install the Patched Boot Image using Fastboot
Connect the device to the PC via USB Cable.
Now transfer the patched boot file from your device to the platform-tools folder on your PC.
Inside the same folder, right-click on an empty area while pressing the ‘Shift’ key.
Select the option ‘Open PowerShell window here’.
Or you could also head over to the platform-tools folder on your PC, type in CMD in the address bar, and hit Enter. This will launch the Command Prompt.
Type in the below code to make sure the device is successfully connected (an alpha-numeric code suggests successful connection):adb devices
Now type in the below code to boot your device to fastboot/bootloader mode:adb reboot bootloader
Next, type the below code to flash the patched boot image file:fastboot flash boot magisk_patched.img
If you get the fastboot: error: Couldn’t parse partition size ‘0x’ issue, as some users have mentioned in the comments, then please refer to our detailed guide: How to Fix fastboot: error: Couldn’t parse partition size ‘0x’.
For devices with an A/B partition, you need to flash the patched boot file to both partitions. Type the below code for the same:fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Now you may Reboot the device by typing the below code:fastboot reboot
If your device is rooted, then you should stop here only. However, if the Fastboot Command method didn’t work out in your case, then only proceed with the next method to install patched boot.img.
If this post is good please thumbs up.
@Senna-chan
Because adb root & adb remount works here is a code example that adds su
Code:
adb root & adb remount & adb disable-verify & adb shell "setenforce 0"
adb push su /system/bin/
adb push superuser.apk /system/app/
adb reboot
jwoegerbauer said:
@Senna-chan
Because adb root & adb remount works here is a code example that adds su
Code:
adb root & adb remount & adb disable-verify & adb shell "setenforce 0"
adb push su /system/bin/
adb push superuser.apk /system/app/
adb reboot
Click to expand...
Click to collapse
So I tried this with a few version of supersu but it didn't work. I tried version 2.76 2.82 and 2.79 and it didn't work. Everytime I get the error no su binary found. The version I uploaded was the arm64 version since I have a ARMv8.
What could be wrong?
Thats great in all but after I flash the boot.img from any version of magisk from v22 onward and the latest canary, it doesn't give me magisk app when i boot back into the os.