Hi!
I just got my OnePlus 3T about a week ago and i noticed something strange. I installed CPU-Z on it, everything else seems fine but under the Device tab, the Board name shows up as "QC_Reference_Phone" instead of "MSM8996" and its the same on CPU-X and Aida64 as well.
I have no Idea what it means. I looked it up but can't seem to find anything.
Does anyone else have the same thing or is it just me ? And can someone give me an explanation of what it means?
I'm on OxygenOS 4.0.2 Nougat if you need to know.
Such information is hardcoded into the hardware. "QC_Reference_Phone" means it's a modified Qualcomm SoC. I believe OnePlus just forgot to insert a suitable description. This has been mentioned on the OnePlus forum.
Inciter said:
Such information is hardcoded into the hardware. "QC_Reference_Phone" means it's a modified Qualcomm SoC. I believe OnePlus just forgot to insert a suitable description. This has been mentioned on the OnePlus forum.
Click to expand...
Click to collapse
I see. So is there any way to make the app report the correct name ? or any apps which would show the actual board name ?
Mizart said:
I see. So is there any way to make the app report the correct name ? or any apps which would show the actual board name ?
Click to expand...
Click to collapse
I don't think it's "hardcoded in hardware" - it's just another ro property:
Get you phone rooted, get a prop editor (or any text editor, if you know how to remount /system rw; or start the text editor from within a root enabled file browser) and change ro.product.board to whatever you want...
EDIT: you need to reboot, since read only properties can't be changed with setprop.
...change it to "oneplus7" and post screenshots of CPU-Z - I'm sure some peoples attention will be with you... *lol*
nvertigo67 said:
I don't think it's "hardcoded in hardware" - it's just another ro property:
...change it to "oneplus7" and post screenshots of CPU-Z - I'm sure some peoples attention will be with you... *lol*
Click to expand...
Click to collapse
A build.prop value was the first thing that came to my mind as well and there IS one property that allows you to modify the board name indeed but i posted the same thing on other places as well and everyone seems to be saying its hardcoded but the apps just read it off the build.prop. I sent a mail to the OP Support as well, waiting for a reply from them to just confirm this thing and get it off my mind for good.
And as for the other thing. It's a pretty good idea haha but i doubt anyone would fall for it. Editing the build properties is fairly common and anyone would see right through it xD
Mizart said:
A build.prop value was the first thing that came to my mind as well and there IS one property that allows you to modify the board name indeed but i posted the same thing on other places as well and everyone seems to be saying its hardcoded but the apps just read it off the build.prop. I sent a mail to the OP Support as well, waiting for a reply from them to just confirm this thing and get it off my mind for good.
Click to expand...
Click to collapse
Let me put it this way: maybe it's written in sillicon - but the property comes out of system/buid.prop of the flashable zip and it is changeble in build.prop.
I have the unpacked 4.0.2 ota full zip on my disc:
Code:
[email protected] /usr/local/src/oxygenos-4.0.2 $ grep ro.product.board system/build.prop
ro.product.board=QC_Reference_Phone
[email protected] /usr/local/src/oxygenos-4.0.2 $
I wouldn't think too much about it. I think it's because OnePlus's sources are based on caf sources - which doesn't know of OnePlus and just call msm8996 based phones QC_Reference_Phone.
If you are in contact with OnePlus regarding this matter, I would be interested how to read such information directly from the soc.
Related
Found this thread reading through the Fascinate subforum, they had this stickied, for good reason.
Here's the original thread: http://forum.xda-developers.com/showthread.php?t=977154
Rodderik said:
Who is affected? All phones pre-gingerbread
Who should act? Users and developers using pre-gingerbread roms
How do I fix? Flash attached .zip at the bottom of this post or use one of the alternate methods down there
What if I think I was infected? Completely wipe your device, format sdard, go back to stock and re-apply rom, then flash the attached .zip (before installing any apps)
Why should I care? read below...
http://www.androidpolice.com/2011/0...your-phone-steal-your-data-and-open-backdoor/
Link to publishers apps here. I just randomly stumbled into one of the apps, recognized it and noticed that the publisher wasn’t who it was supposed to be.
Super Guitar Solo for example is originally Guitar Solo Lite. I downloaded two of the apps and extracted the APK’s, they both contain what seems to be the "rageagainstthecage" root exploit – binary contains string "CVE-2010-EASY Android local root exploit (C) 2010 by 743C". Don’t know what the apps actually do, but can’t be good.
I appreciate being able to publish an update to an app and the update going live instantly, but this is a bit scary. Some sort of moderation, or at least quicker reaction to malware complaints would be nice.
EDIT: After some dexing and jaxing, the apps seem to be at least posting the IMEI and IMSI codes to http://184.105.245.17:8080/GMServer/GMServlet, which seems to be located in Fremont, CA.
I asked our resident hacker to take a look at the code himself, and he’s verified it does indeed root the user’s device via rageagainstthecage or exploid. But that’s just the tip of the iceberg: it does more than just yank IMEI and IMSI. There’s another APK hidden inside the code, and it steals nearly everything it can: product ID, model, partner (provider?), language, country, and userID. But that’s all child’s play; the true pièce de résistance is that it has the ability to download more code. In other words, there’s no way to know what the app does after it’s installed, and the possibilities are nearly endless.
Click to expand...
Click to collapse
The offending apps from publisher Myournet:
* Falling Down
* Super Guitar Solo
* Super History Eraser
* Photo Editor
* Super Ringtone Maker
* Super Sex Positions
* Hot Sexy Videos
* Chess
* ????_Falldown
* Hilton Sex Sound
* Screaming Sexy Japanese Girls
* Falling Ball Dodge
* Scientific Calculator
* Dice Roller
* ????
* Advanced Currency Converter
* App Uninstaller
* ????_PewPew
* Funny Paint
* Spider Man
* ???
Click to expand...
Click to collapse
http://www.androidpolice.com/2011/0...-android-nightmare-and-weve-got-more-details/
Now, on to some more details of the virus. We should point out that this vulnerability was patched with Gingerbread, meaning any device running Android 2.3+ should be fine. In other words, if you’re looking to play the blame game (which I’m not, but having read all the comments on the original post, many people are), then there’s plenty to go around. The hole was fixed by Google, but it’s relatively useless since many phones aren’t yet running a version of Android that is protected. It’s noteworthy that some manufacturers released updates that patched the exploit for devices without updating to Gingerbread; unfortunately, it appears that minority is quite a small one.
Perhaps most important is the question of what infected users can do about their situation; unfortunately, the answer is not much of anything. Because the virus opens up a backdoor and can bring in new code at any time, the only way to really rid an infected device of any damage is to completely wipe the device – not exactly the optimal solution, but it looks like the only one available, at least for now.
Finally, Justin notes that ROM developers working with pre-Gingerbread versions of Android can prevent the virus from backdooring in code by putting a dummy file at /system/bin/profile.
Click to expand...
Click to collapse
As you can see androidpolice.com reports on this backdoor and roots and steals personal information. The apps are removed from the market but that doesn't mean they got them all. Attached is a flashable fix as suggested by androidpolice.com
So users can flash this .zip or simply create a blank file called profile and place it in /system/bin/ (developers are encouraged to include this file in future releases. A blank file is not going to affect performance at all)
Alternate methods:
Using 'adb shell' or terminal emulator (should work on any ROOTED phone) as suggest by xaueious here
Code:
$ su
su
# remount rw
Remounting /system (/dev/stl9) in read/write mode
# touch /system/bin/profile
# chmod 644 /system/bin/profile
#
Alternate 2:
Download blank profile file from here (or create one and name it profile)
Use a program like Root Explorer to copy it to /system/bin/
Then longpress on it and check the permissions should be read/write for user, read for group, and read for others.
Alternate 3:
cyansmoker has put together an apk for the patch here https://market.android.com/details?id=com.voilaweb.mobile.droiddreamkiller
Thanks for pointing this out photoframd and androidpolice.com for investigating and reporting!
UPDATE: I renamed the .zip file and reuploaded it (350 hits wow). Also in the edify scripted version I added 644 permissions to the file (but if you already flashed it then it should have defaulted to that). I also added a pre-edify version of the patch thanks to xaueious for people using a recovery that does not yet understand edify.
Click to expand...
Click to collapse
thankyou for bringing this to our attention.
Fretless said:
thankyou for bringing this to our attention.
Click to expand...
Click to collapse
I second that! many thanx!
Of course. It surprised me that I hadn't seen this earlier.
I've already committed this to the Incredible S rom base, I suggest other devs do so as well.
How would someone without root plug the hole??? or does this only effect the root users?
The Malware uses rageagainstthecage to root the phone, then does all the dirty work. So I'd guess that it would leave your phone rooted.
Apparently the infected phones are already clean according to Google. They have a way to remote wipe the affected app from your phone and clean up any traces it left, as well as hopefully plugging the whole in the process.
So wait..... I had Cyanogen 7 RC1 running.... And I had Spider man (infected app) installed.... but since then I've changed roms....
Since RC1 is 2.3 am I safe???
Zerox8610 said:
So wait..... I had Cyanogen 7 RC1 running.... And I had Spider man (infected app) installed.... but since then I've changed roms....
Since RC1 is 2.3 am I safe???
Click to expand...
Click to collapse
Well, seeing as the article says that the vulnerability only applies to pre-gingerbread roms, yes. You are safe.
wdfowty said:
Well, seeing as the article says that the vulnerability only applies to pre-gingerbread roms, yes. You are safe.
Click to expand...
Click to collapse
Google pushed out an market update with the mal-ware plug a couple of days after the problem showed up. i forgot where i read the article and if i find it i will post.
the apps that had the back door sniffer built in were reversed engineered and the made the patch according to there findings.
synisterwolf said:
Google pushed out an market update with the mal-ware plug a couple of days after the problem showed up. i forgot where i read the article and if i find it i will post.
the apps that had the back door sniffer built in were reversed engineered and the made the patch according to there findings.
Click to expand...
Click to collapse
I think it's one of the articles linked in the original thread qoute.
wdfowty said:
I think it's one of the articles linked in the original thread qoute.
Click to expand...
Click to collapse
lol. yeah your right. i should have checked the op before speaking.
Lol it's all good
Kinda unclear? Ifi have cm7(2.3) and installed one of those apps am i good?
sent from dinc
Rom-Addict said:
Kinda unclear? Ifi have cm7(2.3) and installed one of those apps am i good?
sent from dinc
Click to expand...
Click to collapse
As they said, the problem is for any software version below Gingerbread. And since you're running GB (2.3), you don't have to worry about it. You're safe.
Sent from my Droid Incredible running Myn's Warm TwoPointTwo RLS5.3.
changed the title to ease the confusion...
that sucked, that spider man game was actually kinda cool ;P
Zerox8610 said:
that sucked, that spider man game was actually kinda cool ;P
Click to expand...
Click to collapse
I believe it was a developer that kanged an app, and smali'd in some malicious code. Just use gingerbread or a rom with a dummy /system/bin/profile
Having virtual buttons has been excellent, both for a sensible button layout and because it puts the three-dot overflow menu into a consistent, intelligent location. I know you can get it on AOSP-based ROMs, but I'd be curious to try it with one of the Google Edition variants. Is there one which supports the virtual buttons?
Have you tried adding qemu.hw.mainkeys = 0 to your build.prop? I'm not sure if it'll work, but it's worth a try.
wtfismdna said:
Have you tried adding qemu.hw.mainkeys = 0 to your build.prop? I'm not sure if it'll work, but it's worth a try.
Click to expand...
Click to collapse
I'm actually such a noob that I don't even know what the build.prop is...
If you go to /system/, there's a file called build.prop. If you open the file, you can add "qemu.hw.mainkeys=0" to the end, which should enable software keys. I'm not sure if it'll work on Sense/GE ROMs, but there's no harm in trying. Just make a backup before you do any editing!
Sent from my HTC One using Tapatalk 4 Beta
To my super limited background, that looks like it should just disable hardware keys, but I'll give it a shot. Thanks!
Also if anyone knows of a GE ROM with such an option built in, I'd appreciate it.
Sent from my One using Tapatalk 2
wtfismdna said:
If you go to /system/app, there's a file called build.prop. If you open the file, you can add "qemu.hw.mainkeys=0" to the end, which should enable software keys. I'm not sure if it'll work on Sense/GE ROMs, but there's no harm in trying. Just make a backup before you do any editing!
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Build prop is usually in /system.
Sent from my HTC One
Simba501 said:
Build prop is usually in /system.
Sent from my HTC One
Click to expand...
Click to collapse
Yeah, that's what I meant to say, unfortunately not what I typed.
Fixed now.
Were you ever able to get it to work? I did try adding that command to the stock touchwiz on my GS4, but it never worked. GUI froze and restarted all the time. Having the nexus virtual buttons on the GE HTC & GE GS4 roms would be excellent. Please help anyone! =)
Whach said:
Were you ever able to get it to work? I did try adding that command to the stock touchwiz on my GS4, but it never worked. GUI froze and restarted all the time. Having the nexus virtual buttons on the GE GS4 rom would be excellent. Please help anyone! =)
Click to expand...
Click to collapse
Why are you asking here ... You might want to ask in a Samsung thread because I can't see why you'd ask in a HTC Forum
AllAboutTheCore said:
Why are you asking here ... You might want to ask in a Samsung thread because I can't see why you'd ask in a HTC Forum
Click to expand...
Click to collapse
Thought it was pertinent to any GE Edition Rom - HTC, Samsung, whatever. I'd assume enabling software keys would not be device specific in a GE ROM? (well, at least I hope it is) Just saying......
Whach said:
Thought it was pertinent to any GE Edition Rom - HTC, Samsung, whatever. I'd assume enabling software keys would not be device specific in a GE ROM? (well, at least I hope it is) Just saying......
Click to expand...
Click to collapse
If that's the case then why bother having device specific forums? May aswell just have one forum where people post anything ... If I wanted to ask a question about the HTC One, I wouldn't be asking it in the Samsung section, what's the point?
AllAboutTheCore said:
If that's the case then why bother having device specific forums? May as well just have one forum where people post anything ... If I wanted to ask a question about the HTC One, I wouldn't be asking it in the Samsung section, what's the point?
Click to expand...
Click to collapse
The point being the question was more about enabling the virtual keys in relation to the GE software only. The thread title & discussion was more relevant.
I've now been able to get the virtual keys for both GE edition phones working using the same build.prop command. The command applied to both devices since it concerned the software rather than the hardware....... whether I posted here or in the Samsung forum (which I did) didn't really make a difference did it?......the outcome was the same.
Of course posting in a device specific section is best when the discussion is about the specific hardware, that's obvious. This thread could have easily been located in the Android Dev and Hacking section, but it wasn't and so I just made do with it.
Hope that is a satisfactory enough explanation for this storm in a teacup....if not, have an apology for your appeasement
Hi All,
What i would like to know when this image arrives is if it still enables device encryption by default.
Cheers,
Adrian
Cleaned the thread, changed the title and moved to Q&A.
Draco32 said:
Hi All,
What i would like to know when this image arrives is if it still enables device encryption by default.
Cheers,
Adrian
Click to expand...
Click to collapse
im 99.999999999999999999999999999% sure that google will never change that on the nexus 6
simms22 said:
im 99.999999999999999999999999999% sure that google will never change that on the nexus 6
Click to expand...
Click to collapse
They have changed their terms and conditions recently to reflect that partners don't have to do this so it would be very interesting if they removed it to increase performance.
Draco32 said:
They have changed their terms and conditions recently to reflect that partners don't have to do this so it would be very interesting if they removed it to increase performance.
Click to expand...
Click to collapse
partners is a whole different story, they arent nexus.
It's going to be encrypted.
OEMs get to choose if they want the device encrypted or not.
Knowing samsung, I think they'll want encryption out of the box soon enough.
Not sure about the rest.
The changelog States that 5.1 adds hardware based encryption to nexus 6 which may improve performance.
crowbarman said:
The changelog States that 5.1 adds hardware based encryption to nexus 6 which may improve performance.
Click to expand...
Click to collapse
I haven't dug into source but it appears it's not actually activated. The flag is set to false.
Sent from my Nexus 6 using XDA Free mobile app
akellar said:
I haven't dug into source but it appears it's not actually activated. The flag is set to false.
Click to expand...
Click to collapse
Look in BoardConfig.mk for it.
What they've done to the device tree actually proves that it is their short term objective to throw the switch and enable hwcrypto, which you should take to 100% mean that they will NOT be removing the requirement for crypto.
doitright said:
Look in BoardConfig.mk for it.
What they've done to the device tree actually proves that it is their short term objective to throw the switch and enable hwcrypto, which you should take to 100% mean that they will NOT be removing the requirement for crypto.
Click to expand...
Click to collapse
...and should hopefully provide a much better performance encryption
Hi all,
So I was testing the GN5 and came across a built-in permission manager first thing. Didn't think much of it I mean yes it's a very nice feature and all but then after I had to return the phone, I looked for other references to it online but couldn't find any. It's not available on the Galaxy A8 that's for sure.
So I'm just looking for confirmation that it does indeed exist on every other GN5 out there..
yellowchilli said:
Hi all,
So I was testing the GN5 and came across a built-in permission manager first thing. Didn't think much of it I mean yes it's a very nice feature and all but then after I had to return the phone, I looked for other references to it online but couldn't find any. It's not available on the Galaxy A8 that's for sure.
So I'm just looking for confirmation that it does indeed exist on every other GN5 out there..
Click to expand...
Click to collapse
i can't find it on my note5 N920I so if you could describe how to access it that would be nice
imfaraz said:
i can't find it on my note5 N920I so if you could describe how to access it that would be nice
Click to expand...
Click to collapse
Should've noted that down... but it pops up by itself either before or after download. Didn't need to set anything before hand. Will see if I can dig up the rom info too... it was a test unit for HK
Thanks
yellowchilli said:
Hi all,
So I was testing the GN5 and came across a built-in permission manager first thing. Didn't think much of it I mean yes it's a very nice feature and all but then after I had to return the phone, I looked for other references to it online but couldn't find any. It's not available on the Galaxy A8 that's for sure.
So I'm just looking for confirmation that it does indeed exist on every other GN5 out there..
Click to expand...
Click to collapse
That's the only reason I miss aosp or root for. How do you get that? Is it third party app or what? Seems like test build samsung has around for android M update coming soon to note 5.
Sent from my SAMSUNG-SM-N920A
Does the phone runs on android 6.0 by any chance?
Sent from my SM-N920C using Tapatalk
He probably came across a test phone of some sort - with Android 6.0
Android definitely needs something like this...
I hate downloading apps that need random permissions for things (Like a photo editor that needs to read my SMS messages) - It creeps me out and is just weird. I'm sure some permissions are innocent and others are malicious.
This feature will definitely help Android!
fail..... of all the screenshots I took I forgot to take one of the build info. is there anywhere on google that might store that? I already checked Play store.. that only remembers my model number.
on my GN5 it was built in. I was setting it up from scratch, installing new apps etc.
HNIC215 said:
He probably came across a test phone of some sort - with Android 6.0
Android definitely needs something like this...
I hate downloading apps that need random permissions for things (Like a photo editor that needs to read my SMS messages) - It creeps me out and is just weird. I'm sure some permissions are innocent and others are malicious.
This feature will definitely help Android!
Click to expand...
Click to collapse
yup I was surprised to see it. I'll see if I can clarify with my PR contact...
I've got Android M on my Nexus 6 and that was pretty buggy. Samsung would've needed a miracle to put their touchwiz on it and maintain such stability at this time so that's highly unlikely.
I am pretty sure that ROM wasn't a 6.0 test rom, but just something Samsung cooked into the Chinese (and HK) ROM... already seen it in some Chinese N9200 before... Could be something unique to said variant, or could be something that can be triggered by change of build file...
alexcarterkarsus said:
I am pretty sure that ROM wasn't a 6.0 test rom, but just something Samsung cooked into the Chinese (and HK) ROM... already seen it in some Chinese N9200 before... Could be something unique to said variant, or could be something that can be triggered by change of build file...
Click to expand...
Click to collapse
Well lg g4 had it cooked un and you could access it by creating widget of activities and sellecting permissions settings but I am not able to find it on this phone
Sent from my SAMSUNG-SM-N920A
this function exist in Note 5 Hong Kong version... it will pop out everytime when you install an app.
thank you for clarifying this!
prodigiez said:
this function exist in Note 5 Hong Kong version... it will pop out everytime when you install an app.
Click to expand...
Click to collapse
Can't wait to get that feature!
Flash Ditto Rom for N5, you will have this feature without Hongkong CSC
Zanr Zij said:
Flash Ditto Rom for N5, you will have this feature without Hongkong CSC
Click to expand...
Click to collapse
No root for my Note 5 lol
Is this apk just for the Pixel phone?
https://www.apkmirror.com/apk/googl...-017-253834016-android-apk-download/#variants
jd14771 said:
I just downloaded the gcam for the snapdragon variant.
In the future, the gcam port is dependenant on the phone it's intended for, otherwise you need to adjust the settings manually.id highly suggest not touching ANY settings in the camera app that are in the " settings" menu. You can change the camera modes and stuff but don't touch the settings menu.
As for whitch version to download, any gcam that is in red and Bold is a stable working non beta version.
All snapdragon gcam releases
Latest stable gcam direct download link
Click to expand...
Click to collapse
OK, but does that apk work for the snapdragon version of the Note 9.
Kamau54 said:
Is this apk just for the Pixel phone?
https://www.apkmirror.com/apk/googl...-017-253834016-android-apk-download/#variants
Click to expand...
Click to collapse
yes cause its stock.
dont use it.
u need a port.
please read previous messages.
jd14771 said:
Wot m8, did you even read what I put?
Click to expand...
Click to collapse
Yes I did. You told me what you did, what I should do, gave me a couple links to sites...but you never answered the question. Yes or No would have been sufficient since I know all the other stuff already. I just wanted to know if that link was just for the Pixel, since the article didn't make that clear.
BTW, I have changed many of the settings (as suggested when they came out) in earlier versions to get them to work.
Thanks anyway.
So can anyone point me to the correct gcam for my Note 9 Snapdragon? I assume the latest and greatest Google cam port is pretty much install and use as is? I'm seeing several in Red and bold.. Haven't been keeping up lately. Thanks
Sent from my SM-N960U using Tapatalk
schlepprock01 said:
So can anyone point me to the correct gcam for my Note 9 Snapdragon? I assume the latest and greatest Google cam port is pretty much install and use as is? I'm seeing several in Red and bold.. Haven't been keeping up lately. Thanks
Click to expand...
Click to collapse
i swear i saw an other post than this one dedicated for the SD ..maybe search a bit
bober10113 said:
i swear i saw an other post than this one dedicated for the SD ..maybe search a bit
Click to expand...
Click to collapse
And these are the kind of pics it produces (just took this a minute ago).
Everyone says you make no adjustments to the settings, yet unless I'm living on Venus, green pics are not what I want.
Kamau54 said:
And these are the kind of pics it produces (just took this a minute ago).
Everyone says you make no adjustments to the settings, yet unless I'm living on Venus, green pics are not what I want.
Click to expand...
Click to collapse
well u have to load a .xml profile...at least in the exynos version.
bober10113 said:
well u have to load a .xml profile...at least in the exynos version.
Click to expand...
Click to collapse
I have snapdragon.
Kamau54 said:
I have snapdragon.
Click to expand...
Click to collapse
that may be but i wonder if the gcam port for SD devices has a hidden load config file menu for .xml profiles like the exynos gcam port has.
i guess only you may be able to check it out.
swipe to the "more" section and tap the black area below...
bober10113 said:
that may be but i wonder if the gcam port for SD devices has a hidden load config file menu for .xml profiles like the exynos gcam port has.
i guess only you may be able to check it out.
swipe to the "more" section and tap the black area below...
Click to expand...
Click to collapse
Nothing happened or appeared, and pictures are the same green tinted.
jd14771 said:
I have a snapdragon, and the gcam port I listed works perfect on my device. Not sure why it's giving the usual green tint problems with k. The one I linked to has the settings baked into it so it's load and go.
Click to expand...
Click to collapse
Yes, the one you linked works perfectly on my SD Note 9.
Sent from my SM-N960U using Tapatalk