ok! where to even start...
I like many got this 2in1 at wal-mart and I live it. unfortunately I like many am not yet familiar with the new UEFI bootloader bios SOC stuff
heres what I do know and please correct me if im wrong. also please tell me if this 2 in 1 is and can be flashed the same as the asus t100
ok the Flexx11 has a bayntrail-t CR quad core processor 1.33-1.83ghz model Z3735F the t100 is3740
11.6" screen ips touchscreen at 1366x768 res
Efun is the corp and yifang vers.NX1106.1.02.008\139
THE BIOS IS YFG0315009112
it is a 32bit EFI bootloader
the reason I mention all of this is I have tried several times to dualboot androoid and each time ruined the computer and had to return it and I simply no longer wish to return it and love it to much to get something else
the first try the time began to lag and was unfixable for some reason the second time i somehow lost the keys booting and formatted wrong or something and the tablet bricked it would remain black with keyboard lit and no button combo could get it back no boot at all.
I am currently using AMIDUOS to run android kitkat and I love it but from what I understand it isnt compatible with win10 and really still isnt the same as the full android being on the tablet although really really close and awesome
but honestly I have been doing this stuff for years and now with this new windows secure boot and system on a chip stuff im lost
ever get anywhere with this?
I'm curious as well.
It has to be possible. I say that because I recently owned a ChuWi dual-boot device with the same Baytrail processor and SOC.
I wonder if it wouldn't be possible to take a system dump from one of the chuwi dualboot devices and flash it to the nextbook.
Sent from my Ascend Mate 2 using XDA Free mobile app
I'm also interested in doing this. It appears that the Nextbook Ares has the same hardware (minus 1GB RAM) but has Android. I contacted Nextbook to see if I could get a copy of the Ares Android firmware but was denied. If someone with the Ares could upload a backup that would be helpful.
I was finally able to get this working using this method...
https://hitricks.com/guide-how-to-dual-boot-remix-os-with-windows-uefi-legacy
So far I was able to get it to boot from a partition on the main drive as a test. In the process of installing to a secondary partition on my sd card. We'll see how it goes.
I wasnt able to get the boot menu that he shows but after going through the steps I then had an Android OS boot option in the bios boot menu. Pretty awesome! Runs great. Tried running Dead Trigger 2 as a test with full graphics. Ran perfectly.
I just bought one of these yesterday, and it shipped with Windows 10 Home 32-bit. I'm trying to install the 64-bit version but it won't boot from USB. Turns out it doesn't support 64-bit OSes. Where can I find recovery images for this? I messed up and now I don't have audio or touchscreen drivers.
64 bit processor?
I just bought one of these yesterday, and it shipped with Windows 10 Home 32-bit. I'm trying to install the 64-bit version but it won't boot from USB. Turns out it doesn't support 64-bit OSes. Where can I find recovery images for this? I messed up and now I don't have audio or touchscreen drivers.
Click to expand...
Click to collapse
Alright, I'm slightly confused now. Looking at system specs for mine it says it has an x64 based processor. Doesn't that mean it should be able to handle 64-bit OS? Even though it comes with 32-bit? If possible I would like to put 64-bit on it as well, but I'd like to be sure that that's not going to break it.
GeneticJulia said:
Alright, I'm slightly confused now. Looking at system specs for mine it says it has an x64 based processor. Doesn't that mean it should be able to handle 64-bit OS? Even though it comes with 32-bit? If possible I would like to put 64-bit on it as well, but I'd like to be sure that that's not going to break it.
Click to expand...
Click to collapse
It just won't boot the USB. At all. Unless it's 32-bit.
rowdyrocket said:
I was finally able to get this working using this method...
https://hitricks.com/guide-how-to-dual-boot-remix-os-with-windows-uefi-legacy
So far I was able to get it to boot from a partition on the main drive as a test. In the process of installing to a secondary partition on my sd card. We'll see how it goes.
I wasnt able to get the boot menu that he shows but after going through the steps I then had an Android OS boot option in the bios boot menu. Pretty awesome! Runs great. Tried running Dead Trigger 2 as a test with full graphics. Ran perfectly.
Click to expand...
Click to collapse
I'm loving Remix OS on here with dual boot. Having some issues though and I really want this to work.
Main and I mean main issue is no sound at all, no rotation is next in line and Bluetooth isn't working. Everything else works great.
This is so awesome its like Android lollipop with windows desktop functionality. Now if I can get the bugs fixed I will be in android hog heaven.
GREAT FIND BRO!!!!! EXACTLY what I was looking for maybe even better than.
for those interested here is the XDA section for all things REMIX OS
http://forum.xda-developers.com/remix
By the way for those who may want to know I installed dual boot onto the hard drive it went with no issues.Here's some tips for flexx 11
1. I used a partition manager such as easy partition manager to partition the C: drive regardless of what the tutorial said. Couldn't use windows disk management. I deleted the recovery for an extra 5 gigs (make a backup if you do) I used about 19 gigs from the C: drive and made an E: NTFS.
2.Also do not use the remix files from that tutorial use the ones here from the main site http://www.jide.com/remixos-for-pc they are newer and the ones from the other post where incomplete. Also the newer ones on the site now include OTA updating which is totally awesome.
3. I'm hoping this will help someone..... After I was all finished I expected it to dual boot as any other dual boot restart and then i would see options for the OS's not the case here I got stuck on this I was using easy BCD and trying all sorts of stuff, once I looked at the tut a little closer I realized you don't need any of that. Once your all done do a restart and it will go back to windows as usual. Now go to settings, then recovery, then advanced startup and choose from devices I think its the second option on the left list. There you will find Android OS click that and it will take you to your dual boot options. Sounds a lot more complicated than it really is. But believe me once you know this your better off.
And that's all I've got please and I mean please post here with any fixes especially for sound and if you have questions I will try to help.
Thanks
PS: I AM GETTING OCASIONAL LOCK UPS, MEANING THE OS FREEZES AND I HAVE TO RESTART BY HOLDING POWER.
Im not sure if this is good news or not...
Using the methos outlined I was not able to get audio bluetooth autorotate and other things to work but after a bit of digging I found out that remix os has an image specifically for nextbook baaytrail (Our PC) here: http://www.jide.com/remixos/devices
click other upper left.....
I cannot find instructions to install this though and using the other install instructions from here fail because the only part of the file to replace is the system image.
I also attempted the other install methods and easy BCD does not work for this PC
So if anyone can help to install this file specifically for our computer as well as verify that it works and what works and how you installed would be great
OK this is really cool I have made headway sort of.
I have installed kit kat android-x86-4.4-r3.img using the Androidx86-Installv24-5800.exe installer and i have rotation, root and it works pretty good for the most part wifi works great so far no bluetooth, it freezes during shut down and the major issue as in most cases is the sound. Im not sure about the camera now that I think about but i will check and report back here.
I really want the sound working on this and I woud be bigtime happy this forum could be solved as far as im concerned
From what I understand there is a bug with baytrail and linux where the spp port is pointed automatically to the usb or something. but for the life of me after weeks of scouring the internet cannot find a laymens guide to a simple fix for this. I'm really not even sure there is one because I'm yet find a rock solid confirmation of a solution
Update: camera doesn't work either
So far the 4.4.3 port is the best. I just can't seem to find any help whatsoever so its looking like so close yet so far away. Its a pure shame that audio and a few other major bugs are the only things in the way of this being a fully working and easy dual boot method.
I have bought a nextbook flexx10 but am unable to install remix OS. I have followed all the steps highlighted before.
1. partitioned the drive with gparted to make a 10G NTFS drive
2. downloaded android x86 5.1.1 iso and remix iso from jide website.
3. used android installer and android 5.1.1 iso to install the image
4. used 7zip to uncompress the remix iso
5. then copied over the 4 necessary files from remix to the drive to the android drive
6. copied over grub.cfg
Now, I do see the entry for androidOS but when I select that, I just get a message at the center of my screen that says "AndroidOS boot failed" and a blue OK button in DOS like font. thats it.. I am interested in knowing if any additional BIOS settings needs to be tweaked.
furthermore, I have tried installing android x86 6.0 by formating the same partition as ext4. All proceeded well and i got to the last screen that said "Run android-x86 now" or reboot. I removed the USB and was able to get into android. (some missing functionality). But when i reboot into windows and try to boot into androis, I get the same message of Andoid boot failed..
Thus I need to know if there's some BIOS settings related to permissions or sorts that i'm missing.
thanks
murlig123 said:
I have bought a nextbook flexx10 but am unable to install remix OS. I have followed all the steps highlighted before.
1. partitioned the drive with gparted to make a 10G NTFS drive
2. downloaded android x86 5.1.1 iso and remix iso from jide website.
3. used android installer and android 5.1.1 iso to install the image
4. used 7zip to uncompress the remix iso
5. then copied over the 4 necessary files from remix to the drive to the android drive
6. copied over grub.cfg
Now, I do see the entry for androidOS but when I select that, I just get a message at the center of my screen that says "AndroidOS boot failed" and a blue OK button in DOS like font. thats it.. I am interested in knowing if any additional BIOS settings needs to be tweaked.
furthermore, I have tried installing android x86 6.0 by formating the same partition as ext4. All proceeded well and i got to the last screen that said "Run android-x86 now" or reboot. I removed the USB and was able to get into android. (some missing functionality). But when i reboot into windows and try to boot into androis, I get the same message of Andoid boot failed..
Thus I need to know if there's some BIOS settings related to permissions or sorts that i'm missing.
thanks
Click to expand...
Click to collapse
Sorry for the late reply, use the installer and create a separate drive using C: like a D: or E: and get android 4.4 the .IMG that should work for you and the installer should do everything for you.
So use the uefi android installer after you partition a drive to load android 4.4 the uefi IMG
Its just going to piss you off though because there's no audio and seemingly no way to fix it, which is a crying shame ��
P.S. typically secure boot is off in the bios on this machine, but if by any chance you turned it on or the newer ones come that way make sure it is off or this will not work.
UEFI Settings
So I can get to a menu with 6 icons (2 rows and 3 columns) by running the "shutdown.exe /r /o" command and then going to Troubleshoot>Advanced Options>UEFI Firmware Settings and clicking restart. The problem is that when I get to this menu the touchscreen and keyboard do not work, and I can only move the highlighter up and down, not left and right. Hopefully one you guys have figured this out. I contacted the Nextbook support desk and they were no help at all.
korycooper said:
So I can get to a menu with 6 icons (2 rows and 3 columns) by running the "shutdown.exe /r /o" command and then going to Troubleshoot>Advanced Options>UEFI Firmware Settings and clicking restart. The problem is that when I get to this menu the touchscreen and keyboard do not work, and I can only move the highlighter up and down, not left and right. Hopefully one you guys have figured this out. I contacted the Nextbook support desk and they were no help at all.
Click to expand...
Click to collapse
Okay. So I was able to test this one of my co workers Nextbook and it seems like its a problem with mine.
This might be beneficial for us Flexx 11 users. It's a full port of Remix 2.0 to the Ares 8 with everything working except the camera rotation issue. Very promising. I've heard the hardware is similar. Working on attempting to install on mine. Anyone else tried it?
http://forum.xda-developers.com/remix/supported-devices/port-remix-os-2-0-nextbook-ares-8-t3498015
Hey guys,
NextBook Flexx 11, 64Gb, NXW116QC264, Windows 10
I'm really interested in trying to install Remix OS in Dual boot. However, in my trials, I goofed up my tablet. I found an image, but it turned out to be a Windows 8.1 image, and it wiped everything from my tablet. I had originally had Windows 10 on it.
Could someone perhaps be able to send me the recovery partition of their Nextbook; as long as they had Win10 installed. Maybe if I dump a Win10 recovery partition, I can do a repair on it and restore Win10 to the system.
I can't find the stock/factory rom for the Win10 version of the Flexx.
Thanks in advance,
Kori
KorishanTalshin said:
Hey guys,
NextBook Flexx 11, 64Gb, NXW116QC264, Windows 10
I'm really interested in trying to install Remix OS in Dual boot. However, in my trials, I goofed up my tablet. I found an image, but it turned out to be a Windows 8.1 image, and it wiped everything from my tablet. I had originally had Windows 10 on it.
Could someone perhaps be able to send me the recovery partition of their Nextbook; as long as they had Win10 installed. Maybe if I dump a Win10 recovery partition, I can do a repair on it and restore Win10 to the system.
I can't find the stock/factory rom for the Win10 version of the Flexx.
Thanks in advance,
Kori
Click to expand...
Click to collapse
Just to be clear...(and this goes for everyone wondering in the future) it was windows 10, from the factory??? Last i checked
they only shipped with windows 8.1 or android, depending on the model...If not and you put windows 10 on there, back when it was free, you just use the media creation tool from Microsoft to update windows 8.1 to Windows 10 (after restoring windows 8.1)... it can do this because most tablets have unchangeable hardware, so no cd key is required...it's like how your md5 hash verifies your downloaded files, Windows provides Microsoft with your hardwares md5 hash signature and if it is in the list, then it activates the pc/tablet... but, it only works if you got it free, not if you bought it... if you bought win10 then you will need your cd-key when you re-install, while the other steps are same as above... just note, that for the free upgrade there was NO cd-key, therefore in that instance, if it asked you for a key, you would leave it blank, which you can do in any case, and add your key in from Windows if needed...
And... as for the others having sound issues in Android, I read something about a reason for that having to do with something called an... 'audio stack', I think it was??? Not 100% sure what it meant, but basically, it is designed so the audio hardware only works in windows, I think... (so they can make more money, by making you buy the android tablet separately...)
hope this helps someone who stumbles upon this thread...
Wiebenor said:
Just to be clear...(and this goes for everyone wondering in the future) it was windows 10, from the factory??? Last i checked
they only shipped with windows 8.1 or android, depending on the model...If not and you put windows 10 on there, back when it was free, you just use the media creation tool from Microsoft to update windows 8.1 to Windows 10 (after restoring windows 8.1)... it can do this because most tablets have unchangeable hardware, so no cd key is required...it's like how your md5 hash verifies your downloaded files, Windows provides Microsoft with your hardwares md5 hash signature and if it is in the list, then it activates the pc/tablet... but, it only works if you got it free, not if you bought it... if you bought win10 then you will need your cd-key when you re-install, while the other steps are same as above... just note, that for the free upgrade there was NO cd-key, therefore in that instance, if it asked you for a key, you would leave it blank, which you can do in any case, and add your key in from Windows if needed...
And... as for the others having sound issues in Android, I read something about a reason for that having to do with something called an... 'audio stack', I think it was??? Not 100% sure what it meant, but basically, it is designed so the audio hardware only works in windows, I think... (so they can make more money, by making you buy the android tablet separately...)
hope this helps someone who stumbles upon this thread...
Click to expand...
Click to collapse
I realize this is a dead thread, but I had to chime in... I bought my NextBook Flexx 11 from Walmart 3 or 4 years ago and it shipped with Windows 10 Home, not Windows 8.1... However, IMHO, Windows 10 is a resource hog on this little device. I'm currently looking in to installing Linux...
Related
Important - Read First!
First of all you must know that everything you do is on your own risk. Your device was not designed to run GNU/Linux or Android and that's why you shouldn't expect everything to be perfectly safe. If you don't want any troubles then simply don't tamper with your phone. On the other hand, installing Rhobuntu is probably less dangerous than installing alternative ROM's, because it doesn't touch your ROM and runs completely from the SD card. If something goes wrong and the system would hang up, you always can remove the battery and boot into Windows Mobile. Still, we can't guarantee you anything and we won't be liable for any damage that might happen to your device. If you don't accept this, don't install Rhobuntu.
At the moment two problems are known to occur when using Rhobuntu. They are, however, not Rhobuntu specific and may also occur when using Android.
1- After booting back into WinMo, you can't install or run unsigned apps. This problem probably has something to do with the way haret kicks WinMo out of the RAM. It also seems to occur only in combination with the use of Exchange Server. The only known solution at the moment is Hard Reset. Some users also reported that it can be fixed by using Visual Studio 2008. Check out this threads:
o Not digitally signed with a Trusted certificate/ Activesync keeps UNINSTALLING!
o Program... is not digitally signed with trusted certificate. HELP!
2- Since we still have no proper battery charge indicator working, you might not notice that your battery is completely drained. Deep discharge is, however, not good for batteries and may in some cases even damage them. Here is a thread dealing with this problem when running Android
o Android killed my USB connection, please help
The majority of Rhobuntu users doesn't face these problems, but just in case, you've been warned.
WIKI http://wiki.xda-developers.com/index.php?pagename=RhodiumUbuntu
WEBSITE https://sites.google.com/site/rhobuntu/
This build by Walter79 and the Rhobuntu team:
Rhobuntu 9.04 19.09.2010
changelog:
- zimage update (Xandroid Build 16/09)
- sphone 0.04 (thanks AmiPro)
- 3G scripts update (thanks AmiPro)
- sound works partial (thanks to phhuson) !!! run /sdcard/ubuntu/playwav2 after boot !!!
- alsaplayer added
Download:
Link1: http://www.megaupload.com/?f=RWDJWUN0
Link2: http://rhobuntu.4shared.com
Debian Squeeze Test 19.09.2010
For more information please look at this post http://forum.xda-developers.com/showpost.php?p=8186181&postcount=1208
Download:
link1: http://www.4shared.com/dir/n-2ObqP_/pro2-debian.html
Old Build (27/06/2010)
*http://www.megaupload.com/?f=RWDJWUN0
*http://rhobuntu.4shared.com
Old Build (13/05/2010)
*http://www.megaupload.com/?f=RWDJWUN0
*http://rhobuntu.4shared.com
Old Build (14/04/2010)
*part one:http://rapidshare.com/files/375930803/Jaunty_14_04_2010.7z.001 MD5 77430e728bb17277e671cc55ae03161f and part two: http://rapidshare.com/files/375939439/Jaunty_14_04_2010.7z.002 MD5 523589000dcd5d1dcea668bbe51253af
* http://rhobuntu.4shared.com
* http://www.megaupload.com/?f=RWDJWUN0
Old Build (11/04/2010)
* http://rs427.rapidshare.com/files/374730149/Jaunty_11_04_2010.7z
* http://rhobuntu.4shared.com
* http://www.megaupload.com/?f=RWDJWUN0
Old Build (10/04/2010)
*http://rapidshare.com/files/374138895/Jaunty_10_04_2010.7z
*http://rhobuntu.4shared.com
Pretty cool idea, keep us posted!
Definitely an awesome idea, and one I had been thinking about myself since my original Touch Pro days. An embedded version of Linux should run great on these devices. Hopefully momentum will grow surrounding this.
thats very interesting. any pictures of this running? maybe things can be pulled from android.
THANKS!!!! downloading now!
tried it on my Touch Pro 2 (AT&T Tilt2), No luck. Started to boot, Complained about /etc/init then poof reboot after 7 seconds. Am I missing something.
aq3e said:
tried it on my Touch Pro 2 (AT&T Tilt2), No luck. Started to boot, Complained about /etc/init then poof reboot after 7 seconds. Am I missing something.
Click to expand...
Click to collapse
Did you change the mtype in the sartup script to the tilt2, the one i used is set for the rhod100, i hope that helps. Is anyone else's not working btw?
Help!
I extracted all the files on to a newly formatted 2GB card.
Ran haret and everything ran fine. Bit 'interesting' navigating round the screen but got there in the end.
However, since rebooting my phone back into WM I cannot run any unsigned programs such as haret that worked fine before.
The error says "The file blah cannot be opened either it is not signed with a trusted certificate..."
Any idea what's changed and how I can get my phone back to how it was?
R.
dicko99 said:
I extracted all the files on to a newly formatted 2GB card.
Ran haret and everything ran fine. Bit 'interesting' navigating round the screen but got there in the end.
However, since rebooting my phone back into WM I cannot run any unsigned programs such as haret that worked fine before.
The error says "The file blah cannot be opened either it is not signed with a trusted certificate..."
Any idea what's changed and how I can get my phone back to how it was?
R.
Click to expand...
Click to collapse
Wierd, my winmo works find, minus the calibration issue, it's brilliant, we need some linux Devs to look into this. as a windows user, i have no idea on what to do
Thanks (All we need now is win XP )
Badwolve1
I think something got corrupted/overwritten on my phone...
I cannot run any unsigned apps whether they are installed on the storage card or internal memory.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting back to how it was.
R.
dicko99 said:
I think something got corrupted/overwritten on my phone...
I cannot run any unsigned apps whether they are installed on the storage card or internal memory.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting back to how it was.
R.
Click to expand...
Click to collapse
did you install anything recently, could try uninstalling it
dicko99 said:
I think something got corrupted/overwritten on my phone...
I cannot run any unsigned apps whether they are installed on the storage card or internal memory.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting back to how it was.
R.
Click to expand...
Click to collapse
try installing SdkCerts.cab
http://forum.xda-developers.com/showthread.php?t=554240
the cab is included with the rhodium keymapper zip file. (keymapper app is worth installing as well )
sdkcerts won't install. It has the same problem as other cabs where it prompts to say the program is from an unknown publisher and when I tap Yes to continue it still fails with "Installation of SdkCerts.CAB was unsuccessful."
Tried booting it up on my Verizon TP2 and all it does is run haret and then freeze.
Thanks for putting this together, sebbo90. It boots nicely, and actually performs quite well on my Tilt2. I hope some of the developers take notice of this project and consider fixing the major usability issues like the front keys and the display calibration.
After the first boot I cant get the GUI to run anymore. Removing the directory from the SD and uploading a fresh copy fixes it for one boot only. After that it just hangs at command line.
spdweb said:
After the first boot I cant get the GUI to run anymore. Removing the directory from the SD and uploading a fresh copy fixes it for one boot only. After that it just hangs at command line.
Click to expand...
Click to collapse
How did you even get it to boot?
EDIT: Do you think it will not boot for me since you all are using GSM and i am using a CDMA phone? Some settings may need to be changed i guess. I have been messing around but no luck.
spdweb said:
After the first boot I cant get the GUI to run anymore. Removing the directory from the SD and uploading a fresh copy fixes it for one boot only. After that it just hangs at command line.
Click to expand...
Click to collapse
I had this problem what i did to fix it was to was to do a full reformat on my sd card (not a quick one) this then helped and now it boots everytime. Hope this helps
sebbo90 said:
Did you change the mtype in the sartup script to the tilt2, the one i used is set for the rhod100, i hope that helps. Is anyone else's not working btw?
Click to expand...
Click to collapse
If the mtype needs to be changed, what should it be instead of the default 2292, forgive my ignorance.
EDIT: must be a fluke, it booted now, did not change a thing. Re-extracted the ubuntu rar and shoved it back on the SD and booted. Great Job. All we need now is calibration to get started.
sebbo90 said:
I had this problem what i did to fix it was to was to do a full reformat on my sd card (not a quick one) this then helped and now it boots everytime. Hope this helps
Click to expand...
Click to collapse
I got it working now. It was the directory structure I was using. I spent about 2 hours last night working on the calibration issue. If I could get that working it would be sweet. Tried a newer version of haret and tweaked the startup.txt a bit but the calibration still goes out of range.
On a brighter note, the calibration works fine when booting xdandroid with haret though it is a manual calibration there is hope anyway.
All credit to 'Rufik'
Everything in it is prepared to boot Android straight from SD Card & internal memory - no need to make linux (ext2/3) partition at all. Quick guide:
1. unpack files and put haret.exe, zImage, initrd.cpio.gz, default.txt into root directory of your Omnia's SD Card (Storage Card)
2. put rootfs.img into root directory of your internal memory (My Storage)
3. run haret.exe and click "run"
4. you should see damn small haret's fonts, crc checking should pass with success, haret will jump into kernel
5. now kernel is booting, many messages and logo are visible. I've set a 10sec delay before mounting root filesystem, so you can see message that mmcblk has been found and partitions printed out
6. any failure within kernel booting ends up with kernel panic and phone restart after 30 seconds
7. successful booting results in some long-last message and "android" animation
8. in minute or two you will see desktop
rapidshare.com/files/381541433/andromnia2_alpha_pack.zip
modaco.com/content-page/298997/android-on-omnia-2/page/700/
Just tested this ... booting very nice ... a very nice start but still need a lot of work but a very nice begining..
Keep up the good work
fireburn said:
Just tested this ... booting very nice ... a very nice start but still need a lot of work but a very nice begining..
Keep up the good work
Click to expand...
Click to collapse
do you have the usa version omnia 2. i just tried putting it on my i920 and got it to load up but that was bout it. only displayed in landscape mode and keep switching between linux boot up and android home screen... any help???
nop european version (Portuguese).. it seems to work very well for an alpha version .. screen flicker and some programs that dont work ... but android is booting ...
dac2009 said:
do you have the usa version omnia 2. i just tried putting it on my i920 and got it to load up but that was bout it. only displayed in landscape mode and keep switching between linux boot up and android home screen... any help???
Click to expand...
Click to collapse
That's all that's working at the moment. Hopefully phone and data wont be too far away.
Could you upload to other website. it's getting stuck on 20% everytime
try going to modaco .. theres more links there
Very nice.. i have tried it.. very nice
Omnia 2 is the same like samsung jet S8000?
the samsung jet and the omnia2 have nothing in common they only seem a like...
Omnia on B7610 OmniaPro?
Hello,
Does anybody know if there is any work arround about putting Android on OmniaPro B7610?
Thank you for your answers.
sener said:
Hello,
Does anybody know if there is any work arround about putting Android on OmniaPro B7610?
Thank you for your answers.
Click to expand...
Click to collapse
It's working on mine, just follow the instructions provided and you're all set
so are all the buttons mapped correctly? and does WIFI, GPS, Market, standard-phone functions working?
on the omnia i920 I have android running..only problem is none of the buttons are mapped correctly. There is no Wifi. I'm not able to make calls either. Basically it's a visual goodie for now. I read on Modaco that they have the GPS working I think. It doesn't work on mine however. There is no sound either. I really hope someone can get this working fully because from what I seen it's a sweet os.
theres still a lot to be done ... the project is beeing directed by a guy named almar ...theres a lot of development to do on the drivers ..
two o/s
can work 2 os win&android
we need to get some devs on here to help out almar is one guy and he has done great but he seems busy with life and i think is in exam period. So if you guys know any devs that know android i think we should be able to help him out with drivers.
Hi,
I have Samsung B7610. I tried running the package, Everything appeared as mentioned. I think the buttons are not mapped. It does not detect the network.
I feel at the present stage, it cannot be used for normal telephony.
But, would like to thank for providing this oppurtunity, I am happy to see Android on my phone.
any updates on android for omnia II ?
Mikomi said:
any updates on android for omnia II ?
Click to expand...
Click to collapse
same question.. is there anything new developed?
cheers
Here' s my general experience with Remix OS (v 3.0.206) on my Asus T100. Not surprisingly, it's much the same to my Android x86 experience.
First, a big thanks to the team members at Jide and Anroid x86! And now on to my experience...
The install to my hard drive didn't proceed smoothly. I'm not sure it was because I already had Android x86 installed or because I have my Z drive mapped to my LAN and the install program tries (and fails) to mount my EFI partition there in order to install grub. To get past the failed install, I manually modified my EFI partition to add a menu item for Remix OS alongside Android x86.
After resolving the installation woes, Remix booted fairly quickly and the setup option worked fine. The OS works pretty well and seems to allow all my Android apps to run. I haven't installed and tried them all yet though.
Not all the hardware works. Here's what works and doesn't:
Working
Touchscreen - works
WiFi - 2.4 and 5 GHz both work. WiFi seems to stop working and can't be re-enabled if the tablet sleeps.
Track pad - works, but can't be disabled using the keyboard function key
Keyboard function key volume up and down
Keyboard function key brightness up and down
Dock USB
GPS
Suspend. (The notification light did not go out, so it wasn't fully suspended.) I didn't fully test suspend, so it may or may not be working properly.
Battery icon
External speakers
Accessing my dock hard drive
Not working
Auto brightness
Camera. It doesn't work at all.
HDMI Out. Video displayed does not fully fill width of screen. Audio still comes out of the T100. Booting will not complete if HDMI is connected; it stalls at the command line.
Notification/camera on light - stuck permanently on.
Auto rotate (and no manual rotate either)
Keyboard function key volume mute
Keyboard function key to disable/enable the track pad
Esc key doesn't always behave as the back key.
After putting the tablet into the keyboard dock, Remix launches its File Manager *every time*. It's annoying.
Not tested
Bluetooth
I had freezing issues with a previous Release Candidate of Remix, so this version is usable by comparison. However, with so many non-working items, Remix on the T100 is just passable and not quite ready for a daily driver for me. v 3.0.206 fixed an issue with not being able to use WiFi after it was turned off (and back). If auto-rotate was working, I'd consider using it as a daily driver...
Can you please share your installation procedure?
awyeong said:
Can you please share your installation procedure?
Click to expand...
Click to collapse
Hi, I must have missed the notification of your reply...
I purposefully omitted the installation procedure because it was a pain, I started with android-x86, and I don't really recall the exact steps. Are you having a specific issue?
Hi,
I also have a T100ha & was thinking about putting Remix on it. Actually i was debating buying a Chuwi hibook pro 2 to play with (windows 10 + remix). But its really identical to the T100HA I already have in terms of hardware specs (or at least close).
I am a little fuzzy on if the remix os plays with the partition for a dual boot experience or if this runs on top of the windows 10 OS.
For those starting from scratch, what would you suggest on a Remix OS install - or is it not even close to usable?
RichTJ99 said:
I am a little fuzzy on if the remix os plays with the partition for a dual boot experience or if this runs on top of the windows 10 OS.
For those starting from scratch, what would you suggest on a Remix OS install - or is it not even close to usable?
Click to expand...
Click to collapse
You don't need to create a new partition or resize an existing partition. It gets installed on your C Drive, most of it being installed in C:/RemixOS or whereever you choose. Your MBR will be modified to allow it to boot to WIndows or Remix.
Remix does not "run on top of" WIndows 10, like an emulator or VM. It is installed on the same hard drive, but is booted separately. But that reminds me...if you power on your tablet, it will boot straight to Windows. In order to boot to Remix, you have to a) hold power/Volume down to get to grub where you can select Remix, or b) Use Advanced Startup within Windows 10 to boot to Remix. It would be better if the Grub menu was presented on boot without the button mashing. Thanks, Microsoft/Asus!
You can/should try out a USB install to test it out. You can see what works/doesn't work for yourself and judge whether you want to install it to your hard drive or not. I still have it installed, but only use it occassionally.
So this isnt like Bluestacks which runs within windows? What I dont like about Bluestacks is the resources it uses even when its not running. The T100HA has very limited ones.
I see a number of posts on reddit with people trying to figure out how to install this on the T100HA.
Because I am a little fuzzy - Can you live install the ISO on a USB drive (like Ubuntu) for testing?
Anything not working for you on Remix?
So with the bootable ISO & usb. I power up, hit escape, choose the usb drive. I get the option of resident or guest - i choose guest, it says android-686, a black screen with a border pops up, then the system reboots & ends up in windows.
RichTJ99 said:
So with the bootable ISO & usb. I power up, hit escape, choose the usb drive. I get the option of resident or guest - i choose guest, it says android-686, a black screen with a border pops up, then the system reboots & ends up in windows.
Click to expand...
Click to collapse
This is the part that I don't exactly remember what I did to get it working.
You've probably disabled Secure Boot in Windows (required). I used Rufus to make my USB stick. I had problems when I made it with LiLi. So, if you didn't use Rufus, give it a whirl. Try the resident mode too.
Also, I think I used the Android-x86 USB install and copied the RemixOS files over top of it. Alternatively, go to http://www.jfwhome.com/2016/01/04/latest-steps-to-install-ubuntu-on-the-asus-t100ta/ and follow Step 1 only... First Steps: Prepairing for the Ubuntu Install
I'm stuck on logo...can you put your grub.cfg file here?
or al least the remix os entry...in other PCs, changing parameter I solve that...but now I can't in my asus T100taf...thanks.
So I bought a new phone since my old Onyx (One+ X) died (cracked screen and charging port is getting iffy). And finally I decided on this one, a cheap Chinese docomo branded one off Ebay.
I was so exited when it arrived, the UPS truck was at my gate when I got home that day, ready to leave, but the driver was nice enough to wait and give me my package then and there. Pheew.
Well, now to my, bootloader unlocking, recovery flashing, after market os installation and rooting story...
Bootloader:
The phone was supposed to be unlocked, and I guess that only meant SIM unlocked, because the service menu read "Bootloader unlock allowed: no". Damn.
A few Duckduckgo searches later, turned up I needed the "S!Unlock tool" which I found a copy off online, but username/password fields needed to be filled in, and I think I found a pirated s/n which didn't seem to work, (might have if I had tried harder).
But since it was just over £22 at https://networkunlocking.com/ I thought I could spare that on the off chance it worked. I was very surprised when it finally did, truth, I needed a few tries. And it actually did turn that service menu's pesky "no" to a thumbs-up "yes". Yay!
So now, pulling the cable, holding "volume up" and inserting cable for that blue light goodness, and running the "flashtool.exe -i 0x???? oem unlock bootloader 0x????????????" comand.
Not so fast, that doesnät work with newer flashtool versions...
Finding the old one from my Xperia Arc days and runnning it again, Yay!
(Wish I had read ahead and done that temporary root trick to rip my DRM codes off my phone first. But I don't plan to revert to stock, and I gather (might be wrong) that the DRM is only needed for stock roms, and not Lineage OS and such.)
Recovery (TWRP):
Now the problems start for real, getting into recovery was a **** and a half. Most guides for the phone says to push "volume up" multiple times during the boot-process. This turns out to be plain wrong. The actual button combo is holding "volume down" and "power" button together atleast until the screen goes blank after the unlocked bootloader warning.
Now, I wanted 17.1 on the phone and the recommended TWRp is 3.1.1 or something, and this works to install lineage fine, but don't forget to erase /data partition as I did. Stupid mistake that made wifi fail miserably, and probably a lot of other stuff, that I never tried before noticing my mistake.
However trying to get my own set of ringtones on the phone turned out to be another issue, going back into recovery when I noticed my ringtone.zip had failed. Obviously the media folder had moved since los 15.1,so no wonder right? Turns out it wasn't the only problem. TWRP 3.1.1 (or something) failed to unencrypt the root partition, so changing anything via recovery was a lie. fortunately the latest recovery, 3.5.2_9 did. So after installing that everything was rosy peaches.
Rooting:
SuperSU? forget it.
Magisk? yeah, but how? No really good step by step guide out there, except download from the github page, but what version?
A little trial and error, tried with the arm64 version and it turned out to be the right one. (Sometimes you just get it right on the first try...)
Renamed the apk to .zip put it on the phones memory, entered recovery and installed the zip, et voi effing la, Magisk root installed.
Root checker verifies root status, TitaniumBackup and RootExplorer works. Yes, my phone is playing ball.
Final notes:
This above looks simple right? In fact this was a two day process since the guides are surely lacking for this phone, a lot of trial and error, the greatesthurdle was getting into Recovery, until I found the right button combo I accidently managed to enter it once making me believe I had the right combo and something was wrong with the phone. 4 hours or so wasted trying different versions rebooting and flashing. Getting back my Viber messages turned out to be a problem to, TitaniumBackup got the messages back, but the db had references to my old images on my old phone, and probable pointed at the wrong directory so trying to send images either from gallery or take new photos crashed the app. Solution, backup the messages to my google account, uninstall and reinstall viber and restore from that backup. TitaniumBAckup is good but no magic bullet, it's a ***** that we have to rely on Google for backups though, I am allergic to the cloud, something about it makes my skin crawl.
Otherwise I like the phone, it says docomo on the back, something I can live with. The Chinese vendor even supplied one glass screen protector for the phone and a clear soft plastic case, in case I wanted some extra protection. I only wish there was a screen protector that had the same surface as the one that was on the phone in the box, that slightly opaque cloudy feel was so nice on my finger.
Can I recommend this phone? Nah, if noone writes a step by step guide that will cut down the time I spent on making this phone palpatable, I can't. But if you, like me, don't mind to tinker and don't want a phablet or spend way too much for the privilege to get a screen size you don't want, then sure. But why do we have to get them from China?
My trusty xz1 compact is slowly dieing on me and i am looking for a replacement how much did you pay for yours and is a really new or just refurbished ?
"Final notes:
This above looks simple right? In fact this was a two day process since the guides are surely lacking for this phone, a lot of trial and error, the greatesthurdle was getting into Recovery, until I found the right button combo I accidently managed to enter it once making me believe I had the right combo and something was wrong with the phone"
This Phone is in the mobile Sphere already ancient. Don't expect to get any help here or newer hot to guides.
my biggest problem is the fastboot recognition of my Windows. If this would work reliable i could better flash the phone but getting the right driver is a kind of roulette for this phone.
muhschaf said:
my biggest problem is the fastboot recognition of my Windows. If this would work reliable i could better flash the phone but getting the right driver is a kind of roulette for this phone.
Click to expand...
Click to collapse
Also had a non-connecting fastboot issue on Windows until I ran into this guide showing me it was not about a driver but an installation method:
How to install Sony Xperia Drivers Manually (Super Easy Guide)
Step-by-Step guidelines to install Sony Xperia Drivers Manually (this method can be used on Windows XP, Vista, Windows 7, Windows 8, 8.1 and Windows 10).
xperiausbdriver.com
4qx said:
Also had a non-connecting fastboot issue on Windows until I ran into this guide showing me it was not about a driver but an installation method:
How to install Sony Xperia Drivers Manually (Super Easy Guide)
Step-by-Step guidelines to install Sony Xperia Drivers Manually (this method can be used on Windows XP, Vista, Windows 7, Windows 8, 8.1 and Windows 10).
xperiausbdriver.com
Click to expand...
Click to collapse
Handy cannot boot now anyway so i would probably not able to recover anyway.
muhschaf said:
cannot boot now anyway so i would probably not able to recover anyway.
Click to expand...
Click to collapse
The phone completely refuses to boot?
Do you have recovery installed? If not, are you able to install it via fastboot on linux?
4qx said:
The phone completely refuses to boot?
Do you have recovery installed? If not, are you able to install it via fastboot on linux?
Click to expand...
Click to collapse
okay i will explain.
i had this common issue with this running out of internal space (13GB pictures i could not find, only 300MB left) and after looking into it i figured, that, due to my constant app installing and deinstalling, i had literrally thousends of little images (thumbnails, icons, you name it) that got not deintalled for whatever reason and clogged up my internal memory. So i made a Backup and decided to completly wipe and flash the newest lilac from Modpunk (18.1) and did a big Mistake here. i go into recovery and wiped EVERYTHING...without checking that recovery is untouched. then during the same session i installed the ROM and rebooted...so far all nice and dandy. Setting up the Phone, then get the newsest Gapps and then try to reboot into recovery to install them...well did i mentioned that i had wiped EVERYTHING? Well, there was no recovery anymore. Not my first rodeo i headbutt myself into the desk and spun up ADB/fastboot...only to run into the same problem i run everytime due to improper intalled driver i forgot already about. Longs story short: after some time handy refused to boot also into system.
Phone is now unbootable into any state, but Black screen fastboot over hardware buttons...
i COULD still try to make a blind fastboot flash after following the driver install instruction from above, but consider my lucky or clumsyness i will **** this up too and only waste time. and due to my current covid recovery i have not the energy nor the patient to diddle around with this sorry excuse of an absolute restrictive Phone and rather get me a S5 mini or something else that has no bootlock whatsoever and let you flash it from the very start.
i am plain running out of patient with sonys harassment.
/€: Also the constant "cannot get root" on a rooted phone is plain BS³. having permanent trouble to install adaway or use my sdcard proper is so friggin annoying that i now will search for a android version that got rid of this bull**** and will buy any phone that is suported by that ROM.
It is MY phone, and not Goolge nor the the phone company will dictade what i can or cannot install on it. i decide and i carry the risk, period. and the biggest security reason holds the phone anyway.
@muhschaf okay so it doesn't seem bricked. Pretty sure you just need to flash the recovery through fastboot and flash a ROM. Try that on Windows with the driver method; if that fails boot a Linux distro e.g. EndeavourOS, even from a USB without installing no adb/fastboot driver is necessary for Linux, it just works. You can do it.
4qx said:
@muhschaf okay so it doesn't seem bricked. Pretty sure you just need to flash the recovery through fastboot and flash a ROM. Try that on Windows with the driver method; if that fails boot a Linux distro e.g. EndeavourOS, even from a USB without installing no adb/fastboot driver is necessary for Linux, it just works. You can do it.
Click to expand...
Click to collapse
i known, the question is more "i really want that?" like i said i struggle with this phone ever since. and i realized yesterday the problem is not the phone itself, it's the bull**** of androids security architecture. Google seems to be very prone to make sure that they can shove any amount of advertisements down your throat. Given that they earn their money with ad network it doesn't surprise me.
i came to the conclusion that in reality i want to have a reliable way to install ad away on any given phone i own. i archive similar things on my desktop with Firefox and umatrix and ublock. And what can is say: Having Advertisment fee Internet is a bliss and i not care a bit about "but the free stuff" and i incrisingly fury about my inability to archive similar things on my phone i rely quite a bit.
@muhschaf I get it but you know what they say: good things require effort. But I find that once I set my Android up, I'm happy to have done it.
In regards to ads, you can actually install uBO on Android Firefox now, and many other addons also.
So i gave it a try again and the result was that it detects now a "?" under fastboot but ADB can't see anything failing sucsequently to flash recovery. i am also seemingly unable to get even into hardware fastboot anymore. But could be quite possible that the battery is already drained again. so i recharge it the night.
4qx: i was going away from uBO several years ago. Wonder that he has survived the drain after his "whitelist" decision, but it seems like.
Adaway block advertisement in apps and this is mainly the feature i wanted, see advertisment have gotten out of the browser itself into the Base/apps systems (Android, Windows) and therefore the Adblocker have to go with it. under windows i can control the System itself pretty easy and throughoutly with Powershell and package debloating scripts or regedit. under Android i haven't this option and have to rely on app like adaway. This shortcoming is pretty frustraing for an "Open Source" OS
After nearly a Year i stumble upon something windows related and now i have finally my xz1c back:
Windows USB Hubs of ANY kind (Monitor USB Hubs, Powers external USB Hubs, hell sometimes even the PCH, that is technical also a USB Hub), can and sometime WILL prevent proper lowlevel access to devices like...USB Headsets (Logitech Pro X) and Mobile Phones in fastboot mode (xz1c).
To circumvent this you have to connect the phone to a USB Port on the Back of your PC Motherboard DIRECTLY. every other Port can have an USB Hub in between that alters your write or readout and therefore failed the flashing.
I recently bought Asus Zenfone, because here in Ukraine is war, so I want small device with Windows (electricity often is off here because rockets fall on our electrric infrastructure etc).
So I've bought Asus Zenfone 2 used (it costed 16,25$). It came without accumulator, and 1/3 screen working. So I went to radio-market to buy new battery, it costed + ~10.25$ + 2,5$ to install battery. Then I've bought new touchscreen for it for ~22,5$, plus payed ~6,25$ to install it. Then around 7,5$ to restore battery connectors (on device and accumulator). So finally it worked, and wanted to see how to install Windows on Zenfone. Sure, if I had possibility to buy anywhere Zenfone better, new, not used, - I'ld do it, but it is not that easily available, just like any other Intel smartphone.
So, I started reading - how to make my device rooted. I don't understand how to get root. I found on wikipedia, that rooting is different from unlocking bootloader, and realized - yes. I need to unlock bootloader, and to boot from external flash-disk and install windows, or at least - new kernel with KVM support. I used pn my Android (non intel) Limbo x86 emulator, it can run some old windows 98 etc, maybe even xp, never win 2000, and if it runs win-7 or win-8 - it is so terribly slow. So I decided to buy Asus Zenfone. As in KVM mode I can send commands to CPU directly, and hope this Windows works much faster than in emulator. I hope just at least to run Windows XP on it, I need to code some C# code, so that Andorid phone is not only for mp3-playing, internet on the go and make calls, but to learn, study and to work. I don't know why Microsot, Intel and other companies don't like Intel CPUs in mobiles. They could do it if they wanted. I like WIndows because most programs are for Windows. And I want desktop x86 windows also on every mobile, intead of all Androids.
Anyway, What I tried to with my Zenfone. I found one amazing experience - that our hero and inspirer (ley God blesses him, maybe he will work in Intel/AMD/Asus/Microsoft etc to make more newer KVM kernels for future x86 phones with windows) - so Ycavan made KVM for Asus Zenfone 2. Great, I've read his thread - https://forum.xda-developers.com/t/...0-with-kvm-bridge-compiled-need-help.3145055/ - completely, with pen and paper writing down important information, downloaded all the files, and decided to start flashing.
I copied them to root of my Zenfone, unpacked tars and converted them into ZIPs. I also unpacked .img files to root of phone (I mean its folder which is visible if I connect it thorught USB, I know it is not "/" root of file system of Andoird, but anyway it is visible even inside CWM... sorry, was visible)...
So, I made some mistakes. I downloaded the kernel, tried to flash it using commands like :
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150710.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150714.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150717.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
fastboot flash boot boot_2.19_kvm_bridge.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
but non of them produced bootable Zenfone. So I had to revert to previous bootloader using the CWM tool.
In fact I liked this CWM most. I found this thread - https://forum.xda-developers.com/t/...root-ze500-ze550-ze551-temporary-cwm.3114063/
or similar here on forum, and it worked amazingly. I attached Zen-phone to USB, turned it off, then on while pressing, keeping pressed volume-up key, and after Asus logo appeared and some "zzz" vibration, again it blinked and I saw bootloader with Android robot, and possibility to scroll through menu using volume up-down, to choose normal boot, or reboot/power off, or to run restore etc.
For some reason, Restore there not worked. So anyway, I understood that I can use tool like ADB (Android debug bridge) and fastboot to copy new firmwares/kernels/bootloaders etc to it, so I guessed I can do it myself, and was ready for risks... And this what bad can happen - it happened.
So, I runned in CWM - file cai_dat_CWM.bat - which asked to type ACCEPT and then T4, and phone started to go into amazing mode, some "clouds" started appearing on phone, and it loaded into special secret menu, from which I could select what to do next. To me it looked like default boot manager which I wanted to see like in Dos/Windows machines - so I can choose to run into safe mode windows, or set some settings before booting, or even use "reanimator dvd" etc to load Windows and other tools to do partitioning, passwrods recovery etc. So it looked like on desktops, and very nice. I went inside the menu, and found good option to make backup. I did it all. Then in same CWM tool (I think it is called SuperSU for Android), I finally choose to restore bootloader/kernel/boot (custom recovery), and this saved my from bricking the first time after I followed the manual from Ycavan. Well, I know I can read a lot more threads how to do this and that, but there is always risk that something wrong can happen. So I tried to read as much as I could, and follow manuals as precisely as I could understand. But my phone is kind of "bricked".
Now it shows some scfreen like TV which can't catch any tv program. So it is some random colors - see attached picture. It is good that it shows at least this. But in worse situation - it doesn't show anything. So let me tell how I achieved this, and if you can tell me how to avoid this mistake and to recover it. I hope to get help from anyone here who installed KVM kernel(s) and acheieved running Windows on their zenfone 2 (or maybe anyone who has XPerience with other x86 phones may help, or if it is general issue how to unbrick - then also non x86 users please help).
So, CWM made backup, I became more non-scared to make more experiments with firmware. But main problem is that I don't know which firmware to use. I ideally suggested that when I change kernel to KVM-supported from Ycavan - that it will work with my Andorid 5.0 (it was installed when I bought it). So, but unfortunately, after installing any of KVM kernels of Ycavan - I was unable to understand which OS to install, which version. So even I tried to try to flash whole 1GB+ image (I have downloaded UL-Z00A-WW-2.20.40.59-user.zip from official asus.com - https://www.asus.com/ua-ua/supportonly/asus zenfone 2 (ze551ml)/helpdesk_bios/ - but. I was unable to upload it to zenfone (flash it), as it said it is older than installed version.
Anyway, now it doesn't matter as I cannot run into ANdroid at all. Worse - I cannot even get Bootloader working in Android, as I see after turning phone on - only "white screen" with non-working TV-like image (see attached picture of my Zenfone 2).
So, to make this happen, I did this: I found some information about TWRP. I tried to install as recovery tool. Even though it was flashed into mobile, and I installed it from apk from Google-Play, still, I was unable to run it... So then I found even cooler tool - which was too risky to install. I was good, but Andorid stopped running at all.
This tool is called - preroot601. I runned in it preroot.bat, and then it did something similar to CWM, but several times it restartd the phone _ i have added screenshots of how it looked like on PC / Windows. So after several restarts, it did a lot of changes - Android didn't start after it. Phone always was able to start into recovery mode - into TWRP (I downloaded its .img and flased it as recovery for phone). But in TWRP I think I did something wrong. I made backup of all files (syste,, bootloader, everything). I saw it is cool - to see there terminal, ability so set attributes for files, mount partitions ... even USB -hey, can I run from flash-disk? or from external DVD/Bluray which I have in this mode? I have USB-hub, and can connect to it keyboard, mouse, flash-usb, ssd/hdd - all through Microusb-usb adapter and to usb-hub. So what I wanted to do is to try to see flash-disk, mount it on my android zenfone. And then after restart - I had black screen or this 'non-working analog-TV screen when no program/channel/wave is caught for signal"...
So, I don't even understand what I did, and why this all happened, and why I have to do to restore bootloader at least.
My aim is to have KVM enabled in the kernel. I don't mind if it is old Windows like XP working on this Zenfone, but I like windows to be my main OS on every phone which I may use in future (and hope they all be x86-64 and not ARM). So as I don't have Steamdect now (it has also AMD x86 CPU, like Zenfone), I want to do this, achieve it - having Windows on mobile - Zenfone.
I can carry it in pocket everywhere, so why not people like having desktop Windows x86-64 in each and every mobile? Even Lenovo are collaborating with IBM - then why not make also IBM-Mobile / IBM-smartphone, which will also be as good as PC - to unassemble it, change any part like on desktop, why not do it? I think everyone will enjoy it, and it will boost everything to better hights, levels.
So, please. If anyone here has similar experience of going to same screen like I have (see screenshot), or like that - black screen - indeed my device also may not even show any thing - even no ASUS logo, no bootloader (even if I press Volume-UP after powering and after flash it usually showed bootloader with robot - no... not now)...
So I don't see anything on screen of Android Zenfone now. no text, no bootloader, no recovery even - no TWRP menu. I think I am ready to format whole zenfone, and install there maybe some partition manager (like you know there is Partition magic on PCs, when I can split HDD/SSD nto two parts, one for Windows, and say other for Unix - Ubuntu or Android x 86 - all on same physical drive)... So I want some re-partitioning for intern SD memory, and be able to install there some ISOs, say with DOS, Win3.11, win 95, 98, 2000, xp, 7, 8,1 and maybe even 10. But guess last will be slow. I think Windows XP would be ideal OS for my Zenfone, if it can run fast. Win 7/8 maybe will be slow. But for some sceintific aims - like I just write some algorythm in Visual studio, and can do it even in WinXP, so why don't do it on my Zenfone? I don't like many Andorids, as they are not for work much - they are used by many people to play games, watch videos on phones, surf social networks, but not for real work. Real work is usually on WIndows, and no laptop can replace "Windows x86 in pocket" (on mobile). And I wonder why Microsoft develops "Windows for ARM" instead of investing millions into efforts like which Ycavan did - to make Windows run in KVM mode fast on x86 smartphones.
Ok, So, any ideas? What should I do now? I need some special tool to fix my phone first. Fix its loader. I think I need to bypass fastboot.exe restriction, which shows "waiting for device". Command in cmd like this: ADB.exe devices -L --- shows device from time to time - it shows:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
So, I cannot even flash some recovery device in this way. In devices manager I see "ADB interface" in "USB devices" category in devices treeview. And sometimes Moorefield appears, but with exclaimation mark - I have no idea how to make it disappear. I found here some info that I can install tool - xFSTK_Downloader_v1.7.0.zip - I downloaded it, installe,d but it doesn't run (I have win10 x64bit). hm... And driver required - iSOC_USB_Driver_Setup_v1.2.0.zip - I installed - but nothing.
So, what to do? How to make bootloader appear again? And how to write there prob=per bootloader with KVM kernel, and which firmware to flash so I can use KVM fast there with fast Windows...? Is it possible at all to make it run WIndows natively on Zenfone? or it will always be only in virtual machine inside some ArchLinux or in Limbo x86 on Android?
I read that Ycavan used this ArchLinux, but I don't understand why. Is he installing it over Android? Then also which version he uses? I need to know each and every version whcih he uses to make everything works. I 'ld require all the firmwares which he uses to make it work also - to make some Windows iso run on my Zenfone 2.
Did anyone achieved this successfully, except for Ycavan - to run Windows on Zenfone? Or except for him noone was able to install KVM kernel, and it was similar to mine situation? And maybe this is the reason why manufacturers of phons don't like x86 phones? I don't know. Any ideas?
See screenshots. What to do in this state?
IF anyone can please upload to somewhere whole pack of files ("WIndows on Zenfone starter kit") to make anyone able to just follow instaructions which will work in all cases to install WIndows there like Ycavan has - it would be great. There is lack of more detailed information - which .img files, .zips, firmwares etc, which OSes are supported by Ycavan's KVM kernels?
I have no idea. if anyone passed this path, and achieved Windows on Zenfone, please share your experiences, Ireally need it. Here in Ukraine when electricity disappears almost daily, we need devices like x86 phones almost for everyone. And mo matter if Windows is a bit old. KVM mode I guess must be much faster, almost native speed, so (like on tablet PCs), so please help...
Thank you all in advance, whoever will answer me.
indubhushan said:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
Click to expand...
Click to collapse
wrong mode. adb is only working in
- normal/boot mode
- recovery mode
fastboot is only working in
- bootloader mode
- fastboot mode
You can see 0123456789ABCDEF device in adb devices, therefore you are either in TWRP or in Android (Win?)
type adb shell and check the prompt is either $ (shell) or # (root shell)
in root shell you can flash partitions from cmd line. you can also reboot into bootloader/fastboot mode from cmd line.
Code:
adb reboot bootloader
I had success in restoring my bootloader (logo with android robot) - I intalled xFSTK, so somehow I had success to make it run, and I added threee files (1, 2, and 4th) and tried to flash it. Phone was visible as Moorefield. Then I tried to use Asus flash tool to flash big RAW image, but for some reason I don't know why - I had even whole day left it to flash, it didn't do the task - Android stopped booting - no logo showing at all - have to use xFSTK to recover. Maybe I use wrong RAW image (from official site it is .zip, so have no idea where to get those raw files).
When try to flash using flashboot - I get error: - flash cmd error.
As for devices list. My device rarely appear there. It may appear for some seconds, and then xfstk can have success to flash it, and maybe even make it runnable into Android robot scren (bootloader).
I am thinking that I need to install maybe ArchLinux, which Ycavan is using, but have no idea where to get RAW file for it, and how to flash it. Maybe some problem with my USB port on old laptop, or maybe even with USB cable (though have few good almost new cables, even new 4Amperes one). So maybe even problem in port of Zenfone itself (to change it). No idea. Because even when I tried to flash it (that huge 1GB file), phone disconnected, or showed "ready for commands", instead of showing process of ownloading RAW image/Android into phone's memory.
Flashboot/adb almost unusable. Well, I'll try, maybe it'll work.
My hope is try to go into CWM, run from it into "secret menu" on phone, and from it - to access internal memory of phone, and restore phone from backup. But when I tried to load into it once - it hanged on "clouds". I don't know...
And I don't think I'm ready now to format internal memory of phone or to repartition. At least I don't have backup on some external card (sd-card) etc.
as for adb. maybe it can't see my device, even if it is "recovery mode" (when see in devices manager in Windows - Moorefield). Now I'm stuck on xFSTK and can't go anywhere further like adding TWRP into phone, or foing into backup/restore menu on phone, and of course there is no Android. Even when I see Android robot (boot menu) - I feel happy, that at least phone shows anything, so at least bootloader workds. Maybe difference is in drivers - when I have Moorefield driver, then maybe it contradicts with Zenfone driver, and I have to reinstall them? Or use other OS? I have dual-boot (two Windowses on my laptop), so maybe I need to use one Windows - to work with Moorefield (xfstk) - when phone is in "worst" situation when no logo shows / no bootloader. And the other Windows I have to run on laptop - with Zenfone driver installed (I think it shows something like Asus device in device manager). But they seem to use contradicting drivers, I am not sure. And maybe it's some problem with my usb ports, but hope no. They seem to be ok... Maybe I'll have to go some day to give phone for diagnostics to repairing center again ;-(