Android phone auto-brick itself overnight - Hardware Hacking General

When I woke-up this morning, my android phone (Galaxy SII Plus - Default kernel android 4.1.2 - not rooted) was off. I turned it on and it did some "Application optimisation". It automatically rebooted a few times, than I tried to used it. It was very unresponsive. Android keep popping up messages saying that apps like Skype, Google Plus, Google Play Store, etc. crashed. I was really pissed, I never asked for that "update" (or whatever that was) in the first place (I set it to NOT do any update automatically)...
It was completely unusable. It was constantly automatically rebooting. Eventually it popped up the "Application optimisation" message again, the screen turn black and never came back. I waited for about 30 minutes thinking it might be doing something hardcore... but nothing happen.
- Buttons -
I tried to remove the battery, press any combination of "Home" + "Volume up / down" + "Power" buttons but nothing works. The screen stays black, no sound, no vibration, nothing. I can't even go into "Download mode".
What was that update??? How come an automatic Android core update brick my phone??? Did someone manage to steal Android private keys using the OpenSSL Heartbleed bug and impersonalised Android to push malicious updates? I bought my phone in an other country, so I can't go back to the shop. What can I do?
BTW I'm on Ubuntu. I have been using almost exclusively Linux for the last 20 years so feel free to give hardcore suggestions / command lines. I'm also willing to put the screwdriver in the phone if that can help...
Thanks
Gael
------ EDIT ------
- Heimdall / OneClick.jar -
I just tried the OneClick.jar method. It didn't work. I think I have to go into Download mode which is currently impossible.
http://forum.xda-developers.com/showthread.php?p=15330252
------ EDIT ------
- Odin / Kies -
I installed the USB Drivers, Odin and Kies Files on a VM. When I put the battery in the phone, I can see the USB device in the VM (at lease I know that the VM can see the phone) but it's identified as "Unknown device 0A5C:E720 [0202]". The device vanish after about 2 minutes. I assume that the phone run something very low level, like a BIOS, than shutdown the whole thing for some reason. Neither Odin nor Kies can see the phone during that 2 minutes.
But the good news is, something actually happen when I put the battery in. There is no sign of life on the device itself but I can see something from the computer... There is life inside, so there is still hope. If I could put it in Download mode, that would give me more options.
How likely is a USB JIG device to work on such phone state? It's sending something through the USB port, so maybe it would listen to the JIG and go into Download mode...
------ EDIT ------
- USB JIG -
I made a USB JIG from a 270k ohm resistor, some hair thin copped cable and piece of cardboard. It's not pretty, and I don't think I will be able to use it more than once, but it worth a try...
The micro USB female connector is tiny. I'm pretty sure the 2 cables were on the right spot, and I tested the JIG to be sure the 2 copper cables do not short cut themselves before putting the battery in. The reading from my electric tester was 270k exactly, so the bundle is safe. I put the battery back in, waited a few seconds, but nothing happen...
I'm not 100% sure that my JIG works (maybe the copped cable were not pressing down hard enough). But I don't think any JIG can save my phone at this point.
- JTAG ? -
I had a look at some JTAG. That looks over complicated, but that's probably the only way I can reset the boot loader. Those things are very expensive. I will think about it. I'm not even sure the boot loader has been modified. My phone is not rooted, as long as I know, that partition is RO so even a virus could not mess with it...
Would I see the Samsung Galaxy logo if I boot the phone and the boot loader were ok? Or is that logo part of the OS?

Wow...hope everything works out well for you
Sent from my T-Mobile myTouch Q using xda app-developers app

Related

Won' t turn on! Tried all suggestions

