Hi all
On Thursday evening, my cellphone was drained flat as usual by the evening.
When I got home, I put it on charge. After a few minutes I tried turning it on, it got stuck at the Samsung splash screen,
wouldn't boot any further. After trying a few times, removing the battery, etc, I ended up just leaving it off but on charge
the whole night. The battery was fully charged the next morning(so it's not a battery issue). I had the same issues that
morning.
I spent the whole day on Friday, trying to fix this cellphone of mine. I tried tons of fixes I found on this forum(although
a lot of them use programs/files uploaded to a file service that has been closed down[really annoying]). Posting here
is definitely my last resort, I can't think of anything else to try...
I have tried flashing the firmware
I tried to get Kies to do a firmware update and initilisation
I tried various fixes and went through many, many forum posts.
Last thing I tried is to flash the .PIT and flash what I thought was the original firmware I eventually got hold of from sammobile
I tried the last step twice and am busy downloading another version.
What happened with this, is it'll boot, I see the android with his stomach open and something happening inside, it then reboots
and does exactly the same thing as it had previously done, gets stuck on the Samsung splash.
Could someone maybe step me through how to flash it again? I think I need to basically start from scratch, new PIT and all.
I have the GT-i9300(International) 32Gb - I bought it in South Africa
Thanks very much for any help in advance
Sinjin
Sounds like partition corruption when the battery went flat. If flashing a full rom or the rescue firmware (see general thread), followed by a factory reset, didn't help then you'll probably need a new motherboard.
Sent from my GT-I9300 using Tapatalk
Related
Today i woke up to the new Update for the vibrant. So of course i tried to update it. My phone is rooted if that makes a difference running everything else stock though. I did the one click root or whatever it was. Well i clicked update and sat my phone down as i got ready. Come back its at the boot screen where it says Vibrant and Samsung in white. I figured it was just loading the new files and just taking a little long. Well by the time i got to school it was still like that so i removed the battery so it would not overheat. Replaced the battery booted up and stalled on boot screen again. This time it made the opening music but never transitioned screens. So i took battery out replaced it and went into clockwork and did a nandroid. Reset it same thing happened. Tried that with three of my backups of previous dates. all failed. so i decided to wipe all data of the phone or factory reset. still stuck at boot screen.
If anyone can help me it would be much appreciated. if you need any other information just let me know.
same thing here. i've done all those steps. when i get home, im going to try and update the JI6 update through ODIN. i'll let you know what happens.
Common problem, easy solution..
http://forum.xda-developers.com/showthread.php?t=803492
Hi there guys, In need of some help here! Had my S3 for 8 months now and its been fine, Never rooted, Always been on stock OS's from day one.. About a week ago I started to get random reboots and freezes, A battery pull would fix the issue for a while but then it would come back again, They became more and more frequent and then I did the latest update, 4.1.2 (I think) It worked fine for a day and then yesterday morning I had like one restart, After a battery pull it worked fine. Put it in in my pocket and carried on doing my work. When I next looked at it it was on the samsung boot screen, I thought it must be another random reboot, But this time it kept looping over and over, Makes the little jingle sound with the samsung logo and then repeats constantly.. I did a wipe data/cache from the recovery mode and that didn't change anything, I then flashed the latest unbranded UK OS via Odin, But that didn't do anything either, The only difference that made was that it gave me a false hope as when i booted it, It say 'Optimising Apps' an then went from 0 to 30 something but sadly, After that it began its looping of the samsung logo again. Anyone heard of a case like this? Where an unrooted phone 'bricks' itself? Could it be hardware?.. Hopefully someone can help.. I hope Samsung UK will fix this under warranty! Fingers crossed they will! Any help would be much much appreciated.. Thanks!
It sounds like a partial SDS hardware fault if you stayed on the previous UK ROM and didn't update to XXELLA until just a week ago, return it to Samsung for a new motherboard.
ELLA contained a fix which prevents SDS, but won't cure it if it's already happened.
JayS3 said:
Hi there guys, In need of some help here! Had my S3 for 8 months now and its been fine, Never rooted, Always been on stock OS's from day one.. About a week ago I started to get random reboots and freezes, A battery pull would fix the issue for a while but then it would come back again, They became more and more frequent and then I did the latest update, 4.1.2 (I think) It worked fine for a day and then yesterday morning I had like one restart, After a battery pull it worked fine. Put it in in my pocket and carried on doing my work. When I next looked at it it was on the samsung boot screen, I thought it must be another random reboot, But this time it kept looping over and over, Makes the little jingle sound with the samsung logo and then repeats constantly.. I did a wipe data/cache from the recovery mode and that didn't change anything, I then flashed the latest unbranded UK OS via Odin, But that didn't do anything either, The only difference that made was that it gave me a false hope as when i booted it, It say 'Optimising Apps' an then went from 0 to 30 something but sadly, After that it began its looping of the samsung logo again. Anyone heard of a case like this? Where an unrooted phone 'bricks' itself? Could it be hardware?.. Hopefully someone can help.. I hope Samsung UK will fix this under warranty! Fingers crossed they will! Any help would be much much appreciated.. Thanks!
Click to expand...
Click to collapse
Which firmware are you using?
as Boomboomer said, if you never did a firmware upgrade before your last upgrade you are probably encountering issues with SDS. new motherboerd required
Good luck!
Hello guys,
At first, sorry for the long text but, that's the odyssey that leads to my problem. If you don't want to read everything, jump to the summary.
It all started when my S3 got wet inside my backpack while it was raining. I know that the first thing we need to do is to pull out the battery when you realize it is getting wet and let it dry for days before turn on. However, I was drunk so I tried the opposite turning it on at the end of the day and it didn't work. Then I pulled out the battery and let it dry for weeks. I've also opened the device and disassembled it. I could see some parts with some kind of white dust. So, I cleaned with a toothbrush and rubbing alcohol. After doing that, I tried to turn on the device without success. One or two days later that battery got stuffed and then I sent it to repair.
There, I pointed that it could be a problem with the main board. The guy performed a fast check with voltmeter and said he could be repaired. He took the device and returned with the S3 turned on in less than 15 minutes. Then, he asked if he could reset the device and where I bought it because it didn't have the stock rom (I changed it to Neatrom). Since it was "working" I said I would take it and do the rest of the job restoring the rom.
When I got home, I charged the phone for ~8 hours following the technician instructions since it was a new battery. The strange thing is that the icon for battery was not the green one, but the white one with the round arrow the whole time. Ok, then I did a clean and restore through CMW menu keeping the neatroom. It started autorebooting. Also tried CM12 but got bootloop. The next day, the battery got stuffed so I pulled it out and waited to whole week and sent to repair.
There, he gave me another battery (which now seems to be original). The battery worked and I did a reset through CWM recovery. At first minutes it was ok then it started rebooting. I thought it could be something with the room since It was not rebooting in recovery menu. Anyway, I also took my notebook there in order to restore the stock rom and, in case of errors, I could give the phone to the technician in the same day. The problem is that the process took forever when it got to the point of booting up the phone after restarting it and then I ran out of battery and had to turn it off.
When I got home, I applied the stock rom again and it booted ok but with the common efs/csc problems (Can't recognize sim card, IMEI/Baseband unknown....). Also, menu and back button seems to be not working. No leds or function. It's probable hardware but I check it later.
Well, I have a efs backup I've created with kTools (efs.img 20mb + efs.tar.gz 0kb) which I tried to recover but it didn't changed nothing. I also have another efs.tar.gz file alone with 1kb which I'm not sure if it's a backup but I think I generated that with Backup_EFS.bat. Tried Restore_EFS.bat but got stuck in * daemon not running. starting it now on port 5037 * * daemon started successfully *...
I've already tried odin through PDA and CSC. My country is Brazil and I already tried the open region Stock Rom (PDA:I9300UBUGNK1 and CSC: I9300ZTOUGNK2) and rom from an specific provider.
Summary
- I9300 got wet (rain)
- ~3 weeks drying disassembled + mainboard clean with toothbrush and rubbing alcohol
- Battery stuffed 2 days after assembly and test without success.
- Sent to repair. Something was done there and it revived.
- Phone autorebooting then battery stuffed again.
- Sent to repair. Changed battery
- Tried to apply stock rom (odin). First boot took forever and had to turn the device off.
- Second attempt worked but got IMEI/Baseband unknown, sim card recognition problem
- Tried ODIN through PDA and CSC
At this point I'm downloading A.S_id's rescue firmware and try it's troubleshooting. Later I may try to restore IMEI with -efs rebuild using android SDK....
So many things happened that I'm not even sure what to ask but, if you have a luminous idea on something I've never done, Id kindly ask to let me know.
Did I do something wrong when trying to restore efs? BTW, I also have a full nandroid backup generated by CWM philz touch recovery but it seems it doesn't contain efs partition.
Also, I ask you guys if the IMEI,Simcard,baseband problem can be a hardware problem? I've even seen topics saying about "burning the baseband", is it possible?
I'm just trying to gather all information possible before going to the technical assistance again.
If you read everything, I appreciate your patience and I'd be grateful for any reply.
try to restore the efs.img with PhilZ recovery via custom restore... :good:
Hello guys, I have a serious predicament that needs to be solved.
I haven't did anything major to my phone in years so the past couple days have been a nightmare. Ever since I did a wipe of cache partition after trying to get rid of this "unfortunately, contacts stopped working." message, it's sent my phone into a spiraling disaster. (I have been using stock 5.0 rooted rom for at least a year so idk why the sudden issues)
I've literally tried every method imaginable. I even tried flashing with different versions of Odin and still the exact same problems.
I can get my phone into DL mode easily but Recovery mode only works if I have the phone plugged in at this point (Actually, it seems like the only time when my phone wants to work)
Every time I'm done flashing, it'll load all the way up to the T-Mobile screen then restart the loop all over again :/
Really need help seeing as I need to get this situation handled before work today, thanks!
Nevermind, after more research, I decided to order a new battery and the problem is solved.
Bootloop solved with replacement battery
gkenga said:
Nevermind, after more research, I decided to order a new battery and the problem is solved.
Click to expand...
Click to collapse
A replacement battery also solved my boot loop issue. Prior to replacement, it would boot to Galaxy S5 screen, and then reboot. Replaced battery and boots. Put the old battery back in, and it boot looped.
So I've reached out to this forum as I've tried a million and one things but can't seem to get my phone to boot.
Here's the situation:
I fell asleep watching a video on my phone and my phone died. I plugged it into the charger and it wouldn't boot, would just endlessly be stuck in a boot loop. Looked it up and saw this is a common issue. Went through the standard fixes:
Wiped the cache
Factory reset the phone.
Attempted to boot in safe mode. (Wouldn't work, still boot looped)
After all this failed I thought I would just flash it using Odin v3.14. T-Mobile is my carrier and I'm based in the US so I used this firmware: SM-N950U TMB, LINK(https://updato.com/download-samsung...sa/sm-n950u/B094B9DAF04A11EAB4A2FA163EE8F90B/)
It still didn't work after this. It booted up and the startup process began asking me to agree to the terms and conditions. Before even getting to agree, the phone crashed. I tried this again and it just kept failing and crashing. I did this all while plugged into a charger. What I did begin to notice is that the phone would get hot on the left side, where the battery sits. I'm not sure if this is related to the crash or just the fact that its been discharging and charging a lot while I troubleshoot it. I have tried different firmware as well just in case I had the wrong one, but nothing has been working. When I update the firmware I used the CSC file and not the HOME_CSC and I also use the USERDATA file since at this point I kind of accepted I'm not getting my pictures and files back and I'm just trying to get the phone to work once again, thus just trying to factory restore it. Also, when the phone does start booting it says optimizing apps on the bottom each time I boot it I feel this number is changing. I'm not sure what else to do or if anyone has any suggestions? Thank you in advance