Does the bootloader unlock timer run slow? - Xiaomi Mi 9 SE Questions & Answers

I applied for bootloader unlocking a while ago and it showed that i needed to wait 408 hours. I waited exactly 408 minutes which translates to 17 days. But when i tried unlocking after 17 days it still shows that i need to wait 243 more hours. Can someone please explain what is actually happening here cause its really frustrating.

Related

you have tried 8 times please wait to retry ???

i don't know what to do
i want to pay for sim unlocking the phone but i have this message "you have tried 8 times please wait to retry"
and i don't know what to do...is there any way to make the keyboard work i can't press nothing
please help me
Don't know why you tried guessing the SIM lock code... you can call your provider and get it for free.
I think it times out after 10-15 minutes...

problem with unlocking my artemis

hello i already got my unlock code for my phone but i can't enter it i have on screen
You have tried 10 times. please wait for retry
i kept it on charger for 2 days on without touching it as i know i can enter the code for a while but nothing happened
i flashed the phone with the same and difference operator roms and still the same
anyway to get out of this
Regards
This is just an idea, don´t know if it works but, did you try make a soft or hard reset? i will show you tried 10 times but may be let you enter the code.
Good luck
Same here 9 counters passed and I cannot enter code is there any other way to enter unlock code or by any soft please do reply.
thanks
bcnboy
Same problem:
''You have tried 7 times. Please wait for retry''
How long do I have to wait ???
It seemns nobody find a way to solve this. I payed for unlock code and now it's useless.

The "I can't update to Mango, My phone is bricked" thread.

