Related
Sorry guys, I've been reading all night trying to figure this out, and now my brain's all twisted, and I feel like I'm missing something obvious...
Is there a super-quick way to boot the Fire into fastboot mode once you already have FFF, TWRP, and a rooted rom installed??
The threads I've been reading all night seem to be geared to someone who doesn't have all that installed yet.
Can it be done with terminal emulator on the fire?
I had assumed it could be accessed from TWRP, but no dice. Would a quickboot app from the market get me there, like on almost every device I've used before?
Because of driver issues (that I still haven't solved) the only way I've done it before is when I installed FFF, and TWRP by shorting the board and using Ubuntu from a USB stick. (I'm wanting to switch from just having an ICS Rom to dual-booting, and I have everything ready, but I just am getting confused over how to simply get onto fastboot to accomplish this.
Thanks to anyone in advance that might help...
An easy way would be to use kfu and select boot mode 4000. Or u can just use the fast boot command
Sent from my Amazon Kindle Fire using xda app-developers app
powerpoint45 said:
An easy way would be to use kfu and select boot mode 4000. Or u can just use the fast boot command
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
I need windows to recognize it that way though. That's the whole problem... I've NEVER gotten windows to pick it up but one time... Weeks ago.. Then it was softbricked.. Tried everything and finally had to use the shorting trick with the Ubuntu stick.
No, this post is about me asking if there's some other way once I've installed FFF, TWRP, and am rooted. (Like terminal emulator or something like a rooted app from the Play Store.)
Sent from my SPH-D710 using xda premium
Apparently, I can solve all my headaches by just using a factory cable?
Okay...Here's my problem there:
I've probably got 12-15 Android tablets around the house, and at least 6 phones: The number of USB cables for these devices I've collected is just silly, what with extra chargers and whatnot...
I'm sure one of them is a factory cable from when I opened my Fires.
Could anyone please, upload a picture of THEIR factory cable so I can figure out which one is which? I promise to shut up about fastboot for a while if anyone could do me that solid.
Sent from my Galaxy Nexus using Tapatalk 2
If you bought a skorpn it should have a scorpion logo on it
---------- Post added at 12:21 AM ---------- Previous post was at 12:16 AM ----------
Easiest way to get into fastboot shift+right click on the tools folder in kfu select open command window here power off your kindle leave it unplugged type fastboot -i 0x1949 getvar product (hit enter) it will say waiting for device plug your kindle in it will power on in fastboot mode it should return product : kindle
---------- Post added at 12:25 AM ---------- Previous post was at 12:21 AM ----------
When you want to go back to normal type fastboot -i 0x1949 oem idme bootmode 4000 (hit enter) then type fastboot -i 0x1949 reboot (hit enter) it will then boot normal
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
No pun intended but with all the hassle and questions dualboot sounds like a poor choice but hey your kindle
Thepooch said:
If you bought a skorpn it should have a scorpion logo on it
---------- Post added at 12:21 AM ---------- Previous post was at 12:16 AM ----------
Easiest way to get into fastboot shift+right click on the tools folder in kfu select open command window here power off your kindle leave it unplugged type fastboot -i 0x1949 getvar product plug your kindle in it will power on in fastboot mode it should return product : kindle
Click to expand...
Click to collapse
No, brother: I'm just talking about the regular stock cable that came in the Amazon box: I have no idea which ones out of the jillion cords I have's the right one.
I'll try your recommendation above...just a minute, I'm booted into Ubuntu right now.
Sent from my Galaxy Nexus using Tapatalk 2
Most micro usb to standard work fine I use the one for my droidx all the time
---------- Post added at 12:44 AM ---------- Previous post was at 12:37 AM ----------
Also if your using linux you will need to have fastboot setup on it if you ran andadb script add sudo to the lead of all your commands
Thepooch said:
Most micro usb to standard work fine I use the one for my droidx all the time
Click to expand...
Click to collapse
Well, I've got a ton of cords. If any work, then what's all the talk about using factory cables for, or the jigs that replicate the connection that people sell?
Btw, I just tried the command from above in Ubuntu: no luck (the command went thru in kfu, but said "waiting for device"). Trying windows next, but I've got a feeling that won't work, as my drivers have never gotten to work right.
Sent from my SPH-D710 using xda premium
Yeah, Windows didn't care one bit when I plugged it in and turned it on. Booted straight into ICS, and still says waiting for device in the terminal.
See, I've been doing this stuff for hours... I know how to try this:
I just wanted to know if, with FFF and TWRP, and the ability to run Su in terminal emulator, if there might be an easier way.
Sent from my SPH-D710 using xda premium
Edit: Solved, thanks to Thepooch, who spent a lot of time on Teamviewer setting up a toolkit on a linux USB. No more headaches.
can someone point me in the right direction on how to put factory recovery and rom back on my neighbors kindle fire so he can return it im not familar with kindle fire but did many android and windows before thanks
*Go here and download software http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620
*Rename file to update.zip.
*Now go into twrp and do a FULL WIPE then install the file. Thats all their is to it. Ive done it before.
powerpoint45 said:
*Go here and download software http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620
*Rename file to update.zip.
*Now go into twrp and do a FULL WIPE then install the file. Thats all their is to it. Ive done it before.
Click to expand...
Click to collapse
Will take off the twrp recovery as well? He wants to return it to bestbuy for refund
maxtcee said:
Will take off the twrp recovery as well? He wants to return it to bestbuy for refund
Click to expand...
Click to collapse
yes it will remove twrp make sure you do a full wipe before attempting or you could get some mild brickage requiring a factory cable. wipe factory reset,wipe cache,wipe dalvik, wipe system, flash update.zip reboot then system if prompted...
i wipe everything like you said and for some reason it boots into logo screen then a black screen and stays black i cant seem to get it back into recovery
Use adb shell and Pokey9000's rcmode (or the command line if possible) to change your bootmode to recovery and try it again. Be sure to wipe System and Factory Reset.
If you can't open a shell, you need a factory cable.
soupmagnet said:
Use adb shell and Pokey9000's rcmode (or the command line if possible) to change your bootmode to recovery and try it again. Be sure to wipe System and Factory Reset.
If you can't open a shell, you need a factory cable.
Click to expand...
Click to collapse
dont know what pokey 9000s rcmode but i tried kfu to change the bootmode to recovery but it just reboots and hangs right after the logo
can u explain pokey to me please
EDIT i d/l pokeys fbmode and replaced it in kfu and tried to change the boot mode to fastboot but still hanging am i doing anything wrong ?
any other suggestions
maxtcee said:
dont know what pokey 9000s rcmode but i tried kfu to change the bootmode to recovery but it just reboots and hangs right after the logo
can u explain pokey to me please
Click to expand...
Click to collapse
Okay let's take a step back for a second.
Open the KFU folder and "Shift" + "Right-click" on the folder containing adb.exe and fastboot.exe, and select "Open command window here".
In the window that pops up, enter: (with the device turned on)
Code:
adb shell idme ?
And copy the output here
soupmagnet said:
Okay let's take a step back for a second.
Open the KFU folder and "Shift" + "Right-click" on the folder containing adb.exe and fastboot.exe, and select "Open command window here".
In the window that pops up, enter: (with the device turned on)
Code:
adb shell idme ?
And copy the output here
Click to expand...
Click to collapse
i think my problem might be its not being recognized i keep getting waiting for device and in device manager i dont see kindle i see android adb interface
maxtcee said:
i think my problem might be its not being recognized i keep getting waiting for device and in device manager i dont see kindle i see android adb interface
Click to expand...
Click to collapse
im not seeing that option to open cmd prompt here
im using kfu 9.6 dont know if that makes a difference
maxtcee said:
im not seeing that option to open cmd prompt here
Click to expand...
Click to collapse
Shift + right-click...at the same time
soupmagnet said:
Shift + right-click...at the same time
Click to expand...
Click to collapse
im trying that but its not showing my that option
i see open and run as administrator
if i click on any of them comand prompt opens real quick and closes
maxtcee said:
im trying that but its not showing my that option
i see open and run as administrator
if i click on any of them comand prompt opens real quick and closes
Click to expand...
Click to collapse
I don't know anything about Windows, so I'm just guessing here. You're using Windows 7, correct? Do you have administrator privileges?
No matter, that's just the easy way, try...
Code:
cd /actual_path/to/kfu_folder/containing/adb
...then enter your commands.
---------- Post added at 04:59 PM ---------- Previous post was at 04:53 PM ----------
Let me reiterate, just in case it isn't clear. You don't actually type "/actual_path/to/kfu_folder/containing/adb"
maxtcee said:
i think my problem might be its not being recognized i keep getting waiting for device and in device manager i dont see kindle i see android adb interface
Click to expand...
Click to collapse
ok it says no C:\android-sdk-windows\platform-tools>adb shell idme
- exec '/system/bin/sh' failed: No such file or directory (2) -
soupmagnet said:
I don't know anything about Windows, so I'm just guessing here. You're using Windows 7, correct? Do you have administrator privileges?
No matter, that's just the easy way, try...
Code:
cd /actual_path/to/kfu_folder/containing/adb
...then enter your commands.
---------- Post added at 04:59 PM ---------- Previous post was at 04:53 PM ----------
Let me reiterate, just in case it isn't clear. You don't actually type "/actual_path/to/kfu_folder/containing/adb"
Click to expand...
Click to collapse
i know but its telling me
its not recognized
maxtcee said:
ok it says no C:\android-sdk-windows\platform-tools>adb shell idme
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
That's a bad thing. Your shell is missing or corrupt. You need the shell to change your bootmode to recovery to fix your problem. Without a shell, you need fastboot to be able to change bootmodes. But you need a shell to change the bootmode to fastboot. Darn.
The only way you get into fastboot now is with a factory cable.
http://forum.xda-developers.com/showpost.php?p=20380015
soupmagnet said:
That's a bad thing. Your shell is missing or corrupt. You need the shell to change your bootmode to recovery to fix your problem. Without a shell, you need fastboot to be able to change bootmodes. But you need a shell to change the bootmode to fastboot. Darn.
The only way you get into fastboot now is with a factory cable.
http://forum.xda-developers.com/showpost.php?p=20380015
Click to expand...
Click to collapse
thanks dude time to get drunk and worry about this in the am
Nevermind
Thepooch said:
Nevermind
Click to expand...
Click to collapse
Yeah, that page #2 is a tricky one, eh?
Yeah my bad didnt realize you were that deep yet lol
Hello, this is my first post on this forum, though I have lurked on XDA since as far back as my droid eris.
I have looked around the kindle fire forum for the answers I seek, but I have not seen a thread that helps. If I am asking a redundant question, please kindly show me the relevant thread(s) and I will read them.
I was at a small computer store my friend owns in our tiny little town (white hat computer solutions minersville, pa), when a mutual friend and former classmate of ours brought us a Kindle Fire D01400 with a cracked screen he bought off ebay. the previous owner claimed it worked despite the cracked screen, From a hardware standpoint that is quite correct, as you can see everything yet, and the touchscreen responds.
However, they neglected to mention they were selling one that already was modified, it is running TWRP 2.4.4.0 and has an improperly flashed ROM on it ( the stock keyboard crashes, home screen soft key does nothing, gmail works, but google play store does not). sideloading a keyboard app on fixed the keyboard, but the gapps with the exception of gmail don't function. I figured doing a wipe and flash of a new rom and gapps would be a good starting point to attempt to fix this problem.
However when I go into TWRP recovery and try to wipe the system, dalvik, or cache, the operation fails.
I have tried taking the TWRP manager app and sideloading it and using that to update to the latest TWRP. but the version number remains at 2.7.0.1
So my question is, with the above details kept in mind: How exactly do I go about fixing this tablet and making it a functional piece of android hardware for my friend/customer?
Try my flash able twrp.zips thread http://forum.xda-developers.com/showthread.php?t=2811253
Kindle Fire Flashable Recoveries TWRP/COTR/CWM[2014]
Sent from my XT862 using Tapatalk
sd_shadow said:
Try my flash able twrp.zips thread http://forum.xda-developers.com/showthread.php?t=2811253
Kindle Fire Flashable Recoveries TWRP/COTR/CWM[2014]
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
Downloading and trying it now. Thanks, I usually do my best to find relevant threads before posting, I am not sure how I missed that one.
Will post back with results as soon as I am done
EDIT:
Flashed it to twrp 2.6.1.0 otter I still can't use the wipe option. tried factory reset figuring i could just push the rom and gapps down using adb again, but factory reset also failed. is there a permission I can reset using adb?
vstrenko said:
I am not sure how I missed that one.
Click to expand...
Click to collapse
It's not stickied and 'flashable recoveries' can be misleading, but that is what they are called by many.
---------- Post added at 02:59 PM ---------- Previous post was at 02:05 PM ----------
vstrenko said:
Downloading and trying it now. Thanks, I usually do my best to find relevant threads before posting, I am not sure how I missed that one.
Will post back with results as soon as I am done
EDIT:
Flashed it to twrp 2.6.1.0 otter I still can't use the wipe option. tried factory reset figuring i could just push the rom and gapps down using adb again, but factory reset also failed. is there a permission I can reset using adb?
Click to expand...
Click to collapse
If you edit your post i don't get notified.
sorry I didn't realize, I lurk more than I post
vstrenko said:
sorry I didn't realize, I lurk more than I post
Click to expand...
Click to collapse
what is the rom version currently installed
full name listed in setting>about device(maybe about phone or tablet)>system version
JellyBeer-v4.33-23072013-190721
vstrenko said:
JellyBeer-v4.33-23072013-190721
Click to expand...
Click to collapse
have you used adb.exe or fastboot.exe before?
---------- Post added at 03:26 PM ---------- Previous post was at 03:25 PM ----------
windows 7 or 8?
I have used adb before with my acer iconia a500 and my droid3
windows 7 64bit is my OS
vstrenko said:
I have used adb before with my acer iconia a500 and my droid3
windows 7 64bit is my OS
Click to expand...
Click to collapse
use Install.Drivers.bat from Kindle Fire Utility if you have not yet.
reboot pc, check device manager with kindle connected to PC
should be listed as an Android Phone>adb interface
if OK then
boot Kindle to TWRP
in command prompt on PC
Code:
adb devices
should get something like
Code:
123456789 recovery
if you get waiting for device for more than a few secs or or some kind of bad command error post it.
---------- Post added at 04:15 PM ---------- Previous post was at 04:03 PM ----------
if response is good
Code:
adb shell "cat /proc/cmdline"
sd_shadow said:
use Install.Drivers.bat from Kindle Fire Utility if you have not yet.
reboot pc, check device manager with kindle connected to PC
should be listed as an Android Phone>adb interface
if OK then
boot Kindle to TWRP
in command prompt on PC
Code:
adb devices
should get something like
Code:
123456789 recovery
if you get waiting for device for more than a few secs or or some kind of bad command error post it.
---------- Post added at 04:15 PM ---------- Previous post was at 04:03 PM ----------
if response is good
Code:
adb shell "cat /proc/cmdline"
Click to expand...
Click to collapse
When it is booted into android, it shows in adb as
Code:
list of devices attached
0123456789ABCDEF device
When I boot into TWRP and execute adb devices i get
Code:
list of devices attached
with no further error messages
In TWRP on the second row at the top, along with the battery level (100%) and time 5:26pm, it says SIMULATING ACTIONS in all caps. is it supposed to say that or should it say something else
vstrenko said:
When it is booted into android, it shows in adb as
Code:
list of devices attached
0123456789ABCDEF device
When I boot into TWRP and execute adb devices i get
Code:
list of devices attached
with no further error messages
In TWRP on the second row at the top, along with the battery level (100%) and time 5:26pm, it says SIMULATING ACTIONS in all caps. is it supposed to say that or should it say something else
Click to expand...
Click to collapse
ok
try
with Kindle off, but connected to PC
Code:
fastboot devices
then boot Kindle
sd_shadow said:
ok
try
with Kindle off, but connected to PC
Code:
fastboot devices
then boot Kindle
Click to expand...
Click to collapse
fastboot reports nothing at all when i try that, when i type that in it pauses for a fraction of a second then i am left with a prompt on a new line to enter a command
Code:
C:\Windows\system32\> fastboot devices
C:\Windows\system32\>
vstrenko said:
fastboot reports nothing at all when i try that, when i type that in it pauses for a fraction of a second then i am left with a prompt on a new line to enter a command
Code:
C:\Windows\system32\> fastboot devices
C:\Windows\system32\>
Click to expand...
Click to collapse
download adb-fastboot.zip
Create a folder in C drive named adb (c:adb)
Unzip adb-fastboot.zip
Copy adb/fastboot files (AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe) to folder
Connect kindle to pc, power off kindle
Open Command Prompt
Enter Commands
Code:
cd\adb
Code:
fastboot devices
power on kindle
sd_shadow said:
download adb-fastboot.zip
Create a folder in C drive named adb (c:adb)
Unzip adb-fastboot.zip
Copy adb/fastboot files (AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe) to folder
Connect kindle to pc, power off kindle
Open Command Prompt
Enter Commands
Code:
cd\adb
Code:
fastboot devices
power on kindle
Click to expand...
Click to collapse
It is on when I use fastboot devices from a command prompt.
that is what I get as a result
vstrenko said:
It is on when I use fastboot devices from a command prompt.
that is what I get as a result
Click to expand...
Click to collapse
you may not have enough posts to link images, if that was your intent
try sending a pm or email
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Kindle should be off when entering fastboot commands, because kindle is in fastboot mode only a short time when powering on
sd_shadow said:
you may not have enough posts to link images, if that was your intent
try sending a pm or email
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Kindle should be off when entering fastboot commands, because kindle is in fastboot mode only a short time when powering on
Click to expand...
Click to collapse
Previous owner of the device had the TWRP recovery set to use simulation mode. I was unaware that was even an option since i was not familar with TWRP( my previous android flashing experiences used clockwork) after unchecking those boxes in the advanced settings, I was successfully able to flash a rom and gapps, and everything was perfect after that.
sorry for wasting so much time on this, I really missed something simple on this one.
vstrenko said:
Previous owner of the device had the TWRP recovery set to use simulation mode. I was unaware that was even an option since i was not familar with TWRP( my previous android flashing experiences used clockwork) after unchecking those boxes in the advanced settings, I was successfully able to flash a rom and gapps, and everything was perfect after that.
sorry for wasting so much time on this, I really missed something simple on this one.
Click to expand...
Click to collapse
no problem, I've never used the simulation options before...
I downloaded SDK and set it up, and now I'm using the CMD with the adb commands as far as I can. Now, the problem is the following. When I type "adb devices" I get a list of around 20 items, all stating offline. I tried the restarting the server (http://forum.xda-developers.com/goog...lator-t2804157) and for a brief moment, like 2-3 sec, there is only one device, but it says offline as well.. after that, the list keeps on filling until it reaches around 20 items again. Another thing I saw and tried is using "adb -d reboot bootloader" and it gives the same "error: more than one device", this time without emulator. Another thing I tried is booting into fastboot from the phone itself and following the htcdev method, but when I try to get the token it freezes on "waiting for device" and nothing happens. So basically, I can't unlock the bootloader because I can't even see my phone in the adb devices. I have had HTC Sync isntalled along with the HTC drivers it provides. Also the Windows drivers are installed as well. As I'm typing the thread, I saw that windows has some updates that it wants to install, and I'm letting them install right now.. eventhough I doubt that this is the problem. I'm starting to feel annoyed and I'm looking for help.. any ideas are welcome....
EDIT1: I just restarted my PC with all the updates it installed. I decided to also restart my phone and re-insert the battery just in case. As a side note, when I do adb devices when my phone is unplugged, the list stays empty. After I plug my phone the process goes like I described.. like 20 devices show up, all under the same ID/Name and all with the Offline status.
P.S. - I don't have Bluestacks. I have Sandboxie and Daemon Tools but I doubt they cause the problem as I have tried without them as well.
Ok....
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
Install min adb and fastboot... After that, boot your device into bootloader..open min adb by right clicking and chose open file location..inside folder right click and hold shift and chose open cmd here..in cmd window, type fastboot devices. Let's check and see if PC sees the phone
---------- Post added at 07:10 PM ---------- Previous post was at 07:09 PM ----------
And also... What ROM u on? Sometimes cm 11 and kk ROMs won't let PC see them. There's a diff process for that
Before I go to bed...
Alright, I need some quick help before I lay to sleep.. I somehow managed to unlock the BL and flash CWM but what I don't know how to do now is flash the SU. Should I:
A) Place the .zip version of SuperSU(http://forum.xda-developers.com/showthread.php?t=1538053) in my SDcard and flash it via CWM or..
B) Download something (which, though? hAlp) from here http://androidsu.com/superuser/ and flash it via CWM..
Which one will be the most beneficial and give the root?
P.S. - I will try to explain, as far as I can and remember, what I did to get my device recognised so that the people who read can get help..
Your ROM should have supersu already installed
---------- Post added at 01:31 AM ---------- Previous post was at 01:29 AM ----------
If u flashed cwm or twrp, the option to flash supersu should automatically appear. If not, yes..flash via recovery.
---------- Post added at 01:32 AM ---------- Previous post was at 01:31 AM ----------
But you need to s off to gain root
I have a 1st gen kindle fire.. That I rooted. But when i tried to install GAPPS and TWRP, the CMD window wouldn't let me. The error: "ADB server didn't ACK... Cannot connect to daemon" would pop up. So nothing else would load.
I then tried and tried various methods of fixes ( three days now), but none would work. Same constant error message in CMD window.
To make matters worse now, In one of my attempts to fix the problem, I've managed to brick the kindle. It's stuck on load page. Just says kindle fire on the screen.
ANY ANY ANY help .. would be greatly appreciated
pistol865 said:
I have a 1st gen kindle fire.. That I rooted. But when i tried to install GAPPS and TWRP, the CMD window wouldn't let me. The error: "ADB server didn't ACK... Cannot connect to daemon" would pop up. So nothing else would load.
I then tried and tried various methods of fixes ( three days now), but none would work. Same constant error message in CMD window.
To make matters worse now, In one of my attempts to fix the problem, I've managed to brick the kindle. It's stuck on load page. Just says kindle fire on the screen.
ANY ANY ANY help .. would be greatly appreciated
Click to expand...
Click to collapse
[6.3.4][6.3.3] Flashing FFF and TWRP without Fastboot Cable with Video
http://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
Sent from my XT1028 using Tapatalk
That was exactly one of the post I was working off of. So when I got to step 4: Push Fastboot Mode File to Kindle.. in the command window, I would get the error message, " ADB server didn't ACK... Cannot connect to daemon". I tried for three days now, various fixes.. nothing seemed to work. And NOW, during one of my fixes, it bricked the Fire.
pistol865 said:
That was exactly one of the post I was working off of. So when I got to step 4: Push Fastboot Mode File to Kindle.. in the command window, I would get the error message, " ADB server didn't ACK... Cannot connect to daemon". I tried for three days now, various fixes.. nothing seemed to work. And NOW, during one of my fixes, it bricked the Fire.
Click to expand...
Click to collapse
Stuck at Boot logo?
With animation or no change?
Sent from my XT1028 using Tapatalk
---------- Post added at 03:31 PM ---------- Previous post was at 03:24 PM ----------
Does boot logo, fade in and out slightly?
Sent from my XT1028 using Tapatalk
No fading in and out.
pistol865 said:
No fading in and out.
Click to expand...
Click to collapse
It's in fastboot mode then, send the fastboot commands
Sent from my XT1028 using Tapatalk
"It's in fastboot mode then, send the fastboot commands "
Don't really know what that means?
Fastboot mode?
Send fastboot commands?
Send where?
As I said.. kind of a newbie.. I'm not familiar with all the jargon/terms.
If you have a solution.. could you spell it out like I'm a five year old.. step by step? Otherwise.. I am just going to keep being Lost.
Thank you again
pistol865 said:
"It's in fastboot mode then, send the fastboot commands "
Don't really know what that means?
Fastboot mode?
Send fastboot commands?
Send where?
As I said.. kind of a newbie.. I'm not familiar with all the jargon/terms.
If you have a solution.. could you spell it out like I'm a five year old.. step by step? Otherwise.. I am just going to keep being Lost.
Thank you again
Click to expand...
Click to collapse
There are 2 different types of commands sent from pc to an android device, adb and fastboot.
Adb is used when device is in recovery or system/Rom is running.
Fastboot is used when device is in fastboot mode or bootloader mode.
Sent from my XT1028 using Tapatalk
---------- Post added at 04:41 PM ---------- Previous post was at 04:39 PM ----------
See step 6
Sent from my XT1028 using Tapatalk
sd_shadow said:
There are 2 different types of commands sent from pc to an android device, adb and fastboot.
Adb is used when device is in recovery or system/Rom is running.
Fastboot is used when device is in fastboot mode or bootloader mode.
Sent from my XT1028 using Tapatalk
---------- Post added at 04:41 PM ---------- Previous post was at 04:39 PM ----------
See step 6
Sent from my XT1028 using Tapatalk
Click to expand...
Click to collapse
I tried that.. Got the response: Fastboot is not recognized as an internal or external command,
operable program or batch file.
Also whenever I try and run a command from CMD.. I also get "ADB server didn't ACK.. cannot connect to daemon".
pistol865 said:
I tried that.. Got the response: Fastboot is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
adb.exe and other adb files are not in the same folder that the command prompt is running from.
You need to change directory with cd\
sd_shadow said:
adb.exe and other adb files are not in the same folder that the command prompt is running from.
You need to change directory with cd\
Click to expand...
Click to collapse
Step 3 says to put them all in the same folder on my C drive.
"Step 3: Place Files
Create a folder in c drive named adb,
unzip/extract files,
copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe, fbmode, fff-u-boot_v1.5.bin, and openrecovery-twrp-2.2.2.1-blaze.img to adb folder."
I am sooooooo confused right now!!!
I was following step by step. I got the kindle to Root... but then it all went down hill from there. And now it's bricked. ANd I can't figure out how to get out of it.
As I said.. i've been trying for three days now.. All different methods.
I keep running into problems with the CMD prompts..
That is until I somehow bricked it. Now I can't seem to do ANYTHING on it.
pistol865 said:
Step 3 says to put them all in the same folder on my C drive.
"Step 3: Place Files
Create a folder in c drive named adb,
unzip/extract files,
copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe, fbmode, fff-u-boot_v1.5.bin, and openrecovery-twrp-2.2.2.1-blaze.img to adb folder."
I am sooooooo confused right now!!!
I was following step by step. I got the kindle to Root... but then it all went down hill from there. And now it's bricked. ANd I can't figure out how to get out of it.
As I said.. i've been trying for three days now.. All different methods.
I keep running into problems with the CMD prompts..
That is until I somehow bricked it. Now I can't seem to do ANYTHING on it.
Click to expand...
Click to collapse
Create a folder in c drive named adb
One of the methods I was trying was this : http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/
However, once again, whenever it goes into the CMD phase, I get the phrase: "ADB server didn't ACK... Cannot connect to daemon"
So before I can unbrick it, I'm thinking I need to fix this other problem FIRST. The "ADB server didn't ACK... Cannot connect to daemon" problem.
pistol865 said:
One of the methods I was trying was this : http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/
Click to expand...
Click to collapse
I have not got that to work with System version 6.3.3 or 6.3.4.
So before I can unbrick it, I'm thinking I need to fix this other problem FIRST. The "ADB server didn't ACK... Cannot connect to daemon" problem.
Click to expand...
Click to collapse
It's not bricked it's in fastboot mode, where it needs to be to flash FFF and Twrp, the problem is your pc and the commands you are using.
Create a folder in c drive named adb
sd_shadow said:
I have not got that to work with System version 6.3.3 or 6.3.4.
It's not bricked it's in fastboot mode, where it needs to be to flash FFF and Twrp, the problem is your pc and the commands you are using.
Create a folder in c drive named adb
Click to expand...
Click to collapse
OK.. done..
I've attached an image showing what files are in the folder.
Now I opened a cmd window in C and Started step 4. But I got an error message: * daemon not running. starting it now on port 5037 * ADB server didn't ACK * failed to start daemon * error: cannot connect to daemon.
pistol865 said:
OK.. done..
I've attached an image showing what files are in the folder.
Now I opened a cmd window in C and Started step 4. But I got an error message: * daemon not running. starting it now on port 5037 * ADB server didn't ACK * failed to start daemon * error: cannot connect to daemon.
Click to expand...
Click to collapse
Kindle is in Fastboot mode
adb commands will not work
Use Fastboot commands
see Step 6
sd_shadow said:
Kindle is in Fastboot mode
adb commands will not work
Use Fastboot commands
see Step 6
Click to expand...
Click to collapse
Thank you so much for your help so far..
OK.. so I went ahead and tried step 6. Although the response didn't come back as it should have. I then went to the troubleshooting page and input:
If you got to step
Code:
fastboot devices
and do not get a proper code return, and you have checked drivers in Device Manager, or drivers don't seem to install correctly
you can try
Code:
fastboot -i 0x1949 oem idme bootmode 4000
then
Code:
fastboot -i 0x1949 reboot"
But now when i try to move ahead, the cmd window says it's waiting for device.
The Kindle at first looked as if it were going to reboot, but after a couple of times where the Kindle Fire logo went on and off ( at first disjointed then normal) . then it just stayed on that . Now underneath it says : Battery is too low ( 29%) . Please wait while your Kindle charges.
So I guess I just wait for it to charge? I'm not sure.
What do you suggest my next steps to be?
Again.. Thank you so much for taking the time to help me!
pistol865 said:
Thank you so much for your help so far..
OK.. so I went ahead and tried step 6. Although the response didn't come back as it should have. I then went to the troubleshooting page and input:
If you got to step
Code:
fastboot devices
and do not get a proper code return, and you have checked drivers in Device Manager, or drivers don't seem to install correctly
you can try
Code:
fastboot -i 0x1949 oem idme bootmode 4000
then
Code:
fastboot -i 0x1949 reboot"
But now when i try to move ahead, the cmd window says it's waiting for device.
The Kindle at first looked as if it were going to reboot, but after a couple of times where the Kindle Fire logo went on and off ( at first disjointed then normal) . then it just stayed on that . Now underneath it says : Battery is too low ( 29%) . Please wait while your Kindle charges.
So I guess I just wait for it to charge? I'm not sure.
What do you suggest my next steps to be?
Again.. Thank you so much for taking the time to help me!
Click to expand...
Click to collapse
UPDATE:
Well after a while , the Kindle Fire restored itself to factory.. Had me input all my info again on the Kindle.
So I guess one problem is fixed... It's not Bricked.
Is it still rooted as it was before the problem. And if it is, can I then install FFF and TWRP?
And Finally.. THANK YOU so much for helping me UNBRICK it in the first place!!
pistol865 said:
UPDATE:
Well after a while , the Kindle Fire restored itself to factory.. Had me input all my info again on the Kindle.
So I guess one problem is fixed... It's not Bricked.
Is it still rooted as it was before the problem. And if it is, can I then install FFF and TWRP?
And Finally.. THANK YOU so much for helping me UNBRICK it in the first place!!
Click to expand...
Click to collapse
Did you use install.drivers.bat from Kindle Fire Utility? If not do so now.
Then watch my video, follow my written steps.