Hi everyone,
I've been searching madly for this to no avail. Unfortuantely I've been having some random reboot issues with my Play and it's looking like it's hardware based. Restarting several times per day, usually when coming out of screen lock. Tried flashing multiple firmwares, different kernels, wiping out everything with CWM. Still no luck.
I'm about to return the handset to Telstra to see about a repair as it's still under warranty. Problem is, Telstra is anal about having their own stock software still on the handset. I didn't think to make a backup of the stock Telstra firmware before flashing a generic UK ROM (I know, stupid).
Could anyone point me in the direction of a stock Telstra ROM? Preferably FTF?
99 views and nobody has anything?
I'm having this exact same problem. Did you find a solution for it? I've tried heaps of things, but I have no idea what the problem is, however it's really frustrating. Thanks
Could you perhaps send it back to Sony (with a locked bootloader and no root)? If it's a hardware issue they shouldn't have a problem I think.
I don't have a problem but I have also been scouring the net for an FTF or whatever for stock Telstra R800a incase I need to return it. I read that there is an update for R800a on Telstra if you use PC Companion, but we would need a build.prop from original Telstra firmware for it to recognize.... could somebody share it?
I know it might only be an OTA update, but it's worth a try to get original build.prop values from stock and extract the update from PC Companion cache. Please, if anybody on stock Telstra firmware not yet updated in PC Companion could share their build.prop file, it could help.
I've found many a guide here to go back to stock recovery, etc. However, none of them that I have found seem to have an option for the Koodo T989D (not to be confused with the Telus T989D, while they may be nearly identical the Koodo one has different markings in the software). I need to get my phone replaced because the Bluetooth is flaky (tried stock ROM, LiquidSmooth, CyanogenMOD, MIUI, etc etc, I'm 99% sure it's a hardware issue at this point), and in order to do that I need to get back to Koodo factory spec.
I'm currently on a stock (rooted) Koodo ROM, so if there's a way to simply uninstall Superuser I'll be good to go. However, I'll also need a stock recovery, but I'm not sure if there are any here so far that have the Koodo brandings or a lack of other carrier brandings.
Could anyone help me out? I'm not necessarily looking for a guide (there are plenty of those here), just the stock recovery and possibly a way to remove Superuser.
EDIT: I hate posting before I fully search. Found exactly what I need here
are you going to end up using the ODIN method or TWRP/CWM method? I'm about to do this on my phone also.
Specs:
Note 2, GT-N7100
Build nr: JRO03C.N7100XXALJ3
Baseband version: N7100DXALJ1
Location: Norway
Hello!
I tried to unlock my note 2 with this method:
http://www.ibtimes.com/how-carrier-unlock-samsung-galaxy-note-2-permanently-tutorial-926231
but I got this error:
menu not exist
press back key
current command is 186
I noticed that this is a known problem, but I haven't found any solutions. I read that reverting from 4.1.2 to 4.1.1 might do the trick, but I don't find any ROM supporting my model.
I tried this ROM (http://androidlegend.com/update-galaxy-note-2-n7100-to-xxalj3-android-4-1-1-official-firmware/), but it doesn't work.. It only shows "Samsung" on startup and nothing happens.
Any help appreciated!
Edit: I hard reset the phone, and it got back to version 4.1.1. I still get the same message as stated above..
Yesterday I tried two stock 4.1.1 roms from Sammobile with no luck. 4.1.1 NEE (nordic countries).
I still get the same message:
MENU NOT EXIST
PRESS BACK KEY
Current Command is 186
Is there any other way to do this?
no one..?
This quote pretty much sums up my situation:
amnesico1 said:
Nobody messed with my phone and I had (have) the same issue.
I've googled alot about this issue, both in english and my native language. I haven't found a single case of success getting that menu active. But I've found alot of people with the exact same issue, and making alot of effort to see that menu.
I've tryed at least 10 different firmwares, including uk o2 firmware that some users reported success with their equipments.
All those firmwares and modem/radio flashes made no difference whatsoever in the service menu. Also tryed french sfr, all android versions available (4.0.4, 4.1.1, 4.1.2), and alot more from uk and Portugal.
Like I've posted before, at a local cell shop I've tryed the code on a device in display and in the service menu, the final menu is there. Not like my cell "menu not exist".
I'm guessing it's not firmware dependant (the existence of the last menu), but equipment dependant. Of course you need 4.1.1 for the procedure to work, but you can also see the last menu with 4.1.2. But for some reason to some of us, this menu simply does not exist.
Hope you guys can sort this out.
Click to expand...
Click to collapse
I never got the chance to donit to my n7100 because it came sim unlocked, but i tried on my n7105 and it worked first time i tried an ee 4.1.1 rom, just wondering guys theres a lot of talk about modem's in the unlock thread, maybe try n change the modem
Sent from my GT-N7105 using Tapatalk 2
I'm a bit of a noob, so apologies if this is in the wrong section. I've had a very difficult time finding threads that focus on those who have (stupidly!) applied the OTA 4.3 jellybean update, and what they can do to network unlock the phone. So here goes:
Samsung Galaxy SIII
SGH-T999
Android Version 4.3
Baseband Version T999UVUEMJC
Stock build. No root.
The closest step-by-step I've come across:
Remove T-Mobile SIM. Replace with ATT SIM. Reboot phone.
*#197328640# which successfully puts me into service mode.
This brings up the following menu:
MAIN MENU
[1]UMTS
[2]CDMA
[3]LTE
[4]SIM
From there its
[1]UMTS
[1] DEBUG SCREEN
[8]PHONE CONTROL
[6]NETWORK UNLOCK
[3]PERSO SHA256 OFF ...
Now, that's as far as I can get. The guide then says to go back to [6] and there should be an option, [4] NV INITIALIZZ.
This option is not there for me. (Note: at this point the PERSO SHA256 status is indeed set to SHA256_ENABLE_FLAG [0]).
Another guide suggested BACKing to the MAIN MENU and selecting option [5] run EFS SYNC() after selecting [3]PERSO SHA256 OFF.
I have done this and the screen reads: SYNC success. please reboot.
I do so, heart aflutter... only to be met with a SIM unlock PIN code entry screen.
Unlock fail.
Other threads have suggested downgrading to 4.1.1 in order for this to work and the necessary options be made available. Most of what I have read has said that attempts to downgrade from OTA 4.3 (with big brother KNOX) will result in a hard brick.
So, if you've made it this far... Has anyone figured out how to SIM unlock this particular phone running OTA 4.3 without rooting/downgrading?
If there is a more suitable thread discussing SIII's that are running 4.3 please direct me there.
Many thanks!
You could try and flash a 4.1.1 Modem. After that, try the above process.
Note - In that process, you are required to be super patient at each step.
Perseus71 said:
You could try and flash a 4.1.1 Modem. After that, try the above process.
Note - In that process, you are required to be super patient at each step.
Click to expand...
Click to collapse
Appreciate the response.
Yes, most of what I have come across has indicated that I would need to get 4.1.1 by hook or by crook in order to network unlock the phone, having upgraded to 4.3.
I have some experience fiddling with such things, but many posts have also indicated that, with the new KNOX package in tow, backing down from 4.3 will hard brick this device. I am hoping that, with access to Service Mode, someone will discover a way to network unlock without root/flashing.
Thanks again!
Are you Rooted ? If so flashing the LJC modem from Doc's thread won't brick your device.
Perseus71 said:
Are you Rooted ? If so flashing the LJC modem from Doc's thread won't brick your device.
Click to expand...
Click to collapse
The phone is not currently rooted, no. Most rooting instructions I've seen are for 4.1.1 or 4.1.2. My guess is I'm going to have to root to unlock...
Could you direct me to instructions for rooting OTA 4.3?
Again, many thanks for taking the time to help.
etrash310 said:
The phone is not currently rooted, no. Most rooting instructions I've seen are for 4.1.1 or 4.1.2. My guess is I'm going to have to root to unlock...
Could you direct me to instructions for rooting OTA 4.3?
Again, many thanks for taking the time to help.
Click to expand...
Click to collapse
Follow these. Effectively Flash Custom Rom using ODIN then flash SuperUser Zip.
Perseus71 said:
Follow these. Effectively Flash Custom Rom using ODIN then flash SuperUser Zip.
Click to expand...
Click to collapse
Awesome. I will try this tonight.
etrash310 said:
Awesome. I will try this tonight.
Click to expand...
Click to collapse
Well, no luck. Followed all the directions I could (provided by some awesome contributors including Doc) including:
1)Rooting using the aforementioned method and installing 4.3 with SU and no KNOX. Then just flashing stock modem 4.1.1 UVDLJC, in order to reveal the [4] NV INITIALIZZ option that is not present in Servicemode on jellybean 4.3 firmware.
--- This resulted in very slowed down system with no WiFi capability and no startup or shutdown sounds. Logging into Servicemode just resulted in a blank screen that said Servicemode.
--- Ultimately had to emergency restore firmware via KIES. (Thanks to reading a post by Doc on another thread). This got me up and running again.
2) Rooting using aforementioned method. And searching for stock 4.1.1 firmware in order to downgrade...
--- This has proven to be impossible. I can not find stock 4.1.1 anywhere. All links that have turned up have either been dead hotfile.com links or corrupted .zip files.
--- Additionally, I have been informed that once you upgrade to 4.3 OTA it is IMPOSSIBLE to flash an earlier firmware using ODIN. (Is is possible using CWM perhaps?)
In the end, it appears that the jellybean 4.3 OTA update currently has the community stumped as to how to unlock the SGH-T999 for use on another network with your only option to either convince T-Mobile to give you an unlock code or ordering one online. (And I've read of too many folks getting bogus codes ordering online...)
Still having fun trying, and its very cool to see all the hard work and info that folks like Doc are compiling on here. Maybe somebody is on the way to cracking this nut!!!
etrash310 said:
In the end, it appears that the jellybean 4.3 OTA update currently has the community stumped as to how to unlock the SGH-T999 for use on another network with your only option to either convince T-Mobile to give you an unlock code or ordering one online. (And I've read of too many folks getting bogus codes ordering online...)
Click to expand...
Click to collapse
So after all that, what is your current Rom and Firmware ? Can you try Root66 of 4.2 Rom ? Doc has Re-Hosted with mirrors.
I followed cLogic's guide that you linked to above and am running 4.3 rooted w/o Knox garbage.
Ended up getting phone network unlocked at a local hole in the wall phone shoppe. Figured it was worth a couple extra bucks to have it unlocked face to face in case code didn't work rather than fish out a reputable online source on my own.
Will be curious to compare its power usage to stock 4.3. Phone is working well, although it seems I will have to play with the APN settings as I am unable to send MMS messages... hmmm. Any advice off the top of your head?
I'd given root66 a try and also gave Doc's reposts another shot, but no dice.
So the sum of my endeavors are as follows:
1) If you want to network unlock your galaxy s3 on your own, DO NOT upgrade to jellybean 4.3 OTA until you do. It does not seem anyone has figured a way to ala ServiceMode in 4.1.1 yet.
2) If you have upgraded to 4.3 OTA you can use cLogic's guide linked to above to root your phone sans Knox.
3) If you have already upgraded to 4.3 OTA and want your phone network unlocked, you will have to pay to have it factory unlocked.
4) XDA is the bomb.
UPDATE:
Looks like the MMS messages I was trying to send finally went through... it just took an inordinately long time for them to do so.. not sure why yet.
Of dubious help to the OP, who had his phone commercially unlocked, but for others reading this thread or the OP's curiosity.. the 4.3 update has caused all kinds of grief. Amongst various bugs and battery drain issues, 4.3 has changed dialer codes or shuffled menus around. I can confirm the same results as the OP up to the point where he found that the initialize NV menu missing.
To progress further, I found that I needed:
An active SIM from a different carrier, with said SIM needing to be the phone throughout. This is in contrast to the previous method that worked without a SIM in the phone during the unlock procedure. I successfully unlocked a Note 2 with 4.3 using the steps in this techbeasts.com post.
And was successful with a 4.3 S4 using a slight variation (no NV initialize menu!.. back.. key input.. 1.. back). Both phones were M (Canadian) models.
Reading between the lines of various reports in addition to first hand experience implies that there may be several different carrier specific dodges being employed here. Playing musical chairs with the missing menu items that now have different dialer codes, are now found on hidden sub menus (key input = 1) or in back up files.
The commercial unlock guys are using proprietary tools such as Samsung tool v 16.8. Which usually seem to be database based factory unlocks fetched (or calculated?) from their servers.
.
since this worked on a note2, would it work on a sgs3 t999 that is already on 4.3?
fffft said:
Of dubious help to the OP, who had his phone commercially unlocked, but for others reading this thread or the OP's curiosity.. the 4.3 update has caused all kinds of grief. Amongst various bugs and battery drain issues, 4.3 has changed dialer codes or shuffled menus around. I can confirm the same results as the OP up to the point where he found that the initialize NV menu missing.
To progress further, I found that I needed:
An active SIM from a different carrier, with said SIM needing to be the phone throughout. This is in contrast to the previous method that worked without a SIM in the phone during the unlock procedure. I successfully unlocked a Note 2 with 4.3 using the steps in this techbeasts.com post.
And was successful with a 4.3 S4 using a slight variation (no NV initialize menu!.. back.. key input.. 1.. back). Both phones were M (Canadian) models.
Reading between the lines of various reports in addition to first hand experience implies that there may be several different carrier specific dodges being employed here. Playing musical chairs with the missing menu items that now have different dialer codes, are now found on hidden sub menus (key input = 1) or in back up files.
The commercial unlock guys are using proprietary tools such as Samsung tool v 16.8. Which usually seem to be database based factory unlocks fetched (or calculated?) from their servers.
.
Click to expand...
Click to collapse
etrash310 said:
Well, no luck. Followed all the directions I could (provided by some awesome contributors including Doc) including:
1)Rooting using the aforementioned method and installing 4.3 with SU and no KNOX. Then just flashing stock modem 4.1.1 UVDLJC, in order to reveal the [4] NV INITIALIZZ option that is not present in Servicemode on jellybean 4.3 firmware.
--- This resulted in very slowed down system with no WiFi capability and no startup or shutdown sounds. Logging into Servicemode just resulted in a blank screen that said Servicemode.
--- Ultimately had to emergency restore firmware via KIES. (Thanks to reading a post by Doc on another thread). This got me up and running again.
2) Rooting using aforementioned method. And searching for stock 4.1.1 firmware in order to downgrade...
--- This has proven to be impossible. I can not find stock 4.1.1 anywhere. All links that have turned up have either been dead hotfile.com links or corrupted .zip files.
--- Additionally, I have been informed that once you upgrade to 4.3 OTA it is IMPOSSIBLE to flash an earlier firmware using ODIN. (Is is possible using CWM perhaps?)
In the end, it appears that the jellybean 4.3 OTA update currently has the community stumped as to how to unlock the SGH-T999 for use on another network with your only option to either convince T-Mobile to give you an unlock code or ordering one online. (And I've read of too many folks getting bogus codes ordering online...)
Still having fun trying, and its very cool to see all the hard work and info that folks like Doc are compiling on here. Maybe somebody is on the way to cracking this nut!!!
Click to expand...
Click to collapse
Well try this link .... http://forum.xda-developers.com/showthread.php?t=1949687
well i dont know if it will work for me because my t999 is running cyanogenmod 12.1
The phone must be running stock 4.1.1 in order to sim unlock using the free method. Once the phone is on a 4.3 or newer bootloader, sim unlocking must be done using a code specific to the phone's imei. In order to enter the unlock code, the phone must be running a stock ROM or possibly a custom ROM based on a tw kernel.
audit13 said:
The phone must be running stock 4.1.1 in order to sim unlock using the free method. Once the phone is on a 4.3 or newer bootloader, sim unlocking must be done using a code specific to the phone's imei. In order to enter the unlock code, the phone must be running a stock ROM or possibly a custom ROM based on a tw kernel.
Click to expand...
Click to collapse
So, I previously rooted my s3. It is locked to tmobile. Then I unrooted and tried to unlock it but of course after 4.3 update (LUVUBOH1 Big mistake I see! I tried to flash a different 4.3 stock baseband just to make sure I flashed stock rom but odin failed. I kept trying and even updated odin, but no dice. Any ideas??
Do you have an unlock code? If not, you'll have to buy an unlock code and enter the code while running a stock ROM.
audit13 said:
Do you have an unlock code? If not, you'll have to buy an unlock code and enter the code while running a stock ROM.
Click to expand...
Click to collapse
Yes, I did purchase an unlock code. I'm going to try a different sim. I THINK I'm running stock rom 4.3 LUVUBOH1.
When you insert a non T-Mobile sim, you're not prompted to enter a network unlock code?
I haven't use this site in many years so I apologize if this isn't the correct spot. I tried searching all over for an answer..
I got a brand new S7 off of eBay. The firmware that came on it was somehow messed up, even though it was in a factory sealed box. There were many odd things missing, including the option to OTA. I contacted Samsung and they remotely accessed the phone and confirmed that my software was jacked. Since the phone was new but old, it was out of warranty. Oddly, enough the guy suggested I flash new firmware myself, but would not provide a link. AT&T then told me that they can't flash software and don't even have it... it can only be done by FOTA, lol.
Google led me to a factory firmware. I flashed it via Odin and all was good. I then did the numerous OTA updates until I have the newest 8.0 and security patch.
Now my stupidity comes in... My Bluetooth and Wifi did not work well. My Wifi range sucked and my Bluetooth wouldn't see certain devices. Like an idiot, I figured a CP flash would help it. I flashed an older CP and bricked the phone. I scoured the internet and could not find the newest firmware.
I haven't flashed firmware in years and I should have read up more before doing so. My phone currently works but I hate the version I have as it's oddly different than the 8.0 firmware I got via FOTA. It was the only one I could find online that had the same baseband version that I currently had (G891AUCU4CRH1).
From my understanding, this newest firmware can't be downgraded so I'm stuck trying to find the actual AT&T FOTA update. Is this correct?
If anyone can let me know where to find it, I would greatly appreciate it.
Thanks
Sam
Edit.. dumb me just needed to flash the CSC as well.
Found my own answer. Please delete this thread.
I'll upload the CRH1 files and post a link for you guys. I just flashed and can confirm it works for me.
Hi , can you post link for the update please.
asavov said:
Hi , can you post link for the update please.
Click to expand...
Click to collapse
https://cloud.mail.ru/public/BGy7/g...o/G891AUCU4CRH1_G891AATT4CRH1_ATT_USA_8.0.zip