Develop Bugs

Potentially bricked Desire...

Hey everyone, I'm sad to say that earlier I dropped my beloved Desire and it's not booted properly since e.g. I can only get onto the dialer.
The long and short of it is that I can't mount my SD card, clockwork won't allow it and says it has:
E:can't mount /dev/block/mmcblk0p1
no such file or directory
E: can't mount /sdcard
And ADB doesn't find my device when I type adb devices.
I've come across a few posts but I'm pretty clueless as to what they actually mean...
I've heard this particular command fixes it in Linux...
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
cd /mnt/cdrom/root
/mnt/cdrom/root/fastboot oem enableqxdm 0
But how would I go about doing that, and is there a way of doing that in Windows? I assume that because adb can't see my device then that's a no... It knows it's plugged in because it makes the connection sound and I can see it in device manager.
It's currently S-OFF'd with AlphaRev 1.8 running a Cyanogenmod nightly that I had running for a few days without problem so I assume it's not that. I can get into Fastboot (not much good if Windows doesn't see my device), bootloader and Clockwork.
I feel really stuck right now and would really appreciate the help of one of you knowledgeable lot.
Bearing in mind I'm not very knowledgeable so anything you explain would really have to be explained well!
Thanks guy's.

http://forum.ppcgeeks.com/archive/index.php?t-125093.html

Thanks for that, but ADB doesn't see my device so I can't use that.

DesireRoss said:
Thanks for that, but ADB doesn't see my device so I can't use that.
Click to expand...
Click to collapse
When your on bootloader screen and you plug your usb in does it change to say that you have plugged in usb ? because fastboot isn't adb
Hboot has an option for fastboot
Enable the SD Card functionality. Boot your phone in FASTBOOT mode (back + power), and enter this command: 'fastboot oem enableqxdm 0' . This will re-enable your SD card.
read up on http://forum.xda-developers.com/showthread.php?t=691187

BigMrB said:
When your on bootloader screen and you plug your usb in does it change to say that you have plugged in usb ? because fastboot isn't adb
Hboot has an option for fastboot
Enable the SD Card functionality. Boot your phone in FASTBOOT mode (back + power), and enter this command: 'fastboot oem enableqxdm 0' . This will re-enable your SD card.
read up on http://forum.xda-developers.com/showthread.php?t=691187
Click to expand...
Click to collapse
When I plug it in, all the drivers get installed and it changes to 'HBOOT USB PLUG' on the bootloader. The problem is when I type in 'adb devices' it doesn't show my Desire. I can't fastboot that command because it can't find the phone itself..?

DesireRoss said:
When I plug it in, all the drivers get installed and it changes to 'HBOOT USB PLUG' on the bootloader. The problem is when I type in 'adb devices' it doesn't show my Desire. I can't fastboot that command because it can't find the phone itself..?
Click to expand...
Click to collapse
You have to boot your phone into fastboot.
Code:
fastboot devices
does not work in hboot mode.

MatDrOiD said:
You have to boot your phone into fastboot.
Code:
fastboot devices
does not work in hboot mode.
Click to expand...
Click to collapse
It says 'fastboot' is not recognized as an internal or external command, operable program or batch file.
Arghh!

Are you trying this in fastboot mode? You have to start it with the back button and power button pressed until you see the white screen with the three androids at the bottom, Fastboot highlighted in red letters

BigMrB said:
Are you trying this in fastboot mode? You have to start it with the back button and power button pressed until you see the white screen with the three androids at the bottom, Fastboot highlighted in red letters
Click to expand...
Click to collapse
Yeah, that's what I'm doing. I'm just clueless as to why ADB can't see it? If it could, it would solve my problem... So frustrating.

DesireRoss said:
Yeah, that's what I'm doing. I'm just clueless as to why ADB can't see it? If it could, it would solve my problem... So frustrating.
Click to expand...
Click to collapse
Driver issue?? Try downloading HTC sync to get them...

BigMrB said:
Driver issue?? Try downloading HTC sync to get them...
Click to expand...
Click to collapse
And then uninstall only htc sync, not the drivers. Then reboot computer to apply changes.
To avoid the firmware issue from unrevoked, it's recommend to use unrevoked 3.21:
http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe

Tried what you said and I got 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"
}

Installed android sdk correctly:
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK

I think you might be right... Trying to install the Google USB drivers and it says 'failed to fetch URL' is there anywhere I can manually download it off the net?

http://dl4.htc.com/RomCode/Source_and_Binaries/USB_driver_20101122_release.zip
You can get them through SDK manager you know?!

