Database Users

GTAB legacy recovery options (3588 Recovery Pack, cwm .8, 3588 recovery)

PART1: GTAB 3588 Recovery Pack
IMPORTANT NOTE: THESE WILL ONLY WORK WITH 1.1-BASED ROMS!!!!! The new Viewsonic build 4349 does NOT work with these!!!
What this is
A set of tools to flash recovery within a rooted GTablet. This pack includes stock 3588 and bekit's .8 clockworkmod recovery, the flash_img utility, and a Terminal Emulator. This is completely mod-agnostic and should be able to work on most rooted mods. Do NOT use this on 1.2-based stock or mods!!!!
This pack will be built into TNT Lite 4.3.0 and gADAM 1.3.0. I am supplying this pack for all other rooted "legacy" 1.1-based mods out there.
Installation Instructions
This is in an update.zip format. Extract the rar to the root of your internal memory, so that you have a recovery folder and an update.zip. You'll need the apk folder only if you wish to install the Terminal Emulator via a sideload.
Run either standard or clockworkmod recovery and install the same way you would install any ROM. Again, this is only a small set to tools, not a full ROM!
Usage
a) To flash recovery to 3588 stock recovery, using your GTablet
- Download the app "Android Terminal Emulator", by Jack Palevich. Or sideload it (the apk is in the RAR file)
- Run the app, toggle the soft keyboard and change the font settings, if desired (default is very small)
- Type "su" (Superuser should allow su access. If not, you are not rooted and cannot use this!)
- Type "fixrecovery.sh". This should run the flash_image tool and complete in 5-10 seconds
Reboot into recovery to test. 3588 stock has no options, so assuming you have no update.zip in the root of your /sdcard, it should just error out with an "!" error (that's what we want to see).
b) To flash recovery to clockworkmod .8 bekit version recovery, using your GTablet
- Follow steps 1 to 3, above
- Type "cwmrecovery.sh". You should the flash_image tool run and complete
Reboot into recovery to test. You should see the clockworkmod .8 bekit screen, which means the flash was successful.
c) To flash either recovery with adb
Just use an "adb shell" and then run the shell script needed. Again, this requires root access.
Download
3588 Recovery Pack v1.0 Link: http://www.mediafire.com/?1k1zlrsb4f8tkol
md5sum: 34190022d178a9e22494527103de7eac
(update on 3/23/2011)
=====================================
PART2: Clockworkmod .8 bekit (legacy version)
What this is
This is the legacy clockworkmod for 1.0.1-1.1 ROM's (ie. VEGAn, gADAM, TnT Lite 1.x-4.x, etc). It's an update.zip package to flash to clockworkmod, and is OS and hardware agnostic. Do NOT use this on 1.2-based stock or mods!!!!
Installation Instructions
This is in an update.zip format. Extract the main ZIP to the root of your internal memory, so that you have a recovery folder and an update.zip.
Testing
Reboot into recovery. If you see "clockworkmod .8 bekit" in the title, then it is installed.
Download
clockworkmod .8 bekit Link: http://www.mediafire.com/?dvleg4oatkfxm7w
Alternate Link: http://www.megaupload.com/?d=DHOASVPG
md5sum: d34079a1f0e83d8c4e09efe78cda0cc3
(updated on 11/9/2010)
=====================================
PART3: Stock 3588 Recovery Standalone
What this is
This is the stock 3588 recovery for 1.0.1-1.1 ROM's (ie. VEGAn, gADAM, TnT Lite 1.x-4.x, etc). It's an update.zip package to flash to 3588 stock recovery, and is OS and hardware agnostic. Do NOT use this on 1.2-based stock or mods!!!!
Installation Instructions
This is in an update.zip format. Extract the rar to the root of your internal memory, so that you have a recovery folder and an update.zip.
Testing
Reboot into recovery (and ensure you have no update.zip in the root of your device). Standard recovery is very simplistic - if you get an "!" error, you most likely have standard recovery installed.
Download
3588 Stock Recovery Link: http://www.mediafire.com/?97o1jc7ceth8hp7
md5sum: 983ca4efe81ced2604ccdebc5aedfbb9
(Updated on 3/23/2011)

Is this the 'writing on the wall' concerning 3991? Or just another tool?

joe2262 said:
Is this the 'writing on the wall' concerning 3991? Or just another tool?
Click to expand...
Click to collapse
The need for a way to get back to 3588 recovery has been coming up lately - this is a way to address that.

