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!
I just got my Nexus 5 a while ago and I just unlocked the bootloader and flashed TWRP and as soon as I opened TWRP it basically crashed and rebooted the phone is a boot loop but now when I go to TWRP the log says Unable to mount /data and I can't do anything. Does anyone have the solution? I knew I shouldn't have rooted -_-
Have you flashed a stock cache.img yet? Thats usually the first thing to try.
Sent from my Nexus 5 using Tapatalk
Uhh
Not yet right now I'm currently using Wug's Toolkit and seeing if that helps then i'll try that. Do you have the link by any chance?
OH thank GAWD its working again thanks for your help though
what did you do in the toolkit?
Generally the consensus here is to not use toolkits. There are 2-3 "Johnny Opposite" members, but the masses of senior members see them as a bad thing.
I explain what happend.
You opened bootloader, but you flashed twrp instead of start the phone to let stock recovery finish the formating. You flashed twrp and rebooted to twrp. Twrp found the commands in the memory or on the misc partition to do a factory reset then reboot, but that format command is not compatible with twrp, so that commamd was skipped and then twrp rebooted your, because that was the next command in the line. Now your started booting with an unformated cache and data partition. The easiest way to solve the issue is to do a format data in twrp to format data partition then a factory reset to format cache.
So In the toolkit I basically flashed the stock rom and it basically factory reset EVERYTHING so now its working again thanks for the help! Now to try this over again
killerkyman said:
So In the toolkit I basically flashed the stock rom and it basically factory reset EVERYTHING so now its working again thanks for the help! Now to try this over again
Click to expand...
Click to collapse
Ok thanks. It is best to do those steps manually
Sent from my Nexus 5 using Tapatalk
Yeah so I forgot to reboot before flashing recovery and entering that so now that I crossed that bridge I don't have to worry Wooh thank goodness I thought I totally messed up
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
Hi y'all. I've recently bought a refurbished nexus 5, installed TWRP and wiped cache and dalvik/art-cache. The thing is, when it rebooted, only 10 apps were optimized (given I had many more installed) and when I went to storage, I found out I had 200mb of data in the cache partition.
Is there something else I'm missing? Thanks!
Try flashing a stock rom and then perform a factory wipe from stock recovery.
audit13 said:
Try flashing a stock rom and then perform a factory wipe from stock recovery.
Click to expand...
Click to collapse
Done that, but nothing diferentt happened
Enviado desde mi Nexus 5 mediante Tapatalk
Did you flash the userdata.img file too? After flashing stock, relock the bootloader, reboot to fastboot to see if the bootloader stays locked. If it does, unlucky again and, if it wipes the phone in a few seconds, the emmc could be damaged..
audit13 said:
Did you flash the userdata.img file too? After flashing stock, relock the bootloader, reboot to fastboot to see if the bootloader stays locked. If it does, unlucky again and, if it wipes the phone in a few seconds, the emmc could be damaged..
Click to expand...
Click to collapse
I used the flash-all.bat given. Do I have to flash it or don't? I'll try what you suggest.
I would flash userdata.img as the script doesn't flash it.
Hey, wanted to say it worked! It seems my cache partition was corrupted or something, but your solution did the trick. Thanks!
Glad it worked for you. Enjoy your phone.
Hello everyone,
As stated, I began by waiting the 7 days to get the bootloader unlocked, then proceeded to copy this EU rom to internal storage, after following this video, my phone reboots after installing the room and goes straight into TWRP. When I click on reboot on TWRP, regardless if I choose System, Recovery or Bootloader, the phone keeps coming back to twrp. I would really appreciate if anyone can help me.
desmocedici_77 said:
Hello everyone,
As stated, I began by waiting the 7 days to get the bootloader unlocked, then proceeded to copy this EU rom to internal storage, after following this video, my phone reboots after installing the room and goes straight into TWRP. When I click on reboot on TWRP, regardless if I choose System, Recovery or Bootloader, the phone keeps coming back to twrp. I would really appreciate if anyone can help me.
Click to expand...
Click to collapse
Seems some system files got wiped. Open twrp and format data (don't wipe), after this restart to recovery and transfer the rom into your phone and flash, then reboot that's it. If this still occurs boot loop or returns to twrp, then download full firmware and flash it through mi flash, make sure to only select clean flash not to lock, and then wait until it boots to the welcome screen. After that flash twrp, format data (don't wipe), restart to recovery and transfer the rom into your phone, and flash and then reboot.
Hope this will fix your problem, please let me know
mrnannu said:
Seems some system files got wiped. Open twrp and format data (don't wipe), after this restart to recovery and transfer the rom into your phone and flash, then reboot that's it. If this still occurs boot loop or returns to twrp, then download full firmware and flash it through mi flash, make sure to only select clean flash not to lock, and then wait until it boots to the welcome screen. After that flash twrp, format data (don't wipe), restart to recovery and transfer the rom into your phone, and flash and then reboot.
Hope this will fix your problem, please let me know
Click to expand...
Click to collapse
Thanks for your reply.
I was able to get it fixed by changing the filesystem on the data & internal partitions to f2fs. Did a reboot and phone went into MIUI after that. I regret flashing the EU rom but that's another topic.
You
desmocedici_77 said:
Thanks for your reply.
I was able to get it fixed by changing the filesystem on the data & internal partitions to f2fs. Did a reboot and phone went into MIUI after that. I regret flashing the EU rom but that's another topic.
Click to expand...
Click to collapse
Can go back to Chinese again if you want. Just flash latest .zip format ROM from http://mifirm.net .