It says installaton success but follows with e: cannot load or something in that effect. I had my KF for months now and swaps plenty of roms on i butthe other night I was flashing a rom and accidently erased everything off the KF. I think I bricked my KF Ok people so I think I F***** up royaly. Ughhh thats not what I needed to hear.į/google-nexus-5/development/tool-06-03-14-one-click-factory-restore-t2513937 If the bootloader is relocking itself after every reboot, the emmc is probably defective and the only solution would be a new motherboard. Thanks for the suggestion, but I've tried that and still have had no success The img file is included with the stock Google ROM you are flashing to the phone. Then, immediately boot into recovery and perform a full wipe. These two commands will completely wipe your data. Try booting into fasboot and type "fastboot erase userdata" and then type "fastboot flash userdata userdata.img". So now I'm completely stumped, could this be the end of my Nexus 5? Please if someone could help me out with a solution I would really really really appreciate it! Instead I get this message at the bottom of the screen:Į:failed to mount /cache (Invalid argument)Į:Can't mount /ache/recovery/last_install It still hasn't worked and I'm starting to get worried because I've also started to notice my recovery can't really factory reset or wipe the cache. I then proceeded to try and manually flashing the stock rom files individually and unlocking the bootloader each time I flash a file which was really annoying. Every time I unlock the boot loader and it restarts the bootloader automatically re-locks. But by doing this I noticed that my bootloader was not staying unlocked when I try to unlock it. I figured I could just reflash the stock rom via the boot loader with the wugfresh root toolkit but that unfortunately didn't work. Nexus 5 in a bootloop, E: Failed to mount.Someone please help! Alright so here's the breakdown, my Nexus 5 has recently run into a problem where it suddenly decided to get stuck in a bootloop.
0 kommentar(er)
