Database Users

Installing TWRP. Stuck at "waiting for device"

I'm getting this issue with Kindle Fire Utility when trying to install TWRP;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have rebooted my kindle fire while waiting for it, but I haven't been able to find other solutions, please help! I'm fairly sure that I have ADB working... I'm really not sure what to do

georgeos said:
I'm getting this issue with Kindle Fire Utility when trying to install TWRP;
I have rebooted my kindle fire while waiting for it, but I haven't been able to find other solutions, please help! I'm fairly sure that I have ADB working... I'm really not sure what to do
Click to expand...
Click to collapse
If you would have followed my tutorial you wouldnt have this problem here is the fix:
• I have noticed that some people have problems getting stuck around 2:32 into the video where twrp is downloading and getting ready to install. If this happens to you and it is constantly “waiting for device” You may need to hit disconnect on your KF and run burrito root on your Kindle again, click “agree”,then click “You Rock”, Then click “root”. Once you do so you must re-open adb shell by opening a command prompt and typing the following:
cd c:\KindleADB this is to get into adb shell
adb devices this is to make sure your kindle is connected properly
adb root this is to get proper permissions
Just to be very clear on what you should type in your cmd prompt:
cd c:\KindleADB
adb devices
adb root
• Once you have done this re-open the run bat in KFU v0.9.1 and select option 5 again and it will install the twrp with proper root permissions.
here is a link to my tutorial for you to check if you have more problems afterwards:
http://forum.xda-developers.com/showthread.php?t=1417234

[-_-] said:
If you would have followed my tutorial you wouldnt have this problem here is the fix:
• I have noticed that some people have problems getting stuck around 2:32 into the video where twrp is downloading and getting ready to install. If this happens to you and it is constantly “waiting for device” You may need to hit disconnect on your KF and run burrito root on your Kindle again, click “agree”,then click “You Rock”, Then click “root”. Once you do so you must re-open adb shell by opening a command prompt and typing the following:
cd c:\KindleADB this is to get into adb shell
adb devices this is to make sure your kindle is connected properly
adb root this is to get proper permissions
Just to be very clear on what you should type in your cmd prompt:
cd c:\KindleADB
adb devices
adb root
• Once you have done this re-open the run bat in KFU v0.9.1 and select option 5 again and it will install the twrp with proper root permissions.
here is a link to my tutorial for you to check if you have more problems afterwards:
http://forum.xda-developers.com/showthread.php?t=1417234
Click to expand...
Click to collapse
I tried what you said, and have made some progress, the Kindle Fire is rebooting when it comes to say "waiting for device" but then gets stuck at boot, so I have to put it back to normal boot rather than fast boot

georgeos said:
I tried what you said, and have made some progress, the Kindle Fire is rebooting when it comes to say "waiting for device" but then gets stuck at boot, so I have to put it back to normal boot rather than fast boot
Click to expand...
Click to collapse
Once again all of the answers to your problems and the questions you have are in this tutorial. From what it looks like to me from your screen shot you do not have "root Permissions" if this is in fact the problem then what you are probably trying to do is to start at step five from the Kindle Fire Utility and download to install twrp2.0 If this is what you are trying to do then you must see on the command prompt of KFU that you are downloading and then waiting on device. If this is still your situation then the fix is what I stated above and in my link. If you have gotten passed that problem and still have issues with you either being stuck at the yellow triangle( firefirefire ) or a Kindle Fire boot screen that will not go away then the fix is also in my link... If you do not wish to follow the link and see the videos or read through the trouble shooting guide then I am afraid I have no way of helping you...
If I helped please do not forget to hit the thanks button and post back in my guide thread that it worked okay for you as well so that new members can see that this is one of the easiest guides to follow here is a link to take you to that guide a little quicker good luck....
http://forum.xda-developers.com/show....php?t=1417234
If you need further help reply in that thread and I will be more than happy to help you there so others can find the fix to the problem that you come across a little easier

I got stuck in several places when I did it, the issues I had where an old version of adb, and drivers, had to uninstall and reinstall the drivers
Sent from my Kindle Fire using xda premium

Need Help rooting with Kindle Fire Utility

