Database Info

[Recovery] [15-May-2010] RA-dream-v1.7.0 (also for the Rogers Dream)

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.
All source code is available at github.
This recovery if for the HTC Dream/G1 only, if you have an :
- HTC Magic/MT3G you should go here.
- HTC Hero you should go here.
- HTC Sprint Hero you should go here.
- HTC Eris you should go here.
- HTC Tattoo you should go here.
- HTC Nexus One you should go here.
Important notes
Always check recovery.log before posting your issues!
You can do this by doing :
"cat /tmp/recovery.log" OR "cat /cache/recovery/log" right after you had the issue.
Use the "move log to sd" option in the "others" menu right after you had the issue. This will move the log to /sdcard/recovery.log so you can easily open it with a text editor.
Features
Use the trackball (up+down) to navigate through the menu, press the trackball to select items.
You can also use the volume keys (vol-up + vol-down) to navigate, and the CALL-ANSWER key to select items (in case your trackball is broken).
full ADB access in recovery mode
Busybox v1.15.3
HW-Key navigation (volume keys + CALL-ANSWER) option
Extended menu (with keyboard-shortcuts):
[HOME+Back] Reboot system now :: reboot your phone
[Alt+X] Go to console :: bring up the console
[Alt+T] USB-MS Toggle :: enable/disable USB mass storage (use when the phone is connected to your PC)
[Alt+B] Backup/Restore (recovery partition not included!)
[Alt+0] Nand backup :: Make a Nand backup
[Alt+1] Nand + ext backup :: Make a Nand + ext backup
[Alt+2] Nand restore :: Restore a Nand backup
[Alt+3] BART backup :: Make a BART backup (Nand + ext)
[Alt+4] BART restore :: Restore latest BART backup
[Alt+5] Bck Google files :: Makes a backup of the Google proprietary system files in /cache/google
[Alt+6] Rst Google files :: Restores the Google proprietary system files from /cache/google
[Alt+F] Flash zip from sdcard :: Flash a zip update file from your sdcard
[Alt+W] Wipe
[Alt+0] Wipe data/factory reset :: Wipe /data and /cache
[Alt+1] Wipe cache :: Wipe /cache only
[Alt+2] Wipe Dalvik-cache :: Wipe /cache/dalvik-cache
[Alt+2] Wipe SD:ext partition : Wipe the ext partition on your sdcard
[Alt+4] Wipe battery stats : Wipe the battery stats in /data
[Alt+5] Wipe rotate settings : Wipe the sensor settings in /data
[Alt+P] Partition sdcard
[Alt+0] Partition SD :: Interactive SD partitioning
[Alt+1] Repair SD:ext :: Repair the ext partition
[Alt+2] SD:ext2 to ext3 :: Convert ext2 to ext3
[Alt+3] SD:ext3 to ext4 :: Convert ext3 to ext4
[Alt+O] Other
[Alt+0] Fix apk uid mismatches :: Does extacly that
[Alt+1] Move recovery.log to SD :: Moves the recovery log file to your sdcard. (Use when you want more detailed recovery log information)
[ALT+Q]Power off :: Powers off your phone
Scripts available from console :
Nandroid v2.2.1 : enter "nandroid-mobile.sh" to start.
BART v1.3.1 (Backup and Restore Tool) : enter "utility" or "u" to start.
switchrom.sh V1.1 : enter "switchrom" to start.
sdparted v0.6 : enter "sdparted" to start.
Install
There are several ways to install a custom recovery, choose the one that suits you most (I probably forgot a few).
You don't need to enter "mount -a" if your partitions are already mounted.
via fastboot :
Requires engineerings SPL!
Code:
Copy recovery-RA-dream-v1.7.0.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img
via adb :
Requires a custom recovery (with test-keys) like Cyanogen's v1.4 or my previous recovery
Do NOT follow these steps from a terminal application on the phone, make sure that you've booted into a custom recovery first!!!
Code:
Copy recovery-RA-dream-v1.7.0.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your G1 via usb to your pc/mac/...
adb shell
#mount -a (this can give back an error if you don't have an ext partition, don't worry about it and just proceed)
#flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img
via console :
Requires root
Do NOT follow these steps from a terminal application on the phone, make sure that you've booted into a custom recovery first!!!
Code:
Copy recovery-RA-dream-v1.7.0.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
select console from the menu
#mount -a (this can give back an error if you don't have an ext partition, don't worry about it and just proceed)
#flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img
via terminal application installed on the phone :
Requires root
[*]DO NOT use this method with CM5.0.7, there are currently some memory issues while flashing, use the above methods (preferably the fastboot method) instead until the issue is fixed in CM5.0.7!
Code:
Copy recovery-RA-dream-v1.7.0.img to the root of your sdcard
start the terminal app
#flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img
Download
ALWAYS check the md5sum to make sure the zip isn't corrupted.
Download the R version if you have a Rogers Dream EBI1 phone!
v1.7.0
recovery-RA-dream-v1.7.0.img - MD5Sum: 4b9f198aa8ada3ca1ed5537e9c25e427
recovery-RA-dream-v1.7.0R.img - MD5Sum: f1a061c572e3514800e3bbe65f210afe
recovery-RA-dream-v1.7.0-cyan.img - MD5Sum: 11ae63afee9813a9b76cb3f7fd5ac2ad
recovery-RA-dream-v1.7.0R-cyan.img - MD5Sum: ba2bf2d1c27e1bee009de2f66ac977e7
Change-log :
v1.7.0
Code:
- Fixed some minor bugs
- Recovery and scripts use /sd-ext instead of /system/sd as mountpoint to support the new apps2sd method (implemented mostly by Chris Soyars)
- Added an option to backup/restore Google proprietary Android system files (backuptool.sh written by Cyanogen)
- Removed "move apps2sd"-option as it's not needed anymore with the new apps2sd method
- Updated BART to v1.3.1 (updated by Dumfuq to support /sd-ext)
- Added a wipe cache only option
- Nandroid now backups/restores /cache again by default
- Dalvik-cache wipes /cache/dalvik-cache now
- Removed SDCARD: prefix in output when chosing zip to flash
- Added Cyan version (There's no difference with the normal version, only the wallpaper and textcolor changed)
v1.6.2
Code:
- Added power off menu item
- New unyaffs binary patched by Koushik Dutta and Packetlss to fix the "losing root"-issue and incorrect file-time after a Nandroid restore
- New dump_image binary (by Brainaid) patched by Packetlss to fix the "bad blocks"- Nandroid restore issue. [COLOR="Red"][B](This will not fix old corrupted Nandroid backups! Please make new backups!!)[/B][/COLOR]
- New mkyaffs2image binary
- New flash_image binary
- Updated busybox to v1.5.3
- Nandroid menu options will NOT backup or restore recovery, cache, misc, splash1+2 (to avoid issues)
- Fixed wipe option not wiping when ext was not present
- Created carebear versions after the idea of packetlss
- Switched the Nexus logo to a Green Carebear with Nexus One logo (Thanks Montalbert!)
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 ^^
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
Androidappcritics for the reboot idea in BART
rikupw for the ideas and toggle_ums script.
MLIGN for the idea to port my recovery to the Dream.
http://theunlockr.com for all the awesome video’s ^^
JesusFreke for his awesome JFv1.43's recovery , donate

Looks awesome, flashing now

I gotta try this out!

Great recovery image!! Comes in really handy when away from the pc!! Thx!!

nice work.. gonna check this out in a few

Flashed, no issues, so many options... Still has terminal... Awesome man, thank you so much...

Nice. Any chance of a mirror at like mediafire or something? I can't use rapidshare...

I typed "mount -a" and it says no such file or directory

gtrplr71 said:
I typed "mount -a" and it says no such file or directory
Click to expand...
Click to collapse
I'm sure that step isn't needed, to be honest. I flashed without, like a normal .img flash

it works even if "mount -a" doesn't.
Just use the "flash_image recovery" command in terminal emulator and it should work just fine.
Awesome recovery RA, thanks.

who needs pc now to flash a rom.. .now i can switch back and forth from hero / donut without having to be near a pc !!!!
this kicks donkey !!!

great job, i think you covered everything cyanogen was looking to cover in 1.5
lol, getting a loooooong list now. just a recommendation, in your next release, add backing up google apps. ik there are how-tos everywhere, but ive yet to see an easy way to do it just from your phone.

Miiiiiiiiiiiiiiiiiiiiiiint!
This is pure genius! Thanks a lot dude. I've mastered the console work but honestly this will make life 100x easier, thanks again.. Flashing now, will update with results.
Edit: Works as advertised! A must have for all!

Can some upload to a diff host. Not near a computer atm!

Dude...very nice! I don't post on here much, but I had to give you kudos!

I seen your recovery for the mytouch and have waited for someone to release one for the dream with partitioning options or waiting for someone to add a recovery to your mytouch image.
thanks!

jmotyka said:
Can some upload to a diff host. Not near a computer atm!
Click to expand...
Click to collapse
i put a mirror at my blog as well for no hassle download

there is a lot to choose from. Life just got a little easier. THANK YOU great recovery works great!

thanks a lot man, works great!

works great thank you!

[MOD][HOW TO] apps2ext for cm7 [link2sd + s2e + cMTD + eFOS]

Hi ^^
Like many of us I was having some concerns about moving away from cm6 to cm7. I was using firerat's magpie build of cm6 and LOVED it. My biggest concern was that losing a2ext is not an option for me as I have a ton of apps that I use only occasionally and don't want them taking up space on my internal memory. After looking around I found a couple of solutions that work extremely well together (so far). There was not nearly enough documentation in one place to get everything working out of the box, but hopefully this post will give you enough to get started. My solution involves using a modified version of cMTD by firerat and two apps available on the market or from xda: link2sd and S2E (simple2ext).
Background information:
Firerat's cMTD is a patch that you flash in recovery which allows you to control the size of /system, /cache and /data partitions. Using this patcher you can reduce the extra space left on /system by ~30mb, /cache by ~45mb, and increase the size of /data by the combined difference. I would suggest checking out an older post of mine (linked below) that discusses adjusting the threshold value for low space warnings if you decide to use cMTD as the threshold is a percentage value based on the size of /data. This means that the more /data space you have, the higher the threshold will be (ex: default for n1 is ~20mb, after cMTD modifications that increases to ~35mb).
Ennon's eFOS is a script that you flash in recovery which moves non-essential gapps from /system/app to /data/app, thus freeing up even more space on your /system partition. This *may not* be entirely necessary as the newest gapps archive is *much* smaller (~5mb) than previous versions and many of the gapps are available directly from the market. I'm including the scripts just in case anyone wants them.
Link2sd is a frontend for a script which manages the moving of apps to your ext partition (also supports fat) and creates syslink files in your /data/app folder which point to the app's actual location on the ext partition.
S2E(Simple2Ext) is similar to Link2sd, but instead of creating symlinks for individual apps it allows you to symlink entire folders to the ext partition. S2E may require an EXT flavor partition, but I haven't tried fat so I can't say for sure. I use S2E to move my dalvik cache and download cache folders to my ext partition freeing up even more space on internal memory.
Basic Method:
[a2ext ONLY]
----------------------
Description:
This method will install a copy of Link2SD and S2E(Simple2Ext) to /system/app, create the mounting scripts for an ext3 partition, and adjust your low space threshold value from 10% to 3%. If you wish to recover additional space on your /system and /data partitions using FRcMTD and eFOS, see the Easy or Manual methods below.
Requirements:
+ cm7 rom
+ cm7-a2ext-installer-0.1.zip - http://hotfile.com/dl/112853289/7d2e803/cm7-a2ext-installer-0.1-signed.zip.html
Steps:
1. Download cm7-a2ext-installer-0.1.zip and move it to /sdcard/.
2. Reboot into recovery.
3. NANDROID BACKUP!!!
4. [optional] Wipe all data if installing cm7 for the first time (see the cm7 install instructions for more info).
5. Flash cm7.
6. Flash gapps.
7. Flash cm7-a2ext installer from /sdcard/cm7-a2ext-installer-0.1-signed.zip.
8. Reboot into CM7.
9. [Optional] Open S2E and enable the dalvik cache and download cache options. Moving applications are not necessary.
10. Open Link2sd (if you are prompted to select a partition type, see the link2sd note below. otherwise you should have working a2ext).
11. Reboot to complete the S2E changes.
12. Congratulations! You should now have a2ext with cm7 ^_^
Updating CM7:
1. Reboot into recovery.
2. NANDROID BACKUP!!!
3. Flash CM7.
4. Flash cm7-a2ext installer from /sdcard/cm7-a2ext/cm7-a2ext-installer-0.1-signed.zip.
5. Reboot into CM7.
6. [Optional] Open S2E and enable the dalvik cache and download cache options. Moving applications are not necessary.
7. Open Link2sd (if you are prompted to select a partition type, see the link2sd note below. otherwise you should have working a2ext).
8. Reboot to complete the S2E changes.
10. Congratulations! You should now have a2ext with cm7 ^_^
Easy Method:
[a2ext + FRcMTD + eFOS]
----------------------
Description:
This method will install a copy of Link2SD and S2E(Simple2Ext) to /system/app, create the mounting scripts for an ext3 partition, and adjust your low space threshold value from 10% to 3%. It also includes optional steps that will enable FRcMTD and move less essential gapps from your /system/app folder to your /data/app folder.
Requirements:
+ cm7 rom
+ cm7-a2ext-package-0.1.zip - http://hotfile.com/dl/112853580/9b85471/cm7-a2ext-package-0.1.zip.html
Steps:
1. Download cm7-a2ext-package-0.1.zip and extract the contents to your sdcard.
2. [cMTD] Copy mtdpartmap.txt from the /sdcard/cm7-a2ext/cMTD folder to /sdcard/.
3. Reboot into recovery.
4. NANDROID BACKUP!!!
5. [optional] Wipe all data if installing cm7 for the first time (see the cm7 install instructions for more info).
6. [eFOS] Flash eFOS step 1 from /sdcard/cm7-a2ext/eFOS/ennon-fso-gapps1-signed.zip
7. Flash cm7.
8. Flash gapps.
9. [eFOS] If you are using eFOS, flash step 2 from /sdcard/cm7-a2ext/eFOS/ennon-fso-gapps2-signed.zip.
10. [cMTD] Flash cMTD recovery from /sdcard/cm7-a2ext/cMTD/Recovery-cMTD.zip.
11. [cMTD] Flash cMTD boot from /sdcard/cm7-a2ext/cMTD/Boot-cMTD.zip.
12. Flash cm7-a2ext installer from /sdcard/cm7-a2ext/cm7-a2ext-installer-0.1-signed.zip.
13. Reboot into CM7.
14. [Optional] Open S2E and enable the dalvik cache and download cache options. Moving applications are not necessary.
15. Open Link2sd (if you are prompted to select a partition type, see the link2sd note below. otherwise you should have working a2ext).
16. Reboot to complete the S2E changes.
17. Congratulations! You should now have a2ext with cm7 ^_^
Updating CM7:
1. Reboot into recovery.
2. NANDROID BACKUP!!!
3. Flash CM7.
4. [cMTD] Flash cMTD boot from /sdcard/cm7-a2ext/cMTD/Boot-cMTD.zip
5. Flash cm7-a2ext installer from /sdcard/cm7-a2ext/cm7-a2ext-installer-0.1-signed.zip.
6. Reboot into CM7.
7. [Optional] Open S2E and enable the dalvik cache and download cache options. Moving applications are not necessary.
8. Open Link2sd (if you are prompted to select a partition type, see the link2sd note below. otherwise you should have working a2ext).
9. Reboot to complete the S2E changes.
10. Congratulations! You should now have a2ext with cm7 ^_^
Manual Method:
[a2ext + FRcMTD + eFOS]
------------------------
Description:
This is my original method and is more involved, but it contains all of the steps required to setup a2ext, move your cache folders, adjust your partition sizes using FRcMTD, and move gapps from /system to /data using Ennon's eFOS scripts.
Requirements:
+ cm7 rom
+ cm7-a2ext archive - http://hotfile.com/dl/112487448/8264b72/cm7-a2ext.zip.html
+ root explorer, adb, or terminal access
Steps:
1. Download cm7-a2ext.zip and extract the contents to your sdcard.
2. [cMTD] Copy mtdpartmap.txt from the /sdcard/cm7-a2ext/cMTD folder to /sdcard/.
3. Reboot into recovery.
4. NANDROID BACKUP!!!
5. [optional] Wipe all data if installing cm7 for the first time (see the cm7 install instructions for more info).
6. [eFOS] Flash eFOS step 1 from /sdcard/cm7-a2ext/eFOS/ennon-fso-gapps1-signed.zip
7. Flash cm7.
8. Flash gapps.
9. [eFOS] If you are using eFOS, flash step 2 from /sdcard/cm7-a2ext/eFOS/ennon-fso-gapps2-signed.zip.
10. [cMTD] Flash cMTD recovery from /sdcard/cm7-a2ext/cMTD/Recovery-cMTD.zip.
11. [cMTD] Flash cMTD boot from /sdcard/cm7-a2ext/cMTD/Boot-cMTD.zip.
12. [optional] If you have access to adb in your recovery see the note about adb below.
13. Reboot into CM7.
14. From root explorer:
a) Navigate to /sdcard/cm7-a2ext/link2sd-config-scripts/ use multi-select on 11link2sd and 99complete then select Copy.
B) Navigate to /etc/init.d/ and select mount r/w from the upper right corner of the screen.
c) Paste the copied files.
15. Long press 11link2sd and select Permissions. Ensure that the permissions are set to rwxr-x---. Repeat this step for 99complete.
16. Reboot phone.
17. From the market install Link2sd and S2E.
18. [Optional] Open S2E and enable the dalvik cache and download cache options. Moving applications are not necessary.
19. Open Link2sd (if you are prompted to select a partition type, see the link2sd note below. otherwise you should have working a2ext).
20. Reboot to complete the S2E changes.
21. Congratulations! You should now have a2ext with cm7 ^_^
Additional Steps:
22. [threshold value] If you are getting low space messages with ~30mb free space on internal memory, you should consider checking out my tutorial on adjusting the threshold value. The link is at the bottom of this post.
Updating CM7:
1. Reboot into recovery.
2. NANDROID BACKUP!!!
3. Flash CM7.
4. [cMTD] Flash cMTD boot from /sdcard/cm7-a2ext/cMTD/Boot-cMTD.zip
5. [optional] If you have access to adb in your recovery see the note about adb below.
6. Reboot into CM7.
7. From root explorer:
a) Navigate to /sdcard/cm7-a2ext/link2sd-config-scripts/ use multi-select on 11link2sd and 99complete then select Copy.
B) Navigate to /etc/init.d/ and select mount r/w from the upper right corner of the screen.
c) Paste the copied files.
8. Long press 11link2sd and select Permissions. Ensure that the permissions are set to rwxr-x---. Repeat this step for 99complete.
9. Reboot phone.
10. [Optional] Open S2E and enable the dalvik cache and download cache options. Moving applications are not necessary.
11. Open Link2sd (if you are prompted to select a partition type, see the link2sd note below. otherwise you should have working a2ext).
12. Reboot to complete the S2E changes.
13. Congratulations! You should now have an updated system with a2ext^_^
notes:
-------------------------
adb / terminal note:
If you have access to adb from your recovery, you can potentially avoid an extra reboot by copying the config scripts from /sdcard/cm7-a2ext/link2sd-config-scripts/ to /etc/init.d/ before you boot cm7 for the first time. I haven't tested this, but I see no reason that it shouldn't work. I'm not going to go into too much detail about terminal commands because I will assume that if you're trying this you know what you're doing and if you don't, you should probably just buy root explorer and save yourself the hassle.
cMTD Note:
As of this writing the current install size for cm7 nightlies is just under 120mb. If you install cMTD make sure that the values in mtdpartmap.txt allow for enough room to fully install cm7 or you will have issues. The current values are set to 125mb system, 5mb cache, and everything extra goes to /data. It should also be noted that cm7 dynamically detects the cache value and moves the cache location if the size is <20mb.
link2sd Note:
Normally when you start link2sd for the first time, it asks you to select your partition type so it can create a script to mount the partition at boot. The config scripts (11link2sd and 99complete) serve this function, so if you are prompted to create the script /sd-ext and /data/sdext2 have not mounted properly. This is probably due to a device specific configuration issue. The included files are for an ext3 partition. If you have a different flavor of ext, you will need to adjust the 99complete script accordingly. Also keep in mind that if you are using s2e, it does not yet support ext4 so use at your own risk.
default install location note:
Since you have gone through all this trouble, it might be pertinent to change the default install location to internal in settings > cyanogenmod settings > application > install location. This will prevent cm7 from installing apps to the native FroyoApps2SD, thus negating all the benefits of using a2ext in the first place.
updating cm7 note:
You should be aware that many of these steps will have to be reproduced every time you update cm7. This is due to the fact that cm7 overwrites many of the files you are installing when you update. Fortunately, you won't lose anything on your ext partition and things go much quicker the second time through. See the section updating cm7 above for instructions.
Links:
--------------------------
cm7-a2ext:
cm7-a2ext-package-0.1.zip - http://hotfile.com/dl/112853580/9b85471/cm7-a2ext-package-0.1.zip.html
cm7-a2ext-installer-0.1.zip - http://hotfile.com/dl/112853289/7d2e803/cm7-a2ext-installer-0.1-signed.zip.html
cm7-a2ext archive - http://hotfile.com/dl/112487448/8264b72/cm7-a2ext.zip.html
Apps:
Link2sd - http://forum.xda-developers.com/showthread.php?t=919326
S2E (simple2ext) - http://forum.xda-developers.com/showthread.php?t=917377
cMTD Stuff:
Firerat's cMTD - http://forum.xda-developers.com/showthread.php?p=7061471#post7061471
cMTD cm7 specific - http://forum.cyanogenmod.com/topic/17752-cm7-issues-with-cmtd/
patched cMTD for cm7 (original post) - http://www.teamuscellular.com/Forum/viewtopic.php?f=29&t=178
Ennon's eFOS:
original thread - http://forum.cyanogenmod.com/topic/...-cyanogenmod6-firerats-cmtd-ennons-fso-gapps/
other:
How to change threshold value - http://forum.cyanogenmod.com/topic/...n-space”-warnings/page__p__107672#entry107672
cross posted from http://forum.cyanogenmod.com/topic/19160-how-to-a2ext-for-cm7/

