Database Develop

[Q] Swapping nandroid from one Moto X VZW Dev Ed to another

So, I am a new happy owner of the Moto X VZW Dev Ed. However, Motorola was having a sale last week and said they couldn't give me a price match, but that I could reorder and ship back the other one (which is what I did).
Problem is, I've already updated the first one (I think there were three OTA updates I installed), unlocked and rooted it. Then installed a bunch of stuff, disabled a lot of stuff, etc... I really don't want to do this twice!
My question is if I make a nandroid backup using TWRP (with all options turned on), what is the minimal amount of work I'd have to do to transfer everything to the new phone?
I guess since nandroid backups do not include firmware, it's safest to complete the OTA updates on the replacement phone (unless I know for sure there were no firmware updates installed), unlock, root and lastly restore from the nandroid of the old phone?

etc6849 said:
So, I am a new happy owner of the Moto X VZW Dev Ed. However, Motorola was having a sale last week and said they couldn't give me a price match, but that I could reorder and ship back the other one (which is what I did).
Problem is, I've already updated the first one (I think there were three OTA updates I installed), unlocked and rooted it. Then installed a bunch of stuff, disabled a lot of stuff, etc... I really don't want to do this twice!
My question is if I make a nandroid backup using TWRP (with all options turned on), what is the minimal amount of work I'd have to do to transfer everything to the new phone?
I guess since nandroid backups do not include firmware, it's safest to complete the OTA updates on the replacement phone (unless I know for sure there were no firmware updates installed), unlock, root and lastly restore from the nandroid of the old phone?
Click to expand...
Click to collapse
I would use Philz @hachamacha edition. See the RAZR HD section. If an OTA is needed YES do it first.
The problem is the data partition not the system. Due to your ESN and such.
Hachamacha may help you with some issues.
He is about to do a unified build to include his new X!
---------- Post added at 01:50 PM ---------- Previous post was at 01:26 PM ----------
He just posted the unified
http://forum.xda-developers.com/showpost.php?p=52414440&postcount=78

Thanks, the ESN/IMEI is normally stored in the radio's firmware? Or are you saying there's some file somewhere that also contains that data?

etc6849 said:
Thanks, the ESN/IMEI is normally stored in the radio's firmware? Or are you saying there's some file somewhere that also contains that data?
Click to expand...
Click to collapse
Right data contains phone data. But you may find a way to patch those IDs. Not via *228, as that is for 3g only. Try a complete restore & if you have to wipe data you can.
I do not know what happens when data is loaded from another phone.

aviwdoowks said:
I would use Philz @hachamacha edition. See the RAZR HD section. If an OTA is needed YES do it first.
The problem is the data partition not the system. Due to your ESN and such.
Hachamacha may help you with some issues.
He is about to do a unified build to include his new X!
---------- Post added at 01:50 PM ---------- Previous post was at 01:26 PM ----------
He just posted the unified
http://forum.xda-developers.com/showpost.php?p=52414440&postcount=78
Click to expand...
Click to collapse
Hi aviwdoowks,
I haven't yet posted anything but an intention to post something (how convoluted is that?) ; I have some builds that're up to date, unified, etc, for the *dt versions, but since I can't test until I get one, I hate to dump it on people. If someone doesn't care, then PM me. I'll be around for a few hours today and tomorrow to respond. Just make sure you tell me what device you've got since I just started dev for about 9 or 10 devices today.
Cheers.

hachamacha said:
Hi aviwdoowks,
I haven't yet posted anything but an intention to post something (how convoluted is that?) ; I have some builds that're up to date, unified, etc, for the *dt versions, but since I can't test until I get one, I hate to dump it on people. If someone doesn't care, then PM me. I'll be around for a few hours today and tomorrow to respond. Just make sure you tell me what device you've got since I just started dev for about 9 or 10 devices today.
Cheers.
Click to expand...
Click to collapse
I cannot get multi quote to work.
What do you think of the Op's restore question.
I thought you might come up with a way to restore data to a different X phone.

