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.
Related
I have a Verizon DE moto x that has twrp recovery. My active display keeps getting stuck when I get a notification, so I think I need to flash (or however it must be done) a fresh rooted stock copy. Where can I find info on how to do this?
Sent from my XT1060
Since you aren't downgrading or anything, you won't have to worry about the bootloader, so just grab the Verizon 4.4 SBF and follow the instructions
mastarifla said:
Since you aren't downgrading or anything, you won't have to worry about the bootloader, so just grab the Verizon 4.4 SBF and follow the instructions
Click to expand...
Click to collapse
What is the difference between flashing firmware and flashing factory images?
Cozume said:
What is the difference between flashing firmware and flashing factory images?
Click to expand...
Click to collapse
As far as I know, the only verifiable "factory images" are the Developer Edition ones that Moto hosts on their personal website.
The SBF may/may not be official factory images. However, they are essentially accepted by the community as the next best thing, mainly because the zips follow the rules set by RSD Lite (Insider Moto Tool) and help prevent bad flashes/user error.
Flashing the SBF firmware manually (via fastboot commands) can raise a few problems of its own, if you don't know what you are doing you can cause serious damage to your device, which is why it is safer to use something like RSD Lite. If you are manually flashing, there is no "check" to verify that you installed them in the correct order or that you flashed all the files without missing anything. Therefore, it is much more risky, please know what you are doing if you plan on flashing this way.
mastarifla said:
As far as I know, the only verifiable "factory images" are the Developer Edition ones that Moto hosts on their personal website.
The SBF may/may not be official factory images. However, they are essentially accepted by the community as the next best thing, mainly because the zips follow the rules set by RSD Lite (Insider Moto Tool) and help prevent bad flashes/user error.
Flashing the SBF firmware manually (via fastboot commands) can raise a few problems of its own, if you don't know what you are doing you can cause serious damage to your device, which is why it is safer to use something like RSD Lite. If you are manually flashing, there is no "check" to verify that you installed them in the correct order or that you flashed all the files without missing anything. Therefore, it is much more risky, please know what you are doing if you plan on flashing this way.
Click to expand...
Click to collapse
Just to clarify. Using the rsd lite method will not mess with the boot loader nor the /media folder correct?
Sent from my XT1060
Swimboy46163 said:
Just to clarify. Using the rsd lite method will not mess with the boot loader nor the /media folder correct?
Sent from my XT1060
Click to expand...
Click to collapse
Depends on if you edit the xml file or not. The bootloader will be flashed by default and data will be wiped by default. It's been a while since I've used RSD but I think when it wipes /data it wipes everything (i.e. including /media). That being said, you could always take those steps out of the xml file.
piccit said:
Depends on if you edit the xml file or not. The bootloader will be flashed by default and data will be wiped by default. It's been a while since I've used RSD but I think when it wipes /data it wipes everything (i.e. including /media). That being said, you could always take those steps out of the xml file.
Click to expand...
Click to collapse
Will this work? http://www.youtube.com/watch?v=gDJvZe7_s0E
While yes it will work I would suggest learning HOW it works, take a look at the steps it goes through and see what is happening, don't rely on these kinds of tools, because they become useless if something bad happens. However, if you look at and modify the XML, it is literally only taking out a few lines of code, but if you want an automated version, then use the tool.
mastarifla said:
While yes it will work I would suggest learning HOW it works, take a look at the steps it goes through and see what is happening, don't rely on these kinds of tools, because they become useless if something bad happens. However, if you look at and modify the XML, it is literally only taking out a few lines of code, but if you want an automated version, then use the tool.
Click to expand...
Click to collapse
I can never get adb to run in command prompt. Mostly because windows is different from Mac.
Sent from my XT1060
Swimboy46163 said:
I can never get adb to run in command prompt. Mostly because windows is different from Mac.
Click to expand...
Click to collapse
I have a Windows 7 machine and I can never get adb to run in a command prompt, either. I have a driver problem.
I can only use mfastboot to do anything unless I can fix my driver problem.
Swimboy46163 said:
I can never get adb to run in command prompt. Mostly because windows is different from Mac.
Sent from my XT1060
Click to expand...
Click to collapse
There are a few tutorials for setting it up correctly, I'm not sure that you need the full SDK in order to do this, but I guess it's nice to have anyways. Try reading up a bit about it, I'm sure you can get it running in no time , after that you'll be much more familiar with these kinds of things.
OP, are you on 4.4? if so, then you don't have to worry about the bootloader. Just download the most current factory image from Motorola. The instructions for flashing the factory images are on their website. Go to www.motorola.com, go to the bottom of the page and click on "Developers". Its the same page you went to in order to get the bootloader unlock code. You have to request the factory image, and Motorola will email you a link, or there's several links to it floating around here.
The factory image will have the same bootlaoder version as you have installed as long as your are flashing the same OS version. It won't relock your bootloader, but you will lose root until you flash TWRP recovery. as far as the media partition, just back up your sdcard partition to your computer before flashing the factory image.
Here's the steps:
1. Plug your MX into the computer and back up all files you want to keep (photos, music, videos, downloads, etc...)
2. Download the 4.4 factory image from the source of your choice (If you don't get it from Motorola, make 100% sure you are downloading the correct file)
3. Make sure you have ADB and fastboot set up properly (and make sure you use the motorola fastboot (mfastboot.exe), bot the Google version)
4. Unzip the factory image and place all the files into the same folder as your adb and fastboot files.
5. Boot your MX into fastboot mode (power off, then hold all three buttons for approx 5 seconds and release)
6. Flash the files using mfastboot, and following the order provided in the included xml file.
7. Reboot.
8. Set your phone up and then restore the files you backed up to your computer
9. If you want root, then you will have to go back to fastboot and flash the TWRP recovery and let it install SuperSU.
10. Finally, PLEASE, make a nandroid back up once you have everything set up and before you make any alterations to it.
Thanks guys! The toolkit actually did the trick for me I was being lazy today lol
Sent from my XT1060 using Tapatalk
Swimboy46163 said:
Thanks guys! The toolkit actually did the trick for me I was being lazy today lol
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Thanks buddy for ruining it for everybody. If you would stop being on your rag and complaining like a girl none if this would have happened. Look at what you did little girl.
MOTO X Slapped
Hello,
Guys i have got Moto X XT1052 from a friend for few days. To mainly fix it. Actually, whenever i turn phone on. It keeps on crashing all apps, like Unfortunately, Launcher has stopped, calender and so on. It's not allowing me to touch anywhere else. So i would like to restore it. I checked all threads and found fine solution for flashing. I can do it. But those who uploaded ROMs on filefactory, it's kinda old. And downloading speed is really slow. Even when my net speed is double of it. I should get 300 KB/s some. But i am getting 50KB/s from their site. So i need help on this. If anyone can upload that ROM(XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip) on any other site like mediafire, Google files or torrent. I will really appreciate it. Please i urgently need it. Let me know if anything else to be done too. Because on current bootloader showing Device is Lock. And i saw youtube videos, most of them had Device is unlock. I am using this method, please take a look and let me know. Thanks. http://forum.gsmhosting.com/vbb/f78...to-x-2nd-gen-firmware-flashing-guide-1877668/
You can try to look here:
https://cloud.mail.ru/public/a083d0bb5e97/Motorola/XT1052/
https://cloud.mail.ru/public/64a43f0fcc1e/Moto_X/XT1052/
+
4.4.4 Retail GB (XT1052_RETAIL-GB_4.4.4_KXA21.12-L1.26_56_cid7_CFC_1FF.xml.zip)
4.4.4 Retail DE (XT1052_RETAIL-DE_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF.xml.zip)
4.4.4 Retail EU (XT1052_RETAIL-EU_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF.xml.zip)
http://forum.xda-developers.com/showthread.php?t=2976596
Here you go - https://mega.co.nz/#!U8NkgQqA!2yUsrJlNp0j_8ttzjJmHS4C4hh9cQ__vXtNKfmlm8cg
Sent from my Moto X using XDA Free mobile app
Guys, stuck in mid. Can you tell me, that do i need to unlock device first to get back to stock ROM? I tried manual flashing and RSD method too. But both failed to do anything. All apps still crashing. :l Please help me on this? New for Moto X. :l Thanks.
DarKrypton said:
Guys, stuck in mid. Can you tell me, that do i need to unlock device first to get back to stock ROM? I tried manual flashing and RSD method too. But both failed to do anything. All apps still crashing. :l Please help me on this? New for Moto X. :l Thanks.
Click to expand...
Click to collapse
First you dont need to unlock or lock your bootloader. Have you already tried to just go into recovery mode and factory reset the phone? How did the error start? What did your friend try to do, when he got the error first? What is the EXACT error message you get, while flashing?
Sent from my XT1052 using XDA Free mobile app
N00BY0815 said:
First you dont need to unlock or lock your bootloader. Have you already tried to just go into recovery mode and factory reset the phone? How did the error start? What did your friend try to do, when he got the error first? What is the EXACT error message you get, while flashing?
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
When i do factory option in recovery mode, it just boot up phone normally. And then it shows "Unfortunately, the process com.google.process.gapps has stopped". Then it keeps poping up with more crashes, like launcher, google play services. It hardly let me touch somewhere else. And if i tap "Ok" quickly, phone just shut down. Even in recovery mode, i tried selecting "Recovery" option, and it shown me "Boot up failed". And actually my friend don't know much about phones and all this. He said it just started happening. :l Maybe he installed some weird app. And i don't get any error while flashing. Everything went fine. But when i check phone it doesn't change anything else. Same as old. Even when i erased all user data. Will just erasing data will fix it? Then after that i can do full stock ROM flashing.
Why i am not getting back to stock guys. Everything going fine. Just i checked a thread, where a guy said he is getting that "Variable not supported" something. I am getting same thing. So what can i do? :l Please help me to get back to stock ROM. I really need to fix it. Thanks.
Try motofirmware.center to try and see if they have the ROM you're looking for. I went to this site for the stock ROM for my XT1060 Developer Edition and was able to find it there. It saved me when I messed up my phone earlier this week. When you flash the stock ROM using the RSDLite program, it will do a wipe on your phone as it flashes it to your phone. When you boot up the phone after flashing the stock ROM, your programs should reinstall just fine on the phone once you log on to your Google Play account.
Cindy
DarKrypton said:
So.. i am confused with all this. Maybe you can help me with this. Thanks. I hope you don't mind.
Click to expand...
Click to collapse
We don't know what your doing, what you tried, or why it didn't work, because we can't see you or what your doing.
You need to post in a coherent straight forward manor.
I would use the manual version, so you can see what errors occur more easily.
Make sure you have the right files for your version, and understand this:
http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
copy and paste the terminal output here using code tags.
Click to expand...
Click to collapse
You have been asked multiple times for the exact error messages. We don't know why your computer wont work... But your computer pretty much tells you each time with a specific message. You need to give us those messages.
Consider the fact that there MAY be someone here who doesn't care about you or your phone, but knows the answer. If you make it easy that person MAY help you. If you post paragraph after paragraph of text describing the error message, rather then the 1 line error message they probably wont read. Be as direct as possible, show us what you have done (I didn't really flow many of you links, why should we have to chase down this information to give you free tech support?)
Like this:
I am trying to fix a phone for a friend. Upon boot I get continuous force closes from a variety of different apps. I am left with a crashed an unusable system.
I have tried to flash _____ rom using _____ tool, but recivied the following error message
Code:
word for word error message
I found this thread: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 on returning to stock using RDS light, and used
RETAIL-US_4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip from http://motofirmware.center/files/category/9-ghost/
There was an error durring fasboot, and there seem to be no changes to the phone.
Code:
130 [email protected] ~ % fastboot oem fb_mode_set :(
< waiting for device >
^C
130 [email protected] ~ %
Click to expand...
Click to collapse
Someone can drop in, and with out much work tell what I have done, and see that it is not working because fastboot cannot find the device.
scryan said:
We don't know what your doing, what you tried, or why it didn't work, because we can't see you or what your doing.
You need to post in a coherent straight forward manor.
I am not sure why you follow other peoples tutorials, then ask US about them. For help with your tutorial, ask the people who wrote that tutorial. If you want help here, try first with OUR tutorials. I don't say this to be mean, but we are unfamiliar with other tutorials and can only really support ours.... It gives us a standard to reference back to.
From the first page, "Returning to 100% stock with RDS or manual"
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
I would use the manual version, so you can see what errors occur more easily.
Make sure you have the right files for your version, and understand this:
http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 about downgrading, shouldn't be an issue but not a bad idea to double check what bootloader you have.
Also make SURE you have the right firmware.
Read those threads, and if you still have an issue copy and paste the terminal output here using code tags.
Rather then downloading it from random websites, you know Moto hosts the official firmwares, at least for DE phones on their website so you can get the most recent, verified version direct from the official source rather then going through random unofficial mirrors...
Click to expand...
Click to collapse
Actually mate, i have been using that link only. But when that didn't worked. I tried others. :l But they failed too. This link shown perfect method. But i have no idea why it's keep happening. This seems more confusing that flashing ROMs on my Canvas HD. It was easy. But this is getting crazy. Please help me with this. I tried from fresh. But it's still same. Maybe you could help me with team viewer or something? Plus one thing i would like to tell you. On most tutorials they said, delete a line "<step operation="getvar" var="max-download-size" />" even it's written in that link too, which you posted. But thing is that, i extracted my firmware, and it's already not in XML file. So.. i am confused with all this. Maybe you can help me with this. Thanks. I hope you don't mind.
You have a locked bootloader, your not just flashing a rom, you need to use fastboot, a standard android tool, to restore your phone.
Your not going to flash a rom, you will be downloading that SBF you have been linked to, unzipping it and flashing each partition, AS STATED IN THE RSD THREAD.
DarKrypton said:
So.. i am confused with all this. Maybe you can help me with this. Thanks. I hope you don't mind.
Click to expand...
Click to collapse
We don't know what your doing, what you tried, or why it didn't work, because we can't see you or what your doing.
You need to post in a coherent straight forward manor.
I would use the manual version, so you can see what errors occur more easily.
Make sure you have the right files for your version, and understand this:
http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
copy and paste the terminal output here using code tags.
Click to expand...
Click to collapse
You have been asked multiple times for the exact error messages. We don't know why your computer wont work... But your computer pretty much tells you each time with a specific message. You need to give us those messages.
Consider the fact that there MAY be someone here who doesn't care about you or your phone, but knows the answer. If you make it easy that person MAY help you. If you post paragraph after paragraph of text describing the error message, rather then the 1 line error message they probably wont read. Be as direct as possible, show us what you have done (I didn't really flow many of you links, why should we have to chase down this information to give you free tech support?)
Like this:
I am trying to fix a phone for a friend. Upon boot I get continuous force closes from a variety of different apps. I am left with a crashed an unusable system.
I have tried to flash _____ rom using _____ tool, but recivied the following error message
Code:
word for word error message
I found this thread: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 on returning to stock using RDS light, and used
RETAIL-US_4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip from http://motofirmware.center/files/category/9-ghost/
There was an error durring fasboot, and there seem to be no changes to the phone.
Code:
130 [email protected] ~ % fastboot oem fb_mode_set :(
< waiting for device >
^C
130 [email protected] ~ %
Click to expand...
Click to collapse
Someone can drop in, and with out much work tell what I have done, and see that it is not working because fastboot cannot find the device.
Ok, let me clear everything to you.
I am trying to fix a phone for a friend. Upon boot I get continuous force closes from a variety of different apps. I am left with a crashed an unusable system.
I have tried to flash Moto X XT1052 (XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml) rom posted above by "athulele" using "fastboot" tool, but recivied the following error message. This is first error, with fresh installing. Trying with first command. "fastboot oem fb_mode_set"
Code:
"fastboot" is not recognized as an internal or external command, operable program or batch file.
It's obviously because "fastboot" and ADB are not present in ROM folder. So i guess i need to copy all files from a software i installed "Minimal ADB and Fastboot" as per other tutorials. Which made me more confused. So i want to go with your tutorial.
Second thing, if i make copy of files in ROM folder. It starts taking commands, but with another error. Which is :
Code:
C:\Users\(Username)\Desktop\XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.x
ml>fastboot flash partition fpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
error: cannot load 'fpt.bin': No error
After that, i think i should not continue. After this maybe please take a look. Let me know where i am doing wrong. Must be totally wrong where i copied those files in ROM folder. I couldn't continue without them. Because of that error. Let me know if i am missing any driver. Because as fasr i know i installed all latest drivers. Let me know. Thanks.
Click to expand...
Click to collapse
DarKrypton said:
Ok, let me clear everything to you.
Click to expand...
Click to collapse
Try the commands without "fastboot OEM mode set". Also if your friend had completely stock system, you can try flashing only system.img, boot.img, recovery.IMG
After you flash this, erase data by " fastboot erase userdata" this will erase everything including sdcard .
After that "fastboot erase modemst1" and "fastboot erase modemst2" to clear modem cache. Then try rebooting into system.
Also, you had typed fpt instead of gpt. That's why you got the error
Sent from my Moto X using XDA Free mobile app
athulele said:
Try the commands without "fastboot OEM mode set". Also if your friend had completely stock system, you can try flashing only system.img, boot.img, recovery.IMG
After you flash this, erase data by " fastboot erase userdata" this will erase everything including sdcard .
After that "fastboot erase modemst1" and "fastboot erase modemst2" to clear modem cache. Then try rebooting into system.
Also, you had typed fpt instead of gpt. That's why you got the error
Sent from my Moto X using XDA Free mobile app
Click to expand...
Click to collapse
No no, sorry my bad. Typing mistake here. I did gpt.bin. This time i did mistake, that's why got "error: cannot load 'fpt.bin'". Otherwise it's only "(bootloader) Variable not supported!" And status at end "OKAY" then next command. And i can't take risk for flashing few files only. Because my friend have no idea on this. It's all on me, what can be done. I need to flash full ROM to match up future OTA updates. It's somewhere wrong in copying files in ROM folder. I tried those commands, as per tutorial. So it didn't worked. :l
DarKrypton said:
No no, sorry my bad. Typing mistake here. I did gpt.bin. This time i did mistake, that's why got "error: cannot load 'fpt.bin'". Otherwise it's only "(bootloader) Variable not supported!" And status at end "OKAY" then next command. And i can't take risk for flashing few files only. Because my friend have no idea on this. It's all on me, what can be done. I need to flash full ROM to match up future OTA updates. It's somewhere wrong in copying files in ROM folder. I tried those commands, as per tutorial. So it didn't worked. :l
Click to expand...
Click to collapse
I don't exactly know whether you need an unlocked bootloader to flash via fastboot. But if you don't want to, then you can try factory reset from stock recovery or from the bootloader. There's plenty of guides all around for stock recovery.
Sent from my Moto X using XDA Free mobile app
athulele said:
I don't exactly know whether you need an unlocked bootloader to flash via fastboot. But if you don't want to, then you can try factory reset from stock recovery or from the bootloader. There's plenty of guides all around for stock recovery.
Sent from my Moto X using XDA Free mobile app
Click to expand...
Click to collapse
Naw, fastboot works with locked boot loader. It should be able to reflash on locked as long as the files are signed.
athulele, I think he said he tried factory reset...
Dark, your correct that you need to be in the same directory as that fastboot command (note there is also a mfastboot command. Motorola modified the stock android fastboot tool so it could flash larger partitions, at least from my understanding). If your not in the directory that executable is your OS will not be able to find it (unless you add it to your systems path, but if you don't know how or what that is easier to just make sure the EXE is in the folder your working out of)
The second time you tried to run it it looked like it worked perfectly right? but the correct command is
Code:
fastboot flash partition gpt.bin
Note the syntax is
fastboot [operation] [partition name] [file], so when you gave it the wrong file it correctly said it can't do it. Everything fine here.
again MAKE SURE your flashing the right files, double check your typing the command correctly (Copy and paste is good, but make sure you don't copy any extra characters at the begining or end of the line before you press enter to run the command)
About the worry over only flashing some paritions: You right to worry, you don't want to do this. HOWEVER, if you have the right files they should work. Go through that list of commands one by one. Figure out why any one command fails and get it to work before moving on... But if your flashing the same thing as is already on the phone, your not going to miss match partitions because your flashing the same version of each partition back over itself just trying to fix what ever one is messed up...
But yeah, make sure you got those files, run through those fastboot commands and post the output here. Copying too much of the console output is probably better then too little.
scryan said:
Naw, fastboot works with locked boot loader. It should be able to reflash on locked as long as the files are signed.
athulele, I think he said he tried factory reset...
Dark, your correct that you need to be in the same directory as that fastboot command (note there is also a mfastboot command. Motorola modified the stock android fastboot tool so it could flash larger partitions, at least from my understanding). If your not in the directory that executable is your OS will not be able to find it (unless you add it to your systems path, but if you don't know how or what that is easier to just make sure the EXE is in the folder your working out of)
The second time you tried to run it it looked like it worked perfectly right? but the correct command is
Code:
fastboot flash partition gpt.bin
Note the syntax is
fastboot [operation] [partition name] [file], so when you gave it the wrong file it correctly said it can't do it. Everything fine here.
again MAKE SURE your flashing the right files, double check your typing the command correctly (Copy and paste is good, but make sure you don't copy any extra characters at the begining or end of the line before you press enter to run the command)
About the worry over only flashing some paritions: You right to worry, you don't want to do this. HOWEVER, if you have the right files they should work. Go through that list of commands one by one. Figure out why any one command fails and get it to work before moving on... But if your flashing the same thing as is already on the phone, your not going to miss match partitions because your flashing the same version of each partition back over itself just trying to fix what ever one is messed up...
But yeah, make sure you got those files, run through those fastboot commands and post the output here. Copying too much of the console output is probably better then too little.
Click to expand...
Click to collapse
One thing i would like to ask mate. I am gonna start fresh installation. From laptop now. I noticed one thing, that on
Code:
"fastboot erase modemst1" and
"fastboot erase modemst2"
commands. On boot screen, it just keep showing
Code:
"erasing modemst1..."
for a long time. Does it take that long, or it gets "done" text in a sec? Let me know. I am starting now. Thanks.
Not sure how long it should take tbh. I would let it run, and give it a good while before worrying about it. Maybe open up some kind of system resource monitor on the side (on your computer) so you can see that things are still happening?
There are definitely times that these types of tools will look like its just sitting there though... It should go through eventually, give 10+ minutes before assuming it is not working.
scryan said:
Not sure how long it should take tbh. I would let it run, and give it a good while before worrying about it. Maybe open up some kind of system resource monitor on the side (on your computer) so you can see that things are still happening?
There are definitely times that these types of tools will look like its just sitting there though... It should go through eventually, give 10+ minutes before assuming it is not working.
Click to expand...
Click to collapse
Alright, i am on that command. I am gonna paste whole console commands. Because i think this time it won't work too. :l After every command it's showing
Code:
<bootloader> Variable not supported!
then "OKAY" like it went correct. Plus can you tell me what exactly my variant name is? I can't figure out, as for that OP, it was VZW. But for me, it must be different. I need it for second last command. Thanks.
EDIT : 25 minutes passed. Still same.
Full stock LVY48H on Fi . I've been wanting to go Marshmallow, but Google hasn't gotten around to sending me the OTA. I found this thread in the General forum and downloaded the appropriate .ZIP, but the contents don't look a bit like the ROM downloads, so fastboot doesn't appear to be an option. How do I put it on?
Download factory image, extract, flash each img file separately except for userdata.
Mostlyhrmlss said:
Full stock LVY48H on Fi . I've been wanting to go Marshmallow, but Google hasn't gotten around to sending me the OTA. I found this thread in the General forum and downloaded the appropriate .ZIP, but the contents don't look a bit like the ROM downloads, so fastboot doesn't appear to be an option. How do I put it on?
Click to expand...
Click to collapse
If your bootloader is unlocked, you can flash it manually in ABD or use that toolkit (for factory image). I did that but it it also wiped my phone, which was fine by me, it needed a good cleaning after flashing updates to another custom 5.1.1 rom over and over again!
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
@Tower1972: Attached is a screenshot of the contents of the ZIP. How would I go about flashing that with ADB?
Mostlyhrmlss said:
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
Click to expand...
Click to collapse
RTFM
Tower1972 said:
If your bootloader is unlocked, you can flash it manually in ABD or use that toolkit (for factory image). I did that but it it also wiped my phone, which was fine by me, it needed a good cleaning after flashing updates to another custom 5.1.1 rom over and over again!
Click to expand...
Click to collapse
when youre giving advice to someone, make sure that its correct. you dont flash anything with adb, you use fastboot. fastboot is different than adb.
@boomerbubba: FTFY: Here's a guide on how to do that. I prefer civility when applicable; my sympathies for whatever is going on in your life to make you want to answer in such a way.
@simms22: Turns out the advice was correct: "adb sideload [OTA file].zip" is the appropriate command to accomplish what I'm after here.
Some strategic Googling found me the answer while I was awaiting responses, here it is for the benefit of anyone who should have the same question. Prollyshooda done that first.
Mostlyhrmlss said:
@boomerbubba: FTFY: Here's a guide on how to do that. I prefer civility when applicable; my sympathies for whatever is going on in your life to make you want to answer in such a way.
@simms22: Turns out the advice was correct: "adb sideload [OTA file].zip" is the appropriate command to accomplish what I'm after here.
Some strategic Googling found me the answer while I was awaiting responses, here it is for the benefit of anyone who should have the same question. Prollyshooda done that first.
Click to expand...
Click to collapse
actually, you were incorrect. you said use adb to manually flash. now you said adb for adb sideload. those are two completely different things. all adb sideload does is move a file from your computer to your phone.
edit.. now you are right, i read your response wrong :angel:
Contrition on the Internet? Whodathunkit! We should get together for a beer, I like your kind of folk.
Mostlyhrmlss said:
Contrition on the Internet? Whodathunkit! We should get together for a beer, I like your kind of folk.
Click to expand...
Click to collapse
contrition is one of the things that pull me down. but its honesty, and the truth. so i stay with it
Mostlyhrmlss said:
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
@Tower1972: Attached is a screenshot of the contents of the ZIP. How would I go about flashing that with ADB?
Click to expand...
Click to collapse
I don't know what zip file that is, but it's not a factory image from Google. If you download a factory image from Google, you extract every img file and flash using fastboot.
What is everyone's fascination with adb sideload?
nhizzat said:
What is everyone's fascination with adb sideload?
Click to expand...
Click to collapse
It doesn't require an unlocked bootloader. Which for the people that haven't done that, it wipes your phone as part of the unlock process.
Also, it is a smaller download if you are on an ISP with limited bandwidth.
Google says....
http://https://developers.google.com/android/nexus/images
That will get you going, but since the included script won't work, you have to unzip the zip package, what you will find inside the parent folder. Happy flashing
nhizzat said:
I don't know what zip file that is, but it's not a factory image from Google. If you download a factory image from Google, you extract every img file and flash using fastboot.
What is everyone's fascination with adb sideload?
Click to expand...
Click to collapse
That ZIP is an OTA downloaded from the thread referenced in my original post. My fascination with adb sideload (now that I know what it is) is that I can accomplish an upgrade with a single command, which suits my advanced case of laziness very well . Seems much easier than unzipping a file, then unzipping a file from that file (more than doubling the storage requirement, I have a rather small SSD) and issuing several fastboot commands with slightly different syntaxes and hoping I didn't miss (or mistype) something.
I already know how to do a full flash, I unlocked the bootloader and did so first thing when I bought it used to make sure it was cleared of the previous owner's data and completely up-to-date. What I wasn't sure of is if it would be safe to do so for a full version jump. I'm much more comfortable with OTAs since I've applied several and it stands to reason that a carrier would never issue one if it might cause an undue number of problems for their support staff to address.
Martend said:
That will get you going, but since the included script won't work...
Click to expand...
Click to collapse
That script just burns my biscuits. Why in the name of all that is neat and groovy can't Google fix such a basic problem?
Mostlyhrmlss said:
That script just burns my biscuits. Why in the name of all that is neat and groovy can't Google fix such a basic problem?
Click to expand...
Click to collapse
because its fixed in the latest version of fastboot, that no one seems to be using..
simms22 said:
because its fixed in the latest version of fastboot, that no one seems to be using..
Click to expand...
Click to collapse
Why break it in the first place? lol It's the first thing you learn here, debug & test before releasing it to the masses
So, I got the latest ADB and FASTBOOT from here, put the device in ADB update mode through recovery mode (already OEM unlocked and USB debugging enabled), ran 'adb sideload <filename>' as instructed onscreen, and got "error: device (null) not found" from the command. The device shows up in the Windows device manager when in bootloader mode, but disappears when I go to recovery mode. What am I doing wrong?
Mostlyhrmlss said:
So, I got the latest ADB and FASTBOOT from here, put the device in ADB update mode through recovery mode (already OEM unlocked and USB debugging enabled), ran 'adb sideload <filename>' as instructed onscreen, and got "error: device (null) not found" from the command. What am I doing wrong?
Click to expand...
Click to collapse
do you have the drivers installed? fastboot wont see your device until then.
I installed the drivers as part of the ADB/FASTBOOT package referenced above, but that's not the problem: the device is not shown at all in the Windows device manager, as if it wasn't plugged in.
I think it's possible because the amazon fifth Gen, it has a locked bootloader but we were still able to boot into a custom recovery by using the original kernel of the device somehow. I know it's not the same thing but if we have access to do commands we can flash a custom recovery that way. I'll be asking the guy who made the custom recovery on how he did it. Then maybe we can modify the android 6.0 update zip and inject root into it??
I have that device. It requires fastboot i believe.
Not holding my breath
danweb66 said:
I have that device. It requires fastboot i believe.
Click to expand...
Click to collapse
It is possible to nuke the laf and gain access to fastboot. You could then flash your needed commands and restore laf.
tabp0le said:
It is possible to nuke the laf and gain access to fastboot. You could then flash your needed commands and restore laf.
Click to expand...
Click to collapse
I was about to say exactly that. A fun little trick I picked up with my G2 when I bricked it really damn bad and basically had zero options for getting it to boot again without access to fastboot, which was so wonderfully omitted by LG despite the G2 and the Nexus 5 being almost the same phone under the hood, so I was a bit reckless thinking they wouldn't have made the software so drastically different when they're almost identical hardware.
I have a feeling nuking laf and using a kindle method really could work, but unfortunately I don't have a backup phone to move my number over to while I try until I get a replacement Moto X under warranty (that one literally bricked itself within six months running stock)
I don't think the 5th gen fire has 6.0...I may be mistaken tho.
No I'm not saying use fastboot I'm saying flash the recovery using dd commands instead. You can back up the recovery just incase something happensAL and flash that back. Meaning nuking only the recovery partition and flashing a modified boot.img
Interesting, sounds possible but you would think that someone more advanced than us would of considered this.
Awesomeslayerg said:
No I'm not saying use fastboot I'm saying flash the recovery using dd commands instead. You can back up the recovery just incase something happensAL and flash that back. Meaning nuking only the recovery partition and flashing a modified boot.img
Click to expand...
Click to collapse
base_ten said:
Interesting, sounds possible but you would think that someone more advanced than us would of considered this.
Click to expand...
Click to collapse
I'm pretty sure that's what I did for the tmoble version...was side load the recovery with dd commands..I think the twrp recovery needs to made for sprint tho
Edit: http://forum.xda-developers.com/tmo...recovery-twrp-2-8-7-0-touch-recovery-t3164874 there was 2 ways 2 do it one with flashify an the other with dd commands...not sure if it will work for us but who knows...
Hate to resurrect a perfectly dead thread, but I'm guessing no one has tried this with any success?
Ive been looking into things like i know g2 had lokinexploit att g3 images and recoverys are bumped both had lock bls but i dont know yet i just got this g4 last night and ill be stuck with it for at least a year or so so im in for testing i aint worried bout waranty and i got insuarance have in my opinion better tech skills than a lot of people i know so im all game
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