Related
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.
Hey guys,
My dad has a SM-G930A 6.0.1 unlocked running on T-Mobile. It is starting to show it's age (battery drain, apps not running like they should, etc.) and is still stuck on 6.0.1.. From my understanding, it should be possible to flash to SM-G930T, however I am a bit lost as to where to begin the process to do so. I tired going straight to 8.0 by flashing the SM-G930T 8.0 firmware files but this didn't work (I didn't think it would work, but it was worth a try). With that said, would it be better for me to just stick to updating to SM-G930A 7.0 via the guides posted, or is there a way for me to Flash the SM-930T 8.0 firmware? Thanks in advance.
leprkon said:
Hey guys,
My dad has a SM-G930A 6.0.1 unlocked running on T-Mobile. It is starting to show it's age (battery drain, apps not running like they should, etc.) and is still stuck on 6.0.1.. From my understanding, it should be possible to flash to SM-G930T, however I am a bit lost as to where to begin the process to do so. I tired going straight to 8.0 by flashing the SM-G930T 8.0 firmware files but this didn't work (I didn't think it would work, but it was worth a try). With that said, would it be better for me to just stick to updating to SM-G930A 7.0 via the guides posted, or is there a way for me to Flash the SM-930T 8.0 firmware? Thanks in advance.
Click to expand...
Click to collapse
Wow you guys really get screwed over there in the US with cell phones. It's a pain in the a** to do anything with your phones.
Anyway I'm guessing the phone was originally AT&T right? And now it's unlocked to any carrier.
If you just want to update the phone to the latest firmware then just flash AT&T Oreo. It won't affect the SIM it will still work as before.
If you want to flash any other firmware including T Mobile then you'll need to unlock the bootloader on the device and that's a whole different ball game. With plenty of guides on how to online.
Make sure you back up all the things you want to keep before flashing
cooltt said:
Wow you guys really get screwed over there in the US with cell phones. It's a pain in the a** to do anything with your phones.
Anyway I'm guessing the phone was originally AT&T right? And now it's unlocked to any carrier.
If you just want to update the phone to the latest firmware then just flash AT&T Oreo. It won't affect the SIM it will still work as before.
If you want to flash any other firmware including T Mobile then you'll need to unlock the bootloader on the device and that's a whole different ball game. With plenty of guides on how to online.
Make sure you back up all the things you want to keep before flashing
Click to expand...
Click to collapse
Thanks for the reply! I appreciate the direction. You are right, US phones are a pain. And yes, the phone was originally an AT&T phone, but was unlocked.
As for unlocking the bootloader, I've found different sources that say that unlocking the bootloader on this particular phone is not possible with this particular phone. I did read something about an engineering bootloader being used to get around a locked bootloader for rooting. Could this be used for flashing as well?
cooltt said:
If you want to flash any other firmware including T Mobile then you'll need to unlock the bootloader on the device and that's a whole different ball game. With plenty of guides on how to online.
Click to expand...
Click to collapse
That's not entirely true. Using Odin you can flash any USA firmware onto any other USA device, no bootloader unlocking required.
It's very common for people to flash G930U over their G930V/T/A/P devices to remove bloatware
leprkon said:
As for unlocking the bootloader, I've found different sources that say that unlocking the bootloader on this particular phone is not possible with this particular phone. I did read something about an engineering bootloader being used to get around a locked bootloader for rooting. Could this be used for flashing as well?
Click to expand...
Click to collapse
It's unstable and only lets the device charge up to 80%, your best bet woulld just be a full flash with Odin
This guide is a bit dated but it's the best one out there. Just make sure you google the latest Odin and use all 4 firmware files when flashing https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
Beanvee7 said:
That's not entirely true. Using Odin you can flash any USA firmware onto any other USA device, no bootloader unlocking required.
It's very common for people to flash G930U over their G930V/T/A/P devices to remove bloatware
It's unstable and only lets the device charge up to 80%, your best bet woulld just be a full flash with Odin
This guide is a bit dated but it's the best one out there. Just make sure you google the latest Odin and use all 4 firmware files when flashing https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
Click to expand...
Click to collapse
Thanks for the reply! I had tried flashing the 8.0 G930T variant last night with the latest version of Odin and the PrinceComsy version and got a Model Mismatch error. I read that the modified Odin3 v3.13.1_3B_PatcheD would let me flash the firmware and ignore the Model Mismatch error. However, I didn't go through with it because I was not sure if I would brick my phone and instead erred on the side of caution and made my post here. Would I be safe to flash the files from SM-G930T_1_20180625111401_xf3965l42p_fac onto my current device?
If your firmware files are from a trusted source like sammobile, updato or samfirmtool then it should be fine
Odin3 v3.13.1_3B_PatcheD seems to have positive feedback here on XDA so should be fine too https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Beanvee7 said:
If your firmware files are from a trusted source like sammobile, updato or samfirmtool then it should be fine
Odin3 v3.13.1_3B_PatcheD seems to have positive feedback here on XDA so should be fine too https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Click to expand...
Click to collapse
Thanks for the assist! Everything worked like a charm!
leprkon said:
Thanks for the assist! Everything worked like a charm!
Click to expand...
Click to collapse
Great glad it all worked out
leprkon said:
Thanks for the assist! Everything worked like a charm!
Click to expand...
Click to collapse
Greetings-
I apologize for jumping in an already created thread, but I think I am in the same situation, and like to verify with you both before I use the advice please. I have a SM-G930T that I just purchased, and really like to run a custom rom. But I understand I can not because I have Android 8 on it. I know how to use Odin, and have the latest version plus you guys talked about it here. I have also already downloaded the stock rom from sammobile site. What are my options? Is there a rom I can flash the phone with using Odin that would provide better performance, less G..bage, and more battery life? Is there a way for me to root the phone? I really need an app that requires the phone to be rooted.
Thanks
[email protected] said:
Greetings-
I apologize for jumping in an already created thread, but I think I am in the same situation, and like to verify with you both before I use the advice please. I have a SM-G930T that I just purchased, and really like to run a custom rom. But I understand I can not because I have Android 8 on it. I know how to use Odin, and have the latest version plus you guys talked about it here. I have also already downloaded the stock rom from sammobile site. What are my options? Is there a rom I can flash the phone with using Odin that would provide better performance, less G..bage, and more battery life? Is there a way for me to root the phone? I really need an app that requires the phone to be rooted.
Ok, so flash any unbranded Stock Rom for your device using this version of Odin which has been specifically modified to flash US devices. https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572 PatcheD.zip is the file you want to download.
Then when you have checked the phone is working ok on undrnaded firmware you can go ahead and root the device using this method which is again for US Qualcomm devices. https://www.****************/2018/0...on-galaxy-s7-and-s7-edge-on-android-8-0-oreo/
Take you time and read instructions.
Click to expand...
Click to collapse
Can I get unbranded stock firmware from sammobile? I understand the generic meaning of it, but I need more information on how to get them and what I need to know to work with them.
[email protected] said:
Can I get unbranded stock firmware from sammobile? I understand the generic meaning of it, but I need more information on how to get them and what I need to know to work with them.
Click to expand...
Click to collapse
If I understand it correctly there is no unbranded firmware for the US, its all network specific but you can flash unbranded UK firmware and it will work fine, UK BTU is the one you want from sammobile.
Load into the modified version of Odin and flash.
This is what I found, and downloading.
[email protected] said:
This is what I found, and downloading.
Click to expand...
Click to collapse
Yes that's the right one but like the beanvee and i have said there is a specific way to flash this stock then root the device.
You also need Samsung USB drivers installed so your pc can talk to your device, there's plenty of guides around how to flash with Odin and what you need to do beforehand, the only difference with you is the version of Odin your using and then the method of rooting afterwards.
cooltt said:
Yes that's the right one but like the beanvee and i have said there is a specific way to flash this stock then root the device.
You also need Samsung USB drivers installed so your pc can talk to your device, there's plenty of guides around how to flash with Odin and what you need to do beforehand, the only difference with you is the version of Odin your using and then the method of rooting afterwards.
Click to expand...
Click to collapse
Thanks. I have used Odin before, and I already downloaded the patchD version of Odin from the link. Thank you so much. I'll keep you posted on how it turns out. I still do not have a verified version of a custom recovery for this. Do you guys know of any? I found this link but the link to the suggested twrp does not work. I think it is this one. But I can not be sure. The original link points to a slightly different url.
[email protected] said:
Thanks. I have used Odin before, and I already downloaded the patchD version of Odin from the link. Thank you so much. I'll keep you posted on how it turns out. I still do not have a verified version of a custom recovery for this. Do you guys know of any? I found this link but the link to the suggested twrp does not work. I think it is this one. But I can not be sure. The original link points to a slightly different url.
Click to expand...
Click to collapse
Nope do not use that TWRP, it will flash TWRP but not boot it and you'll be stuck on Samsung logo forever.
There is still no way to unlock a Qualcomm snapdragon bootloader and i'm not sure anyone is working on it anymore.
All it means is you need to flash custom Roms via Odin or possibly the inbuilt S7 recovery, you just need to check the ROM is in a format which can be flashed that way.
With regards to finding a TWRP solution you'll have to do some serious searching on google and read everything.
There are already several de-bloated stock Roms on the forum if thats what you want to do. Root and custom recovery TWRP are two different things though, you get rooted so your good to go?
cooltt said:
Nope do not use that TWRP, it will flash TWRP but not boot it and you'll be stuck on Samsung logo forever.
There is still no way to unlock a Qualcomm snapdragon bootloader and i'm not sure anyone is working on it anymore.
All it means is you need to flash custom Roms via Odin or possibly the inbuilt S7 recovery, you just need to check the ROM is in a format which can be flashed that way.
With regards to finding a TWRP solution you'll have to do some serious searching on google and read everything.
There are already several de-bloated stock Roms on the forum if thats what you want to do. Root and custom recovery TWRP are two different things though, you get rooted so your good to go?
Click to expand...
Click to collapse
Yes root is my main goal, and you are right the debloated roms will work just fine. I can do w/o twrp. Just double checking here; since I am flashing the UK rom, and I believe one of the comments on this thread was how US images are locked tighter, would not I be able to find a UK version of TWRP for my phone? Just checking.
[email protected] said:
Yes root is my main goal, and you are right the debloated roms will work just fine. I can do w/o twrp. Just double checking here; since I am flashing the UK rom, and I believe one of the comments on this thread was how US images are locked tighter, would not I be able to find a UK version of TWRP for my phone? Just checking.
Click to expand...
Click to collapse
Now pull up a chair and listen closely.....99% of the American devices (including yours) have an extremely uncooperative Qualcommm Snapdragon cpu at it's heart and thus refuses point blank to play ball. The online community have done a fantastic job creating the modifications you are now using. The rest of the world (i'm happy to say) enjoy the S7 with an extreamly cooperative Exynos cpu at it's heart. It just loves to be fiddled with, it's a whore of a chip, constantly on the go with all kinds of neat tricks.
Anyhoo... my point is, the software has to be compatible with the hardware you catch my drift? All the cool little programs are written with a specific piece of hardware in mind, unfortunately for you guys Qualcomm is the ice queen.
cooltt said:
Now pull up a chair and listen closely.....99% of the American devices (including yours) have an extremely uncooperative Qualcommm Snapdragon cpu at it's heart and thus refuses point blank to play ball. The online community have done a fantastic job creating the modifications you are now using. The rest of the world (i'm happy to say) enjoy the S7 with an extreamly cooperative Exynos cpu at it's heart. It just loves to be fiddled with, it's a whore of a chip, constantly on the go with all kinds of neat tricks.
Anyhoo... my point is, the software has to be compatible with the hardware you catch my drift? All the cool little programs are written with a specific piece of hardware in mind, unfortunately for you guys Qualcomm is the ice queen.
Click to expand...
Click to collapse
Thank you so much. You guys are amazingly patient, and informative. Thank you for educating me, and helping me achieve my goal.
I have tried a few times but can not flash the files. I have attached screenshots, and followed the instructions here. Do you see anything I should be doing differently?
I initially thought the code came as one tar file, which I could flash, but it was a zip file, which I had to unpack.
Hello Guys i have been searching all over the internet for a few month, where do i find the boot unlock for this particular phone? I need this in order to root and install lineage OS custom rom
I really appreciate if someone has the information.
CAN ANYONE HELP PLEASE? I need to unlock bootloader for Verizon SM-G930V
ibex333 said:
CAN ANYONE HELP PLEASE? I need to unlock bootloader for Verizon SM-G930V
Click to expand...
Click to collapse
I just picked up this model myself and find myself in the same boat. My developer options do list an "OEM unlock" option. Does yours?
ibex333 said:
CAN ANYONE HELP PLEASE? I need to unlock bootloader for Verizon SM-G930V
Click to expand...
Click to collapse
Emmalfal said:
I just picked up this model myself and find myself in the same boat. My developer options do list an "OEM unlock" option. Does yours?
Click to expand...
Click to collapse
It doesn't matter, Verizon devices have locked bootloaders that can't be unlocked, don't waste your time trying, it isn't going to happen. Verizon devices have been this way for years now, I don't forsee that changing at any time in the future.
Droidriven said:
It doesn't matter, Verizon devices have locked bootloaders that can't be unlocked, don't waste your time trying, it isn't going to happen. Verizon devices have been this way for years now, I don't forsee that changing at any time in the future.
Click to expand...
Click to collapse
My device has the "oem unlock" button. Does that not matter? I was surprised as hell to find that.
Emmalfal said:
My device has the "oem unlock" button. Does that not matter? I was surprised as hell to find that.
Click to expand...
Click to collapse
You can try it but I'm pretty certain that Verizon has it locked down. There is a root method for Verizon S7 and S7 edge but no TWRP or custom ROMs that I know of.
Verizon S7 / S7 Edge [Root Guide] SM-G930V SM-G935V [NO KNOX TRIP]
Hi, I am compiling this guide for rooting the verizon variant. I also hope to fill in some gaps in the other guides. I AM NOT RESPONSIBLE FOR ANY PROBLEMS YOU MAY CAUSE OR ENCOUNTER I did not develop this, I'm only telling you how to do it...
forum.xda-developers.com
Droidriven said:
You can try it but I'm pretty certain that Verizon has it locked down. There is a root method for Verizon S7 and S7 edge but no TWRP or custom ROMs that I know of.
Verizon S7 / S7 Edge [Root Guide] SM-G930V SM-G935V [NO KNOX TRIP]
Hi, I am compiling this guide for rooting the verizon variant. I also hope to fill in some gaps in the other guides. I AM NOT RESPONSIBLE FOR ANY PROBLEMS YOU MAY CAUSE OR ENCOUNTER I did not develop this, I'm only telling you how to do it...
forum.xda-developers.com
Click to expand...
Click to collapse
Figured I'd give it the old college try. Got Odin to recognize the phone and went through the root process. All looked well until the very end. "Complete (write) operation failed."
Emmalfal said:
Figured I'd give it the old college try. Got Odin to recognize the phone and went through the root process. All looked well until the very end. "Complete (write) operation failed."
Click to expand...
Click to collapse
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Emmalfal said:
Figured I'd give it the old college try. Got Odin to recognize the phone and went through the root process. All looked well until the very end. "Complete (write) operation failed."
Click to expand...
Click to collapse
It might depend on what version/build number of stock firmware is installed on the device. That guide might be for an older version of a specific version. If what you have is newer than what the guide was written for, that might be why it failed.
Does it say anything in the guide thread about it requiring a specific stock firmware or specific bootloader version?
Emmalfal said:
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Click to expand...
Click to collapse
How about an unlocked device that can be used on Verizon's network?
Droidriven said:
It might depend on what version/build number of stock firmware is installed on the device. That guide might be for an older version of a specific version. If what you have is newer than what the guide was written for, that might be why it failed.
Does it say anything in the guide thread about it requiring a specific stock firmware or specific bootloader version?
Click to expand...
Click to collapse
I've gone through a couple different tutorials and they all seem to link to the same files that I need to download. It's been frustrating because looking for proper files for a phone this old leads to a lot of dead links. I'm probably going to give it up soon, but you know how it is. There's always "one more thing" to try. I tell you, I'm going to research like hell before I buy another phone. I need to know for sure that it can be rooted. In this case, I inherited my wife's old phone and a quick search revealed that it ought to be a piece of cake to root. There's always some little detail that trips me up. I appreciate your help with this.
Emmalfal said:
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Click to expand...
Click to collapse
Try a version of Odin from around the same time the S7/S7 edge was released onto the market. Some versions work better with certain devices, as android evolved and as Odin gets updated to newer versions for newer devices, there are slight differences along the way that can effect how it works on older devices.
If the stock firmware that you are trying to flash is older than what was already installed on the device, it will probably fail due to not allowing the device to be degraded to an older version, it's a "security" measure put there to prevent you from installing a less "secure" operating system.
Droidriven said:
How about an unlocked device that can be used on Verizon's network?
Click to expand...
Click to collapse
Yeah, that would work. It's been so long since I messed around with this stuff -- I've had the pixel for six or seven years I think -- that I've forgotten everything I once knew.
Droidriven said:
Try a version of Odin from around the same time the S7/S7 edge was released onto the market. Some versions work better with certain devices, as android evolved and as Odin gets updated to newer versions for newer devices, there are slight differences along the way that can effect how it works on older devices.
If the stock firmware that you are trying to flash is older than what was already installed on the device, it will probably fail due to not allowing the device to be degraded to an older version, it's a "security" measure put there to prevent you from installing a less "secure" operating system.
Click to expand...
Click to collapse
I'll look that up and try it out. Nothing to lose at this point. All I'm trying to flash at this point is the CF Auto Root Tar.md5, as per the instructions.
Emmalfal said:
I've gone through a couple different tutorials and they all seem to link to the same files that I need to download. It's been frustrating because looking for proper files for a phone this old leads to a lot of dead links. I'm probably going to give it up soon, but you know how it is. There's always "one more thing" to try. I tell you, I'm going to research like hell before I buy another phone. I need to know for sure that it can be rooted. In this case, I inherited my wife's old phone and a quick search revealed that it ought to be a piece of cake to root. There's always some little detail that trips me up. I appreciate your help with this.
Click to expand...
Click to collapse
No, I mean does it say anything about it requiring a specific version of stock firmware or specific version of bootloader to be already installed on the device "before" you do the rooting process described in the guide?
Sometimes these kinds of things require your device to have a certain stock software version as a starting point before the device is modified. Most of the time, if the device is ever updated to a newer version, the specific exploit that was being used to root gets patched in the update, killing the effectiveness of the exploit used to root. From that point on, chances of rooting are nil.
Emmalfal said:
Yeah, that would work. It's been so long since I messed around with this stuff -- I've had the pixel for six or seven years I think -- that I've forgotten everything I once knew.
I'll look that up and try it out. Nothing to lose at this point. All I'm trying to flash at this point is the CF Auto Root Tar.md5, as per the instructions.
Click to expand...
Click to collapse
The vulnerability that CF autoroot takes advantage of may have been patched in newer versions of firmware.
I haven't been able to root any of my devices for last 4-5 years.
Droidriven said:
No, I mean does it say anything about it requiring a specific version of stock firmware or specific version of bootloader to be already installed on the device "before" you do the rooting process described in the guide?
Sometimes these kinds of things require your device to have a certain stock software version as a starting point before the device is modified. Most of the time, if the device is ever updated to a newer version, the specific exploit that was being used to root gets patched in the update, killing the effectiveness of the exploit used to root. From that point on, chances of rooting are nil.
Click to expand...
Click to collapse
Yeah, I've been careful to download files in keeping with my specific phone, not just the G930V but the longer version of that model number, which seems super specific. Nothing works. I've tried three or four different versions of Odin at this point, but they all either fail or get stuck somewhere in the process. Probably time to start searching for a new phone. I looked around for other ways to root this s7 but i'm not finding much. I rooted the PIxel with Magisk.
Emmalfal said:
Yeah, I've been careful to download files in keeping with my specific phone, not just the G930V but the longer version of that model number, which seems super specific. Nothing works. I've tried three or four different versions of Odin at this point, but they all either fail or get stuck somewhere in the process. Probably time to start searching for a new phone. I looked around for other ways to root this s7 but i'm not finding much. I rooted the PIxel with Magisk.
Click to expand...
Click to collapse
I'm not talking about model number version, I mean the specific build number of the firmware that is installed on the device. Some guides/methods only work on specific build numbers of stock firmware or only work if a specific version of bootloader is installed on the device.
Droidriven said:
I'm not talking about model number version, I mean the specific build number of the firmware that is installed on the device.
Click to expand...
Click to collapse
Ah. I'll check that.
Emmalfal said:
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Click to expand...
Click to collapse
The S7 *can* be rooted, with lots of limitations afterwards. It just can't be BL unlocked
It could be failing due to the usb port or cable. I have an S8 that i can no longer flash only because I don't have a usb port in my pc old enough to flash it. I assume the S7 is the same way
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.