Yes I have read all posts regarding "Screen Of Death" issue and i have tried all the suggestions. But still, my 10.1 won' t turn on. I have left it drain the bat for 2 days now.
Even if i plug it to the charger there is no sign of battery charging. Hence just blank black screen. any other idea before I have to go to the Service Center. Thanks. Any help would be appreciated.....
Connect the USB to a Windows computer and press Power + Volume Up for 30seconds. Do you hear a Windows "new hardware found" sound?
Thanks... Tried... Still fail. My PC only signaling found new hardware but fail the installation process. I guess because the tab is still not ON. Help....
It seems my PC recognizes the tab but can't find the driver. I can also feel "warm" near the power button area when i connect it to any electricity but still no TURN ON or BATTERY CHARGING INDICATION.
Have you tried to charge it with the wall charger for at least 2hrs and then unplug it and hold powerbutton 10 sec?
Sent from my GT-I9000 using Tapatalk
AndreBrian said:
Thanks... Tried... Still fail. My PC only signaling found new hardware but fail the installation process. I guess because the tab is still not ON. Help....
It seems my PC recognizes the tab but can't find the driver. I can also feel "warm" near the power button area when i connect it to any electricity but still no TURN ON or BATTERY CHARGING INDICATION.
Click to expand...
Click to collapse
Actually, that is what I was expecting as result.
The Power + Volume Up enables the nvflash APX mode, the screen remains totally black. I simply wanted to know if the tablet works and the culprit is just the screen. From what you say, we get the expected results... Windows detects the new hardware so the tablet works.
Now try the opposite: Power + Volume Down, hold it for 30seconds.
If you don't see nothing on the screen, it is probably a screen contact that got lose... you need to service it by Samsung.
yes done that. Still not ON. When I plug it I can feel it is working since I can feel "the warm" but screen still is blank
Then you already know what to do.
No biggie, Samsung will send you a replacement for sure.
yqed said:
Actually, that is what I was expecting as result.
The Power + Volume Up enables the nvflash APX mode, the screen remains totally black. I simply wanted to know if the tablet works and the culprit is just the screen. From what you say, we get the expected results... Windows detects the new hardware so the tablet works.
Now try the opposite: Power + Volume Down, hold it for 30seconds.
If you don't see nothing on the screen, it is probably a screen contact that got lose... you need to service it by Samsung.
Click to expand...
Click to collapse
yes. In fact now the APX is still working trying to find " a new hardware ". Should I cancel it and try the POWER+VOL DOWN now?
Yes, go ahead.
DONE the Power + Volume Down still not ON. BTW the APX Could not find any driver? Is it normal. Before this happens in fact i can transfer any file with my PC through MTP. Thanks again for your help. Hopefully you still know any other solution.... Keep waiting
The APX driver is included into nvflash package, it does not matter if you install it or not at this point. The advantage of this test is that the APX mode keeps the screen off in purpose, while allowing you to flash the tablet through a CMD window (only if you have an unlocked bootloader). We used this trick to determine if the core of your tablet works... we wanted to isolate the problem related to your screen.
I recommend you to contact Samsung and have the tablet serviced. Some screens lose a contact point when you drop the tablet by accident or if a soldering point is weak... The heat generated inside is enough sometimes to sever a lose circuit connection. Either ways, you do NOT want to keep this tablet.
I hope you did not flashed the tablet with some custom ROM, or else Samsung might void your warranty.
OK. Then the only thing i can do is go to SC.......Hmmmmm I am still using stock rom but unfortunately i did root the tab already. Is it bad judgement??? Thanks anyway.
I really hope it is only the screen connection lose issue. But just for curiousity. If only the screen keeps OFF, does it mean I actually can still check that my gtalk on the tab still connects? How this thing works??? since i just check with my phone my gtalk on tab is off.
You ordered the tablet online from Samsung or you bought it from a retailer like Best Buy?
I bought it from retailer. BTW is there any kind of USB JIG for the tab similar to SGSII? I just thought maybe this can help solve the screen of death issue. Ha ha ha ....
Perfect, just go see the store and explain to them nicely the issue. I'm sure they will exchange it for you.
Forget about the JIG or anything else, your screen is gone wacko... What you do now is try to force a blind guy drive a car... Just go exchange the tablet.
Ok I' ll do that. Thanks for your info and help. Hopefully problem will be solved soon.
I had the same issue but I couldn't return to the store so I went through support. They don't have parts yet so they just send you a different unit. In total it took 2.5 weeks for me and I ended up with an unlocked unit
Sent from my LG-P999 using Tapatalk
x-ravin said:
I had the same issue but I couldn't return to the store so I went through support. They don't have parts yet so they just send you a different unit. In total it took 2.5 weeks for me and I ended up with an unlocked unit
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Damn, it took 2.5 weeks to get a new unit?
The good news is, it's recoverable. The bad news is, it's going to take a long time.
Keep it off the charger.
Hold down the power button to get it cycling through APX mode while plugged into your PC (can hear the USB connection sound in Windows).
Tape the power switch down, verify it's still going into APX mode after taped, then unplug it.
Leave the tablet alone for a few days. Think about puppies, chocolate, bouncing breasts, whatever makes you happy, and forget about the Tab.
Come back, plug it back into the PC, see if you still hear it connect. If so, walk away again, come back the next day.
When it finally stops going into APX mode, plug it into a wall charger and leave it alone for about an hour, it should start charging normally, and once it's got charge showing, it'll power up normally.
Rule of thumb is it'll take about a full day for every 10% of charge that was on the battery when it went down, if you keep the power button taped down.

