Develop Bugs

[Q] Kindle Fire with 6.3 Help with Rooting Please

Hi,
I am a total noob. I don't even know the proper expressions for this whole thing.
So this is my case:
I am outside the US and bought the Kindle Fire with a 6.3 firmware, couple of days ago.
Being curious about what it all can do, created a fake account with a test credit card as I read somewhere in the net.
Then downloaded the KFU 0.9.5 and rooted the device, everything went according to the plan, so I thought.
Then I discovered I had to use something called Market Opener to install other apps. But this Market Opener never worked.
So I found out that I had to change permissions. But this cannot happen as I get that message that adb services can not run in production builds etc. whatever that may mean.
So I downloaded Android SDK, followed the instructions installed it but I still cannot get into the root and change folder permissions. Sometimes it recognizes the device, sometimes not and when it does it tells me the same thing as above.
Then I would need some .apk to do the thing on the device but I cannot install those as I don't have the Market Opener or the Google Play and I cannot get those if I don't have superuser permissions to change things in Folders.
Basically I have been spending the last 3 days in searching the net for answers but to no avail.
So, can someone help me please? What I need to do is being able to install some apps including Market Opener / Google Play and being able to watch Amazon VOD. Is this possible?
Please bear in mind that I have no clue of the specific language, i.e. I don't know what flash is and how to do it nor I know how to do a backup and restore or how to reset everything in the original state.
SO if some of you have the patience to help, please advice me with some noob language so that I can understand.
Thanks in advance for the help that will come

Are you looking to put a custom rom on it or just root? If you're looking to keep Amazon services, you can put MoDaCo's rom on it, which is just like your kindle out of the box with a few extra bells and whistles. There are alot of guides floating around on how to get ADB working. There's an excellent beginners guide in the General section that I highly advise checking out.
Noob terms: if you want to keep the Amazon experience, I reccomend MoDaCo. Look for it in the development fourms.

brainchow said:
Are you looking to put a custom rom on it or just root? If you're looking to keep Amazon services, you can put MoDaCo's rom on it, which is just like your kindle out of the box with a few extra bells and whistles. There are alot of guides floating around on how to get ADB working. There's an excellent beginners guide in the General section that I highly advise checking out.
Noob terms: if you want to keep the Amazon experience, I reccomend MoDaCo. Look for it in the development fourms.
Click to expand...
Click to collapse
Thanks for ur answer.
I have read a lot of guides out there but I seem not to be able to get the ADB working as I always get the message I gave in the original post plus the fact that sometimes it recognizes the device and sometimes not.
I have read the beginners guide which was excellent but without the ADB working there is little I can do I suppose.
As I wrote, I want to play with the device to see what it is able to do and want to use the Amazon VOD if possible. I.e. I would like to be able to use Google Play to get apps on will and still keep the Amazon services. Would that be possible with the MoDaCo staff?
Ok. I downloaded the MoDaCo staff.
Must I reset the kindle to the factory settings before I install that? If yes, how?
And how do I flash it?

Make sure you are in fact rooted.
You seem like you know enough about adb to try the following commands.
adb shell
ls /system/xbin
Look for a file called "su" in the list
Then...
ls /system/app
Look for a file called "Superuser.apk"
A lack of either of these means you're not rooted and may be the source of your problems
If you are trying to change system file permissions through adb...
adb root
adb remount
adb shell chmod blah /blah/blah/yadayada
Just don't literally type "blah /blah/blah/yadayada"
Sent from my Amazon Kindle Fire using xda premium

a factory reset won't really help you because you're basically replacing the operating system. pretty sure all amazon services are working with modaco. to install it, look around for a guide on how to install something called firefirefire (FFF) and TWRP. pretty sure that can all be done with kfu in a couple clicks. then copy the modaco zip onto your kindle, go into the wipe menu and clear out system, cache, dalvik cache, and data (factory reset), then go into install and choose the modaco zip. reboot and you should be set.

soupmagnet said:
Make sure you are in fact rooted.
You seem like you know enough about adb to try the following commands.
adb shell
ls /system/xbin
Look for a file called "su" in the list
Then...
ls /system/app
Look for a file called "Superuser.apk"
A lack of either of these means you're not rooted and may be the source of your problems
If you are trying to change system file permissions through adb...
adb root
adb remount
adb shell chmod blah /blah/blah/yadayada
Just don't literally type "blah /blah/blah/yadayada"
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Thank you for your answer.
I would gladly follow your advice but the adb does not find my device. I don't know whether this is normal and if I must reboot my PC.
The kfu also gives me an offline status...

brainchow said:
a factory reset won't really help you because you're basically replacing the operating system. pretty sure all amazon services are working with modaco. to install it, look around for a guide on how to install something called firefirefire (FFF) and TWRP. pretty sure that can all be done with kfu in a couple clicks. then copy the modaco zip onto your kindle, go into the wipe menu and clear out system, cache, dalvik cache, and data (factory reset), then go into install and choose the modaco zip. reboot and you should be set.
Click to expand...
Click to collapse
Thanks again for the fast answer. I am impressed!
Doesn't the FFF and the TWRP get installed automatically with the kfu?

its most likely your computer. a reboot might help. if not, how did you install the drivers? are you using a mac or pc? try installing the drivers that came bundled with KFU.
if you're using a PC, go into device manager and see if something about android ADB pops up. if not, it's your drivers.
---------- Post added at 07:53 PM ---------- Previous post was at 07:51 PM ----------
GreekCY said:
Thanks again for the fast answer. I am impressed!
Doesn't the FFF and the TWRP get installed automatically with the kfu?
Click to expand...
Click to collapse
haha, no problem .
if FFF was installed, you should see a picture of fire in a caution sign or an android logo over the kindle fire logo when you boot it up. if all you see is kindle fire, then you don't have fff. im pretty sure you need fff to get into twrp. if fff is installed, you should be able to hop into fastboot and install twrp if it's not installed yet.