does this still work?

yes. i have successfully used it on every nightly for CM7 (that i happened to install) through to the current official build as well as the temasek "self kang" builds where available (http://forum.xda-developers.com/showthread.php?t=1421425).

thank you flashing will report bak in a while
---------- Post added at 03:22 AM ---------- Previous post was at 02:56 AM ----------
i tired and it didnt work... it says
--Installing: /sdcard/cm7-a2ext/eFOS/ennon-fso-
gapps1-signed.zip
Finding update package...
Opening update package...
E:Error in /sdcard/cm7-a2ext/efos/ennon-fso-gapp
s1-signed.zip
(Status 0)
Installation aborted.

maxesxp said:
i tired and it didnt work... it says
--Installing: /sdcard/cm7-a2ext/eFOS/ennon-fso-
gapps1-signed.zip
Finding update package...
Opening update package...
E:Error in /sdcard/cm7-a2ext/efos/ennon-fso-gapp
s1-signed.zip
(Status 0)
Installation aborted.
Click to expand...
Click to collapse
Ah. Forgot about that one. I haven't used it in forever to be honest. The ennon thing is super old now. Try looking for a new version or just delete system apps manually using titanium backup, root explorer, the terminal emulator or adb.
Search the forums for help if you're not sure what to toss.

icecreamisdrugs said:
Ah. Forgot about that one. I haven't used it in forever to be honest. The ennon thing is super old now. Try looking for a new version or just delete system apps manually using titanium backup, root explorer, the terminal emulator or adb.
Search the forums for help if you're not sure what to toss.
Click to expand...
Click to collapse
okay thanks anyways

Nexus1 S2E ext4 - individual apps?
maxesxp said:
okay thanks anyways
Click to expand...
Click to collapse
Hi, I've been following your posts - I have cm7.2 and installed S2E - it seems to just WORK without having to do all the flashing above.
.... I see that my ext4 partition has some stuff in it, but the free space still indicates that my space for apps is huge number to 190mb...
have a look at this screen shot
==

[DEV][PORT] RZRecovery 2.1.4 for FIT GT-S5670

I've ported this awesome Custom Recovery to our device
---------------------------------
Overview
---------------------------------
*RZrecovery*:
-=overclock settings=-
-=Arbitrary update.zip selection (with folders) (don't have to rename files to update.zip).=-
-=rom.tgz support (of course)=-
-=Unsigned update.zip support=-
-=ability to wipe system, data, boot, dalvik-cache, battery stats, cache-
-=No automatic backup when installing a rom.tgz=-
-=update.zip from folder support=-
-=Ability to install APK's, IMG's, ZIP's, TAR's, TGZ's from the same menu=-
-=Wipe battery statistics=-
-=Ability to root any ROM=-
-=12 predefined colors + random color selection=-
-=Rave mode: random color every time screen is redrawn=-
-=preinstall update.zip menu=-
-=android_secure nandroid / wipe support=-
-=Hold volume keys to scroll=-
-=Can add plugins for new menu=-​
Click to download a file (ext4 fstype only) [FLASH via Recovery]recontruction)​
And, for ext4+rfs support [FLASH via Recovery]recontruction)​
DON'T MIRROR MY FILE, please!​
BIG THX to
RaidZero for his awesome recovery that I've ported
And, Don't forget to click Thanks Button to me for ported this lol
And, thx to Gandoct & Gandro @kaskus for testing this recovery​

