Database Users

GTab recovery firmware (homebrew and official Viewsonic 1.0.1 & 1.1-based versions)

GTab recovery firmware (homebrew and official Viewsonic 1.0.1 & 1.1-based versions)
TnT 1.1-3588 recovery ROM, dated 01/24 and supplied by Viewsonic / TnT. Link: http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip
md5sum: 0f07d710728640ea1e0f4a5d6d3fa72c
TnT 1.1-3389 recovery ROM, dated 12/23 and supplied by Viewsonic / TnT. Link: http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3389-user.zip
md5sum: e6c09077f67b29c42643b7ae5f10d6e2
TnT 1.1-3316 recovery ROM, dated 12/19 and supplied by Viewsonic / TnT. Link: http://tapntap.http.internapcdn.net/tapntap/update-smb_a1002-3316-user.zip
Alternate link: http://www.mediafire.com/?p9o52540baa5vfg
md5sum: 1333e22b6d802096d3c63757680777f0
TnT 1.0.1-3053 recovery ROM, dated 12/10 and supplied by Viewsonic / TnT. Link: http://tapntap.http.internapcdn.net/tapntap/update-smb_a1002-3053-user.zip
Alternate link: http://www.mediafire.com/?qy92jzoz8upy8xa
md5sum: 7b800e409b5324f2c69e7ba6f84eab97
TnT 1.0.1-2967 recovery ROM, dated 11/22 and supplied by Viewsonic / TnT. Link: http://tapntap.http.internapcdn.net/tapntap/update-smb_a1002-2967-user.zip
Alternate Link: http://www.mediafire.com/?99eb11cqhvrkkc7
md5sum: 43eb0358db25b492751b1b0a71568c51
These were grabbed from my over-the-air update. They are full recovery images that wipes everything except the user data.
NOTE: These are only for 1.0.1 or 1.1 based stock versions. For 1.2 based stock versions, they will be hosted in the same location as my 1.2-based mods./[/url]
===================================
Instructions for use with the internal memory:
1- Mount your device to your PC
2- Download the ROM you wish you use, and save it to the root of the mounted drive. Rename it to "update.zip"
3- Create a folder on your mounted drive callled "recovery".
4- In that recovery folder, create a file called "command", and add this line to that file:
Code:
--update_package=SDCARD:/update.zip
NOTE to Windows users: If you use notepad, it might name the file "command.txt". That won't work. It cannot have a file extension. I would recommend downloading and using the excellent program "notepad++" as a notepad replacement.
5- Shutdown the device and then boot into recovery (Hold Power button and volume up key for a few seconds). If you are using standard recovery, the install should run automatically. If you are using clockworkmod, you will need to manually choose the update.zip file.
6- Reboot when completed (standard recovery users will be rebooted automatically).
Other note: These stock ROMs WILL flash recovery, as they are designed to do that. If you are using clockworkmod, that recovery tool will most likely be wiped out. Also, if you experience a boot loop post-install, you won't have clockworkmod installed to correct it - there are ways to install a clockworkmod image off your microSD, if necessary, then wipe your user data. Most times, these reboot hangs are due to incompatible data partitions between mods - this is especially true for ROMs like gADAM.

This is not working for me trying to flash from clockwork
i'm getting an error
assert failed: write_raw_image("/tmp/recovery.img", "recovery")
E:Error in /sdcard/update.zip
(Status 7)
Installation Aborted
please help!

nick325i said:
This is not working for me trying to flash from clockwork
i'm getting an error
assert failed: write_raw_image("/tmp/recovery.img", "recovery")
E:Error in /sdcard/update.zip
(Status 7)
Installation Aborted
please help!
Click to expand...
Click to collapse
It's spotty with cwm - I've seen the same thing - cwm probably has an issue being overwritten, for some reason.
You might want to alter the ZIP and just rip out the line that's trying to overwrite recovery.

Had this error too
I removed this line from the updater-script file and CWM finished the install succesfully
assert(package_extract_file("recovery.img", "/tmp/recovery.img"), write_raw_image("/tmp/recovery.img", "recovery"), delete("/tmp/recovery.img"));
thanks again roebeet
should I be worried about leaving superuser on this if im returning it?

daCalifa said:
Had this error too
I removed this line from the updater-script file and CWM finished the install succesfully
assert(package_extract_file("recovery.img", "/tmp/recovery.img"), write_raw_image("/tmp/recovery.img", "recovery"), delete("/tmp/recovery.img"));
thanks again roebeet
should I be worried about leaving superuser on this if im returning it?
Click to expand...
Click to collapse
I don't think they'll catch it. Just don't leave your user data intact or anything in the internal memory!

Where can I find the "/recovers/command" file?

deleting that line from the updater-script file worked for me with clockworkmod recovery installed.. if anyone is a noob here's some instructions..
unzip the vanilla recovery rom.. go into the "update-smb_a1002-2967-user\META-INF\com\google\android" folder and edit the updater-script file. I had to use notepad++ to edit it, regular notepad wasn't showing the formatting correctly. then just delete this line "assert(package_extract_file("recovery.img", "/tmp/recovery.img"), write_raw_image("/tmp/recovery.img", "recovery"), delete("/tmp/recovery.img"));" save the file, then zip up the contents of the update-smb_a1002-2967-user folder into an update.zip and copy it to your gtablet. make sure the inside of the update.zip shows the system.img etc files in the root of the zip and that you don't zip it up so those files are one folder deep into the zip. hold down volume + while turning the gtablet on and it should load clockworkmod and let you flash the new update.zip.