brainchow said:
its most likely your computer. a reboot might help. if not, how did you install the drivers? are you using a mac or pc? try installing the drivers that came bundled with KFU.
if you're using a PC, go into device manager and see if something about android ADB pops up. if not, it's your drivers.
Click to expand...
Click to collapse
I am using a PC ( a netbook, don't laugh, I'm on vacation!!)
I installed the drivers using the install_bat from the kfu.
In device manager I see Android Phone and underneath Android Composite ADB Interface...

interesting. check my previous post and see if you have FFF installed. adb should be working fine if device manager can find it. if you can, run adb devices into cmd and see if it picks up your kindle. not sure if the stock rom has a development switch in the settings.. if there's an option to enable usb debugging, make sure that is on. if not, just try moving usb ports and running adb devices.

If adb has trouble recognizing your device, it means it's a driver issue. Either Windows, KFU or a combination of the two causes the drivers to fail for some reason.
Uninstall/delete your current drivers in device manager (may require reboot)
Turn your Kindle off
Reinstall drivers
Turn your Kindle on
Retry adb commands
Sent from my Amazon Kindle Fire using xda premium

brainchow said:
interesting. check my previous post and see if you have FFF installed. adb should be working fine if device manager can find it. if you can, run adb devices into cmd and see if it picks up your kindle. not sure if the stock rom has a development switch in the settings.. if there's an option to enable usb debugging, make sure that is on. if not, just try moving usb ports and running adb devices.
Click to expand...
Click to collapse
I have FFF as I see the fire in a caution sign (yellow triangle thing right?)
ADB still doesn't pick my kindle after a PC restart.
No usb debugging available in the stock rom.
I will uninstall and reinstall the drivers from device manager.
Thanks again for your prompt help. I am oblidged!

GreekCY said:
I have FFF as I see the fire in a caution sign (yellow triangle thing right?)
ADB still doesn't pick my kindle after a PC restart.
No usb debugging available in the stock rom.
I will uninstall and reinstall the drivers from device manager.
Thanks again for your prompt help. I am oblidged!
Click to expand...
Click to collapse
that's fantastic... if you have FFF, try pressing the power button a couple times as it turns on and see if you can get into recovery. you shouldn't need adb now. if you can get into recovery, just wipe and flash the new rom. if you don't, you can use fastboot to install it.

brainchow said:
that's fantastic... if you have FFF, try pressing the power button a couple times as it turns on and see if you can get into recovery. you shouldn't need adb now. if you can get into recovery, just wipe and flash the new rom. if you don't, you can use fastboot to install it.
Click to expand...
Click to collapse
Ok...I reinstalled the drivers
now ADB gets the kindle
I do adb shell
then ls / system /xbin
no such file or directrory
the same goes with the
ls / system / app
But if I give su I get
su
#
Now what?
And in which directory should I transfer the MoDaCo Rom?

GreekCY said:
Ok...I reinstalled the drivers
now ADB gets the kindle
I do adb shell
then ls / system /xbin
no such file or directrory
the same goes with the
ls / system / app
But if I give su I get
su
#
Now what?
Click to expand...
Click to collapse
SU (substitute user) in shell is different from the su binary
Make sure you are typing "L"s, not "i"s then /system/xbin
Sent from my Amazon Kindle Fire using xda premium

soupmagnet said:
SU (substitute user) in shell is different from the su binary
Make sure you are typing "L"s, not "i"s then /system/xbin
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I really do type "L"...still ls/system/xbin: not found

modaco can go anywhere in the kindle.. just copy it somewhere. then press the power button a couple times when FFF comes up and see if you can get into twrp.

brainchow said:
modaco can go anywhere in the kindle.. just copy it somewhere. then press the power button a couple times when FFF comes up and see if you can get into twrp.
Click to expand...
Click to collapse
Guys? I just installed ModaCo and it seems it works fine. Google Play seems to work and all my data are still there (I mean the books I uploaded). If this is right then.... THANKS TO ALL OF YOU SO MUCH!!!!
Drinks are on me! Now I go to sleep! Will keep you informed!!!
Thanks again!!!!

GreekCY said:
I really do type "L"...still ls/system/xbin: not found
Click to expand...
Click to collapse
Space between ls and /system/xbin and no other spaces
It IS there, your Kindle wouldn't work otherwise
Sent from my Amazon Kindle Fire using xda premium

GreekCY said:
I really do type "L"...still ls/system/xbin: not found
Click to expand...
Click to collapse
if you want to use adb, should be ls /system/xbin. make sure you put the space after the ls. i would still recommend flashing modaco nevertheless... that shouldn't need adb. just maybe fastboot if your recovery isnt installed.
---------- Post added at 08:59 PM ---------- Previous post was at 08:57 PM ----------
GreekCY said:
Guys? I just installed ModaCo and it seems it works fine. Google Play seems to work and all my data are still there (I mean the books I uploaded). If this is right then.... THANKS TO ALL OF YOU SO MUCH!!!!
Drinks are on me! Now I go to sleep! Will keep you informed!!!
Thanks again!!!!
Click to expand...
Click to collapse
no problem... enjoy
i would still recommend wiping data and the two caches to ensure that it's bug free. but if everything works fine, so be it.
have fun

