Database Develop

Rooting .906 update

I recently received a replacement droid 3 for the one that stopped working. The replacement has the .906 update installed on it, and the one-click root tool that I used on the old droid 3 that I had fails. When it fails, it says that I might be using a version where the exploit has been fixed. Is there another way that I need to be doing this to get root?

jclingler5213 said:
I recently received a replacement droid 3 for the one that stopped working. The replacement has the .906 update installed on it, and the one-click root tool that I used on the old droid 3 that I had fails. When it fails, it says that I might be using a version where the exploit has been fixed. Is there another way that I need to be doing this to get root?
Click to expand...
Click to collapse
Use the droid 4 motofail root application
Sent from my XT862 using Tapatalk 2

When I run the droid 4 motofail, it immediately says "the system cannot find the specified path" and says press any key to continue. I have the 5.5 drivers installed, i'm connected via usb, in charge only mode, with my original usb cable.

jclingler5213 said:
When I run the droid 4 motofail, it immediately says "the system cannot find the specified path" and says press any key to continue. I have the 5.5 drivers installed, i'm connected via usb, in charge only mode, with my original usb cable.
Click to expand...
Click to collapse
Try going to either factory recovery pwr + x and doing a factory reset ory go to settings,privacy and doing a factory reset then make sure your phone has usb debugging enabled..
When you connect your phone to computer make sure you set your phone to charge only then try to reroot..

I was able to get it to root using the motofail program from the Droid Bionic forum. Rooted the first time like a champ. Thanks for the help though!

I need help in rooting my nexus 7

Hi Everyone,
I am having issues with my previously rooted Nexus 7. My device was rooted when it first came with Nexus 7 toolkit v2.0 and was rooted successfully. After an update to android 4.2 via the OTA updates, the root status was taken off from the device so I've used to tookit again to restore the root. But it seems like it was not properly rooted when I tested it using the root checker basic.
I've downloaded the Nexus 7 toolkit v4.0 yesterday to re-root the device but all options does not seems to work at all.
1. Root Device [Fastboot Mode] showing waiting for device
2. Root Device + Install Busybox [Fastboot Mode] showing waiting for device
3. Boot CWM Recovery and Install Root [Superuser or SuperSU] [ADB Mode] showing waiting for debugging mode for USB connection. already in debugging mode but it would not work.
5. Unroot, Uninstall Busybox + CWM Manager via CWM Recovery [ADB Mode] showing waiting for debugging mode for USB connection. already in debugging mode but it would not work.
Can anyone help me? Thanks.

Sounds like a driver issue to me, try uninstalling and then reinstalling them
Sent from my Nexus 7 using Tapatalk 2

leschua75 said:
Hi Everyone,
I am having issues with my previously rooted Nexus 7. My device was rooted when it first came with Nexus 7 toolkit v2.0 and was rooted successfully. After an update to android 4.2 via the OTA updates, the root status was taken off from the device so I've used to tookit again to restore the root. But it seems like it was not properly rooted when I tested it using the root checker basic.
I've downloaded the Nexus 7 toolkit v4.0 yesterday to re-root the device but all options does not seems to work at all.
1. Root Device [Fastboot Mode] showing waiting for device
2. Root Device + Install Busybox [Fastboot Mode] showing waiting for device
3. Boot CWM Recovery and Install Root [Superuser or SuperSU] [ADB Mode] showing waiting for debugging mode for USB connection. already in debugging mode but it would not work.
5. Unroot, Uninstall Busybox + CWM Manager via CWM Recovery [ADB Mode] showing waiting for debugging mode for USB connection. already in debugging mode but it would not work.
Can anyone help me? Thanks.
Click to expand...
Click to collapse
If that doesnt work ,try Wug's toolkit.

bfranklin1986 said:
Sounds like a driver issue to me, try uninstalling and then reinstalling them
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hi, thanks for the response. I've reinstalled the drivers many time and yet it doesn't help.

Leonhan said:
If that doesnt work ,try Wug's toolkit.
Click to expand...
Click to collapse
I tried wug's toolkit and a prompt came out telling me that adb device not found.

leschua75 said:
I tried wug's toolkit and a prompt came out telling me that adb device not found.
Click to expand...
Click to collapse
It seems to me that adb drivers were not installed properly. Try searching here in the forum "universal naked driver". Uninstall every nexus 7 driver in your pc first before installing that usb pack.

