Develop Bugs

Questions regarding various stuff.

Sorry, i know you must get this all the time guys, but i'm really struggling with rooting and such.
I'm on 1.72 and have no idea how to downgrade. I know you might say "read the guide" blah blah, but i don't understand it "Moron" i hear you saying. Anyway, Is there a complete noob guide for it anywhere? Like literally one that talks you through every step?
Also, my screen cracked, so i opened it up and replaced the screen myself, didn't have insurance or the £170 to have them fix it. Before the screen cracked it was doing this thing where it looked all psychedelic, Whites have blue coming off them, blacks have reds coming off them, that kind of thing. and its doing it again. This made me think it was a software issue, it happen to anybody else? I was thinking if i put a different rom on it, it'd stop, but i dunno. Anyway, thanks for any help anyone gives.

Does the screen replacement involve the flat ribbon cable between the screen part of the phone and the keyboard? I'm thinking it doesn't, but I'm certainly no expert. A damaged ribbon cable can cause colors to display improperly.

Nah, its attached to the screen so it was a new one.

The screen only comes with a small ribbon cable that connects to the pcb in the front half of the phone.
There is a larger ribbon cable that connects the two halves of the phone together, you can see it if you hold the phone halfway between open and closed. If this cable gets damaged, which happens easier than you may think then it can causes all sorts of things to mess up, including the colours on your display.
Unfortunately this cable is attached to the screen pcb so needs to be replaced as one unit.

So i'd need to replace my main pcb? Damn. Thanks for the help though! Could anyone help me with rooting?!
Sent from my HTC Vision using XDA App

at which point are you getting lost? sussed downgrading yet?

emdaftrave;14529179.Could anyone help me with rooting?! :D
.
Sent from my HTC Vision using XDA App[/QUOTE said:
Man, trust me.. It took only 30 minutes for me to root my dz
But, the preparation ( search and search) took 2 weeks
But it worths trying
The main keys are to instal ADB things (sdk android ) and create a gold card. Once you understand how to do that, you already half way.
The links are in the wiki
Cheers
Click to expand...
Click to collapse

Just have a search and there are numerous step by step guides, I was a total amateur and managed to do it, I think the hardest part to try learn would be using ABD (command prompt) and how to navigate to directories and push files but there are numerous guides on this forum so just pick your simplest and go for it!

elliott2705 said:
at which point are you getting lost? sussed downgrading yet?
Click to expand...
Click to collapse
Pretty much trying to install the sdk, i think im gonna reinstall it because its being a bit dodgy for me. But thanks for all the help guys!
Sent from my HTC Vision using XDA App

silverwind said:
Man, trust me.. It took only 30 minutes for me to root my dz
But, the preparation ( search and search) took 2 weeks
But it worths trying
The main keys are to instal ADB things (sdk android ) and create a gold card. Once you understand how to do that, you already half way.
The links are in the wiki
Cheers
Click to expand...
Click to collapse
can you use the SD card already in there as a gold card, or do you need a separate one?

Ok so i have an actual problem now, not just not understanding the guides xD
On the Cyanogenmod wiki guide of how to install ADB, a couple of the steps are:
On success, open the command prompt on the computer, and type in the following command to sure everything is setup properly:
Code:
adb devices
If it lists any devices, everything is fine and you are finished. If not, the drivers may not be installed correctly, please continue.
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Well i did just that, and it doesnt say unknown device anywhere, and yet when i type adb devices in command prompt, it says 'adb' is not recognized as an internal or external command, operable program or batch file. Anybody know what gives?

emdaftrave said:
Ok so i have an actual problem now, not just not understanding the guides xD
On the Cyanogenmod wiki guide of how to install ADB, a couple of the steps are:
On success, open the command prompt on the computer, and type in the following command to sure everything is setup properly:
Code:
adb devices
If it lists any devices, everything is fine and you are finished. If not, the drivers may not be installed correctly, please continue.
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Well i did just that, and it doesnt say unknown device anywhere, and yet when i type adb devices in command prompt, it says 'adb' is not recognized as an internal or external command, operable program or batch file. Anybody know what gives?
Click to expand...
Click to collapse
you either need to cd to the folder within your android sdk that adb is in (I think it's platform-tools), or add the android sdk path to your environment variables (google this, it's easy to do).
open up your command prompt and type:
cd C:\path-to-android-sdk\platform-tools
adb devices
if you don't add the path to your android sdk in the environment variables, you'll have to cd to the folder with adb every time you need to use it... not a big deal if you're not using adb a lot, but it gets annoying if you're opening up a command prompt to push/pull/shell regularly.

pmcqueen said:
you either need to cd to the folder within your android sdk that adb is in (I think it's platform-tools), or add the android sdk path to your environment variables (google this, it's easy to do).
open up your command prompt and type:
cd C:\path-to-android-sdk\platform-tools
adb devices
if you don't add the path to your android sdk in the environment variables, you'll have to cd to the folder with adb every time you need to use it... not a big deal if you're not using adb a lot, but it gets annoying if you're opening up a command prompt to push/pull/shell regularly.
Click to expand...
Click to collapse
ok, i've done it, thank you very much! now to just downgrade and root!

Ok so i'm using the XDA wiki guide on rooting, and i've got to the part where you move all the files onto the phone. Specifically, the files that aren't moving are:
$ adb push flash_image /data/local/tmp/
$ adb push su /sdcard/,
I'm getting a "Permission denied" error in command prompt. I also don't have an /sdcard directory on my phone, maybe thats why i'm getting an error?
EDIT: Never mind, i had the phone in Disk Drive mode when it wasn't supposed to be. Sorry for the double post.

[Q] Ubuntu 11.04 amd64, r800x, fastboot waiting for device

OK, I truly believe I have done my due diligence, but I have not been able to find anything solid that can help me get beyond the problem I'm having. The irony is that I first tried this on my WinXP box at work and could not get beyond the < waiting for device > problem, so I gave up and figured I would have no problem if I patiently waited to go home and try this in linux.
So here's everything I've done so far. As noted in the topic, I run the amd64 version of Ubuntu 11.04. I installed the Andoid SDK linux x86 version (there was no option for an amd64 version). I ran the tool/android client to download the platform-tools, so I got adb. With the phone running normally, I can connect it to my laptop and run "./adb devices" and I get back:
Code:
List of devices attached
43423541314354394D58 device
so that's working. When I run lsusb while the phone is running normally, I see
Code:
Bus 001 Device 020: ID 0fce:215b Sony Ericsson Mobile Communications AB
Then I power off the phone, disconnect it, hold down the search button, and reconnect it. The power LED turns blue. When I run lsusb in this mode, I get:
Code:
Bus 001 Device 022: ID 0fce:0dde Sony Ericsson Mobile Communications AB
As a result, I set the contents of my /etc/udev/rules.d/51-android.rules to:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="215b", MODE="0666", OWNER="procyon"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="0dde", MODE="0666", OWNER="procyon"
and just to make sure my file permissions are ok (since that seems to bite people in the behind a lot), my rule is
Code:
-rwxr-xr-x 1 root root 197 2011-08-11 01:24 /etc/udev/rules.d/51-android.rules
So, with my udev rules reloaded, I attempt a "sudo ./fastboot boot recoveryPLAY.img" and all I get is the unfortunate
Code:
< waiting for device >
I've done just everything I could thing of, have read several (literally dozens) of tutorials, forums posts, and all manner of Google searches, but nothing seems to help me. Some areas where I think I might be having a problem:
a) Obviously, I'm running the 32 bit version of the sdk instead of the 64 bit version. Could that be an issue here?
b) I've seen lots of posts that disagree on whether the rules file should start with a 50 or a 51. Does that matter?
c) Do I need anything else from the Android SDK other than the platform tools? I don't have that directory in my path, but I'm running everything from inside that directory, and I'm running it with sudo.
I think I've provided all the information that I can. Thanks in advance for any help or any light that anyone can shed.

