To content farm and other GSM related forums: DO NOT REPOST OR RECOMPOSE THIS TOPIC WITHOUT MY PERMISSION!
查看简体中文 (Simplified Chinese)
Click to expand...
Click to collapse
Introduction
As we all know the curse from former product police still remains, some of you might not satisfy with Android 11 and want to downgrade the phone.
Now I created downgrade package for Nokia 7.2 so you can downgrade back to Android 10 anytime (will work even if the company pushed final guaranteed update). I included an easter egg inside of the downgrade package and feel free to check it out. I only tested this package on device with unlocked bootloader and I don't want to relock the bootloader for another try, so please let me know if it works on locked bootloader devices.
Usage
1. Please perform normal factory reset in settings to erase Google account information, so you won't be locked from FRP.
2. Enter fastboot mode by pressing both volume down and power key.
3. Choose "recovery mode" here with volume keys and power key to confirm.
4. When you see no command displays on the phone, press both power key and volume up key to get the recovery menu.
5A. (For those who own a PC) Choose apply update from ADB, then sideload the package with ADB sideload command.
Code:
adb sideload path\to\downgrade\package.zip
5B. (For those who don't own a PC but has external SD card) Choose apply update from SD card (you'll have to download the package and copy it to external SD card first), then select the package.
6. Wait for the procedure completes.
7. Choose wipe data/factory reset here.
8. Reboot the phone and downgrade is now completed. You must skip Internet connection and disable the automatic update in development options during the procedure.
Download URL
For TA-1178/1181/1196: https://www.androidfilehost.com/?fid=7161016148664837906
For TA-1193: https://www.androidfilehost.com/?fid=7161016148664837927
SHA256 Checksum
DDV-2400-0-00WW-B01-update_enchanted.zip : 125150C61984093B8ED9099483BAF4255A79390F085585D1CDE6EDF0FE4B20FF
TA-1193_DDVA-2400-0-00WW-B01-update_enchanted.zip :
49C460551913DFBCD133CEEFB8FF74D7D4E70FA63551CAFD7EEE95E06229D20F
Special Thanks
@Raghu_Varma for some development experience
@singhnsk for discovering magic spell of enchantment
Reserved #1
Reserved #2
It works fine on locked bootloader devices.
Thank you for this guide! It saved my Nokia 7.2, which I had upgraded to Android 11, and which didn't want to charge without reboot.
Hi, Ok without root and bootloader locked.
It works perfect.
Now I have to apply all sécurity patch since 2021-02 and be carefull to not have 11 upgrade.
You have a good idea to save this ROM.
Many thanks, If it don't work, I think I wil change this phone.
(sorry for some mistake I can do, but I don't use english usually)
PS : You're rigth with the easter egg, I think about that, I take this risk !! ;-D
Sorry man. But, is this a clean firmware?
After a successful downgrade on a locked bootloader unit, can the bootloader unlock instructions be done now (just on device process, no sideloading a package )?
Thanks for the instructions. Now my front camera works again and everything seems to be "normal". I had to do the procedure using extra memory card. I could not find the right ADB version which would have worked with my Nokia.
Thank you very much. It worked on my device. Of course, using external memory. My device bootloader was also locked. I wish you had Android 9. Whatever I did, I could not unlock the bootloader. Now the problem of charging my mobile phone has been solved. But I still have a camera problem. I hope you can put Android 9 for download as well. Now the camera and flashlight are broken, despite Android 10.
I can also downgrade to android 10 from the latest android 11 from Nokia. This method, it still works. Beautiful <3 Thank you very much.
Can unlock bootloader when downgrade to this android v.10
If not, can downgrade one more time to android 9 and then try again for unlock bootloader?
H A M I D said:
Can unlock bootloader when downgrade to this android v.10
If not, can downgrade one more time to android 9 and then try again for unlock bootloader?
Click to expand...
Click to collapse
Yes. It's possible. I just did it yesterday. Downgrade from v. 11 to v.10 using this solution and after that unlock bootloader.
mic1986 said:
Yes. It's possible. I just did it yesterday. Downgrade from v. 11 to v.10 using this solution and after that unlock bootloader.
Click to expand...
Click to collapse
Please guide me with which method did you unlock bootloader?
H A M I D said:
Please guide me with which method did you unlock bootloader?
Click to expand...
Click to collapse
1. You must to downgrade to Android 10 - solution is described in this topic. Please refer to post no. 1
2. Next you have to use solution from this thread - https://forum.xda-developers.com/t/...ader-unlock-for-nokia-7-2-2021-06-22.4295453/
Please find there attached YT video - it could help you to understand whole process.
One thing is missed there - Sideload Packages it's not available anymore. But you can find such one typing "DDV_sprout-RVDP.zip" in google.
Whole process is quite easy to do
mic1986 said:
1. You must to downgrade to Android 10 - solution is described in this topic. Please refer to post no. 1
2. Next you have to use solution from this thread - https://forum.xda-developers.com/t/...ader-unlock-for-nokia-7-2-2021-06-22.4295453/
Please find there attached YT video - it could help you to understand whole process.
One thing is missed there - Sideload Packages it's not available anymore. But you can find such one typing "DDV_sprout-RVDP.zip" in google.
Whole process is quite easy to do
Click to expand...
Click to collapse
Thank you for your guidance
But there are different files of "DDV_sprout-RVDP". Which one did you use?
Can I use from this?
{Mod edit: Link removed. Oswald Boelcke, Moderator}
H A M I D said:
Thank you for your guidance
But there are different files of "DDV_sprout-RVDP". Which one did you use?
Can I use from this?
Click to expand...
Click to collapse
My version TA-1196 was a global / europe version so I used such one: {Mod edit: Link removed. Oswald Boelcke, Moderator}
mic1986 said:
My version TA-1196 was a global / europe version so I used such one:
Click to expand...
Click to collapse
Thank you for all helps bro
But The mission failed at the first step
It seems that this method no longer works, at least for me (android 11, security update August 1, 2022) because I encountered an error and I could not downgrade to Android 10 according to the first post of this topic.
I hope there will be a solution to unlock Nokia 7.2 bootloader soon so that I can try this phone with different custom ROMs. Of course, if I haven't changed this phone
H A M I D said:
Thank you for all helps bro
But The mission failed at the first step
It seems that this method no longer works, at least for me (android 11, security update August 1, 2022) because I encountered an error and I could not downgrade to Android 10 according to the first post of this topic.
I hope there will be a solution to unlock Nokia 7.2 bootloader soon so that I can try this phone with different custom ROMs. Of course, if I haven't changed this phone
Click to expand...
Click to collapse
i am trying to figure this out too. did you ever find anything?
H A M I D said:
Thank you for your guidance
But there are different files of "DDV_sprout-RVDP". Which one did you use?
Can I use from this?
{Mod edit: Link removed. Oswald Boelcke, Moderator}
Click to expand...
Click to collapse
mic1986 said:
My version TA-1196 was a global / europe version so I used such one: {Mod edit: Link removed. Oswald Boelcke, Moderator}
Click to expand...
Click to collapse
I've removed the download links from your above posts. Pleasein future don't share developments without the permission of the original developers. If you still want to share this, please contact @Raghu varma and obtain his permission. Additionally, always give credits when credits are due; more information is available in the XDA Forum Rules. Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
Related
Is someone out there with original android 8 ROM for TA-1054 to upload so I can flash it and receive all the updates.
The original ROM is in Google folder in mena topic its 7.1.2 but you will get ota,s to 8.1
safron35 said:
The original ROM is in Google folder in mena topic its 7.1.2 but you will get ota,s to 8.1
Click to expand...
Click to collapse
Thank you,
Can you send the link please?
Hallo, i bought a chinese version of Nokia 6 (2018) RM-1054 an the Screen is frozen on NOKIA after first restart after Google-Login. How can i update the Phon for the german Google-Play?
safron35 said:
The original ROM is in Google folder in mena topic its 7.1.2 but you will get ota,s to 8.1
Click to expand...
Click to collapse
I've been browsing that ta-1054 topic for the last couple of days. Let me confirm if I have this right. You were also having the Chinese version ta-1054 stuck with 7.1.1 November 6, 2017 security patch. You managed to flash it with the original ROM version 7.1.2 and you began receiving OTA updates afterwards? If so, please send a link with the ROM version you used for your ta-1054. There is one thing I notice on my phone. I managed to switch on the OEM bootloader trough the developer options in an instant, and I am reading that the other guys are not having access to this option.
Hi,
No progress until now.
I want to flash an original ROM for Android 8 but first I need to unlock bootloader where a key is necessary but I don't know how to get it. I can't find a concrete advice how to solve this problem. I don't know if this device will get any upgrade in the future. Sad.
You need to get you're bootloader unlocked by hikari calyx first,talk to him on twitter he's fine to do it
safron35 said:
The original ROM is in Google folder in mena topic its 7.1.2 but you will get ota,s to 8.1
Click to expand...
Click to collapse
could you send me that rom too, please?
You can download it yourself from the Google drive folder ,just look for it
safron35 said:
You can download it yourself from the Google drive folder ,just look for it
Click to expand...
Click to collapse
Sorry, but i can't find the link of google folder, where is it?
ginherma said:
Sorry, but i can't find the link of google folder, where is it?
Click to expand...
Click to collapse
This one
https://drive.google.com/drive/u/0/mobile/folders/1t64iHuQQjmMnzcujZtjYplh6ipbiF6Cw?usp=sharing
Download the PL2 064D oneand flash it through OST LA
sltushar said:
This one
https://drive.google.com/drive/u/0/mobile/folders/1t64iHuQQjmMnzcujZtjYplh6ipbiF6Cw?usp=sharing
Download the PL2 064D oneand flash it through OST LA
Click to expand...
Click to collapse
Hi, did it work it in your ta 1054?
ginherma said:
Hi, did it work it in your ta 1054?
Click to expand...
Click to collapse
Budy its for ta-1054 only
sltushar said:
Budy its for ta-1054 only
Click to expand...
Click to collapse
I said it because i have already that file, but everyone that download it didn't say if it works or not at their phones to update to 8.1. At the beginning, the file was at pan.baidu server
ginherma said:
I said it because i have already that file, but everyone that download it didn't say if it works or not at their phones to update to 8.1. At the beginning, the file was at pan.baidu server
Click to expand...
Click to collapse
Budy i have ta-1021, cant say if it works or not but as it was confirmed by the build number that one of the member had with 064D, so it was confirmed that its for ta-1054
This firmware is only available till now, rest is your choice
I habe the file and i try to unlock bootloadet and flash it. I will report success or failure after procedure completion.
When i try to flash my ta-1054 with OST I get next error:
The Update process falied!
Error Code: 0xc6da
Error: Download fails,
Error = SE_ERR_ADB_CMD_GET_FAIL_RESULT (0xC6DA)
I understood that I must unlock bootloader to solve the error. I am right ?
Can you give me link to steps for unlocking bootloader?
Tnx
sltushar said:
Budy i have ta-1021, cant say if it works or not but as it was confirmed by the build number that one of the member had with 064D, so it was confirmed that its for ta-1054
This firmware is only available till now, rest is your choice
Click to expand...
Click to collapse
As one of the guys just said, we are getting the following error code. I tried flashing my phone twice, once with internet connection on, and again without. Funny thing is that the OST tool as it name clearly states is asking for an internet connection. It did this twice during the flashing process and both times it ended with the same error code.
The firmware works, but as I keep saying it won't work if you haven't had your bootloader unlocked ,it will give you the error when you try to flash it ,
And how we can unlock bootloader ?
Hello,
this is the very first time here at XDA Developers Forum that I do not find clear information about rooting a smartphone. I am talking about this Nokia 3 updated with OREO 8.0. Only a lot of confusion reading your posts, sirs. Nobody that is telling if rooting this model is possibile or not. So... can anyone says if it is possibile and how to do that, in a clear and simple manner?
Thanks and regards!
jimgordon said:
Hello,
this is the very first time here at XDA Developers Forum that I do not find clear information about rooting a smartphone. I am talking about this Nokia 3 updated with OREO 8.0. Only a lot of confusion reading your posts, sirs. Nobody that is telling if rooting this model is possibile or not. So... can anyone says if it is possibile and how to do that, in a clear and simple manner?
Thanks and regards!
Click to expand...
Click to collapse
here you go
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-flash-twrp-magisk-t3785768
this thread should be on Q&A.
Hello,
thanks for your reply. I already read this thread.
So since I am on OREO, it seems I have firstly to downgrade to Nougat. Can someone please tell me how to do that, posting links to the official 7.0 rom, the software and a short guide? Somewhere I read you have to use OST, somewhere else SP Flash Tool...
Thanks in advance and regards
Cosimo
Hello again...
I am trying to downgrade my Nokia 3 8.0 to Nougat, in order to unlock the bootloader.
I have searched a lot for an official 7.0 rom... nothing official... I tryed to follow this guide:
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320
Managed to install and get a working copy of OST. Connected and start flashing the rom NE1-147I-ind-0-00WW-B02.nb0 (the one I thought it was the earlier one, since nobody wrote "7, 8, or another number" in the file name). OST got stuck at "Reflash service bootloader..."
Can anyone please write a clear guide on how to proceed to root a Nokia 3 OREO that was never ever unlocked before (i mean with bootload never unlocked)? I am going crazy, really...
jimgordon said:
Hello again...
I am trying to downgrade my Nokia 3 8.0 to Nougat, in order to unlock the bootloader.
I have searched a lot for an official 7.0 rom... nothing official... I tryed to follow this guide:
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320
Managed to install and get a working copy of OST. Connected and start flashing the rom NE1-147I-ind-0-00WW-B02.nb0 (the one I thought it was the earlier one, since nobody wrote "7, 8, or another number" in the file name). OST got stuck at "Reflash service bootloader..."
Can anyone please write a clear guide on how to proceed to root a Nokia 3 OREO that was never ever unlocked before (i mean with bootload never unlocked)? I am going crazy, really...
Click to expand...
Click to collapse
flash UAE version of nb0 if IND doesn't flash, that's Android 7.0 May 2017 Security Patch, unlock and lock bootloader there and apply OTA updates from notification up to latest update. Then follow guide.
SkaboXD said:
flash UAE version of nb0 if IND doesn't flash, that's Android 7.0 May 2017 Security Patch, unlock and lock bootloader there and apply OTA updates from notification up to latest update. Then follow guide.
Click to expand...
Click to collapse
Hi, thanks again for your precious support. Can you give me a link to download the UAE version of the firmware? At this address: https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg I can only find the IND one.
Regards
jimgordon said:
Hi, thanks again for your precious support. Can you give me a link to download the UAE version of the firmware? At this address: https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg I can only find the IND one.
Regards
Click to expand...
Click to collapse
oh they deleted it it was before. I have it on PC, but PC can't turn on.
I have found the file elsewhere... NE1-147C-UAE-0-00WW-B01.nb0
I have tried to upload using OST, and got the same result: stuck at "Reflash service bootloader..."
Is there someone that can help me?
jimgordon said:
I have found the file elsewhere... NE1-147C-UAE-0-00WW-B01.nb0
I have tried to upload using OST, and got the same result: stuck at "Reflash service bootloader..."
Is there someone that can help me?
Click to expand...
Click to collapse
which ost la version you have?
I finally managed to downgrade to Nougat 7.0.
Now, in order to get root, do I have to unlock bootloader first? Can I obtain the code only via a request to the_laser (that didn't answer me) or can I use an online tool ?
jimgordon said:
I finally managed to downgrade to Nougat 7.0.
Now, in order to get root, do I have to unlock bootloader first? Can I obtain the code only via a request to the_laser (that didn't answer me) or can I use an online tool ?
Click to expand...
Click to collapse
you need to unlock bootloader first, and you can PM code i will send you key, use only OTA through notification, don't use OST LA for this guide.
Can you tell the way you downgraded ur Nokia 3
jimgordon said:
I finally managed to downgrade to Nougat 7.0.
Now, in order to get root, do I have to unlock bootloader first? Can I obtain the code only via a request to the_laser (that didn't answer me) or can I use an online tool ?
Click to expand...
Click to collapse
Hi,
can u tell me the method in which you downgraded Nokia 3 from 8.0 to 7, also were u able to unlock the boot loader and root the device. Waiting for your reply as one of my friend also wanna do the same.
If you want to repost this internal OTA to other websites (other than XDA itself), please ask me for permission, thanks.
Click to expand...
Click to collapse
WARNING!
This is early internal test build, so LATER OTA UPDATES CAN'T BE GUARANTEED!
If you don't have unlocked bootloader, you'll unable to roll back to stable build!
Please be careful when testing!
Click to expand...
Click to collapse
To users who have installed this internal build, please share your experience report here if you're willing to, thanks.
UPDATE: Thanks everyone. To fix microphone bug, please disable the microphone permission of the "Google" app.
You'll lose "OK Google" ability, but you can make telephone call properly.
Click to expand...
Click to collapse
Now I think it's time to bring you back to canary labs faster than beta labs.
Internal build version: PL2-4040-0-00WW-B01
It will be updated from: PL2-354N-0-00WW-B01, which is released October 2019 Security Update
As I've warned before - having an unlocked bootloader is strongly recommended.
So recent builds removed handy 874 dialing codes, we have to install them under recovery or Nokia Extensions.
Let me tell you how to verify:
1. Dial *#*#227#*#* to check current Version. If older than PL2-354N-0-00WW-B01, update to 354N before proceed.
FYI, 354N is October 2019 Security Update.
Alternately, you can use command "fastboot oem getversions" under fastboot mode / Download mode to check current firmware version.
2. Install PL2-4040-0-00WW-B01-354N-0-00WW-B01-update.zip with Nokia Extensions OTA Update module or adb sideload under recovery.
3. Reboot your phone.
That's it.
If minor fixes released, I will upload them as well, then use the same method to install it.
To root the phone, you may want to use Magisk 20 released October 12th, 2019 or newer.
Download link:
https://www.androidfilehost.com/?w=files&flid=300345
reserved
Installed it on my TA-1043.
OS installed fine over adb sideload, everything seems to be working, and it shows "5" next to my wifi icon - guess it's cause it's 5GHz, also the mobile data icon is still not AOSP and some custom thing. Menus kinda feel stutter-ish. Screenshots were broken on first boot.
alternate download links like google drive?
The update wont install
version no. L2-354O-0-00WW-B01
Update: "Photo" mode in stock camera is broken, says "Action not support: 708". Pro mode works fine
how to use magisk?
i tryed to patch boot on magisk and boot from ADB, but phone going n bootloop and doesn't want up
Hi @hikari_calyx I'm currently on the DRG-354N-0-00WW-B01 stock build version with an unlocked bootloader. But the version on the post has PLC. Also, if after sideloading this rom I decide to go back to the October PIE update how hard will that be. Thanks.
solozeeh said:
Hi @hikari_calyx I'm currently on the DRG-354N-0-00WW-B01 stock build version with an unlocked bootloader. But the version on the post has PLC. Also, if after sideloading this rom I decide to go back to the October PIE update how hard will that be. Thanks.
Click to expand...
Click to collapse
Hi. DRG is Nokia 6.1 Plus. This thread is for Nokia 6.1 (2018) which is PL2.
Getting error when the camera app is set to save photo to sd card.
---------- Post added at 03:24 PM ---------- Previous post was at 02:58 PM ----------
So right now for me on the Internal Stock... I cannot boot any TWRP of any kind or boot any patched magisk boot img. Has anyone been able to boot either TWRP or boot a patched boot img from magisk?
May I ask, can Nokia 6.1 plus use this rom?
joshclaudio said:
Hi. DRG is Nokia 6.1 Plus. This thread is for Nokia 6.1 (2018) which is PL2.
Click to expand...
Click to collapse
The confusion is caused by the fact that the Nokia 6.1 Plus (DRG) forum on XDA was recently deleted and now redirects here.
Apparently XDA is working to restore the DRG forum but it will take some time. Until that is done you can expect to see a lot of confused DRG users here on the PL2 forum. Please help them out if you can.
kazekiri said:
The confusion is caused by the fact that the Nokia 6.1 Plus (DRG) forum on XDA was recently deleted and now redirects here.
Apparently XDA is working to restore the DRG forum but it will take some time. Until that is done you can expect to see a lot of confused DRG users here on the PL2 forum. Please help them out if you can.
Click to expand...
Click to collapse
Yeah, noticed that, too. I've been experiencing redirect problems since yesterday. Anyway, I installed Android 10 leaked internal build on my Nokia 6.1 Plus with a locked bootloader :silly: . Been using it for more than 48 hours and I have not faced any major issue, except for the not working microphone during calls (plugging in earphones can suffice, though).
solozeeh said:
Hi @hikari_calyx I'm currently on the DRG-354N-0-00WW-B01 stock build version with an unlocked bootloader. But the version on the post has PLC. Also, if after sideloading this rom I decide to go back to the October PIE update how hard will that be. Thanks.
Click to expand...
Click to collapse
Here's the link for the DRG version for anyone who needs it. (Since the DRG forum is currently down.)
Only install this if you are using a Nokia 6.1 Plus or X6 (DRG). DO NOT try to install on Nokia 6.1 2018 (PL2).
https://androidfilehost.com/?w=files&flid=300344
Hi hikari calyx! Please help me downgrade my Nokia 6.1 to Android 9. Bootloader locked
kaktyys71 said:
Hi hikari calyx! Please help me downgrade my Nokia 6.1 to Android 9. Bootloader locked
Click to expand...
Click to collapse
"If you don't have unlocked bootloader, you'll unable to roll back to stable build!"
Literally on top of the OP post. As every downgrade/restoration method needs an unlocked bootloader, you can either unlock yours (paid external service), or wait for an eventual OTA zip (not guaranteed, as stated by the OP) that will bring you back on Android 10 official Beta/Release in a couple of weeks.
Solannae said:
"If you don't have unlocked bootloader, you'll unable to roll back to stable build!"
Literally on top of the OP post. As every downgrade/restoration method needs an unlocked bootloader, you can either unlock yours (paid external service), or wait for an eventual OTA zip (not guaranteed, as stated by the OP) that will bring you back on Android 10 official Beta/Release in a couple of weeks.
Click to expand...
Click to collapse
Project Treble A/B? B slot don't help me?
I guess it ils worth a try. Reboot to bootloader, then "fastboot getvar all" to get active slot and "fastboot --set-active=[a/b, your inactive slot]
The thing is, with official OTA updates, once the update is over and everything went well, the previous slot is not necessarily in a bootable/usable state anymore. It is not the case with most custom roms/gsi as you either update directly on the current slot or on the other without modifying the active one, so you can switch between slots without issues.
kaktyys71 said:
Project Treble A/B? B slot don't help me?
Click to expand...
Click to collapse
If you switch inactive slot to active slot and reboot... it will ask to do a factory reset. Perform the factory reset and you should be back to the Pie version. Use the fastboot commands Solannae posted above.
---------- Post added at 11:58 PM ---------- Previous post was at 11:36 PM ----------
Battery draining fast on Internal Android 10.
The battery drain was due to the Adguard app. Everything is working normal again.
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
Hello all,
I have read so many threads, and finally I'm still not sure to have the right method.
My current config has no more memory to update apps so I need to do something ! Here are the details :
Huawei P8 Lite 2017 (PRA-LX1)
build : 8.0.0.402 (C432patch01)
EMUI : 8.0.0
Android : 8.0.0
After reading several threads, here are my questions :
1. I have to use DC Unlocker --> is it always mandatory ?
2. Which TWRP do I have to use ? (link please, I'm completely lost, an still doesn't know which one to download ! :angel: )
3. LineageOS 15.1 seems to be the best choice (battery stamina), does it work perfectly ? (GPS, camera...)
4. What about Treble Project ? I still doesn't understand it is a better idea, how to install it, which ROM to use...
Thanks for all of your replies !
Hello,
DC-Unlocker is mandatory if your bootloader is locked. Recently, TWRP went official on P8 Lite 2017 devices. You can grab it from the official TWRP website (can't post links as I am a new user, search for 'prague' in the device list). I am using LineageOS 15.1 on my device and it's working flawlessly.
I use chimera to unlock bootloader.
But every custom to a have to flash isn't work. Boot loop or other issuses, like "device is uncertificated" so any google apps don't work.
Do i need to decrypt memory? To flash corectly custom rom.
Finally i have only root, and clean all brand apps.
flgmnft said:
I use chimera to unlock bootloader.
But every custom to a have to flash isn't work. Boot loop or other issuses, like "device is uncertificated" so any google apps don't work.
Do i need to decrypt memory? To flash corectly custom rom.
Finally i have only root, and clean all brand apps.
Click to expand...
Click to collapse
https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/
Decrypt in which case? If everything works there is no need to decrypt.
---------- Post added at 23:12 ---------- Previous post was at 22:48 ----------
cactus2000 said:
Hello all,
I have read so many threads, and finally I'm still not sure to have the right method.
My current config has no more memory to update apps so I need to do something ! Here are the details :
Huawei P8 Lite 2017 (PRA-LX1)
build : 8.0.0.402 (C432patch01)
EMUI : 8.0.0
Android : 8.0.0
After reading several threads, here are my questions :
1. I have to use DC Unlocker --> is it always mandatory ?
2. Which TWRP do I have to use ? (link please, I'm completely lost, an still doesn't know which one to download ! :angel: )
3. LineageOS 15.1 seems to be the best choice (battery stamina), does it work perfectly ? (GPS, camera...)
4. What about Treble Project ? I still doesn't understand it is a better idea, how to install it, which ROM to use...
Thanks for all of your replies !
Click to expand...
Click to collapse
1. Download DC Unlocker from GPlay, buy credits (it will send you username and password to your email)
2. Download DC Unlocker to your pc, in phone allow ADB debuging and HDB
3. Type into call app '*#*#2846579#*#*', tap on 'Background settings', next on 'USB Ports Settings' and select 'Manufacture mode'.
4. Plug your phone to PC and click on 'Detect device' and allow all stuff that will pop up on your phone.
5. Click on 'Server' tab (we are still on PC) and enter username and password you've got from app and 'Check login'.
6. Click on 'Unlocking' tab and choose 'Unlock bootloader code'. And your code should popup in text log.
7. Let's move to your phone, go to settings -> developer settings -> Enable OEM unlocking, enter your password.
8. Power off your phone and when it vibrate push Vol - and Power button at same time.
8. Plug it back to your PC and start Command prompt, enter 'fasboot oem unlock 00112233445566778899' (use your code).
9. Now just accept unlocking and formating all your data on the phone.
10. Download TWRP and let's flash it using command 'fastboot flash recovery_ramdisk twrp.img' (if your command prompt is in for example C:\Users\Pepege just cd to your Downloads directory where is downloaded .img file)
11. If it's succesfull just type 'fastboot reboot' and keep holding volume up, if eRecovery pops up click on reboot and this time hold volume up and down (idk why but sometimes works this and sometimes this combo)
12. If you are in TWRP just format DATA, CACHE and Dalvik Cache partition, make backup (if you wanna) and now flash whatever you wanna. LOS, AOSP, it's on you.
Also if you wanna LOCK (not relock) your device, download HuRuUpdater, download oldest version of Android for your model and region (C432 in this case) and flash it, after you reboot from recovery go to bootloader (fastboot mode) and type on your pc 'fastboot oem relock 00112233445566778899' then 'fastboot reboot' now do first setup, go to developer options, disable 'Enable OEM unlock', format data again (to be safe) and you are ready to go, after updating to oreo relock status should change to locked.
EDIT: Adding random Youtube video just in case https://www.youtube.com/watch?v=pclEmwt5C84
EDIT2: Project treble is simply stuff splitting system from vendor, it's on every device runing on oreo or better, more here https://www.xda-developers.com/goog...ze-android-so-oems-can-update-devices-faster/
Also for me best ROM are AOSP 10 and LOS 17.1
No custom rom wanted to boot. The method on this page will not work. All that's left for me is to decrypt the phone's memory. but then knowing that the weekend was over and I needed a phone call on Monday, I just let go.
@DunoCZ
What a great post, thank you so much !!!
Some people have reported more battery consumption on Lineage 16 and 17, compared to 15. Did you test all of these ROM ? Are there people here who have some feedback ?
@flgmnft
If I unterstand well, I need to extract fstab file from the ROM archive in order to remove the encryption : can you confirm or explain me what to do ?
@ilakhnon
It seems you don't have the encryption problem, what is your opinion about it ? did you edit the ROM fstab file ? other ?
cactus2000 said:
@DunoCZ
What a great post, thank you so much !!!
Some people have reported more battery consumption on Lineage 16 and 17, compared to 15. Did you test all of these ROM ? Are there people here who have some feedback ?
@flgmnft
If I unterstand well, I need to extract fstab file from the ROM archive in order to remove the encryption : can you confirm or explain me what to do ?
@ilakhnon
It seems you don't have the encryption problem, what is your opinion about it ? did you edit the ROM fstab file ? other ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/attachment.php?attachmentid=5070533&d=1596027508
Here you go guys, no need to edit it on your own
hummmmm.... bad news : my phone is not detected by DC Unlocker !
I should have tried before buying the license, but it doesn't matter.
But don't you find it strange ?
oh... I didn't read it correctly, the P8 Lite 2017 is not supported, only the P8 Lite (that was my mistake).
But I wonder if I really need it, because I bought it "sim unlocked", what do you think about it ?
EDIT : in other words, how can I know if I can erase the original bootloader ? (adb method)
cactus2000 said:
hummmmm.... bad news : my phone is not detected by DC Unlocker !
I should have tried before buying the license, but it doesn't matter.
But don't you find it strange ?
Click to expand...
Click to collapse
Then try using hisuite to downgrade to nougat, but after unlocking upgrade to oreo to have treble enabled.
I'm waiting for an answer from DC unlocker's developper, and I will test this solution if I don't have another choice.
(I don't know if it is easy to downgrade with HiSuite, I've never used it, I will see that later).
Thank you for your help.
cactus2000 said:
I'm waiting for an answer from DC unlocker's developper, and I will test this solution if I don't have another choice.
(I don't know if it is easy to downgrade with HiSuite, I've never used it, I will see that later).
Thank you for your help.
Click to expand...
Click to collapse
Downgrading via Hisuit is easy
DunoCZ said:
Then try using hisuite to downgrade to nougat, but after unlocking upgrade to oreo to have treble enabled.
Click to expand...
Click to collapse
Hello @DunoCZ,
I was thinking about this post... I won't need to unlock the bootloader if I downgade to Nougat ?
Is there a topic talking about it ?
EDIT : Sorry, I didn't read correctly your post. Unlocking will probably be mandatory, so it doesn't change anything for me.
cactus2000 said:
oh... I didn't read it correctly, the P8 Lite 2017 is not supported, only the P8 Lite (that was my mistake).
But I wonder if I really need it, because I bought it "sim unlocked", what do you think about it ?
EDIT : in other words, how can I know if I can erase the original bootloader ? (adb method)
Click to expand...
Click to collapse
There's no problem unlocking 2017 with DC Unlocker which I did two days ago.
Install HiSuite and run it once to be sure you got proper drivers and make sure you put USB into manufacture mode.
cactus2000 said:
I'm waiting for an answer from DC unlocker's developper, and I will test this solution if I don't have another choice.
(I don't know if it is easy to downgrade with HiSuite, I've never used it, I will see that later).
Thank you for your help.
Click to expand...
Click to collapse
I had the same issue, and contacted dc_unlocker's developer. Basically, the software can read the bootloader unlock password if it just discoverer the phone's port, even if does not seem to recognize the phone. I had to go ahead an got the code, for 4 credits/€
I'm also interested in knowing what is the best overall ROM these days in terms of compatibility and battery consumption!
Hello all,
Sorry for my silence, I had to go back to work, and after a few days I was seriously ill. I begin to recover some energy, it's not great, but enough to come back here... and because my phone, stiill with the original system, becomes really too slooooooooooooow !
@buteo : Do you confirm me I can go further with DC-unlocker software, in order to unlock the bootloader without any risk ?
@All :
As @Natural_High asked, which ROM is currently the best choice ?
Thanks for your help !
cactus2000 said:
Hello all,
Sorry for my silence, I had to go back to work, and after a few days I was seriously ill. I begin to recover some energy, it's not great, but enough to come back here... and because my phone, stiill with the original system, becomes really too slooooooooooooow !
@buteo : Do you confirm me I can go further with DC-unlocker software, in order to unlock the bootloader without any risk ?
@All :
As @Natural_High asked, which ROM is currently the best choice ?
Thanks for your help !
Click to expand...
Click to collapse
You can use DC-unlocker, it's safe. I used it myself a couple of months ago too.
Regarding the ROM, I haven't tried any Android 10 or 9 ROMs. From what I've seen, people say it's still a bit too buggy, so I went for LineageOS 15.1 and it worked fine. I did some tests, since I don't use it as my daily driver, but eveything seemed to work fine! anyway, feel free to try some of the newer ROMs and let us know your opinion
Thank you very much for your answer !
Lineage 15.1 was my preferred choice, I think I will use it.
I hope I won't have any issues, since I really need my phone...
Let's go for backup...
Read the last page here: https://forum.xda-developers.com/p8...geos-15-1-huawei-p8-lite-2017-t3886328/page35
The steps that worked for me are there.