Database Develop

[HOW TO] Root, Install Busybox and SuperCharge your G9

Easy Guides for the G9 Tablets​
Step 1:
Gain temp root
Step 2:
Enable SDE and Permanently root your tablet
Step 3:
Install Busybox without breaking the preinstalled Archos one or losing root
Step 4:
SuperCharge it!
Thanks to Paul @ MoDaCo for the temp root
Thanks to serdu_petru for full root
Thanks to cajl for adb drivers that I edited for noobs
Thanks to letama for the original full root stuff
Thanks to zeppelinrox for v6 supercharger

Temp Rooting - You must do this first
1. Install the ADB drivers, using my other thread here (WINDOWS ONLY)
2. Make sure you have the Android SDK installed and have access to adb
3. Open up a command window (Windows key + R, type cmd and hit enter)
4. Type, with your tablet plugged in:
Code:
adb devices
Your device should appear. If not, repeat steps 1-4 until it does. You may need to restart your computer
5. Download Step 1 and Step 2 Note: Don't open these links in a browser, not tapatalk or the xda app
Download them to your desktop
6. Go back to your command window and type
Code:
cd desktop
7. Write these commands into it, pressing enter at each new line:
Code:
adb push 1 /data/local/
adb push 2 /data/local/
adb shell chmod 0755 /data/local/1
adb shell chmod 0755 /data/local/2
adb shell /data/local/1
adb reboot
adb shell /data/local/2
adb reboot
(Note: Device will reboot at both adb reboot commands)
You are done!
Note: Device doesn't wake from sleep after this and you can only get root via ADB, by typing adb shell
THANKS TO PAUL FROM MoDaCo for this root

