Develop Bugs

[GUIDE] How to mod/root a virgin hero

I'M NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE
Infos
Why Should I root my phone?
Read Here
What can I do with recovery?
With recovery you can principally flash cooked roms, but also other things like make nandroid backups (Internal memory backups), partition your sdcard, fix problems etc...
If you want root there are 2 methods:
First Method
Is very simple, just download and install InstantRoot.apk (attached)
To install this from sdcard you need a file explorer like ASTRO
After the install a notify that says root access gained should appear, if not try second method
Second Method
This will install also recovery
1. Enable Debug USB from Settings->Applications
2. Download flashrec and install it with file manager like ASTRO
3. Download Amon_RA's recovery and put it in your sdcard
4. Run flashrec and tap Backup Recovery
5. Tap in the textbox and write this path:
Code:
/sdcard/recovery-RA-hero-vx.x.x.img
At moment of writing last version is 1.5.2, so the path should be
Code:
/sdcard/recovery-RA-hero-v1.5.2.img
6. Tap Download then flash recoery
7. If you get an error retry from step 3, else continue
8. Turn off your phone and reboot it keeping pressed Home button, recovery should start
9. Connect your phone via usb
10. Download Android SDK and extract all in the same folder
11. Download this and extract it in your sdk/tools folder
12. Open cmd (if you are on windows, if you are on a mac or on linux open terminal) and move to sdk/tools folder using this command
Code:
cd path
13. Give this commands in order
On windows:
Code:
adb shell mount /system
adb push su /system/bin/
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app/
adb shell umount /system
adb shell reboot
On linux/mac
Code:
./adb shell mount /system
./adb push su /system/bin/
./adb shell chmod 4755 /system/bin/su
./adb push Superuser.apk /system/app/
./adb shell umount /system
./adb shell reboot
14. Now you have root access on your phone
If you want recovery:
Just follow root's second method to the step 7
Flashing Custom roms using recovery:
Custom roms are in Zip format, to flash it is really easy once you have recovery.
Once downloaded a rom put it in your sdcard root, then reboot into recovery (Keep home button pressed while turning on your phone)
Now make a wipe going to Wipe->Wipe data, then come back to main menu and go to Flash zip from sd card, select your zip and you're done

Thanks for the guide How does Nandroid backup fit into this?

maybe you need to tell how to downgrade(or a link to a guide )
nice guide, only i have already rooted my phone(2 months ago or something xD)
@Culturelol
nandroid backup is recommeded when you install a new rom, so you can always back to your original/past rom

So i root with this guide, then nandroid and then i can flash the new rom?

One more small question Is there anything special i should know about flashing the radio?

culturelol said:
So i root with this guide, then nandroid and then i can flash the new rom?
Click to expand...
Click to collapse
Yep
culturelol said:
One more small question Is there anything special i should know about flashing the radio?
Click to expand...
Click to collapse
No, only that you can't flash a GSM radio on a CDMA phone and back, if you do this you'll brick your phone

Exit93 said:
Yep
No, only that you can't flash a GSM radio on a CDMA phone and back, if you do this you'll brick your phone
Click to expand...
Click to collapse
Is that done the same way? Boot to recovery and then flash the radio? And is this done before or after wipe / install of the new rom?

culturelol said:
Is that done the same way? Boot to recovery and then flash the radio? And is this done before or after wipe / install of the new rom?
Click to expand...
Click to collapse
You can install radio whenever you want, it's flashed in another nand partition

nice rom - but the Home button doesnt work - is that normal?

krueck83 said:
nice rom - but the Home button doesnt work - is that normal?
Click to expand...
Click to collapse
Wrong discussion...
If you refer to CKDroid you need to flash googlebits to get home button working...

Exit93 said:
You can install radio whenever you want, it's flashed in another nand partition
Click to expand...
Click to collapse
But it is flashed through the recovery screen?

culturelol said:
But it is flashed through the recovery screen?
Click to expand...
Click to collapse
Yes, it is

