Database Users

No Updates at all

Hi all,
I just recently went back to complete stock, from CM, as I want to hand it over to a friend.
I successfully switched back to C432B160 last week.
But still not a single update does show up, though that build is from November 2016.
It always tells me, that there are no updates. I am aware that Updates will show up with Hisuite, but shouldn't the stock updater present updates, too?
(I am not even talking about Nougat)
I already successfully tried a factory reset.
The only idee I have, is that I now have a DS oeminfo on an originally SS phone.
Does anyone have an idee, what might be wrong?

fireburner-de said:
Hi all,
I just recently went back to complete stock, from CM, as I want to hand it over to a friend.
I successfully switched back to C432B160 last week.
But still not a single update does show up, though that build is from November 2016.
It always tells me, that there are no updates. I am aware that Updates will show up with Hisuite, but shouldn't the stock updater present updates, too?
(I am not even talking about Nougat)
I already successfully tried a factory reset.
The only idee I have, is that I now have a DS oeminfo on an originally SS phone.
Does anyone have an idee, what might be wrong?
Click to expand...
Click to collapse
well, if you have ds oeminfo while your phone is ss, try flashing ss oeminfo and then the stock rom again

mjz2cool said:
well, if you have ds oeminfo while your phone is ss, try flashing ss oeminfo and then the stock rom again
Click to expand...
Click to collapse
Well the phone was SS at the beginning, but now I have oeminfo for DS and Stock Rom for DS (B160)

I wiped all and completely new flashed B160.
I did not setup any account (Google, Huawei), but only connected the phone to my WIFI.
Still neither Update nor HiCare show any available updates.
Does this need a SIM Card to be in the phone? Are there any other precautions?
I have no idea why it behaves like this.
edit: both frp and bootloader are locked according to the Bootloader Menu
I might add 2 weeks ago when coming from CM, there were no updates in update menu but HiCare, so I went fo Nougat. Nougat did not work properly, so I went back to B160 in order to start again, but since then, I never saw any update in menu, nor HiCare.
Might Huawei block DS Roms for IMEIS of originally SS phones?

Push, maybe @k1ll3r8e has an answer for me?

fireburner-de said:
Push, maybe @k1ll3r8e has an answer for me?
Click to expand...
Click to collapse
Heyho,
sounds really wired...
-
Here is what u can try,
1) bring the device back to stock (unrooted, loader closed)
2) do a factory reset and also the cache clear which is offered in the stock recovery
-
Start the device, do a dummy setup (only wlan is needed) check if the device offers an update. If not, well, try to manually update from C432B160 to C432B210 and check the update app again.
About this issue, i'm not sure, but maybe Huawei have a "downlaod limit" for an IMEI, that u can only download the update for example 10 times or so... I don't know^^ - I can only say, my device "L31 - Single-SIM - T-Mobile" modded to C432B380 dual-SIM have no issues with updates... I got since B130 every update via the normal update app. - But i also know that the updates will be released in waves, i don't know how they exclude/include devices in such an wave. But maybe, u have an oeminfo from an device which wasn't in the "current wave list". - As already mentioned i don't know how they manage those waves or what the trigger is...
Hope i could help u a bit
Regards
Sebastian

fireburner-de said:
I wiped all and completely new flashed B160.
I did not setup any account (Google, Huawei), but only connected the phone to my WIFI.
Still neither Update nor HiCare show any available updates.
Does this need a SIM Card to be in the phone? Are there any other precautions?
I have no idea why it behaves like this.
edit: both frp and bootloader are locked according to the Bootloader Menu
I might add 2 weeks ago when coming from CM, there were no updates in update menu but HiCare, so I went fo Nougat. Nougat did not work properly, so I went back to B160 in order to start again, but since then, I never saw any update in menu, nor HiCare.
Might Huawei block DS Roms for IMEIS of originally SS phones?
Click to expand...
Click to collapse
So, did you try upgrade on N using Firmware finder?
If not, try it and you will see if your device in black list. I also use DS firmware for SS model and just last night I upgraded normaly from B160 to B370 Ota, and after that to B380 Ota.

@k1ll3r8e
Yes it already is a dummy setup. I will manually upgrade to B210 and try again, Thanks alot! @Alexxxx1
Firmware Finder is the Windows tool, isn't it? If above progress won't work I might boot my Windows partition and check on that.
Is there by chance any other way to check if the device is somehow blacklisted?
@all
Would Huawei push the updates to my device, if I would contact them? (I ask because of the altered oeminfo. Or would the refuse support in that case, which is what I guess)
edit: Does by chance anyone have a link to the C432B210 ROM?