aviwdoowks said:
I cannot get multi quote to work.
What do you think of the Op's restore question.
I thought you might come up with a way to restore data to a different X phone.
Click to expand...
Click to collapse
Near as I can see (and I just tried multi-q for the first time), it is a myth I copied the original question down below and will look and see.
etc6849 said:
So, I am a new happy owner of the Moto X VZW Dev Ed. However, Motorola was having a sale last week and said they couldn't give me a price match, but that I could reorder and ship back the other one (which is what I did).
Problem is, I've already updated the first one (I think there were three OTA updates I installed), unlocked and rooted it. Then installed a bunch of stuff, disabled a lot of stuff, etc... I really don't want to do this twice!
My question is if I make a nandroid backup using TWRP (with all options turned on), what is the minimal amount of work I'd have to do to transfer everything to the new phone?
I guess since nandroid backups do not include firmware, it's safest to complete the OTA updates on the replacement phone (unless I know for sure there were no firmware updates installed), unlock, root and lastly restore from the nandroid of the old phone?
Click to expand...
Click to collapse
Not sure I'm understanding. Was the first phone not a DE, rather an xt1060 or something like that? If so, which model was it? I'm also awaiting (few days) delivery of my first Moto X DE but have had no other one. Any factory unlockable phone I've had in the past is returned to a somewhat blank condition (/system and /data) as soon as you either a) lock or b) unlock using the Moto website so you'll of course, have to do that much and then slap on SuperSU (or whatever you like for root), busybox, etc.
Minimal amount of work? Stick to one recovery type because making backups is easy. If you want to use TWRP (which is a good recovery) to restore to the new phone, then do it. The easiest part of everything is changing recoveries once unlocked and rooted and you "KNOW" that TWRP can restore TWRP. Yes, Philz Touch can also restore TWRP, but when we build for phones new to us, sometimes, the git is in a state where maybe something isn't working, so why bother taking a chance on wasting all that time.
I've got Philz Touch latest version built for the msm8960dt (the motos/ultra/maxx/and others) but haven't looked into it since I've got no phone yet. My other possible suggestion would be to switch to Philz Touch as soon as I put up a pointer on it (or use an older one if you get your phone before). Stick it on your phone and make a new backup in CWM/Philz format. I'll go through the code and enable the /persist partition so you can get a backup of that. When you get the new DE, goto website, unlock, (which will probably just git rid of /data and /system), and if you want the least amount of guessing what is needed and not needed , just install the DE 4.4.2 image from the site so you'll have the firmware that is desired for that model phone. (radio and /firmware / persist stuff). Then boot to recovery and do the restore of the usual partitions. Use the .xml file in the .zip to figure out the order of the partition flashing for /firmware and radios and any other bits you want to flash. I would just create a batch file with 'fastboot flash 'partitionname' '{name}.img' statements in the exact order as in the .XML file and run it.
I don't know which (if anything but stock) ROM you've used and I'm not sure it matters which flavor it is, but it matters which version it was built from on the Moto so be sure it's apples to apples, since most the ROMs I've looked at seem to require the kernel from whatever was installed before. (the /lib/modules are also built to match that kernel as well and are a part of the /system of that ROM).
Everytime I've gone into a new phone situation and decided I was going to get away with a nandroid restore and voila , it always takes a bit of touch-up work, so pick one recovery, make the backups doing it, and do the restores to the DE using it rather than adding yet another variable. I can't think of one situation where I didn't have to at least use say Titanium Backup to restore the apps (I don't bother with data) because things rarely work out the same way. The other not-so-intuitive thing is that moving things from one phone to another (especially a nonDE to a DE) often bring up a new issue or more so expect to have to do a bit of work. Just be sure to make a good copy of the /sdcard/.. stuff that you need to keep (TitaniumBackup), and other data you need that nandroids don't care about, and back it up to your PC using adb. After you unlock, you can copy it to the target phone, and try the recovery. I really like Philz and I like TWRP as well, but I'd never tell someone they could move for sure from one phone to another without any problem. Best bet is using same recovery type on both ends though. Don't restore /persist or /firmware unless you're certain it's wiped. I mean that 4.4.2 image (.xml.zip) from the website has all the firmware you really want in it at it takes about 2 simple statements from adb to get it on the phone. That's pretty easy. Also, you never know. Might get lucky and a nandroid could be all you need but I'm not holding my breath on that.
Good luck.

Am I totally bricked?

