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!
Related
Hi:
I am quite worried, because my Xoom is unable to boot normally. I have EOS Nightly 99 installed, and after many weeks of perfect bahaviour, it was giving some messages like "gapps has closed", so I restarted the tablet. To my surprise, I saw the Moto lgo, the Tam EOS animation, and the "wheel" that appears before booting completely... and that´s it. Stuck.
I tried wiping dalvik-cache and cache and restart. Same result.
I tried restoring a nandroid backup. And here's the strange thing, because it can't restore data. The error message reads:
Error removing /data/data/com.android.browser/databases/webview.db-wal!Error formatting /data!
I tried wiping userdata, same error message
I tried with another recovery, in case it mattered (cwm and rogue). Same error
EDIT (Update):
I tried accessing the Xoom through ADB, and try to delete manually the pesky file. I was succesful. When I tried another "wipe data" from the recovery, I got a similar error:
Error removing /data/data/com.android.browser/databases/autofill.db (another file)
When I tried to delete it, I got the following error message (through adb) [why did it work the first time and not now???]
rm: can't remove 'autofill.db': Read-only file system
Any help, please? I'm at a loss here...
I post some photos of the errors
iruiz2 said:
Hi:
I am quite worried, because my Xoom is unable to boot normally. I have EOS Nightly 99 installed, and after many weeks of perfect bahaviour, it was giving some messages like "gapps has closed", so I restarted the tablet. To my surprise, I saw the Moto lgo, the Tam EOS animation, and the "wheel" that appears before booting completely... and that´s it. Stuck.
I tried wiping dalvik-cache and cache and restart. Same result.
I tried restoring a nandroid backup. And here's the strange thing, because it can't restore data. The error message reads:
Error removing /data/data/com.android.browser/databases/webview.db-wal!Error formatting /data!
I tried wiping userdata, same error message
I tried with another recovery, in case it mattered (cwm and rogue). Same error
Any help, please? I'm at a loss here...
I post some photos of the errors
Click to expand...
Click to collapse
have you tried re-flashing the rom completely?
daley stephenson said:
have you tried re-flashing the rom completely?
Click to expand...
Click to collapse
Yes, I did try that as well. It flashes without problem (rom + gapps), but does not restart (same original problem). I flashed it after a cache and dalvik-cache wipe.
iruiz2 said:
Yes, I did try that as well. It flashes without problem (rom + gapps), but does not restart (same original problem). I flashed it after a cache and dalvik-cache wipe.
Click to expand...
Click to collapse
ok backup your recovery to your desktop just so it is safe
try this
wipe cache - wipe dalvik cache - wipe/reset factory data - flash rom only then reboot - if it bootloops again enter recovery and go to advanced settings and run fix permissions and reboot
daley stephenson said:
ok backup your recovery to your desktop just so it is safe
try this
wipe cache - wipe dalvik cache - wipe/reset factory data - flash rom only then reboot - if it bootloops again enter recovery and go to advanced settings and run fix permissions and reboot
Click to expand...
Click to collapse
Thanks for your reply.
The problem, in case I wasn't clear, is that I can not make a WIPE DATA (that's when I get the error). It doesn't help wiping cache and dalvik beforehand. So I am in the same bootloop situation. tried fixing permissions, but I continue in the same situation.
iruiz2 said:
Thanks for your reply.
The problem, in case I wasn't clear, is that I can not make a WIPE DATA (that's when I get the error). It doesn't help wiping cache and dalvik beforehand. So I am in the same bootloop situation. tried fixing permissions, but I continue in the same situation.
Click to expand...
Click to collapse
sorry i must of mis-read your op - all i can suggest then is returning to stock using adb guide here http://goo.gl/G09vP then flashing your rom again - just make sure you get the right image for your device
daley stephenson said:
sorry i must of mis-read your op - all i can suggest then is returning to stock using adb guide here http://goo.gl/G09vP then flashing your rom again - just make sure you get the right image for your device
Click to expand...
Click to collapse
I will try this, as a last resort. Now I am making a backup of my internal sd card, because this process will delete everything in it. In case somebody wonders how to do this (I didn't know it myself), I used adb. The exact command I used was:
adb pull /data/media .
It's taking ages to backup my internal sd files (at a rate of 7Gb/hour aprox).
Meanwhile, anybody knows what possibly is happening to my Xoom?
After wating several hours to back up my internal sd card, I have been able to wipe (format) /data from fastboot. In case somebody needs to do something similar:
Once in recovery, type in your computer:
adb reboot bootloader (wait for the xoom to reboot into fastboot)
fastboot erase userdata
I then rebooted into recovery, and restored a nandroid backup. This time, no problems.
Now I am in the (again) long process of copying the /data/media files back to my Xoom, but I was VERY relieved to see that it was booting normally after this...
glad you got it fixed dude
I am a relatively new android user but do enjoy flashing roms, kernels etc
My problems began when i was trying to flash a new rom on my Nexus 5
I was trying to flash this rom http://forum.xda-developers.com/showthread.php?t=2655722 but despite doing a factory reset and wiping the dalvik cache and cache it refused to boot in to the new rom
I tried to flash the rom multiple times but without success, eventually when trying to boot into recovery to try again i was greeted with an unthemed TWRP recovery asking for a password despite the fact that i had a custom theme and multirom installed I tried to proceed anyways but was greeted with E: unable to mount storage
In desperation i tried to solve this problem and found this
UsoftTech :: WwW.UsoftTech.CoM ::
TWRP asking for password
After unboxing my Nexus 5, here's what I did:
1. Booted into bootloader
2. fastboot oem unlock
3. Flashed TWRP v2.6.3.0
4. Booted to recovery
The screen that greeted me says "Please Enter Your Password".
I can hit the cancel button below this which takes me to the normal TWRP screen. I then pushed SuperSU to /sdcard, but when I flash it it fails because it's unable to mount /cache or storage.
When I reboot to the system, it takes an awfully long time (approximately 30s) to progress past the "Google" screen, and then it just seems to sit on the booting animation forever.
Any help?
EDIT: Solved my own problem.
Hit cancel at the password screen, then go into Wipe and then do a factory reset by swiping. Then go back into Wipe and press the 'Format data' button. You have to type 'Yes', and it will take a few seconds. After that everything should work normally.
TWRP asking for password
Click to expand...
Click to collapse
I now fear that i maybe without both a rom and all my files such as my music that was stored on my phone.
Is there any way for me to undo the damage i may have done to to my phone?
You can't recover the data. But you can push files over with ADB.
Sent from my Nexus 7 using Tapatalk
JoJostar said:
I am a relatively new android user but do enjoy flashing roms, kernels etc
My problems began when i was trying to flash a new rom on my Nexus 5
I was trying to flash this rom http://forum.xda-developers.com/showthread.php?t=2655722 but despite doing a factory reset and wiping the dalvik cache and cache it refused to boot in to the new rom
I tried to flash the rom multiple times but without success, eventually when trying to boot into recovery to try again i was greeted with an unthemed TWRP recovery asking for a password despite the fact that i had a custom theme and multirom installed I tried to proceed anyways but was greeted with E: unable to mount storage
In desperation i tried to solve this problem and found this
Wrong thread.
d
Click to expand...
Click to collapse
So I unlocked, rooted and installed Euphoria ROM on my Moto G today, and now I'm perplexed to find that when I select the "Reboot" option either in Android or TWRP, I immediately get shoved back into TWRP. Rebooting to Bootloader works as expected, rebooting to Recovery works as expected, but the normal reboot doesn't.
Also, when my phone is offline and I plug it in, it immediately lights up and boots directly into TWRP. I don't know why this is, but I'd like to fix it since it's hit and miss trying to boot into the ROM normally.
Can anyone help me pin point the problem? In all my years with Android I've never seen an issue with boot priority such as this.
Things I have done:
-I tried to decide on a recovery so I flashed PhilZ, CWM, and TWRP in that order from the fastboot commandline
-wiped system, data, cache, dalvik cache, and flashed Euphoria ROM
Thanks!
One thing I would suggest is to flash the stock recovery and try rebooting, even i had encountered this problem. Later you can flash twrp again and everything will work fine.
Are you getting any errors while wiping partitions
sjandroiddeveloper said:
Are you getting any errors while wiping partitions
Click to expand...
Click to collapse
I'm having the same problem here. Wiping works alright, no errors at all. Although the built-in TWRP file manager is unable to see any files in the system folder.
so i wanted to backup my oneplus one using twrp 3.0 and for some reason i decided to wipe the cache before i backed it up. I went to wipe (just the regular cache) and it kept trying to wipe but it never succeeded so i just forced rebooted it went back to twrp and backed up my phone. Once the backup was done i tried to boot it up and i was met with a boot loop. Then i kept rebooting my phone and no luck. then i tried to completely wipe my phone. well just a factory reset. it didn't work i was greeted with an error saying my cache is not mounted or something like that. so now i cant even wipe anything at all and i think twrp has a feature where you can access files from recovery and that doesn't work for me. adb isnt working either i was trying to push a file. What im trying to do is flash a newer version of twrp or try to adb sideload my same rom. but i dont have access to my same rom cause the links are down. my rom is minimal os btw. any ideas ?
Edit: I've fixed the problem by booting into fastboot and flashing a newer version of twrp 3.0.2. then i wiped the cache and it was successful. then i booted up and it works!
About two weeks ago just before CyanogenMod's announcement of its closure I updated my Moto G2015 (1GB) to the latest nightly, which was CM14.1 released on the 25th of December, with its corresponding GAPPS version also released on the 25th of December (ARM, android 7.1, Full)
Yesterday the 7th of January my Google Apps decided that they didn't want to open, at first I thought it was just updating and since my battery was low I plugged in my device, I later realised that my device randomly went to a boot loop and stayed there. I grew impatient so I restarted the phone and went to the Recovery Mode (To Re-Flash the ROM), but to my annoyance the recovery (TWRP) just stayed on the 'Teamwin' logo forever, it would randomly go black then return to that logo. infuriated I turned on my phone and went to backup/reset and clicked 'factory reset'. it annoyingly booted me into recovery to reset the device, which of course I couldn't do.
Now the simple answer would have been for me to go and wipe the cache and data from 'google play services' and or 'launcher3' but I did, either it always shows 'calculating' preventing me from clicking 'manage space' or clearing 'cache' or when it did finally show, after I did click the button for the cache and or data to be cleared it would say 'calculating', and a quick check would discover that nothing was actually cleared.
Kind Regards, and Thank You to any help recieved,
NotSoGreat
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
acejavelin said:
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
Click to expand...
Click to collapse
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
NotSoGreat said:
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
Click to expand...
Click to collapse
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
I'll try now.
acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
Right, so I reinstalled and flashed the latest version TWRP, when I opened into it, it took about 1 minute before it opened up, it ran a quick operation that I just glimpsed, it looked like it was wiping cache and user data, my phone was rebooted and I was right, my phone had been reset for the second time today (I'm almost a pro at reinstalling all my apps). I rebooted into the recovery and Look and Behold, it was working.
Thanks slot for your help and time.