Hi
So I decided to install CyanogenMod on my Galaxy Nexus. I unlocked the bootloader, installed TWRP, but when I tried to install the .zip, I got an error 'Error executing updater binary'. Tried CWM too, got Status 7. How can I fix this? Thanks
Maybe a corrupted download. Try re-downloading it.
adamgraver said:
Maybe a corrupted download. Try re-downloading it.
Click to expand...
Click to collapse
Tried it already, didn't work.
Sent from my One M8 using XDA Free mobile app
Go into mounts and unmount system. That fixed errors for me.
Sent from my Galaxy Nexus
applerulez1 said:
Go into mounts and unmount system. That fixed errors for me.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Already was unmounted. Tried mounting it, but installing the zip seems to automatically unmount it.
Sent from my One M8 using XDA Free mobile app
What .zip are you trying to flash? I could try it on mine, are you sure its flashable or for your model? I'm running out of ideas sorry. Possibly reinstall your recovery if all else fails.
Sent from my Galaxy Nexus
applerulez1 said:
What .zip are you trying to flash? I could try it on mine, are you sure its flashable or for your model? I'm running out of ideas sorry. Possibly reinstall your recovery if all else fails.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I'm trying to flash the latest Cyanogenmod nightly, I'm sure it's flashable and I have reinstalled the recovery several times already. Even tried an older version of TWRP.
Sent from my One M8 using XDA Free mobile app
Okay so how I did that was I actually just installed the latest stable cm10. Then I went to the update section in settings and tapped update. It will update you to the cm11 snapshot, that is as far as I went but it also allows you to update to night builds as well. So just install cm10 and go from there, that's what I did at least unless somebody chimes in an easier way.
Sent from my Galaxy Nexus
applerulez1 said:
Okay so how I did that was I actually just installed the latest stable cm10. Then I went to the update section in settings and tapped update. It will update you to the cm11 snapshot, that is as far as I went but it also allows you to update to night builds as well. So just install cm10 and go from there, that's what I did at least unless somebody chimes in an easier way.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Tried it, didn't work. Now I'm stuck at the CM11 bootlogo (yes, CM11). And yes, I did clear cache.
Sent from my One M8 using XDA Free mobile app
Go back to stock then try what I said above again. It is possibly a hardware issue. I wish you luck c:
Sent from my Galaxy Nexus
applerulez1 said:
Go back to stock then try what I said above again. It is possibly a hardware issue. I wish you luck c:
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Ok, I reset it to stock, flashed TWRP recovery, installed CM10.2 and the 4.3 GApps package and updated it through CM Updater. For some reason, it worked! Thanks! The 4.4 GApps install was also successful, and now I have CM11 nightly! Thank you very much for your help!
No problem, anything to help a fellow galaxy nexus user! :3
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.
when trying to install a new rom i get the same error (status 7: some symlinks failed) with the cm10 and eclipse ROMs. I don't seem to have any trouble with Buglessbeast and euroskank. I have googled and searched XDA but none of the other threads are for the toroplus.
Edit: Thanks for all the help guys. I'm still having this problem.
Things i have tried: go into mounts and remove the top X on the list.(TWRP)
flashing a stock kernel gets me stuck in a boot loop.
I am using the franco kernel and had this same issue using CWM before switching to TWRP.
You can try this...
simms22 said:
try booting out of recovery into the bootloader, then back to recovery to reflash.
Click to expand...
Click to collapse
If you do a Google search you should find some information on it. Its something with the Franco kernel changing the sdcard. Have to download And move the original back into it's correct place
Sent from my Galaxy Nexus using xda premium
qbanlinxx said:
If you do a Google search you should find some information on it. Its something with the Franco kernel changing the sdcard. Have to download And move the original back into it's correct place
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Huh?
Op never even made mention to the word "kernel" in his post.
Not to mention kernel is not even running in recovery (which itself is a small os).
Sent from my i9250
natheist411 said:
when trying to install a new rom i get the same error (status 7: some symlinks failed) with the cm10 and eclipse ROMs. I don't seem to have any trouble with Buglessbeast and euroskank. I have googled and searched XDA but none of the other threads are for the toroplus.
Click to expand...
Click to collapse
Are you using TWRP recovery? If you are that's the issue. The latest update has a flaw, you have to go into recovery, go into mounts and remove the top X on the list. They said they where working on releasing a correction for it. If your not on TWRP then I don't know what's going on.
Sent from my Galaxy Nexus
I was using cwm but switched to TWRP to retry. Same issue.
Sent from my Galaxy Nexus using xda app-developers app
natheist411 said:
I was using cwm but switched to TWRP to retry. Same issue.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Try it when you get into recovery, go to mounts, remove the X on the top option on the list then flash the rom see if it works.
Sent from my Galaxy Nexus
I had this same issue yesterday, and it was related to flashing a kernel. Sorry for trying to help
bk201doesntexist said:
Huh?
Op never even made mention to the word "kernel" in his post.
Not to mention kernel is not even running in recovery (which itself is a small os).
Sent from my i9250
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using xda premium
qbanlinxx said:
I had this same issue yesterday, and it was related to flashing a kernel. Sorry for trying to help
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have also seen something similar. What most people don't realize is the some kernels, including Franco, change things in /system as well, which messes with some things.
Sent from my Galaxy Nexus using Tapatalk 2
Okay, thanks. I was not aware of this. Will checkout some kernel zips to see what's going on.
edfunkycold said:
Try it when you get into recovery, go to mounts, remove the X on the top option on the list then flash the rom see if it works.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I tried this. Still the same outcome. Thanks anyways.
Has this been fixed? I cant install any ROM!
I have exactly the same problem! I am using stock kernal, was using franco kernal before that.
Milamber said:
Has this been fixed? I cant install any ROM!
I have exactly the same problem! I am using stock kernal, was using franco kernal before that.
Click to expand...
Click to collapse
no one here was help but i think i figured it out myself.
try this and see if it works.
when you go to install the rom, before doing so wipe data (factory reset) three times.
i was so frustrated about it i finally said **** it and didnt care if i lost everything, but i didnt loose anything so all is well.
let me know if that works
(status 7) some symlinks failed
I'm fixed this problem, PLEASE ADD THIS POST TO FAQ . Just install Android Commander and copy ROM to phone via it, now i'm on JellyBam android 4.1.2.
1.Install root+busybox.
2.Install via stock recovery siyah 5.0b2
3.In siyah recovery do factory reset
4.Flash any custom ROM
5.Do factory reset, wipe cache, wipe Dalvik cache.
6.Be happy, enjoy.
I'm tryied many recoveryes and kernels, but the problem is in copying process(now all zip's have good CRC, and MD5). . Give me a beer
JeyLo said:
(status 7) some symlinks failed
I'm fixed this problem, PLEASE ADD THIS POST TO FAQ . Just install Android Commander and copy ROM to phone via it, now i'm on JellyBam android 4.1.2.
1.Install root+busybox.
2.Install via stock recovery siyah 5.0b2
3.In siyah recovery do factory reset
4.Flash any custom ROM
5.Do factory reset, wipe cache, wipe Dalvik cache.
6.Be happy, enjoy.
Click to expand...
Click to collapse
Huh? What is siyah 5.0b2???
I did a manual "format /system" from Clock Work Recovery, fixed it for me, Seems the Wipe/Factory reset does not reset the system partition correctly for some strange reason.
This was an issue after a custom kernel.
Milamber said:
Huh? What is siyah 5.0b2???
Click to expand...
Click to collapse
He's on a different device.
Sent from my i9250
chrisjenx2001 said:
I did a manual "format /system" from Clock Work Recovery, fixed it for me, Seems the Wipe/Factory reset does not reset the system partition correctly for some strange reason.
This was an issue after a custom kernel.
Click to expand...
Click to collapse
Wipe/Factory reset does not touch the system partition at all. This is normal. It only wipes the userdata partition.
chrisjenx2001 said:
I did a manual "format /system" from Clock Work Recovery, fixed it for me, Seems the Wipe/Factory reset does not reset the system partition correctly for some strange reason.
This was an issue after a custom kernel.
Click to expand...
Click to collapse
Had a bad download and on initial install I formatted system however it failed. Went back and formatted system and cache manually and worked for me.
I'm not sure if this is related, but I read in the MMuzzy's Jelly Bean 4.2.1 thread (http://forum.xda-developers.com/showthread.php?t=1762846, first post specifically) that unmounting /system fixes this problem, and sure enough it solved the problem for me when I tried to flash that ROM.
Hey guys, I'm really new to rooting, flashing roms, and Android in general (I've used iOS since 2007 until a month ago... please have mercy on my soul). I have an AT&T GN2 that I would like to remove the bloatware from, hence why I began investigating rooting, but it's snowballed into my desire to try out some of the amazing ROMs that the developers here have produced. Since the Note 2 uses the Exynos 4, I rooted using the ExynosAbuse exploit and downloaded Titanium Backup to freeze the AT&T apps. So far, so good.
However, I am wanting to get into how to flash custom ROMs, like CyanogenMod, so I downloaded the CWM RomManager and flashed the CWM Recovery. I downloaded the CyanogenMod 10.1 release for the i317 model (here: http://forum.xda-developers.com/showthread.php?t=2024495) and the latest gApps package (for 4.2.1), and flashed both from CWM RomManager. When it rebooted, it showed the CyanogenMod boot screen, but it appears to be stuck there. I'm not sure what to do at this point, and am hoping I didn't brick my phone. Is there anything I can do at this point?
Use the three button combo to get into recovery, should be volume up, home, and power, and then wipe data or install a stock rooted ROM. That should help get you to a bootable stage.
Sent from my GT-N7105 using xda premium
Have you changed kernel???
Sent from my MT11i using xda app-developers app
id10terrordfw said:
Use the three button combo to get into recovery, should be volume up, home, and power, and then wipe data or install a stock rooted ROM. That should help get you to a bootable stage.
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
When I booted into recovery, I got the CWM recovery (which is a good thing, I suppose). I wiped the cache, and then installed the CM 10.1 zip and gApps zip. However, I think I still need to wipe data/factory reset, right?
So, at this point, I've:
1. Rooted the device using Chainfire's ExynosAbuse apk (super easy).
2. Installed RootChecker (success) and TI backup (froze bloatware apps).
3. Downloaded CWM RomManager.
4. Flashed CWM Recovery.
5. Downloaded CM 10.1 port for i317 (the AT&T GN2 model) and the 4.2.1 gApps zips.
6. Chose to install ROM from SD card in RomManager, added both CM 10.1 and gApps, and only selected install (did not wipe cache or user data at this point).
7. Received blue CyanogenMod boot screen... excited... but it remains on the boot screen. Sad face.
8. Removed battery to power the device off, placed battery back in, and then booted into recovery mode (CWM recovery).
9. Installed the CM 10.1 zip and gApps zip from SD, then wiped cache.
10. ???
Wipe data factory reset. Wipe cache/dalvik. Flash cm, flash gapps. Reboot
And dont use rom manager. Do it in recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Peleus16 said:
Have you changed kernel???
Sent from my MT11i using xda app-developers app
Click to expand...
Click to collapse
This is a great point, at no point op has mentioned kernel.
Sent from my SAMSUNG-SGH-I317 using xda premium
cdshepherd said:
Wipe data factory reset. Wipe cache/dalvik. Flash cm, flash gapps. Reboot
And dont use rom manager. Do it in recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Okay, booted into CMW recovery and performed all in that order. It booted! Hurrah. Only problem: the AOSP keyboard crashes constantly, making text input not possible. Sigh...
NowhereOutThere said:
Okay, booted into CMW recovery and performed all in that order. It booted! Hurrah. Only problem: the AOSP keyboard crashes constantly, making text input not possible. Sigh...
Click to expand...
Click to collapse
Boot back into recovery and fix permissions. That may help
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
cdshepherd said:
Boot back into recovery and fix permissions. That may help
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I booted into recovery mode and fixed permissions... the keyboard still crashes, which means I can't type anything. Do I have to do anything with the kernel? I didn't wipe the dalvik cache, should I have done that?
EDIT: wiped dalvik cache, didn't do anything... apparently, this was a fine release so I'm not sure what could be causing the keyboard issues.
NowhereOutThere said:
Okay, I booted into recovery mode and fixed permissions... the keyboard still crashes, which means I can't type anything. Do I have to do anything with the kernel? I didn't wipe the dalvik cache, should I have done that?
EDIT: wiped dalvik cache, didn't do anything... apparently, this was a fine release so I'm not sure what could be causing the keyboard issues.
Click to expand...
Click to collapse
Im not exactly sure either. I have yet to flash cm. Read the cm thread?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
cdshepherd said:
Im not exactly sure either. I have yet to flash cm. Read the cm thread?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
So what ROM are you using? I just picked cyanogenmod because I've heard of it before, but I would like something that works. Is there a way to add another ROM onto the phone's storage, as I don't have an SD card... And since I can't type anything, it's not like I can download it from the phone's browser?
NowhereOutThere said:
So what ROM are you using? I just picked cyanogenmod because I've heard of it before, but I would like something that works. Is there a way to add another ROM onto the phone's storage, as I don't have an SD card... And since I can't type anything, it's not like I can download it from the phone's browser?
Click to expand...
Click to collapse
Plug it into your computer and see if you can mount your internal sd. If you can download a new rom to your computer and transfer it to sd. Did you make a backup before flashing?
Im just running stock rooted for now.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Well, I'm downloading CleanROM right now. I also downloaded another cm 10.1 file just in case, perhaps it's because I downloaded it on the mobile Chrome browser that I'm having problems? I also downloaded a kernel from the thread to help with performance. However, if I can't get these on the phone, it doesn't matter. Since I'm on a Mac, I have to use Android File Transfer, and it isn't registering my phone, unfortunately. I may have to go out and buy a cheap SD card and throw the files on there. It may not hurt to have one around, anyways.
Text yourself the download link to CleanRom. :thumbup:
And chrome shouldnt have made a difference. I take it you didnt make a nandroid backup before you flashed cm?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
cdshepherd said:
Text yourself the download link to CleanRom. :thumbup:
And chrome shouldnt have made a difference. I take it you didnt make a nandroid backup before you flashed cm?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
No... I thought that a backup of the original ROM was made when flashing CWM recovery, but I am a noob and that did not happen. Unfortunately, the browser doesn't even work! So I cannot text myself the link for the download. I should be able to flash a zip file from a micro sdhc, right?
Flash the right GAPPS, the crashing keyboard is a symptom of incorrect GAPPS. The December one is for 4.2.1 only, which is what CM10.1 is based on. Make sure you flash the right GAPPS with the right CM version.
Sent from my GT-N7105 using xda premium
The CM you linked in the OP is CM10 not 10.1, so you flashed the wrong GAPPs
ManelScout4Life said:
The CM you linked in the OP is CM10 not 10.1, so you flashed the wrong GAPPs
Click to expand...
Click to collapse
Oh... crap. Is there any way I can get the correct gApps on my phone? Ugh... I'm going to have access to a Windows machine today, so I can download the correct GAPPS and put them on my flash drive. I can still put it in USB debugging mode, but will the PC recognize it? Android File Transfer software for Mac does not recognize the phone any more, so I'm a bit limited in what I can do. Unless, like I said before, I can just pop in an SD card with the correct file.
Just grab goo manager from the market and dl the correct gapps to your phone. Either that or use your phones browser. No need for a pc. Boot in recovery, wipe cache and dalvik and flash correct gapps. Should be gtg.
Edit: just saw your browser isn't working. Goo manager's your best bet. Could always try another browser from the market as well. Good luck.
NowhereOutThere said:
Oh... crap. Is there any way I can get the correct gApps on my phone? Ugh... I'm going to have access to a Windows machine today, so I can download the correct GAPPS and put them on my flash drive. I can still put it in USB debugging mode, but will the PC recognize it? Android File Transfer software for Mac does not recognize the phone any more, so I'm a bit limited in what I can do. Unless, like I said before, I can just pop in an SD card with the correct file.
Click to expand...
Click to collapse
While in recovery plug usb into computer (make sure drivers are installed) in recovery menu navigate to mount usb storage. See if that works
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Hey guys,
I am using PA on my Galaxy Nexus and loving it, not I am trying to put it onto a Note 2 (317M)
Not to sure why I am getting a E:signature verification failed when I am trying apply the rom in recovery mode...
I rooted with Odin, I have CWM installed, wiped the cache and did data/factory reset.
Also I downloaded the file from this link, which I got from the Note 2 PA page http://forum.xda-developers.com/showthread.php?t=2069430
Any help would be greatly appreciated!
JERF!
maybe you got a bad download? did you verify md5?
Must be a bad download, or something else. Not to sure why its not working...
To bad, I love this ROM.
Just downloaded & installed.
Try to re-download
Or try TWRP. I've had issues with cwm not being able to install certain .zip files and twrp works fine
Sent from my SGH-I317 using xda app-developers app
g2tegg said:
Or try TWRP. I've had issues with cwm not being able to install certain .zip files and twrp works fine
Sent from my SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
i just installed paranoid last week to test for a few days with cwm no problem. op most likely didn't verify the md5 so that's why he's guessing he's got a bad download and doesn't know for sure. that's probably the easiest way to confirm whether or not it's worth flashing. got a bad download and didn't verify md5, then you'll run into problems and i dunno.. worst case brick your phone.
I was using the latest alpha of CM11, then i i wanted to get back to CM10.2, i did all i had to do (wipes, and stuff) and when starting up, the phone frezees and keep on doing this...
I also have searched about this issue and found no answer.
tpag02 said:
I was using the latest alpha of CM11, then i i wanted to get back to CM10.2, i did all i had to do (wipes, and stuff) and when starting up, the phone frezees and keep on doing this...
I also have searched about this issue and found no answer.
Click to expand...
Click to collapse
Have you tried booting to recovery, then doing an advanced wipe (system/data/cache/dalvik) and reflashing rom/gapps?
What version of recovery are you using?
Almite said:
Have you tried booting to recovery, then doing an advanced wipe (system/data/cache/dalvik) and reflashing rom/gapps?
What version of recovery are you using?
Click to expand...
Click to collapse
yes, i have. I also got back to stock, used an older recover, flashed with an older version of CM and nothing. I first was using CWM 6.0.3.7., after that I used 6.0.4.3, then an older version of TWRP but nothing. I also tried booting to system without flashing gapps.
With stock ROM everything works just fine.
Just wipeout internal and external card once and than install with twrp 2.6.1.0. And don't forget to say thanks
Sent from my SGH-T989 using xda app-developers app
iamdofus said:
Just wipeout internal and external card once and than install with twrp 2.6.1.0. And don't forget to say thanks
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Well, thank you, but it didn´t work.
it happened to me the same thing months ago. never had solution. still in waiting. attempt internal and external SD format. and followed the same. I hope someday they can come up with the solution! : (
i have the same problem too
I try to install multiple ROM 4.2.2 and I could only install one version AOKP Milstone JB1. I also worked the other. however all 4.1.2 rom if I worked. I could not install any 4.3 and 4.4 now does not know what is the problem but I've tried everything! anyone found the solution yet but I see I'm not the only one! (excuse my bad English, not my language )
Well you all are right, I am also using shadow mastery (stock rooted rom). Just because I had the same problem sometimes stucking and rebooting and sometimes after going in gallery. Even I can't use 4.3 and 4.4 roms. Anyone have to contact with room developer or someone who know about this problem.
Sent from my SGH-T989 using xda premium
You might want to find an Official T-Mobile or Telus 4.1.2 or 4.0.3/4.0.4 rom that is Odin flashable, not one that has been custom made/flashable from recovery - then just start over after getting back to true stock, change to TWRP or CWM recovery that is 4.3+ compatiable, root and then flash rom/gapps etc.