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
Related
My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!
dwl99 said:
My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!
Click to expand...
Click to collapse
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM
DigitalMD said:
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM
Click to expand...
Click to collapse
Thanks but Odin cannot see the tablet to re-flash the recovery.
Downlods mode
Then flash new firmware
sembre said:
Downlods mode
Then flash new firmware
Click to expand...
Click to collapse
That's the problem - I cannot access download mode
UPDATE - it just started in download mode! I can manage from here!!
Just for the record you can install adb on the pc and run the command 'adb reboot recovery'. This will force the tablet to reboot in recovery mode.
Sent from my GT-I9300 using xda app-developers app
Jeez, this has taken up most of the day to fix. I came across many problems I have not previously experienced:
1. When the tablet was stuck at the boot animation and I tried to turn it off by long-pressing the power button it immediately restarted. The only way I could get it to turn off was by long-pressing the power button whilst it was connected to my PC.
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
3. Flashing CWM with Odin caused the tablet to reboot into the stock ROM which would not load, in the end I had to untick the "reboot" button in Odin, power it off then manually restart with the Vol- & power buttons.
4. The only way I could get a bootable ROM was by flashing CM10 with CWM. I tried to restore 2 previous CWM backups but on each occasion there was an error restoring the Data partition and I got stuck at the scenario at (1). The backups were made to the external SD card with CWM Touch - is the Touch version unreliable?
I would be really interested if anyone could shed any light on any of this stuff!
For how long did you let it install during the first reboot? It happened to me too, and it took about 10 minutes, maybe even more...
Also, did you try in the "Mount and storage" cwm menu the options "format system", "format data", "format cache" and "format preload" options, prior to re-flashing a ROM? I have read somewhere that for a clean install it's better to do this, as it really clears everything that could mess up the system between two different bases ROMs (like CM and stock).
What I do everytime is using in CWM these 4 "format" options, plus "wipe" system, cache and dalvik, then immediately after this I flash with cwm the new "zip" copied on the card. Then the first reboot is much longer than usual, as at this stage it installs the files, rebuild the dalvik cache etc.
Good luck
dwl99 said:
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
Click to expand...
Click to collapse
I think I gave it a good 20 mins to boot. When I got up this morning there was an error message saying that there was no room to install any more apps even though I had very few installed. Settings -> Storage would not calculate the space available so I figured that the partitions had become corrupted. I did the step by step format you described and reflashed & it all seems to be OK now.
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.
Hello all,
First time posting, long time lurker. Everybody here at XDA has been exceptionally helpful with every Android device I've owned. Whether I've had technical issues, or just wanted to try out some new ROM's or apps. I just wanted to take a second to thank you all before I got started with this post.
I've been pulling my hair out over this Nexus 5. It is my wife's phone that she never rooted, unlocked, or anything outside of generic user space.
I looked all over XDA and the web looking for solutions to this issue, but have been unsuccessful. Below is an overview of what's going on with my device.
___________________________________________
1: Nexus 5 repeatedly bootloops at initial Google logo
2: Bootloader locked - I can unlock it with fastboot oem unlock but it is reverted to locked at each restart.
3: Recovery mode bootloops every time cache is touched - Every time I attempt to sideload images or wipe cache recovery bootloops. This makes it impossible to flash factory images in recovery.
4: Problem seems to be with the cache - In fastboot I can wipe userdata, but when it gets to wiping cache I get an error.
5: Yes I have tried re imaging with factory images, flashing TWRP (doesn't take, ADB wasn't set to on before this happened and I think the bootloader unlock isn't really working, but Im not sure,) flashing stock cache, flashing stock bootloader etc.
Any idea's guys? This is my last attempt to fix before I just take the Nexus apart so I don't waste anymore time on it. I would be happy if I could get any functionality whatsoever.
Thanks so much,
Nathan
:Update:
I was able to boot into TWRP with fastboot boot recovery twrp.img.
Trying my luck here, it seems to have been able to wipe the cache, but not mount /data.
Unable to mount storage
Failed to mount /data (invalid argument)