Is this phone more or less an international device? It shows as LG-F500K in the about menu. Would like to unlock and root.
AFAIK international version is H815
any F500 is korean version
not sure about the unlock, but for root, you can't use the current H815 method
Thanks. I realize I should have posted here initially. Guess I'll need to check procedures to determine if the device is unlocked already. I was told by the salesperson at olleh that the device was unlocked for both sim and bootloader.
So I'm in the U.S. On AT&T, but have ordered a G4 h815 European model. My understanding is this model has root and TWRP capability. Could someone with this model tell me what I should do? What I mean is, should I block any firmware updates, or is there a process necessary with LG to unlock the bootloader? I just want this phone to work on AT&T and for me to be able to load custom ROMs when they start appearing in the forums.
Thanks in advance for the help!
I Used To Own A Tmobile S3 Which I Enjoyed Using Custom Roms Like Cm 12, LiquidSmooth 4.1 And Pac Rom Just To Name A Few And The Lcd Broke . So One Of My Friend Is Selling Me A Used At&t S3 On Stock 4.4.2 For Quite Cheap. But My Problem Is ( Correct Me If Im Wrong) I Think I Read An Article Stating That You Cannot Use Custom Roms On S3s On Stock 4.4.2 Or It Will Brick It . Is This Correct ? An S3 Serves No Purpose To Me On Stock TOUCHWIZ . So Is It Possible To Root And Flash Custom Roms On S3s On OFFICIAL STOCK 4.4.2 TOUCHWIZ ?
Jaii_Versace said:
I Used To Own A Tmobile S3 Which I Enjoyed Using Custom Roms Like Cm 12, LiquidSmooth 4.1 And Pac Rom Just To Name A Few And The Lcd Broke . So One Of My Friend Is Selling Me A Used At&t S3 On Stock 4.4.2 For Quite Cheap. But My Problem Is ( Correct Me If Im Wrong) I Think I Read An Article Stating That You Cannot Use Custom Roms On S3s On Stock 4.4.2 Or It Will Brick It . Is This Correct ? An S3 Serves No Purpose To Me On Stock TOUCHWIZ . So Is It Possible To Root And Flash Custom Roms On S3s On OFFICIAL STOCK 4.4.2 TOUCHWIZ ?
Click to expand...
Click to collapse
The bootloader is not locked on the AT&T S3 (I747). You can use Odin to flash a custom recovery and flash any ROMs for d2att/d2lte you want. No unlocking required. It is a pretty modder friendly phone.
The thing you cannot do on the newer bootloaders is downgrade the bootloader. Attempts to downgrade anything beyond the 4.3 bootloader will result in a hard brick. This also prevents you from using the free sim unlocking method because it involves a firmware downgrade to 4.1. If you need to sim unlock the phone to use it on a different network you'll have to get a code from AT&T (they should provide one since a phone this old just about has to be off contract) or purchase one from a third party.
Jaii_Versace said:
... I Think I Read An Article Stating That You Cannot Use Custom Roms On S3s On Stock 4.4.2 Or It Will Brick It . Is This Correct ?... So Is It Possible To Root And Flash Custom Roms On S3s On OFFICIAL STOCK 4.4.2 TOUCHWIZ ?
Click to expand...
Click to collapse
I concur with @jason2678
I have an AT&T SGS3 (d2att/i747) that is on the NE4 bootloader and modem (4.4.2) and am running CM11 atm. As a matter of fact, none of the CM or AOSP roms since late in 4.4.2 development will run unless you are on one of the 4.4.2 bootloaders (NE4, NJ1, NJ2)
What you stated, quoted above, is true for the Verizon SGS3 (d2vzw/i535).
jason2678 said:
The bootloader is not locked on the AT&T S3 (I747). You can use Odin to flash a custom recovery and flash any ROMs for d2att/d2lte you want. No unlocking required. It is a pretty modder friendly phone.
The thing you cannot do on the newer bootloaders is downgrade the bootloader. Attempts to downgrade anything beyond the 4.3 bootloader will result in a hard brick. This also prevents you from using the free sim unlocking method because it involves a firmware downgrade to 4.1. If you need to sim unlock the phone to use it on a different network you'll have to get a code from AT&T (they should provide one since a phone this old just about has to be off contract) or purchase one from a third party.
Click to expand...
Click to collapse
Hello I am new here and could you please tell me the status of my phone since the phone does not provide me with option to enter unlock code after I inserted other carrier SIM.
I already have my unlock code given by AT&T.
I have CWM custom recovery installed
My phone info from Samsung Phone info Apps is
Bootloader version : I747UCUEMJB
PDA Version : I747UCUFNE4
CSC Version : I747ATTFNE4
Baseband Version : I747UCUEMJB
I have searched and tried with service mode method *#197328640# without success
Is Sim unlock related to bootloader
Thanks
car2carl said:
Hello I am new here and could you please tell me the status of my phone since the phone does not provide me with option to enter unlock code after I inserted other carrier SIM.
I already have my unlock code given by AT&T.
I have CWM custom recovery installed
My phone info from Samsung Phone info Apps is
Bootloader version : I747UCUEMJB
PDA Version : I747UCUFNE4
CSC Version : I747ATTFNE4
Baseband Version : I747UCUEMJB
I have searched and tried with service mode method *#197328640# without success
Is Sim unlock related to bootloader
Thanks
Click to expand...
Click to collapse
It appears that you have an NE4/Android4.4.2/KitKat rom installed over 4.3 bootloader and modem. I have seen several custom TouchWiz roms that run fine with this setup as long as one of a couple of custom kernels were installed. CM and AOSP roms will also run in this condition. BUT, from what I have read you will not be able to use the unlock codes. My reading indicates that you must be on complete stock ROM for the code to work, including stock recovery instead of CWM. ALSO, what I have read says that you only gt five attempts before the code becomes invalid.
I don't know why your phone is not asking for the unlock code, unless it has already been carrier unlocked. Even thouhg it is not asking for the code, does it function as it should?
Frequently the service modes do not work on custom roms, even TW based ones, because they are not using the stock dialers. I have also seen it reported that some were disabled with the 4.3 update and others in more recent updates.
Proceed carefully.
You may be able to enter the unlock code if the phone is running a stock dialler with a matching bootloader and modem combination.
dawgdoc said:
It appears that you have an NE4/Android4.4.2/KitKat rom installed over 4.3 bootloader and modem. I have seen several custom TouchWiz roms that run fine with this setup as long as one of a couple of custom kernels were installed. CM and AOSP roms will also run in this condition. BUT, from what I have read you will not be able to use the unlock codes. My reading indicates that you must be on complete stock ROM for the code to work, including stock recovery instead of CWM. ALSO, what I have read says that you only gt five attempts before the code becomes invalid.
I don't know why your phone is not asking for the unlock code, unless it has already been carrier unlocked. Even thouhg it is not asking for the code, does it function as it should?
Frequently the service modes do not work on custom roms, even TW based ones, because they are not using the stock dialers. I have also seen it reported that some were disabled with the 4.3 update and others in more recent updates.
Proceed carefully.
Click to expand...
Click to collapse
Thanks for respond
I had this phone since 3 years ago (new from ATT) and rooted stock rom with CWM 6.0.4.7 recovery touch . and I remember that I could unlocked through SERVICE MODE when I was overseas. ( sure I had used this phone with Other carrier) about 1 year ago I put this phone in my drawer I did factory reset and installed Stock firmware and update OTA to 4.3.
Last week I want to use this phone with Tmobile SIM but got Phone Not Allowed MM#6 message . The rom was still 4.3, Contact AT&T and got Unlock code.
but this phone didn't ask for unlock code entry option and still 4.3 , tried the whole weekend with service mode and upgrade to 4.4.2 via CWM recovery.
and still no luck
With your suggestion , it means that I don't have choice to downgrade back to 4.3 rom same with my bootloader and baseband? I heard we can't downgrade if we already in 4.4.2 , is that true?
But I still use stock recovery from CWM.
Before I proceed with replacing with stock recovery, is the stock recovery have to be 4.3 stock recovery or any version for S3? do I need to use odin to change to stock recovery?
if you have good link please help?
Thanks again
---------- Post added at 06:40 AM ---------- Previous post was at 06:33 AM ----------
audit13 said:
You may be able to enter the unlock code if the phone is running a stock dialler with a matching bootloader and modem combination.
Click to expand...
Click to collapse
Stock dialer means the entire Rom must be replaced to match my bootloader and modem combination or just replace the dialer in my case and still use 4.4.2?
Appreciated if you can help, thanks
Stock dialler requires a stock Samsung kernel.
From what I am seeing, you are on the 4.3 bootloader and modem. As I said before, there are custom TouchWiz 4.4.2 Roms that will run on the 4.3 bootloader and modem. Changing to a 4.3 rom, stock or otherwise, therefore would not be downgrading your bootloader and modem.
What rom are you on?
Some of the custom TouchWiz roms use dialers from the S5, therefore not stock for the S3.
Some of the custom TouchWiz Roms use the stock kernel, some use a custom kernel.
Did you flash a custom kernel?
What is your kernel version? (check under Settings > About Phone)
With the answers to the questions I asked, audit13 and I may be able to give more definite guidance. It could be as simple as flashing the stock kernel and a stock dialer. But, I can't tell at the moment.
car2carl said:
Thanks for respond
I had this phone since 3 years ago (new from ATT) and rooted stock rom with CWM 6.0.4.7 recovery touch . and I remember that I could unlocked through SERVICE MODE when I was overseas. ( sure I had used this phone with Other carrier) about 1 year ago I put this phone in my drawer I did factory reset and installed Stock firmware and update OTA to 4.3.
Click to expand...
Click to collapse
Are you saying you unlocked it before? If so it should still be unlocked. Flashing/wiping won't affect that, so it's pretty much a permanent thing. If so, maybe the Sim card you're using is an older one? they don't always work on tmobiles networks.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Are you saying you unlocked it before? If so it should still be unlocked. Flashing/wiping won't affect that, so it's pretty much a permanent thing. If so, maybe the Sim card you're using is an older one? they don't always work on tmobiles networks.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
audit13, dawgdoc, DocHoliday77
Thank you for your responses , Sorry I couldn't response any sooner as I worked in mountain/forest area that browsing the web is luxury
(yes I remember for sure I have used this cell phone overseas couple times and the way I unlocked through service mode. Way before AT&T OTA update since new)
I have weird situation that make me wondering if I had unlocked my S3 since message
"PHONE NOT ALLOWED MM#6" comes up if I use any other carrier beside AT&T
Per http://forum.xda-developers.com/showthread.php?t=2789917
thanks to OP
I just managed to change my bootloader to I747UCUFNE4 and also my baseband version to I747UCUFNE4
I still keep my CWM 6.0.4.7 recovery touch
I have Flashed with countless other rom such below:
I747UCUFNE4_Stock_Rooted_Odex.zip
I747UCUFNE4_Stock_Rooted_Deodex_3-31-15.zip
I747UCUFNE4_Stock_Rooted_3-31-15.zip
and even custom rom without any success
This was happened with my S3 after flash.
if I flashed with inserted active SIM Card (T Mobile or foreign SIM Card)
I will see PHONE NOT ALLOWED MM#6 after reboot
if I flashed without any SIM Card inserted after reboot :
- inserted foreign sim card and reboot again
I will have AT&T as roaming provider and for about few seconds received text message about fee from SIM issuer roaming to AT&T so means My S3 is unlocked...
(no... not so much!!!) in few minute I will have "PHONE NOT ALLOWED MM#6" and phone is useless as emergency only.
- inserted T-Mobile Sim Card and reboot again it shows "PHONE NOT ALLOWED MM#6" immediately
My Kernel Version :
3.4.0-1514807
[email protected] #1
Mon May 19 21:00:05 KST 2014
Thank you if you can help.
So you are not getting asked enter a network unlock code when running a stock rom with a foreign sim?
Does your provider use aws frequencies? The i747 does not natively support T-Mobile aws frequencies.
audit13 said:
So you are not getting asked enter a network unlock code when running a stock rom with a foreign sim?
Does your provider use aws frequencies? The i747 does not natively support T-Mobile aws frequencies.
Click to expand...
Click to collapse
No, It doesn't ask at all. just pop up "Phone not allowed MM#6."
my foreign SIM is ok.
I tested on Galaxy Note 4 T-Mo (unlocked) it grabbed ATT roaming,
tested on Iphone 4S (ATT-unlocked) it grabbed Tmobile roaming:laugh:
I just flashed stock recovery and still no go..
do I need to unroot?
Can I flash stock root rom with stock recovery
Thanks
What rom was on the phone when you inserted a foreign sim?
If you are running a Samsung rom, try this:
Www.unlockriver.com/Samsung-unlocking
I am using I747UCUFNE4_Stock_Rooted_3-31-15.zip
I just replaced CWM recovery with UCUFNE4 stock recovery
I did unroot with SuperSU and also
do factory setting through setting menu
basically my phone just as new factory setting but with UCUFNE4
the funny thing is :System Status: Custom is this related I have rooted this device before?
When I turn on bootloader mode (Odin Mode)
product name : SGH-I747
Current Binary: Samsung Official
System Status: Custom
Qualcomm secure boot : enable
warranty bit: 1
bootloader ap Swrev: 3
as I have stated at my 1st post that I had official unlock code from AT&T and got email from them the unlock PIN
but there is no option asking to key in the PIN with other carrier sim inserted .
I have checked also with Swappa esn check
and result is
Blacklisted => Not Indicated
This device does not appear to be globally blacklisted.
spent countless hours just to beat solving this device and read the threads and no result. And still "PHONE NOT ALLOWED MM#6"
I live in eu, i bought my m8 from t-mobile , i unlocked, i flashed custom roms, but its s-on , after 24months , i asked t-mobile for a unlocking key , but everytime when i want to enter that key, wont work, says wrong password.
Its posible that my mid/cid are messing someting with unlocking code ? Anyone got experience with similar problem? Should i flash some europian t-mobile stock rom to get solved this problem or?
And by the way is there a diference between us t-mobile and eu stock roms or they are the same ?
ps. i know some of those stuff are nubish for alot of guys. but i really want my network unlocked.
Thanx
Flash a stock ROM. If you are on an AOSP/CM ROM, it will do that to you. Stock ROM is the way to go to get your phone unlocked.
Hi! I bought a H815 version, foe a steal btw, "130$" Thinking that I could unlock the bootloader, but then doing more research only finding that the only way doing so is if I have a EU version.
So anyone know anyway I could trade or buy a EU or UK version for cheap so I could trade or it doesn't anyone know the status of the USA H815 bootloader status?
Also wtff why isn't the H815 version upgraded to marshmallow? This stock ROM is majorly broken .
tmobile one can be bootloader unlocked. h811.
I just did the same thing, got a h815 USA with locked bootloader.
Using LGUP I was able to flash version 20d MM and it is working fine.
You could try https://www.reddit.com/r/phoneswap/
I've got 20j MM running on my USA H815.
I updated with the .kdz file from here: http://forum.xda-developers.com/g4/general/kdz-firmware-v20j-united-kingdom-2016-t3518925
I used the installers and software from here: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Note that in the LGUP application, you need to click Update to select a .kdz file. You then need to exit and restart the program, then click refurbish to do a clean flash.