Related
Some reason I tried flashing another rom but it won"t let me and keeps going back to the original rom. I had frankenstein and wanted to check out viper. I dled the viper rom and dropped it into my sd and wiped and did the usual through cwm but everytime i boot back up iot goes to frankenstein.. Any ideas? I even deleted the frank rom just to make sure but that shouldnt make a difference should it?
What version of clockwork? You will need version 3.
Sent from my SPH-D700 using XDA App
yeah that"s the one I got. It says Viper opened and completed but after reboot it reverts back to franken
oh crap you know what. I have v2.5.1. That's the one I got with that 1 click root process. Is there an updated clockwork for the epic?
same thing too
That happend to me to but from mystic mountain to frankenstein. What i ended up doing was odening to stock rerooting and then flashing. You don't even have to wipe because odining it technically wiped it lol.
seems like a lot of work just to change roms. What doesnt make sense is that randyshear from youtube that does a lot of the rom reviews and installs just changes them one after another with his epic. Is there a 3.0 cwm for epic?
There is a new clockwork version for the epic. I am on my phone so don't have the link but it is a post in the development section.
Sent from my SPH-D700 using XDA App
I just checked their is a link to cw 3 in the first post of viper rom.
Sent from my SPH-D700 using XDA App
Ive got a complete package on my ROM thread,it contains CWM3.0.0.5,and everything else you would need.
Thanks fellas!
Did anyone flash the new recovery version in rom manager?
Sent from my ADR6300 using XDA App
I did. Not sure about changes in the coding but the new UI is nice.
Sent from my ADR6300 using XDA App
I heard it is mainly for 2.3 ROMs and such, is that true? I'm on Magnolia which is 2.2, would I run into any issues?
weird.. i flashed the new recovery through rom manager then booted into recovery but still had 2.5 on there..
Flashed it this afternoon, using CM nightly #32. Using ROM manager to backup etc., would give me errors when it got to recovery. Some error about the sd card mounting I think. It would work fine booting to recovery, just not using ROM manager. Think the nightly update tonight might address the issue. Had to flash back to an earlier recovery to use ROM manager.
Could not install a new rom with it.
sent from my Incredible using Tapa Talk
I flashed slayers test kernel with it and it seemed to work fine. Have not tried to run a back up yet.
Sent from my ADR6300 using XDA App
Is there a zip to install this new recovery instead of using rom manager? I always remove rom manager from CM7.
what is the new UI and why cant i boot into it? im on cm7.
converge12 said:
what is the new UI and why cant i boot into it? im on cm7.
Click to expand...
Click to collapse
its orange now
You can get it from Koush's website
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
anyone have a changelog?
Drewsipher said:
anyone have a changelog?
Click to expand...
Click to collapse
It requires some sort of new update script, we use the donut update script so koush is pushing us towards the future with this recovery, it works with any kernel because of it being koush's update script. Some roms might work, ask your favorite developer if it is compatable
Sent from my Incredible using XDA App
Darnit! Flashed it and now I can't install any font packs anymore. I guess it has something to do with the update script. Going back to a previous version if I can figure out how.
Sent from my Incredible using XDA App
superchilpil said:
It requires some sort of new update script, we use the donut update script so koush is pushing us towards the future with this recovery, it works with any kernel because of it being koush's update script. Some roms might work, ask your favorite developer if it is compatable
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
well... my I'm running cm7 so I knew I'd be well done in his hands... Multi-touch not working?
anyone with an idea as to why i cant boot into it?
converge12 said:
anyone with an idea as to why i cant boot into it?
Click to expand...
Click to collapse
I can't either
Running CM 7 nightly #25. Flashed the 3.0.5 and I couldn't boot into Recovery. Just reverted to 2.5.1.2, guess we'll have to wait until something gets patched up in CM.
Worked for me. I like the look.
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS5.3.
oh man, i can no longer access recovery. dayum...
i guess i should post some details: updated from 2.7.1.? (2 or 3, whatever) to 3.0.0.5 via free version of rom manager. just happened to have my stock rom loaded at the time.
edit: thx everyone. downloading the zip and reinstalling got me back up and running. yay! thx! i am disappoined, though, that md5 operations still take 15-20 minutes. i was hoping that would be fixed in this release.
I have been trying to hook a buddy of mine up with a new rom for his Evo, basically make it exactly like mine with the newest Fresh Rom. I rooted his phone with Revolutionary and it all went just fine, the phone is now rooted with Superuser successfully installed. I put the Fresh zip on his SD card, wiped everything as you are supposed to, and then flashed the zip. It flashes fine and boots up, loads to the lockscreen and setup, but then reboots and does the whole process again, basically a bootloop. I have tried various roms and kernels, wiped over and over again, redownloaded the file, etc., but nothing seems to work. Am I missing something?! I never had this issue installing this rom on my phone. Any help would be appreciated!
try using a different recovery
Something other than RA? What do you suggest? CWM is crap isn't it?
Sent from my PC36100 using XDA App
Give newer versions on CWM its work just fine for me. I never had a problem.
Sloth
I am skeptical that a different recovery will fix the problem, but I will give it a try and report back. Is there anything else anyone can come up with?
I had a really weird issue where I couldn't flash any of the Gingerbread roms a while back, and had flashed goodness knows how many since I bought my evo on launch day and rooted it day one when it was available.
Trying different recovery versions might help, but if it doesn't, I'd suggest to unroot it and start all over. Find a post in the dev section on unrooting, go back to the stock sprint rom, and start over.
I did that, and was then able to flash all gingerbread roms and get them to not bootloop.
I'm not the only one that was having the problem, but NO devs could/would help figure it out. Not even flipz. Give it a shot.
Thanks for the info, I will try to Recovery thing first and then do a full wipe out and start over from a stock rom. The weird thing about it is that this is the first time this phone has been rooted and the first attempt at flashing roms.
Just curious, how many times does it reboot?? Over and over and over, or are you pulling the battery after the first or send time?
Over and over
Sent from my PC36100 using XDA App
Try recovery and fast boot from there.
Sloth
I changed recoveries to clock work, and it did not make a difference. I continued to get the same boot loop as before with RA. I just wiped out the entire system, and went into the boot loader to unroot back to stock. I will report back my results once I am done
Sent from my PC36100 using XDA App
Either change you clockworkmod or try something else. Dam man that sucks.
Sent from my PC36100 using XDA App
SLB9884 said:
Either change you clockworkmod or try something else. Dam man that sucks.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Changing up the recovery did nothing to fix my problem. I unrooted his phone, regained s-on, flashed a stock rom and am starting over. I will report back my results.
Well damnit anyway, starting all over from scratch did nothing as well. Still get the same damn bootloop. WTF!?!? Anyone else have any other ideas?
I've read every post and I can't think of anything that would help. You think it's a software issue, like inside the phone itself might be bad?
Sent from my PC36100 using XDA App
Is this something that could be discovered on a logcat? I have never done one or know how they work, but would anyone be willing to diagnose the problem if I am able to get a logcat?
Damn that sucks. What your status. Did you fix the bootloop?
Sent from my PC36100 using XDA App
Still no fix discovered, any help on this would be greatly appreciated
Sent from my PC36100 using XDA App
What's interesting, is that this is the exact same boot loop problem I was having on my Evo when trying to flash any sense 3.0 rom.
Sent from my PC36100 using XDA App
Have you tried using / flashing any of the zips that are prepackaged " wipes " ?
Have you tried using TWRP recovery ?
I never had any problems while using RA but had numerous failed flashes with Clockwork.
TWRP has been stellar so far ... no failed flashes yet.
Well, I tried Cyanogen, AOPK and now I tried PARANOID 2.0.
None of them works, GAPPS works, but I get the Status 7 error while installing a ROM, i'm using the SGH-T999V and none of them works.
How are you trying to install them?
Sent from my SGH-T999 using xda premium
You are rooted and trying to install with cwm or twrp recovery, right.
I ask because that error reminds me of stock recovery for some reason...
Sent from my SGH-T999 using xda app-developers app
Hey make sure you've rooted your phone first. I'm on cm10 with leankernel and everything works just great. Good luck!
Sent from my SGH-T999v using xda app-developers app
Sounds like stock recovery to me bud..
Sent from my T999 GS3 @ 2GHZ
d2tmo wrong device?
Status 7 errors can occur in ClockworkMod for everyone saying he's using a stock recovery.
Make sure your rooted and you should be good
Hey SGH-T999V,
I think we'd all love to help, but we need some more information. Can you tell us step by step exactly what you are doing? Once we have that, I think we will be able to help you past this.
I am fully rooted with clockworld recovery 5.0.4 or something, installing zip from sdcard then Status error 7 and yeah...
From what I've gathered, status 7 errors usually occur when the ROM is incompatible with the device e.g when flashing a CDMA rom on a GSM phone. My first advice would therefore be to confirm that the zip file is for the correct GS3 variant. You mentioned aokp and CM. Both these ROMS refer to the T999 as "d2tmo" and the zip files usually contain this in the name (e.g cm-9-20120909-NIGHTLY-d2tmo.zip). I would therefore check this first before anything else.
Assuming that's not the issue, some suggestions would be:
1. This is a longshot, but try toggling signature verification and see what happens. I doubt this is the issue but I have had update zips fail because this was accidentally toggled
2. Try updating CWM: http://forum.xda-developers.com/showthread.php?t=1766552
3. Try changing the recovery to TWRP and see if its the recovery. The easiest way I've found is to use the GooManager app. Install from the play store. Run the app. Hit the menu key and select Install OpenRecoveryScript. Reboot into the TWRP recovery and try flashing from there.
4. Try rerooting the device from scratch
I got this error when I rooted using the Sprint method. I had to reflash cwm using Rom manager before I could install Cyanogen
Sent from my SGH-T999 using xda premium
I had the same problem. I updated cwm and it fixes it. Your version is old....
Sent from my SGH-T999 using Tapatalk 2
Just updated CWM to 6.0.1.2 and tried to flash with TWRP... same Status 7 error with every single ****ing ROMs i'm trying to install.
Wiped everything many times before installing zip, nothing works... i'm giving up and downloading stock ROM until Samsung releases official JB 4.1.
You might have to go back to stock and root it again
Sent from my SGH-T999V using XDA Premium HD app
could try installing the roms with Odin
Could try downloading the roms using Rom manager pro and having it install them
You just got to get one to work and you'll be golden
Is it a setting problem in cwm?
Like toggling allow installation of unsigned packages
Sent from my SGH-T999 using xda premium
Just update cwm to a newer version. I promise that'll fix it.
Sent from my SGH-T999 using xda premium
Or pay someone to do it. Look for rooting services on craigslist
Sent from my SGH-T999 using xda premium
same here
Hi, there,
just looking for solution for the same problem and got this thread...
well, I was rooted and on cyanogen and everything worked fine.
had backups and stuff.
decided to return to stock just to have it updated and backed up and after that to return to cyanogen.
when in CWM, after stock, while re-root-ing, I did a fix permission which erased some of my system files in the backups, so all my backups on the phone became useless (lesson #1: always move your backups away from the phone).
decided to start from scratch, so using ODIN I flashed the proper stock ROM for T999V. Installed the CWM version 5. something, superuser etc.
made a backup this time and store it outside the phone
when I tried to flash the cyanogen 10.0 for m2tmo (which I've flashed before without trouble), I got the error message as our friend here.
I edited the updater-script file in order to erase the first lines and got it flashed...
the problem that I have right now is that I am stuck in the first screen when the cyanogen keeps going round and round and round.... and nothing happens
any suggestion from here?
http://wiki.rootzwiki.com/ClockworkMod_Recovery#Status_7
The status 7 error can be from a bad download, bad signature, and I have seen it from using an old version of clockwork. I would first make sure you are running the most current version of recovery. if that doesn't solve your problem try redownloading the Rom.
Hi, So when I tried to open up twrp recovery, it wouldnt open....it would just stay at the logo and blink every now.and then....So I used oden and installed cwm over twrp and it was fine....I didnt like cwm so I went back to twrp..... it works fine and I can do everything EXCEPT some files are inaccessible and every time I flash something,it works but also gives me the error measages in the image I posted... does anyone know how to fix this?
Sent from my SPH-L710 using xda premium
razzack3000 said:
Hi, So when I tried to open up twrp recovery, it wouldnt open....it would just stay at the logo and blink every now.and then....So I used oden and installed cwm over twrp and it was fine....I didnt like cwm so I went back to twrp..... it works fine and I can do everything EXCEPT some files are inaccessible and every time I flash something,it works but also gives me the error measages in the image I posted... does anyone know how to fix this.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Maybe try installing twrp from goo manager while connected to WiFi to ensure a good download
Sent from my SPH-L710 using Xparent Skyblue Tapatalk 2
I had the same exact problem a couple days ago. I fixed it by going Into goo manager and re flashing a new TWRP. I did it on Mobile Data, worked fine!
Sent from my SPH-L710 using Tapatalk 2
Go back to 2.3.3.0. Search for the flashables ones. Since 2.4.2.1 TWRP have a lot of issues.
Sent from my SPH-L710
I see a lot of people complaining about TWRP related issues with various versions of this recovery.
Is there any reason people don't talk about CWM around here? I've been using different versions of cwm touch and twrp ... And I'm honestly pretty happy with cwm.
Why does it appear that people avoid talking about cwm? ... If indeed it works as well as it seems to me that it does?
One reason is that a lot of people think it's better and recommend it to others. I used cwm on my old evo and was going to when I got my s3, but most people and roms were recommending twrp. I've been using it and have tried out cwm as well. For me, at least it hasn't been problematic, but I don't download them through the goo manager. As I feel like I have less control over what I'm getting (I don't even know what version I'm getting until after I download it). That, and I just don't trust the phone to download without errors even when on Wi-Fi.
Just my two cents.
Sent from my SPH-L710 using xda app-developers app
I just actually switched to cwm a couple days ago because twrp had been giving me backup and restore problems.. everything twrp can do cwm does also, and it seems to be faster backing up and restoring also, but that might just be placebo... devs recommend twrp because that is what their Rom/kernel/mod was tested with... 99% of the time cwm will work just fine also
SPRINT GS3 FAQ
It might be that people are ignorant about cwm just like people are about androids
Sent from my SPH-L710 using xda premium
razzack3000 said:
It might be that people are ignorant about cwm just like people are about androids
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Actually, having used both, I think TWRP had been the better of the two because of the ease of naming your nandroids and the fact that backups in TWRP don't take up so much space as the CWM backups do. Have you seem the crazy Blobs folder in CWM? I like backing stuff up to the PC, but the CWM backups made that process extremely painful. I don't know what happened to make TWRP so unreliable recently, but I just noticed a newer version is out: 2.5.0.0
Sent from my SPH-L710 using Tapatalk 2
DurhamHusker said:
I see a lot of people complaining about TWRP related issues with various versions of this recovery.
Is there any reason people don't talk about CWM around here? I've been using different versions of cwm touch and twrp ... And I'm honestly pretty happy with cwm.
Why does it appear that people avoid talking about cwm? ... If indeed it works as well as it seems to me that it does?
Click to expand...
Click to collapse
There's nothing bad about CWM, but is 2013 and you can't rename your nands which is very important(not necesary) in a phone which date as 1970. Also the touch version looks like a '90 recovery.
But if you want a issues free TWRP go back to 2.3.3.0.
Sent from my SPH-L710
I did that... Now it only recognizes my ext sd card and the 0 folder in my internal storage that I clear out a while ago
Sent from my SPH-L710 using xda premium
topherk said:
One reason is that a lot of people think it's better and recommend it to others. I used cwm on my old evo and was going to when I got my s3, but most people and roms were recommending twrp. I've been using it and have tried out cwm as well. For me, at least it hasn't been problematic, but I don't download them through the goo manager. As I feel like I have less control over what I'm getting (I don't even know what version I'm getting until after I download it). That, and I just don't trust the phone to download without errors even when on Wi-Fi.
Just my two cents.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you update from goo manager, a pop up will tell you what version you are about to install beforehand. Also the webpage that it takes you to in order to start the auto download also states the name of the .IMG which also indicates version. I know what you mean about trusting downloads from the phone though. I personally think that is the reason a lot of people have issues with twrp. I've always updated to the latest twrp and flash almost daily, but have never had to switch versions because of bugs. All versions have ran perfect for me.
razzack3000 said:
It might be that people are ignorant about cwm just like people are about androids
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I've used both for quite a while. I used to only use cwm for the longest but decided to try out twrp because of those ridiculous blobs! What's with that? So I decided to try twrp and I've stayed because of all the little features like a warnings before you wipe things you shouldn't, option to flash more than one zip at once, option to clear cache and dalvik right after flashing, etc... Plus there are some pretty major features that get overlooked. Like the built in file browser. I installed miui once and it created a folder I could not delete and keep deleted. Every time I would reboot, it would come back. Twrp file browser deleted it and kept it deleted. The only thing I don't like about twrp is the system date and time being way off.
Edit: Lol. I've edited like 5 times because I keep wanting to add more info. Also, twrp doesn't take ages to fix permissions. As long as cwm takes, I can just do it manually
Sent from my SPH-L710 using Xparent Skyblue Tapatalk 2
I've been on 2.4.0 and 2.4.4, and only had to do backups but haven't tried to restore yet, so after hearing all the war stories, I went back to 2.3.1.
UPDATE: I just upgraded from 2.3.1 to 2.5.0, performed wipes, a backup and a restore and all went perfectly smooth. The only issue was the time was 2 hours behind what it should have been for US central, so I selected 2 hours ahead and chose military time (my preference) and I'm happy.
Where did you get 2.5.5?i only found 2.5.0
Sent from my SPH-L710 using xda premium
oops, I mean't 2.5.0