[q] emmc_cap erase superbrick - Galaxy S III Q&A, Help & Troubleshooting

Hi guys,
I am getting my S3 tomorrow and wanted to MAKE SURE wether the S3 also has the superbrick risk as the Galaxy Note has ?
Or is it a typical ICS 4.0.3 bug that doesn`t happen on 4.0.4?

That was kernel related.Samsung made a huge f...up.but it was corrected.gs2 suffered from same error.I haven't read anything yet.
Gs3 is lovely a beast

I'm rooted and custom kerneled up with no issues at all.
Sent from my GT-I9300 using xda app-developers app

zodiaxe66 said:
That was kernel related.Samsung made a huge f...up.but it was corrected.gs2 suffered from same error.I haven't read anything yet.
Gs3 is lovely a beast
Click to expand...
Click to collapse
It still isn`t corrected by samsung till now, some devs only diasbled the emmc_cap erase issue in their kernels. But good to know the S3 doesn`t suffer this bug :fingers-crossed:

It was a firmware issue in the SSD-controller (as it usually is with SSD's)
Firmware 0x19 had the issue, Firmware 0x25 does not.
(And no there is no way to upgrade firmware... sadly)

Related

[Q] ICS Kernals Causing Bricks in Galaxy Note (GT-N7000)

I've read on several forums that the ICS kernals are causing hard bricks due to problems with the emmc. Has anyone had this issue with the SGH-I717? I am running the Serophim-Troposphere ROM on my Galaxy Note SGH-I717 and am a little nervous that when I go to flash something else (whether is be ICS of GB), that I will run into this issue and brick my phone. People are saying that kernal becomes corrupted when data wipes and factory data resets are done in Clockworkmod or other recovery programs. Basically, all I'm asking is has anyone who is running a SGH-I717 had this issue with an ICS kernal or is the problem contained with the GT-N7000 due to its different processor?
Thanks for any help!!!
kferguson84 said:
is the problem contained with the GT-N7000 due to its different processor?
Click to expand...
Click to collapse
You answered your own question. That is a different phone, not ours.
You have nothing to worry about.
Awesome! Thanks for the confirmation.
Sent from my SAMSUNG-SGH-I717 running Seraphim-Troposphere ICS ROM

Cannot power on my GS3!

4 months ago i've rooted my Galaxy S3 international (I-9300). Before rooting i took a nandroid backup of the Samsung's ICS. Then i flashed CM10 and recently (1 month ago) i flashed CM10.1. Everything was working OK (except some issues that come with the CM10-10.1). I also came against the SOD (Screen of Death) but as the devs warned us i was OK with that. From time to time i flashed a newer version of the CM10.1 nightly (recent one was 4th of Jan 2013).
Today as i was sitting in my office i picked up my device and pressed the power button just to check the time. The device did not respond and i presumed that it was another case of SOD. So i removed my battery and put it back inside as i always did when a SOD occured. I long-pressed the power button but nothing happened. I went to the nearest Samsung supplier and i bought a brand new Samsung battery to replace the old one but the device never powered up. Now i am stack with a device that cannot power up. I cannot get into download mode as well.
Is it a case of a bricked device? If it is, is there anything i can do to bring it back to life?
Thanks in advance!
In this case you cannot do much....take it to center and require motherboard replacement, if its case of brickbug it will he warranty covered....right now im interested if you flashed XXELLA or newer bootloader or did you flash kernel compiled from 7th source from samsung?
Sent from my GT-I9300 using xda app-developers app
tsangaris said:
4 months ago i've rooted my Galaxy S3 international (I-9300). Before rooting i took a nandroid backup of the Samsung's ICS. Then i flashed CM10 and recently (1 month ago) i flashed CM10.1. Everything was working OK (except some issues that come with the CM10-10.1). I also came against the SOD (Screen of Death) but as the devs warned us i was OK with that. From time to time i flashed a newer version of the CM10.1 nightly (recent one was 4th of Jan 2013).
Today as i was sitting in my office i picked up my device and pressed the power button just to check the time. The device did not respond and i presumed that it was another case of SOD. So i removed my battery and put it back inside as i always did when a SOD occured. I long-pressed the power button but nothing happened. I went to the nearest Samsung supplier and i bought a brand new Samsung battery to replace the old one but the device never powered up. Now i am stack with a device that cannot power up. I cannot get into download mode as well.
Is it a case of a bricked device? If it is, is there anything i can do to bring it back to life?
Thanks in advance!
Click to expand...
Click to collapse
Sudden death, all you can do is get a motherboard replacement at a service center, however they may never know you flashed CM10.1 because the NAND is dead.
gaspernemec said:
In this case you cannot do much....take it to center and require motherboard replacement, if its case of brickbug it will he warranty covered....right now im interested if you flashed XXELLA or newer bootloader or did you flash kernel compiled from 7th source from samsung?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick reply but i am not sure i can help you with the bootloader! I am not an advanced user. I just used Odin v3.04 to flash CF-Root-SGS3-v6.4. When i finally rooted my device i downloaded the CM10 and afterwards the CM10.1 rom and flashed it along with the GAPPS. And then i used a program to match the modem with the RIL (XXDLID). Ofcourse i fixed permissions.
One thing i need to know? Does the phone stays in the warranty if you root it?
delsus said:
Sudden death, all you can do is get a motherboard replacement at a service center, however they may never know you flashed CM10.1 because the NAND is dead.
Click to expand...
Click to collapse
You mean that i shouldnt say anything about root and CM10.1 right?
Also, is there a way for the technicians to find out that i've rooted the device and flashed CM10.1? I mean on a device that it cant even power on!
ps: i live in Cyprus (small island in the meditteranean sea) , so there isnt any advanced service center to examine my motherboard (at least i hope so).
tsangaris said:
You mean that i shouldnt say anything about root and CM10.1 right?
Also, is there a way for the technicians to find out that i've rooted the device and flashed CM10.1? I mean on a device that it cant even power on!
ps: i live in Cyprus (small island in the meditteranean sea) , so there isnt any advanced service center to examine my motherboard (at least i hope so).
Click to expand...
Click to collapse
Don't mention it, don't say anything about firmware, if they ask play dumb and just say the latest version, it's up to them to prove your warranty is void, also is Cyprus in the EU? If so check this out http://forum.xda-developers.com/showthread.php?t=2092530&highlight=eu
In short for your warranty to be voided by flashing Samsung has to prove that it was CM10.1 that caused the problem.
I don't think this will be needed though because your NAND is completely dead so it will be extremely hard if possible for them to prove you flashed anything.
delsus said:
Don't mention it, don't say anything about firmware, if they ask play dumb and just say the latest version, it's up to them to prove your warranty is void, also is Cyprus in the EU? If so check this out http://forum.xda-developers.com/showthread.php?t=2092530&highlight=eu
In short for your warranty to be voided by flashing Samsung has to prove that it was CM10.1 that caused the problem.
I don't think this will be needed though because your NAND is completely dead so it will be extremely hard if possible for them to prove you flashed anything.
Click to expand...
Click to collapse
Yes Cyprus belongs to EU.
I will not mention a thing about firmware and CM hoping they dont find it out.
In the meantime, if they replace the motherboard, i will be running Android with Touchwiz by default?
tsangaris said:
Yes Cyprus belongs to EU.
I will not mention a thing about firmware and CM hoping they dont find it out.
In the meantime, if they replace the motherboard, i will be running Android with Touchwiz by default?
Click to expand...
Click to collapse
Yes you will be on touchwiz, but you can always change that
I have no idea which version though, it depends what they flash at the factory.
delsus said:
Yes you will be on touchwiz, but you can always change that
I have no idea which version though, it depends what they flash at the factory.
Click to expand...
Click to collapse
Samsung should worry about their skin, because i am a user that rooted his device to flash a custom ROM, then the device is not booting by any means and i am thinking to root it again after the motherboard is replaced!!
By the way, the problem on the motherboard is caused 100% because i root the device??
Thanks so much for your answers!
tsangaris said:
Samsung should worry about their skin, because i am a user that rooted his device to flash a custom ROM, then the device is not booting by any means and i am thinking to root it again after the motherboard is replaced!!
By the way, the problem on the motherboard is caused 100% because i root the device??
Thanks so much for your answers!
Click to expand...
Click to collapse
No it is not caused by rooting your device. Your case is a typical Sudden Death Syndrome one. For more info go here:
http://forum.xda-developers.com/showthread.php?t=2091045
You said that the last CM 10.1 you installed was from 04.01.13? Well in that case the Samsung Update7 source wasn`t applied yet to CM10.1 Kernel, so the Kernel was not secure.
Scarface1991 said:
No it is not caused by rooting your device. Your case is a typical Sudden Death Syndrome one. For more info go here:
http://forum.xda-developers.com/showthread.php?t=2091045
You said that the last CM 10.1 you installed was from 04.01.13? Well in that case the Samsung Update7 source wasn`t applied yet to CM10.1 Kernel, so the Kernel was not secure.
Click to expand...
Click to collapse
I didnt find the time to read the thread you post (i am reading it later on). So the not secure Kernel could cause this?
tsangaris said:
I didnt find the time to read the thread you post (i am reading it later on). So the not secure Kernel could cause this?
Click to expand...
Click to collapse
Yes there is a problem with a specific type of eMMC chips in the SIII. There is plenty of evidence now that Samsung fixed this issue with the Update7 Source release and most S3 Kernels have this fix by now. You can read it in detail by clicking the link I posted a couple of posts ago.
I hope that they will repair your device without any problems but they should and if you couldn`t even access download mode it`s pretty much impossible to find out that you had Root or a custom ROM installed.
tsangaris said:
I didnt find the time to read the thread you post (i am reading it later on). So the not secure Kernel could cause this?
Click to expand...
Click to collapse
Some people are saying that the kernel fixes it some are saying they havent, but the service center should fix it because its a known problem.
Also the latest kernel has only been rolled out in UK and Spain. If there has not been a stock update available in your country there is really nothing they can do.
Sent from my GT-I9300 using xda premium
delsus said:
Some people are saying that the kernel fixes it some are saying they havent, but the service center should fix it because its a known problem.
Also the latest kernel has only been rolled out in UK and Spain. If there has not been a stock update available in your country there is really nothing they can do.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I don`t know of any case where someone had an SD while having a fixed Kernel installed. But you are right that nobody knows 100% if the fix really works.
Thank you all for your responses!! I am taking my GS3 to the place that i bought it for repairing first thing tomorrow!
I will let you know of the outcome!
Again, thanks a lot!!
tsangaris said:
Thank you all for your responses!! I am taking my GS3 to the place that i bought it for repairing first thing tomorrow!
I will let you know of the outcome!
Again, thanks a lot!!
Click to expand...
Click to collapse
Good luck
Hey guys,
I have a similar problem except that my screen turns on and shows the Galaxy S3 logo when I try to power it on but it won't go further (shows logo until I pull the battery). It doesn't boot into recovery either but I can start download mode.
The phone just turned off while I was listening to music. I think I was running Omega v27.
So my question is: Should I try flash a stock ROM since I can boot into download mode? And is this even "sudden death"?
Thanks in advance!
Half of sudden death. You should also get the phone to samsung
avrano1 said:
Hey guys,
I have a similar problem except that my screen turns on and shows the Galaxy S3 logo when I try to power it on but it won't go further (shows logo until I pull the battery). It doesn't boot into recovery either but I can start download mode.
The phone just turned off while I was listening to music. I think I was running Omega v27.
So my question is: Should I try flash a stock ROM since I can boot into download mode? And is this even "sudden death"?
Thanks in advance!
Click to expand...
Click to collapse
I would take that to samsung, toy could try flashing stock but if it wasn't a failure flashing something I'm not sure it would work.
I would imagine it will fail before it tries to flash.
Sent from my GT-I9300 using xda premium
vasp3690 said:
Half of sudden death. You should also get the phone to samsung
Click to expand...
Click to collapse
Tried to flash the + RESCUE FIRMWARE SGSIII I9300 + but it doesn't work. It can't flash the .pit-file and it doesn't work without either.
So I really have to return it but:
since the phone boots into download mode they will see that I used a custom firmware. Any chance to change this?