ProcyonSJJ said:
OK, I truly believe I have done my due diligence, but I have not been able to find anything solid that can help me get beyond the problem I'm having. The irony is that I first tried this on my WinXP box at work and could not get beyond the < waiting for device > problem, so I gave up and figured I would have no problem if I patiently waited to go home and try this in linux.
So here's everything I've done so far. As noted in the topic, I run the amd64 version of Ubuntu 11.04. I installed the Andoid SDK linux x86 version (there was no option for an amd64 version). I ran the tool/android client to download the platform-tools, so I got adb. With the phone running normally, I can connect it to my laptop and run "./adb devices" and I get back:
Code:
List of devices attached
43423541314354394D58 device
so that's working. When I run lsusb while the phone is running normally, I see
Code:
Bus 001 Device 020: ID 0fce:215b Sony Ericsson Mobile Communications AB
Then I power off the phone, disconnect it, hold down the search button, and reconnect it. The power LED turns blue. When I run lsusb in this mode, I get:
Code:
Bus 001 Device 022: ID 0fce:0dde Sony Ericsson Mobile Communications AB
As a result, I set the contents of my /etc/udev/rules.d/51-android.rules to:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="215b", MODE="0666", OWNER="procyon"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="0dde", MODE="0666", OWNER="procyon"
and just to make sure my file permissions are ok (since that seems to bite people in the behind a lot), my rule is
Code:
-rwxr-xr-x 1 root root 197 2011-08-11 01:24 /etc/udev/rules.d/51-android.rules
So, with my udev rules reloaded, I attempt a "sudo ./fastboot boot recoveryPLAY.img" and all I get is the unfortunate
Code:
< waiting for device >
I've done just everything I could thing of, have read several (literally dozens) of tutorials, forums posts, and all manner of Google searches, but nothing seems to help me. Some areas where I think I might be having a problem:
a) Obviously, I'm running the 32 bit version of the sdk instead of the 64 bit version. Could that be an issue here?
b) I've seen lots of posts that disagree on whether the rules file should start with a 50 or a 51. Does that matter?
c) Do I need anything else from the Android SDK other than the platform tools? I don't have that directory in my path, but I'm running everything from inside that directory, and I'm running it with sudo.
I think I've provided all the information that I can. Thanks in advance for any help or any light that anyone can shed.
Click to expand...
Click to collapse
I rooted mine last night and I figured it out. Turn your phone completely off first. Unplug everything from the computer. Then hold the "search" button or the magnifying glass while you plug the cable into the phone. There should be a solid blue LED light color at the top of the phone. Then it should work!

