Develop Bugs

LG G4 H815 Device ID

Anyone know the difference between the LG device ID and the Android ID? Any idea which partition it might be stored in? Would other variants such as H810 H811 H812 etc have a device ID as well?
Thanks alot

dharakv said:
Anyone know the difference between the LG device ID and the Android ID? Any idea which partition it might be stored in? Would other variants such as H810 H811 H812 etc have a device ID as well?
Thanks alot
Click to expand...
Click to collapse
Code:
fastboot oem device-id
Btw you do realise you are effectively trying to reverse engineer hashing - and there is a reason why hashing is a trusted method of verification

dharakv said:
Anyone know the difference between the LG device ID and the Android ID? Any idea which partition it might be stored in? Would other variants such as H810 H811 H812 etc have a device ID as well?
Thanks alot
Click to expand...
Click to collapse
The Android device ID is generated on the first Boot and can be easily changed as its stored in the data Partition once generated. This ID is used for example when you buy something in the Google Play Store. .
the fastboot device ID is coming from the internal flash memory of your device and is absolutely unique for every device and there is no (easy) way to modify it. If that is even possible because maybe it's just generated by the CPU.
You can't even see where it is stored as long as you do not use a box which is able to direct Flash (usually this requires soldiering or special cables as well).
It's like the PBL which is the primary Bootloader and you are not able to see / modify that as well. If you could do so you'd be able to flash your own certificates and signed Bootloader stack and can just switch off Secure Boot or enable Unlock in fastboot.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
The Android device ID is generated on the first Boot and can be easily changed as its stored in the data Partition once generated. This ID is used for example when you buy something in the Google Play Store. .
the fastboot device ID is coming from the internal flash memory of your device and is absolutely unique for every device and there is no (easy) way to modify it. If that is even possible because maybe it's just generated by the CPU.
You can't even see where it is stored as long as you do not use a box which is able to direct Flash (usually this requires soldiering or special cables as well).
It's like the PBL which is the primary Bootloader and you are not able to see / modify that as well. If you could do so you'd be able to flash your own certificates and signed Bootloader stack and can just switch off Secure Boot or enable Unlock in fastboot.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Came across a program called QPST. Hopefully it will be of use

ThePiGuy said:
Code:
fastboot oem device-id
Click to expand...
Click to collapse
The command doesn't work on my H812. Any idea how to get the H815 commands onto H812?

dharakv said:
The command doesn't work on my H812. Any idea how to get the H815 commands onto H812?
Click to expand...
Click to collapse
You haven't exactly been descriptive about the error.
Anyway, there is little to no chance this will work - @steadfasterX spent a year working on UsU and I believe he said he already gave this a go

