Database Info

Apply Monthly System Update to Systemless Root ... REALITY CHECK!

Hi everyone
More than a question, I wanted to share some steps I plan to follow to apply the monthly system update and check I am on the right track. I had a Google Pixel 2 for a few months and I am learning more about the model every day.
Previously, I tried to follow different procedures found here on XDA such as applying OTA with boot images temporarily restored but I ended up with a bootloop not event TWRP could fix since all data was encrypted.
Objective:
Update the system to the latest Pixel 2 update (in this case Feb 2018) avoiding bootloops or bricks
Current Status:
Pixel 2 Walleye with Jan 2018 update
Rooted systemlessly with Magisk
No Magisk modules installed
/system modified since I have AdAway and other apps
No BusyBox installed
No Custom Recovery installed
Proposed steps:
Uninstall Magisk completely
Remove root apps from Device Admin (such as Greenify, Tasker, etc.)
Download latest factory image from Google
Extract the following from the image zip:
bootloader.img
radio.img
boot.img
dbto.img
cache.img
system.img
recovery.img​
Restart phone into booloader
Fastboot bootloader.img
Reboot the bootloader
Fastboot the following commands in this order:
radio.img
boot.img
dbto.img
cache.img
system.img
recovery.img​
Reboot phone
Install Magisk by patching boot
Re-run root apps (AdAway, etc.)
Renable root apps as Device Admin (Tasker, Greenify, etc.)
Is the above safe enough to avoid bootloop and also not lose apps and data installed?
I am aware any modifications to /system will be lost.
Have a look, let me know if on track, and if you want, give me your blessing.

Yesterday I used Dueces bootloop recovery script to update without losing anything.
I had magisk + TWRP installed
Download full update not OTA, extract to program tools directory or where you keep your goodies. Pull all factory update in folder with deuces recovery script.
From stk rooted ROM reboot bootloader,
Run dueces script from bootloader
After finished script No to format data
Reboot system when done.
From there you should be good to go, you will need to repatch but image in magisk and all that but i lost no data and had no issues
So I was on 1.171019.019 installed 1.172019.21 from fastboot with script and wiped nothing and lost nothing..
** My directions are probably incomplete so follow his instructions in his OP.

This has been discussed all over the place on the forums but you're over complicating the update process. Here's what you do:
Code:
Download the latest Pixel update
extract the update in your ADB folder on a computer
reboot to bootloader
look for the flash-all.bat and remove the -w at the bottom of that code, Save that file (the -w is what causes the device to be wiped)
run flash-all.bat
once that finishes you can fastboot boot twrp.img
it won't decrypt (Feb update broke TWRP decryption) but go read only and get into ADB Sideload mode
adb sideload kernel.zip
adb sideload magisk.zip
reboot
This is what I've done everytime (minus the adb sideload) and I have had zero issues. No loss of data being the biggest concern. Did this using the march update just yesterday and now I'm good to go.
It is worth saying when you start trying to flash (roms, kernels ect..) and you get a little crazy, Dueces Bootloop Recovery script is 100% something to have on deck if something /does/ go wrong.

nolimit78 said:
adb sideload kernel.zip
Click to expand...
Click to collapse
kernel.zip from where? The OTA? One you saved with TWRP on it?
I currently have TWRP and Magisk (default - nothing changed yet) installed on the February update. Is this going to be a monthly thing - flash the update, reinstall TWRP, reinstall Magisk? Not a complaint, just want to know what I'm doing. (Samsung, for all its faults, was a little easier after 6 years of not even having to look at what I was doing. I'll get comfortable with the Pixel, but this is my first update with TWRP and Magisk installed - it did the February update almost before I could read the screen.)

Rukbat said:
kernel.zip from where? The OTA? One you saved with TWRP on it?
I currently have TWRP and Magisk (default - nothing changed yet) installed on the February update. Is this going to be a monthly thing - flash the update, reinstall TWRP, reinstall Magisk? Not a complaint, just want to know what I'm doing. (Samsung, for all its faults, was a little easier after 6 years of not even having to look at what I was doing. I'll get comfortable with the Pixel, but this is my first update with TWRP and Magisk installed - it did the February update almost before I could read the screen.)
Click to expand...
Click to collapse
The kernel.zip is whatever kernel you'd like to use (flash or elemental) but it's not required. I just rename for shorter commands for ADB Yes, you've hit the nail on the head. If you're going to be stock/rooted, you'll have to do this every month to stay current.

And we're still waiting for Dees_Troy to figure out how to add decryption back to TWRP, so it's reinstall everything - including fingerprints - every month. Oh, well. (Hey, no pressure, Dees_Troy - I appreciate just having TWRP on this thing.)

Rukbat said:
And we're still waiting for Dees_Troy to figure out how to add decryption back to TWRP, so it's reinstall everything - including fingerprints - every month. Oh, well. (Hey, no pressure, Dees_Troy - I appreciate just having TWRP on this thing.)
Click to expand...
Click to collapse
In my process outline, you don't have to remove fingerprints.

To boot to TWRP to handle files that you already copied to the phone? TWRP doesn't decrypt the names any more, does it? So all you see is garbage (encrypted hash, I guess). If I want to restore a backup I have to remove the PIN, which seems to remove the fingerprints. Or are you saying to restore the PIN and the fingerprints are still active?

Rukbat said:
To boot to TWRP to handle files that you already copied to the phone?
Click to expand...
Click to collapse
No, this is only to apply the update and flash a custom kernel and magisk
Rukbat said:
TWRP doesn't decrypt the names any more, does it?
Click to expand...
Click to collapse
No, it sure doesn't. This was caused by the Feb Update
Rukbat said:
If I want to restore a backup I have to remove the PIN, which seems to remove the fingerprints.
Click to expand...
Click to collapse
Yeah, to do anything in TWRP (outside of ADB Sideloading) you'll need to remove the PIN.