Thank you - it works.

Thanks for the instructions.
1-Do you need to follow step 8-12 to get root and flash rom`s or is the android sdk and superuser only if you want to develope yourself?
2- If ypu do this and after want back to stock rom . As far as i`ve read it`s as easy as just flashing from HTC website and you`re back ? Won`t recovery still be left on your phone?
Thanks

Rui-Cruz said:
Thanks for the instructions.
1-Do you need to follow step 8-12 to get root and flash rom`s or is the android sdk and superuser only if you want to develope yourself?
2- If ypu do this and after want back to stock rom . As far as i`ve read it`s as easy as just flashing from HTC website and you`re back ? Won`t recovery still be left on your phone?
Thanks
Click to expand...
Click to collapse
1. Steps from 8 to 12 are only to get root access on stock rom, if you want to change rom you don't need to make those steps
2. To get back to stock rom just flash official update, as far as i know recovery will be deleted

Thanks
Thanks for the guide.
Was being anal and following the guide to the letter (not wanting a brick!) and it just rebooted to stock recovery
Code:
4. Run flashrec and tap Backup Recovery
5. Tap in the textbox and write this path: /sdcard/recovery-RA-hero-v1.5.2.img
6. If you get an error retry from step 3, else continue
Should we be tapping the download button once we entered the img location?
Ne0

alfie196 said:
Thanks for the guide.
Was being anal and following the guide to the letter (not wanting a brick!) and it just rebooted to stock recovery
Code:
4. Run flashrec and tap Backup Recovery
5. Tap in the textbox and write this path: /sdcard/recovery-RA-hero-v1.5.2.img
6. If you get an error retry from step 3, else continue
Should we be tapping the download button once we entered the img location?
Ne0
Click to expand...
Click to collapse
Yes, sorry it's my fault, correcting...

Sorry silly question
Please could someone tell me, if using the first method the InstantRoot.apk. Will this wipe the current ROM/data/apps etc from the phone or will it just enable Root privilages and leave everything else the same?
Many thanks
Jeremy

It just roots your phone and leaves everything in tact, just did it now.
The guide is not clear on how to flash the rom though. Because it says "If you want recovery" I don't want recovery I just want to flash. I have root now what's next? In simple steps, no recovery required just want CKDroid.

hatski said:
It just roots your phone and leaves everything in tact, just did it now.
The guide is not clear on how to flash the rom though. Because it says "If you want recovery" I don't want recovery I just want to flash. I have root now what's next? In simple steps, no recovery required just want CKDroid.
Click to expand...
Click to collapse
You need recovery to flash roms, it's written on the start of the first post

Getting Started [Update 12/23 - OTA Update Install fix for root]