excellent work as always roebeet...if u don't mind just 1 suggestion...when i write my tutorials and such i try to keep things as generic as possible for easier future changes. might i suggest to make your job easier in the future to change the 3588 wording and such to something like latest vs stock or something similar? then all you have to do is update the link and link's descriptor. same thing with cwm i suppose. regardless, this is definitely sticky worthy IMO. great work

flipovich said:
excellent work as always roebeet...if u don't mind just 1 suggestion...when i write my tutorials and such i try to keep things as generic as possible for easier future changes. might i suggest to make your job easier in the future to change the 3588 wording and such to something like latest vs stock or something similar? then all you have to do is update the link and link's descriptor. same thing with cwm i suppose. regardless, this is definitely sticky worthy IMO. great work
Click to expand...
Click to collapse
I actually worded this with future proofing in mind. It will likely always stay 3588.
I have to see if the next VS firmware changes things - if it does, 3588 is a term we will all be using. Or "1.1" or "legacy".

Roebeet,
Just to clarify, if I wanted to go back to 3588 from TNT 5.0.1 (TwoTapsx), I just use the native recovery mode of TwoTapsx to load the 3588 update.zip file and then install clockworkmod .8?
The 3588 recovery packs and procedures mentioned here would or would not also work to down grade from 3991 to 3588?
Thanks,
Gramps..

roebeet said:
I actually worded this with future proofing in mind. It will likely always stay 3588.
I have to see if the next VS firmware changes things - if it does, 3588 is a term we will all be using. Or "1.1" or "legacy".
Click to expand...
Click to collapse
ahh, gotcha. even better then

Gramps said:
Roebeet,
Just to clarify, if I wanted to go back to 3588 from TNT 5.0.1 (TwoTapsx), I just use the native recovery mode of TwoTapsx to load the 3588 update.zip file and then install clockworkmod .8?
The 3588 recovery packs and procedures mentioned here would or would not also work to down grade from 3991 to 3588?
Thanks,
Gramps..
Click to expand...
Click to collapse
I amcurious about this too. Assume I flash to a rom with the new recovery, can I get back to 3588 with these tools?

ramerco said:
I amcurious about this too. Assume I flash to a rom with the new recovery, can I get back to 3588 with these tools?
Click to expand...
Click to collapse
I have to revamp my instructions, but the gist of it is this: You just run 3588 stock ROM, against the TNT Lite 5 / TTx standard recovery. That standard recovery will downlevel the bootloader, which the critical part to avoid a brick.
TNT Lite 4.3.0 and gADAM 1.3.0 should also work, but for the sake of my sanity I'm just going to recommend running 3588 stock as a backout.

Gramps said:
Roebeet,
Just to clarify, if I wanted to go back to 3588 from TNT 5.0.1 (TwoTapsx), I just use the native recovery mode of TwoTapsx to load the 3588 update.zip file and then install clockworkmod .8?
The 3588 recovery packs and procedures mentioned here would or would not also work to down grade from 3991 to 3588?
Thanks,
Gramps..
Click to expand...
Click to collapse
Yeah ... I'm wondering the same too
Also wondering should I follow PART1, PART2 and PART3 for recovery process?

roebeet said:
I have to revamp my instructions, but the gist of it is this: You just run 3588 stock ROM, against the TNT Lite 5 / TTx standard recovery. That standard recovery will downlevel the bootloader, which the critical part to avoid a brick.
TNT Lite 4.3.0 and gADAM 1.3.0 should also work, but for the sake of my sanity I'm just going to recommend running 3588 stock as a backout.
Click to expand...
Click to collapse
Roebeet,
If I have installed clockworkmod for TNT Lite 5, can I just flash update using CWM from image downloaded from PART3 ?

