Develop Bugs

cant find device on usb fastboot?

hello everyone.
am trying to flash a new rom to my device. i followed all the intructions till the one that tells me to flash the boot.img through the usb fastboot.
but my pc cant recognize my one x?
when i choose "Hboot" it says "failed to checj usb master and something like that!

Did you install the HTC drivers on your computer? If you download and install the latest version of HTC Sync it should work.
Sent from my HTC One X using XDA

and if you have the drivers already, try to disable your antivirus and/or firewall before plugging your device. (it happened to me, my antivirus had too strict settings, preventing HTC drivers to install correctly, and also preventing adb to see my device plugged.)

I did download the drivers but nothing happened.
just a one more question. Is it okay to install the boot.img before the ROM?

Hamoor said:
I did download the drivers but nothing happened.
just a one more question. Is it okay to install the boot.img before the ROM?
Click to expand...
Click to collapse
Yes, as long as you go back to recovery right after flashing the boot image and install the ROM, otherwise your phone MAY not boot up (it should boot up and work, but it's a digital device)...

try unplugging...and then selecting HBOOT.....it might not give that error ...

still i cant load the fricking boot.img!!!!!!!
everytime i try it says "cannot load boot.img"
any help

hi
It seems like its a problem wiith the path from which u run the fastboot command.....what is the location of boot.img in ur system? is it in the same folder as fastboot.exe? and while giving the command 'fastboot flash....' what is the location that the command prompt is showing?(the working directory)

Once in the bootloader you must select FASTBOOT first and then connect via usb and type in fastboot devices. If it returns a number you're connected. That, may fix your issue.
Sent from my SGH-T999 using xda premium

Babydoll25 said:
Once in the bootloader you must select FASTBOOT first and then connect via usb and type in fastboot devices. If it returns a number you're connected. That, may fix your issue.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Yeah from what I read op is trying fastboot while in hboot.
Sent from my HTC One X using XDA Premium HD app

[Q] final steps when installing custom recovery

Good night.
I have to ask for help when trying to install custom recovery on this awesome machine.
I have done all steps and wen good, but when doing the final steps:
6) Use fastboot to boot CWM by running "fastboot boot /path/to/OuyaCWMrecovery6.0.3.2.img". This boots from our CWM recovery without writing to any partitions.
When writing this, says "wating for device" and dont advance.
I searched into ouya forums but i could not find the solution.
Also, drivers,sdk and su files are correctly installed.
Thanks for help

asanz00 said:
Good night.
I have to ask for help when trying to install custom recovery on this awesome machine.
I have done all steps and wen good, but when doing the final steps:
6) Use fastboot to boot CWM by running "fastboot boot /path/to/OuyaCWMrecovery6.0.3.2.img". This boots from our CWM recovery without writing to any partitions.
When writing this, says "wating for device" and dont advance.
I searched into ouya forums but i could not find the solution.
Also, drivers,sdk and su files are correctly installed.
Thanks for help
Click to expand...
Click to collapse
Usually that happens when the device isn't at the bootloader. Did you run "adb reboot bootloader" to get to the bootloader?
Sent from my Nexus 7 using xda premium

Yes, i followed all steps, including "adb reboot bootloader" and then waited 30 seconds, just the way its written
At this stage, ouya its switched on but not image, so i suposed i am into bootloader

MIght be a driver issue. On mine the first time I booted into fastboot mode I had to go into device manager, found the android device with a yellow triangle, and had to install the drivers manually with "have disk". Hope this helps.

asanz00 said:
Yes, i followed all steps, including "adb reboot bootloader" and then waited 30 seconds, just the way its written
At this stage, ouya its switched on but not image, so i suposed i am into bootloader
Click to expand...
Click to collapse
Same thing happened to me, I never saw anything until I fastbooted the .img. And then I had to try it on 3 displays before one would show CWM. However after I flashed the .zip I have since tried all the displays and they all have worked every time.

Wow problem solved!
In devices administrator, there was one small called "fastboot" with yellow triangle.
I manually installed a driver called "android bootloader interface" and now it is working
thanks a lot!!!

No problem, always glad to help.

Now im fighting to get multi usb support via using a 5 ports usb-hub, i will write if i can ge througt

Can you post about that in the USB thread ? I just bought an active USB cable and 4 port hub, I hope they weren't a waste. I'll still get some use on my laptop, but not enough to justify the purchase.
Sent from my GT-P3113 using Tapatalk 4 Beta

ultra fail... root process

i have tried way to many times to root this phone and have failed over and over. atleast once every 3 months i try with zero results. the phone is unlocked using the OneX v2.5 tool kit here. when i try to do perm root it says " User C not recognized as an external or internal command, operable program or batch file". ive tried putting the tool kit directly in C: and 86x. nothing works. what do i need to do to root this freaking phone. im fixing to get a bat to this phone!

