Database Info

[Q] Phone soft bricked - tried everything!

Hi, if anyone can help me solve this, I will be eternally grateful.
So I was following the CyanogenMod guide for installing the ROM on my HTC One S, but I foolishly flashed the ROM as a .zip, instead of the boot.img.
I can access the bootloader screen, and also the TeamWin recovery screen, but I cannot seem to use flashboot.
It always comes up as <waiting on device>.
I am lost, because I obviously used flashboot to flash the recovery and the ROM across to my phone, and all the files are still in the same folder.
Basically, I cannot start my phone, other than into the recovery screen or the bootloader screen. I cannot seem to flash anything across either.
If anyone can solve this issue from this poor explanation I will be more than impressed.
Many thanks.

trentarmy said:
Hi, if anyone can help me solve this, I will be eternally grateful.
So I was following the CyanogenMod guide for installing the ROM on my HTC One S, but I foolishly flashed the ROM as a .zip, instead of the boot.img.
I can access the bootloader screen, and also the TeamWin recovery screen, but I cannot seem to use flashboot.
It always comes up as <waiting on device>.
I am lost, because I obviously used flashboot to flash the recovery and the ROM across to my phone, and all the files are still in the same folder.
Basically, I cannot start my phone, other than into the recovery screen or the bootloader screen. I cannot seem to flash anything across either.
If anyone can solve this issue from this poor explanation I will be more than impressed.
Many thanks.
Click to expand...
Click to collapse
It is waiting for device because the phone isn't in bootloader (fastboot USB) connected to pc...most likely.
So with phone in bootloader and it reads fastboot USB
from your fastboot folder press shift and right click to open command window.
fastboot flash boot boot.img
(this assumes you have put the boot.img in the fastboot folder)
Then go to recovery
install rom.zip
wipe the caches
If you don't have the rom.zip on your phone then mount usb storage in twrp and move the rom.zip from your pc to your phone.
Hopefully your Hboot is 2.15 or you will just bootloop.

tivofool said:
It is waiting for device because the phone isn't in bootloader (fastboot USB) connected to pc...most likely.
So with phone in bootloader and it reads fastboot USB
from your fastboot folder press shift and right click to open command window.
fastboot flash boot boot.img
(this assumes you have put the boot.img in the fastboot folder)
Then go to recovery
install rom.zip
wipe the caches
If you don't have the rom.zip on your phone then mount usb storage in twrp and move the rom.zip from your pc to your phone.
Hopefully your Hboot is 2.15 or you will just bootloop.
Click to expand...
Click to collapse
So can I clarify that I need to flash both the boot.img file and the rom.zip separately. Then install the rom.zip, not the boot.img?
Because I install the rom.zip last time without the boot.img being flash, and thats when it messed up.
Basically, am I installing the .zip or the .img?
Thanks a million.

trentarmy said:
So can I clarify that I need to flash both the boot.img file and the rom.zip separately. Then install the rom.zip, not the boot.img?
Because I install the rom.zip last time without the boot.img being flash, and thats when it messed up.
Basically, am I installing the .zip or the .img?
Thanks a million.
Click to expand...
Click to collapse
.img , you need to extract boot.img from ROM zip and than just "fastboot flash boot boot.img" ,no quotes in command -that is for boot.img and you do flash ROM as a zip

luxandroid said:
.img , you need to extract boot.img from ROM zip and than just "fastboot flash boot boot.img" ,no quotes in command -that is for boot.img and you do flash ROM as a zip
Click to expand...
Click to collapse
Thanks!
Next issue. I have flashed the boot.img to the phone, now I need to get the rom.zip onto the phone.
Everytime I click mount on TWRP, my computer tells me that I must format the disk before I can use it.
I can't seem to use adb, I always get "no device found".
Any ideas?

adb push ROM.zip /sdcard ,ROM needs to be in fastboot folder, are U s-off or s- on ,did U flash ROM zip before soft brick, can U see files from TWRP when U go to install from sd...some info that is important,if all fails think you'll have to run RUU to fix memory partitions
Sent from my HTC One S using XDA Premium 4 mobile app

luxandroid said:
adb push ROM.zip /sdcard ,ROM needs to be in fastboot folder, are U s-off or s- on ,did U flash ROM zip before soft brick, can U see files from TWRP when U go to install from sd...some info that is important,if all fails think you'll have to run RUU to fix memory partitions
Sent from my HTC One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Everything is in the same folder. adb push function still won't work.
I am s-on.
I did flash the rom.zip before the soft-brick, but when it bricked, I wiped the memory and cache, reset to factory settings. So there is currently no files on the phone.

