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?
Related
Hi,
I have a totally stock desire s from t-mobile Hungary. Today it gave me an option to install the new Sense 3.0 update.
Everything went fine, until it came to the screen with the phone icon and the red triangle with the (!)
When pulling the battery the phone starts rebooting after the HTC screen.
I tried to press vol up and power buttom it goes into the Android system recovery where i it says:
E:Can't open /cache/recovery/command
It has options for wipe data/factory reset --tried nothing changed
wipe cache partition --nothing changed
apply update from sd card -- tried, gives an error then reboots.
On the sd card i found the ota update in the downloads folder, but im stuck here.
Im also not sure if downloading a stock RUU rom would fix the issue, since im not sure what was originally on the phone.
It was purchased at T-mobile in hungrary.
I dont intend to root the phone since i dont want to lose my warranty, but i would really like to fix this without having to send the phone away for repair.
Thank you for your time!
Ben
as you were completely stock before this update then i would reccomend returning your phone under warranty. as all you have done is follow th eofficial method of updating. the problem has not been caused by you so you should recieve a replacement or fix under warranty
Yes, i'm afraid i will have to send it in for repair. Im asking this because repairs take a long time, and if there is a way to solve it myself, it would be great.
Would it fix my problem if id install a factory rom? And if it would, how can i find out what was on the phone before the update happened?
Thanks
Ben
you could try flashing a custom recovery via 1 of the guides in the development section. then try wipeing and formatting all partitions. the install from an RUU again.
that might work.....
Hi guys,
I'm having a weird problem hoping someone can solve or at least explain.
First, my phone - I9020T, stock 4.0.3 unrooted
Today i finally got 4.0.4 OTA, wanted to install it. The installation got stuck on error (attached image), and when i tried entering recovery, when choosing install from SD card i get:
" E: failed to mount /sdcard (No such file or directory) "
But when i start the device regularly it works fine... no crashes, no error reading from SD-Card.
One more thing you should know is i'm experiencing the "Hairdryer stuck on google logo" bug. which means when i start the device is get stuck on "Google" and i have to pull the battery and heat it under hand dryer for a few second in order it will start regularly. but it used to be okay since i managed a month ago to re-update to 4.0.3 from the recovery (while having the problem).
BTW - tried searching the forum for that problem with o
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.
Hi, I have an S7 edge that started to reboot and hang everyday a while ago (2 month and have it for 4 month). Lately after reboot it got to a boot-loop point where neither clear cache nor clear data solved it and had to reinstall firmware. Did that for a while a couple of times which was frustrating and don't really know what the problem is, probably the motherboard as I read online. not sure at all.
Nevertheless, that is not my only problem since the last time I flash the firmware (always used stock firmwares), somehow it broke the efs mount point or something and now is says "Failed to mount /efs" in the standard Samsung recovery mode. It is still on boot-loop, with no root access, no USB enabled, and no OEM allowed to be installed, so I am in a bit of trouble, can flash a non-stock and I don't really know what options I have.
I bought it overseas so Support says they won't help me.
Any Ideas?
Thanks
andresm13 said:
Hi, I have an S7 edge that started to reboot and hang everyday a while ago (2 month and have it for 4 month). Lately after reboot it got to a boot-loop point where neither clear cache nor clear data solved it and had to reinstall firmware. Did that for a while a couple of times which was frustrating and don't really know what the problem is, probably the motherboard as I read online. not sure at all.
Nevertheless, that is not my only problem since the last time I flash the firmware (always used stock firmwares), somehow it broke the efs mount point or something and now is says "Failed to mount /efs" in the standard Samsung recovery mode. It is still on boot-loop, with no root access, no USB enabled, and no OEM allowed to be installed, so I am in a bit of trouble, can flash a non-stock and I don't really know what options I have.
I bought it overseas so Support says they won't help me.
Any Ideas?
Thanks
Click to expand...
Click to collapse
Greetings and welcome to assist. It looks like you managed to fix your issue
https://forum.xda-developers.com/showpost.php?p=70710190&postcount=119
which is excellent news so I'll close this up and enjoy your stay at xda
Sawdoctor
Hello everyone, first of all I want to apologize for my bad English, I'm Argentine.
I'm in a serious problem that I've been trying to solve for a year now. First of all, my cell phone is a Samsung Galaxy Ace 4 Neo, which I tried to install an unofficial rom based on CM13.
This is where everything began. When I flashed the rom, I accidentally disconnected the USB cable, causing my phone to completely crash. Determined to recover it, I had already installed the TWRP. When I proceed to want to format everything, the /system, /data and /cache partitions gave an error when being partitioned. So I stayed for 2 weeks until I visited a forum (which by the way, I do not remember what it is) that said that changing the ext4 format to exfat would allow you to format well. SERIOUS MISTAKE IS MINE WHEN TRUSTING IN THAT FORUM. By doing this I not only screwed up the phone already, but it did not even turn on. As a last resort, I used Odin to nand erase and reflash the stock rom. Surprisingly, there were no errors when reflashing, but when the phone is turned on, it remains in the boot screen. Investigating Odin's options, I realized that I can not use the re-partition option, since I get the error "Can't open the specified file. (Line: 1831)". I do not know what else to do with this phone, so my last hope is you. Please I need help!!!