[Q] demo unit unsuccessful

hey guys. I have a demo unit.
Now before anything else, I should say that I looked at all three other threads on demo units, and that didn't help.
I looked at ThePooch's alternate method, and it didn't work.
In KFU, it gives the output of what is in the picture.
and in Soupkit, it says "permission denied" when trying to install either FFF or TWRP (I can't remember which, but if this is important, I will find out).
Can someone shed some info on what to do?
More pics are available to those who ask.

jma9454 said:
hey guys. I have a demo unit.
Now before anything else, I should say that I looked at all three other threads on demo units, and that didn't help.
I looked at ThePooch's alternate method, and it didn't work.
In KFU, it gives the output of what is in the picture.
and in Soupkit, it says "permission denied" when trying to install either FFF or TWRP (I can't remember which, but if this is important, I will find out).
Can someone shed some info on what to do?
More pics are available to those who ask.
Click to expand...
Click to collapse
Use SoupKit to change the bootmode to fastboot, then install TWRP. See if that helps.

soupmagnet said:
Use SoupKit to change the bootmode to fastboot, then install TWRP. See if that helps.
Click to expand...
Click to collapse
This could be the VMWare problem that you were mentioning in the other thread. upon reboot, VMWare says something to the effect that it could not connect to the kindle because it is in use by another program. I will try USB-Ubuntu in a few hours, but I think it didn't work last night, if i remember correctly.

I have witnessed one demo unit that was completely unrootable even with the use of a factory cable. So at the end it was only good for parts and the motherboard unusable.

soupmagnet said:
Use SoupKit to change the bootmode to fastboot, then install TWRP. See if that helps.
Click to expand...
Click to collapse
when trying to switch bootmodes, Ubuntu just reboots the kindle. It isn't able to get into fastboot. If I could figure out how to take a screeshot of this I would, but I don't know how.
Anyways, I forgoed that, and tried to just do the TWRP installation and this is what I got:
Verifying MD5 checksum...
openrecovery-twrp-2.2.2.1-blaze.img: OK
Checksum matched.
Installing openrecovery-twrp-2.2.2.1-blaze:
Please wait...
1122 KB/s (4972544 bytes in 4.324s)
/dev/block/mmcblk0p5: cannot open for write: Permission denied
Team Win Recovery Project has been installed.
Do you wish to reboot into recovery now?
-- any ideas?

That`s pretty much what I experienced with the demo unit that would not root, it simply would not enter fastboot no matter which approach I took. I can take a look for you but I feel it`s pretty much a moot point if it wont enter fastboot. Power the device off, open a terminal
Code:
fastboot -i 0x1949 getvar product
hit enter, when it says waiting for device, plug the kindle in. if it does not enter fastboot and return product: kindle you are dead in the water.

jma9454 said:
This could be the VMWare problem that you were mentioning in the other thread. upon reboot, VMWare says something to the effect that it could not connect to the kindle because it is in use by another program. I will try USB-Ubuntu in a few hours, but I think it didn't work last night, if i remember correctly.
Click to expand...
Click to collapse
I've really gotta start reading the names on these posts
jma9454 said:
when trying to switch bootmodes, Ubuntu just reboots the kindle. It isn't able to get into fastboot. If I could figure out how to take a screeshot of this I would, but I don't know how.
Anyways, I forgoed that, and tried to just do the TWRP installation and this is what I got:
Verifying MD5 checksum...
openrecovery-twrp-2.2.2.1-blaze.img: OK
Checksum matched.
Installing openrecovery-twrp-2.2.2.1-blaze:
Please wait...
1122 KB/s (4972544 bytes in 4.324s)
/dev/block/mmcblk0p5: cannot open for write: Permission denied
Team Win Recovery Project has been installed.
Do you wish to reboot into recovery now?
-- any ideas?
Click to expand...
Click to collapse
That's the tricky thing about ADB and shell scripts. I won't go into too much detail, but part of that has to do with how ADB handles the exit status. Typically in Linux, an error results in an exit status of 2 (sometimes 1 depending on the type of error). ADB tends to have errors come out with an exit status of 0, which is why it said TWRP had been installed, when in all actuality it hadn't. The reason TWRP wasn't installed is because you need to either have root privileges, or be in fastboot, hence my previous instructions to boot into fastboot first.
In my opinion, your best bet would be to forgo the VM, forget about the dilapidated WinXP computer and figure out a way to boot your Win7 computer into Ubuntu from a USB stick. You are dealing with way too many variables to effectively determine exactly where things are going wrong.

I 'fixed' two demo KF's, messed up a lot on the first (lucky I didn't brick it).... On the second, I used a fast boot cable and installed TWRP, had a JB ROM on it in 15 minutes.
Try this.... Send TWRP to it using the command line, when it says 'waiting on device', open another window and get it to reboot in fastboot mode. On the first KF I found the utility would only put it in fast boot for a few seconds, but it was long enough to write TWRP if you did it this way.
Not sure why some won't work at all, maybe Amazon got smart on the demo units.
Larry
Sent from my Kindle Fire that thinks it's a Nexus 7

soupmagnet said:
I've really got to start reading the names on these posts
That's the tricky thing about ADB and shell scripts. I won't go into too much detail, but part of that has to do with how ADB handles the exit status. Typically in Linux, an error results in an exit status of 2 (sometimes 1 depending on the type of error). ADB tends to have errors come out with an exit status of 0, which is why it said TWRP had been installed, when in all actuality it hadn't. The reason TWRP wasn't installed is because you need to either have root privileges, or be in fastboot, hence my previous instructions to boot into fastboot first.
Click to expand...
Click to collapse
The above statement took place from USB boot, not VMware. Also, like I said, I attempted to set it into fastboot and it just booted regularly. I tried several times with different cables and ports with no success.
Sent from my Amazon Kindle Fire using Tapatalk HD

I will stick with my original idea no fastboot = no fun. You cant push FBmode manually because installation from unknown sources is disabled by default on a large percentage if not all demo units. Regardless if the device doesn`t enter fastboot not much you can do. Taking advantage of the small window of fastboot at boot is risky if the write time isn`t long enough to get it sent and written but it could be your best bet. IMO I would not attempt this with the bootloader only recovery no harm no fowl.

[Q] My S3 stuck in boot loop

Hello,
if is one here to help me i wil give him thousands bottles with beers.
My s3 is stuck in boot loop, i cant to pass samsung logo, i cant to go in cwm or download mode. I have tried to connect on my pc via usb cable but nothing is happening, i have all drivers installed but odin cant to recognized my phone, i think debugging mode is off. When the phone is off and i connect the charger he show me battery what he trying to get power but is not green.
I attach two photos to be more suggestive.
How can to pass this logo to go in cwm or to make this phone to be recognized by odin?
Thank you for reading me and for your answers.
regards,
florin

DobreaFlorin said:
Hello,
if is one here to help me i wil give him thousands bottles with beers.
My s3 is stuck in boot loop, i cant to pass samsung logo, i cant to go in cwm or download mode. I have tried to connect on my pc via usb cable but nothing is happening, i have all drivers installed but odin cant to recognized my phone, i think debugging mode is off. When the phone is off and i connect the charger he show me battery what he trying to get power but is not green.
I attach two photos to be more suggestive.
How can to pass this logo to go in cwm or to make this phone to be recognized by odin?
Thank you for reading me and for your answers.
regards,
florin
Click to expand...
Click to collapse
First question.. Do you have the I9300 (is the international version of the S3) Sprint version is SPH-L710.. If you have the 710 and flashed I9300 stuff.. you probably bricked your phone. If you DO have the I9300 version, I would pop over to that section of the forums and ask there... Here's the I9300 Section. http://forum.xda-developers.com/forumdisplay.php?f=1563
They are not compatible sadly due to different hardware, so flashing something from here will break your I9300.

Ive been where you are about three times. What i have had to do is plug my phone into the computer and have terminal or cmd prompt open.
I have to navigate to a folder that has ADB in it.
I start the bootloop on the phone and when i see the samsung logo boot up i execute the command
./adb reboot recovery
in windows i think you have to go
adb
reboot recovery
not sure though because i currently dont have a windows machine at my disposal. But you have to time this right. There is a few seconds in the bootloop where you have the ability to adb into the phone and force it to reboot into recovery this way you can flush the bad rom/kernel you accidentally flashed.
Hope this helps.

Thank you for your helpp, quick answers, you are the best form internet. All the time i get solve here in xda.
Solved, my battery it was under 25% and he cant to pass on download mode, i charged to 100% and now i can to flash what i want in download mode.
Thank you again for your quick answers.
Regards,
Florin

Hamspiced said:
Ive been where you are about three times. What i have had to do is plug my phone into the computer and have terminal or cmd prompt open.
I have to navigate to a folder that has ADB in it.
I start the bootloop on the phone and when i see the samsung logo boot up i execute the command
./adb reboot recovery
in windows i think you have to go
adb
reboot recovery
not sure though because i currently dont have a windows machine at my disposal. But you have to time this right. There is a few seconds in the bootloop where you have the ability to adb into the phone and force it to reboot into recovery this way you can flush the bad rom/kernel you accidentally flashed.
Hope this helps.
Click to expand...
Click to collapse
hello can you please be specific how to go in adb folder can you please assist with if some kind of tutorial is there I have the same problem and I havent slept from last two nights trying to solve it please help me

rishidgr8143 said:
hello can you please be specific how to go in adb folder can you please assist with if some kind of tutorial is there I have the same problem and I havent slept from last two nights trying to solve it please help me
Click to expand...
Click to collapse
What S3 do you have and exactly what is wrong with it?
Have a great day!

edfunkycold said:
What S3 do you have and exactly what is wrong with it?
Have a great day!
Click to expand...
Click to collapse
I have GT-I9305
i installed cm 10.2 few days ago
it restarted suddenly and keeps restarting again and again
I cant enter into recovery mode nor in download mode
I some how manage to enter into recovery mode it starts again and give no time wipe factory data same is with download mode
please help me

rishidgr8143 said:
I have GT-I9305
i installed cm 10.2 few days ago
it restarted suddenly and keeps restarting again and again
I cant enter into recovery mode nor in download mode
I some how manage to enter into recovery mode it starts again and give no time wipe factory data same is with download mode
please help me
Click to expand...
Click to collapse
Ok your in the wrong section, this is Sprint d2spr. So you should be posting in the forum for your device.
But most likely what you have is SDS sudden death syndrome. Which means your power button has failed. Very common on the S3 devices. Try jiggling the power button maybe blowing some compressed air into the power button area. See if it will dislodge. It is a known defect.
Have a great day!

edfunkycold said:
Ok your in the wrong section, this is Sprint d2spr. So you should be posting in the forum for your device.
But most likely what you have is SDS sudden death syndrome. Which means your power button has failed. Very common on the S3 devices. Try jiggling the power button maybe blowing some compressed air into the power button area. See if it will dislodge. It is a known defect.
Have a great day!
Click to expand...
Click to collapse
Thanks I will try doing that. I hope this works

Stuck at splash screen.
Help! I have a D2SPR and was flashing my nightly for 9/6/13 CM10.2... and now I can't get past the splash screen. What, if anything, can I do to get recovery to boot? (yes, it was a dirty flash(

Power button + volume up + home button at same time should get you into recovery.
Have a great day!

same issue
I have the Sprint SPH-L710 and flashed a Cyanogenmod nightly this morning. At this point, the phone will not boot. I can get to the Samsung screen but there it hangs. I can also get the phone connected to a computer and Odin sees it but I can't do much else with it. Any thoughts on how to force it into recovery from Odin? Any help would be much appreciated.

midkemiapug said:
I have the Sprint SPH-L710 and flashed a Cyanogenmod nightly this morning. At this point, the phone will not boot. I can get to the Samsung screen but there it hangs. I can also get the phone connected to a computer and Odin sees it but I can't do much else with it. Any thoughts on how to force it into recovery from Odin? Any help would be much appreciated.
Click to expand...
Click to collapse
I was able to get into recovery mode after flashing the CWM recovery mod from here: http://forum.xda-developers.com/showthread.php?t=2391616. I also took a look at the Cyanogenmod forum here: http://forum.cyanogenmod.com/topic/77958-20130906-stuck-on-boot-screen-dont-install/.

johnbistricky said:
Help! I have a D2SPR and was flashing my nightly for 9/6/13 CM10.2... and now I can't get past the splash screen. What, if anything, can I do to get recovery to boot? (yes, it was a dirty flash(
Click to expand...
Click to collapse
Pull battery then do the recovery button combo. It is a a known issue that that nightly doesn't boot. You could just dirty flash another nightly that does work. May break some things though.
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!

@rishidgb
what ive had to do in the past to resolve these issues. Ill Copy/Paste the instructions i have used to Install ADB on my past computers but ill also throw links for the origionals at the bottom of the post.
1. Verify Battery is at least 50% charged. I usually do this by turning the phone off and plugging it into the charger, you should be able to see the battery charging up.
2. Install ADB on your computer. I have a mac, and this was kind of a pain in the ass to do at first but ill explain.
Mac-
1. Download the latest Android SDK from Google: Android SDK - http://developer.android.com/sdk/index.html
2. Extract the ZIP file to your desired location
3. To get ADB, you need to install the SDK: Installing the SDK - http://developer.android.com/sdk/installing/index.html
If you are not a developer and not planning to develop, then just download the following zip file containing only the ADB tool and
proceed with the tutorial: ADB - http://esausilva.com/wp-content/plu...silva.com/misc/android/platform-tools-osx.zip
Create an environment variable (Optional) **This is good because once you create the variable you dont have to navigate to the ADB folder every time to use it.
1. Open Terminal
2. Type cd ~ this will take you to your home directory
3. Type touch .profile this will create a hidden file named profile
4. Type open -e .profile this will open the file you just created in TextEdit
In the file, type export PATH=${PATH}:/pathToTheAndroidSdkFolder/android-sdk-mac_86/platform-tools
Save file, close TextEdit, Quit Terminal, and Relaunch Terminal
NOTE: By creating an environment variable you won’t need to cd to the Android/tools folder every time you want to run ADB
You are good to go, type in terminal adb devices, this should give you a serial number, which corresponds to your phone. Looks something like this:
List of devices attached
HT99PHF02521 device
NOTE: If you did not create an environment variable, then cd to the AndroidSDK/platform-tools folder, then type ./adb devices
Also make sure you have your phone plugged in and have USB Debugging turned on (Settings > Applications > Development)
In Android 4.2.x and up Developer Options is hidden, to make it visible, do the following
Tap seven times in Build Number: Settings > About Phone > Build Number
You will get a message saying you have enabled Developer Options or something like that, go back to Settings and you will see Developer Options in there.
PC-
Step 1: Head over to this link to download the latest version of Android SDK. http://developer.android.com/sdk/index.html
Step 2: Extract the contents of the downloaded file to your hard drive. Within the unzipped “sdk” folder, you’ll find another folder labeled ‘platform-tools’. Since we’re interested in only ADB and Fastboot, this is the one that we’re looking for.
Step 3: Move the platform-tools folder to a convenient location on your PC. The root of C: drive is usually a good idea. I also recommend renaming the folder to something easier, like C:\Android-adb.
By this point, ADB is essentially set up, but to use it, you’ll first need to navigate your command prompt window to this Android-adb folder, and then run all ADB commands inside it. Since it’s too much hassle for most users, we’ll add this location to Windows’ System Path Variable, so you can run ADB commands from anywhere.
Step 4: Right-click the Computer icon on your desktop, and go to Properties.
Step 5: Under System Properties, go to the Advanced tab, and click Environment Variables.
Step 6: The system variables are contained within the lower pane. Locate “Path” here, highlight it, and click the Edit button.
Step 7: There will already be a string of locations here; navigate to the very end, and add the following text (assuming that you have chosen C:\Android-adb as the folder; otherwise, enter whatever path you’ve located adb at):
;C:\Android-adb
Click OK, finally.
Your ADB folder is now configured, and you can run both ADB and Fastboot commands from anywhere in command prompt. To verify, connect your Android device to PC with USB Debugging enabled, launch a command prompt window, and type “adb devices” (without quotes). The daemon will start up, and all connected devices will be listed.
Mac Instructions
http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/
Pc Instructions
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Now that ADB is installed. If you find yourself in a Bootloop, OR you find yourself in a situation where it wont pass by the boot animation, open up terminal or command prompt. Then type Adb Devices, it should recognize your device and list the serial. And from there you can use the command:
Adb Reboot Recovery
From there you can wipe/Factory Restore and then Flash a new rom.
If you cannot reboot recovery but ADB still sees your phone. You can use command ADB shell to open a linux command prompt through your phone to push and pull files. Ive done this to push roms when the phone wouldnt mount properly.
I know this isnt "THAT" thorough, however ADB has litterally saved my ass a BUNCH of times. Id reccomend setting it up if you flash frequently.
Sorry it took me a couple days to respond, i am not on XDA as much as i used to be.

RE:
Thanks for documenting this.
So any solutions/ideas to people who can't get our computer's to recognize our device? Unfortunately, that's the position I'm in

[Q] Kindle Fire BRICKED (Stuck On Kindle Logo) No Susses in CMD

Hello, I Have a Kindle Fire 1st Gen. I Had CM 10.1 on it. I was attempting to put AOSP back on it for My Wife. I did I Noobish Move at 4 am half asleep, I Did NOT go into advanced mode in TWRP and uncheck DATA in the Wipe tab. So This Screwed me "Bricked" Message comes up in TWRP when rebooting, says ( NO OS ) . I have Tried Kindle unbrick utility with no success when clicking on "Stuck at Logo" in utility I get this Error ...> PIC Attatched!>
I then Tried Using android-sdk ( I have went in and edited the files that need to be edited in program files/android...> File_android_winusb as well as in .android folder in the appdata location) Along with CMD & I get a Error So far into the process of Resetting Kindle OS. Pic Attatched as well. It Seems Like I have something missing ?!?!?
I somewhat Suck at CMD, I don't have much experience with it, so Please go slow on me,when Giving advise....
Thanks In Advance!!

If you still have access to TWRP, use it to mount your sdcard to USB.

soupmagnet said:
If you still have access to TWRP, use it to mount your sdcard to USB.
Click to expand...
Click to collapse
I Tried That. I See the Device But when double clicking, It will not let me access it.

Butt Nugget said:
I Tried That. I See the Device But when double clicking, It will not let me access it.
Click to expand...
Click to collapse
Oh that's right, it won't work on 2nd generation devices.
Do you have your drivers installed? Are you able to send any adb commands (adb devices)?

soupmagnet said:
Oh that's right, it won't work on 2nd generation devices.
Do you have your drivers installed? Are you able to send any adb commands (adb devices)?
Click to expand...
Click to collapse
My Kindle is a 1st Gen. I'm not sure If I understand what You are talking about when You say "send Commands/devices" If Your talking about in CMD I Get all the way to Seeing my Device Serial Number for Kindle. The when I type "adb shell" I get a error saying (Failed: No such file or directory <2> - ) You can see this in the screen shot I attached to this thread..

Sorry, I looked at what forum this was in and got a little confused...silly me :silly:
Anyway, back on track...
You should not be receiving that error in TWRP. If you are, then something is seriously wrong with it and probably needs to be reinstalled. Other than that, I'm having trouble seeing where the problem is. (the pic shows that you're not in recovery, btw)
You clearly have access to adb, so...why aren't you using 'adb push' to transfer a new ROM to your sdcard to flash in recovery?