All of the Part 1-3 instructions address versions 1.0.1 - 1.1 (the first generation of ROMs
and software) as far as I can understand. Will there be a "Part 4" like
them to address the 1.2 software -- 3991 and TTx (since I have both and will have to
go back eventually.
Rev
EDIT -- I changed this post to what I want to know so I wouldn't muddy the waters.

butchconner said:
All of the Part 1-3 instructions address versions 1.0.1 - 1.1 (the first generation of ROMs
and software) as far as I can understand. Will there be a "Part 4" like
them to address the 1.2 software -- 3991 and TTx (since I have both and will have to
go back eventually.
Rev
EDIT -- I changed this post to what I want to know so I wouldn't muddy the waters.
Click to expand...
Click to collapse
thank you butch, so i wait for roebeet to post part 4 then

butchconner said:
All of the Part 1-3 instructions address versions 1.0.1 - 1.1 (the first generation of ROMs
and software) as far as I can understand. Will there be a "Part 4" like
them to address the 1.2 software -- 3991 and TTx (since I have both and will have to
go back eventually.
Rev
EDIT -- I changed this post to what I want to know so I wouldn't muddy the waters.
Click to expand...
Click to collapse
There will be, if it's needed. I might update the title and move things around, or create a new thread. It's hard to know until I see what gets released.
"1.0.1" and "1.1" are the stock ROMs we currently have (3588 is actually 1.1-3588, for example). 3991 UAT is "1.2".

So what would the process be to revert from 3991 and TT?
To make sure -- I run the Part I need above using the recovery
in 1.2 (3991 and TTx).
Rev

dony71,
My bad. I said I was trying not to muddy the waters and in asking what
I wanted to know I did just that. My apologies.
Since I didn't see an option for UAT 3991 and TTx (1.2 versions) in the original first post, I was wondering if roebeet was going to add another section explaining in
detail the procedure for them.
Rev

butchconner said:
dony71,
My bad. I said I was trying not to muddy the waters and in asking what
I wanted to know I did just that. My apologies.
Since I didn't see an option for UAT 3991 and TTx (1.2 versions) in the original first post, I was wondering if roebeet was going to add another section explaining in
detail the procedure for them.
Rev
Click to expand...
Click to collapse
It's going to go into the TTx thread, initially (it's my giant list of To Do's). That's because "1.2" isn't released yet.

Thanks for the clarification.
Rev

Roebeet
This should eliminate many questions from new rooters as the original recovery instructions have been modified so many times. Thanks again for making a fairly simple process even simpler

Easy to understand and simple method to recover. Thanks Roebeet.
Will this work to return to stock 1.1 from 1.2.4349 ?

[HOWTO] Update to 4.0.3 OTA ICS from any version with Root access (For I9020T/I9020A)

Okay First of all download the following files
a)http://android.clients.google.com/packages/ota/google_crespo/VQ8PQk_V.zip (4.0.3 OTA)
b)http://android.clients.google.com/p...a25375426.signed-soju-ota-189904.1ada2537.zip (2.3.6 Official I9020T Build)
c)http://bit.ly/su2361ef (SU flashable)
d)http://forum.xda-developers.com/showthread.php?t=988686 (Grab recovery form this thread)
e)http://developer.android.com/sdk/index.html (Grab the android SDK installer)
f)http://attachments.xda-developers.com/attachment.php?attachmentid=687157&d=1313224429 (Radio file only required for I9020A)
Okay so when done with all that proceed as follows
1) Backup your current apps using Titanium Backup (Optional/Recommended)
2) Backup(Nandroid) your rom using backup option in CWM (Optional/Recommended)
3) Do a full wipe, wipe sdcard, system, data, cache Transfer a,b,c,f to your phone.
4) Flash the 2.3.6 Official I9020T Build you had downloaded using the install zip option in CWM (IMP-DO NOT REBOOT RIGHT NOW)
5) Flash the flashable SU file you had downloaded and then reboot.
6) Once your phone is on, continue to set up your account or skip it as you wish. (Optional)
7) Open up market, download the latest SU app, Voodoo OTARootKeeper, Titanium Backup and any other app you use that requires root.
8) Open the updated SU app, hit menu button and click preferences, go all the way down, click on su binary(tap to check for updates) , and make sure it updates to v3.0.3
9) After that is done, open and allow root permissions to all your root apps. (This is important)
9.5) Run Voodoo OTARootKeeper and click on protect root, make sure all options get checked.
10) Turn off phone, keep volume up and power pressed to boot into fastboot.
11) Select recovery with volume buttons and use power to launch.
12) Once you see a android bot image and an arrow image, keep volume up pressed and press power once, then you'll see some options appear.
13) Select apply update option and find the official 4.0.3 OTA file you had downloaded and flash. Reboot.
14) Once you have booted into ICS, go to Voodoo OTARootKeeper and select resture Root, all options should now be ticked, if not something went wrong.
15) Voila, you have root. Now to get back CWM recovery you can follow this -
i) Place the recovery img file in the android sdk platform-tools folder
ii) Switch to the directory where you unzipped the Android SDK & go to "tools"
iii) Then type "fastboot flash recovery yourfilename.img" & hit enter
iv) That should do it.
v) Optionally you may do it form Rom Manager too, if it works.
16) (ONLY FOR I9020A) Reboot phone, turn it off, boot into fastboot, select recovery, CWM should launch, flash the radio file you had downloaded to get radio working on I9020A (ONLY FOR I9020A)
Root only works for the apps that were installed while on 2.3.6
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip , use this root file, flash it in cwm, everything works, permissions etc.
This might work for other variants, tested on I9020A and I9020T, I take no responsibility for anything that might go wrong with your device. I take no credit for any links or procedures provided in this guide, I just tested and compiled.
Thanks and best of luck.

