yashsingh1/xdaforums huggingface dataset:
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
I have the exact same problem as the OP, I tried sideloading but all I get is a bunch of gibberish adb related in the cmd window whenever I enter anything, i.e. adb push, adb device, adb sideload same stuff comes up in the cmd window but nothing is sideloaded onto the device. What am I doing wrong ? I was attempting to install paranoid android port, was wiping everything and in my eagerness I wiped the system/OS, can still enter twrp.... a bit of help would be appreciated!
[7" Kindle Fire HD Q&A, Help & Troubleshooting] soupmagnet:
It would he helpful to know exactly what messages you are receiving...
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
this is the message I recieve, a bunch of commands and explanation as to what adb commands do. :good:
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
I think either my xda app is glitching or that photo got resized so small the text is unreadable. But I am throwing a guess that the command syntax was wrong so adb threw up its default usage text. BTW here's a tip, instead of screen-shotting your PC, right click in the command prompt and press mark, it will let u highlight the text, when done highlighting, tap enter on the keyboard to copy, then you can paste the text here, preferably in code brackets if there is a lot. I find it funny most people don't know this considering how often most people use copy and paste now days, then again Microsoft didn't exactly label it very well. What exactly did you type into the command prompt?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
the pic came up small because it is a thumbnail to the larger pic which is in photobucket, didnt want to flood he page with an overly large photo, thanks for the pro tip! didn't know that but it shall come in handy in future. :)

I typed in adb sideload /pa_tate-3.90-20130801.zip and then got the following:

hope it helps! yes I'm aware my first name is in there, not bothered! :))
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
do I need to provide more detail ? because I'm pretty sure everything you need to know is right there. The OP solved his issue, would of been helpful if he said how?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
Everything we need is right there, I'm trying to figure out why its doing that be cause the syntax looks correct to me. I'll do some checking on mine, have to ask, u did put the file your trying to side load in the same folder as the adb command right?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
doh! :rolleyes:

Its always the simple things we forget to do! Will try it in the morning and let you know! Cheers bub.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
I placed the file in the android sdk folder at C:/Android SDK still no joy, keep getting the same message pop up..... is there a specific folder within android sdk it needs to be in ? build tools ? temp ? platform-tools ?

On a side not Amazon has agreed to send me another one. Theyve asked that I return this one after I get the new one, question, would they be bothered if I didn't ? Or would they try to charge me for the price of a second one ? latter option seems more likely imho...
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
The adb command I believe is in the platform tools folder, put it in there and try it. Also just call amazon and ask them to cancel it and tell them you got it working, I doubt there would be any problems.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
yeah I figured it was the platform tools folder, still nothing, I have tried various syntax entries followed the guidelines laid out by twrp for sideloading, still no joy, same bunch of adb commands are displayed after enter.... I do not know what I am doing wrong, this is not my first time working adb or with rooted devices.....
[7" Kindle Fire HD Q&A, Help & Troubleshooting] soupmagnet:
It amazes me that this is still being discussed.

In TWRP, go to Advanced > ADB Sideload > Swipe....and THEN enter the 'adb sideload' command.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
this has been done. repeatedly. Still getting the same adb message as I posted previously. I truly wish this was as simple as you appear to think it is but clearly it is not, there are 2 options, A) I'm doing something wrong, despite following every shred of advice I have come across or B) I've borked the system worse than the OP did.

EDIT~ I opted to open the cmd line directly in the adb.exe folder ( platform -tools) entered the syntax as shown by TWRP and soup this is the message I recieved:

I'm using a normal cable for this process as I didn't think using the fastboot cable would work. I'll try the factory cable next.

Tried factory cable as well, still no device found..... drivers are installed, I know they are, but the kindle shows up as a pa_tate_blah blah blah instead of the KFHD and there are no drivers for the former....
[7" Kindle Fire HD Q&A, Help & Troubleshooting] soupmagnet:
Tate is the KFHD7

Do 'adb kill-server' and try again. Otherwise, update your adb.exe or SDK

[Edit:] Oh, by the way, you should update your TWRP as well. It has updated hardware IDs that match the KF's now.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
OK, I moved the usb cable to a different port and now the PC reads it as Kindle Fire HD 7 but with the yellow warning indicator stating no drivers found but upon inspection of the device manager the latest drivers are installed.....

entered the code as instructed :

using the factory cable and normal one, same as above,...
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Crashed7HD:
I am watching this thread in detail as this is exactly the issue I am having as I reported earlier on in this thread.

I just downloaded and unzipped to C:\SDK, the current SDK and have version 1.0.32 of ADB. I added ";C:\SDK\sdk\platform-tools" to windows Path variable.

With either Factory or plain-USB cable I get "Device not found" or "waiting on device" depending on which ADB command I try.

Even though ADB can't find it, I DO get the Kindle showing up in File Explorer and I can move an ebook to the Download folder and it shows upon the Fire.

I even went so far as to uninstall my Firewall and Anti-Virus in case they were blocking it. Still "device not found."
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
If you can see the folders you should be able to drop a rom zip at the root and then just do a flash from twrp?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] soupmagnet:
You have to check the hardware IDs listed for your device when it is plugged in and make sure your android_winusb.inf reflects those IDs.

Various ROMs, versions, and until recently, recovery versions, can all have different hardware IDs.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] RaptorYeshua:
Just logged on since I fixed my KFHD.

