Hi all.
I updated to the latest version last night, but I lost my root in the process.
I tired to re-root my GP6 yet unsuccessful. Anybody manage to do it?
Thanks.
Tried how? Assuming your bootloader is unlocked, the easiest way is probably:
Unhide Magisk on your phone for now (so PixelFlasher can find it to easily automatically patch your boot.img)
Enable USB debugging if you haven't already
Grab the T2B1 beta factory image (as by T2B1 it sounds like you're on the beta), and PixelFlasher
Use PixelFlasher to extract the boot.img from the factory image (red rocket icon right of the browse bar)
With your phone connected, hit Scan in the top right of PixelFlasher, and select your Pixel in the dropdown
With the extracted boot image extracted, hit "Patch" in PixelFlasher and let it do its thing
With the patched (band-aid icon) boot image selected, hit "Flash Boot" on the right, then let it do its thing again
You can hide Magisk again at this point.
You should have root back after doing all of that. Let me know if I missed anything or if it gets stuck anywhere.
Jaitsu said:
Tried how? Assuming your bootloader is unlocked, the easiest way is probably:
Unhide Magisk on your phone for now (so PixelFlasher can find it to easily automatically patch your boot.img)
Enable USB debugging if you haven't already
Grab the T2B1 beta factory image (as by T2B1 it sounds like you're on the beta), and PixelFlasher
Use PixelFlasher to extract the boot.img from the factory image (red rocket icon right of the browse bar)
With your phone connected, hit Scan in the top right of PixelFlasher, and select your Pixel in the dropdown
With the extracted boot image extracted, hit "Patch" in PixelFlasher and let it do its thing
With the patched (band-aid icon) boot image selected, hit "Flash Boot" on the right, then let it do its thing again
You can hide Magisk again at this point.
You should have root back after doing all of that. Let me know if I missed anything or if it gets stuck anywhere.
Click to expand...
Click to collapse
Have the same Problem, no root on latest Beta,
although following the above steps ( used them in the pasta for wach beta)
Anyone with root on newest Beta?
To be fair, I'm not rooting on the latest beta, I'm still on the standard TQ1A December release - the instructions I gave should apply to any version, but it's possible T2B1 has broken something. When you open the Magisk app, does it show that Magisk isn't installed, even after flashing the patched boot image?
Jaitsu said:
To be fair, I'm not rooting on the latest beta, I'm still on the standard TQ1A December release - the instructions I gave should apply to any version, but it's possible T2B1 has broken something. When you open the Magisk app, does it show that Magisk isn't installed, even after flashing the patched boot image?
Click to expand...
Click to collapse
Yes, same thing happened to me this morning after doing the common steps to retain root after applying an OTA. I then proceeded to patch the boot image using adb but stil no root access.
Edit. It appears that no one is able to root on T2B1, as someone said in the official guide rooting pixel 6 here on XDA
Same issue, tried with PixelFlasher, manual commands, diffrent Magisk versions, but still can't get it work
Strange, and interesting. May be worth filing a bug at the official Magisk github page if anyone is willing to go through the steps necessary to help troubleshoot the problem (doing all of the above with the latest debug version of Magisk, for starters; if you report a bug using any other version the bot will automatically close your issue). I would if I were running the beta or if we had working TWRP so I could backup and restore, but I juuust got my Pixel back to the way I like it on the non-beta after a factory reset.
Jaitsu said:
Strange, and interesting. May be worth filing a bug at the official Magisk github page if anyone is willing to go through the steps necessary to help troubleshoot the problem (doing all of the above with the latest debug version of Magisk, for starters; if you report a bug using any other version the bot will automatically close your issue). I would if I were running the beta or if we had working TWRP so I could backup and restore, but I juuust got my Pixel back to the way I like it on the non-beta after a factory reset.
Click to expand...
Click to collapse
I've already posted on Reddit r\Magisk [Help] Flashed magisk pathed pathed boot image T2B1.221118.006 don't works, but maybe submitting bug would be better. Yea, TWRP would be best but still nothing for A13 (and A12 I think). I remember that there was similar issue in older updates, but Canary made it work, but... not this time
Tried all the possible ways to root the phone, either using fastboot or Pixel Flasher, but no avail. Perhaps someone could successfully do it and tell all of us how
Same issue in Pixel 6a
Guys, see https://github.com/topjohnwu/Magisk/issues/6441.
It looks like Google released corrupted boot image.
To make it work, You need to patch and flash boot image from Pixel 7.
Pixel 6 -> Pixel 7 boot image.
Pixel 6 Pro -> Pixel 7 Pro boot image.
I don't know what about Pixel 6a.
So, should we download the same latest beta for pixel 7 and extract and patch the boot image inside of it?
BAlex9601 said:
So, should we download the same latest beta for pixel 7 and extract and patch the boot image inside of it?
Click to expand...
Click to collapse
Yea, everything else stays the same. Just after upgrade, instead of patching Pixel 6 boot.img, patch the one from Pixel 7 and flash it.
I've used Pixel Flasher for factory update and then in Magisk app I've patched image and then flashed it with fastboot flash boot <patched_boot.img>.
https://twitter.com/i/web/status/1602774339224367104
Yup broken.. should have read the thread.
m_pastuszek said:
Guys, see https://github.com/topjohnwu/Magisk/issues/6441.
It looks like Google released corrupted boot image.
To make it work, You need to patch and flash boot image from Pixel 7.
Pixel 6 -> Pixel 7 boot image.
Pixel 6 Pro -> Pixel 7 Pro boot image.
I don't know what about Pixel 6a.
Click to expand...
Click to collapse
Is this true? I'm downloading it now to test it. Will update later.
UPDATE:
Apparently, flashing Pixel 7 boot.img into Pixel 6 worked like a charm. I get the root back. Thanks guy!
Thanks for the hint regarding boot.img
I'm facing aslo this issue while updating
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'slider-1.2-9152140'.
Update requires 'slider-1.2-9228550'.
Actually I'm on T1B3.221003.008
Any idea? -> flashed bootloader manually -> solved
Related
MTP does not work in TWRP on the Pixel 3 and will not work until we have time to update the TWRP MTP implementation. You may still use adb to push and pull files.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, you will need to reflash root.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
3.2.3-0: Initial release for the Pixel 3 devices
Pixel 3:
https://twrp.me/google/googlepixel3.html
https://dl.twrp.me/blueline/
Pixel 3 XL:
https://twrp.me/google/googlepixel3xl.html
https://dl.twrp.me/crosshatch/
Reserved.
You are the man! Cant believe we have TWRP this early! Just in time for the next OTA!
Thank you for this! Great work, it feels like an early Christmas!
All set up with TWRP and rooted again,,even made a back up,,,awesome job to the dev!
Thanks you!
Is anyone having the touchscreen not work after a reboot?
Archangel said:
All set up with TWRP and rooted again,,even made a back up,,,awesome job to the dev!
Click to expand...
Click to collapse
I got twrp up and running on my Pixel 3, but when try to install magisk 17.3 via twrp it says it completes but just bootloops. And I have to restore again. How did you go about it?
code_311 said:
Is anyone having the touchscreen not work after a reboot?
Click to expand...
Click to collapse
On the Pixel 2 XL touch was broken unless you used a custom kernel. I guess it's the same on 3. If you boot TWRP using fastboot it should allow touchscreen.
You would think after buying the Pixel 1, 2 and 3 I would have this whole A/B slot thing down pat but I dont LOL. That did the same thing for me too. I just rebooted into recovery and flashed TWRP again and it has been fine since. I think sometimes it switches slots and that causes the bootloop. I messed around with changing slots and I think I am on slot A and all if fine for me.
Mrnicgeuy633 said:
I got twrp up and running on my Pixel 3, but when try to install magisk 17.3 via twrp it says it completes but just bootloops. And I have to restore again. How did you go about it?
Click to expand...
Click to collapse
---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------
I had that happen I think once and I just rebooted back into TWRP and it was fine.
code_311 said:
Is anyone having the touchscreen not work after a reboot?
Click to expand...
Click to collapse
Hey guys - I'm a pixel noob and have a quick question about TWRP/Magisk.
I was rooted before TWRP came out so I flashed the stock boot images back to slots A and B. Then I followed steps 2-12 of the following article to install both Magisk and TWRP using temp TWRP. https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
My question is... when I was temp booted into TWRP, and installed the Magisk zip file, it only said that it installed to slot A. But when I was rooted before TWRP released I remember I had to flash the patched boot image to both slots. So using the process I followed, do I have one slot rooted and the other not? If so, is that a problem? Phone seems to work perfectly and root is working.
Sorry if this is a dumb question. I've always been a HTC guy but I'm trying
ktdt00 said:
Hey guys - I'm a pixel noob and have a quick question about TWRP/Magisk.
I was rooted before TWRP came out so I flashed the stock boot images back to slots A and B. Then I followed steps 2-12 of the following article to install both Magisk and TWRP using temp TWRP. https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
My question is... when I was temp booted into TWRP, and installed the Magisk zip file, it only said that it installed to slot A. But when I was rooted before TWRP released I remember I had to flash the patched boot image to both slots. So using the process I followed, do I have one slot rooted and the other not? If so, is that a problem? Phone seems to work perfectly and root is working.
Sorry if this is a dumb question. I've always been a HTC guy but I'm trying
Click to expand...
Click to collapse
No, only the current slot needs to be rooted.
Hello,
I apparently have one of these Pixel 3's that are not working with the current version of TWRP (twrp-3.2.3-0-blueline.img). Yes, I have a 3, not a 3XL. I have done these a hundred times before so I am fairly confident I am not doing anything wrong either. I get the file to load through ADB but on the reboot, it just hangs on the Google screen forever. I have left it for an hour. I have tried everything I can think of. Does anyone have any advice or is in the same situation? I just got my Pixel 3 in the mail on Friday so it's as fresh as they come. I was thinking of fully flashing the TWRP image, but I really don't think it's going to make any difference and I don't want the extra hassle of tracking down the official boot.img from the repo. I guess I will just have to wait until someone who really knows how to debug these comes across one like mine. Clearly, something has changed in what Google is sending out.
For reference:
Android security patch level: September 5,2018
Baseband version: g845-00023-180815-B-4956438
Kernel Version: 4.9.96-g340a9aaf92bc-ab4959234 #0 Thu Aug 16 23:24:20 UTC 2018
Build number: PD1A.180720.031
Much appreciated! $50 donation to anyone who can get me past this and rooted. I'm an old-time Verizon unlimited data planner and I need that tether check disabled.
Is root
To Pixel 3 owners that succesfully rooted, can you share the build.prop here? /system/build.prop
when i booted in to twrp it was encrypted! but i didnt have a PW.... so for everyone to whom that happens, boot up normally and disable your pin ! then you can see your storage in twrp!
i almost flipped this morning hahahaha
Carmenlove said:
Hello,
I apparently have one of these Pixel 3's that are not working with the current version of TWRP (twrp-3.2.3-0-blueline.img). Yes, I have a 3, not a 3XL. I have done these a hundred times before so I am fairly confident I am not doing anything wrong either. I get the file to load through ADB but on the reboot, it just hangs on the Google screen forever. I have left it for an hour. I have tried everything I can think of. Does anyone have any advice or is in the same situation? I just got my Pixel 3 in the mail on Friday so it's as fresh as they come. I was thinking of fully flashing the TWRP image, but I really don't think it's going to make any difference and I don't want the extra hassle of tracking down the official boot.img from the repo. I guess I will just have to wait until someone who really knows how to debug these comes across one like mine. Clearly, something has changed in what Google is sending out.
For reference:
Android security patch level: September 5,2018
Baseband version: g845-00023-180815-B-4956438
Kernel Version: 4.9.96-g340a9aaf92bc-ab4959234 #0 Thu Aug 16 23:24:20 UTC 2018
Build number: PD1A.180720.031
Much appreciated! $50 donation to anyone who can get me past this and rooted. I'm an old-time Verizon unlimited data planner and I need that tether check disabled.
Click to expand...
Click to collapse
Flash the stock boot image. Then try to fastboot boot "path to TWRP". If it still hangs, redownload TWRP and try again. Here's the stock boot for Pixel 3... https://drive.google.com/file/d/1EMkcRkH7n-1bGlVbbzcEJKKPJeE4l9mB/view?usp=drivesdk
jsauder2 said:
Flash the stock boot image. Then try to fastboot boot "path to TWRP". If it still hangs, redownload TWRP and try again. Here's the stock boot for Pixel 3... https://drive.google.com/file/d/1EMkcRkH7n-1bGlVbbzcEJKKPJeE4l9mB/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks! I will give it a try this morning after some coffee. I learned a cool trick last night to get my hotspot to work un-rooted, so I am less desperate than I was last night.
Carm
freebordjunky said:
when i booted in to twrp it was encrypted! but i didnt have a PW.... so for everyone to whom that happens, boot up normally and disable your pin ! then you can see your storage in twrp!
i almost flipped this morning hahahaha
Click to expand...
Click to collapse
Just enter your PIN at the TWRP prompt and it will work.
Mrnicgeuy633 said:
I got twrp up and running on my Pixel 3, but when try to install magisk 17.3 via twrp it says it completes but just bootloops. And I have to restore again. How did you go about it?
Click to expand...
Click to collapse
I have a similar problem. After installing twrp, I can boot to the OS, but Magisk isn't installed and I don't have root. After going back to Twrp and flashing the magisk zip, i can't get past the bootloader screen with a error saying something about failed to load boot.img.
Re-fastboot flashing the patched boot img to both slots brings me back to a rooted state with all magisk modules loaded and applied, but no more twrp. I technically don't need twrp for anything except for nandroid backups, but I guess i could just backup using the adb backup commands and get similar results, right?
Either way, I'm open to suggestions for how to get twrp and magisk working at the same time.
10.2.22.0
http://bigota.d.miui.com/V10.2.22.0...AGlobal_V10.2.22.0.PFAEUXM_745a374eee_9.0.zip
10.2.17.0
https://bigota.d.miui.com/V10.2.17....AGlobal_V10.2.17.0.PFAEUXM_53263ccd41_9.0.zip
https://bigota.d.miui.com/V10.2.17....AEUXM_20190327.0000.00_9.0_eea_b2470d1b08.tgz
New links will be posted here.
Only ota link for 10.2.22.0?? Thank you
The power of the Mi 9 be with you
Hello,
As seen in my post, my rooted 10.2.22 will only download "corrupted zips" OTA (see post here)
How did you get the URL? I cannot "explore" bigota.d.miui.com for the link when next version arrives...
Thanks!
RedWave31 said:
Hello,
As seen in my post, my rooted 10.2.22 will only download "corrupted zips" OTA (see post here)
How did you get the URL? I cannot "explore" bigota.d.miui.com for the link when next version arrives...
Thanks!
Click to expand...
Click to collapse
Have you flashed Magisk via TWRP or patching the boot image?
Because I want to keep OTA Update but patching and flashing the boot.img of the 10.2.22 above, nothing happens (the patched image is just 40MB while the original one is 130)
ponypezza said:
Have you flashed Magisk via TWRP or patching the boot image?
Because I want to keep OTA Update but patching and flashing the boot.img of the 10.2.22 above, nothing happens (the patched image is just 40MB while the original one is 130)
Click to expand...
Click to collapse
I've only patched the boot image, and it's 40mb as well, but it's OK, everything is working normally. I believe that 90mb of that boot image is just garbage or bootloader protection.
RedWave31 said:
I've only patched the boot image, and it's 40mb as well, but it's OK, everything is working normally. I believe that 90mb of that boot image is just garbage or bootloader protection.
Click to expand...
Click to collapse
So there's something wrong with the way I flash the patched boot image, because after reboot when I open Magisk it says that it's not installed.
This is my first phone with fastboot (had Samsung previously) but everything went smoothly.. I will retry tomorrow.
About the corrupted zip, I also have this issue. Today I updated to 10.2.22 AND unlocked bootloader, so I don't know which one of the 2 is causing it. Maybe bad zip in xiaomi servers, maybe xiaomi not giving right rom to who has bootloader unlocked.
V10.2.24.0
exists in version fastboot?
I can't install this update with my root phone
anemal000 said:
I can't install this update with my root phone
Click to expand...
Click to collapse
Solved!!!
i installed from twrp the 2.13gb version the 517mb one did not install it gave error 7
anemal000 said:
Solved!!!
i installed from twrp the 2.13gb version the 517mb one did not install it gave error 7
Click to expand...
Click to collapse
did you flash V10.2.24.0 ? cheers
Latest 10.2.24 EEA changelog
System
April 2019 Security Patch
Camera
Fix : Photo preview for individual shots weren't displayed in some cases
Settings
Fix : Screen brightness was lowered in dark mode whenever audio volume was adjusted
Fix : Fingerprint scanner couldnt be used when talkback was on
Fix : Clock flashed when fingerprint was used
Fix : Fingerprint unlock issues
The big, big fat lie and complete Xiaomi screwup
Fix : Notifications didn't appear in the notification shade if fingerprint unlock was used
>> NOPE, notifications were there, it's the ICONS that are missing you #£%*!?# developers
Fingerprint unlock is much faster
Else? You still have to use NotchTest. Just buy the pro version, and don't hesitate to transform it to a system app using titaniumbackup to avoid icons being wiped when screen off.
Here's how to root the Pixel 3 running on official and stock Android 10 release, step by step :
(not tested on Pixel 3 XL but it might work the same, just use the right firmware for your device)
What do you need :
> Pixel 3 phone with Android 10
> Unlocked bootloader on your Pixel device
> Latest ADB and FASTBOOT tools on your computer
1 ) Download the latest Android 10 factory image for your device ("Blueline" is the regular Pixel 3) :
Link > Android 10 factory image
2 ) Extract the "boot.img" file on your phone
3 ) Download latest Magisk Manager application on your phone and install it :
Link > https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched
5 ) Enable adb debugging on your Pixel phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
9 ) When i'ts done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings and rebooting your phone.
Note that this guide is actually for using adaway. I don't know if it will work for any other root related feature on your phone.
Great guide, thanks!
ibolito said:
11 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings.
Click to expand...
Click to collapse
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
bafforosso said:
Great guide, thanks!
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
Click to expand...
Click to collapse
Thanks its done!
I get a "This site can't be reached" message when I click the link for magisk manager in step 3. Not sure if anyone else sees it.
Thank you for making this guide!
Thanks, works perfectly!
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Oberbergler said:
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Click to expand...
Click to collapse
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
If I updated via ota adb side load to 10. But used the boot.img from the factory image, would this explain why it did boot, however not one app would start. The system ui would then crash. Just trying to figure out where I screwed up. Thank you.
ibolito said:
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
Click to expand...
Click to collapse
Thanks man Everything was right but I forgot to update adb and fastboot. Now I have root
ignore me -- im idiot.
i am not sure if my pixel 3 is really rooted. all the apps requiring root says they are granted root access, but, for example, i cannot modify system files with a root file manager at all unlike i could with android 9. how can i confirm it is surely rooted?
So I have a problem, maybe someone can help me with.
Back in March I made the following post:
"I was running on the original September Update since I got the phone, I used this guide when I first rooted https://www.xda-developers.com/googl...r-root-magisk/
Today I decided it was time to update so I used this guide https://www.xda-developers.com/flash...-google-pixel/
Then I wanted to reroot my phone. So I bootet the TWRP image and flashed the magisk 18.1 zip. But after that I softbricked my phone and it wouldn't boot anymore.
So in my panic I flashed the TWRP zip and my phone worked again, but now everytime I try to flash the magsik zip the same thing happens, bootloop and back to flashing twrp.zip. "
After that didn't work, I tried flashing the magisk uninstaller, through twrp, but it exited with "Error 1" everytime. (Running TWRP 3.3.0)
So i decided to give up, because I had some personal stuff to take care of, but after Android 10 came out yesterday, I decided to give this another go.
I flashed the factory image without "-w" and everything is working fine. So today I followed this guide, double checked everything but after I flash the patched boot image I get stuck with a bootloop again... I can flash back the original boot image and everything works so it's not a huge deal, but right now I can't use google pay, because it says I'm rooted.
Any idea what I could do? Can't run the uninstaller and can't reroot... ???
thanks!
Have you checked if your patched boot.img matches the firmware on your phone?
Well it's the same one I used to flash the firmware.
I flashed yesterday without an issue and today I loaded that boot.img onto my phone, used the canary magisk manager to patch it and then transfered it back to my PC to flash it.
Edit: I'm thinking this might have to do with the fact that I couldn't uninstall magisk before.
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
GohanBurner said:
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
Click to expand...
Click to collapse
I had it working before I bodged a magisk module install
No luck here. The steps SEEM to work perfectly. Flashed the modified boot image, booted up fine, but magisk says it's still not installed. No root.
- Latest magisk canary
- Used the same firmware
- No errors anywhere along the way
Hey Mac users, I had to use the command fastboot flash boot_b magisk_patched.img
To get the patched image over to my phone. It worked out great. I was able to reboot,
and see the root in Magisk Manager.
YMMV
Thanks, worked like a charm on Linux with latest platform-tools! I thought I'd have to wait a lot longer to get root back on my device.
I have also tried this multiple times. No errors, but I can't edit system files or add modules.
After updating to april security update everytime that I turn on or restart my pixel 6 I got this message "Your device is corrupt. It can't be trusted and may not work properly" before the unlocked bootloader message, is it normal? Can I fix it?
It would be interesting to know "how" you updated. Just take the "regular" OTA update through system settings? Install to Inactive Slot method? Sideload? Flash-all? And if you were rooted and if so what version of Magisk you were on.
But to get rid of the message there are a few things that you can try that have worked for people and may work for you (dependent on if your bootloader is unlocked of course):
1. Flash the March boot image (it may not boot, that's ok), and then flash the April boot image (seems mostly to work when you get the message as a result of flashing a custom kernel).
2. Flash the April factory image again via flash-all while removing the -w in the flash-all.bat script to keep data.
3. Use Android Flash Tool and install the April update again (uncheck all the boxes)
4. Clean flash the April factory image via flash-all or Android Flash Tool (will lose data)
5. Do nothing and wait until next month's update (some have reported that when doing this the corrupt message went away).
The corrupt message does not appear to affect anything in the negative, so if your phone is working fine you can likely just ignore it and see if it goes away after next month's update.
Lughnasadh said:
It would be interesting to know "how" you updated. Just take the "regular" OTA update through system settings? Install to Inactive Slot method? Sideload? Flash-all? And if you were rooted and if so what version of Magisk you were on.
But to get rid of the message there are a few things that you can try that have worked for people and may work for you (dependent on if your bootloader is unlocked of course):
1. Flash the March boot image (it may not boot, that's ok), and then flash the April boot image (seems mostly to work when you get the message as a result of flashing a custom kernel).
2. Flash the April factory image again via flash-all while removing the -w in the flash-all.bat script to keep data.
3. Use Android Flash Tool and install the April update again (uncheck all the boxes)
4. Clean flash the April factory image via flash-all or Android Flash Tool (will lose data)
5. Do nothing and wait until next month's update (some have reported that when doing this the corrupt message went away).
The corrupt message does not appear to affect anything in the negative, so if your phone is working fine you can likely just ignore it and see if it goes away after next month's update.
Click to expand...
Click to collapse
1- Uninstalled magisk (v24.3) > Restore Images
2- Updated from system (April OTA update)
3- Installed Magisk to Inactive slot and rebooted
So far so good
4- After 2 days, april security update popped up
5- Repeated 1~3 steps and got corrupt error after reboot, I tought I was stuck on bootloop, I tried to use Pixel Flash and Android Flash Tool, but because of the error I couldn't flash anything "automatically", because when the tool reboot to recovery mode it gets stucked at corrupt message and can't access recovery. I wiped all and factory reset, but nothing.
6- I flashed everything through adb and managed to boot, but the message is still tthere.
revhellyoN said:
1- Uninstalled magisk (v24.3) > Restore Images
2- Updated from system (April OTA update)
3- Installed Magisk to Inactive slot and rebooted
So far so good
4- After 2 days, april security update popped up
5- Repeated 1~3 steps and got corrupt error after reboot, I tought I was stuck on bootloop, I tried to use Pixel Flash and Android Flash Tool, but because of the error I couldn't flash anything "automatically", because when the tool reboot to recovery mode it gets stucked at corrupt message and can't access recovery. I wiped all and factory reset, but nothing.
6- I flashed everything through adb and managed to boot, but the message is still tthere.
Click to expand...
Click to collapse
There was a problem updating to the April security update using the install to inactive slot method and Magisk 24.3 (as well as Canary 24305 and earlier) for the Pixel 6 series. It was fixed with Canary 24306.
Some reported that they were able to get rid of the message by dirty flashing the factory image via flash-all.
Lughnasadh said:
There was a problem updating to the April security update using the install to inactive slot method and Magisk 24.3 (as well as Canary 24305 and earlier) for the Pixel 6 series. It was fixed with Canary 24306.
Some reported that they were able to get rid of the message by dirty flashing the factory image via flash-all.
Click to expand...
Click to collapse
I just ran into this same issue. Right after I thought I finally was able to update correctly using the inactive slot method. flash-all with wipe did not correct the issue.
*UPDATE* dirty flash using flash tool did correct the issue AFTER installing Canary 24306. Thank you.
For future Pixel 6 updates, is Magisk Canary 24306 recommended instead of stable 24300?
With the past couple OTA updates I've been using 24300 and when flashing a patched boot image it's been rotating between _a and _b slots and the same for older Canary builds. So far no corruption or boot problems. My only concern is that the last couple OTA updates failed over the internet and I ended up sideloading. I don't know if OTAs failing signals a potential problem or not.
manjaroid said:
For future Pixel 6 updates, is Magisk Canary 24306 recommended instead of stable 24300?
With the past couple OTA updates I've been using 24300 and when flashing a patched boot image it's been rotating between _a and _b slots and the same for older Canary builds. So far no corruption or boot problems. My only concern is that the last couple OTA updates failed over the internet and I ended up sideloading. I don't know if OTAs failing signals a potential problem or not.
Click to expand...
Click to collapse
Well, I guess that depends on how you are updating. As you probably know, the April build brought some grief to those who update via "Install to Inactive Slot". Thus, if using this method, Canary 24306 would likely be the best way to go, although who knows what Google has in store for us in May.
Your OTAs could be failing for a number of reasons. You pretty much want to be stock without having /system, /vendor, etc. modified, as well as not being on a custom kernel.
Lughnasadh said:
Your OTAs could be failing for a number of reasons. You pretty much want to be stock without having /system, /vendor, etc. modified, as well as not being on a custom kernel.
Click to expand...
Click to collapse
So far my updates are 2 for 4: first couple were over the air, last couple had to be sideloaded (got the phone in January). I've been on stock the whole way including the kernel, and haven't messed with the root file system, not on purpose anyway. I won't worry about the OTAs until things get messier, but I might go with Magisk Canary in May out of curiosity.
Is there any guide about how to change to magisk stable for magisk canary? All I find at Google is old, like changing update channel
revhellyoN said:
Is there any guide about how to change to magisk stable for magisk canary? All I find at Google is old, like changing update channel
Click to expand...
Click to collapse
Uninstall the Canary app and install the Stable app and then direct install (or patch and flash your boot image again with the Stable app).
Just finished upgrading to May build and patched with Magisk 24300, disabled flags, everthing is good for now.
Long story short, I rooted my N200 T-Mobile variant to A12 DE2118_11_C.15 (Full OTA) not a long time ago with no issues. However to be able to update to DE2118_11_C.16 (Incremental update, w/July 2022 Patch) I had to uninstall Magisk first, then update it to c.16. Now my phone is updated to c.16 but I am very unsure how to root it again to avoid bootloop;
1. Can I use c.15 stock boot image since c.16 was an incremental update? or I need c.16 version?
2. If c.16 boot image is already extracted please share.
3. If none above, how and where I can find the OTA file to extract payload.bin and then boot.img?
I would really appreciate if somebody help me with this, thank you.
HTCore said:
Long story short, I rooted my N200 T-Mobile variant to A12 DE2118_11_C.15 (Full OTA) not a long time ago with no issues. However to be able to update to DE2118_11_C.16 (Incremental update, w/July 2022 Patch) I had to uninstall Magisk first, then update it to c.16. Now my phone is updated to c.16 but I am very unsure how to root it again to avoid bootloop;
1. Can I use c.15 stock boot image since c.16 was an incremental update? or I need c.16 version?
2. If c.16 boot image is already extracted please share.
3. If none above, how and where I can find the OTA file to extract payload.bin and then boot.img?
I would really appreciate if somebody help me with this, thank you.
Click to expand...
Click to collapse
The steps below is what I do since Android 12 update:
**Automatic system updates should be unchecked on Developer options.**
Prerequisites: Rooted with Magisk (v25.2 recommended) / Have stock boot image available.
Preparation:
A. Restore active slot boot img with stock boot on adb shell with root
ex) dd if=/sdcard/boot_a.img of=/dev/block/bootdevice/by-name/boot_a
OR
B. Uninstall Magisk with Restore Image option if available
--------------------------------------------------------------------------------------------------------------
**If you do A first and Direct Install with Magisk, then B option will be available.
1. Update OTA and DO NOT PRESS Restart Button.
2. Backup the new stock boot image. If your current boot is b, then new stock boot is a
ex) dd if=/dev/block/bootdevice/by-name/boot_a of=/sdcard/boot_a.img
3. Patch the newly extracted stock boot with Magisk -> Reboot -> Reboot to fastboot
4. Flash the newly magisk patched image
ex) fastboot flash boot_a new_magisk_boot.img
5. Reboot
OR you can try to install Magisk with in-active slot option at Step #3, then restart with OTA, not with Magisk; however, I've been told that it sometimes makes an issue such as bootloop. Up to you.
follow A1.1 to get your boot.img.
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
After your phone is rooted again, go in developer options and disable automatic system updates so it won't restart without your consent in future OTAs. when it asks for you to restart, go into the magisk app and press install and then "install to inactive slot". Then go back to the system update screen and press restart.
That's it. If you followed the steps correctly, your device should be updated and you should still have root!
Thank you both of you for your help and thorough explanation.
I suppose since I already restarted my device after update I have no chance with @lentm's method.
Now I'm going to follow what @justauserthatusesaphone posted and see what happens.
I will post the result here if somebody else is interested too.
HTCore said:
Thank you both of you for your help and thorough explanation.
I suppose since I already restarted my device after update I have no chance with @lentm's method.
Now I'm going to follow what @justauserthatusesaphone posted and see what happens.
I will post the result here if somebody else is interested too.
Click to expand...
Click to collapse
All you need is the stock boot img file, and here's the latest one:
11_C.16_DE18CB_tmobile_stock.7z is available for download
Click to access the 11_C.16_DE18CB_tmobile_stock.7z (35.3 MB) download with TransferNow
www.transfernow.net
Thank you for posting boot.img @lentm!
I was middle of what @justauserthatusesaphone posted when you attached the boot.img! So thank you very much being mindful of others!
However, just to learn more and be prepared for future updates I tried the other method and it worked perfectly! My device is now rooted with latest update thanks both of you guys!
Next I'm gonna use your method for another N200 which hasn't been updated yet and experience that one as well.
HTCore said:
Thank you for posting boot.img @lentm!
I was middle of what @justauserthatusesaphone posted when you attached the boot.img! So thank you very much being mindful of others!
However, just to learn more and be prepared for future updates I tried the other method and it worked perfectly! My device is now rooted with latest update thanks both of you guys!
Next I'm gonna use your method for another N200 which hasn't been updated yet and experience that one as well.
Click to expand...
Click to collapse
glad to hear you got it!
lentm's link didn't work for me so for anyone else who needs the stock image here is a non-expiring link for stock boot image for Tmobile DE2118 11_C.16:
boot_11_C.16_DE2118_tmobile_stock.img | by towardsdawn for Nord N200 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Could someone please tell me if it's possible to root this device running the latest July 5th update mentioned above without a pc ?
And if so where to find or how to do it ?!
I've been searching everywhere and have only come across a bunch of "one clock root options" that haven't worked .
Brisingrmischief said:
Could someone please tell me if it's possible to root this device running the latest July 5th update mentioned above without a pc ?
And if so where to find or how to do it ?!
I've been searching everywhere and have only come across a bunch of "one clock root options" that haven't worked .
Click to expand...
Click to collapse
One click root APKs don't have access to fastboot to flash a rooted boot.img, which is what you need to do for permanent root for newer Android devices. Also I wouldn't trust those anyway, most are not open source and might contain malware/ads/etc.
You can have a temporary root if your bootloader is unlocked by using a DSU, however if your bootloader has not been unlocked (which you need a PC to do) do NOT attempt to do this. Multiple people have reported bricking their devices attempting to do this so you have been warned.
All files on the DSU will be deleted when you discard the DSU since it is a different system image from the original. If you really know what you're doing you might be able to flash a Magisk rooted boot.img to the original system image from the DSU, I don't know how to do this. You can play around with making the DSU persist through reboots using this guide, I don't know if that works with updates or if all files will have to be discarded if you want to update. I recommend using DSU sideloader with a GSI from phhusson, when it says to run the shell script over ADB you can use a terminal app like Termux instead.
towardsdawn said:
One click root APKs don't have access to fastboot to flash a rooted boot.img, which is what you need to do for permanent root for newer Android devices. Also I wouldn't trust those anyway, most are not open source and might contain malware/ads/etc.
You can have a temporary root if your bootloader is unlocked by using a DSU, however if your bootloader has not been unlocked (which you need a PC to do) do NOT attempt to do this. Multiple people have reported bricking their devices attempting to do this so you have been warned.
All files on the DSU will be deleted when you discard the DSU since it is a different system image from the original. If you really know what you're doing you might be able to flash a Magisk rooted boot.img to the original system image from the DSU, I don't know how to do this. You can play around with making the DSU persist through reboots using this guide, I don't know if that works with updates or if all files will have to be discarded if you want to update. I recommend using DSU sideloader with a GSI from phhusson, when it says to run the shell script over ADB you can use a terminal app like Termux instead.
Click to expand...
Click to collapse
Thank you for your help !
I assume that since my bootloader is not unlocked and I don't have access to a pc I'm pretty much out of luck on rooting this device until I can get access to one .
Guess I'll have find a way to access one .
Much appreciated though !