Warning! Warning! Warning!
All yours Data and files from internal storage will be lost. So make backup all what you need before continuing
First read Bootloader Unlock and Root Instruction
So your bootloader is unlocked and you want TWRP-recovery on yours V35.
1. Download the necessary kernel
Boot+TWRPv3.3.1_only-V35-Pie-ULM20F.img - boot.img from latest V350ULM20f firmware
Boot+TWRPv3.3.1-V35-Pie-ULM20E.img - boot.img from V350ULM20e firmware
2. Flashing
a) Via Root: if you already have unlocked bootloader and root just copy downloaded f-or-e.img on internal sdcard, run CMD on PC and type
adb shell
su
dd if=/sdcard/_downloaded_.img of=/dev/block/bootdevice/by-name/boot_a
or
dd if=/sdcard/_downloaded_.img.img of=/dev/block/bootdevice/by-name/boot_b
reboot recovery
b) Via Qfil: all you need to know is here Bootloader Unlock and Root Instruction
3. Go to recovery ( via buttons or adb reboot recovery )
In recovery you will see a message that the data is encrypted and you need a password, which you not have.
Click cancel, agree to change system files.
In main menu click Install and select attached file Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
In Wipe menu swipe right, then go back, Format Data - type "yes"
Install latest Magisk.zip
Reboot - System
Done!
Edit:
New Instructions in English: https://github.com/kaneorotar/LG-V35-Tinkering-Instructions/blob/master/README_EN.MD
Original:
I see that you are using my TWRP build.
Here is my original instructions (mainly in Chinese but has enough English to make sense): https://github.com/kaneorotar/LG-V35-Tinkering-Instructions
Yes, you are right. I just patched boot.img
thanks, it worked perfectly for me.
Thanks a lot, not a lot of development and love on this device, I just wanted to say some of us really appreciate this.
SaiLas said:
Warning! Warning! Warning!
All yours Data and files from internal storage will be lost. So make backup all what you need before continuing
First read Bootloader Unlock and Root Instruction
So your bootloader is unlocked and you want TWRP-recovery on yours V35.
1. Download the necessary kernel
Boot+TWRPv3.3.1_only-V35-Pie-ULM20F.img - boot.img from latest V350ULM20f firmware
Boot+TWRPv3.3.1-V35-Pie-ULM20E.img - boot.img from V350ULM20e firmware
2. Flashing
a) Via Root: if you already have unlocked bootloader and root just copy downloaded f-or-e.img on internal sdcard, run CMD on PC and type
adb shell
su
dd if=/sdcard/_downloaded_.img of=/dev/block/bootdevice/by-name/boot_a
or
dd if=/sdcard/_downloaded_.img.img of=/dev/block/bootdevice/by-name/boot_b
reboot recovery
b) Via Qfil: all you need to know is here Bootloader Unlock and Root Instruction
3. Go to recovery ( via buttons or adb reboot recovery )
In recovery you will see a message that the data is encrypted and you need a password, which you not have.
Click cancel, agree to change system files.
In main menu click Install and select attached file Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
In Wipe menu swipe right, then go back, Format Data - type "yes"
Install latest Magisk.zip
Reboot - System
Done!
Click to expand...
Click to collapse
Can bootloader be unlocked on ATT V35 V350AWM I can't find it anywhere? There seems to be some talk it cannot be done?
What's the benefit without ROM's for rooting your phone? Magisk modules?
notanymore said:
Can bootloader be unlocked on ATT V35 V350AWM I can't find it anywhere? There seems to be some talk it cannot be done?
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
SaiLas said:
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
Click to expand...
Click to collapse
Hey thanks!
X-Nemesis said:
What's the benefit without ROM's for rooting your phone? Magisk modules?
Click to expand...
Click to collapse
Yes. On my V30 I've never installed a custom ROM. Rooted stock firmware when the TWRP custom recovery (gift by itself for backups), Magisk mods, Xposed mods. You can tweak yourself without having to install a ROM.
During flashing, you may see error messages about 'unable to unmount vendor'. This is fine as long as the zip flashing doesn't fail halfway.
Click to expand...
Click to collapse
realllllllllllly important. I kept getting unable to mount xx (one of vendor system systemroot randomly) and didn't notice it meant the magisk sticked until I gave up and was ready to settle with no twrp.
YUP
notanymore said:
Can bootloader be unlocked on ATT V35 V350AWM I can't find it anywhere? There seems to be some talk it cannot be done?
Click to expand...
Click to collapse
SaiLas said:
Yes, you are right. I just patched boot.img
Click to expand...
Click to collapse
links dont work
Boot+TWRPv3.3.1_only-V35-Pie-ULM20F.img - boot.img from latest V350ULM20f firmware
SaiLas said:
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
Click to expand...
Click to collapse
after flashing twrp on a/b, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (http://Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip), and Magisk, my v35 wont boot, it got stuck on LG logo, I can go back to TWRP.
Is there any kernel, boot img I have to flash it? Im on this V350ULM20f_00_NAO_US_OP_0218.kdz Pie build
zfk110 said:
after flashing twrp on a/b, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (http://Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip), and Magisk, my v35 wont boot, it got stuck on LG logo, I can go back to TWRP.
Is there any kernel, boot img I have to flash it? Im on this V350ULM20f_00_NAO_US_OP_0218.kdz Pie build
Click to expand...
Click to collapse
Did you wipe your data after flashing the files?
The same happened to me once, I solved that by flashing via upgrade the stock firmware, and then re-rooted.
Excelstar said:
Did you wipe your data after flashing the files?
The same happened to me once, I solved that by flashing via upgrade the stock firmware, and then re-rooted.
Click to expand...
Click to collapse
I just went back to TWRP and used his boot.img to flash within TWRP to boot's partition and then I was able to boot without any issues, I was thinking the same, but it looked more work to do.
kaneorotar said:
Edit:
New Instructions in English: https://github.com/kaneorotar/LG-V35-Tinkering-Instructions/blob/master/README_EN.MD
Original:
I see that you are using my TWRP build.
Here is my original instructions (mainly in Chinese but has enough English to make sense): https://github.com/kaneorotar/LG-V35-Tinkering-Instructions
Click to expand...
Click to collapse
Just wanted to say thanks for the updated instructions. Worked like a charm.
Hello, can you help me with the TWRP file for the LG V350AWM?
Related
In the Oneplus 3T forum it is reported that flashing the bootloader resets the dm verity. Can we get the bootloader for Oneplus 3 to try the fix?
wrong forum body...
there's a specific forums for questions & requests.
Hi,
I had also this problem on my OP3 (not T version).
Solved with this :
1- on Freedom OS 1.7 (any rom should work), rebooted to TWRP (Official)
2- wiped everything including internal storage. (if already on .28 TWRP wiping data to f2fs and wiping internal storage normally may save you some steps later on)
3- fastbooted the official recovery (v1 downloaded from OP site)
4- rebooted to official recovery and started install from ADB.
5- sideloaded beta 9
6- rebooted to beta 9 ( booted perfectly with no issues)
7- reboot back to official recovery (now it will be v2)
8- wipe cahce (and data if available)
9- reboot to fastboot and fast boot mod TWRP .28
10 - on TWRP the password issue might appear but it';; be fixed after this step
11- on TWRP wipe Data to f2fs (even if it was f2fs) and wipe internal storage (it may show it as 0 size)
12- reboot to system
13- reboot back to TWRP and now it can access internal storage , flash SuperSU (sr5)
finaly reboot to system.
Regards,
Ted
Stop with this thread there are already specific threads for dm.
I Made an Backup with flashfire (fastboot flashable). And then restored it. After that the warning was away.
i still not get it, what the big problem is with this warning?
Have it since it came out, and cant find any issue with it?! Or do i miss something?
MultiCulti said:
i still not get it, what the big problem is with this warning?
Have it since it came out, and cant find any issue with it?! Or do i miss something?
Click to expand...
Click to collapse
There's technically no problem other than the annoyance of seeing the warning and using an extra 5 secs
I asked this issue on OnePlus online chat. They said that flashing open beta 7 firmware can solve this issue. I've tryed this and dm-verity error has been gone.
qhsusb_bulk said:
I asked this issue on OnePlus online chat. They said that flashing open beta 7 firmware can solve this issue. I've tryed this and dm-verity error has been gone.
Click to expand...
Click to collapse
And then flashed back OOS 4.02?? It is still gone
panther124 said:
I Made an Backup with flashfire (fastboot flashable). And then restored it. After that the warning was away.
Click to expand...
Click to collapse
Worked like a charm! Thanks for the tip
fuarkgl3 said:
Worked like a charm! Thanks for the tip
Click to expand...
Click to collapse
can u tell me how to restore backup file from flashfire.
phanipk said:
can u tell me how to restore backup file from flashfire.
Click to expand...
Click to collapse
Transfer your backup to your computer and extract the zip, then put your phone in fastbooot mode and click flash-all.bat
there have been so many threads on how to remove DM V. just use the search function dude...
There is no need to flash or erase anything.
Just use these two fastboot commands and the dm-verity notification is gone:
fastboot oem disable_dm_verity (this command is not needed)
fastboot oem enable_dm_verity
snippem said:
And then flashed back OOS 4.02?? It is still gone
Click to expand...
Click to collapse
Sorry for late reply. Yes now i am using OOS 4.0.2 with open beta 7 firmware. Firstly flashed full OOS zip with twrp, secondly i flashed OB7 firmware.
Thanks Sniperle
sniperle said:
There is no need to flash or erase anything.
Just use these two fastboot commands and the dm-verity notification is gone:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Click to expand...
Click to collapse
This was just the right trick
No more DM verity mumbo-jumbo.
THANKS!!!
So those two commands can also be used instead of the dm-verify.zip for those that want to make changes to their system partition (by mounting it in twrp) WITHOUT root?
Rastko said:
This was just the right trick
No more DM verity mumbo-jumbo.
THANKS!!!
Click to expand...
Click to collapse
sniperle said:
There is no need to flash or erase anything.
Just use these two fastboot commands and the dm-verity notification is gone:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Click to expand...
Click to collapse
Can i use this with TWRP, Custom ROM and Root activated? Or is this only possible with original bootloader and recovery?
bensen from hell said:
Can i use this with TWRP, Custom ROM and Root activated? Or is this only possible with original bootloader and recovery?
Click to expand...
Click to collapse
I'm using TWRP, LineageOS, phh root and it works
---------- Post added at 11:13 ---------- Previous post was at 10:59 ----------
sjaak1234 said:
So those two commands can also be used instead of the dm-verify.zip for those that want to make changes to their system partition (by mounting it in twrp) WITHOUT root?
Click to expand...
Click to collapse
The ZIP is for the previous use to not trigger dm-verity at all.
The fastboot commands should disable the message if you have already triggered dm-verity.
Ahhh nice, thanks. I thought that is only work with original bootloader and recovery because the OEM in the command. I'll try it at Weekend.
My setup
Pixel XL from Verizon
Bootloader unlocked
Bootloader Version 8996-0121001-1611091517
Baseband 8996-012511-1611190200
Android 7.1.1 NOF26V
Kernal 3.18.31-g367e645 Dec 7, 23, 2016
Twrp Version 3.0.2.0 RC1
I have tried following this guide to get root access https://www.xda-developers.com/root-is-now-available-for-the-google-pixel-and-pixel-xl/
My steps are
1. boot phone into fastboot
2. from pc run fastboot boot boot-to-root.img
3. the phone reboots
4. Phone is stuck with the 4 colored dots jumping over each other
5. i've given this screen up to 30 minutes with no results.
6. Forcing a reboot causes the same issue
7. Flash stock android via the official google factory image method
I have attempted this other method as well http://www.theandroidsoul.com/root-pixel-xl-magisk/
But after TWRP says it's successful, i boot into my OS and there is no supersu and if i manually install supersu, it says no root access.
You are doing it the old way that was for 7.1.
You want SU 2.79 SR3
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
And you want TWRP RC1.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
I would not install TWRP at this point. So copy SU to your phone. Then boot to TWRP.
Fastboot BOOT twrp.img
With twrp.img being the correct name of the file. Then in TWRP install the SU you copied.
The old way... Sheesh, there's only so much space up here. But thank you. You've saved be a big headache when my XL finally arrives.
Edit: you boot TWRP, not flash through fastboot?
Larzzzz82 said:
The old way... Sheesh, there's only so much space up here. But thank you. You've saved be a big headache when my XL finally arrives.
Edit: you boot TWRP, not flash through fastboot?
Click to expand...
Click to collapse
You boot it, always.
If you want to install it you copy the twrp ZIP to the phone. Boot it with the TWRP image file then install the twrp zip from within twrp.
Gotta be done that way. Partition layout has changes, they are a bit intertwined now.
I dont install TWRP anymore.
That was half the fun not needing a PC to flash a ROM.
I see I'll be reading. A LOT before it gets here.
Larzzzz82 said:
That was half the fun not needing a PC to flash a ROM.
I see I'll be reading. A LOT before it gets here.
Click to expand...
Click to collapse
That might be doable, I am not a ROM guy. Root and kernel only....and I always got a PC.
so I would just want to pull down the twrp RC1 image file, boot from fastboot without flashing it, and use it to flash the SU SR3? All i want is root access at the moment on the pixel XL.
if i understand this right, this will just give me SU with root, and not install any form of TWRP.
steber04 said:
so I would just want to pull down the twrp RC1 image file, boot from fastboot without flashing it, and use it to flash the SU SR3? All i want is root access at the moment on the pixel XL.
if i understand this right, this will just give me SU with root, and not install any form of TWRP.
Click to expand...
Click to collapse
Exactly.
Larzzzz82 said:
That was half the fun not needing a PC to flash a ROM.
I see I'll be reading. A LOT before it gets here.
Click to expand...
Click to collapse
You don't need a PC if you just install TWRP.
TonikJDK said:
Exactly.
Click to expand...
Click to collapse
will i need anything more than ADB? I used depixle8 via ADB to unlock my bootloader.. i assume its just the same to push the files through or am i missing something?
steber04 said:
will i need anything more than ADB? I used depixle8 via ADB to unlock my bootloader.. i assume its just the same to push the files through or am i missing something?
Click to expand...
Click to collapse
What files are you pushing that you cannot just load directly with the device powered up?
steber04 said:
will i need anything more than ADB? I used depixle8 via ADB to unlock my bootloader.. i assume its just the same to push the files through or am i missing something?
Click to expand...
Click to collapse
You will need fastboot, so you can fastboot boot twrp. I don't push the SU zip with adb, I just copy/download it to the phone before I reboot into Fastboot. Make sure you get Fastboot from Google, not the Minimal one.
https://developer.android.com/studio/releases/platform-tools.html
Hey guys,
Thanks to @vanche for the modified kernel and twrp recovery and @fayiaz for the guide on how to root and @Johny Cipel for the original guide and everyone else like
@topjohnwu
@santhosh
@abdyasar
For the original twrp, root and other stuff.
Now thats out of the way
Requirements:
-Unlocked Bootloader (Moto G5 Plus with offers from Amazon won't have unlockable bootloaders but if you buy the standard model from them then you'll be fine)
-Vanche's Modified TWRP from here (http://cloud.vache-android.com/Moto/potter/TWRP/twrp-3.1.0-0-potter.img)
- Vanche's Modified Boot Kernel from here (http://cloud.vache-android.com/Moto/potter/root/potter_boot_test7.img)
- Vanche's Wifi Patch because wifi will stop working after flashing the modified boot kernel (http://cloud.vache-android.com/Moto/potter/root/wlan_custom.zip)
- Chainfires Root http://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
--- If you already have TWRP on your phone, the one by Santosh, you must flash the one made by Vanche or it wont work and you can just download the recovery image and flash it via twrp by toggling the flash zip button on the twrp recovery install menu.
1.. Download all the three files then boot your phone into bootloader mode by holding Volume Down + Power
2. Connect your phone to your PC and then open the adb terminal wherever adb is located open command prompt at that folder
3. Place the recovery image and boot image where the adb terminal folder is located
4. Fastboot flash recovery first and then boot into recovery at least once then reboot into bootloader fastboot flash boot the modified boot image.
5. Boot into the system (May take a while for the first time after flashing the boot image).
6. Place the wlan_custom.zip into your phones internal storage
7. Boot back into recovery and then flash the zip this time
8. Then download and flash the SR3 Super Su from above using recovery and you should have root!!
Safety net may break so if you wanna use Snapchat or any other apps that use safety net make sure you login first then root. You can't logout or else you'll have to unroot and log back in.
wiping?
do we need to wipe storage in this process?
yourtitan said:
do we need to wipe storage in this process?
Click to expand...
Click to collapse
It shouldnt, But if you cant boot then you need to flash the no-verity crypt zip once
Awesomeslayerg said:
It shouldnt, But if you cant boot then you need to flash the no-verity crypt zip once
Click to expand...
Click to collapse
thanks for the reply. but i have several data in my phone. can i just unlock bootloader and root as instructed above without wiping my storage? its a task to take backup of everything. thanks in advance.
wifi not working after supersu root
wifi not working mate.. Flashed custom zip .. No use..
Dhan... said:
wifi not working mate.. Flashed custom zip .. No use..
Click to expand...
Click to collapse
Did you correctly flash vanche TWRP and boot image? Because you're supposed to do that first and then flash the wifi zip..
yourtitan said:
thanks for the reply. but i have several data in my phone. can i just unlock bootloader and root as instructed above without wiping my storage? its a task to take backup of everything. thanks in advance.
Click to expand...
Click to collapse
The phone will wipe as soon as you unlock the bootloader so best to back up first.
Sorry but what's the differences beetwen this method and magisk?
Awesomeslayerg said:
Requirements:
-Unlocked Bootloader (Amazon bought Moto G5 Plus dont have unlockable bootloaders so your out of luck)
Click to expand...
Click to collapse
Only the 'Prime Exclusive - With Offers and Ads' Amazon models don't have an unlockable bootloader, while the 'Standard Version' models can definitely be unlocked. You probably should clarify that or some will think that they can't buy from Amazon and unlock/root the phone.
Dahenjo said:
Only the 'Prime Exclusive - With Offers and Ads' Amazon models don't have an unlockable bootloader, while the 'Standard Version' models can definitely be unlocked. You probably should clarify that or some will think that they can't buy from Amazon and unlock/root the phone.
Click to expand...
Click to collapse
Will do thanks
The "Magisk method" didn't give me privileges on /system, there are some things I can do and others do not, this method gave me full root access like in the other MotoG devices? And the safetynet check fails too?
Anyway thank you very much!!
What's going to be different than magisk root?
Videon Tutorial [SuperSu]
Guys I Found This Video Tutorial For This Thread On Roting Moto g5 Plus With Super Su ------- And Worked Great For Me----- link:-
https://www.youtube.com/watch?v=TV78iWxQrRE
gr8 work mate.....I'm rooted with Magisk...wanna go with super su........do i need to
gr8 work mate.....I'm rooted with Magisk...wanna go with super su........do i need to reflash above said recovery?
will it wipe my current data on both storage?
Pls guide..........How is Moto app working with super su?
Shamith08 said:
Guys I Found This Video Tutorial For This Thread On Roting Moto g5 Plus With Super Su ------- And Worked Great For Me----- link:-
https://www.youtube.com/watch?v=TV78iWxQrRE
Click to expand...
Click to collapse
Thank you so much! This worked! Why would WiFi stop working with this boot image?
I'm
donjuro said:
Thank you so much! This worked! Why would WiFi stop working with this boot image?
Click to expand...
Click to collapse
I don't know why but you have to flash WLAN in order to get it to work
Twrp backup can't worked
I successfully rooted my moto g5 plus mobile. And TWRP INSTALL Latest supersu via. But sdcard card backup can't worked. Why can't work sdcard in twrp? I think this twrp unofficial so not supported sdcard process. Please help me. How to work sdcard backup twrp. I try mount sdcard. But can't mount sdcard. Totally I'm very tired. Please help me.
Does someone have the img file for G5/Cedric?
Awesomeslayerg said:
...Safety net may break so if you wanna use Snapchat or any other apps that use safety net make sure you login first then root. You can't logout or else you'll have to unroot and log back in.
Click to expand...
Click to collapse
Do you think that will be fixed soon with a newer version of SuperSU, or some "root hider" apps? The idea of running a phone without root is absurd/offensive/rediculous IMO, but I don't want to be denied the ability to run certain apps because the developers have the rediculous idea that running without root should be "OK" to ordinary users? This idea is extremely offensive to me!!!
Guys, I wonder why the OP is "Account currently disabled"? I hate running without root, but, it seems a bit early and not all the problems have been worked out yet, such as TWRP not accessing SDCARD yet - I think I was a little premature buying my Moto G5 Plus as we don't really have "stable" release custom ROMs or fully functioniong TWRP and to even root we have to rely on some not well known sources for kluged files to make SU work?
So today with some testers i managed to make root on OnePlus 7T, I want to specify that 95% of the work was done by @topjohnwu (Magisk creator). For now you should use only Magisk Canary files
I will explain 2 different guides:
First Root Guide:
This guide is for a specific rom version, so you will need to use a specific patched boot.img
- Download the patched_boot.img
- Reboot your device in bootloader-fastboot mode
- Flash the patched_boot.img in the boot partition:
Code:
fastboot flash boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
Second Root Guide:
This guide is more generic than the first one, you should use this one if you are unable to find a specific patched boot.img
- Download a patched_boot.img (you should try with the latest one)
- Reboot your device in bootloader-fastboot mode
- Boot the patched_boot.img:
Code:
fastboot boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
- Click on Install, then direct install and wait the end of the process
- Reboot the device
Third Root Guide:
Guide by @gpz1100
TIPS:
Actually you should use only Magisk canary files Magisk 20.3
You can get the stock boot images from the fastboot rom: https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
Actually i'm using magisk manager canary and magisk canary debug to patch the boot.img, I don't recommend updating magisk, if you don't want to see the updates install the normal magisk manager
Magisk 20.3 fully support OnePlus 7T and 7T Pro
HOW TO UPDATE a ROM and KEEP ROOT:
Before all Disable all magisk modules
Be sure to use Canary Magisk Manager and Canary Magisk (debug)
You can update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Download:
Patched/Stock Boot Images: https://www.androidfilehost.com/?w=files&flid=300177
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Donations:
Credits:
@RohanAJoshi
Flashed and working flawless.
Really thanks for this.
Awesome work bro.
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
nick_22 said:
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
Click to expand...
Click to collapse
Done, i uploaded them using ftp and i forgot to move the files in the right folder
Working, thanks a lot @mauronofrio
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
See OP, its clearly mentioned there. You have to flash this via fastboot and not any custom recovery. Firstly setup adb on your PC and then check the commands. Its very easy. Do some googling and still if its difficult for you, come back and ask.
jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
Welcome to the android scene, reminds me of the old psx scene
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
Get your stock boot.img from 1st post.
Reboot to bootloader.
And do this command
fastboot flash boot boot.img
fastboot reboot
Device will boot unrooted.
---------- Post added at 05:58 AM ---------- Previous post was at 05:55 AM ----------
jesrani;80464121 [user=4712355 said:
@mauronofrio[/user], thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
RohanAJoshi said:
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
Click to expand...
Click to collapse
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
jesrani said:
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
In older devices like OP5T it happens like this, not in newer devices. OP7T has seamless updates, its installs while device is turned on in second partition.
nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
jesrani said:
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
jesrani said:
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
Canary debug, don't update it
Help please. I have returned to Android after 5years with OnePlus 7t and trying to root it. I am trying this method but not being able to successfully root it. Steps I have tried
Went to fastboot mode by restarting the phone but I don't get an option to install the patched image file. And even boatloader is locked. Do I need to unlock the bootloader. And I unlock will I loose my data. Sorry for silly question I have completely forgot about Android.
Thanks, rooted successfully
?
To be honest need video tutorial asap?
mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Ok. Got it. So, I have already booted back to unrooted mode now. And I cant wipe my data again. Thanks for your response.
Resources:
1. TWRP img: https://drive.google.com/open?id=1M04t6uspBLDJfHXFfJQeOzqDRSk56UMF
2. TWRP zip: https://drive.google.com/open?id=16IbNJJspaqqimqdLeNGBnkRoj3rZ0zcR
Copy all into adb folder
Proceed:
1. Connect the device in fastboot mode, enter the command cmd: fastboot boot TWRP-3.3.1-1004-ASUS_ROG2-CN-wzsx150.img (boot, not flash boot, I do not write missing)
The machine will automatically boot into twrp
2. In Twrp choose Advanced => ADB sideload, enter the command: adb sideload TWRP-3.3.1-1004-ASUS_ROG2-CN-wzsx150.zip
3. Reboot into Twrp, select Advanced => Install root
Done, start and enjoy!
My telegram
https://t.me/rogphonevietnam2
That's work only on CN rom or also on WW?
dracoolia said:
That's work only on CN rom or also on WW?
Click to expand...
Click to collapse
All
Any other tested this method? Could someone else confirm this. Ty
iampatricktan said:
Any other tested this method? Could someone else confirm this. Ty
Click to expand...
Click to collapse
Working well
This works great! Thanks!
You install root or flash zip magisk 20?
dungnghien said:
You install root or flash zip magisk 20?
Click to expand...
Click to collapse
You just helped me on Telgram...Im rich...LOL. Im thinking magisk 20 should work. What do i know though?
suzook said:
You just helped me on Telgram...Im rich...LOL. Im thinking magisk 20 should work. What do i know though?
Click to expand...
Click to collapse
Oh. You can try 20!
suzook said:
I tried this...it booted fine with root, and wifi working, but the next reboot, slot was corrupt. I will try again
Click to expand...
Click to collapse
I think i will let someone else try 1st....LOL
dungnghien said:
Oh. You can try 20!
suzook said:
I tried this...it booted fine with root, and wifi working, but the next reboot, slot was corrupt. I will try again
Click to expand...
Click to collapse
Click to expand...
Click to collapse
my pc dont find fastboot mode
i try connect my rog phone 2 to pc and tell me waiting a device, anyone know how fix? thks
I have same pronlem, when I connect my phone on my laptop in adb that's work but when I'm in fastboot mode that's not find my phone any one can hepl, thx a lot
thermaldude said:
i try connect my rog phone 2 to pc and tell me waiting a device, anyone know how fix? thks
Click to expand...
Click to collapse
dracoolia said:
I have same pronlem, when I connect my phone on my laptop in adb that's work but when I'm in fastboot mode that's not find my phone any one can hepl, thx a lot
Click to expand...
Click to collapse
You guys using the side usb port?
suzook said:
You guys using the side usb port?
Click to expand...
Click to collapse
For me that's work well now I forget to edit PATH??, but I have a question when I install TWRP I dont active SU in advanced in TWRP, I install magisk zip to root my phone, but... because of that I lost TWRP, if I install again TWRP in fastboot I loose my root or not? Because both are boot image
dracoolia said:
For me that's work well now I forget to edit PATH??, but I have a question when I install TWRP I dont active SU in advanced in TWRP, I install magisk zip to root my phone, but... because of that I lost TWRP, if I install again TWRP in fastboot I loose my root or not? Because both are boot image
Click to expand...
Click to collapse
You lost twrp after flashing magisk.zip? That doesnt make sense
suzook said:
You lost twrp after flashing magisk.zip? That doesnt make sense
Click to expand...
Click to collapse
I was on ww 1908.12 with twrp installed. I then updated to magisk 20.0 by flashing the zip through twrp. This caused me to lose twrp and I get an error unbootable slot when trying to enter into recovery now. Since there is no dev support I figure I'm not missing much without it. I was able to update to the latest firmware ww1908.25 by downloading the file from the op gdrive link. Moving it to root then apply update. Go to magisk install to inactive slot and reboot.
sesz said:
I was on ww 1908.12 with twrp installed. I then updated to magisk 20.0 by flashing the zip through twrp. This caused me to lose twrp and I get an error unbootable slot when trying to enter into recovery now. Since there is no dev support I figure I'm not missing much without it. I was able to update to the latest firmware ww1908.25 by downloading the file from the op gdrive link. Moving it to root then apply update. Go to magisk install to inactive slot and reboot.
Click to expand...
Click to collapse
What you did is something different....you absolutely will lose twrp with an ota
Yeah same message, when I have installed zip of magisk with TWRP everything work well with magisk, but now when I want to boot on recovery I have big message in red
ERROR UNBOOTABLE SLOT
dracoolia said:
Yeah same message, when I have installed zip of magisk with TWRP everything work well with magisk, but now when I want to boot on recovery I have big message in red
ERROR UNBOOTABLE SLOT
Click to expand...
Click to collapse
Get back to Fastboot and run this command
fastboot set_active other
^ Then hit enter.
You can go back to recovery by
fastboot reboot recovery
sesz said:
I was on ww 1908.12 with twrp installed. I then updated to magisk 20.0 by flashing the zip through twrp. This caused me to lose twrp and I get an error unbootable slot when trying to enter into recovery now. Since there is no dev support I figure I'm not missing much without it. I was able to update to the latest firmware ww1908.25 by downloading the file from the op gdrive link. Moving it to root then apply update. Go to magisk install to inactive slot and reboot.
Click to expand...
Click to collapse
can you provide me with a link for the version 25 for ww?
and also i tried the method given in the first post but i still cannot connect wifi on my phone. I am on verion 21