soupmagnet said:
Sorry, I looked at what forum this was in and got a little confused...silly me :silly:
Anyway, back on track...
You should not be receiving that error in TWRP. If you are, then something is seriously wrong with it and probably needs to be reinstalled. Other than that, I'm having trouble seeing where the problem is. (the pic shows that you're not in recovery, btw)
You clearly have access to adb, so...why aren't you using 'adb push' to transfer a new ROM to your sdcard to flash in recovery?
Click to expand...
Click to collapse
I've Done searches and only found how to attempt recovery, typing in commands on pc's CMD Prompt while kindle is mounted to usb in twrp and typing commands in on CMD in pc I installed Android SDK and Device driver. So Sounds possibly what I tried is totally different from what Your asking if i done? If So, Could You Explain step by step thee method with new roms or send me in the right directions 2 a how to link or video? Anything I would appreciate GREATLY! :fingers-crossed:

Butt Nugget said:
I've Done searches and only found how to attempt recovery, typing in commands on pc's CMD Prompt while kindle is mounted to usb in twrp and typing commands in on CMD in pc I installed Android SDK and Device driver.
Click to expand...
Click to collapse
I have no idea what you're saying.
All you need to do is, boot into recovery (TWRP), use adb to "push" a ROM to your sdcard (adb push...), then install the ROM in recovery.