Flash Instructions
Download a file, and place it into your sdcard
Install zip from sdcard (CWM) | apply update from sdcard (xrecovery)
Choose a file u've downloaded
Go to advanced options, reboot recovery (CWM) | reboot system now (xrecovery)
Done, and Enjoy it!
Don't forget to hit thanks if u download & use this file ^^

-reserved-

-reserved for-

-reservedd

good job gan mantap!
thanks!

Syfer_Fever said:
good job gan mantap!
thanks!
Click to expand...
Click to collapse
sip sip om sm2

thanks dude will try

How to knw if fone is ext4 or not??
Sent from my GT-S5670 using xda premium

If you have a custom ROM it's probably ext4
Sent from my GT-S5670 using XDA App

mantaaap gan.
sedooot
Sent from my GT-S5670 using Tapatalk

Screenshot please??

Thanks a lot man thanks

19niks91 said:
How to knw if fone is ext4 or not??
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
check recovery's ability mounting on your ROM using
Aspire said:
If you have a custom ROM it's probably ext4
Sent from my GT-S5670 using XDA App
Click to expand...
Click to collapse
But, it perhaps rfs fstype, too. or ext2/ext3

cygnus39 said:
Screenshot please??
Click to expand...
Click to collapse
U can look at a developer thread of this recovery.
Raidzero is a dev of RZR.
I port his recovery to be able to this device

