Database Users

[Recovery] [17-Mar-2010] RA-eris-v1.6.2

This recovery is NOT yet fully compatible with the new apps2sd method! (as implemented in CM5.0.7)
This is a custom recovery based on Cyanogen's recovery source with a lot of things added by me. The purpose of this recovery is to avoid using adb by accessing all features directly from the menu.
This recovery is for the HTC Eris only, if you have a :
- HTC Dream/G1 you should go here.
- HTC Magic/MT3G you should go here.
- HTC Hero you should go here.
- HTC Sprint Hero you should go here.
- HTC Nexus One you should go here.
Use the trackball (up+down) to navigate through the menu, press the trackball to select items. Use the Volume-down key to go back to a previous menu.
Always check recovery.log before posting your issues!
Please make sure that your ROM supports apps2sd if you plan to use the ext-features! (/system/sd MUST be available in the ROM)
Ext4 is currently NOT supported (will add it as soon as I get an .29 Eris kernel compiled)
Features
full ADB access in recovery mode
Awesome Care-Bear version! (Blame packetlss for talking me into it )
Busybox v1.15.3
Kernel with ext3 support (NO Ext4 support)
HW-Key navigation (Trackball + Volume-key) option
Extended menu :
Reboot system now :: reboot your phone
USB-MS Toggle :: enable/disable USB mass storage (use when the phone is connected to your PC)
Backup/Restore
Nand backup :: Make a Nand backup, the following partitions are NOT included :
Recovery (to avoid restoring old version)
Cache (no need to backup imo)
Misc (no need to backup imo + restore issues on some phones)
Splash1+2 (no need to backup imo + restore issues on some phones)
Nand + ext backup :: Make a Nand + ext backup
Nand restore :: Restore a Nand backup
BART backup :: Make a BART backup (Nand + ext)
BART restore :: Restore latest BART backup
Flash zip from sdcard :: Flash a zip update file from your sdcard
Wipe
Wipe data/factory reset :: Wipe /data and /cache
Wipe Dalvik-cache :: Wipe Dalvik-cache both on /data and ext
Wipe SD:ext partition : Wipe the ext partition on your sdcard
Wipe battery stats : Wipe the battery stats in /data
Wipe rotate settings : Wipe the sensor settings in /data
Partition sdcard
Partition SD :: Interactive SD partitioning
Repair SD:ext :: Repair the ext partition
SD:ext2 to ext3 :: Convert ext2 to ext3
SD:ext3 to ext4 :: Convert ext3 to ext4
Other
Fix apk uid mismatches :: Does extacly that
Move apps+dalv to SD :: Moves all apps and Dalvik-cache to sdcard (This will NOT enable apps2sd!)
Move recovery.log to SD :: Moves the recovery log file to your sdcard. (Use when you want more detailed recovery log information)
Power off :: Powers off your phone
Scripts available via adb :
Nandroid v2.2.1 : enter "nandroid-mobile.sh" to start.
BART v1.0.1 (Backup and Restore Tool) : enter "utility" to start.
switchrom.sh V1.1 : enter "switchrom" or "u" to start.
sdparted v0.6 : enter "sdparted" to start.
Download
ALWAYS check the md5sum to make sure the zip isn't corrupted.
Click on the Mirror-link if you don't like rapidshare
Latest :
recovery-RA-eris-v1.6.2.img (Click here to download from a Mirror) - MD5Sum: e3932991f097993602af3c7a4b61a4f8
Special thanks to :
packetlss for all the hours of support and awesome coding skills, THANKS man ^^, donate to Haiti
Koushik Dutta for the unyaffs binary code fix and help ^^
Cyanogen for his dedicated work! , buy him a beer!
JesusFreke for his awesome JFv1.43's recovery , donate
pensive for adding awesome features to Nandroid
Bkmo for his utility script!
Devsk for his switchrom script!
51dusty for his sdparted script!
k4str0 for his fix_permissions v2.03 update.
Devsk, Dumfuq, Overground for creating BART
rikupw for the ideas and toggle_ums script.
http://www.androidspin.com for hosting ^^

works for leaked 2.1?

joey3002 said:
works for leaked 2.1?
Click to expand...
Click to collapse
Yes, it should work.

what could this do for someone with leaked 2.1 exactly?

Amon_RA said:
Yes, it should work.
Click to expand...
Click to collapse
I think he ment non-rooted 2.1 leak, in which case, no, because to install recovery, you need root.
Awesome release, great to see you got it out so fast.

edgeupgx said:
what could this do for someone with leaked 2.1 exactly?
Click to expand...
Click to collapse
No, this is only for the rooted phones. If you are running the non-rooted leaked 2.1, you cannot flash this recovery. The developers are still in the process of working on a down-grade method from leaked 2.1 to 1.5 so you can root your device.

Hoping someone magically stumbles on something that will downgrade since I really dont think anyone will just figure out how to do considering root was stumbled upon this way.

I don't see the carebear! Mine's showing an HTC logo background?

