I have a Fujitsu P1120 touchscreen netbook. I have been trying to dual boot android with the windows xp that is on there but have had no success. I cannot seem to figure out the right way to put android on the hard drive. It keeps coming up with a grub error for invalid filesystem. I have downloaded liveandroid, android 86x. The main problem that I have is that my device doesn't support booting from usb, booting from network, or any usb external drive. So the only way I can get it to work is to manually install android but I don't know how to do that.
Can anyone help me with this please?
i have same problem , i want to install android on fujitsu p1120, but i see installation freezed, now i want to test froyo android
monedadeoro said:
i have same problem , i want to install android on fujitsu p1120, but i see installation freezed, now i want to test froyo android
Click to expand...
Click to collapse
i have tried everything that I can think of besides, network installation. I can't figure out how to set up the server to do it.
How version android x86 work in lifebook p1120?
The touch screen work in android?
I see the information about touch....
http :// ariescomputing .com/lifebook/
I so happy now.. i found one dvd-rw usb work very fast in the my fujitsu...
Is liteOn Slim USB (have 2 usb) dvd-rw and the bios work..
To put it bluntly you're trying to get your netbooks to do something it isn't intended to do. Those thing are built with the absolute bare minimum to do pretty much nothing more than browse the web, hence "netbook". It's not a full PC. Even the newer ones don't run a full version of Windows 7. Short of knowing how to re-write a BIOS image or finding a modified one and flashing it, which has the risk of perma-bricking your computer.
Волк,
Sorry my bad english..I have a good computer, phone and tablet. However I like to modify my old electronics giving new life to them .... Now for example I'll replace the HDD Fujitsu Lifebook P1120 IDE for SSD and I'll put a PCMCIA card with internal memory to speed up Windows. I installed windows 7 and it is working. So I had to make a modification in winsetup.dll to install.
At the moment I install Android but I am having difficulties.
I just got my SNS yesterday and it's my first android phone (was previously using an LG cookie) First thing I did was try to root it, and I seemingly succeeded, or so I thought. It looks like it's rooted and the superuser apps there but I can't install apps using any of the guides I find or even update to 2.3.2 (keep getting and error 7 msg). When I try to install using APKInstaller it tells me it can't find the device, which I think is the problem.
I think the problem is that someway or another windows 7 64 bit stopped recognizing my phone as a Nexus S and now recognizes it as a portable device in device manager (There's also an Android Phone, with an Android Composite ADB interface) I used the SDK to install all the updates available including the google usb driver rev. 4. I tried updating the Portable device driver using the google usb driver but windows keeps it as a WPD Filesystem Volume Driver. Also I noticed when I checked to see if adb gave me a serial number for the phone using the cmd prompt commands in the rooting guides it comes up blank.
I used usbdeview to delete everything seemingly related to Android, but everytime I reconnect the phone it, installs the drivers for the portable device.
I need help to make windows recognize the phone as a nexus s again so I can update and install apps and games etc. If anybody out there can help i'll really appreciate it. Explain the steps to me as if you were talking to a child, leaving nothing out plz. Thanks for any assistance.
I live outside the US (no android market) and would hate to think I messed up and expense phone purchase in just one day
Not quite sure where to start. But my intuition tells me its the Windows 7 64-bit and drivers that's not playing along. You might want to google if other users are having trouble with W7 64-bit with Android drivers. Otherwise, find another computer and repeat the steps. If not, flash a custom ROM to see if that eliminates the problem. You haven't damaged your phone. Don't worry.
just install directly from android market website
Sent from my Nexus S using XDA App
I assume you mean instal the update from the market (which I can't do because I don't have wifi)?
I managed to get the adb to list a device number after I installed java x32 & x64 bit. I still can't install apps or get the update to work, but I'll try unrooting and then rerooting my phone as see how that goes.
Oh, I haven't done the initial sign into gmail thing yet in case that makes any difference
Edit: god I feel stupid. I didn't realize that I had to upgrade from 2.3 to 2.3.1 and then to 2.3.2. I did that an everything upgrade without any problems. Now just got to figure out how to install apk's and I'm golden
Edit 2: Ok, I figured everything out and now i'm up to date with updates and I can install apps and games. Oh Happy Day Thx for all the help
Hi guys !
I wanted to know whether the new Samsung Galaxy Tab 3 10.1 can run Windows 8./LINUX !!
Theoretically it shouldn't be too hard as it has an Intel Atom x86 processor and it shares a lot of it's specs with the Acer Iconia w510 and other tablets running Windows 8
Can you please tell me some of the issues that we may have to deal with ?
Like we will have to do something with the bootloader to make Windows 8 bootable and things like that :/
And please if you want to say something like -Why do you want to run windows on an Android tablet-
XDA is about modding. A new OS will not hurt anyone AFAIK.
What are your ideas ? I think it can be done but what will we need to do ?
Now we will be concentrating on Linux. it Will be easier.
Please use this thread for discussing Linux on the Samsung Galaxy Tab 3 10.1
Thanks for reading !
Nitro_123 said:
Hi guys !
I wanted to know whether the new Samsung Galaxy Tab 3 10.1 can run Windows 8.
Theoretically it shouldn't be too hard as it has an Intel Atom x86 processor and it shares a lot of it's specs with the Acer Iconia w510 and other tablets running Windows 8
Can you please tell me some of the issues that we may have to deal with ?
Like we will have to do something with the bootloader to make Windows 8 bootable and things like that :/
And please if you want to say something like -Why do you want to run windows on an Android tablet-
XDA is about modding. A new OS will not hurt anyone AFAIK.
What are your ideas ? I think it can be done but what will we need to do ?
Thanks for reading !
Click to expand...
Click to collapse
much like apple windows 8 is closed source. Thats pretty much the end of the thread. Without a way to compile, edit the operating system and know what changes your making its just not a undertaking many will accept.
@trevd Do you have anything to say about this ?
@wranglerray I'm just talking about installing windows to a device. AFAIK no compiling/editing will be needed. There are other tablets out there that do the same thing so why not this one ? The only major hurdle I see is making some kind of a custom bootloader that can boot the windows stuff instead of the android stuff. THAT part will probably need to be made from scratch or it may be ported from a similar device.
There are quite a few devices like this that run windows with similar specs so why not this one ?
Nitro_123 said:
@trevd Do you have anything to say about this ?
@wranglerray I'm just talking about installing windows to a device. AFAIK no compiling/editing will be needed. There are other tablets out there that do the same thing so why not this one ? The only major hurdle I see is making some kind of a custom bootloader that can boot the windows stuff instead of the android stuff. THAT part will probably need to be made from scratch or it may be ported from a similar device.
There are quite a few devices like this that run windows with similar specs so why not this one ?
Click to expand...
Click to collapse
well quite honestly your talking about porting windows to a device. Our device comes with android and you want to port windows to it instead. So on our device there are parititons chuncks of data of varying sizes allocated to hold a small part of the code that runs our phone. from ramdisk to the radio. The issue on its surface, we dont know how that partition table lines up with a different device.(which the partition table can and most likely is, completely different) and because winodws 8 is closed source we dont know how it boots, or how to edit the imstaller to ensure the os gets copied over the correct partitions. if porting were as easying as just flashing what ever you want and then changing some things to tweak it i'm sure you'd see hundreds of ports in a day or two. Unforntatley it really kinda sucks
The partitions are the biggest problem. We could in theory also boot from the SD card and as a result bypass all the android stuff and get it dual-booting but first we need to know how we can boot windows
Nitro_123 said:
@trevd Do you have anything to say about this ?
Click to expand...
Click to collapse
Hi There
I've not got a device in my hands yet to be able to give a proper device focused opinion on this.
but since you ask, I will say It really all depends on the bootloader setup on the device and how accessible that is, it could well be a proprietary Samsung Design in which case I wouldn't want to "mess" with it unless you had a JTag handy for when s**t goes wrong, otherwise you'll be holding a very expensive brick.
Even without bootloader access theoretically you could create a 3rd stage bootloader ( possibly Grub2/uboot ) which sits in place of the kernel in the boot image ( or recovery image ) , this would give the Option to load android or chainload into the windows boot manager, this is how things are done on classic x86.
If you have to go with a 3rd Stage Loader then the first steps is to get your own code running instead of the Standard Kernel Initialization inside an android boot image, There's all sorts of fun to be had after that as basically you'd need to place things in memory where the Kernel or the Boot Manager is expecting to find them amongst many other things.
Standard Windows 7/8 Installations setup a "hidden ( not assigned a drive letter in windows) " 100MB NTFS partition which contains the bootmgr.exe ( TRIVIA : boot manager replaced NT LOADER ( NTLDR ) which was used by Windows XP ). The boot configuration datafile ( BCD ) contains the settings for loading the actual operating system.
I wouldn't be too concerned about the closed source nature of Windows as there's still plenty of folks doing some absolutely bonkers **** with Windows/Windows Booting. Check out http://reboot.pro if you want to see some of that. My favourite is the 10MB WindowsXP that boots cmd.exe and nothing else LOL WAT!?! . I'm not saying you'll find the answers there but I'd consider it the "state of the art" when booting windows in unusual ways.
Without getting too far ahead, if you did get it booting then it appears the Asus Memo Pad FHD 10 which is a windows 8 device has the same SOC so I would expect there to be driver support already present ( or available ).
Additionally I've not even considered UEFI and how that would affect the whole scenario as I've not delved into the UEFI chaos yet.
Personally I've not used Windows in anger for a couple of years and I've only booted Windows 8 in VM's just to have a look, so my "WindowsFu" is getting a little rusty.
In Summary : Technically Possible ( anything is possible ) - All depends on the bootloader and how much you want it! and to paraphrase @wranglerray "If it was easy, everyone would be doing it"
Trevd
@trevd @wranglerray Thanks so much for the input
This shouldn't really be too hard to do for an experienced dev IMO but I don't have mcuh experience with all this stuff
The stuff that has been done to the HD2 was a lot harder I think but Cotulla still managed to make a custom bootloader and boot WP7 things like that
Thanks again for the comments
@wranglerray @trevd
http://forum.xda-developers.com/showthread.php?t=2540480
Please read the above link
basically we can now understand what the partitions are and what they do
Is it really that hard to make some kind of a zip file that can be flashed in recovery to boot the windows 8 bootloader ?
Why can't we just install an image of windows 8 to the SD card and boot off it ?
What do I need to know in order to understand and try to make this work ? Since no one is developing for the tab 3 10.1 I thought I'd give it a try
Nitro_123 said:
@wranglerray @trevd
http://forum.xda-developers.com/showthread.php?t=2540480
Please read the above link
basically we can now understand what the partitions are and what they do
Is it really that hard to make some kind of a zip file that can be flashed in recovery to boot the windows 8 bootloader ?
Why can't we just install an image of windows 8 to the SD card and boot off it ?
What do I need to know in order to understand and try to make this work ? Since no one is developing for the tab 3 10.1 I thought I'd give it a try
Click to expand...
Click to collapse
As a newbee I will guess:
Windows can take a bigger effort.
Runing Linux natively, easier. Android drivers should be already Linux Compatible. Tweeking them under Linux I do not know. My best guess is looking how to make grub to run first for dual booting. Or even better, Create a partition on external SD forl Linux, To be safe on TWRP recovery add a bottom to boot Linux or even esier re-use one temporary to test posibility.
Good Luck.
dale_para_bajo said:
As a newbee I will guess:
Windows can take a bigger effort.
Runing Linux natively, easier. Android drivers should be already Linux Compatible. Tweeking them under Linux I do not know. My best guess is looking how to make grub to run first for dual booting. Or even better, Create a partition on external SD forl Linux, To be safe on TWRP recovery add a bottom to boot Linux or even esier re-use one temporary to test posibility.
Good Luck.
Click to expand...
Click to collapse
@dale_para_bajo EXACTLY my friend. You stole the words right out of my mouth
Objective: Get Linux booting. SD card way is better.
Any updates on this?
SharpnShiny said:
Any updates on this?
Click to expand...
Click to collapse
It will never happen, the firmware isn't compatible.
calden74 said:
It will never happen, the firmware isn't compatible.
Click to expand...
Click to collapse
Yeah I've looked a bit more into it since, I think the best chance was Windows RT, and that isn't downloadable I believe, so that's it. Thanks for the reply though.
SharpnShiny said:
Yeah I've looked a bit more into it since, I think the best chance was Windows RT, and that isn't downloadable I believe, so that's it. Thanks for the reply though.
Click to expand...
Click to collapse
Even if Windows RT aka an ARM optimized ISO, was downloadable, it COULD NOT be used on Tab 3 10.1
Because this Tab doesn't have an ARM CPU, it have a x86 (32Bits) CPU. So better get a x86 ISO. I also got the same idea (like many other Tab 3 10.1 users). But the dream is NOT going anywhere. Also, Android apps are honestly BAD OPTIMIZED for this CPU ! That's why the Tab lags.
I sold mine and have bought a Tab 7.7 w/ SuperAmoled HD Screen but I broke its screen and can't now find any replacement in my region
Our best chance would be:
Ability of instally Windows 8 into a single .IMG file like Windows XP has been installed !
However, QEMU and KVM refuses to install Windows 8 into a VM idk why !
The RAM of the Tab is also a bit low to run Windows 8 inside Android.
If only a Great Dev could port or create "The Multi-boot bootloader" for Tab 3 10.1 as done on Nexus 7, then I won't waste my money buying a Windows 8 Tablet again since I would manage to install Windows 8 natively, whatever happened !
Sent from my roomate's computer
Can this work?
trevd said:
Hi There
I've not got a device in my hands yet to be able to give a proper device focused opinion on this.
but since you ask, I will say It really all depends on the bootloader setup on the device and how accessible that is, it could well be a proprietary Samsung Design in which case I wouldn't want to "mess" with it unless you had a JTag handy for when s**t goes wrong, otherwise you'll be holding a very expensive brick.
Even without bootloader access theoretically you could create a 3rd stage bootloader ( possibly Grub2/uboot ) which sits in place of the kernel in the boot image ( or recovery image ) , this would give the Option to load android or chainload into the windows boot manager, this is how things are done on classic x86.
If you have to go with a 3rd Stage Loader then the first steps is to get your own code running instead of the Standard Kernel Initialization inside an android boot image, There's all sorts of fun to be had after that as basically you'd need to place things in memory where the Kernel or the Boot Manager is expecting to find them amongst many other things.
Standard Windows 7/8 Installations setup a "hidden ( not assigned a drive letter in windows) "* 100MB NTFS partition which contains the bootmgr.exe ( TRIVIA : boot manager replaced NT LOADER (* NTLDR ) which was used by Windows XP ). The boot configuration datafile ( BCD )* contains the settings for loading the actual operating system.
I wouldn't be too concerned about the closed source nature of Windows as there's still plenty of folks doing some absolutely bonkers **** with Windows/Windows Booting. Check out httpdouble slash)reboot(dot)pro if you want to see some of that. My favourite is the 10MB WindowsXP that boots cmd.exe and nothing else LOL WAT!?! . I'm not saying you'll find the answers there but I'd consider it the "state of the art" when booting windows in unusual ways.
Without getting too far ahead, if you did get it booting then it appears the Asus Memo Pad FHD 10 which is a windows 8 device has the same SOC so I would expect there to be driver support already present ( or available ).
Additionally I've not even considered UEFI and how that would affect the whole scenario as I've not delved into the UEFI chaos yet.
Personally I've not used Windows in anger for a couple of years and I've only booted Windows 8 in VM's just to have a look, so my "WindowsFu" is getting a little rusty.
In Summary : Technically Possible ( anything is possible ) - All depends on the bootloader and how much you want it! and to paraphrase** @wranglerray "If it was easy, everyone would be doing it"
Trevd
Click to expand...
Click to collapse
I am new to the forum but not windows and android though not advanced but do you think that getting those files in the 100mb partition and making an ext2 image of them with slight modifications to fit in the architecture and flash the image as a recovery image?
or perhaps we could use rom manager and by creating a virtual rom composing of windows and boot them via the rom manager tool.
or perhaps we could use grub or a similar tool to boot into an image file or sdcard with windows installed on it and flash the grub files onto the recovery partition but some one with advanced info please confirm all these possibilities!
________________________________________________________________________________________
Hit thanks if I helped, its not that tough
Go ahead guys !
This thread is becoming IRRELEVANT !
Tab 3 was made to run Android (and possibly Ubuntu since Android is a mobile version of Linux) but NOT Windows !
So just use Android or Nothing.
Sent from my roomate's computer
yes but
Nonta72 said:
Go ahead guys !
This thread is becoming IRRELEVANT !
Tab 3 was made to run Android (and possibly Ubuntu since Android is a mobile version of Linux) but NOT Windows !
So just use Android or Nothing.
Sent from my roomate's computer
Click to expand...
Click to collapse
Yes, but since both Windows and any x86 Linux are designed for the same architecture, shouldn't we be able to boot Windows?
glorified sd card
Dani515 said:
Yes, but since both Windows and any x86 Linux are designed for the same architecture, shouldn't we be able to boot Windows?
Click to expand...
Click to collapse
i think it's possible
check this out starting at angel_666's post #18
http://forum.xda-developers.com/showthread.php?t=2589370&page=2
finding out where the flag checking starts and finishes would probably make the third stage boot
more realizeable. i directly flashed both grub and then plop to recovery block and got nowhere,
so it's mmcblk0boot0 or mmcblk0boot1, i haven't found anything in param===>/dev/block/mmcblk0p16 yet
and if p5210 has the little kernel burnt onto the chip setup, from my understanding of what i've
read it's a really basic/small/simple setup so even if the flag was there and unchangeable we should
still be able to get past it somewhere else, right?
Really ?
Dani515 said:
Yes, but since both Windows and any x86 Linux are designed for the same architecture, shouldn't we be able to boot Windows?
Click to expand...
Click to collapse
I firstly got this idea and have posted here on XDA about it :good:
Look at this thread http://forum.xda-developers.com/showthread.php?t=2682603
However, mine was about running Windows 8 inside Android
Sent from my roomate's computer
Done already?
Hello,
I have found this thread: http://forum.xda-developers.com/showthread.php?t=2070139
If you read further, you can find almost complete solution for archlinux natively on Note 10.1. WIth multiple fixes/scripts. Any reason why it cannot be done on tab3 10.1? I'm asking because I might try to compile proper kernel and prepare some distribution as tablet provides power that ends up completely wasted by android.
Hi there,
I finally decided to root my Note Pro (P900), which is just 10 Days old (refurbished tho, so no warranty issues).
My Backstory (only read if you are bored
The main Reason for me is privacy. Coming from a Xiaomi Android Device with its excellent Permission Manager I was shocked at the Permissions some Apps require, that cannot be changed.
I did my research and tried a relatively unknown option named "Appguard". (Google actually removed it from the PlayStore after a short period of time, still available from their Website). This app was developed by a IT Professor at a german university with the help of his students. It allows to manage app permissions on the fly for installed apps and doesn't require root. However, this requires to reinstall the apps you want to monitor (no big deal) and it also allows apps to get PlayStore upgrades (great!). However as it functions without requiring root, there is no way to monitor system apps (including all the Samsung bloatware!).
I did further research and am now opting for the xPrivacy Plugin for the Xposed Framework.
This of course requires root to function. So here I am.
My device is a stock, unrooted P900 Wifi (32 GB) currently running 4.4.2 (KOT49H.P900XXUANI1). And, I'm on a Mac!
Bummer!
I understand that the current setup to gain easy root is using Odin on a windows machine (wich i dont have!)
I did some more research and found Heimdall. Its a multi platform tool that allows flashing Samsung devices.
Did anyone already try Heimdall and can maybe give me a hand on setting it up?
Does it even work with the P900?
Any other Methods rooting the P900 on Mac OSX?
Thanks a lot in advance!
For times when I need to use Odin I use windows in a VMWare virtual machine on my macbook. The VM image takes up precious SSD space on my rig though so when not in use I'll copy over the image to removable storage to free up space and then copy it back to the macbook when I need it.
Thank you for your reply.
Ive done some tinkering in the Meantime and it seems like at the moment there is no possibility for the P900 using Mac OSX.
There are actually two options (or one technique used by two programs). Both of them are open source, available for Windows, Linux and Mac and can be found on github.
One is Heimdall, which seems to work fine for older Samsung devices and actually uses a special kext to replace the samsung drivers on Mac OSX. It comes with a command line tool as well as a straight forward user interface.
The other one is JOdin3, a Java/Casual based program that can be used directly in the browser or downloaded and run as a java program. It also uses the Heimdall drivers, but offers a user Interface that looks and functions exactly like Odin, plus it inludes a "noob friendly" step by step process in the UI.
The problem is that the heimdall drivers are still having issues with newer samsung devices (including the note pro) preventing it to fetch the PIT file from the device.
As of now, April 23rd 2015 there is currently no way to root your device using Mac OSX
I'm currently downloading a virtual windows machine in virtualbox and will try to root that way.
I have no Windows license, but thanks to the Internet Explorer Team from Microsoft you can download already complete virtual Windows Enviroment for both OSX and Linux directly from the windows servers. For free!
Will report back once I rooted my device.
I successfully rooted my P900!
For those Mac Users out there interested:
I tried Virtualbox first, but it didn't work. I installed the exact same windows image (Win7 Enterprise) with VmWare Fusion and was able to detect my device using Odin with the latest official Samsung drivers.
I used Odin (v. 3.10.6) to flash TWRP Recovery (v. 2.8.6.0). You have to boot directly into recovery after flashing, otherwise the OS will revoke the custom recovery at the first boot.
I then used TWRP recovery to flash SuperSU (v. 2.46) from a USB Drive and made a full backup to the ext. SD card.
Currently downloading the Hyperdrive custom rom. Really looking forward to it.
Did you end up tripping KNOX?
Keep us posted on your progress.
KNOX will be tripped when you install a custom recovery via Odin.
So yes, my KN0X has been tripped.
I'm currently running the Hyper drive Rom with different kernels. Performance seems good and customization Options excellent. l have a problem with random shutdowns (not reboots), no matter what kernel l use.
Pretty sure It's related to the Rom setting/ Setup rather than root method. Some users of the Hyper drive Rom reported similar issues,' however l have to figure this out before university starts again on monday and i absolutely need the tablet for lecture.
If I dont find a solution for the shutdowns until sunday i might have to consider flashing stock + .Xposed
Hello Guys,
I have a Hilti Laser PD-C device that runs:
android: 4.1.2
build: sparky_silver_2.3.15
I want to note that all apps should be arm not x86 but Im not sure of the DPI.
This runs a special modified Hilti rom. I would love to be able to get a custom rom and add more apps. I am willing to toss some donations for this. Has anyone done anything with this device before?
**** Update: ****
I was able to get root access via PC version "KING_ROOT"
http://king.myapp.com/myapp/Kingroot/kingroot_pc/KingRoot_pc_en.exe
1. I downloaded the most current sdk for ADB
2. I also downloaded the Hilti update app.
www.hilti.com/updatepdc
3. I was able to use King_Root even while the app didnt see the device and it recognized the device after I clicked connect.
4. The main ROM is very difficult to get around. You cant just click an app you side-loaded. Download a launcher that matches the android version. I used smart launcher, no reason, just the first I found. Use ADB to sideload on to the device.
(adb install "app name") https://www.apkmirror.com/apk/smart...1-build-054-android-apk-download/#description
5. From here I got full control to the apps I sideloaded. I am still having issues with connecting to BT on my note9 for the internet.
It is what it is... But thanks for the help. I hope anyone else looking finds this.
https://www.hilti.com.qa/media-cano...rating Instruction PD-C , PD-CS (01) (ENEN-US)