Phone is completely broken. - Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help &

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)

Related

[Q] What does define the first screen (Samsung Galaxy S GT-I9000)

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

Stuck in Recovery....With a Twist

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.

GT-P1000 Reboot Loop

Hi,
My dad brought me his non rooted, non modified Galaxy Tab GT-P1000 that is stuck in the famous reboot loop. That is, it reaches the samsung logo and just stays on that animation of the logo glowing and fading.
I've tried various combinations of ROMS, as well as different versions of ODIN and Heimdall. I've successfully reflashed different firmwares but the furthest i get is the samsung logo.
The device was bought out of carphone warehouse UK, for which i found the latest firmware at http://fus.nanzen.se
I can flash this with heimdall 1.1 (1.3 always asks about firmware.xml which i figure is just a way of explaining what's in the tar to save selecting the files seperately). That said, i have tried 1.3 in command line mode on linux.
I get varying results with the flashing process too.
For example, this carphone warehouse firmware flashes fine with Heimdall 1.1 but fails in Odin.
I'm really running out of ideas. I thought it was just that something had got currupt somewhere and a reflash would sort it but no such luck.
Can anyone offer any tips? I've looked around the message board but it's like playing pass the parcel with the links. It seems a lot of people fix their tabs without actually realising what it is that fixed it because they've also gone through a whole load of combinations.
I've tried ROMS from samsung firmware website. Tried JHA from early on. Tried latest 2.2 that isn't tied to a network. Tried ones in the middle. Tried flashing only dbdata. Tried re-partition.
EDIT: I've avoiding looking into rooting it as a solution because my dad is trying to fish out the receipt in case it's under warranty. If it's not i'm prepared to root it. I used to be in the android scene back in the day when the G1 came out. I've programmed applications for Android and written a uni project on it so i am quite familiar with it, just maybe a little out of date with the processes.
EDIT2: Sorry guys just realised there is a galaxy 10.1 section too...
EDIT3: And that i don't have a galaxy 10.1 anyway...i may have flashed my brain with the wrong ROM. Anyone have a "sensible brain" ROM?
Hmmm... you might get helped at the Overcome-site, look for the restock GB v5 in the tutorials...

[Q] i'm in a Ultimate pain (Samsung Galaxy S3 LTE)

I F****** up..
i played with rooting and flashing before i found these forums with guides and stuff.
and now my samsung galaxy have no mobile network, no imei number and freezes when i activate bluetooth..
it was also bricked (logo loop) but i fixed that.
i have flashed stock firmware in it and it works fine beside the 3 problems above.
i've tried
http://forum.xda-developers.com/show....php?t=1801997
http://forum.xda-developers.com/show....php?t=1804123
neither did work since i cant usb connect i've tryed every option to get my pc to usb detect my mobile.
including kies and latest samsung drivers, reinstalling and with or with out kies.
someone please be my hero and give me some answers
you guys ****ing rock and i know we can fixx this!
Unfortunately the only simple way to fix things ...
Unfortunately the only simple way to fix things is to find a backup of your EFS partition - look after something called:
efs.img
efs.tar.gz
efsbackup.tar.gz
efsdev-mmcblk0p3.img.gz
(the img versions are probably the best, but either one should work to some extent).
EDIT:
OOPS, just now I noticed that you are speaking about a i9305 - you should look here:
http://forum.xda-developers.com/showthread.php?t=1946915

[Q] ICS 4.0.4 Won't Activate Sim Card

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 .

Categories

Resources