I have requested the unlock via the miunlocker and got the 360 hours wait message.
Does the phone automatically unlock after this time frame? do I get a notification?
Do I have to run the unlocker again after 360 hours?
does the phoen have to remain on for 360 hours or could I switch it off for 2 weeks?
most importantly - can I remove the simcard from the phone and use in another phone whilst waiting?
As I need a phone for work, with my work emails and apps, so instead of reinstalling on a miui rom, and then wiping and reinstalling again I can simply use my old phone
t3rm3y said:
I have requested the unlock via the miunlocker and got the 360 hours wait message.
Does the phone automatically unlock after this time frame? do I get a notification?
Do I have to run the unlocker again after 360 hours?
does the phoen have to remain on for 360 hours or could I switch it off for 2 weeks?
most importantly - can I remove the simcard from the phone and use in another phone whilst waiting?
As I need a phone for work, with my work emails and apps, so instead of reinstalling on a miui rom, and then wiping and reinstalling again I can simply use my old phone
Click to expand...
Click to collapse
You need to connect to the computer and use the unlock program to unlock it.
It does not have to remain on for the unlock wait period. Does not need a sim installed either.
goofball2k said:
You need to connect to the computer and use the unlock program to unlock it.
It does not have to remain on for the unlock wait period. Does not need a sim installed either.
Click to expand...
Click to collapse
Thanks. So after 15 days I connect it back up and run the unlock again?
I just don't want to wait that long and donut wrong and get the same message...
t3rm3y said:
Thanks. So after 15 days I connect it back up and run the unlock again?
I just don't want to wait that long and donut wrong and get the same message...
Click to expand...
Click to collapse
yes, you can connect up and run the unlocking tool after your timer is up.
Related
Went to flash the new Marshmallow Stock rom and flashed what I thought was it. Until I go to reboot and my phone won't turn on. Flashed the rom from Here, not noticing that it's for the International variant of the g3. Is there a way to fix this without having to take it back to tmobile?
Bump. I just want to be able to at least get back into twrp, I have backups made...
Naturesretard said:
Bump. I just want to be able to at least get back into twrp, I have backups made...
Click to expand...
Click to collapse
So I assume you can't enter TWRP?
Does your pc recognize your phone?
Elanduir said:
So I assume you can't enter TWRP?
Does your pc recognize your phone?
Click to expand...
Click to collapse
Nope. Phone won't turn on and PC doesn't really recognize it like it usually did. Phone won't turn on or anything, so I can't get into twrp or download mode. Found This thread to try and get it responsive. I can't seem to short the pins correctly
Managed to finally short the wires, but the phone wouldn't go very far. It kept throwing up errors about "waiting for the device to connect in flash prg". I gave up and decided to just wait for the phone they said I'd get today due to overnight shipping; it never got shipped that day when I made the call at 1pm, so now i have to wait an extra day.
My phone is gone into LOOPMODE only showing GOOGLE , and no OEM enabled , no USB debugging Enabled also DEVICE state is LOCKED...
please help me to restore my set.
how to Unlock the bootloader or how to enable USB debugging ?
From the reading that I have done, if the device state is locked you are in a bad way.
I have almost had success freezing my phone down to -18C, it will then complete the boot process but reboots before I can get into turn on OEM unlocking in the settings.
I am going to try and boot the phone whilst it is disassembled and use some freeze spray to keep it cool, in a couple of days when I have some free time.
First off , thankyou for replying
sconno said:
From the reading that I have done, if the device state is locked you are in a bad way.
I have almost had success freezing my phone down to -18C, it will then complete the boot process but reboots before I can get into turn on OEM unlocking in the settings.
I am going to try and boot the phone whilst it is disassembled and use some freeze spray to keep it cool, in a couple of days when I have some free time.
Click to expand...
Click to collapse
yeah sure, i m on HOLD , i have tried all things such as adb, nexus toolkit and all adb commands .
Reply soon bro !
Freezing you phone is nonsense and won't do anything for a software problem!
What you need to do is unlock the bootloader again. (do a search for howto do this)
And then give the adb command to format userdata! ("fastboot format userdata") This will wipe any encryption on the phone that's blocking further acces.
The next step is to download the lastest OTA and sideload it through adb. This will unconditionally write a clean stock ROM on your phone and you should be good to go.
MIND THAT THIS WILL WIPE EVERYTING ON YOUR PHONE!!!
r3act said:
Freezing you phone is nonsense and won't do anything for a software problem!
What you need to do is unlock the bootloader again. (do a search for howto do this)
And then give the adb command to format userdata! ("fastboot format userdata") This will wipe any encryption on the phone that's blocking further acces.
The next step is to download the lastest OTA and sideload it through adb. This will unconditionally write a clean stock ROM on your phone and you should be good to go.
MIND THAT THIS WILL WIPE EVERYTING ON YOUR PHONE!!!
Click to expand...
Click to collapse
but how to unlock bootloader , thats the problem bro ! i have done evrytthing to do so !
OK, so after trying to get my phone to boot for the past 3 days, I have finally done it and enabled the OEM unlock option.
I am running bullhead 7.1.2
1. Put phone in freezer at -18C for about 30 minutes.
2. Plugged phone into USB, pressed the power button and it then finally booted all the way.
3. Went into settings
4. Enabled developer options
5. Went into developer options and enabled OEM unlock. (I had to enter my pin number to make this happen)
I can now access the device using adb and device in no longer locked.
sconno said:
OK, so after trying to get my phone to boot for the past 3 days, I have finally done it and enabled the OEM unlock option.
I am running bullhead 7.1.2
1. Put phone in freezer at -18C for about 30 minutes.
2. Plugged phone into USB, pressed the power button and it then finally booted all the way.
3. Went into settings
4. Enabled developer options
5. Went into developer options and enabled OEM unlock. (I had to enter my pin number to make this happen)
I can now access the device using adb and device in no longer locked.
Click to expand...
Click to collapse
but i think my Android is corrupt , it showing only google when i press and hold the power button.
give me another solution bro !
And anyone from MUMBAI (BORIVALI WEST)
Try this. It worked for me on 2 devices.
https://hackaday.com/2017/02/11/nexus-5x-phone-resurrected-by-the-oven/
harihacker said:
Try this. It worked for me on 2 devices.]
Thanks for this, I am going to give this a go with a heat gun later on today.
Click to expand...
Click to collapse
harihacker said:
Try this. It worked for me on 2 devices.
https://hackaday.com/2017/02/11/nexus-5x-phone-resurrected-by-the-oven/
Click to expand...
Click to collapse
lol , I think my Phone is dead RIP .
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.
Good morning,
I'm writing this post 'cause I'd like to know if it's a possibility to "unlock", if I can say this, my phone. My company installs on my phone VMware Hub and the Debug USB is locked because I cannot unlock the related menu. I've tried to format the phone from original recovery by wiping data and nothing changed. So, I've run my phone into bootloader in order to overwrite the original firmware with a new original one. The process is ok but when I restart my phone, VMware is installed and configured.
Now, a question, is it possible to remove it withouth root or debug USB? I'm so annoyed because it is possible to check everything I do in my phone
Did someone answer you? I have the same problem.
Thanks.
Hello, sorry for such late reply been way for too long, the answer is simple, go to developer options, select the oem unlock option reboot the phone to download or recovery i don't remember, a message will come before that will alow you to unlock bootloader, precede to unlock, i can't recall if the phoene will reset but i assume so, when it comes back it will no longer be tied to your employer, it will be an A50 like any other bougt on the store, keep in mind that from then foword you will get a message saying that bootloader is unlocked at phone power on, that's it
Hi, I'm new to XDA. I am trying to get a rooted device so I can play around with it and do cool things. After trying 4 different phones and weeks of nonstop research and attempts, I decided to an Amazon Fire 8 Plus (10th Generation). I know how to unlock bootloader using windows 10 and android sdk. The one problem is that I can't enable OEM unlocking. When I tried fastboot flashing unlock anyway, my tablet got stuck in fastboot mode. Basically, what happens is, I turn it on, nothing suspicious there, but after I confirm it when I get the warning message, it INSTANTLY turns back off. Tinkering around with date and time, software updates, rebooting, and toggle developer options did nothing. I even went as far as disabling the lock screen so it doesn't make me enter my pin when I try to turn it on - still nothing! I am very desperate and tired of all this rooting, it would be nice to get some help!
Also, I think I can use this video
to root if I figure out to get to that temp directory command thing the guy entered. I use windows ten, but can't find how to get to that place.
An answer to either question would be much appreciated, thanks!
Zeek347 said:
Hi, I'm new to XDA. I am trying to get a rooted device so I can play around with it and do cool things. After trying 4 different phones and weeks of nonstop research and attempts, I decided to an Amazon Fire 8 Plus (10th Generation). I know how to unlock bootloader using windows 10 and android sdk. The one problem is that I can't enable OEM unlocking. When I tried fastboot flashing unlock anyway, my tablet got stuck in fastboot mode. Basically, what happens is, I turn it on, nothing suspicious there, but after I confirm it when I get the warning message, it INSTANTLY turns back off. Tinkering around with date and time, software updates, rebooting, and toggle developer options did nothing. I even went as far as disabling the lock screen so it doesn't make me enter my pin when I try to turn it on - still nothing! I am very desperate and tired of all this rooting, it would be nice to get some help!
Also, I think I can use this video
to root if I figure out to get to that temp directory command thing the guy entered. I use windows ten, but can't find how to get to that place.
An answer to either question would be much appreciated, thanks!
Click to expand...
Click to collapse
You will find more accurate information about it in the specific device's forum https://forum.xda-developers.com/c/amazon-fire-hd-8-and-hd-10.4709/ I guess you choose the more problematic OEM to start tinkering with, Amazon is not such good for rooting and modding.