yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] awhite2600:
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.
[Nexus 7 Q&A, Help & Troubleshooting] xbt-:
Is it under warranty?
[Nexus 7 Q&A, Help & Troubleshooting] awhite2600:
No. It's about 10 months old.
[Nexus 7 Q&A, Help & Troubleshooting] cmason37:
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?
[Nexus 7 Q&A, Help & Troubleshooting] AndDiSa:
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.
[Nexus 7 Q&A, Help & Troubleshooting] Remcotjuuh:
He has already said he can only boot into stock recovery, not bootloader.

---------- 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?
[Nexus 7 Q&A, Help & Troubleshooting] awhite2600:
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.
[Nexus 7 Q&A, Help & Troubleshooting] awhite2600:
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.
[Nexus 7 Q&A, Help & Troubleshooting] awhite2600:
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?
[Nexus 7 Q&A, Help & Troubleshooting] awhite2600:
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.
[Nexus 7 Q&A, Help & Troubleshooting] Remcotjuuh:
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?
[Nexus 7 Q&A, Help & Troubleshooting] awhite2600:
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?
[Nexus 7 Q&A, Help & Troubleshooting] Remcotjuuh:
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.
[Nexus 7 Q&A, Help & Troubleshooting] awhite2600:
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:
[Nexus 7 Q&A, Help & Troubleshooting] Remcotjuuh:
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.
[Nexus 7 Q&A, Help & Troubleshooting] AndDiSa:
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!

[MENTION=4782699]Remcotjuuh[/MENTION]: 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.
[Nexus 7 Q&A, Help & Troubleshooting] Remcotjuuh:
I know, but he has clearly said multiple times that he cannot access the bootloader, although I find this very strange too...
[Nexus 7 Q&A, Help & Troubleshooting] sakif.kamali:
Sony xperia s bricked

i'm experiencing a similar problem with my phone. i rooted my phone today (using http://xdaforums.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
[Galaxy Note II Q&A, Help & Troubleshooting] mannyvinny:
My internal memory's 50% storage is occupied by .thumbnail folder..I am running short of memory so I need to delete this folder.so is it safe to delete this folder? If I'm not wrong then this folder ONLY contains gallery pictures thumbnails.

♏〽 ?⭕??✌ ?? ????⭕Ⓜ?
[Galaxy Note II Q&A, Help & Troubleshooting] emgluon:
It's safe to delete them but they'll only come back next time you open gallery.

Inside the thumbnail folder there maybe a few hidden files (ie file name start with .something) some of these may well be a few gb big in your case. You can just delete them instead of each thumbnail file of about 100kb each.

Before deleteing them, make a note of what they are called and after deleteing them make a folder of the same name to avoid them getting created automatically by gallery.
[Galaxy Note II Q&A, Help & Troubleshooting] mannyvinny:
Can u please clarify this:confused:?

♏〽 ?⭕??✌ ?? ????⭕Ⓜ?
[Galaxy Note II Q&A, Help & Troubleshooting] Grumps:
He means dont delete the .thumbnail folder as it will be recreated. Go into it and delete the huge files over 100kb to make some space.
[Galaxy Note II Q&A, Help & Troubleshooting] emgluon:
Those big files in the thumbnail folder. Called something like ".thumbdata3--1967290299" the clue being the data part. They can get very large.

Just copy the name of these files. For example by doing a rename then copy and the whole file name. Delete the file then make a new folder and paste the filename as the folder name.

When later gallery try to automatically generate these thumb data file, it'll find that it cant as there is already a folder of the same name and skip it.
[General Questions and Answers] sejtam:
Had anyone managed to get support from Titanium Track, the developed of these two apps?

For months I have left support requests on their website to ask for help with a long-standing issue they have, but no reaction at all.

The issue involves both apps stopping any DropBox sync stopping when they encounter a zero-size file..

I also mentioned this on their Google play pages under reviews, yet nothing helps, the developer simply never returns any message not shows any other reaction
[Android Q&A, Help & Troubleshooting] kettir:
I just read about an upcoming Samsung android flip phone (only overseas alas). I've always thought that android combined with the form factor of the original Razr would be an interesting combo. Can anyone point me at a flip-form android phone that has an external screen (it can be small) and inside a reasonably sized screen along with a number pad, that would work with AT&T in the USA?
[One (M7) Q&A, Help & Troubleshooting] mjwitt2:
Randomly for the last few weeks, I've heard random DTMF tones while i'm in a call. I always assumed it was the person on the other end just hitting buttons on their phone, but it happens when I'm talking to someone who is on a landline or cell phone. They are not hitting buttons by mistake and neither am I. What's weird is I'm the only one who hears the tones! Both parties (my mother and my wife, mostly) both have AT&T for service.

