Develop Bugs

[Q] Need Assistance, I brick my Galaxy Nexus

Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!

So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?

cbs2002 said:
Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
Click to expand...
Click to collapse
The key piece of information for your symptom is in this line:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
The other lines do help provide background as to the other modes such as recovery and download working properly, which indicates the issue is not *serious*.
The symptom you state, where the device does not boot past the boot logo, usually means the device is not able to boot the kernel or boot past the kernel. The boot logo appears while the kernel is being loaded on the device. Generally, after the boot logo and kernel finish loading a boot animation appears which indicates the kernel has usually handed off to the Android OS to continue booting.
My approach would be to load a completely stock ROM in order to restore a working kernel and ROM to the device. I generally perform this step as a baseline to get everything back in working order.
In many instances the ROM is dependent on the kernel. Your situation requires at least a kernel to be loaded and in order to prevent any further issues, it would be best to load a ROM dependent on the kernel being loaded.
A simple way would be to grab the stock factory images from Google's site and load those back onto the device.
Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode.
Hope that helps!

Since you're rooted I'm going to assume you have ADB and the necessary drivers installed.
1.) Download a ROM. It doesn't have to be stock, you can choose any of the ROMs from the development section for your device. Most of the ROMs are packaged with a kernel already.
2.) Save this ROM file to the same folder where you have ADB installed.
3.) Boot your phone into CWM recovery and plug it into your computer.
4.) Use ADB to push the ROM zip file to your phone (/data/media). For example:
Code:
c:\gnex\>adb push rom.zip /data/media/rom.zip
5.) Use CWM to wipe data, cache, and davlik-cache
6.) Install zip from sdcard and flash the rom.zip.

RMarkwald said:
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
Click to expand...
Click to collapse
1. I am using GSM
2. Whenever I turn on my mobile, the 'Google' and 'Unlock' logo appears and then freeze, with no more respond at all
* I definitely mess up some system files, but don't know how to restore it because my PC do not recognize my mobile.
Thanks

I am seeing more and more of these threads about "bricked" nexus's is this an issue with how new the phone is or people not following instructions properly as they are too eager to root their phones?
All else fails flash back to stock and count yourself lucky.

To silow,
Thanks for your advice, but fail
1. I put adb.exe, adbwinapi.dll and fastboot.exe (3 files) under my PC C drive (i.e. C
2. I also put a stock Rom (rename as rom.zip) under C drive (i.e. C
3. Boot phone into CWM recovery and plug it into computer.
4. Use cmd command and type c:\gnex\>adb push rom.zip /data/media/rom.zip
5. It fails , It say "Access Denied" (in Chinese, but I translate it into English here)
6. How do I use ADB (it is a ADB.exe file, When I double click it, it only flash up a few page very fast and nothing happen)
Please assist!

To Joeykrim,
I agree that
"Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode."
But how? (according to my symptoms)

The command I gave you was just an example. I didn't spell out the exact details because I thought that you would know how to do it considering you rooted the phone.
If you put the adb.exe and AdbWinApi.dll file in your C: drive, make sure you copy the ROM file to your C: drive too. In the follow example I'm going to use "ROM.zip" but use the name of the ROM file that you downloaded. Also I am assuming you are on Windows XP.
1.) Boot your phone into CWM recovery and then plug it in.
2.) Go to your Start Menu and choose Run. Then type in "cmd" without quotes and hit enter to open a command prompt.
3.) Enter:
Code:
cd c:\
4.) Enter the following to make sure ADB can see your phone:
Code:
adb devices
You should see something similiar to this to confirm ADB can see your device:
List of devices attached
019B756F0C018012 device
5.) Enter the following command to copy the ROM file to your phone. Remember to replace ROM.zip with whatever the name of the ROM file is:
Code:
adb push ROM.zip /data/media/ROM.zip
6.) Use CWM to wipe data, cache, and davlik-cache
7.) Install zip from sdcard and flash the rom.zip.