Have you tried a different version, reinstall/redownload and running it as an admin?
Sent from my EndeavorU using XDA Premium 4 mobile app

Bl4ckX said:
Have you tried a different version, reinstall/redownload and running it as an admin?
Sent from my EndeavorU using XDA Premium 4 mobile app
Click to expand...
Click to collapse
no. i havent. do you have a recommendation for a different root system?

both programs ive used says "phone not connected". i dont get it. ive tried debugging and recovery. i have never had an android this hard to root. samsung galaxy s2 was very easy.

have you tried to flash a custom recovery and root package. that's how i did for mine and i was done within 10 minutes

You have a custom recovery ? Just install the SU.zip via recovery then. Tried that ?

mrbtree98 said:
have you tried to flash a custom recovery and root package. that's how i did for mine and i was done within 10 minutes
Click to expand...
Click to collapse
ive tried the all in one unlock and root kit. didnt work. could you post a link to what you used?

I never root stock rom. I'm always on a custom rom.
Just check for the superuser zip and install it in the custom recovery

Mr Hofs said:
I never root stock rom. I'm always on a custom rom.
Just check for the superuser zip and install it in the custom recovery
Click to expand...
Click to collapse
how do you use custom recovery? i tried everything on the all in tool kit(custom recovery to) and says phone not detected or what i posted up top. this is crazy. never have i seen and android phone so hard to root!!!

MPH33 said:
both programs ive used says "phone not connected". i dont get it. ive tried debugging and recovery. i have never had an android this hard to root. samsung galaxy s2 was very easy.
Click to expand...
Click to collapse
Do you get any output with "adb devices"? When you don't (and your phone has debugging enabled), it may as well be a driver problem.
(quick tip: add the antroid-tools folder to your PATH)
I personally can't find my phone on Windows anymore after the 4.2 update, so I just use an Ubuntu liveUSB for adb/fastboot purposes.
Sent from my HTC One X using Tapatalk

My opinion ? Don't use a toolkit. Straight commands from the prompt.
Download android sdk bundle, unpack it and go the the platform tools folder. Put there the recovery (recovery.img) open a command prompt there and type
Fastboot flash recovery recovery.img
Fastboot erase cache

Mr Hofs said:
My opinion ? Don't use a toolkit. Straight commands from the prompt.
Download android sdk bundle, unpack it and go the the platform tools folder. Put there the recovery (recovery.img) open a command prompt there and type
Fastboot flash recovery recovery.img
Fastboot erase cache
Click to expand...
Click to collapse
done as directed. went to cmd typed fastboot. still says internal or external not recognized. man this sux

Have you already followed the instructions on htcdev.com? You have to unlock your phone first before you can flash a recovery
Sent from my HTC One X using Tapatalk

svenvv said:
Have you already followed the instructions on htcdev.com? You have to unlock your phone first before you can flash a recovery
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
yes. the phone is unlocked. it's been unlocked for like 8 months. just cant seem to root it.

Are the drivers correctly installed, download the latest HTC sync. And also check if java and .net.frameworks are installed on the pc

Mr Hofs said:
Are the drivers correctly installed, download the latest HTC sync. And also check if java and .net.frameworks are installed on the pc
Click to expand...
Click to collapse
yes. sync manager is fully updated. maybe its my computer. i built it. running on windows 7 ultimate. hell, i dont know. this is weird. like i said before... my old samsung was so much easier. i just wanna root to get rid of all this bloat.

MPH33 said:
done as directed. went to cmd typed fastboot. still says internal or external not recognized. man this sux
Click to expand...
Click to collapse
That seems like you're not in the correct directory.
To get rid of that error forever just put the contents of platform-tools in your C:\windows\system32 and C:\windows\syswow64 folders
Then you can run the commands from anywhere.
Now:
Install HTC sync drivers.
Put your phone in fastboot mode.
Put a recovery image in the path that the cmd shows when you start it (eg. C/users/USER/) or "cd" to the recovery image.
Then:
fastboot flash recovery recoveryname.img
When that gives decent output we're getting somewhere.
In that case put the supersu zipfile on you phones storage and flash it from recovery.
Sent from my HTC One X using Tapatalk

Try updating or reinstalling drivers for the phone check if your cable is good and connects it to PC
[Knowledge from tegra 2 device you must have APT or NVflash driver and whne phone is off with custom key combination enters flash mode i guss is similar to this]

screw this. phone works great just wanted to root. mint condition, will sell cheap. pm me if interested.

it isn't due to the phone...it's because windows don't know for what this command is...so install again the latest java for your win7 ....you are definitely doing something wrong...you could also try to google that error which you get after typing fastboot bla bla
it works for all other ppl so should also work for you even with my non genuine win8.1 pro it's working fine

