I just got done chatting with Nokia support (both chat and email) about getting the required unlock.key file that you need to unlock the bootloader for the Nokia 8, which they said they would unlock. First, a little background. The process Nokia wants you to go through to get the file is to download an apk of theirs which will analyze your phone a bit and then generate a code which you put into a form on their website to get the file emailed to you. Rather clunky but alright. I do so, but then I get an error when the apk runs. "Error messages: Device not support." Very well. I then talk to support. Chat had no idea how to fix it. Email fared just as well. I will copypaste the entire exchange. (Save for the original email I sent as I forgot to save it. Sorry about that.)
Nokia said:
Welcome to Nokia Mobile Care ,
Thank you for your time writing us and thanks for using our Nokia 8 products. We understand why you came to us thats why we will try our best to assist you !
In order to assist you better and more accurately we would like you to provide us a little bit more information :
- Could you please provide us the screenshot with the error message? Thank in advance!
- How are you unlocking bootloader ? in which step are you at ?
Additionally we will provide you the steps unlocking bootloader below :
1-Go to https://www.nokia.com/en_int/phones/bootloader, accept the terms and sign in
2-Scroll down until you see the phone validation form.
3-Download and install NokiaPhoneUnlockBootloader.apk, there is an included link on the page.
4-You will receive a validation code that must be entered into the form on the website along with the email used, note the validation code is only valid for 30 minutes.
5-You will receive an email containing a link to download a file, the name will contain your IMEI number and have an extension .key, it should be renamed to "unlock.key"
6-Start the phone in download mode.
7-Download and set up ADB
8-Start an ADB shell and run the following commands, unlock.key must be in the platform-tools directory from the ADB setup
fastboot flash unlock unlock.key
fastboot oem unlock
You should then see
Unlock success!
9-then run the command
fastboot reboot
Remember that you are important to us and we're looking forward to your response.
If you have questions or face any difficulties, please contact us at your convenience.
Wish you all the best.
Best regards,
Nokia Mobile Care
-----------------------------------------------------------------------------------------------------------------------------------
© 2019 HMD global All rights reserved.
Nokia is a registered trademark of Nokia Corporation.
HMD global is the exclusive licensee of the Nokia brand for phones and tablets.
-----------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
S5Guy said:
I have downloaded the official apk from Nokia to get the verification code to put on the website form. When I launch the app and put in my email though, it merely shows the error message shown in the attachment.
Click to expand...
Click to collapse
Nokia said:
Thank you for getting in touch with Nokia Mobile Care. It's important for us to have you as our customer.
I can see that you are trying to unlock your phone's bootloader, you have already downloaded the app and you are receiving the message saying that "device not supported".
HMD Global allows the bootloader on certain Nokia phones to be unlocked, allowing for customizations. This feature is intended for developers only.
Once the device is being unlocked, it is no longer covered by the manufacturer's limited warranty provided by HMD Global.
If you have religiously followed the steps my colleague provided to you on the previous e-mail and after it you have received the message "Device not Supported" this mean that your device is not supported to have the bootloader unlocked.
If you are facing some issue with your phone, you can send it to a repair center, out specialists has the information on how to handle it. Note that Nokia only provides the possibilities to unlock bootloader to developers.
We hope that the above information is useful.
Any other question you may have are always welcome. Please feel free to contact us again.
You can reach us via chat daily, English support is available 24/7. The live technical support channel is easily accessible from the Nokia support application your Nokia smartphone and from your PC, at: https://www.nokia.com/en_int/phones/support#contact-us.
Kind regards,
REDACTED
Nokia Mobile Care
[email protected] email is operated by HMD global, the exclusive licensee of the Nokia brand for phones and tablets. Nokia is a registered trademark of Nokia Corporation, visit us online at www.nokia.com/mobile-support
© 2019 HMD global All rights reserved.
Click to expand...
Click to collapse
S5Guy said:
"If you have religiously followed the steps my colleague provided to you on the previous e-mail and after it you have received the message 'Device not Supported' this mean that your device is not supported to have the bootloader unlocked."
^ This is not correct at all. At least for the Nokia 8. https://twitter.com/sarvikas/status/1045298106818949120
I have followed the prior instructions rigorously, but since the apk does not work, I must ask you for the needed "unlock.key" file. I am very well aware of the consequences of unlocking the bootloader.
Click to expand...
Click to collapse
Thank you for getting back to us. I'm sorry to hear that the previous solutions didn't make any difference.
I can see that you are not happy about the previous answer you have had. I understand that can be frustrating sometimes.
As explained before the allowing will depend on many factors, as market, for example. If you have the app running well, if you have tried all the steps to have your bootloader unlocked and still receiving the message "device not supported" there is no other reason than that the app itself is saying the device you are trying to unlock is not supported.
Did you tried to uninstall and reinstall the app? did you tried to restart the process?
Note that here we are a customer care for technical issues customer may face with their device, we do not produce the rules or the policy we just follow then. There is no other advise to you at this moment.
If you have any other question not related to bootloader, please feel free to get back to us any time.
You can reach us via chat daily, English support is available 24/7. The live technical support channel is easily accessible from the Nokia support application your Nokia smartphone and from your PC, at: https://www.nokia.com/en_int/phones/support#contact-us.
Kind regards,
REDACTED
Nokia Mobile Care
[email protected] email is operated by HMD global, the exclusive licensee of the Nokia brand for phones and tablets. Nokia is a registered trademark of Nokia Corporation, visit us online at www.nokia.com/mobile-support
© 2019 HMD global All rights reserved.
Click to expand...
Click to collapse
-
So basically, to sum up, if you're thinking of unlocking the bootloader at all for any reason, steer WAY CLEAR of this phone. My phone may for whatever reason have fallen through the cracks perhaps, but a lot more people than me are reporting this issue. On top of that, I've checked my phone's IMEI to be sure it wasn't stolen or fake and it was perfectly fine and legit. Honestly, I hate that I have to post this message because the Nokia 8 actually has some features I like that aren't really on other phones, but because of this software travesty, I can't recommend it at all.
Nokia, if you're out there, this is a disgrace in both software and support. Please fix this.
Hi
I have the Nokia 8 TA-1012 but I have not tried to unlock the BL. I am currently on Pie so see no reason for doing so as I am happy with the OS.
As most people do not buy a phone to modify the OS I see no problem not recommending this phone for normal use.
Sent from my TA-1012 using Tapatalk
While I didn't unlock through official methods, it might be good to figure out what models of Nokia 8 are affected. Maybe a specific model is affected?
ironman38102 said:
While I didn't unlock through official methods, it might be good to figure out what models of Nokia 8 are affected. Maybe a specific model is affected?
Click to expand...
Click to collapse
It is not related to models, but instead to the build ID's the phones run. (Nokia software is completely generic) Back when Nokia announced the unlock process and the october security patch dropped, phones on october patch started to
report the same issue the OP has encountered. One or two weeks later (after some public outrage ) the app started working again, likely because Nokia added the build ID of the october patch to their
database of allowed versions.
The only solution that doesn't rely on Nokia might be to tear apart their apk and use a rooted phone or an emulator to fake the properties it reads, so the app thinks it runs on a security patch that is supported.
But this approach requires people to send their IMEI to random people on the internet so there are additional risks.
ironman38102 said:
While I didn't unlock through official methods
Click to expand...
Click to collapse
I have heard someone else mention this as well. How did you unofficially unlock the bootloader?
THMSP said:
It is not related to models, but instead to the build ID's the phones run. (Nokia software is completely generic) Back when Nokia announced the unlock process and the october security patch dropped, phones on october patch started to
report the same issue the OP has encountered. One or two weeks later (after some public outrage ) the app started working again, likely because Nokia added the build ID of the october patch to their
database of allowed versions.
Click to expand...
Click to collapse
Perhaps downgrading and then trying the unlock app again might work?: https://forum.xda-developers.com/nokia-8/how-to/how-downgraded-pie-to-oreo-t3888178
frankoid said:
Perhaps downgrading and then trying the unlock app again might work?: https://forum.xda-developers.com/nokia-8/how-to/how-downgraded-pie-to-oreo-t3888178
Click to expand...
Click to collapse
To downgrade without an unlocked bootloader, you need a full OTA image that is configured accordingly, directly from Nokia. You boot into stock recovery and sideload that image, and in theory you should get an Oreo system.
However: The only full OTA downgrade I have done so far was using the revert-OTA from the Pie Beta Labs build. That gives you Oreo with November / December update and AFAIK those builds are not enabled.
The only other full OTA I know of happened it May, and it might be possible to sideload that one to get a system that you can then update and unlock on September / October patch.
But I never used this zip file so I don't know if stock recovery would accept and flash it if you sideload it.
If anyone here wants to try it out: You can download the file from my nokia cloud folder (https://bit.ly/nokia-nb1 - OTA Updates/NB1-488B-00WW-B01-update.zip).
I would be curious about the results. (Only oreo users should try this.. When you downgrade a Pie install it corrupts your userdata)
(I am intentionally not posting a detailed guide. If you can sideload this, you also know about the risks of messing with your phones software )
THMSP said:
To downgrade without an unlocked bootloader, you need a full OTA image that is configured accordingly, directly from Nokia. You boot into stock recovery and sideload that image, and in theory you should get an Oreo system.
However: The only full OTA downgrade I have done so far was using the revert-OTA from the Pie Beta Labs build. That gives you Oreo with November / December update and AFAIK those builds are not enabled.
The only other full OTA I know of happened it May, and it might be possible to sideload that one to get a system that you can then update and unlock on September / October patch.
But I never used this zip file so I don't know if stock recovery would accept and flash it if you sideload it.
If anyone here wants to try it out: You can download the file from my nokia cloud folder (https://bit.ly/nokia-nb1 - OTA Updates/NB1-488B-00WW-B01-update.zip).
I would be curious about the results. (Only oreo users should try this.. When you downgrade a Pie install it corrupts your userdata)
(I am intentionally not posting a detailed guide. If you can sideload this, you also know about the risks of messing with your phones software )
Click to expand...
Click to collapse
I'm your man. With nothing left to lose. o_o Will report back with the results ASAP.
I'm back and with bad news. The update process via the recovery menu seemed to run into an error where it complained about the timestamp on the update zip being too old, but for whatever reason, it proceeded anyway. OK, wiped the data (what data?) and did a factory reset, now it's booting up. I check the system information to be sure and it is 8.1.0. Installed the apk. Ran it. AND THEN...
Device not support.
I'm gonna try this with the zip mentioned in frankoid's post and do another update again, but honestly, it looks like Nokia just wants to be an asshole at this point.
!!!!!!!!!!!!!!! SUCCESS !!!!!!!!!!!!!!!!!!
This update zip is what you need: https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
It may be different for the TA-1012, but according to that earlier post, it does not seem to be the case. Nevertheless, just to be safe, here's the zip for the TA-1012: https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip (I don't have a TA-1012 so I wasn't able to test this particular zip.)
So basically, to make sure there's no problems, make sure in the Developer's options on the phone that OEM unlocking is enabled, then put your SD card into the phone. Plug the phone into your computer. Copy the update zip that you need somewhere onto the SD card. Disconnect the USB cable. Shut down the phone. Then, while holding down the Volume Up button, reconnect the USB cable. You should see a sad android with "No command" displayed. Now release the Volume Up button. Then hold down the power button and then JUST PRESS once on the Volume Up button. You should be at a recovery menu. Using the volume keys, scroll down to the 'Apply update on SD card' option and select it. Select the zip that you copied over to the SD card earlier and then let it install for a while. It will probably pop up with a 'timestamp too old' error, but just ignore this. The update will install anyway. Then once it's done, do a factory reset on the phone and then shut down. MAKE SURE THERE'S NO SIM CARD IN THE PHONE.
Now that's out of the way, just click through the first-time setup screens but DO NOT ENABLE WI-FI or any kind of internet connection. We don't want the phone to update itself back to Android 9. Now plug the phone in again. Copy the bootloaderunlocker apk from Nokia's website onto the phone. Install it. Put in the email address you want the unlock key emailed to. Then voila! You'll get the verification code. Put it into the form on Nokia's website and you'll be emailed an unlock.key file. From there, the site will tell you how to proceed.
Thank you apple boy for this topic.
100% troll.
S5Guy said:
*snip*
Click to expand...
Click to collapse
Great to hear that you got it working! My zip likely not worked because it just throws you back half a year (where official unlock didn't even exist) - you would have to update until you find a security patch that works.
But if November patch worked for you thats great! Since the May OTA worked for you that also means that people could choose to use the unofficial (paid) unlock method so Nokia doesn't know about whether they are locked or unlocked (warranty reasons).
Those OTA zips are model-agnostic btw. Whether they say TA-1004 or TA-1012 doesn't matter, they are the same. Only google makes that distinction on their servers, the software doesn't.
foxbatul said:
Thank you apple boy for this topic.
100% troll.
Click to expand...
Click to collapse
What's less useful...
A detailed set of instructions aimed at helping other forum members
... Or your post?
On mine that option is greyed out...
Thank you that was indeed very helpful. Will do the same now...
If I can find out WHY on my device that option is greyed out. How can I overcome this? Thanks
theviking33 said:
Thank you that was indeed very helpful. Will do the same now...
If I can find out WHY on my device that option is greyed out. How can I overcome this? Thanks
Click to expand...
Click to collapse
Did you touch the option in the past at all? If you did, it will be greyed out. As long as it's switched on though, it's fine. (I heard it will "ungrey" itself after a week, but there you go.)
No, did not do anything and it is off and greyed. I don't think it will magically ungrey itself. I did however download that unlock.apk and sent out email and pin, now waiting if a reply will come with the unlock code and procedure. Its been a few hours and no reply, so perhaps that's not working either.
theviking33 said:
No, did not do anything and it is off and greyed. I don't think it will magically ungrey itself. I did however download that unlock.apk and sent out email and pin, now waiting if a reply will come with the unlock code and procedure. Its been a few hours and no reply, so perhaps that's not working either.
Click to expand...
Click to collapse
I'm assuming you have a brand new TA-1004? And yeah, you should have gotten back a code long ago.
Try some of these options. https://www.theandroidsoul.com/how-to-fix-oem-unlock-greyed-out-or-oem-unlock-disabled-problem/
It could be though that it's just been flat out disabled due to region or whatever. If the solutions in the above link don't work, try downgrading back anyway and then using the apk as explained in an earlier post of mine.
It seems to be a case of "flat out disabled". I did a factory reset already and this setting won't change. I actually bought 2 of those phones and on both is the same.
How do I see or find out what region they are for?
And for the booloader, seems I have to go the old fashion way now...
---------- Post added at 11:38 ---------- Previous post was at 11:25 ----------
I have the TA-1004 DS which is International. So wouldn't understand why ist greyed.
ironman38102 said:
While I didn't unlock through official methods, it might be good to figure out what models of Nokia 8 are affected. Maybe a specific model is affected?
Click to expand...
Click to collapse
Mine has same problem and I've also been through similar online-forum attempts to help.
Model: TA-1012
Hardware version: 3.1
Patch level: 1 Jan 2019
Build No: 00WW_5_11A, 00WW_5_110_SP01
Downgrade your phobe and you can unlock, i have the same phone and this is what i did. I downloaded my phone firmware,i place the update file on my external sd card, i reset my phone to factory stock, i shut down my device an while shut down i press vol + and plug in my cable, i wait for the no comand screen and press power while holding vol up and get in recovery where i update from sd card and boom oreo
Related
I'm unable to use Android Pay - I'm not rooted, the boot loader is RELOCKED but when I try and add my card I get the dreaded "Google is unable to verify that your device or software running on it is Android compatible" error.
So, I was wondering, is it the fact that I did previous unlock my boot loader or something else stopping me.
BTW, Vendor: hw Country: eu, running C432B170.
Cheers.
No joy either
Same problem here. Imported mine and have done nothing but update to latest version of official roms (tried a couple of different ones today as well) and I get the same error. No rooting, purposely held off doing so so I could try Android Pay. SafetyNet Helper says the "CTS profile match" is false. My wild stab in the dark is that it is something to do it with it being identified as an international handset or handset from a non-Android pay supported country.
Had a web chat with an Android Pay helpdesk monkey and they had me reboot and reinstall a few times. They've also had me send some screenshots but I'm not holding out much hope for a useful reply.
captainkibble said:
CTS
Click to expand...
Click to collapse
CTS or CSC?
themissionimpossible said:
CTS or CSC?
Click to expand...
Click to collapse
CTS. Just double checked.
Maybe it's the same thing as CSC for Samsung phones.
In case, this might represent the target market for that phone, and that market might not yet be allowed to use Android Pay.
I'm using the single SIM version, NXT-L09, I managed to add my card but when I tried to pay for something in store I got the unable to verify.... message pop up on screen.
It also fails the CTS profile match in Safetynet helper
Android Pay worked for me today
I gave safetynet helper another try and this time it said my device passed. Re added my card to it and then used it on a London bus.
Using a Mate 8 NXT-L09C636B170
I too am able to use Android Pay. It started working for me last Thursday. While I had an open support ticket with the Android Pay help desk I periodically checked to see if it had started working. Eventually it did. I was able to add cards, SafetyNet Helper passed it's check and I was able to make payments. Result.
The same day, Android Pay help desk got back to me regarding my support ticket (there had been some backwards and forwards with logs, screenshots and the like). They concluded that Android Pay would not work because my phone was rooted. It isn't and has never has been. They had me send screenshots of multiple root checkers that displayed that the phone was not rooted *before* they came to this conclusion. I guess they just wanted the ticket closed and that was the most convenient excuse.
I've put it down to enough people reporting handsets not working that the Google added more phones to the "approved list" and help desks don't know what they are talking about.
My build number is NXT-L29C636B180
Hm.. Well this was interesting to read. Thanks for the updates saying that Android Pay does in fact (hopefully) work! I'm going to to get the L29 International dual SIM version soon so I was curious... I'll update when I get it and test it out
Mine still doesn't work - I then tried upgrading to B320 and I can't even add a card now whereas before I did eventually allow me to add a card. I'm cheesed off with it. Bootloader Locked no root and no Android Pay on a L29C432B320
gnasher666 said:
Mine still doesn't work - I then tried upgrading to B320 and I can't even add a card now whereas before I did eventually allow me to add a card. I'm cheesed off with it. Bootloader Locked no root and no Android Pay on a L29C432B320
Click to expand...
Click to collapse
Same here...
bh4714 said:
Same here...
Click to expand...
Click to collapse
I've downgraded to B170 and now have Android Pay working.
The high level process was:
All done via the help of SRK Tool http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
1) Unlock Boot Loader
2) Install Custom Recovery
3) Root Phone
4) Change to oeminfo and custom.bin eu (c432) - Even though I already was
5) Copy Full Update.app for C432B153 to dload folder
6) Flash stock recovery
7) Boot recovery and allow update to install
8) Factory Reset
9) Copy Update.app for C432B170 to dload folder
10) Boot recovery and allow update to install
I'm not sure how but following this process (although I've listed the steps from memory and not in front of my Laptop I did this on) I ended up with a Bootload LOCKED C432B170 and Android Pay works. I've not - nor will I update to and EMUI 4.1 version until they are released as OTA updates that my phone asks me to install
Android Pay was working fine on B103, I've upgraded to B321 via dload and now got pop up info that my device is incompatible with android pay. Any ideas?
Sent from Huawei Mate 8
Just one question
Hi,
Which recovery should I flash? the one for EMUI 4.1 or 4.0?
thanks
I believe Android Pay will not work with EMUI 4.1. I wish we were warned about this before we were allowed to flash to 320 or 321. No warning with the update links. Sucks!
Sent from my HUAWEI NXT-L29 using XDA-Developers mobile app
Hey Guys,
I have been googling for a while now and I seem to constantly come across conflicting and at times worrying posts which has very much left me stuck right were I am. I just recently purchased a Mate 9 in the hope I would be able to, like all my previous mobiles install a custom rom and tweak it to my specific needs. This however hasn't been the case.
Firmware:
System 8.0.0.046
Dataver MHA-L09 8.0.0.371(C34)
Things that have been tried:
1. No I didn't get a boot unlocker code from the Huawei
2. Yes I have contacted them personally via two different channels and both returned with a we are happy to give it to you, that's not an issue, but this code doesn't exist anymore.
3. DC-Unlock tool didn't detect my mobile in manufacture mode, in which I found another forum post stating to use HCU 3.22 client instead which worked to the point of detecting my mobile, but told me that the current security patch not supported.
4. Contacting DC-Unlock, told me there is no ETA on getting this patch level to work
5. I have read people downgrading to a previous version, unlocking and then installed the custom rom via HiSuite, this doesn't give me that option.
6. I have read people downgrading to a previous version, unlocking and then installed the custom rom via firmware finder.
6.1 Issues with this is that I seen someone claim to upgrade to version 8.0.0.3.75, which is higher then mine, which enabled the rollback feature, is this correct?
6.2 Issues with this is that I have read that gpu turbo has been enabled and many have warned that rolling back to a pre-gpu turbo enabled firmware will brick you mobile and would result in a motherboard needing to be replaced for nearly the cost of the mobile itself.
I am tempted to try another site which I can't remember the name of, which if you pay considerably more then DC-Unlock. at least if they can't get the code, would be refunded. but I think that site is down now as I feel they were playing on people who didn't know how to have done it for free via the Huawei site back in 2018.
So I want to know is there a safe way to unlock my bootloader I think my only option is option 6 but just want more details from others who have done it this way before, or have I pretty much exhausted all my option and just bite the bullet and upgrade to 9.0.1.187 and possibly further through the OTA update process and just enjoy the mobile for what it is and it's limitations?
Thanks again.
You can try the spoofing method here on xda I updated from 8 to 9 with that, as long as firmware finder says your imei is approved
mucski said:
You can try the spoofing method here on xda I updated from 8 to 9 with that, as long as firmware finder says your imei is approved
Click to expand...
Click to collapse
Thanks for that, I can already upgrade to 9, my system updates app is just waiting for me to accept. The issue is that I don't want to go forward. I really want to go backwards, so I can unlock my bootloader first. I'm already at the stage where I have tried most if not all the safe ways to unlocking my bootloader, but with my currently installed android version I can't. The only way forward for me it seems is the firmware finder app and SD force flash back to EMUI 5 aka Android 7 to use DC-Unlocker to unlock it first, then that gives me the freedom of installing the official Android 9 or openkirin.
I just worried as some people have stated that if you attempt a downgrade after a specific point, something about GPU turbo being enabled in later firmwares, which will brick your mobile.
I just want to hear from others who have done this successfully or if it's not possible in my case.
Hi i found official stock rom
mirrors.lolinet.com/firmware/moto/troika/official/RETAIL/TROIKA_RETAIL_10_QSB30.62-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Will this work on the reteu devices (being from a different channel)?
FelixNevorsky said:
Hi i found official stock rom
mirrors.lolinet.com/firmware/moto/troika/official/RETAIL/TROIKA_RETAIL_10_QSB30.62-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
What Does The Letter QSB Mean?
In The Previous Rom Are PSB Or PSBS
takoa said:
What Does The Letter QSB Mean?
In The Previous Rom Are PSB Or PSBS
Click to expand...
Click to collapse
My guess is that QSB is for Android 10 (it was called Q for some time). And PSB is 9.0 (aka Pie)
I mean the letters sbs and sb. thanks
takoa said:
I mean the letters sbs and sb. thanks
Click to expand...
Click to collapse
ummmm......Stable build.....maybe
Was Anyone able to root this version?
Wintershade said:
Will this work on the reteu devices (being from a different channel)?
Click to expand...
Click to collapse
Yes, it should. It's been already tested here on the forum with pretty good results. So yeah, I'd say it will. But if you're not in a hurry, maybe you can wait for a bit longer to get the official build for RETEU.
Channel Signification Firmware
Is a list exist for channel signification for https://mirrors.lolinet.com/firmware/moto/troika/official/
or a way to knows the signication ?
RETEU = Europe
RETUS = USA
RETCA = Canada
RETRU = ???
etc ...
Compatibility Variant / Firmware
Is exists a thumb rule for compatibility firmwares in between XT2013-1, XT2013-2, XT2013-3, XT2013-4.
Actually, I have a XT2013-4 device and I would like flash another firmware variant.
Thanks
RETRU = Russia
RETBR = Brazil
RETAR = Argentina
etc...
Well, I don't think there is any compatibility table or something... At least not an official one. )
Also, I would not try a "-1" firmware for example, on a "-4" device. If I'm not mistaken, one of them (probably the -4 variant...?) is Single SIM. The other ones I think are Dual SIM models (XT2013-2 surely is). So I don't think that's gonna work.
The only compatibility I can confirm is a XT2013-2 device running the RETAIL version without major issues (the signal seems to be lower for both carrier and wifi, for some reason, but other than that, everything works). Everything else is at your own risk. But again, I would not recommend flashing a -1/-2/-3 ROM onto your -4 device. Unless someone else did it and it went ok.
arsradu said:
RETRU = Russia
RETBR = Brazil
RETAR = Argentina
etc...
Well, I don't think there is any compatibility table or something... At least not an official one. )
Also, I would not try a "-1" firmware for example, on a "-4" device. If I'm not mistaken, one of them (probably the -4 variant...?) is Single SIM. The other ones I think are Dual SIM models (XT2013-2 surely is). So I don't think that's gonna work.
The only compatibility I can confirm is a XT2013-2 device running the RETAIL version without major issues (the signal seems to be lower for both carrier and wifi, for some reason, but other than that, everything works). Everything else is at your own risk. But again, I would not recommend flashing a -1/-2/-3 ROM onto your -4 device. Unless someone else did it and it went ok.
Click to expand...
Click to collapse
Thanks for your answer, I have a XT2013-4 and I can confirm that's is a Single SIM.
For info, on my XT2013-4 I tried two différents android 10 firmware made for XT2013-2 and they both runs very smooth but time will tells if there's any issues
- TROIKA_RETAIL_10_QSBS30.62-17-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
- XT2013-2_TROIKA_RETRU_10_QSB30.62-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
/Regards
arsradu said:
RETRU = Russia
RETBR = Brazil
RETAR = Argentina
etc...
Well, I don't think there is any compatibility table or something... At least not an official one. )
Also, I would not try a "-1" firmware for example, on a "-4" device. If I'm not mistaken, one of them (probably the -4 variant...?) is Single SIM. The other ones I think are Dual SIM models (XT2013-2 surely is). So I don't think that's gonna work.
The only compatibility I can confirm is a XT2013-2 device running the RETAIL version without major issues (the signal seems to be lower for both carrier and wifi, for some reason, but other than that, everything works). Everything else is at your own risk. But again, I would not recommend flashing a -1/-2/-3 ROM onto your -4 device. Unless someone else did it and it went ok.
Click to expand...
Click to collapse
There's an interesting channel listing on a XDA TREAD "Identify Software Channel"
https://forum.xda-developers.com/moto-z-play/help/identify-software-channel-t3555285
/Thanks
Gypsy said:
There's an interesting channel listing on a XDA TREAD "Identify Software Channel"
https://forum.xda-developers.com/moto-z-play/help/identify-software-channel-t3555285
/Thanks
Click to expand...
Click to collapse
that is very good to know. thank you!
Gypsy said:
Thanks for your answer, I have a XT2013-4 and I can confirm that's is a Single SIM.
For info, on my XT2013-4 I tried two différents android 10 firmware made for XT2013-2 and they both runs very smooth but time will tells if there's any issues
- TROIKA_RETAIL_10_QSBS30.62-17-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
- XT2013-2_TROIKA_RETRU_10_QSB30.62-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
/Regards
Click to expand...
Click to collapse
Hi..
I have one action with xt2013-4 too.. and wait update to android 10 for long time.. ?
Will you give me an information if my phone model may get OTA android 10? If yes when? If you know.. ?
Otherwise, if I want to flash android 10 to my device, will you give me a guidance how to flash with another ROM model TROIKA, but it compatible with my device like you information before..
Thanks for the feedback
?
zaqiezsbelelzsinski said:
Hi..
I have one action with xt2013-4 too.. and wait update to android 10 for long time..
Will you give me an information if my phone model may get OTA android 10? If yes when? If you know..
Otherwise, if I want to flash android 10 to my device, will you give me a guidance how to flash with another ROM model TROIKA, but it compatible with my device like you information before..
Thanks for the feedback
?
Click to expand...
Click to collapse
Nobody knows when. At least you won't find this information publicly available. Since XT2013-4 seems to be the only remaining model to update...I guess it shouldn't be that much longer.
If you can wait, I would advise you to wait. Flashing is not that difficult. But it comes with some risks, and in case you need to unlock your bootloader for whatever reason, it voids your warranty. So, while not impossible, it would be easier to wait, if you can. I know it's not easy! )
Basic instructions (in case you really wanna do this):
1. get the script attached to THIS post specifically (you're gonna need adb and fastboot files in the same folder as your ROM). You can also type the commands manually, but why bother when you can use a script to do it automatically for you? Also, make sure you choose Android 10! The commands are different for Android 10 compared to Android 9!
2. download the ROM from here (if you want to use the RETAIL channel).
3. unzip it
4. add adb and fastboot into the same folder, along with the script
5. connect the phone to your PC and enable USB Debugging, as well as the fingerprinting pop-up that follows it (also check the box for Always Allow)
6. boot into bootloader/fastboot (from a cold start, press Power + Volume Down).
7. flash with fastboot (using the script above)
8. done.
/!\ MAKE SURE YOU DON'T UPDATE YOUR SECURITY PATCH! THE SECURITY PATCH VERSION YOU'RE CURRENTLY USING AND THE ONE YOU'RE ABOUT TO FLASH NEED TO MATCH, in order to have the least amount of troubles!
Otherwise you might have some issues if you're trying to go back. I know it's tempting to just go and flash the newest version. BUT DON'T!
Again, this is just so you know in a few steps, how it's done. I would still advise you to wait, if you can. So you don't flash the wrong thing, or brick your phone, or stuff like that.
arsradu said:
Nobody knows when. At least you won't find this information publicly available. Since XT2013-4 seems to be the only remaining model to update...I guess it shouldn't be that much longer.
If you can wait, I would advise you to wait. Flashing is not that difficult. But it comes with some risks, and in case you need to unlock your bootloader for whatever reason, it voids your warranty. So, while not impossible, it would be easier to wait, if you can. I know it's not easy! )
Click to expand...
Click to collapse
arsradu said:
@zaqiezsbelelzsinski
I can't and more to @arsradu's answers, but just in case you decide to unlock your bootloader for whatever reason, it voids your warranty., there's the link:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Good luck, if you have any difficulty, please ask!
Click to expand...
Click to collapse
Basic instructions (in case you really wanna do this):
1. get the script attached to THIS post specifically (you're gonna need adb and fastboot files in the same folder as your ROM). You can also type the commands manually, but why bother when you can use a script to do it automatically for you? Also, make sure you choose Android 10! The commands are different for Android 10 compared to Android 9!
2. download the ROM from here (if you want to use the RETAIL channel).
3. unzip it
4. add adb and fastboot into the same folder, along with the script
5. connect the phone to your PC and enable USB Debugging, as well as the fingerprinting pop-up that follows it (also check the box for Always Allow)
6. boot into bootloader/fastboot (from a cold start, press Power + Volume Down).
7. flash with fastboot (using the script above)
8. done.
/!\ MAKE SURE YOU DON'T UPDATE YOUR SECURITY PATCH! THE SECURITY PATCH VERSION YOU'RE CURRENTLY USING AND THE ONE YOU'RE ABOUT TO FLASH NEED TO MATCH, in order to have the least amount of troubles!
Otherwise you might have some issues if you're trying to go back. I know it's tempting to just go and flash the newest version. BUT DON'T!
Again, this is just so you know in a few steps, how it's done. I would still advise you to wait, if you can. So you don't flash the wrong thing, or brick your phone, or stuff like that.[/QUOTE]
One thing I forgot to mention: simply requesting the bootloader unlock code will void your warranty. You don't even need to use it. Once you requested it, it's done.
Now, if you're super careful with that security patch I mentioned above, you might not need to request it in the first place, since you might not need to unlock your bootloader in the first place. Cool, huh?
Unfortunately I don't have so much experience with this. And it's not like I have a bunch of Moto One Actions I can test with. I only have my own. ) But in theory, if you don't update/downgrade your security patch, if you only flash ROMs with the exact same security patch, you could (again, this is just a theory, based on my own experience) go from Android 9 to 10 and back, without unlocking the bootloader. Because it looks like it's not the Android downgrade that's causing the issues. It's the security patch downgrade that forces you to unlock the bootloader.
And I wish I had this piece of knowledge before I requested my unlock code. )) But I didn't. So I'm just happy it wasn't for nothing and I learned a lot in the process.
arsradu said:
Nobody knows when. At least you won't find this information publicly available. Since XT2013-4 seems to be the only remaining model to update...I guess it shouldn't be that much longer.
If you can wait, I would advise you to wait. Flashing is not that difficult. But it comes with some risks, and in case you need to unlock your bootloader for whatever reason, it voids your warranty. So, while not impossible, it would be easier to wait, if you can. I know it's not easy! )
Basic instructions (in case you really wanna do this):
1. get the script attached to THIS post specifically (you're gonna need adb and fastboot files in the same folder as your ROM). You can also type the commands manually, but why bother when you can use a script to do it automatically for you? Also, make sure you choose Android 10! The commands are different for Android 10 compared to Android 9!
2. download the ROM from here (if you want to use the RETAIL channel).
3. unzip it
4. add adb and fastboot into the same folder, along with the script
5. connect the phone to your PC and enable USB Debugging, as well as the fingerprinting pop-up that follows it (also check the box for Always Allow)
6. boot into bootloader/fastboot (from a cold start, press Power + Volume Down).
7. flash with fastboot (using the script above)
8. done.
/!\ MAKE SURE YOU DON'T UPDATE YOUR SECURITY PATCH! THE SECURITY PATCH VERSION YOU'RE CURRENTLY USING AND THE ONE YOU'RE ABOUT TO FLASH NEED TO MATCH, in order to have the least amount of troubles!
Otherwise you might have some issues if you're trying to go back. I know it's tempting to just go and flash the newest version. BUT DON'T!
Again, this is just so you know in a few steps, how it's done. I would still advise you to wait, if you can. So you don't flash the wrong thing, or brick your phone, or stuff like that.
Click to expand...
Click to collapse
Thank you for the feedback
Yes, I understand about the risk. Many years ago I always flashing my device (Nexus 5) while it was release update, but that was then ?. Now, Maybe I will be waiting till my device get update to android 10.
The problem is, there is no valid information from Motorola especially TROIKA XT2013-4 about update to android 10.
Thanks for your advice about flashing ROM..
Cheers ???
You could try to contact your local Motorola Support team. I don't think they will give you an actual ETA. But maybe they can tell you wether or not there will be an update to Android 10 for this particular model (XT2013-4). I think there should be. I see no reason why this particular model would be an exception. But you could double check that. Just in case.
Logic would suggest that there should be one soon. XT2013-1 and XT2013-2 already got the update. So it would make sense for the "-4" model to follow.
Sent from my motorola one action using Tapatalk
arsradu said:
One thing I forgot to mention: simply requesting the bootloader unlock code will void your warranty. You don't even need to use it. Once you requested it, it's done.
Now, if you're super careful with that security patch I mentioned above, you might not need to request it in the first place, since you might not need to unlock your bootloader in the first place. Cool, huh?
Unfortunately I don't have so much experience with this. And it's not like I have a bunch of Moto One Actions I can test with. I only have my own. ) But in theory, if you don't update/downgrade your security patch, if you only flash ROMs with the exact same security patch, you could (again, this is just a theory, based on my own experience) go from Android 9 to 10 and back, without unlocking the bootloader. Because it looks like it's not the Android downgrade that's causing the issues. It's the security patch downgrade that forces you to unlock the bootloader.
And I wish I had this piece of knowledge before I requested my unlock code. )) But I didn't. So I'm just happy it wasn't for nothing and I learned a lot in the process.
Click to expand...
Click to collapse
@arsradu
I notice you have experience with security patches, tanks you to had shared!
IF I REALLY NEED TO DOWNGRADE MY SECURITY PATCH ! EVEN with all amounts of troubles, IS THERE A WAY doing it?
Thanks
Hi!
I come from the Galaxy S series (S4, S5, S7) phones and I m considering of buying a Google Pixel 3
I can find many decent options, all of which are carrier unlocked
My concern with the Pixel 3 is whether I ll be able to install Android vanilla (without any carrier-related bloatware)
For all of my Samsung's so far, I could easily pick the retail ROM (well not exactly 'vanilla'!) from sammobile and load it with Odin (without breaking the knox)
Can I do something similar in the Pixel 3 or are there any security mechanisms to prevent me? (I m talking about installing original ROM - not custom..)
Bonus question - does any of you know if the Pixel 3 from Verizon and US Cellular have branding [carrier logo(s)] on the device?
Thank you in advance!
Well, you will certainly avoid the Samsung bloatwear. I have a P3 from Google and got my son's P3 through T-mobile. It did not have any additional T-mobile bloat on it, but I don't know about the big V.
Note10.1Dude said:
Well, you will certainly avoid the Samsung bloatwear. I have a P3 from Google and got my son's P3 through T-mobile. It did not have any additional T-mobile bloat on it, but I don't know about the big V.
Click to expand...
Click to collapse
I can find it via Verizon and US Cellular - hopefully none of which have put logos on it..
I have one more - rather embarassing question: do you have to use a Google account in order to use the Pixel 3? For several other Android phones that I know of - it's optional. You can still skip this step and use the phone without having to tie the phone with Google. But can you do that on the P3?
Any more hints on that and my ROM-related queries would be really helpful! Thanks
jstoner said:
I can find it via Verizon and US Cellular - hopefully none of which have put logos on it..
I have one more - rather embarassing question: do you have to use a Google account in order to use the Pixel 3? For several other Android phones that I know of - it's optional. You can still skip this step and use the phone without having to tie the phone with Google. But can you do that on the P3?
Any more hints on that and my ROM-related queries would be really helpful! Thanks
Click to expand...
Click to collapse
Verizon branded Pixel 3s have locked bootloaders, which prevent rooting or custom ROMs (vanilla AOSP would be a custom ROM). According to the flashing instructions at https://developers.google.com/android/images, you also need to unlock the bootloader to flash a google factory image.
I'm not sure if you can skip the google account. If you really want to avoid google services, my recommendation would be to install LineageOS, with no gapps.
dcarvil said:
Verizon branded Pixel 3s have locked bootloaders, which prevent rooting or custom ROMs (vanilla AOSP would be a custom ROM). According to the flashing instructions at https://developers.google.com/android/images, you also need to unlock the bootloader to flash a google factory image.
I'm not sure if you can skip the google account. If you really want to avoid google services, my recommendation would be to install LineageOS, with no gapps.
Click to expand...
Click to collapse
Hmm...if the 3s has that, then the 3 will also have it :/
But I m confused...would I be able to unlock the bootloader?
I can see from this page: https://developers.google.com/android/images#blueline that 'blueline' is that vanilla AOSP version that corresponds to the P3 (right?)
The G account issue is less important. I just don't like 'syncing' stuff (accounts, photos etc). Worse case scenario, I ll create an empty profile, just for the logon
jstoner said:
Hmm...if the 3s has that, then the 3 will also have it :/
But I m confused...would I be able to unlock the bootloader?
I can see from this page: https://developers.google.com/android/images#blueline that 'blueline' is that vanilla AOSP version that corresponds to the P3 (right?)
The G account issue is less important. I just don't like 'syncing' stuff (accounts, photos etc). Worse case scenario, I ll create an empty profile, just for the logon
Click to expand...
Click to collapse
3s is not a model, it is the plural of 3. A Verizon Pixel 3 usually cannot be boot loader unlocked, but if you search this forum, you will find a few special cases where it has been done. One such case is at https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
Vanilla AOSP generall refers to a ROM without any google services. See https://android.stackexchange.com/questions/53171/what-exactly-is-in-aosp for more info. Blueline is the Pixel 3 factory image, which has all the google services. It does not have any added carrier bloatware, but I wouldn't call it a vanilla AOSP.
You can turn off all the syncing stuff, and you may be able to skip the google account part. I just can't definitely say you can skip the google account because I have not tried it.
Another consideration with a locked bootloader is the end support date. Google support for the Pixel 3 ends in October, 4 months from now. There will be no security updates from Google after October. If you have an unlocked bootloader, you can switch to LineageOS and continue to receive security updates. That is what I plan to do.
dcarvil said:
3s is not a model, it is the plural of 3. A Verizon Pixel 3 usually cannot be boot loader unlocked, but if you search this forum, you will find a few special cases where it has been done. One such case is at https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
Vanilla AOSP generall refers to a ROM without any google services. See https://android.stackexchange.com/questions/53171/what-exactly-is-in-aosp for more info. Blueline is the Pixel 3 factory image, which has all the google services. It does not have any added carrier bloatware, but I wouldn't call it a vanilla AOSP.
You can turn off all the syncing stuff, and you may be able to skip the google account part. I just can't definitely say you can skip the google account because I have not tried it.
Another consideration with a locked bootloader is the end support date. Google support for the Pixel 3 ends in October, 4 months from now. There will be no security updates from Google after October. If you have an unlocked bootloader, you can switch to LineageOS and continue to receive security updates. That is what I plan to do.
Click to expand...
Click to collapse
Clear!
I ll check on the resources you ve listed here
If the V-branded P3 is troublesome as it sounds, perhaps I should just go for the US Cellular carrier option. Bootloader may also be locked (but we know for sure that the V is..)
Interestingly, the US Cellular P3 is unlocked to all GSM carriers except Verizon, Boost, Virgin Mobile and Sprint
Is the carrier lock specified in the bootloader?
Btw, thanks for all the help!
jstoner said:
Clear!
I ll check on the resources you ve listed here
If the V-branded P3 is troublesome as it sounds, perhaps I should just go for the US Cellular carrier option. Bootloader may also be locked (but we know for sure that the V is..)
Interestingly, the US Cellular P3 is unlocked to all GSM carriers except Verizon, Boost, Virgin Mobile and Sprint
Is the carrier lock specified in the bootloader?
Btw, thanks for all the help!
Click to expand...
Click to collapse
SIM (carrier) unlock and bootloader unlock are separate, and not related. I have no idea if US Cellular is bootloader unlocked. Google sold a global model, which is the bootloader unlocked version, and the one I have. The IMEI/MEID number of the global variant begins with 990012 (don't know how many digits are significant). If I was buying it, I'd ask the seller to confirm it was bootloader unlocked.
Glad I could help.
dcarvil said:
SIM (carrier) unlock and bootloader unlock are separate, and not related. I have no idea if US Cellular is bootloader unlocked. Google sold a global model, which is the bootloader unlocked version, and the one I have. The IMEI/MEID number of the global variant begins with 990012 (don't know how many digits are significant). If I was buying it, I'd ask the seller to confirm it was bootloader unlocked.
Glad I could help.
Click to expand...
Click to collapse
The two P3 options I m considering (Verizon + US Cellular), both are sealed in their original box. According to that post, if the P3 hasn't ever being turned on, which is probably then when bootloader becomes locked
So I wonder if there is a SIM that comes with the phone already and that I have to remove that prior booting the phone. Not sure what he means with "VZW SIM". Is it a different type of SIM e.g. an eSIM??
I know for fact that these phones are CDMA-locked and only GSM is unlocked (but that's what I need anyways)
Does anyone here have any experience from an US Cellular P3 - is the bootloader locked? (the retailer of the phone doesn't seem to know much on such details..)
jstoner said:
The two P3 options I m considering (Verizon + US Cellular), both are sealed in their original box. According to that post, if the P3 hasn't ever being turned on, which is probably then when bootloader becomes locked
So I wonder if there is a SIM that comes with the phone already and that I have to remove that prior booting the phone. Not sure what he means with "VZW SIM". Is it a different type of SIM e.g. an eSIM??
I know for fact that these phones are CDMA-locked and only GSM is unlocked (but that's what I need anyways)
Does anyone here have any experience from an US Cellular P3 - is the bootloader locked? (the retailer of the phone doesn't seem to know much on such details..)
Click to expand...
Click to collapse
VZW SIM is just a Verizon SIM. It is probably the standard SIM card, not an eSIM. I would remove the SIM prior to booting, just to be safe. According to one of those posts, WiFi had to be connected before they could unlock the bootloader.
dcarvil said:
VZW SIM is just a Verizon SIM. It is probably the standard SIM card, not an eSIM. I would remove the SIM prior to booting, just to be safe. According to one of those posts, WiFi had to be connected before they could unlock the bootloader.
Click to expand...
Click to collapse
I ll find out soon, I ve ordered the P3 (US cellular stock)
Seller claims that it is sealed in original box. If that's really the case, then the carrier can't have put a SIM into it, right? But what about an eSIM? If they have the eSIM pre-programmed, then I can't possibly avoid booting the phone with it..
jstoner said:
I ll find out soon, I ve ordered the P3 (US cellular stock)
Seller claims that it is sealed in original box. If that's really the case, then the carrier can't have put a SIM into it, right? But what about an eSIM? If they have the eSIM pre-programmed, then I can't possibly avoid booting the phone with it..
Click to expand...
Click to collapse
Hmmm I think the way it works is that when the phone is produced, for a specific carrier, and the carrier wants it to have a sim, it's put in at the factory. So, I think, sealed with a sim in it, possible.
I don't think us cellular uses e-sims. Double check that but it doesn't look like one of the carriers that's capable of e-sims.
cheers, good luck. I have a vzw coming today, hoping it's new and can unlock as others have... we'll know soon.
Good news! Just got the phone and ... I ve managed to unlock the bootloader!
Exactly same case as described here. No SIM inserted, connected to WIFI, and in Dev Options, turned OEM unlocking to ON!
Then, on the instructions (link by opensense), I ve used adb and the bootloader is now unlocked! I m really chuffed about it
(btw the US Cellular supplied SIM was attached on the box (outside) with a sticker. Box was sealed.
Now, all is left is for me to pick that 'cleaner' Android option I always wanted!
But which one should it be? It's currently running blueline MP1.0(ROW)
Is there any clearer (official) Android ROM that I should switch to instead?
From G services, I would like to keep the Playstore and Maps...
jstoner said:
Good news! Just got the phone and ... I ve managed to unlock the bootloader!
Exactly same case as described here. No SIM inserted, connected to WIFI, and in Dev Options, turned OEM unlocking to ON!
Then, on the instructions (link by opensense), I ve used adb and the bootloader is now unlocked! I m really chuffed about it
(btw the US Cellular supplied SIM was attached on the box (outside) with a sticker. Box was sealed.
Now, all is left is for me to pick that 'cleaner' Android option I always wanted!
But which one should it be? It's currently running blueline MP1.0(ROW)
Is there any clearer (official) Android ROM that I should switch to instead?
From G services, I would like to keep the Playstore and Maps...
Click to expand...
Click to collapse
Congratulations. You'll have to define what you mean by the term "cleaner (official)" ROM. Blueline is the only official Google ROM for the Pixel 3. Anything else will be a custom ROM. I have no experience with any of the Pixel custom ROMs, so can't offer any advice on those.
You can disable most of the unwanted Google services in the blueline ROM. I'd recommend keeping the backup service, though.
Blueline MP1.0(ROW) is not a version listed at https://developers.google.com/android/images#blueline Go to Settings, About Phone, and tap Android Version. Check the "Android security update" date. Latest is June 5, 2021. I suspect yours is quite old.
If you want to update to the current blueline version, you have 2 options, OTA or flash a new factory image.
For OTA, go to Settings, System, System update, and follow instructions.
To flash a new factory image, follow the instructions at the link above. To prevent wiping your data when flashing, edit the flash-all.bat or flash-all.sh file, and remove the "-w" from the last line.
I you intend to change ROM's, I wouldn't bother updating.
Good luck.
dcarvil said:
Congratulations. You'll have to define what you mean by the term "cleaner (official)" ROM. Blueline is the only official Google ROM for the Pixel 3. Anything else will be a custom ROM. I have no experience with any of the Pixel custom ROMs, so can't offer any advice on those.
You can disable most of the unwanted Google services in the blueline ROM. I'd recommend keeping the backup service, though.
Blueline MP1.0(ROW) is not a version listed at https://developers.google.com/android/images#blueline Go to Settings, About Phone, and tap Android Version. Check the "Android security update" date. Latest is June 5, 2021. I suspect yours is quite old.
If you want to update to the current blueline version, you have 2 options, OTA or flash a new factory image.
For OTA, go to Settings, System, System update, and follow instructions.
To flash a new factory image, follow the instructions at the link above. To prevent wiping your data when flashing, edit the flash-all.bat or flash-all.sh file, and remove the "-w" from the last line.
I you intend to change ROM's, I wouldn't bother updating.
Good luck.
Click to expand...
Click to collapse
I think I ll probably stick with the official one then. My current is PQ1A.181105.017.A1 (which is very old as you guessed)
Which means I can jump to Android 10 or 11. From my experience, latest isn't always the best so I might have to keep reading, see if I should jump to a latest build of 10 instead. My emphasis is on stability/security - not new features...
And I want to ensure that the camera is at its best
jstoner said:
I think I ll probably stick with the official one then. My current is PQ1A.181105.017.A1 (which is very old as you guessed)
Which means I can jump to Android 10 or 11. From my experience, latest isn't always the best so I might have to keep reading, see if I should jump to a latest build of 10 instead. My emphasis is on stability/security - not new features...
And I want to ensure that the camera is at its best
Click to expand...
Click to collapse
If security is a concern, you'll want to go to Android 11. 10 has not been updated since August 2020, when Android 11 came out. Also, I believe there have been camera improvements since August 2020, which would not be in the latest Android 10 build.
I have not seen any reports of stability problems with the June 2021 Android 11 update, which has the latest security patches.
I don't know if you can do an OTA update to Android 11 from Android 9. You might have to go from 9 to 10 to 11. You can flash the Android 11 image without going to 10 first.
I intend to do via flashing (whichever version I decide in the end). Not a fan of OTA
Hello: I'm using the guide clintongsan made to root a usa moto one 5g ace android 10 purchased in april 2022 from a T-mobile store here in the south on the east side of the mississippi river.
My build number is QZKS30.Q4-40-95-9 The last build number on this link
( https://mirrors.lolinet.com/firmware/moto/kiev/official/TMO/ ) is QZKS30.Q4-40-95-6 with a
date of 02/11/2022. Will that work for me since I have 95-9 and that one is 95-6 There is a grayed out statement that there are 68 more subfolders but I don't know how to access it to see if my build is there. Also on the Motorola website for unlocking the bootloader, Get your device ID, there are examples for compacting the lines of code into a long string. The examples are for Windows and Mac. I'm using a Linux laptop and no example exists. The Moto site gives a link to download SDK tools. Is there a site where I can download the minimum tools required? Probably more questions to follow for sure. Thank you
vansteering said:
Hello: I'm using the guide clintongsan made to root a usa moto one 5g ace android 10 purchased in april 2022 from a T-mobile store here in the south on the east side of the mississippi river.
My build number is QZKS30.Q4-40-95-9 The last build number on this link
( https://mirrors.lolinet.com/firmware/moto/kiev/official/TMO/ ) is QZKS30.Q4-40-95-6 with a
date of 02/11/2022. Will that work for me since I have 95-9 and that one is 95-6 There is a grayed out statement that there are 68 more subfolders but I don't know how to access it to see if my build is there. Also on the Motorola website for unlocking the bootloader, Get your device ID, there are examples for compacting the lines of code into a long string. The examples are for Windows and Mac. I'm using a Linux laptop and no example exists. The Moto site gives a link to download SDK tools. Is there a site where I can download the minimum tools required? Probably more questions to follow for sure. Thank you
Click to expand...
Click to collapse
Honestly I've been trying to figure out the best way to go about this as well. My fiance is interested in having her phone rooted. I'm just trying to figure a well to where i can just access the boot image off the phone somehow so i can patch it using magisk. well obviously backing up the original image first, but i've heard twrp doesn't work and i tried using QFIL to see if i can access it but i don't think it has EDL. If you figured out a way to do it without flashing a older update to the phone. Please let me know. I'll do the same after I look into it a bit more. I feel like i'm just over complicating somehow lol I have a tendency of doing that.
vansteering said:
Hello: I'm using the guide clintongsan made to root a usa moto one 5g ace android 10 purchased in april 2022 from a T-mobile store here in the south on the east side of the mississippi river.
My build number is QZKS30.Q4-40-95-9 The last build number on this link
( https://mirrors.lolinet.com/firmware/moto/kiev/official/TMO/ ) is QZKS30.Q4-40-95-6 with a
date of 02/11/2022. Will that work for me since I have 95-9 and that one is 95-6 There is a grayed out statement that there are 68 more subfolders but I don't know how to access it to see if my build is there. Also on the Motorola website for unlocking the bootloader, Get your device ID, there are examples for compacting the lines of code into a long string. The examples are for Windows and Mac. I'm using a Linux laptop and no example exists. The Moto site gives a link to download SDK tools. Is there a site where I can download the minimum tools required? Probably more questions to follow for sure. Thank you
Click to expand...
Click to collapse
Just tried this and had no issues at all, Hope this helps
[RECOVERY][UNOFFICIAL] TWRP 3.5.2_10 for Moto G 5G (kiev)
DISCLAIMER: I'm not responsible if you brick or damage your phone in any way by using this recovery. It is always advisable to fully backup your phone before playing around with recoveries, custom roms and similar stuff. What has been tested and...
forum.xda-developers.com
InvisibleAOD said:
Just tried this and had no issues at all, Hope this helps
Click to expand...
Click to collapse
On Build number 95-9? Or a previous version? I'm asking because I couldn't even get the bootloader unlocked on a 95-9 phone (unlock "failed" after getting the code from Moto). I'm still trying to get an answer as to whether if the newest OTA is a problem.
vansteering said:
. . . I'm using a Linux laptop and no example exists. The Moto site gives a link to download SDK tools. Is there a site where I can download the minimum tools required? Probably more questions to follow for sure. Thank you
Click to expand...
Click to collapse
Is this what you're asking for?
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
As for 40-95-9 firmware, a sure way to get that firmware is Moto/Lenovo's "Rescue and Smart Assistant", aka "LMSA" (search, should be easy to find). Use the Rescue option and stop (EDIT/ADD: let the download finish), go to the folder where it was downloaded (make sure to get the download link shown in the utility) and find the firmware in the ".../ROMfiles" subfolder I think it is. That's the full firmware including boot.img. I used that subfolder to reflash the entire 95-9 firmware. EDIT/ADD: But this assumes Rescue and Smart Assistant on Windows, NOT Linux. I don't know if there is a Linux version for that, sorry. {--Or do you have a Windows emulator in your Linux that might solve this particular issue?--)
I DO NOT KNOW -- yet -- if 95-9 is rootable or even unlockable. Unlock failed for me on a 95-9 phone . . . although I did get an Unlock Code from Moto (on a Windows PC).
So this is a question back at you: HAVE YOU MANAGED TO UNLOCK THE BOOTLOADER on your 95-9 phone?
Moondroid said:
On Build number 95-9? Or a previous version? I'm asking because I couldn't even get the bootloader unlocked on a 95-9 phone (unlock "failed" after getting the code from Moto). I'm still trying to get an answer as to whether if the newest OTA is a problem.
Click to expand...
Click to collapse
Yeah it was on 95-9, just make sure to read through the thread cause I kind of messed up in the process but once you flash twrp and boot into it, flash the kiev file and magisk. I had to keep reading. I flashed to both partition a and b.
InvisibleAOD said:
Yeah it was on 95-9, just make sure to read through the thread cause I kind of messed up in the process . . .
Click to expand...
Click to collapse
I should've been more specific with my question, sorry. . . . Did you actually unlock your bootloader on 95-9, or was it unlocked prior to that OTA and then you ran the root process on 95-9?
@vansteering , I don't mean to hijack your thread.
Moondroid said:
I should've been more specific with my question, sorry. . . . Did you actually unlock your bootloader on 95-9, or was it unlocked prior to that OTA and then you ran the root process on 95-9?
@vansteering , I don't mean to hijack your thread.
Click to expand...
Click to collapse
Unlocked on 95-9
been away for awhile. Thanx Moondroid, and Invisible AOD, & everyone for all the info. I'll try a few things this weekend.
InvisibleAOD said:
Unlocked on 95-9
Click to expand...
Click to collapse
Moondroid said:
I should've been more specific with my question, sorry. . . . Did you actually unlock your bootloader on 95-9, or was it unlocked prior to that OTA and then you ran the root process on 95-9?
@vansteering , I don't mean to hijack your thread.
Click to expand...
Click to collapse
no hijacking here, just much needed info. More is better.