So, apparently owners of the HTC Rhodium (Touch Pro 2) can dual boot OSes now. Here is the quote "Reefermattness has created a package that quickly installs the updated Android package for the GSM and CDMA Rhodium, also known as the Touch Pro 2.The package also includes the famous Gen. Y Dualboot application by Yozgatg, which makes it possible to choose your OS at startup." found here http://www.xda-developers.com/android/new-dualboot-xdandroid-package-for-gsmcdma-rhodium/
Question is, CAN THIS HELP US? I know it would be awesome to dual boot ROMs. So, can a DEV take a look and see if this can be done with the Hero as well?
I think we'd be running short on ROM space if we tried that.
Yeah, the CDMA Hero system space isn't too big. Those Touch Pro2 guys have more space to work with, as in enough to dual boot. We barley even have enough to install roms.
The android files are stored on the SD card in a dual boot scenario also. I also don't believe it's true dual boot. You have to boot into WinMo first, then run an executable that loads the Android image. The Gen. Y Dual Boot application actually loads after WinMo loads as well I believe.
black7 said:
The android files are stored on the SD card in a dual boot scenario also. I also don't believe it's true dual boot. You have to boot into WinMo first, then run an executable that loads the Android image. The Gen. Y Dual Boot application actually loads after WinMo loads as well I believe.
Click to expand...
Click to collapse
You're right. True dualboot is like Boot Camp on a Mac, it loads into a bootloader BEFORE any operating system and you choose which OS you want to boot into. Booting into WinMo and then into Android isn't true dual boot.
I dont really care about TRUE dual boot. As long as you can get 2 ROMs, that would be cool
wow I'm surprised its news, back in the TP1 days we could boot into a less than functional version of android from Winmo...
Related
Is there a CDMA Hero equivalent to HaRET for temporarily booting into a 2.x build to nondestructively play with it? I'd love to play with 2.1, but I don't want to completely give up having a camera.
Alternatively... if there's no way to do it from a (rooted) stock Sprint ROM, can a HaRET-like boot go in the OTHER direction? IE, flash an experimental 2.1 ROM onto a rooted CDMA Hero, then temporarily boot from IT into the stock Sprint ROM (or any other ROM that has camera working) on the uSD card?
miamicanes said:
Is there a CDMA Hero equivalent to HaRET for temporarily booting into a 2.x build to nondestructively play with it? I'd love to play with 2.1, but I don't want to completely give up having a camera.
Alternatively... if there's no way to do it from a (rooted) stock Sprint ROM, can a HaRET-like boot go in the OTHER direction? IE, flash an experimental 2.1 ROM onto a rooted CDMA Hero, then temporarily boot from IT into the stock Sprint ROM (or any other ROM that has camera working) on the uSD card?
Click to expand...
Click to collapse
Lots of people here are just using nandroid.
Make a nandroid backup of "good Phone" then load 2.1 when your done, throw your backup back on the phone. In other words, we don't have a virtualization thingy yet or even a really nifty boot loader.
2.1 is fun, but all the cool stuff is yet to come-- IE: Camera, Multi-touch, OPEnGL 3d stuff. It works as a phone, but thats about all its good for.
Hmmm. Is that just because nobody has had the time to write a program like HaRET for HeroC, or is there something fundamentally different about the way Android is flashed, boots, and runs on our phones compared to Windows Mobile that makes a HaRET-like program more or less impossible to pull off the same way?
It does seem like kind of a cruel irony that booting Android from a theoretically proprietary phone running WinMo is trivially easy, but our allegedly open phones won't give us the freedom to pull off the same trick to boot a newer build of the same theoretically open OS.
HaRet has been around a long time - and so has Windows CE, from which HaRet came. Android is relatively new, and flashing images back and forth is so easy there doesn't seem to be much need for that sort of tool.
miamicanes said:
Hmmm. Is that just because nobody has had the time to write a program like HaRET for HeroC, or is there something fundamentally different about the way Android is flashed, boots, and runs on our phones compared to Windows Mobile that makes a HaRET-like program more or less impossible to pull off the same way?
It does seem like kind of a cruel irony that booting Android from a theoretically proprietary phone running WinMo is trivially easy, but our allegedly open phones won't give us the freedom to pull off the same trick to boot a newer build of the same theoretically open OS.
Click to expand...
Click to collapse
Well, if you think about it, Nandroid is exponentially better than a HaRet counterpart. The major drawback to HaRet is that it loads on top of the already loaded OS, which strains the already stretched system resources. It was good for checking Linux out on a Windows Mobile OS, but we can basically do the same thing using Nandroid, but have the benefit of all resources being dedicated to the ROM we're testing out. So, I guess I always kinda thought of nandriod as a HaRet-like loader, but I guess it's all in how you look at it
I don't think there is anything that stops is from it,0other than no need. Also we have only been working on hero stuff for about 3 months on the cdma side, still have lots pa stuff we can do.
Can you dual boot or any other way to have 2 different roms installed at the same time,so i can switch back and forth?Like windows either at boot or logging in and out of 2 different desktops.
Maybe find a way to split the partitions.Any suggestions would be great.
Duel= 2 roms fighting. Make it dual. Thought it was funny, no malice intended.
lol - duel - dual...
It would be interesting if that was possible. There would have to be another program in there to act as the buffer between both OS's though - that would take control of the start-up, hold on a page that has both options and then would boot the option you want.
Not sure if that's possible since some files are right on the root and in order to have an OS work it can't have files in the same directory - they would just overwrite each other.
But, I too, have wondered if it would ever happen. Be a great way to test new ROM's if you didn't always have to overwrite the existing ROM but rather, you could place a new ROM in a special directory and then run it from that - or partition the internal memory with the new partition available to boot from and store.
partition the internal memory with the new partition available to boot from and store.
Click to expand...
Click to collapse
Thats exactly what i was thinking,partition the system os,i rebuild computers and a little system modding in windows,but this is a linux based os,so it would be a little odd for me.I'm gonna look into this a little more.
You may try to contact the guys who developed boot manager. www.init2winitapps.com they have a listing of supported devices and a request form. Works on the thunderbolt 5 slots for 5 roms, I'm unsure how difficult it would be to add support for the iconia.
Sent from my A500 using XDA Premium App
ibsk8 said:
You may try to contact the guys who developed boot manager. www.init2winitapps.com they have a listing of supported devices and a request form. Works on the thunderbolt 5 slots for 5 roms, I'm unsure how difficult it would be to add support for the iconia.
Sent from my A500 using XDA Premium App
Click to expand...
Click to collapse
Thanks,i submitted the idea,lets see if they will run with it,hopefully they will find interest.
Hello Diabblo,
Any update on that?
I think the idea of dual boot (or 5al boot) is just fantastic!
I have beside my iconia a501 a poor old zt180s and it can triple boot on android, ubuntu and WinCE!
Best,
Inji.
inji75 said:
Hello Diabblo,
Any update on that?
I think the idea of dual boot (or 5al boot) is just fantastic!
I have beside my iconia a501 a poor old zt180s and it can triple boot on android, ubuntu and WinCE!
Best,
Inji.
Click to expand...
Click to collapse
Im guessing that device has a open non encrypted boot loader. The Iconia was encrypted at birth with the 3.2 push they tightened security even more from whqt I have read.So this is likely never happening unless acer changes ttjere boot loader policy.not likely to happen.
hope this helps you understand more of this issue.
I'm dual-booting my A500 right now with ICS and Ubuntu. The method for dual-booting is a replacement recovery.img which contains a Linux kernel and acts as a bootloader for Linux. Ubuntu itself runs from a rootfs.img on the internal storage (there's also recovery.img's available to run from external SD too). If I want to run Android, I just boot my tab normally. When I wanna run Ubuntu, I hold vol+ as I'm turning it on to force the modded recovery to load. It's a pretty cool setup more info in this thread: http://forum.xda-developers.com/showthread.php?t=1158260
Dear Erica Renee and Bloodflame,
Thanks a lot for your answers. Ok, I got it with the encrypted bootloader.
Will try the method described by Bloodflame.
Actually, since I got these tablets my main use of them is flashing new ROMs... I don't really have the use of new ROMs but I think it's so exciting!
Cheers,
Inji.
I don't believe the encryption is the problem.
The current boot loader is available unencrypted in update packages if anyone want to have a look at it.
Replacing the boot loader on the device is done as part of a down grade procedure described elsewhere on this forum.
So unless I'm missing something, the problem is more likely time and interest. Someone need to care enough about it and have the time to make some other boot loader work. Or patch Acer's. Either way it is likely to require quite a bit of time and patience.
So let me see if I have this correct. Acer's hardware bios code is 'locked down' enough to keep the average code manipulator out? A custom boot loader needs to be dev'd that can communicate correctly to be able to handle Android recovery and a linux/android boot screen etc. ? Could someone elaborate more blatantly if I am incorrect...
I'm curious if the more informed believe that it will be possible to have CM9 (whenever it comes out) alongside the Kindle's default install. And has anyone discussed modifying the Kindle's android install itself since it was "open sourced"?
I don't know Dual booting an Android OS is possible at this time. It would be possible to dual boot say Linux or windows with an Android OS because of the Boot records inherent in each OS. But this doesn't currently exist in Android OS.
I could be completely wrong though. Let me do a little more research and I'll see what I can help with.
I have been trying some ICS SD Roms.
I have a dual boot application which gives the option to go into Android or windows 6.5.
This doesn't work with ics as the ics rom files are placed in ics folder and i presume the dual boot application is looking for Android.
Is there a similar app so that you can dual boot from ics and windows 6.5.
Have looked but couldn't find
thanks
as91 said:
I have been trying some ICS SD Roms.
I have a dual boot application which gives the option to go into Android or windows 6.5.
This doesn't work with ics as the ics rom files are placed in ics folder and i presume the dual boot application is looking for Android.
Is there a similar app so that you can dual boot from ics and windows 6.5.
Have looked but couldn't find
thanks
Click to expand...
Click to collapse
What program are you using?
Have you tried putting them ion a folder called android and changing "rel_path= ics" to "rel_path=android"?
Or you could always use MAGLDR.
as91 said:
I have been trying some ICS SD Roms.
I have a dual boot application which gives the option to go into Android or windows 6.5.
This doesn't work with ics as the ics rom files are placed in ics folder and i presume the dual boot application is looking for Android.
Is there a similar app so that you can dual boot from ics and windows 6.5.
Have looked but couldn't find
thanks
Click to expand...
Click to collapse
Yep, do what the previous guy said. In startup.txt in the 'ICS' folder, there is a line saying rel_path= ics. Change this to rel_path= Android, then rename the folder with your build in it to 'Android' and it should run fine. The app should also have an option to change the boot location if I'm not mistaken (although it's been ages since I used WinMo/Android SD)
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