I'm trying to remember what I did but I had the same problem initially. Try toggling the USB setting after you plug it into your computer on the tablet. There are two choices.
Sent from my Nexus 7 using xda app-developers app

You also might want to try a different cable / USB port

I had the same problem recently. The drivers did not install correctly. Use wugs toolkit and follow the "install driver" directions. When you get to the part that says option 3 is recommended don't go that route. Use option 1 which I believe is pdnet or pdanet (something like that) and it should work fine after that. That's how it worked for me.
Sent from my Nexus 7 using xda premium

Luda305 said:
I had the same problem recently. The drivers did not install correctly. Use wugs toolkit and follow the "install driver" directions. When you get to the part that says option 3 is recommended don't go that route. Use option 1 which I believe is pdnet or pdanet (something like that) and it should work fine after that. That's how it worked for me.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
+1 PDANet method was my only success too !

If you (meaning the OP, leschua75) or anyone else needs the latest Google USB drivers for Android, they're in the Android SDK obviously or I can upload them someplace like my Dropbox account. I tried the PDANet drivers, RAW drivers, older drivers, and a half dozen of other ones and nothing would allow my N7 to be seen through ADB until I gave up mucking around and just grabbed the proper actual SDK from Google themselves and then saved the drivers, both x86 and x64.
As soon as I installed those drivers manually it was clear sailing with ADB usage and I haven't had one issue since. None of the other drivers ever worked for me personally, while some people have had success.
My belief is that the best ones are from Google directly so that's what I use now. The latest drivers (as of Feb 5, 2013) are here:
http://dl.dropbox.com/u/19019338/Latest_Google_Android_USB_Driver_2-5-2013.zip
And just for the paranoid, here's a VirusTotal scan of the archive and contents along with checksums too:
https://www.virustotal.com/file/42d...34e549649b0a3bce3915374b/analysis/1360594983/
Hope this helps...

Don't forget to restart your computer after installing the ADB drivers

Did you remember to turn on USB debugging?
In the settings menu, select 'about' then scroll down to the bottom and tap build number 8 times to turn on developers options, then go back to the settings page, select developers options and turn on USB debugging hope this helps.
Sent from my Nexus 7 using Tapatalk HD

[RECOVERY] Ouya CWM Recovery

Unofficial CWM Recovery for Ouya
One-Click Style Method
To help people get up and going quickly, I've turned the steps below into an automated script package.
The attached OneClickOuyaRecovery.zip archive contains automated scripts to install CWM Recovery.
Whether you use Linux, Mac OSX, or Windows 7, all are invited to join in the fun!
Before you begin, you need to have your Ouya hooked up to a TV and powered on.
You also need to have a micro usb cable handy.
1) Download the OneClickOuyaRecovery.zip file and extract it (a folder on your desktop is fine).
2) Open the folder and you'll see a folder for each operating system. Open the folder for the OS of your choice.
3a) For Linux and Mac OSX users, run InstallOuyaCWMRecovery.sh in terminal by navigating the folder and running "./InstallOuyaCWMRecovery.sh" (you might just be able to run it by double clicking it. It depends on your setup).
3b) For Windows 7 users, double click the batch file InstallOuyaCWMRecovery.bat
4) Follow the on screen instructions. If you get an error saying there was no device found, run the script again (sometimes adb is finicky).
5) If all went well, you should be brought to CWM recovery.
If you have any trouble, seeking help is more efficient if you post the script's output to a pastebin (http://pastebin.com/) and post a link to it (I/others can see what happened).
Link to OneClickOuyaRecovery.zip - http://invisiblek.org/ouya/OneClickOuyaRecovery.zip
P.S. If anyone has proper hosting and would like to host OneClickOuyaRecovery.zip, please let me know and I'll change the link.
Thanks to invisiblek we have some more permanent hosting than a Dropbox account. Hosting costs money guys, so be sure to drop invisiblek a few coins if you can spare it.
Manual Method
Steps to install CWM on Ouya:
1) Perform the SDK Setup portion of thread http://forum.xda-developers.com/showthread.php?t=2272266 and install su, busybox, and superuser from this thread http://forum.xda-developers.com/showthread.php?t=2270589. This is done so we can get adb access and the necessary tools on the Ouya
2) Download the OuyaCWMrecovery6.0.3.2.img file and the OuyaCWMrecovery6.0.3.2flashable.zip.
3) Transfer the OuyaCWMrecovery6.0.3.2flashable.zip to your Ouya's internal sdcard (you can do this with "adb push /path/to/OuyaCWMrecovery6.0.3.2flashable.zip /sdcard/OuyaCWMrecovery6.0.3.2flashable.zip"). Leave the OuyaCWMrecovery6.0.3.2.img on your computer.
4) Connect your computer to the Ouya's micro-usb port (if it isn't already), connect a USB keyboard to the Ouya (bluetooth won't work), and run "adb reboot bootloader"
5) Wait 30 seconds (seriously)
6) Use fastboot to boot CWM by running "fastboot boot /path/to/OuyaCWMrecovery6.0.3.2.img". This boots from our CWM recovery without writing to any partitions.
7) Using your USB keyboard's arrow and enter keys, select "install zip from sdcard", "choose zip from sdcard", and "OuyaCWMrecovery6.0.3.2flashable.zip". This flashable zip writes CWM to the recovery partition and renames a pesky file that causes the stock recovery to be written on reboot.
8) Select "go back", and "reboot system now" to return to Andriod (CWM will ask "ROM may flash stock recovery on boot. FIX?". Make sure you select "NO")
9) Since we don't have any volume or home keys on the Ouya, to get back into recovery, you need to run "adb reboot recovery". Go ahead and try it once the Ouya has been sitting in Android for a minute or so. If all went well, you should reboot into CWM recovery!
This method was generated from the work done in http://forum.xda-developers.com/showthread.php?t=2292556. If you feel like pressing the thanks button, don't just thank me. Also thank professorpoptart, sonofskywalker3, and rayman. And obviously this is possible because of the fine folks behind CWM and Cyanogenmod.

