Database Info

[Q] NOT your average stuck in bootloop

Bear with me: Right now my nexus is stuck in a bootloop. My nexus had been partially rooted, everytime i went to download the OTA 5.0.1. update it would just take me to TWRP, and i didn't know what to do with that. So I finally tried to fully root the phone, and also use TWRP to install the OTA update. Now I'm stuck, I've tried wiping the cache/factory reset. How do I got about flashing it back to stock without losing all my data?
(apologies for the title, I thought originally that I had killed mtp and adb, but I figured out how to get them back just after posting)
Thanks!

As I saw your post before the edit.... Stop using toolkits and read about adb. If it's bootlooping then it's 95% not bricked so don't panic and read the guides
Just download system.img you want and fastboot it
Edit -
Don't see this as me being mean or a ****. This is stuff everyone needs to know, it's really not hard at all so don't worry. Once you've used it a few times you'll wonder why you ever used toolkits

Ben36 said:
As I saw your post before the edit.... Stop using toolkits and read about adb. If it's bootlooping then it's 95% not bricked so don't panic and read the guides
Just download system.img you want and fastboot it
Edit -
Don't see this as me being mean or a ****. This is stuff everyone needs to know, it's really not hard at all so don't worry. Once you've used it a few times you'll wonder why you ever used toolkits
Click to expand...
Click to collapse
I don't think you're being a ****. I'm very grateful for your input. I used to be very into jailbreaking when I had an iPhone, but i haven't been able to put the same time towards getting the hang of rooting (which I think has a steeper learning curve to begin with|). I sort of understand adb but I obviously need to learn more. I've been using the toolkit because it was simpler. I remember from trying to use adb before that I need to place the files I want to transfer in the same folder as adb (i think?) but I could never get that to work.
I also don't understand system.img.'s relevance here. I'm not getting the "Error: Update package missing system.img" error.

The reason I say read the guides is simply it saves me or anyone else typing out a massive guide that already exists in many places.
If you're looping then something is more than likely wrong with the system not the data. So flashing just the system will keep your data safe (as long as you flash the same android version as you previously had, lollipop or kitkat)
You need to be in the bootloader not recovery and use the command fastboot flash system system.img
Google img's are here - https://developers.google.com/android/nexus/images
(just keep unzipping until you find the individual img files)

photobumm said:
I don't think you're being a ****. I'm very grateful for your input. I used to be very into jailbreaking when I had an iPhone, but i haven't been able to put the same time towards getting the hang of rooting (which I think has a steeper learning curve to begin with|). I sort of understand adb but I obviously need to learn more. I've been using the toolkit because it was simpler. I remember from trying to use adb before that I need to place the files I want to transfer in the same folder as adb (i think?) but I could never get that to work.
I also don't understand system.img.'s relevance here. I'm not getting the "Error: Update package missing system.img" error.
Click to expand...
Click to collapse
He's saying to flash a system image to get you up and running again, and I agree that that is what you should do. As far as placing the files in the same folder as adb and fastboot is concerned (you'll use fastboot to flash the image), you need to do just that. I created a folder on my desktop called "ADB" and that's where both adb and fastboot are, as well as all the files that I flash with fastboot ie. system images, recoveries, etc... Here's a great guide to get you going with adb and fastboot- http://forum.xda-developers.com/showthread.php?t=2277112
Now when you go to flash it, if you decide to use the flash-all.bat to flash everything (the full factory image) and bring you back to stock, you'll have to open the .bat file with a text editor and remove the "-w" from the script and that way it won't wipe your phone. If you want to just reinstall the OS without everything else (worth a shot), just flash the system with the command
Code:
fastboot flash system system.img
and that should get you running again. If what I just said is confusing, read the guide I posted and it should become clear.
Here is where you'll download the factory image from- https://developers.google.com/android/nexus/images
Just unzip it, pull the system.img out and place it in the same folder that fastboot is in and flash away.
And one final thing- definitely avoid toolkits at all costs. You spent a good chunk of change on your phone, take the time to learn how to mod it the correct way.
Good luck!

_MetalHead_ said:
He's saying to flash a system image to get you up and running again, and I agree that that is what you should do. As far as placing the files in the same folder as adb and fastboot is concerned (you'll use fastboot to flash the image), you need to do just that. I created a folder on my desktop called "ADB" and that's where both adb and fastboot are, as well as all the files that I flash with fastboot ie. system images, recoveries, etc... Here's a great guide to get you going with adb and fastboot- http://forum.xda-developers.com/showthread.php?t=2277112
Now when you go to flash it, if you decide to use the flash-all.bat to flash everything (the full factory image) and bring you back to stock, you'll have to open the .bat file with a text editor and remove the "-w" from the script and that way it won't wipe your phone. If you want to just reinstall the OS without everything else (worth a shot), just flash the system with the command
Code:
fastboot flash system system.img
and that should get you running again. If what I just said is confusing, read the guide I posted and it should become clear.
Here is where you'll download the factory image from- https://developers.google.com/android/nexus/images
Just unzip it, pull the system.img out and place it in the same folder that fastboot is in and flash away.
And one final thing- definitely avoid toolkits at all costs. You spent a good chunk of change on your phone, take the time to learn how to mod it the correct way.
Good luck!
Click to expand...
Click to collapse
So I have adb and fastboot running. And I changed the flash-all.bat file. However, I don't understand what I do now? I downloaded the Hammerhead zip and it has a bunch of things in it. Which files do I put into the adb/fastboot folder and how do I then flash them?
In the hammerhead file it lists the bootloader, flash-all, radio and then a zip file "image-hammerhead...". What files am I using and what is the code that I input? Is this the same sa flashing a rom?
I also tried placing the system.img in the adb folder, and then using the
Code:
fastboot flash system system.img
but it gives me an error "cannot load 'system.img'

