Database Users

Full OpenAOS Boot Menu Instructions

Full OpenAOS Boot Menu Instructions
Index:
Thanks/Index
Install the SDE
Install Boot Menu
Install Cyanogen
Install Urukdroid on the openAOS Boot Menu
Editing the menu.lst
Videos
Links
Any one could say to me how to link posts inside a Thread? without opening a new tab?
Thanks:
Thanks goes to:
msticninja for give me Instructions how to install Urukdroid on the Menu.
Bubu for creating the openAOS Boot Menu and Cyanogen.
$aur0n for creating Urukdroid.
vantoman for telling me the right init.rc mounting line for urukdroid.
AlaskaPardus for telling me how to install gapps on cyan.

Install the SDE
Install the SDE
The SDE is a "Special Developer Edition"(=SDE) - Firmware, from Archos, usually only for Developers.
It cames with the Angstrôm Linux-Distribution.
You can use the normal Archos Android, if you have the SDE installed.
Warning, you will loose your Warranty by installing this firmware!
Your device will be watermarked after installation, so Archos can detect that you have installed the SDE!
Installing the SDE:
1) Shut down your Archos.
2) Boot your Archos by holding down the Volume Up ( + ) Button.
3) You will get to the Recovery Menu. You can navigate with the Volume Buttons and the Power Button.
4) Choose "Update Firmware" and connect your Archos with your PC (USB).
5) Download the SDE Firmware here: http://www.archos.com/support/support_tech/_ppp.html?country=de&lang=de&p=gen8
6) Copy the firmware_archos_android_gen8.aos file to your Archos and press the Power Button once.
7) Your Archos now install the SDE Firmware.
8) When you Boot up, your Archos will normally Boot the normal Archos Android, but if you hold down the Volume Down ( - ) Button during Boot Up, you will see the "Boot Menu". (This isnt the openAOS Boot Menu!)