To Silow,
You have been very helpful, but I fail.
"You should see something similiar to this to confirm ADB can see your device:
List of devices attached"
There is NO device number shown after the phrase 'List of devices attached'
To recap:
a) Phone is already plugged in my PC, under the Clockworkmod Recovery 5.5.0.2
b) adb.exe and AdbWinApi.dll file are under C: drive directly
c) Also type cmd in 'Run', a black Dos window shown C:\windows\system32\cmd.exe
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Pls don't give up on me!
: )

you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot (edit: wrong!)

Sounds like your ADB USB drivers are not correctly installed. While the phone is under CWM, when you plug it in is your computer attempting to install drivers for a new device?
Download these bare ADB Interface drivers.ADB USB Drivers
Go into Device Manager on your computer and check the device list for any unknown devices or "?" devices. If you need to update those drivers by pointing them to the drivers you downloaded and extracted from that link above.
When the ADB Interface drivers are correctly installed you should see Android Phone listed under under your Device Manager when it's plugged in with CWM recovery loaded.
---------- Post added at 02:36 PM ---------- Previous post was at 02:35 PM ----------
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.

silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
edit: i did appear to have one missing driver, my mistake. it was listed in device manager as "unknown - full"
its funny cause i never had to use adb from cwm before, never noticed

cbs2002 said:
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Click to expand...
Click to collapse
This symptom generally occurs from not having loaded the drivers for the hardware. As with the majority of hardware devices when being connected to a Windows machine, the drivers need to be loaded. Sometimes these are automatically loaded and other times they have to be manual loaded.
As an alternative and for future reference, the android-sdk package contains general USB drives which usually work for Google Nexus devices.
Generally, as this providers a *cleaner* install, best practice as recommended by Google is to download the whole android-sdk .zip and then from the installer download/install the pieces needed, such as platform-tools (containing adb) and USB drivers as opposed to extracting out the adb.exe and .dll file and installing manually.
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
Agreed. To add greater clarification so there is no confusion: adb can't be used from the bootloader.
The /sbin/adbd daemon on the device is only loaded while in normal android boot mode or in recovery mode as called by the init.rc (or on some older devices, recovery.rc) file in the boot process.
Bootloader mode will only work with fastboot while it is in fastboot usb mode.
On some devices, the bootloader has a separate menu for fastboot and on other devices, the fastboot mode is directly entered when entering the bootloader.
Hope that helps clarify!

To silow (and all other helpers)
1. I fail
2. The ADB USB drivers in my PC should be fine as in Device Manager , I can see Android Phone with Android Composite ADB Interface. (No exclamation mark)
3. On the other hand, whenever I plug my mobile into PC, I can see "Unknown-Full"
4. In DOS, when I first type "adb devices" it shows
* daemon not running. starting it now on port 5037*
*daemon started successfully *
List of devices attached
(but NO device number shown!)
5. When I enter adb devices second time, it shows
List of devices attached (No device number shown)
Thank you so much , but it is Hong Kong time (my place) at 0511 am , I didn't sleep all night and I am very tired.
If you don't mind (especially big helper Silow), please give me email so that I capture screen picture and show you in detail (hope it may help)
my email is
[email protected]
I need to sleep now, I will check my email and see you guys or come back this Forum later (several hours later, as I really need some sleep right now)
Pls don't give up on me as this is an expensive mobile. I think the hardware is fine, just need to figure out a way to unbrick it.
Thanks, and see you!

What you need to do is right click on "Unknown-Full" and click on "Update Driver...". Then choose "Install from a list or specific location". Make sure "Search for the best driver in these locations." is checked and "Include this location in the search:" is check. Click on the Browse button and browse to where you extracted the driver files from the link I posted above. Click Next and this should install the correct drivers for you. Afterwards try "adb devices" again to see if ADB now reconizes your device.

To Silow,
Fail.
1. Already installed the drivers you gave me (and there is no 'Exclamation' Mark) in Device manager
2. Situation is the same , Cannot recognize my mobile (i.e. no Device No. after entering adb devices)
3. "List of devices attached" shown in DOS video but without any number.
No other method?
My mobile is really 'bricked' to death?

