This is a basic question that is annoying because it highlights how much I don't really understand.
What is actually wiped using the different recoveries and should I prefer one over the other?
Details:
I have been using Amon_RA 1.5.2 for quite some time and it is fine. But recently I had to revert to a sense rom to get the newest PRL (60677) since I wasn't getting SMS. When reverting, it made me wonder where this update was kept that it wasn't removed during my wipe, and also, are there other things hanging around which should be cleaned up?
My current root file structure looks like this (ND=not a directory):
acct
cache
config
d
data
default (ND)
dev
etc
init (ND)
init.goldfish (ND)
init.heroc (ND)
init (ND)
mnt
..../asec
..../sdcard
..../secure
proc
root
sbin
sd-ext
sdcard
sys
system
*I had been messing with Apps2SD though it is not currently used on this set up. Should explain the multiple SD card mnts.
Amon_RA 1.5.2 Wipe Menu
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
Clockwork 2.5.0.7 Wipe Menu
wipe data/factory reset
wipe cache partition
Additional Clockwork 2.5.0.7 Mounts and Storage Menu
format boot
format system
format data
format cache
format sdcard
format sd-ext
Any clarification would be much appreciated by me, and I assume the community. Thanks.
--------------------------------------------------------------------
A different thread discussing general difference between Amon_RA and Clockwork
I can't provide much help technically, but I wanted to point out clockwork 2.5 also has a Wipe Dalvik Cache option under the Advanced menu.
I'd definitely like some more technical information too, but I can provide what I've read and observed.
Factory reset wipes data AND cache.
Wiping boot and system happen already when flashing a rom and wiping either will require you to nandroid or reflash the rom. Many roms seem to suppress the messages or something.
[dpeeps74]
mtnchkn said:
Details:
I have been using Amon_RA 1.5.2 for quite some time and it is fine. But recently I had to revert to a sense rom to get the newest PRL (60677) since I wasn't getting SMS. When reverting, it made me wonder where this update was kept that it wasn't removed during my wipe, and also, are there other things hanging around which should be cleaned up?
Click to expand...
Click to collapse
The radio itself, PRL, PRI, and profile, are all stored in a deeper part of the phone than recovery or bootloader, if I remember right it's hardcoded into the dialer function of the phone (NOT in the .apk or ROM), so they stick no matter what you wipe or flash. As for what's different between the 2 recoveries, they both do basically the same thing, but CWM has more wipe options and is newer code, also when flashing zips from CWM you can actually select them inside of folders from your sd, whereas with amon ra it must be on the root of your sd. Also, in amon ra there is an option to "fix UID mismatches" which could be helpful if your device goes crazy but I've never had to use it. CWM has a fix permissions option, but you can also do that from TE, so again, not much use to me personally. I use 2.5.0.1 because it will flash both amend and edify zips, it's green, and doesn't give me the error code that 2.5.0.7 did. I have used every recovery available for the heroc. Also, the 3x versions of CWM have even more options and wipe options. The other sucky thing about CWM is the fact that wipe sd is right next to wipe cache in mounts so people sometimes wipe the wrong one. That is why tte one in the main menu is the one to use for wiping cache. Also, wipe and format are the same thing, different words. Feel free to pick them both apart, I think clockwork has much better functionality, even though the UI kinda blows compared to amon ra. YMMV.
You shluld give RA.1.7 a try
Yea it's Me Again With The
Modified Hero
Wow, this is exactly what's been on my mind lately... I've been looking at the ClockworkMod thread in dev lol.
I just switched from Amon_RA 1.7 to CWM 3.0.2.4 last night. I decided that since I'm trying CM7 for the first time, I would also try a new recovery. Il Duce summed up the differences nicely. What I found comforting was that nandroid backups made in one recovery can be recovered in other recoveries, you just have to move your backups to the appropriate location on the SD card.
I think they're about equal. Amon_RA has a nice interface, and I much prefer the press Home to confirm instead of CWM's. With CWM, you could choose a "Format /system" or something and you are only presented with a "Yes - wipe" confirmation, which doesn't actually tell you what you're wiping. And like Il Duce said, that could easily wipe the sdcard instead of cache. But with CWM you can make your SD card less cluttered and put zips in different folders.
If you're not using Firerat's mod, there's no reason not to just try them all
If you are using Firerat's mod, it's just a bit more troublesome.
laie1472 said:
You shluld give RA.1.7 a try
Yea it's Me Again With The
Modified Hero
Click to expand...
Click to collapse
My phone doesn't handle anything that is OC, which makes me weary of 1.7 since I thought it was OC'ed.
Is it?
mtnchkn said:
My phone doesn't handle anything that is OC, which makes me weary of 1.7 since I thought it was OC'ed.
Is it?
Click to expand...
Click to collapse
darch-ra 1.7 is capped at 691.
mtnchkn said:
My phone doesn't handle anything that is OC, which makes me weary of 1.7 since I thought it was OC'ed.
Is it?
Click to expand...
Click to collapse
IIRC it is OC'ed to 768 MHz.
c00ller said:
IIRC it is OC'ed to 768 MHz.
Click to expand...
Click to collapse
no that's godspeed. 1.7 works fine on my phone, which dies over 729, which means 1.7 isn't 768, it's probably 691, but most def it's not higher than 729.
So what is a good download link for the image, since the only 1.7 I can find on the forums is the 'unofficial mirror of Darch 1.7' which gives me an error when I try flashing (says there is no image)?
il Duce said:
no that's godspeed. 1.7 works fine on my phone, which dies over 729, which means 1.7 isn't 768, it's probably 691, but most def it's not higher than 729.
Click to expand...
Click to collapse
mtnchkn said:
So what is a good download link for the image, since the only 1.7 I can find on the forums is the 'unofficial mirror of Darch 1.7' which gives me an error when I try flashing (says there is no image)?
Click to expand...
Click to collapse
my dropbox
http://dl.dropbox.com/u/5669105/darchra.img
il Duce said:
my dropbox
http://dl.dropbox.com/u/5669105/darchra.img
Click to expand...
Click to collapse
I really apprecaite the link but I get the same error as I did last time I was flashing a darch image
Code:
flash_image: not found
will try it again later with adb.
mtnchkn said:
I really apprecaite the link but I get the same error as I did last time I was flashing a darch image
Code:
flash_image: not found
will try it again later with adb.
Click to expand...
Click to collapse
I wonder if that means the command is "not found" or if it's saying the .img is not found. If it's the latter, make sure you put quotes around the file path if there are spaces, e.g,
flash_image recovery "C:\Android Folder\recovery.img"
If it's the first, then you're right, it should work in adb shell.
mtnchkn said:
I really apprecaite the link but I get the same error as I did last time I was flashing a darch image
Code:
flash_image: not found
will try it again later with adb.
Click to expand...
Click to collapse
Make sure the recover img. Is named.
recovery-heroc-RA-1.7.img
And make sure its not
img.img.
Sometimes the file is not named correctly. Also make sure the img. Is on the root of your sd/card and not in any folder. Good luck
Yea it's Me Again With The
Modified Hero
Turns out I was missing flash_image command. I am going to include the solution below for others, but bottom line, everything is fine now and am running 1.7. If someone has a download for CW 2.5.0.1 which someone mentioned, post it too. Also, here is 1.5 if anyone needs it
http://dl.dropbox.com/u/1759357/recovery-heroc-RA-1.5.zip
I came across this post, which pointed to a flash_image file here. So I copied that into my tools folder, then...
Code:
>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT041HF00432 device
C:\android-sdk-windows\tools>adb root
adbd is already running as root
C:\android-sdk-windows\tools>adb remount
remount succeeded
C:\android-sdk-windows\tools>adb push flash_image /system/bin
851 KB/s (26172 bytes in 0.030s)
C:\android-sdk-windows\tools>adb shell chmod 0755 /system/bin/flash_image
C:\android-sdk-windows\tools>adb shell flash_image recovery /sdcard/recovery-heroc-RA-1.7.img
C:\android-sdk-windows\tools>adb shell reboot recovery
So now I have a new recovery.
Related
hello all, just trying to get a little input on the correct procedures for clearing the cache inbetween roms. i recently swithed from cyanmod 4.1.6 to Drizzy's Hero-V1.2r1 . Ive tried several commands in console so far to wind up reading something along the lines of : not found. Could someone inlighten me with the correct commands to do this or even the correct steps such as wipe, flash , yada yada and then what commands. thanks in advance , veritas
ronrey, so ronreyyyy, so ronrey im all aloonnneeeee
When you switch roms the only thing you need to do is wipe your ext partition and wipe your phone (alt + w). I use Ubuntu to clear my partition, but there are commands to do it if thats what your asking.
supremeteam256 said:
When you switch roms the only thing you need to do is wipe your ext partition and wipe your phone (alt + w). I use Ubuntu to clear my partition, but there are commands to do it if thats what your asking.
Click to expand...
Click to collapse
when u switch roms a small trace of them remains behind in the dalvik folder in the internal that doesnt just get cleared using alt+w so there are a set of commands to handle this task and i believe they go something like this rm -rf system/sd/dalvik-cache. along with some pre and post commands, that are the ones im refering to.
actually here is a direct quote of what i found, i just couldnt get these commands to work, so im thinking maybe they differ when switching to hero, maybe not..but they didnt work for me>>>>>>>>>>>>>>>>>>>>>
Monday, 31 August 2009 18:51 by Simon Walker
--------------------------------------------------------------------------------
User Rating: / 1
PoorBest
--------------------------------------------------------------------------------
So I started running into some performance problems with the Enomther ROM and was considering removing it and going back to Cyanogen. I decided to have a quick chat with Enomther and he gave me some things to do. The results are even more amazing than the first install.
I found out that the dalvik-cache gets carried over between ROM installs and that it can cause problems and that I should delete it, wipe my phone and start again. Enomther gave me this little guide to follow:
Ok ... so reboot into cyanogen's recovery
Press (Alt+x) to enter the console
Enter the following commands ...
mount system
mount system/sd
rm -rf system/sd/dalvik-cache
umount system/sd
umount system
recovery
This will bring you back to recovery, from there perform the "Data Wipe" option in the menu.
When it's done reboot and you should be all good. Of course you'll have to redo your settings, but your apps will reinstall properly.
I'm using cyanogen-4.1.999 and for some reason, I'm seeing a massive speed decrease. I got 4.1.99 to run before it, but it also got slow-downs as well. None of cyanogen's roms did this before.
Example. It takes more than a few seconds for the screen to go from off, to maximum illumination (according to system setting that is).
What should I do?
I don't know what rom you were running before cm-4.1.99 but before you flash 4.1.99 make sure you wipe/clear your ext2/3/4 if you are using a second partition. After you have flashed 4.1.99 you should no longer need to wipe/clear your ext partitions when installing new cyanogen versions
ninjavampire said:
I don't know what rom you were running before cm-4.1.99 but before you flash 4.1.99 make sure you wipe/clear your ext2/3/4 if you are using a second partition. After you have flashed 4.1.99 you should no longer need to wipe/clear your ext partitions when installing new cyanogen versions
Click to expand...
Click to collapse
Crap... I only wiped ALT+W style. Oh well. Should I wipe ALT+W again after reformating?
edit: and when you say second partition, you mean the SDcard right?
Instructions to install cm-4.1.99 and 4.1.999 using cm-recovery1.4
Download tmo1.6, cyanogen 4.1.99 and cyanogen 4.1.999 from cyanogen fourm to root of your sd card (not in any folder)
Boot into recovery mode (home+power)
Wipe
If you are not using a second partition ignore next steps
Enter recovery console any type the following:
#mount -o /system/sd
#rm -rf /system/sd/*
#reboot recovery
Wipe again
Fix filesystems
Continue here if you are not using a second partition
Select option flash any .zip from sdcard and flash the tmo1.6 rom
When it is finished select option flash any .zip from sdcard and flash cm-4.1.99. You can do this with out rebooting your phone after the tmo1.6 flash
When 4.1.99 is finished select reboot option (home+back)
After boot and phone setup turn off your phone and boot into recovery again (home+power)
Select option flash any .zip from sdcard and select cm-4.1.999
When finished reboot phone (home+back) and enjoy the awesomness of Cyanogen!
Tactical Fart said:
Crap... I only wiped ALT+W style. Oh well. Should I wipe ALT+W again after reformating?
edit: and when you say second partition, you mean the SDcard right?
Click to expand...
Click to collapse
Yes I mean the sdcard when talking about second partition
ninjavampire said:
Instructions to install cm-4.1.99 and 4.1.999 using cm-recovery1.4
Download tmo1.6, cyanogen 4.1.99 and cyanogen 4.1.999 from cyanogen fourm to root of your sd card (not in any folder)
Boot into recovery mode (home+power)
Wipe
If you are not using a second partition ignore next steps
Enter recovery console any type the following:
#mount -o /system/sd
#rm -rf /system/sd/*
#reboot recovery
Wipe again
Fix filesystems
Continue here if you are not using a second partition
Select option flash any .zip from sdcard and flash the tmo1.6 rom
When it is finished select option flash any .zip from sdcard and flash cm-4.1.99. You can do this with out rebooting your phone after the tmo1.6 flash
When 4.1.99 is finished select reboot option (home+back)
After boot and phone setup turn off your phone and boot into recovery again (home+power)
Select option flash any .zip from sdcard and select cm-4.1.999
When finished reboot phone (home+back) and enjoy the awesomness of Cyanogen!
Click to expand...
Click to collapse
Ohh i had the same problem too. So Do we need to do the 'alt w' in recovery still?
NOback said:
Ohh i had the same problem too. So Do we need to do the 'alt w' in recovery still?
Click to expand...
Click to collapse
Yes in the instructions I posted above "wipe" is the same as "alt+w"
Doing all those instructions seems to be a lil extreme. Clear your data and cache in the browser, google maps, and street view (thats where it's held the most). And then go to terminal and type:
Code:
su
cd /system/sd/dalvik-cache
rm *
exit
exit
Then reboot your phone. It will take awhile for it to boot up like the very first time flashing.
supremeteam256 said:
Doing all those instructions seems to be a lil extreme. Clear your data and cache in the browser, google maps, and street view (thats where it's held the most). And then go to terminal and type:
Code:
su
cd /system/sd/[B]dalvik[/B]-cache
rm *
exit
exit
Then reboot your phone. It will take awhile for it to boot up like the very first time flashing.
Click to expand...
Click to collapse
fixed typo (dalvik instead of dalvick)
B-man007 said:
fixed typo (dalvik instead of dalvick)
Click to expand...
Click to collapse
Thank you. Way to keep your eye on the ball son.
This only worked until today. When I checked the directory some (all?) of the files there were restored and I had to "rm *" the directory again. Earlier, it took me about 5 minutes to get the phone to cooperate long enough to order a reboot. Ideas?
Tactical Fart said:
This only worked until today. When I checked the directory some (all?) of the files there were restored and I had to "rm *" the directory again. Earlier, it took me about 5 minutes to get the phone to cooperate long enough to order a reboot. Ideas?
Click to expand...
Click to collapse
Well when you reboot the phone...android remakes those files. thats why it takes so long to boot after you do that. the phone should run smoother then.
Have you tried wiping your ext partition?
B-man007 said:
Have you tried wiping your ext partition?
Click to expand...
Click to collapse
Yes. I used sdparted to nuke the whole thing. Now I have a main, swap, and ext2 partitioned card.
Tactical Fart said:
Yes. I used sdparted to nuke the whole thing. Now I have a main, swap, and ext2 partitioned card.
Click to expand...
Click to collapse
is it in that order? because its in the wrong order then. it needs to be FAT32, EXT, Linux-Swap
you should upgrade to EXT3 as it uses journaling (its safer)
did you try booting without the sd card? (wipe and flash the update, remove the sdcard, and reboot)
is there still a problem with the speed w/o it?
No, my partitions are the order you said they should. It was just a basic reformat without any special paramaters.
Also, the slow downs don't occcur until the phone has been on for a while. A reboot fixes the problem quickly, but while the problem is in place, I can't use "su" in the terminal (the phone is so slow that the su permissions manager can't respond in time to give permission and it refuses) and I can't receive calls. Plus it takes about 5 minutes of fighting to reboot, and thats if I don't pull the battery.
Tactical Fart said:
No, my partitions are the order you said they should. It was just a basic reformat without any special paramaters.
Also, the slow downs don't occcur until the phone has been on for a while. A reboot fixes the problem quickly, but while the problem is in place, I can't use "su" in the terminal (the phone is so slow that the su permissions manager can't respond in time to give permission and it refuses) and I can't receive calls. Plus it takes about 5 minutes of fighting to reboot, and thats if I don't pull the battery.
Click to expand...
Click to collapse
im starting to get these problems too. Cyan is going to release anotherr rom (probably today) that aims to fix some of the major errors with the rom according to his twitter. I guess we should just wait and see if it makes it better
cyanogen 4.1.99 and 4.1.999 slow down cure
I upgraded two g1’s to 4.1.99 and then to 4.1.999. First they were slow. I had to upgrade my ext2 partition to ext3. I did this from cyanogen recovery console, 4.1 If you already have 4.1 console installed, Go to console, enter/return, on the keyboard and typed the command, upgrade_fs next to the # and then pressed enter.
If you do not have recovery console 4.1 installed. Use this link below, in the instructions for installing it from the terminal emulator make sure you type, su then press the return/enter then type in the flash command per the instruction.
http://www.cyanogenmod.com/downloads/recovery-image
Then you must be in the 4.1 recovery console, you access by holding down the power and home buttons while rebooting, got to alt-x, Go to console)
in console press enter/return
type the command upgrade_fs then press enter/return then type reboot and press enter/return.
I then downlaoded everything I needed and put them on my sd card and installed following these instructions.
http://www.simplehelp.net/2009/10/04/how-to-install-cyanogenmod-4-1-99-on-your-g1-android-phone/
Worked like a charm and runs fast and stable. Hope this helps.
there are a number of problems with the recovery in the just leaked
Froyo ROM.
1. signature checking
2. passing API version 3 to the updater binary
3. forced wipe after installing an update.zip
the attached zip has a 3e recovery modified to disable signature checking
report API version 2 for backwards compatibility with clockwork mod recovery
and disable the forced wipe after installing any update.
I don't know of any reason to run this version over 2e but it
might be useful to someone.
Installing:
1. turn on USB debugging
2. plug into computer
3. run script and follow on screen prompts.
UPDATED 01/23/2011
fixed path error when space in user name
UPDATED 01/22/2011
compressed the rageagainstthecage resource to prevent anti-virus detection
new anti-virus report
http://virscan.org/report/8e83f338fd7b8631c6b0bc0679efbd29.html
the /system file system is full on the newer ROM's
use the attached update.zip to root then install clockwork
Nice
Sent from my SGH-T959 using XDA App
ummmm... what attached zip?
kuhan said:
ummmm... what attached zip?
Click to expand...
Click to collapse
forgot to upload it.
kuhan said:
ummmm... what attached zip?
Click to expand...
Click to collapse
The one attached to the message(?)
fearmonkey said:
The one attached to the message(?)
Click to expand...
Click to collapse
yeah, he attached it after that post lol
how do you use this?
ok i wil bite. how do you use/flash this it cw is not accesible?
rename to update.zip i assume...... i mean thats how u flash everythign thats zip file if u cant get into clockwork.....
you cant flash this you will have to put the files on the internal sdcard
then use root explorer or adb to move the files into place, recovery goes to
/system/bin and the keys to /efs, update.zip is the clockwork recovery and
stays on the sdcard.
when you boot into recovery and choose re-install packages clockwork will
be able to do its thing.
I do like the sig verification but it's a PITA and may disable it, this is a temp
fix until I can finish hacking on recovery there is very little clues as to where
the functions are so it may be a few days.
forgot to mention to you also have to remount /system rw
mount -o rw,remount /dev/block/stl9 /system
Be-ware. Doing so on the ODIN 2E version will break Recovery all together.
Fine to replace on the Stock 2.2 ..
Ps.
Another Awesome Job untermensch
Not to sound like a total noob, but what benefit does this have over the current 2e recovery?
option94 said:
Not to sound like a total noob, but what benefit does this have over the current 2e recovery?
Click to expand...
Click to collapse
I haven't tried just replacing 3e with 2e, I doubt there is any advantage to
3e, to us anyway. but it is always worth while to find ways around these
things.
EDIT:
just replacing 3e with 2e did not work cant find the update.zip
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
TJD319 said:
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
Click to expand...
Click to collapse
thanks...
just updated the first post with a new version.
whats new
Code:
dissables forced post install wipe, dissables signature checking, and reports
API version 2 for backwards compatability with clockwork mod recovery.
Thanks man i rreally appreciate this like i said before. Working perfect snd no issues. Loving being able to CWM again ha. Anyway thank you again sir keep it up!
TJD319 said:
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
Click to expand...
Click to collapse
Thanks untermensch for your work and thanks to the TJD319 for the clear step by step instructions.
Getting can't mount partition after I select a zip file to flash. I can get to cwr fine and it sees the sdcard (internal) fine since I can navigate and select the file I want. The error comes when I try flash. All the files in the zip are in the root of the sd internal, except for recovery and keys that are in the directory /system/bin and /efs respectively. Any advice?
untermensch said:
thanks...
just updated the first post with a new version.
whats new
Code:
dissables forced post install wipe, dissables signature checking, and reports
API version 2 for backwards compatability with clockwork mod recovery.
Click to expand...
Click to collapse
I personally want to say Thanks for Working on this... I Honestly like this version better than the 2e due to being able to wipe the SD-card now..
Thanks for everything.
eugene373 said:
I personally want to say Thanks for Working on this... I Honestly like this version better than the 2e due to being able to wipe the SD-card now..
Thanks for everything.
Click to expand...
Click to collapse
Thanks for the support Eugene....
updated the no sig check version again, too fix the issue that even though the key
is never used, recovery still looked for the existence of the file and would error out if not found.
untermensch said:
Thanks for the support Eugene....
updated the no sig check version again, too fix the issue that even though the key
is never used, recovery still looked for the existence of the file and would error out if not found.
Click to expand...
Click to collapse
Yo man i really appreciate your work. Froyos been great to me Stock 2.2 and this is perfect man. Working flawlessly for me and Im just happy to be able to nandroid.
hey guys right now im using darchstar's godspeed recovery.. but whats the most recommended recovery mode that everyone uses?
My personal favorite is Clockwork Mod Recovery. You can find the latest for our phone in the Andorid Development section, on the first page of the aospGBmod thread. Should be easy to find as it is right on top 99% of the time due to popularity.
DARCH All the way if your running GB then clockwork because I've read people have had problems with Darch's recovery with GB but if your running CM6 then stick with Darch
Root-Hack-Mod-Always™
laie1472 said:
DARCH All the way if your running GB then clockwork because I've read people have had problems with Darch's recovery with GB but if your running CM6 then stick with Darch
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
Anyone Have The Apk. Or Zip File For Darch's Recovery?
Sent from my HERO200 using XDA App
PMGRANDS said:
Anyone Have The Apk. Or Zip File For Darch's Recovery?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I got it off of darch's website but it's been down as far as I know for a little while now.. Luckily I backed it up on my dropbox when I first downloaded it
I attached it so it'll be on XDA for everyone
Download the Darchstar_ra.zip and extract it onto the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/darchdroid_ra.img
reboot
2 questions will this restore previous RA nandroids and also can this do the complete wipe like clockwork?
kyouko said:
I got it off of darch's website but it's been down as far as I know for a little while now.. Luckily I backed it up on my dropbox when I first downloaded it
I attached it so it'll be on XDA for everyone
Download the Darchstar_ra.zip and extract it onto the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/RA-Darchstar.img
reboot
Click to expand...
Click to collapse
sent from my twopointtwo themed hero
thoughtlesskyle said:
2 questions will this restore previous RA nandroids and also can this do the complete wipe like clockwork?
sent from my twopointtwo themed hero
Click to expand...
Click to collapse
I don't see why it would have problems restoring older nandroids, I've never had problems after updating.
And yes, you can wipe data/cache, cache, davlik-cache, battery stats, and rotation settings in the wipe menu.
I currently use ClockworkMod Recovery 2.5.0.1 for recovery mode.
Specs of my Sprint HTC Hero/APA6277 are...
Android version: AOSP
Baseband version 2.42.02.10.29,
Kernel version 2.6.29.6-aospMD [email protected] #1
Mode version: aospMOD-0.9.9.2
Build number: FRG83
I plan on flashing the AOSP GB Mod to my device as soon as a stable version of it becomes available.
kyouko said:
I don't see why it would have problems restoring older nandroids, I've never had problems after updating.
And yes, you can wipe data/cache, cache, davlik-cache, battery stats, and rotation settings in the wipe menu.
Click to expand...
Click to collapse
have you had any issues with wiping and flashing gingerbread because i didnt at first but lately it seems like its not a full wipe, then again im using a really old version of RA
kyouko said:
I got it off of darch's website but it's been down as far as I know for a little while now.. Luckily I backed it up on my dropbox when I first downloaded it
I attached it so it'll be on XDA for everyone
Download the Darchstar_ra.zip and extract it onto the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/RA-Darchstar.img
reboot
Click to expand...
Click to collapse
Thanx A lot Kyouko!!
I Downloaded It....
But I Wanted To Pick Your Brain A Bit, Before I Flashed It.... Lol!
As I'm Sure You Know,
*Rom Manager* Has The Option "Flash Alternate Recovery" Which Switches The Users Recovery From Clockwork, To Amon_Ra, Right?
So I Guess My Question To You Is, What's The Difference Between This Recovery & The Other Two?
Is There More Features??
Oh, One More Thing.... Sorry!!
I Have A **** Load Of Backups From *Rom Manager* Will The Still Be Compatible, Since I Made'em With Clockwork?
Sent from my HERO200 using XDA App
thoughtlesskyle said:
have you had any issues with wiping and flashing gingerbread because i didnt at first but lately it seems like its not a full wipe, then again im using a really old version of RA
Click to expand...
Click to collapse
That issue was fixed in the newer RA versions (which includes this one and godspeed)
There was a problem wiping with the older RA after the cache location got moved in newer rom versions or something along those lines
PMGRANDS said:
As I'm Sure You Know,
*Rom Manager* Has The Option "Flash Alternate Recovery" Which Switches The Users Recovery From Clockwork, To Amon_Ra, Right?
So I Guess My Question To You Is, What's The Difference Between This Recovery & The Other Two?
Is There More Features??
Oh, One More Thing.... Sorry!!
I Have A **** Load Of Backups From *Rom Manager* Will The Still Be Compatible, Since I Made'em With Clockwork?
Click to expand...
Click to collapse
I'm not sure what the "flash alternate recovery" does because I only tried clockwork once and flashed over the recovery using terminal
As for features I took screens of each menu on the recovery
And I don't know what kind of backups rom manager does. If they're structured like nandroids it might work You may have to create a folder named "nandroid" and inside that folder create another and throw the backups in there. It'd be structured something like this:
/sdcard/nandroid/oldbackups/*folders go here*
And worst case scenario if they don't work but you really want all of them back you can just flash clockwork back to restore them.
kyouko said:
That issue was fixed in the newer RA versions (which includes this one and godspeed)
There was a problem wiping with the older RA after the cache location got moved in newer rom versions or something along those lines
I'm not sure what the "flash alternate recovery" does because I only tried clockwork once and flashed over the recovery using terminal
As for features I took screens of each menu on the recovery
And I don't know what kind of backups rom manager does. If they're structured like nandroids it might work You may have to create a folder named "nandroid" and inside that folder create another and throw the backups in there. It'd be structured something like this:
/sdcard/nandroid/oldbackups/*folders go here*
And worst case scenario if they don't work but you really want all of them back you can just flash clockwork back to restore them.
Click to expand...
Click to collapse
Darch's Recovery is an overclocked version of AmonRa with EXT4 Support. See here for more info
kyouko said:
That issue was fixed in the newer RA versions (which includes this one and godspeed)
There was a problem wiping with the older RA after the cache location got moved in newer rom versions or something along those lines
I'm not sure what the "flash alternate recovery" does because I only tried clockwork once and flashed over the recovery using terminal
As for features I took screens of each menu on the recovery
And I don't know what kind of backups rom manager does. If they're structured like nandroids it might work You may have to create a folder named "nandroid" and inside that folder create another and throw the backups in there. It'd be structured something like this:
/sdcard/nandroid/oldbackups/*folders go here*
And worst case scenario if they don't work but you really want all of them back you can just flash clockwork back to restore them.
Click to expand...
Click to collapse
Thanx For The Screenshots,
Now I'm Curious! And I Already Like The Way It Looks Better Than Clockwork! But To Be Honest Im A Little Nervous About Using ADB. Or Terminal Emulator!
Is It Easy/Hard?
I Heard You Can Brick Your Phone If You Enter A Command Wrong, Is That True?
Sent from my HERO200 using XDA App
PMGRANDS said:
Thanx For The Screenshots,
Now I'm Curious! And I Already Like The Way It Looks Better Than Clockwork! But To Be Honest Im A Little Nervous About Using ADB. Or Terminal Emulator!
Is It Easy/Hard?
I Heard You Can Brick Your Phone If You Enter A Command Wrong, Is That True?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
As long as you don't put "flash_image (BOOT or any other partition here)" you should be fine.
If you input it incorrectly it won't flash,
example: flashimage recovery /sdcard/darchdroid_ra.img
How to flash it via ADB:
Code:
adb shell
su
flash_image recovery /sdcard/darchdroid_ra.img
reboot
kyouko said:
As long as you don't put "flash_image (BOOT or any other partition here)" you should be fine.
If you input it incorrectly it won't flash,
example: flashimage recovery /sdcard/darchdroid_ra.img
How to flash it via ADB:
Code:
adb shell
su
flash_image recovery /sdcard/darchdroid_ra.img
reboot
Click to expand...
Click to collapse
followed the code lines for terminal emu and adb both times got Flash_img: not found even tried entering Darchstar_ra.img same error
thoughtlesskyle said:
followed the code lines for terminal emu and adb both times got Flash_img: not found even tried entering Darchstar_ra.img same error
Click to expand...
Click to collapse
Weird.. Do this for me, open up terminal emulator and type:
Code:
su
flash_image
you should get a return line saying:
Code:
usage: flash_image partition file.img
*see attached picture for example*
Make sure you're inputing it exactly the way I had it in the previous post - underscores and all. If the recovery.img name is different make sure whatever you type is exactly what the img is called.
If it's not in the /sdcard/ directory enter the correct one.
Example) /sdcard/downloads/oldrecovery.img
On my second attached picture you can see that the command worked, but since I already have that recovery flashed it aborts.
thoughtlesskyle said:
have you had any issues with wiping and flashing gingerbread because i didnt at first but lately it seems like its not a full wipe, then again im using a really old version of RA
Click to expand...
Click to collapse
I'd just use CW for Gingerbread, RA doesn't wipe boot or system I believe.
Does anyone know if you are able to Wipe Data/cache/dalvik from adb shell?
just making a script to automate the process.
anyone know the commands?
thanks
Hello
I've tried installing guestekrnL on WIUI. When installing guestekrnL, the only thing I've ticked extra that was other than defaults was:
"Activate init.d functionality and convert file system to EXT4?
- yes
select if init.d is not working yet or if you don't know"
Well, after reboot WIUI was screaming that my sd card is broken and format may help. It formatted it, but it still didn't work. So I've rebooted to recovery via option in power dialog in order to restore old firmware. However there's a problem now: CWM Touch says that it can't write logs to /cache. Mounting /cache, /data or /emmc from recovery doesn't work, only /system and /sdcard are mounting correctly. I've tried BackToExt3 with no luck. I've tried wiping it many times, with no luck. My phone only boots now to CWM. I can't flash stock via APX mode, because I have broken USB port in my phone. What can I do?
Does restoring a backup, flashing a zip file or wiping work?
Ok, I was searching for almost whole hour now and it seems it's a problem with partition table. Fixing can be done via zip, but I need some dumps. First one from "cat /proc/mounts" and second from "parted".
Here's the zip for nook color if someone wants to do that for me: http://forum.xda-developers.com/showthread.php?t=1759558
exinepl said:
Ok, I was searching for almost whole hour now and it seems it's a problem with partition table. Fixing can be done via zip, but I need some dumps. First one from "cat /proc/mounts" and second from "parted".
Here's the zip for nook color if someone wants to do that for me: http://forum.xda-developers.com/showthread.php?t=1759558
Click to expand...
Click to collapse
the Touch CWM might be the issue......most of the times it is found as the source of some unknown issues for some or intermittent issues.
I use the non-touch one always
Hope it helps
Well, how do I flash new recovery from CWM using zip then?
exinepl said:
Well, how do I flash new recovery from CWM using zip then?
Click to expand...
Click to collapse
check for the CWM thread by Rusty....you have the instructions and process in it.
THERE YOU GO>>>SEE HERE
Hope it helps
Unfortunately, it needs USB. I need to flash it via existing recovery.
Mounting problems occur on some zips using touch recovery . Change cwm to non touch 5.0.2.8. But hey, did you flash a stock kernel on wiui ? you need another kernel, like etana, symbiosis.....or just use the one shipped with rom