Could someone please try this version?
It's not the same as the test version I posted earlier...

GrdLock said:
I don't see the carebear! Mine's showing an HTC logo background?
Click to expand...
Click to collapse
Lol, ok, I'll add carebear versions if you really want... which color should I add?

green
the new recovery is working fine though

what is this used for?

BART not working
FYI, I just tried a BART backup and:
"Create BART backup?
Press Trackball to confirm,
any other key to abort.
Performing backup : .
Error : Run 'bart' via adb!"

hoban_eris said:
FYI, I just tried a BART backup and:
"Create BART backup?
Press Trackball to confirm,
any other key to abort.
Performing backup : .
Error : Run 'bart' via adb!"
Click to expand...
Click to collapse
Please provide log file as indicated in the first post!!

Tested
First off, thank you Amon-Ra for the recovery image. I appreciate it and I'm sure those who are trying it do too. I'm running another version on my G1 so good times.
I loaded it up and tested. I did a BART backup with no issues, Partitioned the SD card with no issues, and ran out of other things to do. Thanks again, working great.

so is this the same recovery tha was originally posted i know it has the same version 1.6.2 but was just curious as if it just had changes made to it

87jason said:
so is this the same recovery tha was originally posted i know it has the same version 1.6.2 but was just curious as if it just had changes made to it
Click to expand...
Click to collapse
The one I got from the mirror looks to be the same 1.6.2. He mentioned in the first post that this was a carebear version but I don't have that. Mine also has the ext3 to ext4 options which were supposed to have been removed.... maybe I should have gotten it from the direct link on rapidshare....

Amon_RA said:
Please provide log file as indicated in the first post!!
Click to expand...
Click to collapse
http://pastie.org/874769

Is this the stock Vsnilla Android, if not could you please make one (A ROM with Vinilla Android)

Amon_RA said:
Lol, ok, I'll add carebear versions if you really want... which color should I add?
Click to expand...
Click to collapse
Pink lol. And make it mandatory, no other options .

[MOD]OpenRecovery XT720 01 (2011-08-30) based on Androidiani

