Database Users

AT&T Note 8.0 Kernel Posted

Samsung released the official kernel for the AT&T Galaxy Note 8.0
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SGH-I467_ATT
Perhaps some mods are in this tablets future...
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4 Beta

DanMc85 said:
Samsung released the official kernel for the AT&T Galaxy Note 8.0
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SGH-I467_ATT
Perhaps some mods are in this tablets future...
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks for notifying, now about the locked bootloader, got any where on that? is it the same as the AT&T s4? confirming if recoveries, kernels can be flashed. Also do you have a recovery.img available? (so I can build cwm and twrp)

emwno said:
Thanks for notifying, now about the locked bootloader, got any where on that? is it the same as the AT&T s4? confirming if recoveries, kernels can be flashed. Also do you have a recovery.img available? (so I can build cwm and twrp)
Click to expand...
Click to collapse
I need to find a rom download somewhere to extract recovery.img as I cant dump it without root to my knowledge.
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4 Beta

DanMc85 said:
I need to find a rom download somewhere to extract recovery.img as I cant dump it without root to my knowledge.
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4 Beta
Click to expand...
Click to collapse
yeah you cant, its either root and use the dd method or a stock firmware, do let me knowif you find one.

emwno said:
yeah you cant, its either root and use the dd method or a stock firmware, do let me knowif you find one.
Click to expand...
Click to collapse
I am compiling the kernel from source tonight or tomorrow, after that I will extract all parts for a recovery for you.

dirtydroidx said:
I am compiling the kernel from source tonight or tomorrow, after that I will extract all parts for a recovery for you.
Click to expand...
Click to collapse
Any luck with this?
- Dan

DanMc85 said:
Any luck with this?
- Dan
Click to expand...
Click to collapse
Working on it right now. PM me when you get a chance.

Time to start fiddling
Sent from my GT-N5110 using xda premium

emwno said:
yeah you cant, its either root and use the dd method or a stock firmware, do let me knowif you find one.
Click to expand...
Click to collapse
dirtydroidx said:
Working on it right now. PM me when you get a chance.
Click to expand...
Click to collapse
Hey Guys,
Here is an extracted boot.img, recovery.img, and sboot.bin from the I467UCAMF1 firmware... they have since updated to I467UCAMF2 OTA via AT&T, but it might be worth still looking into making a root/recovery for the MF1 version or possibly seeing if it will also work on MF2 or if it is possible to downgrade via ODIN.
- Dan

Sweet jeebus.. AOSP here I come. Touchwiz can uhh.. Well you know...

Any update on this?

Very interested for this...
-Sent from my Kangabean Google Ed S4

MrKal_El said:
Very interested for this...
-Sent from my Kangabean Google Ed S4
Click to expand...
Click to collapse
I'm interested in this too

DanMc85 said:
Samsung released the official kernel for the AT&T Galaxy Note 8.0
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SGH-I467_ATT
Perhaps some mods are in this tablets future...
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hi DanMc85,
Have you already root your i467? I'm about to buy one today but would like to know if we will see some new ROMS from XDA, etc. Could you confirm to me that your i467 is LTE like Canadians one?
Thanks,
JmCourir.

RIP
Nobody made a custom recovery or ROM for this device. Rest in Pieces Note 8.0.
Bricked it, Reflashed JB, Bricked it, Reflashed JB, Updated to kitkat, Tried to reflash JB, failed.
:crying: RIP :crying:

