Related
My gear live was rooted had twrp on it and i was trying to update it to the newest android wear os i couldn't update it with twrp on it and i tried adb sideload with no luck restarted it restarted my phone no luck so i tried the stock recovery no luck with adb sideload i factory reset my watch everything was fine it downloaded an update which was KNX01Q so i reset the device again and it did the download again but this time it failed in recovery so i flashed the stock img from the gear live restore tool v3 now my watch is on KGW42N and i can't get it to connect to my phone it doesn't show up at all in android wear the weirdest part i used to have an option to search for Bluetooth devices in the watch settings but now there's no option and since i can't connect it to my phone i can't even connect it to my pc says adb device unauthorized.. i can get into recovery the bootloader of the watch it even starts up but it stays at the screen saying to install android wear on your phone but i can't recognize the watch it's like the Bluetooth is off or not working on the watch? Anyone have any ideas or workarounds for an unauthorized adb device?? Any help would be appreciated.
I'm having the same issue. I tried to go back to 100% stock so I could download the newest update, but now my phone doesn't recognize the watch via Bluetooth at all..
Edit: Fixed it, fastboot flashed the stock KMV78Y located here: http://forum.xda-developers.com/gear-live/development/rom-octamodwear-stock-root-busybox-t2834620
For people using the Samsung Gear Live Restore Tool, if that stock image worked for you, I would recommend replacing your 42Nboot.img and 42Nsystem.img with the ones in the above for future endeavors.
Also, that zip file needs a lot more attention in these forums.
YES!!!!
bkid001 said:
i'm having the same issue. I tried to go back to 100% stock so i could download the newest update, but now my phone doesn't recognize the watch via bluetooth at all..
Edit: Fixed it, fastboot flashed the stock kmv78y located here: http://forum.xda-developers.com/gear-live/development/rom-octamodwear-stock-root-busybox-t2834620
for people using the samsung gear live restore tool, if that stock image worked for you, i would recommend replacing your 42nboot.img and 42nsystem.img with the ones in the above for future endeavors.
Also, that zip file needs a lot more attention in these forums.
Click to expand...
Click to collapse
thank you so much you are the best!!
Bkid001 said:
I'm having the same issue. I tried to go back to 100% stock so I could download the newest update, but now my phone doesn't recognize the watch via Bluetooth at all..
Edit: Fixed it, fastboot flashed the stock KMV78Y located here: http://forum.xda-developers.com/gear-live/development/rom-octamodwear-stock-root-busybox-t2834620
For people using the Samsung Gear Live Restore Tool, if that stock image worked for you, I would recommend replacing your 42Nboot.img and 42Nsystem.img with the ones in the above for future endeavors.
Also, that zip file needs a lot more attention in these forums.
Click to expand...
Click to collapse
DUDE!! You totally fixed all the problems I was having with my gear live. I am a late adopter and had so much trouble with it. After flashing that firmware, the watch upgraded to 6.0.1. All my syncing issues, updating issues, every issue I had fixed. Thanks soo much. This is my second one. Had to return the other. Just another thanks. You the man.
No problem guys! I didn't even remember this post, and the only way I knew about it was an email I got because I was quoted
Bkid001 said:
No problem guys! I didn't even remember this post, and the only way I knew about it was an email I got because I was quoted
Click to expand...
Click to collapse
You still the man!! May not seem like a lot for some people but I just wanted a cheap fitness/smartwatch tracker. This was the thing to get. Got it off Amazon and first one was sh!t. Wouldn't sync, update, or anything. Second one was dead. Tried your method on the first one and it revived it! Now it's the smart watch I had imagined it to be. Cheap, good specs, and a fitness tracker. Can't thank you enough.
quantump8 said:
DUDE!! You totally fixed all the problems I was having with my gear live. I am a late adopter and had so much trouble with it. After flashing that firmware, the watch upgraded to 6.0.1. All my syncing issues, updating issues, every issue I had fixed. Thanks soo much. This is my second one. Had to return the other. Just another thanks. You the man.
Click to expand...
Click to collapse
When you say flashed, do you mean that you took the files fro the stock rom he listed in his post, and replaced the "78Y" files with the ones from the post?
Deathscreton said:
When you say flashed, do you mean that you took the files fro the stock rom he listed in his post, and replaced the "78Y" files with the ones from the post?
Click to expand...
Click to collapse
I took the boot.img and system.img from the "78Y" file and replaced the boot.img and system.img from the Samsung Gear Live Restore tool files. But you have to make sure you rename them "42Nboot.img and 42Nsystem.img" before the tool will recognize them. Hope this helps.
quantump8 said:
I took the boot.img and system.img from the "78Y" file and replaced the boot.img and system.img from the Samsung Gear Live Restore tool files. But you have to make sure you rename them "42Nboot.img and 42Nsystem.img" before the tool will recognize them. Hope this helps.
Click to expand...
Click to collapse
I'm not sure I understand. Maybe I confused myself, so let me ask again. xD
I have the original Samsung Gear Live Restore Tool v2 folder on my desktop. Inside, I have the 78Y files, (boot, recovery and system in that order) that are located in that folder. These are the files that need to be replaced by the originals linked above (kmv78y)that solved the issues, correct? I don't have any "42Nboot.img" or "42Nsystem.img" files. Just the ones I listed.
When I downloaded the link to the original stock ROM from the post above, all that was there was a system and boot img, which I assume is what needs to be renamed "42xxxx.img" according to your post, do I correct? And even if that is correct, the Samsung Restore Tool is scripted to look for the 78Y files, not any type of 42N files.
Deathscreton said:
I'm not sure I understand. Maybe I confused myself, so let me ask again. xD
I have the original Samsung Gear Live Restore Tool v2 folder on my desktop. Inside, I have the 78Y files, (boot, recovery and system in that order) that are located in that folder. These are the files that need to be replaced by the originals linked above (kmv78y)that solved the issues, correct? I don't have any "42Nboot.img" or "42Nsystem.img" files. Just the ones I listed.
When I downloaded the link to the original stock ROM from the post above, all that was there was a system and boot img, which I assume is what needs to be renamed "42xxxx.img" according to your post, do I correct? And even if that is correct, the Samsung Restore Tool is scripted to look for the 78Y files, not any type of 42N files.
Click to expand...
Click to collapse
Whatever the files names are, just replace them with the ones from 78Y file. For me, the files from the original tool had "42N" before the system.img name and the tool wouldnt work until I changed the file names. If they are just system.img and boot.img, then just replace without renaming. But all img files must be the same name. Like I said, at least for me, this was the way it worked.
quantump8 said:
Whatever the files names are, just replace them with the ones from 78Y file. For me, the files from the original tool had "42N" before the system.img name and the tool wouldnt work until I changed the file names. If they are just system.img and boot.img, then just replace without renaming. But all img files must be the same name. Like I said, at least for me, this was the way it worked.
Click to expand...
Click to collapse
I ended up trying this and I still have a few problems regarding Contacts (Try again on your phone) and Play Music (Your phone is not nearby...). Maybe app specific issues. I appreciate the help though. :c
Has anyone found a KDZ file for the Sprint LG G4?
Nope, and I'm in need of one badly...
afreed1 said:
Has anyone found a KDZ file for the Sprint LG G4?
Click to expand...
Click to collapse
There will most likely NEVER be a KDZ. If anything it will be a TOT file.
I'm waiting myself. But my phone in a bootloop after using titanium backup. Need this asap
Sent from my 831C using xda premium
I am holding off on rooting the phone until TOT or KDZ is available. I am not too worried about the rooting process causing problems. It's more a concern that I will not be able to keep myself from messing around with the system files and get into a phone not booting or boot loop situation with no custom recovery, nandroid backup or restore file to recover with.
Damn, I wish I never followed the directions for rooting the G4. Now I know there are no backup files in case of problems.... Great
afreed1 said:
Has anyone found a KDZ file for the Sprint LG G4?
Click to expand...
Click to collapse
Nope, and it seems like a lot of people are having boot loops with this phone. We'll just have to wait.
Sprint G4 here (LS991)
I rooted my phone successfully, but being that this is my first LG phone I stupidly uninstalled key apps that brings up the "Security Error" boot loop.
Been looking for a KDZ or TOT file, anything that would help me restore my phone back to stock. Looks like Verizon and TMobile have their stock firmwares out already, but Sprint is always the last to get any significant software.
I have been (and will continue) to follow hyelton's page with the released KDZ files : http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
I will follow up as soon as Sprint's KDZ/TOT file is released.
If there is anything I could do to help the devs get this through, I would gladly help. I just want my G4 back
Rooted using this method: http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
Bondster45 said:
Sprint G4 here (LS991)
I rooted my phone successfully, but being that this is my first LG phone I stupidly uninstalled key apps that brings up the "Security Error" boot loop.
Been looking for a KDZ or TOT file, anything that would help me restore my phone back to stock. Looks like Verizon and TMobile have their stock firmwares out already, but Sprint is always the last to get any significant software.
I have been (and will continue) to follow hyelton's page with the released KDZ files : http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
I will follow up as soon as Sprint's KDZ/TOT file is released.
If there is anything I could do to help the devs get this through, I would gladly help. I just want my G4 back
Rooted using this method: http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
Click to expand...
Click to collapse
Welcome to the bootloop ship, its just a waiting game at this point. But as soon as someone has it, it will be posted ASAP!
1. Did you guys not follow the directions when rooting to create a backup of the initial, non-rooted system.img?
2. What about re-flashing the rooted system.img?
Assuming you can reflash either original or rooted system.img, would booting into factory recovery and doing a factory reset work?
natator99 said:
1. Did you guys not follow the directions when rooting to create a backup of the initial, non-rooted system.img?
2. What about re-flashing the rooted system.img?
Assuming you can reflash either original or rooted system.img, would booting into factory recovery and doing a factory reset work?
Click to expand...
Click to collapse
No no no. Do not factory reset while rooted. You'll continue to get bootloops. You will just have to wait until the KDZ is released.
Welp, looks like I'm returning my phone.
Wont this solve the problem? http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
wilsonch1551 said:
Wont this solve the problem? http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
Click to expand...
Click to collapse
No that solves nothing, we still have no .tot file for the ls991
Sent from my LGLS991 using XDA Free mobile app
thetruejay20 said:
No that solves nothing, we still have no .tot file for the ls991
Sent from my LGLS991 using XDA Free mobile app
Click to expand...
Click to collapse
Pardon my ignorance, but it looks like there is a .kdz file for the G4. Will that not work? I honestly have no clue how .kdz or .tot files work, but I trying to figure out the difference.
Somehow messed up my phone using google cardboard of all things... well at least that is what I was using when it rebooted and went into a boot loop. I rooted it days ago and the phone has rebooted since I did it with no problems. I have not done anything with root yet on the phone but for some reason cardboard sent it into a boot loop. I tried reflashing the rooted system image but that didn't work. My phone is now pretty much bricked. There is no tot file and it is impossible to transfer a file onto the phone or sd card(can't mount sdcard) to try another system image.
This is a disaster for me as I bought this through best buy. I'm hoping I can get LG to re-flash the phone and give me the same exact phone back. Why? The plan I signed was for a leased phone. I worry that if I use the warranty and get a new imei number phone that I will void my lease and I have to purchase the broken phone out-right. But I guess if I get another phone I would just be where I would be 2 years down the road anyways.
Only problem is I was double stupid and did the wireless charging mod so I now wonder if LG would even look at the phone let alone getting warranty to replace it.... however, the warranty place probably wouldn't even notice the sticker was changed.
So I have no clue what route to take. On top of all this since I am on this stupid Best Buy plan I can't re-activate my old phone. Only Best Buy can do that. Now I am phone-less to boot. I wonder if Best Buy will even activate the old phone for me.... I guess I will find out tomorrow. If not I will have to pay $5 more a month to change my plan to the official Sprint plan.
If this all turns to crap I might just eat the lease cost, warranty the phone, re-sell and get something else. I am done with this phone.
Has any of you contacted @Sj12345 ?
He made this tool for us over at the G Flex 2 forums and people have been able to restore their phones back to booting normally.
There is a catch as allways... he needs a full backup of system.img from your phones and you have to be able to access DOWNLOAD Mode.
Good luck guys.
Here is the forum check it out.
Credits to OP.
Alex_XV6700 said:
Has any of you contacted @Sj12345 ?
He made this tool for us over at the G Flex 2 forums and people have been able to restore their phones back to booting normally.
There is a catch as allways... he needs a full backup of system.img from your phones and you have to be able to access DOWNLOAD Mode.
Good luck guys.
Here is the forum check it out.
Credits to OP.
Click to expand...
Click to collapse
Would the tar.gz file or underlying system.img from here work? When I rooted my phone with that image my camera would get errors where the camera has stopped or the device would freeze up and restart a lot.
I'm guessing we need a fresh nonrooted img or tot file. We just need a fresh img or tot file. Can't wait to revert back to complete stock/make a backup/rerun root
http://downloads.codefi.re/thecubed/lg_g4/lef/LS991ZV5.tar.gz
1230clock said:
Would the tar.gz file or underlying system.img from here work? When I rooted my phone with that image my camera would get errors where the camera has stopped or the device would freeze up and restart a lot.
I'm guessing we need a fresh nonrooted img or tot file. We just need a fresh img or tot file. Can't wait to revert back to complete stock/make a backup/rerun root
http://downloads.codefi.re/thecubed/lg_g4/lef/LS991ZV5.tar.gz
Click to expand...
Click to collapse
I guess it would be better to use a clean non-rooted system.img
But if someone that is rooted and has no trouble with any app can pull their sys.img that would work for you.
Remember the way this restores is exclusively for GFLEX2 so I always suggest you should contact @Sj12345 for guidance, He´s the man.
I just saw y´all had a similar problem to ATT GFLEX2 users no TOT/KDZ.
shared a link to the ZV5 sys.img to ya hope it helps
I got impatient waiting
I followed all the documented procedures.
You apply this exactly like ZV5 Root. This is only for LS991 (Sprint).
I've tested Root Explorer and WIFI Tether Router. It hesitated a little on the first attempt to grant root, I was probably rushing.
Once you apply this image on first boot it will want to upgrade Super User and you have to use "Normal".
YOU MUST BE ON ZV6 before you use this.
http://softronix.com/g4/Rooted.LS991.System.ZV6.zip
Not responsible for any bricking. I followed all procedures posted and I'm not gonna replicate it here.
Make sure you backup your unrooted ZV6 System image. I diffed my backup with the one uploaded by another developer and they are different.
I also tested rerooting a ZV5 stock image and it is different than the one uploaded in the ZV5 Root thread.
Oh, I should mention, I restored my ZV5 image first.
Then tried to take the ZV6 OTA update. It just stayed stuck "Now Rebooting". Tried manually rebooting. And it just went back to ZV5 boot.
So then I tried applying the update through the SD Card. That failed too, I guess it doesn't like my format of SD Card (didn't want to wipe that).
I suspect if I factory Reset ZV5 the AV6 OTA would have been fine, but I didn't want to do that.
So I noticed the ADB Sideload upgrade option in Recovery and tried that and it worked fine.
It even gave you the command syntax for ADB sideload. I had to upgrade ADB to make it work (adb sideload told me the verision I had was too old, which came from the LG_Root.Zip).
I have not done a lot of testing. I can't say tomorrow that LG didn't add some sneaky app that removes root or something. But at this moment it seems fine.
Feel free to mirror it.
How has this been working for you so far?
No problems. Even tethered while roaming with Wifi Tether Router.
Thanks for this!
I picked up a G4 a couple weeks ago for a basically a song. After reading that one thread you wrote, I figured.. why not give it a shot?
Which post, moving from M9 to G4?
Don't wanna sound stupid but how do I install this? I'm new to rooting.
votefortrump said:
Don't wanna sound stupid but how do I install this? I'm new to rooting.
Click to expand...
Click to collapse
Never mind I found the root tutorial you were referring to...but at what part of the tutorial do I use the image file you attached in the post? Once again sorry if I seem to be lacking common sense (because I am).
You do exactly what the ZV5 root thread(s) do. But you need to be on ZV6 and then use this rooted ZV6 image instead of being on ZV5 using Rooted ZV5 image.
Can someone provide the link on how to backup current stock system.img? I can't seem to find it.
mswlogo said:
You do exactly what the ZV5 root thread(s) do. But you need to be on ZV6 and then use this rooted ZV6 image instead of being on ZV5 using Rooted ZV5 image.
Click to expand...
Click to collapse
Oh ok, so in this tutorial http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765 I just replace 'system.rooted.phonemodel.img' with 'rootedsystem.LS991.ZV6.img' and I'm good?
Yes, just make you do a backup first and you are on ZV6.
Backup is in 2nd post by autoprime.
Also be careful when copying dd comands from the web page that you copy the whole command.
note the horizontal scrollbar.
ZV6.img flash over ZV5?
I know the post said I have to be on ZV6, but I don't want to loose the ability to flash tot(I've bricked my phone before). Has anyone tried this? I've read other posts that say you can't reflash tot after taking the update, and nothing about updating through this method. Would this brick my phone, should I try it?
Corrupt file .zip?
I have already tried both WiFi and Phone network, but when I finally download the zv6.img file it says is corrupted and doesn't let me extract it. I don't know what is the problem please help me.
TxShack said:
I have already tried both WiFi and Phone network, but when I finally download the zv6.img file it says is corrupted and doesn't let me extract it. I don't know what is the problem please help me.
Click to expand...
Click to collapse
You don't extract the .img file. Just throw it in the sdcard directory root.
G41LAH said:
I know the post said I have to be on ZV6, but I don't want to loose the ability to flash tot(I've bricked my phone before). Has anyone tried this? I've read other posts that say you can't reflash tot after taking the update, and nothing about updating through this method. Would this brick my phone, should I try it?
Click to expand...
Click to collapse
I was able to flash the ZV6 TOT with no issues after updating to ZV6
misteroh said:
You don't extract the .img file. Just throw it in the sdcard directory root.
Click to expand...
Click to collapse
When you download the file it comes in a .zip file. That's what I meant to say when extracting and qhen I did didn't work. Anyways thanks, found another rooted ZV6 .zip on another post and that one let me extract the file in my phone. Don't know why this one won't let me.
Has anyone else had success with this?
A whole bunch of folks are rooted on ZV6. There is also a pseudo custom ROM based on ZV6 called Ultra Pop.
Read through the threads in Development.
http://forum.xda-developers.com/sprint-g4/development
Hello everyone. I just got a Sprint LG G4 today. I would like to root my G4 but not exactly sure how to do it. I have done some rooting in the past so I am a little familar with it. My software version is LS991ZV6, security software version MDF v1.1 Release 5. From what I read, the rooting process is for zv5, is this correct? Is there a rooting process for my software version, and if so, is there a tutorial for it? Does this also install a custom recovery or is there a different process for that? I know this is probably not the place to ask but since I am enquiring, are there any roms for the sprint ls991, ex mm rom, etc? Also, how can I find the files to disable OTA updates. I have googled it and it says to disable sprintinstaller apk but I cannot find that file in settings- apps-all. Also, I read to do a backup before trying to root. I am on stock recovery and when I go into that, there is no option to backup, am I doing something wrong. Thanks again for your feedback.
Going to try it now! Looking forward to trying out xposed! I really don't want to flash an actual ROM because I love the stock camera app way too much.. And the tweaks look awesome.
Hi im on zv9 but want to go back to zv6. Preferably a zv6 rooted. Which guide is the best to follow? If anyone who frequents here could link it would be greatly appreciated.
Thanks
Hoping someone has a minute to inform me of how to repair my bionc from vzw. I had safestrap 3.73 on and upgraded to safestrap 3.75 with rooted stock moto image from way back when. I saw a lineage 14.1 image install and thought what the heck. couldnt hurt. so I did a nandroid backup with compression to the external sdcard of all partions(securedata,system,data,webroot). did another backup to the internal partion. had the prefrered storage device as intenrnal memory. I then wiped system-data-cache-dalvik and left webtop and secure partion alone. I tried unlocking the bootloader from moto bye getting my device info in fastboot but fastboot did not understand the "oem" command. I remember I was able to boot multiple boots but it had to share the same kerenl so I firgured what the the heck. I could always safestrap back and restore if lineage os failed. my mistake. I assumed. I then found there was a file called moto-fastboot but not sure if it was any different than google's fastboot. before I get things anymore screwed up I thought I would kindly ask for someone to throw me a lifepreserver because I wanna get me and the brick outta the water.
anyhow now it tries to boot, reboots and gets a dead android bmp screen. I can get into fastboot still
any help greatly appreciated. I have not used rsdlite in a while nor can I find the cdma_targa_9.8.2O-72_VZW-22_1ff.xml.zip file to manually doit through fastboot. (my own diagnoses but hey I'm an advnace noob with super cape and no superpowers)
yes my weaknesses are no-fear and stupidity based on not reading, reading and then reading a little more.
rp201 said:
Hoping someone has a minute to inform me of how to repair my bionc from vzw. I had safestrap 3.73 on and upgraded to safestrap 3.75 with rooted stock moto image from way back when. I saw a lineage 14.1 image install and thought what the heck. couldnt hurt. so I did a nandroid backup with compression to the external sdcard of all partions(securedata,system,data,webroot). did another backup to the internal partion. had the prefrered storage device as intenrnal memory. I then wiped system-data-cache-dalvik and left webtop and secure partion alone. I tried unlocking the bootloader from moto bye getting my device info in fastboot but fastboot did not understand the "oem" command. I remember I was able to boot multiple boots but it had to share the same kerenl so I firgured what the the heck. I could always safestrap back and restore if lineage os failed. my mistake. I assumed. I then found there was a file called moto-fastboot but not sure if it was any different than google's fastboot. before I get things anymore screwed up I thought I would kindly ask for someone to throw me a lifepreserver because I wanna get me and the brick outta the water.
anyhow now it tries to boot, reboots and gets a dead android bmp screen. I can get into fastboot still
any help greatly appreciated. I have not used rsdlite in a while nor can I find the cdma_targa_9.8.2O-72_VZW-22_1ff.xml.zip file to manually doit through fastboot. (my own diagnoses but hey I'm an advnace noob with super cape and no superpowers)
yes my weaknesses are no-fear and stupidity based on not reading, reading and then reading a little more.
Click to expand...
Click to collapse
Howdy! Sorry it's taken three months for your question to get any attention. Bionic forum's pretty dead, eh? I'm amazed it's still an officially supported Lineage device. Go team!
Sadly, the no one ever found a bootloader unlock, as a fellow informed me here two years ago. Unless some clever hacker happens upon a Bionic and decides to crack it for kicks, it's not likely to happen. But at least we have SafeStrap and Lineage!
You may know this already, but you didn't mention it in your post, so I'll go ahead and say: when installing a ROM like Lineage on the Bionic with SafeStrap, you need to install it on ROM Slot 1, not the Stock ROM Slot. I imagine that might be why you bricked your phone (I've done it myself a few times too ).
Now that I've given you the skinny on the Bionic's limitations, let's see if we can't get you back afloat. Whenever I bricked mine, I never used RDS Lite—I found a utility called House of Moto. You can find the home page here, but you'll need to create an account to see the important stuff and the downloads (you'll also need to install Java). But if you're more familiar with RDS Lite, feel free to use that instead
System images for the Bionic are hard to find nowadays. I seem to have found one link to an article with a direct download link to an update file at the bottom, which I'll link to here. Whether the update file is the same as an FXZ file RDS Lite/House of Moto requires, I'm not sure. Give it a try and see how it goes! If not, I may have a copy of the file on my old computer at my parents' house. If the linked update file doesn't work, I'll see if I can't get ahold of my image file.
Finally, if you do happen to get things up and running happily, I've got a list of optimizations that help Lineage run more smoothly.
Best of luck! :good:
While trying to make some modifications using QFIL, I erased the "laf" and "modem" partitions (both a and b) of my V40. Now I can't get into the download mode to reflash the phone using LGUP. The phone is using the Open Korean Android 10 firmware but any Android 10 version laf and modem partitions (a and b) will help me get into the download mode. I just need to flash those four partitions with Android 10 version.
If anyone could provide me the backup of those partitions, that will be a life saver for my LG V40. Many thanks!
Royaltiger said:
While trying to make some modifications using QFIL, I erased the "laf" and "modem" partitions (both a and b) of my V40. Now I can't get into the download mode to reflash the phone using LGUP. The phone is using the Open Korean Android 10 firmware but any Android 10 version laf and modem partitions (a and b) will help me get into the download mode. I just need to flash those four partitions with Android 10 version.
If anyone could provide me the backup of those partitions, that will be a life saver for my LG V40. Many thanks!
Click to expand...
Click to collapse
Hmmmm, no, I don't think so. For downlaod mode to work, there are a number or partitions that have to match, not just be 'Andoroid 10'. They should be the same variant and the same version (30a, 30b etc etc).
You can easily get these partitions yourself from the kdz. Follow this link for one of the many links for how to do this.
Another thing to keep in mind, the modem partition is a critical one, in that it carries your imei. Using a modem partition from someone else would be introducing their imei into your device. I don't know what would happen, it might just get overwritten with your imei, then again it might mess up your device because of the conflict.
The kdz extractor has been around for quite a few years, it would absolutely be a good idea to learn how to use it, for many reasons.
cheers
I am absolutely sure it is the ”laf” partitions since that were the partitions (a and b) that were erased by me affecting the download mode. As for extracting the partitions from the firmware, I have already tried that using KDZ extractor but it is of no help. I have tried even first extracting the DZ file and then extracting the “laf” partitions but the files have 0 bytes. Hence, useless.
As for IMEI, I only use the phone for WiFi to function as music player.
Can you extract the partitions from the OP_KR Android 10 firmware? I certainly am unable to.
Thanks much!
Royaltiger said:
I am absolutely sure it is the ”laf” partitions since that were the partitions (a and b) that were erased by me affecting the download mode. As for extracting the partitions from the firmware, I have already tried that using KDZ extractor but it is of no help. I have tried even first extracting the DZ file and then extracting the “laf” partitions but the files have 0 bytes. Hence, useless.
As for IMEI, I only use the phone for WiFi to function as music player.
Can you extract the partitions from the OP_KR Android 10 firmware? I certainly am unable to.
Thanks much!
Click to expand...
Click to collapse
follow this link for laf and abl for kor 30d. Good luck.
Thank you so much. Everything is back to normal.
Just wondering if you could also provide me the "boot_a" and "boot_b" partition images since I am unable to extract them from the firmware Android 10 OP_KR.
Thank you so much.
Royaltiger said:
Just wondering if you could also provide me the "boot_a" and "boot_b" partition images since I am unable to extract them from the firmware Android 10 OP_KR.
Thank you so much.
Click to expand...
Click to collapse
Follow this link to boot + twrp (already injected) in Kor Open 30f (that's the only version I seem to have). Boot a and b are identical, so it can be used for either.
I'd suggest though you post what issues you're having getting the extract utility to work, and try to fix those. It would make things much easier for you to be able to get any partition from any version any time you wanted.
the utility does work.
cheers
<from private email, pls don't do that as many can benefit from the answers>
<quote>
Hey,
Thanks for helping me with the “laf” partition for my LG V40 Sprint (flashed to Korean OP_KR). Just wondering if you know how to access the fastboot mode in this phone? ADB does not help as it simply boots the phone back normally.
According to XDA senior member “FreeSoftwareServers” post, you have to wipe the “laf” partition to access the fastboot. Well, I have erased the “laf” partitions using QFIL and that did not give me fastboot mode either.
I need to have it to root the device as well as disable AVB. Any thoughts?
Thanks!
<end quote>
Accessing fastboot happens 2 ways, but they are not 'equal' versions of fastboot.
1) you can get a 'watered down' version of fastboot by nuking the laf partition, and then accessing fastboot by going to download mode (not by going to fastboot normally). It's considered 'watered down' because the implementation of it differs from rom to rom, the worst implementation is the Kor version (it won't allow you to boot anything, it won't unlock the bootloader, it won't even switch slots). No version, by any of the roms, will allow unlocking the bootloader.
2) by flashing the v35 eng abl to one of the abl slots. This gives you the full version of fastboot, can unlock bootloader, switch slots, etc. But because it's version is Oreo, it can't boot anything that isn't Oreo based. What most people do is flash this to their unused abl slot, then use twrp to switch slots, and reboot to that unused slot, you'll automatically go to fastboot, do what u need to do, then use fastboot to switch to the other slot, fastboot reboot, and yer all set.
cheers
Your advice to keep the informative discussion public is well understood.
Now I have tried both ways to access the fastboot, as suggested by you. And neither of them work on the Korean firmwares. But what works is you erase the ”boot_a” partition using QFIL. Of course, you must backup the partition before erasing since it will be needed again.
With the wiped “boot_a“ partition, phone boots you right into Fastboot. After doing the fastboot needed changes, you can flash the earlier saved boot_a back to the partition using QFIL. Works like a charm every time (at least with Korean firmwares).
Royaltiger said:
Your advice to keep the informative discussion public is well understood.
Now I have tried both ways to access the fastboot, as suggested by you. And neither of them work on the Korean firmwares. But what works is you erase the ”boot_a” partition using QFIL. Of course, you must backup the partition before erasing since it will be needed again.
With the wiped “boot_a“ partition, phone boots you right into Fastboot. After doing the fastboot needed changes, you can flash the earlier saved boot_a back to the partition using QFIL. Works like a charm every time (at least with Korean firmwares).
Click to expand...
Click to collapse
if neither of them work for you, then you're doing something wrong. Guaranteed. They've worked for hundreds of others, thousands.
keep in mind, if you erase laf, then you have to use the same keys you would normally use to get to lat (download mode) to get (now) to fastboot (as I said before).
that means with phone off, hold vol up, plug in with usb to pc. Of course be sure the laf you nuked is the slot you are currently on.
And if you tried the v35 eng abl on the inactive slot, switched slots, and then rebooted, and it's not working for you... well, I wonder how all those people got their devices unlocked? because that's how you do it.
sorry but, pebkac. There's no doubt they work.
AsItLies said:
I'd suggest though you post what issues you're having getting the extract utility to work, and try to fix those. It would make things much easier for you to be able to get any partition from any version any time you wanted.
the utility does work.
cheers
Click to expand...
Click to collapse
At your advice, I again tried to extract the partition files from a KDZ file (OP_KR Android 10) and the results are the same i.e., the extracted partition files are 0 kb in size. I am following the procedure down to T. The DZ file gets extracted from KDZ without any problem. But when I try to pull the partition files using the extractor tool, the resulting files are useless as they are 0 kb in size.
I am attaching the screen shot for your analysis.
It will be of immense help if I could be able to extract the partition files myself successfully.
Royaltiger said:
At your advice, I again tried to extract the partition files from a KDZ file (OP_KR Android 10) and the results are the same i.e., the extracted partition files are 0 kb in size. I am following the procedure down to T. The DZ file gets extracted from KDZ without any problem. But when I try to pull the partition files using the extractor tool, the resulting files are useless as they are 0 kb in size.
I am attaching the screen shot for your analysis.
It will be of immense help if I could be able to extract the partition files myself successfully.
Click to expand...
Click to collapse
I've never used the gui version of the extractor, only the cli version under linux, so can't help there. I'd suggest searching for an xda thread discussing the gui.
cheers
AsItLies said:
I've never used the gui version of the extractor, only the cli version under linux, so can't help there. I'd suggest searching for an xda thread discussing the gui.
cheers
Click to expand...
Click to collapse
Now I totally understand your success because I have read at Howtek that the Windows version of extractor does not work on newer KDZ firmwares. Nevertheless I am very grateful to your earlier extracted files.
Just once more: May I trouble you to let me have the extracted partitions (laf, abl and boot) from the Korean firmware for LG V50 (Android 10): V500NO20y_00_OPEN_KR_OP_0115.KDZ. I need these files for a project that I am undertaking on LG V50. That way I will covered in case something goes South.
Thank you so much for your help.
Royaltiger said:
Now I totally understand your success because I have read at Howtek that the Windows version of extractor does not work on newer KDZ firmwares. Nevertheless I am very grateful to your earlier extracted files.
Just once more: May I trouble you to let me have the extracted partitions (laf, abl and boot) from the Korean firmware for LG V50 (Android 10): V500NO20y_00_OPEN_KR_OP_0115.KDZ. I need these files for a project that I am undertaking on LG V50. That way I will covered in case something goes South.
Thank you so much for your help.
Click to expand...
Click to collapse
This is something you can figure out for yourself. There's a great deal of documentation and guides available. I managed to follow them and made the cli version work about a year or so ago. I've had hd crashes and laptop replacements since then. I'm not even sure the HD I had with that on it is still in my possession.
MODERATOR EDIT: CERTAIN CONTENTS OF THIS POST WERE REMOVED TO MAKE IT IN ACCORDANCE WITH THE FORUM RULES
Hey guys,
I have removed some posts from this thread which I felt were getting out of line from the way of a civilized discussion. Follow the FORUM RULES. Rules that were broken:
2.1 Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please don't direct profanity, sexually explicit language or other offensive content toward Members or their work. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street.
2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
Regards,
theimpulson
Forum Moderator / Recognized Developer / Developer Relations