And evidently something else. I removed the PIN, updated, and the phone's been sitting on the G screen for half an hour. So I rebooted to the bootloader, locked it, and now I'm flashing 021. I have a bad feeling that I'm going to be stuck.
---------- Post added at 05:09 PM ---------- Previous post was at 04:10 PM ----------
As I feared. So I followed Google's instructions to flash the factory image. It went fine, until I got:
Created filesystem with 11/7389184 inodes and 511894/29553659 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
Click to expand...
Click to collapse
Then it wrote the system, but
writing 'system'...
OKAY [ -0.000s]
sending sparse 'system' (524284 KB)...
FAILED (remote: No such partition.)
Click to expand...
Click to collapse
It never reboots. If I reboot at that point, I get the recovery screen.
If I reboot into the bootloader and lock it, I get the bootloader with "ERROR: LoadImageAndAuth Failed: Load Error" at the bottom.
I was able to load twrp.img and use it to sideload twrp.zip, but that still doesn't get me back to Android. I tried b ooting into A and B and got the same result - TWRP.
What next? Is there a fix, or does this one have to be replaced also?

Rukbat said:
And evidently something else. I removed the PIN, updated, and the phone's been sitting on the G screen for half an hour. So I rebooted to the bootloader, locked it, and now I'm flashing 021. I have a bad feeling that I'm going to be stuck.
---------- Post added at 05:09 PM ---------- Previous post was at 04:10 PM ----------
As I feared. So I followed Google's instructions to flash the factory image. It went fine, until I got:
Then it wrote the system, but
It never reboots. If I reboot at that point, I get the recovery screen.
If I reboot into the bootloader and lock it, I get the bootloader with "ERROR: LoadImageAndAuth Failed: Load Error" at the bottom.
I was able to load twrp.img and use it to sideload twrp.zip, but that still doesn't get me back to Android. I tried b ooting into A and B and got the same result - TWRP.
What next? Is there a fix, or does this one have to be replaced also?
Click to expand...
Click to collapse
Oh my gosh. Stop sending your phone back.
Update your platform-tools. Change cables. Change ports. Use the search function.
Sent from my Pixel 2 using Tapatalk

I'm not exactly new at this. Different cable, every USB port (including a 2.0 port, new download of both Google's driver and adb/fastboot, a new download of the firmware (and the sha256 is correct).
The next thing I'm going to try, as soon as I finish eating, is another computer. If that fails, and I'm pretty sure it will, I'll call Google tech support. Since it happened twice during an OTA, on two different phones, I may be able to get someone who knows how to feed the firmware into a nearly dead phone. I'm just looking for ideas I haven't had, when I post here. I'm about out of ideas. Again.

Evidently some computer manufacturers don't exactly build what they claim to build. My desktop has 2 USB 3.0 ports (which I already knew wouldn't work) and - supposedly - a USB 2.0 port. Flashing the firmware on the "2.0" port didn't work. Evidently it's not 2.0.
So I resurrected an old Windows 8.0 laptop. I think it has 0 cores running at 0MHz - it's SLOW! But it finally flashed the February update. Tomorrow (it's going on midnight here, and the phone is still downloading the last Google backup) I'll update to March.
Madness - but at least I have a working phone, and know how to get it working again if I need to (and have a few lifetimes to do it). And I have another laptop in the closet that actually works. That one gets resurrected next.

So what you're experiencing isn't new or an issue with your phone that you'd need to RMA the device. It's a learning curve because the A/B partitions are a completely different beast compared to older/other Android devices. Use Duece's Bootloop Recovery script to fix your problems. It'll work and you'll be good to go. Just be sure not to wipe. During my testing, I had to figure out all this myself and was /REALLY/ close to RMA'ing my device. But I continued to research and plugging away and found that that script helps users in your situation, as I've been in that very same situation myself.

No, it's a learning curve because, even though the USB ports on the back of the case are labeled 2.0, and have black plastic, they act like 3.0 ports with a Pixel 2. Doing exactly what both I and Google tech support did with the supposed 2.0 ports, on the aging laptop with real 2.0 ports, solved the "problem" that both Google and I were having. The phone was fine, what we were doing was right, the Acer desktop has a documentation error, and that was the only problem. (Even Google didn't seem to be aware of the USB 3.0/Pixel2 incompatibility, which many of the people in the Pixel 2 forums at XDA are.)

Follow the guide in my signature, it works, and you don't have to muck around with removing PINs and fingerprints.

Thanks for paying attention, but what really bothers me is having to remove the fingerprints in order to do a backup or restore in TWRP. I'm used to just booting to it and flashing a backup if I need it for some reason. If only Google would leave the fingerprint file alone when we went to None for the lock screen, just putting the PIN back would bring the fingerprints back. There's really no reason to delete that file. Maybe delete individual prints at the user's discretion (like changing passwords every once in a while), but not delete the whole thing just because I want to back up my current configuration.

What I do is uninstall Magisk. Then do the normal update from the update page in settings. After this I copy Magisk zip file to a usb drive. I boot into twrp using ADB. It doesn't decrypt but that doesn't matter. Use the USB as storage and install Magisk zip file through TWRP. Reboot and you are done updating with Magisk installed.

That sounds like an easy way of doing it, but doesn't the update balk at the patched boot file? Mine balked at something yesterday, which is what started all the mess yesterday. (Or does Magisk have a "remove and replace the boot file" button?)