Wishmaster2 said:
Where can I find the "/recovers/command" file?
Click to expand...
Click to collapse
It's not in here -- 1.0.1 is a 100% vanilla ROM from Viewsonic so I did not touch it. Viewsonic even calls it 1.0.1.
For the command file, you can grab that in the homebrew 1.0.0 version.

I've flashed my g-tab back to TnT stock dated 11/22. Question: is it possible to get it back to the PRE-updated TnT stock? -- i.e. v.1.0.0 of roebeet's homebrew firmware?
It's a very long story, but I might need to return the g-tab and I need to get it back to the absolute original shape... MANY THANKS!
EDIT: I did tried the flash 1.0.0 on top of 1.0.1 but (not too surprisingly perhaps) nothing happens. I was able to get back to 1.0.1 from TnT Lite 2.0 so I believe I used the correct method.

case-sensitive said:
I've flashed my g-tab back to TnT stock dated 11/22. Question: is it possible to get it back to the PRE-updated TnT stock? -- i.e. v.1.0.0 of roebeet's homebrew firmware?
It's a very long story, but I might need to return the g-tab and I need to get it back to the absolute original shape... MANY THANKS!
Click to expand...
Click to collapse
Tmk, Viewsonic has never supplied a 1.0.0 of their own (technically they never supplied a 1.0.1 either, but we managed to grab it). Why not return it with 1.0.1? That's what I did with my 2nd device - you'll be doing the next owner a favor.

