Jump to content


Photo

[Market] - Ainol Novo 7 Advanced - Enable Full Market (Possibility)


  • Please log in to reply
96 replies to this topic

#41 Jam100

Jam100

    Member

  • Jr. Member
  • PipPip
  • 20 posts

Posted 08 November 2011 - 06:55 PM

Hi,

I think prox32 may have got a full market up and running. Well done mate!

Check out the the gaming thread. He's posted something there about using Galaxy Tab files

http://www.slatedroi...ed/page__st__40

Edited by Jam100, 08 November 2011 - 09:15 PM.


#42 DirectX

DirectX

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 190 posts
  • LocationPhilippines

Posted 08 November 2011 - 07:30 PM

^ what do you mean . . . i want also to access the full market

Posted Image
Ainol Novo 7 Fire
Ainol Novo 7 Aurora II
Ainol Novo 7 Aurora I - V3
Ainol Novo 7 Aurora I - V1
Ainol Novo 7 Advanced


#43 stvewb

stvewb

    Member

  • Jr. Member
  • PipPip
  • 26 posts

Posted 13 November 2011 - 01:41 PM

Before you can do the following steps, you will need to ROOT the device and manually install the Market app.
- I have a script that makes this part relatively easy:
Download Link: Mediafire.com - Tasselhof-RootScript.rar

Once you are rooted and market installed, follow these steps by Roman2025.
Only change the bolded fields.


<hr>

**REQUIRES ROOT ACCESS**

Edit the build.prop file
1) Open Root Explorer
2) Browse to System
3) Click and hold on build.prop (on bottom)
- Scroll down to Edit Text




After you have modified the build.prop.

Follow these directions:

Open Android Market and then Click on Home (launcher)

Go to Settings->Applications->Manage->Running
- Click Market
- Then Clear Cache (NOT CLEAR DATA!!!!)
- Then Force Stop
- Click Google Services Framework
- Click Clear Data
- Click Force Stop

Open Android Market (it will error this is GOOD!)

Shutdown and Restart the tablet
- Wait for Wireless to Kick In
- Wait for System to Finish Loading

Open Android Market
- If it opens without an error GREAT!
- If it opens with the same error... give it a couple minutes or multiple tries at opening (it will go through)


<hr>

Hopefully when all is said and done you will have full market on a Kickn' Device!

Tasselhof


Edited by stvewb, 13 November 2011 - 01:42 PM.


#44 stvewb

stvewb

    Member

  • Jr. Member
  • PipPip
  • 26 posts

Posted 13 November 2011 - 01:46 PM

Before you can do the following steps, you will need to ROOT the device and manually install the Market app.
- I have a script that makes this part relatively easy:
Download Link: Mediafire.com - Tasselhof-RootScript.rar

Once you are rooted and market installed, follow these steps by Roman2025.
Only change the bolded fields.


<hr>

**REQUIRES ROOT ACCESS**

Edit the build.prop file
1) Open Root Explorer
2) Browse to System
3) Click and hold on build.prop (on bottom)
- Scroll down to Edit Text




After you have modified the build.prop.

Follow these directions:

Open Android Market and then Click on Home (launcher)

Go to Settings->Applications->Manage->Running
- Click Market
- Then Clear Cache (NOT CLEAR DATA!!!!)
- Then Force Stop
- Click Google Services Framework
- Click Clear Data
- Click Force Stop

Open Android Market (it will error this is GOOD!)

Shutdown and Restart the tablet
- Wait for Wireless to Kick In
- Wait for System to Finish Loading

Open Android Market
- If it opens without an error GREAT!
- If it opens with the same error... give it a couple minutes or multiple tries at opening (it will go through)


<hr>

Hopefully when all is said and done you will have full market on a Kickn' Device!

Tasselhof



#45 stvewb

stvewb

    Member

  • Jr. Member
  • PipPip
  • 26 posts

Posted 13 November 2011 - 01:48 PM

Will this work with FW 1.8t novo 7 advance. I am new to all this thanks. I have rooted too

#46 Fuzzyman

Fuzzyman

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 31 posts

Posted 15 November 2011 - 10:51 PM

Hi,

I think prox32 may have got a full market up and running. Well done mate!

