Update to MM expected in may... - Galaxy Tab S2 General

As latest leak suggests, tab s2 is one of rare Samsung devices to get mm for sure
http://www.androidauthority.com/samsung-marshmallow-update-roadmap-677528/

Nice, just got my 710 was rly disappointed when I didn't get the 5.1.1 update, and OTA was saying you are on the latest firmware, will try Kies but I guess I will have to flash with Odin my self

samsung says 1 rd quater 2016 for new nad old devices like galaxy s5 ..

mk89pwnz said:
Nice, just got my 710 was rly disappointed when I didn't get the 5.1.1 update, and OTA was saying you are on the latest firmware, will try Kies but I guess I will have to flash with Odin my self
Click to expand...
Click to collapse
Use "SmartSwitch" which replaced Kies.
It will give you BOJ1...
There is also an even newer firmware from December BOL6 which is on Sammobile. It came via OTA but not sure why its not automatically downloading.
Currently sticking with BOJ1 until I can figure out what is up with BOL6.
I did update my mom's S2 to BOL6 and it ran fine.
It should be noted that there is no source yet for BOL6 as its fairly new. I have requested it and it will be released soon.
But that means there is no kernel for root. One could use the older firmware root kernel and it should work fine but I find it best to always use the correct kernel.

Related

This version of the device cannot be updated.

Everything was fine until I updated to KE2 via Kies. Now whenever I connect my phone to Kies I get this message:
This version of the device cannot be updated.
Current firmware version: PDA:KE2 / PHONE:KDJ / CSC:KD1 (XEU)
I have an unbranded, UK Samsung Galaxy S II from buymobilephones.net. I have not rooted or installed any custom ROMs.
I'm using the latest UK version of Kies.
Any idea what the problem is here? I've uninstalled and reinstalled the USB drivers and Kies several times. I was not getting this message a few days ago.
Kies is probably confused because they rolled back and removed the KE2 update from the servers so as far as kies is concerned you are using a rom version that doesn't exist yet. I imagine once they release KE3 in the next couple of days Kies will return to normal.
MrYiff said:
Kies is probably confused because they rolled back and removed the KE2 update from the servers so as far as kies is concerned you are using a rom version that doesn't exist yet. I imagine once they release KE3 in the next couple of days Kies will return to normal.
Click to expand...
Click to collapse
Ah, makes sense. Thanks for the reply.
Kies says this device cannot be updated = their is NO UPDATE for this device you are already running the latest firmware .
KE2 is the last update so their is no update for your phone .
jje
Not always as simple as that, when kies says "your device cannot be updated" its can be because it doesn't recognise your software version, this can happen when its been pulled from samsungs severs, you have flashed firmware that doesn't match you're csc or you're running a custom rom. Normally when you're running the current official firmware it will show you both your firmware and samsungs as the most recent. If samsung have pulled the latest update it will say you device can not be updated insted of saying you're on the latest version, we will just have to wait for a new update.
Sent from my GT-I9100 using XDA App
Yes thats true but in the users post he showed the latest firmware installed .
Plus i have already had one user posting today that i was wrong when i said much as you just said and with PC Hardware IF etc that do not match what's on the server .
About time Samsung gave Kies to a grown up developer anyway .
jje
JJEgan said:
Yes thats true but in the users post he showed the latest firmware installed .
Plus i have already had one user posting today that i was wrong when i said much as you just said and with PC Hardware IF etc that do not match what's on the server .
About time Samsung gave Kies to a grown up developer anyway .
jje
Click to expand...
Click to collapse
My post was because you replied to someone stating that they would no longer be able to update their phone ever again. That is simply not true.

Kies 2.0: "This device's version cannot be updated"