I recently sold my XT1049 on 4.4.4 which I have been using on CDMA. The new owner wants it on GSM, no problem - apparently. I did the normal factory reset from Philz recovery and tried to unlock for GSM. I got stuck on "Home Only" menu. I wrestled with it for like 3 hours, restoring to Sprint 4.4.4 sbf with RSDLite, installing 4.4.2 ROM and any other tricks I knew, still same Home Only. I finally remembered people saying that the T-Mobile ROm worked for them in that situation when they used Sunshine to unlock. I downloaded the T-Mobile ROM I could lay hands on fast - the 4.2.2 and the phone came up and saw GSM network. I was relieved. Shortly it started downloading an update. I flashed a T-Mobile stock recovery in preparation for the update, since the custom recovery cannot take it. And here I am now, after taking and running the update the phone refuses to come up again. Just nothing - no sound when plugged in, no fastboot, just nothing. Any help.please?

Probably, you went from 4.4.4 to 4.2.2. It's been said over and over and over DO NOT downgrade. There's been some that supposedly did but probably hacked up a sbf file and have mismatched pieces which may end up bricking them also
root, roms, and themes.. oh my!

Nemosfate said:
Probably, you went from 4.4.4 to 4.2.2. It's been said over and over and over DO NOT downgrade. There's been some that supposedly did but probably hacked up a sbf file and have mismatched pieces which may end up bricking them also
root, roms, and themes.. oh my!
Click to expand...
Click to collapse
I think you missed my narration. I installed 4.2.2 ROM - not the sbf. I know enough not to do that. Installing a lower version ROm works well, infact the phone was ok until it downloaded and installed the update. i think that update was lower than the 4.4.4 I was already on before flashing the 4.2.2 ROM. OK. Enough of the lashing, any help?

Have you tried this yet.
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
---------- Post added at 11:19 PM ---------- Previous post was at 11:18 PM ----------
Also great info here as well.
http://forum.xda-developers.com/moto-x/moto-x-qa/expert-opinion-to-stock-t2944721
---------- Post added at 11:21 PM ---------- Previous post was at 11:19 PM ----------
Can you get into fastboot mode and flash your carriers 4.4.4 images?

ezeuba said:
I think you missed my narration. I installed 4.2.2 ROM - not the sbf. I know enough not to do that. Installing a lower version ROm works well, infact the phone was ok until it downloaded and installed the update. i think that update was lower than the 4.4.4 I was already on before flashing the 4.2.2 ROM. OK. Enough of the lashing, any help?
Click to expand...
Click to collapse
Sorry about that... Wasn't las lashing Lol... Just wanted to clarify and in case anyone reading it thought like I did
root, roms, and themes.. oh my!

ezeuba said:
I think you missed my narration. I installed 4.2.2 ROM - not the sbf. I know enough not to do that. Installing a lower version ROm works well, infact the phone was ok until it downloaded and installed the update. i think that update was lower than the 4.4.4 I was already on before flashing the 4.2.2 ROM.
Click to expand...
Click to collapse
If you had flashed 4.2.2 the OTA was likely 4.4.
But again... Downgrading, even "PARTS" is risky.
There are many like you who say installing an older rom and not flashing the full SBF (i.e. only flash certain parts with those from an older rom), "works well" yet there are just as many in that state who later brick when an OTA is taken.
When you "installed" 4.2.2 rom, you did not downgrade the GPT.BIN and MOTOBOOT.IMG and the parts they contain (and you couldn't because the phone would not have allowed it). Having the phone in that MIXED MATCHED state (4.2.2 system with gpt.bin and motoboot.img from 4.4.4) will cause issues, including bricking, when an UPDATE happens. Its been documented in many threads.
We've also seen in a mixed matched state where phone's features don't work... like when 4.4.2 first came out, and people downgraded by flashing only system.img from 4.4 claiming it was fine, yet if they tried to go App Drawer -> Settings -> Security they were kicked out of settings.
ezeuba said:
OK. Enough of the lashing, any help?
Click to expand...
Click to collapse
Sometimes the "lashings" happens more so as an attempt to reinforce (to anyone who may come across the thread) that for as many people say "its safe to downgrade" or "its safe to do this to run an older ROM" that it really isn't. It does have real risks, and usually it leads to bricking.
As for help.. If you can not boot the phone to the Fastboot menu, your only hope is trying this thread -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 If you have any questions, ask them in that thread. The Riffbox driver link in the OP doesn't work, so see Post #253 of that thread for a working download link.
If that doesn't work, your phone is toast.
If you do get your phone working, never downgrade, even "just parts".

XT1803 European Firmware

Hello,
I'm hoping to return my XT1803 to stock , and I'm just wondering if anybody knows of (or even just a Nandroid/TWRP backup) a link to download the European version of the stock firmware for the XT1803?
The official firmwares on the Firmware Centre Website that I've had a look at (and all of the download links that I've seen), are all for the US version, unless I'm just being an idiot and these would work too (but then it would be the wrong baseband?)?
Many thanks in advance for helping.