soupmagnet said:
I have no idea what you're saying.
All you need to do is, boot into recovery (TWRP), use adb to "push" a ROM to your sdcard (adb push...), then install the ROM in recovery.
Click to expand...
Click to collapse
I mentioned Earlier (say, the Drive of the device is :F) In My computer, When I click :F It states Cannot access (Drivers are installed for kindle). I'm asking How Can I Mount USB in TWRP and Put ROM File on sdcard when I cannot access it... I Do Not have a Micro USB OTG to USB 2.0 Cable to plug up to kindle with the files put on a external HD to complete this course.
Does that make more since?

Butt Nugget said:
I mentioned Earlier (say, the Drive of the device is :F) In My computer, When I click :F It states Cannot access (Drivers are installed for kindle). I'm asking How Can I Mount USB in TWRP and Put ROM File on sdcard when I cannot access it... I Do Not have a Micro USB OTG to USB 2.0 Cable to plug up to kindle with the files put on a external HD to complete this course.
Does that make more since?
Click to expand...
Click to collapse
Try to understand what you're being told. I'm not saying anything about mounting your sdcard to transfer files to it so get that idea out of your head for a moment.
You need to boot into recovery and use the command 'adb push' to transfer a ROM to your sdcard, then flash it in recovery.
Now, does that make more sense?

