Hi Folks,
Seeing around various section of all the models when users are struggling to restore their phone either due the flashing an incorrect firmware or after updating via Firmware Finder app and then wanting to rollback to earlier version of EMUI. They sometime cannot even flash the custom ROMs due to FRP lock or unable to flash the custom recovery and even after trying all the known methods, we struggle to restore their phone as they messed up badly with their phone and model or version change to something unexpected.
In this thread, lets discuss and share about rollback files available for various models (be it MM, Lollipop anything) so that new users could use it to restore to their original version and then update to official versions.
shashank1320 said:
Hi Folks,
Seeing around various section of all the models when users are struggling to restore their phone either due the flashing an incorrect firmware or after updating via Firmware Finder app and then wanting to rollback to earlier version of EMUI. They sometime cannot even flash the custom ROMs due to FRP lock or unable to flash the custom recovery and even after trying all the known methods, we struggle to restore their phone as they messed up badly with their phone and model or version change to something unexpected.
In this thread, lets discuss and share about rollback files available for various models (be it MM, Lollipop anything) so that new users could use it to restore to their original version and then update to official versions.
Click to expand...
Click to collapse
that would be very helpful.
please follow this!
cxavid said:
that would be very helpful.
please follow this!
Click to expand...
Click to collapse
Thanks. Got bunch of files for 6X hope will get for all slowly
Hi guys,
I actually own a Mate 10 pro, but the Mate 10 forum is quite dead tbh, since both devices are so similar, I hope I can get some answers here
Hi guys,
Although I'm not a totally newbie, I mean I installed Honeycomb on the OG Desire watch out for the volume tho, but I'm totally new to the Huawei thing, although I've owned a Ascend Mate 7 and a P9+ I never went as far as looking for root and custom ROMs, and I'm specially not educated in the whole architectural changes that treble brings.
So I've a few questions, and hopefully someone can clear some of them for me.
1- Unlocked BL means no OTA right? Also not via Firmware Finder?
2- Running stock, if a new update pops up on the web, I download the .zip and extract everything. I can flash the systems but I'm missing lots of things there, fixes on the kernel, and other stuff. Should I flash them all? Is it recommend? Or are the risks to high? Should I wait for the specific rom to be signed for my IMEI or am I okay as long as I choose the right branding (Europe for me).
3- And having magisk root... Does will it make flashing a new update any complicated?
4 - (and the last), when running a AOSP rom, is it possible/recommend to extract a new stock kernel and flash it when an update is available?
Thanks a lot
Hi, i flash the pixel experience rom oreo 8.1 on my moto g 2015 but i dont liked, so i flashed the stock rom 6.0 via adb fastboot and some updates have appeared, i can do?
Twinsen78 said:
Hi, i flash the pixel experience rom oreo 8.1 on my moto g 2015 but i dont liked, so i flashed the stock rom 6.0 via adb fastboot and some updates have appeared, i can do?
Click to expand...
Click to collapse
While I don't know exactly how it is on Moto G3, it seems kind of a game of luck if you get OTA updates back. But necessary steps device independent often are:
- Flash stock ROM with a full wipe
- flash stock recovery
- relock the bootloader
- some devices include a flash counter, for example almost all Samsung devices. This counter has to be reset. Works different for every phone.
- for some devices, for example Sony, specific files MUST be backuped before a flash, otherwise there is no chance of getting OTA back.
But keep in mind that this device doesn't receive updates anymore since about last year. So maybe you just look for the most up to date stock ROM and flash it, which btw on my phone is Android Marshmallow, security patch level April 2017.
I hope this helps a little bit, even though I can't provide very detailed information. Let's hope someone more experienced helps further, or just search around in the web.
BenjyTec said:
While I don't know exactly how it is on Moto G3, it seems kind of a game of luck if you get OTA updates back. But necessary steps device independent often are:
- Flash stock ROM with a full wipe
- flash stock recovery
- relock the bootloader
- some devices include a flash counter, for example almost all Samsung devices. This counter has to be reset. Works different for every phone.
- for some devices, for example Sony, specific files MUST be backuped before a flash, otherwise there is no chance of getting OTA back.
But keep in mind that this device doesn't receive updates anymore since about last year. So maybe you just look for the most up to date stock ROM and flash it, which btw on my phone is Android Marshmallow, security patch level April 2017.
I hope this helps a little bit, even though I can't provide very detailed information. Let's hope someone more experienced helps further, or just search around in the web.
Click to expand...
Click to collapse
are only 3 security patch, i updated and not brick but thanks for the reply.
What i have: a brand new carrier unlocked samsung galaxy s7 sm-g930w8 - came with 7.0
What Id love to do: downgrade to 6.0.1 official touchwiz rom but rooted
What im reading: that the security patch is from february of 2018, which means the bootloader is too new, which means downgrading using odin wont work ( https://www.sammobile.com/forum/threads/36282-Does-Region-Matter )
... so what can i do? i bought this phone with the sole intention of downgrading, as ive seen that it is possible for that phone model (s7) in general
i hate the look of the newer OS. They took the touchwiz out of touchwiz which i loved, although mine is a rare opinion. I want the operation and exact feel of 6.0. the menus are simpler, the notifications area isnt completely stripped of features differing from total stock android. i hate having to pull down twice to see everything. I just really want that older look and feel, but all around, not just a theme.
is there anything i can do to either downgrade or fool the bootloader into letting me carry this out? is this a true limitation, or si that info i found false/old? and if I can downgrade, which build version should I use?
ive been looking here for versions
https://samsung-firmware.org/model/SM-G930W8/ but im not sure which region to go with, or if i can technically use any region
sammobile doesnt list that version anymore at all ( https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/ )
https://mobiletech360.co/samsung-galaxy-s7-sm-g930w8-stock-firmware-rom-android-6-0-1-marshmallow/ there are a number of options here but unsure of the different numbers/builds. or if since its carrier unlocked, i could pick any?
I know most will think im silly for wanting to downgrade or caring that much about appearance, but silliness aside... is this even possible??
a while ago, i purchased an s5 mini, and downgraded that with no issues at all.... but its honestly been so long and i cant for the life of me remember the steps i took or if i needed to care about region codes or other numbers. but it did sucessfully work.... it was really built unwell/cheap, but it did work.... its also slower than my captivate glide which is still my current phone, until/if i can get this s7 working the way i desire.
any help and guidance is appreciated. If it is needed, ill be using it with a Koodo mobile sim.
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
teddytsen said:
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
Click to expand...
Click to collapse
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Click to expand...
Click to collapse
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Hello,
I can understand you and also understand what you want but Samsung installed a downgrade lock in their bootloader in early 2018,
if you installed this version you can't go back to an older version, I think that was in February.
You can go back from a 6.2018 version to a 4.2018 version for example but not to a 1.2018 version!
If you have a version of for example 12.2017, you can also go back to a version of 2016, so you can also go back to Android 6.01,
if not you only have the last versions of Android 7 or update to Oreo.
I hope I could help.
teddytsen said:
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Click to expand...
Click to collapse
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Pawprints1986 said:
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Click to expand...
Click to collapse
TL;DR
your bootloader is currently on version 3, and you cant downgrade to marshmallow
see that "U3BRB2"? that "U3" means your bootloader is on version 3. i assume the marshmallow firmwares use bootloaders pre-version 3 so you cant downgrade to firmwares using bootloaders with version 1 or 2. (this is how it works for F/FD models and im pretty sure samsung made it like that too for the W8 models)
eta 1) unrelated
eta 2) F/FD/W8/S/K/L variants (basically all the exynos models) have unlocked bootloaders. only SD variants have locked bootloaders so it's just your misconception
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
AoEKiller said:
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
Click to expand...
Click to collapse
You'll trip knox (which breaks features like secure folder, private mode, shealth and Sbrowser private mode) and lose the comfort of OTA updates if you do this tho. Not to mention that you can encounter signal reception problems because your flashed ROM is on marshmallow and your bl/cp is on Oreo or nougat. So I wouldn't advise this method as it may break so many things.
So I unlocked bootloader and updated the June firmware on ROG 5 when I got it, and now the device is rooted. Now that the July firmware update is out, how do I update? Do I again have to extract and patch boot.img separately and wipe everything the way I had to the first time? Note that I'm asking about retaining root and Magisk after the update.
New firmware "keep root" WW-18.0840.2103.26
Okay so I went to the Asus website https://www.asus.com/supportonly/ROG%20Phone%205%20(ZS673KS)/HelpDesk_Download/ Got the latest firmware which is the most recent one for this month with the latest security patch. I remember doing this method...
forum.xda-developers.com
It is always good to take a look around before jumping right into a new thread, especially with topics that seem like they really should have been posted already.
ROG Phone 5(s) Help Index
"Quick Filters" let you see all posts of a certain type. This can make finding posts easier, but what if a guide began as a "Question"? This thread aims to bridge that gap. You will find nearly all of the common things new owners are trying to...
forum.xda-developers.com