I know it's an old phone. The LG G5. But I bought it because my Galaxy died, the G5 was cheap, you can run Lineage OS on it! But wait! No you can't! You'll never make it past loading the custom recovery file. The guide on Lineage's website is worthless, as it's from before 8.0 Oreo. LG patched the that hole closed tighter than a... a.. <insert good simile here>. I have tried every way in the world to get into this phone. I've looked at every thread here. Dirtycow doesn't work. You can't revert back to 7.x Nougat anymore. It can't be done. LG won't let you in.
I have dreamed of escaping google's clutches. It's really important to me. But I can't afford to buy some $250+ dollar phone that may or may not have a working exploit right now.
This time I gambled and lost, so I'm asking for help. Does anyone know of any way I might salvage the situation? I'd be open to buying a phone with Lineage already on it, if it were reasonably priced. I'd also be open to paying someone else to install it on this LG G5, but I have serious doubts you'd be able to. Any help or advice to get Lineage would be greatly appreciated!
bennylava said:
I know it's an old phone. The LG G5. But I bought it because my Galaxy died, the G5 was cheap, you can run Lineage OS on it! But wait! No you can't! You'll never make it past loading the custom recovery file. The guide on Lineage's website is worthless, as it's from before 8.0 Oreo. LG patched the that hole closed tighter than a... a.. <insert good simile here>. I have tried every way in the world to get into this phone. I've looked at every thread here. Dirtycow doesn't work. You can't revert back to 7.x Nougat anymore. It can't be done. LG won't let you in.
I have dreamed of escaping google's clutches. It's really important to me. But I can't afford to buy some $250+ dollar phone that may or may not have a working exploit right now.
This time I gambled and lost, so I'm asking for help. Does anyone know of any way I might salvage the situation? I'd be open to buying a phone with Lineage already on it, if it were reasonably priced. I'd also be open to paying someone else to install it on this LG G5, but I have serious doubts you'd be able to. Any help or advice to get Lineage would be greatly appreciated!
Click to expand...
Click to collapse
Hey, easy man. There's some things you should consider before giving up on a phone. The quick search i did on Google let me know that this device can be bootloader unlocked, and rooted. At this point, I may ask: Is your device linked in someway with Verizon? Did you unlocked its bootloader? did you manage to install TWRP with no issues? Maybe you´re lucky enough to find a way out yourself. I'll try to help you in everything i can.
eduardvi995 said:
Hey, easy man. There's some things you should consider before giving up on a phone. The quick search i did on Google let me know that this device can be bootloader unlocked, and rooted. At this point, I may ask: Is your device linked in someway with Verizon? Did you unlocked its bootloader? did you manage to install TWRP with no issues? Maybe you´re lucky enough to find a way out yourself. I'll try to help you in everything i can.
Click to expand...
Click to collapse
Thanks! I could really use the help. I have unlocked the bootloader. Made it that far. But I haven't been able to root it because all the root exploits seem to have been patched out by the time I got the phone. It's running Android 8.0. It is a U.S Tmobile phone.
Here's where my progress ground to a halt: I can't get that LG program, LGup, to flash 7.0 to the phone. It gives me an error saying "Error - Invalid KDZ file". Well that's odd, I got that KDZ file from LG's official website. They have a section where they keep all the old stock ROMs.
Maybe I'm wrong here, but I think this part is absolutely necessary. You must install 7.0 Nougat in order to roll back the changes LG made when they patched up the recovery mode. Otherwise you can't install a custom recovery file, which is vital. No custom recovery file = no Lineage. Looking forward to your reply !
bennylava said:
Thanks! I could really use the help. I have unlocked the bootloader. Made it that far. But I haven't been able to root it because all the root exploits seem to have been patched out by the time I got the phone. It's running Android 8.0. It is a U.S Tmobile phone.
Here's where my progress ground to a halt: I can't that LG program, LGup, to flash 7.0 to the phone. It give me an error saying "Error - Invalid KDZ file". Well that's odd, I got that KDZ file from LG's official website. They have a section where they keep all the old stock ROMs.
Maybe I'm wrong here, but I think this part is absolutely necessary. You must install 7.0 Nougat in order to roll back the changes LG made when they patched up the recovery mode. Otherwise you can't install a custom recovery file, which is vital. No custom recovery file = no Lineage. Looking forward to your reply !
Click to expand...
Click to collapse
Here is what i found out. Considering your device is LG G5 H830, with android 8.0, it seems you cant install TWRP straight on. However, there is still something you can try. At this point I may ask: can you enter Fastboot Mode? this your only hope to actually root the phone, and then flash TWRP.
Check if you actually can enter fastboot. If you can, then try to send some basic commands like "fastboot devices" "fastboot reboot". I say this because some devices have Fastboot mode disabled on oem, rendering on useless fastboot. Hope this is not your case. Also, post here your exactly fingerprint version (your rom version). It has to be exactly the same one, otherwise it might soft-brick your phone. Maybe you can flash a patched boot image of your actual rom to then flash twrp.
eduardvi995 said:
Here is what i found out. Considering your device is LG G5 H830, with android 8.0, it seems you cant install TWRP straight on. However, there is still something you can try. At this point I may ask: can you enter Fastboot Mode? this your only hope to actually root the phone, and then flash TWRP.
Check if you actually can enter fastboot. If you can, then try to send some basic commands like "fastboot devices" "fastboot reboot". I say this because some devices have Fastboot mode disabled on oem, rendering on useless fastboot. Hope this is not your case. Also, post here your exactly fingerprint version (your rom version). It has to be exactly the same one, otherwise it might soft-brick your phone. Maybe you can flash a patched boot image of your actual rom to then flash twrp.
Click to expand...
Click to collapse
I can indeed send "fastboot devices" and "fastboot reboot", and it does work. The device will be listed in the command window on the computer, and the phone will reboot if you enter the command "Fastboot reboot".
As for the fingerprint version, here's what I was able to accomplish via a terminal in Manjaro Linux. Is this the full fingerprint?
[[email protected] ~]$ adb devices
List of devices attached
LGH8305d6bec71 device
[[email protected] ~]$ adb shell getprop ro.build.fingerprint
lge/h1_tmo_us/h1:8.0.0/OPR1.170623.032/182251913485f:user/release-keys
[[email protected] ~]$
bennylava said:
I can indeed send "fastboot devices" and "fastboot reboot", and it does work. The device will be listed in the command window on the computer, and the phone will reboot if you enter the command "Fastboot reboot".
As for the fingerprint version, here's what I was able to accomplish via a terminal in Manjaro Linux. Is this the full fingerprint?
[[email protected] ~]$ adb devices
List of devices attached
LGH8305d6bec71 device
[[email protected] ~]$ adb shell getprop ro.build.fingerprint
lge/h1_tmo_us/h1:8.0.0/OPR1.170623.032/182251913485f:user/release-keys
[[email protected] ~]$
Click to expand...
Click to collapse
Its seems you were lucky enough. I checked your rom build and compared it with the only rom on your phone that can be rolled back. It totally matchs the anti-rollback v01 firmware 8.0, so you still can roll-back to Nougat if you try the firmware version H83020c, wich you can download over here:
Fastboot-Flashable rom:
Codefire - Listing of H83020c
KDZ Format rom:
http://dl02.gdms.lge.com:5006/dn/downloader.dev?fileKey=FWAAZHZF92MNARE76685PNJ/H83020o_00_0205.kdz
Its seems the first one it's Fastboot-Flashable, so you should know what to do next if the KDZ Rom doesn't work. However, check this website and compare the rom build yourself, just to be clear about it:
Download T-mobile LG G5 H830 Stock kdz firmware H83030C
Download T-mobile LG G5 H830 Stock kdz firmware H83030C -
www.mylgphones.com
The first link has 3 flashable roms there. including KDZ and fastboot format. Make sure to try them all if one doesnt work
If both methods are useless to roll back to Nougat, dont hesitate to tell me. There's still a workaround available.
To be clear, the phone needs to be in "Firmware update" mode in order to use flashboot to flash that Fastboot rom, correct? That's where a "Firmware update" message appears on the screen, and it's encircled by two arrows. It's in the middle of the screen, and it's not small like when you're using fastboot.
I ask because iirc, KDZ files require the use of LGup, that LG official program.
bennylava said:
To be clear, the phone needs to be in "Firmware update" mode in order to use flashboot to flash that Fastboot rom, correct? That's where a "Firmware update" message appears on the screen, and it's encircled by two arrows. It's in the middle of the screen, and it's not small like when you're using fastboot.
I ask because iirc, KDZ files require the use of LGup, that LG official program.
Click to expand...
Click to collapse
It needs to be in firmware update mode only if you are flashing a kdz rom through Lg official flashtool. If you are going to flash through fastboot, you have to make sure your PC recognizes your device sending "fastboot devices". The fastboot flashable room is right in the first link (.zip file, 1,6 GB size file)
The one I'm seeing says it's 1.9 Gigabytes in size. It's #15 on that list, and it's called:
LG-H83020c-Flashable.COMPLETE-ARB01.zip
Correct?
Just wanna be clear on this, the last thing we need is a brick lol
bennylava said:
The one I'm seeing says it's 1.9 Gigabytes in size. It's #15 on that list, and it's called:
LG-H83020c-Flashable.COMPLETE-ARB01.zip
Correct?
Just wanna be clear on this, the last thing we need is a brick lol
Click to expand...
Click to collapse
That should be it. Download it and check it has all partitions (boot, system, recovery, etc...)
You are probably gonna have to flash each partition manually (for example, if you are flashing system, you should write "fastboot flash system system.img" and so on)
Below is a pic of everything that came in that zip file, just to make sure we're on the same page and I've got everything necessary.
I must admit that I'm a little intimidated by flashing each individual component in that zip file. I understand that you can just tell it "Flash this thing!" and it will do it. But how does it know where exactly to flash the new thing? How does it know not to just write it over the previous item you just flashed?
Next question: What all needs to be flashed individually? As you can see, there are a total of 28 entries shown in the pic. But the folders "bootloader" and "META.INF" both contain a lot of stuff. Do you just flash bootloader and META.INF, and it already knows to flash everything the folder contains?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bennylava said:
Below is a pic of everything that came in that zip file, just to make sure we're on the same page and I've got everything necessary.
I must admit that I'm a little intimidated by flashing each individual component in that zip file. I understand that you can just tell it "Flash this thing!" and it will do it. But how does it know where exactly to flash the new thing? How does it know not to just write it over the previous item you just flashed?
Next question: What all needs to be flashed individually? As you can see, there are a total of 28 entries shown in the pic. But the folders "bootloader" and "META.INF" both contain a lot of stuff. Do you just flash bootloader and META.INF, and it already knows to flash everything the folder contains?
Click to expand...
Click to collapse
You don't have to write "fastboot flash" 28 times. You can just write "fastboot flash all". But I'd rather flashing manually.
Ignore the META-INF folder. You can't flash any file inside there. You should only flash every file ending in "xx. Img* such as boot.img or. system.img.
This zip contains that folder because it was meant to be flashed through recovery, but if you try to do that, the recovery will not do it, or it will cancel installation, as there is a line that checks your actual fingerprint to avoid Rolling back.
So the command to flash that whole bootloader file at once is "flashboot flash all bootloader"? And it won't care that it's a folder, and not a .img file?
I see what you mean about flashing the .img files that are below the "bootloader" folder in that pic I posted. To me it makes sense that it would flash those. But as you said, you should only flash every file ending in .img and "bootloader" is actually a folder, even if it is full of those files. So I just want to be clear on how exactly to flash that bootloader file.
Sorry about all the newb questions lol. Once I see your reply here, I'm going to attempt the flash. After that, hopefully I won't need any more help.
bennylava said:
So the command to flash that whole bootloader file at once is "flashboot flash all bootloader"? And it won't care that it's a folder, and not a .img file?
I see what you mean about flashing the .img files that are below the "bootloader" folder in that pic I posted. To me it makes sense that it would flash those. But as you said, you should only flash every file ending in .img and "bootloader" is actually a folder, even if it is full of those files. So I just want to be clear on how exactly to flash that bootloader file.
Sorry about all the newb questions lol. Once I see your reply here, I'm going to attempt the flash. After that, hopefully I won't need any more help.
Click to expand...
Click to collapse
Let's try something a little bit easier first. As you say you unlocked bootloader, maybe you can flash the full rom through recovery. Copy the rom to a sdcard and try that first, maybe you will save yourself a lot of headaches doing this first.
I've bought two H830's and got both to TWRP/LOS ROM no problem. Regardless of your current official build on your phone, you can rollback to version 30c and dirtycow from there to get TWRP. You can get necessary tools/info from here.
0. (If you havn't already...) Enable OEM unlock in settings and unlock bootloader/fastboot
1. Use LGUP tool to clean flash an official 30c version (H83030c_00_0813.kdz) build to your LG H830
2. Dirtycow exploit to get TWRP
3. Use TWRP to install
Let me know how it shakes out
Also an important note, you CANNOT flash directly the recovery via fastboot to get TWRP, only the H850 can do that, NOT the H830. That's something important no one ever brings up. You must use the dirtycow exploit.
EDIT: Oh yeah, and I recommend using UPPERCUT to flash the kdz file since LGUP is such broken trash.
eduardvi995 said:
Let's try something a little bit easier first. As you say you unlocked bootloader, maybe you can flash the full rom through recovery. Copy the rom to a sdcard and try that first, maybe you will save yourself a lot of headaches doing this first.
Click to expand...
Click to collapse
So just put the zip file on my external SD card, and then tell flashboot to...? Or somehow use only the phone itself to flash the rom? Sorry I'm afraid I'm having trouble following along as I've never done this before.
But as per your instructions, the rom (the whole zip file) is now on the external storage SD Card.
Or did you mean to extract the zip file to a folder, and put that on the SD card? My next question would be thus:
What is the exact command to begin flashing, once I have everything in it's proper place? I did a little experiment where I tried to flash one of the files individually. The Linux terminal gave me the following error:
[[email protected] Desktop]$ cd bootloader
[[email protected] bootloader]$ fastboot flash aboot.img
unknown partition 'aboot.img'
fastboot: error: cannot determine image filename for 'aboot.img'
[[email protected] bootloader]$
As you can see, the bootloader folder is on the desktop, with many .img files inside it. Just as the pic in post #11 shows. Inside the bootloader folder is a .img file called "aboot.img". And for some reason fastboot "cannot determine the image filename for aboot.img"
DrowningInFreedom said:
EDIT: Oh yeah, and I recommend using UPPERCUT to flash the kdz file since LGUP is such broken trash.
Click to expand...
Click to collapse
Thank you for the reply! I've got two questions for you:
1. Do you have a link to the version of LG UP that you'd recommend using? It seems that there are many links out there in the wild, and some of them are to old versions. I'm not sure exactly which one I should use.
2. How exactly do you use Uppercut with LG Up? I got Uppercut, but it didn't seem to do anything when I double clicked on it. It just sat there. Is it like some kind of addon or modification to LG up? Or is it supposed to open as it's own program. Thanks!
Use the files provided by codefire , Launch UPPERCUT which will then hook into and launch LGUP automatically (All it does is make LGUP work without errors)
DrowningInFreedom said:
Use the files provided by codefire , Launch UPPERCUT which will then hook into and launch LGUP automatically (All it does is make LGUP work without errors)
Click to expand...
Click to collapse
Here's what happened when I tried to flash the right 80320a file (Nougat):
Any idea why it would say that?
Related
Hello!
It seems like I am one of the few people to have a RS987 variant of the V10. I love everything about this phone, but it's killing me not having root access. I've avoided making a topic dedicated to this variant by posting in other threads and PMing people, but I've gotten nowhere.
I'm unable to unlock the bootloader like the T-Mobile variant even though I have to ability to enable "OEM Unlock" in the dev settings, and I've attempted to flash the Verizon VS990 5.1.1 KDZ to my phone in hopes I could root it after flashing it but it failed.
I'm willing to donate $40 to anybody that can provide a root method for RS987 variant of the V10.
Check this out.
http://forum.xda-developers.com/lg-...d-lollipop-kdz-10c-lg-servers-t3332348/page15
First post last link.
SoulAce1290 said:
Check this out.
http://forum.xda-developers.com/lg-...d-lollipop-kdz-10c-lg-servers-t3332348/page15
First post last link.
Click to expand...
Click to collapse
This just the KDZ for stock 5.1.1, which I provided
I should have posted this earlier but I was kind of busy IRL...
Anyway, it should be noted that I DO NOT have an RS987, therefore THIS HAS NOT BEEN TESTED! The usual disclaimers about voiding your warrenty, bricking your device, killing your cat ...etc applys.
Basically, flash
https://mega.nz/#!8k1UyCyC!Z2NIKvNOEkXBiElMLrXkv0RyPKhCN2q0KvlI1OH6ImY
this DZ file with
https://mega.nz/#!xgMgBIQD!VHtXeIlzpPydKRICtGfBUjXvtdN-KNtqX6U9bu3bY8Y
this DLL in LGUP.
I did not modify anything except /system, so theoretically you should be able to flash back the stock KDZ in download mode even if you experience bootloops.
Succeeded in flashing out.dz ... but
I succeeded in flashing the provided out.dz with LGUP, however, the phone would stall at initial LG logo, and wouldn't make the startup sound or animation.
Flashing back to the stock image for the RS987 worked fine, however. Even the carrier settings stayed.
A this point I can't verify if the bootloader is locked or not, I can't get into fastboot, just LG Download mode. Of course I'd be able to easily enable fastboot if I had root by writing zero's to the LAF partition. Ugh catch 22.
I also tried flashing the VS990 image for verizon pre-rooted system... no luck, LGUP refuses since it's not the same model number. I have a pre-rooted system.img file that I created using the extracted system.img from the stock .kdz. But I have not way to re-pack it into a .kdz or .dz file. Of course, I don't know if my rooted system image would work, since I can't test it.
Love the phone, but I'm so sick of Androids being locked down so tight.
WillyPillow said:
I should have posted this earlier but I was kind of busy IRL...
Anyway, it should be noted that I DO NOT have an RS987, therefore THIS HAS NOT BEEN TESTED! The usual disclaimers about voiding your warrenty, bricking your device, killing your cat ...etc applys.
Basically, flash
LINK REMOVED
this DZ file with
LINK REMOVED
this DLL in LGUP.
I did not modify anything except /system, so theoretically you should be able to flash back the stock KDZ in download mode even if you experience bootloops.
Click to expand...
Click to collapse
joatamonk said:
I succeeded in flashing the provided out.dz with LGUP, however, the phone would stall at initial LG logo, and wouldn't make the startup sound or animation.
Flashing back to the stock image for the RS987 worked fine, however. Even the carrier settings stayed.
A this point I can't verify if the bootloader is locked or not, I can't get into fastboot, just LG Download mode. Of course I'd be able to easily enable fastboot if I had root by writing zero's to the LAF partition. Ugh catch 22.
I also tried flashing the VS990 image for verizon pre-rooted system... no luck, LGUP refuses since it's not the same model number. I have a pre-rooted system.img file that I created using the extracted system.img from the stock .kdz. But I have not way to re-pack it into a .kdz or .dz file. Of course, I don't know if my rooted system image would work, since I can't test it.
Love the phone, but I'm so sick of Androids being locked down so tight.
Click to expand...
Click to collapse
Sorry about that. Too bad I don't have an RS987 to debug the issues. How about you send me your img file and I'll try to pack it for you?
I don't think the bootloader is unlocked for the variants except H960A and the T-Mo one. Also, you can view the bootloader status under the hidden menu.
Pre-rooted system.img file for RS987 LG V10
WillyPillow said:
Sorry about that. Too bad I don't have an RS987 to debug the issues. How about you send me your img file and I'll try to pack it for you?
I don't think the bootloader is unlocked for the variants except H960A and the T-Mo one. Also, you can view the bootloader status under the hidden menu.
Click to expand...
Click to collapse
WillyPillow, thank you for the offer to attempt to repack this system.img file into a .DZ file that'd be flashable to the LG V10 RS987...
I've PM'd you a link to a Google Drive with the rooted system.img
One file is system.rar and has a rooted system.img file that works with the RS987 LG V10.
The other file is RS98711a_02_0309.rar which is where I extracted the stock system.img file from. It was a multi-part system.bin file which I extracted and merged with "WindowsLGFirmwareExtractor".
I used the imgrooter script that worked for rooting my LG G4 phone which also had the same version of Lollipop 5.1.1. With LG G4 I was able to flash the file from download mode by opening a shell prompt with the phone using Send_Command.exe ... I was able to get Send_Command.exe to work with the LG V10, by first unlocking the mode by beginning to flash a .KDZ file and then unplugging the USB cable at the 9% progress mark. At this point I had a shell prompt with the phone. HOWEVER, I had extremely limited commands available. I could list files/folders, and run CAT on any file I wanted, but the command for dd or chmod or chown would all crash my shell prompt with the error "Hello I am LAF nice to meet you." At that point all commands with the phone would cease and go back to displaying "FAIL" for any command. (Really strange. I wish LAF would give me DD command from that shell prompt and I'd tell it where to put my system.img file!)
So, good luck re-packing this system.img back into a .DZ file I can flash.
I'm sure myself and other RS987 owners who frequent this forum would love a pre-rooted flashable system image.
Thanks in advance for your efforts.
@joatamonk
I just remembered what the problem is. I forgot a critical step in making the DZ
Unfortunately, I'm a bit busy recently, and I might not be able to fix this until next week. Sorry to keep you waiting.
joatamonk said:
WillyPillow, thank you for the offer to attempt to repack this system.img file into a .DZ file that'd be flashable to the LG V10 RS987...
I've PM'd you a link to a Google Drive with the rooted system.img
One file is system.rar and has a rooted system.img file that works with the RS987 LG V10.
The other file is RS98711a_02_0309.rar which is where I extracted the stock system.img file from. It was a multi-part system.bin file which I extracted and merged with "WindowsLGFirmwareExtractor".
I used the imgrooter script that worked for rooting my LG G4 phone which also had the same version of Lollipop 5.1.1. With LG G4 I was able to flash the file from download mode by opening a shell prompt with the phone using Send_Command.exe ... I was able to get Send_Command.exe to work with the LG V10, by first unlocking the mode by beginning to flash a .KDZ file and then unplugging the USB cable at the 9% progress mark. At this point I had a shell prompt with the phone. HOWEVER, I had extremely limited commands available. I could list files/folders, and run CAT on any file I wanted, but the command for dd or chmod or chown would all crash my shell prompt with the error "Hello I am LAF nice to meet you." At that point all commands with the phone would cease and go back to displaying "FAIL" for any command. (Really strange. I wish LAF would give me DD command from that shell prompt and I'd tell it where to put my system.img file!)
So, good luck re-packing this system.img back into a .DZ file I can flash.
I'm sure myself and other RS987 owners who frequent this forum would love a pre-rooted flashable system image.
Thanks in advance for your efforts.
Click to expand...
Click to collapse
Sorry about the (extremely) late reply.
Here's the updated DZ:
https://mega.nz/#!VkFlGCRK!tNegI52h6aPNYU98pQ6RISmlr53ok57XHZvjIQZR4xM
Hope it works!
No luck
WillyPillow said:
Sorry about the (extremely) late reply.
Here's the updated DZ:
https://mega.nz/#!VkFlGCRK!tNegI52h6aPNYU98pQ6RISmlr53ok57XHZvjIQZR4xM
Hope it works!
Click to expand...
Click to collapse
I thank you greatly for your efforts, however this .dz file didn't work. It got farther than the last one you had made. After flashing it with LG UP 1.14 the phone would reboot, show the android guy (the one with a spinning gear in it's belly), that screen would stay for about 5 seconds, phone would restart again, and then get stuck on the initial LG power up screen, it never played the startup sound or showed the animated LG logo.
RS987 must be a little different than the Verizon version? Perhaps it only loads signed kernels, or signed images or something?
Is this .dz file made from the pre-rooted image I had uploaded? Is there software that can be used to pack .DZ files from the .img file? So that I can try different methods of rooting system.img and flashing that to the phone?
The good news is the phone works fine after I flashed the stock RS98712a file back to the phone.
Thank you again for your efforts, they're appreciated.
Joata
Subscribed
I have the LG v10 from T-Mobile. I bought the phone a few weeks ago and it had Marshmallow installed. Somehow I managed to install TWRP/SuperSU, but then had issues and flashed the official/stock MM image with LGUP. Afterwards I discovered that MM for this device is not currently rootable, and TWRP cant be flashed via fastboot because MM blocks it. So I returned the device to T-Mo store, lied and said it force-upgrade to MM and had began freezing up. They did an in-store trade for an identical model that had 5.1.1 Lollipop.
The device is currently still in factory condition in every way, with the exceptions that I unlocked the bootloader via fastboot and installed TWRP. Nothing else is modified yet and no custom ROMs have been flashed.
I recently became aware that there is no stock LP image for the T-Mo v10, only MM images are available. After all the issues I've had, I'm now paranoid and want to have a complete dump of the phone's entire contents (partitions, bootloader, system, etc) that is in KDZ or TOT format, and can be reflashed with the standard tools available. Since there is nothing official then I would have to do this myself. This would be useful in the event that I run into lots of issues and need to do a emergency stock restore.
I found a thread by XDA user @tungkick, in which he created a modified dump of the device while it was running LP. However, because it was unofficial and he didn't disclose this upfront, his thread was shut down. His file bricked multiple MM users. I assume it would work if one was still on LP and hadn't upgraded to MM. Not to mention that I cant seem to find his file anywhere. So I figure the safest way is to do this myself. I would be willing to make this file available to the community when finished, with full disclosure that it is unofficial. But the problem is, I don't know how.
I know that the Linux dd command can be used to dump images of various things, and I have read that this can be done on PC by connecting to the device via ADB or fastboot. This would hopefully result in an image file that contained the contents of all the device's partitions.
But another issue would be converting it to KDZ or TOT. And it would have to be done in such a way that it would be flashable with the standard tools.
Can someone please give me a technical understanding of the tools and knowledge I would need to undertake this? Would it be too complicated for someone like myself that has little Android/Linux experience (but is generally competent with computers/technology)?
Thanks for any advice!
Noone can help me with this?
To the mods/admins: I think maybe I posted this in an area where it is unlikely to get any useful answers. Can someone move the thread to the Help& Troubleshooting area of the general LG v10 forum (not here in the T-Mobile subforum)? Thanks!
I think it's just that if that could. have been done someone would have done it already. Even tungkick didn't make one for tmobile for some reason. I think because he made his root injected files from official lg files and lg has not released a kdz or tot for tmobile LP.
Just my observation... I could be wrong.
Sent from my pretty nifty brand new LG V10
@ planetbeen: I don't see why it wouldn't be possible. Linux's dd program can dump almost any connected device that it can see. But then it needs to be converted into a standard TOT/KDZ that can be flashed with any standard software. Which is why I want to create an unofficial backup of the entire phone before modifying it further, so I can do an emergency restore if necessary. I just need the right instructions from people who have the technical expertise.
I had trouble with my old LG v10, I had used LG's LGUP program to flash it to Marshmallow from my PC, only to realize that it couldn't be rooted or have a custom recovery. And I also discovered that I couldn't downgrade to Lollipop. So I returned the phone to the store and exchanged it for an identical model that still had LP. I just told them it had auto-upgraded to MM and started crashing. They exchanged, no questions. Before this I had various issues, like GPS crashing randomly when turning it on, Bluetooth also doing the same thing, and the Settings app also crashed sometimes when accessing the Security menu. I had flashed multiple ROMs, but stock-based and CM/AOSP-based, but kept running into issues, oftentimes the same ones. So I figured that something in the phone had become corrupt and figured that flashing stock MM would fix everything. Big mistake. I'll never let this phone upgrade again until MM is solidly hacked, which from what I've read may be a long time away. I paid enough for this phone and I really value hackability. I'm not the average Joe that just uses my phone for Facebook, etc. To me, if a phone cant be hacked, then buying/owning it is a waste of time/money. Same thing with every computer/electronics device I've ever owned.
Thanks again!
It looks like I'm going to have problems getting answers from knowledgable people, so instead of waiting, I'm going to take a little initiative and at least try to do the dump with dd. I found a post by @tungkick that says to enable USB debugging and make a backup file via dd with the 'adb shell' and 'su' commands. Is the following syntax correct?
dd if=/dev/block/mmcblk0 of=/sdcard/H901.bin bs=1024 count=6291456
Do I run these commands from a PC via command line while connected via USB? Or directly on the device in a terminal emulator? Or do I need to run the command while in fastboot/bootloader mode, while Android is powered down?
Thanks again!
Stock use tool extract kdz then choose file dz (use lgup)
remember can not flash if phone update 6.0
Never downgrade because phone brick now.
version 5.1.1
https://drive.google.com/file/d/0B_Hol5T47S-bQkJVemgzMDV0Nzg/view?usp=sharing
@ tungkick: Thanks for the info. I had used the dd command to dump my phone to external SD before, but the file was 6GB! I was unable to use Tool KDZ Extract to extract the *.dz from the *.kdz file you provided. I was able to flash your KDZ with LGUP, but it boots me into TWRP recovery near the end.
Do you mind if I publicly distribute a mirror copy of your file on my Dropbox, so that it will be available to others that need the stock LP firmware for this device?
Thanks again!
I just wanted to say that flashing your KDZ has possibly screwed up my device permanently. Your image has TWRP, not the stock recovery, and is pre-rooted with SuperSU. Normally this would be good but...............
Near the end of LGUP, the device boots into TWRP. System and MicroSD are mounted, but nothing else (data, cache, dalvik, etc). I was able to obtain a stock recovery *.img, then copied it over to my MicroSD while in recovery. Then I flashed it, booted the phone into stock recovery, and performed a factory reset. Afterwards I booted into system, and all looked good, until it got to the "Checking connection" screen, then a lot of apps started force-closing repeatedly. Because of this I can't get to the Home screen, and no amount of factory reset is working. It just keeps happening over and over again.
How to get out of this mess, anyone?
Help please!!!
Still looking for a solution and would really appreciate any help!
My theory is that the /cache and /data partitions somehow got corrupted during the flash. So I tried booting into FastBoot mode and issueing the commands:
fastboot erase cache
fastboot format cache
fastboot erase userdata
fastboot format userdata
It just says something something along the lines of "remote: cant format/erase in an unlocked state". If I relock the bootloader, it says that it cant erase/format in a locked state.
TWRP still cant read those partitions (they won't mount and cant be mounted), and the apps still start force-closing almost immediately after rebooting into system, before I can complete the setup, preventing me from getting to the home screen.
@ tungkick: Is there any possibility we can arrange a TeamViewer meeting to fix this?
Thanks!
Hello,
I currently have an H932 with a corrupt LAF on pie. I am unable to root or downgrade because of this. My phone is laggy and unresponsive at times and hope to upgrade soon. If anyone could help to get the .up file for my h912. The link below is instructions on how to get this URL or .up file.
https://www.the***********.com/how-to-capture-ota-update-url-android/
Thanks,
zapzapdew
Same here,. hopefully someone that has not yet updated, or has just started the h932 root process can capture the ota before continuing the steps
Repairing LAF Partition with LG Bridge
zapzapdew said:
Hello,
I am unable to root or downgrade because of this. My phone is laggy and unresponsive at times and hope to upgrade soon.
Click to expand...
Click to collapse
I face similar issue when I reset my phone (also h932) and then TWRP deleted and replaced by stock recovery. I tried to install twrp again via lafsploit method no luck. my phone not detected on my PC. so I decide to download LG Bridge and perform an update (I assume that your phone can boot android). If your phone is already running 30d pie then click update error recovery (see image below). If you still on older version you can update to recent version without update error recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
proceed and wait till complete. laf partitiom will be restored and download mode works as usual
download LG Bridge
(select software update >> software update tool)
immns said:
proceed and wait till complete. laf partitiom will be restored and download mode works as usual
download LG Bridge
(select software update >> software update tool)
Click to expand...
Click to collapse
May I ask did your phone bootloader unlocked when update using LG bridge. Actually I try before using update error recovery but no luck. After download firmware when install update on stock recovery, it hang on 5% then restart. My phone is bootloader unlocked when I try. Is it necessary has to be on locked bootloader. Thank you.
hendavi said:
May I ask did your phone bootloader unlocked ..... Thank you.
Click to expand...
Click to collapse
yes, i did it with unlocked bootloader. in my case, i could enter download mode but my pc couldn't detect any device. have you tried to enter download mode manually? what's look like? mine says "unknown 0/0/0"
if you never try to flash laf partition with another things (e.g stock laf or twrp), it might be still using h933 laf, and that means you can try to flash twrp using fwul
immns said:
yes, i did it with unlocked bootloader. in my case, i could enter download mode but my pc couldn't detect any device. have you tried to enter download mode manually? what's look like? mine says "unknown 0/0/0"
if you never try to flash laf partition with another things (e.g stock laf or twrp), it might be still using h933 laf, and that means you can try to flash twrp using fwul
Click to expand...
Click to collapse
Thank you for reply, I have try manual enter to download mode but not successful. The phone restart when it boot into download mode.
I try flash twrp using fwul, thanks for the info.
hendavi said:
Thank you for reply, I have try manual enter to download mode but not successful. The phone restart when it boot into download mode.
I try flash twrp using fwul, thanks for the info.
Click to expand...
Click to collapse
Do you know what version of LAF you are running? It was pointed out in the root thread that after you get TWRP, you need to flash the correct version of LAF or put TWRP on LAF.
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
Do you know what version of LAF you are running? It was pointed out in the root thread that after you get TWRP, you need to flash the correct version of LAF or put TWRP on LAF.
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
I don't know what laf do I have now, probably is stock laf because after flash pie stock rom I forget to flash RCTD Remover and Disable DM-Verity zip.
Unable to flash TWRP because my phone cannot go to download mode. Thanks anyway.
immns said:
yes, i did it with unlocked bootloader. in my case, i could enter download mode but my pc couldn't detect any device. have you tried to enter download mode manually? what's look like? mine says "unknown 0/0/0"
if you never try to flash laf partition with another things (e.g stock laf or twrp), it might be still using h933 laf, and that means you can try to flash twrp using fwul
Click to expand...
Click to collapse
could you solve your problem ???? The same happens to me, if you could answer thank you very much.
lost download mode and twrp, also root.
I would like to know if there is any way}, thanks
Reposting this here for visibility:
Hello all. So I am having a similar issue. I was already running a stock rom and I flashed the stock laf from the stock H932 thread. However, I noticed that the latest laf version from that thread doesn't match the latest firmware. I'm not sure if that was the cause but I lost my download mode abilities and twrp recovery (booting into recovery shows "no command". My bootloader is still unlocked and the device will boot into the stock system but download mode freezes whenever accessed meaning I can't use either oreo or pie LGUP to repair it. It shows Unknown B79 and says Unknown / E / L / RO at the bottom. Does anyone have an idea on if there is anything I can do to restore download mode? I noticed I have Would it cause problems to relock the bootloader at this point, as I would like to relock it with the coming changes to safetynet. Thank you for any help.
I don't have any suggestions other than what was already posted in the H932 root thread.
1) If you're NOT already on Pie, you should be offered an OTA update, which will repair Download mode (at least previous OTA updates did that).
2) If you're already on Pie, you need that Pie OTA file which everybody is looking for. Force flashing that with LGUP in FOTA mode (inside the OS) should also repair Download mode (at least previous OTA updates did that).
Do NOT relock the bootloader unless the phone is completely, 100% stock. Otherwise you'll get a brick on next boot, when signature checks are performed on all partitions. As I understand, this will blow a Qfuse, which is irreversible.
TheDannemand said:
I don't have any suggestions other than what was already posted in the H932 root thread.
1) If you're NOT already on Pie you, should be offered an OTA update, which will repair Download mode (at least previous OTA updates did that).
2) If you're already on Pie, you need that Pie OTA file which everybody is looking for. Force flashing that with LGUP in FOTA mode (inside the OS) should also repair Download mode (at least previous OTA updates did that).
Do NOT relock the bootloader unless the phone is completely, 100% stock. Otherwise you'll get a brick on next boot, when signature checks are performed on all partitions. As I understand, this will blow a Qfuse, which is irreversible.
Click to expand...
Click to collapse
Thanks for the info. I'm already on pie. It seems the .up file is nowhere to be found. I can use the phone as is but with the bootloader unlocked I'm hoping that I won't be affected by the supposed upcoming safetynet changes. Is there no other way to repair the laf partition besides getting a hold of a file it seems no one has? Thanks for your help.
tbxn said:
Thanks for the info. I'm already on pie. It seems the .up file is nowhere to be found. I can use the phone as is but with the bootloader unlocked I'm hoping that I won't be affected by the supposed upcoming safetynet changes. Is there no other way to repair the laf partition besides getting a hold of a file it seems no one has? Thanks for your help.
Click to expand...
Click to collapse
I do understand. But remember that Qualcomm, LG and T-Mobile all went out of their way to make sure that this phone was locked down and un-rootable. They stripped flash and boot commands from fastboot. And they choose RSA signatures different from all the other V30 models, so that it would be like a prison island in the middle of the ocean.
The only reason we can still root it at all, is because of a massive effort by a brilliant and knowledgeable Dev, who reverse engineered the boot and laf code. And he found this narrow path to let us root it.
But that doesn't mean the H932 just rolls over and starts to cooperate with us: It's still designed to make it as difficult as possible for us to do what we're trying to do. And it is very unforgiving of any mistakes.
So once both TWRP and Download mode and root (in the OS) are gone, there's not much left to fix the situation. The only thing left is LGUP FOTA. But it requires an OTA file. Several were posted for Oreo, but none so far for Pie.
Anybody with an H932 and enough time on their hands can capture it, if they're willing to roll back to Oreo (losing their data) then update again using OTA.
TheDannemand said:
I do understand. But remember that Qualcomm, LG and T-Mobile all went out of their way to make sure that this phone was locked down and un-rootable. They stripped flash and boot commands from fastboot. And they choose RSA signatures different from all the other V30 models, so that it would be like a prison island in the middle of the ocean.
The only reason we can still root it at all, is because of a massive effort by a brilliant and knowledgeable Dev, who reverse engineered the boot and laf code. And he found this narrow path to let us root it.
But that doesn't mean the H932 just rolls over and starts to cooperate with us: It's still designed to make it as difficult as possible for us to do what we're trying to do. And it is very unforgiving of any mistakes.
So once both TWRP and Download mode and root (in the OS) are gone, there's not much left to fix the situation. The only thing left is LGUP FOTA. But it requires an OTA file. Several were posted for Oreo, but none so far for Pie.
Anybody with an H932 and enough time on their hands can capture it, if they're willing to roll back to Oreo (losing their data) then update again using OTA.
Click to expand...
Click to collapse
I understand, and I am also very grateful for the work put in by that dev and the many others here on xda who help other users out. Perhaps some generous person will be able to do like you mentioned and be able to capture the OTA link. Just out of curiousity, what would that process look like? Roll back to oreo via lgup? And then what would be the best way to capture the link? Could it be done without root? Thanks again for your input.
tbxn said:
I understand, and I am also very grateful for the work put in by that dev and the many others here on xda who help other users out. Perhaps some generous person will be able to do like you mentioned and be able to capture the OTA link. Just out of curiousity, what would that process look like? Roll back to oreo via lgup? And then what would be the best way to capture the link? Could it be done without root? Thanks again for your input.
Click to expand...
Click to collapse
Yes, roll back to Oreo with LGUP. The best way to do that is via Nougat in Partition DL mode, in order to rewrite the partition table. Then to Oreo from there, Upgrade mode should work.
Then trigger the OTA (if it doesn't come right away) by changing the date forward a few days at a time.
Once the OTA is offered, there is a process to capture the link. I've never done it myself. The OP posted a link in post #1, but XDA scrambled it for the benefit of... well, someone, we'd hope. Google should be able to find it.
One thing I forgot: You can also try LG Bridge Recovery mode, if you haven't already. Some reported it fixed their Download mode, others say it requires Download mode. Worth a try. See post #2.
Edit: Capturing the OTA does NOT require root, that much I remember. I seem to recall you just search through logcat file immediately after starting the OTA download. But again, I haven't done it myself.
TheDannemand said:
Yes, roll back to Oreo with LGUP. The best way to do that is via Nougat in Partition DL mode, in order to rewrite the partition table. Then to Oreo from there.
Then trigger the OTA (if it doesn't come right away) by changing the date forward a few days at a time.
Once the OTA is offered, there is a process to capture the link. I've never done it myself. The OP posted a link in post #1, but XDA scrambled it for the benefit of... well, someone, we'd hope. Google should be able to find it.
One thing I forgot: You can also try LG Bridge repair mode, if you haven't already. Some reported it fixed their Download mode, others say it requires Download mode. Worth a try. See post #2.
Click to expand...
Click to collapse
Yea, I tried LG Bridge but I ran into the same problem as LGUP. When the phone reboots to enter download mode it freezes in download mode. It does the same thing when I manually enter download mode. I tried different ports, cords, pcs etc. all the same outcome.
However, I may be able to get ahold of another H932 so that I can possibly try my hand at capturing the ota link. I have to be more careful with this one, haha. It was never rooted or bootloader unlocked and I have no intention of doing that. Does it still need to be rolled back to nougat to rewrite the partitions if it was always stock? If so, then I would flash Nougat_h93210c_00_1017.kdz in Partition DL mode selecting all partitions, then flash Oreo_h93220h_00_0416.kdz (in Partition DL mode selecting all partitions again?) and then capture the update url when I get it via adb, correct?
The H932 handset that lost twrp and download mode was last flashed with one of the latest twrp flashable roms based on the kdz and not the actual stock kdz so I hope it still has a chance of working, but at the very least hopefully I can capture the ota url for some other's benefit.
That's a good plan, including the bit about being extra careful
I would first perform a Factory Reset (from Settings menu) while still in Pie. This will save you from FRP and possibly other issues. Then LGUP Partition DL back to Nougat 10d, using the latest Dev Patched LGUP from one of ChazzMatt's threads. Then reboot. If any problems Master Reset (Button Dance). Then LGUP Upgrade to latest Oreo 20s. Reboot.
Make sure you know what to do when you get the OTA offer BEFORE you get it.
I think there's a good chance you'll be able to salvage your other H932. It doesn't have to be completely stock for LGUP FOTA to restore Download mode. At least that's what others reported.
And posting that Pie OTA will be a great help for many people!
Edit: Of course there IS a risk to the unlocked phone. People have had issues going back and forth to Pie. Just saying...
TheDannemand said:
That's a good plan, including the bit about being extra careful
I would first perform a Factory Reset (from Settings menu) while still in Pie. This will save you from FRP and possibly other issues. Then LGUP Partition DL back to Nougat 10d, using the latest Dev Patched LGUP from one of ChazzMatt's threads. Then reboot. If any problems Master Reset (Button Dance). Then LGUP Upgrade to latest Oreo 20s. Reboot.
Make sure you know what to do when you get the OTA offer BEFORE you get it.
I think there's a good chance you'll be able to salvage your other H932. It doesn't have to be completely stock for LGUP FOTA to restore Download mode. At least that's what others reported.
And posting that Pie OTA will be a great help for many people!
Edit: Of course there IS a risk to the unlocked phone. People have had issues going back and forth to Pie. Just saying...
Click to expand...
Click to collapse
Yes, I have taken a look at the steps to capture the link and they seem simple enoughto just use adb logcat while the ota downloads. But I just want to clarify beforehand... When I use LGUP to partition dl back to nougat I think I should be selecting all partitions, but when I go from nougat to oreo should I be using partition dl again and selecting all partitions once again? Just want to verify, thanks.
tbxn said:
Yes, I have taken a look at the steps to capture the link and they seem simple enoughto just use adb logcat while the ota downloads. But I just want to clarify beforehand... When I use LGUP to partition dl back to nougat I think I should be selecting all partitions, but when I go from nougat to oreo should I be using partition dl again and selecting all partitions once again? Just want to verify, thanks.
Click to expand...
Click to collapse
I had suggested the Upgrade mode for going from Nougat to Oreo, but you can do Partition DL too. In fact, that may be best since you're going straight from 10d to 20s. Yes, all partitions.
@ChazzMatt: You sometimes warn about going straight up to the latest Oreo. Any thoughts here? Particularly coming from Pie in the first place?
TheDannemand said:
I had suggested the Upgrade mode for going from Nougat to Oreo, but you can do Partition DL too. In fact, that may be best since you're going straight from 10d to 20s. Yes, all partitions.
@ChazzMatt: You sometimes warn about going straight up to the latest Oreo. Any thoughts here? Particularly coming from Pie in the first place?
Click to expand...
Click to collapse
OK, so I flashed the stock phone and got to the point of running logcat. Nothing showed up in the logcat so I used the Take Bug Report method. I found two different ota file urls in the log. One of them was repeated more often so I think that is the correct one. However, I am unsure as to how I should proceed now. Do I need an .up file in order to use fota on the phone with no download mode? Did I perhaps grab the wrong zips? The zips appear to contain all the ota partition files. Trying to use the zip results in a "Windows cannot find WPDAPI.exe" error and an MTP is not running error. Granted this is the LGUP version that i just used to flash the stock phone successfully.
Moto G8 Play was a phone launched in October 2019 and that curiously had few (or none) mods created, and until today, February 2021, no one had managed to at least root this device, with guides that bricked the device(or made it bootloop), or at least did not work, where even with the boot.img patched, the magisk manager could not get root access on the device. Thinking about it and after losing many nights trying to do everything to root my phone, I finally got it, and decided to write this guide for you, with proof of operation and a lot of joy in having made such progress,
but enough with ceremonies, let's go to the guide in fact.
What do I need to do before read this guide?
First of all, backup all your data, you will surely lose it if you don't.
Second, keep in mind that I am not responsible for any errors or damage to the device, keep in mind that this is a mod guide that makes you lose the warranty on your device. What I did worked for me, and theoretically it works for you as long as you do everything correctly.
And lastly and most importantly, unlock the bootloader of your device, if you don't do this, it is possible to brick and transform it into a paper weight for lack of attention. Thinking about it, I wrote a quick guide to unlock bootloader, follow the steps:
1. Go to settings> System> About phone> Build Number and follow the image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Still in the settings, go to System> Advanced> Developer options and again follow the image:
3. On your computer, download platform-tools here and extract it to any folder you prefer. Also download and install Motorola USB drivers. After extracting and installing, open the platform-tools folder and copy the folder path, then open windows command prompt(cmd) and type the following commands:
in cmd, type cd and paste the path you copied, and hit enter. After that, type "adb devices" with your USB connected device(Remember to authorize USB debugging when connecting your device to the PC), if you did everything right, you will see something like this:
then type "adb reboot bootloader" to reboot your device for the correct mode. Once in bootloader mode, do not close cmd, it will still be useful. Access the motorola bootloader unlock site and follow the instructions provided. If you did everything right, your bootloader will appear with the status of flashing unlocked on the screen.
Ah, I talked about backup at the beginning, right? I'm glad you did the backup, because you just had your phone reset and data deleted. Now that you've installed everything right, let's start the hybridization process of your smartphone ... Let's install the Motorola One Macro ROM, which is basically the same thing as Moto G8 Play, but with more RAM, storage and 64- bit enabled, following this, download the One Macro Stock ROM here and extract it to the same folder as platform-tools:
It will look more or less like the photo above. After that, you will need a script to transform flashfile.xml into an appropriate flashfile.bat, and you can download this script here. Extract the .exe in the same folder as the platform-tools and the one macro rom, after this run and it will generate a flashfile.bat file. If your device is connected to the usb in bootloader mode you can now run the .bat and flash the rom on your device. Always remember to leave the battery with more than 50% charge to avoid problems and brick the device. If you did everything right, your device will start up normally. Configure, then go to settings and activate debugging following the steps at the beginning of the guide. You can notice that virtually your device is now a Motorola One Macro with the hardware of a Moto G8 Play, done that, let's go to the root process.
Copy the boot.img file from the platform-tools folder to any folder on your android. After that, install the magisk manager on the official website and open the app. In the magisk tab, click install and then "Select and Patch a file", select the boot.img file, after that make the selection process again, click the arrow and wait for magisk to finish the patch. After that, open google files and copy magisk_patched_XXXXX.img to your phone's root folder, and copy it to your computer again, in the platform-tools folder. Preferably rename it to an easier name, like magisk.img.
Do the process of opening cmd and pasting the folder path with the command "cd" before it. Then restart to bootloader mode as you learned above, and enter the command "fastboot flash boot_a magisk.img"
after finishing the process, type "fastboot flash boot_b magisk.img" and restart your device. If all goes well the magisk manager will detect the root and your phone will be ready.
This is the guide, I hope I have helped everyone who has gone so long without being able to root their devices. I wasted a night testing and writing this, so please consider giving feedback and if you post as a tutorial, leave the method credits to Daniel Santos (me).
Not works, when i flash the rom and the device restart, it give a message that is corrupt
CÆSAR said:
Not works, when i flash the rom and the device restart, it give a message that is corrupt
Click to expand...
Click to collapse
Did you unlock the bootloader correctly? If so, which version of Macro One did you use? If you want, I can pass the exact same version that I installed here and it works perfectly
Yes, i've already unlocked the bootloader and runned a comand in adb to check it, and used the last rom available. One question, installing the one macro firmware can damage the device? Because a 64 bit OS need more resources than the 32 bit software from the g8 play.
CÆSAR said:
Yes, i've already unlocked the bootloader and runned a comand in adb to check it, and used the last rom available. One question, installing the one macro firmware can damage the device? Because a 64 bit OS need more resources than the 32 bit software from the g8 play.
Click to expand...
Click to collapse
well, i used the version of the image i sent and it works 100% normal. As for the system, Motorola One Macro and Moto G8 Play have the exact same architecture. They differ only from some sensors, RAM and internal storage. If you want more details of the process, you can send me a dm on twitter (@danadsees) and I can give you the necessary support. I've never tested with the latest version, which uses Android 10, but versions using Android 9 work normally
ok, i will try with that version, and a last question, you tried to play games after install that version?
FInnaly i tried with your version and it works, thx
Does the G8 Play work flawlessly with the One Macro Rom?
RandoMike said:
Does the G8 Play work flawlessly with the One Macro Rom?
Click to expand...
Click to collapse
I think so. I didn't test it in depth, but in games performance looks to be better, and it worked normally in this few days that i've using it.
CÆSAR said:
I think so. I didn't test it in depth, but in games performance looks to be better, and it worked normally in this few days that i've using it.
Click to expand...
Click to collapse
That's curious. I'm gonna try to root my phone. I hope not to brick it haha.
RandoMike said:
That's curious. I'm gonna try to root my phone. I hope no to brick it haha.
Click to expand...
Click to collapse
I ended hard bricking my device . However, I managed to repair it . I dunno what could go wrong xd. I hope this tutorial would make this forum alive again xdxd.
RandoMike said:
I ended hard bricking my device . However, I managed to repair it . I dunno what could go wrong xd. I hope this tutorial would make this forum alive again xdxd.
Click to expand...
Click to collapse
This is my third update. It worked! I can't really believe it!
I would tell all the people who want to do this to be careful. You can hard brick your cellphone, specially if you flash the preloader.bin image. Being that said, thank you, Daniel. Finally I found a tutorial that works haha!
RandoMike said:
This is my third update. It worked! I can't really believe it!
I would tell all the people who want to do this to be careful. You can hard brick your cellphone, specially if you flash the preloader.bin image. Being that said, thank you, Daniel. Finally I found a tutorial that works haha!
Click to expand...
Click to collapse
thank you for your trust. I missed many nights looking for a valid method and I had to develop it myself. this also makes it possible to use custom roms and recoveries from Macro One as well
Daniel69cc said:
thank you for your trust. I missed many nights looking for a valid method and I had to develop it myself. this also makes it possible to use custom roms and recoveries from Macro One as well
Click to expand...
Click to collapse
Finally, there is some hope to revive this forum hahaha
Someone tryed with the android 10 version?
CÆSAR said:
Someone tryed with the android 10 version?
Click to expand...
Click to collapse
In my case, my cellphone just bootlooped. I think I also have to upgrade the fastboot, but I'm afraid it'll just make the phone hard brick. Or maybe I just need to try other Android 10 versions haha.
RandoMike said:
In my case, my cellphone just bootlooped. I think I also have to upgrade the fastboot, but I'm afraid it'll just make the phone hard brick. Or maybe I just need to try other Android 10 versions haha.
Click to expand...
Click to collapse
First update: I tried to restore the stock firmware of my Moto and it hard bricked (what a surprise, huh xD). I had to flash the original fastboot doing some stuff. Maybe we can upgrade to Android 10 doing that hardbrick trick (however, if you are not lucky, you can render the device unbootable), which allows you to reflash either the G8 Play's fastboot or the Macro one (it's weird that the fastboot of the One Macro also works on the G8 Play hahaha).
Second update: The One Macro Rom of Android 10 can't be flashed. It just gives me the error "sparse image size span overflow". I just proceeded to reflash the original Android 10 firmware of the G8 Play (I didn't wanna hardbrick it hahaha). It would be wonderful if anyone managed to solve or try to solve this problem.
Third update: I managed to root my G8 Play with its Stock Android 10 image! hahaha. I just flashed the "boot_a" slot with the original boot.img patched by magisk.
RandoMike said:
First update: I tried to restore the stock firmware of my Moto and it hard bricked (what a surprise, huh xD). I had to flash the original fastboot doing some stuff. Maybe we can upgrade to Android 10 doing that hardbrick trick (however, if you are not lucky, you can render the device unbootable), which allows you to reflash either the G8 Play's fastboot or the Macro one (it's weird that the fastboot of the One Macro also works on the G8 Play hahaha).
Second update: The One Macro Rom of Android 10 can't be flashed. It just gives me the error "sparse image size span overflow". I just proceeded to reflash the original Android 10 firmware of the G8 Play (I didn't wanna hardbrick it hahaha). It would be wonderful if anyone managed to solve or try to solve this problem.
Third update: I managed to root my G8 Play with its Stock Android 10 image! hahaha. I just flashed the "boot_a" slot with the original boot.img patched by magisk.
Click to expand...
Click to collapse
the root really works with the g8 play android 10 rom? i'm going to try
CÆSAR said:
the root really works with the g8 play android 10 rom? i'm going to try
Click to expand...
Click to collapse
Yep. I believed I would just get the "no bootable a/b slot" error, but it worked!
This guide is for moto g8 play or moto one macro or both ?
Hi again
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE! (if you do it right I doubt you will but just in case) BACK UP YOUR STUFF JUST IN CASE BEFORE YOU DO THIS AS YOU WILL WIPE YOUR USERDATA!
We now have access to RETUS Android 11!
Download this (retus android 11 firmware)
unzip all files to one folder somewhere
Code:
adb reboot bootloader
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
Code:
fastboot reboot fastboot
(reboots into fastbootd)
if you have twrp installed you should enter fastbootd and first things first flash stock recovery and reboot to it to continue flashing fastbootd commands doing something like this:
Code:
fastboot flash recovery recovery.img
fastboot reboot bootloader
fastboot reboot fastboot
YOU SHOULD BE IN FASTBOOTD TO FLASH THE STUFF IN THIS NEXT SECTION
Code:
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot reboot bootloader
YOU SHOULD NOW BE BACK IN BOOTLOADER TO ISSUE THESE NEXT COMMANDS
Code:
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
And then use TWRP or magisk boot patching to root your device and enjoy Android 11!
You forgot to include the bootloader in your flashing instructions. I couldn't get this to boot, finally realizing that I forgot to flash the bootloader as I was just following your list. Boots now though and I am using the retus.
I didn't flash bootloader on mine and it booted just fine. I didn't want to take more risk than I already did flashing bootloader and having something go sideways or permanently changed. I deliberately left it out of the flashing instructions but if it worked for you that's good.
I feel like my Bluetooth audio might not be going so hot after this, maybe just my radio in the truck though. Any Bluetooth problems for you yet?
Thanks for your feedback though and a good reference for anyone that needs it.
Did you try out my twrp build?
whoshotjr2006 said:
I didn't flash bootloader on mine and it booted just fine. I didn't want to take more risk than I already did flashing bootloader and having something go sideways or permanently changed. I deliberately left it out of the flashing instructions but if it worked for you that's good.
Thanks for your feedback though and a good reference for anyone that needs it.
Did you try out my twrp build?
Click to expand...
Click to collapse
Yes I did and so far so good. TOUCH WORKS!! Nicely done sir!
Do you need to be unlocked for this to work?
I'm having an audio issue where when someone answers a call, I cannot hear the person on the other end, even after turning call volume all the way up. I never had this with android 10.
Maybe a bad setting perhaps, but I don't know what that setting is...
Has anyone had this happen with this retca build?
thebestofall007 said:
I'm having an audio issue where when someone answers a call, I cannot hear the person on the other end, even after turning call volume all the way up. I never had this with android 10.
Maybe a bad setting perhaps, but I don't know what that setting is...
Has anyone had this happen with this retca build?
Click to expand...
Click to collapse
knowing phones in general, but one-way audio is often caused by bad VoLTE on a network.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But beyond that you may have to re-flash your radio perhaps if it didn't do it right.
Onoitsu2 said:
knowing phones in general, but one-way audio is often caused by bad VoLTE on a network. View attachment 5454283
But beyond that you may have to re-flash your radio perhaps if it didn't do it right.
Click to expand...
Click to collapse
I think I had the one way audio problem after I restored my retca setup with twrp. Retca itself doesn't seem to have this problem after I do a fresh reflash of it to my phone. Retca also doesn't have that voLTE option you show in the screenshot.
This could be TWRP not restoring something, like the radio, properly.
Edited again, removed the question I had since I found the answers after some research
A little off topic but also related to this topic:
By any chance does anyone have the file for RETUS? I would like to revert back to RETUS just because with RECTA, while it works as it should when it comes to normal usage and such, it also makes some apps in my phone not be "compatible" with other apps just because the main apps (Netflix and Hulu for example) are a U.S thing. For some reason cannot be downloaded on RECTA via the Play Store. I could just download apks and call it a day but having the RETUS rom file would help just guarantee that I could download most apps I use without apk file installations. Dummy me backed up everything RETUS related for the bootloader, recovery, and so on but never backed up the rom itself or somehow lost 500 braincells and deleted the thing. (Pov: Don't be a idiot like me, always double and even take the further step of triple checking that you got everything backed up before flashing regardless of it were to work fine or not.)
I would appreciate it if someone could send me it if they have access to it.
Thanks in advanced!
4xc7xy said:
A little off topic but also related to this topic:
By any chance does anyone have the file for RETUS? I would like to revert back to RETUS just because with RECTA, while it works as it should when it comes to normal usage and such, it also makes some apps in my phone not be "compatible" with other apps just because the main apps (Netflix and Hulu for example) are a U.S thing. For some reason cannot be downloaded on RECTA via the Play Store. I could just download apks and call it a day but having the RETUS rom file would help just guarantee that I could download most apps I use without apk file installations. Dummy me backed up everything RETUS related for the bootloader, recovery, and so on but never backed up the rom itself or somehow lost 500 braincells and deleted the thing. (Pov: Don't be a idiot like me, always double and even take the further step of triple checking that you got everything backed up before flashing regardless of it were to work fine or not.)
I would appreciate it if someone could send me it if they have access to it.
Thanks in advanced!
Click to expand...
Click to collapse
You should be able to find it here:
Moto Updates Tracker
An automated channel that tracks Motorola updates releases. By @vachounet and @yshalsager https://mirrors.lolinet.com/firmware/motorola More automated channels that you may like: @yshalsager_projects
t.me
can anyone grab the update they recently pushed to this firmware? I have it on my unlocked US power 2021 ill just sideload it in recovery
nvm it just released today for US
Konner920 said:
can anyone grab the update they recently pushed to this firmware? I have it on my unlocked US power 2021 ill just sideload it in recovery
nvm it just released today for US
Click to expand...
Click to collapse
I keep getting "access denied" when I try to download this from moto updates tracker.
updated op to reflect retus a11 release
Since i flashed the RECTA file when the steps where here awhile ago on my RETUS device, do I have to do all these steps to boot right back into RETUS or no?
Wondering because all I really did (anyone is free to call me an idiot lol) is just test if it booted, patched the img with magisk, tested it again to see if it would have root on it, and then flash it because it had the root lmao.
4xc7xy said:
Since i flashed the RECTA file when the steps where here awhile ago on my RETUS device, do I have to do all these steps to boot right back into RETUS or no?
Wondering because all I really did (anyone is free to call me an idiot lol) is just test if it booted, patched the img with magisk, tested it again to see if it would have root on it, and then flash it because it had the root lmao.
Click to expand...
Click to collapse
Your not an idiot bud, tinkering is a good thing. Everything is a good learning experience
You can stay with retca or flash over to retus, i figured since we actually have our own firmware files now its probably a good thing to be on retus firmware again. Whichever works for you.
Just make sure you back up all your stuff so you dont lose it, between all the crazy flashing stuff ive done tinkering with this device (rom builds and gsis) ive got my restore process down to about 30 mins now to get it back to how i like using it
If you stay on retca you may be able to use a magisk module to change your build.prop to have it think its on the retus version so you can download netflix and such from play store with no issues. I havent tried it but its worth a shot if you dont want to back up and restore again
whoshotjr2006 said:
Your not an idiot bud, tinkering is a good thing. Everything is a good learning experience
Just make sure you back up all your stuff so you dont lose it, between all the crazy flashing stuff ive done tinkering with this device (rom builds and gsis) ive got my restore process down to about 30 mins now to get it back to how i like using it
If you stay on retca you may be able to use a magisk module to change your build.prop to have it think its on the retus version so you can download netflix and such from play store with no issues. I havent tried it but its worth a shot if you dont want to back up and restore again
Click to expand...
Click to collapse
Totally agree with that view, cause I know I tested mine in exactly the same way, it boots, cool. I flashed stock recovery, booted into it, to make sure I had 100% recovery potential, then flashed the test recovery, and went from there. That's 100% how we have to muddle through learning and risking things on devices.
I think my process is down to like 10-mins because I can just restore data partition from a backup. But also have the migrate-ng app backup as well I can utilize too as a "live" backup too (https://forum.xda-developers.com/t/...20-migrate-custom-rom-migration-tool.3862763/).
And yes for this Magisk module, you want to use MagiskHide Props Config, or similar modules for that exact task, then hop into terminal to set it up once installed, and it's easy to alter many things. That's how I forced mine to be landscape as the "watch" it is, among other system tweaks.
I installed the magiskHide props config and a terminal to edit it from my phone, all I have to do to trick my device into being a RETUS is editing the fingerprints, etc. I also took screenshots from a build.prop editor app to question if they're the ones I got to edit to RETUS id's, I'll attach them with this. Sorry for asking so many questions, I'm just still new at tinkering with android phones and such still.
Is there any way to use this zip to update a stock system without twrp? Thank you for any response.
mindmajick said:
Is there any way to use this zip to update a stock system without twrp? Thank you for any response.
Click to expand...
Click to collapse
That is rather impossible, but this zip also is not flashable via twrp, so you may want to hold off on doing anything to your device until you research the process properly.