Database Develop

2.2 available!

So 2 days ago guys from 4pda.ru ported android 2.2 on GT540, it is installed on sd card and you can choose between 2.1 and 2.2.
Here is youtube video:
And here is link on thread on 4pda:
PDA

so why would I need to switch between 2.1 and 2.2? I guess this is just a preliminary POC and a custom rom is now in the works.
can't wait! great job russians!

tong.po said:
so why would I need to switch between 2.1 and 2.2?
Click to expand...
Click to collapse
Maybe cos 2.2 isn't supporting FM/Camera/BT right now and is booted from SD.

Thank god for the Russians! And great job finding this.
Sent from my GT540 using XDA App

woo!
could someone make a tutorial?
as the translated russian is'nt easy.

flyboyovyick said:
woo!
could someone make a tutorial?
as the translated russian is'nt easy.
Click to expand...
Click to collapse
Lol 1+
Sent from my GT540 using XDA App

The Rom is not even released yet, nor it will be released soon. Its in I wouldnt even call it Alpha version yet.

You can find some info there:
http://twitter.com/#!/ZduneX25/status/6643977159708672
__________
Written with Tapatalk on GT540

gonna make a video and read tut of it
and some video of it working ofcourse!

ported only basic functions, engineer version posted atm... No final version...

Direct link to some work and explanation in russian is here: http://4pda.ru/forum/index.php?showtopic=200838 But it is stated as version for developers and professionals only, because it is lacks some functions, half working wi-fi, some problems with bluetooth and it's still in test mode. You will need to format your sd card, make your phone able to load in fastboot mode and one package for dual booting from above link.
You will need following apllications:
Dual boot loader from here: http://narod.ru/disk/122844001/ankuch2.2-oss.img.html
Copy of /system folder: http://narod.ru/disk/41926001/ankuch2.2.tar.html
1. Prepare your sd card
type of disk MBR;
part0/primary - fat16 - sdcard - 128MB+. No reason to create more;
part1/primary - ext2 - system - 256MB+, you can put more if you will put some applications in /system/app;
part2/primary - ext2 - data - 256MB+.
I recommend it to partition in 10/10/80.
If you got a big card and use phone to view video, you can make first partition bigger.
2. After SD card prepare, you will need to load and copy content of /system folder from ankuch2.2.rar archive
Making final phase in 2.1:
1. Mount /system in mode r/w (you can mount it, for example, from RootExplorer - select /system and press button mount r/w)
2. adb shell
3. su
4. mkdir /system/s8
5. mount -t ext2 /dev/block/mmcblk0p2 /system/s8
6. cd /system/s8
7. busybox tar -x -f /data/ankuch2.2.tar
Loading 2.2:
Enter fastboot mode
We load 2.2 - fastboot boot ankuch2.2.img
No loading animation yet, you will need to wait until will be filled content of /data folder
First load can take a long time, you can control it thru adb shell logcat.
adb, btw, I did in first time and from root it loads.
Sorry for mine english Fast translation
Problems and some solutions to avoid them:
1. How to put data transfer?
adb shell
stop ril-daemon
start ril-daemon
-- Can be some problems with APN not loading from SIM card, so you will need to put configuration manually.
-- Connection always will be like EDGE, even if really you getting HSDPA
2. How to get rid of lag in transitions?
Try this:
Spare Parts -> Window animations -> Off
Spare Parts -> Transition animations -> Off
Once I got bugged rild, loaded cpu to 100% and almost halted all apps, thats why from link in russian forum you will see some pics of processes.
You can turn it on:
Dev Tools -> Development Settings -> Show running processes
Changed those options too:
Dev Tools -> Development Settings -> Disable compatibility mode (requires to reboot device)
After this author does not get any hangs.
3. How to connect to Wi-Fi
It is required to copy from your 2.1 file wpa_supplicant.conf to /data/misc/wifi (in this file it is saved all your information about connections)
Change permisions from file chmod 777 /data/misc/wifi/wpa_supplicant.conf (author did not tested more secure permisions) or reboot device
rest in here -> Settings->Wireless & network->Wi-Fi (turn on Wi-Fi)

[ROM][ICS][AOSP] Lenovo Ideapad K1

This is a 100% AOSP ICS build for the Lenovo Ideapad K1. It will wipe your entire system. You will lose all data except what is stored on the EXTERNAL sdcard.
Includes
Android ICS 4.0.4
ClockworkMod Recovery 6.0.1.0
Google Apps
Rooted version includes Superuser and busybox
Issues
Video Camera face effects
Rotation Lock Switch (Software switch works)
Downloads
As always flash at your own risk. I'm not responsible for your device.
Nvflash versions
K1_ICS_AOSP_Rooted_R2.zip
dfddf13bf51e357a4964a11a8adbfd53
Mirror
K1_ICS_AOSP_Stock_R2.zip
b359ec6a06289ccf8c6b83f07346be17
Mirror
CWM versions
CWM_K1_ICS_AOSP_Rooted_R2.zip
90341324a0927f3035e92dc81ffb9416
Mirror
CWM_K1_ICS_AOSP_Stock_R2.zip
c026beb4dc2a11defbc3c3bcbec041cc
Mirror
Instructions
Nvflash version
1. Download one of the packages above and extract it to a directory
2. Power off device
3. Press and hold both the Vol + and Vol - buttons
4. While holding both Volume buttons power the tablet on
5. The screen should go black and the two front LED's should remain lit. You are now in APX mode
6. Connect your device to USB
7a) Windows: Install the APX drivers from the 'drivers' folder
Double click the 'flash-windows.bat' file
7b) Linux: run 'chmod +x flash-linux.sh && sudo ./flash-linux.sh' from the extracted directory
CWM version
1. Download one of the CWM_K1_*.zip versions and move to external sdcard
2. Reboot into recovery
3. Install zip from sdcard
4. Choose zip from sdcard
5. Flash the update.
How to boot into recovery
Non-rooted version
1. Make sure you have the Android SDK installed. http://developer.android.com/sdk/index.html
2. Make sure USB Debugging is enabled on the tablet. Go to Settings > Developers options > and check "USB Debugging"
3. Connect the device to USB
4. Open a terminal or command prompt window and type
Code:
adb shell k1recovery
Rooted version
From a Terminal Application
Run the follow two commands
Code:
su
k1recovery
From adb
1. Make sure you have the Android SDK installed. http://developer.android.com/sdk/index.html
2. Make sure USB Debugging is enabled on the tablet. Go to Settings > Developers options > and check "USB Debugging"
3. Connect the device to USB
4. Open a terminal or command prompt window and type
Code:
adb shell k1recovery
Changelog
Code:
8/11/2012 R2
-Fixed external sdcard permissions
-Fixed keylayout
-Modifed build.prop to spoof Moto Xoom (App compatibility)
7/31/2012 R1
-Initial Release
Source Code
http://github.com/khanning

