Database Users

CUSPTECH Android Headunit

Hi All
I thought I'd open up an new Thread regarding the Cusptech Android head units that are very similar to the S150 units but fundamentally different.
Specs:
http://www.cusptech.com/index.php?c=products2
Here is the link to download firmware for the units.
Official Firmware
http://www.cusptech.com/index.php?c=service&cid=9588d0aa6aefd7aec5f77fd497fe9825
Unofficial Android 4 Firmware.
https://drive.google.com/file/d/0B0MRJU3tnyDrdmpkYlB1VlZ3STQ
Please let me know if you want any more added about this unit

Well, I'm a little bit sad that this unit doesn't have a unique CPU like the others. That was really the easiest differentiator. I guess we'll need more information about this one in comparison with the S150 to make it easy to differentiate between the two.
Do you actually have this unit? Because if you do, I'd like for you to run a few apps to verify specifications and make it easier to create a dedicate wiki page for it.

donaldta said:
Well, I'm a little bit sad that this unit doesn't have a unique CPU like the others. That was really the easiest differentiator. I guess we'll need more information about this one in comparison with the S150 to make it easy to differentiate between the two.
Do you actually have this unit? Because if you do, I'd like for you to run a few apps to verify specifications and make it easier to create a dedicate wiki page for it.
Click to expand...
Click to collapse
Yes I do, which apps you want me to run?

donaldta said:
Well, I'm a little bit sad that this unit doesn't have a unique CPU like the others. That was really the easiest differentiator. I guess we'll need more information about this one in comparison with the S150 to make it easy to differentiate between the two.
Do you actually have this unit? Because if you do, I'd like for you to run a few apps to verify specifications and make it easier to create a dedicate wiki page for it.
Click to expand...
Click to collapse
This is my unit. http://www.cusptech.com/index.php?c=products&t=v&vid=bef7cb4be15327cd8a090aa2c4bb74c5

ryrager said:
Yes I do, which apps you want me to run?
Click to expand...
Click to collapse
Please install Android System Info. Click on the "System" tab, click on the application (overflow) menu and export results to file. Go through it, its a simple html file in /mnt/sdcard directory and censor any information that want to hide like accounts names and SSID then upload it as an attachment.
Also, if you can install CPU / RAM / DEVICE Identifier and check the CPU discovered. If it is unspecific or seems misidentified the please sent the report back to Davy Bartoloni. He's very good at identifying the exact processor and can usually give you feedback within 48 hours. A screenshot would also be nice.

donaldta said:
Please install Android System Info. Click on the "System" tab, click on the application (overflow) menu and export results to file. Go through it, its a simple html file in /mnt/sdcard directory and censor any information that want to hide like accounts names and SSID then upload it as an attachment.
Also, if you can install CPU / RAM / DEVICE Identifier and check the CPU discovered. If it is unspecific or seems misidentified the please sent the report back to Davy Bartoloni. He's very good at identifying the exact processor and can usually give you feedback within 48 hours. A screenshot would also be nice.
Click to expand...
Click to collapse
Sorry how do I get to the overflow menu?

donaldta said:
Please install Android System Info. Click on the "System" tab, click on the application (overflow) menu and export results to file. Go through it, its a simple html file in /mnt/sdcard directory and censor any information that want to hide like accounts names and SSID then upload it as an attachment.
Also, if you can install CPU / RAM / DEVICE Identifier and check the CPU discovered. If it is unspecific or seems misidentified the please sent the report back to Davy Bartoloni. He's very good at identifying the exact processor and can usually give you feedback within 48 hours. A screenshot would also be nice.
Click to expand...
Click to collapse
I installed a virtual button app.. and found the overflow menu.... however I cannot see the html file that it creates in that folder.... so I am at a loss. It says it saved the file but I am unable to find it. Thoughts?

ryrager said:
I installed a virtual button app.. and found the overflow menu.... however I cannot see the html file that it creates in that folder.... so I am at a loss. It says it saved the file but I am unable to find it. Thoughts?
Click to expand...
Click to collapse
Excellent. I was trying to figure out how you're supposed to be able to trigger it with an app. But, all the ones I found required root and I wasn't sure if you had this access yet.
Anyways, the default file location is the /mnt/sdcard/AndroidSystemInfo directory. The nomencalture of the file should be something like "asi-system-infos-{year#}-{mo#da#}-{pid#}.html"
As for the CPU / RAM / DEVICE Identifier, I noticed that it required detection to be improved. Can you please hit the evaluate button and once it is over there should be a "Send Info" button. This will use your email client to attach a report to the developer, Davy Bartoloni. He'll be able to determine the correct information specific to your unit with 48 hours.

ryrager said:
I installed a virtual button app.. and found the overflow menu.... however I cannot see the html file that it creates in that folder.... so I am at a loss. It says it saved the file but I am unable to find it. Thoughts?
Click to expand...
Click to collapse
I haven't seen anything from you in a few days. Were you able to find the file or get confirmation from the Davy?

donaldta said:
I haven't seen anything from you in a few days. Were you able to find the file or get confirmation from the Davy?
Click to expand...
Click to collapse
I just rolled back to 2.3.4 to try use those apps because for some reason I couldn't see anywhere where the files were written. so couldn't upload the html file

ryrager said:
I just rolled back to 2.3.4 to try use those apps because for some reason I couldn't see anywhere where the files were written. so couldn't upload the html file
Click to expand...
Click to collapse
I wish you would have been more vocal. I could have given you a command to use to find the file with a terminal app, like Terminal Emulator.
Code:
$ [COLOR="RoyalBlue"][B]find /mnt -name asi*[/B][/COLOR]
find: /mnt/secure: Permission denied
find: /mnt/sdcard-ext: Permission denied
/mnt/sdcard/AndroidSystemInfo/asi_system_infos-20140210-154124.html
$
As you see above, I use the find "find" command to search for any file or directory name that starts with "asi" from all the subdirectories of /mnt. Because of its id, it cannot traverse through secure or sdcard-ext but it still found the exact path and filename. If you have root access you bypass the permission problems of any subdirectory.
Code:
$ [COLOR="RoyalBlue"][B]su[/B][/COLOR]
# [COLOR="RoyalBlue"][B]find /mnt -name asi*[/B][/COLOR]
/mnt/sdcard/AndroidSystemInfo/asi_system_infos-20140210-154124.html
#

donaldta said:
I wish you would have been more vocal. I could have given you a command to use to find the file with a terminal app, like Terminal Emulator.
Code:
$ [COLOR="RoyalBlue"][B]find /mnt -name asi*[/B][/COLOR]
find: /mnt/secure: Permission denied
find: /mnt/sdcard-ext: Permission denied
/mnt/sdcard/AndroidSystemInfo/asi_system_infos-20140210-154124.html
$
As you see above, I use the find "find" command to search for any file or directory name that starts with "asi" from all the subdirectories of /mnt. Because of its id, it cannot traverse through secure or sdcard-ext but it still found the exact path and filename. If you have root access you bypass the permission problems of any subdirectory.
Code:
$ [COLOR="RoyalBlue"][B]su[/B][/COLOR]
# [COLOR="RoyalBlue"][B]find /mnt -name asi*[/B][/COLOR]
/mnt/sdcard/AndroidSystemInfo/asi_system_infos-20140210-154124.html
#
Click to expand...
Click to collapse
Yes AndroidSystemInfo folder gets created ... just no content is placed inside it.

ryrager said:
Yes AndroidSystemInfo folder gets created ... just no content is placed inside it.
Click to expand...
Click to collapse
Can you maybe try it again but use the terminal emulator to find the file? Maybe show me the output of "ls -l -d /mnt/sdcard/AndroidSystemInfo/" and "ls -l /mnt/sdcard/AndroidSystemInfo/" commands? Btw, do you have root access on this device? Sometimes you cannot see the file because of the app's ID is different from the one that you are using to locate it.