roebeet said:
Why not return it with 1.0.1? That's what I did with my 2nd device - you'll be doing the next owner a favor.
Click to expand...
Click to collapse
(1) The sears folks actually checked! (2) 1.0.1 is less broken so I have less excuses to return it :-(
This is lame, I know...
Thanks for all your work!

I can't figure out how to remove clockworksmod after I restore the Gtab. Everything else is stock except for the recovery.

+1 on this... gotta get rid of that recovery before I take it back.
ojo8 said:
I can't figure out how to remove clockworksmod after I restore the Gtab. Everything else is stock except for the recovery.
Click to expand...
Click to collapse

Please can someone help me out with this.
ojo8 said:
I can't figure out how to remove clockworksmod after I restore the Gtab. Everything else is stock except for the recovery.
Click to expand...
Click to collapse
Sent from my PC36100 using Tapatalk

How Do I Install: Step by Step, The Recovery ROM
Hi There,
Can you explain in "steps" how to install the recovery ROM to the gTablet? or any other ROM?
I have "rooted" my gTablet, installed the "Flash", installed "Launcher Pro", installed the "Titanium-Full-Market Method" and now my gTablet powers right OFF after the gTablet screen.
Thank You

toddsworld34685 said:
Hi There,
Can you explain in "steps" how to install the recovery ROM to the gTablet? or any other ROM?
I have "rooted" my gTablet, installed the "Flash", installed "Launcher Pro", installed the "Titanium-Full-Market Method" and now my gTablet powers right OFF after the gTablet screen.
Thank You
Click to expand...
Click to collapse
The standard recovery (not clockworkmod) has two components. They can live on the internal /sdcard or on a microSD:
update.zip
/recovery/command
update.zip is pretty standard on Android, so I won't go into it - it's basically the package that actually updates the device.
/recovery/command is like a startup script - it tells recovery where the update.zip package is. This file gets erased after an update, I assume to avoid you from accidentally re-running it. It's a text file that will run /sdcard/update.zip, by default. If you need to change this to the microSD card, you need to edit the file so that "SDCARD" reads "SDCARD2", instead.

I too would like to know how or if its possible to revert from clockworkmod to the vanilla recovery?

jfholijr said:
I too would like to know how or if its possible to revert from clockworkmod to the vanilla recovery?
Click to expand...
Click to collapse
Tmk, the only way to successfully eradicate cwm is to use nvflash. I tried flash_image awhile back and could never get it to work.
This is the reason why I usually say that cwm is for the more tech folks, as it's a one way street unless you know how to use nvflash.

roebeet said:
Tmk, the only way to successfully eradicate cwm is to use nvflash. I tried flash_image awhile back and could never get it to work.
This is the reason why I usually say that cwm is for the more tech folks, as it's a one way street unless you know how to use nvflash.
Click to expand...
Click to collapse
No biggie, I baught this thing to force myself to get my hands dirty. Bumps, cuts and bruises are inevitable. Will future OTA updates work with reverting back to the vanilla rom even if stuck with CWM?

jfholijr said:
No biggie, I baught this thing to force myself to get my hands dirty. Bumps, cuts and bruises are inevitable. Will future OTA updates work with reverting back to the vanilla rom even if stuck with CWM?
Click to expand...
Click to collapse
I don't think so because you have to get to recovery to actually use it, which is cwm.

[NIGHTLY][ROM] CyanogenMod 7 for Samsung Captivate (captivatemtd)

This thread is reserved for nightly builds of CyanogenMod Rom for Samsung Captivate.
All Samsung Roms run on top of BML/RFS, CyanogenMod 7 does NOT.
It runs on MTD/yaffs2 (like Nexus One) which means you'll not able to flash just any kernel or run just any other filesystem you want. Use it as it is if possible, otherwise confirm with the kernel developer that you are trying to install whether it would work with CM. We do not support other kernels and know nothing about their capabilities or compatibility. Only the data partition, which is on movinand, is ext4 like on speedmod or voodoo ("lagfix"). No "lagfix" is necessary because this does not use any Samsung proprietary file systems.
CyanogenMod is a free, community built distribution of Android 2.3 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
What are Nightly builds? Auto compiled build of the latest CyanogenMod source from github. This version changes each night and aren't officially supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bugs on CyanogenMod issue tracker).
Warning : Not for new users, flash this build only if you know what you are doing !!! Make SURE you can get into Download mode using only buttons (no other method, Download mode from just buttons is essential).
INSTRUCTIONS:
Latest version: http://download.cyanogenmod.com/?device=captivatemtd
Check the md5sum if you want to be sure that the download worked (different OSes have different programs that do md5, on ubuntu it is md5sum that you run against the zip you download and compare to the md5sum number shown on the download website). ROMManager does this automatically for ROMs you download via ROMManager.
- First time flashing CM 7 to your Captivate (or coming from another ROM)?
Easy way:
Start with a rooted Eclair/Froyo running Eclair/Froyo Bootloaders (do not ask us how to do this).
Install ROMManager Premium.
Flash ClockworkMod Recovery. Pick Captivate (MTD) (ignore the warning about not having an official, pick ClockworkMod 2.x).
Make sure you can reboot into ClockworkMod recovery from ROMManager. Reboot and get back into ROMManager Premium.
Choose download ROMs.
Pick the CyanogenMod Nightlies.
Check the Google Apps addon.
Check Backup current ROM!
Check wipe data, cache, dalvik cache.
Let ROMManager finish the installation.
Harder way:
Make sure you're running a Eclair/Froyo Firmware (2.1 or 2.2) and Eclair/Froyo Bootloaders!
Root your device and install ClockworkMod Recovery.
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon (through ROMManager is easiest)
- Upgrading from earlier CM7?
ROM Manager method:
Install ROMManager Premium.
Flash ClockworkMod Recovery. Pick Captivate (MTD) (ignore the warning about not having an official, pick ClockworkMod 3.x).
Choose Download ROMs.
Pick the CyanogenMod Nightlies.
Check the Google Apps addon.
Check Backup current ROM!
Check wipe cache, dalvik cache.
Let ROMManager finish the installation.
Clockwork Mod method:
Download and push the ROM zip file to the sdcard.
Reboot into recovery.
Do a Nandroid Backup!
Install the ROM zip from sdcard (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps. After flashing the rom, don't forget to flash Google Addon package if you want it. ROM Manager will allow you to flash it if you just go into it and after flashing the ClockworkMod recovery for MTD devices, choose Download ROMs, and pick Google Apps.
Additional Information:
Maintainers:
atin - http://twitter.com/atinm
codeworkx - http://twitter.com/codeworkx
coolya - http://twitter.com/dumdidum
guiperpt - http://twitter.com/guiperpt
unhelpful - http://twitter.com/unhelpfulone
Irc:
Host: irc.freenode.net:6667
Channels: #cyanogenmod, #cyanogenmod-dev, #cmsgs
Changelog:
Generic Changelog CMSRC Twitter
Device specific Changelog by igor.tonky
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy![/QUOTE]

SWEET thanks! Gonna try this out and test it.
Sent from my GT-I9000 using XDA App

Oh snap!
di11i 6.0 w/ Suckerpunch #53
Underclocked to 600mhz
Undervolted to -100mV

Very nice! definitely going to flash it
Is camera working fine now?

Wow
Wow you mean I can actually use Gingerbread on my cappy. I was getting bored of playing with ginger on my HTC dream which is slowwwwer then slow.
Thanks to every dev working on this.

atinm said:
your kitties, doggies and maybe even goldfish are no longer safe.
Click to expand...
Click to collapse
hahaha!
That is the funneyest thing i have herd.

Just want to make sure my understanding is correct
- Don't use "reboot recovery" command or other shiny things to do this!
Flash cm7-captivate-initial-kernel.tar as pda using odin without auto-reboot
So after flash of efs pull battery, get to dl mode, flash initial kernel with auto reboot off. Pull bay after flash go back to recovery?
Do a wipe
Factory restore in clockwork?
Install the Nexus S USB-Drivers from SDK-Manager if you're using windows.
Are these drivers needed to use odin our just files transfers
To revert to a samsung rom, simply use odin with repartition option enabled.
Does odin one click qualify here or use full version?
Just making sure I understand instructions fully, thanks

thx for your hard work man

DAGr8 said:
thx for your hard work man
Click to expand...
Click to collapse
Can't wait to see what you do with this.

Thank you very much but because this is a test release, I will keep my eye very close to see how everyone else does on this ROM. Actually, I'm scared to flash this until it's stable enough for a daily driver .

Can I reserve a post this late? Lol
Sent from my Captivate using XDA App

CM7 getting awfully close!

mcord11758 said:
So after flash of efs pull battery, get to dl mode, flash initial kernel with auto reboot off. Pull bay after flash go back to recovery?
Click to expand...
Click to collapse
No, please read the instructions fifty-thousand times before you do anything. It clearly says to use the three button combo to reboot, directly underneath that. If you do a battery pull while in Download mode, you risk destroying your phone.
mcord11758 said:
Factory restore in clockwork?
Click to expand...
Click to collapse
Yes.
mcord11758 said:
Are these drivers needed to use odin our just files transfers
Click to expand...
Click to collapse
These are drivers to use your phone (incorrect, but avoiding the question). Just install the drivers, because the instructions say so. If you don't, you can't plug your phone into your computer.
mcord11758 said:
Does odin one click qualify here or use full version?
Click to expand...
Click to collapse
Odin One Click. Or Odin3. It doesn't matter. Just reboot into Download mode using the button combo and use Odin.

I must be dumb but, There is no efs-backup for initial kernel to even download, Or I'm unable to find it. On that page, all I see is Initial package, update, and google-addon. No kernel, no efs package.
EDIT: k. I just fail. It was inside the initial package. .-.

Thank you for the response. The initial kernel to be flashed via odin is the z image inside the initial package?

This is why I love Android and XDA! Sweet! Even before Samsung releases it to the I9000 (granted it's still under development).

Are the modem links dead for anyone else?

Yeah I have no idea where the "initial kernel" is. It's not ANYWHERE on the site, nor in the initial package.

Konner920 said:
Yeah I have no idea where the "initial kernel" is. It's not ANYWHERE on the site, nor in the initial package.
Click to expand...
Click to collapse
Yeah, couldn't find that either.

Great job guys. I want to try this as I will flash almost anything once. I will give it some thought. I feel I am one step above noob. Any noobs out there might want to wait some more. Then again if you are a flasher...
Awesome work/progress.
Edit: I made the plunge. Worth every minute.

[TUTORIAL]ClockworkMod Recovery Easy Install

Since people are obviously having trouble installing CWM, I thought I'd make this topic since the other one doesn't seem that it will be updated anytime soon. This does require root.
Step 1: Rooting your phone-Follow the link that's labeled "Superoneclick Root." Download the file and follow instructions. Works on ALL Vibrant Froyo (KA6/KB5) and Eclair. Reboot.
Step 2: Flashing CWM-Download ROM Manager from the market. Open the app, and choose the very first option. It should say "FLash ClockworkMod Recovery." Choose vibrant.
Step 3: Getting into CWM
a. Use the link below that's labeled "Modified 3e REcovery." DOwnload file and follow directions. IF it succeeds, reboot into recovery via 3 button combo and hit rreinstall packages. The phone should reboot into recovery. Hit reinstall packages again and voila.
**Note** this did not work for me.
-OR-
**PRE-POST NOTE** Odin will WIPE ALL APPS AND DATA. Use Titanium Backup from the market to backup apps.
b. If the 3e fix didn't work for you, I suggest using Odin to flash back to stock. Follow either links labeled "Odin Back to Stock" for detailed, step-by-step guides on how to flash back to stock. If it succeeds, reboot to recovery, and you should see "2e recovery" instead of 3e. Hit reinstall packages. It will reboot back into recovery, hit reinstall packages again and voila.
-OR-
c. If those don't work, you can try downloading and flashing a voodoo integrated kernel to access the "red" clockwork recovery via ODIN or SGS Kernel Flasher. I recommend you flash a "stock + voodoo" kernel first however, and then flash your kernel of choice (Overstock, Bali, w/e). MAKE SURE IT'S COMPATIBLE. Follow link down below for stock kernels + voodoo. Find the flasher at the market. This will patch your system with ext4 and is a pretty nice addition. Now, this might take a long time, depending on the amount of apps that you have. You might and probably will hear "linda" which is just a voice that tells you what's happening.
**Note** I have tried SGS kernel flasher multiple times and multiple times it has failed to flash properly---soft brick--boot loop. I'm not saying that you will too, I'm just stating my experiences.
**Disclaimer** I am not responsible for bricked and/or damaged phones, you did it, it was your choice. Although the chance of a hard brick is pretty low.
I do recommend looking at s15274n's guides below if you intend on flashing ROMs. If you don't intend to, might I recommend that you add that to your to do list as well? It might just be a worthwhile experience.
Modified 3e Recovery
http://forum.xda-developers.com/showthread.php?t=833423
Superoneclick Root
http://forum.xda-developers.com/showthread.php?t=803682
Odin Back to Stock + Flashing ROMs
http://forum.xda-developers.com/showthread.php?t=1047087
http://forum.xda-developers.com/showthread.php?t=849028
Stock + Voodoo All Except KB5
http://forum.xda-developers.com/showthread.php?t=870480
Stock + Voodoo KB5
http://forum.xda-developers.com/archive/index.php/t-1036725.html
Hope this helps. Feel free to help me 'perfect' these steps.

Appreciate the effort... I feel (obviously biased) my Noob Root Guide is a little more detailed.. and easier (again, bias), perhaps you want to link to that too in case people are questioning things.
I am NOT a fan of superoneclick OR the modified 3E (like you said it didnt wok for you), just my personal stance. Nice to have options for people though, so thanks!!

I'm running KB5 having Kies'd form the original 2.1 ->2.2 -> 2.2 (KB5). I've also tried the modified 3e recovery without signature check, and it failed to update to CWM for me too.
I'm very reluctant to ODIN to 2.1 stock without getting a real backup. Some questions:
1) Is there nothing I can run from the PC side that can pull a full image from the phone that could be restored if necessary?
2) If I go with the Titanium backup, what exactly will I lose, after ODIN (phone history, settings,..)?
3) If I do ODIN back to 2.1 and install CWM, can I Kies back to KB5 without losing CWM?

kmandel said:
I'm running KB5 having Kies'd form the original 2.1 ->2.2 -> 2.2 (KB5). I've also tried the modified 3e recovery without signature check, and it failed to update to CWM for me too.
I'm very reluctant to ODIN to 2.1 stock without getting a real backup. Some questions:
1) Is there nothing I can run from the PC side that can pull a full image from the phone that could be restored if necessary?
2) If I go with the Titanium backup, what exactly will I lose, after ODIN (phone history, settings,..)?
3) If I do ODIN back to 2.1 and install CWM, can I Kies back to KB5 without losing CWM?
Click to expand...
Click to collapse
1. As far as I know, no.
2. Everthing goes stock...out of the box stock. Import your contacts to your sim card or back it up with AVG or something. SD Card will not be wiped however
3. I believe so, yes.

updated OP!

Iconia Common Questions & Answers

I've seen the following things asked again and again and again, and yet there seems to have been no attempt to make a Q&A for our tablet, so I figured I might as well take a shot, especially now that the mods have given us a proper Q&A section. I don't expect this to be fully comprehensive, but I'll try to cover the important stuff at least!
1. Q: I have an A501, can I use one of the A500 roms, either stock or custom?
A: No, absolutely NO! Well, actually, you CAN, but if you do you WILL lose 3G capability, so don't. There are currently no custom ROMs available for your tablet, sorry. Hopefully that will change soon.
2. Q: Can I root my A500?
A: Yes. There was originally a modded Gingerbreak root for the Iconia, but it only worked on 3.0.1 and has now been superseded by an updated root method. See the following thread for more information:
http://forum.xda-developers.com/showthread.php?t=1138228
3. Q: Is the bootloader really locked?
A: Yes and no. The bootloader itself isn't actually locked as such, but the ROM *is* protected by a hash key. This has been bypassed thanks to sc2k with a great utility called "itsmagic".
4. Q: So how do I use "itsmagic"?
A: The easiest way is to install the custom version of Clockwork Mod, by thor2002ro. See the following thread for more information.
http://forum.xda-developers.com/showthread.php?t=1126364
5. Q: Wow, I'm a newbie and installing that looks complicated. Is there an easier way?
A: Absolutely! Install the Acer Recovery app and it will take care of installing Clockwork Mod AND itsmagic for you, as well as backup your stock recovery!
https://market.android.com/details?id=com.interphaze.AcerRecoveryInstaller
6. Q: I'm scared of Clockwork Mod, is there an easier way to install a custom ROM?
A: Absolutely! From the makers of Acer Recovery, there's the Acer ROM Flasher app!
https://market.android.com/details?id=com.interphaze.Acer_ROM_Flasher
HOWEVER This app does NOT run the "itsmagic" utility (yet), so it's probably better for you to flash from CWM for now (Thank's Euclid's Brother for pointing this out!)
7. Q: Hang on a minute, can't I use the Clockwork Mod that's on the market? How about ROM manager too?
A: Simple answer? No. Our Clockwork Mod is a custom built that runs the "itsmagic" utility at the right time, preventing people from accidentally bricking their tablets. Do NOT use the one on the market or you will brick. As for ROM manager, it's not compatible, sorry. Use the Acer ROM Flasher application instead
8. Q: OK, so I'm rooted and I've got Clockwork Mod installed, now what?
A: The absolute first thing you should do, EVER, before installing a new ROM, is to make a backup of your current on. This feature is built into Clockwork Mod and is really easy to use. Do it.
9. Q: OK, I made a backup, now what?
A: Visit the Developer section of the A500 forums here on XDA-Developers, and you'll find several excellent custom ROMS, as well as links to stock ROMs, for your ROM flashing pleasure.
10. Q: I don't want to install CWM, I just want to flash a new stock ROM, how do I do that?
A: There are several threads detailing this, but to summarise, there are several things you'll need to do.
1. Locate and download the stock ROM you want.
2. Unzip this ROM to your PC. If you get a message about an invalid ZIP file, then you'll almost certainly need to run it through the Acer Update Decrypter first. See below:
http://forum.xda-developers.com/showthread.php?t=1099673&highlight=acer+recovery
3. Once opened, extract the update.zip file found inside this zip.
4. Copy update.zip to the root of your external SD card. NOT the devices internal storage. It won't work from there.
5. Make sure you have more than 60% battery, or plug in to the AC adapter, and turn your device off.
6. Hold down the Volume Down key (the left side of the rocker when device is in landscape orientation), and hold down the power key. Keep both held down until you see 3 rows of white text in the top left corner of the screen. Your device will now flash the update.zip on your SD card.
NOTE: There are several types of update you can flash.. Many are incremental updates and will be smallish (40mb or so). This can NOT be flashed on a device that has had ANY changes at all made to any preinstalled files, as this is an incremental update. However, if the update is 300+mb in size, it's almost certainly a full ROM and should flash fine. If it doesn't though, try a factory reset first.
11. Q: I cannot connect to my WIFI hotspot, why?
A: There are 2 possible reasons, so it depends on exactly what problem you're having.
1. The Iconia does not seem to support wifi ad-hoc (or peer-to-peer) mode. To connect to this kind of hotspot, you will need to modify a file called "wpa_supplicant" and you must be rooted to do this. See below for instructions.
http://forum.xda-developers.com/showthread.php?t=1060909&highlight=ad+hoc
2. Alternatively, if you're just getting a constant loop of "Connecting...", and never get an IP address, Acer have issued a patch for this, but it's for specific ROM's only. You can find this on the Acer update site, or can download directly below. Full instructions are included inside the ZIP file.
http://global-download.acer.com/GDF...AB&Step3=A500&OS=a07&LC=en&BC=Acer&SC=EMEA_27
12. Q: Help! I have a checksum error!
A: You probably flashed something and didn't run itsmagic... This is potentially very serious, but all is not lost. sc2k has been kind enough to provide instructions on how to fix it.
http://forum.xda-developers.com/showthread.php?t=1129873

<Reserved>

Well done. Quite comprehensive.

Just want to point out.. the Acer ROM Flasher (not to be confused with Acer Recovery Installer) does not run itmagic.... (yet..) It was made for a very specific purpose and has not been updated since itsmagic came out.
So, If you use Acer ROM Flasher, which will flash boot.img and system.img, make sure you run itsmagic yourself BEFORE flashing the images. I'll update it to include itsmagic when I have time.
Acer Recovery Installer is really the best way to go. Then use Clockworkmod for your backup/restore and custom rom installation.

Euclid's Brother said:
Just want to point out.. the Acer ROM Flasher (not to be confused with Acer Recovery Installer) does not run itmagic.... (yet..) It was made for a very specific purpose and has not been updated since itsmagic came out.
So, If you use Acer ROM Flasher, which will flash boot.img and system.img, make sure you run itsmagic yourself BEFORE flashing the images. I'll update it to include itsmagic when I have time.
Acer Recovery Installer is really the best way to go. Then use Clockworkmod for your backup/restore and custom rom installation.
Click to expand...
Click to collapse
Thanks for pointing that out. I've updated my OP accordingly.

[Q] Getting latest CWM onto Droid X - help!!

This phone is about to cause me to start mainlining some serious drugs. I just do not understand what I'm doing wrong.
I have read and read and read and downloaded and downloaded and downloaded. At one point I think I had about 10 Firefox tabs open, madly switching between them trying to figure this beast out. So, I have tried to do the necessary homework before posting here.
I received a Verizon Droid X (MB810 model) and was wanting to install a 2nd-init ROM. It came with .621, which I know has been problematic in the past, but seems not to be a terribly big obstacle anymore. Here are the steps I've taken:
o I rooted the phone via the Slitaz ISO.
o Via adb, I pushed the Droid 2 (D2) reboot recovery and ROM manager (RM) APKs.
o I choose boostrap recovery in the D2 application. Superuser grants the appropriate permission.
o Within RM, I download and flash the latest CWM (5.0.2.0) based on the 2nd-init Droid X option.
o RM says that the flash is successful and Superuser rights are granted.
o From within RM, I choose the reboot into recovery option.
o The phone reboots...right back into the operating system, completely bypassing CWM. Redoing the above steps and holding down the home key just boots into the stock recovery.
Now, I can reboot into CWM from the D2 application, but I'm then confronted with the old version of CWM. I've also read where this method will screw-up the boot process to the point that installing 2nd-init ROMs won't work. I've (somewhat) verified this by trying to install the latest AOKP with the D2 version of CWM, which just endlessly loops the unicorn animation. In fact, in a thread detailing this problem on another forum, it was advised to stay far, far away from the D2 application altogether and just use RM.
I've also had to SBF back to .621 on several occasions using RSDLite 4.9.
This has been nightmarish. I spent almost the entire weekend trying to get this phone to boot into the latest CWM. Do I have to SBF the Milestone ROM in order for this to work? Is that even necessary anymore?
Any help would be GREATLY appreciated, as I'm out of ideas at this point. Thanks a bunch.
- Fred