There's no 64-bit version of the Android SDK. I think it may have to do with fastboot's binary.

Cubsfan3493 said:
I rooted mine last night and I figured it out. Turn your phone completely off first. Unplug everything from the computer. Then hold the "search" button or the magnifying glass while you plug the cable into the phone. There should be a solid blue LED light color at the top of the phone. Then it should work!
Click to expand...
Click to collapse
Did you not read:
Procyon said:
Then I power off the phone, disconnect it, hold down the search button, and reconnect it. The power LED turns blue.
Click to expand...
Click to collapse
@Logseman, where is the best place to obtain a good fastboot binary for linux besides the HTC distribution page?

Add -i 0x0fce to the actual fastboot command line too... I had the same problem as you

Thank you so much Blagus, that was exactly what I was missing. I was trying to follow the "Easy Way" method of rooting, as it seemed to be a method in which I would not need to bother ash or mills. Now that you've gotten me over this hurdle, I've come to realize that the "Easy Way" only works if you unlocked the bootloader first, so it appears that I must pm ash or mills anyway? Or is it recommended that I simply wait and be patient until they sort out whatever is needed to provide everyone with a single solution? Thanks again.

I don't get to see this in my R800i. I've put the fastboot binary (from HTC) in platform-tools and this folder in my path. Running "fastboot -i 0x0fce devices" simply returns me the fastboot manual.

[Q-Solved] Kindle Fire unbricking on a Mac-help request

UPDATE: I added "solved" to the title since I am now unbricked. That said, I do hope someone will pop in and tell me how to run the shell scripts on a mac...
Click to expand...
Click to collapse
Hi there. I have spent several days searching xda forums, popping into the kindlefire irc channel, and searching google however have not yet figured this out, could use some help.
I have read: the Kindle Fire Beginners Guide, the Kindle Fire Unbrick thread, The Kindle Fire Utility thread (yup the whole thing), and more.
According to the Kindle Fire Beginner's Guide, only 1% of all brick situations are actually a brick, so I'm going to persevere and go ahead and ask for the help, because also according to the guide, if your fire can't be seen as a device then actually it's a brick. To quote: " unless something else was done to the device after the change in bootmode preventing access to adb or fastboot commands. Then it’s actually a brick at that point."
I can't be sure if anything else was done after the change in bootmode so I'll just explain how I got here and hopefully someone can help out.
I have a mac mini running Os x 10.6.8, and the Kindle Fire which was running stock version 6.2.2.
I used the kindlewater root method to install firefirefire and cwm recovery. Was able to boot into recovery by pressing on the power button for it to go orange and then load the recovery options.
Before doing anything at all (and in consultation with St3p_2 of this forum, one of the kindlewater developers), I decided to perform a backup in preparation for flashing a ROM.
so, I booted, went into recovery, navigated to "install a .zip" and chose "backup" at which point I got a message/nag/reminder that this was a permanent change, and I selected "ok". It did it's thing for a while, went into reboot, and I then had the firefirefire logo blinking in a very very slow loop.
It was recommended to me to perform a factory reset by holding the power button for 2 solid minutes, which should then have returned me to stock. Actually, the first time i did it for minutes I went from having a very slow blinking firefirefire to having a rather fast blinking firefirefire. Following a suggestion i then tried it with the kindlefire unplugged. This resulted in a plain black screen until the fire was plugged in again: no boot, no indication of response to use of the power button. Once plugged in, it has gone back to the rather fast blinking firefirefire logo.
I read through the Kindle Fire Utility thread, found the v0.9.2 version prepared for mac and linux, and downloaded it. Although I am not new to terminal, I am not familiar with what command language is necessary to perform the actions required by this tool. If I open the install_drivers.sh with terminal, i get this:
Reverie:~ apple$ /kindlefire/Kindle_Fire_Utility_MacLinux_0.9-1.2/install_drivers.sh ; exit;
This file will install the correct adb_usb.ini file for proper Kindle Fire detection.
cp: drivers/adb_usb.ini: No such file or directory
Done!
logout
[Process completed]
​so I tried running it in the console. I will spare you the output of the console as it appeared to be merely a printout of the actual code of the file and was quite long.
Trying to run the file runme.sh in terminal before running the install_drivers.sh in the console, I got error messages stating there is no such command, or no such file, depending on my command language.
After running the install_drivers.sh in the console, when I try to run runme.sh in terminal, i get this:
/kindlefire/runme.sh ; exit;
Reverie:~ apple$ /kindlefire/runme.sh ; exit;
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using zergRush exploit
(2) install Busybox (1.18.4)
(3) install SU files (3.0.5)
[*] Before u begin:
(1) make sure adb is in your path
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue... --- STARTING ----
--- WAITING FOR DEVICE
​Which I affirmed because all the requirements had indeed been set that way on the device before the bricking happened. After "starting" and "waiting for device" nothing happens even waiting indefinitely (more than half an hour) and then it never finds the device.
When I go into terminal and type: "adb devices" I get:
Last login: Sun Mar 18 17:08:38 on ttys001
Reverie:~ apple$ adb devices
List of devices attached
Reverie:~ apple$
​This result is the same both before attempting to use the 0.9.2 mac utility and after.
I really am stuck at this point, as everything I find with instructions on how to "unbrick" does require that the machine recognize that your kindlefire is attached. Running any of the tools I find requires that basic bottom dollar, which I don't seem to have.
That said, the behavior of "nothing at all: blank screen" when unplugged, and the behavior of "blinking firefirefire logo" when plugged in would tend to indicate that at the very least the device knows it's plugged in and getting juice, and some process is happening when that's true.
Can someone help? Is my next step to purchase a factory cable, or do I have a software solution available to me that I just didn't find in this haystack of solutions?

