Hi Everybody
I have little problem with my new phone s10 plus
my phone isn't Root and knox Warranty is 0*0
but when i go and check the OTA update, My phone say "your phone is update"
but In sammobile my phone's new update is rolling out.
now My latest update on my phone is AE6 but AE7(May Security Patch) is rolling out.
What can i do for fix problem?
halvlid said:
Hi Everybody
I have little problem with my new phone s10 plus
my phone isn't Root and knox Warranty is 0*0
but when i go and check the OTA update, My phone say "your phone is update"
but In sammobile my phone's new update is rolling out.
now My latest update on my phone is AE6 but AE7(May Security Patch) is rolling out.
What can i do for fix problem?
Click to expand...
Click to collapse
Download ASE7 for your region and flash it via Odin problem solved
Sent from my SM-G975F using Tapatalk
halvlid said:
Hi Everybody
I have little problem with my new phone s10 plus
my phone isn't Root and knox Warranty is 0*0
but when i go and check the OTA update, My phone say "your phone is update"
but In sammobile my phone's new update is rolling out.
now My latest update on my phone is AE6 but AE7(May Security Patch) is rolling out.
What can i do for fix problem?
Click to expand...
Click to collapse
wait! your phone will recieve the update samsung is doing what is called a graduel update which means your phone will recieve it, just be patient and check sammobile and check your region if your region is recieving and your phone is saying phone is up to date do a dirty flash in odin and if that doesn't hel a clean flash(clean flash will delete all data)
halvlid said:
Hi Everybody
I have little problem with my new phone s10 plus
my phone isn't Root and knox Warranty is 0*0
but when i go and check the OTA update, My phone say "your phone is update"
but In sammobile my phone's new update is rolling out.
now My latest update on my phone is AE6 but AE7(May Security Patch) is rolling out.
What can i do for fix problem?
Click to expand...
Click to collapse
Just wait it will come it always comes 5 or 6 days into the next month for me I'm in the UK,
halvlid said:
Hi Everybody
I have little problem with my new phone s10 plus
my phone isn't Root and knox Warranty is 0*0
but when i go and check the OTA update, My phone say "your phone is update"
but In sammobile my phone's new update is rolling out.
now My latest update on my phone is AE6 but AE7(May Security Patch) is rolling out.
What can i do for fix problem?
Click to expand...
Click to collapse
Latest out from AT&T is G975USQS1ASD9 on May 20 not sure about other Carriers. Is your phone from U.S. carrier???
Or try smart switch.
tailgunner9 said:
Latest out from AT&T is G975USQS1ASD9 on May 20 not sure about other Carriers. Is your phone from U.S. carrier???
Click to expand...
Click to collapse
thanks for your post
no my phonet is'nt Us ver..
my Phone is Asia version.
Its very slow.
I am from Singapore and the latest update i have is april security update. Need to wait 1 to 2 months. Its like that since I was on s8.
Hi Same here i have S10+ G9750 and living on Germany all work fine only problem is I have April security patch, no new update is this normal.?
I look ohr and see new update
https://www.sammobile.com/firmwares/galaxy-s10-plus/SM-G9750/TGY/
Gesendet von meinem SM-G9750 mit Tapatalk
updates are released in phases
if its that concerning, you can always flash via odin
Jaspreet.master7 said:
updates are released in phases
if its that concerning, you can always flash via odin
Click to expand...
Click to collapse
is better First factory reset and later flash FW with Odin or is same
Gesendet von meinem SM-G9750 mit Tapatalk
salva111549 said:
is better First factory reset and later flash FW with Odin or is same
Gesendet von meinem SM-G9750 mit Tapatalk
Click to expand...
Click to collapse
Go to recovery mode and wipe data and wipe cache then goto download mode directly from recovery
Jaspreet.master7 said:
Go to recovery mode and wipe data and wipe cache then goto download mode directly from recovery
Click to expand...
Click to collapse
Ok thx Bro
Gesendet von meinem SM-G9750 mit Tapatalk
Jaspreet.master7 said:
updates are released in phases
if its that concerning, you can always flash via odin
Click to expand...
Click to collapse
thatd be too easy tho, waiting seems so much more fun lol
Related
Hey peepz,
I've tried to find updates via KIES and OTA, but it keeps saying that I've got the latest firmware installed (XXUBMEA (DBT)). Why can't KIES and OTA find the new MF8 update?
greetz,
swa100
Is your phone rooted??? If yes, Kies will not let u update....
Sent from my GT-I9500 (Hassan Khalid Malik) using xda premium
swa100 said:
Hey peepz,
I've tried to find updates via KIES and OTA, but it keeps saying that I've got the latest firmware installed (XXUBMEA (DBT)). Why can't KIES and OTA find the new MF8 update?
greetz,
swa100
Click to expand...
Click to collapse
Hi,
It may also be that the update is not available for your area ,yet.
There have been a lot of delays.
malybru said:
Hi,
It may also be that the update is not available for your area ,yet.
There have been a lot of delays.
Click to expand...
Click to collapse
Yes, it's available for my area (DBT version is out), It came out in june.
swa100 said:
Yes, it's available for my area (DBT version is out), It came out in june.
Click to expand...
Click to collapse
Download full rom and flash with odin, problem solved
MichelN said:
Download full rom and flash with odin, problem solved
Click to expand...
Click to collapse
But then I'll have to re-setup multi window-mod and greenify and stuff. Make system apps user apps. I really don't like the idea of doing that all again haha
I have the gear live and twrp. My watch got a notification that said that the update was downloaded and to update. When I start the update, my watch rebooted into twrp. I keep getting an error and the update doesn't install. Does anyone else have this problem, and know how to solve this issue?
I have the same problem, the watch becomes verry hot but I can't complete the update.
I am waiting for a solution. Other whise I have to visit a Samsung service point tomorrow.
Which version of twrp you guys have? I didn't got this error but I was unsuccessfully trying to install the 5.1.1 update trough modified zip I had lots of error that basically were stating that my watch was a different model and I suspect it could be due to last TWRP version. Still to confirm.
I solved using the recovery from tool here in forum to put the stock 4.4w image and did the updates OTA (the last 5.1.1 update was with sideload through original recovery butnI guess if i waited a few days it would be done OTA)
Sent from my SM-G920F using Tapatalk
han ree said:
I have the same problem, the watch becomes verry hot but I can't complete the update.
I am waiting for a solution. Other whise I have to visit a Samsung service point tomorrow.
Click to expand...
Click to collapse
Yea, I have a similar problem. Whenever I try to install using automatic update, it just fails with "something went wrong. Try again?".
insaned said:
Which version of twrp you guys have? I didn't got this error but I was unsuccessfully trying to install the 5.1.1 update trough modified zip I had lots of error that basically were stating that my watch was a different model and I suspect it could be due to last TWRP version. Still to confirm.
I solved using the recovery from tool here in forum to put the stock 4.4w image and did the updates OTA (the last 5.1.1 update was with sideload through original recovery butnI guess if i waited a few days it would be done OTA)
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Hmm so, that backup file I gave you didn't work for you? Could please check something on your watch for me please. I need to know what stock recovery build you have.Mine is stuck on the older version no matter what update I install. Thanks.
aligatro2010 said:
Yea, I have a similar problem. Whenever I try to install using automatic update, it just fails with "something went wrong. Try again?".
Hmm so, that backup file I gave you didn't work for you? Could please check something on your watch for me please. I need to know what stock recovery build you have.Mine is stuck on the older version no matter what update I install. Thanks.
Click to expand...
Click to collapse
Unfortunately no and thanks for yiur patience, I posted on the other thread.. I got so fed up that I flashed a stock image. And went from there since beginning and did it via sideload!
I used the gear live restore tool that is here from tomsgt if i remeber.i did all updates with everything stock . But after update to 5.1.1 i flashed again twrp (but not the latest version this time) and rooted the phone. I'm on travel until Tuesday and i didn't even brought watch. So incan check out ont Tuesday anything you need.
Sent from my SM-G920F using Tapatalk
insaned said:
Unfortunately no and thanks for yiur patience, I posted on the other thread.. I got so fed up that I flashed a stock image. And went from there since beginning and did it via sideload!
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Oh I didn't see that message. Did you install stock image from Samsung Gear Live Restore Tool v2? Thats the one I flashed and ota fails no matter what. Can you check if you stock recovery was updated when you did OTA update? It says the build name when you boot into it from bootloader. (where you did the sideloading)
aligatro2010 said:
Oh I didn't see that message. Did you install stock image from Samsung Gear Live Restore Tool v2? Thats the one I flashed and ota fails no matter what. Can you check if you stock recovery was updated when you did OTA update? It says the build name when you boot into it from bootloader. (where you did the sideloading)
Click to expand...
Click to collapse
Yup, I flashed full stock image and waited for 2 OTA updates until 5.0.2 and then sideloaded the original 5.1.1 in the original recovery, however I dunnl if this 2 first OTA have updated recovery too..
I can't check much right now because the watch is not with me until Tuesday, if even after twrp flash I did after the 5.1.1 update is still mentioned the original there in bootloader I will let you know as soon as I arrive on Tuesday.
Sent from my SM-G920F using Tapatalk
insaned said:
Yup, I flashed full stock image and waited for 2 OTA updates until 5.0.2 and then sideloaded the original 5.1.1 in the original recovery, however I dunnl if this 2 first OTA have updated recovery too..
I can't check much right now because the watch is not with me until Tuesday, if even after twrp flash I did after the 5.1.1 update is still mentioned the original there in bootloader I will let you know as soon as I arrive on Tuesday.
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Oh alright.
My device is from u.a.e (XSG), NO ROOT, I flash Poland latest rom 5.1.1, will I get OTA in future?
Thanks in advance ::thumbup:
Anyone has any ideas?
jdomadia said:
Anyone has any ideas?
Click to expand...
Click to collapse
You will get OTA if you have returned to factory settings after flashing. Your knox value should also be 0x0 and your ROM should be stock.
ozkaya said:
You will get OTA if you have returned to factory settings after flashing. Your knox value should also be 0x0 and your ROM should be stock.
Click to expand...
Click to collapse
Thanks for info, i factory reset after flash, also knox is 0x0,
I asked because many people in my situation not received ota update after it release 5.1.1. When they are already on Poland firmware with 5.0.1.
ozkaya said:
You will get OTA if you have returned to factory settings after flashing. Your knox value should also be 0x0 and your ROM should be stock.
Click to expand...
Click to collapse
hey I don't get ota updates. coming from xsg to xeo. flashed twice via odin. non rooted ..knox valid. any solution?
Sent from my SM-N910C using Tapatalk
http://forum.xda-developers.com/showthread.php?p=62518053
jdomadia said:
hey I don't get ota updates. coming from xsg to xeo. flashed twice via odin. non rooted ..knox valid. any solution?
Sent from my SM-N910C using Tapatalk
http://forum.xda-developers.com/showthread.php?p=62518053
Click to expand...
Click to collapse
That's interesting. Once, I had to factory reset twice to get the proper CSC but the photo looks it is already correct. Maybe Samsung distributes the OTAs in waves to balance server load.
ozkaya said:
That's interesting. Once, I had to factory reset twice to get the proper CSC but the photo looks it is already correct. Maybe Samsung distributes the OTAs in waves to balance server load.
Click to expand...
Click to collapse
No looks like Samsung lock the product code, in note3 & previous all models, once we flash rom of other regions it will change everything including products code...
So no solutions to keep Poland rom ota update?
Any work around, without root?
Thanks in advance
As of 3:45 a.m. this morning I couldn't believe what I was seeing thanks Verizon it's about time still messing around with it (7.1.1.) I'll let you know how it goes like it so far oh yeah I'm on the east coast S.C. THANKS AGAIN AND GOD BLESS EVERYONE!!!
Downloading right now.
Mike
I'm in the United States and I got 7.1.1 last night ?
got it today also
Yep, it's finally here, downloading.
Update 7.1.1 is here on RETEU
Just got the 7.1.1 OTA for the Moto Z Play on RETEU
Will keep you posted as soon as installed and tested
Just downloading 7.1.1. in Germany
I'm doing the 7.1.1 update in France
I'm here on April patch RETEU, but I'm rooted, with custom kernel and modified system.
What is the safe way to install the 7.1 OTA? I've already been notified about it.
Safe way is to flash everything from bootloader with a full package... OTA is to be avoided if you modified system and recovery.
GalaxyDrei said:
I'm here on April patch RETEU, but I'm rooted, with custom kernel and modified system.
What is the safe way to install the 7.1 OTA? I've already been notified about it.
Click to expand...
Click to collapse
Safest way is to flash my 7.1.1 stock rom, if you decide you don't like 7.1.1 you can safely move back or forth to any rom. Taking the OTA means you can't or should downgrade or you could end up hard bricked.
karendar said:
Safe way is to flash everything from bootloader with a full package... OTA is to be avoided if you modified system and recovery.
Click to expand...
Click to collapse
Yeah, I see. But the latest avaible full RETEU firmware is NPN25.137-24-1 and flashing this is not safe. Can I flash RETAIL april patch instead?
Got the update too but is your home button with Google animation? Mine turned into pixel home button 2 hours after the update
GalaxyDrei said:
I'm here on April patch RETEU, but I'm rooted, with custom kernel and modified system.
What is the safe way to install the 7.1 OTA? I've already been notified about it.
Click to expand...
Click to collapse
What did you use to root the Verizon model? I thought it can't be done.
Installation ok (Spain)
It was a long wait but i got it over here ( netherlands ) also.
No issues so far.
karendar said:
Safe way is to flash everything from bootloader with a full package... OTA is to be avoided if you modified system and recovery.
Click to expand...
Click to collapse
how to do that plz ? can i start the OTA and when downloaded i stop the update process, boot twrp, and flash the downloaded ota file ?
Or the only way is to download the from somebody on xda ?
shicomm said:
It was a long wait but i got it over here ( netherlands ) also.
No issues so far.
Click to expand...
Click to collapse
Here is one issue on reteu. Audio FX is not working.
flashallthetime said:
Safest way is to flash my 7.1.1 stock rom, if you decide you don't like 7.1.1 you can safely move back or forth to any rom. Taking the OTA means you can't or should downgrade or you could end up hard bricked.
Click to expand...
Click to collapse
Didn't want to risk anything, so I flashed your ROM
Indeed, getting around the globe reached retus. Now is question, should I accept or not?
Sent from my XT1635-02 using Tapatalk
Hi all,
I wanted to aks, if somebody can help me rolling back my device to an earlier Patch?
I tried some Filmwares with the force Dload Method, but it always ended at 5 %
my Device is a VKY-L09
locked bootloader
Use this thread https://forum.xda-developers.com/9-lite/how-to/unlock-bootloader-code-t3859685
1a. Downgrade firmware to 8.0.0.xxx (June patch) via androidhost.ru - search for your device, get a C432 version.
1b. Downgrade, instructions are in the 'ReleaseDoc' folder. Use the forced install method
I rolled back from september or october update to june's. there's instructions inside every firmware (nothing fancy, used default tutorial in there). Mine device was also locked VKY-L29.
I would appreciate if anyone successfully rolled back from VKY-L09 8.0.0.327 (C654) (November patch) can confirm it...
Also, as this has been probably done for getting the bootloader unlocked, if you can confirm being able to unlock the bootloader, I would appreciate it even more
What firmware did you use to roll back?
My understanding is (and I might be wrong) that rolling back from C654 can brick the phone, so just want to stay on the safe side.
TIA
velvel said:
I would appreciate if anyone successfully rolled back from VKY-L09 8.0.0.327 (C654) (November patch) can confirm it...
Also, as this has been probably done for getting the bootloader unlocked, if you can confirm being able to unlock the bootloader, I would appreciate it even more
What firmware did you use to roll back?
My understanding is (and I might be wrong) that rolling back from C654 can brick the phone, so just want to stay on the safe side.
TIA
Click to expand...
Click to collapse
I think that the Problem is that the Xloader Version changed from the September to the October Update from 01 to 02 or something and that is the Problem
StarSix01 said:
I think that the Problem is that the Xloader Version changed from the September to the October Update from 01 to 02 or something and that is the Problem
Click to expand...
Click to collapse
Thanks @StarSix01, that is what I am afraid too. In summary, I think one cannot unlock bootloader if on C654B327 as neither it can be done by any tool/hack (so far) nor it can be rolled down to the build that can be unlocked. :crying:
velvel said:
Thanks @StarSix01, that is what I am afraid too. In summary, I think one cannot unlock bootloader if on C654B327 as neither it can be done by any tool/hack (so far) nor it can be rolled down to the build that can be unlocked. :crying:
Click to expand...
Click to collapse
Yes i think thats The Case
My understanding is that you may downgrade firmware to june's, so you could unlock bootloader.
i did that with L29 model, don't see why it should differ to L09.
You can not unlock bootloader with firmware newer than june's - that's true, but that's not the same as downgrade. Take a look at tutorial link i posted beforw. There're step by step instructions ± a link to telegram chat with support.
keturidu said:
My understanding is that you may downgrade firmware to june's, so you could unlock bootloader.
i did that with L29 model, don't see why it should differ to L09.
You can not unlock bootloader with firmware newer than june's - that's true, but that's not the same as downgrade. Take a look at tutorial link i posted beforw. There're step by step instructions ± a link to telegram chat with support.
Click to expand...
Click to collapse
The Problem is, that it wont flash
Im getting the fail:
Incompatibility with current Version
StarSix01 said:
The Problem is, that it wont flash
Im getting the fail:
Incompatibility with current Version
Click to expand...
Click to collapse
What is your model number?
Do you use tutorial from that link?
Do you use this firmware to downgrade?
velvel said:
I would appreciate if anyone successfully rolled back from VKY-L09 8.0.0.327 (C654) (November patch) can confirm it...
Also, as this has been probably done for getting the bootloader unlocked, if you can confirm being able to unlock the bootloader, I would appreciate it even more
What firmware did you use to roll back?
My understanding is (and I might be wrong) that rolling back from C654 can brick the phone, so just want to stay on the safe side.
TIA
Click to expand...
Click to collapse
dude, your phone is demo version? what's that region 654? couldn't find any mentions
keturidu said:
What is your model number?
Do you use tutorial from that link?
Do you use this firmware to downgrade?
Click to expand...
Click to collapse
My Model number is VKY-L09 C432
And yes i used this Filmware but it wont work
Gesendet von iPhone mit Tapatalk
StarSix01 said:
My Model number is VKY-L09 C432
And yes i used this Filmware but it wont work
Gesendet von iPhone mit Tapatalk
Click to expand...
Click to collapse
Ok, next question - do you follow HUAWEI VKY-L09 8.0.0.370(C432) Software Upgrade Guideline.docx guide from "release doc" folder? And if yes, do you use "Force upgrade" mode?
If both answers is "yes", then did you try to download september/october firmware and try to downgrade to it?
keturidu said:
Ok, next question - do you follow HUAWEI VKY-L09 8.0.0.370(C432) Software Upgrade Guideline.docx guide from "release doc" folder? And if yes, do you use "Force upgrade" mode?
If both answers is "yes", then did you try to download september/october firmware and try to downgrade to it?
Click to expand...
Click to collapse
Yes i Followed everything
Gesendet von iPhone mit Tapatalk
StarSix01 said:
Yes i Followed everything
Gesendet von iPhone mit Tapatalk
Click to expand...
Click to collapse
And to downgrade September Patch wont work too
Gesendet von iPhone mit Tapatalk
keturidu said:
dude, your phone is demo version? what's that region 654? couldn't find any mentions
Click to expand...
Click to collapse
No, it is not demo. Canadian branding...
This is VTR-AL00 with Nov patch, cannot downgrade too.