Would anybody be so nice to post the values of these properties:
ro.build.description
ro.build.oemfingerprint
Thank you so much 8n advance!
Tell me how to and I will gladly help you mate
Jaizu said:
Tell me how to and I will gladly help you mate
Click to expand...
Click to collapse
Open a shell (adb or local shell), and type these two commands:
Code:
getprop ro.build.description
getprop ro.build.oemfingerprint
Each command will give you the value of the prop. Just copy all 4 lines (the command and the output x2) here. I'm not sure, if the device needs to be rooted, but I think it should work.
The second method is: open /system/build.prop in any editor that can handle read only filey for just reading (nearly all... , and copy the two lines with the properties in question.
Thanx!
Code:
getprop ro.build.description=OnePlus3-user 8.0.0 OPR6.170623.013 121 release-keys
getprop ro.build.oemfingerprint=8.0.0/OPR6.170623.013/09180121:user/release-keys
marcelotorres said:
Code:
getprop ro.build.description=OnePlus3-user 8.0.0 OPR6.170623.013 121 release-keys
getprop ro.build.oemfingerprint=8.0.0/OPR6.170623.013/09180121:user/release-keys
Click to expand...
Click to collapse
Wow! Thanx! Are you sure that OxygenOS 4.1.7 for oneplus3t published on 0825 is though being based on android 7.1.1 is shiped with an oreo build fingerprint? Sorry, if I ask to verify, but this seems so strange to me, that I just want to make sure.
nvertigo67 said:
Wow! Thanx! Are you sure that OxygenOS 4.1.7 for oneplus3t published on 0825 is though being based on android 7.1.1 is shiped with an oreo build fingerprint? Sorry, if I ask to verify, but this seems so strange to me, that I just want to make sure.
Click to expand...
Click to collapse
I'm running Lineage 15 and I have the same build fingerprint.
This means he didn't read the fact that you need OxygenOS.
ast00 said:
I'm running Lineage 15 and I have the same build fingerprint.
This means he didn't read the fact that you need OxygenOS.
Click to expand...
Click to collapse
What more can I do, then putting the most important information in the title? Assuming that people don't want to read every single thread, but only if interested in the topic, which is displayed in the overview... Anyway, thanx for informing me! (version and key date couldn't be by any means 4.1.7)
ro.build.description=OnePlus3-user 7.1.1 NMF26F 108 dev-keys ro.common.soft=OnePlus3 ro.display.series=OnePlus 3T ro.build.oemfingerprint=7.1.1/NMF26F/08081200:user/release-keys
Model ONEPLUS A3003
OxygenOS version 4.1.7
RAM 6GB Internal Storage 128GB
BUILD NUMBER ONEPLUS A3003_28_170818
ro.build.description OnePlus3-user 7.1.1 NMF26F 108 dev-keys
ro.build.oemfingerprint 7.1.1/NMF26F/08081200:user/release-keys
Related
Huawei Mate S is now ready to join the marshmallow fray!
Important bits on below:
What you need to know
-This beta registration is only open for Malaysia variant of Huawei Mate S (CRR-UL00)
-The experimental build of Android Marshmallow 6.0 / EMUI4.0 will be release in the form of OTA (over the air) to registered Huawei Mate S that runs on latest lollipop version (CRR-UL00C470B146)
-Since this is an experimental build, unexpected issues/bugs may arise at any point at anytime.
-Huawei Technologies (Malaysia) SDN BHD is not liable for any damage to or loss of any programs, data, or other information stored in user device due to the use of said experimental build software-Before proceeding with the upgrades, registered user(s) is advised to perform any necessary backup
If you understood all of the above, and would still like to be a part of this program, kindly click on this link to register, by 26th February 2016, 12am.
Once you have successfully registered, sit back and relax, and the experimental build software will be seed to all registered users by Q1 2016.
Nothing is perfect, if you have encoutered issues/bug during your time with the beta testing. We would appreciate your feedback, simply by clicking on this link (*not ready).
If you felt that the experimental build (or beta) Android Marshmallow is unstable, you can choose to downgrade. Thus, do look out for this space for future update.
Release Notes (*coming soon)
*************************************
Source
*********************************************
register quickly
Does anyone know where to get a copy of CRR-UL00C470B146? I only have B115 and cannot find 146 anywhere?
Any One?
Sathelp said:
Does anyone know where to get a copy of CRR-UL00C470B146? I only have B115 and cannot find 146 anywhere?
Any One?
Click to expand...
Click to collapse
Huawei Mate S Firmware(CRR-UL00, Android5.1, EMUI 3.1, C433B146, UAE)
as close to b146 as possible
Thanks but to change the location to C433 to C470 would defeat the object as the Marshmallow beta in this instance is for C433 only. I have run C470 and the raw C000 but happy with C433. I still hold a copy of C433B146.
Thanks but someone must have it or why would they set it as a base target ton upgrade from?
andromodgod said:
Huawei Mate S Firmware(CRR-UL00, Android5.1, EMUI 3.1, C433B146, UAE)
as close to b146 as possible
Click to expand...
Click to collapse
How can i find this c433b146 in android 6? I bought this mate s on second hand and i cant find the way to update
Hello all,
I would like to use a Honor 4x (Cherry) Cyanogen ROM (this one) for my Y6 SLT-L01. I figured it would be possible based on this thread of someone making a TWRP recovery for the Y6 based on the Honor 4x.
At first I just tried flashing the zip from TWRP, but the updater_script stopped me with a :
"This package is for device: c8817d,g620s,C8817D,C8817E,G621-TL00,G620S-UL00,G620S-L01,Che1-CL10,Che1-CL20,Che1-L04; this device is Honor4A."
And so I opened up the cm-13.0-20160504-NIGHTLY-cherry\META-INF\com\google\android\updater_script and removed the assert line spitting out the error, but now I just get a rather non-descriptive:
"Error flashing zip '/(emmc or sdcard, neither works)/cm-13.0lkdslk;lasd-NIGHTLY-cherry.zip'" - full log is attached below
I compared the build prop of my device, and that of the ROM I want to flash, and most of the items look pretty similar or compatible. For example, the ro.board.platform is msm8909 for my device and msm8916 for the ROM.
I've also attached both build props below.
At the end of the day, my question is: Is it possible to hack something quick that will let me use this ROM with my phone because the hardware is so similar? I would rather do that then set up a whole android ROM development build environment. Any advice would be appreciated.
maybe someone here can port it, btw has kernel sources of Y6 released??
Someone can do it, but he needs the proper files
without proper kernel sources i think it would not be possible
Kernel source isn't the most important, proprietary vendod files and device tree are crucial
venom007 said:
without proper kernel sources i think it would not be possible
Click to expand...
Click to collapse
Kernel source are released for the huawei y6
Amaan007 said:
Kernel source are released for the huawei y6
Click to expand...
Click to collapse
maybe someone will port it
Amaan007 said:
Kernel source are released for the huawei y6
Click to expand...
Click to collapse
If it's already released then there's no need to port. Better to build from source.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
If it's already released then there's no need to port. Better to build from source.
Click to expand...
Click to collapse
Well , if any dev owns that device then surely they will get roms
Fworg64 said:
Hello all,
I would like to use a Honor 4x (Cherry) Cyanogen ROM (this one) for my Y6 SLT-L01. I figured it would be possible based on this thread of someone making a TWRP recovery for the Y6 based on the Honor 4x.
At first I just tried flashing the zip from TWRP, but the updater_script stopped me with a :
"This package is for device: c8817d,g620s,C8817D,C8817E,G621-TL00,G620S-UL00,G620S-L01,Che1-CL10,Che1-CL20,Che1-L04; this device is Honor4A."
And so I opened up the cm-13.0-20160504-NIGHTLY-cherry\META-INF\com\google\android\updater_script and removed the assert line spitting out the error, but now I just get a rather non-descriptive:
"Error flashing zip '/(emmc or sdcard, neither works)/cm-13.0lkdslk;lasd-NIGHTLY-cherry.zip'" - full log is attached below
I compared the build prop of my device, and that of the ROM I want to flash, and most of the items look pretty similar or compatible. For example, the ro.board.platform is msm8909 for my device and msm8916 for the ROM.
I've also attached both build props below.
At the end of the day, my question is: Is it possible to hack something quick that will let me use this ROM with my phone because the hardware is so similar? I would rather do that then set up a whole android ROM development build environment. Any advice would be appreciated.
Click to expand...
Click to collapse
Probably not
136fei said:
Probably not
Click to expand...
Click to collapse
There are quite a few roms on huawei y6 development thread
Amaan007 said:
There are quite a few roms on huawei y6 development thread
Click to expand...
Click to collapse
Can you link them here?
adriansticoid said:
Can you link them here?
Click to expand...
Click to collapse
https://forum.xda-developers.com/huawei-y6/development
Amaan007 said:
https://forum.xda-developers.com/huawei-y6/development
Click to expand...
Click to collapse
Thanks man.
Sent from my Honor 8 using XDA Labs
Amaan007 said:
https://forum.xda-developers.com/huawei-y6/development
Click to expand...
Click to collapse
+1
This is something I've been looking into in order to find newer, older, and unreleased updates for the Mi Mix 2.
Ideally, I'd like to figure out a way to get Xiaomi's nightly builds, which go out to only beta testers. I think I'm close, but any help I can get would be awesome.
I currently have two methods. One of them is rather difficult, the other is rather easy. Let's start with the easy one.
Method 1: Example 1
http://update.miui.com/updates/mi-updateV6.php?v=MIUI-7.9.21&c=7.1&d=chiron_global&b=X
This is a URL which asks for an update to the unreleased MIUI 9 7.9.21 global edition.
If you visit this URL, you get the following response:
Code:
{"UserLevel":9,"LatestVersion":{"type":"rom","device":"chiron_global","name":"XM-MIMIX2-GLOBAL 7.9.21","description":"MIUI\u5347\u7ea7","descriptionUrl":"http:\/\/update.miui.com\/updates\/updateinfo\/7.9.21\/chiron_global_0_7.9.21_4494ccfcc506caca9904efb74b489e0a.html","md5":"7f94ca393fae77c6171e6c7a551bea2e","filename":"miui_MIMIX2Global_7.9.21_7f94ca393f_7.1.zip","filesize":"1.6G","codebase":"7.1","version":"7.9.21","branch":"X"},"UpdateList":[{"type":"rom","device":"chiron_global","name":"XM-MIMIX2-GLOBAL 7.9.21","description":"","descriptionUrl":"http:\/\/update.miui.com\/updates\/updateinfo\/7.9.21\/chiron_global_0_7.9.21_4494ccfcc506caca9904efb74b489e0a.html","md5":"7f94ca393fae77c6171e6c7a551bea2e","filename":"miui_MIMIX2Global_7.9.21_7f94ca393f_7.1.zip","filesize":"1.6G","codebase":"7.1","version":"7.9.21","branch":"X"}],"IncrementalUpdateList":[],"MirrorList":["http:\/\/bigota.d.miui.com"],"Signup":{"version":"","total":"","rank":""},"AuthResult":0,"ForceUpdate":0
We can piece together looking at this that the update file can be downloaded at:
http://bigota.d.miui.com/7.9.21/miui_MIMIX2Global_7.9.21_7f94ca393f_7.1.zip
Method 1 Example 2
It was announced today that there was a new Chinese stable release pushed only to some phones called 8.5.7.0.NDECNEF. We can modify the parameters in the URL to get this:
http://update.miui.com/updates/mi-updateV6.php?v=MIUI-V8.5.7.0.NDECNEF&c=7.1&d=chiron&b=S
This returns the following:
Code:
{"UserLevel":9,"LatestVersion":[],"UpdateList":[{"type":"rom","device":"chiron","name":"XM-MIMIX2 V8.5.7.0.NDECNEF","description":"","descriptionUrl":"http:\/\/update.miui.com\/updates\/updateinfo\/V8.5.7.0.NDECNEF\/chiron_0_V8.5.7.0.NDECNEF_a9374e7e6aa4f38a22fd58aae29337ce.html","md5":"487f34ee14e84d0eb9ed280a059bcc65","filename":"miui_MIMIX2_V8.5.7.0.NDECNEF_487f34ee14_7.1.zip","filesize":"1.4G","codebase":"7.1","version":"V8.5.7.0.NDECNEF","branch":"F"}],"IncrementalUpdateList":[],"MirrorList":["http:\/\/bigota.d.miui.com"],"Signup":{"version":"","total":"","rank":""},"AuthResult":0,"ForceUpdate":0}
And that lets us know that the update can be found at:
http://bigota.d.miui.com/V8.5.7.0.NDECNEF/miui_MIMIX2_V8.5.7.0.NDECNEF_487f34ee14_7.1.zip
So now that we see that we have a way to query for downloads, let's look into some of the parameters.
At a minimum we need the following:
v=MIUI-V8.5.7.0.NDECNEF - This is the version with which you are querying.
c=7.1 - This is the build of Andoid. It's Android 7.1 so we put 7.1
d=chiron - This is the device. For Chinese Mix 2 firmwares it's chiron. For global it's chiron_global
You might also notice this:
b=S - S means stable. X means weekly. Actually, there is a whole list as follows, but not sure how accurate it is:
Code:
«S» — monthly build
«X» — weekly build
«D» — daily build
«E» — emegency build
«F» — stable build
«A» — experimental build
«I» — internal build
«T» — top secret build
«U» — unstable build
On top of this, there are more possible parameters. I will get around to these when talking about Method 2.
Right now, I can't access anything but weekly and stable builds, so there are not really any undiscovered/unannounced/internal builds that I've been able to find. But I think we are on the right track to being able to find them. I'm hoping that other people can continue looking using this information, and we'll see if we can find anything. Stay tuned while I update this post with Method 2, which is much more complex and much more likely to yield results.
If you want to keep my stomach full while I keep this research going, give the Donate button a click!
Reserved
Isn't this link (http://bigota.d.miui.com/7.9.21/miui_MIMIX2Global_7.9.21_7f94ca393f_7.1.zip) global miui 9?
I say because Chinese dev rom (miui 9) is the same miui version (7.9.19 which is a lower firmware number)
punkmonkey1984 said:
Isn't this link (http://bigota.d.miui.com/7.9.21/miui_MIMIX2Global_7.9.21_7f94ca393f_7.1.zip) global miui 9?
I say because Chinese dev rom (miui 9) is the same miui version (7.9.19 which is a lower firmware number)
Click to expand...
Click to collapse
Yes, that's global miui 9, but it's old. I'd like to find a newer one.
Caitlin550 said:
<snip>
Click to expand...
Click to collapse
Before you snipped it.... it's from September 21, so it's a month old.
Caitlin550 said:
I believe this is the global version? I know this is different to Xiaomi's global MIUI9 releases
https://sourceforge.net/projects/xi...i.eu_multi_MIMix2_7.10.19_v9-7.1.zip/download
Click to expand...
Click to collapse
It's a modified version of the Chinese ROM. It's not the official global ROM from Xiaomi.
duraaraa said:
Yes, that's global miui 9, but it's old. I'd like to find a newer one.
Click to expand...
Click to collapse
Have you tried it? Does it work without issues?
Does it receive OTA updates to a newer one?
punkmonkey1984 said:
Have you tried it? Does it work without issues?
Does it receive OTA updates to a newer one?
Click to expand...
Click to collapse
Yes, I tried it. It works without issues. It does not receive any newer OTA right now. Hopefully soon.
duraaraa said:
Yes, I tried it. It works without issues. It does not receive any newer OTA right now. Hopefully soon.
Click to expand...
Click to collapse
Any way to update from global stable to this one without wiping all my apps, I still have to wait a few days to unlock my device officially.
punkmonkey1984 said:
Any way to update from global stable to this one without wiping all my apps, I still have to wait a few days to unlock my device officially.
Click to expand...
Click to collapse
Sorry, I don't know. I was only able to get it working with fastboot flashing.
duraaraa said:
Sorry, I don't know. I was only able to get it working with fastboot flashing.
Click to expand...
Click to collapse
This is my first miui device, using miflash, I cant select the .zip file as it's not a fastboot image.
How did you manage to flash the .zip with fastboot flashing ?
punkmonkey1984 said:
This is my first miui device, using miflash, I cant select the .zip file as it's not a fastboot image.
How did you manage to flash the .zip with fastboot flashing ?
Click to expand...
Click to collapse
I used sdat2img.py to convert the system data to something flashable. Then I looked up which partitions need to be flashed where by checking a flash-all.bat file, and followed that format using fastboot to flash each partition.
But... there's no reason to flash this. It's not a public release and it doesn't really do anything better than other choices. I think flashing xiaomi.eu is a better choice.
duraaraa said:
I used sdat2img.py to convert the system data to something flashable. Then I looked up which partitions need to be flashed where by checking a flash-all.bat file, and followed that format using fastboot to flash each partition.
But... there's no reason to flash this. It's not a public release and it doesn't really do anything better than other choices. I think flashing xiaomi.eu is a better choice.
Click to expand...
Click to collapse
Thanks for the reply, Good luck with digging with the OTA update .zips, hopefully, you manage how to capture the download newer unreleased files to share with us all. :good::good:
I was able to get the link for China Stable MIUI 9, first release.
http://bigota.d.miui.com/V9.1.1.0.NDECNEI/miui_MIMIX2_V9.1.1.0.NDECNEI_53c332ffe5_7.1.zip
duraaraa said:
I was able to get the link for China Stable MIUI 9, first release.
http://bigota.d.miui.com/V9.1.1.0.NDECNEI/miui_MIMIX2_V9.1.1.0.NDECNEI_53c332ffe5_7.1.zip
Click to expand...
Click to collapse
Good work,. Miui 9 is really nice. I'll give this update a try now is downloading on ADM.
new ota? 8.5.2.0MIUI
Is there a link for Redmi 4 Prime for Nougat under experimental? hehe
I was able to find the first MIUI 9 Stable (non-developer) global build for Mix 2.
http://bigota.d.miui.com/V9.1.1.0.NDEMIEI/miui_MIMIX2Global_V9.1.1.0.NDEMIEI_232bee13eb_7.1.zip
Caveat is, I think it's actually older than the most recent developer build.
duraaraa said:
I was able to find the first MIUI 9 Stable (non-developer) global build for Mix 2.
http://bigota.d.miui.com/V9.1.1.0.NDEMIEI/miui_MIMIX2Global_V9.1.1.0.NDEMIEI_232bee13eb_7.1.zip
Caveat is, I think it's actually older than the most recent developer build.
Click to expand...
Click to collapse
The global dev builds will always be newer and include the most recent bug fixes and security patches, so that's no surprise the stable was built before any of the recent developer ROMs.
Sent from my Mi MIX 2 using Tapatalk
---------- Post added at 08:28 PM ---------- Previous post was at 08:26 PM ----------
Has anyone tried this stable global MIUI 9?
Sent from my Mi MIX 2 using Tapatalk
@duraaraa you can get me link Redmi note 4 QUALCOMM global dev rom daily update? (no weekly)
Hello, could somebody (best on Global ROM PIE), share Fingerprint and fingerprint description which passed SafetyNet? getprop log from Terminal emulator would be enough. I have this fingerprint
Code:
Xiaomi/dipper/dipper:9/PKQ1.180729.001/V10.1.1.0.PEAMIFI:user/release-keys
and I need description. Thanks.
Sent from my MI 8 using Tapatalk
strange note: latest global pie rom uses poco f1 system image...
From system build.prop
Code:
ro.build.description=beryllium-user 9 PKQ1.180729.001 V10.1.3.0.PEJMIFI release-keys
ro.build.fingerprint=Xiaomi/beryllium/beryllium:9/PKQ1.180729.001/V10.1.3.0.PEJMIFI:user/release-keys
From vendor build.prop
Code:
ro.vendor.build.fingerprint=Xiaomi/dipper/dipper:9/PKQ1.180729.001/V10.1.2.0.PEAMIFI:user/release-keys
Dexer125 said:
Hello, could somebody (best on Global ROM PIE), share Fingerprint and fingerprint description which passed SafetyNet? getprop log from Terminal emulator would be enough. I have this fingerprint and I need description. Thanks.
Click to expand...
Click to collapse
So, how's this going? Have you passed safetynet?
Can you please share your working build.prop?
Hello,
I have just purchased a new Asus Republic of Gamers 12gb/512gb CN version from a UK seller but it has the WW rom listed both for the main rom and for the fingerprint (they are the same - I have checked). It has Android 9 but I want to update it to Android 10.
No updates are available through the automated system update and I have tried manually installing the various roms that are available but it constantly returns "System Update Failed".
Three questions:
1. Is it capable of being updated since it is a CN phone but with WW rom?
2. If it can be updated in its current set-up, which rom do I need?
3. If not, do I need to flash it back to a CN rom so that the rom is the same as the phone (i.e. both CN rather than CN for the phone, and WW for the rom)?
The system specifics are:
Build: PKQ1.190414.001
Java VM: ART 2.1.0
Security: 01.10.2019
Baseband: M3.13.33.31-Yoda_875021,M3.13.33.31-Yoda_875021
Incremental: 16.0631.1910.44-0
Description: WW_Phone-user 9 PKQ1.190414.001 16.0631.1910.44-0
Fingerprint: asus/WW-IO01D/ASUS_IO01_1:9/PKQ1.190414.001/16.0631.1910.44-0:user/release-keys
Device features: 124
Many thanks for your help,
sirbb
I think you need to update to latest android 9 (.64) rom before you can update to android 10
Thanks for the reply. Where do I find that ROM and how do I do that?
reg66 said:
I think you need to update to latest android 9 (.64) rom before you can update to android 10
Click to expand...
Click to collapse
sirbb said:
Thanks for the reply. Where do I find that ROM and how do I do that?
Click to expand...
Click to collapse
Just did a search for you, gonna have to read up yourself though and search too.
https://forum.xda-developers.com/rog-phone-2/how-to/1910-64-ww-update-t4021947
Thanks so much Reg66 - sorted. Did the minor update as you suggested then the Android 10 update. Works perfectly - so easy to do!
Much appreciated!