nothing doing when unplugged seems like a dead battery
would try to charge it with the wall charger for some hours regardless if the orange light comes up - this can last a while
furthermore i don't know which version of kfu for mac you'r using but zergrush is'nt working any more since stock rom 0.6.1
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
for rooting use kindlewater:
http://forum.xda-developers.com/showthread.php?t=1443071
as far as i know the commands need to be entered with a ./ in front ie: ./install_drivers.sh

sisterdelirious said:
Can someone help? Is my next step to purchase a factory cable, or do I have a software solution available to me that I just didn't find in this haystack of solutions?
Click to expand...
Click to collapse
Thanks for reading my guide. I hope it helped you a bit.
Mac OS X is also my primary OS and I take my hat off to you for even trying things this way. I took the easy way out from the very beginning and just used Parallels Desktop to build Windows and Linux virtual machines. If things ultimately don't work out, you might want to try going that route as well. I believe Parallels offers a demo version if you want to see it in action. Regardless, I don't think that matters quite yet, because I tend to agree with b63 here. I think the biggest problem you have right now is a dead battery.
I've never had a dead battery, so I can't comment directly, but take a look at this thread, starting at post #226...
http://forum.xda-developers.com/showthread.php?t=1392693&page=23
There some back and forth for a couple of pages, but that user describes symptoms that sound very much like what you are seeing right now. I think you should try the wall charger first. Plug it in, force the Kindle Fire to turn off and just try to let it charge overnight or something. If you cannot get your KF charged with the stock wall charger, you might want to buy a factory cable. From what I gather, that user reported that his Kindle Fire booted into fastboot mode by using the factory cable even with a (nearly) dead battery. He was then able to flash the stock software, which is able to handle the dead battery situation better than some alternative ROM and have it go through the charge cycle.

Wow... so simple...
b63 said:
nothing doing when unplugged seems like a dead battery
would try to charge it with the wall charger for some hours regardless if the orange light comes up - this can last a while
Click to expand...
Click to collapse
This was the deal. When plugged in with the usb cord it didn't seem to be giving it power and being powerless could not be recognized by the computer. Plugged it into the wall charger and Voila! was able to start up just fine, still rooted via the kindlewater method, capable of being booted normally or booted into CWM recovery. Awesome!
I also did a quick double-check, and now that it's powered-up, running a terminal and typing "adb devices" actually returns a list with the kindle (serial number?) on it.
furthermore i don't know which version of kfu for mac you'r using but zergrush is'nt working any more since stock rom 0.6.1
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
Click to expand...
Click to collapse
I read through everything and the version of kfu that was modded for mac was 0.9.2 which I mentioned in my original post. Sounds like since I was on 6.2.2 that mac version is definitely not going to help me (both kfu out of date and stock version out of date on zergrush) if I were to want it for rooting purposes.
for rooting use kindlewater:
http://forum.xda-developers.com/showthread.php?t=1443071
Click to expand...
Click to collapse
that is the one i used. I was looking for a mac tool for post-root rescue methods...i had thought that the kfu mac version had valuable rescue/unbrick capabilities but at this point I don't remember.
as far as i know the commands need to be entered with a ./ in front ie: ./install_drivers.sh
Click to expand...
Click to collapse
[/QUOTE]
Thankfully, I don't need to try that. my kf got properly unbricked just by plugging it into the wall charger.