I'm trying to use the Kindle Fire Utility to root and install Google Apps/Market but I'm not getting anywhere with it.
I downloaded the file, ran the Driver Install .bat file. then opened run.bat
It keeps saying that the Kindle Fire is not plugged, and I've plugged it in over and over and over.
Its not listed in "Device Manager" as Kindle Fire, it says Android Phone>Android Composite ADB Interface.
Could someone please help me with getting root and Android Market?
I'm in the KindleFire IRC chat, but no one is talking/responding.

i assume you'r talking about kfu 0.9.4
it's a good practice to extract/move it to c:\ and rename it to "kfu" to that it is c:\kfu
have you used the kfu drivers ?
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

b63 said:
i assume you'r talking about kfu 0.9.4
it's a good practice to extract/move it to c:\ and rename it to "kfu" to that it is c:\kfu
have you used the kfu drivers ?
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Click to expand...
Click to collapse
Like I mentioned I ran the install_driver.bat file that is downloaded with KFU.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And KFU will not see it.

is it booted normally ?
then the driver should be "android composite adb interface"
is the kf doing something ? rebooting ?

GooglePlay and Go launcher wont install
When trying to run extras, GApps and Go launcher the utility just closes. I can't install Google Play manually either, even though I have mounted the permissions and the device is rooted. I've also tried the SuperUser app. ES File explorer wouldn't root the system/apps folder. GooglePlay will install but closes out when trying to setup the account. I'm using the latest utility, .9.4, and I have version 6.3 on the kindle. It took me a while to get the drivers to work right, and the root, but I did finally get it. By a while I mean 5 frustrating hours, but its the only way to learn. However my whole purpose for doing this was for the google play store. Any ideas? I will also donate for help. This is an awesome utility. Great job!

You are going to have to do a little more work to get the market to work. Do a search in the development section. There is a thread for that. I think you have to get the vending apk move it to the system/app folder and then reboot and then install it from that folder. A lot of apps require that method use the search function to find info on apps you are having a hard time with.

I am having the exact same issue. The device boots normally. It jsut isn;t recognized by ADB.
KoolAidJunkie said:
Like I mentioned I ran the install_driver.bat file that is downloaded with KFU.
And KFU will not see it.
Click to expand...
Click to collapse

Well done ,learn more

neffarious said:
I am having the exact same issue. The device boots normally. It jsut isn;t recognized by ADB.
Click to expand...
Click to collapse
I removed the drivers and readded them and all was well.
---------- Post added at 04:36 PM ---------- Previous post was at 04:36 PM ----------
leilanifxo said:
Well done ,learn more
Click to expand...
Click to collapse
You do realize this makes no sense in any context...

[INFO/steps] Cydia Impactor Root (easy root method/confirmed working on R800X)

