I'm trying to get my G tab to work with the new Market.
What's happening now is that it's being recognized as a Samsung SPH100 due to the build.prop changes I did to enable the Swype keyboard. I believe that this is preventing me from being able to download items from the new market where others are able to.
Can anyone either post up their build.prop or PM me it if possible?
I have done a search for this but can't find it. If someone can prove my searching abilities are weak and can point me to where I missed it, I welcome that too.
OK, 147 views and no file.
Tell you what, could someone on Vegan-Tab 5.1 copy and paste the text from their build.prop into a response on this thread? That should be easy enough.
I really don't want to reinstall Vegan-tab just to get that file.
Puhleeeese!!
dvus said:
OK, 147 views and no file.
Tell you what, could someone on Vegan-Tab 5.1 copy and paste the text from their build.prop into a response on this thread? That should be easy enough.
I really don't want to reinstall Vegan-tab just to get that file.
Puhleeeese!!
Click to expand...
Click to collapse
Didn't you back it up?
Here's mine. You will have to remove the ".txt" from the file name before use.
Thanks!!
Yeah, when you edit the build.prop the old file get's backed up. Buuuut, be aware when you edit the file again and save it, it will over write the previously backed up file. Doh!!
Hopefully this posts help people but it looks like I resolved how the Market sees my G Tab.
Although it did take a while. Not sure if it was a combination of what my actions were or just some time for the identifiers in the build.prop to kick in.
All in all, it took approx. 1hr for my tablet to now be recognized as a Vegan. I am now able to download and install apps from the web market.
To help people figure out what's going on all I did was the following in the following order.
1. replace the build.prop
2. restart the G-Tab - still showing up as Samsung SPH in web market
3. did market fix by:
a. Market, cleared cache, data and stopped service.
b. Google Framework Services, cleared data and stopped service.
c. Accessed Market and received error.
d. Restarted G-Tab
e. Accessed Market and downloaded and installed a few apps.
My G-Tab was still recognized as a Samsung SPH on the web Market. After about an hour, it showed up as a Vegan on the web Market and I was able to download and install apps from the web Market although some apps are apparently identified as incompatible.
similar problem! please help!?
i made some changes to my build.prop file and i wrecklessly didnt back it up. i have a viewsonic gtablet running vegan tab 7 ginger ed. if anyone would be kind enough to post a copy of their build.prop file, i would be eternally greatful. im trying to buy apps from the market and it doesnt recognize me as a tablet like before. thanks again.
Here is mine from VEGAn 5.1.1
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FRF91
ro.build.display.id=harmony 2.2 FRF91 20101123.172729
ro.build.version.incremental=20101123.172729
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=Thu Dec 30 19:30:00 EST 2010
ro.build.date.utc=1293755400
ro.build.type=eng
ro.build.user=root
ro.build.host=ant-build
ro.build.tags=test-keys
ro.product.model=VEGAn-TAB-v1.0.0b5.1.1
ro.product.brand=nvidia
ro.product.name=Vega
ro.product.device=Vega
ro.product.board=Vega
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=nvidia
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=Vega
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=harmony-eng 2.2 FRF91 20101123.172729 test-keys
# ro.build.fingerprint=nvidia/harmony/harmony/harmony:2.2/FRF91/20101123.172729:eng/test-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
ro.config.sync=no
ro.media.dec.vid.wmv.enabled=1
ro.media.dec.aud.wma.enabled=1
ro.media.enc.hprof.file.format=3gp
ro.media.enc.hprof.aud.hz=44100
ro.media.enc.hprof.aud.ch=2
ro.media.enc.hprof.codec.aud=aac
ro.media.enc.hprof.aud.bps=128000
ro.browser.useragent=1
persist.service.mount.umsauto=1
dalvik.vm.minheapsize=4m
dalvik.vm.heapsize=64m
EXTERNAL_STORAGE_MOUNT=/mnt/sdcard
persist.tegra.dpy5.mode.width=1920
persist.tegra.dpy5.mode.height=1080
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
#
# VEGANTAB additional
#
persist.service.adb.enable=1
ro.setupwizard.mode=DISABLED
dalvik.vm.checkjni=false
ro.kernel.android.checkjni=false
windowsmgr.max_events_per_sec=60
ro.opengles.version=131072
Thank you for the reply, but i need build.prop info for vegan-7.0.0 RC1-Harmony, running on gtablet. Anybody else?
You can get this file from within the update.zip Open the VEGAn 7.0 (or almost any other ROM you want the file from) update.zip then go into the system folder. The build.prop is right there.
Related
Hey this thread should be for all german users and problems occuring on german G1s , i would suggest that german users who have problems downgrading or rooting the G1 can posthere,
i would like to know if someone with an German G1 has already downgraded the device!
well everybody is waiting for a messias
some tried to downgrade but did not succeed..
there are 2 possibilities
1 - someone alters the american downgrade with a different CID or whatever keeps it from running on our G1
2 - some european linux pros find an exploit in our firmware
rc33
What if we get the RC33 update[version 1.5]? Can we downgrade to RC29 then?
I'm a Dutch G1 user, same build thus. Also waiting for root access, for tethering & auto rotate mainly.
As i mentioned in other threads we all got the same issues with downgrading/becoming root/chanching hte bootloader/do anything weird with this device..
My spec are:
Model Info:
T-mobile G1
Firmware version :
1.1
Basebandversion:
62.33.20.08U_1.22.12.29
Kernel version:
2.5.25-01843-gfea26b0
[email protected] #6
Build number:
123099
Bootscreen says:
DREA110 PVT 32B
HBOOT-0.95.000
CPLD-4
RADIO-1.22.12.29
SEP 2 2008
When booting o the update.zip it seays: Finding - / opening - /verifying update package and then at "installing update" package it prompts:
Code:
E:Failure at line1:
assert file_contains("SYSTEM:build.prop", " ro.build.fingerprint=tmobile/kila/dream/trout:1.0/TC4-RC30/116143:user/ota-rel-keys, release-keys") == "true" || file_contains("SYSTEM:build.prop", "ro.build.fingerprint=tmobile/kila/dream/troInstallation aborted.
any ideas?
Do the others have the same issues?
I thiunk i will wait for other comanies to sell android-able phones and get one of their's.
Spent about 20 Hours now on googleing and searching. That usually should do it 10 ten times trying to solve any problem with linux, but it doesn't.
It occurs to me that android isn'T as free as they say and that it isn't as opensource as everybody is told. That's CRAP!
dirty_ said:
It occurs to me that android isn'T as free as they say and that it isn't as opensource as everybody is told. That's CRAP!
Click to expand...
Click to collapse
Please search "open source" on the dream forums. This stupid bs has been gone over before.
German G1s with the new CID can NOT be downgraded with the available leak NBH files. CID mismatch. They also can NOT be upgraded with RC33 update.zip files, as updaters are region specific (assertion in the update script that checks the device's existing fingerprint against an allowed list).
Long story short: German G1 owners have to wait for now.
dirty_ said:
I thiunk i will wait for other comanies to sell android-able phones and get one of their's.
Spent about 20 Hours now on googleing and searching. That usually should do it 10 ten times trying to solve any problem with linux, but it doesn't.
It occurs to me that android isn'T as free as they say and that it isn't as opensource as everybody is told. That's CRAP!
Click to expand...
Click to collapse
Example of someone who does not read, just *****es. The OS is open, the device is not. Blame your cell provider, not Android. Also go read a few threads and by all means, return your G1 and buy something later after you have done some reading.
You can also debate in german here.
hopefully they will fix this issue ...
hm, i'm also waiting for a solution, i've allready asked JF but didn't get an answer yet
when you can't contribute, you're in a really bad position to get an answer
when you have a good idea in how doing this, I'm sure JFv is willing to help...
Can you made a package which install telnet server?
I didnt understand what exact happened when you install a new application, I think it install as root???
seriously waiting for the DREAIMG.nbh for german t-mobile G1.
seriously waiting for the DREAIMG.nbh for german t-mobile G1.
I updated my german t-mobile G1 from rc29 to rc33.
after i upgrade my g1 to rc33 i keep getting an sms from an operator number every 5 minutes. I have to disable the notifications for the text messages cuz I have 36 sms from the same operator and it's getting more.It's annoying.
and the number is +491770702600 . i don't use an t-mobile sim card. my sim card is from e-plus.
I didn't have any problems until i upgraded the g1.
can't downgrade.have read about "SoftSPL Flash any ROM" for fake changing the CID but it's too complicated :S
anyone has the same problem?
Yes the same exactly , i just update it with the:
https://android.clients.google.com/updates/signed-kila-ota-126986.f6469a1e.zip
to rc33 and get the f.... sms all the time, any ideas anyone out there
emiliosdance:
you have a t-mobile sim?
The signed-kila-ota-126986.f6469a1e.zip is a USA RC33 Update...
I dont know why it run on German G1, and the Downgrade RC29 not...
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=PLAT-RC33
ro.build.version.incremental=126986
ro.build.version.sdk=2
ro.build.version.release=1.1
ro.build.date=Fri Jan 16 15:36:09 PST 2009
ro.build.date.utc=1232148969
ro.build.type=user
ro.build.user=android-build
ro.build.host=apa1.mtv.corp.google.com
ro.build.tags=ota-rel-keys,release-keys
ro.product.model=T-Mobile G1
ro.product.brand=tmobile
ro.product.name=kila
ro.product.device=dream
ro.product.board=trout
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
# ro.build.product is obsolete; use ro.product.device
ro.build.product=dream
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=kila-user 1.1 PLAT-RC33 126986 ota-rel-keys,release-keys
ro.build.fingerprint=tmobile/kila/dream/trout:1.1/PLAT-RC33/126986:user/ota-rel-keys,release-keys
# end build properties
#
# system.prop for dream
#
rild.libpath=/system/lib/libhtc_ril.so
wifi.interface = tiwlan0
ro.ril.oem.ecclist = 999,000,08,118,112,120,122,110,119
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.google.clientid=tmobile-us
Click to expand...
Click to collapse
Cause of the rom signature, you can not install der RC29 rom. Your G1 is not able to boot this rom.
Fix it
I just did this update , and it worked , hope that i will not get the messages again:
https://android.clients.google.com/updates/signed-PLAT-RC33-from-RC30.f06aa9b3.zip
what is the diffrent from
signed-kila-ota-126986.f6469a1e.zip
The fix did not work.
The update proses is a little more detailed but the f.....messages still coming.
I am trying now to change the boot loader so i can downgrade, since the German g1 give no access to it.
any ideas
How to root the Changhong Z-me:
You can use SuperOneClick (any version) Google it...
When you plug your phone in make sure usb debugging is ticked (in settings)
Also make sure install from unknown sources is ticked
When you plug your phone in it will prompt to install drivers DONT!!!! ignore it!!
Open SOC it will detect but will prompt to install drivers (general ADB drivers) click install!!
THEN SIMPLY CLICK ROOT!!
Play Store FIX!!!
This not a flashable ZIP!!
SORRY BUT YOU HAVE TO DO IT MANUALLY...
Download the FIX: http://www.4shared.com/zip/RQdAxsy8/ChanghongPlayStoreFIX.html
Copy to SD-CARD
Install ES-File Explorer
go into es-file explorer settings> sort by> Modified> Descending
tick root explorer, up to root and mount file system.
click select multiple items> copy the contents from system/app to the android system/app and so on...
reboot and should be done!!!
LINK your Google account!!
REMEMBER THE FILE PERMISSION ARE THE SAME FOR ALL THE CONTENTS IN THE ZIP you have to change them manually
x-x-x
x- -
x- -
Also a CWM recovery for the Changhong Z-me
http://www.dashifu.com/forum.php?mod=viewthread&tid=391&fromuid=2
rayner123 said:
How to root the Changhong Z-me:
You can use SuperOneClick (any version) Google it...
When you plug your phone in make sure usb debugging is ticked (in settings)
Also make sure install from unknown sources is ticked
When you plug your phone in it will prompt to install drivers DONT!!!! ignore it!!
Open SOC it will detect but will prompt to install drivers (general ADB drivers) click install!!
THEN SIMPLY CLICK ROOT!!
Play Store FIX!!!
This not a flashable ZIP!!
SORRY BUT YOU HAVE TO DO IT MANUALLY...
Download the FIX:
Copy to SD-CARD
Install ES-File Explorer
go into es-file explorer settings> sort by> Modified> Descending
tick root explorer, up to root and mount file system.
click select multiple items> copy the contents from system/app to the android system/app and so on...
reboot and should be done!!!
LINK your Google account!!
REMEMBER THE FILE PERMISSION ARE THE SAME FOR ALL THE CONTENTS IN THE ZIP you have to change them manually
x-x-x
x- -
x- -
Click to expand...
Click to collapse
Hey thanks for your interest in this nice phone and in my thread!
Sorry for late reply but yesterday I managed to install Google Play with a tutorial from this site too but for Kindle Fire.
I used Root Explorer and have done as you say too and it works flawlessly ^^.
The problem is that I don't know how to install a recovery.
I hope more people have this nice phone and we are able to share as much info as we can, I really like it. My last phone was a Samsung Galaxy Spica and I am tired of it because it's crap >_<.
Thank you so much for you effort!
P.S: btw, I would want to know whether there are different versions of GoogleFramework or Vending, because I don't know if they have to be the same for it to work. I mean, with the actual Google Framework and Vending I can still continue updating Google Play app or it will crash since I have to update to the same version the other two?
nobitakun said:
Hey thanks for your interest in this nice phone and in my thread!
Sorry for late reply but yesterday I managed to install Google Play with a tutorial from this site too but for Kindle Fire.
I used Root Explorer and have done as you say too and it works flawlessly ^^.
The problem is that I don't know how to install a recovery.
I hope more people have this nice phone and we are able to share as much info as we can, I really like it. My last phone was a Samsung Galaxy Spica and I am tired of it because it's crap >_<.
Thank you so much for you effort!
P.S: btw, I would want to know whether there are different versions of GoogleFramework or Vending, because I don't know if they have to be the same for it to work. I mean, with the actual Google Framework and Vending I can still continue updating Google Play app or it will crash since I have to update to the same version the other two?
Click to expand...
Click to collapse
no, play store wont crash you can still continue updating the app!!
rayner123 said:
no, play store wont crash you can still continue updating the app!!
Click to expand...
Click to collapse
Hey I have a question about your procedure: what's the use of ETC, FRAMEWORK and LIB folders?, I just moved all the apk and fixed permissions and everything works fine. I could even install Google Maps and use it without problems and I can see inside FRAMEWORK folder there's something related with Google Maps so in the PERMISSIONS folder.
Just installing the apk's will give me any problem in the future?
Thanks for your effort!
nobitakun said:
Hey I have a question about your procedure: what's the use of ETC, FRAMEWORK and LIB folders?, I just moved all the apk and fixed permissions and everything works fine. I could even install Google Maps and use it without problems and I can see inside FRAMEWORK folder there's something related with Google Maps so in the PERMISSIONS folder.
Just installing the apk's will give me any problem in the future?
Thanks for your effort!
Click to expand...
Click to collapse
no they shouldn't be a problem. Just got my changhong z-me into a boot loop sort of thing thing it boots to the wo 3g then reboots! Just installed the beats audio installer from play store!! I repent doing it!!!!
rayner123 said:
no they shouldn't be a problem. Just got my changhong z-me into a boot loop sort of thing thing it boots to the wo 3g then reboots! Just installed the beats audio installer from play store!! I repent doing it!!!!
Click to expand...
Click to collapse
Ohhh, I'm so sorry.
Can't you put the phone into Download Mode by pressing volume+ power buton?
I wonder how to do a firmware backup so you can restore the phone with it using Odin and return it to life. I would be good in case we do further unsuccessful moves T_T. It's a pity I'm not an android developer or pro and I can't help you as much as I would want, sorry.
nobitakun said:
Ohhh, I'm so sorry.
Can't you put the phone into Download Mode by pressing volume+ power buton?
I wonder how to do a firmware backup so you can restore the phone with it using Odin and return it to life. I would be good in case we do further unsuccessful moves T_T. It's a pity I'm not an android developer or pro and I can't help you as much as I would want, sorry.
Click to expand...
Click to collapse
This incident wouldn't have happened if i had a backup and restore function in recovery!! I have found a chinese website with the changhong z-me firmware but i cant download because I'm a newbie apparently i have to 52 prestiege to download?! I think the firmware is a .nb0 as in the recovery there is a option for "download nb0 from sd card". I have found a website on how port CWM. http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-os-x-part1/
Good news is i got a z-me firmware but when i flash PID doesnt match or something. Dude can you plz do me a favour. If u can check for update for ur phone and then share it on this thread! So i can recover my phone.
Dude can u plz provide me ur phones build.prop (it hasnt got anything personal (just incase your wondering )) i just need to check something as i cant access my phone.
Thanks
Hello, sorry for late reply!.
Well, I don't know how to check PID, the info I cal tell you is:
Baseband Version: PCR
Kernel Version: Apps_2.6.32.9-perf
Build Number: 7001_3_180
I don't know whether that info is useful to you, but that's what it says in the "about phone" section, among other trivial things.
And as for the update you say, there's a "check for updates" option inside the phone, but it always says there's no update avaliable.
I will try to find some info about the phone in some chinese sites.
About the build.prop thing you say, I paste you the text:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GWK74
ro.build.display.id=GWK74
ro.build.version.incremental=7001_3_30B
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Fri Nov 4 17:33:01 CST 2011
ro.build.date.utc=1320399181
ro.build.type=user
ro.build.user=user
ro.build.host=user-hostname
ro.build.tags=release-keys
ro.product.model=ChangHong-Z-ME
ro.product.brand=ChangHong
ro.product.name=ChangHong-Z-ME
ro.product.device=z-me
ro.product.board=Z-ME
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=FIH
ro.product.locale.language=zh
ro.product.locale.region=CN
ro.wifi.channels=
ro.board.platform=msm7k
# ro.build.product is obsolete; use ro.product.device
ro.build.product=z-me
service.config.gsensor_cal=1
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=ChangHong-Z-ME-user 2.3.7 GWK74 7001_3_30B release-keys
ro.build.fingerprint=ChangHong/ChangHong-Z-ME/z-me:2.3.7/GWK74/7001_3_30B:user/release-keys
ro.telephony.fdn.data=
# end build properties
#
# system.prop for surf
#
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
DEVICE_PROVISIONED=1
dalvik.vm.heapsize=96m
ro.sf.lcd_density=240
#DMM
ro.dev.dmm=1
#
# system props for the cne module
#
persist.cne.UseCne=vendor
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
#
# [email protected] TWHuang for DMQG.B-82 begin
lpa.decode=false
# [email protected] TWHuang for DMQG.B-82 en
ro.hdmi.enable=true
#
# system props for the data modules
#
ro.use_data_netmgrd=true
#
# system props for telephony modules
#
#device supports EHRPD
ro.config.ehrpd=true
#Enable dumping QcRil log
persist.radio.adb_log_on=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.setupwizard.mode=DISABLED
ro.opengles.version=131072
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
service.config.gsensor_cal=1
wifi.wapi.supported=true
ro.wifi.wapiQC.supported=true
ro.shutdown.long_anim=1
ro.speedup.anim=1
ro.telephony.gsm.sms.auto-reg=true
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.product.model.num=7001
I hope it can help you
P.S: By the way, I have noticed that the WIFI module makes my phone very hot and my girlfriend's one too. The worst thing is that when I active the wifi the battery only lasts 6-8 hours and that's not normal. Maybe some issue with drivers? I have seen the module is WCN1314 but the drivers are WCN1312 I have seen somewhere, is that normal?
Hey! good news.
I found a site which seems huge about phone official and custom ROMS from china (http://www.shendu.com/), but Changhong Z-Me isn't listed. I think it's a matter of time it will appear in there I think. I just have tested the phone with antutu test 2.9.4 (gave me 3010) and there are more Changhong's Z-Me, but some have ICS 4.0.3!.
I hope we can get ICS or Jelly Bean for this nice phone, ar at least some custom Gingerbread roms ^^
EDIT1: I have also found a person explaining how to recover the mobile or something like that (it is translated with google sorry). Check this out, and let's hope it can solve the problem:
http://bbs.ahong.com/viewthread.jsp?tid=686&extra=page203D1
Yes hopefully we do!!! The thing is MSM 7227A gets ICS and the MSM 8255 doesnt eventhough its better?! Hopefully i can recover my phone! I think the recovery is in beta mode as somethings don't work.
I would say just the CPU isn't enough because if so we would be able to put even Jelly Bean, because MSM8255 CPU is so spreadly used. I wish I could be an Android programmer >_<.
nobitakun said:
I would say just the CPU isn't enough because if so we would be able to put even Jelly Bean, because MSM8255 CPU is so spreadly used. I wish I could be an Android programmer >_<.
Click to expand...
Click to collapse
same!!
Hey, I've got a new problem about the phone. It isn't that important, but it gives on my nerves: the phone deletes any contact I edit. After pressing "done" button it deletes the contact and a pup up message tells me that "the contact does not exist".
I don't want to install another phone book because I like this one, simple and fast, and it does not eat much RAM, aspect which I consider very important.
A thing would be to replace this phone and address book with the Gingerbread stock ones, but I've been reading that it could make a crash loop in the phone.
Have you repaired yours already?
Let's keep in touch!
nobitakun said:
Hey, I've got a new problem about the phone. It isn't that important, but it gives on my nerves: the phone deletes any contact I edit. After pressing "done" button it deletes the contact and a pup up message tells me that "the contact does not exist".
I don't want to install another phone book because I like this one, simple and fast, and it does not eat much RAM, aspect which I consider very important.
A thing would be to replace this phone and address book with the Gingerbread stock ones, but I've been reading that it could make a crash loop in the phone.
Have you repaired yours already?
Let's keep in touch!
Click to expand...
Click to collapse
Maybe I'll look in to this problem! No i haven't repaired my phone yet as I'm busy with my studies so hopefully I will be able to get it up and running again soon! Hopefully someone will be able to get CWM/TWRP recovery up and running on this device!!
------------------------------------------------------------------------------------------------
If I've helped you plz hit the Thanks button and show some appreciation!!
It's someway nice, I managed to repair the problem I was having with the missing edited contacts. Now the phone edits and saves them with no problems ^^. In case you have this problem in the future, I explain what I did:
1 - Backup all contacts to your Gmail, vcard or csv file.
2 - Turn sync contacts off (all accounts) and delete all contacts in your phone.
3 - Go to all applications and look for one called "Contacts Storage".
4 - Do a "Clear Data" and turn on Sync Contacts again, or whether you prefer import them all from the vcard file.
*If you use SIM contacts I don't know whether the program would delete them as it does with the ones stored in the phone, I didn't tested it.
Greetings.
My phone is alive
my phone is alive!!! But before it was 2.3.7 with the wo 3g logo on boot now it is official changhong z-me 2.3.7. But as long as i got it working doesn't matter!!
------------------------------------------------------------------------------------------------
If I've helped you plz hit the Thanks button and show some appreciation!!
CDMA
~\DELETED/~
------------------------------------------------------------------------------------------------
If I've helped you plz hit the Thanks button and show some appreciation!!
Hey!, sorry for the late reply.
I'm really happy you could fix it. I've been out from PC because of studies and family, but now I have some spare days jeje.
I have to say I also updated my changhong with the original firmware and the logo is as you say, and it swept out almost every annoying chinese app LOL.
I installed again the google fix and everything is working flawlessly.
P.S: btw, the google fix you uploaded lacks Google Calendar. IT does not matter, because I just installed Calendar and it works fine, no problems so far. Thanks again.
P.S 2: I noticed you added a link for the recovery file. I found another recovery file which seems to be different to the one you found (different size). I found in the official changhong forum (here's the link: http://bbs.ahong.com/viewthread.jsp?tid=1933&extra=page=2 ). Should it be other CWM version?, I still didn't try it, that why I ask, maybe you did .
i have a pc on stix brand sold by geeks.com website it is based on telechips 8920 and i have jailbroken it easily ,now i want to know if anyone be able to have recovery and custom rom made for this one? id prefer the custom rom with support for usb webcams such as logitech quickcam 4000 or any uvc compliant webcam
More info
I think you'll need to provide more info on your system. cpu, gpu, ram, speed, what its identified as, cpu speed, manufacturer, firmware, model, kernel, picture, wifi module? I don't think you can provide too much information. Also ask Geeks to get you more information.
ok here the info as from the website is
Android Powered HDMI TV Stik Adapter
General Features:
White color
Converts your TV/Monitor into a Smart TV
HDMI 1.4 interface
Runs on Android 4.0 OS (Ice Cream Sandwich)
Built-in Atheros AR6103 IEEE 802.11b/g/n WiFi
TCC8925 ARM Cortex A5 1.0 GHz processor
512 MB DDR3 memory
4 GB internal NAND Flash memory
Micro USB OTG (On-The-Go) port (cable included)
USB Type A host port for connecting a USB mouse/keyboard
Device also supports 2.4 GHz wireless mouse or keyboard
DLNA (Digital Living Network Alliance) and WPS support
Fn key
Other Specifications:
HD video decoder (1080p @ 60 fps)
HD video encoder (1080p @ 30 fps)
Five Layers for Display and Graphic Process Unit
PMU (Power Manage Unit)
3D GPU inside (mail 400)
Power Consumption: ≤ 700mA @ 5V
Unit Dimensions:
0.54 x 1.04 x 3.22-inches (H x W x D, approximate)
Weight: 30 g / 0.06 lbs / 1.06 oz
Will post the build.prop later
here is the build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=CX1-V1.0-v12.06_r1-4096-8189-en
ro.build.display.id=CX1-V1.0-v12.06_r1-4096-8189-en -20121127.162506 test-keys
ro.build.version.incremental=-20121127.162506
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=2012�11�27�星期�16:26:37 CST
ro.build.date.utc=1354004797
ro.build.type=userdebug
ro.build.user=root
ro.build.host=robin
ro.build.tags=test-keys
ro.product.model=TV Dongle
ro.product.brand=Android
ro.product.name=full_tcc8920st_evm_4096_en
ro.product.device=tcc8920st
ro.product.board=tcc8920st_evm
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=telechips
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tcc892x
# ro.build.product is obsolete; use ro.product.device
ro.build.product=tcc8920st
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=CX1-V1.0-v12.06_r1-4096-8189-en -20121127.162506 test-keys
ro.build.fingerprint=Android/full_tcc8920st_evm_4096_en/tcc8920st:4.0.4/CX1-V1.0-v12.06_r1-4096-8189-en/-20121127.162506:userdebug/test-keys
ro.build.characteristics=tablet,sdcard
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.system.hdmi_max_resolution=fullhd
ro.system.hdmi_active=true
persist.sys.hdmi_resolution=125
persist.sys.hdmi_resize_x=5
persist.sys.hdmi_resize_y=5
tcc.hdmi.uisize=1280x720
persist.sys.renderer_onthefly=true
ro.system.composite_active=true
persist.sys.composite_mode=0
persist.sys.composite_resize_x=3
persist.sys.composite_resize_y=3
ro.system.component_active=true
persist.sys.component_mode=1
persist.sys.component_resize_x=3
persist.sys.component_resoze_y=3
persist.sys.auto_resolution=0
ro.system.hdmi_portable=false
ro.system.osd_active=true
ro.system.audio_active=true
tcc.solution.mbox=1
tcc.solution.video=1
tcc.solution.preview=0
tcc.solution.mbox.sleep=1
tcc.statusbar_hide.support=1
tcc.solution.deskclock=0
tcc.solution.nothumb=1
tcc.solution.previewduration=0
tcc.internal.subtitle=1
tcc.video.vsync.support=1
tcc.video.vsync.threshold=0
tcc.video.surface.support=1
tcc.video.deinterlace.support=0
tcc.solution.onlyimage=1
tcc.exclusive.ui.enable=0
persist.sys.auto_detection=0
tcc.display.output.stb=1
tcc.component.chip=ths8200
tcc.shutdown.active=0
persist.sys.app_rotation=2
tcc.wifi_blue.stb=1
ro.system.cec_active=true
persist.sys.hdmi_cec=1
tcc.default.timezone=Asia/Shanghai
tcc.wifi.forced.enable=1
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
ro.sf.lcd_density=160
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=368m
tcc.all.hdmi.720p.fixed=0
tcc.all.video.call.enable=0
tcc.all.camera.no.display=0
tcc.video.lplayback.mode=0
tcc.all.web.full.video=0
tcc.show.video.fps=0
tcc.hwc.disable=0
tcc.all.output.support.camera=0
tcc.media.rtsp.cusset=1
tcc.media.rtsp.starttime=10
tcc.media.rtsp.autimeout=10
tcc.media.rtsp.eos=1
tcc.media.rtsp.seekend=3
tcc.http.conn.timeout.sec=500
tcc.http.recv.timeout.sec=600
tcc.http.reconn.trial.num=999999
tcc.http.disconn.at.full=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
hope this tells u about this pc on stik
new info on that is stock rom doest support usb bluetooth dongle either so....
has anyone be able to make headway creating custom rom for this? im not much of a programer only i know how to flash the rom
vwbug2007 said:
new info on that is stock rom doest support usb bluetooth dongle either so....
Click to expand...
Click to collapse
i found out it is really based on similar cx-01 tv dongle and found the source code for it hmmm...
cesar33 said:
I think you'll need to provide more info on your system. cpu, gpu, ram, speed, what its identified as, cpu speed, manufacturer, firmware, model, kernel, picture, wifi module? I don't think you can provide too much information. Also ask Geeks to get you more information.
Click to expand...
Click to collapse
Is it support webcam now?
Could you share it?
i have tried logitech quickcam4000,lifecam and even uvc supported logitech c270 no work and according to usbview app it can see it but skype,ntouch ,p3 ,z5 and camera app wont see it either , samething it wont reonize bluetooth dongle
soosheen said:
Is it support webcam now?
Could you share it?
Click to expand...
Click to collapse
i was able to compile kernel modules from telechips tcc892x and pushed new modules called btusb.ko and pwc.ko( logitech webcam) but when i tried adb shell insmod /system/lib/modules/btusb.ko it will say operation not permitted i even changed the permissions to match other original modules hmmm....
vwbug2007 said:
i have tried logitech quickcam4000,lifecam and even uvc supported logitech c270 no work and according to usbview app it can see it but skype,ntouch ,p3 ,z5 and camera app wont see it either , samething it wont reonize bluetooth dongle
Click to expand...
Click to collapse
good news! i was able to get modules working in pc on stik fine it was recompiling the modules with version ifo as 3.0.8-tcc instead of 3.0.8+ and adb shell su doesnt work so i had to su in the terminal emulator on the stick and insmod yep wireless mouse/keyboard(hid-sunplus.ko) and logitech quickcam pro 4000(pwc.ko) does works! but the webcam isnt seen by any videophone app or camera app! grrr another brickwall although the wireless keyboard/mouse does works i tried the bluetooth usb no luck using btusb.ko hmmmm we didnt have to make a custom rom ,it just adding the missing modules to /system/lib/modules yay!
vwbug2007 said:
i was able to compile kernel modules from telechips tcc892x and pushed new modules called btusb.ko and pwc.ko( logitech webcam) but when i tried adb shell insmod /system/lib/modules/btusb.ko it will say operation not permitted i even changed the permissions to match other original modules hmmm....
Click to expand...
Click to collapse
im working on compiling android jellybean with added tcc8920st source code from cxsoftware site but ran into a road block i have posted on this forum under android development forum the reason is 4.0.4 have buggy bluetooth stck and usb webcam since the pc on stick didnt have the bluetooth menu enabled to use usb bluetooth dongle pairing with mouse and keyboard
vwbug2007 said:
i was able to compile kernel modules from telechips tcc892x and pushed new modules called btusb.ko and pwc.ko( logitech webcam) but when i tried adb shell insmod /system/lib/modules/btusb.ko it will say operation not permitted i even changed the permissions to match other original modules hmmm....
Click to expand...
Click to collapse
argh! i was doing ./build/envsetup.sh then do lunch it keep not finding the ./lunchrc? it had worked fine just one hour before that hmmm.... im on ubuntu 12.04
vwbug2007 said:
i was able to compile kernel modules from telechips tcc892x and pushed new modules called btusb.ko and pwc.ko( logitech webcam) but when i tried adb shell insmod /system/lib/modules/btusb.ko it will say operation not permitted i even changed the permissions to match other original modules hmmm....
Click to expand...
Click to collapse
aha! found the problem is i was thinking of bash comand that doesnt need to type source build/envsetup.sh now i have to use the word source and lunch now finds the .lunchrc hmmmm bad tutorial on their part smile
vwbug2007 said:
i was able to compile kernel modules from telechips tcc892x and pushed new modules called btusb.ko and pwc.ko( logitech webcam) but when i tried adb shell insmod /system/lib/modules/btusb.ko it will say operation not permitted i even changed the permissions to match other original modules hmmm....
Click to expand...
Click to collapse
can you make a dump of your system and kernel/boot images?
i found a working cwm recovery for my 4G cx01 some time ago and it might work for you.
let me know if you want it.
btw, tcc has released new kernel+platform sources https://www.telechips.com/technical_support/kor/opensource/opensource_list.asp
really? a working cwm? as for the custom rom ive given up trying to compile it it always comes up error 2 i could not find any problem in jellybean file directories i even added the tcc specific files such as drivers ,etc and it still complain not finding that tcc files so ill leave that up to someone as im very busy, ill be glad to get that cwm for 4 gb cx01 how did you install that cwm on the cx01? there are different methods
jakiej said:
can you make a dump of your system and kernel/boot images?
i found a working cwm recovery for my 4G cx01 some time ago and it might work for you.
let me know if you want it.
btw, tcc has released new kernel+platform sources https://www.telechips.com/technical_support/kor/opensource/opensource_list.asp
Click to expand...
Click to collapse
https://www.dropbox.com/s/6j9e80v3ezjhxo0/recovery_4k.img
personally I prefer fastboot flash.
there u go. please make and share an nandroid backup for you stock system and boot. yours is the latest that i could find on the web.
thanks much!
vwbug2007 said:
really? a working cwm? as for the custom rom ive given up trying to compile it it always comes up error 2 i could not find any problem in jellybean file directories i even added the tcc specific files such as drivers ,etc and it still complain not finding that tcc files so ill leave that up to someone as im very busy, ill be glad to get that cwm for 4 gb cx01 how did you install that cwm on the cx01? there are different methods
Click to expand...
Click to collapse
thanks a qadzillions!i already had nandroid app back it up unforunately my pc stick is in the storage bin i moved to my mom's 40 miles away as im moving out next week breaking up with my gf so ill be a while i get back to copying that to dropbox later
jakiej said:
https://www.dropbox.com/s/6j9e80v3ezjhxo0/recovery_4k.img
personally I prefer fastboot flash.
there u go. please make and share an nandroid backup for you stock system and boot. yours is the latest that i could find on the web.
thanks much!
Click to expand...
Click to collapse
take your time and hope everything all right for you
vwbug2007 said:
thanks a qadzillions!i already had nandroid app back it up unforunately my pc stick is in the storage bin i moved to my mom's 40 miles away as im moving out next week breaking up with my gf so ill be a while i get back to copying that to dropbox later
Click to expand...
Click to collapse
be forewarned about adding it to dropbox i lost the private 2 gb diretory because of that so i click download instead
vwbug2007 said:
thanks a qadzillions!i already had nandroid app back it up unforunately my pc stick is in the storage bin i moved to my mom's 40 miles away as im moving out next week breaking up with my gf so ill be a while i get back to copying that to dropbox later
Click to expand...
Click to collapse
Surely many of you will want to know how to disable Data Connection at the first boot for your ROM
You need to put ro.com.android.mobiledata=false in # RIL, telephony before ro.com.android.dataroaming=false
Here's a piece of my FutureNext build.prop:
Code:
# RIL, telephony
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/smd0
ro.telephony.default_network=0
[COLOR=GREEN]ro.com.android.mobiledata=false[/COLOR]
ro.com.android.dataroaming=false
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.telephony.ril_class=SamsungMSMRIL
mobiledata.interfaces=pdp0,gprs,ppp0
ro.ril.disable.power.collapse=0
DEVICE_PROVISIONED=1
Thanks to mnemonyc
Can this guide be pinned? Thanks!
I just want to say that this method is used also in my FutureNext!
Thanks bro! Can you make also a guide to disable gps at first boot?
Sure
http://forum.xda-developers.com/showthread.php?p=44659810#post44659810
Does anyone have any idea whether this is gonna work in Nougat/Marshmallow ROMs?
Adithya R said:
Does anyone have any idea whether this is gonna work in Nougat/Marshmallow ROMs?
Click to expand...
Click to collapse
Exactly same domands........... i'm very interesting because at today every time i need to do a clean flash the very first boot of rom i cost to my about 4€ in my simcard. I have tryed everythings like remove sim and make clean flash whitout simcard inserted but when i reput them..... baaam bye bye 4€ from my credit.
Hi all. I'm looking for some understanding of the Samsung s8/s8+ build.prop values. I know how to change the values based off other peoples tweaks, just don't know what the values mean.
Example:
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=7.0_r8
ro.build.selinux=0
Are there a list of tweaks with information of what the tweak actually are for each tweak. If there are a list of build.prop definitions of values I could study than please list the link.
harveyr4 said:
Hi all. I'm looking for some understanding of the Samsung s8/s8+ build.prop values. I know how to change the values based off other peoples tweaks, just don't know what the values mean.
Example:
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=7.0_r8
ro.build.selinux=0
Are there a list of tweaks with information of what the tweak actually are for each tweak. If there are a list of build.prop definitions of values I could study than please list the link.
Click to expand...
Click to collapse
Setupwizard is what you go through after freshly replacing your system image, first get your phone, etc. The build.prop setting of SELinux doesn't override other kernel-related settings in my case; I have a value of 1 in build.prop for that setting (i.e., should be enforcing), but my SE for Android status is permissive (i.e., ENG boot image from SamPWN firmware; I think just BL is multicarrier). I think the gmsversion setting is your version of Google play services.
jhofseth said:
Setupwizard is what you go through after freshly replacing your system image, first get your phone, etc. The build.prop setting of SELinux doesn't override other kernel-related settings in my case; I have a value of 1 in build.prop for that setting (i.e., should be enforcing), but my SE for Android status is permissive (i.e., multicarrier boot image from SamPWN firmware). I think the gmsversion setting is your version of Google play services.
Click to expand...
Click to collapse
Thanks.
Those was just examples. I will post a few changes/tweaks That I have seen if you can explain them to me.
ro.config.dmverity=true
ro.config.kap_default_on=true
ro.config.kap=true
ro.build.selinux=1
ro.config.knox=v30
ro.config.tima=1
ro.kernel.qemu=0
What does these values mean?
harveyr4 said:
Thanks.
Those was just examples. I will post a few changes/tweaks That I have seen if you can explain them to me.
ro.config.dmverity=true
ro.config.kap_default_on=true
ro.config.kap=true
ro.build.selinux=1
ro.config.knox=v30
ro.config.tima=1
ro.kernel.qemu=0
What does these values mean?
Click to expand...
Click to collapse
(I think only the BL of SamPWN was multicarrier due to keys, but boot was ENG like ENG system)
I think you can change dmverity to false, knox to zero, tima to zero, selinux to zero and here is what the OP author of S8+ SamPWN, @elliwigy, posted:
elliwigy said:
these are some of the build prop settings i added or changed in build.prop:
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.dmverity=false
ro.config.kap_default_on=false
ro.config.kap=false
ro.knox.enhance.zygote.aslr=0
ro.tether.denied=false
ro.securestorage.support=true
security.mdpp.mass=skmm
security.mdpp=None
ro.security.mdpp.ver=3.0
ro.security.mdpp.release=1
ro.security.wlan.ver=1.0
ro.security.wlan.release=1
security.mdpp.result=None
ro.hardware.keystore=mdfpp
ro.hardware.gatekeeper=mdfpp
ro.security.vpnpp.ver=1.4
ro.security.vpnpp.release=8.1
ro.security.mdpp.ux=Enabled
sys.config.amp_perf_enable=false
ro.build.selinux=0
ro.config.knox=0
ro.config.tima=0
ro.config.timaversion=3.0
ro.config.iccc_version=1.0
ro.kernel.qemu=1
ro.boot.flash.locked=0
ro.boot.other.locked=0
persist.security.ams.enforcing=0
vzw.os.rooted=false
ro.boot.veritymode=eio
boot.fps=36
shutdown.fps=26
ro.secure=0
ro.adb.secure=0
Click to expand...
Click to collapse
@jhofseth
Yes. The real problem I'm trying to figure out is when I make those tweaks in build.prop, it kills my bluetooth and samsung connect FC . Bluetooth is grayed out in settings. Not sure which of the tweaks is doing this. I'm using the compare in notepad++ and changing the values that are different only. I don't believe any of the tweaks are Bluetooth, not sure what the problem is.
harveyr4 said:
@jhofseth
Yes. The real problem I'm trying to figure out is when I make those tweaks in build.prop, it kills my bluetooth and samsung connect FC . Bluetooth is grayed out in settings. Not sure which of the tweaks is doing this. I'm using the compare in notepad++ and changing the values that are different only. I don't believe any of the tweaks are Bluetooth, not sure what the problem is.
Click to expand...
Click to collapse
Yeah, I'm very cautious with build.prop compared to many. The only setting I've changed so far is adding:
wlan.wfd.hdcp=disable
But, I only added that to get Miracast working again, and wouldn't have added unless I needed it; it was the solution.
@jhofseth
I found the problem with bluetooth not working.
ro.kernel.qemu=1
If I change this value to 0 bluetooth and samsung connect will not work.
Not sure if related to build.prop or something else, but over on the T-Mobile s8 forum, we have one single rom. It was made for the T-Mobile S8. A couple of us have gotten it booted on the s8+ by swapping out the boot.img on the rom with the one found in the AP firmware file for the single+, but the rotation orientation is reversed. Standing straight up, it thinks it's sideways and vice versa. Not a HUGE problem, considering I normally turn off autorotation, BUT it is a hassle when it comes to the camera and gallery apps. They disregard autorotation settings and rotate opposite anyways.
Is this a thing with the international/other carrier variants of the s8 vs the s8+ and has anyone come up with a solution?
Man I really couldn't tell you. A user jrkruse is someone that could help you.