Jump to content

Newest i9000 firmware with protected apps access?


Guest seraphine
 Share

Recommended Posts

Guest seraphine

Access to protected apps in the market requires the usage of an officially released firmware which the manufacturer has made Google aware of, correct?

Which is the NEWEST version of the firmware that is considered official in this manner? I am from the Asian region, therefore I notice that the EU firmware is much farther along than Asian region.

Which of the EU firmware is the newest, official release?

I've been looking, but it's a little hard to tell...

Link to comment
Share on other sites

Guest ryukent
Access to protected apps in the market requires the usage of an officially released firmware which the manufacturer has made Google aware of, correct?

Which is the NEWEST version of the firmware that is considered official in this manner? I am from the Asian region, therefore I notice that the EU firmware is much farther along than Asian region.

Which of the EU firmware is the newest, official release?

I've been looking, but it's a little hard to tell...

I'd use JG5. It's the most stable firmware. Also, you don't need the lag fix because memory management has been fixed. Actually there is a hack to enable all the market software on any firmware. See this post:

http://forum.xda-developers.com/showpost.p...amp;postcount=2

Link to comment
Share on other sites

Guest FerdiBorbon

too much stuffing around just download "Eris Market Fix" from the market...

after it installs run the Application, then turn off your Galaxy S, the boot into recovery mode by holding (Home button + Volume Up button + Power Button)

when you get into recovery mode, scroll to wipe clear cache, then select rebbot.

Then wait about 5 mins and then the paid apps will appear :angry:

enjoy!! well it worked for me!

Link to comment
Share on other sites

Guest DistortedLoop
too much stuffing around just download "Eris Market Fix" from the market...

after it installs run the Application, then turn off your Galaxy S, the boot into recovery mode by holding (Home button + Volume Up button + Power Button)

when you get into recovery mode, scroll to wipe clear cache, then select rebbot.

Then wait about 5 mins and then the paid apps will appear :angry:

enjoy!! well it worked for me!

LOL, where was this post a couple of hours ago before I manually fixed my market access on JG5 by manually replacing build.prop and then manually clearing the cache directory and dalvik-cache directory for the vending app? ;-)

Making note of Eris Market Fix for future reference.

Link to comment
Share on other sites

Guest kanzlr

you just have to push the build.prop from JG1 or any other protected apps enabled build to your phone.

google "build.prop push samsun galaxy i9000" or something like that and a few threads pop up about this issue.

I use JG5 with a build prop i found on a german forum for the galaxy and it works nicely.

Link to comment
Share on other sites

Guest miker71
too much stuffing around just download "Eris Market Fix" from the market...

after it installs run the Application, then turn off your Galaxy S, the boot into recovery mode by holding (Home button + Volume Up button + Power Button)

when you get into recovery mode, scroll to wipe clear cache, then select rebbot.

Then wait about 5 mins and then the paid apps will appear :angry:

enjoy!! well it worked for me!

+1 worked here too (JG5 + SamDroid root) though I'm not sure how long it took to work (I initially thought it didn't work) - but an hour or two later I checked and there they all were.

Link to comment
Share on other sites

Guest DistortedLoop
I'd use JG5. It's the most stable firmware. Also, you don't need the lag fix because memory management has been fixed. Actually there is a hack to enable all the market software on any firmware. See this post:

http://forum.xda-developers.com/showpost.p...amp;postcount=2

That's the hack I actually used, but if you read the whole thread for that one, it fails for a couple of respondents (and me as well) unless you manually clear the cache and dalvik-cache related to to *vending* as well.

You also have to actually kill Market app with a task manager as well:

Kill Market

clear/delete cache for com.android.vending

clear/delete dalvik-cache for *vending*

replace build.prop with the linked one that works

reboot phone.

Protected apps were there for me as soon as the phone booted.

Caution is warranted - there's a thread on here where a guy bricked his phone (won't boot other than recovery) because he used the wrong build.prop.

Also, can build.prop be edited with a text editor? Might be easier to just edit the proper line(s), but with any method, make sure you have good backup of the file.

Link to comment
Share on other sites

Guest seraphine

Cheers mate! Gonna give that a go :angry:

too much stuffing around just download "Eris Market Fix" from the market...

after it installs run the Application, then turn off your Galaxy S, the boot into recovery mode by holding (Home button + Volume Up button + Power Button)

when you get into recovery mode, scroll to wipe clear cache, then select rebbot.

Then wait about 5 mins and then the paid apps will appear :D

enjoy!! well it worked for me!

Link to comment
Share on other sites

Guest hihihehe
too much stuffing around just download "Eris Market Fix" from the market...

after it installs run the Application, then turn off your Galaxy S, the boot into recovery mode by holding (Home button + Volume Up button + Power Button)

when you get into recovery mode, scroll to wipe clear cache, then select rebbot.

Then wait about 5 mins and then the paid apps will appear :(

enjoy!! well it worked for me!

i just used this method and not sure it works or not..

can any1 list any example of protected apps?

Link to comment
Share on other sites

Guest kanzlr

JG5 is smoother, yes, but it doesn't fix the slow DB read/write speeds that hamper some apps, like "Got To Do".

this app is SO much faster with JG5+ext4 than just JG5, it is amazing. Samsung screwed something up regarding the access times to the application data.

That's the hack I actually used, but if you read the whole thread for that one, it fails for a couple of respondents (and me as well) unless you manually clear the cache and dalvik-cache related to to *vending* as well.

You also have to actually kill Market app with a task manager as well:

Kill Market

clear/delete cache for com.android.vending

clear/delete dalvik-cache for *vending*

replace build.prop with the linked one that works

reboot phone.

Protected apps were there for me as soon as the phone booted.

Caution is warranted - there's a thread on here where a guy bricked his phone (won't boot other than recovery) because he used the wrong build.prop.

Also, can build.prop be edited with a text editor? Might be easier to just edit the proper line(s), but with any method, make sure you have good backup of the file.

Link to comment
Share on other sites

Guest DistortedLoop
JG5 is smoother, yes, but it doesn't fix the slow DB read/write speeds that hamper some apps, like "Got To Do".

this app is SO much faster with JG5+ext4 than just JG5, it is amazing. Samsung screwed something up regarding the access times to the application data.

Could the problem actually be with the "Got To Do" app itself? Just curious why some apps seem impacted and others don't on just JG5.

I asked the author of the Benchmark app what directory he writes to with his i/o, but he never responded.

What we really need is a benchmarking app that lets us specify disk read/write tests only, and lets us specify which disk (internal vs external vs ext) so that we can settle this once and for all.

This fork of the discussion probably belongs in a different thread at this pont.

Link to comment
Share on other sites

Guest kanzlr
Could the problem actually be with the "Got To Do" app itself? Just curious why some apps seem impacted and others don't on just JG5.

I asked the author of the Benchmark app what directory he writes to with his i/o, but he never responded.

What we really need is a benchmarking app that lets us specify disk read/write tests only, and lets us specify which disk (internal vs external vs ext) so that we can settle this once and for all.

This fork of the discussion probably belongs in a different thread at this pont.

yep, quite possible. Maybe his DB writes are somewhat non-optimal.

Still it shows that it improves the device speed.

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.