U wiped all this in bootloader ?
Sent from my HTC One S using XDA Premium 4 mobile app
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Anyway best thing is to flash RUU and do all over again...
Sent from my HTC One S using XDA Premium 4 mobile app

luxandroid said:
U wiped all this in bootloader ?
Sent from my HTC One S using XDA Premium 4 mobile app
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Anyway best thing is to flash RUU and do all over again...
Sent from my HTC One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I wiped it all via the TWRP recovery.
Any chance you could walk me through RUU? Or at least point me in the right direction.
It does sound like it would be easiest just to start all over again. What's the best way to do this?
Thank you for your help.

trentarmy said:
I wiped it all via the TWRP recovery.
Any chance you could walk me through RUU? Or at least point me in the right direction.
It does sound like it would be easiest just to start all over again. What's the best way to do this?
Thank you for your help.
Click to expand...
Click to collapse
what happened when you tried to push the rom.zip via adb?

ThudButt said:
what happened when you tried to push the rom.zip via adb?
Click to expand...
Click to collapse
I just get "error: device not found"
Any ideas?
If not, could someone please run me through just wiping everything and starting again?
Cheers

luxandroid said:
U wiped all this in bootloader ?
Sent from my HTC One S using XDA Premium 4 mobile app
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Anyway best thing is to flash RUU and do all over again...
Sent from my HTC One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not sure if this makes a difference, but when connected to my PC, my phone is called "My HTC".
I remember reading somewhere that it should be called an Android ADB Device or something similar?

[Q] Stuck at X screen

Obviously I'm a noob, so sorry if this is stupid or there is an obvious answer (I've spent a lot of time looking and couldn't find it though). I was having problems with my phone so decided to flash back to stock and relock it to 'start again'.
Maybe that wasn't a great idea because I've had lots of problems since then. When I try to flash back to stock using nexus root toolkit I get "failed (remote: invalid bootloader)" and the phone finishes still in bootloader. There was a suggestion to force flash, but given the warnings around that I'm pretty nervous about doing that. If I then start my phone up it stays on the google screen for quite a while and then gets stuck on the X screen (it isn't frozen because the animation keeps running, but nothing else happens, even if I leave it for an hour).
I did a bit more reading and tried wiping the dalvik cache and cache. It then said it was upgrading android, optimising apps etc, but then got stuck again. I tried resetting again and the phone now restarts when I push the off button and slowly goes through both the google screen and X screen.
This might be a stupid problem, but I'm stuck so any help would be great.

Flash the stock images manually rather than with a toolkit. You can find a guide stickied under the nexus 5 general section.
Sent using xda-developers app

http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
Follow this carefully step by step using method 2. Be extremely careful flashing the boot loader, in fact you can probably skip that part. As long as your boot loader is always in tact it's virtually impossible to brick. As of right now you're stuck in what's called a boot loop. Most likely, either your boot.img (not the same as boot loader) or system.img (aka ROM/firmware) is messed up and is causing it.
Welcome to modding, have fun, but be smart
Sent from my Nexus 5 using xda app-developers app

Chromium_ said:
Flash the stock images manually rather than with a toolkit. You can find a guide stickied under the nexus 5 general section.
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks. Either a new problem or a related one - following the guide for setting up adb and fastboot, when i type adb devices into the command prompt nothing is listed (says "list of devices attached", but there isn't anything listed).

beshakey said:
Thanks. Either a new problem or a related one - following the guide for setting up adb and fastboot, when i type adb devices into the command prompt nothing is listed (says "list of devices attached", but there isn't anything listed).
Click to expand...
Click to collapse
Go into fastboot mode and run "fastboot devices". If the device shows up there, that's good enough.
Sent using xda-developers app

Chromium_ said:
Go into fastboot mode and run "fastboot devices". If the device shows up there, that's good enough.
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks, that worked. But having done it when I reboot the phone it does the same thing (hangs of the Google screen for a long time then moves to the X screen and stays there). My phone is rooted and I have clockworkmod installed, so I selected fix root when asked, not sure if that is relevant?

Did you continue to follow the guide and flash the stock images in fastboot
Sent from my Nexus 5 using xda app-developers app

Yeah I did. I got the message "FAILED (remote:invalid bootloader image) and archive does not contain 'boot.sig' 'recovery.sig' and 'system.sig'. Everything else was OKAY. Put into recovery mode fine (with clockworkmod), wiped data and rebooted (fixing root when asked) but the problem described above remains.

More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh

beshakey said:
More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh
Click to expand...
Click to collapse
And you are following the factory image flashing guide that has been provided above?
Can you try going through the guide again, and tell us the specific errors that you are encountering.

And use method two, not the first one that talks about running the flash all script. You should be doing command's like "fastboot flash boot boot.img"
Sent from my Nexus 5 using xda app-developers app

beshakey said:
More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh
Click to expand...
Click to collapse
Don't worry, you'll get it, eventually. When you first start doing this kind of thing, it takes some getting used to because you have to read VERY carefully, and perform each step EXACTLY as stated. Computers are absolutely unforgiving of even the tiniest mistake, so you have to take your time, and be patient when you have to start all over. But, it's a challenge, and a learning process, and a lot of fun, once you get the hang of it.
Sent from my Nexus 5

OK, step by step. If you need more detail yell out.
1) I've downloaded ADB and Fastboot
2) If I put ADB devices into the command prompt I don't get any devices listed. But if I put in Fastboot devices I get the serial number of my phone
3) Previously I'd been using method one. So I now extract the image for hammerhead krt16m to my f:\ drive. I've also extracted radio-hammerhead-M8974A-1.0.25.0.17 and bootloader-hammerhead-HHZ11d to the same location and renamed them to radio.img and bootloader.img respectively
4) Phone is connected to computer and in fastboot (and detected by fastboot devices)
5) In command prompt when I type in fastboot flash bootloader f:/bootloader.img I get the error message FAILED (remoteL invalid bootloader image).
6) Flashed radio.img and rebooted bootloader and system.img (no reboot) without any errors (although they took a while)
7) Flashing userdata.img got the error 'FAILED (remote: flash write failure)
8) Performed all the remaining commands without any errors (when erasing the cache I got the message 'Did you mean to fastboot format this partition? erasing 'cache'... OKAY
9) Entered recovery mode. Earlier when I did this it was fine, but now (like when I try to start the phone) the screen lights up but no text etc appears
10) At this point I'm stuck, as I can't see the cwm text so can't select wipe data/factory data reset (although I did do this as part of earlier attempts)
From the 'on but no text' state, I can using the on button to restart into the same state or can enter fastboot (where text etc appears fine)

One at the boot loader you said you put f:/bootlaoder.img that was wrong, no drive letter. You do not need to flash your boot loader though anyways. Avoid doing that unless you have to, it is the only thing that will brick your phone.
You said system.img flashed fine, did not see any Menton of a boot.img or recovery.img. you need all three of these.
So, start over again. Make sure you flash a boot.img system.img and recovery.img separately. DO NOT flash the bootloader.img unless you have to (to update). Again, the boot loader is the one thing that will brick your phone if done wrong.
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 07:31 AM ---------- Previous post was at 07:28 AM ----------
Sorry I just read through that tutorial and it does tell you to use drive letters. Im used to flashing with my files in the location of fastboot so I don't need to do that.
Sent from my Nexus 5 using xda app-developers app

@op why you are flashing 4.4 images?? it has a different bootloader then 4.4.2.
i guess your primary bootloader now is 11k and not 11d or 11a .....(since you took the ota out of the box)
bootloader version must match with the rest of images.
so download 4.4.2 images and flash them using 11k bootloader. (note that you have the old and new bootloaders on your device, volume down + power will take to the new bootloader 11k, and Volume down + volume up + power will take you to the old bootloader).
regarding adb command, it will not work in fastboot mode, it works when booting in os with usb debugging enabled, or in custom recovery mode

Good catch.
Sent from my Nexus 5 using xda app-developers app

samersh72 said:
@op why you are flashing 4.4 images?? it has a different bootloader then 4.4.2.
i guess your primary bootloader now is 11k and not 11d or 11a .....(since you took the ota out of the box)
bootloader version must match with the rest of images.
so download 4.4.2 images and flash them using 11k bootloader. (note that you have the old and new bootloaders on your device, volume down + power will take to the new bootloader 11k, and Volume down + volume up + power will take you to the old bootloader).
regarding adb command, it will not work in fastboot mode, it works when booting in os with usb debugging enabled, or in custom recovery mode
Click to expand...
Click to collapse
Thanks I'll try that. Is there any way for me to confirm on my phone what my primary bootloader is?

beshakey said:
Thanks I'll try that. Is there any way for me to confirm on my phone what my primary bootloader is?
Click to expand...
Click to collapse
Boot into it using power volume down and it will list the version
Sent from my Nexus 5 using xda app-developers app

travisjustin said:
Boot into it using power volume down and it will list the version
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Will try that, thanks.
I'm pretty sure I've done something stupid to cause this and I had a thought about what it might be - my phone was still at 4.3 for some reason. It would receive the update and install it, but the version wouldn't change to the new one. So should I try to track down the old 4.3.? bootloader?

beshakey said:
Will try that, thanks.
I'm pretty sure I've done something stupid to cause this and I had a thought about what it might be - my phone was still at 4.3 for some reason. It would receive the update and install it, but the version wouldn't change to the new one. So should I try to track down the old 4.3.? bootloader?
Click to expand...
Click to collapse
4.3? The nexus 5 ships with kitkat 4.4 ...there is no 4.3 for it.
Sent using xda-developers app

[Q] Bootloop, Unable to mount '/cache', '/persist', storage

Hi,
Today I woke up to my phone boot-looping after leaving it to charge overnight, despite it having run fine for close to a month (I have been running Cataclysm ROM and TWRP 2.6.4.3 since I got my Nexus 5).
After a long wait at the Google and Nexus logos, there's a system popup of 'Android is upgrading' present on the screen. However, right after completing the 'updating of apps', the system popup 'Media Storage has stopped working' appears and the phone immediately restarts again.
Upon booting into TWRP, it presents me with a password screen, which I have never encountered before. After pressing 'Cancel' though, I'm directed to the TWRP main menu.
Attempts to factory reset the phone resulted in:
Formatting cache using make_ext4fs function.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount storage.
Checking through the phone's internal storage with TWRP's file manager showed my internal storage as (0MB) and that the sdcard folder was empty. Other folders such as system and sys had subfolders which also were displayed as empty, though I'm not sure if that would be the case on a normally functioning device.
Any help would be appreciated, thanks
EDIT: I tried restarting my phone again after posting and after spending a long period of time at the Nexus boot animation, the 'Android is upgrading' system popup now just flashes through a few messages before 'Unfortunately, Calendar has stopped working.' appears and the phone restarts. Not sure if this happened initially, or if this usually happens, but the phone loops from the Nexus boot animation.

Try fastboot flashing the cache.img from the factory image
---------- Post added at 07:10 PM ---------- Previous post was at 06:53 PM ----------
So, is it working now?

jd1639 said:
Try fastboot flashing the cache.img from the factory image
---------- Post added at 07:10 PM ---------- Previous post was at 06:53 PM ----------
So, is it working now?
Click to expand...
Click to collapse
Problem still exists, just that the phone now boots till the 'Select language' screen before a flood of '[Insert Google app/service] has stopped working.' system popups appear and the phone restarts.
TWRP still shows same messages when trying to factory reset, and file manager still shows 0MB internal storage.
EDIT: Apparently the phone is now boot-looping to the conditions as stated in the OP after trying to factory reset.

Looks like full return to stock then
Sent from my Nexus 5 using Tapatalk

rootSU said:
Looks like full return to stock then
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Seems like there's nothing much I can do now anyways... what an unexpected event

exare said:
Seems like there's nothing much I can do now anyways... what an unexpected event
Click to expand...
Click to collapse
Just flash the stock image and see if you still have problems. What do you mean by there's not much you can do?

Quick question: What should I do if a particular img file keeps getting the <remote: flash write failure> error when trying to flash the stock factory images?
jd1639 said:
Just flash the stock image and see if you still have problems. What do you mean by there's not much you can do?
Click to expand...
Click to collapse
I meant in regards to correcting the problem without going back to stock?

exare said:
Quick question: What should I do if a particular img file keeps getting the <remote: flash write failure> error when trying to flash the stock factory images?
I meant in regards to correcting the problem without going back to stock?
Click to expand...
Click to collapse
Not sure I understand. Did you flash the whole factory image and you're getting that error when one of the image files is flashing? If so which image file?

jd1639 said:
Not sure I understand. Did you flash the whole factory image and you're getting that error when one of the image files is flashing? If so which image file?
Click to expand...
Click to collapse
I was following abaaaabbbb63's guide (http://forum.xda-developers.com/showthread.php?t=2513701), but when using the flash-all.bat file I noticed several img files had the <remote: flash write failure> error, thus I tried to do it the 'long way' as stated in the guide, by flashing each image one by one.
radio.img is not able to be flashed, and it is only the second step in the guide...

exare said:
I was following abaaaabbbb63's guide (http://forum.xda-developers.com/showthread.php?t=2513701), but when using the flash-all.bat file I noticed several img files had the error, thus I tried to do it the 'long way' as stated in the guide, by flashing each image one by one.
radio.img is not able to be flashed, and it is only the second step in the guide...
Click to expand...
Click to collapse
Try a different usb port. A usb 2.0 not 3.0 and user the cable that came with your phone

jd1639 said:
Try a different usb port. A usb 2.0 not 3.0 and user the cable that came with your phone
Click to expand...
Click to collapse
Was not using USB 3.0. Tried a different port but same results. I was able to flash the bootloader before this though.

exare said:
Was not using USB 3.0. Tried a different port but same results. I was able to flash the bootloader before this though.
Click to expand...
Click to collapse
Try this
fastboot oem lock. Then reboot into the bootloader. Does it show the bootloader as locked or is it still unlocked?

jd1639 said:
Try this
fastboot oem lock. Then reboot into the bootloader. Does it show the bootloader as locked or is it still unlocked?
Click to expand...
Click to collapse
unlocked. I tried flashing the bootloader again but now it seems to have the write error too.

exare said:
unlocked. I tried flashing the bootloader again but now it seems to have the write error too.
Click to expand...
Click to collapse
I was afraid of that. I think your emmc has gone bad. Sorry to say but you're going to have to rma the device.
---------- Post added at 09:10 PM ---------- Previous post was at 09:03 PM ----------
Can I ask how you rooted your phone?

jd1639 said:
I was afraid of that. I think your emmc has gone bad. Sorry to say but you're going to have to rma the device.
---------- Post added at 09:10 PM ---------- Previous post was at 09:03 PM ----------
Can I ask how you rooted your phone?
Click to expand...
Click to collapse
:crying: do you think I'll be able to get it repaired/refunded considering I have unlocked the bootloader already?
I followed Chromium_'s guide (http://forum.xda-developers.com/showthread.php?t=2507905) and got it rooted by flashing Cataclysm.

exare said:
:crying: do you think I'll be able to get it repaired/refunded considering I have unlocked the bootloader already?
I followed Chromium_'s guide (http://forum.xda-developers.com/showthread.php?t=2507905) and got it rooted by flashing Cataclysm.
Click to expand...
Click to collapse
There have been others who were able to warranty the phone with the bootloader unlocked. Seems Google has been pretty good about that. Just tell them the phone no longer boots which I'm assuming is the case.

jd1639 said:
There have been others who were able to warranty the phone with the bootloader unlocked. Seems Google has been pretty good about that. Just tell them the phone no longer boots which I'm assuming is the case.
Click to expand...
Click to collapse
Okay then. Thanks for all the help!

exare said:
Okay then. Thanks for all the help!
Click to expand...
Click to collapse
No problem, sorry it didn't turn out better. I feel for you

jd1639 said:
I was afraid of that. I think your emmc has gone bad. Sorry to say but you're going to have to rma the device.
---------- Post added at 09:10 PM ---------- Previous post was at 09:03 PM ----------
Can I ask how you rooted your phone?
Click to expand...
Click to collapse
I don't want to sound like a black sheep, but something seems fishy about the emmc on nexus 5 devices
The cause is the method used to unlock/root? Or that casually, most cases are from Junior members that somehow are missing some important things here and there

exare said:
Hi,
Today I woke up to my phone boot-looping after leaving it to charge overnight, despite it having run fine for close to a month (I have been running Cataclysm ROM and TWRP 2.6.4.3 since I got my Nexus 5).
After a long wait at the Google and Nexus logos, there's a system popup of 'Android is upgrading' present on the screen. However, right after completing the 'updating of apps', the system popup 'Media Storage has stopped working' appears and the phone immediately restarts again.
Upon booting into TWRP, it presents me with a password screen, which I have never encountered before. After pressing 'Cancel' though, I'm directed to the TWRP main menu.
Attempts to factory reset the phone resulted in:
Formatting cache using make_ext4fs function.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount storage.
Checking through the phone's internal storage with TWRP's file manager showed my internal storage as (0MB) and that the sdcard folder was empty. Other folders such as system and sys had subfolders which also were displayed as empty, though I'm not sure if that would be the case on a normally functioning device.
Any help would be appreciated, thanks
EDIT: I tried restarting my phone again after posting and after spending a long period of time at the Nexus boot animation, the 'Android is upgrading' system popup now just flashes through a few messages before 'Unfortunately, Calendar has stopped working.' appears and the phone restarts. Not sure if this happened initially, or if this usually happens, but the phone loops from the Nexus boot animation.
Click to expand...
Click to collapse
Try to
- Fastboot flash recovery recovery.IMG (twrp)
- wipe everything through twrp
- try to fastboot flash stock image

Android.process.acore has stopped

My wife's Rooted Nexus 5, stock 6.0.1 phone has become unusable. After deleting some contacts she gets a popup that "Android.process.acore has stopped" every couple of seconds.
Searching for solutions on the web I've
Deleted her contacts data and cache
Deleted her contacts storage data and cache
Reset app preferences
Disabled contacts
And nothing stops it.
Is there a solution to this problem?
Thanks.
Is it possible to restore a working nandroid made on a different nexus 5 to the messed up nexus 5?

maybeme2 said:
My wife's Rooted Nexus 5, stock 6.0.1 phone has become unusable. After deleting some contacts she gets a popup that "Android.process.acore has stopped" every couple of seconds.
Searching for solutions on the web I've
Deleted her contacts data and cache
Deleted her contacts storage data and cache
Reset app preferences
Disabled contacts
And nothing stops it.
Is there a solution to this problem?
Thanks.
Is it possible to restore a working nandroid made on a different nexus 5 to the messed up nexus 5?
Click to expand...
Click to collapse
you need to flash again the stock rom. try using nexus toolkit.
https://forum.xda-developers.com/google-nexus-5/development/toolkit-wugs-nexus-root-toolkit-v1-8-3-t2517778
you can get the stock roms here.
https://forum.xda-developers.com/google-nexus-5/development/rom-android-m-preview-2-flashable-zip-t3157299

Thank you. I thought I might need to reflash the rom. I was trying to avoid it because flashing roms always makes me nervous. But I'll just have to do it.
Xposed is also installed on the phone. I assume I will need to uninstall that first too. Ugh!

maybeme2 said:
Thank you. I thought I might need to reflash the rom. I was trying to avoid it because flashing roms always makes me nervous. But I'll just have to do it.
Xposed is also installed on the phone. I assume I will need to uninstall that first too. Ugh!
Click to expand...
Click to collapse
Try flashing just the system image and not the whole rom. You'll be able to save all your apps and data that way.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
Try flashing just the system image and not the whole rom. You'll be able to save all your apps and data that way.
Click to expand...
Click to collapse
That would be great!
Never done that. I'll search the web for just the 6.0.1 system image. I assume that's different from the "factory image" from https://developers.google.com/android/images
Could you point me in the right direction?

maybeme2 said:
That would be great!
Never done that. I'll search the web for just the 6.0.1 system image. I assume that's different from the "factory image" from https://developers.google.com/android/images
Could you point me in the right direction?
Click to expand...
Click to collapse
Download the factory image, it's a zip file. Extract it and inside is another zip file. Extract that too. Inside that are a number of .img files, one of which is the system.img. You'll use that one. Use fastboot to flash it, fastboot flash system system.img. If you've never used fastboot Google "15 second adb xda" The first thing that should pop up is a tool by Snoop05. That'll install fastboot and adb on your PC.
Sent from my [device_name] using XDA-Developers Legacy app

You are wonderful jd1639. Thank you very much.

What you suggested worked like a charm. I flashed the system.img successfully. Took no time.
Unfortunately, it did not solve the Android.process.acore bug.
So I decided to just flash the entire rom and go that route. That's where I ran into problems.
1. I did adb reboot bootloader
and then flash-all
which resulted in something about system img not found (even though I had moved everything into the same folder).
Now, the phone is now no longer rooted and I can no longer get into recovery. And adb reboot bootloader no longer works. I get "error device offline".
I'm not that knowledgeable in android and flashing and am stuck. What should I do?

Ok, solved the offline problem. Disconnected and reconnected the USB cable.
But still no go. Here's what I get with flash-all
For some reason my paste of the results won't show when I save.....
Essentially,

Ok, solved the offline problem. Disconnected and reconnected the USB cable.
But still no go. Here's what I get with flash-all
For some reason my paste of the results won't show when I save.....
Essentially, it says archive does not contain 'boot.sig', archive does not contain 'recovery.sig'.

Sorry, error.

maybeme2 said:
Sorry, error.
Click to expand...
Click to collapse
The no .sig stuff is normal and you don't need to worry about it. Just ignore it and let the flash continue and do its thing.
Let me know if that works.
Sent from my [device_name] using XDA-Developers Legacy app

Unfortunately, I can't ignore it because it stops with "press any key to exit". So I exit.
Wish you lived next door. I would be glad to pay you to do it.....

maybeme2 said:
Unfortunately, I can't ignore it because it stops with "press any key to exit". So I exit.
Wish you lived next door. I would be glad to pay you to do it.....
Click to expand...
Click to collapse
Does it flash anything before it gets to the press and key? It should flash the bootloader and modem before it gets to the .sig stuff. Or does it immediately go to the press any key? If it goes immediately to the press any key then it sound like the PC isn't recognizing the N5. If that's the case boot into the bootloader, press power and vol up and down keys at the same time. Once it boots into the bootloader then connect it to your PC. Then using fastboot issue the command, fastboot devices If your PC recognizes the N5 it'll spit out a long alpha/numeric number on your pc. About 16 characters long.
If you get the alpha/numeric then go to the folder of the second zip file you extracted. There should be boot, cache, etc image files. Then open a command window /power shell there and we'll flash all the partitions manually. Issue the following commands, one after the other once the previous one ends.
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
If any of those don't work let me know which one.
Sent from my [device_name] using XDA-Developers Legacy app

Thank you again.

Thank you jd1639.
All the flashing worked when I did it sequentially as you suggested. Don't know why the batch file got stuck but no matter, you saved the day.
So it is now factory fresh. Please remind me how to root it.
Thank you so much for hanging in there to help a total stranger.

maybeme2 said:
Thank you jd1639.
All the flashing worked when I did it sequentially as you suggested. Don't know why the batch file got stuck but no matter, you saved the day.
So it is now factory fresh. Please remind me how to root it.
Thank you so much for hanging in there to help a total stranger.
Click to expand...
Click to collapse
No problem. To root download twrp for the N5. I Google teamwin nexus 5. It'll be a .img file. Also download supersu. Google supersu 2.82 sr5. To flash twrp boot into the bootloader and with fastboot flash it, fastboot flash recovery twrp.img. Twrp.img is the full file name of the download. Then boot into recovery (it'll be twrp). From recovery your PC will see the N5 and you'll be able to copy supersu to the download folder of the N5. Then flash it in twrp (install) supersu will be a zip file.
Sent from my [device_name] using XDA-Developers Legacy app

Problems never end.
1. I successfully flashed twrp.img using fastboot. But when I go to recovery I get the empty robot with the red exclamation mark. (No twrp recovery)
2. Other problem: the 32Gb nexus 5 now shows only 16Gb.

maybeme2 said:
Problems never end.
1. I successfully flashed twrp.img using fastboot. But when I go to recovery I get the empty robot with the red exclamation mark. (No twrp recovery)
2. Other problem: the 32Gb nexus 5 now shows only 16Gb.
Click to expand...
Click to collapse
Yep, you're having fun. The problem is twrp is not sticking. But first let's solve the memory issue, which is fairly common. The red ! Is the stock recovery. It's been awhile since I've messed with it so you might have to play around with it a little. When you get the ! Press and release the power and vol up keys. Timing is important so that's where the playing around comes in. It might be vol down or both vol. If you get it right it'll go into the stock recovery, don't ask why you need to mess with the keys and it won't just go into recovery and not go through the ! crap.
Anyway, once you get into recovery go to factory reset and reset the device. That will solve the memory issue.
Now to twrp, instead of flashing twrp you'll want to boot into it. Use fastboot and the command fastboot boot twrp.img. Once in twrp get supersu on your device and then flash it. Then go to reboot in twrp and boot into the bootloader. Then use fastboot to flash twrp, fastboot flash recovery twrp.img. Twrp should stick now.
Edit: to get into stock recovery it's power and both vol keys. Press, hold about 1/2 second, and release.
Sent from my [device_name] using XDA-Developers Legacy app

Yes I'm having fun...... (that's why non-experts are scared to do things which the experts say "not to it - which is true when everything works)
The 32Gb becoming 16 is a problem I encountered previously on another nexus 5. So I noted its solution : the fix is to wipe cache and data. Catch 22: how to do that when you can't get into recovery? I was going to search for a way to wipe cache and data using fastboot when I read your message.
I'll try to do what you advise. Fingers crossed.

Stuck on a loop

So after trying to root my device I successfully unlocked my device and installed twrp and magisk through twrp but after trying to reboot into the system, it doesn't. Every time i try to reboot into the system, it just goes into a loading "G" and boots right back into recovery or twrp.

adrianherndez304 said:
So after trying to root my device I successfully unlocked my device and installed twrp and magisk through twrp but after trying to reboot into the system, it doesn't. Every time i try to reboot into the system, it just goes into a loading "G" and boots right back into recovery or twrp.
Click to expand...
Click to collapse
Flash the stock boot.img to both slots. That should get you running again. Then I'd boot twrp then install magisk. I wouldn't try to flash twrp but if you do make sure you flash that before magisk. Then reboot to twrp and flash magisk.
Sent from my [device_name] using XDA-Developers Legacy app

I'm literally in the same situation. Bootloader unlocked but only able to boot to TWRP. Tried running the "flash-all" from the Google stock image but it doesn't run. Now i'm lost and my new phone is not at its best.

Tarush13 said:
I'm literally in the same situation. Bootloader unlocked but only able to boot to TWRP. Tried running the "flash-all" from the Google stock image but it doesn't run. Now i'm lost and my new phone is not at its best.
Click to expand...
Click to collapse
Make sure you've updated your sdk platform tools.
Sent from my [device_name] using XDA-Developers Legacy app

Just re-downloaded from Google, still doesn't run. Also, not getting "no valid slot to boot" when I flash the boot.img file
---------- Post added at 09:59 PM ---------- Previous post was at 09:38 PM ----------
update: got the flash-all file to work, but now the touchscreen does not work when I am trying to set it up. There is no twrp and I cannot do anything except boot to fastboot or stare at the setup screen

Tarush13 said:
Just re-downloaded from Google, still doesn't run. Also, not getting "no valid slot to boot" when I flash the boot.img file
---------- Post added at 09:59 PM ---------- Previous post was at 09:38 PM ----------
update: got the flash-all file to work, but now the touchscreen does not work when I am trying to set it up. There is no twrp and I cannot do anything except boot to fastboot or stare at the setup screen
Click to expand...
Click to collapse
Are using the commands
fastboot flash boot_a boot.img
And
fastboot flash boot_b boot.img
There are two slots you need to flash the image to.
Sent from my [device_name] using XDA-Developers Legacy app

Hi, I got it to boot, but now I cannot use the touchscreen. Any ways to resolve this?
jd1639 said:
Are using the commands
fastboot flash boot_a boot.img
And
fastboot flash boot_b boot.img
There are two slots you need to flash the image to.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse

Tarush13 said:
Hi, I got it to boot, but now I cannot use the touchscreen. Any ways to resolve this?
Click to expand...
Click to collapse
Is the touch screen issue with twrp or when you boot the device itself? I know some people have had an issue with the touch screen not working in twrp.
Sent from my [device_name] using XDA-Developers Legacy app

Yes, it is when I boot the device. When I try to click on "start" to begin the initial device setup, nothing happens. None of the touch input is being received by the device.
jd1639 said:
Is the touch screen issue with twrp or when you boot the device itself? I know some people have had an issue with the touch screen not working in twrp.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse

Tarush13 said:
Yes, it is when I boot the device. When I try to click on "start" to begin the initial device setup, nothing happens. None of the touch input is being received by the device.
Click to expand...
Click to collapse
I'm not sure why it's doing that. But, if I was faced with that issue I'd first flash the system.img to both slots. And if that didn't work I'd try flashing the vendor.img.
Sent from my [device_name] using XDA-Developers Legacy app

flashed vendor.img and still cant use the touch screen? Touch input is definitely not being recorded. Any other ideas?
jd1639 said:
I'm not sure why it's doing that. But, if I was faced with that issue I'd first flash the system.img to both slots. And if that didn't work I'd try flashing the vendor.img.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
---------- Post added at 11:01 PM ---------- Previous post was at 10:54 PM ----------
Just to clarify, I flashed system to both slots and then vendor. Neither seemed to work.
Tarush13 said:
flashed vendor.img and still cant use the touch screen? Touch input is definitely not being recorded. Any other ideas?
Click to expand...
Click to collapse

Tarush13 said:
flashed vendor.img and still cant use the touch screen? Touch input is definitely not being recorded. Any other ideas?
---------- Post added at 11:01 PM ---------- Previous post was at 10:54 PM ----------
Just to clarify, I flashed system to both slots and then vendor. Neither seemed to work.
Click to expand...
Click to collapse
Have you tried a factory reset on the stock recovery?
Sent from my [device_name] using XDA-Developers Legacy app

I can't get to the stock recovery. When I tried to go there from fastboot, I got a "no command" error. Basically all I can do is go to fastboot mode and either reboot to the start screen where the touch input does not work or power off. I also don't see a recovery file in the source image I downloaded from google.
jd1639 said:
Have you tried a factory reset on the stock recovery?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse

Tarush13 said:
I can't get to the stock recovery. When I tried to go there from fastboot, I got a "no command" error. Basically all I can do is go to fastboot mode and either reboot to the start screen where the touch input does not work or power off. I also don't see a recovery file in the source image I downloaded from google.
Click to expand...
Click to collapse
The boot.img contains the stock recovery as well as the kernel. Flash that.
Sent from my [device_name] using XDA-Developers Legacy app

Tarush13 said:
I can't get to the stock recovery. When I tried to go there from fastboot, I got a "no command" error. Basically all I can do is go to fastboot mode and either reboot to the start screen where the touch input does not work or power off. I also don't see a recovery file in the source image I downloaded from google.
Click to expand...
Click to collapse
The no command thing is normal. When you see that screen, push and hold the power button and then, while still holding the power button, press volume up once. That will get you into recovery.

boot.img flashed, factory reset with stock recovery, still can't use the touch screen. This is beyond anything I've encountered in rooting. No clue why this is happening.