Related
I tried rooting my evo and now every time I start it up it vibrates once and stays on the black lettered "HTC Evo 4G" screen. Help please. And if you can, can you make it so it's noob friendly step by step answer because I am a androind noob a bit.
When I try to go and recover it from the Hboot screen it shows a red triangle with an exclamation point.
jacker300 said:
I tried rooting my evo and now every time I start it up it vibrates once and stays on the black lettered "HTC Evo 4G" screen. Help please. And if you can, can you make it so it's noob friendly step by step answer because I am a androind noob a bit.
When I try to go and recover it from the Hboot screen it shows a red triangle with an exclamation point.
Click to expand...
Click to collapse
How far along into the process did you get? Please give me more info. I am willing to help but in the future try to be as detailed as you can in the original post so that the community can better assist you. Feel free to send me a PM and I will try to guide you. Also after your issue is settled please come back to the post and list the methods and steps you used to rectify the problem. It helps the rest of the community which may have the same problem.
The red triangle means you don't have a recovery like clockwork or amon RA installed. You can fix this by doing a quick search on xda for "HTC Evo amon RA." That will bring up the thread with the image you can flash.
Also, like wc_outlaw stated, we need more information.
Were you rooted before or is this your first attempt?
What method did you use? UnrEVOked or Revolutionary?
What is your radio version?
How far through the rooting process did you get?
Did you see any error messages?
Did you observe any weird behavior from your phone?
When you load into your hboot does it say S-on or S-off?
What hboot version do you have?
All of this information will narrow down things for us that will help us give you a more accurate answer in a shorter period of time.
Sent from my V6 Supercharged Evo.
Thanks for the replies, but I managed to fix it by using this version of RUU:
"RUU_SuperSonic_GB_Sprint_WWE_4.24.651.1_Radio_2.15.00.05.02_NV_2.15_release_199233_signed"
Here is what I did in steps and I will try to be descriptive keep in mind that I did this on Windows 7 and Windows vista should be similar but I don't know about XP. I know this seems like a lot of steps, but the whole process took me only about 5-8 mins:
*BEFORE DOING ALL OF THIS DELETE ANY OLD DRIVERS FROM THE DEVICE MANAGER AND YOUR ADD/REMOVE PROGRAMS IN YOUR CONTROL PANEL!*
- Go to this( wwwyou.tube.com/watch?v=qkRN1wd6SEM) video and in the description download the 2 links!. Credit goes to him for uploading them. I can't post them here because I don't got 8 posts yet. Just add the . between "www" and "youtube" and delete the . between "you" and "tube"
1) Download RUU(I don't think the latest one makes a difference either)
2) Download evo drivers
3) Unzip the evo drivers but don't touch them
4) After take out the battery from your evo and your evo should be OFF when the battery is taken out
5) plug in the usb to your evo and computer
6) put the battery back in the evo and hold the "power button" + " volume DOWN" button till you get to a screen with 3 skateboarding robots at the bottom
7) Select fast boot
8) Stay on that screen that shows power down, restart, etc, but DON'T touch anything
9) With your usb still plugged in and being on the fast boot screen you should see your computer installing the drivers for HTC( Doesn't matter if they successfully install or fail. I will get to that)
10) Now on your computer press start and right click on my computer and click manage
11) After that a window should pop up and click on the left hand side click "Device Manager"
12) You should see USB android device or android devices or something. Drop the list down by pressing the "+" next to it on its left
13) "MY HTC" Should show under the box. Right click that and select "update driver software"
14) With a new window popping up something that says search on my computer something like that
Make sure that "check sub-folders" is checked
Now browse and go to the extracted HTC drivers folder and click on it ONCE and DON'T click any of the sub folders within it. Just the folder that has all the other folders in inside it. ( Example you click: Desktop/HTC Drivers, and NOT: Desktop/HTC Drivers/AMD64)
Now it should detect it and install it.
============================================================
*IF YOU DON'T SEE USB ANDROID DEVICE OR ANDROID DEVICES THEN FOLLOW THIS. IF YOU DO SEE IT THEN IGNORE THIS PART AND SKIP TO STEP 15!*
- Ok you might see a yellow triangle box with an exclamation point next to a device in device manager.
- Press the "+" and it should say like ABD device
- Right click on it and click update driver software.
- With a new window popping up something that says search on my computer something like that
- Make sure that "check sub-folders" is checked
- Now browse and go to the extracted HTC drivers folder and click on it ONCE and DON'T click any of the sub folders within it. Just the folder that has all the other folders in inside it. ( Example you click: Desktop/HTC Drivers, and NOT: Desktop/HTC Drivers/AMD64)
- Now it should detect it and install it.
- Follow step 15 now
============================================================
15) Once installed run the RUU file that you downloaded(*Windows 7, Vista users run as admin and compatibility mode of Windows XP Service Pack 3!*)
16) Make sure your evo is still connected and is still in the fast boot screen
17) Follow the onscreen instruction on RUU
18) When a progress bar(0-100% Bar) shows up on RUU just let it do its thing and DON'T OPEN ANYTHING, OR CANCEL RUU!
19) Make sure your computer DOESN'T go in to Sleep, hibernation mode
20) Once it's done it should reboot and your evo should be working.
Cheers!
Hope I helped!
jacker300 said:
I tried rooting my evo and now every time I start it up it vibrates once and stays on the black lettered "HTC Evo 4G" screen. Help please. And if you can, can you make it so it's noob friendly step by step answer because I am a androind noob a bit.
When I try to go and recover it from the Hboot screen it shows a red triangle with an exclamation point.
Click to expand...
Click to collapse
Does your hboot say s-on or s-off? if s-off, you're rooted, just no recovery. In that case, go to the dev section and download your recovery of choice. The red exclamation mark you see when you go into recovery is stock recovery [no recovery].
jacker300 said:
Thanks for the replies, but I managed to fix it by using this version of RUU:
"RUU_SuperSonic_GB_Sprint_WWE_4.24.651.1_Radio_2.15.00.05.02_NV_2.15_release_199233_signed"
Here is what I did in steps and I will try to be descriptive keep in mind that I did this on Windows 7 and Windows vista should be similar but I don't know about XP. I know this seems like a lot of steps, but the whole process took me only about 5-8 mins:
*BEFORE DOING ALL OF THIS DELETE ANY OLD DRIVERS FROM THE DEVICE MANAGER AND YOUR ADD/REMOVE PROGRAMS IN YOUR CONTROL PANEL!*
- Go to this( wwwyou.tube.com/watch?v=qkRN1wd6SEM) video and in the description download the 2 links!. Credit goes to him for uploading them. I can't post them here because I don't got 8 posts yet. Just add the . between "www" and "youtube" and delete the . between "you" and "tube"
1) Download RUU(I don't think the latest one makes a difference either)
2) Download evo drivers
3) Unzip the evo drivers but don't touch them
4) After take out the battery from your evo and your evo should be OFF when the battery is taken out
5) plug in the usb to your evo and computer
6) put the battery back in the evo and hold the "power button" + " volume DOWN" button till you get to a screen with 3 skateboarding robots at the bottom
7) Select fast boot
8) Stay on that screen that shows power down, restart, etc, but DON'T touch anything
9) With your usb still plugged in and being on the fast boot screen you should see your computer installing the drivers for HTC( Doesn't matter if they successfully install or fail. I will get to that)
10) Now on your computer press start and right click on my computer and click manage
11) After that a window should pop up and click on the left hand side click "Device Manager"
12) You should see USB android device or android devices or something. Drop the list down by pressing the "+" next to it on its left
13) "MY HTC" Should show under the box. Right click that and select "update driver software"
14) With a new window popping up something that says search on my computer something like that
Make sure that "check sub-folders" is checked
Now browse and go to the extracted HTC drivers folder and click on it ONCE and DON'T click any of the sub folders within it. Just the folder that has all the other folders in inside it. ( Example you click: Desktop/HTC Drivers, and NOT: Desktop/HTC Drivers/AMD64)
Now it should detect it and install it.
============================================================
*IF YOU DON'T SEE USB ANDROID DEVICE OR ANDROID DEVICES THEN FOLLOW THIS. IF YOU DO SEE IT THEN IGNORE THIS PART AND SKIP TO STEP 15!*
- Ok you might see a yellow triangle box with an exclamation point next to a device in device manager.
- Press the "+" and it should say like ABD device
- Right click on it and click update driver software.
- With a new window popping up something that says search on my computer something like that
- Make sure that "check sub-folders" is checked
- Now browse and go to the extracted HTC drivers folder and click on it ONCE and DON'T click any of the sub folders within it. Just the folder that has all the other folders in inside it. ( Example you click: Desktop/HTC Drivers, and NOT: Desktop/HTC Drivers/AMD64)
- Now it should detect it and install it.
- Follow step 15 now
============================================================
15) Once installed run the RUU file that you downloaded(*Windows 7, Vista users run as admin and compatibility mode of Windows XP Service Pack 3!*)
16) Make sure your evo is still connected and is still in the fast boot screen
17) Follow the onscreen instruction on RUU
18) When a progress bar(0-100% Bar) shows up on RUU just let it do its thing and DON'T OPEN ANYTHING, OR CANCEL RUU!
19) Make sure your computer DOESN'T go in to Sleep, hibernation mode
20) Once it's done it should reboot and your evo should be working.
Cheers!
Hope I helped!
Click to expand...
Click to collapse
You didn't fix your problem. All you did by running that RUU was unroot your phone. You still have the stock recovery on your phone. So when you try to flash a ROM you will get the same red triangle that you did before. The reason is because you don't have a custom recovery installed that is necessary to flash a custom ROM.
In order to actually fix your problem you need to do what Teh Roxxorz and I suggested.
Concordium said:
You didn't fix your problem. All you did by running that RUU was unroot your phone. You still have the stock recovery on your phone. So when you try to flash a ROM you will get the same red triangle that you did before. The reason is because you don't have a custom recovery installed that is necessary to flash a custom ROM.
In order to actually fix your problem you need to do what Teh Roxxorz and I suggested.
Click to expand...
Click to collapse
Alright, thanks! I'm going to do that later
I'm in bad shape and need some help. I rooted my kindle fire with KFU. All went well but I beleive SU didn't install. I read to flash TWRP and then just install a custom ROM which would have SU.
I flashed TWRP which said it was successful (never saw the yellow triangle though). At that time I made a backup of the stock rom. That went ok as well. I then wiped everything/factory reset from TWRP and tried to install CM7. That was unsuccessful. Once I rebooted I am stuck at the Kinle Fire logo.
I've tried the unbrick utility and it doesn't work. I've uninstalled/reinstalled the driver numerous times and windows does recognize the fire and TWRP sees the device as online. I think I may be stuck in fastboot mode so I tried TWRP to change to normal. No dice. It gets stuck saying waiting for device.
I must say that when the kindle is plugged in to the compter I think it's connecting and disconnecting quickly because it's in a bootloop. Windows is dinging and donging. I also cannot boot into TWRP.
Any thoughts would be greatly appreciated. My daughters are going to kill me. I've rooted many devices and don't consider myself a noob by anymeans so I'm willing to try anything. Thanks in advance.
I forgot to mention that basically anything I try in TWRP I receive these two messages
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
1 Are you able to power it down completely and reboot it to the fff logo?
2 When you plug it in do you have light on the power button?
Sounds like a boot loop yes
But I don't think your completely sunk
You might want to look into getting a factory cable I did a bit of reading on this last night here http://forum.xda-developers.com/showthread.php?t=1392693
But since its dinging and donging in windows open device manager up and see how its being listed there and what drivers its using.
Try plugging it to AC maybe you can break the loop that way
If you can get to twrp try factory restore then reboot system
If it didn't push superuser when you rooted it that could be a problem it took me twice sorry to say
Did you not create a backup before flashing cm7?
Restoring your backup is followed by the error you mentioned above?
Also with kf utility open try plugging and unplugging the USB maybe you will get a split second to hit a key choose manage boot modes if it stabilizes there are options for stock update zip and such or retry root http://forum.xda-developers.com/showthread.php?t=1392693
---------- Post added at 10:51 AM ---------- Previous post was at 10:06 AM ----------
Also look here this was posted yesterday http://forum.xda-developers.com/showthread.php?t=1593493
Thepooch said:
1 Are you able to power it down completely and reboot it to the fff logo?
2 When you plug it in do you have light on the power button?
Sounds like a boot loop yes
But I don't think your completely sunk
You might want to look into getting a factory cable I did a bit of reading on this last night here http://forum.xda-developers.com/showthread.php?t=1392693
But since its dinging and donging in windows open device manager up and see how its being listed there and what drivers its using.
Try plugging it to AC maybe you can break the loop that way
If you can get to twrp try factory restore then reboot system
If it didn't push superuser when you rooted it that could be a problem it took me twice sorry to say
Did you not create a backup before flashing cm7?
Restoring your backup is followed by the error you mentioned above?
Also with kf utility open try plugging and unplugging the USB maybe you will get a split second to hit a key choose manage boot modes if it stabilizes there are options for stock update zip and such or retry root http://forum.xda-developers.com/showthread.php?t=1392693
---------- Post added at 10:51 AM ---------- Previous post was at 10:06 AM ----------
Also look here this was posted yesterday http://forum.xda-developers.com/showthread.php?t=1593493
Click to expand...
Click to collapse
1. I can power down completly and upon rebooting is when I am stuck at the Kindle fire logo.
2. When plugged in I do have a light on the power button.
3. I've briefly looked in to the factory cable and that is an option
4. I see in device manager the Android Phone
5. Plugging it into AC all night didn't help.
6. I did create a backup but I can no longer boot in to TWRP
7. TWRp does see the kindle as online and I can make the selection for boot mode but whatever I choose it comes back with
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
I have the same problem...
I didn't didn't install FireFireFire (I'm a noob so I didn't know what it was for until now)
I rooted my device (I think. KFU said it was rooted)
I wanted to install CM7.
I went into TWRP and wiped everything I was supposed to. (Got into TWRP through KFU.)
Tried to install Cyan7 and failed.
I booted down my kf and now whenever I try to turn it on it stays stuck on the "kindle fire" screen and won't change. I think I permanently bricked it unless someone has an answer to this problem.
I've also tried the above and I get the same error.
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
My problem sounds the exact same as yours nchevaux
Yep.....that sounds like the exact process I did. I have yet to find anything that will help us out. My last resort is to get the factory cable unless someone pulls through here.
If you figure something out let me know. I'll keep you posted on my progress.
Try this:
From KFU:
press 1 - for boot mode menu
press 1 - for Choose NORMAL MODE (4000)
waiting for device ......
DO NOT STOP KFU !!!!!
shutdown device (press button for 10-20 sec)
start AGAIN
DO NOT STOP KFU !!!!!
killgore said:
Try this:
From KFU:
press 1 - for boot mode menu
press 1 - for Choose NORMAL MODE (4000)
waiting for device ......
DO NOT STOP KFU !!!!!
shutdown device (press button for 10-20 sec)
start AGAIN
DO NOT STOP KFU !!!!!
Click to expand...
Click to collapse
KFU doesn't say "waiting for device"
Also the ADB status is online but the Boot Status is "Unknown"
If you figure something out let me know. I'll keep you posted on my progress.
Click to expand...
Click to collapse
Most definitely. I'll be trying as many different methods I can find. I'll keep you posted as well.
This...
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
is adb telling you that your system is broken. My guess is when you restart your KF, you see the boot logo, the display blacks out, then the boot logo comes back a little bit dimmer this time. It might even brighten up again, but that's where it gets stuck.
If this screen ever blacks out like this at the start of the boot process, you are not in fastboot mode. The KF is continuing to boot into the system, but failing. If you can get back into fastboot mode, flash a new recovery. If you can get into TWRP, I would try reflashing the system. If what I just said makes no sense to you, read this...
http://forum.xda-developers.com/showthread.php?t=1552547
and make sure your drivers are working before you continue.
Fixed
thommyyy said:
KFU doesn't say "waiting for device"
Also the ADB status is online but the Boot Status is "Unknown"
Most definitely. I'll be trying as many different methods I can find. I'll keep you posted as well.
Click to expand...
Click to collapse
Fixed it! I made a factory cable and that put me right in to fastboot. At the point you can flash. I know what I did to put my KF in that state, it was just a lack of patients really. There wasn't anything wrong with the KFU, driver, etc...just the user. I'm sure a factory cable would work for you as well and have you up and running in no time.
This is a really good read http://forum.xda-developers.com/show....php?t=1552547
nchevaux said:
Fixed it! I made a factory cable and that put me right in to fastboot. At the point you can flash. I know what I did to put my KF in that state, it was just a lack of patients really. There wasn't anything wrong with the KFU, driver, etc...just the user. I'm sure a factory cable would work for you as well and have you up and running in no time.
This is a really good read http://forum.xda-developers.com/show....php?t=1552547
Click to expand...
Click to collapse
Link doesn't work. Also I'll try to check that factory cable out. I'm not too sure if I am able to get or make one (currently studying abroad).
Still, is there any way around this w/o the factory cable?
Edit: I looked around and so far the only solution is a factory cable... (no soldering skill at all whatsoever)
thommyyy said:
Link doesn't work. Also I'll try to check that factory cable out. I'm not too sure if I am able to get or make one (currently studying abroad).
Still, is there any way around this w/o the factory cable?
Edit: I looked around and so far the only solution is a factory cable... (no soldering skill at all whatsoever)
Click to expand...
Click to collapse
Look on Ebay. I saw you can purchase factory cables there. I know there are some people in the XDA community making them. You may want to search the forum for factory cable and see if anyone can help you out.
I didn't have soldering skills either, just determination. My cable isn't pretty but it did the job. Search Google for "mini USB breakout board". If you order one of these you probably don't need the precision soldering skills. The breakout board offers much more room to work.
Edit: here is the breakout board you would want. http://www.sparkfun.com/products/10031
Hi All.
I’ve rooted my Kindle device successfully before (during v6.2 – have the driver installed from this and cable worked successfully )
Now with the 6.3.1, I used the KFU v0.9.6 to do it – option 2 ‘Install Permanent Root with Superuser’
Followed the instructions as per http://forum.xda-developers.com/showthread.php?t=1399889
- On my XP machine, it detected my Kindle initially but it stopped and my Kindle Fire was showing the stock welcome screen but kept on rebooting.
- Then I tried on a Win 7 machine and ran option 2 again – it did something and now my Kindle is stuck on the FFF screen (Kindle Fire logo in blue and white – v1.4a).
- Now when I run ‘ran.bat’, pc it shows ‘waiting for device’
- The FFF screen was blinking initially but now it’s permanently on.
- I can off my Kindle by pressing the on button for about 20 seconds and when I connect my Kindle in the off state to the pc, it turns on and remain on the FFF screen
1. Installing the driver
So I figured the above is due to the driver.
- However, the Kindle is not appearing in the Device Manager with a yellow ! – hence can’t manually install the drivers.
- Tried install_drivers.bat – it says ‘Google, Inc. (WinUSB)…..Install failed (Unsigned)’
- I ensured that the ‘Driver Signing Options’ is set to ‘Ignore – Install the software and don’t ask for my approval’ and ‘Make this action the system default’.
- So next, I tried to force my XP to install the drivers (Kindle unplugged), by using ‘Add Hardware’ and installing drivers from c:\kfu\drivers –
- Installed all 3 drivers – Android ADB Interface, Android Bootloader Interface & Android Composite ADB Interface.
- Received this message at the end – ‘The software for this device is now installed, but may not work correctly. The device cannot start. (Code 10)’
- But when I plugged in my Kindle and run KFU it still says ‘waiting for device’.
I tried the above steps with:-
- 3 XP machines and 1 Win 7, and
- on different USB ports (tried both USB 2.0 and 3.0)
- and tried using 4 different usb cables
- Same results ‘waiting for device’
- One exception though – for the Win 7 machine – when I ‘install_drivers.bat’, it says ‘Google, Inc. (WinUSB) ….Ready to use’ – but still shows ‘waiting for device’, when running KFU.
2. Delete old drivers
Followed this (http://forum.xda-developers.com/showthread.php?t=1459116) to uninstall the drivers (including the Microsoft support page).
- But XP and Win 7 still did not detect the Kindle in ‘Device Manager’
- Tried to force install the 3 drivers again and still ‘waiting for device’
Additionally tried to download the Google Usb driver from Android SDK - same issue - no yellow !
And tried to connect via 'c:\KindleAdb\adb devices' (learned from the previous root exercise) - no devices appears.
3. Kindle Fire Unbrick Utility
Tried this next - http://forum.xda-developers.com/showthread.php?t=1428428
Tried the many options available. When it is executed, its says ‘error’, despite saying Kindle unbricked at the end.
4. Firekit LiveUSB repair kit 1.1
Finally decided to use the Linux method (http://forum.xda-developers.com/showthread.php?t=1430038)
- Created a USB Ubuntu and ran the program but suprisingly still the same problem – stuck at ‘waiting for device’ (see snapshot attached).
So I’m a bit confused right now. From the above it seems to me that the Kindle is not talking to the PC.
- But if in Linux, it doesn’t work (which from what I read doesn’t require a driver?) then it could possibly be my cable.
- But the cable did work when I rooted in 6.2 and it also worked initially when I used KFU. And also, I tried with 4 different cables.
- Am not sure if the cables are ‘factory cable’ – but it did work initially.
I’m stuck here. Any help/advice would be deeply appreciated. Thank you.
A few things that might help you...
1) If you have FFF 1.4a, you can access its boot menu and have the device boot normally or into recovery. As it boots up, look at the power button LED and watch as it goes from a bright green to a dim green. As soon as it goes dim, press and release the button to bring up the menu on the screen. You can then flip through the menu options by repeatedly pressing and releasing the power button. Leave it alone for a few seconds and it will continue to boot using the selected option.
2) If you don't know whether or not you have a factory cable, you probably don't have one...
http://forum.xda-developers.com/showthread.php?t=1550999
3) For the computer to issue fastboot commands to the device, it must already be connected to the computer before booting into fastboot mode. That is... you cannot boot the KF into fastboot mode and then connect it to the computer. If the computer is <waiting for device>, try turning the KF off by pressing and holding the power button for around 20 seconds to shut it down completely, then turning it back on again. For more information on fastboot....
http://forum.xda-developers.com/showthread.php?t=1668159
If the above suggestions don't work for you, make sure you are getting the expected hardware IDs shown in the previous link.
Thank you kinfauns for your immediately reply.
kinfauns said:
A few things that might help you...
1) If you have FFF 1.4a, you can access its boot menu and have the device boot normally or into recovery. As it boots up, look at the power button LED and watch as it goes from a bright green to a dim green. As soon as it goes dim, press and release the button to bring up the menu on the screen. You can then flip through the menu options by repeatedly pressing and releasing the power button. Leave it alone for a few seconds and it will continue to boot using the selected option.
Click to expand...
Click to collapse
Unfortunately this doesn't happen on my KF. The power button is bright green. And the bootlogo is persistent and remain bright on the display.
I've tried repeatedly pressing and releasing the power button but didn't work.
2) If you don't know whether or not you have a factory cable, you probably don't have one...
http://forum.xda-developers.com/showthread.php?t=1550999
Click to expand...
Click to collapse
Just bought a USB factory fastboot mode cable online .
3) For the computer to issue fastboot commands to the device, it must already be connected to the computer before booting into fastboot mode. That is... you cannot boot the KF into fastboot mode and then connect it to the computer. If the computer is <waiting for device>, try turning the KF off by pressing and holding the power button for around 20 seconds to shut it down completely, then turning it back on again. For more information on fastboot....
http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
I tried this method but nothing changes - when I turn it back on, it goes back to the bootlogo. KFU still says <waiting for device>.
Also tried 'Temporary fastboot mode' - 'fastboot getvar product' - still <waiting for device>.
If the above suggestions don't work for you, make sure you are getting the expected hardware IDs shown in the previous link.
Click to expand...
Click to collapse
My KF doesn't show up on 'Device Manager' - no yellow question mark or whatsoever.
When I manually installed 'Android ADB Interface' - it shows an yellow ! and even after I connect the KF it still shows the yellow !.
Current hardware ID (for 'Android ADB Interface' with yellow !): usb\vid_0bb4&pid_0c01
Device status: This device cannot start. (Code 10)
So I guess, I will wait for my factory cable, unless you have any other suggestions? Thank you.
ivanovicch said:
My KF doesn't show up on 'Device Manager' - no yellow question mark or whatsoever.
When I manually installed 'Android ADB Interface' - it shows an yellow ! and even after I connect the KF it still shows the yellow !.
Current hardware ID (for 'Android ADB Interface' with yellow !): usb\vid_0bb4&pid_0c01
Device status: This device cannot start. (Code 10)
So I guess, I will wait for my factory cable, unless you have any other suggestions? Thank you.
Click to expand...
Click to collapse
I have no idea what that ID number is, but it's definitely not the one you should see for fastboot. That means you have those drivers installed on the wrong interface. I also suspect your bootloader might be corrupt or otherwise not functioning correctly. Using the factory cable will give you a better idea what's going on since you can (almost) be certain that the device has put itself into fastboot mode. Then you can focus on getting the drivers installed properly for the interface that appears in the device manager. As a last resort, you might have to open up the case and use USB boot (in Firekit) to flash a new bootloader.
Just quickly skimmed over your thread but have you tried holding down the power button for a minute or so and then powering it on? I would tend to agree with kinfauns that somehow your bootloader is broken if so a factory cable will do nothing only firekit will remedy a broken bootloader that's why I ask about the long press power off attempt...
Thepooch said:
Just quickly skimmed over your thread but have you tried holding down the power button for a minute or so and then powering it on? I would tend to agree with kinfauns that somehow your bootloader is broken if so a factory cable will do nothing only firekit will remedy a broken bootloader that's why I ask about the long press power off attempt...
Click to expand...
Click to collapse
I pressed power button for more than a minute - tried 2 ways:-
- with the KF on - it switches off and remains switched off.
- with the KF off - it switches on for a bit and then switches off and remains switched off.
I'll just give the factory cable a try when it arrives - will update here again. Hopefully I don't have to open up the case.
Thanks kinfauns and Thepooch.
I have no idea what that ID number is, but it's definitely not the one you should see for fastboot. That means you have those drivers installed on the wrong interface. I also suspect your bootloader might be corrupt or otherwise not functioning correctly. Using the factory cable will give you a better idea what's going on since you can (almost) be certain that the device has put itself into fastboot mode. Then you can focus on getting the drivers installed properly for the interface that appears in the device manager. As a last resort, you might have to open up the case and use USB boot (in Firekit) to flash a new bootloader.
Click to expand...
Click to collapse
Just quickly skimmed over your thread but have you tried holding down the power button for a minute or so and then powering it on? I would tend to agree with kinfauns that somehow your bootloader is broken if so a factory cable will do nothing only firekit will remedy a broken bootloader that's why I ask about the long press power off attempt...
Click to expand...
Click to collapse
Just to update - the factory cable didn't do the trick. KF still stuck at KF blue/white logo - the bootloader must be corrupted.
Hence am going to try opening the case and flash a new bootloader. Wish me luck - will update again soon. Thanks.
Please help me My Kindle is stuck at black screen after Kindle Fire logo. I have Android Composite ADB Interface driver installed, but when I plugged my Kindle Fire to my PC, it detected as a USB Mass Storage, and won't connect as an Android device so I couldn't do anything with adb commands or KFU...
See it in my topic for more information: http://forum.xda-developers.com/showthread.php?p=30542544#post30542544
ivanovicch said:
Just to update - the factory cable didn't do the trick. KF still stuck at KF blue/white logo - the bootloader must be corrupted.
Hence am going to try opening the case and flash a new bootloader. Wish me luck - will update again soon. Thanks.
Click to expand...
Click to collapse
Dear All. My KF is ALIVE! Had to open my back case and do the short point trick - http://forum.xda-developers.com/showthread.php?t=1405052.
Worked like a charm.
Thanks pokey9000, kinfauns and mainly the Thepooch - thank you for guiding me through this.
your welcome I`m quite pleased its fixed myself
same issue not unable to solve
i have exact same issue but i am having a problem to fix it. i wonder if anyone can help me here. i am trying to short the test point but in device manager its shoing usb not recognized again and again. please guide me whats wrong i am doing. using windows 7 (64bit)
I have kfhd7 (tate) and i updated it from cm12.1 to cm13 but after the reboot it is now stuck on white-blue "kindle fire" logo. everytime i reboot it shows the white-yellow logo and then gets stuck on the blue one. moreover, i cant get to twrp3 using keys as it gets stuck and device gets hot. Tried fastboot and adb but the devices is shown offline. I dont have access to a fastboot cable and even dont hope that i will get one shipped sooner. kinldy help
hasanalikhattak said:
I have kfhd7 (tate) and i updated it from cm12.1 to cm13 but after the reboot it is now stuck on white-blue "kindle fire" logo. everytime i reboot it shows the white-yellow logo and then gets stuck on the blue one. moreover, i cant get to twrp3 using keys as it gets stuck and device gets hot. Tried fastboot and adb but the devices is shown offline. I dont have access to a fastboot cable and even dont hope that i will get one shipped sooner. kinldy help
Click to expand...
Click to collapse
this is only for kindle fire 1 (2011)
there is a separate section for device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Sent from my XT1254 using XDA Labs
There are three parts to this thread - How to get into download mode, how to get into recovery mode, and how to solve problems connecting your Android device to your computer. I think you should be able to find where each one begins without too much trouble.
----------------------------------------------------
GETTING INTO DOWNLOAD MODE
----------------------------------------------------
"Just get into download mode and..."
Ever find yourself with a phone that's misbehaving, and you can't seem to figure out how to get it to download mode?
Here's a list of things to try, sorted in a "where are you now" setup:
Note: You will need to use Vol+ to select download mode after you reach the mode selection screen.
FROM A POWERED-DOWN STATE - BATTERY REMOVED
- Insert battery, then press and hold Vol-, Home button, and Power.
- Press and hold Vol-/Home/Power, Insert Battery.
- Use a USB jig (can be manufactured jig or homemade chain of resistors)
FROM CLOCKWORKMOD RECOVERY MENU
- Position the cursor (highlighted selection) on "Restart device", hold Vol-/Home, then press power
- (Where available) Use the "Reboot Download" option in the "Advanced" menu
FROM A FULLY BOOTED PHONE STATE, WITH USB DEBUGGING ENABLED
Note: you may need to have ADB installed on your computer, and/or an Android Terminal Emulator installed on your Android device.
- Connect your Android device to your computer, navigate to your ADB directory, and type "adb reboot download"
- (Where available) Use the rom's power menu option to reboot into download mode.
- From a terminal, type "su", then "reboot download"
- Download the app "quickboot", follow the app directions to reach download mode.
----------------------------------------------------
GETTING INTO RECOVERY MODE (CWM RECOVERY)
----------------------------------------------------
FROM A POWERED-DOWN STATE - BATTERY REMOVED
- Insert battery, then press and hold Vol+, Home button, and Power.
- Press and hold Vol+/Home/Power, Insert Battery.
FROM A FULLY BOOTED PHONE STATE, WITH USB DEBUGGING ENABLED
Note: you may need to have ADB installed on your computer, and/or an Android Terminal Emulator installed on your Android device.
- Connect your Android device to your computer, navigate to your ADB directory, and type "adb reboot recovery"
- (Where available) Use the rom's advanced power menu (long press power in android OS) option to reboot into recovery.
- From a terminal emulator, type "su", then "reboot recovery"
- Download the app "quickboot", follow the app directions to reach recovery mode.
- Download the app "Rom Manager", select "Reboot to Clockwordmod Recovery"
----------------------------------------------------
UNIVERSAL FIRST STEPS FOR CONNECTION ISSUES
----------------------------------------------------
So you've got Odin up, the phone's in download mode, it's connected to the computer, but Odin is saying "What phone?". You've tried jiggling the handle, checking the blinker fluid levels, and even using the board stretcher, but the Android guy is smirking at you with that smug green face.
Although it is possible that there is something else at work that's preventing your phone from connecting, I would suggest trying these "universal first steps" to see if you can resolve the connection issues:
1. Turn off both devices (phone and PC) - and I do mean full power-down. Go ahead and pull the phone's battery, if necessary.
2. Disconnect your phone from your computer at all points - USB out of phone, USB out of computer.
3. Start up your computer. Don't touch it, don't do anything to it. Let it fully boot and completely settle.
(Obviously, log in if it's necessary, but then let it finish booting before moving on to step 4.)
4. Start up Odin. Let that get completely started and settled.
(If on Vista/Win 7, make sure to "Run as Administrator" in the right-click menu.)
5. Connect your USB cable to a different port than the one you last had it connected to.
(If you're on a Windows desktop, the ports in the back of the computer are generally more stable and should be used. If you're on a laptop, use USB port #1)
Do not connect the phone to the cable yet.
6. Start your phone in download mode. Wait until you see the Android guy with the 4-5 lines of text in the upper left corner.
7. Connect your cable to the phone. Let it sit until Odin recognizes it (which should only take a couple of seconds).
If, for some reason, Odin doesn't recognize the phone at this point, here are a few more things to check/try:
- Repeat steps 1-7 above, making sure to change USB ports. As dumb as it sounds, sometimes the phone or computer just doesn't like particular USB ports.
- With everything still up, switch USB ports.
- Try a different OS (if possible) - sometimes Ubuntu will recognize what Windows won't, and vice versa.
- Try doing this on a different computer - again, different OS, different USB ports, they're all links in a chain and sometimes you'll come across a configuration that doesn't have the weak link.
- Try a different cable. I've had a case where I couldn't do any flashing with one cable, but everything was rock-solid and smooth on the same machine with just a different cable.
- Fully uninstall your drivers, reboot the computer, reinstall the drivers, power down, and then start again from step 2. Sometimes faulty drivers are the problem.
--------------------------------------
Additional Note:
If you're moving from an AOSP-based rom (MIUI, CM10, etc) to a Touchwiz-based / Samsung Stock-based rom, remember to wipe data / factory reset prior to flashing a stock rom. You will hang on the "Samsung" logo if you don't.
Please note very carefully, though, to do the wipe in CWM recovery - not 3e recovery. If you do it in 3e recovery, you'll format the internal storage, meaning you lose all your pictures, music, etc.. (I learned this the hard way.)
--------------------------------------------
If anyone has any additional items / corrections, please reply and I'll update the OP accordingly. Thanks.
Reserved
Great guide!
I'd like to add my experiences, while using CWM 6.0.1.2 booting into Recovery is a bit tricky. It appears the default recovery boots instead of CWM. The only work around I know of is to Flash ClockworkMod Recovery first from ROM Manager v5.0.2.0 and then select Reboot into Recovery. Any other method I try seems to fail.
I'm running Stock At&t ROM, rooted.
Hey Mrhaley,
I just found your post. Wish I knew I had to wipe data and factory reset before flashing stock rom... well I followed another post to use kies and now Im stuck. Im hanging on samsung logo. Can you help me fix this?
Thanks
djtiko said:
Hey Mrhaley,
I just found your post. Wish I knew I had to wipe data and factory reset before flashing stock rom... well I followed another post to use kies and now Im stuck. Im hanging on samsung logo. Can you help me fix this?
Thanks
Click to expand...
Click to collapse
OP thanks for exelent post..I had one more problem with USB connection. Sticks in usb port did not connect correctly. Just jently squize USB male connector on samsung data cable so top of male connector will bend just enough to get good connection when you push back to PC port.
@djtiko - I answer on other post to your problem..
djtiko said:
Hey Mrhaley,
I just found your post. Wish I knew I had to wipe data and factory reset before flashing stock rom... well I followed another post to use kies and now Im stuck. Im hanging on samsung logo. Can you help me fix this?
Thanks
Click to expand...
Click to collapse
Do a factory reset again, should fix you up. If not, consider using Odin to flash a stock ROM package.
Thanks got it all fixed, just had to do a data wipe in the stock recovery and then I was golden
ondin
Hey guys when i run the bootloader file should i open it up in the pda tab on ondin or in the Bootloader tab?
Should be in the pda tab I believe.
Edit. Which bootloader file are you referring to? To know for sure, you could just flash the entire stock rooted jelly bean Rom.
If using Odin with Chainfire to auto root just to root I found that the file that you are using to root you HAVE to have in the SAME folder I made the mistake of downloading the Odin then Odin with chainfire from http://forum.xda-developers.com/showthread.php?t=1963790 then was opening the odin first downloaded then it would stall for not able to start the installation then rechecking the unzipped folder for the .tar.md5 file noticed that Odin was there too, loaded it and PRESTO rooted in less than 30 seconds... So for other that are just looking to root give chainfire a check, yes you would need to use the triangle away if you are worried about that however you don't loose anything when doing it this way so all a matter of what you are looking to do. THANK YOU so much for the help with the drivers issues!
Hey guys, before I begin, yes i read the '[HOW-TO] Before asking for troubleshooting help...' page as well as the '[GUIDE] Kindle Fire For Beginners' page, and am still in need of a bit of assistance due to my hilariously lacking knowledge of the workings of electronic equipment. :silly:
I just dug my kindle fire out of my dresser drawer where it has been sitting due to being 'bricked' for quite some time (stuck at the boot logo - white kindle text and orange fire text shimmering on a pure black background - holds a charge but is indefinitely at this screen). It is completely stock, having not downloaded or installed any ROMs or any other software, and initially began experiencing this problem the morning after running it out of battery while downloading a few books and games one night. I promptly plugged it in, went to bed, and woke up to it in this state that next morning.
I have tried downloading Kindle Fire Unbrick V1.1 by ZombiePiratez and running that to fix it, but it does not recognize my kindle fire. So, i downloaded Eclipse ADT with Android SDK for windows and followed some instructions i found for getting it to recognize my kindle as "Android Composite ADB Interface" in hopes that then the unbricking tool would recognize it and work its magic for me. But it didnt. I imagine this is because the process that I followed is flawed.
My question is, if i were to buy a "factory cable" would I be able to unbrick my kindle fire without having to do any of this command promp shamanism thats clearly over my head? Kinfauns states in his guide that "With a factory cable, unbricking just comes down to "plug it in and flash new stuff" in almost every bricking situation." But what does 'flash new stuff' mean; should I have picked that up from the guide as well? Or could I just use the factory cable in conjunction with ZombiePiratez unbricking tool to get back to the factory settings?
Thanks in advance for any pointers
See my How to flash twrp and firefirefire with a Fastboot cable
http://forum.xda-developers.com/showpost.php?p=53652317&postcount=2
Sent from my XT862 using Tapatalk
Hey @sd_shadow !
Thanks for the link to that, the videos you've created make it possible for even someone with my level of tech knowledge to work through this problem. Immensely better than trying to follow a written guide
Anyway, I finally got my fastboot cable and followed the steps in your videos to the tee, however I'm still encountering one small problem. When I get to the point where I'm installing update-kindle-prerooted.6.3.3.v1.zip in TWRP by swiping across the screen, it runs until it gets to the line thanking paulobrien and two others but then promptly freezes (or so i assume since it doesnt continue on and the loading bar halts in its tracks). I decided after a few tries to just hold the power button to get it to shut off and then booted the kindle in normal boot mode - and it worked! - despite not being able to complete the process as shown in your video. But this concerns me, as I do not have any of the additional apps shown in your video (not that this truly matters to me) and under settings -> device it shows that I am running version 6.3.1_user_#####. So I have two questions:
1) Did the fff and twrp processes work, but the 6.3.3 update fail thus enabling me to use my kindle as a v6.3.1 device again?
2) Will it harm my device in any way (e.g. re-bricking) if I just call it good and use it as it is now?
Thanks for all the help so far :highfive:
noobSaurus said:
Hey @sd_shadow !
Thanks for the link to that, the videos you've created make it possible for even someone with my level of tech knowledge to work through this problem. Immensely better than trying to follow a written guide
Anyway, I finally got my fastboot cable and followed the steps in your videos to the tee, however I'm still encountering one small problem. When I get to the point where I'm installing update-kindle-prerooted.6.3.3.v1.zip in TWRP by swiping across the screen, it runs until it gets to the line thanking paulobrien and two others but then promptly freezes (or so i assume since it doesnt continue on and the loading bar halts in its tracks). I decided after a few tries to just hold the power button to get it to shut off and then booted the kindle in normal boot mode - and it worked! - despite not being able to complete the process as shown in your video. But this concerns me, as I do not have any of the additional apps shown in your video (not that this truly matters to me) and under settings -> device it shows that I am running version 6.3.1_user_#####. So I have two questions:
1) Did the fff and twrp processes work, but the 6.3.3 update fail thus enabling me to use my kindle as a v6.3.1 device again?
2) Will it harm my device in any way (e.g. re-bricking) if I just call it good and use it as it is now?
Thanks for all the help so far :highfive:
Click to expand...
Click to collapse
1 yes installing TWRP and FFF reset boot, and allowed 6.3.1 to boot normally
2. the only problem should be that, when connected to wifi, update will redownload and try again once a day or so
Kindle will reboot to TWRP, but update should fail, if that does not bother you it is fine
3. what twrp version did you install? says in twrp if you are not sure
I installed TWRP v2.7.1.0-blaze because that is what you used in the video, even though i had read that 2.2.2.1 may be preferable for stock unrooted kindle fires. I did this so that I could follow your video exactly without having to change any steps except for switching otter to blaze in the cmd promt code I inputted.
Also, as I write this, Ive realized that I still may have made a mistake and installed one of the alternate test files for the 6.3.3 prerooted update and not the complete file itself, so ill get back with that info.
Yeah, i installed the alternate test file the first time :silly:
Went back through and followed your instructions to the 'tee' again and its up and running.
I do have one more question though; when I am using the device I dont get very far before selecting an application or making another command causes the screen to go black, only displaying the time and settings option at the top and the home button, back button, search button, etc at the bottom - none of which respond when selected. This happens with both the go launcher and the kindle launcher, and each time the only way I can stop it is resetting the device... Any suggestions to counteract this?