N7100, standard software, lost Network unlock after freeze, can't now unlock again. - Galaxy Note II Q&A, Help & Troubleshooting

Standard device, running 4.4.2, not rooted or changed other than by downloads provided by KIES, originally on 3 Ireland network, was unlocked and moved to Vodafone over 12 months ago with no issue, using unlock code provided by 3 after the end of contract period was reached.
Had a few strange issues recently but nothing I could be sure of, then one night this week, the phone locked and would not accept any key presses. Removed battery to force power down, then restarted, which has always worked in the past on the rare occasions when this has happened, but this time, when it restarted, it asked for a Sim Network Unlock PIN, which at the time I didn't recognise as being the unlock code supplied by 3.
I don't know if there are issues about the number of times this code can be entered, if there are, due to all sort of errors by Vodafone Support, that limit has probably been exceeded.
The other possibility is that a hardware issue has developed, but as it is only the phone network won't work, my instinct is telling me that this is a software and security issue that may have been triggered by too many failed unlock requests, though it still asks for an unlock code on power up.
So, what have I tried. After several frustrating calls with Vodafone and Samsung support failed to resolve the issue, I dismissed the PIN request and made sure I had some backups of things like Contacts, which worked, so the phone can communicate via USB, and it's also working with no issues via WiFi networking, as I can access things like Facebook via WiFi. My Google account is also working, it's downloaded and updated the applications that are installed on the phone,
In the absence of any real assistance from Vodafone or Samsung, in desperation, I've tried a factory reset, and also tried wiping the cache, but neither of these options are getting rid of the Unlock Sim request, which suggests to me that there is a flag or code somewhere deep in the system that's not allowing a full reset, and that may be related to too many failed Network PIN Entries.
Can I recover this phone, or am I better to just abandon it and get a replacement device, which in all honesty I don't need, the Note II is doing all I need at the moment, and a replacement is going to be an expense I'd rather not have to commit to right now.
I have all the details of the versions, IMEI etc, they are all accessible from within the phone using various *# codes, and they all are still correct and match what they should.
Talking to a local repair shop, if they ask for an unlock code, they are saying that the code they get will be the same as the one I already have received from 3, and as that seems to be not working, they are saying there's no point getting a code from them.
So, where do I go from here? Somehow, I think I need to find a way to wipe everything in the phone, and then reset the IMEI to the correct value, which should in theory allow the device to work again, and recognise the unlock code. That's a lot more than I've done on a phone, I'm computer literate, but not Android and phone experienced, so a lot of the buzz words are not familiar, or mean different things to what I've been used to on other systems.
If I am going to be completely wiping it all, is there any way I can change the service provider to get rid of the issues with the network unlock code, or is that asking for more aggravations?
Thanks in anticipation.

There is a free method that can be used to sim unlock the sgh-i317m which is the North American version of the Note 2. You had to flash back to a stock 4.1.1 ROM, and follow this guide: https://forum.xda-developers.com/showthread.php?t=2014982
The 4.1.1 ROM for the sgh-i317m Note 2 from sammobile.com does not include the 4.1.1 bootloader which is why the downgrade from stock 4.4.2 to 4.1.1 works.

Related

Can't fully install stock ROM with Odin - help please!

