Related
Hi all.
I have searched the forum for solution to my problem but can't seem to find it.
When trying to flash 5.1 I get an error
After,I try to flash all .img files manually. All flash normal except system.img
I searched forums, used Wugs tool, tried on different PC's (Windows 8.1 & Windows 7) tried with different fastboot versions but no result.
Older versions flash normal(5.0.1, 4.4.4, etc..)
Any suggestions?
How much ram the PCs have?
One has 8gb ram installed,another one has 16gb
arsen4oo said:
One has 8gb ram installed,another one has 16gb
Click to expand...
Click to collapse
Strange...
Can you pack the adbs and fastboots to a zip or rar and upload it to somewhere or give me a link which adb and fastboot you use. I am going to try flash 5.1 in 30 minutes.
Here they are.
I am downloading ubuntu to try flashing from there.
*Update.
Succeed flashing on Ubuntu. Don't understand what's wrong with Windows.
arsen4oo said:
Here they are.
I am downloading ubuntu to try flashing from there.
*Update.
Succeed flashing on Ubuntu. Don't understand what's wrong with Windows.
Click to expand...
Click to collapse
Using your binaries it flashed fine, I got no errors.
My specs: Windows 8.1 Pro 8GB ram.
What is different with my setup about ram management is that since I have an SSD as drive C I moved the pagefile.sys to my HDD.
I also have Microsoft Visual C++ 2008, 2010, 2012 redistributables installed. I have no idea if that counts
I don't think problem is caused by pagefile.
But seems many people have this issue when flashing 5.1
Flashing from ubuntu is an alternative solution..
I have no idea what the issue is but here is how I got round exactly the same error message on my Windows 7 machine.
Create a new local user (with admin rights) and then reboot your machine. Log in with that user and close any applications that try to auto-start. Then try the batch file and it should now work.
I think it must be related to memory/open applications. I have loads of stuff open in the background, i.e. in the systray, with my standard login. This new user had nothing. Using this user after a reboot seems to do the trick!
Try to download the nexus image again. It might be corrupted or extract it again using 7zip. Just flashed mine a while ago using "minimal adb and fastboot" on windows 7 x64 with 2gb of RAM. Machines doesn't have anything to do with adb flashing. It's the file itself or the adb drivers.
Edit: I see you've already sorted this out via ubunta machine. Good for you.
I had the same issue last night too. I downloaded the latest nexus USB drivers and the flash completed successfully.
Had the same issue. Spent all night unbricking my phone. One of the partitions didn't flash right and i left my phone over night and it still didn't boot up. got 2 hours of sleep.
Kitkat flashed fine though.
So what i did. im using minimal adb fastboot
1) flash 4.4.4 images
2) extract ALL 5.1 image files (boot, system, etc) into the minimal adb fastboot folder C:\\program files etc etc
3) flash each item manuall
-fastboot flash bootloader bootloadername.img
-fastboot flash radio radioname.img
-then do the same with boot, radio, system, userdata, cache. (fastboot flash "partition" "name".img) so if youre flashing boot, then boot boot.img
this should boot up just fine. 2-5 minutes tops.
Manual flashing fixes it
Thanks a lot russian392! Your instructions resolved the issue for me on Windows 7 Home Premium laptop with only 4GB RAM.
So in addition to the standard flashing instructions I did the following:
1. Unzip image-hammerhead-lmy47d.zip
2. In flash-all.bat change the following line:
Code:
fastboot -w update image-hammerhead-lmy47d.zip
to:
Code:
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
BorgKing said:
Thanks a lot russian392! Your instructions resolved the issue for me on Windows 7 Home Premium laptop with only 4GB RAM.
So in addition to the standard flashing instructions I did the following:
1. Unzip image-hammerhead-lmy47d.zip
2. In flash-all.bat change the following line:
Code:
fastboot -w update image-hammerhead-lmy47d.zip
to:
Code:
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Click to expand...
Click to collapse
yep you got it right :good:
I'm sure your issue will be solved if you do exactly what said in this video
Those videos helped me to flash 5.1 successfully
Sanjay Varma said:
I'm sure your issue will be solved if you do exactly what said in this video
Those videos helped me to flash 5.1 successfully
Click to expand...
Click to collapse
lol i got the idea from the same vid. Just ive flashed partitions manually before.
russian392 said:
lol i got the idea from the same vid. Just ive flashed partitions manually before.
Click to expand...
Click to collapse
lolz - though he is explaining well, I did mistakes as the commands and file names identically followed by each other
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.)
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.
Okay so I recognize if I had more money I could pay for home internet. But I don't so I'm here with a budget phone, less than ideal tech skills, and can't seem to figure out how to root.
I've borrowed multiple windows 10 computers all the same result.
I've installed the latest Adb drivers from multiple sources. Re-installed drivers. Uninstalled drivers to no avail
I have my bootloader unlocked. I downloaded the latest firmware. I extracted it and patched the boot.img.
whenever I type fastboot flash boot magisk_patched.img this is the result
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
when in fastboot mode i see on my phone
device state: unlocked
boot slot:b
Hoping someone can help Life is frustrating without internet.
Jmcarls20 said:
Okay so I recognize if I had more money I could pay for home internet. But I don't so I'm here with a budget phone, less than ideal tech skills, and can't seem to figure out how to root.
I've borrowed multiple windows 10 computers all the same result.
I've installed the latest Adb drivers from multiple sources. Re-installed drivers. Uninstalled drivers to no avail
I have my bootloader unlocked. I downloaded the latest firmware. I extracted it and patched the boot.img.
whenever I type fastboot flash boot magisk_patched.img this is the result
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
when in fastboot mode i see on my phone
device state: unlocked
boot slot:b
Hoping someone can help Life is frustrating without internet.
Click to expand...
Click to collapse
Just a tip, if you're in dire need of a computer, I'd recommend a raspberry pi. It's really handy for your situation. I also don't have home internet and was using purely a Pi for a fair while, it's definitely enough for adb/fastboot stuffs among other things.
Now, onto your issue. Have you tried specifying the boot slot? Normally you shouldn't have to specify the slot but in your case you may have to.
You can try running the command
Code:
fastboot flash boot_b magisk_patched.img
Also, verify that the magisk_patched.img is in the directory you started the terminal/PowerShell window in with the adb executable.
Sent from my Pixel 3a XL using XDA Labs
can you flash anything else in fastboot? or are you only trying to flash the patched magisk image?
I've attached the latest platform tools from Google.
Unzip this folder to the root of your C:/ so it looks like this: C:/adb
Put your magisk_patched.img in the folder then shift+right click anywhere in the folder and "open command prompt here".
With your phone in bootloader mode, at the prompt type: fastboot flash boot magisk_patched.img
I've just done this to check and mine worked first time . Let me know how you get on .
Is the modified magisk file in the same directory as the SDK tools?
I do not recommend that you start using "boot partition" specific commands. You should not have to specify which boot partition to write to. If it's not working that is an indication of a larger issue that needs to be resolved. I've seen plenty of people make things worse when they start using boot partition specific commands.
Wow thank you for the support. I got it to flash by boot_b but then I tried to reboot and the touch screen didn't work so I reflashed the original boot.img and then redid the boot file today and will try it tonight. Will keep everyone posted and will re try other solutions tonight. Going to have to look into raspberry pi to that sounds like a nice project to try
Here's a simple guide for those of you like me who bought a cheap ULM G7 that's actually cross flashed from something else (Sprint for my case).
I got mine with Oreo 11e on it. I'll just explain the steps to get to unlock with 20e (Pie) rooted. I'm not an expert, but I've been doing this stuff for a lot of years. I probably can't answer questions on why it's not working for your situation, so hopefully others can jump in when necessary.
These steps worked for me. Some may be unnecessary. Not sure.
DISCLAIMER: Don't blame me if something goes wrong. Again, this worked for me.
First of all, you'll want to flash to 11g, because we have a patched rooted boot image for it.
https://lg-firmwares.com/downloads-file/17341/G710ULM11g_01_NAO_US_OP_1112
Install the patched LGUP (GUI one, not command line).
Flash 11g by doing a Partition DL, select the kdz in the bottom half (click on the first empty line).
After it's done and it reboots into the system. Let it boot, do the initial setup to get into options and enable OEM unlock and USB debugging.
Then do the unlock guide here:
https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
You can follow the steps in there exactly. There is nothing different that needs to be done for the G7. You're basically using QFIL to flash the v35 eng boot to get a hacked fastboot.
You're now bootloader unlocked.
Now, we want to get 20e rooted. Before we flash the 20e kdz, we need a patched boot image (Magisk). We have to create a patched boot image from the stock boot image. So, here are the steps for reference. If you want to skip this (trust me, you do), download my patched boot image here: https://mega.nz/#!uqZFDKZQ!5dOCFKElmMOXnAMel7dSvyhGY5RkJjBsMwM-kH7eOGo
Skip until you see "Skip to here".
* I was informed after that it's easier to just flash the 20e kdz, then use QFIL to extract the boot image instead of fooling around with kdztools. Leaving this for reference. *
Dowload the 20e firmware: https://lg-firmwares.com/downloads-file/21135/G710ULM20e_00_NAO_US_OP_1010
Use kdztools to unkdz, then undz:
Download the DEVEL branch: https://github.com/steadfasterX/kdztools/tree/develop
Install python. I'm using 3.8 x64 for Windows 10.
In a command prompt, run "pip install zstandard" which you need to unkdz.
In your extracted kdztools folder, run:
Code:
python unkdz.py -f <path to 20e kdz> -x
This extracts a .dz file.
Now run:
Code:
python undz.py -f <path to extracted dz file> -s 42
This extracts the boot image (you can see it's 42 if you do a -l instead of -s).
Now you have your clean/stock 20e boot image.
Go back into fastboot (if you're not still there) and BOOT the rooted 11g boot image: https://androidfilehost.com/?fid=1899786940962574205
Code:
fastboot boot 710ULM11g_rootedboot.img
It'll boot into the system and magisk is installed temporarily. Copy the clean 20e boot image onto your phone. Install Magisk Manager, then in Magisk Manager, click the first Install (top of the 2) and it'll pop up a window. Click Install again, then it'll show a menu with 4 options (honestly, the patch should be moved to the main menu imo). Click "Select and Patch a File". Find your 20e boot image and choose it. Magisk will now patch it and create a magisk_patched.img. This is your rooted 20e boot.
Skip to here.
Now we flash 20e to get Pie. Same as above, use LGUP to partition_dl the 20e kdz (select all).
Once it's done, it'll reboot. Wait for it to get to the initial setup (I don't like force rebooting while system is doing possibly important stuff). Get back into 9008 mode. Use QFIL to flash the patched boot img to "boot_a". Once that's done, just vol down + power for 15 seconds to force a reboot.
You're now 20e + root + bootloader unlocked.
I won't be monitoring this thread a lot, so don't expect quick responses, but there's enough details here for most people who are familiar with rooting to get to where I am.
I successfully rooted my crossflashed spring LG G7 using the guide you linked, and this verizon guide.
I never updated to 11g image. I manually patched the boot_a and boot_b image within Magisk GUI app, within the phone itself.
First of all, you'll want to flash to 11g, because we have a patched rooted boot image for it.
Click to expand...
Click to collapse
Other guides mention disabling/erasing certain partitions: the laf_a/boot_b according to this Lineage16 guide or laf_a/laf_b/boot_a & boot_b according to the 9008 guide, but I could be wrong
Code:
adb root
[In magisk make sure ‘Shell’ is granted super user access AFTER executing the following]
adb shell su dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf_a
adb shell su dd if=/dev/zero of=/dev/block/bootdevice/by-name/boot_b
This will get rid of download mode feature on your phone, rendering LGUP un-useable, you can use QFIL to restore your backed up laf_a/_b files.
There's a KDZ GUI extract tool here.
It found the following in 20e kdz file: boot.img_65286, boot.img_163830; both 64MB. If anyone knows what the bolded parts represent it would be appreciated. I assume the lower number corresponds to A and the higher, is B.
I'll likely use the twrp_june.img for both boot_a/_b.
Any time you want to flash something via twrp you will have to flash twrp via fastboot again (hence the non persistance), do your stuff in twrp, and then reflash the boot img (it will not boot if you dont do this or use josh1x's boot file). Just like steps 5-6 for gapps.
Click to expand...
Click to collapse
According to this guide.
Now, we want to get 20e rooted. Before we flash the 20e kdz, we need a patched boot image (Magisk). We have to create a patched boot image from the stock boot image. So, here are the steps for reference. If you want to skip this (trust me, you do), download my patched boot image here:
Click to expand...
Click to collapse
Assuming you already rooted the phone, there's a way to prevent, the KDZ from overwriting patched boot_a and boot_b in LGUP, as seen 7:00 and 7:25 of the following video.
I appreciate the guide though.
Stuck in fastboot mode, I forgot something..
Aztec_native said:
Stuck in fastboot mode, I forgot something..
Click to expand...
Click to collapse
Do you have download mode? If yes, you can also flash a kdz to start over. With 9008/qfil, almost all situations should be recoverable.
And what were you doing just before getting stuck in fastboot? Did you have a working system before going into fastboot? If you had trouble with the unlock process, you will have to ask in the V40 thread.
paxar331 said:
I never updated to 11g image. I manually patched the boot_a and boot_b image within Magisk GUI app, within the phone itself.
Click to expand...
Click to collapse
Can you patch a boot image on a phone using magisk manager if it's not rooted? I assumed you needed to be rooted to be able to patch.
If you don't, then you can LGUP directly to 20e, pull the boot image using qfil, and patch with magisk manager right after. Saves a lot of steps and time if so.
strifej said:
Do you have download mode? If yes, you can also flash a kdz to start over. With 9008/qfil, almost all situations should be recoverable.
And what were you doing just before getting stuck in fastboot? Did you have a working system before going into fastboot? If you had trouble with the unlock process, you will have to ask in the V40 thread.
Click to expand...
Click to collapse
No download mode, I was trying to flash pie while on rooted Oreo.. it was fine before that. Half the fun, right?
strifej said:
Can you patch a boot image on a phone using magisk manager if it's not rooted? I assumed you needed to be rooted to be able to patch.
If you don't, then you can LGUP directly to 20e, pull the boot image using qfil, and patch with magisk manager right after. Saves a lot of steps and time if so.
Click to expand...
Click to collapse
No. I rooted with QFIL and V35eng.img → abl_a (after backing up abl_a). Then did fastboot oem unlock, re-inserted the backed up abl_a.img file, then did the magisk patch up to boot_a/_b.
Aztec_native said:
No download mode, I was trying to flash pie while on rooted Oreo.. it was fine before that. Half the fun, right?
Click to expand...
Click to collapse
Maybe try a different LGUP? At worst, you can use the command line only one that bypasses checks and can force flash any kdz. But you have to be very careful to not flash the wrong firmware.
I'm not sure if QFIL can flash kdz, but you could research into that if it helps.
strifej said:
Maybe try a different LGUP? At worst, you can use the command line only one that bypasses checks and can force flash any kdz. But you have to be very careful to not flash the wrong firmware.
I'm not sure if QFIL can flash kdz, but you could research into that if it helps.
Click to expand...
Click to collapse
I flashed a firmware that I previously had flashed, ULM20e.
The phone is only recognized in fastboot as Android Bootloader Interface... Can't get anything to work, haha. However, I did get the 11g IMG to get a different screen..
Edit: The update to pie stopped at 91% and then gave an error.
Aztec_native said:
I flashed a firmware that I previously had flashed, ULM20e.
The phone is only recognized in fastboot as Android Bootloader Interface... Can't get anything to work, haha. However, I did get the 11g IMG to get a different screen..
Edit: The update to pie stopped at 91% and then gave an error.
Click to expand...
Click to collapse
Same here:
According to multiple google searches LGUP is not properly patched.
I then made the mistake of using an older version of LGUP, that doesn't give you the option to disable boot_a/_b partitions from being over written; which was a foolish mistake.
I'd like to add that Pie LG stock boot images have NO FASTBOOT support, DO NOT delete laf_a & laf_b files, doing so does away with 'download mode'. If you do delete it, you'll need QFIL to flash abl_a to v35eng.img; this will give fastboot enablement on the phone, and allow to transfer backed up files to phone using 'fastboot'.
The following post helped, in allowing me to regain access to download mode.
QFIL does not allow overwriting of Pie files except abl_a, which is more than enough in this case.
I also patched Pie/20e boot_a/_b files with magisk, and the phone is stuck in a fastboot loop for me as well, this may explain why 11g is needed.
If using LGUP 1.15, you'll come across google link by sarang on how to implement the 'common dll' patch. Forum won't let me link to the website.
Installed 11g after changing to LGUP's program files (x86) directory:
Code:
lgup_cmd.exe com[your com port # in windows device manager] "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" "E:\HIS Documents\Computer guides\LG G7\Softwares\G710ULM11g_01_NAO_US_OP_1112.kdz"
I'm finally able to boot into Android 8.x now, and make magisk fully root.
paxar331 said:
Same here:
According to multiple google searches LGUP is not properly patched.
I then made the mistake of using an older version of LGUP, that doesn't give you the option to disable boot_a/_b partitions from being over written; which was a foolish mistake.
I'd like to add that Pie LG stock boot images have NO FASTBOOT support, DO NOT delete laf_a & laf_b files, doing so does away with 'download mode'. If you do delete it, you'll need QFIL to flash abl_a to v35eng.img; this will give fastboot enablement on the phone, and allow to transfer backed up files to phone using 'fastboot'.
QFIL does not allow overwriting of Pie files except abl_a, which is more than enough in this case.
I also patched Pie/20e boot_a/_b files with magisk, and the phone is stuck in a fastboot loop for me as well, this may explain why 11g is needed.
Click to expand...
Click to collapse
Qfil allows backing up files as well as overwriting almost any file. I do it all the time.
Bricking my phone along the way trying different things. Unlocking and relocking bootloader.
Most of the time when you patch boot imgs people patch and load the magisk patched image to the wrong slot.
I have crossflashed the Korean pie and updated to Android 10 and achieved root with Android 10 as well.
All with qfil and using the command line LGUP to crossflash.
I don't mind helping users with issues as well.
Does anyone know the cmd syntax to execute the following? I.e. 'partition dl' is selected, and every partition but boot_a/_b is selected for installation. LGUP 1.15 GUI asks for a login making it un-usable for most on here.
Edit: This post may correspond with using the right version of LGUP.
I googled parts of this video: https://www.youtube.com/watch?v=ylBSZk7EqcA
I was able to reach 100%.
Unfortunately there's a boot loop, it seems 710ULM11g_rootedboot.img must be flashed before transferring file with LGUP.
I'm stuck and totally confused. Flashed 710ULM11g_rootedboot.img before transferring G710ULM20e_00_NAO_US_OP_1010.kdz. I then pressed power and Vol Down, then tapped the power button, click No on the white screen background, and again, I'm stuck on the fastboot loop.
The fastboot menu looks different than that of the video
https://www.youtube.com/watch?v=ylBSZk7EqcA
The one in the video looks like it's from v35eng.img used in 9008 QFIL guide.
Go back to ULM11g and crossflash using lgup command line to 20e then root it.
I believe there is a rooted 20e boot img that you can load with qfil or if adb fastboot works.
Crossflashing:
https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
Using qfil to load rooted 20e img.
https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
The process in the second guide is the same when loading a rooted img to either boot a or b whatever slot your on.
I was able to solve it.
The magisk patched IMG file by this OP was flashed to both boot_a and boot_b, then executed 'fastboot reboot'; yeah boot_a and boot_b need to be flashed with an identical file.
https://mega.nz/#!uqZFDKZQ!5dOCFKElmMOXnAMel7dSvyhGY5RkJjBsMwM-kH7eOGo
The screen booted twice with the 'Red LG symbol" showing itself twice, before I could get in to the new user setup prompts.
The 20e patched file from the following thread was no good:
https://forum.xda-developers.com/lg-g7-thinq/development/magisk-18-0-boot-images-t3955096
The most important part of this upgrade is definitely making sure LGUP is setup properly, including not installing the stock 20e boot_a/_b partitions, as seen in my previous post, and don't delete the laf_a/_b partitions as a good precautionary measure.
paxar331 said:
I was able to solve it.
The magisk patched IMG file by this OP was flashed it to both boot_a and boot_b, then executed 'fastboot reboot'; yeah boot_a and boot_b need to be flashed with an identical file.
https://mega.nz/#!uqZFDKZQ!5dOCFKElmMOXnAMel7dSvyhGY5RkJjBsMwM-kH7eOGo
The screen booted twice with the 'Red LG symbol" showing itself twice, before I could get in to the new user setup prompts.
The 20e patched file from the following thread was no good.
https://forum.xda-developers.com/lg-g7-thinq/development/magisk-18-0-boot-images-t3955096
The most important part of this upgrade is definitely making sure LGUP is setup properly, including not installing the stock 20e boot_a/_b partitions, as seen in my previous post, and don't delete the laf_a/_b partitions as a good precautionary measure.
Click to expand...
Click to collapse
Yes the boot imgs are identical they are labled a and b because of the dual slots. If you knew what slot you were in prior to flashing any magisk rooted image you would just need to flash that specific boot img slot.
I relocked my bootloader just for kicks.
If you can get into fast boot there is no need to erase laf partitions only if you need fast boot.
I tried it but didn't work in EAW and I lost serial number mac address how get them back??? Need urgent help please
mine was already bootloader unlocked,
but tutorial worked fine here I flashed 20e using LG up and rooted.
What I did:
MAKE SURE YOU ARE BOOTLOADER UNLOCKED. I am not responsible for any damage, it is only what I did.
1)Dowload the 20e firmware: https://lg-firmwares.com/downloads-file/21135/G710ULM20e_00_NAO_US_OP_1010
2) Download this: LGUP new version - https://drive.google.com/file/d/1dJZxrj7nteDDUcQpiJLpX9Mjumm5mtKp/view
3) Install the file you downloaded above (LGUP).
4) Download this: LGUP common.dll https://drive.google.com/file/d/1V8IF2vJed3bQBsBCHLNBJdnW4gRj2uo0/view
5) Open the file downloaded and you will see the folder common. Copy the folder common and paste inside the folder model of the folder of the installation of the LGUP. For example: C:\Program Files (x86)\LG Electronics\LGUP\model
6) You are doing great! Congratulations. Let's proceed with 7.
7) Get phone in hands. Turn off it. Press and hold volume up and connect the phone into notebook. once appears download mode panel you unhold volume up softly.
7.1) When you connect the phone in download mode LG device must show in Windows Device Manager under "Ports" as a LG Serial COM port. Check it.
8) check if you completed the download of the kdz file. Did you complete the download of the big KDZ? Put the KDZ file in C:\ localization of your computer.
9) Let's open a command prompt as administrator. Now, in the command prompt input, type:
cd <path of LGUP folder>
Example:
cd C:\Program Files (x86)\LG Electronics\LGUP
10) Is your phone com5? check in Device Manager under Ports. It is written COM and a number after. If the answer is yes, you only have to type this code and run in the command prompt:
lgup_cmd.exe com5 "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" "C:\G710ULM20e_00_NAO_US_OP_1010.kdz"
11) Are you unsure if your phone is com5? just modify com5 to comX replacing X with the properly number. For my EMW worked with com5.
lgup_cmd.exe comX "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" "C:\G710ULM20e_00_NAO_US_OP_1010.kdz"
12) Wait 5 minutes, less or more.
13) it is completed! Remove the plug of the device.
14) It is like a new phone you have to conclude the phone configuration.
15) install magisk from magisk website but dont update it.
16) Get developer options enabled in your phone.
17) Open command prompt as administrator, type this code:
cd <path of minimal adb and fastboot folder>
Example
cd C:\Android-FastBoot-Adb
Don't have adb and fastboot minimal folder? Research in google and download. If you don't know what is the folder, it contains fastboot.exe inside.
18) Type this code now: adb reboot bootloader
19) confirm in phone allow usb depuration in this device or the command wont work
20) Download in your windows this pre rooted file made for this PIE OS by the author of the thread
https://mega.nz/#!uqZFDKZQ!5dOCFKElmMOXnAMel7dSvyhGY5RkJjBsMwM-kH7eOGo
21) put the file inside the fastboot folder. the file name is g7_20ulm_20e_boot_magisk_patched.img
22) in command prompt (already in cd path of minimal fastboot folder) type this:
fastboot boot g7_20ulm_20e_boot_magisk_patched.img
23) phone will reboot.
24) now phone started, open magisk and update it and click to install directly when it asks.
25) magisk will ask to reboot, click to reboot you are now rooted.
good luck
Hi Just a lost soul passing thru Lol
I'm looking to shed some light on my g710pm, its been a few days since I've been searching to get on AOSP.
I cross flashed to ULM 11g stock and had root and unlocked bootloader, then flashed 21d ULM and now Enable OEM unlock is grayed-out (bootloader is already unlocked ) sub message. SO... I back flashed to ULM 11g with same issue.
I've been reading the forums and have a rough idea how to fix, some how re-flashing laf_a ?
would really appreciate the help
Thanks
Found FIX
1. PS C:\Program Files\platform-tools> adb devices
List of devices attached
LMG710ULM******** device
2. PS C:\Program Files\platform-tools> adb reboot bootloader
3. PS C:\Program Files\platform-tools> fastboot oem lock
(bootloader) Erasing userdata and cache OKAY [ 0.492s]
Finished. Total time: 0.592s
4. PS C:\Program Files\platform-tools> fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.004s
https://forum.xda-developers.com/lg-g7-thinq/how-to/verizon-lg-g710vm20f-t4057031