[Rooted] Pixel 2XL and System Autoupdates? - Google Pixel 2 XL Questions & Answers

I really don't have a clue how to get auto updates via System Updates on my rooted Pixel 2 XL (Pie, Magisk 18.1).
If I check updates it replies that I already have the latest version (still from February 2019).
Is it possible to get updates via system menu on a rooted phone?
P. S. Sorry if I've missed a right thread for this topic)

b3rsus said:
I really don't have a clue how to get auto updates via System Updates on my rooted Pixel 2 XL (Pie, Magisk 18.1).
If I check updates it replies that I already have the latest version (still from February 2019).
Is it possible to get updates via system menu on a rooted phone?
P. S. Sorry if I've missed a right thread for this topic)
Click to expand...
Click to collapse
No, you will have to manually update on a rooted phone. It requires a computer but only takes a couple minutes.

murphyjasonc said:
No, you will have to manually update on a rooted phone. It requires a computer but only takes a couple minutes.
Click to expand...
Click to collapse
Is it possible to update the system without full wiping? As I remember I should put -w in the flash script, but will it update correctly and should I reinstall TWRP or Magisk in this case?

b3rsus said:
Is it possible to update the system without full wiping? As I remember I should put -w in the flash script, but will it update correctly and should I reinstall TWRP or Magisk in this case?
Click to expand...
Click to collapse
It will not wipe your phone as long as you remove the -w. Magisk and Twrp will have to be reinstalled but that's an easy process. Fastboot boot the twrp.img file. That will get you back in to twrp temporary so you can flash the twrp and magisk zip files.

murphyjasonc said:
It will not wipe your phone as long as you remove the -w. Magisk and Twrp will have to be reinstalled but that's an easy process. Fastboot boot the twrp.img file. That will get you back in to twrp temporary so you can flash the twrp and magisk zip files.
Click to expand...
Click to collapse
Is it any difference with the sideload method?

b3rsus said:
Is it any difference with the sideload method?
Click to expand...
Click to collapse
Mostly personal preference.. if you use the side load method you need to download the ota file instead of the full image. I personally prefer flashing the whole image in fastboot. In my experience there is less room for user error but that's my opinion.

murphyjasonc said:
Mostly personal preference.. if you use the side load method you need to download the ota file instead of the full image. I personally prefer flashing the whole image in fastboot. In my experience there is less room for user error but that's my opinion.
Click to expand...
Click to collapse
Thank you very much!)

Probably will be useful for somebody.
How to update system on a rooted Pixel 2 XL with TWRP.
Code:
[LIST=1]
[*]Download OTA file, TWRP.zip and Magisk.zip to the phone
[*]Reboot to TWRP, install OTA archive
[*]Reboot to Bootloader
[*]fastboot boot twrp.img
[*]Install TWRP.zip and Magisk.zip
[*]Power off system from TWRP
[*]Run!
[/LIST]

b3rsus said:
Is it possible to update the system without full wiping? As I remember I should put -w in the flash script, but will it update correctly and should I reinstall TWRP or Magisk in this case?
Click to expand...
Click to collapse
remove the -w from the bat file

wrecklesswun said:
remove the -w from the bat file
Click to expand...
Click to collapse
This!!

Related

How Can Install Montly Updates without loose Root and Custom Recovery