BigMrB said:
http://dl4.htc.com/RomCode/Source_and_Binaries/USB_driver_20101122_release.zip
You can get them through SDK manager you know?!
Click to expand...
Click to collapse
This is the Google usb drivers from the SDK... And it says I can't download that repository because of a bad URL..?

Managed to get the USB drivers, but still not being found in ADB... Is this a lost cause?

Booted into recovery and ADB found it...
Any ideas on what to do from here?

DesireRoss said:
Managed to get the USB drivers, but still not being found in ADB... Is this a lost cause?
Click to expand...
Click to collapse
- Check if ONLY HTC SYNC DRIVERS where installed.
- Checked "unknown sources" in applications?
- Set phone to "charge only" and "never ask?"

MatDrOiD said:
- Check if ONLY HTC SYNC DRIVERS where installed.
- Checked "unknown sources" in applications?
- Set phone to "charge only" and "never ask?"
Click to expand...
Click to collapse
Yeah that was all that was installed. Can't check unknown sources or the other as I can't actually get into anything past the first setup stage and then there's nothing... Just need to re-enable my SD card. Fffffffffff.

[Q] Stuck at stock bootloader

I am such a noob and suck at rooting.I got problem during rooting my kindle fire,here's the stories.I try to search all the way in the forum. But,all of it not working. Could you guys help me ?
1) follow root instruction and downloaded KFU
2) successfully installed superuser and go launcher
3) TWRP or CWR or FFF doesn't appear when i reboot back my device to flash custom rom.
4) I tried to run install_driver and run it again and select bootmode menu
5) I choose 3 for recovery.and its brick.luckily i could switch off my kindle.but when i wanna turned it on,its doesnt return to home menu.its stuck at the stock bootloader.
I'm hoping you guys could help me and suggest me the way how to solve it.
I also attach some screen shot of the kindle and my notebooks when i plugged in usb cable in.
Cheers.
{
"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"
}

it seems to be in fastboot mode - you have to fix your windows driver for fastboot mode, then you can continue with kfu.
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
detailed explanation here: http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2

b63 said:
it seems to be in fastboot mode - you have to fix your windows driver for fastboot mode, then you can continue with kfu.
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
detailed explanation here: http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
thanks for the advice.I will try it after this and inform you back. Btw, do i need kindle usb cable? for fastboot, since i purchased used kindle so the seller didnt gimme those cable. im currently using sony micro usb cable.

no - every micro usb cable will work

b63 said:
no - every micro usb cable will work
Click to expand...
Click to collapse
i will try to read all of it, try to understand it.and get you know once i already figure it out okay?:cyclops:

i already update my driver.and why in KFU,my device is offline.

21th century apes said:
i already update my driver.and why in KFU,my device is offline.
Click to expand...
Click to collapse
your device seems to be in fastboot mode - you have selected the wrong driver.
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
if the device is in fastboot mode "adb status" is allways "offline".
if you have installed the right driver you can check manually
with "fastboot devices" and "fastboot getvar product".
if you get response to this commands you are good to go.

i finally able to install bootloader and twrp.i thought i never make a mistakes.but unfortunately,during time im backing up stock rom,(nandbackup).i check all the boxes (for the left side) and for right side nothing.its running,when completed.its show huge amount of data (around 780 mb).i really think dat tis is normal for backup.in twrp,and video by tom gt,time for backup for 10 minutes.but me,already 5 hour still stuck in twrp.cant go anywhere.

b63 said:
your device seems to be in fastboot mode - you have selected the wrong driver.
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
if the device is in fastboot mode "adb status" is allways "offline".
if you have installed the right driver you can check manually
with "fastboot devices" and "fastboot getvar product".
if you get response to this commands you are good to go.
Click to expand...
Click to collapse
bro i hope you can help me solve tiz things off.during backup nand.for the first time.its stuck and as i mention previously its stuck 5 hours but for almost 2 days.its still not finish.am i brick my fire?am i miss out something?later i'll attach picture for your preferences.i think when i already booted up kindle fire,its consider no such big issues.maybe for me that not familiar.

21th century apes said:
bro i hope you can help me solve tiz things off.during backup nand.for the first time.its stuck and as i mention previously its stuck 5 hours but for almost 2 days.its still not finish.am i brick my fire?am i miss out something?later i'll attach picture for your preferences.i think when i already booted up kindle fire,its consider no such big issues.maybe for me that not familiar.
Click to expand...
Click to collapse
if you managed to install bootloader and twrp then you are good to go.
you tried to make a backup of the stock firmware and now the twrp is stuck.
i don't know what options you checked, but this should be no problem.
just hold the power button for ~20sec till it turns off and try again.
check only options which exist on your device then the backup should be done in ~10min.

