Develop Bugs

Handset security lock on an Orange SPV C550

I am involved in the forensic examination of mobile phones and computers in relation to law enforcement.
I have an Orange SPV C550 to examine that is handset security locked with a code that the owner will not disclose.
Has anyone any idea how to ascertain the code, or get around it so that an examination can take place of the handset.
If anyone has an idea how to 'dump' the flash memory then I would also be very grateful.
Thanks

hmm.. if it is just the password when you power on the device, you can clear it by restoring the device to factory state via hard reset (when the phone is off, push both softkeys and power button, and 0 when the question appears)
if you mean simlock or sth of the kind - such things are on viki and spv-developers. rom dump info is there as well

Thank you for you reply, it is the handset lock that I need to bypass as the SIM card is not PIN protected.
If I do a reset of the handset as suggested then I am going to delete data which somewhat defeats the object of the examination!
I am governed by legislation that states that I should not alter any data if at all possible, whilst I accept by bypassing the security code then some data will change but in the circumstances this can be justified.
I need a way of getting access to the data on this handset by bypassing the security code.
Can anyone point me in the direction of some hardware/software that I can use to pull out the raw data from the handset. If I can do this then apart from obtaining the data by reading the hex data I may even be able to ascertain the user defined handset code.

Bought new backplate, now NFC doesn't work

Hey all,
A few months back (I procrastinated finding a solution to this issue), NFC was not working because one of the locking tabs on the backplate had broken off, and the NFC contacts on the backplate and the phone weren't coming into contact (confirmed by pushing real hard in that spot, which allowed NFC to work). I ordered a new backplate, and it fits perfect. However, the NFC still does not work, even though the contacts are clearly making contact. I don't know exactly why it isn't working, hopefully someone here can help. I do have an idea as to why it isn't working, though.
When ordering the backplate, I opted for the International Note II's backplate because I don't particularly like the AT&T logo on the back. Could be that I require different drivers for the new NFC chip?
If anyone could help, I would greatly appreciate it! If I missed any information I'll be glad to provide it.

Basic antenna...
The version of software is phone dependent....not cover dependent ...
Is the cover an OEM product ???
If not...I've seen covers with an antenna that never worked...because it wasn't a real one....(fake copy)...
If the cover is confirmed to be authentic...you should look at the rom you are using and confirm that NFC is present and functioning...
If the software looks good...then a reset of the rom may be needed to activate the drivers on boot....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

I bought it from Samsung on Amazon, so yes it's official. I've flashed several ROM's since I got the new back, so that's a no-go. Also, I can put on the old back and push hard on the spot where the contacts are and NFC works. Do you think getting NFC files from an International ROM would work?

