Database Develop

z3 compact how to root? me confused or me stupid

i am deeply sorry if this is the wrong place or already been answered but i have spent almost 6 hours looking for the right solution.
so the story is i have a Z3 compact which is branded to Vodafone UK (not sure if it is relevant)
attached are images of my about page and the configuration page (where you dial *#*#7378423#*#*)
i also (on my search) have my code from the sony site where i selected my phone, sent an email, entered IMEI number and gave me a code to run using fastboot (this did not work for me)
based on theses settings what program/files/tools do i need to install custom rom, which i guess also will root it (im looking at either paranoid android or lineageOS)

paresh90 said:
i am deeply sorry if this is the wrong place or already been answered but i have spent almost 6 hours looking for the right solution.
so the story is i have a Z3 compact which is branded to Vodafone UK (not sure if it is relevant)
attached are images of my about page and the configuration page (where you dial *#*#7378423#*#*)
i also (on my search) have my code from the sony site where i selected my phone, sent an email, entered IMEI number and gave me a code to run using fastboot (this did not work for me)
based on theses settings what program/files/tools do i need to install custom rom, which i guess also will root it (im looking at either paranoid android or lineageOS)
Click to expand...
Click to collapse
You can't unlock you bootloader mate, the screenshot you put up says so. Meaning no custom kernels, which also means no ROMs that aren't based on stock. You're stuck with MIUI and various other zip-ports. No Lineage or AOSPA etc.
You can root it no problem though. Just use google or whatever, there's a couple of ways to do it.

someone755 said:
You can't unlock you bootloader mate, the screenshot you put up says so. Meaning no custom kernels, which also means no ROMs that aren't based on stock. You're stuck with MIUI and various other zip-ports. No Lineage or AOSPA etc.
You can root it no problem though. Just use google or whatever, there's a couple of ways to do it.
Click to expand...
Click to collapse
thank you for your response thought this would be a dead thread.
a few follow up questions if i may:
1. i asume i can find any post with MIUI in the title while should be compatible
2. i read something about down grade of firmware (is that a possible option for me)
3. in my google searching, would i need to state that my BL is locked

paresh90 said:
thank you for your response thought this would be a dead thread.
a few follow up questions if i may:
1. i asume i can find any post with MIUI in the title while should be compatible
2. i read something about down grade of firmware (is that a possible option for me)
3. in my google searching, would i need to state that my BL is locked
Click to expand...
Click to collapse
Just find a MIUI ROM in the dev section if you want MIUI.
You can install any firmware from Sony using Flashtool. Learn to use it, it's gonna be your friend.
That means you download any FTF file for your phone (there's a thread somewhere with a collection of FTFs), and you can flash it. KitKat, Lollipop, Marshmallow, or Concept.
I don't know how to root really, I just do it the old fashioned way since my bootloader is unlocked (and I pray that never changes). I think you'll have to downgrade to KitKat, which, again, is very easy if you know how to use Flashtool.
Np mate, I know the feeling of dead threads. Just happened by luck that I saw yours and got intrigued by the title lol.

someone755 said:
Just find a MIUI ROM in the dev section if you want MIUI.
You can install any firmware from Sony using Flashtool. Learn to use it, it's gonna be your friend.
That means you download any FTF file for your phone (there's a thread somewhere with a collection of FTFs), and you can flash it. KitKat, Lollipop, Marshmallow, or Concept.
I don't know how to root really, I just do it the old fashioned way since my bootloader is unlocked (and I pray that never changes). I think you'll have to downgrade to KitKat, which, again, is very easy if you know how to use Flashtool.
Np mate, I know the feeling of dead threads. Just happened by luck that I saw yours and got intrigued by the title lol.
Click to expand...
Click to collapse
It's difficult trying to find a post that works for your situation.
Top of your head do you know any good miui ROMs. Light ones
And if I downgrade to kitkat or something will I be able to unlock my BL (or is it compleatly different )
I don't have the phone with me will check tomorrow

paresh90 said:
It's difficult trying to find a post that works for your situation.
Top of your head do you know any good miui ROMs. Light ones
And if I downgrade to kitkat or something will I be able to unlock my BL (or is it compleatly different )
I don't have the phone with me will check tomorrow
Click to expand...
Click to collapse
Haven't used MIUI since 2013 so you'll have to find one by yourself lol. I'm more of an AOSP guy -- if I was forced to use a locked bootloader I'd just install the concept FTF. That's about as light as you can get on this phone.
You can't unlock your bootloader, period. No software hack will help you. At least not from home. You'd need something like a riffbox and extensive knowledge of the phone's bootloader software to unlock it.

someone755 said:
Haven't used MIUI since 2013 so you'll have to find one by yourself lol. I'm more of an AOSP guy -- if I was forced to use a locked bootloader I'd just install the concept FTF. That's about as light as you can get on this phone.
You can't unlock your bootloader, period. No software hack will help you. At least not from home. You'd need something like a riffbox and extensive knowledge of the phone's bootloader software to unlock it.
Click to expand...
Click to collapse
Concept it is
Ok thank you for making it super clear (for me and anyone else reading this. )
It's annoying that the sony website gave me a code to unlock it. I'm sure they could have known from the IMEI number whqt it was and stuff.

paresh90 said:
Concept it is
Ok thank you for making it super clear (for me and anyone else reading this. )
It's annoying that the sony website gave me a code to unlock it. I'm sure they could have known from the IMEI number whqt it was and stuff.
Click to expand...
Click to collapse
I think the carriers lock the bootloaders, not Sony. As far to my knowledge, Sony ships out the devices unlocked, and the carriers decide whether to lock them, but don't report back to Sony. Their site just assumes you don't have a s'hitty carrier.
Best of luck man, and welcome to the Z3C forums!

H811 unbrick help

Hi everyone,
Please forgive any n00b questions.
I got started with rooting / custom ROMs on a Nexus 4, and I didn't realize at the time that this made things really easy and I didn't need to learn very much about how everything worked. Fast forward to last week -- I decided, at long last, that I was tired of using stock MM on my T-Mo G4 / H811. How hard could it be? Probably not much different from playing on my old Nexus 4 right? Lol, maybe not.
So now 72 hours later, my phone is hard bricked and will not enter download mode. and I need some assistance, if anyone would be so kind.
I will try to recount what I did:
To start with, I was using a Mac, so I used Homebrew to install Android platform tools / ADB.
I decided I wanted to try out LineageOS so I went ahead and followed their very clear steps (on LOS wiki) to unlock the bootloader install TWRP. However, TWRP doesn't seem to have an official build for the G4(!) so I had to look up and use one of the betas from this post. Is this where I went off the rails already? [Of course, very stupidly I also failed to make a complete backup of anything before going on ahead. Rookie mistake.]
After unlocking bootloader and flashing my TWRP beta, I was able to boot into TWRP just fine. I followed the normal prescribed steps of doing a Wipe (normal TWRP defaults -- system, cache, etc.?) before flashing the latest LOS nightly (14.1-something) and also the nano-x64 variety of gapps. I rebooted and got stuck with the LOS boot animation. I let this go for 55 minutes, so I am pretty sure it was an actual bootloop, not just the 1st-time-startup and optimization going on.
I rebooted into TWRP and decided to try a different ROM to see if that was the issue. So I wiped again, flashed another ROM (I believe it was a flavor of AOKP 14.1.x), flashed gapps again, and gave it another try. Again got stuck with an endless bootloop (45 minutes).
Since this is my daily driver, I decided to go back to stock. Found this thread, downloaded the MM-debloated zip, pushed to phone, and again Wiped + Flashed. This time, when I hit reboot, my phone was immediately hard-bricked. No startup screen, no nothing. That was quite unexpected. Also, the first time I had ever HARD bricked a device that I was playing with. Yikes!
Since then, I got a hold of a PC, and have been trying to revive the device by flashing an image to the microSD and booting into Download mode, in the form of this thread or this one.
I did get this to work briefly yesterday, or at least I got to Download Mode / Firmware Update screen, and then attempted to run LGUP with the KDZ file. However I ran into an error at about 9%, and couldn't continue -- and then I had to give back my loaner PC for the day. I also noticed that the LG Mobile Support tool was recognizing my phone NOT as an H811 but as something like HX230 or ... whatever it was, it was definitely wrong. Which is worrisome.
Today I'm giving it another try but my phone will not enter Download Mode at all, nor respond in any other way. I'm curious if this is a battery issue? So I am simply charging it for the time being. I also re-formatted the microSD and re-flashed the single .img just to be safe, but still can't get a response out of the phone. On my PC's device manager it is showing up as the common Qualcomm 9008 that a lot of people seem to have seen. No recognition from LG Mobile Support tool, nor from LGUP.
So ... what now?
It's possible that once my battery gets some charge again, maybe I'll be able to enter DL mode. Let's hope so.
However, I am also totally in the dark about which software version I should be using. 20i? 20p? I have no idea what these refer to, and I did not make any prior notes to capture the state that my phone was in before this all began. So IF I get to DL mode I will definitely need further instruction on the CORRECT KDZ FILE to be flashing. Else I will just compound my problems.
ANY tips or suggestions will be appreciated! Thanks so much.

Should have verified being on 20o firmware
Upon further reading, quite obvious, at the top of this thread, I definitely should have followed the Prerequisite steps. I did NOT verify that I was on 20o firmware. "OR RISK BRICKING YOUR DEVICE" is right.
So I bricked my device, in exactly the way I was warned not to do, it seems.
Still, what's the next step? Any thoughts?

freeradical426 said:
Upon further reading, quite obvious, at the top of this thread, I definitely should have followed the Prerequisite steps. I did NOT verify that I was on 20o firmware. "OR RISK BRICKING YOUR DEVICE" is right.
So I bricked my device, in exactly the way I was warned not to do, it seems.
Still, what's the next step? Any thoughts?
Click to expand...
Click to collapse
try search for a fix if not may be @steadfasterX knows how to help you.

Re: searching for unbrick solutions
raptorddd said:
try search for a fix if not may be @steadfasterX knows how to help you.
Click to expand...
Click to collapse
Thanks, I have been looking around for solutions, but can't seem to find anything aside from the unbrick-guides that I've already listed / already attempted.
Will hope for help from @steadfasterX ! Or some other knowledgeable / benevolent party.

freeradical426 said:
Thanks, I have been looking around for solutions, but can't seem to find anything aside from the unbrick-guides that I've already listed / already attempted.
Will hope for help from @steadfasterX ! Or some other knowledgeable / benevolent party.
Click to expand...
Click to collapse
Ok what was the last KDZ file you flashed which had worked? 20o?
As you have hard bricked your device you can try the sdcard method again if it works flash 20o again (of it it was 20o).
If you flash a lower version you will hard brick again.
If the sdcard doesn't work anymore for you you can try to flash with QFIL but beware to use the right one. If you use the wrong one it will convert your device and believe me that's not what you want. I can share the good ones but unfortunately maybe on next week first.
Otherwise search on your own for 9008 unbrick but check the md5sum of the programmer!! Compare it with the Evil one mentioned in my ARB list here: http://tinyurl.com/antirollg4 and DO NOT USE THE EVIL one..
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Ok what was the last KDZ file you flashed which had worked? 20o?
As you have hard bricked your device you can try the sdcard method again if it works flash 20o again (of it it was 20o).
If you flash a lower version you will hard brick again.
If the sdcard doesn't work anymore for you you can try to flash with QFIL but beware to use the right one. If you use the wrong one it will convert your device and believe me that's not what you want. I can share the good ones but unfortunately maybe on next week first.
Otherwise search on your own for 9008 unbrick but check the md5sum of the programmer!! Compare it with the Evil one mentioned in my ARB list here: http://tinyurl.com/antirollg4 and DO NOT USE THE EVIL one..
Click to expand...
Click to collapse
Thanks very much for the guidance! The post that you linked to REALLY helps. Until now I really was not sure what 10n, 20i, 20o, etc. referred to, aside from just various software versions. Having a definition for anti-rollback and further links to explain, really helps! This gives me more information and I might be able to self-resolve from here. I will give it a shot.
As for your question ... unfortunately there was NO instance where I flashed a working KDZ file, and I didn't know (due to my past experience with my Nexus) that I needed to check the STOCK software version of my phone before beginning to play with ROMs. In other words, I have no idea if I was on 20i, 20o, 20p, etc. From what I understand, this makes things a lot more difficult
Having looked at the linked thread just a little bit, it appears that using a 20o KDZ is the best bet -- because I bricked my device using a 20i ROM so I expect it was due to violating the anti-rollback restriction.
I will look into it more closely and come back if I hit another brick wall. Thanks so much!

If anyone cares, here are the ending results of all this ...
#1 Be wary of anti-rollback restrictions before you flash anything to your G4. You WILL brick your phone!
I tried multiple rounds and multiple variations of all the MicroSD card methods that I could find. I could NOT succeed in unbricking my phone.
#2 Luckily ... I was able to convince LG that I was still technically under warranty!
Because I had the stock bootloop issue in May 2017, LG did an in-warranty repair for me, and replaced the motherboard. So last week, I simply told them "my phone is AGAIN unable to charge and will not power on, just like in May". Since it had only been 5-6 months since the first issue, they agreed to replace the motherboard again.
Moral of the story: you can definitely unbrick your phone by having LG replace the mobo XD XD
From here, I think I will just totally avoid doing any rooting or custom ROMs on my totally-stock G4 coming today in the mail. I will cross my fingers and hope we get OEM Nougat in the USA sometime in the next couple of months.
Thanks again for the help everyone!

Going from DRL6 to CRK1

Hey there, I decided to try out the beta but I'm looking to revert to stock Oreo so I can get Pie through OTA. However I have no clue how to do it, I've read a couple threads referencing this but I can't seem to piece together what needs to be done.
Would someone be so kind to post step by step instructions on what I need to do? I'm pretty techy so just basic instructions would be a great help. Thanks and have a great day!

Spectrah said:
Hey there, I decided to try out the beta but I'm looking to revert to stock Oreo so I can get Pie through OTA. However I have no clue how to do it, I've read a couple threads referencing this but I can't seem to piece together what needs to be done.
Would someone be so kind to post step by step instructions on what I need to do? I'm pretty techy so just basic instructions would be a great help. Thanks and have a great day!
Click to expand...
Click to collapse
Download CRK1 with the SamFirm tool
Flash it with patched ODIN 3.13.1

Spectrah said:
Hey there, I decided to try out the beta but I'm looking to revert to stock Oreo so I can get Pie through OTA. However I have no clue how to do it, I've read a couple threads referencing this but I can't seem to piece together what needs to be done.
Would someone be so kind to post step by step instructions on what I need to do? I'm pretty techy so just basic instructions would be a great help. Thanks and have a great day!
Click to expand...
Click to collapse
Download this firmware crk1 from here https://androidfilehost.com/?fid=11410963190603879881 extract the files and you'll see inside of the extracted folder more files that have .md5 on the end of them right click on the files and click rename and just delete the .md5 part only and leave it so it still has the .tar on the end then use the REGULAR NEWEST version of Odin NOT the patched one and then load the files in their respective places AP to AP, BL to BL etc. etc. Then just flash it to the phone while the phone is in download mode and after the successful flash boot into recovery mode and select factory reset so everything is the way it's supposed to be.... Finished!

I really appreciate the help! I'm a bit confused because Mr. Orange is saying use patched ODIN but MrMike is saying not patched version. I'm not sure which version to use then.

Spectrah said:
I really appreciate the help! I'm a bit confused because Mr. Orange is saying use patched ODIN but MrMike is saying not patched version. I'm not sure which version to use then.
Click to expand...
Click to collapse
The patched one may not work and you'll be forced to start over.. The newest version of odin is for the newer bootloader versions and the patched one isn't updated for the newer bootloader versions but you can try it if you want if it doesn't work then start over.

MrMike2182 said:
The patched one may not work and you'll be forced to start over.. The newest version of odin is for the newer bootloader versions and the patched one isn't updated for the newer bootloader versions but you can try it if you want if it doesn't work then start over.
Click to expand...
Click to collapse
Hmm, is there any advantage to using the parched version? It sounds like there's an official version that will get me the desired results from what you're saying.

Spectrah said:
Hmm, is there any advantage to using the parched version? It sounds like there's an official version that will get me the desired results from what you're saying.
Click to expand...
Click to collapse
The patched version is usually used to switch from N950U to N950U1 or the other way.. I would just use the official version if I were you because I ALREADY flashed from 5DRL7 back to N950USQS5CRK1 and it's working perfectly.. But if you want to mess with the patched version you can but like I said if it doesn't work then you have to start over.

MrMike2182 said:
The patched version is usually used to switch from N950U to N950U1 or the other way.. I would just use the official version if I were you because I ALREADY flashed from 5DRL7 back to N950USQS5CRK1 and it's working perfectly.. But if you want to mess with the patched version you can but like I said if it doesn't work then you have to start over.
Click to expand...
Click to collapse
I'm gonna use the patched version, thanks so much for all of your help!

Spectrah said:
I'm gonna use the patched version, thanks so much for all of your help!
Click to expand...
Click to collapse
Must be something wrong with you obviously.. You go and ask for help and then the person who gives you the most details on how to do it and you'd rather listen to someone who gave you a one line answer. LMAO. Actually this is probably my own fault because I should have known better that when someone asks for step by step instructions basically asking someone to hold their hand through the process that they're a problem..

I used the patched version and it works perfectly on the N950U.

Mr. Orange 645 said:
I used the patched version and it works perfectly on the N950U.
Click to expand...
Click to collapse
Well others in the other thread complained that it didn't work but that's why I said it may or may not work I didn't outright say it doesn't work.

MrMike2182 said:
Well others in the other thread complained that it didn't work but that's why I said it may or may not work I didn't outright say it doesn't work.
Click to expand...
Click to collapse
I never said you did. Is there a particular reason you're being so confrontational and taking things so personal? You just bit the OP's head off and called him "a problem," because he didn't take your advice exactly. I didn't even mention you, quote, or refer to you. I was just sharing my experience, yet you jump on and defend yourself. Try to realax a little and have fun.

Mr. Orange 645 said:
I never said you did. Is there a particular reason you're being so confrontational and taking things so personal? You just bit the OP's head off and called him "a problem," because he didn't take your advice exactly. I didn't even mention you, quote, or refer to you. I was just sharing my experience, yet you jump on and defend yourself. Try to realax a little and have fun.
Click to expand...
Click to collapse
That's because too many folks on here want someone to hold their hand through the entire process instead of actually spending the time to learn how to do it on their own and then when you go spend your time to give them the best answers so they don't waste their time running into possible problems that others have stated that they did and then person just decides to go do the opposite then it's like what did you even ask for help for then? I agree that I was a bit of a jerk but that's from constantly dealing with that on here.

MrMike2182 said:
Must be something wrong with you obviously.. You go and ask for help and then the person who gives you the most details on how to do it and you'd rather listen to someone who gave you a one line answer. LMAO. Actually this is probably my own fault because I should have known better that when someone asks for step by step instructions basically asking someone to hold their hand through the process that they're a problem..
Click to expand...
Click to collapse
Unfortunately that was a typo and I meant the non patched version. Obviously you went above and beyond in making sure I was prepared and I really appreciate that. Sorry about the confusion.

Possible to Downgrade LM-V405QA From Pie to Oreo?

Just got a new in the box unit. It was made in 7/2019 and it arrived with Pie installed even though these originally came with Oreo. Is there any way to downgrade mine and, if so, how to do it and were to get a firmware file? Thanks for your help.

Unless I'm mistaken, this thread will tell you how: https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and this thread contains the links to the KDZs (LG speak for stock ROMs): https://forum.xda-developers.com/lg-v40/development/v40-firmware-links-ainzooalgown-t3940600
[NG]Owner

NGOwner said:
Unless I'm mistaken, this thread will tell you how: https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and this thread contains the links to the KDZs (LG speak for stock ROMs): https://forum.xda-developers.com/lg-v40/development/v40-firmware-links-ainzooalgown-t3940600
[NG]Owner
Click to expand...
Click to collapse
Thanks. I do see those threads and those definitely help. But I am still not clear if I can downgrade. Perhaps it is because I am new to LG phones from Samsung and I know that on some Samsung devices, once you go forward you may not be able to go back. So I am just wondering about all that (along with if I can unlock the bootloader, install TWRP, and root on the model 405QA that I have). Cheers!

Using LGUP 1.14 on DEV mode will let you downgrade, matter is flashing cause phones themselves seem not have any issues by downgrading. Personally I've downgraded both my v40 and my older g7 a couple of times, no probs.

smariob said:
Using LGUP 1.14 on DEV mode will let you downgrade, matter is flashing cause phones themselves seem not have any issues by downgrading. Personally I've downgraded both my v40 and my older g7 a couple of times, no probs.
Click to expand...
Click to collapse
Thanks so much for your time and help. I have downloaded LGUP and installed according to this thread <https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858>. When I try to run it, Win10 asks if it is ok, I say yes, and then nothing else happens. Hmmm. I believe this is LGUP 1.16.0.3. No idea what's up. I have the phone attached and in download mode as described here <https://droidrecovery.com/lg-v40-thinq-recovery-mode/>. Grrr.

Try this LG UP version https://forum.xda-developers.com/showpost.php?p=76995781&postcount=26 set the DLL on DEV mode.
As for unlock bootloader question on your other thread, yep so far it's the easiest method to do it. ADVICE: If you haven't touched anything yet I suggest take a bakup of your partitions via QFIL. So if you mess up something (most likely not but you never know) you will be able to restore everything as it was when you got the phone.

smariob said:
Try this LG UP version https://forum.xda-developers.com/showpost.php?p=76995781&postcount=26 set the DLL on DEV mode.
As for unlock bootloader question on your other thread, yep so far it's the easiest method to do it. ADVICE: If you haven't touched anything yet I suggest take a bakup of your partitions via QFIL. So if you mess up something (most likely not but you never know) you will be able to restore everything as it was when you got the phone.
Click to expand...
Click to collapse
Oh thanks so much! That version of LGUP seems to work (after I manually did some file copying that had permission problems from the scripts). I presume that to downgrade - assuming I have a compatible .KDZ - is to use the FOTA upgrade option?
I will look into the backup as you suggest. As a newbie on these devices, there is alot to learn. Cheers

smariob said:
Try this LG UP version https://forum.xda-developers.com/showpost.php?p=76995781&postcount=26 set the DLL on DEV mode.
As for unlock bootloader question on your other thread, yep so far it's the easiest method to do it. ADVICE: If you haven't touched anything yet I suggest take a bakup of your partitions via QFIL. So if you mess up something (most likely not but you never know) you will be able to restore everything as it was when you got the phone.
Click to expand...
Click to collapse
Ok, I see the phone in QFIL. Under the tools menu, I see QCN Backup/Restore. Is this the backup to which you refer? I don't see anything else that looks promising. Sorry for all of my newbie questions.

So, if you are going to do the back up use this guide: https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-partitions-flash-abl-t-mo-t4051249
Follow steps 1 to 10, Backing up _a partitions will do the job _b patitions will be mirrored from those when restore. Data is not mandatory to back up as it will take much time to read the whole partition. Another tip, rename your backed up files so you can identify them properly later.
Then when you are ready you can play with LG UP most of the time you will like to use Partition DL. Use refurbish only to go stock. FOTA is for updating between versions without losing data (nice if you crossflash/loss the ability to OTA on the phone)

smariob said:
So, if you are going to do the back up use this guide: https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-partitions-flash-abl-t-mo-t4051249
Follow steps 1 to 10, Backing up _a partitions will do the job _b patitions will be mirrored from those when restore. Data is not mandatory to back up as it will take much time to read the whole partition. Another tip, rename your backed up files so you can identify them properly later.
Then when you are ready you can play with LG UP most of the time you will like to use Partition DL. Use refurbish only to go stock. FOTA is for updating between versions without losing data (nice if you crossflash/loss the ability to OTA on the phone)
Click to expand...
Click to collapse
I cannot thank you enough for your time and help. I will read up on all this and continue tomorrow morning. Cheers.

smariob said:
So, if you are going to do the back up use this guide: https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-partitions-flash-abl-t-mo-t4051249
Follow steps 1 to 10, Backing up _a partitions will do the job _b patitions will be mirrored from those when restore. Data is not mandatory to back up as it will take much time to read the whole partition. Another tip, rename your backed up files so you can identify them properly later.
Then when you are ready you can play with LG UP most of the time you will like to use Partition DL. Use refurbish only to go stock. FOTA is for updating between versions without losing data (nice if you crossflash/loss the ability to OTA on the phone)
Click to expand...
Click to collapse
Wow! That is alot of partitions and a lengthy backup chore - even without including the _b partitions. You were 100% correct that renaming each file as you go makes this easier. I used the LUN#_the partition-label.bin as I discovered that some labels were re-used in different LUN.
I never would have figured this out without your help. Thanks.
After a brief rest I will move on and try to unlock the bootloader as described here <https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207>.

It's great to know that, once you've done that UL BL would be a piece of a cake.

smariob said:
It's great to know that, once you've done that UL BL would be a piece of a cake.
Click to expand...
Click to collapse
Thanks so much! You might note I have posted in the other thread about troubles getting unlocked. I seem to have successfully sent the v35 bootloader to the phone. I have the QFIL log showing that. But when I go to fastboot mode and try the unlock command, it fails with unknown command. After restoring/sending the backup of the original partition, I tried issuing the same unlock command (not expecting it to work since I should have been back to the original pie bootloader) and I get the exact same error. This makes me wonder if the v35 bootloader is actually getting installed properly. The phone is on the most recent Pie (QA20e) and seems to boot and run fine - even right after I send the v35 bootloader. There were comments that using this bootloader with Pie might have problems and I have never had any so far. So again, I am wondering if the v35 is actually getting into place. A real mystery to me. Thanks!

whitedavidp said:
Wow! That is alot of partitions and a lengthy backup chore - even without including the _b partitions. You were 100% correct that renaming each file as you go makes this easier. I used the LUN#_the partition-label.bin as I discovered that some labels were re-used in different LUN.
I never would have figured this out without your help. Thanks.
After a brief rest I will move on and try to unlock the bootloader as described here <https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207>.
Click to expand...
Click to collapse
In my case, it turned out that the phone was active on the B slot. So I took backups of those partitions as well, flashed the V35 bootloader into B, performed the unlock, re-flashed the Pie bootloader. When I reboot into normal mode, I now see an unlocked warning and it took a very long time for the phone to get started and prompt me to start all over with my Android install. Before I do that I am trying to restore the backup I made of the userdata partition to see if that spares me the whole setup thing. Thanks to all.

Yeah you've made it at least. Good one on figure out B slot was active. Now you're able to go custom roms or just go root.

smariob said:
Yeah you've made it at least. Good one on figure out B slot was active. Now you're able to go custom roms or just go root.
Click to expand...
Click to collapse
Again, thanks so much for all of you help and encouragement. From my pre-purchase research I had anticipated that I could do a dev unlock of the bootloader quite easily. I have rooted with Magisk now and am moving on to see what I can do. Cheers.

smariob said:
Using LGUP 1.14 on DEV mode will let you downgrade, matter is flashing cause phones themselves seem not have any issues by downgrading. Personally I've downgraded both my v40 and my older g7 a couple of times, no probs.
Click to expand...
Click to collapse
Thanks for all of your help and sorry for all the questions.
I am just wondering if you are able to use TWRP/Magisk root on the downgraded v40? In the TWRP thread it indicates that it requires Pie firmware be installed. If I cannot use TWRP/Magisk root on Oreo, then I will not bother trying to downgrade.
Again, thanks so much!

Now that you mention it. V40 TWRP is meant to use with pie... Will not boot on Oreo. I think there are workarounds for that if it's mandatory for you to be in Oreo, but not personally tested'em.

smariob said:
Now that you mention it. V40 TWRP is meant to use with pie... Will not boot on Oreo. I think there are workarounds for that if it's mandatory for you to be in Oreo, but not personally tested'em.
Click to expand...
Click to collapse
Thanks. Certainly not mandatory. So will stick with Pie for now anyway. Again, thanks so much.

Can 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.