no power button problem
without any reason the phone rebbot itself and stuck in boot loop animation....stock MMB29V Marshmallow , no root, only unlocked
tried:
-wipe cache and data
-reinstalling all singles images files
-reinstalling with flash all bat and finally it works...
what's the problem???
and now? there is something to check? have to change the phone???
tnx
Manually flash each partition again, including userdata.img partition. After flashing the last partition, boot directly to recovery using the power and volume keys (don't reboot the phone at all after flashing the last partition), perform a factory wipe, and reboot.
Ok but i need ti know if is possible to check the health device status
What do you mean by health? You mean each component?
I mean if is possible that something hardware is defective or going to be defective.
can I run some tests?
I know of no tests that are available to the public.
Ok
audit13 said:
Manually flash each partition again, including userdata.img partition. After flashing the last partition, boot directly to recovery using the power and volume keys (don't reboot the phone at all after flashing the last partition), perform a factory wipe, and reboot.
Click to expand...
Click to collapse
I have a similar problem with my N5, it was originally a power-button issue, and after some "whacking" the phone no longer "repeatedly reset" but now it just sits on the "Google" boot screen forever. Probably something got messed up during all the unintended reboots. I already went into recovery and did a factory reset, no luck. Tried flashing to older ROMs, no luck. Started hitting up forums, saw this post, tried your suggestion (flash each partition manually, did a "fastboot reboot-bootloader", enter recovery, wipe, and reboot), and still no luck.
I can get into fastboot/recovery, and even tried loading custom ROMs (CM13 to be exact). No matter what I tried, the phone will power-up, and stuck at the "Google" screen. Note that I've always waited at least an hour after flashing each version before I reboot from the "Google" screen.
I've read somewhere there is a "persist(?)" partition which will throw some error if corrupted, but it will require USB debugging enabled to fix. Unfortunately, I can't boot into any ROM to enable USB debugging...
Am I SOL or is there anything else I can try?
Thanks,
Wallace
WallaceLau said:
I have a similar problem with my N5, it was originally a power-button issue, and after some "whacking" the phone no longer "repeatedly reset" but now it just sits on the "Google" boot screen forever. Probably something got messed up during all the unintended reboots. I already went into recovery and did a factory reset, no luck. Tried flashing to older ROMs, no luck. Started hitting up forums, saw this post, tried your suggestion (flash each partition manually, did a "fastboot reboot-bootloader", enter recovery, wipe, and reboot), and still no luck.
I can get into fastboot/recovery, and even tried loading custom ROMs (CM13 to be exact). No matter what I tried, the phone will power-up, and stuck at the "Google" screen. Note that I've always waited at least an hour after flashing each version before I reboot from the "Google" screen.
I've read somewhere there is a "persist(?)" partition which will throw some error if corrupted, but it will require USB debugging enabled to fix. Unfortunately, I can't boot into any ROM to enable USB debugging...
Am I SOL or is there anything else I can try?
Thanks,
Wallace
Click to expand...
Click to collapse
Are you getting any errors when performing a factory wipe? Does the factory wipe happen very quickly? You flashed the userdata.img partition too?
audit13 said:
Are you getting any errors when performing a factory wipe? Does the factory wipe happen very quickly? You flashed the userdata.img partition too?
Click to expand...
Click to collapse
First time I did a wipe it took over an hour, then the phone rebooted to the dead android screen. So I tried to wipe again, and it seems like all subsequent wipe took anywhere between 3-5 minutes. No error on each wipe (can't say on the first one, since by the time I got back to the phone it has already rebooted). And yes, I did flashed everything - boot, cache, recovery, system, userdata, bootloader, radio - not exactly in that sequence, but all of those partitions are flashed with the image that comes with the Google download package. Then factory reset and reboot.
Thanks,
Wallace
Maybe try erasing cache and data using fastboot commands? If this doesn't work, it's possible that there is a hardware problem with the phone's internal memory.
audit13 said:
Maybe try erasing cache and data using fastboot commands? If this doesn't work, it's possible that there is a hardware problem with the phone's internal memory.
Click to expand...
Click to collapse
Did a "fastboot format cache" and "fastboot format userdata", no error. Still won't boot... are those the commands you are referring to?
Yup, or fastboot erase cache or fastboot erase data.
Sounds like the emmc may be messed up.
audit13 said:
Yup, or fastboot erase cache or fastboot erase data.
Sounds like the emmc may be messed up.
Click to expand...
Click to collapse
Tried all those, and yes same result... also, I flashed a different recovery (TWRP) and thereafter I can't even flash new ROMs anymore. ADB Sideload error our (forgot to write down the error message), and if I copy the file to internal storage and flash from there, TWRP will get stuck for hours.
How common are eMMC corruptions?
W.
The emmc problem is not that common, but it does happen. I'm not sure if it is partition or software corruption or a physical defect.
Other xda members have encountered emmc problems too that could only be fixed through a motherboard swap.
I am running into a situation emmc. the problem is I tried below action so far
1. Attempted to flash recovery partition which failed immediately after first reboot . it never got flashed correctly
2. Attempted to format all the partitions but I could format boot partition I could format no other partition it clearly says that can't mount
3. Then I tried to boot using fastboot command into recovery partition my command is
Fastboot boot recovery.img
I tried cwm I tried TWRP . only 2.6 dot x x worked in twrp. Cwm was not so helpful because it does not give me many features likewise TWRP
Once I boot in the recovery it asks for password if I click cancel it shows me all the interfaces but nothing works I don't have any local storage available it clearly fails to read it and everything shows is encrypted I don't know not sure what is going on there
When I attempt to format I get a error message as no partition available for this operation. No file system available
About phone but I think I am still searching for options but so far I could see that this is e MMC issue and there is no partitions available on this memory I am not able to format this internal memory I am new to the Linux environment and not sure what to do to format this internal emmc...
Can someone suggest any options to format and Re partition the emmc?
Sent from my AO5510 using Tapatalk
Sarvesh.huddedar said:
I am running into a situation emmc. the problem is I tried below action so far
1. Attempted to flash recovery partition which failed immediately after first reboot . it never got flashed correctly
2. Attempted to format all the partitions but I could format boot partition I could format no other partition it clearly says that can't mount
3. Then I tried to boot using fastboot command into recovery partition my command is
Fastboot boot recovery.img
I tried cwm I tried TWRP . only 2.6 dot x x worked in twrp. Cwm was not so helpful because it does not give me many features likewise TWRP
Once I boot in the recovery it asks for password if I click cancel it shows me all the interfaces but nothing works I don't have any local storage available it clearly fails to read it and everything shows is encrypted I don't know not sure what is going on there
When I attempt to format I get a error message as no partition available for this operation. No file system available
About phone but I think I am still searching for options but so far I could see that this is e MMC issue and there is no partitions available on this memory I am not able to format this internal memory I am new to the Linux environment and not sure what to do to format this internal emmc...
Can someone suggest any options to format and Re partition the emmc?
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
The password thing means your encrypted...Unencrypt and you can see all your storage..
Sent from my Nexus 6P using Tapatalk
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
My friend as a n5 that kerps bootlooping too..No roit but unlocked..Never rooted and has no clue how to root or mod a phone...It keeps bootlooping foe no resean 100% stock..It will only stop when i get it to go into bootloader mode and that takes a while...
Sent from my Nexus 6P using Tapatalk
The constant boot looping could be a power button problem?
kenbrownstone said:
The password thing means your encrypted...Unencrypt and you can see all your storage..
Sent from my Nexus 6P using Tapatalk
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
My friend as a n5 that kerps bootlooping too..No roit but unlocked..Never rooted and has no clue how to root or mod a phone...It keeps bootlooping foe no resean 100% stock..It will only stop when i get it to go into bootloader mode and that takes a while...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I dont think anyone has encrypted the phone ever.
Sent from my AO5510 using Tapatalk
Sarvesh.huddedar said:
I dont think anyone has encrypted the phone ever.
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
Maybe im mistaken but evertime i had to put in a password in ttwrp i had gotten encrypted...you get it fixed? My friends started bootlooping for no reason and wouldnt stop til the battery was dead.. Never seen a stock phone do that..
Sent from my Nexus 6P using Tapatalk
---------- Post added at 10:00 PM ---------- Previous post was at 09:59 PM ----------
Reasearch it.... It totally sounds like what happened to me...
Sent from my Nexus 6P using Tapatalk
Related
Hi,
My Nexus 5 has been working pretty well until now. Earlier today I decided to disable lightflow and try the Xposed LED Control module. I installed and rebooted and it seemed to be fine. But then while using the phone shortly after unlocking it it completely froze then rebooted itself. Since then it's been stuck in a bootloop where it gets as far as the boot animation but then freezes for a few seconds and returns to the Google screen again.
I tried power off and back on and tried loading into recovery to see if wiping dalvik + cache might get me as far a boot but when it loads TWRP it asks me for a password (I've never set one nor enabled encryption of any kind) so my only option is to cancel but then it can't mount the partitions to wipe the cache.
I suspect it's the Xposed module I installed that caused this but I can't be sure it's not just coincidental. I haven't done anything else unusual on the phone today.
Is there anything I can do to fix this that won't require a complete factory reset? Is there any way I can at least backup or keep my data? Unfortunately I'm not at a computer where I can run or install ADB but if that would let me save my current setup or data I can do so at home tonight.
Thanks!
Try flash stock cache.img from fastboot
I don't see this being xposed related but who knows?!
Sent from my Nexus 5 using Tapatalk
I know clearing the cache asks for a password, but try to see if you can flash something. The something is the Xposed disabler zip file in the root of your scard.
Hi,
From the Xposed Framework thread:
In case you get into a boot loop:
You can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process
Click to expand...
Click to collapse
Maybe this..., the "Xposed-Disabler-Recovery.zip" should be at the root of /sdcard (at least for me it was the case).
You could try re-flashing recovery in fastboot mode to see if it fixes the password issue or also I believe philz touch recovery can read twrp backups if you want to switch to a different recovery.
The original bootloop seems like /data corruption to me (freeze + fsync perhaps), then the twrp password further evidences that but.... hmmmm
Sent from my Nexus 5 using Tapatalk
viking37 said:
Hi,
From the Xposed Framework thread:
Maybe this..., the "Xposed-Disabler-Recovery.zip" should be at the root of /sdcard (at least for me it was the case).
Click to expand...
Click to collapse
I think I was able to flash this. I keep getting errors about unable to open "/data/app-lib/com.h3r3t1c.onna" - rest off screen, then "Not a directory" and "unable to mount '/persist'", but it seemed to mount /system and flash successfully.
Unfortunately, this doesn't fix the bootloop.
I guess I'll try flashing the cache.img as suggested tonight and see if that works. If not, I guess I'll have to try and wipe.
If I do a factory wipe from TWRP, will I lose photos, videos I've taken? Restoring everything else will be a pain but it's really the photos that I haven't backed up yet I'm more concerned about.
Thanks!
Twrp doesn't wipe /sdcard
Sent from my Nexus 5 using Tapatalk
I just installed that module today and its working fine. I'm on the stock ROM. But doesnt Xposed put an Xposed disabler flashable zip file on your sdcard? Or is that something that maybe I just transferred over and forgot that I did. Because I dont remember transferring it to my phone or downloading it but I have it on there. If you have it, maybe try flashing that to disable Xposed and see if it boots.
EDIT: viking37 actually already suggested this.
Wiping or flashing cache didn't help either.
I tried a factory wipe, which didn't help.
Then I formatted data from TWRP and was able to boot but there were strange issues including a complete inability to connect to the cell network.
Also, TWRP kept complaining that it couldn't mount /persist
So finally I ran flash-all.bat from the factory image download to try and completely return to a factory image. It seemed to work but then I got into a bootloop where it reboots after upgrading android then apps starting.
I tried to do it again but now fastboot keeps giving me this error: FAILED (remote: flash write failure)
or if I try to wipe: FAILED (remote: failed to erase partition)
I'm starting to thing maybe it's a hardware problem with the internal flash... Is that likely or is there still something I can do?
Will I be able to RMA it in this state?
Thanks again for the help!
What's the process to flash the 33R system image without me losing the internal storage data? I have run in to some unfixable issue with the OPO and hence am considering flashing the factory image as the last option.
The only concern is the data on the internal storage which is important for me. As I am unable to boot to the desktop nor use the MTP mode from TWRP, I cannot transfer/back up the content.
I've tried flashing Mahdi/33R/38R zips after wiping system/dalvik/cache/data with no luck. The phone keeps rebooting and is in a loop. Tried fixing permissions from recovery with no luck. I have no idea what am missing here...
I'd appreciate if anyone can provide me with steps to flash system image (without losing the internal storage data) instructions or resolve the other bootloop issue.
Thanks!
All you do is TWRP -> Wipe -> Swipe -> Flash ROM (and others... only flash ROM for now and it'll boot, maybe one of the mods or whatever ur flashing causes ur phone to boot loop)-> Reboot.
And then your phone will stop boot looping
zephiK said:
All you do is TWRP -> Wipe -> Swipe -> Flash ROM (and others... only flash ROM for now and it'll boot, maybe one of the mods or whatever ur flashing causes ur phone to boot loop)-> Reboot.
And then your phone will stop boot looping
Click to expand...
Click to collapse
Thank you. I have done all that to be frank. I flashed only the Mahdi ROM zip first and then booted. No luck. It kept bootlooping. Then tried the same with 33R zip too. No luck again. I have no mods running whatsoever.
I've done a complete wipe too as apps and app data isn't something I care for currently. It's the internal storage.
Use fastboot, grab the latest stock images
fastboot erase system
fastboot erase boot
fastboot erase cache
fastboot flash system system.img
fastboot flash boot boot.img
This won't erase internal SD, all will be intact so long as your prior issue didn't corrupt it in anyway
Have you tried restoring a nandroid?
shaker2k said:
Have you tried restoring a nandroid?
Click to expand...
Click to collapse
Yup, did that too. Restored a couple of nandroids with no luck
demkantor said:
Use fastboot, grab the latest stock images
fastboot erase system
fastboot erase boot
fastboot erase cache
fastboot flash system system.img
fastboot flash boot boot.img
This won't erase internal SD, all will be intact so long as your prior issue didn't corrupt it in anyway
Click to expand...
Click to collapse
Thanks. Yup, used to do that with Nexus 5 and other nexus devices. But the factory image for OPO has other files too. Do I not need to flash them too somehow?
I think those are boot.img and tour radio firmware. I don't think you have tot flash those. But I'm also new to this...
Sent from my 1+1 using XDA Mobile Free
Wiped everything (internal memory too) and flashed the factory image clean and now I have the "Unfortunately, AudioFX has stopped working" error. The phone is unusable literally.
https://forums.oneplus.net/threads/how-do-you-go-from-custom-rom-to-stock-cm11s.95786/
Try this...
Sent from my A0001 using Tapatalk
---------- Post added at 07:31 AM ---------- Previous post was at 07:29 AM ----------
This will wipe your device... And make sure you use the right userdata.img
Sent from my A0001 using Tapatalk
syncopy said:
Wiped everything (internal memory too) and flashed the factory image clean and now I have the "Unfortunately, AudioFX has stopped working" error. The phone is unusable literally.
Click to expand...
Click to collapse
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
playya said:
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Click to expand...
Click to collapse
OMG! You're my hero and savior. This fixed it. Thank you so much. You have no idea how happy I am
Thank you!
Hi folks.
I'm facing a really weird problem. My friend's N5 doesn't want to boot with Lollipop, it shows the boot animation, but nothing happens, more than an hour and nothing.
I tried to flash back to kit kat. It indeed booted, but just to say that the camera and gallery has stopped, and gallery couldn't find any storage. When I go to the storage section in the settings, it doesn't show the pictures, music and other sources, just available space, cache and apps.
I tried to flash a custom rom to, but they all give me bootloops.
I never had this problems with my n4, so i don't know what to do anymore.
Any solutions?
Flash lollipop with fastboot. Then boot into the stock recovery and do a factory reset. Everything will be fine.
Sent from my Nexus 9 using XDA Free mobile app
I've already tried that, didn't work :crying:
Floydroider said:
I've already tried that, didn't work :crying:
Click to expand...
Click to collapse
You flashed the factory image with FASTBOOT and still had this problem? You sure?
Hmm. Try fastboot formatting all the partitions and then flashing the image again. Can't hurt.
_MetalHead_ said:
You flashed the factory image with FASTBOOT and still had this problem? You sure?
Click to expand...
Click to collapse
Yes, i'm absolutely sure. I'm used to use fastboot to flash my Nexus 4. I downloaded the proper factory image from Google and flashed it using both flash-all.bat and manual input in the cmd.
I tried to erase the partitions, format using TWRP, and install a custom ROM.
With twrp I can see the the internal storage partition, and even mount it to access by computer. But when the device boots, it just can't see the partition.
I put a song in the internal storage with twrp just to test, and when the device booted it didnt recognize the song, but when I got back to recovery, it was still there.
It seens that the problem is in the internal storage, but I don't know how to fix, and what could have caused it.
* Sorry, my english is bad :/
Floydroider said:
Yes, i'm absolutely sure. I'm used to use fastboot to flash my Nexus 4. I downloaded the proper factory image from Google and flashed it using both flash-all.bat and manual input in the cmd.
I tried to erase the partitions, format using TWRP, and install a custom ROM.
With twrp I can see the the internal storage partition, and even mount it to access by computer. But when the device boots, it just can't see the partition.
I put a song in the internal storage with twrp just to test, and when the device booted it didnt recognize the song, but when I got back to recovery, it was still there.
It seens that the problem is in the internal storage, but I don't know how to fix, and what could have caused it.
* Sorry, my english is bad :/
Click to expand...
Click to collapse
Try wiping cache in TWRP.
Wakamatsu said:
Hmm. Try fastboot formatting all the partitions and then flashing the image again. Can't hurt.
Click to expand...
Click to collapse
Tried that. I first used fastboot erase, didn't work, and then I use twrp to format to another fs. After that, I flashed the image again. Still nothing.
_MetalHead_ said:
Try wiping cache in TWRP.
Click to expand...
Click to collapse
I have wiped everything lots of times.
It's the first time I have a hard time trying to fix an android phone...
Now I flashed kitkat image again. It booted but with the storage problem. Then I update via notification, and it stuck in lollipop boot animation.
I will let it booting through the night. Or it boots after a couple of hours or the battery dies.
Floydroider said:
I have wiped everything lots of times.
It's the first time I have a hard time trying to fix an android phone...
Click to expand...
Click to collapse
Yeah this seems kinda crazy. Usually when stuff gets messed up like this a factory image clears it up. In your case, I honestly don't know what else to recommend. Sorry I can't be of more help.
Replace internal storage, nothing else you can do
Nothing worked in the end. My friend will send the phone to tech support.
Thank you guys for the help.
:good:
I got a nexus 5 off of eBay, the seller said he had tried to root it and failed so I thought I would have a crack at it.
I thought it would be an easy restore but I ran into a few problems:
Phone originally came with 6.0.1 installed.
On android 5+ I could not access the standard recovery screen, and when I pressed power+volUp it just said formatting /data and would not move from that.
Rolled back to 4.4 and I got into the ususal recovery screen.
Tried to do a factory reset, but it again stuck at formatting /data.
I left it the entire night while I slept and it was still saying formatting /data. in the morning, nothing had changed.
Trying to boot the phone normally just left it on the 4 startup screen.
I've tried doing a full flash of stock android with each seperate part manually.
Also /data is unable to be mounted in any custom recovery, like it is corrupted or locked somehow.
With the stock recovery, it cannot be detected by adb, but in cwm it can.
EDIT: checking the /data folder in adb shell shows it's completely empty, and the same with system even after flashing and flashing again.
Can anyone advise me as to what might be the problem here?
Reflash all partitions manually, including userdata.img file. After flashing the last partition, boot directly into stock recovery and perform a factory wipe, then reboot.
Done that multiple times, I get the same result on stock android.
I don't want to root or anything like that right now, just get it back to a working state.
So you flashed the userdata.img file?
audit13 said:
So you flashed the userdata.img file?
Click to expand...
Click to collapse
yes multiple times
If you flashed userdata.img multiple times and the phone still can't perform a factory reset, the emmc chip may be damaged.
My Nexus 5 is stuck in a bootloop where it says "Optimizing app x of y" and then reboots and repeats this endlessly. I'm not particularly concerned with getting the phone working, I only care about recovering the data on the phone. All the suggestions I've seen involve factory resets which wipe the data. How can I recover my data?
Is the bootloader unlocked? Did you enable usb debugging? Tried wiping cache in recovery?
audit13 said:
Is the bootloader unlocked? Did you thanks usb debugging? Tried wiping cache in recovery?
Click to expand...
Click to collapse
I'm not sure about the bootloader or usb debugging. Is there a way to verify? I have tried wiping the cache but it had no effect.
When you boot the phone, do you see the unlocked padlock at the bottom of the screen? If not, the bootloader is locked.
audit13 said:
When you boot the phone, do you see the unlocked padlock at the bottom of the screen? If not, the bootloader is locked.
Click to expand...
Click to collapse
Unlocked padlock is there, so I guess the bootloader is unlocked.
You can try flashing twrp, boot in twrp, mount data partition, and pull off data. As with any flashing process, things can go wrong which can result in the total loss of data.
What data do you need from the phone?
I have the same problem,
but the bootloader unlocks and locks again after rebooting,
I tried to flash in different ways but I didn't have any results, I did fastboot recovery twrp.img and I managed to get into this recovery, but twrp asks me for my password(i dont have any password), and if I try to format this appear cant mount/cant open cache
Do I need to change my motherboard?
If you can run Teamwin recovery then do a backup, then copy that onto your computer, then wipe data, cache, system, dalvik cache
after this, download any kitkat rom, gapps, and flash it
boot it up, install Titanium backup anow you can recover every app from nandroid backup (menu > special backup)
then backup every app again with titanium backup (menu > batch actions > backup all user apps)
Finally you can wipe your phone again and install any rom you want and recover every app with titanium backup
Why first an kitkat rom? because you can't extract from a nandroid since android 5, but the normal titanium backups work fine
---------- Post added at 04:29 PM ---------- Previous post was at 04:21 PM ----------
_MOE_ said:
I have the same problem,
but the bootloader unlocks and locks again after rebooting,
I tried to flash in different ways but I didn't have any results, I did fastboot recovery twrp.img and I managed to get into this recovery, but twrp asks me for my password(i dont have any password), and if I try to format this appear cant mount/cant open cache
Do I need to change my motherboard?
Click to expand...
Click to collapse
that seems like your filesystem is corrupt or the nand itself. Your phone is not unlocked so I think theres no solution :/ yeah replacing will help
That could be the solution, but I think that's only possible when you're unlocked: https://forum.xda-developers.com/showpost.php?p=76757221&postcount=2
If the bootloader relocks itself when the phone is rebooted, the internal memory chip is damaged and will require a motherboard replacement.