fireburner-de said:
@k1ll3r8e
Yes it already is a dummy setup. I will manually upgrade to B210 and try again, Thanks alot! @Alexxxx1
Firmware Finder is the Windows tool, isn't it? If above progress won't work I might boot my Windows partition and check on that.
Is there by chance any other way to check if the device is somehow blacklisted?
@all
Would Huawei push the updates to my device, if I would contact them? (I ask because of the altered oeminfo. Or would the refuse support in that case, which is what I guess)
edit: Does by chance anyone have a link to the C432B210 ROM?
Click to expand...
Click to collapse
Heyho,
if u have an L31, go to my FTP (oeminfo) and go a few folders back, then u'll find a Huawei folder there are several versions stored.
Edit:
Here is the link (just back on my PC)
Regards,
Sebastian
Sent from my HUAWEI VNS-L31 using XDA Labs

Firmware finder is android app. You can find it in google play store as a free tool for upgrade huawei devices. In Ffinder you will find option for checking autorization of official firmware for your device, is it allowed or not for your device.
Regards

I did flash B210, but no Updates withiin 1 day. (I think time was to short)
I then flashed B370 Full-PV via Firmware Finder.
B380 should come automatically sometime, hopefully.
I think its time to hand it over to my friend now.
Only thing I am curious about is:
settings -> about phone -> certification: Serbia
I guess this is normal for C432?

Only thing I am curious about is:
settings -> about phone -> certification: Serbia
I guess this is normal for C432?
Click to expand...
Click to collapse
Yes, its normally for C432 if device was purchased in Serbia

Alexxxx1 said:
Yes, its normally for C432 if device was purchased in Serbia
Click to expand...
Click to collapse
It was bought from T-Mobile in Germany. But well.

fireburner-de said:
It was bought from T-Mobile in Germany. But well.
Click to expand...
Click to collapse
No worries about that
I bought mine also from T-Mobile DE, and mine shows also "Serbia"... I searched a bit for similar issues and it seems that also the P8 with C432 is for "Serbia" at least a unknown amount of it, sooo i think it comes from the "ROM" not from the device. Maybe they only certify the ROM for a "law based standart" to "Serbia". - Who knows...^^
Regards,
Sebastian

ATTENTION!Help needed to revive phone

I downgraded to marshmallow and I tried to update to nougat through the official way. It was updating for some time and then screen went off. I tried turning it on with no avail. I had latest bootloader which was unlocked.
Please help guys
I beg you

CMKdaGreatest said:
I downgraded to marshmallow and I tried to update to nougat through the official way. It was updating for some time and then screen went off. I tried turning it on with no avail. I had latest bootloader which was unlocked.
Please help guys
I beg you
Click to expand...
Click to collapse
Seems you bricked your phone by downgrade the bootloader...
Did you tried to follow the unbrick guide here https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Otherwise please provide on which rom version you are before downgrade to marshmallow and also the device type you have.
I'm sure @echo92 will help further :good:

strongst said:
Seems you bricked your phone by downgrade the bootloader...
Did you tried to follow the unbrick guide here https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Otherwise please provide on which rom version you are before downgrade to marshmallow and also the device type you have.
I'm sure @echo92 will help further :good:
Click to expand...
Click to collapse
Downgraded from stock nougat to stock marshmallow and tried OTAing back to nougat

CMKdaGreatest said:
Downgraded from stock nougat to stock marshmallow and tried OTAing back to nougat
Click to expand...
Click to collapse
Which stock nougat rom and which marshmallow rom. The versions. And did you tried the unbrick guide?

I tried the unbrick guide. I flashed the blank flash and got a dummy bootloader but I can't flash gpt or bootloader. It always shows failed. How should I do it?

strongst said:
Which stock nougat rom and which marshmallow rom. The versions. And did you tried the unbrick guide?
Click to expand...
Click to collapse
I used this guide. In the third page there's a post containing a blank flash attached. I flashed that but can't flash gpt or bootloader

CMKdaGreatest said:
I used this guide. In the third page there's a post containing a blank flash attached. I flashed that but can't flash gpt or bootloader
Click to expand...
Click to collapse
Can you link the post which you got the blankflash from?
In this post you'll find the latest athene blankflash and the December 2017 GPT/bootloader. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
The December 2017 GPT/bootloader files are here https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80 and I pulled them from the NPJS25.93-14-13 stock ROM.
As an aside, you cannot safely downgrade and use OTA updates. If you downgrade, only use stock firmware to update. You cannot downgrade bootloaders and thus using older OTA updates on your device corrupts your bootloader.