Ok, here's a thread where those who are having difficulty upgrading to Mango should post so as to stay clear from the other "I have Mango" thread.
The format should be
Carrier
Phone Model
Updating from NODO/7004/7008
Force update(disconnect trick) or Official Zune notice?
Error Code
Problem Description: Eg, Phone hangs for 30 minutes at booting screen.
Ok, so my phone is now dead. I don't know what to do..
Carrier O2 UK
Phone Model HTC HD7
Updating from nodo to mango
Problem Description: I didn't get an error code. It froze on the update at step 8 or 9 (restarting the phone) and now will not boot. It vibrates 7 times and stays on the HTC logo screen.
Please help me
It was updating for over 3 hours.
---------- Post added at 12:30 AM ---------- Previous post was at 12:00 AM ----------
Please someone help me?
Carrier: Rogers (Canada)
Phone Model: Samsung Focus
Updating from 7390 (I guess, the one after NODO)
Error Code : none, stuck at step 8 "Restarting your phone"
Problem Description: Phone is frozen at the Samsung logo and nothing happens from there (been there for about 30 mins).
Mango update is quite meh for me here -_-
Carrier ORANGE CARAIBES
Phone Model HTC HD7
Updating from NODO TO MANGO
Error Code
Problem Description: Can't boot anymore. I don't even can turn on the phone :/ My first problem on windows phone!
Chasseur d'étoiles said:
Carrier: Rogers (Canada)
Phone Model: Samsung Focus
Updating from 7390 (I guess, the one after NODO)
Error Code : none, stuck at step 8 "Restarting your phone"
Problem Description: Phone is frozen at the Samsung logo and nothing happens from there (been there for about 30 mins).
Mango update is quite meh for me here -_-
Click to expand...
Click to collapse
just wanted to remind everybody that those of use who went from NoDo to RTM had varied times for the updates, some people reported more than an hour at the boot logo until it continued. After two hours I'd say something is wrong.
A hard reset might bring it to back (loosing all info of course). That in fact worked for me in the first update state going from NoDo to 7661 beta. I thought I bricked my phone, but it came back after a cold boot/hard reset.
derausgewanderte said:
just wanted to remind everybody that those of use who went from NoDo to RTM had varied times for the updates, some people reported more than an hour at the boot logo until it continued. After two hours I'd say something is wrong.
A hard reset might bring it to back (loosing all info of course). That in fact worked for me in the first update state going from NoDo to 7661 beta. I thought I bricked my phone, but it came back after a cold boot/hard reset.
Click to expand...
Click to collapse
My phone was updating for collectively updating for three hours. At least two of those it was stuck on the boot screen. I've tried resetting it (holding both volume keys when turning it on) and nothing works. Microsoft's support page said to disconnect if it freezes..
mdjmurray said:
My phone was updating for collectively updating for three hours. At least two of those it was stuck on the boot screen. I've tried resetting it (holding both volume keys when turning it on) and nothing works. Microsoft's support page said to disconnect if it freezes..
Click to expand...
Click to collapse
a hard reset on mine worked by pushing down power button, camera button and both vol plus and minus at the same time while the phone booted. I unplugged the battery, plugged it back in and then get the timing right to push the buttons down. Good luck.
Dead HTC Surround..
In the same boat as others. Phone stuck between steps 8 & 9, no phone won't turn on at all. Hard reset won't work. Acts like the battery is completely dead and USB port doesn't work. No lights, no beeps.. dead. Ugh.
Never installed any hacks, ROMs etc. I was 100% normal updates. Very frustrating...
This was actually my third attempt to install the updates. Previous times it had froze I was able to do a hard reset and restore the backup.
Anyone have suggestions? I've pulled the battery and it hasn't made any difference.
bbrian said:
In the same boat as others. Phone stuck between steps 8 & 9, no phone won't turn on at all.
Click to expand...
Click to collapse
This happened to my Omnia 7 while doing the final restart. It got stuck on the 'Samsung Omnia 7' logo for about 15 minutes. I just hit the home button and it finished booting.....problem solved.
Ok. Did you guys forced the update or waited for the official notification?
i got a message on my cell about it so i upgraded i i got a sdamsun focus v1.4
Carrier: AT&T
Phone Model: Samsung Focus
Updating from NODO
Force update(disconnect trick)
Error Code C1010009
Problem Description: It got through the friends and family update, then when it tries to update to Mango I get error C1010009 each time. I've tried this on multiple PCs with the same exact outcome. I went through the suggested MS troubleshooting steps and tried the Fix It thing to no avail, Fix It says nothing is wrong. Any suggestions?
VoodooKing said:
Ok, here's a thread where those who are having difficulty upgrading to Mango should post so as to stay clear from the other "I have Mango" thread.
The format should be
Carrier
Phone Model
Updating from NODO/7004/7008
Force update(disconnect trick) or Official Zune notice?
Error Code
Problem Description: Eg, Phone hangs for 30 minutes at booting screen.
Click to expand...
Click to collapse
tamcdonald said:
Carrier: AT&T
Phone Model: Samsung Focus
Updating from NODO
Force update(disconnect trick)
Error Code C1010009
Problem Description: It got through the friends and family update, then when it tries to update to Mango I get error C1010009 each time. I've tried this on multiple PCs with the same exact outcome. I went through the suggested MS troubleshooting steps and tried the Fix It thing to no avail, Fix It says nothing is wrong. Any suggestions?
Click to expand...
Click to collapse
Ok you may want to try to wait for the official notice to pop up. There is a reason why but I used to get that error when I changed my carrier code. A while back there was a Samsung firmware update being pushed down to some carriers that my carrier hadn't released yet. So I changed my carrier code to force the update. The update downloaded but did not manage to install and giving me that error code. I reverted to my original carrier code and a week later, My phone notified me of the same update and successfully installed it.
I believe that nobody is meant to do the disconnect trick and its best to just wait for the official update notice.
It almost seems like some kind of driver issue. After Zune updated it detected a new device and Windows said it installed it ok, the phone works fine in every other way as far as syncing with Zune etc. Device manager says the device is working properly, but when specifically trying to transfer the Mango update it refuses. Weird.
Edit: I fixed it. After reading your post about carrier codes, I starting poking around and rebranded my phone to ATT-US. After that Mango installed no problem.
VoodooKing said:
Ok you may want to try to wait for the official notice to pop up. There is a reason why but I used to get that error when I changed my carrier code. A while back there was a Samsung firmware update being pushed down to some carriers that my carrier hadn't released yet. So I changed my carrier code to force the update. The update downloaded but did not manage to install and giving me that error code. I reverted to my original carrier code and a week later, My phone notified me of the same update and successfully it.
I believe that nobody is meant to do the disconnect trick and just wait for the official update notice.
Click to expand...
Click to collapse
tamcdonald said:
It almost seems like some kind of driver issue. After Zune updated it detected a new device and Windows said it installed it ok, the phone works fine in every other way as far as syncing with Zune etc. Device manager says the device is working properly, but when specifically trying to transfer the Mango update it refuses. Weird.
Edit: I fixed it. After reading your post about carrier codes, I starting poking around and rebranded my phone to ATT-US. After that Mango installed no problem.
Click to expand...
Click to collapse
That's good to know. Now we know one of the causes for the error message. Mine is unbranded 000-88.
bricked focus
Carrier AT&T
Phone:: Samsung Focus v1.3
Updating from 7390
Force Update Disconnecting trick
Error cod:e none froze during step 8 or 9 phone restart phase of 7392 update
Problem: My phone will not move past the AT&T orange world phone screen. I have hard reset the phone numerous times both without SD card and with. Have followed all the steps to what i have seen posted do far. Not really sure what to do now. I have entered it into the download mode twice the first time for over 30 minutes the second time around 20 or so. What would be next step if there is one?
Hi i have i an unuseal problem my phone is htc 7 mozart and in about it says hardware revision NA radio hardware version 0.0.0.0 and when i boot to bootloader mode in the red colour it says something like chinese.Now i am in mango.Why it says that???
{sorry for my english i am from greece}
depdereck said:
Carrier AT&T
Phone:: Samsung Focus v1.3
Updating from 7390
Force Update Disconnecting trick
Error cod:e none froze during step 8 or 9 phone restart phase of 7392 update
Problem: My phone will not move past the AT&T orange world phone screen. I have hard reset the phone numerous times both without SD card and with. Have followed all the steps to what i have seen posted do far. Not really sure what to do now. I have entered it into the download mode twice the first time for over 30 minutes the second time around 20 or so. What would be next step if there is one?
Click to expand...
Click to collapse
How long did it get stuck at the operator screen? I have seen reports of 15mins before the phone boots again.
aggelosss5 said:
Hi i have i an unuseal problem my phone is htc 7 mozart and in about it says hardware revision NA radio hardware version 0.0.0.0 and when i boot to bootloader mode in the red colour it says something like chinese.Now i am in mango.Why it says that???
{sorry for my english i am from greece}
Click to expand...
Click to collapse
Is your phone still working after the update? What are the version numbers? You can check in Settings > About
VoodooKing said:
How long did it get stuck at the operator screen? I have seen reports of 15mins before the phone boots again.
Click to expand...
Click to collapse
It gets stuck there for a long time longest i let it sit there before trying another reset was about 45 minutes or so. I got Zune to recognize my phone and start a restore but it stopped again at the phone restart and sat there for about 30 minutes. I had to exit out to leave work and head home. I also tried to recover the phone with the Windows Phone Support Tool but that timed out at the restart as well and gave me an error code of 800004005.