Install Boot Menu
The openAOS Boot Menu, developed from Bubu, allows you to Boot multible OS (f.e. Archos Android,Linux,Cyanogen,Urukdroid,etc...)
Install the Boot Menu:
1) Shut down your Archos.
2) Boot into the SDE Boot Menu by holding down the Volume Down ( - ) Button.
3) Choose "Recovery System" >> "Developer Edition Menu" >> "Flashing zImage and Initramfs".
4) Connect your Archos with your PC (USB).
5) Download the lastest openAOS Boot Menu files (zImage & initramfs.cgio.gz) from here: http://download.openaos.org/bubu/gen8/
6) Copy these two files to your Archos and press the Power Button once.
7) Your Archos now flashes the Boot Menu`s zImage and initramfs.
8) From now on, when you Boot Up your Archos, the openAOS Boot Menu, will showed you can navigate trough the Menu with the Volume Buttons and the Power Button.
9) From standart you will be able to choose between "Archos" (Normal Archos Android) and "Angstrom" (SDE Linux Distribution)
Please often look into the download archive of Bubu ( http://download.openaos.org/bubu/gen8/ ) for a new version of the Boot Menu!

Install Cyanogen
Install Cyanogen
"CyanogenMod is an aftermarket firmware for a number of cell phones
based on the open-source Android operating system.
It offers features not found in the official Android based firmwares of vendors of these cell phones."
(from cyanogenmod.com)​
You can use the lastest Cyanogen version (based on Android 2.3.4 Gingerbread) with the openAOS Boot Menu. (Both systems are from Bubu)
Install Cyanogen
1) Boot into normal Archos Android and connect it with your PC.
2) Download the lastest Cyanogen *.img file from here: http://download.openaos.org/bubu/gen8/android/
3) Once your downloaded the lastest *.img file from there, you have to rename it to "openaos-gingerbread.img.
4) Now copy that file into the root of your Archos.
5) Now download this menu.lst file (from gbohm) http://www.filesonic.com/file/1302552154/menu.lst.
6) Copy that file to the root of your Archos. (maybe copy&overwrite)
7) Reboot your Archos.
8) I you should see a new entry in the Boot Menu, named "Ginger-bread", choose this.
9) Your Archos now boots Cyanogen!
Please often look into the download archive of Bubu ( http://download.openaos.org/bubu/gen8/android/ ) for a new version of Cyanogen!

Install Urukdroid on the openAOS Boot Menu
Install Urukdroid on the openAOS Boot Menu
UrukDroid is an Android distribution for Archos GEN8 devices.
It's mix of Android 2.2.1, original Archos OS with different Linux/GNU utilities, kernel patches and all kind of modification.
Goal of this system is to allow users to do most of the operations
they are allowed to do on normal Linux distributions.
It's aimed for more advanced users, but tries to be useful on basic level of all people if they don't need special features.​(from http://code.google.com/p/urukdroid/)
Urukdroid is created by $aur0n and many other developers.
Some Users may have problems with this, because you need a bit of Linux Knowledge!
Install Urukdroid on the openAOS Boot Menu
If you dont have Urukdroid already, please also follow the Orange Instructions.
Otherwise start with the Black Instructions below.
1) Shut down your Archos.
2) Boot into the SDE Boot Menu. and choose "Recovery System" >> "Developers Edition Menu" >> "Flash Kernel and Initramfs"
3) Connect your Archos with your PC (USB).
4) Download the Urukdroid 1.1 Installation file from here: http://sauron.pourix.com/UrukDroid/UrukDroid-1.0/UrukDroid_1.0-Install.rar
5) Extract the 3 files inside.
6) Copy the zImage and initramfs.cpio.gz files to your Archos.
7) Press the Power Button once.
8) Your Archos now flash the Urukdroid Kernel.
9) Restart your Archos into the SDE (Holding down Volume Down ( - ) Button)
10) Choose your options at the EasyInstall of Urukdroid.
11) Follow the Installation Process of Urukdroid.
12) You now have Urukdroid.
1) If you dont have Linux on your PC already, please download a Ubuntu Live CD from here: http://www.ubuntu.com/download/ubuntu/download
2) Boot your PC with that CD/USB Stick.
3) Shutdown your Archos.
4) Boot into the SDE Boot Menu. (Hold down Volume Down ( - ) Button)
5) Choose "Recovery System" >> "Repair System" >> "Start USB MSC" and connect your Archos to your PC with booted Ubuntu. (USB)
5.5) You should now see 3 "Devices" connected to your Archos.
These are the 3 Partitions of your Archos.
6) Download this file: http://www.mediafire.com/?oi9g4kujjsytd9x
7) Extract the files out of the archive (one folder & one file)
8) Go to Terminal. (Applications >> Accessories >> Terminal)
9) Type "sudo nautilus"
10) A window, like the Windows Explorer, should open.
11) Go to the directory, where you extracted the archos.inc out of the downloaded file.
12) Copy that file to the root of your Urukdroid Partition.
The Urukdroid Partition is normally 0.5 GB or 1.0 GB big.
13) Now go to the Directory where you have extracted the 2.6.29-omap1 folder out of the downloaded file.
14) Copy that folder into [YOUR URUKDROID PARTITION]/lib/modules.
(You first have to delete the, on your Urukdroid Partition excisting,2.6.29-omap1 folder)
15) Download this file and extract the 2 files out of it http://www.mediafire.com/?xaabbc9in9q4l2u
15) Overwrite the init.rc file on the root of your Urukdroid Partition with the downloaded and extracted one.
[COLOR="Red[COLOR="Red"][/COLOR]"]Warning! This init.rc only work if you have urukdroid installed on internet flash!
You, who have urukdroid installed on sd, please do this steps:[/COLOR]
1) Search for the (commented) Topic "Mount Partitions"
2) The third line under this Topic is commented. (with a #)
3) Uncomment it by erase the #.
4) Now change the line from "mount |____| /data noatime nosuid" (i forgot the middle-part) to "mount ext4 /dev/block/mmcblk1p3 /data noatime nosuid"
(if you use Urukdroid from sd card you have to change the line to "mount /dev/mmcblk2p3 /data")
5) Now search a Topic called "First Boot Logo" (or so) with only one line under it.
Warning: You just have to do this 2 following steps, if you dont have the A70 S or H
6) You have to add the line "exec /system/bin/flip.sh", but you have to add this below the excisting command under the Topic!
7) Save the init.rc file and exit the text editor.
23) Copy the downloaded and extracted file flip.sh to /system/bin
Warning: The following steps should done by all(also the A70 S or H users!)
24) "Exit" the Urukdroid Partition safely and press the Power Button. (on your Archos)
25) Boot your Archos into the normal Archos Android and connect it with your PC. (You can choose if you use Ubuntu or Windows for this, i used windows)
26) Open the file, named menu.lst.
--> If you do it on Windows, be sure you open it with Notepad ++ (can downloaded here: http://notepad-plus-plus.org/release/5.9.2) and that you have enabled the UNIX line endings! (Edit>>EOL Conversation>>UNIX)
27) Add the line:
Code:
UrukDroid|/dev/mmcblk1p2|/rootfs.img|/init|0
If you use Urukdroid from SD Card you have to change "/dev/mmcblk1p2" to "/dev/mmcblk2p2".
28) Save the file and "exit" your Archos safely and reboot your Archos.
29) Boot Up your Archos, now you should see a new Option, to choose, named "Urukdroid".
30) You now have Urukdroid running on the openAOS Boot Menu!

Editing the menu.lst
Editing the menu.lst
This Tutorial is for the more powerful users!
The menu.lst say to the openAOS Boot Menu, which OS are installed on the Device.
The Standart menu.lst, automatically created by the menu on first boot up, looks like:
Code:
Archos|ARCHOS|ARCHOS|/init|0
Angstrom||/rootfs.img|/sbin/init|1
Lets investigate a normal line:
Code:
Angstrom||/rootfs.img|/sbin/init|1
----1---|2|-----3----|-----4----|5
1) The first Part is the name, that is showed on the Boot Menu.
2) The second Part (empty here) is the Developer/producer of the Rom/OS/Image
3) The third Part is the name and directory of the Image File to Boot.
4) The fourth Part is the directory of the root of the Imaeg/Os.
5) The fifth Part is the SGX Overlay Version, you have to set :
"1" for a Linux/Debian OS/Image
"0" for a Android Os/Image
Editing the menu.lst on Windows
If you want to edit the menu.lst on Windows you have to use Notepad++ for this. (can downloaded here: http://notepad-plus-plus.org/download)
You have to be sure, that you have enabled the UNIX Line Endings!
(Edit >> EOL Conversation >> UNIX)
If its "grayed-out" its okey, if not just click on it.
The most maked fault
The most maked fault is this:
Code:
Archos|ARCHOS|ARCHOS|/init|0 [BREAK]
Angstrom||/rootfs.img|/sbin/init|1 [BREAK]
Ginger-bread||/openaos-gingerbread.img|/init|0 [BREAK]
This menu.lst dont work!
It has to be:
Code:
Archos|ARCHOS|ARCHOS|/init|0 [BREAK]
Angstrom||/rootfs.img|/sbin/init|1 [BREAK]
Ginger-bread||/openaos-gingerbread.img|/init|0 [BREAK]
[BREAK]
You have to add a empty line! (Not just press "Enter" once when you are on the end of the last (gingerbread here) line, you have do it twice!)
After that you have to be 2 lines below the last OS line!

Install Google-Apps on Cyanogen
These Instructions are about getting the Google-Applications on Cyanogen.
(Like: Market,Sync,Talk,Backup,..)​1) First install a Root File Explorer (I recommend this free one: https://market.android.com/details?id=gpc.myweb.hinet.net.TaskManager )
2) Download this file: http://www.mediafire.com/?5iu9zvrq0ns6w15
3) Extract all apks out of the zip.
4) Copy all extracted apks to /system/app and reboot your device.
5) When your device boots up you should get to the "Start Up Wizard".
6) Here you have to create or sign in to your Google-Account.
7) Now you have all Google-Apps on Cyanogen!

Videos
Here Are Videos all around the openAOS Boot Menu/Urukdroid/Cyanogen.
Installation Process of the SDE
Installation Process of the Boot Menu and Cyanogen
Hands on with Cyanogen
Warning: This Video is old! Its from the very first version of Cyan! The lastest version is much more stable!
Links
Here are helpfull links to Websites about the openAOS Boot Menu:
openAOS - The "Home" of Bubu, the developer of the menu, with updates and news about archos stuff and cyanogen (also Bubu`s work)
Arctablet - An Archos news portal. They make many of the videos (2 of the 3 videos above). Here you can read about the Boot Menu and other Archos stuff and news.
Bubus file server - The file archive of Bubu. Here you can find the lastest version of the Boot Menu and Cyanogen.