Followed all your instructions, worked fantastically (aside from some strange windows 8 driver issues of course). Great job guys!

FrostyWolf said:
Need to fix your two forum links.
Click to expand...
Click to collapse
Thanks. All fixed.
Sent from my SCH-I535 using xda premium

Excellent work to everyone involved.

So, you are saying that no bluetooth KB work or just the one you tried? Did it have it's owen receiver or did you try to pair with Ouya's bluetooth? I am very interested in this because I have a Asus bluetooth KB/Mouse with their own receiver that I was hoping to use with the Ouya.

lartomar2002 said:
So, you are saying that no bluetooth KB work or just the one you tried? Did it have it's owen receiver or did you try to pair with Ouya's bluetooth? I am very interested in this because I have a Asus bluetooth KB/Mouse with their own receiver that I was hoping to use with the Ouya.
Click to expand...
Click to collapse
I believe what he meant was simply that it won't work in recovery.

tcollum said:
I believe what he meant was simply that it won't work in recovery.
Click to expand...
Click to collapse
That is correct. BT keyboards work fine on the OUYA normally.

Thoughts, when I fastboot the recovery.img I get no video to navigate to the correct option to install the zip. I know the recovery.img I fastbooted booted because it shows listed as "recovery" under adb devices.
I had this issue with the stock recovery and a mix of hooking it up to another monitor and pushing a Generic.kl with an edited home button seemed to fix it. I have reboot and went back into stock recovery and video works fine there, just not when I fastboot the CWM one.
I could use the adb shell in recovery to "--install_package=xxxxxx.zip" but it wont be too much help if I cant navigate the CWM menu...

professorpoptart said:
Thoughts, when I fastboot the recovery.img I get no video to navigate to the correct option to install the zip. I know the recovery.img I fastbooted booted because it shows listed as "recovery" under adb devices.
I had this issue with the stock recovery and a mix of hooking it up to another monitor and pushing a Generic.kl with an edited home button seemed to fix it. I have reboot and went back into stock recovery and video works fine there, just not when I fastboot the CWM one.
I could use the adb shell in recovery to "--install_package=xxxxxx.zip" but it wont be too much help if I cant navigate the CWM menu...
Click to expand...
Click to collapse
Hmmm. That's weird. It worked fine on my TV without pressing a key before hand. Maybe it's the keyboard or TV?
Sent from my Nexus 7 using xda premium

Tried 2 tv's stock recovery works on both.
edit: Tried it on a third TV works!? whatever... At least we know anyone has issue in the future just keep trying more displays until one works...
edit: don't know if it matters but just fyi, but I tried 2 1080P displays and got nothing, tried it on an old 1080i and it worked...
edit: Hooked it back up to the main TV and recovery video still works... whatever...
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

professorpoptart said:
Tried 2 tv's stock recovery works on both.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Probably not the issue, but wanted to rule it out anyway. What's the md5 hash of the .img. I got c6b37906f280b16cd200503c3cde6dfb
Sent from my Nexus 7 using xda premium

