Related
Hi all,
I'm on OpenBeta9 and have /data formatted with f2fs. Couldn't find a clear indication of what TWRP version (and SuperSU) is compatible with this setup.
Could you please assist?
Thanks
Normaly, twrp-3.0.2-1.28-oneplus3 and SR5-SuperSU-v2.78-SR5-20161130091551. But in my case, i had a encrypt problem with the recovery
MrSkyFail said:
Normaly, twrp-3.0.2-1.28-oneplus3 and SR5-SuperSU-v2.78-SR5-20161130091551. But in my case, i had a encrypt problem with the recovery
Click to expand...
Click to collapse
Hi MrSkyFail, thanks for the reply.
Was your problem preventing you to use TWRP normally, or something I could work around?
Also, would you have download links? SuperSU should be easy for me to find, by TWRP is always a mess, since it's a mod version.
Thanks
andrea.ippo said:
Hi MrSkyFail, thanks for the reply.
Was your problem preventing you to use TWRP normally, or something I could work around?
Also, would you have download links? SuperSU should be easy for me to find, by TWRP is always a mess, since it's a mod version.
Thanks
Click to expand...
Click to collapse
For TWRP : http://forum.xda-developers.com/devdb/project/dl/?id=21835
Yeah, i couldn't decrypt my phone in recovery. I try with beta 9 official i lose my TWRP recovery for offical recovery and works.
---------- Post added at 01:27 PM ---------- Previous post was at 01:25 PM ----------
Look this : http://forum.xda-developers.com/oneplus-3/how-to/rom-oxygenos-beta-9-nougat-update-t3519069
MrSkyFail said:
For TWRP : http://forum.xda-developers.com/devdb/project/dl/?id=21835
Yeah, i couldn't decrypt my phone in recovery. I try with beta 9 official i lose my TWRP recovery for offical recovery and works.
---------- Post added at 01:27 PM ---------- Previous post was at 01:25 PM ----------
Look this : http://forum.xda-developers.com/oneplus-3/how-to/rom-oxygenos-beta-9-nougat-update-t3519069
Click to expand...
Click to collapse
I found out that if you only flash OB9 from TWRP, even though you formatted your /data partition and is f2fs, if you don't flash SU before your first boot, your phone becomes encrypted and you will have TWRP pin issues.
The other issue I found was that if you flash OB9, then try flashing SU (I'm running SR5 right now), it doesn't want to boot. The only way I got it to work is after you flash OB9, Mount /system and delete a couple of google apps (for me, I deleted Calendar and gmail; you can download these after you boot up from playstore), then flash SU, then reboot, and profit.
So order of things for me:
1. Wipe (make sure /data is f2fs)
2. Flash OB9
3. Flash TWRP (modded 1-28)
4. Reboot to recovery (you may have to do a manual power off then volume down + power on)
5. Mount /system and delete calendar and gmail apps
6. Flash SU (SR5; I think there's a newer version but I haven't tried it with the new one).
7. Wipe Dalvik and Cache
8. Reboot System
If everything is done correctly, your phone will reboot twice.
You will have dm-verity and unlocked bootloader warning screens.
First boot takes about 3-5 min.
Why would deleting a couple google apps be necessary? I don't get it. And this applies for having cache f2fs too I assume?
Stupifier said:
Why would deleting a couple google apps be necessary? I don't get it. And this applies for having cache f2fs too I assume?
Click to expand...
Click to collapse
You may only need to mount /system before you flash SU. I can't find the post at the moment but this was mentioned (delete a few apps) when OB8 first came around.
Only the /data partition has F2FS support on stock OB8 and OB9.
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.
Hello XDA, I am trying to figure out all the steps to get mainly Twrp, Magisk, Viper and, Substratum working correctly without any hiccups. I have been reading the forums all day and trying to get all the files necessary to get all that working and the files to revert to stock if it doesn't work. I know after the Bootloader is unlocked I won't be able to relock it due to no Moto signed boot images. I just don't want to brick it and be here with other problems later.
So far I have done the following
1. Installed ADB and Fastboot + Drivers
2. Done everything to get the code to unlock bootloader
3. Downloaded the files to flash twrp from (https://forum.xda-developers.com/z2-force/development/twrp-3-1-1-0-moto-z2-force-nash-t3687421)
4. Downloaded the latest stock NCX26.122-59-8 to extract the boot img and patch it with Magisk manager from (https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859)
I think I have everything I need to get it rooted. Here's where I get kinda confused. My phone (XT1789-03 Sprint) is on NCXS26.122-59-8-11 November patch (I think the S is for sprint lol). Would It be okay to flash the Magisk patched boot img from the one I downloaded after I unlock the bootloader? Is Twrp necessary? Is there anything else I need to know about? Thanks in advance.
This forum just died? What the hell noone helps anymore???
Sent from my XT1650 using Tapatalk
TWRP is official now. Download the bootable image from https://twrp.me/motorola/motorolamotoz2force.html and the corresponding zip. Boot to twrp and flash the zip. Flash Magisk and install what you want that needs root. Hint: I'd advise the Viper4Android from Magisk modules in the magisk app.
Uzephi said:
Boot to twrp and flash the zip.
Click to expand...
Click to collapse
What do you mean by this? Fastboot flash TWRP, but then flash what zip?
breakerfall said:
What do you mean by this? Fastboot flash TWRP, but then flash what zip?
Click to expand...
Click to collapse
Do NOT flash the twrp img. "Fastboot boot imagename.img" then flash the twrp zip if you wish to have it as your recovery. You can find both on twrp.me.
This hard.. even with instructions u don't know what to flash where and what it will achieve lol. I just want unlock and root. What's the easiest way to do that on sprint z2 force?
So far I understand u need to install twrp to root with magisk, then use twrp to flash magisk Img, then boot up install magisk apk and u should be rooted. Hope I've got that all right.
But do any of the images on this site also unlock gsm on sprint or TMobile?
Sent from my Moto Z (2) using Tapatalk
Uzephi said:
Do NOT flash the twrp img. "Fastboot boot imagename.img" then flash the twrp zip if you wish to have it as your recovery. You can find both on twrp.me.
Click to expand...
Click to collapse
Not trying to be a **** here, but what exactly do you mean by imagename.img? .. the twrp.img file? and if I don't want TWRP as recovery, then are you saying that it will remain stock if I don't flash the twrp.zip file?
I recently did this on an Essential phone, and the process was: fastboot flash TWRP.img, reboot to TWRP (recovery), flash stock boot.img, then flash magisk.zip.
The last phone I rooted/rommed before that was a Nexus 6, and **** was different then.
breakerfall said:
Not trying to be a **** here, but what exactly do you mean by imagename.img? .. the twrp.img file? and if I don't want TWRP as recovery, then are you saying that it will remain stock if I don't flash the twrp.zip file?
I recently did this on an Essential phone, and the process was: fastboot flash TWRP.img, reboot to TWRP (recovery), flash stock boot.img, then flash magisk.zip.
The last phone I rooted/rommed before that was a Nexus 6, and **** was different then.
Click to expand...
Click to collapse
Yes, just boot it. If you flash, your phone will boot to recovery. Don't flash the TWRP image!!
---------- Post added at 07:25 PM ---------- Previous post was at 07:24 PM ----------
jmagi said:
So far I understand u need to install twrp to root with magisk, then use twrp to flash magisk Img, then boot up install magisk apk and u should be rooted. Hope I've got that all right.
Click to expand...
Click to collapse
You don't flash the TWRP.img file!!! You fastboot boot it. It will temp boot to twrp
Uzephi said:
Yes, just boot it. If you flash, your phone will boot to recovery. Don't flash the TWRP image!
Click to expand...
Click to collapse
Ahhhh!
Fastboot boot TWRP.img, then just flash the magisk.zip in TWRP, right?
Thank you!
Also, @jmagi -- you shouldn't have to manually install the magisk apk. Flashing the magisk.zip in TWRP should result in a Magisk app in your "all apps" next time you boot.
Uzephi said:
Yes, just boot it. If you flash, your phone will boot to recovery. Don't flash the TWRP image!!
---------- Post added at 07:25 PM ---------- Previous post was at 07:24 PM ----------
You don't flash the TWRP.img file!!! You fastboot boot it. It will temp boot to twrp
Click to expand...
Click to collapse
Ohhh thats how it works. So i dont have to install twrp from playstore?
Sent from my Moto Z (2) using Tapatalk
jmagi said:
Ohhh thats how it works. So i dont have to install twrp from playstore?
Click to expand...
Click to collapse
No, you don't
Uzephi said:
No, you don't
Click to expand...
Click to collapse
Ok got it thank you. So fastboot boot twrp, and from twrp flash magisk.img then run magisk after bootup.
I too havent rooted a phone since droid4 which was just doubleclick a bat file lol. All this twrp stuff is new to me. Hope i got it right. Love this phone. Might get another one soon and the qwerty keyboard mod is expected on amazon within a couple months. Only reason i upgraded.
Sent from my Moto Z (2) using Tapatalk
jmagi said:
Ok got it thank you. So fastboot boot twrp, and from twrp flash magisk.img then run magisk after bootup.
I too havent rooted a phone since droid4 which was just doubleclick a bat file lol. All this twrp stuff is new to me. Hope i got it right. Love this phone. Might get another one soon and the qwerty keyboard mod is expected on amazon within a couple months. Only reason i upgraded.
Click to expand...
Click to collapse
Some people had issues and needed to wipe user data after flashing magisk
I have a USA variant, just got the Oreo / EMUI 8.0 update. Everything is stock.
I got my bootloader unlock code from Honor support (via the Google forms the USA Support tweeted out).
All guides for unlocking the bootloader and rooting are for Nugat (7.0).
I am wondering a few things.
1) Has anyone unlocked/rooted Oreo? What steps did you take? What TWRP version are you using (a link is preferable, if you have one)? Did you use the multi-tool, or directly with adb?
2) What root solution did you use? I prefer SU over magisk (for the ability to use xposed), but I heard SU isn't working, only magisk? What version did you use?
3) What backup system do you use when your phone will wipe everything for unlocking the bootloader? Is the Huawei stock "Backup" app that it comes with any good? Any better ones to use?
Basically there's no walkthrough for rooting with the current setup. It'd be awesome if someone wrote one that was basically:
- Backup using W method (backup app, or alternative).
- Unlock bootloader using X method (adb/multi-tool/whatever).
- Root using Y method (TWRP version, SU or magisk, and version numbers)
- Do Z activity (anything else to flash after? xposed? etc.?)
Any thoughts appreciated.
arebelspy said:
I have a USA variant, just got the Oreo / EMUI 8.0 update. Everything is stock.
I got my bootloader unlock code from Honor support (via the Google forms the USA Support tweeted out).
All guides for unlocking the bootloader and rooting are for Nugat (7.0).
I am wondering a few things.
1) Has anyone unlocked/rooted Oreo? What steps did you take? What TWRP version are you using (a link is preferable, if you have one)? Did you use the multi-tool, or directly with adb?
2) What root solution did you use? I prefer SU over magisk (for the ability to use xposed), but I heard SU isn't working, only magisk? What version did you use?
3) What backup system do you use when your phone will wipe everything for unlocking the bootloader? Is the Huawei stock "Backup" app that it comes with any good? Any better ones to use?
Basically there's no walkthrough for rooting with the current setup. It'd be awesome if someone wrote one that was basically:
- Backup using W method (backup app, or alternative).
- Unlock bootloader using X method (adb/multi-tool/whatever).
- Root using Y method (TWRP version, SU or magisk, and version numbers)
- Do Z activity (anything else to flash after? xposed? etc.?)
Any thoughts appreciated.
Click to expand...
Click to collapse
Already covered in this thread.
https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500
mrmazak said:
Already covered in this thread.
https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500
Click to expand...
Click to collapse
That didn't even cover a fraction of the questions I posted. It *maybe* gave the relevant TWRP build, though even that is in question, as one of the most recent posts was "I couldn't get any of the TWRP versions listed in this thread to work fully. " and suggesting something else.
I'm curious if anyone has actually rooted stock 8.0 and what process they used.
arebelspy said:
That didn't even cover a fraction of the questions I posted. It *maybe* gave the relevant TWRP build, though even that is in question, as one of the most recent posts was "I couldn't get any of the TWRP versions listed in this thread to work fully. " and suggesting something else.
I'm curious if anyone has actually rooted stock 8.0 and what process they used.
Click to expand...
Click to collapse
It also said backup partitions when in twrp image mount, and flash magisk 16 for root.
I'm about to try this same exact thing the twrp Oreo thread is a little confusing.
K easy part done bootloader unlocked
Update: installed twrp. Did a few backups. Flashed magisk. Rooted now restoring apps in titanium backup. Adaway finally and going to clean up system. ? Safety net passes. Just a little confused on how to restore if I end up in a boot loop. I'm trying to backup still in twrp. But can't backup data and I don't see boot.img to backup. So yeah I'm scared.
arebelspy said:
That didn't even cover a fraction of the questions I posted. It *maybe* gave the relevant TWRP build, though even that is in question, as one of the most recent posts was "I couldn't get any of the TWRP versions listed in this thread to work fully. " and suggesting something else.
I'm curious if anyone has actually rooted stock 8.0 and what process they used.
Click to expand...
Click to collapse
I had posted that. Use this TWRP. Flash Magisk 16 through TWRP. Enjoy root.
---------- Post added at 11:45 PM ---------- Previous post was at 11:41 PM ----------
allrockedout said:
K easy part done bootloader unlocked
Update: installed twrp. Did a few backups. Flashed magisk. Rooted now restoring apps in titanium backup. Adaway finally and going to clean up system. Safety net passes. Just a little confused on how to restore if I end up in a boot loop. I'm trying to backup still in twrp. But can't backup data and I don't see boot.img to backup. So yeah I'm scared.
Click to expand...
Click to collapse
Flashing kernel.img and system.img from the Oreo update.zip should completely fix a bootloop/brick. I had messed around and bootlooped one of mine, and had to extract those .img files to flash them through fastboot to restore my phone. It will erase the system though so a backup of data through Titanium Backup should be safe.
ryang872 said:
I had posted that. Use this TWRP. Flash Magisk 16 through TWRP. Enjoy root.
---------- Post added at 11:45 PM ---------- Previous post was at 11:41 PM ----------
Flashing kernel.img and system.img from the Oreo update.zip should completely fix a bootloop/brick. I had messed around and bootlooped one of mine, and had to extract those .img files to flash them through fastboot to restore my phone. It will erase the system though so a backup of data through Titanium Backup should be safe.
Click to expand...
Click to collapse
Where can I get system.img and kernel.img can you share it. I'm barely able to reboot keeps rebooting and booting into safe mode. Takes me like 10 minutes to boot to system. can barely get into twrp
allrockedout said:
Where can I get system.img and kernel.img can you share it. I'm barely able to reboot keeps rebooting and booting into safe mode. Takes me like 10 minutes to boot to system. can barely get into twrp
Click to expand...
Click to collapse
Gonna upload them now. I'll edit this post when they're finished. Did you have root before updating to Oreo?
ryang872 said:
Gonna upload them now. I'll edit this post when they're finished. Did you have root before updating to Oreo?
Click to expand...
Click to collapse
No I waited for Oreo before I rooted. I just rebooted again and booted back to system fine. I made a bunch of backups in twrp. But there useless if you don't have booted.img system and data.
allrockedout said:
No I waited for Oreo before I rooted. I just rebooted again and booted back to system fine. I made a bunch of backups in twrp. But there useless if you don't have booted.img system and data.
Click to expand...
Click to collapse
there is no "boot.img" on oreo.
the traditional boot.img has been split into 2 partitions. kernel.img and ramdisk.img.
mrmazak said:
there is no "boot.img" on oreo.
the traditional boot.img has been split into 2 partitions. kernel.img and ramdisk.img.
Click to expand...
Click to collapse
So we need kernel.img ramdisk.img which is boot. Than we need system and data. How do you flash the kernel and ramdisk when in twrp? I'm guessing ramdisk we select recovery ramdisk...and kernel? I got system and data backed up
Flashing kernel.img through "fastboot flash boot kernel.img" absolutely solved my bootloop/brick problem. I am completely new to Huawei phones so if I'm wrong please don't let me spread misinformation.
---------- Post added at 12:43 AM ---------- Previous post was at 12:41 AM ----------
allrockedout said:
So we need kernel.img ramdisk.img which is boot. Than we need system and data. How do you flash the kernel and ramdisk when in twrp? I'm guessing ramdisk we select recovery ramdisk...and kernel? I got system and data backed up
Click to expand...
Click to collapse
You'd need to flash kernel as boot through fastboot(fastboot flash boot kernel.img). TWRP would be ramdisk (fastboot flash recovery_ramdisk *****.img). System and Data backed up through TWRP can be restored through TWRP. At least those worked for me in restoring a bootloop/brick.
---------- Post added at 01:00 AM ---------- Previous post was at 12:43 AM ----------
allrockedout said:
Where can I get system.img and kernel.img can you share it. I'm barely able to reboot keeps rebooting and booting into safe mode. Takes me like 10 minutes to boot to system. can barely get into twrp
Click to expand...
Click to collapse
system.img kernel.img
EDIT: This is for L34 update.zip. I'm going out on a limb by assuming that all honor 7x/mate se versions are the same minus the modem_***.img files. USE AT YOUR OWN RISK.
allrockedout said:
So we need kernel.img ramdisk.img which is boot. Than we need system and data. How do you flash the kernel and ramdisk when in twrp? I'm guessing ramdisk we select recovery ramdisk...and kernel? I got system and data backed up
Click to expand...
Click to collapse
Each partition is it's own. Kernel is kernel, ramdisk is ramdisk, etc.
Recovery_ramdisk is recovery_ramdisk
I preferred to make each partition backup as images. Using adb shell and DD commands.
I know it is not in this thread. But in the "(nougat) twrp complete" thread.
This is linked in I believe post two. Where it describes making backup useing DD.
But the partitions are different in oroe, so need to use different codes as in that thread.
I just posted almost same thing yesterday with the links.
Use this guide to make back up. But substitute the partition layout from the following link
Oreo layout
I might be putting together a script that does the backup form you . And put it into a zip file that you run as a twrp install.
I like that idea. Now I said it out load, yeah I like it
I made first draft of my dd back up install.
It makes new directory on external card "twrp_backup" then makes dd copies of all 56 partitions. It takes a while to complete. , but gives you all the partitions, as they are. I added echo lines to the script to give you stautus of the backup, but the output is not shown on trwp install window. And it appears to be doing all the lines of the script at same time, not one at a time. So even if the echo commands printed output , it would be all at once.
well hold off on that statement of "it works" 30 minutes plus and still running.
No errors in current log, Adb shell ls (backup directory) shows all partitions. But mtp only showing 42 out of 56.
It appears to be hanging somewhere.
Will update when I find it.
update..
It worked. All 56 partitions backed up. took over an hour. then I realized I had internal storage full of junk. Userdate backup took 23GB.
as long as your data is not so full, should be better time.
maybe someone else can help edit it to be better script.
completed recovery log attached. Truncated to remove screen timeout (sleep and wake messages)
mrmazak said:
I made first draft of my dd back up install.
It makes new directory on external card "twrp_backup" then makes dd copies of all 56 partitions. It takes a while to complete. , but gives you all the partitions, as they are. I added echo lines to the script to give you stautus of the backup, but the output is not shown on trwp install window. And it appears to be doing all the lines of the script at same time, not one at a time. So even if the echo commands printed output , it would be all at once.
well hold off on that statement of "it works" 30 minutes plus and still running.
No errors in current log, Adb shell ls (backup directory) shows all partitions. But mtp only showing 42 out of 56.
It appears to be hanging somewhere.
Will update when I find it.
maybe someone else can help edit it to be better script.
Click to expand...
Click to collapse
To return to stock recovery and factory reset what do I restore? Do I need to wipe anything?
allrockedout said:
To return to stock recovery and factory reset what do I restore? Do I need to wipe anything?
Click to expand...
Click to collapse
none of those would be stock recovery. Because in order to have made that backup, you would have been on twrp. So the backup would be also twrp.
need to get the stock oreo recovery from extracting the recovery_ramdisk from update.app. update.app is in the update.zip of your oreo update. The main zip , not the "public" or "hw" one.
once you have the image. select install menu in twrp. change to install image. And install to "recovery ramdisk" also can be done with fastboot.
mrmazak said:
none of those would be stock recovery. Because in order to have made that backup, you would have been on twrp. So the backup would be also twrp.
need to get the stock oreo recovery from extracting the recovery_ramdisk from update.app. update.app is in the update.zip of your oreo update. The main zip , not the "public" or "hw" one.
once you have the image. select install menu in twrp. change to install image. And install to "recovery ramdisk" also can be done with fastboot.
Click to expand...
Click to collapse
K im downloading the update.zip now from firmware finder. I want to do another clean install magisk is force closing now. I'm using the p10 lite twrp.
---------- Post added at 10:13 AM ---------- Previous post was at 09:39 AM ----------
mrmazak said:
none of those would be stock recovery. Because in order to have made that backup, you would have been on twrp. So the backup would be also twrp.
need to get the stock oreo recovery from extracting the recovery_ramdisk from update.app. update.app is in the update.zip of your oreo update. The main zip , not the "public" or "hw" one.
once you have the image. select install menu in twrp. change to install image. And install to "recovery ramdisk" also can be done with fastboot.
Click to expand...
Click to collapse
im having trouble extracting update.app i cant open it on my pc.
---------- Post added at 10:24 AM ---------- Previous post was at 10:13 AM ----------
allrockedout said:
K im downloading the update.zip now from firmware finder. I want to do another clean install magisk is force closing now. I'm using the p10 lite twrp.
---------- Post added at 10:13 AM ---------- Previous post was at 09:39 AM ----------
im having trouble extracting update.app i cant open it on my pc.
Click to expand...
Click to collapse
im downloading huawei update extractor
K I'm going to extract this
Here is stock recovery ramdisk for Honor 7x USA Oreo. https://drive.google.com/file/d/1IylCAhGs304boVkSXnSRrQQ1B5ozHwcX/view?usp=drivesdk
I haven't tested it yet. Going to flash in twrp. Hopefully boot back into stock recovery and factory reset.
I also extracted kernel.img.
I successfully flashed kernel and ramdisk recovery. I rebooted back into stock recovery. Going to try factory reset now.
?
Wouldnt boot up.
Flashed kernel.img through twrp didnt work had to flash through adb and it seems to be booting now.
HELL YEAH!! ok booted up to system now.
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.