Check out the the gaming thread. He's posted something there about using Galaxy Tab files

http://www.slatedroi...ed/page__st__40


Trying that one now.... What is a good way to tell that I'm getting the full market? Any apps I can look for that I wouldn't normally see?

#47 Avenger

Avenger

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 46 posts
  • LocationGTA, Ontario, Canada

Posted 16 November 2011 - 11:19 AM

Trying that one now.... What is a good way to tell that I'm getting the full market? Any apps I can look for that I wouldn't normally see?

Try Skype.

#48 Fuzzyman

Fuzzyman

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 31 posts

Posted 17 November 2011 - 12:37 AM

Hmmmm. Don't see Skype in the Market. On the other hand, Asphalt no longer tells me that it isn't compatible with my hardware, so something worked....

#49 f angeles

f angeles

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 36 posts

Posted 19 November 2011 - 11:54 AM

build.prop not working
if you go to https://market.andro...m/account?hl=en

you can see it' s not recognize well , it says maker unknow

Nickname
Unnamed Device



Visibility Maker Model Carrier Last Used Registered On
Shown in menus Unknown DROID2 GLOBAL - - November 19, 2011

==========

does someone know how to reset google account settings or do we have to do a factory settings reset ?

update: found these instructions
1) run this command to get a shell from your device:

adb shell

2) this is the easiest part: rename accounts.db to reset gmail account

run the following commands:

cd /data/system

look for accounts.db

mv accounts.db accounts.db.bak

3)Reboot your phone/tablet and that´s all! You'll be prompted to register or sing in gmail as in the first time

Edited by f angeles, 19 November 2011 - 03:55 PM.


#50 f angeles

f angeles

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 36 posts

Posted 19 November 2011 - 11:59 AM

seemes the build.prop for novo is not complete

e.g. it's missing the gogole.clientid
ro.com.google.clientid=android-motorola

see here : http://www.droidxfor...ull-market.html

#51 fatesausage

fatesausage

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 526 posts
  • LocationTennessee

Posted 19 November 2011 - 02:38 PM

Wo, wo wo, stop! Why does everyone keep saying "Full Market"? I'm pretty sure there's no such thing as "Full Market". Read this post here if you want to understand, and get extended market access, but you'll never get every application as far as I see it, unless you've got the inside track somehow and then I don't even think it's possible, because in the end it's not even really up to Google on who gets what... It's usually the developer of the application that says you have to have these things for it to work. The most interesting was lanosalf's missing permissions....

http://www.slatedroi...post__p__267816

No matter what, you may end up having to stop the market, clear the data etc, before your changes work. So...

Anyway, I stopped by here because I'm thinking about getting a Novo7 or Allwinner based tablet. Any difference? Which would you won, a Rena3 or a Novo7? PM me so we don't change the discussion here...
My Current Tablets:
Renesas Dual/A9 Android 2.2
Rexing V7/Android 4.0.3 (basically a A10 Ployer Momo9)
Cube U18GT Elite--RK3066 Dual Core

Cube U18GT Elite thread


SausageScript for the RK3066 tablets, based on the Cube U18GT 1.06 firmware, still useful for many RK3066 tablets and possibly others

Guide to extended market access, updated on occaision useful for many Android versions


If I helped you, click here to help me, buy me a beer, or some coffee.


SD classifieds
I have a Renesas Rena3 and Momo9 tablets. PM me if you would like to buy one, and I'll give you a deal.


#52 f angeles

f angeles

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 36 posts

Posted 19 November 2011 - 04:01 PM

Wo, wo wo, stop! Why does everyone keep saying "Full Market"? I'm pretty sure there's no such thing as "Full Market". Read this post here if you want to understand, and get extended market access, but you'll never get every application as far as I see it, unless you've got the inside track somehow and then I don't even think it's possible, because in the end it's not even really up to Google on who gets what... It's usually the developer of the application that says you have to have these things for it to work. The most interesting was lanosalf's missing permissions....

http://www.slatedroi...post__p__267816

No matter what, you may end up having to stop the market, clear the data etc, before your changes work. So...

