[Gen8 Android Development] BGMArchos:
Instructions I use to root my A70 IT 8 GB

Hello,

I've been using z4root on my A70 IT 8 GB, since I discovered the ping command requires root access on the Archos Gen 8 line. In the meantime, I found additional reasons to use root mode, such as:

1) MyBackupPro supports root mode for full application and data backup.

2) Swap to increase the memory on these 256 MB devices. While swapping to a SD Card isn't a good idea, I'm looking to do it on the 250 MB version.

3) 1 Ghz fix, which once I can go to the 2.0.71 firmware won't be necessary.

4) Run applications that use the ping command.

I'm using these instructions for running z4root on my system. They assume you already have z4root installed on your system. As for validating rooting was successful, there are a couple of ways on the Archos Gen 8 devices:

1) Run setCPU

2) Run the Terminal Emulator and try to use the su command. If it exists you're golden, if not then it failed.

Steps I use:

1) Let the boot process complete, but don't start additional commands.

2) Make sure USB Debugging is on and (if you want) see if there is at least 100 MB of storage left.

3) Start z4root

4) Select temp root

5) Confirm the notice about USB debugging. If it doesn't appear, something isn't right.

6) z4root will take you to the settings. At this point select development from the opened settings, disable and then enable USB debugging. Confirm the message about USB debugging.

7) Return to the home page.

8) Go back into settings -> Applications -> Manage Applications -> All Applications (tab). Go to the bottom of the list, find z4root and select it. Once there you need to:

8A) Do a Clear Data. This is important.

8B) If z4root is running do a Force Close.

8C) Return to the home screen.

9) Start z4root again.

10) Select temp root and in 5 seconds or so you should see a White flash and the text on the screen should change to say the application is finishing up.

Allow it to finish. See notes below should these steps fail to produce temporary root.

z4root will tell you it was successful whether it was or not. I don't know why. At least on the Gen 8 line checking is as simple as seeing if the "su" command exists on the system. If it does, you're golden and if not then something failed and you can't access root.

To validate success, I'll use one of the following methods:

TERMINAL EMULATOR: Start the Terminal Emulator application and issue the "su" command. If this fails, you don't have root. (Note: If this is the first time running terminal emulator in root, you'll get a message asking to give your permission for terminal emulator to have root access. If the message fails to appear, you don't have root. Again this is the first time only.)

setCPU: Start setCPU and if it is the first time ever using the command, run the Device Selection choosing "Autodect Speed Recommended." If you get a screen asking permission to add setCPU to the list of application, you're golden. If you don't get the prompt or setCPU says it failed to get root, you don't have root.

Subsequent times you use setCPU and adjust the maximum speed, you'll see a message flash on the screen about setCPU gaining superuser permission. This message is from the Superuser application. NOTE: You may see the message even before you adjust anything on subsequent uses of setCPU during the same session.

TROUBLE SHOOTING z4root:

Should z4root fail, you should try it a second time after doing a Clear Data and Force Close. If this fails, do a reboot and try again.

Should it fail all the above retries, I go back to square one. I'll uninstall it, download it again from XDA-Developers, and install it with reboots between each step. I have yet to have this last method ever fail on me.

Typically, though, I don't need to go beyond a second try with a reboot.

Should it again fail, my best success has been to uninstall z4root, reboot, reinstall, reboot, and then follow the instructions.

Good luck and hopefully your mileage will be as good as mine.

If you hear of a version working with firmware 2.0.71, please, let me know.