nolimit78 said:
This has been discussed all over the place on the forums but you're over complicating the update process. Here's what you do:
Code:
Download the latest Pixel update
extract the update in your ADB folder on a computer
reboot to bootloader
look for the flash-all.bat and remove the -w at the bottom of that code, Save that file (the -w is what causes the device to be wiped)
run flash-all.bat
once that finishes you can fastboot boot twrp.img
it won't decrypt (Feb update broke TWRP decryption) but go read only and get into ADB Sideload mode
adb sideload kernel.zip
adb sideload magisk.zip
reboot
This is what I've done everytime (minus the adb sideload) and I have had zero issues. No loss of data being the biggest concern. Did this using the march update just yesterday and now I'm good to go.
It is worth saying when you start trying to flash (roms, kernels ect..) and you get a little crazy, Dueces Bootloop Recovery script is 100% something to have on deck if something /does/ go wrong.
Click to expand...
Click to collapse
Thank you for the feedback!
One question I had for a while: flashing the data.img wipes what? Doesn't it wipe the apps you have installed?

Request for a Guide

I'm not so happy with EMUI 8/Oreo on my Mate 9. Several widgets don't update, requiring me to change the screen resolution during the day (weird temporary fix). I'd rather run Nova but EMUI pushes against that. I have a pretty good backup phone (ZTE Axon 7) so I thought I would give a generic system image a try. The last time I rooted and installed an alternative ROM was 2014, so I'm rusty. I successfully put minimal fastboot on a PC, unlocked the bootloader and installed TWRP 3.2.1-0 (something may have gone wrong already at this point since I accessed it by vol up + power, rather than vol up + vol down + power). Then I installed the generic system image. It booted, but gave error messages at boot. Perhaps all I needed to do was install it a second time, but instead I tried installing a different image, achieved bootloop, made matters worse, and was rescued by the amazing and wonderful FunkyHuawei.
I am thinking about trying again, but I wondered if an expert would write a more patient guide that provides the exact steps to flashing a generic system image. By the exact steps, I mean with links to files and what you type in minimal fastboot (if indeed that is the right program), or when it is best to install from an SD card. I'm sure such a guide would get more people to try other ROMs besides the generic ROM.

prestonmcafee said:
I'm not so happy with EMUI 8/Oreo on my Mate 9. Several widgets don't update, requiring me to change the screen resolution during the day (weird temporary fix). I'd rather run Nova but EMUI pushes against that. I have a pretty good backup phone (ZTE Axon 7) so I thought I would give a generic system image a try. The last time I rooted and installed an alternative ROM was 2014, so I'm rusty. I successfully put minimal fastboot on a PC, unlocked the bootloader and installed TWRP 3.2.1-0 (something may have gone wrong already at this point since I accessed it by vol up + power, rather than vol up + vol down + power). Then I installed the generic system image. It booted, but gave error messages at boot. Perhaps all I needed to do was install it a second time, but instead I tried installing a different image, achieved bootloop, made matters worse, and was rescued by the amazing and wonderful FunkyHuawei.
I am thinking about trying again, but I wondered if an expert would write a more patient guide that provides the exact steps to flashing a generic system image. By the exact steps, I mean with links to files and what you type in minimal fastboot (if indeed that is the right program), or when it is best to install from an SD card. I'm sure such a guide would get more people to try other ROMs besides the generic ROM.
Click to expand...
Click to collapse
By a generic system image, you are referring to wanting to install an aosp image (treble ROM), correct?

Yes.

prestonmcafee said:
Yes.
Click to expand...
Click to collapse
And obviously you still have your bootloader unlock code?
Also what Mate 9 version do you have and what exact firmware is it running?
I can help ya out no problem. Just obviously want to make sure you avoid going through that again

Thanks, Wirmpolter! I have the unlock code, but it shows as unlocked, at least I get the dire warning about the device being unsafe on boot. I have the US model, build number MHA-L29 9.0.0.360 (C567), with both Android and EMUI versions listed as 8.0.0.

Sorry, MHA-L29 8.0.0.360 (C567)

prestonmcafee said:
Thanks, Wirmpolter! I have the unlock code, but it shows as unlocked, at least I get the dire warning about the device being unsafe on boot. I have the US model, build number MHA-L29 9.0.0.360 (C567), with both Android and EMUI versions listed as 8.0.0.
Click to expand...
Click to collapse
Oh...You're already bootloader unlocked that makes it even easier.
I'm using the system.IMG form the thread below this paragraph. Tried a few different aosp ROMs and it seems to be the best so far. Aside from a couple things of course. And the honor 8 Pro is the same CPU, GPU found in the mate 9.
https://forum.xda-developers.com/honor-8-pro/development/rom-t3758564.
In the main post of that thread, just follow step 2 and 3 and you'll be good to go for having an aosp ROM.
As for magisk/root... You can follow my guide below that I posted the other day. Just let the aosp ROM boot up once first. Also I can extract the ramdisk.IMG you'll need if you can't once you check it over.
https://forum.xda-developers.com/mate-9/how-to/guide-install-magisk-mate-9-running-t3773878
Basically in a nutshell to get setup on an aosp ROM is as follows
1 Download the ROM from the first thread i posted
2 Extract the system.img to where your adb folder is
3 Run command prompt from there
4 With your phone powered off. Hold the volume up button and connect it to your computer (fastboot screen)
5 Run command fastboot flash system system.img
6 Then type fastboot reboot but when you goto run this command get ready to hold the volume up button when the screen goes off so you can get the phone into stock recovery
7 Once in the recovery, perform a factory reset
8 Reboot the phone and should be good to go
Need to do first boot on its own before rooting