seanoo said:
Hello,
I'm hoping to return my XT1803 to stock , and I'm just wondering if anybody knows of (or even just a Nandroid/TWRP backup) a link to download the European version of the stock firmware for the XT1803?
The official firmwares on the Firmware Centre Website that I've had a look at (and all of the download links that I've seen), are all for the US version, unless I'm just being an idiot and these would work too (but then it would be the wrong baseband?)?
Many thanks in advance for helping.
Click to expand...
Click to collapse
You got try it minus the modem(s) and fsg partitions.
No guarantees though.

Phazmos said:
You got try it minus the modem(s) and fsg partitions.
No guarantees though.
Click to expand...
Click to collapse
I went ahead and gave it a go, everything is working however I seem to be unable to get any 4G signal now.

seanoo said:
I went ahead and gave it a go, everything is working however I seem to be unable to get any 4G signal now.
Click to expand...
Click to collapse
Correct apn enabled?

Phazmos said:
Correct apn enabled?
Click to expand...
Click to collapse
Yes. 2G and 3G work fine, just 4G doesn't work.

seanoo said:
Yes. 2G and 3G work fine, just 4G doesn't work.
Click to expand...
Click to collapse
Well, if you skipped flashing the modems and fsg partitions, nothing should have changed as far as radios and bands.
I could only suggest resetting network settings - there's an option in the os for that, but I can't remember where right off (I'm running 8.1 and is different in 7.x), but it is there.
If that's a no go - factory reset the device.
If that's a no go restore the bu of what you had and be happy with it.
A second to last resort would be flashing the entire stock firmware you have, including modems and fsg, and see what happens. Just make sure the flash is successful - it should say okay after each command is run.
The last option would be to see a moto/Lenovo (whoever) service center and have them flash the stock firmware.
Personally, I would stay with custom roms, but the state of custom for this device right now is questionable at best. There are enough of them, but I have little confidence in most of them - very few work 100% but the few that do are decent enough.
Ps - something I have seen is a loss of imei when going back to stock (not by me - I've flashed stock a few times and no issues, but I have xt1806). Check that.

Phazmos said:
Well, if you skipped flashing the modems and fsg partitions, nothing should have changed as far as radios and bands.
I could only suggest resetting network settings - there's an option in the os for that, but I can't remember where right off (I'm running 8.1 and is different in 7.x), but it is there.
If that's a no go - factory reset the device.
If that's a no go restore the bu of what you had and be happy with it.
A second to last resort would be flashing the entire stock firmware you have, including modems and fsg, and see what happens. Just make sure the flash is successful - it should say okay after each command is run.
The last option would be to see a moto/Lenovo (whoever) service center and have them flash the stock firmware.
Personally, I would stay with custom roms, but the state of custom for this device right now is questionable at best. There are enough of them, but I have little confidence in most of them - very few work 100% but the few that do are decent enough.
Ps - something I have seen is a loss of imei when going back to stock (not by me - I've flashed stock a few times and no issues, but I have xt1806). Check that.
Click to expand...
Click to collapse
That is what I thought in regards to the radio, so I flashed the one from the firmware as a what's the worse that could happen, but it has made no difference, except the signal is now much worse, I did try resetting the network settings but it hasn't helped.
I did want to stay with a custom rom, but I was unable to find one I liked, as you say, the custom roms for this device are questionable and most of them are not polished.
I normally use my phone as a hot spot, and I really need the extra speeds that 4G gives, which is why I'm looking to fix the issue if possible.
I did have a look to see if there's a service centre near me, but I can't see one, so I may just wait to see anybody is able to provide me with the correct firmware (or even just the modem and fsg would be excellent).

seanoo said:
That is what I thought in regards to the radio, so I flashed the one from the firmware as a what's the worse that could happen, but it has made no difference, except the signal is now much worse, I did try resetting the network settings but it hasn't helped.
I did want to stay with a custom rom, but I was unable to find one I liked, as you say, the custom roms for this device are questionable and most of them are not polished.
I normally use my phone as a hot spot, and I really need the extra speeds that 4G gives, which is why I'm looking to fix the issue if possible.
I did have a look to see if there's a service centre near me, but I can't see one, so I may just wait to see anybody is able to provide me with the correct firmware (or even just the modem and fsg would be excellent).
Click to expand...
Click to collapse
Did you back everything up in twpr - including efs partition after unlocking?

[OBSOLETE] Variants with KDZs Bl Unlock Guide

THIS GUIDE IS NOW OBSOLETE
Links will be added once the new guide using the firehose comes out - No more bricking!
Thanks to everyone who contributed to the firehose!
I just cut and pasted the whole guide into a txt file, which is linked below in case there's ever any purpose of looking at it again.
https://drive.google.com/file/d/1wTRMvweLlsF-3WU9CYlz7X3ZIRE3vtCs/view?usp=sharing

Isn’t Mr. Zhu the author of twrp?

You might want to wait until I get to my computer again as I realized there are a few minor edits that could be helpful. It's not letting me edit it successfully on my phone

Malossi94 said:
Isn’t Mr. Zhu the author of twrp?
Click to expand...
Click to collapse
Yeah but apparently he stopped development, but le Minh sent the Korean fix after that so I'm not entirely sure lmao

antintin said:
Yeah but apparently he stopped development, but le Minh sent the Korean fix after that so I'm not entirely sure lmao
Click to expand...
Click to collapse
Mr. Zhu repaired kor twrp, and my kor skt G8 participated in the repair development:silly:

Malossi94 said:
Mr. Zhu repaired kor twrp, and my kor skt G8 participated in the repair development:silly:
Click to expand...
Click to collapse
Nice! I'll edit as soon as I get on my computer

Hi have followed the guide and got stuck at step 7. I get only the LG V50Thinq powered by android screen and nothing more. It just stays like for the past 30 minutes. I have rebooted several times but the same. i cannot access (or do not know) download mode.
Any help!

So, if your on a korean version that wil be a q version of android vulnerable. Therefore at step 6, you will need a pie kdz to flash those 4 xbl files. Do not make my mistake, you will get bricked ))

Marmalux said:
So, if your on a korean version that wil be a q version of android vulnerable. Therefore at step 6, you will need a pie kdz to flash those 4 xbl files. Do not make my mistake, you will get bricked ))
Click to expand...
Click to collapse
Sorry I'm afraid I don't understand. That's step 4, and you don't need to flash the whole kdz. Only the partitions the guide says to.

