Related
This is a problem, and it's doing my nut. I have a Vodafone Smart Mini 7, which I desperately want to root, to get all of Google's bloatware and the stuff the original network provider put on it.
I've already unlocked it to all networks, but the bootloader is being a PITA. I've done the usual with adb and fastboot, namely put it into USB Debugging, and then done this;
Code:
adb devices
adb reboot bootloader
fastboot getvar all
When I get to the section on the bootloader, it advises me that it's Secure.
I tried to use
Code:
fastboot oem unlock
and when I confirm on the phone that I want to unlock it, I get told that Remote Unlock is not allowed.
I assume that the fact that fastboot getvar all says that the bootloader is secure, means I need some sort of key to get it off. My old network provider don't know where to get it from, my tech team don't know where to get it from and I'm screwed.
Anyone got any ideas on whether I can get round the "secure" part of this, like some way of finding the key for it? Thanks
TootyRooty said:
This is a problem, and it's doing my nut. I have a Vodafone Smart Mini 7, which I desperately want to root, to get all of Google's bloatware and the stuff the original network provider put on it.
I've already unlocked it to all networks, but the bootloader is being a PITA. I've done the usual with adb and fastboot, namely put it into USB Debugging, and then done this;
When I get to the section on the bootloader, it advises me that it's Secure.
I tried to use
and when I confirm on the phone that I want to unlock it, I get told that Remote Unlock is not allowed.
I assume that the fact that fastboot getvar all says that the bootloader is secure, means I need some sort of key to get it off. My old network provider don't know where to get it from, my tech team don't know where to get it from and I'm screwed.
Anyone got any ideas on whether I can get round the "secure" part of this, like some way of finding the key for it? Thanks
Click to expand...
Click to collapse
I have the exact same issue I read some threads and nothing solid has come out of it some say they managed to get root but others say they bricked the phone
Any news on this topic? I too have one i desperately would like to root because it is permanently full and you cant do anything wih it. The Google apps and the apps installed by my service provider take up all the onboard storage space. I downloaded only Whatsapp and Facebook Lite and bam,the phone is completely full and useless as it cant do updates,runs extremely slow and does all sorts of random stuff like restarting on its own etc. driving me utterly insane.
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
I'm with same problem here!
Suckmymfdick17 said:
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
Click to expand...
Click to collapse
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
knjigo said:
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
Click to expand...
Click to collapse
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Suckmymfdick17 said:
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Click to expand...
Click to collapse
What do you mean with "I blocked my bootloader"?
Twrp is easy to flash. Root is integrated in ressurection remix rom. And this rom is great. Just try to flash twrp in Fastboot and than ressurection remix with twrp.
Can you boot in Fastboot?
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
tjgibri said:
I'm with same problem here!
Click to expand...
Click to collapse
I solved it, I finally flashed the stock rom to my phone and it works.
Apparently my pc was not flashing the stock rom in adb, and the phone turned off when loading the software. I did it 3 times until I load correctly and start well.
if you have the same problem apparently then OEM Blocking is not responsible. You have to flash the most current rom or the one that you had by default when the brick happened to you, you flash it in a normal way with commands of adb and ready, I would have to come back to life.
download from firmware center MotoZ Griffin the most current rom stock at 7.1.1
echo92 said:
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
Click to expand...
Click to collapse
Thanks for your help friend, I finally flashed it with a recent android 7.1.1 update. Apparently the OEM lockout was not the culprit, but it was an interrupted flash of android 7.1.1 at some point when loading the software to the phone, it would shut down on its own and not complete the installation, which showed me the mentioned message. I didn't realize that and thought it was the OEM blockade.
I finally did it on another pc and it worked. the phone came back to life.
I have one Moto Z2 Force (XT1789-05), bought from coolicool.com, I didn't know device came Unlocked Bootloader, Device rom had problem with many apps, I googled and found one topic in XDA developer to Install Stock Rom, I downloaded and Installed India Rom, it's worked somehow fine, but still had problem, I downloaded Verizon Rom, Android 8, after Installed Android 8 Verizon Rom, Locked device bootloader immediately, now device stuck at Welcome Wizard in Android 8, after select language I got this message: (Please wait, this may take a few minutes) this is proof video (http://ahmn.co/Upload/IMG_0161.MOV), after this issue, device already locked, I can't unlock, because need to go to the Developer Option in Setting, I stucked in Welcome Wizard, there isn't any bypass, So, I start to search in Google, XDA-Forum, Android Central and more, I created many threads, many requests, no one can't help me, I tried to reach google developer support to the tell to me how can I bypass Android 8 Welcome Wizard, there is must be a way, but I can't find it, now I can access to Android Recovery and Bootloader
1. if you help me to FORCE UNLOCK device without need Developer Option in setting my problem will solve
2. If you help me to Bypass Android Welcome Wizard, access setting and enable OEM Unlock
3. If you help me to update the device from Android 8 to Android 9 Verizon ROM via ADB Sideload or Update from SD card in Recovery mode
4. If you have any idea to how can I fix it
Extra Information: I bought Belkin and Uni USB-C to Ethernet Adaptor to help me bypass Android 8 Welcome Wizard, I bought WSKY WIFI Adaptor because device Wifi can't find any network (I found QR setup by tap several times in Language Selection), after this section need to download google device policy apk, my device can't find any Wifi Network and my Ethernet Adaptor can't help me either, So, I just remained with my phone, and I can't do anything,
Please, someone, help me
My Device SKU: XT1789-05
Hey folks,
I've tried my best so far, but I am stuck.
I wanted to change the ROM on my wife's Redmi 3 pro. It was running on a rather old RR version and I wanted to go back to MIUI to have a better camera.
After an unsuccesful attempt to flash this, I was stuck in a bootloop.
This - in general - was no problem: I've decieded to flash an official firmware via MiFlash, but this apparently didn't work as well.
So, now MiFlash has locked the phone again but not properly installed anything.
I can access Fastboot and the pre-installed recovery, but nothing more.
The unlock tool tells me that I can't unlock it because it is apparentyl not bound to my MI account (and I have no clue with which account I've unlocked it the last time).
Desperately appreciation any kind of help!
Thanks in advance.
UPDATE: I was apparently not patient enough. After quite a while it finally booted. Now I can access the system again, but still can't unlock the phone.
UPDATE 2: I also found out with which account I've unlocked it and thus everything worked after all. Now sporting Lineage 14 with camera mod.
Please, feel free to explain how can it finally booted. Your experience might be help somebody sometime.
?
hello. first of all i don't speak english and i use google translate and i'm sorry for that.
I have an asus-me302kl tablet. I wanted to install twrp but now it's locked. I installed firmware with rawdate but it has no function. I need help unlocking the bootloader. recovery mode does not turn on either. I am wondering if there is a pat file or some other method to unlock the bootloader. Thanks in advance. I hope I was able to explain myself.
please help
civan34 said:
please help
Click to expand...
Click to collapse
This low-end tablet is heavily outdated ( 7 years old ), means you won't find a TWRP suitable to it.
jwoegerbauer said:
This low-end tablet is heavily outdated ( 7 years old ), means you won't find a TWRP suitable to it.
Click to expand...
Click to collapse
First of all, thanks for the answer. this tablet is a customer tablet. and it's my fault that it's locked. For this I need to unlock the bootloader. is there no tool to flash the software? I managed to install the .rawdata firmware. and the device has root permission but I couldn't go further. Now I'm waiting like this.
@civan34
My suggestion:
Re-flash tablet's Stock ROM ( is a ZIP-file ) to bring tablet back to its initial state ( what includes flashing the Stock Recovery ).
When that's done you can start to unlock tablet's bootloader by means of Fastboot, if it's not denied by OEM/Carrier.
If tablet's bootloader got successfully unlocked you can try to flash LineageOS v15 ( Android 8 Oreo ) onto tablet.
jwoegerbauer said:
@civan34
My suggestion:
Re-flash tablet's Stock ROM ( is a ZIP-file ) to bring tablet back to its initial state ( what includes flashing the Stock Recovery ).
When that's done you can start to unlock tablet's bootloader by means of Fastboot, if it's not denied by OEM/Carrier.
If tablet's bootloader got successfully unlocked you can try to flash LineageOS v15 ( Android 8 Oreo ) onto tablet.
Click to expand...
Click to collapse
I can't install the stock firmware. Doesn't allow flashing over fastboot. Doesn't allow flashing via recovery mode. Is there a program to install stock firmware?
@civan34
A Stock ROM gets flashed by means of ADB
Example command sequence:
Code:
adb devices
adb reboot sideload
adb sideload <FULL_PATH_TO_STOCK_ROM_ZIP_ON_PC>
adb reboot
jwoegerbauer said:
@civan34
A Stock ROM gets flashed by means of ADB
Example command sequence:
Code:
adb devices
adb reboot sideload
adb sideload <FULL_PATH_TO_STOCK_ROM_ZIP_ON_PC>
adb reboot
Click to expand...
Click to collapse
I am a little novice at the command line and do not know how to type the command you typed. Should I type as you wrote, or do I need to change the name of the zip on the computer?
my command
(adb sideload stock.zip) and I get read error for this command.Since I don't speak English, I didn't understand exactly how to write the command. I don't want to overwhelm you, sorry for that
I'm in the same boat.
I picked up 4 of these from an auction. I can't unlock any of them, because the Asus tool, (ME302KL_UnlockTool_Instructions) zip file, no longer works. TWRP is available 3.2, link is below. I have rolled back to the stock ROM on 2 of the machines, no joy. Any suggestions or guidance, would be greatly appreciated. Thanks.
https://forum.xda-developers.com/android/general/recovery-twrp-3-1-1-0-asus-me302kl-t3609759
Link to Asus Unlock file
https://drive.google.com/file/d/1mzntnfm5OlHbKd1cYkd1YEFs6CYeKqmn/view?usp=sharing
jbone899 said:
I picked up 4 of these from an auction. I can't unlock any of them, because the Asus tool, (ME302KL_UnlockTool_Instructions) zip file, no longer works. TWRP is available 3.2, link is below. I have rolled back to the stock ROM on 2 of the machines, no joy. Any suggestions or guidance, would be greatly appreciated. Thanks.
https://forum.xda-developers.com/android/general/recovery-twrp-3-1-1-0-asus-me302kl-t3609759
Link to Asus Unlock file
https://drive.google.com/file/d/1mzntnfm5OlHbKd1cYkd1YEFs6CYeKqmn/view?usp=sharing
Click to expand...
Click to collapse
I contacted Asus a few times about this Bootloader issue, but today I took a different approach. It appears they Blacklisted the ME302KL from the servers, because it is EOL. I made it clear to them. that I can't access the Asus Cloud or any other Asus tool loaded on the machine and I can't do OTA updates either. I made it clear that I should be able to at a minimum be able to upgrade to 4.4.4 from 4.2.2 after resetting the device. They agreed and are escalating the issue up the food chain.
My hope is they remove it from the blacklist which will fix the "Network Error" message when trying to use the Unlock Tool for the bootloader. I will circle back around, once I hear back from them....
jbone899 said:
I contacted Asus a few times about this Bootloader issue, but today I took a different approach. It appears they Blacklisted the ME302KL from the servers, because it is EOL. I made it clear to them. that I can't access the Asus Cloud or any other Asus tool loaded on the machine and I can't do OTA updates either. I made it clear that I should be able to at a minimum be able to upgrade to 4.4.4 from 4.2.2 after resetting the device. They agreed and are escalating the issue up the food chain.
My hope is they remove it from the blacklist which will fix the "Network Error" message when trying to use the Unlock Tool for the bootloader. I will circle back around, once I hear back from them....
Click to expand...
Click to collapse
No joy. Asus says they are under contract with AT&T. The ME302KL has been black listed and Asus will not add it back to the unlock tool or provide any support AT ALL!. They keep telling me the unlock tool isn't theirs. But the amount of times Asus's name is used in the EULA, tells me otherwise. I'm waiting to hear back from AT&T on their position on the matter. Stay tuned...
Ok campers, i have a work around for the ME302KL AT&T bootloader issue. I just verified AT&T can unlock the devices, they just verified 3 devices for me. Only catch, you have to have an account with them.
So, If you like people actually being able to hear you on a call, you probably have a different service, like i do. Based on the call, there are really only 2 options. Option 1, Harassment. Someone you know, has them as their provider. A family member, a friend maybe your priest. So, my suggestion is to harass them into they adding the device, under their plan. They only need to do it long enough, for you to get it upgraded. Once AT&T unlocks it, upgrade the OS, add TWRP and create a custom recovery that never goes back to KitKat. then, have them cancel it off their account. At the most, you're looking at $25 for the month, if anything at all.
Option 2 - Go Prepaid for a couple of months. This one is tricky based on the T&C's on their website. You will need to create a new account, $30 for 5 5gb a month. No contract and what you don't use, rolls over to the next month. Make sure to read their T&C's ased on new prepaid accounts with BYOD. I told the agent I wanted to Only use broadband service, no phone for when im working in the field, until i'm still under contract with Verizon. She pitched services, i dodged and evaded. She told me a month to month prepaid plan was doable, to get it unlocked. They would be able to unlock it for free and so i could upgrade the OS. So, it's not too terrible, just annoying to jump through so many hoops. The first option, would be the easiest.
These are just suggestions. I take no responsibility if you brick the device once it's unlocked. It is AT&T and the device may be commiting suicide in lieu of being on their Network. :0)
I sent the message to AT&T with imei of my ME302KL but the answer is been "the manufacturer doesn't have an unlock code for this device".
Help me to unlock my device.
I'm using samsung A10,i try to root my phone but not sure the step are correct or not. But now my bootloader is unlocked and my data was erase, how to lock the bootloader and recover my data's back.Please help me
Even if you manage to re-lock the bootloader the data are unrecoverably wiped.
So I've been having this issue for a while now. I would like to unlock the bootloader on my Samsung and I'm struggling severely. I've done so much research and attempts and phone calls and in the end, my hands always turn up empty. Could someone please give me some advice or a guide to what I'm supposed to do because it seems like this specific phone under the Tracfone carrier is a ghost when it comes to this and rooting. Once I get a lead I'm suppose to enable oem unlock, well my phone doesn't have one. I've waited more than a week with developer options on and I've even tried adb and fastboot. Still nothing, I really need an expert's help but I can't seem to find anyone. Not even XDA is helpful with this phone. Yeah they have the A10 or A10s but not the A10e under the Tracfone carrier with the model number SM-S102DL. Help would be much appreciated. Thank you
visit here
My A10 phone still in unlock bootloader condition, can i still recover the lost files?