Related
Introduction:
See: Dell Streak 7: Partition Layout
The Streak 7 stores it's device specific data in partitions WP1 and WP2, which are partitions 23 and 24 respectively.
Due to the overzealous and blind use of NVflash, many Streak 7 users have overwritten their device specific data, this guide will document it's layout so you can regenerate some of the values stored in it.
You should NEVER modify WP1 and WP2 under normal usage, only partitions 2-21 should be modified, even then it is good practice to avoid modifying anything but the relevent partitions.
Requirements:
A Streak 7
A template p23.img and p24.img
Ability to use a hex editor
Understanding of hexadecimal addresses
Understanding of how to use NVflash
As stated: this is a TECHINCAL GUIDE, if you do not understand how to use a hex editor and NVflash without relying on batch scripts, THIS GUIDE IS NOT FOR YOU.
WP1 Layout:
Code:
0x85 - 0x91: Unknown version number
0x92 - 0x103: Picasso Number
0x521 - 0x543: PPID
0x548 - 0x554: Service tag
0x559 - 0x573: IMEI
WP2 Layout:
Code:
0x0 - 0x11: Wifi MAC address
0x16 - 0x27: Bluetooth MAC address
Values:
Unknown version number - self-explanitory [Cannot be regenerated]
Picasso number - use unknown, viewable in fastboot mode on 50x roms [Cannot be regenerated]
PPID - self-explanitory [Listed on flap]
Service tag - self-explanitory [Listed on flap]
IMEI - self-explanitory [Listed on flap]
Wifi MAC address - self-explanitory [Cannot be regenerated]
BT MAC address - self-explanitory [Cannot be regenerated]
Notes:
INTENTIONALLY CHANGING YOUR IMEI IS ILLEGAL, DO NOT CHANGE IT UNLESS YOU ARE ATTEMPTING TO FIX IT
INTENTIONALLY CHANGING YOUR SERVICE TAG CAN BE CONSIDERED WARENTEE FRAUD
If you do not fully understand this guide you are not the target audience for it, this guide is for able users to repair other's devices.
Good info
I am new to this device and have found flashing ROMs can really cause issue in the areas you described. I changed the service tag on ln220/pg23 but did not know about the other issues. I have checked the flap on my device and don't seem to see any IMEI number. Appreciate you sharing your knowledge. Could you explain a little more on this? I want to make the changes and reflash stock 2.2.2 for now. I got the box from Dell this week to send it back but I had rather not. Thanks
If your service tags are still correct, dont ever flash p23/p24 unless it is the one dumped from your own device.
Is your a tmo one, and the imei isnt on the flap? I was only assuming it's on the flap, i havnt actually been able to compare the flaps from US4Gs and wifis
TheManii said:
If your service tags are still correct, dont ever flash p23/p24 unless it is the one dumped from your own device.
Is your a tmo one, and the imei isnt on the flap? I was only assuming it's on the flap, i havnt actually been able to compare the flaps from US4Gs and wifis
Click to expand...
Click to collapse
I have the USTMO 4g, and the asset tag is on the flap - it is very small.
flap info
Mine is a US wi-fi only bought at Staples. If you refer to an earlier post, I scewded the pooch when trying to manually install HC and wiped the memory with CWM. I flashed a TMO rom thinking it was the right one, later found the correct stock ROM and flashed it. I had never read anywhere about the information you provided about pg23/24. The only thing on my flap is the ppid (which is wrong on my ROM flash), service tag, some kind of E service number, model number, type, and fcc id that starts with an E. The later three are not on a white background like the others. There is also some sort of barcode. There is a thread about service tags being wrong after flashing, so I changed it using HxD. I would like to get the other entries fixed as well. I'm just a noob, but I ain't scared to try!
Like on the post, the Service tag, IMEI and PPID are the only ones that can be regenerated as they're the only ones written down somewhere.
They're both written on that flap and on the retail box (as each box has that devices's unique info on the sticker.
The e service number isnt ever listed in p23/24, nor is the serial number ever listed on the flap/box.
The only reason some values cant be regenerated is because they were simply never written down anywhere, if you did in fact have the MAC addresses written down along with the other values, you could just plug them back in.
For P24 the only unique data is the mac addresses, the rest of the partition seems to be bit identical across all devices.
P23 is the main one, on top of the plaintext values, there's a couple fields in binary that are no zeroed, and are unique across devices. I havnt even listed those since I have absolutely no idea what they do/contain.
Without knowing how dell generates them in the first place you will never be able to fully regenerate them, the only right way would be to back up your originals and not ever update P23/24.
-----------------------------
Could you take a clear picture of your flap (or anyone that's on a 3/4g model), I only assumed the IMEI is there as the wifi ones seem to have a blank space on the label where you might be able to squeeze in the IMEI tag.
It SHOULD also be on your retail box as the IEMI on a barcode is usually how stores identify them when selling them.
I will check my box when I get home in a day or so, will also get a pic of the flap.
You also might be able to get your mac address from your wireless router. I know my netgear shows the mac of the devices connected to the dhcp server.
box pic
This is a pic of the box info. It is of course the same as on the flap. The fcc id shown here is the only item on the flap that is not printed on a white background.
If I am not mistaken, MAC adresses on the router are picked up from the connected device. So if the MAC address on pg24 is wrong the router just picks it up. The only way to find your correct address would be if you had some sort of router history file of devices that had connected and you had connected before you flashed a new ROM. I am definatly not an expert.
I have found the correct line to adjust for the ppid number but what about the imei number? If I send this back to Dell they could do a complete restore but they could see that I flashed and cancel me out, even though I told the tech I talked to that I flashed in an attempt to get running again. I had rather just fix it myself.
BTW, if it is not, then the original post on this thread should be stickied as mandatory reading before you flash. I thought I had read everything.
You stated yours is a wifi model, so I dont even know why wifi ones have an imei stored in them, obviously it isnt actually used by the device since there's no modem (or is there? noone's ever taken apart a wifi s7 and checked the slot)
The mac: yes if your router has it's history, if it doesnt for any reason you're SOL.
The imei on wifi ones prob isnt checked at all unless something like the service tag looks wrong and they examine the entirety of p23. I would imagine they have factory tools that can pharse it and not simply look at it in a hex editor
The PPID is also device specific, but it's contents are partially unknown, it's
PPID: CN-<product number>-<unknown 5>-<unknown 3>-<unknown 4>-A00
The 3 unknown fields might be related to something, they might be serial numbers.
74261 is a common value for us wifis,
one of the ones I have a ppid from differs from yours by only the last 2 digits in unknown 4.
Getting entire historys of devices might provide more clues on generating the PPID (yes looking at the box will give you it, but I would be interested in knowing what it contains)
I still need shots from a 3/4G one, i assume their boxes/flaps list the imei (as the previous poster suggested that they did)
Thanks for the post, excellent. I have restored to stock following one of the other posts here & have the issue with Tag No. etc changing, so now I can sort it hopefully.
One question though, I noticed my Bluetooth Mac address is sequential to the wireless MAC address. Can others confirm this is the case on their devices, as I have found the Wireless MAc from my router history. If they are sequential it means the Bluetooth MAC can be sorted as well.
For the s5 and apparently on the s7, the bt mac is the next hex digit after the wifi one, so if you have the wifi one just increment by one
Glad you found your router history. I looked all through my Linksys router pages and can find nothing.
more info on the subject
I am continuing to learn more on this subject. I found that in My Phone Explorer you can find the IMEI number along with a link that tells you exactly what it is. I wrote down the number as it was displayed and opened up the PG23 files and could not find anything that comes close to matching it. The correct lines show only 15 digits whereas the number shown in My phone Explorere is 16 digits. As my unit is a wi-fi only one I wonder if it needs an IMEI number at all. I opened PG24 and found that my bluetooth and wi-fi MAC addresses are the same. I was curious to see what the Tmo ROM I flashed contained and opend it. I was suprised to see that it ended with PG22. So I now know that I had all my information correct after I flashed that ROM and lost it after flashing the "original" ROM. As the OP stated, never flash PG23,24.
new info
I changed the ppid and reflashed, just to try and get it back completly stock. When I connected to My Phone Explorer to sync, a new relationship had to be established. When I looked at the status, the IMEI number had changed and I think also the MAC address also but not sure. So these numbers must somehow be related. When you compare the ppid and the IMEI they are different numbers completely but changing the ppid on PG23 results in a change of the IMEI number.
ok so i got a galaxy tab from this guy on craigs list its been rooted and has the uk software with the phone app (model#gt-p1000) firmware 2.3.3, kernel version(2.6.35.7 [email protected]#2) build # gingerbread xxjq1) ok so anyway i put in my tmobile sim card from my android cliq and i can sen text messages im registered on the network getting 3g and the h network but no web and no calls???? help please
oh and ive tried like 3 different apns from epc.tmobile.com and also wap.voicestream.com and internet2 and 3 voicestream lol the only difference is i get the edge network instead of 3g like on epc???????
bump bump bump bump
It's hard to say without knowing exactly what he did to it.
computers are complicated and a tablet is basicly a computer with a phone in it. he could have messed up a modual and decided to get out from under it. because once you start rooting and putting whatever you want on it, it's basicly yours and your warrenty is over. best way is to restore it back to the factory version and start over from there. this way you can tell if it's a software problem or hardware. it's just like building and modding your own computer.
Hi Everyone,
I'm not sure how to try this out, since I'm not in the US, and that RadioComm doesn't work for my Droid 4 (it's been upgraded to ICS)
1) Install latest Motorola drivers and RadioComm
2) Launch RadioComm
3) When it RadioComm launches, Click Main -> MA -> Common -> MDM 6x00
4) Click Settings -> USB -> PST USB
5) Click on FTM Common 1
6) Connect the phone to the PC and wait for it to go green
7) Under NVAccess, find the following values:
4870, NV_GSM_850_CARRIER_SUPPRESSION_I
4871, NV_GSM_DCS_CARRIER_SUPPRESSION_I
4872, NV_GSM_1900_CARRIER_SUPPRESSION_I
8) For each value, press Read, then replace all of the numbers with 0. Once done, press write. Repeat for all 3 values/
Let me know if this works!
Again, I mentioned a problem with RadioComm. I'm using Windows 8 x64, RadioComm worked fine with my Bionic on GB, maybe it's an ICS thing, maybe I need newer drivers, etc... Please let me know if this works!
I was able to get this going on my Droid Bionic (which also had a corrupted IMEI number) so if you want to see that post, view it here :
http://forum.xda-developers.com/showpost.php?p=32256347&postcount=780
danifunker said:
Hi Everyone,
I'm not sure how to try this out, since I'm not in the US, and that RadioComm doesn't work for my Droid 4 (it's been upgraded to ICS)
1) Install latest Motorola drivers and RadioComm
2) Launch RadioComm
3) When it RadioComm launches, Click Main -> MA -> Common -> MDM 6x00
4) Click Settings -> USB -> PST USB
5) Click on FTM Common 1
6) Connect the phone to the PC and wait for it to go green
7) Under NVAccess, find the following values:
4870, NV_GSM_850_CARRIER_SUPPRESSION_I
4871, NV_GSM_DCS_CARRIER_SUPPRESSION_I
4872, NV_GSM_1900_CARRIER_SUPPRESSION_I
8) For each value, press Read, then replace all of the numbers with 0. Once done, press write. Repeat for all 3 values/
Let me know if this works!
Again, I mentioned a problem with RadioComm. I'm using Windows 8 x64, RadioComm worked fine with my Bionic on GB, maybe it's an ICS thing, maybe I need newer drivers, etc... Please let me know if this works!
I was able to get this going on my Droid Bionic (which also had a corrupted IMEI number) so if you want to see that post, view it here :
http://forum.xda-developers.com/showpost.php?p=32256347&postcount=780
Click to expand...
Click to collapse
This looks awesome -- I saw your post in the Bionic forum. I was curious if this worked for anyone in the states on T-Mobile? I was looking to get a Droid 4 and use it on Straight Talk. Currently have an Epic, but loved my OG Droid. 3G is fine enough for me -- just curious if anyone is also able to get MMS working as well, along with APN settings?
What version of RadioComm do you recommend? I've tried 11.9.0 and I get the error when I try to open it:
"Error in getting the pointer to CommP2K and/or CommQC. Error number: Exception of type 'System.Exception' was thrown."
If you can help me get past this error, I'd love to try this out...
terinfire said:
What version of RadioComm do you recommend? I've tried 11.9.0 and I get the error when I try to open it:
"Error in getting the pointer to CommP2K and/or CommQC. Error number: Exception of type 'System.Exception' was thrown."
If you can help me get past this error, I'd love to try this out...
Click to expand...
Click to collapse
I'm using 11.12.2, and try to get the latest motorola phone drivers (different than the USB drivers) I think I'm running 5.9 of those.
Sent from my XT894 running ICS
danifunker said:
I'm using 11.12.2, and try to get the latest motorola phone drivers (different than the USB drivers) I think I'm running 5.9 of those.
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Awesome, I'll give it a shot when I get home. Out of curiosity -- I'm assuming this is similar to QPST. If I bork the modem, I should be able to go back to a prior group of settings, right?
SIM Card should be coming in on Saturday or Monday -- so should be able to get some news to everyone by then.
terinfire said:
Awesome, I'll give it a shot when I get home. Out of curiosity -- I'm assuming this is similar to QPST. If I bork the modem, I should be able to go back to a prior group of settings, right?
SIM Card should be coming in on Saturday or Monday -- so should be able to get some news to everyone by then.
Click to expand...
Click to collapse
Cool, just to give you a heads up, someone tried it in the RAZR forum without success....
Sent from my XT894 running ICS
Shoot. I've read that you can get 3G on AT&T without any problems across forums -- did I misread and this was for international use -- not inside the US? I just want to get 3G on AT&T if possible...
Any thoughts? Or can you point me in the right direction?
terinfire said:
Shoot. I've read that you can get 3G on AT&T without any problems across forums -- did I misread and this was for international use -- not inside the US? I just want to get 3G on AT&T if possible...
Any thoughts? Or can you point me in the right direction?
Click to expand...
Click to collapse
Still trying to figure it out... I don't think we have a solution just yet.
I'm a developer outside of all of this (C# primarily these days, but have an extensive background in C/C++) -- and I've flashed phones to cricket with QPST -- so maybe I can help you guys out with this. If you're up for discussing any background that might catch me up to speed on this (already have my phone), would be up for trying to help break into it and enable this. Just send me a PM if you're up for this. Thank you!
Hey all,
I've only used this program for a little bit but I was able to change the values to what the OP suggested however, I used the Motorola Factory USB cable. I couldn't get the program to recognize my phone w/o it.
I'm using stock rooted ICS too.
Sent from my DROID4 using Tapatalk 2
So, you updated it with that -- were you successful and does GSM now work in the US?
Did anything change?
Phone doesn't make calls now
I followed the steps above
Radio Comm v11.12.2
Motorola drivers 2.2.28
Whatever data card drivers came with radiocomm
This did not allow me to see t-mobile or at&t here in the states.
So, random question/thought... If we find another modem with similar chip in another phone -- say on AT&T -- would we be able to read some of these fields and stuff out -- and then push it into our modem?
it would be great if we can set the phone to just swap SIM cards very easily, especially in the US
terinfire said:
So, random question/thought... If we find another modem with similar chip in another phone -- say on AT&T -- would we be able to read some of these fields and stuff out -- and then push it into our modem?
Click to expand...
Click to collapse
Hmm, might be an idea. I don't think that there were many AT&T phones with this capability though. My idea is to compare an XT910 vs an XT912, since that was a worldwide release.
Best idea, get an XT910, put your SIM into it, grab a full radio dump, then put your SIM into the XT912 that doesn't work and grab another full radio dump and compare the two.
You'd need an internation XT910, since AT&T didn't ship them down there, but that would be a great starting place...
danifunker said:
Hmm, might be an idea. I don't think that there were many AT&T phones with this capability though. My idea is to compare an XT910 vs an XT912, since that was a worldwide release.
Best idea, get an XT910, put your SIM into it, grab a full radio dump, then put your SIM into the XT912 that doesn't work and grab another full radio dump and compare the two.
You'd need an internation XT910, since AT&T didn't ship them down there, but that would be a great starting place...
Click to expand...
Click to collapse
Only thing is that I'd have to go out of my way to do that and spend even more money. I just dropped some on the Droid 4 for an off-contract phone. I wonder if there's any way we could ping some of the other forums, i.e. the Razr and see if anyone can potentially get us full-reads, so that way we could compare/diff them?
In addition -- I wonder if it's possible (probably a long-shot) to potentially order a SIM card or something from another carrier in Europe or somewhere outside the US and get it into the phone, but then have it "added" or "roaming" on a US network or something -- if that might provide a workaround?
Just trying to take stabs at it. I figure I'll hold onto the D4 for another month and see if we have any exciting developments -- and if not -- just push it to Swappa.
So i could use this to unlock the radio for overseas teleco use?
remiqaine said:
So i could use this to unlock the radio for overseas teleco use?
Click to expand...
Click to collapse
D4 already has unlocked radio for most telecoms overseas.
terinfire said:
Only thing is that I'd have to go out of my way to do that and spend even more money. I just dropped some on the Droid 4 for an off-contract phone. I wonder if there's any way we could ping some of the other forums, i.e. the Razr and see if anyone can potentially get us full-reads, so that way we could compare/diff them?
In addition -- I wonder if it's possible (probably a long-shot) to potentially order a SIM card or something from another carrier in Europe or somewhere outside the US and get it into the phone, but then have it "added" or "roaming" on a US network or something -- if that might provide a workaround?
Just trying to take stabs at it. I figure I'll hold onto the D4 for another month and see if we have any exciting developments -- and if not -- just push it to Swappa.
Click to expand...
Click to collapse
Not sure what you a proposing in your second paragraph. I have a UK SIM card, and when I plug it in two other phones (Samsung Renown, a CMDA/GSM basic phone) and a Motorola quad-band GSM phone, it works fine in the US. When I move the SIM into my Droid 4, no signal, although it sometimes gives the Unrecognized SIM message. So it's not a matter of non-US sims.
silver6054 said:
Not sure what you a proposing in your second paragraph. I have a UK SIM card, and when I plug it in two other phones (Samsung Renown, a CMDA/GSM basic phone) and a Motorola quad-band GSM phone, it works fine in the US. When I move the SIM into my Droid 4, no signal, although it sometimes gives the Unrecognized SIM message. So it's not a matter of non-US sims.
Click to expand...
Click to collapse
I get the unrecognized SIM message also. That doesn't affect the phone one bit though, since I just press okay to the message and the phone connects to my carrier. Is your carrier one with a Verizon roaming agreement?
Sent from my XT894 running ICS
Hi All,
I got the ATIV SE and really like it. Problem is that even though it's unlocked SIM and I have also developer unlocked it, I cannot get internet sharing to turn on. I bought from Verizon, but am using it on T-Mobile. Error is:
To enable tethering on this device, go to Verizon.com or dial *611
What is the best way to get this phone to forget about Verizon? Is there a way to just factory reset to vanilla windows?
Thanks for help
fruehling said:
Hi All,
I got the ATIV SE and really like it. Problem is that even though it's unlocked SIM and I have also developer unlocked it, I cannot get internet sharing to turn on. I bought from Verizon, but am using it on T-Mobile. Error is:
To enable tethering on this device, go to Verizon.com or dial *611
What is the best way to get this phone to forget about Verizon? Is there a way to just factory reset to vanilla windows?
Thanks for help
Click to expand...
Click to collapse
I'm not sure but could it be possible that your carrier lock Tethering?
Have you tried an oter csc?
Or can you flash an other ROM`?
Thanks for the reply. No, carrier does not lock. The problem is with the phone being set up to think it's a Verizon phone. Is there a way to flash another rom here? or something like root?
We can interop-unlock Samsung WP8 phones, although if it's fully up-to-date it may need to be downgraded first. I don't know if that will help you, though. I can't tether (well, not over WiFi; wired works) my non-T-Mobile phone on TMo either.
There won't be another CSC to flash... Unless you can get @-W_O_L_F- to help you out with a custom rom....
GoodDayToDie said:
We can interop-unlock Samsung WP8 phones, although if it's fully up-to-date it may need to be downgraded first. I don't know if that will help you, though. I can't tether (well, not over WiFi; wired works) my non-T-Mobile phone on TMo either.
Click to expand...
Click to collapse
Sorry for the slow reply. I didn't get notified by this site that there was a reply to my post.
Can you please help me out with how to do this with ATIV SE?
Interop-unlock instructions are in my signature. I don't know if they'll help you though, and if you're on GDR3 (probable) then you'll need to downgrade first (or use a custom ROM) and for that you need to read @-W_O_L_F-'s threads. I don't know if there's a base ROM (non-Verizon) for the SE; if there is you can probably flash that but we may not have one.
If you wanted to know how to do wired tethering, just search for "tether ATIV S". Seriously, #1 rule of this forum is literally "search before posting"
GoodDayToDie said:
Interop-unlock instructions are in my signature. I don't know if they'll help you though, and if you're on GDR3 (probable) then you'll need to downgrade first (or use a custom ROM) and for that you need to read @-W_O_L_F-'s threads. I don't know if there's a base ROM (non-Verizon) for the SE; if there is you can probably flash that but we may not have one.
If you wanted to know how to do wired tethering, just search for "tether ATIV S". Seriously, #1 rule of this forum is literally "search before posting"
Click to expand...
Click to collapse
Seriously, thank you for the reply. I did lots of searching, but since ATIV S and SE are quite different, I wasn't sure if anything related to S would work.
I'd love to flash an SE base ROM on this, but I haven't been able to find that there is one.
The MS Store in Bellevue said that they would be getting a Samsung base ROM in a couple months that they would flash onto my device for me. But I'd like to do this sooner.
Should I reach out and read wolf's threads to see about using a custom ROM here then?
Thanks!
fruehling said:
Hi All,
I got the ATIV SE and really like it. Problem is that even though it's unlocked SIM and I have also developer unlocked it, I cannot get internet sharing to turn on. I bought from Verizon, but am using it on T-Mobile. Error is:
To enable tethering on this device, go to Verizon.com or dial *611
What is the best way to get this phone to forget about Verizon? Is there a way to just factory reset to vanilla windows?
Thanks for help
Click to expand...
Click to collapse
Try a variation on the following method:
http://forum.xda-developers.com/showpost.php?p=52490701&postcount=5
Worked for the HTC 8x, should work for Samsung as long as you can put in the right model ID. (hint: it's not "dm=Windows%20Phone%208X%20by%20HTC" for your Samsung.) Good luck!
compu829 said:
Try a variation on the following method:
http://forum.xda-developers.com/showpost.php?p=52490701&postcount=5
Worked for the HTC 8x, should work for Samsung as long as you can put in the right model ID. (hint: it's not "dm=Windows%20Phone%208X%20by%20HTC" for your Samsung.) Good luck!
Click to expand...
Click to collapse
Thanks for that! The process worked and got me almost there.
Ok! Super progress here. This is what you need to add for the Samsung ATIV SE
// Replace oemId=Samsung with oemId=NOKIA
oSession.PathAndQuery = oSession.PathAndQuery.Replace ("oemId=SAMSUNG", "oemId=NOKIA");
// Replace the device model with the dm for the Nokia 925 (AT&T / North America):
oSession.PathAndQuery = oSession.PathAndQuery.Replace ("dm=ATIV%20SE", "dm=RM-893_nam_att_206");
Note the CAPS for the oemId.
I installed Access Point (along with some other cool Nokia Apps). I went to enable Internet Sharing, but now I have a new message:
Add Internet sharing?
"Your current data plan doesn't include Internet Sharing (it does). Do you want to open an app from your mobile operator to add it? Internet sharing use your cellular data and may incur additional charges."
Any ideas where to go from here? Clicking Yes does nothing. So does clicking no.
fruehling said:
Thanks for that! The process worked and got me almost there.
Ok! Super progress here. This is what you need to add for the Samsung ATIV SE
// Replace oemId=Samsung with oemId=NOKIA
oSession.PathAndQuery = oSession.PathAndQuery.Replace ("oemId=SAMSUNG", "oemId=NOKIA");
// Replace the device model with the dm for the Nokia 925 (AT&T / North America):
oSession.PathAndQuery = oSession.PathAndQuery.Replace ("dm=ATIV%20SE", "dm=RM-893_nam_att_206");
Note the CAPS for the oemId.
I installed Access Point (along with some other cool Nokia Apps). I went to enable Internet Sharing, but now I have a new message:
Add Internet sharing?
"Your current data plan doesn't include Internet Sharing (it does). Do you want to open an app from your mobile operator to add it? Internet sharing use your cellular data and may incur additional charges."
Any ideas where to go from here? Clicking Yes does nothing. So does clicking no.
Click to expand...
Click to collapse
At this point, I'd call T-Mobile and see if they can double-check everything on their end. They might need to reprovision your data services. I had a similar issue with my old iPhone when I added the 500MB tethering option.
They do have an "access point" app (I forget what it is called) that comes pre-installed on their phones. (Literally useless, it is so when you click Yes on the "learn more" button" it tells you to call customer care to enable internet sharing. I always delete it off of mine when I restore from stock).
That is another fun trick: to get rid of apps you can't uninstall, set the date and time on your phone to later than 2200 and click on the app...it will tell you that it expired and give you the option to uninstall it!
Let me know how you make out!
fruehling,
Did you ever get this solved? I'm planning on getting this phone too, but for use on At&t. I hope I don't run into the same problem. But I do have some questions to ask you, I hope you don't mind answering....1) Does the voice call works as any unlocked phone? .... 2) Can T-Mobile detect that you're using an ATIV SE? Or does T-Mobile says you have an Unknown device when you check your online account? Thanks!
fruehling said:
Thanks for that! The process worked and got me almost there.
Ok! Super progress here. This is what you need to add for the Samsung ATIV SE
// Replace oemId=Samsung with oemId=NOKIA
oSession.PathAndQuery = oSession.PathAndQuery.Replace ("oemId=SAMSUNG", "oemId=NOKIA");
// Replace the device model with the dm for the Nokia 925 (AT&T / North America):
oSession.PathAndQuery = oSession.PathAndQuery.Replace ("dm=ATIV%20SE", "dm=RM-893_nam_att_206");
Note the CAPS for the oemId.
I installed Access Point (along with some other cool Nokia Apps). I went to enable Internet Sharing, but now I have a new message:
Add Internet sharing?
"Your current data plan doesn't include Internet Sharing (it does). Do you want to open an app from your mobile operator to add it? Internet sharing use your cellular data and may incur additional charges."
Any ideas where to go from here? Clicking Yes does nothing. So does clicking no.
Click to expand...
Click to collapse
If you are in Dev Preview.. try the foreign sim trick
if not just install a new keyboard.
I followed the procedure outlined, and using SysAppPusher, it attemped to install "access point" under Microsoft mobile (not Lumia), and from the store, the status changed to "owned". But it didn't actually install it.
I turned off the proxy (as it was recommended) and it still didn't install it. Any idea as to what could be wrong?
I'm on the latest 8.1 release.
I am contemplating purchase of one of these phones, and tried entering some of their IMEI numbers in the imei checker at https://www.t-mobile.com/resources/bring-your-own-phone , and was shocked to find they are ALL described as "Incompatible".
This is a bit confusing after the articles saying the AT&T and Verizon versions would not work after Jan 2021 but that the T-Mobile version would continue working. I tried looking for a later article saying that support for the T-Mobile version this model was being cancelled but could not find any such announcement.
Is that IMEI checker correct? Or is it because the samples I checked may not have gotten the last modem update installed from T-Mobile?
Is anyone still using this phone (specifically the T variant) on T-Mobile in USA? I'm assuming that last update will be important, but does this still work once it is installed?
If yes to the above, do phone calls work as VoLTE, or is it doing the fallback to 2G?
I've also seen threads about enabling more LTE bands, has anyone done that on this phone? In particular is it possible to add support for B71 (600MHz), or is this radio hardware just too old to allow that?
Thanks much, I would really like to know whether I can use this phone or if I would need to find a different model.
https://swappa.com/blog/3g-network-shutdown/ Your phone is fine.
SM-N910T with 2ETI1 OTA modem update works fine. 4g/LTE Data, WiFi Calling works. Does not drop out of 4G/LTE for voice. SM-N910V w/ MODestROM v11 (6.01 TW-based N910VVRU2CQI2 ) w/ a vzw 2CTI baseband update, has working 4gLTE data, but no WiFi Calling, or VoLTE (falls back to 2g, but I still have 2g coverage here, so it's usable, if not optimum. Here's the thing: on the VZW phone, if I set the the salescode to TMB, suddenly VoLTE works, but the Setup pages/menus/statusbar are screwed up, so it's not really useable. Here's where it gets REAL interesteing. On a VZW phone w/ VZW 2CTI1 baseband, & VZW BL, flashed with a custom TMB ROM (trltetmo_N910TUVU2EQI2_Stock_Deodexed, debloated, but still TW), EVERYTHING works. But it's not stable, it periodically loses 4g/lte. What it tells me is that the VZW h/w is NOT THE PROBLEM. I've been at this all day, everyday since VZW turned off CDMA on 01/01/23 and killed my service here. Be warned: If you go down this path, you're gonna be mostly on your own. A LOT of dead links, 'retired' devs, etc. Everyone except you, me, and three other people here have long since moved on from this awesome phone. I'll help you if I can. I bought an SM-N910T , but the damn usb port is dead. Already changed the charging board, not the problem. It's the mobo. If I could identify the usb chip (if it's not the 805 itself, I'd change it. So I have a phone with no adb that I can't unlock/root. I'd much rather get my VZW phone fully working on TMB, since I'm heavily invested in the MODestROM. Haven't given up yet. But search my posts, you'll hear the deafening silence, lol.
Seeing this forum has so little activity, on 1/21 I ended up getting a used Moto E6 (XT-2005-3 is a tmobile aka carrier unlocked MetroPCS version). While overall this is not as nice a device and has fewer features than Note 4, it does cover what for me are the essentials - removable battery, SD card slot, support for 5.8GHz wifi. Best of all, it supports B71 which will be helpful for, well, making phone calls!
I still ponder someday getting one of these as a hobby device, but that would be second place to the E6 for use as a phone, and won't be for a couple more months yet (too many expensive household issues are taking their toll on my "toy" budget right now).
ForestCat said:
SM-N910T with 2ETI1 OTA modem update works fine. 4g/LTE Data, WiFi Calling works. Does not drop out of 4G/LTE for voice.
Click to expand...
Click to collapse
Thank you, this was the part I needed to find out. With that in place, the only thing missing would be the B71 coverage but the E6 is already in place for that.
Re your Verizon adventures, I have no experience with any of that. What I read about T-Mobile dropping support for the verizon version in the last network update is all I know, and I don't have the skills to dispute what they say there. The best I could do is offer some links to threads on this forum but on double checking them it seems you've already been there and got no answers.
The only thing I see that might help you with that is if you could update just the t-mobile modem without disturbing the verizon bootloader. I see you tried that but it didn't stick when using Odin. I don't know if it would be any different using SmartSwitch that seemed to work for MarineWonder as he posted at https://forum.xda-developers.com/t/...pgrade-on-jan-29th-2021.4224237/post-87464609 ?
Then again he may have been putting it on a t-mobile phone rather than mixing with the verizon bootloader so who knows?
My guess since it has been so problematic for you on the verizon phone is that you may need to only use a tmobile phone since that may be the only way to get the last t-mobile modem update. Bummer that the one you bought has a dead usb port. How are you charging it? Is there any chance you could return it to the seller since it came pre-broken? Then put the refund money toward another, hopefully working, tmobile phone? And would that MODestROM work on a non-verizon phone?
The only other thought I had is there are apps to connect to ADB over wifi. Sadly most of these need root. The ones that don't, seem to need at least once using a usb connection to do the "adb tcpip 5555" command to set it all up. . . . how annoying that it is all so circular!
There is also https://telnetd.en.aptoide.com/app?store_name=apps&app_id=59202144 , maybe a telnet connection could do the "adb tcpip 5555" command instead of using the USB connection? Sadly the documentation (at https://waxrain.com/docs/010.html ) appears to be written in Chinese, and I never had much luck with google translate.
The N910T still supports VoLte.. It is still compatible with cellular networks.