antintin said:
Sorry I'm afraid I don't understand. That's step 4, and you don't need to flash the whole kdz. Only the partitions the guide says to.
Click to expand...
Click to collapse
I think he's referring to how its a bit confusing how it says you should use android pie but also implies that you should use latest pre-march firmware, which for korean variant is actually android Q not pie so its little confusing which you should use, i could be wrong though, thanks alot for this guide though!

9RR said:
I think he's referring to how its a bit confusing how it says you should use android pie but also implies that you should use latest pre-march firmware, which for korean variant is actually android Q not pie so its little confusing which you should use, i could be wrong though, thanks alot for this guide though!
Click to expand...
Click to collapse
If someone can't deal with the level of instruction I provided here, I would very much advise against attempting it as it is inherently very risky. Probably not what anyone wants to here, but it is what it is

This is great news. Has anyone Tested using a LOS GSI or AOSP GSI? I am on verizon and have found with another phone that all GSIs on android version 9 and 10 have "No Sim Card" errors and you can not make calls or send texts (strangely you can receive both). This error wasn't seen with other network versions of the phone (palm phone). I am a little hesitant to go through this process to find out if data doesn't work on LOS 17 or AOSP 10. If anyone on verizon tries this out, please report back on how well the GSIs work, or if you find a specific ROM that works on Verizon.

CaptainElwood said:
This is great news. Has anyone Tested using a LOS GSI or AOSP GSI? I am on verizon and have found with another phone that all GSIs on android version 9 and 10 have "No Sim Card" errors and you can not make calls or send texts (strangely you can receive both). This error wasn't seen with other network versions of the phone (palm phone). I am a little hesitant to go through this process to find out if data doesn't work on LOS 17 or AOSP 10. If anyone on verizon tries this out, please report back on how well the GSIs work, or if you find a specific ROM that works on Verizon.
Click to expand...
Click to collapse
I've used a lot of gsis like bless and caos (use those instead of aosp definitely). I haven't had any data issues

antintin said:
I've used a lot of gsis like bless and caos (use those instead of aosp definitely). I haven't had any data issues
Click to expand...
Click to collapse
But I have a sprint model. I'm pretty sure Verizon people have tried it with no issues already though

antintin said:
If someone can't deal with the level of instruction I provided here, I would very much advise against attempting it as it is inherently very risky. Probably not what anyone wants to here, but it is what it is
Click to expand...
Click to collapse
Hi, thank you very much for this tutorial.
It was my mistake and got a permanent brick. It is true that the vulnerable firmware for kor is android Q and i have achieved root after downgrading to a older Q version. My problem was at step 4 because i used the q kdz and i did not download a separate pie kdz for that step.
Now i hope no one else will make my mistake since i really do not see how to get DL mode active or to switch slots without the USB. Only thing i got is the image that precedes the DL mode and the IMEI display. And since the USB is basically dead i think firehose (even if i had it) would not recover my phone.
I have flashed and unlock many phones and this is my first unrecoverable brick. My first LG though and probably the last.

Marmalux said:
Hi, thank you very much for this tutorial.
It was my mistake and got a permanent brick. It is true that the vulnerable firmware for kor is android Q and i have achieved root after downgrading to a older Q version. My problem was at step 4 because i used the q kdz and i did not download a separate pie kdz for that step.
Now i hope no one else will make my mistake since i really do not see how to get DL mode active or to switch slots without the USB. Only thing i got is the image that precedes the DL mode and the IMEI display. And since the USB is basically dead i think firehose (even if i had it) would not recover my phone.
I have flashed and unlock many phones and this is my first unrecoverable brick. My first LG though and probably the last.
Click to expand...
Click to collapse
I'm very sorry to hear that, but the firehose could almost definitely help you unbrick. I tried to clarify more that it has to be a pie kdz now, because before I just wrote "load your pie kdz" and you probably missed that. There should still be a warranty though, so you could try to use that if you'd like. It might say that yours expired on the website, but you can just click past it.

antintin said:
Spoiler
I'm very sorry to hear that, but the firehose could almost definitely help you unbrick. I tried to clarify more that it has to be a pie kdz now, because before I just wrote "load your pie kdz" and you probably missed that. There should still be a warranty though, so you could try to use that if you'd like. It might say that yours expired on the website, but you can just click past it.
Click to expand...
Click to collapse
Thank you antintin for your reply. You bring me some hope. The warranty will not apply because it is stated clearly that any attempt to BL unlock will void it (I got it from a shop in Spain via Ebay).
But the firehose on the other hand.... When do you think it will be available? And how will i ba able to get it?
Thank you very much!

Marmalux said:
Thank you antintin for your reply. You bring me some hope. The warranty will not apply because it is stated clearly that any attempt to BL unlock will void it (I got it from a shop in Spain via Ebay).
But the firehose on the other hand.... When do you think it will be available? And how will i ba able to get it?
Thank you very much!
Click to expand...
Click to collapse
Other people who bricked while different bl unlock methods were tested sent it in for warranty with no issues. The firehose will be available in November at the earliest probably. Proof of purchase from eBay should be enough, but I don't if there's any lg repair centers in Spain that support phones.

