So, I picked up a used G710VM 64GB Storage/4GB RAM, I specifically wanted this model because I'm on Verizon and wanted to ensure that my phone would work with their wack-as-all-hell network. Upon booting it up on the stock firmware for the first time, and intentionally not putting in my SIM, nor getting it online, I saw it using up 16 GBs of storage right out of the gate, and about 2.8 or so GBs of RAM. I thought this unacceptable, and so began my journey of putting custom ROM on it.
I was looking at putting either Lineage OS or AOSP, but both guides require getting TWRP on there first, and that has been my hang-up.
I followed this guide on getting the bootloader unlocked, and got that done.
Now my problem is fastboot mode, with the bootloader unlocked, and on the G710ULM11g firmware, I can get into it just fine. But on the G710EM20b, G710EM20d, and G710ULM20d firmwares I follow the steps to get into fastboot mode, get a warning about the bootloader being unlocked, and then it just does a proper boot up into the OS, every. single. time. And I've gone back and forth between my 8.0 and 9.0 versions of Android a few times, and confirmed it's only the 9.0 ones that are giving me this issue, the 8.0 one lets me in without fail.
Did I unlock the bootloader wrong? Or am I just using the wrong firmware? Has anyone else had luck with a G710VM version of the phone? Or did I hose myself by not buying a ULM or EM version?
Out of appreciation for all the work that everyone in this community does (I read lots but don't post often) I would say, you need to search and skim through at least an hour worth of posts to find that answer, but I'll link it here to say thanks. Short answer- PIE loses Fastboot commands. You can flash to Oreo, and then you should be able to use fastboot commands. I still haven't found a posted method for installing TWRP. I just acquired an 'unlocked' Sprint model with the ULM firmware and would love to explore rom options.
https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
In the same guide post if you look on page 6 you will find how people have updated to pie retaining fastboot.
It can also be used to use a pie vm rooted stock rom also.
MaitiuD2 said:
Out of appreciation for all the work that everyone in this community does (I read lots but don't post often) I would say, you need to search and skim through at least an hour worth of posts to find that answer, but I'll link it here to say thanks. Short answer- PIE loses Fastboot commands. You can flash to Oreo, and then you should be able to use fastboot commands. I still haven't found a posted method for installing TWRP. I just acquired an 'unlocked' Sprint model with the ULM firmware and would love to explore rom options.
https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
Click to expand...
Click to collapse
Thank you very much for responding.
And that really sucks about fastboot and Pie, now I have to wonder how LameMonster82 did it in his guide . Someone else there tried installing that TWRP from Oreo, and got his phone bricked for it.
Halogen_03 said:
So, I picked up a used G710VM 64GB Storage/4GB RAM, I specifically wanted this model because I'm on Verizon and wanted to ensure that my phone would work with their wack-as-all-hell network. Upon booting it up on the stock firmware for the first time, and intentionally not putting in my SIM, nor getting it online, I saw it using up 16 GBs of storage right out of the gate, and about 2.8 or so GBs of RAM. I thought this unacceptable, and so began my journey of putting custom ROM on it.
I was looking at putting either Lineage OS or AOSP, but both guides require getting TWRP on there first, and that has been my hang-up.
I followed this guide on getting the bootloader unlocked, and got that done.
Now my problem is fastboot mode, with the bootloader unlocked, and on the G710ULM11g firmware, I can get into it just fine. But on the G710EM20b, G710EM20d, and G710ULM20d firmwares I follow the steps to get into fastboot mode, get a warning about the bootloader being unlocked, and then it just does a proper boot up into the OS, every. single. time. And I've gone back and forth between my 8.0 and 9.0 versions of Android a few times, and confirmed it's only the 9.0 ones that are giving me this issue, the 8.0 one lets me in without fail.
Did I unlock the bootloader wrong? Or am I just using the wrong firmware? Has anyone else had luck with a G710VM version of the phone? Or did I hose myself by not buying a ULM or EM version?
Click to expand...
Click to collapse
Weird, I'm using G710EM20d firmware on my G710ULM and it boots to fastboot.
"Weird, I'm using G710EM20d firmware on my G710ULM and it boots to fastboot."
-----------------------------------------------------------------------------------------
I have the ULM model as well but the G710EM20d Model doesnt boot to fastboot. Could you tell me the KDZ file you used?
Example, "G710EM10b_00_0521.kdz"
I'd really appreciate the help
u should cross flash the ulm firmware by lg up and then boot ur device in to the download mode after erase laf partition
Related
Due to a series of unfortunate events(user error), I just purchased my third ZenFone 2. Each time I have purchased the same model Z3560, simply with different color and capacity just due to the pricing at each time. I just received the third one and I have found some oddities with it that I just want to share or ask about. I noticed on the gsmarena page that it says that the Z3560 is supposed to have 2GB of RAM but mine has 4GB. Also as I would usually do with a new phone, I went to update it but there is no update button where it was on the previous two ZenFone 2s I have owned, I simply cannot work out where to update this phone. Any ideas as to how to do that? I'm on build number ASUS_Z00A-2.18.40.12_20150529. Finally, when looking in CPU-Z to see the hardware it was reporting I noticed it said I already had root access which is odd? This has literally just been opened in the last 30 minutes and does not seem to be tampered with or a preowned model as the box was still in the shrink wrap plastic packaging that the box comes in. This isn't an issue, I just find it odd as I had to root my previous devices, zenfones included.
Z3560 with 4GB of ram comes from China wit China software,sellers in other countries changing it to EU ROM which is pre rooted,it was with mine but before I bought it seller has info in advertisements about it,I do not have any errors yet and I hope I won't get but I have problem with overheating it is warm on the top of the phone...
Did you stay on the rom that yours came with? Do you know if I am still able to flash other WW firmware onto this? I would like to be on the latest update for my device and this doesn't give me the option so I'm missing out on some of the newer features that I'm used to like disabling the bloat on the device
SnakeBiteScares said:
Did you stay on the rom that yours came with? Do you know if I am still able to flash other WW firmware onto this? I would like to be on the latest update for my device and this doesn't give me the option so I'm missing out on some of the newer features that I'm used to like disabling the bloat on the device
Click to expand...
Click to collapse
I have a 32gb 4gb 3560 zenfone 2, 2 actually. I followed the change to ww from cn guide to make sure everything was ok and have no issue with getting OTA's...
Everything works fine and one is on the latest stock 165 rom, the other is on a custom rom. Both had bootloader unlocked and both are rooted.
If you wish to find the latest pre-rooted rom, go to the pre-rooted rom thread made by Shakalaka, thanks again, and download from there, the latest is on Mega however.... Flash using fastboot...
He also provides recovery, boot and droidboot images,again, flash using fastboot BUT make sure you don't just copy and paste the same thing repeatedly, flashing the system image on the recovery partition after flashing the boot and droidboot image there already can really bork your phone...
Would suggest unlocking bootloader, seems to be easier flashing new roms and no issue with OTA's either. Bit more flexible if things go screwy...
ultramag69 said:
I have a 32gb 4gb 3560 zenfone 2, 2 actually. I followed the change to ww from cn guide to make sure everything was ok and have no issue with getting OTA's...
Everything works fine and one is on the latest stock 165 rom, the other is on a custom rom. Both had bootloader unlocked and both are rooted.
If you wish to find the latest pre-rooted rom, go to the pre-rooted rom thread made by Shakalaka, thanks again, and download from there, the latest is on Mega however.... Flash using fastboot...
He also provides recovery, boot and droidboot images,again, flash using fastboot BUT make sure you don't just copy and paste the same thing repeatedly, flashing the system image on the recovery partition after flashing the boot and droidboot image there already can really bork your phone...
Would suggest unlocking bootloader, seems to be easier flashing new roms and no issue with OTA's either. Bit more flexible if things go screwy...
Click to expand...
Click to collapse
Thanks, I'll unlock the bootloader and flash the latest preroot WW rom
I know its bootloader is locked, but what happens if I try to flash trough fastboot? I mean, in the black kinda console screen after you press Power button + Vol Down button.
ADB interface recognize this, but I'm pretty afraid to make my Moto Z a hard dead block. So, have anyone did this?
Just in case, I want to do exactly this https://www.youtube.com/watch?v=d_YO__aYM7M&t=448s but on my Droid version, the tutorial is on spanish but I know you will understand the video
rusa-raus said:
Just in case, I want to do exactly this https://www.youtube.com/watch?v=d_YO__aYM7M&t=448s but on my Droid version, the tutorial is on spanish but I know you will understand the video
Click to expand...
Click to collapse
So if I've understood you correctly, you're looking to flash Android Oreo onto your device via fastboot?
With a locked bootloader, it's pretty difficult to hard brick your device whilst flashing, just be careful that you have a stable power supply (both to your computer and to your device, and that you have plenty of time). With a locked bootloader, you can only flash the same or newer firmware than you currently have on your device, the bootloader will otherwise block you from flashing older firmwares.
That being said, you'd need the Verizon stock ROMs to flash on a Droid if I recall correctly. The retail Oreo stock ROM we have here may not work and your locked bootloader may force you to flash only Verizon firmwares, so your best bet may be to either wait for the Verizon Oreo OTA, find the Verizon OTA on XDA or hope that someone uploads the Verizon Oreo firmware.
echo92 said:
So if I've understood you correctly, you're looking to flash Android Oreo onto your device via fastboot?
With a locked bootloader, it's pretty difficult to hard brick your device whilst flashing, just be careful that you have a stable power supply (both to your computer and to your device, and that you have plenty of time). With a locked bootloader, you can only flash the same or newer firmware than you currently have on your device, the bootloader will otherwise block you from flashing older firmwares.
That being said, you'd need the Verizon stock ROMs to flash on a Droid if I recall correctly. The retail Oreo stock ROM we have here may not work and your locked bootloader may force you to flash only Verizon firmwares, so your best bet may be to either wait for the Verizon Oreo OTA, find the Verizon OTA on XDA or hope that someone uploads the Verizon Oreo firmware.
Click to expand...
Click to collapse
Understood, seems like Verizon is not gonna update Moto Z Play...
So I've just recovered my phone from my 1st attempt at updating to Pie on my unlocked AT&T v35.
But I'm left wondering if the process for updating from Oreo to Pie is somehow different than when I successfully updated from Marshmallow to Oreo.
The process I thought was:
1. Put phone in download mode
2. Connect phone to pc
3. Run the Modified version of LGUP
4. Select your ULM KDZ choice (any of the three will do)
5. Select Upgrade
6. Flash phone
Are any of these steps incorrect and should step 5 be Refurbish instead of Upgrade?
X-Nemesis said:
So I've just recovered my phone from my 1st attempt at updating to Pie on my unlocked AT&T v35.
But I'm left wondering if the process for updating from Oreo to Pie is somehow different than when I successfully updated from Marshmallow to Oreo.
The process I thought was:
1. Put phone in download mode
2. Connect phone to pc
3. Run the Modified version of LGUP
4. Select your ULM KDZ choice (any of the three will do)
5. Select Upgrade
6. Flash phone
Are any of these steps incorrect and should step 5 be Refurbish instead of Upgrade?
Click to expand...
Click to collapse
I used upgrade, when going from ULM 8.0 to ULM 9.0. I would assume you would use refurbish if going from stock to another firmware. Of course assumptions aren't really reliable.
I've been trying to figure out if I should do UPGRADE or REFURBISH as well.
I found this: https://forum.xda-developers.com/lg-v30/how-to/guide-how-to-upgrade-downgrade-restore-t3738917
Says REFURBISH wipes user data, UPGRADE does not. If moving from one image say from AT&T, to the Unlocked firmware I'd assume you want REFURBISH.
So since I used refurbish to go to the ulm software from 7 to 8, do I still need to refurbish going to any of the ulm pie variants?
Shawnashley said:
I used upgrade, when going from ULM 8.0 to ULM 9.0. I would assume you would use refurbish if going from stock to another firmware. Of course assumptions aren't really reliable.
Click to expand...
Click to collapse
That's what threw me for a loop on my first attempt. Since I'd successfully upgrade from the AT&T 7.0 firmware to I believe the Amazon 8.0 ULM firmware without issues, I thought the process would be the same going to 9.0. But I ran the upgrade through LGUP which was the modified version, and it crashed at 74% and sent me down a wonderful rabbits hole of brickage.
X-Nemesis said:
So I've just recovered my phone from my 1st attempt at updating to Pie on my unlocked AT&T v35.
But I'm left wondering if the process for updating from Oreo to Pie is somehow different than when I successfully updated from Marshmallow to Oreo.
The process I thought was:
1. Put phone in download mode
2. Connect phone to pc
3. Run the Modified version of LGUP
4. Select your ULM KDZ choice (any of the three will do)
5. Select Upgrade
6. Flash phone
Are any of these steps incorrect and should step 5 be Refurbish instead of Upgrade?
Click to expand...
Click to collapse
I don't understand how were you on Marshmallow before flashing to Oreo. I'm pretty sure the the V35 launched on Oreo 8.0. But I'm also looking for a way to get from Oreo to Pie on ULM kdz.
I went from AWM12k to ULM10i choosing REFURB and all went well (I followed xatokk's post on the lgV35 subreddit).
When I try to get from ULM10i to ULM20d (Pie .kdz) I guess I only have to drag ULM20d kdz in LGUP window?
I just want to make sure that's not how you bricked your phone before I try REFURB from ULM10i to ULM20d
Any advice would help, I'm a noob at this.
FWIW, partition DL worked fine going first from AT&T firmware to Oreo ULM and then again to Pie. Sadly I had to set up the phone again.
Neophy said:
I don't understand how were you on Marshmallow before flashing to Oreo. I'm pretty sure the the V35 launched on Oreo 8.0. But I'm also looking for a way to get from Oreo to Pie on ULM kdz
Click to expand...
Click to collapse
Sorry, Brainfart, I was completely out to lunch on that. I wanted to flash the latest available security update, but since I'm in Canada I could never get that from AT&T so I had to find a way to flash it and that led me to XDA and the whole LGUP process. So you were correct on that, and I did flash the Amazon 8.0 KDZ I believe without issue.
My brick happened when using the Amazon pie KDZ and using the same Upgrade process in LGUP. The update got to 74% and then crashed. I then tried to run the refurbish option but that crashed as well so by that time, my phone was beyond my knowledge of how to fix it
cmrntnnr said:
FWIW, partition DL worked fine going first from AT&T firmware to Oreo ULM and then again to Pie. Sadly I had to set up the phone again.
Click to expand...
Click to collapse
Partition DL was not available in the process list of the modded version of LGUP I used. Which one did you use? I think I found the right one.
Now, selecting PARTITION DL, do I need to select all like mentioned in the Frankenstein Phone thread for the V30?
Neophy said:
I don't understand how were you on Marshmallow before flashing to Oreo.
Click to expand...
Click to collapse
This phone launched with Oreo and had nothing prior. He's mistaken, confusing some other model.
That's what I did.
The error you experience may be due to a usb cable. a particular usb port on your computer, other software on your computer, and maybe bios settings. The v30 WTF and Frankenphone forums would be good places for background and solutions.
Fingers crossed for a successful flash.
Neophy said:
Partition DL was not available in the process list of the modded version of LGUP I used. Which one did you use? I think I found the right one.
Now, selecting PARTITION DL, do I need to select all like mentioned in the Frankenstein Phone thread for the V30?
Click to expand...
Click to collapse
Here's what I did if you don't already found a way. I also faced an error trying to flash to Pie ULM.kdz.
I don't know why but LGUP for developer patched from 9to5lg.com didn't work for me. I tried PARTITION DL it crashed at 91% and I also had to reboot my PC. I kept the phone plugged and reinstalled LGUP.
My V35 was on AWM12k when I got it. I followed xatokk's post on the lgV35 subreddit to get it to to ULM10i choosing REFURB.
I kept the same .dll I extracted from to ULM10i and I did a REFURB to ULM20d .kdz just dragging it to LGUP.
I hope this can help you.
To update my earlier reply on this topic. Somehow flashing REFURBISH from AT&T stock Oreo to ULM(Unlocked) Pie it failed and bricked my phone. As mentioned in another thread regarding unlocking the bootloader and root, I had to call on @motogvasyag to not only unbrick my phone remotely but he also unlocked the bootloader and rooted it. If anyone has any issues with bricking you might want to contact him. He's fast and does amazing work. I only mention this because I am very appreciative of him and his work. I'm not sure why my flashing failed at around 70 something percent but I'm glad to have my phone working again along with the update to pie and root.
Truth
MorningStarGG said:
To update my earlier reply on this topic. Somehow flashing REFURBISH from AT&T stock Oreo to ULM(Unlocked) Pie it failed and bricked my phone. As mentioned in another thread regarding unlocking the bootloader and root, I had to call on @motogvasyag to not only unbrick my phone remotely but he also unlocked the bootloader and rooted it. If anyone has any issues with bricking you might want to contact him. He's fast and does amazing work. I only mention this because I am very appreciative of him and his work. I'm not sure why my flashing failed at around 70 something percent but I'm glad to have my phone working again along with the update to pie and root.
Click to expand...
Click to collapse
@motogvasyag unbricked my AT&T V35 that was stuck in fastboot from a failed flash. Took care of it right away. Phone is now factory LG on Google Fi, Pie, wifi calling and all three carriers. Highly recommended!
I have the LG G8 Thinq Sprint Model (LM-G820UMKIT) bought it pre-owned. I recently saw that there was a guide to unlock and root the LG G8 however the requirements is for the device to be on Android 10. I'm currently still on Android 9 and I am unable to update via software update, or through LG Suite. Is there anyway to update to A10?
Adelino80 said:
I have the LG G8 Thinq Sprint Model (LM-G820UMKIT) bought it pre-owned. I recently saw that there was a guide to unlock and root the LG G8 however the requirements is for the device to be on Android 10. I'm currently still on Android 9 and I am unable to update via software update, or through LG Suite. Is there anyway to update to A10?
Click to expand...
Click to collapse
It's unfortunate, but the guide is a bit misleading. I'd bet the person that wrote it had a specific version of android, and didn't know / want to indicate it would work on any other as they hadn't tested it.
But, there's virtually zero reason the unlock procedure shouldn't work on any version of android. The reason is very simple; all you do in that guide is use edl mode (any qualcomm device can do that), you flash the engineering abl to abl partition (it won't matter what version of android the rest of the system is), you go to fastboot (that's what the eng abl gives you), you unlock the boot-loader, you use fastboot to flash the original abl back.
Makes sense? See, you don't use that eng abl to boot the OS, you don't use it for anything at all, except to unlock the boot-loader. That's it. Period. There's no reason for it to not work no matters what version of android your system is.
As far as Sprint update goes... talk to sprint, ask them for help getting it updated. Sprint does not make their kdz available, if you don't get any OTA update from them, you'll then be faced with finding someone's partition backup, and all the complications involved / and danger, of flashing that.
The other option would be to crossflash to a rom that has a kdz. It too is involved and complicated, and potentially dangerous.
good luck
AsItLies said:
It's unfortunate, but the guide is a bit misleading. I'd bet the person that wrote it had a specific version of android, and didn't know / want to indicate it would work on any other as they hadn't tested it.
But, there's virtually zero reason the unlock procedure shouldn't work on any version of android. The reason is very simple; all you do in that guide is use edl mode (any qualcomm device can do that), you flash the engineering abl to abl partition (it won't matter what version of android the rest of the system is), you go to fastboot (that's what the eng abl gives you), you unlock the boot-loader, you use fastboot to flash the original abl back.
Makes sense? See, you don't use that eng abl to boot the OS, you don't use it for anything at all, except to unlock the boot-loader. That's it. Period. There's no reason for it to not work no matters what version of android your system is.
As far as Sprint update goes... talk to sprint, ask them for help getting it updated. Sprint does not make their kdz available, if you don't get any OTA update from them, you'll then be faced with finding someone's partition backup, and all the complications involved / and danger, of flashing that.
The other option would be to crossflash to a rom that has a kdz. It too is involved and complicated, and potentially dangerous.
good luck
Click to expand...
Click to collapse
Thanks for the advice! Yeah I wouldn't see why the device shouldn't be able to boot into EDL mode. I don't mind trying the unlock procedure with the guide, just sucks that there is no MSM tool to unbrick the device if anything does happen. As for updating to A10 I can live without, I only asked because the guide specified A10 as an requirement, which you already answered.
Adelino80 said:
Thanks for the advice! Yeah I wouldn't see why the device shouldn't be able to boot into EDL mode. I don't mind trying the unlock procedure with the guide, just sucks that there is no MSM tool to unbrick the device if anything does happen. As for updating to A10 I can live without, I only asked because the guide specified A10 as an requirement, which you already answered.
Click to expand...
Click to collapse
I would suggest that you look at the bkerler edl tools. Don't do anything until you backed up the device completely.
So I tried rooting my OnePlus 7T yesterday and first downgraded from android 12 to 10 (build number Oxygen OS 10.0.13.HD64BA), then tried to root it and I ended up getting a screen that said QUALCOM Crashdump Mode. After trying to search for an answer how to fix it, I tried to re-flash the phone with the stock rom, which I got from here taking the latest Europe version - https://forum.xda-developers.com/t/...t-stock-fastboot-roms-for-oneplus-7t.3979213/
I entered fastboot mode, and ran flash-all but when I watched a video on how to do it, I was taken to a different screen. I think I was maybe the advanced boot options screen (I had to pick a language then reboot to fastboot or recovery). After rebooting, I unlocked the phone and the wifi is now broken.
I saw a guide on here that said I had to do something about important partitions (not sure what that means), so I'm not sure I am correctly re-flashing the phone from the correct stock rom and can't find a thread that makes total sense to me. Any help would be great
MSM Tool
After restoring upgrade to the last OOS 11 (11.9.1 I think)
Then follow the links I gave you on your other thread .
Tomcar said:
MSM Tool
After restoring upgrade to the last OOS 11 (11.9.1 I think)
Then follow the links I gave you on your other thread .
Click to expand...
Click to collapse
Thanks for the help again.
I've downloaded the EU 10.0.13 MSM tools (as I downgraded my oneplus 7T to this) and it told me "device not match image"
What version of MSM do I need? I checked other links attached on similar forms and more often I only see an option for 7T for 10.0.03 or 10.0.15. I don't know what I'm doing wrong.
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.3994835/
One of them should fit.
Or, if only WiFi is broken, upgrade to 11.0.5.1. and use the MSM Tool for that.
What's you're phone? HD1903?
I think you've flashed the wrong Firmware like India on Europe or vice versa.
Ignore me, I got it to work using a different MSM version (10.0.15). Will go back and try follow your instructions to root as best I can