[Q] Chainfire damaged my SGS vibrant cm10

chainfire app just completely damaged my 500$ samsung Galaxy s when I installed the DRIVERS and when I started the reboot so the drivers take effect and it got stock on doot logo. And I got to Recovery menu and I had a old backup but when I was restoring , the phone canceled and switched off and it got stock on the Vibrant logo. No recovery menu, no flashback. Nothing!!! I send the phone to experts and they told me that the phone is total wasted... if you know how to fix it ,tell me how. Its an Gallaxy s vibrant t959 t-mobile
On the list of soported android phones it was my gallaxy s and it was an lie!
If ther eny way to demand the app on playstore.... answer that to...
THANKS
Betfoyet said:
chainfire app just completely damaged my 500$ samsung Galaxy s when I installed the DRIVERS and when I started the reboot so the drivers take effect and it got stock on doot logo. And I got to Recovery menu and I had a old backup but when I was restoring , the phone canceled and switched off and it got stock on the Vibrant logo. No recovery menu, no flashback. Nothing!!! I send the phone to experts and they told me that the phone is total wasted... if you know how to fix it ,tell me how. Its an Gallaxy s vibrant t959 t-mobile
On the list of soported android phones it was my gallaxy s and it was an lie!
If ther eny way to demand the app on playstore.... answer that to...
THANKS
Click to expand...
Click to collapse
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
Odin back to stock.
If you're on jb, I bet it doesn't work. If on older rom, try an ics one.
Sent from my Galaxy S III
500$ Samsung Galaxy S eh? If you paid for $500 for your vibrant anytime within the last year or so, then I think you have bigger problems to worry about than a brick.
Also, you really shouldn't house any animosity towards Chainfire. He is an excellent developer who has done so much for the modding community.
As for Chainfire3D, I can tell you from first hand experience that it does, in fact, work for the Vibrant. Please keep in mind that with anything involving modding your device, you accept the risk onto yourself willingly.Chainfire did not force you to do anything, that was your choice - you ought to think about these things before suggesting that he lied in regards to the supported devices, you just did not read the directions properly. How do I know this? Because in the description of the app clearly says, and I quote,
"!! For Froyo and Gingerbread ONLY. NOT COMPATIBLE with Honeycomb/ Ice Cream Sandwhich/Jelly Bean !!"
Guess what CM10 is. That's right, not Froyo or Gingerbread.
I used cf3d with ics perfectly fine, actually.
Sent from my SGH-T999 using xda app-developers app
iKoolkid said:
I used cf3d with ics perfectly fine, actually.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I did too actually... But that isn't the point ^^ when I used chainfire on ICS I had already talked with enough people to know that it worked... but I was still accepting the potential risk that it would not work since chainfire didn't recommend using it on anything above gingerbread. I never used it on jb because I heard stories that it didn't work and could really damage the phone... I did my research and read before doing things, this person just jumped in blind and is blaming a respected dev for his own inability to read.
Sent from my Galaxy S3
Xenoism said:
I did too actually... But that isn't the point ^^ when I used chainfire on ICS I had already talked with enough people to know that it worked... but I was still accepting the potential risk that it would not work since chainfire didn't recommend using it on anything above gingerbread. I never used it on jb because I heard stories that it didn't work and could really damage the phone... I did my research and read before doing things, this person just jumped in blind and is blaming a respected dev for his own inability to read.
Sent from my Galaxy S3
Click to expand...
Click to collapse
True, true. Well maybe my vibe got damaged from the soft brick cf3d used. But yes, from both of us, OP, READ. Search before you post and right now, odin to stock and you have to start from stock, then ics, then jb. Do not restore a backup of a jb rom from an ics, froyo, or anything non jb. Same with other versions, because you can bootloop or soft brick the phone. You're lucky it is just soft bricked.
EDIT: If you have read...
1. Sending the phone to the experts (whom probably have specific knowledge of vibrant rooting and bricks) would've been off your list.
2. You would've known NOT to restore that backup.
And now, as many have said, we or any other devs are not responsible of your flashing even if it should've worked and we are also not responsible for things leading:
Bricks
Dead sd cards
Eu bug
Death of a loved one from brick rage
A hole in your wall from above reason
Thermo-nuclear war
Or catz poppings ups frum ur screenz afdur downroading rom asking fur cheezbergers.
Or a phone repairer finding pr0n on your phone when checking it out. We all know how bad that is.
Sent from my SGH-T999 using xda app-developers app
we have the same situation.. in my case it just boot loop.. i try to restore, but it keep restarting..
so back to stock, GB, and to cm10.1 again.. (do I need to flash GB if my stock rom is eclair before flasing to JB?) good thing to have a titanium backup! my phone usable again after more or less 20mins.
Yes. Flash cm7 first.
Sent from my Galaxy S3
Xenoism said:
Yes. Flash cm7 first.
Sent from my Galaxy S3
Click to expand...
Click to collapse
thanks! now I dont install chainfire anymore..
iKoolkid said:
If you're on jb, I bet it doesn't work. If on older rom, try an ics one.
Sent from my Galaxy S III
Click to expand...
Click to collapse
Noooo my problem is not the Rom... my problem is that my sgs vibrant. It's stock on vibrant logo. First boot picture, not boot loop.
It doesn't open recovery!
You enabled chainfire drivers on jb (first mistake) and then you tried to restore a stock backup of eclair while you were still on jb (second mistake). You can't jump from jb down to stock like that, only from jb to ics and some later versions of gingerbread. What you want to do is boot into download mode and revert to stock the correct way. The moral of the story is when messing with your phone, read, read, read before doing anything ever. You're lucky, because it sounds like your phone will be just fine if you properly Odin back to stock via download mode. However, I warn you...if you Odin wrong, there is a good chance of ruining your phone, so read this time and make sure to do it correctly.
Sent from my Galaxy S3

