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!
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.
I used to format /system every time I flashed a ROM on my gs2, but I saw in the numerous imei threads some posts about not doing so because it may be part of the lost imei issues. Do you do it ? Have you had issues ? I'm reluctant to do so , but feel it will be " beneficial to my flashing" if I did...
Sent from my SGH-T999 using Tapatalk 2
jasonren29 said:
Format system does not wipe out imei. It's when you root it the wrong way. If you want to play safe, you can go to development section use imei back up method to back it up
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
+1
Sent from my SGH-T999 using xda premium
No lie I formatted my system the other day and right after tried to revert to a stock android backup that I made. And wasn't able to do so because it told me M.D.5 sum mismatch after I reverted to it earlier in the day. Huh is what I was like and after that clockwork mod recovery would let me restore a cm10 backup I made said something about couldnt restore system. So out of frustration I went back to being unrooted. Just couldn't take the problems with clockwork mod because that's what where the problems ly. It wasn't me it was the recovery
Sent from my SGH-T999 using xda premium
jasonren29 said:
Did you changed the backup in any format? Change name or date? Any minor changes to the backup will fail md5 check
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
None what so ever. I really just flashed the stock back up right before I flashed my gsfree back up so no I made no changes what also ever. Some times when you format systems in clockworkmod recovery this could happen because it happen to me. Can't wait till ext4 touch recovery comes to us here in this forum. Not saying cwm recovery isn't nice but I never had any problems with other recoveries that have been offered.
Sent from my SGH-T999 using xda premium
einrae214 said:
No lie I formatted my system the other day and right after tried to revert to a stock android backup that I made. And wasn't able to do so because it told me M.D.5 sum mismatch after I reverted to it earlier in the day. Huh is what I was like and after that clockwork mod recovery would let me restore a cm10 backup I made said something about couldnt restore system. So out of frustration I went back to being unrooted. Just couldn't take the problems with clockwork mod because that's what where the problems ly. It wasn't me it was the recovery
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
There are ways to fix that issue with the MD5 sum mismatch. I've had it happen a few times and ran a few commands thru ADB and got it working.
Kid Poker said:
There are ways to fix that issue with the MD5 sum mismatch. I've had it happen a few times and ran a few commands thru ADB and got it working.
Click to expand...
Click to collapse
Yes you are right. But I didn't want to go thru all of that. Really didn't have time so just unrooted my phone so there would be no more problems. I get like alot of people and become flash aholics. So I just stop it from being problem later down the road. Look I like rooting and adding mods to my phone like the next guy but there comes to a point where unnecessary issues can be avoided. Like the one I had.... but on the real tip I really enjoy the phone just the way it is STOCK I have zero issues and love the battery life that I have. So until some cooler roms come out I just don't have interest in cm9 or cm10 base roms. I mean I came from the sensation where I could flash a lot more variety of roms. I like this phone the way it is and really that's why I bought it.
Sent from my SGH-T999 using xda premium
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.
Hey i've been on the universe rom for quite some time now, but on FI03, i see that "Shadow_god" has released a ver3 with the F127 agat kernal update which i would like to upgrade to.....But do i use the modified caulk format thats recommended because of coming from a previous version or do a fresh flash, (i had heard that the save data opt could be ifffy in certain cases) Thanks a bunch & keep up the great work
I've been running shadow gods rom from 1.0 and I think it's the best out there. I always flashed from version to version using calks modified format and never had a problem. Never really heard anyone having a problem doing it that way other than a bad download. Just make sure you do a nand backup and you'll be fine
Sent from my SPH-D710 using xda premium
quietmode01 said:
I've been running shadow gods rom from 1.0 and I think it's the best out there. I always flashed from version to version using calks modified format and never had a problem. Never really heard anyone having a problem doing it that way other than a bad download. Just make sure you do a nand backup and you'll be fine
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Worked like a charm! thanks, but quick question...what happened to the usual accessable reboot into recovery opt.?? can i still power down and access it (mods, add-ons)?
Yeah you a can still do it that way. Also He has a jb_ish redesign w/extended toggle that has it on there.
Sent from my SPH-D710 using xda premium