[Q] Can't boot phone after upgrade - CyanogenMod 10.2 Stable

Hey guys,
So the problem I'm experiencing is that my HTC One X is stuck in a boot loop after I applied an update to CyanogenMod 10.2 Stable that I saw in the settings menu. Dumb mistake.
I've tried reading up on the issue but I'm posting here because I want to make sure I don't brick the phone. I bought the phone second hand, already rooted and flashed, so my knowledge on this stuff is extremely limited.
So here's some info:
1. I can access a boot menu when I hold the power and volume down button.
2. From there I can access ClockworkMod Recovery v5.8.4.0
3. I've tried restoring the phone
4. I found and applied the 2 zips that are already in the sd card. The old one: CM 10.1 and CM 10.2. - Both of them get stuck in boot.
5. I've downloaded Fastboot and ADB to my computer.
6. I tried to follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2617301. Fastboot can't find my device (fastboot getvar cid -> waiting for device). I should mention that I mounted /sdcard and also tried mounting 'USB storage' but that didn't seem to do anything.
I also found this thread that might be of help once I get the computer to see my phone: http://forum.cyanogenmod.com/topic/...01-to-102-if-you-get-stuck-at-boot-animation/

ChrisGiggles said:
Hey guys,
So the problem I'm experiencing is that my HTC One X is stuck in a boot loop after I applied an update to CyanogenMod 10.2 Stable that I saw in the settings menu. Dumb mistake.
I've tried reading up on the issue but I'm posting here because I want to make sure I don't brick the phone. I bought the phone second hand, already rooted and flashed, so my knowledge on this stuff is extremely limited.
So here's some info:
1. I can access a boot menu when I hold the power and volume down button.
2. From there I can access ClockworkMod Recovery v5.8.4.0
3. I've tried restoring the phone
4. I found and applied the 2 zips that are already in the sd card. The old one: CM 10.1 and CM 10.2. - Both of them get stuck in boot.
5. I've downloaded Fastboot and ADB to my computer.
6. I tried to follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2617301. Fastboot can't find my device (fastboot getvar cid -> waiting for device). I should mention that I mounted /sdcard and also tried mounting 'USB storage' but that didn't seem to do anything.
I also found this thread that might be of help once I get the computer to see my phone: http://forum.cyanogenmod.com/topic/...01-to-102-if-you-get-stuck-at-boot-animation/
Click to expand...
Click to collapse
Download htc sync it will install the drivers required ,then you're good to go

When you install drivers..Go to recovery wipe everything except battery stats and storage..Then flash cm10.2 zip and then gapps..Then flash boot.img and erase cache..
Sent from my HTC One X using Tapatalk 2

Muksleo said:
Download htc sync it will install the drivers required ,then you're good to go
Click to expand...
Click to collapse
Ok, I'm back from trying that. On my old PC laptop the software just failed to install. I'm trying again... takes forever to install.
I also downloaded it for my Mac, that worked fine but it doesn't actually find the phone when connected.
EDIT: POS computers... The Windows one throws up a weird error, no explanation, just a bunch of numbers. The Mac one is just incompetent...

What windows do you have?? 7,8.1 install drivers automatically..

big noob said:
What windows do you have?? 7,8.1 install drivers automatically..
Click to expand...
Click to collapse
The PC is running Windows 7... but neither of my computers recognize the phone (or mount the storage) through the USB.
I'm f*cked I think.
EDIT: Yep, I got the HTC sync to install finally on the Windows PC. And as I suspected, it doesn't recognize my phone.

So I guess my problem now is that the phone doesn't actually mount. I've never connected it to a computer before so I don't know if this is a new problem or not.
I've tried 2 computers and 2 different cables. I guess the phone is essentially bricked now? So much for "stable" update...

ChrisGiggles said:
So I guess my problem now is that the phone doesn't actually mount. I've never connected it to a computer before so I don't know if this is a new problem or not.
I've tried 2 computers and 2 different cables. I guess the phone is essentially bricked now? So much for "stable" update...
Click to expand...
Click to collapse
Restart your computer after driver installation
after that go where u have fastboot folder press shift and right click and click on open command window here
there u can give fastboot commands

Muksleo said:
Restart your computer after driver installation
after that go where u have fastboot folder press shift and right click and click on open command window here
there u can give fastboot commands
Click to expand...
Click to collapse
Thanks but that's exactly what I've been doing.

Well,did you try to remove all installed drivers..And let Windows install drivers..That always works for me..
Sent from my HTC One X using Tapatalk 2

Partition table doesn't exist