This is a modified OpenRecovery (Skrilaz_CZ) based on Androidiani Recovery (89luca89&Azhad) with some enhanced features for Milestone XT720.
Features:
Main OR menu streamlined
Most Androidiani menu options have been moved into OR > Other Utilities
Add ext3/4 support (thanks fjfalcon)
Added SD Card Utility (OR > SD Card Utility)
Added preference for display brightness in OR (OR > Settings > Brightness)
Added utility to reinstall orbootstrap (OR > "Other Utilities" > "Re-install orbootstrap")
New sh hijack binary will boot to fastboot bootloader if volume-down is held (OR > "Other Utilities" > "Re-install orbootstrap" to enable). This should be compatible with all ROMs and stock.
nandroid: removed ability to backup partitions that always fail (this means "Backup All" works now)
Fixed OR > "Wipe Dalvik Cache" bugs (previous OR/AOR don't clear them all)
Added OR > "Power Off" (helpful when phone is being stupid about charging)
Minor update to sdcard-info.txt output
XT720 basebands added (OR > Change Basebands)
Please note that although most Androidiani menu options have been included in the Other Utilities menu item, that does *not* mean I have tested them on XT720.
Installation:
Download link: http://www.multiupload.com/J8Q15SHP4S
Root the phone
Download OpenRecovery-XT720-01.zip (it contains /sdcard/OpenRecovery and /sdcard/OpenRecovery.zip)
Extract OpenRecovery-XT720-01.zip onto the SD card. This will create a /sdcard/OpenRecovery directory and an /sdcard/OpenRecovery.zip file.
Make sure you're not in USB access mode and install the bootstrap (using adb or Terminal):
Code:
su
cp /sdcard/OpenRecovery/orbootstrap/install_script.sh /tmp
chmod 755 /tmp/install_script.sh
/tmp/install_script.sh STR
Upgrading from OpenRecovery:
Download link: http://www.multiupload.com/J8Q15SHP4S
Make a nandroid and backup your sdcard
Download OpenRecovery-XT720-01.zip (it contains /sdcard/OpenRecovery and /sdcard/OpenRecovery.zip)
Rename the old /sdcard/OpenRecovery folder to /sdcard/OpenRecovery.bak
Extract OpenRecovery-XT720-01.zip onto the SD card. This will create a new /sdcard/OpenRecovery directory.
Optional: Move/copy all files from /sdcard/OpenRecovery.bak/updates to the new /sdcard/OpenRecovery/updates directory
Optional: Reboot into OR. Select "OR" > "Other Utilities" > "Re-install orbootstrap"
Github: https://github.com/Mioze7Ae/openrecovery_xt720
Thanks: skrilax_cz, 89luca89, Azhad, fjfalcon

Is this the same update that was posted in other topics?

No, it's not the same, its the next version. The biggest difference is this one merges Androidiani (the previous one was based on vanilla OpenRecovery). Maybe I should bold the new stuff.

Sorry about this but what does Reinstalling the Bootstrap mean? Don't we already use that for getting in the bootloader? Is it is it gets broken somehow?

Woodrube said:
Sorry about this but what does Reinstalling the Bootstrap mean? Don't we already use that for getting in the bootloader? Is it is it gets broken somehow?
Click to expand...
Click to collapse
If the bootloader gets broken, you won't be in OpenRecovery
Anyway, I see two reasons to use it. (1) to make 100% sure you can get back to OpenRecovery after you've flashed something experimental (say a Milestone A853 update-based ROM) or (2) you want to upgrade your bootstrap to the new version that lets you hold volume-down to boot directly into the fastboot bootloader. (i.e. in the new version volume-up==OpenRecovery, volume-down==fastboot)
Edit: that reminds me... I should make a version of the bootstrap that fixes volume-down to boot OR on Milestone XT720 running Motoroi 50R...

Mioze7Ae said:
If the bootloader gets broken, you won't be in OpenRecovery
Anyway, I see two reasons to use it. (1) to make 100% sure you can get back to OpenRecovery after you've flashed something experimental (say a Milestone A853 update-based ROM) or (2) you want to upgrade your bootstrap to the new version that lets you hold volume-down to boot directly into the fastboot bootloader. (i.e. in the new version volume-up==OpenRecovery, volume-down==fastboot)
Edit: that reminds me... I should make a version of the bootstrap that fixes volume-down to boot OR on Milestone XT720 running Motoroi 50R...
Click to expand...
Click to collapse
Very very nice... thx man

Ok so I may have run into a glitch. Hopefully it is just mine, but it has been awhile since I had updated many of the apps from the market and let me tell ya, there was a shopping list. Haha get it. Anyways, I updated them all and decided it has also been some time since I had made a backup as well.
So I went in and "tried" to make a backup of the usuals (system, data, cust, cache, cdrom and sd). I probably tried 3 or 4 times and it never backed anything up. I even deleted the openrecovery folder and re-unzipped and replaced it and tried maybe another 3 times. It would just hang on the system dumping part for 15+mins (which is way too long).
I rebooted and put the original MZor back in there (the one w/o all the AOR stuff in it-for reference). Booted into recovery and boom, made the full backup in normal time. I ran checks on sd and sd-ext several times throughout and never a problem.
Has anyone else encountered this? I had been using this since it first came out and some of the utilites and all worked fine, but now that I think of it, hadnt tried to make a back up until last night.
***Side question: Since the beginning when I first learned how to make a backup, I read that you should backup system, data, cust, cache, cdrom and sd(if neccessary). My question is why do we and does it matter if we back up the cust, cache and cdrom parts? Wouldn't these get repopulated anyways at first boot? Would everything work if we just restored system, data and sd (again if neccessary)

Woodrube said:
Ok so I may have run into a glitch. Hopefully it is just mine, but it has been awhile since I had updated many of the apps from the market and let me tell ya, there was a shopping list. Haha get it. Anyways, I updated them all and decided it has also been some time since I had made a backup as well.
So I went in and "tried" to make a backup of the usuals (system, data, cust, cache, cdrom and sd). I probably tried 3 or 4 times and it never backed anything up. I even deleted the openrecovery folder and re-unzipped and replaced it and tried maybe another 3 times. It would just hang on the system dumping part for 15+mins (which is way too long).
I rebooted and put the original MZor back in there (the one w/o all the AOR stuff in it-for reference). Booted into recovery and boom, made the full backup in normal time. I ran checks on sd and sd-ext several times throughout and never a problem.
Has anyone else encountered this? I had been using this since it first came out and some of the utilites and all worked fine, but now that I think of it, hadnt tried to make a back up until last night.
***Side question: Since the beginning when I first learned how to make a backup, I read that you should backup system, data, cust, cache, cdrom and sd(if neccessary). My question is why do we and does it matter if we back up the cust, cache and cdrom parts? Wouldn't these get repopulated anyways at first boot? Would everything work if we just restored system, data and sd (again if neccessary)
Click to expand...
Click to collapse
I don't backup cust or cdrom. I made a backup with Mz's new O.R. yesterday and good thing I backed up ext cause my XDA Special backup would not boot without it. Not much help for ya sorry bud Hope you get it worked out.

@Mioze7Ae
can you please compile a standalone APK installer version of the new open recovery for XT720?
after reading the instructions i noticed, it requires an existing open recovery already installed to apply the above updates

AllGamer said:
@Mioze7Ae
can you please compile a standalone APK installer version of the new open recovery for XT720?
after reading the instructions i noticed, it requires an existing open recovery already installed to apply the above updates
Click to expand...
Click to collapse
I tried but my re-compiled version of the OpenRecovery.apk just FC'd.
Thanks for this Mioze7Ae, this is really sweet!

Am I missing out something here? I don't seem to be able to get the additional OR menu to convert to EXT4. I flashed back to Singapore 2.1 and have rooted. Removed the previous Open Recovery folder but where do I get the OpenRecovery.apk? Do I use back the previous version?

You can use Dexter's OpenRecovery.apk to install Open Recovery & then follow Mioze7Ae's instructions in the OP to update it.

Not sure what effect it even has, but the set timezone seems to be backwards ... Selecting GMT-7 runs /bin/timezone.sh GMT+7 and selecting GMT+7 runs /bin/timezone.sh GMT-7

Hey guys, hope you can provide me with a clearer instruction. I have done exactly as per the instructions and now when I boot into recovery, I don't see the extra option to convert to EXT4. The only things I see in the menu is:
Motorola MILESTONE XT720 Open Recovery
Version 1.46
Created by Skrilax_CZ
Use Volume Up/Down to highlight:
Camera_Mode key to select.
Main Menu
Reboot Menu
Settings
USB Mass Storage Mode
Nandroid
Application Menu
Run Script
Apply Update
Wipe Dalvik Cache
Wipe Data / Factory Reset
Wipe Cache Partition
What am I doing wrong? The phone is still running 2.1 update 1 but it's rooted.

It looks like you're running the original OpenRecovery. You need to replace the OpenRecovery folder on the sdcard with the version from the OpenRecovery-XT720-01.zip.
I think I can see how the instructions about renaming might be confusing so I tweaked the phrasing a little bit.

Thanks for the reply Mioze7Ae but I followed exactly as your instructions. Here's what I've done:
-Flashed singapore_STR_U2_01.1E.0
-Rooted with SuperOneClick
-Extracted and transferred to SD the OpenRecovery folder, OpenRecovery.zip and the original OpenRecovery.apk file.
-Ran OpenRecovery.apk
-Install Recovery System. Install Sucess.
-Recovery Boot and that's where it boots into the old OR.
It's the same if I use the OpenRecovery folder provided by hellmonger in The XT720 XDA Special Final RC2 "Hellmonger Edition"

ranggie4 said:
Thanks for the reply Mioze7Ae but I followed exactly as your instructions. Here's what I've done:
-Flashed singapore_STR_U2_01.1E.0
-Rooted with SuperOneClick
-Extracted and transferred to SD the OpenRecovery folder, OpenRecovery.zip and the original OpenRecovery.apk file.
-Ran OpenRecovery.apk
-Install Recovery System. Install Sucess.
-Recovery Boot and that's where it boots into the old OR.
It's the same if I use the OpenRecovery folder provided by hellmonger in The XT720 XDA Special Final RC2 "Hellmonger Edition"
Click to expand...
Click to collapse
Change this:
Extracted and transferred to SD the OpenRecovery folder, OpenRecovery.zip and the original OpenRecovery.apk file.
Ran OpenRecovery.apk
Install Recovery System. Install Sucess.
To this:
Transferred to SD the the original OpenRecovery.apk file.
Ran OpenRecovery.apk
Install Recovery System. Install Sucess.
Extracted and transferred to SD the new OpenRecovery folder, OpenRecovery.zip

R-D said:
Not sure what effect it even has, but the set timezone seems to be backwards ... Selecting GMT-7 runs /bin/timezone.sh GMT+7 and selecting GMT+7 runs /bin/timezone.sh GMT-7
Click to expand...
Click to collapse
I think it only affects the naming of the nandroid directories, but I'll give it a look. Nice catch!

Thanks Mioze7Ae. The last instruction made it clear. It works now. Thank you so much!!!!!!!!

Mioze7Ae said:
I think it only affects the naming of the nandroid directories, but I'll give it a look. Nice catch!
Click to expand...
Click to collapse
it was like this in all the versions of open recovery...
+++++++++
Mioze, can you also add a wipe battery stats in your modified openrecovery? comes in handy when we flash a new rom or restore a nandroid so we dont have to use the battery calibrating app.

[Q] Requirements for new ROMs with different size paritions

Hey everyone.
Can any senior member write me a bit of a guide as of what do I have to do in order to switch ROMs with different partition requirements?
I am looking for as little work as possible. I am having problem making ADB run on my computer, so I need a way to do it without need of ADB. Preferably something straight from the phone. So:
Of course, first I do nandroid backup through CMR. Then what?
Do I have to get to fastboot somehow and manually change values?
Or when I download the cLK ROM version, do I just flash it through CMR by zip from SD and it will repartition automatically to fit the requirements?
Currently my system partition is 190MB, and I'd like to try a 2 roms that are 150MB and 220MB required.
Thanks in advance.

while you wait for someone to link you to the (easily findable ) guide stickies, you can flash a 150 rom to a 190 partition if you are just playing. you will waste 40 meg, but if you're planning to flash again it hardly matters.

Yeah, I figured that, but I am more interested in a quick and safe way to switch system partition size, without ADB.
and when looking at roms, i only see different requirements, but no way to change the sizes.
Would you be so kind to explain, how this repartitioning works for flashing new roms? (clk)

When you flash clockwork, there is a file in the clockwork folder on your PC called flash.cfg (beware of the second file flash.cfg.txt, , if you only see "flash" and "flash.cfg" then you need to unhide file extensions)
anyway, open notepad, drag the flash.cfg file into it and you will see something like
Boot yaffs 8m
System yaffs 150m
Data allsize
(More than just that but you get the idea)
Well, if I change the 150m to 200m, save the file, run daf.exe to instal clockwork, it will be flashed with a 200 Meg system partition.
That's all there is to it.
Each line is one partition, boot, cache, system, data,, data doesn't have a size, it has allsize so will take up whatever space is left. You generally only ever alter the system.
The nand toolkit is the easier way to do it. Same principle, but point and click.
Either way, you perform this from within magldr, "USB flasher" option.
If you are on clk not magldr, I can't help, never used it.
Edit - "without adb " ... hmm, do you mean without USB? You can't.
If you are just having driver problems, there's an install drivers (or something) button in nand toolkit, try it.

samsamuel said:
When you flash clockwork, there is a file in the clockwork folder on your PC called flash.cfg (beware of the second file flash.cfg.txt, , if you only see "flash" and "flash.cfg" then you need to unhide file extensions)
anyway, open notepad, drag the flash.cfg file into it and you will see something like
Boot yaffs 8m
System yaffs 150m
Data allsize
(More than just that but you get the idea)
Well, if I change the 150m to 200m, save the file, run daf.exe to instal clockwork, it will be flashed with a 200 Meg system partition.
That's all there is to it.
Each line is one partition, boot, cache, system, data,, data doesn't have a size, it has allsize so will take up whatever space is left. You generally only ever alter the system.
The nand toolkit is the easier way to do it. Same principle, but point and click.
Either way, you perform this from within magldr, "USB flasher" option.
If you are on clk not magldr, I can't help, never used it.
Edit - "without adb " ... hmm, do you mean without USB? You can't.
If you are just having driver problems, there's an install drivers (or something) button in nand toolkit, try it.
Click to expand...
Click to collapse
Thanks mate. That's exactly the problem, I have found guides for magldr, but never for clk.
And about adb - my pc would need an OS reinstall to run well again - vista, and i already got it pretty screwed up.
Anyway, thanks for your help, I understand it more!

CWM 5.5.0.4 for Gtab--NVFLASH only (BETA from team DRH)

THIS IS NOT CWM FLASHABLE. YOU MUST USE NVFLASH
Edit: It has come to my attention that the CWM is 5.5.0.2. This error has since been corrected. Sorry folks. I'm an idiot.
Hey, i hope this doesn't bother anyone but i compilied and easy zip for NVFLAshing the new CWM.
Thanks Fosser, Team DRH, and the BishopofTechnology (all of whoms work this is, i just put it in one place)
Included is the NVflashable info, the drivers for APX, and the new version of CWM.
Do this @ your own risk, i'm not responsible for any problems (i did test it three times, with each version of CWM, if that counts for anything)
Step 1) Get into APX mode (power + Vol-) [the screen will go black. that's what you want
Here's what the Bish says:
Step 2) Connect the GTab to the PC via the USB cable.
if your PC loads the USB driver and connects to the GTab, SKIP to the “Using NVFlash” section.
if the WINDOWS PC fails to load the driver, just click through Start/Control Panel/Device Manager and find “APX” listed in the devices with a yellow “!” (exclamation point) on the icon.
Select the APX item and find the “Update Driver” button and click it.
When it asks where to search, choose the “local computer” manual selection choice and tell it to Browse to the "Flash USB Drivers".
If you go back to Device Manager after the Windows install has completed, it will show the nVidia USB drivers near the top of the USB device list.
Click to expand...
Click to collapse
Step 3) Run the "nvflash_gtablet.bat"
A CMD prompt will pop up, let it do it's thing (don't stop or unplug during). Give it about a minute or until the CMD prompt disappears. You will the get a message that says "Entering NvFlash recovery mode / Nv3p Server"
At this point is should be okay to restart your tab. I'm running Flashback and had no problems staring up.
If you want to check the new CWM, hold the power + Vol+ when restarting and it should put you into recovery.
CONGRATS! You have the new recovery in preparation for ICS.
Once again, none of this is my work--i just put it into a convenient place.
Thanks again to all the Devs and enthusiasts. You make the Gtab worth having!
Edit 1:
Here is the MD5 check: 3DD468C48A3515E6E5A1C1236FF5068E
Edit 2:
The update recovery is with the normal sized Recovery.
Edit 3: 1) It seems this version partitions the external sd card when you choose to partition sd card. 2) choose zip from internal sdcard seems to use the internal memory 3) "FORMAT SDCARD" will FORMAT MICROSD CARD! YOU WERE WARNED