Hi, and firstly, thanks to any and all who offer their knowledge to assist my conundrum.
I recently purchased a Bell Canada version of the SG Note 2 (i317), I am on Telus so I attempted to Unlock the phone. I looked online and found people were having success unlocking these phones for free using the *#197327640# method, (whereby you go into the service mode, turn off the PERSHO_256 and then INITIALLIZ).
I tried this method and the phone then seemed to work with my telus sim, but only for voice, not data. When I put in a Bell SIM from a friend, both voice and data worked fine - which tells me its not a hardware (radio) issue. I also tried using another friends Telus SIM and had the same results as mine - which tells me it's not a SIM error. Also, all the settings in the mobile network area appeared to be correctly set up.
So, my next step was to try and reflash the phone to the stock Bell ROM and then just buy an Unlock code. I downloaded the stock ROM (2 different ones actually) and used Odin 3.07 to reload the ROM. I've tried it several times now, with both Bell ROMs and each time it says it's been successful, but the phone remains in the same, partially unlocked state.
It seems as though by using the PERSHO_256 method I have permanently, PARTIALLY unlocked the phone. I can't seem to re-lock it by installing the stock Bell ROM, and since it's unlocked, I can't get the foreign SIM error to come up to enable me to put in my purchased unlock code.
If anyone has any insights, it would be GREATLY appreciated. Thanks!
-Luke
did you check and/or setup the apn? it may be just the apn is not set correctly or you have to manually input hte apn
sounds like just APN needs setting...
APN?
How would I check/setup the APN? Is this to allow me to do a full reflash to a stock ROM or to access data with the phone in it's current state?
left ownsho
So I went into ACCES POINT NAMES and checked the sp.telus.net box, no change. Did a restart. No change Any ideas?
Wooooo Hooooo!!!
So, it's working now!!! I dug a little deeper and found the correct APN settings for TELUS. NOW IT F*@^&#*&@ING WORKS!
Thanks so much for pointing me in the right direction!!!

[Q] Device won't connect to any network