To Silow and all,
Something important
1. When choose 'install zip from sd card' under CWM, a list of old folder names remains
(e..g gameloft, DCIM, Pictures, etc). That means almost all old files, folders are STILL in my mobile!
2. I have already use the funcion 'Wipe data/factory reset', 'wipe cache partition', ' Wipe Dalvik Cache'
Perhaps my CWM has problem?

What happens when you update drivers for Unknown-Full?
Boot into fastboot and see if your computer recognizes the phone by checking device manager. The key here is to get your computer to see the phone either in fastboot or CWM.
Perhaps try another cable, USB port, or new computer.
The goal is to get Android Phone ADB Composite Interface to show up in device manager either in Fastboot or CWM. Without that done you cannot use Fastboot to flash nor ADB to push a zip file to the phone.
Sent from my Galaxy Nexus using XDA App

[Q] Trouble with flashing new recovery

Hey everyone,
Alright so I have been trying to root my phone for the past 4 hours. I have unlocked it and flashed a custom recovery using adb. Or at least I thought I did. I tried flashing the clockworks recovery and when I would reboot it into the recovery, I would get an icon of a phone and an exclimation point. I assumed a bricked the phone and freaked out. A minute later the phone rebooted out of recovery and works fine afterwards. So I assume that the problem is the recovery. Something went wrong and I am not sure what.
Here are the steps I followed:
I was fine up until step four when I was trying to flash superuser.
No idea what to do from here.
HTC Unlocked = Bootloader is unlocked?
Not to take away from the OP, but i created a guide for a guy here at work and thought others might benefit from it.
Unlock Bootloader and Root
Unlocking your bootloader will wipe all data from your phone. Meaning you will loose everything make a backup.
Step 1: ADB Installation Instructions. NOTE:You must have ADB installed on your PC even if you use method 2b to unlock the bootloader. You will need adb to install recovery in Step 4.
1. Go to http://developer.android.com/sdk/index.html and download the sdk.
2. Follow installation instructions found here. Note: This is not a forum for this device DO NOT do anything but the adb installation on your system.
Step 2a: Download software from HTC to allow your bootloader to be unlocked.
1. Go to http://www.htcdev.com/
2. Login to the website. NOTE: Register for an account if you haven’t already. You must provide a valid email address.
3. Select “All Other Supported Models” from the drop down list and click “Begin Unlock Bootloader”
4. Follow online instructions.
1. SuperUser http://androidfiles.org/securekey.ph.../superuser.zip - Copy this file you phone. Special thanks to jmztaylor his link.
2. Recovery of your choice TWRP Recovery http://forum.xda-developers.com/show....php?t=2161702 or CWM Recovery http://forum.xda-developers.com/show....php?t=2161706. Put this file in the ADB Tools folder. NOTE: You must type the name of this file perfectly when using adb to flash it in step 4.
Step 4: Using ADB to install recovery
1. Open command prompt ( shift + right click, then choose “Open command window here”) and type “ADB devices” you should see you phone listed, if you do not start over at Step 1. NOTE: Phone must be plugged in and USB Debugging must be checked in settings.
2. Type “ADB flash recovery recovery.img” without the quotes. NOTE: the red is actually the title of the recovery file that you copied in step 3. If it’s different substitute your files name instead.
3. Once complete type “ABD reboot recovery”.
4. You should at this point backup your device
5. Once you create a backup, Choose install and navigate to the SuperUser file you put on your phone in Step 3.
6. If all goes well you are now rooted. Select reboot system to restart phone.
There is some very good information here but its spread out pretty thin. Guides IMHO are very usefull to fill the gap between devs/powerusers and the newbs.Most people that come here have a hard time with the things we take for granted such as adb commands, or adb its self (most will be setting it up for the first time). I tried my best to put it in a knowledge base that everyone can understand if for some reason you do not understand what i was trying to say please ask. I don't own this phone, just helped a friend root his, but if you need to get ahold of me pm me. I'll get back to you as soon as possible.
Any help? Just trying to get rid of the bloatware -_-