Enabling SDE & Permanently Rooting Your tablet
1. Make sure you have done the temp root method
2. Download this zip and extract to your desktop
3. Open the command window again (if it's a new one, type cd desktop again)
4. With your device plugged in, type
Code:
enable_sde
and hit enter
5. Type
Code:
adb shell rm /data/local.prop
and hit enter
6. Download this file (THANKS surdu_petru!)
7a. If you downloaded the file to your computer:
With your tablet plugged into the pc, copy the file to the INTERNAL STORAGE of the drive, NOT IN ANY FOLDERS
7b. If you downloaded the file to your tablet:
Open "Files"
Go to download and copy the file archos_3.2.79.ext4 to the Internal Storage, NOT IN ANY FOLDERS
8. Download this and this and remember where they are
9. Turn off the device normally
10. Hold power + volume down until the archos logo appears and a recovery menu appears
11. Use Volume Up + Down and power to select Recovery Menu > Developer Edition menu
12. Use them to select Flash Kernel and initramfs
13. When a drive appears on your computer, copy the zImage and initramfs.cpio.gz to it. Press power on the device, wait and then press it again
14. The device will boot the unrooted edition (apps and storage will be unaffected)
15. Turn off your device again and boot back into recovery
16. Select Recovery System > Developer Menu > Remove android Kernel
17. Accept warnings (MEDIA & APPS WILL BE UNAFFECTED)
18. Reboot. Your device will now boot the rooted edition every time
BIG THANKS TO surdu_petru and letama for the firmware and SDE

Installing Busybox without breaking your root
You will need:
Root Explorer (costs, sorry :/):
https://market.android.com/details?id=com.speedsoftware.rootexplorer&hl=en
Terminal Emulator (free ):
https://market.android.com/details?id=jackpal.androidterm&feature=search_result#?t=W251bGwsMSwxLDEsImphY2twYWwuYW5kcm9pZHRlcm0iXQ..
Busybox Installer (JRummy)
https://market.android.com/details?id=com.jrummy.busybox.installer&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5qcnVtbXkuYnVzeWJveC5pbnN0YWxsZXIiXQ..
1. Open Root Explorer and go to /bin
2. Press the menu button (very top right) and then Multi-Select
3. Press Select All (bottom left)
4. Press Move and navigate to /system/xbin
5. Press mount R/W (top right) and then Press Paste
6. Open up Terminal Emulator and type the following commands (enter for each new line)
Code:
su
rm -r /bin
ln -s /system/xbin /bin
7. Go back to Root Explorer and navigate to /system/bin
8. Find su and long tap > copy
9. Navigate to /sdcard and tap paste (This backs up su, just in case)
10. Open Busybox Installer and make sure it says 1.19.3 and /system/xbin
11. Hit install
12. Go back to Terminal Emulator and execute this command:
Code:
rm /system/xbin/su
13. Go back to Root Explorer and navigate to /system/bin
14. Find su and long press > copy
15. Navigate to /system/xbin and tap paste
16. Find su and make sure its permissions are rwsr-sr-x
17. If they are, you are done!
If they're not, long press su > permissions and make it look like this:
{
"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"
}
Then you are done

SuperCharge your Tablet with v6 SuperCharger!
1. Download Script Manager from the market
2. Download v6 Supercharger by zeppelinrox here:
RC5 test 2
3. Open Script manager and press browse as root
4. Find your downloaded file in download & tap it
5. Tap the root icon and then hit run
6. Follow the instructions until you get to the "Driver's Console"
7. Type your choice(s)
I recommend 5 & then 20
8. Type 30 and hit enter. The device will reboot. It will take longer to boot than usual, as it is building the cache files
BIG THANKS TO zeppelinrox FOR v6 SUPERCHARGER!

Reserved 5

Reserved 6
You can reply now

nice one quinny when the guide is complete ill give this a go
one qustion when you refer to internal storage do you mean the 250gb hard drive?
and will this root method work on 80g9 250gb version

philmein said:
nice one quinny when the guide is complete ill give this a go
one qustion when you refer to internal storage do you mean the 250gb hard drive?
and will this root method work on 80g9 250gb version
Click to expand...
Click to collapse
It'll work on any g9
I mean when you plug the phone into the computer, a device appears with 2 drives. Internal storage is what you want
If you downloaded it to your tab, just move it to the internal storage with astro
Sent from my ARCHOS 80G9 using xda premium

Quinny899 said:
It'll work on any g9
I mean when you plug the phone into the computer, a device appears with 2 drives. Internal storage is what you want
If you downloaded it to your tab, just move it to the internal storage with astro
Sent from my ARCHOS 80G9 using xda premium
Click to expand...
Click to collapse
only one drive is appearing in my computer saying internal storage size 250gb

philmein said:
only one drive is appearing in my computer saying internal storage size 250gb
Click to expand...
Click to collapse
That's the right one
Also, you're pretty local. I also live in Lancashire

Cool.
I bought the 80 g9 for my brother as a birthday gift awhile ago.
He hasn't rooted or anything but now he probably will.
He's familiar with the SuperCharging bit tho lol
He also created the font I use for my SuperCharger logo (StingRay)

zeppelinrox said:
Cool.
I bought the 80 g9 for my brother as a birthday gift awhile ago.
He hasn't rooted or anything but now he probably will.
He's familiar with the SuperCharging bit tho lol
He also created the font I use for my SuperCharger logo (StingRay)
Click to expand...
Click to collapse
I wonder why he's familiar with supercharging...
Anyway, I'm finishing this topic now, just getting my ****ty net book to work is a triumph
Sent from my Desire HD using xda premium

think ive screwed up here i put the ext4 firmware in the large 250gb hard drive and not the internal the tablet will not boot now i can get back into recovery
but i am unsure what to do from there? its just looping on the archos screen
i need a couple of fags now
i hope i have not bricked it i did everything right except the damm internal drive bit grrr

philmein said:
think ive screwed up here i put the ext4 firmware in the large 250gb hard drive and not the internal the tablet will not boot now i can get back into recovery
but i am unsure what to do from there? its just looping on the archos screen
i need a couple of fags now
i hope i have not bricked it i did everything right except the damm internal drive bit grrr
Click to expand...
Click to collapse
You have the same issue as me. Easy to fix really. Just go to http://update.archos.com/9/gen9/gen9_3.2.79/firmware_archos_it4.aos, download it to your computer and boot into recovery. Scroll to Update Firmware, press power and a drive will appear on your pc. Copy the file to it, and press the power button on the device. Wait and then press power to reboot. You will have to repeat the root process though
Sent from my Desire HD using xda premium

your a lifesaver man
i dont mind repeating coz i wont make the same mistake again
hopefully resurrection time
can i put the ext4 firmware on the archos before i start the whole procedure because i dont get 2 drive in my computer just the one im afraid
also when you say i need to start again do you mean right at the begining from the modaco temp root of from the second section??

philmein said:
your a lifesaver man
i dont mind repeating coz i wont make the same mistake again
hopefully resurrection time
can i put the ext4 firmware on the archos before i start the whole procedure because i dont get 2 drive in my computer just the one im afraid
also when you say i need to start again do you mean right at the begining from the modaco temp root of from the second section??
Click to expand...
Click to collapse
Yeah, you need to to the modaco root again, but you have the files, so it's easy
You can put it on before easily. Just download the file on the tablet and use the app on the tablet called files and do this:
Select Download
Find archos_3.2.79.ext4 and tick it.
Press copy at the top
Press the folder icon in the top left
Press paste (top right), and it will be in the right place
Sent from my Desire HD using xda premium

Added busybox tutorial
Sent from my Desire HD using xda premium

Quinny899 said:
Yeah, you need to to the modaco root again, but you have the files, so it's easy
You can put it on before easily. Just download the file on the tablet and use the app on the tablet called files and do this:
Select Download
Find archos_3.2.79.ext4 and tick it.
Press copy at the top
Press the folder icon in the top left
Press paste (top right), and it will be in the right place
What is the name of the folder the ext4 file should be in
I just want to be sure im doing it right next time?
I'm back up and running now. Once again thanks
Click to expand...
Click to collapse

philmein said:
Quinny899 said:
Yeah, you need to to the modaco root again, but you have the files, so it's easy
You can put it on before easily. Just download the file on the tablet and use the app on the tablet called files and do this:
Select Download
Find archos_3.2.79.ext4 and tick it.
Press copy at the top
Press the folder icon in the top left
Press paste (top right), and it will be in the right place
What is the name of the folder the ext4 file should be in
I just want to be sure im doing it right next time?
I'm back up and running now. Once again thanks
Click to expand...
Click to collapse
It shouldn't be in any folder. Also, make sure Internal Storage is selected (glowing) on the right
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse

[ROM & Kernel] Aurora 1.0.0 Beta - Tutorial now included

Please note that this ROM is intended for the S5830i only! Flash at your own risk!
If you like Aurora just press the thanks button!
{
"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"
}
Contents
Quote 1: Introduction
Quote 2: Features and Credits
Quote 3: Download Link and Installation Instructions
Quote 4: Known Issues
Quote 5: Screenshots
Quote 6: Other Information
2nd Post: Android Shell Environment Information and Tutorial​
1. Introduction
I've been working on this for a couple of months now and this is a very stable ROM that I hope you will agree, has some great features (see below). It doesn't try to act like any particular later version of Android, I've just gone for what looks best in each individual case. I am experiencing almost no force closes whatsoever and no forced reboots at all. Hopefully others will confirm the same. I have declared this first version a beta as I haven't tested it on every firmware and one person can only test for and eliminate so many bugs. It should run fine on all firmwares. I would be grateful if you could report any bugs or issues in this thread.
Click to expand...
Click to collapse
2. Features and Credits
Core System Features
Prerooted with su binary and Supersu root access management tool
BusyBox v1.20.2-linusyang - Fully working - the latest and best version.
ROM deodexed by me
Rafael.Baugis kernel E3 rev. 201212101860
Android (Bash) Shell Environment (original thread) with many great features including:Bash shell v4.1.11(2)
Custom login screen
Multi-session command history
Tab auto-completion
Colour coded ls output
Nano text editor - fully working!
Dropbear secure shell (ssh) server
adbwifi script - surprisingly it allows you to connect to adb over wifi
reboot script - reboot, reboot recovery, soft/hot reboot, power off device
remount script - easily remount /system as re-writable / read-only​AdAway hosts file - blocks advertisements - install Adaway to remove/update
ROM based on XXLI1 - Was thinking of upgrading it to latest firmware but there has been issues with that particular firmware
Apps Features
Bloatware deleted
Chrome as default browser
Total Commander as default file manager
ICS Gallery as default gallery
No-Frills CPU Control
DroidWall firewall
Latest Play Store
Slightly modded Terminal Emulator included with Bash as default shell (Hacker's Keyboard recommended)
Zipaligned all apps for optimized performance
Still 62.3MB free on /system
Theming Features
Xperia S Launcher
SkyRaider boot animation
15 Toggles and 6 Lockscreens Mod
Lidroid Preferences
Almost all icons of all apps changed for custom hand-picked ones
1% Battery Mod
Light blue right-hand status bar icons - personally redesigned some of the icons
Light blue status bar clock
Themed status bar drop-down
Jellybean menu sound
Aurora-coloured overscroll
Aurora landscape wallpaper
Other minor theming stuff
Credits
Rafael Baugis for his excellent kernel
SenseiSimple for Android Shell Environment
Alucard1989pl for 15 Toggles and 6 Lockscreens
bijoy91 for camera settings small fonts fix
UOT kitchen for some of the theming
dsixda's Android Kitchen to deodex the ROM
Anybody else that I've accidently missed out!
Click to expand...
Click to collapse
3. Download Link and Installation Instructions
Download Link (Click Here)
1. Download Aurora's zip file.
2. Put Aurora's zip file in "/sdcard".
3. Reboot into recovery.
4. If you have stock recovery, select "apply update from sdcard" and use this zip file (put it in /sdcard) to open CWM recovery.
5. Once in CWM recovery, select "wipe data / reset" > "Yes"
6. Now select "install zip from sd" > "choose zip from sd card" > "aurora<version>.zip" > Yes
7. Wait for installation to finish, press the back button and select "reboot system now"
The phone will now reboot into Aurora. The first boot will take around two minutes, during which the screen will go blank for around one minute, so no need to panic! Subsequent boots will be much quicker.
Note: When you install this ROM, you will get e3 (stock) recovery. If you need the permanent version of CWM (because and only if you have an ext4 filesystem), then simply flash Rafael's CWM boot.img after flashing Aurora's zip file.
Click to expand...
Click to collapse
4. Known Issues
An icon of an app that is stored on the SD card that has been placed on the home screen / desktop occasionally dissapears after rebooting. This is a bug in the Xperia S launcher and there is not an awful lot I can do about this personally. There are a couple of workarounds however.
Workaround 1: The obvious, move the app to the phone's internal memory
Workaround 2: Place apps stored on the SD card in a folder on the home screen / desktop and they will not dissapear after reboots.
Click to expand...
Click to collapse
5. Screenshots
Click to expand...
Click to collapse
6. Other Information
You may use and/or redistribute my work but please give me credit. If redistributing this ROM, please link to this thread.
By the way this is my first ROM, thought I'd sneakily leave that until last
Click to expand...
Click to collapse

Android Shell Environment Information and Tutorial
Android Shell Environment Information and Tutorial
You may want to read through the original thread first.
Android Shell Environment Aurora Specific Information
​
The main difference between the original version of Android Shell Environment and the one included in Aurora is that all files are stored on the /system partition except for a couple of configuration files.
Take a look in /system/sbin for the useful utilities mentioned in the original thread
Scripts are in /system/bin (along with a lot of other Android system files).
Most of the configuration files are in /system/etc although a couple are in /data/local
In Aurora, unlike the original version, there is no option to make Bash the default shell. Firstly, this causes a bootloop on the S5830i and secondly it is pretty pointless anyway because Bash doesn't load its configuration files when set as the default shell which removes much of its functionality.
The binaries htop, scp, ssh and vim have been removed because they do not work. For all of these, there are working alternatives. For htop, use top instead, for scp use rsync, for vim use nano, for ssh use adbwifi. The text editor Joe does not work properly but has been included. Either use Nano instead or if you can get it working then please tell me how you did it!
Click to expand...
Click to collapse
Android Shell Environment Tutorial​
How To Use Bash​To start Bash:
ADB: From your PC command line, type 'adb shell' <enter>, then type 'bash' <enter>. Do not type 'adb shell bash' all in one go, this will cause problems.
Terminal Emulator: Bash loads automatically.​
Command History - Press the <UpArrow> and <DownArrow> keys to scroll through your command history. Use Hacker's Keyboard to do this in Terminal Emulator.
Auto Completion - Start typing the name of a file, folder or command, then press <Tab> to have Bash automatically complete the rest of the text. If nothing happens when you press <Tab>, then there may be multiple options, double press <Tab> to see the multiple options.
For auto-completion in Terminal Emulator, I have set a default preference so that when the phone's back key is pressed it send's out the keyboard <Tab> key. Note that this means that you cannot close Terminal Emulator using the back key, you have to enter the 'exit' command. You can change this preference in the app's settings.
To leave Bash: - Enter the command 'exit'
Click to expand...
Click to collapse
How To Use Nano Text Editor​
Nano is a user friendly command line editor. To start nano and create a new file simply type 'nano'. To start nano and open a specific file for editing type, e.g. 'nano /system/build.prop'.
If you are editing on the system partition then make sure you enter the command 'remount rw' before starting nano to mount /system as re-writable.
When you are finished editing, to exit nano enter the key combination <Ctrl>+<X>. If you have modified the file, nano will ask you if you wish to save it and request that you enter a file name.
That's basically all there is to it when it comes to the basics of this program.
Click to expand...
Click to collapse
How To Use the Reboot Command​I have rewritten the original reboot script to include a couple more parameters. Reboot now accepts the following options:
reboot - normal reboot
reboot recovery - obvious
reboot hot - hot/soft/quick reboot, restarts the Android runtime
reboot off - powers off the device, alternatively you can use the command 'halt' to acheive this
Click to expand...
Click to collapse
How To Use The Sudo Command​sudo is a well known Linux feature that runs a single command as root, useful if you generally want to work as a normal user for safety/security.
An example of this would be 'sudo adbwifi on'
Click to expand...
Click to collapse
How To Enable/Disable ADB Over WiFi​Do NOT do this from ADB shell, do this from Terminal Emulator.
Enter the command 'adbwifi on'
Follow the prompts on-screen, it tells you the rest.
To disable use 'adbwifi off'
Click to expand...
Click to collapse
How To Demote Yourself To Normal User In ADB Shell​Note: Do not do this from Bash because it doesn't work, either run it before you start bash or type 'exit', run the command, then start Bash again.
By default, ADB shell logs you in as root because Rafael's kernel has an ADB 'root mod'. This is generally very handy but sometimes, working as root is not ideal because it's very easy to brick your phone. Thankfully it is actually possible to be demoted to normal user status with the following command:
'su shell'
If you wish to return to root user, enter the command 'exit'
Click to expand...
Click to collapse
How To Use DropBear Secure Shell Server​
Dropbear allows you to login to your phone's shell (i.e. like adb shell / terminal emulator) from another device such as a PC or phone using, for example, WiFi.
To start Dropbear with the password 'pickledjelly' enter the command:
/system/sbin/dropbear -A -N root -U 0 -G 0 -C pickledjelly -r /system/etc/dropbear_rsa_host_key -b /system/etc/.dbbanner
To login from another Android device you can use e.g. Connect Bot,
use ssh protocol and in the text box enter [email protected]
Replace x and y with your phone's IP address from your WiFi router (you can get this with the command 'ifconfig')
To login from a PC running Linux enter the command:
ssh 192.168.x.y
To stop the Dropbear server issue the command 'killall Dropbear'
Click to expand...
Click to collapse

gud work man......i think this rom can have great future.....

make it final.

great job dude..:good:. now trying to combined with cronmod script by styrke...(only this way to solve our internal memory issue)
well done... all working with cronmod...

Glad some like it, cheers :good:

your rom sounds great! but is there really no way to get it based on xxlk3 (ins) ?

HeathenMan said:
your rom sounds great! but is there really no way to get it based on xxlk3 (ins) ?
Click to expand...
Click to collapse
Hi HeatherMan, I have held back on upgrading the ROM to XXLK3 so far because there were issues with IMEI numbers going awol when combining XXLK3 ROMs with custom kernels. I'll look at this again at some point though.
Aurora does work perfectly fine on XXLK3 firmware though, I currently have XXLK3 UK myself.

hi. why u don't use hell_lock kernel? thats might be better.i guess so.

SemBoyHehe said:
hi. why u don't use hell_lock kernel? thats might be better.i guess so.
Click to expand...
Click to collapse
hell_lock? wtf it is pre alpha and not stable with less features, what kind of better is THAT ?!?

HeathenMan said:
hell_lock? wtf it is pre alpha and not stable with less features, what kind of better is THAT ?!?
Click to expand...
Click to collapse
hey bro. u se ' I GUESS SO' u see that many people have trouble on that ketnel like dont have imei, earphone prob n etc. that why i guesd so

I chose Rafael's kernel because it has the most features and is currently quite stable. Hells Fusion does not presently have full IP tables needed for firewalls and has no governors or schedulers other than the standard ones.
When testing the XXLK3 IMEI issue I found that it occurred in Hells Fusion kernel as well as Rafael's. I also encountered the headphone problem at one point and found that it was because I'd flashed the boot.img but did not have the kernel modules installed.

SoupKit (again)...When you're fed up with trying to get ADB to connect in Windows.

The SoupKit
{
"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"
}
What is SoupKit? At it's heart, SoupKit is for those who are tired of messing around with Windows and are ready to do try something that works. It was created to be "sort of" modular in that after the ADB installer has been installed, other Linux scripts can be installed and run from the command line by just typing the name of the script and without worrying about changing directories or dealing with permissions. It's intended to make the transition from Windows to Linux for Android a little bit easier.
How does it work?
The SoupKit ADB Installer --- FOR ALL KINDLE FIRES
This puts everything where it needs to be, installs any necessary dependencies, installs drivers, configures Linux to run adb and fastboot commands, puts the SoupKit in your $PATH and cleans up after itself, all while taking a fraction of the space needed for the Android SDK. What this means for you is, you will be able open any terminal window and start entering adb or fastboot commands immediately. There's no need to change directories, add sudo commands or certain operators that are confusing to command line newbies ( ./ ). You can enter commands just as you see them in tutorials. No more worrying about “ADB Offline”, “Status Unknown” or “List of devices attached ????????????????”. This alone can make a huge difference for anyone having Kindle Fire problems that can't be fixed in Windows or those who are overwhelmed by the technicalities of configuring Linux for Android.
What you need:
First, you need Linux. Don't worry, it's not as bad as you may think.
Luckily, all Linux distros are free to download and install on your computer. It can also be booted from a USB flash drive so you don't have to wipe out your current OS (although you probably should anyway). You can use a VM, but the only VM that I've found that can detect the Kindle Fire in fastboot mode is Parallels. Vmware won't cut it, and VirtualBox sure as hell won't cut it so don't waste your time with them if you ever need to do anything in fastboot (if you're bricked, you need fastboot).
Probably the best method to get Linux running for a new user is by setting up a Linux LiveUSB.
I'm not going to teach you how to set up a Linux LiveUSB, but there are plenty of FREE programs out there that will not only create a Linux LiveUSB for you, but will download your choice of distro as well, and all you need is a USB flash drive (preferably 8GB or larger). A Google search of “Linux LiveUSB” will offer plenty of choices, although, PendriveLinux seems to be a favorite among most. Just be sure to add plenty of “persistence” (1 or more gigabytes) or you will lose everything every time you reboot. And the better quality of flash drive you can use, the better it will be in the long run. Some flash drives just don't do well and can cause some file system corruption over time (not something you want to be dealing with while you're having Kindle Fire problems).
You'll also have to figure out how to boot your computer from a USB. Check your computer's BIOS manufacturer website for instructions on how to do this.
If you're using a LiveUSB, there is no root/sudo password, just hit enter.
Do not use a USB 3.0 port
Once you have Linux installed and booted, you need to make sure your Internet is working. It may take some configuration on your part but it is necessary for the SoupKit to install properly. Luckily, once you have an Internet connection in Linux, the hard part is over.
Don't put the SoupKit.zip on the USB drive before creating the LiveUSB. Instead, use the web browser to navigate to this page and download it once you have Linux running and your Internet connected. Once it's downloaded, you'll likely find it in your Downloads folder.
SoupKit has been tested extensively on all the latest versions of Ubuntu and Mint, but it hasn't really been tested on anything outside of that. Try other distros if you will, but be warned.
To install:
Right-click the “SoupKit.zip”, select “Extract here” open the SoupKit folder and follow the instructions in the README.
Is that all?
NOPE. What SoupKit would be complete without a little something to go with it? SEE POST #2

Due to recent updates, I've decided to remove the option to install Hashcode's 2nd bootloader. There are too many areas where things can go wrong so I think it would be best to let the user follow the small handful of instructions in the 2nd bootloader thread to get it done. IMO, it is not worth the risk to rely on the user to make sure a downgraded stock bootloader is installed before running the script. Plus I think using a script toinstall the downgraded bootloader gives users a false sense of safety in what is potentially very dangerous to do.
​
ROOT PLUS for 2nd Generation Kindle Fires
That's right. This works for ALL 2nd generation Kindle Fires
What does it do?
The screenshot above should answer that question pretty quickly.
What do you need to know?
Since Hashcode's bootloader hack is device specific, you must download the version for your device. Each one has the exact same script but the stack, boot and recovery images are different for each particular device. You must have the SoupKit installed for this to work properly. It installs in the same way as the SoupKit; unzip, double click, run in terminal, blah blah.
Make sure you have ADB enabled under “Security” in the settings.
Anything else?
At any point after installation, if you need to run the utility again, just type "rootplus" in the terminal.
What's next?
I have a few more things in store for you guys and they will all be made for the SoupKit. As packages are installed, just type the name of the package in any terminal to launch them at any point (hence "modular"). Everything will be easy to install, easy to launch, and new user friendly.
Don't be skerrd. Move out of your comfort zone a little and give Linux and SoupKit a try. I'm sure you won't be disappointed.
Credits:
* Bin4ry - of course, for providing the root exploit
* prokennexusa and his team - for testing this out on all of the second generation devices
* Thepooch - for extensive testing and always being there to lend a hand
Downloads:
SoupKit - http://d-h.st/PbX
RootPlus for all Kindle Fires - http://d-h.st/jOe

Changelog:
04-23-2013 - Update (RootPlus)
* Removed option to install Hashcode's 2nd bootloader, for safety reasons. There is absolutely nothing wrong with Hashcode's 2nd bootloader. The risk lies in recent updates from Amazon.
03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error
03-16-2013 - Bugfix: (RootPlus)
* Fixed issue with permissions on the rootplus script
03-10-2013 - Update: (RootPlus)
* Added extra safety measures, including MD5 check on 2nd bootloader install
02-23-2013 - Initial release

worked great. thanks for a great tool. easy to use.

Awesome...thank you..just set this up on my ubuntu netbook...going to try it today when I update twrp

Update 3-10-2013: Added extra safety measures, including MD5 check on 2nd bootloader install

Works great!

ok just got a new laptop and tried installing this and no go. i know its my fault..i have a fresh install of ubuntu 13.04 and i followed the instructions but when i double click the install.sh file all it does is open a document... when i installed this on my netbook with ubuntu 12.10 i had no issue. any help would be appreciated. i am new to linux

wojo797 said:
ok just got a new laptop and tried installing this and no go. i know its my fault..i have a fresh install of ubuntu 13.04 and i followed the instructions but when i double click the install.sh file all it does is open a document... when i installed this on my netbook with ubuntu 12.10 i had no issue. any help would be appreciated. i am new to linux
Click to expand...
Click to collapse
Yeah, when I updated the script, I forgot to change the permissions...
Give me a little while and I'll fix it for you.

3-16-2013: Fixed issue with permissions on the rootplus script

the issue wasnt with the rootplus it was with the soupkit itself the install.sh script

wojo797 said:
the issue wasnt with the rootplus it was with the soupkit itself the install.sh script
Click to expand...
Click to collapse
That's interesting. I checked the permissions for all scripts and executables before uploading.
I just checked on it again and they are all executable. Perhaps it has something to do with your settings or the version of Ubuntu you are using (only tested on 12.10 and earlier).
You can make a file or script executable by entering the following in the terminal:
Code:
sudo chmod a+x <file>
Or you can right-click on the file, select Properties > Permissions > "Allow executing file as program"

[OK thankOTE=soupmagnet;39303980]That's interesting. I checked the permissions for all scripts and executables before uploading.
I just checked on it again and they are all executable. Perhaps it has something to do with your settings or the version of Ubuntu you are using (only tested on 12.10 and earlier).
You can make a file or script executable by entering the following in the terminal:
Code:
sudo chmod a+x <file>
Or you can right-click on the file, select Properties > Permissions > "Allow executing file as program"[/QUOTE]
Ok thank you.. Appreciate the help and all then work...I'll try as soon as possible

03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error

03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
If you downloaded yesterday's update, please install this one. There was a bug preventing the 2nd bootloader install. It is fixed now.
Sorry for the inconvenience.

04-23-2013 - Update (RootPlus)
* Removed option to install Hashcode's 2nd bootloader, for safety reasons.
By the way, there is absolutely nothing wrong with Hashcode's 2nd bootloader. The risk lies in recent updates from Amazon and the requirement to downgrade the stock bootloader before continuing with the 2nd bootloader install process.

Hi,
I'm totally new to linux, and i managed to install the latest Linux mint (v14.0) I was also able to connect to the internet and i downloaded both the soupkit and rootplus using linux. I extractred the files and doubled clicked on the install.sh as per the readme file however, after i double click it, all the contents of the folder disappear and i don't get any options as per the readme file. The same happens with the rootplus install.sh file, all the files disappear.
These are the steps i've followed.
Installed Linux Mint v14.0 on the system after making necessary partitions(ext4 journal)
Internet connectivity present.
Downloaded both the files into the downloads folder and extracted them
double clicked on the install.sh file and everything disappeared fro the respective folders.
Please guide me as i'm completely blank here.
Regards,
CD

Hi,
I was able to make it work. Instead of double clicking the .sh file, i opened the terminal window in the extracted folder, got super user access and executed this command:
sh install.sh
So now my kindle is rooted and ads free.
Thanks a lot @soupmagnet.
Regards,
CD

So, is it safe to assume this will work on a Kindle Fire HD 8.9" running 8.3.1 fw? Thanks!

anacondo said:
So, is it safe to assume this will work on a Kindle Fire HD 8.9" running 8.3.1 fw? Thanks!
Click to expand...
Click to collapse
Sorry to answer an old post but yes.

[TUTORIAL] Keeping root after upgrade from v10x to v20x

↓ A new root method! ↓
There is now a new root method, that does not require downgrade!
http://forum.xda-developers.com/showthread.php?t=2180688
↑ Read this thread first! ↑
Prerequisites
A rooted LG O4X HD with a v10 firmware. (SuperSU preferred - personally tested)
Device adb drivers installed (so that a phone is detected as an ADB device when in B&R Recovery mode), adb itself is included in the archive
You need an installed Busybox! (/system/bin preferred, or need to edit bat file)
Warning: Do NOT do factory reset between step 1 and step 3! Otherwise /data/rootkit will be deleted, and you will have to start over.
Important note for linux users: bat files are for Windows. If you are using linux, i assume that it will be easy for you to open bat files and do commands by hand.
Step 0
Backup all your settings, and data from internal storage (!), cause factory reset (wipe) will be required.
You can try using LG's backup tool or Titanium Backup or anything else.
Also I'd strongly recommend removing SIM card and SD card from the phone.
Step 1
Make sure USB debugging is enabled (Settings -> Dev Options -> Debugging)
Connect your phone to your PC.
Execute file step0.bat and ensure that you grant su priv to ADB shell (2000).
Now execute file step1.bat - it:
- creates folder /data/rootkit
- copies busybox from /system/bin to /data/rootkit
- copies su from /system/xbin to /data/rootkit
- copies Superuser.apk from /system/app to /data/rootkit
- ensures owner and group of 0 for those files
- chmods files to required attributes (06755 for su, 0644 for apk, 0777 for busybox)
Result should be something like this: Note: In v2 i modified step1, so it tries to copy busybusybox from bin and xbin - one of them will fail, thats normal.
{
"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"
}
Step 2
Upgrade your firmware to v20a. For example: http://forum.xda-developers.com/showthread.php?t=2069723
DO NOT DO FACTORY RESET! OR YOU WILL DELETE /data/rootkit FOLDER! DO STEP 3 FIRST!
Step 3
After successful upgrade shut down your phone.
Now, with USB connected (!!), hold volume up and power, and keep holding it at least until you hear windows "new device" sound.
You must see something like this:
Now execute file step3.bat - it:
- remounts system as writeable
- copies su to /system/xbin/
- copies superuser to /system/app/
- sets permissions on those files
Step 4
Now you can hold power button to reboot or just run step4.bat to reboot instantly.
Make sure that root is working, before doing factory reset!
Now you are STRONGLY recommended to do factory reset - or many things will mess up, such as lock screen settings or storage.
AGAIN warning, that factory reset WILL wipe internal storage, look at step 0
If you did all things correct, root will be kept (because it is on ro system partition now)
Step 5
Enjoy.
Note
If you are already at v20a and you want root, you can:
1) Wait for official release, with really unlocked BL - then it will be possible to install CWM -> get root
2) Wait until I make some interaction with B&R daemon in recovery
3) Wait for someone to find easier method
4) If you dont want to wait, you can go back to v10x (warning: all data will be wiped!), root phone, and do the procedure.
Any comments, notes, criticism or anything else very welcome!
Edit: In version 2 it tries to copy busybox from /system/bin and /system/xbin, thanks to AlderCass for pointing out

