• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Can't access bootloader

kyle2699

Lurker
I want to make this clear as possible. And if I'm in the wrong place to post this question, please move it to the right one. I really need help. And I'm NOT that good with all this tweaks and stuff.

In the past months I also can't access my recovery. What I've done is generate a CWM through MTKDroid Tools then install it, then thankfully I got a CWM.

As the title said, I can't access my bootloader. Why do I want to access it? Because I wanna unlock it via fastboot oem unlock. So that I can flash custom roms. (correct me if I'm wrong)

*I can use my device. It can boot normally and I can go to my custom recovery. Just the bootloader got a problem.

By the way my device is Lenovo A690 (Android 2.3.6 : Rooted via KingoRoot). And I'll tell you, this is an old phone.

I'll list down what I've done so far.

1) I already tried to use adb reboot bootloader, but it just hangs with the logo. So I pull out the battery to stop the hanging... (I'll tell you it really hangs cause I left the phone on that state for about 15 minutes)

2) Tried the Volume Down + Power button. This worked for me one time (and it's also the first time). But since then, I can't access bootloader again. And the result is same as number 1, just hangs in the logo.

3) I also tried using Terminal Emulator for Android with this code:

su
reboot bootloader

Still no luck. What it does is only a normal boot.

Please help me. I posted few months ago but I was ignored. I'll accept any help. Thanks in advance! :)
 
Last edited:
Hey Kyle, for you previous thread, it was probably more of a case that nobody knows the answer or is familiar with your issue (or particular device) and it's solution vs. ignoring you (in fact, I do see that James L responded to you)--we're a forum of other users just like you (including our all volunteer staff), so we rely-upon our member's knowledge and the ones that happen to run across your thread.

Anyway, that being said, I have seen other devices that do not or will not respond to a request to go into bootloader / fastboot mode (via adb) or any key combinations, so this behavior you're seeing is not unprecedented.

I take it that adb works properly for you otherwise--i.e. aside from the adb reboot-bootloader commnad?

Finally, what do you need to do by unlocking the bootloader that you haven't already accomplished by installing a custom recovery? Typically, unlocking the bootloader is done because people want to install a custom recovery, which you've already done.
 
Thanks for your reply.

Yes, adb commands do work. Just the adb reboot-bootloader doesn't.

Last question is, can I already install a custom rom even if I don't even know if my bootloader is unlocked yet?
 
Last question is, can I already install a custom rom even if I don't even know if my bootloader is unlocked yet?

You should be able to install a custom ROM if you have a custom recovery that is built for your particular device. Flashing / replacing the recovery partition is a pretty good indicator that you should be able to update/replace the /system partition, too, for your custom ROM (also, if there are custom ROMs in existence for your specific device, that's another good indication that you'll have success with that task, too). I'm guessing all you're missing is a forum of users with your own device that you can compare notes and get confirmation with...

Hopefully, there is some good information from the location where you might be finding your custom ROM that details flashing instructions, notes, issues, etc.

That being said, be sure to first take a Nandroid backup of your stock setup and save that Nandroid backup off to your PC as a secondary backup just in case.

I can't give you much more than this general guidance because I don't have personal knowledge or experience with your specific device, so I can't give you scenarios or things to watch out for.

Hope that helps some :).
 
Back
Top Bottom