yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Neverendingxsin:
Nfl mobile hasn't worked on aosp roms in a very long time.
[Verizon Samsung Galaxy S III] jkbane:
I didn't know that.
[Verizon Samsung Galaxy S III] soopervoo:
running Synergy Rom and NFL app works
[Verizon Samsung Galaxy S III] ekklesiaillusion:
Your still on a stock base.

---------- Post added at 01:43 AM ---------- Previous post was at 01:42 AM ----------

You need to go into a stock touchwiz Rom and download it. Backup with data on titanium backup. Load your AOSP/AOKP ROM and restore the app and data. Will work.
[Verizon Samsung Galaxy S III] sebastianraven:
I came across the same issue with a few different ROMS. It depends on the Kernel. I'm currently running JellyWiz Hybrid RLS7.

The best way to get it and let's say GPS to work is to flash and go back to bone stock in Odin.

Set up your phone as you normally would. DL the NFL app and run it as normal...

Then root your device and it should work no problem.
[Verizon Samsung Galaxy S III] hypertek:
maybe you can open up your build prop and change it to match a stock one
[Verizon Samsung Galaxy S III] kintwofan:
It's just actually in the build prop. There are a combination if build prop and supporting apps that are needed. I know in is the Verizon login agent, but I'm not sure on the others.
[Verizon Samsung Galaxy S III] coldhardtruth:
Flash this zip in CWR. It will add the Verizon login app. Reboot and launch NFL Mobile. Should be good to go

http://db.tt/kuw82sKJ
[Verizon Samsung Galaxy S III] jkbane:
This works with AOKP ROMs?
[Verizon Samsung Galaxy S III] Neverendingxsin:
Works on aosp roms?
[Verizon Samsung Galaxy S III] gqser:
running cm10 nightly and this worked for me, big thank you :good:
[Verizon Samsung Galaxy S III] j0hnZ:
Thanks for posting the app, but it's telling me nothing is there.
[Verizon Samsung Galaxy S III] Zalithian:
http://dl.dropbox.com/u/8949252/jellybelly-myverizonapps.zip

Here you go. A reupload.
[Verizon Samsung Galaxy S III] j0hnZ:
Thanks it worked, I guess I needed the older my Verizon app cause the one on the market didn't work before. All is well, no more flashing a different Rom to watch the game.
[Verizon Samsung Galaxy S III] sage3:
Anyone know of a way to tweak the apk to allow hdmi out!?
[Verizon Samsung Galaxy S III] screwyluie:
You are my hero! This should be in a sticky
[Verizon Samsung Galaxy S III] jackmei2:
thanks! this method worked for me. I tried installing the verizon sign on apk and that didn't work, but this flashable zip worked like a charm on AOKP
[General Questions and Answers] A_Button117:
What is the safest over clock spled to set my phone at?
[Samsung Galaxy Nexus] envidia:
Hi! The story goes like this:

A friend of mine gave me a bricked Galaxy Nexus to resurrect: the phone keeps playing the colors animations and never ends booting up, but I can enter fastboot and recovery modes.

Things I tried:

1) efrant guide to return to stock.

Here is the big problem: after doing the 'fastboot oem unlock', at the bottom it appears in red text 'LOCK STATE - UNLOCKED'. But then I do a 'fastboot reboot-bootloader' and it changes to LOCKED again, so I can't complete the steps because of this. I think this is what is causing all the troubles.

2) Flash JB package with Odin.

3) Flash ICS package with Odin.

This last two completed successfully, but the phone is having the same problem, there were no changes. The bootloader version is always PRIMEKK15.

Any hints? Maybe it's a hardware problem and there's no software solution? It's a shame, because I can access fastboot and recovery, but everything I tried doesn't seem to work.

Big thanks.
[Samsung Galaxy Nexus] beekay201:
seems to me that the unlock token is not sticking somehow. have you tried relocking it right after you unlock it? for example, can you 'fastboot boot customrecovery.img' and enter cwm after you unlock?