Nice work friend :good:

I don't have adb on my pc, is there a way to simply download the drivers? I ask because my current pc doesn't have the internet
Sent from my LG-P880 using Tapatalk 2

@non4 said:
I don't have adb on my pc, is there a way to simply download the drivers? I ask because my current pc doesn't have the internet
Sent from my LG-P880 using Tapatalk 2
Click to expand...
Click to collapse
adb is included in the archive... i will see what i can do about drivers.
try to connect phone to your PC with debugging on and do "adb devices" from the folder with unpacked adb
if it sees your device - then good

@SkyDev
great findings, nice to see ideas expand to something useful.
did you also went all way and tried to install a changed/modified boot.img and add it to the LNX partition in /dev/block/mmcblk0p2 or /dev/block/platform/sdhci-tegra.3/by-name/LNX , it might just be our bootloader do work as unlocked and we can write unsigned boot / recovery img
edit;
i believe you can easily test it from recovery and su in here. even if you get security error on "boot", i think recovery can still be booted and you can recover the backup of the mmcblk0p2 partition (men always do backups)

Utterly fantastic work, and I'm sure this discovery will be the first huge step in truly unlocking this device. Congratulations!
Sent from my LG-P880 using xda app-developers app

skydev said:
adb is included in the archive... i will see what i can do about drivers.
try to connect phone to your PC with debugging on and do "adb devices" from the folder with unpacked adb
if it sees your device - then good
Click to expand...
Click to collapse
Isn't adb a pain to install? At least it was back in the day when I rooted my desire z with froyo thanks for the good work I will try get this to work on my own
Sent from my LG-P880 using Tapatalk 2

