Related
Hi guys. My SGN is permanently freezing while booting. Suddenly the red lines appear and phone is stucked. It stucks on boot logo, or boot animation, or after successfull boot into system. It looks like this:
http://dl.dropbox.com/u/61718936/IMAG0003.jpg
Phone becomes quite hot on the back near camera.
I bought phone with stock 2.3.6. It was running for about 2 hours and i made OTA update to 4.0.4. It started to reboot itself while i was using it. So thought, i might use custom ROM to get rid of this freezes and reboots. But no change. Even on 4.2.1. I reverted back to 2.3.6. I noticed, that these red lines changes and moves (or even whole screen becomes red) while i'm twisting or pressing phone on various places. So i think, there is cold solder joint somewhere on motherboard. Maybe on graphic chip, because i didn't notice this problem while in recovery or download mode.
Can anybody help me with this problem, or point me on right place to look at on motherboard? Thanks in advance.
Seems to be defective device. Check with service center.
Sent from my GT-N7000 using xda premium
If you're able to, run this app to check for errors, I take it you have root. If it crashes mid scan, you've got problems with your emmc.
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
Sent from my GT-N7000 using xda premium
Frozen Note
I hope you will find a solution for your problem.
But I have to admit I had to smile ("grinsen" in German is a much better word for it) when I saw your title:
Freezing even when >30°C
i'm not able to run device anymore but i already tried this app for checking emmc and this is the one with that bug. But it doesn't matter, because i was flashing only safe kernels, and i don't think this emmc is problem. I think the culprit is graphic chip, or CPU, or CfRF (Chip for Random Freezes)
I was not able to find any similar problem. Tomorrow, i will try to put device into download mode, flash any custom safe kernel with CWM, leave device in this recovery, and see if it freezes again. If yes, the only option is to get device warmer for a few degrees (300-350°C with my heat station haha ) and i will see if there was any cold solder joint. If not, device will be dead anyway so i have nothing to lose
ThaiDai: you mean grin?
Tuxxperia said:
i'm not able to run device anymore but i already tried this app for checking emmc and this is the one with that bug. But it doesn't matter, because i was flashing only safe kernels, and i don't think this emmc is problem. I think the culprit is graphic chip, or CPU, or CfRF (Chip for Random Freezes)
I was not able to find any similar problem. Tomorrow, i will try to put device into download mode, flash any custom safe kernel with CWM, leave device in this recovery, and see if it freezes again. If yes, the only option is to get device warmer for a few degrees (300-350°C with my heat station haha ) and i will see if there was any cold solder joint. If not, device will be dead anyway so i have nothing to lose
ThaiDai: you mean grin?
Click to expand...
Click to collapse
Hope you find the answer dude, let us know what the outcome is.
Sent from my GT-N7000 using xda premium
Have the same problem with CM9/10 and PA ROM, freeze and getting hot...
The best ROM closest to stable for me is the RocketROM_ICS_XXLPY_v1
I got reboot problem but it is useable with this ROM
I Cant even install a Stock ROM (GB/ICS)... Stuck in Samsung LOGO, or Force Close in many apps...
diasdroid said:
Have the same problem with CM9/10 and PA ROM, freeze and getting hot...
The best ROM closest to stable for me is the RocketROM_ICS_XXLPY_v1
I got reboot problem but it is useable with this ROM
I Cant even install a Stock ROM (GB/ICS)... Stuck in Samsung LOGO, or Force Close in many apps...
Click to expand...
Click to collapse
Have you repartitioned?
Sent from my GT-N7000 using xda premium
guys i've made a small progress. I put a pressure on back side of the phone near camera, and i turned the phone on. It successfully booted to system. When i stopped pushing phones back, red lines appeared immediately and phone freezed. When i start to twist phone in hands, lines were getting bigger or smaller. When i pressed the back cover again, lines disappear (but phone was still frozen).
So now my task is, to find out, which chip is badly soldered.
ThaiDai said:
I hope you will find a solution for your problem.
But I have to admit I had to smile ("grinsen" in German is a much better word for it) when I saw your title:
Freezing even when >30°C
Click to expand...
Click to collapse
Lol perfect device for overclocking....
Sent from my GT-N7000 using Tapatalk 2
warfareonly said:
Lol perfect device for overclocking....
Click to expand...
Click to collapse
few months ago i had Samsung Omnia i900 only working in fridge or when it was freezed with frost spray
this phone is mystery. When the battery is fully charged, it works like a charm. I can twist the phone as much i want, it won't freeze. I don't understand.
My n7000 has also this same problam pl. any one help me..
Tuxxperia said:
this phone is mystery. When the battery is fully charged, it works like a charm. I can twist the phone as much i want, it won't freeze. I don't understand.
Click to expand...
Click to collapse
My galaxy note n7000 has same problem from last 3 days i also not found any solution for this when i use phone without scrow fited on back cover my phone working fine only in 1 % of battey but when i tite scrow in back cover my phone frize at galaxy boot logo or samsung logo with or without red line...pl. any one help me... pl....
You guys started having strange issues with ur notes. Maybe its something like a self destruct programmed on your phones so that after a year or two people will switch their phones. Besides the bigger the phones are getting the more issues they are having.
A phone should be like a device that shouod work flawless, in case of emergency one is needing to make a call and found that the phone freezed.
Sometimes i blame everything to android. Despite years of open development. Its yet not stabilizing, i guess because of it being open source vendors are putting crap in it making it more vulnerable to issues.
I dont rely on android rather i use a cheap phone for calls and text or iphone. Its just good for internet, ebooks, movies, music and camera.
Sent from my GT-N7000 using xda app-developers app
Try pulling out the battery and then let the phone dry like a pair of wet socks. Clean the contacts and fit any loose thing that there may be.
Check your cable, if is loose or not, this way you could find if there were any unwanted sparks applied on the device.
Notice how it gets hot when is plugged in and you're using it? the battery reaches quickly 55 degrees which is not optimum, wait to cool to below this temperature.
My condolences in this sad event. Take care.
Hi there,
I fear I hard bricked my G1 (after long years of good service as gps device thanks to a 2600mAh battery).
Since it was quite slow on CM7, I downgraded it to CM6.1. But this would'nt boot. (boot loop)
So I did a bit of reading and decided to downgrade the radio too. I downloaded a flashable zip and flashed it the usual way in the CWM recovery - which didn't finish (after a few minutes), so I removed the battery.
Since then my G1 wont start any more. On top of that, it want event charge. If I try to charge it the status led wont event light up. (I already tried it with two different batteries, both yield the same results.)
Funny thing though: If I don't charge it and let it sit for a few hours, the status LED very shortly lights up when pressing the power button. (But other than this nothing happens and if I press the power button again shortly after the LED stays dead.)
So ... I fear the problem is hardware and not software related.
Does anybody have an idea what could be broken (software or hardware) and if it's software based if there's a way to revive my phone?
(Before anybody asks ... yes, I have newer android phones, but I really live my G1 for nostalgic value so if there a way to get it running again I definitely would try.)
thx a lot,
Bapf
Sounds like you need JTAG, and don't take this the wrong way, but flashing firmware isn't the usual way, its the way you brick your phone. If possible always use fast boot to flash firmware or you are asking for a brick.
You can buy the JTAG equipment yourself and the software is free. Or you can see if you can find someone locally to do it. Unless you have a particular sentimental value to this phone it maybe cheaper to buy a new one.... Sorry for bad news
Sent from my Nexus 7 using xda premium
Bricked G1 - Try Again w/ SIM Card IN!
I had the exact symptoms mentioned in this post - tried nearly everything until I finally put back in the SIM card (even through I don't have T-Mobile anymore) - it booted again and registers the AC adapter and/or USB cable. Hope this helps some who are struggling at this level as I did!!
Bapf said:
Hi there,
I fear I hard bricked my G1 (after long years of good service as gps device thanks to a 2600mAh battery).
Since it was quite slow on CM7, I downgraded it to CM6.1. But this would'nt boot. (boot loop)
So I did a bit of reading and decided to downgrade the radio too. I downloaded a flashable zip and flashed it the usual way in the CWM recovery - which didn't finish (after a few minutes), so I removed the battery.
Since then my G1 wont start any more. On top of that, it want event charge. If I try to charge it the status led wont event light up. (I already tried it with two different batteries, both yield the same results.)
Funny thing though: If I don't charge it and let it sit for a few hours, the status LED very shortly lights up when pressing the power button. (But other than this nothing happens and if I press the power button again shortly after the LED stays dead.)
So ... I fear the problem is hardware and not software related.
Does anybody have an idea what could be broken (software or hardware) and if it's software based if there's a way to revive my phone?
(Before anybody asks ... yes, I have newer android phones, but I really live my G1 for nostalgic value so if there a way to get it running again I definitely would try.)
thx a lot,
Bapf
Click to expand...
Click to collapse
I don't know if this will work,as I've never encountered a situation such as this, but have you tried bootloader(power button+camera button)?
If you can get it into bootloader, then I have the original rc29 DREAIMG.NBH file(plus, rc29 is the best place to start if you want to root it or install a custom rom).If you get it working and just want stock 1.6, i have those updates as well.
(all said out of hope, I have a g1 and I love it,I'm really glad that someone else shares my enthusiasm!!)
If bootloader works, give me your email and i'll send you the files, good luck!:fingers-crossed:
Nope. It won't even start the bootloader.
Sent from my Nexus 4 using xda app-developers app
Well thats unfortunite, I guess it's just for a soft brick.
This is a very strange problem. I never saw anything similar in my life and I searched for someone with a similar problem but I cannot find anything. So I am posting this thread, maybe someone here knows what I should do.
This tablet has been riddled with problems, but this one makes it close to useless. I had several problems since I got the tablet where it won't wake up after sleeping and you had to reboot the thing, where the dock is not available after sleeping and you have to undock and redock it, where the battery drains while sleeping etc etc. Annoyances but I can live with them. I know there is a fix for the dock and you have to send it to Asus, but shipping is expensive so I'll learn to live with it.
This problem though.. this is a big one. So just to clarify, the tablet is rooted with the original 4.4.2 ROM. I did not make any changes in the past week. Yesterday morning, I woke up and used it normally. Later that morning I unplugged it from the charger and that's when I noticed this problem. So while it is connected to the charger the tablet will function normally. After I unplug it the tablet will freeze after a few seconds, reboot on its own and then it will boot until the icons start coming up. Usually after this you get the lockscreen, but instead the screen will black out. After a few seconds the icons start coming back and the the screen will black out again and so on. This loop will continue forever unless you plug the charger in. When you plug in the charger, the icons will come up and after you get the lock screen (instead of the black screen), and you can use it normally. If you unplug it again, the boot loop starts again. This behavior is the same whether using the dock or not.
I don't want to do a factory reset just yet if I can. Last time I did a factory reset, the tablet would not boot and I had to send it back for a replacement. When I get to the fastboot screen, trying RCK I get the dead Android with the red exclamation, and cold booting does nothing.
Any suggestions please? Any kind of log I can get to help? I can post a video if the problem is not clear.
Thanks.
pantera1989 said:
This is a very strange problem. I never saw anything similar in my life and I searched for someone with a similar problem but I cannot find anything. So I am posting this thread, maybe someone here knows what I should do.
This tablet has been riddled with problems, but this one makes it close to useless. I had several problems since I got the tablet where it won't wake up after sleeping and you had to reboot the thing, where the dock is not available after sleeping and you have to undock and redock it, where the battery drains while sleeping etc etc. Annoyances but I can live with them. I know there is a fix for the dock and you have to send it to Asus, but shipping is expensive so I'll learn to live with it.
This problem though.. this is a big one. So just to clarify, the tablet is rooted with the original 4.4.2 ROM. I did not make any changes in the past week. Yesterday morning, I woke up and used it normally. Later that morning I unplugged it from the charger and that's when I noticed this problem. So while it is connected to the charger the tablet will function normally. After I unplug it the tablet will freeze after a few seconds, reboot on its own and then it will boot until the icons start coming up. Usually after this you get the lockscreen, but instead the screen will black out. After a few seconds the icons start coming back and the the screen will black out again and so on. This loop will continue forever unless you plug the charger in. When you plug in the charger, the icons will come up and after you get the lock screen (instead of the black screen), and you can use it normally. If you unplug it again, the boot loop starts again. This behavior is the same whether using the dock or not.
I don't want to do a factory reset just yet if I can. Last time I did a factory reset, the tablet would not boot and I had to send it back for a replacement. When I get to the fastboot screen, trying RCK I get the dead Android with the red exclamation, and cold booting does nothing.
Any suggestions please? Any kind of log I can get to help? I can post a video if the problem is not clear.
Thanks.
Click to expand...
Click to collapse
Hi, to start this reply, I'll let you know that I am no professional at any of this stuff. I am a regular person that has had experience with flashing ROMs and whatnot. In my opinion, this seems like a software (maybe hardware) related problem. So there are a couple of options you have here.
1. Are you still under your warranty period? You could return it and get another one (easy fix)
2. You could try to factory reset, and if it doesn't turn on, rma the tablet (which it sounds like it may be cheaper to just buy a new one anyways)
3. You could try unlocking the bootloader. Then install a custom ROM (kind of risky, but might be less risky than #2)
Overall, you are not in an amazing spot with your tablet. It saddens me to see all the problems with asus's tablets. I have been with them since the transformer prime because of their laptop like tablet makes it easy to use in school, but its always been a struggle staying with their lineup. I have returned their tablets multiple times. Please update when you can
Sent from my SCH-I545 using Tapatalk 2
If you have a microSD in the tablet take it out and try to boot it. I have seen the weirdest problems because of a card on the fritz....
Second possibility: Hardware. The behavior (working fine when connected to power) seems to indicate it doesn't get the charge it needs from the battery. Could be that it is going kaputt. It's not totally fried but enough that the tablet does not get a reliable charge from the battery.
Third option would be to reflash the firmware. That would eliminate a software problem. You will loose root if you do that...
Since you're still on the original firmware, I assume you did not unlock the bootloader and rooted with Towelroot - correct?
Whatever you do, backup everything you care about off the tablet now....
Thanks for your replies/suggestions. I could not use towelroot as it was on 4.4.2 (I think I read it is not possible). The bootloader is unlocked. This is my second tablet as I had returned the original one. I tried putting Cromi-X on it, and when I got to the step to factory reset it (using fastboot), the thing just was stuck in an endless loop. I could not even get to fastboot and my PC wouldn't recognize it. All it did was boot to the ASUS logo (and the message that the bootloader was unlocked) and reboot.
So this is the replacement unit and the charging issue was the problem. I say was because believe me or not the tablet is now smashed to bits. Since it must always be connected with a charger to work, I was carrying it around docked as I usually do and forgot that it was plugged in. I have resorted to an extra long extension cord with the charger plugged in to walk around. Anyway I forgot it was plugged in, the extension cord reached its limit and the charger cord yanked the tablet out of my hands and onto its side - screen facing away. I sweared, feared the worst and went to pick it up. The good news is that it still boots. The bad news is that the screen is completely smashed. The back cover is bent at one corner and the glass is smashed at that corner with cracks running to the other side. The touchscreen is not working anymore either. To add insult to the injury the tablet still only boots up with the charger plugged in..so there's that.
I don't know what to do now. I have contacted ASUS for a possible RMA but got no response yet. The thing is I don't feel like spending more money on it given the problems experienced. A screen with digitizer on ebay is about €75..so not exactly cheap.
I guess we can close this thread as it is now pointless. I hope no one has to go through my experience and that maybe it was a one off thing.
Thanks again to whoever replied. I appreciate it.
Hello, I've had my G Watch R for not quite a full week so far and I've really enjoyed it. Two days ago, I believe that I let the battery die so I placed it on the charger before going to bed. When I woke in the morning i grabbed the watch off the charger without looking at it. Just before i stepped out the door i noticed that it wasn't waking up and It wouldn't even power on. I ran back and slapped it on the charger thinking that it would be more than charged by lunch time. Thats when i noticed the apparent boot issue you can see in the video attached. It hasn't been dropped at all and I have the basic apps installed; facer, watchmaker etc. At this point, Is there anything that I can try short of sending it back?
I've left it on the charger for 24+ hours, it gets slightly warm and stays in the boot loop. As soon as its taken off the charger it has no visible charge and refuses to respond to anything. I purchased it through amazon, so I'm thinking it shouldn't be an issue for me to return it...
http://youtu.be/GgF3iXAhTTI/
Sorry i tried to embed the video but the youtube link for xda seems to be breaking the url somehow
So I have already initiated the return process with amazon and it should be pretty painless. I have almost 3 weeks to send it back, so if anyone has any tips/tricks or ideas I'm more than open to try them....The watch is 100% stock as far as firmware or root is concerned.
Any luck with this? I just got back an RMA for a broken touch sensor, I don't want to have to RMA it again.
try to see if you can get in to the bootloader, and restart the watch from there
i have notice when i charge the watch from empty (so thewatch boots up while charging) it causes problems, usually boot loops as well
I just watched the video (should've done this before hijacking the thread, sorry) and it seems like I'm having a different issue. Instead, mine does the android boot animation, the goes to "Starting Apps" and counting ("x of y Apps"; the y value seems to be different every time), then "Staring Apps" with no count, then it says "Powering Off" and shuts off. But I will post my experience in case someone else with my issue finds this thread.
I'm back up & running today. I got it into the bootloader last night and put it on the charger before I went to sleep (to avoid battery rundown by bootlooping while it charges). I woke up this morning to it bootlooping again. I'm guessing that it restarted itself sometime during the night. I took it off the charger and let it sit for a while (it was pretty warm, so I figured it would be better to let it cool down before trying anything else). I tried to restart it again after about a half hour, but it still only got to "Starting Apps" before shutting off. I reflashed the stock boot, recovery & system images found here: Stock Boot, Recovery and System for G Watch R . I restarted it and completed the initial pairing process (due to wipe when I unlocked it in order to flash system image) and it is now working.
I don't know if what I did actually fixed anything or if it just decided to start working, but I will post again if something happens again. If you don't see any more replies from me, then all is still OK.
EDIT 6/22/15 9:53 pm EDT: No good, see below.
To workaround the bootloop while charging, you can boot into recovery (swipe 10 to 4 a clock while Logo is shown, select and press okay to recovery), than charge battery for a while, after that, you can boot to as normally to AW-system and charge to fully battery!
You can charge with USB on PC, it's work fine for me.
scidon37 said:
I just watched the video
I don't know if what I did actually fixed anything or if it just decided to start working, but I will post again if something happens again. If you don't see any more replies from me, then all is still OK.
EDIT 6/22/15 9:53 pm EDT: No good, see below.
Click to expand...
Click to collapse
So your gwatch r started doing the same thing again? I have the same problem and it won't connect to the computer via fastboot or adb. How did you get on with the RMA? I cant send mine back due to voided warranty. Still hoping for a solution.
Have you tried taking it off the charger and booting it? Also are you running custom software?
bricked watch
atmosphrericks said:
So your gwatch r started doing the same thing again? I have the same problem and it won't connect to the computer via fastboot or adb. How did you get on with the RMA? I cant send mine back due to voided warranty. Still hoping for a solution.
Click to expand...
Click to collapse
Ever find a fix for this? I've been searching like mad the last few weeks. :/
biohazard1150 said:
Ever find a fix for this? I've been searching like mad the last few weeks. :/
Click to expand...
Click to collapse
So i took off the back plate, and found that the spring contact pins inside the watch weren't making good connections to the connect points on the inside of the back plate. Be careful, they are fragile, but you want to bend them out slightly. If you can source parts, get a new contact pin module.
After this, i was able to connect my watch and flash over stock firmware.
I can't guarantee this is what is happening with yours, but let us know if it does work.
I've scince broken the screen and can't find where to get parts!
atmosphrericks said:
So i took off the back plate, and found that the spring contact pins inside the watch weren't making good connections to the connect points on the inside of the back plate. Be careful, they are fragile, but you want to bend them out slightly. If you can source parts, get a new contact pin module.
After this, i was able to connect my watch and flash over stock firmware.
I can't guarantee this is what is happening with yours, but let us know if it does work.
I've scince broken the screen and can't find where to get parts!
Click to expand...
Click to collapse
I still haven't found a fix. My charging works fine, but no PC connection. The bootloader/fastboot wont come up, no logo or anything. I'm sure the EMMC chip is fried, it sounds like many are seeing this issue, some with a black screen and some with a snowy screen. I've had several galaxy phones do the exact same so I'm doubting it can be fixed without going to the manufacturer which mine came from redflagdeals and LG wont service the random online store purchases
I had to take the back off and clean and adjust the contacts that make contact through the back panel. Then I could connect via fastboot.
ouranos2k said:
You can charge with USB on PC, it's work fine for me.
Click to expand...
Click to collapse
This solved my problem. As soon as I plugged it into my PC it booted just fine
ouranos2k said:
You can charge with USB on PC, it's work fine for me.
Click to expand...
Click to collapse
This works for me too! Thank you!
Sent from my SM-N920C using Tapatalk
I have the feeling I'm going to get repetitive here guys, but I've been reading the troubleshooting threads for over an hour and couldn't find an answer to help me.
Last saturday I was to lazy to move from the couch, so I watched as my S3 Mini ran out of battery. I got the "phone is turning off" screen as usual. Later I went to bed, but as I needed my alarm to go off in the morning I tried turning it on again, and nothing* happened. Plugged it on the wall, nothing*. Replaced the battery, nothing*. Gave it a good half hour plugged, and as you can guess, nothing*.
* when I say nothing, I mean it won't light up, won't vibrate, won't wink for me, won't load any kind of error, it's actually just like if you were trying to turn on a phone without any battery connected, no grasp of life comes from its poor soul.
The only moment I could see some action on the device is when I tried connecting it on the PC a few hours ago, as it installed drivers to Windows. Right after installing the drivers however, it won't show in the file explorer. I've tried to detect it with a few development tools such as ORT and Odin and there was no sucess either. Download or Recover mode will not work as well.
One thing I think worth mentioning, is that ever since I rooted it a couple of years ago, whenever I tried to recharge it while it was off, the standard "green charging battery" would never appear. What would appear on the screen was a freezed loading icon (the one that keeps roling again and again, but frozen). This particular issue never came off, even reseting it or installing new ROMs.
I always used Maclaw's, some of the latest 4.x, because I tought the 5.x was to heavy for the s3 minis.
I've read some about USB JIGs and stuff, but what makes me very curious is what the heck?! The phone was working just fine, the battery runs out and I have a brick? Is this possible? Can anyone tell me any work around?
I apologize for possible grammar mistakes.
ScrewedImei said:
I have the feeling I'm going to get repetitive here guys, but I've been reading the troubleshooting threads for over an hour and couldn't find an answer to help me.
Last saturday I was to lazy to move from the couch, so I watched as my S3 Mini ran out of battery. I got the "phone is turning off" screen as usual. Later I went to bed, but as I needed my alarm to go off in the morning I tried turning it on again, and nothing* happened. Plugged it on the wall, nothing*. Replaced the battery, nothing*. Gave it a good half hour plugged, and as you can guess, nothing*.
* when I say nothing, I mean it won't light up, won't vibrate, won't wink for me, won't load any kind of error, it's actually just like if you were trying to turn on a phone without any battery connected, no grasp of life comes from its poor soul.
The only moment I could see some action on the device is when I tried connecting it on the PC a few hours ago, as it installed drivers to Windows. Right after installing the drivers however, it won't show in the file explorer. I've tried to detect it with a few development tools such as ORT and Odin and there was no sucess either. Download or Recover mode will not work as well.
One thing I think worth mentioning, is that ever since I rooted it a couple of years ago, whenever I tried to recharge it while it was off, the standard "green charging battery" would never appear. What would appear on the screen was a freezed loading icon (the one that keeps roling again and again, but frozen). This particular issue never came off, even reseting it or installing new ROMs.
I always used Maclaw's, some of the latest 4.x, because I tought the 5.x was to heavy for the s3 minis.
I've read some about USB JIGs and stuff, but what makes me very curious is what the heck?! The phone was working just fine, the battery runs out and I have a brick? Is this possible? Can anyone tell me any work around?
I apologize for possible grammar mistakes.
Click to expand...
Click to collapse
try to plug in the phone into charger & leave it there like 20 mins or more. battery loads then.
then try access samsung download mode, if you cant the phone is probably useless (brick for ever) because itslike mthe last standing thing.
& sorry i say that but thats typically samsung behaviuor. there allways this kind of threads in the samsung forums of xda... other manufacturer can mostly be restored or atleast you know what make it dead.
Exactly the same problems happening to me.
This is my thread:
http://forum.xda-developers.com/galaxy-s3-mini/help/sgs3-mini-dead-t3085031
Can you try to follow what appears on this link? (I can't by now because my PC is broken)
I think won't do nothing because you won't be able to access to the recovery mode on android, as me, but to try...
http://forum.xda-developers.com/showthread.php?t=1840030
bejunk said:
try to plug in the phone into charger & leave it there like 20 mins or more. battery loads then.
then try access samsung download mode, if you cant the phone is probably useless (brick for ever) because itslike mthe last standing thing.
& sorry i say that but thats typically samsung behaviuor. there allways this kind of threads in the samsung forums of xda... other manufacturer can mostly be restored or atleast you know what make it dead.
Click to expand...
Click to collapse
Hi there,
Thank you for your interest but I have passed this point already. Tried a brand new battery I had laying down in the drawer (which was fully charged with an universal charger) and there is no answer to any attempt of turning it on. Via recovery, download or normal boot.
CrashOverride93 said:
Exactly the same problems happening to me.
This is my thread:
http://forum.xda-developers.com/galaxy-s3-mini/help/sgs3-mini-dead-t3085031
Can you try to follow what appears on this link? (I can't by now because my PC is broken)
I think won't do nothing because you won't be able to access to the recovery mode on android, as me, but to try...
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
Hello there,
I'm sorry to hear I'm not the only one affected by this bug (lets call it a bug). This shows there is a lack of concern from Samsung on dealing with this issues, and thus we see that old programmed obsolescence.
I will try that later on the weekend, and I come back here with an report.
Cheers
ScrewedImei said:
Hi there,
Thank you for your interest but I have passed this point already. Tried a brand new battery I had laying down in the drawer (which was fully charged with an universal charger) and there is no answer to any attempt of turning it on. Via recovery, download or normal boot.
Hello there,
I'm sorry to hear I'm not the only one affected by this bug (lets call it a bug). This shows there is a lack of concern from Samsung on dealing with this issues, and thus we see that old programmed obsolescence.
I will try that later on the weekend, and I come back here with an report.
Cheers
Click to expand...
Click to collapse
this guide useless for you. how u want flash things with odin if u cant enter download mode at all??
im really sorry for you that this phone is dead. just can give you 1 advice, dont buy samsung in future.
I have been repaired my phone successfully!!!
I just needed to change two capacitors on its motherboard, and that's it.
Here the video where I have found the info and how to do that. It's in Spanish but easy to understand for you I think. But if you need some help, send me a PM.
can you take a picture from the location of the 2 capasitors and the types of it
Hi everyone.
I have some news. It took me a while but I followed CrashOverride93's advice on that video. It actually solved one issue, as I now can turn it on, but now I have a second problem, I'm stuck on a boot loop, with acess to Download mode ONLY. No recovery.
Considering where my issue started, and where I am now, I have tried the following:
- Flashed via Odin stock ROM, kernel;
- flashed Wipe;
- flashed PARAM;
- three button combo.
So far I couldn't get it pass the boot loop. Any thoughts?