Related
This is aimed at new "rooters". The process is incredibly easy.
I also take no responsibility if you mess up somehow, and this is for GSM Hero's NOT Sprint Hero CDMA users.
In order to create this guide I downgraded my phone to RUU Orange UK 2.73.61.66 (i.e. unrooted) then updated to the pre-2.1 release from Orange and then updated to the final 2.1 release from Orange. I then used Universal Androot to gain root access and from there install a custom recovery.
I have now also included a link to z4root as an alternative.
Here is a link to my backup guide but please be aware that most of it requires root access.
Prelude:
Install HTC Sync from here
Download Universal Androot
Download z4root
Download Root Checker - only if you need to
Download AmonRA Recovery v1.7.0.1.img - easier if you rename this "recovery.img" when it is on your sdcard
Place both downloaded files on your SD Card
Root & Recovery
1. Download and install Astro File Manager from the Market (or use any other file management program of your choice)
2. Open Astro and find and install Universal Androot (or if that doesn't work try z4root) from your sdcard:
Select UniversalAndroot.apk > Open App Manager > Install > Settings> [tick] Unknown Sources > OK > Back > Select UniversalAndroot.apk > Open App Manager > Install > Install > Open
3. In the app and choose the correct version from the dropdown box:
Superuser for Android 2.0~2.2 - if you have updated your phone recently
Superuser for Android 1.5~1.6 - if you have refused updates recently or your country/provider hasn't released one yet
Then choose: "Root "
Wait until it says "Woot ! Your device is rooted !" and exit the program.
4. Download and install Android Terminal Emulator from the Market (use Better Terminal instead if this one doesn't work)
5. Run "Terminal Emulator". Type (press and hold menu to get the keyboard up) in the following:
su (press enter and wait for the "Super User Request Prompt". Choose "Allow" and make sure its ticked to Allow every time.)
flash_image recovery /sdcard/recovery.img (press enter - make sure this is typed exactly as seen)
N.B. If you have issues here, see * notes below for more assistance
6. Turn off your phone and press Home + Power to start it up again. This should boot into recovery mode.
Install Your Custom Rom
Note: This part of the guide can be repeated with as many different rom's as you like. You do not have to repeat the previous section once you have a recovery image installed.
1. Download a Custom ROM from here to your computer.
2. Make sure your phone is in recovery mode (Home + Power)
Plug your phone into your computer and select "USB-MS toggle" in recovery
Place the Custom ROM on your SD card in the main directory and press Home when it has finished copying over
3. Select Backup/Restore > Nand backup > confirm with Home > Wait
(or Nand + Ext if you have A2SD setup)
4. Press back then select Wipe from the main menu, then select:
Wipe data/factory reset > Home
Wipe cache > Home
Wipe Dalvik-cache > Home
Wipe SD:ext partition > Home
Press back button
Select Flash Zip from SD Card
Select the file
Press Home to confirm
Note: Ignore any "errors", they are normal and usually mean you're not using that feature.
5. Once it is done, select Reboot and you will boot into the new Custom ROM.
Updating your Radio
Note: The radio deals with your signal levels and connectivity.
1. Download the latest radio from the following page
N.B. Radio's are not region specific! Just get the latest
2. Mount your SD Card so your computer can read it and place the downloaded file in the main directory
3. Turn off your phone and boot into the recovery screen (holding Home + Power)
4. Choose:
Flash Zip from SD Card
Pick the radio.zip file and press Home to confirm
Wait
Your phone will reboot a couple of times but when you're back on the Recovery Screen just press reboot system now and it will complete the install and put you back into your custom rom.
DO NOT PULL THE BATTERY OUT, THIS WILL BRICK YOUR HANDSET.
5. When this process has completed reboot the phone and you should have the new radio. This can be checked in Settings > About Phone
*Useful Information!!
42turkeys said:
Tested this on 1.5 the other day, nice one BtDaG
For those of you having problems flashing the recovery, try entering this before the flash_image command:
Code:
rm /data/local/rights/mid.txt
ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
(btw, ROM Manager has an option to flash Amon_RA at the bottom )
Click to expand...
Click to collapse
** Missing flash_image - confirmed to work by another user, please inform if different
Download the flash_image.zip and unzip to your PC folder. Setup ADB. Place the recovery_image .zip in a folder called recovery on your computers C: drive. Then you will be able to run the following adb commands below from a cmd prompt on your computer:
cd c:\recovery
this will ensure you are in the correct folder
adb root
This will start ADB as root, or notify if it is already running as root.
adb remount
This will mount the system partition (/system) as writable, allowing the following
adb push flash_image /system/bin
This will send the flash_image script into the /system/bin, so we can use it from within the shell
adb shell chmod 0755 /system/bin/flash_image
Finally, change the permissions of the script to allow it to perform the desired action. Now that the script is installed, we are ready to proceed with flashing the custom recovery, saved on the root of the SD card earlier:
adb shell flash_image recovery /sdcard/recovery.img
this will install the the recovery - now continue the process where you left off
Click to expand...
Click to collapse
*** solution 3
brisuth said:
A big thankyou to duck0 for identifying the problem and botoo for getting me to a happy conclusion with the correct commands
SOLUTION IS HERE USING Console mode from windows using ADB USB DEBUGGING HAS TO BE ENABLED WITH HERO CONNECTED TO PC THEN TYPE THE FOLLOWING
THEN ENTER AFTER EACH COMMAND
anyone needing help setting up adb see this link http://forum.xda-developers.com/showthread.php?t=757233
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm /system/etc/install-recovery.sh
Thats it all done next step
INSTALL ROM MANAGER FROM MARKET IT IS FREE
open it and sellect flash alternate recovery image from the bottom, you can use the clockwork recovery but it is not compattable with all roms.
once done turn phone off, boot into recovery home + power choose to exit recovery with reboot shut down once again and if you can enter recovery then everything is sweet.
Click to expand...
Click to collapse
Setup Apps2SD
ONLY RECOMMENDED ON CLASS 4+ SD CARDS. Don't bother if you don't know what this is . GIYF.
Do this process after doing everything else! So make sure you have a working custom rom installed which supports Apps2SD. This is designed for VillainROM which doesn't use a swap, if your ROM does support swap ask for a recommended amount. Also note that the ext2 partition will be unreadable from windows or through android os.
1. Backup your SD card to your computer (very important as this process will wipe all the data on it)
2. Restart your phone into recovery mode (Home + Power)
3. Select:
Partition sdcard
Partition SD
Press Home
Swap-size = 0 MB
Ext2-size = 512 MB (recommended)
FAT32-size = Remainder
Press Home
4. Once complete Reboot system now and wait! This can take 20 minutes or so to complete, so just keep waiting!
DO NOT USE EXT3 or EXT4 partitions. They will just wear out your sd card quicker. They are designed for large files systems (i.e. 50GB+) with full operating systems running on them! The only benefit they bring is indexing (which on a 512MB partition is worthless). (Optional - before reboot) - Under partition sdcard you can convert the ext2 partition to ext3 - "SD:ext2 to ext3" - however this isn't recommended as it will wear out your sd card quicker. There is also often support for ext4 so you can do "SD:ext3 to ext4" after the first one too. Though again this will typically just wear out your SD faster without providing any speed benefits. See note above.
Code:
[B]OLD PROCESS BACKED UP JUST IN CASE. PLEASE DO NOT FOLLOW THIS SECTION OF THE GUIDE![/B]
Largely based upon the Unlockr guides, so thank you Unlockr!
Please do NOT be mislead. This is NOT a quick process, though the time has been reduced significantly if you don't need the goldcard method.
There is no "one-click" version or "quick-install".
You should set aside at least an hour for this process and preferably read through the process once before actually attempting it.
[B]Please make a quick post with your experiences, including your brand of phone and location.
Please check the FaQ first before asking questions :)[/B]
[COLOR=DarkGreen][SIZE=3][U]Contents[/U][/SIZE][/COLOR]
[COLOR=DarkRed]Pre: Backup[/COLOR]
[COLOR=Navy]1. Installing a Recovery Image
a. Installing the Correct HTC ROM
2. Loading the Custom ROM
3. Updating your Radio[/COLOR]
[COLOR=DarkOliveGreen]Setup Apps2SD
Check A2SD[/COLOR]
[COLOR=DarkSlateBlue]"GoldCard" Test Procedure
I. Setting up the drivers
II. Create a “GoldCard” from a MicroSD Card
III. Downgrade the Hero using the Goldcard[/COLOR]
[COLOR=DarkGreen]FaQ[/COLOR]
[COLOR=DarkRed][SIZE=3][U]Pre: Backup[/U][/SIZE]
1. Backup contacts etc with HTC Sync.
2. Backup your SD Card or use a spare
3. Backup SMS Messages with SMS Backup & Recovery[/COLOR]
[COLOR=Navy][SIZE=3][U]1. Installing a Recovery Image[/U][/SIZE]
1. On your phone, go to Settings > Applications - and make sure "Unknown Source" is ticked.
2. On your phone, go to Settings > SD card and phone storage - click Unmount SD card.
3. Then click Format SD card.
4. Plug the phone into the computer via USB, then pull down the notification bar and click on the SD card notification. Then click mount.
5. Download this APK and recovery image and save it to your computer:
[URL]http://zenthought.org/content/project/flashrec[/URL] - FlashRec.apk
[URL]http://forum.xda-developers.com/showthread.php?t=561124[/URL] - Amon_Ra’s Hero Recovery Image
6. Copy them both to your SD card (do NOT put them inside any folders on the SD card, just put them on the SD card itself).
7. Unplug the phone from the computer once they are downloaded to the SD card.
8. Go to the Market and download ASTRO File Manager or any file manager program if you do not already have one.
9. Open the file manager and find the FlashRec apk file and click it and choose open app manager and then install it.
10. When it is installed click Open. Click on Backup Recovery Image and wait for it to finish. If you get "backup failed" response see the text on the right for more details, if the backup is a success carry on to step 11.
[RIGHT][SIZE=1][U]a. Installing the correct HTC ROM[/U]
Orange UK Users - Please downgrade your ROM version to [URL="http://www.htc.com/uk/SupportViewNews.aspx?dl_id=675&news_id=261"]2.73.61.5[/URL]
Generic Hero Users - Please downgrade to [URL="http://x7.to/6jexri"]2.73.405.5[/URL], or follow the goldcard method if this doesn't work
T-Mobile UK Users – Please follow the "Goldcard" method below
All Other Users - Please follow the "Goldcard" method below[/SIZE][/RIGHT]
11. Once done, click on the empty text box in the FlashRec program and type:
/sdcard/recovery-RA-hero-v1.6.2.img
(replace exact name as new versions come out)
Then click on the Flash Recovery Image button and wait for it to finish.
[SIZE=3][U]2. Loading the Custom ROM[/U][/SIZE]
N.B. This part of the guide can be repeated with as many different rom's as you like. You do not have to repeat the previous sections once you have a recovery image installed.
1. Download a Custom ROM from [URL]http://forum.xda-developers.com/forumdisplay.php?f=512[/URL] to your computer.
2. Plug in your phone and pull down the Notification bar when the SD notification pops up.
3. Click on the notification and select Mount.
4. Open the SD Card fonder on your computer.
5. Copy the Custom ROM from your computer to your SD Card, do NOT change it, extract the files or put it in any folders
6. Unplug your phone and turn it off.
7. Turn the phone on by holding down Home and Power till you get to the custom recovery screen.
8. Select Wipe from the menu, then select:
Wipe data/factory Reset
Wipe Dalvik-cache
Wipe SD:ext partition
Press back button
Select Flash Zip from SD Card
Select the file
Click Confirm
N.B. Ignore any "errors", they are normal and usually mean you're not using that feature.
9. Once it is done, select Reboot and you will boot into the OS. Once you are loaded in make sure you format your SD card once more through the settings menu and then reboot the phone one last time. This will ensure you get the correct apps.[/COLOR]
[COLOR=Navy][SIZE=3][U]III. Updating your Radio[/U][/SIZE]
[B]N.B. People have been reporting problems with this part of the guide, try it at your own risk. It is not required to be on the latest radio when using a Custom ROM, however it is usually recommended! The radio deals with your signal levels, I found it to increase my signal from a maximum of 2 bars to full. It is likely to help if you travel, but if you are happy with your signal and tend to stay in the same place it may not be worth it.
Be aware that if this doesn't work it can potentially brick you phone... though I've had no reports of that so far. Just people finding it doing different things after it flashes.[/B]
1. Download the latest radio from the following site:
At time of writing that is: [URL="http://www.villainrom.co.uk/radio/Radio_Signed_HERO_63.18.55.06PU_6.35.15.14.zip"]63.18.55.06PU_6.35.15.14[/URL]
[B]N.B. Radio's are not region specific![/B]
2. Mount your SD Card so your computer can read it and place the downloaded file in the main directory
3. Turn off your phone and boot into the recovery screen (holding Home + Power)
4. Choose:
Flash Zip from SD Card
Click Confirm
Reboot system now when prompted
N.B. This can take anywhere between 1 - 10 minutes or maybe even longer in some cases. Do not touch your phone until you either: get back to the recovery screen or your custom rom loads and you see the unlock screen.
DO NOT PULL THE BATTERY OUT, THIS WILL BRICK YOUR HANDSET.
5. When this process has completed reboot the phone and you should have the new radio. This can be checked in Settings > About Phone > Software Information > Baseband Version[/COLOR]
[COLOR=DarkOliveGreen][U][SIZE=3]Check A2SD[/SIZE][/U]
Please assume it is automatically working unless you can load applications without your SD card inserted. However, here is the process for those who are pedantic about these things. Many thanks to VillainROM Wiki for this process.
1. Download check.zip from the bottom of this guide.
2. Extract check.sh
3. Download GScript Lite from the market
4. Place check.sh on your SD card in a folder named gscript
5. Open GScript and press:
Menu
Add Script
Uncheck "needs su"
Load File
Select check.su
Save
6. Then click check from the main screen and you will get a readout of whether it is enabled or not.[/COLOR]
[COLOR=DarkSlateBlue][SIZE=3][U][B]"GoldCard" Test Procedure[/B][/U][/SIZE]
Please comment on whether this procedure works, it is untested. Thanks to [URL="http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735"]ante0's guide[/URL] for some details used.
[SIZE=3][U]I. Setting up drivers etc[/U][/SIZE]
1. Download the latest HTC Sync from [URL="http://www.htc.com/www/SupportViewNews.aspx?dl_id=933&news_id=631"]here[/URL] and the latest SDK from [URL="http://developer.android.com/sdk/index.html"]here[/URL]
2. Install HTC Sync & extract the Android SDK .zip file to C:\ (may help to re-name the folder to a shorter name, in this tutorial it will be C:\android\ )
3. Click on your Windows Start menu and right click on "Computer" > Properties > Advanced System Settings > Environment Variables
Find "Path" under "System Variables" and edit it. Add the following to the end of the text:
;C:\android\tools
4. Restart your computer.
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
When back at your desktop plug then phone in and wait for it to install the correct drivers, this should be done automatically on the latest version of HTC Sync and adb should be enabled.
5. Type the following into the command prompt window (Start > Search > "cmd") and enter the following and press enter:
adb devices
You should see a serial number pop up and look like:
000000000000 device
It’s the serial number of your phone. This means the drivers are working in normal boot mode. Next we need to check them in fastboot mode (thanks to janhol for helping with this next part)
6. Turn off your phone and load into fastboot by holding the Back button and pressing Power with the hero plugged into the computer
7. "Start" > Right Click "Computer" > "Manage" > "Device Manager"
8. Check that the "ADB Interface" reads "My Hero", not "Android bootloader drivers" or anything else.
If it does then:
Right click "Android bootloader drivers" > "Update Driver Software" > "Browse my computer..." > "Let me pick from..." > "Have Disk..." > "Browse" > "C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64" > "androidusb.inf"
Once selected click "OK".
"My HTC" should show in the list of "compatible hardware" now, so select that and click "Next" to install the driver. Switch off the phone (may have to pull the battery).
[SIZE=3][U]II. Create a “GoldCard” from a MicroSD Card[/U][/SIZE]
(Please keep in mind that some memory cards don’t work for this process)
1. Put the memory card you want to use for the GoldCard into your phone, make sure all the data is backed up before proceeding as it will be formatted.
2. With the memory card in your phone, and not connected to the PC, click on:
Settings > SD and Phone storage > Unmount SD Card
Once it unmounts, click Format SD Card.
3. On your phone, click:
Settings > Applications > Development and make sure USB Debugging is on.
4. Return to the Command Prompt from earlier after re-plugging in your Hero. Then type the following with hitting enter at the end of each line:
adb shell
cat /sys/class/mmc_host/mmc1/mmc1:*/cid
5. A code will display, write the code down into a notepad document or similar (MAKE SURE TO WRITE IT DOWN EXACTLY!)
6. Go to this site: [URL]http://hexrev.soaa.me/[/URL] then put in your code you just wrote down into the text box and click submit. It will generate the code reversed and replace the first two digits with zeros automatically. Copy this.
7. Then go to [URL]http://psas.revskills.de/?q=goldcard[/URL] and Paste your CID into the box and fill in the other details. You'll be e-mailed the goldcard. Save the goldcard image to disk.
8. Now go to [URL]http://download.cnet.com/HxD-Hex-Editor/3000-2352-10891068.html?part=dl-HxDHexEdi&subj=uo&tag=button[/URL] to download the HxD Hex Editor. Install it to your computer.
9. Mount your SD card on your phone so that it shows up on your computer as "Removable Disk" - Pull down the notification bar on the phone and select Mount CD Card.
10. Open the Hex Editor (Run as Administrator if you're in Vista or Windows 7) and click on the Extra menu > Open Disk. Under "Physical Disk" select "Removable Disk". Make sure to UNcheck “Open as ReadOnly”. Click OK.
11. Go to the Extra menu again and click Open Disk Image. Open up the goldcard.img that you saved from your email. Press OK when prompted for Sector Size 512 (Hard Disks/Floppy Disks). You should now have two tabs, one is the SD card (Removable Disk) and the other is the goldcard.img.
12. Click on the Goldcard.img tab and press Ctrl + A (select all) Then Ctrl + C (copy).
13. Click on the Removable Disk tab (Your SD Card) and select the complete lines from 00000000 to 00000170 then press Ctrl + V (paste).
14. Click on File then click Save.
15. Close the Hex Editor.
16. Reboot the phone.
Try to open the memory card on the computer (i.e. mount the drive), if it lets you, you are all set. If it asks/tells you to reformat the card, then try steps 13 – 19 again. If it gives you the same error again, then try a different memory card. You can confirm that it has worked by opening the Removable Disk in the hex editor again and making sure the code you pasted in has stayed but this shouldn't be necessary.
[SIZE=3][U]III. Downgrade the Hero using the Goldcard[/U][/SIZE]
1. With your phone plugged in, pull down the notification bar on the phone and select HTC Sync. Make sure it connects to HTC Sync on the computer (not sure if this is necessary anymore).
2. Download this generic HTC Hero RUU
Hero RUU -
[URL="http://x7.to/6jexri"]2.73.405.5[/URL]
[URL="ftp://xda:[email protected]/Hero/Official-ROMs/RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe"]2.73.405.5[/URL] (alternative)
3. Double click the RUU exe you downloaded while the phone is plugged in with the GoldCard in it and follow the on screen procedure. This will install the old generic Hero rom on your phone, this is to allow you to install a recovery image. Reboot and fill in as few details as possible as these will be overwritten soon.
4. Now you have finished this procedure start from the beginning again.[/COLOR]
Website: [URL]http://rootmydroid.co.uk/[/URL]
Other Guides:
[URL="http://forum.xda-developers.com/showthread.php?t=669754"]How to Backup your Phone Between Wipes[/URL]
Even older process - ignore
[COLOR=DarkOrange][SIZE=3][U][B]Old "GoldCard" Procedure[/B][/U][/SIZE]
[SIZE=3][U]I. Setting up the SDK[/U][/SIZE]
1. Download the Latest Android SDK from Google
Android SDK - [URL]http://developer.android.com/sdk/index.html[/URL]
(currently - android-sdk_r06-windows.zip) but get the latest
2. Extract the Android SDK .Zip file to C:\ (may help to re-name the folder to a shorter name, in this tutorial it will be C:\android\ )
3. Run SDK Setup.exe
4. Click "Settings" and check the "Force [URL]https://.[/URL].. sources ..." option
5. Click "Available Packages" and download the "USB Driver Package"
6. On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
7. Plug your phone into your computer via USB cable.
8. Go into device manager: Start --> Search for "device manager"
9. Here we are checking the driver which is installed for your Hero, you may see either of the following scenarios:
Other Devices > ADB
or
Android Phone > My HTC
Either way you should do the following:
Right Click > Update Driver > Browse > C:\android\usb_driver > Next and it should install "Android Composite ADB Interface"
10. Type the following into the command prompt window (Start > Search > "cmd") and enter the following hitting enter at the end of every line:
cd c:\android\tools\
adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set.
If you do NOT see a serial number, then we need to reinstall the drivers.....
end cut off due to size limits
nice
i`m sure it will help alot of people out, it took me a whole day to sort mine out.
cheers
nice one. you've just summarised my last sunday afternoon. great to have this all in one place. needs to be a sticky imho.
Nice Tutorial... Please give me the SPL version and Radio Version of the Hero that this worked on.
brettf said:
Nice Tutorial... Please give me the SPL version and Radio Version of the Hero that this worked on.
Click to expand...
Click to collapse
The radio was different on both the devices tested and I am fairly certain it has no effect on whether you can do this procedure or not. They are now both flashed with the latest radio.
I have no record of the "SPL versions". Again I'm not really sure how this is relevant?
This guide assumes the user has no knowledge of these things and have made no previous modifications to their phone (besides standard updates)
You'll have to bear with me as I'm pretty new to all this as well. The guide was made because I found the others extremely difficult to follow. I'm glad to see by the other posts that I am not the only one
Im doing this now, my Hero was delivered this morning and i was looking for in depth instructions so I cant go wrong. This looks bang on,... Just about to start section II (creating Goldcard) but thought i'd better put up some thanx 1st.
Wish me luck, i'm assuming it'l all go ok, i'l post again once its done.
Thanks again BTDAG.
Peace
Guys I'm stuck,... Section II, part 10, Mount your SD card on your phone so that it shows up on your computer as "Removable Disk".
Through the setting on my phone I can only select "UNMOUNT SD CARD"!!! Arggghhhh!!!
Can anyone help please?
AHA,... That'l teach me to not read the whole thing 1st!!!!!!
In section III, part 3,... You have put "pull down the notification bar and click on the SD card notification. Then click mount." .... Maybe edit the 1st post and put it in (for the idiots like me).
Thanks though.
ddotpatel said:
AHA,... That'l teach me to not read the whole thing 1st!!!!!!
In section III, part 3,... You have put "pull down the notification bar and click on the SD card notification. Then click mount." .... Maybe edit the 1st post and put it in (for the idiots like me).
Thanks though.
Click to expand...
Click to collapse
I had no idea that was in the wrong order, thanks for pointing it out. I'll edit that now!
I had to figure most of this out as I was going so i quickly forgot what I did differently. The more people point out the better the guide will get! XD
Great guide.
Add it as a Wiki... it will not get a sticky!
nprussell said:
Great guide.
Add it as a Wiki... it will not get a sticky!
Click to expand...
Click to collapse
Thanks. I love your ROM's and can't wait for the next Villain release.
Already done as I figured as much.
Oh my god!! Im was having an absolute mare!!!!!
Was trying to downgrade the rom,... but HTC Sync would not connect (Part III, no 3), everything else was ok... 1st i ignored it and just carried on, started flashing, phone went into that 'Fastboot' bit where there are the Android thingies on skateboards, but then failed, came up with an error message, then froze. I had to take the battery out!!!
Started up fine though.
So i gave up for a while to stop me from throwing my laptop against the wall!!!
But the missus has just got home so im booting up her XP lappy, thought it might be cos im using Win7 64bit. So here goes again!!!!
question:
i Would like to install a custom Rom on Hero
i have two micro SD cards ( 2GB i 8GB )
1. I would like to use 8GB card for apps and music...
Do I have to create a "Gold Card" on the 8GB card, or can I use the 2GB card to creat "Gold Card"?
2. Durin the installation of a Custom Rom, do I have to put in the phone the "Gold Card" (2GB), or can I put the 8GB card?
And
3. if I want to "roll back" the original ROM, can I do that just simpley by puting in the "Gold Card" and rolling back te rom saved on Gold Card?
THX
(sorry for my English)
ddotpatel said:
Oh my god!! Im was having an absolute mare!!!!!
Was trying to downgrade the rom,... but HTC Sync would not connect (Part III, no 3), everything else was ok... 1st i ignored it and just carried on, started flashing, phone went into that 'Fastboot' bit where there are the Android thingies on skateboards, but then failed, came up with an error message, then froze. I had to take the battery out!!!
Started up fine though.
So i gave up for a while to stop me from throwing my laptop against the wall!!!
But the missus has just got home so im booting up her XP lappy, thought it might be cos im using Win7 64bit. So here goes again!!!!
Click to expand...
Click to collapse
O Windows 7 64-bit needs different drivers. I have attached them here to the original post. I am also on 64-bit but completely forgot about those hassles. Thanks for the reminder.
ico86 said:
question:
i Would like to install a custom Rom on Hero
i have two micro SD cards ( 2GB i 8GB )
1. I would like to use 8GB card for apps and music...
Do I have to create a "Gold Card" on the 8GB card, or can I use the 2GB card to creat "Gold Card"?
2. Durin the installation of a Custom Rom, do I have to put in the phone the "Gold Card" (2GB), or can I put the 8GB card?
And
3. if I want to "roll back" the original ROM, can I do that just simpley by puting in the "Gold Card" and rolling back te rom saved on Gold Card?
THX
(sorry for my English)
Click to expand...
Click to collapse
1. The gold card is only used to allow you to downgrade (as far as i'm aware) so you can use the 2GB as gold card and 8 GB for music but... (see next)
2. I have no idea, probably best to leave the gold card in and replace it when the ROM is flashed but I don't think it is mandatory. I do however, have no idea how long it is needed for. Just make sure you format the card you're going to use through the phone when you insert it for the first time.
3. If you want to go back to your Orange or T-Mobile ROM from HTC all you have to do is use the latest .exe you get from HTC's support website. Once again it is probably best to format your SD card after first boot.
The only thing that's stopping me from trying this out is the goldcard thing - I really don't want to format my 8Gb card. I could use the 2Gb one from my old G1, but it's going on eBay in the next week so if I needed the exact same goldcard at some point in the future then I'd be stuffed.
I suppose that I'll just have to live without the glory of being rooted for now!
thedoccwc said:
The only thing that's stopping me from trying this out is the goldcard thing - I really don't want to format my 8Gb card. I could use the 2Gb one from my old G1, but it's going on eBay in the next week so if I needed the exact same goldcard at some point in the future then I'd be stuffed.
I suppose that I'll just have to live without the glory of being rooted for now!
Click to expand...
Click to collapse
You could backup the data on the 8Gb card (i.e. copy and paste it to a folder on your pc) then format it and restore any music / pictures etc back to it. Just avoid replacing any old settings files specifically related to the HTC widgets, that is where problems occur.
O i'm also fairly certain you won't need the gold card again unless you go back to the official HTC releases and need to downgrade again and there is no harm to making your 8GB a gold card in the future as you can still back-up and restore the data you wish to keep on it.
wow nice guide, bookmarked! i spent ages looking for all the info about a month ago.
ive decided that i only really need to install a custom ROM when htc decide not to offer official updates anymore.
btdag said:
You could backup the data on the 8Gb card (i.e. copy and paste it to a folder on your pc) then format it and restore any music / pictures etc back to it. Just avoid replacing any old settings files specifically related to the HTC widgets, that is where problems occur.
O i'm also fairly certain you won't need the gold card again unless you go back to the official HTC releases and need to downgrade again and there is no harm to making your 8GB a gold card in the future as you can still back-up and restore the data you wish to keep on it.
Click to expand...
Click to collapse
No, no, no, you're meant to say something like 'ahh, probably for the best that you don't bother for now then'. The slightest pro-rooting comment is going to have me going for it! Still, it is character building, I suppose. And I did feel much better for having done it to my G1...but can I be bothered to do it at this time of night?!?!
mobydeek said:
wow nice guide, bookmarked! i spent ages looking for all the info about a month ago.
ive decided that i only really need to install a custom ROM when htc decide not to offer official updates anymore.
Click to expand...
Click to collapse
but your missing out on so much now
The purpose of this guide is to walk you through the process of rooting your phone running 2.3.3 ONLY! I will do the best I can to make this as painless as possible and help you achieve your goals of S-Off.
***THIS THREAD IS ONLY FOR OBTAINING S-OFF, OBTAINING ROOT, AND INSTALLING CLOCKWORK MOD RECOVERY! ANY QUESTION REGARDING INSTALLING ROMS DO NOT BELONG HERE AND WILL NOT BE ANSWERED! ONLY ISSUES REGARDING ROOT WILL BE ANSWERED BY MYSELF OR OTHER MEMBERS.***
What you will need: (** = File is attached to OP)
Windows XP or higher (Thats all I have, someone else with MAC and/or Linux will need to assist and I can add it to the OP)
http://revolutionary.io/ .:UPDATE:. PRE4 now available
This site is where you will download the rooting tools and obtain a beta key. When you click on the download button for your OS, make sure you view the box that pops up requesting your OS version, phone model, HBoot version, and phone serial number. Without doing this you cannot root your phone so do it or you are screwed. There are two ways to get your phone serial number: 1) Remove the battery and look at the white sticker or 2) On your phone, go to Settings -> About Phone -> Phone Identity and under Device Serial Number you will see it. After you receive your code COPY AND PASTE it onto a word document or notepad because there are times when you will get confused with the font type from the Revolutionary site. Example, in my beta key, the lower case L looks exactly like the capital I and it threw me off. Also, the key IS case sensitive so keep that in mind.
If running windows, you will need these drivers:
http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
If running Linux, reports show that you do not need any drivers.
If running Mac OS, I currently do not know so someone please let me know and I will update.
http://goo-inside.me/superuser/su-2.3.6.3-efgh-signed.zip **
This file is required to obtain ROOT AFTER you have S-Off.
http://forum.xda-developers.com/attachment.php?attachmentid=630611&stc=1&d=1308537076 (WINDOWS) **
http://forum.xda-developers.com/attachment.php?attachmentid=630611&stc=1&d=1308537076 (LINUX) **
http://dl.dropbox.com/u/33327355/cwm-4.0.1.4-vivow.img **
These two items are in case Revolutionary tool fails to install CWM on your phone OR if you want to do this offline at another location. Fastboot and abd tool is the software that will take the img file of CWM and flash it onto your phone after S-OFF is obtained.
Prepping your Phone:
Turn off FAST BOOT in the settings located: SETTINGS -> POWER
Turn on Unknown Sources: SETTINGS -> APPLICATIONS
Turn on USB Debugging: SETTINGS -> APPLICATIONTS -> DEVELOPMENT
Installing Root:
1 - First, install the HTC drivers on your computer. It is a very simple step and you should have no issues doing this at all. Also look at your installed programs list and confirm HTC Sync is not installed. This will stop your device from being detected by Revolutionary to other problems when rooting.
2 - Extract the Fastboot and ABD zip file onto the root of your local disk drive (ex. C:\android-win-tools )
3 - Copy/Cut and Paste the CWM img file into the Fastboot and ABD folder (ex. C:\android-win-tools\cwm-4.0.1.4-vivow.img) Doing this will prep your PC to flash CWM in the event the Revolutionary tool does not download and install it.
4 - Place phone in "Disk Drive" mode then Copy/Cut and Paste the root su zip file (do not extract it) onto the root of your SDCard on your phone (ex. x:\su-2.3.6.3-efgh-signed.zip )
5 - Place phone in "Charge Only" mode. A lot ot people run into issues and not realize this was not selected.
6 - Run the Revolutionary file now that everything is set to go.
7 - You will get a prompt to enter your beta code. This is the code you received when you downloaded the revolutionary file and entered the information to obtain the beta key.
8 - Sit back and WAIT while the application does what is needed. This process will take anywhere from 3 to 5minutes so be PATIENT.
9 - Upon completion, you will get a prompt to install CWM. Say yes here! Once done skip to step 10.
9a - If the revolutionary app crashes or fails to download/install, leave your phone in the state it is (HBoot mode and should say "Fastboot USB". Open a command prompt in windows (Start - Run - type CMD).
9b - If you did exactly as told, type "CD.." until you see "C:\"
9c - Type the following:
CD android-win-tools
fastboot flash recovery cwm-4.0.1.4-vivow.img
9d - This process takes about 30sec max. Almost done!!!
10 - On your phone, back track to the main menu of HBoot using the volume keys and Power button and select recovery (2nd Option). In a few seconds your will be in CWM.
11 - As long as you copied the signed zip file to the root of your sdcard, perform the following:
"Install Zip From SDCard" (5th Option)
"Choose Zip From SDCard" (2nd Option)
Select the root/su zip file (su-2.3.6.3-efgh-signed.zip)
Choose Yes and wait.
Back track to main menu and reboot
12 - Give yourself a pat on the back for paying attention and have a cookie!
I am typing this on my tablet/phone/pc so if an error exists, please let me know right away and I will update the OP. Again, questions here are ONLY for rooting. Anything else...kick yourself in the head, do a real search, and post if needed.
Support:
http://unrevoked.com/rootwiki/doku.php/public/revolutionary
Common Q&A for their recovery tool
irc.freenode.net channel #revolutionary
IRC Support Channel
Special thanks to:
XDA-Developers - You guys rock!!!
AlphaRev and unrevoked (Revolutionary) - You have made many dreams come true!!! DONATE to them if you can peeps.
http://forum.xda-developers.com/showthread.php?t=1122694 - attn1 - his How to guide on manually installing CWM.
Nice guide bro.
Sent from my Incredible Sensation using XDA App
The Incredible 2 or VIVO is not an option in the Beta key?
kyrumo71 said:
The Incredible 2 or VIVO is not an option in the Beta key?
Click to expand...
Click to collapse
The incredible 2 is definitely an option when obtaining a beta key. Unless you are refering to something else?
rivera82falcon said:
The incredible 2 is definitely an option when obtaining a beta key. Unless you are refering to something else?
Click to expand...
Click to collapse
My bad, my work computer is crappy, the 2 does not show up on my browser lol
NICE, this thread should be sticky.
On a side note, make sure you have your phone connected to wifi or 3G if you want the revolutionary tool to download and install the CWM automatically. If not then you would have to flash the CWM manually per the instruction from OP.
kyrumo71 said:
My bad, my work computer is crappy, the 2 does not show up on my browser lol
Click to expand...
Click to collapse
I went to the site just now and HTC DROID Incredible 2 is the 6th option down in the device list. If it still doesn't show up, test another pc or try it on your phone. All you need is the key anyways.
Sent from my A500 using XDA Premium App
Thanks for this guide...
Sent from my DROID using XDA App
Awesome thanks but question. my computer keeps saying usb device not recognized every like 5 seconds when my phone is connected and in bootloader. Is that suppose to be like that?
Darkpsych0 said:
Awesome thanks but question. my computer keeps saying usb device not recognized every like 5 seconds when my phone is connected and in bootloader. Is that suppose to be like that?
Click to expand...
Click to collapse
I will say it is okay as this happens to my PC as well. The files still transfer and CWM flashes through fastboot as well.
Sent from my A500 using XDA Premium App
Mmk. I downloaded ROM Manager but everytime i start it up it says "You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su/" or "system/xbin/su"
I have the file on the root of the sdcard and im pretty sure i rooted it with revolutionary and installed CWM as well.
Ok... Dumb question... where do we find the fastboot and adb zips to install on the C drive??
I have gotten thru step 8 and failed whentrying to install CWM. I manually installed it with step 9 and it said finished. Step 10 says to select recovery but it is not listed. I rebooted to see if that would work but it didnt. Where did I go wrong?
EDIT: Actually it did work just was trying to hard. Thanks for the great instructions.
@ Darkpsycho0
try installing busybox from the market and give it a try again.
@PacerguyDon
The links are in the OP.
It's next to the one that has the img file as well. There is only one zip file and it contains both items in it.
@Flightmed
Power down, and get back into HBoot. You will see the following options:
Fastboot
Recovery
Factory Reset
Simlock
Hboot Usb
Image CRC
The second option (Recovery) is what you want.
EDIT: Glad you got it working!!!
Sent from my A500 using XDA Premium App
Got it... thanks, Found it a few minutes after posting
PacerguyDon said:
Got it... thanks, Found it a few minutes after posting
Click to expand...
Click to collapse
It happens...we get so excited that we tend to overlook the obvious. Kind of like my wife...I love her to death and I love to make love to her but I overlooked the obvious that she is also crazy. Oh well...
Sent from my A500 using XDA Premium App
Busybox said "Root not found! The su binary was not found on your phone." -_____-
Thinking about it and looking back...I didn't complete the instructions on applying root. I apologize to you and everyone else.
When you have CWM installed, open it up through recovery. Next, as long as you copied the signed zip file to the root of your sdcard, select "Install Zip From SDCard" (5th Option).
Select "Choose Zip from SDCard" (2nd Option)
Select the zip file (su-2.3.6.3-efgh-signed.zip)
Choose Yes and wait. Once done, reboot and you should be good!
Again, I apologize. I will update main post asap!
Sent from my A500 using XDA Premium App
That worked.. no more error thanks. I was about to throw my phone across the room especially since while i was waiting for replies I was trying to just install new themes but can't get Astros to work with the apk files correctly. -_- (still can't)
I'm already rooted via 2.2 but this is a great guide for the truly n00b.
Should be seeing lots of new members posting in the development section soon ;!)
Post One: Unlocking and Rooting
Post Two: Installing Roms / Kernels / Tweaks
Post Three: Panic Section / FAQ / Miscellaneous
Unlocking The Bootloader And Obtaining Root
*This part of the tutorial is geared towards Windows users. I have a windows machine and will post instructions only on methods I personally have tested. This guide will assist other users. Once we unlock and root your device: this guide will be relevant to everyone.*
Time required:
20-40 minutes.
Setting up ADB for our device:
Download the AndroidSDK onto your computer.
Note: Google changes their mind every other week as to if this will be distributed as a .zip or an .exe. If you get an .zip file, simply extract the contents to your C:\ drive. For an .exe install it like you would any other program, but set the path directly to the C:\ drive when the installer asks.
Or...you can use this page to download the "ADB for Dummies AIO App."
This will automatically install ADB for you to your C:\ directory. It's very very simple this way.
If your platform-tools folder doesn't have a fastboot.exe, place this fastboot.exe file in your C:\android-sdk-windows\platform-tools (or possibly simply called tools, if you set up ADB ages ago) folder.
Now you have ADB installed! Congratulations.
Unlocking the Bootloader:
***NOTE***
This will perform a factory reset on your device. You'll lose all applications. You'll lose everything. Even the data on your SD Card! Backup your SD to your computer BEFORE performing this. There is a method for backing your applications up, detailed HERE.
Get the drivers:
Uninstall any previously attempted drivers if they don't work and move to the next.
Samsung's website has a download here under "Manuals & Downloads > Software."
Option Two: Navigate to the "Device Manager" (Control Panel > Device Manager) in Windows and Select the android device. Open the properties and select the "Install Driver" option. Pick the driver with "Install from disk." Ignore any warnings about the driver not being signed properly.
PDAnet's drivers may work if the above options don't. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
While that is downloading, on your Galaxy Nexus: turn USB debugging on.
This can be found in Settings>Developer Options>USB Debugging
Once the drivers are installed, navigate to the C:\android-sdk-windows\platform-tools folder on your computer.
Hold shift and right click. Select "Open Command Window Here."
On your phone: turn USB Debugging On. This can be found in Settings>Developer Settings.
Plug your phone into the computer. Now in this command window type:
Code:
adb reboot bootloader
(Hit Enter)
Your phone should now boot into a screen with a green android with his chest exposed.
Type this:
Code:
fastboot oem unlock
(Hit Enter)
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Your phone will ask if you want to unlock it. Select "Yes" by using the volume keys and use power to select it.
Now, navigate to "Recovery Mode" with the volume keys. Use power to select.
A screen with another Android will pop up. Press Volume Up and Power at the same time.
Select Factory Reset. This process may take a few minutes. Be patient and let it work.
Once finished, select "Reboot."
Your phone is now unlocked!
Obtaining Root Access and Custom Recovery:
Turn on USB Debugging in Settings>Developer Options>USB Debugging.
Download the following:
SuperSU (CWM .zip)
CWM (Pick the version for your device [GSM/SPRINT/VERIZON])
Place the recovery-clockwork-VERSIONNUMBER-toro.img (or the recovery-clockwork-VERSIONNUMBER-toroplus.img if you're a Sprint user. Or the recovery-clockwork-VERSIONNUMBER-maguro.img if you're a GSM user) file into your C:\android-sdk-windows\platform-tools folder.
Put the SuperSU.zip on your phone.
Open another Command Prompt if it isn't still open. (Navigate to C:\android-sdk-windows\platform-tools and shift + right click. Select "Open Command Window Here.")
With your phone plugged in type:
Code:
adb reboot bootloader
(Hit Enter)
And wait for your phone to boot into the android again.
Now type:
Code:
fastboot flash recovery IMAGENAME.img
(Change the file name to the correct file name and Hit Enter)
Once that is finished: select the "Recovery Mode" option again on your phone.
You should get a new recovery menu here. Select "install zip from sd card" and "choose zip from sd card."
Find the SuperSU.zip that you transferred earlier and select "Yes" to installing.
Navigate back to "Reboot" and reboot your phone.
You're now rooted!
However, ClockworkMod Recovery won't continue to load after this.
To fix this, find "Rom Manager" from the market. (The free version is fine.) Use the "Flash ClockworkMod Recovery" option.
If your recovery still doesn't stick around after a reboot, you have another couple options. Find a file explorer that allows root access, such as Root Explorer. Use this program to rename /system/etc/install-recovery.sh to /system/etc/install-recovery.bak. You'll need to mount the system as r/w to do this. Root Explorer provides a button at the top to do so.
Or, you can do this completely manually by firing up ADB again and running a few commands:
Code:
adb shell
(Hit Enter)
Code:
su
(Hit Enter)
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
(Hit Enter)
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
(Hit Enter)
Congratulations!
Your phone is now unlocked, rooted, and has a custom recovery!
Continue reading the next posts for info on getting custom roms, kernels, tweaks, and more!
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***
Thanks:
Google, for making Android a reality.
VanillaTbone, for the ADB AIO app.
Droid-Life, for a previous guide that I used as an outline while writing this one.
Efrant, for posting about a bootloader locking utility without USB.
ClockworkMod team, for being a part of making our phones as awesome as they are.
The assorted developers, who continue to push out amazing material for us to use.
The awesome community, for endlessly supporting both Android itself and its users.
Installing Custom Roms Kernels and Tweaks
All of the instructions below require your bootloader to be unlocked. Please follow the guide above and return here when you're done.
Backing Your Files Up:
Time required:
15-25 minutes.
Making a Nandroid
The first thing you're going to want to do is back up your phone's entire system. This is done by making a "nandroid."
To do this, boot into ClockworkMod Recovery. To accomplish this: Turn your phone off. Once it is completely off: hold both volume buttons and the power button until the Android with his chest exposed is displayed. Navigate to the "Recovery Mode" option and select "backup."
This will take some time. Be patient and let it finish. This process is important! You should always have a recent nandroid available on your device.
Backing Your Applications Up
Install Titanium Backup from the market.
Open Titanium Backup. A Superuser request should pop up. Allow it. Note: if Titanium Backup then says it failed to obtain root access; press the menu button and select more>reload application.
Press menu>batch. Select "Backup all User Apps." Select all and "Run the Batch Operation."
Let the process complete. This may take quite some time: depending on how many applications you have installed.
You can now backup your Text Messages, Bookmarks, and WiFi addresses with Titanium Backup as well.
Press Menu>Backup Data To XML to do so.
Backing Your Contacts Up
Note: This process may or not be useful to you. The Google servers should automatically import any contacts you have stored back whenever you install a new rom. Also note that Facebook/Google+/etc contacts will need to be synced again through their respective applications.
Open the Contacts application.
Press the Menu button.
Select import/export.
Export to storage.
Installing A Rom (Or Kernel/Radios/Tweaks/Themes/etc.)
Time Required:
5-10 minutes.
Note:
Follow the guide above about backing your phone up before attempting!
This guide will also work for flashing kernels/radios/themes/tweaks/etc. Simply ignore the part about wiping data and wipe whatever the thread says you should. You only need to restore data after a rom install.
Find a Rom You'd Like To Try:
Verizon Galaxy Nexus
Sprint Galaxy Nexus
GSM Galaxy Nexus
Download the rom you'd like to try on your device.
Most roms also require you to install "gapps" as well.
You can find the correct ones for the rom you're using in the rom thread.
Make sure the Rom and Gapps are on your SD card.
Now, open Google Wallet (if you have it installed) and press Options>Settings>Reset Google Wallet. This will prevent the "Secure Element" errors some users have experienced.
Boot into ClockworkMod Recovery by turning your device completely off. Hold volume up, volume down, and power until the green Android with the open chest is displayed. Navigate to "Recovery Mode" with the volume buttons and select using the power button.
Remember to have a recent nandroid before continuing!
Navigate to "wipe data/factory reset" and select it. Select "yes."
Wait for the process to complete. This may take some time. Be patient!
Once complete: Navigate to "Install Zip from SD card" and "Choose zip from SD card."
Find the rom's .zip and install it. Once that completes install any applicable gapps' .zip.
Select the "Reboot" option.
Congratulations! Your phone should now boot into the custom rom!
Follow the prompts to re-activate your phone.
Restoring Your Applications / Contacts / Nandroid
Time Required:
5-15 minutes.
Restoring Your Applicaions
Install Titanium Backup. Note: you may want the pro key. If you have it, you won't have to manually click "install" on each application. The process is completely automated. Open Titanium Backup (grant root access. If titanium says it failed to obtain root access, press menu>more>reload application). Press menu>batch>restore missing apps with data. Now, here you have a choice to make. Do you want a completely clean install? Select "app only" and run the batch operation (Deselect Google Wallet first. We don't want to risk restoring wallet in any way. Install it manually through the Play Store.). Do you want all of your application data (saved games/settings/etc)? Select "app+data" and run the batch operation (Deselect Google Wallet first. We don't want to risk restoring wallet in any way. Install it manually through the Play Store.). This MAY cause you problems or it may not. Personally, I often restore application data and seldom run into any trouble. If you do find that restoring data caused problems, follow the guide above to re-install your rom and restore without data. This process will take some time. Be patient (I'd suggest turning your screen off so the screen doesn't burn, but that's just me.) It will vibrate upon completion.
You can now restore your Text Messages, Bookmarks, and WiFi addresses if you backed them up by pressing Menu>Restore Data From XML.
Note:
Overclocking/CPU tweaking applications should never be restored with data. Simply deselect it from the list.
Facebook/Haxsync/Google+ may have problems restoring your contacts when installed through Titanium Backup. Simply uninstall and reinstall through the market (and be sure to log in and select to sync your contacts again).
Also, if you have NFC Task Launcher successfully launching Tasker tasks with your stickers: they may not immediately work.
Through my testing, it's as simple to fix as uninstalling NFC Task Launcher and Tasker. Restore Tasker first. Then restore NFC task launcher.
Restoring Your Contacts
If google fails to restore your contacts (not facebook/haxsync/google+/etc) you may import them manually if you backed them up.
Open the contacts application and press menu>import/export>import from storage.
Restoring A Nandroid
If your phone is acting funny or won't boot...restore a nandroid from a previous rom or working set-up.
You may also use a Nandroid to switch back to a previous rom if you decide you don't like the one you're on.
Do this by booting into ClockworkMod Recovery (hold volume up, volume down, and power while your phone is off and navigate to "Recovery Mode").
Simply select "restore" and find the most recent (or relevant) backup.
This process will take some time. Be patient and let it complete! Once done, select "Reboot."
Note:
Nandroids are stored in the "clockworkmod" folder on your SD card. They take up quite a bit of space. ALWAYS have at least one recent one on your SD card. However, since these are huge files: you may like to delete old ones to save space. You must delete backups by booting into CWM and navigating to Backup and Restore>Delete.
Important Notes About Restoration
I outline the method of using Titanium Backup above for a reason. Restoring system applications and data is the most common cause of problems on custom roms. For this reason, always ONLY restore "missing applications" from "user applications" that were backed up when restoring onto a new rom. Every time you restore system data or applications a narwhal sodomizes your favorite childhood cartoon. This is FACT.
Installing Alternate Custom Recoveries
If you find a custom recovery (such as the touch-recovery options) that came as a .img file:
Use these instructions to flash. Plug your phone into the computer. Open up ADB. Move the .img to the C:\android-sdk-windows\platform-tools folder.
Type the following:
Code:
adb reboot bootloader
(Hit Enter)
You can also manually boot to the bootloader by powering off and holding volume down, volume up, power buttons until the green Android with his chest exposed is displayed.
Then type:
Code:
fastboot flash recovery FILENAME.img
(Replace the file name with whatever the .img is called and Hit Enter).
Wait for the process to complete and reboot.
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***
Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu). Navigate to recovery and select it with the power button.
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.
Code:
adb push NAMEOFZIP.zip /sdcard/NAMEOFZIP.zip
(Hit enter)
You may have to reboot recovery to get the file to show up. Now follow the guide above for flashing a rom to get you booting again.
Did you install a tweak that modified only a file or two on your phone? (Find this out by opening the .zip and looking in the folders (ignore META-INF). Good news! We MAY be able to recover you completely. If this doesn't work...you'll have to follow another method.
Get your phone into fastboot (the boot-menu that allows you to select recovery/reboot/etc). Navigate to recovery and select it. Start up ADB. Pull the files that were modified out of the stock rom's .zip (using whatever tweak you were installing as reference to find what was changed) that you're on into the C:\android-sdk-windows\platform-tools folder. Now we're going to push these files onto your phone...replacing the tweaked ones and hopefully getting you booted again. Use this code, but change the values of the file name and where it should reside. This is only an example!
Code:
adb shell
(Hit Enter)
Code:
su
(Hit Enter)
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
(Hit Enter)
This will mount your system so you can write to it.
Code:
exit
(Hit Enter)
This should exit shell and allow the use of adb commands again. You may need to type it a couple of times (until the #_ changes back to the platform_tools> prompt).
Code:
adb push framework-res.apk /system/framework/framework-res.apk
(Press enter after each file that you need to replace).
Note: This last option probably won't work. I'd just skip over it unless you're absolutely adamant about restoring your current setup and want to try everything possible.
Q: I want my SDcard files from my phone...but I'm in a situation where I need to flash stock images! This will erase my SD content. What can I do to save it?
A: Do you have a custom recovery installed? If not, download a custom recovery from post one in this guide and flash it using those instructions. You'll need to be in a custom recovery in order to obtain ADB access without booting your phone. Boot into recovery (With phone turned off: hold Power and Volume+ and Volume- until the bootloader pops up and navigate to "Recovery"). Run the command:
Code:
adb pull /sdcard/ /SDCARD/
(Hit Enter)
This will put all of your files into a folder called "SDCARD" in your C:\ drive. Keep in mind that this will take a LONG time. Maybe a couple of hours.
To restore once you're booting again:
Move the "SDCARD" folder you created from your C:\ drive to the platform-tools folder. Then input:
Code:
adb push SDCARD /sdcard/
(Hit Enter)
Q: How do I make an "ADB Backup?"
A: An ADB Backup will backup your phones data (applications and their settings). Follow the guide HERE about ADB Backups.
Q: My phone gets really sluggish and often turns off or reboots on its own.
A: Without knowing anything about your situation...I'd say you either have severely bad data somewhere or some bad kernel tweaks. Use the rom install guide above, paying close attention to the part about backing up and restoring if you haven't already. In the case of a kernel problem, you're likely undervolting too low. Restore the stock kernel values and see if your problems subside.
Q: My phone screen won't turn on! This requires a battery pull to fix.
A: This is called a "Black Screen of Death" or BSOD. This is generally due to using a governor such as InteractiveX or HotplugX or possibly undervolting your device too low. Change governors or up your slots a bit.
Q: My phone is doing really weird things. Regardless of kernel/rom and even if I don't restore any data at all! Either that or I simply cannot boot up! My phone is possessed no matter what I do!
A: Razorloves has made a wonderful guide on restoring your Verizon phone back to stock. You can find it Here.
Shabbypenguin made an ODIN guide for Sprint users located Here.
Evostance made one for the GSM users, found Here.
Verizon/GSM images can always be found Here in the case that the above guides aren't updated.
Change the file names in the above guides, and you'll be good to go. *At the time of writing: Sprint images not available directly from Google.*
Q: My USB port is broken. How can I return to stock and re-lock my bootloader?
Follow the instructions in THIS post.
FAQ
Roms/Kernels
Q: What is the best rom?
A: The "best" rom is a matter of opinion. Do you like a certain customization and can't live without it? Use a rom that has that option.
Q: What is the best rom for battery life?
A: Roms themselves really shouldn't impact your battery all that much. They can have an impact, but if you're really looking for better battery I'd suggest swapping kernels or tweaking yours.
Q: What is the best rom for stability?
A: All of the roms out are "stable." They may have options that don't work correctly, but generally: this is user error. If you follow my advice on installing a rom, you'll end up with MUCH fewer bugs.
Q: What is the best kernel?
A: The best kernel is a matter of opinion. Some users may love one, while others swear by another. Find one you like and tweak it accordingly.
Q: How do I tweak a kernel for better battery?
A: Generally, you'll want to either change your governor and or undervolt and or underclock your kernel. This is done either by using SetCPU or similar apps, or with an option in your rom (usually labeled "performance" or something similar). Take note: extremely high/low voltages may cause instability. Never "set at boot" until you've thoroughly tested the options you've set. Testing includes low strain (like turning your screen off for an hour) and high strain (like playing a game for an hour) scenarios. To be extra safe: run the values for a couple days before setting them at boot. Follow the users ideas in the kernel's threads for some guidelines. However, remember that not all values will play nicely with all phones.
Miscellaneous
Q: Why does my phone perform so bad on benchmarking tests?
A: This depends on what you define as "bad." Does your phone feel fine? Ignore it. If your phone is really sluggish...you're running bad kernel settings or have bad data somewhere. That being said: our phones aren't going to be FANTASTIC with these benchmark tests. Sorry, but they aren't. We have a huge screen. And huge pixel density. And our GPU isn't the greatest of greats. This isn't bashing on the nexus at all. I'd rather have a phone that performs in every day use than a phone that gets a "FANTASTIC" benchmark but feels groggy when I perform simple tasks.
Q: How can Verizon users get Google Wallet?
A: Scan this with Google Goggles. Open the link with the Play Store.
Q: Why isn't Google Wallet working at [store]?
A: I'm not sure if it's a Google Wallet problem, or a problem with the terminal. But I personally struggle to find a terminal that consistently works in my area. Something that has generally worked for me is to open wallet and go to Options>Reset Google Wallet. You must then re-add any cards you had.
Q: Does my ass look good in these shorts?
A: Yes.
Neat Ideas / How to Show Off the Galaxy Nexus
-Get some NFC stickers. Tagstand has them available.
You can use these to make your phone perform certain tasks when you touch the sticker. Use NFC Task Launcher to define the tasks. These are capable of doing simple things like muting your volume to the more complex like turning on Tasker tasks that do things like auto-reply to text messages while you're at work.
-Do you have any suggestions? Submit them below!
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***
Thanks for the great guide!
I have a few questions. What are kernels? What do they do? Can I have a bad kernel and ROM combination? I'm currently using AOKP build 27. What are some good kernels you would suggest? Should I save my current kernel? How would I go back to my current kernel?
Are BAMF and CM9 only for the CDMA GNex? They both say Toro and isn't that the CDMA version and Maguro is the GSM?
Tks man it was easy and smooth, now i´m rooted rocking cm9 on my Galaxy Nexus!!
3bs11 said:
Thanks for the great guide!
I have a few questions. What are kernels? What do they do? Can I have a bad kernel and ROM combination? I'm currently using AOKP build 27. What are some good kernels you would suggest? Should I save my current kernel? How would I go back to my current kernel?
Are BAMF and CM9 only for the CDMA GNex? They both say Toro and isn't that the CDMA version and Maguro is the GSM?
Click to expand...
Click to collapse
Kernels are the base of your phone.
They are the "engine" as far as software is concerned.
Bad Kernel/Rom combinations...kind of.
Some features may be removed from kernels. Like the ability to use the color control built into CM9. But generally, no. Other than hard-linked features built for the rom and supported by the kernel, no. I've yet to find any other than the CM9 reference I made.
Going back is as simple as re-flashing your kernel.
Remember: turn of any CPU changing apps like SetCPU or Rom-specific "performance" features before switching. You can then re-evaluate your settings.
Bamf is toro only still, I believe.
http://download.cyanogenmod.com/?device=maguro
Maguro cm9 (gsm).
Oh...
And bump for ze sake of easy access.
Wish I could get this stickied <_<
agreed this should be stickied...an a read this 20 times should be applied before posts can be made.....Oh and thanks for this it will be a one stop shop as it progress's.....
Awesome guide. Needs to be stickied. Also, I agree, my ass does look good in these shorts...
Sent from my GSM Galaxy Nexus using XDA Premium
beans_p_ said:
Awesome guide. Needs to be stickied. Also, I agree, my ass does look good in these shorts...
Sent from my GSM Galaxy Nexus using XDA Premium
Click to expand...
Click to collapse
Le' bump.
Huge props, this is fantastically written and very in depth. If I had never flashed before this would be brilliant. Thank you for your work mate excellent job
J
Sent from my Galaxy Nexus - AOKP M4 - Franco M1
Thanks sir!
Another bump.
And I'll continue to do this until this is stickied.
It's straight stupid to not even have ONE stickied thread about the basics...
Can't describe how fantastic this guide is; it should be stickied in both the general and the development section.
If it isn't too much trouble, it would be awesome if you could put the steps to renaming the recovery.sh so the clockwork mod sticks and perhaps to reverse it (if I remember this right).
SovereigN7 said:
Can't describe how fantastic this guide is; it should be stickied in both the general and the development section.
If it isn't too much trouble, it would be awesome if you could put the steps to renaming the recovery.sh so the clockwork mod sticks and perhaps to reverse it (if I remember this right).
Click to expand...
Click to collapse
Actually, I would include that...
But flashing recovery through rom manager works as well.
And I'd rather keep it noob-friendly.
I follow a forum where they said to rename that...and there are like 15 pages of people asking the same questions as to why terminal/adb aren't working.
Fixed wording of "shift" showing as "****" lol.
And...le bump.
@Jubakuba You might want to add the link for the recovery image for maguro as well. Your instructions only have toro in there! Beginners may get stuck on that.
ankushkatari said:
@Jubakuba You might want to add the link for the recovery image for maguro as well. Your instructions only have toro in there! Beginners may get stuck on that.
Click to expand...
Click to collapse
Look again, it's there.
Thanks though!
Edit:
Upon checking to make sure I wasn't wrong...
The link should have appeared next to the CDMA for simplicity.
So I updated.
This was initially a RootzWiki CDMA forum post...
Had to be edited for here a bit...and the merged CDMA/GSM forum here makes it a bit hard.
Thanks!
Awesome job on this Jubakuba, thank you for sharing it. Stickied it is.
(You can quit bumping it now )
xHausx said:
Awesome job on this Jubakuba, thank you for sharing it. Stickied it is.
(You can quit bumping it now )
Click to expand...
Click to collapse
Lol, sorry
And thanks!
thanks, I had no clue about tags, wish they worked with phone off.
That is a very good guide by the way. Wish I had that when I did my phone but I had a great guy help me out. So I was lucky. Thanks for this!
GALAXY NEXUS - SUPPORTS ALL AVAILABLE VERSIONS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.4.1 [05th Oct 2015]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
ChangeLog:
ToolKit v1.4.1 (05th Oct 2015)
+Added new upcoming devices to device selection screen
+Main files now signed with Digital Certificate to ensure files are original and safe
+Added file checker after device selection to check needed files are up to date
+Updated UniversalAdbInstaller for Windows 10 compatability
+Added driver installation option at startup for new installs
+Updated ToolKitClean.exe to allow users to update the main ToolKit.exe file to latest available version without having to download/install the whole ToolKit again (like when a new device is added or files/drivers updated)
+Improvements and minor bug fixes
+Installer now give option for Fresh Install (removes any existing device files) or Upgrade (to just update base files)
--------------------------------------------------------------
USEFUL INFORMATION
How to get into your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Down' and 'Power' buttons to boot the phone into FastBoot Mode
How to get into Recovery
1. First boot into FastBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery
Show the Menu in the Stock Recovery Screen
1. Hold the Power button and keep holding as you press the Volume Up button quickly. The blue recovery menu screen should pop up.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
Manual Rooting Instructions for Galaxy Nexus
UPDATES:
VIDEOS:
Frequently Asked Questions:
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (e.g removing system apps).
From Google:
Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
----------------------------------------------------------------------------
Q. What is FASTBOOT?
Fastboot is 2 things. It is a mode on the phone, which looks a little like Bootloader. You can access it by holding 'Volume Up' and 'Volume Down' whilst turning on the phone.
It is also a way of flashing radios, recovery, boot images and system images in a command line method from a PC much like adb.
----------------------------------------------------------------------------
Q. I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh. Now when you flash CWM Recovery it will NOT be overwritten after a reboot.
OR you can use the ToolKit to rename the files (root access needed).
----------------------------------------------------------------------------
Q. I want to send my phone back so I need to flash a stock rom and relock the bootloader
1. Download, install and run the Google Nexus 4 Toolkit.
2. Install adb/fastboot drivers (if you havent already done so)
3. Option 9 to download a Google Factory Image.
4. After it finishes downloading you will be given the option to flash the image to your tablet. Do this.
4. Let the phone reboot, then shut the device down and reenter fastboot mode (or boot to fastboot mode via the Reboot Screen in the ToolKit).
5. Option3, 2 to relock the bootloader.
Your internal storage will be formatted and data and cache wiped. Your tablet will now be back to an out-of-the-box FULLY STOCK state and ready to send back.
----------------------------------------------------------------------------
Q. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.
Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).
----------------------------------------------------------------------------
Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.
The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton) will pick it up as potentially harmful when it is not. They will pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
----------------------------------------------------------------------------
Q. The ToolKit recognises my tablet in adb mode but not in fastboot mode (or other way round).
Open the Device Manager on your pc and then boot your tablet into fastboot mode or adb mode (dont plug the usb cable in yet). Make sure USB debugging is enabled on your tablet in settings, developer options. Plug the cable in while watching the Device Manager and determine which item is added to the list with the device plugged in. Once you have found it right click on the item and select update driver. Select 'browse my computer' from the list and then browse to the 'drivers' folder in the ToolKit folder (wherever you installed the ToolKit to). Make sure sub folders is ticked and click next. Hopefully the driver will be picked up and installed.
You can check if a driver has been installed by looking at the top of the Main Menu in the ToolKit while in fastboot mode and adb modes. If a serial number is displayed in each mode then it will work fine.
----------------------------------------------------------------------------
Q. Can I back up my apps before unlocking the Bootloader so I don't lose everything?
Performing an APPS BACKUP (option2, 1) will backup all apps that were installed after you first used your device. This will include any associated user data (such as settings or high scores for games) and apps you installed from Google Play Store. Just follow the recommended options and remember to turn your phones screen on before starting it as you need to confirm on your screen.
This option will NOT require your bootloader to be unlocked first.
You can also backup your Internal Storage without unlocking using option 2, 3 from the main menu. This will backup anything you store on your Internal Storage such as game data, music, videos. This is just pulled from your /data/media folder so you can view or edit the files on your pc after they have been pulled.
You can then unlock the bootloader (wiping your device) and retore the apps (option 2, 10) and Internal Storage data (option 2, 11) after doing whatever you want to with your device.
The only thing you cannot do with the ToolKit is to save the system settings but some of those are backed up by google if you chose that option when turning your device on the first time.
----------------------------------------------------------------------------
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.
----------------------------------------------------------------------------
Q. I cannot find Developer options to Enable USB Debugging
With Android 4.2 google have thought it would be funny to hide the Developer options screen in the Settings. This means you cannot enable usb debugging to communicate with your device. To show the Developers options screen do the following:
Goto Settings, About tablet and tap your finger on the the 'Build number' text at the bottom 7 times (not too fast).
When you have tapped 3 times you will be given a countdown of taps until you become a 'developer'.
Once you are told you are now a developer you can go back to the Settings screen and can see Developer options.
You can now go into Developer options and enable usb debugging.
----------------------------------------------------------------------------
Q. I tried to enter the code for the professional version but the Toolkit says the code is incorrect
Make sure the code entered is for the correct Toolkit being used.
You need to make sure you start the Toolkit with the toolkit.exe file when activating and not the tkmain.exe file so the settings can be initialised or the code will not be accepted.
Also make sure you enter the code correctly as the characters are case sensitive.
thnx man!
Works great. very easy and effective. happy to be rooted and have custom recovery and unlocked boot loader. thnc again for hooking us up so quickly.
Much recomended for all users. Easy and all the options and extras you'll need. Then just flash away..............
dangambino said:
Works great. very easy and effective. happy to be rooted and have custom recovery and unlocked boot loader. thnc again for hooking us up so quickly.
Click to expand...
Click to collapse
You're welcome
Can you just confirm if the cwm included in the ToolKit works with the Sprint phone as I have seen nothing about that working or not.
Mark.
mskip said:
You're welcome
Can you just confirm if the cwm included in the ToolKit works with the Sprint phone as I have seen nothing about that working or not.
Mark.
Click to expand...
Click to collapse
Works for me. Flashed it perm and the first thing i did was do a backup. No issues thus far. About to flash Team Win's to see what its all about. But yeah, its working.
whats option 5 rename recovery restore file and also i see manual wipes everything but does the tool kit? i assume the tool kit does too but would just like to clarify thanks.
Anon9mouz said:
whats option 5 rename recovery restore file and also i see manual wipes everything but does the tool kit? i assume the tool kit does too but would just like to clarify thanks.
Click to expand...
Click to collapse
With the non google stock roms there are 2 files that 'could' be present in the system folder. If these files are present and you flash a custom recovery image such as cwm or twrp then on your next reboot the stock recovery will be reflashed and you will lose your custom recovery. To stop this from happening I simply rename the 2 files if they are present so they cant do any harm. The exact commands I use are:
adb-toolkit shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p-old
adb-toolkit shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh-old
Click to expand...
Click to collapse
You can rename them yourself but you need root access and a root explorer.
Unlocking the bootloader will wipe EVERYTHING including the virtual sd card whether done manually or using the ToolKit there is no way round this. Even flashing a rom via odin with the phone still locked will unlock the phone and wipe it during the process.
Mark.
Skip I just sent you a message regarding the radio pull CMD
mskip said:
With the non google stock roms there are 2 files that 'could' be present in the system folder. If these files are present and you flash a custom recovery image such as cwm or twrp then on your next reboot the stock recovery will be reflashed and you will lose your custom recovery. To stop this from happening I simply rename the 2 files if they are present so they cant do any harm. The exact commands I use are:
You can rename them yourself but you need root access and a root explorer.
Unlocking the bootloader will wipe EVERYTHING including the virtual sd card whether done manually or using the ToolKit there is no way round this. Even flashing a rom via odin with the phone still locked will unlock the phone and wipe it during the process.
Mark.
Click to expand...
Click to collapse
O OK thanks for that. I see u mention odin I see it was used for everything with the epic 4g touch (SGS2) but I don't see that yet from this even tho there's a dl mode? Well thanks
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Anon9mouz said:
O OK thanks for that. I see u mention odin I see it was used for everything with the epic 4g touch (SGS2) but I don't see that yet from this even tho there's a dl mode? Well thanks
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Click to expand...
Click to collapse
I think people just prefer using fastboot I know I certainly do.
Mark.
Awesome, going to check it out ASAP. I hate not being able to install my root required apps (ES Explorer/Titanium/etc).
Just got my GNex yesterday, was only one of two that the store got.
LAYGO said:
Awesome, going to check it out ASAP. I hate not being able to install my root required apps (ES Explorer/Titanium/etc).
Just got my GNex yesterday, was only one of two that the store got.
Click to expand...
Click to collapse
You're lucky then I think there has been more demand for the Nexus than anyone thought and most places are out of stock.
Mark.
mskip said:
You're lucky then I think there has been more demand for the Nexus than anyone thought and most places are out of stock.
Mark.
Click to expand...
Click to collapse
I KNOW! I tried doing the preorder, but I had just dropped $4500 on getting my roof repaired & the funds were all tied up. By time I had em, the preorder had closed.
I half expected a line or something when I got there, but wasn't anyone. Asked for it, she said "hmm, let me check". Came back with one in her hand saying they only received two & mine was the last one.
I'm not taking time to set it all up until I root it . . . only to repeat it. I'm kinda befuddled about the lack of SD Card slot though. I didn't realize it didn't come with one until I had pulled the battery looking for where it mounted!
LAYGO said:
I KNOW! I tried doing the preorder, but I had just dropped $4500 on getting my roof repaired & the funds were all tied up. By time I had em, the preorder had closed.
I half expected a line or something when I got there, but wasn't anyone. Asked for it, she said "hmm, let me check". Came back with one in her hand saying they only received two & mine was the last one.
I'm not taking time to set it all up until I root it . . . only to repeat it. I'm kinda befuddled about the lack of SD Card slot though. I didn't realize it didn't come with one until I had pulled the battery looking for where it mounted!
Click to expand...
Click to collapse
Plus one on no sd
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Will be doing this when I get home from work! I was glad I picked my GNex up yesterday...it was the only one my store received! So I was quite happy...can't wait for more support on the sprint side.
I couldn't wait, I rooted after lunch. Getting Swype installed, first thing, EVERY time. I needs my Swype!
Then to get some apps on there. Connection sucks at work though.
Can someone please pull the radio for the sprint galaxy nexus
I did a n00b mistake and restored a google factory image for VZW on my Sprint Galaxy Nexus...
Any help would be greatly appreciated!!!
I may have spoke so soon. I'm getting error 7 assert fail when flashing a twrp recovery zip. Is that an issue with the recovery on the toolkit or the zip. I flashed a teerom and kernel with no issues though.....
Since the information for this device is so fragmented, I decided to attempt to keep it all in one (or a series of) posts. I aim to link to the original posts as well as outline what do to with your device from the time it leaves to box to running the latest and greatest modified rom or CM9 or whatever else is out there. I will not link directly to anything, rather I will link to the thread, and I very seriously recommend reading at least the post, if not the thread, before you begin ANYTHING.
This guide is a work in progress, it is not complete, and I will work on it bit by bit until it's completed!
Section 1: So its shiny and new...how can I MOD IT?
This will be assuming the new shiny toy in question is indeed an Acer Iconia Tab A100, this is not meant to cover any other devices. And, this is assuming it's coming with Honeycomb installed, in stock form. If its used, or comes with ICS, the next section will amuse you.
First thing most users that want to mod their devices do is root their device. Now, rooting is not unlocking, as carrier unlocking is not boot loader unlocking. Rooting a device allows you to access the system in a much more in depth manner, including read/write (R/W) access to the /system partition, among other things. It allows use of programs such as Titanium Backup (TB or TiBu) ROM Toolbox, overclocking or other clock setting utilities such as SetCPU or CPU Master for overclocking (if the kernel supports it) underclocking and undervolting.
So...how do I do that rooting thing? Well assuming you are running Honeycomb and are wanting to update to ICS plus root and unlock the bootloader, we will use the info from this thread Simple Root Method by ZeroNull to update you to ICS and then gain Root access on that new ICS install!
What about rooting Honeycomb? Well most users are already running ICS and prefer it, and those on Honeycomb are likely wanting to update to ICS, so I will leave this out for now. If I have the time I will come back and include the link for that as well.
Now, ICS is installed, and you're rooted, what else can I do? Well you can unlock your bootloader, and load up a custom recovery such as CWM or TWRP and using those, install Custom ROMS! For this, we visit this thread here Install unlocked bootloader by ZeroNull. Follow ALL directions in this thread for a fully unlocked bootloader!
Custom recoveries, what are they and how do I get that shiz? Custom recoveries, CWM and TWRP, allow the user to flash anything they want, provided its for their device and properly packaged. This included custom roms, some tools, and allows you to "wipe" various parts of the device's storage and backup/restore to a previous installation. Powerful, and dangerous, do not go pushing buttons to things you do NOT understand! Also, you MUST delete or rename /system/etc/install-recovery.sh prior to flashing recovery! This will restore stock recovery every time android boots, wiping out your custom recovery. The only time you want that file there is if you are using the crossix mount swap mod, which replaces that file with a modified version that leaves recovery alone.
Safe to do wipe:
Wipe cache, data, dalvik cache, system. Theonew also reports Flex and boot can be wiped as well as SD-EXT. This is not to be confused with External SD, this is a separate partition on your External SD card, wiping it will NOT wipe external SD, only what's installed on that partition, the rest is safe and requires a separate wipe.
If you wipe system you MUST install a new rom or restore from backup!
If you wipe boot please restore or install a new ROM before rebooting! Safety first.
Not safe to wipe:
Don't wipe anything else, and always install a new rom or backup after wiping system!
Never reboot system after wiping without first restoring or installing a new ROM!
Post 2 will cover custom recovery functions in more detail, for both recoveries.
Now that you have an unlocked bootloader, what can I do? Install that custom recovery! There is two flavors, CWM and TWRP, CWM available here CWM Recovery by ptesmoke. Follow the instructions in this post to the letter! Only attempt this after you have ICS, rooted, and unlocked the boot loader correctly! Next we have TWRP Recovery here TWRP Recovery by ZeroNull. Again, follow the instructions to the letter, and attempt only after ICS, root and unlocked boot loader are finished.
Ok, gots me some custom recoveries, what about custom roms? This is why we just did all that work, to prepare for this! Custom ROMs! I'll be listing some (all?) ROMs that you can use, besides stock HC and ICS.
The list in order of version, oldest to newest, updated to retired:
4.0.3
KEBBERSROM by Hardslog Stock based 4.0.3
Flex Reaper by civato ICS 4.0.3 Modified Stock
Green ICS by lgcmn & ZeroNull ICS 4.0.3 Modified Stock
4.0.4
KEBBERSROM SHELLSHOCK by Hardslog 4.0.4, based on A500 and A700 ROMs
Nightly Builds of CM9 by pio_masaki ICS 4.0.4
Aoikaze Modified CM9 by pio_masaki ICS 4.0.4
4.1.1
CM10 Preview builds by waydownsouth 4.1.1
4.1.2
Unofficial CM10 builds by pio_masaki (stock and modded, Phone UI and Tablet UI)
Jellytime Sosei by pio_masaki Jellybean 4.1.2
Cyanosaki_Flex by Hardslog
4.2.2
CarbonROM JB 4.2.2 Unofficial by pio_masaki
These are most of the ROMs. There are others that seem to no longer be in active development and are based on the old leaks that vache was kind enough to grab for us. Development is currently only active in the KEBBERSROM builds by Hardslog, and occasional updated in the CM10 builds by pio_masaki.
That ends Section 1, preparing for awesomeness, and Post 2 will continue with installing your new custom ROM!
Section 2: Recoveries and what they can do for you.
This section will cover recoveries and what they can do, and how to do it. I will be starting with TWRP, as I use that on all of my devices, and after that I will include a CWM section, as a lot, if not most, use that. They are similar in what they do, but different in where things are.
TWRP Recovery
Official TWRP for A100 by linuxsociety
This assumes you have already done everything in section 1, including installed ICS, rooted it, unlocked your bootloader, and installed TWRP custom recovery. Links for this information is provided in Section 1, in the post above.
First thing you should ALWAYS do when you enter recovery, before doing ANYTHING ELSE, is make a nandroid backup!
Getting into recovery: Depending on what ROM you use, this is done a couple ways. First is an AOSP ROM, like CM9/AOKP, which you can hold the power button, then select Reboot, then Recovery. In modified stock or rooted stock ROMs, this menu doesn't exist, you can either use an app like Quick Boot, and select recovery, or power off, then hold the Volume - key (closest to the rotation lock switch) and while holding it, hold power, once the acer screen comes up and starts saying Recovery kernel, release both and recovery will boot provided an update.zip is NOT on the root of your external SD card. This method works for any ROM.
Now I'm in recovery, what do I do? As I mentioned, make a nandroid backup before you do ANYTHING else! From the first screen (home screen) in TWRP select Mount. In mount you can leave everything alone and at the bottom will be two options with Circles. Select Using external SD Card for Backup. This will store your backup on your external SD card, never use internal SD if possible. After you select use external SD, press the Home button in the upper right corner. Now, back on the Home screen, select Backup. Double check the boxes checked are System, Data, Boot and Recovery. At the bottom is a nice little slide bar, slide that over and sit back. Takes about 4-5 minutes depending on how full your device storage is. This does NOT backup internal SD! After this is done, you have created a nandroid backup that when restored will put the system exactly how it was last time you used it. You can make multiple backups of multiple ROMs without issue, just however big your SD card is to hold them.
The restore menu, or the OOPS SAVE MEH menu is your best friend. This will restore you back to the last state your device was in for the backup that is restored. By default TWRP saves by date and time, however you can rename this with any file manager, never caused me any issues. Theonew reminded me of an MD5 issue that can happen on renaming backups, if this does happen, rename it back to the stock naming system to fix it. Generally I'll just append the ROM name to the front, so instead of 2012-6-14--18-25-01 it'll be CM9-2012-6-14--18-25-01. Make sense? That way to restore it in case of error, just drop the name. Easy. Theonew also did some testing, and confirmed that spaces in the folder name WILL cause MD5 errors and fail the restore, please use ONLY dashes and underscores (- and _ lol) in the folder name! To restore make sure you are on the Home screen, then select Restore. In the window you will see a list of your current backups, select one. Next screen has check boxes, make sure System, Data, Boot and Recovery are checked, then slide the bar to begin. This takes a bit, make sure you let it finish! Once done, your system will be at the last point it was used for that backup.
Advanced restore...I'm to lazy to reload and reset up my stuff after a ROM flash, so this is the fast and dirty way of doing it. If you flash a ROM and you don't feel like manually restoring your apps, you can uncheck System, Recovery and Boot, and leave only Data checked. This will restore your user installed apps and settings over the current ROM install. I don't recommend this for different ROMs, only for updates of the same ROM! Up to you but if you get alot of issues, you'll know why. After advanced restoring, go to the Home Screen and select Advanced, then Fix Permissions. Press Home again and select Wipe. Wipe Cache and Dalvik Cache, then reboot system.
Alright, enough already lets get our flash on! From the Home screen, select Wipe, then press on Cache, Dalvik Cache, Factory Reset, and System. Optional you can wipe Battery Stats if your battery seems off. Leave the rest alone. Once these are all wiped, go back to the Home screen, and press Install. The window on the left is your device folders, window on the right is contents of the current folder. I hope you remembered where your rom.zip is, because you select it here. Press on the zip for the ROM of your choice, then slide the bar to flash it. After that is done, select the left button Wipe Cache and Dalvik, then select Reboot system.
OK LETS ROCK THAT ROM! Woah, slow down scooter, there's a few things to do, or not do, first. After it boots, meaning it's past the boot animation and is sitting on the Welcome screen, set it down and leave it alone for 10 minutes or longer. Don't sign in, don't do anything, just leave it be for 10 minutes. If you can't think of what to do to manage the time you have to wait for awesomness of custom ROMs, read the thread of the ROM you chose. Set the thread for 50 posts and just read. After 10 minutes, hold the power key, and either choose Power off or Reboot, Reboot depending on ROM used. After it finishes rebooting (that was alot faster wasn't it?) you can go ahead and do the Welcome stuff, log in to Google, setup your device, download your apps, restore your apps etc. After restoring your apps (try not to restore app + data if possible, though I know games and stuff you'll want to) reboot one more time. After that second reboot, use the tablet as normal. From my experience this offers the BEST possible ROM usage, a vast reduction in lag, bugs, and oddness.
What else can I do with the TWRP Recovery? Well, the most useful tools are Backup, Restore (and advanced restore) and the wipe menu, plus fix permissions. Those generally can fix anything thats wrong. If you notice alot of lagging, FCs or general unruliness, wipe Cache, Dalvik Cache, and Fix Permissions. Another useful ability is ADB, which is beyond the scope of this section, but may be included generally in a later section. ADB can be used to repair otherwise bricked devices, and offers a very large amount of tools that you don't normally get to use in Recovery. Keep in mind ADB is powerful, and can quickly destroy your device, so please, be careful using it.
Placeholder for CWM Recovery section - coming soon!
CWM Recovery for A100 by ptesmoke
Section 3
Additional Recovery tools:
Blackhole Wipe/Nullifier by pio_masaki
These are tools I created to make wiping a little easier, but please read the post completely before deciding to use it! There are multiple versions, and they can and will wipe internal SD, as well as take up to 40 minutes to run (1, not all). Please ask questions if you have them there and I will help as best I can!
AROMA Recovery Touch Recovery
A touch file manger to be used in recovery, even on non touch CWM! Good for renaming backups as soon as you make them (I tend to forget afterwards and get confused by 6 backups with just dates). Also moving a downloaded zip from internal to external or whatever before running a system wipe, any number of things. Please read the post completely before using this tool! It can cause damage if not used properly and with care!
Kernels:
linuxsociety / godmachine's A100 OC Kernel
Plenty of extra balls thrown in for good measure, a good place to look if you like high benchmarks and plenty of extra goodies baked in. Available in a few flavors, with some GPU OC thrown in for good measure.
ezterry's A100 OC/UV Kernel
The only other option for a kernel that we have besides stock and CM9's included kernel. Excellent kernel, really wakes up the A100, allows up to 1.5 GHz for some extra umph and undervolting to help conserve power on our very weak batteries.
PRO TIPS:
The 10 minute rule:
The reason I mention waiting 10 minutes on first boot of a ROM install is this: Alot of things happen the first time the ROM runs, alot of scripts run, the kernel has to settle and search and move things, files are flying all over the nand. Think of a tornado in a cubicle. That's first boot for your device. Allowing it 10 minutes uninterrupted allows all of that to happen and settle down. The following reboot lets all that new info fire up from it's new home and continue settling in. After restoring and downloading apps, that reboot allows that new info to settle into it's new home and the system to catch up. This isn't device specific, rather a general rule of thumb for all devices. Does not really apply to restores unless something is changed.
Undervolting:
Undervolting on this device is only available on ezterry's excellent kernel. The following is a rough guideline of how to do it, and do it right:
Start small, don't just dump it -200 and expect it to work. For the time you're testing, make sure it is NOT set for boot. If something goes wrong you don't want it doing it everytime it boots, right? Go in small increments, -25 is usually OK. For now, don't overclock. Starting at 1 Ghz, lower every speed range down -25, and run the device for at least 10-20 minutes, normal use, hard use, benchmark, browse the web, watch a HD movie. If all is fine and its not lagging, freezing, force closing or heating up more then usual, move everything to -50, and repeat. My device freezes at -150 but runs stable at -145. Every device and chip is different, mine may do -145 yours may do -175 or only -50.
Overclocking
Overclocking is available on ezterry's bodacious (already used excellent) kernel, up to 1.5 GHz, and the CM9 kernel up to 1.4GHz. As with undervolting, this should be done in small steps and tested between to find your max. Generally 1.5 GHz is fine for every device, however all devices and chips are slightly different, and some may not be stable at it. Mixing undervolting and overclocking can be tricky, but following the steps above for undervolting you can find that sweet spot for your device.
Batteries and why they fail
This section is entirely my opinion, other's swear one way, other's another, but this is what I've concluded from multiple posts for this device.
Consider 10% to be 0%. There have been more then a couple posts that say they let their battery fall below 10% and they can NOT get the device to work properly again afterwards. I think there's a few reasons for this, and I'll explain them now. First, a lot of batteries tend to have some kind of breaker protection if the voltage drops below a certain level. This is to prevent damage to the cells, which it does, however we can't close that breaker to restore activity from the battery, IE, it's dead anyways. This threshold varies from one device to another, one battery pack to another, some can go to 0% and be ok, others can't. I say voltage level, because while draining the voltage can spike up, and it can also spike down, which can fall below this threshold even though it says you have 5% battery life remaining, and trigger the protection.
The acer does not seem to power on without a working battery. If the battery is "dead" it doesn't seem to boot. Its basically a brick until either the battery is replaced (by acer I would assume) or the motherboard is replaced due to some sort of damage causing this. Replacing the motherboard costs almost as much as a new unit, so at this point, just save up some more and buy a new one.
For this, I never go below 10% if ever possible. Even on my phones.
Another thing I try not to do is charge in bursts, or at random times. Basically, I plug in at 10%, then allow full charge to 100%, I don't charge in between those ranges, and I don't charge for periods less then 100%. So I don't plug in at 48% then unplug at 60%. I've learned this one from my Evo 4g, the battery was fantastic for months, then I started using the car charger to top off, and the battery life over the course of 2 weeks took a very noticable hit on overall life. I lost easily 4 hours a day usage on it. This on a phone and ROM combo that got me 16 hours a day.
Again this entire section is just what I've noticed and is purely my opinion, please do whatever you please with your device, it is yours after all!
ADB and Fastboot...is it really a faster boot?
No, fastboot isn't a toggle to boot at warp 9. Fastboot is a mode you can put your bootloader into for flashing the system for upgrades, repairs, mods, or general havok if you're not careful. The bootloader is what you see when you first turn on your device, that lovely Acer logo with the text up in the left corner (usually saying bootloader version and Unlocked Mode if unlocked, or nothing if it's locked). If you go into fasboot, it will say download usb protocol, so if you see that, you're in fastboot mode for whatever reason.
How do I get into fastboot mode?
Well you can do this in a couple ways, either Quickboot app (reboot bootloader), if you're on CM9, the power menu will give the option, or you can use ADB for it.
adb reboot bootloader
I'll explain some more about adb after fastboot, I know its odd, but one does have something to do with the other at times.
Once you've rebooted to the bootloader (device will turn off, vibrate, then boot to acer screen) you can then issue your fastboot commands assuming 2 things:
Acer USB drivers are installed and working correctly (if you use adb to reboot, then it is)
Your tablet is connected to your PC over USB.
Now, at this point, its up to you to do whatever you want, but BE CAREFUL USING FASTBOOT FLASH! It doesn't care or check what you're flashing, it'll just flash it. For example, I flashed CWM Touch recovery to boot once because I was distracted and mixed up the images for whatever reason. End result: Can't boot android. Why? Because boot was recovery, it only booted to CWM Touch recovery. Booting to actual recovery booted to TWRP, which was my previously installed recovery. I got it back easy enough once I figured out what I did wrong, but not all mistakes are reversible, or fixable!
General Fastboot uses and commands...
general layout goes like this:
fastboot (this is calling the command) flash (this is what fastboot will do) recovery (where it will send it to) recovery.img (the file it will send)
So, it looks like this:
fastboot flash recovery recovery.img
it will then flash whatever img to whatever partition you said, and let you know when it's done. You can flash any img to any partition, provided it fits, which means you do have to be careful about what you flash to where!
when you are finished with fastboot:
fastboot reboot
There are plenty of other commands, but the general basic use of fastboot is to flash a recovery or bootloader, so that is what I laid out above.
This section is hugely in need of improving, I know, but the guide in general is still rough, my apologies.
What about ADB?
ADB, or Android Debugging Bridge, can be used in System or in custom recoveries to interact with the device behind the curtain, meaning what you do isn't readily apparent on the device itself, unless you do something obvious like reboot it. ADB has a ton of commands, in particular in ADB Shell mode (you drop into the device shell itself, issuing commands from within itself, not from the PC).
Some random ADB commands:
adb reboot (where to reboot to) so:
adb reboot recovery
adb pull (what file to copy) /(where to copy file to) so for example, a recovery log to the adb working folder:
adb pull /cache/recovery/last_log recovery.txt
adb push /(file to copy to) /(file to send to device) so for example, placing that recovery file back into the device:
adb push recovery.txt /cache/recovery/last_log
Thats all the time I have for now, sorry in advance, I'm still working on all of this, I swear lol
Placeholder for additional tips and usage, some ADB stuff, and anything else I can think of.
Placeholder for Toubleshooting.
Placeholder for FAQS.
System Modding
justjackyl's Iconia A100 CM10 Setup & Use Tips/Tricks
A good guide to check out to try to get the most out of your A100 on CM10 (or any JB ROM like Sosei/black bean). A must read for those new to CM10/JB on these devices or in general. Not an outright mod, but a good source of information about some modding you should browse.
Hulu Flash Hack by NoSudo
What the Hulu Flash Hack by NoSudo does is allow you to use our android browser (setup according to the thread) to watch sites like Hulu to play on your android flash player. Its basic function is to scan for, then backup, then place a modified libflashplayer.so file. Setup with script manager and run at boot for best results. As always, read the thread for more information.
Mount Swap by crossix
What the Mount Swap by crossix does is pretty awesome, it mounts your external SD as internal, meaning your 32GB external SD card shows as internal, and is used for your apps, data, downloads, whatever, as if it was your internal SD. Internal SD is then mounted as external SD. It's operation is based on install-recovery being replaced with crossix's version. Instead of replacing recovery, it runs the mount swap. Requires Root, as the file is placed into /system/etc. Designed for stock/modified stock ROMs, it can be used with AOSP/AOKP ROMs by using script manager and setting it to run as Root at Boot. Please read the thread for the files and information on how to use it.
Adapted to ICS Build Prop Mods by patrick_spd4u adapted from crossix
What the Build Prop mods do is pretty basic, however can greatly increase the abilities of the A100, including faster boot times, more apps/games available for download in the Play Store, and tons of other stuff. Adapted from crossix's mods for HC.
Guide to 2 ways of running the crossix mount swap script, Acer based and AOSP/AOKP based
Direct paste from a post I made about this earlier...details using ES File Manager, however you can adapt it for any root file manager.
Using your tab, download the crossix mod zip file.
Unzip the file to get your epic mount swap mod by crossix, it can be unzipped anywhere.
At this point, I'm using ES File Manager but you can use Root Explorer or whatever. I'll be giving directions for ES.
Go into settings, scroll down and check the box for Up to Root.
Scroll a little futher down, same menu, and check the box for Root Explorer. Tap Yes, then allow when SU asks.
Now check the box next to Mount File System.
A little notice should pop up saying system is writable. If it fails at this point, you'll need to reroot, though it should work fine.
Press back, and go to where your crossix install-recovery.sh file is, hold your finger on it, and select Copy from the menu.
Press back and keep pressing it until you get to /. You'll see folders like acct, cache, config, d, etc.
Scroll down to system, and tap on it to go into system
Tap on etc to enter the etc directory.
You should now be in /system/etc, check up top there will be the address bar showing where you are.
You shouldn't have an install-recovery.sh file there, but if you do, long press it and select rename, then rename it install-recovery.bak.
On the upper buttons, select paste.
Now hold on the install-recovery.sh and select Properties, all the way at the bottom of that menu.
Next to where it says permissions, click Change
You will get a new window showing 3 rows of 3 colums of boxes with Xs.
Check the boxes so it looks like this:
XXX
XXX
XXO
Click on OK, then OK again, you should be back to the main ES window. Go ahead and hit home, or hit back over and over to exit.
Stock or Modified stock ONLY
Reboot the device by whatever method you prefer.
Once it finishes booting, wait a minute, then check your Settings>storage and your external SD card should show as internal. You only need to do this 1 time, it will continue to do this after.
AOSP/CM9/AOKP ONLY
Go to the Play store and download Script Manager(smanager).
After it installs, open the app then select Browse as root, Allow when SU asks, then click OK.
It will likely be listing /mnt/sdcard as your default directory, press the folder with .. to go back up until it says /
Click on system, then etc
It should now show /system/etc
Find your install-recovery.sh file, and it will open a new window.
Pay close attention here!
Right under the buttons that say Run Exit Edit Save are some icons,
Fav Su Boot Net Wick Ntfy
Press on Su and Boot, then click on Save.
Now exit smanager and reboot.
Wait a minute, then check settings>storage and your external SD should show up as Internal.
Don't disable smanager from running at boot! If you disable it, your script won't run. smanager must remain installed, or the script won't run.
Thanks to:
ZeroNull: For being one of the pioneers for getting our devices cracked open for our amusement!
ptesmoke: Also for being a pioneer in getting custom recoveries on our devices!
vache: For releasing the ICS leaks way ahead of schedule and hosting them for us to use and abuse!
civato: For releasing his Flex Reaper ROMs on our devices, his modified stock ROMs are still (IMO) the slickest available!
da-pharoah: For helping me understand how recoveries work a little better, allowing me to create Blackhole Wipe/Nullifier, and general encouragement for creating things for this device! (G2x and KF forums)
ezterry: For creating an OC/UV kernel that so far is the best EVER for any ROM on our device!
Theonew: reading ALL of that, and providing some nice info I missed and left out, and catching typos (Almost made it...)
crossix: that mount swap mod is just awesome, I never run a ROM without it!
NoSudo: creating a method to easily modify the system to watch HULU and other sites that normally won't allow it!
There's more I'm forgetting, I'll be adding more as I remember, I promise.
Even though I knew everything you posted, it was very interesting and I recommend everyone (even if you don't need it or already know) to read this guide. Its a marvellous read with some humor to keep you going. One thing though:
- You stated that its only safe to wipe "cache, dalvik cache, data, and system". Technically, this is not true. Flexrom and boot partitions are also safe to wipe (and for some roms for certain devices, the boot partition must be wiped for stable kernel performance, etc.). It's also a good idea to wipe sd-ext if you have it set up (in most cases). Once again, excellent guide (you even did a part of my job ).
Theonew said:
Even though I knew everything you posted, this is a brilliant guide and I recommend everyone (even if you don't need it or already know) to read this guide. Its a marvellous read with some humor to keep you going. One thing though:
- You stated that its only safe to wipe "cache, dalvik cache, data, and system". Technically, this is not true. Flexrom and boot partitions are also safe to wipe (and for some roms for certain devices, the boot partition must be wiped for stable kernel performance, etc.). It's also a good idea to wipe sd-ext if you have it set up (in most cases). Once again, excellent guide (you even did a part of my job ).
Click to expand...
Click to collapse
While sd-ext is safe to wipe, using factory reset wipes that for you, and I think, could be wrong, but cwm does it on data wipes. Part of why I missed it was I confused it with my phone, where wiping sd-ext bricks the phone, and also people mix it up with external SD. I'll add it in as its a very valid point, and I shouldn't let personal things interfere with the guide.
As for boot, our devices don't need that wiped and honestly asks for problems if someone doesn't restore or install a rom to cover it. I've never wiped it on any device, however I will also add that in as it is good info. I left it out of "safe" to prevent possible issues from wiping it.
I forgot about flex and I honestly don't know what it is for lol. Again thanks for reminding me and I'll add it in.
Of course I'm open to posts like these please give some input on what I missed or need to correct, I want this to be the go to guide for the a100 for anything needed!
Tapatalked from my Galaxy S II.
pio_masaki said:
I forgot about flex and I honestly don't know what it is for lol....Of course I'm open to posts like these please give some input on what I missed or need to correct, I want this to be the go to guide for the a100 for anything needed!
Click to expand...
Click to collapse
In your 4th to last sentence of the "Advanced Restore" section, you have a typo . Anyways, according to here: forum.tegraowners.com/viewtopic.php?f=10&t=149, Flexrom is "a partition on the nand that acer made to hold some proprietary apks and build information".
Oh damn almost made it without a typo...not bad for just running through all of that without really checking on it..other then it was english.
Corrections and additions added to the posts, thanks!
pio_masaki said:
Oh damn almost made it without a typo...not bad for just running through all of that without really checking on it..other then it was english.
Corrections and additions added to the posts, thanks!
Click to expand...
Click to collapse
One more thing - This occurred for one of my other devices, but the problem may still exist here. I haven't tried it with TWRP, but renaming CWM backups can cause a md5 mismatch error to occur. If this happens, simply rename it back to a date (in the default format).
I've never ran into that issue on any of my devices in CWM or TWRP, however I have heard of it occuring, definatly something I should add in there. Full of good catches tonight aren't you?
Awesome write up, thanks you guys!!
What about Zeronull's .014 v1.2 rom? http://forum.xda-developers.com/showthread.php?t=1574897
I'm still digging through all the threads for the ROMs, however I included the currently developed or recently released ROMs first, ZN has since released Green ICS, which is included already. I do plan to list every ROM, but it'll take some time to finish this guide up with as much info as possible, then go back and add things in.
pio_masaki said:
I've never ran into that issue on any of my devices in CWM or TWRP, however I have heard of it occuring, definatly something I should add in there. Full of good catches tonight aren't you?
Click to expand...
Click to collapse
I tested it to see if it occurs, and it turns out that it does. I made a backup with CWM, renamed it then tried to restore, and it immediately gave me the "md5 mismatch" error.
Theonew said:
I tested it to see if it occurs, and it turns out that it does. I made a backup with CWM, renamed it then tried to restore, and it immediately gave me the "md5 mismatch" error.
Click to expand...
Click to collapse
That is so weird I never have that issue cwm or twrp. I use es file manager..maybe why?
Tapatalked from my Galaxy S II.
pio_masaki said:
That is so weird I never have that issue cwm or twrp. I use es file manager..maybe why?
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
I renamed it using Root Explorer. Have you tried renaming them to something including spaces?
Theonew said:
I renamed it using Root Explorer. Have you tried renaming them to something including spaces?
Click to expand...
Click to collapse
No, as its a Linux based environment I use dashes and underscores never spaces in directory names. That shouldn't cause md5 fails because the md5 is based per zip not the folder name. If you could try an experiment and rename with es I'd appreciate it, and maybe with and without spaces. I'll try root explorer when I get home and see if it causes issues.
Tapatalked from my Galaxy S II.
pio_masaki said:
No, as its a Linux based environment I use dashes and underscores never spaces in directory names. That shouldn't cause md5 fails because the md5 is based per zip not the folder name. If you could try an experiment and rename with es I'd appreciate it, and maybe with and without spaces. I'll try root explorer when I get home and see if it causes issues.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Done. The error seems to only occur when spaces are used in the name.
Theonew said:
Done. The error seems to only occur when spaces are used in the name.
Click to expand...
Click to collapse
Thanks for taking the time to figure that one out, I've been testing a new rom on my phone plus a new test T20 kernel for ezterry and getting cm9 build 5 up, just kinda managed to forget that experiment lol
I'll have some time...maybe...to append that new bit into that section tonight. The "free" time has been spent trying to get aokp for the a100 but my lack of experience, random problems with the repos and devs ignoring my PMs its been going slow. And by slow I mean nowhere.
Tapatalked from my Galaxy S II.
Great read. Sorta like flashing for dummies. Thaanks for your work.
Sent from my HTC Glacier using Tapatalk
It's great to have all this information compiled in one location. Looking forward to your next installment. THX