Related
I try to root my kindle fire but it says waiting on device
Does anyone know how to fix it?
justin111 said:
I downloaded KFU but it won't installed driver and I have tried older versions and it sayes
(Waiting on device)
Can Someone help me? Please
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2179748
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2179748
Click to expand...
Click to collapse
That help with the drivers but still doesn't recognize device ( waiting on device )
justin111 said:
That help with the drivers but still doesn't recognize device ( waiting on device )
Click to expand...
Click to collapse
Just for the hell of it...try an ADB command. If you don't get a response turn the device off, and close KFU.
Shift + Right-click on the KFU tools folder and select Open command window here.
Enter the following and turn the device on:
Code:
fastboot -i 0x1949 getvar product
justin111 said:
I try to root my kindle fire but it says waiting on device
Does anyone know how to fix it?
Click to expand...
Click to collapse
Are you sure it is a KF1? KF2 is not recognized.
Sent from a bird... No, a plane... Wait, It's a Kindle Fire!
Vlasp said:
Are you sure it is a KF1? KF2 is not recognized.
Sent from a bird... No, a plane... Wait, It's a Kindle Fire!
Click to expand...
Click to collapse
Yes it is a KF1
soupmagnet said:
Just for the hell of it...try an ADB command. If you don't get a response turn the device off, and close KFU.
Shift + Right-click on the KFU tools folder and select Open command window here.
Enter the following and turn the device on:
Code:
fastboot -i 0x1949 getvar product
Click to expand...
Click to collapse
I am not familiar with ADB
soupmagnet said:
Just for the hell of it...try an ADB command. If you don't get a response turn the device off, and close KFU.
Shift + Right-click on the KFU tools folder and select Open command window here.
Enter the following and turn the device on:
Code:
fastboot -i 0x1949 getvar product
Click to expand...
Click to collapse
I tried the shift+ right click but all it says is open in onenote or scan it not open command window
justin111 said:
I tried the shift+ right click but all it says is open in onenote or scan it not open command window
Click to expand...
Click to collapse
okay, then type: cd<space> and drag that folder to the terminal window.
The point is to run the adb commands from the directory the executable is in.
soupmagnet said:
okay, then type: cd<space> and drag that folder to the terminal window.
The point is to run the adb commands from the directory the executable is in.
Click to expand...
Click to collapse
Where do I type that and what is the terminal window.
justin111 said:
Where do I type that and what is the terminal window. I sorry I'm a noob.
Click to expand...
Click to collapse
Command prompt.
justin111 said:
Where do I type that and what is the terminal window. I sorry I'm a noob.
Click to expand...
Click to collapse
Open the start menu and type in cmd, then hit enter. That is the command line, aka the terminal window.
Sent from my Amazon Kindle Fire using Tapatalk HD
jma9454 said:
Open the start menu and type in cmd, then hit enter. That is the command line, aka the terminal window.
Sent from my Amazon Kindle Fire using Tapatalk HD
Click to expand...
Click to collapse
Does this work on windows xp or not
justin111 said:
Does this work on windows xp or not
Click to expand...
Click to collapse
Command prompt does, I don't know if you can access it like I said above.
Sent from my Amazon Kindle Fire using Tapatalk HD
What do I type in cmd?
justin111 said:
What do I type in cmd?
Click to expand...
Click to collapse
Code:
adb devices
or
Code:
fastboot -i 0x1949 getvar product
Make sure your Kindle doesn't show up in the device manager with an exclamation point. If it does, manually reinstall the 'android_winusb.inf'.
If neither of the commands work, and your device doesn't show up in the device manager with an exclamation point next to it, pull the hardware ID of the device as it's shown in the device manager and post it here.
What is cmd supposed to look like?
Am supposed to have my kindle fire pluged in during this process?
justin111 said:
What is cmd supposed to look like?
Click to expand...
Click to collapse
justin111 said:
Am supposed to have my kindle fire pluged in during this process?
Click to expand...
Click to collapse
yes, have your kindle plugged in.
here's a pic of the Command Prompt.
justin111 said:
Where do I type that and what is the terminal window.
Click to expand...
Click to collapse
If you don't know this information, I'd read/research a lot more before attempting to hack your kindle fire.
The terminal window is also known as the dos command prompt and can be accessed from the start menu in the following way:
windows menu->all programs->accessories->command prompt (on windows 7)
Since you do not want a paper weight instead of a useful device please read more and get familiar with windows development. If you get stuck we probably can help, but we do need you to be willing to learn and do some work on your own...
The primary problem people run into with KFU is a device driver issue, you will want to understand windows device drivers and then start learning how to get ADB working with your device first. Once you can do this KFU is a great tool at automating several simple tasks.
Good Luck!
EDIT:
Wow, I must not have noticed a second page was on this thread... I apologize for repeating information that you guys already posted...
Hi xda! And fellow users especially those experts. I just want to know where to find log files of our own note 2? Thanks in advance!
Sent from my GT-N7100 using XDA Premium 4 mobile app
Hi!
The following method will provide you the best log you can get to see your errors.
1. Make sure that you have the phone's drivers installed on the PC.
2. Install Android SDK to get ADB. Any other tool or ADB installation will work as long as you get ADB on your device. The ADB shell is the debug shell and will allow you to get your log (logcat). To get ADB on your machine, install the Java JDK first, then get the Android SDK and install it.
3. Once you have the Android SDK installed, make sure that the Developer mode is enabled on your phone. If you don't see any Developer options section in your Settings menu, go to About device and tap the Build number untill the phone tells you that the Developer options are enabled.
4. Now, in Developer options, make sure that the USB debugging option under Debugging is enabled.
5. Plug in your phone.
6. On the PC, navigate to the installation folder of the Android SDK (usually in the Program Files/Program Files (x86) folder. Go to Android\android-sdk\platform-tools. In the platform-tools folder you should see the ADB.exe. Don't open it, but press Shift + Right Click inside that folder and select Open command windo here.
7. Check to see if your device is seen by ADB: in the CMD window, enter the following command: adb devices. Your device should be listed in the CMD.
8. TO GET THE LOGCAT type the following command: adb logcat. Alternatively, you can use the option -f <filename> to save the log to a file (adb logcat -f log).
I hope this helps!
Ruwin said:
Hi!
The following method will provide you the best log you can get to see your errors.
1. Make sure that you have the phone's drivers installed on the PC.
2. Install Android SDK to get ADB. Any other tool or ADB installation will work as long as you get ADB on your device. The ADB shell is the debug shell and will allow you to get your log (logcat). To get ADB on your machine, install the Java JDK first, then get the Android SDK and install it.
3. Once you have the Android SDK installed, make sure that the Developer mode is enabled on your phone. If you don't see any Developer options section in your Settings menu, go to About device and tap the Build number untill the phone tells you that the Developer options are enabled.
4. Now, in Developer options, make sure that the USB debugging option under Debugging is enabled.
5. Plug in your phone.
6. On the PC, navigate to the installation folder of the Android SDK (usually in the Program Files/Program Files (x86) folder. Go to Android\android-sdk\platform-tools. In the platform-tools folder you should see the ADB.exe. Don't open it, but press Shift + Right Click inside that folder and select Open command windo here.
7. Check to see if your device is seen by ADB: in the CMD window, enter the following command: adb devices. Your device should be listed in the CMD.
8. TO GET THE LOGCAT type the following command: adb logcat. Alternatively, you can use the option -f <filename> to save the log to a file (adb logcat -f log).
I hope this helps!
Click to expand...
Click to collapse
This what I'm looking for mate! Thanks! Will try this later. Thanks for the effort! *thanks button*
Sent from my GT-N7100 using XDA Premium 4 mobile app
That's why whe're all here for.
Keep it real!
Hi,
Not sure if this is the right place (but only place I can post) I've been trying to root my phone in order to install TWRP on my Pixel XL, in order to do so I need to unlock my bootloader.
Now this won't work as in ADB it shows my device as unauthorised, and I've tried everything! Revoking permissions USB debugging, rebooting, the other solution involces deleteing the adb key in .android, but my only .android folder is under c:\\users\MyName\.android and has no adbkey here, only 3 folders -> avd, cache and studio, all of these being empty!
I'm at a real loss to authorise my device so I can continue to root my device.
Any help would be appreciated.
Kind regards
MunkeyBoy14 said:
Hi,
Not sure if this is the right place (but only place I can post) I've been trying to root my phone in order to install TWRP on my Pixel XL, in order to do so I need to unlock my bootloader.
Now this won't work as in ADB it shows my device as unauthorised, and I've tried everything! Revoking permissions USB debugging, rebooting, the other solution involces deleteing the adb key in .android, but my only .android folder is under c:\\users\MyName\.android and has no adbkey here, only 3 folders -> avd, cache and studio, all of these being empty!
I'm at a real loss to authorise my device so I can continue to root my device.
Any help would be appreciated.
Kind regards
Click to expand...
Click to collapse
Have tried to delete the whole .android folder ? and do you have the latest adb / fastboot files. but to unlock your bootloader you actualy dont need adb just fastboot ?
After revoking permissions did you kill and restart the adb server:
adb kill-server
adb start-server
Sent from my Pixel XL using Tapatalk
ahent said:
After revoking permissions did you kill and restart the adb server:
adb kill-server
adb start-server
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yes I did, and nothing changed.
Hogyoku said:
Have tried to delete the whole .android folder ? and do you have the latest adb / fastboot files. but to unlock your bootloader you actualy dont need adb just fastboot ?
Click to expand...
Click to collapse
I used the adb installer by Snoop05 and using that installed latest drivers too! I shall delete the folder and see what happens I guess?
MunkeyBoy14 said:
I used the adb installer by Snoop05 and using that installed latest drivers too! I shall delete the folder and see what happens I guess?
Click to expand...
Click to collapse
Not sure if the link will work but try these this is straight from Google
https://plus.google.com/+YamaniMondt/posts/AjgC41SYT9h
When I run the "adb shell" commad I get the following:
C:\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Not sure if this helps at all
Hogyoku said:
Not sure if the link will work but try these this is straight from Google
https://plus.google.com/+YamaniMondt/posts/AjgC41SYT9h
Click to expand...
Click to collapse
Thank you so much! Running adb using the attached link caused me to get the pop up to approve the RSA. And is now showing as authorised. THank you!
MunkeyBoy14 said:
Thank you so much! Running adb using the attached link caused me to get the pop up to approve the RSA. And is now showing as authorised. THank you!
Click to expand...
Click to collapse
No problem
i want to enter diagnostic mode in LOS14.1, i use command:
setprop sys.usb.config diag,adb
but it didn't work, pls help me,thk
kirtikhurana said:
Use this
Click to expand...
Click to collapse
i have try,but nothing change
kirtikhurana said:
you should be rooted unless it won't work.
Click to expand...
Click to collapse
i rooted,but these command work for lenovo offical rom,such as 048,062,232,244,251,not on los,any suggestion?
kirtikhurana said:
before that command i told. write the two.
adb shell
su
then diag commands.
during these commands your phone will prompt to grant permissions. Tap OK/Yes on phone
*remember to check Android bebugging Is ON in developer settings.
Even if you're unsuccessful you're probably doing wrong.
Click to expand...
Click to collapse
bro,setprop should be root,i know it,i use successful in lenovo offical rom, i told you,my question is: why not work for los,can you check it?
Android 9 added a new feature which allows for the temporary rotation of the screen, with the press of a button would appear when the phone is put into landscape orientation. MIUI for some reason has decided to exclude it, we're at Android 11 and it still doesn't have it. I was wondering if Xiaomi.EU ROM has this feature, or would I have to go with a custom ROM?
do you use tasker? could try the auto-rotate for chosen apps profile found in this thread.
i used it fine for both ROG phone II and this Alioth phone. i just set it for maps, youtube vanced etc.
works great. not sure i'd recommend the other profiles, they may well be device specific
reg66 said:
do you use tasker? could try the auto-rotate for chosen apps profile found in this thread.
i used it fine for both ROG phone II and this Alioth phone. i just set it for maps, youtube vanced etc.
works great. not sure i'd recommend the other profiles, they may well be device specific
Click to expand...
Click to collapse
Cool, this could be a workaround for my issue, just enabling rotation in some apps. I'll try it out, thanks!
It might be a late reply, but in terminal emulator as root you can type this command: "settings put secure show_rotation_suggestions 1" without the quotes and it will enable rotation suggestions when you rotate the screen. You can also use this same command in FKM scripts section and set it to run on boot. If you're not rooted then you must use adb shell on a PC with adb debugging enabled in developer options and use this command: " pm shell settings put secure show_rotation_suggestions 1" without the quotes. After a reboot the setting is disabled again so you have to run the command after each reboot.
pawelmiernik said:
It might be a late reply, but in terminal emulator as root you can type this command: "settings put secure show_rotation_suggestions 1" without the quotes and it will enable rotation suggestions when you rotate the screen. You can also use this same command in FKM scripts section and set it to run on boot. If you're not rooted then you must use adb shell on a PC with adb debugging enabled in developer options and use this command: " pm shell settings put secure show_rotation_suggestions 1" without the quotes. After a reboot the setting is disabled again so you have to run the command after each reboot.
Click to expand...
Click to collapse
THANK YOU SO MUCH! This has always been one of the reasons I hated MIUI, now I finally get to enjoy this feature that MIUI has chosen to hide for some reason!
CharlieMHz said:
THANK YOU SO MUCH! This has always been one of the reasons I hated MIUI, now I finally get to enjoy this feature that MIUI has chosen to hide for some reason!
Click to expand...
Click to collapse
Ikr it's such a useful thing to have!
@pawelmiernik I just registered to say that you are a frigging legend, thank you so much!
Absolutely idiotic that they left out this option somewhere in the settings. Especially when you can reactivate the already implemented button with such a workaround. Ridiculous.
pawelmiernik said:
It might be a late reply, but in terminal emulator as root you can type this command: "settings put secure show_rotation_suggestions 1" without the quotes and it will enable rotation suggestions when you rotate the screen. You can also use this same command in FKM scripts section and set it to run on boot. If you're not rooted then you must use adb shell on a PC with adb debugging enabled in developer options and use this command: " pm shell settings put secure show_rotation_suggestions 1" without the quotes. After a reboot the setting is disabled again so you have to run the command after each reboot.
Click to expand...
Click to collapse
Thanks for this, would like to add that another way of having it persist is to use SetEdit and add show_rotation_suggestions 1 to the secure table. You'll need to give the SetEdit app permissions to write to the secure table. You can do it with root but if you're not rooted you can use adb, just be sure to enable "usb debugging (security settings)" as well.
pawelmiernik said:
It might be a late reply, but in terminal emulator as root you can type this command: "settings put secure show_rotation_suggestions 1" without the quotes and it will enable rotation suggestions when you rotate the screen. You can also use this same command in FKM scripts section and set it to run on boot. If you're not rooted then you must use adb shell on a PC with adb debugging enabled in developer options and use this command: " pm shell settings put secure show_rotation_suggestions 1" without the quotes. After a reboot the setting is disabled again so you have to run the command after each reboot.
Click to expand...
Click to collapse
Just to add on to this, for me, the settings stayed even after a restart, so I didn't need to run it again after reboot.
I think it's because they added this to MIUI 13. I recently bought a POCO F3 and it had it built in. Finally. There is hope in this world.
Weslington9 said:
I think it's because they added this to MIUI 13. I recently bought a POCO F3 and it had it built in. Finally. There is hope in this world.
Click to expand...
Click to collapse
How to turn on this feature, I am on miui13 but can't find it ?