Question for those of you with experience on the V10. I just upgraded to the V20 (love it btw). My V10 is probably the first phone I never rooted, or loaded a ROM on. I've had many devices with custom roms in the past, however they were always carried branded (not unlocked) phones. Here is my question:
I'm giving my V10 to a friend in Europe in a few weeks. Already confirmed that it supports all the necessary bands and channels, plus I've used it over there in the past without issue. Being that it's a VS990, is there an official "LG" factory ROM that I can load so that all the verizon branded crap is gone, apps etc, and so that it works like what most Europeans would expect? Just a plain "unlocked" V10 that gets OTA updates? Or is it not possible, or worth the effort?
Thanks in advance..
X
Can't flash roms to VS990. Locked bootloader does not allow TWRP to be installed, which you need to flash roms.
xarius76 said:
I'm giving my V10 to a friend in Europe in a few weeks. Already confirmed that it supports all the necessary bands and channels, plus I've used it over there in the past without issue. Being that it's a VS990, is there an official "LG" factory ROM that I can load so that all the verizon branded crap is gone, apps etc, and so that it works like what most Europeans would expect? Just a plain "unlocked" V10 that gets OTA updates? Or is it not possible, or worth the effort?
Click to expand...
Click to collapse
There is no such thing endorsed by LG. How important is it to remove the Verizon crud and how much risk are you willing to deal with? Are you adverse to voiding your warranty? Are you willing to pay a repair fee for "accidentally" flashing the wrong KDZ file?
According to multiple reports the KDZ files from the various V10s are pretty compatible with each other. Given this you could download a H901 (T-Mobile) KDZ file and install that and it should be free of bloat, there is even speculation this could be used to unlock the bootloader.
Aside from bricking your device, my biggest worry is the cell modem may have slightly different hardware and the firmware for the H901 might not drive it correctly, though that may merely mean it cannot connect to CDMA networks. Much of the cell modem configuration is left untouched by KDZ files, but there is always a first time for an unpleasant surprise.
So, how comfortable are you with risk? I'm cautiously optimistic this method will work, but this is risky! If you do try this, could you please report back whether it succeeded or not? (more reports good)
beavis5706 said:
Can't flash roms to VS990. Locked bootloader does not allow TWRP to be installed, which you need to flash roms.
Click to expand...
Click to collapse
I was unaware the boot loader on this had not been unlocked yet. Seeing as it's been out a year, I just assumed it had been by this point. My bad!
emdroidle said:
There is no such thing endorsed by LG. How important is it to remove the Verizon crud and how much risk are you willing to deal with? Are you adverse to voiding your warranty? Are you willing to pay a repair fee for "accidentally" flashing the wrong KDZ file?
According to multiple reports the KDZ files from the various V10s are pretty compatible with each other. Given this you could download a H901 (T-Mobile) KDZ file and install that and it should be free of bloat, there is even speculation this could be used to unlock the bootloader.
Aside from bricking your device, my biggest worry is the cell modem may have slightly different hardware and the firmware for the H901 might not drive it correctly, though that may merely mean it cannot connect to CDMA networks. Much of the cell modem configuration is left untouched by KDZ files, but there is always a first time for an unpleasant surprise.
So, how comfortable are you with risk? I'm cautiously optimistic this method will work, but this is risky! If you do try this, could you please report back whether it succeeded or not? (more reports good)
Click to expand...
Click to collapse
It's really not so important, but there's always some risk with you change bootloaders or flash anything to the device. I just know that with this being a Verizon device running in EU, any OTA updates from Verizon (I assume) would never get installed. I was really just looking for a way to keep OTA updates flowing, and as a plus, remove the Verizon bloatware.
I appreciate your candid and informational response! I might just give this a try while I'm over there. =)
X
xarius76 said:
I was unaware the boot loader on this had not been unlocked yet. Seeing as it's been out a year, I just assumed it had been by this point. My bad!
Click to expand...
Click to collapse
This is a substantial annoyance to many people, though there are some hopes of working around this...
xarius76 said:
It's really not so important, but there's always some risk with you change bootloaders or flash anything to the device. I just know that with this being a Verizon device running in EU, any OTA updates from Verizon (I assume) would never get installed. I was really just looking for a way to keep OTA updates flowing, and as a plus, remove the Verizon bloatware.
Click to expand...
Click to collapse
I won't swear to it, but I was under the impression the updates come from LG, at which point it should still nominally update if brought to the EU. Failing that, LG Bridge should be able to get updates.
xarius76 said:
I appreciate your candid and informational response! I might just give this a try while I'm over there. =)
Click to expand...
Click to collapse
Remember, this is risky though hopeful.
Related
OK, i have searched around and have not found anything to my question. Is it possible to flash the ATT version ROM to the T-mobile version?
seattleboi1982 said:
OK, i have searched around and have not found anything to my question. Is it possible to flash the ATT version ROM to the T-mobile version?
Click to expand...
Click to collapse
Yeah, just don't flash any odin files.
aooga said:
Yeah, just don't flash any odin files.
Click to expand...
Click to collapse
can you clarify please?
seattleboi1982 said:
can you clarify please?
Click to expand...
Click to collapse
Not sure what you mean. You can flash any rom from any variant of the S5 (obviously not the exynos variant, but there's hardly anything for it anyway). When I say rom, I mean a zip that's flashable in cwm or twrp. NOT the files that you flash in ODIN (tar, md5). DON'T flash those files from any other phone except the G900T.
seattleboi1982 said:
OK, i have searched around and have not found anything to my question. Is it possible to flash the ATT version ROM to the T-mobile version?
Click to expand...
Click to collapse
Well yes, but the way it works may not be quite the way you picture it. If you flash your phone to TMobile it isn't a 100% change over to TMobile as you probably assume it would be. Picture your phone as having two parts.. a baseband + ROM. The baseband is basically just the bootloader and modem. It's very hard to change the baseband and it's hardly ever done. So your baseband will more than likely remain ATT forever no matter what you do.
But that isn't likely to be a problem either. The baseband is compatible between ATT and TMobile and pretty much any other GSM system too. Otherwise you wouldn't be able to roam on other systems. You can change the ROM part to TMobile and your phone will act, smell and behave like a TMobile phone in pretty much every way that is likely to matter to you. The only obvious snag is that automatic OTA updates may or may not work, if that matters to you.
The customary way to change your phone to TMobile would be to root it, install a custom recovery e.g. TWRP. Then flash a TMobile ROM (or custom ROM if you want to) from TWRP. Note that installing a custom recovery like TWRP will change your Knox warranty bit. That might have warranty implications if your phone is still under warranty. Some carriers don't care about Knox - you can check the ATT forum to see how ATT handles warranty claims.
Alternately, if Knox matters to you, you may be able to flash a full stock TMobile image to your phone with the Odin program. This works for some carriers and not others. I don't know how ATT's locked bootloader would react to that. It's just a possibility that you could investigate if Knox and warranty are an issue to you. It would probably mean using a newer root method that doesn't trip Knox, then flashing a full TMobile firmware image, along with the correct TMobile PIT file. Hopefully Odin would just ignore the baseband and just write the ROM, while preserving the Knox bit. But you'd have to confirm that the ATT bootloader won't go bananas over the attempt i.e. search the forum to find out what happened when other people tried it.
.
fffft said:
Well yes, but the way it works may not be quite the way you picture it. If you flash your phone to TMobile it isn't a 100% change over to TMobile as you probably assume it would be. Picture your phone as having two parts.. a baseband + ROM. The baseband is basically just the bootloader and modem. It's very hard to change the baseband and it's hardly ever done. So your baseband will more than likely remain ATT forever no matter what you do.
But that isn't likely to be a problem either. The baseband is compatible between ATT and TMobile and pretty much any other GSM system too. Otherwise you wouldn't be able to roam on other systems. You can change the ROM part to TMobile and your phone will act, smell and behave like a TMobile phone in pretty much every way that is likely to matter to you. The only obvious snag is that automatic OTA updates may or may not work, if that matters to you.
The customary way to change your phone to TMobile would be to root it, install a custom recovery e.g. TWRP. Then flash a TMobile ROM (or custom ROM if you want to) from TWRP. Note that installing a custom recovery like TWRP will change your Knox warranty bit. That might have warranty implications if your phone is still under warranty. Some carriers don't care about Knox - you can check the ATT forum to see how ATT handles warranty claims.
Alternately, if Knox matters to you, you may be able to flash a full stock TMobile image to your phone with the Odin program. This works for some carriers and not others. I don't know how ATT's locked bootloader would react to that. It's just a possibility that you could investigate if Knox and warranty are an issue to you. It would probably mean using a newer root method that doesn't trip Knox, then flashing a full TMobile firmware image, along with the correct TMobile PIT file. Hopefully Odin would just ignore the baseband and just write the ROM, while preserving the Knox bit. But you'd have to confirm that the ATT bootloader won't go bananas over the attempt i.e. search the forum to find out what happened when other people tried it.
.
Click to expand...
Click to collapse
actually its T-mobile S5 flash to to make it like ATT S5. Samsung is a differant beast for me as i am usually a HTC or Moto user.
seattleboi1982 said:
actually its T-mobile S5 flash to to make it like ATT S5.
Click to expand...
Click to collapse
Your original post stated the opposite. Unintentionally I'm sure, but it goes to show that clarity counts.
It's much easier to go in that direction because the 900T uses an unlocked bootloader and TMB is generally less restrictive.
So yes, you can install an ATT (or other custom ROM) onto a 900T.
Keep in mind that it is not necessary to do so. The 900T will work fine on ATT with it's original firmware. But you can change the ROM to ATT if you want to for some reason. The proper way to do so is to find an ATT PIT file, then flash a full stock ATT firmware + PIT to your 900T. Most people don't bother with the PIT file and occasionally that leads to bootloops and soft bricking.
Anyway, go ahead and flash it if you want. Odin won't change the baseband, but everything else (ROM) will transition to ATT. FWIW, I think that a custom (debloated) ROM e.g. Phoenix ROM (which is not branded for ATT or TMB) is a nicer experience and better performance than using the ATT ROM. But up to you of course.
There is a XDA thread on S5 PIT files that has the 16 GB version of the ATT PIT if you need it.
.
fffft said:
Your original post stated the opposite. Unintentionally I'm sure, but it goes to show that clarity counts.
It's much easier to go in that direction because the 900T uses an unlocked bootloader and TMB is generally less restrictive.
So yes, you can install an ATT (or other custom ROM) onto a 900T.
Keep in mind that it is not necessary to do so. The 900T will work fine on ATT with it's original firmware. But you can change the ROM to ATT if you want to for some reason. The proper way to do so is to find an ATT PIT file, then flash a full stock ATT firmware + PIT to your 900T. Most people don't bother with the PIT file and occasionally that leads to bootloops and soft bricking.
Anyway, go ahead and flash it if you want. Odin won't change the baseband, but everything else (ROM) will transition to ATT. FWIW, I think that a custom (debloated) ROM e.g. Phoenix ROM (which is not branded for ATT or TMB) is a nicer experience and better performance than using the ATT ROM. But up to you of course.
There is a XDA thread on S5 PIT files that has the 16 GB version of the ATT PIT if you need it.
.
Click to expand...
Click to collapse
Odin will change the baseband. There's no need at all do do anything with ODIN. All it does is cause more problems if he does something wrong. I would just use TWRP and flash a stock ATT rom.
aooga said:
Odin will change the baseband. There's no need at all do do anything with ODIN. All it does is cause more problems if he does something wrong. I would just use TWRP and flash a stock ATT rom.
Click to expand...
Click to collapse
Installing a custom recovery like TWRP will trip Knox. That probably isn't an issue as TMobile doesn't care about Knox and virtually everyone says that it does not affect how TMobile handles warranty claims. But the OP should still know about Knox in advance in case it is an issue for him somehow.
I agree that a flashable zip is easier than Odin if the ROM that he wants exists in that form. Specifically, I don't know if anyone has repackaged an ATT ROM into a zip format. If someone has, then i agree with your approach. If not, he would have to use Odin.
IMO, the OP would do best to install something like the unbranded Phoenix ROM via TWRP.
Odin will not usually a foreign baseband to be flashed. Not that he necessarily has to try. You can use Odin to flash AP, CP, and CSC, but not the BL. Only when the constituent components are unavailable do you need to use the full OEM Odin image.
.
OP: Why do you need an ATT rom anyway? If you tell us what part you actually need, it might be easier than flashing an entire rom, either with odin or twrp.
fffft said:
Installing a custom recovery like TWRP will trip Knox. That probably isn't an issue as TMobile doesn't care about Knox and virtually everyone says that it does not affect how TMobile handles warranty claims. But the OP should still know about Knox in advance in case it is an issue for him somehow.
I agree that a flashable zip is easier than Odin if the ROM that he wants exists in that form. Specifically, I don't know if anyone has repackaged an ATT ROM into a zip format. If someone has, then i agree with your approach. If not, he would have to use Odin.
IMO, the OP would do best to install something like the unbranded Phoenix ROM via TWRP.
Odin will not usually a foreign baseband to be flashed. Not that he necessarily has to try. You can use Odin to flash AP, CP, and CSC, but not the BL. Only when the constituent components are unavailable do you need to use the full OEM Odin image.
.
Click to expand...
Click to collapse
How would someone deal with tmobile warranty without a tmobile account?
Is that possible at all?
Like via prepaid or something? Just wondering..
I would trip knox if I knew I had something to fall back on.
Lostatsea23 said:
How would someone deal with tmobile warranty without a tmobile account?
Is that possible at all?
Like via prepaid or something? Just wondering..
I would trip knox if I knew I had something to fall back on.
Click to expand...
Click to collapse
No, you need to be a tmobile customer with a postpaid account.
aooga said:
No, you need to be a tmobile customer with a postpaid account.
Click to expand...
Click to collapse
Well. Theres my options lol
aooga said:
No, you need to be a tmobile customer with a postpaid account.
Click to expand...
Click to collapse
Do you have a source or even solid rationale for that? I don't disagree that TMB, like pretty much any carrier treats current, postpaid customers better. But I have not seen any written policy or even credible assertions that TMB disavows their warranty for prepaid or ex-customers. AFAIK, if you bought the phone from TMB, postpaid or prepaid, you have a warranty through TMB. The obvious impediments being a stolen phone or account in serious arrears.
Discretionary powers exist, so it's sometimes difficult to distinguish between common practice or what they can be persuaded to do versus actual policy. Policy is a definite advantage in negotiations, so if there is anything written that says prepaid or ex-customers must deal with Samsung directly, I'd like to see that.
Everything in my direct experience is to the contrary. TMB honours warranty and doesn't care about Knox. They do have less respect for prepaid customers. But the few prepaid TMB customers that I know still had TMB handle their warranty claims.
.
fffft said:
Do you have a source or even solid rationale for that? I don't disagree that TMB, like pretty much any carrier treats current, postpaid customers better. But I have not seen any written policy or even credible assertions that TMB disavows their warranty for prepaid or ex-customers. AFAIK, if you bought the phone from TMB, postpaid or prepaid, you have a warranty through TMB. The obvious impediments being a stolen phone or account in serious arrears.
Discretionary powers exist, so it's sometimes difficult to distinguish between common practice or what they can be persuaded to do versus actual policy. Policy is a definite advantage in negotiations, so if there is anything written that says prepaid or ex-customers must deal with Samsung directly, I'd like to see that.
Everything in my direct experience is to the contrary. TMB honours warranty and doesn't care about Knox. They do have less respect for prepaid customers. But the few prepaid TMB customers that I know still had TMB handle their warranty claims.
.
Click to expand...
Click to collapse
Source would be experience. When you call, you cannot speak to a warranty rep unless you have a tmobile account. They ask for the phone number and last 4 of your ssn. Maybe you can convince them to make an exception, but when I tried with ATT, they told me since you're not a ATT customer, we can't help you.
aooga said:
Source would be experience. When you call, you cannot speak to a warranty rep unless you have a tmobile account.
Click to expand...
Click to collapse
All right. Your experience is completely contrary to mine. With no evidence of that being policy, I can only assume that you've encountered less helpful CSRs. Anyone finding themselves in a similar position may well prevail if they try talking to different CSRs.
.
fffft said:
All right. Your experience is completely contrary to mine. With no evidence of that being policy, I can only assume that you've encountered less helpful CSRs. Anyone finding themselves in a similar position may well prevail if they try talking to different CSRs.
.
Click to expand...
Click to collapse
Have you actually done an exchange with a carrier that you don't have service with? Just think about it...they don't have any of your info. CC, ssn, email, even your full name. If for some reason the customer doesn't ship the defective phone back, they can't charge you. If tmobile has a way of doing this for non-customers, I'll gladly shut up
aooga said:
...
Click to expand...
Click to collapse
I already expressed my opinion on this. If you disagree, so be it. And it's tangential and off topic in this thread.
Getting back on topic, the OP asked if he can flash an ATT "ROM" onto his TMB 900T phone.
Yes he can. We agreed that the easiest way to do so is to use TWRP, provided that he does not mind Knox being tripped. And of course, assuming that someone has repackaged an ATT ROM into a flashable zip format.
The alternative is a traditional Odin flash. He can flash ATT firmware onto his TMB 900T phone. It should be done in conjunction with the appropriate ATT PIT file. But those who are impatient or don't know about PIT files, usually don't run into problems eschewing the PIT. I won't advise that approach though.
Two last considerations. There isn't necessarily a good reason to do any of this in the first place. A TMobile S5 can roam on or use an ATT SIM directly. And without missing out on anything that the average user would notice. But it is possible to so for sundry reasons. As one way of changing the CSC and opt into an automatic OTA update scenario. To gain carrier specific ATT apps and so forth.
There is a lot of confusion regarding the mechanics of transitioning a phone from TMB to ATT for these sundry goals. A phone has a ROM, which is the apps and most of the system files. That can certainly be changed.
And then there is the low level baseband. The baseband can be updated with something newer from the same carrier that the phone originated from. But it is difficult and hard to find a good reason to change the baseband to a different carrier. To be more specific the baseband represents the bootloader and modem. A modem from one carrier works just fine on another carrier 99% of the time. So pragmatically, the best approach is to simply update the modem to a newer version from the original carrier, regardless of what carrier you actually use the phone on. There is rarely something carrier specific in a modem module.
If you enjoy fighting with Odin, you can flash some modems from foreign carriers. It will also sometimes brick your phone. And Odin often refuses to proceed with the flash for various reasons. So again, not recommended. Nor necessary in most cases.
The bootloader is exponentially harder to change to another carrier. Not to mention almost pointless except for cosmetic reasons and involves having Odin jump through a lot of hoops. Difficult enough to do that it isn't inaccurate to say it can't be done. It can't be done by most people. And it would be rare to hear a reason with merit for doing so.
.
.
seattleboi1982 said:
OK, i have searched around and have not found anything to my question. Is it possible to flash the ATT version ROM to the T-mobile version?
Click to expand...
Click to collapse
Why would you want to run an att rom, no wifi calling? lol, anyways, what rom are you trying to run?
i would like to run as close as possible to an AT&T ROM as im an ATT subsciber with a T-mobile phone. especially now with VoLTE.
I am currently on a galaxy s4, just started messing around with android a little. I am interested in switching to a slightly newer phone. Assuming I get a g3 that is on the latest OTA update, is it possible to unlock the bootloader or install any type of custom recovery? I am interested in flashing different roms, which I currently can't do on my verizon OF1 S4. If I can't on this phone, what about a g4? I am really only interested in phones with user replaceable batteries that I can swap out, so my options are somewhat limited. Thanks for any help.
James.
I got a G3 that was on 35B -- which I believe is the latest version. You pretty much have to TOT back to 10B (see the thread regarding flashing back to stock), and then you can root, install TWRP, etc from there. Once you've got that, you can pretty much do what you want.
Personally, I had some fussing about with USB device drivers and so on -- I think it took me more time to get the device properly recognized in windows than any other parts of the process!
You'll notice that there are various different ROMS, some based on stock and some that are AOSP, Cyanogen, etc...
jamesvmccann said:
I am currently on a galaxy s4, just started messing around with android a little. I am interested in switching to a slightly newer phone. Assuming I get a g3 that is on the latest OTA update, is it possible to unlock the bootloader or install any type of custom recovery? I am interested in flashing different roms, which I currently can't do on my verizon OF1 S4. If I can't on this phone, what about a g4? I am really only interested in phones with user replaceable batteries that I can swap out, so my options are somewhat limited. Thanks for any help.
James.
Click to expand...
Click to collapse
Hey, thanks for the quick reply. That is excellent news. Sealed the deal for me, I will be buying this phone sometime this weekend. Not familiar with any of the LG tools, or this TOT method you mentioned, so I will read through the threads carefully. Thanks again.
Sure thing!
back to stock, using TOT is this thread.
To get back to 10B from 35B you'll need the dll file in here
Once I was back at 10B, I used stumproot to get root and then used adb to push a bumped TWRP onto the device.
Other tip: Backup your phone's EFS partition before you do too much, you want to keep a copy of that around just in case...
jamesvmccann said:
Hey, thanks for the quick reply. That is excellent news. Sealed the deal for me, I will be buying this phone sometime this weekend. Not familiar with any of the LG tools, or this TOT method you mentioned, so I will read through the threads carefully. Thanks again.
Click to expand...
Click to collapse
just to clarify what was said,
there is NO way to unlock the bootloader
there is a bypass called Bump, similar to loki, but not. yes, you can do anything you would with a real unlock, but we also have no fastboot, and thats not fixable.
if this is ever effectively patched, and you take the update, flashing roms is over.
just wanted to make sure you understood, there was no true unlock.
Hello everyone,
Right now I have another thread for the root over ADB with DirtySanta, I've that far. I have a potential method but I need more information on it from somebody else so I am waiting on a response from him, once i have that I'll work on it. If you guys have any other potential ideas that'd be great.
Thanks,
Abine45
This is my link to the root on ADB. I will be updating it tonight or tomorrow for the convenience of others. Thanks for waiting.
http://forum.xda-developers.com/verizon-lg-v10/general/temporary-root-adb-t3523538
NEW INFORMATION FOUND! I GOT SIGNIFICANT ROOT ACCESS WITH DIRTYSANTA!!!
SO i used the DirtySanta fearing for my life I wouldn't ruin my device, well the v10 failed it. rebooted and it didn't do anything but reboot back into the normal bootloader and stuff. But what i found is that he go the dirty cow to just work under root, so maybe from there we could do something, anybody have any ideas?
people care but it seems kind of like you expect people who have no clue to do any of this to assist. Hence the reason they are willing to pay a rather large sum of money for a bounty.
1. You cannot repackage a TOT file, well you can but, because it is digitally signed so that the locked boot loader will recognize it and allow it access to image the system. Repacking a rooted version on MM or Nougat will brick the phone if it is not digitally signed by LG.
2. You can pull a copy of the boot image with dirty cow but you can do that from the TOT or KDZ. You cannot put a new one in with dirty cow with out bricking the phone.
3. Most likely not. SELINUX policies combined with updates and fixes have removed most of the previous exploits.
4. Nothing personal but if you are asking us where the boot image resides... that does not inspire anyone here to give you a hand. You need to be in the android devs forum asking these questions.
http://forum.xda-developers.com/android/software-hacking
Haxcid said:
people care but it seems kind of like you expect people who have no clue to do any of this to assist. Hence the reason they are willing to pay a rather large sum of money for a bounty.
1. You cannot repackage a TOT file, well you can but, because it is digitally signed so that the locked boot loader will recognize it and allow it access to image the system. Repacking a rooted version on MM or Nougat will brick the phone if it is not digitally signed by LG.
2. You can pull a copy of the boot image with dirty cow but you can do that from the TOT or KDZ. You cannot put a new one in with dirty cow with out bricking the phone.
3. Most likely not. SELINUX policies combined with updates and fixes have removed most of the previous exploits.
4. Nothing personal but if you are asking us where the boot image resides... that does not inspire anyone here to give you a hand. You need to be in the android devs forum asking these questions.
http://forum.xda-developers.com/android/software-hacking
Click to expand...
Click to collapse
How did Tungkick manage to repackage it then? The dirty cow exploit can exchange recovery though on an unlocked bootloader so shouldn't I be able to replace the boot image if done correctly wouldn't it work? I could possibly unpack everything and modify it all and test it but the issue comes back to repacking and flashing?
Ask him, but if you attempt to do this on a locked and encrypted boot loader then you will brick the phone. I mean think about it, if it was really just that simple every phone would be rooted and rom'd. Most phones running 6 or above have had the security vastly increased to make the phone secure so they can be used by government employees. Hence the introduction to SELINUX polices into the kernel which is why getting root is so unbelievably difficult. The locked boot loader resets everything at boot so getting root and maintaining is so hard combined with SELINUX does not allow standard root to perm. write anything to the system partition and then good old hboot kills anything you did mange to write on reboot... you can start to see how difficult this really is.
Tungkick did this on 5.1 Lollipop not 6.0 Marshmallow. The above mentioned difficulties with increased SELunix security plus 6.0 and up requires systemless root.
Still would love to know why no dev will go near this Phone. Does XDA have some deal with LG to not hack their phones? Very fishy why every dev avoids this device like it has the plague.
beavis5706 said:
Tungkick did this on 5.1 Lollipop not 6.0 Marshmallow. The above mentioned difficulties with increased SELunix security plus 6.0 and up requires systemless root.
Still would love to know why no dev will go near this Phone. Does XDA have some deal with LG to not hack their phones? Very fishy why every dev avoids this device like it has the plague.
Click to expand...
Click to collapse
LG are just not popular devices for hacking due to they make if extremely difficult. LG is a Corp. friendly company it is why Verizon loves them where companies like HTC are a bit more user sympathetic.
Funny you say that
beavis5706 said:
Tungkick did this on 5.1 Lollipop not 6.0 Marshmallow. The above mentioned difficulties with increased SELunix security plus 6.0 and up requires systemless root.
Still would love to know why no dev will go near this Phone. Does XDA have some deal with LG to not hack their phones? Very fishy why every dev avoids this device like it has the plague.
Click to expand...
Click to collapse
Funny you say that! Tungick said to me, and i quote "[email protected]#$g you" and blocked me from Facebook. He also told me that he wouldn't tell me because it's a secret. He didn't speak very great English, that's why there is an ing at the end of the F-bomb. I asked Jcase through XDA and he said he wouldn't and so i put it better explanation of help through an email and he said I was harassing him... In which case before hand he said he doesn't develop for LG because he says basically we are A-holes sadly and that we don't live up to our donation pledges.
That's what I'm saying though. It's like no dev will go anywhere near an LG device, at least the newer ones anyway.
They can't be much harder to crack than Samsung and those are getting cracked.
The person who rooted 5.1 on V10 basically tells you to F off. Yeah there is nothing odd about that.
beavis5706 said:
That's what I'm saying though. It's like no dev will go anywhere near an LG device, at least the newer ones anyway.
They can't be much harder to crack than Samsung and those are getting cracked.
The person who rooted 5.1 on V10 basically tells you to F off. Yeah there is nothing odd about that.
Click to expand...
Click to collapse
True, that's why I'm going to try to do it. If you know anything and want to help could use it.
Wish I could help. All I know here is you need systemless root on 6.0+. This has nothing to do with the v10 in particular. Systemless root should work on all devices 6.0+. It has already been achieved on the Galaxy s7 and it has locked bootloader. I don't see any reason why this can't work on the v10.
I just installed Linux on my computer gonna try somethings this weekend... We need to keep in touch
qujuanmiller said:
I just installed Linux on my computer gonna try somethings this weekend... We need to keep in touch
Click to expand...
Click to collapse
For sure, message me on xda.
beavis5706 said:
Wish I could help. All I know here is you need systemless root on 6.0+. This has nothing to do with the v10 in particular. Systemless root should work on all devices 6.0+. It has already been achieved on the Galaxy s7 and it has locked bootloader. I don't see any reason why this can't work on the v10.
Click to expand...
Click to collapse
Anybody can help! Do some research and send it and whatever you would like to do. Try different things, Try to modify bits of code and see what you can do! Always gotta start somewhere!
Modify code? You just went way above my head. I know about root, certainly don't know how to achieve it. That's why I count on the folks at XDA. I only have one v10, can't afford to brick it. Plus I already have root on 5.1.1 and I heard that 6.0 causes this phone to have problems.
Many, many v10's were offered up in order to attain root. Not one was taken by any dev. Maybe you can still get your hands on one of those.
You need to find someone that knows about systemless root. Without that you aren't getting anywhere.
beavis5706 said:
Modify code? You just went way above my head. I know about root, certainly don't know how to achieve it. That's why I count on the folks at XDA. I only have one v10, can't afford to brick it. Plus I already have root on 5.1.1 and I heard that 6.0 causes this phone to have problems.
Many, many v10's were offered up in order to attain root. Not one was taken by any dev. Maybe you can still get your hands on one of those.
You need to find someone that knows about systemless root. Without that you aren't getting anywhere.
Click to expand...
Click to collapse
The thing with that is the fact that even if I know how systemless root works, I still have no way to install it, so first I need to find a way to get in the system.
Think I might have a way though
From what I understand systemless root will modify the boot image to attain root. Super SU will decide how to flash based on firmware version. Will automatically root normal with Lollipop and down, will automatically modify boot image on Marshmallow and up. How you will be able to modify the boot image on a VS990 without bricking it I don't know.
In order to do system less root we need a unlocked bootloader... It says that everywhere I'm reading
Hi abine45,
Please read this post completely, the guys here are close to obtain the perma root on android 6, using dirty cow.
https://github.com/timwr/CVE-2016-5195/issues/9
Sent from my E2006 using Tapatalk
I looked at this thread... a bit more technical than I am able to do... did it end up working? Looks like no, but I might have missed something.
Thanks!
Hi,
Originally I had opened this thread in LG 5 AT&T forum. But, after a request from @Nitro1max1, I understood that he is right and it should be reached for more useres.
Please find the link for requesting LG to open our bootloader - https://www.change.org/p/lg-electro...utm_source=share_petition&utm_medium=copylink
Hopefully, we could make a change together.
last thing, this is the origina thread - https://forum.xda-developers.com/at...se-kdz-tot-t3587926/post71887733#post71887733
I will switch updating here since it will be more convinent to update in one single place.
Cheers,
Mor
stop
What happens when we reach 100 people?
Hopefully, LG will pay attention to our request. This device is no longer a valuable asset for LG (the newly LG G6 is out), therefore I guess we will have a fair odds with getting an unlocking method.
H840 now officially can unlock bootloader
I signed even though I know they will give a sh...t
The real question is who is the one who holds the responsibility for locking the bootloader,LG or AT&T?
I've included both of then in the petition, but, it will be easier to know who have the upper hand here.
About the H840, they are so lucky
Well, I got some idea that might work - but, maybe someone will prove me wrong.
While searching around for methods to unlock the boot-loader for AT&T varient, I came across lots of information about bricked phones. A method that had been proposed there, is to use some device that have JTAG protocol in order to revive the phone.
Digging around the JTAG subject, I found out that it's basicly an interface that have the ability to write new bootloader and pushing new .kdz images.
So, with using some common sense, it might be, that AT&Ts owners could use this method in order to flash the european bootloader into their system and bypassing this whole signed bootloader issue. after that, flashing a new european .kdz file will support this new bootloader that will transform the phone to EU modle.
Only thing is the IMEI and other modem related drivers needs to be taken in consideration.
What do you think about it?
P.S - I'm trying to get in touch with some JTAG box that might give a clearer picture about this subject.
ForMartha said:
Well, I got some idea that might work - but, maybe someone will prove me wrong.
While searching around for methods to unlock the boot-loader for AT&T varient, I came across lots of information about bricked phones. A method that had been proposed there, is to use some device that have JTAG protocol in order to revive the phone.
Digging around the JTAG subject, I found out that it's basicly an interface that have the ability to write new bootloader and pushing new .kdz images.
So, with using some common sense, it might be, that AT&Ts owners could use this method in order to flash the european bootloader into their system and bypassing this whole signed bootloader issue. after that, flashing a new european .kdz file will support this new bootloader that will transform the phone to EU modle.
Only thing is the IMEI and other modem related drivers needs to be taken in consideration.
What do you think about it?
P.S - I'm trying to get in touch with some JTAG box that might give a clearer picture about this subject.
Click to expand...
Click to collapse
No... nononononono. JTAG will not work, look around the threads. I'll say it one more time:
THE ONLY WAY, ONLY. WAY. THIS PHONE WILL GET A BOOTLOADER UNLOCK OR PERSISTANT ROOT IS BY CREATING A NEW EXPLOIT. DONE. THAT'S IT. LITERALLY NOTHING ELSE WILL WORK.
Honestly Annoying said:
No... nononononono. JTAG will not work, look around the threads. I'll say it one more time:
THE ONLY WAY, ONLY. WAY. THIS PHONE WILL GET A BOOTLOADER UNLOCK OR PERSISTANT ROOT IS BY CREATING A NEW EXPLOIT. DONE. THAT'S IT. LITERALLY NOTHING ELSE WILL WORK.
Click to expand...
Click to collapse
Well - you made your point with saying it.
I had looked in the threads but I didn't understand what lockes us with flashing new boot partition using JTAG method (it's like mounting the entire emmc to a point where it can be written with new bootloader etc.)
Please let me know what I'm missing here..
ForMartha said:
Well - you made your point with saying it.
I had looked in the threads but I didn't understand what lockes us with flashing new boot partition using JTAG method (it's like mounting the entire emmc to a point where it can be written with new bootloader etc.)
Please let me know what I'm missing here..
Click to expand...
Click to collapse
You can find the full explanation if you dig around, but basically for the G5 (and most devices) the bootloader unlock is not located in aboot, it is an actual change in the whole bootchain. You can modify aboot to disable a sig check, but that is not the same as unlocking the bootloader and doing so will break the signature of the aboot.img and hard brick your device.
Question is, what is the real differance between H850 to H820. they are sharing the same physical parts, but the bootloader is diffarent. so, by using external tool that will flash the new bootloader, it could be done, right?
Signed.
Honestly Annoying said:
THE ONLY WAY, ONLY. WAY. THIS PHONE WILL GET A BOOTLOADER UNLOCK OR PERSISTANT ROOT IS BY CREATING A NEW EXPLOIT. DONE. THAT'S IT. LITERALLY NOTHING ELSE WILL WORK.
Click to expand...
Click to collapse
few days ago LG G5 SE (H840 - Euro) was added to list of unlockable devices (probably it's a coincidence and not related to this petition, but also give a hope to owner of other G5 devices)
ayaromenok said:
few days ago LG G5 SE (H840 - Euro) was added to list of unlockable devices (probably it's a coincidence and not related to this petition, but also give a hope to owner of other G5 devices)
Click to expand...
Click to collapse
Yep, I agree. I tend to belive that it's LG's move. let's hope that they will do the same for the H820.
Meanwhile, I've spend sime time speaking with @autoprime (thanks for your time!) and the way he sees it is the following :
1. Finding some exploit in the H820 bootloader that will pretty much will effect all the other devices. Question is, if one will find it - will he share it on XDA or sell it to Qualcomm or LG. Time will tell.
2. Finding some leaked debug bootloader (one which the development team is using or the tech system) - That way we will be able to flash custom boot.img (AKA some open recovery).
Meanwhile, I'm doing some digging around for finding exploits.
Now, let's have our finger crossed for one to happen.
ForMartha said:
The real question is who is the one who holds the responsibility for locking the bootloader,LG or AT&T?
I've included both of then in the petition, but, it will be easier to know who have the upper hand
Click to expand...
Click to collapse
You have to take into account that for carrier-specific models, the CARRIER is actually the customer of LG, not the end user.
Only if you buy an unlocked device you are LG's customer.
So I'd guess that LG cannot provide a bootloader unlock for carrier-specific devices, this goes against the contract. Of course things change when the carrier agrees to the unlocking. But do you really think your carrier will allow this?
T-Mobile USA doesn't seem to care, but Verizon and AT&T?
Here in Europe carriers sell the regular H850, they "just" add additional bloat, so you can flash stock KDZs and unlock the bootloader. But the American carriers seem to stick to a different approach. Customers need to vote with their wallets to change this, but I think most people just don't care.
Well said BabelHuber,
Still, I have wish that it will be released eventually.
LG needs to do this or it will be my last LG phone.
Signed
Signed
Hi XDA haven't been on here for a while.
So I have a question I was given a S9+ from Sprint it's unlocked I'm currently using it on TMO but I don't have wifi calling nor video calling. I wanted to see if it was possible to flash a TMO firmware. Since it's still on July's patch here's a screen shoot of current firmware.
I moved from Sprint to Tmo, and just put in the sim and then updated the firmware through the system update interface. All works as expected.
The difference may (or may not) be, if the phone was unlocked by Sprint or by another method. My wife's phone was unlocked via "another method" and cannot get it to update system software. I haven't bothered looking into it further though, as we don't expect to keep the S9+ too much longer.
berzerkus said:
I moved from Sprint to Tmo, and just put in the sim and then updated the firmware through the system update interface. All works as expected.
The difference may (or may not) be, if the phone was unlocked by Sprint or by another method. My wife's phone was unlocked via "another method" and cannot get it to update system software. I haven't bothered looking into it further though, as we don't expect to keep the S9+ too much longer.
Click to expand...
Click to collapse
Yes mine was unlocked different method so it won't update normally.
That's why I asked if I could cross flash to TMO
Colombia81er said:
Yes mine was unlocked different method so it won't update normally.
That's why I asked if I could cross flash to TMO
Click to expand...
Click to collapse
If you figure it out, let us know. I'd be interested in giving it a go.
berzerkus said:
I moved from Sprint to Tmo, and just put in the sim and then updated the firmware through the system update interface. All works as expected.
The difference may (or may not) be, if the phone was unlocked by Sprint or by another method. My wife's phone was unlocked via "another method" and cannot get it to update system software. I haven't bothered looking into it further though, as we don't expect to keep the S9+ too much longer.
Click to expand...
Click to collapse
Colombia81er said:
Yes mine was unlocked different method so it won't update normally.
That's why I asked if I could cross flash to TMO
Click to expand...
Click to collapse
berzerkus said:
If you figure it out, let us know. I'd be interested in giving it a go.
Click to expand...
Click to collapse
if your phone is unlocked via whatever method, it wont interfere with system updates. OTAs will happen at regular intervals based on the firmware flashed on the phone and the recovery status. Stock recovery means that youll get OTAs, if youre not, its likely a glitch and has nothing to do with the unlock status.
If youre looking to get your phone working on tmob and its a spr phone, all you really need to do is unlock it, put the new sim in it and configure the APN. If you want full features like voLTE and wifi calling, then youll need to flash a tmob firmware version on your phone which requires the patched version of Odin. I have a Cricket branded (originally, at least) S9 and i flashed the U1 firmware on it via patched Odin and the phone now thinks its a factory unlocked S9, as i also unlocked it via "alternative methods". Perfectly seamless transition and i get OTAs all the time
berzerkus said:
If you figure it out, let us know. I'd be interested in giving it a go.
Click to expand...
Click to collapse
Sorry to revive the post, so i finally did the update it worked flawless i did the update to the latest firmware G965USQS7DTB1_G965UOYN7DTB1_TMB now i got Wifi Calling and VoLTE.
I used Odin3-v3.13.1-Patched
Unrar the firmware and then just load the files in Odin
Heres a great tut https://www.youtube.com/watch?v=bnPkwICq_Bw&t=