Anyway, I stopped by here because I'm thinking about getting a Novo7 or Allwinner based tablet. Any difference? Which would you won, a Rena3 or a Novo7? PM me so we don't change the discussion here...

ok maybe not full access but what i want

acces to apps 'tested only for other devices' like skype, ...
acces to apps 'restricted to my geographical area/country' ... maybe play with gsm.sim.operator.iso-country
-> not realy sure about this, the market says device not compatible for app (but i am sure it will run on it)
see : https://market.andro...ndroid.sncbnmbs
"This app is incompatible with your Unknown DROID2 GLOBAL.Unknown DROID2 GLOBAL This item is not compatible with your device."

i will try to make some tests with nexus s build.prop mod + gsm.sim.operator.iso-country for my coutry
i will keep u informed, anyone else willing to tests some build.prop ?

#53 f angeles

f angeles

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 36 posts

Posted 19 November 2011 - 04:19 PM

ok first try
========
system crash

adb logcat extract
---
stemui/com.android.systemui.statusbar.StatusBarService}
I/Zygote ( 2232): Process: zygote socket opened
I/ActivityManager( 2232): Start proc com.android.systemui for service com.androi
d.systemui/.statusbar.StatusBarService: pid=2291 uid=1000 gids={3002, 3001, 3003
}
I/ActivityManager( 2232): Config changed: { scale=1.0 imsi=0/0 loc=fr_FR touch=0
keys=0/0/0 nav=0/0 orien=0 layout=0 uiMode=17 seq=2}
E/ProductConfig( 2232): cdma_shadow not have framework config class
W/dalvikvm( 2232): threadid=22: thread exiting with uncaught exception (group=0x
40210560)
W/RecognitionManagerService( 2232): no available voice recognition services foun
d
I/ActivityManager( 2232): Config changed: { scale=1.0 imsi=0/0 loc=fr_FR touch=3
keys=1/1/2 nav=1/1 orien=2 layout=268435491 uiMode=17 seq=3}
E/AndroidRuntime( 2232): *** FATAL EXCEPTION IN SYSTEM PROCESS: WindowManagerPol
icy
E/AndroidRuntime( 2232): java.lang.NullPointerException
E/AndroidRuntime( 2232): at com.android.internal.policy.impl.LockPatternK
eyguardView.getUnlockMode(LockPatternKeyguardView.java:669)
E/AndroidRuntime( 2232): at com.android.internal.policy.impl.LockPatternK
eyguardView.isSecure(LockPatternKeyguardView.java:509)
E/AndroidRuntime( 2232): at com.android.internal.policy.impl.LockPatternK
eyguardView.getInitialMode(LockPatternKeyguardView.java:654)
E/AndroidRuntime( 2232): at com.android.internal.policy.impl.LockPatternK
eyguardView.<init>(LockPatternKeyguardView.java:204)
E/AndroidRuntime( 2232): at com.android.internal.policy.impl.LockPatternK
eyguardViewProperties.createKeyguardView(LockPatternKeyguardViewProperties.java:
48)
E/AndroidRuntime( 2232): at com.android.internal.policy.impl.KeyguardView
Manager.show(KeyguardViewManager.java:125)
E/AndroidRuntime( 2232): at com.android.internal.policy.impl.KeyguardView
Mediator.handleShow(KeyguardViewMediator.java:980)
E/AndroidRuntime( 2232): at com.android.internal.policy.impl.KeyguardView
Mediator.access$700(KeyguardViewMediator.java:94)
E/AndroidRuntime( 2232): at com.android.internal.policy.impl.KeyguardView
Mediator$2.handleMessage(KeyguardViewMediator.java:847)
E/AndroidRuntime( 2232): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 2232): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 2232): at com.android.server.WindowManagerService$Polic
yThread.run(WindowManagerService.java:628)
I/ActivityManager( 2232): Starting: Intent { act=android.intent.action.MAIN cat=
[android.intent.category.HOME] flg=0x10000000 cmp=com.android.launcher/com.andro
id.launcher2.Launcher } from pid 0
D/WifiHW ( 2232): [wifiHW] faied to read proc/net/wireless
D/WifiHW ( 2232): [wifiHW] nano initial,try_time(0)
D/szipinf ( 2232): Initializing inflate state
I/Process ( 2232): Sending signal. PID: 2232 SIG: 9
I/ActivityManager( 2232): Start proc com.android.launcher for activity com.andro
id.launcher/com.android.launcher2.Launcher: pid=2303 uid=10003 gids={}

