Related
I have a US T-Mobile G1, but am in Belgium, and we don't have T network here...
is the update coming to the devices, regardless of the network they're registered on, or do I really need to be in the US, on a T-Mobile network, to get the update?
Anyone from Belgium, or somewhere in Europe that has a G1 that is on another network than it was meant for?
Is there (going to be) any means of pulling the update manually, even on another network?
Thanks for sharing the info...
First, is your phone rooted or not?
Second, what firmware/rom are you running?
You do not need to be on T-mobile to get the update. Your phone checks with a server run by google. If there is an update for it it will get sent to your phone. If your phone is rooted it wont update due to running testkeys instead of releasekeys (unless you are running an ADP firmware).
Once the exact location of the file is known you can manually download it and update your phone if you dont want to wait.
Since you say its a US G1 you should be able to get the 1.5 update which should drop sometime between May 11th and the end of the month. Your location may prevent that from happening, however you can just use the zip file that will get posted on this site somewhere if that happens.
First of all, thanks for the quick response.
The phone is not rooted, it's a normal user phone, no hacks, no custom soft...
Current version is 1.1 RC33 126986 with the release keys intact...
I'll wait until the end of the month and see then...
Just need it to get SipDroid running... (www.sipdroid.org) Wanted to make it a 'cordless phone' for my asterisk server running at home...
Thanks for the info and help!
I'll let you know when I get the update.
Just to let you know, I'm currently abroad with my G1 (UK on T-Mobile), with data roaming turned off.
Connected my G1 to the internet over Wifi and the update was detected and downloaded over Wifi. So looks as though it shouldn't matter what you're connected over.
I have mine secondhand and i have no idea if its rooted or not. but i know i don't have any updates yet. btw im in turkey where no t-mobile service is avaliable.
my device's firware is like that, can you tell its rooted or not? I know im a real newbie. If its rooted how can i take it to original state that can pull the original cupcake
Firmware version 1.0
kernel version
2.6.25-01843-gfea26b0
[email protected] 6#
built number
kila-user 1.0 TC4-RC30 116143
ota-relkeys,release keys
saluk said:
I have mine secondhand and i have no idea if its rooted or not. but i know i don't have any updates yet. btw im in turkey where no t-mobile service is avaliable.
my device's firware is like that, can you tell its rooted or not? I know im a real newbie. If its rooted how can i take it to original state that can pull the original cupcake
Firmware version 1.0
kernel version
2.6.25-01843-gfea26b0
[email protected] 6#
built number
kila-user 1.0 TC4-RC30 116143
ota-relkeys,release keys
Click to expand...
Click to collapse
I think (thx to xda-develpers ) mine is not rooted right? Then why didn't I got the cupcake or the previous version which is newer than mine :/
Im just curious if i will receive the update OTA or not. I rooted my phone however it states that it is release keys and not test keys. Below is what the About Phone screen looks like
Firmware Version
1.1
kernel Version
2.6.25-01843-gfea26b0
[email protected] #1
Build Number
kila-user 1.1 PLAT-rc33 126986
ota-rel-keys, release-keys
Thanks for the help
To answer the actual question. Will you get the OTA T-Mobile update? No, you will not. T-Mobile is pushing it to their customers. T-Mobile and Google are not the same company and T-Mobile has no responsibility to update the "device" but rather to update their customers.
The reason the UK guy got the update is because he is in the customer database for T-Mobile UK. So as his phone is part of that network (regardless of roaming/not roaming) it came to him.
However, I am sure there will be some smart G1 user who, when getting the update downloaded OTA, will FIRST copy the update off their phone BEFORE installing it. Then uploading a copy of the update so those who still have not received it can download it and install it manually. (That is a hint to any US T-Mobile person on this forum who gets the update)
You should get the OTA updates. I bought a dev phone in december and in January I got the OTA ADP1.1h update. I'm not on T-Mo at all and never have. I am on AT&T and all was well and I would assume you should be too.
ExploreMN said:
To answer the actual question. Will you get the OTA T-Mobile update? No, you will not. T-Mobile is pushing it to their customers. T-Mobile and Google are not the same company and T-Mobile has no responsibility to update the "device" but rather to update their customers.
The reason the UK guy got the update is because he is in the customer database for T-Mobile UK. So as his phone is part of that network (regardless of roaming/not roaming) it came to him.
However, I am sure there will be some smart G1 user who, when getting the update downloaded OTA, will FIRST copy the update off their phone BEFORE installing it. Then uploading a copy of the update so those who still have not received it can download it and install it manually. (That is a hint to any US T-Mobile person on this forum who gets the update)
Click to expand...
Click to collapse
I beg to differ, I might be wrong but everyone was getting the previous updates because they aren't sent from T-Mobile. They are sent from Google. It is just a T-Mobile build so as long as you have internet it will download the update.
neoobs said:
I beg to differ, I might be wrong but everyone was getting the previous updates because they aren't sent from T-Mobile. They are sent from Google. It is just a T-Mobile build so as long as you have internet it will download the update.
Click to expand...
Click to collapse
I beg to differ your begging to differ! Google, from what I understand, has its own 1.5 cupcake update which is similar to the T-mobile version in just about every respect. However, while searching for cupcake I read an article that noted there were some differences between the two builds. Perhaps Google was responsible for the G1 update to 1.1, but from the sounds of it, that is not the case now.
ExploreMN said:
I beg to differ your begging to differ! Google, from what I understand, has its own 1.5 cupcake update which is similar to the T-mobile version in just about every respect. However, while searching for cupcake I read an article that noted there were some differences between the two builds. Perhaps Google was responsible for the G1 update to 1.1, but from the sounds of it, that is not the case now.
Click to expand...
Click to collapse
I am not saying that Google created it but rather it is hosted on Google Servers, this can't change because the update script pulls the update from Google servers. Maybe in 1.5 it will change but as of 1.1 it still checks Google for the update.
Basically as long as you can reach the google address it all will update.
You will NOT get an OTA.
You only get an OTA IF:
1) You have a G1 and are a tmobile customer. The update may come from google's servers, but the update is controlled by tmobile, and its user database. It is a tmobile phone.
2) You have an ADP, and have already *MANUALLY* updated to 1.1 firmware. Then, you will get the official google (via HTC) ADP 1.5 update. OTA functionality for ADP was only rolled out in the 1.1 firmware.
Other than that, no, you will NOT get the update, and you will need to root the phone and manually update to either the ADP release, one of the t-mobile releases or any of the 'cooked' roms on here.
Also there seems to be some confusion on the ADP vs. G1 versions. Infact, it is the exact same phone, and the *exact* same software, but the tmobile release has the t-mobile logo and all their spam apps (my favs etc). Otherwise, they are the same thing!
Hope this cleared some stuff up.
I bought the phone second hand and use it on orange and i got the update. im not a tmobile user, but the person i bought the phone off was. but have never personally used it on tmobile and received the 1.5 update fine. hope this helps
menov321 said:
I bought the phone second hand and use it on orange and i got the update. im not a tmobile user, but the person i bought the phone off was. but have never personally used it on tmobile and received the 1.5 update fine. hope this helps
Click to expand...
Click to collapse
You probably got the google generic 1.5 update and not the t-mobile specific update.
bakgwailo said:
You will NOT get an OTA.
You only get an OTA IF:
1) You have a G1 and are a tmobile customer. The update may come from google's servers, but the update is controlled by tmobile, and its user database. It is a tmobile phone.
2) You have an ADP, and have already *MANUALLY* updated to 1.1 firmware. Then, you will get the official google (via HTC) ADP 1.5 update. OTA functionality for ADP was only rolled out in the 1.1 firmware.
Other than that, no, you will NOT get the update, and you will need to root the phone and manually update to either the ADP release, one of the t-mobile releases or any of the 'cooked' roms on here.
Also there seems to be some confusion on the ADP vs. G1 versions. Infact, it is the exact same phone, and the *exact* same software, but the tmobile release has the t-mobile logo and all their spam apps (my favs etc). Otherwise, they are the same thing!
Hope this cleared some stuff up.
Click to expand...
Click to collapse
Where did you get your info? We had tons of users getting the update OTA for the 1.1 and even previous 1.0 builds. BTW there are 3 versions of software, 2 by t-mobile, 1 by google. The 2 t-mobile versions are US and UK which have different applications because of the way company each works.
ExploreMN said:
You probably got the google generic 1.5 update and not the t-mobile specific update.
Click to expand...
Click to collapse
Where did you hear there is a generic google version? So far only the ADP 1.5 has been made available to us, and we only know of the ADP and T-Mobile versions.
There is also this one, cupcake for holiday phone europe
http://android.clients.google.com/updates/signed-dream_gfh_eu-ota-147201.ea8cd686.zip
posted here
http://phandroid.com/2009/05/05/official-german-cupcake-url-leaks-for-developers/
I have a T-mobile G1 on Rogers in canada with a data plan,
YES, YOU WILL EVENTUALLY GET THE UPDATE.
Originally i believed that i do not get updates, so i manually upgraded fron RC29, to RC30,
one day, at work, i got a notification to go from RC30 to RC33 OTA.
petko64 said:
I have a T-mobile G1 on Rogers in canada with a data plan,
YES, YOU WILL EVENTUALLY GET THE UPDATE.
Originally i believed that i do not get updates, so i manually upgraded fron RC29, to RC30,
one day, at work, i got a notification to go from RC30 to RC33 OTA.
Click to expand...
Click to collapse
That could be because updates were stopped halfway through on one of the updates to make sure they fixed some security holes.
The last update I got before any T-mobile customers and I was on AT&T. I actually pulled the file off my phone and gave it to JesusFreke but by the time he got it the link had already been posted.
Hi all,
A little while ago I screwed up one of the software tweaks in the app 'Galaxy S Tweaker', then my phone would not boot. So I decided I might as well attempt to flash an I9000 Froyo ROM (can't remember the exact one at them moment, but either JP3 or JM5, I think.) and it is running great! except for one pretty big thing...my phone doesn't work as a, well, phone. It simply says: 'no service' and I'm obviously not able to send/receive text messages or calls.
Before I had 'bricked' my phone, I had it unlocked and running fine on the Telus network here in Canada. (I used the popular method as detailed in a different XDA thread, but it would seem as though Samsung has patched that, because I tried that method again, but to no avail.)
I would also like to note that I have tried 2 online unlocking services, and BOTH of them have come up negative, saying they can't retrieve an unlock code for my device!
Does anyone know what the problem could be?
Thanks,
Dylan
I'm thinking about getting a Moto X Style just for use everywhere I have wifi coverage (I'd have no cellular service/carrier at all). Does anyone know if I will still get all of the security/OS updates or can they only come from a carrier?
If you buy it from Motorola directly, the carrier is not involved. But don't think that means you'll get timely updates. Apparently Moto used to be good at this, but no longer. Mine is still on Android Security Patch Level: February 1, 2016
Can anyone confirm they've gotten an OTA update without a SIM card installed or been able to load current updates with Motorola Device Manager?
xdafan15 said:
Can anyone confirm they've gotten an OTA update without a SIM card installed or been able to load current updates with Motorola Device Manager?
Click to expand...
Click to collapse
I have with my Moto G3 which is unlocked, purchased from Motorola. Haven't tried with the Pure, but it is a carrier free device as well.
If you watch logcat and check for updates on the device, you'll see it connects to a Motorola server to check as well.
Pretty sure that's how all the tmo people got the update before it was released to them.
Has anyone had experience using Motorola Device Manager to load current updates or are they only available over the air?
MXPE is not carrier branded so you can get OTA without a SIM. Doesn't matter where you buy the phone (I have seen it sold on Amazon and Best Buy as well)
Sent from my awesome phone!
xdafan15 said:
Can anyone confirm they've gotten an OTA update without a SIM card installed or been able to load current updates with Motorola Device Manager?
Click to expand...
Click to collapse
I received my Moto X Style on Friday, didn't have a sim card inserted when I plugged it on. It was on Android 5.1.1 and as soon as I set out the home wifi, it told me there was a software update, and I got 6.0 installed.
xdafan15 said:
Has anyone had experience using Motorola Device Manager to load current updates or are they only available over the air?
Click to expand...
Click to collapse
Has anyone used MDM?
xdafan15 said:
Has anyone used MDM?
Click to expand...
Click to collapse
We're all trying to tell you that it works, it's fine, you don't need to worry. Carriers are not involved in delivering updates for unlocked devices because a) nothing is customized by any carrier on the unlocked device and b) your only relationship with them is via the SIM card, and you haven't paid them anything for the device. At the risk of sounding condescending, the thing you're worried about is just not how it works.
However, I went ahead and tried to install MDM just to test it out, and it seems that software has other unrelated problems and I can't use it.
So instead, I turned off mobile data and took the SIM card out, and confirmed yet again that it can connect to Motorola's update server and report that there are no updates available. So that's the real problem: you can update the device, but there are no updates to be had.
Edit: maybe the confusion is that term "OTA". Are you just talking about OTA as in over the cell network, or are you referring to WiFi as "OTA" as well? You know that those two work differently, right? OTA updates from a carrier via the cell network clearly only come from them, and clearly can't happen without a SIM. But there's not much difference in downloading the update from Motorola's server via WiFi on the device vs. downloading it via WiFi on your computer with MDM and sending it to the device via USB; it still comes from Motorola.
thejoelpatrol said:
We're all trying to tell you that it works, it's fine, you don't need to worry. Carriers are not involved in delivering updates for unlocked devices because a) nothing is customized by any carrier on the unlocked device and b) your only relationship with them is via the SIM card, and you haven't paid them anything for the device. At the risk of sounding condescending, the thing you're worried about is just not how it works.
However, I went ahead and tried to install MDM just to test it out, and it seems that software has other unrelated problems and I can't use it.
So instead, I turned off mobile data and took the SIM card out, and confirmed yet again that it can connect to Motorola's update server and report that there are no updates available. So that's the real problem: you can update the device, but there are no updates to be had.
Edit: maybe the confusion is that term "OTA". Are you just talking about OTA as in over the cell network, or are you referring to WiFi as "OTA" as well? You know that those two work differently, right? OTA updates from a carrier via the cell network clearly only come from them, and clearly can't happen without a SIM. But there's not much difference in downloading the update from Motorola's server via WiFi on the device vs. downloading it via WiFi on your computer with MDM and sending it to the device via USB; it still comes from Motorola.
Click to expand...
Click to collapse
Thank you for trying to test MDM for me, I really appreciate that. I wish it had worked properly.
I'm not asking about MDM because I'm still questioning the OTA availability. That has been answered.
I'm asking because in the past, rooted phones wouldn't accept OTAs, so I'm trying to figure out how to apply security updates without having to un-root, then re-root. Maybe the answer to this is obvious, but it isn't to me.
Maybe the OTA availability problem mentioned above isn't an issue any more as I believe Marshmallow uses systemless root? I probably will stick with the stock ROM, just rooted.
@thejoelpatrol, are you rooted? If so, have you continued to be able to apply updates OTA?
xdafan15 said:
Thank you for trying to test MDM for me, I really appreciate that. I wish it had worked properly.
I'm not asking about MDM because I'm still questioning the OTA availability. That has been answered.
I'm asking because in the past, rooted phones wouldn't accept OTAs, so I'm trying to figure out how to apply security updates without having to un-root, then re-root. Maybe the answer to this is obvious, but it isn't to me.
Maybe the OTA availability problem mentioned above isn't an issue any more as I believe Marshmallow uses systemless root? I probably will stick with the stock ROM, just rooted.
@thejoelpatrol, are you rooted? If so, have you continued to be able to apply updates OTA?
Click to expand...
Click to collapse
Ah, ok, now see that is a whole other issue. That would have been good to know from the start. No, I'm not rooted, but it's getting increasingly tiresome, so I'll probably need to do that at some point. I've mostly used Cyanogenmod in the past but last I checked it wasn't ready for clark. I'll probably take a look at some stock root options when I get around to it. And so your concern here is worth thinking about.
Hi all,
My old vibe died and couldnt find a better phone on the market since 2015 so got a new one. However I dont know what the heck is installed on this one.
I have never rooted before but have a cs degree so im not out my league. With the details in the image below, do you know what I can do to get stock installed?
The phone has a trojan application called fun weather and i cant remove it. Have done everything from root access to hard deleted. But as soon as i get wifi again it downloads. Are all custom roms like this so the developer can make cash? I also dont know if this is ROW or China. It has google services installed.
VERSION AND DETAILS SCREENSHOT HERE (2K image here fills the whole browser.)
http://i.imgur.com/jLn2bih.jpg
Regardless apprecaite the help here.
C
OK so after failing to remove it I was able to flash the device.
I made a guide for my future self and also to show that the China mobile varient can be easily flashed and still work. Im from UK and no issues with SIM. It also read my philippines card no problem
corriejgreen said:
OK so after failing to remove it I was able to flash the device.
I made a guide for my future self and also to show that the China mobile varient can be easily flashed and still work. Im from UK and no issues with SIM. It also read my philippines card no problem
Click to expand...
Click to collapse
Maybe this was one of the early firmware. Lenovo has given 5.0 to this mobile. Why didn't you try to update it?
Hey guys,
So i have the canadian version of the mini, with the details as follows:
model number: ZTE B2017G
android version: 6.0.1
build number: ZTE B2017G+BELLV1.0.0B06
and I cant update it, ive downloaded the nougat update file from here: https://forum.xda-developers.com/showpost.php?p=73257562&postcount=13
and attempted to update it in system setting from sd card, but got the message: package mismatch installation aborted.
Update didnt work from recovery either. Any ideas on how to update it, or if its even possible? Thanks!!
talha746 said:
Hey guys,
So i have the canadian version of the mini, with the details as follows:
model number: ZTE B2017G
android version: 6.0.1
build number: ZTE B2017G+BELLV1.0.0B06
and I cant update it, ive downloaded the nougat update file from here: https://forum.xda-developers.com/showpost.php?p=73257562&postcount=13
and attempted to update it in system setting from sd card, but got the message: package mismatch installation aborted.
Update didnt work from recovery either. Any ideas on how to update it, or if its even possible? Thanks!!
Click to expand...
Click to collapse
Doesn't seem like it's updatable at this point in time.
Reached out to ZTE: No updates available. If there were to be it would be through bell/Virgin as it's specific build/firmware/model.
Reached out to Virgin, bell and PC mobile as well. If something interesting comes from it I will surely post.
parawizard said:
Doesn't seem like it's updatable at this point in time.
Reached out to ZTE: No updates available. If there were to be it would be through bell/Virgin as it's specific build/firmware/model.
Reached out to Virgin, bell and PC mobile as well. If something interesting comes from it I will surely post.
Click to expand...
Click to collapse
Cool, thanks man.
Btw, is the Bell/Virgin model rootable? So we can put custom rom on it? Would it be the same roms other models would use?
I know tdm is working on one atm (https://forum.xda-developers.com/axon-7-mini/development/recovery-twrp-7-1-unofficial-t3685339)
talha746 said:
Cool, thanks man.
Btw, is the Bell/Virgin model rootable? So we can put custom rom on it? Would it be the same roms other models would use?
I know tdm is working on one atm (https://forum.xda-developers.com/axon-7-mini/development/recovery-twrp-7-1-unofficial-t3685339)
Click to expand...
Click to collapse
I think it should be but I haven't tried yet as I am using this phone as my daily. Maybe if I grab another one.
I need help too with the canadian version. There is no option to activate the NFC...
lanautechdroid said:
I need help too with the canadian version. There is no option to activate the NFC...
Click to expand...
Click to collapse
I don't think this version has NFC. There is no mention of it anywhere.
https://www.ztedevices.ca/axon-cat/axon7mini.html
USA version does mention it.
https://www.zteusa.com/axon7mini/
I got the Axon 7 mini from PC Mobile as well. Looks like the Canadian mini is a variant P852A15H, without NFC.
Any idea how to get rid of the carrier name at the top right? SytemUI tuner doesn't seem to activate either.
The mini is really sleek and light! Haven't had the battery issues mentioned in reviews either. Wish we could update to N though.
For what it's worth, there may be some activity behind the scenes for a minor update to the Canadian Axon 7 Mini late this month.
If this individual is to be believed, it will be bug fixes and security patches ONLY. That is, it will NOT be an upgrade to Nougat; we'll still be stuck on Marshmallow. But at least we'd end up with a security patch newer than late-2016.
https://community.zteusa.com/discussion/comment/228993/#Comment_228993
I wonder if this method will work for Canadian version:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
fy0u1 said:
I wonder if this method will work for Canadian version:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
Click to expand...
Click to collapse
It's said somewhere in the ZTE section that someone tried it and bricked his phone.
zigonneux said:
if you read more posts, it's said somewhere that someone tried it and bricked his phone.
Click to expand...
Click to collapse
That was after I posted here
So, are there any news on rooting+custom ROM for this device?
Security patch today
Hi,
Just got ZTE B2017G_BELLV1.0.0B08 this morning ....
yergy said:
Hi,
Just got ZTE B2017G_BELLV1.0.0B08 this morning ....
Click to expand...
Click to collapse
Did it upgrade to Nougat? What version of Android is it on after the B08 update.
Bettaxis said:
Did it upgrade to Nougat? What version of Android is it on after the B08 update.
Click to expand...
Click to collapse
No nougat, still M, only security patch february 2018. Better than nothing
yergy said:
No nougat, still M, only security patch february 2018. Better than nothing
Click to expand...
Click to collapse
Confirmed. 105.67 MB download, the device stays on Marshmallow. It brings the device from the November 1, 2016 security patch to February 5, 2018.
This is the first OTA ever released for the Canadian variant. It would include fixes for some pretty high-profile vulnerabilities, such as Blueborne, Krack, and Spectre, so it's definitely welcome.
talha746 said:
I have the canadian version of the mini
Click to expand...
Click to collapse
Bettaxis said:
I got the Axon 7 mini from PC Mobile as well. Looks like the Canadian mini is a variant P852A15H, without NFC.
Click to expand...
Click to collapse
Can you please execute the following adb command and post your product name here?
Code:
adb devices -l
List of devices attached
... device product:P852A11 model:ZTE_B2017G device:tulip transport_id:1
The adb devices -l command lists the following properties: ro.product.name, ro.product.model and ro.product.device
Hint: I downloaded the latest ADB tool from https://developer.android.com/studio/releases/platform-tools.html#download
I just finished a live chat with a ZTE rep. I give him all informations he asked and he told me that he's submitting that info to R&D and they will get back to me within 5 - 6 business days with a package update.
My build number is ZTE B2017G_BELLV1.0.0B08
I don't keep my hope very high on this, but hey you never know ...
I'll post what comes out of this ...
yergy said:
I just finished a live chat with a ZTE rep. I give him all informations he asked and he told me that he's submitting that info to R&D and they will get back to me within 5 - 6 business days with a package update.
my build number is ZTE B2017G_BELLV1.0.0B08
I don't keep my hope very high on this, but hey you never know ...
.
Click to expand...
Click to collapse
good luck with that
The Canada-specific version of the Axon 7 Mini was not sold on the open market, but rather was sold as a bundle through one of Bell Canada's affiliates. (I am aware of it being sold through Virgin Mobile and PC Mobile.) As such, it is running a customized OS that was approved by Bell Canada. The Bell Canada-specific OS has always been visually distinct from the version of the OS that shipped on open-market versions of the Axon 7 Mini; in my opinion it appears quite a bit more similar to the vanilla Android experience, with the exception of the preinstalled Bell account management apps.
Unfortunately, because the phone was bundled through Bell Canada, that means that ZTE will also be obliged to get Bell Canada's approval of any OS updates that may be offered for the phone. We've already seen, with the patch that was released earlier this year, that the OS update path being approved by Bell Canada is following a very different track from what ZTE has been offering on the open market, and I don't expect to see that change any time soon.
And it really doen't matter if ZTE's engineering department is technically capable of offering Nougat or newer for this device. They'd still have to get it cleared by Bell Canada first before they could distribute it.