Update: decided to do a logcat
FROM BOOT:
E/NFC ( 2806): could not retrieve NFC service
E/NFC ( 2806): could not retrieve NFC service
E/NFC ( 2806): could not retrieve NFC service
I/NfcService( 3039): Starting NFC service
I/NFCJNI ( 3039): NFC Service: loading nxp JNI
I/NfceeAccess( 3039): read 3 signature(s) for NFCEE access
D/NfcService( 3039): NFC is on. Doing normal stuff
I/NfcService( 3039): Enabling NFC
D/NFCJNI ( 3039): Start Initialization
E/NFC-HCI ( 3039): Could not open /system/vendor/firmware/libpn544_fw.so
W/NFC ( 3039): Firmware image not available: this device might be running old NFC firmware!
D/NFCJNI ( 3039): NFC capabilities: HAL = 8150100, FW = b1011a, HW = 620003, Model = 11, HCI = 1, Full_FW = 1, Rev = 26, FW Update Info = 0
D/NFCJNI ( 3039): phLibNfc_SE_GetSecureElementList()
D/NFCJNI ( 3039):
D/NFCJNI ( 3039): > Number of Secure Element(s) : 1
D/NFCJNI ( 3039): phLibNfc_SE_GetSecureElementList(): SMX detected, handle=0xabcdef
D/NFCJNI ( 3039): phLibNfc_SE_SetMode() returned 0x000d[NFCSTATUS_PENDING]
I/NFCJNI ( 3039): NFC Initialized
D/NfcService( 3039): NFC-EE OFF
D/NfcService( 3039): NFC-C OFF
W/FeatureManager( 3729): isFeatureEnabled(NFC_HCE_PPMS) called before the first sync of ClientConfiguration.
D/NfcService( 3039): NFC-C ON
W/FeatureManager( 3729): isFeatureEnabled(NFC_HCE_PPMS) called before the first sync of ClientConfiguration.
D/NfcService( 3039): NFC-C OFF, disconnect
D/NfcService( 3039): NFC-C ON
TURNING OFF NFC
I/NfcService( 3039): Disabling NFC
W/FeatureManager( 5630): isFeatureEnabled(NFC_HCE_PPMS) called before the first sync of ClientConfiguration.
D/NFCJNI ( 3039): Terminating client thread...
D/NFCJNI ( 3039): phLibNfc_Mgt_UnConfigureDriver() returned 0x0000[NFCSTATUS_SUCCESS]
W/FeatureManager( 5630): isFeatureEnabled(NFC_HCE_PPMS) called before the first sync of ClientConfiguration.
TURNING ON NFC
I/NfcService( 3039): Enabling NFC
W/FeatureManager( 5630): isFeatureEnabled(NFC_HCE_PPMS) called before the first sync of ClientConfiguration.
D/NFCJNI ( 3039): Start Initialization
E/NFC-HCI ( 3039): Could not open /system/vendor/firmware/libpn544_fw.so
W/NFC ( 3039): Firmware image not available: this device might be running old NFC firmware!
D/NFCJNI ( 3039): NFC capabilities: HAL = 8150100, FW = b1011a, HW = 620003, Model = 11, HCI = 1, Full_FW = 1, Rev = 26, FW Update Info = 0
D/NFCJNI ( 3039): phLibNfc_SE_GetSecureElementList()
D/NFCJNI ( 3039):
D/NFCJNI ( 3039): > Number of Secure Element(s) : 1
D/NFCJNI ( 3039): phLibNfc_SE_GetSecureElementList(): SMX detected, handle=0xabcdef
D/NFCJNI ( 3039): phLibNfc_SE_SetMode() returned 0x000d[NFCSTATUS_PENDING]
I/NFCJNI ( 3039): NFC Initialized
W/FeatureManager( 5630): isFeatureEnabled(NFC_HCE_PPMS) called before the first sync of ClientConfiguration.
D/NfcService( 3039): NFC-EE OFF
D/NfcService( 3039): NFC-C ON

Drat333 said:
I bought it from Samsung on Amazon, so yes it's official. I've flashed several ROM's since I got the new back, so that's a no-go. Also, I can put on the old back and push hard on the spot where the contacts are and NFC works. Do you think getting NFC files from an International ROM would work?
Click to expand...
Click to collapse
I think that based on the above statement...you could try NFC Drivers from the international version...without much risk...
But I honestly don't think that the physical antenna changed between devices where different note 2 models were concerned...
Only the individual carrier specific files...
It's worth a shot...go for it....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

That's what I thought, and I've been searching around for the drivers with no luck. Any idea where I could get them?
And thanks for your help!

Drat333 said:
That's what I thought, and I've been searching around for the drivers with no luck. Any idea where I could get them?
And thanks for your help!
Click to expand...
Click to collapse
No...
I've searched for a reference. ..but there is little information on this. ...
I suggest that you pm one of our development people and see if they know where the files are located within the stock rom...
From there. ..The files could be pulled directly and placed into the system for testing. ..
I don't think a decompile would be needed. ..but I could be wrong. ..and the devs will have a more definitive answer. ...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

