Hi all,
I purchased a gemini wifi recently, but a 4g version arrived! I'm now trying to flash Linux on there, but I cannot get the flash tool to do anything.
I'm pretty sure that this is a driver issue, but I'm not sure what to do about it. I've tried windows 11 and 10, as well as ubuntu 20.04 to flash this thing and nothing is working.
On the windows 11 host I even disabled memory protection to allow the drivers to work correctly, but that made no difference.
Following the guides on planet computer, it's not clear what state the device should be in, but I've tried normally booted into android as well as in recovery mode (booted with Esc and side button depressed on boot}
What am I missing here? Does flashing this device just no longer work?
Thanks in advance for your help!
it still works presuming you are referring to this guide: https://support.planetcom.co.uk/index.php/Linux_Flashing_Guide
I unfortunately don't think I am able to help you debug the situation from the information you provided.
I am not sure where most of the users congregate, but I have seen some sporadic recent activity here: https://www.oesf.org/forum/index.php?board=192.0
From my own experience, windows 7 and windows 10 have worked flawlessly, ubuntu worked for me in the past, but had trouble recently. win7 and win10 in virtualbox requires delicate usb device setup adding device during gemini reboot, and still gives some trouble.
I haven seen any updates or security patches from planet on neither android nor debian, so got myself a sailfish X license to support their development, it looks like a lot of updates (most recently yesterday: https://forum.sailfishos.org/t/release-notes-vanha-rauma-4-4-0-72/ )
good luck
Related
Alright, so the issue is... I have the SDK... and it won't work on either of the operating systems I run. I am running Ubuntu 9.10 and Windows 7, both 64bit. There are two main aspects I am after with it. Using DDMS to take screenshots and mess with stuff on devices, and the virtual Android system. On Ubuntu, DDMS comes up, but it shows my device as just ?????? and I am unable to do anything. I have already tried putting in the rules thing I found all over google, and it has done nothing. The correct IDs were in as well. On Windows, why I try to use it... it pops up with a command prompt screen for a split second and does nothing. On both Ubuntu and Windows, when I try to use a virtual device, all it does is crashes. This is with all different settings. So, is there anyone that can help me out with these issues? I just spent 3 hours of google searching to no avail. None of the fixes or anything I have found made any difference. Well... that's not true... one of them made DDMS not work at all... but that just needed to be restored. Any help would be appreciated. Thanks!
Update: Doesn't work on the gf's laptop either which is running on Windows XP. So, it doesn't work on Ubuntu, Windows 7, or Windows XP. Wtf does this run correctly on?
Hi,
I'm using latest froyo/eclair on nand, but have problems with adb and windows 7 x86. I've installed latest android sdk, connected my kaiser and then installed drivers. I can connect with adb but it disconnects and reconnects all the time. I cannot even install app or copy files. The same situation is on my second win7 installation.
This is rather not android build problem, but windows, because on the same laptop with ubuntu, adb works without such problems.
Anyone have some workaround for this? Maybe there should be other drivers used?
Same thing happens to me. It happened with his eclair build also. I wonder if it has to do with background processes running. I reinstalled froyo and nothing so far. Before I used to get the charging light go on and off all the time killing my battery.
Actually this happens on XP also, and has happened on every build I have used, I'm sure it's a driver or even hardware issue.
Since I very rarely use adb it's never really been an much more than an occasional annoyance.
I'm expecting to get a G1 delivered in the next few days, so I may be able to check the whole driver/hardware aspect in more depth.
My own workaround for this is simply to use an SD card reader and adaptor for moving files around between phone and computer, actually I find this almost as fast as adb, considering the time taken to set up adb, enter the commands, etc.
zenity said:
Actually this happens on XP also, and has happened on every build I have used, I'm sure it's a driver or even hardware issue.
Since I very rarely use adb it's never really been an much more than an occasional annoyance.
I'm expecting to get a G1 delivered in the next few days, so I may be able to check the whole driver/hardware aspect in more depth.
My own workaround for this is simply to use an SD card reader and adaptor for moving files around between phone and computer, actually I find this almost as fast as adb, considering the time taken to set up adb, enter the commands, etc.
Click to expand...
Click to collapse
It's not hardware issue,but rather windows drivers. Like I wrote earlier - it works ok on ubuntu...
voyteckst said:
Hi,
I'm using latest froyo/eclair on nand, but have problems with adb and windows 7 x86. I've installed latest android sdk, connected my kaiser and then installed drivers. I can connect with adb but it disconnects and reconnects all the time. I cannot even install app or copy files. The same situation is on my second win7 installation.
This is rather not android build problem, but windows, because on the same laptop with ubuntu, adb works without such problems.
Anyone have some workaround for this? Maybe there should be other drivers used?
Click to expand...
Click to collapse
Same problems for me with the Polaris.
Anyone this working with windows 7 x86?
I've given up trying to get it to work on both my machines, I get buy with the sdsplit app
Hi All,
I have been unable to get my oppo n1 (CM edition) to connect to my home PC (win8 x64). This is annoying as my work PC (also win8 x64) detected and interacts fine with the MTP end point on the phone when connected via USB cable.
Could someone take a look at their drivers when their phone is connected and if possible zip them up for me? i would grab the ones from my work place but it just when friday afternoon and i cant believe this is such a hassle for me.
for the record, my home system currently detects the oppo as USB\VID_22D9&PID_2764\58E10EA
all the other drivers i have found are either for the ADB end point or some other PID.
no, secure boot is too much hassle as wrangling inf files can wait till monday i guess.
TIA to anyone that responds.
ms_comp_mtp
welp i think i have traced this down to a strange fault in just my own PC.
tested my oppo on a win7-x64 machine - installs fine.
I am comparing the setupapi logs to see any divergences and have found one.
my win8 box windows is not "seeing" the usb\ms_comp_mtp "compatible ID" (this is the magic that allows one driver to match many different VID/PIDs, thus a generic MTP driver should work for anything that advertises it self as MTP).
Now for the hard question of why that isnt being sent/seen by my box...
also to add to the mystery - PTP mode works fine, just MTP gives me grief.
While my own journey is far from over, ive learnt the C:\windows\inf\setupapi.dev.log file is quite useful for assisting in figuring out what isnt working when it comes to device driver installations.
I am happy to have a mod close this off, given this problem appears isolated to just my machine.
Has anybody gotten the Sony's official usb drivers to work? Its somewhat mandatory for xperifix et all.
I tried it on 2 completely different machines.
On win7 x64 box the driver complains about Error 10 - This device cannot start.
On a win10 enterprise thinkpad the error is similar:
"This device cannot start. (Code 10)
The specified request is not a valid operation for the target device."
I am starting to suspect that the drivers are faulty. FWIW the thinkpad has NEVER seen *ANY* adb/android/sony drivers before.
This is the "Sony sa0118 ADB Interface Driver" btw. Installed as a legacy device as per Sony's instructions. Driver is already not working before a device is connected. Device is subsequently also not recognized. Device works perfectly fine in flash mode on my Linux notebook, just not both windows boxes Ive tried (sadly Windows is required for Xperifix)
You use the drivers that comes with flash tool? Those are working for me without any trouble on Win10
juandiazmora said:
You use the drivers that comes with flash tool? Those are working for me without any trouble on Win10
Click to expand...
Click to collapse
tried these and they got me a little further - but not very. On first connect of the xz2c in "blue" mode Windows said something along the lines of configuring new device: Android. So far so good. Then started xperifix, which found the device and started to get device information during which it crashed (program got stuck, no .NET exceptions or anything). Now even 2 reboots later the phone is no longer recognized, I assume xperifix somehow borked up the fastboot drivers?
PS: the constant more often than not non-working recaptchas are getting a little annoying..
The drivers have to be installed in testmode on Windows 8-10. In Windows 7 it should work "out-of-the-box". And yes, I know I'm answering to one year old question, but it could be helpfull to someone one day. Maybe.
Hi there. Sorry if I sound dumb. I'm new to this whole thing and this was supposed to be my first experience with flashing custom ROMs and stuff like that. I was planning to get ready to install LineageOS on my Nexus 7 using a Windows 10 PC. Unfortunately, things quickly went south.
My first roadblock was the tablet not being recognised by fastboot. I checked online for a bit and from what I could gather, the solution was to install the Google USB drivers using device manager. I went into device manager, right clicked my Nexus 7 in "portable devices", selected "update driver" and chose the Google USB driver I downloaded from the official Android developers website. I'm not sure if this is relevant but the tablet was in fastboot mode when I did this. From that point on, my tablet is no longer recognised and it just keeps saying "device descriptor request failed" whether it's in fastboot or normal mode, and regardless of which USB mode I choose.
I tried uninstalling the driver, factory resetting, WugFresh NRT, and using different cables and USB ports. I checked for all sorts of solutions but they either didn't help or they require an unlocked bootloader (which was the very first thing I tried to do before finding out I needed to install the driver for fastboot to recognise the Nexus 7). Does anyone here know of a solution to get this working again? I'm completely stumped on what to do.
EDIT: I tested with a Chromebook and an old Windows 7 PC I had lying around. Neither could detect my Nexus 7 and the W7 PC even said it failed to install the driver as soon as I plugged it in. It seems that the driver update screwed up my tablet somehow and I have no idea how to fix it. I really don't understand how this could have happened considering I followed Google's own instructions for updating the driver.
Does anyone perhaps have a copy of the OEM driver for the 2013 N7 Wi-Fi (flo) model? ASUS don't distribute the driver on their website anymore and I'm out of ideas.
BenSkylake said:
my tablet is no longer recognised and it just keeps saying "device descriptor request failed" whether it's in fastboot or normal mode
Click to expand...
Click to collapse
Review this thread and the solutions.
After you have fixed it, you can easily install a new custom ROM with two steps:
RESTOCK - installs USB drivers and unlocks it, latest official stock ROM
CROSS - various custom ROMs, 1-click installation, TWRP, incl root
k23m said:
Review this thread and the solutions.
After you have fixed it, you can easily install a new custom ROM with two steps:
RESTOCK - installs USB drivers and unlocks it, latest official stock ROM
CROSS - various custom ROMs, 1-click installation, TWRP, incl root
Click to expand...
Click to collapse
Thanks for the response. I don't think I'll have enough time to try this today but I might as well ask. Do any of these fixes work without needing a USB connection to a PC, or if they do, do they require adb and fastboot to work? Because if so, I won't be able to use them since my USB data connectivity is completely busted no matter what I plug my Nexus into.
k23m said:
Review this thread and the solutions.
After you have fixed it, you can easily install a new custom ROM with two steps:
RESTOCK - installs USB drivers and unlocks it, latest official stock ROM
CROSS - various custom ROMs, 1-click installation, TWRP, incl root
Click to expand...
Click to collapse
I just ran the RESTOCK 1 script and it worked wonders! My tablet's USB connectivity has been fixed and as an added bonus, my bootloader is now unlocked. I'll be continuing the process in Linux on my Pixelbook since it doesn't require any driver installations as far as I know. Thank you so much! You're a life saver!