Related
Hi there.
I have a problem with my HTC Desire. I have downloaded an .apk file for it and also the Astro File Manager to install it. I installed astro file manager and went to the apk location. I clicked install but there is a problem. Every time I try to click install it comes up with the following message:
Parse Error
There is a problem parsing the package.
At first I thought the file is corrupt. I downloaded several other apks (same file) but nothing seemed to bypass the error. Please can anyone tell me what is wrong with it. I tried searching on google but nothing relevant came up with the search.
I have attached the file (apk) to this thread.
Thank you!
OmbladonHTC
I've no problem to install it. BTW what android version do u use. I think this app is supported by Android 4.0+ (ics).
This doesnt work beccause of my version. But neither does this
twisted_forever said:
I've no problem to install it. BTW what android version do u use. I think this app is supported by Android 4.0+ (ics).
Click to expand...
Click to collapse
Hi There.
Thanks for replying, I have one problem, you were right, it doesn't work because it is version 2.3 and up and I have 2.2.2. But there is another problem, Minecraft doesn't work either and it is 2.1 and up. I really don't understand. Here are my phone specs:
Software Information:
Android Version: 2.2.2
Kernel Version: 2.6.32.15
And also here is the minecraft that doesn't work for me even when it says 2.1 and it is available on Google Play. But I don't want to buy it just because of credit card details and such.
Thanks again
OmbladonHTC said:
But I don't want to buy it just because of credit card details and such.
Click to expand...
Click to collapse
But I don't want to buy it because I'm cheap and like to steal apps instead of supporting the developers who put time, effort and money into creating these apps for me.
Fixed that for you. This is clearly what you meant.
Do something better with your life
bortak said:
But I don't want to buy it because I'm cheap and like to steal apps instead of supporting the developers who put time, effort and money into creating these apps for me.
Fixed that for you. This is clearly what you meant.
Click to expand...
Click to collapse
Did I tell anyone to comment about what I said? No I did not. So why do you have to be the only one who is messed up? Hah, you have a rooted phone meaning you can get free items too so why don't you shut up and go play outside kid.. If you dont wanna do that at least do something useful and help people. This is a website for helping not for ignorant people such as yourself, so please find something better to do.
I don't want to give my credit card details and others because they are private and any good hacker can bypass Android's security and enter the website and steal everything...I see that you don't know what happened to Sony last year do you?
Hey junior calm down... Bortak is very helpful but warez? C'mon! A lot of effort been put to development of these apk... as you saying about security on android you did first step how to help hackers you are afraid of... Having root and downloading dodgy apk from untrusted sites... Well done...
Now to the point of your question... your system needs to be updated or you need to download correct version of your apk...
Please delete that paid app from your attachment as it is breaking xda rules:
6. Do not post warez.
If a piece of software requires you to pay to use it, either pay or find your cracks and serials somewhere else. We do not accept warez nor do we permit any member to promote or describe ways in which Warez, cracks, serial codes or other means of avoiding payment, can be obtained.
Don't take it a bad way pls
OmbladonHTC said:
Hi there.
I have a problem with my HTC Desire. I have downloaded an .apk file for it and also the Astro File Manager to install it. I installed astro file manager and went to the apk location. I clicked install but there is a problem. Every time I try to click install it comes up with the following message:
Parse Error
There is a problem parsing the package.
At first I thought the file is corrupt. I downloaded several other apks (same file) but nothing seemed to bypass the error. Please can anyone tell me what is wrong with it. I tried searching on google but nothing relevant came up with the search.
I have attached the file (apk) to this thread.
Thank you!
OmbladonHTC
Click to expand...
Click to collapse
hey juz check if ur sd is protected with password or something. and its the reason y its showing... if sd is protected under developer options & phone is rooted it occurs. check that out n try and tht prob will be solved..it worked for me. check that out n reply.
anish.2010 said:
hey juz check if ur sd is protected with password or something. and its the reason y its showing... if sd is protected under developer options & phone is rooted it occurs. check that out n try and tht prob will be solved..it worked for me. check that out n reply.
Click to expand...
Click to collapse
U think he still has this problem over 2 years later??
jmcclue said:
U think he still has this problem over 2 years later??
Click to expand...
Click to collapse
juz helping out man..as i came across that,,
Hey all,
For starters, disclaimer:
I am not responsible for thermonuclear war, bricks, and or your parents grounding you for said brick.
This method is VERY finicky, and very hard to reproduce. I cannot promise anything. It worked for me.
You need to download the following apks:
- KingRoot (Newest available on kingroot.net)
- KingUser (Newest available on kingroot.net)
- SunShine (3.0+, available @ theroot.ninja)
Once you have downloaded all of these apk files, follow the below steps:
1. Go to Settings ==> Security ==> Check "Allow Installation of Apps from Unknown Sources" and agree to the prompt.
2. Go to Settings ==> About ==> Software Info ==> Tap "Build Number" 12 Times.
3. Go to Settings ==> Developer Options ==> Check "USB Debugging"
4. Now install all the APK files by clicking on them.
5. Ensure you are connected to a reliable WiFI network.
6. Ensure you have Location Services/GPS and High Accuracy turned on in Settings.
7. Open KingRoot and select "Try to Root" when prompted.
8. Now, wait for it to complete. We don't expect KingRoot to succeed! We only expect it to display a prompt and then fail! If it reboots, you need to reopen KingRoot and try again.
Keep closing (through your Recent Apps Menu) and re-opening/re-running KingRoot until you get a prompt that says "Google cannot verify this app, would you like to Install KingUser?" click "Install" any similar message will work, i.e. "Google recommends you not install this app, would you like to install KingUser?" but a similar message must display, if it doesn't display, re-run KingRoot.
9. After the message goes away, and KingRoot fails, close the app, and open KingUser.
10 Verify that KingUser says you are rooted.
At this point, you are temp-rooted. You cannot write to the /System partition. You can only use apps that don't require /System access (very few).I recommend you cough up the $25 for SunShine. Only follow the instructions from here if you have $25 and want to unlock your boot loader, go S-OFF, and get Permanent Root & R/W /System Access.
11. Now, open SunShine and follow the on screen prompts, grant it SU access when prompted. It will reboot (Do not re-open SunShine as instructed after reboot!!!).
12. Repeat the steps 7-9 outlined above to re-gain temp-root.
13. NOW re-Open Sunshine and follow the on-screeen prompts.
Congrats! You are S-OFF, Unlocked, and your warranty bit returns an "OFFICIAL" status in bootloader mode. Now to install TWRP.
14. Download TWRP from here: http://android.cmphys.com/twrp-m7vzw/ ON YOUR PC/MAC/LINUX BOX
Make sure to use this and not the stock TWRP build! The stock TWRP build doesn't have full Lollipop encryption support (as of 5/29/15).
15. Reboot to bootloader with the volume buttons, or use ADB to reboot to bootloader.
16. Plug your phone into your PC and verify you see it when you run "fastboot devices" from CMD/Terminal.
17. Run "fastboot flash recovery /pathtotwrpimghere/nameoftwrpimg.img".
18. Run the volume buttons to select "Recovery".
19. Download the flashable SuperSU .zip for 2.46 and transfer it to your phone while in TWRP.
20. Install the SuperSU .zip from TWRP and reboot.
21. Uninstall KingUser.
You are rooted and S-OFF. Enjoy your ROMs/Kernels freely.
This method is highly finicky. It worked for me, and it can for you! it took me about an hour to get KingRoot to display the message asking to install KingUser. Just keep trying!
Good Luck!!!
Anyone else get this to work?
Sent from my Nexus 6 using XDA Free mobile app
I did get this to work. Previously stock lollipop and s-on locked hboot 1.61.
Now s-off unlocked 1.61 and stock lollipop.
I installed kingroot/king user. Got root. Ran sunshine...purchased it...sunshine rebooted phone.
On reboot clear data of kingroot/king user...uninstall and reinstall king root / king user. Get root again...finish sunshine.
Rebooted, unlocked! Rerun kingroot stuff for root. Install twrp from play store, ignore warnina have it install...works. Perm root now.
Sent from my Nexus 6 using XDA Free mobile app
i cant afford 25$ for sunshine :'( #3rdworldsproblems
Anyone having an issue installing kingroot? I was able to install once, but since then I continually get an error saying app not installed.
I thought Sunshine could S-Off LP on the Verizon HTC One already. No?
xdadevnube said:
I thought Sunshine could S-Off LP on the Verizon HTC One already. No?
Click to expand...
Click to collapse
No, it does not: everything before Loolypoop works with Sunshine.
nvm
This method works! Stock lolipop hboot 1.61. Thank you so much!
I got it to work! Verizon HTC One M7 5.0.2
In fact, all I had to do was download KingRoot and it actually successfully rooted my phone. I checked Root checker just in case and it says Root access is properly installed.
Austinh1517 said:
I got it to work! Verizon HTC One M7 5.0.2
In fact, all I had to do was download KingRoot and it actually successfully rooted my phone. I checked Root checker just in case and it says Root access is properly installed.
Click to expand...
Click to collapse
You won't have true write protection disabled until you turn s-off if you haven't already. Other wise apps you remove and settings you change with root will revert each time you reboot.
Sent from my HTC6535LVW using Tapatalk
dottat said:
You won't have true write protection disabled until you turn s-off if you haven't already. Other wise apps you remove and settings you change with root will revert each time you reboot.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
This is true. With these phones, root itself is almost moot. S=off is what I really want. Sure u can use titanium backup, but u CANT remove system apps, change boot animations, edit build.prop, etc... All because of.the built in write protection which u need s=off for... Ppl need to just bite the bullet and get sunshine. I got it the day it finally came out for us (back on 4.4.2) and been thankful for it every day since...
dottat said:
You won't have true write protection disabled until you turn s-off if you haven't already. Other wise apps you remove and settings you change with root will revert each time you reboot.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Yeah I noticed that. I'll get Sunshine sooner or later
How many times did you guys have to run KingRoot? And do you run it to completion each time? I've run it at least 10 times on my device, it fails every time, and I have yet to see a prompt as described in the OP.
breaker911 said:
Anyone having an issue installing kingroot? I was able to install once, but since then I continually get an error saying app not installed.
Click to expand...
Click to collapse
Now I'm having this problem. I kept running kingroot, then it rebooted on me and told me I couldn't try to run it any more. So I uninstalled it thinking that would clear the problem. Now every time I try to install it it errors out and says "App not installed". I have no idea what to try next. Anyone have any hints?
dougleto said:
Now I'm having this problem. I kept running kingroot, then it rebooted on me and told me I couldn't try to run it any more. So I uninstalled it thinking that would clear the problem. Now every time I try to install it it errors out and says "App not installed". I have no idea what to try next. Anyone have any hints?
Click to expand...
Click to collapse
Always can ruu
Sent from my HTC6535LVW using Tapatalk
I'm not quite ready to nuke my entire phone just yet . Or is there a slightly less nuclear RUU option that I'm unaware of?
dottat said:
Always can ruu
So very sorry for my ignorance As I am going to get the cell phone craze and then the smartphone craze.
The last cell phone I owned took a team of mules to take the battery.
Please tell me what the term ruu means.
My interest is to completely or near completely "gut" my Verizon note 4 in my US Cellular note 4 and then be able to install single or multi boot systems, hopefully using modular Code
That would be either less than typical roms then I read about here or else very streamlined roms only data that would support the main operating system and whatever hardware is installed. I certainly wouldn't want to end up with S OFF and routed machines that I could then install stock or custom-written Apps, software firmware and Code whatever else kind I may desire. well I remain hopeful that many will tell me this is not a problem even so it's all tells me it is impossible I will remain confident of success As I am convinced tenacity is more powerful than all the smarts in the world as well as a good looks fast runners sweet talkers and even possibly the best Coders out there that may only lack that one trait named tenacity. if there's another post about this anymore please get me to that.
Thank you in advance we anticipated cooperation and kindness, I remain.
Charlie aka Gladhatter
Sent from my SM-N910V using XDA Free mobile app
Er
Click to expand...
Click to collapse
dougleto said:
I'm not quite ready to nuke my entire phone just yet . Or is there a slightly less nuclear RUU option that I'm unaware of?
Click to expand...
Click to collapse
Factory reset, or using HTC sync to "repair phone"
Sent from my HTC6500LVW using XDA Free mobile app
---------- Post added at 09:23 PM ---------- Previous post was at 09:17 PM ----------
Gladhatter said:
So very sorry for my ignorance As I am going to get the cell phone craze and then the smartphone craze.
The last cell phone I owned took a team of mules to take the battery.
Please tell me what the term ruu means.
My interest is to completely or near completely "gut" my Verizon note 4 in my US Cellular note 4 and then be able to install single or multi boot systems, hopefully using modular Code
That would be either less than typical roms then I read about here or else very streamlined roms only data that would support the main operating system and whatever hardware is installed. I certainly wouldn't want to end up with S OFF and routed machines that I could then install stock or custom-written Apps, software firmware and Code whatever else kind I may desire. well I remain hopeful that many will tell me this is not a problem even so it's all tells me it is impossible I will remain confident of success As I am convinced tenacity is more powerful than all the smarts in the world as well as a good looks fast runners sweet talkers and even possibly the best Coders out there that may only lack that one trait named tenacity. if there's another post about this anymore please get me to that.
Thank you in advance we anticipated cooperation and kindness, I remain.
Charlie aka Gladhatter
Sent from my SM-N910V using XDA Free mobile app
Er
Click to expand...
Click to collapse
Unfortunately most of us in this section won't be able to help. Your best bet is going to the Verizon Samsung Galaxy Note 4 section. Coming for help with your note 4 in an HTC section is like asking some people who know Chevy if they could help you fix your Ford. The expert advise would be ask the Ford experts and not the Chevy experts.
RUU is a term for HTC phones: Rom Update Utility. Samsung devices use Odin and I have no idea how to use it. I would help if I could.
The correct area for your device:
http://forum.xda-developers.com/note-4-verizon
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Factory reset, or using HTC sync to "repair phone"
Sent from my HTC6500LVW using XDA Free mobile app
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
What does the repair phone option do? And I guess I wasn't too clear. My phone, for the most part, is fine. Everything works fine *except* that KingRoot won't install correctly. All my other apps are fine.
OK, I just bought a new Moto Z2 Play, and I of course, want to Root it. I have done Root on all my previous smart phones so I have some experience. I read thru all the threads here, but still have some remaining questions.
Where can I get the latest Moto drivers for Win 10 64-bit? I rather have just the drivers, if possible, than some other bloat Moto utilities too.
Where can I get the latest ADB ? I know, there are lots of sources if I search, but I am looking for a safe copy.
What do I use for TWRP? TWRP 3.2.1-0 ? [TWRP][64 bit][3.2.1_r12] ? Alternate TWRP v3.1.1.0 ? I am even asking, because I read a post and its reply, that mentioned that the 64-bit had to be used, but I haven't seen that mentioned anywhere else.
As part of TWRP, should I do the "Swipe to allow modifications for /system" ? I have read posts suggesting either way, and remain unsure which is best.
I plan to install the latest Magisk Manager, v5.5.5. Or should I install simply Magisk v15.3?
Should I plan to Hide the Magisk Manager?
Do I need to, also, install SuperSU and BusyBox from the Google Play Store?
Is there anything additional I need to do, to successfully handle Safety Net ?
Thanks!
Did you read?
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
I used Juniors version of TWRP.
https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Yes to Magisk Manager.
Yes to Magisk.
No to SuperSU.
No to Busy Box.
First, let me start with a heartfelt thanks! :highfive:
pizza_pablo said:
Did you read?
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
Click to expand...
Click to collapse
Yes, but it has instructions like this:
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda.
Click to expand...
Click to collapse
Which is why it left feeling unsure, do I swipe or not? Is having the system partition modified "good" and a normal part of this type of root'ing?
Plus, the mention of flashing SuperSU, lead to my question about going that (which you replied 'no').
Maybe I am simply having a case of information overload. With possibly, a strong addition of having too many different opinions which might not all be valid.
WaltA said:
First, let me start with a heartfelt thanks! :highfive:
Yes, but it has instructions like this:
Which is why it left feeling unsure, do I swipe or not? Is having the system partition modified "good" and a normal part of this type of root'ing?
Plus, the mention of flashing SuperSU, lead to my question about going that (which you replied 'no').
Maybe I am simply having a case of information overload. With possibly, a strong addition of having too many different opinions which might not all be valid.
Click to expand...
Click to collapse
I'm glad you have read! :good:
I understand you're dilemma and have also experience info overload, when researching rooting / flashing procedures. It never hurts to read it, yet again and watch any YouTube videos available on the subject.
I always swipe to allow modifications when installing TWRP. Otherwise, TWRP will be in READ ONLY mode.
I am not certain about Busy Box, but haven't needed it. Magisk has A Super User function, so SuperSU is not needed.
I am no expert, just trying to help, so please don't take anything I've said as the gospel. Read everything and then read it again.
pizza_pablo said:
Did you read?
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
I used Juniors version of TWRP.
https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Yes to Magisk Manager.
Yes to Magisk.
No to SuperSU.
No to Busy Box.
Click to expand...
Click to collapse
Any hint up to which 8.0 security patch update will @Junior Passos method will work
Sent from my Moto Z2 Play using XDA Labs
The Analog Kid said:
Any hint up to which 8.0 security patch update will @Junior Passos method will work
Click to expand...
Click to collapse
No. I'm still on Nougat. I have no interest in Oreo, for this device.
The Analog Kid said:
Any hint up to which 8.0 security patch update will @Junior Passos method will work
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
I'm on August security patch.
Hey I am getting this error Current Account Cannot unlock this device everytime i try to unlock my Redmi 5A. I have tried every method mentioned on internet but still the same result. I contacted customer care and they said they had no solution. Someone please help me. Any method will do. I just want to unlock my phone at all costs. I'm even willing to pay for unlocking my device's bootloader. For the love of god someone plz help cause I'm at my wit's end now.
P.S. Don't try to tell me to follow method by @xcaanz because i dont know low lev prog language and there is no clear tutorial for that.
Device Specs: Redmi 5A -2, 16. Current Rom- MIUI 10 beta( 8.9.20) but i've tried to unlock on MIUI global stable 9.5 as well as 9.6.
I'm sorry it's xaacnz not xcaanz.
You have to register your xiaomi account for unlocking at http://en.miui.com/unlock/. The error you are getting means you are not registered.
oddhap said:
You have to register your xiaomi account for unlocking at http://en.miui.com/unlock/. The error you are getting means you are not registered.
Click to expand...
Click to collapse
I have already done that. No matter what i try i get the same error.
just stupid questions... i have read all of your posts and see you have read everything and tried everything. but its not absolutely clear... did you receive SMS confirmation? did you click on Find device and located your phone? did you solve the previous error 86012 cannot bind account? did you check the driver is shown as Xiaomi Corp? have you tried another usb cable or switched the port? tried with older version of Mi unlock tool? Developer options OEM unlocking box still greyed out at any time?
(just answer with yes, yes, yes)
---------- Post added at 22:27 ---------- Previous post was at 22:09 ----------
just some google results.. some of this (more ore less) claims there is a waiting period (hours .. days ..) which will increase.
https://forum.xda-developers.com/showthread.php?t=3565459
https://forum.xda-developers.com/showthread.php?t=3608650
http://en.miui.com/thread-1394024-1-1.html
http://xiaomitips.com/guide/how-to-fix-couldnt-verify-device-error-during-bootloader-unlock-process
https://www.allaboutxiaomi.com/unlock-bootloader-redmi-xiaomi-device
aIecxs said:
just stupid questions... i have read all of your posts and see you have read everything and tried everything. but its not absolutely clear... did you receive SMS confirmation? did you click on Find device and located your phone? did you solve the previous error 86012 cannot bind account? did you check the driver is shown as Xiaomi Corp? have you tried another usb cable or switched the port? tried with older version of Mi unlock tool? Developer options OEM unlocking box still greyed out at any time?
(just answer with yes, yes, yes)
---------- Post added at 22:27 ---------- Previous post was at 22:09 ----------
just some google results.. some of this (more ore less) claims there is a waiting period (hours .. days ..) which will increase.
https://forum.xda-developers.com/showthread.php?t=3565459
https://forum.xda-developers.com/showthread.php?t=3608650
http://en.miui.com/thread-1394024-1-1.html
http://xiaomitips.com/guide/how-to-fix-couldnt-verify-device-error-during-bootloader-unlock-process
https://www.allaboutxiaomi.com/unlock-bootloader-redmi-xiaomi-device
Click to expand...
Click to collapse
First- The process to apply is now simplified, so we no longer have to give a reason for unlocking on mi.com/unlock and it doesn't send u an SMS confirmation now. U just get the waiting time on mi unlock tool. Here is the thread-
http://en.miui.com/thread-246705-1-1.html
I get directed to download page directly after filling in my login credentials.
Yes, i clicked on find device and my device was located.
As for the error 86012, i have tried Plex VPN and many other VPNs and set the server to Hong Kong/ China but it did not work. Later i read on XDA that u can unlock even with error 86012.
Yes indeed. Checked that just now and the driver is shown as Xiaomi Corp.
No, I haven't tried another USB cable.
When i try with older version of Xiaomi unlock i can not login as it gives network error everytime.
No OEM unlock is not greyed out.
Hope u can help me now.
Thank you for this information, this link is the most useful from all the stuff i have read so far. Didn't know that no sms confirmation is required.
So, what happens if you enable OEM unlocking in Developer Options and then unlock in fastboot mode?
Code:
fastboot oem unlock
aIecxs said:
Thank you for this information, this link is the most useful from all the stuff i have read so far. Didn't know that no sms confirmation is required.
So, what happens if you enable OEM unlocking in Developer Options and then unlock in fastboot mode?
Code:
fastboot oem unlock
Click to expand...
Click to collapse
I'll give it a shot but i have read that it gives some sort of error.
Anyways thnx for ur time
In your Link, they mentioned a logfile /sdcard/MIUI/debug_log/*.zip, can you share this? see ...
Steps to reproduce the error: iv. Once the error message is shown, head towards dialer and dial *#*#284#*#*
Found a comment on this Video, maybe thats the reason for not working?
http://www.youtube.com/watch?v=AE4JhUbZ_LQ
"You need the original firmware that your phone is supposed to be shipped with to unlock the bootloader. If your device is a Chinese model it needs the China ROM, if it's the Global model it needs the Global ROM." (ChinaMobileMag)
aIecxs said:
Found a comment on this Video, maybe thats the reason for not working?
http://www.youtube.com/watch?v=AE4JhUbZ_LQ
"You need the original firmware that your phone is supposed to be shipped with to unlock the bootloader. If your device is a Chinese model it needs the China ROM, if it's the Global model it needs the Global ROM." (ChinaMobileMag)
Click to expand...
Click to collapse
My device is global version and i have MIUI 10 Global dev at present but I also tried unlocking at MIUI 9.5 which is the version Riva was shipped with. The result was still the same. Seriously idk what to do anymore. And yeah regarding that bug report, i gave not tried unlocking after i got the error Couldn't verify. I'll try once again to check if i'm getting some other error this time on unlock tool. But at present i don't have my Laptop so it might take a day or two. If u need the bug reoprt sooner do tell me. I'll upload it right away( I guess there's no point clinging to a small ray of hope now). Anyways thanks mate!!
aIecxs said:
In your Link, they mentioned a logfile /sdcard/MIUI/debug_log/*.zip, can you share this? see ...
Steps to reproduce the error: iv. Once the error message is shown, head towards dialer and dial *#*#284#*#*
Click to expand...
Click to collapse
Here's the bug report. I tried using command fastboot oem unlock again but it didn't work.
the logfile says CloudDeviceStatus stateCode 200 "ok" which means it has a successful connection to server, but then gives error device not found code 86012 description "设备不存在".
this may have different reasons (but i am not that expert):
a) the data on server is deleted - server fault?
b) access denied - account fault?
c) the device-id (or whatever they submit) election is empty or invalid - rom issue?
d) account is not binded to device?
Is this phone brand-new, do you still remember all accounts used from this device? Log-in to every single account and delete all binded devices, then use the very first account only. For my understanding only one account can be granted permission. Just try over and over again after 15 days - sorry i can not help
aIecxs said:
the logfile says CloudDeviceStatus stateCode 200 "ok" which means it has a successful connection to server, but then gives error device not found code 86012 description "设备不存在".
this may have different reasons (but i am not that expert):
a) the data on server is deleted - server fault?
b) access denied - account fault?
c) the device-id (or whatever they submit) election is empty or invalid - rom issue?
d) account is not binded to device?
Is this phone brand-new, do you still remember all accounts used from this device? Log-in to every single account and delete all binded devices, then use the very first account only. For my understanding only one account can be granted permission. Just try over and over again after 15 days - sorry i can not help
Click to expand...
Click to collapse
Bought the phone in August 2018. The account that im trying to unlock with is the acc. I created in this phone.
Thnx mate for ur help. I can not thank u enough for what u have done. Prior to this also i had created threads in MI community, asked for help in via posts in XDA thread but no one gave a damn about my problem. Thnx again for at least digging this deep in the problem.
You can send a email to customer support with subject unlocking: 设备不存在 and attach the filtered log file from my post - or even post this error again. You are clearly not the only one, this is a common problem. You can search in chinese forums, too. Please keep this thread updated, it will be helpful for others. I am facing this problem too, my son has Redmi 5a and i failed unlocking bootloader so the phone never was rooted, therefore has no TWRP and in case the screen will brake i don't know how to rescue data... at the moment for him best solution is "never touch a running system" and @xaacnz 's method is high risk for bricking we should better not try with daily driver
edit: post it on youtube channel too, or send a private message with invitation to your xda thread
http://www.youtube.com/watch?v=CiciDJfzlB8
aIecxs said:
You can send a email to customer support with subject unlocking: 设备不存在 and attach the filtered log file from my post - or even post this error again. You are clearly not the only one, this is a common problem. You can search in chinese forums, too. Please keep this thread updated, it will be helpful for others. I am facing this problem too, my son has Redmi 5a and i failed unlocking bootloader so the phone never was rooted, therefore has no TWRP and in case the screen will brake i don't know how to rescue data... at the moment for him best solution is "never touch a running system" and @xaacnz 's method is high risk for bricking we should better not try with daily driver
edit: post it on youtube channel too, or send a private message with invitation to your xda thread
http://www.youtube.com/watch?v=CiciDJfzlB8
Click to expand...
Click to collapse
Ok I will. Btw bout that yt channel, I just have to add a comment right? I'll create another thread on Mi forums about this problem. It really sucks not being able to unlock bootloader. TBH the only reason i bought this phone was because on searching the forums I found that this was the only device in my budget that had this many cusroms and other mods. I really am disappointed at how it turned out.
Hope we can find a solution soon!
aIecxs said:
Found a comment on this Video, maybe thats the reason for not working?
http://www.youtube.com/watch?v=AE4JhUbZ_LQ
"You need the original firmware that your phone is supposed to be shipped with to unlock the bootloader. If your device is a Chinese model it needs the China ROM, if it's the Global model it needs the Global ROM." (ChinaMobileMag)
Click to expand...
Click to collapse
"avoid flashing any firmware or any MIUI ROM which is older than what you're using now otherwise you'll brick your device"
[FAQ][Anti-Rollback] All your questions are answered here
aIecxs said:
"avoid flashing any firmware or any MIUI ROM which is older than what you're using now otherwise you'll brick your device"
[FAQ][Anti-Rollback] All your questions are answered here
Click to expand...
Click to collapse
Anti rollback is not related to this error. But i have tried with latest version of MIUI beta -8.9.20. It did not work. Also tried it on the latest global stable. Still no result.
Just heard that Riva has started receiving Oreo in china devepoper which means it will come to global very soon. I can only hope that this issue of "Current........this device" gets resolved after this major update. Fingers crossed.:fingers-crossed:
adityam0338 said:
Just heard that Riva has started receiving Oreo in china devepoper which means it will come to global very soon. I can only hope that this issue of "Current........this device" gets resolved after this major update. Fingers crossed.:fingers-crossed:
Click to expand...
Click to collapse
I strongly believe that you need to wait for a month at least before you can unlock your Redmi 5A again(unless you have done something that Xiaomi decided to lock it for good). I accidentally locked my bootloader after doing a"flash and lock" on the MIUI DEV rom, then unlocked 2nd time after 32+ days, while on the DEV Rom
Does anyone know if there’s any way to eliminate the Google warning message that pops up every time you boot up a Pixel phone once you have unlocked the phone’s bootloader? I just saw instructions for doing this on a Samsung phone and I’m just wondering if it’s also possible on my Pixel 2 XL.
just disable dm-verity
Using the Universal DM-Verity, ForceEncrypt, Disk Quota Disabler, which I found in an XDA forum, I disabled DM-Verity, but the Google boot up warning message is still displayed whenever the phone boots up. Either the script didn’t work or the warning message is not DM-Verity dependent.
Any additional help would be appreciated.
neilth said:
Using the Universal DM-Verity, ForceEncrypt, Disk Quota Disabler, which I found in an XDA forum, I disabled DM-Verity, but the Google boot up warning message is still displayed whenever the phone boots up. Either the script didn’t work or the warning message is not DM-Verity dependent.
Any additional help would be appreciated.
Click to expand...
Click to collapse
hex edit it
The warning message is independent of dm-verity and is triggered upon unlocking the bootloader. While hacking the bootloader to have the message not be displayed may be possible, that course of action could cause an unrecoverable brick. The easiest way to not have the message show is to lock the bootloader.
Thanks for the bad news.
neilth said:
Thanks for the bad news.
Click to expand...
Click to collapse
When the message comes up, tap your power button twice.
The first press pauses booting up, the second is to continue to booting up. I do this whenever I turn on or reboot my phone, and the message is gone in less than a second.
Thanks, I guess that’s about the best solution available.
neilth said:
Thanks, I guess that’s about the best solution available.
Click to expand...
Click to collapse
It's a minor inconvenience. When I say less than a second, I mean like a quarter second or so. Part of the sh*t you get with an unlocked bootloader. The phone is obviously in your hands already if you're seeing the warning message. Just double tap the power button and it'll boot up.
Back story here, I used to use HTC devices. When you went S-Off on them, you'd get a red warning that the build was for in house HTC development purposes only, and that sharing it could lead to legal consequences (lol). That warning stayed up for at least 15 seconds. Maybe 20. And there was no way to dismiss it.
I have a 2013 Google Nexus 7 with an unlocked bootloader and the only "warning" is the appearance of an open padlock at the bottom of the boot screen. Following this the Google legal department must have decided that the current warning message was needed to protect Google from potential lawsuits over possible security issues possibly caused by having an unlocked bootloader on any of their devices.
neilth said:
I have a 2013 Google Nexus 7 with an unlocked bootloader and the only "warning" is the appearance of an open padlock at the bottom of the boot screen. Following this the Google legal department must have decided that the current warning message was needed to protect Google from potential lawsuits over possible security issues possibly caused by having an unlocked bootloader on any of their devices.
Click to expand...
Click to collapse
I have the same tablet lol.
Yeah, the warning is probably for people who don't realize that there are vulnerabilities with having an unlocked bootloader. Most of us older Android enthusiasts already know this.
I don't know about lawsuits, but it's more along their line of being "secure". Not so long ago, Android was less secure than iOS. They have changed that with the Pixel line and the monthly updates.The warning is probably tied to that. idk
Strephon Alkhalikoi said:
The easiest way to not have the message show is to lock the bootloader.
Click to expand...
Click to collapse
This might be a stupid question, but is it possible to run Lineage with a locked bootloader so I can still use tap-to-pay features?
TheRealEdwin said:
This might be a stupid question, but is it possible to run Lineage with a locked bootloader so I can still use tap-to-pay features?
Click to expand...
Click to collapse
Not a stupid question. Yes you can. I don't think you'll be able to update it however, though I haven't tried.
TheRealEdwin said:
This might be a stupid question, but is it possible to run Lineage with a locked bootloader so I can still use tap-to-pay features?
Click to expand...
Click to collapse
Use a safetynet fix. Passing safetynet is usually all that's required. On LineageOS 20 rooted on a Pixel 5a and have all wallet, tap to pay, and problematic apps like Dasher working perfectly fine. Just have to re-flash my modified boot image after any OTA update
TheRealEdwin said:
This might be a stupid question, but is it possible to run Lineage with a locked bootloader so I can still use tap-to-pay features?
Click to expand...
Click to collapse
https://github.com/Displax/safetynet-fix/releases/tag/v2.4.0-MOD_1.2 is the Git for the modded version (by the same people) of the safetynet fix plugin. (the original version of the plugin didn't work for me personally HERE is the original) install this, let it reboot, then in magisk you want to go to settings > enable Enforce DenyList > Configure DenyList(under it) and select and apps that don't work.