[Q] S4 Broken Screen - ADB Not Working - Cannot Activate Debugging

Been trying for hours now to try and sort out an issue I am having. My S4 is damaged, the phone works but the screen and digitizer is broken. I want to check a few sms messages, access and control the phone from my PC and basically make a complete clone/image of my phone. I cannot for the life of my figure out how to do this.
I use windows 7, I have installed SDK tools, have ADB/fastbook etc. Device isn't found with ADB. Spent hours reading information about installing correct drivers, which I have done. No luck what so ever. The phone is not rooted, developers tools is not on, usb debugging is not on either.
I am starting to think this is a lost battle as I cannot sort this out.
Any ideas?
Thanks
Bump.
Anyone? Is there no way to solve this problem? Tearing my hair out.
Best bet (given ADB doesn't work) would be to root the phone & get a custom recovery on (via Odin; this is might be very difficult if you can't somehow have the phone & PC recognise each other - you don't need to have had debugging on though) then do a nandroid backup (someone using the same recovery/version might be able to walk you through the button presses.
What S4 variant (model number) are we talking about ?
MistahBungle said:
Best bet (given ADB doesn't work) would be to root the phone & get a custom recovery on (via Odin; this is might be very difficult if you can't somehow have the phone & PC recognise each other - you don't need to have had debugging on though) then do a nandroid backup (someone using the same recovery/version might be able to walk you through the button presses.
What S4 variant (model number) are we talking about ?
Click to expand...
Click to collapse
GT-I9505 is the model number that is displayed behind the battery. The screen is broke and so is the touchscreen (completely black). I tried to figure out via ODIN but that wouldn't recognise the phone either. I assumed you'd need to boot in recovery/download mode but because I cannot see anything on screen, when I do the volume down, home and power thing I do not know what to do next so the phone boots up normally. I know this because I have unread SMS and when phone loads my SMS tone goes off.
Really not sure how to get around this.
You're going to have to get it into DL mode somehow (don't need to use home button on S4, just vol down/power); try a jig. Once you've done that, then you need to get the phone & PC to recognise each other. If you're having problems with that, prepare to continue to do a lot more reading/trying stuff if you're having PC-side driver issues (there's a lot of threads on here re: the issue). There's also an 'Odin troubleshooting' guide in S2 General by Hopper8 which is worth looking at as much of the stuff he suggests also holds true for the S4 (except the firmware stuff, which is obviously different).
There's not going to be any quick & easy in this instance, I'm afraid. It's going to be hard work.
Edit - Also..USB board/port on the phone might also be damaged, so when you reach the point of having tried everything on the PC-side & everything you can possibly try on the phone-side, replace the USB board/port on the phone. This is quick/easy/cheap (<US$20) to do & might just enable you to get things done where everything else has failed.
Extra edit - And...A jig working (getting you into DL mode) or not is probably a good test of whether the USB board/port on the phone is still good; I.E if the jig works, the board/port is probably still good, if it doesn't, the board/port might be shot as well.
The USB is fine because when I plug the phone in when in normal boot it recognises the data storage. I will try to boot in DL mode. Are there any gestures my S4 will do when booting in DL? Vibrations? As I cannot see anything on screen that will indicate it's worked. I think that once I can get the phone to work with ODIN/ADB I will be good to go as I am relatively tech savvy.
Nope. You're going to by flying blind so far as having no screen/no vibrations in DL mode goes. You're going to be relying on the jig working, and once you hook it up to the PC & fire up Odin, you'll know straight away whether you've got a successful connection up & running (as screenshots in the many Odin guides on here will show you).
I see, will just have to keep trying.
So on the S4 it's hold power and volume up, then wait? or do I need to press anything else afterwards? Or is it power and volume down?
Thanks
No luck with download mode. Girlfriend has a note 2, and her method is Vol down, home and power button. Screen comes up almost immediately with confirmation. Volume up needs to be pressed to confirm. Tried to replicate with S4, no avail.
No luck with starting S4 in download mode. I have followed video on youtube. Supposed to be Vol Down, Home and Power button. Wait till vibrate and warning screen, then press up. Because I cannot see the screen I cannot see the warning screen. But I Hold for 4 seconds, release just after vibrate and then press up, but phone seems to boot up in normal mode.
Ok, finally in download mode, now what? I know it works because it installed new drivers and device manager states a samsung modem. Need to try and clone and do what I need to do ASAP and taking to store tomorrow to exchange for new one.
Any last minute ideas?
Thanks
ODIN3 v1.85 shows a yellow box, this is good right? I downloaded CWM from http://galaxys4root.com/clockworkmodtwrp-recoveries/
What do I need to do next, do not want to make this worse, I just need to enable usb debugging or at least be able to use adb, I am good to go from there
Only a few hours left? Surely someone knows what Flash I need to do to allow me adb access???
Right, go into recovery mode...adb now works.
What do I need to do to enable debugging?
Edit:
I can't get adb to work... error: closed
any ideas
If you cant get adb to work in recovery then youre out of luck.
Incase this happens with new phone, always have a remote access app like Cerberus installed. MightyText is a pretty nice app too.
I see, ok no worries. Thank you anyways