Dexter_nlb said:
@SkyDev
great findings, nice to see ideas expand to something useful.
did you also went all way and tried to install a changed/modified boot.img and add it to the LNX partition in /dev/block/mmcblk0p2 or /dev/block/platform/sdhci-tegra.3/by-name/LNX , it might just be our bootloader do work as unlocked and we can write unsigned boot / recovery img
edit;
i believe you can easily test it from recovery and su in here. even if you get security error on "boot", i think recovery can still be booted and you can recover the backup of the mmcblk0p2 partition (men always do backups)
Click to expand...
Click to collapse
Well, when now root is easily obtainable, you can do it
I think you are more experienced in all those things, i am low-levelly playing with phones only for 3-4 days so far.
I just dont want to trash stuff to the extent that reflash would be required.
Anyway i worked on the method almost 10 hours instead of sleeping at night, so now i think i going to go take some "Deep sleep" /10:46/
Anyway, i am noting again: if anyone also has disassembly skills, then you really should try to disassemble and analyze brd (backup and recovery daemon) - it runs at recovery with root rights, listens for commands on udp port, and probably can be used for "perfect root" (root without reflashing, and maybe even any LG device)

for people having issues using adb, you can download "terminal" from play , and do the same steps except do not start from a windows shell with adb
you just open the terminal.
secondly all files needed, should be tar'd instead, so the busbox more easily can unpack all files with proper rights instantly to the dest folder.
ie.
# cd /data ; tar xf /data/local/tmp/rootkit.tar
assuming rootkit folder is extracted and all files already was properly set with rights in linux when tar'ing the folder.
so conclusion
you do 3 steps to do this.
1. download rootkit.tar
2. open terminal on phone
3. cd to /data and extract(tar xf) rootkit.tar from where you put it when downloaded
this is all without adb used.
but you need adb in the end to run the bat file