---------------
:(


here is the build.prop i tried
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GRJ22
ro.build.display.id=crane_aino-eng 2.3.4 GRJ22 eng.flysky.20111108.195110 test-keys
ro.build.version.incremental=eng.flysky.20111108.195110
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=2011年 11月 08日 星期二 19:52:55 CST
ro.build.date.utc=1320753175
ro.build.type=user
ro.build.user=qgd748
ro.build.host=il93lnxdroid09
ro.build.tags=release-keys
ro.product.model=Nexus S
ro.product.brand=verizon
ro.product.name=shadow_vzw
ro.product.device=cdma_shadow
ro.product.board=shadow
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=exDroid
# ro.build.product is obsolete; use ro.product.device
ro.build.product=shadow_vzw
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=cdma_shadow-user 2.3.3 4.5.1_57_DX5-18 110410 release-keys
ro.build.fingerprint=verizon/shadow_vzw/cdma_shadow/shadow:2.2.1/VZW/23.340:user/ota-rel-keys,release-keys
# end build properties

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapsize=32m
debug.egl.hw=1
ro.opengles.version=131072
ro.ril.wake_lock_timeout=1000
ro.kernel.android.checkjni=0
persist.sys.timezone=Asia/Shanghai
persist.sys.language=zh
persist.sys.country=CN
ro.additionalmounts=/mnt/extern_sd;;/mnt/usbhost1
ro.additionalshares=/mnt/extern_sd;
ro.udisk.lable=Novo7
gsm.version.baseband=1.80_Beta2
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.com.google.clientid=android-motorola
ro.com.google.clientidbase=android-verizon
ro.com.google.clientidbase.am=android-verizon
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientid=android-motorola
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.mot.hw.uaprof=http://uaprof.motorola.com/phoneconfig/MotoMB200/profile/MotoMB200.rdf
ro.build.version.full=Blur_Version.4.5.588.MB810.Verizon.en.US
gsm.sim.operator.numeric : 20601
gsm.operator.numeric : 20601
gsm.sim.operator.iso-country : be
gsm.operator.iso-country : be
gsm.sim.operator.alpha : Proximus
gsm.operator.alpha : Proximus

==============
i recovered via adb push /shell and a copy of a good build.prop
nasty thing this build.prop ...
i will retry tomorrow or in a few days

#54 fatesausage

fatesausage

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 526 posts
  • LocationTennessee

Posted 19 November 2011 - 04:45 PM

ok first try
========
system crash

adb logcat extract
---
stemui/com.android.systemui.statusbar.StatusBarService}
I/Zygote ( 2232): Process: zygote socket opened
I/ActivityManager( 2232): Start proc com.android.systemui for service com.androi
d.systemui/.statusbar.StatusBarService: pid=2291 uid=1000 gids={3002, 3001, 3003
}
I/ActivityManager( 2232): Config changed: { scale=1.0 imsi=0/0 loc=fr_FR touch=0
keys=0/0/0 nav=0/0 orien=0 layout=0 uiMode=17 seq=2}
E/ProductConfig( 2232): cdma_shadow not have framework config class
W/dalvikvm( 2232): threadid=22: thread exiting with uncaught exception (group=0x
40210560)
W/RecognitionManagerService( 2232): no available voice recognition services foun
d
I/ActivityManager( 2232): Config changed: { scale=1.0 imsi=0/0 loc=fr_FR touch=3
keys=1/1/2 nav=1/1 orien=2 layout=268435491 uiMode=17 seq=3}
E/AndroidRuntime( 2232): *** FATAL EXCEPTION IN SYSTEM PROCESS: WindowManagerPol
icy
E/AndroidRuntime( 2232): java.lang.NullPointerException
E/AndroidRuntime( 2232): at com.android.internal.policy.impl.LockPatternK
eyguardView.getUnlockMode(LockPatternKeyguardView.java:669)
E/AndroidRuntime( 2232): at com.android.internal.policy.impl.LockPatternK
eyguardView.isSecure(LockPatternKeyguardView.java:509)
E/AndroidRuntime( 2232): at com.android.internal.policy.impl.LockPatternK
eyguardView.getInitialMode(LockPatternKeyguardView.java:654)
E/AndroidRuntime( 2232): at com.android.internal.policy.impl.LockPatternK
eyguardView.<init>(LockPatternKeyguardView.java:204)
E/AndroidRuntime( 2232): at com.android.internal.policy.impl.LockPatternK
eyguardViewProperties.createKeyguardView(LockPatternKeyguardViewProperties.java:
48)
E/AndroidRuntime( 2232): at com.android.internal.policy.impl.KeyguardView
Manager.show(KeyguardViewManager.java:125)
E/AndroidRuntime( 2232): at com.android.internal.policy.impl.KeyguardView
Mediator.handleShow(KeyguardViewMediator.java:980)
E/AndroidRuntime( 2232): at com.android.internal.policy.impl.KeyguardView
Mediator.access$700(KeyguardViewMediator.java:94)
E/AndroidRuntime( 2232): at com.android.internal.policy.impl.KeyguardView
Mediator$2.handleMessage(KeyguardViewMediator.java:847)
E/AndroidRuntime( 2232): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 2232): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 2232): at com.android.server.WindowManagerService$Polic
yThread.run(WindowManagerService.java:628)
I/ActivityManager( 2232): Starting: Intent { act=android.intent.action.MAIN cat=
[android.intent.category.HOME] flg=0x10000000 cmp=com.android.launcher/com.andro
id.launcher2.Launcher } from pid 0
D/WifiHW ( 2232): [wifiHW] faied to read proc/net/wireless
D/WifiHW ( 2232): [wifiHW] nano initial,try_time(0)
D/szipinf ( 2232): Initializing inflate state
I/Process ( 2232): Sending signal. PID: 2232 SIG: 9
I/ActivityManager( 2232): Start proc com.android.launcher for activity com.andro
id.launcher/com.android.launcher2.Launcher: pid=2303 uid=10003 gids={}

