Develop Bugs

[Q] Clockwork Recovery v3.0.0.3 troubles

So I updated to the newest version of Clockwork Recovery and have backups that have a previous versions as well but as some of you may or may not know v3 is full of bugs.
I cannot flash or restore anything and the phone boots and force closes everything off of the restore. Only thing that seems to be working is 3G, wifi, and unlock screen. When I slide to unlock I get HTC Sense and HTC DM forced closing over and over.
Is there anyway to force a downgrade or switch to amon ra recovery from recovery mode?

Try doing a full wipe in recovery.
Sent from my PC36100 using XDA App

gqstatus0685 said:
Try doing a full wipe in recovery.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Tried the full wipe but the phone continues to act the same way, keeps rebooting the htc "quietly brilliant" screen.

CWM Recovery 3.0.0.X
If that doesn't work you may have to flash a stock image and re-root. Once re-rooted you can flash a prior recovery 2.5.x and restore from there. That's what I had to do after upgrade to 3.0.0.0. Not hard just frustrating.

I'm pissed. This should have been tested thoroughly. This isn't like some game that FC's. This screwed a lot of people. Unroot and re-root like he said.
Sent from my PC36100 using XDA App

I didn't have to reroot.
The latest version of ROM Manager allows u to flash to the 2.5 recovery in the Previous Versions of Clockwork button in ROM manager. Worked like a charm.
Sent from my Evo using the XDA App

I tried that and it didn't work. It said something about scripts.
Sent from my PC36100 using XDA App

Help!
I can't reroot or any of that, it won't get past the splash screen. I can access the recovery mode but when I restore a NAND backup or wipe and/or anything else it just reboots right into the splash again. This is a real big disappointment, I dont' think I will ever use clockwork again.

gqstatus0685 said:
I tried that and it didn't work. It said something about scripts.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Koush talked about how in 3.0 he removed the support for the old scripts that google has dropped since android 1.6. He and AmonRa kept support for that style of scripting for a while, but most rom builders should have been off of those by now. CyanogenMod has been using the newer scripting for more than 9 months now.

Just flash alternate at bottom of cwm
ricankng787 said:
So I updated to the newest version of Clockwork Recovery and have backups that have a previous versions as well but as some of you may or may not know v3 is full of bugs.
I cannot flash or restore anything and the phone boots and force closes everything off of the restore. Only thing that seems to be working is 3G, wifi, and unlock screen. When I slide to unlock I get HTC Sense and HTC DM forced closing over and over.
Is there anyway to force a downgrade or switch to amon ra recovery from recovery mode?
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

Omegablues said:
If that doesn't work you may have to flash a stock image and re-root. Once re-rooted you can flash a prior recovery 2.5.x and restore from there. That's what I had to do after upgrade to 3.0.0.0. Not hard just frustrating.
Click to expand...
Click to collapse
so do i still have to re root even if im s off?

Can't change roms?

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!

[Q] Not bricked but i cant boot my roms!

So my roms i download will install and boot up but once i get to that specific roms boot screen it just does an infinite loop. i then take the battery out, boot it into recovery and go back to my back up. I am not sure why it is doing this and would just love to be able to use cm7 (which did the infinite boot as well). its rooted using unrevoked and i have used a few other roms on it as well this has just been what has been happening lately. any help would be much appreciated!!

Had the same prob with cm7 #22, but 23 is working just fine, try that one. Remember the Dec said some may be broken, just fish around, but be very careful.
Sent from my ADR6300 using XDA App

Sorry, meant to say the "dev" said some cm7 nightlys are experimental and may be broken. Flash to the last rom that functioned for you, then use rom manager to download the latest cm7 nightly. Which is what I'm using now and am very satisfied with.
Sent from my ADR6300 using XDA App

30 is running great for me

6stringandy said:
Sorry, meant to say the "dev" said some cm7 nightlys are experimental and may be broken. Flash to the last rom that functioned for you, then use rom manager to download the latest cm7 nightly. Which is what I'm using now and am very satisfied with.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
see i tried the latest one and a few others. im not sure what it could be, that makes them go to the infinite boot screen. Should i try factory reset, root it again, restore my old version, then try to boot more roms?

crazyturtle777 said:
see i tried the latest one and a few others. im not sure what it could be, that makes them go to the infinite boot screen. Should i try factory reset, root it again, restore my old version, then try to boot more roms?
Click to expand...
Click to collapse
Flash CM7 in recovery. Then BEFORE you reboot, install a different kernel
This is your best choice for CM7 - http://forum.xda-developers.com/showthread.php?t=905873
Then reboot your Inc and see if it boots up, I have heard of a couple people who couldn't get their Inc to boot up with the stock CM& kernel, no clue why though.

hahaha so i got it to work. it was rom manager not letting me go through with it all. just did it manually through recovery. but i got sm7 to install and no notification bar. hence why im laughing. just gonn install miui and give her a shot.

Can't install new roms!! WTF? Bootlooping!?!

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.

Can't install any ROMs to SGH-T999V

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.