Recently tried to install Android Pay onto the P9 hoping to make use of the contactless payments made via NFC. After installing the android pay app successfully when going to add a card I get the following message' Android pay can't be used- google is unable to verify that your device or the software running on it is android compatible' I have made no changes to the software, not flashed any rom etc. Has anyone else encountered the same problem, is there something I am doing wrong? I'd assume the P9 would support this feature in the UK.
Mine works fine in uk running b166.
Does the b number relate to build number? If so mine shows as B131
Salty1863 said:
Recently tried to install Android Pay onto the P9 hoping to make use of the contactless payments made via NFC. After installing the android pay app successfully when going to add a card I get the following message' Android pay can't be used- google is unable to verify that your device or the software running on it is android compatible' I have made no changes to the software, not flashed any rom etc. Has anyone else encountered the same problem, is there something I am doing wrong? I'd assume the P9 would support this feature in the UK.
Click to expand...
Click to collapse
Hi mate,
Same issue here. Just got my p9 yesterday second hand and it says the same thing about not being able to verify the device.
Is it safe to assume previous owner rooted?
Salty1863 said:
Does the b number relate to build number? If so mine shows as B131
Click to expand...
Click to collapse
Yes b number is build number. The latest in Europe is 166/170 .
xodeus said:
Yes b number is build number. The latest in Europe is 166/170 .
Click to expand...
Click to collapse
I'm assuming I should have received some sort of OTA update by now then? Recently purchased the phone new from EE
sstanton86 said:
Hi mate,
Same issue here. Just got my p9 yesterday second hand and it says the same thing about not being able to verify the device.
Is it safe to assume previous owner rooted?
Click to expand...
Click to collapse
That could be one of the reasons but then it could not. I purchased mine brand new from EE but unfortunately experiencing the same problem. Seems like I am behind most on some sort of software update
Made a thread about this a week or so ago. Bought a P9 locked to Vodafone and unlocked it. Still had a Vodafone splash screen so flashed the unbranded firmware.
The advice was that the OEM info doesn't match what Google requires, hence needed fixing. I'm away on business at present so can't test the fix, but check my thread and test it!
Sent from my EVA-L09 using Tapatalk
sstanton86 said:
Hi mate,
Same issue here. Just got my p9 yesterday second hand and it says the same thing about not being able to verify the device.
Is it safe to assume previous owner rooted?
Click to expand...
Click to collapse
@Salty1863
I got mine brand new from EE. Build number C440B138
Just tried the Android Pay app and it worked fine. Let me add a card. I do know unlocking bootloader / rooting does intentionally stop the app from working. It's for security. But your phone should not have come from EE in that state brand new.
I think this comes from flashing the C900 variant. You need to change the country code to 432 and then flash B166
Try here for the guide:
http://forum.xda-developers.com/p9/how-to/how-to-change-cust-c900-c432-t3392824
Hi,
Not sure if this address your problem as I cannot remember the exact error message I received but I've been using Android Pay from day 2. On day 1 I couldn't add my card and it kept failing for no reason but I realised this card was already on my Google account.
I can't remember if I added the card via the pay Chrome page or deleted the card from my account and started again but it was one of those two and been working fine ever since. Have even factory reset the phone and reinstalled the app without a hitch.
Like I said - it could help or I could be Barking up the wrong tree.
T
I've had a look around on the net, and other users are suggesting the problem lies with the screen resolution of 480dpi, and that it's too high for the app to recognise it as "official" Android.
Is there a way of changing the dpi of your handset WITHOUT root?
I'm having the same trouble with Android Pay.
Get the message that Google cannot verify my handset or software is Android compatible, when I try to add a card.
Never unlocked the bootloader, or rooted.
Very frustrating
This could be a long shot but I can see that you're from sheffield warface so I may have an odd solution. My contactless wouldn't work anywhere until I paid for a drink in the bar on West Street called Cavendish and ever since then it has been absolutely fine although this was after removing the card and entering the details again.
willhumph said:
This could be a long shot but I can see that you're from sheffield warface so I may have an odd solution. My contactless wouldn't work anywhere until I paid for a drink in the bar on West Street called Cavendish and ever since then it has been absolutely fine although this was after removing the card and entering the details again.
Click to expand...
Click to collapse
It won't even let me add a card
I just got my p9 yesterday and it's taken card details fine. The security test app (can't remember name) passes. Now I just have to try it in a shop
My P9 fails the Google safety net test.
I did try the nougat beta, and have come back down to MM.
I didn't root or unlock bootloader though. I wonder if I triggered something when I was messing about with it. All root test apps show me as locked.
Same issue here. Received my phone back from Huawei repairs and no longer allows Android Pay or fingerprint login for Natwest app. No flashing or rooting whatsoever. Fails SafetyNet test with the "CTC Profile Match:False" nonsense too.
Currently on EMUI 4.1 Build EVA-C900B166 and Android 6.0
Don't really want to be flashing anything onto the phone and have seen the OnePlus 3 seemed to have a similar issue before it was resolved with an update however I got nowhere when speaking to Huawei this afternoon. Has anybody having any luck resolving this without too much tinkering with the software?
JacquesPollard said:
Same issue here. Received my phone back from Huawei repairs and no longer allows Android Pay or fingerprint login for Natwest app. No flashing or rooting whatsoever. Fails SafetyNet test with the "CTC Profile Match:False" nonsense too.
Currently on EMUI 4.1 Build EVA-C900B166 and Android 6.0
Don't really want to be flashing anything onto the phone and have seen the OnePlus 3 seemed to have a similar issue before it was resolved with an update however I got nowhere when speaking to Huawei this afternoon. Has anybody having any luck resolving this without too much tinkering with the software?
Click to expand...
Click to collapse
You are on C900 which is a "Frankenfirmware" (flashing a C432 build over a C636 make appear C900 for example)
To succeed the safetynet check you mustn't be on C900.
Envoyé de mon EVA-L09 en utilisant Tapatalk
Marsou77 said:
You are on C900 which is a "Frankenfirmware" (flashing a C432 build over a C636 make appear C900 for example)
To succeed the safetynet check you mustn't be on C900.
Envoyé de mon EVA-L09 en utilisant Tapatalk
Click to expand...
Click to collapse
Hi and thank you for your reply.
I have no idea about anything like this, what is C900 and a "frankenfirmware" and ultimately is it simply going to have to be a matter of me waiting on a manufacturer update? Sorry for the more than likely stupid questions?!
JacquesPollard said:
Hi and thank you for your reply.
I have no idea about anything like this, what is C900 and a "frankenfirmware" and ultimately is it simply going to have to be a matter of me waiting on a manufacturer update? Sorry for the more than likely stupid questions?!
Click to expand...
Click to collapse
You can read more here.
http://forum.xda-developers.com/showthread.php?t=3384748
A C900 can't receive OTA nor accept manual update. You have to unlock bootloader then do some manipulation. Read this thread
Envoyé de mon EVA-L09 en utilisant Tapatalk
Related
A few days after updating my phone to Nougat, my phone restarted itself, and after the restart, a security error showed up saying "This phone has been flashed with unauthorized software and is locked", and after unlocking the phone a screen came up saying that my device has been network locked and it can be unlocked using the device unlock app, and the invalid sim card error.
I was never rooted or anything like that, my phone had received OTA updates. I did not master reset, but I rebooted many times, and the error message appeared on every boot, but disappeared after a while allowing me to use my phone. And now, although the error doesn't seem to appear anymore, i still can't use my network, and when I checked the IMEI, it had changed to 350000000000006, and the one on the back is different.
Is there any possible way to fix this without sending this phone back to Samsung/T-Mobile for exchange, because I had bought this phone from USA but brought it to Pakistan, and Samsung Pakistan says that they would charge me for the repairs ( I still haven't visited them, they told this to me through mail).
HELP PLEASE?
Bump?
Have you tried using Samsung Smart Switch?
DevicesNow said:
Have you tried using Samsung Smart Switch?
Click to expand...
Click to collapse
I didn't try Samsung Smart Switch, but I had reflashed it using Odin, and tried a factory reset and it didn't fix it, i got it fixed through Z3X box.
This happened to me also.
ashal said:
A few days after updating my phone to Nougat, my phone restarted itself, and after the restart, a security error showed up saying "This phone has been flashed with unauthorized software and is locked", and after unlocking the phone a screen came up saying that my device has been network locked and it can be unlocked using the device unlock app, and the invalid sim card error.
I was never rooted or anything like that, my phone had received OTA updates. I did not master reset, but I rebooted many times, and the error message appeared on every boot, but disappeared after a while allowing me to use my phone. And now, although the error doesn't seem to appear anymore, i still can't use my network, and when I checked the IMEI, it had changed to 350000000000006, and the one on the back is different.
Is there any possible way to fix this without sending this phone back to Samsung/T-Mobile for exchange, because I had bought this phone from USA but brought it to Pakistan, and Samsung Pakistan says that they would charge me for the repairs ( I still haven't visited them, they told this to me through mail).
HELP PLEASE?
Click to expand...
Click to collapse
The same has happened with me. Can you please tell me how you managed to unlock. From where? how much it costed? Please help me. Thanks.
Hunterzzz said:
The same has happened with me. Can you please tell me how you managed to unlock. From where? how much it costed? Please help me. Thanks.
Click to expand...
Click to collapse
I had taken in to a repair shop who had a Z3X box. That's the only way to get it fixed. He downgraded my phone to Marshmallow and re-flashed the cert. I live in Pakistan and that costed my Rs.1000 (i.e. $10). Make sure you take your phone's box with you as a proof of purchase because changing IMEIs is illegal in many places.
P.S. I can't upgrade to Nougat now, if I will, the phone won't register to the network.
ashal said:
I had taken in to a repair shop who had a Z3X box. That's the only way to get it fixed. He downgraded my phone to Marshmallow and re-flashed the cert. I live in Pakistan and that costed my Rs.1000 (i.e. $10). Make sure you take your phone's box with you as a proof of purchase because changing IMEIs is illegal in many places.
P.S. I can't upgrade to Nougat now, if I will, the phone won't register to the network.
Click to expand...
Click to collapse
Thanks mate. I also live in Pakistan - Lahore. I took my phone to Hafeez center and they charged me 1500. Now the phone is on Marshmallow. I'm receiving notification of update. I've tried 3 times but if failed to install. When I tap on update it downloads the OS which is about 1.3GB. then restarts to install but it fails when reaches 30%.
Can you please tell me why we can't update our phones. I'm using another s6 which is also of T-mobile and it's running fine on nougat.
Hunterzzz said:
Thanks mate. I also live in Pakistan - Lahore. I took my phone to Hafeez center and they charged me 1500. Now the phone is on Marshmallow. I'm receiving notification of update. I've tried 3 times but if failed to install. When I tap on update it downloads the OS which is about 1.3GB. then restarts to install but it fails when reaches 30%.
Can you please tell me why we can't update our phones. I'm using another s6 which is also of T-mobile and it's running fine on nougat.
Click to expand...
Click to collapse
Not sure about that but we can't update because probably our CERT files have been patched in EFS is messed, I got it done back in July 2017, and at that time, the guy who repaired it said that they didn't have Z3X's software update for Nougat, so they had to downgrade my phone to Marshmallow, and the patch they used won't work on Nougat. Don't know about yours though, maybe he used an updated patch or a different tool, you can ask that guy whether if its safe for you to update to Nougat or not, if he allows it, then try flashing Nougat through Odin, if it doesn't work you'll have to get it patched by him again. Don't update if he doesn't allow, otherwise he won't patch it again without extra charges, and if he allows that and something goes wrong you can blame him for that
Hi,
I have the international Note 9 unlocked (SM-N960F/DS) and I am still on N960FXXU1ARH5 Security Patch : 1 August.
It's october 7th now, should I have not received an update?
Nic2112 said:
Hi,
I have the international Note 9 unlocked (SM-N960F/DS) and I am still on N960FXXU1ARH5 Security Patch : 1 August.
It's october 7th now, should I have not received an update?
Click to expand...
Click to collapse
Depends how they roll out the update i got my security update few days ago on my unlocked BTU some still haven't have you manually checked for update
Nic2112 said:
Hi,
I have the international Note 9 unlocked (SM-N960F/DS) and I am still on N960FXXU1ARH5 Security Patch : 1 August.
It's october 7th now, should I have not received an update?
Click to expand...
Click to collapse
Just download the latest firmware and flash via odin, problem solved.
Where do u live it also depends on region i also stuck on 1 august security patches
Also the are rolling out a new update for camera
mimo2008 said:
Depends how they roll out the update i got my security update few days ago on my unlocked BTU some still haven't have you manually checked for update
Click to expand...
Click to collapse
Hi,
It looks like my phone's region was set to Singapore (XSP). Both the SIM cards I use are for Canada. Is there a way to change the phone's region?
Nic2112 said:
Hi,
It looks like my phone's region was set to Singapore (XSP). Both the SIM cards I use are for Canada. Is there a way to change the phone's region?
Click to expand...
Click to collapse
as stated before, just flash another n960f firmware manually.
so try OXM
single sim and dual sim have the same firmware in case you were wondering.
bober10113 said:
as stated before, just flash another n960f firmware manually.
so try OXM
single sim and dual sim have the same firmware in case you were wondering.
Click to expand...
Click to collapse
Thank you and I know I'm asking very basic questions here, it's just so simple with a Pixel and I really don't want to brick the Note.
What you are saying is that it doesn't matter the region I pick, the Note 9 will continue to work as an "international" phone where my two Canadian providers and Google Pay will continue to work? I have XSP right now as region so if my phone is set to Singapore and I can use Google pay in Canada, one doesn't prevent the other from working.
I can also see that versions ending in "ARJ1" are available from samfirm and the "J" would mean it includes October patches if I understand everything right.
Nic2112 said:
Thank you and I know I'm asking very basic questions here, it's just so simple with a Pixel and I really don't want to brick the Note.
What you are saying is that it doesn't matter the region I pick, the Note 9 will continue to work as an "international" phone where my two Canadian providers and Google Pay will continue to work? I have XSP right now as region so if my phone is set to Singapore and I can use Google pay in Canada, one doesn't prevent the other from working.
I can also see that versions ending in "ARJ1" are available from samfirm and the "J" would mean it includes October patches if I understand everything right.
Click to expand...
Click to collapse
familiarize your self with what is a snapdragon and an exynos and the different phone models pertaining to each then bricking won't be an issue. anyways ODIN usualy wont let you flash something that is not compatible.
yes J is October and for google pay, usually its supported pretty much wide spread. samsung pay is an other story and is the more coveted of the 2 'pays'. but since you're after Google pay, it should still be working.
just remember that you cant downgrade bootloaders so be sure of your intentions because you cant revert back to a lesser revision.
bober10113 said:
just remember that you cant downgrade bootloaders so be sure of your intentions because you cant revert back to a lesser revision.
Click to expand...
Click to collapse
Thank you, that's a very good point. I know Samsung can be slow to update to begin with so I was looking for ways to be at least not in a situation where my phone is the last to get the slow updates. To have an expensive flagship phone that still can't apply the September updates is disappointing. I have manually flashed my pixel often because the "check for update" would not give me an update so that's not usually a problem for me. I also liked how the pixel has very few customization options compared to the Note 9, that's fewer options to reconfigure after a fresh flash!
Nic2112 said:
Thank you, that's a very good point. I know Samsung can be slow to update to begin with so I was looking for ways to be at least not in a situation where my phone is the last to get the slow updates. To have an expensive flagship phone that still can't apply the September updates is disappointing. I have manually flashed my pixel often because the "check for update" would not give me an update so that's not usually a problem for me. I also liked how the pixel has very few customization options compared to the Note 9, that's fewer options to reconfigure after a fresh flash!
Click to expand...
Click to collapse
for me the more options the better!
I have never received an OTA in my life. always applied manually
bober10113 said:
for me the more options the better!
I have never received an OTA in my life. always applied manually
Click to expand...
Click to collapse
I applied the update from today (in the stock firmware thread) and I was a bit concerned as this was a first flash but everything went well. I have to say as nice as it is to like a phone "stock" like the pixel, having customization option is good. Also it will discourage me from doing full wipes all the time because it takes more time to reconfigure!
Thank you for your help today, I really had a hard time figuring out which country/region I should flash.
Nic2112 said:
I applied the update from today (in the stock firmware thread) and I was a bit concerned as this was a first flash but everything went well. I have to say as nice as it is to like a phone "stock" like the pixel, having customization option is good. Also it will discourage me from doing full wipes all the time because it takes more time to reconfigure!
Thank you for your help today, I really had a hard time figuring out which country/region I should flash.
Click to expand...
Click to collapse
glad everything turned out well
It was working fine on android 8 since it came out (4-5 months?)
There was an annoying notification since the past 2- 3 weeks for a software update, so I decided to finally do it.
No changes after doing that update, I received an another update notification of around 150 mb. ( not really sure but def. under 300mb)
After that, my mobile network service suddenly went out, mobile data is disabled and grayed out, same when I try to click on Mobile connections.
On the lock screen, it says "service disabled" and *#06# says imei null.
What happened? I know this definitely happened after the update, and my phone was bought brand new, how can i fix this?
Also, I'm located in India and use a Vodafone sim card, I tried putting other carrier sim and it's still giving the same error which worked perfectly before the update
Any help would be appreciated
I'm guessing I might have to do a factory restore, but I would like to have that as the last option
try revert back to 20d
immns said:
try revert back to 20d
Click to expand...
Click to collapse
Yeah, had to do a default firmware flash to 20d
. Thanks!
How
Pastasan said:
Yeah, had to do a default firmware flash to 20d
. Thanks!
Click to expand...
Click to collapse
Hello
How do you do that ??? Do you have the unlock app installed ?
Because the same happened to me !! Hlp !
69janez said:
Hello
How do you do that ??? Do you have the unlock app installed ?
Because the same happened to me !! Hlp !
Click to expand...
Click to collapse
unlock app will be pre-installed, it's stock app on H872
Yes, it is installed and worked fine, but after last security update few days ago, blocked and i could not use my lg g6 anymore ! I got a note that my phone is not agilibili anymore. I bought it on e- bay its fine phone, but i dont know the solution to resolve this ! We dont haved T mobile in Slovenia ! Tnx for answere !
69janez said:
Yes, it is installed and worked fine, but after last security update few days ago, blocked and i could not use my lg g6 anymore ! I got a note that my phone is not agilibili anymore. I bought it on e- bay its fine phone, but i dont know the solution to resolve this ! We dont haved T mobile in Slovenia ! Tnx for answere !
Click to expand...
Click to collapse
my device also shows that message "not eligible bla..bla.." I think you have to downgrade to 20d firmware. But as you can see my phone is running latest update and cellular is working fine since I believe once this phone is unlocked permanently, it will remains unlocked.
immns said:
my device also shows that message "not eligible bla..bla.." I think you have to downgrade to 20d firmware. But as you can see my phone is running latest update and cellular is working fine since I believe once this phone is unlocked permanently, it will remains unlocked.
Click to expand...
Click to collapse
As i understand T mobile unlock sheet app, after you unlock phone, app should delete itself !! In my case this didnt happend, and the result is as I describe before ! It seems i spend 240 € for very fine but lockedphone. Next time dont buy on e- bay you idiot, i say to myself. Because two days ago i bought new Samsung A7 2018 with 64 gb for les money ! And unlocked, of course !!
All the besdt in the future !!! JR !
need some help here , my pixel 4 xl just updated to jan 2021 update
, post update im unable to connect to mobile network .
already tried hard reset not working
also flashed previous factory image still aint working
is any other thing i can try to solve the problem or im doomed?
capayam said:
need some help here , my pixel 4 xl just updated to jan 2021 update
, post update im unable to connect to mobile network .
already tried hard reset not working
also flashed previous factory image still aint working
is any other thing i can try to solve the problem or im doomed?
Click to expand...
Click to collapse
Who is your provider? Are you using SIM or eSIM? Are you rooted? Did you disable all the Magisk modules before the update? If you forgot that step, have you since disabled all Magisk modules and started over?
While you may be out of commission on the phone side (although, Google Voice would be a good band-aid), you may not be out of commission on the SMS side. Google's text app, Messaging, recently went live with RCS messaging and it can send texts via WiFi.
Incidentally, if it's Google Fi that's giving you fits, the same thing happens to me every time I do a clean install. Fi refuses to connect until I've rebooted two or three times and then the final confirmation comes several hours later.
im in malaysia bought secondhand 1 year ago on grey market , check my sim with another phone , working well on that phone. had been running my phone on regular stock since bought.
capayam said:
im in malaysia bought secondhand 1 year ago on grey market , check my sim with another phone , working well on that phone. had been running my phone on regular stock since bought.
Click to expand...
Click to collapse
Okay, you answered almost none of my questions but it's irrelevant at this point because it sounds like the phone was stolen. If the IMEI is reported as stolen, it's flagged in a database and alerted carriers will shut off the service.
If that's the case, at this point, I'd be more concerned about the police knocking on my door than lack of mobile service. I'd send you over to IMEI.info to verify but I'm guessing I haven't told you anything you didn't already know.
imei number legit not reported or blacklisted, but yeah i think this phone is doomed unless there some magic update resolved this
capayam said:
imei number legit not reported or blacklisted, but yeah i think this phone is doomed unless there some magic update resolved this
Click to expand...
Click to collapse
Why don't you try to reset using the last official 10 firmware (to reset all partitions), then activate through setup, then flash and test a custom rom. This is of course only possible if it's an unlocked bootloader (which you didn't mention) but that's where I'd start especially if it worked before the update. You say is legit and sounds like it worked BEFORE the last update so roll back and then use a custom rom.
GROOVYJOSHCLARK said:
Why don't you try to reset using the last official 10 firmware (to reset all partitions), then activate through setup, then flash and test a custom rom. This is of course only possible if it's an unlocked bootloader (which you didn't mention) but that's where I'd start especially if it worked before the update. You say is legit and sounds like it worked BEFORE the last update so roll back and then use a custom rom.
Click to expand...
Click to collapse
will try it later dude
capayam said:
will try it later dude
Click to expand...
Click to collapse
Unfortunately it's my best guess because I can't reproduce it myself but if it worked prior to the firmware upgrade, it should work by reverting the firmware to the previous firmware in my opinion. I'd take it the step furtherand go with a custom 10 ROM to remove Google firmware updates messing with it in the future (assuming we get it working again).
Interestingly enough, I searched other forums and found other users reporting the same issue. Again, assuming it worked on the previous firmware, I would roll bak to it. Ideally, I would rollback to 10 because I know 10 works (not sure how well it works for you in your local and provider), but thats where I would start. Backup everything you need, then use the last 10 firmware to -w the device and activate then start over.
Why is this posted in development?
shiftr182 said:
Why is this posted in development?
Click to expand...
Click to collapse
who knows
Hi guys, I'm in a very big trouble, since I was trying to rollback yesterday from A13 Oxygen 13, in a converted NE2110 Chinese model flashed previously with NE2115 Rom, I was having ridiculous battery life with the rom, so I want to test the European NE2113 rom, I've download the NE2113 Rollback package and applied with the local update apk provided by Oneplus, the procedure was apparently sucessfull, but SIM isn't recognized when A12 NE2113 rom booted, I've thought its a band relates problem, so I've flashed black the NE2115, but stills the same, I've get in to the IMEI numbers, and both are NULL and Baseband is blank.
I'm in Ecuador so it's absolutely impossible for me to sent the phone to Oneplus Repair services, and even if it was possible I doubt a lot they can take the phone, because it's bootloader unlocked.
If anyone have an idea about something I can do, I'll really appreciate that, it's an expensive phone and I've put a lot of effort to buy one trought and auction sale and even played to import from United States, so if you think there any hope available please share with me, I've read the one post here with someone who still needs to repair the IMEI seeing it's impossible for now, but at least I have to try to restore the phone, I can't have a media player unusable SIM phone of almost 700 bucks.
dannytgt said:
Hi guys, I'm in a very big trouble, since I was trying to rollback yesterday from A13 Oxygen 13, in a converted NE2110 Chinese model flashed previously with NE2115 Rom, I was having ridiculous battery life with the rom, so I want to test the European NE2113 rom, I've download the NE2113 Rollback package and applied with the local update apk provided by Oneplus, the procedure was apparently sucessfull, but SIM isn't recognized when A12 NE2113 rom booted, I've thought its a band relates problem, so I've flashed black the NE2115, but stills the same, I've get in to the IMEI numbers, and both are NULL and Baseband is blank.
I'm in Ecuador so it's absolutely impossible for me to sent the phone to Oneplus Repair services, and even if it was possible I doubt a lot they can take the phone, because it's bootloader unlocked.
If anyone have an idea about something I can do, I'll really appreciate that, it's an expensive phone and I've put a lot of effort to buy one trought and auction sale and even played to import from United States, so if you think there any hope available please share with me, I've read the one post here with someone who still needs to repair the IMEI seeing it's impossible for now, but at least I have to try to restore the phone, I can't have a media player unusable SIM phone of almost 700 bucks.
Click to expand...
Click to collapse
1 Update your device to the latest version A16
2 Reset via recovery
DenisPDA said:
1 Update your device to the latest version A16
2 Reset via recovery
Click to expand...
Click to collapse
I've tried but actually I've notice a bigger problem : battery isn't charging, I've only 30% left, tried to reflash the NE2115 with same results IMEIs are gone, phone connects trought USB cable to PC but is no way to charge it