So now my issue is I get a "error: could not load 'system.img'. after running
Code:
fastboot flash system system.img [code/] . I also tried with boot.img. Same error.
I ran the "flash all" script, by accident, a screenshot of the terminal is attached.. I'm still stuck in a the boot loop, however, and if try to enter recovery mode an android lying down with a red triangle is present. The above "error: could not load..." is still present.

Create a folder and put fastboot in it.
So you unzipped the stock image. You said you have some images in the folder and a zip image.
Unzip that second zip.
There you will find the rest of the images you need.
Now take the recovery, bootloader, system, userdata, cache, and radio images and move them into the folder which you created for fastboot.
Rename the bootloader image to bootloader. img
Now when looking at that open folder containing all the images and fastboot hold down shift and left click and select "open command promt from window"
Type
/fastboot erase bootloader
/fastboot flash bootloader bootloader.img
/fastboot reboot-bootloader
/fastboot erase recovery
/fastboot flash recovery recovery.img
/fastboot erase radio
/fastboot flash radio radio.img
Repeat for the rest of the image files
Finally type /fastboot reboot
Profit.
---------- Post added at 10:54 PM ---------- Previous post was at 10:51 PM ----------
P. S. Make sure your phone is booted in fastboot mode first.

Oh and that android is stock recovery

U fixed it?

So for some reason I still kept getting that error. I ended up restoring to stock using the nexus root toolkit. So it all worked out in the end.

How to unroot, lock bootloader and go back to stock?

For background, I have Verizon pixel 2 and am using a Mac.
I went down a massive rabbit hole last night reading through these forums and all the posts and was able to unlock bootloader, flash the January OTA and then root by doing the modified boot file with magisk. (interestingly enough the booting into recovery gives me red ! Over a dead Android and I could not load the OTA that way, nor did the adb sideload OTA comand work either, I had to push the extracted walleye img and then the zip file as discussed in one of the steps in some other thread here)
So anywho, in the end I now have a phone that gives me 2 errors when it reboots, one for unlocked bootloader and another for root telling me something is wrong with my phone and i should contact the manufacturer (which I read on here is normal), but my biggest issue is that my ADT alarm app doesn't work anymore (even if i check it off for hide in magisk). I feel like the root is just not worth it for me and I want to revert to completely stock image, even if it resets my phone and I have to re back everything up all over again like did when i had to do the unlocking of the boot loader.
So -- What are the steps I should take?
1)uninstall magisk from magisk manager?
2)delete magisk manager?
The above will unroot me, correct?
3)Do I push the stock boot image file onto the phone?
4) do I have to repush the latest OTA walleye image and zip file onto the phone again?
5) do I then do the adb reboot and do the flashing lock command (same command i did to unlock the boot loader) to lock up the bootloader and reset to stock?
If someone could be as explicit as possible in correctiong or validating my steps above it would be much, much appreciated.
I don't want to do any more unnecessary steps in flashing things than is needed so if I have extra steps above (perhaps 4 is not needed?) Let me know.
Thanks

Proceed with Caution
I am not an expert by any means, but can speak from personal experience. I was in the exact same situation as you. I followed the detailed steps to unlock the bootloader on my pixel 2, received similar issues, and the same prompt when the phone rebooted. All that to say proceed with caution.
My thoughts on questions 1 & 2: I personally wouldn't recommend you remove or delete magisk from the manager. When I did i had to reinstall it via twrp. My phone functioned fine, apart from the error at reboot.
My thoughts on questions 3 -5: When I followed the steps on XDA for your questions here I ended up bricking my Pixel 2 with locked bootloader from Verizon. Probably an error on my part, but wouldn't want someone else to go through the headache, hours of issues, and then an expensive paper weight.
My suggestion would be to:
1. Leave your phone as is and attempt to trouble shoot the app or apps you are having issue with
2. contact Google support on your phone and see if they would replace it
3. wait for an established method to unroot the pixel 2 here
Thankfully Google replaced my phone due to the error after rebooting, prior to me bricking it. I knew I had a replacement phone coming. So I attempted to go back to stock and that is when I messed it up.
Note sure this is exactly what you were looking for, but hope this helps you.

Dozens of posts with hundreds of pages on how to root but no advice on how to go back to stock cleanly?

iridium7777 said:
Dozens of posts with hundreds of pages on how to root but no advice on how to go back to stock cleanly?
Click to expand...
Click to collapse
Your version is Verizon which is making things more complicated. Generally when the bootloader is unlocked, you just hit flash-all.bat and then relock the phone. Given that the Verizon I'm not sure.
So you are on stock ROM with all these apks loaded ? If you go to settings, then do a factory data reset, you'll reset the phone back to stock and completely wipe the phone and return it to stock, at that point you can go into bootloader mode and relock.
Again your bootloader is unlocked, so the flash-all is your best option. If you see the red exclamation point with the error android laying on his back, you press power and up volume and toggle that and it will bring in the stock recovery which you can sideload the OTA however it may fail since you have magisk.
I bought my phone stock last year and have not rooted it or modified it in anyway. Too many problems and it only gets harder and harder as Google releases a new phone.