I have searched and saw that some EVO users experienced this while using Google Voice, but I'm not using it when I'm making calls. I have it INSTALLED, but I'm not actually using it to make calls.

I'm running:

Android 4.2.2 BrightstarUS RUU W/ OTA

Radio: 4a.17.3250.14_10.39.1150.04L

with included Kernel from the RUU

This is a rock-solid build for me, constantly getting me LTE in a fringe area, and I'm super happy with it. I'd uninstall GV, but I need it for texting. Aside from that, Any thoughts?
[Android Q&A, Help & Troubleshooting] Nylo:
Hello,

I had to clear data and do a force close on LUKS Manager. It now cannot find my .VOL.

How would I go about getting LUKS Manager (Android) to recognize it again, or is this possible?

LUKS .v 2.4
[Android Q&A, Help & Troubleshooting] biopsin:
I create a new tiny dummy file, then replace it with the real thing.
[Android Q&A, Help & Troubleshooting] Nylo:
Sounds good. Ill give it a shot.

Thanks,

Nylo

HTC Inspire GB233 Root

Stock AT&T ROM
[Android Q&A, Help & Troubleshooting] rileylarche:
Hey guys has anyone else noticed in the YouTube app on android 4.3 that if you use the keybord in landscape and use the hide button that there i s a big graphical glitch where the keyboard used to be?

Thanks!:confused:
[MDA III, XDA III, PDA2k, 9090 General] finch:
I do not post a lot but I do read and I love this site. You all have great information.

My question is: Why is the BT such a problem? How come the BT works so well on regular phones but on these divices it is an issue.

I hope this is not a dumb quetion I am just trying to understand.

Thanks.
[MDA III, XDA III, PDA2k, 9090 General] 3waygeek:
The general consensus, as I've read here & at HoFo, seems to be that some part of the BA's hardware isn't up to par. ISTR reading that the placement of the BA's antenna is a bit problematic; since both BT & WiFi use the same 2.4 GHz frequency, they could conceivably use the same antenna. Thus a poorly designed 2.4 GHz antenna could explain the BA's substandard WiFi and BT performance.
[MDA III, XDA III, PDA2k, 9090 General] kennethm:
My BA's WLAN isn't bad at all. I can easily get a fully usable connection to my Netgear WGT 624 accesspoint inside my room on the third floor in a concrete building at a distance of appr. 90 meters.

Also usable inside my car parked on the opposite side of the building!

(See attached images)

[/img]

BT works well at 10 meters with a GPS receiver.
[MDA III, XDA III, PDA2k, 9090 General] finch:
Thanks for the input guys.
[MDA III, XDA III, PDA2k, 9090 General] Jiggy:
Bluetooth to headset range

Has anyone got to the bottom of the issue with the range for the headset. I have had to keep my radio where it is for T-Mobile BB but have updated to the 3900 build.

No matter what the bluetooth build or the radio version it just seems to me that talking on a headset is dreadful if it is more than 4 feet away from the device. If for example you have the device in your pocket I still get a lot of static and scratchy voice quality.

The headset I use is the SE HBH660. Is it the general consensus that we just have the live with this?

All view comments and opinions welcome even if you think I am totally wrong :lol:
[MDA III, XDA III, PDA2k, 9090 General] robboy:
i can not even get my device to find my BT handsfree.

any ideas
[MDA III, XDA III, PDA2k, 9090 General] mike freegan:
:O Mine won't even pick up the network in my conservatory 10 meters away. I can get low signal in my bedroom approx 3meters above the router.
[MDA III, XDA III, PDA2k, 9090 General] finch:
Re: Bluetooth to headset range

I use a Motorola 850 same thing. I hate this. I am in the car the phone is in the seat next to me. WORKING PERFECT. I get out of the car and put it in the belt holster BAM cracking static etc. Now the distance from the headset to the phone is greater in the car than on my belt.

I mean Jesus tapdancing Christ. I do not get it. I have tried the headset on the same side of the body trick and everything. :x

:) O well the fun of new technologies.
[Nook HD, HD+ Q&A, Help & Troubleshooting] duvious:
I tried to avoid updating my Nook HD+ to the new update 2.1.1 but it did it anyway before I could root and install the update block. Now, it seems that the update may have put a block of some sort on it so you cannot boot from an SD Card. I have inserted the CWM card while it was on and when it was off and I still cannot boot with it inserted.

Anyone else have this problem?
[Nook HD, HD+ Q&A, Help & Troubleshooting] digixmax:
Have you checked that the SD card in question is (still) bootable -- i.e., its first partition is of the type 0x0C FAT32 LBA, has its Active flag set, and contains the appropriate set of boot files?
[One (M7) Accessories] Neon01:
I dislike the way the edges of the phone are angled toward the front face - I'd much prefer them to be just flat and squared off to the front and back (like the iphone). Are there any cases that give you this feel - at least to some extent? It'd also be nice if it flattened out the "convexity" of the back too. Anything that might increase tactile feel/responsiveness of the standard buttons is a bonus.