ThePiGuy said:
You haven't exactly been descriptive about the error.
Anyway, there is little to no chance this will work - @steadfasterX spent a year working on UsU and I believe he said he already gave this a go
Click to expand...
Click to collapse
If I remember correctly the output is blank. I will double check and let you know. Either the command doesn't work or my device doesn't have a device ID (maybe only EU H815's have them)

dharakv said:
Came across a program called QPST. Hopefully it will be of use
Click to expand...
Click to collapse
No. And before you start using it ensure you understand that this can easily brick your device, convert your device and blow fuses. I can just highly recommend to stop here.
dharakv said:
The command doesn't work on my H812. Any idea how to get the H815 commands onto H812?
Click to expand...
Click to collapse
Every device has it. But the fastboot is different on every model and even firmware.
The fastboot on a h812 does not need to show it because it can't be unlocked that way. That's all.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
No. And before you start using it ensure you understand that this can easily brick your device, convert your device and blow fuses. I can just highly recommend to stop here.
Every device has it. But the fastboot is different on every model and even firmware.
The fastboot on a h812 does not need to show it because it can't be unlocked that way. That's all.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Does a blown fuse instantly mean hard brick? Also, if the h812 fastboot commands aren't complete, how can I view my device ID? is there any other way?
Thanks for all your support and advice.

dharakv said:
Does a blown fuse instantly mean hard brick? Also, if the h812 fastboot commands aren't complete, how can I view my device ID? is there any other way?
Thanks for all your support and advice.
Click to expand...
Click to collapse
Blowing fuses means not hard brick. It means several things behave different without any way to revert as it's a physical one-way process.
One well known fuse is ARB. Read about that in the antirollback post linked in my signature.
Another is happening when using qfil which afterwards only allow special firehose programmers ( and we have only 2 which not are able to handle the latest ones ) and there are also many fuses unknown as there is no official or leaked documentation about it.
Sent from my LG-H815 using XDA Labs
PS: the thanks button is there for a reason..

If only I can somehow get an H811 KDZ onto it...
Maybe if I flash H810 KDZ and then the H811 KDZ?

[LG V35 KDZ] [AT&T/Fi/Amazon] July Update Fi Variant

Not a lot happening with the V35 in the dev community, apparently, but the update came out today for my brand new Project Fi LG V35.
I've seen requests for the KDZ file in various threads, so here it is if anyone can use it.
KDZ File on AndroidFileHost (MD5: c3daf5a98064086d86a3d78b35b6ab9c)

So this file would be all that's needed other than a patched version of LGUp to change my At&t variant to the factory unlocked variant?

I just got notification for this update on AT&T

dafloof said:
So this file would be all that's needed other than a patched version of LGUp to change my At&t variant to the factory unlocked variant?
Click to expand...
Click to collapse
I'm currently interested in doing this as well with my ATT variant since I'm missing a few features as a T-mobile user, but I don't want to brick it if I mess up the flashing process.

Did anyone successfully flash the FI KDZ to an AT&T version or no?

Bl00dRunzC0ld said:
Did anyone successfully flash the FI KDZ to an AT&T version or no?
Click to expand...
Click to collapse
I dont think anyone has tried and someone would need to make a patched version of LGup for the V35.

I love the V35, but I really don't think I can live without root. If there's anyone who may be thinking of starting any development on this, I'm more than happy to test things out on my Project Fi V35!

leknessmonster said:
I love the V35, but I really don't think I can live without root. If there's anyone who may be thinking of starting any development on this, I'm more than happy to test things out on my Project Fi V35!
Click to expand...
Click to collapse
I'm on the carrier unlocked V35 and can't even boot into the bootloader so it's looking grim.
---------- Post added at 10:50 PM ---------- Previous post was at 10:25 PM ----------
Synssins said:
Not a lot happening with the V35 in the dev community, apparently, but the update came out today for my brand new Project Fi LG V35.
I've seen requests for the KDZ file in various threads, so here it is if anyone can use it.
KDZ File on AndroidFileHost (MD5: c3daf5a98064086d86a3d78b35b6ab9c)
Click to expand...
Click to collapse
I wish we were given a dedicated forum. I feel like it would help. Requests just say use a tag. They made one for the V30S which is not only completely dead, but it's basically the V30. Our V35 is very different.

Totally agree with this post... Feels like v35 owners got the middle finger on this one
Cobra04 said:
I'm on the carrier unlocked V35 and can't even boot into the bootloader so it's looking grim.
---------- Post added at 10:50 PM ---------- Previous post was at 10:25 PM ----------
I wish we were given a dedicated forum. I feel like it would help. Requests just say use a tag. They made one for the V30S which is not only completely dead, but it's basically the V30. Our V35 is very different.
Click to expand...
Click to collapse

Cobra04 said:
I'm on the carrier unlocked V35 and can't even boot into the bootloader so it's looking grim.
---------- Post added at 10:50 PM ---------- Previous post was at 10:25 PM ----------
I wish we were given a dedicated forum. I feel like it would help. Requests just say use a tag. They made one for the V30S which is not only completely dead, but it's basically the V30. Our V35 is very different.
Click to expand...
Click to collapse
Agreed. I wish we had our own forum. I did find some info on developer options directly from LG. Sadly the V35 is not on the list of devices they will allow you to unlock.
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryId=CTULRS0703

jwrezz said:
Agreed. I wish we had our own forum. I did find some info on developer options directly from LG. Sadly the V35 is not on the list of devices they will allow you to unlock.
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryId=CTULRS0703
Click to expand...
Click to collapse
Every Twitter rep says it won't be. If you look, the US V30 isn't actually there either. Only the European ones.
I really like the phone but I'm considering returning it because of LG's unwillingness to allow us to unlock the bootloader. It would be perfect if it were possible.

Cobra04 said:
Every Twitter rep says it won't be. If you look, the US V30 isn't actually there either. Only the European ones.
I really like the phone but I'm considering returning it because of LG's unwillingness to allow us to unlock the bootloader. It would be perfect if it were possible.
Click to expand...
Click to collapse
How long do I have to return to Fi, I wonder. I may have to pick up a P2XL or just wait for the 3. I like the Nexus line for developer options alone. I hope some one finds an exploit otherwise. Sucky. Why have the developer options and OEM unlock availability in the settings? LG, you anger me.

jwrezz said:
How long do I have to return to Fi, I wonder. I may have to pick up a P2XL or just wait for the 3. I like the Nexus line for developer options alone. I hope some one finds an exploit otherwise. Sucky. Why have the developer options and OEM unlock availability in the settings? LG, you anger me.
Click to expand...
Click to collapse
According to Fi's return policy, you have 15 days from date of receipt. I ended up returning mine since it seems like development here is bleak. I did see that @runningnak3d is turning his attention to the US T-Mobile LG G7 variant. Maybe he might turn his attention here too after? :crying:

Please correct me if the info I just looked up is wrong....
It looks like there are only two models of the V35 -- the Korean model, and one for AT&T?
EDIT: OK, so there is the carrier unlocked Fi version, the Korean version, and the AT&T version. The rest of this post still applies, but change any 2s to 3s
If that is the case, and neither has an unlockable bootloader, then I seriously doubt it will ever happen.
Most of the TZ is on the CPU starting with the SD845, but more importantly, the abl (what used to be aboot, also called the apps bootloader) is encrypted. It is no longer possible to decompile it to try and find any exploits.
Well, let's just say *I* don't have what it takes. Since it is decrypted when the phone boots, it would be possible to dump RAM while the phone boots .. but that is some expensive equipment.
On the V30, an exploit was found by someone just randomly flashing an unlock.bin from another model. It turns out that before they patched that exploit, that ANY unlock.bin would unlock the bootloader. However, this was on a model that LG allowed to be unlocked, and the RSA key was the same on all other models (except the H932), so they could just cross flash.
Let's just assume that was possible on the V35, next is getting TWRP onto the phone. I was able to find an exploit in laf for the H932 due to the fact that there are many models, and the carriers like to build their own firmware. So, you end up with not just holes that LG left in, but holes that the carriers themselves add because they don't know what the eff they are doing.
So, back to the V35....
With only 2 models, and neither of them having official bootloader unlock, and only two different versions of laf to work with, I don't see it happening.
-- Brian

runningnak3d said:
Please correct me if the info I just looked up is wrong....
It looks like there are only two models of the V35 -- the Korean model, and one for AT&T?
If that is the case, and neither has an unlockable bootloader, then I seriously doubt it will ever happen.
Most of the TZ is on the CPU starting with the SD845, but more importantly, the abl (what used to be aboot, also called the apps bootloader) is encrypted. It is no longer possible to decompile it to try and find any exploits.
Well, let's just say *I* don't have what it takes. Since it is decrypted when the phone boots, it would be possible to dump RAM while the phone boots .. but that is some expensive equipment.
On the V30, an exploit was found by someone just randomly flashing an unlock.bin from another model. It turns out that before they patched that exploit, that ANY unlock.bin would unlock the bootloader. However, this was on a model that LG allowed to be unlocked, and the RSA key was the same on all other models (except the H932), so they could just cross flash.
Let's just assume that was possible on the V35, next is getting TWRP onto the phone. I was able to find an exploit in laf for the H932 due to the fact that there are many models, and the carriers like to build their own firmware. So, you end up with not just holes that LG left in, but holes that the carriers themselves add because they don't know what the eff they are doing.
So, back to the V35....
With only 2 models, and neither of them having official bootloader unlock, and only two different versions of laf to work with, I don't see it happening.
-- Brian
Click to expand...
Click to collapse
There is also a fully unlocked V35 and the "unlocked" Project Fi model. Not aware of anymore models.

Cobra04 said:
There is also a fully unlocked V35 and the "unlocked" Project Fi model. Not aware of anymore models.
Click to expand...
Click to collapse
So fully unlocked as in bootloader unlock supported by LG? If so, then that is getting somewhere....
-- Brian

runningnak3d said:
So fully unlocked as in bootloader unlock supported by LG? If so, then that is getting somewhere....
-- Brian
Click to expand...
Click to collapse
I should clarify, unlocked as in carrier unlocked. That is the model I have. I'm not familiar with LG devices, but there isn't even a way to boot into the bootloader.

Yea, I hate to say that it is impossible (I did that for the H918, the H872 and then the H932 and ended up proving MYSELF wrong) but this isn't looking good.
With the V20, G6 and V30:
A - Had models that had officially unlockable bootloader support from LG
B - Could decompile aboot (on the V20 and G6 at least)
C - had LOTS of different versions of laf to work with.
I will download the KDZ and take a look though...
-- Brian

runningnak3d said:
Yea, I hate to say that it is impossible (I did that for the H918, the H872 and then the H932 and ended up proving MYSELF wrong) but this isn't looking good.
With the V20, G6 and V30:
A - Had models that had officially unlockable bootloader support from LG
B - Could decompile aboot (on the V20 and G6 at least)
C - had LOTS of different versions of laf to work with.
I will download the KDZ and take a look though...
-- Brian
Click to expand...
Click to collapse
Anyway I can help?

I need partition lists of each lun. Can you burn FWUL to a USB stick, and run lglaf?
If so, I will tell you what commands I need run.
-- Brian

Bootloader bounty? Too soon?

Is it too soon to start a bounty for a bootloader unlock? Do we even have any devs using this device(Lm-G710TM)? Im good for $100+.

It's not soon for USA unlocked (G710ULM) because 11th July was the release, till now why there's no bootloader for this unlocked variant! Already European variant enjoying root.

I usually give it like two months before I expect activity to pick up for new phones; even when owning Nexus phones. But, it's very discouraging to see how dead this place is, especially for any US variants. If there's no encouraging development for this phone by the time the Pixel 3 drops, I might just ditch this phone for that instead. This is a solid phone, but it could be absolutely great with a custom ROM/kernel.

totally agree, this is a great and solid phone. Could use a few tweaks and it'll be even better!
Alcolawl said:
I usually give it like two months before I expect activity to pick up for new phones; even when owning Nexus phones. But, it's very discouraging to see how dead this place is, especially for any US variants. If there's no encouraging development for this phone by the time the Pixel 3 drops, I might just ditch this phone for that instead. This is a solid phone, but it could be absolutely great with a custom ROM/kernel.
Click to expand...
Click to collapse

Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian

runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
I know VZW it's all locked The OEM switch is missing also. I'm assuming for at least Verizon there needs to be an exploit if ever found.

For now, I am just talking about the TMO version.
-- Brian

runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-g7-thinq/help/t-mobile-oem-unlock-t3833156

runningnak3d said:
For now, I am just talking about the TMO version.
-- Brian
Click to expand...
Click to collapse
Welcome aboard mate, been looking for your presence here but was doubting it as you don't have this device as of yet. I'm happy to see you and say that I was wrong, can't thank you enough for the work you have done on other devices.
Will be more than willing to help anyway I can, although I am currently on the sprint variant for the moment.

Hey @ps3hacker3 Long time no speak
Yea, I have learned enough that it is getting a lot easier even if I don't have the phone. However, I am going to need some info from people that DO have the G710TM.
-- Brian

runningnak3d said:
Hey @ps3hacker3 Long time no speak
Yea, I have learned enough that it is getting a lot easier even if I don't have the phone. However, I am going to need some info from people that DO have the G710TM.
-- Brian
Click to expand...
Click to collapse
LG G710ULM owner here. I know it's not specifically a T-Mobile version but it does allow OEM unlocking by default. I could be wrong, but I'm guessing the differences between the G710TM and G710ULM aren't that big (if any at all). If you need any info from my end, let me know. I'd love to get the ball rolling on bootloader unlocks for this phone. Lots of untapped potential here.

So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian

runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
Upon rebooting into Bootloader I'm presented with a quick guide for unlocking the phone:
1) Read Device ID
:fastboot oem device-id
2) Write Unlock Key
:fastboot flash unlock unlock.bin
3)Check bootloader is unlocked
:fastboot getvar unlocked
fastboot oem unlock results in a FAILED (remote: 'unknown command') message. Screenshot attached. My first attempt didn't work because I guess I didn't have the right bootloader drivers installed.
So it looks like even the unlocked models are in the same boat as everyone else, except Europe.

runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
The T-Mobile version has the oem unlock slider.
Edit: if I run the fastboot oem unlock command, nothing happens. The phone when using reboot bootloader, gives me 3 options. Get ID, check unlock, I forget the wording on the other, but it's basically to input your unlock file I think.

20degrees said:
The T-Mobile version has the oem unlock slider.
Edit: if I run the fastboot oem unlock command, nothing happens. The phone when using reboot bootloader, gives me 3 options. Get ID, check unlock, I forget the wording on the other, but it's basically to input your unlock file I think.
Click to expand...
Click to collapse
On my Windows 10 machine, when this phone is in Bootloader and plugged in via USB, Device Manager showed it as just "Android" with a warning symbol next to it. Had to grab the latest Google ADB and Fastboot drivers and force install the drivers (Choose from list, Have Disk..., Android Bootloader Interface, etc.) in order for the computer to actually recognize the phone properly when in the Bootloader. Otherwise issuing Fastboot commands just resulted in <waiting for any device> or whatever. Strange, because I haven't touched this OS install in probably a year and I had no problems issuing commands to my Pixel XL in Bootloader this spring.
Anyways, looks like until LG decides they want to support unlocking other variants, we're dead in the water.

Alcolawl said:
On my Windows 10 machine, when this phone is in Bootloader and plugged in via USB, Device Manager showed it as just "Android" with a warning symbol next to it. Had to grab the latest Google ADB and Fastboot drivers and force install the drivers (Choose from list, Have Disk..., Android Bootloader Interface, etc.) in order for the computer to actually recognize the phone properly when in the Bootloader. Otherwise issuing Fastboot commands just resulted in <waiting for any device> or whatever. Strange, because I haven't touched this OS install in probably a year and I had no problems issuing commands to my Pixel XL in Bootloader this spring.
Anyways, looks like until LG decides they want to support unlocking other variants, we're dead in the water.
Click to expand...
Click to collapse
Be forewarned, I've noticed that fastboot doesn't always work, despite latest drivers. As of late, the Pixel has been known to hang on these same commands at times as well. My Moto Z2 Force suffers from this error as well.
---------- Post added at 04:11 AM ---------- Previous post was at 04:04 AM ----------
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
I hope you know many are INCREDIBLY excited to have you on board! I'm not advanced, but once I receive my computer back, I'll definitely be available to help with providing info and helping test, as I have a TMO variant (I may or may not work for TMO as well, so yeah... )

runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
Own a TMobile variant, oem unlocking option is there, fastboot commands do not work (or are extremely limited)
getprop | grep unlock (if it means anything)
[Ro.oem_unlock_supported]: [1]
[Sys.oem_unlock_allowed]: [1]
I know I probably didn't help out much, if you have any other questions feel free to ask I'll help out as much as I can. thank you for contributions and congrats on the V30 root.

runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
I have the tmobile variant. Let me know what you might need.
Unlock Slider is present in developer settings and is not greyed out. Unlock command just hangs.

runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
Sprint variant also has "Allow OEM unlocking" available and it is changeable

So you can issue fastboot flashing unlock_critical but not fastboot flashing unlock -- that is just weird.
If you issue the unlock_critical, do you get the warning that your phone is possibly corrupt, but will continue to boot?
-- Brian

LG G8 firmware flash

I just purchased a Verizon LG G8 that is unlocked and want to use it on Metro. I haven't gotten the phone yet but I would like to (if it's possible) flash a unbranded firmware. I'm confused about whether I can use LGUP or LG flash tool to do this. Can someone please tell me if this can be done and if so what is the best firmware to flash to have it unbranded with minimal bloat?

I miss the good old days on XDA where people actually came on XDA and there was always someone able to help out. I feel like that doesn't exist anymore. Too many phones and too many different carriers.