I know this is an old thread, but I just can't let go of this tablet! I need a tablet that is not too big or too small so that I can take notes with it. A 10" tablet gets heavy in your hand after a while. Further, very few tablets come with a built-in stylus. If I have to carry an extra stylus, I would either forget or lose it. In fact, I read a 2017 report that Note 8.0 is considered one of the best tablets for note taking! Enough promotion for this aging (4-year-old) device. Now the reality...
Until anyone comes up with a bootloader exploit, the SGH-I467 (AT&T version)'s obituary is essentially written. Yes, you can root it with KingoRoot. Since it's one-click, it cannot get simpler. However, if you can't bypass the bootloader, you are stuck with 4.4.2.
However, the Canadian version (SGH-I467M) has an unlocked bootloader. If anyone would just port a kernel for this tablet, it would give this one many more years of life. Even with the GT-N5120 Lineage OS 14.1 ROM and Boeffla kernel, I can get LTE connection and Nougat out of the box. Light sensor and MIC are still broken, which is expected since this is N5120's kernel. N5120 has two MICs and proximity sensor while I467M has only one MIC and no proximity sensor. I assume N5120's kernel on an I467M would be looking for the wrong MIC and there is some correlations between the proximity and light sensors. Bluetooth is also broken. I don't have explanation for it. I can't explain either why Boeffla kernel would enable the LTE connection since the European radio bands are different than the North American ones. I'm happy it's fixed though! The native kernel from the 14.1 Lineage OS can never establish the radio link though it does see the SIM and IMEI. (The 13.0 LOS cannot detect the IMEI and SIM at all and Boeffla in this case cannot fix it either.)
I am not a developer, but if anyone is willing to port a kernel for SGH-I467M to work with LOS 14.1, I'd be happy to be your beta tester. Thank you
---------- Post added at 11:56 PM ---------- Previous post was at 11:52 PM ----------
Darklordevo said:
Updated to kitkat, Tried to reflash JB, failed.
Click to expand...
Click to collapse
SGH-I467 (NOT I467M, the Canadian version) has a locked bootloader. Once it is upgraded to KitKat, you cannot go back to JB! When I used to hack SGH-I467, I downloaded the -AMF1 firmware (the only one in circulation), thinking if anything went wrong, I could always re-flash with this official firmware. Boy, I learned my lesson when I bricked it. Since mine already had Kitkat, this official JB firmware in circulation is useless. I almost sold it for parts until I came across someone on eBay offering the KitKat firmware!
---------- Post added 2nd March 2018 at 12:18 AM ---------- Previous post was 1st March 2018 at 11:56 PM ----------
DanMc85 said:
Samsung released the official kernel for the AT&T Galaxy Note 8.0
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SGH-I467_ATT
Perhaps some mods are in this tablets future...
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4 Beta
Click to expand...
Click to collapse
It's funny Samsung released the kernel source code for a tablet with a locked bootloader. What can you do with it? I think they are doing it for the sake of fulfilling their open source obligation.
On the other hand, if SGH-I467 and SGH-I467M share very similar kernel, I can imagine someone can port it for SGH-I467M. I am actively looking for a kernel for the Canadian version, I467M, to extend the life of my Note 8.0

I have both I467 and GT-N5110, and are both on the latest 4.4.2 introduced last year about this time.
I am not a dev, but since owning the two devices, i have modded my tablets to be nearly identical. The GT-N5110 has Boeffla kernel and the I467 is stock.
Both run circles around any developed ROM, as for 10 hours of use on battery and no issues, plus mods from S5, Tab 4 and wee mods never released in any developed firmwares to complete a full featured gallery, and allow color blind, interactive control and grey scale mode.
It took messing with 5 different roms and combining missing systrm files for adding hidden features in stock framework and touch wiz.
Only needed a wee mod to remove the few stage fright mp4 issues to button up left over security issues.

gooberdude said:
Both run circles around any developed ROM, as for 10 hours of use on battery and no issues, plus mods from S5, Tab 4 and wee mods never released in any developed firmwares to complete a full featured gallery, and allow color blind, interactive control and grey scale mode.
Click to expand...
Click to collapse
Could you share some instruction on how you did it? Have a 5110 and love it, but it's starting to slow down. Factory resetting, but would love to speed it up

N910T firmware on N910w8

Hi All
excuse my ignorance but is it possible to flash n910T stock firmware
on n910w8 as both are snapdragon LTE varients?
So in other words I want to go from ANJ3 stock firmware to ANJ7 stock firmware..
My Note 4 is rooted with cwm recovery and I understand that i'll loose the root and
cwm recovery if I flash the stock firmware and I am totally fine with that.
Please let me know, Much appreciated!
Cheers

Anyone?