sent from my i9250
[Samsung Galaxy Nexus] envidia:
Yes, if I do:

# fastboot oem unlock

# fastboot boot cwm-recovery.img

It enters CWM just fine. The problems seems to be that the changes are not persistent, or at least that's what it shows the info in the fastboot mode. Even after all the things I flashed, the bootloader never changed.

I will be trying to relock it right after unlocking it and I'll post the results.

Thanks.
[Samsung Galaxy Nexus] Feinar:
You can try to use the GALAXY NEXUS TOOLKIT V7.8. It has many helpful features for unlocking, rooting, flashing factory images, or separate radio\bootloader images. User-friendly GUI are included.
[Samsung Galaxy Nexus] efrant:
He already knows how to use fastboot. There is no need for him to use a toolkit which does nothing different aside from hide the commands from you...
[Samsung Galaxy Nexus] Herman76:
Guess he have his 10 posts now so he won't post for a while ^^
[Samsung Galaxy Nexus] Mach3.2:
And don't recommend toolkits to people asking for help, 3/4 of the time they are clueless, recommending it to them will just make them sink deeper in to a god knows how deep pool of sh*t. No offence to you though, just don't recommend toolkits next time:)
[Samsung Galaxy Nexus] envidia:
Thanks guys.

I'm reading that people recommend doing an OMAP flash, but only when the phone is completely dead. I can get to fastboot / Odin mode, is there anything that I should try before doing an OMAP flash?
[Samsung Galaxy Nexus] beekay201:
i think we already ran out of options. you could try omapflash... although i still think it's an issue with the unlock token/nand.
[Samsung Galaxy Nexus] envidia:
I've just tried that and it works as expected.

# fastboot oem unlock

*It says the bootloader is unlocked in the phone display*

# fastboot oem lock

*It says the bootloader is locked again in the phone display*

Then I tried flashing the ICL53F 4.0.2 stock image through fastboot, because it uses the bootloader that I have at the moment. It didn't work, it's still stuck at the animation colors. Look at the results, it all seems ok:

[B]# ./fastboot oem unlock[/B]
...
OKAY [ 10.102s]
[B]# ./fastboot -w update image-yakju-icl53f.zip[/B]
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEKK15
Baseband Version.....: I9250XXKK6
Serial Number........: 0149C25E0200A00B
--------------------------------------------
checking product...
OKAY [ 0.007s]
checking version-bootloader...
OKAY [ 0.008s]
checking version-baseband...
OKAY [ 0.008s]
sending 'boot' (4074 KB)...
OKAY [ 0.436s]
writing 'boot'...
OKAY [ 2.510s]
sending 'recovery' (4406 KB)...
OKAY [ 0.624s]
writing 'recovery'...
OKAY [ 4.459s]
sending 'system' (317594 KB)...
OKAY [ 40.473s]
writing 'system'...
OKAY [1387.576s]
erasing 'userdata'...
OKAY [ 0.035s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14539534336
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3549691
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/887696 inodes and 97200/3549691 blocks
sending 'userdata' (137559 KB)...
writing 'userdata'...
OKAY [262.626s]
erasing 'cache'...
OKAY [ 0.007s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 452984832
Block size: 4096
Blocks per group: 32768
Inodes per group: 6912
Inode size: 256
Journal blocks: 1728
Label:
Blocks: 110592
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27648 inodes and 3566/110592 blocks
sending 'cache' (8832 KB)...
writing 'cache'...
OKAY [ 15.788s]
rebooting...

finished. total time: 1714.590s

The only thing that caught my attention is the fact that the process lasted almost 29 minutes. I don't know if that's normal.
[Samsung Galaxy Nexus] efrant:
Follow the steps in my guide here (instead of using the fastboot update command), with the following exception: instead of doing step 10, replace that step with: fastboot erase userdata
[Samsung Galaxy Nexus] envidia:
I did:

[B]# ./fastboot oem unlock[/B]
...
OKAY [ 9.623s]
finished. total time: 9.623s
[B]# ./fastboot flash bootloader bootloader-maguro-primekk15.img[/B]
sending 'bootloader' (2308 KB)...
OKAY [ 0.324s]
writing 'bootloader'...
OKAY [ 7.972s]
finished. total time: 8.296s
[B]# ./fastboot flash radio radio-maguro-i9250xxkk6.img[/B]
sending 'radio' (12288 KB)...
OKAY [ 1.739s]
writing 'radio'...
OKAY [ 4.395s]
finished. total time: 6.134s
[B]# ./fastboot flash system image-yakju-icl53f/system.img[/B]
sending 'system' (317594 KB)...
OKAY [ 43.399s]
writing 'system'...
OKAY [1387.456s]
finished. total time: 1430.855s
[B]# ./fastboot erase userdata[/B]
erasing 'userdata'...
OKAY [ 0.033s]
finished. total time: 0.033s
[B]# ./fastboot flash boot image-yakju-icl53f/boot.img[/B]
sending 'boot' (4074 KB)...
OKAY [ 0.568s]
writing 'boot'...
OKAY [ 4.384s]
finished. total time: 4.953s
[B]# ./fastboot flash recovery image-yakju-icl53f/recovery.img[/B]
sending 'recovery' (4406 KB)...
OKAY [ 0.620s]
writing 'recovery'...
OKAY [ 4.458s]
finished. total time: 5.079s
[B]# ./fastboot erase cache[/B]
erasing 'cache'...
OKAY [ 0.007s]
finished. total time: 0.007s
[B]# ./fastboot reboot[/B]
rebooting...

finished. total time: 0.006s

It isn't working, same result as always.

I'm new to this Android world, so I have to ask: could CWM or similar custom recovery offer some additional method to try? Because I can boot CWM recovery, but I don't know if can do something from there.

Thank you guys.
[Samsung Galaxy Nexus] beekay201:
can we get a logcat of the bootloop?

anyways, if you flash cwm, does it stick? it doesnt, i assume. be reminded that /system/recovery-from-boot.p needs to be renamed or removed, if exists.

imo, using cwm to flash a rom won't do much here, given the current situation.

sent from my i9250
[Samsung Galaxy Nexus] envidia:
About the logcat, I've read that you have to use adb, but it never worked for me. When I do:

[B]# ./adb devices[/B]
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
<empty space here>

I can boot the CWM recovery. If I flash it, it doesn't stick. I don't know how to delete /system/recovery-from-boot.p, do I need adb?

I tried the OMAP flash, then tried to unlock the bootloader and after the fastboot reboot-bootloader, it gets locked again.

I'm reading lots of threads with bricked Galaxy Nexus, but never one with this behavior.
[Samsung Galaxy Nexus] The Gingerbread Man:
Only thing I can suggest is try fast booting a different bootloader version to a newer one.

http://xdaforums.com/showthread.php?t=1587498

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] beekay201:
it seems it always stays on kk15

sent from my i9250
[Samsung Galaxy Nexus] The Gingerbread Man:
OK then odd, the other thing I'd suggest is go to the Google factory image website https://developers.google.com/android/nexus/images then using mskips tool kit there is a feature to turn the .IMG into .tar (I think its .tar?) which can then be using in Odin mode instead. Flashing this way is different than fast boot and the Google factory images contain boot loader and radio and obviously a ROM.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] efrant:
That is because your ADB driver is not installed. It seems like you have the fastboot driver installed, but not the ADB driver.

Since you've already tried fastboot, odin and omapflash, I doubt anything else will work. The only other thing I can think of that could possibly work is for flash the bootloader using dd, but I doubt it. Most likely a hardware issue.
[Samsung Galaxy Nexus] envidia:
Thanks, The Gingerbread Man. I've already tried flashing stock images through Odin and there's no change at all.

I'm on Linux, I thought that if fastboot is working, adb should work as well. I'm trying adb with the phone in fastboot mode, should I try in Odin or recovery mode?

Let's suppose the problem is the NAND flash memory, is it replaceable? Of course I'm not doing it myself, but I'm thinking if the phone has to be replaced by a new one, or can be repaired.
[Samsung Galaxy Nexus] efrant:
Oops, forgot you were using linux (so no drivers required). But ADB should not work your device is booted in fastboot mode or odin mode. It will only work when you are booted into recovery or into Android.

Not really. You would need to replace the motherboard as a whole.
[Samsung Galaxy Nexus] envidia:
Hey, thanks again.

I'm with the phone in the 'Android system recovery <3e>' mode right now. Every time I enter this mode, below the blue options, it appears the following text in yellow:

Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
Removing unneeded files...
Patching system files...
Patching boot image...
Unpacking new files...
Unpacking new recovery...
Symlinks and permissions...
Random offset: 0x2a7
Writing bootloader...
Patching radio...
Fixing fs_size in crypto footer...
Patching remaining system files...

Is this normal?

By the way, adb isn't working in this mode either.
[Samsung Galaxy Nexus] envidia:
From the recovery menu, if enter 'apply update from cache' I see there's a file called:

5a81769b6d01.signed-yakju-IMM76I-from-ICL53F.5a81769b.zip

I think this is the file that caused the brick in the first place.
[Samsung Galaxy Nexus] envidia:
Whatever change I make to the filesystem, it isn't persistent. Example:

[B]~ # mount[/B]
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/platform/omap/omap_hsmmc.0/by-name/system on /system type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata on /data type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache on /cache type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered)
[B]~ # umount /cache/[/B]
[B]~ # ls /cache/[/B]
[B]~ # which mount[/B]
/sbin/mount
[B]~ # /system/bin/mount -o rw -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache/[/B]
[B]~ # ls /cache/[/B]
5a81769b6d01.signed-yakju-IMM76I-from-ICL53F.5a81769b.zip
lost+found
recovery
[B]~ # /system/bin/rm /cache/5a81769b6d01.signed-yakju-IMM76I-from-ICL53F.5a81769b.zip [/B]
[B]~ # /system/bin/sync[/B]
[B]~ # ls /cache/[/B]
lost+found recovery
[B]~ # /system/bin/umount /cache/[/B]
[B]~ # ls /cache/[/B]
[B]~ # /system/bin/mount -o rw -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache/[/B]
[B]~ # ls /cache/[/B]
5a81769b6d01.signed-yakju-IMM76I-from-ICL53F.5a81769b.zip[COLOR="Red"] <-- it comes back after being removed[/COLOR]
lost+found
recovery
[Samsung Galaxy Nexus] efrant:
Try this:

1) Download the LC03 bootloader (CWM-flashable zip) from here and rename it to lc03.zip

2) Download CWM 5.5.0.2 recovery from here and rename it to cwm.img

3) Type: fastboot boot cwm.img

4) Push the bootloader to your device: adb push lc03.zip /sdcard/

5) Navigate the menus in CWM on your device to "flash update from zip" or whatever it is called, and flash the bootloader.

6) Reboot and see if you have a new bootloader.
[Samsung Galaxy Nexus] airtime82:
also if this doesnt work and I know this will sound stupid but once and a while when I odin back to stock my phone bootloops so what I do is while its bootlooping I pull the battery, reinsert it, Start the phone at the fastboot screen boot into stock recovery, factory reset and reboot from there and it works again.
[Samsung Galaxy Nexus] envidia:
The CWM 5.5.0.2 doesn't boot. It gets stuck at the android robot with the red triangle. If I try with the last version of CMW, it says:

-- Installing: /sdcard/lc03.zip
Finding update package...
I:Update location: /sdcard/lc03.zip
I:using /data/media for /sdcard/lc03.zip.
Opening update package...
Installing update...
Installation aborted.

I tried that multiple times.

Thanks guys. I think there's no more things to try. It's a mystery what happened to this phone.
[Samsung Galaxy Nexus] airtime82:
Well if you can get into fast boot, get into recovery and Odin recognizes I think there has to be someone that can help on here. Did you post on rootz?

