Related
The Reason i ask is either it is or i am the unluckiest person ever with a S2 lol
So far got the phone at xmas wasn't happy with the screen colours sent it off they said the main chip was faulty and had been replaced and a software upgrade etc...
Got it back and flashed a custom rom, well a few and noticed that i then had an issue where if someone called i had to put loudspeaker on in order to hear the other person...
Put phone back to stock and sent it off again...
Phone came back last week picked up monday used for a day all seemed fine, flashed a custom rom got another problem with the phone this time i have to put the loudspeaker on to hear other people they can hear me fine...
So its back to stock and back to vodafone tomorrow...
So can custom roms/kernels cause physical issue's with phones, never had an issue with my HTC Desire HD but i'm beginning to wonder if i should leave my next S2 stock, or have i just been unlucky ???
Would also add when going back to stock the screen colours seem much better than custom roms but the sounds issue's remain...
One word NO!
What rom are you flashing?
Checkrom, wickedrom, illusion Xt, not sure which if any has caused any issues could be I'm just unlucky
Definatly noticed issues with screen colours too which now in I'm back on stock have been sorted
Its all a bit weird
Sent from my GT-I9100 using xda premium
wakers said:
Checkrom, wickedrom, illusion Xt, not sure which if any has caused any issues could be I'm just unlucky
Definatly noticed issues with screen colours too which now in I'm back on stock have been sorted
Its all a bit weird
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Trust me if that was the case damaging my phone by flashing a rom then my phone would of been damaged goods by the first month i had it
Anyway just be careful how you flash a rom and it is always advised to do a full wipe before installing one
Um, actually, yes.
You run the (slight) risk of bricking your phone every single time you flash something to it. If you're the type of person who's paranoid about these things & can't handle the idea of possibly not getting warranty service if things go wrong, you shouldn't be messing with your phone in the first place.
Anyone who has an expectation (as opposed to a "hope") of warranty service after they stuff around with the phone is an idiot.
The SG2 is a hard phone to brick. Follow the general guidelines and you should be fine. I can't imagine flashing a rom can break this phone. Worst that can happen is you brick it. Either it works or it doesn't.
Yeah Im fully aware that you risk bricking the phone
I've been flashing roms to HTC,s for years always trouble free
I always read and full wipe between flashes
Sounds like I've been unlucky then 3rd time phone is going back and since Xmas 1day without a fault not a great introduction to Samsung for me...
Sent from my GT-I9100 using xda premium
In all my time reading SGS1 and 2 the only ones who have bricked their phone are the idiots (1) who refuse to read instructions . Even then 90% of them have been able to recover .
the SGS2 quota of 1 is getting higher day by day for some reason .
jje
Yeah 3 physical faults though in a month which is what got me thinking maybe installing the custom roms is causing an issue, but if others are installing with no issue's i've obviously just been unlucky
Hopefully this time i get it back its sorted...
wakers said:
Yeah 3 physical faults though in a month which is what got me thinking maybe installing the custom roms is causing an issue, but if others are installing with no issue's i've obviously just been unlucky
Hopefully this time i get it back its sorted...
Click to expand...
Click to collapse
~Don't accept a repair... DEMAND A NEW PHONE
Samsung doesnt change phones, only repairs.
GeorgeCm said:
Samsung doesnt change phones, only repairs.
Click to expand...
Click to collapse
Who said Samsung??? I meant Vodafone, and they do give new phones
About a stock I don't know, and on aosp try it
http://forum.xda-developers.com/showthread.php?t=1385862
Suarez7 said:
Trust me if that was the case damaging my phone by flashing a rom then my phone would of been damaged goods by the first month i had it
Anyway just be careful how you flash a rom and it is always advised to do a full wipe before installing one
Click to expand...
Click to collapse
Seconded..
It's possible to introduce some new bugs by flashing a custom ROM (that's the price of development, you uncover new weird stuff), but not to physically damage the phone. You'd have to fiddle with the battery or greatly increase the voltages to accomplish that.
If you experience hardware issues after flashing a ROM, it means that the hardware was faulty before, and flashing the ROM just uncovered it and made it obvious to you whereas it was hidden before.
But don't let it get you down. Apparently a lot of SGS2's are faulty when coming out of the factory and need to be replaced.
The first one I had didn't last the night, it 'overcooked' itself when I plugged it to the mains to get it recharged (I knew those phones could get pretty hot but damn ! a 100°C is too much for it, it didn't stand the strain and gave up)..
In fairness they suggested a new phone in Vodafone today so it's gone back with the the request of a new phone rather than repair so we'll see
Also if anyone is interested I obviously flashed a few custom roms and reset the counter to zero and installed original Vodafone software and have had no issues warranty wise
wakers said:
In fairness they suggested a new phone in Vodafone today so it's gone back with the the request of a new phone rather than repair so we'll see
Also if anyone is interested I obviously flashed a few custom roms and reset the counter to zero and installed original Vodafone software and have had no issues warranty wise
Click to expand...
Click to collapse
I seem to have been lucky with a Vodafone SGSII, I'd have insisted on a new phone from it's first problem, Vodafone have always been pretty good at replacing.
I am wondering however how did you manage to reset the flash counter ? Even with a USB Jig mine won't reset. It will go into download mode, but that's it. I presumed my six week old SGSII was a newer one a jig won't work on.
Before trying to reset the counter you should flash the old boot loader (pre-KI1) on, the new one cannot be reset safely with a jig. Works just fine after this
What Snakeforhire said i flashed the old bootloader reset the counter with the USB Jig then reflashed the new bootloader...
Updated through kies and sent back...
I did foolish thing of flashing Samsung S2 I9100P with Orange releases of Android 4. I not been able to find and Roms with the right details:
PDA: I9100PXXKJ4
PHONE: I9100PXXKI3
CSC I9100PO2UKJ2
An original or anything close would be appreciated, searched high and low for 2 days and tried loads with no luck...
I'm new to all this and have made mess of things any help and direction would be most appreciated.
Regards
The Noob
If you didn't make a backup/didn't keep a copy of this firmware I doubt anyone else will have a copy. You might as well use whatever Gingerbread stock firmware you can get from Samfirmware.com.
You could ask O2 service how much .
You could flash O2 ICS non P firmware and wait for release of the O2 P.
jje
Thnx JJEgan & MistahBungle
I had not made a back up, so that out the question, I have got a I9100 set up, just hope that the O2 update gets out and available.
Just can't seem to find any I9100P stock anywhere, just have to keep on hunting.......
Thank you
farscape67 said:
Thnx JJEgan & MistahBungle
I had not made a back up, so that out the question, I have got a I9100 set up, just hope that the O2 update gets out and available.
Just can't seem to find any I9100P stock anywhere, just have to keep on hunting.......
Thank you
Click to expand...
Click to collapse
If its released its on CHECKFUS .
jje
JJEgan
Thank you for that I have downloaded it and check on it was bit puzzled at Product Code tried Gt-i9100p and i900p
Nothing came up i keep checking many thanks for the help
Don't know how reliable this info is but I read this on the o2 forum..
" Nevermind to my last post, just had a very promising chat with an o2 guru, most help ive had so far and also a release date for ICS on S11NFC. * Theo: The end of next week. Theo: Is there anything else I can help you with? Arran: so by the 13/5/12 i will be able to update my NFC version to ICS? Theo: Yes, that's right. Theo: Is there anything else I can help you with? Arran: that's everything thankyou for all of your help * Hopefully this will hold up and be true "
Looks like us o2 GT-I9100P users just have to wait and see.
Sent from my GT-I9100P using Tapatalk 2
I spoken with both Samsung and O2 to day and they say its coming but there is no ETA
Samsung suggested as its a new phone to return it and get the S3 might be quicker then the update.
So I guess it a bit of a wait or take the advice and go for the S3 have 3 days to send it back on my 14 day return....
I to day received a Micro usd jig and it will not reset the counter, i am but doomed the phone is due to go back just waiting for the return bag to arrive...
this is just hopeless nothing I do seems to work out
ICS has just been released via kies for the I9100P (o2 network)
Sent from my GT-I9100P using Tapatalk 2
Just upgraded now was waiting out for the official ics before updating. Nice and smooth took 3 or 4 minutes and everything seems ok.
Chrome Beta check
Android beam check
Face unlock check
Google Wallet check
Other pros/cons
Pros
debugging tools for devs very handy
new mobile data usage is very good
Access to sharepoint and network folders from Exchange (not 100% sure if new )
New task manager
Cons
Email view seems bigger even on small
don't really like the graphic change of the pattern unlock
Notification bar icons seem "chunky"
Prefered GB volume control telling me in plain text which volume is being affected and not just an icon
Additional
Did we really need a new wifi icon :d
Not fussed with restart option, im used to holding button down to restart
Running temperatures seems to be lower down from average of 45C to 36/7C
Thanks for the information, just have to wait for the file to be uploaded to the web
Hey guys, first post, first real major issue I've encountered well rooting a phablet.
I have a ATT galaxy note, yesterday I rooted it and installed the Saurom ROM, everything was a breeze, I decided to try out ICS, I accidentally installed Criskelo onto the device before finding out it wasn't okay for the ATT note.
It hung on installing the rom itself and so I removed the battery imagining I could just revert to Saurom til I found a new ICS rom. But after I interuppted the ROM from installing, I get NO POWER! No download mode, nothing whatsoever on the screen =[ I'm ultra sad, best solution I find for the note is possibly a USB jig but I don't know if it will bring me back from this...
ANY HELP IS GREATLY APPRECIATED! I'm sitting here with a bricked note and a broken heart.
Don't be heartbroken just yet. This just happened to a friend of mine with his Note. I'm sending him your way. He's working today so I doubt he can get to you right away but I'm pretty sure he has the answer you need.
Sent from my SAMSUNG-SGH-I717 using xda premium
Have you tried accessing the phone with odin to see if it shows up there?
did you install CWM prior to flashing? try the three button combo to boot into recovery
did you backup prior to flashing ICS?
erikistehsex said:
Hey guys, first post, first real major issue I've encountered well rooting a phablet.
I have a ATT galaxy note, yesterday I rooted it and installed the Saurom ROM, everything was a breeze, I decided to try out ICS, I accidentally installed Criskelo onto the device before finding out it wasn't okay for the ATT note.
It hung on installing the rom itself and so I removed the battery imagining I could just revert to Saurom til I found a new ICS rom. But after I interuppted the ROM from installing, I get NO POWER! No download mode, nothing whatsoever on the screen =[ I'm ultra sad, best solution I find for the note is possibly a USB jig but I don't know if it will bring me back from this...
ANY HELP IS GREATLY APPRECIATED! I'm sitting here with a bricked note and a broken heart.
Click to expand...
Click to collapse
Some ROMs can damage the device's onboard flash. Surprisingly the Note is one of the few devices that you can actually physically break by flashing the wrong ROM.
erikistehsex said:
Hey guys, first post, first real major issue I've encountered well rooting a phablet.
I have a ATT galaxy note, yesterday I rooted it and installed the Saurom ROM, everything was a breeze, I decided to try out ICS, I accidentally installed Criskelo onto the device before finding out it wasn't okay for the ATT note.
It hung on installing the rom itself and so I removed the battery imagining I could just revert to Saurom til I found a new ICS rom. But after I interuppted the ROM from installing, I get NO POWER! No download mode, nothing whatsoever on the screen =[ I'm ultra sad, best solution I find for the note is possibly a USB jig but I don't know if it will bring me back from this...
ANY HELP IS GREATLY APPRECIATED! I'm sitting here with a bricked note and a broken heart.
Click to expand...
Click to collapse
You may need to contact mobile tech videos and get jtag unbricking service.
A bad flash happened to me in my first week of owning the phone so I was under the 30 day return policy with AT&T. I told them I was updating apps in the market, it got super hot, shut off, and would not power up.
They couldn't get it to turn on either, for obvious reasons, and they exchanged it no further questions asked. Hopefully your still in the return period.
Sent from my Icey G-Note Beast with XDA Premium 0_o
I done the same thing..odin should pick it up kust flash att recovery
Sent from my SAMSUNG-SGH-I717 using XDA
I'm sorry to say you probably have a hard brick on your hands. There's more info in this thread. I did the same thing myself. studacris's answer is the only option, you'll need to send it to someone who can do a JTAG repair on it, or you need to hope it's under warranty and send it back to AT&T and tell them that it just plain broke.
All notes are under warranty from Samsung still. They are for a year of purchase date. note has not been out a year.
Normally when I've had a a phone brick on me or a friends phone when out of the 30 day period, I would call 611 and have them send me a phone and when I received the new one I would mail the bricked one. It wasn't a big issue since the phones have manufacture warranties. Now they opened a device support center near buy and you can go and get a new one that same day.
Sent from my SAMSUNG-SGH-I717 using XDA
question for the OP's question, Samsung has that flash counter on the phone, I'm assuming with a bad flash like this it doesn't go up. But does it? And it if does, would Samsung be able to tell what happened? I know Samsung has a hard stance on flashers. To OP, I did the same thing, and I resorted to getting the JTAG thing done, the few places I've came across won't charge unless they can fix it. And they only charge like $50.
I tried jtag. Waste of money. They could not save my phone, plus they charged me $30 for looking at it.
Not to mention I lost out on my shipping.
Sent from my SAMSUNG-SGH-I717 using xda premium
The last resort is to try a Jig to force download mode. If that fails, you are done. You can look on your PC in the Device Manager. In there it will show you an "state" when you connect the device trying to get into Download Mode. Google that state. I am guessing you are getting the bad one which at this time is a device exchange.
Dear All,
today I ran into a massive problem with my brand new i9300, which i bought 2 days ago and literally bricked the phone in very unusual way - no network available so I can not make/receive calls, texts or data.
I bought the phone in Bangkok(Thailand), as is(without warranty as it is not from original thai distribution therefore I saved bit over 100 bucks). When I got home and start exploring the phone a little I noticed weird thing - when booting up the logo is GT-I9300T and when I checked on firmware, it was showing GT-I9300T as well but the paper boxe(written in french) showed GT-I9300 as well as the sticker under the battery(GT-I9300). The phone was unlocked and rooted, can not remember the firmware it was equipped with but it was TELSTRA branded(boot on/off animation plus lots of crap appz TELSTRA related). Plus there were few bugs like phone was not able to lock itself(pin, face unlock etc. etc. - nothing was working, no unlocking needed because it never locked anyway) no matter what I did. That really annoyed me so I decided to flash DarkyROM III v3(have been playing with DarkyROMs for last 2 years on my SGS) as I learned that i9300 and i9300T firmwares are interchangable anyway so it should not matter. So I flashed according the guide, no problems encountered at all, it went very smooth. But after the phone booted up, despite everything else was working nicely, there was no signal/network available. Only the "crossed-circle" in the top-right corner where usually the signal bars are.
So I went to the service mode, tried to force different bands in both - GSM and WCDMA but no luck. Still no networkd available. So I decided to give a go to few another modems - both versions i9300 and i9300T - flashed in CWM and Odin too - no luck, still the same. So I reflashed few SAMSUNG stock firmwares plus tried the various modems again, still the same result - crossed circle instead of signal bars, no network. So I went to SAMSUNG SERVICE CENTER, they were very helpful, played with my phone for almost an hour, flashed latest official thai firmware but the result is still the same. No network. They even reflashed the initial bootup animation so now it is showing correctly GT-I9300. They checked the imei+s/n and confirmed the phone is I9300 coming from France originaly(french distribution) and apologized, because it is french phone they do not have the required firmware/software on hand so that they can help me and fix my phone. So what can I do? I guess if SAMSUNG Service Center can not help me, does it mean I should throw away my phone into the nearest thrashbin? I spent almost 600USD on it - its a lots of money for me. Well lesson for me is - never buy anything from unofficial distribution!
But please let me ask you guys - any idea what can I do to make it work again? Anyone else have similar experience as me?
The phone shows same IMEI as on the paper sticker below the battery, but the serial number shows ony zeros(0000000) instead the letters/numbers which are mentioned on the sticker.
Any more info, please let me know. I will appreciate any suggestion/help/assistance to make my SGS3 work again, please please please help me!
Thanks a lot, kind regards
Tomas
Are you absolutly sure that this phone wasnt stolen? It can be locked by IMEI If it was.
By Tapatalk 2
SirKunon said:
Are you absolutly sure that this phone wasnt stolen? It can be locked by IMEI If it was.
By Tapatalk 2
Click to expand...
Click to collapse
I have no idea, how can I find out? I guess SAMSUNG Service Center would tell me, no? And the phone was working perfectly until the flash.
Its not brand new if its been rooted .
See the recent posts regarding the T Model and network .
jje
Maybe this phone was simunlocked in some kind of temporary way. After flashing original firmware efs was rebuilded with simlock to original carrier, Telstra in this case? I dont think you have got their sim to check this. Maybe try few ways to simunlock now, just after flashing a tripplefile stock firmware with mx.pit and repartition checked in Odin.
Take out your current simcard and external sd card while flashing.
By Tapatalk 2
@JJEgan: thanks but as per SAMSUNG SC the unit is i9300, not i9300t as was flashed originally.
@SirKunon: how complicated is it to simunlock? Do I need some specialized equipment/sw? So what you suggest is to find stock firmware with three separate files - pda, phone, csc - and flash them together with mx.pit repartition ticked? Can't that mx.pit do some more harm? And how about bootloader, what is it really good for?
Indopilot said:
@SirKunon: how complicated is it to simunlock? Do I need some specialized equipment/sw? So what you suggest is to find stock firmware with three separate files - pda, phone, csc - and flash them together with mx.pit repartition ticked? Can't that mx.pit do some more harm? And how about bootloader, what is it really good for?
Click to expand...
Click to collapse
Bootloader is usualy included in all firmwares and flashed, no matter is it one or three files. But generaly only roms with separete csc, pda and modem include script commands for wiping data (dalvik also) and cache just after flashing a firmware. Some carriers are using diffrent than stock recommended partition layout and that why i suggest repartition - to wipe all junks from Telstra branding.
About simunlock You should search this forum, I didnt do that with my s3 becouse its stock unlocked. I only debranded my phone from T-mobile to stock. On sgs and sgs2 i have to use some soft, I dont remember how its names. From efs folder (root needed) extract nvdata.bin in this file are informations about IMEI and simlock encoded. You need to find that software which will remove simlock bytes and after that push nvdata.bin back to efs partition and set right owner (radio or root) and permissions. Maybe three is also easiest way to do that. But root always will be necesary.
This is only things that may help if sammys SC itself failed.
By Tapatalk 2
Easy solution for you :-
http://forum.xda-developers.com/showthread.php?t=1838480
Can people stop using the term "bricked" when it's clearly not please.
Sent from my GT-I9300 using xda app-developers app
riso123 said:
Can people stop using the term "bricked" when it's clearly not please.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I'm sure people like me can stop using the term "bricked" if you know a better term for a cell you can not use for calling, texting and using data anymore(sorry but phone u can not use for its main purpose is a brick to me). But honestly I would expect more from a senior member like u than an "advice" like that just to add an 1 extra count on your posts count. If you don't know how to or don't want to help, just say that straight away or don't reply at all. Your comment like this is not gonna help anyone and certainly no-one is gonna learn anything new from it.
Indopilot said:
I'm sure people like me can stop using the term "bricked" if you know a better term for a cell you can not use for calling, texting and using data anymore(sorry but phone u can not use for its main purpose is a brick to me). But honestly I would expect more from a senior member like u than an "advice" like that just to add an 1 extra count on your posts count. If you don't know how to or don't want to help, just say that straight away or don't reply at all. Your comment like this is not gonna help anyone and certainly no-one is gonna learn anything new from it.
Click to expand...
Click to collapse
What does me being "senior" have to do with it? It doesn't make me any more of a role model, doesn't earn me extra money and doesn't make my poopie smell nice...
Your phone is not bricked, it's just lacking in functionality at the moment. It's likely something that can be fixed... if it was bricked, you would have no functionality and no way to fix the device, thus making it a useless brick...
So yeah, my original post stands... your using the term, along with a lot of other people, incorrectly and it's annoying.
Sent from my GT-I9300 using xda app-developers app
try flashing it with stock rom for australia.
riso123 said:
What does me being "senior" have to do with it? It doesn't make me any more of a role model, doesn't earn me extra money and doesn't make my poopie smell nice...
Your phone is not bricked, it's just lacking in functionality at the moment. It's likely something that can be fixed... if it was bricked, you would have no functionality and no way to fix the device, thus making it a useless brick...
So yeah, my original post stands... your using the term, along with a lot of other people, incorrectly and it's annoying.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Well what else can I add, maybe just "thank you very much for your very useful advice, it's very much appreciated and it helped me a lot". But on a serious note now, obviously you have absolutely no idea how to help as the SAMSUNG SC does, but at least they don't try to be a smart ass and admit that straight away. Anyways my apologies to everyone who got offended by my term "brick", I should use more proper term "useless". I hope this will make you happy now so you can get a good night sleep Mr. Smart###!
Indopilot said:
Well what else can I add, maybe just "thank you very much for your very useful advice, it's very much appreciated and it helped me a lot". But on a serious note now, obviously you have absolutely no idea how to help as the SAMSUNG SC does, but at least they don't try to be a smart ass and admit that straight away. Anyways my apologies to everyone who got offended by my term "brick", I should use more proper term "useless". I hope this will make you happy now so you can get a good night sleep Mr. Smart###!
Click to expand...
Click to collapse
You have been given the needed advise to fix the problem. The only reason that flashing your carrier and country brand firmware would be that your IMEI has been blocked. If your IMEI is blocked then the phone is likely a stolen unit.
What more advise do you want/need, Mr Arrogant?
Edit: oh, and of course your EFS could be screwed. But again, flashing to stock would fix that too...
Sent from my GT-I9300 using xda app-developers app
First if all, not all country implemented the IMEI blocking.
It requires huge resource to maintain the database.
Which country and network you are trying to use it at?
Secondly I haven't seen one method of flashing to change the boot logo like SAMSUNG SC did.
Can the Thai have done the same originally?
What is the model number under the battery.
Sent from my GT-P1000 using xda app-developers app
priyana said:
First if all, not all country implemented the IMEI blocking.
It requires huge resource to maintain the database.
Which country and network you are trying to use it at?
Secondly I haven't seen one method of flashing to change the boot logo like SAMSUNG SC did.
Can the Thai have done the same originally?
What is the model number under the battery.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Sorry I have no idea about IMEI blocking - maybe it is not that common here due to huge amount of mobiles in use around here? I am in northern Thailand, trying to use it on DTAC and yesterday got 2 more SIMs to try another operators - AIS and TRUEMOVE. Even tried my czech and indonesian SIMs, without luck.
I do not know the way SAMMY SC used to change my boot logo but they did it somehow. And this morning I dropped my S3 to one of those street shops specialised in unlocking and repairing phones - they said should be no problem to fix it, left it there for an hour but they returned it to me with apologies that they reflashed what they could and tried different firmwares but no luck. And BTW they reflashed the boot logo too - now it is back to GT-I9300T(which is annoying, will go to SC again on Monday to reflash it back to I9300).
The model number under the battery states: GT-I9300 and SAMMY SC confirmed I9300.
And yes I am sure despite the fact the phone has been sold to me as brand new, someone must have tampered with it - I guess to unlock it or something - it was rooted and CWM was installed. As I mentioned according SAMMY SC the phone comes from french distribution, is GT-I9300 but it was TELSTRA(I think australian) branded and flashed with GT-I9300T.
And to top it up - KIES can not identify what was the original FW for this unit - after inserting the model and S/N into KIES, it just says to check the S/N again and insert the correct one. Real mistery!!!:crying:
But anyway thanks a lot for help and suggestion priyana,
Tomas
Indopilot said:
Sorry I have no idea about IMEI blocking - maybe it is not that common here due to huge amount of mobiles in use around here? I am in northern Thailand, trying to use it on DTAC and yesterday got 2 more SIMs to try another operators - AIS and TRUEMOVE. Even tried my czech and indonesian SIMs, without luck.
I do not know the way SAMMY SC used to change my boot logo but they did it somehow. And this morning I dropped my S3 to one of those street shops specialised in unlocking and repairing phones - they said should be no problem to fix it, left it there for an hour but they returned it to me with apologies that they reflashed what they could and tried different firmwares but no luck. And BTW they reflashed the boot logo too - now it is back to GT-I9300T(which is annoying, will go to SC again on Monday to reflash it back to I9300).
The model number under the battery states: GT-I9300 and SAMMY SC confirmed I9300.
And yes I am sure despite the fact the phone has been sold to me as brand new, someone must have tampered with it - I guess to unlock it or something - it was rooted and CWM was installed. As I mentioned according SAMMY SC the phone comes from french distribution, is GT-I9300 but it was TELSTRA(I think australian) branded and flashed with GT-I9300T.
And to top it up - KIES can not identify what was the original FW for this unit - after inserting the model and S/N into KIES, it just says to check the S/N again and insert the correct one. Real mistery!!!:crying:
But anyway thanks a lot for help and suggestion priyana,
Tomas
Click to expand...
Click to collapse
Hi Tomas,
I am experiencing the same problem have u been able to fix your phone? If so how did you do it? I hv tried flashing so many firmwares and took it to like 10 stores without success. Imei is shown also, but sn differs from the one on the sticker. Thanks!
Yes, the issue has been solved easily and free of charge although Sammy SC in Czech Republic and Thailand told me it is a hardware issue and motherboard has to be replaced(costs 225UDS in Thailand and 250EUR in Czech Republic). I repeat it is a lie and trick how to rip you off of some cash - it is SW issue only and I found a place where it has been fixed in less than half an hour and free of charge. Sorry, I m travelling now, will give u more details later Keep hope alive!
Sent from my GT-I9300 using xda app-developers app
manormachine said:
Hi Tomas,
I am experiencing the same problem have u been able to fix your phone? If so how did you do it? I hv tried flashing so many firmwares and took it to like 10 stores without success. Imei is shown also, but sn differs from the one on the sticker. Thanks!
Click to expand...
Click to collapse
You need to visit some service centre wih SPT box.
It will make your phone functional.
But you need to remove modem before flashing roms
If you flash modem after repair you will loose signals.
muhammad.ali123 said:
You need to visit some service centre wih SPT box.
It will make your phone functional.
But you need to remove modem before flashing roms
If you flash modem after repair you will loose signals.
Click to expand...
Click to collapse
So this issue can not be solved and I will have to stay on the same modem forever? So how can we ever update our firmware if modem can not be tampered with? It sounds like this issue bans us completely from updating our firmware I wanted to try other stock/modded firmwares or at least kernels but now I m afraid to touch the firmware in order not to lose signal again:'(
Sent from my GT-I9300 using xda app-developers app
Hello everyone here
I am planning to get the new old SGS3, but after looking in this forum, I am quite hesitating, because of samsung behaviour, I explain:
- Few months after getting my sgs2 I've heard of Brickbug and Exynos exploit, I got cold sweats each time hoping there will be a solution/fix and there was, I swore to never buy a Samsung phone before a quarantine period of at least one year, AND I WAS RIGHT ! This may look wrong but I'm not as rich as that... (Just letting time to tell me if it is a safe device and not an - accidental - crap) anyway, lets go to the questions:
- Is the sudden death fixed in the way the brickbug of sgs 2 or there still some risk to get my new old sgs 3 born dead ? I'm confused reading opposed reviews of the problem !
- Will flahing a 4.0.4 sgs 3 to 4.1.2 get the device operator locked back as the sgs 2 did, if yes could it be resolved with galaxsimunlock ?
(in all cases, I will probably use neatROM with a safe philz kernel)
- I a buy a SGS 3 with 4.1.2 jellybean out of the box, have I a chance that it will be enough new to have an eMMC chip which is not affected ? (I think the bug came with the first made eMMC chips, but I may be wong)
- If I get an SGS 3 with 4.0.4 android, should I flash it asap to safe 4.1.2 (XXELKC or above) as if it has fire and I must extinguish it ?
- Finnally, going through all this trouble, is the SGS 3 worth to get ?
Hi there friend,
first of all I strongly suggest you read the SDS thread:
http://forum.xda-developers.com/showthread.php?t=1993044
It has all of your answers.
As for my personal opinion it's a great device I'm using it for almost a year now after coming from the nexus s
Cheers
leech4 said:
- Is the sudden death fixed- I'm confused reading opposed reviews of the problem !
Click to expand...
Click to collapse
What opposed views? Everything in that thread is correct.
- Will flahing a 4.0.4 sgs 3 to 4.1.2 get the device operator locked back
Depends upon unlock method but NO if unlocked by network .
jje
I don't know how about sudden death problem but Samsung fixed freeze problems with XXEMB1 firmware, so you can't say that Samsung forgot it's ex-flagship,because it's still very popular phone and it's still gets all latest updates and etc. So in general it's still worth to buy it.
The freeze problems are a result of the sds fix
Sent from my GT-I9300 using Tapatalk 2
Thank you for your answers
eytan123 said:
Hi there friend,
first of all I strongly suggest you read the SDS thread:
http://forum.xda-developers.com/showthread.php?t=1993044
It has all of your answers.
As for my personal opinion it's a great device I'm using it for almost a year now after coming from the nexus s
Cheers
Click to expand...
Click to collapse
rootSU said:
What opposed views? Everything in that thread is correct.
Click to expand...
Click to collapse
I'll do, but while reading that thead, I felt like it is a very frequent problem so I stopped at the few first pages and looked elswhere
Regarding opposed views, I've found in at least two forums, that even after flashing a "secure" ROM, there was some devices that still present the symptoms of what I call "Alzheimer S III" : a degenerative evolution of memory that leads to death :silly:
JJEgan said:
- Will flahing a 4.0.4 sgs 3 to 4.1.2 get the device operator locked back
Depends upon unlock method but NO if unlocked by network .
jje
Click to expand...
Click to collapse
I hope the Galaxsimunlock will do the job, because it will probably not be an operator unlock
Simonna said:
I don't know how about sudden death problem but Samsung fixed freeze problems with XXEMB1 firmware, so you can't say that Samsung forgot it's ex-flagship,because it's still very popular phone and it's still gets all latest updates and etc. So in general it's still worth to buy it.
Click to expand...
Click to collapse
rootSU said:
The freeze problems are a result of the sds fix
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I hope you are right, I'll read furthermore but the balance of opinion for me at the moment leans to get that phone, maybe on the week end
Did anyone got an SGS III out of the box with JB, and what was the version
By the way I've read somwhere that LL4 stock firmware "locks" the phone and stops any downgrading, makes triangleaway not woking anymore and removes abylity to reset flash counter, can anyone confirm that ?
Fyi, all s3's manufactured since December 2012 have upgraded firmware on the emmc. Typically imei starting 35 instead of 33 are good.
There are some reports of sds after 4.1.2 but I'm still yet to find one where it was 100% substantiated (meaning full stock, never rooted, confirmed sds).
We're still not certain that partial damage could occur before upgrade to fixed versions if android....
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
Fyi, all s3's manufactured since December 2012 have upgraded firmware on the emmc. Typically imei starting 35 instead of 33 are good.
There are some reports of sds after 4.1.2 but I'm still yet to find one where it was 100% substantiated (meaning full stock, never rooted, confirmed sds).
We're still not certain that partial damage could occur before upgrade to fixed versions if android....
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Pretty good to know, thank you for the information