I have an issue here that is absolutely driving me up a wall. This is further compounded by the fact that the system this is happening to, the owner is leaving to go on a trip in 3 hours. I MUST fix it by then.
This part has nothing to do with my problem, this is some background info:
I personally use an HTC Imagio, flashed with a custom ROM, and obviously on Verizon's network. I tether it and sync it with a Windows 7 x64 Ultimate laptop at home.
The issue at hand: I have an HTC Mogul on the Sprint network for a higher up exec at my company that uses it with a Lenovo ThinkPad running Windows 7 Enterprise x64.
I cannot:
Get Generic RDNIS driver to install - at all -. I have combed through every post, every thread for the entire day relating to this issue. It is further compounded by the fact that the update for Windows 7 and the Windows Device Center update will NOT install. I also tried my prior mentioned HTC Imagio on the computer, it also generates a splatted device in the device manager, that not even Windows Update can load.
I have tried running the system in a local machine admin account to bypass UAC (and even disabled UAC altogether) and even checked safe mode for duplicates/issues.
What am I missing here? I can't even get the phone to sync its data, nevermind getting the tethering to work, which is what she needs the most. The phone is able to go into the Windows Mobile connection where it shows the USB connection type, and the connect button at the bottom - it'll connect, but it will drop the connection within 10 seconds.
Does *anyone* have ANY ideas where I can go from here? I have already rebooted both systems, but unfortunately a file reset is not an option here, and I'm less inclined to believe it would since my own phone has the same issue on her laptop.
Indigo64 said:
I have an issue here that is absolutely driving me up a wall. This is further compounded by the fact that the system this is happening to, the owner is leaving to go on a trip in 3 hours. I MUST fix it by then.
This part has nothing to do with my problem, this is some background info:
I personally use an HTC Imagio, flashed with a custom ROM, and obviously on Verizon's network. I tether it and sync it with a Windows 7 x64 Ultimate laptop at home.
The issue at hand: I have an HTC Mogul on the Sprint network for a higher up exec at my company that uses it with a Lenovo ThinkPad running Windows 7 Enterprise x64.
I cannot:
Get Generic RDNIS driver to install - at all -. I have combed through every post, every thread for the entire day relating to this issue. It is further compounded by the fact that the update for Windows 7 and the Windows Device Center update will NOT install. I also tried my prior mentioned HTC Imagio on the computer, it also generates a splatted device in the device manager, that not even Windows Update can load.
I have tried running the system in a local machine admin account to bypass UAC (and even disabled UAC altogether) and even checked safe mode for duplicates/issues.
What am I missing here? I can't even get the phone to sync its data, nevermind getting the tethering to work, which is what she needs the most. The phone is able to go into the Windows Mobile connection where it shows the USB connection type, and the connect button at the bottom - it'll connect, but it will drop the connection within 10 seconds.
Does *anyone* have ANY ideas where I can go from here? I have already rebooted both systems, but unfortunately a file reset is not an option here, and I'm less inclined to believe it would since my own phone has the same issue on her laptop.
Click to expand...
Click to collapse
Try Virtual XP (Windows XP image inside Windows 7) and install ActiveSync in there. You may be lucky enough to get it to work. I had a similar issue and fixed it that way...
Yeah, I've pretty much arrived at the conclusion that there is something on the system that is blocking the install of the WMDC, and short of a Windows reload, I can't get it to work. I'd considered XP mode, but this user won't know what to do with it, it adds an extra layer of complexity that she frankly doesn't care about, and won't use.
Hello,
I read in some posts that there are some users of the Samsung Ative 500T that they are running Windows 8 Pro. I was unable to post a reply in the forum, so here is my question: How do you do it???
I tried using an existing / unactivated key for a win8 upgrade I had purchased. (The tablet is running Windows 8, BTW). After choosing "add features to Windows8" and entering the key (determined to be valid), the system would run through the upgrade process, then quit with the generic response of "there was a problem encountered".
I spent over an hour on the phone with Microsoft Tech Support - the even generated a new key, as well as running a remote repair. All to no avail.
I'm looking for suggestions or ideas as to what I need to do.
Thanks in advance for your time.
I did the same thing you did and it worked without a problem. (I had purchased an extra Win 8 Upgrade key while they were still only $39).
A couple of thoughts:
1. Did you have the tablet plugged in when you did the upgrade? If not make sure it's plugged in, and change the power setting so that the tablet won't go to sleep while it's on AC.
2. I've noticed some strange behavior with the tablet when it's docked versus undocked. When I first tried to make a recovery USB key it kept failing. After 3 or 4 tries, I removed the tablet from it's dock, and then I was able to make the recovery USB key without a problem If you have a keyboard dock, try doing the upgrade with the tablet in and out of the dock to see if it makes any difference.
3. I uninstall most of the bloat ware on this tablet including Norton. You might have a program installed that is interfering with the upgrade.
Just noticed that the Chinese site Rerede.com has finally managed to build support for the WiFi card in the Surface Pro in a build of Android-IA.
This build seems to support everything, apart from bluetooth:
Original link: I don't have rights to place URLs in as I haven't posted enough here. If a moderator can add the link here, I would appreciate it.
Original text (from Google Translate):
Code:
All along, only heard Surface Pro can run Ubuntu and Android. But never seen someone real up and running, often took a running Live CD boot to coax interface, now Rerede.com released China's first support for Surface Pro Android system. Support the Android installed on your machine up. And it can coexist with your Windows!
Working conditions:
· Touch
· Keyboard
· Camera
· Gravity sensor · WIFI
· Other
Not supported:
· Bluetooth
Compatibility:
· Support and native dual-boot Windows 8
• The need to disable Secure Boot
Data is priceless! Please make the necessary data backup before installing! We do not assume any responsibility for loss of data!
Unzip password: rerede.com
Copy the code
Preparation:
In a hard disk to free up more than 1G unallocated space, 4GB recommended
Installation:
1, decompress, burn to use UltraISO to live.img U disk
2, disable SecureBoot
3, the use of U disk boot, select the third item, manually install Android4, tips Choose disk to install Android, select the disk you want to install, I chose Surface of SSD (1),
Tips Do you want to preserve Windows and dual boot (if dual boot Windows), press Y
5 Tips Do you want to resize Windows to make more space (whether android resized), press N
6 Tips Install GummiBoot BootLoader (using gummiboot), press Y
7, when prompted Enter boot menu timeout (boot menu wait time), I chose 5
8, press Enter to install, the installation process approximately less than 1 minute.
9 After the installation is complete, unplug the U disk, enter the restart to complete the installation reproduced or quoted, please indicate from the hot community , Rerede.com
Pictures attached
That looks really nice. Hope they figure out the bluetooth as well.
JLIT99 said:
Just noticed that the Chinese site Rerede.com has finally managed to build support for the WiFi card in the Surface Pro in a build of Android-IA.
This build seems to support everything, apart from bluetooth:
Click to expand...
Click to collapse
Thanks for this, it's really working, although far from perfect. Fastest touch response on android =))
Here's the direct link to download: http://rerede.com/surface.android-ia.rerede.com.vPRC2.zip
Could you get the front Cam working?
Turns out that front cam doesn't run by default. I fixed it along with some other things like youtube playback, play store etc. It's almost perfect now
Surface 2 Pro
Has someone tested these instructions on a Surface 2 Pro ? Working ?
Unfortunatly, I have a Surface 1 Pro and encounter the following error:
FATAL: ASERTION FAILED bootable/iago/plugins/gummiboot.c:gummiboot_execute:154 'efibootmgr' encountered an error (status 100)
Gummiboot the EFI bootmgr does not install. Maybe it would be possible to install it manually.
Secure Boot is disabled, and I also tried different USB sticks and the original unmodifed Android-IA image. No success.
Current progress: managed to boot into Android-IA using Refined, which itselfs loads Gummiboot.
However the overall stability of Android-IA on the Surface Pro is not good:
- Wifi most of the time does not work. Turning it on/off does not help. Neither does it help to disable power saving features. Maybe we could try a different driver
- Sometimes when the device is not used for about 2 minutes and goes black, it cannot be turned on again. I have to hold the power button to force a shutdown.
ToniSoft said:
Current progress: managed to boot into Android-IA using Refined, which itselfs loads Gummiboot.
However the overall stability of Android-IA on the Surface Pro is not good:
- Wifi most of the time does not work. Turning it on/off does not help. Neither does it help to disable power saving features. Maybe we could try a different driver
- Sometimes when the device is not used for about 2 minutes and goes black, it cannot be turned on again. I have to hold the power button to force a shutdown.
Click to expand...
Click to collapse
What do you mean by using Refined?
how do you get this installed? When i reach the instructions to press Y if to save dual boot my type keyboard does not work. How did you proceed? Thank you.
zcrugby,
How do you get this installed? When i reach the instructions to press Y if to save dual boot my type keyboard does not work. How did you proceed? Thank you.
Click to expand...
Click to collapse
You need to use a USB hub, so that you can have you USB stick and USB keyboard attached simultaneously. This installation program does not recognize the Surface keyboard, but it does recognize a standard USB keyboard.
I, however am having a different problem. I get (almost) to the end of the whole process, after it says press enter to continue with the installation and does a bunch of stuff, but then give the following error:
FATAL: ASERTION FAILED bootable/iago/plugins/gummiboot.c:gummiboot_execute:154 'efibootmgr' encountered an error (status 100)
It was mentioned earlier in this thread, but no one seemed to shed any light on the subject. In other forums some have suggested that it was just an incompatible memory stick, but I have not tried multiple memory stick by different manufactures...
Others have suggested that you need to disable AHCI and instead run in IDE mode, but with the Surface Pro 2's woefully underwhelming BIOS, I haven't yet figured out how to disable AHCI. There's some that say that simply changing some registry keys will do the trick, but I haven't gotten that to work yet, and I don't have extremely high hope for it when I do.
Does anyone here have any thoughts about this error??? Anyone run into it who has successfully gotten it working after seeing this error? If so, how?
Thanks!
please help: Fatal Asertion Failed... (status 100)
Does anyone have any light to shine on the follow error? Please?
FATAL: ASERTION FAILED bootable/iago/plugins/gummiboot.c:gummiboot_execute:154 'efibootmgr' encountered an error (status 100)
I've detailed some of the (failed) solutions I've found on other boards/threads regarding to how to get around this error on other devices, but none seem to be the trick for getting past this error on the surface. I'm really surprised that there don't seem to be more people trying to install Android on the MS Surface... or perhaps there are, but for most people things go more smoothly. Any help our there, please?
Thinking about returning the surface if I can't get android on it. I'm really interested in a powerful tablet that can dual boot windows/android.
Quixtrike said:
Does anyone have any light to shine on the follow error? Please?
FATAL: ASERTION FAILED bootable/iago/plugins/gummiboot.c:gummiboot_execute:154 'efibootmgr' encountered an error (status 100)
I've detailed some of the (failed) solutions I've found on other boards/threads regarding to how to get around this error on other devices, but none seem to be the trick for getting past this error on the surface. I'm really surprised that there don't seem to be more people trying to install Android on the MS Surface... or perhaps there are, but for most people things go more smoothly. Any help our there, please?
Thinking about returning the surface if I can't get android on it. I'm really interested in a powerful tablet that can dual boot windows/android.
Click to expand...
Click to collapse
When you get this error, it means that efibootmgr is unable to create the boot entry but all the files are in fact in boot partition. I also received this error, but since I also had Ubuntu (well, you kind of also need Ubuntu to access Android partitions easily anyway) I used the efibootmgr in Ubuntu to manually create Android entry. This way, I'm able to select advanced boot options under Windows (created desktop shortcut) and switch to Android really easily. You should leave the Windows as default so that you might never need a keyboard attached for boot menu. If you don't want to install Ubuntu just to solve this error, you *might* get away with a live Ubuntu CD, however I never tried that.
ozkaya said:
When you get this error, it means that efibootmgr is unable to create the boot entry but all the files are in fact in boot partition. I also received this error, but since I also had Ubuntu (well, you kind of also need Ubuntu to access Android partitions easily anyway) I used the efibootmgr in Ubuntu to manually create Android entry. This way, I'm able to select advanced boot options under Windows (created desktop shortcut) and switch to Android really easily. You should leave the Windows as default so that you might never need a keyboard attached for boot menu. If you don't want to install Ubuntu just to solve this error, you *might* get away with a live Ubuntu CD, however I never tried that.
Click to expand...
Click to collapse
Hi ozkaya, this sounds really promising, and I've even kind of gotten it installed, but it was going crazy (constant nonstop scrolling to select a boot mode as if I were holding down the arrow key; ended up being like Russian Roulette booting), so I decided to clean the slate and try again, the only problem is, I keep getting this error again... As a side note, I'm not overtly familiar with Ubuntu though I do have OSX successfully running on the Surface Pro 2, but I'm using a thumb drive to boot into it.
A few follow up questions:
-Are you saying that you use grub to boot into Android rather than gummiboot?
-Would you be willing to described "used the efibootmgr in Ubuntu to manually create Android entry" in more detail?
-How exactly to you select advanced boot options under Windows & create desktop shortcut?
*sorry if any of these questions are super basic. Back in the early XP days I was fairly savvy with dual/triple booting, but windows 8 and the Surface Pro's lackluster BIOS options are completely baffling me.
Quixtrike said:
Hi ozkaya, this sounds really promising, and I've even kind of gotten it installed, but it was going crazy (constant nonstop scrolling to select a boot mode as if I were holding down the arrow key; ended up being like Russian Roulette booting), so I decided to clean the slate and try again, the only problem is, I keep getting this error again... As a side note, I'm not overtly familiar with Ubuntu though I do have OSX successfully running on the Surface Pro 2, but I'm using a thumb drive to boot into it.
A few follow up questions:
-Are you saying that you use grub to boot into Android rather than gummiboot?
-Would you be willing to described "used the efibootmgr in Ubuntu to manually create Android entry" in more detail?
-How exactly to you select advanced boot options under Windows & create desktop shortcut?
*sorry if any of these questions are super basic. Back in the early XP days I was fairly savvy with dual/triple booting, but windows 8 and the Surface Pro's lackluster BIOS options are completely baffling me.
Click to expand...
Click to collapse
1- No I'm not using grub, in fact I also tried to daisy chain grub booting gummiboot booting Android and it doesn't work. I'm using native EFI entry.
2- I don't have it written up somewhere, I did it as I was reading and trying. But basically, you first need to install Ubuntu with dual boot with Windows. Have a look at the /boot partition, you will see the gummiboot files and config files there. Then research command line parameters for efimootmgr program and create the entry for the gummiboot file in /boot partition.
3- Just use google for this one, you can select advanced startup options somewhere from the settings in Windows 8 fancy menu. You can also create desktop shortcut for this. Once you completed Step 2, you will see Windows, Ubuntu and Android entries there. Since, Windows will be default, when you would like to switch to Android, you just double tap the shortcut and select Android. In Android you just power off and next restart will be Windows again. No keyboards, mouse etc needed. I also got the front cam and youtube playback working. Only bluetooth doesn't work.
Surface Pro 2
Anyone got this to work with Surface Pro 2? I am thinking of getting one, and if it could run android, im definitely getting one!
(I don't really see the point of getting Surface 1 when the 2 is out now)
I have followed the instructions and it installed fine, and then booted to android however as soon as I reboot I can no longer run android (or fastboot/recovery) without reinstalling it all over again from USB.
The error I get from gummiboot is:
HandleProtocol (DiskIoProtocol): Unsupported
Failed to start boot image 'Android': Unsupported
I would really appreciate some help from anyone who has a better understanding of this since I couldn't find anyone with a similar problem.
(I am using a 128gb Surface Pro 1/Original)
Thanks
when turning trusted platform module on and off it works sometimes
Jacob.Halsey1 said:
I have followed the instructions and it installed fine, and then booted to android however as soon as I reboot I can no longer run android (or fastboot/recovery) without reinstalling it all over again from USB.
The error I get from gummiboot is:
HandleProtocol (DiskIoProtocol): Unsupported
Failed to start boot image 'Android': Unsupported
I would really appreciate some help from anyone who has a better understanding of this since I couldn't find anyone with a similar problem.
(I am using a 128gb Surface Pro 1/Original)
Thanks
Click to expand...
Click to collapse
I'm having the same problem over and over .. still no luck
Hello!
I have been facing a peculiar problem since last week.
When I plug in my Core, it starts charging instead of connecting as a media device/ camera, before which it used to work fine. But If i plug in my Core before booting my PC, it recognises it as a media device or camera and i can use it in the usual way. Ditto for my External hard drive.
I know it's a PC problem coz it gets detected straightaway in other PCs but this is the only PC I have and it is causing me problems as any virus that comes with it will have a free hand if i connect it during boot. or won't it? any help will be appreciated!
Core UserRob said:
Hello!
I have been facing a peculiar problem since last week.
When I plug in my Core, it starts charging instead of connecting as a media device/ camera, before which it used to work fine. But If i plug in my Core before booting my PC, it recognises it as a media device or camera and i can use it in the usual way. Ditto for my External hard drive.
I know it's a PC problem coz it gets detected straightaway in other PCs but this is the only PC I have and it is causing me problems as any virus that comes with it will have a free hand if i connect it during boot. or won't it? any help will be appreciated!
Click to expand...
Click to collapse
Try to re-install your window, and again install samsung drivers i.e, ''kies'' keep any antivirus ,in future
hope that ll work..
anup34 said:
Try to re-install your window, and again install samsung drivers i.e, ''kies'' keep any antivirus ,in future
hope that ll work..
Click to expand...
Click to collapse
Hey!
Thanks for replying but if you noticed I have mentioned its not a problem specific to Core, but is happening with my external hard drive/ flash drives too, so reinstalling kies wont help.
Nevertheless, I did update the driver for core as soon as this problem cropped up (about 3 weeks) and that didn't help
Also reinstalling windows would be the last resort. I was hoping to find something other than that.
oh btw, it's not a virus/malware/rootkit problem 'coz I DO have a licensed Anti virus up and running since I first bought this PC which should be 2 yeas now. I asked about the virus coz if i connect my core during boot, and 'suppose' my mobile has got infected by a virus since the last time i scanned it, wont the virus have a free hand till my pc boots as the anti virus will essentially scan it only after windows starts?
I have done system file check but no problem there.
I got a couple of things I 'll try before formatting my c drive like updating BIOS and running memtest for RAM. if these don't work then I 'll have no other option left
people please feel free to pitch in with any ideas which could detect the problem
had the same issue
Core UserRob said:
Hey!
Thanks for replying but if you noticed I have mentioned its not a problem specific to Core, but is happening with my external hard drive/ flash drives too, so reinstalling kies wont help.
Nevertheless, I did update the driver for core as soon as this problem cropped up (about 3 weeks) and that didn't help
Also reinstalling windows would be the last resort. I was hoping to find something other than that.
oh btw, it's not a virus/malware/rootkit problem 'coz I DO have a licensed Anti virus up and running since I first bought this PC which should be 2 yeas now. I asked about the virus coz if i connect my core during boot, and 'suppose' my mobile has got infected by a virus since the last time i scanned it, wont the virus have a free hand till my pc boots as the anti virus will essentially scan it only after windows starts?
I have done system file check but no problem there.
I got a couple of things I 'll try before formatting my c drive like updating BIOS and running memtest for RAM. if these don't work then I 'll have no other option left
people please feel free to pitch in with any ideas which could detect the problem
Click to expand...
Click to collapse
hi buddy
i had the same issue few months ago. it was frustrating. i tried everything and it failed. im using avast antivirus .i suspected that it was the cause but it wasn't. as far as i remember the problem occurred while i plugged in the core to kies and it suddenly showed the phone unrecognizable since i think its running on omkars Monster$ rom.i suspect kies sort of deleted the reg files or something of the core and it became unrecognizable. fortunately for me my windows 8 was giving some other issues so i reinstaled it completely. aaaand the problem is gone. i kept away from KIES ever since and so far no issues at all.
hope i helped.
cheers..