Related
im about to get 16gb vodafone version from a friend of mine who bought it in Netherlands. im just curious...are there any differences on hardware/software? i mean:
1. some vodafone mark on the phone
2. some mark on boot
3. or some programs that are preinstalled/modified
4.are there problems with root and rom flashing?
or its just like normal 8gb version? dude told me that its locked version but unlock code is in some phone file or something(?!)
I've got a 16GB galaxy s from vodafone (UK).
No branding on the phone anywhere - no logo or anything on boot either.
Haven't rooted or flashed rom yet so don't know, but it will enter recovery mode, etc.
Hope that helps
prcach said:
im about to get 16gb vodafone version from a friend of mine who bought it in Netherlands. im just curious...are there any differences on hardware/software? i mean:
1. some vodafone mark on the phone
2. some mark on boot
3. or some programs that are preinstalled/modified
4.are there problems with root and rom flashing?
or its just like normal 8gb version? dude told me that its locked version but unlock code is in some phone file or something(?!)
Click to expand...
Click to collapse
The 16gb's were limited edition from Vodafone. They are completely unbranded, and the ones WITHOUT the voda sticker on the box are SIM unlocked too.
That's true for all the UK models, I assume the Dutch ones will be the same.
The 8gb are all SIM locked and branded to hell too.
ibizaGTi said:
The 16gb's were limited edition from Vodafone. They are completely unbranded, and the ones WITHOUT the voda sticker on the box are SIM unlocked too.
That's true for all the UK models, I assume the Dutch ones will be the same.
The 8gb are all SIM locked and branded to hell too.
Click to expand...
Click to collapse
if its in some case locked...how hard would it be to unlock it?
"The 16gb's were limited edition from Vodafone. They are completely unbranded, and the ones WITHOUT the voda sticker on the box are SIM unlocked too."
The same in Ireland
prcach said:
if its in some case locked...how hard would it be to unlock it?
Click to expand...
Click to collapse
You can find a FREE tool (Unlock for the Galaxy S) in the Android Market to get the unlock codes, or search in the forums for one of these tools
I have the 8gb GT-I9000 which I got from 02, it was the phone only, no sim, for £329, and it's completely unbranded, it has an O2 wallpaper.
I Don't know if it's unlocked as I want to get used to it before I try to change anything
I got a 8gb i9000 from Vodafone here in the UK too. No branding or vodafone marks or anything. It's also unlocked too.
Sent from my GT-I9000 using XDA App
I have the dutch vodafone 16GB galaxy S.it is completely free from branding our whatsoever, no way to tell it's a vodafone phone, and it came simlock free...
Sent from my GT-I9000 using XDA App
Hi, I bought a dutch vodafone Galaxy S (16Gb) secondhand. But i suspect that the previous owner flashed it since it's rooted and runs JM2.
Can you let me know which is the stock rom for the dutch vodafone SGS's?
I also have a SGS 16 gb from vodafone-NL. It comes with JM2 out of the box. And imho root it is a must ;D.
Btw, 3 button recovery mode is disabled. Anyone else from Holland with 3 button disabled?
Sent from my GT-I9000 using XDA App
Mine is also running jm2. But I can't see any paid apps in my market.is that normal? I thought it might be caused by unofficial firmware.
I have the dutch vodafone 16gb sgs. Completely unbranded, no simlock.
It has jm2 update 1out of the box and 3 button enabled.
I only rooted it and installed oclf and rommanager.
Realy fast and no lagg at all!
Send from my Galaxy S using XDA app
Mine came from Voda UK as a warranty replacement for a WinMo. No branding, unlocked with only a small Voda logo on the r/h side of the box.
Came with the JF3 firmware but now booted n rooted on JPC 2.2 and I love it (well almost).
Just wondering has anyone got a dump of the UK vodafone firmware, I forgot to dump mine when I flashed it via Odin.
Thanks in advance
maick said:
I also have a SGS 16 gb from vodafone-NL. It comes with JM2 out of the box. And imho root it is a must ;D.
Btw, 3 button recovery mode is disabled. Anyone else from Holland with 3 button disabled?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Mine is dutch and also had 3br disabled. Just to recap to my earlier question. Is there a reason that my marketonly shows free apps? Apparently I'm running official jm2, and its rooted. None of the market fixes work. I tried fix from sgs tools app and eris market fix. But still only free apps are available.
maick said:
I also have a SGS 16 gb from vodafone-NL. It comes with JM2 out of the box. And imho root it is a must ;D.
Btw, 3 button recovery mode is disabled. Anyone else from Holland with 3 button disabled?
Click to expand...
Click to collapse
Maick, I got this too.
Only got it last wednesday, and have tried entering Recovery / Download modes multiple times already.
With the deviced powered on, powered off, different sequences of the buttons involved, on USB, off USB, with Kies active or inactive.
It just doesn't respond to any of those button combos.
It just gives me the standard shutdown menu when the phone is on, when the phone is off it just boots and when I keep pressing the power button it's going into the boot logo loop, rebooting the phone on end, until I stop pressing the power button.
Yay. Now I fear for rooting and especially flashing the device, since I might brick it when the flashing goes wrong.
Hi there!
When I rooted mine I got to recovery mode using the android SDK method and as far as I know everyone should be able to get to recovery mode via the android sdk.
Later today I will attempt to flash the 3br patch (you can find more about the patch on the sgs android development forum here in xda) and cross my fingers to not brick it. If I brick it I will bring it back to vodafone. ;P
If you want to attempt to get to recovery mode using the android sdk, search a but on youtube and you will find out exactly what to do.
Hope this info can help you or anyone else in the same situation. ;D
Sent from my GT-I9000 using XDA App
I just did Richthofen's patch, and it works like a charm. 3BR functions like it should and we're safe again from faulty flashes. Hooraay.
Be sure that when you use the simple patch, that you are at least running JM1, otherwise you'll end up bricked.
Just flashed the fix a few minutes ago and now I am the proud owner of a 3BR enable SGS I9000
strangest thing, i confirm the update and it closes and thats it. It doesnt show a download in the status bar or anything. any ideas?
Mine still says it is already upto date even though I know the 2.3.3 update is out for almost everyone else?!?
FK1983 do you have an o2 branded phone? (with o2 crap installed on/o2 boot up screen?) If so then you are probably waiting for o2 to ok the actual update as well as installing all their extra crap onto 2.3.3 before they let you update
Same probably for magicriggs and anyone else that has not recieved their updates yet. The update you are seeing will be the generic 2.3.3 update you have to wait for verizon to ok the update first then customise it with all the crap/restrictions they want on it.
Mozza2k11 said:
FK1983 do you have an o2 branded phone? (with o2 crap installed on/o2 boot up screen?) If so then you are probably waiting for o2 to ok the actual update as well as installing all their extra crap onto 2.3.3 before they let you update
Same probably for magicriggs and anyone else that has not recieved their updates yet. The update you are seeing will be the generic 2.3.3 update you have to wait for verizon to ok the update first then customise it with all the crap/restrictions they want on it.
Click to expand...
Click to collapse
It's on Virgin Mobile, must be why?
FK1983 said:
It's on Virgin Mobile, must be why?
Click to expand...
Click to collapse
It doesn't matter which network the phone is on. If you got it direct from virgin or it has the virgin boot up screen then its virgin "branded". Until virgin or any other network decides to ok the update (and make any modifications they want) unfortunately you will be waiting. Unless you unlock your boot then you can flash the generic 2.3.3 that people with unbranded phones got.
P.s i said o2 since the o2 logo is under your name
Would that be the same case with me? I originally got my XP from my carrier but I had already network unlocked it with a code that I purchased from Theunlock.ca and de-branded it with a generic R800i UK firmware where mines was originally a R800a.
Flava0ne said:
Would that be the same case with me? I originally got my XP from my carrier but I had already network unlocked it with a code that I purchased from Theunlock.ca and de-branded it with a generic R800i UK firmware where mines was originally a R800a.
Click to expand...
Click to collapse
No this only applies to people with a branded phone and a locked bootloader. If you unlock your boot which you have done you can do as you did and flash the generic fw (without extra branded crap on just standard bloat) From now on you will just update using the fw posted here instead of waiting for rogers.
Cool, thanks for clearing that up a bit!
But I didn't unlock my bootloader, I can't because it came from my carrier. What I unlocked was the network and now I can use another SIM card from a different carrier on it if I wanted to. But I guess it's still the same since I was able to flash it with a generic fw already.
I had no issues with the updating itself.
But I noticed that the standard music player sometimes doesn't play sound at all. I first have to kill it with a program like 'Advanced Task Killer' and then it works again. Anyone else has this problem?
My Unlocked XP can download the update but fails on the install, its attempts to install, resets, unpacked update, then attempts to update (icon on screen goes from two dots and openbox icon, to three dots and phone with arrow above) then screen goes blank, phone boots as normal (takes about 2-3mins) then warns that update was unsuccessful after pincode entry.
Thought it might due to lack of internal space, so cleared 80 megs on application space and still no luck.
Sent from my R800i using XDA App
Bricked after OTA update
My husband's Xperia play got bricked today after an OTA update. It had no customized software, just an unlocked bootloader.
Looks like this issue it's just affecting those ones with an unlocked one.
I just checked for the update manually on my PLAY earlier today and it was able to find the update. But I'm not going to install it until you can root v2.3.3 on a locked bootloader.
ritap said:
My husband's Xperia play got bricked today after an OTA update. It had no customized software, just an unlocked bootloader.
Looks like this issue it's just affecting those ones with an unlocked one.
Click to expand...
Click to collapse
If you unlock your bootloader you cannot use SEUS or OTA to update your phone anymore. You will have to flash the lastest fw onto the phone. See here to 2.3.3 firmware http://forum.xda-developers.com/showthread.php?t=1097591 also if you flash the first one you can then flash the rooted 2.3.3 http://forum.xda-developers.com/showthread.php?t=1098736 Same goes for Da22a since your XP is unlocked
So still no way to root 2.3.3 on a locked bootloader yet, only with an unlocked bootloader at the moment? Because it's not possible for my to unlock my bootloader on my PLAY because it was originally from my carrier.
Mozza2k11 said:
If you unlock your bootloader you cannot use SEUS or OTA to update your phone anymore.(snip)
Click to expand...
Click to collapse
I see you're right and i wish i had my husband have a look here before even thinking about it.
The problem is: while SEUS prevents you from unintentionally doing that, which i regard as fair, OTA just bricks your phone without further notice.
We've taken it to SE for repair, which they should do for an amount of euros they still haven't notified us (you see, it's out of warranty). Easy money, then: tell people how to unlock their phones and then spread some code which bricks unlocked phones .
I don't think SE speculated in making money here. It's a more like a 'here you go' now you have control over your phone to do almost what you like. The main target here I think is devs and flashaholics and such. There's always a risk involved with unlocking your bl and changing the S-ON to S-Off and such things. Ofcause you loose your warranty otherwise every john/jane does would come back and reclaim a new device when they bricked there phone. This comes from a demand within the android community that this is an option.
Further more I don't think SE knew about this. The .img to flash is not comming from We but from this community so they can't be held responsible for putting out an OTA that bricks your phone cause of what people might flash onto there phones. I hope that they will make some kind of check in the software updater similar to SEUS in the future or the ones who make flasheble .imgs will be able to disable OTA in the .imgs to come or upload a new one for people to use.
Regards Dousan...
ritap said:
I see you're right and i wish i had my husband have a look here before even thinking about it.
The problem is: while SEUS prevents you from unintentionally doing that, which i regard as fair, OTA just bricks your phone without further notice.
We've taken it to SE for repair, which they should do for an amount of euros they still haven't notified us (you see, it's out of warranty). Easy money, then: tell people how to unlock their phones and then spread some code which bricks unlocked phones .
Click to expand...
Click to collapse
Im not sure SE will repair your phone. I have read other people on here have sent it in for repair and got it back the same. Today a fix for bricked phones has come out http://forum.xda-developers.com/showthread.php?t=1126354. I would suggest getting your phone back from SE and fixing it yourself. Since the above thread's fix is free (you could always donate to Bin4ry & Blagus, dont know who else helped?)
I also agree with Dousans comments. Below a quote from http://unlockbootloader.sonyericsson.com/
Therefore, you should only unlock the boot loader of your phone if you are an advanced user with good knowledge of the technology and risks involved. We strongly recommend that standard users NOT unlock the boot loader, as it is not needed
Click to expand...
Click to collapse
Also not sure how long this has been posted on the site but se knows now and it working on a fix to stop it.
Note: We have seen in some forums that customers unlocking the boot loader on their phones have experienced problems when they accept a FOTA (Firmware upgrade Over The Air) update. The issue has been reproduced and we are working on a solution. For customers that have unlocked the boot loader please do not accept the Firmware upgrade OTA.
Click to expand...
Click to collapse
Rogers official one comes July 1st. (Canada Day)
Mozza2k11 said:
Im not sure SE will repair your phone. I have read other people on here have sent it in for repair and got it back the same. Today a fix for bricked phones has come out http://forum.xda-developers.com/showthread.php?t=1126354. I would suggest getting your phone back from SE and fixing it yourself. Since the above thread's fix is free (you could always donate to Bin4ry & Blagus, dont know who else helped?)
I also agree with Dousans comments. Below a quote from http://unlockbootloader.sonyericsson.com/
Also not sure how long this has been posted on the site but se knows now and it working on a fix to stop it.
Click to expand...
Click to collapse
You and Dousan may be right but indeed after unlocking the BL we didn't flash it; moreover, after that the phone has been working perfectly for more than a month, since the ota update of course: so it's their software which has bricked the phone, not us.
Moreover, it's true that we lost our warranty, and it's fair that those Johns/Janes won't get a new phone for free, but this doesn't allow then to spread around dangerous software and allowing free repair only to "warranty" customers.
I've already had a look at the fix described in this forum but it didn't fit, Blagus told me there was no solution, the payservers were down so i took the Play to SE...
Anyone know how to get flashtool to recognize the play? The only options are arc x10 x8 etc.
Same as this guy:
how did you guys even get the flashtool to work with the play? ive got the latest version and i keep getting an error saying it cant identify my device and the only options are for x10, x10 mini, x10 mini pro, x8 and arc, just curious
Click to expand...
Click to collapse
I have a Samsung Galaxy S. The details on 'About' menu of the phone are:
Model Number:
GT-I9000
Firmware version:
2.1-update1
Baseband version:
I9000XXJF3
Kernel version:
2.6.29
[email protected] #2
Build number:
ECLAIR
I use the phone on T-Mobile. I have no idea if it is locked, etc, but was purchased there from new (well a reseller website, not sure where it physically came from).
I have never updated this phone. This is as the phone was purchased one year ago. I have not installed any new ROMs, official or custom. I am the only owner and therefore no it has never been updated without my knowledge.
I am aware a new version of Android is out and have installed the Kies software, wishing to do this the 'official' route.
I get the following error message in Kies:
The current version is not an official release.
Firmware upgrade service for unofficial versions is not supported.
Current firmware version: PDA:JF4 / PHONE:JF3 / CSC:JE6 (TMU)
Any help at all? I really want to get this updated, especially after the hassle of install the terrible Kies software! I would prefer to do this the 'official' route without installing custom ROMs etc.
Has anybody seen such a message before? Thanks!
If your using a T-Mobile version, use Samsung Kies Mini. Search for it in google.
carlo.edmon said:
If your using a T-Mobile version, use Samsung Kies Mini. Search for it in google.
Click to expand...
Click to collapse
Thank you very much for the reply.
I am on T-Mobile UK and got the phone from them. I assume this means I am using a T-Mobile UK version. Can Samsung Kies Mini upgrade T-Mobile UK? If so, can you please provide a link? When searching via Google all I can find is Kies Mini for Mac. There are some old versions that come up, too, but these seem to be for specific phones.
If you could give any further advice on how to upgrade my Samsung Galaxy S i9000 on T-Mobile UK that'd be great .
Thanks.
PS - Is this part of my original post:
Kernel version:
2.6.29
[email protected] #2
relevant at all? Should it say 'root'? I have never 'rooted' the phone. Could this be why Kies is unhappy with my firmware version? Thanks.
Try this one:
"ars.samsung.com/customer/usa/jsp/faqs/faqs_view_us.jsp?SITE_ID=22&PG_ID=2&PROD_SUB_ID=557&PROD_ID=560&AT_ID=341559"
It's for US but just give it a try. After installing the software, let it update to the latest version then connect your phone. My sister's phone came from US and I used this to update hers.
carlo.edmon said:
Try this one:
"ars.samsung.com/customer/usa/jsp/faqs/faqs_view_us.jsp?SITE_ID=22&PG_ID=2&PROD_SUB_ID=557&PROD_ID=560&AT_ID=341559"
It's for US but just give it a try. After installing the software, let it update to the latest version then connect your phone. My sister's phone came from US and I used this to update hers.
Click to expand...
Click to collapse
Thanks for the link, I had found that before but ignored it because it does not mention i9000.
I'll give it a while incase any other ideas come in, otherwise I'll give it a go. The fact it's for the US (and you used it to update a US phone) does not give me confidence it'll work for a UK phone. I'll try it as a last resort, but I'd like to see if there are any other options for the moment.
I've given T-Mobile UK a call who were useless -If you cannot update because of Samsung Kies then you'll have to contact Samsung, not us. I contact them and they basically say 'take it into a Samsung authorised repairer'. I call my nearest one and it sounds far from a professional outfit - 'Just drop it off'. I'd hoped they could update it on the spot but I was told I'd have to leave it with them... I cannot afford to be without my phone, though.
It looks like I might have to stick to the current version I've got, I cannot get Kies to give any message other than the one in the original post... And none of the 'official' support lines are bothered. No wonder people don't bother with the 'official' releases... Though I'd like to in order to keep my warranty intact.
Thanks.
Use odin and update it your self or contach t mobile about your problem
got-petrol said:
Use odin and update it your self or contach t mobile about your problem
Click to expand...
Click to collapse
Thanks for the reply. I have tried contacting T-Mobile already, see previous post (relevant section below):
I've given T-Mobile UK a call who were useless -If you cannot update because of Samsung Kies then you'll have to contact Samsung, not us. I contact them and they basically say 'take it into a Samsung authorised repairer'. I call my nearest one and it sounds far from a professional outfit - 'Just drop it off'. I'd hoped they could update it on the spot but I was told I'd have to leave it with them... I cannot afford to be without my phone, though.
I'm basically left without any help from them. I'd rather not go down the Do-It-Yourself route, mainly because I do not understand all of the steps that need doing. Each guide is *slightly* different... And I've no idea which (specific) files I should download and from where... And kernel? And ROM? And.. Urgg. I also see Phone/PDA/CSC... It's a minefield for somebody that does not know enough and wanted an easy update.
I am starting to consider doing it myself but really need to find one definitive guide that I should follow.
Thanks.
I'm trying to update my SM-P605 Galaxy Note 10.1 2014 LTE to P605XXUBMJ9 and I am so confused by the manual process. I can't do OTA because I rooted and when I go to a ROM download site there are all these regions and carriers mentioned. I'm worried about bricking my device or carrier locking it to a company thousands of miles away. Can you help? Sorry for being so dumb but I've never bought a device outside of a store where they set everything up for you.
Current specs:
Android 4.3
P605XXUBMJ4 Baseband
3.4.0-1927787 [email protected] #1 Kernel
JSS15J.P605ZSUBMJ6 Build number
Enforcing SEPF_SM-P605_4.3_0002 SELinux status
I'm currently in the USA, using T-Mobile, and I was told by Amazon that the device is unlocked.
thatblokematti said:
I'm trying to update my SM-P605 Galaxy Note 10.1 2014 LTE to P605XXUBMJ9 and I am so confused by the manual process. I can't do OTA because I rooted and when I go to a ROM download site there are all these regions and carriers mentioned. I'm worried about bricking my device or carrier locking it to a company thousands of miles away. Can you help? Sorry for being so dumb but I've never bought a device outside of a store where they set everything up for you.
Current specs:
Android 4.3
P605XXUBMJ4 Baseband
3.4.0-1927787 [email protected] #1 Kernel
JSS15J.P605ZSUBMJ6 Build number
Enforcing SEPF_SM-P605_4.3_0002 SELinux status
I'm currently in the USA, using T-Mobile, and I was told by Amazon that the device is unlocked.
Click to expand...
Click to collapse
Being that its a ZS build it looks like its from China.
I would only flash P605ZS***** Builds if you are worried about locking it by mistake.
FYI: The first two digits after the model number are the region
http://www.cpkb.org/wiki/Samsung_firmware_naming_conventions#2._Region_code
scrosler said:
Being that its a ZS build it looks like its from China.
I would only flash P605ZS***** Builds if you are worried about locking it by mistake.
FYI: The first two digits after the model number are the region
http://www.cpkb.org/wiki/Samsung_firmware_naming_conventions#2._Region_code
Click to expand...
Click to collapse
Thank you a million times. I feel like such an idiot :S Do you know if there's an upgrade to MJ9 yet in the China region? Do I need to take any extra precautions to ensure it stays carrier unlocked and usable in the United States.
thatblokematti said:
Thank you a million times. I feel like such an idiot :S Do you know if there's an upgrade to MJ9 yet in the China region? Do I need to take any extra precautions to ensure it stays carrier unlocked and usable in the United States.
Click to expand...
Click to collapse
My understanding is the partition that holds the carrier info / locking info is not touched during a flash with Odin. HOWEVER, I never got into that unlocked device thing because I never had a need to.
Someone else may be better suited to the question than I but as long as you flash ZS based firmwares you should be fine as I did not see a carrier listed for that tablet in China so they may all be unlocked.
Actually, I only think the Verizon one is going to be the locked one but I dont know.
scrosler said:
My understanding is the partition that holds the carrier info / locking info is not touched during a flash with Odin. HOWEVER, I never got into that unlocked device thing because I never had a need to.
Someone else may be better suited to the question than I but as long as you flash ZS based firmwares you should be fine as I did not see a carrier listed for that tablet in China so they may all be unlocked.
Actually, I only think the Verizon one is going to be the locked one but I dont know.
Click to expand...
Click to collapse
You are very helpful in my quest to not ruin an expensive tablet. Do you know if there's an upgrade compatible with ZS for the MJ9 update? I honestly don't mind waiting if there's a chance I'll turn it into a paper weight. Not even a Kit Kat build just some bug fixes from what I understand.
Again, thanks for your help.
I just don't understand all the carrier builds of MJ9. Bloody heck some of em even have custom names which would be a good sign it's specific to region/carrier. So confused by this all
So maybe unroot your device and then you will have an Ota Update... Because if you'll use Odin for flash other firmware you won't be rooted yet, i think.
chabasse said:
So maybe unroot your device and then you will have an Ota Update... Because if you'll use Odin for flash other firmware you won't be rooted yet, i think.
Click to expand...
Click to collapse
Aren't OTA updates issued by providers? T-Mobile doesn't support this device so there's not going to be an MJ9 update. Ever. It's using an LTE frequency not even found in the States. I just bought it online because I didn't want to wait for somebody here to give me support. I'm simply trying to do a manual update without my device being a paperweight or waking up to expect a connection from cellular towers in Asia.
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.