(MODS - Please Close this thread)
Hi Everyone,
The Cydia Impactor root method (discussed in this thread) appears to be a really easy and quick way to root our Xperia Play phones. I have searched the Xperia Play threads and couldn't find any other posts discussing this root method for our phones, so I'm starting this thread to share information about it with my fellow Xperia Play users. (Since I can only test it on the R800x, it would be great if others could test it to confirm that it works for other versions of the Xperia Play...but I believe it should. I have 2 Xperia Play phones (one with a locked and one with unlocked bootloader. I tested this method on both phones running 2.3.3 & 2.3.4 Gingerbread and it worked as expected in each test).
:good:
CREDITS:
I take no credit for this root method. All credit and thanks should go to saurik for creating the Cydia Impactor, and to Chainfire for SuperSU. Also, thank you to karandpr for starting the other Xperia thread, where I first learned about this method. (If I've forgotten anyone, please PM me and I'll add you).
DISCLAIMER:
If you choose to download and install any of the linked files to your computer or phone, then you are choosing to take full responsibility for any risks or potential consequences that come with rooting and tinkering with your phone. Neither I, nor anyone else in the linked threads will be liable for anything that you choose to do with your phone or computer. Please don't proceed with this root method if you don't agree.
Prerequisites: For the below method to work, you must have the Xperia Play drivers installed on your computer to allow your phone and computer to communicate with each other.
~~~~~~~~~~~~~~~~~~~~~~~~
STEPS:
1. Download the Cydia Impactor zip file: (FOUND HERE) to your computer and unzip it. (On my computer, I created a folder called "Cydia Impactor Root Method," and then used 7zip to unzip it into that folder).
2. Enable USB debugging on your phone and connect the phone to your computer with a USB cable
3. On your computer, navigate to where you unzipped the contents of the Impactor zip file. Right click on the Impactor application and open it with Administrator rights.
4. Click Start and let the root exploit do its thing.
5. On your phone, go to the Google Play Store and install Chainfire's SuperSU (Link), then open SuperSU and update the SU binary. (I chose the "Normal" option to update the SU binary and it worked).
That's it! Your phone should now be rooted with SuperSU installed. This worked great for me and I'm hoping that others will find this information helpful.
PS: This root method doesn't install Busybox, so you'll need to do that if you plan to stay stock rooted. Here's a good app to help you install it if you're not familiar with Busybox: Link
---------------------------------
---------------------------------
Sreenshot of the Cydia Impactor program after opening it on the computer:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshot after Cydia Impactor rooted the phone & placed SU binary into system/xbin:
Screenshot of SuperSU asking if you want to update binary with "Normal" or Custom Recovery method:
Screenshot of SuperSU confirming successful installation of SU binary update:

reply
i cant do it in my mob the computer said no device founed

davi.beckham said:
i cant do it in my mob the computer said no device founed
Click to expand...
Click to collapse
I am assuming that you have not installed the Xperia Play drivers onto your computer to let your phone and computer communicate properly. I apologize, but I guess that I assumed people would have known to have done that before trying the above root method. I will update the original post to include these additional steps.
There are numerous ways to install the drivers on your computer, but installing Sony's PC Companion from this link: ( http://support.sonymobile.com/us/tools/pc-companion/ ) will probably be easiest if you are totally new with this stuff. PC Companion takes up a lot of space on the computer's hard drive--so it's not my first choice, but it is a very easy way to get the proper drivers installed.
1. just install the PC Companion on your computer, then enable USB Debugging on your phone by going into Settings/Applications /Development/ then Enable USB Debugging. (I don't think it's necessary... but you might also want to enable Unknown Sources too).
2. Connect your phone with your computer with the USB data transfer cable and this should let your Windows computer install the correct drivers automatically. (You might want to reboot the computer after installing the drivers, but probably not necessary).
After doing these 2 additional steps, retry the rest of the steps in the above rooting method and I believe that it should work.

Thread closed at OPs request

[ROOT][SuperSU] I8200N Working!

I'M NOT RESPONSIBLE IF ANTHING GOES WRONG USING THIS METHOD!!! IT'S ONLY ONE THAT WORKED FOR ME, SO I'M JUST SHARING IT FROM MY EXPERIENCE! USE AT YOUR OWN RISK!!!
Hi everyone!
So, i was looking for root my new I8200N. Only way to do it is with VRoot/iRoot chinese application, but it installs Kinguser instead of SuperSu or Superuser. In my experience it's like half root coz many apps doesn't fully work with it. I tried everything i could find but nothing worked. I finally found solution so if you have troubles, here we go:
All requirements in attachment, just unrar it!
1. Install SAMSUNG USB Drivers (Recommended reboot!)
2. On AD (Android Device) go to | Settings > More > About | then press about 10 times on version number to unlock developer features. See at screenshot.
Then go back and enter developer settings. Check USB debugging, OK.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Connect your AD with USB to PC and finish driver installation if needed in Device Manager.
4. Install VRoot and open it
Between this two, mobile will ask something with long address. Just check remember for this PC or something like that and Allow/OK.. And for white windows, go to Deny or something like that. It's something about Google Play...
On PC press "Root" when becomes available.
Just wait a minute and phone will reboot and it should be rooted. It should be like this:
Optional: You can delete chinese apps that comes installed, you just need "Kinguser".
5. Settings > More > Security | check "Unknown Sources" and OK.
6. Copy Lucky Patcher to AD and install it. Open it and when Kinguser ask for permission, go to Allow. Update if available.
7. In Lucky Patcher go to | Toolbox > Patch to Android > Check:
- Signature Verification status always True
- Disable .apk Signature Verification
- Disable Signature verification in the package manager
Apply
AD will reboot, if not then reboot after it finished.
8. Copy "kinguser.apk" from attachment to AD and install it. Open it and when asks you for update, CANCEL it!
9. Unrar "mrw" from attachment and whole folder copy to AD. I found easier paste it in device than SDcard coz of address we'll gonna need later.
10. Install Terminal from Google Play. https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
11. Open Terminal, type "su" (without quotes) and press enter. When promted for root access, Authorize/Allow it.
12. Now type "sh /storage/emulated/0/mrw/root.sh" (Without quotes). I pasted mrw folder in root of AD, so address is like that one in quotes. You can put it somewhere else, just type correct address. Then press enter. If any error or something comes up, just go for OK or what ever you got and don't worry it's normal. After few seconds, you will be promted for root access from SuperSU, Allow it!
Phone will reboot. Update SuperSU binary and app if needed.
Congratz! You are rooted with SuperSU!
I successfully rooted 2 devices with this method.
Happy rooting!

Just to highlight issues with this, vroot will install apps on your pc without you knowing even after uninstalling.
Also you can completely remove kingroot and replace with supersu by using another mod found on this forum.
You will need an app to mount system as read writable on boot. See the playstore.
Sent from a stolen phone!

That was the only way i could found that really works for me. Days i've been searching for root and this is only i could get working.

kingroot infected?

Hello all,
I recently started to get lots of popads on my device, so I ran my usual scan with Malwarebytes and it came up with KingRoot being heavily infected with malware. I cant uninstall, since its what i used to root and its also a system app. Any help?

loganwaffle8 said:
Hello all,
I recently started to get lots of popads on my device, so I ran my usual scan with Malwarebytes and it came up with KingRoot being heavily infected with malware. I cant uninstall, since its what i used to root and its also a system app. Any help?
Click to expand...
Click to collapse
see rootjunky's supersume video
https://www.youtube.com/watch?v=3O3DcpeS_Ic
or manually install supersu with a terminal emulator
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html

Ill try the rootjunky method in a few hours, I tried the terminal emulator installed and it just forceclosed all apps and rebooted.
Sent from my KFTBWI using XDA Labs

So I got a bit impatient, and decided to retry the w0lfdroid method. The same thing happened from last time (apps wouldnt open) and so I decided to reboot.
As the device began to shutdown, SuperSU appeared for a few seconds, then my device switched off. I believe I have bricked my device as it has been stuck on the 'fire' logo for the past 10 minutes. Congrats to me ._.

I tried to install adb and its drivers, however drivers wouldnt install saying 'windows couldnt find any driver software for you device' when i point it to the drivers. Any idea why?

loganwaffle8 said:
I tried to install adb and its drivers, however drivers wouldnt install saying 'windows couldnt find any driver software for you device' when i point it to the drivers. Any idea why?
Click to expand...
Click to collapse
Download kindle_fire_usb_driver.zip from Amazon site
Connecting Your Fire Tablet for Testing or XDA
extract files
run KindleDrivers.exe
Then manually select drivers
Open device manager Settings>Devices>Device Manager
Connect Kindle Fire
Enable USB debugging
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface for Stock rom or recovery/adb sideload
Select Android ADB interface for Fastboot mode
or Android Composite ADB interface
next
you may have to reboot pc
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my KFFOWI using XDA Labs

Thanks
Have I done it right? I hope I've done everything. Also when I open ADB a load of text flashes down the cmd box for about a second then it closes. Ran as administrator and everything. Hoping I can get this fixed by the weekend...

Ok, I think I got it.
Doing adb devices gives me G000HH0454340LB9, I beleive this is the correct device?
Anyways, plan is:
Boot into recovery on device and select apply update from adb
Get the 5.1.1 update (firmware it originally had) and place it in the folder adb installed in.
Do adb sideload (file name)
Wait (maybe grab a cup of coffee?)
Hopefully success, back to stock firmware!
Afterwards ill root with kingroot and then remove using rootjunky supertool.

Ok, this is getting kinda annoying.
Placed the update-kindle-32.5.4.1_user_541112720 .bin file in the same folder I have adb installed.
Booted devices into recovery mode, selected apply update from adb
Open adb, do adb sideload update-kindle-32.5.4.1_user_541112720
Get error message 'cannot read update-kindle-32.5.4.1_user_541112720'
Have ALL correct drivers and stuff installed @sd_shadow

Can anyone help? I really need this fixing...

loganwaffle8 said:
Can anyone help? I really need this fixing...
Click to expand...
Click to collapse
try downloading the firmware again, or try a different version like 5.1.2
which version is on it now?
Sent from my KFFOWI using XDA Labs

The version on my device before it was bricked is 5.1.1. I'm staying on that version since its the easiest to root.