Dexter_nlb said:
for people having issues using adb, you can download "terminal" from play , and do the same steps except do not start from a windows shell with adb
you just open the terminal.
secondly all files needed, should be tar'd instead, so the busbox more easily can unpack all files with proper rights instantly to the dest folder.
ie.
# cd /data ; tar xf /data/local/tmp/rootkit.tar
assuming rootkit folder is extracted and all files already was properly set with rights in linux when tar'ing the folder.
so conclusion
you do 3 steps to do this.
1. download rootkit.tar
2. open terminal on phone
3. cd to /data and extract(tar xf) rootkit.tar from where you put it when downloaded
this is all without adb used.
but you need adb in the end to run the bat file
Click to expand...
Click to collapse
Well, adb will be required anyway, and i want to keep freedom of choosing the su binary and Superuser.apk file.
The only requirement: su must grant root if called from recovery (when Superuser.apk is not accessible)
Also, why mess with terminal? You can easily misspell command, and they are long and important (because executed as root)
But idea with tar is good, maybe it will be required to do it this way, from B&R way.

I'm trying this method now and I noticed that a command in step1 fails on my system.
I changed:
adb shell su -c cp /system/bin/busybox /data/rootkit/
to
adb shell su -c cp /system/xbin/busybox /data/rootkit/