antintin said:
Other people who bricked while different bl unlock methods were tested sent it in for warranty with no issues. The firehose will be available in November at the earliest probably. Proof of purchase from eBay should be enough, but I don't if there's any lg repair centers in Spain that support phones.
Click to expand...
Click to collapse
In Spain there are several. But i`m in Ireland, and here is none ))

Successfully rooted korean variant, thanks for the guide! I was wondering if its okay now to update to newest firmware via LGUP upgrade mode? (I really want the system wide accent color customization in newest firmware, among other things) I assume it should be but i really don't wanna have to redo all this so id rather just ask, thanks in advance!

Can Not Find .kdz file for LG V40 ATT Android 10! Crossflashing has not worked for me

Greetings Community,
In the last few years, I have fallen in love with LG phones. There are many reasons for this that I do not have time to list. I Originally purchased an LG V30 and loved it. But then a few issues emerged such as the headphone jack not working, the charge port being extremely finicky, it not having been officially updated to Android 10 etc.
So, I purchased a GSM unlocked LG V40. What I didn't know about this phone was it was an AT&T GSM unlocked phone that (like other AT&T android devices) does not receive any updates at all unless it is connected through the AT&T network (which I confirmed through much research and contacting AT&T). I then thought it would be as easy as flashing the factory firmware on the device, but oh no; it was no where close to being that easy. After much difficulty with getting the correct and current DLL to work with LGUP, I then went to find the correct kdz file for this device. Only then I found that the android 10 kdz file for the AT&T V405UA was nowhere to be found. After this, I decided to try to flash the Verizon variant for the V405UA only to find the error for crossdl from ATT>VZW.
So this is what I am asking/wondering:
Is it possible that anyone can find the Android 10 kdz file for the AT&T V405UA?
Is there another way to flash a factory Android 10 firmware/os to this phone?
Is there a way to crossflash the VZW version to an ATT phone?
What my phone is currently running:
Android version: 9 (Pie)
Android security patch Level: January 1st, 2020
Software version: V405UA20y
Model #: LM-V405UA
I am most definitely a noob compared to most people on here so go easy on me

No AT&T kdz? That's because it's one of the carriers that doesn't make them available, to anyone, anywhere, at anytime.
Follow this thread to find a backup someone made from qfil. But, there's a number of things one has to know before attempting to flash that backup;
1) You need to install / get to know how to use Qualcomms qfil, there's a specific thread to read about that.
2) There are some partitions (they are in that backup) that YOU ShOULD NOT flash, because they contain imei and serial number.
3) Using qfil to restore a backup is very time consuming, it does have options to load with a rawprogram*.xml, if you have them, but the above backup does not.
4) The V40, in case u may not know, is a 'dual slot' phone. That makes it more complicated to deal with than prior phones.
You don't have to worry about being a 'noob'. No one cares about that. But, you'll find that people will ignore you if you ask questions that are already obviously answered in the threads, or you obviously don't even bother to do a google search to answer your question first.
If you put in the effort, but still find yourself stuck, people will help. If you put in virtually no effort and scream for help, people will recognize that 'entitled' behavior and ignore your questions.
good luck.

AsItLies said:
No AT&T kdz? That's because it's one of the carriers that doesn't make them available, to anyone, anywhere, at anytime.
Follow this thread to find a backup someone made from qfil. But, there's a number of things one has to know before attempting to flash that backup;
1) You need to install / get to know how to use Qualcomms qfil, there's a specific thread to read about that.
2) There are some partitions (they are in that backup) that YOU ShOULD NOT flash, because they contain imei and serial number.
3) Using qfil to restore a backup is very time consuming, it does have options to load with a rawprogram*.xml, if you have them, but the above backup does not.
4) The V40, in case u may not know, is a 'dual slot' phone. That makes it more complicated to deal with than prior phones.
You don't have to worry about being a 'noob'. No one cares about that. But, you'll find that people will ignore you if you ask questions that are already obviously answered in the threads, or you obviously don't even bother to do a google search to answer your question first.
If you put in the effort, but still find yourself stuck, people will help. If you put in virtually no effort and scream for help, people will recognize that 'entitled' behavior and ignore your questions.
good luck.
Click to expand...
Click to collapse
Hey, thanks for the reply. I will certainly look into this thread. I have done quite a bit of research on this but was unable to find anything (mostly because I don't think I looked up the right thing ?) maybe you could point me in the right direction to some more search terms or threads to take a look at. Thanks!

Birdflyer said:
Hey, thanks for the reply. I will certainly look into this thread. I have done quite a bit of research on this but was unable to find anything (mostly because I don't think I looked up the right thing ?) maybe you could point me in the right direction to some more search terms or threads to take a look at. Thanks!
Click to expand...
Click to collapse
Well, there's only three major forums in this group. Question and answers, ROMs, guides. Look in those for topics that have the most comments, start reading.

AsItLies said:
Well, there's only three major forums in this group. Question and answers, ROMs, guides. Look in those for topics that have the most comments, start reading.
Click to expand...
Click to collapse
Ok, I will work on that. Thanks for the suggestion.

Yeah there is not a kdz for att to my knowledge but your best bet is unlock the bootloader (search the forums) and flash the US 20A unlocked pie firmware and flash a android 10 based rom via twrp. (Again search the forum its all readily available)

darkensx said:
Yeah there is not a kdz for att to my knowledge but your best bet is unlock the bootloader (search the forums) and flash the US 20A unlocked pie firmware and flash a android 10 based rom via twrp. (Again search the forum its all readily available)
Click to expand...
Click to collapse
Ok, awesome. I will update both of you guys on what I end up doing, thanks for all the suggestions. I am certainly up to more as well!

can crossflash Android 10 to V405ua Verizon or V405ebw EU or V409N via LG UP Dev

Birdflyer said:
Ok, awesome. I will update both of you guys on what I end up doing, thanks for all the suggestions. I am certainly up to more as well!
Click to expand...
Click to collapse
What kind of problems did you have when cross flashing the verizon kdz?
I have a Sprint cross flashed to verizon and working without any problems

oscarillo said:
What kind of problems did you have when cross flashing the verizon kdz?
I have a Sprint cross flashed to verizon and working without any problems
Click to expand...
Click to collapse
GiaiPhapAndroid said:
can crossflash Android 10 to V405ua Verizon or V405ebw EU or V409N via LG UP Dev
Click to expand...
Click to collapse
darkensx said:
Yeah there is not a kdz for att to my knowledge but your best bet is unlock the bootloader (search the forums) and flash the US 20A unlocked pie firmware and flash a android 10 based rom via twrp. (Again search the forum its all readily available)
Click to expand...
Click to collapse
Hey Sorry I forgot to update you guys on what ended up happening, I found someone who was on AT&T but didn't end up having enough time to have AT&T push the update to the phone. So, I finally just decided to return the device, as it was too much of a hassle. Thanks for all your guys' help.

I see you no longer have the phone but:
Here is your answer to cross flashing to another KDZ. I just did it today on the very same phone that had the very same issue when is came to cross flashing the second time.
https://mylgphones.com/how-to-flash-stock-pie-kdz-firmware-on-lg-v40-thinq-with-lgup.html?amp
These instructions got me where I needed to be with ease. It seems that some KDZ files cross flash easy but cross flashing from them is difficult as I have tried everything from everywhere.
Looking at the CMD line your com port# may be different. and of course your KDZ file may be different also...
====================================================

I assumed that LG made one V40 and each carrier had a different rom, which would listen to their bands only, to save power.
AT&T has ended all their good plans and has focused on the $30 per month and up, which is 3x to 4x more than I was paying for family and employee phone plans with usable but limited data.
So, I want to flash my 4 lg v40 att phones to T-mobile, since the att firmware does not listen to band 71, which is the best band to have in most situations.
I learned how to use lgup and roms. I assumed that you should be able to just flash any att v40 with a v40 tmo rom. However, I get a cross error. More research led me to qfil files and tools that make building your own Linux look like an afternoon job.

Gabriel51 said:
I see you no longer have the phone but:
Here is your answer to cross flashing to another KDZ. I just did it today on the very same phone that had the very same issue when is came to cross flashing the second time.
https://mylgphones.com/how-to-flash-stock-pie-kdz-firmware-on-lg-v40-thinq-with-lgup.html?amp
These instructions got me where I needed to be with ease. It seems that some KDZ files cross flash easy but cross flashing from them is difficult as I have tried everything from everywhere.
Looking at the CMD line your com port# may be different. and of course your KDZ file may be different also...
====================================================
Click to expand...
Click to collapse
degarb said:
I assumed that LG made one V40 and each carrier had a different rom, which would listen to their bands only, to save power.
AT&T has ended all their good plans and has focused on the $30 per month and up, which is 3x to 4x more than I was paying for family and employee phone plans with usable but limited data.
So, I want to flash my 4 lg v40 att phones to T-mobile, since the att firmware does not listen to band 71, which is the best band to have in most situations.
I learned how to use lgup and roms. I assumed that you should be able to just flash any att v40 with a v40 tmo rom. However, I get a cross error. More research led me to qfil files and tools that make building your own Linux look like an afternoon job.
Click to expand...
Click to collapse
Ya, thanks guys for the help. I ended up getting a used OnePlus 7T and have been very happy with it. I also know that when it stops receiving official updates, I will be able to keep on updating it for a while through this amazing community and their custom ROMs.