Hey guys I'm new to the forums, I just don't know what to do anymore. I have a Galaxy Mega from AT&T with SOD in case you don't know what sleep of death is basically when I lock my Mega and put it to sleep he won't wake up until I do a hard reset or pull the battery out, I'M DESPERATE.
If anyone knows a solution for this please let me know.
Just in case, this is the phone info:
Android version 4.2.2
Baseband version I527UCUAMK2
Kernel version 3.4.0-2052936
[email protected] #1
Mon Nov 4 16:57:11 KST 2013
Build number JDQ39.I527UCUAMK2
Thank you in advance!
felixbodden said:
Hey guys I'm new to the forums, I just don't know what to do anymore. I have a Galaxy Mega from AT&T with SOD in case you don't know what sleep of death is basically when I lock my Mega and put it to sleep he won't wake up until I do a hard reset or pull the battery out, I'M DESPERATE.
If anyone knows a solution for this please let me know.
Just in case, this is the phone info:
Android version 4.2.2
Baseband version I527UCUAMK2
Kernel version 3.4.0-2052936
[email protected] #1
Mon Nov 4 16:57:11 KST 2013
Build number JDQ39.I527UCUAMK2
Thank you in advance!
Click to expand...
Click to collapse
Are you rooted? Did you freeze or remove anything?
Sent from my SAMSUNG-SGH-I527
azpatterson3 said:
Are you rooted? Did you freeze or remove anything?
Sent from my SAMSUNG-SGH-I527
Click to expand...
Click to collapse
Yes I'm rooted now but before the rooting I had the same problem, and no I didn't remove anything. Also the phone is unlocked but I don't know the tool that was used to perform the unlocking, I just bought the phone from ebay but the seller won't even bother to answer my messages.
felixbodden said:
Yes I'm rooted now but before the rooting I had the same problem, and no I didn't remove anything. Also the phone is unlocked but I don't know the tool that was used to perform the unlocking, I just bought the phone from ebay but the seller won't even bother to answer my messages.
Click to expand...
Click to collapse
Short of Kies or Odin to flash stock back on it... I don't know. Hope it is not a hardware issue. If you used paypal, I would let them know about the seller and maybe get your money back
Here is the link to the odin tar.md5 file
http://forum.xda-developers.com/showthread.php?t=2558602
azpatterson3 said:
Short of Kies or Odin to flash stock back on it... I don't know. Hope it is not a hardware issue. If you used paypal, I would let them know about the seller and maybe get your money back
Here is the link to the odin tar.md5 file
http://forum.xda-developers.com/showthread.php?t=2558602
Click to expand...
Click to collapse
Thank you for the help man but no luck :/ it flashed successfully yet still the same problem. I know for sure it must be software related, I wish there was a custom rom for i527.
felixbodden said:
Thank you for the help man but no luck :/ it flashed successfully yet still the same problem. I know for sure it must be software related, I wish there was a custom rom for i527.
Click to expand...
Click to collapse
its a software issue even with a fresh flash? sounds like it is hardware related to me. I would check ATT and see if you can get it replaced if it is an ATT mega.
To to reflash ang stock ROM..
Sent from my GT-I9205 using Tapatalk
felixbodden said:
Hey guys I'm new to the forums, I just don't know what to do anymore. I have a Galaxy Mega from AT&T with SOD in case you don't know what sleep of death is basically when I lock my Mega and put it to sleep he won't wake up until I do a hard reset or pull the battery out, I'M DESPERATE.
If anyone knows a solution for this please let me know.
Just in case, this is the phone info:
Android version 4.2.2
Baseband version I527UCUAMK2
Kernel version 3.4.0-2052936
[email protected] #1
Mon Nov 4 16:57:11 KST 2013
Build number JDQ39.I527UCUAMK2
Thank you in advance!
Click to expand...
Click to collapse
To me...This sounds like a kernel issue. I've had similar issues when testing kernels I'm building. That is if the mega runs fine when actually on and functioning. Here's a trick to know if the mods done prior to purchase involved modifying the kernel.
When the mega shuts down and won't boot...plug it into the charger ...let it cycle thru and show the little battery icon level meter...then start it back up...If it boots without hard reset we can go from there.
Mega
i527 bootloop after update
need help any kind of help . my att mega i527 is in bootloop after update my phone was rooted an update went through without me knowing i tried all the files posted throrghout the site but nouthing works
Related
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?
IDK if anyone has had this issue before, but I purchased a GT-I9300 and it is missing all the samsung apps (all the S-Apps and other things that make the S3 the S3). I called Samsung and told them what happened, and they wanted to shaft me with $50. Anybody got any idea what I can do for this? Everything else works fine. I am going to try saywhatt's apps to see if I can get all the stuff I am missing on the phone in. Just in case anyone else has an idea as to what to do in my case.
Thanks in advance :cyclops:
U can download `em manually.Google it up.
zekefreed777 said:
IDK if anyone has had this issue before, but I purchased a GT-I9300 and it is missing all the samsung apps (all the S-Apps and other things that make the S3 the S3). I called Samsung and told them what happened, and they wanted to shaft me with $50. Anybody got any idea what I can do for this? Everything else works fine. I am going to try saywhatt's apps to see if I can get all the stuff I am missing on the phone in. Just in case anyone else has an idea as to what to do in my case.
Thanks in advance :cyclops:
Click to expand...
Click to collapse
Sounds like its not a new phone or a fake to me .
What is your firmware details ??? settings about phone
jje
You can also flash a Stock rom via Odin. But first check if your phone is the real deal. Like "JJEgan" said Go to setting > About Device... and let us know what Model Number, Android Version, Baseband, Kernel, and Firmware you have.
JJEgan said:
Sounds like its not a new phone or a fake to me .
What is your firmware details ??? settings about phone
jje
Click to expand...
Click to collapse
Android version: 4.1.9
Build number:IMM76D. GT-I9300ZSALE9
Custom Build Version:1359856456
Like I said before, tried googling & I'm double checking that I am taking the correct steps to put the right stuff on there on here. I'm currently trying to fish out the .apk's I may need to install but I need to look through the manual to see what I am missing. I previously had a G2X which I managed to get to CM 10 thanks to the wizards here, but I just got this phone, and it seems to be running ICS. It just doesn't have as many apps as it should out of the box.
Another thing I think may be worthy of noting is that it has "Samsung Apps" in the home screen but it says it does not install.
Thanks again for the swift responses.
EDIT1:
Baseband: MAUI.11AMD.W11.50.SP.V20,2012/08/13 14:56
Kernel Version:3.0.13
1211 V72
Sun Feb 3 16:11:02 CST 2013
Missing Samsung stuff and a new phone return to vendor .
Or just flash a stock rom .
jje
JJEgan said:
Missing Samsung stuff and a new phone return to vendor .
Or just flash a stock rom .
jje
Click to expand...
Click to collapse
If I flashed this to JB with Odin, would that solve the issue?
yes unless it's fake, in which case you'll kill it
Glebun said:
yes unless it's fake, in which case you'll kill it
Click to expand...
Click to collapse
I see. Does it matter that it was confirmed by Samsung or no? They checked the IMEI for verification...
zekefreed777 said:
Android version: 4.1.9
Build number:IMM76D. GT-I9300ZSALE9
Custom Build Version:1359856456
Like I said before, tried googling & I'm double checking that I am taking the correct steps to put the right stuff on there on here. I'm currently trying to fish out the .apk's I may need to install but I need to look through the manual to see what I am missing. I previously had a G2X which I managed to get to CM 10 thanks to the wizards here, but I just got this phone, and it seems to be running ICS. It just doesn't have as many apps as it should out of the box.
Another thing I think may be worthy of noting is that it has "Samsung Apps" in the home screen but it says it does not install.
Thanks again for the swift responses.
EDIT1:
Baseband: MAUI.11AMD.W11.50.SP.V20,2012/08/13 14:56
Kernel Version:3.0.13
1211 V72
Sun Feb 3 16:11:02 CST 2013
Click to expand...
Click to collapse
This is knock off device and not a real S3 The reason they are not there is that most likely the device doesnt have the hardware to support it. Thos device normally come with around 500 mb of ram and that is not even close to enough to run the samsung apps. Mix in that 4.1.9 is not an official build of android so you most likely will have issues with google based apps.
zelendel said:
This is knock off device and not a real S3 The reason they are not there is that most likely the device doesnt have the hardware to support it. Thos device normally come with around 500 mb of ram and that is not even close to enough to run the samsung apps. Mix in that 4.1.9 is not an official build of android so you most likely will have issues with google based apps.
Click to expand...
Click to collapse
I see. I'll go through Samsung then. Thanks for looking over the specs.
zekefreed777 said:
I see. I'll go through Samsung then. Thanks for looking over the specs.
Click to expand...
Click to collapse
Once Samsung gets it they will return it to you unaltered. The min they see it is a knock off device they will refuse to do anything with it.
As for the IMEI that is easily faked and knock offs are known to use copied IMEI numbers to fool the buyers into thinking it is legit. If I were you I would toss it on Ebay and get another device.
Too many people looking for a cheap high end device and they end up with a POS that is equal to a toaster. Please make sure you know what you are buying before you buy it. You will find almost no help/support/or anything for those devices anywhere.
I have a Galaxy S3 GT-i9300 on o2 uk which i have had unlocked at a phone shop so i can use it in t-mobile. Water got spilt on my Galaxy S3 a few months ago, the phone died but eventually came back to life after drying it out although the screen didnt work and it wouldnt boot properly . I took it to a phone shop who said they replaced some ribbons, its now working fine except the mobile data just doesnt work.
Its currently on 4.1.2 and want to update to 4.2.2 just to see if this will fix it.
I cant update ota because the device has been modified (guessing because of the unlock). Will I lose my unlock if I flash the firmware to 4.2.2 with odin? Or does anyone have any more ideas of ways I could try to fix it.
Build number: JZ054.I9300XXEMC2
Kernal version: 3.0.31-1042335
Standard reply really did you check your apn settings? You have not said what or if anything you have tried...
tallman43 said:
Standard reply really did you check your apn settings? You have not said what or if anything you have tried...
Click to expand...
Click to collapse
Never even crossed my mind actually. I will check them, ive tried another sim card. Not sure what else there is to try?
Thanks for the reply
craigant said:
Never even crossed my mind actually. I will check them, ive tried another sim card. Not sure what else there is to try?
Thanks for the reply
Click to expand...
Click to collapse
No problem If they are not there just Google them and input manually ...
tallman43 said:
No problem If they are not there just Google them and input manually ...
Click to expand...
Click to collapse
Sorted, thanks as if I overlooked this what a noob!
craigant said:
Sorted, thanks as if I overlooked this what a noob!
Click to expand...
Click to collapse
Lol no problem....
Hello xda people,
i have the galaxy mega gt-i9200 with 4.2.2 software (no knox included)
ive tried every 4.4.2 kitkat update firmware from sammobile and everytime i end up with the same result.
Problem is when i flash the firmware , it boots up and my touchscreen and softkeys are disbaled/dont work.
i have no clue what the problem is, custom roms seem to work, and 4.2.2 official stock works.
can someone help me out? please.
Ntech02 said:
Hello xda people,
i have the galaxy mega gt-i9200 with 4.2.2 software (no knox included)
ive tried every 4.4.2 kitkat update firmware from sammobile and everytime i end up with the same result.
Problem is when i flash the firmware , it boots up and my touchscreen and softkeys are disbaled/dont work.
i have no clue what the problem is, custom roms seem to work, and 4.2.2 official stock works.
can someone help me out? please.
Click to expand...
Click to collapse
Maybe nobody has had this same issue. JIMMBOB offered a suggestion in one of your other threads.
You have 3 different threads.....are they 3 different problems. I only ask cause they are worded differently.
When you flash, are you flashing clean?
I am trying to offer some assistance. It sounds as if your having same problem across the board. Just have to start with basic responses so dont get upset. Try to walk through your process of flashing. Maybe you missed something. We all can.
Folks are reading, again maybe others just havent come across this issue.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Ntech02 said:
Hello xda people,
i have the galaxy mega gt-i9200 with 4.2.2 software (no knox included)
ive tried every 4.4.2 kitkat update firmware from sammobile and everytime i end up with the same result.
Problem is when i flash the firmware , it boots up and my touchscreen and softkeys are disbaled/dont work.
i have no clue what the problem is, custom roms seem to work, and 4.2.2 official stock works.
can someone help me out? please.
Click to expand...
Click to collapse
Ntech02 said:
I flashed this stock rom here http://forum.xda-developers.com/showthread.php?p=53767196 for my GT-i9200 Mega
coming from silentnight's flashable stock rom & another time from C-ROM 4.4.3,
each time i flash the stock rom (http://forum.xda-developers.com/showthread.php?p=53767196) it completes, reboots just fine, and when it starts up my screen doesnt respond anymore ive tried factory resets and full wipes & reflashed multiple times, idk what to do to make it work.
i can still go back to custom roms and my screen works fine on those. ive even tried going to 4.2.2 official stock but that doesnt work either.
someone please help =(
Click to expand...
Click to collapse
Ntech02 said:
Hello xda,
ive been having an issue for sometime but idk what it is,
when i boot my phone i cant see the logo that says "GALAXY MEGA i9200" it just stays black until the samsung boot animation appears.
in addition i cant see the DOWNLOAD mode screen either, although i can still enter download mode by using the button combination or just hitting reboot to DOWNLOAD mode.
does anybody know how to fix this?
Click to expand...
Click to collapse
Ntech02 said:
i have asked multiple times and im getting no response which is why i took my question here. if u werent gonna help me figure out something u didnt have to reply. and i can say its a stock rom because thats what it is. Stock Russian 4.4.2 kitkat Update for the GT-I9200. the only thing is this developer removed knox & the recovery. ive tried both versions of the rom and ended in the same result.
Click to expand...
Click to collapse
@Ntech02
Are you sure you are flashing the correct Official Firmware? I show many but you stated Russian above so I show two for your phone on KitKat. Also, if you were not made aware or didn't read up on the forums, once you upgrade to the "NE4 Bootloader" (Or KITKAT) and above you can not revert back to the previous ( JellyBean ) "Bootloaders". If you manage to flash back to them you will more than likely brick your phone.
Flashing a Custom Rom via Custom Recovery being from NF2, NE4, NA2, and MJ2 Roms for your Mega is still okay. Just remember not to Flash/Odin the Official Firmware from prior NE4 as the Firmwares include the Bootloader in them that one can not downgrade to.
All except for one of these Official Firmware is Flashable via Kies as well:
GT-I9200 Ukraine (Kyivstar)......2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200OXEDNF1
GT-I9200 Kazakhstan...............2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200OXEDNF1
GT-I9200 Uzbekistan ...............2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200OXEDNF1
GT-I9200 Russia .....................2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200SERDNF2
GT-I9200 Brazil .......................2014 June ........4.4.2 ........I9200UBUDNE2 ........I9200ZTODNE2
GT-I9200 Russia .....................2014 May .........4.4.2 ........I9200XXUDNE4 ........I9200SERDNE4
I know it has been mentioned / suggested before in other sections of the forum but updating your profile to reflect at least the Country and a Carrier for your phone would be helpful to provide some assistance.
captemo said:
Maybe nobody has had this same issue. JIMMBOB offered a suggestion in one of your other threads.
You have 3 different threads.....are they 3 different problems. I only ask cause they are worded differently.
When you flash, are you flashing clean?
I am trying to offer some assistance. It sounds as if your having same problem across the board. Just have to start with basic responses so dont get upset. Try to walk through your process of flashing. Maybe you missed something. We all can.
Folks are reading, again maybe others just havent come across this issue.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
Yes i understand i have 3 threads but someone could've at least attempted to help me out like you & dark angle is doing now, so i thank you guys for taking the time to reply.
its the same issue regarding the screen, im not gonna get upset with u lol
but ive followed all the instructions correctly, and yes ive flashed clean.
im on philz cwm recovery as it is.
i would erase my data b4 installing the kitkat stock update.
used odin3 3.09 & 3.04
the firmware flashes fine.
it boots up like its supposed to, but the screen is just unresponsive .
ive done factory resets from stock recovery
ive even left it on over night to see if maybe something didnt load. but nothing works maybe its a driver issue?
DarkAngel said:
@Ntech02
Are you sure you are flashing the correct Official Firmware? I show many but you stated Russian above so I show two for your phone on KitKat. Also, if you were not made aware or didn't read up on the forums, once you upgrade to the "NE4 Bootloader" (Or KITKAT) and above you can not revert back to the previous ( JellyBean ) "Bootloaders". If you manage to flash back to them you will more than likely brick your phone.
Flashing a Custom Rom via Custom Recovery being from NF2, NE4, NA2, and MJ2 Roms for your Mega is still okay. Just remember not to Flash/Odin the Official Firmware from prior NE4 as the Firmwares include the Bootloader in them that one can not downgrade to.
All except for one of these Official Firmware is Flashable via Kies as well:
GT-I9200 Ukraine (Kyivstar)......2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200OXEDNF1
GT-I9200 Kazakhstan...............2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200OXEDNF1
GT-I9200 Uzbekistan ...............2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200OXEDNF1
GT-I9200 Russia .....................2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200SERDNF2
GT-I9200 Brazil .......................2014 June ........4.4.2 ........I9200UBUDNE2 ........I9200ZTODNE2
GT-I9200 Russia .....................2014 May .........4.4.2 ........I9200XXUDNE4 ........I9200SERDNE4
I know it has been mentioned / suggested before in other sections of the forum but updating your profile to reflect at least the Country and a Carrier for your phone would be helpful to provide some assistance.
Click to expand...
Click to collapse
hey darkangel thank you both for trying to help me out,
my i9200 is unlocked and on tmobile, i am in the USA but my firmware is the Russian 4.2.2
i actually am on the NE4 (kitkat) bootloader but im still running Russian 4.2.2 jellybean,
i did a nandroid backup from Philz CWM recovery b4 i flashed the Russian official kitkat update
as stated above anything i tried just didnt work. the screen is unresponsive and so are the softkeys
so i just flashed philz recovery again and restored my jellybean stock which is how im still running on JB.
ive had no issues as far as bricking my phone im pretty savy when it comes to android i think im having a bad day lol
Ntech02 said:
hey darkangel thank you both for trying to help me out,
my i9200 is unlocked and on tmobile, i am in the USA but my firmware is the Russian 4.2.2
i actually am on the NE4 (kitkat) bootloader but im still running Russian 4.2.2 jellybean,
i did a nandroid backup from Philz CWM recovery b4 i flashed the Russian official kitkat update
as stated above anything i tried just didnt work. the screen is unresponsive and so are the softkeys
so i just flashed philz recovery again and restored my jellybean stock which is how im still running on JB.
ive had no issues as far as bricking my phone im pretty savy when it comes to android i think im having a bad day lol
Click to expand...
Click to collapse
This is more than likely going to sound like a stupid noob answer.
Did you buy your phone new or used?
I noticed when I was looking at buying a Mega with a broken screen, if you use a cheap replacement screen, you need to plug in the factory screen and boot and then plug in the aftermarket screen. I wonder if maybe you got it used and it was repaired and the stock OS is seeing as not being an OEM screen? Maybe Custom ROMs don't check these things?
@Ntech02 try flashing this rom via recovery http://forum.xda-developers.com/showthread.php?t=2608110
Sent from my GT-I9200 using XDA Premium 4 mobile app
nitromuscle said:
This is more than likely going to sound like a stupid noob answer.
Did you buy your phone new or used?
I noticed when I was looking at buying a Mega with a broken screen, if you use a cheap replacement screen, you need to plug in the factory screen and boot and then plug in the aftermarket screen. I wonder if maybe you got it used and it was repaired and the stock OS is seeing as not being an OEM screen? Maybe Custom ROMs don't check these things?
Click to expand...
Click to collapse
I Bought it New from NewEgg.com but the screen did break b4, and i bought a replacement 70$ screen and fixed it myself, idk if thats cheap but thats how much they typically cost on amazon.com . all custom roms work, and the 4.2.2 jelly bean official software works fine.
you maybe right about the OEM screen
alexischino said:
@Ntech02 try flashing this rom via recovery http://forum.xda-developers.com/showthread.php?t=2608110
Sent from my GT-I9200 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
is this kitkat?
@Ntech02 No is jellybean 4.2.2 but if you are on kitkat you can flash this rom via recovery i'm using the russia 4.4.2 kk and i have flash the v10 and the v11 you can use them to go back to jellybean.
Sent from my GT-I9200 using XDA Premium 4 mobile app
alexischino said:
@Ntech02 No is jellybean 4.2.2 but if you are on kitkat you can flash this rom via recovery i'm using the russia 4.4.2 kk and i have flash the v10 and the v11 you can use them to go back to jellybean.
Sent from my GT-I9200 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ohhh no no no lol ive been saying all along that im already on JB 4.2.2 official stock.
im still on the kitkat boot loader though.
You should be fine running JB on kitkat bootloader as long as you do not try and Odin a firmware with the JB bootloader and try to go back to the 4.2.2 bootloader. It will not let you go back to it. Flashing ROM's for your phone is all good as long as you do not touch the bootloader.
But if you really want to have KitKat then you need to try and reflash one of the KitKat official Firmwares I had mentioned above for your phone. You can only flash Firmwares via Odin from KitKat and above now because of the KitKat Bootloader.
So i'm running the Tigerlilly Rom at the moment and was going to do a phone backup through Kies 3. I plug my phone in and it says it has a software update... All it says is that its OH3, and I'm updating it now. I'll let you guys know what it is. Also does anyone else get this with stock?
okay so its still kitkat 4.4.2, I'm not sure what the difference is to be honest
May be security patches I did see it flash up on my wife's device last night but I have no details for it. If I find anything I edit this post.
DJBoxer said:
May be security patches I did see it flash up on my wife's device last night but I have no details for it. If I find anything I edit this post.
Click to expand...
Click to collapse
Thats what I thought too. The update restored my phone back to stock though lol
kireflow90 said:
Thats what I thought too. The update restored my phone back to stock though lol
Click to expand...
Click to collapse
Yes looks like a new base here details I have so far for it.
ModelSGH-T399N
Model nameGALAXY Light
CountryUSA (T-Mobile)
VersionAndroid 4.4.2
Changelist2903595
Build dateTue, 25 Aug 2015 06:39:34 +0000
Product codeTMB
PDAT399NUVUAOH3
CSCT399NTMBAOH3
I will be using this for stock base for my builds.
Sent from my SGH-T399N using Tapatalk
DJBoxer said:
May be security patches I did see it flash up on my wife's device last night but I have no details for it. If I find anything I edit this post.
Click to expand...
Click to collapse
Found this article that actually probably explains the update http://www.cnet.com/news/every-android-device-vulnerable-to-newly-discovered-bugs/
Sent from my SGH-T399N using XDA Free mobile app