Hello everyone..
I was @ Android 8 then i flash rom 8.1 bootloader still locked not rooted
Model xt1900-7 the software channel reteu
So wat i ask for is by flashing other updated rom means I lost OTA & if so how to fix that & get OTA again?
Yes, you lost your OTA. The only way to updating is flashing official zips via ADB.
Noway to fix that??
No - and that's why you don't flash this phone if you want to keep it stock. Or don't flash it all.
---------- Post added at 07:26 PM ---------- Previous post was at 07:25 PM ----------
On practical side - live with it or try Lineage.
H4x0r1337 said:
Hello everyone..
I was @ Android 8 then i flash rom 8.1 bootloader still locked not rooted
Model xt1900-7 the software channel reteu
So wat i ask for is by flashing other updated rom means I lost OTA & if so how to fix that & get OTA again?
Click to expand...
Click to collapse
Is your bootloader unlocked?
The only ROMs that I have seen for this phone are for North American models- Amazon, Fi, and retail US.
If you can find a leaked ROM for your phone, you should be able to flash back to stock and receive OTAs again.
gee one said:
Is your bootloader unlocked?
The only ROMs that I have seen for this phone are for North American models- Amazon, Fi, and retail US.
If you can find a leaked ROM for your phone, you should be able to flash back to stock and receive OTAs again.
Click to expand...
Click to collapse
No bootloader locked..even so am not rooted..
H4x0r1337 said:
No bootloader locked..even so am not rooted..
Click to expand...
Click to collapse
OTAs from reteu channel require previous reteu ROM version. It means correct previous Blur_Version. OTA update from retus Blur_Version is impossible to reteu Blur_Version.
For example, "Blur_Version.27.301.32.payton.retail.en.US" (October 2018 reteu OTA) requires previous "Blur_Version.27.281.28.payton.retail.en.US" (August 2018 reteu OTA).
If you want get OTA again, you have to flash correct reteu fastboot ROM (OPWS27.57-40-22 = "Blur_Version.27.281.28.payton.retail.en.US" could work).
You have to unlock bootloader, because flash from 8.1 retus to 8.0 reteu is downgrade and downgrade is impossible with locked bootloader..
Comby_sk said:
OTAs from reteu channel require previous reteu ROM version. It means correct previous Blur_Version. OTA update from retus Blur_Version is impossible to reteu Blur_Version.
For example, "Blur_Version.27.301.32.payton.retail.en.US" (October 2018 reteu OTA) requires previous "Blur_Version.27.281.28.payton.retail.en.US" (August 2018 reteu OTA).
If you want get OTA again, you have to flash correct reteu fastboot ROM (OPWS27.57-40-22 = "Blur_Version.27.281.28.payton.retail.en.US" could work).
You have to unlock bootloader, because flash from 8.1 retus to 8.0 reteu is downgrade and downgrade is impossible with locked bootloader..
Click to expand...
Click to collapse
So if I flash Android pie once it release will that make me back to OTA?
H4x0r1337 said:
So if I flash Android pie once it release will that make me back to OTA?
Click to expand...
Click to collapse
Yes, if Pie (fastboot rom) will be compatible with reteu channel.
Related
I always thought that an open bootloader means no OTA any more, but my XT1900-7 reteu device just received an OTA after a full flash/data wipe.
So I was wrong. Does unlocked bootloader and non-rooted mean OTAs work just fine?
I have flashed XT1900-1_PAYTON_RETAIL_8.0.0_OPWS27.57-40-22_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml. Now the phone is on OPWS27.57-40-25, Android 8.0, patch level October 2018. It still is a XT1900-7 reteu.
:good:
I have the XT1900-1 android one version. Before unlocking my bootloader, I had the December 2018 security update. I unlocked my bootloader to get lineageOS, but decided to go back to stock using muchy_cool's guide. But now the security patches are going up to November 2018, and then it says its up to date.
Is there a difference between the stock firmware from the guide and the stock firmware upon buying the phone? I would assume so because if I relock the bootloader again, the warning message on boot changes to "device has loaded a different operating system". But then this is still stock firmware. Why don't the updates get detected?
Paximonium said:
I have the XT1900-1 android one version. Before unlocking my bootloader, I had the December 2018 security update. I unlocked my bootloader to get lineageOS, but decided to go back to stock using muchy_cool's guide. But now the security patches are going up to November 2018, and then it says its up to date.
Is there a difference between the stock firmware from the guide and the stock firmware upon buying the phone? I would assume so because if I relock the bootloader again, the warning message on boot changes to "device has loaded a different operating system". But then this is still stock firmware. Why don't the updates get detected?
Click to expand...
Click to collapse
Well it sounds like the OTAs ARE working if you're still on the November update. (My non-Pie phone is still on October update and Android 8.0)
It sounds like you just haven't gotten the December update yet. So did you first get September, October, and November?
As I am aware, even if you got the update it will fail at the moment of installation. There is no official stock recovery available so far that's why even if you lock the bootloader you are using the modified system warning shows at the time of booting.
Hi, I've got a dual-sim moto g6 (xt1925-5). I see that software channels such as reteu or retail have more recent Pie updates whilst retgb last Pie update was PPS29.55.24. I know that because my phone is rooted with unlocked bootloader and twrp, I would not get OTA updates. But from what I've read I could flash any updates from retail or reteu using RSDLite.
So I'm wondering if I would loose any functionalities or have any drawbacks by switching away from retgb ? any recommendation as to either move to reteu or retail ?
Thanks.
bump...
So I flashed the latest reteu I could find (PPS29.55-37-4) using fastboot and keeping user data. It went smoothly (only got an bad key error for the bootloader img, which was expected with unlocked bootloader). Reflashed twrp / disable_dm / magisk before the first boot. Phone rebooted and working fine.
Settings shows the right build but I'm still on retgb somehow. I expected to see reteu, any ideas ? Something I did wrong ?
Sorted, found it in /data/system/users/0/mot_settings_global.xml
Is it possible to downgrade to older firmware? At the moment I have this years September patch. Without rooting or unlocking if possible.
vbaros said:
Is it possible to downgrade to older firmware? At the moment I have this years September patch. Without rooting or unlocking if possible.
Click to expand...
Click to collapse
Every few months samsung will update the bootloader along with the firmware. You can only downgrade to an older firmware so long as it has the same bootloader version as what you are currently running. Not possible to downgrade bootloader even with root unfortunately.
Philnicolls89 said:
You can only downgrade to an older firmware so long as it has the same bootloader version as what you are currently running. Not possible to downgrade bootloader even with root unfortunately.
Click to expand...
Click to collapse
Is there a list of firmwares where you can see the bootloader version?
vbaros said:
Is there a list of firmwares where you can see the bootloader version?
Click to expand...
Click to collapse
The bootloader version number is written in the firmware version. Go to sammobile and browse the firmwares for your phone model to compare.
Example:
The latest October firmware for my s10+ is G975FXXS9DTI8. The '9' before the DTI8 represents the bootloader.
Im currently on the September firmware which is G975FXXU8DTH7. The '8' before the DTH7 represents the bootloader.
So when I decide to update, there will be no going back.
Hope this helps
Hello guys.
So I recently got a phone that's stuck with the August 2021 security patch. I wanna flash the latest software so had 2 questions:
1. Should I flash the most recent software update or considering I've never actually updated my phone, should I flash all the previous updates from August first before I flash the latest one.
2. I wanted to know if anyone has experience flashing SM-G998U1 firmware on a SM-G998U phone. I heard you can flash "U1" or carrier unlocked firmware on a "U" or carrier locked phone. Just that you'd lose all your data. I have an SM-G998U locked to Verizon and since I'm not in the US Verizon says they can't unlock it for me. So my only option is to flash new firmware updates. But I can't for the life of me find any Verizon SM-G998U firmware from after August 2021 (that's my latest security patch) online. So wanted to hear from anyone with experience that's flashed "U1" firmware on a "U" phone.
Flashing FW is no solution to unlock phones.
OnnoJ said:
Flashing FW is no solution to unlock phones.
Click to expand...
Click to collapse
I'm not trying to unlock my phone. It's usable cause it doesn't reject simcards. Just denies me OTA updates. All I want is new software.
Is there another option apart from flashing new firmware if I want to update it? I'd love to unlock the phone but all the websites keep talking about generating codes. My phone doesn't request a code. And I can still use it. If there isn't another option for unlocking, can you assist with the questions I've asked?
Fine to flash new firmware to get the latest.
1. If you flash complete FW using Odin, you can flash the latest, no need to flash intermediate updates.
2. Did you search the forum yourself? See following thread for FW versions of the US-devices: https://forum.xda-developers.com/t/...s-and-flashing-discussion-here.4220111/unread
OnnoJ said:
Fine to flash new firmware to get the latest.
1. If you flash complete FW using Odin, you can flash the latest, no need to flash intermediate updates.
2. Did you search the forum yourself? See following thread for FW versions of the US-devices: https://forum.xda-developers.com/t/...s-and-flashing-discussion-here.4220111/unread
Click to expand...
Click to collapse
Thanks so much for all the help Yeah I've seen that thread before. But only firmware available until November 2021. Nothing after. So think I'll try the U1 to U option for now.