Hi all,
I've purchased a Sumsung Captivate from an U.S.A. Best Buy store less than 30 days ago.
I've unlocked it and I'm using it in Italy.
I've noticed random shutdowns and read that my phone should be changed from Samsung/AT&T for this issue (I'm afraid that it is an hardware issue).
Anybody knows if Samsung may change it after unlock? Is there any way to restore SIM locking as AT&T configuration?
Thank you in advance
backtothefuture81 said:
Hi all,
I've purchased a Sumsung Captivate from an U.S.A. Best Buy store less than 30 days ago.
I've unlocked it and I'm using it in Italy.
I've noticed random shutdowns and read that my phone should be changed from Samsung/AT&T for this issue (I'm afraid that it is an hardware issue).
Anybody knows if Samsung may change it after unlock? Is there any way to restore SIM locking as AT&T configuration?
Thank you in advance
Click to expand...
Click to collapse
As stated in numerous other threads, the random shutdown/reboot on official software is very common and would most likely persist even after the swap. Look into installing a Custom 2.2 ROM that doesn't have this issue(I think all Custom 2.2 ROM's dont have this issue)
****BUT*****
READ UP FIRST on the SIM unlocking procedure on 2.2. You may need to back up files from 2.1 before you do it!
geokhentix said:
As stated in numerous other threads, the random shutdown/reboot on official software is very common and would most likely persist even after the swap. Look into installing a Custom 2.2 ROM that doesn't have this issue(I think all Custom 2.2 ROM's dont have this issue)
****BUT*****
READ UP FIRST on the SIM unlocking procedure on 2.2. You may need to back up files from 2.1 before you do it!
Click to expand...
Click to collapse
You're right, I've installed already a custom firmware and just one shutdown happens 10 days.
However, I was asking it because my "30 days" are expiring and if Samsung changes it with a more reliable one it's not bad!
geokhentix said:
As stated in numerous other threads, the random shutdown/reboot on official software is very common and would most likely persist even after the swap. Look into installing a Custom 2.2 ROM that doesn't have this issue(I think all Custom 2.2 ROM's dont have this issue)
****BUT*****
READ UP FIRST on the SIM unlocking procedure on 2.2. You may need to back up files from 2.1 before you do it!
Click to expand...
Click to collapse
I'm not sure that this is true. My first Captivate (which fell into Samsung's reported 'defective' IMEI range) had shutdown issues regardless of what ROM it was running. I swapped to one outside of the range (better screen as well) and I haven't had a shutdown since.
GGXtreme said:
I'm not sure that this is true. My first Captivate (which fell into Samsung's reported 'defective' IMEI range) had shutdown issues regardless of what ROM it was running. I swapped to one outside of the range (better screen as well) and I haven't had a shutdown since.
Click to expand...
Click to collapse
I said I think it is an hardware problem because if they really echange the phone for that IMEIs it may be necessarily an hardware issue for me.
Anyhow, Is there any way to restore SIM locking as AT&T initial configuration?
(I know how to rerstore firmware but I think it doesn't restore the SIM locking..)
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:
Hi everyone.
I'm a bit stuck here, and I have googled quite a bit, but seem to come across conflicting information.
Basically I bought a PAYG S3 LTE on EE UK that had official status, and wanted to unlock it to the 3 network. The only way I found to do it for free was to downgrade the ROM to 4.1.1 and use the hidden menu hack and so just decided to take it to the local phone shop and let someone do it properly.
But when I got it back, it turns out that he actually did the 4.1.1 hack himself and has rendered the phone 'modified'. I was a bit miffed as I wanted to keep it on 4.3 and get OTA updates.
So my question is, can I flash a stock 4.3 ROM back to the phone, and if so, will it keep the network unlocked for my 3 sim? Also, will I be able to root 4.3?
I do apologise if these are pretty obvious questions, but like I say, I just have seen many people saying different things.
I've also flashed a few phones of my own, so I'm not a complete newb in that respect.
Any info will be much appreciated.
Cheers.
Download your corresponding 4.3 firmware from: http://sammobile.com/firmwares/
And just flash it with Odin
Hi Everybody,
TL; DL
Modem N910FXXU1DPG1
Bootloader N910FXXS1DPG1
Fixed problem for me
Long story:
I had problem with random reboots/shutdowns and thethering locks (after some time no data over mobile network) on my note 4 N910F for about 3 maybe 4 months,
I thought this problem is rom related, so i have checked Emotion roms both Marshmallow (6.0.1) and Nougat (7.1.1) also i have checked stock and stock de-bloated rom but problems where still appearing.
Also I thought that problem maybe caused by Hangouts because very often after receiving Hangout message on my pc and then checking my phone it was off. So i run several days without Hangouts but still same issue.
For some time I thought maybe my battery was dying so i replaced it with new oem one , still same thing.
So once i was at place with bad mobile coverage so i have choose manually other signal provider and tether internet from my phone but not so long that my data locked.
Since i have manually chooseother provider my phone stayed at roaming and in WCDMA mode (i have no LTE on the roaming)
And my phone haven't rebooted/shutdown once in week !
So from that moment i knew that something smelly was going on with LTE modem, and my search for proper bootloader/modem started.
I have checked old ones , new ones from battlehero Note 4 - Bootloader and Modem Collection but nothing helped so i was convinced that my modem is damaged
Afters some digging in rom threads i saw that I'm not only one with this issue so there was two options:
There was mass issue with modem hardware like NOTE 1 nand memory
There is problem with modem software for some ppl
So i have searched and searched for some other modems and bootloaders , and i have finally found combination that worked for me!
Modem N910FXXU1DPG1
Bootloader N910FXXS1DPG1
Since installing this CP and BL i have no restart/shutdowns and no tetering locks
Thank you _alexndr for posting CP/BL collection
how many time are you tested this solution ?
I received a free Samsung S6 Edge from some friends. The phone had a busted battery which I fixed. The phone is still on the original 5.1.1 that the phone was released with.
When I try to do updates it says DM initialization not ready. Check network or SIM card. When I received the phone I was told it doesn't work with cell service. I checked to make sure and it definitely doesn't. There are no options for cell service in settings or the drop-down menu. This phone is missing IMEI numbers, IMEISV numbers, and baseband versions too. The only way I found out the IMEI number was it was printed on the back of the phone.
I am fairly certain the problems are software-based and not the motherboard but I don't know enough about phones to be sure. Do you guys know? I also want to remove AT&T from the phone to install a custom ROM on the device. (There is no OEM unlock in the developer options) Can I flash SM-925F firmware on the device to make it factory unlocked or will this brick the device? Will flashing the original SM-925A firmware fix the problems with the device? Please let me know if you need any more information to answer my question.
I found this: //G925A\\ Nougat 7.0.1 Latest Stock ATT Odin files G925AUCS7ERC1 | XDA Developers Forums (xda-developers.com) Should I flash this on my device? Will it fix any of the problems I had on it?
Can I flash the SM-925F firmware? Is the hardware of the factory unlocked phone and AT&T versions the same or will it brick this phone if I flash it?
Since the phone is AT&T you'll have to go through AT&T for the unlock codes before you can flash anything other than an AT&T ROM. To my knowledge there are no custom ROMS for the S6 Edge, but I could be mistaken.
skeltonh said:
Since the phone is AT&T you'll have to go through AT&T for the unlock codes before you can flash anything other than an AT&T ROM. To my knowledge there are no custom ROMS for the S6 Edge, but I could be mistaken.
Click to expand...
Click to collapse
I know this phone is old news however, I actually have the S6 and S7 edge lying around and so i got bored lol...here is my dilemma; Evidently the phone (S6 Edge G925A) had an abnormal factory reset, which is a load of BS, and now I can not get that security detail, which you know calling Samsung always ends to NO AVAIL!! I have flashed with Odin the firmware that my device is on the ERC1 firmware and still I get stuck @abnormal reset. I've searched numerous sites, different forums and still to no avail. Something told me inside that you was the man to drop a line to, any leads or info will be more than appreciated brother...Thanks for your time....
PSSS....
I got my unlock code from AT&T some time ago but the code is 16 digits long and code only takes 8 digits, and of course to hear AT&T tell it, " I simply must not putting the code in correctly"...lmao