I've been running 2.5.1.2 for awhile. Let ROM Manager install 3.0.0.8 for me, and now I get the dreaded "doesn't wipe ****" bug. No matter how many times I wipe, it doesn't wipe. I'm going to go back to 2.5.1.2 for now, but I don't want to be one of those guys holding up progress. So, what's the current flavor recovery that everyone likes?
Incredible w/Amoled screen.
jaykresge said:
I've been running 2.5.1.2 for awhile. Let ROM Manager install 3.0.0.8 for me, and now I get the dreaded "doesn't wipe" bug. No matter how many times I wipe, it doesn't wipe. I'm going to go back to 2.5.1.2 for now, but I don't want to be one of those guys holding up progress. So, what's the current flavor recovery that everyone likes?
Incredible w/Amoled screen.
Click to expand...
Click to collapse
Ain't seen you around these parts in awhile. The thing about the recoveries is since most Roms are now edify (do to gb) we have to use 3.X recoveries.
Generally 3.0.0.7 for Amoled and 3.0.0.8 for SLCD.
wildstang83 said:
Ain't seen you around these parts in awhile. The thing about the recoveries is since most Roms are now edify (do to gb) we have to use 3.X recoveries.
Generally 3.0.0.7 for Amoled and 3.0.0.8 for SLCD.
Click to expand...
Click to collapse
What he said
If ive helped you, please hit the damn thanks button!
jaykresge said:
I've been running 2.5.1.2 for awhile. Let ROM Manager install 3.0.0.8 for me, and now I get the dreaded "doesn't wipe ****" bug. No matter how many times I wipe, it doesn't wipe. I'm going to go back to 2.5.1.2 for now, but I don't want to be one of those guys holding up progress. So, what's the current flavor recovery that everyone likes?
Incredible w/Amoled screen.
Click to expand...
Click to collapse
Download vr superwipe, flash that after you wipe EVERYTHING, you will have no issues. I actually flash it, wipe, flash again, then flash rom. This wipin 3 times is a croc.
If ive helped you, please hit the damn thanks button!
I'm trying 3.0.0.7 right now. I'll report back if I still have wiping issues.
3.0.0.7 on my AMOLED works perfectly, not sure why anyone would wipe or flash multiple times. If your recovery isn't wiping properly, I don't see how executing the same command would yield different results. Although it does sound like the 3.0.0.8 recovery is bugged on AMOLED devices, not sure about SLCD.
To Jay, how do you know that the recovery isn't wiping correctly? Checking /system, /data, and /cache partitions in ADB after wiping them in recovery?
I've found this link helpful in understanding how CWM recovery works and what happens in the wiping process.
http://cvpcs.org/blog/2011-06-05/time_to_wipe_data/cache
To summarize, there's a 37MB difference in available space between flashing a ROM with 2.5.1.2, and flashing the same ROM with 3.0.0.x (7 or 8, tried both). For example, the ROM that I normally use gives me 679MB/748MB in available space. Flashing it with 3.x give me 642MB.
Any idea what's going on? I'm back on 2.5.1.2, and I'm happy with it. It works as I expect it to.
EDIT: Just wanted to state that reverting to 2.5.1.2 alone doesn't fix the issue. Once that extra 37MB is taken up, it's permanent. The only solution is to RUU back to 2.2, run unrevoked, and start over. This restores the lost space.
wildstang83 said:
Ain't seen you around these parts in awhile. The thing about the recoveries is since most Roms are now edify (do to gb) we have to use 3.X recoveries.
Generally 3.0.0.7 for Amoled and 3.0.0.8 for SLCD.
Click to expand...
Click to collapse
the 2.x versions flash both amend and edify, 3.x flashes only edify. No need to update for that reason and actually a good reason to stay with 2.x versions for the ability to flash new and old roms that haven't been updated.
Amend is old (abandoned back with cupcake I believe) so koush eliminated the ability to flash amend scripts in 3.x so that it would force devs to get with the times and use edify. Edify is not new, has nothing to do with gingerbread.
I use amon ra recovery and have had no issues, flashes both amend and edify still.
i need a recovery for my dinc the one i installed is not working. i can't do nothing when i enter into ClockworkMod Recovery v3.0.0.8
if i press reboot system now = nothing happen
apply update from sdcard = nothing happen
wipe data/factory reset = nothing happen
wipe cache partition = nothing happen
install zip from sdcard = nothing happen
backup and restore = nothing happen
mounts and storage = nothing happen
advanced = nothing happen
power off = same result nothing happen
can someone please tells me what's going on?
i need help with this now my phone do not work at all.
i use unrevoked 3 flash and root tool "everything was perfect" i installed room manager premium with recovery v3.0.0.8 with alt recovery 2.5.1.2 everything was good. after running the cyanogenmod 7 my phone now stay with the logo of the cyanogenmod 7 and do not enter to the main screen.. PLEASE HELP ME
airjordanmmix said:
i need a recovery for my dinc the one i installed is not working. i can't do nothing when i enter into ClockworkMod Recovery v3.0.0.8
if i press reboot system now = nothing happen
apply update from sdcard = nothing happen
wipe data/factory reset = nothing happen
wipe cache partition = nothing happen
install zip from sdcard = nothing happen
backup and restore = nothing happen
mounts and storage = nothing happen
advanced = nothing happen
power off = same result nothing happen
can someone please tells me what's going on?
i need help with this now my phone do not work at all.
i use unrevoked 3 flash and root tool "everything was perfect" i installed room manager premium with recovery v3.0.0.8 with alt recovery 2.5.1.2 everything was good. after running the cyanogenmod 7 my phone now stay with the logo of the cyanogenmod 7 and do not enter to the main screen.. PLEASE HELP ME
Click to expand...
Click to collapse
Don't use the power button. Use the optical joystick. Common mistake.
Sent from my Droid Incredible running a random CM7 nightly.
EDIT: Just wanted to state that reverting to 2.5.1.2 alone doesn't fix the issue. Once that extra 37MB is taken up, it's permanent. The only solution is to RUU back to 2.2, run unrevoked, and start over. This restores the lost space.
Click to expand...
Click to collapse
Jay, you're saying that once room has been taken up in data partition, it's for good? Even if you wipe? You have to RUU to get it back?
I'm only asking because I keep getting hit with a low space notification on every sense rom I've tried lately and am wondering if this is the cause?
Sent from my HTC Incredible
TheWhiteBandito said:
Jay, you're saying that once room has been taken up in data partition, it's for good? Even if you wipe? You have to RUU to get it back?
I'm only asking because I keep getting hit with a low space notification on every sense rom I've tried lately and am wondering if this is the cause?
Sent from my HTC Incredible
Click to expand...
Click to collapse
I apologize, I should elaborate. What I displayed was the only solution that worked for me. There may be other methods (like that program another poster mentioned). But no, I'm not going to flash something along with every recovery to make sure that everything was wiped properly.
If you want to test, click through to my links below. Install Liberation Enhanced 1.1 (nandroid first). Once you install, skip every part of the Sense startup process, and go straight to settings, then SD and Storage. See how much available phone storage you have left. You should have 677MB. If you have significantly less than that, then you've also been affected by this. If you fall into this, then do the following;
-Run the RUU back to 2.2
-Run unrevoked (this will install 2.5.1.2 as your recovery)
-Re-flash the same ROM, you should now be at 677MB. Problem solved until the next time you use CWM Recovery 3.x.
I don't know where the extra storage is going, but I don't think that it's in the /data/data partition, meaning that it wouldn't affect your low on space notification.
Just out of curiosity, did you format /system when you tried the 3.x recovery? I don't believe that /system is covered by the wipe data/factory reset.
It shouldn't be any different than the 2.x recovery though, going through the same steps should yield the same results. I would consider contacting Koush to see if there's an explanation for what's happening.
k_nivesout said:
Just out of curiosity, did you format /system when you tried the 3.x recovery? I don't believe that /system is covered by the wipe data/factory reset.
It shouldn't be any different than the 2.x recovery though, going through the same steps should yield the same results. I would consider contacting Koush to see if there's an explanation for what's happening.
Click to expand...
Click to collapse
I'll certainly bother him. I tried going into advance and formatting; system, boot, data, and cache. I also tried the "wipe 3 times" myth on all of them. Bottom line is, with 2.5.1.2, if you wipe data, it does so correctly without any further steps. That's the way it should be, so that's the recovery that I will use.
That's definitely odd. Have you figured out where the 37mb of files are that the 3.x recovery doesn't wipe?
k_nivesout said:
That's definitely odd. Have you figured out where the 37mb of files are that the 3.x recovery doesn't wipe?
Click to expand...
Click to collapse
Not yet. I'm curious, but lack the time. I might investigate it further at a later time.
jaykresge said:
I apologize, I should elaborate. What I displayed was the only solution that worked for me. There may be other methods (like that program another poster mentioned). But no, I'm not going to flash something along with every recovery to make sure that everything was wiped properly.
If you want to test, click through to my links below. Install Liberation Enhanced 1.1 (nandroid first). Once you install, skip every part of the Sense startup process, and go straight to settings, then SD and Storage. See how much available phone storage you have left. You should have 677MB. If you have significantly less than that, then you've also been affected by this. If you fall into this, then do the following;
-Run the RUU back to 2.2
-Run unrevoked (this will install 2.5.1.2 as your recovery)
-Re-flash the same ROM, you should now be at 677MB. Problem solved until the next time you use CWM Recovery 3.x.
I don't know where the extra storage is going, but I don't think that it's in the /data/data partition, meaning that it wouldn't affect your low on space notification.
Click to expand...
Click to collapse
Ah I see what you're saying now. I will give that a try when I get the chance! I always keep Liberation on my SD card anyway!
k_nivesout said:
Just out of curiosity, did you format /system when you tried the 3.x recovery? I don't believe that /system is covered by the wipe data/factory reset.
It shouldn't be any different than the 2.x recovery though, going through the same steps should yield the same results. I would consider contacting Koush to see if there's an explanation for what's happening.
Click to expand...
Click to collapse
/system is NOT covered by the wipe data/factory reset option. My only thought behind this is that it's meant to just remove your user data, but keep your ROM aka a factory reset. If you were to factory reset a normal, unrooted inc, you would be left with the stock OTA rom without any user data. I believe that is the same mindset.
I always go to mounts and storage and wipe /system before flashing a new rom
As I understand, formatting /system should be in the updater-script for whatever rom you're flashing, but isn't necessarily always included. Formatting /system should probably be mentioned in the OPs for most roms.
And Jay, I'd be interested if you find out what isn't being wiped on the 3.x recoveries that is on the 2.x.
Related
Hi all
I have a HTC Desire which I initially rooted using the UnRevoked method. Using Clockworkmod Recovery, I began installing ROMs to my hearts content. Everything was perfect, and I was changing ROMs every few days, testing them out, trying to find the perfect ROM for me, restoring back to the one which was currently my favourite
Later, being a newbie, I discovered that when I try to use ADB to push apps to the phone, I realized my NAND was read only, and my phone was S-ON. I then used AlphaRev HBOOT to S-OFF my phone, and this is where things have taken a turn...
It seems that since I have done the S-OFF, I can install ROMs fine, I can back them up and restore them too, all with no problems or errors during the process. But now it seems that whenever I restore to any backup, when the phone boots up, it gets to the point where the screenlock is visible, and then once I unlock the screen, I seem to get loads of force closes for various apps popping up on the screen and not letting me do anything! I can no longer rely on my Clockworkmod backups anymore
Extra information:
HTC Desire S-OFF via AlphaRev 1.8 HBOOT, CWM-AlphaRev Recovery 2.5.1.8Problem seems to occur with 2 ROMs I tested after S-OFF. Currently running InsertCoin1.8h DHD ROM port, and my last backup of this ROM when restored gave same problem as above. Previously running Oxygen 2.0 RC7, last backup also gave force closes when restored. With the Oxygen ROM, I managed to solve the problem by re-flashing the original ROM zip without wipe, but all my customizations and themes are lost. When I flash any ROM, I always wipe using the "Wipe user data and cache" option, then wipe the Dalvik cache, and then flash. I do the same thing when restoring to any backed up ROM too. My phone is rooted, I have SU permissions, I can push files to /system/app via ADB without any errors, so it is S-OFF. I do not get any problems using the ROMs, they are fast and very fluid, I can install themes and zips cooked in UOT kitchen, other kernels, patches, etc. I have formatted my SD card 3 times, and re-partitioned it each time using ROM manager initially, and later Clockworkmod Recovery 3.0.0.5 (temporarily installed this recovery to create 1GB EXT partition, presumably on EXT4?)
Sorry for the huge dump of information, its just to provide as much information as I can, so to not frustrate anyone kind enough to help me (assuming you are not already frustrated because I asked a complete newbie question with a simple answer!)
Any ideas what the problem can be? I thank anyone in advance and really appreciate any responses
Did you wipe data and cache?
Sent from my HTC Desire
I (and some other users) had the same problem with the 2.5.1.8 alhpa rev recovery..I solved using the 2.5.0.7 recovery
Did you wipe data and cache?
Sent from my HTC Desire
Click to expand...
Click to collapse
Yes, I always do, it is something I am weird about
I (and some other users) had the same problem with the 2.5.1.8 alhpa rev recovery..I solved using the 2.5.0.7 recovery
Click to expand...
Click to collapse
Initially I did not install the AlphaRev recovery, and was running 2.5.0.7. I think I still had the same problem, thats why I installed the AlphaRev. But honestly speaking, I cant remember properly, so I cant be sure. I will try other recoveries and post back.
Thanks for the suggestion!
First, this is not for people whom cannot boot into the recovery at all. If your recovery does not load, or you can't get past the "white screen", there are other threads and options for you (e.g. installing the recovery though fastboot or Unrevoked).
PROBLEM: You boot into the CWM3 recovery fine. You can install compatible zips fine. However, when trying to backup, the recovery locks up at some point during the backup process.
Solutions I tried: RUU to stock. Downgrading to 2.5.0.5 and back up to 3.0.0.5. Deleting the clockworkmod folder on the sdcard. reinstalling ROM Manager. wiping cache/dalvik before backing up. None of these things worked.
Solution that seems to have worked: swap out sdcards, doing battery pulls on the phone inbetween and booting back into recovery, until you find one that allows the backup to complete. Once a backup completes fully, you will be able to swap back to your original sdcard and CWM3 should work as intended.
Specifically here's what I did:
Step 0: Flash 3.0.0.5 through ROM Manager.
Step 0.5: Turn progress bar off in ROM manager settings. I do not believe this is important. But for completeness, I did do this.
Step 1: Boot into recovery
Step 2: run backup with Transcend 8gb class 6: No luck. Battery pull, back to recovery
Step 3: Sandisk 1.0gb class unknown: no luck, battery pull, back to recovery
Step 4: Sandisk 512MB class unknown: worked twice in a row!
Step 5: Back to 8gb class 6: backup works now. Still in testing, but I believe this (obscure, weird) solution works.
I just used ROM Manager to download CM7 #40 nightly, backup and install apps through CWM3 and it worked.
Let me know if this works for you.
EDIT: Well, its not perfect, because I cannot restore a backup because I get the MD5 mismatch error. At least there's progress.
EDIT2: There are deeper problems here. Please post your success or lack thereof.
I can't believe that simply getting a backup to work once fixes the problem. I just can't see the recovery caring that it finally got one right, so now it works from now on. Recovery doesn't know what it has done in the past.
Perhaps repeatedly inserting and removing the cards, just that act itself, somehow was the fix.
not impressed with cwm 3 at all, seems real buggy. Sometimes have problems with it not doing a clean wipe/factory wipe. When I install a rom, it has some wierd stuff going on. Stuff like loading a live wallpaper from the previous roms setting. I never use it to download roms anymore. I might switch over to ra amon recovery. Or maybe back to the 2. series
it seems @koush and @dougpiston had a twatt on the twitter about cwm3 borking on the dinc. you can read the full conversation over there, but the gist is that we should enable "erase recovery" option w/in rommanager settings, reflash recovery.
I guess the recoveries are best flashed clean, rather than over one another. ???
okay. the above fix has been confirmed to work by myself and one other user on the htc incredible cm7 nightly thead, AdhvanIt.
So you want to load cwm through rom manager after you enable "erase (previous) recovery" in settings and it will be puppies and rainbows from now on.
Sent from my dinc using XDA App
Regarding the erase recovery, I had tried it for the backup will not finish problem and the weird fix above is the only thing that worked, but will give it another try for my broken restore issue.
Wow I find odd that I have no problems what so ever with cwm 3
Sent from my Incredible using XDA App
tdiman said:
Regarding the erase recovery, I had tried it for the backup will not finish problem and the weird fix above is the only thing that worked, but will give it another try for my broken restore issue.
Click to expand...
Click to collapse
After going back to 2.5.1.2 with erase recovery enabled, and then back to 3.0.0.5 I'm back to square 1 with not being able to complete a full backup.
I'm going with 2.5.0.5 until either I get a new SD card or someone else comes up with a fix.
tdiman said:
After going back to 2.5.1.2 with erase recovery enabled, and then back to 3.0.0.5 I'm back to square 1 with not being able to complete a full backup.
I'm going with 2.5.0.5 until either I get a new SD card or someone else comes up with a fix.
Click to expand...
Click to collapse
bummer. keep us posted. I too have 16gb sandisk. had many issues with cwm3 but they seem to have stablized with the erase recovery fix... fricking variables...
Sent from my dinc using XDA App
burnmatoaka said:
bummer. keep us posted. I too have 16gb sandisk. had many issues with cwm3 but they seem to have stablized with the erase recovery fix... fricking variables...
Click to expand...
Click to collapse
There were some changes pushed to CM7 a couple of nights ago for the recovery management, as well as the new ROM Manager update, that got me to try again. This time I deleted all partitions on the sdcard and repartitioned it with a large FAT32 partition and a small ext4 partition after it. I deleted my unused swap partition. ROM Manager recognizes both partitions as it is able to format them, so thats good.
I used ROM manager and installed Amon-Ra, then installed 3.0.0.5. Same hang-on-backup problem as before. Back to 2.5.0.5
erase recovery has been on the whole time...
you have a gremlin in there! I assume you've tried full-wipe and all. Maybe install cwm3 from HBOOT with a fresh download and/or md5verified copy of the recovery?
hit up @clockworkmod on the twitter. I know he can be kind of a flake, but he does invite feedback when he drops an update... it was how we found out about the erase recovery thing.
you aren't having any other weirdness with other ROMs, are you? worst, worst case, your hardware is "circling the drain." sucks, but you know plenty of used dincs be hitting the market when Thunderbolt finally drops. See what Koush says though--be persistent, and it wouldn't hurt if you happen to have a RM premium license
good luck, and again, keep us posted.
sent from my dinc using xda app,
burnmatoaka said:
you have a gremlin in there! I assume you've tried full-wipe and all. Maybe install cwm3 from HBOOT with a fresh download and/or md5verified copy of the recovery?
Click to expand...
Click to collapse
In the spirit of the title of this thread, I do believe I have an actual working fix over in the DEV forum. I recompiled CWM3 from source. Please see
http://forum.xda-developers.com/showthread.php?t=970032
and let me know your experiences over there, those of you that may or may not still be following this thread
@clockworkmod just dropped a new version of the inc recovery that supposed to fix "wiping /datadata issue from ROM Manager" Has this been our problem?
sent from my dinc using xda app,
I do not believe that was my original issue as the problems I had were independent of ROM manager, but 3007 fixes whatever my issue was as well as the wipe issue, which is great.
3007 also has the option to power off, thanks Koush!
Has anyone tried the 3.0.0.8? Just flashed and hoping it works better.
phaze one said:
Has anyone tried the 3.0.0.8? Just flashed and hoping it works better.
Click to expand...
Click to collapse
Fast scrolling is back.
zero issues with 3.0.0.8 for me. SLCD.
Sent from my ADR6300 using XDA Premium App
unable to get 3.0.0.7 to boot, though. no big thing, just looking for that mythical multi-touch fix. <sigh>
(and ZOMG my post#10 means i can talk in the grown-folkxx forums. sorry for the fluff)
Sent from my ADR6300 using XDA Premium App
I'm pretty new to rooting and flashing, but did flash several ROMs over the period of a few months. Recently, I wanted to clean my phone up so I thought I'd start from scratch. I unrooted which which went well and then rooted again last night via Unrevoked (3.70). I used bootloader for AmonRa's 2.3 recovery which went well, made a nand, and flashed Miks 4.5 ROM. Since then, when booting into recovery, I see 'E: Can't open CACHE:recovery/log' and it worries me as I have no clue what it means. Also, and I'm unsure if it's even related, but my Market worn't download anything anymore.
Any thoughts/solutions?
Thanks in advance!
cdadams1223 said:
I'm pretty new to rooting and flashing, but did flash several ROMs over the period of a few months. Recently, I wanted to clean my phone up so I thought I'd start from scratch. I unrooted which which went well and then rooted again last night via Unrevoked (3.70). I used bootloader for AmonRa's 2.3 recovery which went well, made a nand, and flashed Miks 4.5 ROM. Since then, when booting into recovery, I see 'E: Can't open CACHE:recovery/log' and it worries me as I have no clue what it means. Also, and I'm unsure if it's even related, but my Market worn't download anything anymore.
Any thoughts/solutions?
Thanks in advance!
Click to expand...
Click to collapse
try booting into recovery and wiping your cache
I thought I tried that already per a suggestion I read somewhere, but it didn't work. Lemme try it again and I'll post back in a few.
Thanks!
if it doesnt work try downloading terminal emulator from the market (free) and run this command:
su
cd /cache
rm -rf *
do you have rom manager, believe rom manager lets you flash amon ra recovery, its an option at the bottom of the menu, if it lets you flash and you are able to go into recovery i would wipe cache, dalvik and data and the reflash the rom(you should probably download it again and put it in the root of your sd card, i say re-download just to make sure you didn't get a corrupted download the first time)
cdadams1223 said:
... Recently, I wanted to clean my phone up so I thought I'd start from scratch....
Click to expand...
Click to collapse
Next time just wipe EVERYTHING twice and flash THIS, then you will be stock and clean BUT still rooted
@blakeboys - Well, your suggestion worked. Apparently I tried wiping my Dalvik-cache and not just cache. This time I did both and voila...it worked. I'm now able to download apps from the market again. I haven't returned to recovery to see if I get that same error so I'm not sure about that.
@emcp422 - I do have ROM Manager, but I do not use it. It is not set-up yet to flash the latest AmonRA which is 2.3. I never had a problem of accessing my recovery. If it happens again, I will do as you suggested and re-download it and install it again.
Thanks for yall's help!
no problem, glad we could help ya
blakeboys said:
Next time just wipe EVERYTHING twice and flash THIS, then you will be stock and clean BUT still rooted
Click to expand...
Click to collapse
Will do...thanks man!
cdadams1223 said:
@blakeboys - Well, your suggestion worked. Apparently I tried wiping my Dalvik-cache and not just cache. This time I did both and voila...it worked. I'm now able to download apps from the market again. I haven't returned to recovery to see if I get that same error so I'm not sure about that.
@emcp422 - I do have ROM Manager, but I do not use it. It is not set-up yet to flash the latest AmonRA which is 2.3. I never had a problem of accessing my recovery. If it happens again, I will do as you suggested and re-download it and install it again.
Thanks for yall's help!
Click to expand...
Click to collapse
Actually ROM manager does flash Amon Ra 2.3 for some reason the app shows 2.2.2 or whatever but if you boot into recovery its actually 2.3
RileyGrant said:
Actually ROM manager does flash Amon Ra 2.3 for some reason the app shows 2.2.2 or whatever but if you boot into recovery its actually 2.3
Click to expand...
Click to collapse
That's good to know! Thanks!
I was running CM9 and then went to MIUI and then back to CM9. Ever since I have not been able to do a proper update to the CM9. Got fed up with it and tried to roll it back to one of the Nandroid backups. It got stuck for hours. Pulled the battery. Tried to go through the process of installing CM9 again fresh. Used Darkside SuperWipe and it kept freezing on "Wiping Cache" and the same thing when I use CWM (v6.0.1.4)! I have attached two screen shots. It reads:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
Then when I ask it to format the cache it get frozen.
How can I fix the cache? I cannot boot into CM9 or anything for that matter. I just get the awesome little Cyan Dude and the warp background flying at me continually until I pull the battery. Can anyone help? Is there any way to get ADB to work with out turning on USB Debugging on the phone?
Same issue with Clockworkmod Recovery
Sorry to say I can't answer your question, but actually just downloaded cm9 and was trying to factory reset in order to prepare to flash it and ran into the same cache issue. I tried everything and still couldn't get around it, almost bricked my phone, got stuck in a loop. Hadn't even done anything yet, except download the cm9 Rom. Also freezes when trying to wipe cache and when trying to restore a backup when it gets to the cache. I'll be keeping an eye on your post, and Ill let you know if I figure anything out as well.
I hate to say it but... use TWRP. It looks and works better. Trust me.
Sent from my SGH-T989 using xda app-developers app
whatiznt said:
I hate to say it but... use TWRP. It looks and works better. Trust me.
Click to expand...
Click to collapse
I trust you but on the Team Win Recovery Project's changelog you can see that it has not been updated in almost a year! CWM is updated much more frequently and also I enjoy having the touch version! Very convenient.
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
jalight27 said:
Just downloaded cm9 and was trying to factory reset in order to prepare to flash it and ran into the same cache issue. I tried everything and still couldn't get around it, almost bricked my phone, got stuck in a loop. Hadn't even done anything yet, except download the cm9 Rom. Also freezes when trying to wipe cache and when trying to restore a backup when it gets to the cache. I'll be keeping an eye on your post, and Ill let you know if I figure anything out as well.
Click to expand...
Click to collapse
Thank you my friend. What you describe is exactly what happened to me. Tell me, what version of CWM Recovery do you have? Were you coming from stock? Which CM9 was it? Nightly, stable?
mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
Please pardon my ignorance as I am relatively new at all this. How do you downgrade CWM? I am unable to boot the phone into the ROM. Can it be done through Recovery? ODIN?
I've looked around but I can't find a download for 5.0.2.7-- at least not one that's labeled specifically for our phone. It can be done in many different ways, flashing via recovery or Odin would definitely work, just need to find the right file.
Same version as you've got. Was actually coming from Jedi Mind Trick v8 and was going with the nighty. I loaded a backup of my stock ICS, which of course froze during the restore once it got to the cache, but I let it sit for like 15 min or so and then reset it and surprisingly it loaded up fine despite the fact that I had to reset it during the restore. I'm trying to follow up with the advice these two guys gave me on my post (really the same thing they've told you). With my extremely limited knowledge in this field I'm still working it all out and trying to make sure I ask the stupid questions so as not to mess anything up, well at least not too bad, lol.
mintharis said:
I've looked around but I can't find a download for 5.0.2.7-- at least not one that's labeled specifically for our phone. It can be done in many different ways, flashing via recovery or Odin would definitely work, just need to find the right file.
Click to expand...
Click to collapse
Go into rom manager and scroll down to previous versions
VoiD_Dweller said:
Go into rom manager and scroll down to previous versions
Click to expand...
Click to collapse
I don't have ROM manager installed. Does it provide a tar that can be flashed via Odin?
Newer Recovery
Clockworkmod 6 doesn't need the Darkside tools anymore. I had a similar problem but it was causing my phone to lock up. Just try using the regular cache wipe and dalvik cache wipe and see if that works for you.
mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
I can confirm this, I have a samsung galaxy S II and I was having HUGE problems with the newer version of CWM. Cache would not clear at all even with darksides super wipe. My CM9 was stuck in a boot loop because I had forgotten to clear my cache and factory reset, and I was not able to do this at all, so i thought i was screwed.
However what i did was flash an older version of CWM (5.0.2.7) through odin, and BAM I was able to clear all my data with no problem and reflash CM9. Works perfectly now.
Pugnap00 said:
I can confirm this, I have a samsung galaxy S II and I was having HUGE problems with the newer version of CWM. Cache would not clear at all even with darksides super wipe. My CM9 was stuck in a boot loop because I had forgotten to clear my cache and factory reset, and I was not able to do this at all, so i thought i was screwed.
However what i did was flash an older version of CWM (5.0.2.7) through odin, and BAM I was able to clear all my data with no problem and reflash CM9. Works perfectly now.
Click to expand...
Click to collapse
Can you please provide a link for the 5.0.2.7 tar you flashed?
mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
CWM v6.0.1.4 has pretty much made my phone useless. When in Recovery I can't even scroll down or up. I even tried restarting my phone to downgrade but I have no response from my MENU, HOME, BACK or SEARCH button.
WORD OF ADVICE. PLEASE STAY AWAY FROM CWM v6.0.1.4.
EdwardLThompson said:
I was running CM9 and then went to MIUI and then back to CM9. Ever since I have not been able to do a proper update to the CM9. Got fed up with it and tried to roll it back to one of the Nandroid backups. It got stuck for hours. Pulled the battery. Tried to go through the process of installing CM9 again fresh. Used Darkside SuperWipe and it kept freezing on "Wiping Cache" and the same thing when I use CWM (v6.0.1.4)! I have attached two screen shots. It reads:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
Then when I ask it to format the cache it get frozen.
How can I fix the cache? I cannot boot into CM9 or anything for that matter. I just get the awesome little Cyan Dude and the warp background flying at me continually until I pull the battery. Can anyone help? Is there any way to get ADB to work with out turning on USB Debugging on the phone?
Click to expand...
Click to collapse
Simple Solution is that the Cache in your device is large, it has to be cleaned, For this use Darkside cache wipe. It Solves the problem.
suffuciently hungeom
mintharis said:
Can you please provide a link for the 5.0.2.7 tar you flashed?
Click to expand...
Click to collapse
Here you go,
Look at step 6, it will have links to the tar based on your carrier. Its actually 5.0.2.6, works just the same though.
http://theunlockr.com/2011/12/01/how-to-root-the-samsung-galaxy-s-ii-all-versions/
I hope this helps you!
That happened to me as well when I was going to update to CM10. The faq for CM10 says you need to update to a Touch version of CWM which ROM Manager really wanted to install the Touch version. CWM shows it's version 6 and the menus were different but when I was finally able to get a ROM to boot in Safe Mode it reported CWM as being version 5.x. I could not mount or dismount the Cache in CWM. ODIN brought it back to stock but I messed around with the partition checkbox and hard bricked it. Otherwise it looked as tho things would have been ok after using ODIN to start over.
Darkside's wipe wouldn't work (either version) in this case.
screw cwm im going to twrp
ok same thing happened to me..but there are files i need in the phone and i dont think i want to use cwm after this...so can i use odin to flash it to twrp and recover my files through the twrp usb mount?
(lol nvm, i flashed a older version of cwm through odin and then recovered my files then got twrp)
mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
Like I said in my earlier post had your exact problem and did exactly what was recommend here, and it worked beautifully. Solved all my problems, no residual effects to speak of. Now I can flash my roms in peace.
Ok, so I've been flashing Roms since I first had the G1 but my step sons Galaxy S II is giving me fits as of late.
I've been working on it for over 2 days now and can not figure the problem even after reading through all the how to's and individual rom threads. I initialy rooted his phone back in April/May and had a early ICS phandroid rom on it. However I wanted to move him to JB. I've done the customary wipe data/cache but no matter what JB rom I flash it goes into what I believe is a bootloop. I've read several places it been said to let sit after flashing for 10 minutes so I let sit for 20 and it was still on boot (but no obvious point where you can tell it's looping).
When I went to restore his backup that would no longer boot at all, just a blank screen. So long story short I restored everything to stock then updated to ICS through keis. and tried the process again thinking it might need updated firmware/radio. Same thing happened and I had to restore stock and update through keis again. I am now at a complete loss as I update my phone (One S) and wifes (GSIII) atleast once a week on nightlies.
The one thing that I thought was odd is both on the original 2.3.6 and now 4.0.4 when I go into settings at search for update i get a message saying "no firmware". Not sure if that means anything but it didn't sound right to me.
Any help or suggestions would be overwhelmingly appreciated.
You will get different methods on here but for starters what recovery are you running. Thats problem 1 I guarantee for your bootloop. I use TWRP 2.3 which can be found by downloading goo.im and flashing it from the menu screen. You can also go to the forum here in development for the zip file.
When using TWRP or any touch recovery do not use the wipe scripts. Lets start there.... Since the method to flashing is basically the same all over its just the wiping procedure with the wrong recovery can be tricky
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
jhenson496 said:
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
Click to expand...
Click to collapse
I personally prefer that recovery and I'm running a cm 10 on my phone with no issues at never had anything. Yes it's rather simple to put on an even if you want to try the CWM touch recovery by all means go ahead
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
jhenson496 said:
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
Click to expand...
Click to collapse
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
Click to expand...
Click to collapse
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
abesgs2 said:
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
Click to expand...
Click to collapse
My friend I linked the zips in the post right above yours
playya said:
CHANGELOG for 2.3.0.0:
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
Click to expand...
Click to collapse
Just saw that last part by Playa, sorry didnt mean to kang you haha... but hes got it down ^^^