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.
Related
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.
Greetings,
I realise this may have been asked a number of times before on this forum (and other forums, for that matter), but my circumstances don't appear to be quite the same as those of the people asking if any of the Google searching I've done is anything to go by (correct me if I'm wrong, once you've read this):
I recently got a Samsung Galaxy S on Vodafone UK (see below for more firmware details) which I have since rooted, and I was hoping get OpenVPN working on it using OpenVPN Installer and OpenVPN Settings from the Android Market. I understand as part of the process that I need a module named tun.ko which ordinarily has to have been compiled specifically for a particular phone, yes? With that in mind I was hoping to be able to use this post from a thread I dug up during a search of this forum in order to help me. So I loaded this onto my phone's internal storage and then inserted the exact path accordingly into OpenVPN Settings, however I get the below error when I try to initiate a new tunnel:
Code:
FATAL: cannot allocate tun/tap dev dynamically
Here are the things I've tried up to now to get this working (in no particular order), which so far haven't worked:
1) Installed BusyBox Installer from the Android Market, in order to install BusyBox (obviously ) which I understand OpenVPN Settings requires to initiate a new tunnel.
- Having done this I have also tried re-installing OpenVPN via OpenVPN Installer, and redefining the path to BusyBox's 'ifconfig' and 'route' processes, which I understand the OpenVPN Settings app uses.
2) Tried switching between 'modprobe' and 'insmod' as the chosen method of calling the tun module prior to tunnel initialisation.
3) Tried moving the tun.ko module I downloaded from the above linked post to different locations, then add the exact path in OpenVPN Settings accordingly.
4) Tried using various differing tun modules downloaded from different webpages, loading each one in turn as above.
5) Tried switching between 3G and Wi-Fi hoping that somehow the behaviour would change (was running out of ideas at this point ).
6) I read somewhere that you can compile your own tun.ko module using the kernel source code that matches your particular firmware version, so I tried visiting the link referenced in the above linked post [http://opensource.samsung.com/] in order to find the source code for my phone. However I can't seem to find my exact firmware listed (see below for my firmware). Incidentally how exactly would you compile your own module from the source code? Does this require the Android SDK, which I have readily available? [EDIT: I've had another look at the list of source code downloads for my phone and I noticed one entitled 'GT-I9000_OpenSource_Froyo_update2.zip' for the so-called 'JPX' version, which appears to be for the European versions of the handset. Do I assume the 'X' here is a wildcard in place of whatever letter or number represents the user's firmware, or does the 'X' represent the actual firmware version itself?]
7) Tried manually editing the .ovpn config file to read 'dev tun' instead of 'dev tap' as it was originally (I can post the full config file if anyone requires it for the troubleshooting process, perhaps there's something here I've missed).
If it helps at all here are the firmware details for my handset (taken from 'About phone' section under 'Settings'):
Code:
Model number: GT-I9000
Firmware version: 2.2
Baseband version: I9000BUJP5
Kernel version: 2.6.32.9
[email protected] #1
Build number: FROYO.BUJP7
N.B. This was pre-loaded onto the phone (probably by Vodafone), I haven't flashed/updated it with anything else.
Any help would be appreciated. Thanks.
Regards,
Jon.
Bump, this forum seems to get a lot of activity!
Bump. Still no help?
Why don't you install a kernel with TUN support? voodoo and hardcore do support it.
I'm using hardcore's and my OpenVPN connection works without any problems. See this post for more inform about the client and server settings:
http://forum.xda-developers.com/showpost.php?p=11299020&postcount=3
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?
** Version 1.1 UPDATED October 2016 **
SUMMARY:
Allows WhatsApp users on Android to extract their backed up WhatsApp data from Google Drive.
UPDATE: This tool was last updated on October 20th 2016.
IMPORTANT: If you wish to extract crypt keys or WhatsApp databases from non-rooted Android devices then you need: WhatsApp Key/DB Extractor instead.
QUESTION:
Why would I even need this?
Us mere mortals have absolutely no access to any application data stored on Google Drive, even though it's our data.
Google said:
What is the Application Data folder?
The 'Application Data folder' is a special folder that is only accessible by your application. Its content is hidden from the user, and from other apps. Despite being hidden from the user, the Application Data folder is stored on the user's Drive and therefore uses the user's Drive storage quota. The Application Data folder can be used to store configuration files, saved games data, or any other types of files that the user should not directly interact with.
Click to expand...
Click to collapse
BRANCH UPDATES:
v1.0 - Initial release.
v1.1 - Added Python 3 support.
PREREQUISITES:
O/S: Windows Vista, Windows 7, Windows 8, Windows 10, Mac OS X or Linux
Python 2.x - If not installed: https://www.python.org/downloads/
Android device with WhatsApp installed and the Google Drive backup feature enabled
Google services device id (if you want to reduce the risk of being logged out of Google)
Search Google Play for "device id" for plenty of apps that can reveal this information
Google account login credentials (username and password)
INSTRUCTIONS:
Extract "WhatsApp-GD-Extractor-master.zip".
Edit the [auth] section in "settings.cfg".
Run python WhatsAppGDExtract.py from your command console.
Read the usage examples that are displayed.
Run any of the examples.
TROUBLESHOOTING:
Check you have the required imports installed (configparser and requests).
I.E.: pip install configparser requests
DOWNLOAD: WhatsApp-GD-Extractor-master.zip
AUTHOR: TripCode
I can list all files from all my backups (I have four backups with ID from 0 to 3) but I can download files from "Backup 0" only.
I debugged the script and when I try to download a file from backupID 3 I obtain a 404 error.
Can you help me? Thanks.
TripCode said:
** Version 1.1 UPDATED October 2016 **
SUMMARY:
Allows WhatsApp users on Android to extract their backed up WhatsApp data from Google Drive.
UPDATE: This tool was last updated on October 20th 2016.
IMPORTANT: If you wish to extract crypt keys or WhatsApp databases from non-rooted Android devices then you need: WhatsApp Key/DB Extractor instead.
QUESTION:
Why would I even need this?
Us mere mortals have absolutely no access to any application data stored on Google Drive, even though it's our data.
BRANCH UPDATES:
v1.0 - Initial release.
v1.1 - Added Python 3 support.
PREREQUISITES:
O/S: Windows Vista, Windows 7, Windows 8, Windows 10, Mac OS X or Linux
Python 2.x - If not installed: https://www.python.org/downloads/
Android device with WhatsApp installed and the Google Drive backup feature enabled
Google services device id (if you want to reduce the risk of being logged out of Google)
Search Google Play for "device id" for plenty of apps that can reveal this information
Google account login credentials (username and password)
INSTRUCTIONS:
Extract "WhatsApp-GD-Extractor-master.zip".
Edit the [auth] section in "settings.cfg".
Run python WhatsAppGDExtract.py from your command console.
Read the usage examples that are displayed.
Run any of the examples.
TROUBLESHOOTING:
Check you have the required imports installed (configparser and requests).
I.E.: pip install configparser requests
DOWNLOAD: WhatsApp-GD-Extractor-master.zip
AUTHOR: TripCode
Click to expand...
Click to collapse
Hello, you could explain how to run the script on windows I have problems with "pip install configparser requests"
..
Good Work but i have a problem!
When i want to execute it says only:
Unable to locate google drive file map for: com.whatsapp
What can i do or what i make wrong?
"Unable to locate google drive file map for: com.whatsapp"
I too am receiving the same error message:
"Unable to locate google drive file map for: com.whatsapp".
Could this be related to a lack of API credentials for traversing the hidden AppData folder structure?
I'm running this via Ubuntu 16.10 x64; Linux desktop 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux and have installed the necessary prerequisite packages as detailed above).
Can someone please assist us (I'm more than happy to provide debugging information etc)?
Kind regards,
John
---------- Post added at 03:41 AM ---------- Previous post was at 03:29 AM ----------
john.morton said:
I too am receiving the same error message:
"Unable to locate google drive file map for: com.whatsapp".
Could this be related to a lack of API credentials for traversing the hidden AppData folder structure?
I'm running this via Ubuntu 16.10 x64; Linux desktop 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux and have installed the necessary prerequisite packages as detailed above).
Can someone please assist us (I'm more than happy to provide debugging information etc)?
Kind regards,
John
Click to expand...
Click to collapse
On further inspection of the Python code and having reviewed drive.google.com it appeared that I hadn't actually run an initial backup and there was no data to present. I believe things are now working correctly (at least in terms of the info and list functions - I'll try the remainder shortly).
What a fantastic script!
john.morton said:
I too am receiving the same error message:
"Unable to locate google drive file map for: com.whatsapp".
Could this be related to a lack of API credentials for traversing the hidden AppData folder structure?
I'm running this via Ubuntu 16.10 x64; Linux desktop 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux and have installed the necessary prerequisite packages as detailed above).
Can someone please assist us (I'm more than happy to provide debugging information etc)?
Kind regards,
John
---------- Post added at 03:41 AM ---------- Previous post was at 03:29 AM ----------
On further inspection of the Python code and having reviewed drive.google.com it appeared that I hadn't actually run an initial backup and there was no data to present. I believe things are now working correctly (at least in terms of the info and list functions - I'll try the remainder shortly).
Click to expand...
Click to collapse
Just a quick note to confirm the script still works and I've successfully downloaded the database and images/photos.
I'd like to acknowledge the hard work of the developer and convey my gratitude.
PS: any chance you can provide a slightly modified version to dump EVERY single hidden file from Google Drive (as I'm trying to discover potential chat and images that may be obfuscated by Google but potentially still present etc)?
john.morton said:
Just a quick note to confirm the script still works and I've successfully downloaded the database and images/photos.
I'd like to acknowledge the hard work of the developer and convey my gratitude.
PS: any chance you can provide a slightly modified version to dump EVERY single hidden file from Google Drive (as I'm trying to discover potential chat and images that may be obfuscated by Google but potentially still present etc)?
Click to expand...
Click to collapse
May I know what to write after pull to get the key file i am only able to get the crypt file
vsur said:
May I know what to write after pull to get the key file i am only able to get the crypt file
Click to expand...
Click to collapse
The keyfile isnt necessary to get all your texts back. simply copy the crypt file in the given folder structure.
as far as i know the keyfile isnt stored online nor offline, online in the data partition or smth like there
XXX\Mi-4c\Internal shared storage\WhatsApp\Databases\msgstore.db.crypt12
Click to expand...
Click to collapse
And install Whatsapp. Then it should find the data by itself and if you are using the same number it should be decrypted correctly.
But if you changed your number i think there is no way to decrypt now
Error= BadAuthentication
I've done everything correctly, but when i try any of the examples it just says "Error= BadAuthentication " even though I am sure of my credentials. please advise.
Thank you sir.
its just saved me,downloaded whatsapp database backup only
Any video tutorial please...I really need it
python-learner said:
I've done everything correctly, but when i try any of the examples it just says "Error= BadAuthentication " even though I am sure of my credentials. please advise.
Click to expand...
Click to collapse
I am having the same issue. Did you get this resolved?
Great work freeing out info, bitta help needed...
I can download all 3 of my backups but I can't find them anywhere locally.
python WhatsAppGDExtract.py -pull "Databases/msgstore.db.crypt12" 1
Downloaded: "WhatsApp/Databases/msgstore.db.crypt12".
Anyone know?
Edit - Got it to work with WhatsAppGDExtract.py -pull "Databases/msgstore.db.crypt12" 0 1 2
Getting the same result again and again "Error= BadAuthentication"
Hi! Thank you for this extractor! For everyone who's getting "Error=BadAuthentication", go to https://security.google.com/settings/security/apppasswords , set up an app password and use that for the settings.cfg file. If the website says that you can't set up app passwords, it means that you don't have 2stepverification enabled for your google account. Search it in your google account settings (it should be under "security" or something... it's in the same place you can edit your password), enable it and then set up the app password. Then, if you want, you can re-disable 2stepverification (and obviously that'll re-disable the possibility to add and use app passwords).
python-learner said:
I've done everything correctly, but when i try any of the examples it just says "Error= BadAuthentication " even though I am sure of my credentials. please advise.
Click to expand...
Click to collapse
Same problem for me. I tried 2 different google accounts with sure passwords
cvanti said:
Same problem for me. I tried 2 different google accounts with sure passwords
Click to expand...
Click to collapse
Open first the folder where the file is at using comand prompt then run the .py file, rather than running it using its full directory. This allows the file with the credentials that you entered to be read, otherwise if you run it directly, your credentials are not considered. Hope this helps as this was what I did wrong
Help, did everything and tried launching from cmd but it just opens and closes in a split second. No error or anything. Same result when I ran it from the folder.
Dear Xda members,
I have an big problem since yesterday (22 july 2017). Accidently I deleted an directory on my gallery with 200 images.
It was a big mistake and I need this images back. Is there any way to recover these deleted images?
I have used a program with the name: diskdigger. But this program let me recover pictures with thumbnail format. I want original format or better quality...
You would help me so much if you can help me with this problem!
Using a Samsung Galaxy s6 Edge
Thanks in advance.
masterugur said:
Dear Xda members,
I have an big problem since yesterday (22 july 2017). Accidently I deleted an directory on my gallery with 200 images.
It was a big mistake and I need this images back. Is there any way to recover these deleted images?
I have used a program with the name: diskdigger. But this program let me recover pictures with thumbnail format. I want original format or better quality...
You would help me so much if you can help me with this problem!
Using a Samsung Galaxy s6 Edge
Thanks in advance.
Click to expand...
Click to collapse
dont do anything else in fear of overwriting the deleted files
download diskdigger from play store and run that its really good at getting deleted photos back
oh snap i didnt finish reading your post sorry thats about the best way i know without paying
but basicly u need to turn off ure phone as data needs to be written to the disk u run more and more chance of bits and bytes being overwriten
u might try the drfone android but i never had any luck with it but was always trying lgs and its more for sammys and iphones.
and please next time post ?s in ?s thread
Same here.
Whole day searching, PhotoRec, DiskDIgger, Rooting, Knox, ROM, UMS ... getting dizzy..
Boils down to: no root no chance.
I have searched and found for my phone a reasonably simple way to "root it", but it says "Beware, this is risky, know everything before proceeding, knox will be tripped and brick could hit you." just before the download button. (here: desktop.firmware.mobi/device:403/firmware:16678/cfar )
And then if I take this risk, I could still see nothing in PhotoRec, as nothing is certain in this realm.
Is there a guide somewhere for this avail?
=------------ required info below:
baseband version
G920FXXU6ERF6
Kernerl version
3.10.61-13830439
[email protected]#1
wed jun 20 16:32:45 KST 2018sm-
Build number
NRD90M G920FXXU6ERF5
SE for Android status
Enforcing
SEPF_SECMOBILE_7_0_0010
Wed jun 20 16:52:25 2018
Knox version
Knox 2.7.1
Standard SDK 5.7.1
Premium SDK 2.7.1
Customization SDK 2.7.1
Container 2.7.1
CEP 2.1.1
Enterprise billing 1.2.0
OTP 2.6.0
SE for Android 2.4.3
SSO 2.5.0
Shared device 2.6.0
TIMA 3.3.015
VPN 2.3.0
Security software version
MDF v3.0 Release 1
WLAN v1.0 Release 1
VPN v1.4 Release 8.1
ASKS v1.4 Release 180122
SMR Jun 2018 Release 1
Android security patch level
June 1, 2018
xt666m said:
Same here.
Whole day searching, PhotoRec, DiskDIgger, Rooting, Knox, ROM, UMS ... getting dizzy..
Boils down to: no root no chance.
I have searched and found for my phone a reasonably simple way to "root it", but it says "Beware, this is risky, know everything before proceeding, knox will be tripped and brick could hit you." just before the download button. (here: desktop.firmware.mobi/device:403/firmware:16678/cfar )
And then if I take this risk, I could still see nothing in PhotoRec, as nothing is certain in this realm.
Is there a guide somewhere for this avail?
Click to expand...
Click to collapse
yes, this does really boil down to "no root = no chance" sadly. The only thing you can do is turn it off like said above to avoid the phone writing 1's and 0's in the spot where the picture data physically resides as the directory manager doesnt know its there anymore since it was "deleted". You have the 920F, so you should be able to root it. Its out of warranty anyways, so IMO, its worth a shot