..........

Good guide but first two links are broken.

bajansurfer said:
Good guide but first two links are broken.
Click to expand...
Click to collapse
Thanks, fixed.

Do I really need to flash official 2.3.6 before ICS? what if I wipe and format then install 4.0 immediately?

poging22 said:
Do I really need to flash official 2.3.6 before ICS? what if I wipe and format then install 4.0 immediately?
Click to expand...
Click to collapse
Might not work, though you can try, if it fails, do it my way, also its impossible to get any kind of root that way.

Link for the ATT Radio doesnt seem to be working

Great work!
wipe SD card?
Is this necessary?

I don't think it's necessary to wipe the SD card, I followed the procedure in http://forum.xda-developers.com/showthread.php?t=1396913 and although it said my SD card would be wiped, everything was still there after I was done!

Anyone on a i9023 tried this?

Hmm...does "any version" includes M200(Korean Nexus S)?
Sent from my Nexus S using Tapatalk

http://attachments.xda-developers.com/attachment.php?attachmentid=687157&d=1313224429
I think he meant that for the 9020A radio

Link fixed, sorry for that, SD wiping might not be necessary, but I suggest as it makes it cleaner. Might work for I9023 and M200, I have no clue, maybe some experienced developer can answer that better.

Not to crap on a great tutorial, This is exactly what I would be looking for if I were not already set up and running. Last night was a dizzying whirlwind of flashing, high heart rates and finally becoming familiar with fastboot and flashing things like that.....lol
But in the end I simply found a cwm flashable zip without radio or bootloader and installed through cwm like any other rom. As far as root all I did was flash a zip file found on the forums and I was good to go.

Hi mine keeps hanging in the boot animation and can't get into recovery, what else can i do? Is my phone bricked?

little hiccup at step 12. im getting the android bot with exclamation mark but i press volume up with power and nothing happens. menu doesnt show up....
Edit: NVM... i pressed it 3 or 4 times and it finally worked

Michie23 said:
Hi mine keeps hanging in the boot animation and can't get into recovery, what else can i do? Is my phone bricked?
Click to expand...
Click to collapse
You should post it in questions, I cannot answer this.

fromthestars said:
Not to crap on a great tutorial, This is exactly what I would be looking for if I were not already set up and running. Last night was a dizzying whirlwind of flashing, high heart rates and finally becoming familiar with fastboot and flashing things like that.....lol
But in the end I simply found a cwm flashable zip without radio or bootloader and installed through cwm like any other rom. As far as root all I did was flash a zip file found on the forums and I was good to go.
Click to expand...
Click to collapse
Many ways of doing it, I just am suggesting one, the flashable zip for ics isn't available as yet, what did you flash?

i9020 keeps getting status 7 aborted and my padlock is still unlocked on t-mobile 2.3.6

Has any tried this on an i9023? Thank u
Sent from my Nexus S using xda premium

Useful Files if You are Having Problems Updating to ICS

