Been trying to access some info from the "My Account" app and says my phone model is not supported. I think its due to the change in model number in the about phone section. Anyway to change it back to what it was before?
Btw im running CM 5.0.8
Edit: Reason for editing: On the "Model Number" part, its says HTC Dream, I wanted to change the text string back to what it use to be so I fully use the my account app.
old post, but I would like to know where/what I need to do to change the model also. I can't update via my sammy i9000 via Kies, because it's reading as a GT-I9000 after installing a Euro 2.2 ROM, when it's infact a GT-I9000T.. which Kies now has a New Zealand 2.2 update for. The issue is the 3G support of the Euro ROM and the fact it makes my screen on first power up do the rainbow snow deal. I'm hoping the NZ ROM for the actual 9000T will fix this... but I need to change the device model # to test.
The Kies registry patch trick didn't work for me at all. I would run the app, it would appear to change the registry keys, but Kies would either add another set of 3 keys (4, 5, 6) or just change the 1, 2, 3 modified reg keys to what the phone is reporting instead of keeping the modified info.
Any help would be greatly appreciated
/system/build.prop
i am carllindsay, i was surfing to know that, thanks for sharing a nice thread.
dhkr123 said:
/system/build.prop
Click to expand...
Click to collapse
How do you open /system/build.prop? I use ASTRO and can't open it. Is there any editing app that can open any extension?
general-tso said:
How do you open /system/build.prop? I use ASTRO and can't open it. Is there any editing app that can open any extension?
Click to expand...
Click to collapse
You could rename it to .txt, edit, change to .prop.
Or you could adb pull, edit, push ect.
never mind. I have SGS Tools app that lets me edit /system/build.prop without renaming it. SGS Tools is available on the Market for free.
for those who don't know what SGS Tools is, you're missing a lot! Try it.
general-tso said:
for those who don't know what SGS Tools is, you're missing a lot! Try it.
Click to expand...
Click to collapse
For anyone who actually knows how to use a computer.... no, they're not missing ANYTHING. The terminal is FAR more powerful than any nonsense like that.
Related
I recently purchased an OKTA touch in New Zealand which is basicaly a vogue with slightly edited operating system.
I have been trying to get it into diagnostic mode to use cdma workshop on it but the okta phone function doesnt go into it when i dial ##DIAG# or ##DIAG[send]
Is there a program I can download to put it into diagnostic mode? I updated the operating system to the latest altel but the okta keypad stayed.
Ok all fixed now, just had to download a program called nOpen.exe and open the file /Windows/DmRouter.exe with the command line /DIAG
for some reason this file would not appear when i tried to find it manually
ok I found the program online
and it worked on winmo
buzzybee4444 said:
Ok all fixed now, just had to download a program called nOpen.exe and open the file /Windows/DmRouter.exe with the command line /DIAG
for some reason this file would not appear when i tried to find it manually
Click to expand...
Click to collapse
I was gonna suggest to flash a rom that had Phone Codes in it. Not being able to use the codes is normally for 2 reasons:
1. Skinned dialer
2. Not having the carrier's provisioning installed.
Glad you got it working though.
Check this out!
sorry thought this was android
medjai said:
You may want to take a look at my post. This will virtually work with any device who's kernel source is released . http://forum.xda-developers.com/showthread.php?t=948360
Click to expand...
Click to collapse
Erm - he's using WinMo.
Seems there is an issue affecting most devices when ro.serialno is not set in build.prop.
ANDROID_ID is generated by running the ro.serialno through a command, if not set then ANDROID_ID is always the same. Some apps on the market, for me it is "Fast Web Installer" from appbrain that is giving me an issue because my ANDROID_ID is currently the magic number = 9774d56d682e549c
Seems some other developers use the Android_ID to identify handsets on the market when apps are installed. There is an app on the Market to view the android_id and if rooted be able to change it.
I'm about to update my build.prop with my device serial number and see if I get a true random ANDROID_ID
I'm currently using Cog 2.2 beta7
Could someone check the build.prop file on a stock ROM? By stock I mean truly stock because I believe the handsets from the factory have this set, but when we flash the JF6 it no longer has the ro.serialno.
Edit: http://code.google.com/p/android/issues/detail?id=10639
looks like adding ro.serialno does not help us since the ROMs we use are not true first boots, the system.db already has the value set so it doesn't generate a new one.
next I will try removing the ANDROID_ID from the system.db and see if that fixes it...
im bookmarking this, it would really be a big help
well i found an app that allows you to change it, but can't find a way to set it to what it should be from factory using serial number.
would be easy to get an app to use same method and just ask for your serialno if not set
turns out cynogen had the same issue since the ro.serialno was not set, they added code recently to generate based on serialno and first boot time so it would have seed data even if serialno was not set.
http://github.com/CyanogenMod/andro...mmit/81ed751a1dcf1e7c722db2cdded38bef4308a1c5
so something in samsungs source may be goofed cause they don't seem be pulling ro.serialno, i set android_id to "" in the database and rebooted, it stayed the same.
I then deleted the entry all together and rebooted and it went back to the magic number.
edit: well checked with getprop and ro.serialno is blank even though I set it in build.prop
I'm done tinkering for tonight, I changed my value manually for now to a randomly generated hex value and my "fast web installer" is working fine now.
Does seem to be an issue though, and not sure the code solution on cyanogen's site is best way either. They are looking at using ro.serial and time to generate random just in case the serial is blank.
If your someone who purchases a lot of apps, then it might be a good idea to make sure your android_id is random and then keep it so you can restore it later if needed. Some app developers use this to identify the end user.
If you go back to 2.1 you can retrieve your original Android ID and manually set it in Froyo
I did a fresh restore to JF6 and it was set to a unique one, then done a restore to a nandroid I had from an old 2.1 install and it was the same ID. So hopefully that one is unique to my device
well i installed the froyo leak on my gf's captivate after i had zero problems after like a week or 2....now she needs an app in the market and calls me complaining about how she cant find it. Whoops, forgot to tell her about that little tid bit!
Any work on at least a temporary fix? I was going to just tell her to sideload the app using sideload wonder machine, but i can't find an .apk for a free app on the market!!
well i installed the froyo leak on my gf's captivate after i had zero problems after like a week or 2....now she needs an app in the market and calls me complaining about how she cant find it.
Click to expand...
Click to collapse
This is normal for pre-release firmware.
1. Root her phone.
2. Edit her /system/build.prop file
3. Find the line that starts with this: ro.build.fingerprint=
4. Make it say this: ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/231334:user/release-keys
Save, exit, reboot.
The fingerprint line is carrier agnostic. Android Market just looks for known (to Google) fingerprints. If you have a known good one, you get to see all the protected apps that your unknown fingerprint prevented you from seeing.
Joe1981AL said:
well i found an app that allows you to change it, but can't find a way to set it to what it should be from factory using serial number.
would be easy to get an app to use same method and just ask for your serialno if not set
turns out cynogen had the same issue since the ro.serialno was not set, they added code recently to generate based on serialno and first boot time so it would have seed data even if serialno was not set.
Click to expand...
Click to collapse
hi im curious about the name of the app that let you change the android id can you post a link for it or the name of the app ty
Edit: found an app but havent tried it heres the link anyone who rooted the phone with busybox can try this http://adaptiveeng.blogspot.com/2010/10/android-id-changer.html
I am having this same problem. I wanted to use the fast web installer but it wouldn't work as well.
Has anyone figured how to change it so this will work?
jdsemler said:
This is normal for pre-release firmware.
1. Root her phone.
2. Edit her /system/build.prop file
3. Find the line that starts with this: ro.build.fingerprint=
4. Make it say this: ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/231334:user/release-keys
Save, exit, reboot.
The fingerprint line is carrier agnostic. Android Market just looks for known (to Google) fingerprints. If you have a known good one, you get to see all the protected apps that your unknown fingerprint prevented you from seeing.
Click to expand...
Click to collapse
thats great! thank you for the quick reply! just tried this on my phone and it worked great. I knew it was a common problem but never found a real answer on what to do. It's just too bad she lives 6 hours from me and i'm not sure i feel like writing her a step by step (as in button by button) guide for her to do this. She will live without the app for another week or so haha.
I was hoping that there would be an app on the market that would allow me to put her a random android id like the above guy stated. Anyways...thanks again.
I'm not running Cog2.2b7, but it seems to me you could use this method to generate yourself a unique Android ID using the emulator option under Make a new androidID with the Emulator. Then, using this command to pull the unique ID off the emulated Android device:
adb shell sqlite3 /data/data/com.google.android.googleapps/databases/accounts.db "select * from meta";
Once you have the Android ID, close out the emulator, and put this Android ID into your phone.
Like I said, I'm not running that version of Cognition, but give this a shot.
i am curious as to what the difference is between what i did (modifying the build.prop file as stated a few posts up) and getting my unique android ID and insterting it back into the phone while running froyo? I can see the apps on the market, was that not the issue at hand with the android ID?
The Android ID is a unique identifier for your phone.
The fingerprint is more of a signature to tell the Android Market that you have a known good firmware and what firmware version it is (2.2 in this case). When you have an approved signature, you get to see apps that were promoted to the market with the "Protected" flag enabled. If you do not have an approved signature, it is as if those apps aren't there.
Need clarafication
Hi Im interested in this ID changing process, but have a question about it. Now does this also fix other issues with 2.2 like not being able to log in to certain apps because the ID of your phone has been changed? I have a captivate but I have been reading thru the threads and noticed a lot of devices, well the ones who upgraded to 2.2, are having the same issue. If this does that i thank you very much cuz i have been looking for a fix for a few weeks now.
jdsemler said:
I'm not running Cog2.2b7, but it seems to me you could use this method to generate yourself a unique Android ID using the emulator option under Make a new androidID with the Emulator. Then, using this command to pull the unique ID off the emulated Android device:
adb shell sqlite3 /data/data/com.google.android.googleapps/databases/accounts.db "select * from meta";
Once you have the Android ID, close out the emulator, and put this Android ID into your phone.
Like I said, I'm not running that version of Cognition, but give this a shot.
Click to expand...
Click to collapse
hi how can i change my android ID MAnually seems the link i provided on top doesnt work on me xD
I have been successful with these steps in getting my phone's id corrected (Cog 2.2 Beta6)
adb
su
sqlite3 /dbdata/databases/com.android.providers.settings/settings.db "update secure set value = '[your HEX android id]' where name = 'android_id';"
sqlite3 /dbdata/databases/com.google.android.gsf/gservices.db "update main set value = '[your DEC android id]' where name = 'android_id';"
reboot
I got my old id by doing a text search with notepad++ on a backup made with rom manager.
jfl0wers said:
I have been successful with these steps in getting my phone's id corrected (Cog 2.2 Beta6)
adb
su
sqlite3 /dbdata/databases/com.android.providers.settings/settings.db "update secure set value = '[your HEX android id]' where name = 'android_id';"
sqlite3 /dbdata/databases/com.google.android.gsf/gservices.db "update main set value = '[your DEC android id]' where name = 'android_id';"
reboot
I got my old id by doing a text search with notepad++ on a backup made with rom manager.
Click to expand...
Click to collapse
I did play around with sqlite3 as well, I didn't search through my old backup though I just put JF6 back with Odin, one click root, and downloaded "Android ID" from the market, wrote down the ID, and then flashed to cog 2.2 beta7 and restored.. Of course then setting my ID with app..
I know I went the long way, but it worked
For those who have AT&T tablets and have issue with using mediahub (it keeps prompting you that there is an update but when clicking OK, Market can't find the update), the trick is to put in your AT&T SIM card (the one that comes with the tab). Market will not find the update until you do so. Even though your original SIM card is not activated, it will still work. Once it finds the update, turn on Wifi and update as usual.
I've also noticed that AT&T tab will appear under Market once you insert the original AT&T SIM (even though it is not activated) and you could access all the AT&T software there.
This doesn't seem to work once you've flashed a Euro rom. I've tried messing with the build prop signature, but I can't get any ATT-specific stuff working, other than the data counter widget.
Now that you have the updated mediahub from AT&T, can you pull the APK off and post it please?
I'm running JMEv4 and I just ripped the MediaHub.apk from the stock ROM. Installed fine, but whenever I try to sign-up, it gives me a location can't be used.
EDIT: Yeah, there's definitely something buggy about it. It's not even loading the thumbnails of movies. And that location error is "Your location is not known or supported." Looks like OP is going to have to upload that updated apk.
agentdr8 said:
This doesn't seem to work once you've flashed a Euro rom. I've tried messing with the build prop signature, but I can't get any ATT-specific stuff working, other than the data counter widget.
Now that you have the updated mediahub from AT&T, can you pull the APK off and post it please?
Click to expand...
Click to collapse
Good to know..Have you tried changing sales_code.dat to ATT? It is the current value on origin AT&T tab. You will also need to Clear data under Market, MediaHub and Media storage. Not sure if you need to reboot.
Dunno which version this one is but it is from the most recent AT&T tablet and it's working (this is after the update prompt from market).
Here is build.prop that works with the above MediaHub.apk
Cool! I'll give it a try!
EDIT: Same issue as I had with my APK. Gotta be some other setting. I even changed the sales_code.dat to ATT from KOR.
What is ATT MediaHub? can someone please explain.
Thanks
dg5976 said:
What is ATT MediaHub? can someone please explain.
Thanks
Click to expand...
Click to collapse
It is like itunes for the tab. The reason everyone wants to get this to work is because ATT tabs came with a $50 credit towards movie rentals.
The problem is that once you flash your rom you can't update Media Hub and you can't sign into media hub anymore.
There is a nice group of us that have this $50 credit and can't use it. Kind of pissing me off personally. Still trying to find a fix for this.
Thanks everyone who is trying.
silversubie said:
Dunno which version this one is but it is from the most recent AT&T tablet and it's working (this is after the update prompt from market).
Click to expand...
Click to collapse
Just tried this APK and it still prompts for an update from the market (of which it can't find). This is with the build.prop that was posted as well. TiBu shows this MediaHub as version 108.
silversubie said:
Dunno which version this one is but it is from the most recent AT&T tablet and it's working (this is after the update prompt from market).
Click to expand...
Click to collapse
Where did you pull that from (out of curiousity)?
JaysFreaky said:
Where did you pull that from (out of curiousity)?
Click to expand...
Click to collapse
From the virgin AT&T tab /system/app/ after I upgraded MediaHub when was prompted.
agentdr8 said:
This doesn't seem to work once you've flashed a Euro rom. I've tried messing with the build prop signature, but I can't get any ATT-specific stuff working, other than the data counter widget.
Now that you have the updated mediahub from AT&T, can you pull the APK off and post it please?
Click to expand...
Click to collapse
I'm using JME and the attached MediaHub and build.prop. I can't update but I could use MediaHub. The trick is turn off Wifi (so it won't prompt you for update), launch MH, turn Wifi back on and enjoy
Hm. Do you happen to see another MH.apk inside /data/app?
Did you install the build.prop into the system directory on JME firmware? What do I need to do to get it to work on JME firmware?
JaysFreaky said:
Hm. Do you happen to see another MH.apk inside /data/app?
Click to expand...
Click to collapse
Here we go...unzip and drop it into/replace the one in /data/app/
silversubie said:
Here we go...unzip and drop it into/replace the one in /data/app/
Click to expand...
Click to collapse
Hm. Still having the same problem I was originally having.
Anyone else have luck with the JME rom?
Here are the steps for me on JME v4
1. Install MediaHub posted by OP
2. Replace builds.prop with OP's
3. Update sales_code.dat to ATT (not sure if this is needed but I did it)
4. Clear data/cache for MediaHub, Market and Media Storage
5. Replace /data/app/com.sdgtl.mediahub.p1.att-1.apk with OP's
6. Start MH
It is no longer prompt me to update. I haven't bought anything but I could watch preview clip fine.
quattr0 said:
Here are the steps for me on JME v4
1. Install MediaHub posted by OP
2. Replace builds.prop with OP's
3. Update sales_code.dat to ATT (not sure if this is needed but I did it)
4. Clear data/cache for MediaHub, Market and Media Storage
5. Replace /data/app/com.sdgtl.mediahub.p1.att-1.apk with OP's
6. Start MH
It is no longer prompt me to update. I haven't bought anything but I could watch preview clip fine.
Click to expand...
Click to collapse
Wow! That actually worked! Thanks both of you guys!
Couple of quick questions for those of us who don't know the file structure yet:
Where do I put the builds.prop file?
How do you update the sales_code.dat file?
Thanks,
Richard
I'm new to the android ecosystem but I've always been jealous of swype users, is it possible to port this feature to the nook touch?
Just replace apk file of swype with default keyboard using Root Explorer in system/app
I tried installing a keyboard apk file into system/app file by copy and paste with ES file explorer but it said failed. is there a special app or procedure I need to do this with? and where did you get the apk file? I would like a keyboard with directional arrows (for spreadsheets) and numbers for faster input. Thanks
Are you sure system is r/w?
Sent from my GT-I5700 using Tapatalk
roryn3kids using ES file explorer use the following instructions and you'll have access to r/w root files:
1. Scroll down to Root Settings and enable Root Explorer and Mount File System.
Not sure if this next step was needed but I did it anyway
2. Once again from the setting menu click on File Settings and enable "Show Hidden Files"
then copy the file from your data\app folder to your system\app folder
Swype "friendliness" to nook STR
The instructions above worked fine for me.
The problem is that I found the apk somewhere (a rather new version but still not the latest) and, even when it works, I do not get any "word list menu" like the one shown in those Swype Howto videos.
This means that, either I use an extremely short vocabulary, or I waste 50% of the time correcting the suggested word...
For instance, let's say I wanted to write f***, Swype forces me to accept the word duck.
This is good, because then I have the time to think twice before swearing but in the end... hum, let's say it's not that productive.
Of course, I checked that the options are properly configured (or I think so)
Does it happen to any of you, nook STR users?
BTW, I might also say that I cannot install the beta from swype.com/category/get-swype/
Have any of you succeeded on this?
Not that I want to re-activate a Post that was last updated in August, but it's nice to have as much information regarding swype as possible in a single post.
Thanks
I just discovered the Swype feature on my galaxy player 4.0 and it's great!
Never used Swype before this, But Since finding it a few days ago, it's all I've used! lol
Hope you get it installed, cuz its awesome.
Ok, I have further investigated the Issue and I can confirm now that it is properly configured (I compared it with some other devices) so let's ask it the other way around...
Is there any nook-STR-user who properly installed Swype?
How did you do it or, better said, where did you get your swype from?
Thanks very much, and a happy new year!
(sent using my not-that-effective-but-still-funny-to-play-with swype keyboard )
My findings with SWYPE are :
1. when you set your keyboard to SWYPE and do FACTORY reset, you might get problem in the "re_registration" your Nook. For some reason, the factory reset will not erase everything and the device is looking for SWYPE keyboard - which is obviously not there. So you won't have any keyboard to type onto !!! Having not a backup might get you in serious trouble !!!
2. As mentioned over here, the word prediction/suggestion is not visible so really, there is the small nuisance when you have to correct few words. keep an eye on it, when writing.
3. You might find a little bit frustrating the highlighting of a pressed button. Well, OK ... the truth is, that it's TOTALLY ANNOYING !!! Have a look on my video on youtube so you know, what I'm talking about :
youtube.com/watch?v=OYKjvqhxJmU&context=C3503defADOEgsToPDskIus5a7mP57B922B9wWU5cP
But, this can be fixed !!!
youtube.com/watch?v=S3vwQSvjUYM&context=C34142eeADOEgsToPDskJDd6sKkvt8EqkgO74yVfe7
Big THANK YOU goes to "djdarkknight96". His solution is to make the "highlighting" transparent, so it doesn't bother you any more. There was an attempt to make the trace line transparent as well, but without success (FC). Please, have a look at his thread for more info.
P.S. : With the youtube links -> as a new member outside links are not allowed for me yet -> so please add "www"
zholy said:
My findings with SWYPE are :
1. when you set your keyboard to SWYPE and do FACTORY reset, you might get problem in the "re_registration" your Nook. For some reason, the factory reset will not erase everything and the device is looking for SWYPE keyboard - which is obviously not there. So you won't have any keyboard to type onto !!! Having not a backup might get you in serious trouble !!!
Click to expand...
Click to collapse
My findings with this are that the swype keyboard is actually still there, so you need to use adb to delete the apk file and, if you replaced the original, find that one and use adb to add it.
does anyone know how to get to Qualcomm USB Settings. *#7284# doesn't work.
Thanks
brianrent said:
does anyone know how to get to Qualcomm USB Settings. *#7284# doesn't work.
Thanks
Click to expand...
Click to collapse
Are there no secret codes for this phone?
Nevermind.
For those interested I followed the instructions here
Didn't work the first time with lower case "on" so I used uppercase "ON" and it worked.
brianrent said:
Nevermind.
For those interested I followed the instructions here
Didn't work the first time with lower case "on" so I used uppercase "ON" and it worked.
Click to expand...
Click to collapse
Did you have any issues writing to /efs/carrier from Root Explorer? Every time I try it says the write failed. I even changed the permissions on the folder to 777 and that didn't help. I also tried to push the file from ADBGUI and that didn't work either.
Worked for me just fine. just had to hit read write button at the top before I used notepad or whatever is called to edit it.
Sent from my SM-N900V using xda premium
I don't know if it matters or not but my phone is rooted.
Sent from my SM-N900V using xda premium
Okay, I got the file changed but I cannot get the menu to pop up. I'm just supposed to go to the dialer and type in *#06# and something is supposed to pop up, or am I supposed to hit the dial button?? It just tries to call and I get the default Verizon message that the call can't be completed as dialed. Also, I tried the "intent" shortcut method and when I try to run it, it says "Application not Installed" I've verified that I do have HiddenMenu.apk in my /system/app folder. Not sure why this isn't working for me. My phone is rooted, but I am running the stock Verizon build.
Any help would be greatly appreciated.
ephreet said:
Okay, I got the file changed but I cannot get the menu to pop up. I'm just supposed to go to the dialer and type in *#06# and something is supposed to pop up, or am I supposed to hit the dial button?? It just tries to call and I get the default Verizon message that the call can't be completed as dialed. Also, I tried the "intent" shortcut method and when I try to run it, it says "Application not Installed" I've verified that I do have HiddenMenu.apk in my /system/app folder. Not sure why this isn't working for me. My phone is rooted, but I am running the stock Verizon build.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I did go into /system/app folder and clicked HiddenMenu.apk and installed it but that was before i made the change to capital letters for the "ON" edit. Not sure if that mattered or not. You dont need to hit send, it will work after you hit the last # if it is working.
ephreet said:
Okay, I got the file changed but I cannot get the menu to pop up.
Click to expand...
Click to collapse
I got mine just by editing the text to "ON" with root explorer text editor... never touched hiddenmenu.apk
did you reboot after editing text?
It's just one thing I tried before it finally worked but as I said don't know if it's necessary and probably its already installed if it's in that folder. I'm glad it worked for someone else though.
Sent from my SM-N900V using xda premium
In case anyone was wondering some of the NV Items are WRITE PROTECTED so even though "NV-items_reader_writer.exe" will say "successfully written" some items such as 550 it will not overwrite the info and no change will take place.
Just out of curiosity, what does this hidden menu give access to?
beamed from transporter room 3
It gives you the ability to change USB settings so you can use tools to edit NV item entries. One of which is 550 which is your imei number in case flashing screws up your imei. Also you can backup your entire EFS.
Sent from my SM-N900V using xda premium
Not sure if this is the right thread !
I want to back up my EFS. I screwed up my S4 and want to be careful this time. Is there a tool or tutorial for Verizon Note 3 ?
If *#7284# doesn't work try *#0808#