I bought my Galaxy SL from Egypt; however, I've lost my original ROM. I've tried both I9003JPKD1 and I9003JPKE1 (Both are Arabic), yet kies still complains it can't update the version. I've problems with these 2 ROMs. The perfromance is sluggish and the camera hangs a lot. I need to use Kies to update to the original firmware my phone came with. Is there anyway to do this?
Kies wont update the version as Samsung has not officially released any for this phone.
you will need to flash other ROM using the Odin and all info about that is already available just check the flashing guide and be careful as you might loose your warranty.
amrhesham said:
I bought my Galaxy SL from Egypt; however, I've lost my original ROM. I've tried both I9003JPKD1 and I9003JPKE1 (Both are Arabic), yet kies still complains it can't update the version. I've problems with these 2 ROMs. The perfromance is sluggish and the camera hangs a lot. I need to use Kies to update to the original firmware my phone came with. Is there anyway to do this?
Click to expand...
Click to collapse
Kies detect your location and your fw release version, i tried matching the fw and my pc region but still no luck.
braveBuddy said:
Kies wont update the version as Samsung has not officially released any for this phone.
you will need to flash other ROM using the Odin and all info about that is already available just check the flashing guide and be careful as you might loose your warranty.
Click to expand...
Click to collapse
Yes, I flashed the only 2 Arabic firmwares available on samfirmware using Odin; however, it seems both of them were signed in KSA and not Egypt. Where can I find an Egyptian ROM?
I have the same problem here

Looking for comprehensive stock firmware list for S7Edge

Hey all. I am in the US but bought international S7Edge when it came out. I dont know what firmware it had I think it was some italian one maybe. Then i rooted and started using custom roms. Then when nougat officially came out for S7Edge i un-rooted and went back to 100% stock using i think Vodafone 7.0 firmware. I think because i rooted i have a negative test response from Knox which i think stops me from getting OTA updates. It shows in software info that my OS version has security patch only from January 2017 so I am clearly not on latest firmware even though OTA says I am on latest.
Is there a site with a database of all firmwares out for the S7Edge international variant So i can find the latest and flash it to my phone since OTA wont get the latest.
samsmobile has the latest.
Yoiu still have an issue with your kernal as phone still thinks you have custom rom. Tripped knox on stock firmware will not stop OTA from downloading.

Good News Guys >>>>Official T-Mobile Galaxy J7 Android 7.1.1 Nougat update released