Did you copy superuser to your phone? And are you sure you are using the correct file location for adb in the command prompt? You must make sure you are and that all files you want to flash are also in the same folder as adb. Please respond if you have superuser on your phone and if you are positive you are using the correct adb folder location for the command prompt. I'm not the best at this however, I read up a lot on it just to root my phone. Took me 4 hours about as well, but that was before the recoverys came out. I suggest trying to flash twrp recovery, it's a bit buggy (for me) but I find it easier to use.
Sent from my HTC One VX using xda app-developers app

Code:
ADB flash recovery recovery.img
that is your problem to start with its not "ADB flash"
boot your phone into bootloader with usb connected to PC, Phone should read "fastboot"
Go the your adb directory in command prompt.
ex.
Code:
C:\PcUser\Master\Androidsdk\adb\
Make sure all drivers are installed, from CMD prompt window type "fastboot devices" to check your phone is showing.
if you see your device then you can type
fastboot flash recovery [drag your recovery image into cmd window] and hit enter and it should flash
once recovery is flashed you can either "fastboot Reboot" or on the phone use the Vol rockers to navigate to menu and hit bootloader then from there choose recovery

Hi,
I have the same issue about 2 days, I install TWRP Recovery and all it's ok, and flash in fastboot mode with adb like ilostchild tolds You.

It seems that I met the same problem.
My issue is the phone only boot into CMW mode, although I tried to restart it many times. When connect to usb cable, lappy did not recognize the phone so I can use adb command.
Please help me.

I can't make ADB recognize the device, I already installed the SDK the HTC Sync program but the device appears either as "My HTC" or "Android 1.0" and won't appear under "adb devices", any help? I have been googling for 3 days for a solution but I haven't found anything so far.

zeratos said:
I can't make ADB recognize the device, I already installed the SDK the HTC Sync program but the device appears either as "My HTC" or "Android 1.0" and won't appear under "adb devices", any help? I have been googling for 3 days for a solution but I haven't found anything so far.
Click to expand...
Click to collapse
Try using another computer!!! Install all neded drivers, searxh google and let windows automaticly install some. Connect via fastboot and it should say
Fastboot usb.
Also....dont search for adb devices, just enter commands starting with fastboot like... Fastboot install recovery cwmrecovery.img

spooky_ghosty said:
Try using another computer!!! Install all neded drivers, searxh google and let windows automaticly install some. Connect via fastboot and it should say
Fastboot usb.
Also....dont search for adb devices, just enter commands starting with fastboot like... Fastboot install recovery cwmrecovery.img
Click to expand...
Click to collapse
I already tried all those things you mentioned, I have been looking for 3 days for a solution for this problem on google without any luck, the device doesn't recognize any command either and I already set up a virtual machine and tried on that machine as well. u_u

Uninstall HTC sync then try adb devices be possitive you are using the correct location for adb. Usb debugging MUST be on as well. Copy paste the commands into the prompt to make sure you are entering them right. Be sure you have the downloaded files in the same folder you are using with adb.

Johann12911 said:
Uninstall HTC sync then try adb devices be possitive you are using the correct location for adb. Usb debugging MUST be on as well. Copy paste the commands into the prompt to make sure you are entering them right. Be sure you have the downloaded files in the same folder you are using with adb.
Click to expand...
Click to collapse
Already tried uninstalling HTC Sync, after that I deleted every trace of it. USB Debugging WAS ON before the phone crashed but I can't activate it now because the phone keeps looping between reboots.

Try to flash it via htc sync. Download the update and rewrite everything!
Sent from my HTC One VX using xda app-developers app

[Q] HTC Desire HD not recognised - can't install custom ROM's problem with fastboot