[Update 12/23] For those of you unable to install the new system update, I've found a solution -- scroll down to the update! I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY OCCUR!
So I figured I'd at least get things started - Credit goes to whomever first tried z4root on their Droid Pro - and to mahst687 for the deodexing.
Lets Begin!
Resources:
Motorola ADB Driver
Android SDK
xUltimate V2.2.2
(Can't post links apparently, sorry -- googles your friend!)
#1 Root:
As seen on numerous android sites already, root is obtainable via z4root in the market. It may not work the first, second, or even third time -- just keep trying, it works I promise.
#2 Bootstrap and Clockwork Recovery
Download and install 'Rom Manager' from the Market. Once installed flash the Droid2 Clockwork Recovery. After flashing, obtain the Droid2 Bootstrapper and install it. Confirm Clockwork Recovery works by booting to recovery via Bootstrap.
#2 Deodex:
Download Android SDK for ADB, as well as the Motorola ADB Drivers posted above. Second, download xUltimate - also posted above. Once everything is downloaded and installed we're ready to begin.
1. Run Main in the xUltimate package - if the ADB drivers installed successfully you should be greeted with a menu containing several options - great!
2. Next run option 1.
3. Run option 2.
3. Run option 3 - sit back and relax for a bit
4. Once option 3 is done doing its thing, navigate to the xUltimate folder, more specifically the "origi_frame", and delete guava.odex
5. Run option 4 - it'll be a short wait
6. Exit the xUltimate
7. Enable USB Mass Storage on the phone and transfer both "done_app", and "done_frame" to the ROOT of the SD card.
8. Once both folders have transferred disable USB Storage, but keep the phone plugged in via USB.
9. Open up a command prompt and browse to the android SDK Tools folder (or where ever your ADB executable is located).
10. Enter the following commands:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
11. If all went well your phone should reboot - which may take a few minutes. Enjoy!
[Update]12/23/2010
For those of you unable to get the new Droid Pro OTA working I have found a solution! You will need:
1)Root
2)Clockwork Recovery
3)System.img from update
4)Current Nandroid backup of your phone
5)ADB drivers and ASDK
So lets begin.
1)Boot into Clockwork recovery and create a backup of your phone.
2)Once complete, mount the phone as USB storage and pull the system.img file from the nandroid backup folder, as well as the nandroid.md5 (KEEP THESE FILES SAFE!!!!!)
3)Obtain the system.img file from here (Compliments of whoopsiedaisy).
4)Replace the system.img file in the Nandroid backup folder on your PHONE.
5)ADB into your phone (preferably still in recovery) and do the following:
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2010-xx-xx.xx.xx.xx
# rm nandroid.md5
# md5sum *img > nandroid.md5
6)If all goes will it should create a new MD5 checksum file utilizing the new system.img
7)Go to the 'backup and restore' menu in Clockwork, and select 'Advanced Restore'
8)Select the correct nandroid backup folder where the new system.img file is located, and then select 'Restore System'
9)Assuming all goes well, go to Settings, About and check your new system version!

Nice, can't wait to try this on my wifes phone after work.
Sent from my ADR6300 using XDA App

Is the second step necessary if you just want root access so you can install Wireless tether, etc?

jayhammy said:
Is the second step necessary if you just want root access so you can install Wireless tether, etc?
Click to expand...
Click to collapse
Not at all. Simply run z4 if all you require is root access (and a host of apps like Wireless Tether, DroCap, Titanium Backup ...)

Can you please post the quickoffice apk from the Dpro so I can put on an DX? Same would go for the software that allows me to Invite attendees to meetings using GAL. It be copasetic if you can.

Thanks a ton! Freaking worked flawlessly on my Droid X.
Nate

Cool. Cant wait to try this on my wife's phone.

I downloaded everything you said and i started my deodex but when i select option 3 in main it tells me "error no odex file" have i done something wrong please advise

Is it really that simple?
I feel like I must be missing something. I just download an app from the market and reboot and I'm rooted?
Also, what is the deodex for? I want to root my phone to install the apps I want and I want wifi tether. Do I need it?
Also, I really want to understand what is going on under the hood, but I don't know where to start. Is there a 'for dummies' tutorial somewhere that I can go to to start understanding what all of this stuff is, so I can make informed decisions for myself about what I want instead of begging for help on internet forums? Thanks in advance for any suggestions.

Is there a way to unroot? I am not rooted but just curious.

rllong1 said:
Is there a way to unroot? I am not rooted but just curious.
Click to expand...
Click to collapse
Yes, Z4Root app allows you to root, re-root, and UNroot.

I see no uproot button on the screen. Only a root button
Sent from my DROID PRO using XDA App

I had version 1.1 of z4. I now have the. 3 version and it has the unroot button
Sent from my DROID PRO using XDA App

rllong1 said:
I see no uproot button on the screen. Only a root button
Sent from my DROID PRO using XDA App
Click to expand...
Click to collapse
You'll only see the unroot button once you've rooted. Otherwise, it will first show only the "root" option.

