Greetings everyone, i go by the name Ainz Ooal Gown. Here i bring you the Official Guide on LGUP to fix a Brick of your device or to simply Cross flash/Upgrade your device from Windows.
First things first if you try this and end up with a brick or your device transforms and tries to take over the world; it's not my fault you messed up not me. So just read all of this thread not just the O.P to, and get out of a bind if you reply with "the thread is too long i wont read it please help" don't expect anything short of "there's a search bar use it"
Second things have changed cross flashing no longer unlocks your Sim capabilities, you must contact your Carrier to have your Sim unlocked. The only other thing you can do is buy the US Unlocked model and root that one.
Third and i can't believe i must add this those of you who have a T-Mobile V40 if you flash a T-Mobile KDZ you'll be fine....if you flash any other KDZ enjoy and expensive Paper weight.
Download These FIles: DLL LGUP UI_Config
No root:
Step 1. Install the provided LGUP.msi (you should now have C:\Program Files (x86)\LG Electronics\LGUP)
Step 2. Install the provided DLL (you should now have C:\Program Files (x86)\LG Electronics\LGUP\model\Common)
Step 3. Extract the LGUP_UI_Config_m250n_[cxz].zip file anywhere on your computer, then copy or move the file to the common folder (the same one the DLL installs too)
Step 4. Enter download mode and flash any KDZ that is compatible with your device with the Refurbish or Upgrade options.
With root:
If you're rooted and BL unlocked, ALWAYS use Partition DL unless you want to go completely unrooted/bootloader relocked.
Download the previous files and LGUPCompatableLAF
Make sure your using fastboot with USB 2.0, it may work with 3.0 but it's better to use 2.0
Step 1. Extract the LGUPCompatibleLAF.rar file anywhere on your computer.
Step 2. Put your phone in fastboot mode. If on Oreo, just power off and hold vol down while plugged in, if on PIE Power off press vol up, while plugged in.
Step 3. In Windows 10 right click the start button and choose either "Command Prompt" or "Command Prompt(Admin)"
Step 4. In the command prompt type cd followed by where you extracted the rar for me it's "cd C:\Users\juanj\Downloads\Flash\LGUPCompatableLAF" ( Windows 7 and older simply when in the extracted folder Hold Shift on your keyboard and right click and choose "open a command prompt here" ).
Step 5. We need to get into the V35 Engineering bootloader, run this command: fastboot.exe set_active b and press enter. (If your on Oreo and have V35 bootloader in Slot_a skip this step.)
Step 6. Reboot, and it should boot straight into the v35 eng if you were already on PIE.
Step 7. Run this command to flash the LGUP Compatible LAF: fastboot.exe flash laf_a laf.img press enter.
Step 8. Now, we need to get back to our A slot, run: fastboot.exe set_active a (again Skip if your already on Oreo with V35Bootloader in Slot_a).
Step 9. Reboot by pressing and holding vol down and power while your device is plugged in (let go of the power button and volume down button and now press and hold vol up before the LG Logo shows up). You should be in download mode and LGUP will work.
Step 10. follow the non root part but use Partition DL, Select all and uncheck abl_a and laf_a to keep the bootloader unlocked in Slot_a then abl_b and laf_b to keep V35 Fastboot access in Slot_b.
Thanks to: @CXZa @maxmotos @Xsavi
"UI_Config.lgl" file for V40
Hello All,
Please find attached an archive containing the "UI_Config.lgl" file for V40 retrieved and modified based on instructions from @CXZa ( @CXZa, thanks a lot for the great job done!).
Instructions:
***
1. Copy the "UI_Config.lgl" file into "*\LGUP\Common" folder
2. Change the file's properties and make it "Read-only" (should already be there)
3. Ignore the "can't open new file" warning by LGUP 1.16
***
Hope this help!
taronhov said:
Hello All,
Please find attached an archive containing the "UI_Config.lgl" file for V40 retrieved and modified based on instructions from @CXZa ( @CXZa, thanks a lot for the great job done!).
Instructions:
***
1. Copy the "UI_Config.lgl" file into "*\LGUP\Common" folder
2. Change the file's properties and make it "Read-only" (should already be there)
3. Ignore the "can't open new file" warning by LGUP 1.16
***
Hope this help!
Click to expand...
Click to collapse
I will add this bit to the OP.....
Works perfectly!
pp342261 said:
Works perfectly!
Click to expand...
Click to collapse
Just so others know were you rooted before this?
Ainz_Ooal_Gown said:
Just so others know were you rooted before this?
Click to expand...
Click to collapse
yes, bl unlocked also :good:
Thanks for posting this. Can we use this to flash any v405 rom (except tmobile) to any lg v405 v40 phone without 9008 mode?
Can we not flash twrp to recovery for the lg v40 as opposed to using the laf partition? I got a copy of twrp.img from vlad for the v40 which looks like was created by Precious Princewill. I haven't tried it yet. Frankly want to make sure there is a working lg up in case i lose recovery. Also not sure how twrp works with PIE. Does it allow you to flash to both slot a or slot b?
Posts like this sometimes makes me wish I didn't get bl unlocked and root.. So much simpler. With lack of anything really interesting to test and play with like crossflashing on the V30 for example, I can't find the motivation to actually do any of this..
neocyke said:
Posts like this sometimes makes me wish I didn't get bl unlocked and root.. So much simpler. With lack of anything really interesting to test and play with like crossflashing on the V30 for example, I can't find the motivation to actually do any of this..
Click to expand...
Click to collapse
if you have TWRP installed i'm currently uploading a Backup with No data of a GSI i have working on the V40
Alibaba0101 said:
Thanks for posting this. Can we use this to flash any v405 rom (except tmobile) to any lg v405 v40 phone without 9008 mode?
Can we not flash twrp to recovery for the lg v40 as opposed to using the laf partition? I got a copy of twrp.img from vlad for the v40 which looks like was created by Precious Princewill. I haven't tried it yet. Frankly want to make sure there is a working lg up in case i lose recovery. Also not sure how twrp works with PIE. Does it allow you to flash to both slot a or slot b?
Click to expand...
Click to collapse
TWRP lets you Flash on the current active Slot, But the current Lineage OS we're working on flashes to the non active Slot for some reason.
Ainz_Ooal_Gown said:
TWRP lets you Flash on the current active Slot, But the current Lineage OS we're working on flashes to the non active Slot for some reason.
Click to expand...
Click to collapse
ThanksQ
Does the current twrp allow backup and restore of the active slot? And how can i tell which is the active slot? Is there a different recovery for each slot? I haven't even looked at what the partition scheme looks like with pie yet.
Alibaba0101 said:
ThanksQ
Does the current twrp allow backup and restore of the active slot? And how can i tell which is the active slot? Is there a different recovery for each slot? I haven't even looked at what the partition scheme looks like with pie yet.
Click to expand...
Click to collapse
yes you can have the older TWRP 3.3.0-0 in one slot and the newer TWRP 3.3.1-0 in the other but you can check your active slot in the reboot section of TWRP
Ainz_Ooal_Gown said:
if you have TWRP installed i'm currently uploading a Backup with No data of a GSI i have working on the V40
Click to expand...
Click to collapse
You know what, I never actually checked whether mine came with TWRP or not (again lack of stuff to flash). Prolly worth a look see.
GSI huh. Would be great if it'd work properly. My local carrier uses bands that US phones don't enable / use which is why all my LG phones run Korean fw. Those are the only ones that play nice, otherwise it's wifi-only-land fer me.
This is one peculiar thing I've noticed with LG phones so far. Even if the phone hw itself supports every single band under the sun (like me old V30), running certain regional fw disables some of them. Specific to the V30 : Logic dictates that you can go into service mode and enable those and alls good yeah? But no, not with LG. You do that, it then locks you onto those bands never auto-switching anymore. Which sucks when you swap sims or roam on other networks. Like.. dude.. WTH??
Successfully crossflashed at&t 8.1 into Korean 9.0. Thanks!
suderujn said:
Successfully crossflashed at&t 8.1 into Korean 9.0. Thanks!
Click to expand...
Click to collapse
Hello, did you do refurbished?
Inerent said:
Hello, did you do refurbished?
Click to expand...
Click to collapse
yep
neocyke said:
You know what, I never actually checked whether mine came with TWRP or not (again lack of stuff to flash). Prolly worth a look see.
GSI huh. Would be great if it'd work properly. My local carrier uses bands that US phones don't enable / use which is why all my LG phones run Korean fw. Those are the only ones that play nice, otherwise it's wifi-only-land fer me.
This is one peculiar thing I've noticed with LG phones so far. Even if the phone hw itself supports every single band under the sun (like me old V30), running certain regional fw disables some of them. Specific to the V30 : Logic dictates that you can go into service mode and enable those and alls good yeah? But no, not with LG. You do that, it then locks you onto those bands never auto-switching anymore. Which sucks when you swap sims or roam on other networks. Like.. dude.. WTH??
Click to expand...
Click to collapse
This has been true of almost every manufacturer now. There are no truly unlocked world phones, at least not in the US. Each firmware is locked to the bands for that carrier with little to no ability to cross flash the radios or enable bands. I have at&t in the USA and they have some sort of deal with most carriers that don't allow their firmware to be posted and their phones are all bootloader locked. You can cross flash them and get the bootloader unlocked, but you will always lose a few bands.
The LG v40 US unlocked firmware appears to have more bands than most (v405qa) which is what i cross flashed to my lg v40. It supports:
LTE Bands: 1/2/3/4/5/7/8/12/13/14/17/20/25/26/28/29/30/38/39/40/41/46/66/71;
WCDMA Bands 1/2/4/5/8;
GSM 850/900/1800/1900 MHz; 800 MHz
CDMA; 1.9 GHz CDMA PCS; Secondary 800 MHz CDMA
https://www.lg.com/us/cell-phones/lg-V405QA7-unlocked-v40
Although after cross flashing this rom, my phone firmware still show v405ua model#. So I'm not sure that it fully has worked or if the v405qa is just a varation of the v405ua rom.
Alibaba0101 said:
This has been true of almost every manufacturer now. There are no truly unlocked world phones, at least not in the US. Each firmware is locked to the bands for that carrier with little to no ability to cross flash the radios or enable bands. I have at&t in the USA and they have some sort of deal with most carriers that don't allow their firmware to be posted and their phones are all bootloader locked. You can cross flash them and get the bootloader unlocked, but you will always lose a few bands.
The LG v40 US unlocked firmware appears to have more bands than most (v405qa) which is what i cross flashed to my lg v40. It supports:
LTE Bands: 1/2/3/4/5/7/8/12/13/14/17/20/25/26/28/29/30/38/39/40/41/46/66/71;
WCDMA Bands 1/2/4/5/8;
GSM 850/900/1800/1900 MHz; 800 MHz
CDMA; 1.9 GHz CDMA PCS; Secondary 800 MHz CDMA
https://www.lg.com/us/cell-phones/lg-V405QA7-unlocked-v40
Although after cross flashing this rom, my phone firmware still show v405ua model#. So I'm not sure that it fully has worked or if the v405qa is just a varation of the v405ua rom.
Click to expand...
Click to collapse
It will always show your base model
Ainz_Ooal_Gown said:
It will always show your base model
Click to expand...
Click to collapse
Is this different than the v30 then? After cross flashing us998 on my sprint v30, it now shows us998 as the model#.
Alibaba0101 said:
Is this different than the v30 then? After cross flashing us998 on my sprint v30, it now shows us998 as the model#.
Click to expand...
Click to collapse
Sorry serial number should always be the same but flashing US Unlocked KDZ which is a V405QA doesn't change the Sprint V405UA to a QA....i forget if it was different on the V30 or not
Related
I'm about to buy a used Moto X XT1060 in a couple of days. I understand thats the Verizon variant of the phone.
I wanted to make sure that this phone will work fine on GSM and 3G networks in my country. My country uses 850/1800 for GSM, 2100 for 3G and 1800 (Band 3) for LTE. I know that LTE wont work cause this device doesnt have band 3 but Im quite happy with 3G.
Can you guys please confirm that 3G will work fine on this phone? Ive found some threads here on XDA from people who are having issues using 3G data on this phone.
http://en.wikipedia.org/wiki/Moto_X_(1st_generation)#Variants
XT1060
CDMA Bands: 850/1900
GSM Bands: Quad
UMTS Bands: 850/900/1900/2100
LTE Bands: 4/13
All variants support four 2G GSM bands 850/900/1800/1900.
The XT1050 is a regional device for smaller carriers but uses identical bands.
The Verizon XT1060 is CDMA/GSM variant that is SIM unlocked out of the box. To use the XT1060 on a GSM carrier, you need to force its radio to GSM and the Verizon firmware will always tell you its a "non-verizon sim" inserted in the phone.
It supports the following frequencies..
CDMA = 800/1900
GSM/GPRS/Edge (aka 2G/2.5G) = 850/900/1900/2100 MHz
UMTS/HSPA (aka 3G) = 850/900/1900/2100 Mhz
HSPA+ (aka 4G) = 850/900/1900/2100 Mhz
4G LTE = Band 4 and 13.
When using on GSM carriers, it will get the fastest connection based on what the phone supports vs what the carrier uses.
To be honest, If you want to use it on a GSM carrier, you're better off getting the XT1053, or other GSM unlocked X. And.. take a look at this thread... http://forum.xda-developers.com/moto-x/moto-x-qa/xt1053-xt1060-developer-edition-t3057585
Hey guys! Thanks for the help @fury683 and especially @KidJoe
Fortunately, I'm very well versed with the frequencies supported by the phone.
And my first choice would be to try and get a XT1052 - the international variant.
Unfortunately, in my city, the only variant available is the XT1060 and the too the retail version.
All I wanted to confirm was whether the Verizon Firmware will give me any problems like not detecting my sim or not connecting to 3G networks (local networks use 2100 for both HSPA & HSPA+ so theoretically it shouldn't have any problems).
Also, can I root it? There's a 90% chance that it'll be running 4.2.2 so I've heard there's the Sunshine unlocking method or something which can help me unlock the bootloader (unless the previous owner already did it; in which case it'll be a blessing!)
And is there anyway I can confirm if the phone is refurbished (whether it has been opened at any point in its life)?
usmanshahid said:
Hey guys! Thanks for the help @fury683 and especially @KidJoe
Fortunately, I'm very well versed with the frequencies supported by the phone.
And my first choice would be to try and get a XT1052 - the international variant.
Unfortunately, in my city, the only variant available is the XT1060 and the too the retail version.
All I wanted to confirm was whether the Verizon Firmware will give me any problems like not detecting my sim or not connecting to 3G networks (local networks use 2100 for both HSPA & HSPA+ so theoretically it shouldn't have any problems).
Also, can I root it? There's a 90% chance that it'll be running 4.2.2 so I've heard there's the Sunshine unlocking method or something which can help me unlock the bootloader (unless the previous owner already did it; in which case it'll be a blessing!)
And is there anyway I can confirm if the phone is refurbished (whether it has been opened at any point in its life)?
Click to expand...
Click to collapse
The XT1060 will work on GSM for carriers supporting/using the "standard 4" (850/900/1900/2100 MHz). You MIGHT have to manually enter your APN settings.
As for rooting, If the phone has 4.4.2 or lower, and has NEVER had 4.4.4 on it, you can use Sunshine to unlock the bootloader, then root. IF you receive the phone and it has 4.4.4 on it, you will not be able to unlock the bootloader. And there is no root method for 4.4.4 with a locked bootloader.
I found this beautiful AT&T Moto X today. And before I finalize the deal in a day or two, I want to run a few things by you guys;
1. The phone is running '165.44.1.ghost_att.ATT.en.US' - which is 4.4.2, right?
The bootloader is locked with a Status '0'. So I guess rooting is out of the question, right?
2. When I opened the phone in fastboot, it showed the following bootloader info;
30.B4 (sha-a542ee0)
What does that mean, exactly?
3. Under the 'Kernel Version', it showed some numbers and this;
[email protected]#1
a date stamp
^What does this mean?
I had the phone in my hand for about a good twenty minutes. It was in a very good condition. Had the AT&T logo and a tiny "assembled in USA" stamp on the back. It had a couple of AT&T apps as well.
So what do you guys think? Should I go for it? And are there any other things I should check before I cough up the cash?
And is there any way I can check NFC in the store?
Oh and did the new XT1058 come as a network locked device? Will I be able to run it on my local networks without any locking issues? (all frequency bands available on the phone are supported in my country!)
@KidJoe The phone was showing its IMEI in the "About Phone" tab in the settings menu.
So that should indicate its free from that dead IMEI issue that some of the other guys on XDA faced, right?
Also, I've heard the Rogers stock ROM is almost completely free of bloat. So can I flash a Rogers 4.4.2 SBF without unlocking the bootloader on the phone?
usmanshahid said:
I found this beautiful AT&T Moto X today. And before I finalize the deal in a day or two, I want to run a few things by you guys;
1. The phone is running '165.44.1.ghost_att.ATT.en.US' - which is 4.4.2, right?
The bootloader is locked with a Status '0'. So I guess rooting is out of the question, right?
Click to expand...
Click to collapse
That is correct. Its 4.4.2
usmanshahid said:
2. When I opened the phone in fastboot, it showed the following bootloader info;
30.B4 (sha-a542ee0)
What does that mean, exactly?
Click to expand...
Click to collapse
That is the bootloader version. Its consistent with 4.4.2... WHICH IS GOOD!!!
Use Sunshine to unlock the bootloader, then you can root no matter what rom is on your phone.
usmanshahid said:
3. Under the 'Kernel Version', it showed some numbers and this;
[email protected]#1
a date stamp
^What does this mean?
Click to expand...
Click to collapse
I'm not sure the Kernel Version for the ATT roms. Sorry.
usmanshahid said:
I had the phone in my hand for about a good twenty minutes. It was in a very good condition. Had the AT&T logo and a tiny "assembled in USA" stamp on the back. It had a couple of AT&T apps as well.
So what do you guys think? Should I go for it? And are there any other things I should check before I cough up the cash?
And is there any way I can check NFC in the store?
Oh and did the new XT1058 come as a network locked device? Will I be able to run it on my local networks without any locking issues? (all frequency bands available on the phone are supported in my country!)
@KidJoe The phone was showing its IMEI in the "About Phone" tab in the settings menu.
So that should indicate its free from that dead IMEI issue that some of the other guys on XDA faced, right?
Also, I've heard the Rogers stock ROM is almost completely free of bloat. So can I flash a Rogers 4.4.2 SBF without unlocking the bootloader on the phone?
Click to expand...
Click to collapse
If you do NOT take any updates, you can unlock the bootloader using Sunshine, and then you're free to upddate, and root as you wish.
To test NFC in "store", if you have a fitbit Flex, Force or Charge, install the fitbit app on the phone, tap your fitbit device. Does the app launch? If yes, NFC is working fine. I don't know of another way.
The XT1058 is SIM Locked (aka carrier locked), but you can purchase a SIM unlock code on line cheap, unless you can get ATT to provide it to you (you have to meet their conditions).
You can NOT flash anything but stock Moto XT1058 for ATT rom unless you unlock the bootloader.
KidJoe said:
That is correct. Its 4.4.2
That is the bootloader version. Its consistent with 4.4.2... WHICH IS GOOD!!!
Use Sunshine to unlock the bootloader, then you can root no matter what rom is on your phone.
I'm not sure the Kernel Version for the ATT roms. Sorry.
If you do NOT take any updates, you can unlock the bootloader using Sunshine, and then you're free to upddate, and root as you wish.
To test NFC in "store", if you have a fitbit Flex, Force or Charge, install the fitbit app on the phone, tap your fitbit device. Does the app launch? If yes, NFC is working fine. I don't know of another way.
The XT1058 is SIM Locked (aka carrier locked), but you can purchase a SIM unlock code on line cheap, unless you can get ATT to provide it to you (you have to meet their conditions).
You can NOT flash anything but stock Moto XT1058 for ATT rom unless you unlock the bootloader.
Click to expand...
Click to collapse
Thanks for all your help!
I got the phone today. It's on 4.4.2 and is already SIM unlocked. I plan to unlock the bootloader after a few days!
usmanshahid said:
Thanks for all your help!
I got the phone today. It's on 4.4.2 and is already SIM unlocked. I plan to unlock the bootloader after a few days!
Click to expand...
Click to collapse
Cool, just make sure you do NOT take any Over The Air Updates. Once you get 4.4.4 on there, you wont be able to bootloader unlock an ATT XT1058.
@KidJoe
Dude, I ran into a problem with Sunshine. They don't accept my credit card and I don't have a paypal account.
I'm working on getting a new card, but in the mean time I wanted to ask if I could use the Pie hack to temporarily root the phone to remove the AT&T bloatware.
Would that work?
usmanshahid said:
@KidJoe
Dude, I ran into a problem with Sunshine. They don't accept my credit card and I don't have a paypal account.
I'm working on getting a new card, but in the mean time I wanted to ask if I could use the Pie hack to temporarily root the phone to remove the AT&T bloatware.
Would that work?
Click to expand...
Click to collapse
Yes, but keep in mind that TowelPie is a temp root and doesn't disable write protection. So, Boot, root, remove the bloat, but if you reboot the phone (or power off/on), bloat returns and you need to re-root
@KidJoe
I unlocked my phone's (ATT XT1058) bootloader recently using Sunshine.
Unfortunately, after I updated it to 4.4.4, it somehow got network locked.
Can I remove the network lock by flashing the stock ROM of the international Moto X (XT1052)?
usmanshahid said:
@KidJoe
I unlocked my phone's (ATT XT1058) bootloader recently using Sunshine.
Unfortunately, after I updated it to 4.4.4, it somehow got network locked.
Can I remove the network lock by flashing the stock ROM of the international Moto X (XT1052)?
Click to expand...
Click to collapse
Flashing the rom from a different model will not sim unlock you.
KidJoe said:
Flashing the rom from a different model will not sim unlock you.
Click to expand...
Click to collapse
So how do I SIM unlock my phone? Besides getting the code from ATT.
Is there any way to do it for free?
Thank you for your help!
EDIT: In many of your threads you've warned people to not attempt to downgrade the ROM. Meaning I can't flash a Stock 4.4.2 SBF after I've updated the phone to 4.4.4.
But what if flash a custom ROM like cyanogenmod and then attempt to flash the stock 4.4.2 SBF. Will it still brick my phone?
usmanshahid said:
@KidJoe
Dude, I ran into a problem with Sunshine. They don't accept my credit card and I don't have a paypal account.
I'm working on getting a new card, but in the mean time I wanted to ask if I could use the Pie hack to temporarily root the phone to remove the AT&T bloatware.
Would that work?
Click to expand...
Click to collapse
You can use Western-Union to transfer your payment to the sunshine developers... Im also from Pakistan and Unlocked my bootloader through sunshine by using the western union payment method... You dont need to work hard for a new credit card..
usmanshahid said:
So how do I SIM unlock my phone? Besides getting the code from ATT.
Is there any way to do it for free?
I just spent around $35 on Sunshine (the $10 extra was for transferring the money from my country).
It may not sound like much, but it's a lot in my country.
Click to expand...
Click to collapse
I don't have anything I can suggest to SIM unlock the XT1058 for free. Some services online sell SIM unlock codes, that would be the only thing I can suggest.
usmanshahid said:
EDIT: In many of your threads you've warned people to not attempt to downgrade the ROM. Meaning I can't flash a Stock 4.4.2 SBF after I've updated the phone to 4.4.4.
But what if flash a custom ROM like cyanogenmod and then attempt to flash the stock 4.4.2 SBF. Will it still brick my phone?
Click to expand...
Click to collapse
CM11, CM12, or any ROM based on AOSP, only flash SYSTEM, and do not touch gpt.bin or the critical parts of motoboot.img. So if you go from Moto 4.4.4 -> CM, you still have parts of the Moto 4.4.4 on there... So later if you go CM -> Moto 4.4.2 SBF, you're still at risk of bricking.
And the next question you will likely ask is... "what if I skip those parts"... To that I say... Read items 11, 13, 14, 16, and 17 at -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
KidJoe said:
I don't have anything I can suggest to SIM unlock the XT1058 for free. Some services online sell SIM unlock codes, that would be the only thing I can suggest.
CM11, CM12, or any ROM based on AOSP, only flash SYSTEM, and do not touch gpt.bin or the critical parts of motoboot.img. So if you go from Moto 4.4.4 -> CM, you still have parts of the Moto 4.4.4 on there... So later if you go CM -> Moto 4.4.2 SBF, you're still at risk of bricking.
And the next question you will likely ask is... "what if I skip those parts"... To that I say... Read items 11, 13, 14, 16, and 17 at -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
Click to expand...
Click to collapse
Thank you for all your help and advice. I really appreciate it!
@KidJoe
Sir, I went through your blog on cdmaforums and I have a couple of questions.
1. Due to the GPT.BIN issue, will all the nandroid backups I made using TWRP on 4.4.4 become useless after I update to Lollipop in future?
2. If (after its released), I take the Lollipop OTA file, extract it and only flash the system and boot images will I still have the GPT.BIN issues?
Cause technically, I will have the gpt.bin file from 4.4.4 and all my nandroid backups should work just fine, no?
Found another thread where you warned us not to try this.
3. Supposedly while messing about with my phone, I brick it. Can I get it back to normal?
I found a method to do this on your blog, but I was wondering if it could be used to recover from the messed up gpt.bin files?
[I want to try the thing I mentioned in point 2 above so I need to know if I'll be able to recover my phone if something happens.]
4. What is NON-HLOS.BIN? I found this file in a 4.4.4 SBF that I extracted. Didn't flash it - I was moving from ATT 4.4.4 to EU 4.4.4 so I guess it wouldn't have made much of a difference.
5. I have a ATT phone which was carrier locked. Will erasing the modemst partitions re-activate the modem lock?
6. After I've downloaded an OTA via the system update option on my phone, is there anyway to extract that OTA from the /cache partition?
7. I had a stock ATT 4.4.4 ROM from which I switched to the stock EU 4.4.4 ROM (I didn't flash the entire EU SBF because TWRP was giving an error - MD5 sums didn't match - so I extracted the system and boot partitions and flashed those). So now, as I understand, if I get an official 5.1 OTA, all I have to do is flash the stock recovery and install the OTA after which I can re-flash TWRP again. That correct, or am I missing something?
Thank you!
usmanshahid said:
@KidJoe
Sir, I went through your blog on cdmaforums and I have a couple of questions.
1. Due to the GPT.BIN issue, will all the nandroid backups I made using TWRP on 4.4.4 become useless after I update to Lollipop in future?
2. If (after its released), I take the Lollipop OTA file, extract it and only flash the system and boot images will I still have the GPT.BIN issues?
Cause technically, I will have the gpt.bin file from 4.4.4 and all my nandroid backups should work just fine, no?
Found another thread where you warned us not to try this.
3. Supposedly while messing about with my phone, I brick it. Can I get it back to normal?
I found a method to do this on your blog, but I was wondering if it could be used to recover from the messed up gpt.bin files?
[I want to try the thing I mentioned in point 2 above so I need to know if I'll be able to recover my phone if something happens.]
4. What is NON-HLOS.BIN? I found this file in a 4.4.4 SBF that I extracted. Didn't flash it - I was moving from ATT 4.4.4 to EU 4.4.4 so I guess it wouldn't have made much of a difference.
5. I have a ATT phone which was carrier locked. Will erasing the modemst partitions re-activate the modem lock?
6. After I've downloaded an OTA via the system update option on my phone, is there anyway to extract that OTA from the /cache partition?
7. I had a stock ATT 4.4.4 ROM from which I switched to the stock EU 4.4.4 ROM (I didn't flash the entire EU SBF because TWRP was giving an error - MD5 sums didn't match - so I extracted the system and boot partitions and flashed those). So now, as I understand, if I get an official 5.1 OTA, all I have to do is flash the stock recovery and install the OTA after which I can re-flash TWRP again. That correct, or am I missing something?
Thank you!
Click to expand...
Click to collapse
Except for NON-HLOS.BIN, What you are asking is pretty much covered in -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
but I'll reply here anyway...
1. You could restore them, BUT once you have a newer ROM installed on the phone, due to the mismatch of GPT.bin and Motoboot.img parts of the phone, you'll likely encounter bugs and potentially some features not working (due to the mismatch between the GPT and Motoboot parts and the rest of your rom, and the mismatch of any other parts of the phone not included in the nandroid back up made with TWRP).
2. Although you scratched and said you found the thread... Again, see my answer to #1.
3. There are varying degrees of "bricking." If you still can access the phone via fastboot, in some cases recovery is as simple as re-flashing the SBF that matches the NEWEST version you had on your phone. Other cases its much harder than that, and still other cases you can't recover at all. We've seen it all.
4. it either IS or IS RELATED TO the MODEM of the phone.
5. I'm sorry, I do not know for sure.
6. After downloading, but before installing, the OTA update ZIP file is stored on the phone in /cacahe folder. You need to be rooted to access this folder. If you are rooted, you can copy this file to /SDcard to then copy it to your PC or elsewhere.
7. First off, TWRP doesn't work with flashing IMG files from inside an SBF so I'm not sure what you were trying there. But anyway... IF you used mfastboot to flash EU's System.IMG and BOOT.IMG to your phone, IF you get notified for an available update, it will be the update for the EU ROM. It will be interesting to see what happens. Due to the mix-matched parts on your phone (system/boot from EU, rest from ATT USA), the pre-flash validation might fail, and the OTA wont install. However, IF enough of your phone matches the EU rom, then the update will install and PATCH files/parts on the phone with the EU version, then you may be stuck on the EU version..
KidJoe said:
7. First off, TWRP doesn't work with flashing IMG files from inside an SBF so I'm not sure what you were trying there. But anyway... IF you used mfastboot to flash EU's System.IMG and BOOT.IMG to your phone, IF you get notified for an available update, it will be the update for the EU ROM. It will be interesting to see what happens. Due to the mix-matched parts on your phone (system/boot from EU, rest from ATT USA), the pre-flash validation might fail, and the OTA wont install. However, IF enough of your phone matches the EU rom, then the update will install and PATCH files/parts on the phone with the EU version, then you may be stuck on the EU version..
Click to expand...
Click to collapse
I'm sorry, I should have been more clear.
TWRP was giving errors so I opened the zip file on a computer and flashed the system.img and boot.img via the fast boot command.
I had flashed the recovery.img as well, but that got overwritten when I flashed TWRP again. Pretty much all that was left was gpt.bin file, non-hlos.bin, fsg.mbn and motoboot.img.
As I understand it, motoboot.img is the bootloader and gpt.bin is a partition table and both these files will be the same for all 4.4.4 ROMS.
And non-hlos.bin and fsg.mbn are modem files which should also be the almost same for both EU and ATT ROMS. Except maybe having a modem lock or something on the ATT version.
Before I take the OTA, I'll flash the recovery.img from the EU 4.4.4 SBF which I unzipped to prevent clashes.
Do you think the rest of the files would be enough to cause the pre flash validation check to fail?
Could you elaborate on what you mean by 'stuck on the EU version'?
And would you recommend that I take the OTA, provided I get one?
Thank you!
In the previous thread, we discussed a method to convert T-Mobile 6T's to the international variant, sort of, but it required an unlocked bootloader, which itself requires a SIM unlock which T-Mobile gives people a hard time about.
However, it is through @Dark Nightmare and @iaTa's efforts that we've come this far. Today, I share with everyone a new method to turn a T-Mobile 6T into an international variant. One that does NOT require an unlocked bootloader or a SIM unlock!
Before you proceed: Following the steps below WILL wipe your phone. Please backup all of your important files from the phone before proceeding.
Here are the steps:
1) Download 6T MsmDownloadTool v4.0.58 (OOS v9.0.11) provided by @iaTa
2) Download patched flasher tools here: https://drive.google.com/open?id=1dYuVxnf_J97KPrRt6KEBOjau1BRvtnJQ (the patches simply remove checks that allow all the images to be flashed on the phone, I've personally tested the "MsmDownloadTool V4.0_factory_patched.exe" but not the "MsmDownloadTool V4.0_factory_mcl_op1_patched.exe" variant. You can do a binary diff on the EXEs against the originals in case there's any issues with trust.
3) Shut down your T-Mobile 6T completely
4) Press and hold Volume Up and Volume down keys simultaneously
5) With those two buttons held down, plug in your USB cord to your PC
6) Ensure that the USB drivers for Qcom download mode are installed and working (available in the MSMDownloadTool thread)
7) Extract the patched tools EXEs to the same directory as where you extracted the MSMDownloadTool
8) Run "MsmDownloadTool V4.0_factory_patched.exe" (or the other one, if you're feeling adventurous)
9) Click "Start" when you're ready to start patching the phone
10) After about 5 minutes it will finish its job and reboot the phone
11) Phone will boot normally, but no more T-Mobile logo, and instead there is the OxygenOS generic logo
12) Now your T-Mobile 6T is now running identical software to the unlocked 6T sold directly by OnePlus, and running the latest software (OxygenOS 9.0.11 at the time of this writing). You can even participate in Open Betas if you'd like, and the "Local Upgrade" feature is now enabled and working.
13) ???
14) Profit
Hope this helps somebody out.
It definitely works.
If you want to unlock bootloader after it's converted, then it's just a simple fastboot oem unlock WITHOUT having to wait 7 days for OnePlus unlock bin. Just like the 6T sold by OnePlus directly. And you can even load a dual-SIM tray and both SIM slots work normally.
This is great news! Did this method override the critical partitions in your test to fully convert? Did it become a full conversion or is it just another cool method to use the international Oxygen OS? You think OTA will work as normal now as well instead of doing a local upgrade and etc? Great job and excuse the numerous questions. I'm just curious and excited about this. I've been lurking in these related threads all this time and watching them progress. Lol
@AnonymousTipster change the title from "conversation" to "conversion".
Amazing guide by the way, nice job.
My tmo variant 6T is carrier unlocked and bootloader unlocked and converted to international via the old conversion method downloading the full OTA and flashing the "flash all" bin.
By using this MSM tool, after it locks up my bootloader again, can I still use my old unlock bin? Or will I have to request a new bin key from OnePlus?
I just tested this and can happily confirm that it works!!! Thank you!!!
lemonspeakers said:
My tmo variant 6T is carrier unlocked and bootloader unlocked and converted to international via the old conversion method downloading the full OTA and flashing the "flash all" bin.
By using this MSM tool, after it locks up my bootloader again, can I still use my old unlock bin? Or will I have to request a new bin key from OnePlus?
Click to expand...
Click to collapse
The answer is two posts above yours. As the whole phone had been rewrote you have the international version and therefore don't need any bin key.
Besides using Magisk or another Launcher, is there a way to maintain the Google Now tab when swiping to the far right?
So, it's fully and 100% conversion? Meaning that full and incremental OTA's can get them worry free?
imrock666 said:
So, it's fully and 100% conversion? Meaning that full and incremental OTA's can get them worry free?
Click to expand...
Click to collapse
Won't know until the next OTA is released, to date we are unable to get OTAs, but local upgrade works fine.
Dark Nightmare said:
Won't know until the next OTA is released, to date we are unable to get OTAs, but local upgrade works fine.
Click to expand...
Click to collapse
Ok, so we will have to test until next one comes out? Gotcha!
Just did the conversion, so far so good. Running the OPBackup/Restore to get everything setup.
I was running 9.06 for a while then switched back to the T-mobile rom.
Yesterday I tried to convert to 9.011
The phone would reboot itself right after I got to the setup screen so I MSM back to T-Mobile rom.
Does anyone know if this method would correct that bug?
Holy s h i t
Nice work! I am elated the project has come this far!..nicely done guys! I'll guinea pig it up with the other exe later.
This is great news!! Well try it out today as well.. Sidebar here.. Will the international firmware support a double SIM tray or is the hardware the sticking point?
Thanks again
Excellent job... Can't wait to get home and switch.
Good bye... T-Mobile...No more waiting for your update!!! :silly:
This is awesome, thank you for the post! So after converting, we can unlock the bootloader and flash a custom kernel the same way? I was tempt on keeping my bootloader locked to keep HD videos for Netflix and any other app. I hear it's not safe to flash a custom kernel and then re-lock bootloader? Any advice would be nice.
Nonetheless, glad to see we can convert without having to unlock the bootloader! Cheers!
Flyinace2000 said:
Just did the conversion, so far so good. Running the OPBackup/Restore to get everything setup.
Click to expand...
Click to collapse
Questions about using the OPBackup/Restore as this is my first OP phone. Sorry if I sound dumb LOL, Just never used OPBackup/Restore before...Thanks for any help.
Do I need to setup an account on the OP site to backup?
When doing a restore do you skip during setup/sign in as far as all apps being downloaded from google?
And does the OPBackup/Restore restore all apps and settings putting the phone right back where it was before?
TheKnux said:
@AnonymousTipster change the title from "conversation" to "conversion".
Amazing guide by the way, nice job.
Click to expand...
Click to collapse
Thanks, had a brain fart when I wrote it
zerosim said:
This is awesome, thank you for the post! So after converting, we can unlock the bootloader and flash a custom kernel the same way? I was tempt on keeping my bootloader locked to keep HD videos for Netflix and any other app. I hear it's not safe to flash a custom kernel and then re-lock bootloader? Any advice would be nice
Click to expand...
Click to collapse
Yes you can unlock the bootloader after the conversion and flash anything you'd like at that point. However I don't recommend relocking your phone if you've flashed anything custom as that could leave your phone in a soft bricked state and you'd have to wipe your phone again with msm tool.
I did the crossflash of my lg v40 to the US unlocked pie V405UA20a very very simply without unlocking bootloader, root or some other step. Everything works great, my imei was not deleted, nor my serial number. just flash the kdz by installing lgup and ... can i help you to do the crossflash
Everything works perfect but there is no option for Wi-Fi calls? someone knows?
Hello
EddiePR said:
I did the crossflash of my lg v40 to the US unlocked pie V405UA20a very very simply without unlocking bootloader, root or some other step. Everything works great, my imei was not deleted, nor my serial number. just flash the kdz by installing lgup and ... can i help you to do the crossflash
Everything works perfect but there is no option for Wi-Fi calls? someone knows?
Click to expand...
Click to collapse
So could you explain how you did the crossflash with the bootloader not being unlocked. I have LGUP installed and the US unlocked KDZ file. It failed for me.
Which guide did you use or if you care to explain the steps here. Thanks!
EDIT: Figured it out.
New question, are you able to put TWRP on your phone with current methods out there? if so, how?
Will OTA still work?
conmonks said:
So could you explain how you did the crossflash with the bootloader not being unlocked. I have LGUP installed and the US unlocked KDZ file. It failed for me.
Which guide did you use or if you care to explain the steps here. Thanks!
EDIT: Figured it out.
New question, are you able to put TWRP on your phone with current methods out there? if so, how?
Click to expand...
Click to collapse
I have not tried TWRP. just the crossflash
jimmyStoo said:
Will OTA still work?
Click to expand...
Click to collapse
I can't confirm if the OTA works since there is no new version yet
EddiePR said:
I can't confirm if the OTA works since there is no new version yet
Click to expand...
Click to collapse
Your device was unlocked before you Crossflashed?
0x0null said:
Your device was unlocked before you Crossflashed?
Click to expand...
Click to collapse
no. flashing the US unlocked rom no sim unlocks. but it no longer shows the uicc unlock option in settings.
conmonks said:
So could you explain how you did the crossflash with the bootloader not being unlocked. I have LGUP installed and the US unlocked KDZ file. It failed for me.
Which guide did you use or if you care to explain the steps here. Thanks!
EDIT: Figured it out.
New question, are you able to put TWRP on your phone with current methods out there? if so, how?
Click to expand...
Click to collapse
Do you mind sharing how you figured it out? I've tried doing this with my Sprint unlocked device but I have had no success so far. Device isn't recognized despite downloading LG Mobile Drivers.
sammibulin said:
Do you mind sharing how you figured it out? I've tried doing this with my Sprint unlocked device but I have had no success so far. Device isn't recognized despite downloading LG Mobile Drivers.
Click to expand...
Click to collapse
Yes. I'm not very good in English and I do not know how to create a guide here in XDA. But give me a chance and I'll try
[Guide]
I am not responsible if something goes wrong.
everything works perfect with total comptability, but I can't confirm if fastboot can be accessed after crossflash. Also, there is no option of wifi calling or calling plus, I cannot confirm OTA, because I installed android pie and it is the latest version for US unlocked. ***Maybe if you install the latest android 8 oreo before ,then you can test if ota works***
Downloads:
files: https://drive.google.com/open?id=1b-ZK3pN2ph7JvG6n4sDyXHxGLT53IfvE
firmware: https://lg-firmwares.com/lg-lmv405qa-firmwares/#tab=firmwares
*rename the firmware file to pie.kdz and put in desktop*
install lg usb drivers (be sure your device can adb. enable usb debugging, open command and put adb devices. check notification on the device and hit always. also Switch between all USB connection modes from the mobile so that Windows installs all the drivers
install lg up
Put LGUP_command.dll it into the folder: C:\Program Files (x86)\LG Electronics\LGUP\model\common ( if there is no common folder, create one and put the file there )
now...
put device in download mode
power off device
connect usb cable to pc, but not the phone
Hold and keep phone volume up
Plug your USB Cable to your phone while holding volume up, already in download mode, release volume up button
now go to device manager an check in ports/lge the value number for example com3, save it
Then go back to C:\Program Files (x86)\LG Electronics\LGUP
Hold the shift key and right click on a free space.
Choose to open a command prompt or PowerShell in Windows 10
After oppening it, type cmd and hit enter.
now you need to put this
lgup_cmd.exe com3 “C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll” “C:\Users\your desktop username\Desktop\pie.kdz
and hit enter, but need to change the com number value. for example mine was com3. if yours is com2, com5 or another just change the number.
and that is. if you do it right then it will start flashing and you will see the progress on the mobile and the powershell
I have an Lg V40 sprint unlocked, would I lose the unlock if I try this?
oscarillo said:
I have an Lg V40 sprint unlocked, would I lose the unlock if I try this?
Click to expand...
Click to collapse
Certainly not, but I can't confirm it
EddiePR said:
Certainly not, but I can't confirm it
Click to expand...
Click to collapse
It did work!
Still unlocked
Thanks
oscarillo said:
It did work!
Still unlocked
Thanks
Click to expand...
Click to collapse
Very nice
jimmyStoo said:
Will OTA still work?
Click to expand...
Click to collapse
I did cross flash to verizon frirmware and the OTA works. So, i hope US unlocked too
i have a us cellular variant, can I convert to the us unlock with this trick?
gtuxyco said:
i have a us cellular variant, can I convert to the us unlock with this trick?
Click to expand...
Click to collapse
I don't know, but I'm almost sure you can
EddiePR said:
I did the crossflash of my lg v40 to the US unlocked pie V405UA20a very very simply without unlocking bootloader, root or some other step. Everything works great, my imei was not deleted, nor my serial number. just flash the kdz by installing lgup and ... can i help you to do the crossflash
Everything works perfect but there is no option for Wi-Fi calls? someone knows?
Click to expand...
Click to collapse
This crossflah works for the att variant too?
Would this factory reset data ?
brigantti said:
This crossflah works for the att variant too?
Click to expand...
Click to collapse
Not sure
(francais) hello i bought a lg v40 thinq lg405ebw. can i flash every v40 rom on or i can only flash lg405ebw rom? and for unlock bootloader in the howto i see lgv35 file for lgv40..... i don't want make error because error = brick often.
thanks for your answer.
bsteph27 said:
(francais) hello i bought a lg v40 thinq lg405ebw. can i flash every v40 rom on or i can only flash lg405ebw rom? and for unlock bootloader in the howto i see lgv35 file for lgv40..... i don't want make error because error = brick often.
thanks for your answer.
Click to expand...
Click to collapse
Is your's a dual sim model? I've heard that can be an issue as I think there are very few roms that support dual sim. Otherwise, yes, should be able to flash whatever you want, except of course t-mobile rom.
the lgv35 file works on the vv40 because they have the same chip; sdm845. You'll also see a v35_engineering_abl bootloader mentioned, it too works on the v40, but it won't actually boot the device unless you're running Pie.
One thing about the v40, with the firehose available, it's pretty hard to brick.
cheers
AsItLies said:
Is your's a dual sim model? I've heard that can be an issue as I think there are very few roms that support dual sim. Otherwise, yes, should be able to flash whatever you want, except of course t-mobile rom.
the lgv35 file works on the vv40 because they have the same chip; sdm845. You'll also see a v35_engineering_abl bootloader mentioned, it too works on the v40, but it won't actually boot the device unless you're running Pie.
One thing about the v40, with the firehose available, it's pretty hard to brick.
cheers
Click to expand...
Click to collapse
thank you very much for your answer . i search double sim rom.
Hey guys,
I have a unlocked Sprint LG V40 off of eBay. Im on Tmobile and sometimes i loose reception and it gets stuck on 2G or 3G.
1. Should I crossflash it to Verizon or US if I'm on Tmobile? Which one will unlock all bands on Tmobile?
2. To flash Verizon or US I simply flash it through LGUP right? Do I need to backup or flash any modem, bootloader or anything else image? If so how do i backup those. Do i simply do a DUMP from LGUP?
3. Do i select Upgrade or Refurbish on LGUP options when flashing verizon or US ROM?
Im new to flashing LG so can u point me to the right guide. Thanks
megadrive007 said:
Hey guys,
I have a unlocked Sprint LG V40 off of eBay. Im on Tmobile and sometimes i loose reception and it gets stuck on 2G or 3G.
1. Should I crossflash it to Verizon or US if I'm on Tmobile? Which one will unlock all bands on Tmobile?
2. To flash Verizon or US I simply flash it through LGUP right? Do I need to backup or flash any modem, bootloader or anything else image? If so how do i backup those. Do i simply do a DUMP from LGUP?
3. Do i select Upgrade or Refurbish on LGUP options when flashing verizon or US ROM?
Im new to flashing LG so can u point me to the right guide. Thanks
Click to expand...
Click to collapse
You'd get more bands (like band 71) with US Open. Only issue there is that it's android 9, not 10. Some believe 9 was better though.
2) there's a guide for using lgup. There's also a guide for unlocking bootloader that describes how to use edl and qualcomms qfil, which will allow you to backup partitions. The key ones to backup would be ftm, fsg, modem, modemst1 and modemst2.
3) When using lgup to crossflash, do a partition D/L first, and select all partitions. Then, when it finishes, go back and do a refurb with the same kdz.
cheers