So from now on we will be able to flash future updates through recovery without wiping everything?

So from now on we will be able to flash future updates through recovery without wiping everything?
Click to expand...
Click to collapse
Exactly, future updates will be CWM flashable .zip's.
All, I just noticed that Google Chrome isn't showing in the market, but Maps is. I swear it was showing up when I was testing previously. Will have to investigate...

khanning88 said:
Exactly, future updates will be CWM flashable .zip's.
All, I just noticed that Google Chrome isn't showing in the market, but Maps is. I swear it was showing up when I was testing previously. Will have to investigate...
Click to expand...
Click to collapse
I dont know if it's me or because of the ROM. WIth the rooted ROM before AOSP, I was able to install Chrome with a APK downloaded from mobilism but sometimes the pages are fine then just rendered white , for all tabs.
Does anybody use SKYPE ? When I do video chat, my broadcast picture stretched vertically when I broadcast-only (no picture feed from the other side), the picture my friend saw is fine though.
Many thanks for your hard work.

That is the main thing that i hate about Lenovo's Factory ICS image, i still cant install Chrome or Evernote, or many of my NEEDED apps. I hope that you get this working soon. or at least a temp fix.

Just flashed the rooted aosp, the boot animation is a nice touch. The app compatibility issue seems fully resolved outside of Chrome, pointed out already, which is no biggie for me atleast. I still can sideload Chrome and runs perfectly. Also, so far the dictionary miss-spell issue doesnt seem to be a problem anymore. Maybe its just me but touch responsiveness seems a little better/quicker with this build. Just tried using the command 'k1recovery' to boot into recovery and it keeps giving me an error relating to permissions, saying it cant create /dev/block/mmcblk0p5. Seems like I just need to change the permissions of the /block folder but wasnt sure if I was just not doing something right.
Massive improvements from Lenovo's vanilla ICS still, thanx khanning!

Noticed some graphical glitches. Screen goes black if switching orientations on lockscreen and home screen.

@Khanning88 Can you provide a mirror please? Goo.im is down and shows "Internal server error".
Never mind. It's up again.

me_is_rushin said:
Noticed some graphical glitches. Screen goes black if switching orientations on lockscreen and home screen.
Click to expand...
Click to collapse
Yup the screen flashes when switching orientations, for a split second...

That's great. thanks for share.

Flashed this one and works wonderful.
Rebooting to recovery didn't work 1st, but then mounted filesystem as rw and tried the command and could get to recovery.
Got an error "Can't mount backup path" when trying to make a backup. Is it because I didn't have an external sd card.
If yes, is there a way to take a nandroid backup to internal memory?
BTW, thanks again for providing this ROM.

Thanks khanning88 for giving this fabulous AOSP ROM
Does this ROM support the Wifi+3G version?

I found some issues installing apps, including some games, Zinio magazine reader, google earth, etc, all saying incompatible with my device.

I experienced alot of freezes while restoring my backup with titanium backup.
I keep testing if it also occurs in normal use.

Installed AOSP-Rooted. So far, Chrome (already noted as issue in OP), and POGO Games showing up as Incompatible.
Other than that, and possible other apps being incompatible, looks great and installed as easy as can be.
Thanks Khanning!
-Cybie

we need an easy way to enter recovery. Rom Manager button doesn't work.
Reboot recovery from terminal emulator doesn't work either.
Could you implement the nice options when turning the unit off?

several more freezes. obviously not depending on any special app..

erickwan said:
Does this ROM support the Wifi+3G version?
Click to expand...
Click to collapse
I'm not sure if 3G works since I have a Wifi version, but if someone with a 3G version could meet me in freenode IRC room #ideapad-k1 I would be happy to work on it. If you aren't familiar with IRC just go to this link and join the chat.
http://webchat.freenode.net/?channels=ideapad-k1
we need an easy way to enter recovery. Rom Manager button doesn't work.
Reboot recovery from terminal emulator doesn't work either.
Could you implement the nice options when turning the unit off?
Click to expand...
Click to collapse
From a terminal app type:
Code:
su
k1recovery
Or from adb type:
Code:
adb shell k1recovery
Either method will reboot the device into recovery. I will work on adding the power menu options later.
several more freezes. obviously not depending on any special app..
Click to expand...
Click to collapse
I haven't experienced any "freezes" but when it happens to you could you please document what you were doing and take a logcat to help debug.
http://rootzwiki.com/topic/11930-learn-to-logcat-like-a-pro/

Here is a very simple way to reboot into khanning's CWM recovery.
1. Playstore --> Download/Install aShell app
2. Run App
3. Select Checkbox for "Root" (In Settings, you can set app to start Root as Default)
4. type "k1recovery" into textbox
5. press "start command" button.
Simple, no need to be in "true shell" mode. This app allows you to run shell commands without the terminal. Great for newbies, quicker for anyone.
Hope this helps!
-Cybie

Here is a quick fix for the hardware keys. Just flash the .zip file from recovery. Updated first post with more detailed booting into recovery instructions.
K1_keylayout_fix.zip

Ubuntu 13.04 Final Release

