Database Users

[TUT] Flashing your first A500 custom ROM

Well, flashing a custom ROM on our beloved Iconias became quite easy now thanks to developers on xda. Most of you are quite familiar with the procedure but there are still people that ask basic things all over the ROM developement threads. This is just a beginner's guide, an attempt to collect all the procedures and tools in one thread. Nothing of this is my work and I would like to say THANK YOU to sc2k, thor2002ro, Euclid's Brother, Chainfire, monki-magic, drellisdee, ezterry, Skrilax_CZ, gersma and all A500 developers for making this possible.
You will need the following: external SD card, root rights, unlocked bootloader (if you're on stock ICS), custom recovery and a custom ROM of your choice.
Well lets start by placing an SD card in the SD card expansion slot. Its file system should be FAT32!
*This is optional: To be sure it is recognized later in CWM, format it first with SD Formatter - a tool that can be downloaded from here. Use your home computer / notebook with a card reader for this procedure. Alternatively you can do this using an ANDROID phone.
1.ROOT
Root for Honeycomb 3.0.1 by monki-magic
original thread by Slowie911 here
1. Make sure usb debugging is turned on and unknown sources is selected in Applications settings.
2. Have a micro sd card inserted and turn the tablet on portrait mode and lock it with the switch to fix it in portrait.
3. Download and execute the attached apk. (i had to download from my comp and transfer to the tablet for it to work).
4. Once the apk is installed run the root procedure within the app which was installed
5. Wait and you will receive full root access.
Download Gingerbreak 1.20
Root for Honeycomb 3.1 by sc2k thread here
1. Goto Settings->Applications and enable "Unkown sources"
2. Download the attached APK file
3. Copy the file to your Iconia
4. Install the APK & start the tool
5. Click "root"
6. Enjoy
/IconiaRoot should work on both 3.0.x and 3.1/
Download Iconiaroot 1.3
Root for Honeycomb 3.2.x OTA
Unfortunately there's no dedicated rooting app yet developed for HC3.2. It also comes with a new bootloader. In order to get root you need to revert to an older version of Honeycomb first where Iconiaroot works. How to do that is explained in details in this thread
UPDATE: if you're on OTA HC 3.2.x then you can just update to ICS and use the method for rooting ICS - links posted below
Root for ICS 4.x.x OTA
Stock ICS Leak One-Click Root Tool by blackthund3r
or
Full root for A500 ICS 4.0.3 - Simple method, posted by ZeroNull
2. Bootloader
Since there are many new ICS custom ROMs and custom recoveries, please read in their dedicated threads if they require ICS bootloader. Some of the ROMs can recognize the version of your bootloader and load the proper boot.img during boot. In general - if you're on Honeycomb - you have HC bootloader. If you've updated OTA to ICS, then you have stock ICS bootloader, that is unusable for flashing custom ROMs and therefore you need the unlocked bootloader. A guide on how to install it read here - thanks civato. This thread links to a nice little piece of software (option 1) by gersma that can automatically do all the job for you - install ICS unlocked bootloader and custom recovery. Read and download here - AfterOTA by gersma
3.Custom recovery
original thread with clockworkmod recovery by thor2002ro here
1. Open Market app with your tablet and search for Acer Recovery Installer.
Acer recovery installer
2. Install it and then open it. It has ClockworkMod Recovery by thor2002ro rev1.3.4 built-in.
3. Select "ClockworkMod Recovery rev.1.3.4 by thor2002ro". Tap on install Recovery Image. A popup offering to backup current recovery image will appear. Surely, buckup! Thus you can restore your original recovery image in case of need. Then CWM will be installed. Once it is installed you can remove Acer Recovery Installer tool from your system if you want.
thor2002ro updated CWM to 1.7.3. You can download the zip from tegraowners.com. Later versions of his recovery does not meet GPL because of the "mini" kernel of his - sources not being released. It supports flashing both from internal memory and the external SD card. In order to update your CWM to this latest version, place the downloaded ZIP on your external sd card and update from your CWM by choosing install zip from sd card. Alternatively you can extract the recovery.img from the zip, place it on your external sd card and install it through Acer Recovery Installer by choosing Custom or Stock recovery.img from micro sdcard.
GPL compliant recoveries
RA Revamped for Iconia
TeamWin Recovery Project (twrp) - needs ICS bootloader
A500 Public Recovery
Since the creation of AfterOTA by gersma, you can use his software to install both the bootloader and CWM before flashing the ROM. Get it HERE
4. Flashing custom ROM
Download the ROM of your choice which should be a zip file. Place the zip on your EXTERNAL SD card. Power off your device. Now hold volume down and power buttons together until you see text appearing on the top left corner of the screen - you can release both buttons now. Wait until CWM loads. Volume keys (Up and Down) are used to navigate the CWM menu. Power button is uded as "Enter" i.e. to proceed with your selection. Before going on to install your ROM do a full backup of your system first. Navigate to "backup and restore" and then select Full Backup. Wait untill the operation completes.
Now do the following:
Wipe menu:
- wipe data/factory reset -> navigate to "Yes - delete all user data"
this should format you data partition and cache partition (dalvik cache is gone as well)
Mounts and storage menu
- Format System
this should format your system partition
The above commands are presented in thor's CWM. There are slightly different menus and sub-menus in the other custom recoveries but if you dig a little you'll find that they do the same things and you'll get the idea of what you're doing.
Now you're ready to install your ROM. Get back to the main CWM menu and select
- Install zip from sdcard -> choose zip from sdcard.
Navigate to your zip on the SD card and install it - choose "Yes" again to install. Wait untill installation is complete, return to the main CWM menu and choose "reboot system now".
You're done, enjoy your first custom ROM. Take time for its initial configuration.
5. Flashing custom KERNEL
Flashing custom kernel is as same as custom ROM. You place the zip (Kernels come in zip files as well) on your external SD card and:
- Install zip from sdcard -> choose zip from sdcard.
It is recommended before flashing a new kernel to wipe cache partition and dalvik cache. And of course first you flash the ROM and then the desired Kernel
6. UNBRICKING by flashing a stock ROM
thanks to vache we have full packages shared in his topic
vache said:
Once the desired file downloaded, you have to use Acer Update Decryter by thor2002ro to decrypt them.
After decrypting the file, you have to extract the update.zip from it, put it on an external SDCard (does not work on internal memory) and boot your tablet with Vol- & Power. The update will launch automatically.
Click to expand...
Click to collapse
p.s. Feel free to add stuff to this tutorial - video, pistures or anything you find useful or to correct me if I've made a mistake.

This is fantastic. Thank you. I have had my iconia for a month now and been looking at flashing a custom rom but kept backing out. Just a couple of questions for clarification:
(1). Does wiping data erase the internal sd?
(2). If by some stroke of bad luck a flash is unsuccessful and a boot loop or similar occurs, am I right in my understanding that you can just go straight back into recovery and re-flash?
(3). What are the chances of bricking the tablet?
Sorry for noon questions, please just wanna certain because my gf bought me this tablet under the condition I don't do anything risky like on my x10 that I flash almost daily haha
Thanks for replies
Sent from my A500 using XDA Premium App

kylec said:
This is fantastic. Thank you. I have had my iconia for a month now and been looking at flashing a custom rom but kept backing out. Just a couple of questions for clarification:
(1). Does wiping data erase the internal sd?
(2). If by some stroke of bad luck a flash is unsuccessful and a boot loop or similar occurs, am I right in my understanding that you can just go straight back into recovery and re-flash?
(3). What are the chances of bricking the tablet?
Sorry for noon questions, please just wanna certain because my gf bought me this tablet under the condition I don't do anything risky like on my x10 that I flash almost daily haha
Thanks for replies
Sent from my A500 using XDA Premium App
Click to expand...
Click to collapse
1. No, it doesn't.
2. Yes. You can do that. There's another option in mounts and storage -> format system - that will format even your system partition and leave your device bare with no ROM files on it. That would be a really clean install I guess
EDIT: I just saw that system is formatted during ROM installation. So no need to do that
3. Always read first what option you've selected and be sure you understand what it does. If you have CWM successfully installed, you have a powerfull tool to restore reflash, wipe, format etc. I've flashed my HD2 hundreds of times and now my Iconia is on the run Never ever had a boot failiure.

drkalo said:
1. No, it doesn't.
2. Yes. You can do that. There's another option in mounts and storage -> format system - that will format even your system partition and leave your device bare with no ROM files on it. That would be a really clean install I guess
3. Always read first what option you've selected and be sure you understand what it does. If you have CWM successfully installed, you have a powerfull tool to restore reflash, wipe, format etc. I've flashed my HD2 hundreds of times and now my Iconia is on the run Never ever had a boot failiure.
Click to expand...
Click to collapse
Thank you very much. I will click thanks when I'm on my computer :-D
Sent from my A500 using XDA Premium App

VERY good information here. Thank you very much for taking the time.
I've flashed ROMS on my last two "chinatabs" but haven't gotten into it with my A500 yet. (To be frank, I'm still thrilled with the prospect of OTA updates from a manufacturer after my last experiences.)
It looks like the process is very similar to my Rena3 tablet.

strider_mt2k said:
VERY good information here. Thank you very much for taking the time.
I've flashed ROMS on my last two "chinatabs" but haven't gotten into it with my A500 yet. (To be frank, I'm still thrilled with the prospect of OTA updates from a manufacturer after my last experiences.)
It looks like the process is very similar to my Rena3 tablet.
Click to expand...
Click to collapse
Thank you, that lays it out all nice and precise for us all. Like strider_mt2k, I have been holdng off on the custom ROMs, because my first tablet was a Gtab, and while it became a pretty awesome tablet, it had to be flashed with a custom ROM to be really usable. The OTA thing was holding me back. But I think that I may try to flash the thing this weekend if I get the chance.

Thanks. Glad it could be of use.

nice tutorial dude! thanks!!
could you please make another tutorial to return back to stock?
specially to return back to stock te kernel.
thanks!!!

As mentioned, best case is if you've backed up your device before flashing any ROM or Kernel. Thus you can restore to your country specific version.
Otherwise its pretty simple - its just like flashing any other ROM following the steps described.
Download the stock one that dr1337 shared from here:
http://forum.xda-developers.com/showthread.php?t=1154492
or choose the right full package - shared by vache:
decript it with Acer update decripter by thor2002ro
Of course they come with stock kernel

I am new in this with flashing and that kind of stuff.
Now is my question, how is it with updates from acer?
Greetz

distructor said:
How is it with updates from acer?
Click to expand...
Click to collapse
I'm not sure I understand your question. Could you be more specific?

if i put a custom rom on the device could i still use the build in update program of acer?

distructor said:
if i put a custom rom on the device could i still use the build in update program of acer?
Click to expand...
Click to collapse
Unfortunately I can not tell you for sure. I haven't tried all of the custom ROMs but in most cases - no you won't be able. I've tried Tabooney, Honeyvillain, Virtuous Picasso, Virtuous Galaxy. ROM developers usually update their ROMs to the latest base available. I think it depends on many things - base, kernel, stock apps removed etc.
Maybe someone who have succeeded with custom ROM updating would share his experience.

Can anyone tell me if there is a version of ROM manager that supports the version of CWM that there is for the Iconia. I would love to be able to simplify my ability to backup my ROM's before flashing.

synapses11 said:
Can anyone tell me if there is a version of ROM manager that supports the version of CWM that there is for the Iconia. I would love to be able to simplify my ability to backup my ROM's before flashing.
Click to expand...
Click to collapse
You can install a clockworkmod for Iconia no matter of the version of ROM manager. But it is much much easier to use Acer Recovery Installer. I recommend you using it instead of playing with recovery img files. It is a one time procedure after all
Anyway - here's what you need to do if you don't want to use Acer recovery installer, or you don't want to use ADB:
http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-3-using-rom-manager/
instead of CWM 3.x you will need to get CWM from thor2002ro In this guide you substitute the recovery that ROM Manager is about to flash with thor's CWM. I haven't tried this method myself but it should work.
With Acer Recovery Installer you can flash custom recovery as well. As long as you have it in IMG format you can be flashed from within the app - "install custom or stock recovery image from sd card".

great thread.
thanks!!!

Great Tutorial!!!
Just a couple of doubts:
First question: Backup files.
3. Flashing custom ROM
"...Before going on to install your ROM do a full backup of your system first. Navigate to "backup and restore" and then select Full Backup. Wait untill the operation completes. "
Where do the backup files go in the system? On internal or external SD card? Is it an *.img file extension?
Should i move it to my computer to keep it save, or just leave it where ever they are?
Second question: Kernel.
4. Flashing custom KERNEL
"Flashing custom kernel is as same as custom ROM. You place the zip (Kernels come in zip files as well) on your external SD card and:
- Install zip from sdcard -> choose zip from sdcard.
It is recommended before flashing a new kernel to wipe cache partition and dalvik cache. And of course first you flash the ROM and then the desired Kernel"
I am on Stock 3.1 ROM with original Kernel, if i want to try Virtuos Picasso, do i have to flash a new Kernel? And if yes, shouldn't i do it before flashing the ROM? Or just flash the ROM and then the Kernel? What happens if i just flash the Rom and use the stock kernel?
Thank you..

Your backup goes to your external SD card in a folder named clockworkmod\backup\2011-XX-XX.HH.MM.SS
As you can guess the name of the backup corresponds to the time it is created. This backup can be used to restore your system through CWM in case of need.
CWM does not backup /data/media folder. Additionally: you should also delete .android_secure.img from your backup set or a full restore will fail before it restores flexrom.
The last is an issue described by Euclid's brother:
http://forum.xda-developers.com/showpost.php?p=16467191&postcount=3
I am on Stock 3.1 ROM with original Kernel, if i want to try Virtuos Picasso, do i have to flash a new Kernel?
Click to expand...
Click to collapse
No, of course! Your custom ROM (Virtuous Picasso in your example) and any ROM comes with its Kernel. Its up to you to decide wheather to change it or not after that by flashing another Kernel. Follow every Kernel developer's notes for ROM compatibility. So, that answers the last part of your question - you cannot flash Virtuous Picasso and still think you're on stock kernel

drkalo said:
No, of course! Your custom ROM (Virtuous Picasso in your example) and any ROM comes with its Kernel. Its up to you to decide wheather to change it or not after that by flashing another Kernel. Follow every Kernel developer's notes for ROM compatibility. So, that answers the last part of your question - you cannot flash Virtuous Picasso and still think you're on stock kernel
Click to expand...
Click to collapse
Oh, i see...i thought that the flashing ROM procedure of a custom ROM, would just flash the ROM and not the Kernel...so in this case i just have to choose the ROM that i want to flash and do not have to pay attention about the Kernel compatibility...unless i flash a Kernel only. Right?
Thank you very much!!

That is correct

[GUIDE] For flashing on an ics rom that has issues in cwm recovery.

This is the development section i know. But people with issues look here for answers first therefore i decided to post it here. To devs: Please move as necessary. Sorry for any inconvenienced caused.
For people encountering problems in cwm , while on ics.
E.g
-Modem flashing takes forever
-Extracting system is done in like 1 sec.
-Bootloops after whatever.
Steps to take
1.Download Angelom's abyssnote kernel.
http://www.mediafire.com/?80n18xm228ttrr9
2.Put it into your sd card.
3.Boot into recovery.
(Optional/What i did.)
4.Full wipe. Even dalvik.
5.Flash the kernel
6.In advanced reboot into recovery.
Take note if step 5 worked as it should the recovery should be in red
7.On reboot flash as per normal / as per instructions from rom
chefs.
If all else fails, reboot into download mode and flash via odin a stock rom and re root.
Instructions over at dr.ketan's thread.
Credits to chasmodo who found out about this aa stated in post #4. And to angelom and redpill kernel dev.

People should upgrade using MobileOdin to the Chinese Leak then flash the ROM. I encountered no problems and everything went smoothly. It seems people getting stuck on modem are apparently jumping from GB to ICS by just flashing the ROM. Flash the .tar then flash the ROM.
Sent from my Ceramic White GT-N7000 using Forum Runner

There are instances where flashing from ics to gb. Results in this error...
Sent from my GT-I9220 using Tapatalk

It was originally posted here:
http://forum.xda-developers.com/showthread.php?t=1507329
Thanks to chasmodo. It helped me a lot.

whys this in the dev section?

Richy99 said:
whys this in the dev section?
Click to expand...
Click to collapse
A very good question.
Thread Moved To general​
Please only post development in this dev section​

come from team rocket ics 1.1 (sorry, still to buggy for me , but thanks for work)
for me it worked so:
- boot into recovery
- install Abyss 3.7 (I had still on SD)
- go in advance
- reboot recovery (got redpill instead of cwm)
- wiped cache and dalvik/cache (forgot factory/data)
- backup and restore menu
- restore from internal sd
- choose my backup from chainfire repack ics
that´s it
p.s. I renamed some backups like this 2012-01-29.12.15. V22 and it doesn´t work. MD5 mismatch. It have to without a space between like 2012-01-29.12.15.-V22

If all else fail, reboot into download mode and reflash KKA and root it before restoring backup. Worked for me after failing to install team rocket ics 1.3

WHat about if I have problem restoring my titanium backup??? I have followed every single instruction up to v1.5... I have root functions etc...(i know because I have root explorer working as per told) but still I am unable to restore my apps from TB...every time I do so, the phone will vibrate and SOD....freaking upsetting...its almost complete but without my apps, my phone is useless..
please enlighten me

CWM 5.5.0.4 and 5.8.31

what is the difference between CWM 5.5.0.4 and 5.8.3.1. Why ROM manager installed CWM 5.8.3.1 in Galaxy Tab P7500 while taking backup, though CWM 5.5.04 was already installed using ODIN I.85. Is it necessary to re install CWM 5.5.0.4. If so, how to re install CWM 5.5.0.4. My galaxy TAB P7500 is running on stock ICS 4.04.

Only a few changes are made(you can't even say where)from 5.5.0.4 to 5.8.3.1...
The ROMmanager must make sure that the CWM on your device matches with the version of the APP,but upgrading does no harm i.e. it's no need to reinstall CWM...
Beware!don't go into CWM if you are on the stock ICS because it has the rolling screen issue,flash all you need with ROMmanager,don't install CWM touch when you are using stock ICS(it'll be a waste of time,mony,etc)
If you want to get out of CWM(5.5.0.4) after flashing but get confused with the rolling screen just do thisress vol down and then press the power button twice...the tab restarts with all the changes you've made...
And finally:feel free to ask questions,XDA in always here to help you!

arashtarafar said:
Only a few changes are made(you can't even say where)from 5.5.0.4 to 5.8.3.1...
The ROMmanager must make sure that the CWM on your device matches with the version of the APP,but upgrading does no harm i.e. it's no need to reinstall CWM...
Beware!don't go into CWM if you are on the stock ICS because it has the rolling screen issue,flash all you need with ROMmanager,don't install CWM touch when you are using stock ICS(it'll be a waste of time,mony,etc)
If you want to get out of CWM(5.5.0.4) after flashing but get confused with the rolling screen just do thisress vol down and then press the power button twice...the tab restarts with all the changes you've made...
And finally:feel free to ask questions,XDA in always here to help you!
Click to expand...
Click to collapse
I'm using CWM 5.5.0.4 here with stock ICS. No problems at all.
5.5.0.4 is the version recommended to prevent rolling recovery.

I also followed pershoot's advice in the 2.6.36.4 thread. I did get the rolling recovery even with 5.5.0.4.
I am on stock US ICS and odined the following:
(1) US ICS 4.0.4 BL variant
(2) Recommended recovery (CWM non touch 6.0.1.2)
Now I have no flicker in the recovery or the ROM like I had experienced in the past. However, I'm rather way of CWM 6.0.1.2 because I used the previous non-touch (6.0.1.1 I think) and wasn't able to restore a Nandroid...it just hung on me. Where did you get the 5.5.0.4 that worked with stock ICS ROM/BL Jack?

Hi dj.
Can't remember now where I got 5504, read so many guides.
I have it in my drop box.
I'll post the link for it shortly.

Really

djmatt604 said:
I also followed pershoot's advice in the 2.6.36.4 thread. I did get the rolling recovery even with 5.5.0.4.
I am on stock US ICS and odined the following:
(1) US ICS 4.0.4 BL variant
(2) Recommended recovery (CWM non touch 6.0.1.2)
Now I have no flicker in the recovery or the ROM like I had experienced in the past. However, I'm rather way of CWM 6.0.1.2 because I used the previous non-touch (6.0.1.1 I think) and wasn't able to restore a Nandroid...it just hung on me. Where did you get the 5.5.0.4 that worked with stock ICS ROM/BL Jack?
Click to expand...
Click to collapse
Here ya go dj
https://dl.dropbox.com/u/99900479/recovery.tar.zip

You're the man! I may go back to stock firmware just to give this a go. Thanks!!

djmatt604 said:
You're the man! I may go back to stock firmware just to give this a go. Thanks!!
Click to expand...
Click to collapse
You're welcome.
Good luck.

Thank you for your nice advice and assurance. Sir I have another question/doubt. Please clarify
I am having P7500 in India. I flashed Italian stock rom 4.04 using ODIN. Later rooted the Tab using CWM 5.5.4 method. subsequently I installed ROM Manager. I did back up. It appears that CWM version was changed by ROM manager. Now I want to flash Indian stock rom 4.04 recently released and also rooting. Please suggest a mode.

Download the stock IN firmware from Sammobile and flash in Odin with PDA with your tablet in download mode. You will lose everything on your internal storage so if you want to keep your backups make sure to move them off the tablet before you flash.
You'll find lots of guides in the Q&A and Dev sections that will provide root methods for your 4.0.4 stock firmware. Or, you can skip all of this and just flash a rooted ICS ROM with a full wipe to save yourself the steps. It's really up to you.

Thank you Sir for your valuable advice.
Please clarify, If I flash INU stock ROM 4.04 on ITLY stock ROM 4.04, using ODIN, will it wipe out applications data also?
Earlier When I flashed ITLY stock ROM 4.04 on my original stock ROM 3.2 INU on my galaxy tab p7500 using ODIN, it did not wipe out any data from internal storage and all the applications were automatically installed after reboot..

It may, it may not...it depends on whether or not you boot up after the flash without issues. If you get stuck on the Samsung logo or a boot loop, you will need to boot into stock Android recovery and do a factory reset, that would format your /data partition and result in loss of apps etc.
That Thanks button works well if I have helped you makes me look like less of a noob! Good luck to you

djmatt604 said:
It may, it may not...it depends on whether or not you boot up after the flash without issues. If you get stuck on the Samsung logo or a boot loop, you will need to boot into stock Android recovery and do a factory reset, that would format your /data partition and result in loss of apps etc.
That Thanks button works well if I have helped you makes me look like less of a noob! Good luck to you
Click to expand...
Click to collapse
I recommend doing a full wipe with CWM recovery before flashing with ODIN. Doing that avoids having to do a full wipe with Stock recovery which wipes the internal. Wiping before flash should avoids formatted internal. Would others confirm, this is what I have noticed on my tab.

[Q] Official CM10 nightly for manta

Just curious if there is a thread for the official CM10 for manta (ie. from get.cm)... Does anyone have a list of what's not working? Trying to see if that is something I want to flash and if I do, what I will need to put up with that is not working.
Also, for those of you running the official nightlies, do you flash everyday to try and keep up? Would think it's quite the hassle to reset up the N10 everyday (assuming you lose everything with each new build).

http://forum.xda-developers.com/showthread.php?t=2027991
The CM OTA updater makes sure you don't lose anything between flashes including your GAPPs and settings, so it's not a big deal updating everyday.

cowabunga said:
Just curious if there is a thread for the official CM10 for manta (ie. from get.cm)... Does anyone have a list of what's not working? Trying to see if that is something I want to flash and if I do, what I will need to put up with that is not working.
Also, for those of you running the official nightlies, do you flash everyday to try and keep up? Would think it's quite the hassle to reset up the N10 everyday (assuming you lose everything with each new build).
Click to expand...
Click to collapse
For some reason the moderators felt that the CyanogenMod thread should be in general rather than either development forum.
Everything that works on the stock ROM works on CM10.1. Be sure to flash Google apps from http://www.goo.im
From then on you can keep CM10 up to date via the included updater in Settings->About as often as you'd like and you won't lose anything by doing the updates.

Thanks for the responses and the link to the official CM10 forum. Was looking in the development forums and was only finding "unofficial" threads.
Going to read up on CM10 for manta and then decide if I can live with what's broke. From the sounds of it, seems everything is mostly working.

So I've decided to take the plunge and go with CM10. I'm not finding instructions for a Mac. I've only seen toolkits that either run on windoze or linux.
Would the following instructions work from a Mac? I already have bootloader unlocked and CMW 6.0.1.9 touch installed (although it seems to be randomly rebooting while in recovery; think there is a fixed version that does not do this; however, I downloaded my version directly from the clockworkmod site, so...).
I've seen a few youtube video on how to install cm10 but they never tell you how to get the zip files onto the internal storage. They all start with the wipe then flash zip steps. So I thought I would try the following...
* copy latest cm10 nightly zip to /sdcard on the n10
* copy gapps to /sdcard on the n10
* boot into recovery
* Wipe Data/Factory Reset
* Wipe cache
* install from zip and install the cm10 nightly zip from /sdcard
* install from zip and install the gapps zip from /sdcard
* reboot
Not sure if the files in /sdcard will get deleted as a result of the "wipe data/factory reset" step and hence, not available when I get to the install from zip steps.
Anyone have better step by step instructions for getting cm10 onto an unlocked n10 with cwm touch installed using just a Mac?

Just noticed the official clockworkmod website has cwm 6.0.2.3 available. Have reflashed the new recovery. Seems to be better. The random reboots seem to be gone.
Now on to cm10. Anyone confirm my steps above or have better instructions?

For anyone wondering, I went ahead and switched to cm10 using the steps I listed 2 comments above. So these instructions will work if you want to manually install cm10 on your n10.

cowabunga said:
For anyone wondering, I went ahead and switched to cm10 using the steps I listed 2 comments above. So these instructions will work if you want to manually install cm10 on your n10.
Click to expand...
Click to collapse
So how does it run? I may flash this weekend as I hear it is reboot free.

[q] is there twrp recovery for mortorola bravo?

in teamwin official website i couldn't find twrp recovery support for motorola bravo, however motorola defy was in the list to get twrp recovery.
does TWRP for defy work on bravo? or we need a different for bravo? i love that recovery ...can some body help me install that on my bravo???

hiandro said:
in teamwin official website i couldn't find twrp recovery support for motorola bravo, however motorola defy was in the list to get twrp recovery.
does TWRP for defy work on bravo? or we need a different for bravo? i love that recovery ...can some body help me install that on my bravo???
Click to expand...
Click to collapse
The Defy TWRP works on the Bravo, but its only up to version 2.1 and can't install large Aroma roms (WR, Pikachu, etc). Your better off reading the thread over at Defy Development. Its neat and works, but our custom CWM 5 is the best for us in terms of reliability and stability.

skeevy420 said:
The Defy TWRP works on the Bravo, but its only up to version 2.1 and can't install large Aroma roms (WR, Pikachu, etc). Your better off reading the thread over at Defy Development. Its neat and works, but our custom CWM 5 is the best for us in terms of reliability and stability.
Click to expand...
Click to collapse
can u give me link to download latest CWM please.

hiandro said:
can u give me link to download latest CWM please.
Click to expand...
Click to collapse
Its installed be default with CM10 or PA. The newer the rom, the newer the recovery.
You can copy the zip/system/bootmenu/.... to other roms to get the touch ui in the bootmenu, just don't overwrite your current roms init scripts....and use a PRE 2nd Kernel zip when porting the bootmenu to non custom kernel roms. This isn't something I'd advise doing cause if you don't know what your fully doing you can easily put yourself in a position to flash the sbf. I sbf'd 3 times adding the JB Touch bootmenu to CM7.

skeevy420 said:
Its installed be default with CM10 or PA. The newer the rom, the newer the recovery.
You can copy the zip/system/bootmenu/.... to other roms to get the touch ui in the bootmenu, just don't overwrite your current roms init scripts....and use a PRE 2nd Kernel zip when porting the bootmenu to non custom kernel roms. This isn't something I'd advise doing cause if you don't know what your fully doing you can easily put yourself in a position to flash the sbf. I sbf'd 3 times adding the JB Touch bootmenu to CM7.
Click to expand...
Click to collapse
I installed cm10 then after I went to stable recovery and I wipe data/factory reset and then wipe cache and again wipe dalvik cache,and then I went to install zip from SD card and then choose mokee and flashed the zip.and when I reboot the phone it got stuck at Motorola red logo. again i boot into recovery (it was different, which mokee installed maybe)and when i wipe data and cache it said something like this:can't mount E/cache/recovery/log .and then i went to backup and restore and restored my cm10 backup and it only restored system(no data) why did this happen did I did something wrong?? or is there problem in recovery?? please tell me about this.

hiandro said:
I installed cm10 then after I went to stable recovery and I wipe data/factory reset and then wipe cache and again wipe dalvik cache,and then I went to install zip from SD card and then choose mokee and flashed the zip.and when I reboot the phone it got stuck at Motorola red logo. again i boot into recovery (it was different, which mokee installed maybe)and when i wipe data and cache it said something like this:can't mount E/cache/recovery/log .and then i went to backup and restore and restored my cm10 backup and it only restored system(no data) why did this happen did I did something wrong?? or is there problem in recovery?? please tell me about this.
Click to expand...
Click to collapse
I have a couple of ideas, but I'd be guessing with all of them. Probably just an error from CM10 using a newer recovery than Mokee. Since CM10's /system was restored, so was its bootmenu\recovery -- try doing a full restore now that you're using the same recovery that backed it up .
Crap like this is why we need an unlocked bootloader, or even just a place to hide a custom recovery -- with every rom you flash, your recovery changes and bad things can\have happened. While its nowhere as bad as it once was, problems like yours still occur from time to time. Its the same reason that there's so many posts with people having problems from using BandroidX Recovery -- its a very old CWM based recovery that uses different formats than whats used now (can't even install newer roms with it). Old and new don't usually play nicely with us .

skeevy420 said:
I have a couple of ideas, but I'd be guessing with all of them. Probably just an error from CM10 using a newer recovery than Mokee. Since CM10's /system was restored, so was its bootmenu\recovery -- try doing a full restore now that you're using the same recovery that backed it up .
Crap like this is why we need an unlocked bootloader, or even just a place to hide a custom recovery -- with every rom you flash, your recovery changes and bad things can\have happened. While its nowhere as bad as it once was, problems like yours still occur from time to time. Its the same reason that there's so many posts with people having problems from using BandroidX Recovery -- its a very old CWM based recovery that uses different formats than whats used now (can't even install newer roms with it). Old and new don't usually play nicely with us .
Click to expand...
Click to collapse
Yeah, i tried to restore backup using cm10 recovery and although it said cant restore .android.secure something like that(iam not quite sure) it restored system as well as data.
The thing is i like mokee os .its speed, clean and clear... ecetra but it is not jelly bean.can't we have a cm10 tweaked and modified for bravo.of course I love your PA jelly bean there are lots of tablet tweaks can you also add some other functions like in pimp my rom.
And thanks man for answering my queries