postacik said:
I'm trying this method now and I noticed that a command in step1 fails on my system.
I changed:
adb shell su -c cp /system/bin/busybox /data/rootkit/
to
adb shell su -c cp /system/xbin/busybox /data/rootkit/
Click to expand...
Click to collapse
Prerequisites
A rooted LG O4X HD with a v10 firmware. (SuperSU preferred - personally tested)
Device adb drivers installed (so that a phone is detected as an ADB device when in B&R Recovery mode), adb itself is included in the archive
You need an installed Busybox! (/system/bin preferred, or need to edit bat file)
Warning: Do NOT do factory reset between step 1 and step 3! Otherwise /data/rootkit will be deleted, and you will have to start over.
Important note for linux users: bat files are for Windows. If you are using linux, i assume that it will be easy for you to open bat files and do commands by hand.
Click to expand...
Click to collapse
Already mentioned in first post.

lukas77 said:
Already mentioned in first post.
Click to expand...
Click to collapse
I stated that I changed the line to work "on my system".
So everybody trying this will pay attention to that...

sry for this newbie ques,
but how to install adb drivers in our device..

jitesh22 said:
sry for this newbie ques,
but how to install adb drivers in our device..
Click to expand...
Click to collapse
There are many posts on these forums on how to do this - search for them, as this thread does not deal with that.