I'm currently learning toward the Diztronic TPU case.

Any thoughts?
[One (M7) Accessories] icepixie:
I have the diztronic and it's a good case, was my go-to case for the last little while. Because the material is not slippery and it's a slightly bulkier case, you don't notice the convexity of the back. The phone is pretty "stable" as a result when it's on a flat surface. Regarding the sides, it's a border of sorts with a small ridge in the case between the sides and the back. This will probably give you the feeling of the sides being squared off.
[One (M7) Accessories] ro_explorer:
[MENTION=717278]Neon01[/MENTION] ... I'm sorry for asking this but why did you bought this phone if you do not like at all the construction ?
[One (M7) Accessories] Neon01:
Thanks, that sounds perfect.

Who said I didn't like the construction? It's the only Android ever sold (from what I can tell) with iphone build quality (or better). I'm not enough of a fanboy of any product not to call out bad ergos when I feel them. The chamfered edges of the One are atrocious. I hated them on the One X, and I hate them on the One. They're angled the wrong way, IMO, but just squared off would be best. The back is not really as much of an ergo thing, but it gives the phone a weird thicker feel. It doesn't help that (with no case), when set down, the center of gravity is directly over the camera glass due to the convexity. These aspects aren't enough to drive me away from what I otherwise consider to be a phenomenal phone, but I'll try to minimize them where I can.
[One (M7) Accessories] ro_explorer:
Well ... I find the ergonomics of the phone excellent and I have no complain about the angles of the edges .. on the contrary, I like the feel in the hand.
[One (M7) Accessories] BlessedTalent:
Check my post on page 190 second from the top, I have a case that has an flat back like you want. It does add some bulk because it builds up the edges to be flat but I love the case and feels great. Hope it helps!

http://xdaforums.com/showthread.php?t=2171713&page=190
[Android Q&A, Help & Troubleshooting] jheysl2:
I tried updating the software on the system but it is stuck in boot loop and it seems to be a known problem, I've tried holding down the update button inside but with no luck, I have tried emailing them too but there has been no response, Anyone know or tried a fix for this? :(

This is the exact device: Cyclone Android Media Center
[Android Q&A, Help & Troubleshooting] demkantor:
change desc.txt.txt

to desc.txt

remember windows may be hiding file extensions from you
[Nexus 7 (2013) General] acdcking12345:
I get this dot that trails me as I move around on the screen. Can that be removed?
[Nexus 7 (2013) General] robbiev80:
Did you enable "Show touches" in the Developer options menu? Simply uncheck the box beside that option to get rid of them.
[Galaxy S 4 Q&A, Help & Troubleshooting] -=nezero=-:
Hello,

Having issues with heimdall on Ubuntu 12.04.

I was trying to flash ClockworkMODs recovery but i just hit this issue:

sudo heimdall flash --RECOVERY recovery-clockwork-touch-6.0.3.6-jfltexx.img --no-reboot
Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
PIT file download successful.

Uploading RECOVERY
0%libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12

ERROR: Failed to send file part packet!
ERROR: RECOVERY upload failed!

Ending session...
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...

Its been a while since i have done this, but i'm sure i have no issues before on this system.

Anyone know what the issue is?
[Galaxy S 4 Q&A, Help & Troubleshooting] memstick:
I don't know what the issue is, but version 1.3.2 of Heimdall worked. I think the issue is in the latest version of heimdall somehow. The error thrown by libusb seems to be of the "not supported" type.

[/COLOR]
[Galaxy S 4 Q&A, Help & Troubleshooting] evarInward:
Hey, I know this thread is somewhat old... But I am running ubuntu 12.04 x64 as well. I only saw 1.3.2 in i386 at the github downloads for heimdall. Did you just install libusb-1.0 i386 as well to get heimdall 1.3.2 to work?
[Galaxy S 4 Q&A, Help & Troubleshooting] evarInward:
Hey guys! Just wanted to let you know that if you are still having this issue, you need to update your kernel. If you are unsure how to do this, just drop me a line and I'll give you some links and info. Just remember to rebuild heimdall and libpit.
[Galaxy S 4 Q&A, Help & Troubleshooting] yogneo:
similar issue

I think i have a similar problem

i am using heimdall 1.4 on ubuntu 12.04, when i try to flash cwm recovery the program stops at detaching driver and does not even proceed to "Initialising protocol..." in the above image.

using samsung i9082

could someone help please.
[Galaxy S 4 Q&A, Help & Troubleshooting] Mpa4Hu:
same, same device
[Galaxy S 4 Q&A, Help & Troubleshooting] ice.modding:
sorry but... heimdall, works on i9500?