mybook4 said:
Probably not the issue, but wanted to rule it out anyway. What's the md5 hash of the .img. I got c6b37906f280b16cd200503c3cde6dfb
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
got it working, edited my previous post... basically tried a third, lol

Crazy driver / edid issues maybe? Who knows. I'm glad you got it working though.
Sent from my Nexus 7 using xda premium

mybook4 said:
Crazy driver / edid issues maybe? Who knows. I'm glad you got it working though.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I was also unable to get video after running fastboot unless I had the HDMI plugged in prior to issuing the command.

FrostyWolf said:
I was also unable to get video after running fastboot unless I had the HDMI plugged in prior to issuing the command.
Click to expand...
Click to collapse
Ohhhhhh. I keep HDMI plugged in the entire time. Maybe that's the issue. Professorpoptarts, we're you plugged into HDMI at all times?
Sent from my SCH-I535 using xda premium

When it wasnt working yes, had everything connected, then powered up, then fastbooted. Even tried unplugging and plughing back in the hdmi a few times to try and get it to come on. However since I got it working I have not gad the issue (knock on wood)
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

professorpoptart said:
When it wasnt working yes, had everything connected, then powered up, then fastbooted. Even tried unplugging and plughing back in the hdmi a few times to try and get it to come on. However since I got it working I have not gad the issue (knock on wood)
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
is there a custom kernel up for this device yet? I havent seen one.

Kernel source was released 4 days ago, it may take some time.
However, I'm currently working on porting Cyanogenmod 10 from source, professorpoptart is working on porting an aosp rom from the HTC One X+, and I'm probably going to release a "Custom ROM" tonight that's just an easy flash to add a bunch of extra functionality. So no kernels yet, but Roms should start popping up soon.

I love you all!

FrostyF7 said:
I love you all!
Click to expand...
Click to collapse
Hooray! I'm taking my ouya off craigslist! I was beginning to think nobody was going to develop for this box! I can't wait to start sending donations! (soon, life is expensive these days....).

[Q] Can't read Atrix HD on my computer after flashing PACman ROM

Hi guys. I just installed PACman ROM latest version on my previously stock Atrix HD. Now, I can't read my Atrix HD on my computer. I already installed motorola device manager and still can't read. Is there a driver that I need to install? Thanks

tanos0415 said:
Hi guys. I just installed PACman ROM latest version on my previously stock Atrix HD. Now, I can't read my Atrix HD on my computer. I already installed motorola device manager and still can't read. Is there a driver that I need to install? Thanks
Click to expand...
Click to collapse
Because developer mode isn't enable,
Setting --->About Phone--->hit build number 7 times.
Settings -->Developer options--->Android Debugging
rock on.

tanos0415 said:
Hi guys. I just installed PACman ROM latest version on my previously stock Atrix HD. Now, I can't read my Atrix HD on my computer. I already installed motorola device manager and still can't read. Is there a driver that I need to install? Thanks
Click to expand...
Click to collapse
Turn on USB debugging, while connecting your device to system, reboot it without disconnecting. Also if it prompt for RSA key access check always allow this computer and accept it....
Sent from my MB886 using xda app-developers app

No dice
Tried your suggestions, guys. But its still not working.
I tried the 7 clicks. It showed that I have developer access. Then I turned on USB debugging and restarted the phone. No notification about USB debugging, my computer still doesn't detect it.

tanos0415 said:
Tried your suggestions, guys. But its still not working.
I tried the 7 clicks. It showed that I have developer access. Then I turned on USB debugging and restarted the phone. No notification about USB debugging, my computer still doesn't detect it.
Click to expand...
Click to collapse
No adb/debgging is normal on the custom roms. Haven't had adb in at least 2 weeks.

skeevydude said:
No adb/debgging is normal on the custom roms. Haven't had adb in at least 2 weeks.
Click to expand...
Click to collapse
Too bad. Does that mean that I can't use MTP mode?

tanos0415 said:
Too bad. Does that mean that I can't use MTP mode?
Click to expand...
Click to collapse
Can you give details as to what computer/os you are running?
Does it charges when you plug the phone into the computer?
With or without developer mode enabled, your computer should still respond to the phone. If it doesn't then the problem is the computer.

