Related
Hey everyone!
It's 5:47am on this Tuesday, November 9th, and I have a firmware update notification in the status bar.
What should I do?
Devs?
: )
Are you running a custom Rom or stock? If stock, what is your current software and firmware version.
cswroe said:
Are you running a custom Rom or stock? If stock, what is your current software and firmware version.
Click to expand...
Click to collapse
I'm running a custom rom, SlideMeRoot, with the first Mytouch Slide update applied.
Or SlideMeRoot is a version of the stock rom?
Then:
Firmware: 2.1-update1
Software number: 1.27.531.1
Images attached.
They are trying to give you the OTA. Don't take it if you like your root.
RUbernerd said:
They are trying to give you the OTA. Don't take it if you like your root.
Click to expand...
Click to collapse
I know that's why I've posted here.
: )
There hasn't been a text message sent out about any other updates. This is them trying to ruin your root access.
RUbernerd said:
There hasn't been a text message sent out about any other updates. This is them trying to ruin your root access.
Click to expand...
Click to collapse
Seriously doubt it.
: )
I also haven't heard about any privilege revocation updates in that case.
The OTA broke root for so many people it isn't funny.
RUbernerd said:
The OTA broke root for so many people it isn't funny.
Click to expand...
Click to collapse
I have the modified radio update already installed if that's what you mean.
It's displayed in the last image in the images I attached above.
Stratis1978 said:
I have the modified radio update already installed if that's what you mean.
It's displayed in the last image in the images I attached above.
Click to expand...
Click to collapse
Slidemeroot uses is older than ota, they are sending you the rom that cr modded(1.3.x). Upgrade to cr for new radio and it will go away.
Edit: read rest of your post,it may be a small hotfix, probably not 2.2 .Maybe 2.1.1
Sent from my T-Mobile MTS/G1 using XDA App
Ace42 said:
Slidemeroot uses is older than ota, they are sending you the rom that cr modded(1.3.x). Upgrade to cr for new radio and it will go away.
Edit: read rest of your post,it may be a small hotfix, probably not 2.2 .Maybe 2.1.1
Sent from my T-Mobile MTS/G1 using XDA App
Click to expand...
Click to collapse
I don't know what it is but interesting none-the-less.
I'll consider it over a coffee.
So ummm who wants to take apart this BRAND new update and see what it is?
I've got alogcat installed and ready...
Stratis1978 said:
So ummm who wants to take apart this BRAND new update and see what it is?
I've got alogcat installed and ready...
Click to expand...
Click to collapse
Sounds like you've got the OTA many of us have had for quite some time. Take a look at my signature; if your build resembles my current ROM it's an older OTA. Post some screen shots as you did earlier so we can see the change since you've updated. Thanks.
NJAZ said:
Sounds like you've got the OTA many of us have had for quite some time. Take a look at my signature; if your build resembles my current ROM it's an older OTA. Post some screen shots as you did earlier so we can see the change since you've updated. Thanks.
Click to expand...
Click to collapse
I've also had that update for quite some time.
So before anyone else suggests that very update again in this thread, bear that in mind.
Well what are you waiting for? Go ahead and transfer it from the phone and post it
Annnd to quote myself:
Stratis1978 said:
So ummm who wants to take apart this BRAND new update and see what it is?
I've got alogcat installed and ready...
Click to expand...
Click to collapse
Stratis1978 said:
I've also had that update for quite some time.
So before anyone else suggests that very update again in this thread, bear that in mind.
Click to expand...
Click to collapse
Bear in mind the OTA update was more than just a radio upgrade ... which from your initial post appears to be the extent of the OTA you have had for quite some time. Interested to see the updated screen shots though ...
fermunky said:
Well what are you waiting for? Go ahead and transfer it from the phone and post it
Click to expand...
Click to collapse
Dude (and everyone else who reads this thread), please -- I'm asking for guidance here.
So if you want me to do something, articulate what that is.
I will transfer the update from my phone and post it here, just tell me HOW.
Anything else you need: also articulate what that is and how.
NJAZ said:
Bear in mind the OTA update was more than just a radio upgrade ... which from your initial post appears to be the extent of the OTA you have had for quite some time. Interested to see the updated screen shots though ...
Click to expand...
Click to collapse
It was more than a radio upgrade; it was also a fix for other slide conundrums.
So you want me to apply this OTA update and post screen shots?
Because that would be unwise for a rooted phone...
It's line! Got it on my phone this morning. Xt1058.
Awesome awesome
Live, not line.
Nobody's excited??
R3dbeaver said:
Live, not line.
Nobody's excited??
Click to expand...
Click to collapse
Not if you don't have the captured ZIP/OTA file to share xP
Downloaded and installed on my stock X, and it seems fine - other than a repeated "Unfortunately, Moto has stopped" message after boot up. Anyone else on Rogers seeing this?
The Moto app opens fine, though it seems to be missing driving mode now?
Got the notification last night. Haven't taken the plunge yet.
Hoping this means the ATT version isn't too far off
thedosbox said:
Downloaded and installed on my stock X, and it seems fine - other than a repeated "Unfortunately, Moto has stopped" message after boot up. Anyone else on Rogers seeing this?
The Moto app opens fine, though it seems to be missing driving mode now?
Click to expand...
Click to collapse
In case anyone else faces this, it was resolved this by clearing the "Moto", "Moto Actions", "Moto Display" and "Moto Voice" app data.
[edit]
One annoyance is that the LTE icon constantly flashes on/off while I'm at home - it used to switch between LTE and HSPA. Anyone know of a way to revert to the previous behaviour? The constant sliding of notification icons as it appears and disappears is distracting.
yeah i am waiting for att version hope that they dont lock bootloader just like they did in 4.4.4
rjcrystal199 said:
yeah i am waiting for att version hope that they dont lock bootloader just like they did in 4.4.4
Click to expand...
Click to collapse
I'm betting they will.
stealtheye said:
Not if you don't have the captured ZIP/OTA file to share xP
Click to expand...
Click to collapse
I think I captured it before updating using OTA snatcher, but it weirdly says it's build 212.etc instead of 222. However the size of the file (695) matches the 5.1 OTA.
Plus the inside of the zip looks like the leaked 5.1 soaktest I had seen, so I think it's the one we're looking for.
...
Trying to install it as I write (OTA failed, I must have forgotten to "restock" something), will keep you updated!
The zip:
owait
...I can't put it yet because I didn't post enough yet.
I created an account in order to post here.
Can I cry?
Yes go ahead and cry, it's OK dawg
Wireless...
Got the update to work on my phone, yeahz!
Sooo, if there isn't anyone who has captured the ota, maybe I could send the link to someone who can post it?
alenym said:
I think I captured it before updating using OTA snatcher, but it weirdly says it's build 212.etc instead of 222. ...
Click to expand...
Click to collapse
This is because it shows what build it is upgrading FROM
Sent from my XT1058 using XDA Free mobile app
alenym said:
I think I captured it before updating using OTA snatcher, but it weirdly says it's build 212.etc instead of 222. However the size of the file (695) matches the 5.1 OTA.
Plus the inside of the zip looks like the leaked 5.1 soaktest I had seen, so I think it's the one we're looking for.
...
Trying to install it as I write (OTA failed, I must have forgotten to "restock" something), will keep you updated!
The zip:
owait
...I can't put it yet because I didn't post enough yet.
I created an account in order to post here.
Can I cry?
Click to expand...
Click to collapse
Yeah with OTAs they are named by what they are updating so it is 5.1. If it fails that means you're missing something stock or have root or something not stock. So factory reset and try. As for the poet issue...we all had to through it. Just go around other forums. Post and just talk about stuff and then post the link. What is the name of your OTA?
Is it me or did the on-screen buttons gets smaller?
stealtheye said:
Yeah with OTAs they are named by what they are updating so it is 5.1. If it fails that means you're missing something stock or have root or something not stock. So factory reset and try. As for the poet issue...we all had to through it. Just go around other forums. Post and just talk about stuff and then post the link. What is the name of your OTA?
Click to expand...
Click to collapse
Blur_Version.212.144.12.ghost_row.RCI.en.CA.zip
I went back to stock using the 4.4.4 RCI I found on a filefront folder with all the Moto X stock FW that was posted on this forum (no link, sorry ) and then accepted the 1.2 mb minor OTA. The one correcting the audio on emergency calls on first boots. This one installed itself without any problem but the 5.1 didn't.
I tried disabling xposed and stuff for the verification to work but it failed. I had flashed the new framework to make the new Moto app work some time ago (I really wanted to name my phone Félix), so it was probably blocking the OTA update. So in the end I just used RDS lite to flash everything back to stock (after doing a backup ofc) and then it worked. Yayz.
And yes, I think the buttons are a bit smaller. I've had the uncanny feeling of my screen being bigger.
The lock of the active notifications is also a tad smaller and "rounder".
3/10!
Courtesy of our new fellow "alenym" here is the link to the OTA
https://drive.google.com/file/d/0Bx8c_ewmmyNzT1lrbVUwT2FXV1U/view?usp=sharing
Does anyone know how to modify the signal status icons (LTE, 3G, etc) next to the signal bar? I'm not a fan of how Rogers opted for the larger icons and use 3G instead of H and H+. I've tried using the Xposed module SignalIconsAOSP and all it is able to do is make the icons smaller. It's not able to switch the 3G icon to H/H+.
i used xposed framework and gravity and that took care of it under KK. I am not sure about Lolipop yet
The easiest solution would be to always be on LTE, ofc.
However, I'm with a rogers xt1058 and it still uses H and H+ instead of 3G (unless I have really bad coverage), so I'm not sure if your problem comes from Rogers' choice of icons or Rogers' coverage... (See below)
Otherwise I know the brazilian stock firmware for the Moto X has different icons than Roger and can be installed on Rogers' xt1058 (I installed it and kept it for a few days before finding stock Rogers FW). It displays 4G instead of LTE and it's quite smaller than the huge LTE. Didn't pay attention to the 3G though.
You could give it a try I guess if nothing else works. The only inconvenient is that the only system languages are English and Portuguese, so if you want to yell at your phone in French like me it may be a problem.
MOB31E is up now (along with first Nougat patch for those other devices)
https://dl.google.com/dl/android/aosp/shamu-mob31e-factory-051e2d25.zip
so we still remain in 6.0.1?
thetransit123 said:
so we still remain in 6.0.1?
Click to expand...
Click to collapse
Yes, still Marshmallow. Oddly, this one is named differently than the last couple monthly security updates. It does follow that mid-July performance numbering system.
The 6p is still on 6.0.1 too. So don't get too discouraged!
Tried to download the sept security update and the google ota link and files not there: 404. That’s an error. That’s all we know.
ryancell said:
Tried to download the sept security update and the google ota link and files not there: 404. That’s an error. That’s all we know.
Click to expand...
Click to collapse
I had that earlier too, but it's working now.
Preparing for nougat?
we probably wont get nougat until they release the "pixel phones"
i can see two new image same time for shamu, i can understand Google.
/system/etc/hosts
anyone experiencing issues with adaway (or a custom /system/etc/hosts file) and this image? MOB31E appears to be a minor bump, but i thought i'd ask around before nuking my main device.
Voight Kampff said:
anyone experiencing issues with adaway (or a custom /system/etc/hosts file) and this image? MOB31E appears to be a minor bump, but i thought i'd ask around before nuking my main device.
Click to expand...
Click to collapse
I'm using Magisk's superuser and systemless AdAway on the new update with no problems.
JimSmith94 said:
I'm using Magisk's superuser and systemless AdAway on the new update with no problems.
Click to expand...
Click to collapse
some links, please?
thanks
gothy.gothy said:
some links, please?
thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
http://forum.xda-developers.com/showthread.php?t=2190753
AlexX-DE said:
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
http://forum.xda-developers.com/showthread.php?t=2190753
Click to expand...
Click to collapse
Thanks
Can anyone tell me the difference between MMB30W and MOB31E? I was going to sideload the September OTA, but not sure which one I am supposed to use. Haven't found any details anywhere. I'm currently on MMB30R, but I hadn't noticed there were multiple images released each month when I've sideloaded until now so not sure if I'm supposed to be on that image or not?
gill30 said:
Can anyone tell me the difference between MMB30W and MOB31E? I was going to sideload the September OTA, but not sure which one I am supposed to use. Haven't found any details anywhere. I'm currently on MMB30R, but I hadn't noticed there were multiple images released each month when I've sideloaded until now so not sure if I'm supposed to be on that image or not?
Click to expand...
Click to collapse
MMB has the radio that the carriers have agreed on, it's for their own version of Marshmallow. MOB has a newer radio. If you sideload it anyway, use the most recent.
If I am currently on M0B30W Project Fi, I see there are two builds below mine...which version below would I update to for the security patches safely if I'm stock?
6.0.1 (MMB30W) or 6.0.1 (MOB31E)
Voight Kampff said:
anyone experiencing issues with adaway (or a custom /system/etc/hosts file) and this image? MOB31E appears to be a minor bump, but i thought i'd ask around before nuking my main device.
Click to expand...
Click to collapse
No issue, but i did the usual...booted into twrp and deleted a couple of unneeded keyboards to make space.
ryancell said:
If I am currently on M0B30W Project Fi, I see there are two builds below mine...which version below would I update to for the security patches safely if I'm stock?
6.0.1 (MMB30W) or 6.0.1 (MOB31E)
Click to expand...
Click to collapse
Either one will work. They are exactly the same except for the radio. The MMB images contain an older radio that carriers have approved and the MOB images contain a newer radio that hasn't been approved by carriers yet. You could try the MOB image and if the radio performance isn't up to par you could extract the one from the MMB image. I've always used the MOB images and haven't had any radio issues, but I'm not on Project Fi...
Voight Kampff said:
anyone experiencing issues with adaway (or a custom /system/etc/hosts file) and this image? MOB31E appears to be a minor bump, but i thought i'd ask around before nuking my main device.
Click to expand...
Click to collapse
Nope, but I always delete useless preinstalled junk to make space.
I just got the OTA update notification for the VZW Pixel, fully stock, unrooted, locked bootloader. Never joined the beta either. So now we'll see if any of these BT and reboot issues have been resolved. Here's hopin'
Update size: 938.4 MB
bobby janow said:
I just got the OTA update notification for the VZW Pixel, fully stock, unrooted, locked bootloader. Never joined the beta either. So now we'll see if any of these BT and reboot issues have been resolved. Here's hopin'
Update size: 938.4 MB
Click to expand...
Click to collapse
do you have always on ambient display with this update?
Tech_Savvy said:
do you have always on ambient display with this update?
Click to expand...
Click to collapse
Yes I do. Everything seems to have rolled over fine. Update screen was not the bouncing thingies but simply the G logo. Haven't rebooted to see.. oh just a little of the dots, then a quick G and then it was up. Like maybe 10 seconds for a reboot. Wow.
bobby janow said:
I just got the OTA update notification for the VZW Pixel, fully stock, unrooted, locked bootloader. Never joined the beta either. So now we'll see if any of these BT and reboot issues have been resolved. Here's hopin'
Update size: 938.4 MB
Click to expand...
Click to collapse
I just downloaded and installed it with a unlocked bootloader no problem. It's still unlocked and I just rooted it.
All the OTA images are available at https://developers.google.com/android/ota. You can all download as you wish.
henrique.mageste said:
All the OTA images are available at https://developers.google.com/android/ota. You can all download as you wish.
Click to expand...
Click to collapse
Anyone know which one is for Verizon?
jackdubl said:
Anyone know which one is for Verizon?
Click to expand...
Click to collapse
The .012 image. It is meant for all the phone's not covered by the .011 build.
Always On Ambient Display
Either, this didn't make it through in my update somehow or I'm overlooking the setting.
Can anyone offer any help on enabling this feature?
Thanks!
Man, that's annoying, I still haven't gotten it on my Project Fi pixel. I left vzw because I never got updates!
skyline315 said:
Either, this didn't make it through in my update somehow or I'm overlooking the setting.
Can anyone offer any help on enabling this feature?
Thanks!
Click to expand...
Click to collapse
I'd like to know as well
Where is the setting for always on ambient display? All I see is the regular ambient display, where it turns on for new notifications.
speedy859 said:
Where is the setting for always on ambient display? All I see is the regular ambient display, where it turns on for new notifications.
Click to expand...
Click to collapse
I've asked around and consensus seems to be that it was NOT included in this update after all. Looks like they're saving it for the Pixel 2.
JoeHockey said:
Man, that's annoying, I still haven't gotten it on my Project Fi pixel. I left vzw because I never got updates!
Click to expand...
Click to collapse
Im on fi I just downloaded the ota and then sideloaded it.
Go to settings - display - advanced and it will be towards the bottom.
Nevermind, misread. It is only for notifications. You can make it turn on when you pick it up though. By turning on "lift to check phone"
Sent from my Pixel using XDA Free mobile app
Misterxtc said:
I just downloaded and installed it with a unlocked bootloader no problem. It's still unlocked and I just rooted it.
Click to expand...
Click to collapse
Hi,
Can you let me know what version of twrp.img u used for fastboot? I tried rc1 and alpha 1. Both locked my phone up.
Really appreciate ur help
randogg65 said:
Hi,
Can you let me know what version of twrp.img u used for fastboot? I tried rc1 and alpha 1. Both locked my phone up.
Really appreciate ur help
Click to expand...
Click to collapse
I use the modded one for O here. You need to fastboot and load TWRP every time you use it because it is not flashable yet.
Misterxtc said:
I just downloaded and installed it with a unlocked bootloader no problem. It's still unlocked and I just rooted it.
Click to expand...
Click to collapse
which root method did you use since you didn't sideload? thanks.. jforgive me if it's been posted. ust getting back onto the forums and currently reading up
Misterxtc said:
I use the modded one for O here. You need to fastboot and load TWRP every time you use it because it is not flashable yet.
Click to expand...
Click to collapse
Thanks! Really appreciate it
honourbound68 said:
which root method did you use since you didn't sideload? thanks.. jforgive me if it's been posted. ust getting back onto the forums and currently reading up
Click to expand...
Click to collapse
I can't remember where I got the file I used so I would say try here.
Meanwhile...
cbusm30 said:
I'd like to know as well
Click to expand...
Click to collapse
There are also 8.0.0 factory images as well (along with the usual older factory images) - they are all here: http://www.infinitiofsuitland.com/VehicleSearchResults?search=new
To play it safe, I grabbed one 7.1.2 and one 8.0.0 factory image for the Pixel to put through the wringer (since this would be the first Pixel I've ever put through the paces).
Pretty much exactly the same across all the models with minor differences. I'll try to upload new dumps when new builds hit.
DOWNLOAD:
From T-Mobile GS8+ Build OPR1.170623.026.G955USQU1ZQJJ
How are you dumping it, and what's keeping you from dumping the update file?
Can anyone with this update dial *#2263# and post a screenshot. It should list the supported bands, I'd like to know if they enabled Band 46.
Thanks.
milan03 said:
Can anyone with this update dial *#2263# and post a screenshot. It should list the supported bands, I'd like to know if they enabled Band 46.
Click to expand...
Click to collapse
Yes, they did
milan03 said:
Can anyone with this update dial *#2263# and post a screenshot. It should list the supported bands, I'd like to know if they enabled Band 46.
Click to expand...
Click to collapse
Once I read up on what Band 46 is, I decided to do a speed test. Apparently, LAA is in full effect in Memphis :laugh: :victory:
Info: https://www.qualcomm.com/invention/technologies/lte/laa
docnok63 said:
Once I read up on what Band 46 is, I decided to do a speed test. Apparently, LAA is in full effect in Memphis :laugh: :victory:
Info: https://www.qualcomm.com/invention/technologies/lte/laa
Click to expand...
Click to collapse
I got double the speeds I normally get. Need to test some more though.
If we flash this do we get the OTAs whenever they release an update?
mperez19 said:
If we flash this do we get the OTAs whenever they release an update?
Click to expand...
Click to collapse
If you're not in the Beta program itself, I'd say there's 98% chance no as the update is tied to your Samsung account. The OP states that he'll upload any future Beta updates, though. Of course, you'll always be able to flash the official Oreo build once it's released (probably without wiping data.)
docnok63 said:
If you're not in the Beta program itself, I'd say there's 98% chance no as the update is tied to your Samsung account. The OP states that he'll upload any future Beta updates, though. Of course, you'll always be able to flash the official Oreo build once it's released (probably without wiping data.)
Click to expand...
Click to collapse
Hmm. I'm currently in the Unlocked Model beta. If i flash back to TMobile do you think it would count me in the beta still? Since its tied to the account?
mperez19 said:
Hmm. I'm currently in the Unlocked Model beta. If i flash back to TMobile do you think it would count me in the beta still? Since its tied to the account?
Click to expand...
Click to collapse
Probably, since the account and Beta are tied to your IMEI. If not, you can flash back to unlocked and upgrade again. You won't lose your Beta status unless you leave the program.
0vermind said:
Pretty much exactly the same across all the models with minor differences. I'll try to upload new dumps when new builds hit.
DOWNLOAD:
From T-Mobile GS8+ Build OPR1.170623.026.G955USQU1ZQJJ
Click to expand...
Click to collapse
Assuming this is applied through recovery with ADB sideload right? Or?
I tried flashing it in recovery using "update via SD card" and pointed to the zip file and I got an error with wrong footer.
bogdi1988 said:
Assuming this is applied through recovery with ADB sideload right? Or?
I tried flashing it in recovery using "update via SD card" and pointed to the zip file and I got an error with wrong footer.
Click to expand...
Click to collapse
I'm wndering what would be a proper way of flashing the modem for us that are rooted without losing root? I'm still on the August build.
Thanks.
milan03 said:
I'm wndering what would be a proper way of flashing the modem for us that are rooted without losing root? I'm still on the August build.
Click to expand...
Click to collapse
This is simply a system dump and doesn't contain the bootloader and modem. We'd need the full OTA for those and we can't get them without root. As you've probably noticed, even the gurus at Sammobile haven't posted it yet because it'd be EXTREMELY difficult to catch the OTA even over your own network. I was able to post my Band 46 screenshot because I'm actually in the Beta program.
docnok63 said:
This is simply a system dump and doesn't contain the bootloader and modem. We'd need the full OTA for those and we can't get them without root. As you've probably noticed, even the gurus at Sammobile haven't posted it yet because it'd be EXTREMELY difficult to catch the OTA even over your own network. I was able to post my Band 46 screenshot because I'm actually in the Beta program.
Click to expand...
Click to collapse
Wait, is Band 46 enabled on this 7.x.x update, or only on Beta 8.0?
milan03 said:
Wait, is Band 46 enabled on this 7.x.x update, or only on Beta 8.0?
Click to expand...
Click to collapse
Only beta 8. Running latest 7.x update with Oct security patch and 46 is not enabled.
Apart from wifi-calling and the usual Tmo stuff, is what's the difference between this and the U1 Oreo firmware?
docnok63 said:
This is simply a system dump and doesn't contain the bootloader and modem. We'd need the full OTA for those and we can't get them without root. As you've probably noticed, even the gurus at Sammobile haven't posted it yet because it'd be EXTREMELY difficult to catch the OTA even over your own network. I was able to post my Band 46 screenshot because I'm actually in the Beta program.
Click to expand...
Click to collapse
Beat me to it. Folks, this is just a system dump. Unfortunately, without root, I cannot access the Cache partition, which is where the OTA zip file is stored.
I'm posting system dumps to encourage anyone and everyone to dig through. Hopefully we can find an exploit or some tidbit. I never bothered with the sampawn. While I am very grateful for the time, effort, and energy that went into that root, it's not a true root. When Oreo drops we're back to ground zero.
WHAT'S DIFFERENT:
- Polish: That's partly Google. Partly Samsung. Battery battery life. Things open faster. Etc. And I dirty flashed too.
- Battery Life: Took my phone off charger 16 hours ago and I have 40% left. Screen time 3hr. I heavily rely on my phone every day. Team communication apps, research, navigation, etc. No games. Could be different.
- PiP: Awesome. I had Navigation open earlier today and switched to Music to change songs, a little floating window with my navigation opened. PiP works with Google Maps!
- Band 46: Hasn't been fully initialized in my area, but signals are definitely much more stable.
- WiFi: More stable. I can reach 5G band at further distances. Likely just cleaned up code that's making these work better.
- Small UI changes, such as people edge is more glassy.
Oreo is well worth the patience. I'm only encountering small bugs here and there. It's very stable. So I'd say, maybe Xmas we'll have Oreo. Could be wishful thinking, but I'm hella impressed. This **** is smooth. Only thing I hate is the stupid emojis are the same as before.
Sent from my SM-G955U using Tapatalk
I have the ota file. I go it the day it came out. I did not post it because know one knew how to flash the OTA's
737cd1ee16384c80815ac4fa601193a7.bin
1.36 GB (1,471,096,822 bytes)
CRC32 f6e48ca3
MD5 665aea1f910d68c49b9ae5b90cc8e6b5
SHA-1 150aedf1780b6a32d83384cca46120b1f608abda
goofwear said:
I have the ota file. I go it the day it came out. I did not post it because know one knew how to flash the OTA's
737cd1ee16384c80815ac4fa601193a7.bin
1.36 GB (1,471,096,822 bytes)
CRC32 f6e48ca3
MD5 665aea1f910d68c49b9ae5b90cc8e6b5
SHA-1 150aedf1780b6a32d83384cca46120b1f608abda
Click to expand...
Click to collapse
You should post it just in case someone knows how to do it.
bogdi1988 said:
You should post it just in case someone knows how to do it.
Click to expand...
Click to collapse
I would upload it Like I normally do, but know one was able to figurere it out last year for the Galaxsy s7 edge.
@tengtengvn and I tried to figure it out. You can see the forum here.
https://forum.xda-developers.com/tmobile-s7-edge/how-to/direct-link-nougat-update-t3510467
I have been looking into the the S8+ Ota and noticed
Code:
patch/system/bin/tinycap.p.,.ÓõSBDIFF10×.
SBDIFF. If we can figured out how they SBDIFF the OTA against the 7.0/NRD90M/G955USQU1AQHD firmware. we may be able to flash it.
I also noticed the OTA .bin file has to zip files concatenated together. the first zip only has one file in it called metadata and it is just text.
Code:
ota-type=FILE
post-build=samsung/dream2qltesq/dream2qltesq:8.0.0/OPR1.170623.026/G955USQU1ZQJJ:user/release-keys
post-timestamp=1509361774
pre-build=samsung/dream2qltesq/dream2qltesq:7.0/NRD90M/G955USQU1AQHD:user/release-keys
pre-device=dream2qltesq
If some people show interest I may upload it.