FORUMS
Remove All Ads from XDA

[WIP][MODEM][SM-T705] **LTE BANDS IN USA**[TESTERS NEEDED][DEV ASSISTANCE req]

808 posts
Thanks Meter: 926
 
By THEDEVIOUS1, Senior Member on 13th September 2014, 02:06 AM
Post Reply Subscribe to Thread Email Thread
D*mnit...i just typed up this informative article to explain whats going on & then the ENTIRE thing got deleted
Please keep checking this post as i will gradually add back the info as i go...for now i will post the zips/files & steps I've taken up to this point along with any other knowledge that u need to know and thx to @sicarius128 for pointing out the release of the south american model

USALTE705_NG1_MODEM.zip
^T705M NG1 MODEM (Flashing this will enable the north american LTE frequencies...i have tested this myself & it DOES indeed work to change the bands)

STOCK705_NF7_MODEM.zip
^T705 NF7 MODEM (this will put u back on the stock radio if u need it...although it is labeled NF7 it is the same modem that is included with the newer NG2 as well)

IF ANYONE IS ACTUALLY ABLE TO CONNECT AFTER FLASHING THIS THEN PLEASE DONT JUST GET HAPPY AND RUN OFF BECAUSE I NEED ALL THE DETAILS I CAN GET...THX IN ADVANCE

if u enter the dial code *#2263# (if this doesnt work then try *#0011#...i will include a link below with navigation instructions to get to the band selection menu) then select "LTE BAND" both before & after then u will notice that those available have in fact changed from "1.3,5,7,8,20" which are the stock/rest of the world values to "1,2,4,5,7,17" which correspond to the correct USA frequencies...at this point the mod MAY very well be working for some users but unfortunately for me my device still wont connect to the lte network for whatever reason so i need testers to see if this is an exclusive issue to my tab/sim or are there other settings that need to be changed somewhere. Below i will list additional steps i have taken & document other pieces of the puzzle i have put together for those of u who are interested,,,i humblyrequest that any devs or other knowledgeable users PLEASE post with your wisdom so we can get this working

http://forum.xda-developers.com/gala...4-lte-t2860001
^SERVICE MODE *#0011# NAVIGATION INSTRUCTIONS (please see post #2...there is an app called "advanced signal status" that makes this easier to access)

So...once i flashed the columbian modem & found that i still wasnt connecting to LTE even though the NA frequencies were in fact found in the aforementioned menu i tried a few more fixes. After doing some reading i ran across a file in the "system/etc" folder named "lteon_netlist.xml" which seems to contain an index of whitelisted lte networks from around the world & upon opening it i noticed that ALL of the north american companies were missing. i found the the file of the same name from the columbian rom & sure enough it included AT&T as well as t-mo & other domestic services. This almost SURELY seems to be an important part of the problem but even after replacing this file my problem persisted...i guess i should mention that i'm on straight talk with an ATT compatible sim & it may not be important but i tried my sim in a LG phone & it worked after i forced it to LTE . To further complicate things...it wouldnt work on an ATT branded note 3 & the sim card from the same note 3 wouldnt connect to lte on my device either even with proper apn settings

So with all of that said...a few more failed attempts i've made include the following
1. added various apn settings including KNOWN working values on other devices
2. deleted "persist.radio.lteon" from the location "data/property" or change its value from false to true
3. flashed the kernel from the colombian rom & even created an entire rom from the firmware in hope that some combination of the files it contained would cause it to connect...everything was fully functional after the fact but alas no LTE
4. did a REAL factory reset with the stock recovery which even erases the contents of the internal sd card
5. altered a note 2 zip which contains ATT csc files inside which interesting enough does change the device product code to T705NTSAATT according to the app "phone info" (links to zip & app below)
6. Used the band selection menu mentioned above to force lte bands only but not only does ths not work it desnt seem to survive a reboot either...i also used the app method to do the same (link below)
7. Last but not least...i have tried to flash the bootloader & YES i'm aware of how dangerous this is which is why i wont be uploading the zip here although i havent yet found a way to get it to overwrite which is one of the question i need answered below

lteon_netlist.zip
^LTEON_NETLIST.XML (this zip is NOT flashable because i was being lazy ....unzip then replace the file in "system/etc" & dont forget to change permissions to 0644 or rw-r--r--)