---------- Post added at 09:28 PM ---------- Previous post was at 09:07 PM ----------

does this thread help at all? cant hurt http://xdaforums.com/showthread.php?t=1760787
[Samsung Galaxy Nexus] envidia:
Thanks for your help, airtime82. I already tried the omapflash.

If we couldn't find a solution here in XDA, I think there's no possible software solution. This has to be a hardware problem. The Galaxy Nexus is sometimes called 'unbrickable', but this time it is bricked, in a weird way.
[Samsung Galaxy Nexus] efrant:
It generally is "unbrickable" . But if you have a hardware issue, you have a hardware issue. It's not related to you "bricking" your device.
[Samsung Galaxy Nexus] envidia:
Yes, I understand that. But this seems to be SO software related that is hard for me to accept it.

Thank you all for the help. I will take the phone to a service center and see what they can do. I live in Buenos Aires, where the phone was never officially released, so I don't know what will happen.
[Samsung Galaxy Nexus] beekay201:
@envidia, what about twrp?

this is a long shot, and may not even be the right direction, but did your friend encrypt the device?

sent from my i9250
[Samsung Galaxy Nexus] envidia:
I'll try with TWRP.

About the possibility of the device being encrypted, I don't think so. Mi friend isn't an advanced user, and I could access all the folders and files through adb.
[Thinkpad Tablet General] snappy2244:
Hello All,

I am in a real bind here with my Thinkpad tablet. Lets just say i should have left well enough alone. Anyway, i have the

183925U tablet with A310_02_0039_0089_US that i originally rooted. I used titanium backup to remove some apps. When i

tried to update to ICS, it failed. At the time i read some forums and they said remove root with OTA and then update and

then use OTA to get root back. Tried that and it failed. I got a brilliant idea to remove root and do a factory restore

to hopefully get ICS to load. Now i have no root, cant downlaod anything cause i cant update, cant sideload and cant get

root back.

The update fails with assert check and goes on to say Music.apk cannot be found. I looked into how to reload or even copy

that file to the system but no matter what i try i get "Read Only File System" and i cant get past this. adb push does

nothing. i can push to /data/local but cant do anything with it from there

i can do the following:

adb shell

$su

#

and from there i have tried the mount -o rw remount /system and it seems to accept the command but the system wont let me

move or copy with mv or cat to the /system directory. Is there any way i can get past this? I really just want ICS stock

no root. Please help if you can. I am new so please be gentle and if you wouldnt mind spelling out any commands for me.

