Related
I have tried both Incubus26jc's Super Froyo (RLS8) and VaniljEclair RLS7c . I manage to install them in sd card (I want to use them via haret.exe) but when I reach the welcome screen where I have to touch the android to continue, the screen does not respond ( D-pad and center button work). Could someone help me? I decided to open a new thread because of what I have searched, I found only one member with a similar (but not the same) problem
The installation method I follow is this (mostly copied from a SuperJMN's post):
1º Run HaRET
2º From the installer, select Install System
3º Choose install update (if any)
4º Choose to fix permissions (if there had been an update)
5º Reset (don't select "Quit", just reset, this is to avoid problems)
6º Wait for Windows Mobile to start and run HaRET again.
Although I am flashing to nand and you are using haret/zimage, we may have the same problem with the unified touch screen driver that DZO implemented around 16 June. Is there is a way to use the kernel .nbh and system .tar with haret, rather than zimage? If so, you might try using an older kernel from before 16 June ... or perhaps an older zimage.
I have similar problem, if not the exactly the same. Using an older kernel seems to be a workaround of this problem. hxxp://forum.xda-developers.com/showpost.php?p=7041656&postcount=21 (You need to fix the hxxp as appropriate as I am not allowed to link URL yet)
i have the similar problem too, havent fixed it :/
I tried zImage-12-06-10 (the last one before the 16th of June) and installation procedure did not even start. But zImage-29-04-10 worked for me. However, Froyo is not that fast. If I change any files (zImage or something else) is it possible to have a speed improvement?
Same problems.
All Android realeases work on my pola100 only with zImage 29.04.10.
No work with other kernel.
I suggest to developers to analyse 29.04.10 and try to understand WHY this works and others no.
Regards.
regarding screen response, panel and changes on kernel module for touchscreen please see this post from dzo
also check this for solution from k_k
HTH
mensa07 said:
regarding screen response, panel and changes on kernel module for touchscreen please see this post from dzo
Click to expand...
Click to collapse
Those are the changes after which my touchscreen stopped working.
mensa07 said:
also check this for solution from k_k
Click to expand...
Click to collapse
It would be nice if this worked for the Polaris ... how would I change the value of this parameter before flashing the kernel? Thanks!
tmcfarland said:
Those are the changes after which my touchscreen stopped working.
It would be nice if this worked for the Polaris ... how would I change the value of this parameter before flashing the kernel? Thanks!
Click to expand...
Click to collapse
you can use terminal or adb to change the value
files for a fast android version
Could someone with a fast and stable version of eclair or froyo please tell us what files did he/she used to make that happen because I installed incubus froyo build and it is a bit slow? I am talking about installing it in my sd card and run it using haret.exe
Hello, since there seems to be some confusion I decided to start this thread for the 32A port.
The G1 / Magic 32B thread is here: http://forum.xda-developers.com/showthread.php?t=776922
Note that all the work on PSFreedom was done by KaKaRoTo, and he was helped by DrMon in the MSM72K port, i merely compiled their work and put it in a simple package for everyone to enjoy.
I created 2 packages, an enabler and a disabler, that you have to flash over your working CM 6.0 Final installation.
Flashing the enabler will install the modded kernel and PSFreedom module. You will lose usb functionality completely (no adb, no mass storage etc.) until you flash the disabler.
After flashing the enabler the module will always start upon boot, you have to enter no commands on the terminal emulator.
[SIZE=+2]HOW TO:[/SIZE]
Preliminary: Make sure you are on CyanogenMod 6.0 Final and everything is working correctly. It has been reported that it works also with older CM6 versions and CM5 too, you may try if it works and report it in this thread. If it's the first time, do a Nandroid backup before testing!
Download these files: http://www.multiupload.com/MY1LOGZ6YP (32A-Enabler), www.megaupload.com/?d=3UU2L0UX (32A-Disabler)
Put them on your SD card
Reboot into recovery and Flash Enable_PSFreedom_32A.zip
Reboot
Now psfreedom should be loaded as a module, you will see no difference, except for the loss of normal usb functions.
To run the exploit:
Make sure you are on 3.41 (DO NOT UPDATE OVER THE NETWORK!)
Connect the phone to the PS3 using usb
Turn it off completely (unplug power cable or turn off back switch on Fat models)
Plug it back in (turn on back switch)
Turn it on and immediately press the eject button (you should hear 3 quick beeps)
Booting should take a bit longer (5-10 seconds)
If you see two new options under the games tab, the exploit worked. You can now unplug the phone. Mind that you will have to do this procedure every time you boot your PS3. Try using another USB cable if it doesn't work with a few tries.
To uninstall:
Boot back into recovery
Flash Disable_PSFreedom_G1.zip
Reboot
You should have usb functions back to normal.
Payloads:
This version of PSFreedom contains the new PSGroove 1.1 payload (peek & poke)and is enabled for backups, but backup manager talk should not be done on this thread, there are other boards for that.
If you want to try other payloads (F.I. the new AerialX's apploader), you just have to load it into /proc/psfreedom/payload . You can do it by typing:
Code:
cat payload > /proc/psfreedom/payload
The payload can be wherever you want and has to be in the classic binary format. (just remember to substitute "payload" with the correct path).
Even better, if you put the new payload in the /data/local directory, named "payload" (no quotes), it will be automatically loaded upon startup, thus becoming the default payload.
Mirrors:
Code:
Enabler: http://depositfiles.com/en/files/o1qpcbkeo
http://www.zshare.net/download/80630364707ab8fe/
http://rapidshare.com/files/420315547/Enable_PSFreedom_32A_v3.zip
Disabler: http://www.zshare.net/download/801637791c6185b2/
Versions:
Code:
v0: initial release
v1: +module loaded on startup
+created disabler
v2: updated payload (peek & poke)
v3: resolved bootloop bug, updated PSFreedom, dynamic payload loading.
reserved (10 characters long)
Thanks for yours work!
What about an application to enable/disable psfreedom? Will it be possible in the future?
My Magic (32A) does just reboot over and over after flashing the enabler.......also after flashing the disabler........so now restoring (i ALWAYS back-up befor flashing anything!)
But thanks for trying!
radio version for cm6
one question, CM6 can be for New Radio, or just Old radio?
H3llSp4wN said:
one question, CM6 can be for New Radio, or just Old radio?
Click to expand...
Click to collapse
there's a port also for new radio showthread.php?t=723520
But there are some issues (like broken camera)
Old Radio, new radio requires a different kernel.
For the app, for now psfreedom requires a modded kernel, and it is not possible to switch them on the fly using an app. I know they're working on using a different driver, to avoid having to recompile the kernel. Still don't know if it can be done though.
Can anyone provide a mirror please?
cm6
i'm just a bit confused about what cm6 rom should be better and should i use, because there are severeal releases (minimou, redux etc).
can u give me a tip about this?
best regards
I always use the vanilla one, straight from the cyanogenMod forums. I think it should work with any of those versions though. Just make sure you're on old radio and you make a nandroid backup before trying.
got everything right now.
thanks for the mirror.
Got a question? Does the mt3gs use the msm72k also and why is it not on the port list? Sorry I'm probably in the wrong area but thought I would try
Hi , just have a question , looked arround with google , couldn't find my answer, maybe someone here knows,
Before trying this out, I would like to know if I can revert my ps3 to original state,
or to how it was before running psgroove?
yes as the exploit must be ran on every boot so simply reboot and delete bxxm
H3llSp4wN said:
i'm just a bit confused about what cm6 rom should be better and should i use, because there are severeal releases (minimou, redux etc).
can u give me a tip about this?
best regards
Click to expand...
Click to collapse
i use redux and it works for me (i still use the release that u have to do thru the terminal)
focus400hp said:
Got a question? Does the mt3gs use the msm72k also and why is it not on the port list? Sorry I'm probably in the wrong area but thought I would try
Click to expand...
Click to collapse
MT3G is 32B, so head off to the Dream section and get that one instead.
with cm6 my g1 go in loop... why?
Hey guys, I'm running into a little trouble after installing the PSFreedom enabler. My htc magic 32a (3.5mm jacket) just sits on the "HTC Magic" screen for eternity after flashing PSfreedom. I do have CM 6.0 installed, I believe its from Cyanogenmod 6.0 S/D version, I don't know what ebi I am nor if need to do something with kernel, but I just know I go into recovery, flash PSfreedom enabler, reboot, the "htc magic" logo shows up and then it sits there forever...Is there something I'm doing wrong?
@ repukken, rock187. You should use the 32B port. The link is in the first post.
Lollipop_Lawlipop said:
MT3G is 32B, so head off to the Dream section and get that one instead.
Click to expand...
Click to collapse
its mt3g slide i believe its different though i did use the precompiled for the dream 32b on a g1 yesterday and works very well and with no probs at all still want to see something for the slide. i asked in the slide forums and everyone just had s*** to talk really
As lately some people are asking me about ROM porting I decided to create this new thread where we can share knowledge about this hard task.
Please note this is a Dev talk thread, so DON'T ASK about fixing a particular ROM problem here. Also don't ask questions like "My phone is bricked! please help!". This IS NOT the appropriate place for it. There are plenty of other threads to help you out.
Also note that this is not a step by step guide (and not a guide at all), it's just a point where you can start from. Android is a very complex system and there are many things I don't know yet. So, research and hard work is what you need to learn it deeply. My first tip is Google really works. Don't be afraid to search
Ok, to the basics. Porting a ROM is no simple task. It requires advanced understanding of how android works and how it is organized. Previous Linux/Unix knowledge helps A LOT. As android is based on this O.S. there are many similarities between both. In fact many ppl consider android to be a kind of linux distro.
The very first task to port a ROM is finding a device which is compatible with your own. For example Defy/Milestone2. Then you are going to choose a ROM to port to your device.
As our devices (Milestone2) have a locked bootloader we now need to find a system image that have a compatible kernel with the ROM we are trying to port. This is mainly based on trial and test and takes a long time. You'll be ending flashing your phone several times with RSD Lite. You should learn how to use MotoAndroidDepacker and how to create a fixed SBF.
The basic procedure to try that:
1. Open original ROM update.zip and remove any files/commands that flashes boot/devtree/recovery/anything.
2. Install this new file on your phone via CW Recovery.
3. Boot into bootmenu and enable ADB so you can read logcat while phone boots.
4. Choose Boot/Normal. If your ROM uses 2nd-init you will need to place/edit/adapt bootscripts into bootmenu 2nd-init folder.
5. Check logcat for errors:
- If you're getting HAL errors you're going to need a new kernel;
- If you can start android without getting HAL errors but still getting errors and bootloop on android animation you should try to replace libs with appropriate original ones.
6. Once you are able to boot android you should test it's features to see what needs to be fixed.
This is what I have to say for now. The thread is now open for discussion.
At this week, motorola has just pushed the GB official update for Droid 2 and Droid 2 Global....
Can i try to port this new rom to milestone 2 and after a success boot, fix the radio..??
I was asking that, because some people has success on port CM7 to milestone 1, when it originally maked for droid 1...
tks a lot..!!
jorgebaruchi said:
At this week, motorola has just pushed the GB official update for Droid 2 and Droid 2 Global....
Can i try to port this new rom to milestone 2 and after a success boot, fix the radio..??
I was asking that, because some people has success on port CM7 to milestone 1, when it originally maked for droid 1...
tks a lot..!!
Click to expand...
Click to collapse
It may be possible, but you'll have a hard time fixing the baseband.
You may have to mod the init.rc scripts and find the right radio binaries (rild is one of them) and drivers.
Ask those ms1 people for help, if they are still with the same phone...
Sent from my Milestone 2 XDA App
I don't know if this will be relevant or not.
I wanted to know if to do any of this, having a Linux distro as OS a must or can I try my hands at it on a windows based machine. I mean I'm sure that a Linux distro will give certain advantages (as Android is based on UNIX/Linux) but can we get things to work a 100% on windows.
If yes, then will someone be kind enough to get give the list of all softwares etc. which will be required to do the job on Windows machine as well as a Linux machine.
I do know a few softwares but I'm not sure if I have an exhaustive list. I would like to learn and try and at least be able to modify in bits n pieces to begin with.
I apologize if this wasn't supposed to be asked in this thread.
The only thing i can get from SBF is a bunch of smg files.
But the only ones i can open are
preinstall.smg
CG39.smg
Is there a way to open/see the rest?
2)
Im trying to modify the CM7 rom, what boot does it use? 2nd-init or 2nd-boot?
i guess it is second-init. but not sure
thanks a lot for this !!!
WeeDv2 said:
The only thing i can get from SBF is a bunch of smg files.
But the only ones i can open are
preinstall.smg
CG39.smg
Is there a way to open/see the rest?
2)
Im trying to modify the CM7 rom, what boot does it use? 2nd-init or 2nd-boot?
Click to expand...
Click to collapse
SMG files are disk images of certain partitions of your flash memory.
You can only open CG39.smg and preinstall (CG66.smg) because they are the only images in ext3 format. The rest of images may be on ramdisk format or some proprietary format. For more details on partition codes take a look here:
http://and-developers.com/partitions:cdt
You may be able to open and see contents of other partitions but the only one that matters aside from system and preinstall is the boot partition (CG35.smg), which contains the init scripts we should mod in order to make they work with 2nd-init. Boot partition is in ramdrive format. More details here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://elinux.org/Android_on_OMAP
It is easier to unpack boot image using Dsixda's Kitchen here:
http://forum.xda-developers.com/showthread.php?t=633246
Edit: To see what boot your CM7 uses just go inside /system/bootmenu/config and look for a file called default_bootmode.conf. That should be the boot method used. It's normally 2nd-init.
sahilarora911 said:
I don't know if this will be relevant or not.
I wanted to know if to do any of this, having a Linux distro as OS a must or can I try my hands at it on a windows based machine. I mean I'm sure that a Linux distro will give certain advantages (as Android is based on UNIX/Linux) but can we get things to work a 100% on windows.
If yes, then will someone be kind enough to get give the list of all softwares etc. which will be required to do the job on Windows machine as well as a Linux machine.
I do know a few softwares but I'm not sure if I have an exhaustive list. I would like to learn and try and at least be able to modify in bits n pieces to begin with.
I apologize if this wasn't supposed to be asked in this thread.
Click to expand...
Click to collapse
Don't worry, this is the right place
As for your question: yes you can work in windows if you like, but using at least a Linux VM is more productive. I don't have a full list of applications to give you, as different mods may require different tools, but I advice you to have at least:
- Notepad++ (essential for editing text files and keeping linux end-line format);
- dsixda's Android Kitchen (http://forum.xda-developers.com/showthread.php?t=633246)
- 7zip (or some other compress tool you like)
- Moded putty for ADB as working with windows command prompt really suck (http://forum.xda-developers.com/showthread.php?t=803225)
- Oracle Virtual Box (if you are going to use linux VM).
r2beta0 said:
SMG files are disk images of certain partitions of your flash memory.
You can only open CG39.smg and preinstall (CG66.smg) because they are the only images in ext3 format. The rest of images may be on ramdisk format or some proprietary format. For more details on partition codes take a look here:
http://and-developers.com/partitions:cdt
You may be able to open and see contents of other partitions but the only one that matters aside from system and preinstall is the boot partition (CG35.smg), which contains the init scripts we should mod in order to make they work with 2nd-init. Boot partition is in ramdrive format. More details here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://elinux.org/Android_on_OMAP
It is easier to unpack boot image using Dsixda's Kitchen here:
http://forum.xda-developers.com/showthread.php?t=633246
Edit: To see what boot your CM7 uses just go inside /system/bootmenu/config and look for a file called default_bootmode.conf. That should be the boot method used. It's normally 2nd-init.
Click to expand...
Click to collapse
Thanks again r2beta
thanks r2beta0
- Notepad++ -- got it
- dsixda's Android Kitchen -- downloaded (need some link for a how-to on its usage)
- 7zip -- got it
- Moded putty for ADB -- got it
- Oracle Virtual Box -- can't install Linux on my system as this is a work machine
dunno if I can do without the last option.
sahilarora911 said:
thanks r2beta0
- Notepad++ -- got it
- dsixda's Android Kitchen -- downloaded (need some link for a how-to on its usage)
- 7zip -- got it
- Moded putty for ADB -- got it
- Oracle Virtual Box -- can't install Linux on my system as this is a work machine
dunno if I can do without the last option.
Click to expand...
Click to collapse
Oracle Virtual Box is an application that lets you run an operational system on a virtual machine, in other words, it doesn't install linux on your real computer. It's a very useful tool that I use everyday. Google for it and learn a bit, you won't be disappointed. About kitchen: the link I provided was download + guide. Read it again. If necessary read the full thread.
r2beta0 said:
Oracle Virtual Box is an application that lets you run an operational system on a virtual machine, in other words, it doesn't install linux on your real computer. It's a very useful tool that I use everyday. Google for it and learn a bit, you won't be disappointed. About kitchen: the link I provided was download + guide. Read it again. If necessary read the full thread.
Click to expand...
Click to collapse
I know a bit about virtual box but as I said I'm not allowed to have softwares not approved by the IT team to be present on the system. Though I can get away with small things like notepad++ and 7-zip, having virtual box on my system may raise some eye brows.
I'm trying to arrange an alternative system.
Me neither. I must do almost everything at home, and at this very moment I simply don't have any free time. I'm afraid you're not going to see me here very often anymore (maybe in a few months? a year? well, it might be a bit too late for milestone2...)
hi. Have a question, I want to remove baseband from a flashable zip (lets say, CM7 from Tezet) , is it posible? I dont know where to look for it (baseband). Thanks!!
Baseband is located in \system\etc\motorola\bp_nvm_default\
But don't remove it, just replace it with files from ROM, which have baseband you want.
---UFO--- said:
Baseband is located in \system\etc\motorola\bp_nvm_default\
But don't remove it, just replace it with files from ROM, which have baseband you want.
Click to expand...
Click to collapse
Ok thanks for the info.
Sent from my A953 using XDA
Hi All,
Just a quick question. I have ported Paranoid Android 2.10 to MS2 but the problem I am facing is that Reboot goes through Bootmenu and I have to choose reboot from Bootmenu again.
Any inputs?
Thanks in advance
Megalith27 said:
Hi All,
Just a quick question. I have ported Paranoid Android 2.10 to MS2 but the problem I am facing is that Reboot goes through Bootmenu and I have to choose reboot from Bootmenu again.
Any inputs?
Thanks in advance
Click to expand...
Click to collapse
I meant to get to it last night, but I was tired after work and fell asleep watch tv. Eventually, later tonight, I'll be uploading PA for MS2. Check my Defy PA thread in 12-14 hours cause I'm about to go to work and I'm not gonna feel like making a MS2 PA thread or updating my Bravo PA thread -- but the Defy Thread is always up to date when I put out new roms.
Also, I'm looking to get either a Defy or MS2 -- I've heard that there's 3G issues with AT&T users (which I am) with the MS2 -- Apparently the MS2 has different 3G frequencies than AT&T. Are there any AT&T MS2 users who are knowledgeable about that? While I can deal with no 3G, edge only, calls only -- I need to make sure I can at least do that before I commit to something.
I'd rather have the MS2 because I want a hw keyboard and I don't have the $300+ to try and get a Photon Q LTE from eBay (and I don't have to change up my repos if I get a MS2). If anyone here knows of a phone that's AT&T compatible, Defy code compatible, and has a keyboard, please let me know.
Thanks.
//Normally I'd post the latter half in the Q&A section, but ya'll don't have one so I'm just gonna piggyback
//My Bravo doesn't have a Q&A page either -- it needs one that's not my PM box...Don't PM me on how to root your phone and flash CM7 -- read one of the 5 guides on the first page of both General & Dev...:silly:
Ok devs need some help here.
I am trying to port a rom to our Milestone 2...but it bootloops on rom animation.
I tried to logcat it but I don't think it gets as far as adb server to detect the device.and just keeps saying "waiting for device"...so I end up with no logcat to diagnose the problem.
I can logcat my current working rom but only after the phone boots....am i missing something here? please, help
Any help is very much appretiated.
Thanks a lot in advance
Ive been folowing the tutorial for how to "dualboot" Android And Windows Phone and i use Haret linux loader to boot up to android.
but it doesn't boot up it give's me Kernel Panic And says something with Killing Process
I Tried GB With Raphel 100 (As that's the device i got acording to the reseller) also i dont know how to check it either =/ (When i have no manual or box)
but i still got the same problem and i have followed the tutorial
Edit. Solved Changed to tael rom and worked, EnergyROM has some kernel loading issue
Any Idea?
Can you run haret.exe from the microSD (without the dual boot option)?
R^7Z said:
Can you run haret.exe from the microSD (without the dual boot option)?
Click to expand...
Click to collapse
yes,
If this help's
I got WP 6.5 Energy.
or do i need a more proper tutorial?
I followed thedeadcpu's reake tutorial on youtube
What I'm attempting to troubleshoot is where the problem is by figuring out whether you can run XDAndroid properly without the dual boot option. Basically if it is the script used to run the dual boot program or if somehow you missed a step in setting up XDAndroid. So, what I need to know is if running haret.exe from your microSD on your TP actually works and if you are able to get to the Android home screen. If not and if you are unable to run Android properly, we might have to start from the setup process. I am currently running 29022.Sense2.5.Cookie.2.0.sencity.Jul.06 so I doubt it has much to do with the ROM but there is a possibility there might be an issue with the program itself. However, we need to tackle one thing at a time in order to confirm where the problem is.
R^7Z said:
What I'm attempting to troubleshoot is where the problem is by figuring out whether you can run XDAndroid properly without the dual boot option. Basically if it is the script used to run the dual boot program or if somehow you missed a step in setting up XDAndroid. So, what I need to know is if running haret.exe from your microSD on your TP actually works and if you are able to get to the Android home screen. If not and if you are unable to run Android properly, we might have to start from the setup process. I am currently running 29022.Sense2.5.Cookie.2.0.sencity.Jul.06 so I doubt it has much to do with the ROM but there is a possibility there might be an issue with the program itself. However, we need to tackle one thing at a time in order to confirm where the problem is.
Click to expand...
Click to collapse
well as far as i seen i can run haret but at haret.exe it give's me some end trace
and kernel panic problem, either it freeze or it reboots to windows (how to check exactly what device of raph i got)
EDIT. I got raph100 , i used the setup.txt once had same problem
So it's possible that you are having issues with setting up XDAndroid. My next question is to ensure you are running the most up-to-date bundle of XDAndroid and to find out which version you are running; Froyo or Gingerbread. This way I can direct you to the correct and current location of this bundle. I currently am running a version of Gingerbread and it seems to be all working and last time I checked, Froyo was working as well. The startup.txt file I am using is the one for the RAPH100 and comes from the bundle. Additionally, in order to ensure a good data.img file, I go a step further and leave out the media and Androidapps folders. I also include a ts-calibration file so I can by-pass the calibration step. Let me know if you'd like to know my process. It's simple but yet pretty much 100% effective.
R^7Z said:
So it's possible that you are having issues with setting up XDAndroid. My next question is to ensure you are running the most up-to-date bundle of XDAndroid and to find out which version you are running; Froyo or Gingerbread. This way I can direct you to the correct and current location of this bundle. I currently am running a version of Gingerbread and it seems to be all working and last time I checked, Froyo was working as well. The startup.txt file I am using is the one for the RAPH100 and comes from the bundle. Additionally, in order to ensure a good data.img file, I go a step further and leave out the media and Androidapps folders. I also include a ts-calibration file so I can by-pass the calibration step. Let me know if you'd like to know my process. It's simple but yet pretty much 100% effective.
Click to expand...
Click to collapse
Man youve been to a big help, i changed to TAEL rom, due to EnergyROM was slow, and guess what XDANDROID worked! so i guess it was my rom ^^
Hi
I saw that the TF101 and SL101 are very similar.
On ASUS Website they even provide me with both, TF and SL firmware if I go to downloads.
So my question:
Are any Custom ROMs compatible to both, TF and SL?
Or are there modifications needed?
@Devs: Who's ROM is compatible to SL101?
Use the slider compatibility pack available here: http://forum.xda-developers.com/showthread.php?t=1586382&highlight=slider+compatibility
Then Any tf101 rom works with the slider!
1. Flash ROM
2. Flash slider compatibility pack over it
3. ???
4. Profit.
Thanks.
Another question to ROMs:
I know there is a possibility to run Ubuntu on the TF in dual-boot with android.
What about this on SL101?
If I use this tool: http://forum.xda-developers.com/showthread.php?t=1364095 will I be able to flash the Compatibility Pack afterwards?
And will Ubuntu run clean then?
That may be another matter entirely, as the compatibility pack is for Android 4.0 ICS. I don't think it would help. You can still flash ubuntu, but you may encounter a few bugs, it's an ARM processor build though. It will work, I just can't say whether it would work well or not. Don't flash the compatibility pack with it though.
But didn't I get this right?
I will hae both, Android and Ubuntu on my device then.
I have to flash the comp pack over the Android ROM to get it working perfectly.
So if I use the tool above I install my Android and Ubuntu ROM together. How do I get Android working correctly then?
How does this ubuntu dualboot install?
is it like this:
One half CWM + Android, Other half Ubuntu
or like this:
CWM is above everything and Ubuntu and Android are the next level deeper?
I mean does CWM even have access to ubuntu through normal flash methods?
What if I want to change my android ROM after installing ubuntu? If I just flash using CWM, will I overwrite my ubuntu?
No, the ubuntu zip that you flash simply tells the tab to boot the ubuntu system image you store on your internal memory rather than your android os, your android os is unaffected as you flash the android zip to reboot android.
So I have to flash a zip file every time I want to boot the other OS again?
I mean everytime i want to switch between Ubuntu and Android?
I thought it would be a real Dual-Boot. Unfortunately I am completely new to Ubuntu. The last time I had a dual-booting device was my HD2 with Windows and Android using MagLdr... I thought it would be similar to this.
//Edit:
http://forum.xda-developers.com/showthread.php?t=1191141
If I install in dual boot config did I get that right:
It replaces the ClockWorkMod/Recovery Boot-Option with buntu boot option?
So I will be able to boot Android (normally), Ubuntu (by starting recovery) or flash a new ROM through NVFlash. But I will loose ClockWorkMod
I don't want to spam the thread with this so I ask here. Excuse me for this please.
Yes that is correct, Make Sure, you have NvFlash though. Otherwise you'd be pretty stuck in the event of an issue