Hey guys, because there is unfortunately no fully working TWRP yet and lack of magisk patched boot.img for each rom, i decided to make a script to make things easier.
This script is based on the post https://forum.xda-developers.com/showpost.php?p=81277507&postcount=613 from @gpz1100, which is based on thread [GUIDE] How to Root OnePlus 7T without TWRP by @mauronofrio
What does it do?
The script pull the boot image from your actual system and copy it to your PC.
Then you have to copy the boot image back to your device and patch it with Magisk Manager.
To prevent problems and bootloops the script will boot the patched image first, if anything went well the script will flash it subsequently.
Requirements:
unlocked bootloader
ADB/Fastboot installed
latest TWRP from here
Make sure the .bat and twrp image are in your adb/fastboot folder!!
How to use?
Download the .bat file, place it into your ADB/Fastboot directory and start it.
If windows shows a warning, then just click on "more informations" and then "run anyway".
If you trust me, dont trust the internet and check hash sum MD5 after downloading the file with:
Code:
CertUtil -hashfile <filename> MD5
MD5 checksum is: 303f338c32841ac752d24647ec6ede14
If you dont trust me there are several options:
Use the guide from https://forum.xda-developers.com/showpost.php?p=81277507&postcount=613 from @gpz1100 and do it yourself
or use any guide from [GUIDE] How to Root OnePlus 7T without TWRP by @mauronofrio
check the code on github here
If you run into problems/errors:
Be sure the .bat file is located where adb.exe and fastboot.exe is
If you need urgent root, than follow the guide mentioned above
Be patient, i try to fix the problem as soon as possible
Only tested on Oneplus 7T with OxygenOS
Download from: google drive or from github
Credits:
topjohnwu - for Magisk
mauronofrio - for TWRP
gpz1100 - for his guide
Will I still be rooted if I take an OTA update?
---------- Post added at 01:16 PM ---------- Previous post was at 12:57 PM ----------
Also at one point your after trying to pull the boot image from the phone the script says:
## checking for adb devices..
## device still not in custom recovery, retrying...
Yet the phone restarts. The script retries about 4 times then fails. I think at whatever set in the script before that occurs, it needs to fastboot into recovery rather than do a normal restart.
slipnslider said:
Will I still be rooted if I take an OTA update?
---------- Post added at 01:16 PM ---------- Previous post was at 12:57 PM ----------
Also at one point your after trying to pull the boot image from the phone the script says:
## checking for adb devices..
## device still not in custom recovery, retrying...
Yet the phone restarts. The script retries about 4 times then fails. I think at whatever set in the script before that occurs, it needs to fastboot into recovery rather than do a normal restart.
Click to expand...
Click to collapse
no, but you can root again with the tool
slipnslider said:
Will I still be rooted if I take an OTA update?
Click to expand...
Click to collapse
No. After ota you won't have root. But after installation of ota don't reboot and do this:
1. Open magisk manager
2. Install --> install after ota
3. Reboot.
Now you have updated system with root.
slipnslider said:
Will I still be rooted if I take an OTA update?
---------- Post added at 01:16 PM ---------- Previous post was at 12:57 PM ----------
Also at one point your after trying to pull the boot image from the phone the script says:
## checking for adb devices..
## device still not in custom recovery, retrying...
Yet the phone restarts. The script retries about 4 times then fails. I think at whatever set in the script before that occurs, it needs to fastboot into recovery rather than do a normal restart.
Click to expand...
Click to collapse
oh sorry i missed the second question,
the script should boot your phone into twrp recovery, where it get's adb access to pull the boot.img. Do you named the twrp img to TWRP.img?
Yeah it was named TWRP.img but I actually had another problem going on with my device that I believe was causing this. Got it all fixed using that back to root/unbrick Msm.exe tool that someone else posted
Worked flawlessly, got a little bit lost when the prompt about magisk came out then realised that I needed to copy files over, patch on the phone with the Magisk Manager app then copy files over again.
But once that's sorted, it worked with no issues
Noob question but the flash of the modified boot.img would be a clean flash or a flash over the existing one,asking cause I haven't rooted a device and was wondering if this would erase all of my apps and existing settings?
Radicalcokemonkey23 said:
Noob question but the flash of the modified boot.img would be a clean flash or a flash over the existing one,asking cause I haven't rooted a device and was wondering if this would erase all of my apps and existing settings?
Click to expand...
Click to collapse
Flashing boot.img won't wipe your data. But unlocking the bootloader will reset your phone.
Kollachi said:
No. After ota you won't have root. But after installation of ota don't reboot and do this:
1. Open magisk manager
2. Install --> install after ota
3. Reboot.
Now you have updated system with root.
Click to expand...
Click to collapse
I didn't want to update because I would loose root but I'll give your advice a go.
At 71% it says something went wrong.
imakul8 said:
At 71% it says something went wrong.
Click to expand...
Click to collapse
i think ur phone disconnect during the process, maybe try another usb cable or usb port for the process
Kollachi said:
No. After ota you won't have root. But after installation of ota don't reboot and do this:
1. Open magisk manager
2. Install --> install after ota
3. Reboot.
Now you have updated system with root.
Click to expand...
Click to collapse
Yes, just make sure you install into INACTIVE slot after OTA, if you havent rebooted yet.
I believe one problem exists with twrp (possibly depending on the version) ... when the script tries to download the stock image, TWRP wants confirmation for write access. Unless I confirm that, the download doesn't succeed. Once confirmed, the same adb line in the script entered manually then works ...
I bought a phone advertised as factory unlocked. It has no carrier branding. It turns out to be a model HD1907, which in Wikipedia shows as T-Mobile.
I installed the OnePlus USB drivers from the phone.
I used the original cable.
In Developer Options I had set Advanced Reboot on and USB Debugging on. I tried OEM Unlocking on and off just to try.
I am getting a failure at the boot to TWRP step. The fastboot error, which I tried manually as well, is:
FAILED (remote: 'boot is not allowed in Lock State')
On the fastboot screen I do see the message:
DEVICE STATE - locked
Am I going to need to go through a bootloader unlocking process like this?
Noob Bootloader Unlock Guide: Answers to several questions and solutions to problems.
***Warning: I am not responsible for bricked or broken devices, warranties, computers, etc. This is your phone and your free will to follow the below steps and you bare the full burden of any consequences.*** A note for the Moderators: I am...
forum.xda-developers.com
It's a nicely done script, by the way.
I'm sorry but I'm really newbie, so please can you tell me how to activate adb access?
imakul8 said:
At 71% it says something went wrong.
Click to expand...
Click to collapse
I'm stuck in the same problem, I changed the slot but nothing changes...
Related
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
charesa39 said:
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
Click to expand...
Click to collapse
Right, thanks for the information. So I repeated and booted into TWRP again. Tapped 'Install', navigated to /cache, saw a couple of folders named 'back up', 'lost+found', and then a file name of a large string of letters followed by the recognisable "razor KTU70 from KOT49H", so I went ahead and flashed the latter, checking 'verify signature'. Runs through a few commands and in a few seconds comes back as failed, so I reboot into the OS.
Any ideas?
Aerowinder said:
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
Click to expand...
Click to collapse
I think I have an idea, but I'll check just to be sure. Thanks for the direction.
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Anderson2 said:
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Click to expand...
Click to collapse
If it fails look to see what the specific error is. It would help to know that. If you pulled it from your cache then I assume it was downloaded by itself and should be the correct OTA. I do NOT have the "Zip file signature verification." box checked or "Enable MD5 verification of backup files." but I am extremely careful to flash/install the correct files. The OTA installed fine for me two days ago using TWRP 2.7.1.0. The 4.4.4 mentioned earlier is the factory image. You will need adb and fastboot installed on your computer to flash the factory image or any image that is pulled from inside the factory image. Wug's toolkit will work also, I think, but I've never used any toolkits. Eventually there will be a stock 4.4.4 rom that you can flash/install in TWRP but I'm not aware of one right now.
You can take the normal updates with root and TWRP (I did), but a custom kernel will prevent them from installing.
I retried to install the downloaded ota file from cache, but this time I checked zip file verification and got the error message that zip verification failed.
File name was
df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip
So it seems the downloaded ota file may be corrupted. How do I get my Nexus 7 2013 to re-download a new one?
(The ota download for my Nexus 5 installed with no problems - but I think it didn't go through TWRP even though TWRP is installed there too).
Thanks
---------- Post added at 04:05 AM ---------- Previous post was at 03:59 AM ----------
Further
I renamed the ota file and in settings checked for system update and got a response that my system is upto date. But it is still 4.4.2.
Need to re-download the ota. How?
Changed the system date to 2 weeks earlier and succeeded in re-downloading the ota file.
So I retried installing it and it again took me to my TWRP recovery screen. I again installed the ota from cache and again the zip verification failed : 1
And the update failed again.
Still on 4.4.2
Did not change any system files as far as I know.
Need help.
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Aerowinder said:
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Click to expand...
Click to collapse
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Anderson2 said:
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Click to expand...
Click to collapse
1. The Google firmware link in my signature is the one you want. You say you have the 2013 wifi model, aka flo, aka razor. "Factory Images "razor" for Nexus 7 [2013] (Wi-Fi)" is the proper section for you. You want 4.4.4 (KTU84P), and that's at the bottom of the razor section. Click the link to download.
2. Download the most up to date ADB/Fastboot from the link in my signature (19.0.2 (API 19)). Don't extract it yet.
3. You will lose root. Download SuperSU from my signature. 2.00 is the current version. After you download that, you can put it on your device so you can flash it in recovery in a few minutes.
The firmware you downloaded is razor-ktu84p-factory-b1b2c0da.tgz. This is a compressed archive, and you will need to extract it. If you don't know how, 7-Zip should work.
So, you've extracted the files. Delete flash-all.bat, flash-all.sh, flash-base.sh (so you don't accidentally run them).
Now, all you have left is bootloader-flo-flo-04.02.img and image-razor-ktu84p.zip.
Extract image-razor-ktu84p.zip to the current directory, so you will now have bootloader-flo-flo-04.02.img, boot.img, cache.img, recovery.img, system.img, userdata.img, android-info.txt, image-razor-ktu84p.zip in your folder.
Delete userdata.img, flashing this on accident will wipe your data. Delete image-razor-ktu84p.zip, android-info.txt, cache.img, recovery.img (this is stock recovery, you want TWRP).
Now you have boot.img, bootloader-flo-flo-04.02.img, system.img.
Remember the ADB & Fastboot zip you downloaded from my signature? Extract it to the directory with bootloader-flo-flo-04.02.img, boot.img, system.img. All 4 files. This directory now contains 7 files.
Back out of the razor-ktu84p folder. Just one step back. Now, hold shift the right-click the razor-ktu84p folder. Select Open command window here.
Reboot your device to bootloader mode. Do so by shutting it down. Then while the power is off, hold volume down and press the power button. Release these buttons when you see the big green Android.
In your command window, type the command: fastboot devices
Your device with it's serial number should show up on the list. If it does not there is a problem and you need to stop here.
If the device shows up, let's update it.
fastboot flash bootloader bootloader-flo-flo-04.02.img
<wait for it to finish>
fastboot reboot-bootloader
<wait for it to reboot>
fastboot flash system system.img
<wait for it to finish>
fastboot flash boot boot.img
<wait for it to finish>
fasboot reboot-bootloader
Done with fastboot.
At this point, enter recovery (TWRP) and wipe cache and Dalvik under advanced wipe.
Remember the SuperSU you downloaded earlier and put on your device for later? Flash that now.
Reboot, all done. Most of this is just juggling files around. If you have any questions ask.
You are wonderful aerowinder. This is just what I needed to go ahead. Thank you so much.
About your signature, it doesn't show the links when viewed in my Tapatalk version, but I went to the Web view and got it from there. (just FYI if others ask about your links).
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
droider137 said:
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
Click to expand...
Click to collapse
If you were already on 4.4.3, all you need to do is fastboot flash system.img, that is correct.
No, you can't flash that firmware zip in recovery.
thanks
Hi Aerowinder
Thanks again for the excellent instructions. Everything went like clockwork until it didn't ?......
I got to the point where I issued the command fastboot devices which did show the tablet serial number. But my next command to flash the bootloader img gave me the error:
Cannot open 'bootloader-flo-flo-04.02.img
(I had copy pasted the command from your instructions).
The subdirectory below the command window contains that file (one of 7 files)
Sorry. What should I do?
In case you need the info, the device screen showed
Fastboot mode
Product name - flo
Variant - flo 32G
Hw version - rev_e
Bootloader version - flo-04.02
Carrier info = none
Serial number - xxxx
Signing - yes
Secure boot enabled
Lock state - unlocked
Thanks again.
Aerowinder, you are not only an expert but an excellent teacher. Your instructions above should be a sticky.
I'm all done. Everything is fine.
The problem I had above was a file path problem. Not sure why you told me to open the command window in the parent folder. When I opened it in the folder containing the seven files all your commands worked fine. (Except for your last one where you had a spelling mistake: fasboot instead of fastboot).
Thank you very much.
(I wrote the 'new' version of rooting out of memory / conjecture, it should not do irreversible harm to your tablet, however, always apply common sense and proceed with caution. Caveat - I am neither a developer nor software engineer.)
'New' version of rooting procedures can be carried out with relative ease now that @krustymars has done the heavy lifting and ported TWRP to Teclast X16Plus; applies to both native android 5.1.1 and Remix 2.0.
In his write-up, it wasn't mentioned that TWRP can only be installed if X16 Plus's bootloader is 'OEM unlocked' and ROM will only boot if X16 Plus's boot image is patched (insecured), after the flashing of TWRP.
To unlock is not difficult (fastboot oem unlock), but it will also wipe /data of the ROM (making it unbootable too?). Question mark here as I am uncertain whether this action will render the ROM unbootable or not. For the sake of not doing double jobs, we assume it will.
The third condition for the ROM to first boot properly after flashing is the original recovery must be present (again I am not sure if a patched boot image will do the trick; for the same reason above, we assume it won't)
Therefore the only way out is to ensure the bootloader is not re-locked after the flashing of ROM, for us to be able to flash an effective TWRP AFTER the ROM has finished its first boot.
I believe the above are the main reasons why @stratos7 faced difficulties when intending to root via TWRP.
A simple and rudimentary step by step guide as below (you will LOSE ALL DATA in the tablet, backup all your important stuffs before proceeding):
1) Rename the ROM's original recovery.img to recovery.org. Copy krustymars' TWRP over and rename it recovery.img
This is to ensure that after the flashing, the reboot process will fail and the script will not re-lock the bootloader
2) Flash the ROM as per normal (enter DNX Fastboot by pressing vol+ vol- and power button concurrently, then use Intel Platform Flash Tool Program to flash).
3) After a successful flash, the tablet will enter recovery (TWRP) first time during reboot, and failed. It will be stuck in a boot loop (showing TWRP error).
4) Force shut it by pressing the power button for 10-15secs.
5) Enter fastboot by pressing vol- and power button concurrently.
6) Flash the orginal recovery via adb fastboot.
fastboot flash recovery recovery.img
7) Reboot normally and the ROM will load properly (1st successful boot will take a while; as long as you see the Remix OS logo flashing, all are good).
8) 10x click on Build Number to activate Developer's Menu
9) Activate USB debugging
10) Reboot into fastboot by typing
adb reboot fastboot
11) Check to ensure that bootloader is still unlocked.
12) Flash krustymars' TWRP
fastboot flash recovery TWRP_TeclastX16Plus_by_krustymars.img
13) Flash patched boot image
fastboot flash boot boot.img
14) Choose Recovery Mode, ensure X16 Plus boots into TWRP fine
15) Reboot into ROM from TWRP
16) If you are satisfied that all are fine after rebooting into the ROM, and have copied the latest downloaded SuperSU.zip flashable file into the Internal or Micro SD memory, you can either adb reboot fastboot or shutdown the tablet and vol- power button into fastboot, and then choose Recovery Mode from within fastboot to enter TWRP to flash SuperSU to get root.
Do note that you cannot update binaries within Android, you can update the SuperSU app though if a new version comes up in Play store, just not the binaries. If your binaries become outdated, you will need to flash the latest SuperSU.zip again via TWRP.
The necessary files (minus SuperSU, do grab that from Chainfire's site) - https://www.mediafire.com/?3blso8sjw4kb3e6
Once again, proceed with caution / common sense and the above shouldn't land you in any irreversible situation. All the best!
_____________________________________________________________________________________________________________________________
OLD METHOD
The below instructions for rooting Teclast X16 Plus originated from Teclast's forums. All credits go to the respective creator(s), I merely translated them to post here.
1) Download the standard rooting package from http://www.mediafire.com/download/nrez4ggzau1u8ax/Root.X16Plus.V1.zip
2) Download your corresponding edited boot image file and extracted build prop file (for either Remix OS 2.0 ver B2016062701 or Android 5.1 ver 1.07)
- for Remix OS http://www.mediafire.com/download/b6aazky2y9eqch7/Remix_OS_2.0.zip
- for Android 5.1 http://www.mediafire.com/download/zz40a8cgav385l3/android5.1.zip
3) Download and install Intel's tools and drivers in the order below - http://www.mediafire.com/download/p723or9hxip5eu8/Intel_Flash_Tools.rar
You can omit this step if these drivers are already installed.
- iSocUSB-Driver-Setup-1.2.0.exe
- IntelAndroidDrvSetup1.10.0.zip
- PhoneFlashToolLite_5.5.2.0_win32.exe
4) Download kingroot tool from below, copy the apk file to your X16 Plus and install. There is no need to run the installed app now.
5) Ensure USB debugging is switched on under developer options in your ROM
6) Unzip both the rooting package and your corresponding edited boot image and extracted build.prop files. Cut and paste the unzipped boot image and build prop files into the unzipped rooting package directory.
7) Launch command prompt and change directory to the unzipped rooting package directory
8) Connect your X16 Plus via USB
9) Type and enter - adb reboot bootloader
10) X16 Plus will reboot into fastboot mode
11) Type and enter - fastboot flash boot boot-root.img
12) Type and enter - fastboot reboot
13) X16 Plus will reboot into normal mode, wait for the bootup process to finish
14) Type and enter - su.bat
15) Run the previously install Kingroot app, Kingroot will prompt you to repair root privileges, allow it to do so.
16) Reboot your X16 Plus after the above repair and you will have full root access. If root access is still incomplete, run the above step 14) su.bat command again
Just one thanks cannot say how much grateful I am. THANKS. It work.
Thanks a lot Potatohead ! You rock !
I will try this instruction and post a feedback as soon as possible !
potatohead,
I have just finish to root my tablet. It's very easy and everything is fine.
Once again, thanks a lot ! :good:
great job !!
all are OK under win XP
Thx
Hi @potatohead , Hi @TrYkeR ,
I've just discovered a new firmware V1.07 for our X16 plus on the Teclast website (in the download section) . My tablet is running with the V1.04 version.
Do you know you to flash it, cause TeclastOTA is unable to ugrade it both with the Online mode ("undiscover new version") and the Local mode ?
Reno.
I'm using 1.07, I use a tutorial from their webside.
The big problem is download the firmware, their server sucks a lot. I use jdownload since chrome crash 2 times and do not recover the download
Firmware:
http://pan.baidu.com/s/1nvKVjnF
https://yadi.sk/d/TrUPzmkXsFrXJ (mirror)
here they talk about it:
http://techtablets.com/forum/topic/teclast-x16-plus-i-want-to-change-from-v-1-04-to-v-1-07/
I didn't find the post that I use, but was really easy, like paste the .img files into a folder, put teclast plus in "download mode", they called it diferent, and run an script (.bat)
Hi @TrYkeR,
Thanks for your prompt reply.
I searched for the tuto but I didn't find it too (I already have the V1.07 download). I do not want to do it by myself, i'm not enough confident.
If you find it...
Reno
renofaringite said:
Hi @TrYkeR,
Thanks for your prompt reply.
I searched for the tuto but I didn't find it too (I already have the V1.07 download). I do not want to do it by myself, i'm not enough confident.
If you find it...
Reno
Click to expand...
Click to collapse
I didn't found the exactly post I've use.
Was in this forum:
http://techtablets.com/forum/forums/teclast/general-discussion/page/1/
im new users teclast x16 plus .. is better remixos or android 5.1 firmware 1.0.7 (for drain battery etc..)
Hello friends,
I have the same question.... is better remixos or android 5.1 firmware 1.0.7?
Thanks a lot !!
Renew link
Potatohead, could you please post another link to root.x16plus.v1.zip?
Mediafire removed the file, nowhere else to be found (according to google...)
Thanks in advance!
So did anyone else happen to pick this up from tinydeal while they had it for $79? Not sure if it's arriving with 5.1 or Remix, but this is good to know.
Henk S. said:
Potatohead, could you please post another link to root.x16plus.v1.zip?
Mediafire removed the file, nowhere else to be found (according to google...)
Thanks in advance!
Click to expand...
Click to collapse
As you, I'm looking for this file to root my tablet.
Henk S. said:
Potatohead, could you please post another link to root.x16plus.v1.zip?
Mediafire removed the file, nowhere else to be found (according to google...)
Thanks in advance!
Click to expand...
Click to collapse
bja9 said:
As you, I'm looking for this file to root my tablet.
Click to expand...
Click to collapse
Guys, you can get it here
Link:
pan.baidu.com/s/1eSfpVW2
Password:
xc1u
---------- Post added at 05:20 AM ---------- Previous post was at 05:17 AM ----------
potatohead said:
The below instructions for rooting Teclast X16 Plus originated from Teclast's forums. All credits go to the respective creator(s), I merely translated them to post here.
...
Click to expand...
Click to collapse
I followed the instructions and flashed boot-root.img successfully, however I'm unable to run adb remount in su.bat
it says "remount of system failed: Permission denied", "remount failed"
any ideas?
btc002 said:
Guys, you can get it here
Link:
pan.baidu.com/s/1eSfpVW2
Password:
xc1u
---------- Post added at 05:20 AM ---------- Previous post was at 05:17 AM ----------
I followed the instructions and flashed boot-root.img successfully, however I'm unable to run adb remount in su.bat
it says "remount of system failed: Permission denied", "remount failed"
any ideas?
Click to expand...
Click to collapse
Tank you for the link to the file. It works fine for me !
Rooting in progress.
Did someone sucessfully installed Remix OS 3.0 or W10 ? (W10 i get acpi boot error :/)
I followed the instructions and flashed boot-root.img successfully, however I'm unable to run adb remount in su.bat
it says "remount of system failed: Permission denied", "remount failed"
any ideas?
Click to expand...
Click to collapse
me too...any ideas?
best regards
:good:
..
Hi All
Note: This procedure is for Windows PC only.
I can see there is a similar thread to help on rooting your device.
I created this thread it make it more easier and focussed just on rooting your device rather with additional information.
This menthod is to root your device without TWRP.
There is a detailed guide by @Freak07 which you can find here.
Prerequisite:
1. Your device bootloader is unlocked
2. You have enabled your Developer Options and enabled USB debugging (Settings > System > About phone > Software information, tap build number 7 times to enable Developer options)
3. Flash Tools, download from here and extract to your PC
4. Latest Magisk Manager which you can download from the relevant thread (search or click here)
BOOT IMAGES
Stock Boot images:
Firmware WW_16.1220.1906.174_0 >>>> Click here
Firmware WW_16.1220.1908.189_1.1.1 >>>> Click here
Patched Boot images:
Firmware WW_16.1220.1906.174_0 (patched with Magisk 19.3 stable version) >>>> Click here
Firmware WW_16.1220.1908.189_1.1.1 (patched with Magisk 19.3 stable version) >>>> Click here
Steps to Root:
1. Connect your device with USB cable
2. Go to the folder where you copied Flash Tools and double click to run cmd-here.exe
3. In the command prompt run the command adb devices, this will run the Deamon and show your device under List of devices attached. If doesn't show your device, check your device is connected and USB debugging is enabled.
4. Now run the command adb reboot bootloader to boot your device in to Fastboot mode
5. Now flash the patched boot image with the command fastboot flash boot magisk_patched.img
Restart your device with the fastboot command fastboot reboot and enjoy your ROOTED device
It works great, thanks!!
But then I installed miracast magisk module and now everytime I flash magisk patched boot, my phone is stuck on Asus logo so I have to flask stock boot to use my phone.
I think I should flash system image but when I unzip firmware from Asus site ( https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/ ) on my mac,
It doesn't show any system image (or even boot image), only "compatibility" , "payload" and some other stuff.
Can you tell me what I am doing wrong?
EMJI79 said:
But then I installed miracast magisk module and now everytime I flash magisk patched boot, my phone is stuck on Asus logo so I have to flask stock boot to use my phone.
I think I should flash system image but when I unzip firmware from Asus site ( https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/ ) on my mac,
It doesn't show any system image (or even boot image), only "compatibility" , "payload" and some other stuff.
Can you tell me what I am doing wrong?
Click to expand...
Click to collapse
Hi ASUS firmware for Zenfone do not have system img and instead it is the payload.bin which holds all system files. You can extract system image using python based tools.
You can remove the module if you flash TWPR and using file manger in TWRP to remove magix folder. This will remove magisk completely. Or, reset system via stock recovery. Completely switch off your device. Now, press and hold volume up button and press power button. It will help you to boot in to stock recovery. Or you can follow the guide here
If you still want to flash stock firmware, this link may help.
smohanv said:
Hi ASUS firmware for Zenfone do not have system img and instead it is the paylod.bin which holds all system files. You can extract system image using python based tools.
You can remove the module if you flash TWPR and using file manger in TWRP to remove magix folder. This will remove magisk completely. Or, reset system via stock recovery. Completely switch off your device. Now, press and hold volume up button and press power button. It will help you to boot in to stock recovery. Or you can follow the guide here
If you still want to flash stock firmware, this link may help.
Click to expand...
Click to collapse
If I just reset system via stock recovery, will I lose user data?
EMJI79 said:
If I just reset system via stock recovery, will I lose user data?
Click to expand...
Click to collapse
Yes you do. But you will not loose the files and folder in internal storage like photos etc..
You have to install all user applications again.
I would suggest you to follow the thread to flash TWRP and just remove magisk folder in TWRP file manager.
smohanv said:
Yes you do. But you will not loose the files and folder in internal storage like photos etc..
You have to install all user applications again.
I would suggest you to follow the thread to flash TWRP and just remove magisk folder in TWRP file manager.
Click to expand...
Click to collapse
I will do that.
Just another question: can I just boot in Twrp without installing it?
EMJI79 said:
I will do that.
Just another question: can I just boot in Twrp without installing it?
Click to expand...
Click to collapse
You can boot in to TWRP without permanently flashing it.
Take few cautions before you attempt to boot in to TWRP using this option,
1. Remove fingerprint in security settings (settings > Security & lock screen > Fingerprint)
2. Remove screen lock PIN in settings > security & lock screen > screen lock > select NONE here and also make sure Fingerprint is not enabled in this screen
How to boot in to TWRP:
Download TWRP from here
Use the command in Fastboot > fastboot boot twrp-3.3.1-15-ASUS_I01WD.img
Now you can use file manager in TWRP and remove magisk folder. You have to mount system folder to do so.
EMJI79 said:
I will do that.
Just another question: can I just boot in Twrp without installing it?
Click to expand...
Click to collapse
Did you try the method I explained here >> https://forum.xda-developers.com/showpost.php?p=80100285&postcount=8
smohanv said:
Did you try the method I explained here >> https://forum.xda-developers.com/showpost.php?p=80100285&postcount=8
Click to expand...
Click to collapse
I will do that now. I just came back home.
Thanks.
---------- Post added at 04:28 PM ---------- Previous post was at 03:58 PM ----------
Do you think I can this:
https://magiskroot.net/uninstall-magisk-module-twrp/
edit: it's for older versions of Magisk
Still I can't see the Magisk modules or Magisk folder in /data or /system/data , it appears empty
EMJI79 said:
I will do that now. I just came back home.
Thanks.
---------- Post added at 04:28 PM ---------- Previous post was at 03:58 PM ----------
Do you think I can this:
https://magiskroot.net/uninstall-magisk-module-twrp/
edit: it's for older versions of Magisk
Still I can't see the Magisk modules or Magisk folder in /data or /system/data , it appears empty
Click to expand...
Click to collapse
Are you able to boot in TWRP recovery as I mentioned. Please confirm.
Have you mounted system in twrp. It won't go anywhere. You should find it. I have done this several times.
Read here for some more help.
https://magiskroot.net/uninstall-magisk-module-twrp/
Sent from ASUS ZenFone 6 (2019) using Tapatalk
smohanv said:
Are you able to boot in TWRP recovery as I mentioned. Please confirm.
Have you mounted system in twrp. It won't go anywhere. You should find it. I have done this several times.
Read here for some more help.
https://magiskroot.net/uninstall-magisk-module-twrp/
Sent from ASUS ZenFone 6 (2019) using Tapatalk
Click to expand...
Click to collapse
Yes I am able to boot in TWRP and browse inside the files.
I am checking system square in TWRP mount section however I tried to mount data also and it isn't possible.
I will try the advised link later today, thanks for the help.
EMJI79 said:
Yes I am able to boot in TWRP and browse inside the files.
I am checking system square in TWRP mount section however I tried to mount data also and it isn't possible.
I will try the advised link later today, thanks for the help.
Click to expand...
Click to collapse
Yes. I did try as well. It seems like TWRP is loading in READ ONLY mode. I doubt whether you can flash the uninstall mod as well. But worth trying as you can save all your installed apps.
smohanv said:
Yes. I did try as well. It seems like TWRP is loading in READ ONLY mode. I doubt whether you can flash the uninstall mod as well. But worth trying as you can save all your installed apps.
Click to expand...
Click to collapse
Which method from the link do you advise to try first?
smohanv said:
Yes. I did try as well. It seems like TWRP is loading in READ ONLY mode. I doubt whether you can flash the uninstall mod as well. But worth trying as you can save all your installed apps.
Click to expand...
Click to collapse
Check this link and follow. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
smohanv said:
Check this link and follow. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
Click to expand...
Click to collapse
No luck, can't flash anything in TWRP ...
Guess I have to wait TWRP is updated.
Mauronofrio telling that one have to install 3.3.1-15 to write on data:
https://forum.xda-developers.com/ze...cial-twrp-recovery-asus-t3937844/post80108953
EMJI79 said:
Mauronofrio telling that one have to install 3.3.1-15 to write on data:
https://forum.xda-developers.com/ze...cial-twrp-recovery-asus-t3937844/post80108953
Click to expand...
Click to collapse
yes. I can see that there is an installer (magisk module) which has to be flashed in magisk in order for TWRP to write on data partition.
In your case, you cannot boot your device with rooted image as you have a module which is causing bootloop. Catch 22 sistuation.
In this situation I think you have only one option left which is resetting your device loosing all installed apps. Sorry mate. Could not help you at this time.
New Update
smohanv said:
yes. I can see that there is an installer (magisk module) which has to be flashed in magisk in order for TWRP to write on data partition.
In your case, you cannot boot your device with rooted image as you have a module which is causing bootloop. Catch 22 sistuation.
In this situation I think you have only one option left which is resetting your device loosing all installed apps. Sorry mate. Could not help you at this time.
Click to expand...
Click to collapse
Hello Smohanv,
Say I want to update to the latest Firmware that got released yesterday, and I am currently rooted via the method you introduced on the first page with firmware 16.1220.1906.174_0, how do I go about it?
If I do the Manual update, will I loose root? Or should I wait for you to release a patched one, and then do the manual update?
Thanks.
Damionix said:
Hello Smohanv,
Say I want to update to the latest Firmware that got released yesterday, and I am currently rooted via the method you introduced on the first page with firmware 16.1220.1906.174_0, how do I go about it?
If I do the Manual update, will I loose root? Or should I wait for you to release a patched one, and then do the manual update?
Thanks.
Click to expand...
Click to collapse
Yes you will loose root. Why do you go for build 171 when 189 is available now.
Official link: >>> https://www.asus.com/us/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
New build can be downloaded from here >>> Download
TWRP 3.3.1 & Root for Moto 1 VisionThanks to the efforts of yuri-2016 and and my humble contribution, the TWRP 3.3.1 was made from scratch and a new method of Root was tested.
Accept this gift from the bottom of your heart! :highfive:
Instructions
USB debugging must be enabled on the phone and the bootloader must be unlocked!
1. Download attached archive TWRP_Root_Motne_Vision.zip and extract files from it in the following order::
- .bat executive file and vbmeta.img to the folder with the firmware files;
- TWRP-3.3.1_Motorola_One_Vision.img to \adb\ folder.
- TWRP-3.3.1_Installer_Motorola_One_Vision.zip, Disable_Dm-Verity_ForceEncrypt.zip, Magisk Installer, MagiskManager copy to External SDcard in your phone.
2. Load phone in fastboot mode, then connect it to PC, then start an executive file .bat. At the end of flashing the phone will reboot into bootloader-mode and then TWRP again.
3. In the Recovery at the very beginning we put a checkmark in the checkbox to avoid this request in future, and give permission to modify the system for writing.
4. Go to the Wipe page and run the Format Data for decryption. Enter "yes" for the request. Exit to the Main Menu and reboot to Bootloader.
5. Attention! You mus BOOT into Recovery mode (DO NOT INSTALL it !), through the command:
Code:
fastboot boot C:\adb\TWRP-3.3.1_Motorola_One_Vision.img
6. Flash an archive TWRP-3.3.1_Installer_Motorola_One_Vision.zip which will make TWRP permanent.
NOTE: If you want to keep the stock Recovery , do not install this archive, but in order to boot into TWRP you will need to run the command from Step 5 every time.
7. Configure TWRP via “Settings”-page (time, time zone, language, etc.) as you want.
8. Go to “Install” page and flash the Magisk Installer , and flash Disable_Dm-Verity_ForceEncrypt.zip
9. Reboot in System. Phone will reboot several times, don`t worry. Perform initial settings again.
10. Install MagiskManager.apk, because the application installed in the system generates an error and does not start.
Now your device has a custom recovery TWRP and Root rights! :good: :victory:
01/10/2019 New instruction have been made
30/09/2019 New build TWRP !!!
Fixed: Removed the "Enable MTP" button.
Note: Who will reinstall the new TWRP build over the old one, follow these steps:
1. Download new TWRP_Root_Motne_Vision.zip
2. Load into Recovery mode via the command:
Code:
fastboot boot C:\adb\TWRP-3.3.1_Motorola_One_Vision.img
3. Install TWRP-3.3.1_Installer_Motorola_One_Vision.zip
4. Flash Magisk installer, Disable_Dm-Verity_ForceEncrypt.zip.
5. Reboot in the Recovery again.
6. Try to adjust the brightness, connect USB-OTG, check the absence of the "Enable MTP" button.
Old instructions
Friends! I got the Root for this device.
I'm not saying it's the only way to get a Root. I suggest something I used on my own device.
You are responsible for everything you do with your device!
Getting Root was performed on firmware XT1970-3_KANE_RETEU_DS_9.0_PSA29.160-30
Attention! The process of receiving the Root will delete all your data from the device.
1. The bootloader must be unlocked on the device beforehand.
2. Extract files from the archive https://drive.google.com/open?id=1xgTVlIXOFWq59I1-D9bnRlj1heJycT_I :
- vbmeta.img, vbmeta_patch.img and boot_patch.img to the adb folder;
- MagiskManager-v7.3.4.apk to a convenient folder for you. It will then need to be copied either to the phone memory or to the SD Card.
3. Load the device into fastboot mode and connect it to your PC.
4. Flash vbmeta.img with the command:
Code:
fastboot flash vbmeta_a vbmeta.img
5. Flash boot_patch.img with the command:
Code:
fastboot flash boot_a boot_patch.img
6. Flash vbmeta_patch.img command:
Code:
fastboot flash vbmeta_a vbmeta_patch.img
7. Load the device into the system by pressing the Start button. Phone will reboot in Recovery where there will be a warning that it is necessary to execute Factory reset. It is necessary to give your consent.
The phone will reboot several times again, don't worry.
8. Perform the initial setup. Install MagiskManager-v7.3.4.apk.
9. Launch the MagiskManager application. He will offer to update the application, click the Yes button. The phone will reboot.
Your device now has Root permissions and access to the system!
ilia3367 said:
Friends! I got the Root for this device. Tomorrow I will try to describe in detail the process of getting the Root.
Click to expand...
Click to collapse
Thank you so much!
That's incredible. I hope it works on Moto One Action too.
ilia3367 said:
Friends! I got the Root for this device. Tomorrow I will try to describe in detail the process of getting the Root.
Click to expand...
Click to collapse
This is excellent news, thanks !
Unlock the bootloader
Download the stock rom
Install magisk manager
Click install and chose patch boot image
Copy the patched boot image to your PC
Flash the new image using ADB
I think these are the steps to root the phone
SnoopDoggyStyleDogg said:
Unlock the bootloader
Download the stock rom
Install magisk manager
Click install and chose patch boot image
Copy the patched boot image to your PC
Flash the new image using ADB
I think these are the steps to root the phone
Click to expand...
Click to collapse
Those step give you the validation img error
I'm continuing with my friend to create TWRP
SnoopDoggyStyleDogg said:
Unlock the bootloader
Download the stock rom
Install magisk manager
Click install and chose patch boot image
Copy the patched boot image to your PC
Flash the new image using ADB
I think these are the steps to root the phone
Click to expand...
Click to collapse
That's what a lot of people think. I thought so too.
Thank you so much for the guide... I'll try in the afternoon
@ilia3367
Hello
I have a One Action, could you help me to get root?
Do I need to patch all those images with Magisk?
Thanks in advanced.
sfoot13 said:
@ilia3367
Do I need to patch all those images with Magisk?
Click to expand...
Click to collapse
Make a modified boot.img with Magisk and take my other files. Try to do it according to the instructions.
ilia3367 said:
Make a modified boot.img with Magisk and take my other files. Try to do it according to the instructions.
Click to expand...
Click to collapse
Thank you so much for your help and work!
I'll do that when I arrive at home
Hey! That's really good news pal. Do you think I can flash your Vision's vbmeta.img and vbmeta_patch.img and my magisk-patched boot.img on my Motorola One Action?
Tuandroidaldia said:
Hey! That's really good news pal. Do you think I can flash your Vision's vbmeta.img and vbmeta_patch.img and my magisk-patched boot.img on my Motorola One Action?
Click to expand...
Click to collapse
Replied on the previous page.
ilia3367 said:
Replied on the previous page.
Click to expand...
Click to collapse
Nope, it's not working on Motorola One Action, it says: "<bootloader> validation image failed" using my Magisk Patched Boot.img. Did you patched your boot using another tool or how?
Thanks.
@ilia3367 Finally Rooted. Thank you so much for your work. Very appreciate!
Tuandroidaldia said:
Nope, it's not working on Motorola One Action, it says: "<bootloader> validation image failed" using my Magisk Patched Boot.img. Did you patched your boot using another tool or how?
Thanks.
Click to expand...
Click to collapse
what about vbmeta? was possible to flash it?
@ilia3367 before Root and after unlock the bootloader when I touched the system update option, it said: "system integrity is compromised" now after Root when i touch it , it check for update again. It means that I can update the firmware via ota?
AndresOrue said:
@ilia3367 before Root and after unlock the bootloader when I touched the system update option, it said: "system integrity is compromised" now after Root when i touch it , it check for update again. It means that I can update the firmware via ota?
Click to expand...
Click to collapse
Magisk probably hides the bootloader status so that update check works, but it will most likely fail during install. At least that's how it works on moto one and moto one power.
On moto one I either reflash current build without wipe and then take ota and re-root after, or just flash the update if I get them early, and re-root-
AndresOrue said:
It means that I can update the firmware via ota?
Click to expand...
Click to collapse
I don't think it's possible. The system must be completely virgin to update the OTA. Then why do I need a Root? I need it to customize the system.
ilia3367 said:
I don't think it's possible. The system must be completely virgin to update the OTA. Then why do I need a Root? I need it to customize the system.
Click to expand...
Click to collapse
Thanks a lot. I just unlocked my BL for the second time and this root method is working fine.
May I ask if you just used magisk manager to patch boot, cause when I do I get error on flash.
Code:
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (33792 KB) OKAY [ 1.172s]
Writing 'boot_a' FAILED (Status read failed (Too many links))
And how did you patch vbmeta?
I'm just curious since this patched boot isn't the latest and I wonder how to make this work with the latest boot.img from September patch update.
So after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root ; i modified the contents so it would fit the moto phone a bit better:, but thnx goes to Ibolito over at the pixel 3 forums
1 ) Download the latest Android factory image for your device ("see this guide on where to find it.
2 ) Extract the "boot.img" file from the downloaded image and copy it to your phone.
Warning! Make absolutely sure the firmware is exactly the same as the installed one. If not, you might loose touch.
Be aware that LMSA will download the latest firmware, even if it is not yet installed. That might break your touchscreen
Click to expand...
Click to collapse
3 ) Download latest Magisk Manager application on your phone and install it :
Link
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched.img
edit: i received a comment that the name might be something like Magisk_patched_somerandomletters_.img since the latest magisk update
5 ) Enable adb debugging on your phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
extra: You could test a single boot with that image by typing "fastboot boot magisk_patched.img"
if it boots fine you should have root for this single boot / magisk would show as installed.
9 ) When it's done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and check if everything is good, and it should be
extra info:
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Edit: rewritten entire post so it would look more like a guide, and extra warning because a lot of people seem to loose touch if they don't have the exact same firmware downloaded as on their phone.
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
testtubebaby said:
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
Click to expand...
Click to collapse
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
pjottrr said:
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
Click to expand...
Click to collapse
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Sorry, no idea, i found the provided link via google,
testtubebaby said:
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
zuggi_m said:
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
Click to expand...
Click to collapse
@zuggi_m , how does posting the same url help?
i don't see a retgb here ....
Maybe someone with more dev experience can tell if you need the exact same firmware or if the version numbers are the same it is ok to use that file ?
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
mingkee said:
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
Click to expand...
Click to collapse
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
pjottrr said:
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
Click to expand...
Click to collapse
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
mingkee said:
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
Click to expand...
Click to collapse
maybe i'm missing your point here, my description is just so people who have to figure it out can just use my steps to get root, it is indeed based on fastboot flashing . so i'm not sure what you are trying to say, or am i misinterpreting something?
https://forum.xda-developers.com/motorola-one-hyper/development/rom-omnirom-t4044405
I did root on One Hyper (shipped with Android 10) using fastbootd method
Used old method soft brick my One Hyper
That's why I'd like to know
pjottrr said:
so after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root
you need to download the firmware for our device,
That can be found here;
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETEU/
after that, extract, patch, fastboot install patched version, done.
I did have some issues with the current magisk manager ( from highonandroid, i did find another source, installed version 7.5.1 of the magisk manager from this source
and that one was able to patch the boot.img
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Click to expand...
Click to collapse
There's a head up
US version: Sofia
The rest: Sofiar
I will buy US G Power in May and let's the fun begin
Check out One Hyper general to install Dolby Atmos and it can be toggle on/off.
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
CCivale said:
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
Click to expand...
Click to collapse
So you should know G Stylus ROM is Sofiap.
Be aware the way Android 10 flashing is different.
Download and install the latest ADB in order to access fastbootd (fastboot reboot fastboot) and flash boot, recovery, dtbo, vbmeta, and super
Hmmmm, I will have to read more about fastbootd in your other thread.
I did use the boot.img for the sofiap.
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
hazd said:
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
Click to expand...
Click to collapse
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
pjottrr said:
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
rsdsecure-cloud.motorola.com/download/SOFIA_RETAIL_QPM30.80-51_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
hazd said:
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
Click to expand...
Click to collapse
I downloaded the kernel and waiting for the unit.
I can flash full ROM with fastboot and fastbootd, but just flashing kernel would be much faster.
Moreover, check One Hyper general to get Dolby Atmos because you can turn on and off anytime you want.