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
Related
where can i find motorola custom fastboot commands?
i'm stuck on 4.4.3 with CWM.
i want to install stock 4.4.4 but i can't because of CWM.
and i can't remove CWM because motorola only provides 4.4.2 which can't be flashed over 4.4.3
I'm figuring that if RDS-lite or whatever out-of-nowhere program can do that, it does so using fastboot commands. and that list of commands may be available somewhere.
anyone have any idea?
thanks.
there are no "custom motorola fastboot commands".
RSDLite doesn't use mfastboot
What model X do you have?
Have you tried looking at both -> http://sbf.droid-developers.org/phone.php?device=0 and http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 for the SBF you need?
You can use mfastboot to flash an older recovery.img. It SHOULD work, however future OTA may fail due to an incorrect version of recovery.
KidJoe said:
there are no "custom motorola fastboot commands".
RSDLite doesn't use mfastboot
What model X do you have?
Have you tried looking at both -> http://sbf.droid-developers.org/phone.php?device=0 and http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 for the SBF you need?
You can use mfastboot to flash an older recovery.img. It SHOULD work, however future OTA may fail due to an incorrect version of recovery.
Click to expand...
Click to collapse
What does RDSlite uses?
gcbxda said:
What does RDSlite uses?
Click to expand...
Click to collapse
Install RSD-Lite. Download zip file from above link and unzip it. Boot your device to Bootloader and connect to PC via USB. Open Rsd-Lite and Select XML file from unzipped folder. Click "Start". RSD-Lite will automatically install for you.
kenosis said:
Install RSD-Lite. Download zip file from above link and unzip it. Boot your device to Bootloader and connect to PC via USB. Open Rsd-Lite and Select XML file from unzipped folder. Click "Start". RSD-Lite will automatically install for you.
Click to expand...
Click to collapse
I'm more interested in what RDSlite uses to talk to the phone. Any idea about that? thanks.
gcbxda said:
I'm more interested in what RDSlite uses to talk to the phone. Any idea about that? thanks.
Click to expand...
Click to collapse
routines built into the exe and dll's of the app.
Seriously, its not a "front end" or "gui" to mFastboot or other tool. Its its own tool. Just like the software updater that is part of the Motorola Device Manager package is its own tool.
RSDLite is basically Moto's equivalent to Samsungs Odin.
KJ said:
RSDLite is basically Moto's equivalent to Samsungs Odin.
Click to expand...
Click to collapse
which i also failed to find any info about.
how do they talk with the phone?
a binary protocol? is there anyone trying to decode that?
i have a windows VM with RDSlite now... one of the advantages of those two companies releasing a rogue program like that, they don't have to give support if it burns down your house and kill your cat, but i also do not have to agree to not reverse engineer it ...if it was released by those companies and not some chinese gov spy agencie
Dunno... I use them and they work. Good enough for me. ?
Not a conspiracy theorist here. ?
KJ said:
Dunno... I use them and they work. Good enough for me. ?
Not a conspiracy theorist here. ?
Click to expand...
Click to collapse
lol. just because i'm paranoid, it does not mean they aren't after me!
i was sure i wrote more to that reply than just the joke... sigh, either i'm getting more retarded by the hour or the CIA did it!
anyway, joke aside, think about it:
if there is a secret protocol that the manufacturer implements on their fastboot to do things like downgrade without any hassle and probably much more, like flashing modem and other parts that we don't have access normally, why the heck should we not investigate it?!
my curiosity is less about paranoia (even though i'm 99% sure odin and rdslite are the work of a joint china-us spy effort that patches images on the fly to include backdoors) and more about unlocking more from our hardware.
i think in the end i'm still pissed off that i carry a computer more powerful than my desktop but that can only run a silly UI because i have access to nothing.
gcbxda said:
anyway, joke aside, think about it:
if there is a secret protocol that the manufacturer implements on their fastboot to do things like downgrade without any hassle and probably much more, like flashing modem and other parts that we don't have access normally, why the heck should we not investigate it?!
Click to expand...
Click to collapse
Well, first off, the only difference between fastboot.exe from the Android SDK and moto's patched version (aka mFastboot) is the ability to flash larger files. The system partitions on Moto phones have been bigger and therefore the mFastboot was created. Standard fastboot will tell you the file size is too great when flashing system.img to Moto phones and that is why mFastboot is needed.
Using fastboot or mfastboot you can downgrade SOME PARTS "without any hassle." However, there are security measures on the phones which prevent downgrading certain parts (think S-ON vs S-OFF on HTC). Moto doesn't allow you to downgrade the GPT.BIN or the contents of Motoboot.img. But you could flash older logo.bin, recovery.img, boot.img, system.img, and modem/radio files. that being said, there are compatibility and other issues that pose other problems when you downgrade.
Fastboot and mFastboot does allow flashing the modems and other parts. The moto X does have a /persistent partition which is not contained in the SBF. But if unlocked & rooted, we can modify it (add/remove files).
gcbxda said:
my curiosity is less about paranoia (even though i'm 99% sure odin and rdslite are the work of a joint china-us spy effort that patches images on the fly to include backdoors) and more about unlocking more from our hardware.
Click to expand...
Click to collapse
Well, RSDlite is a moto tool, and Odin is a Samsung tool.
as for "China-US Spy effort" I'm not even going to go there, other than saying that IS paranoia.
Feel free to sit down, decompile them, analyze them. If you find PROOF anything, post it.
gcbxda said:
i think in the end i'm still pissed off that i carry a computer more powerful than my desktop but that can only run a silly UI because i have access to nothing.
Click to expand...
Click to collapse
Feel free to sit down and create your own port of Android... or take the time to program your own OS. But these are not meant to be "totally open" devices that the user can do anything they want on it. There are some proprietary components. There are some limits.
KidJoe said:
Well, first off, the only difference between fastboot.exe from the Android SDK and moto's patched version (aka mFastboot) is the ability to flash larger files. The system partitions on Moto phones have been bigger and therefore the mFastboot was created. Standard fastboot will tell you the file size is too great when flashing system.img to Moto phones and that is why mFastboot is needed.
Using fastboot or mfastboot you can downgrade SOME PARTS "without any hassle." However, there are security measures on the phones which prevent downgrading certain parts (think S-ON vs S-OFF on HTC). Moto doesn't allow you to downgrade the GPT.BIN or the contents of Motoboot.img. But you could flash older logo.bin, recovery.img, boot.img, system.img, and modem/radio files. that being said, there are compatibility and other issues that pose other problems when you downgrade.
Fastboot and mFastboot does allow flashing the modems and other parts. The moto X does have a /persistent partition which is not contained in the SBF. But if unlocked & rooted, we can modify it (add/remove files).
Well, RSDlite is a moto tool, and Odin is a Samsung tool.
as for "China-US Spy effort" I'm not even going to go there, other than saying that IS paranoia.
Feel free to sit down, decompile them, analyze them. If you find PROOF anything, post it.
Feel free to sit down and create your own port of Android... or take the time to program your own OS. But these are not meant to be "totally open" devices that the user can do anything they want on it. There are some proprietary components. There are some limits.
Click to expand...
Click to collapse
lol, stop paying attention to the joke man
and not talking about mfastboot, talking about how RDSlite talks to the phone. if that does MORE than fastboot/mfastboot, why shouldn't we found out how? that's basic curiosity, despite paranoia.
and i did try to install the 4.4.2 they provided over 4.4.3, but there is no point in allowing to install recovery or whatever if you need a new partition layout everytime. so allowing downgrading something but not gpt is the same as nothing.
Hello there XDA members, recently I found a thread by konsolen regarding a root method which involves unplugging the USB cable from the computer at 9% of the download mode screen.
http://forum.xda-developers.com/showpost.php?p=63449717&postcount=2
I have personally risked bricking my device and can confirm you can list the files in the system partition following those instructions. Don't really know what to do from there, so I went ahead and downloaded the KDZ and TOT extractor tool from the G2 forum and extracted the stock system partition from the unofficial ZV9 TOT, and uploaded them here.
https://mega.nz/#!vNhzxDhZ!D4xXMG0lP56tozHBLo9cuBiKlmcf1qIr2iToSqm7GM4
I also included the ZAF and Boot bin files extracted from the TOT with the hopes that someone can edit them to make a seamless root for the G4. I included the ZAF because another member, Agimax made a flashable partition with access to fastboot mode for the G4 here. Hope you see this post pal.
http://forum.xda-developers.com/showpost.php?p=64167865&postcount=330
That's about as far as I got on my own. Really hoping root comes to MM soon, as of now I'm stumped. Also, I don't know if root injection would work for this version of android, hopefully it does. I will attempt this tomorrow(have to set up a VM with Linux first).
G41LAH said:
Hello there XDA members, recently I found a thread by konsolen regarding a root method which involves unplugging the USB cable from the computer at 9% of the download mode screen.
http://forum.xda-developers.com/showpost.php?p=63449717&postcount=2
I have personally risked bricking my device and can confirm you can list the files in the system partition following those instructions. Don't really know what to do from there, so I went ahead and downloaded the KDZ and TOT extractor tool from the G2 forum and extracted the stock system partition from the unofficial ZV9 TOT, and uploaded them here.
https://mega.nz/#!vNhzxDhZ!D4xXMG0lP56tozHBLo9cuBiKlmcf1qIr2iToSqm7GM4
I also included the ZAF and Boot bin files extracted from the TOT with the hopes that someone can edit them to make a seamless root for the G4. I included the ZAF because another member, Agimax made a flashable partition with access to fastboot mode for the G4 here. Hope you see this post pal.
http://forum.xda-developers.com/showpost.php?p=64167865&postcount=330
That's about as far as I got on my own. Really hoping root comes to MM soon, as of now I'm stumped. Also, I don't know if root injection would work for this version of android, hopefully it does. I will attempt this tomorrow(have to set up a VM with Linux first).
Click to expand...
Click to collapse
Good luck
G41LAH said:
Hello there XDA members, recently I found a thread by konsolen regarding a root method which involves unplugging the USB cable from the computer at 9% of the download mode screen.
http://forum.xda-developers.com/showpost.php?p=63449717&postcount=2
I have personally risked bricking my device and can confirm you can list the files in the system partition following those instructions. Don't really know what to do from there, so I went ahead and downloaded the KDZ and TOT extractor tool from the G2 forum and extracted the stock system partition from the unofficial ZV9 TOT, and uploaded them here.
https://mega.nz/#!vNhzxDhZ!D4xXMG0lP56tozHBLo9cuBiKlmcf1qIr2iToSqm7GM4
I also included the ZAF and Boot bin files extracted from the TOT with the hopes that someone can edit them to make a seamless root for the G4. I included the ZAF because another member, Agimax made a flashable partition with access to fastboot mode for the G4 here. Hope you see this post pal.
http://forum.xda-developers.com/showpost.php?p=64167865&postcount=330
That's about as far as I got on my own. Really hoping root comes to MM soon, as of now I'm stumped. Also, I don't know if root injection would work for this version of android, hopefully it does. I will attempt this tomorrow(have to set up a VM with Linux first).
Click to expand...
Click to collapse
Fastboot mode flashing partiton wont work
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:
Just got a new in the box unit. It was made in 7/2019 and it arrived with Pie installed even though these originally came with Oreo. Is there any way to downgrade mine and, if so, how to do it and were to get a firmware file? Thanks for your help.
Unless I'm mistaken, this thread will tell you how: https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and this thread contains the links to the KDZs (LG speak for stock ROMs): https://forum.xda-developers.com/lg-v40/development/v40-firmware-links-ainzooalgown-t3940600
[NG]Owner
NGOwner said:
Unless I'm mistaken, this thread will tell you how: https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and this thread contains the links to the KDZs (LG speak for stock ROMs): https://forum.xda-developers.com/lg-v40/development/v40-firmware-links-ainzooalgown-t3940600
[NG]Owner
Click to expand...
Click to collapse
Thanks. I do see those threads and those definitely help. But I am still not clear if I can downgrade. Perhaps it is because I am new to LG phones from Samsung and I know that on some Samsung devices, once you go forward you may not be able to go back. So I am just wondering about all that (along with if I can unlock the bootloader, install TWRP, and root on the model 405QA that I have). Cheers!
Using LGUP 1.14 on DEV mode will let you downgrade, matter is flashing cause phones themselves seem not have any issues by downgrading. Personally I've downgraded both my v40 and my older g7 a couple of times, no probs.
smariob said:
Using LGUP 1.14 on DEV mode will let you downgrade, matter is flashing cause phones themselves seem not have any issues by downgrading. Personally I've downgraded both my v40 and my older g7 a couple of times, no probs.
Click to expand...
Click to collapse
Thanks so much for your time and help. I have downloaded LGUP and installed according to this thread <https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858>. When I try to run it, Win10 asks if it is ok, I say yes, and then nothing else happens. Hmmm. I believe this is LGUP 1.16.0.3. No idea what's up. I have the phone attached and in download mode as described here <https://droidrecovery.com/lg-v40-thinq-recovery-mode/>. Grrr.
Try this LG UP version https://forum.xda-developers.com/showpost.php?p=76995781&postcount=26 set the DLL on DEV mode.
As for unlock bootloader question on your other thread, yep so far it's the easiest method to do it. ADVICE: If you haven't touched anything yet I suggest take a bakup of your partitions via QFIL. So if you mess up something (most likely not but you never know) you will be able to restore everything as it was when you got the phone.
smariob said:
Try this LG UP version https://forum.xda-developers.com/showpost.php?p=76995781&postcount=26 set the DLL on DEV mode.
As for unlock bootloader question on your other thread, yep so far it's the easiest method to do it. ADVICE: If you haven't touched anything yet I suggest take a bakup of your partitions via QFIL. So if you mess up something (most likely not but you never know) you will be able to restore everything as it was when you got the phone.
Click to expand...
Click to collapse
Oh thanks so much! That version of LGUP seems to work (after I manually did some file copying that had permission problems from the scripts). I presume that to downgrade - assuming I have a compatible .KDZ - is to use the FOTA upgrade option?
I will look into the backup as you suggest. As a newbie on these devices, there is alot to learn. Cheers
smariob said:
Try this LG UP version https://forum.xda-developers.com/showpost.php?p=76995781&postcount=26 set the DLL on DEV mode.
As for unlock bootloader question on your other thread, yep so far it's the easiest method to do it. ADVICE: If you haven't touched anything yet I suggest take a bakup of your partitions via QFIL. So if you mess up something (most likely not but you never know) you will be able to restore everything as it was when you got the phone.
Click to expand...
Click to collapse
Ok, I see the phone in QFIL. Under the tools menu, I see QCN Backup/Restore. Is this the backup to which you refer? I don't see anything else that looks promising. Sorry for all of my newbie questions.
So, if you are going to do the back up use this guide: https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-partitions-flash-abl-t-mo-t4051249
Follow steps 1 to 10, Backing up _a partitions will do the job _b patitions will be mirrored from those when restore. Data is not mandatory to back up as it will take much time to read the whole partition. Another tip, rename your backed up files so you can identify them properly later.
Then when you are ready you can play with LG UP most of the time you will like to use Partition DL. Use refurbish only to go stock. FOTA is for updating between versions without losing data (nice if you crossflash/loss the ability to OTA on the phone)
smariob said:
So, if you are going to do the back up use this guide: https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-partitions-flash-abl-t-mo-t4051249
Follow steps 1 to 10, Backing up _a partitions will do the job _b patitions will be mirrored from those when restore. Data is not mandatory to back up as it will take much time to read the whole partition. Another tip, rename your backed up files so you can identify them properly later.
Then when you are ready you can play with LG UP most of the time you will like to use Partition DL. Use refurbish only to go stock. FOTA is for updating between versions without losing data (nice if you crossflash/loss the ability to OTA on the phone)
Click to expand...
Click to collapse
I cannot thank you enough for your time and help. I will read up on all this and continue tomorrow morning. Cheers.
smariob said:
So, if you are going to do the back up use this guide: https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-partitions-flash-abl-t-mo-t4051249
Follow steps 1 to 10, Backing up _a partitions will do the job _b patitions will be mirrored from those when restore. Data is not mandatory to back up as it will take much time to read the whole partition. Another tip, rename your backed up files so you can identify them properly later.
Then when you are ready you can play with LG UP most of the time you will like to use Partition DL. Use refurbish only to go stock. FOTA is for updating between versions without losing data (nice if you crossflash/loss the ability to OTA on the phone)
Click to expand...
Click to collapse
Wow! That is alot of partitions and a lengthy backup chore - even without including the _b partitions. You were 100% correct that renaming each file as you go makes this easier. I used the LUN#_the partition-label.bin as I discovered that some labels were re-used in different LUN.
I never would have figured this out without your help. Thanks.
After a brief rest I will move on and try to unlock the bootloader as described here <https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207>.
It's great to know that, once you've done that UL BL would be a piece of a cake.
smariob said:
It's great to know that, once you've done that UL BL would be a piece of a cake.
Click to expand...
Click to collapse
Thanks so much! You might note I have posted in the other thread about troubles getting unlocked. I seem to have successfully sent the v35 bootloader to the phone. I have the QFIL log showing that. But when I go to fastboot mode and try the unlock command, it fails with unknown command. After restoring/sending the backup of the original partition, I tried issuing the same unlock command (not expecting it to work since I should have been back to the original pie bootloader) and I get the exact same error. This makes me wonder if the v35 bootloader is actually getting installed properly. The phone is on the most recent Pie (QA20e) and seems to boot and run fine - even right after I send the v35 bootloader. There were comments that using this bootloader with Pie might have problems and I have never had any so far. So again, I am wondering if the v35 is actually getting into place. A real mystery to me. Thanks!
whitedavidp said:
Wow! That is alot of partitions and a lengthy backup chore - even without including the _b partitions. You were 100% correct that renaming each file as you go makes this easier. I used the LUN#_the partition-label.bin as I discovered that some labels were re-used in different LUN.
I never would have figured this out without your help. Thanks.
After a brief rest I will move on and try to unlock the bootloader as described here <https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207>.
Click to expand...
Click to collapse
In my case, it turned out that the phone was active on the B slot. So I took backups of those partitions as well, flashed the V35 bootloader into B, performed the unlock, re-flashed the Pie bootloader. When I reboot into normal mode, I now see an unlocked warning and it took a very long time for the phone to get started and prompt me to start all over with my Android install. Before I do that I am trying to restore the backup I made of the userdata partition to see if that spares me the whole setup thing. Thanks to all.
Yeah you've made it at least. Good one on figure out B slot was active. Now you're able to go custom roms or just go root.
smariob said:
Yeah you've made it at least. Good one on figure out B slot was active. Now you're able to go custom roms or just go root.
Click to expand...
Click to collapse
Again, thanks so much for all of you help and encouragement. From my pre-purchase research I had anticipated that I could do a dev unlock of the bootloader quite easily. I have rooted with Magisk now and am moving on to see what I can do. Cheers.
smariob said:
Using LGUP 1.14 on DEV mode will let you downgrade, matter is flashing cause phones themselves seem not have any issues by downgrading. Personally I've downgraded both my v40 and my older g7 a couple of times, no probs.
Click to expand...
Click to collapse
Thanks for all of your help and sorry for all the questions.
I am just wondering if you are able to use TWRP/Magisk root on the downgraded v40? In the TWRP thread it indicates that it requires Pie firmware be installed. If I cannot use TWRP/Magisk root on Oreo, then I will not bother trying to downgrade.
Again, thanks so much!
Now that you mention it. V40 TWRP is meant to use with pie... Will not boot on Oreo. I think there are workarounds for that if it's mandatory for you to be in Oreo, but not personally tested'em.
smariob said:
Now that you mention it. V40 TWRP is meant to use with pie... Will not boot on Oreo. I think there are workarounds for that if it's mandatory for you to be in Oreo, but not personally tested'em.
Click to expand...
Click to collapse
Thanks. Certainly not mandatory. So will stick with Pie for now anyway. Again, thanks so much.
Can someone please with ATT android Q build 30E send me both A and B boot.img
nikothebarber said:
Can someone please with ATT android Q build 30E send me both A and B boot.img
Click to expand...
Click to collapse
Niko, yer asking everywhere for this, but u already have it right? Your phone is att updated to 30e right?
So, just like anyone else would have to do, use qfil and get it? I mean, if you're going to root and get twrp on the device, you're going to have to install and learn to use, qfil.
As I mentioned in another thread, if you post your boot_a image, I'll twrp patch it for u and post it back.
Do you need help using / installing qfil?
No I believe im mismatched I accidentally flashed a and b boot ing ive got it working but boot imgg is older then 30e, I get the error on start up saying current version is not available for user can't find match carrier NT code FFFFFF: 84
nikothebarber said:
No I believe im mismatched I accidentally flashed a and b boot ing ive got it working but boot imgg is older then 30e, I get the error on start up saying current version is not available for user can't find match carrier NT code FFFFFF: 84
Click to expand...
Click to collapse
Okay, since you did an OTA update (right?) then the other boot image would be the previous version OS for att. Maybe to get the newest one u can do the update again? (I don't know, I"m asking, I don't have a carrier specific phone so no way to test that).
Also, that NT error code is usually only going to occur when u 'cross flash'. Which makes me wonder... what boot partition are u really using? It sounds like it **may** not even be an att one?
I better understand your situation now, sure does make it obvious why you want to do a backup before any modifications right? sorry, I'm sure you've learned that lesson now, but maybe others can benefit from your tough lesson.
Here's the first thing I'd do if u; Make A COPY OF EA boot partition, as they are now. At least you'll have a backup of ea one from here (whatever they happen to be).
One of the easiest ways to do that would be (assuming you have twrp injected), would be to boot recovery, connect to pc with usb cable, and type in 'adb shell'.
Then use the following dd commands (modify for your directory structure on sd card);
dd if=/dev/block/bootdevice/by-name/boot_b of=/external_sd/backup/current_att_boot_b.img
this assumes you have a directory on your sd card called 'backup'. Replace it with whichever you may have. Do the same for boot_a also (change boot_b to boot_a), and change the output name to reflect what you're backing up.
So with these backups, you **could** decide to copy your boot_b backup tot he boot_a partition and see what happens? I mean it sounds like you're not sure what is on either one of your boot partitions, so trying that may be the only way to have some idea of what's there.
*If** it turns out that the device boots okay with boot_b copied over, then at least you'll have a boot partition that could be twrp injected and not have the nt_error code?
good luck
I mixed up the active side and replaced one with the other already . I never did OTA and unfortunately it does not work. I have back ups now of boot a and b with qfil, my firmware is 30e and boot img is 30b. I need boot.img 30E
I've got 30e boot.bin can.you add twrp to it
nikothebarber said:
I've got 30e boot.bin can.you add twrp to it
Click to expand...
Click to collapse
Well I have no way of knowing which one is 30e and which is att prior version. But I can tell you the 30e_a u posted here is identical to the 30e_a posted in this thread.
cheers