hungrymr2 said:
Can you give details as to what computer/os you are running?
Does it charges when you plug the phone into the computer?
With or without developer mode enabled, your computer should still respond to the phone. If it doesn't then the problem is the computer.
Click to expand...
Click to collapse
Yeah its charging. Drivers tried installing but it says that it was not successfully installed. It also shows as unknown device.
I'm running Windows 7 64bit. It can detect fine back when it was stock. The problem only showed up after I installed PAC rom

The drivers can be corrupted for no good reason try deleting and re-installing.

tanos0415 said:
Too bad. Does that mean that I can't use MTP mode?
Click to expand...
Click to collapse
Can't use MTP or Camera mode (at least on my linux box I can't). All I know is adb doesn't work and that's the only reason I have to plug into usb...I unmount my sd and plug it into my PC to do file transfers (or adb push from recovery)...adb does work in recovery, just not the system.
tanos0415 said:
Yeah its charging. Drivers tried installing but it says that it was not successfully installed. It also shows as unknown device.
I'm running Windows 7 64bit. It can detect fine back when it was stock. The problem only showed up after I installed PAC rom
Click to expand...
Click to collapse
Same things happen on my linux box...problem showed up the same time for me as well....installed a 4.2.2 rom...
//this is a known issue....related to the kernel and usb drivers (started about three weeks ago) Use an earlier, first week of June or so, kernel if you need adb/usb...thought I don't recommend doing that.

frog1982 said:
The drivers can be corrupted for no good reason try deleting and re-installing.
Click to expand...
Click to collapse
+1 try to delete them in safemode to ensure that the old drivers are gone for good.
I did try PAC once and it connected to my win 7 64bit without any issues.
Sent from my MB886 using xda app-developers app

tanos0415 said:
Hi guys. I just installed PACman ROM latest version on my previously stock Atrix HD. Now, I can't read my Atrix HD on my computer. I already installed motorola device manager and still can't read. Is there a driver that I need to install? Thanks
Click to expand...
Click to collapse
I had this problem.
Step 1: Enter system Settings>Developer options.
Step 2: Tick "Android debugging", "USB debugging notify" (makes it easier to know if connection is successful), and change the "Root acess" setting to "Apps and ADB".
Step 3: Reboot Phone and connect to computer.
This is what I did and I haven't had a problem since. Hope this helps

Blackest Pain said:
I had this problem.
Step 1: Enter system Settings>Developer options.
Step 2: Tick "Android debugging", "USB debugging notify" (makes it easier to know if connection is successful), and change the "Root acess" setting to "Apps and ADB".
Step 3: Reboot Phone and connect to computer.
This is what I did and I haven't had a problem since. Hope this helps
Click to expand...
Click to collapse
already tried that. thanks anyway. :good:

Did you do all that And the restart the computer itself? I think I read that on another android forum (android central maybe?) That that helps sometimes...
Sent from my PACman Atrix HD using XDA Premium

ADB drivers

Hi All,
I'm trying to get ADB working. I installed the drivers via Motorola Device Manager. After plugging in my X it installs:
- USB Composite Device
- XT1058
But does not install
- Motorola ADB Interface (no driver found)
Anyone get ADB working / know where I can get that driver?
Thanks,

Try here http://forum.xda-developers.com/showthread.php?t=2406409
Sent from my XT1058 using XDA Premium 4 mobile app

flashallthetime said:
Try here http://forum.xda-developers.com/showthread.php?t=2406409
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you, that did it!

Great, now to flash recovery
Sent from my XT1058 using XDA Premium 4 mobile app

It did not work for me. Always Error: device not found.
The XT1058 in Device Manager have an exclamation mark on it. Already reinstalled Motorola Drivers many many times. Im stuck!

douglasrac said:
It did not work for me. Always Error: device not found.
The XT1058 in Device Manager have an exclamation mark on it. Already reinstalled Motorola Drivers many many times. Im stuck!
Click to expand...
Click to collapse
Windows 8 or 8.1 ?
Sent on my Gummy running Lenoto X

flashallthetime said:
Windows 8 or 8.1 ?
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Windows 7.

douglasrac said:
Windows 7.
Click to expand...
Click to collapse
Did you try another USB port
Sent on my Gummy running Lenoto X

Yes. At least 3 of them.

douglasrac said:
Yes. At least 3 of them.
Click to expand...
Click to collapse
Latest Motorola device manager? What have you tried specifically
Sent on my Gummy running Lenoto X

