Help. I need to sell my H932 but the buyer is afraid of having root and not getting ota updates.
I was never too smart in regards to cell phones. But 2 weeks ago I had brain surgery and I'm even dumber now. I need steps written for a child. I have lgup but don't have a current .kdz. Its currently running H93220s.
Is Android 9 available ota?
Thanks in advance.
bsliv said:
Help. I need to sell my H932 but the buyer is afraid of having root and not getting ota updates.
I was never too smart in regards to cell phones. But 2 weeks ago I had brain surgery and I'm even dumber now. I need steps written for a child. I have lgup but don't have a current .kdz. Its currently running H93220s.
Is Android 9 available ota?
Thanks in advance.
Click to expand...
Click to collapse
Android 9 is not available yet for h932
Your other question someone else can answer. Don't know much about h932.
Thanks for the no 9 news. Oh well.
lg-firmware.com find H932SV then download kdz latest 20s, use correct lgup to flash it, reset phone.
immns said:
lg-firmware.com find H932SV then download kdz latest 20s, use correct lgup to flash it, reset phone.
Click to expand...
Click to collapse
Thanks. Downloading the .kdz right now.
I already have lgup installed. While trying to install this new lgup, I get the message, "Error 1316. The specified account already exists." I'm assuming I have this version installed but don't know for sure.
I may be wrong, but if you're on stock 20s you're on the most recent update from LG.
conbak49 said:
I may be wrong, but if you're on stock 20s you're on the most recent update from LG.
Click to expand...
Click to collapse
I'm on a rooted 20s. I want to be on an unrooted, any version.
The instructions on LG's website say to hold the volume up button and plug it into a pc. I do that and it boots in TWRP. Typing adb devices from a Windows command prompt shows the V30 and it being in recovery mode. But starting lgup, it says, "There is no handset connected. Please connect a handset."
If I use TWRP to boot into the system, adb devices doesn't show any handsets connected. LGUP does see it but doesn't see the new .kdz file. And the phone reboots about once a minute.
If I boot into TWRP and do a default Wipe, it doesn't reboot.
What did I do wrong?
bsliv said:
I'm on a rooted 20s. I want to be on an unrooted, any version.
The instructions on LG's website say to hold the volume up button and plug it into a pc. I do that and it boots in TWRP. Typing adb devices from a Windows command prompt shows the V30 and it being in recovery mode. But starting lgup, it says, "There is no handset connected. Please connect a handset."
If I use TWRP to boot into the system, adb devices doesn't show any handsets connected. LGUP does see it but doesn't see the new .kdz file. And the phone reboots about once a minute.
If I boot into TWRP and do a default Wipe, it doesn't reboot.
What did I do wrong?
Click to expand...
Click to collapse
Doing a default wipe eliminates the OS from your phone so you don't have an OS to boot into. If you want unrooted stock and are able to boot into TWRP, you should be able to to just flash the flashable 20s kdz for the H932 w/o Magisk and that will put you back on stock. See the thread with instructions. I believe if you flash w/o Magisk that will also eliminate your ability to get back to TWRP. To root again I believe you'd have to start all over again so choose carefully.
Actually, you'd have to use the flashable 20s Stock ZIP, not the KDZ, if you want to flash it with TWRP. But that wouldn't restore stock Recovery nor Download mode (laf). Thus the new owner wouldn't be able to update with OTA or LG Bridge.
The best way to ensure complete stock is to flash KDZ, as you tried. Since your Download mode seems to be gone, I would flash the laf ZIP file in TWRP. You can find it in the Stock H932 ZIP thread and in the H932 root thread.
After that, follow the exact steps in the H932 root guide to get into Download mode, then flash the 20s KDZ using LGUP Refurbish Mode.
To be truly stock (and avoid the warning screen during boot) you have to also lock the bootloader, but you can only do that once all partitions are completely stock, otherwise you could brick the phone.
TheDannemand said:
Actually, you'd have to use the flashable 20s Stock ZIP, not the KDZ, if you want to flash it with TWRP. But that wouldn't restore stock Recovery nor Download mode (laf). Thus the new owner wouldn't be able to update with OTA or LG Bridge.
The best way to ensure complete stock is to flash KDZ, as you tried. Since your Download mode seems to be gone, I would flash the laf ZIP file in TWRP. You can find it in the Stock H932 ZIP thread and in the H932 root thread.
After that, follow the exact steps in the H932 root guide to get into Download mode, then flash the 20s KDZ using LGUP Refurbish Mode.
To be truly stock (and avoid the warning screen during boot) you have to also lock the bootloader, but you can only do that once all partitions are completely stock, otherwise you could brick the phone.
Click to expand...
Click to collapse
When I hold volume up and plug the USB into my pc, it briefly says Download Mode then TWRP goes on the screen.
I can't get the 20s.kdz to install using LGUP.
I truly appreciate all the help but this may be beyond my capabilities. (Brain surgery sucks.)
bsliv said:
When I hold volume up and plug the USB into my pc, it briefly says Download Mode then TWRP goes on the screen.
I can't get the 20s.kdz to install using LGUP.
I truly appreciate all the help but this may be beyond my capabilities. (Brain surgery sucks.)
Click to expand...
Click to collapse
It's OK, people here want to help
Did you flash the laf ZIP in TWRP to fix your Download Mode? If not, that should be your first step. (If you end up losing TWRP too, it gets much more difficult.)
1. Download the StockLAF from this post by weakNPCdotCom's. Verify its MD5 to make sure it downloaded properly.
2. Transfer StockLAF.zip to you phone by whichever means (USB cable, SD card etc).
3. Boot into TWRP, either deliberately or by trying to get into Download Mode
4. Flash StockLAF.zip to restore your Download Mode.
5. Use TWRP to turn off the phone (I forget the exact command) and disconnect its cable.
6. Download and install LGUP from this post by runningnak3d. It's not the latest, but we know it works on H932.
7. Now try Download mode again: With the phone off, hold Vol Up, and plug in the USB cable that is connected to your PC.
8. If you manage to get into Download mode, launch LGUP and make sure it detects the phone.
9. Flash the H932 20s KDZ using LGUP Refurbish mode. Of course if you don't already have it, download it from lg-firmwares.com and verify its MD5.
10. Unplug cable and let phone reboot after LGUP (hopefully) completes flashing the KDZ.
11. Once (hopefully) in stock Oreo, tap Settings>General>About phone>Software info>Build number until Developer Options are enabled.
12. Enable Settings>General>Developer Options>Enable OEM unlock.
13. Turn phone off and unplug the cable.
14. With phone off, enter Fastboot mode by holding Vol Down and plugging in the USB cable. Plug into computer.
15. In ADB window, enter fastboot devices to verify ADB is working.
16. In ADB window, enter fastboot oem lock to re-lock the bootloader.
17. Use fastboot keys to reboot phone into OS.
18. Run Settings>General>Reset>Factory data reset. Do NOT use Master Reset (button dance) or the new user might trigger FRP/kill switch.
19. Done. Ship the phone to your buyer.
I'm insanely busy tonight, so afraid I won't be there for any follow-up questions. But anybody here should be able to help with those steps.
TheDannemand said:
It's OK, people here want to help
Did you flash the laf ZIP in TWRP to fix your Download Mode? If not, that should be your first step. (If you end up losing TWRP too, it gets much more difficult.)
1. Download the StockLAF from this post by weakNPCdotCom's. Verify its MD5 to make sure it downloaded properly.
2. Transfer StockLAF.zip to you phone by whichever means (USB cable, SD card etc).
3. Boot into TWRP, either deliberately or by trying to get into Download Mode
4. Flash StockLAF.zip to restore your Download Mode.
5. Use TWRP to turn off the phone (I forget the exact command) and disconnect its cable.
6. Download and install LGUP from this post by runningnak3d. It's not the latest, but we know it works on H932.
7. Now try Download mode again: With the phone off, hold Vol Up, and plug in the USB cable that is connected to your PC.
8. If you manage to get into Download mode, launch LGUP and make sure it detects the phone.
9. Flash the H932 20s KDZ using LGUP Refurbish mode. Of course if you don't already have it, download it from lg-firmwares.com and verify its MD5.
10. Unplug cable and let phone reboot after LGUP (hopefully) completes flashing the KDZ.
11. Once (hopefully) in stock Oreo, tap Settings>General>About phone>Software info>Build number until Developer Options are enabled.
12. Enable Settings>General>Developer Options>Enable OEM unlock.
13. Turn phone off and unplug the cable.
14. With phone off, enter Fastboot mode by holding Vol Down and plugging in the USB cable. Plug into computer.
15. In ADB window, enter fastboot devices to verify ADB is working.
16. In ADB window, enter fastboot oem lock to re-lock the bootloader.
17. Use fastboot keys to reboot phone into OS.
18. Run Settings>General>Reset>Factory data reset. Do NOT use Master Reset (button dance) or the new user might trigger FRP/kill switch.
19. Done. Ship the phone to your buyer.
I'm insanely busy tonight, so afraid I won't be there for any follow-up questions. But anybody here should be able to help with those steps.
Click to expand...
Click to collapse
Beautifully written. And it seamed to work!!! Thank you very much.
bsliv said:
Beautifully written. And it seamed to work!!! Thank you very much.
Click to expand...
Click to collapse
Awesome, glad to hear it. Good job :good:
Related
i tryed to root my phone everything was going alright, but wen i went to boot it up i got stuck on
ASUS IN SEARCH OF INCREDIBLE and a loading logo, i can not get in to my bootloader
my pc detects it but fast boot and adb do not detect it
what do i do :crying::crying::crying::crying:
FluidArc said:
i tryed to root my phone everything was going alright, but wen i went to boot it up i got stuck on
ASUS IN SEARCH OF INCREDIBLE and a loading logo, i can not get in to my bootloader
my pc detects it but fast boot and adb do not detect it
what do i do :crying::crying::crying::crying:
Click to expand...
Click to collapse
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
now what do i do
i do not know what ferwere i am on and my recovery is broken how to i get it up and runing
dh_711 said:
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
Click to expand...
Click to collapse
Once happened to my zf2, what i did is formatting cache from the adb then my device could be detected, thus i could enter the recovery mode
Sent from my ASUS_Z00AD using XDA Free mobile app
i can not enter recovery
dawnsleeper said:
Once happened to my zf2, what i did is formatting cache from the adb then my device could be detected, thus i could enter the recovery mode
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
it is fix all good guys thx
FluidArc said:
i can not enter recovery
Click to expand...
Click to collapse
Hey,
Could you please help me (or anyone for that matter).....I've soft bricked my phone and I'm a little weary about following any other steps incase I fully brick the phone.
I have a Zenfone 2 that was CN Z00A 2.20.40.63 , I tried to root because random chinese apps kept downloading on my phone and obv it soft bricked (kept looping at boot).....since then I have tried a lot of stuff without luck and my brain is fried from all the information.... I went to the recovery mode but ADP couldn't find my phone and then I loaded a recovery image on my SD calling it MOFD_SD.ZIP but that didn't work due to signature verification error. Now after reading what you wrote I can see that fastboot is recognizing my device....I would go through with the process but I'm afraid if I screw this one up it could be the end of fastboot working and therefore me being royally screwed.
Since my phone was naturally CN Z00A 2.20.40.63 I'm wondering if the pre-rooted images on the site you mentioned above will work? There is no download for CN Z00A 2.20.40.63 and I want to know whether it's safe to use CN Z00A 2.20.40.61 (or a WW image) or whether I have to try another option (if you have any suggestions).
If anyone could reply with help it would be greatly greatly appreciated.
dh_711 said:
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
Click to expand...
Click to collapse
Captain_Hindsight said:
Hey,
Could you please help me (or anyone for that matter).....I've soft bricked my phone and I'm a little weary about following any other steps incase I fully brick the phone.
I have a Zenfone 2 that was CN Z00A 2.20.40.63 , I tried to root because random chinese apps kept downloading on my phone and obv it soft bricked (kept looping at boot).....since then I have tried a lot of stuff without luck and my brain is fried from all the information.... I went to the recovery mode but ADP couldn't find my phone and then I loaded a recovery image on my SD calling it MOFD_SD.ZIP but that didn't work due to signature verification error. Now after reading what you wrote I can see that fastboot is recognizing my device....I would go through with the process but I'm afraid if I screw this one up it could be the end of fastboot working and therefore me being royally screwed.
Since my phone was naturally CN Z00A 2.20.40.63 I'm wondering if the pre-rooted images on the site you mentioned above will work? There is no download for CN Z00A 2.20.40.63 and I want to know whether it's safe to use CN Z00A 2.20.40.61 (or a WW image) or whether I have to try another option (if you have any suggestions).
If anyone could reply with help it would be greatly greatly appreciated.
Click to expand...
Click to collapse
Well, I'm not sure if it'll work but check this out (Scroll down to No. 4 - Changing from CN to WW version):
forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
I'm no expert, but to be honest the state your device is in, I don't see any other options. Because when my device (it had WW firmware) got soft-bricked, I followed the guide by androidsoul and it did recover my phone. Not sure about yours since its a CN one.
If you like living on the edge and are really desperate, go ahead try this out, if not, better wait for someone with more knowledge then me.
EDIT: I forgot but since ADB isn't working, you can't use this method. So the only option I see that you have is flashing a pre-rooted rom.
Hello everyone i tryed to search similar issues in the forum but i only found this thread without solution: http://forum.xda-developers.com/g4/help/h815-stuck-bootloop-download-mode-t3235362
My G4 stucks on boot loop and i cannot reach bootloader mode or recovery.
I updated to M then i decided to unlock the bootloader.
Then I try to install twrp. Via fastboot flash command twrp doesn't seem to get installed. So i try to boot in twrp and then install the img to the recovery partition. All seemed to go fine. When i try to reboot to recovery twrp ask me to root the device. Why not? I leave twrp installs superSu (I think this was my mistake). Now I've a continuous bootloop, even if I simply plug it to the charger. Vol down + Power buttons neither vol up + power doesn't work.
Sorry for bad english
Yep.. You shouldn't have selected the built in version..
Copy an updated SuperSU.zip file onto a spare SD Card and slot it into the Phone.
Reboot into TWRP and install the new SuperSU.zip from the SDCard..
Are you able to boot TWRP? Of yes, take Hostilians advice.
Are you unable to boot TWRP? Enter download mode ( unplug device-> hold down Volume + -> plug device) and install a fresh OS using LGUP.
eldriSs said:
Are you able to boot TWRP? Of yes, take Hostilians advice.
Are you unable to boot TWRP? Enter download mode ( unplug device-> hold down Volume + -> plug device) and install a fresh OS using LGUP.
Click to expand...
Click to collapse
Hi
I have same situation. After SuperSu zip installation my G4 stuck on boot loop. Can somebody explain a little bit this procedure? I don't know how install a fresh OS and don't know what is a LGUP.
I found another link over Internet but...I'm not sure: rootmygalaxy.net/unbrick-lg-g4-with-lg-flash-tool
I don't have any way to enter into TWRP because as I say G4 is stucked and adb command don't work.
Any help appreciated
rubendob said:
Hi
I have same situation. After SuperSu zip installation my G4 stuck on boot loop. Can somebody explain a little bit this procedure? I don't know how install a fresh OS and don't know what is a LGUP.
I found another link over Internet but...I'm not sure: rootmygalaxy.net/unbrick-lg-g4-with-lg-flash-tool
I don't have any way to enter into TWRP because as I say G4 is stucked and adb command don't work.
Any help appreciated
Click to expand...
Click to collapse
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Follow this instructions here... although it doesn't tell you how to use it with your device in download mode! Anyways... is very easy to do it.
First install LGUP_8994_DLL_Ver_0_0_3_23 them LGUP. Plug in your device (you will notice that it doesn`t recognize your device, no worries) Unplug device, shut down, hold Volume + and plug device. It will enter download mode. Now go to LGUP click upgrade and choose your .kdz. Easy.
Cheers!
eldriSs said:
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Follow this instructions here... although it doesn't tell you how to use it with your device in download mode! Anyways... is very easy to do it.
First install LGUP_8994_DLL_Ver_0_0_3_23 them LGUP. Plug in your device (you will notice that it doesn`t recognize your device, no worries) Unplug device, shut down, hold Volume + and plug device. It will enter download mode. Now go to LGUP click upgrade and choose your .kdz. Easy.
Cheers!
Click to expand...
Click to collapse
Hi
I didn't have to do it exactly this way. My phone was stucked in boot loader (black screen lg logo) and simply connected by usb to my windows. LGUP detected without extra actions and then I refurbished it with a kdz file.
Hope it helps someone
Thanks!
I just bought a brand new Nexus 7 16 GB wrapped in it's plastic unused. Charged it turned it on, as expected it's on 4.3.
Problem is when I check for updates it says the tablet is up to date and will not update to 6.0 which I believe is the latest this tab will go to.
Question is will this self correct if left on or will I need to manually update using OTA update from a PC. Also if I do need to manually update will I need to find and install every intervening update between 4.3 and 6.0?
It'll be easiest to use the factory image to flash it to 6.0.
If you go the OTA route you'd have to go through every update individually to get to 6.0.
fr4nk1yn said:
It'll be easiest to use the factory image to flash it to 6.0.
If you go the OTA route you'd have to go through every update individually to get to 6.0.
Click to expand...
Click to collapse
Thanks, Sorry to be a noob but how do I install a factory image?
telfish said:
Thanks, Sorry to be a noob but how do I install a factory image?
Click to expand...
Click to collapse
Download ADB from here and install: https://forum.xda-developers.com/showthread.php?t=2588979
Download the image, making sure you have the correct one. I'm assuming you have a Wi-Fi version so it would then be the "Razor": https://developers.google.com/android/images#razor
Boot into the bootloader by powering off, then holding the power and volume down buttons simultaneously.
Connect to your computer with the USB cable, open a CMD, or terminal, window and type fastboot oem unlock. That will wipe the device. I don't remember if it reboots automatically afterward. if so boot back into the bootloader the same as before.
Extract the system image. Open the extracted folder then if you're on Windows just double click the flash-all.bat file. after it's done it will ultimately reboot to Android.
-edit: If you're adventurous once in the bootloader you can flash TWRP and the Oreo Go ROM from here.
fr4nk1yn said:
Download ADB from here and install: https://forum.xda-developers.com/showthread.php?t=2588979
Download the image, making sure you have the correct one. I'm assuming you have a Wi-Fi version so it would then be the "Razor": https://developers.google.com/android/images#razor
Boot into the bootloader by powering off, then holding the power and volume down buttons simultaneously.
Connect to your computer with the USB cable, open a CMD, or terminal, window and type fastboot oem unlock. That will wipe the device. I don't remember if it reboots automatically afterward. if so boot back into the bootloader the same as before.
Extract the system image. Open the extracted folder then if you're on Windows just double click the flash-all.bat file. after it's done it will ultimately reboot to Android.
-edit: If you're adventurous once in the bootloader you can flash TWRP and the Oreo Go ROM from here.
Click to expand...
Click to collapse
Thanks so much, managed to get it to 6.1 and all is working fine.
Here is some background.
I ordered an LG G7 ULM off of ebay a few days ago. When I got it, I noticed that it was an LG G7 Sprint that was converted to ULM. (Which is typical of eBay). I decided to flash the latest ULM firmware to the device by downloading the latest kdz and flashing with LGup. What I didn't realize until later is that I flashed the "Brightpoint" ULM version. Knowing this, I wanted to flash the non Brightpoint version, but when I try getting into download mode, it doesn't work. It only shows the G7 logo, then shows the battery charging symbol.
Additionally, I am in USB debugging mode and have OEM unlock on in developer options.
Things I have tried:
Holding volume up and then plugging USB
Holding volume down and plugging in USB
Holding volume up and power button
Holding volume down and power button
Reboot fastboot via adb
Also, when i try using LGup without download mode it gives and error "spc code does not match"
Does anyone know how to fix this?
https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
If you try ti flash when phone is not in download mode you get "spc code does not match" error.
First method is correct
"Holding volume up and then plugging USB" If that doesn't work try adb reboot download (I don't think there is download option with fastboot command or not supported by LG G7)
If you have ADB installed,connect phone with USB cable
1)Check your phone is listed in with command
Adb devices
2) then run this command
adb reboot download
sampal said:
If you try ti flash when phone is not in download mode you get "spc code does not match" error.
First method is correct
"Holding volume up and then plugging USB" If that doesn't work try adb reboot download (I don't think there is download option with fastboot command or not supported by LG G7)
If you have ADB installed,connect phone with USB cable
1)Check your phone is listed in with command
Adb devices
2) then run this command
adb reboot download
Click to expand...
Click to collapse
1. Adb devices shows my device.
2. I tried the adb reboot download. It just reboots normally. Shows lg logo then my phone is booted up.
None of the fastboot commands word because I can't get into download mode.
onenite said:
1. Adb devices shows my device.
2. I tried the adb reboot download. It just reboots normally. Shows lg logo then my phone is booted up.
None of the fastboot commands word because I can't get into download mode.
Click to expand...
Click to collapse
If you have one of the models with OEM unlock inside the developer menu, you're wasting your time because it does nothing. I don't even know why it's there because the LG G7 ThinQ does not have fastboot mode baked in.
Try running a fastboot command and you will see. You have to get past the bootloader to access anyting to do a root and this is not possible on most of the phones here . Also you do not run these commands from download mode I don't believe, they would usually be done when in fastboot or recovery mode.
The only mode you're probably going to get into is download mode. It would be for manually upgrading firmware. You can go into that mode by holding power and Volume +. I tried for three days straight until I stumbled upon another Canadian who was able to root his phone but he had to use a special box and connectors.
There is no fastboot or recovery. All you can find is download mode and safe boot. I wish you the best of luck but if you have the same variant that I do and most of Canada does if it was purchased here then you will not be able to access fastboot because it does not exist. Don't take my word for it though, do your research and you will see I am speaking the truth. Or you can kill yourself and rip out your hair trying to get fastboot to to load but you will not succeed in doing anything but ending up bald. Luckily I shave my head or else I would have done that. Good luck on your research and if you should get fastboot to do anyting please post it in here for everyone to see so we can praise you and root our own phones also. Cheers my friend.
I didn't read back deeply but it sounds like you're attempting what I did, and use modded boot.img files to further gain access to what we need to root the phone. This is true as for what we need to do, but most who have flashed these images have either ruin their devices totally or had to reflash stock firmware. There were a few that got lucky and let's talk firmware fixed the issue but most phones that broke are probably in a landfill now. Please do share if you succeed in anyting we haven't already tried. I tried flashing to a firmware that does have fast boot capability but it did not work because fastboot is built into the phones and the firmware for any particular country has no effect on whether you can root your phone or not. Just before this I mentioned the boot.img method and I'm guessing the command you are running is something like fastboot flashroot_a boot.img and then typing the same command a second time but only with a letter b instead of an a. This method will not work either so please share if you discover a third method that no one else has discovered yet. I would donate money to you because you would basically be the developer of the root method that actually works.
TWiiTCH said:
If you have one of the models with OEM unlock inside the developer menu, you're wasting your time because it does nothing. I don't even know why it's there because the LG G7 ThinQ does not have fastboot mode baked in.
Try running a fastboot command and you will see. You have to get past the bootloader to access anyting to do a root and this is not possible on most of the phones here . Also you do not run these commands from download mode I don't believe, they would usually be done when in fastboot or recovery mode.
The only mode you're probably going to get into is download mode. It would be for manually upgrading firmware. You can go into that mode by holding power and Volume +. I tried for three days straight until I stumbled upon another Canadian who was able to root his phone but he had to use a special box and connectors.
There is no fastboot or recovery. All you can find is download mode and safe boot. I wish you the best of luck but if you have the same variant that I do and most of Canada does if it was purchased here then you will not be able to access fastboot because it does not exist. Don't take my word for it though, do your research and you will see I am speaking the truth. Or you can kill yourself and rip out your hair trying to get fastboot to to load but you will not succeed in doing anything but ending up bald. Luckily I shave my head or else I would have done that. Good luck on your research and if you should get fastboot to do anyting please post it in here for everyone to see so we can praise you and root our own phones also. Cheers my friend.
I didn't read back deeply but it sounds like you're attempting what I did, and use modded boot.img files to further gain access to what we need to root the phone. This is true as for what we need to do, but most who have flashed these images have either ruin their devices totally or had to reflash stock firmware. There were a few that got lucky and let's talk firmware fixed the issue but most phones that broke are probably in a landfill now. Please do share if you succeed in anyting we haven't already tried. I tried flashing to a firmware that does have fast boot capability but it did not work because fastboot is built into the phones and the firmware for any particular country has no effect on whether you can root your phone or not. Just before this I mentioned the boot.img method and I'm guessing the command you are running is something like fastboot flashroot_a boot.img and then typing the same command a second time but only with a letter b instead of an a. This method will not work either so please share if you discover a third method that no one else has discovered yet. I would donate money to you because you would basically be the developer of the root method that actually works.
Click to expand...
Click to collapse
Thanks for the reply.
I was reading into flashing the laf.img file which would fix the download mode not working, but I'm unable to gain root, so that isn't really an option.
I guess for now, I'm stuck with this firmware version. But, at least I'm on the latest pie version... Hopefully there will be a fix for it, or maybe someone will know how to fix this.
I have heard that you can buy for a service to fix this for around $30. But I don't think I would trust someone doing changes to my phone without a guarantee.
Help me
I have the same problem too, my phone is Verizon variant and I can't get to download mode
babykut said:
I have the same problem too, my phone is Verizon variant and I can't get to download mode
Click to expand...
Click to collapse
OK, I have solved it by myselft, you can use ADB (adb reboot recovery) to restart your phone and then holding volume up key to boot into download mode, hope it work for you
babykut said:
OK, I have solved it by myselft, you can use ADB (adb reboot recovery) to restart your phone and then holding volume up key to boot into download mode, hope it work for you
Click to expand...
Click to collapse
Oh my God, you are a genius. I can't thank you enough.... It worked!!!
onenite said:
Oh my God, you are a genius. I can't thank you enough.... It worked!!!
Click to expand...
Click to collapse
You are welcome
babykut said:
OK, I have solved it by myselft, you can use ADB (adb reboot recovery) to restart your phone and then holding volume up key to boot into download mode, hope it work for you
Click to expand...
Click to collapse
Thank you bro
babykut said:
OK, I have solved it by myselft, you can use ADB (adb reboot recovery) to restart your phone and then holding volume up key to boot into download mode, hope it work for you
Click to expand...
Click to collapse
When exactly do you hit the volume up button?
it doesnt seem to work for me
landonloco said:
When exactly do you hit the volume up button?
it doesnt seem to work for me
Click to expand...
Click to collapse
1) Give "adb reboot recovery" command
2) Press Enter
3) The display's phone shutting down
4) Hold the up volume down until you see the little label "download mode"
It works!
Jengirl said:
1) Give "adb reboot recovery" command
2) Press Enter
3) The display's phone shutting down
4) Hold the up volume down until you see the little label "download mode"
It works!
Click to expand...
Click to collapse
Wuh. It could work, but my question is, HOW THE HELL DID YOU GET YOUR LAPTOP/PC TO DETECT THE CELL PHONE!!!!!!
PD: I Have the same problem, plis help me
Jengirl said:
1) Give "adb reboot recovery" command
2) Press Enter
3) The display's phone shutting down
4) Hold the up volume down until you see the little label "download mode"
It works!
Click to expand...
Click to collapse
it shows no command screen
Do you want to bootloader and unlock and root your V35? Do you want to do this yourself? Are you feeling the need for some adventure? If you answered yes to these questions, then you are at the right place. The goal with these instructions is to make the process as smooth and pain-free as possible. These instructions are based upon what I know works through firsthand experience and what I have gathered reading. My experience is with an AT&T branded V350AWM. Others also report success. That said, there can still be problems leading to bricked phone so don’t continue if you are not comfortable with the risk. An unavoidable side-effect of bootloader unlocking is that all data on your phone will be erased. Make a back up if you don’t want to lose it permanently.
This is what you will be doing in a nutshell.
Setting the phone into a baseline Oreo conditions
Extraction of abl, laf, and boot partititions
Installation of the engineering abl and erasing the laf's using QFIL
Unlocking the phone
Flashing to Pie and maybe Q in the future if you want to update from Oreo
Generation and installation of a magisk-patched boot image for root
Upon successful completion, you will have a fresh, bootloader unlocked and rooted phone that is otherwise stock.
Preparation and requirements:
On the hardware side, you will need a PC with MS Windows installed either directly or as a virtual machine and a high quality USB cable designed for data transfer. Older USB 2.0 hardware is preferred when working with LG phones. There is a long list of software to install.
Minimal adb and fastboot
Instructions: https://forum.xda-developers.com/showthread.php?t=2317790
Download: https://www.androidfilehost.com/?fid=746010030569952951
The LG mobile drivers, http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Dev-Patched LGUP
Instructions and warnings in post #6 with thanks to @ChazzMatt: https://forum.xda-developers.com/lg-v35/help/att-v35-unlocked-wont-verizon-t3958765
Download with thanks to @tecknight for the software: https://androidfilehost.com/?fid=11410963190603845019
9008 Port Driver:
https://raw.githubusercontent.com/g...alcomm_QDLoader_HS-USB_Driver_64bit_Setup.zip
QPST with QFIIL
Some basic instructions: https://androidmtk.com/use-qpst-flash-tool
Download: https://qpsttool.com/qpst-tool-v2-7-480
Download and install each of these programs on your PC in the listed order.
You are also going to need some super important supporting files that make all of this magic possible.
The V35 engineering abl that will give you fastboot with thanks to @vlad48 for making it available: https://www.androidfilehost.com/?fid=1395089523397895796. Yes,it says V20, ignore it, it is fine. Extract abl_a and abl_b, and append a “.img” extension to each. Note the locations on your PC for future use.
The recently available emergency download (EDL) firehose that makes direct partition flashing possible released by Biao on Telegram. It is available here:
https://androidfilehost.com/?fid=4349826312261705871
or as an attachment in @Xsavi’s similar and earlier instructions for the V40: https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
Note its location for later use.
Troubleshooting:
These instructions assume that your phone boots normally. Even with that there can still be issues due to software drivers and pc-hardware. They can be broadly summarized as a difficulty getting the computer to recognize and communicate with the phone and vice-versa. They arise frequently. If you encounter difficulties, review these troubleshooting tips compiled and written by @ChazzMatt and taken from his V30 WTF instructions.
Look in your ADB folder on your PC and confirm all known Windows file extensions enabled, https://goo.gl/YxLRG5.
Confirm all Windows hidden files and folders are visible, https://goo.gl/1jBKne.
Confirm USB debugging is on in Developer Options, and your PC has authorization for your phone, https://goo.gl/DgojL9.
Install another version of ADB. Install as close to the root of your hard drive as possible. X:\ADB where X is your hard drive.
Re-install LG mobile drivers, https://is.gd/Jbrvx1.
Try another USB cable.
Installing this Windows driver found attached to this post, (Thanks @gazzacbr and @FZZF) https://goo.gl/CqqNZT.
Install Google USB driver, (Thanks @s0lidsneak) https://goo.gl/z2Tahw.
Try another USB port on your computer or try cheap USB 2.0 hub, https://is.gd/gM1mM0.
Reboot the computer.
Try another computer. (THIS usually solves the problem, https://goo.gl/x637H1. Kudos if you find an an old Win7 PC, https://goo.gl/EaGMhs.)
Master Reset (full reset of phone using hardware buttons), https://goo.gl/N4LcLD. Phone will be reset anyway after bootloader unlock. Doing it prior may fix something preventing the command from working.
Step 1: Setting an Oreo baseline:
The engineering files for bootloader unlock of the V35 phone are designed to work with Oreo. If you are an Pie or Q, it is highly recommended that you flash back to Oreo. For those of you with the common AT&T V350AWM model that is not on Oreo, there are a couple of points to consider
AT&T does not release flashable roms. If you are on AT&T Pie or eventually Q, there is no going back unless of course you take the time to make a backup of the rom itself. That is not covered in this guide nor am I aware of a guide on how to do this.
AT&T sim-locks its branded V35’s and the menu to unlock is specific to the AT&T rom. You should strongly consider purchasing of a sim-unlock code and applying it before flashing another rom!
To set the baseline:
If you are already on Oreo perform a master reset. To do this, start by turning the phone off. Then press and hold the power and volume - buttons at the same time until you see the LG logo appear. When the LG log appears, release the power button and then press and hold it again while continuing to press the volume – button. Follow the menus to perform the reset.
If you are on Pie or Q, you are going to flash or cross-flash back to Oreo. The kdz's are available for downloaded from https://lg-firmwares.com/lg-lmv350ulm-firmwares/#tab=firmwares. Reports are that roms can be cross-flashed across V35 models with the exception of the Korean V350N. If you are not familiar with the roms, the favored ones are the Google Fi / North American versions for the V350ULM. Down load the latest Oreo version
https://lg-firmwares.com/downloads-file/18971/V350ULM10i_00_NAO_US_OP_0221, md5sum: 64554877b692601d5906d2bdc9691712To flash the rom, turn the phone off, press and hold the volume – button while connecting it to the computer’s USB. The phone screen should show “Download Mode”. Start-up LGUP on your PC, select the rom kdz, and flash it using “Refurbish”. Do not use any other modes or you will have serious trouble!
Step 2: Partition Extraction, Modification and Bootloader Unlock
Enable “OEM Unlock”: Turn on the phone and go through a minimal set-up process. Next go to Settings→ System→ About Phone→ Software info. Repeatedly tap on “Build Number” until you receive a message that you are now a “Developer”. Next go to Next go to Settings→ System→Developer options. Look for “OEM unlock” and flip the switch to on. Exit the “Settings” menus.
Boot the phone in EDL 9008 mode: The “button dance” to put the phone into EDL mode requires quick hands. To increase the likelihood of success, take the phone out of any case to expose the volume buttons. With the phone fully booted and turned on, connect it to your computer by USB. Press and hold the power and volume – keys at the same time. The phone will likely take a screenshoot, keep holding the buttons, afterwards it will bring up a reboot countdown message. With one second left, start pressing the volume + button while still keeping the power and volume – buttons pressed. The phone will show a black screen and windows with make its connection sound if you succeeded in reaching ECL mode. Release the button immediately. Look at your computer, you should also see an entry in the Windows Device Manager under “Ports” that reads:
“Qualcomm HS-USB QDLoader 9008 (COMXX)”
where XX is the port. The phone will just reboot if you didn’t click the volume + button sufficiently fast. Keep trying, you will eventually succeed. If the screen on the phone does go black and you don't see the phone listed in the Windows Device Manager, then you should check installation of 9008 port driver.
Start and configure QFIL: Go to the Start Menu or whatever passes for it on your Windows computer and fire up QFIL. Survey the screen:
You should see “Qualcomm HS-USB QDLoader 9008 XX” next to “Select Port…”.
There should be small text in the lower right corner that reads “Storage Type:”; Select “ufs”.
There is a subheading near the upper left that reads “Select Build Type”. Tick “Flat Build”.
Now using the “Browse…” button under the “Select Programmer", navigate to the folder that contains the firehose file, “prog_ufs_firehose_Sdm845_lgev40.elf” and select it.
Extract partitions: Click on “Tools” in the menu bar of QFIL. Select “Partition Manager”. You will be asked if you selected the correct firehose. If you did then click OK. A screen will now appear that lists partitions on your phone. Scroll down the list and look for “abl_a”, “laf_a”, “abl_b”, and “laf_b”.
Right click on “abl_a”
Select “Manage Partition Data”
Select “Read Data…”
Open a folder and navigate to location where the extracted file is located. The QFIL “Status” output shows the location and filename. On my PC, it reads:
“C:\Users\whoiam\AppData\Roaming\Qualcomm\QFIIL\COMPORT_XX\ReadData_ufs_xxxxx.bin” where XX is the port number and the “xxxxx” are details about the partition name. Copy the file to a dedicated folder and rename it “abl_a.img”.
Repeat the this process for “laf_a”, “boot_a”, “abl_b”, “laf_b”, and “boot_b” partitions. Note the locations of these files as back-ups and also for the following section on rooting.
Use QFIL to get fastboot:
Write the engineering abl’s: In QFIL, do the following:
Right click on abl_a.
Select “Manage Partition Data”
Select “Load Image”
In the dialog, Navigate to the location of the engineering abl_a.img file you downloaded in the preparation section, select it, and click “Open”.
Repeat this same procedure for abl_b.
Erase laf’s: In QFIL, do the following:
Right click on “laf_a”
Select “Manage Partition Data”
Select “Erase”
Confirm that you want to erase
Repeat for laf_b.
Unplug the phone from USB
Press and hold the power and volume - buttons until the LG V35 boot logo appears. Allow the phone to reboot.
Turn the phone off.
Unlock the bootloader:
Enter fastboot mode: Hold the volume + button and plug in the USB cable. The phone will boot to a series of menus that include “Start” and “Power off”.
Run a command prompt as Administrator. If necessary navigate to the directory where you installed adb.exe and fastboot.exe.
Check that the phone communicates with fastboot: Type “fastboot devices” and press enter. It should return details about your device. It reads “LMV350AWMxxxxxxx fastboot” with my phone.
Bootloader unlock: Type “fastboot oem unlock”. Congratulations if it reports OK, your phone is now unlocked. If it reports failed then try another USB port on your PC, a better/different cable, and potentially even another PC.
Reboot the phone
Step 3: Restore download mode and flash to desired rom:
If the current version of Oreo is where you want to be then skip to Step 4.
If you want to upgrade to Pie or eventually Q, then you need to restore the laf_a, laf_b, abl_a, and abl_b partitions to recover download mode. It should be clear from what you have done above with QFIL how to do this.
Download the kdz of your desired rom. The Google/NAO version of Pie is recommended and available at this link, https://lg-firmwares.com/downloads-file/22230/V350ULM20f_00_NAO_US_OP_0218.
To flash the rom, turn the phone off, press and hold the volume – button while connecting it to the computer’s USB. The phone screen should show “Download Mode”. Start-up LGUP on your PC, select the rom kdz, and flash it using “Refurbish”. Do not use any other modes or you will have serious trouble!
Step 4: Install Magisk for Root:
Re-enter EDL mode with the above button dance procedure
Extract boot_a and boot_b partitions: Click on “Tools” in the menu bar of QFIL. Select “Partition Manager”. You will be asked if you selected the correct firehose. If you did then click OK. A screen will now appear that lists partitions on your phone. Scroll down the list and look "boot_a” and “boot_b”.
Generate a Magisk-patched booted image working directly with the phone:
Download a stable version of Magisk Manager from the official website: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445. It should be saved in the “Download” folder.
In Settings, navigate to Apps & Notifications→ Special access → Install unknown apps. Click on File Manager and set it to allowed.
Open the “File Manager” app and navigate to the Download folder.
Select and install the “MagiskManager-v7.5.1.apk” file keeping in mind that the version numbers may be different.
Connect the phone to USB and place it in file transfer mode.
Copy boot_a.img and boot_b.img to the phone Download folder
Start “MagiskManager” and select “Install”. When presented with the option, tap “Select and Patch a File”.
Navigate to the “Downloads” folder where and select boot_a.img.
There will now be a file named “magisk_patched.img” in the “Downloads” folder. Change its name to magisk_patched_a.img.
Repeat this process with boot_b.img.
Install the Magisk-patched boot images using the PC:
Copy the magisk_patched_a.img and magisk_patched_b to the windows computer.
Put the phone into 9008 EDL mode with the button dance described above.
Start QFIL, configure it as described above, and then click on “Tools” in the menu bar of QFIL and Select “Partition Manager”.
Scroll through the list of partitions and locate boot_a. Right click on it and select “Load Image”. Point it to the magisk_patched_a.img file.
Repeat the previous step for boot_b and load the magisk_patched_b.img file
Reboot your rooted phone.
Step 5: Remove Root Checker: (Added 20200409)
I say with sarcasm that another way that LG has made our lives better was to implement a root-check and monitoring system. Many here are familiar with the root check daemon from the V30. There is a root-check disable twrp package to fix this problem. Installation and use of TWRP for the V35 is tricky. Don't worry, there is another way.
Put the phone in USB debug mode
Connect to your computer
With adb from a command prompt on the computer do the following
adb devices <-- If your devices is properly connect and recognized, adb will respond
List of devices attached
LMV350XXXXXXXXX device
adb shell <-- If you have a shell into the phone you will now see
judyp:/ $
pm uninstall -k --user 0 com.lge.srtc <-- This command removes the root checker, if it succeeds you will get the response:
Success
pm uninstall -k --user 0 com.lge.mlt <-- This command removes the LG monitor, if it succeeds you will get the response:
Success
Happy Rooting!
Wow,
Thanks for the great guide, can't wait to try this.
One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?
THANK YOU for this. Seriously. Really well done. I can't wait to try it if I ever get my phone back into shape where I CAN try it. ?
There are several posts by owners of AT&T branded V35's who cross-flashed to the Korean V350N Pie rom successfully. They were in a rush for Pie and it was released for Korean models first. Still, I have in my notes not to do the reverse, but I can't find the link. Hypothetically, one can recover from about anything using 9008 mode and QFIL provided you have back ups of the partition images of your phone.
fpozar said:
Wow,
Thanks for the great guide, can't wait to try this.
One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?
Click to expand...
Click to collapse
cmrntnnr said:
There are several posts by owners of AT&T branded V35's who cross-flashed to the Korean V350N Pie rom successfully. They were in a rush for Pie and it was released for Korean models first. Still, I have in my notes not to do the reverse, but I can't find the link. Hypothetically, one can recover from about anything using 9008 mode and QFIL provided you have back ups of the partition images of your phone.
Click to expand...
Click to collapse
I was one of those who leaped to the Korean KDZ. Now I am running NAO firmware. Guide looks well written. I might wind up taking the leap. Good job bro!
Thanks, I follow your steps very carfully, and now I have a rooted v35.
Nicely done. Thank yoh for sharing the result.
fpozar said:
Wow,
Thanks for the great guide, can't wait to try this.
One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?
Click to expand...
Click to collapse
vavoo said:
Thanks, I follow your steps very carfully, and now I have a rooted v35.
Click to expand...
Click to collapse
So due to prior.... mishaps, my phone will not boot ("all slots are unbootable!"), and fastboot produces "Flashing Unlock is not allowed" every time the OEM unlock is attempted. What should I do?
I am stuck at Fastboot Mode. It says the "Device state - Unlocked", but when if I choose Start or Power off/on my phone it just goes back into fastboot everytime.
1. I installed and flashed the Pie rom you linked in step 1
2. I turned "Oem unlock" to On.
3. placed the phone in 9008 mode, backed up abl_a, laf_a, boot_a, abl_b, laf_b, and boot_b.
Loaded the img to abl_a and abl_b.
Finally, Erased laf_a and laf_b
4. within fastboot, unlocked bootloader
Any ideas ?
If the phone unlocked, go back into 9008 EDL mode and restore the laf and abl images using your backups. That should get you booting.
dave1567 said:
Any ideas ?
Click to expand...
Click to collapse
1. Download the attached EDL.zip
2. Extract it to a local folder on your PC
3. While your V35 is in fastboot mode plug it to your PC via USB (USB2 port preferred)
4. Double click on RebootEDL.bat
5. Phone will enter 9008 (EDL) mode screen will be black.
6.Using QFIL flash back your PIE abl_a and abl_b
7. Using QFIL flash attached FTM partition from FTMV35PIE.zip.
8. Hold Vol-and power to reboot.
vlad48 said:
1. Download the attached EDL.zip
2. Extract it to a local folder on your PC
3. While your V35 is in fastboot mode plug it to your PC via USB (USB2 port preferred)
4. Double click on RebootEDL.bat
5. Phone will enter 9008 (EDL) mode screen will be black.
6.Using QFIL flash back your PIE abl_a and abl_b
7. Using QFIL flash attached FTM partition from FTMV35PIE.zip.
8. Hold Vol-and power to reboot.
Click to expand...
Click to collapse
I didn't use your bat since it looks like I can still boot into 9008 mode with the button dance method.
Unfortunately, still nothing!
I flashed my abl_a.img and abl_b.img backups I made to the abl_a/b partitions and flashed your FTM_BL.img to my FTM partition, but it didn't seem to do anything except cause some graphical glitches within fastboot menu (everything still functioned though)
Just in case, I re-locked my phone (fastboot oem lock) and started the QFIL process over (flashing with engineered abl_a and abl_b imgs)
Then within fastboot mode, I ran "fastboot oem unlock" a few times because it fails, but finally it went through
Now the phone is unlocked again, but still just always just boots into fastboot mode!
Of course it will boot only to fastboot as you are using engineering abl from Oreo - please understand there is a signature check match which fails and you will not be able to continue booting.
So, in brief, you need to have all partitions on respective bootable slot form either Oreo or Pie kdz version. So you need to be sure that you flashed your PIE abl wither via QFIL or via LGUP.
vlad48 said:
Of course it will boot only to fastboot as you are using engineering abl from Oreo - please understand there is a signature check match which fails and you will not be able to continue booting.
So, in brief, you need to have all partitions on respective bootable slot form either Oreo or Pie kdz version. So you need to be sure that you flashed your PIE abl wither via QFIL or via LGUP.
Click to expand...
Click to collapse
Unfortunately, I don't understand. Thanks for trying to help though.
Anyways, I managed to fix the problem and I'm all set.
- Restored my laf_a and laf_b partitions
- Booted into download mode and re-installed the pie image with LG Up.
- Was now able to boot normally
- Followed the instructions in the guide to get magisk installed and now I'm all set!
Thanks all and hope this helps someone
I scouted my way through these very same steps a couple weeks ago. Soft bricked my device a couple times ? but eventually got her there. Glad too see a dedicated guide is out now. Only problem I've run into is the ctsprofile:fail problem. Been able to fix with spoof pixel fingerprints but it's not ideal. Still looking for solutions if anyone knows anything.
Iantuition said:
So due to prior.... mishaps, my phone will not boot ("all slots are unbootable!"), and fastboot produces "Flashing Unlock is not allowed" every time the OEM unlock is attempted. What should I do?
Click to expand...
Click to collapse
What is the minimum needed for you to enter download mode? I have backups of most partitions i will be happy to share and you can use Qfil to flash those to get to download mode then use LGUP to flash a normal kdz? If so, let me know.
so somehow between qfil and getting fastboot i've got myself in trouble. i dont understand what i did wrong but i got stuck in a fastboot loop and tried following some of the fixes mentioned previously in this thread. when i get back to qfil and try to go to partition manager it wont let me see any of the partitions and shows various sahara errors and fails in the log box. can someone please help idk what to do
Sorry to hear that. The first time I tried to use QFIL I got a Sahara error and could not see partitions. It was resolved by reinstalling the 9008 port driver and then QPST in that order. It happened again later when windows tries to be helpful by automatically reinstalling drivers when the phone is plugged in but with a mode change.
Flowtron3000 said:
so somehow between qfil and getting fastboot i've got myself in trouble. i dont understand what i did wrong but i got stuck in a fastboot loop and tried following some of the fixes mentioned previously in this thread. when i get back to qfil and try to go to partition manager it wont let me see any of the partitions and shows various sahara errors and fails in the log box. can someone please help idk what to do
Click to expand...
Click to collapse
Will this help me sim/carrier unlock my v35awm?
Can you lock the bootloader after this is done and keep root? Need it for banking apps.