Hello All,
I couldn't find a Galaxy S Duos section so I'm posting here in the hope of getting some help.
I rooted the phone earlier in the year for no other reason that just to see if I could do it.
Shortly afterwards it developed the problem of not booting up from Power On and would simply flash the samsung writing and shut down again.
If I needed to do a a cold boot it was necessary to remove and replace the battery first. I don't power down very often so this was not a huge problem.
A few days ago I needed to switch one of the sims and afterwards discovered that it would no longer recognise the Sims and would show no Sims present.
I installed the most up to date firmware from earlier this year S7562XXBMD2 ICS 4.0.4 with ODIN and the process appeared to go well and the phone now shows that ICS 4.0.4 is present but still it won't recognise Sims.
Is the phone bricked, or is there a way out of this problem.
All i can suggest as its the wrong phone is to read the faqs and guides for I9300 and see if you can work out what your problem is .
http://forum.xda-developers.com/showthread.php?t=2344125
They may be totally irrelevant or plain wrong for your Galaxy S Duos.
Alternative find a forum via google .
Related
Here is why I'm asking this. I have a SGS I9000b. After some wrong doing that almost bricked my phone, the screen started to show that I had and SGS I9000b and then the B would quickly vanish resting only the Samsung Galaxy S GT-I9000.
The fact is, after some effort I was able to install eclair on the phone and put it to run again, but now when I start it, it shows SGS GT-9000 to quickly be substituted by GT-9000b.
I was unable to upgrade my SGS to froyo again, and maybe this is one reason that I cant, every time I try, I get that /dev/ error.
So, What does it means when at the start screen the modle changes suddenly?
Hope I could express myself clear enough.
I came across a similar thread yesterday.
http://forum.xda-developers.com/showthread.php?p=13268587
I guess the first part of the boot screen is from the bootloader and the second part of the boot screen is from the ROM? (pls correct me if I am wrong)
So, have you tried flashing I9000B stock ROM with bootloader using Odin?
If you want to upgrade using samsung softwares, you need to have the stock rom of your phone or an official stock upgrade (can find on samfirmware or in various posts here), otherwise in order to change rom you can use odin
Long time reader, First time poster.
I know that i am going to get bashed for starting a thread on a topic with past posts but please hear me out because this situation is a little different...
I Had a T-mobile Samsung Galaxy S Vibrant which i destroyed internally by going from a rooted 2.3 Android then stuck in Download mode then restored to factory settings with Android 2.1 then tried to upgrade to standard 2.2 with Kies, fried the internals...
I found someone selling a Bell Galaxy S with a broken screen so i had a guy transplant the motherboard from the Bell Galaxy S into the shell of a T-Mobile Galaxy S. It worked! Fully working phone and functional...
But then I installed ROM Manager from Android Market and did the ClockWorkModRecovery with the recovery for the Bell Galaxy (as according to the CynogenMod wiki)
A package unloaded, the phone restarted, then it showed recovery. The VOL+/- and Power combo does not work because according to some forum posts the Bell version uses the home button to select...which the T-mobile Galaxy does not have.
So now i am stuck in Recovery Mode with no escape. I ordered a samsung JIG off ebay and am waiting for it but i am concerned about how i can restore this phone into a standard Factory fresh android (for which i promise to never root this phone again because it seems to be cursed!)
I know from the past that before i messed up the original T-mobile Galaxy S, one time i had it in Download Mode then i used Odin 1.3 and a factory fresh file to have it restored back to its original state. Does the bell samsung galaxy have a similar file like the Vibrant?
When a bell motherboard is inserted into a T-mobile sell, is the phone for all intents and purposes a Bell Galaxy? I am guessing the answer is yes but i could be wrong...
Thanks for the help, Appreciate It.
Hello everyone.
I installed CWM 5.0.2.6 and then Cyanogen mod 9 succesfully. Then I changed it to "MIUI TOCAi 0.1.4" and it was working fine although it could not find my network. I tried searching manually but without success (it kept on showing up that it's not able to register to the network im choosing and that i should try again later.) It had simlock before so I tryed to unlock it using this thread "http://forum.xda-developers.com/showthread.php?t=1204705". I got the code etc but I didnt know where to type it in. I turned the phone off and on hoping that the menu with this code request would pop out but it didnt so I replaced the sim card with another one. It still didnt pop out so I replaced it with the previous one and the phone bricked.
Im not able to get to CWM or to the system at all. Im only able to get to DL mode. I tried to unbrick it using this method "http://forum.xda-developers.com/showthread.php?t=1071970" and few similar ones. I used multi and single package but without success.
The simlock was for "3" network. Tryed O2 and Vodafone simcards.
Is there any way to unbrick it without going to the service?
I'm going to post youtube links to show you how it looks in just a few minutes.
Part 1 : http://www.youtube.com/watch?v=oNln0KJQ-0o&feature=youtu.be
Part 2 : http://www.youtube.com/watch?v=urRAhOq0OCw&feature=youtu.be
Part 3 : http://www.youtube.com/watch?v=EU-EshQdj7E&feature=youtu.be
Looks like your efs partition (either stl5 or bml5) got corrupted. This cannot be fixed by flashing roms or stock roms, since its a sepparate partition. Network Unlocking the ace might result in a brick specially if not done from stock firmware.
i bricked my gio after network unlock too, it was due to the efs partition being messed up, i couldnt get it to boot normally or recovery (screen flashes then dies) but download works, and odin didnt solve anything, so i sent it in to samsung and got a new gio
to sum it up, you now have a nice paperweight
I have the Galaxy SIII 4G
running Android 4.1.2
Locked on Telstra
Any other information needed? ask me.
So, I got my phone from a friend, and was very exited and tried rooting.
Firstly using Odin and a guide which I can't link since I'm new to the forums and can't post links, I didn't get some steps right and phone wasn't rooted, I then did a factory reset.
Went to find another guide and then found the Galaxy SIII Toolkit (Am new to forums, can't post links) and used it, I found that the version 7.0.0 didn't include support for my android version on the 4G so I tried the normal international version that wasn't for 4G, it was very similar but this may have been what had broken it. (me choosing the wrong one, stupidly) and after trying and trying, using some other things like Odin, my phone is now stuck on the "Downloading...Do not turn of the target !!" and even if I pop the battery, reset the device, try to get to recovery, and trying many other things, It just doesn't budge. When I was able to get to recovery and able to make it to Samsung galaxy SIII logo but no further,(I managed to flash CWM recovery) I tried factory resetting but it still didn't work.
As you can tell, coming from a Galaxy Nexus to a Samsung Galaxy SIII is pretty exiting, then having the phone broken within the first day of having it is very saddening (Seriously almost cried).
I need urgent help, if you need any more information on the phone, feel free to ask, even though I may not know.
Thanks :fingers-crossed:
there's a reason there are 2 different versions for the i9300 and i9305. They're 2 different phones.
http://forum.xda-developers.com/showthread.php?t=1946915
and this is a wrong section, it's for the i9300 (it says so right in the title)
Good Morning Guys
After a lot of struggle I decided to post me and my friends problem here, I know on XDA Developers there are a lot of clever guys who might help us to solve this problem. Please note that I have a Galaxy S3 which is rooted and loaded with Custom ROM WanamLite Rom, so I am familiar with the process on how to do this and we have tried all options to fix the OS on this Galaxy S4 i9505 of my friend. Here are the details:
We are from South Africa and when overseas my friend bought a Galaxy S4 i9505 in Bangkok, he had the option between the clone and an Original, so he bought the ORIGINAL rather than the clone. Now once he got back to SA he started using the phone which wasn't network locked but we noticed that the OS version was a bit funny and that the phone was already rooted out of the BOX (Strange) so we thought he bought a clone and followed all the links on the the net showing how to determine weather its a clone or not. So we came to the solution that his phone is NOT a clone but it has a weird OS on it that we cant change/load another OS on. Here is what we tried:
1) We wanted to load a new OS or Custom ROM since the phone was already rooted, so we first tried to download the stock firmware from SAMMOBILE for South Africa and copied it to the Ext SDcard and rebooted the phone in Recovery mode. There we didn't have any option to install OS/ZIP from Ext SDcard ..... Not even under advanced. There is NO Mounts & Storage nothing, it just doesn't display any External Storage options. So this made us go to step 2
2) We thought okay lets try at least and load another custom ROM since its already rooted and see if we can fix the problem the other way around. So we installed Odin on PC and connected phone in download mode to install CWM recovery, ODIN pics up the device as "Unknown" and the port in ODIN doesn't become green. We have installed/uninstalled various S4 USB Drivers and when the phone is connected to Windows 7 PC is shows Unknown Device ...... You can access the phone Sdcard & ExtSDcard through Windows although its shows Unknown Device, but when rebooting in recovery mode it doesnt see the Ext SDcard - WTF?
This is where we gave up and decided to see if any of you guys can help or have any ideas to fix this and get a proper OS working on it ...... Cause I suspect that whatever OS is on the phone wont even receive OS updates and we want to be able to update the OS/Custom ROM for new OS versions like Android v5 thats on the way. Help would be appreciated guys
Take care