---------------
:(


here is the build.prop i tried
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GRJ22
ro.build.display.id=crane_aino-eng 2.3.4 GRJ22 eng.flysky.20111108.195110 test-keys
ro.build.version.incremental=eng.flysky.20111108.195110
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=2011年 11月 08日 星期二 19:52:55 CST
ro.build.date.utc=1320753175
ro.build.type=user
ro.build.user=qgd748
ro.build.host=il93lnxdroid09
ro.build.tags=release-keys
ro.product.model=Nexus S
ro.product.brand=verizon
ro.product.name=shadow_vzw
ro.product.device=cdma_shadow
ro.product.board=shadow
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=exDroid
# ro.build.product is obsolete; use ro.product.device
ro.build.product=shadow_vzw
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=cdma_shadow-user 2.3.3 4.5.1_57_DX5-18 110410 release-keys
ro.build.fingerprint=verizon/shadow_vzw/cdma_shadow/shadow:2.2.1/VZW/23.340:user/ota-rel-keys,release-keys
# end build properties

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapsize=32m
debug.egl.hw=1
ro.opengles.version=131072
ro.ril.wake_lock_timeout=1000
ro.kernel.android.checkjni=0
persist.sys.timezone=Asia/Shanghai
persist.sys.language=zh
persist.sys.country=CN
ro.additionalmounts=/mnt/extern_sd;;/mnt/usbhost1
ro.additionalshares=/mnt/extern_sd;
ro.udisk.lable=Novo7
gsm.version.baseband=1.80_Beta2
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.com.google.clientid=android-motorola
ro.com.google.clientidbase=android-verizon
ro.com.google.clientidbase.am=android-verizon
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientid=android-motorola
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.mot.hw.uaprof=http://uaprof.motorola.com/phoneconfig/MotoMB200/profile/MotoMB200.rdf
ro.build.version.full=Blur_Version.4.5.588.MB810.Verizon.en.US
gsm.sim.operator.numeric : 20601
gsm.operator.numeric : 20601
gsm.sim.operator.iso-country : be
gsm.operator.iso-country : be
gsm.sim.operator.alpha : Proximus
gsm.operator.alpha : Proximus

==============
i recovered via adb push /shell and a copy of a good build.prop
nasty thing this build.prop ...
i will retry tomorrow or in a few days


Your description and fingerprint don't match, you've got froyo for one and gingerbread for the other, plus it's in there 2 times... Do a getprop from adb and see what your values are showing up as. Your OS version needs to be the same throughout (2.2.1 and 2.3.4 and so on)... Also, not sure you need the GSM information you have. The less the better, take a good look at the post I sent you and you'll see I covered a good bit of this information. I would just take the default build.prop and add/change what you need till it works like you want it to.

Also there are some prop editors on the market, that you can use to edit build.prop and change the values till you get it right, most of them will sort by property and that can be helpful...

Edited by fatesausage, 19 November 2011 - 04:51 PM.

My Current Tablets:
Renesas Dual/A9 Android 2.2
Rexing V7/Android 4.0.3 (basically a A10 Ployer Momo9)
Cube U18GT Elite--RK3066 Dual Core

Cube U18GT Elite thread


SausageScript for the RK3066 tablets, based on the Cube U18GT 1.06 firmware, still useful for many RK3066 tablets and possibly others

Guide to extended market access, updated on occaision useful for many Android versions


If I helped you, click here to help me, buy me a beer, or some coffee.


SD classifieds
I have a Renesas Rena3 and Momo9 tablets. PM me if you would like to buy one, and I'll give you a deal.


#55 minibeats

minibeats

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 208 posts

Posted 19 November 2011 - 07:25 PM

So, after updating to the 1.8 B2, I'm looking to change the build prop so that it thinks it's a droid. I've seen in the previous posts what needs changing with earlier firmware, but I was wondering if I need to change anything else on the build prop to say 1.8 Beta 2 as well, as the build prop info listed earlier is for earlier firmware. Anyone know?

Either that, or could someone upload the correct buildprop for 1.8 b2 to enable more of the market so I can just download it and paste it in the correct place?

#56 Khiem

Khiem

    Member

  • Jr. Member
  • PipPip
  • 13 posts

Posted 24 November 2011 - 07:46 PM

I have done all of the steps and when I reboot my device, it turns back to the normal build.prop. Any advice?

#57 minibeats

minibeats

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 208 posts

Posted 24 November 2011 - 10:01 PM

I have done all of the steps and when I reboot my device, it turns back to the normal build.prop. Any advice?


I''m assuming you are on either firmware 1.8t or 1.8 b2.
If so, go to topnotchtablets.com and click on product support along the top bar. Click on Novo 7 advanced and download the automod tool kit. Run like Taselhoff's script, but you will see there is an option (I think number 6) to replace the old build prop with the new one. Run that and it should do it for you. I MUST repeat, I have done this on only firmwares 1.8t and 1.8 b2 - if you are on another firmware then either update or reply and we can see why it's not working.

#58 Khiem

Khiem

    Member

  • Jr. Member
  • PipPip
  • 13 posts

Posted 25 November 2011 - 12:31 AM

I''m assuming you are on either firmware 1.8t or 1.8 b2.
If so, go to topnotchtablets.com and click on product support along the top bar. Click on Novo 7 advanced and download the automod tool kit. Run like Taselhoff's script, but you will see there is an option (I think number 6) to replace the old build prop with the new one. Run that and it should do it for you. I MUST repeat, I have done this on only firmwares 1.8t and 1.8 b2 - if you are on another firmware then either update or reply and we can see why it's not working.



My android won't boot now , its stuck in the shiny android and it keeps repeating the bootscreen. :(

#59 Khiem

Khiem

    Member

  • Jr. Member
  • PipPip
  • 13 posts

Posted 25 November 2011 - 12:50 AM

Please help guys, i'm panicking. This is my brother's tablet. He's going to kill me :(

#60 minibeats

minibeats

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 208 posts

Posted 25 November 2011 - 02:10 AM

Please help guys, i'm panicking. This is my brother's tablet. He's going to kill me :(


You have Ainol Novo Basic!!!? Oh dear..

Edited by minibeats, 25 November 2011 - 04:08 AM.