I don't think there's a patched LGUP to do this for LG G8 yet.

lentm said:
I don't think there's a patched LGUP to do this for LG G8 yet.
Click to expand...
Click to collapse
Holy shiit, someone actually answered my question! That is insane! Thanks for the info man!

Is there a y method that currently works to flash firmware on the LG g8? I would like to flash the stock unlocked carrier unbranded firmware.

There is no way to flash through LGUP or any other tools currently but you can unlock boot-loader root and install firmware package through twrp but doesn't work for T-Mobile or Metro

awireless said:
There is no way to flash through LGUP or any other tools currently but you can unlock boot-loader root and install firmware package through twrp but doesn't work for T-Mobile or Metro
Click to expand...
Click to collapse
How are you unlocking bootloader and rooting?

Shtiff1 said:
How are you unlocking bootloader and rooting?
Click to expand...
Click to collapse
There is a thread for it and same thing at the g7 thread. Just use octoplus jtag pro to flash the v35 engineering boot-loader to device and from there you can unlock boot-loader and do all the stuff. If you dont have octoplus jtag pro there is a guy who will do it for you he charges i dont know how much though.

how to convert oneplus 7t tmobile to international without unloking bootloader ?

hi, i want to convert my 7t from tmobile to international but without uncloking the bootloader.
i have found some threads about it here, but they are a bit confusing since they are showing how to do everything, like rooting, unlcloking and all these stuffs together and i just want to do the conversion to international without uncloking the bootloader, so if someone could help me with that i will appreciate it.
because i do not want to brick my phone i just want to do it right
the current model i have now is this (oneplus 7t HD1907 build number 10.0.12HD63CB)
so thanks.

