Is it possible to downgrade from A12 to A10/11? (exynos) - Samsung Galaxy S10+ Questions & Answers

Hello there!
I recently got a hand me down S10+ (exynos) from a relative and I want to flash LineageOS on it.
One small problem, its got the latest A12 version (March 1st 2022 security patch).
I have already picked out an A11 version with a matching bootloader binary (G975FXXSEFUL1) and installed Odin onto my computer (usb debugging is also enabled).
Links to guides and other forum posts are appreciated.
(I apologize if this has been asked before, I haven't found out how to search specific sup-sections of this forum (if even possible).)

MrSeatbelt said:
Hello there!
I recently got a hand me down S10+ (exynos) from a relative and I want to flash LineageOS on it.
One small problem, its got the latest A12 version (March 1st 2022 security patch).
I have already picked out an A11 version with a matching bootloader binary (G975FXXSEFUL1) and installed Odin onto my computer (usb debugging is also enabled).
Links to guides and other forum posts are appreciated.
(I apologize if this has been asked before, I haven't found out how to search specific sup-sections of this forum (if even possible).)
Click to expand...
Click to collapse
If the bootloader is unlocked, it should be fairly trivial to flash an older ROM using Odin.

V0latyle said:
If the bootloader is unlocked, it should be fairly trivial to flash an older ROM using Odin.
Click to expand...
Click to collapse
Im assuming it doesnt come unlocked, redirect me to a guide maybe?

MrSeatbelt said:
Im assuming it doesnt come unlocked, redirect me to a guide maybe?
Click to expand...
Click to collapse
Use the Search function. Google is also your friend. I haven't been in the Samsung game for quite some time.
Be aware that unlocking the bootloader is often impossible on Exynos devices.

V0latyle said:
Use the Search function. Google is also your friend. I haven't been in the Samsung game for quite some time.
Be aware that unlocking the bootloader is often impossible on Exynos devices.
Click to expand...
Click to collapse
So I followed a guide and it told me to enable the OEM unlock function in the dev settings.
so is it unlocked now?
or does that just allow me to unlock it?
(apologies if I sound like a complete novice)

MrSeatbelt said:
So I followed a guide and it told me to enable the OEM unlock function in the dev settings.
so is it unlocked now?
or does that just allow me to unlock it?
(apologies if I sound like a complete novice)
Click to expand...
Click to collapse
nvm, found a better guide
(https://www.recovery-mode.com/android/unlock-bootloader-samsung-galaxy-s10-plus-and-hard-reset.html)

when flashing with odin do I need userdata?

Ive done some digging and apparently userdata is used for phone carriers to brand the phones they give out?

Ok it was pretty simple, userdata isnt needed.
Hello A11!

Related

Risk of unlocking bootloader and flashing twrp.

Hello
I am aware that there isn't any warranty at all here that anything you do won't have negative effects on your phone. I've flashed quite a few roms on phones like the oneplus one, sony xperia sp, samsung galaxy core plus, nexus 5x, lg cookie, moto defy plus,... I've had tens of soft bricks, but never anything I couldn't recover from.
Anyways, I'm sick and tired of the laggy MiFavor UI on this phone, and would like to install CM13. I've an A2016G. I've seen some EU folk have issues with Tenfar's unlocking method, having hard bricked them since they can't get into a certain (EDL?) mode.
My question is this: if I read every thread and follow every step very carefully, is there a major risk my axon 2016G turns into a 450 euro paperweight? Is there perhaps another unlock method that's 99% secure?
Thank you
Jan
Hate to be that guy, but is there no-one with some knowledge around this?
Thanks.
Controllerboy said:
Hate to be that guy, but is there no-one with some knowledge around this?
Thanks.
Click to expand...
Click to collapse
Let me be the second guy, I'm amazed no one replied...
I'm in the same predicament; do I stay stock and use a great piece of hardware with crap software, or do I dare take the plunch and be able to make the phone as it ought to be at the risk of ending up with a very expensive paperweight...
What the hell did ZTE think when developing the A2017G model. And why is there after all these month no clear answer/procedure for this model. Is it that rarely used? How come there is no solution even though the firehose files are out there?
Hope someone finds a fullproof solutions soon....
Cheerz,
/Cacti
Verstuurd vanaf mijn ZTE A2017G met Tapatalk
I have the US model and I won't use tenfar's method on the phone for which it's intended. It's a questionable method
Unlocking your bootloader and Flashing CM13 is pretty easy and I don't really think there is much risk of permanently bricking your phone. However as of right now it really isn't worth the effort. I flashed CM 13 yesterday and it ran well, but the camera wasn't working so I decided to go back to the stock software. So unless you don't need the camera I'd skip flashing for now.
lag?
Controllerboy said:
Hello
I am aware that there isn't any warranty at all here that anything you do won't have negative effects on your phone. I've flashed quite a few roms on phones like the oneplus one, sony xperia sp, samsung galaxy core plus, nexus 5x, lg cookie, moto defy plus,... I've had tens of soft bricks, but never anything I couldn't recover from.
Anyways, I'm sick and tired of the laggy MiFavor UI on this phone, and would like to install CM13. I've an A2016G. I've seen some EU folk have issues with Tenfar's unlocking method, having hard bricked them since they can't get into a certain (EDL?) mode.
My question is this: if I read every thread and follow every step very carefully, is there a major risk my axon 2016G turns into a 450 euro paperweight? Is there perhaps another unlock method that's 99% secure?
Thank you
Jan
Click to expand...
Click to collapse
ok, where is this lag? I've been using it stock since I got it after the Note 7, which was very laggy, and have failed to notice any lag.
Zero lag here as well, buttery smooth at all times. Heads and shoulders above the Note 7 that I came from in terms of responsiveness and general performance.
Sent from my ZTE A2017 using Tapatalk
jawz101 said:
I have the US model and I won't use tenfar's method on the phone for which it's intended. It's a questionable method
Click to expand...
Click to collapse
On the US model, you can get an unlocked bootloader & all the trimmings without using tenfar's tool at all, although it's a bit more of a roundabout method.
Just unlocked mine working great.
Hi,
Just thought I'd add as I'm one of those who did end up in DFU mode permanently. I have a reasonable understanding of the issue at hand and I've been one of the few who have been vocal about not calling the current method safe of us.
My suggestion if you have a A2017G is not to bother using tenfar's tool unless you're willing to RMA or make use of your warranty. I'm not in a position where I can do that, but since most are there hasn't been much interest in a solution.
I don't have the firehose itself to begin working on fixing the issue, though I do have a rough idea of how do so using the partition table for TWRP but I don't think I have the time to learn how to put it all together myself. Particularly when I'm replacing my Axon 7 with a Mi Note 2.
What is needed is an unbrick tool, ZTE have made and released them for their own devices before, why they don't do that with Axon 7 is beyond me.
rendler said:
Zero lag here as well, buttery smooth at all times. Heads and shoulders above the Note 7 that I came from in terms of responsiveness and general performance.
Sent from my ZTE A2017 using Tapatalk
Click to expand...
Click to collapse
You must be using the US or CN model, because the EU model is laggy as hell. It's by far the laggiest ROM I used on a phone with high-end specs..
keessonnema said:
You must be using the US or CN model, because the EU model is laggy as hell. It's by far the laggiest ROM I used on a phone with high-end specs..
Click to expand...
Click to collapse
Yup, using Chinese model with 128GB of storage.
Sent from my ZTE A2017 using Tapatalk
Just my 2 cents having unlocked the bootloader on my A2017G. I used tenfar's tool to backup the boot and stock recovery images and flashed the TWRP recovery and didn't run into problems fortunately. I wouldn't recommend to flash the rooted boot.img by tenfar until (hopefully) we'll have a unbrick tool for the G version.
My recommendation ----- On the G version don't mess around with the bootloader! ----- My recommendation
I've been able to unlock the bootloader on B03, reflashed stock recovery with tenfar's tool and successfully updated to B05 from the SD card.
If you want root I recommend to go the unlock bootloader - flash SuperSU 3.65 route instead of flashing the pre-rooted boot.img from tenfar with a locked bootloader as chances of things going haywire seem to be greater with the second method on the G version.
In case you have any reservations I definitely recommend to wait for a unbrick method of the G version before you try any of this. If and when such a method will come is undetermined at this point in time.
@lag of G version: Can't confirm that on B05, everything running smooth so far. There are a few graphical glitches though (stock browser displaying left side first und has sometimes trouble to show the content fullscreen.
Pull down notification bar has double lined icon text slightly cut off on the bottom once you switch to landscape mode and pull down the notification bar.
jawz101 said:
I have the US model and I won't use tenfar's method on the phone for which it's intended. It's a questionable method
Click to expand...
Click to collapse
I've seen this said a couple of times (or maybe it's just you in different threads, I don't know), but I don't understand it. By its very nature, rooting your phone is "questionable". Why is tenfar's method/tool any worse than any other method or tool? Do you have some technical insight to provide (and if so, please do so) or is it just an opinion based on nothing? I certainly don't have any issue with the latter, but I find it odd that people without any technical expertise speak as if they're an authority of some kind.
rczrider said:
I've seen this said a couple of times (or maybe it's just you in different threads, I don't know), but I don't understand it. By its very nature, rooting your phone is "questionable". Why is tenfar's method/tool any worse than any other method or tool? Do you have some technical insight to provide (and if so, please do so) or is it just an opinion based on nothing? I certainly don't have any issue with the latter, but I find it odd that people without any technical expertise speak as if they're an authority of some kind.
Click to expand...
Click to collapse
It's probably me and a few others. Ok, answer me these questions:
What does the tool specifically modify on the phone?
What is a "firehose mbn" anyway? Tenfar mentioned it is how it gains access to the phone. I don't know if that is a tool to do so or if it's a file that gets put on the phone in a more permanent chipset-level storage only meant to be altered by Qualcomm or phone manufacturers. I'm find with replacing a recovery, kernel, ROM- the boot.img or anything lower than that is closed source for a reason. Probably because it's talking directly to the hardware and code at that lower level can circumvent anything in a kernel, recovery or ROM.
Would it affect Snapdragon SmartProtect?
https://www.qualcomm.com/products/snapdragon/security/smart-protect
Why do virus scanners call it a Windows trojan if it's an Android hack?
Yes, I call it questionable because I have questions. Since the file is encrypted you can't answer those questions for me. All I can gather is everyone who has used it has basically said "I used it and it did what I wanted it to do so it must be safe."
---------- Post added at 10:20 AM ---------- Previous post was at 09:46 AM ----------
@rczrider
Here are the posts in the thread by a security expert asking questions about the method.
http://forum.xda-developers.com/search.php?searchid=430010789
Here is tenfar's response to him
http://forum.xda-developers.com/axo...r-unlokced-t3441204/post68301899#post68301899
Here's a post from him on ZTEUSA
https://community.zteusa.com/message/50425
Here's a blog post he made about it
https://blog.onedefence.com/signed-firehose-images-and-why-theyre-dangerous/?pk_campaign=zte-forums
jawz101 said:
It's probably me and a few others. Ok, answer me these questions:
What does the tool specifically modify on the phone?
What is a "firehose mbn" anyway? Tenfar mentioned it is how it gains access to the phone. I don't know if that is a tool to do so or if it's a file that gets put on the phone in a more permanent chipset-level storage only meant to be altered by Qualcomm or phone manufacturers. I'm find with replacing a recovery, kernel, ROM- the boot.img or anything lower than that is closed source for a reason. Probably because it's talking directly to the hardware and code at that lower level can circumvent anything in a kernel, recovery or ROM.
Would it affect Snapdragon SmartProtect?
https://www.qualcomm.com/products/snapdragon/security/smart-protect
Why do virus scanners call it a Windows trojan if it's an Android hack?
Yes, I call it questionable because I have questions. Since the file is encrypted you can't answer those questions for me. All I can gather is everyone who has used it has basically said "I used it and it did what I wanted it to do so it must be safe."
---------- Post added at 10:20 AM ---------- Previous post was at 09:46 AM ----------
@rczrider
Here are the posts in the thread by a security expert asking questions about the method.
http://forum.xda-developers.com/search.php?searchid=430010789
Here is tenfar's response to him
http://forum.xda-developers.com/axo...r-unlokced-t3441204/post68301899#post68301899
Here's a post from him on ZTEUSA
https://community.zteusa.com/message/50425
Here's a blog post he made about it
https://blog.onedefence.com/signed-firehose-images-and-why-theyre-dangerous/?pk_campaign=zte-forums
Click to expand...
Click to collapse
OK, It would be nice if people would inform themselves about this but unfortunately this is the state of XDA now... so here we go
- Firehose is a protocol used to communicate to the qcom chipset directly at a level lower than OS. Since there are security measures in place, in order to talk to it you need a signed firehose withe a coresponding certificate that is burned into the SBL. This is what ZTE uses to directly flash the units at factory and can also be used at repair centers. Tenfar is in possession of such a file and his flasher utilizes it to write modified boot and recovery that would otherwise be discarded by SoC's security protocols. Since it's obfuscated code to hide the firehose plus in addition uses comm libs and code that probably reads and writes other files, it is no wonder it gets flagged by AV software. I had ODIN flagged by Avast once.
- The boot.img is not closed-source, it is actually kernel and ramdisk and can be unpacked so you can see what's inside. It can be compared to stock as well and in fact that is exactly what his are, patched stock boot images. The boot image has been patched in order to allow the modified boot img with root to boot since SecureBoot is still in place due to locked bootloader. In addition is modifies SE Linux to allow root to run. And that brings us to why this tool exists in the first place. It is to allow you to bypass SecureBoot and have root and was created in the period before unlock method was provided by ZTE. It is still the only method to use on non-US model. It is a hack tool by definition and has made development on this phone move ahead way further then it would.
- The security concerns raised were more along the line of how bad it is that the signed firehose is in the wild, not so much to what tenfars tool does or how it does it. The expert even wanted the firehose to be posted on the forum(SMH), which tenfar refused since he did not wanted it to spread and hence obfuscated the code. The signed firehose would present a security vulnerability if someone came in physical contact with your phone since they could dump data or load something on it without your knowledge, as pointed out on the sec blog and other posts, but it has nothing to do with whether you use tenfars tool or not.
- Smart Protect is an API feature that the an AV app would have to use, it exists in the SoC but does nothing on it's own so is irrelevant but i figured i'd clarify it (again)
Most either understand that or don't care. This is the XDA, where we break our warranties and bypass SafetyNet in order to have different emojis Thanks to tenfars tools i have noticed that ZTE has broken the FDE on their stock builds since TWRP was able to decode /data with default password even though it shouldn't. So in my book it's a net plus, at least i know how unsafe it is now.
xtermmin said:
On the US model, you can get an unlocked bootloader & all the trimmings without using tenfar's tool at all, although it's a bit more of a roundabout method.
Click to expand...
Click to collapse
Would that be this method?
http://forum.xda-developers.com/axon-7/how-to/bootloader-unlock-t3437778/page1
And thank you @peramikic for the answer. I've been googling forever on the mbn stuff but never found much on what it exactly is save that it's a manufacturer's tool. This clears up a lot for me. My biggest concern was if an mbn was something that actually rewrites code on the chip itself. Sounds like it's just an external tool a manufacturer uses to put their image onto the phone.
jawz101 said:
Would that be this method?
http://forum.xda-developers.com/axon-7/how-to/bootloader-unlock-t3437778/page1
And thank you @peramikic for the answer. I've been googling forever on the mbn stuff but never found much on what it exactly is save that it's a manufacturer's tool. This clears up a lot for me. My biggest concern was if an mbn was something that actually rewrites code on the chip itself. Sounds like it's just an external tool a manufacturer uses to put their image onto the phone.
Click to expand...
Click to collapse
No problem. The mbn itself is just a file format. In this case it has information about emmc partitions. It is also signed with proper certificate. That let's it talk to the chip and is pretty much just a low lever read/write interface.
As far as that method linked, it will work only if you are on the B20 release, US model only. The file looks for a particular build signature as well as partition signatures so it will not flash on anything else.
peramikic said:
No problem. The mbn itself is just a file format. In this case it has information about emmc partitions. It is also signed with proper certificate. That let's it talk to the chip and is pretty much just a low lever read/write interface.
As far as that method linked, it will work only if you are on the B20 release, US model only. The file looks for a particular build signature as well as partition signatures so it will not flash on anything else.
Click to expand...
Click to collapse
Yeah. At this point I think I'm too lazy to futz with downgrading, patching, then upgrading, and all that. Probably just go with the tenfar tool then 0_o
jawz101 said:
Would that be this method?
http://forum.xda-developers.com/axon-7/how-to/bootloader-unlock-t3437778/page1
Click to expand...
Click to collapse
Yeah, I used that method because I was already on B20, and my PC runs linux so :effort: to setup a Windows VM to use tenfar's tool. Using that (ZTE's official B20_Boot) and ZTE's official B20 image, you can have an unlocked BL and be on B29 without using tenfar's tool.
tl;dr: Whatever version you're on -> B20 -> B20_Boot -> unlock BL -> B20 -> OTA to B27 -> OTA to B29 (-> flash TWRP, SuperSU, whatever)

BLU-VIVO-8 - New Firmware Update: BLU_V0150UU_V7.0.04.02_GENERIC_12-12-2017 03:58

I thought that all would like to know that the new BLU-VIVO-8 has received Yesterday (December 30), a new Firmware update, which updates this phone to the Android Security Patch Level dated: November 5, 2017, and also brings some corrections to the Android Nougat-7 system and Google Play Store update...
As I has noticed that the new Gionee-M7-Power and also other phones, have been launched with the latest Android Nougat v7.1.1 and AMIGO 5.0, that it is the same AMIGO-UI system that the New BLU-VIVO-8 uses...
At first I thought that maybe BLU would surprise all of us with this Android Nougat v7.1.1 + AMIGO-UI 5.0 System, or perhaps with the newer Android-Oreo-8, but unfortunately they were neither, because although this update file has more than 650 MB, it was only for minor corrections and for updating the Android Security Patch to a more recent one.
We need more split ups in various BLU Models. Because this is the forum for the R1 HD.
We need some custom rom for this device
Can any one help?
Has anyone unlocked this bootloader? "Fastboot oem unlock" didn't work for me.
Barthvader said:
Has anyone unlocked this bootloader? "Fastboot oem unlock" didn't work for me.
Click to expand...
Click to collapse
Don't have that phone, but believe I saw others confirm it on a different thread. Don't remember where.
So that leaves questions on your setup.
Does "fastboot devices" confirm you are connected and have drivers installed.
Did you enable oem unlock in developer options?
mrmazak said:
Don't have that phone, but believe I saw others confirm it on a different thread. Don't remember where.
So that leaves questions on your setup.
Does "fastboot devices" confirm you are connected and have drivers installed.
Did you enable oem unlock in developer options?
Click to expand...
Click to collapse
Yes to both of those. I have multiple installs of adb and drivers, etc. So maybe there is a clash somewhere. I know that the Gionee A1 is supposed to be a clone of this phone and those steps should work. I think i am going to try XN Rootkit if trying again on a new fresh pc doesnt work. I would love to hear confirmation from an owner of this phone if there are any around on the steps neccessary to unlock the bootloader.
Barthvader said:
Yes to both of those. I have multiple installs of adb and drivers, etc. So maybe there is a clash somewhere. I know that the Gionee A1 is supposed to be a clone of this phone and those steps should work. I think i am going to try XN Rootkit if trying again on a new fresh pc doesnt work. I would love to hear confirmation from an owner of this phone if there are any around on the steps neccessary to unlock the bootloader.
Click to expand...
Click to collapse
I think maybe I am mistaken.
What i read was for ViVo XL 2
There is forum for VIVO 8L -- but it is different chip so when there device gets root it will be different.
https://forum.xda-developers.com/blu-vivo-8l
Stock Firmware [use for development, unbrick and flashing]
Download Link- http://www.mediafire.com/file/6axy0fifg0ag2pd/Blu_V0150UU_MT6755_V7.0.03.05_REPAIR_T7016.zip
i have take it from here https://romprovider.com/2018/01/install-official-firmware-blu-vivo-8/
BLU_V0150UU_V7.0.04.03_GENERIC_21-03-2018 09:25 need ROM
Please help me i need BLU_V0150UU_V7.0.04.03_GENERIC_21-03-2018 09:25BLU_V0150UU_V7.0.04.03_GENERIC_21-03-2018 09:25
This firmware please give me link

I need help with my U997 (Z?) how to flash stock, etc.

I was happy because I bought a US997 , but then when I was following the tutorial to unlock the bootloader I found that is a weird unespected Z version (which I still don't know what it means or what it is this version)
Well, I want to flash with my pc the stock room again (just to have a clean restart, because I bought it used) it have the 11A but I saw that the 16A is up, the questions are
Can I flash the 16A? How? Where can I download the clean image, etc?
Use the search function...
basicreece said:
Use the search function...
Click to expand...
Click to collapse
Oh wow, it would be amazing if I hadn't used it before made this post.
I can't find anything about the "Z" version of the US997.
Clearly haven't used it correctly then. Also life hack, Google is your friend.
From what I have found, you can't unlock the bootloader on the Z version:
https://forum.xda-developers.com/lg-g6/help/us997-model-bootloader-unlock-supported-t3668594
Where did this phone come from originally? Is it US Cellular?

help blocked at startup htc after update

Hello
I write because following an update yesterday htc u ultra my companion he does not want to start it is blocked on htc and becomes very hot!
I tried several things seen on xda but there I am completely blocked.
I have access to different things, booloader, recoverry, etc ... but nothing changes I did a factory reset but the problem does not evolve
I tried to flash it with a ROM ruu but he told me that it is not the good CID. taken here https://forum.xda-developers.com/u-...stock-htc-ultra-dual-sim-1-64-400-10-t3758077
after i have an idea but i do not know if this is possible i have access to someone who has the same phone bought at the same place at the same time is it possible to extract the RUU rom to reinject it into that of my wife ???
I am hopeless we leave in 8 days and my wife finds herself without phone can you m help me to find the good RUU or extract that of my friend to reinject it?
the model is this one https://www.eglobalcentral.fr/htc-u-ultra-64go-4g-dual-sim-desimlocke-blanc-fr.html
apparently it's a Taiwanese model double sim
thanks for all the help !!
PS it was all original not rooted nor bootloaded unlocked just the update ota do
It would be better if you post the threads links properly, yours got truncated.
If you have, as you claim, the Taiwanese Dual SIM model you should be able to follow the downgrade procedure from Oreo to Nougat. I did it multiple times.
You cannot extract RUU. It is specially prepared package that performs several upgrade operations separately. You can only make dump of already installed system but for that you do need an unlocked bootloader and custom recovery (TWRP) on both devices.
QDT said:
It would be better if you post the threads links properly, yours got truncated.
If you have, as you claim, the Taiwanese Dual SIM model you should be able to follow the downgrade procedure from Oreo to Nougat. I did it multiple times.
You cannot extract RUU. It is specially prepared package that performs several upgrade operations separately. You can only make dump of already installed system but for that you do need an unlocked bootloader and custom recovery (TWRP) on both devices.
Click to expand...
Click to collapse
sorry i corrected the links.
on the other hand I can do this procedure despite that I have access only to bootloader and recovery?
I'm not an expert I thought I can just flash with a RUU but I can not find one
bibou0007 said:
sorry i corrected the links.
on the other hand I can do this procedure despite that I have access only to bootloader and recovery?
I'm not an expert I thought I can just flash with a RUU but I can not find one
Click to expand...
Click to collapse
It seems to me you have got yourself a wrong RUU. The ones from the post are for India, not Taiwan.
Surely I can not get my hands on a Taiwanese RUU!
do you know where can I find a link?
bibou0007 said:
Surely I can not get my hands on a Taiwanese RUU!
do you know where can I find a link?
Click to expand...
Click to collapse
Here is one:
https://androidfilehost.com/?fid=962021903579498986
thank you very much I test his and come tell you!
it does not work it tells me that it's not the right version android I have to find an android 8
thank you
bibou0007 said:
it does not work it tells me that it's not the right version android I have to find an android 8
thank you
Click to expand...
Click to collapse
We don't have RUU 8.0. Try boot to download mode and flash TWRP recovery. Downgrade to Nougat (7.0).

Nokia 6.1 plus - downgrade from android Pie to Oreo? / Flashing stock firmware?

I updated to android Pie on my Nokia 6.1 plus TA-1103. It's too buggy and I don't like it a bit! Downgrading to Oreo "over the air" method via Nokia beta labs doesn't work for my carrier.
I see that official Oreo firmware is available for download. Is there any way to flash it back now when I am currently on Android 9.0 ?
gd91 said:
I updated to android Pie on my Nokia 6.1 plus TA-1103. It's too buggy and I don't like it a bit! Downgrading to Oreo "over the air" method via Nokia beta labs doesn't work for my carrier.
I see that official Oreo firmware is available for download. Is there any way to flash it back now when I am currently on Android 9.0 ?
Click to expand...
Click to collapse
can you provide the link to download official oreo firmware?
vasiulla said:
can you provide the link to download official oreo firmware?
Click to expand...
Click to collapse
I thought these are stock firmwares... https://www.getdroidtips.com/nokia-6-1-plus-stock-firmware/ Maybe I am wrong?
gd91 said:
I thought these are stock firmwares... https://www.getdroidtips.com/nokia-6-1-plus-stock-firmware/ Maybe I am wrong?
Click to expand...
Click to collapse
These are definitely the zips of stock ROM. But these are designed to take you forward and not backward (unless a specially designed package is pushed by the company). So, your only means to downgrade is via Nokia Care channels or paid downgrade services available online.
gd91 said:
I updated to android Pie on my Nokia 6.1 plus TA-1103. It's too buggy and I don't like it a bit! Downgrading to Oreo "over the air" method via Nokia beta labs doesn't work for my carrier.
I see that official Oreo firmware is available for download. Is there any way to flash it back now when I am currently on Android 9.0 ?
Click to expand...
Click to collapse
You can visit any nearest Nokia care centre and ask them to downgrade your phone to oreo. They'll do it
Shraykashyap said:
You can visit any nearest Nokia care centre and ask them to downgrade your phone to oreo. They'll do it
Click to expand...
Click to collapse
Not an option. Nearest Nokia center is way too far from me.
gd91 said:
I updated to android Pie on my Nokia 6.1 plus TA-1103. It's too buggy and I don't like it a bit! Downgrading to Oreo "over the air" method via Nokia beta labs doesn't work for my carrier.
I see that official Oreo firmware is available for download. Is there any way to flash it back now when I am currently on Android 9.0 ?
Click to expand...
Click to collapse
Does anyone have the latest firmware link for the TA-1103?
gd91 said:
Not an option. Nearest Nokia center is way too far from me.
Click to expand...
Click to collapse
Then you will only have the possibility of a paid downgrade.
---------- Post added at 08:54 PM ---------- Previous post was at 08:53 PM ----------
jvictormonteiro said:
Does anyone have the latest firmware link for the TA-1103?
Click to expand...
Click to collapse
It is the same for all WW variants of the device. So, you can flash any WW firmware if your bootloader is unlocked. Otherwise it is not possible to flash on your own.
How to downgrade
gd91 said:
Not an option. Nearest Nokia center is way too far from me.
Click to expand...
Click to collapse
Hi mate, PM me if your bootloader is unlocked and I can go though the steps to downgrade to 8.1
I've been shown how to do it and its tried and tested & working well.
If your bootloader is locked, then search for the paid service to unlock it. He will also downgrade it at the same time.
Nokia X6 with Custom Oreo ROM - How to load stock Android Pie 6.1 plus image
Hi,
I bought a Nokia X6 in September 2018 (6GB/64GB) and would like to install the Stock Nokia 6.1 Plus Android 9 image.
I see my phone is rooted and it shows the message "Your device has loaded a different operating system." everytime I start it and I have to use Magisk to hide several banking applications.
The phone works great and I knew it was going to be relased in Europe eventually, but I am scared to brick it by loading the Android 9 Image.
I already tried attempting the update through OTA but the zip file is ignored. Nothing happens.
I am new to this forum so I don't know if my question has been asked by someone else.
Can you please help me?
Thank you!
- - - Since I am reading that Pie is not that good, I would be happy to stay with Oreo as long as I can use stock and unroot. Have you got any tips for it? ---
mpiulg83 said:
Hi,
I bought a Nokia X6 in September 2018 (6GB/64GB) and would like to install the Stock Nokia 6.1 Plus Android 9 image.
I see my phone is rooted and it shows the message "Your device has loaded a different operating system." everytime I start it and I have to use Magisk to hide several banking applications.
The phone works great and I knew it was going to be relased in Europe eventually, but I am scared to brick it by loading the Android 9 Image.
I already tried attempting the update through OTA but the zip file is ignored. Nothing happens.
I am new to this forum so I don't know if my question has been asked by someone else.
Can you please help me?
Thank you!
- - - Since I am reading that Pie is not that good, I would be happy to stay with Oreo as long as I can use stock and unroot. Have you got any tips for it? ---
Click to expand...
Click to collapse
Strange that the seller has sent you a rooted phone. Anyways, yes, you can install the global version IF your bootloader is unlocked. And that works fine for a few phones I tried it on
singhnsk said:
Strange that the seller has sent you a rooted phone. Anyways, yes, you can install the global version IF your bootloader is unlocked. And that works fine for a few phones I tried it on
Click to expand...
Click to collapse
thank you for coming back to me.
How can I find out if it is unlocked? Also, can you please point me to the right firmware? I have the TA-1099.
I believe the rooted it to install the custom Oreo rom as the Nokia 6.1 Plus had not been released when I purchased the Nokia X6. I actually paid £ 100 less because of this
mpiulg83 said:
thank you for coming back to me.
How can I find out if it is unlocked? Also, can you please point me to the right firmware? I have the TA-1099.
I believe the rooted it to install the custom Oreo rom as the Nokia 6.1 Plus had not been released when I purchased the Nokia X6. I actually paid £ 100 less because of this
Click to expand...
Click to collapse
It won't need root to install a different official ROM. The flash tools for internal usage don't need root.
You can check the device's bootloader status using Fastboot commands. Make sure fastboot drivers are installed. Then put your Nokia in Download mode. After that use the following command:
fastboot oem device-info
Sent from my Nokia 8.1 using XDA Labs
singhnsk said:
It won't need root to install a different official ROM. The flash tools for internal usage don't need root.
You can check the device's bootloader status using Fastboot commands. Make sure fastboot drivers are installed. Then put your Nokia in Download mode. After that use the following command:
fastboot oem device-info
Sent from my Nokia 8.1 using XDA Labs
Click to expand...
Click to collapse
Thanks singhnsk
I downloaded ADB and fastboot, along with the latest Nokia X6 USB Drivers.
I am following the guide here : https://www.getdroidtips.com/nokia-6-1-plus-stock-firmware/#The_Advantage_ofStock_Firmware and I would like to avoid having the original X6 firmware (chinese) and use the 6.1 plus instead, but not sure which one.
Also, what is in your opinion the best XDA post I can follow for the upgrade? Is the one above ok? I just need to unroot my device and install the stock 6.1 Plus Oreo (or Pie if is getting better) making sure it will work with my Vodafone and Three UK Sim Card (which are working fine for now).
Thanks again
mpiulg83 said:
Thanks singhnsk
I downloaded ADB and fastboot, along with the latest Nokia X6 USB Drivers.
I am following the guide here : https://www.getdroidtips.com/nokia-6-1-plus-stock-firmware/#The_Advantage_ofStock_Firmware and I would like to avoid having the original X6 firmware (chinese) and use the 6.1 plus instead, but not sure which one.
Also, what is in your opinion the best XDA post I can follow for the upgrade? Is the one above ok? I just need to unroot my device and install the stock 6.1 Plus Oreo (or Pie if is getting better) making sure it will work with my Vodafone and Three UK Sim Card (which are working fine for now).
Thanks again
Click to expand...
Click to collapse
Actually, it depends on what condition your device is in right now. If the bootloader is unlocked (fastboot oem device-info), then you will be able to install the global firmware.
On the other hand if the device has a locked bootloader, then a tutorial alone won't help. You'll need to buy a remote flashing service to flash the global ROM onto the device. The flash tool needs to gain the flash permission from FIH servers to gain a temporary elevation to flash files to a locked bootloader.
Sent from my Nokia 8.1 using XDA Labs
singhnsk said:
Actually, it depends on what condition your device is in right now. If the bootloader is unlocked (fastboot oem device-info), then you will be able to install the global firmware.
On the other hand if the device has a locked bootloader, then a tutorial alone won't help. You'll need to buy a remote flashing service to flash the global ROM onto the device. The flash tool needs to gain the flash permission from FIH servers to gain a temporary elevation to flash files to a locked bootloader.
Sent from my Nokia 8.1 using XDA Labs
Click to expand...
Click to collapse
Hi,
I followed this guide to go into fastboot mode: https://www.hardreset.info/devices/nokia/nokia-x6-2018/fastboot-mode/
When I do, I can only see "Download mode" on the top left and the big logo "powered by Android", that's it.
Is that correct or?
I allowed my bootloader to be unlocked, for the developer options, but I don't seem to find a way to boot in fastboot mode. I will try volume up + powerbutton shortly.
mpiulg83 said:
Hi,
I followed this guide to go into fastboot mode: https://www.hardreset.info/devices/nokia/nokia-x6-2018/fastboot-mode/
When I do, I can only see "Download mode" on the top left and the big logo "powered by Android", that's it.
Is that correct or?
I allowed my bootloader to be unlocked, for the developer options, but I don't seem to find a way to boot in fastboot mode. I will try volume up + powerbutton shortly.
Click to expand...
Click to collapse
The download mode = fastboot mode. So, you reached the right place.
The developer option setting has no use on a Nokia phone. It just does nothing. But since you're seeing that option, your bootloader is most likely still locked. If you are on July or an older Android Security patch, then you can unlock the bootloader by buyng an unlock key. After that you can unlock it and then flash the global firmware.
Sent from my Nokia 8.1 using XDA Labs
singhnsk said:
The download mode = fastboot mode. So, you reached the right place.
The developer option setting has no use on a Nokia phone. It just does nothing. But since you're seeing that option, your bootloader is most likely still locked. If you are on July or an older Android Security patch, then you can unlock the bootloader by buyng an unlock key. After that you can unlock it and then flash the global firmware.
Sent from my Nokia 8.1 using XDA Labs
Click to expand...
Click to collapse
Hi, yes I think so at this point. I am on May security patch and it does not show any new updates when I check. I am thinking to unroot it at this point and keep it with Android 8.1 unrooted, but I am not sure I will get the updates from Nokia.
What do you think?
Thanks for your reply and I hope all this information is useful to the other members of the forum.
Update: I just bought the unlock code and waiting for it. I will let you know how it goes.
Downgrade from Android 9 to Android 8
Hello!
I downloaded this file: https :// drive.google.com/uc?id=1BUR6xrbgbVlMQDyHz6oXZpmPrlRuFYgY&export=download
from this forum: http: // forum.gsmdevelopers.com/nokia-android-phones/72857-nokia-6-1-plus-ta-1083-exclusive-tasted-firmware-ch_sameer.html
and apparently it's possible to downgrade from Android 9 to Android 8. The file contains the OST LA program and the stock ROM for TA-1083 (DRG-237B-0-00WW-B05) in .nb0 format. The program asks for user and password, but I read somewhere that it's possible to patch it or edit it with Notepad++. I'm new to this and I don't know how to use the program.
Can someone more experienced test this method and report back, please?
marcellesilva said:
Hello!
I downloaded this file: https :// drive.google.com/uc?id=1BUR6xrbgbVlMQDyHz6oXZpmPrlRuFYgY&export=download
from this forum: http: // forum.gsmdevelopers.com/nokia-android-phones/72857-nokia-6-1-plus-ta-1083-exclusive-tasted-firmware-ch_sameer.html
and apparently it's possible to downgrade from Android 9 to Android 8. The file contains the OST LA program and the stock ROM for TA-1083 (DRG-237B-0-00WW-B05) in .nb0 format. The program asks for user and password, but I read somewhere that it's possible to patch it or edit it with Notepad++. I'm new to this and I don't know how to use the program.
Can someone more experienced test this method and report back, please?
Click to expand...
Click to collapse
You cannot crack/patch OST LA. The patched version will work on bootloader unlocked devices only. For the others, there's no way to flash without having the login to server with account.
Sent from my Nokia 8.1

Categories

Resources