Drat333 said:
That's what I thought, and I've been searching around for the drivers with no luck. Any idea where I could get them?
And thanks for your help!
Click to expand...
Click to collapse
I really don't know if this will help, but I'm running a rom designed for the international version on my i317. The driver firmware identified in your logcat is libpn544_fw.so, which I pulled from my rom for you. You can try to push it, maybe, see if it works? If you need the entire contents of the fw folder, or any additional libs, I can probably pull those for you too, just let me know if you find out what you need. It should be compatible since the rom is for the international version and identifies my device as an international note 2. It shouldn't hurt to try.
See attached (not a flashable zip, just contains the fw.so!)

S7 Active expects US Knox Profile

Hello together,
we got our hands on 2 Galaxy S7 active (SM-G891A) with Android 8 (G891AUCS6CSI2) installed that we want to use with our KNOX Licenses.
Unfortunately Samsung doesnt let you register US Devices with a Knox Profile from the EU KNOX Server.
Our Distributor tried to register the IMEI's of the devices to the EU Server, but the devices wont get any updates, dont see themselves registered to a KNOX Server and still wont accept EU Profiles when offered them via Bluetooth.
Anyone got an idea, how to force the devices to accept the profiles or change the region of their knox?
Thanks in advance!
Best regards,
SheetMetalProduct

technician unlock Mi in Note 8 Pro

Colleagues,
A customer (an older Mr. with a teenager) brought me a note 8t (note 8 pro) to unlock, whe power on go to a screen: "this device is locked this device is associated with an existing Mi Account. For security reasons, you need to enter the password to verify the device" - So what happens: the boy had a chip and was not putting a credits (here the telecom block pre-paid chip when you dont put credits each month), until the telecom canceled the number, and the boy didn't care much for that and bought another chip and some time after, he says he had to reset, anyway, the cell phone turns on and enters the Mi account's length screen, he doesn't remember his password and can't recover, because the code goes to his old number that has been canceled and he has no more.
I'm a technician, but I usually always took care of hardware, I never performed a service more related to software like that.
I didn't find anything on the internet about unlocking the Note 8 Pro, I got here:
I didn't see a step by step so I don't know.
If I re-install Miui will solve this?
https://forum.xda-developers.com/re...ui-stock-reinstall-redmi-note-8-pro-t4004391*
Or there is another way?
Could anyone help?

Sadly as far as I am aware you need to either already have access to the xiaomi account to remove the device, or input the password on the device to unlock it. For security purposes clearly.

JuanM2020 said:
Sadly as far as I am aware you need to either already have access to the xiaomi account to remove the device, or input the password on the device to unlock it. For security purposes clearly.
Click to expand...
Click to collapse
Indeed clearly is for security reason (stolen phone? sounds like a fishy story).
But is not it possible to recover via email? Because if I remember correctly we also had to provide an email upon Mi Account creation. I am not sure because I never had to recover yet, but is not a link sent to attached email to reset account password?
If the guy neither have original number, password or email, that's smells way more than fishy to me
Regards

Question why some of pixel 6pros blocks when you reset it?

i am going to buy pixel 6pro and some of my friend told that some of them blocks when you restart it. they dont know why this happens. i read on other forum that T-mobile unlock causes that problem. can anyone explain why that happens?

yifo777 said:
i am going to buy pixel 6pro and some of my friend told that some of them blocks when you restart it. they dont know why this happens. i read on other forum that T-mobile unlock causes that problem. can anyone explain why that happens?
Click to expand...
Click to collapse
What do you mean by "blocks"?
There's nothing preventing the device from being restarted.
Are you talking about Factory Reset Protection lock, which prevents the device from being used if it is factory reset? Reset is not the same as restart.

oh i get it now.
and does this happen on all pixel 6pros or?

It happens with every Android device where the bootloader is locked. If the seller does not know the username and password of the last user or cannot get a hold of the person whose account is on the phone, setup will not continue. At that point assume the phone is stolen and likely blacklisted.