I'd hold off for now until development shows a bit more and people understand it a bit better. On the Note 3 for example you could flash any of the SNAPDRAGON N9005 ROMS on any of the devices, only difference was you had to install the kernel for your device.
EXAMPLE : Flash an N900T ROM onto your W8 would be OK but you'd have to flash the W8 kernel to get it to boot and work (wifi/signal etc).
EDIT: Just re-read, Stock isn't possible via ODIN as it changes the system and boot partitions are different, however with Custom ROMS my explanation is OK

radicalisto said:
I'd hold off for now until development shows a bit more and people understand it a bit better. On the Note 3 for example you could flash any of the SNAPDRAGON N9005 ROMS on any of the devices, only difference was you had to install the kernel for your device.
EXAMPLE : Flash an N900T ROM onto your W8 would be OK but you'd have to flash the W8 kernel to get it to boot and work (wifi/signal etc).
EDIT: Just re-read, Stock isn't possible via ODIN as it changes the system and boot partitions are different, however with Custom ROMS my explanation is OK
Click to expand...
Click to collapse
Thanks for your detailed reply bud,
I guess i'll have to wait like you suggested. Only reason I wanted to switch firmware is because I find note 4 very laggy with the Canadian (n910w8) firmware. I know it's not my device because I've played with 3-4 different note4s and they are all the same. I've also gotten rid of most of the bloatware. Had a T-mobile note 3 prior to this and that was blazing fast with stock rom (bloatware disabled not removed). Not sure what the deal is with Note4s, i truly hope a future firmware update will fix the lag.
Cheers

farhanali_ said:
Thanks for your detailed reply bud,
I guess i'll have to wait like you suggested. Only reason I wanted to switch firmware is because I find note 4 very laggy with the Canadian (n910w8) firmware. I know it's not my device because I've played with 3-4 different note4s and they are all the same. I've also gotten rid of most of the bloatware. Had a T-mobile note 3 prior to this and that was blazing fast with stock rom (bloatware disabled not removed). Not sure what the deal is with Note4s, i truly hope a future firmware update will fix the lag.
Cheers
Click to expand...
Click to collapse
I imagine an incremental software update will fix the lag. The LG G3 also suffered this fate and was fixed with a little patch.
Sent from my Spectrum ZX +2

Yeah you'll see an update in... January?
radicalisto said:
I imagine an incremental software update will fix the lag. The LG G3 also suffered this fate and was fixed with a little patch.
Click to expand...
Click to collapse
Yeah but when? I am infuriated and frustrated with my Note 4. I experience lag and complete sh*t wifi performance. I feel like I've been ripped off for buying this crap that isn't even throughly tested before shipping.
Samsung announces 9.56 Billion Dollars $9,560,000,000 profit in 2013 and yet they can't make a f***king stable phone to ship. Absolutely pathetic. At least Apple patches and pushes iOS fixes literally within a week. I don't expect to see an update to the SM-N910W8 for weeks if not months from now. On the Note 3 they were few and far between.
What a waste of money (and no I can't return it store policy used over 30 minutes of talk / 50 MB of data yeah yeah canadian carriers are rape and they get away with it so don't go down that road).
---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------
farhanali_ said:
Thanks for your detailed reply bud,
I guess i'll have to wait like you suggested. Only reason I wanted to switch firmware is because I find note 4 very laggy with the Canadian (n910w8) firmware. I know it's not my device because I've played with 3-4 different note4s and they are all the same.
Cheers
Click to expand...
Click to collapse
Glad you confirmed that all the devices in the store are also affected. Its rarely a hardware issue despite what people say "Return it and the new one didn't have it" more or less those people just aren't perceptive enough and believe what they want.

I was wondering, I would love to switch to Sprint or tmobile but I don't get 4g coverage were I live, is there a way to make a tmobile or Sprint note 4 get 4g lte from Verizon's towers, would it be possable to flash a different radio would that work. Thanks

Deleted

Marshmallow

LG is most likely developing the Android 6.0 Marshmallow operating system and may release it for its G3 and G4 flagships via an over-the-air (OTA) update, in the coming weeks. Although the update schedule is yet to be revealed.
The company's Korean support site has listed the Android 6.0 Marshmallow update for some variants of the LG G3 and LG G4 flagships, which include the LG G3 F400S, F400K and F400L as well as the LG G4 F500S, F500K and F500L. All these variants are currently running on Android Lollipop operating system.
Click to expand...
Click to collapse
View full post here: http://www.ibtimes.co.uk/android-6-0-marshmallow-update-lg-g3-g4-likely-be-released-soon-1522322

I'd say it's coming as the T-Mobile support page says it's in testing/already developed. (And that's a US Carrier variant)
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Sent From My LG G4

I'm guessing this will mean a new root method will be required?

Knowbody42 said:
I'm guessing this will mean a new root method will be required?
Click to expand...
Click to collapse
Also a 6 month+ wait for Telstra to do their "testing". Unless we can simply flash it the way we do now with locked bootloaders and injecting root.

I'm excited for the camera app from the V10 being ported over!!

I hope it has better power managment..battery gets warm to hot with some apps and lag is still a problem on non rooted phone..

I'm hoping that it'll only be a couple weeks before MM is released to the G4, but I'd be happy if it's before the new year. It would make sense to have it out before Xmas so people might buy the G4 as a gift.
I guess not too many of the general public are going to care/know about the latest release of android, whereas people do want something that can handle iOS 9 or whatever version they're on now.

Here's hoping for a fairly quick release and a screen saturation control!
Amazed at how much the price of the G4 has dropped. I bought mine for £360 three weeks ago and it's dropped another £42 since! Probably £299 by Xmas. Why bother waiting for a One Plus/Nexus etc.?

bustervic said:
I'm excited for the camera app from the V10 being ported over!!
Click to expand...
Click to collapse
+1
It is inevitable i believe because both phones use identical sensors...
frnkly said:
I hope it has better power managment..battery gets warm to hot with some apps and lag is still a problem on non rooted phone..
Click to expand...
Click to collapse
+1
We should get much better battery life, especially in stand-by. But i'm hoping for beter power managment
while in use and a better optimised cpu governor... Lag shoulden't be a problem in MM...
daglesj said:
Here's hoping for a fairly quick release and a screen saturation control!
Click to expand...
Click to collapse
+1
That would be great...

I'm wondering how long it will take Big Red to push this out.

Knowbody42 said:
I'm guessing this will mean a new root method will be required?
Click to expand...
Click to collapse
Possibly, but at the same time, possibly not.
The current low effort root method actually uses a bootloader exploit which COULD not be patched by the new version (This is a BIG IF). If this is the case, we'd be able to use the same exact method as before to inject root.
---------- Post added at 05:57 PM ---------- Previous post was at 05:46 PM ----------
Also, don't want to be a party pooper, but LG promised the Lollipop release "Soon" last year and ended up taking a long time to release it through most vendors... So I don't trust LG on that front.

karendar said:
Possibly, but at the same time, possibly not.
The current low effort root method actually uses a bootloader exploit which COULD not be patched by the new version (This is a BIG IF). If this is the case, we'd be able to use the same exact method as before to inject root.
---------- Post added at 05:57 PM ---------- Previous post was at 05:46 PM ----------
Also, don't want to be a party pooper, but LG promised the Lollipop release "Soon" last year and ended up taking a long time to release it through most vendors... So I don't trust LG on that front.
Click to expand...
Click to collapse
Well said, it's a big if... But nevertheless, someone will find out the way to root, someone always does
About the MM release, i believe it will be out around the new year, probbably in early january :fingers-crossed:

Knowbody42 said:
I'm guessing this will mean a new root method will be required?
Click to expand...
Click to collapse
The M update will be hell for root on bootloader locked devices....Lets assume they close the initial exploit used in Low Effort Root, that means a new exploit must be found (which certainly is possible but will take time). The problem is right now you can't root on M without a custom kernel, the stock M kernel doesnt play nice with SuperSU (causes bootloops), also by default M restricts read/write access to the system partition even with root. So again a custom kernel is needed to defeat these. If you have a bootloader locked device its going to be very difficult to root your device on M. Hopefully the devs can find something but if you need root best move on to a bootloader unlockable device/variant.
---------- Post added at 12:02 PM ---------- Previous post was at 12:01 PM ----------
karendar said:
Possibly, but at the same time, possibly not.
The current low effort root method actually uses a bootloader exploit which COULD not be patched by the new version (This is a BIG IF). If this is the case, we'd be able to use the same exact method as before to inject root.
---------- Post added at 05:57 PM ---------- Previous post was at 05:46 PM ----------
Also, don't want to be a party pooper, but LG promised the Lollipop release "Soon" last year and ended up taking a long time to release it through most vendors... So I don't trust LG on that front.
Click to expand...
Click to collapse
M will likely require a new bootstack, guaranteed that LG patches the backdoor, i'd be very surprised if they left it open. Even if you inject the current SU binary/SuperSU it doesnt play nicely with a stock compiled M kernel, causes bootloops on Nexus Devices, so that means you need a custom kernel unless Chainfire can figure out how to make it work with the default M kernel.

djkinetic said:
The M update will be hell for root on bootloader locked devices....Lets assume they close the initial exploit used in Low Effort Root, that means a new exploit must be found (which certainly is possible but will take time). The problem is right now you can't root on M without a custom kernel, the stock M kernel doesnt play nice with SuperSU (causes bootloops), also by default M restricts read/write access to the system partition even with root. So again a custom kernel is needed to defeat these. If you have a bootloader locked device its going to be very difficult to root your device on M. Hopefully the devs can find something but if you need root best move on to a bootloader unlockable device/variant.
---------- Post added at 12:02 PM ---------- Previous post was at 12:01 PM ----------
M will likely require a new bootstack, guaranteed that LG patches the backdoor, i'd be very surprised if they left it open. Even if you inject the current SU binary/SuperSU it doesnt play nicely with a stock compiled M kernel, causes bootloops on Nexus Devices, so that means you need a custom kernel unless Chainfire can figure out how to make it work with the default M kernel.
Click to expand...
Click to collapse
I'm not really worried about a root method for M... There will be a method by the time M comes out for our phone.
The current exploit, I'd also be surprised if they didn't patch it(as I mentioned) , but then again, I've seen exploits not be patched by major versions, so it's not impossible. Only a release will tell us.

karendar said:
I'm not really worried about a root method for M... There will be a method by the time M comes out for our phone.
The current exploit, I'd also be surprised if they didn't patch it(as I mentioned) , but then again, I've seen exploits not be patched by major versions, so it's not impossible. Only a release will tell us.
Click to expand...
Click to collapse
I'm not as optimistic as you. Yes, the exploit we used to root may still be open (after all, they left it open on the G3 -> G4). But a new problem is present: Starting with Android 6.0 all kernels now use a forceencrypt flag. Even all Nexus users have had to flash a custom kernel which flips the flag to noforceencrypt before they could root - that was never the case in the past and Nexus users could just flash SuperSU on the stock kernel and be done with it. Not anymore. Google is locking things down in the interest of security.
You can try it yourself if you have a Nexus. Flash SuperSU on the stock 6.0 kernel. You'll bootloop as the kernel won't allow the system to boot while SuperSU is installed. Only way to root is to flash a custom kernel with the proper modifications to allow root.
The reason this is a problem for us G4 users is, since we have locked bootloaders (with the exception of a few international units), we cannot flash custom kernels. No kernel flashing = no way to flip noforceencrypt in the kernel = no root on M Sure, you can maybe find a way to get SuperSU and the root binaries in there, but when you try to boot you'll just bootloop as the system won't let you in.
Maybe a workaround will be found, but this new kernel security is a seriously blow to our ability to attain root on the G4 running M.

biff6789 said:
I'm not as optimistic as you. Yes, the exploit we used to root may still be open (after all, they left it open on the G3 -> G4). But a new problem is present: Starting with Android 6.0 all kernels now use a forceencrypt flag. Even all Nexus users have had to flash a custom kernel which flips the flag to noforceencrypt before they could root - that was never the case in the past and Nexus users could just flash SuperSU on the stock kernel and be done with it. Not anymore. Google is locking things down in the interest of security.
You can try it yourself if you have a Nexus. Flash SuperSU on the stock 6.0 kernel. You'll bootloop as the kernel won't allow the system to boot while SuperSU is installed. Only way to root is to flash a custom kernel with the proper modifications to allow root.
The reason this is a problem for us G4 users is, since we have locked bootloaders (with the exception of a few international units), we cannot flash custom kernels. No kernel flashing = no way to flip noforceencrypt in the kernel = no root on M Sure, you can maybe find a way to get SuperSU and the root binaries in there, but when you try to boot you'll just bootloop as the system won't let you in.
Maybe a workaround will be found, but this new kernel security is a seriously blow to our ability to attain root on the G4 running M.
Click to expand...
Click to collapse
Yea with the current changes that Google made with M at the kernel level bootloader locked devices have very little hope of being rooted, the reason why we can still root on nexus devices is because our bootloaders are unlockable you take that away and we would be in the same boat, this release of android has pretty much signaled the end of me buying any carrier phones that i know will be locked down. its simply too much hassle for most devs to bother with finding new exploits in the coming android versions.

Rydah805 said:
I'd say it's coming as the T-Mobile support page says it's in testing/already developed. (And that's a US Carrier variant)
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Sent From My LG G4
Click to expand...
Click to collapse
Man. Sweet.
Sent from my LG-H811 using Tapatalk

Rydah805 said:
I'd say it's coming as the T-Mobile support page says it's in testing/already developed. (And that's a US Carrier variant)
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Sent From My LG G4
Click to expand...
Click to collapse
It does? It looks to me like it says both the g3 and g4 are in Manufacturer Development not testing. The nexus 6 is the only device I see that's in testing. I would be shocked if it comes out before December and I would not be shocked if we don't see it until next year.

biff6789 said:
The reason this is a problem for us G4 users is, since we have locked bootloaders (with the exception of a few international units), we cannot flash custom kernels. .
Click to expand...
Click to collapse
Please, most of the world has unlocked bootloaders.

Mad_Duke said:
Please, most of the world has unlocked bootloaders.
Click to expand...
Click to collapse
Just Europe and T-Mobile USA (AFAIK) at the moment.
The percentage of G4's with unlockable bootloaders is pretty small.

[Discussion] Sideloading of OTAs on 2gb XT1540

Since people turned the original OTA thread into a **** show, and the current one has the thread locked I'm creating this. Before the thread was closed we had multiple users complaining of a repeated error after attempting to sideload the OTA involving the device looking for incorrect version numbers.
I don't know if anyone found a solution yet but knowing how impatient most of us are to get this update I decided to make a discussion thread and see if we can't get it working or at least find out a solution.
Solution: Flash the latest 1gb firmware in fastboot, skip through setup wizard but be sure to add a wifi access point, then check for updates, you should get the OTA, everything is fine so far, no issues whatsoever. Thanks to @hp420 for making the suggestion

l3ones said:
Since people turned the original OTA thread into a **** show, and the current one has the thread locked I'm creating this. Before the thread was closed we had multiple users complaining of a repeated error after attempting to sideload the OTA involving the device looking for incorrect version numbers.
I don't know if anyone found a solution yet but knowing how impatient most of us are to get this update I decided to make a discussion thread and see if we can't get it working or at least find out a solution.
Click to expand...
Click to collapse
The only things you really need to make sure flashing the OTA manually works perfectly is to
1. Have the stock recovery installed
2. Have the right firmware installed (matching the firmware number with the one in the OTA)
3. Have an unmodified system partition (i.e. no root/busybox/mods etc.)
4. Flash the OTA that matches your SKU ID (e.g. Flashing an XT1540 OTA on an XT1540 Moto G3)
And the only reason my thread is locked is to give the users the links to the OTA without the **** show

dd98 said:
The only things you really need to make sure flashing the OTA manually works perfectly is to
1. Have the stock recovery installed
2. Have the right firmware installed (matching the firmware number with the one in the OTA)
3. Have an unmodified system partition (i.e. no root/busybox/mods etc.)
4. Flash the OTA that matches your SKU ID (e.g. Flashing an XT1540 OTA on an XT1540 Moto G3)
And the only reason my thread is locked is to give the users the links to the OTA without the **** show
Click to expand...
Click to collapse
The issue was with #2. When trying to flash the 2gb version of MM on the phone it was asking looking for 23.72-65, now there is one for the 1gb but not the 2gb, at least not posted. From the info I gathered it seems that the 72-65 firmware for the 2gb version was the soak test version. I think, I could be wrong but from other posts that I saw the soaks for 2gb ended in 65.

dd98 said:
The only things you really need to make sure flashing the OTA manually works perfectly is to
1. Have the stock recovery installed
2. Have the right firmware installed (matching the firmware number with the one in the OTA)
3. Have an unmodified system partition (i.e. no root/busybox/mods etc.)
4. Flash the OTA that matches your SKU ID (e.g. Flashing an XT1540 OTA on an XT1540 Moto G3)
And the only reason my thread is locked is to give the users the links to the OTA without the **** show
Click to expand...
Click to collapse
The issue is that the OTA is looking for a version number never released for the 2gb version. I'll try it again and type up the error output.

l3ones said:
The issue is that the OTA is looking for a version number never released for the 2gb version. I'll try it again and type up the error output.
Click to expand...
Click to collapse
To be exact it's looking for "motorola/osprey_retus_2gb/osprey_u2:5.1.1/LPI23.72-65/51:user/release-keys".
Could I just edit the metadata.json to look for the proper version and repack/resign?

l3ones said:
To be exact it's looking for "motorola/osprey_retus_2gb/osprey_u2:5.1.1/LPI23.72-65/51:user/release-keys".
Could I just edit the metadata.json to look for the proper version and repack/resign?
Click to expand...
Click to collapse
If I knew how to do this I would give it a try

Well, since it has to be signed by the OEM, I've decided to just pull the files and get cooking on a rom for it. I forgot how long it takes cygwin to install

Person who grabbed that ota here. I guess it's too late for me to go through and try to dump the firmware that apparently I'm the only one to have?
New to this whole business, are we sure the 2gb LPI23.72-65 firmware was "never released" or just "never caught"? The firmware dl thread has only two listed for the 2gb version, but four for the 1gb version.
(re: cygwin I'm running linux native on my end if there's anything I should be messing around with)

Just flash the 1gb factory image it wants you to have, then the ota

Gotolei said:
Person who grabbed that ota here. I guess it's too late for me to go through and try to dump the firmware that apparently I'm the only one to have?
New to this whole business, are we sure the 2gb LPI23.72-65 firmware was "never released" or just "never caught"? The firmware dl thread has only two listed for the 2gb version, but four for the 1gb version.
(re: cygwin I'm running linux native on my end if there's anything I should be messing around with)
Click to expand...
Click to collapse
Im not 100% sure about the whole never release part, Im going by the official firmware page that we have here. Im just thinking it would have been captured by now if it was out there.
---------- Post added at 03:46 PM ---------- Previous post was at 03:44 PM ----------
hp420 said:
Just flash the 1gb factory image it wants you to have, then the ota
Click to expand...
Click to collapse
If you flash 1gb firmware on the 2gb and then do the OTA, im guessing its going to be the 1gb MM firmware?
Do you think it would be possible to the run the 2gb MM update through stock recovery after?

hp420 said:
Just flash the 1gb factory image it wants you to have, then the ota
Click to expand...
Click to collapse
Did you wind up doing this? Everything normal in the end?
---------- Post added at 05:18 PM ---------- Previous post was at 05:17 PM ----------
Gotolei said:
Person who grabbed that ota here. I guess it's too late for me to go through and try to dump the firmware that apparently I'm the only one to have?
New to this whole business, are we sure the 2gb LPI23.72-65 firmware was "never released" or just "never caught"? The firmware dl thread has only two listed for the 2gb version, but four for the 1gb version.
(re: cygwin I'm running linux native on my end if there's anything I should be messing around with)
Click to expand...
Click to collapse
Only thing im thinking is that the 6.0 ota somehow patches to 65 then up to the 6.0

