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
Related
EDIT:
In my humble opinion, there's a new blade around, since all the sources for recoveries on english websites don't work with my 256mb "new" blade (jan 2012), while many people using older chinese blades from china unicom can use all the software found online.
flashing re regular cw with rom manager, adb won't work and give errors later shown in this post.
the only recovery i found that will actually work and let me install another rom is a recovery i found on a chinese forum.
downolad this recovery: http://dl.dbank.com/c0sw12amzu
chinese forum: http://bbs.anzhi.com/forum.php?mod=v...fromuid=423904
in that forum u can't see the download link because you have to log in and write a message in that topic in order to see the link.
to flash this recovery go to this thread, page 3 first post and follow the instructions from matt4321.
I am waiting for someone to try with "new blades" with the same problem as mine.
ORIGINAL POST:
hi everybody, i tried to look also in the forum with the search and i didn't find anything relevant...
i have the blade from china unicom, i rooted it and installed cw. everything was almost smooth (i downloaded the wrong z4root, but then i got it right).
when i tried to make a backup or anything else vis CW it shows me this:
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/command
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
basically i can't do anything. i can't even make a factory reset.
what went wrong?
thanks to anybody that can help me.
Flash cwm using rom manager again
i tried but nothing... :/
thanks by the way.
Does anyone knows how to install CW via adb? i found how to do it here http://forum.xda-developers.com/showthread.php?t=852905 but i have no idea how to download the latest cw for my china uni blade.
thanks if anyone has some hints!
Are you sure you installed the right version of CWM according to your phone's GEN?
Sent from my Blade using XDA app
well, i guess so, my phone is gen2. i installed cw from rom manager, i just selected zte blade. i tried to reinstall cw, to reinstall rom manager, tried to dowload cw with wifi or data internet connection, same result as 1st post, or either like phone stuck on start screen when booting into cw (but the phone was working).
btw, i am using the latest cw.
i wonder what's wrong with my zte :/
Do not use CWM's latest verson
tetora said:
well, i guess so, my phone is gen2. i installed cw from rom manager, i just selected zte blade. i tried to reinstall cw, to reinstall rom manager, tried to dowload cw with wifi or data internet connection, same result as 1st post, or either like phone stuck on start screen when booting into cw (but the phone was working).
btw, i am using the latest cw.
i wonder what's wrong with my zte :/
Click to expand...
Click to collapse
I guess that there's nothing wrong with your device. My Blade is similar to yours (256MB RAM) and the last version of CWM does not work: I even can't enter recovery mod with it. The solution is to use CWM version before the last one (5.0.1.0 I think).
You can easily install it via ROM Manager: Just go to the last option (CWM all versions and select the desired one).
[]'s
Ah, the Best rom so far to our stripped Blade in my opinion is Squadzone's CM7.2.0 RC 5.6
5.0.1.0 isn't working... could you please check which one you have on your blade?
btw thanks, i didn't see that option in ROM Manager!
i am trying with the 5.0.0.8, just in case... i hope it will work...
edit: no, it doesn't work... :/ i'll try with the previous one. with 5.0.0.8 i can't even boot in cw.
Anyone has a tip? it really doesn't work. i really have no idea how to do it via adb, if this could fix the problem.
tetora said:
Anyone has a tip? it really doesn't work. i really have no idea how to do it via adb, if this could fix the problem.
Click to expand...
Click to collapse
I guess the only option for you is to try Amon RA recovery. I don't even know if it still exists. Check out the CM wiki regarding flashing. It might be there.
Sent from my Blade using XDA app
---------- Post added at 06:30 PM ---------- Previous post was at 06:18 PM ----------
You can follow this if you want but the versions of recoveries are old.
http://forum.xda-developers.com/showthread.php?t=915143
Sent from my Blade using XDA app
the problem is that i can't enter recovery mode (i can, but i can't use it) and i can't get the "green android" screen.
to my extent, i have no way to write anything via usb onto the phone. am i right?
i tried all of the cw versions, but all of them give me the same error i posted in the 1st post...
I think CWM can't find your root. Very weird issue. Will check and get back.
Sent from my ZTE Blade using XDA app
Try rooting the phone again! I had problems with my sisters blade when Z4root wouldn't perm root, only temp root (even if i pressed the perm root button).
Use zergRush to root again (or something similar) then flash CWM again through fastboot or adb
z4root actually works, apps that need SU enabled work also when i restart the phone.
zergrush doesn't work. everything seems fine but in the end the phone is not rooted.
plus, i can't use fastboot or adb since the recovery mode does not work, so i have to reinstall it from rom manager.
and yes, i tried to root it again, but with z4root, but nothing.
You should be able use adb with the phone on. Make sure USB debugging is enabled. Install drivers, use adb to reboot into bootloader, then flash cwm through there. Maybe there is a problem with the way rom manager is trying to flash cwm.
Sent from my ZTE-BLADE using Tapatalk 2
tetora said:
hi everybody, i tried to look also in the forum with the search and i didn't find anything relevant...
i have the blade from china unicom, i rooted it and installed cw. everything was almost smooth (i downloaded the wrong z4root, but then i got it right).
when i tried to make a backup or anything else vis CW it shows me this:
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/command
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
basically i can't do anything. i can't even make a factory reset.
what went wrong?
thanks to anybody that can help me.
Click to expand...
Click to collapse
it could come from root access or you have made a bad manipulation, I have got a similar problem, my recovery has been deleted after have tried to flash one .
thanks matt, but I still can't do anything. adb command works from command line, but fastboot is not working.
the device is recognised when i type "adb devices" when rebooting in recovery, but any commands starting with fastboot give back an error "fastboot is not recognised as a command ..."
maybe it's the way i added fastboot. i found the fastboot.exe and put in the android-sdk\tools folder. even if i restart the pc it's still not recognised.
but if i go in the folder where fastboot.exe is it works, well, kinda, because "fastboot devices" gives me nothing. "fastboot \?" gives me the list of every option i can use, but i can't use them.
i guess it is like this because when i reboot the pc says there are no drivers for the phone. i actually tried to give him the drivers that come with the android sdk and the ones from zte, but both of them do not work. I guess that with the right drivers it will work, but i have no idea where to get them. am i right?
thanks for the patience.
i almost forgot, usb debug is enabled.
i found some drivers here: http://android.modaco.com/topic/319156-winxp7-zte-blade-drivers-and-adb/ and now it's recognised from the pc as "android bootloader interface", but fastboot is not working, it doesn't see the device. :/
tetora said:
thanks matt, but I still can't do anything. adb command works from command line, but fastboot is not working.
the device is recognised when i type "adb devices" when rebooting in recovery, but any commands starting with fastboot give back an error "fastboot is not recognised as a command ..."
maybe it's the way i added fastboot. i found the fastboot.exe and put in the android-sdk\tools folder. even if i restart the pc it's still not recognised.
but if i go in the folder where fastboot.exe is it works, well, kinda, because "fastboot devices" gives me nothing. "fastboot \?" gives me the list of every option i can use, but i can't use them.
i guess it is like this because when i reboot the pc says there are no drivers for the phone. i actually tried to give him the drivers that come with the android sdk and the ones from zte, but both of them do not work. I guess that with the right drivers it will work, but i have no idea where to get them. am i right?
thanks for the patience.
i almost forgot, usb debug is enabled.
Click to expand...
Click to collapse
Okay so it seems the issue is that fastboot won't work and there's some drivers issue!? I remember a while back when i had issues with getting fastboot to work with my ZTE blade, I can't remember where i got the drivers from but recently got my Xoom and the drivers installed from the device wouldn't work, so used koushs drivers for his tether app which worked, give those drivers a go but for ZTE of course, http://www.clockworkmod.com/tether/drivers
you could also try flashing CWM via adb which is what I used to do when I had issues with fastboot, i've got the instructions and commands saved on my computer if you want me to upload them? but then again a google search would probably produce the same results but i've used these before and know they work.
EDIT: also after rereading what you said and saying fastboot isn't recognized as a command (sorry if this is a dumb point) put when in the command prompt you are changing the directory to where the fastboot file is located right?!
as I understand, adb can't flash the recovery, only fastboot.
the drivers are working, windows xp recognise the phone both in recovery and in bootloader mode.
yes, i am running fastboot from the path fastboot.exe is located.
with google the only thing i get is rebooting via adb into bootloader and use fastboot...
so far no luck...
Kit-Kat OTA came out for my Nexus 4 today and I went to apply it but during the install it errored out and the phone subsequently enters a boot loop. I can get into a recovery shell and attempt to push the update via sideload but I get an error:
Symlinks and permissions...
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted
I'm 99% sure there's a binary in /system/xbin/ or /system/bin/ thats set immutable (chattr +i) causing this to fail but I can't launch an adb shell from recovery to fix this. Can anybody help me out here?
ykram said:
Kit-Kat OTA came out for my Nexus 4 today and I went to apply it but during the install it errored out and the phone subsequently enters a boot loop. I can get into a recovery shell and attempt to push the update via sideload but I get an error:
Symlinks and permissions...
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted
I'm 99% sure there's a binary in /system/xbin/ or /system/bin/ thats set immutable (chattr +i) causing this to fail but I can't launch an adb shell from recovery to fix this. Can anybody help me out here?
Click to expand...
Click to collapse
Are you using stock recovery to do this?
You pretty much explained why, but if you had rooted the phone it could fail due to other reasons too.
If you have an unlocked bootloader then you can boot TWRP (not install, but boot by fastboot boot twrp.img), it have its own terminal and you can go in and chattr -i that file.
Or with unlocked bootloader you just "fastboot format system" and flash the full system.img from the factory image. Or use TWRP to flash a stock rom.
I don't see how else you could have ran a chattr command to the /system without root. But without an unlocked bootloader you pretty much only have the choice of factory reset or unlock the bootloader in which both will wipe all data. But I'm pretty sure beside fastboot erase and format, not even factory reset in recovery could get rid of an immutable file. There is no adb access in stock recovery beside adb sideload signed packages (otherwise every android phones will be very unsecure).
eksasol said:
Are you using stock recovery to do this?
You pretty much explained why, but if you had rooted the phone it could fail due to other reasons too.
If you have an unlocked bootloader then you can boot TWRP (not install, but boot by fastboot boot twrp.img), it have its own terminal and you can go in and chattr -i that file.
Or with unlocked bootloader you just "fastboot format system" and flash the full system.img from the factory image. Or use TWRP to flash a stock rom.
I don't see how else you could have ran a chattr command to the /system without root. But without an unlocked bootloader you pretty much only have the choice of factory reset or unlock the bootloader in which both will wipe all data. But I'm pretty sure beside fastboot erase and format, not even factory reset in recovery could get rid of an immutable file. There is no adb access in stock recovery beside adb sideload signed packages (otherwise every android phones will be very unsecure).
Click to expand...
Click to collapse
Unfortunately, you're correct. I was rooted at one point and had an old 'su' binary around that was immutable, completely forgotten about. My bootloader is stock atm and I'm still stuck on 'no command' I'm accepting the inevitability that I'll have to wipe and start over but I'm not even sure how to flash the factory firmware now since I'm either stuck in a 'Google' boot loop or I get 'no command'.
Any suggestions?
ykram said:
Unfortunately, you're correct. I was rooted at one point and had an old 'su' binary around that was immutable, completely forgotten about. My bootloader is stock atm and I'm still stuck on 'no command' I'm accepting the inevitability that I'll have to wipe and start over but I'm not even sure how to flash the factory firmware now since I'm either stuck in a 'Google' boot loop or I get 'no command'.
Any suggestions?
Click to expand...
Click to collapse
When you see no command that is normal. To bring up the stock recovery menu, while holding Power first, press Volume Up.
Google bootloop have nothing to do with flashing factory image since it required using fastboot in fastboot mode (not in recovery), aka the bootloader menu. Links in my signature have instructions to flash factory image.
eksasol said:
When you see no command that is normal. To bring up the stock recovery menu, while holding Power first, press Volume Up.
Google bootloop have nothing to do with flashing factory image since it required using fastboot in fastboot mode (not in recovery), aka the bootloader menu. Links in my signature have instructions to flash factory image.
Click to expand...
Click to collapse
Cool, gotch ya. Many thanks for the response and help.
I tried to search, but in vain.
Hardware: Nexus 4
Software : Android 4.4.4
For reasons that are not clear to me the machine restarted and is stuck in those 4 rotating circles, and doesnt go beyond it. Tried multiple things such rebooting, rebooting into recovery and booting again, tried adb to see if it can see the machine in recovery mode, but to no avail.
Can someone please help? Thanks in advance.
Did you do anything, flash anything to get the boot loop? Boot loop can usually be cleared by doing a factory reset. But you'll have to reset up your phone afterwards
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Did you do anything, flash anything to get the boot loop? Boot loop can usually be cleared by doing a factory reset. But you'll have to reset up your phone afterwards
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This is a stock android and have no changes whatsoever except automatic update to 4.4.4. Only thing that is different is it is unlocked.
For last one week the phone kept complaining that it was unable to back up photos and videos. So I kept the wifi on over the night, and next morning I saw what i thought was it was trying to reboot but unable to do.
Is it possible to connect to machine while it is in recovery mode? My ADB can't discover the device either in recovery mode or while it is trying to boot. Is there a way to press some button and hard reset it?
Concoran said:
This is a stock android and have no changes whatsoever except automatic update to 4.4.4. Only thing that is different is it is unlocked.
For last one week the phone kept complaining that it was unable to back up photos and videos. So I kept the wifi on over the night, and next morning I saw what i thought was it was trying to reboot but unable to do.
Is it possible to connect to machine while it is in recovery mode? My ADB can't discover the device either in recovery mode or while it is trying to boot.
Click to expand...
Click to collapse
Can you get into the bootloader? If so you can flash a custom recovery. ADB won't work in the stock recovery.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Can you get into the bootloader? If so you can flash a custom recovery. ADB won't work in the stock recovery.
Click to expand...
Click to collapse
I can get into bootloader - if you mean by pressing down volume button and powering on - so you see a few options such as 'Start', 'Restart Bootloader' et al.'
If I can get into this, what option do I have? How I can I some custom recovery such as TWRP?
Also, I saw a youtube video where a gentleman shows how to completely reset from Recovery mode (hold power button and press up volume key), but that doesn't seem to work for me.
Concoran said:
I can get into bootloader - if you mean by pressing down volume button and powering on - so you see a few options such as 'Start', 'Restart Bootloader' et al.'
If I can get into this, what option do I have? How I can I some custom recovery such as TWRP?
Also, I saw a youtube video where a gentleman shows how to completely reset from Recovery mode (hold power button and press up volume key), but that doesn't seem to work for me.
Click to expand...
Click to collapse
Yes, that's the bootloader. Google 15 second adb install xda and install that. Then download the latest version of this http://techerrata.com/browse/twrp2/mako
Rename it recovery and put it in the same directory as fastboot.exe which will be installed with the 15 second adb install
Open a Windows command prompt in the same directory as fastboot and then with your phone connected to the pc and in the bootloader type the command in the command window
fastboot flash recovery recovery.img
This will instal twrp to your phone
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Yes, that's the bootloader. Google 15 second adb install xda and install that. Then download the latest version of this http://techerrata.com/browse/twrp2/mako
Rename it recovery and put it in the same directory as fastboot.exe which will be installed with the 15 second adb install
Open a Windows command prompt in the same directory as fastboot and then with your phone connected to the pc and in the bootloader type the command in the command window
fastboot flash recovery recovery.img
This will instal twrp to your phone
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
My Biggest concern right now is not TWRP. I need to somehow get the machine to boot. It is stuck in those 4 circling things, and I need to somehow get the OS to work (or re-install if needed).
I am able to get to recovery where I see options to 'apply aupdate from ADB,' 'wipe data' and 'wipe partition'. I have wiped off everything, now I need to somehow get OS to install, and I don't know how. I tried using 'adb sideload 'image-occam-ktu84l.zip', but it fails.That file was extracted from occam-ktu84l-factory-0d3fd624.tgz from Android site.
Update: Great, now TWRP is installed. What next? I don't want CM at this point. Just stock Os. How do I get on to the machine?
Concoran said:
My Biggest concern right now is not TWRP. I need to somehow get the machine to boot. It is stuck in those 4 circling things, and I need to somehow get the OS to work (or re-install if needed).
I am able to get to recovery where I see options to 'apply aupdate from ADB,' 'wipe data' and 'wipe partition'. I have wiped off everything, now I need to somehow get OS to install, and I don't know how. I tried using 'adb sideload 'image-occam-ktu84l.zip', but it fails.That file was extracted from occam-ktu84l-factory-0d3fd624.tgz from Android site.
Update: Great, now TWRP is installed. What next? I don't want CM at this point. Just stock Os. How do I get on to the machine?
Click to expand...
Click to collapse
Adb side load this http://forum.xda-developers.com/showthread.php?p=47476426
Edit, you could also flash the .zip you mentioned in your post by
fastboot update your file.zip
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Adb side load this http://forum.xda-developers.com/showthread.php?p=47476426
Edit, you could also flash the .zip you mentioned in your post by
fastboot update your file.zip
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Now that I have TWRP, how do I install CM? I would eventually like to return to stock, but at least for now, I need to get the phone going.
UpdateOk, the TWRP wasn't functioning well (swipe function wouldn't work), so got CWM recovery, and installed CM. CM too goes into infinite loop. Now I am completely stuck, I have no idea what else I can do.
Concoran said:
Now that I have TWRP, how do I install CM? I would eventually like to return to stock, but at least for now, I need to get the phone going.
UpdateOk, the TWRP wasn't functioning well (swipe function wouldn't work), so got CWM recovery, and installed CM. CM too goes into infinite loop. Now I am completely stuck, I have no idea what else I can do.
Click to expand...
Click to collapse
Flash the factory image in fastboot
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Flash the factory image in fastboot
Click to expand...
Click to collapse
I installed both TWRP and CWM alternatively, installed factory images using flash-all.bat, install CM11. But in both cases, 1. factory image : The system get stuck in boot mode where those 4 circles keep rotating around each other, 2. In CM11, the arrow keep rotating indefinitely.
I don't know what else I can do.
Any pointers? Thanks in advance.
I am beginning to suspect hardware malfunction. In which case, is there a log somehow I can see?
As an Aside: 1. Adb refuses to see the device in fastboot mode. Not sure if this is an expected behavior. Fastboot can.
2. Stock Android USB Drivers never work. I had to get the WugFresh Development drivers.
This is Windows 8 environment.
jd1639 said:
Flash the factory image in fastboot
Click to expand...
Click to collapse
As I said earlier, both factory image and CM go into infinite loop at bootup. I have no idea what else to do.
Question now is to see if something is wrong with hardware. I don't know how to check that. Is there a way to do some diagnostics
Concoran said:
As I said earlier, both factory image and CM go into infinite loop at bootup. I have no idea what else to do.
Question now is to see if something is wrong with hardware. I don't know how to check that. Is there a way to do some diagnostics
Click to expand...
Click to collapse
You probably have a failure of the emmc. What happens if you try to lock the bootloader and then reboot? Does it stay locked?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You probably have a failure of the emmc. What happens if you try to lock the bootloader and then reboot? Does it stay locked?
Click to expand...
Click to collapse
Yes, after locking (fastboot oem lock), bootloader the status says locked and I no longer see that unlocked icon when booting.
- At the moment I have CWM, and I see advanced options to format different folders which I have already done. But what I am not able to do is to use adb to copy the image-occam-ktu84l.zip to sdcard. Only way I have been able to install any zip is using sideload. Is that normal? I wonder if I am following right steps to begin with.
- Also, are there tools that can run and check if emmc has no bad sectors etc?
- In CWM I formatted whole log of folders, and now when CWM boots, it can't find /cache/recovery/* files. Which I take as a good sign - since old stuff is now gone. From here I don't know how to proceed. Any help - very thanful.
Concoran said:
Yes, after locking (fastboot oem lock), bootloader the status says locked and I no longer see that unlocked icon when booting.
- At the moment I have CWM, and I see advanced options to format different folders which I have already done. But what I am not able to do is to use adb to copy the image-occam-ktu84l.zip to sdcard. Only way I have been able to install any zip is using sideload. Is that normal? I wonder if I am following right steps to begin with.
- Also, are there tools that can run and check if emmc has no bad sectors etc?
- In CWM I formatted whole log of folders, and now when CWM boots, it can't find /cache/recovery/* files. Which I take as a good sign - since old stuff is now gone. From here I don't know how to proceed. Any help - very thanful.
Click to expand...
Click to collapse
If you can side load you should be able to adb push a rom. When in recovery type adb devices. Does it show that your device is connected? Do you get an error?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you can side load you should be able to adb push a rom. When in recovery type adb devices. Does it show that your device is connected? Do you get an error?
Click to expand...
Click to collapse
I can sideload from adb. (adb sideload <filename>.zip while CMW is waiting for abd sideload). But can't push since adb doesn't recognize the device while in fastboot - the way fastboot can.
Concoran said:
I can sideload from adb. (adb sideload <filename>.zip while CMW is waiting for abd sideload). But can't push since adb doesn't recognize the device while in fastboot - the way fastboot can.
Click to expand...
Click to collapse
You have to be in recovery to run adb commands. The bootloader is only for fastboot commands. Try pushing while you're in recovery, not the bootloader.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You have to be in recovery to run adb commands. The bootloader is only for fastboot commands. Try pushing while you're in recovery, not the bootloader.
Click to expand...
Click to collapse
Here 's what I see when I to sideload,
In CWM, I choose 'install from zip, which takes me to next page where i chose to select from sideload. I then start sideload from 'adb sideload occam-ktu84l-factory-0d3fd624.tgz' (sometime I use the extracted zip from that tgz),
Following is what I see on CMW,
'Restarting adb
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
installation aborted'
Concoran said:
Here 's what I see when I to sideload,
In CWM, I choose 'install from zip, which takes me to next page where i chose to select from sideload. I then start sideload from 'adb sideload occam-ktu84l-factory-0d3fd624.tgz' (sometime I use the extracted zip from that tgz),
Following is what I see on CMW,
'Restarting adb
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
installation aborted'
Click to expand...
Click to collapse
Ok, you can't use that file (tgz) in cwm, adb or fastboot. What you can do is extract it and then use the zip file. But, you'll have to boot into the bootloader and then use the command
fastboot update update.zip
Sent from my Nexus 5 using XDA Free mobile app
Hello All
I have soft bricked my Nexus 4 by applying the 5.1 OTA update from the notification in Android. This has left me with both normal boot and recovery leading to the No Command screen. From here, it seems my only route of salvage is the 'Android system recovery <3e>' menu, accessed by tapping Vol Up whilst holding Power on this screen, and using the 'apply update from ADB' option. Unfortunately, after modifying my .inf to allow Windows recognition of the device in sideload mode according to instructions I found on this forum and finding the 5.1 OTA zip for download, I reach another error. The sideload process stops at around 92% on the computer and the phone reads:
Code:
Creating parent of system/priv-app/Hangouts/lib failed, error No space left on device E:Error in /sideload/package.zip (Status 7) Installation aborted.
This error in sideloading persists regardless of using the 'wipe data/factory reset' and 'wipe cache partition' options in the Android system recovery menu. For background purposes, I was on stock LRX22C with CWM 6.0.4.7 for a recovery, and I am now trying the LRX22C to LMY47D OTA zip. Your suggestions are appreciated.
Thank You.
You have to be 100% stock system, kernel, and recovery. If you had cwm on your not stock. Flash the system.img from the version of Android you're currently on with fastboot.
Sent from my Nexus 9 using XDA Free mobile app
Thank you. I feel like a dunce having forgotten all the stuff that can be done with adb and fastboot from the bootloader menu, or even that fastboot referred to the bootloader menu. I mainly like to keep CWM around for having the flashable zip of the offline photo gallery these days. Since CWM and the built-in updater aren't compatible, is the best way for me to take updates just to run the flash-all.sh for each one that comes out and replace CWM afterwards?
I'm on a nexus device too and that's what I do. I'd recommend twrp over cwm, cwm is not updated anymore. You'll have to re-root too. Just flash supersu.zip in the customer recovery. This is a good guide to follow, http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
fripjob said:
Hello All
I have soft bricked my Nexus 4 by applying the 5.1 OTA update from the notification in Android. This has left me with both normal boot and recovery leading to the No Command screen. From here, it seems my only route of salvage is the 'Android system recovery <3e>' menu, accessed by tapping Vol Up whilst holding Power on this screen, and using the 'apply update from ADB' option. Unfortunately, after modifying my .inf to allow Windows recognition of the device in sideload mode according to instructions I found on this forum and finding the 5.1 OTA zip for download, I reach another error. The sideload process stops at around 92% on the computer and the phone reads:
Code:
Creating parent of system/priv-app/Hangouts/lib failed, error No space left on device E:Error in /sideload/package.zip (Status 7) Installation aborted.
This error in sideloading persists regardless of using the 'wipe data/factory reset' and 'wipe cache partition' options in the Android system recovery menu. For background purposes, I was on stock LRX22C with CWM 6.0.4.7 for a recovery, and I am now trying the LRX22C to LMY47D OTA zip. Your suggestions are appreciated.
Thank You.
Click to expand...
Click to collapse
I had a similar problem. Since I have a number of Nexus Devices I have found using "SoftSkip" Android ToolKit allows me to perform lollipop updates and avoid using OTA"s You should check it out. just google it. The instructions are very simple to follow. I have also used it with both of my Nexus 7's and my Nexus 5 sucessfully. I hope that helps......... Now if I could solve the LTE problem that would be great
Hi,
My ZE550KL was locked in boot with this message: "Security Error: This phone has been flashed with an unauthorized software & is locked", so i followed some tutorials and was able to install TWRP recovery (i had bootloader already unlocked). Then when trying to reinstall stock rom, i realized i had to reinstall the stock recovery. I did it and installed the stock rom with version matching with the stock recovery i installed(UL-Z00L-WW-1.17.40.1531-user). Everything was going ok, but when my newly installed stock rom was popping multiple apps stopped working an i was unable to basically do anything. So i tried reinstalling stock rom again, but this is when things collapsed. As i entered recovery to reinstall the rom, it has lots of errors from partition cache
Code:
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
. This same errors happens when i try to wipe it from the recovery, but when i erase the cache partition on fastboot it says "OK". I also tried to reinstall twrp, but apparently my bootloader was blocked again, and it says it is flashed when i try, but when rebooting it boots again on stock recovery.
So i tried just booting twrp, but then it says my bootloader is blocked and can't boot twrp. Also tried sideloading stock rom from adb, but it gets the same cache partition errors. I tried
Code:
fastboot -w
and it says OK but the cache partition errors are still there. I also tried
Code:
fastboot erase ASDF
and i get some errors.
TLDR; I'm stuck at a cycle where i have to remount cache and all other partitions via TWRP, but i can't install TWRP because my bootloader got locked again and i can't unlock it because i need to install some rom to do it, but since my cache partition is destroyed i can't install anything, neither via fastboot on pc nor from recovery on the phone.
Did you tried the unoffical unlock way? It can done via PC in fastboot mode. Also did you tried `fastboot format system` kind of commands?
TheImpulson said:
Did you tried the unoffical unlock way? It can done via PC in fastboot mode. Also did you tried `fastboot format system` kind of commands?
Click to expand...
Click to collapse
I didn't. Can you please explain how to do it? Thanks
VMokaccino said:
I didn't. Can you please explain how to do it? Thanks
Click to expand...
Click to collapse
Damn! I just noticed that you will need to be in system to gain root access. I guess then it won't work. I suggest to try `fastboot format system/userdata/cache` way as it fixed my issues with partitions multiple times.
Here you go for unoffical guide: https://forum.xda-developers.com/ze...de-unlock-bootloader-asus-unlock-app-t3405850
TheImpulson said:
Damn! I just noticed that you will need to be in system to gain root access. I guess then it won't work. I suggest to try `fastboot format system/userdata/cache` way as it fixed my issues with partitions multiple times.
Here you go for unoffical guide: https://forum.xda-developers.com/ze...de-unlock-bootloader-asus-unlock-app-t3405850
Click to expand...
Click to collapse
Well, i tried all these format commands, but nothing has changed
VMokaccino said:
Well, i tried all these format commands, but nothing has changed
Click to expand...
Click to collapse
Did you tried what this guide says: https://www.asus.com/zentalk/thread-116230-1-1.html
TheImpulson said:
Did you tried what this guide says: https://www.asus.com/zentalk/thread-116230-1-1.html
Click to expand...
Click to collapse
I tried this, but my phone is now stuck on Fastboot Mode. It doesn't matter if i press VOL + or VOL -, it always enters in Fastboot Mode
VMokaccino said:
I tried this, but my phone is now stuck on Fastboot Mode. It doesn't matter if i press VOL + or VOL -, it always enters in Fastboot Mode
Click to expand...
Click to collapse
It's because you don't have any recovery or ROM on your device. Try flashing stock recovery.
TheImpulson said:
Did you tried what this guide says: https://www.asus.com/zentalk/thread-116230-1-1.html
Click to expand...
Click to collapse
TheImpulson said:
It's because you don't have any recovery or ROM on your device. Try flashing stock recovery.
Click to expand...
Click to collapse
Well, i tried flashing all stock recovery versions i could find, but none of them worked. I guess my phone is dead.
VMokaccino said:
Well, i tried flashing all stock recovery versions i could find, but none of them worked. I guess my phone is dead.
Click to expand...
Click to collapse
Take your phone to service center I guess.