Alright. Download tested and verified. this is deff 5.5.0.4!
sorry again folks

Anyone that is interested in installing this via CWM, I created a CWM flashable verison from fosser2's download. Here is a link to the "normal font" version http://dl.dropbox.com/u/36150173/CWMR5504_recovery.zip. If you want the "big font" version, all you have to do is open the zip, delete the recovery.img, rename the Team DRM/fosser2/plastikman supplied version to recovery.zip & then add it to the zip.
I have installed this on 2 of my gTabs (one gTab Comb v3.3, the other CCCv8) and did not had any issue installing it this way.
Just a few notes on this version; it does give you the ability to flash from both the internal sd & external sd but uses a different naming convention though..."sdcard" is the name used for the external microsd slot and "internal sd" is what we would normally call sdcard. This version also appears to have fixed the "reboot recovery" bootloop bug of cwm3.0.2.8 (or aleast bypassed it)...when I selected "reboot recovery" it did the same as "reboot system now" (as I was doing this I crossed my fingers hoping it wasn't going to bootloop me...yea..no bootloop).
CWMR is touch capable. You scroll/select in 3 different ways...you can either use the capacitive buttons (which have been remapped to...Search is "select", Home is "scroll up", Menu is "Scroll down" and Back is "back"), you can also use the on screen touch controls (back, up, down & return), or you can also swipe up and down to scroll up/down and swipe sideway to select.
Al
PS:
WARNING: This is the beta6 release. The op page over in the Slatedroid gTablet Laboaratory says that selecting repartition will only repartition the EXTERNAL SD. Two users have reported magic value mismatch after repartioning with this version. plastikman, who created it says he is looking into it.

So u can install from the older cwm that's in flashback like any other zip?
Sent from my SAMSUNG-SGH-I997 using XDA App

why does it only boot into CWM mod now? it would boot normally when i was on CWM 3.x.x.x

Yes but beware of repartition bug
lsu205 said:
So u can install from the older cwm that's in flashback like any other zip?
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Yes you can. I installed on both mine from CWM 3.0.2.8.
Please note the warning I put on my previous post! It probably isn't a good ides to "repartition" with this version until plastikman finds the bug. If you need to repartition (which shouldn't be very oftern) you can always flash the old CWM (or stock recovery) via this version. The recoveries are so small that I keep a copy of each on the tablet just in case.