Hi dudes! Im trying to find a way to install Monthly Updates without loose the root and the custom recovery, some body can tell me how? Because im really want update to Oreo but i want be root user and dont have to make a clean install system every month... exist the way? Please help.... And Thanks!
What I do is flash all the updated partition images individually using "fastboot flash", then let it boot and settle for a few minutes (at the very least until the "performing updates" notification completes).
I then reboot into bootloader and from there boot into TWRP (without installing it) using "fastboot boot twrp.img" and then reinstall Magisk zip. None of Magisk's settings or modules are lost by doing it this way.
If you uninstall Magisk before updating the system, you risk losing its settings.
You can use Flashfire.
nowster said:
What I do is flash all the updated partition images individually using "fastboot flash", then let it boot and settle for a few minutes (at the very least until the "performing updates" notification completes).
I then reboot into bootloader and from there boot into TWRP (without installing it) using "fastboot boot twrp.img" and then reinstall Magisk zip. None of Magisk's settings or modules are lost by doing it this way.
If you uninstall Magisk before updating the system, you risk losing its settings.
Click to expand...
Click to collapse
Okey, but using adb?
fnldstntn said:
You can use Flashfire.
Click to expand...
Click to collapse
How dude? Can you tech me please?
Aijen said:
How dude? Can you tech me please?
Click to expand...
Click to collapse
https://youtu.be/WxWRYnzI1O4
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Yes, you can use TWRP's "Advanced" adb sideload feature to install Magisk zip.
"adb" only works when Android is running (or some recovery images are running). When the phone is in bootloader mode the tool you need is "fastboot".
fnldstntn said:
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Click to expand...
Click to collapse
Thanks a lot! I will tried to do it!
fnldstntn said:
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Click to expand...
Click to collapse
Are you do that method without problems?
Aijen said:
Are you do that method without problems?
Click to expand...
Click to collapse
Yes it worked for me. But if you have twrp make a nandroid backup.
fnldstntn said:
Yes it worked for me. But if you have twrp make a nandroid backup.
Click to expand...
Click to collapse
Another thing....the last. Did you maintain the Custom Recovery or Flash it again?
fnldstntn said:
https://youtu.be/WxWRYnzI1O4
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Click to expand...
Click to collapse
dude! one last need reflash Magisk every time the OTA comes or Magisk survival the OTA flash with Magisk? THANKS A LOT WORKS!!!!
Aijen said:
Another thing....the last. Did you maintain the Custom Recovery or Flash it again?
Click to expand...
Click to collapse
i dont remember
Aijen said:
dude! one last need reflash Magisk every time the OTA comes or Magisk survival the OTA flash with Magisk? THANKS A LOT WORKS!!!!
Click to expand...
Click to collapse
i dont know.
Aijen said:
dude! one last need reflash Magisk every time the OTA comes or Magisk survival the OTA flash with Magisk?
Click to expand...
Click to collapse
Magisk embeds itself in the boot partition. This prevents OTA from working.
Replacing the stock recovery partition also stops OTA from working.
The only reliable way to upgrade is by flashing the partitions again from the new factory image zip file, then reinstalling TWRP and Magisk afterwards.
fnldstntn said:
You can use Flashfire.
Click to expand...
Click to collapse
Any ideas what will happen to ElementalX after flashing OTA using Flashfire?
zo1021 said:
Any ideas what will happen to ElementalX after flashing OTA using Flashfire?
Click to expand...
Click to collapse
Using the logic need to reflash it again
nowster said:
Magisk embeds itself in the boot partition. This prevents OTA from working.
Replacing the stock recovery partition also stops OTA from working.
The only reliable way to upgrade is by flashing the partitions again from the new factory image zip file, then reinstalling TWRP and Magisk afterwards.
Click to expand...
Click to collapse
Sounds logic to me....
FlashFire is saying that the update will likely fail because the OTA update is a block level update. Suggestions on how to get around this?

How to update android on customized kernel?