So basically i followed this guide - wiki.cyanogenmod.org/w/Install_CM_for_ace
Let's start from the first part wiki.cyanogenmod.org/w/Install_CM_for_ace
I plug in phone, i can see it in my PC as D drive but nothing more, after command "fastboot devices" i get 0 info - just like no devices were connected, but after i write "adb reboot-bootloader" my phone goes into this white screen. After this message about unrecognised device connected to USB appears. From now i can't use command "astboot flash recovery your_recovery_image.img"
I also has question, what does command "fastboot oem get_identifier_token" stands for? After writing this command i get info "waiting for device....".
I've also has question - why I unlock phone? What does it stands for? Does unlock means the same as rooting phone?
My System is Windows 8.1 64 bit.
Maybe i should install some HTC drivers or something like this? I installed HTC Sync, then uninstalled it, so just pure drivers should be left on PC but it still do not help me :/
USB debugging is on.

Fastboot issue on windows 8.1
I'm experiencing exactly the same problem as you. I'm on windows 8.1 and am unable to use the fastboot command. Have you been able to find a solution to it? Or have you been able to root your mobile? The HTC Desire HD community here seems to be not very helpful since your thread is months old and nobody has cared to help you with it.

maciek1o3s said:
So basically i followed this guide - wiki.cyanogenmod.org/w/Install_CM_for_ace
Let's start from the first part wiki.cyanogenmod.org/w/Install_CM_for_ace
I plug in phone, i can see it in my PC as D drive but nothing more, after command "fastboot devices" i get 0 info - just like no devices were connected, but after i write "adb reboot-bootloader" my phone goes into this white screen. After this message about unrecognised device connected to USB appears. From now i can't use command "astboot flash recovery your_recovery_image.img"
I also has question, what does command "fastboot oem get_identifier_token" stands for? After writing this command i get info "waiting for device....".
I've also has question - why I unlock phone? What does it stands for? Does unlock means the same as rooting phone?
My System is Windows 8.1 64 bit.
Maybe i should install some HTC drivers or something like this? I installed HTC Sync, then uninstalled it, so just pure drivers should be left on PC but it still do not help me :/
USB debugging is on.
Click to expand...
Click to collapse
make sure you have a working usb cable
1) your phone must be unlocked to flash a new rom
2 )Our phones are locked by HTC to protect the phone from unwanted things
3) HTC official web site helps you to unlock your phone ,follow the instructions as they have mentioned,it is too easy
http://www.htcdev.com/bootloader
every thig is explained here
3) for root try this
http://forum.xda-developers.com/showthread.php?t=2169515
4) download rom you want and copy it to sd card
shut down your phone ,push power+volume down button
on bootloader screen you must see UNLOCKED
choose fastboot
plug it to PC
you LL see fastboot Usb
On PC ,copy and paste the boot.img file of the rom to fast boot folder (it is in the nameofrom.zip )
open a command windows on this folder
write fastboot devices
fastboot flash boot boot.img
Enter
:good::good::good:here are the some links and videos to help you on flashing boot.img
http://www.youtube.com/watch?v=5xVl2dBTnmI
http://d-h.st/6LC
4) then go recovery on phone
wipe data factory cache dalvik cache and install zip from sd card
choose the rom
and restart your phone
5) identifier_token is kind a code which HTC sends you , it belongs your phone to unlock your phone
6) Root and Unlock are different things also there is another guy, it name is S-off
7) Windows 8 maybe will have problem , but windows 7 and windows xp are OK
8) make sure close antivrus and firewall
I hope these will help you

[Q] Help installing CM11 on My Ouya.

Hi,
I'm attempting to convert my Ouya to a regular Android device and I'm starting to work with the various manuals that exists
in the 'development' section of the forum.
I've performed the following steps:
1. installed the ADB drivers on Windows 7
2. connected the Ouya to the computers and fix the device manager to detect is as ADB driver.
3. checked that the device it detected (using "adb devices" command).
4. executed the 'adb reboot bootloader' command.
at this point the Ouya (with a wired keyboard connected) rebooted and the TV turned black (but it still detect the HDMI).
5. checked if the device is connected in fastboot, using the command: fastboot devices.
6. executed the command: fastboot boot OuyaCWMrecovery6.0.3.2.img
and it stuck in: 'downloading 'boot.img' ...'
Anyone knows what the problem is?