b63 said:
if you managed to install bootloader and twrp then you are good to go.
you tried to make a backup of the stock firmware and now the twrp is stuck.
i don't know what options you checked, but this should be no problem.
just hold the power button for ~20sec till it turns off and try again.
check only options which exist on your device then the backup should be done in ~10min.
Click to expand...
Click to collapse
Thank you dude.Finally im able to use custom rom.oh,yeah .Btw,i got one last question.Why i cant connect my kindle with computer.instead its show my kindle,its only charging.coz i need to backup all my stuff inside my kindle to computer.

21th century apes said:
Thank you dude.Finally im able to use custom rom.oh,yeah .Btw,i got one last question.Why i cant connect my kindle with computer.instead its show my kindle,its only charging.coz i need to backup all my stuff inside my kindle to computer.
Click to expand...
Click to collapse
that depends on the rom you used. some have a option to enable this function.
the best advise would be to search or ask in the section of the rom you used.
great that it's working now - much fun with your kf

hey dude.im already killed my kindle fire and now its dead.here the stories :
i try to backup all my stuff to my computer.as what you told me before,i try to follow.pick ROM that have usb debugging option for transfering data.okay done.but when i transferring my data from kindle to pc.(i dunno what happen) accidentally my kindle fire hang and i disconnect all the cable hoping that my kindle fire will be okay.but thats the end of my kindle fire.its failed to boot.just plain black screen.when i plugged in the cable.led light blinking.like normal.red and yellow.but there's nothing i can do.i open up device manager on my pc,instead of android phone appeared during time im connecting my phone with pc,its appeared usb mass storage (code 10).device cant start and load.hope you could guide me.anybody.
all guide will be kindly appreaciated.thanks.

Huawei Watch Update 1.4 is here!

Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you are connected to your charging dock.
Make sure you are running the latest update LCB43B.
I did all this on Win 10.
1. Just be fully stock including recovery. Refer to Skin1980's guide here to return to stock if you used his previous kernel or did any other mods like TWRP or root. (http://forum.xda-developers.com/huawei-watch/general/guide-return-to-stock-huawei-watch-t3219596)
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339) (People have reported PDANET drivers are working if the naked drivers do not work for them and are somewhat easier to install.)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip and make sure its located inside the root directory of your adb installation.
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Don't forget to hit the thanks button! I appreciate it!

Thank you. Can you please create a step by step guide for idiots like me, who have never used adb etc..?

hey when i try to go to recovery and do the "adb devices within stock recovery.. i see this
c:\android\hwatch> adb reboot bootloader
c:\android\hwatch>adb devices
list of devices attached
c:\android\hwatch>
even though when i was on the main menu of the watch before rebooting to recovery and all that
list of devices attached
FFS7N15B06003222 device
i go to bootloder reboot recovery adb devices... get nothing in there

chachin said:
hey when i try to go to recovery and do the "adb devices within stock recovery.. i see this
c:\android\hwatch> adb reboot bootloader
c:\android\hwatch>adb devices
list of devices attached
c:\android\hwatch>
even though when i was on the main menu of the watch before rebooting to recovery and all that
list of devices attached
FFS7N15B06003222 device
i go to bootloder reboot recovery adb devices... get nothing in there
Click to expand...
Click to collapse
I updated OP check the steps again. adb commands won't work in bootloader. Once in recovery swipe down and select apply update from adb then issue the "adb sideload update.zip" command.

so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>

chachin said:
so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>
Click to expand...
Click to collapse
Make sure the update file is inside your root adb directory on your hard drive.

chachin said:
so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>
Click to expand...
Click to collapse
It looks like your device is still not visible to adb. Make sure you don't have any other devices connected like a phone with debugging turned on also. And you do need to be in recovery with it awaiting the sideload update.zip command. You seemed to be in the correct place.

Mine got pushed to me, I just have to charge it
Sent from my VS990 using Tapatalk

xceebeex said:
Mine got pushed to me, I just have to charge it
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
YAY! Always the best way to go. Where are u located?

RngrYogi said:
Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
1. Just be fully stock including recovery.
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Click to expand...
Click to collapse
But... the phone must be connected on the pc? I can't detect the watch with adb devices..

I was wondering why I couldn't boot to the recovery directly so thanks a ton for the help! Also dayum, the speaker sure is quite loud for a smartwatch!
To the person above no, you do not need to have the phone to your pc connected for it to work.

got it installed like it so far, to me the speaker sounds alot better then the one in the gear s