I using pixel 2xl running android p with kiriskura kernel.
It’s can’t update android via ota.
Does it has other way to update without wipe data ?
HushCha said:
I using pixel 2xl running android p with kiriskura kernel.
It’s can’t update android via ota.
Does it has other way to update without wipe data ?
Click to expand...
Click to collapse
Use the search button, there even is an own thread for this here. Don't expect to get the information spoon-fed :laugh:
Download the ota zip file from Google and flash it via twrp.
Afterwards flash kernel, twrp and magisk BEFORE REBOOT
Sui77 said:
Download the ota zip file from Google and flash it via twrp.
Afterwards flash kernel, twrp and magisk BEFORE REBOOT
Click to expand...
Click to collapse
Twrp, kernel, then magisk is the proper order. Me, personally, I prefer to flash factory images with -w removed from flash-all.bat. It's always been reliable for me.
DuckRuckus said:
Twrp, kernel, then magisk is the proper order. Me, personally, I prefer to flash factory images with -w removed from flash-all.bat. It's always been reliable for me.
Click to expand...
Click to collapse
I agree I flash factory image now that twrp decrpts I then boot twrp img and flash magisk then I'm all set. I don't use a custom kernel.
HushCha said:
I using pixel 2xl running android p with kiriskura kernel.
It’s can’t update android via ota.
Does it has other way to update without wipe data ?
Click to expand...
Click to collapse
I use deuces script. It works great for me every time I upgrade.
Whats best about it is it upgrades both the slots. A lot of people mess up side a/side b and hork their phones. Deuces script fixes their installs, and upgrades with it are flawless.

Help Updating to December Security Patch

I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
DarkPhoenix said:
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
Click to expand...
Click to collapse
From what I understand you can not do ADB in TWRP to install an update. What I did was download the factory images, remove -w from the flash all.bat. flashed the images and let the phone boot normally. Once I knew it was running I went to the bootloader and booted TWRP temporarily. Once that was up I flashed Magisk and then my kernel
I don't install TWRP anymore.
DarkPhoenix said:
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
Click to expand...
Click to collapse
Adding to what hatdrc said, you want the full image, not OTA, and install from your PC in fastboot mode. If you are concerned about saving your data, remove the -w switch from flash-all.bat first using a file editor like notepad. Have the twrp.zip, kernel.zip and magisk.zip files already staged. I personally don't boot to system first (but you can), I "catch" the reboot after flashing completes with the volume down button to reboot to fastboot mode. Then fastboot boot twrp.img, and then install twrp, kernel and magisk zips all in one go using the "add more zips" button in twrp. Every month when you update, you'll lose twrp, kernel and magisk, so those have to be reflashed each time. You'll soon get used to it and can do the whole thing in about 5 minutes consistently. Just make sure to pre-stage the 3 zip files on the phone before you start. Best of luck.
I tried that but couldn't get it to work. I downloaded the ADB tools again just in case there was an issue with that. I'm going to run the flash-all script again to see if I can get it to work.
DarkPhoenix said:
I tried that but couldn't get it to work. I downloaded the ADB tools again just in case there was an issue with that. I'm going to run the flash-all script again to see if I can get it to work.
Click to expand...
Click to collapse
if whats suggested above doesnt work, you can make the OTA work....download the ota to your PC, boot to Android Recovery (not TWRP), apply the ota via ADB from the menu. Whenever I have "odd" issues applying the Full image, this always works for me. Obviously you need to re-root after.
GL!
cmh714 said:
if whats suggested above doesnt work, you can make the OTA work....download the ota to your PC, boot to Android Recovery (not TWRP), apply the ota via ADB from the menu. Whenever I have "odd" issues applying the Full image, this always works for me. Obviously you need to re-root after.
GL!
Click to expand...
Click to collapse
Doesn't installing TWRP remove Android Recovery?
DarkPhoenix said:
Doesn't installing TWRP remove Android Recovery?
Click to expand...
Click to collapse
hmm, since I dont install TWRP anymore, you may be correct....still cant hurt to try
DarkPhoenix said:
Doesn't installing TWRP remove Android Recovery?
Click to expand...
Click to collapse
Yes it does. TWRP replaces the stock recovery.
Sent from my [device_name] using XDA-Developers Legacy app
v12xke said:
Adding to what hatdrc said, you want the full image, not OTA, and install from your PC in fastboot mode. If you are concerned about saving your data, remove the -w switch from flash-all.bat first using a file editor like notepad. Have the twrp.zip, kernel.zip and magisk.zip files already staged. I personally don't boot to system first (but you can), I "catch" the reboot after flashing completes with the volume down button to reboot to fastboot mode. Then fastboot boot twrp.img, and then install twrp, kernel and magisk zips all in one go using the "add more zips" button in twrp. Every month when you update, you'll lose twrp, kernel and magisk, so those have to be reflashed each time. You'll soon get used to it and can do the whole thing in about 5 minutes consistently. Just make sure to pre-stage the 3 zip files on the phone before you start. Best of luck.
Click to expand...
Click to collapse
Ok, I got the flash-all script to run. My brain shut down and I was running the wrong command.
DarkPhoenix said:
Ok, I got the flash-all script to run. My brain shut down and I was running the wrong command.
Click to expand...
Click to collapse
Well done. Now you can do it all over again in a week on Monday the 7th when the January build comes out.
v12xke said:
Well done. Now you can do it all over again in a week on Monday the 7th when the January build comes out.
Click to expand...
Click to collapse
I was updating so I could install Bootleggers rom so updating should be a lot easier lol.

