Hi, I recently changed the bootloader to lollipop using odin and loaded Civato's 5.02 rom on my pm-900 (previously running hyperdrive rom 2.1). It was working great for about a month and suddenly, I cannot charge my tablet properly. The charging is unbelievably slow (8 hours charging only increasing battery from 50 to 74%). I tried booting into recovery, wiping cache/davalcik and rebooting. Have tried different cables, outlet, adapters; in the past whenever I had charging issues, one of these worked, but currently, nothing seems to help at all. My question (since my battery is running perilously low) is can I restore a full nandroid backup from my Hyperdrive rom days with the kitkat bootloader (has bootloader partition as part of backup) or do I first need to flash the older bootloader in odin, then restore nandroid? At this point, I just want to try to get my tablet charging again before it runs out of juice and I can't do anything. Thanks in advance for any help. p.s. I have considered that the cable connector in the tablet itself is becoming faulty and I have read about some people re-soldering connections or unplugging and then replugging in the battery after opening the tablet. I've never opened the tablet and have been looking for youtube video that might show how it's done with relation to charging issues, haven't been able to find one. If anyone can point me to one, I'd be very grateful. Thank you!
Related
Hello everyone,
I searched the forums for awhile but could not find a satifying answer for my question. So i am hoping you guys will have an answer for me.
First of all i would like to point out that i am not looking for an answer for how to unbrick the phone. There are several guides and hopefully when i get home i will be able to fix the problem. *Fingers crossed*
I did not have my Galaxy S for long. After getting it and installing KIES and updating my firmware the battery life what terrible so I rooted the phone and then installed Gingerbread 2.3.6 JVU. it worked like a charm.
Yesterday when I was playing with the CWM application, I decided that i was going to back up the phone and backed it up using the application. This morning one of my programs was acting weird and I decided to restore the backup I have done yesterday.
Upon going into applications and CWM, I chose the restore option and started the process. Everything was going smoothly, the phone was plugged in to the charger as well.
When the phone rebooted after the initial process I am stuck at logo screen. i can go into download mode (That is why I am hoping that I will be able to unbrick it) however that is as far as the phone goes. When I try to go into CWM Recovery mode, I am once again welcomed by the phone getting stuck at logo screen.
Does anyone have any idea as to why this might have happened? To avoid future problems is there any extra steps I should have taken before using the CWM restore function?
Thanks for the help.
m_hawkmoon said:
Hello everyone,
I searched the forums for awhile but could not find a satifying answer for my question. So i am hoping you guys will have an answer for me.
First of all i would like to point out that i am not looking for an answer for how to unbrick the phone. There are several guides and hopefully when i get home i will be able to fix the problem. *Fingers crossed*
I did not have my Galaxy S for long. After getting it and installing KIES and updating my firmware the battery life what terrible so I rooted the phone and then installed Gingerbread 2.3.6 JVU. it worked like a charm.
Yesterday when I was playing with the CWM application, I decided that i was going to back up the phone and backed it up using the application. This morning one of my programs was acting weird and I decided to restore the backup I have done yesterday.
Upon going into applications and CWM, I chose the restore option and started the process. Everything was going smoothly, the phone was plugged in to the charger as well.
When the phone rebooted after the initial process I am stuck at logo screen. i can go into download mode (That is why I am hoping that I will be able to unbrick it) however that is as far as the phone goes. When I try to go into CWM Recovery mode, I am once again welcomed by the phone getting stuck at logo screen.
Does anyone have any idea as to why this might have happened? To avoid future problems is there any extra steps I should have taken before using the CWM restore function?
Thanks for the help.
Click to expand...
Click to collapse
Maybe your backup was corrupted somehow. You could have tried wiping the dalvik cache after restoring your backup (before rebooting), but its too late now. Since you can get into download mode, you can easily fix the problem (your device is just soft bricked - nothing to worry too much about).
Theonew said:
Maybe your backup was corrupted somehow. You could have tried wiping the dalvik cache after restoring your backup (before rebooting), but its too late now. Since you can get into download mode, you can easily fix the problem (your device is just soft bricked - nothing to worry too much about).
Click to expand...
Click to collapse
The phone rebooted automatically. Did not give me the chance to do anything beforehand.
As you said the phone was soft bricked so when i got home that day i just fixed it. No problem. However I am really really into getting to find out how a 1 day old back up can get corrupted.
OK so I bought a phone off craigslist as a replacement for my gf, really unstable running the stock 2.3 firmware, did a factory reset, seemed to be stable afterwards but the battery meter constantly reads 100%, so I flashed it to 2.3 stock with ODIN, problem was still present, put clockwork mod on it, wiped battery stats, still was there. Installed a PAC MAN rom, still there, flashed back to stock 4.1 firmware, problem still present, and finally put the dirty unicorn ROM on it and its still stuck.
So I found a post saying to charge up all the way, delete the batterystats.bin file reboot in recovery wipe cache partition and davlik cache, power off and keep plugged in, disconnect charger reconnect and leave powered off but charging, then turn on, did that and leaving on till it powers itself off and its still stuck at 100%
Oddly when the phone is turned off upon first showing it does display the correct battery for about 15 seconds and then reverts to 100%
What is going on here, how do I fix this
rodimus_prime said:
OK so I bought a phone off craigslist as a replacement for my gf, really unstable running the stock 2.3 firmware, did a factory reset, seemed to be stable afterwards but the battery meter constantly reads 100%, so I flashed it to 2.3 stock with ODIN, problem was still present, put clockwork mod on it, wiped battery stats, still was there. Installed a PAC MAN rom, still there, flashed back to stock 4.1 firmware, problem still present, and finally put the dirty unicorn ROM on it and its still stuck.
So I found a post saying to charge up all the way, delete the batterystats.bin file reboot in recovery wipe cache partition and davlik cache, power off and keep plugged in, disconnect charger reconnect and leave powered off but charging, then turn on, did that and leaving on till it powers itself off and its still stuck at 100%
Oddly when the phone is turned off upon first showing it does display the correct battery for about 15 seconds and then reverts to 100%
What is going on here, how do I fix this
Click to expand...
Click to collapse
u would need to try an oem battery and cable to see if it corrects the issue, if not then its probably the charging port, reading this post might help http://forum.xda-developers.com/showthread.php?t=2493751
An OEM battery really isnt a possiblity as no places sell it locally (sure I can order it online but this is a time sensitive project) and I really dont want to dump any further money into this project if its not going to work
I bought my S3 I9300 (INTL) when it first came out. Since then, it has been working perfectly fine. I rooted it a year ago and installed cm10 at that time as well. Afterwards, I had also successfully switched back to stock rom via my nandbackup.
A week ago, I did a nand backup via CWM and then decided to install CM 13 nightly. After that I had no serious issues (just small issues such as data connection not automatically turning on. Had to do it from settings) so I didn't update either. Two days ago just when I needed my phone the most, it turns off suddenly. Every time I try to turn it on, it can't go past the CM boot logo. I then put my phone on charge. I turned it on and it worked while it was charging. At 88% i take off the plug and the same thing happens again (bootloop). I then plug the charger back on and restart after going to download mode (to stop the bootloop). It then shows a charge of 5 percent. I charge again then I decided to quickly to a factory reset as I was in a hurry. Then while I was in my car, I let it restore the backup from my sdcard1. However, I noticed that it said "failed to restore /data". I did another reset and cleared cache etc but everytime it would say either failed to restore /data or /system. Doing an advanced restore didn't work either. Then factory reset again and downloaded CM 11 more stable version. I moved it from my tab (which I downloaded it with) to my phone via sd card. However, it fails to install. At 20% it restarts my phone back in to bootloop but this time a samsung bootloop as I already did a reset. Now my phone is unusable and bootloops every time I try to turn it on. Further note, the charging icon shows the cm13 charging icon.
Right now: Downloading stock rom from a different country because can't find mine.
Hi,
Try posting your question here:
Galaxy S III Q&A, Help & Troubleshooting
The experts there may be able to help.
Good luck!
When I got my replacement tablet for the recall, I followed the instructions to kill the kill switch on my old tablet (a 16gb Wifi only version). I deleted the TegraOTA folder, and used the zip file as well. I then installed BlissPop and have left it that way since.
A few days ago, I decided to switch from the now-defunct BlissPop over to LineageOS. For some reason, I couldn't get the tablet to boot into recovery (I installed the TWRP app, wouldn't boot into TWRP; I flashed TWRP using fastboot, wouldn't boot into TWRP; I flashed Nvidia's stock recovery, still wouldn't boot into recovery).
So I decided to flash stock, but new everything (I think the 5.2 or 5.3 version). Booted into OS setup (without connecting to network) so I could enable debugging/connect with ADB. This worked, so I rebooted into bootloader and finally got into TWRP. But, because of shared storage, I couldn't get into system folder to see if TegraOTA was back. So I decided to go back to original stock so I could access internal storage. Performed a factory reset, flashed the very original stock system/recovery/boot from these forums.
Restarted tablet and... nothing. Black screen. When its plugged in, the light shows it has charging, but no amount of time or effort pressing the power button will get it to do anything.
Did I brick it somehow? I've flashed various upgrades, OTAs, custom ROMs on both Shield Tablets I've had and am 99.99% sure that I didn't do anything wrong this time. Did I unknowingly flash something that would allow the kill switch to be thrown even if the tablet was never connected to my network? Is there any way to test? Basically I want to be certain its 100% done for before I toss it and buy a new tablet (I sold my replacement earlier this week, which is why I decided to upgrade the old one in the first place). Thanks in advance for any help!
If you installed latest stock and system detected tablet with bad battery it probably killed itself even if you did not connected it to internet
Hi All,
Would very much appreciate some help.
My phone is stuck in a reboot loop, after having frozen last night randomly (no changes were made to the phone). I have tried force restarting and wiping the cache partition via Android system recovery, as advised, although it got stuck at ‘formatting /cache’ for hours overnight. Other notable copy displayed on this screen was: ‘No support single sku supported api 3 dm-verity error’, although it gave no other details of the error.
I can try 'wipe data/factory reset', although would prefer to try other means first. Would it help to show you the recovery logs?
Also note that I'm unable to flash custom stock rom as the cable port in the phone is damaged (due to prior water damage a year ago), and I’ve been using a charging pad since.
What are my options here? I assume my data is beyond recovery, but would like to be convinced otherwise!
Many thanks in advance.
Ed
"Cable port in the phone is damaged (due to prior water damage a year ago)"
Hi , when you say "cable port" you mean charging port , and it has corrosion on pins so ?
If is that , I suggest you to clean charging port with 100% alkohol , needle for clothing and cosmetic Ear Picks Tipped, old toothbrush (clean!)...
Be be carefully to don't push so hard 5 pins from micro usb port ...
Picture from pins to clean ( yellow )
https://i1.wp.com/lemmymorgan.com/w...your-micro-USB-cable.jpg?resize=768,310&ssl=1
Before that make sure your device is completely OFF first !!!
Good Luck
Hi Teddy,
Thanks for the reply and help. Yes, I meant the charging port. Cleaning it may be an option, although I'd only attempt this if flash custom stock rom is the only way forward, as I'm quite happy using the induction charging pad for now.
I've given a wipe cache partition another go but it just gets stuck at Formatting /cache, for hours. If I share the recovery log, would this help ascertain the problem?
Any other help is appreciated!
If you need to backup your data you can try to flash just twrp recovery and to backup on your PC .
Example:
https://www.youtube.com/watch?v=clBVD6QOpRQ
But you must to clean your charging port or replace new one , who knows , maybe charging port cause that problem with bootloop ...
So you have two options:
1. Trying to fix pin connection with cleaning ....
2. Replace new charging port dock (buy exactly for your model !)
example :
https://www.ebay.com/itm/USB-Chargi...=item28071f2651:g:hcUAAOSwIFtaHSWG:rk:12:pf:0
Another option is not avaible .....
First thing first looks like some one tried to trick you.The cache partition is one of the partitions to be loaded while booting and one of the apps had some thing looped or malicious that causes the phone to recheck it again and again and again...I've made myself this kinda mess every 2nd day or so.The best way is to change the recovery to custom by flashing it and booting into it.The Android stock recovery checks signatures verify **** due to which it's just use less.You need to get the charging pin replaced though I would recommend you to replace the whole board due to...You know repairing a thing is always bad.After which flash TWRP and format dalvik.Remember the recovery verifies things before deleting so if something is broken it won't delete it but verify it again and again.
Sent from my Pixel 3 XL using Tapatalk