Can´t boot after flash rom

Boas. I installed a rom but at first did not even read the part where it says that the 1st boot may take between 2 to 3 hours, so badly spent 15min I found it strange the delay and hung up the equipment.
Now every time I start it says "Sony" and is always so.
They think they did something wrong or do I have to wait for those 3 hours?
What can I do to resolve this?
It's that I can not get into Recovery.
Cumps
What rom have you tried to flash?(pls add the threadlink) Have you unlocked your bootloader?
catumilo said:
Boas. I installed a rom but at first did not even read the part where it says that the 1st boot may take between 2 to 3 hours, so badly spent 15min I found it strange the delay and hung up the equipment.
Now every time I start it says "Sony" and is always so.
They think they did something wrong or do I have to wait for those 3 hours?
What can I do to resolve this?
It's that I can not get into Recovery.
Cumps
Click to expand...
Click to collapse
Reflash kernel or flash some other
Send from My ARC
catumilo said:
Boas. I installed a rom but at first did not even read the part where it says that the 1st boot may take between 2 to 3 hours, so badly spent 15min I found it strange the delay and hung up the equipment.
Now every time I start it says "Sony" and is always so.
They think they did something wrong or do I have to wait for those 3 hours?
What can I do to resolve this?
It's that I can not get into Recovery.
Cumps
Click to expand...
Click to collapse
If you have a locked bootloader, you'll need to reflash stock rom using flashtool. If you want to discuss this in portuguese send me a PM.

I can't unlock the bootloader by the official way

About two weeks ago I acquired the device and immediately started the unlocking process, but today after completing the regulatory waiting time, the timer was restarted indicating that I should wait another 360 hours again.
Is there any other way to unlock the device bootloader without having to wait again?
KevinSYB said:
About two weeks ago I acquired the device and immediately started the unlocking process, but today after completing the regulatory waiting time, the timer was restarted indicating that I should wait another 360 hours again.
Is there any other way to unlock the device bootloader without having to wait again?
Click to expand...
Click to collapse
Nope there is no workaround. And no, timer shouldnt reset unless you tried cheating it, like binding different account to your device or stuff like that. Generally, you just press unlock, then you recieve a message you have to wait 360h. You wait 360h, then press unlock again and you are done.

Categories

Resources