Someone has already rooted the device
I tried to download all the files it mentioned .
but still I was stuck by the TWRP flashing process
because this device is using A/B partition way not same as the other android devices.
:cyclops: **** i cant send the website link
happywhd said:
Someone has already rooted the device
I tried to download all the files it mentioned .
but still I was stuck by the TWRP flashing process
because this device is using A/B partition way not same as the other android devices.
:cyclops: **** i cant send the website link
Click to expand...
Click to collapse
I am not aware of a TWRP compiled for our device yet that you can flash. If you are interested in doing it follow this guide: https://forum.xda-developers.com/showthread.php?t=1943625
happywhd said:
Someone has already rooted the device
I tried to download all the files it mentioned .
but still I was stuck by the TWRP flashing process
because this device is using A/B partition way not same as the other android devices.
:cyclops: **** i cant send the website link
Click to expand...
Click to collapse
fastboot flash boot xxxx.img
worked for me.
Max4D said:
fastboot flash boot xxxx.img
worked for me.
Click to expand...
Click to collapse
where did you get the img file?
Marco589 said:
where did you get the img file?
Click to expand...
Click to collapse
Asus forums
sorry i can't post links yet
Shakalaca has uploaded TWRP images to Mega
https(colonslashslash)wwwv(dot)asus(dot)com(slash)zentalk(slash)tw(slash)thread-362963-1-1(dot)html
https(colonslashslash)mega(dot)nz(slash)#F!pst3URCQ!l_N503AsNmytaErhmuiwqg
Max4D said:
Asus forums
sorry i can't post links yet
Shakalaca has uploaded TWRP images to Mega
https(colonslashslash)wwwv(dot)asus(dot)com(slash)zentalk(slash)tw(slash)thread-362963-1-1(dot)html
https(colonslashslash)mega(dot)nz(slash)#F!pst3URCQ!l_N503AsNmytaErhmuiwqg
Click to expand...
Click to collapse
TWRP
https://mega.nz/#F!pst3URCQ!l_N503AsNmytaErhmuiwqg
I think Magisk causes bootloop. I believe there is a modded version, but I don't have a link.
Edit: I found post about Magisk - https://forum.xda-developers.com/showpost.php?p=78003101&postcount=14
Tesla74 said:
TWRP
I think Magisk causes bootloop. I believe there is a modded version, but I don't have a link.
Click to expand...
Click to collapse
You can download the modded version from Shakalaca's custom Magisk channel
ＨＴＴＰＳ://bit.ly/2NGVKqS
Max4D said:
You can download the modded version from Shakalaca's custom Magisk channel
ＨＴＴＰＳ://bit.ly/2NGVKqS
Click to expand...
Click to collapse
https://bit.ly/2NGVKqS
Thanks
If anyone is looking for fastboot:
https://devsjournal.com/download-minimal-adb-fastboot-tool.html
Max4D said:
fastboot flash boot xxxx.img
worked for me.
Click to expand...
Click to collapse
Ballanda can't get fastboot to work: https://forum.xda-developers.com/rog-phone/how-to/rog-phone-recognized-pc-fastboot-mode-t3860453
Tesla74 said:
Ballanda can't get fastboot to work: https://forum.xda-developers.com/rog-phone/how-to/rog-phone-recognized-pc-fastboot-mode-t3860453
Click to expand...
Click to collapse
I didn't install any drivers manually.
Just connected my phone to a Win 10 PC.
As for fastboot I just used my usual environment.
Has been a while so unfortunately I don't remember precisely, but I think I got it from Android SDK.
I've used the same environment to root my Zenfone 3 Deluxe before, if that makes any difference.
P.S.
Rashad83 says it doesn't return devices but can execute the command.
I've flashed TWRP but didn't use the fastboot devices command(I could try when I get home) so that might be the case.
Max4D said:
You can download the modded version from Shakalaca's custom Magisk channel
ＨＴＴＰＳ://bit.ly/2NGVKqS
Click to expand...
Click to collapse
Can you explain what to do with the json file?
Marco589 said:
Can you explain what to do with the json file?
Click to expand...
Click to collapse
The URL is for the Magisk channel
Install Normal Magisk Manager apk.
Set channel to custom, type in the URL.
Download Custom Magisk Manager.
Uninstall Normal Manager
Install custom Manager.
DL(from the channel)&install custom Magisk directly with Manager.
Max4D said:
The URL is for the Magisk channel
Install Normal Magisk Manager apk.
Set channel to custom, type in the URL.
Download Custom Magisk Manager.
Uninstall Normal Manager
Install custom Manager.
DL(from the channel)&install custom Magisk directly with Manager.
Click to expand...
Click to collapse
Thanks a lot!
All in all to root the phone:
Unlock bootloader
Flash twrp
And install magisk as you said
Right?
Marco589 said:
Thanks a lot!
All in all to root the phone:
Unlock bootloader
Flash twrp
And install magisk as you said
Right?
Click to expand...
Click to collapse
That's right.
Although in hindsight,twrp might not be necessary if u just want root, but I did it in that order.
(Was thinking of posting a guide, but since I can't post direct links yet, hopefully someone who can would
I tried 3 different cables on 8 different USB ports on 3 different Windows 10 machines, and I cannot get the phone to flash TWRP. I tried FASTBOOT DEVICES and nothing comes up. Regardless, I still tried to FASTBOOT FLASH RECOVERY TWRP.IMG, and all I get is <waiting for device>. All my other phones work fine, and I do have all of the necessary drivers installed.
Is there a way I can sideload or flash Magisk via ADB, since I can use that? I can live without TWRP.
Max4D said:
That's right.
Although in hindsight,twrp might not be necessary if u just want root, but I did it in that order.
(Was thinking of posting a guide, but since I can't post direct links yet, hopefully someone who can would
Click to expand...
Click to collapse
Great!
As soon as I receive my rog (as It got lost just right after the shipping) , I'll do It ?
I hope you guys having fastboot issues are using the official Android Studio and not the minimal adb or any other version.
Max4D said:
The URL is for the Magisk channel
Install Normal Magisk Manager apk.
Set channel to custom, type in the URL.
Download Custom Magisk Manager.
Uninstall Normal Manager
Install custom Manager.
DL(from the channel)&install custom Magisk directly with Manager.
Click to expand...
Click to collapse
Here is a direct link to the custom Magisk Manager to save a few steps:
https://www.dropbox.com/s/c8fm2ka60cmlvi6/MagiskManager-6.0.2-20181010.apk?dl=1
---------- Post added at 05:30 PM ---------- Previous post was at 05:25 PM ----------
kgptzac said:
I hope you guys having fastboot issues are using the official Android Studio and not the minimal adb or any other version.
Click to expand...
Click to collapse
https://developer.android.com/studio/
kgptzac said:
I hope you guys having fastboot issues are using the official Android Studio and not the minimal adb or any other version.
Click to expand...
Click to collapse
I tried Minimal ADB and Fastboot. ADB connects fine, Fastboot does not.
I tried the Android platform tools version of ADB and Fastboot. I 'm pretty sure that is the same thing that installs with Android Studio. ADB connects fine, Fastboot does not.
Just for fun, I did the 2 GB download and tried the full blown Android Studio version of ADB and Fastboot. Strike three.
So, same results no matter what I do. I can interact through ADB, but not Fastboot on the ROG phone. When I try to issue a Fastboot command while the phone is in Fastboot mode, all I get is "Waiting for any device".
It's never been this hard with any of the 6 devices I've owned and rooted. I am wondering if I should flash the stock firmware and start over. So far all I've done is unlock the bootloader using the ASUS unlock tool APK.
ballanda said:
I tried Minimal ADB and Fastboot. ADB connects fine, Fastboot does not.
I tried the Android platform tools version of ADB and Fastboot. I 'm pretty sure that is the same thing that installs with Android Studio. ADB connects fine, Fastboot does not.
Just for fun, I did the 2 GB download and tried the full blown Android Studio version of ADB and Fastboot. Strike three.
So, same results no matter what I do. I can interact through ADB, but not Fastboot on the ROG phone. When I try to issue a Fastboot command while the phone is in Fastboot mode, all I get is "Waiting for any device".
It's never been this hard with any of the 6 devices I've owned and rooted. I am wondering if I should flash the stock firmware and start over. So far all I've done is unlock the bootloader using the ASUS unlock tool APK.
Click to expand...
Click to collapse
What region is your phone? Maybe some region roms have fastboot disabled?
Related
While I tried to root using TWRP and all the suggested ways i continued to get errors, bootloops, corrupted boot, etc. I downloaded the rooted developers OS Image, then used magisk to patch the boot image. If anyone has any interest in the Boot.img or the developers OS image, let me know i can post links and instructions if needed. This will require the bootloader unlocked (i have read you can unlock with a keyboard, but i never had any luck and used a controller). Please reply with requests if needed.
Just one question: When you install the NEXT developer image, how will you go about retaining Magisk and your boot.img patch? Don't need a step-by-step-- just in simple terms. Curious.
EDIT: Found my answer: https://forum.xda-developers.com/showpost.php?p=77162700&postcount=85
I have a question i dont want create a thread for this so with root its possible to use 2 usb drive ?because for only the one right on the HDMI cable Work
laharl_22 said:
I have a question i dont want create a thread for this so with root its possible to use 2 usb drive ?because for only the one right on the HDMI cable Work
Click to expand...
Click to collapse
I'm not sure, but i think its possible to use 2 USB drives now if you turn off adb debugging or use a hub.
Michajin said:
I'm not sure, but i think its possible to use 2 USB drives now if you turn off adb debugging or use a hub.
Click to expand...
Click to collapse
Thanks it work
This is really good, thanks, so i can use flash this 7.0.2 boot.img on top of the latest "nv-recovery-image-shield-atv-7.1.0-dev_rooted" without any issues?
@Michajin Can you please share your boot.img that is patched with magisk?
samjoandco said:
This is really good, thanks, so i can use flash this 7.0.2 boot.img on top of the latest "nv-recovery-image-shield-atv-7.1.0-dev_rooted" without any issues?
@Michajin Can you please share your boot.img that is patched with magisk?
Click to expand...
Click to collapse
What version are you on? I downloaded the full zip, put the unzipped file on a USB from a computer. Then Took the USB to my Shield ran magisk manager 6.0 and installed, selecting patch boot, selecting the file from the USB. Magisk places the patched boot into my download folder where i pulled back onto my computer the fastboot flash boot boot.img (or patched_boot.img whatever the file is called that got patched).
I have the patched 7.1 boot.img right now. I have the full developers files, with drivers and patch all in it for 7.1 with magisk manager if you want i can put it on my Google drive for the whole thing. It is 1.09 Gb for the full files.
samjoandco said:
This is really good, thanks, so i can use flash this 7.0.2 boot.img on top of the latest "nv-recovery-image-shield-atv-7.1.0-dev_rooted" without any issues?
@Michajin Can you please share your boot.img that is patched with magisk?
Click to expand...
Click to collapse
Guess i Didn't read very well! Here is the Boot.img for magisk 7.1.
fastboot flash boot boot.img
Use 7-zip to unzip, had to make it a tar to upload here (12mbs)
How to fix a bootloader who not boot ? I have only bootloader IS unlocked warning screen and NVIDIA logo but no os and unable to boot bootloader or twrp
laharl_22 said:
How to fix a bootloader who not boot ? I have only bootloader IS unlocked warning screen and NVIDIA logo but no os and unable to boot bootloader or twrp
Click to expand...
Click to collapse
I am assuming you have a nvidia shield 2017
Download the full image from nvidia here
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20TV%202017%20Developer&tx=$additional,shield
Connect via fastboot (plug in controller press A - B and power on)
From fastboot connect with a computer via A-A usb cable
unzip the file from nvidia into the folder where your fastboot drivers are
run the flash-all.bat file
Michajin said:
Guess i Didn't read very well! Here is the Boot.img for magisk 7.1.
fastboot flash boot boot.img
Use 7-zip to unzip, had to make it a tar to upload here (12mbs)
Click to expand...
Click to collapse
Thanks Michajin, much appreciated, I will try it on the weekend! :highfive::good:
One question:
I am on the latest 7.1.0 but not on developer image, can i just unlock the bootloader and flash the boot image to get root ?
or i need to installed the developer version (nv-recovery-image-shield-atv-7.1.0-dev_rooted)?
I dont want to install everything again.
samjoandco said:
Thanks Michajin, much appreciated, I will try it on the weekend! :highfive::good:
One question:
I am on the latest 7.1.0 but not on developer image, can i just unlock the bootloader and flash the boot image to get root ?
or i need to installed the developer version (nv-recovery-image-shield-atv-7.1.0-dev_rooted)?
I dont want to install everything again.
Click to expand...
Click to collapse
As far as i know Unlocking erases data anyways. You unlock you have to reinstall everything anyways.
The boot image works only on developer image? Thanks
gas80 said:
The boot image works only on developer image? Thanks
Click to expand...
Click to collapse
I don't know what the differences are between the dev image and the regular version. I believe the dev version is just pre-rooted. I think it will work, but i have only tested on the dev image. Flash at your own risk.
Hi there,
I need help. Im looking for a ROM thats flashable with TWRP so i can install it. Previously I had Lineageos installed but it wasnt running smooth enough.
I cant install the rooted recovery file from Nvidia with TWRP.
The reason why im wanting to use TWRP is because i want to use Magisk with the Shield.
Ive allready patched a stock boot image with magisk version 17.1
my current Twrp version is 3.2.1-1
Thank you very much
cheers
[Edit]
I solved the problem by following this post
thanks
Michajin said:
What version are you on? I downloaded the full zip, put the unzipped file on a USB from a computer. Then Took the USB to my Shield ran magisk manager 6.0 and installed, selecting patch boot, selecting the file from the USB. Magisk places the patched boot into my download folder where i pulled back onto my computer the fastboot flash boot boot.img (or patched_boot.img whatever the file is called that got patched).
I have the patched 7.1 boot.img right now. I have the full developers files, with drivers and patch all in it for 7.1 with magisk manager if you want i can put it on my Google drive for the whole thing. It is 1.09 Gb for the full files.
Click to expand...
Click to collapse
Could you please upload it on google drive. That would be greatly appreciated. :good:
gambaaa said:
Could you please upload it on google drive. That would be greatly appreciated. :good:
Click to expand...
Click to collapse
I dont know if it sent, here is a link for the dev image with magisk installed on the boot.img. The original and patched boot.img are in the zip file., along with the magisk app.
Please flash at you own risk, i have the 2017 shield and it worked for me. I ran the flash-all.bat.
Here is a link to the file on my GDrive ( I will be blocking access after the weekend)
Goodluck,
Michajin
Michajin said:
I dont know if it sent, here is a link for the dev image with magisk installed on the boot.img. The original and patched boot.img are in the zip file., along with the magisk app.
Please flash at you own risk, i have the 2017 shield and it worked for me. I ran the flash-all.bat.
Here is a link to the file on my GDrive ( I will be blocking access after the weekend)
https://drive.google.com/open?id=15sJ6YFmwiAZX0mXQk_ANq5Nfvs9E8oJF
Goodluck,
Michajin
Click to expand...
Click to collapse
Great job! I will try it this week-end. So I just plug my nvidia shield via usb and run the flash-all.bat ? Also, do I need to unlock my bootloader before doing anything. I have stock 8.0 oreo
gambaaa said:
Great job! I will try it this week-end. So I just plug my nvidia shield via usb and run the flash-all.bat ? Also, do I need to unlock my bootloader before doing anything. I have stock 8.0 oreo
Click to expand...
Click to collapse
Yes, as far as i know you have to have an unlocked bootloader. You plug in your Sheild VIA a-a USB, you might have to install the sheild drivers. Press AB on your controller and power on. That will get you into fastboot. You have to run the unlock bootloader command WARNING this will wipe your DATA. All the drivers you need will be on this page available to download https://developer.nvidia.com/shield-open-source and for instructions on how-to goto here http://nv-tegra.nvidia.com/gitweb/?...;f=README_NEW_SHIELD;hb=rel-24-uda-r1-partner (the instructions tell how to do flash each file, i found it faster to do the flash-all.bat, but be patient, i think it takes about 30 minutes)
Michajin said:
Yes, as far as i know you have to have an unlocked bootloader. You plug in your Sheild VIA a-a USB, you might have to install the sheild drivers. Press AB on your controller and power on. That will get you into fastboot. You have to run the unlock bootloader command WARNING this will wipe your DATA. All the drivers you need will be on this page available to download https://developer.nvidia.com/shield-open-source and for instructions on how-to goto here http://nv-tegra.nvidia.com/gitweb/?...;f=README_NEW_SHIELD;hb=rel-24-uda-r1-partner (the instructions tell how to do flash each file, i found it faster to do the flash-all.bat, but be patient, i think it takes about 30 minutes)
Click to expand...
Click to collapse
Wonderful! Thanks for the explanation!
Has anyone here rooted this tablet with Magisk?
Any very detailed step by step guide somewhere with links to the specific files to download for this tablet? (It'd be great if it didnt't require a PC but even if it does, I'd really appreciate a detailed step by step guide to put Magisk on this tablet)
Thanks
Try this
Planet Indigo said:
Has anyone here rooted this tablet with Magisk?
Any very detailed step by step guide somewhere with links to the specific files to download for this tablet? (It'd be great if it didnt't require a PC but even if it does, I'd really appreciate a detailed step by step guide to put Magisk on this tablet)
Thanks
Click to expand...
Click to collapse
Hi there,
I wouldnt't use Magisk on your device as it might softbrick your drive
So use KINGOROOT.
THE STEPS ARE VERY EASY TO FOLLOW.
https://www.kingoapp.com/
Regards,
KIBS2173
KIBS2173 said:
Hi there,
I wouldnt't use Magisk on your device as it might softbrick your drive
So use KINGOROOT.
THE STEPS ARE VERY EASY TO FOLLOW.
https://www.kingoapp.com/
Regards,
KIBS2173
Click to expand...
Click to collapse
Why would Magisk be more risky than Kingoroot on this device? I liked the idea of Magisk because it is systemless root and it is easier to hide from some apps.
Can Kingoroot one click root apk even root a Teclast M16 running android 8?
For M16, there is no root at all yet. I look forward to it myself, but so far there is nothing ....
Planet Indigo said:
Why would Magisk be more risky than Kingoroot on this device? I liked the idea of Magisk because it is systemless root and it is easier to hide from some apps.
Can Kingoroot one click root apk even root a Teclast M16 running android 8?
Click to expand...
Click to collapse
Hi there,
I tried Magisk on a chinese phone, and after flashing the software, the phone just went into black screen and soft-bricking the whole phone, the phone works in the background but the screen is black. And KINGOROOT will not flash anything into your device.
Regards
KIBS2173
Karamarov1 said:
For M16, there is no root at all yet. I look forward to it myself, but so far there is nothing ....
Click to expand...
Click to collapse
So you have the tablet yourself and no luck with anything?
I can't seem to find anything on the net about rooting this tablet, it's weird too since it "only" has android 8, not the latest android versions. I sure hope Magisk or another root method is going to be developed soon because I'm really interested in that tablet model.
KIBS2173 said:
Hi there,
I tried Magisk on a chinese phone, and after flashing the software, the phone just went into black screen and soft-bricking the whole phone, the phone works in the background but the screen is black. And KINGOROOT will not flash anything into your device.
Regards
KIBS2173
Click to expand...
Click to collapse
I heard from another forum user who has the Teclast M16 and he said that Kingoroot didn't work on it.
Try this
Planet Indigo said:
So you have the tablet yourself and no luck with anything?
I can't seem to find anything on the net about rooting this tablet, it's weird too since it "only" has android 8, not the latest android versions. I sure hope Magisk or another root method is going to be developed soon because I'm really interested in that tablet model.
I heard from another forum user who has the Teclast M16 and he said that Kingoroot didn't work on it.
Click to expand...
Click to collapse
Hi there,
So i was researching more about this tablet, turns out you can root by installing a custom recovery (TWRP) and from there you can install SUPERSU to achieve root for your tablet. I am not sure if this method works, but if your able to get the stock firmware and the stock recovery and the software to flash the firmware i think you might as well go ahead using that method.
THIS IS THE ARTICLE I FOUND ONLINE :
https://www.getdroidtips.com/how-to-install-twrp-recovery-on-teclast-t30-and-root-it-easily/
*MAKE SURE YOU FIND OUT IF THIS TABLET HAS A TWRP RECOVERY BEFORE DOING ANYTHING ELSE*
Thank you for looking into it, unfortunately that guide is for the Teclast T30 and the guy advises to only use it for that model. I don't own that tablet yet so I can't try any of the steps myself but I'm very interested in this particular model (16/9 ratio, hdmi out, dc charger in, etc...) so I was really hoping to find a tested working method to root it before I go ahead and purchase it.
i found this: https://www.getdroidtips.com/root-teclast-m16/
I rooted my Teclast M16 using Magisk. Simply unlocked the bootloader through adb/fastboot commands, then have magisk manager patch the boot image from firmware download and then flash it using adb/fastboot command line fastboot flash boot magisk_patched_boot.img reboot system and its rooted.
I haven't found a twrp recovery yet, but I'm thinking about trying my hand at building my own, despite being a noob.
I can confirm
install adb fast boot
Enable USB debugging and OEM Unlock on your Android device.
adb reboot bootloader
fastboot flashing unlock
Volume up
fastboot reboot
Wait a few minutes to reinstall
enable usb debugging again
download firmware
you will finde a google spreadsheet on the facebook page of telcast
Copy boot.img on the device
install magisk manager via apk
install magisk via patch boot.img in download folder
download patched boot.img
patch device
adb reboot-bootloader
fastboot flash boot magisk_patched_boot.img
fastboot reboot
M16(M6P2)_Android 8.0_V1.07_SZ
boot.img httpx://mirr.re/d/2wHd
full httpx://mirrorace.com/m/1Ek3z httpx://mirr.re/d/2wHj
Hi. Have you got you on working twrp recoberto?
fdsafggg said:
I can confirm
install adb fast boot
Enable USB debugging and OEM Unlock on your Android device.
adb reboot bootloader
fastboot flashing unlock
Volume up
fastboot reboot
Wait a few minutes to reinstall
enable usb debugging again
download firmware
you will finde a google spreadsheet on the facebook page of telcast
Copy boot.img on the device
install magisk manager via apk
install magisk via patch boot.img in download folder
download patched boot.img
patch device
adb reboot-bootloader
fastboot flash boot magisk_patched_boot.img
fastboot reboot
M16(M6P2)_Android 8.0_V1.07_SZ
boot.img httpx://mirr.re/d/2wHd
full httpx://mirrorace.com/m/1Ek3z httpx://mirr.re/d/2wHj
Click to expand...
Click to collapse
Hi.
I tried to unlock the bootloader .
adb devices command shows the m16.
I send the command "adb reboot bootloader" - the device enter in bootloader.
next I send the command "fastboot devices" and I get this:
PS E:\modified_fastboot> fastboot devices
???????????? fastboot
any help to make fast boot see the device?
Thank you
dcoelho said:
Cześć.
Próbowałem odblokować bootloader.
Polecenie urządzeń adb pokazuje m16.
Wysyłam polecenie "adb reboot bootloader" - urządzenie wchodzi w bootloader.
następnie wysyłam polecenie „urządzenia fastboot” i otrzymuję to:
PS E:\modified_fastboot> urządzenia fastboot
???????????? szybki start
jakakolwiek pomoc, aby szybki rozruch zobaczył urządzenie?
Dziękuję Ci
Click to expand...
Click to collapse
Hi, You bad comand when bootloader. When bootloader after comand: " fastboot oem unlock" , luck on skreen, push volume up, wait moment, after next comand:"fastboot reboot". After this command, the tablet will reset to factory settings with unlocked bootloader.
Hello everyone. I have TWRP for M16, everything is almost fine, after uploading it normally work on M16, except for touch not working, I did not check if it works with the mouse. Maybe someone will find it to correct it so that the touch works? I upload the file, it may be useful to someone. Regards RW
reupload boot.img
Unlocking Bootloader1. Make sure you have a sim and active mobile data. Then go to about phone tap build number 7-8 times. After that go to advanced settings > developer options > turn on OEM unlocking and then check if this device is secure and click add account and device.
2. Download Mi unlock tool from here. Extract it and paste it in C:/unlock. or else your device won't be recognized for unlocking.
3. Open Mi unlock tool and then enter the Mi account which was on your device. Put your device in fastboot mode by pressing vol- and power and then connect to PC. Press unlock and if it tells you to wait you have no other option but to wait. If your mi flash tool shows connect your device even after you have connected it. Follow this guide here.
4. After you have unlocked your bootloader reboot your phone.
Flashing TWRP and Rooting via magisk
1. Download this TWRP image here. Thanks to the original developer mauronofrio.
2. Download adb and fastboot tools here and install it.
3. Now put your phone in fastboot mode and connect it with your pc. Now where you have downloaded the TWRP file rename it to TWRP.img and open a CMD window there if you don't know how just google.
4. Type the following commands
1. fastboot devices
2. fastboot flash recovery TWRP.img
3. fastboot reboot recovery.
Click to expand...
Click to collapse
5. Your phone will boot into TWRP now. But TWRP will be overwritten by stock miui recovery to stop that you need to flash Magisk. Download this zip move it to internal storage then flash by tapping on install and swipe to flash. Reboot your device. Reboot to recovery again to check if TWRP is present.
Now your device is rooted
OR
Flash latest OrangeFox Recovery if you don't want magisk.
Flashing A rom
1. Download.
2. Flash.
3 Format Data.
Done
Feel free to ask any questions. And don't point a finger at me for messing your device.
My mi unlock tool says can't get info. I using Indian version miui 12
Thanks for the useful guide. I have a quick question, does this works with MIUI 12?
igeekyayush said:
My mi unlock tool says can't get info. I using Indian version miui 12
Click to expand...
Click to collapse
Sorry for late reply. Have you installed the drivers correctly? Try using another port in your pc or use this mi unlock tool version zip
Doombuggie85 said:
Thanks for the useful guide. I have a quick question, does this works with MIUI 12?
Click to expand...
Click to collapse
Yes, it does.
hello,
thanks for the reply sir. yes i've tired changing port, pc everything. today i've factory reset my phone and added mi account and now i'm getting 7 days wait time. let's see now
LoadOP2 said:
Sorry for late reply. Have you installed the drivers correctly? Try using another port in your pc or use this mi unlock tool version zip
Click to expand...
Click to collapse
igeekyayush said:
hello,
thanks for the reply sir. yes i've tired changing port, pc everything. today i've factory reset my phone and added mi account and now i'm getting 7 days wait time. let's see now
Click to expand...
Click to collapse
Okay keep the sim inserted and use the device for 7 days. And if it doesn't work try using older version of unlock tool.
Hi there!
Silly question: is it possible to install TWRP but keep the official ROM? (phone is unlocked)
_benedict_ said:
Hi there!
Silly question: is it possible to install TWRP but keep the official ROM? (phone is unlocked)
Click to expand...
Click to collapse
Flashing a custom rom is optional. You don't NEED to flash a rom to get TWRP...
---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------
I've unlocked the bootloader using the unlock tool and waited for 7 days,
But i rooted the device using a different method where i patched a boot.img and flashed that to the device.
Will this method still work for me as I'm already rooted but just want TWRP so i can flash other ROMs.. The post says you have to flash magisk from the (temporary) TWRP for the TWRP to stay as the recovery..
Will the magisk on my phone and the magisk installed here collide?
I just want TWRP so i can switch to a custom rom, so any input is appreciated!!
_benedict_ said:
Hi there!
Silly question: is it possible to install TWRP but keep the official ROM? (phone is unlocked)
Click to expand...
Click to collapse
Skip the flashing a rom part and you will be good to go.
But i rooted the device using a different method where i patched a boot.img and flashed that to the device.
Will this method still work for me as I'm already rooted but just want TWRP so i can flash other ROMs.. The post says you have to flash magisk from the (temporary) TWRP for the TWRP to stay as the recovery..
Will the magisk on my phone and the magisk installed here collide?
I just want TWRP so i can switch to a custom rom, so any input is appreciated!!
Click to expand...
Click to collapse
You can flash twrp and then check if it persists. If not flash magisk again their is no thing as magisk colliding lol. Just make sure you flash a newer version. And if nothing works flash stock rom and then twrp.
If you have the stock boot IMG flash it and then intsall twrp and magisk.
smsry said:
Flashing a custom rom is optional. You don't NEED to flash a rom to get TWRP...
Click to expand...
Click to collapse
LoadOP2 said:
Skip the flashing a rom part and you will be good to go.
Click to expand...
Click to collapse
Haha, makes sense! Thank you for your answers
Nevermind.. i got it to work pretty easily..
I have twrp on this device and Pixel Experience ROM and it's working all fine..
But there's this one thing where when booting to recovery, it asks me to input a password for User(0) when i try to input anything it says password failed..
From reading the log, it says it's for decrypting data(8f I'm not mistaken)
Is this important? Do i need to decrypt it?
Currently the ROM works fine with no errors, so I'm not gonna bother, but would still like to know what this "decrypting" thing is..
smsry said:
Nevermind.. i got it to work pretty easily..
I have twrp on this device and Pixel Experience ROM and it's working all fine..
But there's this one thing where when booting to recovery, it asks me to input a password for User(0) when i try to input anything it says password failed..
From reading the log, it says it's for decrypting data(8f I'm not mistaken)
Is this important? Do i need to decrypt it?
Currently the ROM works fine with no errors, so I'm not gonna bother, but would still like to know what this "decrypting" thing is..
Click to expand...
Click to collapse
Yes, If you use a lock screen enter that password it will be decrypted. You will have to format data if you decide to flash any other rom anyway.
flashed twrp but not able to boot into recovery.
igeekyayush said:
flashed twrp but not able to boot into recovery.
Click to expand...
Click to collapse
There can be many reasons for that. Please tell me the error or what's actually happening. Then only I can be of help.
Sir ive used xiaomi flashtool v2 after that and it worked. Thanks sir. After that i updated to latest twrp from that chinese one.
LoadOP2 said:
There can be many reasons for that. Please tell me the error or what's actually happening. Then only I can be of help.
Click to expand...
Click to collapse
Joyeuse
Hello, Does it work for Joyeuse (European version)?
The name of TWRP says Curtana -Unified
rfguy said:
Hello, Does it work for Joyeuse (European version)?
The name of TWRP says Curtana -Unified
Click to expand...
Click to collapse
Yes Unified means all Snapdragon 720g Devices which include Joyeuse, Curtana, Gram, Excalibur.
Hey buddy, thank you for this quick step-by-step guide. I flash ROMs since 2012 and you know what? It helped me the same. Having all stuff needed for go from stock to custom concentrated in one place (plus some useful tip like the Magisk flash at the end) it's always useful and time-saving. Thank you
2 Micro-notes about fastboot btw:
- write 'fastboot (with lowered 'f'): it may confuse some newbie
- it's 'reboot' instead of 'boot'
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
T4gB0t said:
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
Click to expand...
Click to collapse
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Hw4ng3r said:
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Click to expand...
Click to collapse
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
T4gB0t said:
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
Click to expand...
Click to collapse
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Hw4ng3r said:
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Click to expand...
Click to collapse
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
T4gB0t said:
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
Click to expand...
Click to collapse
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Hw4ng3r said:
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Click to expand...
Click to collapse
I downloaded the software from the official website and used payload dumper to extract the boot image. To be sure that I understood everything... you suggested to use "fastboot boot patched.img" instead of "fastboot flash boot patched.img", and once the phone restarted to go to magisk manager and click direct install.
Do I need Magisk Manager canary or the normal version for this to work and do I have to mantain the canary version or can I install the normal version once it is rooted?
Either 22.1 or Canary works for A11
Hw4ng3r said:
Either 22.1 or Canary works for A11
Click to expand...
Click to collapse
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
T4gB0t said:
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
Click to expand...
Click to collapse
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
T4gB0t said:
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
Click to expand...
Click to collapse
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Hw4ng3r said:
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Click to expand...
Click to collapse
So not Magisk v.23 but Magisk canary?
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Hw4ng3r said:
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Click to expand...
Click to collapse
Okay thanks, I'll try with v.23 first and If that does not work than I'll try with the canary one. Thank you very much!!!
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Wacko1805 said:
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Okay thank you, I'll try if the other method does not work
T4gB0t said:
Okay thank you, I'll try if the other method does not work
Click to expand...
Click to collapse
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Hw4ng3r said:
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Click to expand...
Click to collapse
I'm sorry to bother you again, but I tried with "fastboot boot patched.img" and it still did not work. It got stuck while booting again with "unable to parse kernel log" as error message. Do you have any other suggestions?
P.S. I got a full backup with "adb backup -apk -all -shared -f /path/to/location" today and thought about just doing a factory reset, trying to root the phone, restore the backup. Do you think that might actually work? Thank you for your help!
How exactly did you patched your boot.img?
FSadino said:
How exactly did you patched your boot.img?
Click to expand...
Click to collapse
I tried doing it with magisk (both v.23 and canary)
Hello, I am from Canada and I just got a Moto G Power (2021) XT2117-4 with the firmware QZBS30.Q4-43-129-2. I unlocked the bootloader thru Motorola with no problems. I installed Rescue and Smart Assistant and downloaded my firmware. I patched the boot.img thru Magisk and flashed it to my phone using ADB. I was not able to achieve root. I also tried to boot thru recovery mode but got the no command sign. I then rescued my phone and tried it again flashing to both boot_a and boot_b still to no avail. If anyone has any info on why this is and has a solution to my problem it would be greatly appreciated.
jwreidmoto said:
Hello, I am from Canada and I just got a Moto G Power (2021) XT2117-4 with the firmware QZBS30.Q4-43-129-2. I unlocked the bootloader thru Motorola with no problems. I installed Rescue and Smart Assistant and downloaded my firmware. I patched the boot.img thru Magisk and flashed it to my phone using ADB. I was not able to achieve root. I also tried to boot thru recovery mode but got the no command sign. I then rescued my phone and tried it again flashing to both boot_a and boot_b still to no avail. If anyone has any info on why this is and has a solution to my problem it would be greatly appreciated.
Click to expand...
Click to collapse
Does the phone boot with the patched boot.img ?
sd_shadow said:
Does the phone boot with the patched boot.img ?
Click to expand...
Click to collapse
Yes.
jwreidmoto said:
Yes.
Click to expand...
Click to collapse
What does the magisk app say?
Can you share a screenshot?
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
What does the magisk app say?
Can you share a screenshot?
Click to expand...
Click to collapse
That is just how the patched boot.img is created.
Now you have to flash it with fastboot.exe
Been thru that already no root.
Do I have to rename it to boot.img when I flash it or can I leave with with the patched name?
I am going to start from scratch again. I don't think I made a mistake because I rooted my G7 Play this way too. I also get feedback from terminal confirming flashing.
jwreidmoto said:
Do I have to rename it to boot.img when I flash it or can I leave with with the patched name?
Click to expand...
Click to collapse
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
and
How to root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and more
Rooting your phone is still possible — and fun — these days. Here's how to do it on your Android device.
www.xda-developers.com
Followed link instructions exactly and still no root. Maybe I have to go with a TWRP recovery method. I will keep checking forums for others having same issue.
jwreidmoto said:
Followed link instructions exactly and still no root. Maybe I have to go with a TWRP recovery method. I will keep checking forums for others having same issue.
Click to expand...
Click to collapse
Ok, if you want help you have to give details.
No root means nothing.
I downloaded firmware from Rescue assistant copied boot.img to phone selected it thru magical and patched it. Copied patched boot.img to PC. Put it in ADB folder renamed it back to boot.img. Opened up ADB terminal and flashed - fastboot flash boot boot.img. Terminal said writing boot_a......okay.....finished. reboot no root. Tried again with flashing to boot_a and to boot_b. Reboot still no root. That's about all I can tell you everything checked out including ramdisk - yes in Magisk, boot.img from same firmware that is currently on phone. Not sure why it's not working.
Actually, sorry phone is now rooted. Once I added root checker to superuser in magisk it showed phone was successfully rooted Thanks for all your help!
Just to confirm, as I've yet to root my device and may encounter this same issue. Did you solve it having done anything different with the rooting procedure or was it a simple matter of adding the root app to Magisk SU? If the latter, Did magisk display the SU prompt at all?
Yes, the root instructions are good. I think why Magisk did not prompt me, initially was because my phone was setting up for the first time and it was bogged down by Google restoring apps etc. Now Magisk prompts me every time for root apps.
So I'm Down to Help this is what I did. So
Download Rescue and blah blah assistant
Found My Phone Checked and Double Checked all information then when I did so I extract led the Folder to My desktop, looked inside it's little bundle of goodness to find boot.img pulled it out and connect my Moto G.
At This Point I Just Opened up My Phone storage (from My P.C) pulled it out and stuck it in my main storage.
At that point Went and Got Magisk v.23 renamed the download as Magisk v.23.apk
Then Riped her Open Like A wild animal installed the .apk (If the File Manager or whatever you are using won't let you install go to settings for the particular File Manager you are using on your phone and allow download a from unknown sources)
Pulled out the boot.img I put in my main storage and went to My sexy New Magisk App and selected "select and Patch a file"
At the Point stepped out for a quick smoke and had a tug.
Then your final product will be Magisk_patchedv23.img (or something like that)
Then after you get all that mumbo move that back to your P.C
I assume you have adb fastboot
So then I pull it up (not sure if it affects anything but I did adb Root)
Anywho first I did
adb devices -l
As soon as I see my phone se then I know I got it.
#also side not make sure the wording next to the device says device
Ok so at the point type
adb reboot fastboot
Then repeat same command as the adb one
Fastboot devices
#seeyour device? Dope
Then wherever you put that patched image sometimes you need to put the FULL path
Example for me it was
Fastboot flash magisk_patched.img boot
Which didn't work so tried the _a still nothing soo hence the FULL PATH I put it on my desktop if you don't know the full path right click the file and hit properties
final Command for me
fastboot flash boot C:\Users\insan\Desktop\magisk_patched.img
Boom Done and Done!!!! And as always take Back Ups Before and After and Save that Patch .img
I've needed it like 10 times !
Hope That Helps Ya
And the last pic Is Proof
God Bless, and Good Luck!