Great guide, it was the battery
kinfauns said:
Thanks for reading my guide. I hope it helped you a bit.
Mac OS X is also my primary OS and I take my hat off to you for even trying things this way. I took the easy way out from the very beginning and just used Parallels Desktop to build Windows and Linux virtual machines. If things ultimately don't work out, you might want to try going that route as well. I believe Parallels offers a demo version if you want to see it in action. Regardless, I don't think that matters quite yet, because I tend to agree with b63 here. I think the biggest problem you have right now is a dead battery.
Click to expand...
Click to collapse
Thank you for your guide. I thought it was extremely well written and very helpful. It definitely helped me relax a little stress-wise while looking for a solution.
That was it (dead battery). I did try meddling around a bit with virtualbox virtual machines: a windows 7 ultimate, and a linux box that I have that does not have internet access making doing anything realtime while reading suggestions just isnt easy/feasible right now. I found that the virtualbox vms did not have access to the usb devices (flash drives, external hard drives, ostensibly if it were visible to the computer the kindle) despite my installing some optional extension packs for that purpose. I didn't explore the vms further to linux or xp simply because of the time required to install and configure a vm. I also didn't rewire my home so net access went to the linux box for the same reason... ultimately both are possible but both more hassle than it seems to be worth before simply asking the question, can it be done on a mac?
I've never had a dead battery, so I can't comment directly, but take a look at this thread, starting at post #226...
http://forum.xda-developers.com/showthread.php?t=1392693&page=23
There some back and forth for a couple of pages, but that user describes symptoms that sound very much like what you are seeing right now. I think you should try the wall charger first. Plug it in, force the Kindle Fire to turn off and just try to let it charge overnight or something. If you cannot get your KF charged with the stock wall charger, you might want to buy a factory cable. From what I gather, that user reported that his Kindle Fire booted into fastboot mode by using the factory cable even with a (nearly) dead battery. He was then able to flash the stock software, which is able to handle the dead battery situation better than some alternative ROM and have it go through the charge cycle.
Click to expand...
Click to collapse
I'm just so glad this worked. Thank you for your help!

glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

Similar issue
My KF is seeming to have a similar but distinctly different issue as the OP. Because I can turn on the KF without it being plugged in, I cannot imagine that it is a battery issue.
When I plug it in to a Windows machine, the FFF bootloader comes on, the KF seems to connect, be recognized, fail at driver installation (which I have done manually, with no success), and then disconnect. This prevents me from running any sort of commands.
When I connect to my Mac, I get the FFF bootloader and then no response whatsoever.
Trying to run commands from Terminal or the Command line or using KFU on my Windows machine all result in a "waiting for device" message.
Not sure what I should do from this point to get it back to accepting adb commands. I'm confident that once I do I'll be able to save it, but at this point I'm stuck.
Any ideas?

Kindle Fire HD 7 bootloop and no ADB

Hi guys,
First of all I am new to this forum but i have read almost every thread about this subject but i can't seem to find my exact situation.
So yesterday I decided I wanted to root my kindle fire HD 7 and put Cynangonmod on it. So i found this video of a guy explaining it and I downloaded the files he provided and I followed his steps.
That is when the first problem came up. He wanted me to install the ADB drivers which I couldn't get done. It told me something like '' could not install the drivers, please install them manually ''.
Thats is when I came to you guys and I noticed there were a lot of people having the same problem. I had to download some other replacement drivers and install those but even that didn't work so I was basically out of luck.
After a couple hours I managed to get the drivers functioning after deleting them and installing them again. I was surprised this actually worked because I did try that before.
But anyway the drivers were working and my kindle responded just like in the video. I followed the steps in the video and I was happy to see some progression. So my device basically was rooted at this point. So just like in the video I transferred the recovery files, CM-11 and the GAPPS I downloaded to my Kindle while strictly following the steps in the video. Next up I used ES file manager to open up the APK file and install it. At this point I exactly followed the tutorial by selecting the right files and checking the right boxes in the Fire Flash menu. Everything looked OK.
I flashed and installed the script like in the tutorial and pressed rebooted into recovery. Unfortunately this is when the party was over.
Instead of the device booting up and saying Kindle Fire with Fire being orange and turning Blue after a couple seconds, my device just booted without turning blue and was basically looping the hole time.
This was a real bummer since I was so happy that I luckily passed the hole ADB driver issue.
Now when I connect my Kindle to my computer nothing happens....just nothing...my computer doesn't even recognize my Kindle at all. So I decided to search the web for this bootloop problem and I downloaded several utility's which should unbrick my Kindle. But since my computer doesn't even recognize my Kindle actually being plugged in these tools will never work anyway.
I have no idea what is going on but it seems like it's the ADB drivers not functioning again? and what I should do now? Or can I just throw my Kindle in the trash?
This is the video I used on YouTube. You might want to watch this to understand my situation.
/watch?v=PVuvR-hHOLE
The files I downloaded are in the description of the video. I do not have the unbrick utilities and the replacement drivers anymore. But that doesn't matter now anyway since my computer doesn't recognize my device.
Please help me guys!!
Thanks!

