Related
Hello, I was happily using a previous miui build and updated using ROM Manager and it was going fine until the phone stopped being able to recognise the SD card whatsoever, so I tried looking that up, and was finding things about reformatting memory cards, trying different ones etc. I tried all these things to no avail, I am now trying to RUU it back to a stock Sense ROM in the hope that will fix the SD card problem but when I try to connect it via USB to the PC it isn't recognised at all. I've tried installing HTC Sync etc. I've no idea what to do anymore?
ANY ideas much appreciated!
Thanks~
You have a classic USB brick. Don't panic, it's pretty frequent. Try this: http://forum.xda-developers.com/showthread.php?t=691639&highlight=usb+brick
It says on that article ' SD card functionality has to work' at the minute the Desire won't recognise the SD card whatsoever!
When they are giving these instructions, are they assuming that your phone is connected to a computer and in the adb thing?
Thanks so much!
matthewamac said:
It says on that article ' SD card functionality has to work' at the minute the Desire won't recognise the SD card whatsoever!
When they are giving these instructions, are they assuming that your phone is connected to a computer and in the adb thing?
Thanks so much!
Click to expand...
Click to collapse
Retarded post: Download a terminal program and: For this, do 'fastboot oem enableqxdm 0' in fastboot mode. Strike that.
Can you boot in Fastboot ? Back arrow + power.
Is your phone visible to the computer in fastboot ?
Don't jump into restoring an RUU as you will really be in trouble then!
Trust me, I've bricked mine and gone down this road to put it right and it can be done.
Get hold of Android-SDK (Google it), get that installed and prepare to learn. In my case I managed to restore SD card functionality and thought I had won, then discovered that I still had a USB brick. Nevertheless, many hours reading and several vodkas later I had it fully restored.
If you still have clockwork recovery on the phone (I'm assuming you're using that?) then it's a pretty easy fix, don't panic! And above all, don't attempt to go back to stock as then you'll still have a knackered phone but with no root to recover it (although I doubt you can if your phone can't read it, unless you learn the fastboot stuff and flash the RUU before actually fixing the problem).
The thread linked gives some idea, there's also a lengthier one, search 'USB brick'.
And good point by paul.c, that would be far simpler but I've never tried it myself - although esentially that is indeed the command required to get the SD card working again.
Just beware that getting the SD card working may not be the end of your woes, you may then find (as I did) that USB functionality is broken and bluetooth doesn't work, classic 'USB brick' symptoms. Again, pretty easily fixed.
paul.c said:
Retarded post: Download a terminal program and: For this, do 'fastboot oem enableqxdm 0' in fastboot mode. Strike that.
Can you boot in Fastboot ? Back arrow + power.
Is your phone visible to the computer in fastboot ?
Click to expand...
Click to collapse
Yes, I can get to fastboot ok and the phone's recognised in it. I've been trying to use the command prompt & do 'adb devices' but that's not working it states 'adb' is not recognized...etc. Should I be doing the 'fastboot oem enableqxdm 0' in a terminal on the phone or in the SDK on my computer ?
matthewamac said:
Yes, I can get to fastboot ok and the phone's recognised in it. I've been trying to use the command prompt & do 'adb devices' but that's not working it states 'adb' is not recognized...etc. Should I be doing the 'fastboot oem enableqxdm 0' in a terminal on the phone or in the SDK on my computer ?
Click to expand...
Click to collapse
Adb only works when running a rom. You have to run this comment in android sdk on your computer.
Swyped from my HTC Desire using XDA App
MatDrOiD said:
Adb only works when running a rom. You have to run this comment in android sdk on your computer.
Swyped from my HTC Desire using XDA App
Click to expand...
Click to collapse
So for Android SDK should you be properly booted or should you be in the Fastboot screen?
matthewamac said:
So for Android SDK should you be properly booted or should you be in the Fastboot screen?
Click to expand...
Click to collapse
If you have to issue fastboot commands your phone has to be in fastboot.
paul.c said:
If you have to issue fastboot commands your phone has to be in fastboot.
Click to expand...
Click to collapse
My SDK is working fine for commands such as 'ADB Devices' now but when I go into Fastboot and give the command 'fastboot' it states that it's not recognized! Do you have to have S-Off for this to work?
Well... you start your phone.. by pressing.. Vol down and power.. than connect your phone with usb cable to pc ... open command prompt.. got to your sdk folder "platform-tools' and than enter ADB or Fastboot command..
But when you connect your phone to PC.. check if ADB drivers are installed.. go to device manager and check if your phone is recognised as ADB interface under Android Phone
jhonybravo4u said:
Well... you start your phone.. by pressing.. Vol down and power.. than connect your phone with usb cable to pc ... open command prompt.. got to your sdk folder "platform-tools' and than enter ADB or Fastboot command..
But when you connect your phone to PC.. check if ADB drivers are installed.. go to device manager and check if your phone is recognised as ADB interface under Android Phone
Click to expand...
Click to collapse
Ah, I just looked in my platform-tools folder and there was adb etc. but I could not find fastboot. Where can I download that?
In the device manager, it's under 'Android USB Devices' as 'My HTC' is that ok?
OK, I have the SDK working fine, but when I go to this ( http://ks25738.kimsufi.com/misc/index.php ) website to get the .img file I need I can't figure out my kernel/ROM number - in the settings it says:
Android Version
2.3.4
Baseband Version
32.54.00.32U_5.14.05.17
Kernel Version 2.6.37.6-cyanogenmod-01494-g8dc02ff
[email protected]
Build Number
MIUI.1.6.17
The wesbite states the number should be 10 characters long, anyone know which one the ROM number is?
Thanks
You are once again trying to flash an RUU. Do not do this without first fixing your SD card problems.
fastboot oem enableqxdm 0
and also
fastboot oem eraseconfig
Need more details on where you are at. If you don't fix the issues you have then flashing an RUU could leave you in a much worse situation than you are now, and where you are now is easily fixed!
Parva4 is right.. you should 1st try enabling your sd card....
what you need to do is...
first download adb drivers for your device...
power on your phone into fastboot.. by pressing volume down and power.. connect usb cable to pc.. and in device manager.. update driver to adb driver.. while in hboot.. and than run that fastboot command which Parva4 mentioned.
I sorted it out, thanks to all who helped!
I did the fastboot enableqxd 0 command to unlock the SD card then once that was able to be used I flashed back to a nand backup I had made minutes before I did the flash that went wrong and now it's working fine!
I've tried switching it on and off
mains/usb
fastboot script doesn't work
Should a "Battery level too low to flash" still show in "fastboot devices"??
Do you have a running rom on the phone ?
try to wipe data and reflash if you have any custom rom
williamharvey said:
try to wipe data and reflash if you have any custom rom
Click to expand...
Click to collapse
That's probably not possible due to the fact that the batt is to low
Mr Hofs said:
That's probably not possible due to the fact that the batt is to low
Click to expand...
Click to collapse
Rom/system has been wiped Via Superwipe Script
It's a locked bootloader
I'm going to try on a different pc to see if i can get it to work in fastboot to use fastboot charge script!
It's not charging via usb but i've left it on mains now.
How did you execute the .bat file for recharging ?
With the phone in bootloader and then run the script, it should continuously reboot the phone
Mr Hofs said:
How did you execute the .bat file for recharging ?
With the phone in bootloader and then run the script, it should continuously reboot the phone
Click to expand...
Click to collapse
Tried with HBOOT/Fastboot it just says <waiting for device>
Do you have the HTC drivers installed and do you have the fastboot folder with the fastboot and adb files on the pc ?
You have to run the script from the within the folder with the fastboot files and with the phone in bootloader menu .....
When its in bootloader you should see
Fastboot usb
When the phone is conected to the pc !
Then you can try this command
Fastboot devices
Then the serial from the phone should show up
All the fastboot commands have to be executed from the command prompt on the pc
Mr Hofs said:
Do you have the HTC drivers installed and do you have the fastboot folder with the fastboot and adb files on the pc ?
You have to run the script from the within the folder with the fastboot files and with the phone in bootloader menu .....
When its in bootloader you should see
Fastboot usb
When the phone is conected to the pc !
Then you can try this command
Fastboot devices
Then the serial from the phone should show up
All the fastboot commands have to be executed from the command prompt on the pc
Click to expand...
Click to collapse
It was connecting before im going to try on another pc now
How are you doing ?
I used the bat script the problem was a driver issue fixed by downloading htc drivers going into device manager and installing a driver for "fastboot"
thanks for the reply
Hy
I had an unlocked bootloader phone. Yesterday I flashed the new Android 6, Europe version from the Huawei blog forum, no beta, on my Huawei GX8. I used the method, dload on SD card, Phone off an the press Volume down+volume up+Power button.The flashing was normaly.
Now the phone starts normaly but I can´t start fastboot. When the phone is off and i press Vol down + Power the phone start the android system and the Huawei logo is coming not the fastboot Modus. I can see my phone and the order under Windows but i can not control my phone with the fastboot command. (example: fastboot device. the answere ist searching devices, but it comes no resolution) I loaded the last version of Fastboot, but the problem is the same.
Please can you help me. What can i do? Many thanks for your help!
Should be connect the charger cable to the phone.
charger or computer
excuse me for bad english
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
bertl237 said:
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
Click to expand...
Click to collapse
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
krispin said:
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
Click to expand...
Click to collapse
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
bertl237 said:
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
Click to expand...
Click to collapse
So, you connect your phone, open minimal adb and fastboot too, run "adb devices", you see device id? If yes, run "adb reboot bootloader" . Phone shoult reboot to fastboot mode. Then run "fastboot devices" to see if it is connected properely.
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
bertl237 said:
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
Click to expand...
Click to collapse
No, you should be able to use adb and fastboot with stock recovery.
After first adb command you shoult approve authorization on your phone.
Here is screenshot from minimal adb...
Phone must be in MTP mode.
And here is phone in fastboot
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
bertl237 said:
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
Click to expand...
Click to collapse
Just reboot to fastboot and flash surdu-petru version of TWRP recovery 3.0.2 with command "fastboot flash recovery xxxxx.img". And than reboot to recovery and flash supersu zip.
Hi guys!
After years playing around with android roms and devices it looks that i probably brick a device for first time.
I'll try to be brief, but if you need more info it will be a pleasure give it to you.
Now my MI6 have recovery cofface 3.1.1.-0 installed but no os. I can reboot on bootload with keys. The problem is that im unable to push a zip into the device. Commands "adb devices" and "fastboot devices" return no devices founded.
a) OTG: Recovery doesnt allow me to mount USB-OTG. I enter in Mount and when i click over USB-OTG it highlighted but the checkbox still empty.
b)Plug into pc: The phone appears and disappears each second. Tried multiples wires.
Udev not found warning shows up when I click in the device before it disappears.
c) ADB sideload: not working, cause i cant reach MI6 from PC.
I add some stuff i see in logs and could be interesting:
When i use sideload:
Code:
I: cannot find file /sys/class/android_usb/android0/idProduct
I: cannot find file /sys/class/android_usb/android0/idVendor
When is in appear/disappear loop:
Code:
I:[MTP]Mtpserver::run fd: 20
E:[MTP] request read returned -1, errno: 5 , exiting MtpServer::run loop
I tried to recover it from Windows and Linux even from FWUL liveiso but all same results.
Any idea is appreciated, thanks a lot!
PD: Excuse my English Besides not having a good level, I'm tired of being all day trying things
Shugui said:
Hi guys!
After years playing around with android roms and devices it looks that i probably brick a device for first time.
I'll try to be brief, but if you need more info it will be a pleasure give it to you.
Now my MI6 have recovery cofface 3.1.1.-0 installed but no os. I can reboot on bootload with keys. The problem is that im unable to push a zip into the device. Commands "adb devices" and "fastboot devices" return no devices founded.
a) OTG: Recovery doesnt allow me to mount USB-OTG. I enter in Mount and when i click over USB-OTG it highlighted but the checkbox still empty.
b)Plug into pc: The phone appears and disappears each second. Tried multiples wires.
Udev not found warning shows up when I click in the device before it disappears.
c) ADB sideload: not working, cause i cant reach MI6 from PC.
I add some stuff i see in logs and could be interesting:
When i use sideload:
When is in appear/disappear loop:
I tried to recover it from Windows and Linux even from FWUL liveiso but all same results.
Any idea is appreciated, thanks a lot!
PD: Excuse my English Besides not having a good level, I'm tired of being all day trying things
Click to expand...
Click to collapse
That recovery is ancient. Just use fastboot to flash a stock rom with miflash. Then flash latest twrp.
NickTheSickDick said:
That recovery is ancient. Just use fastboot to flash a stock rom with miflash. Then flash latest twrp.
Click to expand...
Click to collapse
Commands "adb devices" and "fastboot devices" return no devices founded.
Click to expand...
Click to collapse
This is the first roadblock for him.
if fastboot devices can't detect his device, then any fastboot command to flash a partition is also invalid.
Have you tried different machine to do adb devices/ fastboot devices?
ArcOnFire said:
This is the first roadblock for him.
if fastboot devices can't detect his device, then any fastboot command to flash a partition is also invalid.
Click to expand...
Click to collapse
You right
ArcOnFire said:
Have you tried different machine to do adb devices/ fastboot devices?
Click to expand...
Click to collapse
Yes, linux and windows. And drivers are OK cause it worked before.
I think when i wiped system the device got corrupted someway. Now if i plug it into debian machine the computer detect the phone one sec., then dissapear other second, appear again... and so on.
My idea was to flash new recovery from otg but recovery didnt mount the device. Im researching for some way to mount it manually but at the moment not success.
Shugui said:
You right
Yes, linux and windows. And drivers are OK cause it worked before.
I think when i wiped system the device got corrupted someway. Now if i plug it into debian machine the computer detect the phone one sec., then dissapear other second, appear again... and so on.
My idea was to flash new recovery from otg but recovery didnt mount the device. Im researching for some way to mount it manually but at the moment not success.
Click to expand...
Click to collapse
I'm assuming it's a driver error. Few years ago i had a mtk smartphone and somehow i managed to hard brick it, PC recognize it just for 2 or 3 seconds and that was because fastboot drivers didn't installed so i had to install it manually from device manager, for mtk drivers name was preload 89xx (driver must be for specific motherboard model number), i opened device manager, boot phone in fastboot mode, connect it to pc and on the short time wen the PC recognize the phone i hited right click and choose update driver manually, i believe it could be possible to do the same thing with mi 6, i don't know if there are separate drivers for fastboot mode to be able to install them.
mArIuS% said:
I'm assuming it's a driver error. Few years ago i had a mtk smartphone and somehow i managed to hard brick it, PC recognize it just for 2 or 3 seconds and that was because fastboot drivers didn't installed so i had to install it manually from device manager, for mtk drivers name was preload 89xx (driver must be for specific motherboard model number), i opened device manager, boot phone in fastboot mode, connect it to pc and on the short time wen the PC recognize the phone i hited right click and choose update driver manually, i believe it could be possible to do the same thing with mi 6, i don't know if there are separate drivers for fastboot mode to be able to install them.
Click to expand...
Click to collapse
I'll try this when i have a bit more time. Right now i dont have all the time i desire. Too much work and university stuff
Thank you all.
I'll be back
Shugui said:
I'll try this when i have a bit more time. Right now i dont have all the time i desire. Too much work and university stuff
Thank you all.
I'll be back
Click to expand...
Click to collapse
Guys i need ur help please, i cant boot into twrp from fastboot
My step is
My step is go to fastboot > instal mi driver in device manager then adb interface coming > open adb folder > put twrp into adb folder > change name twrp file into recovery then use this command > fastboot flash recovery recovery.img then succes and fastboot boot recovery.img but just stuck on mi logo for 30minutes i guess
Fahrilubis said:
Guys i need ur help please, i cant boot into twrp from fastboot
My step is
My step is go to fastboot > instal mi driver in device manager then adb interface coming > open adb folder > put twrp into adb folder > change name twrp file into recovery then use this command > fastboot flash recovery recovery.img then succes and fastboot boot recovery.img but just stuck on mi logo for 30minutes i guess
Click to expand...
Click to collapse
fastboot devices
fastboot flash recovery twrp.img
fastboot flash boot twrp.img
fastboot reboot
i think u forgot the third command. Anyway check the info, im not 100% sure
Shugui said:
fastboot devices
fastboot flash recovery twrp.img
fastboot flash boot twrp.img
fastboot reboot
i think u forgot the third command. Anyway check the info, im not 100% sure
Click to expand...
Click to collapse
Thx brother solv
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.