Develop Bugs

[Q] Can't Flash Modem

My Phone
Model #: SPH-D710
Android Version: 2.3.4
Baseband Version: UNKNOWN
Kernel Version: 2.6.35.7-SPH-D710.EG30-CL435734
Build #: Tnz BLEND v1.4
Hardware Version: UNKNOWN
I bought the phone second hand with the Tnz rom installed and it worked fine. I tried to flash CM9 with ODIN and it failed. I restored it and now I have no signal. Now I can't get ODIN to recognize the phone on either my desktop or laptop with any of my 3 data cables and when I try to flash a modem in CWM v5.0.2.7 (Using the .zip from the Wiki) it gets all the way to the end and then I get this message:
Code:
script aborted (no error messege) E:Error in /emmc/update-modem-EG30-FULL-CWM.zip
(Status 7)
Installayion aborted
I checked the zip with winrar both on on my computer and when it's on the phone and it checks out. At this point I'm out of ideas so any help would be greatly appreciated

Why not start over.
Download the EL26+CWM kenel [http://kernelrepo.chris41g.org/defa...Chris41g\ACS\ZIP&filename=EL26_StockACS5.zip], the EL29 modem [http://www.buildarom.com/E4GT/Modems/E4GT_Modem_EL29.zip] and something like Calkulin's stock rooted EL29 [http://forum.xda-developers.com/showthread.php?t=1332837] Copy them to the SD card (on you computer) then put the SD card into the device, Flash the EL26+CWM. Use that CWM (EL26 one) to factory reset.
Then install the modem. Then the ROM. and see what happens.
Hope you didn't use ROM manager by the way - that's a BIG no no.

You might be in trouble.
Can you boot into download mode? If you can use EL29 oneclick to get back to stock.

Thank you both for your quick replies.
I was able to flash the kernel but when I tried to flash the modem I got the same error message. The 1-click recovery won't recognize my phone in download mode, just like ODIN.
I think I'm in trouble :crying:

rodeodude said:
Thank you both for your quick replies.
I was able to flash the kernel but when I tried to flash the modem I got the same error message. The 1-click recovery won't recognize my phone in download mode, just like ODIN.
I think I'm in trouble :crying:
Click to expand...
Click to collapse
Yeah u may have bricked....cm9 isn't an Odin type flash. Everytime someone says their PC won't recognize the phone they wind up bricked. Read through the how not to brick your phone thread in general and hopefully someone found a workaround.
Can you get into a cwm recovery even with volume up+power? Not the stock one, but a custom recovery without the android in the background.
Sent from my SPH-D710 using XDA

dante32278 said:
Yeah u may have bricked....cm9 isn't an Odin type flash. Everytime someone says their PC won't recognize the phone they wind up bricked. Read through the how not to brick your phone thread in general and hopefully someone found a workaround.
Can you get into a cwm recovery even with volume up+power? Not the stock one, but a custom recovery without the android in the background.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Well shoot, guess its time to start digging....
Yes I can boot into CWM, that's what I was using to try and flash things.

rodeodude said:
Well shoot, guess its time to start digging....
Yes I can boot into CWM, that's what I was using to try and flash things.
Click to expand...
Click to collapse
If you made a nand, hope u did, try and flash that. If not then try a safe gb rom from your sd card. Can't be worse than what u have already.
Sent from my SPH-D710 using XDA

Similar Problem
rodeodude said:
My Phone
Model #: SPH-D710
Android Version: 2.3.4
Baseband Version: UNKNOWN
Kernel Version: 2.6.35.7-SPH-D710.EG30-CL435734
Build #: Tnz BLEND v1.4
Hardware Version: UNKNOWN
I bought the phone second hand with the Tnz rom installed and it worked fine. I tried to flash CM9 with ODIN and it failed. I restored it and now I have no signal. Now I can't get ODIN to recognize the phone on either my desktop or laptop with any of my 3 data cables and when I try to flash a modem in CWM v5.0.2.7 (Using the .zip from the Wiki) it gets all the way to the end and then I get this message:
Code:
script aborted (no error messege) E:Error in /emmc/update-modem-EG30-FULL-CWM.zip
(Status 7)
Installayion aborted
I checked the zip with winrar both on on my computer and when it's on the phone and it checks out. At this point I'm out of ideas so any help would be greatly appreciated
Click to expand...
Click to collapse
I also have a similar problem. I have no signal and cannot get out of airplane mode.
Android version: 2.3.4
Baseband Version: Unknown
Kernel Version: 2.6.35.7-SPH-D710.EG30-CL435734
Build Number: GINGERBREAD.EG30
Hardware Version: Unknown
I also flashed A Custom rom.
I have had some kind of luck playing around with the nv_data files using this http://forum.xda-developers.com/showthread.php?t=1264021
I browsed my EFS directory and created blank nv_data files with root explorer.
After the reboot I had empty signal bars come up at the top and my Baseband fields filed out with the correct version and with my IMEI back.
This however only lasted about a minute before I got a crossed out circle for the signal and I back to Unknown values for the versions.
I had my phone connected to the PC the whole time and I also noticed my PC was repeatedly making the sound that it recognized a usb device (samsung mobile modem diagnostic serial port, I believe) until the phone lost the bars and went back to Unknown values.
Now my pc won't even detect the samsung diagnostic modem at all.
Also when I try to go into Setting -> About phone -> Status, I get a force close of com.android.phone

coronelac said:
I also have a similar problem. I have no signal and cannot get out of airplane mode.
Android version: 2.3.4
Baseband Version: Unknown
Kernel Version: 2.6.35.7-SPH-D710.EG30-CL435734
Build Number: GINGERBREAD.EG30
Hardware Version: Unknown
I also flashed A Custom rom.
I have had some kind of luck playing around with the nv_data files using this http://forum.xda-developers.com/showthread.php?t=1264021
I browsed my EFS directory and created blank nv_data files with root explorer.
After the reboot I had empty signal bars come up at the top and my Baseband fields filed out with the correct version and with my IMEI back.
This however only lasted about a minute before I got a crossed out circle for the signal and I back to Unknown values for the versions.
I had my phone connected to the PC the whole time and I also noticed my PC was repeatedly making the sound that it recognized a usb device (samsung mobile modem diagnostic serial port, I believe) until the phone lost the bars and went back to Unknown values.
Now my pc won't even detect the samsung diagnostic modem at all.
Also when I try to go into Setting -> About phone -> Status, I get a force close of com.android.phone
Click to expand...
Click to collapse
I have the same exact problem. Did you ever find a fix for this?

Same Here
ClassickWORLD said:
I have the same exact problem. Did you ever find a fix for this?
Click to expand...
Click to collapse
Same issue here
Tried odin back to stock EL29
tried flashing modem separately via Odin / phone slot
tried factory reset data & cache wipes then format system/data
So far no luck
WiFi works -- 4g shows signal/searching
Signal area round -- no baseband/hardware info
Can access download mode, but not QPST/diag modem mode
Any ideas appreciated!

rodeodude said:
My Phone
Model #: SPH-D710
Android Version: 2.3.4
Baseband Version: UNKNOWN
Kernel Version: 2.6.35.7-SPH-D710.EG30-CL435734
Build #: Tnz BLEND v1.4
Hardware Version: UNKNOWN
I bought the phone second hand with the Tnz rom installed and it worked fine. I tried to flash CM9 with ODIN and it failed. I restored it and now I have no signal. Now I can't get ODIN to recognize the phone on either my desktop or laptop with any of my 3 data cables and when I try to flash a modem in CWM v5.0.2.7 (Using the .zip from the Wiki) it gets all the way to the end and then I get this message:
Code:
script aborted (no error messege) E:Error in /emmc/update-modem-EG30-FULL-CWM.zip
(Status 7)
Installayion aborted
I checked the zip with winrar both on on my computer and when it's on the phone and it checks out. At this point I'm out of ideas so any help would be greatly appreciated
Click to expand...
Click to collapse
what cm9 zip did you flash! what is the file name? did you get it from cyanogenmod.com?

I fixed my issue via tips from other threads
I odin flashed stock gingerbread
After boot, I was prompted for sprint update to FF18, which I let run while I was searching out FF18 modem.
Then Odin 1.85 flashed ff18 modem in phone slot with EFS clear & reboot checked
After reboot, signal bars were back & phone initiated activation
hope this helps someone else
ClassickWORLD said:
I have the same exact problem. Did you ever find a fix for this?
Click to expand...
Click to collapse

Magickly said:
Same issue here
Tried odin back to stock EL29
tried flashing modem separately via Odin / phone slot
tried factory reset data & cache wipes then format system/data
So far no luck
WiFi works -- 4g shows signal/searching
Signal area round -- no baseband/hardware info
Can access download mode, but not QPST/diag modem mode
Any ideas appreciated!
Click to expand...
Click to collapse
I just had this same issue -- tried to flash a modem and booted back up and no service, unknown baseband version, etc etc. I thought I had bricked it, but I managed to nurse it back to health. Here's what I did:
Went to the recover from bad flash topic in Dev forum and flashed that (though it doesn't flash a modem)
Then flashed FH13 modem
Then flashed Blue Kuban ROM (which is based on FH13)
Then booted into that and I have signal and baseband is recognized as FH13

Baseband Hardware "Unknown" Fix
Just had this same problem, 30k ft. overview of issue; I was messing around with flashing NV-items in DFS and reset RF and must have loaded the wrong .ncf file or something, not sure, and ended up with the same problem. Baseband and hardware versions are "unknown". Tried your fix with fix bad flash topic in DEV and FH13 modem with blue kuban with no luck. Still unknown versions. When I review the cutany app with serial and read the model it is reading out: GT s5 670_EUR and this is the SPH-D7710 Galaxy S2 Epic Touch 4G. SO......umm...
I have tried:
- flashing a few other roms and modems. no luck
- tired editing the NV items. but can't get back into Diag mode. (may try above post.)
- reset the ##7886#
- wiped /efs and restored it.
- went to stock EK02 unrooted
- rooted and unrooted
-
Thoughts:
- maybe get the right firmware radio/ hardware and manually flash them (where to get them or what is it that i need?.)?
- edit the build.prop to get a different build that fits the model?
- some how trying to fix com.android.phone? not sure how it works?
- some how, wipe every thing on root? and start over? not sure this can happen?
- read-only error when trying to edit root dir, ? have adb
So in summary I need some direction asap!
GPadraic said:
I just had this same issue -- tried to flash a modem and booted back up and no service, unknown baseband version, etc etc. I thought I had bricked it, but I managed to nurse it back to health. Here's what I did:
Went to the recover from bad flash topic in Dev forum and flashed that (though it doesn't flash a modem)
Then flashed FH13 modem
Then flashed Blue Kuban ROM (which is based on FH13)
Then booted into that and I have signal and baseband is recognized as FH13
Click to expand...
Click to collapse

<<Thoughts:
- maybe get the right firmware radio/ hardware and manually flash them (where to get them or what is it that i need?.)?
- edit the build.prop to get a different build that fits the model?
- some how trying to fix com.android.phone? not sure how it works?
- some how, wipe every thing on root? and start over? not sure this can happen?
- read-only error when trying to edit root dir, ? have adb
So in summary I need some direction asap!>>
I had a similar issue and finally fixed by first flashing the oldest working nandroid backup I had, then flashing stock sprint gingerbread (unrooted - as if I would be returning to a sprint store) using one click (available here on xda) which restores system to out of box state.
I had to switch out to different usb cable AND a different usb port to get comm port to be recognized. I also restored a QPST backup.
After reboot, baseband & IMEI were restored. Sprint prompted to install system update, which I believe corrected the other remaining glitches.
I then flashed FF18 and all is well now, except...
I did discover day or so later that usb charging port is going --- I suspect that may have contributed to the freaky disappearing baseband.
Perhaps a bad connection (yikes!) during one of my marathon flashing sessions.
Now having port replaced.

Volcom1600 said:
Just had this same problem, 30k ft. overview of issue; was I was messing around with flashing NV-items in DFS and reset RF and must have loaded the wrong .ncf file or something, not sure, and ended up with the same problem. Baseband and hardware versions are "unknown". Tried your fix with fix bad flash topic in DEV and FH13 modem with blue kuban with no luck. Still unknown versions. When I review the cutany app with serial and read the model it is reading out: GT s5 670_EUR and this is the SPH-D7710 Galaxy S2 Epic Touch 4G. SO......umm...
I have tried:
- flashing a few other roms and modems. no luck
- tired editing the NV items. but can't get back into Diag mode. (may try above post.)
- reset the ##7886#
- wiped /efs and restored it.
- went to stock EK02 unrooted
- rooted and unrooted
-
Thoughts:
- maybe get the right firmware radio/ hardware and manually flash them (where to get them or what is it that i need?.)?
- edit the build.prop to get a different build that fits the model?
- some how trying to fix com.android.phone? not sure how it works?
- some how, wipe every thing on root? and start over? not sure this can happen?
- read-only error when trying to edit root dir, ? have adb
So in summary I need some direction asap!
Click to expand...
Click to collapse
Sounds like you are heading in the right direction(s) for a possible fix.
You can't get into diag on some ROMs because you can't access them via the dialer and/or they are not there and/or supported.
What I'd do first is use one of sfhub's One-clicks and do a full reset. (I'd probably choose FF18 http://forum.xda-developers.com/showthread.php?t=1721229).
One other thing I'd mention is to check the md5sum on EVERY download. Bad downloads are the cause of SO many issues.
Then, once it's back up 'Activate this phone' then try a update PRL and Update Profile.
Again this is what I would do. You could spend days trying to figure it out and not get the solution. But if you'd like to use your phone why not bite the bullet; do a full wipe and make sure your phone works as, well a phone.
Then add a safe CWM kernel (Agat 5.4 or rujelus22 1.8) via sfhub's Autoroot or Mobile Odin.
From there you can then mess with other ROMs, modems and kernels. Check out rwilco's repository for modems and kernels. He's done a great job of organizing and putting together CWM flashable zips, tars and One-Clicks
Good Luck!

Magickly said:
<<Thoughts:
- maybe get the right firmware radio/ hardware and manually flash them (where to get them or what is it that i need?.)?
- edit the build.prop to get a different build that fits the model?
- some how trying to fix com.android.phone? not sure how it works?
- some how, wipe every thing on root? and start over? not sure this can happen?
- read-only error when trying to edit root dir, ? have adb
So in summary I need some direction asap!>>
I had a similar issue and finally fixed by first flashing the oldest working nandroid backup I had, then flashing stock sprint gingerbread (unrooted - as if I would be returning to a sprint store) using one click (available here on xda) which restores system to out of box state.
I had to switch out to different usb cable AND a different usb port to get comm port to be recognized. I also restored a QPST backup.
After reboot, baseband & IMEI were restored. Sprint prompted to install system update, which I believe corrected the other remaining glitches.
I then flashed FF18 and all is well now, except...
I did discover day or so later that usb charging port is going --- I suspect that may have contributed to the freaky disappearing baseband.
Perhaps a bad connection (yikes!) during one of my marathon flashing sessions.
Now having port replaced.
Click to expand...
Click to collapse
Lol "during one of my marathon flashing sessions"!! started this journey at 4pm PST today.
Thus far>
- Back to stock unrooted applied all updates ota (wifi) at FF18 4.0.4b (IMM761.FF18)
- reviewed my anycut serial number still says 1. model GT-s5670_EUR with blank imei and s/n (this may have been from the bad NV flash in DFS?
- will try QPST restore my.qcn file,
HOW did you get into Diag mode? tried ##8778# with CP and ALL but QSPT still can not find my usb connection? so I can restore the qcn?

OH wow, was this flashed with an international version!? Looks like it.
You may need a jtag repair or replacement.

Did you try flashing with regular Odin - not the one click downloader - and checking the EFS clear option?
There is another one that someone mentioned but I can't recall what it was now that will force the NVDATA back to factory setting. I'll see if I can find it.

Thanks, been working on this one for almost 18hrs. Have a timer going. Might be a new record...I'm sure of it that the root of all evil here was DFS and the lack of programing literature, basically trial and error, just in this case more error then trial....
I spoke with a tech in the Sprint back repair center reaching out into the dark here for the lowest guy on the ladder, not much help, but just gave it a shot in the dark with all honesty, and technically they are not skilled to handle this kind of thing, they have manual programing ability with some internal portal software, but not Samsung hardware programing or chip Qualcomm tools. (not sure that is the issue here) basically said exchange it for a referb. Or find hardware firmware or something..Wasn't sure what to say....
So about to toss in a towel here, but, yes tried using different odin's and clearing efs. Also tried again to delete /esf and place /efs.bak with edited nv_data.bin etc.. from other topics. I have a back up of my nvf file from DFS demo. I just can't get to the port to flash it on CP mode, as it will not connect. I don't know were the files go within root to replace them manually?? Some how have a hunch that its a simple copy and paste or delete edit some where.
The wrong model no. is what is driving me off the wall, maybe though the phone usb with some other software (NVFlash? ANYONE know if that needs Daig mode of just a usb to root access? Also maybe ADB shell cp those specific modems and flash files for that EURO model?.humm..
(Thinking out-loud here, but I think it is possible to in theory to flash other phone model and have them working on different networks if the hardware provides it. Would be cool idea and ultimate hack to get the Mifi and clone it to E4gT or find a way to tape it to the back of your epic for $34.99 all you need is data to use SIP Droid and G voice for all voice and text and the SIP following you as long as your either on good wifi or a 3g data connection, not sure about 1x and SIP but if you lived in a good coverage area this would work great no more $100 bills, otherwise Boost Mobile for $15 a month for data Pay as you go using SIP..Cool Technology these days pretty soon there will be no more cell phone channels it will all be data..
That's about it for me, maybe one more hour of reading posts and googling for any other leads to fix this mess, other wise hale marry and turnover on the 20 yard line for this one man team.
Thanks to all that replied.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
garwynn said:
Did you try flashing with regular Odin - not the one click downloader - and checking the EFS clear option?
There is another one that someone mentioned but I can't recall what it was now that will force the NVDATA back to factory setting. I'll see if I can find it.
Click to expand...
Click to collapse

[INFO] [FAQ] Galaxy S3 w/ LTE - SGH-T999L & SGH-T999N

T-Mobile Galaxy SIII
LTE Edition
SGH-T999L
Now Covering the New Metro PCS SIII
SGH-T999N
Current Builds:
T999L = UVAMB7
T999N = UVAME4
Development Thread
{Depreciated - For Reference Only}
[Stock][ROM]Galaxy S3-LTE (d2ltetmo)
Thread Purpose
To help new T999L and T999N owners get started on discovering the full potential of their new device.
To assist members with troubleshooting and provide general help and information for the device.
To answer the most frequently asked questions about the T999N, T999L and LTE.
Note: While this will be primarily focused on the T999L, nearly ALL information will be directly applicable to the T999N as the devices are identical. Only the firmware is different. I will try to state specifically anywhere there is a difference. But if it is not stated as such, it is fairly safe to assume the information in question is relevant, as is, for both devices.
There will also certainly be information here that can be helpful to everyone. I invite comments and suggestions from all of you!
I am aware that there is a good deal of confusion out there about these latest versions of the S3. I hope to help alleviate that confusion by consolidating available information here. My goal is to provide you with everything you need in order to get what you want out of your device (well almost everything!! )
Be aware that I plan to organize this over the first several posts, so please read everything before posting questions and/or new threads.
What this thread IS NOT
A place to continue the debate about the T999 being LTE capable.
A place to complain about T-Mobile telling you that the T999 will get LTE.
A place to find support for the OLD MetroPCS model, SCH-R530. (I think thats the correct model)
SPECS
Processor
Qualcomm MSM8960
1.5GHz Dual-Core
1MB Level 2 Cache
ARMv7
Memory
2GB RAM
LPDDR2
Storage
16GB Total
xxxx User Accessible
Up to 64GB SD Card Expansion
GPU
Qualcomm Adreno 225
4.8" Super AMOLED Display (Active Matrix, Organic LED)
720x1280 Display Resolution
305.8 Pixels /inch
1920x1080 Video Out Resolution (via MHL)
Audio
Wolfson WM1811
Stereo Output
Camera (Rear)
8MP
1x Optical Zoom
16x Digital Zoom
JPG Format
Camera (Front)
1.92MP
1280x720
Picture Format - JPG
Video Format - 3GP
Camcorder
1920x1080 @ 30fps
Formats: 3GP, 3G2, MPEG4
USB
Micro USB Connector
USB 3.0
USB OTG (On The Go) 1.3 Compliant
Bluetooth
BT 4.0
BT Stereo A2DP/AVCRP
Broadcom BCM4334
Wi-Fi
a/b/g/n
2.4GHz / 5.0GHz
Broadcom BCM4334
Cellular Networks
Band 1 - UMTS 2100
Band 2 - UMTS 1900
Band 4 - UMTS 1700/2100 & LTE 1700/2100
Band 5 - UMTS 850 ; GSM 850 / 900 / 1800 / 1900
Band 17 - LTE 700
Data Links
GPRS - Class 12
EDGE - Class 12
UMTS
HSPA+21
HSPA+42 - HSDPA Cat. 24 (42 MB/s) - HSUPA Cat. 6 (5.76 MB/s)
LTE - Cat. 3
LTE
LTE 1700/2100 - Channels available with 5MHz, 10MHz, 15MHz and 20MHz bandwidth
LTE 700 - Channels available with 5MHz and 10MHz bandwidth
Other Features
Digital Compass
Barometer
Active Noise Cancellation
DLNA
NFC
Business Certified Samsung SAFE v2.5
CMAS
HD Voice
T-Mobile LTE is Currently Deployed in the Following Locations
Alabama
Birmingham
Decatur
Huntsville
Mobile
Montgomery
Tuscaloosa
Arizona
Phoenix
Tucson
Arkansas
Little Rock
California
Bakersfield
Fresno
Los Angeles
Modesto
Napa
Oakland
Oxnard
Riverside
Sacramento
Salinas
San Diego
San Francisco
San Jose
San Rafael
Santa Ana
Santa Barbara
Santa Cruz-Watsonville
Santa Rosa
Stockton
Vallejo-Fairfield
Colorado
Boulder
Denver
Connecticut
Bridgeport
New Haven
District of Columbia
Washington
Florida
Jacksonville
Lakeland-Winter Haven
Miami
Orlando
Sarasota
Tallahassee
Tampa
West Palm Beach
Georgia
Atlanta
Gainesville
Savannah
Hawaii
Honolulu
Illinois
Chicago
Indiana
Indianapolis
Lafayette
Kansas
Lawrence
Wichita
Kentucky
Lexington
Louisiana
New Orleans
Maryland
Baltimore
Massachusetts
Boston
Cambridge
Michigan
Ann Arbor
Detroit
Warren
Minnesota
Minneapolis
Missouri
Kansas City
Nevada
Las Vegas
Reno-Sparks
New Jersey
Atlantic City
Newark
New Mexico
Albuquerque
New York
Albany
Binghamton
Buffalo
Nassau
New York
Rochester
Syracuse
North Carolina
Charlotte
Durham
Greensboro-High Point
Raleigh
Winston-Salem
Ohio
Akron
Cleveland
Columbus
Dayton
Oklahoma
Bartlesville
Oklahoma City
Tulsa
Oregon
Portland
Salem
Pennsylvania
Erie
Philadelphia
Pittsburgh
Rhode Island
Providence
South Carolina
Charleston
Spartanburg
Greenville
Tennessee
Memphis
Nashville
Texas
Austin
College Station-Bryan
Dallas
El Paso
Fort Worth
Houston
San Antonio
Utah
Ogden
Provo-Orem
Salt Lake City
Virginia
Richmond
Virginia Beach
Washington
Bellingham
Kennewick
Mount Vernon
Seattle-Bellevue
Spokane
Puerto Rico
Mayagüez
Ponce
San Juan
FAQ
Here is a somewhat rough draft of some of our most frequently asked questions. I will add, edit, revamp, make better as we go. If you notice a popular question that I left out, let me know so I can add it! I just wanted to get them out asap as I felt I have waited long enough!
Why Can't I Get LTE?
That depends:
Are you certain you have an LTE capable device? Namely the SGH-T999L?
Are you sure that LTE is available in your area?
Did you pay your bill on time?
It is also highly possible that there are currently network/tower problems in your area. Call T-Mobile Support and ask.
Check your IMEI number. If it is zero, PM me!
My ROM doesnt show LTE in the statusbar, only 4G.
If you have flashed a custom rom, you may be getting LTE only it does not know how to display this in the status bar.
To tell what your connection is for sure, start a download (your next rom is a good one), then go to Settings > About Device > Status > Network Type
Why does my phone say it is a T999?
Because you flashed a rom that was based on or intended for the original T999 model. This is perfectly normal.
If you really want to change it, go to /system/build.prop and edit all lines that say SGH-T999, to your model or whatever you like.
(WARNING!!!) If you change this to a different model than the T999 or T999L, some apps may think they are on that different model device. This can cause a brick if you try to flash firmware with Mobile Odin. Other apps may not function as intended. Use Caution!
Can I flash ROMs from the T999?
In short, YES
BUT....some ROM's will not flash without a little intervention, so to speak. If you get a Status 7 error and the ROM will not flash, this is what you do:
Unzip the Rom.
In the Meta-Inf folder, delete the signatures (CERT.RSA, CERT.SF, MANIFEST.MF)
Browse to META-INF\com\google\android\ and open the updater-script in Notepad++
At the top of the script, there will be one or several lines beginning with "Assert". Delete these Lines. Save the updater-script.
Re-Zip the Rom and try again to flash.
Can I update my bootloader so I can Flash CM?
NO. AND DO NOT ATTEMPT TO DO SO!!! YOU WILL BRICK YOUR DEVICE!!!!
See the question above about removing the "Assert" lines from the Rom's updater-script to make the rom flashable.
Can I Network/Carrier unlock via the free method posted in General?
Unfortunately, this is not possible on 4.1.2 as Samsung patched against it in this build. Because there is no earlier firmware for the device, you cannot downgrade like people can with the original T999.
Your only options are to try to get the unlock code from T-Mobile, or pay for the service from an online retailer. You can find some on ebay, or just by a google search.
Can I flash another radio?
YES.
The T999 and T999V modems will flash, but you will have no connectivity. So do not flash these. There is no point.
However, as of right now you can only use two modems. UVAMB7 from the T999L, and UVAME4 from the T999N are interchangeable. Meaning you can use the T999N modem on the T999L, and vice versa. Please read my Modem/Baseband thread for downloads and more information on modems. (Link is in my sig)
Can I flash any of the firmware that is for the T999 or T999V?
NO! YOU WILL HARD-BRICK YOUR DEVICE!!!!
ONLY flash T999L firmware to a T999L and T999N firmware to a T999N!!!!
If it does not match your model EXACTLY, it will almost certainly brick your device!!!
Can I flash the T999L firmware to my T999N, or vice versa?
NO! This is one of the areas where the two are NOT compatible!
ONLY flash T999L firmware to a T999L and T999N firmware to a T999N!!!!
If it does not match your model EXACTLY, it will almost certainly brick your device!!!
What is safe to flash to the T999L?
You can safely flash any of the Roms, Kernels and Recoveries found here in the T-Mobile GS3 forum.
You should also be able to flash any of the mods available, but unless you are on a matching firmware build, YMMV.
Flashing T999/T999V modems shouldn't harm the phone, but they will not work.
Why wont my camera work after I flashed CM?
This is a known issue reported by several people on several roms. It seems the fixes are different for some roms, and one or two have no solution as of right now. The most likely cause is a Kernel/Module mismatch. (for example, if you flashed a T999 based rom, but kept your T999L kernel, it will not work as the kernel cannot work with the T999 modules.) In this case, the fix is simple, flash any of the kernel plus modules I have made available. This will flash the kernel, plus its compatible modules and should solve the camera issue. Some have reported this being fixed by flashing the ktoonsez kernel (it includes its own modules).
In the cases where this does not solve the issue, it may be due to an incorrect module, lib, framework, cameradata, kernel, or any combination of those or possibly something else we have not found yet.
Why is my WiFi and/or Bluetooth not working after flashing a T999 based Rom?
Most likely this is also due to a kernel/module mismatch. Try flashing one of the kernel plus moudles I have available.
Let me know if you think of any other questions I should add here! Thanks!
Doc ​

How To Root!!!
How To Root Your T999L
There are currently three methods I have confirmed working to gain root access. I will list them in recommended order.
Method 1 - The Root66 Way (RECOMMENDED)
Use Odin to flash the ROOT66 Firmware. Download from my firmware thread or mrRobinson's original Root66 thread. (Don't forget to thank mrRobinson for his hard work! He doesn't even have this device, but he still takes the time to fix us up with this firmware!)
Download the Root66 firmware. Several builds may be available, it is suggested that you use the latest version available, though you should read about any update before taking the plunge!!! (At the time of this writing, NC1 is the latest firmware for the T999L).
Flash in Odin 3.09 as you would any other firmware. (Place in the AP section) (If still using Odin v3.07, put the firmware in PDA instead of AP like in v3.09)
How to Flash Root66 (or any firmware) In Odin
Download and install the latest Samsung USB Drivers (see my sig)
Download and extract Odin 3.09 (see my sig)
Download the root66 firmware linked above.
Run Odin by double clicking the Odin.exe within the folder you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM# port listed toward the top-left of Odin (under ID:COM)
Click on the AP button (3.09) or PDA button (3.07) in the middle-right area of Odin.
Browse to and select the firmware you downloaded
Make sure Auto-Reboot and F. Reset Time are the only options checked and that AP (or PDA) is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This can take a few minutes, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache! (It may seem to hang during boot, this is normal and you must be patient!!!)
DONE!!! :victory:
:highfive:​
Method 2 - The Recovery Way
Use Odin to flash either CWM or TWRP custom recovery. (use the latest available d2tmo or d2lte version. d2ltetmo versions will have some compatibility issues with certain Roms/Mods)
Reboot to the custom recovery.
Flash your preferred superuser app and binary.
You can download Odin, SuperSU, Superuser, TWRP and CWM from my signature.
How to Flash Recovery In Odin
Download and install the latest Samsung USB Drivers from my signature
Download and extract Odin 3.09 from my signature
Download your preferred recovery in a .tar or .tar.md5 format. (you can get these from my signature.)
Run Odin by double clicking the Odin.exe within the folder you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM# port listed toward the top-left of Odin (under ID:COM)
Click on the AP button in the middle-right area of Odin.
Browse to and select the Recovery you downloaded
Make sure Auto-Reboot and F. Reset Time are the only options checked and that AP is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct recovery and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash.
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
DONE!!! :victory:
You may now reboot into your custom recovery and flash the SuperSu.zip to gain root!
:highfive:​
Method 3 - The Motochopper Way
Use the MotoChopper Exploit
Thread and instructions here: [ROOT] Root Samsung Galaxy S4 with Motochopper
Yes this tutorial is for the S4, but it will work for the T999L as well.
Note: I dont recommend using Motochopper simply because it will be patched against soon. (most likely the next update) So IMO its best to just learn a method you can use again in the future.
Now, Before you do anything else!!!!
BACKUP YOUR NV-DATA!!!
This will create an On-Device backup of your IMEI and other NV Items.
Do this and you will not have to keep track of any files as it will be backed up internally, permanently.
You only have to do this ONCE! It will not go away when you flash Roms, Recoveries, Firmware, etc!
Download and Install the Terminal Emulator from the Play Store.
Open Terminal Emulator and enter the following:
Code:
su
reboot nvbackup
The device will reboot and backup all necessary data. That's it!!!
Restoring your NV-Backup
If you do lose your IMEI, all you have to do is open Terminal Emulator and enter the following:
Code:
su
reboot nvrestore
​

Revert to Stock and Unroot
How To Revert To Stock​
Note: Do not forget to use Triangle Away to reset your binary counter if you are planning to make a warranty claim.
Note2: BACKUP! BACKUP! BACKUP!
Method 1 - Using TWRP or CWM Recovery
Reboot into CWM or TWRP Recovery
Flash PureStock Rom
Flash the unmodified, Secure UVAMB7 Kernel
Flash Stock UVAMB7 Recovery
Next, if you want to wipe everything but your internal SD Card, Factory Reset before rebooting.
If you want a 100% clean, out of the box type device, reboot Recovery.
This should take you into the stock recovery you just flashed. Now Factory Reset.
Reboot Phone
(Last chance to run Triangle Away!)
Open SuperUser/SuperSU (app)
Find and select the option to Permanantly Unroot.
Reboot
Done!!!
Method 2 - Using Odin
Download Odin 3.07 from my signature
[*]Download Chainfire's Triangle Away to your External SD Card (Thread)
[*]Download and extract Stock System + Root
[*]Download Stock Recovery
[*]Download Stock Kernel
[*]Open Odin
[*]Reboot Phone into Download Mode. (Power + Home + Volume Down, Then press Volume Up when prompted.)
[*]Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
[*]You should now see a COM# port listed toward the top-left of Odin (under ID:COM)
[*]Click on the PDA button in the middle-right area of Odin.
[*]Browse to and select the Stock System you downloaded
[*]Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
[*]TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
[*]If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
[*]Click Start to begin the flash. This can take a few minutes, so be patient!
[*]Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
[*]You may unplug the phone and close Odin if you wish.
[*]Wait at least 5-10 minutes for the system to boot the first time and then build its cache! (It may seem to hang during boot, this is normal and you must be patient!!!)
[*]If the phone still hangs during boot up, hold the power button down until it shuts off, quickly release power and then Immediately repress Power + Home + Volume Up. This will boot recovery. Now Factory Reset and Reboot.
[*]Follow these same steps again for the Stock Kernel and Stock Recovery you downloaded. (Note: You can alternatively now replace all 3, System, Recovery and Kernel, with the official root66 firmware! root66_TMO_T999LUVAMB7.7z)
[*]DONE!!!
Reboot Phone
Install Triangle Away and reset the flash counter.
Reboot and check Triangle Away to see if it still says the counter is at zero.
Now, to unroot, open SuperUser/SuperSU (app)
Find and select the option to Permanantly Unroot (Full Unroot or similar)
Reboot
Next, if you want a 100% clean, out of the box type device, reboot Recovery.
This should take you into the stock recovery you just flashed. Now Factory Reset.
This will wipe Triangle Away as well as your Internal SD Card.
Your phone should now be exactly as it was when you powered it on the very first time!
Done!!!
​

Custom Recoveries​
What you need to know
Currently, only CWM has a recovery specifically for the T999L. Because of this, you can use Rom Manager to install CWM if you are rooted.
I do not recommend this however....
I suggest you use either CWM or TWRP for the T999 (d2tmo). It will work just the same and you will not have any of the compatability problems.
Most devs do not have their roms set up to allow flashing to the T999L, this will solve one part of that problem.
The only drawback to this is that you cannot use Goo Manager or Rom Manager to install/update your recovery.
Depending on where you get it, the flashable zips for CWM and TWRP may not flash if you try to change/update by flashing from your current recovery. If you use the files I have linked to in my signature, this should not be an issue.
So unless you know for sure that you have a d2tmo recovery installed, I would go ahead and flash one I have available just to get it out of the way.
Mobile Odin
Mobile Odin does not yet support the T999L. I have already submitted the required information to Chainfire, and since it is most likely already completely compatable, I am hoping it will be added in the next update.
If you are currently running a T999L build, Mobile Odin will immediately tell you it is not supported if you open it. If you are using a T999 Rom, Mobile Odin would most likely work. I base this on the fact that the T999 recoveries will work and Mobile Odin functions in a way as a temporary recovery. Keep in mind, this is nothing more than a guess on my part.
Flashing ROM's To Your T999L
You CAN flash any of the ROM's which are built for the original T999. Pretty much any ROM you find in our Development Section should work on the T999L.
There are, however, just a few small things that you need to remain aware of.
TouchWiz ROM's
Touchwiz ROMs are those based on the Stock, Shipped firmware (The software that came on your device)
If the ROM you choose includes a kernel, everything should work and you have nothing else to worry about.
If it does NOT come with a kernel, you will most likely have to flash either the UVDMD5 kernel, or the UVAMB7 kernel + Modules. More information and both can be found in my Development thread.
Either kernel should work just fine. You are free to choose either one. If you run into issues with one, please share the information so everyone else can benefit, and also to confirm for you that it is a kernel problem.
CM / AOSP / AOKP
Some of these roms will not flash without editing the updater-script. As these roms progress, the devs should add the T999L making this more of a Non-Issue.
If you get a Status 7 error, you will most likely need to follow these steps to make it flashable.
Unzip the ROM.
Browse to and open the updater-script (use Notepad+++
At the top you will see the 'Asserts'
You have 2 options:
1. Remove all of the Assert lines.
2. Add another assert. If the current ones are using d2tmo, add d2ltetmo. If using UVDMD5, add UVAMB7.
Save and rezip the file. (delete the signatures if present)
Flash ROM.

ROMS
For the moment, I will use this area to post ROMs that have had their updater-scripts edited to allow flashing to the T999L.
CM_10.1.2_d2tmo-d2ltetmo-d2can.zip
​

I know! Lets have a spelling contest!

Thank you doc for starting this thread. I came over to TMo from sprint. Sprints speeds in my area (S.W. Houston) sucked a**.. Speeds are 2x sometimes 3-4x faster than sprint now. No lie. Although I'm very excited to have the S3Lte variant. I had no idea about S3's being different for TMo. The first day I got my phone I rooted and flashed what I thought was capable for my phone and winded up hard bricking. Luckily I was able to play dumb and get another one. I'm currently rooted on stock until one of these kick ass devs shoots out some Roms I can flash with no worries.
With all that said. I'm looking forward to being a part of this community as I can already tell you guys are very welcoming. I have been flashing since I got my OG Evo 3 yrs ago so I'm somewhat experienced but I can't code to save my life. I will continue to check on the daily and help out with any questions I feel I can provide a answer for. Cheers to all and happy flashing.
Sent from my SGH-T999L using xda app-developers app

hi..
my phone is s3 t999. rooted .
i installed CWM.
i bacup files . 3 or 4 times .
now it is cover my phone memory. i want to remove bacup files from phone memory.
i can not delete manually .have no idea about how to delete.
when i connect to pc. it shows phone memory. it also shows the folder clockwordmode . but there is no file to delete
please help anyone

I'm not completely understanding your question. You want to remove files from your phones internal memory but your asking about files on your SD??.
Have you tried to reboot?.
What ROM are you running?
Sent from my SGH-T999L using xda app-developers app

Double post. Replied to other one.
Sent from my SGH-T999 using xda premium

Any recoveries work with T999L yet?

All of them.
Sent from my SGH-T999 using xda premium

In my other GS3 i was able to use goo manager to flash recovery.......is there anyway to use these with T999L?
Im sorry for all the questions just dont want to brick my shiny new t999L

Flash the latest twrp from docholiday's sig. Its twrp for the T999, but it works without issues. And if you flash twrp or cwm for the T999L with goo/ROM manager, the recovery will fail to flash pretty much everything.
I'm going to post a guide later today on how to get root, custom recovery, and custom ROMs and kernels on the T999L. For now the best resource is doc's d2ltetmo thread in android development.
Edit: just realized that this post is a guide almost exactly like the one I was writing. Major brain fart.
Sent from my T999L on PACman

I downloaded twrp 2600 tar and img
Would flashing with odin trigger the triangle or anthing?
A guide would be amazing!!!!
Used motochopper to root!

manofsteel1 said:
I downloaded twrp 2600 tar and img
Would flashing with odin trigger the triangle or anthing?
A guide would be amazing!!!!
Used motochopper to root!
Click to expand...
Click to collapse
Geeze guys! Patience please! If you read the first post I did say this thread should have everthing needed when done. Everthing is pretty much done as it is, I just have to format it all to make it easy to read and navigate. Its just taking a little while because I have my daughter this weekend. I am working on getting it done as quick as I can. Its all coming very soon! I promise!
Sent from my SGH-T999 using xda premium

And flashing the stock system will not trip the counter. But if you have a custom recovery it will always say at least 1.
Sent from my SGH-T999 using xda premium

No problems I just don't want to brick it lol
Sent from my SGH-T999L using xda app-developers app

manofsteel1 said:
No problems I just don't want to brick it lol
Sent from my SGH-T999L using xda app-developers app
Click to expand...
Click to collapse
As long as you stick to roms, kernels, and recoveries found in this forum, you should be fine. I thonk so far, the only T999L bricks have been due to flashing the firmware for other models. (I'm referring to root66 and official firmware as well as the recovery flashable firmware in the dev section. These are for the T999 and T999V only)
Ill go ahead and post what I have about flashing roms in a few min. Ill format it later on but this way you'll have something for the time being.
Sent from my SGH-T999 using xda premium

1) flash the stock rooted system with Odin
2) (Optional but HIGHLY recommended) backup your NV (as described above)
3) flash recovery of your choice with Odin
4) (Optional but HIGHLY recommended) make a nandroid (using the recovery you just flashed)
Now you are good to flash almost anything for the T999 in recovery. Be warned that any modem other than MB7 will have no service on a T999L. Also, some ROMs or kernels may bootloop or have other issues; post in the ROM/kernel thread accordingly.
Avoid flashing with Mobile Odin; T999L is not supported yet.
Also, avoid flashing with PC Odin after the initial root/recovery process, unless you are flashing back to 100% stock - then follow the guide in the second post of [url="http://forum.xda-developers.com/showthread.php?t=2308514]this thread[/url]

[Q] Phone doesn't connect to GSM

Hello.
So my N7100 doesn't connect to mobile network. No voice calls, text messages or mobile internet. Wifi works just fine, although signal seems to be a little weaker (maybe just my imagination).
What I did and how it happened:
I got sick of Samsung being assholes and not pushing out software updates, so I decided to flash some custom ROM. I choose CM, because they had that "one click installation", so I didn't have to do a lot of work. After a week of using CM I decided that it sucks and wanted back my original android with all gimmicks from Samsung, mostly because battery life with CM was terrible, not even one day. And that's when everything went downhill. I downloaded and installed firmware for Baltic region, because I live here and I bought my phone here. From that moment my phone stopped being phone and evolved into wifi only tablet. After being very pissed and trying to flash couple different roms I gave up. Found my phones original box user manual and other papers. It turns out that my phone is made for Hungary region. So shop where I bought it must have imported wrong models (most likely cheaper for bigger profit). Flashing original for Hungary made firmware doesn't resolve this issue.
Guys, I really need help. I just want to return to stock - original firmware and reset flashing counter. Please help, and if possible in layman's terms...

EddsLV said:
Hello.
So my N7100 doesn't connect to mobile network. No voice calls, text messages or mobile internet. Wifi works just fine, although signal seems to be a little weaker (maybe just my imagination).
What I did and how it happened:
I got sick of Samsung being assholes and not pushing out software updates, so I decided to flash some custom ROM. I choose CM, because they had that "one click installation", so I didn't have to do a lot of work. After a week of using CM I decided that it sucks and wanted back my original android with all gimmicks from Samsung, mostly because battery life with CM was terrible, not even one day. And that's when everything went downhill. I downloaded and installed firmware for Baltic region, because I live here and I bought my phone here. From that moment my phone stopped being phone and evolved into wifi only tablet. After being very pissed and trying to flash couple different roms I gave up. Found my phones original box user manual and other papers. It turns out that my phone is made for Hungary region. So shop where I bought it must have imported wrong models (most likely cheaper for bigger profit). Flashing original for Hungary made firmware doesn't resolve this issue.
Guys, I really need help. I just want to return to stock - original firmware and reset flashing counter. Please help, and if possible in layman's terms...
Click to expand...
Click to collapse
Press *#06# and see if your EMEI is fine... If it says something like 000000000049 it seems to be bugged and you can try this solution:
I flashed the firmware N7100XXDMF2_N7100OLBDMD2_XME using ODIN PC and follow the below using root explorer:
- copy /efs/ to the sdcard
- delete /efs/
- reboot (after reboot I got the yellow recovery mode window floating over, no lock screen, and pressing power button turns the phone off directly)
- /efs/ will be autocreated again. copy the efs folder from the sd card to / (root explorer will tell you that the folder already exists and it will merge them)
- reboot
PS: I did not have an /efs/ backup before applying the above.
Click to expand...
Click to collapse
I saw from another post. Im going to try this too since Im having the same problem as you.
Find your ROM here: http://www.sammobile.com/firmwares/1/?model=GT-N7100&pcode=CHE#firmware I selected Chile Entel, but you can choose your country and company, it is the original ROM and it should fix our problem, Im downloading the ROM by now.
To use Odin, just put your phone in download mode (vol up/down + home + power) and then plug in to your PC, open Odin and at "PDA" select your ROM, then put start and just wait a few minutes and it should be working again...
After this, you should make a back up of your EFS file using a root explorer and then flash with any ROM you want (Im trying Ditto 3, it seems to be a cool jelly bean) and after this flash, you should put your new EFS file... Just the problem that Im facing is how to put this backup since the EFS is a folder being readed all the time, so there should be a program to do this, but I cant figure this out yet.

My phone doesn't have any IMEI any more. "null/null" is value given by my phone after requesting IMEI. I already flashed original ROM, problem is still here.
About /efs/ I could backup it with "File Manager"app from google play, but I can't delete it, because it is in read only.

EddsLV said:
My phone doesn't have any IMEI any more. "null/null" is value given by my phone after requesting IMEI. I already flashed original ROM, problem is still here.
About /efs/ I could backup it with "File Manager"app from google play, but I can't delete it, because it is in read only.
Click to expand...
Click to collapse
Somehow you will have to access to edit it and you will be able to solve that problem... Otherwise go to technical service.

kito2 said:
Somehow you will have to access to edit it and you will be able to solve that problem... Otherwise go to technical service.
Click to expand...
Click to collapse
In order to delete /efs/ you have to be rooted, when you flash factory rom you loose root privileges.

EddsLV said:
In order to delete /efs/ you have to be rooted, when you flash factory rom you loose root privileges.
Click to expand...
Click to collapse
After flash factory rom is easy to make root again hehe.. Anyways keep reading and maybe you will find another solution, you can't be the only one who had that problem... Good luck my friend.
Try this link http://forum.xda-developers.com/showthread.php?t=1896696

kito2 said:
After flash factory rom is easy to make root again hehe.. Anyways keep reading and maybe you will find another solution, you can't be the only one who had that problem... Good luck my friend.
Click to expand...
Click to collapse
Thanks. So I rooted my phone and did all than you wrote above - copied, deleted, replaced. It didn't helped and now I have that yeleow recovery window all the time :/

Need efs from a T889

I've thoroughly trashed my efs & nv items. Long story but basically, I went into dialer menu #*9090#, picked option #3 and, thinking I had multiple backups of everything, picked yes. Dumb? Yes.
My backups were on a hard drive that I'd replaced with an SSD and got lost during that replacement. I hadn't backed up the backups - only had the single copy now lost.
Phone will boot but now shows unknown baseband, borked IMEI. I can get into download mode and have TWRP recovery installed. WIFI works, I can easily get stuff on/off the device & access an ADB shell. It's rooted/stock UVALJ1.
I did find one backup, made using QPST (.qcn file), but in trying on two different PCs & a 32bit WinXP VM I cannot get the phone recognized by QPST (drivers installed, finds port, but "No phone".)
If someone can give me a TWRP backup of their efs I *think* that may get me fixed. I know that may contain your IMEI & if it fixes me but contains the wrong IMEI, that's fairly easy to fix, assuming all the posts on fixing that issue are accurate. I'm not trying to steal an IMEI, I'm trying to make my Note 2 usable as a phone again.
Sent from my Nexus 7 using Tapatalk

LanceDiamond said:
I've thoroughly trashed my efs & nv items. Long story but basically, I went into dialer menu #*9090#, picked option #3 and, thinking I had multiple backups of everything, picked yes. Dumb? Yes.
My backups were on a hard drive that I'd replaced with an SSD and got lost during that replacement. I hadn't backed up the backups - only had the single copy now lost.
Phone will boot but now shows unknown baseband, borked IMEI. I can get into download mode and have TWRP recovery installed. WIFI works, I can easily get stuff on/off the device & access an ADB shell. It's rooted/stock UVALJ1.
I did find one backup, made using QPST (.qcn file), but in trying on two different PCs & a 32bit WinXP VM I cannot get the phone recognized by QPST (drivers installed, finds port, but "No phone".)
If someone can give me a TWRP backup of their efs I *think* that may get me fixed. I know that may contain your IMEI & if it fixes me but contains the wrong IMEI, that's fairly easy to fix, assuming all the posts on fixing that issue are accurate. I'm not trying to steal an IMEI, I'm trying to make my Note 2 usable as a phone again.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Flashing EFS from another device is not going to work.
Try to recover the IMEI using KIES emergency recovery. http://forum.xda-developers.com/showthread.php?t=2261153
If this still does not work try flashing the UVALJ1 modem.

ciphercodes said:
Flashing EFS from another device is not going to work.
Try to recover the IMEI using KIES emergency recovery. http://forum.xda-developers.com/showthread.php?t=2261153
If this still does not work try flashing the UVALJ1 modem.
Click to expand...
Click to collapse
Can't seem to get KIES to connect - the most definitive result I got was a device not supported by KIES message after uninstalling/reinstalling drivers, making sure the phone is in the right mode etc. For the most part KIES just sits at connecting forever. This is the case with both the Note 2 and a Samsung Galaxy S4. KIES isn't exactly inspiring confidence it can magically restore my entire efs & all NV items...
Just to clarify, I can access recovery just fine - I can use Odin to flash to whatever albeit the bootloader is 4.3/Knox locked. I can flash modems, ROMS, etc and access ADB shell or whatever else I'd need to do with ADB. Can't seem to get KIES to work and as I understand it what you're telling me to do in KIES won't actually restore efs, it just resets it to a stock state and lets efs rebuild - assuming the NV items are still there, which they are not. I really hope I'm wrong and I'll have to come back here once I get KIES sorted out and tell you how silly I was for not believing you in the first place!
I did re-flash the modem using TWRP, no change there.
Here's the text of the warning I foolishly ignored:
Warning: Must read below guide
All Communication between AP/CP-
will be disconnected!
To return to normal mode,you
must download efs12.tar file!
All NV data will be erased!
Really want to use RmNET?
Click to expand...
Click to collapse
This was in the ServiceMode menu accessed with dialer code *#9090# but now there isn't a menu there - just a blank screen that says ServiceMode at the top. Dialer code *#0011# produces the same result - no menu where there used to be one, just blank screen/ServiceMode. Based on that warning, this isn't something I expect KIES to fix - but as I said, I hope I'm wrong about that...

Tried KIES on another PC with same result - that was 2.x KIES.
I used Odin 3.09 to flash to T-Mobile stock rooted 4.3 from this thread: http://forum.xda-developers.com/showthread.php?t=1975560
Switching to KIES 3 got KIES talking to the phone. It says I'm on the current version of the firmware (because I am - it's what I just flashed with Odin.) If I go into Tools/Emergency nothing is listed. If I go into the second choice and enter the model number with the phone plugged in, it tells me it doesn't support firmware initialization. If I do it without the phone plugged in, it works and accepts the serial number from the phone. If I plug the phone in right after I've gotten past this point, KIES winds up going off into never never land a bit later after it tells me everything is going to be wiped and the phone will be put back to its initial state (which does sound somewhat promising.)
Its spawning this AdminDelegator process which seems to just be sitting doing nothing and the KIES window is shaded. I can close it but that's about the only interaction possible with it in this state - none of the menus work and it seems like it's waiting on something to be clicked maybe in the AdminDelegator process but that process has no window anyplace.
It's possible there is something useful buried in KIES but it's a horrible piece of software. They seem to be authoring it on at best 32bit Windows 7 and that's a stretch, I suspect they're still targeting 32bit XP. I'm on x64 Windows 8.1. I could rant much more but I'll leave it at that.
I'm going to keep working with it and see if I can get around how they've written it or I might just stick it in a 32bit XP VM and see if it's happy back in 2005, software-wise. <G>
I may wind up giving up and just getting another phone - I've already read up some on my options and the funny thing is, I still want a Note 2 - they can be had for more reasonable $ now than a year ago anyway...

LanceDiamond said:
Tried KIES on another PC with same result - that was 2.x KIES.
I used Odin 3.09 to flash to T-Mobile stock rooted 4.3 from this thread: http://forum.xda-developers.com/showthread.php?t=1975560
Click to expand...
Click to collapse
Did you verify the IMEI after this flash ?

ciphercodes said:
Did you verify the IMEI after this flash ?
Click to expand...
Click to collapse
Short answer: IMEI & baseband same as before the flash - both are "Unknown".
Prior to my messing with the dialer menu, everything was fine. I'd used Odin or TWRP recovery to flash a variety of different ROMs the last of which was the 4.3 we're talking about here and it was working. I'd used it for several days. Everything but screen mirroring worked without any problem and I had service - I read up on the screen mirroring problem and it sounded like getting the device to show "Official" might help so I tried to reset my flash counter which I did not do before going to 4.3. Flash counter wouldn't reset so I decided to go back as far as I could on modem/ROM and see if I could reset flash counter then. (I know my Knox flag is not fixable - I was just trying to change the flash counter.)
Using TWRP, I installed UVALJ1 modem & associated ROM, leaving the 4.3 Knox locked bootloader in place to see if that'd work. It did, it booted and I had service. I was actually playing with the menus to see if the old dialer code free unlock menu settings still seemed to work because someone had posted about needing to unlock - looked like the menus were still there for doing an unlock. In messing with the menus I picked the option that messed everything up and since doing that, no matter what I flash, IMEI & baseband are unknown.
Unless KIES rebuilds the entire radio - which it very well might based on it needing the correct model and then wanting a valid serial # - I think I need an efs restore to get the phone communicating with anything now.
One thing I just now did - using the free NV Items Reader Writer from this thread: http://forum.xda-developers.com/showthread.php?t=1804117
On my Note 2 configured as "DM+Modem+ADB" in Qualcomm USB settings (the only of several dialer menus I know of that still actually exists & seems to work), I can see the modem & port in device manager. But the app cannot communicate with the phone. If I change nothing, unplug the Note 2, plug in my Galaxy S4 in "DM+Modem+ADB" mode, I see modem & ports pop up in device manager and now the app can communicate with the phone.
I'm afraid, based on the text of that warning and searching for what "AP" and "CP" are, that the phone isn't going to be able to communicate with much of anything until it gets its efs fixed. This test where I just swap phones seems to be comfirming that this phone isn't responding like it should. Basically my modem & the rest of the phone are disconnected right now - at least that's my understanding. If the modem really is disconnected then obviously trying to do something to fix it via the modem is never going to work. The KIES may work - if I can ever get it sorted out. Haven't yet tried it in a VM might do that right now...
Edit:
Got KIES3 & drivers working in Windows XP SP3 VM. KIES connects to phone but if I pick Tools/Firmware Upgrade with the phone connected it just says "SGH-T889 does not support initializing" and my only choice is "OK". If I go Tools/Firmware without the phone plugged in, I can enter the model # and then it asks for serial #. If I plug the phone in at the point it goes all the way to where it says it's downloading firmware and then same result as on Windows 8 - an AdminDelegator process gets started, KIES gets sort of dimmed like it's waiting on something and nothing ever happens. If I never connect the phone KIES goes through the downloading process then gets an error with options to send a message or cancel - no information about what the message is, what the error is - just I can send it, it won't contain personal information or I can cancel.

XAA/XAA/VZW - Texting Issue

Hey all,
I followed the guide at https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473/page66 starting with a stock Verizon S8 plus
But ended up screwing something up and ended up with XAA/XAA/VZW instead of XAA/VZW/VZW and now I can not send any text messages.
I did enable all bands from within *#2263#, but I only have the options of LTE/3G/2G when looking at the network mode.
Just wondering if anyone ended up in the same spot I am and how you resolved it (without returning the phone)

sniper7kills said:
Hey all,
I followed the guide at https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473/page66 starting with a stock Verizon S8 plus
But ended up screwing something up and ended up with XAA/XAA/VZW instead of XAA/VZW/VZW and now I can not send any text messages.
I did enable all bands from within *#2263#, but I only have the options of LTE/3G/2G when looking at the network mode.
Just wondering if anyone ended up in the same spot I am and how you resolved it (without returning the phone)
Click to expand...
Click to collapse
Did you flash XAC with CSC, reboot and flash XAC Home_CSC, then flash VZW with home_CSC only? Are you using Princeton?

sniper7kills said:
Hey all,
I followed the guide at https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473/page66 starting with a stock Verizon S8 plus
But ended up screwing something up and ended up with XAA/XAA/VZW instead of XAA/VZW/VZW and now I can not send any text messages.
I did enable all bands from within *#2263#, but I only have the options of LTE/3G/2G when looking at the network mode.
Just wondering if anyone ended up in the same spot I am and how you resolved it (without returning the phone)
Click to expand...
Click to collapse
I'm sitting in the same boat. I did have everything working and wanted to updated to the newest vzw firmware but wouldn't let me do a straight update, as ODIN kept saying Model mismatch. So I started the process over with the newest vzw firmware and now am stuck at XAA/XAA/VZW.
Also tried going back full VZW firmware and that is not happening.
Also after following the guide and everything is flashed, I cannot go in a flash the same Home CSC file from the vzw firmware as it tells me there is a model mismatch still

VinylJStar said:
Did you flash XAC with CSC, reboot and flash XAC Home_CSC, then flash VZW with home_CSC only? Are you using Princeton?
Click to expand...
Click to collapse
Yes, I did in that order; and I used Odin PrinceComsy 3.12 to flash XAC as I had a md5sum issue in Odin 3.12.7 and then had to use Odin 3.12.7 for VZW as I kept getting a model mismatch in PriceComsy.
PrinceComsy that I have has an MD5 sum of 91a4593ebdba14268ee719e7a5e04e8e
Oden 3.12.7 that I have has an MD5 sum of 5162c42e934b7efbf353e3837ccb0ba3
If you used something that was different can you provide a link?
pimpmaneaton said:
I'm sitting in the same boat. I did have everything working and wanted to updated to the newest vzw firmware but wouldn't let me do a straight update, as ODIN kept saying Model mismatch. So I started the process over with the newest vzw firmware and now am stuck at XAA/XAA/VZW.
Also tried going back full VZW firmware and that is not happening.
Click to expand...
Click to collapse
I would agree, What about Visual Voicemail? When I try to launch it it simply says "not supported".
So far its just the verizon bloat thats removable and outbound text messages that aren't working.

I'm noticing a lot of people having issues. Where are you getting your versions of the custom Odin? It might be something to do with that. I'll upload the one I got that worked for me tonight with the exact steps I took. Maybe that will help some people.

cadcamaro said:
I'm noticing a lot of people having issues. Where are you getting your versions of the custom Odin? It might be something to do with that. I'll upload the one I got that worked for me tonight with the exact steps I took. Maybe that will help some people.
Click to expand...
Click to collapse
I used the Prince Comsy version and the first time I did this is worked fine. But I installed an older version of the VZW firmware and did not have the new advanced display color control. So I tried to just update to the newest one in the Prince Comsy ODIN and gave me a Model Mistmatch error. So I figured I would bite the bullet and do the process over again but use the newest firmware, and am now stuck at this point. I have re-done the process 5 times now and no matter what I am still ending up with XAA/XAA/VZW and no network, IMS is not registering and not out bound text. Also there seems to be no way to go back to full stock and when I flash through ODIN, it goes to the blue Installing Update screen and errors out at 32% every time.

cadcamaro said:
I'm noticing a lot of people having issues. Where are you getting your versions of the custom Odin? It might be something to do with that. I'll upload the one I got that worked for me tonight with the exact steps I took. Maybe that will help some people.
Click to expand...
Click to collapse
Honestly; I don't recall 100% but it would have been from a link posted to XDA-Developers.
Firmware wall all retrieved from sammobile or from links posted here as well.
Please do update and share that link when you get a chance.
Fingers crossed that a straight XAA firmware comes out in the next week that will resolve this issue, and bypass the need for XAC all together.
pimpmaneaton: I have the same exact issue at 32%.

Sorry about the wait guys, I'm in the process of moving into a new place so paperwork is a plenty.
Anyways, here's the version that I downloaded from a thread on XDA.
http://www.mediafire.com/file/26modnk5c01n96h/Odin3_v3.12_PrinceComsy.zip
Also here are the exact steps I took when flashing the multiple firmwares. I actually did this all through the comsy version of Odin.
1: I reset and formatted my phone from the settings menu option, and let it do it's thing.
2: I flashed the Canadian XAC firmware over the phone, and selected the default CSC file. DO NOT use the Home_CSC file for this flash.
2a: enabled the PIN to unlock AND power on the device. No accounts, extra settings or add ons.
3: Once the setup was finished, I went to the Dev settings and enabled USB debugging
4: After that I went into the phone settings menu and enabled all LTE bands and saved my settings.
5: Once that was all done, I used ADB to boot the phone into download mode and selected the stock VZW firmware, and made sure to select the Home_CSC this time
After a few minutes the phone booted up and the setup menu was the same as it was in the Canadian version. I went through all that while connected to Wifi added my accounts and logged everything in, etc. Once it was at the home screen, after maybe 20 seconds it gave me a popup to select the Global network type. Once I selected it, it took maybe another minute or two until I started getting signal and LTE. I sent a test message and I was able to send and receive texts just fine. Data is also working perfectly, as well as calls. Hopefully everything keeps working fine, but as of now everything has been working smoothly.

cadcamaro said:
Sorry about the wait guys, I'm in the process of moving into a new place so paperwork is a plenty.
Anyways, here's the version that I downloaded from a thread on XDA.
http://www.mediafire.com/file/26modnk5c01n96h/Odin3_v3.12_PrinceComsy.zip
Also here are the exact steps I took when flashing the multiple firmwares. I actually did this all through the comsy version of Odin.
1: I reset and formatted my phone from the settings menu option, and let it do it's thing.
2: I flashed the Canadian XAC firmware over the phone, and selected the default CSC file. DO NOT use the Home_CSC file for this flash.
2a: enabled the PIN to unlock AND power on the device. No accounts, extra settings or add ons.
3: Once the setup was finished, I went to the Dev settings and enabled USB debugging
4: After that I went into the phone settings menu and enabled all LTE bands and saved my settings.
5: Once that was all done, I used ADB to boot the phone into download mode and selected the stock VZW firmware, and made sure to select the Home_CSC this time
After a few minutes the phone booted up and the setup menu was the same as it was in the Canadian version. I went through all that while connected to Wifi added my accounts and logged everything in, etc. Once it was at the home screen, after maybe 20 seconds it gave me a popup to select the Global network type. Once I selected it, it took maybe another minute or two until I started getting signal and LTE. I sent a test message and I was able to send and receive texts just fine. Data is also working perfectly, as well as calls. Hopefully everything keeps working fine, but as of now everything has been working smoothly.
Click to expand...
Click to collapse
Thank for the upload; but its the same version I already have.
So I tried to do a Manual software Update (Settings->Software Updates->Download updates manually) check and i noticed something weird;
"Current Version: G955USQU1AQD9/955UOYN1AQD9/G955USQU1AQD9"
What do each of those build numbers mean?
I'd assume one is the bootloader, one is the the radio, and one is the android version???

guess ill wait for unlocked s8+ firmware and try that, maybe the next verizon update will fix the Xaa/Xaa/Vzw issue

So I just wanted to let you guys know that I sent my phone off to Samsung. Because the Knox hasn't been tripped, the warranty is still valid. So I will let you guys know what they do as far as repairing the phone's software.
Sent from my VS988 using Tapatalk

I'm waiting until the unlocked S8+ releases. I'll try that firmware.
Sent from my Nexus 6P using Tapatalk

Try this flash COMBINATION_FA70_G955USQU1AQD8_CL11249373_QB13326524_REV00_user_mid_noship_MULTI_CERT.tar.md5 and then enable usb debugging and open adb shell and type in echo "VZW" > /efs/imei/mps_code.dat and reboot and flash the full verizon files and bl, ap, cp, home csc, and user data should get you back to vzw/vzw/vzw

Whats the chance someone knows about the SM-G955U1 ?? http://updato.com/firmware-archive-select-model?exact=1&q=SM-G955U1

sniper7kills said:
Whats the chance someone knows about the SM-G955U1 ?? http://updato.com/firmware-archive-select-model?exact=1&q=SM-G955U1
Click to expand...
Click to collapse
its the unlocked firmware, just flashed it. went through a whole sim config thing. It did not complete successfully but I'm going to keep trying. SmS confirmed working on this firmware.

Seems legit will contain testing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G955U1 using Tapatalk

Factory reset fixes that problem

Just wanted to provide an update to everyone as well...
Using PrinceComsy Odin, I was able to flash the XAA version of 955U1.
I used the NON-HOME csc file (Didn't have anything I wanted/needed to save) and its working like a champ.
I did have one weird pop-up about "installing features based on the new sim card that was inserted" but no errors.
Beyond testing if visual voicemail works from verizon, I'm happy to report my phone is fully operational Texting-wise.

I have the 955U1 downloaded but I am still using the Canadian FW with Verizon features enabled. Can I just flash over this one with the new firmware and be good to go? Or is there a certain method to doing so.

cadcamaro said:
I have the 955U1 downloaded but I am still using the Canadian FW with Verizon features enabled. Can I just flash over this one with the new firmware and be good to go? Or is there a certain method to doing so.
Click to expand...
Click to collapse
Curious about this too, as im also on the Canadian firmware.