This thread is to announce the release of, and provide information for,
Ubuntu 13.04 FINAL VERSION for the HP TouchPad.
Brought to you in LESS THAN 24 HOURS AFTER RELEASE by WillCast.
Screenshots of "new" E17 attached to this post!
FEATURES
Automatic login to Enlightenment 17 (E17)
All E17 packages (including Terminology) rebuilt from source from the enlightenment-svn PPA.
e17-gtk-theme installed and activated.
< 2 GB extracted size. For best results, use a 4GB or larger ubuntu-root. (Most are.)
GUI Config Programs (see next section)
Wi-Fi working
RNDIS over USB working (2.6 and 3.0)
Bluetooth working except for BTAudio
Normal Ubuntu boot sequence (no strange initramfs hacks, and working fstab)
(new and updated) KEXEC IS REQUIRED
2.2GHz max Overclock - Not even stable on my TP! (Max 1.78GHz on 3.0.8)
Working Audio (manual switch between Internal and External)
AUTOMATIC, TOGGLABLEScreen Rotation
Software Compositing Enabled
Desktop Style Interface with Seperate Windows
Settable Brightness
Settable Charger Current Limit
Settable LED Triggers
VLC Media Player, GStreamer (Rhythmbox/Pithos) pre-configured to work
PULSEAUDIO (Enslaved to alsa dmix to prevent issues) (yay)
GRAPHICAL TOUCHPAD CONFIG UTILITIES
All are available from the desktop.
setbrightness (fixed) - Set LCD brightness with a slider.
setImax (new) - Set the charger current limit from a list.
setfreq (new) - Configure CPU speed from a list, optionally, set to persist over reboot.
tsrotate (fixed) - Turn auto-rotation on or off.
audiocfg - Select the audio output - internal, external or both.
setLEDtrigger (New) - Select the LED triggers for the left and right sides of the home/center button. Examples provided in dialog.
PRE-INSTALLED SOFTWARE
Available from the EVERYTHING Starter in the Bottom-Left Corner
Mozilla Firefox
Gnash (Flash 7-8) plugin, Lightspark (Flash 9+) plugin, IcedTea 7 (Java) plugin
Pithos (Pandora radio client)
Rhythmbox (music player)
VLC media player
LibreOffice
GIMP 2.8
GNOME system monitor, Baobab disk usage tool, GCalcTool calculator, gedit text editor
RELEVANT INFORMATION
Root password: root
Normal Username: ubuntu, Password: ubuntu
Auto-login Enabled
To configure Bluetooth and date/time, go into System Settings (aka gnome-control-center).
Use the NetworkManger Applet in the panel to configure Wi-Fi.
TO PERFORM A NEW INSTALL (ONLY), AUTOMATICALLY WITH SMACKME2
SmackMe2 thread: http://forum.xda-developers.com/showthread.php?t=2132703
Copy the two provided files (uImage.kexec and TouchPadBuntuRootfs1304b2.tar.gz) to the sminstall folder under the root of your /media/internal. If "sminstall" does not exist, first create it.
Follow the instructions on how to install "native Linux' in the SmackMe2 thread.
TO PREPARE FOR MANUAL UPGRADE (NOVATERM)
Install NovaCom and NovaTerm on your "real" computer - please consult one of the many references on how to install it.
Boot the TouchPad into WebOS.
Connect the TouchPad to the PC with a microUSB cable.
Enter USB mode and copy the uImage.kexec and TouchPadBuntuRootfs1304b2.tar.gz files to the root of your TouchPad's internal storage.
PROPERLY "eject" the TP from your PC.
Enter Developer Mode. (In the Just Type box, type "upupdowndownleftrightleftrightbastart", and select Developer Mode.)
On your PC, open "novaterm".
You are now ready to type in the "Manual Installation" commands.
MANUAL UPGRADE (Commands to type into Novaterm)
This will erase any data and settings stored under Ubuntu. Stuff in the media storage (/media/internal or /mnt/sdcard) will be unaffected.
Code:
mkfs.ext3 /dev/store/ubuntu-root
mkdir /tmp/u
mount /dev/store/ubuntu-root /tmp/u
cd /tmp/u
tar -xzpvf /media/internal/TouchPadBuntuRootfs1304f.tar.gz
umount /tmp/u
cd /media/internal
mount -o remount,rw /boot
cp uImage.kexec /boot
sync
TO BOOT AFTER INSTALLATION
Reboot your TouchPad.
Select "kexec" in the MoBoot menu, and press Center to boot kexec.
Wait for the white screen.
Select "Ubuntu 13.04" in the kexecboot screen, and select (press POWER/SLEEP button on top, not CENTER button).
Wait for Enlightenment to start.
TROUBLESHOOTING / FAQ:
If you don't see Ubuntu in the moboot menu, that is normal - you have to boot Kexec and then boot Ubuntu 13.04 from kexec.
If your TouchPad doesn't have a "kexec" menu option after rebooting, make sure you copied uImage.kexec to the proper location, and retry.
If your kexec uImage doesn't boot or freezes before the white screen, check your free space on the boot partition (/dev/mmcblk0p13). Delete kexec, free up at least 3MB (by deleting extra uImages and/or themes) and recopy it manually.
If you can't select Ubuntu from the kexec menu, make sure you're pressing Power and not Center to select it.
If your kexec freezes instead of booting Ubuntu, make sure you have the latest kexec from this post. The old one doesn't support large initramfs files which are present in 13.04 beta2 (and the final version.)
If you experience problems with Kernel 3.0.8, remember that it is alpha quality!
To reboot your TouchPad if it stops responding, hold down Center and Power until you see "Please release key(s)."
DOWNLOAD LINKS - Google Drive hosted
NEW AND UPDATED KEXEC: (required to boot): https://docs.google.com/file/d/0B4WUjKii92l2RHJoNE93c2dVRlU/edit?usp=sharing
13.04 FINAL ROOTFS: https://docs.google.com/file/d/0B4WUjKii92l2bDRlQ0NTbTZBemM/edit?usp=sharing
KERNEL 3.0.8 ALPHA: https://docs.google.com/file/d/0B4WUjKii92l2TXd5RTJfQnJtS3c/edit?usp=sharing
PREVIOUS VERSIONS - UNSUPPORTED
13.04beta2: https://docs.google.com/file/d/0B4WUjKii92l2N0V2Q3ljTHI0WEU/edit?usp=sharing
12.10final: https://docs.google.com/file/d/0B4WUjKii92l2eDduajFwUGhVYlU/edit?usp=sharing
12.10beta1:https://docs.google.com/file/d/0B4WUjKii92l2OExhVDdXX3dGcjQ/edit?usp=sharing

nicee. was thinking to sell my touchpad. but now. thanks to u.
Sent from my LG-P769 using Tapatalk 2

How's battery life with this?

Battery life is something I haven't tested. It's okay, I think, about 3-4 hours. Remember, Ubuntu doesn't sleep on these, never has AFAIK.

i cant format the ubuntu-root to ext4. everytime i run mkfs.ext4 i get this error while mounting:
mount: mounting /dev/store/ubuntu-root /tmp/u failed:Invalid Argument
if i format to ext3 mounting works. Can i use ext3 instead of ext4??

I'm using Ubuntu 12.10, I don't mind to start from scratch.
But..... Would upgrading from 12.10 to this version via novaterm screw anything up?
Sent from my Nexus 7 using xda app-developers app

That (ext3) should work - I enabled the config option where you can mount ext2/ext3 as ext4 on my kernel. I forgot that webos uses slightly old filesystems
I'll update the instructions.
In the battery life quest, I just noticed that the dnsmasq process often eats up 100% CPU, so I just disabled it. I'll upload a revised image to the same link (love GDrive), but if any of you have already DLed one then I can tell you what to do to fix it:
in Terminal:
Code:
sudo gedit /etc/NetworkManager/NetworkManager.conf
delete or comment out ("#") the line reading "dns=dnsmasq" and save, quit, reboot (or sudo killall dnsmasq)