Thanks!!!
It will be about a week before I can try again but I'm looking forward to it. Are you pretty happy with it?

prestonmcafee said:
Thanks!!!
It will be about a week before I can try again but I'm looking forward to it. Are you pretty happy with it?
Click to expand...
Click to collapse
Yeah, fairly happy about it. A few bugs though but nothing major. Get better standby drain and about the same SOT time as EMUI. The only thing that is lacking is the camera in aosp doesn't use both cameras.
There is the stock camera port (works with magisk) but it's lacking a few things like video recording doesn't work... And umm not sure what else.

I needed to install an update, enable developer options and enable OEM unlocking (which was greyed out) before it would install. Here is my earlier post:
Dang, didn't work. Here is what I did.
-reset phone, but did not enable developer options.
-extracted and placed system.img in the minimal fastboot and adb folder. Ran a command prompt with administrative rights (win 10)
-shut off and connected Huawei mate 9 by USB, holding vol up
-vol up brought the EMUI restore screen. Shut off and tried again, same outcome. So shut off and tried vol down, and that brought up the fastboot screen. It reported phone unlocked but FRP locked.
-ran command "fastboot flash system system.img" and get:
target reported max download size of 471859200 bytes
sending sparse 'system' 1/4 (460796 KB)...
OKAY [ 11.167s]
writing 'system' 1/4...
FAILED (remote: Command not allowed)
finished. total time: 11.183s
I suspect this is due to the FRP locked condition.

Now I've run into a different problem: the EMUI screen gives me the options of
Download latest version and recovery
Reboot
Shutdown
It does not give me the option of a factory reset. What seemed to work was holding volume down through a couple of boots, when EMUI gave me the option of a factory reset. This gave me what appears to be a fully functioning system!

prestonmcafee said:
Now I've run into a different problem: the EMUI screen gives me the options of
Download latest version and recovery
Reboot
Shutdown
It does not give me the option of a factory reset. What seemed to work was holding volume down through a couple of boots, when EMUI gave me the option of a factory reset. This gave me what appears to be a fully functioning system!
Click to expand...
Click to collapse
Yeah, the FRP lock would prevent fastboot commands from working.
So, your system is back up and running?