is the download ok i have try to unzip it and it gives me an error file is not a zip file

Alternate location
wuilly said:
is the download ok i have try to unzip it and it gives me an error file is not a zip file
Click to expand...
Click to collapse
You don't need to unzip it but it does need to be a vailid zip.
Yes, the download is OK from dropbox. I just redownloaded it to my PC & tested the archive. No erors found.
I also put it on mediafire...try this link http://www.mediafire.com/download.php?qg3n084hfu783i2 & see if it's any different for you.
Al
---------- Post added at 09:23 PM ---------- Previous post was at 09:15 PM ----------
jamcar said:
why does it only boot into CWM mod now? it would boot normally when i was on CWM 3.x.x.x
Click to expand...
Click to collapse
It shouldn't (and didn't for me). Are you sure you didn't select accidentally hit "reboot recovery" instead of "reboot system now" (since you were still in CWM3.0.2.8 untill you reboot)? If you did accidentally hit reboot recovery then it would have put you in a CWM bootloop.
There are 2 ways I've used to fixed a CWM bootloop (yes I've accidentally hit reboot recovery too)..one was is to use nvflash to format partition 7 (MSC) and the other way is to use CWM to flash stock recovery and then install CWM3.0.2.8 (for b/l1.2) via stock recovery. Formatting MSC is the fastest, but most people I suggest these fixes to choose to do the stock recovery route. If you want detailed instruction for either, let me know.
Al

