Hi everyone,
I have a Nexus 5 that, up until recently, was unlocked and rooted. However, my power button started giving me issues, and after looking around online I determined it was a hardware issue. My phone is still within the warranty period, so I decided to unroot, re-lock, and reset the warranty flags. To do so, I used WugFresh's Nexus Root Toolkit. This seemed to work fine.
However, later on my battery died while I was out away from home. When I plugged it in overnight to charge, I woke up to find that it was stuck on the flying dots boot animation. I haven't been able to get it to start up since then.
All the solutions I find require flashing a custom recovery, or the factory image. However, I can do neither, since my bootloader is now locked.
I've also tried re-unlocking the bootloader using both the NRT and the manual method described here. The final reboot never progresses past the flying dots animation, and when I hard reset and relaunch into fastboot mode, it tells me that the bootloader is still locked.
As an alternative, I tried booting into recovery mode/recovery menu and doing a factory data reset there. I get the following error messages:
Code:
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recover/log
... and so on for every folder it tries to access on the cache partition. Afterwards, when I reboot, same problem. Flying dots and that's it.
Note regarding all of the above: in each case I've tried to let the boot animation run for as long as possible just to make sure. At minimum, I've let each method go for at least an hour and a half, but it never progresses any further.
So. How screwed am I? Does anybody have a solution to get my phone working again?
You can still try to flash to stock image with Julian OS tool (script)
http://forum.xda-developers.com/goo...o-flash-5-0-lrx21o-flash-5-0-n5-tool-t2957801
This script unlocks your bootloader, flashes os 5.0/5.01 and relocks your bootloader, all within 2 minutes. I have tried it and it works fine. At the end you have a stock unrooted device.
Related
Dudes,
I was running CM 0701 nightly fine and decided to boot to CWM-based recovery and flash latest nightly from 0703. It got about 2/3 the way through updating apps after boot and froze. Then screen stayed black, but would backlight. Was unresponsive to touch, but I could get it to take screenshots (at least I could hear the sound made by triggering one). I longpressed the power button to force reboot and entered bootloader. Finally I could see the screen again. I thought all was better and it just needed a reboot so I reboot again and let it boot. Still no screen. So I longpressed to reboot, got into bootloader, then revovery... and tryed to reflash nightly from 0701 but it won't access my "/sdcard" because it won't mount. Same error ("Error mounting /data!) when I try to fatory reset or mount/unmount.
WTH?!
Anybody have any ideas what broke this? What it a change in last two nightlies? A change to the recovery?
I'm going to try http://forum.xda-developers.com/google-nexus-5/help/help-e-mount-sdcard-cwm-6-0-4-5-trying-t2802715 when I get home... in way too many hours. Sadface.
I also posted this in CM Forums: http://forum.cyanogenmod.com/topic/...cant-mount-data-after-0703-nightly-boot-fail/
Firstly try and fastboot flash a stock cache.img
rootSU said:
Firstly try and fastboot flash a stock cache.img
Click to expand...
Click to collapse
Thanks @rootSU. Ultimately and unexpectedly the phone came back to life before I could get to a computer with adb access. I had tried rebooting several times before, but magically after about 6 hours of downtime (no charge or anything) it rebooted up fine. It was a little shaky and slow at first, and ran the update apps process again on the next boot but has since be stable. No flashing. A couple reboots. All fine.
Thanks to the XDA community for existing and providing such a reassuring resource for knowledge and problem solving!
I need help in recovering a two year old Nexus 4 to usable state.
It went into a loop while in use. Background and symptoms are as follows:
1. OS was OTA updated to Lollipop and was used for several days before problem occured.
2. Now, on powering on, the device remains indefinitely (checked for 30-40 minutes) in the loop displaying 4 coloured shapes going in circles.
3. At first, I tried factory reset, but that failed showing errors like failure to mount /cache etc.
4. Device can be put in fastboot mode (showing product, variant etc.), but always with "locked" state.
5. I used Nexus root toolkit 2.0.4 for attempting recovery. The device is detected in fastboot mode.
6. I tried to unlock bootloader. But it fails to unlock. After selecting unlock option with volume-up and pushing power button, device seems to unlock, but it then boots into the loop similar to the one after power-on. Powering off and putting the device in fastboot mode shows the device state as "locked" again.
7. "Flash stock + unroot" with "soft-bricked/bootloop" option attempts to write to the device but fails at every step with the reason: FAILED (remote: not supported in locked device). This happens 7 times during flash and once during postflash boot. I repeated the exercise with "force-flash mode" and "post-flash factory reset" checked as well, with same failure messages.
8. FYI: I have downloaded the factory image "occam-lrx22c-factory-86c04af6.tgz". It is verified by NRT as OK.
Based on this, I feel that unless the device can be "unlocked", writing to it and recovering it will be difficult.
Can anyone suggest a different set of steps / different recovery program, which may help?
I have read similar threads on this forum, but could not get a complete set of "instructions + working links to tools" from those threads.
Hello,
Earlier this week my nexus 5 refused to boot after i powered it down while at work. The phone begins to boot up but hangs at the spinning colored circles, i have left this over 24 hours and there is no change.
The device is stock and unrooted, I have tried a factory reset from recovery mode which completed OK however did not fix the problem.
At this point i would of normally just RMAd the device however i bought it on amazon, and the seller appears to have imported it from Hong Kong, so there was no valid warranty for me to claim under. Lesson learned there for the future but not a great help for me at the moment.
Because the device would still power up and since the warranty was already invalid i decided to try flashing it to factory. I unlocked the bootloader and flashed a factory image to the device in hopes this would resolve the fault but again just had the same results, I am however totally new to doing this so may have made a mistake here, but from what i can tell i followed the process correctly as i did not receive any errors.
The phone still boots to the same point, and i am still able to access the bootloader, is there anything else you think i can try or is the device bricked?
Flash the factory image with fastboot. See this, http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app
So i attempted to flash again, followed method 2 on the linked post this time.
It all appeared to go through OK until i came to do the final factory reset when i noticed an error on the screen this time.
E: failed to mount /cache (invalid argument)
E: failed to mount /cache (invalid argument)
E: can't mount /cache/recovery/command
E: failed to mount /cache (invalid argument)
E: can't mount /cache/recovery/last_locale
locale is [(null)]
stage is []
reason is [(null)]
After running the factory reset and rebooting the phone it is still stuck at boot
So today after reading around I've found a number of people with similar issues that made some progress by reverting to Kitkat, so i re-flashed the phone to 4.4.4.
The phone now boots up again however i have no reception at all, Google Play store and the camera also appear to not work. All other functions I've tried seem to be OK so there's at least some progress.
I let the phone update back to 5.0.1 but just ended up not booting again so i downgraded once more.
I would be perfectly happy to remain on 4.4.4 so long as my phone actually worked, but at the moment nothing I've tried has managed to correct the lack of reception. I've not found anything online to solve the problem even though some people have mentioned the same issues after downgrading.
Can anyone point me in the right direction?
TigerDude said:
So today after reading around I've found a number of people with similar issues that made some progress by reverting to Kitkat, so i re-flashed the phone to 4.4.4.
The phone now boots up again however i have no reception at all, Google Play store and the camera also appear to not work. All other functions I've tried seem to be OK so there's at least some progress.
I let the phone update back to 5.0.1 but just ended up not booting again so i downgraded once more.
I would be perfectly happy to remain on 4.4.4 so long as my phone actually worked, but at the moment nothing I've tried has managed to correct the lack of reception. I've not found anything online to solve the problem even though some people have mentioned the same issues after downgrading.
Can anyone point me in the right direction?
Click to expand...
Click to collapse
You should try this http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Thank you so much, for a while there i thought i owned a £300 paperweight but everything's running again, you sir are a legend.
TigerDude said:
Thank you so much, for a while there i thought i owned a £300 paperweight but everything's running again, you sir are a legend.
Click to expand...
Click to collapse
Indeed he is! :good: Saved my phone too. I had the exact situation as you http://forum.xda-developers.com/goo...p-lollipop-t3098632/post60491129#post60491129
I am wondering though: In my case the error I got was "failed to mount /persist" , and bitmodo's guide is exactly for that. In your case it was the cache partition. Is there a different command to fix the cache partition?
My wife's stock moto g phone went into what I can only guess was some sort of bootloop this morning. I have been playing with it all evening with no luck. I could get into fastboot, but selecting recovery I would end up in another sort of loop where I could see the distress "no command" image briefly flashing on the screen every 5-10 seconds and there was no way to use the volume/power buttons to get into the recovery screens. No warranty left on the phone so I decided to play.
I was able to use adb to unlock the boatloader, root the phone and flash TWRP, I could push over a copy of a slimkat rom I chose, but whenever I attempt to wipe cache and what not I keep getting mount errors (can't mount /data, /system, etc.) Trying to format gives me mount errors as well, and using file manager all directories appear empty except for anything I push over to /sdcard
I since flashed using adb (Philz Touch 6) and once again all I see are mount errors....
I guess my question is, is it possible that this could be a hardware issue and and will never get passed this ? Or have I accomplished enough above to prove there is still life in the phone and just need to keep searching and trying things?
If you think there is a chance, any ideas of what I could try next?
Thanks
Morgan
Trying to root my phone. Flashed TWRP in Odin, then installed SuperSU through TWRP. At the end it gives me the error in the title, and I get a 'failed integrity check' when booting into the system.
Help?
I've always read you have to do a factory reset after TWRP installation due to encryption, but apparently you don't have to
It still says you lose your OS though.
https://forum.xda-developers.com/galaxy-s7/help/root-twrp-flashing-t3535545
AzzyC said:
No factory reset required. Basically, the file system of your Data partition is incorrect and that is why it can't be mounted on to.
Go to 'Wipe'->'Advanced Wipe'->Click on the Data box->'Partition Options'->(You may be seeing values like 0mb for most of the information displayed and why you can't mount to it; if you are not let me know!)->'Change File System'->(Try out different File Systems until you being to see true values for the sizes, but avoid using EXT2 and EXT3 if you can)
Doing all this you will be able to Mount to your Data partition, however your OS will be deleted! So get your phone into Download mode, open up Odin program on your PC, and flash a Bootloader (BL) and your phone will be fine.
Then flash the 'no-verity-encryption-opt.zip' and then your SU Binary and Xposed Framework etc.
Good luck again Buddy!
---------- Post added at 05:41 PM ---------- Previous post was at 05:12 PM ----------
Wait Install the No-verity zip first then, then flash a BL
Click to expand...
Click to collapse
It's a brand-new phone so I don't really care about the OS.
Also I tried restoring my Nandroid backup, but the drive appears empty when I go to the "Restore" option in TWRP. Not sure if I need to fix the data thing first anyway, but surely it should show up?
EDIT: Now that I think about it wasn't there some requirement to clear a cache at some point? I vaguely remember that from the last time I rooted an S7.
I've tried formatting, and the readout says "formatting" and then "Done.", but there's still a progress bar and the title area still says "Formatting...".
EDIT 2: It's plugged in but the battery is still dropping, and it only started at 8%. So it might just die anyway.
I recently went back and forth between Oreo and a TWRP Nougat backup, and was flashing TWRP each time I went up to Oreo because I was installing it via Odin which was blowing away TWRP.
I must have had to factory reset and flash the dm-no verity.zip a few times each TWRP install before I got /system and /data to not return an error. I was probably doing something out of order, but it always seemed finnicky.
How does one do the factory reset?
TWRP still reckons it's formatting, even though it says "Done.", but the battery has just hit 0% so it won't last much longer anyway.
EDIT: Or not...battery still going strong at apparently 0%. But it's been formatting for over two hours now.
Advanced wipe with data, cache, and davlik cache checked should be enough
When was I supposed to do that step? It rings a bell but it isn't in the instructions I found.
The phone finally died, and now I cant' seem to get past the TWRP splash screen.
EDIT: Just plugging it in results in the TWRP splash screen. None of the buttons seem to do anything, so I can't get into download mode and reflash TWRP or anything...
Okay, so I left it on the charger for a couple of hours.
Pressing and holding the power button turns it off. A few seconds after plugging it in, I get the Galaxy splash screen followed by the TWRP splash screen, and then the latter just stays there. Forever.
Once I turn it off, I'm unable to turn it back on at all - standard boot, recovery or download. I pressed and held the buttons for a full minute, made no difference.
EDIT: Leaving it off the charger results in the screen turning off a few minutes later. Again, no amount of pushing the buttons will do anything.
EDIT 2: Got it into download mode by plugging it in and holding the buttons down while waiting for it to automatically boot. Next step? Flash a bootloader, or reflash TWRP, or both?
Tried reflashing TWRP, changes nothing. Also tried flashing a BL and CP from the last time I installed SupermanROM, but it failed in Odin. Not sure if they're just too old or something, I have no idea how that stuff works or how updated my software is or anything.
It's the same handset I had before, but it had to go back to Samsung for repair because the battery blew up, so they very kindly wiped everything, reset Knox, etc.