Database Develop

[Q] Unlocking DS7

Ok, so I work for this company that is mass selling these DS7... We have all types of the models come in, and I'm trying to figure out which ones can be upgraded to Honeycomb 3.2...
I know that the WiFi unbranded model can receive the OTA update, but the T-mobile WiFi is unable to receive it.
As far as I can tell none of the 3G models can receive the Honeycomb update. I have been reading around these forums today, and found out that (correct me if I'm wrong) carrier unlocked 3G models can be get the OTA Honeycomb update.
I have been looking at this software to carrier unlock the DS7 (Dell Streak Unlocker ), but don't know if it a one-time-use device specific unlock, or if I could use it to unlock many devices.
I know there is a lot of information provided here hidden in these forums, but I am at work, and I cannot spend all day looking for answers. If someone could just help me out I would greatly appreciate it.

If you're running into multiple S7's, could you report what roms are installed on them?
To find your rom version:
Go to settings -> about tablet
List the following:
OEM Version: GLUNB1Axyyyzz
X is your hardware model:
(note that this isnt consistant below 340)
1: US 4g
2: EU 3g
3: Wifi
yyy is your rom version
zz is your region
Build number:
Baseband ver:
(if applicable)
Dell Streak 7 Official roms - XDA wiki
Dell Update Process - XDA wiki
You're likely going to run into a couple that I dont already know about,
I would like to ask if you could make nvflash dumps of them, but I'll settle for just rom info if you can do that much.
General breakdown:
From a hardware perspective: all S7's can be upgraded, they're all more or less identical internally (bar the modems)
From a software perspective, Tmo ones and wifi ones below 340 cannot be officially updated.
The unlocker software likely is one time use/per code.
I cant say it actually is because I've never tried, but it strongly sounds like it would be.

First of series
I don't know how to perform a nvflash dump, but I can provide the system information. I will be posting different systems as I come across them. If there is a guide that you can point me to that shows how to get the nvflash dump I would be happy to gather that data for ya.
#1 DS7 T-mobile branded 3G (android version 2.2.2)
OEM - GLUNB1A133633
Build - 15420
Baseband - 11.810.09.06.00

#2 DS7 T-mobile branded 3G (android version 3.2)
OEM - GLUNB1A151230
Build - 20031
Baseband - 11.810.09.06.00

[Q] Interop unlock on SGH-t899m

I have a Samsung SGH-t899m that is on the Telus network at the moment. I need to get it interop unlocked so I can add the registry tweaks needed to see the full filesystem.
Can this device be interop unlocked in the manner of the others that I have seen?
Is there anywhere I can buy a device that already has interop unlock and full filesystem access?
Thanks,
Kevin

The original WP8 interop-unlock hack was developed on a phone exactly like yours, as it happens! However, it doesn't work if your phone has the firmware version that normally comes with GDR3, or if it has any version of WP8.1
However, -W_O_L_F- has produced some fake carrier customizations (part of a ROM, but not a full custom ROM) that can be flashed to such phones, and will do the interop-unlock for you. It's pretty straightforward. Check the Dev&Hacking subforum for threads about custom ROMs or CSCs or MBNs.

Thanks for the help everyone!
So it turns out I had to buy a sim card so I could get access to the dialer to get the Diagnosis app unhidden. Fortunately, it looks like my phone has GDR2 and is carrier unlocked already. Yay!
Now if I can just figure out how to get all capabilities so I can install the native webserver all capabilities version.
GoodDayToDie said:
The original WP8 interop-unlock hack was developed on a phone exactly like yours, as it happens! However, it doesn't work if your phone has the firmware version that normally comes with GDR3, or if it has any version of WP8.1
However, -W_O_L_F- has produced some fake carrier customizations (part of a ROM, but not a full custom ROM) that can be flashed to such phones, and will do the interop-unlock for you. It's pretty straightforward. Check the Dev&Hacking subforum for threads about custom ROMs or CSCs or MBNs.
Click to expand...
Click to collapse

If you're using an interop-unlocked Samsung on WP8.0, just run the standard process in the interop-unlocks thread; it's not too complicated. Install an app, run it, install another, run it too.

already on 8.1.xx.xxx
I have the SGH T899M and already went into 8.1.xxx.xx.
Reg edit and hidden diagnosis menu have since been removed after gdr3 I believe, this we know already. I have also purchased the developer account and have dev unlocked this phone to allow use of deployment.
However we cannot have full app capabilities with just a dev account. Is there any safe rom to downgrade to be able to make use of reg edit , interlop and gain full app rights? I am sorry if this has been covered somewhere else but I have been searching everywhere for this info before I made my post here.

Nexus 6 - T-Mobile - Not connecting to LTE

I just got my wife a Nexus 6 from Craigslist. I foolishly didn't 100% test the phone and I think I got a lemon or something.
Her phone has never connected to LTE. I've tried manually changing APNs, swapping SIM cards with my phone to see if the card is bad, checking the phone settings by dialing *#*#4636#*#*, etc... And everything is identical to my Nexus 6 with no luck. I went to a T-Mobile store just now and they couldn't figure anything out.
Two questions:
1. Is there anything else I can do to get LTE activated?
2. Can an LTE radio be damaged or disabled somehow?
I'm at my wit's end here... I'm hoping y'all can help me get it fixed.
Thanks!

1st is the phone running stock or a custom rom? .second try to reset your apn setting to default and using the setting that the phone provides in apn

It is stock, no customization or rooting.
I'll try the default when my wife gets back from the store and report back.

Reset APN to default settings, no luck.
The previous owner was on a smaller carrier, like a Metro PCS or something similar... Can't remember, but I don't know if their settings are different than T-Mobile's.

Yes their settings are diff... metro is fast.metropcs.com for apn inside and tmobile is fast.t-mobile.com. You can try clicking the apn make sure its fast.t-mobile.com and check the ipv and set to ipv6 and ipv4 for roaming. Then at the very bottom under MVNO select None. Then restart phone. If your still not pulling up data you may want to push a radio image to the device possibly and maybe the radio firmware is screwed up since your not original owner of the device.

All the APN settings are correct and identical to my working Nexus 6.
Are there tutorials on how to push a radio image and where to get said radio image?

https://www.androidpit.com/how-to-update-nexus-5-bootloader-and-radio - Nexus 5 instructions but they are the same just download nexus 6 files instead from here
https://dl.google.com/dl/android/aosp/shamu-mob30i-factory-21357b09.tgz - MOB30I Latest Marshmallow files...
When you follow that guide you could just flash-all command it and flash marshmallow stock in its entirety... it would flash latest bootloader and modem with it or you can extract the modem and bootloader files from the file and follow the guide. If you dont care whats on device you may want to just flash the whole thing and skip the extracting the modem and bootloader parts.
**Obviously since you'd be replacing the nexus 5 files with 6 files aka shamu instead of hammerhead change the names in the commands you type in fastboot. Just a reminder.

Thanks so much for the help!
I'll try this later and let you know if it works.

hermunn123 said:
Thanks so much for the help!
I'll try this later and let you know if it works.
Click to expand...
Click to collapse
No problem and best of luck on it.

hermunn123 said:
I'm at my wit's end here... I'm hoping y'all can help me get it fixed.
Click to expand...
Click to collapse
Enter into the bootloader and check the Product/Variant information within. For the US, it should read "shamu XT1103" followed by the memory size and a hexadecimal string. If it reads "shamu XT1100", you have the international model, which would explain the trouble you're having. Another possible explanation, especially if the model is "shamu XT1103", is that the device is blocked on T-Mobile.
To answer your questions:
1. If you have an international model, you may be able to activate the missing bands necessary to support LTE here in the US. Otherwise, flash the latest ROM from Google, as there are settings in the services menu you accessed which once selected cannot be changed unless a new ROM image is flashed.
2. LTE radios can both be damaged and disabled. The LTE could be disabled in the service menu, or the hardware is damaged.

Strephon Alkhalikoi said:
Enter into the bootloader and check the Product/Variant information within. For the US, it should read "shamu XT1103" followed by the memory size and a hexadecimal string. If it reads "shamu XT1100", you have the international model, which would explain the trouble you're having. Another possible explanation, especially if the model is "shamu XT1103", is that the device is blocked on T-Mobile.
To answer your questions:
1. If you have an international model, you may be able to activate the missing bands necessary to support LTE here in the US. Otherwise, flash the latest ROM from Google, as there are settings in the services menu you accessed which once selected cannot be changed unless a new ROM image is flashed.
2. LTE radios can both be damaged and disabled. The LTE could be disabled in the service menu, or the hardware is damaged.
Click to expand...
Click to collapse
I have same problem. I have XT1100 on T-Mobile, but I can only use 3G. How to see which LTE bands on this devices are activated?

If you have an XT1100 in the US you're missing bands 2, 4, 12 and 17. Of those, bands 2 and 4 are the most important as AT&T and T-Mobile both use those bands extensively. And unlike the US model, Verizon and Sprint won't work at all. Search the General forum, as there is a thread on how to add bands to the radio. Be warned however. When I attempted it on my Galaxy S4 I nearly bricked the device.

Also (and I know its basic) but check under settings ---> mobile ---> preferred network type and make sure it says LTE (just on the off chance it was switched somehow)

updating to Pie - how to tell / predict / force firmware region

I've got an unrooted xz1c that came with some sort of non-US stock firmware - which I know, because the fingerprint reader works. It's been nagging me to update it to Pie since I bought it, and I'm thinking I'd like to do it via the "official" (OTA) route, since it claims to be able to do it in-place, without having to reinstall apps, restore data, etc. What I want to avoid, though, is ending up with a US update, losing my fingerprint reader, and having to jump through hoops to get it back.
The build number in About Phone says 47.1.A.12.270. Is there some way of determining the current region, and confirming what region the update plans to install (without starting the update) - and/or forcing the region to match what I currently have? My google accounts, phone #, etc. are all US-based, if that makes any difference in terms of the update deciding what region is appropriate.
I was looking at a guide for installing specific region firmware via xperifirm/newflasher, but it indicated that the result would be a wiped phone, and I don't have time to deal with re-configuring everything from scratch right now.

Firmware customization does not change by applying OTA update. It will install the update of the same region that is already installed.

meeotch1 said:
I don't have time to deal with re-configuring everything from scratch right now.
Click to expand...
Click to collapse
In the past the OTA updates have famously locked thier owners out of thier phones by not regonising the unlock code that has been set, so make sure you disable it before you start.
Also, updating from 8 to 9 leaves some apps glitchy and there have been several reports of phone problems that can only be resolved by a full factory reset.
If you want the best experiance from your phone, wiping it would be the best option when upgrading.
Use Xperia transfer to back up apps/call history/contacts/text history. Then restore once you've wiped your phone.

@meeotch1 If you are happy with Oreo and without the latest security patches and updates, just let the phone OTA update it to the final Oreo version 47.1.A.16.20 and leave it there.
You can force close the Software update app from app settings to make it stop nagging about the update. And with adb you can even disable it permanently (and enable later if you wish to go for Pie).

Thanks for the advice. Good to know that the nag is disableable. So I take it that OTA upgrades *within* major versions (so Oreo 47.1.A.12.270 to 47.1.A.16.20) do not suffer the glitches mentioned by the first reply above?
Also, when I eventually go Pie, what's the least painful / most reliable restore method after wiping the phone? Is the built-in Xperia backup/restore available in Settings good enough? I'd prefer not to upload all my data to Google, unless there's some guarantee that it's encrypted. Don't need the NSA digging through my messages to radical terrorists and international drug lords.

To find out the customization, go to the service menu and select "Software Info".
You'll see an entry named "Customization Version" with a number like "1310-4371_R6C".
You can then look in XperiFirm at the column named "CDA".
On the example I gave, "1310-4371" corresponds in XperiFirm to "Customized US".
You can also look further down in the software info at "Current Modem Config" where the format will be something like:
/system/etc/customization/modem/amss_fsg_lilac_tmobile_us_ims_tar.mbn"
That tells me that my SIM card matched a mobile operator that is recognized as having a valid modem configuration file for my customization's region and, as such, loaded the correct modem file for that operator.
It also shows that I'm using T-Mobile US as my operator (tmobile_us) and I have some kind of VoLTE available (ims).

Change CSC?

Is it safe to change the CSC so we can use a Samsung image that's less bloated? My version has O2 apps installed and I'd rather reclaim that space for something else, or at least not have to look at it.
Change CSC on Samsung Devices | Guide | iHax
Looking for a way to change CSC/Country Specific Code on your Samsung Galaxy device? Here's a quick guide on how to do it easily.
ihax.io

I don't know about other regions, but in the USA region, I beleive the SIM card will set the CSC for you, and not allow it to change. In some cases, even that doesn't work properly (I had to return a phone because it wouldn't switch). Maybe you have more control in other regions or with Exynos phones...

Just tried the key combo and no dice, got a message that said 'that function is not supported' or something like that. I asked a question elsewhere here - what would happen if I were to just flash a different Android 12 firmware version on this phone? Right now, the phone is O2U, would I brick if I used XAA (US)?

I don't know what key combo you're talking about. As I mentioned, in the USA region, the SIM determines the CSC. What type of phone do you have (Exynos vs Snapdragon) as this could affect things as well?
If you flash a snapdragon ROM onto an Exynos phone, I imagine you're going to have problems. I don't know if that bricks it, but I wouldn't be surprised if it does.

BillTheCat said:
Just tried the key combo and no dice, got a message that said 'that function is not supported' or something like that. I asked a question elsewhere here - what would happen if I were to just flash a different Android 12 firmware version on this phone? Right now, the phone is O2U, would I brick if I used XAA (US)?
Click to expand...
Click to collapse
Yoooooo I'm going through same issue. Look you can flash any firmware Purdy much as long as the binaries are the same im trying to root a galaxy a13 5g from MetroPCS that only has two months activation in and its beating my ass. I was able to do some kinda unlock on it coz now it says device is corrupted dm-verity can't be trusted but I still don't have oem unlock displayed in developer options I've flashed t-mobile,Verizon,MetroPCS, and now I'm on Canadian firmware which is supposed to be unbranded but because MetroPCS has the network lock on it it hasn't mattered what I've flashed because I even had it XAA by flashing the a5150 csc tar file trying to root this funding piece of suit phone but to no avail.unless I get the network unlock icant get the bootloader unlock option,tried vbmeta image no verity no force encrypt every Magisk version boot image patched even tried different device with same chip and set up... impossible broski if you phone is network unlocked and you are able to unlock bootloader so you can bypass vaultkeeper/avb/secureboot/vbmeta/dmverity/prism.img....etc etc etc and with root access only then can you change and/or modify any part of a samsung device as far as my knowledge and experience goes
{Mod edit: Inappropriate language iaw. rule no. 2 removed. Oswald Boelcke}