Great work and thanks for putting in one spot. I'll probably wait till a ICS ROM is released with but must say that this is a great first step till we get it. Cant wait for 10" of ICS....my cappy luvs ICS...

J017373 said:
Edit 3: 1) It seems this version partitions the external sd card when you choose to partition sd card. 2) choose zip from internal sdcard seems to use the internal memory 3) "FORMAT SDCARD" will FORMAT MICROSD CARD! YOU WERE WARNED
Click to expand...
Click to collapse
What does the recovery do when you don't have a microSD card in the slot. The /etc/recovery.fstab file is setup to fall back to using the internal SD card like CWM-4.0.1.5 is. Does it work on the internal SD card if no external one is present?
---------- Post added at 09:23 PM ---------- Previous post was at 09:19 PM ----------
aabbondanza said:
and the other way is to use CWM to flash stock recovery and then install CWM3.0.2.8 (for b/l1.2) via stock recovery.
Click to expand...
Click to collapse
That procedure only works as a side effect. Simpler to wipe MSC directly. See post #3 of this thread.
Stash that zip file on you SD card, and if you accidentally select "Reboot recovery", just "flash" it to fix the always boots-to-recovery problem.

Just installed using CWM recovey and all is well. Just to test I took out my external sd card and when I went to update from sdcard it showed the content of the internal. So I am guessing that if one would decided to partition there internal sdcard they might need to pull there external out first. Then boot up recovery for there updates.