Hey all,
So I seem to have soft bricked my tablet (Nexus 7 2013 LTE). I can get into fastboot mode (but not into the recovery menu) then I am stuck on the Google logo. Does this mean the device is repairable?
Device manager on Windows shows the tablet as
- an unknown device (no drivers installed / Samsung (Wugfresh) / Google drivers)
- Android bootloader interface (Snoop05's tool)
- Android ADB Interface (PDAnet (Wugfresh)).
On all of them the driver is not correctly installed and I have the exclamation mark showing on device manager. I am unable to access the tablet via fastboot or ADB at this time.
I have tried every permutation I can think of so am turning to the hive mind for advice.
To compound matters I am in Turkey and I don't speak Turkish. I've been in an internet cafe for about 5 hours now and it's 1am (Turkish keyboards have an ı where i should be and you can imagine how many times I have mistyped). I am on a year long cycle tour and the tablet has my music, books, guidebooks and dictionaries on it so I am pretty hacked off. Especially given that I've only just arrived...
I did manage to connect via ADB yesterday but ran out of time as I was borrowing someone's computer and can't replicate the steps. Gah!
I have backups of all my data so essentially I would just like to factory reset. Any help gratefully received!
Thanks,
Don

Well, I found the right combination of drivers (Snoop05's tool then PDANet on Wugfresh) and can now see the device via fastboot so I have unlocked it. However whenever I try and flash boot / system / recovery, etc via fastboot I'm receiving an error 'remote: partition table doesn't exist'. Any ideas, people?

Probably useful to add that the problem was initially caused when I removed the SIM card whilst the unit was switched on. I received a message asking me to reboot and it has been bricked since. Also, I was runing stock unrooted.
Thanks

I have now tried every toolkit I can find but still no joy. I seem to have corrupted my partition table which is preventing me writing anything to the device.
To confirm - I can boot into fastboot mode and can see the device via fastboot using command line and can unlock it using 'fastboot oem unlock'. I have the images to write using 'fastboot flash boot/recovery/system [image location] but nothing will let me write to the device without receiving the error 'FAILED - remote: partition table doesn't exist'.
I have searched everywhere and can't find very much. Is the device recoverable or have I fecked it...? I need to get out of internet cafes and onto my bike...
Cheers in advance

Gulp! 100+ views and no replies...does no-one want to break it to me that my lovely tablet is beyond help! Is the only solution some wizardry using GParted or something? I'm already in way over my head.
I'm only bugging you all as I am running out of time in town and need to head off into the wilds. I have tonight and that's it for at least a week. It would be nice to have some company ie books and music...oh and a Turkish dictionary and translator...poor attempt to drum up sympathy I know.

I'll be honest, I've never seen such an issue as yours but it's worth a try since you got fastboot to do fastboot format of all your partitions and see if it helps to flash factory image. Something like fastboot format system for example.
Sorry I can't be more help
Nexus 7 LTE
Carbon Rom
Faux Kernel

dondelion said:
I have now tried every toolkit I can find but still no joy. I seem to have corrupted my partition table which is preventing me writing anything to the device.
To confirm - I can boot into fastboot mode and can see the device via fastboot using command line and can unlock it using 'fastboot oem unlock'. I have the images to write using 'fastboot flash boot/recovery/system [image location] but nothing will let me write to the device without receiving the error 'FAILED - remote: partition table doesn't exist'.
I have searched everywhere and can't find very much. Is the device recoverable or have I fecked it...? I need to get out of internet cafes and onto my bike...
Cheers in advance
Click to expand...
Click to collapse
Remove Wug's drivers and what ever other old drivers you have and follow this tutorial http://forum.xda-developers.com/showthread.php?t=2381582 make sure your getting for the data and not WiFi only. Get them old drivers out of there first.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

Raverbunny said:
I'll be honest, I've never seen such an issue as yours but it's worth a try since you got fastboot to do fastboot format of all your partitions and see if it helps to flash factory image. Something like fastboot format system for example.
Sorry I can't be more help
Nexus 7 LTE
Carbon Rom
Faux Kernel
Click to expand...
Click to collapse
Fastboot format still appears to require an intact partition table as I still receive an error - 'FAILED (command write failed (invalid argument))' but thank for the response.
LinearEquation said:
Remove Wug's drivers and what ever other old drivers you have and follow this tutorial http://forum.xda-developers.com/showthread.php?t=2381582 make sure your getting for the data and not WiFi only. Get them old drivers out of there first.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried this but same problem - no partition table so unable write anything to the device, thanks...

don, did you ever solve this?
I am having a similar problem but cannot unlock the device.

i have the same problem ....i just usedf flo-ebb clamours repartition and it wiped out all my partions i can only access fast boot but cant install anything as it says " no such partition "

Is your bootloader unlocked? If so, you should be able to flash the factory image in fastboot.
If not, you should be able to sideload the OTA in recovery.