Maric98 said:
Hi guys,
First of all I am new to this forum but i have read almost every thread about this subject but i can't seem to find my exact situation.
So yesterday I decided I wanted to root my kindle fire HD 7 and put Cynangonmod on it. So i found this video of a guy explaining it and I downloaded the files he provided and I followed his steps.
That is when the first problem came up. He wanted me to install the ADB drivers which I couldn't get done. It told me something like '' could not install the drivers, please install them manually ''.
Thats is when I came to you guys and I noticed there were a lot of people having the same problem. I had to download some other replacement drivers and install those but even that didn't work so I was basically out of luck.
After a couple hours I managed to get the drivers functioning after deleting them and installing them again. I was surprised this actually worked because I did try that before.
But anyway the drivers were working and my kindle responded just like in the video. I followed the steps in the video and I was happy to see some progression. So my device basically was rooted at this point. So just like in the video I transferred the recovery files, CM-11 and the GAPPS I downloaded to my Kindle while strictly following the steps in the video. Next up I used ES file manager to open up the APK file and install it. At this point I exactly followed the tutorial by selecting the right files and checking the right boxes in the Fire Flash menu. Everything looked OK.
I flashed and installed the script like in the tutorial and pressed rebooted into recovery. Unfortunately this is when the party was over.
Instead of the device booting up and saying Kindle Fire with Fire being orange and turning Blue after a couple seconds, my device just booted without turning blue and was basically looping the hole time.
This was a real bummer since I was so happy that I luckily passed the hole ADB driver issue.
Now when I connect my Kindle to my computer nothing happens....just nothing...my computer doesn't even recognize my Kindle at all. So I decided to search the web for this bootloop problem and I downloaded several utility's which should unbrick my Kindle. But since my computer doesn't even recognize my Kindle actually being plugged in these tools will never work anyway.
I have no idea what is going on but it seems like it's the ADB drivers not functioning again? and what I should do now? Or can I just throw my Kindle in the trash?
This is the video I used on YouTube. You might want to watch this to understand my situation.
/watch?v=PVuvR-hHOLE
The files I downloaded are in the description of the video. I do not have the unbrick utilities and the replacement drivers anymore. But that doesn't matter now anyway since my computer doesn't recognize my device.
Please help me guys!!
Thanks!
Click to expand...
Click to collapse
Have you tried getting into recovery manually? Turn the device on, immediately hold down volume up while the logo is still yellow, keep holding until a few seconds after it turns blue, it should go into twrp if you flashed twrp correctly. If worse comes to worst you can always use a fastboot cable to recover from this. Also adb is not supposed to work when you are at a bootloader screen, at most you probably could access fastboot if the logo turns blue, because the device may breifly show up as a tate device with second bootloader installed, normally it wouldnt. You would have to isntall the drivers in that brief moment or run a ubuntu live cd to do it. Anyways tell me if you can get into recovery.

stunts513 said:
Have you tried getting into recovery manually? Turn the device on, immediately hold down volume up while the logo is still yellow, keep holding until a few seconds after it turns blue, it should go into twrp if you flashed twrp correctly. If worse comes to worst you can always use a fastboot cable to recover from this. Also adb is not supposed to work when you are at a bootloader screen, at most you probably could access fastboot if the logo turns blue, because the device may breifly show up as a tate device with second bootloader installed, normally it wouldnt. You would have to isntall the drivers in that brief moment or run a ubuntu live cd to do it. Anyways tell me if you can get into recovery.
Click to expand...
Click to collapse
Thanks for your reply!
I have actually tried to holding down the volume button when it turns on but it doesn't do anything. It's like the device is ignoring me and just keeps looping.

Could be the recovery partition is screwed up but that would only happen if you had a bad recovery image. This is going to get a bit complicated. I recommend using a Ubuntu live CD for this because you won't run into a very annoying driver issue if you use Ubuntu, though they just released a update and I don't know for sure if the package names are the same. Use the latest Ubuntu if you choose to do this or you could simply get a fastboot cable or the blackhat fastboot adapter that goes in between the kindle and the cable. You simply need to try to flash a recovery IMG through fastboot. It should be pretty straight forward, no need to return to stock kindle os to fix this assuming my theory as to why its doing this is correct.
If you wanna use Ubuntu then grab the latest version from their site(think its 14.something) and either burn it to a CD or make a bootable USB using either their instructions, or my preferred utility unetbootin, then boot up into Ubuntu live os and open the settings and look for something about software update. I haven't upgraded to the latest distro so this bit of info is a bit guess and check. If you find software update then make sure all the download from internet boxes are checked then hit close, if it asks to reload choose yes and ignore the first command i'm about to mention. Open a terminal, run these commands in order:
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot android-tools-adb
sudo fastboot -i 0x1949 getvar product
Once it says waiting for device, plug the kindle in with the power off, it should then go into fastboot since you have 2nd bootloader installed. Normally this method wouldn't work without a second bootloader unless you are on the 8.9". From there you can open the 2.7 zip of twrp and extract the img file from it to your home folder and run:
Code:
sudo fastboot -i 0x1949 flash recovery recovery-image-name-here
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
Could be the recovery partition is screwed up but that would only happen if you had a bad recovery image. This is going to get a bit complicated. I recommend using a Ubuntu live CD for this because you won't run into a very annoying driver issue if you use Ubuntu, though they just released a update and I don't know for sure if the package names are the same. Use the latest Ubuntu if you choose to do this or you could simply get a fastboot cable or the blackhat fastboot adapter that goes in between the kindle and the cable. You simply need to try to flash a recovery IMG through fastboot. It should be pretty straight forward, no need to return to stock kindle os to fix this assuming my theory as to why its doing this is correct.
If you wanna use Ubuntu then grab the latest version from their site(think its 14.something) and either burn it to a CD or make a bootable USB using either their instructions, or my preferred utility unetbootin, then boot up into Ubuntu live os and open the settings and look for something about software update. I haven't upgraded to the latest distro so this bit of info is a bit guess and check. If you find software update then make sure all the download from internet boxes are checked then hit close, if it asks to reload choose yes and ignore the first command i'm about to mention. Open a terminal, run these commands in order:
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot android-tools-adb
sudo fastboot -i 0x1949 getvar product
Once it says waiting for device, plug the kindle in with the power off, it should then go into fastboot since you have 2nd bootloader installed. Normally this method wouldn't work without a second bootloader unless you are on the 8.9". From there you can open the 2.7 zip of twrp and extract the img file from it to your home folder and run:
Code:
sudo fastboot -i 0x1949 flash recovery recovery-image-name-here
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
That actually sounds really difficult.
Just to be clear there is no way to do this on just Windows 7 or OSX? Instead of installing Ubuntu ( which I am not familiar with ). Also could you explain a bit more about the functions of those fastboot cables / adapters because I don't really understand what they do and are you sure those will work with the status of my device? I assume as soon as I get that cable / adapter I Need to plug my device in to the computer and have to get it working via some commands? But anyway is there a way I can stick to windows or mac OSX ( Which I did not use before in the rooting process )

