Related
Hi, I have a kindle fire 2nd Gen that I am trying to root. when I run the steps in the easy root thread, I also tried using the new adb driver they posted in the developement thread that was supposed to "Fix" the faulty adb driver. well my computer recognizes my kindle, and when I try to open my cmd, type in the steps for root, I get a message that says ( I screenshotted it as a jpg. and my computer finds my kindle as a android usb composite device.I have adb and the unknown sources turned on for my kindle. Just please help because I really wanna get it rooted. I even tried to reset windows 7 back to factory. My kindle is running 10.2.6. but as I was saying, if I run the Qemu Method and type adb devices, it still won't show up. PLEASE HELP ME!
dagriff1997 said:
Hi, I have a kindle fire 2nd Gen that I am trying to root. when I run the steps in the easy root thread, I also tried using the new adb driver they posted in the developement thread that was supposed to "Fix" the faulty adb driver. well my computer recognizes my kindle, and when I try to open my cmd, type in the steps for root, I get a message that says ( I screenshotted it as a jpg. and my computer finds my kindle as a android usb composite device.I have adb and the unknown sources turned on for my kindle. Just please help because I really wanna get it rooted. I even tried to reset windows 7 back to factory. My kindle is running 10.2.6. but as I was saying, if I run the Qemu Method and type adb devices, it still won't show up. PLEASE HELP ME!
Click to expand...
Click to collapse
this http://forum.xda-developers.com/showthread.php?t=2041138 ha work for me.
Hey Guys,
as the title says, I can't connect to my OUYA anymore.
What have I done?
Set up adb and sdk descripted here
https://devs.ouya.tv/developers/docs/setup
Set up wireless adb, busybox, superuser, and su binaries descripted here
http://forum.xda-developers.com/showthread.php?t=2272266
Everything worked fine so far.
Then I rebooted the OUYA. From now on the device manager didn't found the OUYA anymore. If I switch USB-debugging off, its found as 'portable device'. If I switch USB-debugging on, it disappears and there is no other new item.
OUYA factory reset
This didn't helped anything. But with this step I lost SU.
So, as i read, USB-ADB is shut down on OUYA as soon as you enable wireless-ADB. A terrible 'feature', whatever. Now I can't modify the build.prop to take out the "service.adb.tcp.port=5555" line.
I managed to get into the recovery mode (by connecting a keyboard and pressing alt+print+i multiple times, then home) , but that's pretty helpless if adb can't find the ouya.
Has anybody an idea how I can get adb working properly again? Any ways are good, flashing a new rom, getting su, factory reset, anything =D
JackBackstack said:
Hey Guys,
as the title says, I can't connect to my OUYA anymore.
What have I done?
Set up adb and sdk descripted here
https://devs.ouya.tv/developers/docs/setup
Set up wireless adb, busybox, superuser, and su binaries descripted here
http://forum.xda-developers.com/showthread.php?t=2272266
Everything worked fine so far.
Then I rebooted the OUYA. From now on the device manager didn't found the OUYA anymore. If I switch USB-debugging off, its found as 'portable device'. If I switch USB-debugging on, it disappears and there is no other new item.
OUYA factory reset
This didn't helped anything. But with this step I lost SU.
So, as i read, USB-ADB is shut down on OUYA as soon as you enable wireless-ADB. A terrible 'feature', whatever. Now I can't modify the build.prop to take out the "service.adb.tcp.port=5555" line.
I managed to get into the recovery mode (by connecting a keyboard and pressing alt+print+i multiple times, then home) , but that's pretty helpless if adb can't find the ouya.
Has anybody an idea how I can get adb working properly again? Any ways are good, flashing a new rom, getting su, factory reset, anything =D
Click to expand...
Click to collapse
If you can get into recovery, just copy over the latest OTA file onto a usb stick, wipe Data/cache then flash the OTA.
Also for windows, not doing " echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini" " can sometimes make it not be found on its own, was originally required to do it for ADB
In recovery mode, the only way is to flash the OTA via ADB. There is no option like from usb-stick or internal/external sd-card.
and my adb_usb.ini seems to be correct.
But thanks for your suggestions (=
I had the same issues. I'm waiting on a replacement. http://forums.ouya.tv/discussion/comment/13562
JackBackstack said:
Hey Guys,
as the title says, I can't connect to my OUYA anymore.
What have I done?
Set up adb and sdk descripted here
https://devs.ouya.tv/developers/docs/setup
Set up wireless adb, busybox, superuser, and su binaries descripted here
http://forum.xda-developers.com/showthread.php?t=2272266
Everything worked fine so far.
Then I rebooted the OUYA. From now on the device manager didn't found the OUYA anymore. If I switch USB-debugging off, its found as 'portable device'. If I switch USB-debugging on, it disappears and there is no other new item.
OUYA factory reset
This didn't helped anything. But with this step I lost SU.
So, as i read, USB-ADB is shut down on OUYA as soon as you enable wireless-ADB. A terrible 'feature', whatever. Now I can't modify the build.prop to take out the "service.adb.tcp.port=5555" line.
I managed to get into the recovery mode (by connecting a keyboard and pressing alt+print+i multiple times, then home) , but that's pretty helpless if adb can't find the ouya.
Has anybody an idea how I can get adb working properly again? Any ways are good, flashing a new rom, getting su, factory reset, anything =D
Click to expand...
Click to collapse
I haven't messed with root/cwm, since there really isn't much brick protection... you might try 'adb reboot recovery' during bootup... if you can force it to fastboot, you can boot the recovery image, and it should have adb with su access, you should be able to repair you mistakes from there, or just do a data/cache reset to wipe the device.
EDIT: assuming you can get to fastboot somehow, you would just have to 'fastboot boot recovery.img' where recovery.img is the build of cwm.
EDIT 2: try booting with a usb keyboard, during boot, you might be able to spam the kernel with the key combination alt-SysRq-i. This may force it to boot into recovery... Then you should be able to either use regular ADB, maybe push a OTA.zip via ADB, and ultimately install a OTA... Hope some of this is helping, I have no real hands on practice with much of ADB on this specific device... But I'm a LONG time android tinkerer.
EDIT 3: If you're able to get it to crash and boot into recovery via Alt-SysRq-i . It's a recovery based on 4.x as it should be... and you should be able to 'adb sideload OTA.zip'... Sorry for all these edits, I just keep realizing I have more to say.
Here's the link for the apk(down page a bit) to enable disable wireless adb allowing USB adb:
http://forum.xda-developers.com/showthread.php?t=961466
Sent from my Galaxy Nexus using xda app-developers app
HaYNigloo said:
Here's the link for the apk(down page a bit) to enable disable wireless adb allowing USB adb:
http://forum.xda-developers.com/showthread.php?t=961466
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Will that require root?
Yes, since it's right inline with installing su, busybox, and supersuer using ADB. With the option to go ADB wireless, this is a necessity if you'll be installing CWM.
HaYNigloo said:
Yes, since it's right inline with installing su, busybox, and supersuer using ADB. With the option to go ADB wireless, this is a necessity if you'll be installing CWM.
Click to expand...
Click to collapse
Yeah that's what sucks. I followed a post on here and thought I had the unit rooted but either I messed it up or the OTA updates wiped it out. Since I no longer have adb access I cannot get root to enable wireless adb access. Snake eating its own tale
Oh! I believe there are wireless adb apps that don't require root. Try looking into the play store to find out which ones.
Edit 1: The Play Store has a wireless ADB app by Sherdle [ADB Wireless (no-root)]which doesn't require root!
Sent from my Galaxy Nexus using xda app-developers app
Hi everyone,
Actually I'm stuck the exact same way and I'm wondering if beowolfschaefer and JackBackstack have found a solution to get ADB work over TCPIP.
Thanks guys.
KrelianGS said:
Hi everyone,
Actually I'm stuck the exact same way and I'm wondering if beowolfschaefer and JackBackstack have found a solution to get ADB work over TCPIP.
Thanks guys.
Click to expand...
Click to collapse
I'm missing something. I have read this a couple times but cant figure out what is happening.
Is your Ouya not booting up at all?
If it boots can you do an
adb connect xxx.xxx.xxx.xxx and then adb shell to get a shell?
HT123 said:
I'm missing something. I have read this a couple times but cant figure out what is happening.
Is your Ouya not booting up at all?
If it boots can you do an
adb connect xxx.xxx.xxx.xxx and then adb shell to get a shell?
Click to expand...
Click to collapse
The Ouya is booting perfectly and wifi-ADB is enable. Problem is I can't connect to it anymore.
I already tried adb connect 192.168.xxx.xxx but i get a "device not found" error. It's the good IP (check on the Ouya and on my router with the MAC Adress)
It might be a port probleme. I tried both 5037(default) and 5555.
By the way, in the settings, should I switch USB-Debugging on or off ? Or it doesn't matter ?
KrelianGS said:
The Ouya is booting perfectly and wifi-ADB is enable. Problem is I can't connect to it anymore.
I already tried adb connect 192.168.xxx.xxx but i get a "device not found" error. It's the good IP (check on the Ouya and on my router with the MAC Adress)
It might be a port probleme. I tried both 5037(default) and 5555.
By the way, in the settings, should I switch USB-Debugging on or off ? Or it doesn't matter ?
Click to expand...
Click to collapse
I am pretty sure USB debugging needs to be on for ADB to accept connections. make sure it is on
Hi there, I've recently tried rooting my lgg3 but im running into a few problems.
Just to clarify:
I've installed the drivers
Enabled USB de-bugging
Used task manager to end abd.
Tried MTP and PTP
But when ever I run the Oneclick root, it failes to start abd, then fails daemon, and then 'successfully' starts demon only to fail it again. It does this about 3 times before re-booting the phone into download mode.
From there, it asks me to wait for SuperSU to install, which it never does.
I'm really stuck here and could use any help. I've also tried using the GUI and .bat rooting tools, the .bat gets further into it than the actual, updated GUI, rebooting the phone, whereas the gui fails at the start as it cant start abd nor daemon.
For starters, please update with:
Your variant (model number)
Current Android software version
Which one-click root tool you are trying to use
The output from 'adb devices' entered into ADB
Looks like I bricked my fireTV Stick today.
What i did: After i updated to 5.2.1.0 I rooted with Kingo Root. I checked if everything was still running fine, which was the case.
Then i removed Kingo Root App and the superuser app that came with Kingo Root. I installed Chainfires latest supersu.apk which did not work (immediately crashed after start). Then i downloaded older version v1.97 of chainfires supersu. This version did not crash directly after starting it. It asked to update the su binary, which I accepted. Unfortunately it did not seem to work, that's why i rebooted the stick after some minutes.
Now it stucks at the "fireTV stick" logo.
Connection to adb works if i connect the Stick to my PC.
Is there anything i can try? Is there a way to factory reset via adb or anything like that?
Bierfreund said:
Looks like I bricked my fireTV Stick today.
What i did: After i updated to 5.2.1.0 I rooted with Kingo Root. I checked if everything was still running fine, which was the case.
Then i removed Kingo Root App and the superuser app that came with Kingo Root. I installed Chainfires latest supersu.apk which did not work (immediately crashed after start). Then i downloaded older version v1.97 of chainfires supersu. This version did not crash directly after starting it. It asked to update the su binary, which I accepted. Unfortunately it did not seem to work, that's why i rebooted the stick after some minutes.
Now it stucks at the "fireTV stick" logo.
Connection to adb works if i connect the Stick to my PC.
Is there anything i can try? Is there a way to factory reset via adb or anything like that?
Click to expand...
Click to collapse
Connect your fire stick to a windows pc/laptop. (i used windows 10 64bit)
Let the drivers install.
Download the windows version of Kingo root.
Click root, try this a couple of times (it probably will fail and stick at 70 percent)
unplug the stick and try again, when it hits 70 percent again plug your hdmi lead in (already connected to tv)
It should root and write back the correct su files.
If you want to unroot, install kingo and super user again on the fire stick then either use the unroot feature in super user app (you will have to purchase mouse toggle for fire tv, if you havent got it already to navigate to the 3 little dots menu icon top right corner)
Or re plug it into windows pc/laptop and unroot through the windows tool.
Worked! Did not know, that there's also an windows application for Kingo root.
So it's better to not use another superuser app when rooting the fireTV (stick) with Kingo root?
Thanks sconnyuk. I have a bricked Stick from the Feb. KingRoot -> SuperSUMe disaster. Tried a lot of things, no luck.
But the Windows KingoRoot worked on the first try. (No 70% stoppage or anything.) I now have a root shell over adb. I'm going to wait on a rooted ROM to get it back to a normal state, but at least now I have hope.
Bierfreund said:
Worked! Did not know, that there's also an windows application for Kingo root.
So it's better to not use another superuser app when rooting the fireTV (stick) with Kingo root?
Click to expand...
Click to collapse
Just use Kingo roots superuser. Im going to try a few different su versions later see if I have any luck.
At the moment any other than kingoroots will brick, (caun unbrick if in this situation so I guess anyome can try)
---------- Post added at 05:53 PM ---------- Previous post was at 05:52 PM ----------
ftgftg said:
Thanks sconnyuk. I have a bricked Stick from the Feb. KingRoot -> SuperSUMe disaster. Tried a lot of things, no luck.
But the Windows KingoRoot worked on the first try. (No 70% stoppage or anything.) I now have a root shell over adb. I'm going to wait on a rooted ROM to get it back to a normal state, but at least now I have hope.
Click to expand...
Click to collapse
No need to wait. Try this guide ive put together, just do it over usb. Cant see why I wouldnt work.
http://forum.xda-developers.com/fire-tv/development/fire-tv-stick-downgrade-firestarter-3-2-t3399298
sconnyuk said:
Connect your fire stick to a windows pc/laptop. (i used windows 10 64bit)
Let the drivers install.
Download the windows version of Kingo root.
Click root, try this a couple of times (it probably will fail and stick at 70 percent)
unplug the stick and try again, when it hits 70 percent again plug your hdmi lead in (already connected to tv)
It should root and write back the correct su files.
If you want to unroot, install kingo and super user again on the fire stick then either use the unroot feature in super user app (you will have to purchase mouse toggle for fire tv, if you havent got it already to navigate to the 3 little dots menu icon top right corner)
Or re plug it into windows pc/laptop and unroot through the windows tool.
Click to expand...
Click to collapse
Thanks for the tutorial. But it doesn't work for me. I have and old fire stick TV with 5.0.5 that I bricked with KingRoot (not Kingo) -> SuperSUMe. I tried to follow your steps and KingoRoot goes to 100% at the first time. But when I connect the stick to my PC it's still stucks at the FireTV Logo . I don't know if I followed some step wrong.
PS: Sorry for my bad english.
SrTommy said:
Thanks for the tutorial. But it doesn't work for me. I have and old fire stick TV with 5.0.5 that I bricked with KingRoot (not Kingo) -> SuperSUMe. I tried to follow your steps and KingoRoot goes to 100% at the first time. But when I connect the stick to my PC it's still stucks at the FireTV Logo . I don't know if I followed some step wrong.
PS: Sorry for my bad english.
Click to expand...
Click to collapse
Try multiple times with Kingoroot, You can try windows version of KING root multiple times also.
Failing this you can try to run both programs simultaneously.
Good luck
sconnyuk said:
Try multiple times with Kingoroot, You can try windows version of KING root multiple times also.
Failing this you can try to run both programs simultaneously.
Good luck
Click to expand...
Click to collapse
It finally works!!!...... almost
Now the sticks pass the fire tv logo, but takes a lot of time to open the firestarter menu. And I can't do anything there. The remote doesn't response. I try to do a factory reset to the stick but I can't find the way . Thank you anyway. At least I can escape from the loop at boot.
SrTommy said:
It finally works!!!...... almost
Now the sticks pass the fire tv logo, but takes a lot of time to open the firestarter menu. And I can't do anything there. The remote doesn't response. I try to do a factory reset to the stick but I can't find the way . Thank you anyway. At least I can escape from the loop at boot.
Click to expand...
Click to collapse
Try removing the batteries and re-pairing the remote, try this multiple times as it has happened to me before.
sconnyuk said:
Try removing the batteries and re-pairing the remote, try this multiple times as it has happened to me before.
Click to expand...
Click to collapse
I thought that I had edited my previous post but it seems that it didn't save the changes. Finally I could restore my fire stick following your downgrade guide. I reinstalled the firmware 5.0.5 and everything works perfect. Thanks a million!!!
SrTommy said:
I thought that I had edited my previous post but it seems that it didn't save the changes. Finally I could restore my fire stick following your downgrade guide. I reinstalled the firmware 5.0.5 and everything works perfect. Thanks a million!!!
Click to expand...
Click to collapse
Your welcome.
Glad I could help.
Hi,
I tried to install XPosed to be able to install Google Play store later following a guide I successfully used on my rooted FTV 1st gen.
XPosed installation went fine but probably I deleted some user file I had not and box started checking for updates. I stopped the process in the meantime. Nothing seems to be affected. Root is still in place and firmware version is still 5.0.5. BUT each time a reboot my stick now it asks to pair my remote, then asks me to choose a language as it wants to complete an update. Just when I goes further it says that it has not been possibile to complete update. I tried to "downgrade" with a clear 5.0.5 firmware zip. It went fine but I had to disable OTA again to avoid the online updates. So it still fails to check for updates and each time it tries to reinitialize update process. basically default amazon launcher doesnt work anymore but it's not a issue cause I have Firestarter 3.3 which works fine. The worst issue is that each time I reboot it asks for rempote pairing and I can't use amazon video anymore. Basically I'd like to remove this "checking for update" process and return to my actual rom. Is that possibile?
Thanks.
puppinoo.
Hoping someone can help me out. My stick is bricked. I loaded up the Kingoroot and tried to run the steps to recover it. However i dont think it's recognize the device since kingoroot is stuck at the loading page. Which driver files did you install for the fire stick? thanks.
Bricked fire stick- any advice
I tried to transfer a ustv4.0 APK zip file to the firestick via USB after some extensive instructions on YouTube video but found that using Google Drive with ES File Explorer would be the quick and easy method. I also got lost in the instructions after downloading ADB and fire starter. When plugging the firestick back into the TV to go the ES file route, the firestick doesn't even show up on the TV now- the HDMI port that I had used would display 'fire stick' and display the HDMI port #, now nothing shows up and then the screen times out quickly as if nothing is plugged in. When I first plugged in the firestick to my windows 10 laptop, I checked the drives and it didn't show up although I could hear a USB connection chime as if something just was connected and if I disconnected it, it had a disconnect chime as well. I did see in device manager before unplugging it that it had shown up as 'unknown device' towards the bottom land labeled as AFTM. Can anyone tell me what they think may have gone wrong and why it no longer shows up on the TV or why it's now not starting up for that matter? Any help would be appreciated.
tjmethod said:
I tried to transfer a ustv4.0 APK zip file to the firestick via USB after some extensive instructions on YouTube video but found that using Google Drive with ES File Explorer would be the quick and easy method. I also got lost in the instructions after downloading ADB and fire starter. When plugging the firestick back into the TV to go the ES file route, the firestick doesn't even show up on the TV now- the HDMI port that I had used would display 'fire stick' and display the HDMI port #, now nothing shows up and then the screen times out quickly as if nothing is plugged in. When I first plugged in the firestick to my windows 10 laptop, I checked the drives and it didn't show up although I could hear a USB connection chime as if something just was connected and if I disconnected it, it had a disconnect chime as well. I did see in device manager before unplugging it that it had shown up as 'unknown device' towards the bottom land labeled as AFTM. Can anyone tell me what they think may have gone wrong and why it no longer shows up on the TV or why it's now not starting up for that matter? Any help would be appreciated.
Click to expand...
Click to collapse
Hi did you find a solution. I have the same problem.
Thx
I have a P607T currently running Android 5.1.1. I have reset the tablet and installed root checker, and it says that "Root access is not properly operating or granted on this device" and says that KingUser is installed. I had previously used Kingroot to root a previous version of Android, but not sure why it is still installed. I am trying to figure out how to remove KingUser, but there is no icon and it does not show up in the app manager. I tried installing kingroot again and it shows in the app manager as a system app. Kingroot can no longer root my device on Android 5.1.1. I downloaded the 5.1.1 android rom for my device, but when I try to install it tells me that the footer is wrong and that signature verification failed and stops the install and reboots. One additional note, I have never been able to connect the tablet via USB to a pc, it has never shown up as a device or usb drive, so anything that requires me to connect to a pc won't work for me. (It charges fine, via usb and I have changed out the USB connector, but still no pc connection).
If you can follow my ramblings... I am just trying to get my tablet to be able to play movies and video from paid services, but it won't let me since it thinks the device is rooted. So does anybody have any ideas on how I can un-root my non rooted tablet or hide the root from VUDU, Fandango, Amazon, Netflix, etc.?
Have you tried a factory reset?
Yep, first thing I tried. I think kingroot or something wrote it's executable to the part of the system that doesn't get reset/overwritten on a factory reset.
Sorry to hear, try flashing all stock firmware from samsung from samsungs websight, flashing w samsungs flashing software.