[Q] Nexus 4 Damage Help

So first some back-story, I'll get right into it. I recently dropped my phone in some water. As soon as possible I dried off the outside, and let it sit. That was the only thing I could do at the time, I had no rice, no tools to open up the phone, anything. I ended up with a solid red light, and everything unresponsive.
The next day I got some tools to open her up. There was pretty extensive corrosion to the motherboard, so using some alcohol I cleaned it all off, rinsed it, and let it dry. I also took apart everything else and cleaned any corrosion. The inside looks brand new. However, this isn't the point of the thread.
It appeared my cleaning helped quite a bit. Upon re-assembling and plugging in, I immediately got a charging sign on the phone. However, after trying to power on, I got no response. Additionally, The charging signal went out after about 20 seconds, and the whole phone became unresponsive again. I can do this process as many times as I want, but the same thing happens every time.
So I tried a different approach. First I hold down both volume rockers plus the power button, and plug it in while holding them down. This puts the phone into "download mode" However, once in download mode the phone is, again, unresponsive. After plugging into my laptop, my computer recognizes the phone, but not as "Nexus 4," but as "Full JellyBean on Mako."
Is there anything I can do about this? I've heard about drivers being able to be installed when in download mode, but I would not know what these are, where to get them, or how to install them. I really don't mind if my phone never works 100% again, I doubt it would. I just want to be able to get into the storage so I can recover some of the files I lost.
It's also probably worth mentioning I have not gotten a solid red light after the clean. Once in a while I will get a blinking red light after plugging it in, but after less than a minute it stops and goes through the charging/stop charging phase I'm so familiar with. Any help at all would be appreciated, and thanks in advance.
The charging block and/or battery could be wrecked, for safety reasons and because it will probably become faulty soon you should change the battery anyway. If the charging block is broken flashing your phone could fail. It's also possible the board was irreparably damaged, but it's probably worth a try as the parts aren't too expensive.
DrFredPhD said:
The charging block and/or battery could be wrecked, for safety reasons and because it will probably become faulty soon you should change the battery anyway. If the charging block is broken flashing your phone could fail. It's also possible the board was irreparably damaged, but it's probably worth a try as the parts aren't too expensive.
Click to expand...
Click to collapse
After trying to figure more things out, I kept it plugged in for a while. It appears my battery actually holds at least a pretty good charge, as the indicator is full when I plug it in now. However, I don't know what you mean when you say charging block.
Also, I seemed to determine my power button isn't working either. I always thought no response to pushing it meant there was something else going on, but I am able to put it into "download mode" by just holding down the volume rockers and plugging it in. Is there a way to turn on the phone another way besides the power button? Also if not, will buying another power button fix the problem? I don't want to buy one then later figure out the reason it wasn't turning on was just a board problem, and not a problem with the button itself.
You can short the power button with a screwdriver or something should turn the phone on., By charging block I mean the secondary board that the micro usb port is a part of, it can be replaced fairly easily if necessary.
26694484 100
DrFredPhD said:
You can short the power button with a screwdriver or something should turn the phone on., By charging block I mean the secondary board that the micro usb port is a part of, it can be replaced fairly easily if necessary.
Click to expand...
Click to collapse
With a screwdriver? Enlighten me, I'd have no idea how to do that. If I had a faulty charging block, then my phone wouldn't be able to charge correct? My phone was plugged in for a while in download mode, and it gained a full charge from a relatively low charge. I also took the block apart and cleaned any corrosion, so I think that's still functional.
Some more progress, upon further attempting to turn the phone on, I was able to get it into fastboot mode. When plugging into the computer it is recognized, but as just "Android." I will type out what information is displayed here, minus serial number, as a new member cannot submit links in posts apparently.
FASTBOOT MODE
PRODUCT_NAME - mako
VARIENT - mako 8GB
HW VERSION - rev_11
BOOTLOADER VERSION - MAK0230d
BASEBAND VERSION - M9615A-CEFWMAZM-2.0.1700.98
CARRIER INFO - None
SERIAL NUMBER -
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - locked
Also, fastboot at the top (as far as I know) usually says "Start" or "Recovery Mode," but mine says "Restart bootloader." When I try switching with my volume buttons, nothing happens.
Another update, just in case anyone is still listening..
Str1ngcheese said:
Also, fastboot at the top (as far as I know) usually says "Start" or "Recovery Mode," but mine says "Restart bootloader." When I try switching with my volume buttons, nothing happens.
Click to expand...
Click to collapse
This no longer applies, for some reason I am able to switch through all modes, incliding "Start, Power Off, Recovery Mode, and Restart bootloader."
Str1ngcheese said:
Another update, just in case anyone is still listening..
This no longer applies, for some reason I am able to switch through all modes, incliding "Start, Power Off, Recovery Mode, and Restart bootloader."
Click to expand...
Click to collapse
Now that you're at this point, have you attempted to flash the phone with a stock image? I'd be weary of what the other poster said though and ensure your USB connection is holding steady because you don't want it dying half way through a flash because then you'll have a brick.
Monotoko said:
Now that you're at this point, have you attempted to flash the phone with a stock image? I'd be weary of what the other poster said though and ensure your USB connection is holding steady because you don't want it dying half way through a flash because then you'll have a brick.
Click to expand...
Click to collapse
I have tried actually. I used the Nexus Root Toolkit v1.8.0 to try and flash it. At first it wouldn't find the device, but through device manager I manually installed the usb_driver onto the phone. After this, the toolkit was able to find the phone. I attempted to flash the image, but it ended up staying in fastboot mode. The program then suggested I try to enable "force flash," which I did, and this time it was never able to finish because the phone tried to restart, but went through that "charging to unresponsive" state I described in my first post.
Upon trying to flash it normally again, it looks like maybe the phone has to be unlocked to do this properly? I then tried to unlock with the same program, but in order to do that, I need the power button to confirm I actually want to unlock the phone. So yet again, I need that power button working.
Any ideas/suggestions/solutions would be amazing.
Jellybean on mako means that your phone is in lgnpst/qcpnst mode. Looks like something failed to start and made the bootloader trogger that mode
Sent from my Nexus 4 using xda app-developers app
opssemnik said:
Jellybean on mako means that your phone is in lgnpst/qcpnst mode. Looks like something failed to start and made the bootloader trogger that mode
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Soo, any suggestions?
Str1ngcheese said:
Soo, any suggestions?
Click to expand...
Click to collapse
clean all the contacts with alcohol (not the normal one, the other that i dont remember the name).clean all the corrusion that you can find,let your phone charge for some hours and try again
opssemnik said:
clean all the contacts with alcohol (not the normal one, the other that i dont remember the name).clean all the corrusion that you can find,let your phone charge for some hours and try again
Click to expand...
Click to collapse
I've already done that.
Str1ngcheese said:
The next day I got some tools to open her up. There was pretty extensive corrosion to the motherboard, so using some alcohol I cleaned it all off, rinsed it, and let it dry. I also took apart everything else and cleaned any corrosion. The inside looks brand new.
Click to expand...
Click to collapse
Problem is the power button doesn't work, and the flashing fails. It looks like the flashing fails because the phone isn't unlocked. To unlock, I need the power button. Kinda stuck.
Str1ngcheese said:
I've already done that.
Problem is the power button doesn't work, and the flashing fails. It looks like the flashing fails because the phone isn't unlocked. To unlock, I need the power button. Kinda stuck.
Click to expand...
Click to collapse
the golden contacts on the power button / mobo could be damaged, do a little short till phone turns on
opssemnik said:
the golden contacts on the power button / mobo could be damaged, do a little short till phone turns on
Click to expand...
Click to collapse
How would I go about doing a short?
Str1ngcheese said:
How would I go about doing a short?
Click to expand...
Click to collapse
touch in both pins, something that passes electric current(like a yarn,wires, copper wire, something that passes electrical current).its basicly what the power button does.

