yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note II] danxmanly:
Problem solved on my own...

Found out that the only contacts I could assign photos were one's also in my google contacts. Those that were set up just in Deja office would not allow me to edit photos.. period.

I synced all my contacts to google, ( didn't really wanna do that ), but merged them and combined duplicates and now I can update the contact photos.

If a mod wants to delete this thread.. go ahead. It might serve some purpose for those that use Deja Office though.

Cheers..
[AT&T Samsung Galaxy Note II] RichMD:
This brief guide is to help others get Google Wallet working on AOSP based ROMs. There are guides already by Dafoxs and Antiochasylum but they are apparently for Samsung based ROMs and the lib files, etc are incompatible with AOSP based ROMs. Personally, I tried several times and the NFC setting kept getting wiped out so I had to do restores. These instructions are what ManelScout4Life posted and the thread is at his request. All the credit goes to the DEVs that made this possible - I am NOT a developer -

Seriously

... Lastly, the typical disclaimer applies - I take no responsibility for bricking your phone, etc. I highly recommend making a nandroid backup before any mod like this. These instructions worked on JellyBAM 3.2 compiled by ManeelScout4Life - http://xdaforums.com/showthread.php?t=2069164

1) The lib files should not be modified like the posts for the SamSung based ROMs. However, you will need the modified Google Wallet .apk that is included in the zip you can download from their threads. I used the attached file that I downloaded from this thread - http://xdaforums.com/showthread.php?t=2037372&highlight=google+wallet

2) I already had NFC enabled so ensure it is on in settings if you haven't already.

3) You need to modify /system/build.prop. I used Root Explorer (remember to change to RW) and you have to modify three lines. I made a copy of the existing build.prop before editing because you will revert to the existing file once complete to match your actual device.

3a) ro.product.model=Galaxy Nexus

3b) ro.product.name=yakju

3c) ro.product.device=maguro

4) I then rebooted before installing Google Wallet from the Play store. I then opened the app and performed the setup. The other guides mention getting FCs on NFC and to continue on but I never had any and the setup completed. YMMV.

5) Once the setup is complete with the version of the app from the store, you need to replace the app with the modified version that you downloaded in step 1. I used TB to force stop the app before I deleted it from /data/app.

6) I then use Root Explorer again to place the attached apk in /system/app (remember RW). I checked permissions and removed the group write check but again am not certain if that was necessary.

7) I then changed the build.prop.bak file to build.prop so it is back to before you started.

8) Reboot and hopefully it will work.

Hopefully, this helps and is clear.

Note: I see a prompt in the app shown in the attached pic but it will still work. It is really just a warning about a rooted device.
[AT&T Samsung Galaxy Note II] capite:
I pretty much did this, and it didn't work until I fixed permissions on the modded file that I moved to system/apps at the last step, like I saw in the YouTube video
[AT&T Samsung Galaxy Note II] RichMD:
So, I assume you removed the group write permission like I mentioned in step 6 and that fixed it for you? I assume it is the same video referenced in the link I have in step 1. The person checked permissions and removed that one check but he didn't say you had to. I did it anyway and maybe that is why it worked for me the first time that I followed the instructions I listed - from ManelScout4Life.
[AT&T Samsung Galaxy Note II] Moose0704:
Thanks for this!

Sent from my Samsung Galaxy Note II
[AT&T Samsung Galaxy Note II] capite:
Yes

So, I assume you removed the group write permission like I mentioned in step 6 and that fixed it for you? I assume it is the same video referenced in the link I have in step 1. The person checked permissions and removed that one check but he didn't say you had to. I did it anyway and maybe that is why it worked for me the first time that I followed the instructions I listed - from ManelScout4Life.
[AT&T Samsung Galaxy Note II] MonsterBandit:
told me to reset the app...and its hanging at 98%...thoughts?
[AT&T Samsung Galaxy Note II] RichMD:
If you reboot and check the "about device", does it show Galaxy Nexus before you even download the app?

Have you double checked the spelling on the other two lines?

What ROM and version are you on?
[AT&T Samsung Galaxy Note II] crisis187:
All I did was change name, model and device in build prop let me download and install and runs flawless no need for modified app
[AT&T Samsung Galaxy Note II] RichMD:
I assume the reason for the modified app is for it to continue working after you change the build.prop back to an unsupported device. I guess on AOSP ROMs where S-pen apps don't work, then the proper build.prop isn't as important. You will lose access to external sd card possibly and other issues possibly.
[AT&T Samsung Galaxy Note II] crisis187:
I switched back the info seems to work still haven't fully tested yet