Cream i pmed you instructions and steps i did to fix it.

Hope it helps.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] RaptorYeshua:
Can't PM for some reason, here is how I did it

Put your ZIP at your ADB program file location

Navigate through CMD to ADB location

Boot into TWRP>advanced>ADB sideload (swipe to begin)

type adb devices and it should show your device connected and say sideload

Type "adb sideload nameofzip.zip" no quotes

Wait and hopefully it gets fixed, good luck. That whole fiasco nearly gave me a heart attack.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Crashed7HD:
How do I get TWRP to do anything when ADB says "Device not found?"

From the TWRP website...

"Download file above."

"Execute the commands below from the command prompt with your Kindle connected to the PC."

"adb shell"

That FIRST command fails with "Device not found."

---------- Post added at 08:57 PM ---------- Previous post was at 08:52 PM ----------

Thanks for trying to help, but how do I boot into TWRP? It is NOT installed on the Fire and ADB cannot see the device.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
If you don't have twrp installed then what exactly are you trying to do?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
Stunt has a point, if you do not have twrp which means a 2nd bootloader has to be installed so there is no way you could have twrp unless you have the bootloader first. I do not understand how adb doesn't see the device but your file explorer does ? My problem is vastly different from that mate. Can you turn your Kindle on ? Beyond the boot screen ?

As for my situation, I do not think it is tenable any longer and as such I have given up on sorting this one out since Amazon has sent me a replacement anyway and I rooted it within 10 minute sof taking it out of packaging :D Will do the 2nd bootloader later, for now I'm happy to just tweak with Kindle Free Pro and throw on the Play store.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] calkenneth:
Did you back-up your OS image somewhere? Can you use TWRP to recover it?

If not, you need to download a ROM (such as Hashcode's CM10.1 from http://xdaforums.com/showthread.php?t=2245335. Then you have to use ADB to push an image onto the storage partition, and then use TWRP to flash the image. Did you see #6 from this thread?

http://xdaforums.com/showthread.php?t=2271909

6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.

Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done.
​

Alternatively, can you get the device into fastboot mode? You can use fastboot commands to recover it too.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
yeah I kept the original back up and several other backups of roms I had tested on the device previously. None of them were on the Kindle when I messed it up.

No matter what I do I can not get my PC to recognize the device due to the name it was given by the Kinology rom Kindle Fire HD 7, plug and play does not work for the device to be used via ADB, it IS picked up by the PC but it IS NOT accessible, no drivers and so no ADB commands work.

I can not get it into fastboot mode, I have tried using the factory cable and no joy. I usually know enough to know what I'm doing, but sometimes I do **** it up which is how I ended up in this boat in the first place. As far as I can tell this device is stuck right where it's at unless I find another way to access the device via adb or there is another method of entering fastboot ?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] soupmagnet:
I keep saying this but it seems as though my words keep falling on blind eyes...