Thanks bro need it

Bug while backup
In rfs+ext4
Bacup book....ok
backup system.....ok
bakup data .......fail
Backup cache....... fail
backup android secure fail

omarhasan76 said:
Bug while backup
In rfs+ext4
Bacup book....ok
backup system.....ok
bakup data .......fail
Backup cache....... fail
backup android secure fail
Click to expand...
Click to collapse
did it happen on ext4, too?
hehe.
if recovery support 2 fstype, it's usually can be serious problem

- It is only cosmetical stuff, but Title of main menu says:
Welcome to RZRecovery (2 <---- there´s end of line
by raidzero
Well all the written stuff is not readable completely, Fontsize too big??^^
- USB storage does not function, means no connection to PC .... using windows 7
- Recovery Overclocking gives Error: scaling_available_frequencies not found
---------- Post added at 04:16 PM ---------- Previous post was at 04:13 PM ----------
omarhasan76 said:
Bug while backup
In rfs+ext4
Bacup book....ok
backup system.....ok
bakup data .......fail
Backup cache....... fail
backup android secure fail
Click to expand...
Click to collapse
same here on EXT-ONLY version

Delanoister said:
I've ported this awesome Custom Recovery to our device
---------------------------------
Overview
---------------------------------
*RZrecovery*:
-=overclock settings=-
-=Arbitrary update.zip selection (with folders) (don't have to rename files to update.zip).=-
-=rom.tgz support (of course)=-
-=Unsigned update.zip support=-
-=ability to wipe system, data, boot, dalvik-cache, battery stats, cache-
-=No automatic backup when installing a rom.tgz=-
-=update.zip from folder support=-
-=Ability to install APK's, IMG's, ZIP's, TAR's, TGZ's from the same menu=-
-=Wipe battery statistics=-
-=Ability to root any ROM=-
-=12 predefined colors + random color selection=-
-=Rave mode: random color every time screen is redrawn=-
-=preinstall update.zip menu=-
-=android_secure nandroid / wipe support=-
-=Hold volume keys to scroll=-
-=Can add plugins for new menu=-​
Click THIS to download a file (ext4 fstype only) [FLASH via Recovery] (pass: delano)​
And, THIS for ext4+rfs support [FLASH via Recovery] [(pass: delano)​
DON'T MIRROR MY FILE, please!​
BIG THX to
RaidZero for his awesome recovery that I've ported
And, Don't forget to click Thanks Button to me for ported this lol
And, thx to Gandoct & Gandro @kaskus for testing this recovery​
Click to expand...
Click to collapse
Is it work on stock ROM?

[CWM] Motorola Fire / Spice Key: xt311 / xt316 / xt317

Hey Motorola Fire owners!
Here's ClockWorkMod for our beloved QWERTY phone [With nandroid backup minor issues]
Any damages, you're responsible of it.
The Steps:
1- Download busybox from playstore, i prefer stericson's one, install busybox binary.
2- Download Pimp My Rom from playstore, open it, click > Universal init.d support, then click > activate
3- Download latest zip (bootmenu 3-12-12.7z)
4- Extract it, and run Install-boot-menu.bat
If you want to know what the script does:
5- Download latest bootmenu folder, extract it, copy "bootmenu" folder to /system/ (by using any root browser of your choice)
6- Fix permission of all the files inside "/system/bootmenu/binary/" to: RWXR--R--
7- a- Create a new file with no extention, rename it to 97bootmenu, put it inside "/etc/init.d/" set it's permissions to RWXRWXRWX (full permissions)
7- b- inside this file paste this code and save it:
Code:
#!/system/bin/sh
stop
exec /system/bootmenu/binary/bootmenu
-Then Reboot
Now focus, while you're seeing motorola logo, the capacitive keys' leds will light up at certain timing, quickly press VOL- button before the lights go off, if you later, don't want to boot to bootmenu, just don't press the VOL- button, the phone will boot normally to system
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​To restore backed up nandroid system.yaffs2.img
In terminal emulator or adb shell type:
cd /sdcard/clockworkmod/backup/YYYY-MM-DD.HH.MM.SS/
md5sum *.img > nandroid.md5
Where <YYYY-MM-DD.HH.MM.SS> is the folder of your backup.
Then go to cwm again and restore ( i prefer advanced restore > system )
Or with fastboot: By typing: "fastboot flash system system.yaffs2.img"
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Now the most important part, press thanks button, it motivates me
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I'd like to thank those who made this dream come true: GentryLamp - 7amdoun (Thanks alot bro) - Aweosomeabhijeet - Mr. indigo - Andrewidya - AndYRo - Chen2011521
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
Changelog:
3-12-12
-Added automatic installer (abhijeet's idea)
1-12-12
-Booting to bootmenu through volume down button (Thanks alot 7amdoun!)
-Now you don't have to delete 97bootmenu at all
-Unified bootmenu-recovery background
30-11-12: Very old build
-Removed ability to backup data via clockworkmod since it probably is corrupted, causing bootloops when restoring, you can backup the whole rom using onandroid backup instead
-Ability to restore nandroids
28-11-12: Very old build
-Fixed font size of the recovery, (Thanks chen2011521)
-Changed wallpaper because i got bored
25-11-12: Very old build
-Modified Stock.sh so when you select [+boot] > [stock] it boots normally to stock system, Without needing pc. (Thanks aweosomeabhijeet)
-Fixed some mounting issues, may be able to backup .android_secure
24-11-12: Very old build
-First alpha release
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
Downloads:
Removed old builds, for the user not to download them and use the new incompatible steps.

Just registered!
---------- Post added at 04:40 PM ---------- Previous post was at 03:43 PM ----------
Only just created a bunch of commands to mount secure.android. After normal backup of system and data, gave me this error:
Backing up .android_secure...
Freeing space...
sh: dedupe: not found
Done freeing space.
sh: dedupe: not found

Already did it!!
Waiting for more to come
:good::good::good::good::good:

No more dedupe error, tar generated correctly! but more mounting problems! The last logs lines:
Backing up .android_secure...
com.joelapenna.foursquared
com.google.android.youtube
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
So fstab is sill umcomplete!
---------- Post added at 05:59 PM ---------- Previous post was at 05:42 PM ----------
Im startint to think that every sbf has diferents mounts...

xt316 chinese 2.3.5
97bootmenu permission 744
and reboot into bootmenu
but not full permission.
Backup stuck at /system
....
Did you port the recovery from source? You can change it font smaller.

Mazen.kh said:
Hey Motorola Fire owners!
Here's CWM for our beloved QWERTY phone [Still have issues with nandroid backup]
Okay so first of all this is not only my work
I only built CWM6 and put it inside the bootmenu, also helped in discovering init.d support, and when you nandroid backup, i fixed the creation of system.img and data.img (with help of dear friends from taringa.net) :angel:
The Steps:
1- Download busybox from playstore, i prefer stericson's one, install busybox binary.
2- Download PimpMyRom.apk from attachments and install it, because the one in the market have some errors causing FCs
3- From Pimp my rom, click > Universal init.d support, then click > activate
4- Download bootmenu.zip, extract it, copy "bootmenu" folder to /system/ (by using any root browser of your choice)
5- Fix permission of all the files inside "/system/bootmenu/binary/" to: RWXR--R--
6- a- Create a new file with no extention, rename it to 97bootmenu, put it inside "/etc/init.d/" set it's permissions to RWXRWXRWX (full permissions)
6- b- inside this file paste this code and save it:
HTML:
#!/system/bin/sh
stop
exec /system/bootmenu/binary/bootmenu
7- Reboot
After reboot, android bootmenu will appear, choose recovery, then select custom recovery
Now you entered CWM 6 :cyclops:
Please don't select the "mounts" section, still needs fixes, might be dangerous
If you take nandroid it will successfully backup system.img and data.img without sd-ext.
You may not be able to restore them through cwm.
But you can restore them through FASTBOOT.
I flashed many zips through this recovery successfully.
PS: to boot again to system, normally connect the device through adb, and type:
adb shell
rm -r /system/etc/init.d/97bootmenu
Then reboot using "adb reboot" or reboot function in bootmenu
Now the most important part, press thanks button, it motivates me to keep up the good work
I'd like to thank those who helped in getting this bootmenu to work:
- Gentry Lamp
- 7amdoun
- Aweosomeabhijeet
- Mr. indigo
- Andrewidya
- AndYRo (from Taringa.net)
probably others that i forgot to mention
I'll keep updating the recovery until it becomes perfect
Click to expand...
Click to collapse
Hey Mazen I would like to suggest you something.
Open bootmenu folder go to script folder and open stock.sh
and add
Code:
rm -r /system/etc/init.d/97bootmenu
reboot
Then if you select boot>Stock your phone will reboot twice and boot normally.
then no need of using adb in PC.

I make everything as u say and restarted it above 6 times but nothing happens and my device starts normally!!!
EDIT: try to change permissions of 97bootmenu to rwxr-r- & restart 2 times but nothing happened!!

chen2011521 said:
xt316 chinese 2.3.5
97bootmenu permission 744
and reboot into bootmenu
but not full permission.
Backup stuck at /system
....
Did you port the recovery from source? You can change it font smaller.
Click to expand...
Click to collapse
I built it online and modded some files, couldn't build from source, the font is not so important right now so i'm working on fixing the nandroid backup
aweosomeabhijeet said:
Hey Mazen I would like to suggest you something.
Open bootmenu folder go to script folder and open stock.sh
and add
Code:
rm -r /system/etc/init.d/97bootmenu
reboot
Then if you select boot>Stock your phone will reboot twice and boot normally.
then no need of using adb in PC.
Click to expand...
Click to collapse
I tried that once and it booted to the bootmenu again but i will retry, thanks :laugh:

wrong :|

I follow ur steps and I fail in problem! just tell me what shoud I do NW?
and nothing wrong in my device!
EDIT: I change some permissions and it's work but I forgot what I do and I reboot without need PC!
I advice u guys to make that suggest by aweosomeabhijeet it's awesome

Ok remember to use reboot after rm command.
Sent from my XT530 using xda app-developers app

european sbf
Hey guys has anyone an european sbf for the xt311, i really need it.

Hey Mazen,
How did you manage to get CWM to make a full backup. I tried everything but it just freezes on system. I edited recovery.fstab to point to /dev/block/mtdblock* for every partition but it keeps complaining that it can't find that volume to mount.

7amdoun said:
Hey Mazen,
How did you manage to get CWM to make a full backup. I tried everything but it just freezes on system. I edited recovery.fstab to point to /dev/block/mtdblock* for every partition but it keeps complaining that it can't find that volume to mount.
Click to expand...
Click to collapse
I added mkyaffs2image
and AndYRo fixed a couple of mounting errors, if you build CWM 6 online you can take our xt311's modded files and only replace "recovery" file in /recovery/sbin/, with the corresponding one in your CWM 6

Mazen.kh said:
I added mkyaffs2image
and AndYRo fixed a couple of mounting errors, if you build CWM 6 online you can take our xt311's modded files and only replace "recovery" file in /recovery/sbin/, with the corresponding one in your CWM 6
Click to expand...
Click to collapse
Edit: I ported CWM6 to my phone manually and it loads and backs up boot and recovery but still gets stuck on /system
Any ideas?

Moderator warning.
Thread has been cleaned. Remember forum rules when posting.

Mazen.kh said:
Hey Motorola Fire owners!
Here's CWM for our beloved QWERTY phone [Still have issues with nandroid backup]
Okay so first of all this is not only my work
I only built CWM6 and put it inside the bootmenu, also helped in discovering init.d support, and when you nandroid backup, i fixed the creation of system.img and data.img (with help of dear friends from taringa.net) :angel:
The Steps:
1- Download busybox from playstore, i prefer stericson's one, install busybox binary.
2- Download PimpMyRom.apk from attachments and install it, because the one in the market have some errors causing FCs
3- From Pimp my rom, click > Universal init.d support, then click > activate
4- Download latest bootmenu.zip, extract it, copy "bootmenu" folder to /system/ (by using any root browser of your choice)
5- Fix permission of all the files inside "/system/bootmenu/binary/" to: RWXR--R--
6- a- Create a new file with no extention, rename it to 97bootmenu, put it inside "/etc/init.d/" set it's permissions to RWXRWXRWX (full permissions)
6- b- inside this file paste this code and save it:
Code:
#!/system/bin/sh
stop
exec /system/bootmenu/binary/bootmenu
7- Reboot
After reboot, android bootmenu will appear, choose recovery, then select custom recovery
Now you entered CWM 6 :cyclops:
Please don't select the "mounts" section, still needs fixes, might be dangerous
If you take nandroid it will successfully backup system.img and data.img without sd-ext.
You may not be able to restore them through cwm.
But you can restore them through FASTBOOT.
I flashed many zips through this recovery successfully.
PS: to boot again to system, normally:
In bootmenu select [boot] > [stock]
OR
Connect the device through adb, and type:
adb shell
rm -r /system/etc/init.d/97bootmenu
Then reboot using "adb reboot" or reboot function in bootmenu
Now the most important part, press thanks button, it motivates me to keep up the good work
I'd like to thank those who helped in getting this bootmenu to work:
- Gentry Lamp
- 7amdoun
- Aweosomeabhijeet
- Mr. indigo
- Andrewidya
- AndYRo (from Taringa.net)
probably others that i forgot to mention
I'll keep updating the recovery until it becomes perfect
Click to expand...
Click to collapse
Thanks for creating a thread!
I'm trying with UAE sbf, unfortanelly I have to reflash it, since there's a problem with my Init.d support.

*Can we able to change the font size in the recovery not in the bootmenu? cuz it's looks bigger
PS. i make oNandroid backup and I delete it to try the backup section in the recovery when I make it it's stuck on
backup system.....
and no progress bar like any CWM recovery!

If build from source,android.mk in bootable/recovery can change font.
smaller font looks well on xt311/6
I have built one, but some problem not solve.

chen2011521 said:
If build from source,android.mk in bootable/recovery can change font.
smaller font looks well on xt311/6
I have built one, but some problem not solve.
Click to expand...
Click to collapse
Upload it so i can mix things and fix the font

[MOD][SCRIPT] Super WIPE Script HTC One | Aroma GUI (upd.18/03/2015)

This tool will allow you to easily WIPE system, data (except /data/media), boot (kernel) and cache partitions directly from custom recovery.
Before using this tool you need to be sure you are using latest version of custom recovery (TWRP or CWM). The current downloads for both CWM and TWRP can found below:
The latest M7 U/UL TWRP can be downloaded HERE. I recommend to use TWRP 2.6.3.0 (for v1.0.2d) and TWRP 2.8.5.* (for v2.0.2) .
v1.0.2d will work for Intarnational version, GE, T_Mobile, AT&T but NOT for SPRINT DEVICE
and v.2.0.2 - for all version!!!
To use this tool please copy zip file to your phone and then boot into custom recovery and choose Install. Then browse to where you copied zip file and select it. Aroma installer will begin. Choose options you want to run.
What script does:
1. Wipe /cache partition (select in Aroma);
2. Wipe delvik-cache (select in Aroma);
3. Wipe /system partition (select in Aroma);
4. Wipe /data partition except /data/media (select in Aroma);
5. Format boot partition (kernel) and removes /system/lib/modules (select in Aroma);
/system/lib/modules
/system/etc/init.d/01-h2w
/system/etc/init.d/01-pwp
/system/etc/init.d/01-therm
/system/etc/init.d/01-blinkbuttons
/system/etc/init.d/01-f2s
/system/etc/init.d/01-f2w
/system/etc/init.d/01-f2ws
/system/etc/init.d/01-f2wt
/system/etc/init.d/01-p2w
/system/etc/init.d/thoravukk
system/etc/init.d/89elementalx
/system/etc/init.d/99elementalx
/system/etc/init.d/99elementalx~
/system/etc/init.d/99bulletproof
/system/etc/init.d/56zram
/system/etc/init.d/30sweep2wake
/system/etc/elementalx.conf
/system/bin/fstrim
/system/usr/keylayout/synaptics-rmi-touchscreen.kl
/sys/android_touch/sweep2wake
/sys/android_touch/doubletap2wake
/sys/android_touch/logo2wake
/sys/android_touch/pocket_detect
/sys/android_touch/logo2menu
5. Removes some system files from /data/media;
/sdcard/.android_secure
/sdcard/.bookmark_thumb1
/sdcard/LazyList
/sdcard/LOST.DIR
/sdcard/.data/footprints
/sdcard/.data/mail
sdcard/Android/data/com.android.providers.media
/sdcard/Android/data/com.google.android.apps.genie.geniewidget.news-content-cache
/sdcard/Android/data/com.google.android.apps.maps
/sdcard/.data/navigator/Data/Temporary
6. Check partitions for errors;
7. Create a log of work on internal memory card.
This operation will remove all your data except for /data/media.
If you wipe ONLY BOOT, then you must to flash new kernel and kernel modules too (/system/lib/modules)!
Make sure that you have nandroid backup and Titanium backup before a full wipe!!!
You must have new ROM on /data/media to flash after full wipe!!!
If AROMA Installer stops at 0%, then you must to press Power button and hold 15-17 seconds to reboot. Then go to recovery and start installation again. This will help you.
***Credits***
amarullz for his AROMA Installer Script.
mike1986 for his SUPER WIPE script for Android Revolution HD.
Venom Team for updater-script for ViperOne.
LlabTooFeR for his updater-script for Maximus.
***Download***
Super_Wipe_HTC_One_FULL_v2.0.2.zip - some updates from 18/03/15
Arhive:
Super_Wipe_HTC_One_FULL_v1.0.2d.zip - 2.66 MB - some updates from 24/11/13
md5: 60cff28e4f5ec11e11c15e7d37c54d35
Enjoy!

Version for HTC ONE M9 (ONLY!!!!)
(Russian interface)
Download:
Super_Wipe_HTC_One_M9_FULL_v3.0.1_RUS.zip

Thank you! :good:

Excellent, i miss this scripts since DHD days Thanks mate...

@Golv - good job

i want to wipe everything except the contents on my sdcard download folder > eg. downloaded roms for flashing in TWRP
what should i choose.
what is this script do is the same as wiping in TWRP recovery?

Magpir said:
i want to wipe everything except the contents on my sdcard download folder > eg. downloaded roms for flashing in TWRP
what should i choose.
what is this script do is the same as wiping in TWRP recovery?
Click to expand...
Click to collapse
You must select all of items then will be deleted data, system, cache the boot partitions, after that you can return back into recovery, choose Install and select rom to flash.
This script makes a wipe as well as in TWRP recovery. It's more convenient to use script for somebody ...

Golv said:
You must select all of items then will be deleted data, system, cache the boot partitions, after that you can return back into recovery, choose Install and select rom to flash.
This script makes a wipe as well as in TWRP recovery. It's more convenient to use script for somebody ...
Click to expand...
Click to collapse
i dont understand what this script does is wipe more stuff than the standard TWRP recovery or what?
isnt wiping the boot partitions dangerous?

Magpir said:
i dont understand what this script does is wipe more stuff than the standard TWRP recovery or what?
isnt wiping the boot partitions dangerous?
Click to expand...
Click to collapse
In TWRP all the same, except wipe of boot partition. And there is no partition format /data/media in this script.
Boot partition can be flashed into bootloader (fastboot usb) through:
Code:
fastboot flash boot boot.img
or through:
Code:
fastboot oem rebootRUU
fastboot flash zip boot.zip
(If you S-OFF you can put into zip 2 files: boot.img and android-info.txt, if s-on - signed firmware.zip)
or into custom recovery (zip).
It's dangerous to delete HBOOT partition! In this case - bricks. If you erased boot partition then you can enter into bootloader and recovery and restore all things! ...

so are u telling me that yr script is different from wiping in TWRP ?
So yr script dont delete Hboot partition?

Do not worry! :laugh:
This script don't delete Hboot partition!

so its safe to use?

I checked all items of script on myself. All safe. And if someone does not think before to do something, it is always dangerous!

Awesome, been using a wipe script for the galaxy nexus, great to have one for the One, thanks OP!

when i use this script.
checked all options and wipe.. no rom and no kernel on my phone?
flash now a rom without choose fullwipe in aroma..
why all my apps on phone, my own homescreen?
sent from my HTC One powered by ViperOne

Hopie, thank you! Try this version. Super_Wipe_HTC_One_FULL_v1.0.2d.zip - 2.66 MB An updated version in OP.

Молодец, @Golv. Так держать.
Great work! Thanks.

forgot to answer
with new version all ok..
ium think u know it ^^
sent from my HTC One powered by IronByte

works this script on android 5?

Hopie said:
works this scriot on androud 5?
Click to expand...
Click to collapse
Yes.