Unable to flash OTA update

Hi all, I have TWRP + Magisk on my device and I am attempting to update from PQ1A.181205.006 to PQ2A.190205.001.
Steps taken
1. Downloaded the OTA from here: https://developers.google.com/android/ota#crosshatch
2. Moved the OTA to phone storage.
3. Checked SHA256 checksum matches.
4.
Code:
adb reboot recovery
5.
Code:
fastboot boot twrp-3.2.3-3-crosshatch.img
6. From TWRP > Install > OTA zip file
Fails with the attached error. I have also tried sideloading through TWRP with the same result. Has anyone hit this error or successfully flashed the OTA update through TWRP?
I have not heard of anyone successfully loading an OTA through TWRP. Either restore stock recovery (install boot.img to both slots) and sideload with the Google instructions or run the flash-all (remove the -w) to use the factory image. Either way, you ere going to be reverting to stock recovery.
P.S. Your message doesn't make sense since you say you have TWRP on your device but then are showing that you used fastboot boot to run the TWRP .img file. If TWRP was on your device, you wouldn't have to use that command. You would just have entered TWRP with the adb reboot recovery command. I am guessing you are rebooting into the bootloader screen where either you run the TWRP .img or run the flash-all.
I also thought I saw a previous post somewhere that said you cannot skip an update, so going from December to February may not work.....not sure...
But definitely you need to load the OTA via regular Recovery using adb not TWRP....
Can you install a OTA?
I thought you had to perform an ADB sideload of an OTA.
Even then I am not aware that ADB sideload works for Pixel 3xl yet.
I have been flashing the factory image with -w removed.
parakleet said:
Can you install a OTA?
I thought you had to perform an ADB sideload of an OTA.
Even then I am not aware that ADB sideload works for Pixel 3xl yet.
I have been flashing the factory image with -w removed.
Click to expand...
Click to collapse
ADB sideload works fine for the OTAs in stock recovery. That's how I've been doing mine.
On a side note, the Essential phone is the only phone I've come across so far that TWRP will flash the factory OTAs.
spotmark said:
ADB sideload works fine for the OTAs in stock recovery. That's how I've been doing mine.
On a side note, the Essential phone is the only phone I've come across so far that TWRP will flash the factory OTAs.
Click to expand...
Click to collapse
The P2XL and Nexis 6p can flash OTA's via twrp as well. Hopefully Team Win will get it sorted out for you guys as well :good:
Badger50 said:
The P2XL and Nexis 6p can flash OTA's via twrp as well. Hopefully Team Win will get it sorted out for you guys as well :good:
Click to expand...
Click to collapse
Flash them or sideload them? I never had a P2XL, but I had a Nexus 6p and I don't remember being able to flash that with the factory zips. That doesn't mean my memory isn't shot either.
spotmark said:
Flash them or sideload them? I never had a P2XL, but I had a Nexus 6p and I don't remember being able to flash that with the Factory zips. That doesn't mean my memory isn't shot either.
Click to expand...
Click to collapse
Yeah, it was possible, just not many people knew about it, but it definitely works :good:
Flashing them that is.
I went from dec to feb update no problem
hilla_killa said:
I went from dec to feb update no problem
Click to expand...
Click to collapse
Sideloading or factory image method?
I am trying to do an OTA update on my Pixel 3xl. I have TWRP installed and need to get back to stock recovery. I have the stock boot.img file and have attempted to flash with adb fastboot but I keep getting this error
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
Bootloader is unlocked
USB debugging is on
Any help would be appreciated.
Badbrad17 said:
I am trying to do an OTA update on my Pixel 3xl. I have TWRP installed and need to get back to stock recovery. I have the stock boot.img file and have attempted to flash with adb fastboot but I keep getting this error
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
Bootloader is unlocked
USB debugging is on
Any help would be appreciated.
Click to expand...
Click to collapse
Did you first extract the secondary zip file inside the factory image, and then placed the boot.img in your platform-tools folder, and the used the command..fastboot flash boot boot.img....??
Badger50 said:
Did you first extract the secondary zip file inside the factory image, and then placed the boot.img in your platform-tools folder, and the used the command..fastboot flash boot boot.img....??
Click to expand...
Click to collapse
Yes that is what I did.
Badbrad17 said:
Yes that is what I did.
Click to expand...
Click to collapse
Okay, and you are in fastboot mode and not adb from the OS as well I take it? Have you tried a different USB cable and port? If all else fails, you can flash the boot.img in twrp as well.
Badger50 said:
Okay, and you are in fastboot mode and not adb from the OS as well I take it? Have you tried a different USB cable and port? If all else fails, you can flash the boot.img in twrp as well.
Click to expand...
Click to collapse
OH I di not know I could do it in TWRP. Will try that first. thanks
Badbrad17 said:
OH I di not know I could do it in TWRP. Will try that first. thanks
Click to expand...
Click to collapse
Just make sure you flash it to the boot partition :good:
raphytaffy said:
Hi all, I have TWRP + Magisk on my device and I am attempting to update from PQ1A.181205.006 to PQ2A.190205.001.
Steps taken
1. Downloaded the OTA from here: https://developers.google.com/android/ota#crosshatch
2. Moved the OTA to phone storage.
3. Checked SHA256 checksum matches.
4.
Code:
adb reboot recovery
5.
Code:
fastboot boot twrp-3.2.3-3-crosshatch.img
6. From TWRP > Install > OTA zip file
Fails with the attached error. I have also tried sideloading through TWRP with the same result. Has anyone hit this error or successfully flashed the OTA update through TWRP?
Click to expand...
Click to collapse
I've installed 3 latest updates from twrp ...
Download the latest OTA, you have to be in stock Rom and Kernel stock ... and have last twrp on your phone... Flash OTA and twrp installer to keep twrp ... restart in twrp for magisk or restart system ... benefits
sorry for my bad english.
Badger50 said:
Just make sure you flash it to the boot partition :good:
Click to expand...
Click to collapse
How do I make sure of this? Sorry I'm a bit of a noob.
Badbrad17 said:
How do I make sure of this? Sorry I'm a bit of a noob.
Click to expand...
Click to collapse
Tap install on the twrp home screen. Then go to where you have the boot.img on your internal storage and tap image on the bottom right. Then select the "boot" partition, and swipe to install. This will return you back to stock recovery and kernel :good:
Badger50 said:
Tap install on the twrp home screen. Then go to where you have the boot.img on your internal storage and tap image on the bottom right. Then select the "boot" partition, and swipe to install. This will return you back to stock recovery and kernel :good:
Click to expand...
Click to collapse
Well I managed to do that, but now when my phone rebooted the touch screen no longer responds. Very strange. It all loads fine and I can see my screen but nothing works. I tried to go back into recovery and I get the little dead Android guy laying on his back with a red exclamation point and "No Command" below it.
Any ideas?

[GUIDE] How to Root OnePlus 7T without TWRP

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.

Categories

Resources