[Q] Phone refuses to boot - sometimes.

I've run into a problem with my S4. I'm rooted, and running Hyperdrive 15.
My phone refuses to boot quite often. Sometimes it will boot up perfectly fine and run for a day - day and a half, or it'll lockup and then refuse to boot up again, OR it will just not boot at all. My power button seems to be unresponsive, and the only way that I can get some action out of the phone is by reseating the battery in the well.
What I think it is, could be 1 of a few things, or a combination of them - i'm not sure.
Scenario 1: While playing with the Hyperdrive tweaks, my phone was hung after running the Zipalign tool for over 20 minutes and I had to pull the battery.
Scenario 2: I'm deployed on a ship currently, and I have my phone in a high-salt enviornment and I'm afraid that there might be salt corrosion inside of the power switch or the USB connection - shorting it out. I took my phone apart tonight and cleaned both items with isopropyl alcohol ( the switch itself on the main board ) but that didn't seem to produce any new results.
Scenario 3: I was recently rooting a Kindle Fire HD 7" for a friend out here, and I was dumb and didn't realize that I was pushing boot loader files that were designed for the Kindle Fire and not for my Galaxy S4. I have since tried to enter recovery, but with little avail. Download mode is also out.
A description of what my phone does when I reseat the battery: My phone will vibrate, the Galaxy S4 logo will show for 1.5 to 2 seconds ( same for download mode ) and if I hold the appropriate button, ' Recovery Booting.... ' will display as well. At that point, my phone will shutoff and the power button will become unresponsive.
If anyone can give me a bit of guidance on how to proceed to repairing my phone, I'd be super grateful.
Scenario 3: I was recently rooting a Kindle Fire HD 7" for a friend out here, and I was dumb and didn't realize that I was pushing boot loader files that were designed for the Kindle Fire and not for my Galaxy S4. I have since tried to enter recovery, but with little avail. Download mode is also out.
This sounds like the most plausible reason.
You will need something like JTAG to really fix it.
Lennyz1988, thanks for the quick reply. Internet out here is slow at best, and sometimes unusable.
As far as your JTAG option, I believe that would work, except that I dont have access to that kind of hardware right now. Sending my phone out at this point entails a month of transit time on each side of the turnaround time required for someone to re-flash my phone, and I wholly believe that I can do this.
As an update to my phone, it will not charge the battery anymore. I'll use someone elses phone to charge my battery soon. If anyone can give me a direction to go as far as how to completely reflash my phone IF it turns on, i'd be grateful beyond belief. I dont want to believe that if I can get it to start up again, that it is a total brick and completely useless - if it turns on again, i need someway to push new boot loader files to it. Really hoping someone can help.
Thanks again in advance.