soupmagnet said:
Try to understand what you're being told. I'm not saying anything about mounting your sdcard to transfer files to it so get that idea out of your head for a moment.
You need to boot into recovery and use the command 'adb push' to transfer a ROM to your sdcard, then flash it in recovery.
Now, does that make more sense?
Click to expand...
Click to collapse
I am attempting to understand what u are saying But I'm thinking ur not giving full step after step instructions OR this Version I have (v2.6.0.0) differs from Yours, Because there is No such OPTION as ADB PUSH..... I have ADB sideload (under Advanced Tab) which only wipes Cashe.. I've looked in every single area in TWRP and see nothing of anything You are talking about, other than "MOUNT" obviously.

soupmagnet said:
Try to understand what you're being told. I'm not saying anything about mounting your sdcard to transfer files to it so get that idea out of your head for a moment.
You need to boot into recovery and use the command 'adb push' to transfer a ROM to your sdcard, then flash it in recovery.
Now, does that make more sense?
Click to expand...
Click to collapse
While Searching Google for Help I seen this..> http://forum.xda-developers.com/showthread.php?t=2361144
I'm bout to install a Pc with Linux and try pushing it that way.. Have not tried that.

You don't need Linux to run adb commands *face palm* While I am a linux enthusiast, all he's trying to say is boot into twrp, plug kindle into your PC, and open a command prompt, CD into the directory of adb and run "adb push pathtofile /sdcard/filename" this should push it to the kindle, though their might be something else u need for in prior to this I'm not sure, soupemagnet will probably post back if there is. BTW I don't know if u actually meant u were going to install Linux, but if you don't plan on using it after this or anything in the case u do decide to still use it for this, u don't need to install it, distros like Ubuntu let you boot into a full os from the CD so u don't need to install it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
You don't need Linux to run adb commands *face palm* While I am a linux enthusiast, all he's trying to say is boot into twrp, plug kindle into your PC, and open a command prompt, CD into the directory of adb and run "adb push pathtofile /sdcard/filename" this should push it to the kindle, though their might be something else u need for in prior to this I'm not sure, soupemagnet will probably post back if there is. BTW I don't know if u actually meant u were going to install Linux, but if you don't plan on using it after this or anything in the case u do decide to still use it for this, u don't need to install it, distros like Ubuntu let you boot into a full os from the CD so u don't need to install it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Stunt Thnx... You Helped breaking it down. I just used KFU and Fixed this within 3 minutes.. Thnx Man!:good:

Kindle fire 8.9 bricked need help

So I rooted my kindle fire 8.9 and installed a 2nd bootloader along with team win recovery the root went fine but as soon as I installed the 2nd bootloader the kindle dose not go past silver kindle fire page I can load custom recovery but nothing else
Someone please help me with this

So it won't boot into the os, but will go into recovery. That a been happening with the latest update apparently, if it detects twrp or the modded boot loader it throws a fit and won't boot, you need to push a rom to flash to twrp and either downgrade the os, or flash a custom ROM. To do this you need to know how to use command prompt and adb, so if you know that much you would run something like this: adb push filetoflash.zip /sdcard/filetoflash.zip
From there its a simple matter of installing the file from inside twrp. If you need more details just reply back.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
So it won't boot into the os, but will go into recovery. That a been happening with the latest update apparently, if it detects twrp or the modded boot loader it throws a fit and won't boot, you need to push a rom to flash to twrp and either downgrade the os, or flash a custom ROM. To do this you need to know how to use command prompt and adb, so if you know that much you would run something like this: adb push filetoflash.zip /sdcard/filetoflash.zip
From there its a simple matter of installing the file from inside twrp. If you need more details just reply back.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for that is there any tutorials on this?

Eh idk if there's a tutorial for this exactly but there are plenty of threads with this problem and something similar where they accidentally wiped the internal storage and had to do same thing that you are having to do basically. I can point you in the right direction, just tell me what ROM you want on it, and I'll do my best to give you some instructions to get it onto the device.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Eh idk if there's a tutorial for this exactly but there are plenty of threads with this problem and something similar where they accidentally wiped the internal storage and had to do same thing that you are having to do basically. I can point you in the right direction, just tell me what ROM you want on it, and I'll do my best to give you some instructions to get it onto the device.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
cm 10.1 i guess just want to get this fixed so all help is appreciated don't want to have to throw the kindle away

