Related
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 .
Note: I consider this obsolete and recommend rusmod
Bugfix v3
Here's the latest bugfix for Dexter's 1.3 aka stock221v13. This includes everything from Bugfix v2 and adds:
Extended power menu that adds "Reboot" and "Recovery" (see thumbnail below for a screenshot)
Include conservative governor (c19932, nadlabak)
Tweak to improve SD card read performance (reverendkjr)
DO NOT APPLY THIS TO XAVWANTED'S OR KHALPOWERS ROMS
The extended power menu requires extensive modifications to the framework. This patch includes Dexter's 1.3 framework. Don't hose your phone! I can help port the menu to the other ROMs, but this can and will bork your stuff if you're not running stock221v3 (+bugfix updates are OK).
Instructions:
Read all the instructions
Save stock221v3-bugfix-3.zip to OpenRecovery/updates/stock221v3-bugfix-3.zip
Boot to OpenRecovery
OR menu > nandroid > backup > system > backup selected
OR menu > nandroid > restore > stock221v13 > system > restore selected
OR menu > apply update > stock221v3-bugfix-3.zip
OR menu > wipe dalvik cache
OR menu > reboot system
Download:
http://www.multiupload.com/MTCIACFSJN
More details:
https://github.com/downloads/Mioze7Ae/XT720-patch
Experimental patches for bugfix v3
Experimental patches are minimally tested.
Metamorph compatibility fix
Volume-down boot to enter fastboot
Bugfix v2
Summary:
Graphics/OpenGL performance tweak (xavwanted)
Media library tweaks (xavwanted)
memhack (khalpowers) moves dalvik-cache to either /cache or /sd-ext
By default moves dalvik-cache to /cache
Will use /sd-ext/dalvik-cache instead if it exists (see also "User control of /sd-ext" below)
minfree memory parameters tweaked
Parameters from AutoKiller Memory Optimizer database
http://andrs.w3pla.net/autokiller/list/currentType/378
http://andrs.w3pla.net/autokiller/list/currentType/591
Fix milestone overclock persistence
Autodetects ext2/3 (kousik)
ext2/3 partition is checked and possibly repaired on boot
Disable automatic apps2ext. Native Froyo App2SD is not affected.
See also "User control of /sd-ext" below
apps2ext used to be called app2sd before native Froyo App2SD (apps2fat) existed. Confusing!
Add support for Link2SD
See also "User control of /sd-ext" below
Adds Maps.apk and updates YouTube.apk
User control of /sd-ext through manual creation of directories
/sd-ext/app (move /data/app to /sd-ext [apps2ext])
/sd-ext/dalvik-cache (move /data/dalvik-cache to /sd-ext)
/sd-ext/app-private (move /data/app-private to /sd-ext)
/sd-ext/link2sd (enable Link2SD 1.5.1 support)
apps2ext has priority over link2sd and overrides! It doesn't make sense to use both!
Replaces /system/oc with modular scripts in /system/etc/init.c
See the README on github for more details. https://github.com/Mioze7Ae/XT720-patch
Installation
Download and copy stock221v13-bugfix-2_signed.zip to the /sdcard/OpenRecovery/updates directory
Reboot into OpenRecovery
"Nandroid > Restore" Dexter's stock221v13 system (restoring boot not necessary)*
"Apply update" and select stock221v13-bugfix-2_signed.zip
Wipe data / factory reset*
*Advanced users: If you've been running Dexter's 1.3 (stock221v13) with the previous stock221v13-bugfix-1.zip, then it should be possible to apply bugfix-2 cleanly over stock221v13-bugfix-1.zip without first restoring system if you haven't made incompatible customizations to /system. You can also probably just clear the dalvik-cache instead of wiping, but I recommend doing that manually if you've moved it to sd-ext.
Download
http://www.multiupload.com/E7NJ9H2F9C
https://github.com/downloads/Mioze7Ae/XT720-patch/stock221v13-bugfix-2_signed.zip
Experimental patches for bugfix v2
Experimental patches are minimally tested.
Conservative governor suggested by c19932 module from nadlabak (included in bugfix-3)
reserved
this post intentionally left not blank
Disable automatic apps2ext. Native Froyo App2SD is affected.
Click to expand...
Click to collapse
Do you mean unaffected or is Froyo Native Apps2SD not working?
3rdstring said:
Do you mean unaffected or is Froyo Native Apps2SD not working?
Click to expand...
Click to collapse
Yes. You are correct native Apps2SD is NOT affected by disabling the automatic apps2ext. Thanks for catching that quickly!
tried to apply over last 1.3 bugfix patch.... "installation aborted".
I have installed it over the first bugfix. It works perfekly! Where i can see if it applied?
Whats is the diffrent between app2ext an link2sd?
c_urbanek said:
tried to apply over last 1.3 bugfix patch.... "installation aborted".
Click to expand...
Click to collapse
It's kind of a Hail Mary. It did work in my testing and I just tried it again with success. One thing is the new patch is signed so it could also be that your zip got corrupted in download. I've gotten installation aborted messages when the zip was corrupt, but there are probably other ways for it to fail. The md5sum should be
Code:
a93cfa1d6ea73a4ee8ff6ec4afc72baa stock221v13-bugfix-2_signed.zip
smoki3 said:
I have installed it over the first bugfix. It works perfekly! Where i can see if it applied?
Whats is the diffrent between app2ext an link2sd?
Click to expand...
Click to collapse
If you can see a /system/etc/init.d/00_memfree file on your phone, the update was applied.
App2ext moves all apps to the ext partition. Link2SD lets you do it selectively. This isn't a tremendous gain on Froyo, because we have the native move to SD. One difference is that using app2ext apps will be available while the sdcard is being accessed over USB. Also widgets should work for app2ext. At one point I unscientifically convinced myself that app2ext was faster at loading apps than the native move. That said, I'm not currently using either app2ext or link2sd except when testing. I did a big app purge recently and combined with the memhack I'm not running out of space (yet )
Okay the patch works very good! I have more memory now and it seems like it is very fast now! Great work
Thanks for this new update.
I have installed the patch stock221v13-bugfix-1, means that the new patch stock221v13-bugfix-2_signed what I can get to the Updates folder and apply it without restoring the data from the factory?
Means that the Dalvik-cache will automatically be going to SD?
Still need to partition the SD?
What about applications that are currently in the SD, which were moved to app2sd?
Thanks!
Tavinsky said:
Thanks for this new update.
I have installed the patch stock221v13-bugfix-1, means that the new patch stock221v13-bugfix-2_signed what I can get to the Updates folder and apply it without restoring the data from the factory?
Means that the Dalvik-cache will automatically be going to SD?
Still need to partition the SD?
What about applications that are currently in the SD, which were moved to app2sd?
Thanks!
Click to expand...
Click to collapse
By default, what bugfix-2 does is move dalvik-cache to a different partition inside the phone, not to the SD card. /data and /cache are two different internal partitions. /data is what the phone GUI calls "Internal memory", but both are internal.
Why do this?
Eclair 2.1 wasn't designed for JIT so dalvik-cache didn't exist. New in froyo 2.2, JIT creates a lot of data in /data/dalvik-cache (at least 50mb, often 70-80mb). To accommodate for this increased use of /data in the Korean Motoroi froyo, Motorola adjusted the partitions to take 50mb from /cache and 20mb from /system to grow /data by 70mb. Dexter's 1.3 is built off of the 2.1 kernel and partitions and we can't change Motorola's partitioning (because of locked bootloader). So we end up losing space from /data. What we can do is put dalvik-cache on /cache (the one Motorola shrank) instead. That's what the update does.
Moving dalvik-cache to sd-ext is different. If you did not do that while running bugfix-1 (believe me you would know if you did), then you should be able to just apply bugfix-2, select wipe dalvik and reboot (the first boot after wiping dalvik is always slow). It should find your apps. There is a small chance you will have to wipe data / factory reset. I cannot guarantee it will work in all circumstances but it's worth a try. Take a nandroid backup of system, data, cache before applying bugfix-2 just to be safe.
If you did move dalvik-cache to sd-ext, then OpenRecovery doesn't know how to wipe dalvik-cache correctly, so you'd have to do that manually. If you set up dalvik-cache on sd-ext, then you probably already know how ways to do that.
It should not affect any apps that are on SD.
If I was really clever I would figure out how to make the update clear dalvik-cache on install... hmmmm.
By default, what bugfix-2 does is move dalvik-cache to a different partition inside the phone, not to the SD card. /data and /cache are two different internal partitions. /data is what the phone GUI calls "Internal memory", but both are internal.
Why do this?
Eclair 2.1 wasn't designed for JIT so dalvik-cache didn't exist. New in froyo 2.2, JIT creates a lot of data in /data/dalvik-cache (at least 50mb, often 70-80mb). To accommodate for this increased use of /data in the Korean Motoroi froyo, Motorola adjusted the partitions to take 50mb from /cache and 20mb from /system to grow /data by 70mb. Dexter's 1.3 is built off of the 2.1 kernel and partitions and we can't change Motorola's partitioning (because of locked bootloader). So we end up losing space from /data. What we can do is put dalvik-cache on /cache (the one Motorola shrank) instead. That's what the update does.
Moving dalvik-cache to sd-ext is different. If you did not do that while running bugfix-1 (believe me you would know if you did), then you should be able to just apply bugfix-2, select wipe dalvik and reboot (the first boot after wiping dalvik is always slow). It should find your apps. There is a small chance you will have to wipe data / factory reset. I cannot guarantee it will work in all circumstances but it's worth a try. Take a nandroid backup of system, data, cache before applying bugfix-2 just to be safe.
It should not affect any apps that are on SD.
Click to expand...
Click to collapse
Thanks for your prompt reply, I have the question of how to move the dalvik-cache, you told me that "Would you believe me know if you did", then I'm sure they did not. Then, after applying the new patch, how should I move that dalvik-cache?.
Just to make sure, when making a backup nandroid, I mark all partitions, excluding Basband software, linux bootloader, logo and device tree? If something fails, with this new backup can restore the phone as it was after applying the ROM of Dexter's, and the data and preferences?
Tavinsky said:
Thanks for your prompt reply, I have the question of how to move the dalvik-cache, you told me that "Would you believe me know if you did", then I'm sure they did not. Then, after applying the new patch, how should I move that dalvik-cache?.
Click to expand...
Click to collapse
It should move automatically. You don't have to do anything
Tavinsky said:
Just to make sure, when making a backup nandroid, I mark all partitions, excluding Basband software, linux bootloader, logo and device tree? If something fails, with this new backup can restore the phone as it was after applying the ROM of Dexter's, and the data and preferences?
Click to expand...
Click to collapse
That sounds right. I can't remember exactly which ones can't be backed up. To undo trying the patch you need to restore System, Data, Cache (maybe), SD Data (possibly, if you have one). It doesn't hurt to get more. Just read the nandroid output carefully to make sure no errors happened.
I did not apply your patch because I am not really running out of storage memory on my phone and seems like that's the main focus of this patch. Just want to drop by and say thank you for your work and the clear description of the changelog, instead of the typical "optimal performance" and "faster system and more internal memory" that other posters do
While I appreciate the work and contribution by all members, I surely hope they will also post a more clarified changelog like yours
c19932 said:
I did not apply your patch because I am not really running out of storage memory on my phone and seems like that's the main focus of this patch. Just want to drop by and say thank you for your work and the clear description of the changelog, instead of the typical "optimal performance" and "faster system and more internal memory" that other posters do
While I appreciate the work and contribution by all members, I surely hope they will also post a more clarified changelog like yours
Click to expand...
Click to collapse
Thanks. Maybe I should break the changelog into subsystems. That might make it easier to scan.
The main non-memory improvements over bugfix-1 is xav's egl.cfg which really does help speed up the interface considerably and is the secret sauce of the recent themed ROMs here. We discussed it on the main thread just after bugfix-1 was released and a lot of us adopted it, but it seemed too experimental to push out as a default at the time. I've been running it since then without a problem and forgot that not everyone has it. Since khal and xav have been including it in all their ROMs, I decided it was probably time.
I also get a little annoyed at having to dig out these basic improvements from mostly theme and app-choice packages, but it does hone my understanding of android . I try to not push these things immediately out of respect to khal and xav. There was enough complaining yesterday about how to remove a theme get a "fast" stock ROM, that I decided it was probably time. There really hasn't been too much innovation lately between the ROMs, it's mostly been theming. It's sad xav's selling his phone.
The big problem still remains RAM use. Tweaking the minfree parameters seems more of a band-aid than a fix. That seems to be universal across all the froyo ROMs. Something isn't right. Maybe now that the Milestone froyo is finally released we can get to the heart of the problem.
* /sd-ext/app (move /data/app to /sd-ext [apps2ext])
* /sd-ext/dalvik-cache (move /data/dalvik-cache to /sd-ext)
* /sd-ext/app-private (move /data/app-private to /sd-ext)
* /sd-ext/link2sd (enable Link2SD 1.5.1 support)
* apps2ext has priority over link2sd and overrides! It doesn't make sense to use both!
Mioze7Ae again i love you ...you truly inspire me... sorry to ask such a basic question but i thought that in /sd-ext the forlder should be named *example* dalvik_cach and not dalvik-cach i see you changed all the _ for - is that on pourpose?
hello Mioze7Ae:
I have upgraded the stock221v13-bugfix-2_signed.zip.Upgraded before tock221v13-bugfix-1.zip.This had little impact, right? The upgrade will also be saving it? Always charge the battery power ah
hellmonger said:
Mioze7Ae again i love you ...you truly inspire me... sorry to ask such a basic question but i thought that in /sd-ext the forlder should be named *example* dalvik_cach and not dalvik-cach i see you changed all the _ for - is that on pourpose?
Click to expand...
Click to collapse
It must be /sd-ext/dalvik-cache not /sd-ext/dalvik_cache. If you use the _ the boot scripts will ignore it. See line 37 in
https://github.com/Mioze7Ae/XT720-patch/blob/master/src/system/etc/init.c/10_sdext
Maybe I accidentally hit a shift somewhere previously and didn't proofread carefully. Sorry for any confusion.
fwals said:
hello Mioze7Ae:
I have upgraded the stock221v13-bugfix-2_signed.zip.Upgraded before tock221v13-bugfix-1.zip.This had little impact, right? The upgrade will also be saving it? Always charge the battery power ah
Click to expand...
Click to collapse
I think you are asking: Is it OK to apply stock221v13-bugfix-2_signed.zip on top of stock221v13-bugfix-1.zip? I'm 95% confident it is OK.
Mioze7Ae said:
It must be /sd-ext/dalvik-cache not /sd-ext/dalvik_cache. If you use the _ the boot scripts will ignore it. See line 37 in
https://github.com/Mioze7Ae/XT720-patch/blob/master/src/system/etc/init.c/10_sdext
Maybe I accidentally hit a shift somewhere previously and didn't proofread carefully. Sorry for any confusion.
Click to expand...
Click to collapse
No no sorry to bother you you trully rock!!!!!!!
Hey Guys whenever i download any apps from market i get the error Install Unsuccessful .... Insufficient storage ...
What to do :-/
Rom Hell Fire v7.2
UOT Kitchen Flashed 1
Overclocked 729 Mhz
Wildfire
delete apps or move some to SD card? If your memory is full it's logical you can't add apps
Sounds to me that a2sd is not properly set up.
I been having some issues running out of storage internaly. and after some fiddeling around with a2sd it was ok. And how to do it is posted in this rom's explanation on how to install it.
ruymanca said:
The ROM takes about 10 minutes to start for the first time since the beginning makes for a facility, I recommend formatting the memory trageta do a clean install or possibly delete the folders: ANDROID, LOST DIR ANDROID as these folders SECURE conflicts created by data from the old roms
I recommend making partitions ie swap64mb ext512 and the rest as fat32 mind too expensive or necessarily recommend formatting the card will memory or possibly delete the folders in the same android, haer all the wipes, the Rom takes a few minutes to make first start since being installed all the extras on the first boot takes 3 to 5 minutes, once this echo this start and made previous settings obligation is to do a reboot for full functionality telefeno
Installation of the rom:
1. reboot in recovery mode
2. we wipes all
3. selected to install update sip
4. restart the tlf
5. enter the terminal console and register the following:
his press enter
# a2sd cachesd or enter
the phone will reboot and have about 150 megs of free internal memory
Click to expand...
Click to collapse
nope dint workk :-/
Type "su" first (Without Quotes), then try the a2sd command.
Can u mention it Step by Step?
Hi all, i have same issue.
Yesterday i finally rootat my Wildfire and put Cyanogenmod 7.0.3.stable on it.
Its very nice!
BUT cant allways install apps from market. I have 87mb free on inside memory and 1,7gb in sdcard... So what is problem?
What i need to do? I can full wipe all my data from telefone if somone tell me how i can do this..
Can somone help?
Use dalvik wipe from xrecovery to clean ur phone data..
Sent from my U20i using XDA Premium App
try istalling darktremor a2sd script (need to be istalled from recovery if not already integrated into your rom) and download a2sdgui from market, it's a gui for the script mentioned earlier. into recovery you have to partition your sd card too (advanced) 1024mb ext and i suggest 64mb swap, then open the app I told you (a2sdgui) and move everything to ext, dalvik cache too.
I agree with the poster above.
if you have issues with a2sd, I recommend installing A2SDGUI from market. (I assume you already have darktremors a2sd script installed). I had darktremors script working fine, but after flashing a zip file, it was not working. So I installed the A2SDGUI from darktremor and fixed the script. Now it is working. Just search the market and install it. It is great. Now I have around 168 MB free after all the installed apps.
Hope this helps,
SOLUTION TO INSUFFICIENT STORAGE:
1. Use FROYO+ default apps2sd. It gives the option to force moving of 95% of the apps to sdcard. Even root is not necessary. You can move 95% of apps only after using the adb command "adb shell pm setInstallLocation 2". This command is not even needed in cm7. And this method uses the fat/fat32 partition of sdcard not the ext partition. Specifically apps will be installed to .android_secure folder in the root of sdcard.
2. This method includes creating ext partition on sdcard and using an app called "link2sd". This is a root only app. No scripts are needed. That app has option to even link individual apps to ext partition. Also links dalvik cache.
3. Creating ext + swap partition and using dtapps2sd script. Root is required. Also custom recovery is required for flashing the script. This might be the toughest one but it is pretty awesome. Moves apps , data, dalvik cache to ext partition. Everything can be done with commands from the terminal emulator. Or you can use the "a2sdgui" app for graphical user interface.
Sent from my HTC Wildfire using XDA App
The GUI for the script is much more user-friendly than emulator terminal. And you can undo everything you did if it's not as you tought faster than from terminal.
I am not aware of how Hell Fire works. But yes for Cyanogenmod 7 I know there is a issue downloading a large application from the market. It won't download. Problem is the space.
Fix for this is few steps:
1. In Terminal type the following commands.
2. su
3. mkdir /sdcard/download-cache
4. cd /cache
5. mv download download.bak
6. ln -s /sdcard/download-cache download
Done... Now Go to market and download anything you won't get such errors..
If It Helps Don't forget Press Thank Button.
Thanks a lot!
I just get my new sd-card( 16 Gb) and install darktremor a2sd script + a2sdgui.
Works just like it says!
No more thinking what program van install and what not....
Well I just installed the MOdd Again ... and I was done
Though i bought Samsung Galaxy ace as its my second time the Touch Panel doesn't work ... first in Tattoo and den in Wildfire
So ... Thanx a lot guys for Helping
DestinyAwaits said:
I am not aware of how Hell Fire works. But yes for Cyanogenmod 7 I know there is a issue downloading a large application from the market. It won't download. Problem is the space.
Fix for this is few steps:
1. In Terminal type the following commands.
2. su
3. mkdir /sdcard/download-cache
4. cd /cache
5. mv download download.bak
6. ln -s /sdcard/download-cache download
Done... Now Go to market and download anything you won't get such errors..
If It Helps Don't forget Press Thank Button.
Click to expand...
Click to collapse
Working perfectly fine for me Thanks!
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.
DISCLAIMER: I'm not a dev, nor do I play one on t.v. Use the information and links at your own risk. READ and UNDERSTAND what your doing before flashing is the best bet.
I take no responsibility or credit for the information.
The OP is primarily just quotes/links from JcSullins over at RootzWiki about his current CWM Recovery v 6.0.1.9.
This thread is NOT intended as a walk through of a first time install of Android/CM on the Touchpad. There are several threads on Xda and RootzWiki for that.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rootzwiki version of this thread
CONTENTS: (See RolandDeschain79's CWM6 Video)
Post 1 - JcSullins fixed CWM6, installable from Acme3 or Recovery. (Scroll down)
Post 2 - Background on file system corruption/inode errors with CWM5 and early TWRP recoveries.
Post 3 - Moboot 3.5 and Moboot 3.8 background and issues with TWRP recovery.
Post 4 - How to Clean Install / Dirty Install Rom Updates using CWM6 after first install with Acme3.
Post 5 - Basic info for using CWM Recovery.
Post 6 - CM9/CM10 First Time Install Links (not all inclusive)
NEW CWM6 Setting: Dedupe (.dup) vs .tar backups. See post 5 for how to change the setting and read Koush's Explanation.
The Fixed CWM6 (2012-12-15) From RootzWiki AcmeInstaller3 thread Post 204
JcSullins said:
OK, fixed CWM6 update package has been "officially released"
JcSullins CWM Recovery v6.0.1.9 Goo.im Download
(Mpg2 Edit: Use the 12/15/2012 version because the script is setup to work with BOTH AcmeInstaller AND a previously installed Recovery)
Any CWM users should upgrade to this version (including those who installed the CWM6 testing from a few days ago).
Note that it will remove any existing uImage.ClockworkMod or uImage.TWRP before install.
Click to expand...
Click to collapse
From Rootzwiki Post 209
jcsullins said:
You can install with whatever recovery you currently have installed.
The version number it shows is 6.0.1.9.
Two things to check that it is correct version:
1) Selecting "install zip from sideload" from main menu will give a "Not implemented." message
2) In the "Backup and Restore" menu, you will see "choose default backup format" at the bottom (not "choose backup format")
To make sure that all the filesystems are "clean", I would suggest doing the following after it is installed:
1) go to 'backup and restore', select 'backup' (might take a little while)
NOTE: DO NOT CONTINUE WITH NEXT STEPS IF BACKUP FAILS FOR SOME REASON
2) go to main menu and select "mounts and storage"
3) select "format /cache"
4) select "format /data"
5) select "format /system"
6) go to main main, then select "backup and restore", then select "restore" and select the backup you just made
Click to expand...
Click to collapse
Thread continues Rootzwiki Post 211
Mpgrimm2 said:
JcSullins, thanks for your previous post about cm6. I had just posted this earlier when i found this thread....
My understanding from your previous post is that a fresh format with the newer Cwm6 you just posted will correct any file system/inode corruption. Am I correct?
Click to expand...
Click to collapse
jcsullins said:
Yep, that's correct.
Click to expand...
Click to collapse
Background: File system corruption/inode errors
Background: File system corruption/inode errors from RootzWiki Acme3 thread Post 102
jcsullins said:
The "Fix Recovery" commit - http://review.cyanogenmod.org/26596 - fixed the building
of recovery as part of standard build process.
http://review.review.cyanogenmod.org/#/c/26704/ plus review.cyanogenmod.org/#/c/26705/
is the fix for the filesystem corruption. If you build a recovery for the Touchpad (or know
someone who does), please make sure you/they include these two commits.
Click to expand...
Click to collapse
jcsullins said:
This issue was initially discovered in the days of CM7 when I created scripts to resize the /data partition. Several people were having trouble
using them because the filesystems check (fsck) on /data would fail. After some testing, I discovered that ext4 filesystems created with make_ext4fs
from system/extras/ext4_utils would fail a "fsck -fn <block_dev>" check immediately after creation with numerous inode errors. As far as we knew,
there was never any "real" data corruption. The problem seemed to only surface when doing a fsck required for doing a filesystem resize.
The issue resurfaced when we needed to resize /system for jellybean installs. Luckily, with the jellybean version of ext4_utils, I was able to uncover
the real source of the problem (make_ext4fs assumed our kernel supported ext4_lazyinit when it doesn't) and the fix (see above).
I tested TWRP v2.3.1.0 for tenderloin and it had the issue. I contacted Dees_Troy about rebuilding a fixed TWRP. Turns out that the TWRP for
tenderloin is not built using the jellybean source, so the above fix would not apply. However, he changed TWRP to use mke2fs instead of make_ext4fs to work around the issue.
In short, TWRP v2.3.2.3 for tenderloin does not have the issue. It is the current version available from http://teamw.in/project/twrp2/75
NOTE: The link on that page says it's v2.3.1.0 when it's really v2.3.2.3 it downloads.
Click to expand...
Click to collapse
Moboot 3.5 and Moboot 3.8 background and issues with TWRP recovery.
By now you should also be using the latest CWM6 (12/15/12) or latest TWRP (2.3.3.0+) due to files system corruption issues. If you use Cwm6, I recommend Moboot 3.8 as well.
Twrp & Moboot 3.8 summary ...
Moboot 3.8 is still considered a "Testing" version but allows correct device S/n reporting to android OS needed for certain apps/games like Asphalt 7 etc. There are no issues reported (yet) when used with cwm6 because it has always used sdcard/clockworkmod/ for backups.
TWRP uses your device S/N (000000000 on Moboot 3.5) to create the folder where backups are stored, when you update to Moboot 3.8, TWRP will be looking at a new backup folder (ie 12345678) and won't see your previous TWRP backups. This is not an issue on all future backups (or if you started with Moboot 3.8). If needed you can use a file browser to move the old TWRP backup files to the new S/n folder and it has been reported to work.
(Note: I have not tried TWRP on the Touchpad, but I have used it on other devices).
JcSullins' Moboot 3.5 (Last stable version)
JcSullins' Moboot 3.8 (Testing version)
Moboot 3.8 has been setup to be flashed from either Acme3 or the installed recovery (ie CWM6).
For download links and more info, I created a dedicated thread: [INFO] on JcSullins' Moboot versions (& Version Poll)
Currently... If you have 'ever' installed (ie originally) with AcmeInstaller3 you don't have to use it or AcmeUninstaller anymore for regular installs or updates, you can use the latest Cwm6 or TWRP 2.3.3.0 using either the clean install or dirty install that I detail below. If you get your install all hosed up, Acme is still the best way to clean out all the garbage, by completely removing (AcmeUninstaller) and reinstalling android (AcmeInstaller3).
Using AcmeUninstaller/AcmeInstaller3 method works well and is considered the 'tried & true' method because of issues with prior recoveries.
Prior versions of Acme(1&2) created a system partition size of 300mb which was appropriate for cm7/9. Cm10 needs about 350mb or more so Acme3 is needed because it sets the size of partition to 400mb AND formats without all the corruption/inode errors that occurred when formatting with prior recoveries (cwm5 & TWRP 2.1.x) hence "tried & true".
Per JcSullins (See the OP) if you perform a format of the 3 partitions with Cwm6 (& implemented in TWRP 2.3.3.0) it will correct any corruption issues (so u don't need to rely on Acme for a correct format once it has set the correct partition size).
To summarize,
if your system partition was previously sized to 400mb with Acme3, then yes, formatting and flashing with CWM6 will work correctly.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Note: Cwm6 12-15-2012 and Moboot 3.8 zips can be installed from your current recovery as well as being installed via Acme3. If you have already installed CM via Acme3 (provides 400mb system partition size needed for future installs of CM10), and have Moboot 3.8 (optional but recommended) and CWM6 (not optional, need this version or latest TWRP 2.3.3.0), then...
How to Clean Install / Dirty Install Rom Updates using CWM6 after first install with Acme3.
Step 1 (backup & format)
- Make a backup of your current CM9 install (See next post for details on using CWM6)
- Format/wipe ... system, data & cache (via Cwm6)
(ensures there isn't any file system corruption left over from prior recovery versions)
Step 2 Option 1 (clean install)
- flash CM9 and ICS Gapps zips via CWM6
(or CM10 & JB Gapps)
- Reboot, re-run CM setup
Step 2 Option 2 (Dirty install)
- "Backup and Restore" -> "Advanced Restore" -> select your CM9 backup -> "Restore data"
(advanced restore of cm9 data only)
- flash CM9 and Gapps zips via CWM6
(or CM10 & JB Gapps)
- Reboot, (should have all your apps and settings)
-------------------------------------------------------------------------------------------------------------------------
Some may disagree with me but I have never considered wiping Cache/Dalvik Cache a "Clean Install".
(using AcmeUninstall/AcmeInstaller3 would be a clean install too).
Clean Install vs Dirty Install Rom/Updates via Recovery: (After initial install with Acme3)
Generally, if your recovery is working right (each one has had issues at some point in it's development on every device I've had), the typical steps I've seen...
"Clean installing" a rom usually means to format the 3 basic partitions (& sometimes the /boot too depending on the rom/kernel script) and flash the rom as recommended by most devs to avoid issues (some rom installer scripts will handle the formatting for you, but shouldn't be assumed unless stated by the rom's developer. 9-14-13: See Attachment for example).
"Dirty Installing" a rom typically involves formatting the system & cache (sometimes only the cache :thumbdown: ) and flashing a rom to preserve /data partition with user apps & settings.
A cleaner method for this is to format all 3 partitions, flash rom, and restore only /data from a backup.
I've rarely seen dirty installs recommended by devs, but when I have seen them say it was "OK to try", it was done on the same rom/firmware base between incremental rom updates only (vs b/w CM7 - CM9 or CM9 - CM10, etc), and if you had a bug, you needed to go back and do a clean install before reporting it or expecting help. I will add that many people have been successful restoring their CM9 data after flashing CM10 & Gapps.
Basic CWM Recovery Info
CWM Recovery Backup, Format/Wipe, Restore, & Flash: ! MAKE SURE YOU READ THE NOTES IN THE OP AT THE TOP FIRST !
You CAN get into RECOVERY by: pressing [pwr] and selecting "boot ClockworkMod" from the bootloader (Moboot) when powered off.
You CAN get into RECOVERY by: holding [pwr], selecting "Reboot", then "Recovery" from within CM9/10.
Sdcard/clockworkmod/ (This is the folder CWM Recovery creates/uses.)
________________ /backup (recovery's backup of /system, /data, /boot.img, etc. are saved here by date. You can edit the filename.)
________________ /download (If you use CWM Rom Manager, it will place its downloads here. I've never used it.)
After the device has a Custom recovery, the recovery can be used to:
1) Flash/install .zip files:
- New/rooted kernels, including boot.img files (controls how the o.s. works with hardware)
- Roms (complete /system & /data file with kernel, custom apps, modded settings)
- Bootanimations (should be correct resolution)
- Other system improvements
- Themes (modify look of device/menus etc. Usually specific to each device (ie HP TP) & FW/Rom Base (ie CM9 vs CM10)
Must clear "dalvik cache" & may need to flash "deodexed template" or deodexed Rom, boot to system, before flashing each theme).
2) Make .tar(or dedup) backups of /system, /data, & /cache. Also backs up /boot ( boot.img or Kernel), and some versions may backup /recovery (recovery.img ), /wimax (wimax.img ) if available, that can be restored, usually together.
Note: Format the appropriate partition before restoring. (Usually format/wipe the first 3.)
It’s a good idea to make an initial backup right after you install the custom recovery. Then you can just format, restore the backup, if things get messed up.
3) Format/wipe the 3 main partitions and flash other partitions (depending on recovery version):
/system (o.s., system apps)
/data (google acct, app & phone settings, downloaded/installed apps)
/cache (used by o.s. to access info/apps, includes "/dalvik cache")
Android Partitions Explained
----------------------------------------------------------------------------------------------------------------------------------------
Controls:
[ Vol Up/Dwn ] = move or highlight selection
[ Home ] = select item/option
Note: On CWM Touch versions HW controls may still work.
How to Flash a Zip (Generally):
Place the .zip on the SDcard (or Sdcard/zip or similar folder of your choice)
Boot to recovery.
-> WIPE CACHE (habit of mine)
-> INSTALL ZIP FROM SD CARD -> CHOOSE ZIP FROM SDCARD
(navigate to where the zip is and select it)
-> REBOOT SYSTEM NOW (may need to "Go Back" to get to reboot option)
How to flash a rom (Generally):
- Make a backup in recovery first (/system, /data, /cache, etc.)
- Format/wipe the 3 partitions as appropriate.
(some Rom zips will do this for you, but may require a specific recovery coding such as “Edify” in CWM).
- Flash the Rom.zip (and any supplements like Gapps)
- Reboot to system, let it load, Verify functions
How to flash a theme (Geneally):
- Go to recovery, Wipe " Dalvik Cache ",
- Flash the " Stock Deodex Template" or Deodexed Rom (Depending on your version)
- Reboot to system, let it load, Verify functions
- Go To recovery, ADVANCED, Wipe "dalvik Cache"
- Flash the theme you want, ie GreenSteel.zip
- Reboot to system, let it load, Verify functions
Note: Anytime you wipe cache/dalvik cache it will take longer to boot the first time (ie Android is Updating).
Back up & Restore your file system with CWM recovery (DETAILED)
1 - (Enter Recovery)
-> BACKUP AND RESTORE -> BACKUP (This will separately backup: boot.img, /system, /data, /cache, wimax.img, etc)
Note: If you prefer the dedupe (.dup) backup format over .tar (default) and want to change the setting,
go to -> CHOOSE DEFAULT BACKUP FORMAT (before creating your backups)
* NOTE: you can stop here if you just want a backup*
2- (Format Manually through Recovery)
-> WIPE DATA/FACTORY RESET ( this will format the DATA & CACHE partitions for you in one shot )
-> MOUNTS AND STORAGE -> FORMAT SYSTEM
-> FORMAT DATA (Optionally there if needed, i.e. to restore only data partition)
-> FORMAT CACHE (Optionally there if needed)
4- (Restore Manually through Recovery)
-> BACKUP AND RESTORE -> CHOOSE YOUR BACKUP
-> RESTORE (This will restore all parts of the backup: /system, /data, & /cache, /boot [ boot.img or Kernel], /recovery [recovery.img], /wimax [wimax.img], SD-EXT if setup )
Note: If there is more than one, the numbers are a date/time stamp (ie: 2012-02-16.06.14.40 is Feb.16, 2012 at 6:14AM), so choose the appropriate one.
I typically change the name later, ie: "2012-02-16 CM9andApps".
(9-14-13 edit: Changing the name in newer CWM recoveries may create "MD5 checksum" errors and prevent a restore. Needs verified).
4.1- ADVANCED OPTION (Restore portions of backups individually, typically used to restore /data after Rom Update)
-> ADVANCED RESTORE -> CHOOSE YOUR BACKUP IMAGE ( /system, /data, /cache, /boot, /recovery, /wimax, SD-EXT)
-> RESTORE
5- (Reboot)
-> REBOOT SYSTEM NOW (may need to "Go Back" to get to reboot option)
CM9/CM10 First Time Install Links
CM9/CM10 First Time Install/Discussion threads
(XDA) Roland Deschain's How to install jcsullins CM10 Unofficial Build 20121216, with Sound, Camera & Microphone
(Also has Cm9 install info and zip packages with all current files.)
(Rootz) Nevertell's CM9 Install Directions in Post 19 of Newbie Questions thread
(@ NT, this is worthy of it's own thread or rolled into the OP of Travis' CM9 thread)
(Liliputing) How to install Android 4.0 or 4.1 on the HP TouchPad (CyanogenMod)
(This is a great guide and the one I originally used, but the linked install files for AcmeInstaller3, Cm9/10, Gapps, Moboot 3.8, & Cwm6 are out of date)
JcSullins' HpTouchpad Goo.im folder
(source for many current files: Cwm6, Moboot, Acme3, AcmeUninstaller, CM10.0 Experimental, etc)
Official CyanogenMod 9 HpTouchpad Downloads
(Click the "Nightly" link for now)
Latest Goo.im Google Apps Downloads
(Must match your CM base, ie CM9, CM10.0, CM10.1)
CM9/CM10 Support/Discussion Threads
(Rootz) Travisross69's [ROM] Official CyanogenMod 9 Nightly Build Discussion
(Rootz) Roland Deschain's How to install jcsullins CM10 Unofficial Build 20121216, with Sound, Camera & Microphone
(Xda) Imfloflo's [NIGHTLY] [ROM] CyanogenMod 9
(Xda) BigSimon's [ROM] [12/16] Unofficial CM10 Preview by Jcsullins Now with sound+camera
mpgrimm2 said:
one more post for me
Click to expand...
Click to collapse
What is this all about ?
Menthe is MIA on his JcSullins CWM6 thread since Dec 7th. I requested (Dec 20th) to take over the thread but the Mods recommended I just create a new one and they would merge it. I waited long enough and I think people may find the info useful if they don't want to use a pc/Acme3 to do all their rom updates/nightly's. I will duplicate this over at Rootz once I am all setup.
this is a lot of useful info. thanks for putting it together
Re: [RECOVERY] JCSullins' Touchpad CWM6 Recovery v6.0.1.9 [2012-12-15]
mpgrimm2 said:
Menthe is MIA on his JcSullins CWM6 thread since Dec 7th. I requested (Dec 20th) to take over the thread but the Mods recommended I just create a new one and they would merge it. I waited long enough and I think people may find the info useful if they don't want to use a pc/Acme3 to do all their rom updates/nightly's. I will duplicate this over at Rootz once I am all setup.
Click to expand...
Click to collapse
I'm sorry I'm a little lost I am new to this thread but I am NOT new to the touchpad nor xD a when did you have to use a computer to update CyanogenMod I didn't know people needed to do that because I just do it right through my touchpad. I am so glad I came to the threads because I thought only cm mod was available. Now only if I port gay bi sorcery over here this would be crazy it is the best rom out there it has more tweaks than every other ROM combined literally. It's so large and crazy it ca there is a central server for a lot of the mods an tweaks because it would be too large
Sent from my cm_tenderloin using xda premium
Crwolv said:
I'm sorry I'm a little lost I am new to this thread but I am NOT new to the touchpad nor xD a when did you have to use a computer to update CyanogenMod I didn't know people needed to do that because I just do it right through my touchpad. I am so glad I came to the threads because I thought only cm mod was available. Now only if I port gay bi sorcery over here this would be crazy it is the best rom out there it has more tweaks than every other ROM combined literally. It's so large and crazy it ca there is a central server for a lot of the mods an tweaks because it would be too large
Click to expand...
Click to collapse
Post 2 & 4 give a basic background on the issue. Basically, early recoveries were creating file system corruption when formatting partitions. It didn't always produce noticeable problems, but it was there. The workaround was to use AcmeInstaller3 from a PC for installs/updates and then restore a backup from within Recovery. Acme3 reformats the partitions correctly and would list/scroll all the file system errors before it fixed them (sometimes taking 15 - 20 mins to finish). Jc's CWM6 fixed the problem so it's ok again to do everything from recovery.
Remember you move to CM10, your system partition size needs to be @ 400mb (done initially with Acme3).
I'm not sure what the rest of your post is about.
Added Roland's Video and link to Koush's explanation of .dup vs .tar backup settings.
Just for grins and giggles (and with limited script reading skills), I decided to have a look at the installer script in TP CM9/10 zip package and found the following.
Code:
unmount("/system");
show_progress(0.500000, 0);
format("ext4", "EMMC", "/dev/store/cm-system", "0");
mount("ext4", "EMMC", "/dev/store/cm-system", "/system");
This confirms the fact that the CM9/10 zip will format ONLY the system partition for you during install, so if u want a clean install all that is needed (for CM9/10, not necessarily all roms) is to do a "wipe data/factory reset" (formats /data & /cache) and flash the zip.
So if u are just upgrading from a prior CM "nightly" to the current one, you can do a simpler "dirty install" by wiping/formatting cache and flashing the CM zip to retain your data (this assumes u have no file system corruption from earlier recoveries on your data partition).
I still stand on my general steps for "clean" & "dirty" installs via recovery since there isn't a guarantee that the rom developer setup the installer to do any formatting for you like CM9/10 does. The extra format shouldn't hurt in the long run (before the TP is obsolete anyway).
Sent from my "Up all night, sleep all day" HP CM9 Touchpad
sorry, it's a badly written post
1. Have to include a changelog
2. whether it's beneficial...
stayfidz said:
sorry, it's a badly written post
1. Have to include a changelog
2. whether it's beneficial...
Click to expand...
Click to collapse
PLease explain this statement better.
Are you referring to my OP, the previous post above yours, the whole thread, etc. Did you read through the thread and the "background" section to know what was going on with the TP recoveries before JcSullins' fixed it (not me or my work) or just look for a download link?
mpgrimm2 said:
PLease explain this statement better.
Are you referring to my OP, the previous post above yours, the whole thread, etc. Did you read through the thread and the "background" section to know what was going on with the TP recoveries before JcSullins' fixed it (not me or my work) or just look for a download link?
Click to expand...
Click to collapse
Hi, to the whole post, we're not all geeks by nature
1. By the way, what this recovery fixes, adds?
thanks again
You don't have to be a geek to "read and understand what you are doing first" (first statement in the op) before modifying your device. All users are expected to read and learn even a little bit. No one is going to spoon feed it to you.
Perhaps I am wrong, but it sounds like you are not bothering to read through posts 1 & 2. This thread isn't hundreds or thousands of posts long. There is even a link to a video by Roland Deschain about this Cwm6 next to the "contents" and an explanation on .dup vs .tar backups by Koush after the "contents".
Myself and others will help, but you have to be willing to roll up your sleeves and read a bit then come back with a question if u still actually have one.
Sent from my "Up all night, Sleep all day" EVO3D!
This was informative. I had no idea that there was a file corruption problem with older recoveries. That would explain a lot of issues I had. Just completely wiped my Touchpad back to factory (webOS default) then used ACME 3 to get CM10 back on with CWM6. Hope that solves my random issues. Thanks!
All the goo.im links are dead. Any other way to get this?
buddhag33k said:
All the goo.im links are dead. Any other way to get this?
Click to expand...
Click to collapse
Yes, head over to RolandDeschain's thread and download one of the cminstall.zip packages, its included in there.
[ROM GUIDE] How to install Jcsullins CM10/CM10.1 Unofficial Builds
Edit: Goo.im appears to be doing updates. Some of the files are back.
.