Check your hardware IDs

. Make sure they are in your android_winusb.inf. If they're not there, add them and reinstall it. If that still doesn't work, use a different computer. If that doesn't work, set up a liveUSB and use Linux. If you're scared of Linux, use the SoupKit(again). There should be no reason for anyone to have such are hard time communicating with their device over ADB or fastboot.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
how do I check the hardware ID if I can not access it ? I have used a different computer, fresh install of Android SDK even. So how do I check the hardware ID ?

this is my android_winusb.inf :

Why is it all Nexus ? never owned one?

Not scared of Linux, actually a fan of Ubuntu just do not have an in depth knowledge base of it's workings.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
I'm tempted to post the modified drivers I made to see if the hardware vid and pid are the same, I made my own custom android_winusb.inf that works with kf1 kfhd7 and kfhd7 running cm before hashcode changed the vid and pid to stock kindle( he did that on the os recently right?). Oh and for the record to check your hardware Id u right click the device that got the exclamation in the device manager, goto details tab, and hit hardware id's on the drop down list(or something like that, I'm in Linux so i can't check right now). I uploaded my modified drivers the other day on a thread, I'll link you to them, see if they work for you.

Edit: wow i just made the post a few days ago and i cant find it, il just repost the drivers again...

Edit2: Trying to keep different version of my drivers from floating around on the forum, so use the link in my signature for the most up to date drivers.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
the above is my hardware ID I assume if they do not match the ones you provided I insert them into the inf file ?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
Yea replace the vid and pid on mine with that, keep in mind there are 2 sections to that inf file, on is ntx86 and the other amd64, I suggest replacing the line in both areas if you don't know if your is is 64 bit or 32 bit, I always do it anyways.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
replaced as one would result looks like so :

there's more but it's not relevant as I simply replaced the 64 bit as well, but since I know I'm on a 32 bit system...anyway still getting device not found.... it is plugged in, I just can not understand why I am having such a hard time communicating with this device! It should be sorted by now!
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
OK now I'm co fused, I don't think something is right there I didn't think about it much at first, but I don't think the rev is necessary, and it also wouldn't take place over the mi if I remember right, I'm looking at this going "wtf is this a kindle?" Because last time I dealt with an android device and it only showed up like that in the hardware id's, it was an lg optimus titan, and I had to use factory drivers from lg for it to show as more devices... Just try choosing the driver manually from that android_winusb.inf, I think u need to choose android adb composite device, you will have to uncheck show compatible drivers.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] soupmagnet:
What version of Windows are you running?

[Edit:] Also, so I don't have to read through this entire thread again, what state is your device in?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] calkenneth:
If you are having problems getting your computer to see your drivers, do what Stunts is advising, or install the drivers from the Android SDK which I posted in this thread:

http://xdaforums.com/showthread.php?p=44062963#post44062963

1. Extract those drivers into a directory you can find easily. Those drivers are DIRECTLY from Amazon and are signed drivers.

2. Go into Device Manager and find the Kindle.

3. Update the drivers by manually searching for the drivers in the directory where you extracted everything.

4. For category of device, choose Kindle, and then find the ADB USB Composite or something to that effect.

It should now see your device when you're connected in fastboot mode. By the way, you said that you aren't able to get it into fastboot mode. What happens? Are you following the process correctly? (Turn off device entirely, connect cable to computer, then connect cable to device).
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
I've now got it into fastboot mode, I was making an error with the syntax when entering the command, I have my back up ready but am hitting a stumbling block, a simple one I know but bear with me, we are getting there

what's wrong ?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] calkenneth:
Easy, your fastboot directory isn't in your Windows path.

