Hi All,
Trying to do what should be simple - install TWRP , then omnirom.
Have a new le pro 3, running stock firmware.
have enabled usb debugging, enabled oem unlock.
I can see the le pro 3 in adb devices. I then reboot (adb reboot bootlader).
Phone goes into fastboot. But fastboot devices, or any other command cant see the phone in fastboot mode..
Appreciate any help.. I'm at a loss. Thanks!
Even if ADB show your empty list, when you're at bootloader you can flash TWRP... Look my thread about brick.
Do it with flashing guide... You should also unlock in bootloader mode. And check the status.
For anyone that cares - on a Macbook pro retaina (with windows 10 as VM) - I could only see phone in adb, not fastboot.
installed fastboot for OSX, and ditched the virtual machine, and voila.
Related
Hai all , I am new here.
I need some help to unbrick my device. i tried almost all method and still no luck. the only method i havent tried is DFC, but i dont prefer to do it since its pretty complicated.
My device run rom Global Stable Miui 7 and i flashed Developer rom Global using EDL download mode.
there was an error and now my device stuck in Mi logo. I can still access Mi bunny fastboot ( vol down + power)
So far I have tried 3 methods
Method 1: reboot to fastboot mode, plug to pc, open ADB cmd prompt and type fastboot oem EDL. But no success because device is still locked bootloader.
Method 2: reboot to fastboot mode, plug in to pc, download fastboot EDL cmd from xda forum, unzip then run edll.cmd, device reboot to mi logo again.
Method 3: in Mi logo, plug in to pc, open cmd prompt, type Adb reboot edl, press enter but device cannot reboot to edl mode because it says I need to tap on confirmation dialog on device. But its not possible since device only load up to mi logo
Download the latest stable fastboot ROM from here http://en.miui.com/a-234.html then flash it.
Sent from my Redmi 3S using Tapatalk
If only it was that easy. I've tried 3 methods above but still no luck. Use Adb reboot edl, fastboot oem.
How to flash if its only stuck at mi logo
Because I had this exact same thing happened before. What I did was while it kept bootlooping at the Mi boot splash I held down Vol - + power until fastboot mode pops up. Then you'd be able to flash.
Sent from my Redmi 3S using Tapatalk
Trovies said:
If only it was that easy. I've tried 3 methods above but still no luck. Use Adb reboot edl, fastboot oem.
How to flash if its only stuck at mi logo
Click to expand...
Click to collapse
First off you cannot just unlock the bootloader easily, like in fastboot or anyhow, you need to follow the guides. And this is possible by the way only with a working Dev rom.
Well so now, you've to get miflash tool and flash either stock rom, or dev rom.
You simply hold power and volume down as long (can take some time) as it will show "fastboot" and some android art.
Then you follow the guides to flash either stock rom or dev rom using fastboot, and you're good to go.
I don't see why this wouldn't be working for you, try to stick exactly to what i said. If you don't know how to use Miflash then search at en.miui.com
Trovies said:
Hai all , I am new here.
I need some help to unbrick my device. i tried almost all method and still no luck. the only method i havent tried is DFC, but i dont prefer to do it since its pretty complicated.
My device run rom Global Stable Miui 7 and i flashed Developer rom Global using EDL download mode.
there was an error and now my device stuck in Mi logo. I can still access Mi bunny fastboot ( vol down + power)
So far I have tried 3 methods
Method 1: reboot to fastboot mode, plug to pc, open ADB cmd prompt and type fastboot oem EDL. But no success because device is still locked bootloader.
Method 2: reboot to fastboot mode, plug in to pc, download fastboot EDL cmd from xda forum, unzip then run edll.cmd, device reboot to mi logo again.
Method 3: in Mi logo, plug in to pc, open cmd prompt, type Adb reboot edl, press enter but device cannot reboot to edl mode because it says I need to tap on confirmation dialog on device. But its not possible since device only load up to mi logo
Click to expand...
Click to collapse
Did you unlock developer mode as in my case I am also stuck in bootloop and fastboot oem edl is not working as developer mode is disabled thus oem is also disabled.
Hey!
I had the same Problem.
Flashing with Miflash was unsuccessfull and then EDL was locked. You can check this when the device is in fastboot and send "fastboot oem edl". Then there may be the message that EDL is locked. In that case you have to build a "deep flash cable". It is pretty easy. You can check this tutorial:
http://en.miui.com/thread-310325-1-1.html
But I would build it another way: Just cut a USB cable and reconnect all wirepairs with the open copper. Now you can just put "ground" and "data+" togehther and follow steps 7 to 9. At point 10 you can just disconnect the wires "ground" and "data+" again, so that all wires are connected normally again. Now you are in EDL and can flash with MiFlash.
Hi guys,
I'm having problems unlocking bootloader.
The phone enter into fastboot mode but when I type "fastboot oem unlock-go" in the cmd of windows it doesn't recognize my device.
I have installed Minimal ADB and Fastboot and I have installed ADB Driver installer too but it doesn't recognize the device.
Can anybody help me with this please?
I need to unlock it because I want to root it.
Thanks
Have you tried unplugging and replugging when the phone goes into fastboot mode?
I just got my pro 3, did the OTA to the .19 software and unlocked and rooted just today and my girlfriend's very very fresh windows 10 install.
If that doesn't work just delete the adb driver, replug the device and windows should install the same drivers I used.
hello, i have problem fastboot mode, it detect my phone but in device manager not Identify the device. only show (!Android)
but in adb it detect when turn on devices. i want unlockbootloader to install custom rom
MOD can close this thread. done by install driver Android device to Android bootloader interface (windows 10 pro)
I am a Noob, trying to unlock the boot loader on ny Redmi 2 Pro. However I get the following message when using the MiFlash Unlock, downloaded form the MI site.:
Couldn't unlock
Device basic data verification failed. This device couldn't be unlocked.
I have created a Mi Account, signed into it on both my phone and laptop.
I want to install a lightweight ROM with only the Google apps that I really use, and according to my research, this is the first step before installing TWRP.
Any idea why I get this error?
You don't have to!, There's NO bootloader lock on Redmi 2/2prime/2pro, it's unlocked since out of the box.
xehed said:
You don't have to!, There's NO bootloader lock on Redmi 2/2prime/2pro, it's unlocked since out of the box.
Click to expand...
Click to collapse
Thank you xehed!
Do you perhaps know where one can find the correct Win 10 x64 drivers for the Redmi 2 Pro?
I have visited the Xiaomi Geek website and downloaded the Xiaomi Redmi 2/2A/2 Prime/2 Pro ADB drivers but when I run the adb device command it does not seem to find my device.
I have enabled Developer Tools and enabled USB Debugging, booted into Fastboot Mode (Power and Volume Down), plugged it in and ran the command, but nothing.
Does one need to root the phone first before running ADB commands as well as installing TWRP?
Any ideas?
*EDIT*
When I run the ADB command "adb devices" it says:
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
and then just goes back to c:\adb>
In Control Panel under hardware it says "Android Phone" and then under that "Android Bootloader Interface"
I think I have won... My nerves! lol
rdk_usr said:
Do you perhaps know where one can find the correct Win 10 x64 drivers for the Redmi 2 Pro?
I have visited the Xiaomi Geek website and downloaded the Xiaomi Redmi 2/2A/2 Prime/2 Pro ADB drivers but when I run the adb device command it does not seem to find my device.
I have enabled Developer Tools and enabled USB Debugging, booted into Fastboot Mode (Power and Volume Down), plugged it in and ran the command, but nothing.
Does one need to root the phone first before running ADB commands as well as installing TWRP?
Any ideas?
Click to expand...
Click to collapse
You can install/flash twrp through device itself, no need to use PC.
Nice
Hey guys, I know this isn't super active anymore, but I tried looking and tried posting elsewhere, and I can't find the answer I need. I'm sure it's something super simple I've overlooked.
I was gifted a 2015 Nvidia Shield TV Pro that was never used, so when I turn it on it gets stuck forever asking for my google login and won't proceed (like this thread here).
I can access the fastboot menu on the unit, and I've installed the PC drivers - BUT
When I open command and type "adb devices" it shows no devices connected.
I'm TOLD this is because I need to activate USB debugging on the unit, but how can I toggle on the USB debugging if I can't get past the google sign-in for a first-time set up?
Am I approaching this wrong?
PLEASE help!
Hello, I have exactly the same issue.
I would be really grateful if someone could help us.
i think you must set your SHIELD in FASTBOOT mode and after flash the stock firmware from https://developer.nvidia.com/gameworksdownload (you can't set FASTBOOT mode from ADB because of the wrong login)
to set fastboot mode look here : https://nvidia.custhelp.com/app/ans...invoke-the-android-fastboot-menu-on-shield-tv
Thanks conduisant! It helped.
I have spent some time to flash new recovery:
How far I was able to proceed:
I downloaded ADB Fastboot drivers
I downloaded recovery image (nv-recovery-image-shield-2017-atv-8.2.3)
I connected Nvidia Shield 2017 (model: P2897) with USB-A-to-USB-A cable to the PC
I was able to see "unknown device" so I installed ADB drivers (SHIELD_Family_WHQL_USB_driver_201801)
In device manager I can see my shield (as a Android Bootloader Interface)
I can access fastboot (pressing A+B on controller during turn on of shield)
I opened CMD and type "fastboot devices" - press enter - I can see my device is listed "03xxxxxxx fastboot"
I am able to execute "fastboot oem unlock", so bootloader is unlocked
I am able to write recovery image by using following commands written in instructions:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot oem lock
fastboot reboot
(no errors, everything was "OKAY")
But after the device restart , I can post only until the nvidia logo and that is it. Unfortunately I do not even know which was the original (stock) version of system in nvidia shield pre-installed. I tried to flash several versions of recovery images, but nothing helped. I can still see only nvidia logo :-(
But what I noticed, my Fastboot looks pretty different. I do not see my bootloader version, also some options are missing (lock bootloader, unlock bootloader etc.)
I also tried another options - boot recovery kernel, safe mode, but only nvidia logo every time.What is strange, when I turn-on the device, the Fastboot is automatically booted (I do not even hold A+B to initiate fastboot) I need to select continue.
So now I am not even able to try login into the shield anymore. I guess I already bricked the device :-(
what you have done is pretty correct !
Shield seems to be hard bricked, you can also try to flash TWRP + lineage OS ROM only to see if the SHIELD still not boot...i've no other idea
Thank conduisant for your effort!
Unfortunately, I am not able to boot into the TWRP.
I tried to flash TWRP what I have found here on forum:
UNOFFICIAL-twrp-3.0.2-ALL-Shields-build2.zip
But no success.
I tried to also flash official TWRP:
twrp-3.2.3-0-foster.img
But also no success.
I do not know which offical recovery to flash before LineageOS ROM (or it does not matter?)
Unfortunately, for some reason my gamepad in Fastboot stopped working (gamepad is connectied via USB to the shield, closest to HDMI port)
It just rumble when Fastboot booted and blinks blue led. I tried to charge gamepad - or - another nvidia shield gamepad but it does not work.
Also USB keyboard does not work. Looks like the USB port does not work properly anymore, so I am not able to click "Continue" in fastboot anymore to post at least until nvidia logo.
Luckily, the bootloader is still unlocked, so I am able to flash anything but I have already lost my mind.
I need another coffee and one full-day of meditaion.
i've got 2017 SHIELD, and i've flashed this TWRP last days + this LINEAGE OS : and all working good
TWRP = https://eu.dl.twrp.me/foster/twrp-3.7.0_9-0-foster.img.html
LINEAGE OS = https://download.lineageos.org/foster
when USB debugging is ON, only one USB port is activate for USB devices (keyboard for example) : it's the port near HDMI, the other port (near fan grid) is for ADB connection for the PC