Great summary, thanks a bunch

after doing ur how to for Urukdroid it didn't work ; but i'm root now on the original firmware i dont know how or why super user is working... god damn it
with full read and write

Just as a note.
If you have a A70s/h you don't need step 24 in Uruk configuration as our Display is mounted correct.

I can't startup my urukdroid in A101. I have tried below two lines in my config.
I can see it will start to boot Urukdroid, but after that it will switch to ARCHOS animation screen and wait for a long time.
UrukDroid|/dev/mmcblk2p2||/init|0
For this one, it will also start to boot Urukdroid at the first time, then it switch to ARCHOS animation screen and boot up android stock firmware.
UrukDroid|/dev/mmcblk2p2|/rootfs.img|/init|0

vantoman said:
after doing ur how to for Urukdroid it didn't work ; but i'm root now on the original firmware i dont know how or why super user is working... god damn it
with full read and write
Click to expand...
Click to collapse
and
I can't startup my urukdroid in A101. I have tried below two lines in my config.
Click to expand...
Click to collapse
I know, I know
This is Urukdroid! I didnt believe it too, but i tested Urukconfig and it works normally
It dont install the normal Urukdroid apps... i dont know why...

fzelle said:
Just as a note.
If you have a A70s/h you don't need step 24 in Uruk configuration as our Display is mounted correct.
Click to expand...
Click to collapse
Thanks for the tip
I added this at first post

jan_tsui said:
I can't startup my urukdroid in A101. I have tried below two lines in my config.
I can see it will start to boot Urukdroid, but after that it will switch to ARCHOS animation screen and wait for a long time.
UrukDroid|/dev/mmcblk2p2||/init|0
For this one, it will also start to boot Urukdroid at the first time, then it switch to ARCHOS animation screen and boot up android stock firmware.
UrukDroid|/dev/mmcblk2p2|/rootfs.img|/init|0
Click to expand...
Click to collapse
Try the latest initramfs from BuBu, the one from 4 July. The devices for the external SD card were added again.
Sent from my HTC Desire using Tapatalk

Lenn said:
and
I know, I know
This is Urukdroid! I didnt believe it too, but i tested Urukconfig and it works normally
It dont install the normal Urukdroid apps... i dont know why...
Click to expand...
Click to collapse
Lenn ; no i mean it start archos firmware from the boot menu and u'll get root i've tested it with the latest firmware and i'm root

vantoman said:
Lenn ; no i mean it start archos firmware from the boot menu and u'll get root i've tested it with the latest firmware and i'm root
Click to expand...
Click to collapse
Yeah i know you mean,i have this too
But this is urukdroid^^ urukconfig works normally

Your howto works fine, thank you very much.
But I have a problem - maybee simple.
On my Archos 101, after booting gingerbread (last bubu image) all stands upside down (bootmenu, afterwards the ADW screen). I just have checked all in the CM settings, so ADW become right, but some apps (like camera) won't follow and stay upside down .
What have I misdone?

zingel said:
Your howto works fine, thank you very much.
But I have a problem - maybee simple.
On my Archos 101, after booting gingerbread (last bubu image) all stands upside down (bootmenu, afterwards the ADW screen). I just have checked all in the CM settings, so ADW become right, but some apps (like camera) won't follow and stay upside down .
What have I misdone?
Click to expand...
Click to collapse
Actually this bug have been solved...
Do you have the lastest versions? Please check