**EDIT

After installing multi window support to jelly bear ROM wallet force closes when trying to add account :(
[AT&T Samsung Galaxy Note II] RichMD:
How about if you complete the instructions above - adding the modded app, changing permissions, deleting the downloaded app, etc?
[AT&T Samsung Galaxy Note II] MonsterBandit:
sorry for the delay...yes everything was spelled correctly, said Galaxy Nexus etc etc...I'm running CM10 by madmack...with it hanging i forced out, deleted pushed modded apk fixed perm and rebooted...opened the app and it hung on "setting up google wallet" for a good 15min...so i forced out and left it at that.
[AT&T Samsung Galaxy Note II] RichMD:
With the Galaxy Nexus build.Prop and Google wallet downloaded from the store, the setup needs to complete before you move to the next steps of reverting the build.prop and pushing the modded app. Those steps are to keep the app working without having issues due to a Galaxy Nexus build.prop. I would delete the app, and start over. I assume you never got an email stating you activated wallet.
[AT&T Samsung Galaxy Note II] RichMD:
Also, did you ever use the steps/zip posted by dafoxs or the other thread (forgot the name)? If so, your NFC setting might be gone or you have incompatible lib files, etc. I would revert to the nandroid backup if you made one before following those procedures which are for Samsung based ROMs rather than AOSP/CM10
[AT&T Samsung Galaxy Note II] ManelScout4Life:
Wait. You installed multi window support on jelly beer!?
[AT&T Samsung Galaxy Note II] RichMD:
LOL!
[AT&T Samsung Galaxy Note II] meshuggah_rltw:
Modified build.prop and now my phone won't turn on. Any help?

---------- Post added at 02:37 PM ---------- Previous post was at 02:30 PM ----------

Took out battery, replaced it. Boot to recovery and restored Nandroid. Not sure what went wrong but I think I'll give up hopes of Google Wallet. Made me a little skiddish now.
[AT&T Samsung Galaxy Note II] bofhemeritus:
This method of getting Google Wallet appears to break both Google Now and video output on cm10.1 variants that are running the open source audio hal.

Google Now goes into the 'Didn't catch that, retry?' Loop.

Steps to reproduce:

Install cm10.1 later than 01/26/2013

Allow it to boot and stabilize.

Setup Google Now.

Modify build.props to reflect Galaxy Nexus, yakju, maguro as dictated in OP.

Reboot.

Google Now will now have the 'Didn't catch that' error if you attempt voice recognition.

Sent from my "berry", spelling may vary.
[AT&T Samsung Galaxy Note II] RichMD:
Thanks,

I can't confirm this works on 10.1 (Android 4.2.x) - only confirmed on 4.1.x even though I expect Google Now, etc will be fine after reverting your build.prop. I'm "assuming" Google Wallet will work as indicated in these steps but Google Now, etc may have problems while the bulld.prop stilll indicates the wrong device - temporary until your wallet is working.

However, were you able to get Google Wallet to setup properly?

If you did get it working, did you try changing the build.prop back to original? I don't know if that would solve the Google Now but your steps listed don't indicate that you finished reverting the build.prop.

Please reply with your results for others.
[AT&T Samsung Galaxy Note II] bofhemeritus:
Hello -

I did actually revert the build.props file to the original settings, and Google Now continued to give the same error. I'm about to test it without opening Google now until after the revert and reboot.

Thanks for your help!

If you like my work, donate to the Juvenile Diabetes Research Fund.
[AT&T Samsung Galaxy Note II] ceo.mtcl:
Tried on latest pa. Worked like a charm. You must have done something wrong.
[AT&T Samsung Galaxy Note II] RichMD:
Thanks for the confirmation. I haven't tried 4.2 yet since it appears it is more of a hassle to go back to 4.1.x due to file-system changes. I'm waiting until it is more mature and the Samsung/Touchwiz s-pen functionality is tough to give up on this device.
[AT&T Samsung Galaxy Note II] bofhemeritus:
I can confirm that this is only happening if you open Google Now while the modified build.prop file is in place. Curiously, replacing the build.prop file with an appropriate one didn't correct the issue - but, reflashing and doing this properly according to your directions, and doing nothing other than wallet while the modified build.prop file is in place works like a charm. So, 100% user error on my part. Thanks for the patience!
[AT&T Samsung Galaxy Note II] RichMD:
Glad I could help.
[AT&T Samsung Galaxy Note II] SuperTongue:
Got it to work on my VZW Note II running the CM10.1 nightly. Tried it out today at a local Sheetz outside at the gas pump and it worked perfectly. Unfortunately, it still doesn't work inside at the cash register (it also didn't work on TW ROMs). Assuming this is basically going to work like it did before, it should also work at my local CVS.

