Hello everyone, I am new to this forum and I apologize that I do not like English very well.
In these days I was trying something with my m8 to delete the partition cache in the recovery, because it was turned off at 50% of the battery, when I gave it to erase the cache suddenly began to vibrate by itself, rebooted and still followed Vibrating even when off vibrates.
Try to let the battery wear out and even so when I put it back with the charger it still had the same vibration when it started charging
And I do not know what to do and poor to restart it factory and re-erasing the cache of the partition and remains the same.
I'm already thinking about taking it to repair, but if anyone knows of any solution I would save having to take it and repair it
Thanks and sorry for my little english
Related
Hi All,
I've recently updated my Desire S to CM10.1 using a ROM off here --> [ROM][XXYYYZZ][UNOFFICIAL] CyanogenMod 10.1.
Everything has been running fine until I found the "Simulate Secondary Displays" button under Developer Options and decided it would be cool to see what it does...
The kicker:
a) Screen is now stuck exactly where it was on the Developer Options prior to selecting a screen resolution
b) Holding down power button for any period of time does nothing
c) Holding down Volume up + Volume down + Power for any period of time does nothing
d) The computer recognizes the phone as it makes it's lovely "new device found" sound, but stupidly, at some point I've disabled USB debugging so can't use adb to reboot as it returns authorisation error (The authorisation option doesn't pop-up on device screen as it's frozen).
I've read about this exact problem happening on other phones after selecting this option but they all seem to be able to use either b) or c) to get back to bootloader to reflash the ROM.
So, my question: if I let the battery die, what are my chances? I've read myself out of pulling the battery due to eMMC issues. Unfortunately the damn battery was mostly full so could take a long while to drain :S
Thanks!
So let the battery die (takes about a day), boot to recovery, wipe data (or figure out where this setting is stored and delete the relevant file), no problem. I don't see the issue here.
Pulling the battery out doesn't cause eMMC issues. The problem is caused if you pull the battery out and then put it straight back in. Remove the battery, leave it out for a minute or so and then put it back in and manually boot into recovery.
SimonTS said:
Pulling the battery ut doesn't cause eMMC issues. The problem is caused if you pull the battery out and then put it straight back in. Remove the battery, leave it out for a minute or so and then put it back in and manually boot into recovery.
Click to expand...
Click to collapse
Ah, that's interesting. Is there any reference material available to explain why that is the case? What is physically happening here?
So let the battery die (takes about a day), boot to recovery, wipe data (or figure out where this setting is stored and delete the relevant file), no problem. I don't see the issue here.
Click to expand...
Click to collapse
Apologies, it wasn't a particularly open question. It was more out of frustration that there is an option available that will always freeze the phone when it isn't supported on the device.
I let it die then used recovery to clear cache and davlik cache and booted fine until freezing on the "Optimising apps" screen. Let it die again, clear all data, clear cache, clear davlik cache, restore nand successfully.... Boots to HTC then black screen, no response to anything, same as when it first froze.
EDIT:
Repeat same process but clear cache and davlik cache after nand restore... black screen, no response. Cant even tell if it is actually doing anything. Charge light doesnt come on when plugged into pc whilst on black screen.
All I can think of now is flash the CM10.1 ROM again or maybe restoring the original nand from before CM10 but will have to be after work. Is this behavior indicative of a larger (potentially physical) problem?!
PoZER937 said:
Ah, that's interesting. Is there any reference material available to explain why that is the case? What is physically happening here?
Click to expand...
Click to collapse
From what I remember - there was some in-depth discussion on one of our threads about 18 months ago - the actual cause is that re-inserting the battery while the circuitry is discharging causes a spike which can be high enough to blow the eMMC.
Just to let you know, reflashed CM10.1 ROM and all is well in the world again Thanks guys for replying!
However, NAND restore did not work. As the NAND backup is supposed to be the be-all and end-all for phone recovery, should I be concerned this failed?
Hey,
yesterday i faced a problem i didn't knew of yet. As i mentioned sometimes, i came from an One M7 2 weeks ago as it didn't work the way it should - camera useless and awful battery life. I rooted the M7, had problems with it and so on - just how it is with a rooted phone + custom roms.
However, due to the DRM i didn't root my Z3 yet. Yesterday i took it out my pocket, thought it was a bit warm.. nevermind. It worked. 30 minutes later i pulled it out again, still warm, and screen wouldn't turn on. I reset it (power and vol+ for those who didn't know), tried to boot again.. well, it took several minutes and finally showed me the attached error message. The system performance was really, really low. Everything stuttered, i couldn't even enter my pin. A few forced reboots later i could finally enter my pin and get into my system only to notice that my data partition wasn't doing fine. I had to set language and so on in the initial setup process, apps kept force-closing in seconds. My own apps were still on the device, however when i tried to open WhatsApp there was no data there, i should have gone through the registration process. The phone froze after seconds each time. I tried to enter the fastboot menu (is it called that way?) while booting to just do a factory reset, didn't find the button combination. So finally, after i found home without navigation from no man's land (sure, why doesn't it happen at home anyway..), i managed to boot it, get through settings and initiate a factory reset. Of course, all the apps were deleted then and i could install all apps like LightFlow again. Had to re-enter all the settings i did in those kind of apps, it was kind of annoying.
So, my questions: Why the hell did this happen to my Z3? Not rooted, didn't even think of it. There wasn't a day on the One M7 without flashing anything and it never happened. It wouldn't have been as bad as it was on the Z3, as i HAD root, could have wiped data in TWRP in a matter of seconds and also had backups of my data, which i of course didn't have for my unrooted Z3.
Is it likely to happen again? Can any app do this on a non-rooted phone? I read a bit about the error, that it would be caused by some apps, but not in the extent as it happened on my phone. Most of the times it would just be an annoying error message.
I got a thing in always getting a defective unit, so i hope it isn't happening again on the Z3
Maybe the internal flash is corrupted/failing. I had a similar issue with my HTC One X I went to nap one day and half hour later it shut down, it restarted but boot looped. Eventually it showed no data partition as being mounted and completely died. They replaced the motherboard.
Better contact Sony, maybe you need a replacement.
Mh, actually that's the least thing i want to do.. I'd have to wait for at least 2 weeks to get it back and chances are that they won't do a thing or damage it (bad experiences with my former Razr i). It works just fine after the factory reset, no errors yet. If it should happen again, i'd of course send it in for repair but i think, until then i will use it normally, with more caution and backups of course.
Probably the cleanest solution HERE
I am very sure that there are all sorts of variations on this but I am sufficiently clueless to need a whole new level of hand-holding. I have a Lolipop level Nexus 5. Never did any modifications. On 7/10/15 I turned off the phone and turned it back on a few minutes later. Google was displayed and it started in with the 4 spinning colored balls..... It never gets past this (is this a bootloop?). I can let it stay in this pretty hypnotic display until the battery is dead... hours and hour. I tried the power down, power up and volume down to get to recover mode ... then the power and volume up to get to wipe and delete phone, it says it completes. Rebooting leaves me in the same condition. I have had the phone for just over a year and never had any issue. It is in prime condition, hardly a scratch.
I need someone to hold my hand and tell me everything is going to be alright. And please, what do I do? I see other posts about partition corruption ... how do I check if this is the issue? If it is the issue, I'll tell you right now, the solutions talked about are well beyond me.. flashing this and editing that and boot to adb and spinning in place, chanting naked during a full moon.
Any body feeling like helping a lost soul?? Beg beg.
Additional info and concern.... Just noticed that what I asked the phone to do is 'wipe date/factory reset' . It responds with :
-- Wiping data--
Formatting /data...
Formatting /cache...
Data wipe complete.
That is all it says, is that the correct sequence? It doesn't say anything about the cache and factory reset. Clueless. Thanks.
Duplicate.
http://forum.xda-developers.com/google-nexus-5/help/warning-newbie-student-driver-boot-t3155923
I am using a One Plus One and recently flashed Cyanogen 12.1.
Something very interesting is happening:
One morning my phone's screen wasn't displaying anything yet the phone was obviously working. I know this because the hard-button lights were on and I could feel the vibration when I held down the volume button to put it into vibrate mode. I even pressed the buttons to take a screenshot and when I looked in my gallery later, it was there.
So the phone was functioning in every way except for the display.
To fix it, I tried rebooting. It didn't work. So then I went into TWRP and wiped the dalvik cache. When the phone rebooted, the screen turned on and everything worked as normal.
So the next morning, the same thing happened. It happened at the same time of the day, right after I woke up. It had been charging all night. I woke up to the alarm on my phone and the screen was on so that I could turn the alarm off. Then I turned the screen off. The next time I tried to turn the phone on, same thing... screen not on... dalvik cache... yadeeyadayada...
So I thought maybe it was charging my phone all night that caused it. So the next night, I didn't charge my phone overnight, and in the morning, the same result.
So then it occurred to me that it might be my alarm app (I use 'Morning Routine'), but even when I didn't use the app, the same thing still happened.
I read up online and followed so advice (turning off proximity sensor, disabling the "prevent accidental wakeup function"). The advice did not work.
I am at a loss and can only figure that my phone's screen not turning on is caused by having it off for quite a while (6-8 hours). And the only solution for it is wiping the dalvik cache. This is really annoying to do every morning considering wiping the dalvik cache results in all of my apps needing to be "optimized for android."
Any help would be great. Thanks!
XDA Visitor said:
I am using a One Plus One and recently flashed Cyanogen 12.1.
Something very interesting is happening:
One morning my phone's screen wasn't displaying anything yet the phone was obviously working. I know this because the hard-button lights were on and I could feel the vibration when I held down the volume button to put it into vibrate mode. I even pressed the buttons to take a screenshot and when I looked in my gallery later, it was there.
So the phone was functioning in every way except for the display.
To fix it, I tried rebooting. It didn't work. So then I went into TWRP and wiped the dalvik cache. When the phone rebooted, the screen turned on and everything worked as normal.
So the next morning, the same thing happened. It happened at the same time of the day, right after I woke up. It had been charging all night. I woke up to the alarm on my phone and the screen was on so that I could turn the alarm off. Then I turned the screen off. The next time I tried to turn the phone on, same thing... screen not on... dalvik cache... yadeeyadayada...
So I thought maybe it was charging my phone all night that caused it. So the next night, I didn't charge my phone overnight, and in the morning, the same result.
So then it occurred to me that it might be my alarm app (I use 'Morning Routine'), but even when I didn't use the app, the same thing still happened.
I read up online and followed so advice (turning off proximity sensor, disabling the "prevent accidental wakeup function"). The advice did not work.
I am at a loss and can only figure that my phone's screen not turning on is caused by having it off for quite a while (6-8 hours). And the only solution for it is wiping the dalvik cache. This is really annoying to do every morning considering wiping the dalvik cache results in all of my apps needing to be "optimized for android."
Any help would be great. Thanks!
Click to expand...
Click to collapse
Hello, and welcome to XDA!
Dalvik cache trick throws a wrench into things, but I used to have a similar issue with an older device - the screen wouldn't come one, but the hard button backlight would - pulling the battery and rebooting relieved the problem for that fit. I ended up scaling down the max processor speed (as it was being overclocked on the current custom ROM) back to the stock value. The problem went away at the point. But that was for my device, and because yours requires a dalvik cache wipe, it is probably a different cause.
At any rate, please go ahead and create an XDA account. Then, venture over to post in the [Q&A] Help thread. Ask away! (Noob friendly) thread, (or at least) in the > OnePlus One > ONE Q&A, Help & Troubleshooting forum. Your device experts can be found there.
Hope this helps, and good luck!
Hello all,
Today my Verizon S6 (on CleanRom 1.5) started to keep rebooting. After it boots, I can use the phone for less than a minute until it reboots again.
Here's how it began to happen today, if it helps.
- I didn't plug my phone to a charger last night, and when I woke up the phone had like 0%~1% battery. The phone died soon after I picked up the phone.
- At the same time I turned on the phone, I connected it to the stock charger.
- I used it for like 1-2 minutes, and the phone seemed to get confused whether it should die again or not (at 0% battery level)
- Then the phone decided to die again, and keeps rebooting itself.
My guess is something related to booting, initializing, or battery might have gone wrong. Also the soft button lights get never turn on.
Now I cannot use the phone really, as it dies like 30 seconds after I swipe the lockscreen.
- I tried to boot into safe mode, it didn't help.
- I wiped cache partition, it didn't help either.
The last thing I would like to try is to odin CleanRom again (or factory reset) but I would like to try other things first because I cannot even backup the data as it keeps rebooting. Odin will wipe all the data in my phone.
Any help or suggestions guys?
mtshure said:
Hello all,
Today my Verizon S6 (on CleanRom 1.5) started to keep rebooting. After it boots, I can use the phone for less than a minute until it reboots again.
Here's how it began to happen today, if it helps.
- I didn't plug my phone to a charger last night, and when I woke up the phone had like 0%~1% battery. The phone died soon after I picked up the phone.
- At the same time I turned on the phone, I connected it to the stock charger.
- I used it for like 1-2 minutes, and the phone seemed to get confused whether it should die again or not (at 0% battery level)
- Then the phone decided to die again, and keeps rebooting itself.
My guess is something related to booting, initializing, or battery might have gone wrong. Also the soft button lights get never turn on.
Now I cannot use the phone really, as it dies like 30 seconds after I swipe the lockscreen.
- I tried to boot into safe mode, it didn't help.
- I wiped cache partition, it didn't help either.
The last thing I would like to try is to odin CleanRom again (or factory reset) but I would like to try other things first because I cannot even backup the data as it keeps rebooting. Odin will wipe all the data in my phone.
Any help or suggestions guys?
Click to expand...
Click to collapse
The OE2 tar file shouldn't wipe your phone as it is not a full wipe tar. I don't know if your phone would do it with it's reboot problem but a dirty flash of clean rom shouldn't wipe your phone either. However, a reboot during the middle of either of those would not be good. Flashfire does seem to be able to keep a phone from rebooting once it gets going or at least it has for me when I have been caught in a bad way before.
Problem Solved!!!
Thank you Tulsadiver for your suggestions. But is it okay to do odin without wiping anything?
I almost gave up after struggling several hours and thought about doing a factory reset, but the problem is solved now.
I found it weird that the soft key lights never turn on, so I thought that there might have been something wrong with the power management. So I turned the ultra power saving mode on (fortunately the phone didn't reboot before I did that), and it didn't reboot itself. I turned it back off then now the problem is gone!
I am happy with it now, and this might be one of the things to try if you experience a random reboot.