Related
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 all,
First post on xda here. I was trying to update my frosty jelly bean v6 to v7 via OTA update, installed the package and it restarted itself in CWM mode but it said something alone the lines of "failed update... update file not found." I downloaded the v7 package from the developer's link and was thinking about just installing it from zip on sd card.
Why can't it update? If I install v7 from the zip and wipe cache will that work too or no?
Sent from my SGH-T999 using xda app-developers app
Install from CWM yourself, as you suggested.
Do I have to perform a full data wipe for that then? Or would just cache and dalvik cache be ok.
Not really sure why OTA update didn't work in CWM in the first place, if anyone can offer answers that'd be helpful. Thanks!
Sent from my SGH-T999 using xda app-developers app
timma1 said:
Do I have to perform a full data wipe for that then? Or would just cache and dalvik cache be ok.
Not really sure why OTA update didn't work in CWM in the first place, if anyone can offer answers that'd be helpful. Thanks!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
This what you do after you put the zip in the scard...make sure your in recovery..
Wipe data/factory reset
Wipe cache & dalvik
Install Rom
Wipe cache and dalvik (again)
Fix Permissions
Reboot & let it sit for 5-10 mins (Don't touch anything!)
Reboot & enjoy!
*Please perform a full wipe for v7!
Hope this helps.
Thanks. Yeah I saw that on the dev thread... I followed those steps when i first flashed the frosty JB. But my question is do i really have to do a data wipe even for every version update? That seems to be a lot of hassle...
Sent from my SGH-T999 using xda app-developers app
Wipe Dalvik and dirty flash it. 4.1.1 > 4.1.2 = no clean flash necessary. I guess it's the devs' fault for spreading all of this clean flashing nonsense that's been more contagious than the bubonic plague. Like the IMEI loss rumors. It's only necesary if: going from ICS to JB, or vice versa. Or if you're having some major issue that no one else is having. Which is rare.
Thanks for the suggestion. I tried to dirty flash it but it said the signature verification failed?
Just to note the only tweak I made to my sd card previous to trying to update was deleting the original frosty JB v6 zip. That shouldn't matter right?
Sent from my SGH-T999 using xda app-developers app
timma1 said:
Thanks for the suggestion. I tried to dirty flash it but it said the signature verification failed?
Just to note the only tweak I made to my sd card previous to trying to update was deleting the original frosty JB v6 zip. That shouldn't matter right?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
What is the version of your CWM? i think its need to be updated.
3.0.7
Sent from my SGH-T999 using xda app-developers app
Yup, update it, the latest version is 6.xxx. i encountered the same error when i tried to install cm10 with an outdated cwm.
For a noob, you can easily update cwm by downloading and installing ROM MANAGER using your phone from PLAYSTORE.
launch the rom manager app then you can see an option there to update cwm
Id like to make a quick point on the dirty vs clean flashing.
Usually, it is correct that dirty flashing is ok except when jumping between android versions. (Even then, when going forward in version, its still often ok to dirty flash).
However, in the cases we see here this is not necessarily true. I am of course referring to our jb leaks and roms based on them.
Dirty flashing these after an update can cause problems. Many people, myself and the devs themselves included, have seen where a number of bugs would be nonexistent if you just did a clean flash. These are experimental builds based on leaked firmware. I'm certain the devs you guys are referring to recommend a clean flash for two reasons. First, it simply makes their rom operate much better. Second, and most important from a dev standpoint, if you dirty flashed, and are experiencing bugs, there is nothing the dev can really do for you. In fact, unless you clean flashed the rom, you shouldn't even report on bugs unless you find a fix for it.
Another thing to consider is a couple if these roms are based not just on a leak, but on multiple leaks often from more than one carriers device! Due to this, if you dirty flash you are much more likely to have bugs show up. It really depends on what has been changed, updated and rebased, and no one can predict how uts going to act.
No one says you cannot dirty flash these roms. Many have done so with few to no issues. But, if you do, and you run into problems please do not blame the dev or expect him to fix the problem unless it is being reported by the majority of users.
Not trying to argue or say anyone is right or wrong. I'm just trying to clear up the reason for the dev suggestion to clean flash.
Hope it helps!
Sent from my SGH-T999 using xda app-developers app
Hello in new to this forum my Lil bro got the new s3 so he was on stock and i used the rooted stock ROM so i won't trigger the counter after that i download aokp 4.2.1 that installed good but when i go back and flash gapps 12122012 it causes his keyboard to force close and a dialogue box pops up real fast mutiple times so can't see what its saying can someone help me please.
Sent from my SGH-T959V using xda premium
Install a different version of gapps.
Or
Are you sure you need gapps?
It's usually for aosp ROMs.
Reinstall the ROM clean
Then install your gapps
Sent from my SGH-T999 using xda premium
most built from source roms need Gapps flashed.
You probably just need to wipe cache and data from within app manager the app is Android Keyboard (AOSP)
Ok guys, these are modded versions of TDJ's tools to add the preload partition. This should allow you to wipe cache and dalvik without jacking up the symlinks. Also for you guys having issues installing a ROM, the superwipe should fix that. First flash the ROM and reboot (important), then if you are having issues flash the super wipe and then the ROM again. Reboot and you should be good.
Thanks again TDJ!!! You rock bro.
Note to other developers: Feel free to link here from your thread, just don't re-upload them please. Thanks
Everyone else: if you see these uploaded anywhere else please let me know. I have no problem with others linking to these but do not want them uploaded anywhere else.Thanks
Saved. . . . . . .
One more. . . . . .
I'm awesome
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
thx for this, i was annoyed by the preload problem.
Is this for CWM recovery or TWRP as well?
Sent from my SGH-T989 using xda app-developers app
Will work for both.
Thanks Jamison this will solve alot of headaches!
So whenever we want to wipe cache/dalvik use zip file instead of built in twrp??
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
euklid said:
So whenever we want to wipe cache/dalvik use zip file instead of built in twrp??
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
If on a TMo based 4.1.2 ROM, yes.
Whats the difference between the two downloads?
inpherknow said:
Whats the difference between the two downloads?
Click to expand...
Click to collapse
One is cache/dalvik, superwipe is data/factory reset.
Well before using the scripts ROM would not boot but after super wipe no problems, TWRP 2.5.0.0 :thumbup:
Sent from my SGH-T989 using xda premium
Jamison-does the cache wipe also fix permissions?
Sent from my SGH-T989 using xda app-developers app
Yes it does.
Sent from my dark hole called an office.
I used these scripts installing a ROM and I am having very serious issues. I was using Clockwork and when I rebooted I got stuck in a boot loop. I booted back into recovery but I was not getting fully back into recovery. I tried several times. I finally ODINed back to stock but I can't get the ****ing phone to boot up. It gets toa popup that says ""unfortunatley google partner setup has stopped" and then if I clear that "Google account manager has stopped", "google calender storage has stopped""unfortuantely the process com. android.phone has stopped". ****. I have tried ODIN to 3.5 stock and 4.0.3 both having similar issues.
Anyone have any idea, may have absolutley nothing to do with these scripts but any ideas would be very much appreciated.
What are you running and what are you trying to flash? Wouldn't be the scripts as they only wipe, format, align the partitions.
Sent from my dark hole called an office.
Jamison904 said:
What are you running and what are you trying to flash? Wouldn't be the scripts as they only wipe, format, align the partitions.
Sent from my dark hole called an office.
Click to expand...
Click to collapse
I was running CWM 6.0.2.9 touch and trying to flash the StockWalk ROM. I don't know if you have seen something like this before but it seems like I am totally unable to install any GAPPS even when flashing stock ROM in ODIN. I had flashed the same ROM before attempting to use the scripts, the reason was that I was unable to add my google account (may be a defect in the ROM but others are saying they have not had issue).
*when I say install GAPPS I am just refering to the ones that install on TW ROMS, I am not flashing a GAPPS file of any kind
ArcticFish said:
thx for this, i was annoyed by the preload problem.
Click to expand...
Click to collapse
blackangst said:
If on a TMo based 4.1.2 ROM, yes.
Click to expand...
Click to collapse
OK so I thought I knew enough to not feel like a noob, but here I am with three questions.
First question is what is a "preload problem"?
Second question is this will only work on 4.1.2, and not 4.2.2 (CM 10.1)?
And the third question is will using the original DS wipes mess something up?
T mobiles 4.1.2 loads a preboot partition. Wiping cache with anything but these scripts also wipes these partitions. This script is modified to not do that. No preboot partition = boot loop.
Thus, if you're on anything BUT Tmobiles 4.1.2 you don't need this script and there's no advantage to using it.
Sent from my SGH-T989 using xda app-developers app
Love this ROM but trying to make sure that I have the latest version. When I look in about phone it shows my version to be 1.190..I have downloaded 1.275 and when I boot into recovery to flash it still shows the earlier version. What am I doing wrong?
Have you checked inside of the beanstalk thread ??
That would be the likely place for information regarding BS roms and updates. ..g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
Any luck yet? I too have BS (and love it!) And am looking to update it as well...this was my first ROM so I'm not necessarily sure how to update...do I just DL the new patch and just flash right over the version I'm running now?
Yep
Sent from my SAMSUNG-SGH-I317 using xda premium
Most beanstalk releases should be able to be dirty flashed overtop of previous installs. But just make sure that for one your recovery is up to date and that you wipe cache after the rom flash is complete. There is an option sitting to the left of the reboot button after you flash a file in TWRP. If this doesn't work you might have to do a full wipe and start fresh.
Personally I've done about 4 consecutive dirty flashes and it's been alright but you can honestly never really tell. It's always the safer bet to do a clean install where you wipe everything and flash the new update.
~PsyCl0ne
Sent from my GT-N7105 using xda app-developers app
Okay of course it was user error. I found that when I was going to flash to file I was not going to the correct file to choose from. I have to go into the 0 file and then scroll down the downloads in that file. From there I can choose the correct file. Since all this I have stumbled upon the Liquid Smooth ROM with Soap kernel and it is mind blowing. Battery life is crazy.
Sent from my GT-N7105 using xda app-developers app