Everything works perfect, and now i have root on my JB .

Works like a charm! Thanks so much skydev! :laugh:

I upgraded to v20a with these instructions and now I have a rooted v20a.
Thank you very much skydev.
A picture for proof: http://g1303.hizliresim.com/17/7/ktz5m.png
I think we will be able to root when new versions arrive as long as we keep the /data/rootkit folder.
Edit: I upgraded to v20a with my LG PC Suite Version Hacker ( http://forum.xda-developers.com/showthread.php?t=2134192 ) and did no factory reset after the upgrade. Everything seems to work fine upto now.

quick and dirrrrrty
thats how i like it^^
well done

AW: [TUTORIAL] Keeping root after upgrade from v10x to v20x
Worked fine. There we're no problems. Did the kdz flashing via virtual machine with windows and the rooting part on mac os x since your scripts can be easily adapted. Also i dont have to care about adb or fastboot drivers.
Gesendet von meinem LG-P880 mit Tapatalk 2

[ROM] [4.3.1] CyanogenMod 10.2

Hi, if anyone would like to run a 4.3.1 Google OS on a Archos G9 80S device (and currently only this), download and extract this file:
19_01_2014-13_32_32
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!).
- 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 !
What's new ?
------------ since 19_01_2014-13_32_32 -------------
Last attempt to satisfy "H" model users. Wrong fstab definition file was used.
ArchosControlCenter: Alternate command for enabling disabling 3G service activation/deactivation.
------------ since 17_01_2014-20_17_32 -------------
KSM (Kernel samepage merging) support. (Enable it in CM performance options).
HDMI enable for 101 models too.
WLAN MAC address taken from device. Until now in my releases, the MAC address where the same for all devices. (gave some conflicts, when two devices are used in parallel).
------------ since 22_12_2013-13_29_20 -------------
Deactivated PCB temperature sensor. It is not part of the devices, and (my) default setting gives the cpufreq
module a wrong view of the situation. Now it should reduce the reboot which is caused by critical temp, by reducing core speed.
------------ since 19_12_2013-23_43_36 -------------
Using CPUFreq from 3.0.31 omapzoom reference kernel
Included app from @mordesku (modified by me) -> 3G should work!
Note that if you only pushed the image as update, please make sure to delete the /data/data/com.android.providers.telephony/databases/telephony.db
(adb shell rm /data/data/com.android.providers.telephony/databases/telephony.db) and reboot the device to rebuild.
I forgot to include the apns-conf.xml so there are no APN's available (as result no data connection can be established).
Removed my Widget to not affect the archos control center app
Some kernel changes.
Enabled zram and init.d
Initial support for H models (testing and patches are welcome).
Newest CM Updates: Changes since last release
------------ since 02_12_2013-22_56_07 -------------
Removed clicks when audio driver is closed
Reduced the volume a little bit to avoid scratches
Removed default dpi setting on build
Newest CM Updates: Changes since last release
------------ since 21_11_2013-21_45_53 -------------
Using new pvr library SGX-BIN: DDK binaries and KM source [email protected]
HWComposer 1.1 interface
No ICS audio blob anymore. Adapted omap upstream audio HAL.
Some internal audio extensions by TI (omap_enhancement)
Kernel audio sources updated to 3.0.31 omap upstream release.[/INDENT]
------------ since 08_11_2013-22_14_52 -------------
CM10.2
Upstream init.rc
TI Openlink WLAN driver R5.SP6.01
Temporary disabled ClockworkMod Recovery
A widget "Archos Control Center" where the user can activate the deep sleep behavior. Warning: If you use the archos as alarm clock you will oversleep! (It only will wake up, when pressing the power button).
Also the 3G port can be activated with this widget. I discovered some hangs, which can only solved by removing and re-adding the widget on the screen. If someone can help me with this widget, please have a look at: github It's my first app ever... so it is very ugly =)
Initial A101s support.
Something I've not tried...
3G USB Stick is working.
Issues:
- GPS not reliable (as usual for every release....) -> After complete new system ("Reset Android & Storage") the GPS is working very good. Subsequent boots later it gets worse at my device(s):
My Workaround: Go into Settings->Apps->All->Google Service Framework and delete data and cache. Then reboot and GPS should e working. Also I get sufficient results with the GPS Toolbox App.
21_11_2013-21_45_53:
Microphone as degraded sound quality compared to the stock rom.
Some sound clicks here and there when system sounds are turned on.
Audio sound is a little bit quiet compared to the stock rom. (Needs to be adjusted by myself).
Can't test HDMI (both audio/video). (It's also not an use case for me). If someone would like to help....
HDMI scaling issues
"H" models doesn't seem to work.
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
Archive:
17_01_2014-20_17_32
22_12_2013-13_29_20
19_12_2013-23_43_36
02_12_2013-22_56_07
21_11_2013-21_45_53
08_11_2013-22_14_52
07_11_2013-22_53_33
Archos CM10.2 - 26_10_2013-23_26_11

Thanx for your work now i'm bakcig up my data and will test as soon as possible. Is this build run from disk images or it replace original archos system?

mordesku said:
Thanx for your work now i'm bakcig up my data and will test as soon as possible. Is this build run from disk images or it replace original archos system?
Click to expand...
Click to collapse
As usual for the custom Android releases for this archos device , they don't replace the original partitions. But it is not possible to run both in parallel. So practically yes, it replace the original system.