rajeevvp said:
What does the recovery do when you don't have a microSD card in the slot. The /etc/recovery.fstab file is setup to fall back to using the internal SD card like CWM-4.0.1.5 is. Does it work on the internal SD card if no external one is present?
---------- Post added at 09:23 PM ---------- Previous post was at 09:19 PM ----------
That procedure only works as a side effect. Simpler to wipe MSC directly. See post #3 of this thread.
Stash that zip file on you SD card, and if you accidentally select "Reboot recovery", just "flash" it to fix the always boots-to-recovery problem.
Click to expand...
Click to collapse
Just can't keep up with you raj...why did it take you 2 months to come up with the flashable msc format? Just kidding. I got the format msc from that very thread back in October. Everyone I've run into that is in a CWM loop I've given them the option of formating msc (via nvflash) or flashing stock recovery/then CWM. In every case they have always chosen to flash stock recovery & then flash 3028 (probably because most of the people I help are pretty new to the gTab). I think now they will choose the format via flash method. Thanks for the tip.
Just a question though. Exactly what is the CWM kernel writing to MSC to cause the loop? I assume it is the bootloader that checks for the rocker switch position & some mysterious bit on MSC to determine which kernel to load (but I'm just guessing). But if that is correct then why does flashing stock recovery, doing a normal boot & then flashing CWM fix the problem too (so I'm guessing I am wrong about my guess)? In any case can you explain why it works that way?
Al

When ahead and changed back. When trying to downgrade to a 2.2 rom ended up with a mix match error on boot up. Looked good for what it is. Expecially liked the touch option on it, but it needs some work.

nobe1976 said:
When ahead and changed back. When trying to downgrade to a 2.2 rom ended up with a mix match error on boot up. Looked good for what it is. Expecially liked the touch option on it, but it needs some work.
Click to expand...
Click to collapse
There are a couple of problems that I noticed with this version of CWM, and which might be responsible for your problems.
1. Roebeet's gtablet.cfg file which almost everybody uses to nvflash back to the 1.2 stock ROM has a bug in the system.img size calculation:
Code:
$ [B]fgrep size= roebeet.cfg[/B]
size=3145728
size=131072
size=2097152
size=131072
size=4194304
size=16777216
size=33554432
size=16777216
size=16777216
size=[B]259715200[/B]
size=0xFFFFFFFFFFFFFFFF
The second last line is the size of the "system" partition and it is misaligned. Every other partition is correctly rounded up to end at the gTablet's NAND flash erase size (128K). Compare with bekit's gtablet.cfg:
Code:
$ [B]fgrep size= bekit.cfg[/B]
size=3145728
size=131072
size=2097152
size=131072
size=4194304
size=16777216
size=33554432
size=16777216
size=16777216
size=[B]209715200[/B]
size=0xFFFFFFFFFFFFFFFF
Here all the partitions--including the last which uses the remaining available space--are rounded up to a 128K boundary. Looks like roebeet just added 50M to bekit's system.img size without rounding it up. The correct value should've been (using roebeet's system.img size as NUM):
Code:
$ [B]( NUM=$((259715200)); echo $(( (NUM + ((1<<17)-1)) & ~((1<<17)-1) )) )
[/B]259784704
--which brings us to problem no. 2:
2. The CWM-5.5.0.4 Beta 6 has a "cmdline" file containing NAND flash partition sizes which overrides the user's partition sizes read from the Partition Table. This is fine if the sizes are the same, but, a bad idea otherwise. In this CWM, the cmdline file sets "system" to be what we calculated above (259784704) but, which disagrees with the size in the PT (259715200).
Use the zip file in the attachment to empty the cmdline file out. This will cause the partition sizes to be read from the PT on the NAND flash.
My recommendation is that:
1. Users nvflash to 1.2 using either
a) the attached gtablet.cfg which has all the partitions correctly ending at 128K boundaries or
b) bekit's original gtablet.cfg. (This option is what I recommend. The "cache" partition is used for OTA updates and if it is much smaller than the "system" partition--like in roebeet's gtablet.cfg, then, depending on the size of the image, automatic updates might fail.)
2. Install the new CWM-5.5.0.4 Beta 6, and then immediately flash the attached zip file to empty out the cmdline file.

aabbondanza said:
why did it take you 2 months to come up with the flashable msc format?
Click to expand...
Click to collapse
Didn't think adb was going to be difficult for people who have no problem with nvflash...
Just a question though. Exactly what is the CWM kernel writing to MSC to cause the loop?
Click to expand...
Click to collapse
I looked at this sometime back and its complicated. I'll make a post on this later this weekend after I've looked at VS's newly posted 1.2 kernel patch.
I assume it is the bootloader that checks for the rocker switch position & some mysterious bit on MSC to determine which kernel to load (but I'm just guessing).
Click to expand...
Click to collapse
For "mysterious bit" substitute "string", but, you are correct.

Have a user over at slatedroid tried it & still got this error.
Magic value mismatch
Critical failure: Unable to start kernel.
Unrecoverable bootloader error (0x00000002)
Trying to get more info on exactly what he did to get the error.
Al

CWMR5504 Fixed
aabbondanza said:
Have a user over at slatedroid tried it & still got this error.
Magic value mismatch
Critical failure: Unable to start kernel.
Unrecoverable bootloader error (0x00000002)
Trying to get more info on exactly what he did to get the error.
Al
Click to expand...
Click to collapse
Thanks to rajeevp!!
Plastikman verified rajeevvp was correct and has issued an updated CWMR. Here it is in a flashable format http://dl.dropbox.com/u/36150173/CWMR5504_recovery.zip. He switched from using pershoot's kernel (which required the command line) to using the stock kernel. I tested the new version to install a rom, do a factory data reset, a wipe cache, a wipe dalvik & a fix permissions. All worked normally. Give it a try. I also corrected the links in my previous posts to point to the updated version.
Al

aabbondanza said:
Thanks to rajeevp!!
Plastikman verified rajeevvp was correct and has issued an updated CWMR. Here it is in a flashable format http://dl.dropbox.com/u/36150173/CWMR5504_recovery.zip. He switched from using pershoot's kernel (which required the command line) to using the stock kernel. I tested the new version to install a rom, do a factory data reset, a wipe cache, a wipe dalvik & a fix permissions. All worked normally. Give it a try. I also corrected the links in my previous posts to point to the updated version.
Al
Click to expand...
Click to collapse
Thank you. This worked well for me, since I was not inclined to do the nvflash thing. I was able to boot back into my Beasty+Clemsyn rom without incident. Tested by rebooting again and was able to boot into the rom with no issues.

aabbondanza said:
He switched from using pershoot's kernel (which required the command line) to using the stock kernel.
Click to expand...
Click to collapse
... and in the process also brought back the always-reboots-into-recovery problem, right? Whereas with the pershoot kernel "Reboot Recovery" would just reboot the tablet into the ROM?
BTW, the pershoot kernel doesn't need a cmdline file: craigacgomez's CWM-4.0.1.5 too has a pershoot kernel and its cmdline file is empty. As I mentioned before: if the cmdline file is empty, then the bootloader will construct a cmd line for the kernel.

to install the cwm recovery do I simply transfer the zip to the internal sdcard and flash zip from sdcard as if it were a rom?

clockworkmod

Hi guys, I had clockworkmod 5.0.2.6 installed but it was small(partition). I've found some clockwork mods with bigger partition(250, 400) in guide and downloaded them. I flashed them via daf and they've flashed successfully. Now, the problem is none of newer roms(ics, jb) work with that version of cwm. How to install other recovery(for eg. newer cwm)? Don't give me the guide, I'm sick of them and have a few bookmarked but there is no solution for that. Oh, I forgot. I have mag1.13 and cwm 3.0.0.8(orange one)..
Thanks in advance.

Shaumaaa said:
Hi guys, I had clockworkmod 5.0.2.6 installed but it was small(partition). I've found some clockwork mods with bigger partition(250, 400) in guide and downloaded them. I flashed them via daf and they've flashed successfully. Now, the problem is none of newer roms(ics, jb) work with that version of cwm. How to install other recovery(for eg. newer cwm)? Don't give me the guide, I'm sick of them and have a few bookmarked but there is no solution for that. Oh, I forgot. I have mag1.13 and cwm 3.0.0.8(orange one)..
Thanks in advance.
Click to expand...
Click to collapse
If your just looking to increase system partition then there is a file (flash.cfg I think) that you need to modify, open it and it should be fairly clear what to modify to increase the partition size.

I edited the flash.cfg with notepad++ and wanted to flash the same recovery again but daf is showing me some error.

first, in case you handt realised, increasing teh system size is only needed when the size required by your rom needs it, , , , so for example flashing a 200mb rom to a 400mb partition will waste 200mb, the system wont use that extra space. Your total available storage does NOT include teh system partition, sop teh bigger system partition you create, the lesws available internal storage you will have for data.
Look in the folder where flash.cfg is, , find recovery-raw.img and replace it with the new recovery .img you want to use.
Then, because of the line
recovery rrecov|ro|nospr filesize recovery-raw.img
in flash.cfg, when you run the flash it will create the correct recovery partition size.
(If the newer recovery didnt use a larger recovery partition, or if you wanted to reinstal recovery again after already doing the above, ((meaning the recovery partition is already big enough)) you would simply start cwm, and flash the new recovery from sd card, just like flashing a rom)
showing me some error.
Click to expand...
Click to collapse
completely useless sentence, you may as well not bother, how do we know what error it shows? mind reading?

This error
An error has occurred
Read below for more information
Error Description: Config load failed.
Info: .\RSPL\RSPL.cpp (725)
Error Description: CONFIG: bad data size format
Info: .\RSPL\RSPL.cpp (428)

**** yeah! I did it!
Thanks bro'

I dindn't Heeeeeeeeelp..
I installed the cwm touch and when installing rom with aroma(pacman) it stays at 0% but it's putting files to system. Then it passes the mag and stays at bootanimation. Whats wrong?
EDIT: I'm uploading video of my problem

Fixed
Fixed with magldr repartitioning. Thanks anyway.