The PIPO X9 is an awesome device- in theory.
I received mine with Android working great, and Windows stuck in a setup loop.
So I downloaded the PIPO files, but with no instructions couldn't reinstall Win10.
Researched the heck out of this machine online- found almost nothing available.
Reinstalled Windows 10 from a 32 bit USB drive, then tried Pipo's Android setup.
That hosed everything; now it reboots endlessly as though it has no OS anymore.
My error was likely in removing partitions when installing Windows, but I wanted to start from scratch and clean things up (come on, 15+ partitions? Seriously?). I can get into the EFI shell to start the Android setup again, but it throws flash errors and changes nothing. I can't get 32-bit Windows to boot from the shell at all; 64-bit Windows gets stuck at disk.sys every time. I have all the PIPO Win10 files, but still can't make them do anything at all. I can get into the bios fine too, for what it's worth. I'd much rather learn how to make this box work than just returning it and trying to find a replacement- the hardware is exactly what I need for a project.
Anyone have any thoughts or ideas to try before it gets shipped back?
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?
Odin will bluescreen XP if it's running in a VirtualBox guest, but not after sending just enough to the phone to corrupt something. If you happened to be flashing your bootloader, congratulations, you just bricked your phone. Thankfully it wasn't the bootloader I was flashing and I can still get the phone into Odin mode; I'm gonna try to recover it when I get home to my Win7 desktop machine.
Heimdall does not support the Captivate Glide yet, and I tried Odin in Wine -- it doesn't see the phone. For the time being you *NEED* a native Windows machine to root the Glide -- the usual workarounds simply don't work.
You should NEVER flash or do anything with your phone without a proper setup. Heck, I wouldn't even flash without being on a laptop (for the battery) or a comp connected to a UPS.
This is good information to know but it would be incredibly stupid to flash while using an emulated OS. If you're on Linux or Mac, go to a friends house with Windows. It simply isn't worth the risk.
Thanks for the confirmation and to everyone else-don't do it. Just do things the right way.
It's a locally hosted VM running on a laptop, so yeah, I had the battery backup
I've done this before with other devices and this is the first time I've run into an issue where the VM actually broke things enough to corrupt stuff on the phone. Every other time it's been either, it went off without a hitch, or I can't quite bridge the connection from the host to the VM. Even from a theory standpoint, hey, companies use VMs for critical server systems. There's nothing dicey about a VM, at least until you run into a weird bug like this.
It's just that in this particular case, in the particular combination of Odin, XP guest, and Ubuntu host, something goes horribly wrong insidie the VM and crashes out XP. Actually, it's worse than that -- my XP VM won't boot anymore. What the hell happened.... gotta be a bug in VirtualBox.
Oh well. Hey, that's the whole point of recovery mode, right?
Definitely just use a PC running Windows. It sounds like you know what you're doing but if you're flashing recovery or a radio image, theres no point in the extra risk. If you're just doing a ROM and already have recovery there, you should be fine because you can always drop a new ROM on the SD and reinstall from there.
I've never bricked a phone myself but I do all of my friends phones. I think the scariest I've had was upgrading WinMo on my friends old Blackjack from 5.5 to 6.5. The official flash program froze at 85% or so. I let it sit for an extra hour and was almost sure it would be bricked but thankfully once I pulled the battery on it, it booted right up to 6.5.
But things like that happening..I wouldn't even mess around with an emulated OS and pushing a flash of recovery or something. Best to just be safe and go to a friends house if you have to.
I'm curious if you would have had better results is you were using VMWare instead of Virtualbox.
I've not used Virtualbox before, but I've read that VMWare has superior performance and hardware pass-thru.
I use VMWare a LOT (like a whole, whole lot), and I've never had any sort of trouble with the hardware pass-thru.
ericpeacock79 said:
I'm curious if you would have had better results is you were using VMWare instead of Virtualbox.
I've not used Virtualbox before, but I've read that VMWare has superior performance and hardware pass-thru.
I use VMWare a LOT (like a whole, whole lot), and I've never had any sort of trouble with the hardware pass-thru.
Click to expand...
Click to collapse
I didn't have any passthrough problems with VirtualBox either... until I got this phone. It's a really oddball corner case. I wonder if Odin does something weird with the Windows USB drivers...
what i did was run parallels on mac, with a Windows 7 guest to flash rooted rom and then CWMR. now i just put the zip to flash on my sdcard which i can access fine on mac.
Hello again, I am having a bit of trouble as of right now and i would like some feedback, now a little back story, I used to be into rooting and such, always dong it for my friends and i was quite good. Then came my hiatus of about a year or so and now im back and i guess i dont remember exactly how to do this and i have screwed up a friend of mines kindle
My dilemma
I have gone in with the rooting process with kfu and i went and changed the drivers to adb and then i went into bootload and changed it to fastboot, and i have forgotten that windows frowns upon such a thing and now the kindle is stuck in a bootload at the stock booting screen of the white and red "KindleFire" and every time i connect it i get and error message saying that the device isnt recognized by windows and it is probably malfunctioning (which we all know it isnt) and i want to change it back to normal bootload but kfu wont recognize it either because of windows. I have tried to re-install the drivers to get it to be recognized as an android device again but alas that dosent seem to work either. So it would most appreciated if i could get some help on this one.
well this post can be ignored because i figured it out
If its a windows problem try running a VitualMachine of a linux distro and try using fastboot there. Or create a live usb of a linux distro and temporarily run linux on your pc.
I used this to get Ubuntu on my laptop. http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
tobiascuypers said:
If its a windows problem try running a VitualMachine of a linux distro and try using fastboot there. Or create a live usb of a linux distro and temporarily run linux on your pc.
I used this to get Ubuntu on my laptop. http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
Click to expand...
Click to collapse
well i would like to avoid to using linux but if i really have to i will
is there any possible way to do it without linux
Hey guys, I managed to run myself into a little bit of a pickle..
I have flashed the Tipsy ROM v.4.9 on my G3 D550 a couple of weeks ago, and foolishly forgot to flash the extra file that was recommended to keep the phone rooted. During the process TWRP that was previously working perfectly has vanished and now when trying to enter recovery mode it gets into a weird flickering screen and a bootloop.
Now I have tried re-flashing TWRP from my Windows 10 laptop with a thousand different drivers that I found online (uninstalling, rebooting, reinstalling etc etc), but every single time the phone is reckognised with the adb devices command, but the fastboot devices command leaves me in the cold. I have tried everything I could think of. I tries a friends laptop, also windows 10, nada. Then I tried an Ubuntu live session from my own machine, same thing. ADB working, fastboot not.
Does any of you maybe have any idea of how I could get my root and ultimately my recovery back? I am kinda stuck with this rom now, which albeit being great, is obviously not fully fleshed out yet, plus of course it cuts the option of trying out more of the wonderful work that some of you guys here do!
I would appreciate any kind of help!
Thanks!
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