Related
Hello! I've read that LG Panther have an update which supports copy/paste, but zune writes me that my phone is up to date (my current build is 7003). I've tried to change a region and tried to sign in using different accounts, but that was hopeless... Any opinion?
proplayer666 said:
Hello! I've read that LG Panther have an update which supports copy/paste, but zune writes me that my phone is up to date (my current build is 7003). I've tried to change a region and tried to sign in using different accounts, but that was hopeless... Any opinion?
Click to expand...
Click to collapse
I've heard the same thing, and as far as I know, it's not going out via Zune (I've not got it, or seen it on either a Taylor or a Panther). I think we'll just have to wait...
Same here. My zune and phone both don't detect updates.
fb401 said:
Same here. My zune and phone both don't detect updates.
Click to expand...
Click to collapse
I think regularly checking the Connect site might be the best option for finding new builds.
l3v5y said:
I think regularly checking the Connect site might be the best option for finding new builds.
Click to expand...
Click to collapse
Microsoft Connect? I've tried to search there and failed...
proplayer666 said:
Microsoft Connect? I've tried to search there and failed...
Click to expand...
Click to collapse
The update isn't there yet, but I suspect it'll go there before anywhere else.
i've searched in google about this and understood that zune must flash this update, but it haven't caused. I think a special version of zune exists (not 4.7).
proplayer666 said:
i've searched in google about this and understood that zune must flash this update, but it haven't caused. I think a special version of zune exists (not 4.7).
Click to expand...
Click to collapse
I very much doubt you'll find an update, and I'm even more sceptical that it'll be on Zune. 4.7 is the latest version I know of, there might be some linking to Live IDs, or maybe only some devices/LiveIDs get the update.
Hello All,
I just wanted to chime in and say that I also have a GW910 and it also claims to be 100% up-to-date on version 7.0.7003.0
I just wondered if you lot all think that we will even get the update in 2011 at all.
Also... do any of you know what will happen regarding firmware updates (radio etc)?
I ask because I have a problem here in Luxembourg where my phone loses connection to HTTPS sites after a while. It can still connect to the internet but to anything related to HTTPS (SSL etc).
I know that it isn't a fault with the phone itself (Hardware) because it only happens when I am travelling around and my phone has to change between 3G and Edge quite often. It I stay at home, there is no problem at all.
Comments anyone??
nebc100 said:
Hello All,
I just wanted to chime in and say that I also have a GW910 and it also claims to be 100% up-to-date on version 7.0.7003.0
I just wondered if you lot all think that we will even get the update in 2011 at all.
Also... do any of you know what will happen regarding firmware updates (radio etc)?
I ask because I have a problem here in Luxembourg where my phone loses connection to HTTPS sites after a while. It can still connect to the internet but to anything related to HTTPS (SSL etc).
I know that it isn't a fault with the phone itself (Hardware) because it only happens when I am travelling around and my phone has to change between 3G and Edge quite often. It I stay at home, there is no problem at all.
Comments anyone??
Click to expand...
Click to collapse
I think we probably will get an update, there's not much point having developer hardware if we're developing on software that's out of date.
Radio updates etc I'm less sure about, my Taylor says the radio is from August, though the OS is much more recent.
That sounds like an issue with the general OS, and it may be being patched anyway, I'd see if you can submit that as a bug (via Connect) or via the on device feedback mechanism (can't remember how to access it, but I remember it being there).
According to this thread http://forums.create.msdn.com/forums/t/77100.aspx, no dev phones will be updated.
fb401 said:
According to this thread http://forums.create.msdn.com/forums/t/77100.aspx, no dev phones will be updated.
Click to expand...
Click to collapse
and what about mango? also no update?
screamer333 said:
and what about mango? also no update?
Click to expand...
Click to collapse
You need NoDo in order to get Mango, so no. I still have my Panther, I'm just waiting on the next batch of hardware this fall so I can change over.
I found a copy of the ChevronWP7.Updater and was able to update my pre-release LG GW910 build 7004 to NoDo. After I did that I was able to install Mango beta 2.
cmcginnis said:
I found a copy of the ChevronWP7.Updater and was able to update my pre-release LG GW910 build 7004 to NoDo. After I did that I was able to install Mango beta 2.
Click to expand...
Click to collapse
How did you get to 7004, I can read on my phone that I am on 7003.
cedtat said:
How did you get to 7004, I can read on my phone that I am on 7003.
Click to expand...
Click to collapse
Here is how I was able to get Mango installed on my pre-release developer phone (LG GW910).
NOTE: These directions are slightly modified to work as if you were starting from build 7004 (maybe 7003). After I the Chevron update I to install Mango beta 2 but received a 80180048 error. I used the backup that was created to get it back to the state just prior to the Mango update process.
The steps I took starting out with build 7004.
Run the ChevronWP7.Update twice to bring the phone up to build 7390 (NoDo)
Use the "Walshed" Phone support tool to put the device in a state where it can receive official updates - http://blog.walshie.me/walshed-phone-support-tool-official-fix-to-get-you-back-on-track
Be sure to follow the instructions and select ALL of the languages the keyboard supports.
Then following the Mango beta 2 installation instructions.
Mango beta 2 should install without any issues.
IMPORTANT: Uninstalling the Zune software will DELETE your backup. I created a RAR archive of the backup but kept it in the same folder and everything was wiped out.
cmcginnis said:
Here is how I was able to get Mango installed on my pre-release developer phone (LG GW910).
NOTE: These directions are slightly modified to work as if you were starting from build 7004 (maybe 7003). After I the Chevron update I to install Mango beta 2 but received a 80180048 error. I used the backup that was created to get it back to the state just prior to the Mango update process.
The steps I took starting out with build 7004.
Run the ChevronWP7.Update twice to bring the phone up to build 7390 (NoDo)
Use the "Walshed" Phone support tool to put the device in a state where it can receive official updates - http://blog.walshie.me/walshed-phone-support-tool-official-fix-to-get-you-back-on-track
Be sure to follow the instructions and select ALL of the languages the keyboard supports.
Then following the Mango beta 2 installation instructions.
Mango beta 2 should install without any issues.
IMPORTANT: Uninstalling the Zune software will DELETE your backup. I created a RAR archive of the backup but kept it in the same folder and everything was wiped out.
Click to expand...
Click to collapse
Hello,
I have tried what you say, but sadly the ChevronWP7.unlocker doesn't seem to work.
I get the Black screen where is asks what language, and whatever I select the screen simply closes.
What OS did you use? Was it a 64bit OS or 32bit OS?
I want to try it again, but at the moment I am stuck.
Thanks
nebc100
P.S. would you be willing to send me a copy of the ChevronWP7.unlocker that you used?
If so PM me, and I will send you my e-mail address.
nebc100 said:
Hello,
I have tried what you say, but sadly the ChevronWP7.unlocker doesn't seem to work.
I get the Black screen where is asks what language, and whatever I select the screen simply closes.
What OS did you use? Was it a 64bit OS or 32bit OS?
I want to try it again, but at the moment I am stuck.
Thanks
nebc100
P.S. would you be willing to send me a copy of the ChevronWP7.unlocker that you used?
If so PM me, and I will send you my e-mail address.
Click to expand...
Click to collapse
If you have tried it, disconnect your phone, reboot it, then connect it and wait for Windows to tell you the device has been correctly installed (if that hasn't happened yet). Then try ChevronWP7.Update again.
I used the 64-bit version. I'll find and post the link I used to download the app.
cmcginnis said:
If you have tried it, disconnect your phone, reboot it, then connect it and wait for Windows to tell you the device has been correctly installed (if that hasn't happened yet). Then try ChevronWP7.Update again.
I used the 64-bit version. I'll find and post the link I used to download the app.
Click to expand...
Click to collapse
There seems to be a misunderstanding in your communication. It seems as if you had a Panther that already HAD 7004 loaded on to it, which allowed you to updated all the way to post-Nodo.
There is currently no way possible for the Chevron Updater to bring a 7003 Panther up to 7004. Useless Guy even opened up the source code and tried to force the program into update his device and it did not work.
fb401 said:
There seems to be a misunderstanding in your communication. It seems as if you had a Panther that already HAD 7004 loaded on to it, which allowed you to updated all the way to post-Nodo.
There is currently no way possible for the Chevron Updater to bring a 7003 Panther up to 7004. Useless Guy even opened up the source code and tried to force the program into update his device and it did not work.
Click to expand...
Click to collapse
I am sorry if I did not communicate that correctly. Yes, I started with a Panther which already had build 7004 on it.
Here goes the story
I have an HD7 from Bell Mobility and unlocked as soon as i got it with chevron unlocker. Updated officially to pre-NoDo with phone still unlocked as usual.
Then just about a week ago i got impatient and flashed my phone with custom NoDo rom which was working fine without any issue.
After reading alot about the possibility of still having an unlocked (with work aound)phone after Updating through Zune. I decided to flash back the original rom from Bell (7004).
Issue is after flashing, i tried unlocking using chevron unlocker but it does not work and i get this error message (attached).
I have tried all the trouble shooting i can find here and through googling still same error message
Anyone have this problem and what is the solution to getting my phone unlocked again.
thanks
redoxy said:
Here goes the story
I have an HD7 from Bell Mobility and unlocked as soon as i got it with chevron unlocker. Updated officially to pre-NoDo with phone still unlocked as usual.
Then just about a week ago i got impatient and flashed my phone with custom NoDo rom which was working fine without any issue.
After reading alot about the possibility of still having an unlocked (with work aound)phone after Updating through Zune. I decided to flash back the original rom from Bell (7004).
Issue is after flashing, i tried unlocking using chevron unlocker but it does not work and i get this error message (attached).
I have tried all the trouble shooting i can find here and through googling still same error message
Anyone have this problem and what is the solution to getting my phone unlocked again.
thanks
Click to expand...
Click to collapse
try install the certificate again to see if works
jgcaap said:
try install the certificate again to see if works
Click to expand...
Click to collapse
tried that again but still same error message
thanks anyway
redoxy said:
tried that again but still same error message
thanks anyway
Click to expand...
Click to collapse
Did you also switch your phone off and back on and then try to unlock? My experience is that certificates only work after restarting the phone.
Heathcliff74 said:
Did you also switch your phone off and back on and then try to unlock? My experience is that certificates only work after restarting the phone.
Click to expand...
Click to collapse
Yep did that also. and not just once but multiple times.
Wonder why this is happening
redoxy said:
Yep did that also. and not just once but multiple times.
Wonder why this is happening
Click to expand...
Click to collapse
I've came across this error little while back as I tend flash back and forth, was at a loss until I did the following:
Navigate to c:\windows\system32\drivers\etc\ then open hosts with notepad and delete any references to windowsphone developer services
Note: as it's system file you may need to take ownership otherwise you will not be able to edit it!
hope this helps you!
gfreek said:
I've came across this error little while back as I tend flash back and forth, was at a loss until I did the following:
Navigate to c:\windows\system32\drivers\etc\ then open hosts with notepad and delete any references to windowsphone developer services
Note: as it's system file you may need to take ownership otherwise you will not be able to edit it!
hope this helps you!
Click to expand...
Click to collapse
Did Exactly as you instructed and it worked.
thanks
Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. I have been trying to unlock this phone for 2 days now!
Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well my code is 16 numbers long. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same.
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.
Tread3r said:
Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. For purposes of convenience and time (I have been trying to unlock this phone for 2 days now!) I will post my IMEI code here ( 3529000059203526 ) and the unlock code given to me by sony through email (61CAA387DC11C4CF).
I hope this doesnt break any rules or anything.
I am doing this to see if anyone here can help me. Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well as you can see my code is 16 numbers long, so in effect I only entered up to number "5". I would like to know if anyone is willing to test my IMEI and see if they get the same code. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key, this is why I am posting. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same (as above).
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.
Click to expand...
Click to collapse
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Thanks for the advice, I will edit it ASAP.
abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Hey he removed the imei number from his original message but that's pointless unless u remove it from your quote
Sent from my Xperia S using xda app-developers app
I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967
Chriszo said:
I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967
Click to expand...
Click to collapse
Glad to hear im not alone . No I still haven't found a way to unlock it. Sorry for asking but what does "PN" mean? Just so we are clear.
Ok thanks for your answer. No problem, but its just a mistake. Correctly it should be "PM" for personal message. I thought you would write on this way so I cant read any reasults
UPDATE:
I have tried other processes that all have the same steps, be it they were simplified programs with GUI's. I have come to the conclusion that my fastboot driver was installed incorrectly, because the first time I installed it on my phone I was able to see the S1 bootloader icon on device manager and I was able to click on it fast enough to enable it to install the driver. And correct me if im wrong but when we press UP on the volume rocker on our XS's and connect it to the USB we should see a blue right light? Well that is what happens when I do it so I assume I installed it correctly then.
Now after these first few failed attempts at unlocking I got frustrated and just factory reset my phone, completely ( I made back ups of course). This time however I used a program which is suppose to install all the drivers and simplify the whole unlocking process, I dont remember what program exactly, i'll check my files and get back to you guys on that.
Again it failed, showing the FAILED ("oem" error message) so I checked the steps from Doomlords guide and re checked my device manager. This time when I connect my phone it doesnt show the S1 bootloader icon on Dev manager, instead it shows "android phone ADB Interface". BUT I still get the blue LED when I connect my phone via USB, so does that mean I have fastboot on my phone again? ( I assume I do because the program I used says it did install it correctly and it even showed the "install anyway" window)
I am almost loosing all hope to unlock my XS , maybe I got a lemon phone or did something wrong again. I am willing to do another factory reset and restart the whole process again. This time I will follow every single step on the official website and see what happens.
But before I do that I want to ask, does anyone know of any news or whereabouts for an unofficial unlock bootloader process? I know its a long shot because we already have an official way but as from recent experience it doesnt work 100% of the time.
Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/
Chriszo said:
Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/
Click to expand...
Click to collapse
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.
Tread3r said:
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.
Click to expand...
Click to collapse
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).
It was AOKP, the advanced project for this device.
I think your right, but in how far is the bootloader linked to the needed kernel? And why cant the bootloader be unlocked several times...?
Of course the kernel is a main part of the rom, but without an unlocked bootloader even the kernel would not be accepted by the bootloader. Thats the problem with other firmwares/ roms why you have to unlock it
I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?
razormc said:
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).
Click to expand...
Click to collapse
I am using Windows 7 and I have used flashtool. I believe the drivers are correct because,as you said, the blue LED does show and stay while I fastboot my phone. Same goes for the green LED when I go to flashboot.
Chriszo said:
I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?
Click to expand...
Click to collapse
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve
Tread3r said:
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve
Click to expand...
Click to collapse
First, unlock your bl. Then root. I done that on my old Arc S and it works great.
Sent from my LT26i using xda developers-app
@ Tread3r:
Yes the drivers are installed correctly, because the phone starts into fastboot and flashboot with each the right light.
Thats the great problem with our devices. I did it nearly the same way and Ive got a similar problem, as the first answers describe in this post. Actual the original stock rom is installed on my Sony and all works correctly, but its just a short-term workaround
The bootloader unlockind process still end in an error message and that is my problem.
@ Vatih:
Nice try, but this is our problem... :/
---------- Post added at 11:41 AM ---------- Previous post was at 10:57 AM ----------
I cant believe it myself, but the alternative way works, althought I cant read anythink in the tool because of the language...
I've got the superuser app and root permissions and all works.
This link helped me: http://forum.xda-developers.com/showthread.php?p=39498268
It's the tool for the "new" firmware, .55, the latest from sony.
Hope, its also succesfully with your devices
I solved our problem. My bootloader is now open
I did it with the unlock, flashtool tool of this forum that helps you to open the bootloader and flash kernels and roms.
http://forum.xda-developers.com/showthread.php?t=2087337
Seems like just the code was wrong.
It worked with the first try
But be careful, although its just the bootloader, all data will be deleted. My phone is empty again :/ Of course I've got some backups...
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
I did the oem unlock thing in dev options, but upon putting in any commands, it simply tells me that the command doesn't exist essentially. No idea what I'm doing wrong, I think nothing. Was there a patch or something that removed this command?
idk what happened but redownloading fastboot/adb files and stuff allowed me to unlock it.
ClubSpade12 said:
idk what happened but redownloading fastboot/adb files and stuff allowed me to unlock it.
Click to expand...
Click to collapse
This usually happens if you haven't updated your platform tools in awhile or since you switched phones. It is generally a good idea to update the platform tools every few months or at least whenever there's a new android version available. Glad you're all set.