Hello,
received the Phone with the t-mobile branding (german version).
What i did is to use the official device unlock from Sony so be able to flash another Firmware.
Then i downloaded the generic DE from the FlashTool, and flashed it.
This failed because the rom was already on Android 7.
I did not manage to aquire the -9090 Rom in Android 6.0.1
So i flashed the central europe version.
First problem: this version does not (yet?) update to Android 7 - and actualy is NOT the version i wanted to have in the end.
Second problem: The camera app did not work anymore (already in use)
So i've read through this forum, and got the information, i need to re-unlock the device.
Did that, camera works.
However now i always get "this device is not trusted"
What i actualy want to have:
- A stock ROM in german, whcih gets OTA updates.
- Working Stock-Apps
- No warning when starting the Phone.
I do not care wether the warning is disabled, or simply not shown because of another bootloader. There should simply be no annoying warning.
I also have the exact same phone twice (mine, and the one for my girlfriend) in case this help somehow. In theory the best situation would be to hard-sync every single byte on the disk (i assume?)
I did not read anything about "do not flash currently, as this will make you loose your drm keys forever and the stock camera will no more work at all". But after watching this forum for some days now, it seems that exactly that has happened? So using a locked bootloader will not work anymore due to lost and unrecoverable drm keys? I cannot copy them from the other phone? So i need to replace the bootloader with another one to get rid of the message? And i also need to reflash the firmware as soon as FlashTool supports Android 7?
In the end a total piece of crap, because of a goddamn branding -.-
What would you guys recommend to do now? Just want to make it work without an error or unsecure warning displayed at every boot.
You did not need to unlock to flash another firmware.
Now you have unlocked you can't use the camera without keeping it unlocked and if it is unlocked you will get the warning message.
Just flash a 6.0 ftf from a region with the update then you will get the ota update
Ps, there are plenty of warnings on the Sony site about drm keys that you must have visited to get your unlock code...
And you cannot copy drm keys from another device
(Please delete, post moved to other forum)
Hi all,
So i,ve been reading the forums here for a little while, gathering as much info as i possibly could. This is my first post, in hopes of getting a little more clarification from some of the more experienced people on here.
Im currently living in China, where I plan to buy a couple of P20 pro’s, one for me and the other for the wife. The phones here in China are normally locked down, with no google play, and normally installed with a whole bunch of local apps.
I would like to flash an international stock firmware back to the phones. From what I’ve read, i will need to first need to install TWRP. Im using a MBP, so im guessing ill need to install the Android Debug Bridge.
Im a little confused when it comes to the firmware file versions. I realise that the handset model changes somewhat, so I guess im asking what do I need to be careful of in this regards? What do all of the different letters and numbers in the firmware file mean? I’ve worked a few out, but a definitive guide would be much appreciated.
If I want to get to a non-country modified version, of the stock firware, then what file should I be looking for? Im guessing its a non-region specific version. Is it fine to just flash this to the phone using TWRP, as long as its the correct version, dual sim, 6Gig mem, 128G storage, and the P20 Pro. Or do I also need to be aware of some other differences?
Finally what is the preffered method for unlocking the bootloader? I’ve seen different post, some mentioning registering with Huawei, and other talk about an unlock tool... what do you use?
Any help gratefully appreciated.
Bp_tec
Bootloader
Deleted
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.
You can manually update to latest Android 11 (April patch)
Bootloader unlock may be required.
Download the ROM https://mirrors.lolinet.com/firmwar...-DEFAULT_regulatory-DEFAULT_cid50_CFC.xml.zip
Unpack the zip and enter bootloader (turn the phone off and press and hold volume down and power it on)
Flash everything EXCEPT radio.img. Failure to do it will result in NO SIM error!
Everything is better with this version ROM. Do not update to Android at this time because it's a mess.
I manually upgraded to A12 on my XT2141-2 as soon as I was able. The only issue I've had was SIM not detected with 1 specific Lsposed module enabled, disabling that one module resolved that though. And ofc not having Gravity Box yet kinda sucks but I've had a blast with new theming possibility with A12 thanks to Repainted and Project Themed apps.
Could you elaborate on any issues you experienced yourself?
Sorry to have to ask this, but what happens if I somehow screw things up? unless I'm mistaken there's no TWRP for this phone (yet) to help with recovery...and how might I go about backing things up before I try to flash a new ROM build on my device? (Still new to things)
edit: addition: probably a stupid question, but I've only ever flashed the `boot.img` file, am I supposed to "fastboot flash" every file over?
ruq said:
Sorry to have to ask this, but what happens if I somehow screw things up? unless I'm mistaken there's no TWRP for this phone (yet) to help with recovery...and how might I go about backing things up before I try to flash a new ROM build on my device? (Still new to things)
edit: addition: probably a stupid question, but I've only ever flashed the `boot.img` file, am I supposed to "fastboot flash" every file over?
Click to expand...
Click to collapse
will this unlock verizon edge 5g
jakethesnake24 said:
will this unlock verizon edge 5g
Click to expand...
Click to collapse
No. Everything I've read states that Verizon Phones are hard-locked-down and cannot be rooted, unless there exists or is discovered at some point in the future an exploit to crack such phones. Sorry if that means you're out of luck.
I believe the preferred way of having a rootable phone is to always outright purchase it independently of any carrier. I purchased mine unlocked at a Best Buy.
In case anyone is reading this and getting a 404 on the OG post link for the ROM I found it under this updated link.
In case I get another phone with the latest RETUS OTA and run into the same problem where the phone will not accept the Unlock Code sent by Motorola. "FAILED (remote error)" every time. I don't know if this new OTA is the problem, or if the phone I received had a hardware or firmware problem. I posted here about that problem 2 days ago, so the history is in that thread. TIA . . .
= = = = = = = = =
SOLVED. Rollback from 40-95-9 to 40-95-6 --CANNOT-- be done. Anti-rollback "protection" prevents the 95-6 version of bootloader.img from being flashed.
NOTE: Trying to flash older firmware wipes the existing firmware, so attempting to do this will leave you with a systemless phone. If you insist on trying it yourself, BE SURE TO HAVE A COPY OF YOUR CURRENT (OR NEWER) FIRMWARE on hand.
According to my notes, at some point when I was doing OTA updates I did end up with 40-95-9; however, I suspect this update occurred after I unlocked the device. Hence, when I rolled back to the Feb version, I did not run into issues.
That said, I would NOT attempt to roll back with a stock bootloader locked device. You (likely) may run into motorola's implementation of Androids roll back protection which will prevent the device from booting. Without the 40-95-9 firmware file, I don't think it will be easy to get back to a working device. i.e. some form of blank flashing will be necessary. You might be able to recover from this, but I think it will be a headache.
Hopefully someone else will respond with some better advice/info for you.
HTH
EDIT you wrote in your other thread:
I should probably stress, I flashed the entire firmware with no problems at all.
Click to expand...
Click to collapse
but I'm not sure what you flashed. I doubt it was an older version. If you have the 40-95-9 firmware file, you might be ok to try. Just be aware you could end up with a device that is at best difficult if not impossible to unbrick.
Before flashing anything, be sure to allow OEM unlocking from developer options and get your unlock code from motorola's www site as you did previously.
Even tho it will soft brick the device, I'd flash everything from an older version. Reboot to the now hopefully older bootloader (you can check what bootloader is running with `fastboot getvar all`). If you end up with the red "No valid operating system" screen, just simultaneously hold down the power and volume down buttons until you get back to the bootloader. Assuming you can get into the bootloader (I'm not 100% cerntain that you can) from there you may be able to unlock or at least re-flash the 40-95-9 firmware to recover.
Note I have not attempted this so I can't say this will work. It's just what I would try in this situation if I didn't care about the time spent trying to recover or permanently bricking the device.
Good luck and I hope you don't have to try it.
It's just too hard to guess what might happen with the new arrangement of partitions in Android 10. I've rescued a couple of soft-bricks (Moto and Samsung believe it or not) but they were cheaper or just older. I'd rather not risk hard-bricking a phone after just shelling out $170-200 for it. (That's Swappa prices, everywere else is another $100 or so.) On older partitioning an unlocked bootloader wouldn't have made any difference in whether rollback worked or not. It was (pretty much) all about matching up bootloader versions (or digital signing for locked bootloader etc). Rollback would either work or it wouldn't.
Right now I'm trying to find a phone with something prior to 95-9 firmware. If I can't find that, I think I'll just try to talk my lady into a slightly smaller phone. She's been spoiled by the newer 6.7-6.8" phablets. I hate them myself, but this is not for me.
Thanks a bunch for trying to help.
notmyrealhandle said:
. . . in your other thread:
. . . I'm not sure what you flashed. I doubt it was an older version. If you have the 40-95-9 firmware file, you might be ok to try. Just be aware you could end up with a device that is at best difficult if not impossible to unbrick.
. . .
Click to expand...
Click to collapse
Forgot to say, I was explaining in the other thread that I had downloaded 95-9 via Lenovo's Rescue and Smart Assistant right off the bat, so I would have that for backup just in case. I did end up flashing it (the old-fashioned way, with a couple dozen fastboot commands) to see if maybe that would fix any possible glitch in the firmware. Also after trying to unlock a few more times, I reconnected to Rescue and Smart Assistant and actually ran the whole rescue deal, thus flashing 95-9 one more time.
I had also downloaded 95-6 from lolinet but didn't get the nerve to try flashing it. Android 10 on this phone is just too weird. Last year I unlocked and Magisk-rooted a Moto G Stylus 2021 on Android 10 with never a hint of a problem anywhere.
NOPE, this cannot be done. See bottom of my first post.