I have been having a reboot problem on my t989, it has been turning itself after ive turned it off when i plug it into a charger.I have been trying to figure this problem out for the last to months and a havent pin pointed the problem. i have checked if it was the sd card and it wasnt that , it happened two months ago when i was running darkside evolution v8 tdj.and have tried many roms to see if it was darkside and it was not. but whenever I switch to a stock firmware such as GB or stock tmobile ICS the problem stops. i am currently running clones and drones. please if anyone knows how to fix this problem or knows whats causing this to happen it will be very appreciated. thank you!
Sounds to me like you already know the cause. When you go back to stock, do you also replace the recovery? I seem to recall there was a similar glitch in the tmo g2 where it would boot to recovery if it was powered off when attached to the charger.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
tronmech said:
Sounds to me like you already know the cause. When you go back to stock, do you also replace the recovery? I seem to recall there was a similar glitch in the tmo g2 where it would boot to recovery if it was powered off when attached to the charger.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Its not booting into recovery its turning itself on. And yes when I switch to the stock firmware I flash it via Odin.
Well, I would say to try at least one other rom. The phone has to at least partially start up in order to control the charge cycle. (Chainfire has a charge animation replacement for one of the galaxy s phones on the play story, IIRC) So at least part of the kernel starts...
Sent from my Polaroid Tablet using Tapatalk 2
Okay I will try that. And I was watching it do the self turn on and on the top corner very shortly it says something about safe mode and I'm guessing that's directly corrilated with the problem but how is it related is my question
Related
I rooted my phone, unlocked it and put the HD rom on my phone. For some reason, when I turn my phone off and try to turn back on while its plugged in for some reason it just shows up with the battery icon and won't turn back on unless I take the battery out and back in.
Any ideas?
Sent from my Galaxy Nexus using Tapatalk
justinisloco said:
I rooted my phone, unlocked it and put the HD rom on my phone. For some reason, when I turn my phone off and try to turn back on while its plugged in for some reason it just shows up with the battery icon and won't turn back on unless I take the battery out and back in.
Any ideas?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
This is due to the recovery you are using, you should be able to reboot it through adb.
How do I go about that? Reboot the phone? I don't mind just taking the battery our and back in when I'm out, its just annoying. I was rebooting my phone in the car when this happenee
Sent from my Galaxy Nexus using Tapatalk
We already discussed the issue here:
http://forum.xda-developers.com/showthread.php?t=1400290
However it seems that the "bug" is related to custom firmwares. If you use a stock ROM (even if rooted) everything works like a charm.
This is very strange... maybe custom roms modifiy something in fastboot or anything else?
so umm .. is clockwork mod now bricking phones? I tried to use the app to backup the phone... and when it was shutting off i saw a couple of apps that stopped responding and then it shut off .. after several minutes of it not doing anything at all .. I took out the battery to manually get into recovery and back it up .. but .. it never came back on.
Damn thing is hard bricked. No recovery .. no vibrate, lights, and no boot of any sort when the power key is pressed and also no download/odin mode either .. completely dead.
i have/had the hard recovery on the phone and was the latest of recovery and rom manager too .. I was on the official ICS nightly ROM from a couple days ago.
sooo is this something that is happening a lot? I heard from someone that the phones have an unstable system partition that is causing it .. but only unstable after its rooted .. anyone hear anything about these things??
thanks!
Strapt said:
so umm .. is clockwork mod now bricking phones? I tried to use the app to backup the phone... and when it was shutting off i saw a couple of apps that stopped responding and then it shut off .. after several minutes of it not doing anything at all .. I took out the battery to manually get into recovery and back it up .. but .. it never came back on.
Damn thing is hard bricked. No recovery .. no vibrate, lights, and no boot of any sort when the power key is pressed and also no download/odin mode either .. completely dead.
i have/had the hard recovery on the phone and was the latest of recovery and rom manager too .. I was on the official ICS nightly ROM from a couple days ago.
sooo is this something that is happening a lot? I heard from someone that the phones have an unstable system partition that is causing it .. but only unstable after its rooted .. anyone hear anything about these things??
thanks!
Click to expand...
Click to collapse
What app are you referring to to back up your phone?
Sent from my SGH-T989 using Tapatalk 2
Same Here
My S2 got hard bricked too. I was on TDJ's DARKSIDE.UCLE2 with Blaze 4G LB7 radio. Thought about trying out CM9, which flashed just fine and was working well. But after i tried to back it up with CWM, it got stuck. Took the battery out and hasnt been on since. Wont power on, wont go into download. Ordered a USB Jig to try if it works. If not, gon send it on its way to samsung repair service.
snguyen0730 said:
What app are you referring to to back up your phone?
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
clockwork mod Rom Manager
BiGrOsOuTh said:
My S2 got hard bricked too. I was on TDJ's DARKSIDE.UCLE2 with Blaze 4G LB7 radio. Thought about trying out CM9, which flashed just fine and was working well. But after i tried to back it up with CWM, it got stuck. Took the battery out and hasnt been on since. Wont power on, wont go into download. Ordered a USB Jig to try if it works. If not, gon send it on its way to samsung repair service.
Click to expand...
Click to collapse
hmmm so its not just me then .. thats good to know .. and also sucks too .. so i wonder if that means that the Rom manager app is pretty useless now on the ICS .. or what the hell happened there.
Hold the power button for 10 seconds and see if something happens
Sent from my SGH-T989 using xda premium
JPOKeefe said:
Hold the power button for 10 seconds and see if something happens
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
oh I did .. and also times much longer with that ... same with trying to get it into download mode ... with and without a usb .. different cables ... different ports .. and so on .. not doing a thing at all
I already rooted the replacement .. but my deal though is that im concerned that it will happen again with Rom Manager .. seems like one other person has had this issue with it as well ... is Rom Manager something we should stay away from using now if this has been happening for others as well ..?
Okay first off yall deff need to stop taking battery out and also Do Not Take It Out While In Recovery hold power button until it reboots like dude said^ rom manager is not a reliable app anymore i wouldnt use it
Sent from my SAMSUNG-SGH-T989 using xda premium
casonswag said:
Okay first off yall deff need to stop taking battery out and also Do Not Take It Out While In Recovery hold power button until it reboots like dude said^ rom manager is not a reliable app anymore i wouldnt use it
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
This happened to me as well today... never had a problem with it before. Now all of a sudden today I used it to boot into recovery and phone shut off and never turned back on, can't get into download mode nothing... what a POS app, which should be removed or blocked access from all roms. How on earth would this app cause a hard brick... it makes no sense. What does it do when it sends a reboot to recover command.
This happened to me yesterday. I've been running CM9 for months with no problems. No problem using CWM on it to do backups. Yesterday I decided to use ROM Manager premium to back it up. I entered a file name, pressed the button, the screen went dark, and it's been dark since then. The battery was as 98%. It has not responded to any key combination since then.
I've never seen anything like it, and I've had 10 or so different devices that I've rooted with recoveries.
No replacement for titanium backup. Just for those reading this.
Hope you guys get your phones working tho! That sucks!!
Sent from my cell phone telephone....
OK, for some reason my a100 started acting funny today. I went to restart it and it wouldn't get past the Acer screen. So I figured I would do a hard reset. It still won't get past the screen. I am on ICS, was rooted and that's all..no different rom. I have been trying the paper clip method but doesn't get past the first Acer screen. A few weeks ago I had installed the ACER recovery from the market, but never really was able to figure it out. I seem to remember doing a backup with it but that's all.. I've tried the other reset method by holding the volume up and power, and toggling the screen lock switch. It just goes to the recovery but then has an error..recovery verified failed.. is there a way to hook this thing up to a PC like my old DROID x and sbf? See my pic of the recovery error..
Sent from my DROID4 using Tapatalk 2
droidxxxxx said:
OK, for some reason my a100 started acting funny today. I went to restart it and it wouldn't get past the Acer screen. So I figured I would do a hard reset. It still won't get past the screen. I am on ICS, was rooted and that's all..no different rom. I have been trying the paper clip method but doesn't get past the first Acer screen. A few weeks ago I had installed the ACER recovery from the market, but never really was able to figure it out. I seem to remember doing a backup with it but that's all.. I've tried the other reset method by holding the volume up and power, and toggling the screen lock switch. It just goes to the recovery but then has an error..recovery verified failed.. is there a way to hook this thing up to a PC like my old DROID x and sbf? See my pic of the recovery error..
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Means you run a custom recovery but have a locked boot loader. Not much you can do if you're no longer on the a200 boot loader to unlock again, you either need cwm/twrp or android running to flash anything at all.
Other option is a stock recovery but emmc corruption leading to the failure. Either way, not much to do besides contacting Acer.
Tapatalked from my Galaxy Nexus - Kuroikaze B4
Thanks for the quick reply..how do I know what bootloader I'm on?
Sent from my DROID4 using Tapatalk 2
droidxxxxx said:
Thanks for the quick reply..how do I know what bootloader I'm on?
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Upper left corner is a version number, also what color the acer logo is.
Tapatalked from my Galaxy Nexus - Kuroikaze B4
It's the first Acer logo..kinda white/silver looking...how did this happen all of a sudden? It always ran fine..I never did unlock the boot loader, just rooted it to run certain apps..but why won't the stock pin hole method work?
Sent from my DROID4 using Tapatalk 2
Here's a pic with the logo..
Sent from my DROID4 using Tapatalk 2
Well you mentioned a recovery backup which means a custom recovery which means unlocked boot loader. Based on that, the a100 boot loader was restored somehow and locked you out of recovery.
Then you say you never unlocked it, which then means emmc corruption of either the recovery partition or even a portion of the boot loader.
Either way the outcome is the same, a trip to acer.
Custom ROM or not, emmc failure will happen to all a100s eventually, when depends on usage. Acer chose to use a defective problematic emmc on the a100 which is known to brick.
The only potential way around it is to use Linux society / godmachine kernels and his twrp recovery. It may or may not prevent it, but its better then nothing. As its timing is almost random (to us) its nearly impossible to tell if its effective or not.
Tapatalked from my Galaxy Nexus - Kuroikaze B4
hey pio, does increased flashing of custom zips, whether rom, kernel, mod etc. increase the risk of failure? i would think flashing read only memory repeatedly would result in premature wear lending to faster ultimate failure.
your opinion?
Sent via G2x on CM7 b135.1 w/faux 52 kernel
Well.. maybe it did not let me do a recovery... I seem to remember trying anyway. I definitely remember not getting very far with the recovery app itself..and I never unlocked the boot loader because I liked the stock from.. So even if I would not of rooted it it would still do this? I will look in the box for a number for Acer..I lost my receipt though..will they still help me? The Linux thing you mentioned..is that preventative or something I could do now?
Sent from my DROID4 using Tapatalk 2
droidxxxxx said:
Well.. maybe it did not let me do a recovery... I seem to remember trying anyway. I definitely remember not getting very far with the recovery app itself..and I never unlocked the boot loader because I liked the stock from.. So even if I would not of rooted it it would still do this? I will look in the box for a number for Acer..I lost my receipt though..will they still help me? The Linux thing you mentioned..is that preventative or something I could do now?
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Nothing can repair a tab with emmc failure. The kernel is preventative.
Log onto Acer.com and go through their chat with a rep process. There they'll tell you if its covered or not and what to do about sending it in for repair if that's what is decided upon.
That recovery app wouldn't work without being unlocked, so if you never did that then you never had a custom recovery and that leaves hardware failure if some sort.
Tapatalked from my Galaxy Nexus - Kuroikaze B4
---------- Post added at 05:23 PM ---------- Previous post was at 05:17 PM ----------
justjackyl said:
hey pio, does increased flashing of custom zips, whether rom, kernel, mod etc. increase the risk of failure? i would think flashing read only memory repeatedly would result in premature wear lending to faster ultimate failure.
your opinion?
Sent via G2x on CM7 b135.1 w/faux 52 kernel
Click to expand...
Click to collapse
Yes and no. What we came up with is wear leveling is causing it. The emmc controller accepts a command from the kernel it can't actually do, then begins to blank the emmc, usually killing the gpt. Its been covered elsewhere, so I won't get to crazy on details, but it will happen stock or not. /cache usually triggers it as its most written to, however anything can trigger it.
Flashing and wiping cache can accelerate this issue. My tab had it after 3 months, usually it seems to be 6+ months of normal use to see it. Completely stock ICS never flashed seems to go a year or so, maybe.
Mine had failure pretty quick as its a dev device, in particular developing the black hole nullifier which writes zeroes over each partition. Flashing ROMs and wiping twice or even up to 8 times in a day accelerates the issue also.
Tapatalked from my Galaxy Nexus - Kuroikaze B4
What should I say is the problem? That all sounds pretty complex..lol
Sent from my DROID4 using Tapatalk 2
Well..that was pretty painless..gonna mail that sucker tomorrow.. I had 113 days left..thank bejeezus.. lol
Sent from my DROID4 using Tapatalk 2
droidxxxxx said:
Well..that was pretty painless..gonna mail that sucker tomorrow.. I had 113 days left..thank bejeezus.. lol
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
I was gonna say tell them its not booting lol glad it worked out.
Tapatalked from my Galaxy Nexus - Kuroikaze B4
I gave a brief description.. and chose "system hangup" as the issue.. Acer in Texas will be fixing it hopefully.
Sent from my DROID4 using Tapatalk 2
After they fix it..hopefully it won't do it again..I sent it off today..
Sent from my DROID4 using Tapatalk 2
I had the same issue. I tried installing a stock rom from ext SD, and several other recovery methods found in various threads, but when I started the tab up, whilst holding volume button farthest from the rotation lock and toggling the rotation lock, it actually reset everything back to the day I brought it home. It booted into the original HC, and I was able to get the ICS OTA update. Seems to be none the worse for wear at this point.
Sent from my A100 using xda app-developers app
Ok..got my tablet back yesterday from Acer..they fixed it very quickly..props to their warranty department. Now..I assume I got a new main board replacement..which is great..but now..I am on the original honeycomb os..I have tried the update wanting to return to ICS..but it says none is available. Also the market is not upgrading to the Play store..and it forces you into landscape, even if the lock is disegaged. Also, the market is not finding all my apps..and even not recognizong ones I've paid for..and worse of all..is the honecomb camera..it sucks..no panorama..which I was using daily at work. Can I get ICS back? Anybody else having this issue with a repaired a100?
Sent from my A100 using xda app-developers app
droidxxxxx said:
Ok..got my tablet back yesterday from Acer..they fixed it very quickly..props to their warranty department. Now..I assume I got a new main board replacement..which is great..but now..I am on the original honeycomb os..I have tried the update wanting to return to ICS..but it says none is available. Also the market is not upgrading to the Play store..and it forces you into landscape, even if the lock is disegaged. Also, the market is not finding all my apps..and even not recognizong ones I've paid for..and worse of all..is the honecomb camera..it sucks..no panorama..which I was using daily at work. Can I get ICS back? Anybody else having this issue with a repaired a100?
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
Slap this stock ICS ROM on your microsd card, named update.zip. http://forum.xda-developers.com/showthread.php?t=1611696
Power off, then press and hold the power and the volume rocker closest to the corner simultaneously for about 5 seconds. The tab will vibrate and update to ICS. Let it sit until it is done. Then there should be a few updates if you check for updates.
Ok..will try that later tonight..it doesn't need to be unlocked or rooted for this?
Sent from my SCH-I535 using Tapatalk 2
droidxxxxx said:
Ok..will try that later tonight..it doesn't need to be unlocked or rooted for this?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
It only needs unlocked for custom or modded ROMs, thats a stock leak (if its what I'm thinking) and passes the bootloader locks and recovery fine.
So, lately my phone has been acting kinda weird.. Basically, it'll shut off on it's own, no matter what my battery level or if I'm on the charger, its pretty random. When I go to turn it on, it shows me the samsung logo and shuts off after about 3 seconds of the galaxy s3 logo. It does the same in download mode and recovery. The phone will stay off and do that for an hour or more, and then itll turn on and be all dandy again for hours or at least another day. I'm going to take off all my pictures on the sdcard and odin back to stock as soon as possible for warranty, but does this sound like a hardware failure or software? I read about the s3 sudden death syndrome, but this one isnt permanent. Any ideas?
I agree with your assessments.
I'd wonder about overheating or a bad battery.
Sent from my SGH-T999 using xda app-developers app
what's your setup as of right now?
Beware if it shuts down when your flashing back to stock in the middle of the process it may never turn back on.
Sent From My Galaxy S3 Boricua 100%
It might be the kernel that came with the ROM you installed. I used to have problem with ktoon kernel.
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
mejorguille said:
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
Click to expand...
Click to collapse
If you have an app that controls kernel voltage that is still set up for set on boot and the voltage is too low when it boots or is granted root it'll kill it in this manner. Otherwise your phone is [email protected]#
Sent from my SGH-T999 infected with AnthraX using Tapatalk 2
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
I used the phone for work, not play, no overclocking was done neither was any undervolting. I ran stock kernel settings.
Aerowinder said:
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
Click to expand...
Click to collapse
I remember a time when XDA had helpful answers and users weren't reduced to insults. I've been around a couple years, hacked more phones than I can count and flashed hundreds of roms in my days, back when everything was still done in adb and terminal emulator. It's no wonder a lot of decent user has started moving over to rootzwiki
so here's what happened.....
i rooted my note 2 a few days after i purchased it. everything was fine. the only reason i was tryng to get back to unrooted stock was because i was having issues with sms and needed to take the phone to sprint to have them look at it.
well i found and followed the instructions here- http://forum.xda-developers.com/showthread.php?t=2086769
everything was fine til i got home from an event in my city and realized that my phone wasnt charging no matter how long i left it on the charger.
so i downloaded odin3 v3.04 and tried to use lj1 firmware package to put the phone in the state it was when i pulled it out of the box.
well, i tried 3 times and it failed i believe at writing the system.
my battery is at 15% and have no way of charging it. oh, and when i try to turn the device on, the only thing that comes up on the screen is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." and i cant even get kies to install on my pc, dont know why it just keeps reinstalling the hotfix and never gets past that point.
what can i do to save my phone?
my sis inlaw has the same device i do and i might be able to use her battery if i have to.
EDIT: I cant believe it but i fixed my phone!!!!!!!!!!!
After alot of rewording my search criteria with the search function on this forum, i finally found this- http://forum.xda-developers.com/showthread.php?t=2241136
This was my salvation! and i did it with only 15% battery to work with.
Its because it wasn't bricked. If it had been actually bricked you wouldn't be able to do anything with it except hold papers in place
Sent from my SPH-L900 using Tapatalk 2
Sorry, soft bricked is what I was gettin at. Im from redneck central and we use one word for just about everything. My bad.
Sent from my SPH-L900 using xda premium
Lol. No worries.:beer:
Sent from my SPH-L900 using Tapatalk 2