{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
updated my n7 3g to 4.2.2 and now when i chose to unlock bootloader (with 4.2.1 chosen) it stops on waiting for adb mode when i write no.If i go to fastboot and write yes pertty much same,nothing changes...I got drivers and debugging on
help
Seems like adb is not working, most likely because of the new 4.2.2 security for adb debugging. I pulled my hair out for 3 hours the other night trying to get it to work. I had to uninstall the drivers, reboot, test, rinse repeat. I was using Wug's toolkit, it details everything pretty good.
Activate developer mode, enable adb, plug in your device, send an adb command (like adb devices). It will send back adb offline. Now look at your phone. You should see a screen about allowing adb from your computer. Allow it. Now once or twice, this prompt did not appear for me. I simply had to unplug and replug the device, then it appeared. Once it is allowed, test it by doing the old adb reboot bootloader and once there fastboot oem unlock and there you go!
Or you can continue with your tool kit at that point, up to you !!
Hi, FatalaS...
I'm not familiar with WugFresh's toolkit... or indeed any other toolkits... I'm more of a fastboot man.
I also generally don't tend to use adb much, except when I'm performing a full backup (via adb pull) to my laptop (which is infrequent, as it seems to take forever - a LOT of stuff to be backed up!).
I use fastboot primarily... for flashing custom recoveries and new kernels/boot.img's.
I do this by copying my chosen recovery.img file (currently TWRP, renamed as recovery.img) or a boot.img file (currently franco's, renamed as boot.img), into the same folder on my laptop, where I keep my fastboot and adb executables.
I shutdown my Nexus 7, and reboot into FASTBOOT/BOOTLOADER mode by pressing and HOLDING the VOL DOWN button, and whilst HOLDING, press the POWER-ON BUTTON.
Having connected my Nexus 7 to my laptop, I then check I have a valid FASTBOOT connection (via a command prompt window, open on the folder I alluded to above), with...
Code:
fastboot devices
This should report a serial number along the lines of something like this...
Code:
015d2424b1xxxxx fastboot
...and then... (and this is directly pertinent to your original question)...
Code:
fastboot oem unlock
...will unlock the bootloader - YOU DON'T NEED ADB FOR THIS - JUST ENSURE YOUR TABLET IS IN FASTBOOT MODE AND RUN THIS COMMAND.
I did this several months ago on my Nexus 7, and once done, it never needs to be repeated... unless you relock the bootloader at some point, with the surprisingly original syntax...
Code:
fastboot oem lock
------------
Having done this (unlocked the bootloader), you can then fastboot flash custom recoveries (like TWRP or CWM) with...
Code:
fastboot flash recovery <your chosen recovery.img>
...or flash CERTAIN (but not all) custom kernels, with...
Code:
fastboot flash boot <your chosen boot.img>
Some kernels consist of more than just a simple boot.img (such as franco's)... some put various files in various parts of /system and thus need to be flashed via your chosen custom recovery, in much the same way custom ROMs are flashed.
-----------
Hope this somewhat lengthy post helps...
Rgrds,
Ged.
You can't unlock 4.2.2 Android with 4.2.1 Toolkit the Android version MUST MATCH.
http://www.youtube.com/watch?v=GnHFtFTp-cc
Listen to this video CAREFULLY + read the Toolkit thread slowly and you will find your solution.
Related
Hey Everyone!
Its not new that there is quite some chaos regarding the fastboot mode on our device. Though some could access it, others could not. All that would happen when I tried to reboot into bootloader was that it would get stuck on the boot logo. Many said that the bootlogo itself was the fastboot mode. However lsusb on my linux term would not recognize anything attached. So I was quite sure there was some issue. Recently when I was having a chat with Nori, I could confirm that the same. It so happens that when he boots into fastboot mode, there appeared a tiny text at the left bottom of the screen would appear saying the device was in fastboot mode.
A little bit of research and experimentation, I figured out that there was an issue in the appsboot image on the Indian version. So, I flashed the Taiwan version of the aboot on my device and VOILA! I had fastboot mode! Here is how you can get it.
BEFORE I GO ANY FURTHER, I MUST WARN YOU THAT THIS IS HIGHLY RISKY IF DONE WRONG! THERE IS A RISK OF HARD BRICKING YOUR DEVICE! AND I AM NOT RESPONSIBLE FOR WHATSOEVER THAT HAPPENS TO YOUR DEVICE.
1) Head over to http://140.115.126.139:808/gplus_e7/E7_0301_v5832_IMG/ or here
2) Download the aboot.img and save it to the root of your sdcard.
3) Open up a terminal emulator or adb shell and type in the following code.
Code:
su
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
4) Thats it.. Now reboot into bootloader using any rebooter or using adb and you should see something like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(sorry for all the dust.. should have viped it I guess.. well, atleast shows how good the camera is..)
Good Luck!!
hi.
my device goes to fastboot mode but fastboot command is not working on it.. what can be pb..?
\Desktop\GenerelMobile_Elite>fastboot oem unlock
< waiting for device >
pc detects is "Android Composite ADB Interface" in the device manager..
adb reboot-bootloader is working or wol down + power on..device goes to fastboot mode..
but not working on root directory..
Code:
[email protected]_MOBILE:/ # fastboot reboot
fastboot reboot
[B]sh: fastboot: not found[/B]
127|[email protected]_MOBILE:/ #
this should be closed this does not work
gaganpattanayak said:
this should be closed this does not work
Click to expand...
Click to collapse
It works fine for me. Have you followed the instructions properly?
Yes it goes to the screen and then if you give a fastboot command something seems to happen but nothing happens
HI , my phone gionee e7 is in fastboot mode..I dont know how it got into this mode .. can you tell me how to exit from this mode and get the phone started
my fone is stuck on fastboot mode how to get over it ?
I have a SIM free ( unlocked ) P9 lite that I got from Car phone warehouse and I am wanting to update it to the latest version ie nougat. however I am confused by all the different variations ie VNS-L21C10B360 , VNS-L31C185B360, VNS-L31C636B361 etc that are floating around. My device is VNS-L31C432B131, how can i decide as to which update to use.
Also is there a way to determine if my bootloader is locked or not?
Thanks in advance.
Hello,
L31 is the 3GB of RAM version, the L21 is the 2GB of RAM one. Your device is L31, C432 means it's the european firmware and B131 is the firmware version. If you want to update tu Nougat you have to follow the L31 tutorial, and to determine your bootloader status you can do it in this way:
-Turn off the phone
-Press power button and volume up
-Your phone will boot to fastboot mode and you will see if the bootloader is LOCKED (Green) or UNLOCKED (Red)
I suppose your phone is still locked as you don't know how to verify the status
I have tried that and I only got three options.
Reboot System
Wipe data/Factory reset
Wipe Cache Partition
.
Oh sorry, you have to press power button and volume down.
I forgot that power up was to boot to recovery, I apologise!
Ive tried that and the phone just starts as normal
You can try using the computer then..
Download and install adb & fastboot minimal drivers
Allow debug USB in developer settings in the phone
Plug the phone to the computer
In the drivers folder open a CMD (shift + right click)
Type "adb devices" to see if the phone is detected
If yes then type "adb reboot bootloader"
Potato997 said:
You can try using the computer then..
Download and install adb & fastboot minimal drivers
Allow debug USB in developer settings in the phone
Plug the phone to the computer
In the drivers folder open a CMD (shift + right click)
Type "adb devices" to see if the phone is detected
If yes then type "adb reboot bootloader"
Click to expand...
Click to collapse
I have downloaded and installed ADB however I only have 4 items in the Folder
adb ( exe )
AdbWinApi ( dll )
AdbWinUsbApi ( dll )
Fastboot ( exe )
There is no drivers folder
The folder with the 4 files is the correct one, open the CMD there
Thanks for helping ( and putting up with me lol ) it seems that my bootloader is locked, however FRP (?) is unlocked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I am correct would the revolution rom work for me on this device ( https://forum.xda-developers.com/hu...t/24-12-16-revolution-nougat-rom-rc1-t3525138 ) or would I be better with something like this ( https://forum.xda-developers.com/hu...t/android-7-emui-5-0-vns-l31-l21-l23-t3513816 ) or by using this update ( http://www.droidviews.com/update-huawei-p9-lite-manually-official-android-7-0-nougat-emui-5-0/ )
If you want to update to Nougat I suggest you to unlock the bootloader, flash Meticulus' TWRP and then follow this guide:
https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932
someone use l31c636 please creat file oeminfo help me thanks
DISCLAIMER:
take care, this will erase all data on phone. I'm not responsible for any data loss. Follow the instructions on your own risk!
---------------------------------------
You updated to ZUI 3.5 using https://forum.xda-developers.com/zu...-to-zui-z2-t3928693/post79493369#post79493369 ? Congrats!
Once you updated to ZUI 3.5 you don't need to get unlock_bootloader.img anymore.
To activate developer option click 7 times on ZUI version under settings - system - about:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-
-
Once you did that you get developer options in settings - system:
Click on it and activate the options OEM unlocking and USB debugging
You can accept the following warning:
Now:
Setup ADB and Fastboot on your PC. (can be found here as well: https://forum.xda-developers.com/showthread.php?t=2317790)
Connect your Lenovo ZUK phone to the PC.
└ If you get a prompt on phone’s screen to Allow USB debugging, tap OK.
Open a command window inside the folder where you saved your adb and fastboot install (I suggest using C:\ZUK). To do this, open the folder and then “Shift + Right click” on any empty white-space inside the folder and select “Open command window here” from the context menu.
Once command window is open, issue the following command to boot device into bootloader mode:
adb reboot bootloader
Once in bootloader mode, issue the following command to unlock the device:
fastboot -i 0x2b4c oem unlock-go
└ You’ll see the following output:
...
OKAY [ 0.041s]
finished. total time: 0.041s
Now phone will reboot. Let the reboot finish completely. Then do "adb reboot bootloader" again.
now flashing twrp. Download latest twrp version here: https://twrp.me/zuk/zukz2row.html
Make sure the downloaded twrp version is located in adb directory as well. Rename it into twrp.img. Then in command prompt type:
fastboot flash recovery twrp.img
(if your device is not recognized check hardware manager for driver. You may use fastboot -i 0x2b4c flash recovery twrp.img instead)
Reboot your phone to system using the following command:
fastboot reboot
That's it. You unlocked bootloader and flashed twrp.
--------------------------------------------------------------------
Hello,
I have done evreything as you described in your "howto"
I have now unlock bootloader and TWRP installed. Each time I try to flash a custom rom I have "fail to mount /vendor (invalid argument)..." error.
Still the custom rom I have tried to flash were recent Pie roms so factory to vendor problem should not be the problem.
I think there is somethig here that I did not understood
Can someone help me please?
Thank you
fastboot does not accept the option -i
Thanks for the detailed description.
weimerd said:
DISCLAIMER:
take care, this will erase all data on phone. I'm not responsible for any data loss. Follow the instructions on your own risk!
---------------------------------------
5. Once in bootloader mode, issue the following command to unlock the device:
fastboot -i 0x2b4c oem unlock-go
└ You’ll see the following output:
...
OKAY [ 0.041s]
finished. total time: 0.041s
--------------------------------------------------------------------
Click to expand...
Click to collapse
I am on step 5 with fastboot oem unlock-go. However, it sas "fastboot: unknown option -i"
What may be the issue?
My phone is zuk z2 pro (z2121)
ZUI 3.5.3165
Android 8.0.0
Android patchdate: 5.02.2018
usb debugging is active
oem unlock is also done
"adb devices" shows me the device. I can also change into bootlaoder using the command "adb reboot bootloader". The phone is connected via
I am stuck and the phone still has the chinese rom, I cannot seem to proceed. Thanks for any pointers.
Hello everyone, I recently installed via twrp 3.5.0.9 the new official V12.0.5.0.QFJEUXM rom from the latest xiaomi eu stable rom (xiaomi.eu_multi_HMK20MI9T_V12.1.2.0.RFJCNXM_v12-11). I just wanted to see how it was, now, I can not install the recovery again to install the xiaomi eu. Someone know how to help me.
It is as if it does not recognize the device when I send it the adb command, although in principle it does.
Thank you first of all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
viru78 said:
Hello everyone, I recently installed via twrp 3.5.0.9 the new official V12.0.5.0.QFJEUXM rom from the latest xiaomi eu stable rom (xiaomi.eu_multi_HMK20MI9T_V12.1.2.0.RFJCNXM_v12-11). I just wanted to see how it was, now, I can not install the recovery again to install the xiaomi eu. Someone know how to help me.
It is as if it does not recognize the device when I send it the adb command, although in principle it does.
Thank you first of all.View attachment 5294485View attachment 5294487
Click to expand...
Click to collapse
Before flashing, try: fastboot devices
In Developer options, is OEM unlocking and ADB debugging enabled?
If fastboot devices does not recognize device, try another USB cable or uninstall USB drivers and try again
Yes , OEM unlocking and ADB debugging is enabled, and i had tried with original cable and other one. Thanks for your answer i will keep trying.
"Before flashing, try: fastboot devices" it doesn´t work.
Don't type reboot bootloader if you are already in fastboot
Just flash recovery.
Your address is long, try c:\adb\twrp.img
viru78 said:
Yes , OEM unlocking and ADB debugging is enabled, and i had tried with original cable and other one. Thanks for your answer i will keep trying.
"Before flashing, try: fastboot devices" it doesn´t work.
Click to expand...
Click to collapse
Seems that something is wrong with your USB driver on the PC - adb devices works but fastboot devices does not (where Bootloader is unlocked and OEM Unlocking enabled)
Try uninstalling the USB driver(s) on the PC or try another PC
yaro666 said:
Don't type reboot bootloader if you are already in fastboot
Just flash recovery.
Your address is long, try c:\adb\twrp.img
Click to expand...
Click to collapse
Or copy the (twrp) img file right into the ADB folder on the PC, and go with CMD into the ADB folder before running adb/fastboot commands
Then no paths are needed, just like:
fastboot flash recovery twrp.img
But that will not help him as long as fastboot devices fails
I thought about address length, sometimes adb has problem with it, worth a try
fixed, thanks for your answers, the problem was the laptop and drivers, i have had used other pc and install without problems.
Hello, Having a Lenovo TB-X606F tablet, I purchased a Lenovo Smart Dock, but cannot get it to work with this tablet. Is it possible to flash the tablet in TB-X606FA so that the dock are finally recognized? I installed the Amazon Alexa apk - Show mode and Lenovo Smart Dock Firmware Updater but nothing recognized
Thank you
thekiller91 said:
Hello, Having a Lenovo TB-X606F tablet, I purchased a Lenovo Smart Dock, but cannot get it to work with this tablet. Is it possible to flash the tablet in TB-X606FA so that the dock are finally recognized? I installed the Amazon Alexa apk - Show mode and Lenovo Smart Dock Firmware Updater but nothing recognized
Thank you
Sébastien
Click to expand...
Click to collapse
There are probably missing kernel drivers ?
You could try loading the X606FA ROM using LMSA. Use the off-line rescue option.
No guarantees it will work. It's an experiment, so it might brick your device. If it fails, LMSA might be able to restore the X606F ROM.
Hello, with LMSA I could flash with firmware TB-X606FA_S300269_210602_BMP for example? the 2 tablets are identical in terms of hardware I do not see why this would brick I can not find how to do it in LMSA it suggests that the firmware TB-X606F_S300320_210716_BMP Thank you
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello, I tried via LSMA now my tablet is running in a loop, I just manage to go to fastboot mode, what to do?
Thank
following that I tried to send the original boot.img by adb and here is what I have
following that I tried to send the original boot.img by adb and here is what I have
thekiller91 said:
Hello, I tried via LSMA now my tablet is running in a loop, I just manage to go to fastboot mode, what to do?
Code:
Your device has failed verification and may not work properly.
Please download boot image with correct signature or disable verified boot.
...
following that I tried to send the original boot.img by adb and here is what I have
Code:
fastboot flash boot boot.img
FAILED (remote: 'not allowed in locked state')
fastboot: eroor: Command failed
Click to expand...
Click to collapse
Have you unlocked your bootloader? To flash in fastboot, you have to unlock your bootloader first. If you didn't allow that in Settings before you started, then you'll need to reload your old ROM to do it.
The simplest thing to do is to rescue your tablet using LMSA. Make sure you are using the "manual selection" mode. Select you original tablet designation (TB-X606F). When Android boots:
enable developer settings
allow OEM unlock and USB debugging
unlock the bootloader
make sure you can load twrp (which tests that fastboot is working)
make sure adb is working in twrp (adb shell)
do a backup
Then you can start your experiment again.
Yahoo Mike said:
Have you unlocked your bootloader? To flash in fastboot, you have to unlock your bootloader first. If you didn't allow that in Settings before you started, then you'll need to reload your old ROM to do it.
The simplest thing to do is to rescue your tablet using LMSA. Make sure you are using the "manual selection" mode. Select you original tablet designation (TB-X606F). When Android boots:
enable developer settings
allow OEM unlock and USB debugging
unlock the bootloader
make sure you can load twrp (which tests that fastboot is working)
make sure adb is working in twrp (adb shell)
do a backup
Then you can start your experiment again.
Click to expand...
Click to collapse
I managed to recover the tablet with the stock rom and with LSMA, it detected the fastboot and restored the rom. On the other hand my smart dock remains incompatible with my tablet just because of a software, really bad on the part of lenovo! I try with LSMA in manual the FA model to see, I hope that it will not crash!
thekiller91 said:
I managed to recover the tablet with the stock rom and with LSMA, it detected the fastboot and restored the rom. On the other hand my smart dock remains incompatible with my tablet just because of a software, really bad on the part of lenovo! I try with LSMA in manual the FA model to see, I hope that it will not crash!
Click to expand...
Click to collapse
Hey, any success?