castrwilliam said:
That should work. If you were to encounter any trouble installing then there is an error with the commands I posted.
On the battery life quest, I just noticed that the dnsmasq process often eats up 100% CPU, so I just disabled it. I'll upload a revised image to the same link (love GDrive), but if any of you have already DLed one then I can tell you what to do to fix it:
in Terminal:
Code:
sudo gedit /etc/NetworkManager/NetworkManager.conf
delete or comment out ("#") the line reading "dns=dnsmasq" and save, quit, reboot (or sudo killall dnsmasq)
Click to expand...
Click to collapse
I remember there being sleep issues on old builds. On this, can I sleep the device, or does it have to be shut down when not in use?
- Thanks, always wanted an Ubuntu build
Sent from my ADR6425LVW using xda app-developers app
---------- Post added at 09:42 AM ---------- Previous post was at 09:39 AM ----------
Also, right clicking was really annoying before. Is it usable on your build?
Sent from my ADR6425LVW using xda app-developers app

eriscentro said:
I remember there being sleep issues on old builds. On this, can I sleep the device, or does it have to be shut down when not in use?
- Thanks, always wanted an Ubuntu build
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
You need to turn off the whole tablet, yes. I don't think it was ever made to work on ubuntu. It wasn't really a priority when we were missing stuff like headphone audio. I guess I can look into dmesg and try to diagnose.
To right click you need to click on the mouse cursor button on onboard, and then the flipped looking pointer button on the 2nd row down of the button group that appears - after tou do that, the very next click wll be seen as a right click.

I'll take a look once I do the install later today, waiting for my TP to finish charging up. Thanks!
Sent from my ADR6425LVW using xda app-developers app

there are a lot of dependencie errors and broken packages when u try to install software(i.e. eclipse). is there a way to fix it
??

imapjonny said:
there are a lot of dependencie errors and broken packages when u try to install software(i.e. eclipse). is there a way to fix it
??
Click to expand...
Click to collapse
I haven't tried this release yet, eclipse worked fine under 12.10.
May not be compiled properly or hasn't been updated to the 13.04 armhf port repositories.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 01:42 PM ---------- Previous post was at 01:41 PM ----------
blmvxer said:
I haven't tried this release yet, eclipse worked fine under 12.10.
May not be compiled properly or hasn't been updated to the 13.04 armhf port repositories.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
One thing I'd like to see in the armhf repository is spotify. That's honestly all I need on an Ubuntu tablet.
Sent from my Nexus 7 using xda app-developers app

Im struggling to get sound working, any ideas?
Sent from my GT-N7100 using xda app-developers app

imapjonny said:
there are a lot of dependencie errors and broken packages when u try to install software(i.e. eclipse). is there a way to fix it
??
Click to expand...
Click to collapse
Depends on what you're installing. Remember this is an ARM powered device and not your normal x86/x64 processor you'll find in a normal laptop or desktop.

castrwilliam said:
Ubuntu 13.04 beta 2 [FINAL BETA]
Click to expand...
Click to collapse
Thanks for this.
When you say final beta I assume you mean final build?
Or do you have plans for something that can be considered past the beta stage of development?

Thanks for this. Things seem to be running alot better than the previous 13.04 build.
A couple things i noticed -
The onscreen keyboard didn't easily come up. I have a bluetooth one so maybe i gave up too soon on trying to get it.
I also have a bluetooth mouse. After a minute or 2 of using it the cursor disappears from the screen. You can tell its still connected because as I move it, various things get hovered on.
Flash player is no longer available for firefox or chromium. I tried linking to the webos flashplayerlib but it still doesn't work. i installed the gnash stuff but that doesn'
t work everywhere.
Thanks again for this though. is working great post from it now.

Isn't there an Open-Source flash player somewhere?
Sent from my Nexus 7 using xda app-developers app

Im not a massive linux user so apologies if this sounds pretty basic, but can tou theme the bar with rhe wifi and clock? I really want the 'classic' ubuntu look...
Sent from my GT-N7100 using xda app-developers app

fach1708 said:
Im not a massive linux user so apologies if this sounds pretty basic, but can tou theme the bar with rhe wifi and clock? I really want the 'classic' ubuntu look...
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Sudo apt-get gnome-shell
Sent from my Nexus 7 using xda app-developers app

Thanks Castrwailliams Great work dude
:good:
Rock On Castrwilliams keep up the good work man
installed it using smackme2

[Touch Interface kexec Bootloader/Installer] nsboot aka NinjaSwag Bootloader beta