jayhammy said:
You'll only see the unroot button once you've rooted. Otherwise, it will first show only the "root" option.
Click to expand...
Click to collapse
I was rooted. I had titanium installed and superuser. Z4 ran fine but I had an old version of it. I dont know if that matters but thats all I did. I downloaded the 1.3 version and I now have the unroot button. On the old version there was no option for temp root either. Just root. On the version I have now there is a temp root and perm root button.

Would just like to let people know that your method for "updating" via nandroid backup would not work for me. Followed all the instructions to the letter and during the advanced restore I continually received md5sum mismatch errors.
So I took the chance and updated through the OTA update, it installed fine but lost root. Ran z4root (twice) and gained root access again .
Looking forward to some real custom daily driver roms for this guy.

darkninja157 said:
Would just like to let people know that your method for "updating" via nandroid backup would not work for me. Followed all the instructions to the letter and during the advanced restore I continually received md5sum mismatch errors.
So I took the chance and updated through the OTA update, it installed fine but lost root. Ran z4root (twice) and gained root access again .
Looking forward to some real custom daily driver roms for this guy.
Click to expand...
Click to collapse
Is there a way to uninstall the CWM recovery?

darkninja157 said:
Would just like to let people know that your method for "updating" via nandroid backup would not work for me. Followed all the instructions to the letter and during the advanced restore I continually received md5sum mismatch errors.
So I took the chance and updated through the OTA update, it installed fine but lost root. Ran z4root (twice) and gained root access again .
Looking forward to some real custom daily driver roms for this guy.
Click to expand...
Click to collapse
Kinda new to the whole rooting thing, just got a new Pro and rooted successfully with z4root, got rid of bloatware and installed titanium backup, wifi tether, etc. Am I correct in reading your post that I can unroot, OTA update, and re-root again? If so, will I have to uninstall bloatware again, or reinstall root apps? Or any other repeats? Any danger in doing this?

mynameismolotov said:
Kinda new to the whole rooting thing, just got a new Pro and rooted successfully with z4root, got rid of bloatware and installed titanium backup, wifi tether, etc. Am I correct in reading your post that I can unroot, OTA update, and re-root again? If so, will I have to uninstall bloatware again, or reinstall root apps? Or any other repeats? Any danger in doing this?
Click to expand...
Click to collapse
No need to un-root. This update is for the system portion only and does not touch the userdata. I simply went ahead on the rooted phone, let the OTA update download and install. In doing so lost root, but had no trouble gaining root access again via z4root. Did not have to re-remove any of the bloatware, at least if I remember correctly. Root apps will not need to be reinstalled but you may need to re-give them permission for root access. No danger that I have noticed or can think of.

For anyone doing the update the android method....
For it to work
You must do the adb "new" md5 creation portion with your phone in clockwork recovery for it to work and to not receive the mismatch error...
To do this, reboot recovery... then plug in usb from your computer... during the phone boot into recovery you should hear the alert from your computer that something from usb was plugged in. Finally, use the mount option in recovery to mount sd card to be able to transfer the .img file over to the correct directory then unmount sd card and do the adb commands in terminal window...
I had the same mismatch errors using my windows 7 machine and creating the md5 with android booted
Hope this helps

[GUIDE] How to add Flash_Image to rom using terminal

