Database Develop

trying to root cdma hero with 2.1 on a mac, help please.

i just got my refurb phone in the mail, and to my surprise it has the 2.1 update on it. D:
im having a real hard time rooting, could anybody help.
i haven't gotten any progress.

my mac interpretation of this is below thissssss
regaw_leinad said:
If you do not see the Superuser Permissions app in the app tray after running the exploit, on your phone, go to
Settings > About Phone > Software information
If it says 2.27.651.6 under "Build Number" (notice the bolded, underlined, italic 6), you need to run the RUU in the second post of this thread to revert to .5 first. Doing this WILL erase all of your data on your phone, so be sure to back up anything if you need to first.
It's been a long search for root, but it has finally been achieved!
The Hero 2.1 exploit is based on the EVO rooting method.
The EVO rooting could not have been possible without the combined efforts of:
Matt Mastracci
ozzeh
Joshua Wise
They are all AMAZING and should be thanked for all they have done.
Thank you to Amon_RA for the recovery.img (1.5.2) and Jus10o for packing up a boot.img for me last night when I needed it quick.
Over the past week, Matt and I worked hard applying this exploit to gain permanent root on the Hero.
I now have permanent root access on 2.1 down to a few simple steps that are detailed in this guide.
Also, I'd like to thank everyone that worked really hard on trying to find root here in the Hero community, and specifically all of those who contacted me and worked together with me trying to gain root:
abcdfv
imleon
thatguythatdid
navalynt
nfinitefx45
lifetrip718
rejectedkid
nebenezer (for being cool)
These guys worked incredibly hard with me and had extremely innovative ideas. They deserve a ton of credit for sticking with it as well trying to find . They were all in this for all the Hero users.
If I forgot your name, please let me know via pm so I can add you to the list.
As of right now, this guide is for windows only. Soon to come, OSX & Linux.
HOW TO ROOT SPRINT'S 2.27.651.5 RELEASE FOR THE CDMA HERO (Stock Android 2.1)
Make sure your phone is unplugged from your computer until I tell you to plug it in!
If you already have the Android SDK and HTC Sync set up on your computer, skip to Step 4 now
Step 1: Download the Android SDK here
Step 2: Extract the Android SDK zip. Move the contents of the extracted zip to C:\
Your Android tools folder path should now be C:\android-sdk-windows\tools
Step 3: Download HTC Sync 2.0.33 here
Run the installer, and reboot your computer when it is finished. Move on to step 4 once rebooted.
Step 4: Download the hero-root.zip. This zip contains everything you need to root your Hero.
(md5: c6e5058ed14f71c68fb099e10be142fb)
Step 5: Extract the 3 files inside hero-root.zip to the C:\android-sdk-windows\tools folder on your computer.
Step 6: Make sure USB Debugging is ON (checked) on your Hero. Go to Settings > Applications > Development > and make sure it is checked.
Step 7: Plug your phone into the computer via USB, Make sure that the connection type in the Notification Pull-Down Bar is "Charge Only", not "Disk Drive" or else this won't work.
If your computer asks you to restart after the new drivers were installed, do that now.
Step 8: Open a Command Prompt window by clicking the Start button and typing cmd into the search box and pressing enter.
It is also found under Start Menu > All Programs > Accessories > Command Prompt
Step 9: You will now enter the commands that I have put in code boxes followed by pressing ENTER, one code at a time.
You may also copy/paste these commands in to the Command Prompt, pressing ENTER after each, one at a time.
Comments will be outside of the code boxes (do NOT type these into the Command Prompt as they just are to help describe the root process)1:
Code:
cd C:\android-sdk-windows\tools
You should now see C:\android-sdk-windows\tools>
Now type2:
Code:
adb devices
If you've been following this guide you will see your phone's serial number. If you get "device not found" error, you either need to make sure you the drivers were properly installed or make sure you enable USB debugging on your phone. Continue on once you get the proper phone serial output.
You will now push the files needed to gain root to your sdcard in your phone with these following commands:3:
Code:
adb push unrevoked /sdcard
4:
Code:
adb push recovery.img /sdcard
5:
Code:
adb push boot-patched.zip /sdcard
Now we run the exploit. Be patient, this may take up to 40 seconds.6.
Code:
adb shell
7.
Code:
sh /sdcard/unrevoked
You should now see output that says this:
Code:
# sh /sdcard/unrevoked
sh /sdcard/unrevoked
Unpacking, please wait...
88 88 88b 88 88""Yb 888888 88 dP dP"Yb 88 dP 888888 8888b.
88 88 88Yb88 88__dP 88__ 88dP dP Yb 88odP 88__ 8I Yb
Y8 8P 88 Y88 88"Yb 88"" 8dP Yb dP 88"Yb 88"" 8I dY
`YbodP' 88 Y8 88 Yb 888888 YP YbodP 88 Yb 888888 8888Y
==================================================================
unrEVOked: root for HTC evo and hero (http://unrevoked.com)
$
-----------------
Now, on your phone, go to your app tray, and you will see that the Superuser Permissions app is in it.
Open the Superuser Permissions app. You will see a blank screen.
-----------------
In the Command Prompt on your computer, type:8.
Code:
su
A prompt will appear on your Hero asking you to give /system/bin/sh privileges. Click Allow.
Go back to your command prompt, and you should see
Code:
$ su
su
#
Now type:9.
Code:
flash_image recovery /sdcard/recovery.img
Flashing the recovery may take many seconds to complete. Wait until the # symbol returns to proceed.
You should now see
# flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
#
This means it was a successful flash.
Now type10.
Code:
reboot recovery
Your phone will now boot to the custom recovery image you just flashed.
If that doesn't work, (ie you get errors or it stays at the white/green HTC screen) try using this recovery image, put it on your sdcard, and try code #9 again.
In the Recovery Menu on your phone, choose the option:
Code:
Flash zip from sdcard
Then select
Code:
boot-patched.zip
and press the Home button to apply.
Once Recovery says "Install from sdcard complete", you need to make a nandroid backup!
In the main menu or the Recovery Screen, you will see an option that says
Code:
Backup/Restore
Choose that option, and then choose the option
Code:
Nand backup
This can take up to 5 minutes, so be patient while you see the
Code:
............
Once done, a nandroid backup of your phone will be created and saved to your sdcard in the folder directory:
Code:
/sdcard/nandroid/(your serial number)/
When it is complete, hit the back button to return to the Main menu, and hit "Reboot system now" from the menu to reboot normally!
DISABLE OTA UPDATES!!!!
To disable OTA updates that will patch this exploit, (after rooting and booted after creating a nandroid backup) run the following commands from Command Prompt.
Code:
cd C:\android-sdk-windows\tools
Code:
adb remount
Code:
adb shell
Code:
mv /system/etc/security/otacerts.zip /system/etc/security/otacerts.zip.bak
After doing this, the OTA updates WILL still download, BUT they will not pass signature checks to flash because of the code you just entered.
You now have full root access on 2.1!
{
"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"
}
Click to expand...
Click to collapse
step 2, where he moves the android sdk just move it to where ever you want,
step 3, don't worry about step 3,
step 4, do it as he says
step 5, move the files to the tools file in the android sdk folder you extracted to your preferred location,
step 6, do as he says
step 7, do as he says
step 8, go to your applications folder, open utilities, open terminal
BTW DO NOT TYPE THE QUOTES INTO THE TERMINAL
step 9, go to where you put the android sdk folder and right click on the tools folder and you should see the whole location for it, something like this /blah/blah/androidsdk/.......... so now in your terminal you are going to write "cd (now type the location from the tools folder path)and add /tools" to the end. what you are doing is moving your terminal into that tools folder where the root files are.
9-2, instead of adb devices it is "./adb devices"
9-3, instead of adb push unrevoked /sdcard it is "./adb push unrevoked /sdcard"
9-4, instead of what he has it is "./adb push recovery.img /sdcard"
9-5, instead of what he has it is "./adb push boot-patched.zip /sdcard"
9-6, type "./adb shell"
9-7, type what he has
9-8, type su
9-9, type what he has
9-10, type what he has
continue doing what he says,
if you want the disabling the ota part translated just ask me

eagles16 said:
my mac interpretation of this is below thissssss
step 2, where he moves the android sdk just move it to where ever you want,
step 3, don't worry about step 3,
step 4, do it as he says
step 5, move the files to the tools file in the android sdk folder you extracted to your preferred location,
step 6, do as he says
step 7, do as he says
step 8, go to your applications folder, open utilities, open terminal
BTW DO NOT TYPE THE QUOTES INTO THE TERMINAL
step 9, go to where you put the android sdk folder and right click on the tools folder and you should see the whole location for it, something like this /blah/blah/androidsdk/.......... so now in your terminal you are going to write "cd (now type the location from the tools folder path)and add /tools" to the end. what you are doing is moving your terminal into that tools folder where the root files are.
9-2, instead of adb devices it is "./adb devices"
9-3, instead of adb push unrevoked /sdcard it is "./adb push unrevoked /sdcard"
9-4, instead of what he has it is "./adb push recovery.img /sdcard"
9-5, instead of what he has it is "./adb push boot-patched.zip /sdcard"
9-6, type "./adb shell"
9-7, type what he has
9-8, type su
9-9, type what he has
9-10, type what he has
continue doing what he says,
if you want the disabling the ota part translated just ask me
Click to expand...
Click to collapse
i really appreciate your help, it workded. the ota translation would be lovely, if its really needed. idk if its needed after flashing a custom ROM, if so, your help would be nice.

glad to know it worked out for you , ill do the ota one right now
plug you phone in, set to charge only, make sure usb debugging is on,
step 1, open up terminal from the utilities folder again, and remember the step where we did " cd /blahh/blahh/androidsdk/tools", yeah well do it again fa sho.
step 2, type "./adb devices"
step 3, type "./adb remount"
step 4, type "./adb shell"
step 5, type "mv /system/etc/security/otacerts.zip /system/etc/security/otacerts.zip.bak"
and you should be good to go

eagles16 said:
my mac interpretation of this is below thissssss
step 2, where he moves the android sdk just move it to where ever you want,
step 3, don't worry about step 3,
step 4, do it as he says
step 5, move the files to the tools file in the android sdk folder you extracted to your preferred location,
step 6, do as he says
step 7, do as he says
step 8, go to your applications folder, open utilities, open terminal
BTW DO NOT TYPE THE QUOTES INTO THE TERMINAL
step 9, go to where you put the android sdk folder and right click on the tools folder and you should see the whole location for it, something like this /blah/blah/androidsdk/.......... so now in your terminal you are going to write "cd (now type the location from the tools folder path)and add /tools" to the end. what you are doing is moving your terminal into that tools folder where the root files are.
9-2, instead of adb devices it is "./adb devices"
9-3, instead of adb push unrevoked /sdcard it is "./adb push unrevoked /sdcard"
9-4, instead of what he has it is "./adb push recovery.img /sdcard"
9-5, instead of what he has it is "./adb push boot-patched.zip /sdcard"
9-6, type "./adb shell"
9-7, type what he has
9-8, type su
9-9, type what he has
9-10, type what he has
continue doing what he says,
if you want the disabling the ota part translated just ask me
Click to expand...
Click to collapse
im stuck on step 9... can you make video or something

hotboyray said:
im stuck on step 9... can you make video or something
Click to expand...
Click to collapse
I'm not a mac user so this might be wrong but if you have the latest updated version of the sdk files they for some reason took out the adb file. So google search for the adb files, download them into the android sdk tools file and then try step 9 again. This should work.

One click root APK in the themes forum if you can't get it. It's worked everytime for me. Super fast

This doesn't work for me
Sent from my HERO200 using XDA App

Clockwork from Ubuntu

Install Andrioid sdk
(I renamed the Android folder sdk to simplify things)
Install ADB
(see Karolis post... thanks)
Now I have make some corrections to the standard install and this has worked flawlessly for me.
1. Unzip "Root.zip". Place "ota.zip" & "update.zip" into Android SDK.
(You wont need loop)
2. I started with the 2gig sd provided, formatted it in windows and copied attn1's ROM to it (leave it zipped).
3. Then I downloaded Clockwork_Aria_MT3GS.zip and placed that and a copy of the above ROM in the android sdk/tools folder.
4. Open terminal in Ubuntu and type cd /sdk/tools and hit enter
5. Heres where the differences start. Plug the phone in to you pc powered on WITHOUT the sd card in it. When the phone asks select charge only.
6. In the terminal type sudo ./adb devices and hit enter
(your device should show up)
7. In terminal type sudo ./adb reboot bootloader and hit enter
8. Now the phone should have rebooted showing the white screen. Select BOOTLOADER and hit the power button on the phone. Wait for the text to change to "HBOOT USB Plug. This is the tricky part use volume down on the phone to select "Recovery" but DONT hit the power button until you are ready to push the sd card in after you hit the power button.
9. You should come to the red triangle screen now. In terminal type sudo ./adb devices again and your devise should show up. If not eject the sd card switch to the terminal and type sudo ./adb reboot bootloader again.
10. If your device showed up Hit Volume up and the power button on your phone.
11. Now use volume down to select Apply sdcard:update.zip and push the power button to execute. Let that run trough, finish and go back to the screen you started at.
12. In terminal type adb push ota.zip /sdcard/update.zip and hit enter.
13. in terminal type adb push update.zip /sdcard/update.zip but do NOT press enter yet.In recovery, again scroll down with power down to select sdcard:update.zip but do not execute yet.Press the power button and then watch phone to say "verifying" and then press enter IMMEDIATELY on the keyboard. If timed right, Clockwork recovery should load. If not, start back at step push ota.zip /sdcard/update.zip and repeat from there until clockwork loads.
14. From Clockwork Recovery, do a Nandroid backup. From Clockwork Recovery, select install zip from sdcard, and execute, then choose zip from sdcard and execute, and then you can scroll down to your pre-rooted rom of choice and execute that to flash it. In Clockwork you can scroll with trackpad or volume buttons, and you can execute with either the power button or a trackpad button push.
Thanks to attn1. I stole alot of what you typed, your ROM and for getting this working in the first place.

Let me know if I screwed anything up. Its been a long day : )

I think that your method works well, but I find that of attn and eugene is easier to manage, since plugin a usb cable is easier than popin a sd card.
Anyway, great summary. But you don't really need step 1 if you are using attn's ROMs.
sd73ta said:
Let me know if I screwed anything up. Its been a long day : )
Click to expand...
Click to collapse

I'll edit the first part out when I get home. This worked for me because I couldn't get it to find my device the other way and this way found the device first try each time i did it. Thanks for the input

plutino99 said:
I think that your method works well, but I find that of attn and eugene is easier to manage, since plugin a usb cable is easier than popin a sd card.
Anyway, great summary. But you don't really need step 1 if you are using attn's ROMs.
Click to expand...
Click to collapse
if you dont mind Im still kinda new to this which step should I take out?

After hours of failing to get things to work on my Win7 machine, this saved the day. Thanks!

I was unable to success with the SD card method, so I cannot really comment on which steps are unnecessary. But now the almighty unrevoked has automated the whole process and we don't need to chase the bear any longer.
sd73ta said:
if you dont mind Im still kinda new to this which step should I take out?
Click to expand...
Click to collapse

[TUT][OUTDATED] How to Root your G9, Enable SDE, and Optimize

{
"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"
}
NEW GUIDE SEE HERE: http://forum.xda-developers.com/showthread.php?t=1653566
Hi everyone! The following guide I put together is a simple, easy to follow guide, for all G9 users. If you own an ARCHOS G8, this guide will not work for you. This guide will help you easily root your tablet. If you have found anything helpful, please click "thanks" on my post, and visit the original threads of our amazing developers and leave thanks there too! Before you go on, please BACKUP ALL IMPORTANT FILES YOU DO NOT WANT TO LOSE TO A SAFE LOCATION.
If you have rooted other android devices before..rooting your Archos G9 may be a little difference. Instead of rooting stock firmware, we first temp root, then enable SDE (special developer edition) menu. Once SDE menu is enabled, it adds an option in recovery to install developer firmware. This is when we install a modified firmware that has busybox and super user included. We do this because the exploit in the temp root causes some issues that doesn't make sense to keep in the long term. Hence the name "temp" root. This guide is very safe to follow. Chances are most problems you run into are very easy to recovery. Please view the FAQ at the bottom of this post if you have questions or run into problems. Because we don't have to flash recoveries or mess with the bootloader like some Android devices require, and because all methods are universal to G9s, this rooting process is very safe and easy to follow.
Please if you have any issues following this guide, reply with the stock firmware you have (be it honeycomb, ICS, firmware 4.0.6 etc) and the G9 model (flash or HDD 250gb). Board version and processor (OMAP 4430 and 4460 should not be a problem with anything, so probably don't include this when you ask your problem.)
STEP 1: Pre-root/Temp-root
1. Install the ADB drivers, using Quinny's 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 root_hack and extract. Note: Don't open these links in a browser, not tapatalk or the xda app
Download them to your desktop (or wherever your ADB installation is if you cannot access ADB from your desktop)
6. Double click rootdevice.cmd to open, press any key after reading the prompt.
(Note: Device will reboot a couple times)
7. Restart your tablet (important do not skip this step)
THANKS TO PAUL FROM MoDaCo for this root
THANKS TO QUINNY and LETAMA for the original guide
STEP 2: Enable SDE
1. Make sure you have done the temp root method. Please turn off your tablet. Your tablet should now be off.
2. Download this zip and extract to your desktop
3. Turn on your tablet. Once your tablet is on, plug it into your computer via usb cable.
4. double click enable_sde.bat
5. Once that is finished, type the following: (press enter after each line)
Code:
adb shell
rm /data/local.prop
6. (If the above code doesn't work or doesn't do anything, it is okay, move on with the rest of the guide). SDE should now be enabled, make sure buy turning off your device, then once it's off:
7. Hold power + volume down until the archos logo appears and a recovery menu appears
8. Use Volume Up + Down and power to select Recovery Menu > Developer Edition menu
9. If you can get to Developer Edition menu, you have correctly enabled SDE.
STEP 3: (optional, but recommended from honeycomb). Format your device, and then install/re-install ICS. No worries: You will not lose SDE menu doing this.
It is recommended to do a full device format when upgrading to ICS. If your device is acting up or feels "laggy" after updating to ICS, this usually helps. Before you begin, please note: You will lose all apps, media files, pictures, etc. Please backup any important files. Consider Titanium Backup (root users only to backup any apps with personal data you want to keep (game scores, etc).
AGAIN: YOU WILL LOSE *ANYTHING* NOT BACKED UP!
Note: You WILL need a PC connected to the internet, and the USB cable that came with your device. Before you being, please download Archos 80/101 G9 OS v 4.0.6 (190668Kb, for 80/101 G9 devices only) to your PC, copy to your desktop or wherever you will remember, then do the following:
Step 1: Power off your device
Step 2: Boot into recovery by holding the volume rocker down and pressing the power button simultaneously
Step 3: Once in recovery, select "Format System", then "Reformat Device..." (use the volume up/down to change selection, power button to select)
Step 4: Once formatted, return to recovery using the same method above, this time select "Update Firmware"
Step 5: Plug your device into your computer using the USB cable that came with your device
Step 6: A new drive should appear in "My Computer", copy firmware_archos_it4.aos to this device
Step 7: Ensure the transfer is completed, then press the power button on your device, keep it plugged in while it is updating
Step 8: Your device should boot, and be updated to the latest firmware 4.0.6
STEP 4: Install rooted firmware. YES! This will work after installing the official ICS OTA update or official AOS.
Before you begin, you will need SDE enabled. Please follow steps 1 & 2 in my first post. If you have SDE enabled, you can continue. Any downloaded applications and personal media should remain untouched. You have some options for which ROM you want. Please download files to your PC hard drive.
For stock ROM w/ root (busybox and superuser), download and extract the following:
4_0_6_update.zip
kernel_update.zip
For custom ROM [email protected]_V02, download and extract the following:
https://hotfile.com/dl/154778665/e6b99ad/ics_blue_update.zip.html
http://www.2shared.com/file/triOUMDR/ics_blue_kernel.html
BE SURE to extract, Archos recovery does not recognize zip files
Step 1: Power your device on
Step 2: Once your device is on, and your home screen is visible, plug your device into your PC
Step 3: Open a command prompt on your PC and type
Code:
adb devices
Step 4: Ensure your device shows up so you know it's connected properly and adb is active
Step 5: Type
Code:
cd desktop
This is to change the directory to where you download the two files
Step 6: If you have flash NAND model (8gb or 16gb): Type
Code:
adb push archos.ext4.update /data/media
If you have HDD model (250gb): Type
Code:
adb push archos.ext4.update /mnt/storage
Give it some time to transfer, it is a large file and will take several minutes, you will be presented with transfer info once the transfer is complete
Step 7: Power off your device
Step 8: Boot into recovery by holding the volume rocker down and pressing the power button simultaneously
Step 9: You should now be in Recovery mode with the following options "No" "Reboot" "Update Firmware" "Repair System" "Format System" "Developer Edition Menu". Select "Developer Edition Menu"
Step 10: Select "Remove Android Kernel" (if the option is present, if not, skip)
Step 11: Select Flash Kernel and Initramfs
Step 12: Copy zImage and initramfs.cpio.lzo to the drive that appears
Step 13: Reboot your device. Your device should now be rooted.
Frequently Asked Questions! (FAQ)
Will this guide work for my Archos 80 G9? For my 101 G9? I have Archos 101 G9 OMAP 4430. I have 250GB hdd model! I have turbo edition!
Yes this guide will work for ALL Archos G9 users. This includes 80 G9s and 101 G9s. This includes all 8gb G9s and 16gb G9s and 250GB G9s and 1.0 GHz G9s and 1.2 GHz G9s and 1.5 GHz G9s and OMAP 4430 G9s and OMAP 4460 G9s and board version V5 etc etc. ALL G9s!
Can I just drag the .zip file to the RAMDISK that appears when I flash zImage and initramfs?
No! Archos recovery cannot read ZIP files. You must first EXTRACT, then copy the contents of the extracted folder. NOT the folder itself. This means you will have two files on the RAMDISK, and no additional folders. If you don't know what a RAMDISK is, try Google or Wikipedia. If you get stuck in a boot loop because you forgot to extract archos.update.ext4 or drive.zip, you must follow the instructions below.
Help! I am stuck in a bootloop! Archos splash screen appears and keeps rebooting. I messed up when I was rooting, and now android will not boot! I accidentally formatted my device, and now I cannot boot into android.
This is a simple mistake and in 99% of cases it is easy to fix. Follow these steps:
Step 1: Download official Archos G9 firmware for ALL G9 tablets (aos file) HERE
Step 2: Boot into recovery turning your device off and then holding volume down + power at the same time
Step 3: Choose "Update Firmware"
Step 4: Connect USB cable to computer and tablet
Step 5: A removable device should appear (RAMDISK), copy the file you just download straight to that drive
Step 6: Press the power button once the file is done copying. DO NOT UNPLUG your device until it has finished updating and has booted back into android.
If you did not format your tablet or delete any personal media, your files should be uneffected.
Will I lose SDE menu if I update my tablet with official AOS or OTA update
As of the latest update (4.0.6) no official update from Archos has removed SDE menu. You should be fine, and your SDE menu should remain untouched.

Useful tips
Overclock
How to overclock your device. For SDE only.
First please download and extract https://hotfile.com/dl/152251241/ef27ecd/fast_ics_oc.zip.html
Then follow the instructions in my second post to push to your device then copy zImage and initramfs.
After you have successfully booted download SetCPU or No-Frills CPU Control and overclock to your desire. Thanks to surdu for making this happen! Visit his original thread HERE to view all warnings.
Howto take a screenshot
ICS has a built-in screenshot feature. No need to download any app!
Step 1: On the screen you wish to capture, press and hold the power button and volume down button simultaneously for a few seconds until the screen flashes and you hear a shutter. Be sure to press them at the same time
Step 2: You can find the saved screenshots in storage > Pictures > Screenshots
Step 3: Alternately, you can simply find them in the folder labeled "Screenshots" in the gallery.
Touchscreen issues
If you have touch related issues/errors, try the following:
Step 1: Turn your device off
Step 2: Carefully wipe down the screen with a dry or lightly damp rag. If you use a lightly damp rag, be sure to dry it with a dry one quickly.
Step 3: Power on your device
Step 4: Go to Settings > Repair & formatting > Touch screen calibration > *Put your device down on a flat, hard surface like a table, tap Calibrate the Touch Screen ONCE, then DO NOT TOUCH.
Step 5: Once finished, you can return to your launcher or wherever you wish
Multiple Users
More than one person uses your Archos?
Either designate home screens using a contact widget, or use a note widget in launchers like GO Launcher. There are also apps that support multiple profiles for root users like SwitchMe Root Profile Manager, however I can not guarantee this will work.
Multi-boot!
See this: http://forum.xda-developers.com/showthread.php?t=1578438
Removeable System apps
System apps you can safely disable (new ICS feature) or delete via Titanium Backup or other root app: (only remove the ones you don't use)
Archos Connect
Archos Remote Control
Media Center
Media Server
Movie Studio
Online Registration
Photo Frame
Talk Back
User Manual
If you have any tips I should add, or if any part of this guide is inaccurate or outdated, please let me know!
BIG THANKS:
Android Development Team for giving us awesome Honeycomb and Ice Cream Sandwich OS!
Archos for their hardware and awesome customer support!
serdu_petru for full root and all his hard work putting together these rooted firmwares so quickly!
letama for his original work on this device and work with kernels for overclock!
gen_scheisskopf for his work on allowing root access for HDD models!
Quinny899 for putting together his easy root guide for noobs like me!
Any other wonderful people involved in the development and advancement of this wonderful device!
GUIDE TBC

Didn't you mean "reformat device"? because by reformatting Android, you don't lose data in /mnt/storage...

Hi!
Thank you very much for your good and complete tutorial !
Have a nice week !

blogmaw said:
Didn't you mean "reformat device"? because by reformatting Android, you don't lose data in /mnt/storage...
Click to expand...
Click to collapse
yes that's what I meant. Thanks, got those two mixed up simple mistake
surdu_petru said:
Hi!
Thank you very much for your good and complete tutorial !
Have a nice week !
Click to expand...
Click to collapse
thanks man! have a great week too

Hi !
Thank you....but into BIG THANK !.....do not forget to mention the @gen_scheisskopf for your useful help ....without him work ...now HDD models wouldn't work !

surdu_petru said:
Hi !
Thank you....but into BIG THANK !.....do not forget to mention the @gen_scheisskopf for your useful help ....without him work ...now HDD models wouldn't work !
Click to expand...
Click to collapse
I have added him thank you for reminding me!

Concerning multiple users, I would suggest you Switch Me, it allows users to have their own sessions on the tablet.
As for the uncompatible apps, it's mostly games that haven't been certified as compatible but they actually run flawlessly! (9mm, Asphalt 6 HD...). I tried to modify build.prop and init.Archos.80S (in my case) but it didn't work on ICS (see topic http://forum.xda-developers.com/showthread.php?t=1528899)
Sent from my Archos 80G9 using XDA Premium HD app

blogmaw said:
Concerning multiple users, I would suggest you Switch Me, it allows users to have their own sessions on the tablet.
As for the uncompatible apps, it's mostly games that haven't been certified as compatible but they actually run flawlessly! (9mm, Asphalt 6 HD...). I tried to modify build.prop and init.Archos.80S (in my case) but it didn't work on ICS (see topic http://forum.xda-developers.com/showthread.php?t=1528899)
Sent from my Archos 80G9 using XDA Premium HD app
Click to expand...
Click to collapse
Is this what you're talking about?

first,thanks for your work with the tutorial
i have a few questions:
it is possible to root with ICS already installed?
by enabling SDE and installing the rooted fimware is the only steps necessary?
if not, is possible to downgrade to honeycomb to gain root?
i have a little of experience with rooting android devices(huawei u8230,still alive and kicking an a nexus s of a friend) and i remember that in some cases with a diferent version of android i had to gain root again.
thanks in advance and sory for the questions

sleepingman said:
first,thanks for your work with the tutorial
i have a few questions:
it is possible to root with ICS already installed?
by enabling SDE and installing the rooted fimware is the only steps necessary?
if not, is possible to downgrade to honeycomb to gain root?
i have a little of experience with rooting android devices(huawei u8230,still alive and kicking an a nexus s of a friend) and i remember that in some cases with a diferent version of android i had to gain root again.
thanks in advance and sory for the questions
Click to expand...
Click to collapse
hi! this firmware is "pre-rooted", meaning you just have enable sde and install the firmware seen in the big STEP 2
Do that, and your device will be rooted. I don't think you can downgrade, however ICS is far superior, surdu already released the rooted firmware
hope that answers your question

thanks for your advice.
the only reason to downgrade is to enable root but if the only needed step is to enable SDE and install this rom, much easier
today or tomorrow im going to do that and after i will post the results
cumps

sleepingman said:
thanks for your advice.
the only reason to downgrade is to enable root but if the only needed step is to enable SDE and install this rom, much easier
today or tomorrow im going to do that and after i will post the results
cumps
Click to expand...
Click to collapse
good luck!

alternate location for phase 1 phase 2 files
Hi Shano56,
Thanks for the thread. It is just what I am looking for. I have upgraded to ICS and want to root it.
One question though, is there an alternate location to down load files "1" and "2" when attempting to temp root?
It seems everytime I go to download Step1 and Step2 in temp rooting I get an error message "all free slots on server are taken try again later" ......

colinevers said:
Hi Shano56,
Thanks for the thread. It is just what I am looking for. I have upgraded to ICS and want to root it.
One question though, is there an alternate location to down load files "1" and "2" when attempting to temp root?
It seems everytime I go to download Step1 and Step2 in temp rooting I get an error message "all free slots on server are taken try again later" ......
Click to expand...
Click to collapse
Hi!
You can download now => https://hotfile.com/dl/149500142/93e089a/Pre_RootEnable_SDE.zip.html
( pre-root with 1 & 2 and enable_sde ). Good Luck !

Hi,
The first post says work in progress. Is this work in progress or is it working without any problems?
Thanks in advance.
Dan

Hi again,
So I couldn't resist. Followed the instructions and all went fine. Looks like I have root access (E.g. can install apps which require root access).
One problem and one question.
Problem: Please ignore if people do not want to talk about this app but adfree doesn't work. says it can't see partition.
Question: Will I always have root access or do I need to go into boot options screen every time that I turn on the device and choose developer edition?
Thanks,
Dan

e9508686 said:
Hi again,
So I couldn't resist. Followed the instructions and all went fine. Looks like I have root access (E.g. can install apps which require root access).
One problem and one question.
Problem: Please ignore if people do not want to talk about this app but adfree doesn't work. says it can't see partition.
Question: Will I always have root access or do I need to go into boot options screen every time that I turn on the device and choose developer edition?
Thanks,
Dan
Click to expand...
Click to collapse
You will have always root accesse if you Remove Android Kernel into SDE recovery ....! Good luck !

e9508686 said:
Hi,
The first post says work in progress. Is this work in progress or is it working without any problems?
Thanks in advance.
Dan
Click to expand...
Click to collapse
hi! i just put WIP up there cause I'm still adding stuff to the guide.. however everything posted is okay to use. it is safe

NEED HELP PLEASE!
1)Okay I tried prerooting using surdu_petru file from previous post
(everything looked fine except touch screen response that a six second delay after prerooting)
2) then ran surdu_petru sde_enable.bat file.
(everyting looked okay, but still had six second screen response delay)
I tried rebooting into recovery holding power and volume down simultaneously, wanted to try sde boot. UNfortunately now I am screwed.
I can only boot in recovery console and there is no OS to boot from.
How do I get back to the semblence of a working system (forget ROOTING) from the recovery console ?
PLEASE HELP
---------- Post added at 06:23 AM ---------- Previous post was at 05:59 AM ----------
okay panic mode has resided......
followed STEP 1 at the first entry of this thread and am back to square one!
Will attempt to root ICS again after a good night sleep!
Can't tell you how much I appreciate this forum.....

[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] 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