Related
Sorry if this is a repost. But hopefully someone can help me out. I'm fully rooted, full nandroid unlock.full 100 yeards. Now this morning I was going to do the process for "Permanently replacing your recovery with ClockworkMod Recovery Image"
But for some strange reason, ADB doesn't see my Evo. I tried running "Command prompt" as administrator also and it wasa no go. I typed "adb devices" and my device wasn't listed like it was yesterday before I did a full nandroid Unlock.
Do anyone have any tips on how I can resolve this issue?
If this helps, I running the Bugless Beast Rom.
Thanks
You might have forgotten a step or two.
Open cmd
Type cd c:\android-sdk-windows\tools\ or wherever your sdk tools folder is.
Then it should work.
thanks. I'll give that a try and reply back
Strange thing....before I rooted/flashed a rom I created a Nandroid backup (I think it was stock. It doesn't have Superuser Permission in my list of Apps). Well I reverted back to that nandroid backup and now ADB sees my Evo.
I will flash back to my previous rom and trywhat you posted. Hopefully tat'll work
phatalboom said:
You might have forgotten a step or two.
Open cmd
Type cd c:\android-sdk-windows\tools\ or wherever your sdk tools folder is.
Then it should work.
Click to expand...
Click to collapse
Yeah, I tried what you suggested and itstill didn't see my Evo. I guess my only option is to revert back, then do the process.
Sometimes you need to restart the adb server. Try the following:
Code:
adb kill-server
adb shell
If you get a '#' then you're in.
I'm having same issues and it's not working. My device is not being seen. Do you I have to have the Evo in charging mode or Disk Mode?
chuckhriczko said:
Sometimes you need to restart the adb server. Try the following:
Code:
adb kill-server
adb shell
If you get a '#' then you're in.
Click to expand...
Click to collapse
or, you could just try
adb kill-server
adb start-server
lol
then check with
adb devices
seriously though, you may have put on a bad image. did you check the md5 hash? if not, do. there are threads around here on how to do that, if you are using windows. i don't have the link, because linux just has a command for it.
Try doing:
killall adb
sudo -s
adb devices
You must run adb as root on ur pc
timothydonohue said:
or, you could just try
adb kill-server
adb start-server
lol
then check with
adb devices
seriously though, you may have put on a bad image. did you check the md5 hash? if not, do. there are threads around here on how to do that, if you are using windows. i don't have the link, because linux just has a command for it.
Click to expand...
Click to collapse
Thanks for trying to help me out. But it still didn't work.
toastcfh said:
Try doing:
killall adb
sudo -s
adb devices
You must run adb as root on ur pc
Click to expand...
Click to collapse
What do you mean that I must run adb as root on my pc, i don't know what that mean. Do you mean run it by using the "Command prompt" program?
Also this only happens to me on the Bugless Beast Roms. When I revert back to my 1st nandroid backup that I was using before I flashed any rom, everything worked fine.
Is USB debugging enabled?
CentroniX said:
Is USB debugging enabled?
Click to expand...
Click to collapse
Thanks ...that fixed it! I enabled it typed "adb devices" and it showed up. thanks again!
No problem, glad you got it working! When I first started out I ran in to that trap over-and-over. Now I just make it a rule of thumb to turn it on after flashing and leave it on.
Have fun!
I would have started another thread, but this is basically a similar problem to the one I had at first with adb.
Ok...I was trying to install a rosie.apk that was in a zip format. Long story short, the OP informed me that he made a mistake and provided me the wrong information as to reinstalling the rosie.apk. He was giving me steps to "push it" via adb, instead of flashing it.
No problem to Poster and thanks for help if you reading this . But anyways after all that, When I open up "Cmd" and type anything with adb in front of it...adb devices, adb shell..., i get the message that adb is not recognized as a internal or external command. Before this incident happened i was able to just type "adb devices" and my Evo would show.
Do anyone know how to fix this?
By the way I also tried typing all the commands in the previous posts...and I get the same error message.
**Update** I got it working I had to redo the path. All is good now.
Thanks much!
You need to be in the tools directory of the sdk so cmd can find the adb command.
Alright so last night i ran the DCupdater and saw the damagecontrol v3.1.2 update. So i downloaded it and tried running that. Thats when my evo started freaking out and the sd card kept getting disconnected. After all that nonsense it got installed. But then as my phone restarted it was in for the loop of watching the HTC EVO 4G logo. Thats when i tried going to one of my backups and that seemed to work. So then after that i when back to damagecontrol v3. But that messed everything up even more because now im stuck on v3 without sd card. When i try going into the bootloader it wont let me. When i hook up the phone to my pc via usb it wont let me see the sd card contents. I tried doing the:
fastboot oem enableqxdm 0
fastboot reboot
but that had no effect and the cmd wouldnt even recognize the command
what do i do?
xarttyx said:
Alright so last night i ran the DCupdater and saw the damagecontrol v3.1.2 update. So i downloaded it and tried running that. Thats when my evo started freaking out and the sd card kept getting disconnected. After all that nonsense it got installed. But then as my phone restarted it was in for the loop of watching the HTC EVO 4G logo. Thats when i tried going to one of my backups and that seemed to work. So then after that i when back to damagecontrol v3. But that messed everything up even more because now im stuck on v3 without sd card. When i try going into the bootloader it wont let me. When i hook up the phone to my pc via usb it wont let me see the sd card contents. I tried doing the:
fastboot oem enableqxdm 0
fastboot reboot
but that had no effect and the cmd wouldnt even recognize the command
what do i do?
Click to expand...
Click to collapse
before you enter those commands you have to hold power and volume down and go into fastboot on the phone - after that connect it to the computer
click start - run - CMD
After that
type cd "location of your android sdk tools folder" - OR cd "drag the folder of your tools folder into the prompt"
THAN
type the commands -
fastboot oem enableqxdm 0
fastboot reboot
mongoose8p said:
before you enter those commands you have to hold power and volume down and go into fastboot on the phone - after that connect it to the computer
click start - run - CMD
After that
type cd "location of your android sdk tools folder" - OR cd "drag the folder of your tools folder into the prompt"
THAN
type the commands -
fastboot oem enableqxdm 0
fastboot reboot
Click to expand...
Click to collapse
where do i find that folder... im sorry i dont really know much of this
i'm assuming you are using windows. it's the location of your \android-sdk-windows\tools\ folder from when you installed the android sdk in order to root in the first place. it is also the location of adb. if need be, do a search for adb.exe and it should point you directly to the location of everything you need.
It keeps saying "the system cannot find the path specified". I dont even know what to do. This sucks.
it might be under a different path, where did u install ur android sdk?
i don't really remember. i found it though searching for adb and i guess i have 2 folders of it... zipped and unzipped... but i tried putting both path names in there and that went nowhere
When you search for adb or your android sdk tools folder, go into that folder and hit Shift+right click and "open command window here" then use your commands.
awesomeindeed said:
When you search for adb or your android sdk tools folder, go into that folder and hit Shift+right click and "open command window here" then use your commands.
Click to expand...
Click to collapse
that option does not pop up.. im running xp if that helps
im still having trouble figuring out what to do.
xarttyx said:
that option does not pop up.. im running xp if that helps
Click to expand...
Click to collapse
copy the path of the folder with adb.exe in it - start - run cmd - command "cd path of adb folder" - then follow the instructions above
Well I want to command my htc desire from cmd but I am not beeing successful.
I type/get (phone in Fastboot mode):
c:\Program Files\Android\android-sdk\platform-tools>adb devices
List of devices attached
c:\Program Files\Android\android-sdk\platform-tools>adb shell
error: device not found
This what I have in Windows "Device Manager" ADB Interface (Installed correctly did not have any "Yellow exlamation icon"):
"Android Bootloader Interface"
any ideas?
Yes, ignore that as mine too said the same. Here's my instructions that I recorded so that I can remember (old age) :-
Put phone into fastboot mode (back button + power)
In CMD, go to dir C:\Android\android-sdk\Tools
Type: path C:\Android\android-sdk\Platform-tools)
Click to expand...
Click to collapse
Note that mine is not located in the 'Program Files' directory so you will need to change that to suit. From there you should be able to run fastboot commands. The 'path' command I had to set due to ADB being in a different directory to Fastboot so running any fastboot commands failed as it was looking to use ADB which doesn't reside in the same directory.
If you are using fastboot, you want to type
Code:
fastboot devices
rather than adb devices. ADB is for use when the phone is normally booted rather than in bootloader/fastboot.
parva, i tried that but nothing changed
C:\sdk\tools>fastboot reboot-bootloader
< waiting for device >
C:\sdk\tools>fastboot devices
and nothing... happens ... My device is there! (Android Bootloader Interface)
more ideas?
Try a different USB cable?
Or another usb port. And make sure you installed all necessary drivers correctly.
Sent from my HTC Desire using XDA App
Why should i try another cable if with this cable I transfer files, windows check all drivers etc... already tried in another pc -.-
what should i see on device manager for the htcdesire device when it is on fastboot?
maybe try using safe mode (if using windows) it could be a firewall or a program blocking the connection
but tell me what should I see on device manager when my htc is on fastboot
portelaux said:
parva, i tried that but nothing changed
C:\sdk\tools>fastboot reboot-bootloader
< waiting for device >
C:\sdk\tools>fastboot devices
and nothing... happens ... My device is there! (Android Bootloader Interface)
more ideas?
Click to expand...
Click to collapse
Are you sure that everything is in that directory? Only by default it installs to 'C:\Program Files\Android', I simply removed the 'Program Files' directory but you haven't even got an 'Android' directory now. Reinstall it and start again maybe, using defaults. You're directory structure may or may not be the issue here but we could be here until this time next year fixing something that is unrelated.
Reinstall the SDK and only remove the 'Progam Files' part of the directory then follow my instructions again.
portelaux said:
but tell me what should I see on device manager when my htc is on fastboot
Click to expand...
Click to collapse
If all is well, when you type "fastboot devices" in your terminal window , you should see something of this format, meaning your connection is good.
"fastboot H3567FYH5577"
Copy the content of Platform-tools to tools. And try ADB that way - if the drivers are correctly installed it should work.
And you must have the USB Debugging option enabled (settings> applications> developement).
Well thanks you all anyway...
My sdk device control started working ^^ ... i dont know why but if already find devices etc
thanks you all
portelaux said:
Well thanks you all anyway...
My sdk device control started working ^^ ... i dont know why but if already find devices etc
thanks you all
Click to expand...
Click to collapse
Please add "[SOLVED]" to topic's title, to help other users.
Hi guys! I'm new to the forum but not new to the IT world and not new to Linux or Android devices.
I'm stuck at the Kindle Fire screen after a failed attempt to root the device. Here's what I did. I'm hoping somebody can please help me. I did lots of Google searches to try to solve my issue and I can't seem to find the right solution.
So here's the background. I tried to root my KF by using this process http://www.pcworld.com/article/244303/how_to_root_your_kindle_fire.html on an Windows 7 VM. Then I found that SuperOneClick didn't work for KF6.3. So then I tried to KF Utility v.0.9.5 http://forum.xda-developers.com/showthread.php?t=1399889
I selected the option to root the KF. After it went through the process and I got the Kindle Fire screen (which is sounds like the KF is in the fastboot process) I couldn't get anything to work at that point. I couldn't get the VM to even see the KF nor Ubuntu (which is the main OS of that laptop). So then I figured I bricked the device. So I followed these instructions http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/ but that won't work ecause the KF isn't being recognized by the OS. SO at that point, I couldn't get anything to work. So I rebooted the laptop (which is running Ubuntu 12) and the KF booted back up and it fired back up.
If I power off the KF and turn it back on, it gets stuck at the KF bootup screen.
So at that point I decided to throw Windows 7 on a different laptop that I have and see if I can get it to work. So I installed java & Android ADK for my OS (Windows 7). I installed the USB driver and updated the packages. So I go through these instructions first http://forum.xda-developers.com/showthread.php?t=1568340 and I can't get the KF to be recognized as a device through adb. So I go back to the PC World instructions (linked above) and I follow steps through step 8. And I still can't get the KF to be displayed through adb. When I try to kill the adb server and then enter adb devices, I still can't get the KF to be recognized.
Oh and btw, Windows 7 does recognize the device as a "Kindle".
Any help would be greatly appreciated.
Sparty On!
Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works:
Sent from my Amazon Kindle Fire using Tapatalk 2
Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.
I'm having the same problem I think since windows doesn't recognize my kindle I can't install the drivers.
AndroidSparty said:
Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.
Click to expand...
Click to collapse
Us the same commands without -i 0x1949
fastboot oem idme bootmode 4000
fastboot reboot
Sent from my Amazon Kindle Fire using Tapatalk 2
ammubarak said:
Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works
Click to expand...
Click to collapse
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567
From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA
I received mine with 6.3 and KFU wouldn't recognize it even after using the driver installation. BUT I found way around it. You need to install the drivers manually, and then KFU will work. Download the drivers, then extract the .android folder (create it if you don't have one) to
C:\Documents and Settings\YOURUSERNAME\.android open up your device manager, click on the Kindle and follow the UI to select the .android folder. Restart and use KFU. Enjoy!
soupmagnet said:
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567
Click to expand...
Click to collapse
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
backspacepc said:
From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!
AndroidSparty said:
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!
Click to expand...
Click to collapse
Actually it will, status will still be off line, just select the boot mode option, and then on the next screen select normal bootmode
Sent from my MB860 using XDA
For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.
soupmagnet said:
For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.
Click to expand...
Click to collapse
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA
backspacepc said:
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Actually...I'm a she.
Since I have both available to me...it sounds like I should scrap the Windows (which is an understatement anyway) and use Linux/Ubuntu. That I can do!
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
AndroidSparty said:
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
You may also want to try to rerun your root script, oddly enough I've had that work before too.
Sent from my MB860 using XDA
AndroidSparty said:
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Did you notice the second post in the Linux tutorial?
kinfauns said:
Thanks for the guide on setting this up for linux. I just wanted to point out a small error in the instructions. The echo command above is incorrect and will not do what you intended. It should be corrected to
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
Click to expand...
Click to collapse
backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I just ran kfu and I I was able to get it to do a normal boot. YAY!
Then I ran the .bat file in the KFU and I selected the permanent root. During the activating fastboot, it said that "Oops something went wrong...." it couldn't find the kindle. Then it installed twrp.img is missing and it downloaded successfully. So then I got the Notice, and it's installing TWRP and it's waiting for the device. I turned the Kindle off & on a few times to get the KFU to recognize the Kindle, and no luck. At least I was able to boot into the KF while it's still still waiting for the device. BUT....at this point during the TWRP install process, it's waiting for the device and not recognizing it.
soupmagnet said:
Did you notice the second post in the Linux tutorial?
Click to expand...
Click to collapse
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.
AndroidSparty said:
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.
Click to expand...
Click to collapse
I can't imagine why using vi would make any difference but you could try gedit to see if it works.
As for TWRP, you could install it manually (Windows). Make sure you have a connection with adb/fastboot and use KFU to set your device to fastboot mode. Keep in mind when you do this that you may have to go through the whole process of fixing your drivers again (blame Windows/KFU).
When you're in fastboot mode, hold the power button until the device shuts down.
Shift + right click the KFU folder that contains fastboot (tools) and open as a command
In the prompt that comes up, enter:
Code:
fastboot -i 0x1949 flash recovery /path/to/twrp2.1.img
When your prompt says "waiting for device", turn the device back on.
Make sure it's twrp 2.1 Version 2.0 is installed in a different manner and will most likely cause problems if installed with the "flash recovery" command.
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.