echo92 said:
Can you link the post which you got the blankflash from?
In this post you'll find the latest athene blankflash and the December 2017 GPT/bootloader. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
The December 2017 GPT/bootloader files are here https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80 and I pulled them from the NPJS25.93-14-13 stock ROM.
As an aside, you cannot safely downgrade and use OTA updates. If you downgrade, only use stock firmware to update. You cannot downgrade bootloaders and thus using older OTA updates on your device corrupts your bootloader.
Click to expand...
Click to collapse
Thank you so much man. Much appreciated

echo92 said:
Can you link the post which you got the blankflash from?
In this post you'll find the latest athene blankflash and the December 2017 GPT/bootloader. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
The December 2017 GPT/bootloader files are here https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80 and I pulled them from the NPJS25.93-14-13 stock ROM.
As an aside, you cannot safely downgrade and use OTA updates. If you downgrade, only use stock firmware to update. You cannot downgrade bootloaders and thus using older OTA updates on your device corrupts your bootloader.
Click to expand...
Click to collapse
I already flashed a blank flash. How do I flash another one??

CMKdaGreatest said:
I already flashed a blank flash. How do I flash another one??
Click to expand...
Click to collapse
You won't be able to flash another blankflash unless your device is in the Qualcomm HS-USB 9008 mode again (in other words, you hard bricked by corrupting your bootloader again).
I'm hoping as whatever blankflash you used worked properly and thus you shouldn't have issues flashing the latest firmware. However, they can overwrite a damaged bootloader with the dummy bootloader, and as such you need to verify you're flashing the correct blankflash. The inbuilt checks should stop you from flashing the wrong blankflash however.
If you still want to revert back to Marshmallow, then do not use OTA updates at all.
As an aside, do not always depend on these blankflashes, Motorola is updating the bootloader with every firmware release and there's always a chance the blankflashes may not work anymore. We're not supposed to have these blankflashes (leaks from generous engineers are our source) and so we don't know if we can get another one should the current blankflash stop working.

echo92 said:
You won't be able to flash another blankflash unless your device is in the Qualcomm HS-USB 9008 mode again (in other words, you hard bricked by corrupting your bootloader again).
I'm hoping as whatever blankflash you used worked properly and thus you shouldn't have issues flashing the latest firmware. However, they can overwrite a damaged bootloader with the dummy bootloader, and as such you need to verify you're flashing the correct blankflash. The inbuilt checks should stop you from flashing the wrong blankflash however.
If you still want to revert back to Marshmallow, then do not use OTA updates at all.
As an aside, do not always depend on these blankflashes, Motorola is updating the bootloader with every firmware release and there's always a chance the blankflashes may not work anymore. We're not supposed to have these blankflashes (leaks from generous engineers are our source) and so we don't know if we can get another one should the current blankflash stop working.
Click to expand...
Click to collapse
It worked. After the bootup, I received an update. I updates my phone and it successfully booted up. I received another update. Now, after this, its back to the same condition. Why is this happening?

Can you give me links for the firmware too if you don't mind? I need the Indian version for XT1643. Dont mind me man, I'm still in 9th grade

CMKdaGreatest said:
It worked. After the bootup, I received an update. I updates my phone and it successfully booted up. I received another update. Now, after this, its back to the same condition. Why is this happening?
Click to expand...
Click to collapse
CMKdaGreatest said:
Can you give me links for the firmware too if you don't mind? I need the Indian version for XT1643. Dont mind me man, I'm still in 9th grade
Click to expand...
Click to collapse
Did you re-flash the latest firmware? https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 For NPJS25.93-14-13 (Nougat, Dec 2017 build)
If not, then your device is still with a mismatched bootloader and system - you have the December 2017 bootloader but the much older Marshmallow system. That means any OTA update you take may well keep hard bricking your device unless you re-flash your device to have firmware of the same patch level (bootloader and system). Then, you should be okay to take OTA updates.
This is the major problem with downgrading - OTA updates have the ability to overwrite your bootloader without checking first if your bootloader is the same patch level as your system. As you've downgraded, this is likely why older OTA updates brick.
Un-brick your device then use the flashing instructions here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 with the latest NPJS25.93-14-13 firmware. Do not use/install OTA updates until you've re-flashed the latest stock firmware.

echo92 said:
Did you re-flash the latest firmware? https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 For NPJS25.93-14-13 (Nougat, Dec 2017 build)
If not, then your device is still with a mismatched bootloader and system - you have the December 2017 bootloader but the much older Marshmallow system. That means any OTA update you take may well keep hard bricking your device unless you re-flash your device to have firmware of the same patch level (bootloader and system). Then, you should be okay to take OTA updates.
This is the major problem with downgrading - OTA updates have the ability to overwrite your bootloader without checking first if your bootloader is the same patch level as your system. As you've downgraded, this is likely why older OTA updates brick.
Un-brick your device then use the flashing instructions here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 with the latest NPJS25.93-14-13 firmware. Do not use/install OTA updates until you've re-flashed the latest stock firmware.
Click to expand...
Click to collapse
The first link in your last post, does it have latest firmware? I reflashed the may or march 2016 firmware after the blank flash, I don't remember which

CMKdaGreatest said:
Can you give me link to latest firmware?
Click to expand...
Click to collapse
The link to the latest firmware was the first link I gave you in my previous reply... NPJS25.93-14-13 is the latest stock ROM for India, Brazil and EU devices.
Yeah, flashing the May 2016 or March 2016 firmware really won't help you - again, as your bootloader is December 2017 flashing older firmware and attempting to take OTA updates will just keep hard bricking you until you reflash the December 2017 firmware, or if you do not use OTA updates. You cannot downgrade bootloaders usually.

echo92 said:
The link to the latest firmware was the first link I gave you in my previous reply... NPJS25.93-14-13 is the latest stock ROM for India, Brazil and EU devices.
Yeah, flashing the May 2016 or March 2016 firmware really won't help you - again, as your bootloader is December 2017 flashing older firmware and attempting to take OTA updates will just keep hard bricking you until you reflash the December 2017 firmware, or if you do not use OTA updates. You cannot downgrade bootloaders usually.
Click to expand...
Click to collapse
Yea I'll try tomorrow man. Thanks a ton!! The method of blank flash is the same right?? If it doesnt work then what should I do??

