Unlock Bootloader - Connection Problem or Invalid MMI code - General Questions and Answers

Hello all,
With the use of this forum, I have been able to Root my LG Optimus F60 (metropcs) LGMS395 - Software Version LGMS39510d
I, then went on to attempt to unlock the bootloder for this phone.
I followed the instructions in the "Official Unlock Bootloader LG%..."
But, when I enter the combo - 3845#*880#, I immediately receive a dialog window that states
"Connection Problem or Invalid MMI code"
To make matters worse, I installed TWRP Manager from Google Play and attempted to use that interface to boot to: Recovery and Bootloader.
Neither worked.
I have done the following:
1. Rooted and checked via Root Checker
2. Downloaded the LG Support tool to make sure that I have the updated drivers.
3. USB Debugging is enabled
4. Attempted to use: adb reboot recovery (reboots my phone, LG screen comes up, Metro screen comes up, back to home Screen)
5. Attempted to use: adb reboot oem-unlock (same as # 4)
6. After #4 and #5, I then tried to enter the combo to check the status of the bootloader - 3845#*880#. That is when i get the darn error message.
7. I have contacted LG, but am awaiting a response....
This phone is brand new, bought only 6 days ago...
Can anyone throw a bone this way?

Related

[Q] Can't unlock phone

I am trying to Root and unlock my Phone a Nexus S
I am using this h**p://www.youtube.co*/watch?v=GSD92Qjt5Og
Lock state show up as Locked
When Phone reboots there no option to unlock it
The Options I have are
Reboot
Reboot Bootloader
Recovery
Power off
HELP
For some reason I'm getting an invalid URL. Might be a copy paste and edit fail on my part though. Did you grab the drivers for android sdk, download adb and try the fast boot method? A google search for Nexus S fastboot OEM unlock should help. I'm on my phone and have the links saved on my PC sadly
Sent by pocket technology.
I got it thanks

[Completed] ONYX (OnePlus X) doesn't boot after unlocking bootloader

Hello everybody,
My phone had some weird glitches, factory reset didn't work, and the capacative buttons didn't work anymore, and I had to restart the play store to install the apk after it downloaded the app. I made a new User, the buttons worked again and I could normally install apps. But it was a temporary fix, and as I couldn't factory reset I decided to unlock my bootloader because that resets your phone. So what I did is:
1. I installed all the proper drivers
2. I opened an commandprompt in the adb folder
3. I typed adb devices, it said unauthorized, I authorized it on my phone, and it said that it was authorized after that.
4. I typed adb reboot bootloader
5. I waited untill it went into fastboot mode and typed fastboot oem unlock (I had the function to unlock the bootloader enabled in developer options).
My phone rebooted after this, now it only shows the OnePlus logo and powered by android, it doesn't boot further. I can't return the phone as I bought it second hand. When I connect the phone to the laptop that I used for it (The usb cable was connected directly to the motherboard, incase that matters and it was an original 4 pin samsung cable), it recognizes it as an Android device, so I think it's a soft brick.
How to fix this? Thanks in advance.
-Oczosinkoo
Hi !
You can try this tutorial
https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Good luck !

Custom Binary blocked by FRP lock & Odin/PC won't recognize the device

Hello all,
So I finally got the dreaded FRP lock error when trying to reboot my phone.
Things I've tried to do:
1. Install Smart Switch and enter my model number + S/N and I get an error "This model number cannot be initialized"
2. Install Samsung Kiss update the drivers etc
3. Download stock firmware and try flash through Odin "Device wont recognize on PC or Odin" (But with another phone it will, so USB is fine)
4. Went into the recovery menu, wiped device/cleared cache etc
So the problem is the device is not recognizing on my on Windows 10 + Windows 7 - If I can get the device to recognize i will be able to flash stock firmware and my issue will be resolved.
If anyone has a bypass, or has resolved their issue please let me know - because I have tried everything.

Unlocking bootloader zui device only!

I have found a way to unlock bootloader again! (if the normal fastboot command does not work for you!)
I had mine bootloader re-locked for some stupid reason. And my phone stayed at Lenovo logo, So no booting or flashing custom roms again. I had giving up the hope. But after searching on some Chinese website. I found a way and it WORKED! I have now again a unlocked bootloader.
The website is in Chinese but don't worry people you just need to fill in some small data.
1: go to the website : https://www.zui.com/iunlock
fill box 1 your IMEI 1
fill box 2 your SERIAL key (the key that you get when you connect to fastboot and use the command 'Fastboot Devices')
fill box 3 your email
fill box 4 the security code that you see to the right of it ( Four numbers )
check the last box, as accepting the rules for warranty blabla. And click the BLUE BIG button
Now wait and have patience! After a while you will get a email with a file in it. Download that file and put it in your adb folder.
now check your device first if its connected and that you see the serial.
- > Fastboot devices <-
If YES than continue...
Use the command :
Fastboot flash unlock (name_of_the_file).img
after that use command:
fastboot oem unlock-go
And your bootloader is UNLOCKED AGAIN !!! :highfive::good::laugh:
Phone is back to life
Disclaimer: sharing your imei is not safe, other people can easily duplicate it on other phones. Google: ''why you shouldn't share your imei''.
Use this as your last resort if your phone doesn't boot or is bricked. Use a fake imei, follow the process and once or phone is unlocked, update the imei using the link @sth0r created on xda to fix imei for the lenovo z5
xperia_bird said:
I have found a way to unlock bootloader again! (if the normal fastboot command does not work for you!)
I had mine bootloader re-locked for some stupid reason. And my phone stayed at Lenovo logo, So no booting or flashing custom roms again. I had giving up the hope. But after searching on some Chinese website. I found a way and it WORKED! I have now again a unlocked bootloader.
The website is in Chinese but don't worry people you just need to fill in some small data.
1: go to the website : https://www.zui.com/iunlock
fill box 1 your IMEI 1
fill box 2 your SERIAL key (the key that you get when you connect to fastboot and use the command 'Fastboot Devices')
fill box 3 your email
fill box 4 the security code that you see to the right of it ( Four numbers )
check the last box, as accepting the rules for warranty blabla. And click the BLUE BIG button
Now wait and have patience! After a while you will get a email with a file in it. Download that file and put it in your adb folder.
now check your device first if its connected and that you see the serial.
- > Fastboot devices <-
If YES than continue...
Use the command :
Fastboot flash unlock (name_of_the_file).img
after that use command:
fastboot oem unlock-go
And your bootloader is UNLOCKED AGAIN !!! :highfive::good::laugh:
Phone is back to life
Disclaimer: sharing your imei is not safe, other people can easily duplicate it on other phones. Google: ''why you shouldn't share your imei''.
Use this as your last resort if your phone doesn't boot or is bricked. Use a fake imei, follow the process and once or phone is unlocked, update the imei using the link @sth0r created on xda to fix imei for the lenovo z5
Click to expand...
Click to collapse
hi i tried to follow this guide to unlock bootloader but on the lenovo website it is asking for an 8 digit serial number but my lenovo z5 only has 7 digit serial number can you please help
karanzxhao said:
hi i tried to follow this guide to unlock bootloader but on the lenovo website it is asking for an 8 digits but my lenovo z5 only has 7 digits
Click to expand...
Click to collapse
In this case the fastboot command is wrong.
You want to boot the phone up to the landing screen and enter ADB devices in your command prompt. Enter That.
You can also get the correct serial by opening the dialer app and entering *#06# in your touch phone pop-up keypad
Hope that helps!
This was helpful, It worked for me. Thanks.
Guide outdated - this worked for me now
Phone: ZUK Z2 Plus (Z2131)
After having tried many times following this tutorial and never receiving any E-Mail, I found a rather simple solution that worked:
I didn't really expect it to work, so this is from memory, wordings may differ a bit.
First: make backup of your data!
Make sure you have updated ZUI to the latest available version.
Enable developer options ( From your device go to " About -> ZUI version" , scroll down and click " build number " continuously until you see "You are now a developer")
Go to developer Options and look for the toggle "Allow OEM Unlock" (or similar) and set it to enable. Confirm.
Reboot.
The phone automatically performs a factory reset (All Data lost!).
Now you can continue with flashing custom recovery (TWRP) and ROM.
For example use Lineage OS. Instructions: (Sorry, can't post the link)
Finally I can enjoy the phone with custom ROM and up-to-date Android 10.
Is this why I can't see my device when it is in fast boot mode or boot loader mode?
a9REhdDp5V said:
Guide outdated - this worked for me now
Phone: ZUK Z2 Plus (Z2131)
After having tried many times following this tutorial and never receiving any E-Mail, I found a rather simple solution that worked:
I didn't really expect it to work, so this is from memory, wordings may differ a bit.
First: make backup of your data!
Make sure you have updated ZUI to the latest available version.
Enable developer options ( From your device go to " About -> ZUI version" , scroll down and click " build number " continuously until you see "You are now a developer")
Go to developer Options and look for the toggle "Allow OEM Unlock" (or similar) and set it to enable. Confirm.
Reboot.
The phone automatically performs a factory reset (All Data lost!).
Now you can continue with flashing custom recovery (TWRP) and ROM.
For example use Lineage OS. Instructions: (Sorry, can't post the link)
Finally I can enjoy the phone with custom ROM and up-to-date Android 10.
Click to expand...
Click to collapse
You are liar.
This solution will not work, because bootloader still will be locked at this state

stuck on download mode

Revision 1
S7 edge(G935F, exynos model)
Android 8.0.0(Oreo)
rooted = yes, using odin and cf-autoroot file
dev options = turned off
USB debugging = off
OEM unlock = locked
carrier = when bought it isn`t tied to any carriers, now it don`t have any SIM card
SD card = Inside, but broken
What happened?
I try to root the phone. This is the first I`ve root a phone. I follow the instructions exactly and it worked. Then the OS notifies me that I have to restart my phone because of security issues. I restarted it, but it won`t boot. There`s a message in the top corner of the screen that says "custom binaries blocked by FRP", I looked it up and saw how to fix it, found it from imyfone.com (
[2023] Fix “Custom Binary Blocked by FRP Lock” - 100% Work
Stuck on 'custom binary blocked by frp lock' error on your Android device? Find the latest & easiest way here to fix it quickly!
www.imyfone.com
), follow it, when I need to input my carrier and country, imyfone don`t list my country (Indonesia) and don`t have the options to select no carrier so I can`t proceed because it already warns me that if I got the info wrong, I will brick my phone. Then I try to brainstorm an idea by myself and found if I redownloads the rooted tar.md5 to my phone, it will boot again. I boot it to the download mode, prepares Odin, ADB, an USB driver, connect it to this computer and start downloading. Odin says it failed to download but the phone is still stuck on the download mode, and I disconnected the USB several times (What do you need USB for if the download has failed?)
What have I tried? (Not in chronological order)
- ReiBoot, to get out of the download mode and fix the phone
- Factory Reset
- Restarting from the original recovery mode
- redownloads the tar.md5 file to my phone
What I think is the solution?
1. Give up and admit that the phone is broken (not recommended), or
2. Wait until the battery dies and try to boot it again
additional info
[If there`s a need for revision(s) like more infos, just ask in this discussion]
the rooting guide is from tenorshare.com (https://www.tenorshare.com/android-root/how-to-root-samsung-galaxy-s7-or-s7-)

Categories

Resources