Lenn said:
Actually this bug have been solved...
Do you have the lastest versions? Please check
Click to expand...
Click to collapse
The 101 will still have problems with the camera, etc. Display output is reversed, and the accelerometer has been reversed as well to cope with it. Eventually we'll get the display reversed instead of the accelerometer. Speaking of the camera, can you use it? I can't as the sdcard isn't mounted properly.

[HTCEvoDesign4G][ROM][Stock][Debloated][2.12.651.5] DesignerEvo v0.5, Updated April 9

DesignerEvo v0.5, a customized stock rom for the HTC Evo Design 4G!
Visit the original announcement / discussion thread on SDX-Developers here.
Based on the stock HTC build 2.12.651.5 / Android 2.3.4 / HTC Sense 3.0, and baked using the Android Kitchen 0.184 by dsixda (http://forum.xda-developers.com/showthread.php?t=633246).
My goal was to create something that would be more useful for me, but figured other people might be able to benefit from it as well!
Important note: If you want to Factory Reset this ROM, you should reinstall the DesignerEvo-update.zip immediately after performing the reset to restore content to the /data partition. Otherwise there will be a number of preinstalled things missing.
Current Release:
DesignerEvo v0.5 (MD5SUM 71088007ee3da6d2baaf83a113e48f44)
Download here: http://d-h.st/C0I
Old Releases:
DesignerEvo v0.4
Redacted due to Wifi issues
DesignerEvo v0.3 (MD5SUM a0dd61849533fb64d887d6cb1e400cbb)
Download here: http://d-h.st/11i
DesignerEvo v0.2 (MD5SUM 00359825fee03c49007634213ebab901)
Download here: http://d-h.st/b0t
DesignerEvo v0.1 (MD5SUM 44d081019e2fe69dcf416eced88f9448)
Download here: http://d-h.st/gy023lstrxw9
Changelog:
Version 0.5:
Based on HTC RUU 2.12.651.5
Now install boot animation to /data/local/bootanimation.zip so you can easily override it if you want (via symlinks to /system)!
New DesignerEvo boot animation from Dysgenic! http://forum.xda-developers.com/showthread.php?t=905538
Backed out this change in 0.5 since it broke WiFi: Use busybox instead of toolbox for common utilities, gives a bit better functionality on things like ls and friends (colors!)
Version 0.4:
Redacted due to WiFi issues
Version 0.3:
Based on HTC RUU 2.12.651.5
Upgraded version of Android Wifi Tether to 3.1 Beta11 (IMPORTANT: Be sure to enable MSS clamping + Routing Fix in the Wifi Tether settings, otherwise tethering won't work on 3G!).
Added in HTC Radio apps + widget per user request!
Added back in Polaris Office (lets you open MS Office files, and won't run properly when installed to /data, needs to be in /system).
Resoled issue with lockscreen shortcuts and widgets on a Factory Reset.
Updated versions of Amazon Appstore + all other Play-updateable apps.
Added UOT Kitchen battery guage with battery percentage shown.
Modified statusbar to display 1x for 1xRTT data when not in a 3G area.
Using the same boot.img from DesignerEvo-0.2, note that if you don't install the correct boot.img, your WiFi and many other things will NOT WORK CORRECTLY!!! If you have already flashed 0.2, you don't have to re-flash for 0.3 though! People coming from stock and 0.1 should flash the 0.2 boot image (included in this download).
Version 0.2:
Based on HTC RUU 2.12.651.5
Downgraded to Android Wifi Tether v3.0.7 update9 since it is more stable on the Design 4G. You can still upgrade to newer versions, but this is the one that seemed to work the best.
Version 0.1:
Based on HTC RUU 1.19.651.0
Stock kernel 2.6.35.10 with initrd tweak
Debloated (Sprint / HTC stock apps removed, many can be re-downloaded from the Market)
Deodexed
Zip-aligned
/data/app enabled to allow easy removal of stock applications
/etc/init.d scripts enabled (busybox run-parts)
Disabled OTA updates in build.prop (FOTA settings)
Many updated stock applications, moved to /data/app to allow for uninstall / market updates
(Console) Applications added:
Bash shell (default)
BusyBox v1.19.3
Nano text editor
(Android) Applications added:
(Downgraded) EPST from the Evo 4G allowing applying custom PRLs on-demand (##PRL#)
Superuser 3.0.7
Android Wifi Tether v3.1 beta6
Amazon Appstore
EStrong's File Explorer
Ookla Speed Test
How to flash (note that if you have not yet done a HTC Bootloader Unlock, this will perform a factory reset on your phone!!! Be very sure that this is what you want! If you have rooted without unlocking, I highly recommend downloading Titanium Backup to perform a full backup of all your apps and data first!):
Enable USB Debugging on your android phone (http://www.groovypost.com/howto/mobile/how-to-enable-usb-debugging-android-phone/)
Get adb / fastboot working (needed to unlock and flash boot.img)
Windows: http://www.umnet.com/mobile-blogs/321-AndroidADBFastboot_Easy_5_minute_setup_(Great_for_nOObs)
Mac/Linux: Install the Android SDK from Google and then download fastboot from here: http://koushikdutta.blurryfox.com/G1/
Perform a HTC Bootloader Unlock on your HTC Evo Design 4G (makes use of fastboot installed in step 2): http://htcdev.com/bootloader
Reboot into the bootloader (adb reboot bootloader) to access fastboot (or pull your battery, and re-insert it, then immediately hold down Power and VolDown until the white HTC HBOOT screen appears).
Run all following steps in the directory where you've decompressed DesignEvo-0.1.zip:
Run "fastboot flash recovery recovery-unofficial-cwm-5.0.2.7.img" (credit goes to 2fast4u88 on XDA: http://forum.xda-developers.com/showthread.php?p=20444019)
Alternatively, flash any other Evo Design 4G Recovery image (the unofficial TWRP build is also known to work)
Run "fastboot flash boot DesignerEvo-0.1-boot.img"
Now recovery and boot will be flashed. On your phone, select "BOOTLOADER" using VolUp/Down and Power to select.
Press VolDown to select RECOVERY (might take a few seconds to scan your SDCard first) and press Power to select.
You should now be booted into 2FS CWM-based Recovery v5.0.2.7.
Now would be a good time to make a nandroid backup of all your stock partitions! The nandroid backup plus the stock-boot.img I include in my download zip will get you back to a factory flash if necessary. (More info on nandroid: http://forum.xda-developers.com/showthread.php?t=1186090)
Run "adb shell mount sdcard" to mount your SDCARD on the phone. Nothing should be returned (if success).
Run "adb push DesignerEvo-0.X-update.zip /sdcard/DesignerEvo-0.X-update.zip" to copy the update.zip image to your sdcard.
Once the push is successful, choose "install zip from sdcard" (again using VolUp/Down/Power).
It will likely take about five minutes to copy. Be patient
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select "DesignerEvo-0.1-update.zip" (probably near the bottom)
Select "Yes - Install DesignerEvo-0.X-update.zip"
After about 5 minutes, you should see "Install from sdcard complete"
You can now select "+++Go Back+++", and should wipe your Cache and Dalvik Cache before proceeding.
Finally, choose "reboot system now"
Your phone should now reboot into DesignerEvo. Verify by navigating to Settings->About phone->Software information->Software number!
Regards-
hofopds

Reserved...
Reserving slot 2...

[Q] Feedback to [GUIDE] Root (Updated for ICS) #213 on page 22

Am 10 postings away from being allowed to join the original discussion.
Have ICS 4.0.4 OTA upgrade to ...-P6800XXLQ1-...
Used the procedures and data from Attached Files of posting #213 by kable in #213 in
http://forum.xda-developers.com/showthread.php?t=1454112&page=22
CWM installed well from recovery.
But CWM did not install root.zip!
Error message:
CWM Recovery v5.8.1.5
E: Can't mount /sdcard/
What could have gone wrong? What further details are needed to find a remedy? What else is needed to root successfully?

Updates:
I have found solutions after reading all posts related.
If you have just PC Odin an unrooted SGT 6800 into ICS, your SGT now cannot be rooted. What I have done thereafter is as follows:
1. PC Odin CWM 5.5.0.4 into my 6800;
2. set-up your 6800 into recovery mode ( press power & vol-up same times, release power button once your see active screen, then release vol-up button as well, you will be in CWM recovery mode;
3. goto zip from sdcard; toggle signature verification & script asserts to disable;
4. then choose zip from internal sdcard; from there you should choose root.zip ( this root.zip was saved into your external sdcard in advance.)
5. Once done, choose reboot.
Now you new ICS is rooted.

Which zip and which sdcard, that is the question.
Hi ronnieho,
thanks for your quick response and help. I am sure you will get me running. Please give me some more details which due to my lack of experience I feel to be missing.
Please let me explain this, then you will know which details still trouble me:
Last week I managed to root my ICS SGS2 following these instructions:
http://www.pocketpc.ch/samsung-gala...-stock-ics-firmware-ohne-flashen-kernels.html
It is in german, but based on the original thread
http://forum.xda-developers.com/showthread.php?t=1501719
The german instruction was very specific about which zip to put into which (internal or external) sdcard.
The english XDA instructions are not that specific about these obviously very important details.
Would you please add these details to your instructions:
1. PC Odin CWM 5.5.0.4 into my 6800;
Does this mean, place CWM.zip into the external sdcard (i.e. /sdcard/extStorages/SdCard) of the 6800?
From the threads refered to in my first post I have CWM 5.8.1.5. May this work too? Or must it be CWM 5.5.0.4? Where can I get CWM 5.5.0.4?
2. set-up your 6800 into recovery mode ( press power & vol-up same times, release power button once your see active screen, then release vol-up button as well, you will be in CWM recovery mode;
Yes, this is how I get into recovery mode.
3. goto zip from sdcard; toggle signature verification & script asserts to disable;
goto _which_ zip from _which_ sdcard.
Rooting my SGS2 I used
- install zip from sdcard
Here _sdcard_ meant the external sdcard
And _zip_ meant CWM.zip.
Is this also true for your instruction step 3?
toggle signature verification & script asserts to disable;
Where/to what item should I apply these instructions?
4. then choose zip from internal sdcard; from there you should choose root.zip ( this root.zip was saved into your external sdcard in advance.)
So far I did not save any zip to the internal sdcard?
Should I have saved root.zip into the internal sdcard in step 1?
Which root.zip? Remember, I have CWM.zip and root.zip from the Attached Files of posting #213 by kable in http://forum.xda-developers.com/showthread.php?t=1454112&page=22
Can I use these files or should I download different zip-files? From where?
Sure, I could simply try out my questions, but I am afraid to brick my Tab.
Another important detail may be that I did not use Odin to copy the zip files to the tap. In my successful rooting of the SGS2 I simply used the USB MTP connection and copied the zip-files like I copy video and audio files, and it worked. I would prefer to keep this copy practice also regarding the Tab7.7. Or must I copy with Odin? Why? Do I miss something if I copy in MTP mode? Does Odin do a different copy? Does Odin copy to different/specific sdcard locations?
I am confident that using your instruction will make the difference. Please give me the details which I feel to be missing.
Thanks!

Took the risk - Success, at last!
Since I did not get any more helpful answers, I had to reconsider the situation. Finally I decided to take the risk by using a best of
a) the xda-developers [GUIDE] Root (Updated for ICS)
http://forum.xda-developers.com/showthread.php?t=1454112
, e.g. postings #1 by Jade Eyed Wolf, #213 by kable, #227 by ronnieho, #230 by mashkuov, etc.
b) aljee77 guide for the SGS2
http://www.pocketpc.ch/samsung-gala...-stock-ics-firmware-ohne-flashen-kernels.html
Trusting that the xda-developers zip-files, CWM.zip and root.zip, will be ok for the Tab7.7
and hoping that the aljee77 procedure will also work as well for my Tab7.7 as it has worked for my SGS2,
I took the risk and finally succeeded to root my Tab7.7.
My successful procedure (Thanks to aljee77 and mashkuov):
1. Data preparation (zip-files)
1.1 Downloaded CWM.zip and root.zip to my computer from mashkuov, post #230 in http://forum.xda-developers.com/showthread.php?t=1454112&page=23
1.2 Copy these zip files from my computer to respective sdcard in my tab.
I have the Samsung Kies drivers installed on my computer. But I do not use Odin. I connect the tab and the computer with the USB data cable and simply use the USB MTP connection. I simply copy the zip-files like I would copy video and audio files by simple Windows Explorer file-drag/drop between the the source/target location icons.
1.3 I copy CWM.zip into my _external_ SDCARD
(on the computer: GT-P6800/Card
on the tab: /sdcard/extStorages/SdCard)
1.4 I copy root.zip into my _internal_ SDCARD ( /sdcard/ ) <--- aljee77 procedure <--- :good:
(on the computer: GT-P6800/Tablet
on the tab: /sdcard/)
2. Temporary installation of CWM Recovery:
- Reboot to recovery:
2.1 Download and install LATEST SAMSUNG KIES (or stand-alone USB drivers if you can find them)
2.2 Transfer CWM.zip to the EXTERNAL CARD on Galaxy Tab 7.7 (already done in step 1.3)
2.3 Turn off the Galaxy Tab 7.7
2.4 Enter Recovery
- Hold Volume UP button + Power Button
- When TAB turns ON, RELEASE POWER BUTTON (Keep Holding Volume UP Button)
* Will Enter Recovery
2.5 In the following basic menu use Volume Up/Down to navigate and Power OFF to select/accept options!
- Choose apply update from external storage.
- Choose CWM.zip and wait until CWM recovery appears.
* Now a temporary CWM is installed and activated.
* This CWM recovery is only a _temporary_ CWM and will be gone after reboot!
* see #217 by vegaman: http://forum.xda-developers.com/showpost.php?p=28300775&postcount=217
3. Install root
* Once the CWM recovery appears:
* _Touch-screen_ to navigate and to choose an option!
- install zip from sdcard (1st CWM menu)
- choose zip from internal sdcard (2nd CWM menu) <--- aljee77 procedure <--- :good:
- toggle signature verification & script asserts to disable <--- ronnieho #227 http://forum.xda-developers.com/showthread.php?t=1454112&page=22
- +++ GO BACK ++++ (from 2nd to 1st CWM menu)
- reboot system now (1st CWM menu)
* After reboot your tab will be rooted and temporary CWM will be gone.
4. Enjoy!
Now the tab is rooted! Temporary CWM is gone.
Now you can download Superuser App and Superuser Elite App (both by ChainsDD) from the market.
5. If you want a permanent CWM see #220 by Handymeister: http://forum.xda-developers.com/showpost.php?p=28319010&postcount=220
- after installing temporary CWM I flashed the root.zip with it.
- then reboot
- with root I flashed the CWM with Mobile Odin and that works fine and is now resistant again
Click to expand...
Click to collapse
6. If you need to unroot, see #5 by kazuni: http://forum.xda-developers.com/showpost.php?p=21600037&postcount=5
Re-flashing manufacturer rom through Odin is the only method as far as i know
Click to expand...
Click to collapse
Many thanks to aljee77 from pocketpc.ch and to the xda-developers posting experts in [GUIDE] Root (Updated for ICS)!
http://forum.xda-developers.com/showthread.php?t=1454112
Problem solved!

[GUIDE] Port firefox OS to Nexus 4 + Galaxy 2 Dual Boot

How To Install Firefox OS on a nexus 4 and dual boot. ​
XDA-Developers member pureexe has created an Image that will help you to port Firefox OS to your Google Nexus 4. Here is the list of what works and what doesn’t works:
What Works:
– Wi-Fi
– Data
– Phone Calls
– Contact Import
– GPS
– SMS/MMS
-Some Sensors (Light+Gyroscope+Acceleration)
-ADB
Does NOT Work:
– Camera
-MTP/PTP
– A lot of other things
How To Flash
Step 1: First connect your device to PC (desktop/laptop) via USB and make sure that USB debugging enabled on your device.
Step 2: Now to be on safe side create a Nandroid backup from recovery its because if something goes wrong then you can easily backup all your data.
Step 3: After creating backup, now download the ROM (FFOS_mako_********.zip) file and place these files on the SD card of the phone.
Step 4: Now switch off the phone and boot the phone into Recovery mode.
Step 5: Assuming you are in the Recovery mode and now you have to wipe the full data on your device. To do this, you have to click on “Wipe Data/Factory Reset” option. As soon as you click on “Wipe Data/Factory Reset” option a new screen pop-up where you have to click on “Yes” option.
Step 6: After wiping out all the data on your device you have to wipe the cache & the dalvik cache also.
Step 7: Now go to “install zip from SD card” option and click on “select zip from SD card”. After selecting the option “select zip from SD card” you have to choose the ROM file.
Step 8: After performing all the correctly in step 7 you have to clear the cache and & dalvik cache again.
Step 9: Now, go to “Install zip from SD card” option and click on “Select zip from SD card”. After selecting the option “Select zip from SD card”, you have to choose the optional file like home app or server module
Step 10 : Assuming you have performed all the steps correctly, now simply reboot your device and it will boot into Firefox OS.
Click to expand...
Click to collapse
How to dual boot: ONLY FOR GALAXY S2
Warning: This procedure doesn't really work anymore. It only works with Android 4 (Ice Cream Sandwich) and Siyah Kernel v 5.0.1. Later versions of either won't work. Consider this guide archived, and use it at your own risk.
If you want to test B2G from time to time but continue using Android as your main OS and you have a Samsung Galaxy S2, you can choose to install B2G in a separate partition (which is already present on the phone) and choose where to boot into when your device starts.
Prerequisites
In order to dual boot Android and B2G, you have to meet these prerequisites:
You have to have built B2G for the Galaxy S2
You have to download the Siyah kernel v. 5.0.1 for the Galaxy S2
You need the tool simg2img, that you get automatically if you build B2G following the guide on MDN
You need the heimdall tool, best if version 1.3.1 as you may encounter problems with version 1.3.2
One-time operations
There are several operations to do in order to get a working dual boot. The following ones need to be done the first time only.
In order to use heimdall without requiring root access, you should create a file called android.rules (the portion of the name before the .rules extension is arbitrary) and place it in /etc/udev/rules.d. The file should contain a line line the following:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
In order to activate this rule, you should restart udev:
Code:
sudo service udev restart
and then unplug and replug in the phone. The above rule will also allow adb to access the SGS2 without requiring root privlidges.
Flashing the Siyah kernel
The Siyah kernel is mandatory for the dual boot, because it is this kernel that manages it. Once you have downloaded and decompressed the tar file, you'll be left with a file named zImage. In order to flash it on your phone you have to follow these steps:
Switch off your phone
Reboot in download mode (press together volume down + home + power buttons and then, when asked, volume up button)
Use heimdall to flash the kernel with the following command (your phone needs to be connected to your PC):
heimdall flash --kernel /path/to/zImage
Once the kernel is flashed the phone will reboot.
Preparing the B2G rom environment
Once you've installed the Siyah kernel, it's time to use its functions to prepare the environment to install your B2G image in the secondary partition. Follow these steps:
Switch off your phone
Reboot in recovery mode (press together volume up + home + power buttons)
In the CWMR Touch interface, go to dual-boot options -> Wipe 2ndROM data/cache -> Yes - Wipe. This operation will take some time
Once the operation is finished, select Go Back and then reboot system now to reboot your phone. If you check, inside the internal SD card of your phone you'll now have a .secondrom directory with inside two files named cache.img and data.img.
B2G update operations
The following operations need to be done every time you build a new version of B2G.
In order to simplify command line instructions, it's advised to copy all needed files in a same folder of your choice. These are the files that need to be copied inside the folder:
Code:
simg2img, found in B2G/out/target/product/galaxys2/system/bin/
system.img, found in B2G/out/target/product/galaxys2/
userdata.img, found in B2G/out/target/product/galaxys2/
Once you have all the files in one place, do the following:
Create a data.img file out of the sparse file userdata.img. You can do it with the following command:
Code:
simg2img userdata.img data.img
Put the data.img file on your phone's .secondrom folder. You can do this either by enabling file storage mode on your phone and connecting it to your PC or, if you have USB Debug active, you can use adb:
adb push /path/to/data.img /sdcard/.secondrom/data.img
Switch off your phone
Reboot in download mode (press together volume down + home + power buttons and then, when asked, volume up button)
Use heimdall to flash B2G firmware inside the second partition:
heimdall flash --hidden system.img
Once the flash is finished, your phone will reboot and at boot time you can boot into your second rom (the B2G one) by pressing the home button during the bootloader countdown. If everything has gone right, once you've finished booting B2G you'll have a black screen on your phone. You now have to install Gaia.
Note: Depending on how you want to test B2G, you may not want to put a new data.img file on the phone every time you update B2G, as it will wipe all of your preferences, installed applications and in general pretty much everything you've done while using B2G.
Boot operations
The following operations need to be done every time you boot inside B2G.
Unfortunately, there's no simple way to put Gaia inside the system.img B2G image, and it get lost when you switch off your phone, so you'll need to install Gaia again every time you boot inside B2G. To install Gaia, type the following on a console after you've booted your phone inside B2G (so you have a black screen) and have connected your phone to your PC:
cd B2G/gaia
GAIA_DOMAIN=foo.org make install-gaia
After the upload of Gaia is completed, on your phone's screen the B2G interface will appear.
Click to expand...
Click to collapse
Dual Boot With Nexus 4 :
Original Link Here
Text Steps :
-Download FFOS.zip file
-Go to TWRP recovery
-Go to advanced, MultiROM, add ROM
-Select android, and don't share kernel
-Select next, then select zip file
-Select the FFOS.zip file
-After that go to list ROMs, pick FFOS, select flash zip, and flash the addons you want
-Reboot to multiboot
-Select FFOS and boot it
-Wait about 2 minutes
-You're now booted to FFOS
BTW FFOS stands for firefox OS
Downloads :
FFOS image Here
Contributors + Complier
pureexefor image and steps
Mozilla (for Dual Boot 1)
Riro Zizo for dual boot 2
Me, for putting all this stuff together!

@Apph3x
I have two version of porting
- Base Jellybean 4.3
- Base Kitkat
i know Base Kitkat is bad but working fine on base Jellybean 4.3
on jellybean everything working except MTP
Please read this post http://forum.xda-developers.com/showpost.php?p=44451567&postcount=2

Thanks
@pureexe I know but I'm sparse on time will update soon. The image is your latest 1 tho ;D thanks for original guide

Updated
Removed by owner
vvvvvvvvvvvvvvvv

Updated
UPDATE BASE LAYER 4.3
What Works:
- Wi-Fi
- Data
- Phone Calls
- Bluetooth
- Camera (Rear Camera & Front Camera)
- Video Record
- GPS
- SMS/MMS
- MUSIC (Mp3 & ogg decoder working)
- USB tethering
- WIFI tethering
- Video HQ decoder
- Sensor (Light+Gyroscope+Acceleration)
- ADB
- A lot of thing
Does NOT Work:
-MTP/PTP
Download
http://forum.xda-developers.com/devd...ct/dl/?id=3793

[11] [GSI] [OFFICIAL] AOSP Q Mod //CAOS

C A O S​(Note, I did not make this rom. This is a Generic System Image (GSI) made by Caos' devs. so it is not specifically built for the A51, but it's really stable and I am using it now. ALL CREDIT GOES TO CAOS' DEVS!)
Your warranty is now void!​We're not responsible for bricked devices, dead SD cards,​thermonuclear war, or you getting fired because the alarm app failed. Please​do some research if you have any concerns about features included in this ROM​before flashing it! YOU are choosing to make these modifications, and if​you point the finger at us for messing up your device, we will laugh at you​​
CAOS (Custom AOSP OS) is a project which is based on @phhusson's Treble GSI AOSP 10. CAOS' devs began it because ASOP has stability, speed and support but also some issues and limitations - pure AOSP's code has some bugs and it doesn't have much useful things and it's hard to pull it. So CAOS' devs did this fork. System can run with SELinux enforced state, as an original Phh AOSP GSI. Fully compatible with PHH-Treble patches exclude few low level changes: no root app, no "su" binary in system; by default exist file /system/phh/secure (for Google Certification PASS), so if you can boot AOSP GSI, but can't boot CAOS - try to removing that file
UPDATE VERSION
latest build: 2020.10.29
treble patches: v222+
SPL: 5 Oct 2020
File Downloads/Installation​THINGS THAT YOU NEED ON YOUR WINDOWS COMPUTER.​
Odin
Unzip the file. There is a EXE file in it. Double click it to launch. There will be a pop up, just press ok.
FILES THAT YOU NEED TO FLASH THE ROM.​The rom itself
Make sure you have 7-zip installed. Right click it and click extract files. Go into the unzipped folder and rename the file inside to "system.img"
TWRP Decrypter
Just leave this file as a zip. Don't unzip it.
ChonDoe Flasher
Just leave this file as a zip, Don't unzip it.
INSTALL RECOVERY AND UNLOCK BOOTLOADER (SKIP THIS PART IF YOU ALREADY HAVE TWRP.)​I have made a reddit post on twrp. DO NOT DO THE MAGISK PART.
FLASHING THE FILES​Go into TWRP. Press wipe and go into format data. Type in yes and wipe your data. Press the home button in your nav bar and go back into Wipe. Press advanced wipe, tick "data", "Dalvik / ART cache" and "Cache". Format it.
Press the home button in the nav bar again. Now, go into reboot and click recovery. Don't do anything. Once it's back into TWRP, plug your phone into the pc if you haven't already.
On your Windows PC, go into File Explorer, This PC, A515F and then internal storage. Take the "system.img" file and drag it into there. Do the same with "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip" and "ChonDoe_Flasher.zip"
Once all of them are copied, go onto your phone. Click install and you should see your files. If you don't, go into /sdcard. Flash "ChonDoe_Flasher.zip". Once it's done, flash "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip". Press "Reboot System" once "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip" is installed.
If this looks really confusing to you, there is a tutorial for this. However, it's for HavocOS. But everything is the same except the rom. But the steps are the same. Watch it here.​
Congrats! You have installed Caos!​
CONTACTS
> telegram group
> project page
KNOWN BUGS:
• excluding fixes, the same as on AOSP Quack (in some cases doesn't work: broadcasting on TV, calls via BT; offline charging does not work normally fingerprint doesnt work; problems with GPS etc etc)
NOTE: always test ROM first without Magisk (with clean boot ramdisk). and don't send me bug reports if you have:
a) Magisk installed​b) modified/custom vendor or kernel​c) dirty flashing rom without wiping data​
CREDITS
persons: @phhusson
projects: TrebleGSI • BlissROMs • crDroid • PixelExperience • ION • neon-OS • Havoc-OS • LineageOS • Evolution-X • LiquidRemix • ExtendedUI • GrapheneOS • abc rom