I'll check around and see what places near me support it. Any ideas as to why it wouldn't work inside? My old Galaxy Nexus (LTE) worked fine without any required credit prompts, etc.
[AT&T Samsung Galaxy Note II] RichMD:
If it works in some places but not others, I don't know if that is anything that can be fixed on your phone. Are you using the updated version that just came out 1/28?
[AT&T Samsung Galaxy Note II] SuperTongue:
I got the updated version to work when the build.prop was set to Galaxy Nexus but turning it back to the Note 2 would cause it to do the "Device not compatible" error message. So I went ahead and did everything again and put the APK for the older version onto my phone, and it worked from there. Not sure what else I can do, seems like it might just be the type of register.

Quick question: If I'm on an AOSP ROM, is there any downside to keeping my build.prop on the Galaxy Nexus? And would Wallet even work at point of sale when doing so?
[AT&T Samsung Galaxy Note II] RichMD:
If you want the latest version to work then use the APK in this thread by Monaco - http://loadbalancing.modaco.com/dow...roid.apps.walletnfcrel.modaco.1.6-R96-v13.apk

Concerning your question, I'm not certain on this, but for AOSP ROMs I would probably keep Galaxy Nexus since I believe you will have access to some apps in the play store that you wouldn't otherwise. However, you will have some issues if you try to flash a ROM, use Goo Mgr, etc and it checks the device, etc. As long as you know to swap the build.props, you probably are all set. I am currently on a Samsung/Touchwiz ROM and having it set as a Nexus device would affect S-Pen functionality - handwriting recognition, S-Pen widgets (calendar, etc). Since you don't have that on AOSP it is much less of a concern. I don't know what app compatibility you might lose but ask in the thread for the ROM you are running.
[AT&T Samsung Galaxy Note II] SuperTongue:
Nice, thanks for the link. Seems to be working, although I haven't tested a purchase yet. (All I had to do was replace the old APK in system/app with the new one, correct?)

Also, thanks for the info on the build.prop question. Pretty much what I thought, so it doesn't seem too bad to just keep Galaxy Nexus on the build.prop file.
[HTC One X] BlueSingA:
Hey again..

I was hoping my first custom ROM flashing would be successful considering I've read plenty of threads on how to do it and were pretty careful, but that's not the case.

I tried to give Slim Bean a shot, downloaded Slim-endeavoru-3.1.0-OFFICIAL from their page, and Slim_Gapps along with it.

HBOOT is 1.39, CWM is 5.8.4.0

So I did just as instructed, booted into recovery, wiped data, formatted /system, and then flashed Slim Bean, and Gapps after that was done. When I reboot I just get stuck in the Slim Bean loading screen for a while without anything happening. Tried rebooting and re-flashing a couple of times doing the same procedure - but nothing. Can anyone help me out?
[HTC One X] beanbean50:
do u flash the boot.img
[HTC One X] BlueSingA:
boot.img is in the Slim-endeavoru-3.1.0-OFFICIAL.zip file already so I thought if I flashed the whole zip it would flash the boot.img along with it, no?
[HTC One X] jorjino2000:
No, you should flash boot.img via your computer.

Search in this forum how to do it.

Unfortunately in developer's tread for the ROM you choose it is not good explained...
[HTC One X] leonforthewin:
Someone tell me if I am wrong but the reason you have to flash the boot.img separately is because we have not achieved S-OFF with the HTC One X which gives us unbridled access to everything.

Take the boot.img out of the rom '.zip' and put your phone into fastboot mode. Using the command line and fastboot type 'fastboot flash boot boot.img' obviously for this exact command to work the boot.img needs to be in the same folder as fastboot.exe. Otherwise just type the exact location of it.

Your phone should boot if everything else has been done perfectly.
[HTC One X] BlueSingA:
I'll try that right away.
[HTC One X] beanbean50:
and:

fastboot erase cache

fastboot reboot
[HTC One X] leonforthewin:
Thanks, I always forget to do that myself haha
[HTC One X] beanbean50:
correct...!
[HTC One X] BlueSingA:
Okay so I went into fastboot mode, shift-right click on where the fastboot folder on my PC is, opened command prompt (previously pasted the boot.img from Slim Bean to that folder), typed in fastboot flash boot boot.img, fastboot erase cache and fastboot reboot. After reboot I went straight into recovery, flashed the ROM and Gapps, rebooted and now it's stuck HTC's boot screen. :/
[HTC One X] jorjino2000:
With what unzip program you extracted the boot.img?