Quallenauge said:
- Wait for reboot your devices : after reboot you can see Android prepares the system for a while .....be patient !
Click to expand...
Click to collapse
Hi again. My tab is displaying archos logo for long time (about 10-15 minutes) now is this normal. I have question where exacty i should put the update file. In debian i put it to /media/data/data/local where /media/data is my mount point.
{
"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"
}

mordesku said:
Hi again. My tab is displaying archos logo for long time (about 10-15 minutes) now is this normal. I have question where exacty i should put the update file. In debian i put it to /media/data/data/local where /media/data is my mount point.
Click to expand...
Click to collapse
Sorry, my fault.....
Can you please rename the file while you copy? (I have corrected my first post).
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/data/local/[B]archos.ext4[/B]

Quallenauge said:
Sorry, my fault.....
Can you please rename the file while you copy? (I have corrected my first post).
Code:
sudo mkdir <Mount_Path>/data/local
sudo cp archos.ext4.update <Mount_Path>/data/local/[B]archos.ext4[/B]
Click to expand...
Click to collapse
(Just for reference, when using the update mechanism the file has to placed here:
Code:
sudo cp archos.ext4.update <Mount_Path>/data/[B]media[/B]/archos.ext4.update
)

Quallenauge said:
Sorry, my fault.....
Can you please rename the file while you copy? (I have corrected my first post).
Code:
sudo mkdir <Mount_Path>/data/local
sudo cp archos.ext4.update <Mount_Path>/data/local/[B]archos.ext4[/B]
Click to expand...
Click to collapse
Renamed file as you said but still tab is stuck on archos logo.
--- edit
My bad . Got to many data directories. Rom boots form /media/data/local/archo.ext4 before was /media/data/data/local/archos.ext4

mordesku said:
Renamed file as you said but still tab is stuck on archos logo.
--- edit
My bad . Got to many data directories. Rom boots form /media/data/local/archo.ext4 before was /media/data/data/local/archos.ext4
Click to expand...
Click to collapse
Thanks for your reply. I corrected the paths in previous posts.

Is it stable for very day use???
Everithing working lie Cam and HW video?

Using it since yesterday. It's very smooth and fast. No freezes at all.
Sent from my ARCHOS 80G9 using Tapatalk 4

Installation on Mac OS X
For those of you who want to brave installation from a Mac, you can use FUSE to mount the data partition. You'll need to follow the directions here to be able to mount the partition with write access. Once the partition is mounted, follow @Quallenauge's fabulous instructions! I'm watching a spinning CyanogenMod logo right now!
Note: If you copy the file from the command line, you'll probably get a message saying "could not copy extended attributes to data/local/archos.ext4: Operation not permitted". Don't worry, the file copied just fine. If you're really paranoid, run md5sums on the file to verify.
- Dave

stealthdave said:
For those of you who want to brave installation from a Mac, you can use FUSE to mount the data partition. You'll need to follow the directions here to be able to mount the partition with write access. Once the partition is mounted, follow @Quallenauge's fabulous instructions! I'm watching a spinning CyanogenMod logo right now!
Note: If you copy the file from the command line, you'll probably get a message saying "could not copy extended attributes to data/local/archos.ext4: Operation not permitted". Don't worry, the file copied just fine. If you're really paranoid, run md5sums on the file to verify.
- Dave
Click to expand...
Click to collapse
Damn to install it yesterday i installed debian on virtualbox on my macbook
Sent from my ARCHOS 80G9 using Tapatalk 4

My tablet is still showing the snazzy CyanogenMod bootloader image after an hour and refuses to load the Android GUI. I tried starting the process over again with the same results. I am able to get to an adb shell and play around there, but Android never finishes loading. I'm running a G9 80S with 1GHz OMAP 4430 and 512MB of RAM. Logcat attached.

Hi,
thank you for building this and all your other ROMs.
Quallenauge said:
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/data/local/archos.ext4
Click to expand...
Click to collapse
This is inconsistent.
Is it local/ or data/local/?
I tried to install the ROM following your instructions.
I renamed "archos.ext4.update" to "archos.ext4".
I reset Android and Storage, exported the USB storage, on my machine it was mounted on /media/username/data.
I then used the following commands:
Code:
sudo mkdir /media/username/data/local
sudo cp archos.ext4 /media/username/data/local/
Then I selected "OK" in the tablet and "Flash Kernel and Initramfs" followed by:
Code:
sudo cp zImage /media/username/A80S_REC/
sudo cp initramfs.cpio.lzo /media/username/A80S_REC/
Then I rebooted the tablet.
Now the tablet was flashing the Archos logo for a second and then rebooting, in a loop.
So I guessed the local/ directory was wrong and I might have to use data/local/.
I repeated the steps above, replacing "local/" with "data/local".
This time the tablet didn't reboot in a loop, but I only got the static Archos logo, not the animated Archos logo or the CyanogenMod logo.
I probably missed a step or misread some instruction.
Any idea where I made the mistake?

@esque: Sorry for the confusion... Your first attempt was right:
Code:
sudo mkdir /media/moronoxyd/data/local
sudo cp archos.ext4 /media/moronoxyd/data/local/
@all: Please perform an unmount before pressing "OK" on the device. If not, the image is broken!
Just to be sure, reboot the tab and mount the drive and perform a
Code:
md5sum <Mount_Path>/local/archos.ext4
and verify that value with the image on your host.
If there are the same values, we have to find another solution for the problem.
@stealthdave: Your logcat file looks very close to the problem above (file image broken).

Quallenauge said:
@stealthdave: Your logcat file looks very close to the problem above (file image broken).
Click to expand...
Click to collapse
Yes, that was the issue. umount for everyone!!!

Thanks.
Great job, like buying a new tablet.
The only thing I would add is to sudo sync before unmounting.

Quallenauge said:
@all: Please perform an unmount before pressing "OK" on the device. If not, the image is broken!
Click to expand...
Click to collapse
D'oh! I knew I made a rookie mistake.
Yes, that did the trick.
Thanks Again!

Hi,
Great job.
Is there a possibility to have the same ROM for the 101 version ?
Regards
Sent from my Galaxy Nexus using xda premium

Hi,
After two days of using this rom I must say it is very fast and smooth. But on idle after 6 hours I got -40% battery drain. Also I can feel heat from it. Got installed only 2 apps and one game. Is there any chance to implement deep sleep in this rom, to minimize batery drain?