Related
So I have my Xoom unlocked and I am trying to flash the recovery in order to root. I have the recovery in the platform tools folder along with fastboot and all that, and I'm able to get the Xoom into fastboot from adb, but I can't get the recovery to flash. I'm typing the name correct. And I'm putting in 'fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img' without the quotes. Honestly I'm a little bit stumped at this point.
I have had the same issue for the past few days I have also tried the steps here no luck.... http://forum.xda-developers.com/showthread.php?t=1249798
supenova3000 said:
I have had the same issue for the past few days I have also tried the steps here no luck.... http://forum.xda-developers.com/showthread.php?t=1249798
Click to expand...
Click to collapse
I used the same guide. It just makes no sense that I can control the Xoom and unlock it, but I can't flash the darn recovery.
williamthegoat said:
I used the same guide. It just makes no sense that I can control the Xoom and unlock it, but I can't flash the darn recovery.
Click to expand...
Click to collapse
I tried moving the files from the tools folder to platform tools still no luck.. all of this for the I C S flash I'm going to keep working on a solution I will let you know if I have any luck!
So I have the android sdk in c:\ , and in the sdk folder I have everything, and in the platform tools I have my fastboot and recovery. I then use cmd to get into adb, then I put the xoom in fastboot. From there I try to flash the recovery, which always fails. I must be doing something wrong here.
Try downloading the IMG again. Or try out the rogue recovery. I actually like rogue better.
Sent from my MB860 using xda premium
I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS
Thanks for the responses and help guys
Think you have to be stock to flash to ICS, at least that was the word yesterday.
I gave up trying to root just as I found out about the ICS update.
williamthegoat said:
I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS
Thanks for the responses and help guys
Click to expand...
Click to collapse
Two simple errors:
1) not opening the command window from the folder where you have fastboot and the image files you're trying to flash; and
2) not realizing that you have hidden file extensions in Windows, and typing ...recovery.img.img
williamthegoat said:
So I have my Xoom unlocked and I am trying to flash the recovery in order to root. I have the recovery in the platform tools folder along with fastboot and all that, and I'm able to get the Xoom into fastboot from adb, but I can't get the recovery to flash. I'm typing the name correct. And I'm putting in 'fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img' without the quotes. Honestly I'm a little bit stumped at this point.
Click to expand...
Click to collapse
I assume that you've set up a path in environment variables to run adb and fastboot from ay directory... and are running the flash command from a folder other than where your .IMG file is located. In order for fastboot to find the file you're trying to flash, you actually have to run your flash command from the folder your file is located...
So, cd\...\platform-tools and then flash
The simplest way I perform all of my operations for this:
I leave everything installed into it's default locations. I download tiamat's CWM image and place it into the platform-tools folder.
For Windows 7, I use Windows PowerShell.
For example: Open Start Menu > Type "power" to search, "Windows PowerShell" should show up. (For me, its default at the top - so I press enter to open it)
Once opened: I type this configuration EXACTLY as is: (Keys in <>)
Code:
cd C:\Pr <TAB><TAB> An <TAB> An <TAB> Pl <TAB><TAB> <ENTER>
This above brings me directly to:
C:\Program Files (x86)\Android\Android-sdk\Platform-tools\
Of course, this will be different depending upon your computer setup. I've nailed this routine to get to the path the quickest.
to use FASTBOOT (XOOM already in fastboot mode):
Code:
./fastboot flash recovery rec<TAB><ENTER>
This auto completes the filename as ./recovery-tiamat-r4c-xxxx.img
Of course, depending on how many files/folders you have, you may have to hit <TAB> multiple times. I have to do it 3 or 4 times to select the recovery image I want.
Auto-complete is a nice thing. "./" is added to command from the working directory.
williamthegoat said:
I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS
Thanks for the responses and help guys[/QUOTE
Worked for me too!!! Thanks!!!
Click to expand...
Click to collapse
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.)
XDA Friends,
WOULD YOU LIKE TO MAKE A LITTLE MONEY TODAY???
I am calling out to you in DIRE need. I have royally screwed up my brand new Razer phone (US) and as far as I can tell there is only one way back and that is to get one of you gracious souls to do me a very big favor. What I need is a SD Card that has been formatted to work on a Razor phone and that contains, an ENTIRE cheryl-global-3005.zip. One that has not only the boot.img but the system.img. The reason I need to get this from one of you is that while I was in TWRP I accidentally flashed boot.img in System instead of Boot. This overwrote System and so now I cannot boot into the main system, it essentially goes into a boot loop. So that means I cannot get adb to work which means I cannot move files onto the SD Card (that is specially formatted for that phone and cannot be used to move files physically). And I failed to get the entire image onto the sd card prior to this happening so I do not have a system.img file on the phone in any capacity with which to flash to at least get back to factory.
So I'm thinking that if I can get someone to send me a formatted sd card that contains the full cheryl zip then I can put that card in my phone flash the system.img file from it that should get me back.
If you are willing to help me out with this I WILL PAY YOU.
PLEASE send me a private message here so we can arrange this as soon as possible. I'm phoneless without this fix.
You forgot to mention where are you from, my friend.
My advice comes free of charge:
Hold the power key until the device shuts off. Then download the system images from https://developer.razerzone.com/razer-phone-dev-tools/factory-images/
Unzip this file and run the flash_all.bat file. (I assume you have fastboot set up already considering you've flashed TWRP). Once this completes you should see it booting up to a stock system.
You also have the option of manually flashing the system.img from this factory image using fastboot. No SD card required
Unfortunately, I cannot get to the download mode anymore in order to use fastboot. The only thing I can get to is TWRP. Any other attempt just sends it into bootloop.
@Kimbaroth I'm from North Carolina, United States.
Unfortunately, I cannot get to the download mode anymore in order to use fastboot. The only thing I can get to is TWRP. Any other attempt just sends it into bootloop.
@Kimbaroth I'm from North Carolina, United States.
OK scratch that I am able to get into download mode now. @Flippy125 thanks for the advice. I'll give that a try.
Ok, I am able to run fastboot devices and I can see that it recognizes the device. However, when i try to run "fastboot flash flash_all.bat" I get the following error message: unknown partition 'flash_all.bat'
error: cannot determine image filename for 'flash_all.bat'
I also tried "fastboot push cheryl-global-3005.zip" and that failed with error: unknown command push
I also tried "fastboot flash system.img" and that failed with error: unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
Not sure what I'm doing wrong here. Any thoughts?
lostnsound said:
Ok, I am able to run fastboot devices and I can see that it recognizes the device. However, when i try to run "fastboot flash flash_all.bat" I get the following error message: unknown partition 'flash_all.bat'
error: cannot determine image filename for 'flash_all.bat'
I also tried "fastboot push cheryl-global-3005.zip" and that failed with error: unknown command push
I also tried "fastboot flash system.img" and that failed with error: unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
Not sure what I'm doing wrong here. Any thoughts?
Click to expand...
Click to collapse
I think you meant "fastboot flash system_a system.img"
And you don't need to do "fastboot flash flash_all.bat", you just double click flash_all.bat that is inside the folder and it should work, as long as you have fastboot correctly installed
EDIT: I'm not sure, but I think "flash_all.bat" would erase all your files. Can anyone confirm this?
lostnsound said:
Ok, I am able to run fastboot devices and I can see that it recognizes the device. However, when i try to run "fastboot flash flash_all.bat" I get the following error message: unknown partition 'flash_all.bat'
error: cannot determine image filename for 'flash_all.bat'
I also tried "fastboot push cheryl-global-3005.zip" and that failed with error: unknown command push
I also tried "fastboot flash system.img" and that failed with error: unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
Not sure what I'm doing wrong here. Any thoughts?
Click to expand...
Click to collapse
fastboot flash system system.img
@el4nimal and @waiflih
What is the difference between system and system_a?
Also, can you explain what slot A and slot B are? I have not run into those terms before when rooting other phones (previous was a Nexus 6p).
Thanks for the help guys! I really appreciate it. I'm at work right now so I will try your suggestions at lunch when I can run home for bit.
lostnsound said:
@el4nimal and @waiflih
What is the difference between system and system_a?
Also, can you explain what slot A and slot B are? I have not run into those terms before when rooting other phones (previous was a Nexus 6p).
Thanks for the help guys! I really appreciate it. I'm at work right now so I will try your suggestions at lunch when I can run home for bit.
Click to expand...
Click to collapse
I'm not sure, but I think those are partitions like C:/ and D:/ on a PC.
"System_a" would flash system.img only on Slot A, "System_b" on Slot B, I don't know what "system" does....i think it flashes both
IT'S ALIVE!
So "fastboot flash system system.img" is what worked. Appears that running that command updated system_a based on what I could see in the cmd prompt logging. But it worked as I am now able to boot into the operating system. THANK YOU GUYS SO MUCH!!! You saved me $700. What can I do to support you?
lostnsound said:
IT'S ALIVE!
So "fastboot flash system system.img" is what worked. Appears that running that command updated system_a based on what I could see in the cmd prompt logging. But it worked as I am now able to boot into the operating system. THANK YOU GUYS SO MUCH!!! You saved me $700. What can I do to support you?
Click to expand...
Click to collapse
I'm glad that it worked. Just enjoy it!
Reading this brought a warm feeling to my heart. Have fun with the phone. It's great!
Glad this got sorted. I think I can speak for all of us tinkerers when I say we've all been in this situation before and called upon the forum for advice. Pay it forward ^_^
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
Thread Closed Per OP Request
Don't work,
I give up
Thanks in advanced. All comments can help!
I have a tablet I can depure via USB and where I can root the tablet. But if I connect to the internet, the "registration and password" of university program enters and is saved (even after formatting it is stuck on this screen) blocking the tablet, I believe that after the internet loads, it installs this locking program ... What would be the name of this type of application? I'd like to know, how remove this app, to If connect in internet, we can block (and try install TWRP via internet with TWRP Management)...
C.Modica said:
Hello everyone !
I've been trying to resolve this issue for weeks. I have a tablet that I can't unlock (it's super hard, it's like Dark Souls of tablets). Well let's start.
He has a program that blocks asking for password and user (this a old from a university), where you request access via wireless or 2G/3G. without it you can't access it, so I believe I have to change his firmware instaled in, but I'm having a hard time to make it.
• Let's go to basic product information:
The chip is a RK3066 (same from TV BOX based on rockchip).
The model is YPY L1050 from POSITIVO (it's from Brazil).
- Software and Items
I have the drivers installed (correctly);
I have adb installed;
I have SD_Card;
I have acess from PC;
The tablet is unroot;
• Back to the items:
So, the good news is that I have the same tablet model, unlocked (with another type of ROM that I am unaware of). That works normally, without problems. Well, I saw a procedure that basically it is possible to extract this image from the good tablet, to the locked tablet. I did that, I ended up extracting a series of .img files from the unlocked tablet: boot, cache, kernel, system, etc... ok.
• Trying a extract from unlock same tablet:
I try transfer the copied files from "good unlock tablet" (extrated with AndroidTool), and put in (with the same tool) in the lock tablet... There is a problem, even before starting the operation, I have the error "Test Device Fail ", in the last is not possible to transfer files via USB (I can only do commands like" ResetDevice ", or export the images from the blocked tablet via AndroidTool... and yes I have the drivers instaled, commands like adb sideloader in the fastboot works).
• Trying a firmware found in internet:
Well, I tryed to download the firmware found on the internet corresponding to the device model, but unfortunately I have the same error as above. I download the .img firware original and using the RKBatchTool and have the same error (the operation don't start, give "Test Device Fail" in "Upgrade" and "Restore").
I believe that both operations do not accept transferring via USB.
PS: The tablet unlocked the command of "TestDevice" works fine.
• What I was thinking of doing:
1 - I think I need to take the all .img(s) files extracted from the unlocked device, put it in a single image (.img), put it in a SD_Card and in the "fastboot" take the option "update rkimage from external storage". But I don't know how to do this. (I try search for it);
2 - Somehow being able to do "apply update from external storage", maybe doing the same procedure above with an "update.img", but I also don't know how to do that (put all img. files together in the form of a one update.img).
3 - Have anothers options, like "apply update from ADB", the PC response this conection with tablet, (I can see the device with ''adb device'' cmds in sideload mode in PC). The problem is that I don't know how I'm going to send the .img file, if I send it inside a .zip (I even tried that, send all the .img files inside a .zip to see if it works. The tablet arrives to read the files but in the end the operation aborts). So my knowledge is lacking in this part.
4 - Another would be such a "ROM Dump." I'd like to do a "ROM dump" with an SD card, I even researched it on the internet but I didn't find this procedure to rockchip (only for Amlogic).
With SD Card:
There was a youtube that managed to unlock a tablet like that, but it was a previous model that I'd like to unlock (and different version of firmware, android etc). His method was to put a bootable sd_card, but he doesn't explain how he does it (he only gives the file done) and looking at the files internally, I just think they were converted to linux formats (system.tar.gz, userdata.tar.gz, some .sh .so files, and a bootenv.img, uImage etc) and with completely different names from .img... It is a pity that it is not for my Tablet model .
Well, that's it in the end, I need to change the firmware and I don't know how to do it.
PS: I tried other operations/methods as well, but I will not comment so that this post doesn't get big.
Thanks in advanced. All comments can help!
Click to expand...
Click to collapse
Instead of trying to package the .img files into one file, you should try flashing each .img individually via fastboot using commands with the following structure:
fastboot flash <name of partition> <name of partition.img>
The following commands are examples.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
You will need to use a separate command for each individual .img.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Instead of trying to package the .img files into one file, you should try flashing each .img individually via fastboot using commands with the following structure:
fastboot flash <name of partition> <name of partition.img>
The following commands are examples.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
You will need to use a separate command for each individual .img.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Hi, thanks for the reply. Well I can make it via adb sideload? I can't use the command "adb reboot fastboot". Because this command "adb reboot fastboot" only turns off the tablet don't restarting into fastboot/download mode (just turns off). But If I manually enter on the bootloader, I can access the adb sideload option, where the adb install on computer can detects the device via the "adb devices command" with sideload.
C.Modica said:
Hi, thanks for the reply. Well I can make it via adb sideload? I can't use the command "adb reboot fastboot". Because this command "adb reboot fastboot" only turns off the tablet don't restarting into fastboot/download mode (just turns off). But If I manually enter on the bootloader, I can access the adb sideload option, where the adb install on computer can detects the device via the "adb devices command" with sideload.
Click to expand...
Click to collapse
It isn't going to work via adb unless the device is rooted and then it won't be via adb sideload, it would be done by using dd commands to dd the .img files directly to their partitions.
Sent from my SM-S767VL using Tapatalk
I just found a solution. It requires some tinkering, though.
I had to use a machine running windows 7, because that's the only OS that the drivers worked.
Download the firmware for the Ypy L1050F here: https://www.stockrom.net/2018/07/l1050.html
It comes with the drivers, the ROM, and a tool called RKBatchtool 1.8
You'll have to decompress everything, open RKBatchtool and choose the firmware that is in the ROM folder (Not the DEMO one).
Now comes the tricky part: You gotta undo the 3 screws aroud the tablet, then pry it open with your fingers(remember to remove microSD and SIM first, to avoid breaking stuff!). I recommend startind by the side with the usb, hdmi and power ports to get some leverage. The back cover should pop right off. Then you have to locate the NAND chip in it. Should be a Micron one with 48 pins. The small circle at one of the corners of the chip represents pin 1. Plug your usb cable to the tablet. With the tablet TURNED OFF, use a SIM removal tool or very fine tip metallic screwdriver to short pins 17 and 18 on the NAND chip and plug the power jack into the tablet. RKBatchtool should show that a device was connected. You can release the screwdriver now and just click the "Upgrade" button in RKBatchtool. Now this is very important: DO NOT UNPLUG your tablet until everything is done. It'll tell you when it's done uploading the firmware and checking it. Enjoy your new usable tablet!
I scoured the internet and found this procedure being used for TV Boxes with the same RK3066 SoC. AFAIK, nobody else managed to do it so far, so spread the word.
You are awesome. Broke the internet! I will follow your procedures to try to unlock it. Many thanks again xmas for you.
[edit] don't work