did you wipe data before/after flashing SBF?
if not, that could cause issues

sd_shadow said:
did you wipe data before/after flashing SBF?
if not, that could cause issues
Click to expand...
Click to collapse
Yes, I forgot to mention I did that in my OP.
I just don't understand what's going on. It's almost as if RM is lying to me about having successfully flashed the newest CWM. I say this because, when I immediately do the flash procedure after booting the phone, nothing shows up in /preinstall/recovery/ using Root Explorer (RE). It's only after I do the D2 bootstrap recovery option that /preinstall/recovery/ is populated with the CWM files. The problem is that these files represent the 2.0.5.8 version, not the 5.0.2.0 update.
To even deepen the mystery, after I did the above, I then went back into RM and reflashed to the latest CWM. I then looked at /preinstall/recovery/ again and all of the original 2.0.5.8 files were still there. There was no evidence that I could determine that RM installed anything anywhere.
I'm at a total loss.

did you try deleting NFS Shift or Madden from the preinstall, then reflash CWM in RM?

sd_shadow said:
did you try deleting NFS Shift or Madden from the preinstall, then reflash CWM in RM?
Click to expand...
Click to collapse
I just did that. RE is showing 244MB free, which I'm assuming is more than enough for RM to do its thing. I then redid the steps I outlined above and /preinstall/recovery/ still isn't populating with the 5.0.2.0 update.
This is beyond bizarre. How can RM state that it successfully flashed to the latest CWM when it doesn't appear to do anything? If RM runs into an error in the file creation process, does it report that to the user or just acts as if everything is normal?

