Copied from the OnePlus forums - no response yet so far
I recently got my new OnePlus 9rt, however I've ran into a few perplexing issues with the handset.
The first issue is that it is just outright missing the manual update option. No cog, no nothing.
The second issue which compounds to the first, is that every time I try to update the software to MT2111_11.A.07_2022031423170148, it fails. My current version is 11.3 according to the phone. Manually updating through the oxygen OS installer also fails. Which brings me to the next point..
The third issue is that under the model section of the phone, instead of saying the model of the handset, it says the model is Lahaina for arm64, which I'm quite sure it's not meant to be there. Everything else, build number, baseband version, kernel version (provided below) match the other handsets. However a cursory examination on this forum says that there were/are people on this forum with a similar issue to the second point.
So I'm wondering, is this ROM official? Or did I get a corrupted pre-install of the software on the phone? Or am I overthinking this?
Also messages don't delete completely in messenger app. You delete them, and then a second later they return.
For reference, here is the information..
Build number: MT2111_11_A.03
Baseband version: Q_V1_P14,Q_V1_P14
Kernel version: 5.4.96-qgki-g449ba87830ff
Thanks in advance
Where did you buy the phone from and what country are you in? Currently the handset is only officially sold in China and India.
Was the package completely sealed, or has it been opened? It sounds to me like you have been sold a handset from the Chinese market and it's had the unofficial Indian ROM flashed on it.
ie. this one https://forum.xda-developers.com/t/...xygenos-a-04-a-07-for-mt2110-devices.4404719/
I bought the phone from Kogan, and I'm from Australia. This isn't the first time I bought a OnePlus from there, but this is my first time with these issues specifically.
As for the package, it was sealed yes. And yes, those issues are practically identical with a few asides - such as the cog button missing. Such as that one..
Device name in settings displayed incorrectly "Lahaina for amd64" instead of expected "MT2111".
Yeah, that's 100% what it is.
Issue resolved, thanks!
Skywrath0135 said:
Issue resolved, thanks!
Click to expand...
Click to collapse
how to fix this? i have same problem
Related
Good day
I have just gotten my Desire a few days back. So far so good. I'm really pleased with it, but I still have a couple of questions (which hopefully can be answered here).
I suppose when I bought my phone, it was an AP phone. And I also will assume that it is from Asia/Asia Pacific/South East Asia because I have a choice of using English (Malaysian), English (Singaporean), and others, as well as a Thai and PinYin keyboard. My Desire also has a preset Scene, called HTC Asia. No big deal, I'm from Malaysia anyway.
Question: What is a sure-fire way to check out where my phone is from?
And I will also assume that it is unbranded. I have read a few posts, and branded phone will have the service provider logo appear on start up. Mine doesn't.
Question: Does this mean it is unbranded? Or just unlocked? How would I know if it is unlocked?
I tried updating my Desire to Froyo. No luck. Searching for software updates through the phone yields no results. The message telling me that my phone is up to date keeps popping up whenever I search. Here is my software information.
Firmware Version 2.1update1
Baseband version 32.41.00.32U_4.08.00.09
Kernel Version 2.6.29-b7e82785 htc-kernel(at)and18-2 #1
Build number 1.19.707.7 CL171460 release-keys
Software Number 1.19.707.7
Browser Version WebKit 3.1
Question: Why is this so? Isn't Froyo out for SEA? Or does my phone's origins have something to do with the Froyo update? Will I even get a Froyo update?
I've actually brought my phone to a technician, just to chat abit, but then I decided, "Heck, if I can't get froyo, I might as well root it and flash a 2.2 rom". No dice either. After having a look at my phone, the technician told me that my hardware is (too) "new" or something, and I would have to leave my phone with him overnight for him to study it. But he has rooted other Desires before.
He also told me that my Desire would never get Froyo OTA. (because its AP?)
Question: Whats the deal? Are there really Desire's with new hardware out?
eden2812 said:
Good day
I have just gotten my Desire a few days back. So far so good. I'm really pleased with it, but I still have a couple of questions (which hopefully can be answered here).
I suppose when I bought my phone, it was an AP phone. And I also will assume that it is from Asia/Asia Pacific/South East Asia because I have a choice of using English (Malaysian), English (Singaporean), and others, as well as a Thai and PinYin keyboard. My Desire also has a preset Scene, called HTC Asia. No big deal, I'm from Malaysia anyway.
Question: What is a sure-fire way to check out where my phone is from?
And I will also assume that it is unbranded. I have read a few posts, and branded phone will have the service provider logo appear on start up. Mine doesn't.
Question: Does this mean it is unbranded? Or just unlocked? How would I know if it is unlocked?
I tried updating my Desire to Froyo. No luck. Searching for software updates through the phone yields no results. The message telling me that my phone is up to date keeps popping up whenever I search. Here is my software information.
Firmware Version 2.1update1
Baseband version 32.41.00.32U_4.08.00.09
Kernel Version 2.6.29-b7e82785 htc-kernel(at)and18-2 #1
Build number 1.19.707.7 CL171460 release-keys
Software Number 1.19.707.7
Browser Version WebKit 3.1
Question: Why is this so? Isn't Froyo out for SEA? Or does my phone's origins have something to do with the Froyo update? Will I even get a Froyo update?
I've actually brought my phone to a technician, just to chat abit, but then I decided, "Heck, if I can't get froyo, I might as well root it and flash a 2.2 rom". No dice either. After having a look at my phone, the technician told me that my hardware is (too) "new" or something, and I would have to leave my phone with him overnight for him to study it. But he has rooted other Desires before.
He also told me that my Desire would never get Froyo OTA. (because its AP?)
Question: Whats the deal? Are there really Desire's with new hardware out?
Click to expand...
Click to collapse
im not sure if the froyo update has hit asia yet, but there is no problem at all with rooting, yes there is a new type of desire with a slcd screen, thats the only new hardware i can think about, but even that can be easly rooted, look in the android development section for guides
Hello,
I am very new to the Android scene, I just bought two GN from expansys. And it seems that one of the phones is google version which is fully updated but the samsung version wont seem to update.
Please note: I am in canada and have yet to put a carrier sim in it. just wifi for now. my specs read,
baseband version i9250xxkk1
build number: i9250xwkk5_ITL41D
Should i return this phone for this? The phone works great and has a great screen so I am hoping I can just keep it. I am moving to the uk in feb so I ma thinking once I put a uk sim in the update will get pushed to the device?
thanks for you help.
What's your build name in the build.prop?
its says in my settings that the build number is i9250xwkk5_itl41d
which is weird since most people have just the ITL41D OR F version. mine seems to be longer. maybe this is what the samsung update was?
thanks for the reply btw
I'd just reflash it all to the latest google build if I were you.
sounds good I will reflash it. I can only follow instructions in numberic sequence. is there a link that I could get that shows me how to do that?
thanks for reply
Good evening.
I'm living in Japan and after years of head aches and troubles with japanese-market-only phones I decided to get a new-no-contract-sim-free phone
I chose the Zenfone 2 due to its price and update availability..
It says it should get an update to Android 6.0 but when I tried to update I noticed its only on Android 5.0
No 5.1 or 5.2...
This phone was release in January if Im not mistaken.. is it possible they didnt update it nor fix any bugs in a year ?!
OR...
Does it the next chapter of me getting screwed cause I'm living in Japan?
I've check about the update and it says on their site FAQ that it is possible to update manually... Push a zip file..
https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/
The latest version is:
Version WW_2.20.40.139
but I noticed there are WW CN TW and *drums rolling* JP versions...
Now, in some of the other versions I saw mentioning of JP thingy being updated... does it means I can Install a WW version on a JP phone ?
example:
25.Fix JP FlipFont issue
29.Remove BookLive from JP SKU
They write that:
3. Only apply to same SKU update, Example: WW->WW, CN->CN, .
so.. do I have to wait for a JP SKU ?!
My current ver. is:
Android 5.0 JP_2.20.40.97_20150917 (update from 3 months ago? yet still android 5.0!?)
Baseband : 1527_5.0.35.1_0815,1527_7.0.20.0_0723
Kernel version: 3.10.20-x86_64........
Build number: LRX21V.JP-ASUS_Z00A-2.20.40.97_20150917
Again.. is this a regional thingy?
Are all other Zenfone 2 still stuck on Android 5.0?
Btw I've got an unrooted 2GB version...
Thanks in advance to all the helpers
6.0 hasn't come out yet. We are all waiting for it.
Hi the whole "latest" android version thing is a plague caused OEMs and/or the dreadful carriers versions, they always (think they have to) add their flavor on top vanilla (stock) android, be it a launcher (the interface), replacing stock android and/or google apps, sometimes with good and fast results (e.g. Motorola) because they add to stock android rather than changing the whole thing (e.g. freaking Samsung).
You're better off flashing a custom ROM, if you follow instructions CAREFULLY it would take an hour if you're a beginner as it's hard -but not impossible- to brick newer phones.
Game Hustla said:
Hi the whole "latest" android version thing is a plague caused OEMs and/or the dreadful carriers versions, they always (think they have to) add their flavor on top vanilla (stock) android, be it a launcher (the interface), replacing stock android and/or google apps, sometimes with good and fast results (e.g. Motorola) because they add to stock android rather than changing the whole thing (e.g. freaking Samsung).
You're better off flashing a custom ROM, if you follow instructions CAREFULLY it would take an hour if you're a beginner as it's hard -but not impossible- to brick newer phones.
Click to expand...
Click to collapse
Question though..
Since its the JP SKU .. will I have problems ?
I had lots of problems on my XPERIAs, since they had JP systems/kernel/everything...
I only have experience tinkering with various japanese xperias... this is my first ZEN so... It should be easier to root and such than sony's... right?
It's easier to root and unlock bootloader than sony! As for changing JP to WW version of the firmware there is a guide how to. No risk of brick since you are familiar with these procedures as i read.
Hi @major9686
Do you recieve the monthly security and bug fix updates?
It seems that the japanese market has both WW and JP SKU phones. Hence the anomaly on the support page.
I don't know, flashing WW might break your cellphone service.
So 2.20.40.97 JP is the version your phone should have.
Yes the stock is still on android 5.0. and in time you will get 6.0 as will we all.
Android 6.0 is confirmed. But will take some time. This is true about most of the phones, except few who gets quick updates. Asus is still better than others.
Sent from Asus ZenFone 2 with Tapatalk
I dont really like my Asus so far ...
My EeePC gave me problems back in the day, the battery died and I cant replace it no one sells it anymore...
It barely lasted 2 years... now it only runs when plugged and even then lags (even after getting an SSD inside)
My Nexus 7 is also a bit laggy even after factory reset, only bought it 6 months ago
and my recently bought Zenfone 2, already been to repair once but problem still persists. Ear Receiver doesnt work, only if I press the screen around the ASUS logo, some sound gets out.
GPS is messed up, gyroscope as well.
SIM Card 1 is giving me trouble, only after several resets, factory reset and whats not it suddenly became readable without becoming unavailable after every few seconds...
and the most annoying thing, after the repair the USB port became loost, the cable isnt held in place as well as it was before the repair.
But you get what you paid for... so far I had a few Xperias and they all had great build quality. I'm soooo sorry I decided to get an asus this time
whats more, even getting an Asus sim-free I get stuck with the Japanese kernel which doesn't allow me to remove the friggin shutter sound from the camera unless I'll root it
Getting this piece was a big mistake. build quality is sooo bad!
Last Asus I'll ever buy...
In PC components already learned my mistake years ago and changed to Gigabyte...
And dont get me started on being stuck on Android 5.0 ... at least with sony we get 1-2 updates...
I got tired of waiting for an update. Bad battery life and Asus apps using most of the memory so I decided to unlock the boot loader yesterday with their software, rooted and installed Bliss Rom based on CM 6.0.1 witch is awesome
Hi,
I found the latest 2.20.40.164 firmware for Japan SKU on their support website.
NB: This is a full ROM.
Download
Sent from my GT-I9500
Hi,
getting my hands on a 520M - I cannot find info for twrp/recovery info stating specifically a given version works on the M model. (this is a latin american regional model as I understand it), but the phone comes unlocked, assume it is 6.0 though I can upgrade to an early 7.0 version (avoiding the u2/u3 bootloader issues).
Can/might it work with https://forum.xda-developers.com/sa...fficial-release-twrp-recovery-galaxy-t3648152 ? Or looking at it another way, are there any hardware differences that might make it likely to have issues?
Any insight appreciated,
DullPeon said:
Hi,
getting my hands on a 520M - I cannot find info for twrp/recovery info stating specifically a given version works on the M model. (this is a latin american regional model as I understand it), but the phone comes unlocked, assume it is 6.0 though I can upgrade to an early 7.0 version (avoiding the u2/u3 bootloader issues).
Can/might it work with https://forum.xda-developers.com/sa...fficial-release-twrp-recovery-galaxy-t3648152 ? Or looking at it another way, are there any hardware differences that might make it likely to have issues?
Any insight appreciated,
Click to expand...
Click to collapse
From my understanding the letter behind the SM-520x just marks the region, the hardware used should be the same however. I would try it, but make sure to download your stock recovery, so you can fix it, just in case it doesn't work out correctly! Hope i could help
Hey guys
I bought a g7 play xt1952-1 phone from tecobuy (it all came packaged like a brand new phone)
The firmware is showing version ppy29. 105-57
The software channel is showing reteu, hardware version pvbt (is that hardware version correct?)
When I run software update check it shows its up to date with march update..however when I check some of the firmware sites they list newer firmware.
Can anyone confirm what the latest firmware is?or how do I check which reteu region is my firmware ? (like which reteu country)
Or can I download the other reteu firmware and flash it without unlocking the boot loader??
ive discovered my cid when running the fastboot command is cid 32
all the other firmware available...is usually cid50..
anyone know what region cid32 is supposed to be? this phone is supposed to be international/eu?
also when i ran the lenovo recovery software (lenovo smart assist)for the phone...it downloaded the CID50 firmware and i tried or did install that one..however when i still check using fastboot it still showing cid32..
and whats the difference between cid32 and cid50?
could cid32 be the demo display model?
redavenger said:
also when i ran the lenovo recovery software (lenovo smart assist)for the phone...it downloaded the CID50 firmware and i tried or did install that one..however when i still check using fastboot it still showing cid32..
and whats the difference between cid32 and cid50?
could cid32 be the demo display model?
Click to expand...
Click to collapse
It appears that the latest firmware build for your variant of the xt1952-1, RETEU, is PPY29.105-134 (cid50) which would have a security patch level of June 1st. You can download the latest firmware build from this repo of official stock moto firmwares.
https://mirrors.lolinet.com/firmware/moto/channel/official/RETEU/
Don't give a lot of thought to the cid nomenclature. If your device is the RETEU xt1952-1, the link above will definitely provide you with the latest, correct build for your device. Of course, you may install this firmware with a locked or unlocked bootloader. If your bootloader is unlocked, installing the latest firmware via fastboot will not relock it.
The best I can recall, cid32 indicates a factory installed, initial "out-of-the-box" build. But again, do not give much thought to this. Regardless of your exact geographical location, the latest build of PPY29.105-134_cid50 for the RETEU xt1952-1 is the correct build for your phone.
yeah the phone did get flashed with the cid50 rom..with a locked bootloader...its all working correctly.
only thing i can put the cid32 version down to is that it could be a south eastern european version...as the instructions in the box are for romania/slovakia/hungary/bulgaria
so could cid32...be referring to the retail eu version for that region?
also it would be good if i can get my hands on the cid32 firmware version.
redavenger said:
yeah the phone did get flashed with the cid50 rom..with a locked bootloader...its all working correctly.
only thing i can put the cid32 version down to is that it could be a south eastern european version...as the instructions in the box are for romania/slovakia/hungary/bulgaria
so could cid32...be referring to the retail eu version for that region?
also it would be good if i can get my hands on the cid32 firmware version.
Click to expand...
Click to collapse
I agree that it's possible, but not a practice traditionally implemented by Motorola in the past. Anyway glad everything worked out for you mate. I'll dig a little further into the cid32 just out of curiosity and see what I can find on my end.
yeah if you could find out what the cid32 means that would be great...and if you could get your hands on the cid32 firmware too?
redavenger said:
yeah if you could find out what the cid32 means that would be great...and if you could get your hands on the cid32 firmware too?
Click to expand...
Click to collapse
The cid value is 100% insignificant when it comes to ascertaining the correct build. With Motorola smartphones, the two factors which matter are the model number (almost always beginning with "XT") and the firmware channel (e.g. RETEU, RETAIL, AMZ, SPRINT, etc.). As long as these match your getvar values, then you have the correct build. With the cid nomenclature, a lower number doesn't necessarily indicate an older build. In other words, there are scenarios whereas a cid32 value can be a newer build than a firmware package with a cid50 value. I chatted with Lenovo tech support on this. I hope this info helps.
If you are searching for the newest build for your device with a cid32 value, versus the cid50, it does not appear that such a build exists. Lenovo is not aware of any such build and my search within Motorola firmwares repos didn't turn up anything. All info indicates that you are running the correct build for your device.
yeah its a funny thing though..the phone came with cid32 firmware build...dated for march 2019...so already it was running outdated firmware out of the box..and it didn't pick up any OTA updates either..
when i tried flashing via lenovo smart assist program..it downloaded the current cid50 reteu firmware...the program did try to flash it..and it said it was successful...but it wasn't because it was still running the march 2019 updates...anyway i used fastboot commands to install the firmware..
thats why i am very curious as to why the phone is still set as a cid32? and why didnt it just switch to cid50 when i tried using the lenovo smart assist program.
somebody at lenovo should know what the cid32 means.
redavenger said:
yeah its a funny thing though..the phone came with cid32 firmware build...dated for march 2019...so already it was running outdated firmware out of the box..and it didn't pick up any OTA updates either..
when i tried flashing via lenovo smart assist program..it downloaded the current cid50 reteu firmware...the program did try to flash it..and it said it was successful...but it wasn't because it was still running the march 2019 updates...anyway i used fastboot commands to install the firmware..
thats why i am very curious as to why the phone is still set as a cid32? and why didnt it just switch to cid50 when i tried using the lenovo smart assist program.
somebody at lenovo should know what the cid32 means.
Click to expand...
Click to collapse
I have a Moto E 2015 (2nd Gen) and a Moto G 2013 (1st Gen) which are both untouched and in out-of-the box states. A fastboot getvar command on both returns a cid32 value. I should also mention that both of these devices are US variants (the Moto E is a Sprint variant (Boost Mobile), while the Moto G is a GSM unlocked retail). This would lead me to believe that the cid32 value is indicative of an undistributed, out-of-the-box firmware build that was installed at the factory by the OEM. (Both of these devices use cid50 firmware packages which have been officially released.) I, too, would think that a Lenovo employee would know the meanings of the various cid values. The two I've chatted with -- both from tech support -- either do not know or will not say. (I should note that Lenovo and Motorola Mobility are known for classifying certain firmware information as classified. I ran into a brick wall a couple years back while attempting to get more information on the public release of certain blankflash files used to restore hard bricked Moto devices via EDL (qload) mode. Motorola maintained the position that any blankflash files available to the public had been leaked and not officially or unofficially released. Motorola stated that they do not release blankflash files under any circumstances for security reasons).
I have researched this some more on various Moto device forums here on XDA. It appears that the cid value within firmware package names is indicative of regional differences in the radio firmware files only (with Moto firmware packages, the radio firmware typically encompasses both the NON-HLOS.bin and the fsg.mbn files). In other words, take two firmware packages, one with a cid32 value and the other with cid50, but otherwise everything is the same. From what I've gathered, the only difference between the two packages would be the radio firmware builds.l, Many firmware packages use a "universal" radio firmware build. For example, my two Moto devices that I mentioned previously will run perfectly fine on cid50 firmware, although they shipped with cid32. In your case, it appears that the circumstances are the same. If you are having no signal or data connection issues, then the cid50 package on your device is perhaps a "catch-all" radio firmware type. In any event, so long as you aren't having any type of adverse signal issues or data connectivity problems, the cid50 radio firmware running on your device now is fully compatible and correct in type. But, please keep in mind that I'm going on research and personal experience with Moto brand devices. My theory on the cid value could be completely wrong, so please do not quote me on fact. I hope the info helps some.
interesting viva......it makes the whole cid32 value quite interesting.
my g7 play version with cid32 value is or was a bulgaria/romanian shipped version...so if your phones were us variants with cid32 value then yes it probably doesn't mean a regional area, but like you mentioned possibly some kind of a "undistributed, out-of-the-box firmware build that was installed at the factory"...still it would very interesting to know why some phones come with cid32 and others cid50.
redavenger said:
interesting viva......it makes the whole cid32 value quite interesting.
my g7 play version with cid32 value is or was a bulgaria/romanian shipped version...so if your phones were us variants with cid32 value then yes it probably doesn't mean a regional area, but like you mentioned possibly some kind of a "undistributed, out-of-the-box firmware build that was installed at the factory"...still it would very interesting to know why some phones come with cid32 and others cid50.
Click to expand...
Click to collapse
Yeah, quite perplexing, and a topic of which your original post has made me curious. I am still researching the cid values and will post any info I come across.
out of curiosity the devices you had, were they bought through official channels? or through 3rd party shops...especially the retail phone you bought.
i'm thinking maybe the cid32 value could mean a oem phone which is to be sold to or via 3rd party channels? like a re-seller? for example i got my g7 play via tecobuy, which is one those re-sellers and not a official supplier...so that way motorola doesn't provide a warranty, but it has to go back to the re-seller?
redavenger said:
out of curiosity the devices you had, were they bought through official channels? or through 3rd party shops...especially the retail phone you bought.
i'm thinking maybe the cid32 value could mean a oem phone which is to be sold to or via 3rd party channels? like a re-seller? for example i got my g7 play via tecobuy, which is one those re-sellers and not a official supplier...so that way motorola doesn't provide a warranty, but it has to go back to the re-seller?
Click to expand...
Click to collapse
My Moto G was purchased directly from Motorola, while my Moto E was purchased from Best Buy.
i guess that throws my theory out the window
redavenger said:
i guess that throws my theory out the window
Click to expand...
Click to collapse
Not necessarily. Best Buy is a first tier retailer that receives preferential treatment from most suppliers. Joe's Discount Phones and Vape located in the back of the 24 hour convenience store (or a trailer) is another story.
That said, I agree cid is meaningless from a consumer/modder perspective.
i think i have another theory what the cid32 might mean.
i think it could mean that its not to receive any updates?
for example when i flashed the phone using LMSA...it downloaded the reteu cid50 version....however the phone still shows cid32...anyway forward a month and there is a new software update version 105-134-2, however the phone doesnt pick it up when using the update check on the phone...
however using LMSA..its downloading this newer version.
anyway could this cid32 mean that its a restricted phone which isnt supposed to get OTA updates?
hey , i found this one in a lenovo forum
it seems to be the cid32 & cid50 versions just mean a retail device
https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Moto-g7-play-firmware-version/td-p/4507434
maybe it helps to answer your question
overdoxx11 said:
hey , i found this one in a lenovo forum
it seems to be the cid32 & cid50 versions just mean a retail device
https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Moto-g7-play-firmware-version/td-p/4507434
maybe it helps to answer your question
Click to expand...
Click to collapse
Cool. That makes sense. I recently ran across a scenario where a firmware package with a cid32 tag was installed to a Moto G3 which showed cid50 tag via fastboot getvar all. Even after the fastboot installation of the firmware, the cid50 tag showing on the device did not change.