Anyone?
Please!!
section51 said:
Hi,
I'm attempting to convert my Ouya to a regular Android device and I'm starting to work with the various manuals that exists
in the 'development' section of the forum.
I've performed the following steps:
1. installed the ADB drivers on Windows 7
2. connected the Ouya to the computers and fix the device manager to detect is as ADB driver.
3. checked that the device it detected (using "adb devices" command).
4. executed the 'adb reboot bootloader' command.
at this point the Ouya (with a wired keyboard connected) rebooted and the TV turned black (but it still detect the HDMI).
5. checked if the device is connected in fastboot, using the command: fastboot devices.
6. executed the command: fastboot boot OuyaCWMrecovery6.0.3.2.img
and it stuck in: 'downloading 'boot.img' ...'
Anyone knows what the problem is?
Click to expand...
Click to collapse

section51 said:
Anyone?
Please!!
Click to expand...
Click to collapse
Did you try the oneclick install in the android development page?(http://forum.xda-developers.com/showthread.php?t=2350900) Then after that, update your recovery to the latest and then install this.... http://forum.xda-developers.com/showthread.php?t=2692836

jcgagtv699 said:
Did you try the oneclick install in the android development page?(http://forum.xda-developers.com/showthread.php?t=2350900) Then after that, update your recovery to the latest and then install this.... http://forum.xda-developers.com/showthread.php?t=2692836
Click to expand...
Click to collapse
I've used both links that jcgagtv699 sent me and I was able to install the OuyaCWMrecovery6.0.3.2.
From there I've upgraded the version to 6.0.4.8 and start installing the Ouya Bootmenu (http://forum.xda-developers.com/showthread.php?t=2692836)
and after it was installed successfully I get a menu when the ouya is loaded:
Normal boot
Alternate boot
Recovery
Failsafe
Bootloader
but the problem is that on matter what option I choose I get a RED screen with 'install from zip file'.
Help please!!!

Sounds like you only have the Bootmenu installed. From here you need to install cm11 at the "install from zip file" point.

problem with fastboot twrp flashing

my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.

Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
try upgrade your android sdk on your pc

Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful

i am trying to flash twrp there is no folder called adb i have installed the 15 second adb and all so i have got this minimal adb flashboot and i tried with that and got this ---- FAILED (remote: Flashing is not allowed in Lock State). i have granted all usb and oem unlocking. please help with this

Phone shows unlocked during the boot?
I had the same Problem,after a Factory Reset works for me.
I am on Miglobe-Rom Miui10 8.6.28.
Minimal ADB is enough.
Or use this from Attachment.
Unpack with Win.zip and copy Twrp in this Folder.
Conect the Phone with your Pc ,boot into Bootloader and click "cmd-here.exe"
Use this Command
fastboot flash recovery twrp-3.2.1-3-whyred.img

@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J

gamebenchjake said:
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
Click to expand...
Click to collapse
Have you fixed your app to run on Magisk-SU ?

otonieru said:
Have you fixed your app to run on Magisk-SU ?
Click to expand...
Click to collapse
Hey Otonieru,
Not yet, but I've got one of the engineers working on it - hopefully it'll be up in the next 30 days or so

Same problem here after updating my gcam was not working was enabling hall again but it is not booting into twrp

Redmi Note 5 pro
So my Bootloader is locked,
My phone stuck in MI recovery idk how.
I cant install MIUI via fastboot. Im stuck ..
Can anyone please help me here not sure how to proceed further.

If you have made sure that you have all the drivers installed and still have not solved, you need to use an Intel-based PC / notebook and use a usb 2.0.

”Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful”
i did that but it is showing failed（too many links）and "press any key to reboot" showing on my phone's fastboot screen

Fastboot boot recovery.img flashing problem on Redmi note 5 pro
My bootloader is unlocked and my oem as well as usb deb is on. After i connect my phone in fastboot mode to my pc. The cmd shows fastboot devices but when it comes to fastboot boot recovery.img flashing device get disconnected. Plzzzzzz let me know a solution for this. A solution for this will be highly appreciateable.