Hi, I have an SGH-I747M that was originally purchased through Bell. In an attempt to unlock to make it work on Koodo, I went through SamMobile (after reading there was no way to unlock post 4.3 OTA update) and that seemed to half work.They resell a service from 123unlock.nl which is a client that uses adb or something of the sort to mess with phone files. The program afterwards said "Your phone is now unlocked! However if you don't see any carriers you need to do something in the advanced option and pay another $2x.xx dollars to do so". I didn't feel like giving them any more money at this point because I was upset that what I originally paid for didn't work properly. The fix was apparently an option in the advanced options that was an NVM repair/rebuild or something of the sort. I should have screenshotted the issue but of course didn't.
Now, the phone will boot up and does not offer me a SIM unlock option anymore. When searching for carriers it will ever only find Rogers for some reason. It won't recognize Koodo or Telus or anything of the sort (or bell when my bell SIM is in). Every now and then when it boots up, it will successfully send a text but only within a 5-10 second time frame after boot (I've made 1 phone call as well for 3 seconds). I've tried the Koodo SIM in my own Nexus 5 and works fine so the network is okay at least (plus I called Koodo and they verified on their end things look good... if that makes a difference). The SGS3 won't even accept an original Bell SIM at this point. It's always on either no network, 1 bar or full bars, never anything in between. I've tried flashing different ROMs from Bell stock to Koodo stock and CM11 and it won't work no matter what I do. Under all ROMs it pops up an "ME Returned temporary error" message on the screen.
I'm hoping someone might have seen this issue before or know what's going on with the phone that I can fix. I'm assuming it's something to do with the modem part of the phone that's refusing to connect to carriers but I'm at a loss to fix it. I haven't tried flashing different modems on it yet because I'm unsure which one would be a good fix and no one has had roughly the same issue I could find in 3 days of Googling for this issue. Any ideas are greatly appreciated. Thanks.
sgtcanadian said:
Hi, I have an SGH-I747M that was originally purchased through Bell. In an attempt to unlock to make it work on Koodo, I went through SamMobile (after reading there was no way to unlock post 4.3 OTA update) and that seemed to half work.They resell a service from 123unlock.nl which is a client that uses adb or something of the sort to mess with phone files. The program afterwards said "Your phone is now unlocked! However if you don't see any carriers you need to do something in the advanced option and pay another $2x.xx dollars to do so". I didn't feel like giving them any more money at this point because I was upset that what I originally paid for didn't work properly. The fix was apparently an option in the advanced options that was an NVM repair/rebuild or something of the sort. I should have screenshotted the issue but of course didn't.
Now, the phone will boot up and does not offer me a SIM unlock option anymore. When searching for carriers it will ever only find Rogers for some reason. It won't recognize Koodo or Telus or anything of the sort (or bell when my bell SIM is in). Every now and then when it boots up, it will successfully send a text but only within a 5-10 second time frame after boot (I've made 1 phone call as well for 3 seconds). I've tried the Koodo SIM in my own Nexus 5 and works fine so the network is okay at least (plus I called Koodo and they verified on their end things look good... if that makes a difference). The SGS3 won't even accept an original Bell SIM at this point. It's always on either no network, 1 bar or full bars, never anything in between. I've tried flashing different ROMs from Bell stock to Koodo stock and CM11 and it won't work no matter what I do. Under all ROMs it pops up an "ME Returned temporary error" message on the screen.
I'm hoping someone might have seen this issue before or know what's going on with the phone that I can fix. I'm assuming it's something to do with the modem part of the phone that's refusing to connect to carriers but I'm at a loss to fix it. I haven't tried flashing different modems on it yet because I'm unsure which one would be a good fix and no one has had roughly the same issue I could find in 3 days of Googling for this issue. Any ideas are greatly appreciated. Thanks.
Click to expand...
Click to collapse
Can you check your phone's settings => About Device and let's know what parameters you have there (Android Version, Baseband Version, Build Number>.
You mentioned you can send text or make call within a limited time frame. Was that with the Koodo SIM or the Bell? If the former, it would suggest the phone is unlocked to some extent but you are probably experiencing a baseband failure or need to correct the APN settings. Did you also try doing a factory reset?
Larry2999 said:
Can you check your phone's settings => About Device and let's know what parameters you have there (Android Version, Baseband Version, Build Number>.
You mentioned you can send text or make call within a limited time frame. Was that with the Koodo SIM or the Bell? If the former, it would suggest the phone is unlocked to some extent but you are probably experiencing a baseband failure or need to correct the APN settings. Did you also try doing a factory reset?
Click to expand...
Click to collapse
The information you're asking for is attached.
The texts I got off were from the Koodo SIM. I have updated the APN as well, and I did do a flash back to stock resetting all settings through Kies emergency update. I found a little trick where if you softbrick it by trying to flash 4.1, it'll give you the "Please use kies" error and that'll take you back to full stock 4.3. I'm pretty sure the baseband failure is the option I need to explore but at this point I don't know where to go to fix this.
Edit: I read this online and tried it: "The 4.3 update introduces a "security feature" which requires carrier- or region-locked phones to be activated once on the original locked network before the unlock code will work." The phone didn't recognize any network with the Bell SIM in except "EXT" which I've never heard of before and it did not connect properly so that didn't work. I also read that inputting #7465625*638*# will give me the Samsung SIM unlock menu which it did however I don't think the issue here is with the root and I'd hate to pay $50 at this point to have that not work as well.
sgtcanadian said:
The information you're asking for is attached.
The texts I got off were from the Koodo SIM. I have updated the APN as well, and I did do a flash back to stock resetting all settings through Kies emergency update. I found a little trick where if you softbrick it by trying to flash 4.1, it'll give you the "Please use kies" error and that'll take you back to full stock 4.3. I'm pretty sure the baseband failure is the option I need to explore but at this point I don't know where to go to fix this.
Edit: I read this online and tried it: "The 4.3 update introduces a "security feature" which requires carrier- or region-locked phones to be activated once on the original locked network before the unlock code will work." The phone didn't recognize any network with the Bell SIM in except "EXT" which I've never heard of before and it did not connect properly so that didn't work. I also read that inputting #7465625*638*# will give me the Samsung SIM unlock menu which it did however I don't think the issue here is with the root and I'd hate to pay $50 at this point to have that not work as well.
Click to expand...
Click to collapse
It's unlikely to be the regional lock as this feature means your phone will work with compatible networks in the region but not in other regions. You may, however, run Chainfire's Region Lock Away to be sure <http://forum.xda-developers.com/showthread.php?t=2470551>
Your firmware settings look OK so I'd be doubtful about a corrupted modem. You may still try to re-flash the modem via custom recovery. Download link for the CWM flashable zip is available here ... http://www.androidfilehost.com/?fid=23252070760973552
The guys who sold you the original code seem to have sold a dud as there is no reason for them to be asking for secondary payments and this sounds like the footprint of a regular scam. I'd be surprised though as they seem to be well rated
Larry2999 said:
It's unlikely to be the regional lock as this feature means your phone will work with compatible networks in the region but not in other regions. You may, however, run Chainfire's Region Lock Away to be sure <http://forum.xda-developers.com/showthread.php?t=2470551>
Your firmware settings look OK so I'd be doubtful about a corrupted modem. You may still try to re-flash the modem via custom recovery. Download link for the CWM flashable zip is available here ... http://www.androidfilehost.com/?fid=23252070760973552
The guys who sold you the original code seem to have sold a dud as there is no reason for them to be asking for secondary payments and this sounds like the footprint of a regular scam. I'd be surprised though as they seem to be well rated
Click to expand...
Click to collapse
I've tried reflashing the modem and I've actually paid $50 for the unlock code from Bell, the original carrier. I used the code to get the network unlock menu and inserted the code. I still get between 1-4 bars now with no network access on either network. It's not showing anything except Rogers still in network operator selection.
Any ideas at this point? It refuses to connect to any networks. I'm out of options.
Edit: I don't know if this makes a difference, but when I do root explorer I can't actually find the nv_data.bin file. It doesn't have anything of the sort in the /efs folder.
sgtcanadian said:
I've tried reflashing the modem and I've actually paid $50 for the unlock code from Bell, the original carrier. I used the code to get the network unlock menu and inserted the code. I still get between 1-4 bars now with no network access on either network. It's not showing anything except Rogers still in network operator selection.
Any ideas at this point? It refuses to connect to any networks. I'm out of options.
Edit: I don't know if this makes a difference, but when I do root explorer I can't actually find the nv_data.bin file. It doesn't have anything of the sort in the /efs folder.
Click to expand...
Click to collapse
Please let me understand a few things ... when you first acquired the phone, was it working normally on Bell prior to the first unlock attempt or you never used it at all until you tried Koodo? Secondly, was the unlock code you got from Bell identical to the one you got from the online service?
I'm trying to establish if it is a case of hardware failure not reported by the previous user especially if you bought it pre-owned from the secondary market. If you are not sure of the previous usage history, it could be a faulty or disconnected antenna which may require professional service. On the other hand if you are sure it was working fine prior to the unlock attempt, try the following ...
1) From the dial pad, enter *#197328640#
2) [1] UMTS
3) [1] DEBUG SCREEN
4) [8] PHONE CONTROL
5) [6] NETWORK LOCK
6) [3] PERSO SHA256 OFF
7) Press Menu => Back button and go all the way back to Step 3) above
8) [6] COMMON
9) [6] NV REBUILD
10) [1] NV REBUILD
Reboot and restart and let's see if this does it.
I've got a similar symtom different scenario (sister in-laws phone). I was also only able to see Rogers network on a search. I've got Telus version. It was working fine until it was brought to the Philippines, got unlocked there and brought back to Canada.
I was only able to see Rogers network until I went into the Service Menu (similar to above) and found the option to change the band. I changed it to Automatic. After that I was able to see Telus network. When trying to connect/register it would take a long time and give me an error "Unable to connect, try again later". I still need to do more troubleshooting, but that might be something to look at.
Note: Phone has stock MOD ROM, rooted and unlocked.

