Database Users

[Q] Cyanogenmod7 problem

Hi everybody. I was trying to install cyanogenmod7 on my rooted kindle fire. I got halfway through the process i rebooted the kindle fire, it started to load clockwork i got the message cwm-based recovery v 5.0.2.7. Apply update from sdcard. Then all of a sudden i receive a message saying: Install from sdcard, finding update package, opening update package,but got error saying can't open /sdcard/update.zip (no such file or directory) installation aborted. Now when i turn on the kindle fire i just get the same message. Can't access nothing at all. Just stuck on that message. I was hoping that there might be a way to fix this problem.thank you.

Is the name of the ROM file called update.zip saved at /sdcard?
Sent from my GT-S5830 using XDA App

no it is just sdcard/update.zip

At the given state of your KF, can you see your KF via adb command i.e. adb devices.
If you are able to see your device, then the fisrt test I would receommend to copy the update.zip from your PC to the KF via adb push command i.e.
adb push x:\update.zip /sdcard were x: is your PC drive where the ROM resides.
Then reboot your KF either via the power switch or adb command.
See if the recovery boot will recognize the ROM or not.
If not, I will recommend to chnage your recovery startup program to FireFireFire. You may search the original thread of inatlling FIREFIREFIRE to your KF instead of the one you have now.
Regards

[Q] problems with CW [SOLVED]

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...

[Solved]Stuck in TWRP Yellow triangle

Hi I have TWRP recovery mod on my kindle also i had CM7 Installed and everything was fine until I decided to try out this ROM:
http://forum.xda-developers.com/showthread.php?t=1486953
I booted into the recovery mod, installed the ROM and when I rebooted my Kindle it got stuck on yellow triangle I rebooted the device again and I tried to go to recovery and install the cm7 again, so i kept pressing the power button, the button's light turned orange but it was still stuck on the traingle
can anybody help me?

I also tried rebooting it many times and didn't help!

http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4

Damn it its so confusing ... isn't a easier way? I'm not pro... I copied "fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img" in the command promote and it keeps telling me "Not Recognized" Please help! why when everyone have this issue with that freaking ROM the still kept the thread up?

there is no easier way
download kfu 0.9.3:
http://forum.xda-developers.com/showthread.php?t=1399889
extract it to c:\ and rename it to "kfu" that it is c:\kfu
now open a (elevated) command prompt and cd to c:\kfu\tools
there are all needed commands
also copy\extract all downloaded files to the tools directory
do the commands as described ...
btw. this seems to happen at bad downloads - it is allways a good idea to check md5 before flashing

Shhhhooooooootttt! Tried re installing the TWRP with utility and worked got the recovery mod and restored the old cm7 ROM ... Thank You GOD I was getting a heart attack...
Problem solved

glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

Just one more question how can i check md5 before flashing? What is MD5?

there are lot of progs - just google for "md5 checksum"
here is one for windows:
http://www.winmd5.com/
edit: what is md5:
md5 is a file checksum - the devs give them on the download page - eg:
Download:
MIUI.us_blaze_4.0.3-2.2.3-alpha_0xD34D.zip
MD5: e4d8fbf891b2dc456a387ad1cb19496b
Click to expand...
Click to collapse
with a program as above you can verify if the downloaded file is correct

Good to know about these stuff, Don't want this to happen again... thanks again my friend

[Q] Nexus 10 missing from USB connections in recovery

Hi All,
I've been trying to sideload the net OTA. The dvice shows up while it's running. I can do a 'adb reboot recovery' and it reboots OK, sits at a screen where it says "no command" but the Windows cannot see any kind of connected USB device, no unknown....nothing. I checked on all 5 ports. In Bootloader mode it shows up OK but not in recovery.
Any ideas?
Thx
Update: Now the piece of sh1t will only boot into recovery....how do I get out of that?!? I tried to reset, I can get into boot loader, but 'Start' or fastboot reboot does not get be back into Android.....and as I'm typing this it reboots itself into the OS.....oh well :-|

I'm having this exact same issue. Did you find any fix?

timesgodjillion said:
I'm having this exact same issue. Did you find any fix?
Click to expand...
Click to collapse
No but I worked around it:
Download and install the Nexus 10 Toolkit
download the latest TRWP recovery
rename it to that one supported and included in the Toolkit (I found no way to upgrade the Toolkit to 1.7.1 without paying!)
copy it into the right folder inside the toolkit structure
copy the OTA update into the SDCARD
start the toolkit and boot a recovery without flashing (Option 10 I think)
chose the TWRP recovery
once the recovery has booted you install the OTA zip
Mine failed with some assert error (system/bin/debuggerd) so you may need to use the updater script and remove the assert line (and ONLY the line causing you grief)
Make sure you use something like Notepad++ that doesn't mess up the script file
clear cache and dalvik and then reboot
worked for me

[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