OK sorry for the long wait, my friend bought me a copy of reach today since it was the only halo game I hadn't played so I put off writing a small tutorial until I was done.
First you need a working copy of adb, and your drivers working with twrp, so if you don't have a copy of adb handy, download my wallpaper fix and extract it so that there's a folder on the c drive called"stunts wallpaper fix", if you have adb somewhere else, just adjust how I say to do that to using the other path. So after u have extracted my fix to c:\, you should open the folder and see adb.exe in there, now download these 2 files into that folder:
http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130812-UNOFFICIAL-jem.zip
http://goo.im/gapps/gapps-jb-20130812-signed.zip
Now boot the kindle into twrp and plug it i to your pc and open a command prompt, I usually do it from a run box but searching the start menu for it works also. Once its open type "CD c:\stunts wallpaper fix" and press enter, now type "adb.exe devices" and make sure your device is listed' if it isn't open the device manager and check for a device with a triangle, if there is use the driver link in my signature to update the drivers to that and it should work. Anyways if your drivers are going well and it lists itself under devices, type this into command prompt "adb.exe push cm-10.1-20130812-UNOFFICIAL-jem.zip /sdcard/", then when it's done type "adb.exe push gapps-jb-20130812-signed.zip /sdcard/". If all goes well the files should be on the device, if you are coming from stock amazon I would tell twrp to backup only the data partition, since your system partition is kinda useless at this point, and once u have a backup you need to do a factory reset under wipe I believe, I don't remember for sure so I'll say do this even though the factory reset probably covers most of this, do a advanced wipe as well, only check cache, dalvik cache, and system. Now tell it to wipe. Once that is done hit install on the home screen and choose the cm 10.1 file on the sdcard first, and swipe to install it, then once done go to install again and choose the gapps and install it too, now reboot into the system. Tada!
If this is confusing or you need help with something else just post back, I know I didn't exactly organize this post very well but I kinda did it from my kindle so it wasn't easy to format it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
OK sorry for the long wait, my friend bought me a copy of reach today since it was the only halo game I hadn't played so I put off writing a small tutorial until I was done.
First you need a working copy of adb, and your drivers working with twrp, so if you don't have a copy of adb handy, download my wallpaper fix and extract it so that there's a folder on the c drive called"stunts wallpaper fix", if you have adb somewhere else, just adjust how I say to do that to using the other path. So after u have extracted my fix to c:\, you should open the folder and see adb.exe in there, now download these 2 files into that folder:
http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130812-UNOFFICIAL-jem.zip
http://goo.im/gapps/gapps-jb-20130812-signed.zip
Now boot the kindle into twrp and plug it i to your pc and open a command prompt, I usually do it from a run box but searching the start menu for it works also. Once its open type "CD c:\stunts wallpaper fix" and press enter, now type "adb.exe devices" and make sure your device is listed' if it isn't open the device manager and check for a device with a triangle, if there is use the driver link in my signature to update the drivers to that and it should work. Anyways if your drivers are going well and it lists itself under devices, type this into command prompt "adb.exe push cm-10.1-20130812-UNOFFICIAL-jem.zip /sdcard/", then when it's done type "adb.exe push gapps-jb-20130812-signed.zip /sdcard/". If all goes well the files should be on the device, if you are coming from stock amazon I would tell twrp to backup only the data partition, since your system partition is kinda useless at this point, and once u have a backup you need to do a factory reset under wipe I believe, I don't remember for sure so I'll say do this even though the factory reset probably covers most of this, do a advanced wipe as well, only check cache, dalvik cache, and system. Now tell it to wipe. Once that is done hit install on the home screen and choose the cm 10.1 file on the sdcard first, and swipe to install it, then once done go to install again and choose the gapps and install it too, now reboot into the system. Tada!
If this is confusing or you need help with something else just post back, I know I didn't exactly organize this post very well but I kinda did it from my kindle so it wasn't easy to format it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thank you so much you guide has fixed the brick I am now running cm.

stunts513 said:
OK sorry for the long wait, my friend bought me a copy of reach today since it was the only halo game I hadn't played so I put off writing a small tutorial until I was done.
First you need a working copy of adb, and your drivers working with twrp, so if you don't have a copy of adb handy, download my wallpaper fix and extract it so that there's a folder on the c drive called"stunts wallpaper fix", if you have adb somewhere else, just adjust how I say to do that to using the other path. So after u have extracted my fix to c:\, you should open the folder and see adb.exe in there, now download these 2 files into that folder:
http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130812-UNOFFICIAL-jem.zip
http://goo.im/gapps/gapps-jb-20130812-signed.zip
Now boot the kindle into twrp and plug it i to your pc and open a command prompt, I usually do it from a run box but searching the start menu for it works also. Once its open type "CD c:\stunts wallpaper fix" and press enter, now type "adb.exe devices" and make sure your device is listed' if it isn't open the device manager and check for a device with a triangle, if there is use the driver link in my signature to update the drivers to that and it should work. Anyways if your drivers are going well and it lists itself under devices, type this into command prompt "adb.exe push cm-10.1-20130812-UNOFFICIAL-jem.zip /sdcard/", then when it's done type "adb.exe push gapps-jb-20130812-signed.zip /sdcard/". If all goes well the files should be on the device, if you are coming from stock amazon I would tell twrp to backup only the data partition, since your system partition is kinda useless at this point, and once u have a backup you need to do a factory reset under wipe I believe, I don't remember for sure so I'll say do this even though the factory reset probably covers most of this, do a advanced wipe as well, only check cache, dalvik cache, and system. Now tell it to wipe. Once that is done hit install on the home screen and choose the cm 10.1 file on the sdcard first, and swipe to install it, then once done go to install again and choose the gapps and install it too, now reboot into the system. Tada!
If this is confusing or you need help with something else just post back, I know I didn't exactly organize this post very well but I kinda did it from my kindle so it wasn't easy to format it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Ok how do you use the driver link from your signature, I'm using windows 8 and can't get any drivers to install. I sold my kindle and now it's stuck on the blue kindle fire logo. I stupidly wiped everything including system in twrp .

Windows 8 is a bit more tricky because you have to boot the os up with driver signature enforcement disabled, look it up on Google, once you do that you go into the device manager a d find the device with an exclamation and hit update driver, then browse to the folder where you extracted the files from the zip in my signature,
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Windows 8 is a bit more tricky because you have to boot the os up with driver signature enforcement disabled, look it up on Google, once you do that you go into the device manager a d find the device with an exclamation and hit update driver, then browse to the folder where you extracted the files from the zip in my signature,
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks .. I'll give it a go tonight