, mac os, normally I would hate mac os just because its a bit nooby and i don't agree with apples policy towards open source(or the lack of) and finding loopholes in whatever the license the unix kernel was under, but this time it may actually be useful, mac is is based on a Unix kernel, which is in a manner similar to the Linux kernel that Ubuntu uses. If you have used a mac then using Ubuntu would be easy, but in this case you shouldn't need to because it should load the drivers up immediately like in Ubuntu. Just grab the android SDK for mac os since i don't think the Linux binaries are compatible. Try placing the extracted android SDK on your desktop, and put previously mentioned recovery img file in the same folder as the fastboot command, open a terminal from applications>utilities and CD into the directory on the desktop that fastboot is in, and try running the fastboot commands I mentioned. Not sure if sudo is needed or not on a mac.
OK as to fastboot cables/adapters, basically you plug your kindle into it and the PC, and your kindle immediately kicks into fastboot mode. You could easily repair it fro windows in this manner since the Tate device would hang around so you could update it's driver without much difficulty. Tech locally you could try the same on windows without a fastboot cable but the device would only appear for a few seconds before it disappears making it hard to install the drivers in that time frame.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
, mac os, normally I would hate mac os just because its a bit nooby and i don't agree with apples policy towards open source(or the lack of) and finding loopholes in whatever the license the unix kernel was under, but this time it may actually be useful, mac is is based on a Unix kernel, which is in a manner similar to the Linux kernel that Ubuntu uses. If you have used a mac then using Ubuntu would be easy, but in this case you shouldn't need to because it should load the drivers up immediately like in Ubuntu. Just grab the android SDK for mac os since i don't think the Linux binaries are compatible. Try placing the extracted android SDK on your desktop, and put previously mentioned recovery img file in the same folder as the fastboot command, open a terminal from applications>utilities and CD into the directory on the desktop that fastboot is in, and try running the fastboot commands I mentioned. Not sure if sudo is needed or not on a mac.
OK as to fastboot cables/adapters, basically you plug your kindle into it and the PC, and your kindle immediately kicks into fastboot mode. You could easily repair it fro windows in this manner since the Tate device would hang around so you could update it's driver without much difficulty. Tech locally you could try the same on windows without a fastboot cable but the device would only appear for a few seconds before it disappears making it hard to install the drivers in that time frame.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thanks I hope my mac will get the job done. It would make it a lot more easier than going linux I think.
Ok. Ill try it on my mac. I will now download Android SDK and place the extracted file on my desktop. I guess I install all tools and all that. And keep you up-to-date.
I downloaded the SDK and placed the folder to my desktop and opened the SDK manager by going to sdk / tools / android and installed SKD tools and SDK platform Tools. Although when i downloaded it it gave me a log that told me something like '' Stopping ADB server failed (code -1). '' And now I get a red checkmark. I don't know if getting a red checkmark is actually good. And i don't know if it's installed now and if the error message matters.

Problem with fastboot (ZE550ML)

Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"

kanagawaben said:
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
Click to expand...
Click to collapse
You need to rename the system image to system.img and put it where the fastboot file is. It's looking for it but can't find it.

No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.

Cause Windows sucks. I'm on Linux and no issues. Maybe someone on Windows can chip in?

I can easily do a quick ubuntu install and try it that way if you think it might work better. At the weekend maybe. Could you give me some pointers on how to do it in linux if I do? Would be much appreciated!

