German users hands up - G1 Android Development

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

Related

Possible backdoor loader?

Using Anycut, select Activity, and in there choose "Device info". This tells you all the build related info, and on the bottom there is a way to check for new builds depending on your "build type". Maybe if using the wifi IP settings forced it through a proxy, where we would sniff the request. Possibly see if there are builds (beta?) we could load, or redirect it to a custom build?
worldestroyer said:
Using Anycut, select Activity, and in there choose "Device info". This tells you all the build related info, and on the bottom there is a way to check for new builds depending on your "build type". Maybe if using the wifi IP settings forced it through a proxy, where we would sniff the request. Possibly see if there are builds (beta?) we could load, or redirect it to a custom build?
Click to expand...
Click to collapse
Great find
We should start a list... I will even keep all the data in a spread sheet if everyone can give me all the info
Build Description
Build ID
Build Date
Build Type
Build User
Build Host
Linux Kernal version
Baseband Version
RIL Impl version
Android ID
G1 back door updater
I have a G1 without the update... I also have adb shell access to it and succesfully ran bash and busybox on it. I know where all the partitions are in the filesystem (mtdblock1-5) and where the kernel resides (boot is mtdblock2).
When the upgrade comes out, I will sniff the packets and let you guys know (and possibly even put the upgrade file up for download somewhere).
Build Description
kila-user 1.0 TC4-RC19 109652
ota-rel-keys, release-keys
Build ID
TC4-RC19
Build Date
Sat Sep 13 00:11:34 PDT 2008
Build Type
user
Build User
android-build
Linux Kernel version
2.6.25-01828-g18ac882
[email protected] #1
Thu Sep 11 23:18:27 PDT 2008
Baseband Version
62.33.20.08H_1.22.12.28
RIL Impl version
HTC-RIL 1.0 (Aug 19 2008, 21"32:33)
damien667 said:
I have a G1 without the update... I also have adb shell access to it and succesfully ran bash and busybox on it. I know where all the partitions are in the filesystem (mtdblock1-5) and where the kernel resides (boot is mtdblock2).
When the upgrade comes out, I will sniff the packets and let you guys know (and possibly even put the upgrade file up for download somewhere).
Build Description
kila-user 1.0 TC4-RC19 109652
ota-rel-keys, release-keys
Build ID
TC4-RC19
Build Date
Sat Sep 13 00:11:34 PDT 2008
Build Type
user
Build User
android-build
Linux Kernel version
2.6.25-01828-g18ac882
[email protected] #1
Thu Sep 11 23:18:27 PDT 2008
Baseband Version
62.33.20.08H_1.22.12.28
RIL Impl version
HTC-RIL 1.0 (Aug 19 2008, 21"32:33)
Click to expand...
Click to collapse
The upgrade will download at various times... it will ask you to update after it has downloaded.
BTW I added two fields I forgot. Build Host (I am wondering if this is different for some and that is how they get updates) and Android ID (also wondering if this has to do with updates.)
Here is my info
Build Description
kila-user 1.0 TC4-RC19 109652
ota-rel-keys, release-keys
Build ID
TC4-RC19
Build Date
Sat Sep 13 00:11:34 PDT 2008
Build Type
user
Build User
android-build
Build Host
undroid13.corp.google.com
Linux Kernel version
2.6.25-01828-g18ac882
[email protected] #1
Thu Sep 11 23:18:27 PDT 2008
Baseband Version
62.33.20.08H_1.22.12.28
RIL Impl version
HTC-RIL 1.0 (Aug 19 2008, 21"32:33)
Android ID
200145da5528c72d
Important information vs useless information
What is useless information is the serial numbers or which machine built your ROM image.
What IS NOT useless, and VERY important, is the ip address and/or domain name where the update file is downloaded from as well as the location of said file on said server, as well as the file name itself.
With that information, we could technically cook our own updates to the firmware if we figure out how to build one, simulate the updating server on a local network, and spoof the phone into thinking it's receiving a legit update when it's actually putting a cooked update onto itself... no need for root access to update the phone!
I read that you will receive a text message with a "download now" button to proceed with the update... if this is true, I can capture the entire traffic sequence of said update and we can emulate it on a local network.
I've tried some preliminary tests using the AnyCut app to open the page to force a "check for updates" and see what server it connects to but could not sniff packets from my wired LAN to my wireless LAN... I will try to sniff the packets straight on my linux router next time and see if I can tell who the phone talks to to check for updates.
If anyone wants to help, that would be excellent.
damien667 said:
What is useless information is the serial numbers or which machine built your ROM image.
What IS NOT useless, and VERY important, is the ip address and/or domain name where the update file is downloaded from as well as the location of said file on said server, as well as the file name itself.
With that information, we could technically cook our own updates to the firmware if we figure out how to build one, simulate the updating server on a local network, and spoof the phone into thinking it's receiving a legit update when it's actually putting a cooked update onto itself... no need for root access to update the phone!
I read that you will receive a text message with a "download now" button to proceed with the update... if this is true, I can capture the entire traffic sequence of said update and we can emulate it on a local network.
I've tried some preliminary tests using the AnyCut app to open the page to force a "check for updates" and see what server it connects to but could not sniff packets from my wired LAN to my wireless LAN... I will try to sniff the packets straight on my linux router next time and see if I can tell who the phone talks to to check for updates.
If anyone wants to help, that would be excellent.
Click to expand...
Click to collapse
HTC is already telling people how to cook your own rom. I want to know how they go about deciding who gets the updates and when... are the build hosts all the same? or do they differ? is our ID sequential? does it mean something? At this point I don't think there is any useless info... we don't know enough about the entire process.
I will see what I can sniff in wireshark but I am not sure. I would really like to get my hands on a prerelease version and find out it's info.
HTC takes the Android SDK with kernel and rootfs, compiles it with the ARM toolchain, adds the proprietary t-mobile stuff, and makes an image to flash onto the phone. All of this information AND sourcecode is available from Google's GIT repository in the android SDK sourcecode. You can find it all here:
http://git.source.android.com/?p=platform/vendor/htc/dream.git;a=tree;h=refs/heads/master;hb=master
Since this phone goes through t-mobile, they are the ones who decide the updating process and order. According to their forums it's random.
http://forums.t-mobile.com/tmbl/board/message?board.id=87&thread.id=8855&view=by_date_ascending&page=1
The point is to get a back door into the root shell account so we can run whatever code we want on the phone as the root user... this will give us the ability to put a home-cooked android compilation on the phone if we so pleased.
Another way to do this is to figure out how the bootloader works on the phone and somehow tell it to boot up from a kernel in the sd card instead of the one in the ROM.
... I read that google was responsible for deploying the updates and that is why it is random. I think it is because they use your android ID not your IMEI or any other number. And I bet all our android ID's have similarities.
BTW... I ran the debug client and the FOTA is cancelled by the server. It then crashes. So I am guessing what we are doing isn't working. There must be something else.
I have my G1 connected over wifi to my network. Using Cain to arp poison and wireshark to sniff.
Sorry to say, but I saw this one coming...the "call home" is encrypted via TLS/SSL.
Mine was contacting Google at 74.125.19.102. I captured the ssl cert. You can get a copy of it here: http://rapidshare.com/files/158237323/74.125.19.102.crt.html
More info to come
I figured it would call google.... but google sends an abort to my device. I know what classes it uses to call home... maybe we can figure it out in there.
Caught something interesting. Apparently when it calls home, its gives google quite a bit of information. I have censored some of it, such as IMEI, serial number, etc
Code:
POST /checkin HTTP/1.1
Content-type: org/x-json
Content-Length: 271
Host: android.clients.google.com
Connection: Keep-Alive
User-Agent: Android-Checkin/1.0
{"imei":"***************","checkin":{"build":{"bootloader":"0.95.0000","serialno":"************","carrier":"tmobile","radio":"62.33.20.08H_1.22.12.28","revision":"128","id":"tmobile/kila/dream/trout:1.0/TC4-RC19/109652:user/ota-rel-keys,release-keys","product":"trout"}}}HTTP/1.1 200 OK
Date: Tue, 28 Oct 2008 05:01:58 GMT
X-Content-Type-Options: nosniff
Expires: Tue, 28 Oct 2008 05:01:58 GMT
Cache-Control: private, max-age=0
Content-Length: 102
Content-Type: text/html
Server: GFE/1.3
{"stats_ok":true,"time_msec":1225170118172,"intent":[{"action":"android.server.checkin.FOTA_CANCEL"}]}
I dont think this feature is going to help us. It just looks like a way for the phone to call home. Now if somebody can get a full capture of the update when its transferred, then we might have something useable.
I don't think we even need to sniff it... I just think we need to dump it from the device. My device has a file in its firmware folder... hmmm
neoobs said:
I don't think we even need to sniff it... I just think we need to dump it from the device. My device has a file in its firmware folder... hmmm
Click to expand...
Click to collapse
How did you find that out?
used ADB to browse my files
The checkin mentions keepalive, might this just be a keepalive for push services?
I don't like how it's sending all of the phone's info w/ just ssl. You could conceivably swipe someones IMEI and serial no. and send a keepalive, I wonder what you would start getting if you did that...
I would prefer a session key hashed w/ time w/ a public key from Google. That would do, right?
Whatever... This kind of bothers me.
I have the certs from my phone that I pulled. Wonder if that will help.
The data I got was not encrypted! There was some other information that was encrypted that I havent tried to crack.
Unless wireshark decrypted the data on the fly (which I dont think it did), the data I retrieved was NOT encrypted.
damien667 said:
HTC takes the Android SDK with kernel and rootfs, compiles it with the ARM toolchain, adds the proprietary t-mobile stuff, and makes an image to flash onto the phone. All of this information AND sourcecode is available from Google's GIT repository in the android SDK sourcecode. You can find it all here:
http://git.source.android.com/?p=platform/vendor/htc/dream.git;a=tree;h=refs/heads/master;hb=master
Since this phone goes through t-mobile, they are the ones who decide the updating process and order. According to their forums it's random.
http://forums.t-mobile.com/tmbl/board/message?board.id=87&thread.id=8855&view=by_date_ascending&page=1
The point is to get a back door into the root shell account so we can run whatever code we want on the phone as the root user... this will give us the ability to put a home-cooked android compilation on the phone if we so pleased.
Another way to do this is to figure out how the bootloader works on the phone and somehow tell it to boot up from a kernel in the sd card instead of the one in the ROM.
Click to expand...
Click to collapse
I am no linux guru......but why not write a backdoor into the kernel if we have the source?? I dont think i know C , nor linux system programing enough to do this...but it seems relatively easy.
or we could always wait for an exploit for the 2.6.25 kernel and then compile it for the android.
I would personally love to be able to use the nice andriod ui, but have the ability to pop a root shell and run all of the linux code i have come to love.

i have a white g1 with rc23????

yes its truwe i have a white g1 with kila-userdebug 1.0 TC3-RC23 99582 test-keys
and im having trouble usin terminal emulator after getting root
i keep following the steps n when i get into terminal emulator n type in "su"
i dont get the pound symbol
kila-userdebug 1.0 TC3-RC23 99582 test-keys
That's probably why. TC4 is the U.S. and TC5 is the UK, where are you from?
I have a G1 with RC23
Hi everybody,
I have a G1 with kile-userdebig RC23, and I lost access to the sdcard. it wont mount or even see the sdcard. Because of this sdcard problem I couldn't update it to the next RC versions...
HELP!!!
Thanks a million...
Did you try a different Sdcard?
Is the sdcaard recognized in recovery or bootloader mode? What bootloader do you have? Dev or hardspl or g1original?
Us g1 or uk/europe ?
Is it branded T-Mobile? If not, this is probably a pre-G1 test device. HTC and Google used these to develop the platform before the launch of G1. You can update it if you like to a more recent build, as it uses the test keys. However you will have to turn off the assertions in the update-script. I described this process for other test device owners in the past. DREAIMG should work too.

Decompiling/hacking the VF HTC Magic

Hello all,
I'm currently sat with my VF-UK HTC Magic and want to start pulling this thing apart a bit if it'll be of use to the more experienced on here, although I'm not 100% where to start.
Below is a breakdown of where I am at the moment, can people please post with further suggestions and what files/dumps from the device you'd like to see etc.
With adb loaded into root mode: (adb root)
Code:
C:\android-sdk-windows-1.5_r1\tools>adb shell
# ls
ls
sqlite_stmt_journals
cache
sdcard
etc
system
sys
sbin
proc
logo.rle
init.sapphire.rc
init.rc
init.goldfish.rc
init
default.prop
data
root
dev
I am in the process to pulling off these files to package up for others etc. however not having a great deal of experience I'm looking for some pointers as to which bits to pull off and upload?
I'm also in the process to playing with SQLite. Which I've successfully got into but my SQl experience is based on MS SQL so again getting my head around this with a view to locating and extracting the operator setting files etc.
Any tips, requests to try on the device (within reason) etc. please post
Thanks
I'm not sure if the forum rules would allow it, but you would get a million more page views (and therefore help) if you post this at the Dream section instead. The Dream and the Magic/Sapphire is basically the same phone anyways, except for the keyboard (or lack thereof) so I don't see the harm.
Jethro - Should Vodafone staff really be asking questions like this?
Tell'em armholes Jethro.
P.S keep the emails coming, We love you up at 2nd Line
Why not? This is an open source device, only the SIM belongs to VF. As I am not decompiling the SIM or even the radio stack at this point everything I'm accessing is within my rights - at least this is my grasp of the licensing side. The Linux kernel is obviously open source and Android itself is released using the Apache License.
"Like any free-software license, the Apache License allows the user of the software the freedom to use the software for any purpose, to distribute it, to modify it, and to distribute modified versions of the software."
So as far as my understanding goes I'm not contravening any licensing or contract, if anyone can provide evidence otherwise then please post and I’ll stand corrected.
Otherwise I'm cracking on with more adb fun today!
@jbelman
source is free, but not compiled binaries, so you are not allowed to 'hack'.
Can anyone explain exactly why the actual compiled binary licensing model differs from the source code?
thevery said:
@jbelman
source is free, but not compiled binaries, so you are not allowed to 'hack'.
Click to expand...
Click to collapse
And who cares about this? It's my phone, so I can even throw it out of the window, if I want.
@jbelman
How did you get the root rights? If I run adb root, I get an error message, that the adbd daemon cannot run with root rights in production builds.
I did some research with adb shell before.
I haven't found any hole I could use to get root rights. Your shell runs with user and group "shell". All the data on the NAND-Flash (Apps and so on) are saved with the user and group "system" and you are not even allowed to enter this directory with another user.
The SD-Card is mounted nosuid and noexec. So we can't execute a local root exploit or something like this from here.
Breaking out of the Java VM is also not possible, because every Application runs with an own user. What would perhaps be possible is exploiting the VM (if there is a security vulnerability in it) and executing a local root exploit (if there is any available for this kernel) from there.
I'm currently waiting for the first update Vodafone delivers. I will sniff the download source of it and save it on my computer to have a backup if anything goes wrong when I'm playing with other firmware versions. I don't want to brick my phone.
@ Matschkeks1988
Are you using 1.1 or 1.5 SDK? I used 1.5.
I'm also a bit loath to really screw around until I've got a stable replacement image etc. should I brick it. Fingers crossed we can grab using update like you suggest.
By the way if anyone has any issues with adb giving: error: more than one device and emulator (I got this after using pull command). Disconnect your device and run: adb kill-server. This will remove all the devices, plug back in and away you go again.
I appear to have a different version baseband, kernel and build:
Baseband:
62.47S.20.17U_2.22.19.07I
Kernel version:
2.6.27-00342-g1936dcd
Build number:
CRA71C
What's everyone else on?
Version
Baseband version
62.50S.20.17U_2.22.19.261
Kernel version
2.6.27-00392-g8312baf
[email protected]) (gcc version 4.2.1) #72
Build Number
CRB17
Vodafone contract phone
Baseband version
62.50S.20.17U_2.22.19.26I
Kernel version
2.6.27-00392-g8312baf
[email protected] #72
Build number
CRB17
Baseband version
62.50S.20.17U_2.22.19.26I
Kernel version
2.6.27-00392-g8312baf
andr[email protected] #72
Build number
CRB17
uk vodafone contract
Looks like Jethro's device is from a different pot.
Which hardware revision do you have? Do you have search button? Who much onboard storage? All of these things changed through the development process.....
Baseband version
62.50S.20.17U_2.22.19.26I
Kernel version
2.6.27-00392-g8312baf
[email protected] #72
Build number
CRB17
Click to expand...
Click to collapse
Same here. SFR/Vodafone (France) contract. Search HW key variant.
Baseband version
62.50S.20.17U_2.22.19.26I
Kernel version
2.6.27-00392-g8312baf
[email protected] #72
Build number
CRB17
The same for VF Spain.
IseeBrickedPhones said:
Looks like Jethro's device is from a different pot.
Which hardware revision do you have? Do you have search button? Who much onboard storage? All of these things changed through the development process.....
Click to expand...
Click to collapse
The hardware is normal. The difference appears to be software only.
My info:
http://i42.tinypic.com/jf8acw.png
Vodafone Spain
jbelman said:
The hardware is normal. The difference appears to be software only.
Click to expand...
Click to collapse
Does this mean you do not have a retail Magic? Where did you buy it from?
Yes VF Retail.
I have spoken to VF about this today and they are looking into why it was shipped as the build is pre-release, as such I can't perform a wireless update.
VF won't release a update to flash over USB either, something to do with Google.
I'm going to have to get it exchanged. So will continue my research on this earlier build while I have it.

[ROMs] Leaked ZTE Roms

Hello friends.
This is intended to be a thread providing up-to-date versions of ZTE ROMs, mainly for the very unsupported (so far) ZTE V71A and ZTE V11A, but if you have other requests for ZTE roms, please ask and I'll see if I can provide.
--- VDF_IT_V11AV2.0.0B02.zip (466.13 MB) http://www.multiupload.nl/E709JNIJ2H
--- FWUpgrade_Pad_CDMA_V55.zip (215.24 KB) http://www.multiupload.nl/NP6EWS6K3B
--- SPT_AM_V55V1.3.0B09.zip (193.05 MB) http://www.multiupload.nl/YTMKD922CU - NEW v55 ROM
--------------------------------------
The above files are most probably all down, and I can no longer locate new versions for them.
I can, however quote:
dclou said:
Hello All:
The phone company in Taiwan(TWN GSM) has just released the offical 4.0.4 rom zte V71A
(Taiwan mobile mypad p4 is the OEM of ZTE V71A)
http://service.taiwanmobile.com/csonline/cellphone/download.html
Just Connect to the above hyperlink and press "P4 Android 4.04 升級檔 "
Then you can download it and upgrade to 4.0.4.
Please help to update this ROM to the first page of this thread...^^
Click to expand...
Click to collapse
I'm sorry friends. I've lost access to the ZTE servers from where I procured new roms for devices.
Unless I find a different source, I can't provide any updates.
Until further notice this thread may be considered dead.
Thanks man, soo is this older or newer? http://kepfeltoltes.hu/120218/tmp_-2133757290_www.kepfeltoltes.hu_.png
1.2.0B09 released in february 2012 vs 1.0S released in july 2011
Leave me your e-mail adress by pm if you want the file, but be advised that we still don't have a flashing utility to install it with, me and mobilx are still trying to figure out how we can get this software on our devices.
sangemaru said:
1.2.0B09 released in february 2012 vs 1.0S released in july 2011
Leave me your e-mail adress by pm if you want the file, but be advised that we still don't have a flashing utility to install it with, me and mobilx are still trying to figure out how we can get this software on our devices.
Click to expand...
Click to collapse
That would be good. did you get my pm?
Zte score roms?
Sent from my X500 using xda premium
Okay, so here is a pdf for the huaweii media pad 7, of the flashing process and the unlmt.cfg needed is 0byte also , it is supposed to be the same process, dont use the files from here, its not for v71a or v11a!
http://www.huaweidevice.com/tcpsdownload/downLoadCenter?category=&flay=software&downloadID=NDM5NzQ=
brd912, couldn't you have just said X500 in the first place? I'll look, if I find anything I'll let you know.
zsolti, so far I've had no success with using the huawei procedure to flash our tabs, and mobilx hasn't been online today so I haven't got a clue from him about this.
The bad news is, as confirmed earlier by mobilx, the builds are IDENTICAL to what we currently have on our devices. Not encouraging at all (Verified by comparing build.prop). And we don't even know how to flash them yet...
I'm attempting to obtain a carrier unlocked nandroid backup right now, to see if it's locked at a component firmware level or at software level. Maybe we'll see some good news on that front.
Hello there,
This guide in english explains a lot. So this unlmt.cfg file actually serves as a trigger to automatik or manual update.
That means
if it is present update will start on PWR off PWR on
if it is NOT present than you need to go to the FTM mode VOL+ & PWR and update process will start
dload folder must be on ext-sd card.
Again leaked FWs for V11a are the same as ones on our devices
Sangemaru can confirm if his internal FW name on 7 inch matches with the leaked ones.
Go to yours build.prop file and check ro.build.sw_internal_version=VDF_RS_V11AV1.0.0B03 example of mine device
VDF - network - vodafone
RS - country - serbia
V11A - model - 10 inch
V1.0.0 FW version - very first
B03 - localisation ( APNs, keyboards etc) Serbian network APNs and Cyrillic keyboard
Yea, I read it.
At least for my tablet, it didn't apply. Update would not trigger, either on reboot or ftm mode, with neither UPDATA.zip or update.zip names, with the file or not, with fresh sd card format or not, development mode or not, etc.
I'm assuming it worked on your V11A, so somebody should attempt it on their own V71A's if possible. I may have messed something up, or simply have an unsupported sd card.
The one in first post for V71a is :
ro.build.zte_build_number=SmartTab7-MSM8260-V02d-Dec022011-Vodafone-ES
ro.build.software_version=SmartTab7-MSM8260-V02d-Dec022011-Vodafone-ES
ro.build.sw_internal_version=VDF_ES_V71AV1.2.0B09
ro.com.google.clientidbase.ms=android-hms-vf-{country}
ro.com.google.clientidbase.am=android-vf-{country}
ro.build.date=Sat Dec 3 02:09:34 CST 2011
Mine is:
ro.build.zte_build_number=SmartTab7-MSM8260-V02d-Dec022011-Vodafone-HU
ro.build.software_version=SmartTab7-MSM8260-V02d-Dec022011-Vodafone-HU
ro.build.sw_internal_version=VDF_HU_V71AV1.2.0B09
ro.com.google.clientidbase.ms=android-hms-vf-{country}
ro.com.google.clientidbase.am=android-zte
ro.build.date=Sat Dec 3 03:44:43 CST 2011
.
Anyone know what will happen if we flash a firmware from another carrier, like in my case? Because the network id isnt the same for hungary it is 21670, for spain its different...
I'm assuming one thing will happen: nothing.
hei, did any of you has dialer app, it seems vodafone had removed this one
p.s. am on july rom
if there is one can some one post it
tanks
Honeycomb, friend. Honeycomb has telephony support removed. If you want phone service look into a VoIP service.
Hi all !!!!!
I'm Italian .......
My device specs :
M8660A-AABQNLYM-3.1.32T 1 Jul 23 2011 22:00:00
Kernel version :
2.6.35.11-perf.
[email protected]#2
Build Number :
SmartTab10-MSM8260-V02d-Dec022011-Vodafone-IT
huawei media tab
sangemaru said:
Honeycomb, friend. Honeycomb has telephony support removed. If you want phone service look into a VoIP service.
Click to expand...
Click to collapse
did notice that huawei media pad has a dialer app, however did not succed to start it.
I'm saying that in greate proportion the two tablets are just the same.
no luck
zsolti256 said:
The one in first post for V71a is :
ro.build.zte_build_number=SmartTab7-MSM8260-V02d-Dec022011-Vodafone-ES
ro.build.software_version=SmartTab7-MSM8260-V02d-Dec022011-Vodafone-ES
ro.build.sw_internal_version=VDF_ES_V71AV1.2.0B09
ro.com.google.clientidbase.ms=android-hms-vf-{country}
ro.com.google.clientidbase.am=android-vf-{country}
ro.build.date=Sat Dec 3 02:09:34 CST 2011
Mine is:
ro.build.zte_build_number=SmartTab7-MSM8260-V02d-Dec022011-Vodafone-HU
ro.build.software_version=SmartTab7-MSM8260-V02d-Dec022011-Vodafone-HU
ro.build.sw_internal_version=VDF_HU_V71AV1.2.0B09
ro.com.google.clientidbase.ms=android-hms-vf-{country}
ro.com.google.clientidbase.am=android-zte
ro.build.date=Sat Dec 3 03:44:43 CST 2011
.
Anyone know what will happen if we flash a firmware from another carrier, like in my case? Because the network id isnt the same for hungary it is 21670, for spain its different...
Click to expand...
Click to collapse
Hi majaelix,
Tried all proceudres described in this post with no luck updating firmware, I have a Vodafone Spain V71a with 1.0 software version.
Tired to create several folders in sd-ext and puting inside the update.zip and the .cfg file with no success
Tried to sign the zip with Signapk utility but when I try to update it from Recovery, it says: "signature check failed", I think one of the files nneded to sign a zip file is related to the recovery, so I don't know how to generate it.
Also tried to root it with fastboot boot superboot.img but my fastboot can't detect the device form pc, I'vhe checked if drivers are installed in device administration and all seems to be ok.
Did you make any advance on this issue, I'm looking forward.
caveman_78 said:
Hi majaelix,
Tried all proceudres described in this post with no luck updating firmware, I have a Vodafone Spain V71a with 1.0 software version.
Tired to create several folders in sd-ext and puting inside the update.zip and the .cfg file with no success
Tried to sign the zip with Signapk utility but when I try to update it from Recovery, it says: "signature check failed", I think one of the files nneded to sign a zip file is related to the recovery, so I don't know how to generate it.
Also tried to root it with fastboot boot superboot.img but my fastboot can't detect the device form pc, I'vhe checked if drivers are installed in device administration and all seems to be ok.
Did you make any advance on this issue, I'm looking forward.
Click to expand...
Click to collapse
No, but Please standby, a fellow Hungarian 10" user is probably going to make some kind of update we have obtained a build that is even newer, it is the following:
SmartTab7-MSM8260-V03a-Jan182012-Vodafone-HU
good news
zsolti256 said:
No, but Please standby, a fellow Hungarian 10" user is probably going to make some kind of update we have obtained a build that is even newer, it is the following:
SmartTab7-MSM8260-V03a-Jan182012-Vodafone-HU
Click to expand...
Click to collapse
Wow, those are good news. I can't wait for the update. maybe after, we can try to make some weird ICS port.
Please, keep us informed...
Thanks...
i have some problem
hello i have a V71A and i wanna take back the stock rom beacuse i formated system... and a CWM is buggy and usb mass storage is doesn't work and my pc don't see the tablet just CD-rom and not more "adb devices -list of devices atthaced (and nothing)" pls help (sorry for my english)
Uninstall and reinstall usb drivers. Your problem is a driver issue. And how exactly did you format the system?

ChangHong Z-me ROOT / PLAY STORE FIX!!!

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 .

Categories

Resources