CSC_705_ATT.zip
^ATT CSC (please be aware...this will show the csc version as N7100ATTDMB1 but doesnt seem to cause any issues)

https://play.google.com/store/apps/d...gnalinfo&hl=en\
^ADVANCED SIGNAL STATUS APP (used to determine your current network connection...can be used to force to a certain type or to enable/disable individual gsm/wcdma/lte bands

https://play.google.com/store/apps/d...honeinfo&hl=en
^PHONE INFO (provides a ton of info about your device...including a list of all secret codes as well as a csc changer)

couple of quick questions for anyone who can provide answers or otherwise assist...thx in advance
1. @bentee20 @crzcraft does choosing the particular bands or lte only in fact force the mode on your devices...i'm aware when u use the app method that u will need to change the setting every boot. Just out of curiousity...could u guys post your location and device/rom details
2. @vovochka-s2 did u ever find a 705 pit file or can anyone else please provide one for us?
3. Directly related to issue 2...has anyone use hemidall to flash there tab & if so could u please list the steps as well as version u used
4. i dont expect any other users to attempt this at least until i can confirm it fixes things...CAN ANYONE PLEASE PROVIDE A PROVEN WAY OF FLASHING THE BOOTLOADER ON NEWER GALAXY DEVICES? It wont flash through odin do to security reasons (neither would the modem file file but it flashed fine using twrp)...i have tried installing it through recovery but after reboot nothing seems to have been changed according to the phone info app


the input of @UpInTheAir (particularly would like your opinion on #3 & #4 above...yeah i know bro but i'm so close & this is the level of desperation i have reached ) or @edan1979 would be welcome although i dont think either of u are actually in the states so im not sure how important this issue is to u if at all...to answer your question from the other thread a few weeks NO i 'm not aware of the exact location of the network selector list but i did notice that it disappears from settings after using the att csc zip so i might spend some time to track it down tonight even though i came across an easy way to change it back

@Hakams the above modem should fix your issue if u never figured it out...please report your results
Last edited by THEDEVIOUS1; 31st October 2014 at 12:12 AM.
The Following 3 Users Say Thank You to THEDEVIOUS1 For This Useful Post: [ View ] Gift THEDEVIOUS1 Ad-Free
 
 
13th September 2014, 04:48 AM |#2  
UpInTheAir's Avatar
Senior Member
Flag Phuket, Thailand
Thanks Meter: 14,477
 
Donate to Me
More
Sorry, I'm not going to get involved with bootloaders, if you get that wrong, your device is in a permanent world of hurt. It is possible to flash with Odin and I remember CWM.zip from the SGS2 days. On some devices, once you upgrade, it is impossible to revert.

Kernel side:

There is option in kernel build .config file with various regions. I haven't yet looked at what it really does in any sort of depth. I think I remember some thresholds and such. Maybe also drivers specific to various regions. (incl. modem/mobile connectivity ??? )

Code:
CONFIG_TARGET_LOCALE_EUR=y
# CONFIG_TARGET_LOCALE_KOR is not set
# CONFIG_TARGET_LOCALE_USA is not set
# CONFIG_TARGET_LOCALE_DEMO is not set
I don't know if it will even compile, but will try later on if you wish ?
13th September 2014, 05:16 AM |#3  
OP Senior Member
Thanks Meter: 926
 
Donate to Me
More
Quote:
Originally Posted by UpInTheAir

Sorry, I'm not going to get involved with bootloaders, if you get that wrong, your device is in a permanent world of hurt. It is possible to flash with Odin and I remember CWM.zip from the SGS2 days. On some devices, once you upgrade, it is impossible to revert.

Kernel side:

There is option in kernel build .config file with various regions. I haven't yet looked at what it really does in any sort of depth. I think I remember some thresholds and such. Maybe also drivers specific to various regions. (incl. modem/mobile connectivity ??? )

Code:
CONFIG_TARGET_LOCALE_EUR=y
# CONFIG_TARGET_LOCALE_KOR is not set
# CONFIG_TARGET_LOCALE_USA is not set
# CONFIG_TARGET_LOCALE_DEMO is not set
I don't know if it will even compile, but will try later on if you wish ?

I understand the risks & all i'm asking if u happen to know a sure-fire way then please pm me or something but i've already attempted odin, twrp & even dd with no results (of course this would be a last resort option...as more users present new info i'm sure i can find the patience to exhaust those possibilities before doing anything dumb)...as far as the kernel is concerned if its not too much trouble then PLEASE attempt to build one for us. I tried the one from the T705M but as i already stated above it flashed fine & was fully functional but didnt let me connect to LTE...one would assume those configurations would already be set since the frequencies are unlocked by default although i could see samsung using that as another way to keep those devices out of the american market so that they dont hurt domestic sales. I appreciate u chiming in & patiently await a test build of the USA enabled kernel...thx in advance
Last edited by THEDEVIOUS1; 13th September 2014 at 05:29 AM.
13th September 2014, 05:34 AM |#4  
UpInTheAir's Avatar
Senior Member
Flag Phuket, Thailand
Thanks Meter: 14,477
 
Donate to Me
More
You won't know of a sure fire way until (if) it's successfully done. ...

If you want to proceed, I can't help with that as I haven't played with the BL for a long time and don't want to give wrong or outdated info. Different devices use different ways.
As I said, I won't get involved with the BL at all (publically or PM).

I will try and compile that kernel for you though.
The Following User Says Thank You to UpInTheAir For This Useful Post: [ View ] Gift UpInTheAir Ad-Free
13th September 2014, 11:51 AM |#5  
UpInTheAir's Avatar
Senior Member
Flag Phuket, Thailand
Thanks Meter: 14,477
 
Donate to Me
More
PM sent:

kernel compiled
Code:
CONFIG_TARGET_LOCALE_USA=y
Fairly sure it won't do anytrhing, could only find threshold changes in source related to that config change.

Please be aware I haven't tested the kernel for boot. There is a CIFS patch I've implemented not in v1.5.

The "problem" could actually be on the hardware side. I've owned a I9100T and I9300T. I remember that modems on ther "T" models were optimised for 850 MHz 3G band. The only difference was (the software) modem, and some internal jumper (recalling fading memory here.....)

Ha, found a thread regarding the SGS3 jumper,......... http://forum.xda-developers.com/gala...t1688836/page2

My point is, that there could be hardware changes needed as well
Last edited by UpInTheAir; 13th September 2014 at 11:56 AM.
13th September 2014, 01:21 PM |#6  
edan1979's Avatar
Senior Member
Flag KL
Thanks Meter: 1,146
 
More
I cant do anything as well. its out of my league.
13th September 2014, 05:16 PM |#7  
Member
Thanks Meter: 9
 
More
This would be very useful, maybe US users raise some funds to pay for a test device for a recognized developer to see if this could be implemented?
However if it's a one-shot and the phone/tablet is permanently useless, than it might not be worth it.
15th September 2014, 06:13 AM |#8  
UpInTheAir's Avatar
Senior Member
Flag Phuket, Thailand
Thanks Meter: 14,477
 
Donate to Me
More
PIT
I created a PIT file for SM-T705 16GB through heimdall. Cannot for the life of me get firmware to flash with the PIT (re-partition enabled), checked the PIT with PIT Magic on Windows and seems OK, but then again, unfortunately I don't know a great deal about it. I tried with Odin 1.85, 3.07, 3.09. All setup is Ok because I can flash the firmware without.

There was a risk of hard brick,......... but I was "in the mood". That mood is changing again though .............
15th September 2014, 06:27 AM |#9  
OP Senior Member
Thanks Meter: 926
 
Donate to Me
More
Quote:
Originally Posted by edan1979

I cant do anything as well. its out of my league.

It's ok bro...thx for checking in

Quote:
Originally Posted by Satorikn

This would be very useful, maybe US users raise some funds to pay for a test device for a recognized developer to see if this could be implemented?
However if it's a one-shot and the phone/tablet is permanently useless, than it might not be worth it.

Although I would prefer not to I'm willing to risk a brick of my own personal device & just file an insurance claim if so...hopefully we will have a breakthrough before then

Quote:
Originally Posted by UpInTheAir

I created a PIT file for SM-T705 16GB through heimdall. Cannot for the life of me get firmware to flash with the PIT (re-partition enabled), checked the PIT with PIT Magic on Windows and seems OK, but then again, unfortunately I don't know a great deal about it. I tried with Odin 1.85, 3.07, 3.09. All setup is Ok because I can flash the firmware without.

There was a risk of hard brick,......... but I was "in the mood". That mood is changing again though .............

Could u PLEASE upload or pm me the pit file kind sir...don't know if u tried the custom kernel yourself but even though it was a no go I definitely appreciate the effort
@UpInTheAir
hate to waste a post so hopefully u will see this bat signal...which drivers/process did u use to get heimdall to even initiate the flashing process? I can get it too recognize the device fine but once I press start I have various errors depending upon which driver i choose in zdiag...starting to wonder if it's because I'm on x64 Windows 8 or what?
Last edited by THEDEVIOUS1; 15th September 2014 at 07:00 AM.
15th September 2014, 06:41 AM |#10  
UpInTheAir's Avatar
Senior Member
Flag Phuket, Thailand
Thanks Meter: 14,477
 
Donate to Me
More
Quote:
Originally Posted by THEDEVIOUS1

It's ok bro...thx for checking in

Although I would prefer not to I'm willing to risk a brick of my own original device & just file an insurance claim if so...hopefully we will have a breakthrough before then

Could u PLEASE upload or pm me the pit file kind sir...don't know if u tried the custom kernel yourself but of course it was a no go but I definitely appreciate the effort

This is the heimdall PIT printout:

Entry Count: 24
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21324
Unknown 4: 13641
Unknown 5: 12596
Unknown 6: 48
Unknown 7: 0
Unknown 8: 0


--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 2046
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename:


--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: -
FOTA Filename:


--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:


--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: -
FOTA Filename:


--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 16384
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA1
Flash Filename: -
FOTA Filename:


--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 24576
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:


--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 65536
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs1
Flash Filename: m9kefs1.bin
FOTA Filename:


--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 73728
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs2
Flash Filename: m9kefs2.bin
FOTA Filename:


--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 81920
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs3
Flash Filename: m9kefs3.bin
FOTA Filename:


--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 90112
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CARRIER
Flash Filename: carrier.img
FOTA Filename:


--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 98304
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename:


--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 114688
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:


--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 131072
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:


--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 151552
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename: -
FOTA Filename:


--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 172032
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CDMA-RADIO
Flash Filename: modem_cdma.bin
FOTA Filename:


--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 180224
Partition Block Count: 98304
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
FOTA Filename:


--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 278528
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TOMBSTONES
Flash Filename: tombstones.img
FOTA Filename:


--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 286720
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TDATA
Flash Filename: tdata.img
FOTA Filename:


--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 294912
Partition Block Count: 24576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSDATA
Flash Filename: persdata.img
FOTA Filename:


--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 319488
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RESERVED2
Flash Filename: -
FOTA Filename:


--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 18
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 327680
Partition Block Count: 4894720
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:


--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 19
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5222400
Partition Block Count: 409600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:


--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5632000
Partition Block Count: 471040
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:


--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 21
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 6103040
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img
FOTA Filename: remained


I'm just going to give it one last shot..........

Edit: Failed again, stuck at "get PIT for mapping" using 3.07.

PM sent
@THEDEVIOUS1

Installed heimdall on Ubuntu 14.04 64bit ..... Just for your PIT

I didn't actually try flashing anything through heimdall though. Never have (yet).

Kept getting an error eventually download the PIT with device connected to the PC USB 3.0 port. ..

Edit2: Tried to flash PIT with heimdall, but no go. "ERROR: Failed to receive PIT file part response!" , obviuosly something wrong with the PIT. I tried via DD and managed to pull some sort of PIT (doesn't flash), because the count= & BS= no idea where to obtain this info. I'm sure it's device specific
Last edited by UpInTheAir; 15th September 2014 at 08:00 AM.
The Following User Says Thank You to UpInTheAir For This Useful Post: [ View ] Gift UpInTheAir Ad-Free
28th October 2014, 09:34 PM |#11  
jadid's Avatar
Member
Seattle, WA
Thanks Meter: 8
 
Donate to Me
More
Tester
I will test this tonight when I get home and report back.
Question: What are my chances I will have a successful flash? This may be an obvious question, but assume I will need to root my device first, right?

Device Model: SM-T705
Baseband version: T705ZHU1ANG2
Kernel version: 3.4.39-2290729 dpi@SWDD5823 #1
Build number: KOT49H T705ZHU1ANG2

Read More
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes