Database Users

[Q] Nexus 7 Bricked, can't access Bootloader or Fastboot

I think I may have my Nexus 7 (2012) in a badly bricked state.
I was running Android 4.3, unlocked and rooted with stock recovery. The tablet froze while using GMail. Pressing the home or back buttons just gave me a black screen with the buttons "highlighted" by circles. I waited several minutes and decided to just power off the tablet. When I looked over about a half hour later I saw that the tablet was frozen on the white Google screen. Two more reboots produced the same result.
I did some research and determined that it might be a good idea to try a cache wipe. I booted into the bootloader and selected Recovery. The tablet rebooted to an android on his back with a red triangle and the words "No command" underneath. Attempting to boot back into the bootloader (Power, Vol+, Vol-) produced the same results - red triangle and the words "No command". I could no longer boot into the bootloader. Powering off and powering on normally also takes me to "No command".
I discovered that I can press Power & Vol+ while in the "No command" state. Doing so produces the following text at the bottom of the screen:
E:Can't open /cache/recovery/log
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_install
E: failed closing /dev/block/platform/sdhci-tegra.3/by-name/MSC
(I/O error)
I get a menu at the top with the options to reboot, apply update from ADB, wipe data/factory reset and wipe cache. Attempting to wipe cache produces:
-- Wiping cache...
Formatting /cache..
Cache wipe complete.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_locale
After a few minutes I boot back to the red triangle android.
Attempting a factory reset produces:
--Wiping data...
Formating /data...
Formatting /cache...
Date wipe complete.
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
E: failed closing /dev/block/platform/sdhci-tegra.3/by-name/MSC
(I/O error)
E:failed to mount /cache (Invalid argument)
I've tried using the apply update from ADB option. I can use adb devices to see the serial number. Fastboot doesn't seem to respond and won't list the device. Flashing the factory 4.3 image (downloaded from Google and unzipped) using adb sideload uploads the image and then produces the error:
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
...followed by all of the "cache mount / open errors shown previously"
Not sure what else to try. (I'm learning all of this as I go from reading posts on this site.) Is there a way to adb sideload the recovery partition as I suspect that it is corrupt?
Sorry to be so long winded. I figured that too much info was better than not enough. Any help would be greatly appreciated.

So you can still access the recovery menu? That surely means that your tablet isn't bricked and if you can access the recovery, then you too must be able to access the bootloader. Power off your tablet and try to boot into fastboot by using power and volume -, volume + isn't necessary. Are you sure you have also installed the drivers for fastboot mode? Then try to flash the factory images using the guide here
http://forum.xda-developers.com/showthread.php?t=1907796
Sent from my Nexus 7 using xda app-developers app

Remcotjuuh said:
So you can still access the recovery menu? That surely means that your tablet isn't bricked and if you can access the recovery, then you too must be able to access the bootloader. Power off your tablet and try to boot into fastboot by using power and volume -, volume + isn't necessary. Are you sure you have also installed the drivers for fastboot mode? Then try to flash the factory images using the guide here
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
First - thanks for responding.
To answer your questions. No, I can't access the recovery menu. It doesn't matter how I boot - power button only, power button and vol-, vol+ or power, vol- only --- the device immediately boots to the android on his back with the red triangle. I don't get the normal "menu" where I can use the buttons to choose and select recovery mode. Sometimes there are the words "No command" under the android, sometimes there isn't. I can't get the tablet into fastboot mode.
When the device boots to the android + red triangle, the only thing I have been able to do is push power, Vol+ which gets me to the menu with
reboot system now
apply update from ADB
wipe date/factory reset
wipe cache partition
The "wipe" options fail with the text shown in my original post. If I select "apply update from ADB" it puts the device into ADB Sideload mode. (Not normal ADB mode.) My only option here is to ADB sideload images. I have tried sideloading the factory image. The image transferes, but it fails with a signature error and won't install. I have downloaded the image several times directly from google.
I have uninstalled and reinstalled the drivers a few times. I've used the article that you referenced, another article on this site and used the Wugs Nexus Root Toolkit to install the drivers. I know that my drivers were good originally as I used them to root the device.
Could the errors that I am seeing when I attempt the wipe options indicate a hardware issue? The device seems to be attempting to mount the cache and other partitions and can't.
Additional help is greatly appreciated. Thanks.

awhite2600 said:
First - thanks for responding.
To answer your questions. No, I can't access the recovery menu. It doesn't matter how I boot - power button only, power button and vol-, vol+ or power, vol- only --- the device immediately boots to the android on his back with the red triangle. I don't get the normal "menu" where I can use the buttons to choose and select recovery mode. Sometimes there are the words "No command" under the android, sometimes there isn't. I can't get the tablet into fastboot mode.
When the device boots to the android + red triangle, the only thing I have been able to do is push power, Vol+ which gets me to the menu with
reboot system now
apply update from ADB
wipe date/factory reset
wipe cache partition
The "wipe" options fail with the text shown in my original post. If I select "apply update from ADB" it puts the device into ADB Sideload mode. (Not normal ADB mode.) My only option here is to ADB sideload images. I have tried sideloading the factory image. The image transferes, but it fails with a signature error and won't install. I have downloaded the image several times directly from google.
I have uninstalled and reinstalled the drivers a few times. I've used the article that you referenced, another article on this site and used the Wugs Nexus Root Toolkit to install the drivers. I know that my drivers were good originally as I used them to root the device.
Could the errors that I am seeing when I attempt the wipe options indicate a hardware issue? The device seems to be attempting to mount the cache and other partitions and can't.
Additional help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
Is it under warranty?

xbt- said:
Is it under warranty?
Click to expand...
Click to collapse
No. It's about 10 months old.

Your cache partition is corrupt. Because cache is corrupt, your N7 probably can't boot anything but recovery. Did your N7 turn off while you were wiping cache or something?
Sent from my Nexus 7 using Tapatalk 4

Looks to me as if your boot / system is not working or corrupt. But you are writing you boot always to the dead Android, that's the bootloader mode and from there you should be able to flash a new system by fastboot. As long as you can go to bootloader there is hope for your device unless some hardware defect prevents you from flashing the system images. Try to install the fastboot drivers for your OS and then try to flash the system images. Probably you need to unlock your bootloader first.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Looks to me as if your boot / system is not working or corrupt. But you are writing you boot always to the dead Android, that's the bootloader mode and from there you should be able to flash a new system by fastboot. As long as you can go to bootloader there is hope for your device unless some hardware defect prevents you from flashing the system images. Try to install the fastboot drivers for your OS and then try to flash the system images. Probably you need to unlock your bootloader first.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
He has already said he can only boot into stock recovery, not bootloader.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 12:08 PM ---------- Previous post was at 12:07 PM ----------
Now I got myself thinking, the factory images fail, but what about an image for a custom recovery? Try to adb sideload yours from www.clockworkmod.com/rommanager. Is your bootloader unlocked?
Sent from my Nexus 7 using xda app-developers app

cmason37 said:
Your cache partition is corrupt. Because cache is corrupt, your N7 probably can't boot anything but recovery. Did your N7 turn off while you were wiping cache or something?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
The tablet froze during normal operation. (Checking GMail.) I simply turned it off...or so I though. When I looked over about 30 minutes later it was stuck on the white "Google" screen. I was able to boot into the normal bootloader at this point. My thoughts were to then select stock recovery and just wipe the cache. It's been in the "red triangle" and "No command" since then.

AndDiSa said:
Looks to me as if your boot / system is not working or corrupt. But you are writing you boot always to the dead Android, that's the bootloader mode and from there you should be able to flash a new system by fastboot. As long as you can go to bootloader there is hope for your device unless some hardware defect prevents you from flashing the system images. Try to install the fastboot drivers for your OS and then try to flash the system images. Probably you need to unlock your bootloader first.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The bootloader is unlocked. I was rooted with stock recovery. I have uninstalled and reinstalled drivers several times. I know for certain that the ADB drivers are installed. I don't have an easy way to confirm that the fastboot drivers are installed - but they should be.

Remcotjuuh said:
He has already said he can only boot into stock recovery, not bootloader.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 12:08 PM ---------- Previous post was at 12:07 PM ----------
Now I got myself thinking, the factory images fail, but what about an image for a custom recovery? Try to adb sideload yours from www.clockworkmod.com/rommanager. Is your bootloader unlocked?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I can try sideloading a custom recovery. I may have already tried this...I've tried so many things. I will try again.
The link that you provided points to .img downloads. I thought that ADB Sideload only worked with .zip images. Am I wrong?

awhite2600 said:
I can try sideloading a custom recovery. I may have already tried this...I've tried so many things. I will try again.
The link that you provided points to .img downloads. I thought that ADB Sideload only worked with .zip images. Am I wrong?
Click to expand...
Click to collapse
Remcotjuuh said:
He has already said he can only boot into stock recovery, not bootloader.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 12:08 PM ---------- Previous post was at 12:07 PM ----------
Now I got myself thinking, the factory images fail, but what about an image for a custom recovery? Try to adb sideload yours from www.clockworkmod.com/rommanager. Is your bootloader unlocked?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I tried sideloading the clockwork recovery. The .img file transfers. The Nexus 7 then displays:
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
:
followed by all of the E: can't mount/open cache/recovery messages as mentioned in my initial post.

Then I'm getting to a dead end here too. I guess you have tried flashing the bootloader too? And how about using the "flash-all.bat" in the factory images package?
Edit:
Maybe sideloading the zip from the images package that contains boot, system and recovery?
Sent from my Nexus 4 using xda app-developers app

Remcotjuuh said:
Then I'm getting to a dead end here too. I guess you have tried flashing the bootloader too? And how about using the "flash-all.bat" in the factory images package?
Edit:
Maybe sideloading the zip from the images package that contains boot, system and recovery?
Click to expand...
Click to collapse
I'm pretty sure that I've tried flashing the bootloader. When I try again (using adb sideload) I get the same signature verification failed message on the N7 that I did when attempting to sideload recovery images. I then get failed to mount cache messages.
I tried the flash-all.bat. Unfortunately that requires fastboot mode and the tablet won't go into fastboot mode. The batch file just sits waiting for the device to respond. Manually typing fastboot devices fails to list anything.
The only "response" that I seem to be able to get is when I put the tablet into sideload mode. I can type adb devices from a command prompt and get a reply with the serial number. The only other adb command that responds is adb sideload - which always reports signature failed on the tablet. Do you think this is a hardware issue?

awhite2600 said:
I'm pretty sure that I've tried flashing the bootloader. When I try again (using adb sideload) I get the same signature verification failed message on the N7 that I did when attempting to sideload recovery images. I then get failed to mount cache messages.
I tried the flash-all.bat. Unfortunately that requires fastboot mode and the tablet won't go into fastboot mode. The batch file just sits waiting for the device to respond. Manually typing fastboot devices fails to list anything.
The only "response" that I seem to be able to get is when I put the tablet into sideload mode. I can type adb devices from a command prompt and get a reply with the serial number. The only other adb command that responds is adb sideload - which always reports signature failed on the tablet. Do you think this is a hardware issue?
Click to expand...
Click to collapse
I have no idea whether this is a hardware issue, could be, could not be. I remember a thread in which someone had a similar problem, only he had only access to fastboot mode. He eventually fixed it by running the flash-all.bat dozens of times, very strange. So how about sideloading the zip containing boot, recovery and system? I haven't read you tried that. And how about adb pushing flashable zip to your device and flash them in recovery? You can try all kinds of zip, ROMs, recoveries. They do need to be signed because you only have access to the stock recovery I guess.

Remcotjuuh said:
I have no idea whether this is a hardware issue, could be, could not be. I remember a thread in which someone had a similar problem, only he had only access to fastboot mode. He eventually fixed it by running the flash-all.bat dozens of times, very strange. So how about sideloading the zip containing boot, recovery and system? I haven't read you tried that. And how about adb pushing flashable zip to your device and flash them in recovery? You can try all kinds of zip, ROMs, recoveries. They do need to be signed because you only have access to the stock recovery I guess.
Click to expand...
Click to collapse
I've tried sideloading the full factory image. That contains all of the boot, recovery and system images. Just like every other sideload that I've tried the file transfers from the PC. The tablet then reports that the signature verification fails. I've downloaded the factory image three times. I've done FC (file compare) from a command prompt and confirmed that none of the downloads are corrupt - they all match each other.
EDIT: I can't push a flashable zip as I can only adb sideload. I can't adb to just transfer a file. I also can't get into the recovery menu so I can't select a file to flash.
I agree that this is very strange. I've tried Googling the various "can't open / mount cache" message that I keep getting. I can't find anything about them. So this may be a very uncommon issue.
I appreciate your help. I'll keep trying different things. If anyone can think of anything else to try I would appreciate any advice. :fingers-crossed:

awhite2600 said:
I've tried sideloading the full factory image. That contains all of the boot, recovery and system images. Just like every other sideload that I've tried the file transfers from the PC. The tablet then reports that the signature verification fails. I've downloaded the factory image three times. I've done FC (file compare) from a command prompt and confirmed that none of the downloads are corrupt - they all match each other.
EDIT: I can't push a flashable zip as I can only adb sideload. I can't adb to just transfer a file. I also can't get into the recovery menu so I can't select a file to flash.
I agree that this is very strange. I've tried Googling the various "can't open / mount cache" message that I keep getting. I can't find anything about them. So this may be a very uncommon issue.
I appreciate your help. I'll keep trying different things. If anyone can think of anything else to try I would appreciate any advice. :fingers-crossed:
Click to expand...
Click to collapse
No problem. Just be persistent and try sideloading, and maybe adb pushing, the different kinds of images/.zips. Maybe you'll be lucky and magically succeed just like the other guy did. I guess this is everything I could advise you. Good luck.

Fastboot is working only when you are in bootloader mode, when you are in recovery or in "normal" operating mode only adb will work. The command is normally located in the sdk/platform-tools directory of the sdk and I suppose you have the latest android SDK installed.
Btw. for me it makes absolutely no sense that the tablet is booting to recovery directly, because the bootloader is loaded and started before, Only from there you are able to go to recovery, i.e. if recovery mode is working, bootloader must work, too.
To recover your system: go to bootloader mode and get fastboot running, then get the system image and extract all files and do the following:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system -w
fastboot flash system system.img
fastboot reboot
this should be sufficient. If you want to be sure you can also do
fastboot reboot recovery
and do a system wipe from there. And after that reboot into your system. Good luck!
@Remcotjuuh: it's better to use fastboot instead of adb, because you are one level below, i.e. if your recovery is not working correctly, adb will fail while fastboot does not depend on a working adb process.

AndDiSa said:
and do a system wipe from there. And after that reboot into your system. Good luck!
@Remcotjuuh: it's better to use fastboot instead of adb, because you are one level below, i.e. if your recovery is not working correctly, adb will fail while fastboot does not depend on a working adb process.
Click to expand...
Click to collapse
I know, but he has clearly said multiple times that he cannot access the bootloader, although I find this very strange too...

Sony xperia s bricked
Remcotjuuh said:
So you can still access the recovery menu? That surely means that your tablet isn't bricked and if you can access the recovery, then you too must be able to access the bootloader. Power off your tablet and try to boot into fastboot by using power and volume -, volume + isn't necessary. Are you sure you have also installed the drivers for fastboot mode? Then try to flash the factory images using the guide here
http://forum.xda-developers.com/showthread.php?t=1907796
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i'm experiencing a similar problem with my phone. i rooted my phone today (using http://forum.xda-developers.com/showthread.php?t=2327473) and it was running fine, but i installed an application from the play store called [Root] Developer tools to allow me to load up recovery boot. i gave it permission but when i tried turning my phone on it just stays blank. ive tried the hard reset (up+power button) but all that happens is my phone vibrates 3 times and a green light flashes. please help

[Q] Trying to restore recovery/OS but can't put any files on it!

I have an LG G2 D800 with Cyanogenmod on it right now, and Clockwork Mod for my recovery. When booting into CWM, it gives me these errors:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Also, when in the OS (in Cyanodenmod), when I plug it in, it won't let me drag any files onto it. The Google Play Store keeps on crashing too. What I want to do is just flash a new recovery, then wipe away CM and start it again. It's kind of hard right now though because I have no idea how I can get the files on my phone to do this, any help will be appreciated.

Bump :/

hi,
Recovery:
http://forum.xda-developers.com/showthread.php?t=2449670
OR
You can try to download goomanager :http://goo.im/devs/s0updev/goomanager with your phone's browser
File transfer:
ADB sideload http://forum.xda-developers.com/showthread.php?t=2559200
OR u can try the Wireless storage option on your phone if cm have it ....:http://forums.androidcentral.com/lg-g2/317028-wireless-storage-lg-g2.html
good luck

x10tom said:
hi,
Recovery:
http://forum.xda-developers.com/showthread.php?t=2449670
OR
You can try to download goomanager :http://goo.im/devs/s0updev/goomanager with your phone's browser
File transfer:
ADB sideload http://forum.xda-developers.com/showthread.php?t=2559200
OR u can try the Wireless storage option on your phone if cm have it ....:http://forums.androidcentral.com/lg-g2/317028-wireless-storage-lg-g2.html
good luck
Click to expand...
Click to collapse
what the function TWRP???

TWRP is a recovery .
u can manage it with twrp manager under android, and it have " adb sideload" in the Advanced menu
current is 2.7.0.0
i saw that for your recovry too: http://forum.xda-developers.com/showthread.php?t=2715496

x10tom said:
hi,
Recovery:
http://forum.xda-developers.com/showthread.php?t=2449670
OR
You can try to download goomanager :http://goo.im/devs/s0updev/goomanager with your phone's browser
File transfer:
ADB sideload http://forum.xda-developers.com/showthread.php?t=2559200
OR u can try the Wireless storage option on your phone if cm have it ....:http://forums.androidcentral.com/lg-g2/317028-wireless-storage-lg-g2.html
good luck
Click to expand...
Click to collapse
Trying to download anything through my browser just makes the browser crash, I'll try the first method though, thanks

x10tom said:
hi,
Recovery:
http://forum.xda-developers.com/showthread.php?t=2449670
OR
You can try to download goomanager :http://goo.im/devs/s0updev/goomanager with your phone's browser
File transfer:
ADB sideload http://forum.xda-developers.com/showthread.php?t=2559200
OR u can try the Wireless storage option on your phone if cm have it ....:http://forums.androidcentral.com/lg-g2/317028-wireless-storage-lg-g2.html
good luck
Click to expand...
Click to collapse
I keep getting this error: http://i.imgur.com/h2SnlNn.png

did u tryied to open cmd with administrator's rights?
did u tryied option 2?:
adb push openrecovery-twrp-2.6.3.2-g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
adb shell
(IF YOU DONT SEE A # prompt, type su to get it.)
cd /data/local/tmp
dd if=/data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
adb reboot recovery

x10tom said:
did u tryied to open cmd with administrator's rights?
did u tryied option 2?:
adb push openrecovery-twrp-2.6.3.2-g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
adb shell
(IF YOU DONT SEE A # prompt, type su to get it.)
cd /data/local/tmp
dd if=/data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
adb reboot recovery
Click to expand...
Click to collapse
Yeah I tried both methods. Does this have anything to do with it? When I type in 'adb devices', I see my phone, but when I'm in adb shell, when I type in 'adb devices', it doesn't find anything.
EDIT: I found out I was able to install goomanager onto my phone, looks like I'll try that method instead
EDIT again: Looks like goomanager can't find the recovery to install on my phone, and I've tried installing both flashify and rashr, but it won't let me, ugh this is such a pain, I thought I was close

Is your "usb debuging" on?under developpement setting?
i found an automated script for adb http://forum.xda-developers.com/showthread.php?t=2472223
Adb should work
If not ,and if any apk can flash your recovery, u have to back to full stock
http://forum.xda-developers.com/showthread.php?t=2432476.
Then re root,reflash recovery etc....
How did u flash your strange recovery?do same but with twrp.img or a philz_touch.img
Look for thread about both, there is some 'how to install'.
I hope to be clear my language isnt english.

x10tom said:
Is your "usb debuging" on?under developpement setting?
i found an automated script for adb http://forum.xda-developers.com/showthread.php?t=2472223
Adb should work
If not ,and if any apk can flash your recovery, u have to back to full stock
http://forum.xda-developers.com/showthread.php?t=2432476.
Then re root,reflash recovery etc....
How did u flash your strange recovery?do same but with twrp.img or a philz_touch.img
Look for thread about both, there is some 'how to install'.
I hope to be clear my language isnt english.
Click to expand...
Click to collapse
Thank you so much, the BAT file worked! But now I still have the same problems I was having with CWM, as in that my cache won't wipe, and my USB won't mount either.
EDIT: Nvm, wiping the cache in TWRP fixed it, I think I can figure out what to do from here on out, THANK YOU SO MUCH THOUGH

you are welcome

CWM error cant mount-open cache/recovery

Guys, i just bought an used Nexus 4 and after flashing the cwm recovery and trying to boot in the recovery mode i get a few errors stating:
cant mount cache/recovery
cant open cache/recovery
I notice there are a few topics about this and the solution is to adb push or something, but the adb push command wont work in recovery for me, says device not found and i know my drivers are correct since i can fastboot and do stuff.
I actually got the device running perfectly flashing Chroma via sideload, but cwm wont work! I cant access anything from inside cwm... I also tried twrp and no luck.
I also tried a full original image flash, no luck
Can you please help me with this?
Thanks

luizffgarcia said:
Guys, i just bought an used Nexus 4 and after flashing the cwm recovery and trying to boot in the recovery mode i get a few errors stating:
cant mount cache/recovery
cant open cache/recovery
I notice there are a few topics about this and the solution is to adb push or something, but the adb push command wont work in recovery for me, says device not found and i know my drivers are correct since i can fastboot and do stuff.
I actually got the device running perfectly flashing Chroma via sideload, but cwm wont work! I cant access anything from inside cwm... I also tried twrp and no luck.
I also tried a full original image flash, no luck
Can you please help me with this?
Thanks
Click to expand...
Click to collapse
when you flashed the factory image it should have brought you back erasing and replacing everything. In fastboot did you flash the bootloader, radio, system partitions (.IMG), recovery partition, and so on.? If not try this steps guide http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312/page194 its pretty detailed but it helped me after I wiped everything off my phone trying to learn. If that's a bit too much then try searching for wugfresh nexus toolkit. Both will wipe everything from your nexus then replace it and should get everything going

Zenfone 5(A501CG) unable to flash via adb sideload

Recently I had an update from ASUS and at that time I had root on my device...So I guess my phone got brick due to updating while having a rooted device...I have tried all the steps of flashing via adb..Did "fastboot flash boot boot.img" , "fastboot flash recovery recovery.img"...All goes well...
Now the problem is when I get into bootloader(Power + vol up)/recovery/apply update from ADB from my device and on my PC "adb sideload filename.zip" it just does nothing...My cmd just waits and same goes to my device all it is written are
E:Can't open /tmp/update-script.log
Now send the package you want to apply
to the device with adb sideload(filename)"...
EDIT-"adb devices" doesn't recognize my device only "fastboot devices" does
I hope someone could help or maybe lead me to a post which has the same problem...Or maybe I need to send my phone to Asus Service Center for this issue...My bet now if this doesn't works I would try to flash some custom ROM maybe

First step backup u r data by twrp custome recovery..then go to link
www.google.co.in/url?q=http://www.w...ggOMAE&usg=AFQjCNHyTiR4lWYSzNkTaJO83PBJIf9Buw
U r problem will solved
NOTE: U MUST RETURN TO U R STOCK ROM THEN APLLY KITKAT VER 2.20.40.53 THEN LOLLIPOP 3.20.40.52 THEN GO 30.20.40.78...

Same problem with the op. i'll follow the steps u give in the link but it still failed. its says (E: Can't mount /cache/recovery/log), (E: Can't open /cache/recovery/log), (E: failed to mount /cache), and it keeps repeating for (/cache/recovery/last_log), (/cache/recovery/last_insta). So, how do i fix it? anybody knows?

mrsajlast said:
Same problem with the op. i'll follow the steps u give in the link but it still failed. its says (E: Can't mount /cache/recovery/log), (E: Can't open /cache/recovery/log), (E: failed to mount /cache), and it keeps repeating for (/cache/recovery/last_log), (/cache/recovery/last_insta). So, how do i fix it? anybody knows?
Click to expand...
Click to collapse
U reset data and cache ??? From fastboot mode

mrsajlast said:
Same problem with the op. i'll follow the steps u give in the link but it still failed. its says (E: Can't mount /cache/recovery/log), (E: Can't open /cache/recovery/log), (E: failed to mount /cache), and it keeps repeating for (/cache/recovery/last_log), (/cache/recovery/last_insta). So, how do i fix it? anybody knows?
Click to expand...
Click to collapse
yasin0005 said:
U reset data and cache ??? From fastboot mode
Click to expand...
Click to collapse
i have similar problem with mrsajlast, and reset data and cache... how do i fix it ?? please help

Phone stuck on erasing boot loop

Hello guys, I ran into some trouble by trying to reset my phone to stock firmware. I followed this guide https://forum.xda-developers.com/showthread.php?t=2759495 but with the moto e4 firmware, now it bootloops to erasing and bad key. Please help, it doesnt let me boot into recovery

frederickrl said:
Hello guys, I ran into some trouble by trying to reset my phone to stock firmware. I followed this guide https://forum.xda-developers.com/showthread.php?t=2759495 but with the moto e4 firmware, now it bootloops to erasing and bad key. Please help, it doesnt let me boot into recovery
Click to expand...
Click to collapse
Update, I was able to boot into twrp, currently attemtping to flash a rom

similar problem: recovery loop
frederickrl said:
Update, I was able to boot into twrp, currently attemtping to flash a rom
Click to expand...
Click to collapse
Hello,
this is my situation:
- switchin-on my new moto e4 (XT1762)
- boot into recovery (TWRP)
- in TWRP, I am able to 'work', i.e. install LineageOS 15.1 (this is my main goal)
--- I WIPE
--- I INSTALL the lineage ZIP file (lineage 15.1 20180310 unofficial woods
--- I REBOOT
BUT, sadly, the reboot is done again into TWRP.
The installation of lineageos did not report any error.
How can I check, that what I've installed so far (TWRP and magisk) is correct and working?
Did I forget something? E.g. do I have to install GAPPS as well? Or Magisk? Or SUperSU?
Shall I try another custom ROM? Or another version of lineageOS? (Oh, yes, I tried Lineageos 15.0, but I got 'ZIP error'.
Thanks for your help!

Fussloseskriechtier said:
Hello,
this is my situation:
- switchin-on my new moto e4 (XT1762)
- boot into recovery (TWRP)
- in TWRP, I am able to 'work', i.e. install LineageOS 15.1 (this is my main goal)
--- I WIPE
--- I INSTALL the lineage ZIP file (lineage 15.1 20180310 unofficial woods
--- I REBOOT
BUT, sadly, the reboot is done again into TWRP.
The installation of lineageos did not report any error.
How can I check, that what I've installed so far (TWRP and magisk) is correct and working?
Did I forget something? E.g. do I have to install GAPPS as well? Or Magisk? Or SUperSU?
Shall I try another custom ROM? Or another version of lineageOS? (Oh, yes, I tried Lineageos 15.0, but I got 'ZIP error'.
Thanks for your help!
Click to expand...
Click to collapse
I imagine you are having the same problem that I was having. This is what I think happened, there is a particular partition which TWRP fails to erase, if this is the case I believe you are able to boot into the device by hitting start in the bootloader, hold volume down and power then select start. Tell me how it goes

TWRP loop
frederickrl said:
I imagine you are having the same problem that I was having. This is what I think happened, there is a particular partition which TWRP fails to erase, if this is the case I believe you are able to boot into the device by hitting start in the bootloader, hold volume down and power then select start. Tell me how it goes
Click to expand...
Click to collapse
Thanks for this hint, frederick.
Unfortunately, it did not work.
I rebooted to bootloader mode, then I pushed 'DOWN' and 'POWER' for several seconds - but I could not select anything - display was switched off and the device rebooted to TWRP again.
That's strange, because yesterday I've got this 'MENUE', when pushing 'DOWN'&'POWER' for selecting FACTORY, RECOVERY, ... but this does not appear now.
More facts (it might help):
- After switching on the the device, I get this 'Orange state' message.
Perhaps any other hints?

Fussloseskriechtier said:
Thanks for this hint, frederick.
Unfortunately, it did not work.
I rebooted to bootloader mode, then I pushed 'DOWN' and 'POWER' for several seconds - but I could not select anything - display was switched off and the device rebooted to TWRP again.
That's strange, because yesterday I've got this 'MENUE', when pushing 'DOWN'&'POWER' for selecting FACTORY, RECOVERY, ... but this does not appear now.
More facts (it might help):
- After switching on the the device, I get this 'Orange state' message.
Perhaps any other hints?
Click to expand...
Click to collapse
I have no other recommendations as to what to do. Just flash stock firmware with rsdlite and everything will be back to normal, if you have any data that you need to back up you can use TWRP to transfer the files to a PC

Fussloseskriechtier said:
Thanks for this hint, frederick.
Unfortunately, it did not work.
I rebooted to bootloader mode, then I pushed 'DOWN' and 'POWER' for several seconds - but I could not select anything - display was switched off and the device rebooted to TWRP again.
That's strange, because yesterday I've got this 'MENUE', when pushing 'DOWN'&'POWER' for selecting FACTORY, RECOVERY, ... but this does not appear now.
More facts (it might help):
- After switching on the the device, I get this 'Orange state' message.
Perhaps any other hints?
Click to expand...
Click to collapse
In twrp select reboot bootloader. In bootloader, tap volume until you see "start". Tap power. Do not try holding buttons together in bootloader. It doesn't do anything. Single taps.

madbat99 said:
In twrp select reboot bootloader. In bootloader, tap volume until you see "start". Tap power. Do not try holding buttons together in bootloader. It doesn't do anything. Single taps.
Click to expand...
Click to collapse
After "REBBOT BOOTLOADER" in TWRP, I get a black screen, where (on the very bottom) there are two lines: => FASTBOOT mode
=> device unlocked
Tapping or holding the volume&power buttons does not work in this state.
As mentioned before, by any reason I do not have this nice menue anymore, the one with RECOVERY, START, ...
So this could be the problem, right? Is my bootloader not working properly? Which part is telling the device to startup either in TWRP (=recovery) or into the Bootloader/System?
Mmmmh....

Fussloseskriechtier said:
After "REBBOT BOOTLOADER" in TWRP, I get a black screen, where (on the very bottom) there are two lines: => FASTBOOT mode
=> device unlocked
Tapping or holding the volume&power buttons does not work in this state.
As mentioned before, by any reason I do not have this nice menue anymore, the one with RECOVERY, START, ...
So this could be the problem, right? Is my bootloader not working properly? Which part is telling the device to startup either in TWRP (=recovery) or into the Bootloader/System?
Mmmmh....
Click to expand...
Click to collapse
Fastboot mode is bootloader. Why the options aren't there I couldn't tell you. I see you flashed a rom for woods. Do you have the mediatek version? Hopefully you didn't flash wood stuff on a Perry device. Bootloader may be different. I have Qualcomm. Was that option ever there in fastboot mode?
This is how to fix the recovery loop. And possibly boot you in to whatever is left of your os.

madbat99 said:
Fastboot mode is bootloader. Why the options aren't there I couldn't tell you. I see you flashed a rom for woods. Do you have the mediatek version? Hopefully you didn't flash wood stuff on a Perry device. Bootloader may be different. I have Qualcomm. Was that option ever there in fastboot mode?
This is how to fix the recovery loop. And possibly boot you in to whatever is left of your os.
Click to expand...
Click to collapse
Thanks again for your hints!
First of all, my device variant is XT1762, i.e. woods. I did not use PERRY software.
The bootloader options (RECOVERY MODE, FACTORY MODE, etc.) were there, but it seems I've somehow broken this peace of code... I believe this is the reason of my problems. Unfortunately I do not understand the Android boot sequence...
However, I tried >> fastboot erase misc << via terminal:
result:
erasing 'misc'...
FAILED (remote: partition table doesn't exist)
finished. total time 0.009s
I double checked it vie file manager in TWRP: there is no MISC folder.
It seems, my only option is to go back to stock ROM... :crying:

Fussloseskriechtier said:
Thanks again for your hints!
First of all, my device variant is XT1762, i.e. woods. I did not use PERRY software.
The bootloader options (RECOVERY MODE, FACTORY MODE, etc.) were there, but it seems I've somehow broken this peace of code... I believe this is the reason of my problems. Unfortunately I do not understand the Android boot sequence...
However, I tried >> fastboot erase misc << via terminal:
result:
erasing 'misc'...
FAILED (remote: partition table doesn't exist)
finished. total time 0.009s
I double checked it vie file manager in TWRP: there is no MISC folder.
It seems, my only option is to go back to stock ROM... :crying:
Click to expand...
Click to collapse
I think the partitions are different in mtk version. But I would try flashing stock.

I have exactly the same problem after trying to flash lineage 14.1 to my XT1762.
Unfortunately I have only a TWRP Backup of my stock system before the flash and recovering that didn't fix the problem.

Fussloseskriechtier said:
Perhaps any other hints?
Click to expand...
Click to collapse
MiGri said:
I have exactly the same problem after trying to flash lineage 14.1 to my XT1762.
Unfortunately I have only a TWRP Backup of my stock system before the flash and recovering that didn't fix the problem.
Click to expand...
Click to collapse
I know what a pain in the ass my Perry variant was just to get the root going, so I can just imagine your frustration.
Did you guys take the update they're pushing out on the phones? Check. Some of the updates might be forced or you may accidentally said Okay and didn't realize it- that could be the reason why you're having trouble. The significant other got an update on the E4, and now can't do root.

I was able to get my phone back to work using https://forum.xda-developers.com/moto-e4/development/rom-original-stock-firmware-woods-twrp-t3766902

Stock ROM used to repair bootloader
Articul8Madness said:
I know what a pain in the ass my Perry variant was just to get the root going, so I can just imagine your frustration.
Did you guys take the update they're pushing out on the phones? Check. Some of the updates might be forced or you may accidentally said Okay and didn't realize it- that could be the reason why you're having trouble. The significant other got an update on the E4, and now can't do root.
Click to expand...
Click to collapse
Hello!
In the meantime I actually deleted everything and flashed the Stock ROM on my XT1762.
After that, my Bootloader menue (RECOVERY MODE, FACTORY MODE, START, ...) appeared again...
I felt lucky and started the whole procedure again: use TWRP, backup, delete Cache, Flash custom ROM, delete Cache, restart... and finally, I got lineageOS 15.1 and CrDroid running on my phone.
Now I use CrDroid, because LineageOS 15.1 did not Support my SIM Card... ? However, I am happy with CrDroid: fast, slim, nice looking, ...
So in the end, it seems that I deleted a specific part in my Flash which caused the "boot Loop". But I could repair it by flashing the Stock ROM again.
Thanks guys, you're doing a good Job!
Buy!

Fussloseskriechtier said:
Hello!
In the meantime I actually deleted everything and flashed the Stock ROM on my XT1762.
After that, my Bootloader menue (RECOVERY MODE, FACTORY MODE, START, ...) appeared again...
I felt lucky and started the whole procedure again: use TWRP, backup, delete Cache, Flash custom ROM, delete Cache, restart... and finally, I got lineageOS 15.1 and CrDroid running on my phone.
Now I use CrDroid, because LineageOS 15.1 did not Support my SIM Card... ? However, I am happy with CrDroid: fast, slim, nice looking, ...
So in the end, it seems that I deleted a specific part in my Flash which caused the "boot Loop". But I could repair it by flashing the Stock ROM again.
Thanks guys, you're doing a good Job!
Buy!
Click to expand...
Click to collapse
I'm also stuck in boot loop... What directories/files did you delete? Have backup of stock rom, but restore fails:
This /data backup was made with f2fs file system! The backup may not boot unless you change back to f2fs
Failed to mount /data (Invalid argument)
TWRP says that file system of /data is ext4. Not possible to change or repair the file system in TWRP with Wipe / Advanced wipe / Repair or change file system. Result:
Error changing file system
or
/sbin/e2fsck -fp /dev/block/mmcblk0p27 process ended with error: 8
Phone is always starting in TWRP ending with:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
In terminal no problem to create (mkdir) and delete directories.
Flashing of lineage 14.1 or 15.1 for woods ends also with:
Failed to mount '/data' (Invalid argument)
This command in TWRP terminal didn't work:
fastboot erase misc
erasing 'misc'...
FAILED (remote: Partition table doesn't exist)
There is no misc folder.
Any ideas?
Thank you in advance!

pancobe said:
I'm also stuck in boot loop... What directories/files did you delete? Have backup of stock rom, but restore fails:
This /data backup was made with f2fs file system! The backup may not boot unless you change back to f2fs
Failed to mount /data (Invalid argument)
TWRP says that file system of /data is ext4. Not possible to change or repair the file system in TWRP with Wipe / Advanced wipe / Repair or change file system. Result:
Error changing file system
or
/sbin/e2fsck -fp /dev/block/mmcblk0p27 process ended with error: 8
Phone is always starting in TWRP ending with:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
In terminal no problem to create (mkdir) and delete directories.
Flashing of lineage 14.1 or 15.1 for woods ends also with:
Failed to mount '/data' (Invalid argument)
This command in TWRP terminal didn't work:
fastboot erase misc
erasing 'misc'...
FAILED (remote: Partition table doesn't exist)
There is no misc folder.
Any ideas?
Thank you in advance!
Click to expand...
Click to collapse
Just flash stock firmware with rsdlite, it's the simplest way to go. Then if you'd like flash your rom

frederickrl said:
Just flash stock firmware with rsdlite, it's the simplest way to go. Then if you'd like flash your rom
Click to expand...
Click to collapse
Thank you for the hint on rsdlite, didn't know the program! Unfortunately I have two problems, have only access to an old XP box (I'm normally on a mac), and rsdlite doesn't recognise the phone, driver problem presumably... And the program doesn't recognise the format of the backup I made with TWRP...
Is it possible to repair the file system on the phone via terminal? Or to delete parts of the system safely and reinstall the stock system? The other guy apparently did something like that. Or to unpack a custom rom and place the parts via terminal so it can install on next boot?
Thank you!

Did following check:
mount /data
mount: '/dev/block/mmcblk0p27'->'/data': Invalid argument
e2fsck -n /dev/block/mmcblk0p27
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p27
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Would it be safe to rmdir /data and mkdir /data ?
Thanks...

pancobe said:
Thank you for the hint on rsdlite, didn't know the program! Unfortunately I have two problems, have only access to an old XP box (I'm normally on a mac), and rsdlite doesn't recognise the phone, driver problem presumably... And the program doesn't recognise the format of the backup I made with TWRP...
Is it possible to repair the file system on the phone via terminal? Or to delete parts of the system safely and reinstall the stock system? The other guy apparently did something like that. Or to unpack a custom rom and place the parts via terminal so it can install on next boot?
Thank you!
Click to expand...
Click to collapse
Rsdlite is not meant to install your twrp backup. It's for installing the official firmware package. And you need to install moto drivers of course.