Hello all,
Has anyone been experiencing issues with DroidDroid lately?
I can't seem to get any of the USB modes to work.
Haven't heard back from the developers yet as I'm sure they're busy.
I'm running newest version of Android P and I got the recent update for DriveDroid.
When I select Standard Android Kernel as the USB system(the one that always worked) and try the other 2 available USB systems. It just continues loading forever at "Hosting DriveDroid Image"
This tool is very invaluable to me, I'm hoping to get it working again. Any help is appreciated!
Thanks =]
mark7807
Someone over at reddit just confirmed it worked. https://www.reddit.com/r/androidapps/comments/90i6d1/alternatives_to_drivedroid/ecs3ple im giving it a try now myself...
Works fine for me
Related
Hey, I got tired of waiting for Motorola's non existant software updates and decide to install the US update with the help of the 5 step post that is in the development forum(http://forum.xda-developers.com/showthread.php?t=1089695). I then tried to connect my camera to the Xoom but it would not detect it in the Gallery app. I'm not doing anything wrong, I've got PTP mode on the camera, got a USB-host cable and the Xoom is also detecting the camera when I check the dmesg log. So I was wondering if anybody here had a european Xoom with "hacked" 3.1 update could try connecting a camera with PTP to the Xoom and see if it shows up in their gallery app.
Did you flash a custom kernel that supports USB? If not head over to dev section and flash a kernel. Also use ES file explorer or anything else you may use and look in the usbOTG directory. Check to see if your camera images are in there.
sjuberman said:
Hey, I got tired of waiting for Motorola's non existant software updates and decide to install the US update with the help of the 5 step post that is in the development forum(http://forum.xda-developers.com/showthread.php?t=1089695). I then tried to connect my camera to the Xoom but it would not detect it in the Gallery app. I'm not doing anything wrong, I've got PTP mode on the camera, got a USB-host cable and the Xoom is also detecting the camera when I check the dmesg log. So I was wondering if anybody here had a european Xoom with "hacked" 3.1 update could try connecting a camera with PTP to the Xoom and see if it shows up in their gallery app.
Click to expand...
Click to collapse
I think it is not a problem with your update--hacked or not. It seems that being able to import photographs into gallery is problematic. It seems to work for only certain cameras, or is hit-or-miss at best. I hope this gets resolved soon. See this thread: http://forum.xda-developers.com/showthread.php?t=1142257
I thought it might be my camera(Canon 5D) so I asked around and found people that have used that camera with the xoom successfully. I also tried a point-and-shoot(Canon Ixus 130) and it didn't work either. I also tried flashing Tiamat 1.1 and it didn't change anything. Think I'll try the Aussie stock 1.3 images that just came in and see if it does the trick.
sjuberman said:
I thought it might be my camera(Canon 5D) so I asked around and found people that have used that camera with the xoom successfully. I also tried a point-and-shoot(Canon Ixus 130) and it didn't work either. I also tried flashing Tiamat 1.1 and it didn't change anything. Think I'll try the Aussie stock 1.3 images that just came in and see if it does the trick.
Click to expand...
Click to collapse
Let us know if you have success. Good luck!
Flashed stock AU images, updated OTA to 3.1 and it did not help with either camera. Flashed back to stock 3.0.1 european, going to try Tiamat again today/tomorrow.
Hi, I'm sorry if this has been asked before, basically a few weeks ago I was having problems with my Tab 2 p3110, it just wasn't running right. At around the same time I ordered an EZCAST hdmi device for my tv.
Well, I used Odin and cwm and taught myself how to upgrade to kitkat withCM11 nightlies, great stuff, fixed the issues I was having.
Then my tv dongle arrived, the one feature I wanted to use more than anything was screen mirror/AirPlay. No you can imagine my dismay when I couldn't even find the option in cm11, I found cast screen but it wouldn't work.
So, having tried several nightlies hoping the problem would be fixed I settled on reinstalling the stock 4.2.2 rom following the instructions on here. It bricked my tab 2 but I managed to get it going again and reinstalled the stock rom after several days of trying.
All this to find the screen mirror option was not available on the stock rom!! I can't figure out why but thought, maybe, an upgrade was needed, so I headed to the update tab to be told that my device was modified, updates are not available!
To be honest I'm ready to throw it in the lake behind my house I'm that frustrated, does anyone have any suggestions on getting screen mirroring working?
http://live.samsung-updates.com/index.php?device=GT-P3110
Here... get the clean firmware here. It will give a pure system that won't trip the modification check.
It will also give you the factory recovery system.
Look up the p311x PIT file and when in odin pick the size that matches your tablet.
If it hangs at boot try doing a factory reset from recovery.
That's what worked for me to allow me to check updates.
I can't say that this will fix screen mirror, since I've never used it or seen the option on my p3113
Sent from my SGH-T999 using Tapatalk
Thanks for that. I can't find my model number on the list, The british one is close and as thats where I live i think i'll give that a go.
Thanks again for your help
Didn't work, still saying that the device has been modified and in download mode shows "count 1"
Any other ideas?
Triangle away?
Sent from my SGH-T999 using Tapatalk
Hey, I use my tablet with the Samsung Smart View ap.
You must have the right samsung tv for it to work and it's not perfect, but it is a nice feature. I stopped updating my tab because this is the most important feature for me.
I rooted my device and have the same issue as you, that's how I came across this thread.
Hey Folks,
got some messy Prob's with my old nVidia Shield LTE Tablet.
The Facts:
-KillSwitch not Triggered and it was succesfully Rooted in November 2015, TEGRA-OTA was also Removed (nomoreota)
-worked for Months (beneath one year), only Super-SU penetrated me periodely that it needs to be Updated, but it couldnt be done, it said "not enough Space" after trying to install a newer Version. :silly:
-past Month (January 2017) i decided to do a Factory-Reset, because Girlfriend should get the Shield, thats where the Problem started:
After clicking Factory-Reset, it began to work. After 4 Hours and nothing happening, i decided to Power it Off and start fresh with Installing a clean Stock-ROM and remove the TEGRA-OTA as i done a year before.
But from now on things get messy and to complicated for me.
In the Past i rooted and flashed it with "Shield-RAM", found here on xda.
But this Time it didnt ended with a working Shielt-Tablet. It stucks alwas in a Bootloop, in Recoverymode also as in normally booting the flashed OS.
Confused an disturbed by this, i tried different Recoverys (TWRP 2.8 and 3.0, also a CWM), all with the same Effect: Bootloop
Now i only can acces the Bootmenue which says Bootloader Unlocked.
I dont now what to do from here on and would be very happy and glad, if someone can help me figuring out whats going wrong.
If further Details are needed i will do my best to provide things i forgot here to mention.
With kind regards - ToxicFighter1
Ps.: excusy my bad spelling, bit rusty in flawless english typing:good:
Hi !
There is this thread where you can try to get it back to stock https://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541
This nice index may help as well
Good luck !
Thanks, but that's not the problem. If I boot into Fastboot / Bootloader, it's totally fine. In fact, I can plug the tablet up to my PC when it's in any state and doesn't experience the issue. It only occurs when I have it plugged into AC. SO far, I've tried 3-4 different cables and power supplies for 2.4A, 2.1A, and 1.2A - all adapters which worked 100% prior to updating.
Suggestions?
OK - Finally fixed it...
I replaced everything as shown above, but ran into the issue again as soon as FlashFire installed the OTA. So, I tried a different way to upgrade and no longer have the issue. Below is what I did...
- Installed 4.4.0 via ADB/fastboot wirhOEM recovery
- Completed initial setup and upgraded to 5.0 via built in system update
- Rebooted
- Booted to bootloader and flashed TWRP recovery
- Booted to TWRP
- Installed SuperSU via sideload
I would have started out applying 5.0 via adb/fastboot, but have yet to see a full image available yet. Used same TWRP and SuperSU as originally used. Just eliminated GlashFire from process. Once I rebooted and everything loaded, plugged into 2.4a power, and it worked without going into boot loop.
Hope this may help someone else - Thanks
Hey Folks,
thx for the few answers, i'll try these Tips out the upcomig Days.
Lot'a Stuff to do atm, bit Busy.
With kind regards - Toxic
xanthrax said:
Hi !
There is this thread where you can try to get it back to stock https://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541
This nice index may help as well
Good luck !
Click to expand...
Click to collapse
Hey there, and personally Thx for the provided Link.
As announced i did try it, but with no Success.
I'll or explicit the Tablet gets Stuck at Step 17, the Bootsreen doesn't disapear.
Dont know whats Wrong, cause i did all as menitioned in the Post, every ADB/Fastbootstep with Succes-Message, and because Bootloader was already Unlocked, i took the Rooted Image.
But now, im still on Bootscreen, sick
With kind regards!
Just got the Oreo 8.1 update on my Project Fi Moto X4 (Motorola Version: OPW28.46-13). The phone does not show up in Windows anymore. No MTP, no ADB. It does charge. I've tried it on two different PCs. It was working seconds before applying the update. The cable does work properly with an S8.
Anybody else seeing this?
I'm a professional Android developer and I was using the phone for development before the update. The other issue is that Developer Mode was disabled after update. I re-enabled it after 8.1 and it didn't work. I've disabled/enabled USB Debugging and developer options several times.
Update:
Tried on OS X now too, same issue. OTG does work.
Work-Around:
https://forum.xda-developers.com/showpost.php?p=76430795&postcount=32
No mention in the release notes: https://mobilesupport.lenovo.com/us/en/Solution/MS127386
Can you help us out with getting the OTA via https://forum.xda-developers.com/moto-x4/how-to/androidone-april-ota-t3784442?
Neffy27 said:
No mention in the release notes: https://mobilesupport.lenovo.com/us/en/Solution/MS127386
Can you help us out with getting the OTA via https://forum.xda-developers.com/moto-x4/how-to/androidone-april-ota-t3784442?
Click to expand...
Click to collapse
It takes some days for the update to show on motoota.
The previous two months became available on there as my phone got the OTA notification. I have yet to see someone who has receive the April, verify they attempted Motoota here on XDA or Reddit.
dburckh said:
Just got the Oreo 8.1 update on my Project Fi Moto X4 (Motorola Version: OPW28.46-13). The phone does not show up in Windows anymore. No MTP, no ADB. It does charge. I've tried it on two different PCs. It was working seconds before applying the update. The cable does work properly with an S8.
Anybody else seeing this?
I'm a professional Android developer and I was using the phone for development before the update. The other issue is that Developer Mode was disabled after update. I re-enabled it after 8.1 and it didn't work. I've disabled/enabled USB Debugging and developer options several times.
Update:
Tried on OS X now too, same issue. OTG does work.
Click to expand...
Click to collapse
I am experiencing the same situation with Project Fi Moto X4 32G (Motorola Version: OPW28.46-13). No MTP, no ADB. It does charge OK. I had no such problems before the upgrade from 8.0 to 8.1. I tried on both Linux and OS X. The same issue. And yes, USB OTG works.
I have the exact same issue and fun fact, this means it no longer works with an Android Auto head unit (it worked flawlessly right up until the second the OTA update was installed).
Factory Data Reset did not fix it. Guess we are hosed unless somebody finds a work-around.
dburckh said:
Factory Data Reset did not fix it. Guess we are hosed unless somebody finds a work-around.
Click to expand...
Click to collapse
This makes me not want to take the update now. What bad news.
Folks, I have this too on my Moto G5S Plus after the April security patch for Nougat. No notification shade when I plug into the PC. No way to access MTP, ADB, etc... I also effects my charging. After the MTP interface fails, I have to reboot the phone before it will charge again.
Post in the Moto/Lenovo forum please. It's a HUGE problem.
dburckh said:
Just got the Oreo 8.1 update on my Project Fi Moto X4 (Motorola Version: OPW28.46-13). The phone does not show up in Windows anymore. No MTP, no ADB. It does charge. I've tried it on two different PCs. It was working seconds before applying the update. The cable does work properly with an S8.
Anybody else seeing this?
I'm a professional Android developer and I was using the phone for development before the update. The other issue is that Developer Mode was disabled after update. I re-enabled it after 8.1 and it didn't work. I've disabled/enabled USB Debugging and developer options several times.
Update:
Tried on OS X now too, same issue. OTG does work.
Click to expand...
Click to collapse
Got the OTA, it does not work and we'll never know why.
Just got the OTA. Don't have my OTG cable, but i can can confirm that I see device in fasboot, but not in ADB.
Neffy27 said:
Got the OTA, it does not work and we'll never know why.
Click to expand...
Click to collapse
Motorola just replied to my support request saying that they are going to replace my phone! I'm hoping it doesn't come to that.
dburckh said:
Motorola just replied to my support request saying that they are going to replace my phone! I'm hoping it doesn't come to that.
Click to expand...
Click to collapse
I am confused... Because of a software update broke ADB?
It would seem so. I will probably try to talk them out of it. I would rather have them escalate a fix.
encountered same issue
dburckh said:
Motorola just replied to my support request saying that they are going to replace my phone! I'm hoping it doesn't come to that.
Click to expand...
Click to collapse
Same here, just got 8.1 this morning on A1 moto x4 and android auto does not work anymore when it is connected to my car HU.
I just got the April 1 8.1 update this morning on my Moto X4 OPW28.46-13. Exactly the same thing. Android Auto head unit doesn't recognize the phone (or vice versa), and the USB options are greyed out and say only "not connected" whether plugged into the head unit or a computer. Project Fi support tells me I need to hard reset the phone. I don't have time to do that at the moment, but they tell me that if it doesn't work (and I very much doubt that it will) they'll "check the warranty options." Which I think is a euphemism for "send you a new phone if it's still under warranty".
What aggravates me about this (aside from the huge waste of time of having to deal with it) is - what if the phone were NOT under warranty? After their update breaks my phone, would they then tell me to buy a new phone?
My stupid X4 will download the 8.1 OTA, start installing, then fail halfway through. Guess there's a bright side after all.
dburckh said:
It would seem so. I will probably try to talk them out of it. I would rather have them escalate a fix.
Click to expand...
Click to collapse
Same response from support. I wonder if anyone that is able to create a TWRP backup, and test if a clean reset fixes issue.
jhedfors said:
Same response from support. I wonder if anyone that is able to create a TWRP backup, and test if a clean reset fixes issue.
Click to expand...
Click to collapse
I made full wipe after the update, nothing has changed.
Hi everyone. I've been using my old MZ600 (US) as a comic reader and would occasionally get on the internet or try and do something else. Just dealt with the dog slowness that was introduced years ago when it got updated to 4.1.2 (or maybe started with 4.0.4). Finally decided to just reimage it with stock and then apply updates.
I've run into two issues, though. I can't enable developer mode after I image it. I used the links from this forum post to get the stock images: https://forum.xda-developers.com/t/info-stock-images-other-links.1049485/
Tried both and while I get a working OS installed, for some reason tapping on the build number 7+ times does not enable developer mode. No idea what the issue is. Any suggestions? Does anyone have different versions of the stock image?
And even if I did get that working, I can't find the OTA updates. I found this forum post but all of the links are dead. Anyone know where those might be?
https://forum.xda-developers.com/t/ref-mz600-mz602-mz604-xoom-ota-rollup-thread.2461156/
The other thing I noticed is if I try to boot to recovery, I just get the little android mascot with a yellow ! triangle in him. Never any options. I thought maybe I could copy the update files (when I got them) over USB and then install the updates from recovery but that doesn't appear to be an option.
Update: I kept poking around and apparently this old version doesn't give a popup or show anything that developer mode was enabled. However, when going to Settings > Applications there is [now] a Development option and under that I can turn on USB Debugging. Sweeeet.
But I still need the OTAs if anyone knows where to get them, (US, Verizon tablet)