Related
Hi....i was going to format my shift and since i never used the vista recovery option from the bios i downloaded gparted and made a live cd usb and booted it up, deleted every single partition uncluding the hidden one that i could see and in total i had one big unallocated partitionless harddrive which i saved the changes and rebooted.
I then inserted a usb stick with windows 7 on it and proceeded to install, i created a new partititon and windows asked to create that 100mb system reserved and i then proceeded with the installation which took more than twice as long as it has ever done before.
Is this due to my gparted fiddling? Because at the second stage of installation, the unpacking of files it went quick and smooth up to 38% and after that slow as hell, unlike ever before during any version install...
And now that i finally had that part of the installation behind me it proceeded to automatically reboot for the final stage and when it did reboot after the RAM and basic BIOS tests it reported bad SMART status and i pressed F1 to continue and everything resumed as it should...
But I cannot find any settings in the BIOS to turn of the SMART checking so what can I do now?
Did i not delete the MBR? as I thought it would have gone with the partitions...
And why did the installation go so incredibly slow this time?
now I just got a Blue Screen & Ataport.sys message.
Could it really be such bad timing that the computers HDD has started to fail at the same time i deleted the partition or is this a software issue and not a hardware one?
What version of Windows 7?
I accidentally downloaded a RC/ Checked Debug version which had the same problems on an original untouched HDD.
If you are using correct version, then try repartitioning woth another tool liek acronis disk director. Format completely. Reboot, then re-partition , install windows 7 (RTM available tomorrow)
oh you sound a bit more optimistic than over at hd guru forum, check what they wrote when i published my thread over there:
http://forum.hddguru.com/htc-shift-recovery-partition-gives-false-smart-bios-error-t12907.html
Hi I am currently running debian on my phone using the method outlines here
http://www.myhangoutonline.com/2009/11/22/install-linux-on-your-g1/
Ive gotta say it quite slow and the method of installation is strange.
Here is a video of someone dual booting NATIVE debian on a G1. Read descrip in video for more info.
http://www.youtube.com/watch?v=tX1BOGl8Fnw
I would really want an option where you boot into recovery (Holding Home) and there is a menu where you can choose to boot into a normal recovery (Amon_Ra's) and the other options would let you choose between what OS you want to boot into like Gnome,OpenMoko,Debian. A normal boot would take you back to android.
Speeking of OpenMoko
there is a tut here
http://wiki.openmoko.org/wiki/OpenMoko_on_HTC-Dream
and i was wonderin weather anyone had tried this because it seems very interesting and would make it possible to bood gnome,debian etc
any opinions are highly appreciated
let me know what you think.
i dunno if im allowed to but bump
donut = 1.6 right?
yes
cupcake = 1.5
donut = 1.6
eclair = 2.0/2.1
Hi!
I've got OpenMoko dual-booting natively on my G1.
When I first looked into the problem, I saw that:
1) OpenMoko option involved boot flashing that would disable booting into Android.
2) Debian option had no ready-to-use rootfs. You had to bring on the usbnet and install debian packages through netinstall. But Debian was able to dual boot, thanks to FukTheRegister's excellent recovery image.
I surely needed something in the middle
I had contacted the OpenMoko port developer, leviathan (a nice guy btw). He's doing some great job of hacking the forked Android kernel to work on HTC Dream together with some other guys. He told me that he was continuing his work on OpenMoko for HTC Dream and that made me want to try it instead of Debian. By the way, FukTheRegister's Debian and Ubuntu ports are based on leviathan's OpenMoko kernel.
What I did to install and dual-boot OpenMoko was:
1) I partitioned my microSD card into three partitions: FAT, ext3, ext3
2) I extracted the OpenMoko rootfs to the third partition (ext3)
3) I made myself a recovery image that would consist of the most recent OpenMoko kernel from gitorious AND FukTheRegister's ramdisk (I just glued them together and threw away some modules to make it fit into 5Mb - maximum for recovery partition images)
4) I copied the recent kernel modules to /lib/modules/ on the 3rd partition of the sd card
5) I copied my recovery image to the sd card and flashed it with flash_image recovery /sdcard/openmoko-recovery-partition3.img right on the phone (under root).
After that I was able to boot OpenMoko with holding HOME + END during the bootup or Android (holding nothing).
See http://vaskas.ru/om-g1/ for all the relevant files.
If you want to try it yourself:
- repeat stage 1) after me
- take the openmoko-rootfs-20091128.tar.gz and repeat stage 2) after me
- copy the openmoko-modules-20100128.tar.gz to /lib/modules/ on the 3rd partition and extract it there
- take the openmoko-recovery-partition3.img and repeat stage 5) after me
P.S. I am not 100% sure that it's going to work for you, because I experimented a lot. It's pretty likely to work though.
hi again vaskas!
thx for work. Tried your setup, it worked for me.
Now it would be nice to have a recovery with an option to boot the second ext3.
Openmoko on Dream ----> nice!
Seems to get a usb connection:
http://wiki.openmoko.org/wiki/Usb_networking
Is a ssh/dropbear server already running on boot?
vaskas thx so much for the huge leap forward ecept im a little confused. so when i hold home + power using ur method it will boot into openmoko, butif i boot normally it wouild go into android, but what if i wanted to boot into normal recovery like amon_ra's?
if i boot into android normally and then run quickboot app and select recovery will it boot opoenmoko or amon_ra's recovery. also with your method does keeping apps on the first ext3 still work? while the second ext3 is for openmoko?
also when making second ext3 partition what size should i make it?
p.s this is sooooooo sick with open moko the possibilities are endless aswell as for people who prefer they can turn openmoko into debian and some time in the future android
so future = openmoko installed instead of android and then being able to boot debian/android or stay in openmoko environment.
also if it's not to much trouble vaskas can u please make a vid and put on you tube or here thx in advance andthx for ur hard work
olvap377 said:
vaskas thx so much for the huge leap forward ecept im a little confused. so when i hold home + power using ur method it will boot into openmoko, butif i boot normally it wouild go into android, but what if i wanted to boot into normal recovery like amon_ra's?
Click to expand...
Click to collapse
No, normal recovery won't be there, since my image replaces it. As far as I know, it's the only way to dual-boot now. If you wish to use your normal recovery image (amon_ra's or cyanogen's), just flash it with flash_image recovery my.img. When you're done with it, flash it back to openmoko's.
olvap377 said:
if i boot into android normally and then run quickboot app and select recovery will it boot opoenmoko or amon_ra's recovery. also with your method does keeping apps on the first ext3 still work? while the second ext3 is for openmoko?
also when making second ext3 partition what size should i make it?
Click to expand...
Click to collapse
I haven't tried quickboot yet.
Yes, Apps2SD still works perfectly with the first of ext3 partitions. I suggest that you make the second one at least 700Mb in size. I've got 500Mb taken by OpenMoko, for instance.
olvap377 said:
also if it's not to much trouble vaskas can u please make a vid and put on you tube or here thx in advance andthx for ur hard work
Click to expand...
Click to collapse
Well, you shouldn't really thank me since I only built a recovery image It's the kernel and ramdisk hackers who rock.
I'll make a vid when I have some free time, but I really suggest that you try it yourself
scheich said:
hi again vaskas!
thx for work. Tried your setup, it worked for me.
Now it would be nice to have a recovery with an option to boot the second ext3.
Openmoko on Dream ----> nice!
Seems to get a usb connection:
http://wiki.openmoko.org/wiki/Usb_networking
Is a ssh/dropbear server already running on boot?
Click to expand...
Click to collapse
FukTheRegister's ramdisk has such an option. I can try to make such a recovery if you need it.
Yes, dropbear is started automatically.
I'd love to see a solid and stable distro that would provide all the things that Android doesn't have, with:
- A compact desktop environment, supposedly e17 or LXDE
- Midori or Google Chrome
- Pidgin
- Sylpheed or Claws for GPG-secured e-mail
- MPlayer or VLC
- FBReader
- evince
- AbiWord
- Gnumeric
- Conky
- Gpodder for podcasts
- Some music player like Sonata
- Cron, sshd, gcc, scripting languages like Python and Ruby
- Zhone for making calls, texting, storing the address book
See, I'm not advocating touch-oriented software. I think we still need touch-capable apps for calling, texting and the address book. The others can be easily manipulated with the trackball and keyboard on G1.
That's what we should aim for IMHO: http://wiki.openmoko.org/wiki/Image:Debian_lxde_zhone.png
OpenMoko project has all this stuff. And that's really awesome. The question is if such an OS should be based on Angstrom (like OpenMoko SHR) or Debian (see http://wiki.openmoko.org/wiki/Debian). My preference is Debian since I'm a long-time Debian/Ubuntu user.
i prefer debian too and i will try this when i get home
i'm sorry for my really dumb question.
but how can i copy something from windows (7) to a ext2 partition?
and if you are creating those partitions, do both ext2 have to be primary or
one primary and one secondary?
thx in advance
lolmensch said:
i'm sorry for my really dumb question.
but how can i copy something from windows (7) to a ext2 partition?
and if you are creating those partitions, do both ext2 have to be primary or
one primary and one secondary?
thx in advance
Click to expand...
Click to collapse
They both have to be primary. I also recommend you to upgrade them to ext3 which is more stable thanks to journaling.
As far as I know, it's not possible to write to extX partitions from Windows. You can copy the files you need to the FAT partition and move them within the phone using Astro or other file manager.
You can mount the second ext3 partition from Terminal Emulator in Android like this:
$ su
# cd /sdcard
# mkdir SD2
# mount /dev/block/mmcblk0p3 /sdcard/SD2
Then it will be accessible from Astro in /sdcard/SD2.
i followed all the steps correctly but it just gets stuch at boot screen if i try to boot into recovery
any advice
maybe this has something to do with the fact that i have ebi1 phone?
pls help i really want this
EDIT:
wow im dumb i figured it out if u look at my sig ull see the way my partitions are setup
i followed all ur steps except each time i changed instructions from p3 to p4 becasue i also have a linux swap so when i installed this recovery it tried to boot from part3 which is my swap and obviously didn;t work
so vaskas can u please for everyone who has a linux swap release another recovery except that boots from part4?
Have also a swap as the fourth partition.. That doesn't matter, I think. Its only important, that the second ext3 is the third partition.
Heres my partition table:
fdisk -l /dev/mmcblk0
Code:
Disk /dev/mmcblk0: 1977 MB, 1977614336 bytes
255 heads, 63 sectors/track, 240 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000ac1bc
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 1 64 514048+ b W95 FAT32
/dev/mmcblk0p2 65 131 538177+ 83 Linux
/dev/mmcblk0p3 132 223 738990 83 Linux
/dev/mmcblk0p4 224 240 136552+ 82 Linux swap / Solaris
olvap377 said:
i followed all the steps correctly but it just gets stuch at boot screen if i try to boot into recovery
any advice
maybe this has something to do with the fact that i have ebi1 phone?
pls help i really want this
EDIT:
wow im dumb i figured it out if u look at my sig ull see the way my partitions are setup
i followed all ur steps except each time i changed instructions from p3 to p4 becasue i also have a linux swap so when i installed this recovery it tried to boot from part3 which is my swap and obviously didn;t work
so vaskas can u please for everyone who has a linux swap release another recovery except that boots from part4?
Click to expand...
Click to collapse
Ok, try http://vaskas.ru/om-g1/openmoko-recovery-partition4.img - it should work.
I'll try to make a multiple-choice one soon.
thx alot il try when i get home from school
EDIT: still dosent work just freezes at boot screen
plzzzz help any advice
olvap377 said:
thx alot il try when i get home from school
EDIT: still dosent work just freezes at boot screen
plzzzz help any advice
Click to expand...
Click to collapse
Do you mean you're stuck into the "G1" screen? If so, it's a recovery/kernel problem, not really connected with partitioning and stuff. I'm not sure if this openmoko kernel supports EBI1/32A, may be it's the problem
Well I have a dream which is 32b but with ebi1 radio I think this is the problem because amon_ra has a special recovery just for rogers dreams meaning something is different between them
If u could compare amon's rogers to normal recovery and find the differences could u chabge yours to make the latest part 4 file ebi1 compatible?
olvap377 said:
Well I have a dream which is 32b but with ebi1 radio I think this is the problem because amon_ra has a special recovery just for rogers dreams meaning something is different between them
If u could compare amon's rogers to normal recovery and find the differences could u chabge yours to make the latest part 4 file ebi1 compatible?
Click to expand...
Click to collapse
Frankly speaking, I don't think I'm going to have much time for this Since my radio is different, I won't be able to test it properly too.
Actually, I hope that more people join the thread so that we'll be able to solve much more problems together. I wonder where the guys from "Installing Debian on G1" are gone, I saw 2-3 people really interested in native Linux there.
Can you still rename the thread? If so, what do you think about appending something like " - Native OpenMoko and Debian" to it?
EDIT: compared Amon_Ra's recoveries in hex editor, they seem quite different
Hello, I've spent several hours searching a solution for this problem, both on this forum as well as others. But still unable to find one I try my luck here.
This is the case:
U8800 bought in Sweden a couple of weeks ago. Installed SuperBoot r1 and CWM 4.0.0.5 Perfect Recovery from XDA forums. Installed Oxygen 2.2.2 r4, worked fine until yesterday. When it got stock at the screen lock. Pulled battery and then it was stuck in a boot loop showing only the IDEOS-logo. Tried to get into recovery with Vol+ and power. But still only gets to IDEOS-logo and then reboot after about 10 seconds.
I'm able to get into bootloader (pink-screen) by Vol+, Vol- and Power. Have tried to replace boot.img and recovery.img with others (original backup, CWM 5.0.2.3) in both Ubuntu 11.10 and Win 7). But still unable to reach recovery. And next time I start bootloader and check it's still the same boot.img and recovery.img as it was before I replaced them.
Seems like I'm unable to write to image folder somehow. It looks good when I disconnect it from the computer. Have tried "safe removal" in both Ubuntu and Windows, no difference. Also tried to rename the files to boot_backup.img and recovery_backup.img and then put the new files in there. But next time I start bootloader they are once again restored to how they were before (same file size as before) and the renamed files doesn't exists any more.
Have also tried to install B136 stock ROM via bootloader, looked good at first but when it was finished it said "Installation failed" (or something similar)...
Read somewhere modding the build.prop could cause boot loops, but I haven't touched that and therefore doesn't have any backup of it either.
Any ideas?
Yep, it looks like your bootloader may be corrupt...Do the following:
Boot the phone in Bootloader (pink screen) by pressing Vol+, Vol- and Power and connect the USB cable. Copy all the files you can find on that partition (this will be your backup) and format the partition with FAT32 file system, create a folder named "image" and copy the following files on there.
EMMCBOOT - http://www.mediafire.com/?lb6ifvgk72iru4a
AMSS.MBN - http://www.mediafire.com/?d6r45q6p5gew59v
Recovery.img - http://www.mediafire.com/?57njygc8oianjac
Boot.img - http://www.mediafire.com/?6d5i0714a7o9z97
Once you've done this, take the battery out and boot into Recovery and flash a new Rom (VOL+ and Power.)
Let me know how this goes...
Thank you very much for your help!
However when I try to format the partition windows says it couldn't complete the format. Tried both to right click > format and disk management > format. FAT32/std fast format as well as regular/slow. Neither work. If I do a regular format it goes at normal rate up to 100% and then says the disk isn't formatted...
I don't know if I dare to remove the partition and make a new in disk management, feels like I would screw something else up then?
Any tips?
Have tried to format in Ubuntu 11.10 as well, with the standard tool it didn't complain, but it didn't format it either. Installed GParted and tried that, it did seem to work and said it had successfully formatted it. But yet the image-folder still remains on the boot partition...
Run a systemcheck with the disk management in Ubuntu and it said the file system was OK.
I'm almost out of ideas now...
I don't think you're actually formatting the drive as the "image" folder should be gone once the format is done.
Try using a windows PC, I know that Gparted and Ubuntu can be a bit tricky sometimes...
Also, you've definitely installed the drivers for the cable?
On Windows 7 the drivers are being automatically installed, so maybe you should try that...
I've tried Windows 7 several times (the only Windows I use). It's very weird the files just wont go away. I have taken Shift+Del on the image folder several times and they are removed just as any other files on the computer. Then the next time I connect it the very same files (58 MB) are back! When I do a format the computer shows the disk empty, but when the error window comes up the files are back... In ubuntu GParted shows the partition empty, but after a re-scan the 58 MB are back...
Can try to see if I can make a screen recording to see if I'm doing it wrong somehow.
Thanks for your support!
I have a short screencast on screenr illustrating the problem, but unable to post a link I'll try to describe it.
screenr(dot)com(slash)WMls
Pastasallad said:
I have a short screencast on screenr illustrating the problem, but unable to post a link I'll try to describe it.
screenr(dot)com(slash)WMls
Click to expand...
Click to collapse
Seen your screencast...it's a bit unclear. Sent you a PM, hopefully we'll be able to sort this out.
Same problem here h ttp//forum.xda-developers.com/showthread.php?t=1318647
The bootloader seemed to be beyond rescue. Nothing seemed to help, tried several drivers and computers. But the partition seemed locket somehow, couldn't replace the files. Tried to flash in stock ROM 136 and 138. Both failed unless you removed the cust update file. Then it succeeded, but still bootloop when it restarted.
So the phone is now returned for service.
Thanks katu2006 for all the help!
UPDATE: it works. see my link below. If anyone knows how to root I'd appreciate if you reply.
Hi
I own a Linx 7 windows tablet. Android x86 builds have not been great due to lack of sound and other driver issues.
I want to flash the bios - the dual boot one - from the cube iwork7 tablet.
In a youtube video by "Mr Borshchuk" - i cant post links, the cube is shown here running the LINX bios, the same version as my tablet. Can I do the reverse and flash the cube dual boot bios on my Linx?
Do you think this would work?
They seem to have the same spec etc and I'm guessing the same board- the cube just has a silver back. All ports are in the same place.
UPDATE: After looking more on 4pda, the iwork seems to come in 1/16GB variants and 2/32GB variants. My linx has 1GB of ram but 32gb of storage. Would this be an issue? My search also confirmed they are hardware clones.
So, that's the BIOS flash method. My other thought is is there a way to boot the android rom from the cube tablet from the stock linx bios? I have tried using the androidx86 bootloader combined with parts of the cube image and parts of androidx86 but, as expected, it didn't work.
So: I'm currently downloading the dual-boot bios from 4pda. Should I flash to my Linx?
Thanks. I've always loved XDA.
androidonlinx said:
Hi
I own a Linx 7 windows tablet. Android x86 builds have not been great due to lack of sound and other driver issues.
I want to flash the bios - the dual boot one - from the cube iwork7 tablet.
In a youtube video by "Mr Borshchuk" - i cant post links, the cube is shown here running the LINX bios, the same version as my tablet. Can I do the reverse and flash the cube dual boot bios on my Linx?
Do you think this would work?
They seem to have the same spec etc and I'm guessing the same board- the cube just has a silver back. All ports are in the same place.
UPDATE: After looking more on 4pda, the iwork seems to come in 1/16GB variants and 2/32GB variants. My linx has 1GB of ram but 32gb of storage. Would this be an issue? My search also confirmed they are hardware clones.
So, that's the BIOS flash method. My other thought is is there a way to boot the android rom from the cube tablet from the stock linx bios? I have tried using the androidx86 bootloader combined with parts of the cube image and parts of androidx86 but, as expected, it didn't work.
So: I'm currently downloading the dual-boot bios from 4pda. Should I flash to my Linx?
Thanks. I've always loved XDA.
Click to expand...
Click to collapse
I just thought what's the worst that could happen and flashed the bios. it worked. installing android and windows now.
EDIT: Android works. If anyone wants to know how I did this, please reply
EDIT: Windows works. I have achieved a dual boot setup .
androidonlinx said:
I just thought what's the worst that could happen and flashed the bios. it worked. installing android and windows now.
EDIT: Android works. If anyone wants to know how I did this, please reply
Click to expand...
Click to collapse
Windows works. .linxtablet.co.uk/viewtopic.php?f=49&t=1462&p=8748#p8748 is a guide. I am that user.
Can you just flash the android with this? I've no need for windows but if you could please share some info on the procedure.
Thanks
redeyes_ni said:
Can you just flash the android with this? I've no need for windows but if you could please share some info on the procedure.
Thanks
Click to expand...
Click to collapse
Check my 'link' to LinxTablet forums. You have to flash both but you can just ignore Windows and have a 16GB android partition.
androidonlinx said:
Check my 'link' to LinxTablet forums. You have to flash both but you can just ignore Windows and have a 16GB android partition.
Click to expand...
Click to collapse
Done all that which was handy enough so thanks but the android partition is only showing up as:
Internal Storage
Total Space: 4.36GB
I've loaded some apps which leaves me 2 GB free.
The only other partition is the external SD. Is there something I need to do to get the rest of the 16GB? Seems to me that it hasn't mounted or partitioned the internal memory correctly. The tablet is 32GB and I'm not concerned at just using the 16GB for android but with 2 GB left it's going to be a bit tight for apps.
Thanks again, any help would be appreciated.
I'm not sure. I'll check mine tonight but I remember having more storage than that. Are you sure your tablet is a 32gb version
Try using Minitool or Easus on the Windows side to resize the android partition if you can, or even just view the layout.
KitKat lacks support for apps to extsd. Root would mean we can fix this. The device does not support USB as port is otg and charge only so root has to be done with APK on tablet or on offline android fs from Windows. Anyone know how to root?
EDIT: checked. I have 3.43 GB free. Sorry, should have checked earlier. Android system takes up 2GB not shown, storage is only 28GB after bootloader, BIOS partition huge due to touch support in menus plus unnecessary drivers, plus I imagine the EFI partition was wrongly sized. This is fine for me, but will look into when I am working on Android again.
Currently not working on Android any more (fruity-based desktop OS port instead) but will come back to it. Hoping to also create an Androidx86 build to avoid BIOS flashing, but the BIOS flash does mean you have 64bit EFI on the Android side so can boot Win7, Darwin (you know what I mean ) and Ubuntu without modification.
Still looking to root. Anyone?
androidonlinx said:
I'm not sure. I'll check mine tonight but I remember having more storage than that. Are you sure your tablet is a 32gb version
Try using Minitool or Easus on the Windows side to resize the android partition if you can, or even just view the layout.
KitKat lacks support for apps to extsd. Root would mean we can fix this. The device does not support USB as port is otg and charge only so root has to be done with APK on tablet or on offline android fs from Windows. Anyone know how to root?
EDIT: checked. I have 3.43 GB free. Sorry, should have checked earlier. Android system takes up 2GB not shown, storage is only 28GB after bootloader, BIOS partition huge due to touch support in menus plus unnecessary drivers, plus I imagine the EFI partition was wrongly sized. This is fine for me, but will look into when I am working on Android again.
Currently not working on Android any more (fruity-based desktop OS port instead) but will come back to it. Hoping to also create an Androidx86 build to avoid BIOS flashing, but the BIOS flash does mean you have 64bit EFI on the Android side so can boot Win7, Darwin (you know what I mean ) and Ubuntu without modification.
Still looking to root. Anyone?
Click to expand...
Click to collapse
Thanks man. I'll try to resize the partition if/when I need it. Great work, well appreciated.
androidonlinx said:
Currently not working on Android any more (fruity-based desktop OS port instead) but will come back to it. Hoping to also create an Androidx86 build to avoid BIOS flashing, but the BIOS flash does mean you have 64bit EFI on the Android side so can boot Win7, Darwin (you know what I mean ) and Ubuntu without modification.
Still looking to root. Anyone?
Click to expand...
Click to collapse
Any bugs to note with the *toshing?
Rooting wise I can see two options. 1. mount the android system in windows with ext2 viewer or something and root it manually using a SuperSU.zip or better yet with linux (to avoid permissions issues). 2. Is there any other stage in the android boot process that you can halt it at? Dnx mode or droidboot (I'm assuming similar setup to chuwi vi10), where perhaps the usb will work in slave mode and it is identified as a fastboot device, allowing you to flash a custom recovery/root.
HypoTurtle said:
Any bugs to note with the *toshing?
Rooting wise I can see two options. 1. mount the android system in windows with ext2 viewer or something and root it manually using a SuperSU.zip or better yet with linux (to avoid permissions issues). 2. Is there any other stage in the android boot process that you can halt it at? Dnx mode or droidboot (I'm assuming similar setup to chuwi vi10), where perhaps the usb will work in slave mode and it is identified as a fastboot device, allowing you to flash a custom recovery/root.
Click to expand...
Click to collapse
Good idea. The flash is done using droidboot but I cannot get back into recovery again
androidonlinx said:
Good idea. The flash is done using droidboot but I cannot get back into recovery again
Click to expand...
Click to collapse
If its anything like the vi10 then Dnx mode is volume up and power from device off. Volume down and power is Windows/Android switcher. Volume down once the android logo appears will boot into droidboot.
Then there is the question of if you have a working custom recovery to flash, I think any of the baytrail recoveries from Dell/Chuwi etc. devices would work - will a kernel change if needed, and if the buttons work to enter recovery.
HypoTurtle said:
If its anything like the vi10 then Dnx mode is volume up and power from device off. Volume down and power is Windows/Android switcher. Volume down once the android logo appears will boot into droidboot.
Then there is the question of if you have a working custom recovery to flash, I think any of the baytrail recoveries from Dell/Chuwi etc. devices would work - will a kernel change if needed, and if the buttons work to enter recovery.
Click to expand...
Click to collapse
Will try this when I next have some spare time and my Linx to hand.
Knowing the reputation if Cube it wouldn't suprise me if the stock recovery allowed custom zips but otherwise I will try and flash another recovery from a similar tablet.
I'll take another look on 4pda to see if they have achieved root there too
Thanks again
I have root if anyone is interested email me on [email protected]
HypoTurtle said:
If its anything like the vi10 then Dnx mode is volume up and power from device off. Volume down and power is Windows/Android switcher. Volume down once the android logo appears will boot into droidboot.
Then there is the question of if you have a working custom recovery to flash, I think any of the baytrail recoveries from Dell/Chuwi etc. devices would work - will a kernel change if needed, and if the buttons work to enter recovery.
Click to expand...
Click to collapse
I got root working on my linx7 with the icube dual boot email me and I will tell you how
Hi mate, I found you late but really wants to know how to install Android in Linx 7, I don't wan windows at all, please reply
Thanks
U
onlinejobwork said:
Hi mate, I found you late but really wants to know how to install Android in Linx 7, I don't wan windows at all, please reply
Thanks
U
Click to expand...
Click to collapse
Go to linxtablet.co.uk I put my work on there it does mean flashing the bios so backup your product key also the Android partition is only 4gig so you can dual boot and have both I did find a way of making it 8gig but it was messy and buggy
[email protected] said:
Go to linxtablet.co.uk I put my work on there it does mean flashing the bios so backup your product key also the Android partition is only 4gig so you can dual boot and have both I did find a way of making it 8gig but it was messy and buggy
Click to expand...
Click to collapse
any direct link please ?
onlinejobwork said:
any direct link please ?
Click to expand...
Click to collapse
http://linxtablet.co.uk/viewtopic.php?f=4&t=2096
I'm trying to set up Phoenix OS, first on a USB3 stick, then I want a partition install/dual boot.
I have an HP Elite X2 1012 G1 tablet/2-in-1. I can get the USB to boot if I write it from the .iso with RUFUS, but for a few problems.
1.) No persistence. How do I set up persistence? I found some instructions to use toporesize to create a data.img file, but that just makes it get stuck at A N D R O I D text.
2.) Can't seem to add Google account (this is the MOD w/ gapps and root .iso from the Phoenix forum that's available right now). I click settings -> accounts -> google, and it goes back to the accounts screen and then I can't click anything.
3.) Due to required FAT32 formatting for the USB, I can't create a persistance file > 4Gb.
Once I can prove I can clear these issues, I'd like to create a partition and install this as a dual-boot solution. To the best of my knowledge (not having tried this), any method of installing this will mess with my MBR and install grub. I DO NOT WANT THAT. I would prefer to use the windows boot loader for a number of reasons. Is there any way to make this happen?