kanagawaben said:
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Click to expand...
Click to collapse
I have encountered that problem with the "waiting for device" while I was flashing pre root rom.
Try the cmd adb devices
Then it will list the device connected to the computer...if it says not authorized, then you need to check the phone which is turned on and a pop up window with the RSA key and tap on trust this computer or something..
Then repeat adb devices and it should say allow or something..then it will allow you to flash.
(double check the commands online, I might missed something)

Nah, don't blame Windows... I flashed mine with Windows 10 and worked wonders.
Also... could it be that PC isn't USB 3.0? Perhaps system.img transfer is stopped somewhere during the copying phase?

Thanks, but actually the first time I tried it I did the adb devices command and authorised my pc on the phone. When I connect and do adb devices now it shows the string of numbers code for the device. However, still can't get past "waiting for device"

My pc has both usb 3 and usb 2 ports. Tried on all of them and with various different cables including the asus issued ones, all to no avail.

Can u post a pic of your flashtool folder?
Sent from my Nexus 7

Here is a snap of my platform-tools folder and cmd window

Did you manage to find a solution to this?
I updated the zenfone 2 via OTA to the latest system update.
Ive read and downloaded all relevant files to install the pre root img from the correct sources.
Now when I hold power + vol up. I can see the droid on its back. I choose the RECOVERY option and press power button to select.
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
All the correct drivers are installed into Windows 7, the phone asks me to allow RSA key connection to laptop.
Ive tried the flash tool installer 1.0.7 with phone connected and system img (renamed) and still nothing.
Anyone got any ideas?
Ive factory reset twice in a row and allowed debugging.
Ive placed the (renamed) system.img into the fastboot folder and tried the open command with line ' fastboot flash system system.img' and the reply is usually unable to read system.img or device waiting.
Ive installed the latest android sdk develppment kit and still unable to root using this pre root image.
Im familiar with android and how to follow instructions on rooting, but this zenfone 2 is mind boggling.
Thanks for reading. I know its someone else post. I didnt want to start a fresh post with the same dilemma.
Any advice on whats going wrong would be appreciated.

tsam19 said:
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
Click to expand...
Click to collapse
Hit power and vol up again, just really quickly. Don't hold it, just press and let go. Sometimes it takes several attempts.

hkdmjack, yes your right managed to do it at last.
Cheers

Hi guys, I am facing quite a difficult problem at the moment.
My friend has "accidentally" attempted to use an Asus Zenfone 5 rooting method to root his zenfone 2 550ML.
When I received it to take a look at it, I instantly noticed that I could not get into fast boot (or droidboot). I expected to see usual droid with text on the left side and also expected to be able to select from a number of options using the volume keys (i have some past experience), but instead am met with this solid usb logo. One like this: h ttp://zenfo ne-blog-forum.2 8820.n7.nabble.c om/file/n4 5/P_20140728_051139 .jpg (remove spaces)
I did some research, and found that there were many "bricked" zenfone 5's which were stuck on this usb logo, however this zenfone 2 can start up normally and be used throughout the day normally. Only when I try to enter fast boot, by either ADB commands or by power + volume up, I cannot get past the usb logo.
I have linked up the ZenFone to my computer, and confirmed that ADB devices correctly lists the device (I have usb debugging enabled), however, when I try to go to fast boot and am met with the usb logo, my computer does register and detect the phone, however, under device manager it has a yellow triangle with the device named "" MOOREFIELD". When the ZenFone 2 is in this usb logo state, I cannot access any fast boot commands. I am quite stumped at the moment.
Any help please? By the way, I use a windows 8.1 computer with usb 3 ports. However, I have tested using different cables, and on a windows 7 laptop with usb 2 ports, still to no avail. Should I try and update the firmware using Asus' software? Or is there a better solution?
Thanks
Edit: My friend claims that he did not see at any point in time, the flashing on the zenfone 2 start. He was faced with a "<waiting for devices>" or something similar message, telling me that the phone was not fully in fast boot yet. If I can get it into fast boot, I am sure I can reflash the custom stock onto the phone, and most issues will be resolved.

same error
i have the same error by my zenfone2 after update
please help

amohammadiazar said:
i have the same error by my zenfone2 after update
please help
Click to expand...
Click to collapse
Could you specify which update you did? From your computer? Or via Asus update on ur phone?

pkvk9122 said:
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
Click to expand...
Click to collapse
my orginal firmware is CN and i wanted to change to WW mode i tried by pc .... now when i conect phone t pc it want moorefeild driver for conection and i dont have those ,,

Whenever I try to flash system.img it gets stuck on "writing 'system'..." and just hangs there. I have left it for over half an hour and it still didn't work. Does anyone know a solution to this problem?

Hey guys,
So after a while without any responses, I headed over to Asus customer service to receive a very unhelpful reply.
I gave up hope of finding an answer online and so I decided to take a leap of faith by updating the firmware via the Asus Update app on the phone.
I upgraded from 2.14 to 2.15 and miraculously fastboot seemed to have restored itself. I am not sure whether or not every single update restores fastboot, or whether the update to 2.15 does, but I'm glad that it has been fixed.
My previous problems of being unable to detect fast boot devices has been resolved. Hopefully others who have experienced the same issue can find this post helpful.