i don't think you will get an error
have you tried redownloading D2 bootstrap and rom manager, from market?
have you read this? http://rootzwiki.com/topic/31737-root-droid-x-root-method-for-234-45621-does-not-require-milestone-sbf/page__st__20#entry878745

Maybe this is a dumb question, but I'm not familiar with the Slitaz ISO.
So does that install a 2nd-init ROM? Or have you installed a 2nd-init ROM manually?
If you haven't, you shouldn't be selecting the 2nd-init recovery. Use the regular Droid X recovery, install the 2nd-init recovery only after flashing a 2nd-init ROM.

the link was to a post that
someone was having trouble updating cwm to 5.0, and some possible fixes
as for the Slitaz ISO, is just a linux program used to run the magic md5 root method

fleggett said:
I just did that. RE is showing 244MB free, which I'm assuming is more than enough for RM to do its thing. I then redid the steps I outlined above and /preinstall/recovery/ still isn't populating with the 5.0.2.0 update.
This is beyond bizarre. How can RM state that it successfully flashed to the latest CWM when it doesn't appear to do anything? If RM runs into an error in the file creation process, does it report that to the user or just acts as if everything is normal?
Click to expand...
Click to collapse
found a great work around, or Tomsgt123 shows how in one of his youtube videos
If updating to 5.0.0 with Rom Manager fails
using a file manager/root browser with root access go to
/preinstall/recovery select recovery.zip rename recovery.zip.bak
then go to sd card>clockworkmod>downloads>recoveries> copy the recovery.zip that has ‘shadow.zip’ in properties
go back to /preinstall/recovery and paste recovery.zip
as described in [VIDEO] How to update CWM Recovery on the Droid 2-by Tomsgt123

test test test

blindmanpb said:
Maybe this is a dumb question, but I'm not familiar with the Slitaz ISO.
So does that install a 2nd-init ROM? Or have you installed a 2nd-init ROM manually?
If you haven't, you shouldn't be selecting the 2nd-init recovery. Use the regular Droid X recovery, install the 2nd-init recovery only after flashing a 2nd-init ROM.
Click to expand...
Click to collapse
Slitaz ISO, is just a linux program used to run the magic md5 root method
no it does not install a rom
you only need to update cwm if you want to restore a nandroid backup of a 2nd init rom,
most 2nd init roms come with their own bootstrap, found in the reboot options
you shouldn't install bootstrap or update cwm unless the rom does not install bootstrap

Sorry for the previous "test test test". The forum wasn't letting me post anything until I realized I'm under the ten post threshold and I was trying to quote text that had links.
Thanks, sd_shadow, for the extremely helpful pointers. Unfortunately, I no longer have the phone in my possession, but I might be getting another one to play with soon. I'll let you know if I run into the same problems after applying your potential fixes. Thanks again!