{
"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"
}
Thank you dear XDA members for your advice on how to adb sideload
Sent from my LG-H815 using Tapatalk

Tried installing the naked drivers in the link but that fails, any suggestions?

str8spir said:
Thank you dear XDA members for your advice on how to adb sideload
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Very glad we could help! Just wanted everyone to be as happy as I was when I saw the file drop!

RngrYogi said:
Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
1. Just be fully stock including recovery.
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Click to expand...
Click to collapse
Thanks worked flawlessly...

ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost

chachin said:
ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost
Click to expand...
Click to collapse
Let me test mine and see if it is visible while waiting on the adb sideload update.zip command

No luck for me installing these drivers

chachin said:
ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost
Click to expand...
Click to collapse
C:\ADB>adb devices
List of devices attached
MQB7N15914000616 sideload
This is what I see while in sideload mode inside recovery. Not sure why its not working for you.:crying:

Flashed wrong kernel by mistake

Hi,
I got a little bit of a problem on my head.... I planned to flash CM12.1 on my HOX but i flashed a different boot.img by mistake! Now i cant get the phone into debugging mode and while using hasoonss toolkit it wont see my device cause i cant get it into debugging mode . Any ideas on how to solve the problem? There are a lot of threads inhere about bricked hox but i cant find one talking about the same problem....
Hope i can get some help on this.

Ow and a bit more info, i can get into bootloader and recovery.

go_insane1981 said:
Ow and a bit more info, i can get into bootloader and recovery.
Click to expand...
Click to collapse
if you can get into bootloader then just get the good boot.img and flash it using fastboot flash boot boot.img

Tried that but it won't see my device.

It doesn't apear in my devices.

go_insane1981 said:
It doesn't apear in my devices.
Click to expand...
Click to collapse
When on bootloader/fastboot mode, type
fastboot devices
to check connection
if it returns your device serial no, then it is good for you to
fastboot flash boot boot.img
adb devices is working when in recovery or on running OS, not on bootloader/fastboot

ckpv5 said:
When on bootloader/fastboot mode, type
fastboot devices
to check connection
if it returns your device serial no, then it is good for you to
fastboot flash boot boot.img
adb devices is working when in recovery or on running OS, not on bootloader/fastboot
Click to expand...
Click to collapse
Tried both ways again but no reaction wth a list of devices. It's blank...

install htc drivers http://www.mediafire.com/?eqrqb44r3ot18g1

SÜPERUSER said:
install htc drivers http://www.mediafire.com/?eqrqb44r3ot18g1
Click to expand...
Click to collapse
Any options on how to install the drivers different from normally? Apparently the drivers won't install as it should install...
Have HTC sync on my system, can i use some of those exe's in there?

This is wat happens with HTC installer.

go_insane1981 said:
This is wat happens with HTC installer.
Click to expand...
Click to collapse
You have a newer sets of drivers installed and the installer exits instead of downgrade the version.
Are you sure you are in fastboot mode?
To enter this.
Power off your phone.
Hold Power and volume down button until phone enters a white screen with Hboot written on it.
{
"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"
}
Now press power button again. The screen should now change to this
Showing fastboot marked in red.
Go to device manager and look for the driver. It should look like this ( Android USB Devices, My HTC)
In cmd type fastboot devices.
My cmd returns this.

Cant seem to get the drivers in my device manager, they are installed but not showing in my device manager...

SÜPERUSER said:
You have a newer sets of drivers installed and the installer exits instead of downgrade the version.
Are you sure you are in fastboot mode?
To enter this.
Power off your phone.
Hold Power and volume down button until phone enters a white screen with Hboot written on it.
Now press power button again. The screen should now change to this
Showing fastboot marked in red.
Go to device manager and look for the driver. It should look like this ( Android USB Devices, My HTC)
In cmd type fastboot devices.
My cmd returns this.
Click to expand...
Click to collapse
Ok i used a old htc and now it sees my device again.

Device manager sees the HOX now too.

go_insane1981 said:
Device manager sees the HOX now too.
Click to expand...
Click to collapse
It was my thought at first. So now we know that htc apparently dropped the support for one x and older devices in their driver pack. Good to know

Now i need to take a look at how i can push a diff rom in there since the other rom apparently wont work..

go_insane1981 said:
Now i need to take a look at how i can push a diff rom in there since the other rom apparently wont work..
Click to expand...
Click to collapse
What rom are you trying to install?

SÜPERUSER said:
What rom are you trying to install?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-x/development/rom-cyanogenmod-12-1-t3396521

