Related
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
GraphicsApathy said:
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
Click to expand...
Click to collapse
Can you go to your phone's settings => about device and check what the firmware settings are? Let's see what you have under firmware version, baseband version & build number. If possible, you may post a screen shot. Did you say you returned to stock by wiping your phone? Hardly seems likely and you would have probably needed to flash some firmware. Would you recall what you flashed?
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
GraphicsApathy said:
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
Click to expand...
Click to collapse
It's definitely on AT&T firmware. Apologies if I sound like I'm doubting you but are you certain it had T-Mobile firmware when you acquired it? I'd guess it was probably already an AT&T phone. If you bought it in the secondary market, there could have been some previous repairs involving parts swaps. Your safest bet may be to leave it as is and unlock for you use on T-Mobile. Trying to force on T-Mobile firmware now could result in a brick. As it is on 4.1.1, you can easily free unlock it by following the well tested method you'll find elsewhere in this forum.
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
GraphicsApathy said:
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
Click to expand...
Click to collapse
There could have been a previous JTag operation involving forced firmware installation on the MB. I've seen previous hybrid firmware involving one or other partition belonging to a different model - e.g. the modem, bootloader or something else but not the complete system.
Yes, that's the unlock method I was referring to. You won't get any confirmation that the process worked at the end. However, if you did it correctly, you would know it worked when you insert a non-compatible SIM card and it works. You should also be able to install T-Mobile apps especially the Wi-Fi calling app which is a really nice feature of T-Mobile.
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
UPDATE: Successfully obtained and installed T-Mobile microSIM. Still wish to replace AT&T boot animation and bloatware with T-Mobile's, though.
GraphicsApathy said:
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
Click to expand...
Click to collapse
OK. I'd be interested in knowing the outcome but I'll be surprised if it isn't unlocked already. Did some further research and there have been some reports of people successfully 'flashing' AT&T firmware on T-Mobile phones, and vice versa. Not sure why this should happen and conventional logic suggests the result should be a hard brick which is indeed the most common outcome. I'll also suggest you boot into download mode and see the information under bootloader. If the device has a T-Mobile bootloader, it may be possible to remove the OS via custom recovery and re-flash T-Mobile firmware.
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
GraphicsApathy said:
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
Click to expand...
Click to collapse
If download mode info shows secure bootloader enabled, the phone is, to all intents and purposes, now an AT&T phone. Attempting to flash T-Mobile firmware may likely result in a brick which would require a JTag fix. I was hoping download mode would show it still had a T-Mobile bootloader which could have allowed for safe firmware installation but this does not appear to be the case. Likely the motherboard was previously replaced or it suffered a brick and AT&T firmware was JTagged on. Either way, it would be safer to leave it as is.
Bummer. I'll leave it as is then. Thank you for all the help.
Dear LG Friends,
Long time XDA member, coming from the Windows Phone days HTC, then to Android HTC, bunch of Samsungs, and am now thinking about the LG space. More specifically moving from the Note 3 (T-Mobile US) running on the AT&T US, to the LG G3.
Before I do, I need some help from you guys. Which variant should I go for? I know my primary choices will be the T-Mobile and the AT&T variants (I believe they are 851 and 850)? Based on what's important to me, below, can you guys advise which variant to get?:
1. Development Support - Which variant has the MOST amount of Custom ROM options, that is on-going and kept current? I am spoiled with the Note 3, which has a massive development support. I have never tried the LG OS/Skin (escaping me what it's called), but if it's anything like the TouchWiz on Samsungs, I think it will be important to have CM/AOSP/AOKP and etc support.
2. This is related to # 1 - But I heard that only T-Mobile has the unlocked Bootloader? However, doing some research, I believe the AT&T and the Verizon and Sprint variants can also be unlocked? Is this true? If so, are they anymore limited than the factory unlocked T-Mobile variant?
3. LTE bands - I will most likely be using the phone on AT&T US, but if development options/support are higher on other variants, I might consider buying those models, even if they are missing some AT&T bands. For the Note 3 - T-Mobile is a Pentaband phone, meaning it had all the bands needed, so it could easily work on AT&T LTE, all the time. The reverse was not true.
And basically that is it. Initial instinct says to go chase the T-Mobile variant, based on my needs above. But please educate me and help me out if I have missed something. Thank you so much in advance!
Any input guys?
ProFragger said:
Any input guys?
1. Development Support - Which variant has the MOST amount of Custom ROM options, that is on-going and kept current? I am spoiled with the Note 3, which has a massive development support. I have never tried the LG OS/Skin (escaping me what it's called), but if it's anything like the TouchWiz on Samsungs, I think it will be important to have CM/AOSP/AOKP and etc support.
Click to expand...
Click to collapse
If you want OTA updates i suggest sticking with the AT&T variant since you have a valid AT&T sim. If you use a AT&T sim in a T-Mobile variant you wont ever get OTA updates and that means missing out on necessary fixes
1. All 3 US Variants are mostly the same, all have CM12 and all the random obscure AOSP roms as well
2. Well unlocked bootloader isnt that fancy it just means theres fastboot mode compared with the other editions where fastboot mode doesnt work properly even if you enable it. It essentially just makes installing TWRP easier since you dont have to root before installing it unlike other variants
Nevertheless Lollipop can be rooted on all US Variants right now really easily. But the only downside to it is that removing custom roms sometimes can be a pain since you have to use a way where it sometimes works and sometimes doesnt
itsbighead said:
If you want OTA updates i suggest sticking with the AT&T variant since you have a valid AT&T sim. If you use a AT&T sim in a T-Mobile variant you wont ever get OTA updates
1. All 3 US Variants are mostly the same, all have CM12 and all the random obscure AOSP roms as well
2. Well unlocked bootloader isnt that fancy it just means theres fastboot mode compared with the other editions where fastboot mode doesnt work properly even if you enable it
Click to expand...
Click to collapse
Hi Friend,
Thanks for your response, this is very helpful!
No OTA is never a thing I consider. Everything that matters to me, is what I listed already.
So, is the development support (new ROMs, updates and etc) the same for all US variants or would you say one variant is particularly more popular?
As for the locked bootloader, I thought you needed an Unlocked bootloader to flash Custom ROMs, no? It seems like "Bump" fixes this for Verizon, Sprint, and AT&T and gets you TWRP on your phone, but do we need to do extra steps everything to the boot.img for non T-Mobile variants? Or is it a one time mod and then regular flashing and Backups with TWRP?
If it's the same for all variants after Bump, then you're right, I will likely stay with an AT&T variant, thanks to that Band 7 LTE.
Thank you again for your help, hopefully more can chime in !
ProFragger said:
Hi Friend,
Thanks for your response, this is very helpful!
No OTA is never a thing I consider. Everything that matters to me, is what I listed already.
So, is the development support (new ROMs, updates and etc) the same for all US variants or would you say one variant is particularly more popular?
As for the locked bootloader, I thought you needed an Unlocked bootloader to flash Custom ROMs, no? It seems like "Bump" fixes this for Verizon, Sprint, and AT&T and gets you TWRP on your phone, but do we need to do extra steps everything to the boot.img for non T-Mobile variants? Or is it a one time mod and then regular flashing and Backups with TWRP?
If it's the same for all variants after Bump, then you're right, I will likely stay with an AT&T variant, thanks to that Band 7 LTE.
Thank you again for your help, hopefully more can chime in !
Click to expand...
Click to collapse
No need for any steps. Its just install TWRP and your on your way to installing whatever rom you want
Unlocked bootloader means that the system doesnt security (consistency) checks on system partitions
For LG G3, its because someone cracked the encryption for the kitkat android bootloader which means people can sign non stock boot.img without having to worry about unlocking the bootloader.
itsbighead said:
No need for any steps. Its just install TWRP and your on your way to installing whatever rom you want
Unlocked bootloader means that the system doesnt security (consistency) checks on system partitions
For LG G3, its because someone cracked the encryption for the kitkat android bootloader which means people can sign non stock boot.img without having to worry about unlocking the bootloader.
Click to expand...
Click to collapse
Gotcha, thanks again mate! Another (hopefully last) question. If I buy G3, where someone had already OTA'd to 5.0+, will I still be able to root it, install TWRP and get KK ROMs, like CM11 or something?
And vice versa, if the phone comes with KK, do I need to patch with Bump and then I can install ROMs?
Thank you again!
ProFragger said:
Gotcha, thanks again mate! Another (hopefully last) question. If I buy G3, where someone had already OTA'd to 5.0+, will I still be able to root it, install TWRP and get KK ROMs, like CM11 or something?
And vice versa, if the phone comes with KK, do I need to patch with Bump and then I can install ROMs?
Thank you again!
Click to expand...
Click to collapse
You can root it but i dont know if installing TWRP will work. I didnt want to try it incase it doesnt work and it runs the factory reset script instead. That happened to me once before
But i would say just to be sure, downgrade back to KitKat to do it
Yeah, if the phone comes with KitKat just root, install TWRP using root permissions and then your on your way
itsbighead said:
You can root it but i dont know if installing TWRP will work. I didnt want to try it incase it doesnt work and it runs the factory reset script instead. That happened to me once before
But i would say just to be sure, downgrade back to KitKat to do it
Yeah, if the phone comes with KitKat just root, install TWRP using root permissions and then your on your way
Click to expand...
Click to collapse
This is helpful, once again bud. So how would I downgrade back to KK? Would I have to run a stock firmware of some sort? In Samsung, he Flash a .Tar file through their flashing tool called the Odin. Would that be similarly done here?
I have a G3 that I tried the 1 click root method on. It said it was successful but on reboot it is stuck at the LG logo.
I am trying to follow a guide to flash the stock firmware. (androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants)
Can someone please tell me whether the guide is still good and whether the link it directs to (androidrootz.com/p/lg-g3-stock-fiwares) is where I want to get the firmware from? It seems to be over a year old at this point.
Also I am a bit confused about which firmware I want, I thought my version was the D855 International version, does that mean I can use either the D855 EUR or HK firmwares?
Sorry if some of these questions are obvious, got the device yesterday and it is my first Android phone! Also sorry the links are clickable, I don't have 10 pots yet.
Got it back to 4.4.2 using the aforementioned pages. Flashed the European firmware after reading some stuff elsewhere.
Hi,
I purchased the phone in the UK from the network carrier Vodafone. I have done a fair bit of research on the rooting and unrooting process mainly via videos and reading tutorials on XDA.
I would like to root the phone and gain super user access and install some Xposed modules but would also like to be able to unroot and flash back to a stock Vodafone firmware encase I need to claim under warranty. I have been trolling the internet to get the correct KDZ file and found this site (ttp://devtester.ro/projects/lg-firmwares/country.php?country=United+Kingdom). I believe that the correct firmware may be on here but am a little confused on what the suffix and software version means to be honest.
The reason for my confusion is that I updated the firmware to 6.0 Marshmallow through the LG bridge but when I now check my phones software version it states v20b-234-15. I assume this is right but from memory the first software version when I got the phone was something like H81510B_00.
I cant remember exactly what it was before unfortunately but the KDZ files I have found state H81510C_00 (Suffix - AVDFVK) and H81510C_00 (AVDFLR) and this does seem to make sense but I'm thinking it was B instead of C but and not 100% on that.
Do you think these KDZ files would be the correct one to flash back to encase I run in to some problems rooting?
I am also assuming that this KDZ is Android Lollipop and not Marshmallow so is it OK to use this to revert back from Marshmallow?
Thanks and any help would be much appreciated.
Ross
The 10X version are all Lollipop, 20X is marshmallow.
When flashing a KDZ on your phone, what's important is what model your phone is. H815 in your case.
If you want to restore to stock in case something goes wrong, you can find everything here: http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
In there is a link to this directory: http://storagecow.eu/index.php?dir=Xda/LG+G4/ where you find pretty much all KDZ files for G4 phones.
I'm not that experienced myself, but I rooted my phone just recently and I can share my experience with you.
I have a H815. It was a V10c-TWN-XX version (Taiwan). I updated to Marshmallow with LG Bridge also and the new software version was V20b-TWN-XX.
Marshmallow rooting is not possible on my phone because I can't unlock the bootloader on it. And Marshmallow rooting is only possible with an unlocked bootloader. Unlocking the bootloader is only possible on European phones (http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS). I asked autoprime (renown user and developer here) if I can unlock bootloader after flashing an European KDZ on it. He said no, having European software on it is not enough, it has to be a phone manufactured for the european market. Dont know why, guess because of different hardware.
So, not being able to root MM, I had to revert back to stock (downgrade) using one of the KDZs.
I chose the most recent one in the directory I linked (which is the Poland H81510E). In the "Go Back to Stock" thread I linked the OP says to use LG Flash Tool 2014, which unfortunately doesn't work with Marshmallow. But fret not, it works with LG UP! http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
When I tried flashing the KDZ with Flash Tool 2014, the process failed with an error at 5%. It worked flawlessly with LG UP. Here's more information regarding downgrading, but it really isnt hard. Just download + install LG UP. Launch it. Connect your phone. Choose KDZ file. Select option "upgrade". Hit start.
NOTE: after the firmware update was done, the phone rebooted automatically and for me it stuck at at the LG Logo (bootloop). But a simple hard factory reset did it, the phone booted and my new version was 10e-something. With Lollipop 5.1 of course.
After that, I rooted my phone using this pre-rooted image: http://forum.xda-developers.com/g4/development/h815-eu-l-p-t-sea-twn-t3176195
and this guide: http://forum.xda-developers.com/g4/...-tmo-vzw-intl-variants-soon-root-lg-t3164765/
I now have a "H81510e-EUR-XX" Lollipop 5.1 with root (SuperSU 2.49).
I don't really know about Vodafone and if carrier specific firmware is necessary in this case. If not, you could use any 815 firmware.
From the site you have linked with the KDZ files..... it seems they are all the same.
If you check the table for H815 KDZs from Vodafone, there are some 10C and 10D versions. Now I compared the fileKey parameter in the URL to the 10C files and the 10D files and also the bytes of the files.
All the 10C version are identical to each other, same for 10D.
Check out this screenshot I made for you: http://i.imgur.com/Ie0w4us.png
Bytes are also identical, so it's pretty safe to say those are the same files.
Dont know why they are listed several times there. The suffix doesnt matter.
I'd grab a 10D if I were you. But I think the Poland 10E should work, too. Better confirm it with somebody else though.
If you flash your system to 10e, you can use the pre-rooted image I used. Otherwise you will have to inject root yourself: http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586. In this method you create an image of your system and inject root into the image, which you then flash back on your phone.
I have the LG G8 Thinq Sprint Model (LM-G820UMKIT) bought it pre-owned. I recently saw that there was a guide to unlock and root the LG G8 however the requirements is for the device to be on Android 10. I'm currently still on Android 9 and I am unable to update via software update, or through LG Suite. Is there anyway to update to A10?
Adelino80 said:
I have the LG G8 Thinq Sprint Model (LM-G820UMKIT) bought it pre-owned. I recently saw that there was a guide to unlock and root the LG G8 however the requirements is for the device to be on Android 10. I'm currently still on Android 9 and I am unable to update via software update, or through LG Suite. Is there anyway to update to A10?
Click to expand...
Click to collapse
It's unfortunate, but the guide is a bit misleading. I'd bet the person that wrote it had a specific version of android, and didn't know / want to indicate it would work on any other as they hadn't tested it.
But, there's virtually zero reason the unlock procedure shouldn't work on any version of android. The reason is very simple; all you do in that guide is use edl mode (any qualcomm device can do that), you flash the engineering abl to abl partition (it won't matter what version of android the rest of the system is), you go to fastboot (that's what the eng abl gives you), you unlock the boot-loader, you use fastboot to flash the original abl back.
Makes sense? See, you don't use that eng abl to boot the OS, you don't use it for anything at all, except to unlock the boot-loader. That's it. Period. There's no reason for it to not work no matters what version of android your system is.
As far as Sprint update goes... talk to sprint, ask them for help getting it updated. Sprint does not make their kdz available, if you don't get any OTA update from them, you'll then be faced with finding someone's partition backup, and all the complications involved / and danger, of flashing that.
The other option would be to crossflash to a rom that has a kdz. It too is involved and complicated, and potentially dangerous.
good luck
AsItLies said:
It's unfortunate, but the guide is a bit misleading. I'd bet the person that wrote it had a specific version of android, and didn't know / want to indicate it would work on any other as they hadn't tested it.
But, there's virtually zero reason the unlock procedure shouldn't work on any version of android. The reason is very simple; all you do in that guide is use edl mode (any qualcomm device can do that), you flash the engineering abl to abl partition (it won't matter what version of android the rest of the system is), you go to fastboot (that's what the eng abl gives you), you unlock the boot-loader, you use fastboot to flash the original abl back.
Makes sense? See, you don't use that eng abl to boot the OS, you don't use it for anything at all, except to unlock the boot-loader. That's it. Period. There's no reason for it to not work no matters what version of android your system is.
As far as Sprint update goes... talk to sprint, ask them for help getting it updated. Sprint does not make their kdz available, if you don't get any OTA update from them, you'll then be faced with finding someone's partition backup, and all the complications involved / and danger, of flashing that.
The other option would be to crossflash to a rom that has a kdz. It too is involved and complicated, and potentially dangerous.
good luck
Click to expand...
Click to collapse
Thanks for the advice! Yeah I wouldn't see why the device shouldn't be able to boot into EDL mode. I don't mind trying the unlock procedure with the guide, just sucks that there is no MSM tool to unbrick the device if anything does happen. As for updating to A10 I can live without, I only asked because the guide specified A10 as an requirement, which you already answered.
Adelino80 said:
Thanks for the advice! Yeah I wouldn't see why the device shouldn't be able to boot into EDL mode. I don't mind trying the unlock procedure with the guide, just sucks that there is no MSM tool to unbrick the device if anything does happen. As for updating to A10 I can live without, I only asked because the guide specified A10 as an requirement, which you already answered.
Click to expand...
Click to collapse
I would suggest that you look at the bkerler edl tools. Don't do anything until you backed up the device completely.