Since upgrading to 4.4.2, the clock on the top right keeps freezing, where it just stops updating for hours. I am using Franco kernel and the optimized bionic/dalvik patches, everything else is stock.
Anybody else having this issue? Not sure whether it's related to this issue, but I did flash the razorg system image by accident before updating to 4.4.2. But I did use a nandroid backup to restore a good state before installing the 4.4.2 update.
Sent from my Nexus 7 using xda app-developers app
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.
Lately after I turn on my phone appears a message that process com.android.phone has stopped. The problem occurred in version 4.1.1, I did a factory reset to version 4.1.2 and the problem persists. Anyone knows a solution?
Try clearing data for the phone app. I had similar problem with contracts storage app
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
Doesn't work =/
Sent from my Galaxy Nexus using xda app-developers app
I had the same problem after flashing 4.1.2 rom.
Then I went back to 4.1.1 and this problem disappeared.
Though I'm on 4.1.2 again without the error message.The ways from this thread may help you.
1) run "Fix Permissions" via Rom manager or CWM
2) remove stk.apk from system/app
Hey All,
What was this latest update for?.My phone suddenly is using lots of battery with everything looking normal.
ecarbone51 said:
Hey All,
What was this latest update for?.My phone suddenly is using lots of battery with everything looking normal.
Click to expand...
Click to collapse
They fixed the boot loop issue, and I think pushed a newer recovery, but nothing else as far as I know.
Sent from my ADR6300 using xda app-developers app
Several of the framework files were updated, and system apps were updated. Like stated before, it is ment to fix reboots.
Hi, this morning I encountered something which I haven't seen before in my 3 years or so of flashing roms on Android phones. The scenario was the standard process: Root with Odin > Install CWM with Odin > Copy Rom / gapps package to sdcard > Wipe & Install rom with CWM.
I rooted my Note II using CF Auto Root, all went fine, I flashed the latest Phil's touch CWM recovery using Odin which was also successful.
I had root access and was able to do a titanium backup of apps and messages/call logs. I successfully did a Nandroid backup of the stock rom.
After wiping data through CWM as per normal, I flashed the latest Utacka ParanoidAndroid and gapps. The flash was successful, but after rebooting, the 'Samsung Note II' splash screen only appeared briefly, then the image sheared and distorted and the screen went black, in less than three seconds.
I restored my nandroid backup and repeated the process, this time also formatting system, and installing CM10.1 nightly instead of PA. Again, I got a distorted splash screen then a black screen when trying to boot.
Can anyone think of a reason why my phone does not seem to be able to boot a custom rom?
Many thanks
I read on the forum someone else had a similar issue with cm as well
Sent from my GT-N7100 using xda app-developers app
koalauk said:
I read on the forum someone else had a similar issue with cm as well
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Really? I've tried searching xda, google and the CM forums and havent found anything relevant.
I had this problem recently and after some nice guys helping me out we conclude that the solution is to flash RedPill kernel as the culprit for this glitch is the stock kernel you previously had.
I had such issue with my Note2 too. I was advised to flash Thor kernel 0.15 too after flashing cm10.1 and gapps. And problem was solved. Now cm10.1 boots normal on my Note2.
Sent from my GT-N7100 using xda premium
Did you do a factor reset.
Sent from my GT-N7100 using xda app-developers app
If I boot into recovery, wipe cache and dalvik (I fix permissions too, although this probably isn't necessary), then it boots right up like nothing is wrong with no fanfare.
If I'm lucky, this will even persist for an additional reboot. Otherwise on subsequent reboots it just bootloops forever until I go back to recovery and wipe cache/dalvik again, and then it boots right up again. Once into the ROM, everything runs fine, no issues at all.
I've tried rolling back a nightly or two but it doesn't seem to make a difference. Was there some major change in the last few weeks that I missed? How far do I need to roll back to get this to work?
It's my gf's tablet so I don't really want to wipe data if I can avoid it. Was even thinking of dirty flashing up to CM11.
Any insight is appreciated.
With my phone this problem ended up being using the wrong baseband version for the ROM/kernel that I was using. I was able to fix it by resetting it back to stock using ODIN (tool which can be used to recover Samsung devices) but from the sounds of it you have no such luxury.
Do you have any backups of when everything worked? If not try to find a way to get back to stock however you can. Aside from that make sure that you are using the correct ROM for your hardware.
Good luck and keep us updated.
czahrien said:
With my phone this problem ended up being using the wrong baseband version for the ROM/kernel that I was using. I was able to fix it by resetting it back to stock using ODIN (tool which can be used to recover Samsung devices) but from the sounds of it you have no such luxury.
Do you have any backups of when everything worked? If not try to find a way to get back to stock however you can. Aside from that make sure that you are using the correct ROM for your hardware.
Good luck and keep us updated.
Click to expand...
Click to collapse
The kindle is wifi only, so I don't think there are any baseband issues. Will update when/if I fix it.
Restoring to stock is a good idea. It's been over a year since this thing was stock, so it's quite possible we missed a firmware update or something.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Mine does this after I installed the new sgt7 4.4.2 rom. Did you end up fixing yours?
whatever100 said:
Mine does this after I installed the new sgt7 4.4.2 rom. Did you end up fixing yours?
Click to expand...
Click to collapse
Not yet, but I think it worked fine on cm10.2 for awhile.
Sent from my Nexus 5 using XDA Premium 4 mobile app
UPDATE - I dirty flashed cm11 and gapps as if I were updating any other nightly, and the issue appears to be gone. So freaking annoying, lol.