First I am sorry for long post because of details and my poor English.
I have a L Bello D335 running on stock Rom(updated to Lollipop via OTA) and it is unrooted.
Yesterday I tried to unlock bootloader, I typed command [fastboot oem unlock] in Fastboot mode, and my phone went to Bootloader Unlock Screen. It said to press Vol+ button to confirm unlocking bootloader or press Vol- button to cancel. I picked up the phone and press Vol+, but USB cable connection was disconnected accidently because of loose micro USB plug:crying: (that is what I've noticed after 5 minutes, it was disconnected and reconnected on moving the phone). Then phone screen stayed in Bootloader Unlock Screen and it didn't responded to pressing keys.
On computer cmd windows, after [fastboot oem unlock] it said:
FAILED (Status read failed (Too many links))
fastboot: error: Command failed
Click to expand...
Click to collapse
Then I typed command [fastboot reboot]
and it said:
Rebooting FAILED (Device sent unknown status code: e)
fastboot: error: Command failed
Click to expand...
Click to collapse
Then I typed command [fastboot devices]
and it showed strange code like:
[email protected]???^?l?l fastboot
Click to expand...
Click to collapse
I didn't check [fastboot devices] before and I don't know how the result is.
Then I've noticed loose micro USB plug and thought bootloader unlock process was interrupted.
And I disconnected phone and boot up and the phone is working well and all app/data remain like before.
But now, if I type [fastboot devices] in Fastboot mode, it is showing a strange code instead of an alphanumeric code. It is a different code every time, like:
[email protected]???*?G?G fastboot
Click to expand...
Click to collapse
(or)
[email protected]???▼?╟?╟ fastboot
Click to expand...
Click to collapse
I tried different cable and ports but always the same.
And fastboot commands [fastboot reboot], [fastboot getvar unlocked], [fastboot getvar all] are working. Bootloader is still locked. ADB command [adb devices] returns alphanumeric code.
Is it something corrupted or because of locked bootloader?
If it is corrupted,
What are the possible damages? and
How to fix it?
Thanks in Advance
Reply
You could try unlocking the bootloader again, BUT first the cable needs to be held in place with some tape (on the phone around the left display corner and back to the cable) and THEN unlock the bootloader via PC.
Good luck! :good:
Related
i'm in the process of re-locking my bootloader in order to send it to Samsung for repair (home button not working). when i run the command line "fastboot oem lock", it just keeps hanging at "waiting on device" and nothing happens. i have the correct drivers installed. when i run "adb devices", it shows up the device. however, when i run "fastboot devices", it does not show up anything. any help on relocking my bootloader would be appreciated. Thanks!
Probably shouldn't be answering this here buuuuut...
adb reboot bootloader
and THEN
fastboot oem lock.
See what happens. You have to be in boot loader mode. Please move your questions to the Q&A section sir.
i did enter that command in order to get into fastboot. after that , i ran the command "fastboot oem lock" but it gets stuck at "waiting on device"
Update your drivers
Yea at this point I'd say its a connectivity problem. Drivers and or cable, but since you are getting adb devices to recognize, its not your cable. You should really use ubuntu, you would save yourself a lot of time, because you don't really have to deal with drivers like windows.
'sudo fastboot oem lock'
You need to be super user.
sure you went into bootloader and not recovery? because adb is seen in recovery and doesnt work in bootloader!
how to relock the bootloader:
First of all you're gonna need:
- A PC/Android SDK/ADB Toolkit
- An android with an unlocked bootloader
- A usb cable connected to the device
I made this thread because I had the same problem but I found a way to fix it! I was trying to load into a corrupted recovery and it kept being stuck on the "Your device is unlocked and cant be trusted, your device is booting now" thingy, but I found my way out and it's really easy!
Tutorial:
Steps:
- 1: Hold the power button down till your phone shuts down and re-open by also holding down the "volume-down" key, so it loads into fastboot.
- 2: Go onto your pc/mac (cmd/terminal) and type the command "fastboot oem relock <your unlock number>". Then it should be something like this:
fastboot oem relock <your unlock number>
(bootloader) The device will reboot and do factory reset...
OKAY [ 15.785s]
finished. total time: 15.785s
Click to expand...
Click to collapse
To get your "unlock number" take a look at this:
-We get our Unlock Code for Bootloader, write it somewhere !-
^^^ This is on the emui website = emui . com
(XDA doesnt allow me to add a picture of what I mean because I'm a new user )
If you need more help, leave a comment below! :good::laugh:
Why i got this message that say failed?
Hello to everyone that read and thanks you for the time passing to read my problem.
First of all : this is not my native language so excuse me for my english ... :/
After that, this is my first thread ... :/
And then , i'm tryin to learn but i'm pretty newbie on computing ... :/
(i'm trying to root my phone like every newbie does first by following slowly and accurately this tutorial: https://www.getdroidtips.com/root-wiko-view-3-lite/
i'm gonna details all i did step by step but at the end cause i don't think that the problem come from here)
so after etablishing the connection between my device and the PC using a wiko usb driver
i tried to flash my Wiko View 3 Lite ROM to boot the patched "boot.img" via Minimal ADB and Fastboot V1.4.3 (latest version)
so once i enter the command : fastboot flash boot "MyPatchedBootFile".img
i got a :
Failed.(flashing lock flag is locked. Please unlock it first!)
so i should able the flashing option somehow somewere ?
i tried several fastboot command but nothing... (btw i is there a way to kow all the comandes i can do on my PC cause i see the command changing depending phones or fastboot )
that's what i have :
FAILED (remote :Not implemet.)
i'm not sure to understand what "no implemet" mean ??
I can't find any useful info exept this one unfortunately that could be the same for my phone's model :
Rooting a wiko jerry is impossible due to all fastboot commands lock the phone
On Linux: All fastboot commands lock. Particularly fastboot oem unlock or fastboot flashing unlock. After removing and re-attaching the phone to the usb port (without turning it off), the phone bec...
android.stackexchange.com
i'm continuing to look for anwsers, can someone have an idea ??
( that's what i did:
1/ i've downloaded magisk.apk's last vertion on my phone
2/ found a Wiko View 3 Lite full ROM online for the rom.pac file
3/ converted it w the SPD flash tool (i didn't really understood this step :/) : https://www.getdroidtips.com/patch-boot-img-root-spreadtrum-device/
4/ sent it to my phone
5/converted it agan via magisk.apk on my phone
6/ took it back from my computer to the same folder that i launch the ADB and fastboot comand prompt
7/last step normally :/ i should write the command: fastboot flash boot xxxxxxxxx.img and i gotstuck here ....
)
thanks again for all your help guys ))
Hakodu13 said:
...
so once i enter the command : fastboot flash boot "MyPatchedBootFile".img
i got a :
Failed.(flashing lock flag is locked. Please unlock it first!)
so i should able the flashing option somehow somewere ?
i tried several fastboot command but nothing... (btw i is there a way to kow all the comandes i can do on my PC cause i see the command changing depending phones or fastboot )
that's what i have :
FAILED (remote :Not implemet.)
i'm not sure to understand what "no implemet" mean ??
I can't find any useful info exept this one unfortunately that could be the same for my phone's model :
Rooting a wiko jerry is impossible due to all fastboot commands lock the phone
On Linux: All fastboot commands lock. Particularly fastboot oem unlock or fastboot flashing unlock. After removing and re-attaching the phone to the usb port (without turning it off), the phone bec...
android.stackexchange.com
i'm continuing to look for anwsers, can someone have an idea ??
...
Click to expand...
Click to collapse
Before trying to deal with phone's bootloader, will say running any Fastboot commands, you have to enable "OEM unlock" option in phone's Android Settings->Developer option. If done so, reboot phone. Afterwards run Fastboot commands
Code:
fastboot devices
fastboot oem unlock <- or: fastboot flashing unlock
jwoegerbauer said:
Before trying to deal with phone's bootloader, will say running any Fastboot commands, you have to enable "OEM unlock" option in phone's Android Settings->Developer option. If done so, reboot phone. Afterwards run Fastboot commands
Code:
fastboot devices
fastboot oem unlock <- or: fastboot flashing unlock
Click to expand...
Click to collapse
Hey
Thanks for your awnser,
i did it already, i've activated EOM unlock , USB debug and also desactivated the standby when the phone is plugged
also i think all fastboot command work cause i can reboot my phone using "fastboot reboot"command
fastboot devices reconize my phone
fastboot flashing unlock dosn't work
it is writed: FAILED (remote: Not implemet.)
fastboot oem unlock dosn't work,
it is writed: FAILED (remote: unknown cmd.)
something interesting is when i write fastboot "AnithingElse" unlock
it says: fastboot: usage: unknown command "AnithingElse"
and no: FAILED (remote: unknown cmd.)
like if adbandfastboot know the commannd " fastboot oem unlock " somehow but not my phone.
thanksthanksthanks again for your awnser!!!
My guess is that running Fastboot commands is denied by OEM/Carrier. And that's not wondering me because phone is based on UniSoc chipset.
AFAIK to get Fastboot working on such phones you have to request from OEM/Carrier the unlock-code as 1st thing of all things and when received have to flash it to phone.
jwoegerbauer said:
My guess is that running Fastboot commands is denied by OEM/Carrier. And that's not wondering me because phone is based on UniSoc chipset.
AFAIK to get Fastboot working on such phones you have to request from OEM/Carrier the unlock-code as 1st thing of all things and when received have to flash it to phone.
Click to expand...
Click to collapse
Ye i guessed the commands is denied on purpose
but why ? just for me not to have root acces ?
and what if i want to flash or reflash my ROM just to have back a new fresh boot ?
do a lot of phone constructor use that radical trick ?
and what is OEM/Carrier ? where can i find this ? i can't find anything online ...
merci ))
OEM is an acronym and stands for Original Equipment Manufacturer ( e.g Samsung )
Carrier is the is cell phone company that provide cellular service to cell phone users ( e.g. AT&T, Verizon )
I posted this in the appropriate forum but this phone is so old I've not received any response.
So I've decided to root and customize my Z2 Force and want to unlock the bootloader to get TWRP installed. All device side settings are correct (USB Debug, OEM unlock etc.) in developer mode. ADB commands are working fine as I can see my SN when using ADB Devices command. I then reboot to the bootloader through ADB (adb reboot bootloader) and it works fine and my Z2 boots into the bootloader. Then I try to get the unlock code (fastboot oem unlock) and I get a message after trying to run the command: access denied. I started my CMD window using run as admin - no help. Installed ADB all over again with new generic drivers and moto drivers - no help. Even installed everything in the root directory on my hard drive - no help
I don't understand why I'm getting this message. I've unlocked and rooted all my phones over the years but they've all been HTC. Never messed with a moto phone before. Anyone think this is a permalocked bootloader version - MODEL:XT1789-04 TYPE:M29E2
Things I have not tried yet:
Another computer
Tested fastboot command on one of my other phones
Any help is appreciated.
theandies said:
I posted this in the appropriate forum but this phone is so old I've not received any response.
So I've decided to root and customize my Z2 Force and want to unlock the bootloader to get TWRP installed. All device side settings are correct (USB Debug, OEM unlock etc.) in developer mode. ADB commands are working fine as I can see my SN when using ADB Devices command. I then reboot to the bootloader through ADB (adb reboot bootloader) and it works fine and my Z2 boots into the bootloader. Then I try to get the unlock code (fastboot oem unlock) and I get a message after trying to run the command: access denied. I started my CMD window using run as admin - no help. Installed ADB all over again with new generic drivers and moto drivers - no help. Even installed everything in the root directory on my hard drive - no help
I don't understand why I'm getting this message. I've unlocked and rooted all my phones over the years but they've all been HTC. Never messed with a moto phone before. Anyone think this is a permalocked bootloader version - MODEL:XT1789-04 TYPE:M29E2
Things I have not tried yet:
Another computer
Tested fastboot command on one of my other phones
Any help is appreciated.
Click to expand...
Click to collapse
The process to unlock a moto phone is a bit different. OEM commands are as it says, defined by the OEM. They need to be precise and functional. The command:
Code:
fastboot oem unlock
alone will not work.
Step1:
Instead, You should enter:
Code:
fastboot oem get_unlock_data
You will get an unique 131 ID string that looks for example like this:
Code:
(bootloader) 0000000000000000000000000000001
(bootloader) 0000000000000000000000000000002
(bootloader) 0000000000000000000000000000003
(bootloader) 0000000000000000000000000000004
(bootloader) 0000005
Copy the output to a text editor and delete the (bootloader) and the spaces in between, so it's one whole string.
Step2:
Visit the official Moto unlock website. Sign-in with your account, you will be using the E-mail used to create said account to receive the unlock key. Paste the edited 131 ID string and click Can my device be unlocked? button. If it is unlockable, then a conformation page will appear asking for consent and warranty bla bla bla.... Just read it and accept.
Step3:
When you click unlock, you will receive a KEY through your E-mail attached to the moto account used. Save that E-mail somewhere offline, as it can be used to re-unlock the bootloader in the future if you relock it. Connect your device in fastboot again and type:
Code:
fastboot oem unlock KEY
Where KEY is the one you got in the E-mail.
Done!!! Enjoy your freedom , also check the mark near my answer if it solved your question so others don't have to search for long.
Thanks for your reply. Yes I wrote the fastboot command wrong in my post.
The problem I'm having is even when using the fastboot command you posted I still get "access denied" when using fastboot commands. ADB works fine allowing me to reboot into the bootloader through the command prompt/USB as in ADB devices.
theandies said:
Thanks for your reply. Yes I wrote the fastboot command wrong in my post.
The problem I'm having is even when using the fastboot command you posted I still get "access denied" when using fastboot commands. ADB works fine allowing me to reboot into the bootloader through the command prompt/USB as in ADB devices.
Click to expand...
Click to collapse
As long as in Android -> Settings -> Developer options the option "OEM unlock" isn't got enabled - and phone got rebooted afterwards - you receive the reported error.
OEM unlocking is turned on in developer settings
I'll post up some screenshots soon. Right now I'm on day three of work on the 12 hour night shift.
I tried to by this instruction https://forum.xda-developers.com/t/bootloader-unlock-realme-gt-neo-2-rmx3370-all-variants.4391679/ But I don't have "Apply" as in paragraph 4) but there is as in the picture. What does this mean and how to unlock the bootloader in this case?
it says that you already joined in depth-test programm. So just boot your device into the fastboot mode and connect it to the pc. Then open up the "adb programm" whit the cmd/terminal and type: "fastboot flashing unlock". Them your device will reboot and show warning and use the volume button to select "Yes Unlock Bootloader"
Topo's said:
it says that you already joined in depth-test programm. So just boot your device into the fastboot mode and connect it to the pc. Then open up the "adb programm" whit the cmd/terminal and type: "fastboot flashing unlock". Them your device will reboot and show warning and use the volume button to select "Yes Unlock Bootloader"
Click to expand...
Click to collapse
If it looks like this, is the bootloader unlocked? I did not do anything with the phone, it is like that from the box.
yes it is unlocked!
Topo's said:
yes it is unlocked!
Click to expand...
Click to collapse
thanks for the help
make sure to leave a like for the support it will help me!