Well my Windows 7 is brand new. Just installed, no garbage on it.
- Installed MotorolaDeviceManager_2.4.5 (most updated in Motorola support site)
- Installed Android SDK and updated.
Doesn't work.
- Tried different USB ports, front and back. Red or blue.
- Tried the Motorola Device Manager from the topic you said, the 6.2.
- Tried Disable and Enable again USB Debugging.
- Tried changing driver manually according to some tutorials (ABD Interface driver on Windows Device Manager)
- Unchecked option to verify harmful apps installed by ADB/ADT on Developer Tools.
- Checked Allow unknown sources on Security option.
- Prayed to God for several hours.
As said I rooted my phone (retail). Then I accepted the OTA update 4.4.2. (Yes, stupid me). I manage to get out of bootloop by Wiping Cache, Dalvik, etc. So back to 4.4, still rooted. Since I don't want to lose root, I would like to flash a new recovery.img that will allow the update to go trough.

douglasrac said:
Well my Windows 7 is brand new. Just installed, no garbage on it.
- Installed MotorolaDeviceManager_2.4.5 (most updated in Motorola support site)
- Installed Android SDK and updated.
Doesn't work.
- Tried different USB ports, front and back. Red or blue.
- Tried the Motorola Device Manager from the topic you said, the 6.2.
- Tried Disable and Enable again USB Debugging.
- Tried changing driver manually according to some tutorials (ABD Interface driver on Windows Device Manager)
- Unchecked option to verify harmful apps installed by ADB/ADT on Developer Tools.
- Checked Allow unknown sources on Security option.
- Prayed to God for several hours.
As said I rooted my phone (retail). Then I accepted the OTA update 4.4.2. (Yes, stupid me). I manage to get out of bootloop by Wiping Cache, Dalvik, etc. So back to 4.4, still rooted. Since I don't want to lose root, I would like to flash a new recovery.img that will allow the update to go trough.
Click to expand...
Click to collapse
OK, have you attempted to put your phone in fastboot mode and plug it in , you should see the driver notification pop up. Also you should be using mfastboot not fastboot to install recovery found here http://forum.xda-developers.com/showthread.php?t=2603358
Sent on my Gummy running Lenoto X

Phone is detected by the PC and adb devices command when on normal system. But when I go to fastboot mode it doesn't recognize anymore by abd. Still the display shows USB Connected and I can hear Windows sounds showing something was indeed connected/disconnected. But ADB is dead.
I was never able to use mfastboot. Simple doesn't work either. Anyway, if ADB is at least able to see the device, then I can try it again.
---------- Post added at 08:41 PM ---------- Previous post was at 08:38 PM ----------
Oh and I just tried one more thing: Install RSD Lite. RSD Lite is able to see the device while on fastboot. ADB command still NO.

douglasrac said:
Phone is detected by the PC and adb devices command when on normal system. But when I go to fastboot mode it doesn't recognize anymore by abd. Still the display shows USB Connected and I can hear Windows sounds showing something was indeed connected/disconnected. But ADB is dead.
I was never able to use mfastboot. Simple doesn't work either. Anyway, if ADB is at least able to see the device, then I can try it again.
---------- Post added at 08:41 PM ---------- Previous post was at 08:38 PM ----------
Oh and I just tried one more thing: Install RSD Lite. RSD Lite is able to see the device while on fastboot. ADB command still NO.
Click to expand...
Click to collapse
Adb is probably your issue ,if rsdlite see it that means the fastboot driver is installed, the link I gave you has the SDK installer link
Sent on my Gummy running Lenoto X

But SDK is installed and updated.
Can I use RSD to flash recovery.img ?

douglasrac said:
But SDK is installed and updated.
Can I use RSD to flash recovery.img ?
Click to expand...
Click to collapse
No only stock recovery, seems like its a problem with SDK , try one if those tool kits from the development threads and see If they work
Sent on my Gummy running Lenoto X

Well I will try to reinstall SDK.
Why I can't flash recovery.img ? I want to flash the stock recovery. Isn't this abd commands the same as RSD Lite program do?

douglasrac said:
Well I will try to reinstall SDK.
Why I can't flash recovery.img ? I want to flash the stock recovery. Isn't this abd commands the same as RSD Lite program do?
Click to expand...
Click to collapse
So you're wanting to get the ota, if so then yes flash the complete. Sbf firmware using rsdlite
Sent on my Gummy running Lenoto X

But then 4.4.2 is rootable? I don't want to lose the root.

douglasrac said:
But then 4.4.2 is rootable? I don't want to lose the root.
Click to expand...
Click to collapse
Is your boot loader unlocked?
Sent on my Lenoto A2109 tablet