Thanks to anyone who can help me. Have a nice day
[Defy Themes and Apps] drgopi1234:
please some one port beautiful miui boss ios v4/jb theme to miui gb please
[7" Kindle Fire HD General] Ichigo:
Once(if) it gets a custom recovery and bootloader, and gets jellybean ROMs, its going to be awesome.

Sent from my Kindle Fire
[7" Kindle Fire HD General] longthinkzhang:
:good: Good Decision
[7" Kindle Fire HD General] jzen:
I also have a Nexus 7, last week it started having whiteout and washed out screen/collor issues. Its been over a month so not sure what to do with it now, but I have really been loving my rooted kindle fire hd with google play store and apps :)
[7" Kindle Fire HD General] angellsl:
Then I'm going to buy one
[7" Kindle Fire HD General] wrexus:
I sold my original Kindle Fire to get the Nexus 7. But after going through 2 units, I finally returned it due to hardware failure issues and decided to wait. When the new Kindle Fire HD was announced, I was so excited I ordered the 7 inch model even though I also ordered the 8.9 inch model. For some reason, possibly due to how well they are built, the Kindle Fires hold their value very well. I'm not worried at all about re selling the 7 once I get the 8.9.
[7" Kindle Fire HD General] vzwty:
This applies to me also. I just traded my Nexus 7 for an unopened Fire HD plus $40. My Nexus had similar issues to yours. So far I'm very pleased with my decision. You can have a home screen if you install ADW launcher. It's the only launcher I could get to work. If you hit the home button it does not give you the option to choose a new launcher, it defaults to the Amazon launcher. Also, the Kindle app won't open from ADW. I made ADW a favorite and avoid the home button unless I need to get to my Kindle App. Not the ideal situation but gives you the option to not use the carousel, change the wallpaper, use widgets, etc.

Once CM10 is out for the Fire HD it will make things even better.
[7" Kindle Fire HD General] Devinchang:
Good!
[7" Kindle Fire HD General] aydjc:
Thank you for your sharing, I need it!
[7" Kindle Fire HD General] Ravynmagi:
Another thing I'm liking about the Kindle Fire HD is it's soft keys. I side loaded Dolphin and enabled full screen mode and I really have FULL SCREEN. I love how the soft keys minimize to a small little overlapping tab on the edge. I have so much screen space for viewing pages. The Nexus 7 has those huge honking ever present soft keys that rarely go away.
[7" Kindle Fire HD General] asrr62:
I am on the same boat. Nexus 7 would be awesome it it wasn't for the build quality. I am thinking about the nook HD+, it sounds awesome.
[7" Kindle Fire HD General] fattire:
KFHD = locked. N7 = unlockable

Good luck with CM10 on the KFHD. The bootloader is locked. It's not necessarily impossible to work around it, but will be a major headache/inconvenience, and many CM folk I know are steering clear just on principal.
[7" Kindle Fire HD General] Ichigo:
Its not impossible for amazon to do it. But there's no chance they will.

Sent from my Kindle Fire
[7" Kindle Fire HD General] Tswig:
im trying to do something similar to what u did.is there a way i can side load google music w/o rooting?
[7" Kindle Fire HD General] Ravynmagi:
I backed up the Google Music app from my Nexus 7 using ES File Manager. Then copied it to my Fire HD and installed it. It seems to be working just fine, I'm streaming my music from Google.
[7" Kindle Fire HD General] lochana:
I was on the same boat as you. After returning two nexus 7s due to raised screen, I was hoping for a better build 7 inch tablet. I end up buying an excite 7.7. I was able to get the excite for 360$. I think it is a good deal considering the superb screen, build quality and features....
[7" Kindle Fire HD General] Melodycd:
Hi! I did get my KFHD a week ago. I wanted to buy Nexus 7, but Fire HD looks better for the same price. Rooted, G Play, all work awesome! The only problem is - I can't start any launcher from the google market. It is downloaded, installed, but there is NO open button and it doesn't show up in apps... What am i doing wrong?
[7" Kindle Fire HD General] Ravynmagi:
I've heard only ADW Launcher seems to work. And if you press the Home button you'll go back to the Amazon launcher instead, so I guess you need to put ADW Launcher in your favorites and avoid hitting the home buttons. That sounds like a PITA to me, so I haven't messed with it myself.
[7" Kindle Fire HD General] alkemist80:
If you do root, you can put go launcher ex apk in the system/app folder, install and reboot. Go launcher will work and you can set it to default, the kindle will ask what you want to use when it boots from that restart. Then you'll be good to go. I had it working perfect on my KFHD but its back in the box and going to UPS tomorrow.
[7" Kindle Fire HD General] vzwty:
its really not that big of a pain
[7" Kindle Fire HD General] nooktablet:
so you guys are using amazon's hardware with google's software?

lol the nook hd+ looks awesome too, sadly it doesn't not have a front camera,

why?
[7" Kindle Fire HD General] Melodycd:
Why do you send it back?