Good News Guys >>>>Official T-Mobile Galaxy J7 Android 7.1.1 Nougat update released
We reported recently that the Galaxy J7 might soon receive the Nougat update. The handset was spotted at the Wi-Fi Alliance running a Nougat build. It was a big indication that the company was planning on rolling out the update soon.
T-Mobile has now started rolling out the Android 7.1.1 Nougat update for the Galaxy J7. It’s one of the few devices that Samsung has updated straight to version 7.1.1 from Marshmallow.
T-Mobile Galaxy J7 Android 7.1.1 Nougat Update
T-Mobile has started rolling out the Nougat update for the Galaxy J7 over-the-air. However, the company’s support document for this handset is all over the place. It assigns version number Android 6.0.1, Android 7.0 and Android 7.1.1 to one single firmware version, J700TUVU3BQI5.
This is obviously not possible. Clearly, there are clerical issues with the document. That doesn’t mean the T-Mobile Galaxy J7 Android 7.1.1 Nougat update isn’t rolling out. Those who own this handset on T-Mobile will soon receive an update notification if they haven’t already.
This firmware is also available for download from our firmware section where the Android version is accurately mentioned as Android 7.1.1 Nougat. Despite the fact that this update has been released in October, it comes with the August security patch.
Galaxy J7 owners on T-Mobile can either wait for the update to go live in their region or simply download the firmware from our website.
Download 7.1.1 here and happy flashing J700TUVU3BQI5 - Galaxy J7 SM-J700T TMB USA (T-Mobile)
Click here
Source :- SamMobile
Tmobile received the update from samsung on 8/28. They filled it with their garbage and sent it last thursday, most of us flashed aqf1 stock and got it ota friday morning.i dont see any clerical errors or anything like that at all. And ive been digging through the build for a week. Im running it now. All internation j7 roms flash with this builds kernel, but reboot in the setup wiz, so once we get a good base there will be a ton of ports in this community. Also, we have found, edge screen, blf, high performance mode, and aod hidden but inactive in the phone. This build is something amazing folks.
Btw, sammobile is a useless, slow dinosaur. Updato via playstore is the best source for firmware.
fullofhell said:
Tmobile received the update from samsung on 8/28. They filled it with their garbage and sent it last thursday, most of us flashed aqf1 stock and got it ota friday morning.i dont see any clerical errors or anything like that at all. And ive been digging through the build for a week. Im running it now. All internation j7 roms flash with this builds kernel, but reboot in the setup wiz, so once we get a good base there will be a ton of ports in this community. Also, we have found, edge screen, blf, high performance mode, and aod hidden but inactive in the phone. This build is something amazing folks.
Btw, sammobile is a useless, slow dinosaur. Updato via playstore is the best source for firmware.
Click to expand...
Click to collapse
I would like to have the edge screen without installing a Rom you think is possible?.
carlosbalbuena_ said:
I would like to have the edge screen without installing a Rom you think is possible?.
Click to expand...
Click to collapse
Not sure. It isnt working yet.
Will this work for the metro pcs variant ( SM-J700T1) as well?
hightech316 said:
Will this work for the metro pcs variant ( SM-J700T1) as well?
Click to expand...
Click to collapse
I think so..i got edge lighting to work. Im writing each csc tweak down and will include them in our next build.see photo,.this is native in the stock firmware
Has anyone flashed this update on their metro J7?
Does this update contain t-mobile bloat?
hightech316 said:
Has anyone flashed this update on their metro J7?
Does this update contain t-mobile bloat?
Click to expand...
Click to collapse
flash the aqf1 metro firmware, then take update to 7.1.1 ota. Then u will have metro nougat
fullofhell said:
Not sure. It isnt working yet.
Click to expand...
Click to collapse
And the Performance mode got it by installing some application or what?
carlosbalbuena_ said:
And the Performance mode got it by installing some application or what?
Click to expand...
Click to collapse
Download csc editor by wanam via playstore its in one of those...u look thru and change each item to "true" then reboot. Its called performance tuning
fullofhell said:
Download csc editor by wanam via playstore its in one of those...u look thru and change each item to "true" then reboot. Its called performance tuning
Click to expand...
Click to collapse
Ok bro I'm going to try and the edge lighting like it did
I got the stock ROM deodex and services jar modded but when I connect it to my lab top it don't come up unless I go and turn off USB debugging
mario1634 said:
I got the stock ROM deodex and services jar modded but when I connect it to my lab top it don't come up unless I go and turn off USB debugging
Click to expand...
Click to collapse
This firmware is being a arsehat for me too.
When I flashed the original boot img. Now my lab top able to see my phone. It crazy because I can still pull and push but programs like assayyed don't see it until I flash stock boot img
mario1634 said:
When I flashed the original boot img. Now my lab top able to see my phone. It crazy because I can still pull and push but programs like assayyed don't see it until I flash stock boot img
Click to expand...
Click to collapse
Weird af
fullofhell said:
flash the aqf1 metro firmware, then take update to 7.1.1 ota. Then u will have metro nougat
Click to expand...
Click to collapse
Great, thanks!
Once I have time I'll upload a rooted nandroid
Safe to flash through TWRP while rooted with xposed? Or should I disable xposed and uninstall root? Also, should I wipe when flashing or does it matter
phoen1x74 said:
Safe to flash through TWRP while rooted with xposed? Or should I disable xposed and uninstall root? Also, should I wipe when flashing or does it matter
Click to expand...
Click to collapse
U cannot in any capacity flash a stock firmware with twrp.u have to wipe your whole phone and go to download mode and flash the firmware via odin. Dont forget to unzip the file first so u have the unzipped form of it loaded in the ap slot
Aight I'm chill (no way at all to update without wiping my phone?) Like what if I don't wipe and flash in odin; will that lead to problems?
phoen1x74 said:
Aight I'm chill (no way at all to update without wiping my phone?) Like what if I don't wipe and flash in odin; will that lead to problems?
Click to expand...
Click to collapse
U could if u werent rooted or had twrp installed..if u dont wipe before odin, it will prob fail until u wipe it honestly.

Android 8 Oreo Update

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.

Categories

Resources