[Q] HELP!!using international galaxy s2 i9100 screen on sgh i777

hello ,
i bought a factory unlocked galaxy s2 sgh-i777 and i m using it in india but recently i broke it's display/screen and now i got it repaired by samsung india ...they replaced my old screen with the screen of i9100...because of which only theback and the setting capacitive buttons are working and the home button is not working...so can i install official jellybean of i9100 on my sgh-i777 in order to make the home button to work?
i am currently using the button savior app but i m trying to sell the phn anf it would be difficult to sell it because of it's home button nt functioning...
please help...
thanks..
mrinal
Hey Mrinal. Well even I stay in India and I have been using an unlocked SGH-I777. My display has been cracked but ts still working as perfect as it was before.
Well about your issue, I can say is even if you flash a I9000 ROM, you may get the home button to work, but you will have to use the default kernel which comes inside the ROM itself. But as it is meant for the I9i000 you may face certain problems(software related) if you use it on SGH-I777.
So all I can say is if you are okay with the issues that may be faced, go ahead and give it a try.
And please let me know how much did they charge you to replace the display.
gireeshtty9 said:
Hey Mrinal. Well even I stay in India and I have been using an unlocked SGH-I777. My display has been cracked but ts still working as perfect as it was before.
Well about your issue, I can say is even if you flash a I9000 ROM, you may get the home button to work, but you will have to use the default kernel which comes inside the ROM itself. But as it is meant for the I9i000 you may face certain problems(software related) if you use it on SGH-I777.
So all I can say is if you are okay with the issues that may be faced, go ahead and give it a try.
And please let me know how much did they charge you to replace the display.
Click to expand...
Click to collapse
hey bro , thanks for answering my question... as per ur ques. about how much money it costs to get it repaired. i gave my phone to a local repairman who inturn got it repaired for me for 7500rs...
btw, u said that i may face some software related problems by using the i9100 rom, but as per i know both the mobiles are quite identical in terms of hardware....
i am quite scared to flash i9100 rom because it could possibly brick my phone and i may have to shell out more money to again get it repaired....
i need to be fully sure then only i will think of flashing i9100 rom...
Mrinal_gupta said:
hey bro , thanks for answering my question... as per ur ques. about how much money it costs to get it repaired. i gave my phone to a local repairman who inturn got it repaired for me for 7500rs...
btw, u said that i may face some software related problems by using the i9100 rom, but as per i know both the mobiles are quite identical in terms of hardware....
i am quite scared to flash i9100 rom because it could possibly brick my phone and i may have to shell out more money to again get it repaired....
i need to be fully sure then only i will think of flashing i9100 rom...
Click to expand...
Click to collapse
If you can somehow get root and install cyanogenmod, there is a fix I can think of. Can you do this? I am asking you before I tell you so I don't waste your time.
azeem40 said:
If you can somehow get root and install cyanogenmod, there is a fix I can think of. Can you do this? I am asking you before I tell you so I don't waste your time.
Click to expand...
Click to collapse
I have already rooted my phone and also installed Busy box but i'm using original firmware that is UCMD8 which i had flashed through odin. If i can cyanogenmod without modding my kernel then i will possibly is install cyanogenmod. By the way i had already mistakenly bricked my old galaxy SL and damaged its emmc chip, so i'm kinda scared. But if it doesn't involve flashing custom rom or installing modded kernel then i will surely install cyanogenmod.
Mrinal both the phones have different GPU's and there are one or two more differences between both the phones. So the I9i000 kernel will be specially designed to be functional for that specifications. So this may cause you problems. Please just google the "difference between I9100 and SGH-I777" u'll get to know what m talkin bout.
You need to modify the keylayout file, take it from i9100. Hopefully that'll be it. All the rest can be left from i777.
Search for the exact file you need, it's some think like /system/etc/*something*.kl. Google is your friend.
The reason I asked is because there is a mod that gets you nexus software keys, but idk it works with stock rom.
azeem40 said:
The reason I asked is because there is a mod that gets you nexus software keys, but idk it works with stock rom.
Click to expand...
Click to collapse
brother, i am using button savior app that gives me onscreen buttons just like the one on nexus.. btw i was thimking of flashing i9100 official jellybean so that the buttons starts working again..so, do u think it's good to flash i9100 firmware ...is there any risk of getting my device bricked?
Mrinal_gupta said:
brother, i am using button savior app that gives me onscreen buttons just like the one on nexus.. btw i was thimking of flashing i9100 official jellybean so that the buttons starts working again..so, do u think it's good to flash i9100 firmware ...is there any risk of getting my device bricked?
Click to expand...
Click to collapse
Make sure it is ported to the i777; otherwise yes, you risk bricking it.
Mrinal_gupta said:
brother, i am using button savior app that gives me onscreen buttons just like the one on nexus.. btw i was thimking of flashing i9100 official jellybean so that the buttons starts working again..so, do u think it's good to flash i9100 firmware ...is there any risk of getting my device bricked?
Click to expand...
Click to collapse
No chances of bricking if you flash an I777 kernel after flashing the I9100 ROM. And i dont think you have to use an app for onscreen buttons. I mean if u r on a stock ROM you'll have to else if u r using a custom AOSP ROM then the navigation is already present in the settings..jus have to enable it.
Sent from my SGH-I777 using xda premium
gireeshtty9 said:
No chances of bricking if you flash an I777 kernel after flashing the I9100 ROM. And i dont think you have to use an app for onscreen buttons. I mean if u r on a stock ROM you'll have to else if u r using a custom AOSP ROM then the navigation is already present in the settings..jus have to enable it.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
brother, are u sure that with this method i won't brick my phone because one member told me that if i'll flash stock i9100 firmware then i will surely brick my phone...he also said that i should flash a rom that is ported from i9100 to sgh-i777 but a ported rom has been modded to work with sgh-i777 that means it will still have the working capacitive buttons...so i m not able to think what should i do now....
are u 100% sure that by ur method of flashing stock i9100 rom and i777kernel my phone will work..cause i don't think both these firmware and kernel of different phones will work together...
Jack_R1 said:
You need to modify the keylayout file, take it from i9100. Hopefully that'll be it. All the rest can be left from i777.
Search for the exact file you need, it's some think like /system/etc/*something*.kl. Google is your friend.
Click to expand...
Click to collapse
friend can u please elaborate more...or can u give me some kind of tutorial or something...
any help will be greatly appreciated....
thanks.....
Mrinal_gupta said:
brother, are u sure that with this method i won't brick my phone because one member told me that if i'll flash stock i9100 firmware then i will surely brick my phone...he also said that i should flash a rom that is ported from i9100 to sgh-i777 but a ported rom has been modded to work with sgh-i777 that means it will still have the working capacitive buttons...so i m not able to think what should i do now....
are u 100% sure that by ur method of flashing stock i9100 rom and i777kernel my phone will work..cause i don't think both these firmware and kernel of different phones will work together...
Click to expand...
Click to collapse
Look. If you are gonna flash a stock I9100 ROM den you sure will brick it. And by stock I mean pure stock straight from Samsung. And if you flash a CUSTOM stock ROM you wont get a brick as far as you have ported it to SGH-I777..to my knowledge. I have done this.
And I would suggest you to flash an AOSP ROM.
And porting the ROM is nothing like "specially mod the rom". You just have to replace a few 'modules' which are in the system/etc/modules folder(M not sure if it is in etc or usr folder) and flash it off. You dont have to change any keylayout file as u want the buttons to work same as on I9100. Please google "How to port an I9100 ROM to SGH-I777". Its pretty simple process.
And make sure you flash a SGH-I777 kernel after u flash the I9100 ROM.
Sent from my SGH-I777 using xda premium