Okay, so i know several of you, like myself, have been trying to flash the recovery 3.x using flash_image through terminal but keep getting an error. This is because the rom you are using doesn't have the flash_image file in the /system/bin folder. I found these instructions on another section of the xda forums.
Disclaimer: I'm not responsible for any damage done to your phone. do this at your own risk..
1. Download and extract the file i have attached.
2. Copy the file to the root of your sdcard.
3. Open the terminal and type in these commands.
su [hit enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system [hit enter]
cp /sdcard/flash_image /system/bin [hit enter]
Now your able to flash recovery 3.x from terminal using these commands
su [hit enter]
flash_image recovery /sdcard/(recovery name).img (recovery name is whatever you have your recovery 3.x named)
i hope this helps at least one person...
Happy Flashing

Thanks bud, saved me the trouble .

No problem...like I said , if it helps at least one person im happy to know it was worth my time...

1. Make sure you have Rom Manager Installed (Free in Market).
2. rename "recovery3......img" with "recovery-clockwork-2.5.1.4-glacier.img"
3.put this "recovery-clockwork-2.5.1.4-glacier.img" on sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries/
4. Open Rom Manager and choose 2.2.1.4 from "All ClockworkMod Recoveries"
that earlest !!! then ClockworkMod Recovery v3..... will now be installed on your phone.

ls1xtreme said:
Okay, so i know several of you, like myself, have been trying to flash the recovery 3.x using flash_image through terminal but keep getting an error. This is because the rom you are using doesn't have the flash_image file in the /system/bin folder. I found these instructions on another section of the xda forums.
Disclaimer: I'm not responsible for any damage done to your phone. do this at your own risk..
1. Download and extract the file i have attached.
2. Copy the file to the root of your sdcard.
3. Open the terminal and type in these commands.
su [hit enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system [hit enter]
cp /sdcard/flash_image /system/bin [hit enter]
Now your able to flash recovery 3.x from terminal using these commands
su [hit enter]
flash_image recovery /sdcard/(recovery name).img (recovery name is whatever you have your recovery 3.x named)
i hope this helps at least one person...
Happy Flashing
Click to expand...
Click to collapse
Great guide! Will add this to my post on how to flash cwr3.

ls1xtreme said:
I found these instructions on another section of the xda forums.
Click to expand...
Click to collapse
Source would be nice.

neidlinger said:
Source would be nice.
Click to expand...
Click to collapse
Sorry but I honestly don't remember...i just did a google search for "flash_image with terminal"or something like that...

Thanks for help working excellent

says.file not.found
Sent from my HTC Glacier using XDA App

suwei said:
1. Make sure you have Rom Manager Installed (Free in Market).
2. rename "recovery3......img" with "recovery-clockwork-2.5.1.4-glacier.img"
3.put this "recovery-clockwork-2.5.1.4-glacier.img" on sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries/
4. Open Rom Manager and choose 2.2.1.4 from "All ClockworkMod Recoveries"
that earlest !!! then ClockworkMod Recovery v3..... will now be installed on your phone.
Click to expand...
Click to collapse
YOU NEED TO MAKE THAT A THREAD IT WORKED LIKE A CHARM TEN MINUTES LATER I AM RUNNING CM7 I CANT BELEIVE OT WAS AS SIMPLE AS THAT THUMBS UP THANKZZ
Sent from my HTC Glacier using XDA App

rich2thad said:
says.file not.found
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Where exactly is it giving u this message???
Oops...didn't realize u had figured it out...

after the second command it gives me an messege saying
cp not found

JXTONY said:
after the second command it gives me an messege saying
cp not found
Click to expand...
Click to collapse
I wonder if this procedure requires busybox?

Okay I have tried multiple methods as posted in this section and I cannot get to Clockwork recovery 3.xxx... I did it once before and then reverted back to the version flashable via Rom Manager. It takes me straight to fastboot when I try to reboot into recovery. Any clues what I'm doing wrong? I'm running CM6 currently and I'm slightly annoyed that I got it to work once but can't again
Sent from my HTC Glacier using XDA App

Geoi1006 said:
Okay I have tried multiple methods as posted in this section and I cannot get to Clockwork recovery 3.xxx... I did it once before and then reverted back to the version flashable via Rom Manager. It takes me straight to fastboot when I try to reboot into recovery. Any clues what I'm doing wrong? I'm running CM6 currently and I'm slightly annoyed that I got it to work once but can't again
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Have you tried to go into Rom Manager and flash the latest recovery for your phone? You can also try my method of installing ClockworkMod Recovery. It can be found HERE. If you have ADB/Fastboot set up you can also try pushing a new recovery img to your phone. If you dont have ADB set up you can use MY GUIDE to get it set up.
It sounds like your phone cant find the recovery img (could be missing).
Hit me with a PM and I can help walk ya through it if you need.

help. i downloaded the file and flashed it. i was able to boot to clockwork 3.0 and flash cm7. now when i choose 2.5.1.4 it says "an error occurred while flashing your recovery". not sure what to do. i can still get 2.5.1.2, but it won't let me get back to 2.5.1.4 which should be 3.xxx. i would like to flash to a newer nightly, but can't get the clockwork 3.xxx.

cveez11 said:
help. i downloaded the file and flashed it. i was able to boot to clockwork 3.0 and flash cm7. now when i choose 2.5.1.4 it says "an error occurred while flashing your recovery". not sure what to do. i can still get 2.5.1.2, but it won't let me get back to 2.5.1.4 which should be 3.xxx. i would like to flash to a newer nightly, but can't get the clockwork 3.xxx.
Click to expand...
Click to collapse
If you are on iced glacier try going into your settings/applications/Rom Manager and uninstall updates. Then go back to Rom Manager and try flashing 2.5.1.4

i am on cm7 nightly 24. i thought i would try to uninstall updates anyway. i went settings, applications, manage applications and rom manager is not there. i went to the market, thinking i would uninstall and reinstall rom manager and it only gives me the option to open. no uninstall. not sure what to do now,

There its a new zip I posted in the cm7 thread a page or so back
Sent from my HTC Glacier

i deleted the file i had. downloaded the latest file, flashed it and i still get the same error message.

Almost Complete Directions for A100(root, unlock, cwm, flash ROM)(HC & ICS info)

A Work in progress.
DISCLAIMER!
This Document ONLY applies to Acer Iconia A100 devices. For info on upgrading from HC to ICS you can look HERE to see the method I used to upgrade from stock HC 3.2 GEN2 to ICS (Note: This was before the general ICS release. It works on OTA update also) Then follow these directions to get to CWM with Custom ROM.
I'm writing this because we STILL don't seem to have a single clear set of instructions. So here is my attempt at getting one started. Please feel free to point out errors, or help us build a set of directions. I'm not trying replace anyones documentation or take credit for anything. All the info in these directions can already be found here in various posts.
Thanks to Vache, Civato, ZeroNull, Euclid's Brother, Ptesmoke, abliss, aznmode, eew245, crossix, Icewyng, toyface, PG101, Smokku and Everyone else for all the Work an Insight.
ROOT
To root ICS Leaks you need to use mempodroid(info & file here). Eew245 wrote up instructions (on applying mempodroid on A100 to obtain a root shell). ZeroNull also has made a basic script found here that will root the device for you if you prefer.
I use the method outlined by Eew245. You can use your own "su" and "busybox" binaries if you saved them. This method provides full permanent root.
I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox).
UNLOCK
ZeroNull has made an easy to use package with instructions here If you don't have the Android SDK installed ZeroNulls method works fine. However if you want to use your own platform-tools you will need to modify the scripts first.(Just change the path for adb. Otherwise it will try to look for adb in the scripts working directory instead of platform-tools).
Pic of Bootloader warning about unlocking from Acer
PIC HERE
Lock Unlock Icons from same bootloader screen.
PIC HERE
Note: If you miss the window of oportunity running the script or unlock commands the first time. You DON'T need to rerun the whole script. The a200 bootloader is already installed. You just need to fastboot reboot bootloader again from your console, THEN you can use the vol keys and home to unlock the bootloader. BUT do what ever you feel safest doing and just pay attention and be careful. (Here I'm referring to the waiting too long after the script boots recovery into unlock mode. If you wait too long it times out and you can't choose unlock until you fastboot reboot bootloader again.)
RECOVERY
(make sure you have installed the a200/unlocked bootloader first. You will see a message at the top of the screen that says (UNLOCK MODE) when bootloader is showing it's message at boot.)
Here is the message I'm referring to PIC HERE
NOTE: When installing a Custom Recovery at some point you have to rename /etc/install-recovery.sh or remove it. I would recomend you rename it to install-recovery.sh.bak. You should do this before doing "adb reboot bootloader" otherwise when you try to reboot into recovery from ROM manager you will get a dead android because cwm will be overwriten with the old recovery(and you don't want that). If you DO get a dead android carefully read the directions again. Q. Why didn't I put this in a step? A. Because I dont want people to brick a device so I want to make sure they are paying attention before I tell them to rename a file that will keep the system from fixing recovery if they mess up.
Using Acer Recovery Installer 2.99 Beta(NOT MARKET VERSION)
=======================================
Download .apk enable non-market installers. Run installer, enjoy.
The Acer Recovery Installer 2.99 Beta is found HERE
Using ADB/Fastboot to flash CWM
============================
Use the steps found HERE(obviously don't re-root, unlock, just follow the other parts.
Or you can also use A100 TWRP recovery v2.1.0+ I have not tried it yet. It looks nice, has touch screen functionality, I think it uses a different backup format or something though. I'm not sure and have not had time to read up on it yet.
NOTE: Read my note above about /etc/install-recovery.sh
FLASH FROM CWM
==============
If you used ADB/Fastboot method you will need a way to reboot into CWM. ROM manager or bootloader reboot thingie will work for this.
If you installed Acer Recovery Image you can use it the app to boot into CWM.
CWM 5.5.0.4 uses the Volume Up/Down Toggle to navigate the menu and a short click of the power button to select things. Be careful about what you choose to do in CWM.
MAKE A BACKUP!!
===============
If you have just installed a custom recovery NOW would be a GOOD time to make a backup with CWM.
To Install a Custom ROM
===============
(BE CAREFUL. MAKE SURE The ROM you choose to install DOESN'T have a bootloader.blob and/or /recovery folder inside. Otherwise it could overwrite your CWM)
Just put the .zip file on an SD card and put it into the device. Use ROM Manager or Acer Recovery Installer
More to come, and I will add some pics showing what various screen look like when I'm able.

"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??

cheeb said:
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
Click to expand...
Click to collapse
i +1 the question what will break if i update busy box?

cheeb said:
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
Click to expand...
Click to collapse
I don't know if this helps or makes things worst, but I have updated busybox after using Zeronull's root script on pretty much every ICS leak, CM9, and Flexreaper without any issues at all. I always read that warning, but ignored it because I need a more complete busybox version for certain tasks I run on my tablet.

NoSudo said:
A Work in progress.
Using ADB/Fastboot to flash CWM
============================
Use the steps found HERE(obviously don't re-root, unlock, just follow the other parts.
Click to expand...
Click to collapse
Just a little tip. Actually same thread post#28 uses very simple method thanks to mapaz04 to flash the recovery.
Great job though!
I did almost the same in my native language.

cheeb said:
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
Click to expand...
Click to collapse
I have not used ZeroNulls root method. So I am not sure why he says that. I think his script MAY just use the su and busybox in place in /data/local/ or something(not sure havnt D/L the package to figure it out). You CAN setup su and busybox in the correct locations WITHOUT an issue in ICS.
I use the "hard" method which is very simple. I KNOW you can remove the /data/local/tools copy afterwords doing it by hand.
An Explanation:
The reason you have to push su, mempodroid, busybox, and a mount script to /data/local/ is because you can get write access to it WITHOUT su. Then you run mempodroid which does a little magic and tricks system into thinking a shell was started by root. This drops you into the # prompt(temp). Then you mount /system(still using the files from /data/local). Then you copy the files to the correct path inside /system. Once you chmod su and run it you get root becase su is a special kind of executable. It's what is called an SUID application. As long as the permissions are correct to allow you read/exec access to both su and busybox. You no longer need /data/local/tools. At this point you CAN update busybox and su if you like.
P.S. You can also use your OLD su and busybox for the whole thing. I saved my old su and busybox and always just reuse them then update.
If you want to understand more I would suggest reading up on what SUID is all about and also learn about Unix file permissions.

I can confirm that: rooting,bootloader unlock and change on the recovery can be made with OTA update.

Nice work!

gertjanad said:
Nice work!
Click to expand...
Click to collapse
Thanks, and a bump to keep the info around the first page.

Added to bump it back up so people can find it.

Is there a kernel that allows overclocking yet
Sent from my A100 using XDA

I have not played with OCing, I honestly don't see a need.
I know cwm 5.5.0.x has an Overclock menu so I'm guessing yes you can. But I am not familiar enough with the device/cpu to know how the multipliers etc are to be configured, nor do I experience lag or performance issues that would cause me to desire lowering battery efficiency and increase heat for faster performance.
Though I am familiar with the process on PCs both jumpered and jumperless.

Up!

[Q] [Solved] Problem re-rooting (running stock 4.2.2)

I had previously rooted my phone and everything was fine... The OTA 4.2.2 update came automatically and took away root (but kept the bootloader unlocked). A few months passed and I decided to reroot using the same approach as before .... it fails. It looks like it works, but once the phone reboots I don't have root access.
Note I am using the following commands:
> adb push su.zip /sdcard/
> fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
> adb reboot bootloader
Then I select install from sdcard and selecting the su.zip file and back out / reboot.
Only odd thing I see is that I have two superuser apps installed (must have used different zip files). But neither app works...

ChrisG12 said:
I had previously rooted my phone and everything was fine... The OTA 4.2.2 update came automatically and took away root (but kept the bootloader unlocked). A few months passed and I decided to reroot using the same approach as before .... it fails. It looks like it works, but once the phone reboots I don't have root access.
Note I am using the following commands:
> adb push su.zip /sdcard/
> fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
> adb reboot bootloader
Then I select install from sdcard and selecting the su.zip file and back out / reboot.
Only odd thing I see is that I have two superuser apps installed (must have used different zip files). But neither app works...
Click to expand...
Click to collapse
adb reboot bootloader ?? or fastboot reboot-bootloader?? you are supposed to be in fastboot mode.
i dont know if this will make sense: flash latest CWM http://www.clockworkmod.com/rommanager and install latest supersu http://download.chainfire.eu/324/SuperSU/UPDATE-SuperSU-v1.30.zip
open supersu and update su binary
install busybox

2 in a row: OP, read the stickies on general and q&a by efrant before asking questions.
a maguro wrote this.

Actually - I did read the stickies before posting - thanks though. I know how to root - done it on a few devices in the past. Done it successfully on my Nexus in the past too...
For the record, those commands I listed are valid (they are from instructions on Droidlife.com and XDA) - I prefer not to use a "one-click" tool. So I use the Android SDK and run commands from a DOS window one at a time. Also - this way I don't have the custom ROM permanently installed on my phone...
That exact procedure worked in the past - but now it doesn't. I've tried the latest roms, etc. nothing - all the commands seem to run fine but after the phone reboots - I don't have root.
I did at one point try one of the one click tools ("Nexus Root Toolkit") - but it didn't seem to work either.
Has anyone seen this problem? I seem to have two copies of supeuser installed on my phone (one from the previous successful rooting and one from my current attempts) - is that a problem? I can't seem to get rid of them (chicken and egg - need root to remove APK)...

Huh? Superuser? Use SuperSU. Here, check this thread. http://forum.xda-developers.com/showthread.php?t=1538053 - the flashable zip is on the first post. Now, what you should do is, while on a custom recovery, 'adb shell', mount /system rw, delete traces of previous su zips, and then flash SuperSU zip.
a maguro wrote this.

Thanks man - that did it!

ChrisG12 said:
Thanks man - that did it!
Click to expand...
Click to collapse
Please edit thread title to include [SOLVED] after [Q]; reported to mod team for closing.
a manta wrote this.