nsboot - NinjaSwag Bootloader/Installer
WILL REPLACE smackme2 and kexecboot!
Source: https://github.com/willcast/nsboot
Kernel source: https://github.com/willcast/ubuntu-kernel-tenderloin/tree/kexec (kexec branch, not Ubuntu)
Binary: https://docs.google.com/file/d/0B4WUjKii92l2Ukl4TE1EM1pjTDg/edit?usp=sharing
I have been working on this for about 2 weeks...
Features
Touch screen based interface
Able to boot kexec kernels
Able to install Android and Native Linux OSes, kexec tar files, and uImage kernels
Able to back up entire volumes as .tar.gz (with permissions & ownership)
Directly compatible with smackme and kexecboot config files
Can replace moboot entirely with the touch of a button.
Integrated file browser
Software touch keyboard available
Haptic feedback
uImage is < 4 MiB
Loads 3x faster than kexecboot
Has integrated ADB server so you can push and pull files from any mounted FS, or run a local shell.
Known issues so at this time
Colors are messed up in included TWRP recoveries
Things still to be tested
nothing as of now
kexec images for reference
webOS 3.0.5: https://docs.google.com/file/d/0B4WUjKii92l2WU9fdkNZa0V5NUk/edit?usp=sharing
Arch Linux ARM: https://docs.google.com/file/d/0B4WUjKii92l2YWRFUWJoMkpXRzg/edit?usp=sharing
Ubuntu: https://docs.google.com/file/d/0B4WUjKii92l2MXlEVmxQUHoyUzg/edit?usp=sharing
Slackware: https://docs.google.com/file/d/0B4WUjKii92l2MnRwMGRyTmRQcW8/edit?usp=sharing
Fedora untested: https://docs.google.com/file/d/0B4WUjKii92l2S3pVUkZNNzNSQUU/edit?usp=sharing
Android 2.2 Froyo: https://docs.google.com/file/d/0B4WUjKii92l2d2cwQlBtVVd4aGM/edit?usp=sharing
Android 2.3 Gingerbread: https://docs.google.com/file/d/0B4WUjKii92l2UGtETzBwNnNvckU/edit?usp=sharing
Android 4.0 Ice Cream Sandwich: https://docs.google.com/file/d/0B4WUjKii92l2UDc2cVZ2TjBWM2s/edit?usp=sharing
Android 4.1 Jelly Bean: https://docs.google.com/file/d/0B4WUjKii92l2d3g0U3p6c0l4NFk/edit?usp=sharing
Android 4.2 Jelly Bean: https://docs.google.com/file/d/0B4WUjKii92l2dlFzcFBacThSVXc/edit?usp=sharing
How to test
Code:
novacom boot mem:// < uImage.nsboot
To install, copy it to /boot (/dev/mmcblk0p13). It can also install itself if you put a copy of it on the SD card, and go Installer menu -> install uImage and navigate to it.
Screenshots are attached.
YouTube demo of a earlier version with only the boot working and a simpler menu: http://www.youtube.com/watch?v=0oQhSa4sqPU
Updates:
All OSes now boot (At least on my TP.)
Those which have had their kexec archives revised on GDrive since the first post are in italic.
Android 4.2
Android 4.1
Android 4.0
Android 2.3
Android 2.2
Android Recovery (included with all Android kexec archives)*
webOS
Ubuntu
Slackware
Arch Linux
Fedora
* The colors are still out of whack in recovery. It's mostly unneeded at this point with Built-In ADB support and zip installation, but I included it for those who want its more obscure or advanced features, or are more comfortable with its UI. Testing it specifically is appreciated because I don't have any plans to develop a test suite for it.
Compatibility list
Android ROMs
4.2
There is currently an issue with installing later Android 4.2 ROMs. The following 4.2 ROMs will install and boot:
Evervolv nightly 05-15-2013
The following 4.2 ROMs get stuck in a fairly serious bootloop (logcat shows at least surfaceflinger, mediaserver, and zygote segfaulting). I have tried different kernels.
CM 10.1 unofficial nightly 06-02-2013
Schzoid 2.0 nightly 04-23-2013
Other 4.2 ROMs are untested.
4.1
The following Android 4.1 ROMs have been tested and work:
JCSullins' CM 10 preview, 12-16-2012
Schzoid 1.2, 03-06-2013
4.0
The following Android 4.0 ROMs have been tested and work: CM 9 nightly, 01-06-2013
2.3
The following Android 2.3 ROMs have been tested: CM 7 Alpha 3.5
Issue: When the screen is woken up in CM7, nothing shows up on the display. The backlight does turn on.
2.2
The following Android 2.2 ROMs have been tested and work: my Froyo kang, version 0.4 and 0.3 (0.4 is on google drive on top of 0.3)
Native Linux
Ubuntu
The following Ubuntu releases have been tested and work: Ubuntu 13.04 final, Ubuntu 12.10 final.
Others are welcome to be tested, but I will probably not take issue with anything before 12.10 beta not working.
Arch Linux
Arch Linux boots, and seems to work. Wi-Fi has not been tested.
Slackware
Slackware boots and seems to work. Wi-Fi and Bluetooth have not been tested.
Debian/Bodhi
I am unable to locate any tar.gz archives to test for this distribution, nor a kernel of any sort. If anyone wishes to step up and send one to me or even host it, I would be grateful and also I'd probably get it booting within a day.
Fedora
These haven't yet been tested. They are theorerically installable with the new "tar.gz to custom LV" feature, but I would need to find a way to free more space on my TP to install them (my media partition is currently about 10 GB, 6 GB used for music, and 2.5 GB used for testing files.

Thank you
Good Job! I will test it tomorrow.I have been looking forward to ArchLinuxArm for a long time.Thank you.

Looks really good, I'll give it a spin.

Nice thing. But how Do I add my existing cm Installation to it? And how to add the cwm recovery in bootlist?
I repaced moboot with this and now i Can only Access Ubuntu
Sent from my GT-I9300 using xda app-developers app

Sir, I downloaded this, installed it, installed kexec-webos.
I rebooted
in boot menu section, i selected HP WebOS 3.0.5
Waited for 10 secs in Starting new kernel.
nothing only reboots
thinking to use webOSDoctor
But it is not going to webOS recovery mode.:crying:
What to do?:crying::crying::crying::crying::crying:

superboy123 said:
Sir, I downloaded this, installed it, installed kexec-webos.
I rebooted
in boot menu section, i selected HP WebOS 3.0.5
Waited for 10 secs in Starting new kernel.
nothing only reboots
thinking to use webOSDoctor
But it is not going to webOS recovery mode.:crying:
What to do?:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Same here! But i Can Access Ubuntu
Sent from my GT-I9300 using xda app-developers app

superboy123 said:
Sir, I downloaded this, installed it, installed kexec-webos.
I rebooted
in boot menu section, i selected HP WebOS 3.0.5
Waited for 10 secs in Starting new kernel.
nothing only reboots
thinking to use webOSDoctor
But it is not going to webOS recovery mode.:crying:
What to do?:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
After I made the webOS image, I noticed that it's a bit... finicky. Just reboot from nsboot main menu. Then try loading webOS again.
If you need to get to recovery mode, the way to do it is to reboot like that, holding down VOLUME UP.

imapjonny said:
Nice thing. But how Do I add my existing cm Installation to it? And how to add the cwm recovery in bootlist?
I repaced moboot with this and now i Can only Access Ubuntu
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
If you installed CM to the logical volumes named /dev/store/cm-*, you need to back up and reinstall it from nsboot. As for booting CM recovery from nsboot, if you haven't done that yet, a feature I put in already lets you make .tar.gz archives from volumes (including Android ones.) I just enabled the extraction of them to Android volumes (used to only allow others), so you could use that to "move" your Android.
Minimum System Sizes to use for android partitions:
2.2 (froyo): 256MB
2.3 (gingerbread): 320MB
4.0 (ics): 320MB
4.1 (jellybean): 450MB
4.2 (jb mr1): 480MB
Step by step instructions:
Upgrade nsboot. Just released a new one. Either scp/adb it from a running OS or redo the install procedure except for the replace moboot part, after downloading it again.
Get the kexec tarchive for your android version onto the SD card. You could scp or adb push it. If needs be, find your old Android recovery image, and boot it via novacom:
Code:
novacom boot mem:// < uImage.ClockworkMod
Boot nsboot.
Go to Utilities - create volume tarchive.
Select "cm-system". Name the backup "System".
Repeat last two steps for "cm-data" if you want to keep your data partition. I don't recommend backing up "cache".
Go to Utilities - create volume set.
Name the new Volume Set depending on your Android/CM release: Use the names "android22", "android23", "android40", "android41", or "android42".
Format the new volume set: go to Utilites->format volume set, and select it. Click Confirm/OK.
After the set is created, go to Installer menu -> install .tar.gz to existing volume. Navigte to /mnt/media/nsboot/backups. You will find your two backups. Select "System" to restore to "androidXX-system", depending on the version you just created. Make sure you use a big enough size - see above table.
Repeat the last step for data, if you made such a backup.
You now need to find the kexec archive you copied to your SD card (it's mounted in /mnt/media.) Install it. If you chose the right volume set name, it will work.
Reboot or rescan boot items and you should see the Android version in your boot menu. Tell me if it doesn't work.
If it does work, go to utility menu -> delete volume set and select "cm" as your set. This will remove the old cm set, and leave the new androidXX one.
After that, if it did work, go to utility menu -> reclaim media space to get back any lost space for your media/sdcard partition.

Thank s it worked well. But i didnt get webos to run. I installed the webos kexec tar via install kexec tar to existing volume and of i wann Boot it, it hangs up and reboots nsbootloader
Sent from my GT-I9300 using xda app-developers app

imapjonny said:
Thank s it worked well. But i didnt get webos to run. I installed the webos kexec tar via install kexec tar to existing volume and of i wann Boot it, it hangs up and reboots nsbootloader
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
So when you guys who are having trouble with webOS try launching it, do you get to the screen that says 'please wait, booting...' or the HP logo that pulsates? Where does it reboot? I'm thinking I might have uploaded an old, non-workable tar file for that OS.
FYI: After testing every boot option, I discovered a problem with Android 4.1 (only 4.1). I'm looking into it.
EDIT: just uploaded a new kexec-webos.tar. I have things set up so the link remains the same. Redownload the new tarfile, and see if it works, it works on my end. Still working on fixing 4.1 - it's the only thing left, but most of you are probably using it (trying to.)

Sir,
Thanks for your reply.
But, I cannot get into recovery mode
I rebooted pressed POWER+VOLUME UP, nothing just going into nsboot.
I also tried pressing POWER+HOME+VOLUME UP, that is also the same.
please help.:crying::crying::crying:
I also replaced moboot with nsboot.

superboy123 said:
Sir,
Thanks for your reply.
But, I cannot get into recovery mode
I rebooted pressed POWER+VOLUME UP, nothing just going into nsboot.
I also tried pressing POWER+HOME+VOLUME UP, that is also the same.
please help.:crying::crying::crying:
I also replaced moboot with nsboot.
Click to expand...
Click to collapse
I have never seen this happen for real, and there is no way my code can just disable that combination. That said, I'm not leaving anyone out in the cold with a practically unusable TP.
If you have any ROMs installed, now is the time to use them to transfer needed files over to your sdcard.
Recovery mode works perfectly when I do it, I use that when I want to test a new version without installing it. I'll look in the moboot source and add a button to reboot directly into recovery. I'm also adding ADB support (if I can get kexec to tolerate the usage of the USB bus before the call, which I'm not sure.)
bootie (the TP first stage loader, comes before nsboot or moboot) transfers control over very, very quickly, so if you're pressing these buttons after you touch "Reboot", then don't. Though I don't seem to have issues if I do so, don't hold down Power unless you're force rebooting the TP or powering it on from the cold. Hold down Volume Up as you click reboot, keep it held down as you click "yes", and don't release it.
Also try powering off, then powering back on after 10 secs. Again, hold down Volume Up, then Power, don't switch over.
If you are really frantic, purposefully deleting the nsboot uImage (/mnt/boot/uImage.nsboot) will make your TouchPad boot to the "www.palm.com/ROM" screen, which is a more mandatory form of recovery mode. You could also "rename" or "move" moboot into nsboot, and you'll get moboot back.

castrwilliam said:
EDIT: just uploaded a new kexec-webos.tar. I have things set up so the link remains the same. Redownload the new tarfile, and see if it works, it works on my end. Still working on fixing 4.1 - it's the only thing left, but most of you are probably using it (trying to.)
Click to expand...
Click to collapse
Okay everything is working well with this new tar.
Sent from my GT-I9300 using xda app-developers app

Make sure your pad is fully charged. I have had problems before during partially charged tp
John 3:16

castrwilliam said:
I have never seen this happen for real, and there is no way my code can just disable that combination. That said, I'm not leaving anyone out in the cold with a practically unusable TP.
If you have any ROMs installed, now is the time to use them to transfer needed files over to your sdcard.
Recovery mode works perfectly when I do it, I use that when I want to test a new version without installing it. I'll look in the moboot source and add a button to reboot directly into recovery. I'm also adding ADB support (if I can get kexec to tolerate the usage of the USB bus before the call, which I'm not sure.)
bootie (the TP first stage loader, comes before nsboot or moboot) transfers control over very, very quickly, so if you're pressing these buttons after you touch "Reboot", then don't. Though I don't seem to have issues if I do so, don't hold down Power unless you're force rebooting the TP or powering it on from the cold. Hold down Volume Up as you click reboot, keep it held down as you click "yes", and don't release it.
Also try powering off, then powering back on after 10 secs. Again, hold down Volume Up, then Power, don't switch over.
If you are really frantic, purposefully deleting the nsboot uImage (/mnt/boot/uImage.nsboot) will make your TouchPad boot to the "www.palm.com/ROM" screen, which is a more mandatory form of recovery mode. You could also "rename" or "move" moboot into nsboot, and you'll get moboot back.
Click to expand...
Click to collapse
Sir,
I deleted nsboot, moboot and all uImages.
But now i am getting a blank screen after 5 secs it reboots.
this has been occured unlimited times.
Please Help

superboy123 said:
Sir,
I deleted nsboot, moboot and all uImages.
But now i am getting a blank screen after 5 secs it reboots.
this has been occured unlimited times.
Please Help
Click to expand...
Click to collapse
Okay, try the volume up button. If that doesn't work, try holding power + volume up + home (rebooting it), ignoring the boot loop. I only said to delete one uImage... wait, uImages are the only files you deleted, not anything else in /boot, right?
Do you ever see the HP logo?
If you touched "boot.bin" (among certain other possible files in /boot) you'll probably need the debrick program. This isn't nsboot's fault... link to program is here: http://forum.xda-developers.com/showthread.php?t=2010270
If you use that program, follow its instructions TO THE LETTER, if there is anything you need clarification on, ask here - I've never had to use it, but I've heard of it fixing TPs that don't even show anything on the LCD. That said, if something goes wrong with it, it has the opportunity to make the problem far, far worse.

castrwilliam thank you for your work
Rock on dude
loving your work man keep it up dude:good:

superboy123 said:
Sir,
I deleted nsboot, moboot and all uImages.
But now i am getting a blank screen after 5 secs it reboots.
this has been occured unlimited times.
Please Help
Click to expand...
Click to collapse
Is the pad fully charged? I would strongly suggest letting it charge for twenty four hours.
P.S. don't panic
Sent from my Galaxy Nexus using Tapatalk 2

Is it possible to install Ubuntu 13.04 and 12.10 at the same time?
Sent from my GT-I9300 using xda app-developers app

I am a little confused on the install process, would you mind elaborating.
Sent from my Galaxy Nexus using Tapatalk 2

[ROM] 5.1.* CyanogenMod 12.1

Hi, if anyone would like to run a 5.1.x Google OS on a Archos G9 80S device (and currently basically verified only with this), download and extract the file
16_12_2015-16_26_24
Installation (tested only with linux) :
- reboot into SDE menu and under "Format System" perform a "Reset Android & Storage" to clear all data of previous installations (this is really important for the first installation. Updating a existing installation (same major version) doesn't require this step !).
- reboot into SDE menu and under Developer Edition Menu -> "Export Data Partition"
- mount this usb drive
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/local/archos.ext4
sudo sync
sudo umount <Mount_Path>
- wait until the unmount process is done
- reboot into SDE menu and under Developer Edition Mernu , Flash Kernel and Initramfs : copy zImage and initramfs.cpio.lzo on the new driver that appears on desktop/laptop
- Wait for reboot your devices : after reboot you can see Android prepares the system for a while .....be patient at least ~20 minutes for the first run!
!!Update!!: If you have already installed CM12.0 then it may possible that you don't have to delete the data partition. You only have to copy the kernel/initramfs and ext4 file. I use the command for the last step:
Code:
adb push archos.ext4.update /data/media/ && adb reboot
What's new ?
------------ since 16_12_2015-16_26_24 -------------
Added usual CM updates. -> Also this release include the latest security fixes.
------------ since 05_08_2015-05_48_32 -------------
Added usual CM updates. (See included changelog for details) -> Also this release include the latest security fixes.
Added the 99Performance file from BlackGunZ Big thanks!
------------ since 31_05_2015-19_39_10 -------------
Added usual CM updates. (See included changelog for details)
Add *some* memory improvements, suggested by trevd (big thanks!)
*Maybe last release*
------------ since 23_04_2015-22_05_13 -------------
Initial release.
Re-Enabled Non-PIE Support to support the gps module.
Rebuild: All used revisions for this release are stored in a separate folder in the archive.
Additions:
Archos Control Panel App from @mordesku: http://forum.xda-developers.com/showpost.php?p=47789812&postcount=88
Thanks: @stargo @Hashcode @trevd
@CM community @all the cool omap4 hackers where I taken some code and inspirations !!!
Without these peoples, It would not so easy to make some (working) builds of the CM-12.1.
Archive:
31_05_2015-19_39_10
23_04_2015-22_05_13
XDA:DevDB Information
Archos G9 CyanogenMod 12.1, ROM for the Archos Gen9
Contributors
Quallenauge
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: Cyanogenmod
Version Information
Status: Alpha
Created 2015-04-24
Last Updated 2015-04-24

Thanks for keeping this old tablet going! I'll give it a try this weekend. :good:

jawiler said:
Thanks for keeping this old tablet going! I'll give it a try this weekend. :good:
Click to expand...
Click to collapse
Hi Quallenauge,
I've tried installing this version, but it just goes to a black screen for over 1/2-3/4 hour. I've tried downloading from both sites and checked the MD5SUMs and everything checks out. I went with a clean install.. I've installed your previous versions without any problems. Any ideas?
thanks
Nevermind, I tried a different computer and it worked this time

jawiler said:
Hi Quallenauge,
I've tried installing this version, but it just goes to a black screen for over 1/2-3/4 hour. I've tried downloading from both sites and checked the MD5SUMs and everything checks out. I went with a clean install.. I've installed your previous versions without any problems. Any ideas?
thanks
Nevermind, I tried a different computer and it worked this time
Click to expand...
Click to collapse
Mostly this error comes into play if the kernel&initramfs step or the update package is transferred and the mass storage drive is not cleanly unmounted.

@Quallenauge I knew I should have waited as I've just built cm-12.0 .... I even used your build environment script. Slightly unorthodox but it gets the Job done :good:
Anyway couple of notes from my side .. a bit of dex_preopting does wonders for the boot time
In the full_archos_g9.mk or similar
Code:
WITH_DEXPREOPT := true
WITH_DEXPREOPT_PIC := true
PRODUCT_DEX_PREOPT_BOOT_FLAGS := --compiler-filter=everything
PRODUCT_DEX_PREOPT_DEFAULT_FLAGS := --compiler-filter=everything
$(call add-product-dex-preopt-module-config,services,--compiler-filter=everything)
Not 100% sure that WITH_DEXPREOPT_PIC is required I threw it in anyway...
I also read up on low memory optimizations ( tricks/hacks ) , dropped all the wallpapers and a ton other other apps that I'm not using
It's pretty smooth ... That can be done at runtime by anyone who is feeling brave .
Hackon folks!
trevd

trevd said:
@Quallenauge I also read up on low memory optimizations ( tricks/hacks ) , dropped all the wallpapers and a ton other other apps that I'm not using. It's pretty smooth ... That can be done at runtime by anyone who is feeling brave .
Click to expand...
Click to collapse
Hi @trevd, I always follow your advice therefore I wonder what changes have you applied to optimize this rom? Could you give us any clue?
Thanks in advance

@Quallenauge First, thank you for your great port and efforts ! God bless you.
I found how to fix the root problem by doing some researches. For so, I edited the following line persist.sys.root_access which is present in build.prop file like this :
Code:
persist.sys.root_access=1
After a reboot, my tablet is correctly rooted and Archos Control Panel enables normally the deep sleep mode at boot.
Have a good day !

Hi! Any chance, to use working USB Stick?

BlackGunZ said:
I found how to fix the root problem by doing some researches. For so, I edited the following line persist.sys.root_access which is present in build.prop file like this
Click to expand...
Click to collapse
Hey, could you explain how you do that?
I have CM 12.1 installed on my Archos 80 G9, ADB is working and when I use 'adb shell' I'm supposedly root but can not write to /system.
I can pull the build.prop and change it, but I don't know how to put it back onto /system.

esque said:
Hey, could you explain how you do that?
I have CM 12.1 installed on my Archos 80 G9, ADB is working and when I use 'adb shell' I'm supposedly root but can not write to /system.
I can pull the build.prop and change it, but I don't know how to put it back onto /system.
Click to expand...
Click to collapse
Of course ! The most secure method is to edit the build.prop with CM File Manager.
Before, using ADB put this command after "adb shell" to mount your /system partition RW. After, do the steps I said below :
Code:
mount -o remount,rw /
First, open the file manager. Then, access to the app's options by taping on its icon at the left and choosing after that its settings icon, which is present at the left down side. Go to Advanced section and tap on Access mode next, choose Root access by this way the app will ask root permissions and a pop-up will appear to accept it. You will be redirected to the root (/ directory) of your Archos, scroll down again and go to /system directory. Screenshots :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Secondly, tap on your build.prop file and open it with the file manager's text editor. Choose the line persist.sys.root_access, delete the "3" value and put "1" instead. Screenshots :
Finally, save the file and reboot your phone. Voilà !

esque said:
I can pull the build.prop and change it, but I don't know how to put it back onto /system.
Click to expand...
Click to collapse
Do not forget to change file ownership and permission after pushing it back - or else you'll get a bootloop.
Since you do not know how to remount filesystem, I'd second @BlackGunZ and recommend using any root file editor on android to avoid bootloops and reflashing android (as opposed to adb pull/push).

Bor-ka said:
Do not forget to change file ownership and permission after pushing it back - or else you'll get a bootloop.
Since you do not know how to remount filesystem, I'd second @BlackGunZ and recommend using any root file editor on android to avoid bootloops and reflashing android (as opposed to adb pull/push).
Click to expand...
Click to collapse
That's why I suggested him to use CM File Manager, you're right sir.

@Quallenauge
JustArchi updated his ArchiDroid Optimizations for Lollipop (CyanogenMod). Can they be useful ?

I would really like to try this rom, can anyone help me with a step by step guild for installation, kinda new to installing in this fashion.
i ran the wubi installer to dual boot windows/linux
using ubuntu desktop.
need to know what i need to install prior and how to install it.
Pm me please, i don't want to mock-up the development page
thanks in advance
am i using terminal and going to the usb directory then using these commands?
- mount this usb drive
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/local/archos.ext4
sudo sync
sudo umount <Mount_Path>

@toolhas4degrees
For Windows, check the quote below and I can confirm that it works (I always use it), but for Linux I can't provide you a help as I don't have it.
taninos said:
Install this rom or other roms using Windows is pretty easy with Ext2Fsd Open Source Project ( it works over Win2k, Winxp, Vista, Win7, Win8, Server 2003, Server 2008/R2). Install Ext2Fsd on your PC and follow the next steps below to achieve this purpose. Neither this tablet drivers nor ADB nor a linux virtualized on Windows are needed.
Steps:
00 install Ext2Fsd
01 reboot into SDE menu and under "Format System" perform a "Reset Android & Storage" to clear all data of previous installations (this is really important!)
02 reboot into SDE menu and under Developer Edition Mernu -> "Export Data Partition"
03 connect your Tablet with your PC
04 start Ext2Fsd (ext2 volume manager interface). You should see your local drives and a extra one which is the Linux partition
05 mark that partition and press F7
06 start the service and be sure to check the "Enable writing support for ext3 volumes" and uncheck "Mount all volumes in read-only mode. Press apply
07 again mark your linux partition and press F3 and uncheck "Mount volume in read only mode"
08 now you should see the partition under "myComputer". Open it and if you reseted "Reset Android & Storage" you should see 2 Folders ("media" and "lost+found")
09 make a new folder called "local"
10 rename the archos.ext4.update to archos.ext4 and copy it into "local" folder
11 unmount the linux partition as you would do with any usb drive and then press ok on your tablet
12 go to "Developer Edition Menu" and choose "Flash Kernel and Initramfs"
13 a new drive will appear under "my computer". Copy zImage and initramfs.cpio.lzo to it and press ok
14 reboot your tablet and after a couple of seconds you should see the Archos logo and then Cyanogen logo
Click to expand...
Click to collapse

BlackGunZ said:
For Windows, check the quote below and I can confirm that it works...
Click to expand...
Click to collapse
It is a tad incomplete
11a. go to "Developer Edition Menu" and choose "Remove android kernel" (if not present - skip this step)

Last release? How about working USB stick?

BlackGunZ said:
Of course ! The most secure method is to edit the build.prop with CM File Manager.
Before, using ADB put this command after "adb shell" to mount your /system partition RW. After, do the steps I said below :
Code:
mount -o remount,rw /
First, open the file manager. Then, access to the app's options by taping on its icon at the left and choosing after that its settings icon, which is present at the left down side. Go to Advanced section and tap on Access mode next, choose Root access by this way the app will ask root permissions and a pop-up will appear to accept it. You will be redirected to the root (/ directory) of your Archos, scroll down again and go to /system directory. Screenshots :
Secondly, tap on your build.prop file and open it with the file manager's text editor. Choose the line persist.sys.root_access, delete the "3" value and put "1" instead. Screenshots :
Finally, save the file and reboot your phone. Voilà !
Click to expand...
Click to collapse
Hi
I've tried your method but I can't select root access in cm file manager. It does not work. How can I do ? Any idea ?
Thanks in advance
Ladalgigi
Envoyé de mon ARCHOS 101G9 en utilisant Tapatalk

sashokmc said:
Last release? How about working USB stick?
Click to expand...
Click to collapse
The last release is the one which is present in the OP, for an update we have to wait ! I didn't test the USB stick, sorry. ^^'
ladalgigi said:
Hi
I've tried your method but I can't select root access in cm file manager. It does not work. How can I do ? Any idea ?
Thanks in advance
Ladalgigi
Envoyé de mon ARCHOS 101G9 en utilisant Tapatalk
Click to expand...
Click to collapse
Exit CM File Manager, go to Settings, Developer Options and turn off the root permissions. Then, switch on again the root access to "ADB and applications" and try again

BlackGunZ said:
The last release is the one which is present in the OP, for an update we have to wait ! I didn't test the USB stick, sorry. ^^'
Exit CM File Manager, go to Settings, Developer Options and turn off the root permissions. Then, switch on again the root access to "ADB and applications" and try again
Click to expand...
Click to collapse
Thank you very much ! It works !
Very great ROM
Ladalgigi
Envoyé de mon ARCHOS 101G9 en utilisant Tapatalk