Cusp
Hi all,
finally a thread for the Cusptech Navigation devices, YAY
I own one that i purchased mid last year. Unfortunately I must say it is really buggy. I would love to get CN MOD on them instead of stock "garbage".
As I am a little bit techy, I already gathered some Infos about the Navi:
The devices are based on Mainboards created by cusptech and sntron (sntron.com). The Mainboard incorporates different Modules/Interfaces for Bluetooth, FM-Radio, DVB-T Television and DVD. The Modules are controlled through Android Apps (SNT-FM, SNT-BT and so on). There is a main hardware audioswitch on the Mainboard that switches the sound between the different Interfaces(from BT to FM to Android Media...). Unfortunately the Output levels are not all equal. For example in my case, the BT and FM-Radio is way louder than Android Media. I already tried to access the Volume Control through Tasker, sadly Tasker has only control of the Android Media Sound. The BT-Module is not as usually found on android devices, it is fully controlled by the SNT Software and is not accessible through android itself in the settings nor can one send files through it for example. The sound quality of the BT-Interface is not really good and the Software itself is buggy and often crashes. I don't use it anymore.
I will install Android System Info and if i can find the files I put them here. Btw. I am using 2.3.4 because android 4 is still in early beta. As I know the device is rooted, at least that's what Root-Checker tells me. Although sometimes, some apps are complaining about missing root rights, like Tasker. I don't know why.

tobias.s said:
I will install Android System Info and if i can find the files I put them here.
Click to expand...
Click to collapse
Thanks, I appreciate it.
tobias.s said:
Btw. I am using 2.3.4 because android 4 is still in early beta. As I know the device is rooted, at least that's what Root-Checker tells me. Although sometimes, some apps are complaining about missing root rights, like Tasker. I don't know why.
Click to expand...
Click to collapse
Well, if you can install a terminal app; like Terminal Emulator, then type "su" and the command prompt changes from "$" to "#" then you have root.
As for your other programs telling you that it cannot access root, that is usually with a problem with mismatched_uid symlinks in the app's /data/data/{package.name}/* directories. The symptom is often caused by an incomplete update where package manager saw a uid mismatch in the settings and file system. So, you may see symlink references like the following.
Code:
lib -> /mismatched_uid/settings_10037/fs_1000
The above is showing that PM has found a user id mismatch from the settings "10037" with the apps user files "1000". However, since the /mismatched_uid/settings_10037/fs_1000 directory path doesn't actually exist the app isn't able to use its files. If you have busybox AND a terminal app installed. You can run the following command to see if this is the case with any of the currently installed apps.
Code:
$ [B][COLOR="RoyalBlue"]su[/COLOR][/B]
# [COLOR="RoyalBlue"][B]find /data/data -type l -exec busybox ls -l {} \; | grep mismatch[/B][/COLOR]
The above command uses find to search through all the apps symlinks and uses long listing to show you their links. Grep is used to filter out for the word "mismatch" to make the list smaller. If the command shows nothing at all then try removing the " | grep mismatch" to get the full output. The fix is pretty easy. Uninstall the program make sure its directory in /data/data/{package.name} is gone then reinstall.

Wow thank you for the Input. Will try it tomorrow and keep you informed.
Today my Tasker crashed after using Google Maps. Unfortunately Maps is not quit stable on the device. Seems that Android is trying to close Tasker and ban it from the status bar. Even with correct Configuration in Tasker. Must check this because I created a Profile which controls the Backlight of the unit based on Sunset/Sunrise and location. Anyway.
Attached is the file that I found in /sdcard/AndroidSystemInfo/ . Just black labled the IMEI and MAC.

tobias.s said:
Attached is the file that I found in /sdcard/AndroidSystemInfo/ . Just black labled the IMEI and MAC.
Click to expand...
Click to collapse
Excellent. But, you might have to post it on a file sharing host; like Dropbox, Skydrive or Google Drive. I think you need to have at least 10 posts before you can post attachments and linkable URLs. You can get around the URL parser by just surrounding the URL with underscores; like _https://www.dropbox.com/s/8suzxlgcdv640n8/old.google.maps.apk_ which will allow you to post an non-clickable link that can be copy & pasted into the URL bar of a browser.
(or you can copy and paste the context of the file into a post)

Is the attachment now viewable? I reattached it to the post. If not, I would upload it elsewhere.

tobias.s said:
Is the attachment now viewable? I reattached it to the post. If not, I would upload it elsewhere.
Click to expand...
Click to collapse
Yes, it is. Thank you very much.

donaldta said:
Yes, it is. Thank you very much.
Click to expand...
Click to collapse
Beat me to it...Thanks Tobia.s. I just got latest firmware from Lucy at Cusptech ... think its the same as the one that leaked earlier 20131125

debugging issue on Huawei Ascend P6

Hi there, hope I'm asking in the right forum. I'm desperately looking for a solution for about a week now.
The problem: whenever I debug any app on my new Ascend P6 (build B607), I see an annoying LogCat message marked as WARN and tagged with my package:
Code:
java.io.FileNotFoundException: /data/cust/xml/hw_launcher_load_icon.xml: open failed: ENOENT (No such file or directory)
This thing is somehow preventing any other logs from my app from being shown, so I'm just developing blind, since this crap is the only thing I see in the log after debugging any of my apps. What I've tried: rooting the device, using the adb shell to create this file but of course I don't know what should be inside, so now it's pretty much the same, though the XmlPullParser fails this time (sure, 'cause the file is empty). I've been searching all round the Internet, even on some Chinese forums, and I found many people describing the same situation but there never was a solution. Any ideas how to fix that?

the logcat part sorry no expertise in that Context
But for XML part try using a SAX parser like in Xeres the XML parser from Apache
Sent from my GT-S5302 using Tapatalk 2

sak-venom1997 said:
the logcat part sorry no expertise in that Context
But for XML part try using a SAX parser like in Xeres the XML parser from Apache
Sent from my GT-S5302 using Tapatalk 2
Click to expand...
Click to collapse
I guess you have misunderstood me The file the system is trying to parse has nothing to do with my projects, it's located in /data directory and normally u can't even access it.
To clarify: this is a system file for some reason not included in my stock firmware. Using root access and adb shell, I created this file in the mentioned directory, but of course it's empty. Thinking about contacting huawei support and asking them to provide me with this file I haven't even found anything where you can write to them ><

chmod in a Root Shell Fails On A File in /data/data

I hope I am getting this is the right place. If not, please respond with a suggestion of where to place it. Thanks!
First some background. I have written a root app that, to accomplish its work, must chmod some files located under /data/data. This app works as expected on my 3 test devices - all JB or KK and has been published to Play Store where comments from users indicate that it works on other devices including those with Android 5 and 6.
The other day, a user contacts me and says the app doesn't work on his device. Here is some of the device info my app captures:
Linux Version: 3.10.40-perf-g90ddf4a
Android SDK Version: 22
Maker: motorola
Brand: motorola
Product: quark_verizon
Device: quark
Model: XT1254​
My app confirms that the device is indeed rooted and that there is a recent SuperSu app installed. My app is able to chmod directories and some other files. But it cannot manage certain others. I get a result code of 10 but am not sure what exactly that means except some form of failure.
I should add that trying to change the permissions on the file using Root explorer also seems to fail (silently) since right after doing so, the user ran my app and its log shows the file's permissions unchanged.
I wondered if it was an SeLinux issue - something about the files' contexts - but having my app perform ls -Z shows that the contexts (other than the user id - as expected) are identical to those on my 3 devices. Plus there are no context violation warnings in dmesg as I understand there should be were SeLinux the issue.
I have read about extended file attributes and there is one for marking a file immutable. I don't know if this would case a chmod to fail but maybe. I doubt this is the case with these files since I know they are being changed by the file's owning app. But there is no way to confirm this unless the user installs busybox which contains the lsattr command. And he isn't keen on doing that.
Can anyone suggest what might be causing this problem and why it might be restricted to this particular device? I am just completely stumped.
Thanks

Kiw l21 middle eastern MM released...

The official huawei page of our region has stated that it has released the MM update for kiw l21 and it should reach us in 2-3 working days...
There will be an OTA and a link on their website... I want to mirror the link on sites like mega etc for people who don't get the update right away.... But don't kniw how to, can someone please explain the procedure so middle eastern people don't have to wait any longer...
Sent from my KIW-L21 using Tapatalk

hi.can send me rom link?

Faheemarif252 said:
The official huawei page of our region has stated that it has released the MM update for kiw l21 and it should reach us in 2-3 working days...
There will be an OTA and a link on their website... I want to mirror the link on sites like mega etc for people who don't get the update right away.... But don't kniw how to, can someone please explain the procedure so middle eastern people don't have to wait any longer...
Sent from my KIW-L21 using Tapatalk
Click to expand...
Click to collapse
where is the link??? Please share with us

Faheemarif252
What is the web address of the official Huawei page thats states this ?
Please provide a link so that we can read this.
Thank you

If you read the original post correctly... Huawei said that the OTA will reach in 2-3 working days... That means monday or tuesday (at least where i live).... Some people have got the ota but i still haven't... And there is no update available till now on their website...
One of my friends recieved the update so i should be soon too.... I will mirror the OTA and share the link asap
Sent from my KIW-L21 using Tapatalk

It should be in XDA's Honor's 5x repository

Faheemarif252 said:
The official huawei page of our region has stated that it has released the MM update for kiw l21 and it should reach us in 2-3 working days...
There will be an OTA and a link on their website... I want to mirror the link on sites like mega etc for people who don't get the update right away.... But don't kniw how to, can someone please explain the procedure so middle eastern people don't have to wait any longer...
Sent from my KIW-L21 using Tapatalk
Click to expand...
Click to collapse
I simply use the logcat feature of android to get the URL of an OTA update
Open a command prompt and use these two commands to clear the log and then dump the log to your PC and simply look (search) for any http:// in the log
I simply use.
adb logcat -c
followed by
adb logcat -d > logcat.txt
to learn more read below
1. When you get prompted to download an update on your Android device, immediately plug your phone into a computer.
2. From that computer, open a command prompt, type “adb logcat” and hit enter. (On a Mac it’s “./adb logcat”)
3. The command prompt will then begin to spit out information from your phone.
4. Feel free to then tap the “Download” button on the update from your phone.
5. Once the download starts, you will be able to find the URL of the file that is downloading in the logcat.
6. You can do a handful of things now to find it-
Click to expand...
Click to collapse
To better use the "adb logcat" command, we need to look at its options:
"adb logcat -b <buffer>" - Loads an alternate log buffer for viewing, such as event or radio. The main buffer is used by default. There are log buffers on the Android system: "main", "events", and "radio". The default buffer is "main".
"adb logcat -c" - Clears (flushes) the entire log and exits.
"adb logcat -d" - Dumps the log to the screen and exits.
"adb logcat -f <filename>" - Writes log message output to a file. The default is the "stdout - Standard Output".
"adb logcat -g" - Prints the size of the specified log buffer and exits.
"adb logcat -n <count>" - Sets the maximum number of rotated logs to <count>. The default value is 4. Requires the -r option.
"adb logcat -r <kbytes>" - Rotates the log file every <kbytes> of output. The default value is 16. Requires the -f option.
"adb logcat -s" - Sets the default filter spec to silent.
"adb logcat -v <format>" - Sets the output format for log messages. The default is brief format.
Click to expand...
Click to collapse

clsA said:
I simply use the logcat feature of android to get the URL of an OTA update
Open a command prompt and use these two commands to clear the log and then dump the log to your PC and simply look (search) for any http:// in the log
I simply use.
adb logcat -c
followed by
adb logcat -d > logcat.txt
to learn more read below
1. When you get prompted to download an update on your Android device, immediately plug your phone into a computer.
2. From that computer, open a command prompt, type â??adb logcatâ? and hit enter. (On a Mac itâ??s â??./adb logcatâ?)
3. The command prompt will then begin to spit out information from your phone.
4. Feel free to then tap the â??Downloadâ? button on the update from your phone.
5. Once the download starts, you will be able to find the URL of the file that is downloading in the logcat.
6. You can do a handful of things now to find it-
To better use the "adb logcat" command, we need to look at its options:
"adb logcat -b <buffer>" - Loads an alternate log buffer for viewing, such as event or radio. The main buffer is used by default. There are log buffers on the Android system: "main", "events", and "radio". The default buffer is "main".
"adb logcat -c" - Clears (flushes) the entire log and exits.
"adb logcat -d" - Dumps the log to the screen and exits.
"adb logcat -f <filename>" - Writes log message output to a file. The default is the "stdout - Standard Output".
"adb logcat -g" - Prints the size of the specified log buffer and exits.
"adb logcat -n <count>" - Sets the maximum number of rotated logs to <count>. The default value is 4. Requires the -r option.
"adb logcat -r <kbytes>" - Rotates the log file every <kbytes> of output. The default value is 16. Requires the -f option.
"adb logcat -s" - Sets the default filter spec to silent.
"adb logcat -v <format>" - Sets the output format for log messages. The default is brief format.
Click to expand...
Click to collapse
Nice trick, thanks

clsA said:
I simply use the logcat feature of android to get the URL of an OTA update
Open a command prompt and use these two commands to clear the log and then dump the log to your PC and simply look (search) for any http:// in the log
I simply use.
adb logcat -c
followed by
adb logcat -d > logcat.txt
to learn more read below
Click to expand...
Click to collapse
Thnx a lot bro... I'll try the same as soon as i get the ota...
Sent from my KIW-L21 using Tapatalk

Faheemarif252 said:
Thnx a lot bro... I'll try the same as soon as i get the ota...
Sent from my KIW-L21 using Tapatalk
Click to expand...
Click to collapse
yep no problem another tip the file is normally named update.zip
and can be found in internal storage HwOUC folder with a folder inside with 5 digit number containing update.zip file

Nahid s said:
where is the link??? Please share with us
Click to expand...
Click to collapse
mammadpsy said:
hi.can send me rom link?
Click to expand...
Click to collapse
Tasha T said:
Faheemarif252
What is the web address of the official Huawei page thats states this ?
Please provide a link so that we can read this.
Thank you
Click to expand...
Click to collapse
Hey guys, Here is the link for Official MM update for ME - http://download-c.huawei.com/download/downloadCenter?downloadId=90103&version=351925&siteCode=pk

vsriram92 said:
Hey guys, Here is the link for Official MM update for ME - http://download-c.huawei.com/download/downloadCenter?downloadId=90103&version=351925&siteCode=pk
Click to expand...
Click to collapse
i have a bug in my phone in this update
when i receive new notification ex.whatsapp not show whatsapp icon in statusbar
show me pic who send me a message in statusbar
plz help me this bug

Amr fego said:
i have a bug in my phone in this update
when i receive new notification ex.whatsapp not show whatsapp icon in statusbar
show me pic who send me a message in statusbar
plz help me this bug
Click to expand...
Click to collapse
It's due to EMUI I guess

PalakMi said:
It's due to EMUI I guess
Click to expand...
Click to collapse
how can i fix this bug !!!!
i tired to found solution

Amr fego said:
how can i fix this bug !!!!
i tired to found solution
Click to expand...
Click to collapse
Try uninstalling and reinstall whatsapp

PalakMi said:
Try uninstalling and reinstall whatsapp
Click to expand...
Click to collapse
this problem in all application in my phone after i install this update

Amr fego said:
this problem in all application in my phone after i install this update
Click to expand...
Click to collapse
It's because the update, just go with a custom ROM that's better

how i return to custom rom !?

Amr fego said:
how i return to custom rom !?
Click to expand...
Click to collapse
Just unlock bootloader, install TWRP recovery and install custom ROM of your choice

the page huawai to get code to unlockbootloader not opend get me error
any anthor way to install TWRP recovery without unlock bootloader

Stock fingerprint

Can a good Samaritan give me the device fingerprint of the P Smart (from a stock rom) (Located in the build.prop)
Thanks

Awsumist said:
Can a good Samaritan give me the device fingerprint of the P Smart (from a stock rom) (Located in the build.prop)
Thanks
Click to expand...
Click to collapse
HWFIG-H:/ # getprop ro.build.fingerprint
HUAWEI/FIG-LX1/HWFIG-H:8.0.0/HUAWEIFIG-LX1/148(C432):user/release-keys
Though build.prop in /system says:
ro.build.fingerprint=Huawei/generic_a15/generic_a15:8.0.0/OPR6.170623.010/jenkin07102055:user/test-keys
Edit: I upgraded with HuRu and have a Google Framework Magisk module running (in case this explains the differences?)
Feel free to explain, if you know something about this Thanks!
Stock 8.0.0.148 (C432), L31 board

callmeWhiskers said:
HWFIG-H:/ # getprop ro.build.fingerprint
HUAWEI/FIG-LX1/HWFIG-H:8.0.0/HUAWEIFIG-LX1/148(C432):user/release-keys
Though build.prop in /system says:
ro.build.fingerprint=Huawei/generic_a15/generic_a15:8.0.0/OPR6.170623.010/jenkin07102055:user/test-keys
Edit: I upgraded with HuRu and have a Google Framework Magisk module running (in case this explains the differences?)
Feel free to explain, if you know something about this Thanks!
Stock 8.0.0.148 (C432), L31 board
Click to expand...
Click to collapse
Just trying to get safetynet to pass on my P Smart on a GSI. I'll try to figure something out later this week but thanks for the help man!

Awsumist said:
Just trying to get safetynet to pass on my P Smart on a GSI. I'll try to figure something out later this week but thanks for the help man!
Click to expand...
Click to collapse
A while back (when for "whatever reason" SafetyNet failed (ctsProfile:false)), I successfully used "MagiskHide Props Config" with a P20Pro fingerprint (though it's 8.1, other HUAWEI fingerprints didn't work) to pass SafetyNet.
In case this helps
Oh, and please (if you know the answer) - share info about why my terminal output is different from build.prop regarding ro.build.fingerprint
Cheers!

callmeWhiskers said:
A while back (when for "whatever reason" SafetyNet failed (ctsProfile:false)), I successfully used "MagiskHide Props Config" with a P20Pro fingerprint (though it's 8.1, other HUAWEI fingerprints didn't work) to pass SafetyNet.
In case this helps
Oh, and please (if you know the answer) - share info about why my terminal output is different from build.prop regarding ro.build.fingerprint
Cheers!
Click to expand...
Click to collapse
I have no idea why the shell command is different. I always just thought it read the getprop commands directly from build.prop. Literally as I'm writing this response I found out that my getprop fingerprint output is the actual fingerprint of my device where as the one located in build.prop is just the generic one. Weird

Interesting... is your generic one exactly the same as mine?
I've asked this question in the "MagiskHide Props Config" thread. I'll report back.

callmeWhiskers said:
HWFIG-H:/ # getprop ro.build.fingerprint
HUAWEI/FIG-LX1/HWFIG-H:8.0.0/HUAWEIFIG-LX1/148(C432):user/release-keys
Though build.prop in /system says:
ro.build.fingerprint=Huawei/generic_a15/generic_a15:8.0.0/OPR6.170623.010/jenkin07102055:user/test-keys
Edit: I upgraded with HuRu and have a Google Framework Magisk module running (in case this explains the differences?)
Feel free to explain, if you know something about this Thanks!
Stock 8.0.0.148 (C432), L31 board
Click to expand...
Click to collapse
Stupid question but are you sure you ran getprop ro.build.fingerprint and not getprop ro.vendor.build.fingerprint because I just found out that that's the vendor fingerprint (which I still have the stock vendor image so I have a very similar one)

Awsumist said:
Stupid question but are you sure you ran getprop ro.build.fingerprint and not getprop ro.vendor.build.fingerprint because I just found out that that's the vendor fingerprint (which I still have the stock vendor image so I have a very similar one)
Click to expand...
Click to collapse
I triple checked (Termux, Terminal Emulator, ADB shell). Both commands (getprop ro.build.fingerprint & getprop ro.vendor.build.fingerprint) result in giving me the same output/fingerprint:
Code:
HWFIG-H:/ $ [B]getprop ro.build.fingerprint[/B]
HUAWEI/FIG-LX1/HWFIG-H:8.0.0/HUAWEIFIG-LX1/148(C432):user/release-keys
HWFIG-H:/ $ [B]getprop ro.vendor.build.fingerprint[/B]
HUAWEI/FIG-LX1/HWFIG-H:8.0.0/HUAWEIFIG-LX1/148(C432):user/release-keys
HWFIG-H:/ $
and in both build.prop (/system & /vendor) only the generic one is found. (under /vendor the generic one is displayed as ro.vendor.build.fingerprint & under /system the generic one is displayed as ro.build.fingerprint)
Which means, I have NOT a slight clue, where the getprop commands actually "looks" for the fingerprint.
PS: Since I did a Factory Reset after I altered my fingerprint per Magisk Module, I'm pretty sure that's "normal" though - but I'll ask this follow-up finding in the MagiskHide Props Config thread. Maybe they can shine a light on this. I wish I had access to a completely (never) "altered" EMUI device...

Ok, sorry - I completely lost interest in EVERYTHING related to smartphones/computers for at least a couple of months (it's truly embarrassing, how long it took me to do this (and I fully blame my current travel setup, because at home this takes just a couple of minutes)) *pinky swear*
I can finally confirm, my build.prop isn't altered in any way. It's "supposed" to be like mentioned before (apparently the getprop cmd gets it values from "somewhere" else). Exact cause/behaviour (vendor discrepancy)... I don't care anymore :victory:
Source:
I extracted the build.prop from stock system.img of a FullOTA-MF image and used diff cmd to compare them.
Click to expand...
Click to collapse
Good luck with everything you wan't to achieve!
Cheers

callmeWhiskers said:
Ok, sorry - I completely lost interest in EVERYTHING related to smartphones/computers for at least a couple of months (it's truly embarrassing, how long it took me to do this (and I fully blame my current travel setup, because at home this takes just a couple of minutes)) *pinky swear*
I can finally confirm, my build.prop isn't altered in any way. It's "supposed" to be like mentioned before (apparently the getprop cmd gets it values from "somewhere" else). Exact cause/behaviour (vendor discrepancy)... I don't care anymore :victory:
Source:
Good luck with everything you wan't to achieve!
Cheers
Click to expand...
Click to collapse
Thanks man. I got safetynet to pass with the p20 pro fingerprint as you advised me. Have a great day :good: