So I have what was originally a VZW 955U, flashed soon after I got it, to the unlocked 955U1 firmware using Prince's Odin and have been happy so far. Now with all the Oreo updates released except for the unlocked one, I'm wondering if I can just use prince's odin again to load the latest TMB Oreo firmware or need to do the whole engboot thing first? My current software is latest Nougat build for 955U1 and shows up as TMB//VZW.
Any thoughts?
No one? I remember reading on some of the earlier threads that if you flashed U1 first, you could then flash to the other carriers versions without the other steps but want to confirm. Don't want to deal with bootloops or softbricks.
I think you need the eng file ..but there is not oreo eng file..
Tried a lot of things, flashing tmobile oreo directly using modified and unmodified odin, trying to flash the latest Nougat builds from Tmobile using Prince Odin (the Dec one almost took and showed up as TMB/TMB/VZW but ultimately would not get updates) and then flashing back to the unlocked version but nothing worked, will likely have to do a full erase and reload the unlocked version. The eng boot file no longer works far as I can tell. Will just have to wait for the unlocked version to get updated. Sucks as this is a corporate phone and my firm has been pushing to get Oreo on all devices.
If someone has a recent guide on carrier switching the S8 , would appreciate it. Most guides here are from May of 2017 and I'm betting those files are too old to be compatible if you're on the latest Dec build for 950U1/955U1. At least doing a full reset and reflash of the 955U1 brought Wifi Calling which wasn't quite working right since I had just flashed over the 955U1 software over the stock verizon last year.
I think I'll just wait a few more weeks for the 955U1 Oreo to drop. Has to happen eventually right? Lol.
Related
So, I have a 32gb Amazon-variant XT1625 on MPJ24.139-48 with an unlocked bootloader and root. I want to update to Nougat, but it's looking like setting up to take the Amazon update is going to be a fair amount of effort; I'm wondering if it's possible to just flash the retail version of Nougat since it's looking like I'm going to have to go to a fair sum of effort anyway.
I've also heard that Moto G4 Plus ROMs will work on the G4, but I don't know the specifics on that.
i dont see why not as long as you already unlocked the bootloader prior to Moto(Lenovo) disallowed unlocking of amazon varients of the g4. heres a link to the stock nougat firmware
https://androidfilehost.com/?fid=673368273298955218
I flashed -64 retus software on mine and it immediately had two nougat updates afterwards. Still waiting for one that fixes the aboot sector vulnerability too but never know when that may come
Travisholt92 said:
I flashed -64 retus software on mine and it immediately had two nougat updates afterwards. Still waiting for one that fixes the aboot sector vulnerability too but never know when that may come
Click to expand...
Click to collapse
then you was able to flash retail version in a amazon prime phone? I have one and it dont boot if i instal a retail version.
di anybody actually get this working? I had the same issue as @iurd2007 I was able to unlock the bootloader just fine. The flash appeared to have taken successfully. But it just gets caught in a boot loop when trying to reboot the system after the flash. I followed the instructions here:
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
okay, so i've tried various roms both official and unofficial, as well as even the stock Nougat and Oreo flashable roms found here:
https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367
So far, the only ROM i've been able to get installed is omni rom 9, but it keeps crashing several apps over and over on the setup wizard. I've read somewhere that using a different version of TWRP recovery image might help. I've tried the official TWRP recovery from twrp.me, the patched arm64 version found here: https://sourceforge.net/projects/tw...3-r1-athene-arm64_rajatgupta1998.img/download , also the latest version patched for efs backup/restore here: https://forum.xda-developers.com/devdb/project/?id=29106#downloads. So far the the one that seems to work the best is the third version of TWRP. It would be nice if all these custom patches made it back into an official release, but it's probably asking a lot of a phone that is almost 4 years old at this point. and a budget friendly phone at that.
Bought an unlocked S8 from Samsung I use AT&T for service. I wouldn't be opposed to flashing/odin'ing AT&T firmware. Currently on build NRD90M.G950U1UEU1AQH3 and the August 1st security patch. I'm unsure of the best path to get to an AT&T firmware.
Go to the att section. Find the qf7 firmware and flash it with Odin.
Go to the adb update from server thread. Download all the firmwares (starting with qf7 to whatever it is) and put them on your external storage. While on qf7 reboot into recovery and select install update from storage. Flash each one, after the last one wipe data/factory reset and reboot.
So to be clear, flash AQF7 in Odin. This will get me onto an AT&T specific SM-G950U (<-- Not U1) ROM that I can then sideload the updates onto? Is sideloading the ADB updates just to speed things up vs waiting for OTAs once I'm on the correct ROM?
I flashed my at&t version to AHQ3 thinking I would be getting faster support. I am also surprised that the Unlocked AHQ3 is still on the August security patch. I really expected this version to get patched much faster or am I missing something?
msk said:
I flashed my at&t version to AHQ3 thinking I would be getting faster support. I am also surprised that the Unlocked AHQ3 is still on the August security patch. I really expected this version to get patched much faster or am I missing something?
Click to expand...
Click to collapse
The US unlocked version is the red headed stepchild of the S8 world, it really is slower for updates.
I am running AQK3 on an ATT version, think I got it from sammobile, just got one I think it was the VZW version but don't remember, didn't change the AT&T bloatware... since I did not pawn/root it in my current setup. Patch level is oct not nov...
You should have received the November security patch update last night or should be getting it sooner than later. If anything try running the manual software update on WiFi when you get a chance.
Deleted
Maybe because the Sprint Oreo will be using BLv6 so its 2 numbers behind everyone else? lol ... anyone have any thoughts about what the BL-version could possibly be for the Sprint Oreo? ... could they or would they use a BLv4 like everyone else?
that was the Sprint answer
SprintBama said:
Maybe because the Sprint Oreo will be using BLv6 so its 2 numbers behind everyone else? lol ... anyone have any thoughts about what the BL-version could possibly be for the Sprint Oreo? ... could they or would they use a BLv4 like everyone else?
Click to expand...
Click to collapse
If anything, they would change it to v7. Maybe they are waiting for a merger, which could happen next week
I checked for update today and got 1627.64mb g930pvpu6cre7 Samsung experience 9.0 with oreo.
I haven't gotten an update from Sprint on my S7 since December 2016. I am still on some random Nougat beta version.
I thought a brand new firmware update to Oreo would reset whatever bug was in there causing this, but it looks like one person in my house got the Oreo update and mine is still saying I am up to date when I check manually.
Is there no longer an ODIN for macOS? I thought there was one, but I used it on another Mac maybe 4 years ago when I was on my S3 and rooting it. Doesn't seem to exist anymore.
Just received oreo on my s7 for boost. So far I'm not impressed. I was really hoping for Dolby on this but guess not. The build number is SMG930PVPU6CRE7
kalala said:
I haven't gotten an update from Sprint on my S7 since December 2016. I am still on some random Nougat beta version.
I thought a brand new firmware update to Oreo would reset whatever bug was in there causing this, but it looks like one person in my house got the Oreo update and mine is still saying I am up to date when I check manually.
Is there no longer an ODIN for macOS? I thought there was one, but I used it on another Mac maybe 4 years ago when I was on my S3 and rooting it. Doesn't seem to exist anymore.
Click to expand...
Click to collapse
On Mac you can use Heimdall to flash the latest Nougat firmware then update through OTA to Oreo. Because there isn't any firmware file yet on Updato or Sammobile.
i manfully updated @ 4:15. they sent it @ 1627.64 mb. still downloading. when I got my att update I tried all the batch root methods for my 935a. saving magisk for last bc I didn't have the boot.img for the cre4 update.
I I only had the "att beta" update from March. long story short it won't boot with the nougat eng.boot. I gave it an hour. I cleared the cache, factory reset, tried to add flash all of the earlier img files I had for oreo, nothing worked. had to flash it back to nougat bra1. I immediately requested the update again. they approved. the next day I attempted to flash magisk 16.4. w/ the modified odin 3.1.3 version. it wouldn't flash. with the cre4 boot.tar in hand, I tried every method on gods green earth to gain some sort of r/w access. it was late, I was tired, I flashed the eng boot. once again it was stuck at the Samsung boot logo. it wouldn't allow me into recovery to push the cre4 update zip. once again I'm back to bra1 nougat. I booted into recovery & updated it from the sd card. when it booted I noticed it wasn't anywhere as clean & polished as the ota I had twice. I've flashed back to brd1 ten times, & requested the ota. after smart switch, I used all the avail windows software I could acquire & kept trying, they won't send it. but they did provide me with a new picture for my samsung account. I'll post it later. gotta check out this 930p oreo.
razor001_ said:
On Mac you can use Heimdall to flash the latest Nougat firmware then update through OTA to Oreo. Because there isn't any firmware file yet on Updato or Sammobile.
Click to expand...
Click to collapse
I don't think Heimdall works on High Sierra or even Sierra anymore.
I'm wanting to move to a SM-930U version of stock android on my 930P. But in struggling to do so for the past couple of weeks I finally figured out that sprint as updated the bootloader to version 5 and most of the firmware images for 930U are version 4 (android 7 nugut). (PU4 vs PU5) which results in a Odin fuse error.
The phone is currently nagging me to go from PU5BQL1 to BU6BRD2. If I understand the nameing convention that would move me to version 6 of the bootloader.
What are the odds I can move to oreo for 930U and avoid the bootloader fuse issue? I think I also understand that as of this posting date a 930U oreo firmware has not been released?
schmism said:
I'm wanting to move to a SM-930U version of stock android on my 930P. But in struggling to do so for the past couple of weeks I finally figured out that sprint as updated the bootloader to version 5 and most of the firmware images for 930U are version 4 (android 7 nugut). (PU4 vs PU5) which results in a Odin fuse error.
The phone is currently nagging me to go from PU5BQL1 to BU6BRD2. If I understand the nameing convention that would move me to version 6 of the bootloader.
What are the odds I can move to oreo for 930U and avoid the bootloader fuse issue? I think I also understand that as of this posting date a 930U oreo firmware has not been released?
Click to expand...
Click to collapse
almost zero... asuming that Oreo for "U" Variants step up with BL on this month maybe next one, is something pausible but stepping up two versions in any short time is questionable... but who knows. The best you can do is wait this or the next month for BL update on U variants.
To be clear I'm still on version 5. I will continue to put off the upgrade to 6.
Literally no matter what I do. I cannot flash ANYTHING in Odin to either revert back to 7.0 or stock 8.0. Its not flashing any version of 7 or 8 and its not flashing any U firmware or AT&T firmware.
What am I doing wrong. I flashed 8.0 with the intent to be able to revert back to stock 7.0 once official Oreo rolled out and I literally cant do anything in Odin. I've tried odin 3.13 and 3.12 prince version. HALP
update: flashed G930UUEU4BRD1 using odin 3.12 successfully. phew
As far as I know, the newest Oreo version of AT&T is CRE4, not BRD6 as you say
SKv.DinDin said:
As far as I know, the newest Oreo version of AT&T is CRE4, not BRD6 as you say
Click to expand...
Click to collapse
You may be speaking about where I said CRD6, that is a version of Oreo that doesn't have much difference than the latest version of Oreo CRE4. Most of them after release have been minor changes. I was not flashing back to BRA1 to constantly flash the newest update of Oreo. I have an unlocked s7 so I can flash any carrier but eventually when the official oreo firmware comes out for either tmobile or the unlocked 930 varient i will be switching back to OTA updates
aarongotgame said:
You may be speaking about where I said CRD6, that is a version of Oreo that doesn't have much difference than the latest version of Oreo CRE4. Most of them after release have been minor changes. I was not flashing back to BRA1 to constantly flash the newest update of Oreo. I have an unlocked s7 so I can flash any carrier but eventually when the official oreo firmware comes out for either tmobile or the unlocked 930 varient i will be switching back to OTA updates
Click to expand...
Click to collapse
You tried with patched odin? Odin v3.13.1 3B.
anarasgarli said:
You tried with patched odin? Odin v3.13.1 3B.
Click to expand...
Click to collapse
The issue was probably that I needed to put home file in csc and exclude the csc file and then factory reset and clear caches. I probably ended up factory reset before Odin and didn't activate USB debug or the files I was using were corrupt. Since then I've just flashed TMobile Oreo that came out a few days ago and I'm gonna just use official ota for future updates
aarongotgame said:
The issue was probably that I needed to put home file in csc and exclude the csc file and then factory reset and clear caches. I probably ended up factory reset before Odin and didn't activate USB debug or the files I was using were corrupt. Since then I've just flashed TMobile Oreo that came out a few days ago and I'm gonna just use official ota for future updates
Click to expand...
Click to collapse
Looks like same problem with Galaxy S8, just search Stuck 32% error at Galaxy s8.
Reverting back from Oreo to either Nougat or Marshmallow
I am a newbie here.. Recently my ATT Galaxy S7 received Oreo upgrade and I am not at all liking it.
Can someone please guide me if it's possible to go back to Nougat or even marshmallow (preferable). If yes, what would steps for same..
My device is SM-G930A. Originally ATT device and now it's unlocked by ATT.
My device is currently NOT rooted , I am OK with rooting it.. I would appreciate if someone can help me with steps for same as well..
Thanks in advance..
I'm trying to wrap my head around all this, but my head is spinning. In December I was looking to get my S7 flat to 7.0 rooted. I discovered that root can only be achieved with eng kernel and that has its drawbacks. I decided I don't need/want root at that cost of stability, performance and battery life. Somehow I settled on installing a "U" variant that seemed to work well with less Verizon bloat. I couldn't get the S Health app and monitors on the back of the phone working, but I figured I could live with that. Recently I tried casting my phone to a Amazon Fire Stick and discovered the "Smart View" button is missing and I couldn't figure out how to get it back, so I might've lost that too. I also discovered in the past nine months Oreo is out with additional features and I figure if I'm going to go through the hassle of reinstalling, I might as well upgrade.
So, I hear root with Oreo is better than it's been, but not perfect, so I'l like to upgrade to unrooted oreo, either stock or debloated (if such a version exists without tradeoffs). Is there a certain version I'm supposed to go to so there's some flexibility in reinstalling the OS? Like I know sometimes versions of software are released that upgrade little, but patch exploits.
Also, if I do get whatever version of Oreo installed, do I then ignore OTA updates going forward? Is there any advantage to that?
And I can use the mobile hotspot feature. I don't think I have any special plan to accommodate that, nor do I have an unlimited plan (with Verizon). Is that intended, or is that from the "U" variant. Would I lose that?
My phone's info is below, if anyone can decipher what I did:
Model #: SM-G930U
Android Version: 7.0
Baseband Version: G930UUEU4BQE2
Kernel Version: 3.18.31
Build #: NRD90M.G930UUEU4BQE2
I apologize, I know my nomenclature isn't up to snuff. I realize that this stuff isn't for the casual user, at least on this phone. It's very hard to figure out what's current if you're not in the loop.
Thank you for any help you can offer.
If possible, I'd try just doing an Odin of the full Verzion equivalent to what you are on. That has the best chance of being compatible with the bootloader you are on. If not, you may have to downgrade to earlier U variant and then switch to equiv V variant. If I recall correctly the *BRA1 firmware intersected on all carrier releases. In my case in the past, I was on too new of an AT&T variant and it wouldn't let me switch because the model didn't match. I had to switch to the generic U variant and then go to Verizon variant after.
In your case I'd try either of these in full Odin form (and may need princecomsy Odin or other that will force it):
G930VVRS4BQC9 - Closest Verizon V variant firmware that is released same month as your current version (a couple weeks later)
G930VVRU4CRE5 - June 5th 2018 Verizon V variant firmware based on 8.0
Edit:
Alternatively I think you should be able to go to the latest U generic variant 8.0 firmware, whatever that would be. I think that's G930UUEU4CRG2 at the moment
djh816 said:
If possible, I'd try just doing an Odin of the full Verzion equivalent to what you are on. That has the best chance of being compatible with the bootloader you are on. If not, you may have to downgrade to earlier U variant and then switch to equiv V variant. If I recall correctly the *BRA1 firmware intersected on all carrier releases. In my case in the past, I was on too new of an AT&T variant and it wouldn't let me switch because the model didn't match. I had to switch to the generic U variant and then go to Verizon variant after.
In your case I'd try either of these in full Odin form (and may need princecomsy Odin or other that will force it):
G930VVRS4BQC9 - Closest Verizon V variant firmware that is released same month as your current version (a couple weeks later)
G930VVRU4CRE5 - June 5th 2018 Verizon V variant firmware based on 8.0
Edit:
Alternatively I think you should be able to go to the latest U generic variant 8.0 firmware, whatever that would be. I think that's G930UUEU4CRG2 at the moment
Click to expand...
Click to collapse
Thank you for the reply! I really wasn't expecting any replies, there's just too much going on in my post.
I backed up everything tonight so when I flash it I can wipe everything and do it right. This sammobile site lists all the firmware updates and that helped somewhat demystify things. Is it true that the fifth digit from the right of build is the bootloader? If that's the case, does that mean I can install any version from the last MM update through the september oreo update and upgrade and downgrade between them without issue since they all have a "4" for that digit? Is the bootloader the thing that sometimes gets updated, preventing downgrades or is the baseband and modem also something that I need to consider. If I just install the latest verizon oreo update, am I limited in downgrading?
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930V/
Umbra. said:
Thank you for the reply! I really wasn't expecting any replies, there's just too much going on in my post.
I backed up everything tonight so when I flash it I can wipe everything and do it right. This sammobile site lists all the firmware updates and that helped somewhat demystify things. Is it true that the fifth digit from the right of build is the bootloader? If that's the case, does that mean I can install any version from the last MM update through the september oreo update and upgrade and downgrade between them without issue since they all have a "4" for that digit? Is the bootloader the thing that sometimes gets updated, preventing downgrades or is the baseband and modem also something that I need to consider. If I just install the latest verizon oreo update, am I limited in downgrading?
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930V/
Click to expand...
Click to collapse
Purely anecdotal but in my case I think the newer version I had was the issue. I don't believe you are limited in downgrading if you have a full signed odin of your current model variant that you can downgrade too. I think the main issues come in when you are going from a different model and a newer/older firmware. If you are staying on latest G930V Verizon firmware for example, I believe you could downgrade as far back as needed with full Odin. Just not necessarily U variant firmware without finding the crossover point with that firmware (like AT&T and Verizon variants both on BRA1 firmware). I could be mistaken on the requirements but messing around with flashing an older rom with same 930 variant, then switching to a new variant from that may work. In my case I had to downgrade to BRA1 AT&T, then switch to BRA1 generic 930U, then switch to Verizon BRA1 930V. Also the stock version of Odin didn't like me switching variants but princecomsy version worked (not sure if that works well with new firmwares though). As you say though, there may be some limits in downgrading depending on what bootloader you are on. I don't think I've personally had a situation where I couldn't but with all those efuses out there who knows..But even then you should be able to pivot to another variant of similar release date
djh816 said:
Purely anecdotal but in my case I think the newer version I had was the issue. I don't believe you are limited in downgrading if you have a full signed odin of your current model variant that you can downgrade too. I think the main issues come in when you are going from a different model and a newer/older firmware. If you are staying on latest G930V Verizon firmware for example, I believe you could downgrade as far back as needed with full Odin. Just not necessarily U variant firmware without finding the crossover point with that firmware (like AT&T and Verizon variants both on BRA1 firmware). I could be mistaken on the requirements but messing around with flashing an older rom with same 930 variant, then switching to a new variant from that may work. In my case I had to downgrade to BRA1 AT&T, then switch to BRA1 generic 930U, then switch to Verizon BRA1 930V. Also the stock version of Odin didn't like me switching variants but princecomsy version worked (not sure if that works well with new firmwares though). As you say though, there may be some limits in downgrading depending on what bootloader you are on. I don't think I've personally had a situation where I couldn't but with all those efuses out there who knows..But even then you should be able to pivot to another variant of similar release date
Click to expand...
Click to collapse
I don't still know about downgrading and switching, but I can live with that. I took the plunge and opted to install the latest Verizon firmware last night. Surprisingly I was able to just install it over the U firmware with basic Odin. I Then went into recovery and did a factory reset. It's gonna take awhile to set everything up how I like, but S Health works, I've got the Smart view toggle (didn't get to test it yet), mobile hotspot works, but I get some cool new features to explore (I especially like being to able to have more control over what notifications show for each app, instead of a blanket on/off). Not crazy about the new AOD font, but I'll get used to it. Thanks for nudging me in the right direction
Umbra. said:
I don't still know about downgrading and switching, but I can live with that. I took the plunge and opted to install the latest Verizon firmware last night. Surprisingly I was able to just install it over the U firmware with basic Odin. I Then went into recovery and did a factory reset. It's gonna take awhile to set everything up how I like, but S Health works, I've got the Smart view toggle (didn't get to test it yet), mobile hotspot works, but I get some cool new features to explore (I especially like being to able to have more control over what notifications show for each app, instead of a blanket on/off). Not crazy about the new AOD font, but I'll get used to it. Thanks for nudging me in the right direction
Click to expand...
Click to collapse
Woo, welcome back to the walled garden lol.. BTW I found in the themes/lockscreen app (can't recall where) they had the old lockscreen font I preferred as a clock option