[ Description ]
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.
[ Features ]
Detailed description of every menu item
[ Known Issues ]
v2.3.3 has some screen tearing/color weirdness going on. This is just a graphical bug in the recovery kernel, nothing to worry about. I'll try to fix it in a next version.
[ Download ] - ALWAYS check the md5sum to make sure the file isn't corrupted!
recovery-RA-supersonic-v2.3.img - MD5Sum: c00243750cc79e4a1dd4888db175b19f
PC36IMG.zip - MD5SUM: 6dbb98f9cfa35033982c3803d2520466
Mirror to all my recoveries (Click a few adds to keep it up and running - Thanks DrMacinyasha ^^)
[ Install ] - There are several ways to install a custom recovery, feel free to pick the one that suits you best :
- the Bootloader way - - Thanks Tiffany84 ^^
Place PC36IMG.zip on the root of your sd card.
Boot the phone into the bootloader by powering the phone down, then press the power and the volume down buttons at the same time.
Once the phone boots into the bootloader the phone will automatically recognize the zip file. It will ask if you would like to update, select yes and let it do it's thing and you will be good to go
- via Rom Manager - - STILL NEEDS TO UPDATED TO v2.3!!
Download "Rom Manager" from the Android market
Start "Rom Manager"
Select "Flash ClockworkMod Recovery" and wait for it to finish
Select "Flash Alternate Recovery" and wait for it to finish -> this will install the latest version of RA recovery.
- via terminal app or adb - (Make sure your rom contains flash_image!!)
Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter)
[ Important notes ]
Don't restore wimax nandroids between different phones! If you still plan to do it make sure to remove the wimax image from the nandroid backup before restoring!!
I'll only answer to posts with a real problem description and a pastebin log. All other "issues" will be skipped/ignored.
Make sure have enough free space available on your sdcard when making a nandroid backup!!
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.
[ Special Thanks ]
http://www.androidspin.com for hosting ^^
Tiffany84 for the PC36IMG's ^^
DrMacinyasha for the mirror ^^
jhansche for the initial port of the evo recovery and his menu navigation and verification code.
joncfoo for the menu loop code.
toastcfh for testing and all his awesome work on the Evo (root, unlocked nand, ..) Thanks ^^ Buy him a coffee!!
flipzmode for testing, screenshots and feedback, Thanks ^^
packetlss for all the hours of support and awesome coding skills, THANKS man ^^, donate to Haiti
Koushik Dutta for his awesome work on recoveries and ROM manager ^^
Cyanogen for his dedicated work! , buy him a beer!
Chris Soyars for the new Apps2SD method ^^
JesusFreke for his awesome JFv1.43's recovery , donate
pensive for adding awesome features to Nandroid
51dusty for his sdparted script!
k4str0 for his fix_permissions v2.03 update.
rikupw for the ideas and toggle_ums script.
Change-log
v2.3
Nandroid will skip sd-ext backup when it's not present.
Nandroid will not check the battery percentage anymore.
Switched off signature check by default (Stop asking now, ok?).
Cache is not selected as part of a default Nandroid backup anymore.
Added wipe Boot, System and sdcard to the wipe menu.
Re-ordered some items in the wipe menu.
Switched to a CM android-msm-2.6.35-unified kernel (should stop the endless dots).
v2.2.1
Fixed Nandroid ext backup/restore. It now backups/restore the entire ext.
v2.2
Nandroid backup is now selective, boot/system/cache/data are selected by default.
Nandroid checks if there's at least 500MB free on SDcard before starting a backup.
Kernel min freq is set to max freq to speed up things (tip of toastcfh).
Added/updated error/warning messages.
v2.1.1
Updated kernel to 2.6.32.17 , this should fix the partition issues on newer hboots
Nandroid now backups the entire content of /sd-ext , not just the apps. This fixes bootloops of certain restored roms.
Moved the "Toggle signature verification"-option from the Other- to the main flash-submenu.
Re-ordered the wipe menu.
Added SDEXT support for update scripts.
Added "filebrowser" support when you select a zip to flash.
Added "/.." support to the filebrowser so you can navigate up.
Added a mount menu so you can manually (u)mount stuff.
Added a toggle verification switch so you can flash those awesome unsigned winrar rom releases...
Fully re-wrote the wipe menu (it's not using a script anymore), added a few new wipe options.
Added "/sdcard/.android_secure" support , nandroid now backups/restores .android_secure (Froyo a2sd apps) by default.
Added a few new Google apps to the Google app backup script.
v1.8.0
updated Nandroid so it also backups and restores the wimax partition.
made the recovery 400kb smaller so it fits most recovery partitions with bad blocks.
added a return option (instead of pressing vol-up+down) to the menu (by jhansche).
completely ignore verification (by jhansche).
added menu loop (by joncfoo).
v1.7.0.2
Reduced the overall size so it can still be flashed when having lots of bad blocks.
v1.7.0.1
Initial release (port from my Nexus One recovery)
awesome I was waiting for this i was tired of having to go home to change roms!
Nice, i'm going to try this out right now and report back if there are any problems.
It works nicely. I don't like having to press both volume-keys to go back to the previous menu, but it's not a deal breaker. Good job Amon_RA. =]
trying to flash the image its telling me not found when i tried every which way to flash it any ideas? Ugh sorry maybe i need to read...a little more next time sorry!
Arthur101 said:
trying to flash the image its telling me not found when i tried every which way to flash it any ideas? Ugh sorry maybe i need to read...a little more next time sorry!
Click to expand...
Click to collapse
How are you flashing it? the fastboot method worked fine for me
Edit:
1) Get fastboot.exe here
2) Place recovery-RA-evo-v1.7.0.1.img in the same dir as fastboot
3) boot your phone into fastboot (Volume Dwn+ Power) Select fast boot
Then follow
fastboot devices(press enter) (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-evo-v1.7.0.1.img(press enter)
I keep getting a error opening /sdcard/recovery-RA.img no such file or directory.
Fixter said:
I keep getting a error opening /sdcard/recovery-RA.img no such file or directory.
Click to expand...
Click to collapse
It's recovery-RA-evo-v1.7.0.1.img , not recovery-RA.img ...
Amon_RA said:
It's recovery-RA-evo-v1.7.0.1.img , not recovery-RA.img ...
Click to expand...
Click to collapse
I got the error with both names. I renamed the file to see if I was making mistakes with the file name since it was so long.
Hey, Ra, you do realize we ARE going to need Care Bears on our Evo recoveries just like you spoiled us with on our MT3G's... I'm just saying!
I've tried downloading the file a couple of times to make sure it wasn't corrupted but I keep getting "sending 'recovery' (5032 KB)... OKAY
writing 'recovery'... FAILED (remote: image update error)"
Also thanks for the new recovery, was hoping you'd release one for our Evo's
And I know I have flash_image because I did Toasts Nand Unlock yesterday. And I checked and the file is on the root of the SD Card.
Fixter said:
And I know I have flash_image because I did Toasts Nand Unlock yesterday. And I checked and the file is on the root of the SD Card.
Click to expand...
Click to collapse
it should be in /data
once you restore a rom that didn't have it, it's no longer on the phone where it should be. if you put it back in /data and chmod 755 it you should have no problem.
Cordy said:
it should be in /data
once you restore a rom that didn't have it, it's no longer on the phone where it should be. if you put it back in /data and chmod 755 it you should have no problem.
Click to expand...
Click to collapse
Yup. I just did. I was thinking about this and went ahead. Thanks for the information though.
PS: I get a Build Not Set on the End of the Recovery.
Amon_RA said:
Features
Fix apk uid mismatches :: Does extacly that
Click to expand...
Click to collapse
thanks for this great recovery! im excited to try it!
two quick questions:
does the fix apk uid mismatches uses the common fix_permissions.sh script?
do you have a github or location where the source code is viewable?
thanks again!
Fixter said:
I got the error with both names. I renamed the file to see if I was making mistakes with the file name since it was so long.
Click to expand...
Click to collapse
How are you flashing? Fastboot, flash_image? Are you sure you mounted /sdcard? Do an "ls /sdcard/recovery*" to make sure the sdcard is mounted and that the recovery image can be found.
Cordy said:
I've tried downloading the file a couple of times to make sure it wasn't corrupted but I keep getting "sending 'recovery' (5032 KB)... OKAY
writing 'recovery'... FAILED (remote: image update error)"
Click to expand...
Click to collapse
Did you unlock NAND?
joeykrim said:
thanks for this great recovery! im excited to try it!
two quick questions:
does the fix apk uid mismatches uses the common fix_permissions.sh script?
do you have a github or location where the source code is viewable?
thanks again!
Click to expand...
Click to collapse
Erm, I'm using the same fix_permissions.sh script as in my other recoveries, check github :
Scripts : http://github.com/packetlss/amonra_recovery_scripts
Recovery : http://github.com/packetlss/amonra_bootable_recovery
Still need to push the evo recovery.
Amon_RA said:
Did you unlock NAND?
Click to expand...
Click to collapse
Yes, I'm able to flash toasts recovery.img through fastboot no problem.
How do I check if I loaded the recovery correct? I get a Build : Not Set when I entered the recovery on the lower end where its suppose to say the build number.
You should work together with Koush and make one great recovery. He has some features such as the ability to flash a zip from ANYWHERE on the SD Card. The two of you should be able to work some miracles.
Ceger
Related
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!
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 v1.4 recovery.
The purpose of this recovery is to avoid using adb by accessing all features directly from the menu.
This recovery if for the HTC Sprint Hero only, if you have an :
- HTC Hero you should go here.
- HTC Dream/G1 you should go here.
- HTC Magic/MT3G you should go here.
This recovery is for the CDMA based Hero from Sprint only!
Ext4 is NOT supported because we don't have the kernel Source of the HTC Sprint Hero yet... Sorry
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).
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)
Features
full ADB access in recovery mode
Awesome Care-Bear version! (Blame packetlss for talking me into it )
Busybox v1.15.3
HW-Key navigation (volume keys + CALL-ANSWER) 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 (recovery partition not included!)
Nand backup :: Make a Nand backup
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 from console :
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.
Install
There are several ways to install a custom recovery, choose the one that suits you most (I probably forgot a few).
via adb -> Requires a custom recovery (with test-keys)
Code:
Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
via fastboot + adb -> In case you don't have a custom recovery, so when you get signature fail errors
Code:
adb shell reboot bootloader
fastboot boot recovery-RA-heroc-v1.6.2.img
adb shell mount /sdcard
adb push recovery-RA-heroc-v1.6.2.img /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell reboot
Download
Latest :
recovery-RA-heroc-v1.6.2.img (Click here to download from a Mirror) - MD5Sum: 8382266e4cea526c3cd49d9610f083e0
recovery-RA-heroc-v1.6.2-green.img (Click here to download from a Mirror) - MD5Sum: 41d833b6489aec0617eda0fd4415af8a
recovery-RA-heroc-v1.6.2-blue.img (Click here to download from a Mirror) - MD5Sum: 7ab7e13bbd3e0ad7d84398760398bb77
recovery-RA-heroc-v1.6.2-pink.img (Click here to download from a Mirror) - MD5Sum: c9d4d456acfd1440adddc6d989847219
Old versions :
recovery-RA-heroc-v1.5.2.img (Mirror) - MD5Sum: ccaff51d3a28861240fa9d455924a50f
Change-log :
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://www.androidspin.com for hosting ^^
http://theunlockr.com for all the awesome video’s ^^
Cyanogen for his dedicated work! , buy him a beer!
JesusFreke for his awesome JFv1.43's recovery , donate
Quick shoutout to the_miker and jmanley69 for helping with the testing.
i love you... In a non homo way. But seriously, you are great. Thanks for helping us CDMA users.
Agreed. Thank you all so much. Now is it possible to include apps2sd in the image or do we have to wait for a Rom foe this?
chuckhriczko said:
Agreed. Thank you all so much. Now is it possible to include apps2sd in the image or do we have to wait for a Rom foe this?
Click to expand...
Click to collapse
Apps2SD is usually part of a modded rom, it's possible to do now that you guys have root, but the recovery is not involved in any of that though (except making it easier to fiddle with the phone).
Yes but I know the latest recovery image for the dream had an apps2sd option. I just figured that would be easier.
how do you root cdma hero?
edit: i found info.. thanx amon_ra for the recovery
@Amon_RA - well done mate this is great news for all our American cousins and a major break though in my opinion.
The image works like a charm! I tried installing MoDaCo's 2.9 Image and it just hung at the HTC screen but the nandroid backup from the image restored fine and dandy.
thecodemonk said:
The image works like a charm! I tried installing MoDaCo's 2.9 Image and it just hung at the HTC screen but the nandroid backup from the image restored fine and dandy.
Click to expand...
Click to collapse
you have to wait for ROMs with a CDMA kernel
mopodo said:
you have to wait for ROMs with a CDMA kernel
Click to expand...
Click to collapse
Yeah I figured...just thought it was worth trying to see if something might just happen to work out of the box.
ive been trying for like 2 hours to install this rom to my sprint hero and i cant get it someone help
how do you get it to not stick on the htc screen on reboot after flash?
Do I load this the same way as other recovery images? Like I did with my myTouch and my G1? Thanks. Just confirming before I **ck up my friend's Hero.
I tried to adb into recovery but I can't, as I do on the G1, hit Alt-L by the triangle. I hate to be a n00b about this but this one seems to be entirely new to me.
thorracing1 said:
ive been trying for like 2 hours to install this rom to my sprint hero and i cant get it someone help
Click to expand...
Click to collapse
This isn't a ROM, it's just a recovery image used to INSTALL a ROM (and perform backups and other things).
Can you walk us through what you did, step by step, so we can figure out where the problem may be?
AndroidAppCritic said:
Do I load this the same way as other recovery images? Like I did with my myTouch and my G1? Thanks. Just confirming before I **ck up my friend's Hero.
I tried to adb into recovery but I can't, as I do on the G1, hit Alt-L by the triangle. I hate to be a n00b about this but this one seems to be entirely new to me.
Click to expand...
Click to collapse
I don't know how the myTouch did it but there's a guide you can follow to get it in the CDMA forum: (root AND flashing the recovery image)
http://forum.xda-developers.com/showthread.php?t=581577
(If you're on a Mac: http://forum.xda-developers.com/showthread.php?t=581686)
OR you can follow that guide or perform the flashrec method:
http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click/
(substitute the newest version of flashrec from http://zenthought.org/content/project/flashrec and use the Recovery image from this thread instead of the one mentioned in the link above)
The flashrec doesn't give you root but you can just drop the image in I believe still.
thecodemonk said:
I don't know how the myTouch did it but there's a guide you can follow to get it in the CDMA forum: (root AND flashing the recovery image)
http://forum.xda-developers.com/showthread.php?t=581577
(If you're on a Mac: http://forum.xda-developers.com/showthread.php?t=581686)
OR you can follow that guide or perform the flashrec method:
http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click/
(substitute the newest version of flashrec from http://zenthought.org/content/project/flashrec and use the Recovery image from this thread instead of the one mentioned in the link above)
The flashrec doesn't give you root but you can just drop the image in I believe still.
Click to expand...
Click to collapse
Yeah, I realized I was being a n00b and didn't bother to search too much before asking. But I figured someone else was going to ask anyway so I'd take any flaming if need be. Thanks a lot. I had it rooted when I asked but wanted busybox and the other goodies from the recovery. The easiest root ever.
uses for recovery image
This is my first phone root and I've gotten everything done and complete and just want to learn a little more. I searched but probably not for the correct terms but I'm wondering what for/when some of these options on the recovery image are needed. If there is an explanation somewhere, just point me, otherwise, I appreciate the help with answers! Thanks!
o Wipe data + cache (factory reset) DO YOU LOSE ROOT/RECOVERY IMAGE FLASH?
o Wipe ext partition on SD-card WHAT FOR/WHEN?
o Wipe Dalvik-cache on SD-card (NOT on /data !) WHAT FOR/WHEN?
o Repair ext filesystem WHAT FOR/WHEN?
o Convert ext2 to ext3 THIS IS FOR APP2SD TO WORK RIGHT? **nevermind found answer to this one
o Fix package UID mismatches WHAT ARE UID MISMATCHES?
o Fix auto-rotate issues WHAT ISSUES?
jirafabo said:
This is my first phone root and I've gotten everything done and complete and just want to learn a little more. I searched but probably not for the correct terms but I'm wondering what for/when some of these options on the recovery image are needed. If there is an explanation somewhere, just point me, otherwise, I appreciate the help with answers! Thanks!
o Wipe data + cache (factory reset) DO YOU LOSE ROOT/RECOVERY IMAGE FLASH?
Click to expand...
Click to collapse
This formats the data and cache partition on the phone. Data is where the installed applications and system settings are stored normally. Basically it factory resets the phone back to an unconfigured state. You do not lose root or recovery.
o Wipe ext partition on SD-card WHAT FOR/WHEN?
Click to expand...
Click to collapse
Often we used an ext2/3/4 partition on the SD card to store applications (instead of storing them on the data partiton in the phone) This is what's called Apps2SD that you're seeing all over the forum, it allows us to install much more applications since the ext partition can be much bigger than the internal data partition. Wipeing this means that the entire ext partition is cleared.
o Wipe Dalvik-cache on SD-card (NOT on /data !) WHAT FOR/WHEN?
Click to expand...
Click to collapse
Dalvik is the program that runs all the Android applications (written in Java). It needs to store a cache of the compiled versions of that somewhere so it doesn't have to compile them every time they run. This is normally done on the data partition, but some people choose to move this to other places (like the SD cards ext partition). This option lets them wipe it easily. At this time I don't think there are any Hero customs roms that use this feature.
o Repair ext filesystem WHAT FOR/WHEN?
Click to expand...
Click to collapse
Sometimes the filesystem can become corrupt (for example if the battery runs out just as the phones write to the filesystem). This option tries to repair it.
o Fix package UID mismatches WHAT ARE UID MISMATCHES?
Click to expand...
Click to collapse
On android each installed application is assigned it's own userid (uid) in the operating system. This is for security purposes. If you have your apps on an ext partition on your card (apps2sd), and you install a new rom, there will be a mismatch between the uid assigned to the files/directories on the card and what the Android OS thinks the apps uid is. This option runs a script to try and correct that.
o Fix auto-rotate issues WHAT ISSUES?
Click to expand...
Click to collapse
Some phone (mostly G1s and Sapphires) sometimes have issues with the calibration of the accelormeter. The calibration data is saved in a specific file. This option just removes that file to reset the calibration to factory value. I've never heard of the Hero having these issues and the option is there just in case basically.
packetlss said:
This formats the data and cache partition on the phone. Data is where the installed applications and system settings are stored normally. Basically it factory resets the phone back to an unconfigured state. You do not lose root or recovery.
Often we used an ext2/3/4 partition on the SD card to store applications (instead of storing them on the data partiton in the phone) This is what's called Apps2SD that you're seeing all over the forum, it allows us to install much more applications since the ext partition can be much bigger than the internal data partition. Wipeing this means that the entire ext partition is cleared.
Dalvik is the program that runs all the Android applications (written in Java). It needs to store a cache of the compiled versions of that somewhere so it doesn't have to compile them every time they run. This is normally done on the data partition, but some people choose to move this to other places (like the SD cards ext partition). This option lets them wipe it easily. At this time I don't think there are any Hero customs roms that use this feature.
Sometimes the filesystem can become corrupt (for example if the battery runs out just as the phones write to the filesystem). This option tries to repair it.
On android each installed application is assigned it's own userid (uid) in the operating system. This is for security purposes. If you have your apps on an ext partition on your card (apps2sd), and you install a new rom, there will be a mismatch between the uid assigned to the files/directories on the card and what the Android OS thinks the apps uid is. This option runs a script to try and correct that.
Some phone (mostly G1s and Sapphires) sometimes have issues with the calibration of the accelormeter. The calibration data is saved in a specific file. This option just removes that file to reset the calibration to factory value. I've never heard of the Hero having these issues and the option is there just in case basically.
Click to expand...
Click to collapse
Really appreciate the reply. Know it wasn't a short one!
One more... for uids, the uid stays the same if I just reinstall the same ROM? The ROM determines the uid correct? I played with my phone so much yesterday that by the end of the day I had flashed my backup and modaco over top 3 times in all. Didn't have any problems with apps and apps2sd looks to be running well, so I assume the uid's stay the same if you stick with the same rom.
Hi all,
My port of TWRP. I know berni posted a build already, but mine is newer and I've tested it for a few days, haven't seen any buggy behaviour other than buggy restore (see bug hunting).
Features (copied from TWRP list):
Ability to save custom recovery settings
Default partitions to back up
Default zip folder location
Default color theme (lots to choose from) (Thanks to ffolkes!)
Default Time Zone (for more accurate time stamps)
Zip Signature Verification
Zip md5 Verification (looks for file with zipname.zip.md5)
Ability to flash multiple zips in one go
Ability to select which individual partitions to backup, and restore.
Ability to choose compression or no compression backups.
Compression takes longer of course, but you save roughly half the space. EVO3D's stock system uncompressed is ~800mb, 380mb compressed. You choose.
Ability to auto restore GAPPS on zip flash (for CM based ROMS)
Ability to auto reboot after successful flashes (for the lazy)
Some devices utilize their capacitive buttons in recovery.
Home - Main Menu
Menu - Advanced Menu
Back - Up a Menu Level
Search - Select Current Selection
Battery Level and Timestamp (Better safe than sorry)
Prerequisites:
Rooted phone
P920 recommended, untested on P925
How to install:
1. Download recovery.img which is attached.
2. Copy it to the folder containing adb.
3. Shift+Right click in the folder, select open command window here
4. Enter the following commands (hit enter after every line):
adb push recovery.img /sdcard/recovery.img
adb shell
su (you might have to accept a Superuser prompt)
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096
exit
exit
Click to expand...
Click to collapse
5. Enter adb reboot recovery and hit enter
6. ???
7. Profit!
Screenshots:
Follow the instructions above and you get interactive and functional "screenshots"
Credit for this goes to TeamWin for their very cool recovery and the CyanogenMod team for all that they do. Thanks also to berni for giving me the motivation to port it myself due to nonfunctional cache wiping
Bug hunting:
EXT4 backups don't restore properly (have a theoretical fix for this, stay tuned. In the meantime, rename all files which look like *.ext4.win to *.ext3.win by mounting USB storage on your computer and do the same for the md5 files)
If there are any bugs please tell me about it.
Changelog:
18/8: initial release
Hi, is it works on optimus 3D MAX?
Thanks in advance
Not sure. This is entirely untested on that, but I doubt it works
Sent from my LG-P920 using Tapatalk 2
Hi pandaball, we allready pm each other. Can u make twrp for O3D Max? I can provide u the stock recovery and the mountpoints!
Lots of people would be thankful.
I tryed myself but didnt get it to work.
Thanks in advance
Kind regards,
Sent from my LG-P720 using xda app-developers app
No. The phone has to be supported by CyanogenMod first.
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
TWRP Recovery
For Galaxy Fit
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
BUGS:
If you have found a bug, please consider posting it here.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
SPECIAL NOTE:
This is the first build of TWRP and may have some unknown bugs. I take no responsibility of your devices. This is "testing" phase (for some days only). Help in testing if you wish to otherwise stay away until a final release. Don't post back here that: "You destroyed my phone", "You are cheating", "You are playing with my device".
One more thing, we are using androidarmv6 sources and if you are asking for help on IRC channel mentioned above then please mention there that: "we are not using CM or OMNI sources, we are using androidarmv6 sources".
CREDITS:
TeamWin: For this awesome open-source recovery.
androidarmv6 team: To make all these possible.
@chraso: Hosting & for providing Compatible flags
Me: Compiling
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes.
DOWNLOAD:
http://www.mediafire.com/view/?xum64uit9a43q6s
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
About the current build:
STABLE.
Reboot to system bug now fixed.
Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2
TpupLpasa said:
One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works.
Click to expand...
Click to collapse
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail
TpupLpasa said:
Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2
Click to expand...
Click to collapse
jemail said:
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail
Click to expand...
Click to collapse
1st - install PhilZ Touch Recovery 6.40.1.
2nd - install twrp.
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Ok, thanks.
update
Bhargav97 said:
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Click to expand...
Click to collapse
heh, doesn't work. I just use Windows 8.1 with the latest updates. Maybe this is a problem... Maybe not...:crying:
Bhargav97 said:
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Click to expand...
Click to collapse
I would advise against this. I tried it and it soft bricked my phone.
I will wait for the official release, which I hope will be soon. I really like TWRP.
jemail
TpupLpasa said:
Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2
Click to expand...
Click to collapse
jemail said:
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail
Click to expand...
Click to collapse
iSanechek said:
Ok, thanks.
update
heh, doesn't work. I just use Windows 8.1 with the latest updates. Maybe this is a problem... Maybe not...:crying:
Click to expand...
Click to collapse
@Bhargav97, as you kindly asked me I tried to complete the recovery image.
Guys, as I don't own any Fit device, you'll have to flash this at your own risk. Though I've done this before for my device. If anything will not work - let me know. Good Luck!
DL Link: remooved
belyava said:
@Bhargav97, as you kindly asked me I tried to complete the recovery image.
Guys, as I don't own any Fit device, you'll have to flash this at your own risk. Though I've done this before for my device. If anything will not work - let me know. Good Luck!
DL Link: http://yadi.sk/d/IAr6Z_OvQohqq
Click to expand...
Click to collapse
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
This image completely screws the boot image too, you cannot normal boot after flashing the recovery image. Reflashing the previous working recovery image does not help. I have to restore a recovery image using ODIN to get back to a functional recovery.
No success I am afraid.
jemail
jemail said:
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
No success I am afraid.
jemail
Click to expand...
Click to collapse
sorry, I must have made a mistake. I''ll check tomorrow. Sorry for the inconvenience
jemail said:
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
This image completely screws the boot image too, you cannot normal boot after flashing the recovery image. Reflashing the previous working recovery image does not help. I have to restore a recovery image using ODIN to get back to a functional recovery.
No success I am afraid.
jemail
Click to expand...
Click to collapse
Ok, try this one
belyava said:
Ok, try this one
Click to expand...
Click to collapse
Success!
Install Zip -> works.
Back up -> works.
Wipe -> works.
Restore -> works.
Reboot System -> works.
Reboot Recovery -> works.
Great work.:good:
Will continue to test and report any bugs.
jemail
jemail said:
Success!
Install Zip -> works.
Back up -> works.
Wipe -> works.
Restore -> works.
Reboot System -> works.
Reboot Recovery -> works.
Great work.:good:
Will continue to test and report any bugs.
jemail
Click to expand...
Click to collapse
There are a lot of method nowadays for unpack-repack and most of them fails to make a proper repack, so you'll have booting problems like you had when you tried to do it yourself. I just told @belyava to do unpack-repack because he did this with the recovery (TWRP - had same reboot to system issue) of his device successfully. Thanks @belyava for this help.
Everything expected to work. However, you can always report bugs with a proper recovery logfile.
Updated download link with a new mediafire link. The latest build can be now labelled as STABLE build.
hi anyone have got it if possible in rar zip for this recovery.
ahmetakin said:
hi anyone have got it if possible in rar zip for this recovery.
Click to expand...
Click to collapse
Why do u need a flashable package when u can install it simply via terminal emulator?
@jemail will u kindly check the time taken while backup and restoring rom? Just to know whether this is better than CWM.
swat4samp said:
Why do u need a flashable package when u can install it simply via terminal emulator?
@jemail will u kindly check the time taken while backup and restoring rom? Just to know whether this is better than CWM.
Click to expand...
Click to collapse
I can't speak for your ROM, but for me back up ( 3 1/2 mins max) and restore (3 1/2 mins max).
jemail
Ok yesterdeay install with terminal emulator thanks.