@mikeprius -- thank you for replying. after reading more on here, it seems like that's the way to go -- flash-all script, seems like i don't really need to do 1&2 that i wrote above as the flash-all will wipe that out by itself.
at that point i should be running the latest stock 8.1 but with an unlocked bootloader (and according boot up message screen) and i should be able to re-do the fastbook unlocking command to lock the phone back up.
(and yes, after reading even more now -- and i tried this yesterday -- i completely missed the portion about PWR + Vol Up button, that's why i think i had that issue, but still, i was able to push the update by pushing img and then the zip through).

iridium7777 said:
@mikeprius -- thank you for replying. after reading more on here, it seems like that's the way to go -- flash-all script, seems like i don't really need to do 1&2 that i wrote above as the flash-all will wipe that out by itself.
at that point i should be running the latest stock 8.1 but with an unlocked bootloader (and according boot up message screen) and i should be able to re-do the fastbook unlocking command to lock the phone back up.
(and yes, after reading even more now -- and i tried this yesterday -- i completely missed the portion about PWR + Vol Up button, that's why i think i had that issue, but still, i was able to push the update by pushing img and then the zip through).
Click to expand...
Click to collapse
If I were in your situation and the bootloader is unlocked, just use flash-all which has a wipe script then call it a day. I think trying to screw around even more is just a waste of time and I wouldn't even bother with the OTA, just erase and flash stock. You don't have to relock your bootloader if you don't want to, if you stay fully stock you may still be able to get OTA updates. I'm not sure if a bootloader locked is required someone can chime in as it has been awhile since I've done this, but over 1 yr ago, I just kept the bootloader unlocked, kept things stock and everything was good to go. Obviously there are security issues with an unlocked bootloader, but I'm sure you know this already

@mikeprius you keep saying reset/erase, do you suggest i re-set the phone and then flash the stock image?
i was just going to flash the stock image, i figured it already wipes the phone, and locking the bootloader would wipe it again, so what's the point of erasing all data prior?

Not to hijack this thread, but a question to add... I thought that there were kernels that would mask certain things to allow all of those apps to work, and get rid of the "problem with device" message.
Is that correct?

iridium7777 said:
@mikeprius you keep saying reset/erase, do you suggest i re-set the phone and then flash the stock image?
i was just going to flash the stock image, i figured it already wipes the phone, and locking the bootloader would wipe it again, so what's the point of erasing all data prior?
Click to expand...
Click to collapse
Just flash the stock images. It will auto reset.
Again, don't mess with anything just flash stock images, then go from there.
Also flash the newest version of the stock images out there. The pixel 2 will error if you try to downgrade any version.

here are all the steps to UNROOT and LOCK the boot loader on your Pixel 2 on a Mac (windblows users simply ignore all the "./" references).
1) download the latest ADB tools from google
2) download the latest factory Walleye image
3) unzip files from 1&2 into a common directory
4) edit flash-all.sh file and add "./" infront of every instance of "fastboot" in the script [windows users ignore this step]
5)hook up your phone to your computer in debug and file transfer mode. check that "./adb devices" loads your devide
6)type " ./adb reboot bootloader"
7) check that your device is still connected by typing "./fastboot devices"
8) type "./flash-all.sh"
===the script will run and your phone will be restored to stock, and UNROOTED. upon boot up skip through all of the setup steps and get to the phone settings as fast as you can. enable developer option, enable debug mode, set phone to data transfer ====
9) check that your phone is connect to your computer by "./adb devices"
10) type "./adb reboot bootloader"
11) check your devices is still connected by "./fastboot devices"
12) type "./fastboot flashing lock"
===== this will re-wipe your device again, you'll see the circle of death, and this will LOCK your boot loader back up again======
side note, feel free to skip over the steps where you check that your phone is still connected to the computer (./fastboot devices) if you're less paranoid and comfortable.