Experiences SIM unlocking SGH-I747 (Galaxy S III) AT&T 4.3 with codes

Has any one had positive experiences with SIM unlocking the AT&T sgh-i747 (Galaxy S III) after the 4.3 update with a code??
I paid $14.99 to SamMobile to unlock using their software but it didn't work and they don't answer my emails. But that's not with a code
Admins: if there is a thread for this already, please point me to it. I could not find one with successes after the 4.3 update
Note that AT&T didn't want to give me a code: I had cancelled the service already and paid the ETF (foolish, I know), and now they don't care about me
I've seen plenty if users have success unlocking with a code. I don't know about how sammobile does it though.
You have to be stock for it to work BTW.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Thanks doc. By "stock" you mean the official ROM without root? As I said, it's not the original version (4.1.1) but the OTA update to 4.1.3 by AT&T
I will have to buy some code
Root doesn't matter. Many custom stock based ROMs will also work but some may have removed some needed files which is why I just said stock. As long as its stock based and has the stock dialer it should work though.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
So, no one has any experience to share? has anyone unlocked a Galaxy S III 4.3 with a code? It's OK if you prefer to PM that info to avoid being interpreted as advertising
Official AT&T Unlock Code Fails
My contract ended id-September so I requested an unlock code, which was previded (below). I sent two separate requests for the unlock code and the number provided twice matches. I tried the unlock code (while using a T-Mobile SIM card) twice and the phone said the code was incorrect.
I prepared the phone by doing a factory reset. These are the phone details:
Model number
Samsung-SGH-I747 running
Android version
4.4.2
baseband
I747UCUFNE4
kernel
3.4.0-1514807
[email protected] #1
Mon May 19 21:00:05 KST 2014
Build number
KOT49H.I747UCUFNE4
These are the instructions provided:by AT&T:
Thank you for contacting AT&T Customer Care about unlocking your AT&T Mobile device. We have reviewed your request and confirmed that the device may be unlocked. You should complete the unlock process before porting out your number for use with another carrier. Please allow 24 hours upon receipt of this notification to complete the unlock process.
Your Unlock Code is :12345678
Unlock Steps - Use Non-AT&T SIM Card
1. Power off the device and insert a non-AT&T SIM card.
2. Power on the device.
3. Network Lock displays: Enter the device unlock code.
4. Enter the eight-digit unlock code.
5. Press OK.
Note: You are allowed five attempts to unlock before your device permanently locks to the AT&T network. Note: If your device has been altered from the original manufacturer's standards, such as rooting the device, your unlock code may not work and you will need to contact the original manufacturer for assistance.
For questions regarding AT&T Mobile device, please visit the Phone/Device Learning Center. Thank you for your business. For other questions about our AT&T wireless service or other Mobile devices, please visit att.com.
I've tried the unlock twice and it did not work. The phone is rooted. I think I manually installed 4.4.2 because the OTA failed many time to update.
I think these instructions are confusing in that step 3 and step 4 both say enter the unlock code. Is there a second code? I thought an phone unlock code is a single 8-digit number.
I have successfully unlocked an old HTC Aria so I have a little bit of experience performing unlocks. But if you have advice I'd appreciate hearing your thought.
wpscully said:
My contract ended id-September so I requested an unlock code, which was previded (below). I sent two separate requests for the unlock code and the number provided twice matches. I tried the unlock code (while using a T-Mobile SIM card) twice and the phone said the code was incorrect.
I prepared the phone by doing a factory reset. These are the phone details:
Model number
Samsung-SGH-I747 running
Android version
4.4.2
baseband
I747UCUFNE4
kernel
3.4.0-1514807
[email protected] #1
Mon May 19 21:00:05 KST 2014
Build number
KOT49H.I747UCUFNE4
Click to expand...
Click to collapse
Forgive me for asking but is your phone running a stock ATT ROM? Does the imei obtain from the phone match the imei on the label under the battery?
audit13 said:
Forgive me for asking but is your phone running a stock ATT ROM? Does the imei obtain from the phone match the imei on the label under the battery?
Click to expand...
Click to collapse
Yes, the IMIE shown on the label and via About device --> Status are identical. I asked AT&T twice for the unlock code because I thought maybe I sent the wrong code. I'm 99.9% sure the IMIE number I used is correct.
Yes, the flavor of Android installed is the AT&T version. If I recall, in August 2014 I used ODIN to manually install 4.4.2 because the over-the-air update was not working. (The OTA would download but fail to install. I'd wait for two or three days before I could try a second, third, forth... time.) I have also done a reset via Accounts --> Backup and reset. The MicroSD card was erased too, through the reset process. The lock screen, the home screen, all the typical AT&T add-on applications seem to be as they were when I purchased/upgraded the phone two years ago.
4.4.2 is rooted and I have Chainfire's SuperSU v2.00 Pro installed.
I should mention this: When I look at About device --> Status, all the way at the bottom, is "Device status" which shows "Custom". This isn't a setting. I suppose this is why the network unlock code is not working.
I'm not sure what to do next. I can't recall the page on XDA which guided me through the install of 4.4.2. I'll look a little harder because I'm sure I used XDA as my guide for the upgrade. Perhaps I'll try to install a non-root 4.4.2 image.
I never expected that I'd have five and only five tries at network unlock. I've used three tries... I need to make sure the last two work! Any advice is appreciated.
Sorry, I'm out of ideas. All I can suggest is flashing back to completely stock with stock recovery and no root access.
someniceguy said:
Note that AT&T didn't want to give me a code: I had cancelled the service already and paid the ETF (foolish, I know), and now they don't care about me
Click to expand...
Click to collapse
In my case AT&T told me they would not give me a code until I paid off my contract. I would seem they don't care about their former or current customers.
I showed them though, I was still on 4.1.2 and simply donwgraded my modem and used the free unlock method. It's now time to upgrade to kitkat.
@wpscully
Don't know if you still need help, but maybe this would do the trick? I think it's the last post that's describing a different method of getting the unlock code to work.
http://forum.xda-developers.com/showthread.php?p=55677344
Sent from my SAMSUNG-SGH-I747 using Tapatalk
@DocHoliday77, your pointer you mention above has proven invaluable. For the record here is the link I used; http://forum.xda-developers.com/showpost.php?p=55677344&postcount=137 MrBrown72 has a secret code and menu selections which seem to tell my phone to ignore all the customizations I made (root, maybe removing some AT&T bloat) and accept the valid network unlock code AT&T provided when my contract ended. The phone is now working on T-Mobile, rooted still, and none the worse for wear. I also want to thank Audit13 for advice on what not to do, and well as his guiding me so I found the hints that the phone considered itself "custom".
Finally I'll mention that if I had not been able to unlock this phone I never, ever would have selected AT&T as a cell provider. In this process they were professional, respectful, and helpful. T-Mobile didn't get my old line transferred before my AT&T contract ended. AT&T probably could have made clearing up this transfer very hard. But they were kind, understanding and efficient in reinstating my old number briefly so T-Mobile could finish the transfer.
I know others have had trouble with vendors. I wish all companies could understand that being unhelpul or rude is the fastest way to lose a customer for life.

SGH-I747M from bricked and no IMEI/ESN to working!

Hi,
After several days trying to unlock my phone and getting it bricked I finally managed to have it in a working condition and unlocked! I'm not sure if what I did unlocked it, but at least it's rooted and in working conditions.
So I decided to share my story and all the steps that I took to fix it. I would have written just the steps but somebody might find specific parts of the story useful.
Original Equipment and Status:
Phone: Samsung Galaxy S3 SGH-I747M (LTE version)
Carrier: Telcel
Country: Mexico
Original Stock OS: 4.1.1
Last working OS: Cyanogenmod 11 Nightly 20141221
Backstory
I'm having a roadtrip that will take a couple of weeks and I got a TMobile SIM to use during my trip through USA and Canada, however my phone was locked to Telcel.
CM brought me some couple of issues with the modem and network selection and as I live right next to the border and cross it every week or so, I was having a hard time switching between carriers and international roaming so I have to upgrade the modem to the latest one (From I747MUMBLL1 to I747MUMUEND3) and for some time I was able to select network operators but still it was locked.
No USSD / Unlock Code Fail
I found on the web there is a way to unlock SG3 for free through the hidden menu, but it didn't work for me but found out USSD codes no longer work in 4.3 so I restored the stock ROM for 4.1.1 (I have no idea how I managed to do this, but got it downgraded) I was able to get to the hidden menu and followed this instructions but I kept using multiple modem versions that aren't for JB the hidden menu didn't gave the option to generate the nv_date file. I think this was due the use of newer modem versions that didn't have the option to initialize the file.
Next attempt was to purchase SIM unlock codes without success, the providers I attempted were TheUnlockingCompany and CellUnlocker, neither of them were able to get me a code to unlock the phone
Also attempted to modify the NV_DATA file but well, it didn't exist in the /efs folder, there were other files but nothing related nv_data.bin. So I really needed to have that file to unlock it but no success in initializing it.
Third-party local unlock dealer
As all the attempts previously failed I needed to have my phone unlocked and was running out of time. So I took it to a local dealer who has more experience unlocking phones. This part I don't have all the info in whatever he did, all I know is that he was unable to work with CM and attempted to unlock it with a brasilian stock firmware, which got it bricked and it was getting more difficult to unlock it.
AFAIK I did have the old bootloader, but his attempts included upgrading the bootloader which includes KNOX and any attempt to restore old rom versions gave me the error SW REV CHECK FAIL : Fused 1 > Binary 0 therefore it was impossible now to get back to stock 4.1.1 and attempt the older modem versions which at this stage found out could have solved the original unlock issue but .... too late.
His attempt with the brasilian stock ROM got the phone bricked and now instead of trying to unlock it I was trying to revive the phone, all my attempts in bypassing KNOX and downgrading the bootloader failed - also attempted to get back to 4.2 and 4.3 through CM 10.1, 10.2 and stock 4.1.1 but bootloader was too recent which prevented me to use those CM versions.
I was able to get it unbricked using CF-AUTO-ROOT - this is a life saver at least to be able to boot the phone, everytime I get a bricked status just by flashing this allowed to boot.
Phone kinda working: NO IMEI NOR ESN
Finally I decided to restore but directly to 4.3 stock for my original provider Telcel. The phone works now... kinda. It boots and gets signal, but NO DATA. I just found out IMEI/ESN information got lost and I didn't have any backup, yes I know I should have but whatever I was doing at least was not touching that information, but this other guy got it messed up.
One interesting thing is that even though there was no IMEI information, but original SIM card works to send/receive calls and SMS. Data doesn't work, but at least calls and SMS does.
Phone included KNOX and was preventing me to use the previously mentioned tool CF-AUTO-ROOT and found this tutorial: http://forums.androidcentral.com/samsung-safe-knox/352922-sprint-galaxy-s3-possible-knox-fix-cf-autoroot.html - this actually works but didn't give me the option to remove KNOX.
THe problem now is that any attempt to use SuperSU through USB debugging was blocked by KNOX but apps opened directly from the phone weren't, with this I installed CWR right away and TitaniumBackup, this last one allowed me to uninstall any KNOX crap. Rebooted the phone and no more issues whatsover in root usage.
As I only have 1 remaining day to have this phone in working conditions and it's christmas today I went on in trying to rebuild my IMEI.
Rebuild IMEI WITHOUT BACKUP
After lot of research and no friends which the same phone that could give their nv_data files, I found out THIS guide (again USSD codes not working so I used EFS Pro to switch USB modes) and basically this is what I did:
Download EFS Professional - Epic tool to work IMEI/ESN info and switch USB mode between MTP+ADB and DEV+MODEM+ADB
Download QPST version 2.7 build 323 NOTE: USE THIS VERSION, NEWER VERSIONS DO NOT INCLUDE RF NV Item Manager
Follow the instructions in the previously mentioned guide, but the USB you can switch it from EFS Pro under Samsung Tools.
It is really important to notice the IMEI number needs to be entered with the HEX checkbox enabled and in reverse.
You probably could do this straight from EFS Professional -> Qualcomm Tools, but this worked for me.
At the end of the guide there was no confirmation or any message the NV information was written successfully, so I just rebooted my phone and success! IMEI is back!
Just to test I tested my T-Mobile SIM and it works! - I'm not sure if this unlocked the phone or whatever the other guy did, but well the phone now accepts any SIM.
No Data / Stuck on EDGE
Now that the phone has the IMEI number and is unlocked I found out DATA still was not working.
I used the tools ESN, MEID and EUIMID Calculator to generate the rest of the missing information which was ESN and MEID. I entered this information in EFS Pro -> Qualcomm NV Tools, checked the boxes and clicked on write making sure the select box next to it was set to Phone.
Rebooted my phone and yes the information was there, however STILL NO DATA.
I came across this life savior - Load this file with NV Item Reader/Writer Some people on the thread say even their already working LTE data achieved better speeds with this.
Rebooted my phone and wallah! DATA and LTE are back! AND UNLOCKED!
What did I learn from all of this? DAMN KNOX and ALWAYS ALWAYS backup /EFS or whatever IMEI/ESN/MEID info is, even if you plan to use custom roms or not, or unlock the phone.
Link to useful tools and sites
CF-AUTO-ROOT - Fix a failed ROM update attempt in ODIN and/or apply permanent root.
ESN, MEID and EUIMID Calculator - Calculate the MEID and ESN based on IMEI
QPST version 2.7 build 323 - Qualcomm Product Support Tool - Modem and service editor
NV Item Reader/Writer - NV Information backup/restore
this life savior - Restore DATA LTE
SamFirmware - Stock roms
I think i love you ...

Non-Standard Error Message on LG Dev Bootloader Unlock Site?

Hello,
I purchased an unbranded, open EU model H815 LG G4 (from Handtec) with the hopes of unlocking its bootloader through the service LG provides on their dev website. I was able to follow the steps in order to procure my device's IMEI number and Device-ID, and despite entering the information correctly, I get rejected with the following error:
Service unavailable. Please contact the site administrator ([email protected])
I have double and triple checked the information entered. The IMEI and Device-ID both clear the checks with an "OK." I have tried using multiple browsers and operating systems. I have tried completing the process on my home network, work network, and even on my cell phone's data network. I have tried a few times each week for two or three weeks now. I always get this same error message.
It is my understanding that this is NOT the usual message that one receives when trying to unlock a carrier-branded H815 or some other country's non-supported H815 variant (such as the Taiwanese model). I'm also pretty sure that other folks who imported their kits via Handtec had no issues unlocking. In Settings, the phone shows as an LG-H815 device and is currently running firmware software version V10b-EUR-XX. It IS currently rooted using Team Codefire's low effort root method, but now with Xposed finally running, I'd like to unlock the bootloader and get my game on, so to speak.
Is there anything I can do to complete the process?
I did send an email to the site admin as instructed by the error message, but I'm not terribly hopeful that they'll be able to help.
Thank you in advance,
I had that message the first time I tried. I tried several times but no go.
I tried again the following day, and it worked fine. May have been an LG site issue??
Thank you for taking the time to reply.
I suppose I'll up the frequency of my retries and hope for the best.
Pretty standard HTTP 503 error code. It's exactly as it says - service unavailable. It likely nothing to do with your inputs.
Yeah, I figured it was nothing those first few days too. But it's been going on for a few weeks now, regardless of browser, OS, and network.
I did hear back from LG, and they advised clearing my cookies and trying again.; and replying back if it continued to fail. Which it did, so I did. Heh.

Categories

Resources