I don't think it's possible without unlocking bootloader.

manny18pr said:
I don't think it's possible without unlocking bootloader.
Click to expand...
Click to collapse
i see, well thanks

I mean...
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com

the_link_8 said:
hi, i want to convert my 7t from tmobile to international but without uncloking the bootloader.
i have found some threads about it here, but they are a bit confusing since they are showing how to do everything, like rooting, unlcloking and all these stuffs together and i just want to do the conversion to international without uncloking the bootloader, so if someone could help me with that i will appreciate it.
because i do not want to brick my phone i just want to do it right
the current model i have now is this (oneplus 7t HD1907 build number 10.0.12HD63CB)
so thanks.
Click to expand...
Click to collapse
I have done it (converted to international, locked bootloader) using this nice guide
[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile...
forum.xda-developers.com
N:B: Copy and replace all the files of the extracted fastboot rom (keep the files from the platform tools).
After flashing 10.0.12, do an immediate OTA to 10.0.15. After that execute "fastboot oem lock".

zaman9632 said:
I have done it (converted to international, locked bootloader) using this nice guide
[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile...
forum.xda-developers.com
N:B: Copy and replace all the files of the extracted fastboot rom (keep the files from the platform tools).
After flashing 10.0.12, do an immediate OTA to 10.0.15. After that execute "fastboot oem lock".
Click to expand...
Click to collapse
Hi mate,
Did you get the unlock token from OnePlus by waiting 7 days or using This Link?
Thanks

ericZX26 said:
Hi mate,
Did you get the unlock token from OnePlus by waiting 7 days or using This Link?
Thanks
Click to expand...
Click to collapse
I waited for 7 days. I didn't want to take additional risk. Thanks.

zaman9632 said:
I waited for 7 days. I didn't want to take additional risk. Thanks.
Click to expand...
Click to collapse
Waiting for my unlock token.
By the way, did you clean the data( by factory reset or in Recovery Mode ) before or after flashing the 10.0.12?
Thanks

ericZX26 said:
Waiting for my unlock token.
By the way, did you clean the data( by factory reset or in Recovery Mode ) before or after flashing the 10.0.12?
Thanks
Click to expand...
Click to collapse
When you will unlock the bootloader, it will automatically clean everything.