I'm ecstatic to report that the this alternative method by Tomsgt123 worked! Here is what I wound-up doing, from start to 5.0.2.0 finish.
First the facts, all taken from settings -> About phone
System version: 4.5.621.MB810.Verizon.en.US
Model number: DROIDX
Android version: 2.3.4
Baseband version: BP_C_01.09.15P
Kernel version: 2.6.32.9-g1282440 ([email protected] #1)
Build number: 4.5.1_57_DX8-51
ERI version: 5
PRL version: 58012
Bootloader: 30.04
1. Obtain SliTaz GNU/Linux (3.0) root ISO in preparation to root phone. File I used is named Droid2_D2G_DX_DX2-RootCD-2012.iso.
2. Burn SliTaz ISO to bootable media.
3. Enter Windows and boot phone normally.
4. Ensure USB debugging is enabled via the settings -> Application settings -> Development -> USB debugging checkbox.
5. Connect phone to computer via USB cable.
6. Drag from top of phone and select the USB connection -> Charge Only radio button.
7. Boot computer via SliTaz.
8. Choose option 3 (Root Droid X) and follow onscreen directions to the letter, including putting phone in bootloader mode.
9. Boot phone normally and invoke Superuser. Immediately exit Superuser. (This step probably isn't necessary.)
10. Install Droid 2 Bootstrapper (D2B), ROM Manager (RM), and Root Explorer (RE) on phone (I used adb).
11. Invoke D2B and choose Bootstrap Recovery. When done, exit D2B.
12. Make sure phone is connected to internet.
13. Invoke RM and choose Flash ClockworkMod Recovery. Current Recovery should be 5.0.2.0.
14. Choose 3rd option, Motorola Droid X (2nd-init).
15. Tap Flash ClockworkMod Recovery. Wait until recovery files are downloaded and flashed, then exit RM.
16. Invoke RE and navigate to /preinstall/recovery.
17. Rename recovery.zip to recovery.zip.bak.
18. Still within RE, navigate to /sdcard/clockworkmod/download/download2.clockworkmod.com/recoveries.
19. Press and hold on recovery-clockwork-5.0.2.0-shadow.zip and copy the file.
20. Navigate back to /preinstall/recovery and paste the above file.
21. Rename the above pasted file to recovery.zip.
22. Exit out of RE and return to RM. Tap Reboot into Recovery and hit OK at the "Are you sure...?" prompt.
23. Phone should reboot into the 5.0.2.0 version of CWM.
Thanks again, sd_shadow. Without the above "manual" method, I would never have gotten the 5.0.2.0 version of CWM onto this phone. Now, time to play!
- Fred

And guess what? All those previous steps I carefully and deliberately outlined have been rendered obsolete by one, small apk:
http://rootzwiki.com/topic/25017-ro...workmod-flashable-updates-by-ky/page__st__190
(Still can't post links...yet.)
This is the Droid X Bootstrapper 621 MOD (DXB621). Functionally, it is the same as the old D2B except for two huge and critical features:
1. It contains CWM 5.0.2.0 out-of-the-box.
2. It works without having to do the aforementioned file manipulation inside RE.
Because of the above, it negates the need for RM (and D2B) entirely. I immediately installed DXB621 on my freshly SBF'd and rooted Droid X (see previous stats) and it worked flawlessly.
After all this, I'm convinced there is something wrong with RM as it relates to the Droid X with .621 already installed, whether via the OTA update or via SBF.
As a big bonus, after some finagling, I was also able to install HijackedBootMenu 1.1.5 621 1.1, which is a real gift, since it allows booting into CWM (or RZR) without having to first boot the phone to use either D2B, RM, or DXB621 itself.
So, the moral of this long and windy story is to simply use DXB621 for your recovery needs, don't mess with D2B and RM, and don't look back.
- Fred

nice find
I had seen that thread before, too bad the modified bootstrap isn't noted in first post, but page 20 of 110
I tried it on my D2 a955, and was able to to boot to cwm 5.0
so I will add it to my list.

sd_shadow said:
nice find
I had seen that thread before, too bad the modified bootstrap isn't noted in first post, but page 20 of 110
I tried it on my D2 a955, and was able to to boot to cwm 5.0
so I will add it to my list.
Click to expand...
Click to collapse
Yeah, getting any bootstrap to work on a Droid is the first step (after rooting) in doing much of anything, and using the most recent CWM seems to be required for all the latest and greatest ROMs, so it really should be somewhere on page 1 of that monster thread. I only stumbled across it via dumb luck.
I've run into a bizarre issue, though. With the phone connected to a running computer via USB, it won't boot into either CWM or RZR from Hijacked BootMenu (HB). Once you hit either recovery option, it just goes to a (slightly lit) black screen and stays there. The power button doesn't work at that point, so it requires a battery pull.
A clue as to what's going on might be that Windows recognizes the device when HB runs. It's only when I disconnect the cable before booting the phone that either recoveries invoke normally. Very strange.
I currently have CMKang.b3 loaded on the phone. I was pleasantly surprised to see that both the Camera and Torch apps work just fine, as I thought both were inoperable under CM9. This specific build is 9-20130120-UNOFFICIAL-shadow.
- Fred

sd_shadow said:
found a great work around, or Tomsgt123 shows how in one of his youtube videos
If updating to 5.0.0 with Rom Manager fails
using a file manager/root browser with root access go to
/preinstall/recovery select recovery.zip rename recovery.zip.bak
then go to sd card>clockworkmod>downloads>recoveries> copy the recovery.zip that has ‘shadow.zip’ in properties
go back to /preinstall/recovery and paste recovery.zip
as described in [VIDEO] How to update CWM Recovery on the Droid 2-by Tomsgt123
Click to expand...
Click to collapse
THANK YOU! I was having a similar problem as the OP, and this FINALLY fixed it!

also take a look at the modified d2 bootstrap that has been upgraded to cwm 5.0
will save a few steps if you have to reinstall
edit: I have rewritten my instructions here
[HOW TO] Install/Use Droid 2 Bootstrap

The modified Bootstrap is the trick. Straight to CWM 5.0. Took me a long time to figure out that ROM manager appears to update CWM but does not work. I found ROM manager to be of no use or value at all to me and don't install it or delete it.

Got 11 Open
Looking for an answer myself. Currently trying to install using Rom Manager then using button presses to get into Recovery. Will post update shortly.