minieod said:
Did you wind up doing this? Everything normal in the end?
---------- Post added at 05:18 PM ---------- Previous post was at 05:17 PM ----------
Only thing im thinking is that the 6.0 ota somehow patches to 65 then up to the 6.0
Click to expand...
Click to collapse
So far everything seems normal. I ran the newest 1gb firmware, got the OTA, saved the link, Installed it. Phone is currently optimizing apps. Will keep you posted. If all seems well I will try to run the 2gb Update on top of this one, if possible.
UPDATE: All seems to be running fine, in system options it does show that im on the 1GB versus the 2GB of Marshmallow (not sure how this will effect anything in the long run). Seems a bit smoother, but that could just be placebo. As everyone posted, everything looks pretty much the same. Lock screen has a new font, IMO it looks cleaner.

pl4life52 said:
So far everything seems normal. I ran the newest 1gb firmware, got the OTA, saved the link, Installed it. Phone is currently optimizing apps. Will keep you posted. If all seems well I will try to run the 2gb Update on top of this one, if possible.
UPDATE: All seems to be running fine, in system options it does show that im on the 1GB versus the 2GB of Marshmallow (not sure how this will effect anything in the long run). Seems a bit smoother, but that could just be placebo. As everyone posted, everything looks pretty much the same. Lock screen has a new font, IMO it looks cleaner.
Click to expand...
Click to collapse
This is exactly as I suspected. The person who pulled this URL has a 2gb device, which was bought used. The owner before them must have flashed the 1gb factory image to have it on the newest firmware, since the only way to be fully updated on the 2gb is via the most recent 5.1.1 ota....so they flashed a 1gb factory image to take the easy route and shipped it out.Then when the ota notification came through it was for the 1gb variant since it was running 1gb firmware.
Simple solution....flash the most recent 1gb factory image and hit the update button. It seems to be working for everyone.

hp420 said:
This is exactly as I suspected. The person who pulled this URL has a 2gb device, which was bought used. The owner before them must have flashed the 1gb factory image to have it on the newest firmware, since the only way to be fully updated on the 2gb is via the most recent 5.1.1 ota....so they flashed a 1gb factory image to take the easy route and shipped it out.Then when the ota notification came through it was for the 1gb variant since it was running 1gb firmware.
Simple solution....flash the most recent 1gb factory image and hit the update button. It seems to be working for everyone.
Click to expand...
Click to collapse
Got it from Best Buy, actually. Not used.
Just got it for Christmas, and I'm guessing the people around here have had their phones for a while?

Gotolei said:
Got it from Best Buy, actually. Not used.
Click to expand...
Click to collapse
Well I got nothin' then lol
I got mine in September from motomaker

Gotolei said:
Got it from Best Buy, actually. Not used.
Click to expand...
Click to collapse
Does your system options show 1gb or 2gb version?

yoyoche said:
Does your system options show 1gb or 2gb version?
Click to expand...
Click to collapse
2gb all around.

Well nuts

pl4life52 said:
So far everything seems normal. I ran the newest 1gb firmware, got the OTA, saved the link, Installed it. Phone is currently optimizing apps. Will keep you posted. If all seems well I will try to run the 2gb Update on top of this one, if possible.
UPDATE: All seems to be running fine, in system options it does show that im on the 1GB versus the 2GB of Marshmallow (not sure how this will effect anything in the long run). Seems a bit smoother, but that could just be placebo. As everyone posted, everything looks pretty much the same. Lock screen has a new font, IMO it looks cleaner.
Click to expand...
Click to collapse
when you get into about phone and all that. it shows 1GB. what about when you go to settings > memory ... does it show XXXMB / 1.0 GB being used, or 2.0?

Updated the OP with solution for visibility. It worked great for me.

Oreo System Dumps - OPR1.170623.026.G955USQU1ZQJJ 11-3-2017

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.