Not sure exactly what happened. I was using the tablet and all of a sudden the bottom three buttons disappeared as well as the top bar. The system kept getting force closes. I rebooted and it just sat in the reboot mode. I tried to recover from the system but that is not working. I cant seem to get the system to mount via usb now. I am in clockwork mod v5.8.0.2 and do not see an option. If I could mount it I could put an img file back on and get it to work. Any help would be great.
xndrxw said:
Not sure exactly what happened. I was using the tablet and all of a sudden the bottom three buttons disappeared as well as the top bar. The system kept getting force closes. I rebooted and it just sat in the reboot mode. I tried to recover from the system but that is not working. I cant seem to get the system to mount via usb now. I am in clockwork mod v5.8.0.2 and do not see an option. If I could mount it I could put an img file back on and get it to work. Any help would be great.
Click to expand...
Click to collapse
You could try to flash back the stock software to see if that helps? Look here for some help.
Are you running a custom ROM or anything else? ALSO, once you do manage to get everything fixed, I would upgrade your CWM to the most current version 6.0.1.0 by flashing this in the older (5.8.0.2) version.
Sounds like it might be permission related, you could try a 'fix permissions' in recovery
Sent from my GT-I9300 using Tapatalk 2
Permissions did not fix it. I am trying to figure out the ADB.
xndrxw said:
Permissions did not fix it. I am trying to figure out the ADB.
Click to expand...
Click to collapse
Just do a bunch of reading! We were all noobs once
I keep getting the message "error: cannot load 'bootloader-grouper-3.34.img' . It seems like something is wrong with the file. Is there a way I could just flash another Rom on this way or even update the clockwork mod using adb?
xndrxw said:
I keep getting the message "error: cannot load 'bootloader-grouper-3.34.img' . It seems like something is wrong with the file. Is there a way I could just flash another Rom on this way or even update the clockwork mod using adb?
Click to expand...
Click to collapse
Did you download the nakasi file from the google site? You shouldn't have an issue with that. And you can update CWM using ADB, just check over in the Android Development section.
A lot of people have been having problems with the nexus 7, best bet is return it and get a new one
Sent from my Galaxy Nexus using xda app-developers app
Finally got it working. Now just need to install the new clockwork mod and move this thing to the GlazedJellyBean rom.
Boooty said:
A lot of people have been having problems with the nexus 7, best bet is return it and get a new one
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
This is seriously not the advice to be giving out on the forums for a minor software issue on an unlocked and rooted tablet especially.
Boooty said:
A lot of people have been having problems with the nexus 7, best bet is return it and get a new one
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Worst advice i've heard, ever.
Sooo true.. You root/ unlock its yours NOT GOOGLES TO REPLACE
CharliesTheMan said:
This is seriously not the advice to be giving out on the forums for a minor software issue on an unlocked and rooted tablet especially.
Click to expand...
Click to collapse
similar issue with TWRP.. I did temp root thru nexus root/recovery app (thanks dev) Then pushed cwm recovery to data/media.. Booted back into temp cwm from above and flashed up to date cwm.. will stick with cwm for now..
good luck OP .
xndrxw said:
Finally got it working. Now just need to install the new clockwork mod and move this thing to the GlazedJellyBean rom.
Click to expand...
Click to collapse
i'm having the same issue. how did you finally get it to work? i've redownloaded the file a bajillion times and still nothing. HELP
Related
Anyone else having this problem?
I'm using Unrevoked 3.1 on Windows XP.
I've got USB debugging on and the drivers installed.
The phone reboots into HBoot but then never goes into recovery. Just reboots.
Anyone else having this problem? It is definitely screwing me over for 2.2 haha.
andrewzpsu said:
Anyone else having this problem?
I'm using Unrevoked 3.1 on Windows XP.
I've got USB debugging on and the drivers installed.
The phone reboots into HBoot but then never goes into recovery. Just reboots.
Anyone else having this problem? It is definitely screwing me over for 2.2 haha.
Click to expand...
Click to collapse
Is superuser permissions installed? And if so what do u get when u open terminal emulator and type Su?
Sent from my ADR6300 using XDA App
tcberg2010 said:
Is superuser permissions installed? And if so what do u get when u open terminal emulator and type Su?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Superuser will not install. Unrevoked just reboots the phone it seems... never going into the custom recovery or flashing SU.
Which is my problem haha. I want 2.2 but can't flash it without root.
If I lose root because of this and am the only one I'm not going to be a happy camper lol
Possible
After reading 700+ pages of the other thread I have decided to steer clear from the buggy-beta and wait for the OTA, but I have had trouble with v3.1 and a regular reboot, so I wanted to chime in with 1 question:
Is your phone hot while this is happening?
I returned my Incredible due to excessive heat triggering reboots. When the phone was in the warm-to-hot zone, I could NEVER get into recovery. I could get into HBOOT, choose recovery, and then it would do 2 reboots, the second one being a regular.
Only way i could get into recovery was with a fully charged overnight battery, first thing in the morning (phone nice and cool).
Just got into it. used the custom image... the new 2.5.0.4 (if I'm not mistaken).
It was weird, and it may not be the image... it may have just taken like 10 tries to do it.
I'm not even wasting my time loading the OS... just putting on Froyo right now while in clockwork.
Crossing my fingers that it loads!
andrewzpsu said:
Just got into it. used the custom image... the new 2.5.0.4 (if I'm not mistaken).
It was weird, and it may not be the image... it may have just taken like 10 tries to do it.
I'm not even wasting my time loading the OS... just putting on Froyo right now while in clockwork.
Crossing my fingers that it loads!
Click to expand...
Click to collapse
Create nandroid backup before u do anything else, just in case.
Sent from my ADR6300 using XDA App
tcberg2010 said:
Create nandroid backup before u do anything else, just in case.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I have backups pre-OTA.
andrewzpsu said:
I have backups pre-OTA.
Click to expand...
Click to collapse
As long as u have extra protection in case the first layer fails you'll be alright
Sent from my ADR6300 using XDA App
WARNING!
Ask your questions in correct thread. If a new thread must be started, and a question is asked, use the General section. Thanks
seemed to work for me
having trouble after i got the new ota loaded. I get to the reboot phone reboots then unrevoked says waiting for phone to reboot any ideas didn't have this problem before?
edit: never mind got restarted computer life is good now
I am having the same issue. I have installed the drivers, then when I run the reflash tool it reboots my phone after about 3 seconds and loads up HBOOT and then from there it reboots my phone and the reflash tool either says "waiting on phone to reboot" or "installing image" or something like that but it just sits there for hours and doesn't progress. I have debugging enabled.
To add a little history, I already rooted using the hard method awhile back and then unrooted. Now I am trying to root again and can't.
Hey trying to help my brother with his phone and I've never encountered this problem before.
He downloaded Rom Manager from the Market and proceeded to flash CWM.
After flashing I told him to use the "Reboot into recovery" in order to create a NANDroid back up.
His phone reboots and then gets stuck on an image of what he says is a "phone with a red exclamation mark."
I've checked with him and he says "fast boot" is off. His phone IS rooted.
Obviously this is the first time he's ever needed to use CWM.
I've never personally encountered this problem and I've rooted 10 (6 replacements for me and one for my wife, 2 for my brothers and one for their girlfriend lol.) MT4Gs and have installed custom ROMs.
If you guys have any suggestions or ideas PLEASE let me know.
Thanks a lot.
The forum search yielded some threads about turning off "fast boot" or maybe a bad flash.
I've had him reflash CWM. Still no luck.
Again, thanks for any help.
I'm assuming he's rooted right? With S-OFF? In any case, it seems that it's not sticking. One common mistake is that he might have accidentally denied the SU permissions while opening RM. So un install and re install RM and make sure you accept SU permissions.
mackster248 said:
I'm assuming he's rooted right? With S-OFF? In any case, it seems that it's not sticking. One common mistake is that he might have accidentally denied the SU permissions while opening RM. So un install and re install RM and make sure you accept SU permissions.
Click to expand...
Click to collapse
Yeah Macky...he is rooted. I'll have him try it again. He did mention something about su.binary something or another.
I told him to update Superuser. We'll see if that helps.
nguyendqh said:
Yeah Macky...he is rooted. I'll have him try it again. He did mention something about su.binary something or another.
I told him to update Superuser. We'll see if that helps.
Click to expand...
Click to collapse
Yeah try updating the latest SU and make sure he didn't deny RM. That's might be what happened. If not, try updating his CWM manually via terminal emulator, ADB or Fastboot.
Here's how to do that.
For clockwork recovery to actually work, you have to download rom manager and from within rom manager install clockwork first.
You just do not download rom manager and right away boot into recovery.
Sent from my HTC Glacier using xda premium
Maybe I shouldn't be rude. Sorry.
nguyendqh said:
"He downloaded Rom Manager from the Market and proceeded to flash CWM."
Thanks. I can tell you read the original post. Appreciate the help man.
I didn't know that at all.
Click to expand...
Click to collapse
Whoa! Why don't we chill out a bit yea. I just mentioned it because some people think that just downloading rom manager and trying to boot into recovery that's how you flash the thing and get it working.
And I did read the whole thing and did read where you said rom manager got downloaded and prceeded to flash cwr. But you also stated you told your bro to press reboot into recovery. Which made me think he probably mistakenly, try booting into recovery before actually flashing it. I was just trying to cover steps to help you guys out.
Sent from my HTC Glacier using xda premium
coupetastic-droid said:
Whoa! Why don't we chill out a bit yea. I just mentioned it because some people think that just downloading rom manager and trying to boot into recovery that's how you flash the thing and get it working.
And I did read the whole thing and did read where you said rom manager got downloaded and prceeded to flash cwr. But you also stated you told your bro to press reboot into recovery. Which made me think he probably mistakenly, try booting into recovery before actually flashing it. I was just trying to cover steps to help you guys out.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I apologized in the previous post before I even saw this. Sorry bad day at work.
Not your fault.
And thanks. Honestly. =P
nguyendqh said:
I apologized in the previous post before I even saw this. Sorry bad day at work.
Not your fault.
And thanks. Honestly. =P
Click to expand...
Click to collapse
All good. Hope you find a fix.
Sent from my HTC Glacier using xda premium
coupetastic-droid said:
All good. Hope you find a fix.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Gonna give this a try when he gets home from work.
http://forum.xda-developers.com/showthread.php?t=1200147
I got the ota the other day and debated installing it because my M is rooted and the bootloader is unlocked and I have flashed ClockworkMod recovery. I searched for a while to see what others were saying and didn't really find anything of note so I decided to go ahead and run the install. When the phone rebooted into recovery and tried to install the update, it gave me the following Error: E: Failed to verify whole-file signature. Then there was an option to apply unsigned update (or zip, I can't remember the wording exactly). I chose not to do this and went back in the recovery menu and rebooted back into system. The phone booted normally and then immediately rebooted on its own back into recovery to try to install the update again, ending in the same results. This happened 2-3 more times before I finally formatted the Cache Partition through cwm which ended the bootloop (not sure that you can really describe that as a bootloop since it was actually doing what it thought it should be). My question is this, is it safe to go ahead and install the unsigned update via CWM? I have also since seen threads stating that if you had removed some of the bloatware apps, that the update would fail. I have removed many of these unneeded apps, should I reinstall them? I have seen a link or two to the bloat apks...
Having a unlocked bootloader doesn't matter. You just need to be stock 4.1.1 bloatware and all.
what he said^
you can update it with cwm but you have to have all the crapware that came stock still present.
Do you have to unroot first to get it to install? I have TWRP recovery on mine and can't get the update to install.
Sent from my XT907 using xda app-developers app
bobcheeks said:
Do you have to unroot first to get it to install? I have TWRP recovery on mine and can't get the update to install.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No. You don't have to unroot. You must have modified something else.
Sent from my Nexus 7 using Tapatalk 2
antp121 said:
what he said^
you can update it with cwm but you have to have all the crapware that came stock still present.
Click to expand...
Click to collapse
So if I restore the bloatware, it is ok to choose the "install unsigned zip"?
Thanks for the quick reply, you guys rock!
bwat1009 said:
So if I restore the bloatware, it is ok to choose the "install unsigned zip"?
Thanks for the quick reply, you guys rock!
Click to expand...
Click to collapse
If its all there, yep. It'll be fine
Sent from my Nexus 7 using Tapatalk 2
antp121 said:
If its all there, yep. It'll be fine
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
bwat1009 said:
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
Click to expand...
Click to collapse
I RSDed back to 4.1.1 because mine hung on the clock app. I had installed the 4.2 clock.
bwat1009 said:
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
Click to expand...
Click to collapse
You could try grabbing the apk from /data/app and moving it to /system...
Or grab it from one of the many /system dumps around here...
Someone should turn the OTA into a flashable zip from CWM/TWRP that doesn't check for that.
I may do that...
sloosecannon said:
You could try grabbing the apk from /data/app and moving it to /system...
Or grab it from one of the many /system dumps around here...
Someone should turn the OTA into a flashable zip from CWM/TWRP that doesn't check for that.
I may do that...
Click to expand...
Click to collapse
I had the same thought about moving the apk to the system/app directory and did just that. My expectation was that I would still get the error but for a different app since I just tested with the one that had been throwing the error but it didn't change, still gave the error for the amazon mp3 app even though it was successfully installed in the correct directory. Thanks for the thought though. If you could turn it into a flashable zip, I would be much appreciated. I would love to do that myself but I have no idea how. I know just enough through trial and error (and a lot of forum reading) to be dangerous...
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
bwat1009 said:
I had the same thought about moving the apk to the system/app directory and did just that. My expectation was that I would still get the error but for a different app since I just tested with the one that had been throwing the error but it didn't change, still gave the error for the amazon mp3 app even though it was successfully installed in the correct directory. Thanks for the thought though. If you could turn it into a flashable zip, I would be much appreciated. I would love to do that myself but I have no idea how. I know just enough through trial and error (and a lot of forum reading) to be dangerous...
Click to expand...
Click to collapse
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
tehjolly81 said:
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
Click to expand...
Click to collapse
Have you tried using mattlGroff's DROID RAZR M Utility? Worked for me.
Sent from my XT907 using xda premium
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
Alright, thanks for the tip and the link, I will give it a try and let you know...
tehjolly81 said:
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
Click to expand...
Click to collapse
I'm pretty sure you need an unlocked boot loader to downgrade.
netizenmt said:
Have you tried using mattlGroff's DROID RAZR M Utility? Worked for me.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
I did. It fixed an issue where my phone wasn't booting, but it did not revert me to 4.1.1. Just found your comment in the other thread about modifying the xml file.. I'll try that next. Thanks.
patehi nice
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
That worked at getting the system apps that I had removed back into the /syste/app directory and now the update appears to be installing... Will let you know if it works.
*UPDATE*
Well that worked like a charm, update installed successfully, root access maintained, cwm allowed me to prevent reflash of stock recovery so all is right with the world... Thanks you guys!
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
Thank you! I had missing Amazon_IMDb.apk, Facebook.apk, Kindle.apk, PlusOne.apk files. Copied these to my phone and updated successfully!
I have read some articles on here about this but my problem is slightly different. My ROM works fine but when I select to put my phone into recovery mode the fastboot mode text comes up I power my device off and it starts back up in cm 10.2. Since these seems to be a little different than others problems I've read on here I've been hesitant to try any of the solutions. And if it requires me to use a computer I only have access to a mac
So, install Windows on it... or run a live version. Or VM one.
Steamer86 said:
So, install Windows on it... or run a live version. Or VM one.
Click to expand...
Click to collapse
That doesn't answer the problem on my phone.
Are you trying to reboot through the Rom our another app like titanium? Some if the root apps cab tell you if you have a recovery. Maybe the recovery is messed up so it forces to fastboot. Just my thoughts, no expert.
Sent from my VS980 4G using Tapatalk
m.cassedy said:
Are you trying to reboot through the Rom our another app like titanium? Some if the root apps cab tell you if you have a recovery. Maybe the recovery is messed up so it forces to fastboot. Just my thoughts, no expert.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
I am using ROM manager. thats what the problem is im pretty sure is the recovery is messed up. I don't know how to fix it.
Get flashify. Flash twrp or cwm recovery per your variant. They are posted around here on forums. Never flash anything again with ROM manager. It is what blew your recovery. You're lucky your ROM even works.
Didn't know that about Rom manager. Is it just because of our g2 or compatibility with the recovery?
Sent from my VS980 4G using Tapatalk
I'm not sure, I just know it cant flash them right. Never looked into it. Could be due to boot loader problems, partitions, ect. Probably something simple.
I've tried asking this in the q&a section on the main thread but I think I'm being ignored because I'm asking a question about the at&t version inside a Verizon thread. Idk. But I've tried installing hyperdrive rls15 and I follow the instructions on the main page for at&t and I get to where I need to reboot and wait 10 mins. Well it just stays on the splash screen. I've tried repeating the install 4 time's now amd the same results. I found a tooic saying fix permissions but it fails. I'm sorry if this has been asked already. I have looked through several different threads but I may have overlooked it. My phone baseband is I337UCUAMDL im on 4.2.2 and have twrp v2.5.0.2 as my recovery. I've also verified the md5. any suggestions?
I hate to double post but if anyone has any ideas as to why this is happening I'm going to try and redownload and try loki patch I don't know if it's needed but I will try.
motel6man said:
I hate to double post but if anyone has any ideas as to why this is happening I'm going to try and redownload and try loki patch I don't know if it's needed but I will try.
Click to expand...
Click to collapse
Same problem here,
I'm going to try and install a kernel through TWRP. I've tried a fresh root / loki install, same issue.
For me, I remember having to install an AT&T compatibility pack.zip file on previous Hyperdrive releases, like RLS 10.
I tried to install RLS15 and at the very end of install, it says this:
Flashing Kernel
file_getprop: failed to stat"/tmp/aroma/kernel.prop": No such file or
directory
However, for some reason, after trying to install this new release, I was not able to restore data in TWRP from a backup of RLS 10. I was able to restore to a non-rooted backup (i don't know how), and it appears that I am not rooted anymore, and I don't think I have superuser anymore. So, I'm not exactly sure where to start.
Glad to see I'm not the only one this is happening to. Please let me know if you figure it out. I noticed the same thing but thought I seen someone else say that it was nothing.
so i redownloaded all files and nothing. tried loki patch and nothing. tried kt kernel because i seen another post with someone saying it was the only one that worked for them and nothing. im still stuck on splash screen. please if anyone knows how to fix this please let me know im desperate now. i really want to try this rom so any help would be greatly appreciated. thanks
Same here =/
Flashing a kernel before ROM didn't do anything.
I'm starting to think that we don't have Super User installed anymore, I tried re-installing some BackUps (rooted backups)
and TWRP said something like, you don't have SuperUser instyalled, want to install it? *Slide to Install* Phone quickly reboots (not showing any proof of Super User being installed in TWRP emulator) and still no effect.
When I get some time ill look into how to install SuperUser, which I thought was already put on when we root.
Have you tried installing any other ROMS with success?
Are you still on MDL? I am, and im starting to think i need to just go ahead and do the update from AT&T, and then switching over to Safestrap recovery, but i hope i can find another solution before doing all that.
Sent from my SAMSUNG-SGH-I337 using xda premium
d9vabder said:
Same here =/
Flashing a kernel before ROM didn't do anything.
I'm starting to think that we don't have Super User installed anymore, I tried re-installing some BackUps (rooted backups)
and TWRP said something like, you don't have SuperUser instyalled, want to install it? *Slide to Install* Phone quickly reboots (not showing any proof of Super User being installed in TWRP emulator) and still no effect.
When I get some time ill look into how to install SuperUser, which I thought was already put on when we root.
Have you tried installing any other ROMS with success?
Click to expand...
Click to collapse
I haven't tried any other roms yet. I haven't really seen any that I liked.
d9vabder said:
Are you still on MDL? I am, and im starting to think i need to just go ahead and do the update from AT&T, and then switching over to Safestrap recovery, but i hope i can find another solution before doing all that.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I'm still on mdl. I'm going to keep looking around for a solution. Please let us know if you found a way to fix it.
Also heres a screen shot of my info
motel6man said:
I've tried asking this in the q&a section on the main thread but I think I'm being ignored because I'm asking a question about the at&t version inside a Verizon thread. Idk. But I've tried installing hyperdrive rls15 and I follow the instructions on the main page for at&t and I get to where I need to reboot and wait 10 mins. Well it just stays on the splash screen. I've tried repeating the install 4 time's now amd the same results. I found a tooic saying fix permissions but it fails. I'm sorry if this has been asked already. I have looked through several different threads but I may have overlooked it. My phone baseband is I337UCUAMDL im on 4.2.2 and have twrp v2.5.0.2 as my recovery. I've also verified the md5. any suggestions?
Click to expand...
Click to collapse
Are you using Safe strap?
I was having the same problem after like 4 tries i figured out that every time I would download this it would go into the internal memory when it should have gone into the xd. I had to move folders manually. After that everything has been working correctly.
Do you know what folders have to be moved and where?
Sent from my SAMSUNG-SGH-I337 using xda premium
d9vabder said:
Do you know what folders have to be moved and where?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I created a new one on the xd card named it roms so I won't forget.
All I did was go to Mounts in TWRP recovery and mounted my microSD card and this fixed the problem.
Sent from my SAMSUNG-SGH-I337 using xda premium
d9vabder said:
All I did was go to Mounts in TWRP recovery and mounted my microSD card and this fixed the problem.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
cool im going to go try it in a few mins thanks
i tried mounting both internal and external and still nothing can you go through the steps you did from start to finish maybe im missing something
Okay, so the first thing i did was mount my microSD(external sd) then a full wipe. Even though i was mounted to my sd card, i still had to navigate to my internal memory to select the zips i wanted to flash. I first installed an older release of Hyperdrive Rom, and during installation, i selected Full Wipe option again. i also added my AT&T compatibility pack.zip to be flashed right after the ROM. Also, i dont know if this affected anything, but i tried installing the T-Mobile compatibility pack on a previous attempt. I read somewhere where some1 did this and it worked for them, but it didnt work for me until i did another install of RLS15 and the ATT pack.
Hope this can help you
Sent from my SAMSUNG-SGH-I337 using xda premium