s3 4.0.4

Is it possible to downgrade to 4.0.4 from 4.1.2?
abubakarsohail said:
Is it possible to downgrade to 4.0.4 from 4.1.2?
Click to expand...
Click to collapse
First, That is not an Downgrade,it's an Update xD
Second: Yes,you can update your phone to Android 4.1.2 (or 4.3,4.4 etc. using the Various Guide you find in General or Developer Question)
:laugh:
Niko99ITA said:
First, That is not an Downgrade,it's an Update xD
Second: Yes,you can update your phone to Android 4.1.2 (or 4.3,4.4 etc. using the Various Guide you find in General or Developer Question)
:laugh:
Click to expand...
Click to collapse
I know what I wrote I am asking if I can downgrade to 4.0.4 from 4.1.2?
Means what I want to say is that is it possible to downgrade to ICS from 4.1.2 JB?
I believe you can but what's the point? More battery life isn't worth the risk of the insane chip sudden death syndrome.
Sent from my GT-I9300
Niko99ITA said:
First, That is not an Downgrade,it's an Update xD
Second: Yes,you can update your phone to Android 4.1.2 (or 4.3,4.4 etc. using the Various Guide you find in General or Developer Question)
:laugh:
Click to expand...
Click to collapse
acrossy said:
I believe you can but what's the point? More battery life isn't worth the risk of the insane chip sudden death syndrome.
Sent from my GT-I9300
Click to expand...
Click to collapse
Look I flashed 4.0.4 BTU on my phone but then I was getting no signal no gsm connectivity
I guess I had a corrupted IMEI
If you do weird things to your phone then you will break it. Efs v2 will not be read by 4.0 firmware, there is no way to downgrade.
Questions go in the q&a forum. Report your own post and ask a moderator to move it.
Sent from my GT-I9300 using Tapatalk
you have to flash 4.1.2 or newer to retreive your imei back
Sent from my GT-I9300 using XDA Premium 4 mobile app
I think there is some way, but you would need a backup of EFS v1 (if im not mistaken). Basically its a long and tedious process and i know that JB is complete crap on the SIII and that ICS ran alot better, but i dont think its currently worth the effort to downgrade, just wait for KK.
Also sudden death only affects 16GB variants.
What about for example if I'm using slim kat 4.4.2 right now, is it possible to downgrade back to stock rom 4.3 by flashing it? I remember I did it before, is it risky like this scenario?
revilionz said:
What about for example if I'm using slim kat 4.4.2 right now, is it possible to downgrade back to stock rom 4.3 by flashing it? I remember I did it before, is it risky like this scenario?
Click to expand...
Click to collapse
You can flash a 4.3 rom over slim kat. Just do a clean install. I have been hopping between cm11 and stock 4.3 for quite some time and have not had issues.

Categories

Resources