how to? hahaha
same problem it was before "only official release binaries are allowed to be flashed"
only now I have no BL "A520FXXU3" to power flash with the December att patch
caiquess95 said:
how to? hahaha
same problem it was before "only official release binaries are allowed to be flashed"
only now I have no BL "A520FXXU3" to power flash with the December att patch
Click to expand...
Click to collapse
Follow the same procedure as below:
https://forum.xda-developers.com/sa...torial-root-november-security-update-t3715661
Cannot bro. Until now, only the December security update use "level 3" block bootloader. So cannot use BL of other lower firmware. November security update use the same "level" bootloader with lastest MM update ("level" 2).
thangluong said:
Cannot bro. Until now, only the December security update use "level 3" block bootloader. So cannot use BL of other lower firmware. November security update use the same "level" bootloader with lastest MM update ("level" 2).
Click to expand...
Click to collapse
Worked for me. I have rooted mine using the same process by flashing below combination:
BL: A520FXXU2AQFA
AP+CP+CSC: All from Dec. 18 nougat build (QLA)
waltermsalomon said:
Worked for me. I have rooted mine using the same process by flashing below combination:
BL: A520FXXU2AQFA
AP+CP+CSC: All from Dec. 18 nougat build (QLA)
Click to expand...
Click to collapse
Can you upload BL that you used? It's work even you're in the latest security patch version december?
kobejor said:
Can you upload BL that you used? It's work even you're in the latest security patch version december?
Click to expand...
Click to collapse
I have attached the BL file. Yes, working on latest security patch (december).
waltermsalomon said:
I have attached the BL file. Yes, working on latest security patch (december).
Click to expand...
Click to collapse
Hey man it didn't work for me any other methods to root?
It did not work for me either. sw rev. check fail. device 3. binary 2
What country is your rom?
caiquess95 said:
It did not work for me either. sw rev. check fail. device 3. binary 2
What country is your rom?
Click to expand...
Click to collapse
It is Philippines (XTC) and phone origin is Vietnam, we are in the same CSC group and it should work. Please try exactly what I did.
Flash nougat BL with nov security patch along with the dec nougat build for AP+CP+CSC. After complete installation, I tried flashing TWRP (ofcourse enabling OEM unlock and USB debugging) and it failed. So went again to download mode then flashed BL (the file I attached) along with the dec nougat build. Again completed installation, then successfully flashed TWRP via odin. Afterwards, proceed to rooting my device.
waltermsalomon said:
It is Philippines (XTC) and phone origin is Vietnam, we are in the same CSC group and it should work. Please try exactly what I did.
Flash nougat BL with nov security patch along with the dec nougat build for AP+CP+CSC. After complete installation, I tried flashing TWRP (ofcourse enabling OEM unlock and USB debugging) and it failed. So went again to download mode then flashed BL (the file I attached) along with the dec nougat build. Again completed installation, then successfully flashed TWRP via odin. Afterwards, proceed to rooting my device.
Click to expand...
Click to collapse
I can not flash BL nougat from the September patch because it has level 2, and my BL is level 3 ....
Are you also Filipino?
Strange, maybe it is country specific issue. Mine has level 2 BL and rest Level 3 per dec build and I was successful flashing it. If you have a way to revert back from previous nougat build, say nov security patch, and can re-root your device, try flashing the latest nougat via flash fire. Use "flash firmware" action button and follow the instructions. Untick the "recovery" checkbox so you maintain twrp. From there, reroot your device through twrp. I also did this process and I was successful doing the whole thing.
kobejor said:
Are you also Filipino?
Click to expand...
Click to collapse
I am.
---------- Post added at 09:00 PM ---------- Previous post was at 08:25 PM ----------
caiquess95 said:
I can not flash BL nougat from the September patch because it has level 2, and my BL is level 3 ....
Click to expand...
Click to collapse
If you have flashed level 3 BL initially then you have a slim chance of downgrading your device from previous builds. Maybe I was just lucky enough because I used flashfire at first to upgrade to dec nougat build. I just didn't like settings menu as it was quite different from previous nougat, so I reflashed everything via odin but using level 2 BL and the rest level 3 (dec build). Try to follow the furom from the thread I initially gave you as they have also issues same as yours.
waltermsalomon said:
I am.
---------- Post added at 09:00 PM ---------- Previous post was at 08:25 PM ----------
If you have flashed level 3 BL initially then you have a slim chance of downgrading your device from previous builds. Maybe I was just lucky enough because I used flashfire at first to upgrade to dec nougat build. I just didn't like settings menu as it was quite different from previous nougat, so I reflashed everything via odin but using level 2 BL and the rest level 3 (dec build). Try to follow the furom from the thread I initially gave you as they have also issues same as yours.
Click to expand...
Click to collapse
then ... for me it will not be possible because my bl is level 3 ... no way I can flash a bl level 2
waltermsalomon said:
Strange, maybe it is country specific issue. Mine has level 2 BL and rest Level 3 per dec build and I was successful flashing it. If you have a way to revert back from previous nougat build, say nov security patch, and can re-root your device, try flashing the latest nougat via flash fire. Use "flash firmware" action button and follow the instructions. Untick the "recovery" checkbox so you maintain twrp. From there, reroot your device through twrp. I also did this process and I was successful doing the whole thing.
Click to expand...
Click to collapse
Flashfire doesn't flash bootloaders which is why you were able to root.
I hope there's a other way to install twrp or cwm even the boot loader can't downgrade.?
kobejor said:
I hope there's a other way to install twrp or cwm even the boot loader can't downgrade.?
Click to expand...
Click to collapse
Unlikely. Once it's locked that's usually it, no modifications possible.
It'll probably be locked down forever now unless Samsung release an unlocked firmware.
ashyx said:
Unlikely. Once it's locked that's usually it, no modifications possible.
It'll probably be locked down forever now unless Samsung release an unlocked firmware.
Click to expand...
Click to collapse
How sad to hear that!?
But I know a lot of great devs. here so it's possible to fix that :good:
ashyx said:
Flashfire doesn't flash bootloaders which is why you were able to root.
Click to expand...
Click to collapse
Oh, I was lucky didn't flash v3 BL even when I reflashed via odin. Thanks for that info.
Anyupdate about this problem?
Related
Samsung Galaxy J5 (2015)​
DO NOT FLASH/INSTALL NEW MARSHMALLOW UPDATES BECAUSE YOU CAN'T DOWNGRADE TO 5.1.1 ANYMORE !!!
DO NOT UPDATE YOUR PHONE ON 5.1.1, NEITHER ON 6.0.1 THROUGH SOFTWARE UPDATE !!!
( If you are on 5.1.1/6.0.1 and you update it from Settings > About phone > Software Update, I think you might end with same problem. )
ORIGINAL POST: http://forum.xda-developers.com/showpost.php?p=69504640&postcount=362 .
QUOTES:
KingWilliams said:
A warning to all ... samsung has come up with marshmallow bootloaders starting from baseband versions J1 (this is the last 2 values of baseband version) which will NOT allow u to downgrade ur bootloader...it will show an error like aboot.mdn fused ..which means u are stuck on marshmallow forever until a newer baseband is available...so be careful while upgrading to marshmallow from lollipop fellas :good:
Click to expand...
Click to collapse
milad wolf said:
hi . i cant back to stock android 5.1.1 in j5h ( in new secure update on all galaxy phones if you install last version of rom . downloading dosnt let to install old rom) . and becouse of that i cant install cm12.1 too. any solutions?
Click to expand...
Click to collapse
Proxy101 said:
Hi good people of XDA, i'm currently running a samsung j500h with a 6.0.1 update.
I really want to root it. I tried every possible way and followed every instruction on every sites that i went through (including here). But it doesn't seem to work on my phone. So i asked a developer form facebook and he suggested that i try downgrading to lollipop, from there root my phone and install a pre rooted 6.0.1 rom. But i cant do that as well.
Here are the errors that i'm getting:
CF-autoroot,twrp and su update flash: phone cant boot into recovery, it shows the samsung logo but with a black line that ramdomly pops on any part of the screen and slowly making it blur.
Cf auto root on the other hand, makes my phone stuck on the logo. it never boots now matter how long i wait.
Downgrading:
Error on phone says like these: aboot write fail: Fused 2>binary 1 (something like that)
it still boots and still on 6.0.1.
Does someone here has the same problem?
Click to expand...
Click to collapse
Unfortunately, i couldn't find any fix/tips about this after a Google search.
I'm not sure, but I think that if Samsung release new 5.1.1 updates, maybe it will have a new bootloader too and maybe then we can downgrade from 6.0.1 to 5.1.1.
#Henkate said:
DO NOT FLASH/INSTALL NEW MARSHMALLOW UPDATES BECAUSE YOU CAN'T DOWNGRADE TO 5.1.1 ANYMORE !!!
DO NOT UPDATE YOUR PHONE ON 5.1.1, NEITHER ON 6.0.1 THROUGH SOFTWARE UPDATE !!!
( If you are on 5.1.1/6.0.1 and you update it from Settings > About phone > Software Update, I think you might end with same problem. )
ORIGINAL POST:http://forum.xda-developers.com/showpost.php?p=69504640&postcount=362 .
QUOTES:
Unfortunately, i couldn't find any fix/tips about this after a Google search.
I'm not sure, but I think that if Samsung release new 5.1.1 updates, maybe it will have a new bootloader too and maybe then we can downgrade from 6.0.1 to 5.1.1.
This thread should be sticky, but I don't know if we, users, can do it. So I will contact a moderator.
Click to expand...
Click to collapse
Samsung has indeed become a huge crap. Android is an open source but these dudes always tend to make it a closed source. Really upset with this but we have no choice. Whether u update manually or via kies it will be the same.
And thanks henkate for making this thread. This will be proved useful to many. :good:
I got reply from moderator regarding sticky thread and he told me that sticky thread is not necessary because there are too low discussions on our J5 forum (it's not so popular) and that when our J5 forum will be more "developed"/popular, we could have a sticky thread which would contain all those important threads.
So, this thread will not be on top of this section ( Guides, News & Discussions) when there will be new threads or new posts in other threads.
thank u so much big bro
#Henkate said:
DO NOT FLASH/INSTALL NEW MARSHMALLOW UPDATES BECAUSE YOU CAN'T DOWNGRADE TO 5.1.1 ANYMORE !!!
DO NOT UPDATE YOUR PHONE ON 5.1.1, NEITHER ON 6.0.1 THROUGH SOFTWARE UPDATE !!!
( If you are on 5.1.1/6.0.1 and you update it from Settings > About phone > Software Update, I think you might end with same problem. )
ORIGINAL POST: http://forum.xda-developers.com/showpost.php?p=69504640&postcount=362 .
QUOTES:
Unfortunately, i couldn't find any fix/tips about this after a Google search.
I'm not sure, but I think that if Samsung release new 5.1.1 updates, maybe it will have a new bootloader too and maybe then we can downgrade from 6.0.1 to 5.1.1.
Click to expand...
Click to collapse
Thanks for this
Thanks. I was going to flash new one but stopped after reading this
Sent from my SM-J500F using Tapatalk
#Henkate said:
DO NOT FLASH/INSTALL NEW MARSHMALLOW UPDATES BECAUSE YOU CAN'T DOWNGRADE TO 5.1.1 ANYMORE !!!
DO NOT UPDATE YOUR PHONE ON 5.1.1, NEITHER ON 6.0.1 THROUGH SOFTWARE UPDATE !!!
( If you are on 5.1.1/6.0.1 and you update it from Settings > About phone > Software Update, I think you might end with same problem. )
ORIGINAL POST: http://forum.xda-developers.com/showpost.php?p=69504640&postcount=362 .
QUOTES:
Unfortunately, i couldn't find any fix/tips about this after a Google search.
I'm not sure, but I think that if Samsung release new 5.1.1 updates, maybe it will have a new bootloader too and maybe then we can downgrade from 6.0.1 to 5.1.1.
Click to expand...
Click to collapse
Even If u cant downgrade Bootloader, you can always just repack the system boot and recovery from 5.1.1 and flash and TADA you are back on Lollipop
oranaise2412 said:
Even If u cant downgrade Bootloader, you can always just repack the system boot and recovery from 5.1.1 and flash and TADA you are back on Lollipop
Click to expand...
Click to collapse
I dont know if its easy like that since other people with other Samsung phone couldnt solve this.
Another guy got same problem with downgrading:
http://forum.xda-developers.com/galaxy-j5/help/flashing-twrp-error-samsung-j500h-t3501187 (read at "Downgrading").
PS: Please dont quote the OP. Thank you!
I know that you have asked and been told no but we have got to keep this at the top of this thread.
This is so important for people to know.
What's are best option to keep this at the top ?
John
oranaise2412 said:
Even If u cant downgrade Bootloader, you can always just repack the system boot and recovery from 5.1.1 and flash and TADA you are back on Lollipop
Click to expand...
Click to collapse
It won't flash. Even if it flashes, without the right bootloader ur phone wont boot at all.
Edit:
If i am wrong, u can always suggest a solution. :good:
KingWilliams said:
It won't flash. Even if it flashes, without the right bootloader ur phone wont boot at all.
Edit:
If i am wrong, u can always suggest a solution. :good:
Click to expand...
Click to collapse
Your correct with what your saying mate
I'm guessing that this could mean all future stock Roms are gonna have this issue ???
John
KingWilliams said:
It won't flash. Even if it flashes, without the right bootloader ur phone wont boot at all.
Edit:
If i am wrong, u can always suggest a solution. :good:
Click to expand...
Click to collapse
Well depends always on the BL but in most cases my solution works
oranaise2412 said:
Even If u cant downgrade Bootloader, you can always just repack the system boot and recovery from 5.1.1 and flash and TADA you are back on Lollipop
Click to expand...
Click to collapse
Agreed. Quite often Samsungs bootloaders are backwards compatible with previous firmware.
Boot.img and system.img should be all that is required to downgrade and possibly NON-HLOS.BIN if there are wifi issues.
Not only that there's a possibility the bootloader doesn't need to be flashed and the MM rom will boot with the lollipop bootloader.
However there are no guarantees either way.
ashyx said:
Agreed. Quite often Samsungs bootloaders are backwards compatible with previous firmware.
Boot.img and system.img should be all that is required to downgrade and possibly NON-HLOS.BIN if there are wifi issues.
Not only that there's a possibility the bootloader doesn't need to be flashed and the MM rom will boot with the lollipop bootloader.
However there are no guarantees either way.
Click to expand...
Click to collapse
Well, someone of the guys which can't downgrade anymore should try this and report.
EDIT:
@Proxy101 : Can you try this to downgrade to 5.1.1 and report if it works?
Even If u cant downgrade Bootloader, you can always just repack the system boot and recovery from 5.1.1 and flash and TADA you are back on Lollipop
Click to expand...
Click to collapse
Agreed. Quite often Samsungs bootloaders are backwards compatible with previous firmware.
Boot.img and system.img should be all that is required to downgrade and possibly NON-HLOS.BIN if there are wifi issues.
Not only that there's a possibility the bootloader doesn't need to be flashed and the MM rom will boot with the lollipop bootloader.
However there are no guarantees either way.
Click to expand...
Click to collapse
fake
i have j500FN i flashed marshmallow -- downgrade on lolipop flash CM12.1 from nick verse ---wipe all flash marshmallow via odin and again downgare all work good without errors
wyr007 said:
i have j500FN i flashed marshmallow -- downgrade on lolipop flash CM12.1 from nick verse ---wipe all flash marshmallow via odin and again downgare all work good without errors
Click to expand...
Click to collapse
It's not fake. The two users who reported has J500H. The latest firmware changelist of J500H is not same as J500FN one (also I don't see a firmware with "J" at FN). Maybe the new update didn't come on J500FN yet.
Whether you believe it or not, it's up to you. Keep updating if you want, but then don't complain here that you can't downgrade.
You've been warned about this.
Thread cleaned up of all Off Topic Posts.
Also bump again and again is really not needed. Please don't do that again.
Can we please stay on topic?
Thank for this useful thread. Stay at cm12.1 @nick_verse after read this thread
Sent from my SM-J500G using Tapatalk
Just had an idea... We could spread these news by adding this thread with red color in our signature. You can edit your signature here: http://forum.xda-developers.com/profile.php?do=editsignature .
Example of signature code:
Code:
[PLAIN]
[B][SIZE="4"][URL="http://forum.xda-developers.com/android/general/galaxy-j5-qa-thread-galaxy-j5-series-t3382922/post66943563#post66943563"][COLOR="Red"]Galaxy J5 Q&A[/COLOR][/URL][/SIZE][/B] <-- click
[/PLAIN]
[email protected]
Here it is
Factory
https://dl.google.com/dl/android/aosp/angler-n4f26o-factory-c53f0a50.zip
Factory
https://dl.google.com/dl/android/aosp/angler-nuf26k-factory-bde381d4.zip <------ VERIZON ONLY
OTA
https://dl.google.com/dl/android/aosp/angler-ota-n4f26o-6a853f19.zip
OTA
https://dl.google.com/dl/android/aosp/angler-ota-nuf26k-baec5b5e.zip <------ VERIZON ONLY
cheers
N4F26O
Baseband 3.78
Kernel 3.10.73 (Dec 7)
Patch Level: Feb 5
Bootloader 3.64
https://source.android.com/security/bulletin/2017-02-01.html
Both N4F26O:
Fac image with encryptable boot-kernel:
https://www.androidfilehost.com/?fid=673368273298929182
Encryptable boot-kernel only:
https://www.androidfilehost.com/?fid=673368273298929179
so we just flash this and it will not affect anything on my phone? im rooted stock rom and franco kernel
Someone correct me if I'm wrong but I think it replaces the recovery which you can just put back. You'll also lose root I think which again you could just flash. At least that's how it was for the stock roms I've dealt with on other phones.
jaron7_11 said:
so we just flash this and it will not affect anything on my phone? im rooted stock rom and franco kernel
Click to expand...
Click to collapse
what do you have installed?flashfire or TWRP
danmaman said:
what do you have installed?flashfire or TWRP
Click to expand...
Click to collapse
Twrp
jaron7_11 said:
Twrp
Click to expand...
Click to collapse
you can use this guide
http://elementalx.org/how-to-install-android-monthly-security-updates/
cheers
Good to have... for now
danmaman said:
you can use this guide
http://elementalx.org/how-to-install-android-monthly-security-updates/
cheers
Click to expand...
Click to collapse
That one doesn't mention the radio. I prefer to use Heisenberg's guide. Usually #14 for when I'm flashing updates but there's a lot of other useful tips as well.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Hi there! Does this have any fixes or is it just security stuff? I'd like to know if the echo during a hangouts/Skype/Duo call gets any better. Thanks!
Sent from my Nexus 6P using Tapatalk
Pig Vomit said:
N4F26O
Baseband 3.78
Kernel 3.10.73 (Dec 7)
Patch Level: Feb 5
Bootloader 3.64
https://source.android.com/security/bulletin/2017-02-01.html
Click to expand...
Click to collapse
on January Factory [N4F26J]image our Baseband/Radio is 03.79
the latest February Factory [N4F26O]image is Baseband/Radio is 03.78
downgrade?
fLipz said:
on January Factory [N4F26J]image our Baseband/Radio is 03.79
the latest February Factory [N4F26O]image is Baseband/Radio is 03.78
downgrade?
Click to expand...
Click to collapse
Yes it seems so..... Weird
Looks like radio version is downgraded !!?
I use FlashFire and it keeps TWRP and ROOT
fLipz said:
on January Factory [N4F26J]image our Baseband/Radio is 03.79
the latest February Factory [N4F26O]image is Baseband/Radio is 03.78
downgrade?
Click to expand...
Click to collapse
Last month people speculated that N4F26I with radio 3.78 was for non-Verizon and N4F26J with radio 3.79 was for Verizon because it fixed VOLTE and Voicemail for Verizon customers. Perhaps they just neglected to label last month? I note the new Verizon-only NUF26K keeps the 3.79 radio.
I'm on T-Mobile and last month was running 26J with 3.79 radio and had no problems. Now on 26O with 3.78 and having no problems.
My 6P got the I version last month. I suppose the J was only for the US provider Verizon because I didn't see anyone I know with a 6P to receive the J version.
Do someone know is there a pixel mod for February images?
rnavass said:
Do someone know is there a pixel mod for February images?
Click to expand...
Click to collapse
I applied an older version, it seems to be working but I am getting a weird message on boot "Internal error in your device" or something similar to that.. weird.
I mean it's all working alright , just this message on boot.
EDIT:
OK the exact error was "There's an internal problem with your device. Contact your manufacturer for details"
It was an error in the prop.build file. Mismatch with the vendor prop.build file.
Copied the value :ro.build.fingerprint from the vendor file to the prop.build under system and it disappeared.
wizardwiz said:
I applied an older version, it seems to be working but I am getting a weird message on boot "Internal error in your device" or something similar to that.. weird.
I mean it's all working alright , just this message on boot/
Click to expand...
Click to collapse
Which one did you flash it?
Hi Folks!
Single thread for all the fastboot flashable stock firmwares and official OTAs.
Captured OREO 8.1.0 OTAs can be found in a separate folder, Check the region specific folders and DO READ THE DESCRIPTION OF THE FILES FOR MORE INFORMATION.
Make sure you are on unmodified stock rom with build number NPSS26.116-61-11(For RETIN Region OTA) and NPSS26.116-64-11(For RETBR Region OTA) before flashing/installing it, or else it wont flash/install.
Bootloader status does NOT matter, so unlocked guys can install it too, just make sure you have flashed stock first via fastboot.
Edit: Uploaded the fastboot flashable firmware OPS28.65-36.
Those who have unlocked bootloader can flash it via fastboot.
Locked bootloader ones can use the OTA files but make sure you are on eligible firmware.
Downloads:
Fastboot Flashable Firmwares: https://www.androidfilehost.com/?w=files&flid=214680
Captured OTAs: https://www.androidfilehost.com/?w=files&flid=282605
Suggestions:
Never re-lock your device's bootloader.
Never downgrade your firmware.
XDA:DevDB Information
Moto Stock Firmwares/Captured OREO OTAs, ROM for the Moto G5S Plus
Contributors
CheckYourScreen
ROM OS Version: 8.x Oreo
Version Information
Status: Stable
Created 2018-09-17
Last Updated 2018-09-22
Installation Steps
For OTA files:
Make sure you are on unmodified stock firmware, or just flash the stock rom again using fastboot.
Place the OTA file in internal storage(do not place it in a folder)
Go to settings>Apps and give storage permissions to Motorola Update Services app
Go to about and check for update.
Reserved
Wow.. ! thanks for this update. now my motorola will rock again !
Cant update bro my update app cant find package in internal storage i already gave permission app to storage
Nice updated..working fine here thank you
masnish kunwar said:
Cant update bro my update app cant find package in internal storage i already gave permission app to storage
Click to expand...
Click to collapse
Might sound weird, but if you're not on home network or wi-fi, it won't work.
AnubhavKumarc said:
Might sound weird, but if you're not on home network or wi-fi, it won't work.
Click to expand...
Click to collapse
No
Flash using sideload
Adi5 said:
No
Flash using sideload
Click to expand...
Click to collapse
It didn't detect the update on my phone when I was on roaming network, as soon as I switched to Wi-Fi it did, Motorola Update services doesn't work on roaming. And yeah it can be flashed using sideload, but that's not what I was talking about.
Can I update to oreo ota from soak test 1 which is on June 2018 patch.. I had Manually flashed the 1St soak at that time..
From this version, can I update to August 2018 oreo?
If yes, how?
Its soak test or stock rom ??
bakryu said:
Its soak test or stock rom ??
Click to expand...
Click to collapse
Looks like soak, by seeing the kernel version "prerelease"
geekychandu said:
Looks like soak, by seeing the kernel version "prerelease"
Click to expand...
Click to collapse
No
Rajat22 said:
Nice updated..working fine here thank you
Click to expand...
Click to collapse
I wonder if it's final OTA, then why the kernel version says "prerelease"
Can't set wallpaper in this rom...
---------- Post added at 06:40 PM ---------- Previous post was at 06:09 PM ----------
hazan95 said:
Can't set wallpaper in this rom...
Click to expand...
Click to collapse
Don't worry figured it Out!
Pls provide mirror links AndroidFileHost is slow AF.
After I flashed Oreo update my network lost bro what should i do?? i tried to restore it with efs and presist but not worked..
What about reteu channel? It was not mentioned at all
bakryu said:
Its soak test or stock rom ??
Click to expand...
Click to collapse
Final stable build of stock oreo.
geekychandu said:
Looks like soak, by seeing the kernel version "prerelease"
Click to expand...
Click to collapse
geekychandu said:
I wonder if it's final OTA, then why the kernel version says "prerelease"
Click to expand...
Click to collapse
Thats GCC toolchain release info for god sake
dheerajz said:
Pls provide mirror links AndroidFileHost is slow AF.
Click to expand...
Click to collapse
You can wait for moto to send you ota. No mirrors plz.
masnish kunwar said:
After I flashed Oreo update my network lost bro what should i do?? i tried to restore it with efs and presist but not worked..
Click to expand...
Click to collapse
Follow the volte fix. Join telegram group (https://t.me/g5splus) and type #voltefix and follow the steps.
eCoB said:
What about reteu channel? It was not mentioned at all
Click to expand...
Click to collapse
Official roll out and ota packages have been released only for retbr and retin region. Wait for moto to release ota for EU region, I'll upload it once available.
I realize that there are some issues about global realme XT, I came to a lot of problems like others. Let me summarize some points:
1. Global version : (Ru/Eu/TW/......)
*come with NFC
the main difference between global and India version
(you can't tell between EX and EUEX) , so NFC is the key.
*cannot unlock bootloader (from os6 to os7)
If you do unlock bootloader, try to show us how.
*cannot root (unless BL unlocked)
*do not update to India Rom, if you do try this post
https://forum.xda-developers.com/realme-xt/help/realme-ui-bugs-eu-device-t4076145
*the lastest update is Android 10 ui c.01 (update a.05 to a.06 first before to c.01)
https://realmeupdater.com/downloads/latest/RMX1921EUEX/
https://download.c.realme.com/osupdate/RMX1921EUEX_11_OTA_1010_all_lZytoJtMnV4X.ozip
which is newer than India c.03 rom, I think that's why we still can update via recovery mode.
*Realme Official ROMs Archive for Realme XT
https://realmeupdater.com/downloads/archive/RMX1921EUEX/
anyone with other issues please add on. Thanks!
-- unlock bootloader is possible now, however I don't have xt anymore --
Hi, where is this being downloaded from. Took over two hours then it gave me a failed download notice so I tried two more times with failed again. Thanks
the lastest update is Android 10 ui c.01
the link is still working.
https://download.c.realme.com/osupdate/RMX1921EUEX_11_OTA_1010_all_lZytoJtMnV4X.ozip
donkeyman1234 said:
the lastest update is Android 10 ui c.01
the link is still working.
https://download.c.realme.com/osupdate/RMX1921EUEX_11_OTA_1010_all_lZytoJtMnV4X.ozip
Click to expand...
Click to collapse
I'll try again thanks....
mdcowby said:
I'll try again thanks....
Click to expand...
Click to collapse
How do you install this once downloaded When I go into recovery and click this file I get an error. Do you have to unzip it I've never messed with. .ozip files
Thanks for your help
No. I think you're at A.05. Then update to A.06.
After that you can update to Android 10.
schwatter said:
No. I think you're at A.05. Then update to A.06.
After that you can update to Android 10.
Click to expand...
Click to collapse
Correct I have A. 05 so I have to update to A. 06 then. where can I find the A. 06 I have global realme xt just want to make sure I grab the right download.
firmware can be downloaded here:
https://realmeupdater.com/downloads/archive/RMX1921EUEX/
donkeyman1234 said:
firmware can be downloaded here:
https://realmeupdater.com/downloads/archive/RMX1921EUEX/
Click to expand...
Click to collapse
Thanks so much.....
---------- Post added at 07:53 AM ---------- Previous post was at 07:43 AM ----------
mdcowby said:
Thanks so much.....
Click to expand...
Click to collapse
One more? When I put it on my SD card how do I install it. I'm not used to, .ozip files
Boot into recovery mode and choose update from sd card. Or just move the file to the phone memory and use phone's file explorer to open it, then the phone shall be able to update.
But wait. Some say A.05 can unlock bootloader. If you need it, test it. Maybe you have luck.
donkeyman1234 said:
Boot into recovery mode and choose update from sd card. Or just move the file to the phone memory and use phone's file explorer to open it, then the phone shall be able to update.
Click to expand...
Click to collapse
Perfect thanks again. worked perfectly now I just hope installing to Android 10 I'll do that tomorrow. Stay safe
---------- Post added at 08:55 AM ---------- Previous post was at 08:47 AM ----------
schwatter said:
But wait. Some say A.05 can unlock bootloader. If you need it, test it. Maybe you have luck.
Click to expand...
Click to collapse
I'm not into all that anymore I spent more time on my lgv20 phone then with anything else. I do like the opinion of rooting at some point if this will root. I had a Lgv20 since 2016 loved that phone. But I'm enjoying this one a lot. I just want to be updated to the latest versions. And security patches. Thanks again for your help.
so i just got a note 8 its stuck on oreo im not receiving any updates so i thought i outta do it manually but the thing is i dont have the oem unlock option yet do i need it for flashing stock firmware with odin plus what firmware should i flash? i got snapdragon n950u xaa/xaa/tmb its on bootloader v5 i think i need to upgrade to pie
I think OEM unlock, is just to disable Factory Reset Protection if you don't know the original Google account used to register the device.
....whenver the device is wiped.
---------- Post added at 05:45 PM ---------- Previous post was at 05:41 PM ----------
[/COLOR]
Savitar8097651 said:
so i just got a note 8 its stuck on oreo im not receiving any updates so i thought i outta do it manually but the thing is i dont have the oem unlock option yet do i need it for flashing stock firmware with odin plus what firmware should i flash? i got snapdragon n950u xaa/xaa/tmb its on bootloader v5 i think i need to upgrade to pie
Click to expand...
Click to collapse
You can download the tmb stock firmware with samfirm.exe or frija on pc and flash it with Odin.
The OEM switch doesn't do anything to prevent flashing firmware through Odin. Also you won't see it on snapdragons models, only through the combination firmwares.
The OEM switch is used on exynos models to unlock bootloaders. The n950W/U/U1 has LOCKED bootloaders so it doesn't work on them.
BluePhnx said:
---------- Post added at 05:45 PM ---------- Previous post was at 05:41 PM ----------
[/COLOR]
You can download the tmb stock firmware with samfirm.exe or frija on pc and flash it with Odin.
The OEM switch doesn't do anything to prevent flashing firmware through Odin. Also you won't see it on snapdragons models, only through the combination firmwares.
The OEM switch is used on exynos models to unlock bootloaders. The n950W/U/U1 has LOCKED bootloaders so it doesn't work on them.
Click to expand...
Click to collapse
i tried flashing this one N950USQU5DSD3 firmware and on odin after setup connection it gave all threads completed 1 failed 0 completed can u help me on this?
this my phone
Bootloader Version :
N950USQS5CRK1
PDA Version :
N950USQS5CRK2
CSC Version:
N950UOYN5CRK1
Baseband Version:
N950USQS5CRK1
i took the firmware off this post https://forum.xda-developers.com/gal...n950u-t3925823
Did you extract everything resulting in Ap..Bl..Cp..Csc..Home_csc?
Using correct Odin. Try different USB port
Sent from my SM-N986U using Tapatalk
To add to that make sure it's a usb 2 port or lower version. Don't use usb 3 port it seems to cause issues with Odin.
Savitar8097651 said:
so i just got a note 8 its stuck on oreo im not receiving any updates so i thought i outta do it manually but the thing is i dont have the oem unlock option yet do i need it for flashing stock firmware with odin plus what firmware should i flash? i got snapdragon n950u xaa/xaa/tmb its on bootloader v5 i think i need to upgrade to pie
Click to expand...
Click to collapse
Snapdragon does not have OEM unlock
Sent from my SM-N986U using Tapatalk
It's strange, more than 10.days i use Horizon room and rooted, but i don't see that "OEM unloock" on developer menu, the root works fine....Question is ... is it problem for my note8 or not?
Alboooz said:
It's strange, more than 10.days i use Horizon room and rooted, but i don't see that "OEM unloock" on developer menu, the root works fine....Question is ... is it problem for my note8 or not?
Click to expand...
Click to collapse
No
It should be fine! Since your bootloader is already unlocked and rooted.
Some roms hide that OEM unlock switch. Guess to prevent the phone kg state to go to prenormal mode if toggled.
BluePhnx said:
No
It should be fine! Since your bootloader is already unlocked and rooted.
Some roms hide that OEM unlock switch. Guess to prevent the phone kg state to go to prenormal mode if toggled.
Click to expand...
Click to collapse
I understand it now, thanks friend.