M30s does not boot - stuck at very first screen

Hi all,
my Gylaxy M30s rebooted itself yestarday, and now is stuck at the very first screen (the one showing "SAMSUNG Galaxy M30s" in the center and "Powered by android" at the bottom).
Vol down + power results in a reboot attempt (screen goes black, vibration), but the phone is stopping at the same screen again.
I am not able to turn the phone off.
Switching from Vol down to Vol up immediately when screen goes black does not enter recovery mode.
Vol down + power while charging sometimes leads to the charging symbol being shown on the screen, but without the percentage in the middle.
Charging over night did not help.
The phone cannot be connected to a Win PC.
Any suggestions what I can try?
Thanks,
Alchemist
Try volume down+volume up and while pressing those buttons, plug your phone into your computer. Tell me the results of that.
Nothing happening...
I mean trying those combinations immediately after using power+ volume down to reboot.
What did you do with your phone? Died suddenly when normally using?
Yes, phone died during normal usage.
Ah, I see - a screen comes up warning me that downloading a custom OS might harm the phone.
Also, the PC makes this "USB connected" sound when I then press Vol up, but I do not see a new drive connected, I think.
I am slightly optimistic now?
Press volume up.Then install Samsung usb drivers(search on Google)
Ugh, just wanted to do this, but now the phone is completely dead. No response to any button or charging. Will hang it on the charger for a few hours, but my optimism is gone...
OK, now it works again. I am in the screen with the colourfull stuff and the phone waits for some download.
Driver is installed on PC. Is there anything supposed to happen - the phone is still not accessible via PC, or is it?
Install Odin (search in Google 'odin samsung' and download)
Download stock firmware(android os) at www.samfw.com , after downloading you will see files like AP-M505xxxxxxx.tar.
Select, from the stock ROM AP-M305xxxxx.tar for AP in odin CSC-M305xxxxx.tar for CSC, and so forth then click start .
OK. All data will be lost, right? Is there some way to access the internal storage to rescue some files before flashing the new firmware?
Sorry to tell you that you cannot have data restored bad news for you sorry
Sorry. If you only see one file(make sure it is .tar or .tar.md5 file) after you extracted the .zip firmware, install it to the AP slot.
Any chance I could fix this issue with tools like dr.fone, UltFOne, ReiBoot?
I do not have any experiences with these - no idea if the just want to make money with desparate customers? ...
These could possibly brick your phones even more ( anyways flashing with Odin could also brick your phone). However, it in some cases can fix your device.
If you HAVE to have your data back and you don't mind paying, visit a service center and tell them: 'Hey my phone died and i HAVE to have the data back '.(I know, your warranty is expired probably, but they might still do the things for you with paying.)(if those stores closed during lockdown then I don't know any way to fix it.)
OK, another thing I have observed: The screen goes black after about 30 sec to 5 min when not charged - the shorter it was charged, the quicker the screen goes black. Buttons do nothing when screen is black. When reattached to charger, phone tries to boot and is then stuck at said screen - no button pressing needed for the phone to try to start. The longer the phone has been without charger, the longer it takes until the phone tries to boot.
Maybe it's just the battery that is dead - or would the phone with a dead battery boot normally when attached to charger?
If that is the case, open up your phone, put in a replacement battery, and try to boot up(yes, you need to. it will be a frustrating process.). Your phone could be having a faulty battery and nothing else, to cause this issue.
Im having the same problem mentioned above. The samsung service centre says to replace the motherboard which costs almost half the price of the actual phone..
Mystic_Jamdam said:
Im having the same problem mentioned above. The samsung service centre says to replace the motherboard which costs almost half the price of the actual phone..
Click to expand...
Click to collapse
Truth to be told: The guy in the repair shop opened the phone and wanted to change the battery - when he saw that water must have come into the phone, corroding the motherboard. So yeah, all data lost, but... no backup, no mercy. I now have set up a NAS for all computers and devices in our family... ;-)
If it really is a hardware problem then the quality must have been really bad.

Categories

Resources