Hey there community,
I've recently bought an used Asus MeMO Pad with the following data:
Model number: ME173X
Android version: 4.2.2
Kernel version: 3.4.5
Build number: ME173X_WW_user_4.2.4.04152_20140714 release-keys
As I want to get root access and maybe put some alternative OS on it, i wanted to unlock the bootloader. I'm using a Linux OS on my Laptop so I won't be able to rely to those windows applications for this case.
In general adb and fastboot commands work as intended via USB. With adb there are no issues at all, but the fastboot mode is where the trouble begins.
As I read in several guides for unlocking the bootloader on this device, there should be some kind of (even minimalistic) user interface where I should be abled to confirm that I want to unlock the bootloader.
On my device I only get a black screen with one white line at the bottom stating
=>FASTBOOT mode ...
fastboot devices detects the device and I can perform fastboot reboot.
As soon as I try to run any command that needs an user interaction on the devices screen (e.g. fastboot oem unlock), the shell on my Linux system is in a wait loop (guess it's waiting for devices response) and on the ASUS the screen remains totally the same.
Anyone of you any idea what could be the issue with this device? In Androids settings I've enabled USB-debugging, did I miss something?
Recovery mode is Android system recovery <3e>. I don't know if or how I could install custom backups with that one, only worked with TWRP yet.
Already thanks a lot for reading into my struggle - maybe someone of you could help me out of that.
I am following this one, since I have exactly the same problem.
I did try to unlock the bootloader on a Win11 device, but the tablet did not connect long enough to be able to unlock the bootloader.
Any help or suggestions to get a custom rom on this oldie via Linux would be much appreciated.
I believe your droidboot partrition could be damaged, it should be easily fixable with flashing ESP recovered from firmware files.
Regardless of that, im pretty sure you cant just unlock the bootloader like this, first of all you will need to upgrade to lollipop 5.0 and then flash modified bootloader, otherwise wont work, Asus does not support unlocking bootloader on this device unfortunately.
Related
Per title, Nexus 6 will not get past the white "Google". I can get into recovery fine. But the bootloader is locked, so I cannot properly flash stuff. Attempting to unlock the bootloader, I'm told I need to enable the option in the settings menu that I cannot access.
Looks like I'm not the only one I have the same issue and nothing works
AndrewZorn said:
Per title, Nexus 6 will not get past the white "Google". I can get into recovery fine. But the bootloader is locked, so I cannot properly flash stuff. Attempting to unlock the bootloader, I'm told I need to enable the option in the settings menu that I cannot access.
Click to expand...
Click to collapse
is this happened after trying to install update with adb sideload?
I got my nexus 6 today and tried to sideload the ota zip file, but I had no luck and now my nexus can not boot. I had enabled the option for bootloader unlock but my big mistake was that i tried to factory reset the device from recovery and now the bootloader can't be unlocked.
supposed to be experience with nexus devices, but with the bootloader locked I don't know what to do.
any ideas guys?
psybill said:
is this happened after trying to install update with adb sideload?
I got my nexus 6 today and tried to sideload the ota zip file, but I had no luck and now my nexus can not boot. I had enabled the option for bootloader unlock but my big mistake was that i tried to factory reset the device from recovery and now the bootloader can't be unlocked.
supposed to be experience with nexus devices, but with the bootloader locked I don't know what to do.
any ideas guys?
Click to expand...
Click to collapse
Yeah I think that's what I may have done too. I was just trying to go back to 100% stock (ignoring 5.1 even).
And of course NOW the 5.1 image is up on Google's page.
Have the same situation: flash 5.1 OTA and then wiped system
Now I can't unlock bootloader (as system just cant boot) and can't flash stock image (as system.img can't be flashed with locked bootloader)
I do not want to believe this is a brick, but it is very likely it
Sadly I've just done the same thing. ADB updated from 5.0.1 to 5.1, and the system.img didn't copy correctly. Phone wont boot past the Google splash screen, and I can't flash a factory image to recover the phone, because in order to unlock the bootloader I have to enable the option in developer settings, which I can't get to because the phone wont boot!
I understand the purpose of having an extra layer of security to prevent malicious types from trying to flash factory images onto stolen devices, but surely any system that allows a user to brick a device simply by leaving a setting unchecked (in a hidden menu, no less!) is asking for trouble? Particularly on a developer orientated device like a Nexus.
It seems crazy that a developer can ADB the official Google Android OTA zip, using the official Google Android SDK, onto the official Google Android flagship device, and the simple corruption of one of the sent files can cause the device to become totally unusable. Surely, say, providing an option in the developer option settings to PIN protect the bootloader, rather than just preventing it from being unlocked all together, would be a more sensible choice?
For what it's worth, I explained my situation to Google, and they are replacing the phone under warranty. This is probably your best (or only) option at this stage.
Good luck, and please let me know if you do manage to find a work-around/ solution to your woes!
Hi all,
I've purchased a used P20 Pro from a friend which has an unlocked bootloader and has been previously rooted. I normally keep my phones stock so I want to lock relock the bootloader (I have the code) but despite trying to follow various guides I have been unsuccessful.
Would anyone be able to guide me through the process of relocking the bootloader please?
The main reason I like to keep stock is manufacture updates etc and I don't have the knowledge to maintain a rooted phone.
R89B said:
Hi all,
I've purchased a used P20 Pro from a friend which has an unlocked bootloader and has been previously rooted. I normally keep my phones stock so I want to lock relock the bootloader (I have the code) but despite trying to follow various guides I have been unsuccessful.
Would anyone be able to guide me through the process of relocking the bootloader please?
The main reason I like to keep stock is manufacture updates etc and I don't have the knowledge to maintain a rooted phone.
Click to expand...
Click to collapse
I don't believe that an unlocked bootloader will prevent you from getting updates. As far as I know the only difference is the warning you get when you boot that "you can't trust the phone."
IF YOU BRICK YOUR PHONE IT'S YOUR RESPONSIBILITY
Don't know if there is another way but of you have fastboot and adb you can do it:
1. Make sure developer options are enabled
2. Connect your phone to the computer using USB cable.
3. Open a command window and type 'adb boot bootloader'
4. Once the device has booted into the bootloader mode type 'fastboot oem lock'
This WILL ERASE all your user data and you will have to configure everything from scratch. You will need the unlock code if you ever want to unlock it again so make sure you don't loose it.
my phone is SoftBank 502SO X Performance using GENERIC GLOBAL 8.0.0 F8131 rom. i tried most of the fastboot commands i could find. everything just throws out "command not allowed" error except for reboot and getvar command. any help please? i also have OEM Unlocking turned on as well as USB Debugging and turned off MyXperia Find My Device. my bootloader is locked and the service code shows up with "no". i remember a few years back where i use this android 4.4.4 budget phone (also bootloader locked and will not be unlocked in any way) can do most of the fastboot commands (flash system/ boot/ recovery/ etc...)
if it cannot fixed in anyway, is there any rooting app specifically for android 6.0.1 - 8.0.0? i tried using kingoroot, kingroot. none of them can break through.
Any help would be appreciated.
yeah , i have that phone as well , we kinna get ****ed because unless there is a exploit there is no way to unlock bootloader . There is a exploit have potential it's cve 2019-2215 but i found no developer working on it there is a app based on it (qu1ckr00t) but it not work on all device and i have try to compile it but i don't have the skill to do that . And i have try contact sony to resolve it but they said no . So yeah hope in the near future there will be a way
Eager to try out Android 11, I sideloaded the ota zip of the latest Developer preview on my Pixel 4 XL. I have the Verizon version, so my bootloader is locked and I was unable to get it to unlock. So, I figured the ADB sideload method would be perfect.
Everything went smoothly until after the OTA was installed:
I just get a screen that says "Can't find a valid operating system. Device will not start." -- this screen appears for recovery and rescue mode.
The only thing I do have access to is Fastboot. Device appears when I type in "Fastboot devices", but I'm guessing that it doesn't matter since my bootloader is locked and I can't flash anything?
Google support was no help and just send me the address of a repair shop.
Does anyone know if I'm totally F'd in this situation?
Thanks
Nevermind I'll keep looking
Can you change slots? fastboot --set-active=a
It tells you what slot you are on in the bootloader screen. It won't hurt anything. You can always change it back. It's the only thing I know to try.
You can get a stock image and flash it from the stock recovery; dont recall how that procedure is done but there is a guide floating around here as it comes up every once in a while. Usually a Verizon owner...
Are you able to unlock the bootloader (activated before sideload)? So flash unlock and then the factory Image. If you can't unlock your bootloader you are stuck and best option is to open a warranty case by Google...
Try this - https://pixelrepair.withgoogle.com/
You may need to use a VPN if it says not supported in country. Never used it before but worth exploring.
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Sean Hicks said:
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Click to expand...
Click to collapse
Buying it "unlocked" means you bought it free of a carrier, such as Verizon, who lock the bootloader, and can't be unlocked.
But you still need to unlock the bootloader, it comes locked, for security reasons. So if you never unlocked it, it's locked.
I haven't installed beta 12 yet.
Do you have the latest SDK tools? (adb, fastboot, etc)
I was under the impression though, that you can't downgrade with a locked bootloader. But not sure.
Sean Hicks said:
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Click to expand...
Click to collapse
This probably isn't of any help now, but going forward, it may be. In Developer options, you can enable 'OEM unlocking'. As you can see now, it may well be a very good idea to enable that **before** you start messing with the phone, because if something does go wrong (as it has for you), then you can (hopefully) still get to fastboot and do 'fastboot flashing unlock'.
So, knowing this, you may want to keep an eye out for some tool or something that will allow you to possibly turn on oem unlocking (because your device won't boot).
Another thing to try is switching slots and see if the other slot boots? If you can get to fastboot try; fastboot --set-active=(a or b), then fastboot reboot. (If you don't know which slot is active, do 'fastboot getvar all', in the output it will tell you which is current.
cheers
Your bootloader being locked should not affect your ability to restore factory images/OTAs from Google. They are signed by Google and will pass the signature checks. You should try to download the latest factory image (either 11 or 12beta) and flash it via recovery => adb sideload.