Database Develop

gps, usb, ota problems

Hi all,
I've purchased a samsung captivate from United States and bring it to italy where I'm using with Wind operator.
I'm starting thinking that it was the worst purchase that i've never made.
First of all, I've unlocked at&t sim restriction and it was the only think went fine.
In italy I had time to test the phone and I've noticed the full unworking gps feature: position was never catched and just 1 or 2 satellites was found with low signal.
I'm trying to use samsung kies to upgrade the firmware before install a custom rom but samsung kies doesn't found the phone! (on win 7 or xp the fault is the same.. Mtp driver not installed correctly or kies says that phone is not supported!)
Moreover, updates by OTA don't work because the updated tool fails to connect to at&t server!
I'm really sick for all of that.. The last think I can do is to root the phone and install a custom ROM but I'm afraid that gps still doesn't work.
What do you think about this?
​

You don't need to update to install a custom rom. So I wouldn't stress too much about it. Make sure you back up the folder which contains the unlock information!! I made that mistake.
Many roms out there try to fix gps issues. For now, many of us (including me) have awful gps capabilities.
Edit, I should say that many roms vastly improve the GPS, so after you've read up on flashing and want to give it a try, it's probably your best bet.
Sent from Captivate, sorry for the brevity.

I don't know if your experience with the original firmware is the same that i have but my gps is not working at all. I can't understand how they can sell a phone with this buggy behaviour.
However, if it does not work also with the new firmware may I flash back original firmware for at&t / samsung assistance? I don't think so but maybe you are more informed than me.

Have you tried installing the gpsjm9 files with clockwork? Makes even stock gps better.
Sent from a phone somewhere in the universe

cappysw10 said:
Have you tried installing the gpsjm9 files with clockwork? Makes even stock gps better.
Sent from a phone somewhere in the universe
Click to expand...
Click to collapse
i see its from/for an i9000. will it be fine with the captivate?

chasesavestheday said:
i see its from/for an i9000. will it be fine with the captivate?
Click to expand...
Click to collapse
yes...and you can flash from stock to a custom.
you can flash back to stock via odin 1-click.
my best gps performance (build 1007)
have been with
Doc's, Chronus, and Assonance.

Struggling with Cappy. Help Please.

Hi, all XDA users.
I've been waiting to post my problems here and tried a few things I could to fix then with no success.
Here's what happened.
I bought a Captivate in february in an eletronics store in Miami, and since I am from Brazil, at the time my only concern was to make sure the device was unlocked, so I tested my sim card and was OK.
So my problems started as I went back to my country, the phone works good, but some issues appeared and they are kind of major for a device like that. Here they are:
I can't download from the market ever since I bought the phone. From a wifi conection or 3G . That was disturbing me so I did the factory reset and that allowed me to use the market for a while, something like 10 minutes maybe, before started giving me the "download was unsuccessful" error. And I did the factory reset a few times . But that was only a taste .
I also can't update my phone from the 2.1 eclair to 2.2 froyo or whatever is available, through Mini Kies, always getting the "unregistered device" message, before anyone asks I tried that in a Win XP and a Win 7 64 .
I tried to do the update several times but I was never able to enter download mode on the phone.
I installed some apps using the Sideload Wonder Machine, since I wasn't able to do it using SDK tools . Perhaps because of the Win 7 64?
So I decided to leave the IPhone for this device for its greater hardware capacity and because of the Android OS overall improvement, but I can't do much with it now, and since I am totally noob, I don't really know if my device was rooted before I bought, I don't know If the best thing to do is to flash stock and start over.
Didn't flash because I am afraid of bricking it.
The one thing I know is that I was able to get rid of all the crap from AT&T and nothing changed in my phone, and I heard that I needed to be rooted to be able to do what I did.!?! Is that true? Please help.
Here are some info about my phone.
Firmware version: 2.1 update 1
Kernel version : 2.6.29
Samsung SGH-I897
Baseband Version : I897UCJF6
Thanks all for your time .

Kies Mini is for US updates. Did you try the full version of Kies? Might work for you there.
Mobile Phone's Software & Manual

Will flashing a new modem help? Did you check network settings? Call company and switch to that region. I don't know. Just some suggestions.
Sent from my SGH-I897 using XDA App

Download one click odin flash the stock jf6 and master clear.this will do a full factory reset.
Sent from my GT-I9000 using XDA Premium App

cappysw10 said:
Kies Mini is for US updates. Did you try the full version of Kies? Might work for you there.
Click to expand...
Click to collapse
I did try the full version, but I will do it again in a XP version of windows and tell what happens .
I am downloading it from the brazilian samsung domain (.com.br) .

I tried again to use the regular Kies but didn't work.
It kept saying my device is not supported .
Funny thing is that in the Kies website, as you change the country flag in the bottom of the screen, the supported devices also changes, and in Brazil there is only a "Wave" called line of devices, while seems that the cappy I can only find in Canada. My point is that the Captivate IS supported.

I had a similar problem when a bad ROM flash borked my IMEI and product code. Chances are good that whoever unlocked your phone ended up screwing this up. Check out this guide to restore a specific IMEI to the device.
Also, you won't find the Captivate supported outside of the US or Canada, since it is only sold under that name by a few specific carriers (in the US, only AT&T carries it). Outside the US, Samsung mostly pushes other Galaxy S phones. Still the same "family" of phones, but there are differences between them.

yourname146 said:
I had a similar problem when a bad ROM flash borked my IMEI and product code. Chances are good that whoever unlocked your phone ended up screwing this up. Check out this guide to restore a specific IMEI to the device.
Also, you won't find the Captivate supported outside of the US or Canada, since it is only sold under that name by a few specific carriers (in the US, only AT&T carries it). Outside the US, Samsung mostly pushes other Galaxy S phones. Still the same "family" of phones, but there are differences between them.
Click to expand...
Click to collapse
Thank you so much. When I first had the problem I figured this was one possibilitie, but the salesguy assured the phone was "factory unlocked", so no one could've laid their hands on the device to screw it up like that. Your info was very valious, I will try to do the restore and let you know.

My T-Mobile Streak got Honeycomb!

Hi,
First off I bought my T-mobile branded Streak 7 from Craigslist a week ago before Dell announced that only the WiFi and unlocked Streaks would get 3.2! I was soo MAD!! So i posted my Dell on craigslist for dirt cheap on October 7th at 5:00 p.m. When I got home all on the sudden at 9:00 p.m. California time I got a notification that an update was available!! I proceeded to jump up and down and hit the download the update!! I went through all the steps and I have an official 3.2. streak T-mobile version!! I bought it from someone who stated it was new and I only used it on WiFi, So I thought I would be skipped on the update. Guess only the t-mobile version's that were activated on t-mobile are affected?
Battery life is still the same and most of my apps work, except NetFlix!!
Anyone else rocking the official update on there t-mobile?

What rom version do you have? It was likely updated with a wifi/retail rom and not a tmo one as they dont exist

salgalvan said:
Hi,
First off I bought my T-mobile branded Streak 7 from Craigslist a week ago before Dell announced that only the WiFi and unlocked Streaks would get 3.2! I was soo MAD!! So i posted my Dell on craigslist for dirt cheap on October 7th at 5:00 p.m. When I got home all on the sudden at 9:00 p.m. California time I got a notification that an update was available!! I proceeded to jump up and down and hit the download the update!! I went through all the steps and I have an official 3.2. streak T-mobile version!! I bought it from someone who stated it was new and I only used it on WiFi, So I thought I would be skipped on the update. Guess only the t-mobile version's that were activated on t-mobile are affected?
Battery life is still the same and most of my apps work, except NetFlix!!
Anyone else rocking the official update on there t-mobile?
Click to expand...
Click to collapse
Ok im lost u have a branded tmobile device and you got a official hc up date from dell? How the hell.

does it actually have the Tmo logo on back of device?
even then could be faked... just syaing.. I hope its legit..
if so please PM TheManii.. he will be interested.
This might be great news!

Hi,
Ya I it came in the official T-Mobile box and paper work, and the T-mobile data only sim!! I took my sim outta my Dell Streak 5, which is also on T-mobile and it worked! But when i tried to browse the net I keep being re-directed to the T-mobile site!! It does show the 4g logo and edge too when I'm out of range. (My Dell Streak 5 I bought from Craiglister who bought it in Australia so I have been using a T-Mobile sim for years!

I'm guessing cause I was to lazy to get a t-mobile broadband plan. I was using only with WiFi.. So it was never registered with t-mobile. That's my best guess. I will post a photo of the info tonight.

TheManii said:
What rom version do you have? It was likely updated with a wifi/retail rom and not a tmo one as they dont exist
Click to expand...
Click to collapse
It is 3.2 along with the Dell Stage widgets. Listen guys I have no reason to be pulling anything over on anybody.. I was so Mad when I read on Dell that all but t-mobile streaks would be updated. I promise I'll post more info tonight.. I was No [email protected]#! way when I saw the update notification!
Ya it is the WiFi Retail honeycomb version! Every T-mobile app was missing, like Blockbuster, t-mo tv, but I can download them from the market.

???????????????

this is likely that unbranded update posted on streaksmart. Like you said If the device has never been registered on tmobile... but how would they actually keep track of this for the update... hmmm I dont know. But congratulations buddy, make sure to pm The Manii in case this is something new.

Photos added.
Hey everybody! Well I add some photos, but let me know if I should add more!

That's the unbranded US 4G one, you cant officially flash it from the previous tmo roms

By unbranded, do you mean the one that hasn't the "T-mobile" decal in the back?
because i have one that doesn't have the decal in the back, but it IS branded "t-mobile" (i have the T-mobile SIM and everything).
is the same?

I mean the rom, the Tmo s7 is the only physically branded device dell sells.
I'm talking about the rom as it's region 30 which is "dell" or "US" region
Tmo roms are 33 which is "tmobile" region roms

Isn't the point that it got sent to his tablet in the first place?
Sent from my Nexus S using XDA Premium App

Thanks Smurphjw! My point was only that I got the update and nothing else! So maby T-Mo users might get the update too, with out having to root. I understand that the rom is unbranded, but Dell was clear that only WiFi Streaks would gt the update.

I seriously doubt it was on an unmodified device as the update script in the pkgs only checks two things before installing:
1) If the device is a streak7
2) what region it is (out of either "tmo (33)" "Boss (00)" - which is what the EU regions use" and "US (30)")
The flashable zips I released only did two things: remove those two checks and remove the modem updates

TheManii said:
I seriously doubt it was on an unmodified device as the update script in the pkgs only checks two things before installing:
1) If the device is a streak7
2) what region it is (out of either "tmo (33)" "Boss (00)" - which is what the EU regions use" and "US (30)")
The flashable zips I released only did two things: remove those two checks and remove the modem updates
Click to expand...
Click to collapse
I have a quick question. Since all you did was remove the checks and modems, why can't one just change the zip file to update.pkg and use the stock recover to flash to HC? Why does one have to install CWM and then install the zip?
Or just change the region to (33), and then we can use the package without CWM? (I know, it is probably too simple, or it would have been done this way already).

The stock recovery decrypts pkgs, that's what makes pkgs different.
If you simply renamed the zip to pkg it would try and decrypt that and would end up with garbage. The stock rec has no options, it will only "decrypt the pkg" -> "attempt to flash decrypted pkg". Only way to flash something with the stock one is to first encrypt it correctly so it will decrypt it on it's own
Changing the region requires modifying the recovery image, which has already been done with links on the update guide

TheManii said:
The stock recovery decrypts pkgs, that's what makes pkgs different.
If you simply renamed the zip to pkg it would try and decrypt that and would end up with garbage. The stock rec has no options, it will only "decrypt the pkg" -> "attempt to flash decrypted pkg". Only way to flash something with the stock one is to first encrypt it correctly so it will decrypt it on it's own
Changing the region requires modifying the recovery image, which has already been done with links on the update guide
Click to expand...
Click to collapse
OK, thanks for the explanation. I'm still on Froyo, but I may update at some point. It seems pretty clear, and easy except for having to get CWM on the S7.

I seriously doubt it was on an unmodified device as the update script in the pkgs only checks two things before installing:
1) If the device is a streak7
2) what region it is (out of either "tmo (33)" "Boss (00)" - which is what the EU regions use" and "US (30)")
The flashable zips I released only did two things: remove those two checks and remove the modem updates
If you look at the photos I posted under the firmware it shows I have the US 30. I never posted trying to tick anyone else off. I never modified my Streak, but I give up, because apparently I'm lying according to ThManni. I only wanted to post my good news, and give some hope to others. When I bought my Streak it came in a sealed box with all the plactic on screen and back of unit. Sorry to all who dought me when I say I never modified my streak at all.

Rooting Galaxy s3 mini....

Hi, I posted about this on another thread, but was then told that there is a forum for the S3. I would like to root my S3 mini GT-18190N, running 4.1.2. Its still under guarantee so it needs to be able to unroot.
Somebody mentioned CydiaImpactor, as it would be the easiest. So I installed to my mac, ticked both usb debugging and accept unknown sources, and ran the program. Within seconds I got an error, 'Error signature bugs unavailable'.......which I posted to the thread, and heard nothing from there and still havent about what that meant. I eventually found out that it means the bug has been fixed. But that is all I got.
I just wondered, what does that mean, does it affect any other ways of rooting? I found another rooting program on here, was given the the stock firmware for my phone but that needs to be unlocked. I did ask about whether the same problem would affect that firmware, but no answer. It seems the advice given on the first thread I started, about taking this to the correct forums needs to be done, which is why I am asking here. Sorry for multiple posting its not spam, its on advice from members on here.
I am a complete novice, never rooted before. So could anybody show me a root system that works for my phone.
Thank you

johnmwc2 said:
Hi, I posted about this on another thread, but was then told that there is a forum for the S3. I would like to root my S3 mini GT-18190N, running 4.1.2. Its still under guarantee so it needs to be able to unroot.
Somebody mentioned CydiaImpactor, as it would be the easiest. So I installed to my mac, ticked both usb debugging and accept unknown sources, and ran the program. Within seconds I got an error, 'Error signature bugs unavailable'.......which I posted to the thread, and heard nothing from there and still havent about what that meant. I eventually found out that it means the bug has been fixed. But that is all I got.
I just wondered, what does that mean, does it affect any other ways of rooting? I found another rooting program on here, was given the the stock firmware for my phone but that needs to be unlocked. I did ask about whether the same problem would affect that firmware, but no answer. It seems the advice given on the first thread I started, about taking this to the correct forums needs to be done, which is why I am asking here. Sorry for multiple posting its not spam, its on advice from members on here.
I am a complete novice, never rooted before. So could anybody show me a root system that works for my phone.
Thank you
Click to expand...
Click to collapse
hi bro, maybe i will buy this s3mini because i notice that it cost only 114.50 euro in my country, more than 50% less than the official price
so...
about root:
you can root the s3mini flashing the firmware with odin
else you can use cydia impactor(be sure to download the latest version from official websites)
i notice that samsung patched the masterkey bug exploited by cydiaimpactor in other galaxy phone but i dont know about s3mini 18190
however i rooted an s3mini of one of my friend s1 months ago, he has never made a firmware update and after he enabled debug usb and installed driver it work! and got root access on his phone, after root you CAN'T do ota update! you an use odin however maybe samsung upgrade to kitkat android 4.4
did you do some firmware update?

-Install TWRP (this video might be of help)
-enter recovery mode and reboot. TWRP will ask you whether you want to root or not

Hi, before I did anything I took a copy of the phone which I have stored on the laptop, windows 7. Then with CWM rooted the phone, and installed a ROM I found. The first time it didnt work, so I had to find another ROM, and install that. This ROM works but its not from my Carrier, which is EE/Orange. The Base version ends in AMJ2, which I dont seem to be able to find to get the correct ROM. The Build Number I have which is the ROM is DMod v6. It works, but its causing problems with Samsung. I have given hope of getting back to the original, but if I could get it to work with EE, it would be better. DModv6 is a US based ROM.
I hope I have explained it ok, its the first time I have done this, so not sure. Please ask for more details.
Sorry it took me so long to answer, have not been very well.
Thank you for your help

What do you mean by it not working with EE/Orange? What functionality do you not have?
Sent from my GT-I8190 using xda app-developers app

Mermaid Man said:
What do you mean by it not working with EE/Orange? What functionality do you not have?
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
As I have already mentioned, its a US based ROM, which only recognises T-Mobile UK. My phone keeps loosing the connection all the time. and I have to reconnect. T-Mobile UK is the US version of T-Mobile even though we have T-Mobile in the country, but without the UK at the end of it. And believe me it is not working properly. The phone itself does work, its faster, the battery life is much longer than when it was on EE. But I am also now having problems with Samsung, they have stopped me from using their software, because they say my phone is not using the correct software.
My first try, I did get Kit Kat running, but without the CAMERA, it wouldnt work. But there again, it was on a US based ROM, and had problems keeping the connection going. That was awesome but without the Camera, it was a bit useless. If I could get a ROM thet had either EE or Orange,

johnmwc2 said:
As I have already mentioned, its a US based ROM, which only recognises T-Mobile UK. My phone keeps loosing the connection all the time. and I have to reconnect. T-Mobile UK is the US version of T-Mobile even though we have T-Mobile in the country, but without the UK at the end of it. And believe me it is not working properly. The phone itself does work, its faster, the battery life is much longer than when it was on EE. But I am also now having problems with Samsung, they have stopped me from using their software, because they say my phone is not using the correct software.
My first try, I did get Kit Kat running, but without the CAMERA, it wouldnt work. But there again, it was on a US based ROM, and had problems keeping the connection going. That was awesome but without the Camera, it was a bit useless. If I could get a ROM thet had either EE or Orange,
Click to expand...
Click to collapse
Hey mate,
Try to use Maclaw's Recovery and KitKat ROM. They work perfectly! Flash Maclaw's recovery first (TWRP) and then wipe cache and dalvik and then flash the kitkat ROM (CM 11).
find them all here: maclaw.pl/downloads/ (stupid 10 post rule for new accounts doesn't let me post the link to HELP the user (johnmwc2)
---------- Post added at 06:32 PM ---------- Previous post was at 06:28 PM ----------
Also the reason that your phone has gone all crazy is because of the ROM you flashed (US version) probably only supports the US frequencies which is why you only get t-mobile network (in some places) as the frequencies change in each location as the phone masts give out different frequencies in different locations according to their surroundings (some frequencies penetrate walls much easier but may not go as far and vice versa).
Im 70% sure the ROM is the problem. the other 30% is me thinking maybe the ROM might not have anything to do with allowing the phone to receive phone signal ( in terms of SOFTWARE not hardware - before anyone tries flaming me). My other instinct tells me maybe its the baseband/modem version thats incompatible witht the US ROM?
just use Maclaws KitKat and TWRP!
They work a treat! :laugh:

pixel 4 xl mobile network problem

need some help here , my pixel 4 xl just updated to jan 2021 update
, post update im unable to connect to mobile network .
already tried hard reset not working
also flashed previous factory image still aint working
is any other thing i can try to solve the problem or im doomed?

capayam said:
need some help here , my pixel 4 xl just updated to jan 2021 update
, post update im unable to connect to mobile network .
already tried hard reset not working
also flashed previous factory image still aint working
is any other thing i can try to solve the problem or im doomed?
Click to expand...
Click to collapse
Who is your provider? Are you using SIM or eSIM? Are you rooted? Did you disable all the Magisk modules before the update? If you forgot that step, have you since disabled all Magisk modules and started over?
While you may be out of commission on the phone side (although, Google Voice would be a good band-aid), you may not be out of commission on the SMS side. Google's text app, Messaging, recently went live with RCS messaging and it can send texts via WiFi.
Incidentally, if it's Google Fi that's giving you fits, the same thing happens to me every time I do a clean install. Fi refuses to connect until I've rebooted two or three times and then the final confirmation comes several hours later.

im in malaysia bought secondhand 1 year ago on grey market , check my sim with another phone , working well on that phone. had been running my phone on regular stock since bought.

capayam said:
im in malaysia bought secondhand 1 year ago on grey market , check my sim with another phone , working well on that phone. had been running my phone on regular stock since bought.
Click to expand...
Click to collapse
Okay, you answered almost none of my questions but it's irrelevant at this point because it sounds like the phone was stolen. If the IMEI is reported as stolen, it's flagged in a database and alerted carriers will shut off the service.
If that's the case, at this point, I'd be more concerned about the police knocking on my door than lack of mobile service. I'd send you over to IMEI.info to verify but I'm guessing I haven't told you anything you didn't already know.

imei number legit not reported or blacklisted, but yeah i think this phone is doomed unless there some magic update resolved this

capayam said:
imei number legit not reported or blacklisted, but yeah i think this phone is doomed unless there some magic update resolved this
Click to expand...
Click to collapse
Why don't you try to reset using the last official 10 firmware (to reset all partitions), then activate through setup, then flash and test a custom rom. This is of course only possible if it's an unlocked bootloader (which you didn't mention) but that's where I'd start especially if it worked before the update. You say is legit and sounds like it worked BEFORE the last update so roll back and then use a custom rom.

GROOVYJOSHCLARK said:
Why don't you try to reset using the last official 10 firmware (to reset all partitions), then activate through setup, then flash and test a custom rom. This is of course only possible if it's an unlocked bootloader (which you didn't mention) but that's where I'd start especially if it worked before the update. You say is legit and sounds like it worked BEFORE the last update so roll back and then use a custom rom.
Click to expand...
Click to collapse
will try it later dude

capayam said:
will try it later dude
Click to expand...
Click to collapse
Unfortunately it's my best guess because I can't reproduce it myself but if it worked prior to the firmware upgrade, it should work by reverting the firmware to the previous firmware in my opinion. I'd take it the step furtherand go with a custom 10 ROM to remove Google firmware updates messing with it in the future (assuming we get it working again).
Interestingly enough, I searched other forums and found other users reporting the same issue. Again, assuming it worked on the previous firmware, I would roll bak to it. Ideally, I would rollback to 10 because I know 10 works (not sure how well it works for you in your local and provider), but thats where I would start. Backup everything you need, then use the last 10 firmware to -w the device and activate then start over.

Why is this posted in development?

shiftr182 said:
Why is this posted in development?
Click to expand...
Click to collapse
who knows