Related
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
So my phone now will only reboot up to the HTC Incredible white screen. I'm not even sure what the issue is, all i did last before it got stuck was erase data on an old sd card i had in the phone. Then I just did a reboot and it froze on the white screen.
I'm running GB evervolv 2.3.2 with 2.6.37.4 incredikernel.
I can get into HBOOT but when i click on recovery it takes me into fastboot everytime.
What can i do to fix this????
Sorry please move this thread to the Q&A section, i thought that's where I was posting it, my bad.
Go to the Clockwork Recovery thread and download the update for a different version and try getting that to flash via bootloader. That way you can at least get into recovery if you need to flash new. Just to clear it up, did you use your phone to delete stuff off the old card, by using Astro or ES file explorer? I know ES file explorer has root access so is there a chance you could've deleted a system file on accident? All it takes is a click of the SD card icon and you're in root instead of SDcard. Also this is probably a thread more for the Q&A subforum, just an fyi
i deleted an old sd card that i don't even use for my phone, i was just putting it in there to clear out whatever was left on it. so i could use it new.
And it still bootloops even when you put your normal SD card back in?
yup, i dunno what it's deal is.
I remember an older version of cm7 on the nook color warned against formating sd cards because it accidentaly formats the boot partition, this may be a bug that exists in the rom your using.
at least you can get into hboot, you should be able to download ruu image and flash it in hboot. this would get you back to stock, then root and install clockwork, and then restore your latest nandroid.
Flash this recovery in hboot
http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
It should at least give you a working recovery.
i have to rename things as update.zip in order for hboot to flash them right??
facedown41 said:
i have to rename things as update.zip in order for hboot to flash them right??
Click to expand...
Click to collapse
NO leave it PB31IMG.ZIP.
hboot can only see that name. if you rename it hboot will not see it at all.
also make sure your card is formatted as FAT32
got it into recovery so i'm just wiping and restoring, thanks for the help!
ok now i'm getting a bootloop on the cm7 boot screen...i just went to flash that new instead of my nandroid because the nandroid was from an older rom.
Did you wipe everything? Davik, Cache, Data, etc?
wiped data and cache...didn't do davik because i've never had to in the past. but i'll give it a try.
would i need to update CMW from version 2.0+ to 3 in order for cm7 to work? because it's still bootlooping
THIS IS EXACTLY WHAT JUST HAPPENED TO ME!
i was on MIUI 1.3.25 (the newest GB release) and i was formatting an sd card and when i restarted my phone i got stuck at the splash screen! i have been able to boot back into cwm recovery but even when i wipe and flash, nothing works.
i booted into recovery and tried to restart from there - failed
i reflashed 3.18 (wiped cache/dalvik) - failed
i wiped all data and reflashed 3.18 - failed
wiped all, flashed 3.25, fixed permissions - stuck at splash screen again
restored an old MIUI (v1.1.15) - stuck at splash screen
pleaseee let me know if you figure this out
edit:
i ran the RUU and got stock to start working. i'm about to root and try flashing something
JWorth said:
THIS IS EXACTLY WHAT JUST HAPPENED TO ME!
i was on MIUI 1.3.25 (the newest GB release) and i was formatting an sd card and when i restarted my phone i got stuck at the splash screen! i have been able to boot back into cwm recovery but even when i wipe and flash, nothing works.
i booted into recovery and tried to restart from there - failed
i reflashed 3.18 (wiped cache/dalvik) - failed
i wiped all data and reflashed 3.18 - failed
wiped all, flashed 3.25, fixed permissions - stuck at splash screen again
restored an old MIUI (v1.1.15) - stuck at splash screen
pleaseee let me know if you figure this out
edit:
i ran the RUU and got stock to start working. i'm about to root and try flashing something
Click to expand...
Click to collapse
Are you getting errors when you wipe?like when you wipe data does it say error can't mount or anything like that.... I have a feeling you may have to flash an Ruu and then reroot
Sent from my Incredible using XDA App
no, no errors. but i flashed the RUU and rerooted and everything works just fine. I flashed MIUI again and it worked perfect
thanks!
I figured that's what you would have to do glad you are back running
Sent from my Incredible using XDA App
I always mount my sdcard in a linux and format/fix/repartion, or at least let Clockwork Recovery do it. I have never found a Sense, Vanilla, or AOSP ROM that handled SD partition operations very well, without at least a little tragedy.
Sent from my ADR6300 using XDA Premium App
rynosaur said:
I always mount my sdcard in a linux and format/fix/repartion, or at least let Clockwork Recovery do it. I have never found a Sense, Vanilla, or AOSP ROM that handled SD partition operations very well, without at least a little tragedy.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
This tends to be things go as far as ROMs partitioning my sd, always back it up externally and format/partition before transferring stuck back over to it while in phone.
I am having trouble flashing a new kernel and it is driving me crazy. I am running CM7 with the Tiamat 3.3.7 kernel and wanted to update to a new Tiamat version. I downloaded the zip and placed it on the SD card.
I booted into Recovery using RA and performed a Nandroid backup. Then wiped the cache and davlik. Then flashed the kernel. Screen said it was installed correctly.
What is the next step? I get back to the main screen on RA and I choose "reboot system now", correct? When I do this, it either 1) loops the htc evo screen or 2) takes me back to the bootloader menu.
I have tried the battery pull trick and re-flashed the kernel a few times now and nothing seems to fix the problem. Is there a simply step I am missing here?
nvmd, it finally kicked over and rebooted cleanly. thread can be deleted if need be. thanks.
Prior to receiving my GS2 from T-Mobile I did research on how to Root, Flash ROMs, you know, all the cool things Android phones can do, and I mean A LOT of research. When I finally did recieve my phone the first thing I did was root it, which worked flawlessly - at which point I thought "Hey, this isn't so hard I won't have any problems at all!" OH BOY WAS I WRONG.
Here's where everything went wrong: The first ROM I thought I'd install was AOKP Milestone and then I'd try CM10, so I put both .Zip files into my SD card. I backed up to Titanium Backup and to my External SD card through Clockwork mod then I installed AOKP Milestone and made it to the home screen with some force close messages. It was running, but didn't look very stable to me and the whole "Swagger" thing turned me off to it. I went back to Clockwork Mod and the website that I got CM10 from also told me to run DarkSide Wipe before installing the ROM so I did just that. Ran Darkside, installed CM10, then installed Gapps. I then rebooted my phone and CM10 started to load up, but after 10 minutes of just the splash screen I assumed it was stuck in a bootloop. I then restored the backup I made before installing Milestone, but I remember there being an error and it not being successful. It was at this point that Clockwork Mod started being buggy. Starting to panic, I tried a factory reset through CWM. It formatted data no problem, but it would hang at "formatting /cache" until I turned off the phone. So I panicked some more and formatted system, emmc, data. (Not a smart idea, I know.) but it would hang when I tried formatting the cache again. And its been stuck in a bootloop ever since.
I read somewhere that you could use Odin to revert your phone to make it completely stock by flashing a kernel. I thought my prayers were answered! I was finally going to just start over and forget this ever happened! No. My computer won't even recognize my phone is plugged into it. (Yes, I have all drivers up to date. Yes, I am using Samsung Micro USB, and Yes, I have Keis installed.) Since my computer won't recognize my Phone, Odin won't.
* I can access Clockwork mod, and Download mode, but my computer won't recognize my phone when plugged in.*
I know it's a lot to read but I have tried so many things I'm just so discouraged about this whole thing. I know I'm a noob so please explain your answers like I'm 5. I don't understand most Android modding slang.
Thank you.
What version of CWM are you using?
Sent from my SAMSUNG-SGH-T989 using xda premium
6Seven said:
What version of CWM are you using?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
v6.0.1.9 Touch
If you have an external sd card, load a rom on to it from your computer and then get your phone into recovery mode and choose to install from external sd card. See if that works. Also sometimes a cache wipe can take a while. Also don't panic and start doing things you know nothing about. I would recommend and ice based rom then figure how to get twrp recovery then move on to cm10. . If you can get past this, I can help you. Pm me
badaphooko01 said:
If you have an external sd card, load a rom on to it from your computer and then get your phone into recovery mode and choose to install from external sd card. See if that works. Also sometimes a cache wipe can take a while. Also don't panic and start doing things you know nothing about. I would recommend and ice based rom then figure how to get twrp recovery then move on to cm10. . If you can get past this, I can help you. Pm me
Click to expand...
Click to collapse
Ok, I will see if I can get an ICS ROM onto my Micro SD. If it works I will PM you. Thank you.
I'm still open to more suggestions!
EDIT: The funny thing is, when my phone is in CWM my computer recognizes it and I can mount USB storage, but won't recognize it while in download mode. Weird.
don't use superwipe with cwm 6+. it will break your recovery and cause a bootloop.
also it seems that a lot of people have problems with cwm 6.0.1.9 and it seems like it doesn't wipe properly so i would recommend latest twrp or sk8terwitskil's cwm. i think that's what happened with aokp and why you were having so much fcs.
merrygocow said:
don't use superwipe with cwm 6+. it will break your recovery and cause a bootloop.
also it seems that a lot of people have problems with cwm 6.0.1.9 and it seems like it doesn't wipe properly so i would recommend latest twrp or sk8terwitskil's cwm. i think that's what happened with aokp and why you were having so much fcs.
Click to expand...
Click to collapse
Duly noted. Thank you for the info, really helps.
also have you looked at this thread?
http://forum.xda-developers.com/showthread.php?t=1513359
have you tried removing your battery and see if that will help your computer recognize your phone? i don't know if it will work or not but try. :laugh:
merrygocow said:
also have you looked at this thread?
http://forum.xda-developers.com/showthread.php?t=1513359
have you tried removing your battery and see if that will help your computer recognize your phone? i don't know if it will work or not but try. :laugh:
Click to expand...
Click to collapse
Yes, that is what I was referring to here:
I read somewhere that you could use Odin to revert your phone to make it completely stock by flashing a kernel. I thought my prayers were answered! I was finally going to just start over and forget this ever happened! No. My computer won't even recognize my phone is plugged into it. (Yes, I have all drivers up to date. Yes, I am using Samsung Micro USB, and Yes, I have Keis installed.) Since my computer won't recognize my Phone, Odin won't.
Click to expand...
Click to collapse
Battery pull didn't work either. :/
UPDATE: I've tried installing 3 different ICS ROMs from the external SD via CWM but they all seem to freeze 3/4 through the install. After about 5 mins of being frozen the phone reboots and the bootloop just comes back. Once again I have nowhere to go. I'm lost.
If anyone has more suggestions, please share!
i don't know where i read it but i just remember now that someone said kies and odin are incompatible. so maybe that's why odin couldn't detect your phone? kies might have been running in the bg.
so i would uninstall kies and driver. restart comp. then download and install just the driver from samsung website. then put the phone into download mode and connect to pc. see if that will help.
if not, i don't know lol. usually i would suggest flashing to twrp but i don't know how well that's gonna go over a broken recovery.
I would suggest flashing TWRP recovery 2.3.3 and try and flash a ROM again after....CWM has gone downhill in my opinion.
Here is the TWRP thread http://forum.xda-developers.com/showthread.php?t=1768742
Or download GooManager app and install that way
And do not use any cache wipe scripts with this.
Sent from my SGH-T989 using xda premium
You need to have computer install odin driver while you're in download mode before odin works. Try this wipe cache, wipe dalvik, wipe data/factory reset, format system, format cache and format system. Then flash new rom in recovery.
Sent from my SGH-T989 using Tapatalk
RESOLVED!
Funny thing is, I just plugged in my phone to a computer running Windows 7 and Odin recognized it! I guess my XP at home doesn't like phones. From there I flashed a stock kernel and VIOLA! Phone is out of the box new! Now I'm very weary about installing a ROM again.. I don't want to go through that ever again. Maybe i'll do some more research before I molest the software's insides.
Thank you everyone for your contributions!
Try recovery from sk8erwitskil, it's the only one that seems to work w/ my Hercules. I had similar problems to what you were experiencing and it's the only recovery that worked for some reason. I am on a GNex now so take that for what it's worth. I'll pull out the Herc. tonight when I get home to update to the CM10 latest nightly, it's been a while.
Hello guys,
It seems I did something stupid and now I cant get into recovery.
I had CM10 alpha 6 with CWM 6.0.2.7. Just to experiment with the stock rom again, I flashed FAW version 3 with the CWM recovery. So I rebooted the phone and everything seemed to went fine.
Then I wanted to flash extra packages for theming etc. But phone can not go into recovery. With the button combination v up, home and power the samsung logo just flashes and phone goes off again. I could get into download mode. But it takes couple of tries.
I tried to flash CWM via adb and it seemed to to be flashed without any errors. But still could not get into recovery.
Do you guys have any suggestions as to what to do? Should I try to flash stock rom via odin and start from scratch? Or do you have a better approach? I dont want to get stuck on sam firmware as I love CM10 .
I am cursing my stupidity. Why do you even want to ecperiment with stock rom.
Any help is greatly appreciated.
Thanks in advance.
Edit 1 : OK I took the sdcard off and took the battery out waited 10 to 15 minuted. Tried again to boot into recovery without the sdcard. Voila it worked.
I do not know what did the trick. Was it trying without sd or waiting without battery, I dont know. But happily I am back to CM10. Pheewww...
Sent from my GT-I8150 using xda app-developers app
Edit 2: Ok it seems it was the SD card I had. Again I had the same issue and I could not get into recovery. Moment I take it out, I can get into recovery. For some weird reason the SD card I have causes this issue. I will check with another sdcard soon.
Fiuuh. congratulations bro ..
you add the solution too. it will be a great information for other people
My suggestion would be to delete and then recreate all partitions on the SD Card.
Sent from my GT-I8150 using xda app-developers app