A lot of people seem to have the same broken files so I figured I would post a few here. These are all from a US 32GB TpT on OTA2.5 but should work for any US TpT:
Original generic.kl
Original wpa_supplicant
Original gps.conf
Original busybox
My US OTA2 clean nandroid backup (not completely clean, you will need to replace Generic.kl and wpa_supplicant with the files provided above) If you are totally screwed up you can restore this in CWR, replace the two files mentioned, and then proceed to update normally (OTA2.5 then ICS). For US Tablets only!!!
A bunch of system files (I think this was copied when I was still on OTA1 but maybe some files will still be useful if they weren't patched).
The update.zip I flashed to restore stock recovery before updating to ICS. Use at your own risk, it has only been tested once by me. This should not be necessary but may help if you are getting the indigo failure message as I got that message in CWR but not with stock recovery.
Don't change any system files in ICS until someone gets CWR working: if you break your system without CWR you're gonna have a bad time.

I think you should mention which location each file is located at.

bigsnack said:
I think you should mention which location each file is located at.
Click to expand...
Click to collapse
I agree. I need to try this method but need help with the locations of the files that need to be streamlined into the nandroid backup provided.
Hope someone could help out.
Update:
1. Replace generic.kl @ this location: /system/usr/keylayout/
2. Replace wpa_supplicant @ this location: /system/bin/

Getting some MD5 mismatch when I try to restore your backup x.x

yahoowizard said:
Getting some MD5 mismatch when I try to restore your backup x.x
Click to expand...
Click to collapse
Redownload the file. I restored from the nandroid backup posted without MD5 chechsum error. Sometimes files get corrupt while downloading.

Blanco954 said:
Redownload the file. I restored from the nandroid backup posted without MD5 chechsum error. Sometimes files get corrupt while downloading.
Click to expand...
Click to collapse
Nope, happening again x.x

yahoowizard said:
Nope, happening again x.x
Click to expand...
Click to collapse
I've seen this happen before on different Android phones I owned that had CWR installed. I could not restore my backup due to MD5 checksum mismatch. It might be attributed to the version of CWR you have and the version used to create it.
What exactly is happening in your case? I didn't necessarily had to load this restore, the only problem with my upgrade was the "Indigo" error. I went thus route cause I was anxious and didn't research my problem. Need to practice some more self control before I hose my TPT. Maybe we can pitch in and help you figure something out.
Sent from my DROID RAZR using xda premium

E: failed to verify whole-file signature
E: signature verification failed
Then it aborts. It's not as specific as busybox or Indigo or any of the other errors people have been getting, so not sure what I'm supposed to be fixing.

yahoowizard said:
E: failed to verify whole-file signature
E: signature verification failed
Then it aborts. It's not as specific as busybox or Indigo or any of the other errors people have been getting, so not sure what I'm supposed to be fixing.
Click to expand...
Click to collapse
I assume your attempting to install the OTA that was downloaded to the tablet. I am not an expert but this error your getting is due to not having the stock recovery installed. There's a post on this forum where you can download the Lenovo ICS update files. Make sure you are stock with bloat. Download that pair of files and place them on the root of your SD card.. If you made a nandroid backup of stock OS when you rooted your tablet restore that backup. Temp unroot with OTA rootkeeper. Reboot to recovery and choose to install the update from SD card via CWR. Make sure its the large file first. You might get an assert check error "Indigo" if so you will need to restore the stock recovery using the file GodfatherIP linked in OP. Once you have restored stock recovery the update should install without a problem and you can enjoy ICS on TPT. It is way better than broken GB.
Sent from my DROID RAZR using xda premium

jhankinson said:
A lot of people seem to have the same broken files so I figured I would post a few here. These are all from a US 32GB TpT on OTA2.5 but should work for any US TpT:
Original generic.kl
Original wpa_supplicant
Original gps.conf
Original busybox
My US OTA2 clean nandroid backup (not completely clean, you will need to replace Generic.kl and wpa_supplicant with the files provided above) If you are totally screwed up you can restore this in CWR, replace the two files mentioned, and then proceed to update normally (OTA2.5 then ICS). For US Tablets only!!!
A bunch of system files (I think this was copied when I was still on OTA1 but maybe some files will still be useful if they weren't patched).
The update.zip I flashed to restore stock recovery before updating to ICS. Use at your own risk, it has only been tested once by me. This should not be necessary but may help if you are getting the indigo failure message as I got that message in CWR but not with stock recovery.
Don't change any system files in ICS until someone gets CWR working: if you break your system without CWR you're gonna have a bad time.
Click to expand...
Click to collapse
i have just restored your nandroid and also put hte two files you mentioned in place (Original generic.kl and Original wpa_supplicant). i am using a 64GB USA TPT too. i plan to make an updated nandroid before i try ota 2 and then ics and if all goes well, i'll post the updated nandroid in this thread.
update1:
after doing the above, i then:
-restored the stock recovery after your nandroid, rebooted twice still on cwr recovery
-did not seem to work at first however i then reran an custom update.zip for 0089US_CWR
-did a check for updates and noticed it went to the stock recovery update
-now am updating to ics!! hopefully that will go through smoothly.
update2:
-getting busybox assert error, putting busybox file in play next. used voodoo rootkeeper to make backup to keep root on ics too. temp unrooted, trying update again. :fingers-crossed:
update3:
ICS!!!!!!!!!!!!!!!!!! i'll post nandroid later today and can confirm these files combined w/a cwr update to 0089 got me out of my failed update funk. thanks again all!
My Contribution/Files:
note: i have a 64GB USA TPT (1839-27U). was running CWR and was rooted.
-USA, OTA2 Nandroid w/Original generic.kl and Original wpa_supplicant in place. You will still need to add back the busybox file after you update to 0089
nandroid zip
-0089 CWR update zip (not made by me, found somewhere on xda)
cwr update zip

seamonkey420 said:
i have just restored your nandroid and also put hte two files you mentioned in place (Original generic.kl and Original wpa_supplicant). i am using a 64GB USA TPT too. i plan to make an updated nandroid before i try ota 2 and then ics and if all goes well, i'll post the updated nandroid in this thread.
update1:
after doing the above, i then:
-restored the stock recovery after your nandroid, rebooted twice still on cwr recovery
-did not seem to work at first however i then reran an custom update.zip for 0089US_CWR
-did a check for updates and noticed it went to the stock recovery update
-now am updating to ics!! hopefully that will go through smoothly.
update2:
-getting busybox assert error, putting busybox file in play next. used voodoo rootkeeper to make backup to keep root on ics too. temp unrooted, trying update again. :fingers-crossed:
update3:
ICS!!!!!!!!!!!!!!!!!! i'll post nandroid later today and can confirm these files combined w/a cwr update to 0089 got me out of my failed update funk. thanks again all!
My Contribution/Files:
note: i have a 64GB USA TPT (1839-27U). was running CWR and was rooted.
-USA, OTA2 Nandroid w/Original generic.kl and Original wpa_supplicant in place. You will still need to add back the busybox file after you update to 0089
nandroid zip
-0089 CWR update zip (not made by me, found somewhere on xda)
cwr update zip
Click to expand...
Click to collapse
Excellent post. Thanks for your contribution, these files will come in handy for other members that are in a pinch.
Sent from my DROID RAZR using xda premium

seamonkey420 said:
update3:
ICS!!!!!!!!!!!!!!!!!! i'll post nandroid later today and can confirm these files combined w/a cwr update to 0089 got me out of my failed update funk. thanks again all!
My Contribution/Files:
note: i have a 64GB USA TPT (1839-27U). was running CWR and was rooted.
-USA, OTA2 Nandroid w/Original generic.kl and Original wpa_supplicant in place. You will still need to add back the busybox file after you update to 0089
nandroid zip
-0089 CWR update zip (not made by me, found somewhere on xda)
cwr update zip
Click to expand...
Click to collapse
Is there a version for 16gb US models, because I am getting MD5 mismatch.

bigsnack said:
Is there a version for 16gb US models, because I am getting MD5 mismatch.
Click to expand...
Click to collapse
i wonder if you can re-generate the MD5 checksum for the nandroid?
i'll find that post and link to it below:
http://forum.xda-developers.com/showthread.php?t=976453&page=2
For anyone who has had the Clockwork-mod Recovery MD5 mismatch! error.
Update: thanks Exca
If you have androids SDK ( ADB installed) try this easer method by Exca
This is a much easier way:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick

This thread may save me. I'll try it and post back.

Going to stock without CWM

Hey guys. This is my first post. Okay so I have a Iconia A500, running Lightspeed_4.5. I flashed this a while ago, I don't even remember how I rooted it. Here's one of the problems, I don't have any type of Recovery. I tried using the Acer Recovery app to put a recovery but that will not work. I just want to go back to STOCK with NO ROOT. Also i'm a noob at all of the stuff, so please make it simple.

arupp654 said:
Hey guys. This is my first post. Okay so I have a Iconia A500, running Lightspeed_4.5. I flashed this a while ago, I don't even remember how I rooted it. Here's one of the problems, I don't have any type of Recovery. I tried using the Acer Recovery app to put a recovery but that will not work. I just want to go back to STOCK with NO ROOT. Also i'm a noob at all of the stuff, so please make it simple.
Click to expand...
Click to collapse
Head to this thread and download one of the FULL packages HC or ICS take your pick...
Unzip it and extract the "update.zip" -
Copy to your external sdcard - it must be named update.zip not update.zip.zip!!
Power Off your tab
Hold volume down button and power on again
Tab should display "erasing data, erasing cache" and then begin the update process
If you have trouble unzipping, the file will need "decrypting" see that attachment for the decrypt tool...Your antivirus will see this tool as a trojan but don't worry its fine....run the tool and add your zip as input...in a minute or two in the output box - you'll see a "......decrypted.zip" . then you're good to extract the update.
Also make sure you use a FULL package not an Update package - i know the terminology is confusing - you want an update.zip from the FULL package, not an update from the update package

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