iridium7777 said:
here are all the steps to UNROOT and LOCK the boot loader on your Pixel 2 on a Mac (windblows users simply ignore all the "./" references).
1) download the latest ADB tools from google
2) download the latest factory Walleye image
3) unzip files from 1&2 into a common directory
4) edit flash-all.sh file and add "./" infront of every instance of "fastboot" in the script [windows users ignore this step]
5)hook up your phone to your computer in debug and file transfer mode. check that "./adb devices" loads your devide
6)type " ./adb reboot bootloader"
7) check that your device is still connected by typing "./fastboot devices"
8) type "./flash-all.sh"
===the script will run and your phone will be restored to stock, and UNROOTED. upon boot up skip through all of the setup steps and get to the phone settings as fast as you can. enable developer option, enable debug mode, set phone to data transfer ====
9) check that your phone is connect to your computer by "./adb devices"
10) type "./adb reboot bootloader"
11) check your devices is still connected by "./fastboot devices"
12) type "./fastboot flashing lock"
===== this will re-wipe your device again, you'll see the circle of death, and this will LOCK your boot loader back up again======
side note, feel free to skip over the steps where you check that your phone is still connected to the computer (./fastboot devices) if you're less paranoid and comfortable.
Click to expand...
Click to collapse
hey there. what is the command suppose to look like? every combination I try gives me an error:
first, I don't even enter the Fastboot command the same wayit given me an error:
Asads-MacBook:~ asad$ ./fastboot devices
-bash: ./fastboot: No such file or directory
so I try this: Asads-MacBook:~ asad$ fastboot devices
[serial #] fastboot
these are all the errors I get:
Asads-MacBook:~ asad$ cd /Users/asad/Desktop/walleye-opm1.171019.021
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: fastboot./: No such file or directory
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: ./fastboot: No such file or directory
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
fastboot: usage: unknown command ./flash
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: fastboot./: No such file or directory
...
how is the command suppose to look that I can edit it the right way?

"fastboot: No such file or directory" means that you didn't do step 1, step 3 on the file you didn't download, and there should probably be a "cd /<whatever the 'common directory'>" is. (I just created a directory named adb. That's good enough for me to know what it's for.)
You have to download adb and fastboot (which come in the adb tools file), unzip them to whatever directory you're going to use for flashing the phone, and cd to that directory.
Then, since you're evidently on MacOS, each command has to have ./ in front of it (that says "the current directory"). Try all that, then see what happens.

Rukbat said:
"fastboot: No such file or directory" means that you didn't do step 1, step 3 on the file you didn't download, and there should probably be a "cd /<whatever the 'common directory'>" is. (I just created a directory named adb. That's good enough for me to know what it's for.)
You have to download adb and fastboot (which come in the adb tools file), unzip them to whatever directory you're going to use for flashing the phone, and cd to that directory.
Then, since you're evidently on MacOS, each command has to have ./ in front of it (that says "the current directory"). Try all that, then see what happens.
Click to expand...
Click to collapse
yayy! that worked!
so i had adb and fastboot in a folder (platform-tools) and i had the factory image in its own seperate folder (walleye-files). i was making the cd; walleye folder and trying to flash-all.sh there.
so i had to put the files from the walleye folder into the platform-tools folder. Then I made platform-tools the cd. now when . i could now follow all the steps from 4-12 and got the pixel 2 the way it was OTB.
thanks!

Great! I'm not a Mac expert (last time I used one was the 128K Mac in 1985), so I'm not sure how to export a path in MacOs, so I gave you the complicated way, but you got it done anyway. (If you ever find out how to add the platform-tools folder to your path, you can leave adb and fastboot in there and keep the ROMs [walleye] in their own folder, cd to it and adb and fastboot will still work.)

January images

The factory images are up my friends. Go pick what you need :good:
https://support.google.com/pixelphone/thread/24852169?hl=en
Added bonus: Here is a link to the January stock boot and magisk patched boot.img's
This is for the global build #QQ1B.200105.004 :good:
https://drive.google.com/file/d/1Dgh7w0r4ZzPZ7qOePhfADjPuLp-K84yO/view?usp=drivesdk
PS: I used stable magisk 20.2 to patch the boot.img

Dey Up Bruv...
Im downloading mine already <3

OTA is only 12MB.

Only 1st january, not 5th?

can confirm Jan update works with magisk root and ed_xposed. Thanks for updating us with the update availability!

Badger50 said:
The factory images are up my friends. Go pick what you need :good:
https://support.google.com/pixelphone/thread/24852169?hl=en
Added bonus: Here is a link to the January stock boot and magisk patched boot.img's
This is for the global build #QQ1B.200105.004 :good:
https://drive.google.com/file/d/1Dgh7w0r4ZzPZ7qOePhfADjPuLp-K84yO/view?usp=drivesdk
PS: I used stable magisk 20.2 to patch the boot.img
Click to expand...
Click to collapse
Hi, and thx.
But can u share a small how-to, for updating, step by step? Just wanna be sure that I on the right way.

lapapunk said:
Hi, and thx.
But can u share a small how-to, for updating, step by step? Just wanna be sure that I on the right way.
Click to expand...
Click to collapse
In a nutshell: This is how I do it. Others MMV
1. Make sure platform-tools are up to date. The latest is 29.0.6. And use a USB A to USB C cable.
2. Download factory image, extract it, extract the image.zip, move boot.img to your phones internal storage.
3. Disable all magisk modules and substratum themes, remove face ID and reboot.
4. Patch the stock boot.img, and move the patched.img to your pc platform-tools folder, then turn phone off.
5. Move all your necessary factory image files to your platform-tools folder: bootloader, radio, the still zipped image.zip and the flash-all.bat file for Windows machines. Using notepad or whatever, edit the flash-all.bat file and remove the -w from the script, leaving a single space between the remaining words, save your edit.
6. Put phone in bootloader mode, and plug it into your pc. Open a command prompt {See 6A} on your platform-tools folder, type in: fastboot devices. If your device is recognized with it's ID, your good to go. Then, what I do is go into my platform-tools folder and double click the flash-all.bat file to start the process. Let it finish, and let your device boot up.
6A. For Win 10 users. Open a command prompt by typing "cmd" in the search box, then open the prompt. You'll see C:\Users\<your name> with the flashing cursor. Then type "cd" then hit the space bar. Then drag and drop your completed platform-tools folder in the command line, and let it populate. Then hit enter, and now you can issue your fastboot commands :good:
7. Once it boots ok with the update, turn phone off, and go into bootloader mode. Connect to pc, and fastboot the patched boot.img to both slots with..
fastboot flash boot magisk_patched.img --slot=all
And let it boot up with root.
8. Then start enabling your magisk modules a couple at a time. Be warned, sometimes, not all magisk modules play nicely with monthly updates, so take it slow. Luckily, January is cool with the @Tulsadiver mods, and the Active Edge mods from what I've seen.
9. And there ya go. Ok....so it was a little bigger than a nutshell!

When doing the above flashing use an A to C, not the supplied cable. If you're already in a flash failure with the supplied cable grab an A to C and flash again without doing a factory reset or taking any other actions to try and get it up; this will usually get it booting as if the first flash was successful.
Edit... I know you would have put it in there if you'd remembered Badg, it's hard to remember every little speed bump when whipping up a set of instructions like that.

@Badger50
Ok, thx.
But what about this guide? On my pixel 2xl this method worked great. Will it work on 4xl?

Badger50 said:
In a nutshell: This is how I do it. Others MMV
1. Make sure platform-tools are up to date. The latest is 29.0.5. And use a USB A to USB C cable.
2. Download factory image, extract it, extract the image.zip, move boot.img to your phones internal storage.
3. Disable all magisk modules and substratum themes, remove face ID and reboot.
4. Patch the stock boot.img, and move the patched.img to your pc platform-tools folder, then turn phone off.
5. Move all your necessary factory image files to your platform-tools folder: bootloader, radio, the still zipped image.zip and the flash-all.bat file for Windows machines. Using notepad or whatever, edit the flash-all.bat file and remove the -w from the script, leaving a single space between the remaining words, save your edit.
6. Put phone in bootloader mode, and plug it into your pc. Open a command prompt on your platform-tools folder, type in: fastboot devices. If your device is recognized with it's ID, your good to go. Then, what I do is go into my platform-tools folder and double click the flash-all.bat file to start the process. Let it finish, and let your device boot up.
7. Once it boots ok with the update, turn phone off, and go into bootloader mode. Connect to pc, and fastboot the patched boot.img to both slots with..
fastboot flash boot magisk_patched.img --slot=all
And let it boot up with root.
8. Then start enabling your magisk modules a couple at a time. Be warned, sometimes, not all magisk modules play nicely with monthly updates, so take it slow. Luckily, January is cool with the @Tulsadiver mods, and the Active Edge mods from what I've seen.
9. And there ya go. Ok....so it was a little bigger than a nutshell!
Click to expand...
Click to collapse
You're an absolute legend mate, thanks!!

lapapunk said:
@Badger50
Ok, thx.
But what about this guide? On my pixel 2xl this method worked great. Will it work on 4xl?
Click to expand...
Click to collapse
Nothing wrong with that either. It was written by Mr. Magisk himself. However, that is mostly for OTA's that I never use. I prefer updating by factory images :good:

krabman said:
When doing the above flashing use an A to C, not the supplied cable. If you're already in a flash failure with the supplied cable grab an A to C and flash again without doing a factory reset or taking any other actions to try and get it up; this will usually get it booting as if the first flash was successful.
Edit... I know you would have put it in there if you'd remembered Badg, it's hard to remember every little speed bump when whipping up a set of instructions like that.
Click to expand...
Click to collapse
Many thanks for reminding me of probably the biggest bug-a-boo problem plaguing the pixel line when it comes to updating or data transfer. Which is why I have several different cables! The P2XL was a great teacher for sure :good:

Do we flash global for TMobile?

Some_Ghost said:
Do we flash global for TMobile?
Click to expand...
Click to collapse
According to Google....yes :good:

After the January update, I no longer have call screening (automatic or otherwise). Not sure if related to being a GSuite user or not. Ugh...

Badger50 said:
In a nutshell: This is how I do it. Others MMV
1. Make sure platform-tools are up to date. The latest is 29.0.5. And use a USB A to USB C cable.
2. Download factory image, extract it, extract the image.zip, move boot.img to your phones internal storage.
3. Disable all magisk modules and substratum themes, remove face ID and reboot.
4. Patch the stock boot.img, and move the patched.img to your pc platform-tools folder, then turn phone off.
5. Move all your necessary factory image files to your platform-tools folder: bootloader, radio, the still zipped image.zip and the flash-all.bat file for Windows machines. Using notepad or whatever, edit the flash-all.bat file and remove the -w from the script, leaving a single space between the remaining words, save your edit.
6. Put phone in bootloader mode, and plug it into your pc. Open a command prompt on your platform-tools folder, type in: fastboot devices. If your device is recognized with it's ID, your good to go. Then, what I do is go into my platform-tools folder and double click the flash-all.bat file to start the process. Let it finish, and let your device boot up.
7. Once it boots ok with the update, turn phone off, and go into bootloader mode. Connect to pc, and fastboot the patched boot.img to both slots with..
fastboot flash boot magisk_patched.img --slot=all
And let it boot up with root.
8. Then start enabling your magisk modules a couple at a time. Be warned, sometimes, not all magisk modules play nicely with monthly updates, so take it slow. Luckily, January is cool with the @Tulsadiver mods, and the Active Edge mods from what I've seen.
9. And there ya go. Ok....so it was a little bigger than a nutshell!
Click to expand...
Click to collapse
you are a great help and i wish i could take you out for a beer or 5

Badger50 said:
In a nutshell: This is how I do it. Others MMV
1. Make sure platform-tools are up to date. The latest is 29.0.5. And use a USB A to USB C cable.
2. Download factory image, extract it, extract the image.zip, move boot.img to your phones internal storage.
3. Disable all magisk modules and substratum themes, remove face ID and reboot.
4. Patch the stock boot.img, and move the patched.img to your pc platform-tools folder, then turn phone off.
5. Move all your necessary factory image files to your platform-tools folder: bootloader, radio, the still zipped image.zip and the flash-all.bat file for Windows machines. Using notepad or whatever, edit the flash-all.bat file and remove the -w from the script, leaving a single space between the remaining words, save your edit.
6. Put phone in bootloader mode, and plug it into your pc. Open a command prompt on your platform-tools folder, type in: fastboot devices. If your device is recognized with it's ID, your good to go. Then, what I do is go into my platform-tools folder and double click the flash-all.bat file to start the process. Let it finish, and let your device boot up.
7. Once it boots ok with the update, turn phone off, and go into bootloader mode. Connect to pc, and fastboot the patched boot.img to both slots with..
fastboot flash boot magisk_patched.img --slot=all
And let it boot up with root.
8. Then start enabling your magisk modules a couple at a time. Be warned, sometimes, not all magisk modules play nicely with monthly updates, so take it slow. Luckily, January is cool with the @Tulsadiver mods, and the Active Edge mods from what I've seen.
9. And there ya go. Ok....so it was a little bigger than a nutshell!
Click to expand...
Click to collapse
What should I do when the cmd window comes to "fastboot: error: failed to extract 'android-info.txt': iteration ended" as shown in the attachment.
And the process stops.

howardfok said:
What should I do when the cmd window comes to "fastboot: error: failed to extract 'android-info.txt': iteration ended" as shown in the attachment.
And the process stops.
Click to expand...
Click to collapse
Hard to say exactly since i've never seen that error. Did you follow my guide to the letter?
Is this the first time this has happened?
Are you using power shell commands?
Are your platform-tools up to date?
Have you tied different USB A to USB C cables and ports?
More info would be helpful :good:

Badger50 said:
Hard to say exactly since i've never seen that error. Did you follow my guide to the letter?
Is this the first time this has happened?
Are you using power shell commands?
Are your platform-tools up to date?
Have you tied different USB A to USB C cables and ports?
More info would be helpful :good:
Click to expand...
Click to collapse
Yes, I followed your guide and the cmd window worded well at the previous procedure and showed several [ok] but stuck at this point.
I doubled clicked 'flash-all.bat' file rather than used power shell.
The platform-tools is up to date since it was downloaded today.
I have not tried another cable. The cable may work well because I used this to unlock bootloader and root the device last month.
BTW, should I re-zip the replaced boot.img (Patch from Magisk) and other .img files (from the full image) to get a new zip file before flashing?

howardfok said:
Yes, I followed your guide and the cmd window worded well at the previous procedure and showed several [ok] but stuck at this point.
I doubled clicked 'flash-all.bat' file rather than used power shell.
The platform-tools is up to date since it was downloaded today.
I have not tried another cable. The cable may work well because I used this to unlock bootloader and root the device last month.
BTW, should I re-zip the replaced boot.img (Patch from Magisk) and other .img files (from the full image) to get a new zip file before flashing?
Click to expand...
Click to collapse
I would try a different cable and port first.
Don't worry about the patched boot.img until you have a successful flash of the factory image, and your phone boots up first. The secondary image.zip within the factory image definitely needs to remain zipped and in your platform-tools tools folder. The installation script needs to extract it so it can be flashed. This may be why your getting the error if this is the case.

General [Root] Magisk Patched Boot image

Firmware 18.0830.2101.81 Magisk patched boot image.
I have dumped the boot image from Asus payload BIN using Python. Tested and works flawlessly.
Try on your own RISK!
How to install:
- Unlock your bootloader using ASUS unlock app.
- Enable debugging in developers options.
- Install ADB & Fastboot Drivers.
- Extract then copy the attached boot.img to ADB tools folder.
- Open a prompt command in ADB folder, enter command "adb reboot bootloader"
- Select Recovery using the volume keys and power key , then select fastboot.
- Enter command "adb flash boot boot.img"
if the above doesn't make sense, then probably you shouldn't be trying to root using this method.
Thanks.

M.Qassem said:
Firmware 18.0830.2101.81 Magisk patched boot image.
I have dumped the boot image from Asus payload BIN using Python. Tested and works flawlessly.
Try on your own RISK!
How to install:
- Unlock your bootloader using ASUS unlock app.
- Enable debugging in developers options.
- Install ADB & Fastboot Drivers.
- Extract then copy the attached boot.img to ADB tools folder.
- Open a prompt command in ADB folder, enter command "adb reboot bootloader"
- Select Recovery using the volume keys and power key , then select fastboot.
- Enter command "adb flash boot boot.img"
if the above doesn't make sense, then probably you shouldn't be trying to root using this method.
Thanks.
Click to expand...
Click to collapse
Thanks dear I'm on 18.0830.2101.75 can you provide patched image boot for my version because i want to change fingerprint to WW then install newer version through my phone.

İs there stock boot.img

How to relock the bootloader and remove root?

M.Qassem said:
Firmware 18.0830.2101.81 Magisk patched boot image.
I have dumped the boot image from Asus payload BIN using Python. Tested and works flawlessly.
Try on your own RISK!
How to install:
- Unlock your bootloader using ASUS unlock app.
- Enable debugging in developers options.
- Install ADB & Fastboot Drivers.
- Extract then copy the attached boot.img to ADB tools folder.
- Open a prompt command in ADB folder, enter command "adb reboot bootloader"
- Select Recovery using the volume keys and power key , then select fastboot.
- Enter command "adb flash boot boot.img"
if the above doesn't make sense, then probably you shouldn't be trying to root using this method.
Thanks.
Click to expand...
Click to collapse
Hey i got update version 18.0810.2101.95
Can i use this img to root or i have to update first?

Eeveeone said:
Hey i got update version 18.0810.2101.95
Can i use this img to root or i have to update first?
Click to expand...
Click to collapse
First update, then flash this img, this img caused bootloop my phone so take care.

sorankira said:
First update, then flash this img, this img caused bootloop my phone so take care.
Click to expand...
Click to collapse
If like that better not update to 18.0830. but how i want to get stock img for 18.0810

Eeveeone said:
If like that better not update to 18.0830. but how i want to get stock img for 18.0810
Click to expand...
Click to collapse
Download 18.0810 firmware on your PC and download dumper tool it will extract payload.bin you can find stock images there.

sorankira said:
Download 18.0810 firmware on your PC and download dumper tool it will extract payload.bin you can find stock images there.
Click to expand...
Click to collapse
Can you help me by doing it. coz i couldnt do the proper way. it say syntax error

Eeveeone said:
Can you help me by doing it. coz i couldnt do the proper way. it say syntax error
Click to expand...
Click to collapse
My internet is very slow indeed like 100KB/s but i will try to download it and send you the stock img.

sorankira said:
My internet is very slow indeed like 100KB/s but i will try to download it and send you the stock img.
Click to expand...
Click to collapse
Thx a lot.. currently i managed to do it. Now i have the stock img

Does anyone tried applying an OTA update while rooted? Is it sufficient to restore stock boot image, apply update zip file and flash new patched boot image? I have not tried it yet, because there is no TWRP available and I want to backup my data before trying.

MarekPietrzak said:
Does anyone tried applying an OTA update while rooted? Is it sufficient to restore stock boot image, apply update zip file and flash new patched boot image? I have not tried it yet, because there is no TWRP available and I want to backup my data before trying.
Click to expand...
Click to collapse
Yes you can apply ota update.
When the OTA Update finishes don't reboot click later, then go to magisk install OTA to inactive slot.

THANK YOU! This file saved my phone. I installed some other boot image that wouldn't let me boot the phone, this file brought it back to life.
Thank you again!

M.Qassem said:
Firmware 18.0830.2101.81 Magisk patched boot image.
I have dumped the boot image from Asus payload BIN using Python. Tested and works flawlessly.
Try on your own RISK!
How to install:
- Unlock your bootloader using ASUS unlock app.
- Enable debugging in developers options.
- Install ADB & Fastboot Drivers.
- Extract then copy the attached boot.img to ADB tools folder.
- Open a prompt command in ADB folder, enter command "adb reboot bootloader"
- Select Recovery using the volume keys and power key , then select fastboot.
- Enter command "adb flash boot boot.img"
if the above doesn't make sense, then probably you shouldn't be trying to root using this method.
Thanks.
Click to expand...
Click to collapse
Hallo
Any boot.img for latest version WW ASUS-18.0840.2103.26-1.1.81?
Can`t get my payload working, because not installing in correct folder.

ltth said:
Hallo
Any boot.img for latest version WW ASUS-18.0840.2103.26-1.1.81?
Can`t get my payload working, because not installing in correct folder.
Click to expand...
Click to collapse
Try extracting from your phone for payload.bin file. Or there is a "rooting my notes" discussion video in one of the post. You can see there

I have the payload bin file, but can`t extract in payload_dumper-master (not working correctly so I get the boot.img

ltth said:
I have the payload bin file, but can`t extract in payload_dumper-master (not working correctly so I get the boot.im
Click to expand...
Click to collapse
[Tutorial] Android OTA payload dumper on Android
Introduction This tutorial will teach you how to specifically extract the boot.img from your OTA/ROM's payload.bin on your Android device, rather than a computer. In addition to this, you will also have the ability to access all other img files...
forum.xda-developers.com
Use this link to extract the boot.img from payload.bin using your phone. Give a try. I also had issues extracting from pc. So did in my phone and worked.

jhosharath said:
Try extracting from your phone for payload.bin file. Or there is a "rooting my notes" discussion video in one of the post. You can see the
Click to expand...
Click to collapse

I found a Payload_Dumper wich worked very well, just have execute the scipt, then I got my boot.img
Thanks for your help!!

DOOGEE S59 pro unlocking bootloader issue

Hello.
I have a DOOGEE S59 pro phone and i tried a bunch of times to unlock its bootloader, but it didn't work.
I've already done these things:
I've installed the USB driver and the MediaTek driver from https://gsmusbdriver.com/
I've enabled "OEM unlocking" and "USB debugging" in the developper options
I've ran the CMD prompt in the platform-tools folder (which is placed in the C: drive) and run this code:
PS C:\Program Files\platform-tools> adb devices
List of devices attached
S59PROEEA0000026105 device
PS C:\Program Files\platform-tools> adb reboot bootloader (now the phone shows " =>FASTBOOT mode . . . ")
PS C:\Program Files\platform-tools> adb devices
List of devices attached
(My phone isn't listed anymore)
PS C:\Program Files\platform-tools> fastboot oem unlock
< waiting for any device >
And this is it. I can't do anything else. When I hold the power button + the volume up key I can return to normal mode, but what can I do to unlock the bootloader? I wanted to root my phone and flash some magisk modules after that, but the situation is like I said. Can somebody help me?

Since the phone is using a MediaTek chipset you can try using MTKclient, after downloading the zip completely power off your phone and open a terminal inside the 2nd folder of the unzipped zip file, the run the command python mtk da seccfg unlock after you did that hold the button combination for fastboot mode so long until the screen goes fully black and mtkclient should try unlocking the bootloader. Tried and tested on my Xiaomi Redmi 9 because I didn't want to factory reset.

.

xinthenoob said:
Since the phone is using a MediaTek chipset you can try using MTKclient, after downloading the zip completely power off your phone and open a terminal inside the 2nd folder of the unzipped zip file, the run the command python mtk da seccfg unlock after you did that hold the button combination for fastboot mode so long until the screen goes fully black and mtkclient should try unlocking the bootloader. Tried and tested on my Xiaomi Redmi 9 because I didn't want to factory reset.
Click to expand...
Click to collapse
Thank you, I'll try that and I'll tell you if it works.

KakoFed said:
Thank you, I'll try that and I'll tell you if it works.
Click to expand...
Click to collapse
I completely forgot 2 more things!
1. You need to have python installed (during the install when you see a button that says "Add to PATH" check it)
2. After opening the terminal run pip install -r requirements.txt

xinthenoob said:
I completely forgot 2 more things!
1. You need to have python installed (during the install when you see a button that says "Add to PATH" check it)
2. After opening the terminal run pip install -r requirements.txt[
[/QUOTE]
Click to expand...
Click to collapse
I've just installed python, but I don't see the "Add to PATH" button. When I try to type that command, it says 'pip' is not recognized as an internal or external command,
operable program or batch file.
What should I do?
And also, which version of python do I have to install?

xinthenoob said:
I completely forgot 2 more things!
1. You need to have python installed (during the install when you see a button that says "Add to PATH" check it)
2. After opening the terminal run pip install -r requirements.txt
Click to expand...
Click to collapse
I also tried to open a command prompt in the mtkclient folder itself, and it said that:
pip : The term 'pip' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the s
pelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ pip install -r requirements.txt
+ ~~~
+ CategoryInfo : ObjectNotFound: (pip:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

xinthenoob said:
I completely forgot 2 more things!
1. You need to have python installed (during the install when you see a button that says "Add to PATH" check it)
2. After opening the terminal run pip install -r requirements.txt
Click to expand...
Click to collapse
Alright, I don't know what have I done, but it totally worked! Thank you so much!

KakoFed said:
I've just installed python, but I don't see the "Add to PATH" button. When I try to type that command, it says 'pip' is not recognized as an internal or external command,
operable program or batch file.
What should I do?
And also, which version of python do I have to install?
Click to expand...
Click to collapse
It should be somewhere also don't use PowerShell, it's weird sometimes

xinthenoob said:
It should be somewhere also don't use PowerShell, it's weird sometimes
Click to expand...
Click to collapse
Hi, it's me again.
I unlocked the bootloader successfully, but now I am trying to root my phone using magisk. I patched a boot.img file from the Doogee s59 pro firmware and I tried to flash it via ADB, but it didn't work. I went into the fastboot mode (it is saying "fastbootd" actually), and I typed
fastboot devices
That worked, my phone was listed, but after that I tried to flash the patched boot.img file using this command:
fastboot flash boot <the file directory>
And also
fastboot boot <the file directory>
And it didn't work, it said:
warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 33554432).
sending 'boot' (32768 kb) failed (write to device failed (no link)) fastboot: error: command failed
Something like this.
What am I doing wrong?
Please help

KakoFed said:
Hi, it's me again.
I unlocked the bootloader successfully, but now I am trying to root my phone using magisk. I patched a boot.img file from the Doogee s59 pro firmware and I tried to flash it via ADB, but it didn't work. I went into the fastboot mode (it is saying "fastbootd" actually), and I typed
fastboot devices
That worked, my phone was listed, but after that I tried to flash the patched boot.img file using this command:
fastboot flash boot <the file directory>
And also
fastboot boot <the file directory>
And it didn't work, it said:
warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 33554432).
sending 'boot' (32768 kb) failed (write to device failed (no link)) fastboot: error: command failed
Something like this.
What am I doing wrong?
Please help
Click to expand...
Click to collapse
You can flash the boot using mtkclient once again, first back up boot and vbmeta using python mtk r boot,vbmeta boot.img,vbmeta.img then transfer the patched boot to your PC and rename it boot.patched after doing that you can flash it onto your phone using python mtk w boot,vbmeta boot.patched,vbmeta.img.empty. Making a backup of those two is VERY important Incase something goes wrong.
Also I think it's because your phone has a integrity check, if you really want to flash it using fastboot I could find a fix

xinthenoob said:
You can flash the boot using mtkclient once again, first back up boot and vbmeta using python mtk r boot,vbmeta boot.img,vbmeta.img then transfer the patched boot to your PC and rename it boot.patched after doing that you can flash it onto your phone using python mtk w boot,vbmeta boot.patched,vbmeta.img.empty. Making a backup of those two is VERY important Incase something goes wrong.
Also I think it's because your phone has a integrity check, if you really want to flash it using fastboot I could find a fix
Click to expand...
Click to collapse
Thanks, I'll try it, but in case something goes wrong, how do I use the backup files?
And also, could I install magisk modules after that?

KakoFed said:
Thanks, I'll try it, but in case something goes wrong, how do I use the backup files?
And also, could I install magisk modules after that?
Click to expand...
Click to collapse
Same way you flashed the patched files, always include the vbmeta.img.empty if you're flashing anything but the vbmeta.
If everything goes as planned, absolutely! I'm using energize protection as an ad blocker and it's working great.

xinthenoob said:
Same way you flashed the patched files, always include the vbmeta.img.empty if you're flashing anything but the vbmeta.
If everything goes as planned, absolutely! I'm using energize protection as an ad blocker and it's working great.
Click to expand...
Click to collapse
Ok, thanks, I'll try everything of that later

.

xinthenoob said:
Same way you flashed the patched files, always include the vbmeta.img.empty if you're flashing anything but the vbmeta.
If everything goes as planned, absolutely! I'm using energize protection as an ad blocker and it's working great.
Click to expand...
Click to collapse
Hi, I have a problem AGAIN. When I flashed the boot.patched file, it was almost ok, until I saw that my bluetooth and WiFi connections stoped working after the flash. There was this window opening again and again that the Bluetooth app still stops working. I had to flash the normal boot.img file for it to work.
How can I solve this problem? I still want to root my phone

xinthenoob said:
Same way you flashed the patched files, always include the vbmeta.img.empty if you're flashing anything but the vbmeta.
If everything goes as planned, absolutely! I'm using energize protection as an ad blocker and it's working great.
Click to expand...
Click to collapse
ACTUALLY NEVER MIND
I found a solution myself, it was the boot.img file that I think was the problem. I patched the boot.img file again but this time I patched that one that I backuped with MTKclient.
Thank you so much for your help, you were really helpful for me

KakoFed said:
ACTUALLY NEVER MIND
I found a solution myself, it was the boot.img file that I think was the problem. I patched the boot.img file again but this time I patched that one that I backuped with MTKclient.
Thank you so much for your help, you were really helpful for me
Click to expand...
Click to collapse
Sorry I caught the flu and was out for a while but I'm glad you found a way