Related
Hi. Dont jump on me for those questions but couldnt find anything here on xda nor google helped me.
So here it is.
Just bought my Note 8. GT-N5110. It has Android 4.1.2 and build version JZO54K.N5110XXBMD1. Not rooted
As I know 4.2.2 is available I wanted to update. But OTA says I am up to date.
I tried then Kies. I have all the drivers uptodate and Kies version uptodate as well. When I connect my Note it is recognized but it seems that Kies doesnt read everything what it should.
It doesnt show the firmware version at all.
When I am trying to check for firmware updates all I get is mssg:
GT-N5110 does not support initialising.
I also tried sammobile. But cuz I couldnt determine which version of Note 8 I have and didnt know which firmware to pick up and installed their apk.
It should check for me everything but I am getting only
Model GT-N5110
Product code. - nothing
PDA N5110XXBMD1
CSC N5110CCBMD1
Modem - nothing
After hitting GET LATEST receiving only mssg - No info foun for the provided firmware.
So my questions are:
- How can I determine is the firmware update available for my Note or not yet?
- How can I determine which version of Note do I have? I bought it on amazon.co.uk so I think it is European version but are there country specific version as well for WIFI only model?
- Which firmware should I download from sammobile to stay "legal" lets say. UK? Dont want to root at the moment.
Any help really appreciated.
cheers
mkiggy
mkiggy said:
Hi. Dont jump on me for those questions but couldnt find anything here on xda nor google helped me.
So here it is.
Just bought my Note 8. GT-N5110. It has Android 4.1.2 and build version JZO54K.N5110XXBMD1. Not rooted
Any help really appreciated.
cheers
mkiggy
Click to expand...
Click to collapse
Hi.
I have the same version. (Settings, System, About (or something like that at the bottom) and then in the buildnumber there is the version.
Mine is rooted so i can't do OTA and it doesn't find an update.
I guess since there isn't any 4.2.2 version on sammobile, there doesnt exist any yet for our build.
Greetings
Chris
Thanks for that.
Decided to root so wont worry anymore about OTA or KIES updates.
Cheers
Firmware
mkiggy said:
Thanks for that.
Decided to root so wont worry anymore about OTA or KIES updates.
Cheers
Click to expand...
Click to collapse
From this link you can get to know about the latest available firmware for your device Model & Product Code. See image 1.
And this link will give you info about all the firmware released for the same. See image 2.
Is the tablet you bought is a used one? Because if it is brand new, then the PDA should be N5110XXBMC9, which is the first release. Also missing Product code can mean something very wrong.
AkiOrpheus said:
Is the tablet you bought is a used one? Because if it is brand new, then the PDA should be N5110XXBMC9, which is the first release. Also missing Product code can mean something very wrong.
Click to expand...
Click to collapse
it was brand new bought from amazon.
what you mean "very wrong" ?
My phone is recognizing tge processor as unknown. The phone works fine, but im kind of concernd. Is there a fix?
mine says the same, I think it's normal
A mistake in original firmware. It's fixed in 2.22 firmware (Android 4.4.3).
ufoman said:
A mistake in original firmware. It's fixed in 2.22 firmware (Android 4.4.3).
Click to expand...
Click to collapse
sorry to tell you, buut it is not fixed on that version, at least not for me, im a dev-ed unit
Do you have a custom rom? Ask the developer to fill the relevant line in build.prop...
G928IDVU1AOH2 Android 5.1.1 lollipop Official firmware Released today in VAU Australia (vodafone)
http://best-tech-reviews.com/update-sm-g928i-g928idvu1aoh2-android-5-1-1-7795/
Damn....I want to flash this so much on my tmobile (us) version :silly:
Is it possible to do that? I'm in the same boat.
I'm not very familiar with samsung modding, unfortunately
SolarTrans said:
Is it possible to do that? I'm in the same boat.
I'm not very familiar with samsung modding, unfortunately
Click to expand...
Click to collapse
Yes it's possible but we need to flash on top our (tmobile) kernel.
I also can't find our tmobile frimeware tar (for odin in case of bootloop)
Damn....booooooring
Hmm I'm downloading the TMO firmware from SamsungUpdate to start, but it's gonna take another 6 hours because of their metered connection -_-.
We'll see how that works out, but ideally I'd be 100% debloated and rooted with Samsung Pay working.
Don't think that'll be possible, but at least we're dealing with unlocked bootloader devices haha
SolarTrans said:
Hmm I'm downloading the TMO firmware from SamsungUpdate to start, but it's gonna take another 6 hours because of their metered connection -_-.
We'll see how that works out, but ideally I'd be 100% debloated and rooted with Samsung Pay working.
Don't think that'll be possible, but at least we're dealing with unlocked bootloader devices haha
Click to expand...
Click to collapse
where did you get the update from?
@Jduncan312
http://samsung-firmware.org/download/SM-G928T/i70w/TMB/G928TUVU1AOGD/G928TTMB1AOGD/
hello
any lucks for the SM-G928C ?
My edge plus is already on 5.1.1 - why the desire to download the same version of firmware from another country? Maybe I'm missing something...
That's not new
Guys, the phone is running great!
Updating for the sake of updating isn't always a good thing when out of the box it's actually working well!
When a device has problems there are threads everywhere of complaints. When a device works things are quiet usually with just the usual how to question. Of course everyone wants root, when it comes it comes. Be patient!
codee said:
My edge plus is already on 5.1.1 - why the desire to download the same version of firmware from another country? Maybe I'm missing something...
Click to expand...
Click to collapse
I do not believe you have to do anything.
While yes, both are version 5.1.1, if you look at the last 4 digits of your firmware build number you should see AOGD. The new firmware build number ends in AOH2, showing this is a newer build date. Nothing major, probably just a few under the hood changes, which usually means a liitle better performance.
http://forum.xda-developers.com/galaxy-nexus/general/help-understand-android-build-t1655863
crowlaw said:
While yes, both are version 5.1.1, if you look at the last 4 digits of your firmware build number you should see AOGD. The new firmware build number ends in AOH2, showing this is a newer build date. Nothing major, probably just a few under the hood changes, which usually means a liitle better performance.
http://forum.xda-developers.com/galaxy-nexus/general/help-understand-android-build-t1655863
Click to expand...
Click to collapse
what about the root-ability?
If you are rooted on an older firmware, and you flash a stock rom via Odin you will lose your root access. So long as your phone model can be/is rooted on your current firmware, after you flash the newer firmware just follow the same steps to root your phone again.
crowlaw said:
If you are rooted on an older firmware, and you flash a stock rom via Odin you will lose your root access. So long as your phone model can be/is rooted on your current firmware, after you flash the newer firmware just follow the same steps to root your phone again.
Click to expand...
Click to collapse
any differences between the OS Firmware, Build Number, or Baseband?
Hello XDA, I have been working on an Aosp-ish nougat rom for our beloved trltetmo. It has nearly no features yet, since it's an AOSP ROM. I'm a Nexus dev, and just recently started working on the trltetmo because I bought one. I had a marshmallow rom and kernel(but tend not to release stuff to anyone to avoid drama and the eta requests).
Downloads: https://www.androidfilehost.com/?a=show&w=files&flid=111459
I have uploaded my work to GitHub: http://github.com/TrlteNougat
For now until I get my gpu back, you have to flash this kernel for MM bootloader support: https://www.androidfilehost.com/?fid=529152257862667083
Known issues:
- Camera is wonky. It's going to be difficult to fix
- The phone acts like it's a dual sim phone, no usability is sacrificed, it just shows two APN settings and the carrier on Dialer
Features:
None yet, it's AOSPish
What is being worked on:
Bluetooth
Call audio (mixer_path issues)
The kernel source is up: https://github.com/TrlteNougat/kernel_samsung_trlte/commits/n7.0
Manifest located here: https://github.com/TrlteNougat/manifest
Nice! Subscribed.
Test build
https://www.androidfilehost.com/?fid=24723757092306996
This one doesn't reboot randomly. Still has ril and Bluetooth errors. Sound doesn't work. Camera does.
I m not dev. But great to see work on 7 ...cheers to all devs...hoping for a stable one soon thx again
I'm keeping my eye on this thank you
Sent from my SM-N910T using Tapatalk
Ril is now partially working. I can send and receive texts. Calls cause a soft reboot, but shouldn't be hard to fix. Still no data connection yet, but that'll be fixed soon enough. Wifi connects but doesn't access internet for some reason. I haven't looked into that any.
Because why not
improper bootloader and in some cases modem can cause Wi-Fi to behave similar to how you have described. I'm not a TMO user but I think there should be several versions newer than OK2
if you have any desire to return to 5.1.1 or keep the option open to do it in the future, you may want to steer clear of the newest 2 or so bootloaders as they may prohibit further downgrading. if TMO is anything like Sprint, anything PE2 and older should still permit downgrades. newer versions I have not tested or seen any info on the topic.
[QRCODE][/QRCODE]ok I did a quick check and you are in fact on a 5.1.1 modem. I don't know if you've updated your bootloader but I get the feeling you would know if you have or not lol
all TMO MM firmware is newer than the Sprint firmwares (PB5, PC1, PD1, PE1, PE2) that I know to not prohibit downgrades, so you're on your own there.
if you believe the test builds to be compatible with the Sprint model, I'd be happy to help test as time allows for it
Sterist said:
[QRCODE][/QRCODE]ok I did a quick check and you are in fact on a 5.1.1 modem. I don't know if you've updated your bootloader but I get the feeling you would know if you have or not lol
all TMO MM firmware is newer than the Sprint firmwares (PB5, PC1, PD1, PE1, PE2) that I know to not prohibit downgrades, so you're on your own there.
if you believe the test builds to be compatible with the Sprint model, I'd be happy to help test as time allows for it
Click to expand...
Click to collapse
910T can be downgradable to DOK2 but not below that (unless you use work around and flash 910T2 firmware, which will allow you to go to 4.4.4 BL , and still can come back to latest) but thats a different story, regardless of that , however , you can anytime switch among DOK2 to PE3 to PG2 in any order. I think android N for 910T should be tested on EPG2 and not on DOK2 , atleast should give it a try on EPG2. I think the dev @USA-RedDragon , already must have tried all bootloaders and basebands , i m just replying to above posts.
Manan79 said:
910T can be downgradable to DOK2 but not below that (unless you use work around and flash 910T2 firmware, which will allow you to go to 4.4.4 BL , and still can come back to latest) but thats a different story, regardless of that , however , you can anytime switch among DOK2 to PE3 to PG2 in any order. I think android N for 910T should be tested on EPG2 and not on DOK2 , atleast should give it a try on EPG2. I think the dev @USA-RedDragon , already must have tried all bootloaders and basebands , i m just replying to above posts.
Click to expand...
Click to collapse
I tried EPE3 on mm but got too frustrated with the issues. So I've been weary to try it again. But you do have a point that I should try with newer bl/modem combos. I've got a mm rom compatible with epe3, so I might as well flash that. The Odin files are on my desktop staring me down
Side note, the logs point to something bring wrong wkth the code and not a bl/modem -> rom compatibility. But I could be wrong. Never hurts to try
USA-RedDragon said:
I tried EPE3 on mm but got too frustrated with the issues. So I've been weary to try it again. But you do have a point that I should try with newer bl/modem combos. I've got a mm rom compatible with epe3, so I might as well flash that. The Odin files are on my desktop staring me down
Click to expand...
Click to collapse
to make it easier ,why dont you just flash EPG2 BL and CP using odin (as opposed to entire MM rom) .and see if it fixes any of the issues with current N build.
Manan79 said:
to make it easier ,why dont you just flash EPG2 BL and CP using odin (as opposed to entire MM rom) .and see if it fixes any of the issues with current N build.
Click to expand...
Click to collapse
I'll do that. Progress is still ongoing with all this. But this week I've been busy with an Android Dev's biggest bane: a full-time job ?
USA-RedDragon said:
Side note, the logs point to something bring wrong wkth the code and not a bl/modem -> rom compatibility. But I could be wrong. Never hurts to try
Click to expand...
Click to collapse
sure ,i do understand that I do want to ask , how about xda devs who work for CM14 unofficial? i dont see much active devs on this thread, i would have thought all the note 4 devs who worked on CM13 unofficial would jump on this to help you out
Manan79 said:
sure ,i do understand that I do want to ask , how about xda devs who work for CM14 unofficial? i dont see much active devs on this thread, i would have thought all the note 4 devs who worked on CM13 unofficial would jump on this to help you out
Click to expand...
Click to collapse
Eh. I have other devs at my disposal. Most don't use XDA, and I tend to not either, but this(like any major version bump on a Samsung) is a big endeavor, so I made the thread for people to jump in if they wanted
USA-RedDragon said:
Eh. I have other devs at my disposal. Most don't use XDA, and I tend to not either, but this(like any major version bump on a Samsung) is a big endeavor, so I made the thread for people to jump in if they wanted
Click to expand...
Click to collapse
got it thx, let me know if you want me to test 910T builds, however i do need sim to be working for incoming/outgoing calls , cant live without that rest all i can test.
Mi A3 Global : DO NOT UPDATE!
V11.0.3.0.QFQMXTC (not QFQMIXM one) is rolling out to the Mi A3 global users.
There was a serious bug in the latest update, so DO NOT UPDATE!!
#WARNING #ALERT #READ
This a warning to everyone who's using the stock ROM here: do NOT update your device to the latest build that shipped via OTA.
Apparently Xiaomeme has rolled out an incorrect build for our device. After flashing, it splashes "Telcel" logo (which is a Mexican carrier), and only SIM1 seems to work post update. If you see any updates, just ignore and do NOT flash.
Thank you! I was updating when I read your warning, now I have a paused update. Thinking about doing a factory reset to get rid of that. I'm starting to be seriously tired of these mistakes and faulty updates...
Thank you again for your advice.
That's why I switched to EU. As Xiaomi releases EU updates after global channel, these kind of mistakes are less likely to happen with EU builds.
What can I Do if i installed the Update?
Do you think xiaomi can fix it with a Update?
Can I block it somehow if the notification "Installation pending" is coming?
palorent said:
What can I Do if i installed the Update?
Do you think xiaomi can fix it with a Update?
Click to expand...
Click to collapse
I have updated :crying::crying: and dual sim is not working
ksaravanan97 said:
I have updated :crying::crying: and dual sim is not working
Click to expand...
Click to collapse
+1
I have switched to MIUI 12 few days ago ?? Am safe. BTW it's (Xiaomeme stock rom) the worst rom I ever used ?
thearorahimanshu said:
I have switched to MIUI 12 few days ago Am safe. BTW it's (Xiaomeme stock rom) the worst rom I ever used
Click to expand...
Click to collapse
You probably don't realize the irony in that - "mocking" Xiaomi for stock Android and at the same time be proud in using their heavily modified Android OS (MIUI).
#Vangreen said:
+1
Click to expand...
Click to collapse
+1
_mysiak_ said:
You probably don't realize the irony in that - "mocking" Xiaomi for stock Android and at the same time be proud in using their heavily modified Android OS (MIUI).
Click to expand...
Click to collapse
am not proud to use it, but its better to use it instead of using Xiaomeme so called stock rom that is full of bugs. actually that's not a rom they are providing, they are giving a lot of bugs with a small amount of rom ??
Well, wife already updated (we both have the A3). We're still locked (bootloader's), and I see Xiaomi is "WORKING FEVERISHLY" to rectify (Ha!).
My question is, is the consensus here of a hard/factory reset would correct this?
soxtober05 said:
Well, wife already updated (we both have the A3). We're still locked (bootloader's), and I see Xiaomi is "WORKING FEVERISHLY" to rectify (Ha!).
My question is, is the consensus here of a hard/factory reset would correct this?
Click to expand...
Click to collapse
i think the option its called "never buy a xiaomi again" :highfive:
soxtober05 said:
Well, wife already updated (we both have the A3). We're still locked (bootloader's), and I see Xiaomi is "WORKING FEVERISHLY" to rectify (Ha!).
My question is, is the consensus here of a hard/factory reset would correct this?
Click to expand...
Click to collapse
Hard reset will hardly help, the issue is related to incorrect ROM. You can either unlock bootloader (this will do a factory reset), flash the right ROM and relock the bootloader. Or just wait for the fix from Xiaomi, they will hopefully release it shortly.
Fix Update is there for those who get the wrong firmware.
??
It is fixed now with a new update... Stupid mistake on Xiaomi's part but at least they are quick to fix it.
Didn't received the bugued update but today I received the fixed update announcing the fix of dual sim bug.
XJeFX said:
Didn't received the bugued update but today I received the fixed update announcing the fix of dual sim bug.
Click to expand...
Click to collapse
+1
I installed it, but in my hurry, forgot the Magisk step before rebooting.
Anyone got patched V11.0.17.0.QFQMIXM?