go_insane1981 said:
http://forum.xda-developers.com/htc-one-x/development/rom-cyanogenmod-12-1-t3396521
Click to expand...
Click to collapse
Have you flashed this "new storage layout"?
http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358

SÜPERUSER said:
Have you flashed this "new storage layout"?
http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
Click to expand...
Click to collapse
Making a new layout is something i missed, Mone said ;
Flashing instruction like usual: perform a full wipe with TWRP for new layout, flash the ROM, flash the suggested GApps, reboot into fastboot mode, flash the boot.img exctracted from the ROM.zip, reboot into system, enjoy cm-12.1.
So i wiped the damn thing( ) after making a backup offcourse(which btw doesn't help cuz its screwed...). But i completely missed that i had to make a new layout... But stil i am convinced it can be "unbricked" one way or another.
I basicly follwed all the steps mentioned in this thread; http://forum.xda-developers.com/showthread.php?t=2069904 and it al worked up to the point i flashed the wrong kernel. After that i searched the forum for hours and found some things which could be connected but with a total different view of what my problem is/was(partially solved with your help) and ended up with putting a SOS sign up for help.

Question Help With FastBoot On My Red Magic 6 Pro

Hello everyone,
I know this forum is for the Red Magic 6 not the Pro version but I couldn't find the Pro forum so I decided to hop into here expecting for some help
basically this happens
{
"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"
}
I am always stuck on waiting for any device when my Red Magic 6 Pro is connected to my PC and the phone is in fastboot the only way I can detect the phone is through ADB, I am in desperate help from any XDA professional please I need help ASAP
Thank you

You have to install device drivers and adb drivers

wele-sh said:
You have to install device drivers and adb drivers
Click to expand...
Click to collapse
But I have all the drivers installed including fastboot and ADB

MohammedAws said:
But I have all the drivers installed including fastboot and ADB
Click to expand...
Click to collapse
When the phone is turned on, open the adb commands. and type (adb devices) does it recognize your device?

wele-sh said:
When the phone is turned on, open the adb commands. and type (adb devices) does it recognize your device?
Click to expand...
Click to collapse
Yes when I use ADB devices it shows my device but when I write ADB reboot bootloader it boots me to where I need but when I type fastboot devices nothing shows and as in the image when I try to unlock my bootloader it just says waiting for any device

Okay now
MohammedAws said:
Yes when I use ADB devices it shows my device but when I write ADB reboot bootloader it boots me to where I need but when I type fastboot devices nothing shows and as in the image when I try to unlock my bootloader it just says waiting for any device
Click to expand...
Click to collapse
You have to Install Android Bootloader Interface Drivers .

wele-sh said:
Okay now
You have to Install Android Bootloader Interface Drivers
Click to expand...
Click to collapse
So look I have the Android ADB interface installed on the device manager do I replace it with the bootloader interface?

MohammedAws said:
So look I have the Android ADB interface installed on the device manager do I replace it with the bootloader interface?
Click to expand...
Click to collapse
https://www.droidwin.com/install-google-android-bootloader-interface-drivers/

wele-sh said:
https://www.droidwin.com/install-google-android-bootloader-interface-drivers/
Click to expand...
Click to collapse
So the link you sent me I did the steps before but it's ADB interface do I choose bootloader interface instead of ADB interface?

MohammedAws said:
So the link you sent me I did the steps before but it's ADB interface do I choose bootloader interface instead of ADB interface?
Click to expand...
Click to collapse
Yes

wele-sh said:
Yes
Click to expand...
Click to collapse
Alright I'll try to do it right now and I'll reply to your message when I see if it worked

wele-sh said:
Yes
Click to expand...
Click to collapse
so i changed it into bootloader interface but i get an error when I update it, it says the device cannot start but the driver still managed to install but i still can't get the fastboot working

MohammedAws said:
so i changed it into bootloader interface but i get an error when I update it, it says the device cannot start but the driver still managed to install but i still can't get the fastboot workingView attachment 5372177
Click to expand...
Click to collapse
I have exactly the same problem and have tried to install various drivers. Did you manage to solve this? I would appreciate your help if you did.

Anyone got a solution?

Contact me on telegram..
Chyavan Muhammed
ɀǶ
t.me

Problem is from windows driver signature enforce. You can fix by disable Driver Signature Enforcement :
Fastboot Not Detecting Device on Windows 10/ 11? Fix for OnePlus, Xiaomi, Realme & More
If Fastboot is not detecting devices on Windows 10/11, follow our guide and install the fastboot drivers for OnePlus, Xiaomi, Realme & more.
beebom.com