Try with 7zip...

One more thing- if I remember correct you need to use special boot.img for using 4.1 or 4.2 roms, because they do not work with latest hboots 1.31-39.

Search for such boot.img.
[HTC One X] BlueSingA:
WinRAR. Okay, gonna try with 7zip.. Also, by extracting the boot.img from the zip you guys mean just to extract it or taking it out of the zip completely? Because I removed it from the zip entirely and flashed it via fastboot only.
[HTC One X] leonforthewin:
You'll be fine with WinRAR. Check back on the forum thread page of the rom you downloaded and look for a md5 sum/number. Google MD5 checker or something to that effect and check whether the MD5 checks up. Could be that a few 1's and 0's are out of place.

My other concern is the rom you have flashed. SlimBean – not tried it, I'm guessing it's a light weight Jelly Bean yeah? Are you sure that you have the correct hboot version for Jelly Bean yet? You can't force update all HOX's to Jelly Bean yet.

EDIT: Missed a bit of your post – I'm not aware of the implications but I and many others have always just copied the boot.img not cut. Obviously if you cut it and it gets zipped back up the MD5 will definitely not match. Save yourself a the head ache and download the rom again to be 100%. Delete the old.
[HTC One X] jorjino2000:
Please see here:

Hope this helps you.;)
[HTC One X] BlueSingA:
Okay, checked the MD5 sums and they indeed didn't match.. redownloaded again, and it matched since I didn't cut out the boot.img. I'll try again.

@jorjino can you just give me a really short insight (since I bugged you enough, lol) on what is that kernel supposed to do? And do I flash those modules from fastboot as well?
[HTC One X] jorjino2000:
You have to download the newhboot.img from my previous post, rename it to boot.img and flash it via fastboot and cmd menu your PC. That's all. No more downloads or steps.
[HTC One X] BlueSingA:
Now I'm in a bootloop with the new boot.img... think I'm going to try a different ROM.
[HTC One X] leonforthewin:
I don't wish to be rude but did you ignore the fact that the MD5's didn't match?
[HTC One X] jorjino2000:
Last try with this download:

Do not forget to rename the file to boot.img.
[HTC One X] leonforthewin:
Can you post me the link to the rom you downloaded? I'm looking on their site and there are no current files in the Jelly Bean HTC One X category. They have old unsupported roms for the HTC One X here.. http://www.slimroms.net/index.php/downloads/all/viewcategory/144-endeavoru.
[HTC One X] BlueSingA:
I downloaded 3.1.0 from the link you posted, it's the latest version they released, but they no longer support 4.1.x because they're making some fast progress on 4.2 and according to them 4.1.x is now bugree.
[HTC One X] BlueSingA:
Okay I downloaded IceColdJelly and flashed it successfully. I can't express how grateful I am to the both of you for taking the effort to go through things together with me and enlighten me along the way on how some things should be done. I hope I can repay you one day, but until then I'm happy to chip in some cash if you send me the info in private. Cheers!
[HTC One X] leonforthewin:
Not a problem! Just glad I could help in anyway or form pal. It seems that particular rom had given people problems boot wise, but whatever.

I'm really considering to go over to a AOSP style rom myself – I'm in love with how the notifications work and look. The Sense version although very nice seems somewhat watered down.
[HTC One X] BlueSingA:
Yes I figured the Slim Bean was faulty for giving me headaches even though without the help here I probably wouldn't flash anything successfully.. Thanks again!
[HTC One X] beanbean50:
all's well that ends well :)
[HTC One X] jorjino2000:
I am glad you found a ROM for you.

I had same problems as you couple of days ago when wanted to try non-sense ROM. Sorry, but can not found first the correct boot.img for 4.2...

It's good to know you can relay on this forum and members. ;)

Enjoy your mobile!

Cheers!
[Verizon Samsung Galaxy Note II] Zacedward:
Hi I need to put my verizon note 2 back to stock using odin does anyone have the most recent official firmware that I can use thanks
[Verizon Samsung Galaxy Note II] Its TwiX:
First page on Android Development...

http://xdaforums.com/showthread.php?p=35265728

[ODIN][VRALJB] Restore to Stock

Sent from my Xposed Beans Note 2
[Verizon Samsung Galaxy Note II] Travisdroidx2:
Didnt you already odin back to stock I thought I seen from the link given?