OK, now that I have it up and running, here is the procedure I used, fixing what are either typos or variations because my system was slightly different. I unlocked the bootloader using instructions from:
http://www.teamandroid.com/2017/04/08/huawei-mate-9-unlock-bootloader/
I used Minimal ADB and Fastboot from
https://forum.xda-developers.com/showthread.php?t=2317790
I downloaded and extracted the system image from the link Wirmpolter provided:
https://forum.xda-developers.com/honor-8-pro/development/rom-t3758564
Here is a slightly edited set of instructions that worked for me:
a. unlock bootloader
b. reset phone
c. enable developer mode (settings/system/about phone tap on build number until developer mode is enabled), enable OEM unlock and USB debugging
d. check that FRP unlock and bootloader unlock worked by booting into fastboot screen (for me, hold VOL DOWN while booting)
1 Download the ROM from the thread above
2 Extract the system.img to where your adb folder is
3 Run command prompt from there (or use MA&F's desktop icon, which does the same thing)
4 With your phone powered off. Hold the volume DOWN button and connect it to your computer (fastboot screen)
5 Run command: fastboot flash system system.img
6 Then type fastboot reboot but when you goto run this command get ready to hold the volume up button when the screen goes off so you can get the phone into stock recovery
7 Once in the recovery, perform a factory reset [eRecovery didn't have this option, so I rebooted a couple of times while holding vol up and it eventually gave me the option to factory reset]
8 Reboot the phone and should be good to go

Up and Running!
Wirmpolter said:
Yeah, the FRP lock would prevent fastboot commands from working.
So, your system is back up and running?
Click to expand...
Click to collapse
I'm up and running. Thanks! So far, the only glitches are:
While Android can see and format the SD card (a Samsung 64GB), the SD card is invisible over a USB connection and Google Maps and my music player can't see it. File explorer and copy files to the SD card, so the SD card works.
The camera is terrible, but you have a fix for that.

I'm quite lost about how to install Magisk and a camera module
At the risk of asking too much, I have another request. I'm looking at how to install the stock camera on my Mate 9 with the AOSP, and here is my pathetic understanding of the steps.
First, I looked at your (Wirmpolter) instructions:
1. Install latest Magisk Manager from the Official Thread: https://forum.xda-developers.com/app...mless-t3473445
Follow the instructions of "Install Via Magisk Manager" in the main thread, but instead of providing the boot image (which these devices do NOT have), provide the stock ramdisk.img extracted from your Update.app using Huawei Update Extractor.
2. If you are using Mate 9 with model MHA-L29636 running on firmware ending in B362, you can download the stock ramdisk.img I extracted from official OTAs in the attachments
If you have stock ramdisk images for other devices, please share them and I'll add them to the OP.
3. Pull the patched image with adb pull /sdcard/MagiskManager/patched_boot.img, and flash the patched ramdisk via fastboot:
fastboot flash ramdisk patched_boot.img
Reboot and you shall have a properly rooted device passing SafetyNet, start playing with some Magisk modules!
Here are some questions:
1. Huawei update extractor
https://forum.xda-developers.com/showthread.php?t=2433454
I probably need help using this. The item I need extracted is the update.app, but where do I get the update.app that I extract from? And I'm extracting ramdisk.img?
2. download file for my phone that will be the source of the update.app in #1 (MHA-L29 8.0.0.366(C567)) from FunkyHuawei? Firmware finder? or from the phone itself? (see, I'm pretty lost)
3. install magisk manager (from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager -- this is an android app? Do I sideload it?
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img
Magiskmanager is an android app. How do I install on my phone? I was expecting this to be a windows app that would install magisk on my phone, so was thrown when it was an .apk.
Finally, the camera image is here:
https://forum.xda-developers.com/showpost.php?p=75848917&postcount=2
It isn't clear to me how to flash using Magisk, but perhaps that will be obvious once I have magisk operating.

prestonmcafee said:
1. Huawei update extractor
https://forum.xda-developers.com/showthread.php?t=2433454
I probably need help using this. The item I need extracted is the update.app, but where do I get the update.app that I extract from? And I'm extracting ramdisk.img?
2. download file for my phone that will be the source of the update.app in #1 (MHA-L29 8.0.0.366(C567)) from FunkyHuawei? Firmware finder? or from the phone itself? (see, I'm pretty lost)
Click to expand...
Click to collapse
Firmware Finder (they have Windows desktop and Android apps for it, and there's also http://pro-teammt.ru/firmware-database/ which does the job just as well, though it's all in Russian.)
Find the FullOTA-MF firmware that corresponds to your model, download the 'update.zip' that goes with it - on the website, it's under the link 'update' in the same row. If you do it on your phone in the Firmware Finder app, hit "Download" on the relevant detail screen and it'll prompt you for which files you want.
Once you've got the update.zip, extract it, you'll find a file UPDATE.APP, which is what the extractor wants. If it throws up an error, disable CRC checking of the extracted content. (I don't recall what the label for it is and I don't have it installed on the machine in front of me...); and yes, you'll want RAMDISK.img from it.
prestonmcafee said:
3. install magisk manager (from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445):
Magiskmanager is an android app. How do I install on my phone? I was expecting this to be a windows app that would install magisk on my phone, so was thrown when it was an .apk.
Click to expand...
Click to collapse
Magisk Manager wants to create a patched ramdisk image. When it updates, it'll want to update the ramdisk image on your device (which it'll be able to do since it's running with root privileges itself anyway), but for the first pass, it needs that image provided and for you to manually flash it.

Thanks!
That is perfect. I downloaded the correct file from FF and I will try installing Magisk tomorrow or Sunday.

prestonmcafee said:
That is perfect. I downloaded the correct file from FF and I will try installing Magisk tomorrow or Sunday.
Click to expand...
Click to collapse
The magisk manager app apk you just run on your phone to install it, no side loading required.

Thanks! Magisk installed! To flash the camera app, I first extract and flash kernel.img from update.app with fastboot, put the camera zip (extract first?) in the magisk folder on the phone to install it with magisk?

That worked
prestonmcafee said:
Thanks! Magisk installed! To flash the camera app, I first extract and flash kernel.img from update.app with fastboot, put the camera zip (extract first?) in the magisk folder on the phone to install it with magisk?
Click to expand...
Click to collapse
That seems to have worked.

[Magisk] Root Honor 10

Since I got my hands on honor 10 firmware I decided to release Magisk root for honor 10
This is pulled from TL10/AL10 firmware.
Note to unlock your bootloader you'll have to email [email protected] or use Google doc provided by Chris!
Once you got your code and unlocked your bootloader unlocked.
Boot into bootloader mode (power off phone) and hold volume down while plugging in cable to phone.
Now in terminal/cmd type
fastboot flash ramdisk col-magisk-tlxx.img
And you're done.
After booting to system it's recommended to flash Magisk again with magisk manager to avoid module installation issues.
https://mega.nz/#!8SQyVayC!G4wDQWdkXcmkwQ44dmsd7MYhFlhdOX2M88Jc25BWr6k
Ill get hunted for this !

Is this the same method to install Magisk? https://www.getdroidtips.com/root-huawei-p20-lite/

sam razzy said:
Is this the same method to install Magisk? https://www.getdroidtips.com/root-huawei-p20-lite/
Click to expand...
Click to collapse
Exactly just use this patched ramdisk
Sent from my DUK-L09 using Tapatalk

I'm new to Honor devices - so please excuse my stupid question
What I understand is that it is required to flash the RAMDISK.
Is your solution working on every firmware or is it specific to version? ( currently running COL-L29 8.1.0 (C432) )
Are there any known issues with OTA updates?
KR,
Damien

well it's COL, i don't think exact version makes difference, but waiting for someone else to try
but i ain't gonna do it until i know how to backup stock ramdisk
also be aware with root you can't install OTA updates anymore

Unlock code
Okay, so now that huawei isn't giving away unlock Codes anymore, ist there another way to unlock the bootloader?

disappear
LastStandingDroid said:
fastboot flash ramdisk col-magisk-tlxx.img
And you're done.
Click to expand...
Click to collapse
Hi guys.
I flash the image, but after a while after loading the phone the root disappears. After a reboot, it reappears and disappears after a while. How to fix it?
Chiptrip said:
Okay, so now that huawei isn't giving away unlock Codes anymore, ist there another way to unlock the bootloader?
Click to expand...
Click to collapse
The unlock code is available by links

somehow i cant boot into fastboot on my honor 10. any help?

MachineGunJinx said:
somehow i cant boot into fastboot on my honor 10. any help?
Click to expand...
Click to collapse
Try pressing volume down + Powerbutton WHILE connected to pc via USB
When i flash OP's image root seems to stick, but when I install Magisk Manager and update via App its gone...

Chiptrip said:
Okay, so now that huawei isn't giving away unlock Codes anymore, ist there another way to unlock the bootloader?
Click to expand...
Click to collapse
I have succeeded to get the Unlock code today (May 27, 2018) via the web pages.
---------- Post added at 12:29 ---------- Previous post was at 12:26 ----------
PeterMarkoff said:
well it's COL, i don't think exact version makes difference, but waiting for someone else to try
but i ain't gonna do it until i know how to backup stock ramdisk
also be aware with root you can't install OTA updates anymore
Click to expand...
Click to collapse
You do not need to wait, it is part of released stock firmware 104.

MachineGunJinx said:
somehow i cant boot into fastboot on my honor 10. any help?
Click to expand...
Click to collapse
adb reboot bootloader
after all you will be dealing with ADB anyway, so no point using physical buttons

You can insert an USB cable (connected to the pc) into the phone while pressing vol- to enter fastboot.

worked fine for me, thx a lot

cplpro18 said:
worked fine for me, thx a lot
Click to expand...
Click to collapse
are you staying on EMUI with root or flashed also some custom ROM? what were exact steps, did you wipe data in process? lazy to set up phone again but at least root would be nice until i well move to custom ROM completely

PeterMarkoff said:
are you staying on EMUI with root or flashed also some custom ROM? what were exact steps, did you wipe data in process? lazy to set up phone again but at least root would be nice until i well move to custom ROM completely
Click to expand...
Click to collapse
Yes i'm going to stay on EMUI with root - at least there is a stable custom rom, which seems to have performance benefits.
Bought my Honor 10 last friday and got my bootloader unlock code still by Huawei (26. of mai is the deadline for already sold smartphones by Huawei and Honor, or am i wrong?!). Activated USB debugging, installed minimal adb driver, rebooted to fastboot and unlocked the bootloader. After the reboot, a factory reset was done automatically (mercifully i just set up my google login and a few apps)... Don't remeber i had to choose between a factory reset or not but i thing i had no choice.
Activated USB debugging again, rebooted to bootloader and flashed the magisk.img.
Finally installed the magisk APK and flashed magisk again in the app.
Root works fine!

cplpro18 said:
Bought my Honor 10 last friday and got my bootloader unlock
Activated USB debugging again, rebooted to bootloader and flashed the magisk.img.
Finally installed the magisk APK and flashed magisk again in the app.
Root works fine!
Click to expand...
Click to collapse
thanks, just needed the last part, have already unlocked BL for few days, i will give a yet to root today, seem same as instructions in OP though someone claimed issues
unlock page should be online until July 24 for devices released before may 24, do any newer model should not be possible even before end of July

OK, so successfully rooted, easy peasy, just flashed magisk.img from 1st post containing Magisk 16.4 through ADB, then installed Magisk manager 5.6.4 which was crashing on launch no matter what (clearing data, all permissions), then installed Magisk manager 5.7.0 which works fine
finally enjoying adaway, mixplorer root access, stored wifi passwords and finally I can have proper SD Maid and uninstall facebook services which I could just disable and other useless google/huawei crap
edit: there is problem after reboot, magisk manager 5.7.0. again crash on launch and so do all apps requiring root
edit 2: for change uninstalling and installing 5.6.4 now works, it seem currently installed version doesn't work and always need to switch to different version from previous which will crash on launch after reboot, upgrade from within 5.6.4 succesful and I changed my channel from stable 16.0. to beta 16.4, will see if it will persist after root
edit 3: it seem combination Magisk manager 5.7.0 + Magisk 16.4 persist after reboot. tried multiple reboots, this combination finally persist although Magik manager main screen it's odd it's showing only Installed version and Uninstall, no other options like checking CTS (which passed before)

I have unlocked BL but I am unable to flash the ramdisk.. fastboot says Phone Unlocked, FRP Lock
Code:
[email protected] ~/Downloads $ fastboot flash ramdisk col-magisk-tlxx.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (6558 KB)...
OKAY [ 0.273s]
writing 'ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.278s
edit: I had to again switch the OEM unlock to "on" and added my gmail account. Then it worked, FRP unlocked

5ulo said:
I have unlocked BL but I am unable to flash the ramdisk.. fastboot says Phone Unlocked, FRP Lock
Code:
[email protected] ~/Downloads $ fastboot flash ramdisk col-magisk-tlxx.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (6558 KB)...
OKAY [ 0.273s]
writing 'ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.278s
Click to expand...
Click to collapse
Hello, in next days i will get the Honor 10, how have u unlocked your bootloader ? By this thread ? I ask that because my country isn't in the list Country on the Huawei website for now.

@Rom: unlocked via emui.com.. received the unlock key instantly

General Official Android 13 firmware is now available

It was posted about 2 hours ago on Asus website, here is the direct link: https://dlcdnets.asus.com/pub/ASUS/...300-2304-user.zip?model=rog phone 5 （zs673ks）
I just updated and phone runs smooth, no data loss during upgrade, magisk and lsposed works.

MarekPietrzak said:
It was posted about 2 hours ago on Asus website, here is the direct link: https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS673KS/UL-ASUS_I005_1-ASUS-33.0210.0210.200-1.1.300-2304-user.zip?model=rog phone 5 （zs673ks）
I just updated and phone runs smooth, no data loss during upgrade, magisk and lsposed works.
Click to expand...
Click to collapse
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo

Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
rami88436 said:
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Click to expand...
Click to collapse

MarekPietrzak said:
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
Click to expand...
Click to collapse
MarekPietrzak said:
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
Click to expand...
Click to collapse
hey, Thanks for replay, i am facing now another messeges.
1- the phone does not charging at all
2- when i plug in into chrage its reboot again and again.
3- the bootloader is open, but when i try to flash any files through bootloader i get:
FAILED (Status read failed (Too many links))
or
FAILED (remote: 'Warning: battery's capacity is very low
to recovery mode i am unable to go there
i tried boot or flash the twrp.img also only boot.img also flash_raw_and_wipe_data.cmd
nothing helps me!!!

Hello, can you try to keep phone on charger for a few hours? Maybe it will charge enough to enter recovery mode. You should never flash twrp by fastboot on a/b devices as they don't have recovery partition. Please restore stock boot.img extracted from payload.bin and after this try booting into fastbootD, not fastboot and then attempt flashing complete firmware package (raw). To boot into fastbootD, keep holding volume keys, when you see a bootloader screen use volume keys to select option "recovery mode". You should now enter stock recovery. Ussing vol keys select option "enter fastboot". You should be now in fastbootD. This is possible only with boot.img without twrp installed as fastbootD is a part of stock recovery, magisk is fine.
Remember to perform all flashing operations with usb port on the left side, the bottom one does not work in bootloader. And make sure you are using latest adb/fastboot binaries, these from popular auto-installers are usually outdated and may cause errors during flashing.

MarekPietrzak said:
Hello, can you try to keep phone on charger for a few hours? Maybe it will charge enough to enter recovery mode. You should never flash twrp by fastboot on a/b devices as they don't have recovery partition. Please restore stock boot.img extracted from payload.bin and after this try booting into fastbootD, not fastboot and then attempt flashing complete firmware package (raw). To boot into fastbootD, keep holding volume keys, when you see a bootloader screen use volume keys to select option "recovery mode". You should now enter stock recovery. Ussing vol keys select option "enter fastboot". You should be now in fastbootD. This is possible only with boot.img without twrp installed as fastbootD is a part of stock recovery, magisk is fine.
Remember to perform all flashing operations with usb port on the left side, the bottom one does not work in bootloader. And make sure you are using latest adb/fastboot binaries, these from popular auto-installers are usually outdated and may cause errors during flashing.
Click to expand...
Click to collapse
I've tried leaving it on overnight and it never charges, there's even no charging lights.
Yesterday I tried flashing via Bugjeager and it didn't work either (betwenn to android devices)
Although the bootloader is unlocked, it gives me a Not Allowed In Lock State message!
the current version of the installed firmware is that old that i flashed WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw, it is non extractable so i cant get the boot.img of it!

I am attaching here the matching boot.img for your 2101.95 firmware. Your phone boots to bootloader as I can see on the video but cannot enter recovery as you have corrupted your boot partition. Can you pm me output of fastboot getvar all command? Please do not post it publicly as it may contain private data such as serial numbers. Good luck!
Are you sure that you have unlocked bootloader? I understand that you have relocked your bootloader and since then your phone never booted into working system. It is not possible to unlock bl with fastboot, only with asus app which requires working Android system

MarekPietrzak said:
I am attaching here the matching boot.img for your 2101.95 firmware. Your phone boots to bootloader as I can see on the video but cannot enter recovery as you have corrupted your boot partition. Can you pm me output of fastboot getvar all command? Please do not post it publicly as it may contain private data such as serial numbers. Good luck!
Are you sure that you have unlocked bootloader? I understand that you have relocked your bootloader and since then your phone never booted into working system. It is not possible to unlock bl with fastboot, only with asus app which requires working Android system
Click to expand...
Click to collapse
wow you are alive haha i thought you not gonna answer me again. ok just 1 second

rami88436 said:
wow you are alive haha i thought you not gonna answer me again. ok just 1 second
Click to expand...
Click to collapse
Sometimes I can be a bit slow to respond as I am on the university during day. Hopefully your issue seems to be possible to be solved just by flashing raw firmware and wiping data partition.

so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?

rami88436 said:
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Click to expand...
Click to collapse
if youre still stuck, try to fastboot flash raw firmware and reroot and re update again. twrp only works for me with the magisk twrp installer but then you'll have to re flash patched image as it will remove root

chairman011 said:
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
Click to expand...
Click to collapse
try root your phone through kirnal su

chairman011 said:
if youre still stuck, try to fastboot flash raw firmware and reroot and re update again. twrp only works for me with the magisk twrp installer but then you'll have to re flash patched image as it will remove root
Click to expand...
Click to collapse
hahaha, the owner of this thread had helps me a lot but no way and yesterday i have been lost my imei and isn and the rest.., that was because i tried using miflash.

I did it in the same way as you, just after OTA i installed magisk to inactive slot and rebooted. Maybe you have some incompatible magisk modules which caused bootloop on A13.
chairman011 said:
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
Click to expand...
Click to collapse

MarekPietrzak said:
I did it in the same way as you, just after OTA i installed magisk to inactive slot and rebooted. Maybe you have some incompatible magisk modules which caused bootloop on A13.
Click to expand...
Click to collapse
Oh ok ok makes sense. I had curl module installed. I loved android 13 but I'ma stay on 12 cause the modified read/write script only works on Android 12 and 11 and I need it to uninstall bloatware. Disabling them isn't good enough for me lol I gotta uninstall them completely. I can only do that if system is read/write and this script flashed through two works great to have read/write system. Thank you though
rami88436 said:
hahaha, the owner of this thread had helps me a lot but no way and yesterday i have been lost my imei and isn and the rest.., that was because i tried using miflash.
Click to expand...
Click to collapse
Oh ok ok makes sense. Usually when I face a brick problem I just flash raw firmware fastboot

Actually you can debloat fully systemless, just create magisk module which replaces bloatware directories with empty folders. Or even better use this: https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
It is an automated way to make packages fully disappear without remounting system as rw. This module replaces them with empty folders, just like in the manual solution. The packages disappear from system completely and if you install any debloated app from play store or apk it will be installed as user (non-system) app.
chairman011 said:
Oh ok ok makes sense. I had curl module installed. I loved android 13 but I'ma stay on 12 cause the modified read/write script only works on Android 12 and 11 and I need it to uninstall bloatware. Disabling them isn't good enough for me lol I gotta uninstall them completely. I can only do that if system is read/write and this script flashed through two works great to have read/write system. Thank you though
Click to expand...
Click to collapse

MarekPietrzak said:
Actually you can debloat fully systemless, just create magisk module which replaces bloatware directories with empty folders. Or even better use this: https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
It is an automated way to make packages fully disappear without remounting system as rw. This module replaces them with empty folders, just like in the manual solution. The packages disappear from system completely and if you install any debloated app from play store or apk it will be installed as user (non-system) app.
Click to expand...
Click to collapse
Oh wow thank you man I'll give it a shot.

I found a gui-based app on github to systemlessly debloat, it is easier to use than this script I posted link to. Here is the link: https://github.com/sunilpaulmathew/De-Bloater

Does anyone have the full RAW firmware, flashed via fastboot? Thank you all

ThienAn2023 said:
Does anyone have the full RAW firmware, flashed via fastboot? Thank you all
Click to expand...
Click to collapse
Mod. edit: private link removed. alecxs

Question ROOT

Hi, I would like to ask if anyone knows how to get root permissions and install a super su or superuser application, by the way, I really care about not bricking my phone because it is my only phone that I am able to use as a daily driver. i mainly want to remove system apps and use drivedroid app

I imagine the process for the G62 would be similar to the G60. See this thread

@synakszymon09 Please check your PMs immediately.

magisk work on all devices android 6+: https://github.com/topjohnwu/Magisk --- i have also one phone and do it with magisk.

what a phone do you have. if you have a xiaomi you must unlock the bootloader. MAKE SURE: Unlocking erase your data. so make a backup first if you are sure

ABC00012345 said:
what a phone do you have. if you have a xiaomi you must unlock the bootloader. MAKE SURE: Unlocking erase your data. so make a backup first if you are sure
Click to expand...
Click to collapse
I made a post on Moto g62 so it's probably logical that I use Moto g62 I'm quite skeptical about magisk unless it's the only method because the last time I used it I broke my phone and spent PLN 80 (about $20) on a service center that still didn't fix it

synakszymon09 said:
I made a post on Moto g62 so it's probably logical that I use Moto g62 I'm quite skeptical about magisk unless it's the only method because the last time I used it I broke my phone and spent PLN 80 (about $20) on a service center that still didn't fix it
Click to expand...
Click to collapse
is there a other method

ABC00012345 said:
is there a other me Could you write step by step how to root this phone without risk of brickingCould you write step by step how to root this phone without risk of bricking
Click to expand...
Click to collapse

its extremaly simple
unlock bootloader
download the firmware for phone
extract boot.img and copy to phone /sdcard
install magisk
open magisk and flash magisk to image file
copy /download/magisk_boot.img to pc
restart phone to fastboot
flash magisk_boot.img to both boot_a & boot_b
flash vbmeta --disable verification & verity
flash vbmeta_system --disable verification & verity *not mandatory
flash vbmeta_boot --disable verification & verity *not mandatory
restart phone

please see my comment - it is extremely basic - as an added messure as i have had magisc not be completely functional ( and this is frrom reasearching but there is a slight difference between flashing the device directly and flashing the boot.img file and then having to flash thatt via fastboot) but as I say it is just an added measure
re-flash the device from magisk after it has been booted just to cement the root processes - and you shouldnt have any issues at all.

smiley.raver said:
its extremaly simple
unlock bootloader
download the firmware for phone
extract boot.img and copy to phone /sdcard
install magisk
open magisk and flash magisk to image file
copy /download/magisk_boot.img to pc
restart phone to fastboot
flash magisk_boot.img to both boot_a & boot_b
flash vbmeta --disable verification & verity
flash vbmeta_system --disable verification & verity *not mandatory
flash vbmeta_boot --disable verification & verity *not mandatory
restart phone
Click to expand...
Click to collapse
I have a problem even with the first step because my computer does not see the phone in fastboot mode (adb works as it should) and when I try to install the drivers, the progress bar stops at some point

synakszymon09 said:
I have a problem even with the first step because my computer does not see the phone in fastboot mode (adb works as it should) and when I try to install the drivers, the progress bar stops at some point
Click to expand...
Click to collapse
place your phone into fastboot mode - power and volume down or enter abd command to adb reboot bootloader

This is the most obvious thing that I didn't even check in any guide, I just guessed

did you get it to work?

smiley.raver said:
did you get it to work?
Click to expand...
Click to collapse
unfortunately not, but I'll try to install these drivers again because I have another computer and now I'm using linux (I'm going to install them via wine HQ)

IT WORKED and that's even without drivers I got a lot of numbers and letters after typing fastboot oem get_unlock_data

[[email protected] szymon]# fastboot oem get_unlock_data
< waiting for any device >
(bootloader) Unlock data:
(bootloader) 3A95314132950537#5A593232473337
(bootloader) 4D4D57006D6F746F2067360000#A9D0
(bootloader) B4207FCFBBEB957812FBEDF94C05075
(bootloader) CA3D171765180BD2F9B98DDBF55AC#4
(bootloader) D91C0FC000000000000000000000000
OKAY [ 0.029s]
Finished. Total time: 0.029s
[[email protected] szymon]#

unfortunately it doesn't work as it should

out of date, I managed to unlock it, I just didn't remove the space from the string before