Google Nexus 5 :: Flashing Factory Image Didn't Return To Stock
Jul 31, 2015
I had on my nexus 5 custom recovery, custom kernel (franco) and paranoid android rom (rooted). I wanted to get back to stock and flashed factory image lollipop 5.1 doint this
I was using the Cataclysm Rom for months without any problems. Today I restarted my phone (I do this every other day, when it gets a little bit slow) and it stuck in bootloop.
I tried wiping dalvik/cache, doing a factory reset, reflashing Cataclysm, nothing worked. So I decided to go back to stock (using [URL] ....) and I'm still stuck in a bootloop every time. I can access and use fastboot/stock recovery in the normal way, but it won't boot.. What I could do?
i have a nexus 5 rooted on stock android 5.1.1 . I am trying to flash the 5.1.1 factory image to unroot my device. But unfortunately i just get this message when its trying to flash the system.img and my device is now bricked target reported max download size of 1073741824 bytes load file:could not allocate 1073741824 bytes error: cannot load 'system.img' : not enough space.
I'm attempting to flash the latest factory image LMY48I and keep getting this error. Any problem with the image? The MD5 checks out and I've downloaded the file twice.
I have flashed various version 5 stock firmware's and the latest 6.0 using nexus tool kit, as well as specifically flashing only stock recovery using the tool kit and I cannot load into the stock recovery. I've spent hours looking for information on manually flashing the stock recovery without the tool kit but have found the instructions very vauge. Any information on flashing manually only the recovery would be very useful or information on why I may be having this issue.
I know every time i flash a rom it only shows about half of my internal storage. I have a 32gb version. So I end up having to go into a recovery "temp flashed" using the tool kit in order to clear some information and then i get my 32gb's back.
I"m wondering if the space being auto allocated or partitioned is interfering with the flash of the recovery..
I had to restore my phone to stock last night by manually flashing the 6P image from Google's Nexus page. I noticed that the storage now shows as 32GB instead of 64GB total. How to fix this?
archive does not contain 'boot.sig' archive does not contain 'recovery.sig' failed to allocate 1043723460 bytes error: update package missing system.img
I always get this error whenever I try to flash the Nexus 5 with using the flash-all file, I installed Android Studio, restarted my PC, even got the 6.0 factory image. None work and I always get that error? I'm trying to restart this Nexus 5 for my dad. The Nexus 5 is rooted with franco kernel and TWRP but on stock ROM.
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
I was recently on chroma rom with a layers theme applied and I decided to go back to stock and it seems like the layers theme stayed through all the flashes.... I'm not complaining because I much prefer my theme then the stock theme but I'm just curious as to why it stuck
I lost my nexus 5, 15days ago. All photos were saved in google photos. yet my account is not showing any backup of those pictures. All other google apps have successfully retrieved data but google photos has no backup. Is there anyway I can retain those pictures?
I was restoring a twrp backup and when it reaches "flashing system image" in the restore process it just reboots. Ive tried a few things but cant get it going. It just bootloops.
I was on 4.4.2 until two days ago when I flashed (for the first time, with success.. I think) to 4.4.3. Of course my bootloader was locked so when I unlocked it I lost my data, even with removing the -w flag in the batch file. Anyhow, here is what I had in my platform tools folder before executing the script to flash:
Notice that I don't have a system image in the directory. While the command prompt was executing, I noticed that it said "unable to find system.img" yet, when all was said and done, my phone rebooted, and it shows me on 4.4.3 now. I'm assuming it was successful because all the features of my phone work and it shows 4.4.3 like everyone else, but I'm still worried that the initial system img file wasn't in the directory. Should I go ahead and make sure ALL the img files (not just bootloader and radio) are in platform tools folder and re-flash again? Luckily I won't lose everything this time since my bootloader is unlocked and I will simply keep -w removed from the batch file.
Bought a nexus 5 for the youger bro last year and rooted so he could install kodi.What ever messing about he has done there is no image on the phone so is soft bricked.The phone waas rooted and the boot loader unlocked also you can access twrp.What can i do to restore from a nexus 5 image as i have no backups.
I bought a used Nexus 5 a few days ago and it has worked fine till today.
When I bought it, I checked every function of the phone on the spot to see if it was okay. It was rooted and a custom recovery and ROM was on it. I brought it home and flashed the factory image from Google. Worked fine till today.
Today, the phone turned itself off, first it showed a black screen, then a dimly lit but still black. I tried to turn it on but it shows a pixelated screen like this:
I then searched a lot: [URL] .....
I tried everything on these pages, but I couldn't solve my problem.
After a while, the phone turns off (with flickering screen) due to battery drain and if I plug it to my computer, it turns on with a dimly lit black screen then off, but I can access the storage on Windows.
I tried to open the bootloader, but it won't open. If I had been successful at accessing the bootloader, I would have easily reset the phone.
Nexus 5 32 GB LTE version Stock Android 5.1.1 Not rooted
My mum's N5 is completely stock - I can't believe i'm having issues with the only non-rooted device in my house!
I applied the OTA 6.0 update but when starting the phone i get a never-ending loop of "unfortunately ... has stopped" about lots of apps, and google services framework, process.acore, play services, etc
I got into stock recovery and cleared cache, no change
Any way to fix it without wiping data/factory reset?
So I'm running PAC ROM; I have a slight issue, I want stock GApps on my phone to add some features I've been wanting. When I flash it (tk_gapps-stock-5.1.1-20150809-signed.zip) on the official Nexus 5 lolipop ROM I got an error message, I read it and it says that I need to flash is ontop of another TK GApps, unless I wipe my cashe partition. So I wiped my Davlick Cashe and Cashe. Still have me the same message.
Getting a lot of notices to wait or quit the stock android browser.. Phone is not full or running too many apps.. I notice the same on my mac chrome also. Beach balling a lot..
my Nexus 5 has recently run into a problem where it suddenly decided to get stuck in a bootloop. I figured I could just reflash the stock rom via the boot loader with the wugfresh root toolkit but that unfortunately didn't work. But by doing this I noticed that my bootloader was not staying unlocked when I try to unlock it. Every time I unlock the boot loader and it restarts the bootloader automatically re-locks. 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. 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. Instead I get this message at the bottom of the screen:
E:failed to mount /cache (Invalid argument) E:Can't mount /ache/recovery/log E:Can't open /ache/recovery/log E:failed to mount /cache (Invalid argument) E:Can't mount /ache/recovery/last_log E:Can't open /ache/recovery/last_log E:failed to mount /cache (Invalid argument) E:Can't mount /ache/recovery/last_install E:Can't open /ache/recovery/last_install E:failed to mount /cache (Invalid argument)
So now I'm completely stumped, could this be the end of my Nexus 5?
I've been looking around, but I can't find anything to suggest root is available on the stock kernel. CF-Autoroot doesn't work for 6.0, and so far all I've found is root for custom kernels but I want all stock.