Good luck to the op if you figure it out please share how you got it working thanks!
[Verizon Samsung Galaxy Note II] Zacedward:
I did but i tryed using that triangle away and it brought me back to the screen where it says unatorized software when I did a reboot and I need that firmware again so I can take it out of that unatorized software thing not unless if you know of a way to do it with out having to re dowload the stock firmware again thanks
[Verizon Samsung Galaxy Note II] Travisdroidx2:
Sorry I am new to this device. I was under the impression if you flashed it back to a stock rooted odin then you would have the original firmware and the app should work as advertised. Sorry never used it myself that is why I am curious incase I ever get in your position.
[Verizon Samsung Galaxy Note II] Zacedward:
yah im new to the device and also to rooting and stuff sorry for the dumb questions just want to learn how do do this stuff really interesting by the way do you know if I have to install anything in the pit in odin or just the stock firmware in pda odin thanks
[Verizon Samsung Galaxy Note II] silvershoy2:
did you find out how to fix the problem? I'm having the same one.
[Verizon Samsung Galaxy Note II] Zacedward:
Yah I did I just followed this post and it worked the one below this post tryed to put link in but it didnt work sorry
[Verizon Samsung Galaxy Note II] Travisdroidx2:
. Great to hear you are good now counter and everything reads good now?
[Verizon Samsung Galaxy Note II] Zacedward:
I just followed that post and it worked only took like 7 min to fix
[Verizon Samsung Galaxy Note II] silvershoy2:
Did the file download quickly for you? Mine isn't making any progress for some reason... It's been stuck at 0 for about an half hour. and How did the link work for you? Could one of you upload it to dropbox or something else for me please?
[Verizon Samsung Galaxy Note II] Zacedward:
Everything except it still says 1 flash count so I am going to unlock bootloader tomorrow then try it I was reading the triangle away description in the play store and it says the bootloader has to be unlocked befire my bootloader was not unlocked so I think thats why my phone did that
[Verizon Samsung Galaxy Note II] Zacedward:
Mine eent somewhat quick took like 45 min to download
[Acer Iconia A500] cebbes30:
Please

I tried several times to ask on this forum if someone can help me, but no luck so far i am verry desperad now

I have install Skrilax CZ bootloader V8 on my tab, but thats all i dont now what i need to do now to install a custom rom, i have put the update file in to the sd kart but it wont install.

I have this option only

option

Reboot

Fastboot Mode

Boot Primary Kernel Image

Boot Secondary Kernel Image

Boot Recovery

Set Boot Secondary kernel Image

Set Debug mode on

Wipe Cache.

So cany anyone tel me what i must do to root and install CWM recovery

so i can install then after custom roms?

Is ther no tutorial from heren to folow!!
[Acer Iconia A500] dibb_nz:
Please don't double post it gets confusing -

remember, this is the holiday season and alot of us are having a break and spending time with our long neglected family members, we can't be around here as much as we would like....:(

Yes there are guides on using fastboot, skrilax's bootloader thread for one...

PLEASE don't flash an update.zip it doesnt work that way, you'll end up stuck again

you should read the first 2 guides linked in my sig..
[Acer Iconia A500] Nadaaaaa:
I too need help exactly on this point

I have not the slightest clue what to do and i do not think this is a duplicated post.

I spent days to come at this point and i don't want to **** things up.

I red your posts dibb_nz and it just gets more confusing

You write in this post :

PLEASE don't flash an update.zip it doesnt work that way, you'll end up stuck again

and then you write here: http://xdaforums.com/showthread.php?t=2049778

Have your Custom Rom downloaded and copied to your External SD Card ready to install immediatelyafter flashing skrilax's patched bootloader

So is it too hard for someone to tell what to do here to install a custom rom ?!

P.S. I also got [ ERROR: Invalid primary (LNX) kernel image ] on my screen.

http://s15.postimg.org/e02avn6aj/IMG_0020.jpg

something to worry about ?
[Acer Iconia A500] Heisenberg:
Thread closed, duplicate of this one:

http://xdaforums.com/showthread.php?t=2076510
[Galaxy S III Q&A, Help & Troubleshooting] goodknight001:
Verizon S3 is rooted and running pac rom. Wanted to try cm10.1 with 4.2 gapps. Backed up, wiped and also WIPED CACHE PARTITION FOR THE FIRST TIME. then i installed the new rom and now i am without service even if i restore my backups. what did i do and how do i fix it?
[Galaxy S III Q&A, Help & Troubleshooting] alaska_ryder:
No data service

I am having same problem with neat rom. I have tried different modems and kernels but all still do not give me data service.
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
This is I9300 forum .

jje