Add it to the path via Control Panel -> System -> Advanced System settings (lefthand side of the screen) -> Advanced Tab -> Environment Variables (button at the bottom).

Highlight PATH and click Edit. At the end of the dialog box, add exactly this text since that's where your fastboot command is located. Make sure you use the semicolon!

;C:\Android SDK\platform-tools\​

Then try again.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
success at last! via fastboot using cmd I have restored my Kindle to stock rooted 7.4.3. Thank you all for your time and patience. It is very much appreciated. Now I've a 2nd Kindle to sort out from someone else! neighbors got the red screen. See ya!
[7" Kindle Fire HD Q&A, Help & Troubleshooting] calkenneth:
Glad it worked out! Red screen is fairly easy to fix too, using the same technique. I got a red screen when I missed a step when flashing the 2nd bootloader and TWRP onto my device. Once I flashed in that extra file, it was fine. How did your neighbor get the red screen?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
same way you did, forgot to tick the box where the big red letters were warning him of the boot not being 7.2.3, using flashfire I think he said, I thought I had a fastboot cable but it appears the cable that came with my kindle isn't actually a factory cable so I've ordered one. Even using the fastboot method with a normal usb cable doesnt work for the red screen apparently....
[7" Kindle Fire HD Q&A, Help & Troubleshooting] calkenneth:
Are you sure about that? As soon as you get the device into fastboot, you should be able to run fastboot commands, including the ones needed to flash the 7.2.3. bootloader. Anyways, good luck!
[7" Kindle Fire HD Q&A, Help & Troubleshooting] CreamEggKing:
thats the problem, the device isn't going into fastboot, just stays red screened and the cmd window just hangs at <waiting for device> after i enter fastboot -i 0x1949 getvar product

I'll just wait for the cable to arrive. :good:

thanks again!
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Rednival:
I got a factory cable and I actually fixed it myself with some research and tinkering around. It is now rooted. I am just trying the whole wallpaper fix thing now.
[Nexus 4 Q&A, Help & Troubleshooting] NamNamNom:
Hi,

Nexus 4's loud speaker volume isn't so high compared to other phones, as you guys already know. I know that there are apps that can increase the volume. But how far can i push it? I don't want to ruin my speaker. And yes, there is a mod that increases the volume of the nexus 4 , but unfortunately it doesn't work on xylon rom, which i'm using.

Thanks
[Nexus 4 Q&A, Help & Troubleshooting] abaaaabbbb63:
I don't see any reason to push the speaker. The quality of the sound isn't normally great. By increasing the volume, quality will decrease even further.

Try increasing the volume with about 10%. That shouldn't damage anything.
[Nexus 4 Q&A, Help & Troubleshooting] NamNamNom:
I don't care about sound quality really, i just want to hear the song lol. And i dont know if 10% makes it better.
[Nexus 4 Q&A, Help & Troubleshooting] abaaaabbbb63:
Well, more than that could blow up the speaker.
[Nexus 4 Q&A, Help & Troubleshooting] NamNamNom:
Hahahah
[Galaxy S 4 Accessories] offwiththeface:
Samsung Qi Compatible Wireless Charger - $25 + $4 shipping

Samsung is selling their wireless charging pad, which is Qi based, for $25 + $4 shipping. This is a great deal for all you fellow new nexus 7 owners, and anyone else with a Qi compatible phone!

Promo Code: rv18623

http://www.samsung.com/us/mobile/...100IJWUSTA

Unfortunately credit card has to be american address so me and other Canadians are out of luck
[Galaxy S 4 Accessories] Alexander T.:
Well, and yes and no :)

I live far outside of USA, but managed to order it successfully by just substituting the billing address; put the one, provided by shipito service (mail forwarder).

The package now is in transit to shipito warehouse, from where it will be forwarded out via international postal service to my country.
[Galaxy S 4 Accessories] aznlunatic:
link not working for me
[Galaxy S 4 Accessories] RatusNatus:
There is a code now...

http://www.samsung.com/us/mobile/...100IJWUSTA

Promo Code: rv18623
[Galaxy S 4 Accessories] CZ Eddie:
Page not found.

So is that a total wireless solution for ~$30 or do you still need other items to make it all work?

Speaking as someone who has never looked into wireless charging before....
[Galaxy S 4 Accessories] offwiththeface:
Still need the receiver backplate which comes out to $20 with the discount
[Galaxy Tab 7.7 Q&A, Help & Troubleshooting] cneal:
Hi all,

I have a Galaxy Tab 7.7 (GT-P6800) running Stock Jelly Bean v4.1.2 (rooted). I have flashed and re-flashed the tab multiple times with Honeycomb, ICS, and several variants of Jelly Bean, so I'm familiar with Odin, CWM, ROM Toolbox etc.

Now to the problem: While just about all other apps run nicely and display text in a readable font, the Facebook app seems to choose the tiniest font it can find. Photos in posts appear normally but the accompanying post and comments are teeny-tiny and hard to read.

I attach a couple of screenshots of the FB app and others, so you can see the difference.

Any suggestions for making the FB text bigger?

Thanks!

Chris
[Galaxy Tab 7.7 Q&A, Help & Troubleshooting] edan1979:
my suggestion. install xposed framework and its module app setting. you can change the size of the apps. its relatively easy. no need flashing. you can refer more info at the apps thread.

http://xdaforums.com/showthread.php?t=2072081
[Galaxy Tab 7.7 Q&A, Help & Troubleshooting] cneal:
Thanks edan1979. I'll give that a try and update the thread with the results.

Chris
[Upgrading, Modifying and Unlocking] seriouskilla:
Hi folks,

is there a chance to change the MDAIII to a XDAIII?

I changed my GSM-provider from t-mobiel to o2 and would like to have a full functionally "XDA" instead of a "MDA".
[HTC Wildfire S] SnpyPL:
Hi

Due to low internal memory, I decided to flash my sister's HTC WFS with new firmware which supports int2ext+. Tried with "stock rom by crossfire 77" and "Marvellous Sense3.5 by Kevinjoa" (both great roms :good: ) but on both appeared the same problem. After installation of int2ext+ and first reboot - everything go OK (everything from google play install without error, everything runs nice), but after second reboot downloaded apps dissapear or "force close" window pop up (google play show only install option - not run or uninstall on apps that was already installed). What should i do ? Or what i do wrong ? Before installation of new firmware, everything was wiped, sd card has two partition (FAT32 ~ 7GB, EXT ~ 1GB - partitioned by CWM and formatted). Phone shows in settings ~ 700 MB of free internal memory. Please help.
[HTC Wildfire S] Guitarfreak12:
Try to run 'fix permissions' from cwm or rom manager

Sent from my HTC "Marvellous" WFS
[HTC Wildfire S] SnpyPL:
Thank You for answer but "fix permission" didn't help - still the same error (force close) appears
[HTC Wildfire S] jasql83:
Similar Problem

Hi i had a similar problem i've installed on my htc WFS CyanogenMod10.1-20130703-4.3-F-NIGHTLY-marvel and CronMod-INT2EXT4+_signed to have more space on my device.

Everything went smooth till i restarted the device oan when it booted the aplications that i installed disapired from the system well the system didnt see them even that the icons where on sreen.

Try to flash again that mod int2ext and see if the aplication returns.

I did that and it helped.

The problem is that if i turn the "Advanced Restart" whenever i restar the HTC the aplications disapir and when the option is turn off the aplications are there and working.

Sorry for my english :)
[HTC Wildfire S] Guitarfreak12:
You just found the bug what it is causing then ;)

Sent from my HTC "Marvellous" WFS

---------- Post added at 11:49 AM ---------- Previous post was at 11:48 AM ----------

Uhm, lemme think. Try to flash another rom. Maybe the init.d support has a bug or something

Sent from my HTC "Marvellous" WFS