CMKdaGreatest said:
Yea I'll try tomorrow man. Thanks a ton!! The method of blank flash is the same right?? If it doesnt work then what should I do??
Click to expand...
Click to collapse
Should be, please use the latest athene blankflash in the Unbrick guide: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 and the latest stock ROM as mentioned. I would also advise deleting any old stock ROMs - Marshmallow or Nougat - on your computer, unless you are confident you will not use OTA updates whilst downgraded. Motorola and other OEMs appear to have not designed protections into their updates for downgraded devices (and assume that you've taken responsibility ever since you unlocked your bootloader).
If this doesn't work, then you'll either have to wait for another newer blankflash to be leaked (perhaps when we get the Oreo update, but again, it's by chance whether we get another blankflash), or be willing to pay for a motherboard replacement. A motherboard replacement appears to be in the range of 7000-10000 rupees or your regional equivalent.

echo92 said:
Should be, please use the latest athene blankflash in the Unbrick guide: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 and the latest stock ROM as mentioned. I would also advise deleting any old stock ROMs - Marshmallow or Nougat - on your computer, unless you are confident you will not use OTA updates whilst downgraded. Motorola and other OEMs appear to have not designed protections into their updates for downgraded devices (and assume that you've taken responsibility ever since you unlocked your bootloader).
If this doesn't work, then you'll either have to wait for another newer blankflash to be leaked (perhaps when we get the Oreo update, but again, it's by chance whether we get another blankflash), or be willing to pay for a motherboard replacement. A motherboard replacement appears to be in the range of 7000-10000 rupees or your regional equivalent.
Click to expand...
Click to collapse
I'm just curious to know what happens if we flash an old blank flash.

CMKdaGreatest said:
I'm just curious to know what happens if we flash an old blank flash.
Click to expand...
Click to collapse
Depends - if it's an old blankflash for our device (for Snapdragon 617, MSM8952), it'll likely fail as the blankflash, in communicating with the device's bootloader, determines the blankflash is too old to repair the bootloader. Blankflashes appear to send a programmer over to your device which verifies that your device bootloader is not newer than the blankflash, else you'd be downgrading your bootloader and possibly causing a security issue. Thus, your device may not be rescued and require a new motherboard. We saw plenty of these incidents when users downgraded to Marshmallow from Nougat 6 months ago and then tried to use OTA updates, and it was only with the leak of a newer bootloader version B1:06 compatible blankflash that people were able to rescue their devices without spending a lot of money. Without that blankflash, I think we have very limited means of rescue. We cannot make these blankflashes as they have to be cryptographically signed and built by OEMs like Motorola, I think to maintain the bootloader security, as such we do not know if we'll get a new one. In theory, we could make a loader image - a complete image of a working device - to try to bypass the bootloader corruption without needing a blankflash. That has had some success on other devices, but hopefully you should need neither a blankflash nor a loader image.
We've seen instances of other Moto devices' blankflashes rescuing devices (e.g. Moto Z2 Play rescuing Moto Z Play and G5 Plus), however, their CPUs are very similar. Our Snapdragon 617 is not used by any other Motorola device, so we have a very limited source of blankflashes.
I would hope blankflashes are in general well programmed enough to not flash onto devices they are not meant to flash onto, else if they could flash onto a different device, you could really screw up your device.
In summary, an older blankflash likely just won't work, and you'd either have to wait for a newer blankflash or pay for an expensive repair. Unless you are willing to do either, I would be very careful in future with downgrading.

echo92 said:
Depends - if it's an old blankflash for our device (for Snapdragon 617, MSM8952), it'll likely fail as the blankflash, in communicating with the device's bootloader, determines the blankflash is too old to repair the bootloader. Blankflashes appear to send a programmer over to your device which verifies that your device bootloader is not newer than the blankflash, else you'd be downgrading your bootloader and possibly causing a security issue. Thus, your device may not be rescued and require a new motherboard. We saw plenty of these incidents when users downgraded to Marshmallow from Nougat 6 months ago and then tried to use OTA updates, and it was only with the leak of a newer bootloader version B1:06 compatible blankflash that people were able to rescue their devices without spending a lot of money. Without that blankflash, I think we have very limited means of rescue. We cannot make these blankflashes as they have to be cryptographically signed and built by OEMs like Motorola, I think to maintain the bootloader security, as such we do not know if we'll get a new one. In theory, we could make a loader image - a complete image of a working device - to try to bypass the bootloader corruption without needing a blankflash. That has had some success on other devices, but hopefully you should need neither a blankflash nor a loader image.
We've seen instances of other Moto devices' blankflashes rescuing devices (e.g. Moto Z2 Play rescuing Moto Z Play and G5 Plus), however, their CPUs are very similar. Our Snapdragon 617 is not used by any other Motorola device, so we have a very limited source of blankflashes.
I would hope blankflashes are in general well programmed enough to not flash onto devices they are not meant to flash onto, else if they could flash onto a different device, you could really screw up your device.
In summary, an older blankflash likely just won't work, and you'd either have to wait for a newer blankflash or pay for an expensive repair. Unless you are willing to do either, I would be very careful in future with downgrading.
Click to expand...
Click to collapse
It worked!! Thank you so much. Now it's perfect!!

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).

Huawei P smart FIG-LX1 how to root without unlocking bootloader

Hi XDA, since huawei doesn't provide the bootloader unlock codes anymore and dc-unlocker doesn't support my FIG-LX1. I'm looking for a way to just boot into twrp and install root from there or lineage os from the project treble thread. I read somewhere that you can do that with fastboot but I'm not sure. Any concrete answers to this?

Not possible afaik

..

sun75 said:
I unlocked exactly the FIG-LX1 (L31 board) last July using DC-Unlocker Service with no problems at all. The only one problem... it's not free: you have to pay €4 (or 4 credits, it's the same for my country..., I don't know in other countries).
---
EDIT:
Yes, Dc-unlocker does not natively support fig-lx1 in the Huawei phone list, BUT have you connected it in fastboot mode? (see attached jpeg...).
Click to expand...
Click to collapse
Just to update folks who see this DC unlocker does not unlock bootloader if you are running Android 8 like me. If you have paid they will refund. As they just did for me.

..

sun75 said:
I was on Android 8 also, and I unlocked it with no problems at all in minutes with DC-Unlocker. You have to "read" the boot code with the client (after paying, instructions on their website) and unlock it with few adb commands! Nothing else!
Click to expand...
Click to collapse
So why does their app say if you on android 8 and get error 375 they will instantly refund. Was you on August security patch? Even on their live chat support they said in person right now there is nothing they can do and they will notify me when it changes.
---------- Post added at 06:44 PM ---------- Previous post was at 06:33 PM ----------
sun75 said:
I unlocked exactly the FIG-LX1 (L31 board) last July using DC-Unlocker Service with no problems at all. The only one problem... it's not free: you have to pay €4 (or 4 credits, it's the same for my country..., I don't know in other countries).
---
EDIT:
Yes, Dc-unlocker does not natively support fig-lx1 in the Huawei phone list, BUT have you connected it in fastboot mode? (see attached jpeg...).
Click to expand...
Click to collapse
Yes it wouldn't recognise my device once in fastboot mode, the Huawei suite works when device on and adb but not the dc unlocker. Just incase I am wrong which is highly possible: could you explain the process? Please
I connect device go to server and it said I paid
Press read device and it shows which port I'm connected to.
Then I entered device into manufacturer mode and pressed get bootloader code.
Then I got error 375
---------- Post added at 05:58 PM ---------- Previous post was at 05:44 PM ----------
sun75 said:
I was on Android 8 also, and I unlocked it with no problems at all in minutes with DC-Unlocker. You have to "read" the boot code with the client (after paying, instructions on their website) and unlock it with few adb commands! Nothing else!
Click to expand...
Click to collapse
So are you enjoying benefits of root or are you using custom roms?

..

sun75 said:
Ok, your procedure is the same I did.
The only diff is I immediately uninstalled Huawei Suite (maintaining the drivers it installs!) because it interferes with DC-Unlocker and with adb.
I unlocked my phone on 14/8/2018, and I was on .146 C432, which, if I remember well, is the July update.
I never tried before(I regularly upgrade/downgrade via HuRu), but, can you downgrade your phone to .146 (or whatever is the July release of your "brand") via the stock ERecovery?
Maybe they fixed something between the two releases, because I got the unlock code in minutes and you get the error...
I'm very sad for you and I apologize for the posts before... if this is the case: I wish you can downgrade in some way!
Click to expand...
Click to collapse
Oh dude nice message! All good here mostly wanted to debloat which I have done now without root. I'm really happy with this device. The only other reason why I'd want root is to change mixer path values get louder phone and speaker. I got a refund from dc so all good for now. I take your advice and look into downgrade. Also there doesn't seem to be much development in here for this device? Are you on custom rom?
And thanks for your response

..

sun75 said:
Initially yes: all the OpenKirin's Roms, after most Treble Roms. But now I'm back to "Stock" + my ultradebloat script + Magisk and JamesDSP audio module. I think this is the most stable combination free of unwanted apps, at least for now!
For "development", any Treble Rom "type A" is good for our P Smart, so our development is elsewhere:
https://forum.xda-developers.com/project-treble
Click to expand...
Click to collapse
Do you have twrp or stock recovery?
I just came from moto G5 was flashing all day but once oreo got released it was bad news as moto didn't make it 64bit. Custom roms were incomplete broken camera etc serious lack of community and development, everyone was was excited to get back to stock. I'm loving this psmart!

..

Edited since irrelevant because of not unlockable bootloader.

sun75 said:
I unlocked exactly the FIG-LX1 (L31 board) last July using DC-Unlocker Service with no problems at all. The only one problem... it's not free: you have to pay €4 (or 4 credits, it's the same for my country..., I don't know in other countries).
---
EDIT:
Yes, Dc-unlocker does not natively support fig-lx1 in the Huawei phone list, BUT have you connected it in fastboot mode? (see attached jpeg...).
Click to expand...
Click to collapse
Can you help me to get bootloader unlock code please? I did connect in fastboot mode but there isn't any option to read bootloader unlock code. I have 5 credits in DC Unlocker

..

sun75 said:
I unlocked exactly the FIG-LX1 (L31 board) last July using DC-Unlocker Service with no problems at all. The only one problem... it's not free: you have to pay €4 (or 4 credits, it's the same for my country..., I don't know in other countries).
---
EDIT:
Yes, Dc-unlocker does not natively support fig-lx1 in the Huawei phone list, BUT have you connected it in fastboot mode? (see attached jpeg...).
Click to expand...
Click to collapse
Well took the advivce but can't get dc unlock to run cost £3.70 to buy credits it doesn't even detect unlocked usb manufacture mode from keypad press method in guide in window, chose auto detect for huwaei phone in fastboot mode tried multiple ways, including huwaei phones auto detect and it doesn't detect it?
Can you explain your exact options you used please?

[
If you are on August 2018 update or newer, it seems that Huawei has patched the BL forever, so they are out of games... for now!
In that case, you can try to request a refund![/QUOTE]
you can downgrade with firmware finder &dns to unlockable version ....so said one guy who says he could downgrade
......

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