Database Users

[Q]Android Market 3.1.5 update denies many apps (Device not compatible)

Hello XDA
First post here, altho am an old XDA searcher hehe.
I just flashed a new ROM, [18.Sep.11][ZIP]★★★★★HyperDroid-CM7-v3.0.1[a2sd][CyanogenMod7 LEO 2.3.5][seader_R5]
Now, the good thing is, I can use my small standard battery pack again as it doesnt drain it that fast.
Bad part is...
As I backed up most off my apps from my previous ROM and imported them here, I cannot update them anymore.
And most apps I wana download just cannot be downloaded because of incompatibility (my behind!)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now am stuck with retarded alted apps for twitter, FB and many other apps, or just not using them at all anymore...
It there a workaround for this issue? Maybe downgrade the market (which prob will auto update again...)
I might have seen a post with some one saying "you got to edit some .ini file in your root with a android notepad" but seems like I cant even install a simple Android notepad, so therefore quite anoying...
Edit to that part:
I did manage to get a rooted combination to mod the build.prop file
This is what I changed:
Code:
ro.product.model=HTC Vision
ro.product.brand=tmobile
ro.product.name=vision
ro.product.device=vision
ro.product.board=vision
ro.product.manufacturer=HTC
But, it did not work...
Thanks in advance, keep the trolling for yourself or your little brother, just share what you think is a fix for this, I will thank you for it.
PVTD
EDIT 2: Current solution is on the 2th post.

I did find a fix who takes a bit of work, but I hope to get some one to make a decent full fix for it
Here is how I did it:
First, locate the Android Market in your apps list and select it.
You will find a button saying "Uninstall Updates", use it.
Once it's done, open the Android Market, press "I agree" and notice the app will auto close.
Act fast, as the app is downloading the updated market in silent mode.
What you do is open a rooted file explorer. Any should do.
Go to "root/cache/downloaded/ and delete everything inside.
Then it should be done, as that worked for me, tho not sure how long it would take to update again.
Hope this works for you
PVTD
Sent from my HTC Vision using XDA App (It did fool the XDA app xD should be HTC HD2)

The Fix
You'll need Root Explorer
Open Root Explorer
Open the system folder
Long hold on build.prop and choose open in text editor
find the line that says ro.sf.lcd_density=
Change the numbers from 192 to 160
Save the file
Reboot your phone
Go to application management
choose the All tab
find market
choose it and then choose to force stop
then clear your cache
close out of file manager
reopen market place
you should now be able to get to the apps that you couldn't!

The rom on my hd2 comes with the new market by default...at first I thought the device incompatible messages were due to my 192dpi but even reverting to 240 it still showed same. Is there another solution?

Side note--There is an LCD density changing app so you can change on the fly with out having to go through all the file system stuff. Also the LCD density change seems to work for some and not for others, so to me it's a bust.
Now for the market-- The only thing that I have found to work short of altering the market itself, is using the market on my computer and pushing to my phone. This of course is a hassle and requires you to keep track of when updates come out for the apps you have.... But it works. I most recently had this problem with widget locker only seconds before I had it uninstalled it from my phone. Went on the web and pushed it to my phone, boom, installed.

Changing the LCD density didn't work for me.. I just reverted to the old Market app to allow installation of some apps.

I had same problem... here's how I fixed it. Change LCD density to default 240, then reboot. Then go to settings-applications-manage apps-market. Under market push clear data. Open market and agree and that worked for me.
I was getting a yellow banner in market that said "your device is not compatible with this item"
Sent from my HTC HD2 using xda premium

chevyboy33 said:
I had same problem... here's how I fixed it. Change LCD density to default 240, then reboot. Then go to settings-applications-manage apps-market. Under market push clear data. Open market and agree and that worked for me.
I was getting a yellow banner in market that said "your device is not compatible with this item"
Sent from my HTC HD2 using xda premium
Click to expand...
Click to collapse
Thanks Chevyboy33,
This worked on my HD2 CM7 build

tmtx76 said:
You'll need Root Explorer
Open Root Explorer
Open the system folder
Long hold on build.prop and choose open in text editor
find the line that says ro.sf.lcd_density=
Change the numbers from 192 to 160
Save the file
Reboot your phone
Go to application management
choose the All tab
find market
choose it and then choose to force stop
then clear your cache
close out of file manager
reopen market place
you should now be able to get to the apps that you couldn't!
Click to expand...
Click to collapse
i dont see "thanks" button but, GREAT THANKS, It's working!!!!

chevyboy33 said:
I had same problem... here's how I fixed it. Change LCD density to default 240, then reboot. Then go to settings-applications-manage apps-market. Under market push clear data. Open market and agree and that worked for me.
I was getting a yellow banner in market that said "your device is not compatible with this item"
Sent from my HTC HD2 using xda premium
Click to expand...
Click to collapse
Just flashed AmeriCanAndroid AOSP HD2 GB2.3.7 CM7.1 and experienced the same problem. This solution also worked for me. I installed all the apps that I weren't able to, then changed back to custom dpi and rebooted again.
Thanks

unfortunately I am from europe, and its not working for me. I want to use birdiesync and/or myphoneexplorer and both are incompatible. I already wiped the caches and changed lcd-Density but no fortune so far. I use Americandroid and HD2

Kreativist said:
unfortunately I am from europe, and its not working for me. I want to use birdiesync and/or myphoneexplorer and both are incompatible. I already wiped the caches and changed lcd-Density but no fortune so far. I use Americandroid and HD2
Click to expand...
Click to collapse
For americandroid, you need to change the density in startup.txt, then reboot. No need to modify the build.prop file yourself as the change will get overwritten on reboot by whatever is in startup.txt

tmtx76 said:
You'll need Root Explorer
Open Root Explorer
Open the system folder
Long hold on build.prop and choose open in text editor
find the line that says ro.sf.lcd_density=
Change the numbers from 192 to 160
Save the file
Reboot your phone
Go to application management
choose the All tab
find market
choose it and then choose to force stop
then clear your cache
close out of file manager
reopen market place
you should now be able to get to the apps that you couldn't!
Click to expand...
Click to collapse
Thanks, this worked for me, but I changed my res to 240 and removed data rather than cleared the cache. I also installed "DPI Changer" after manually editing the file a few times to make life easier.

goldengoose said:
Thanks, this worked for me, but I changed my res to 240 and removed data rather than cleared the cache. I also installed "DPI Changer" after manually editing the file a few times to make life easier.
Click to expand...
Click to collapse
Thanks. I have confirmed changing the LCD Density & deleting the Market app data is/was necessary on my rooted Photon 4G. I tested 160, 192, 200, 210, 225 (my original), 240 & 264. Along with app cache, sys cache, & memory dumps for each density. The only thing that worked for me was LCD Density 240, reboot, delete Market app data & system cache.
Immediately after & without rebooting I was prompted for a new agreement in Market & able to install previously incompatible app.
Now I need to figure out how to get Market to register Chomp as an installed app without having to delete & reinstall. It was installed by downloading the apk from their website due to this alleged incompatibility.
Weird thing is Market shows app installed when I search it. However it does not appear in my apps section of Market. Any ideas? Perhaps I should clear the Chomp data too? Lol

chevyboy33 said:
I had same problem... here's how I fixed it. Change LCD density to default 240, then reboot. Then go to settings-applications-manage apps-market. Under market push clear data. Open market and agree and that worked for me.
I was getting a yellow banner in market that said "your device is not compatible with this item"
Sent from my HTC HD2 using xda premium
Click to expand...
Click to collapse
Worked perfectly thank you

wtf. so i need to change lcd densitiy everytime i want to downoad an app?
this sounds definitley ****
srsly, i just flashed the NexusHD2 ICS ROM and not even root explorer is compatible now. then i installed it via a apk from my sd card.
im switching back to GB..

D4rkSoRRoW said:
wtf. so i need to change lcd densitiy everytime i want to downoad an app?
this sounds definitley ****
srsly, i just flashed the NexusHD2 ICS ROM and not even root explorer is compatible now. then i installed it via a apk from my sd card.
im switching back to GB..
Click to expand...
Click to collapse
Switching back to GB won't solve your problem. This is due to the market app. The pro version of LCD density changer says there is way to spoof the market to think the LCD density is at 240 (which is the one that works).

gprash said:
Switching back to GB won't solve your problem. This is due to the market app. The pro version of LCD density changer says there is way to spoof the market to think the LCD density is at 240 (which is the one that works).
Click to expand...
Click to collapse
Is that actually "LCD Density Modder Pro"?
My density is/was already set at 240.
Ok, I want to make sure I have this correct....
I have to buy an app that fools the Market into thinking I have the density set to the value that it already is?
Before I go to that trouble, I want to verify that the issue is truly with the LDC density and not with the model of the phone? I ask because, even after changing my build.prop to remove all references to HD2, and changing to model to "vision", when I go to settings/about phone it still says my phone is an HTC HD2. (complete steps I took found here: http://forum.xda-developers.com/showthread.php?p=23726581#post23726581)
Example: I went to [draw something] Plonga's official site via my phone (after repeatedly verifying the changes to the build.prop, rebooting, and then clearing the data from Google and the Market) and that site still verified that I was using an HTC HD2 and wouldn't let me d/l directly from the site.

Anyone else have any ideas?

I used MarketEnabler apk from the market to solve this problem when changing the lcd density did not work. The one that worked for me was vodafone ie . You can get the codes using MarketEnablerCodes apk.(both free apks)
Of course these apks have to be "compatable"..lol.
I back-up a lot and have had these apks for a while..if you need

Remove autoupdate Market

How i can remove autoupdate of market?
I open market and have new version. Then i go on application, uninstall update and have old Market. After some time i have new market again.
New market on my wildfire is very slow and FC, and if i have luck to find something, get error to insufficient disl space or app is not compatible.....
With old Market don't have problems. And i want remove autoupdate of Market..
Please someone...

The answer to your question was in the next thread to this one!
Freeze the updater with titanium backup.
Sent from my HTC Wildfire using xda premium

Scratch0805 said:
The answer to your question was in the next thread to this one!
Freeze the updater with titanium backup.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
what if I don't have donate version?

dengseng said:
what if I don't have donate version?
Click to expand...
Click to collapse
Simply put.......... get it, or find a different app with root access to freeze it.
We suggest titanium because its the best at what it does, and is worth every penny to a serial flasher.
That sounds a bit wrong!
Sent from my HTC Wildfire using xda premium

Titanium don't help me
Titanium don't help me, but:
Root users:
1. Root explorer - goto system/apps (press mount r/w - if don't press that you will get message for read only)
2. delete "market updater" and com.vending... (something like that - file have vending in name)
3. reboot
4. download old market from here, and install
5. reboot
6. check again in system/apps if exists market update (if no exists, than is OK)
7. with titanium backup make market like system app
7. run market

mozvatic said:
Titanium don't help me, but:
Root users:
1. Root explorer - goto system/apps (press mount r/w - if don't press that you will get message for read only)
2. delete "market updater" and com.vending... (something like that - file have vending in name)
3. reboot
4. download old market from here, and install
5. reboot
6. check again in system/apps if exists market update (if no exists, than is OK)
7. with titanium backup make market like system app
7. run market
Click to expand...
Click to collapse
How to put market back in system using titanium backup???

Don't just bluntly delete the apk, disable it! From a root shell, enter
pm disable com.android.vending.updater
There, it's "frozen". No need for a paid app, S-Off or whatever. Just root.

Yeh but not everyone is as fluent as you in adb, damn took me 4 days just to get it setup correctly and now a month later I'm still learning the basics. With TB its a simple long press on the app and freeze but if you don't have adb its a long process installing for first time and then learning the commands.
Sent from my HTC Wildfire using xda premium

4 days to download the SDK and run it? Did you order a new PC in the process?
EDIT: Consider installing ConnectBot or Android Terminal Emulator. That way you don't need adb and the soft keyboard is good enough for the occasional tweak.

Like i said smartass not everyone is as up to date as you may be, bear in mind that i only bought my first android phone 6 months ago, only found xda 4 months ago and have never really tried to hack anything before except a few games.
It wasn't the downloading that was the problem with adb it was the instructions i was following, they were a little misleading as to where everything should be so as i was getting errors left right and centre so i decided to look further into it and realised i was missing things and a few things weren't in the right place, i never asked for help though mate figured it all out on my own and it's perfect now.
All i'm trying to say is the people having these problems most probably haven't got a clue how to use adb or the terminal for that matter as if they did they probably wouldn't be here asking questions therefore giving them the easiest, quickest possible way to solve there problem is best imo.

You're probably completely right about that, sorry for being a "smartass".

henkdv said:
Don't just bluntly delete the apk, disable it! From a root shell, enter
pm disable com.android.vending.updater
There, it's "frozen". No need for a paid app, S-Off or whatever. Just root.
Click to expand...
Click to collapse
I tried that but I couldn't update any app from the market when disabled.
EDIT: it is not because of that but after removing market udpates it behaves strange, seems that I am able to install 1 or 2 updates but any successive update fails. I will try to get the log to see what is the problem.
EDIT2: seem to be caused by low memory

That's odd, mine still auto-updates applications (but not the market itself).

antish said:
How to put market back in system using titanium backup???
Click to expand...
Click to collapse
Yes, please explain me someone!
Thanks!

Scratch0805 said:
Like i said smartass not everyone is as up to date as you may be, bear in mind that i only bought my first android phone 6 months ago, only found xda 4 months ago and have never really tried to hack anything before except a few games.
It wasn't the downloading that was the problem with adb it was the instructions i was following, they were a little misleading as to where everything should be so as i was getting errors left right and centre so i decided to look further into it and realised i was missing things and a few things weren't in the right place, i never asked for help though mate figured it all out on my own and it's perfect now.
All i'm trying to say is the people having these problems most probably haven't got a clue how to use adb or the terminal for that matter as if they did they probably wouldn't be here asking questions therefore giving them the easiest, quickest possible way to solve there problem is best imo.
Click to expand...
Click to collapse
Totally agree. I to this day still have no idea how to use adb or fastboot!!! When I have tried I have failed miserabley lol.
On topic, I personally just deleted market updater from the rom zip before I flash the rom and have no problems with AP updates.
Lol I must be a smarter arse to get away without using sdk, adb or fastboot for so long.
sent from my wilderbeast:buzz

you do not need to use adb. Just open the terminal emulator and type
Code:
$ su
confirm granding superuser priviledges
prompt should be changed from $ to #
Code:
# pm disable com.android.vending.updater
thats all.
you can restore it similarily using the "pm enable com.android.vending.updater" command.

cceerrtt said:
you do not need to use adb. Just open the terminal emulator and type
Code:
$ su
confirm granding superuser priviledges
prompt should be changed from $ to #
Code:
# pm disable com.android.vending.updater
thats all.
you can restore it similarily using the "pm enable com.android.vending.updater" command.
Click to expand...
Click to collapse
worked for me thanks a lot bud

cedriccc said:
worked for me thanks a lot bud
Click to expand...
Click to collapse
I just repeated what henkdv wrote before. ;-)

And I got the idea from The_Complete_Noob
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[Q] Tricking Android Market and avoiding Incompatible App message

Alright guys.
I'm facing some issues here... Facebook has updated or something and now it doesn't show up in the 2.2 Market. 3.4 Market shows it but it says it's uncompatible and I can't install it.
Espier Launcher (another app I like) has two versions. 2.1 shows in 2.2 market. Both show in 3.4 market BUT the first one, even though it says it works for 2.2 and above, the market says it's incompatible.
This is a very big PITA because I'm tired (yes, TIRED) of trying apps that aren't compatible and they work very happily on my Magic, so they should stop the fuss and let us install everything and let us decide if the app works or not... it's not google's problem to solve, but the app developer's instead.
Now, I'm working on this and I need your help. I've had *some* success with making the device think it has GB installed instead of Froyo, however, the market crashes upon loading (the same goes for Maps which randomly FCs upon reboot).
---
On a sidenote, for the ones who go like "Y U USE FROYO D:" go flash my ROM and find out why, and ALSO it doesn't make a difference in this issue so don't tell me that it does because I've already tried this in other CM7-based ROMs.
---
I've found out that some of the build.prop properties (specially ro.build.* and ro.device.*) can fake this out to make some apps available. I've also tried to change the LCD density but it doesn't make any difference. The idea is to find out a good matching fingerprint which works for all apps (or for most, if possible).
I'm willing to give a go at your suggestions and tries and share my findings. That is, if you guys are willing to help me in this endeavour, too .
Any thoughs, suggestions, advice, etc. are greatly appreciated!
Thanks in advance
- DARKGuy

I'm having the same problem. the annoying thing is that I used most of the apps that are now incompatible with my device.

Hey, really? That seems to have happened to me too. I wanted to install alarmdroid last night and somehow it didn't appear in the market. I assume it's because it's incompatible now. I mean... WTF?
Sent from my HTC Magic using XDA App

Hi Darkguy
I hope we can find a solution for this problem.
here is something that looks promising but I could not make it work:
geeknizer.com/install-incompatible-unsupported-apps-from-android-market
lol, I cant post links yet...
BTW: I love your ROM, me and my wife use it and its fast as hell : good job there...

badikhi said:
I hope we can find a solution for this problem.
here is something that looks promising but I could not make it work:
geeknizer.com/install-incompatible-unsupported-apps-from-android-market
lol, I cant post links yet...
BTW: I love your ROM, me and my wife use it and its fast as hell : good job there...
Click to expand...
Click to collapse
Me too!
Oh, I've seen that link but I didn't give it much testing. However I'm trying it both with old market and new, clearing cache/data from market/google services framework and such and it doesn't seem to work. At least, NOT that fingerprint. I've tried a GB fingerprint and it causes some FCs on Maps and Market, so there must be something in that fingerprint which doesn't trigger a change or something.
Hehe, I'm really glad you two like and use the rom my ROM makes couples happy, yay XD!

Alright. I'm eating noodles <3 and fighting market:
I've found these online but they don't seem to work
Code:
ro.product.model=Nexus S
ro.product.manufacturer=samsung
ro.build.fingerprint=google/soju/crespo:2.3.4/GRJ22/121341:user/release-keys
ro.build.description=soju-user 2.3.4 GRJ22 121341 release-keys
Code:
ro.product.model=PD_Novel
ro.product.manufacturer=unknown
ro.build.fingerprint=google/passion/passion/mahimahi:2.1-update1/ERE27/24178:user/release-keys
Code:
ro.board.platform=s3c6410
ro.build.product=smdk6410
ro.build.description=sec_smdk6410-eng Eclair pandigitalopc1/sourceidDL00000009 eng.publisher.2011.01.03.131654 test-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.1-update1/ERE27/24178:user/release-keys
Code:
ro.product.model=Nexus S
ro.product.manufacturer=samsung
All this taken from:
http://forum.xda-developers.com/archive/index.php/t-1333584.html
(here is "market fixer" -> http://kyros-tablet-zone.team-talk.net/t204-dev-easy-market-fixer-plus-v10-62411 <- but it's just stupid, it doesn't do anything related to our issue)
http://www.redmondpie.com/how-to-in...-from-android-market-for-unsupported-devices/
https://plus.google.com/103394636954928901514/posts/btyxqnxB3nc
Yes, I've also tried 2.3 Market (which I've just found and I'm gonna use as a new market) and it doesn't do anything.
I've also tried clearing cache/data from GSF & Market prior to testing all these build.prop changes. Something is really effed up there in the market :/

No success
I tried all these changes in build.prop and even tried changing the build.prop before installing the ROM again. this method does not seem to work.
I have 1 question. why do we have a build-SAPHIRE.prop? does it do anything or just a backup?
thanks

badikhi said:
I tried all these changes in build.prop and even tried changing the build.prop before installing the ROM again. this method does not seem to work.
I have 1 question. why do we have a build-SAPHIRE.prop? does it do anything or just a backup?
thanks
Click to expand...
Click to collapse
I'm looking for info on the Froyo market now. It seems the solutions are a bit different, so I'm trying them out now
Hmn, now that you mention it... I've put it in all the ROMs I've tried or used back when I was editing GingerYoshi and making this ROM because I think it added some info needed for the phone. Looking at it now, it seems to be somewhat of a culprit, so I've removed it and I'm gonna give these solutions another try now, so thanks for pointing it out!
It also seems like clearing cache+data from Download Manager helps too, along with Google Services Framework and Market. Or so I read somewhere

I F***KIN' DID IT!!!!!!!!!!!!!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'll post updated instructions soon
---
OKAY... it seems that the Market caches data on the server too, associated to your google account.
Now, this problem only seems to appear if you install Market 3 and then go back to Market 2, if you do, the apps flagged as incompatible will disappear no matter what you do. At least, that's how I messed up my market... but I did so AFTER uploading the 0.3.8 U1 so it's weird that some of you have got the same problem.
The idea seems to make Market clear the data once it's downloaded on the phone and by consequence clears it when it synchronizes with the web server (it's just a theory), which seems to fix the issue.
There IS a solution and this is the working one:
1. Go to manage applications, all tab.
2. Go to market, clear cache, data and force stop
3. Go to Google Services framework, clear data and force stop
4. Edit the following build.prop lines to be the following (Some of these lines may already be correct)
ro.build.id=GRJ22
ro.build.display.id=GRJ22
ro.product.name=soju
ro.product.device=crespo
ro.build.description=soju-user 2.3.4 GRJ22 121341 release-keys
ro.build.fingerprint=google/soju/crespo:2.3.4/GRJ22/121341:user/release-keys
5. Reboot phone, and give it a bit of extra time to startup before opening the market.
6. Open market, agree to TOS.
7. Go to manage applications, all tab.
8. Go to market, clear cache and force stop (DO NOT CLEAR DATA)
9. Go to Google Services framework, clear data and force stop
10. Open market, and you should get an error. (This is good)
11. Restart phone again.
This is taken from ( http://forum.xda-developers.com/showthread.php?t=1133702 ) (THANKS! btw ^^).
Now, following these steps is VERY, VERY important. You must repeat all of them (except editing the build.prop if you've already modified it) until you get the error as in step 10 and reboot the phone. If you can't see the apps again, well the workflow is the following one:
1. Clear all data/cache/etc from market/gsf.
2. Go back to market and see if the LICENSE TERMS appear. If they don't, reboot, clear data, etc. until it does.
3. AFTER the license terms appear, do steps 5-11. The "DO NOT CLEAR DATA" warning is VERY important, else IT WON'T WORK.
Now... for FroyoDragon, I'll post an updated version and a fixed build.prop for ya guys maybe tomorrow or around this week ^_^. YAY!
Also, it seems that removing the build.sapphire.prop file helped in the process of market detecting the build.prop changes, so kudos to badikhi! ^^

Congratz...
This is great news. and I'm always happy to help.
I have 1 request. can you include google talk in the next release of the dragon?
thanks

darkguy2008 (or anyone),
Any idea if this works on other phones, ie Evo 4G? I have seen other posts which edit the build.prop but the changes are specific to a phone.

I had to do this to my phone, a Droid 2. Several apps I used to have would not download again becasue they are now magically incompatable even though they worked just fine before.
Anyway, I went through the steps a few pages up. All I changed in build.prop was model and manufactuer. I changed it to Nexus S, and Samsung. The apps are now showing back up on my phone. However, when I go to market.android.com on my computer, it was still showing as the droid 2. I removed it, but now its not showing any devices for my account, so I can download from the market that way.
Ill give it some time and download a few apps and see if the servers get updated in a bit. But, at least from the phone, this works great.

badikhi said:
This is great news. and I'm always happy to help.
I have 1 request. can you include google talk in the next release of the dragon?
thanks
Click to expand...
Click to collapse
Indeed it is, thanks for the suggestions =).
I think I can, yes.
satur9 said:
darkguy2008 (or anyone),
Any idea if this works on other phones, ie Evo 4G? I have seen other posts which edit the build.prop but the changes are specific to a phone.
Click to expand...
Click to collapse
In theory it should, just as long as you have build.prop. Look at what the guy with the Droid 2 did and it could help your phone too. I'm really impressed to know that it doesn't work on the Evo 4G, which is a fairly recent phone... :/
helllmonkey said:
I had to do this to my phone, a Droid 2. Several apps I used to have would not download again becasue they are now magically incompatable even though they worked just fine before.
Anyway, I went through the steps a few pages up. All I changed in build.prop was model and manufactuer. I changed it to Nexus S, and Samsung. The apps are now showing back up on my phone. However, when I go to market.android.com on my computer, it was still showing as the droid 2. I removed it, but now its not showing any devices for my account, so I can download from the market that way.
Ill give it some time and download a few apps and see if the servers get updated in a bit. But, at least from the phone, this works great.
Click to expand...
Click to collapse
That's alright, it's good to know the steps worked for you . I might give it a try and change it to Nexus S & Samsung and see if it helps - so it's cleaner that way. Thanks for sharing your results

Hmm, I've got a few doubs now:
Do any of you see Google Talk in the market? along with Facebook, AlarmDroid, Google Maps and such? if you can see those apps, can you share your build.prop? THANKS!
I also have a few questions:
1. Does this happens on GingerBread markets/ROMs?
2. Does this happens on devices which have Froyo or GB as stock ROM? (such as recent devices)?

darkguy2008 said:
Hmm, I've got a few doubs now:
Do any of you see Google Talk in the market? along with Facebook, AlarmDroid, Google Maps and such? if you can see those apps, can you share your build.prop? THANKS!
I also have a few questions:
1. Does this happens on GingerBread markets/ROMs?
2. Does this happens on devices which have Froyo or GB as stock ROM? (such as recent devices)?
Click to expand...
Click to collapse
You can't see Google Talk in the market. It's not there. That's the reason I asked you to include it in your ROM. you have to take it from the gapps zip. If you need a gapps for froyo I can send you the 1 I use with your ROM and it works for me.

badikhi said:
You can't see Google Talk in the market. It's not there. That's the reason I asked you to include it in your ROM. you have to take it from the gapps zip. If you need a gapps for froyo I can send you the 1 I use with your ROM and it works for me.
Click to expand...
Click to collapse
Oh, I see. Sure, send it, I'll give it a look ^_^!
But is that normal? I mean, should GTalk appear in the market or are Maps/Gmail the only which should?

darkguy, did you update the working build.prop in the 0.3.9 version?

daeron666 said:
darkguy, did you update the working build.prop in the 0.3.9 version?
Click to expand...
Click to collapse
Yes I did, but the market's still screwed up so it's a matter of luck. If it doesn't then try the steps here and it should.
Another thing I did was to apply the 160 density update.zip right after flashing FroyoDragon 0.3.9 then went into the market and it seems it did the job, then I went back to 135 and it's still working cool.

oh no, it doesn't work....!!

darkguy2008 said:
I F***KIN' DID IT!!!!!!!!!!!!!!!!
Congrats (one more time) for Market Fix. It worked!!!
Click to expand...
Click to collapse
Click to expand...
Click to collapse

[request] effective method to prevent OTA updates

Since every method proposed in the thread over in the General forum to prevent updates doesn't work, even having custom TWRP recovery, i'm reaching out to the developers to ask for help on this. I suspect ADCP is involved myself but have no way to trace it.
What if I set /cache to read only? That apparently is where the .bin gets written to by whatever process downloads it, and from there it's read by recovery. Is /cache used by anything else on a typical Android system?
Not everyone wants to use CM7 but that appears to be the ONLY thing that "breaks" OTA updates. I'm sure there's some link in the chain we could interrupt to stop this creeping menace. I'm sure i'm not the only person with 6.2 rooted sitting here with wifi off!

Just a suggestion, but if you set the folder kindleupdates on the sdcard to read-only (it's where updates are downloaded to), would that break OTA updates?

jb0ne said:
Since every method proposed in the thread over in the General forum to prevent updates doesn't work, even having custom TWRP recovery, i'm reaching out to the developers to ask for help on this. I suspect ADCP is involved myself but have no way to trace it.
What if I set /cache to read only? That apparently is where the .bin gets written to by whatever process downloads it, and from there it's read by recovery. Is /cache used by anything else on a typical Android system?
Not everyone wants to use CM7 but that appears to be the ONLY thing that "breaks" OTA updates. I'm sure there's some link in the chain we could interrupt to stop this creeping menace. I'm sure i'm not the only person with 6.2 rooted sitting here with wifi off!
Click to expand...
Click to collapse
Unregistered fires will not get OTA updates. Renaming com.amazon.dcp.apk to com.amazon.dcp.apk.bak will unregister your fire but you will be able to sign into and use all of the amazon services individually.

neilrl79 said:
Unregistered fires will not get OTA updates. Renaming com.amazon.dcp.apk to com.amazon.dcp.apk.bak will unregister your fire but you will be able to sign into and use all of the amazon services individually.
Click to expand...
Click to collapse
Somone just posted that their unregistered Kindle has been updated! There is no escape

Somebody on 6.2 delete /system/etc/otacerts.zip and see if it still updates
Sent from my Galaxy Nexus using XDA App

JackpotClavin said:
Somebody on 6.2 delete /system/etc/otacerts.zip and see if it still updates
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I just went to do that in File Expert, and I don't have a /system/etc/otacerts.zip.
Any other possible locations for that file? I'll try it.
Edit: Found it in /system/etc/security. It has a 1.6kb file called releasekey.x509.pem in it. Renamed to otacerts.bak
Edit2: Just to be safe, moved the file to my sdcard and deleted it from /system/etc/security. Rebooted ok, temp unrooted, Amazon Videos works, my books work, everything seems ok. Note that I am also one of those who disabled OTASilentInstall as well though that doesn't seem to have mattered for some.

bus_ter said:
Somone just posted that their unregistered Kindle has been updated! There is no escape
Click to expand...
Click to collapse
Interesting, I wonder if they recently unregistered it,after the update had already downloaded and was just waiting to install. My fire has never been registered and has never seen an OTA, in fact a couple of amazon techs told me that it was unable to be updated while unregistered. Although now that i think about it, I can't imagine amazon techs know anymore than anyone else

Wrong forum... Rename /system/etc/otacerts.zip does help.

this would be great. at least then we could edit the binarys before updating to include FFF and TWRP.

Mine is still on 6.2 with these methods.
How to disable auto software update OTA on Kindle Fire?

JayceOoi said:
Mine is still on 6.2 with these methods.
How to disable auto software update OTA on Kindle Fire?
Click to expand...
Click to collapse
Yes, Jayce, but there are people reporting use those methods and still getting the update.

I added another layer of protection, the program Droidwall. I allowed Amazon Apps and Amazon Videos plus a bunch of others but did not allow ADCP. Now if I browse to Amazon App Store, buy an app, it no longer pushes to my Kindle, despite the web page saying just go to the Amazon App store App on my kindle and it would download automagically. I had to manually initiate a download of the app. So either otacerts.zip or firewalling off ADCP disabled remote push of apps -- and hopefully disabled remote push of updates, that part remains to be seen.

new method
new method (not confirmed yet i think)
Kindle Fire 6.2.1 breaks root and you cannot re-root. To prevent this, simply install DroidWall. If you are afraid of downloading the update and want to keep wifi disabled, just do a google search for Droidwall.apk and sideload.
Once installed, launch Droidwall. Make sure the mode says "Mode: White list (allow selected). You will have to manually select which apps to give Wifi access to (I selected Email, Browser, Netflix, and Amazon Video on Demand). You should only select the apps you REALLY want to give access to. Then hit Menu and Apply Rules. Enable Wi-fi, and you should be good.
I tested while running Wireshark and watched the bandwidth according to my Tomato router - no more huge files being downloaded.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DroidWall : https://market.android.com/details?id=com.googlecode.droidwall.free
or : http://code.google.com/p/droidwall/
source : http://gizmodo.com/5870339/how-to-keep-your-kindle-fire-rooted-and-update+free

Has your log of the app shown you anything?

Where does it log to?

This works if you rename OTASilentInstall.apk to OTASilentInstall.apk.bak and apply the rooted 6.2.1 update. NOTE when you apply the update you have to rename the apk again.
Sent from my still rooted Kindle Fire using xda premium

jb0ne said:
Where does it log to?
Click to expand...
Click to collapse
the app has a log file you can turn on. You view it via the app under more in settings of the app.
http://i.imgur.com/sRDb6.jpg

zirooo said:
new method (not confirmed yet i think)
Kindle Fire 6.2.1 breaks root and you cannot re-root. To prevent this, simply install DroidWall. If you are afraid of downloading the update and want to keep wifi disabled, just do a google search for Droidwall.apk and sideload.
Once installed, launch Droidwall. Make sure the mode says "Mode: White list (allow selected). You will have to manually select which apps to give Wifi access to (I selected Email, Browser, Netflix, and Amazon Video on Demand). You should only select the apps you REALLY want to give access to. Then hit Menu and Apply Rules. Enable Wi-fi, and you should be good.
I tested while running Wireshark and watched the bandwidth according to my Tomato router - no more huge files being downloaded.
DroidWall : https://market.android.com/details?id=com.googlecode.droidwall.free
or : http://code.google.com/p/droidwall/
source : http://gizmodo.com/5870339/how-to-keep-your-kindle-fire-rooted-and-update+free
Click to expand...
Click to collapse
Hi, but just wanted to confirm will this work or will it still update??
Has anyone tried this?

icebuck said:
Hi, but just wanted to confirm will this work or will it still update??
Has anyone tried this?
Click to expand...
Click to collapse
I was using the Droidwall method all day yesterday and today only allowing Netflix, Youtube, Pandora, Spotify, Onlive, Dolphin HD and Market Place wifi access and Just a few minutes ago my kindle was attempting to download and install the update while I was pushing a few apps and I did adb reboot and before it could finish and I'm still at 6.2 but now I've just disabled all wifi access which sucks.

dev/null/ said:
I was using the Droidwall method all day yesterday and today only allowing Netflix, Youtube, Pandora, Spotify, Onlive, Dolphin HD and Market Place wifi access and Just a few minutes ago my kindle was attempting to download and install the update while I was pushing a few apps and I did adb reboot and before it could finish and I'm still at 6.2 but now I've just disabled all wifi access which sucks.
Click to expand...
Click to collapse
Same err...My WiFi is off.
Until some solid solution is found to stop these forced updates.

Root method likely possible via modified Binary method...

sa·yo·na·ra
ˌsīəˈnärə/

GSLEON3 said:
ABSOLUTELY DO NOT, DO NOT TRY THIS IS WILL LIKELY BRICK YOUR DEVICE!!!
Ok, so I have been able to confirm that using a modified Sony Xperia script, the Binary Root Mothod is able to initiate a desktop restore. HOWEVER, I am woefully unfamiliar with Kindle devices & I have not had time to study the partition structure, so I went no further than initiating the Desktop Full Data Restore mode on the HDX 8.9.
Based on what I have seen thus far, I do believe that root will be possible using existing Binary methods once a HDX desktop backup can be properly modified for these devices. The standard Kindle restore leaves the accept or cancel buttons grayed out. However, as you can see in the attached picture, using a modified version based on a Sony script, allows for the restore selection to be made.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once I have some time, I will see what I can learn about the method Binary uses & see what files are currently included in previous Binary method backup files. In all likelihood, the root process will remain the same for the Kindle line as previous versions. At this time however, unless you know what you are doing, leave well enough alone & lets see what @Hashcode thinks.
Click to expand...
Click to collapse
Just wanted to say thanks for helping the cause.

GSLEON3 said:
ABSOLUTELY DO NOT, DO NOT TRY THIS IS WILL LIKELY BRICK YOUR DEVICE!!!
Ok, so I have been able to confirm that using a modified Sony Xperia script, the Binary Root Mothod is able to initiate a desktop restore. HOWEVER, I am woefully unfamiliar with Kindle devices & I have not had time to study the partition structure, so I went no further than initiating the Desktop Full Data Restore mode on the HDX 8.9.
Based on what I have seen thus far, I do believe that root will be possible using existing Binary methods once a HDX desktop backup can be properly modified for these devices. The standard Kindle restore leaves the accept or cancel buttons grayed out. However, as you can see in the attached picture, using a modified version based on a Sony script, allows for the restore selection to be made.
Once I have some time, I will see what I can learn about the method Binary uses & see what files are currently included in previous Binary method backup files. In all likelihood, the root process will remain the same for the Kindle line as previous versions. At this time however, unless you know what you are doing, leave well enough alone & lets see what @Hashcode thinks.
Click to expand...
Click to collapse
Well at least things are moving here. It's been so sad seeing no development on this thread. I have the KF HDX 7" and willing to offer mine for testing. I've been itching to see at a least root. I also did run the Bin4ry method and the restore reboots but doesn't do anything else.

Really? Unless that's new with the hdx, any backup/restore should work fine. Even if its files are corrupt.
Sent from my KFTT using xda app-developers app

Are you SURE? You know EXACTLY what is pushed in the desktop restore?
I am not familiar with KF Binary or First Aide backup/restore methods, but unless Binary is solely adding the necessary files for root, that could be disastrous. I find it hard to believe that is the case, considering how badly display & performance are affected during the previous HD versions desktop restore methods.
Sent from my Nexus 7 using XDA Premium HD app

GSLEON3 said:
Are you SURE? You know EXACTLY what is pushed in the desktop restore?
I am not familiar with KF Binary or First Aide backup/restore methods, but unless Binary is solely adding the necessary files for root, that could be disastrous. I find it hard to believe that is the case, considering how badly display & performance are affected during the previous HD versions desktop restore methods.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I have manually corrupted files and was able to send them to the device just fine. The restore option was not grayed out, but when you hit that button, it does nothing and just does not restore the data.
Sent from my KFTT using xda app-developers app

r3pwn said:
I have manually corrupted files and was able to send them to the device just fine. The restore option was not grayed out, but when you hit that button, it does nothing and just does not restore the data.
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Be careful. I can tell you that I was at one point able to get the SU binary into a temp folder & copied into xbin, however, when I tried to get bb over as well, the device rebooted & I have not been able to get any ADB connection since. I have reset & removed devices, used different pc's & even factory reset the HDX. After four hours I cannot get any ADB access period.

You try using a terminal on the kindle and manually restarting the adbd service? I'm not aware of if you need root access to do so but maybe you can get some debugging output or just get it working in general by tinkering with this. For reference try something like
Code:
stop adbd
start adbd
Edit: also at this point you technically are rooted, I'm not sure if u have to have an apk to interface with the su binary, but after trying to help my friend root his Alcatel phone (don't get me started), the thing is rooted but while trying to get it switched from using supersu to superuser I believed superuser isn't functioning but we still have root access, and I don't believed superuser is in the/system/app directory, so point being, if u can sideload superuser and es file explorer you might be able to fix the situation if busy box caused the problems.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

good to hear this, hope the rooting method coming out soon!

stunts513 said:
You try using a terminal on the kindle and manually restarting the adbd service? I'm not aware of if you need root access to do so but maybe you can get some debugging output or just get it working in general by tinkering with this. For reference try something like
Code:
stop adbd
start adbd
Edit: also at this point you technically are rooted, I'm not sure if u have to have an apk to interface with the su binary, but after trying to help my friend root his Alcatel phone (don't get me started), the thing is rooted but while trying to get it switched from using supersu to superuser I believed superuser isn't functioning but we still have root access, and I don't believed superuser is in the/system/app directory, so point being, if u can sideload superuser and es file explorer you might be able to fix the situation if busy box caused the problems.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yeah, I've tried just about everything I've ever seen or done to resolve abd issues since 2007. Still a no go. Going to give usb otg a try. Otherwise it's RMA & start over. While the SU binary is in place, I still cannot access it. Calls to SU or trying to open the SU app cause an instantaneous FC & reboot.
I'll tell you though, I really like the tablet. Awesome display & the SD800 w/Adreno 330 flat out rocks. This is totally what the Nexus 10 should have been.
I've also been able to determine that Motorola is the OEM. There are Motorola backup files native to the device at least. I am also going to run this weekend & pick up a 1k transistor, to make a Motorola factory fastboot cable, since I gave mine away with an Xperia tablet. With the factory cable, I should be able to issue fastboot commands. That may enable me to devise a BL unlock.

GSLEON3 said:
Be careful. I can tell you that I was at one point able to get the SU binary into a temp folder & copied into xbin, however, when I tried to get bb over as well, the device rebooted & I have not been able to get any ADB connection since. I have reset & removed devices, used different pc's & even factory reset the HDX. After four hours I cannot get any ADB access period.
Click to expand...
Click to collapse
How are you sure that you got it into xbin?
Sent from my iPod touch using Tapatalk