Hi
I have always used cwm to put a rom on my wifes folio, mainly because I could not get fastboot to work.
With this new jelly bean rom, I cannot do it that way and need to fastboot, tried and failed again. Cannot see how to get the driver for the connection. Its driving me mad and really need some help, tried surfing here to find a solution and had no luck
David.
davjet said:
Hi
I have always used cwm to put a rom on my wifes folio, mainly because I could not get fastboot to work.
With this new jelly bean rom, I cannot do it that way and need to fastboot, tried and failed again. Cannot see how to get the driver for the connection. Its driving me mad and really need some help, tried surfing here to find a solution and had no luck
David.
Click to expand...
Click to collapse
I suppose you're running Windows?
Have you followed this guide to modify the drivers?
Yes, using windows but now its windows 8, is there any difference?
Sent from my Galaxy Nexus using xda app-developers app
fastboot works from xubuntu 12.10
Hi,
You might want to try xubuntu 12.10 as a plattform for fastboot. xubuntu runs on really old HW - mine is 8 years old. fastboot can be installed right from the SW Center. To flash the recovery image I had to use
fastboot -S 0 flash recovery name-of-recovery-image
Besides xubuntu is worth a try anyhow.
Best regards
Related
Hi guys,
I have a touchpad that had android since the first day, I managed to crash it totally, so now I only have a fastboot interface left.
My question, would there be a way to flash CM7 or CM9 on it without novacom running ? (I simply don't have that), or better would there be a way to reflash the bootloader so that it has bootie and webos ? .. any answers / tricks would be appreciated
henri_p said:
Hi guys,
I have a touchpad that had android since the first day, I managed to crash it totally, so now I only have a fastboot interface left.
My question, would there be a way to flash CM7 or CM9 on it without novacom running ? (I simply don't have that), or better would there be a way to reflash the bootloader so that it has bootie and webos ? .. any answers / tricks would be appreciated
Click to expand...
Click to collapse
What do you mean crash it totally? Do you not have access to a PC? Can you not get into recovery?
Sent from my cm_tenderloin using Tapatalk 2
I have looked but I cannot find anything on how to get fastboot for Nook Tablet working (and yes I do have CM9 0.05.1) and I want to flash recovery but it is not recognizing my Nook. All it has on device manager is Other Devices/ Acclaim with an exclamation point. Please help
Hi, have you installed adb succesfully in your pc previously?
If yes then the next thing you need is fastboot.exe file, if not then start with that first then fastboot.
You can find what you need here, also if you search in my threads (link in my signature) you can find a tutorial about how to install and use ADB.
~ Veronica
Acclaim
I have the same challenge. I have ADB working successfully (and have used Veronica's guide to repartition my NT - thanks again). Yet when I use Cyanoboot and start Fastboot my device shows up in Other Devices as Acclaim and none of the USB drivers I have pointed to get installed. It isn't mission critical that I solve this but it would be nice from a knowledge base to understand what I am missing in case I ever need to use Fastboot. It seems to be a much easier tool to change the installed Recovery image than ADB. Any help would be appreciated.
adb works for me. i currently have cyanoboot, when i try to go to start fastboot to install a new recovery, i notice in my device manager there is an uninstalled driver called "Acclaim". Already tried the NT drivers for it and it didn't work. Any ideas? I recently flashed succulent's cm7 image which had a cwm v5.0.x and i want to flash cwm v 5.5.x. Already tried using indirect's NT recovery flasher and no go on that...
ShinnAsuka said:
adb works for me. i currently have cyanoboot, when i try to go to start fastboot to install a new recovery, i notice in my device manager there is an uninstalled driver called "Acclaim". Already tried the NT drivers for it and it didn't work. Any ideas? I recently flashed succulent's cm7 image which had a cwm v5.0.x and i want to flash cwm v 5.5.x. Already tried using indirect's NT recovery flasher and no go on that...
Click to expand...
Click to collapse
+1
Can someone upload fastboot mode driver for NT for me? I turn my NT into bootloader but my PC can't "see" NT so I can't fastboot recovery.img.
Thanks.
Sorry for my bad English.
bingoz said:
Can someone upload fastboot mode driver for NT for me? I turn my NT into bootloader but my PC can't "see" NT so I can't fastboot recovery.img.
Thanks.
Sorry for my bad English.
Click to expand...
Click to collapse
when doing fastboot do you see "acclaim" under other devices in device manager? I had to install another set of drivers in order for fastboot to work.
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
when doing fastboot do you see "acclaim" under other devices in device manager? I had to install another set of drivers in order for fastboot to work.
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
My PC search for driver but I can't install. Would you please send me link to "set of drivers in order for fastboot to work"? Thank you very much
bingoz said:
My PC search for driver but I can't install. Would you please send me link to "set of drivers in order for fastboot to work"? Thank you very much
Click to expand...
Click to collapse
you need to find the id of the nook under other devices acclaim. then you modify the android_winusb.inf file with those new id's and install the drivers
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
you need to find the id of the nook under other devices acclaim. then you modify the android_winusb.inf file with those new id's and install the drivers
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
Can you explain more or upload the file already edit for me? Thank you
bingoz said:
Can you explain more or upload the file already edit for me? Thank you
Click to expand...
Click to collapse
each product id is different so uploading the file isn't going to do you much good. sorey
Sent from my Nook Tablet CM7 BETA using xda premium app
mamifsidtect said:
I have looked but I cannot find anything on how to get fastboot for Nook Tablet working (and yes I do have CM9 0.05.1) and I want to flash recovery but it is not recognizing my Nook. All it has on device manager is Other Devices/ Acclaim with an exclamation point. Please help
Click to expand...
Click to collapse
I don't have windows so I won't comment on that. There is one thing that I never see mentioned when talking of adb access problems.
On custom roms (your case cm9 0.05.1) in settings, developer options, Android debugging should be checked to allow adb access. If not checked that may be your issue.
If I'm having adb issues and it was working previously I'll boot to cwm (5.5.0.4 version not 5.0.2 or whatever) and go from there.
You should get adb working properly, but to flash recovery you can use one of the flashable zip files while in cwm. They work for me!
Got a few minutes on a windows 7 pc (people should take their breaks at their desk). If you are using Veronicas thread http://forum.xda-developers.com/showpost.php?p=22049356&postcount=1 you will find a file runmefirst.bat if you run it and follow instructions about unplugging and replugging nook it will create and setup the previously mentioned file. Do not run zergy as suggested. When it pulls device manager your exclamation should say nook. Right click it, update driver software, browse my computer, let me pick, and then choose the directory with your usbdrivers, tell it yes to use them. Do not worry about anything else from runmefirst.bat including anything else to run. You just want it to set the codes for your nt and then it is of on use.
I had adb working for my nt quickly on that windows 7 pc. It had no previous adb or usb drivers installed.
Good Luck
I got nook tablet drivers installed and it works for adb however fastboot still has acclaim!
anyone have steps how to fix this?
fastboot has no devices
nba1341 said:
I got nook tablet drivers installed and it works for adb however fastboot still has acclaim!
anyone have steps how to fix this?
fastboot has no devices
Click to expand...
Click to collapse
like i said in a previous post, right click the acclaim item under other devices and look for the product id and edit the android_winusb.inf accordingly.
after that right click acclaim, update driver software, and browse for the drivers yourself. if all goes well fastboot should work. this is how i did it. not that i ever really use fastboot but its good to have just in case.
Is there any step-by-step tutorial on how to flash NT with fastboot? I have tried to search, but still could not get it work.
Thanks.
mamifsidtect said:
I have looked but I cannot find anything on how to get fastboot for Nook Tablet working (and yes I do have CM9 0.05.1) and I want to flash recovery but it is not recognizing my Nook. All it has on device manager is Other Devices/ Acclaim with an exclamation point. Please help
Click to expand...
Click to collapse
Check your android_winusb.inf to see if you have the right entry for the NT -- see http://forum.xda-developers.com/showpost.php?p=35971559&postcount=13.
---------- Post added at 12:19 AM ---------- Previous post was at 12:15 AM ----------
Penguin101 said:
Is there any step-by-step tutorial on how to flash NT with fastboot? I have tried to search, but still could not get it work.
Thanks.
Click to expand...
Click to collapse
Why not flash your NT using SD-based CWM Recovery (e.g., see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31)?
The easiest way under windows, is just choose the driver on your own, use the driver from the Android SDK (sdk\extras\google), and you will be presented with a couple of options, choose Android Composite ADB Interface.
I'm trying to get this tool Minimal ADB and Fastboot installed on my PC, wan't to get rid of the large android-sdk folder. Problem is that I'm on Windows 8.1. Are there any drivers out for the Rezound that are compatible with my OS? I need the drivers so my phone is recognized.
xXezmacXx said:
I'm trying to get this tool Minimal ADB and Fastboot installed on my PC, wan't to get rid of the large android-sdk folder. Problem is that I'm on Windows 8.1. Are there any drivers out for the Rezound that are compatible with my OS? I need the drivers so my phone is recognized.
Click to expand...
Click to collapse
to put it lightly....no not really....most are made for windows 7...a google search may be able to help more....you may be able to do a compatability mode install but i cant guarantee itll work
HTC hasn't made drivers for any device on windows 8.1. Why not just use a linux live CD for your phone needs? Or just use linux all together, no need for drivers there
Sent from my dlx using xda app-developers app
Uzephi said:
HTC hasn't made drivers for any device on windows 8.1. Why not just use a linux live CD for your phone needs? Or just use linux all together, no need for drivers there
Sent from my dlx using xda app-developers app
Click to expand...
Click to collapse
Thx for the advice but I wouldn't even know where to begin. I'm pretty tech Davy but computer's, os, aren't really my strong point. Even ubuntu scares me lol.
Sent from my ADR6425LVW using Tapatalk
There are some noob friendly distros out there for the beginner who knows nothing about linux. Almost all linux distros have live CDs to try them out before install.
Sent from my dlx using xda app-developers app
I am using this: http://forum.xda-developers.com/showthread.php?p=45417322
For adb and fastboot stuff, and I'm running Win8.1.
Sent from my ADR6425LVW using Tapatalk
tmanschuette said:
I am using this: http://forum.xda-developers.com/showthread.php?p=45417322
For adb and fastboot stuff, and I'm running Win8.1.
Click to expand...
Click to collapse
Thanks for posting that link here. I know the Rezzy is a dying breed, but I still have mine, and I always have a heck of a time getting my Windows 8-OS computer to recognize my device correctly. The tool pointed to in your link seems to keep adb/fastboot updated as well.
I'm already rooted, but I started up the app as administrator connected the phone, refreshed in the About Phone tab, and lo and behold, it recoginized it. The only test I ran was to boot into the bootloader using the tool. No problems. Hope other tasks go just as well...
cheers,
john
Uzephi said:
HTC hasn't made drivers for any device on windows 8.1. Why not just use a linux live CD for your phone needs? Or just use linux all together, no need for drivers there
Click to expand...
Click to collapse
so just running a live disc can connect me with fastboot commands?
I imagine this is consistent for all of the android phones I'm tinkering and learning with (rezound, one, s3)?
sockaplaya14 said:
so just running a live disc can connect me with fastboot commands?
I imagine this is consistent for all of the android phones I'm tinkering and learning with (rezound, one, s3)?
Click to expand...
Click to collapse
if trying to obtain s-off or flashing anything via fastboot via linux my guide is what you will need bud....seeing as windows 8 still has many bugs and issues...
REV3NT3CH said:
if trying to obtain s-off or flashing anything via fastboot via linux my guide is what you will need bud....seeing as windows 8 still has many bugs and issues...
Click to expand...
Click to collapse
I have to agree with this... use the Linux version and boot via a live CD.
jrredho said:
The only test I ran was to boot into the bootloader using the tool.
Click to expand...
Click to collapse
Since the time of my original post in this thread, I've now tried to use fastboot commands. No dice. This all-in-one is definitely not a panacea for Win8.1 users.
So I'd have to agree with other users in this thread: Use a Linux variant for your work on HTC phones. Adb and fastboot are line commands for Heaven's sake, so most tasks won't require one to learn and understand the ins and outs of Linux.
Good luck,
john
jrredho said:
Since the time of my original post in this thread, I've now tried to use fastboot commands. No dice. This all-in-one is definitely not a panacea for Win8.1 users.
So I'd have to agree with other users in this thread: Use a Linux variant for your work on HTC phones. Adb and fastboot are line commands for Heaven's sake, so most tasks won't require one to learn and understand the ins and outs of Linux.
Good luck,
john
Click to expand...
Click to collapse
or downgrade to windows 7...lol
i accidentally wiped everything via TWRP and now i am stuck in recovery with no os and no way to put a ROM on. I don't know if there is a wireless adb feature in recovery but i have had no luck (plenty of Googleing ) i at at my wits end at this point, any help would be greatly appreciated
wildestweasal said:
i accidentally wiped everything via TWRP and now i am stuck in recovery with no os and no way to put a ROM on. I don't know if there is a wireless adb feature in recovery but i have had no luck (plenty of Googleing ) i at at my wits end at this point, any help would be greatly appreciated
Click to expand...
Click to collapse
The first thing we need to know is what OS is on the PC so you can get the right drivers. Do you have the SDK set up and workiing?
wildestweasal said:
i accidentally wiped everything via TWRP and now i am stuck in recovery with no os and no way to put a ROM on. I don't know if there is a wireless adb feature in recovery but i have had no luck (plenty of Googleing ) i at at my wits end at this point, any help would be greatly appreciated
Click to expand...
Click to collapse
The experimental twrp doesn't work for me for adb. If that's what you're running, you can try rebooting to the bootloader and flashing the last official twrp to see if that works.
crpalmer said:
The experimental twrp doesn't work for me for adb. If that's what you're running, you can try rebooting to the bootloader and flashing the last official twrp to see if that works.[/QUO
idk its the 2.6.3 version. But fastboot doesnt even respond i think my usb port when out but i ordered a replacement though got tired of messing with it thanks though
Click to expand...
Click to collapse
wildestweasal said:
crpalmer said:
The experimental twrp doesn't work for me for adb. If that's what you're running, you can try rebooting to the bootloader and flashing the last official twrp to see if that works.[/QUO
idk its the 2.6.3 version. But fastboot doesnt even respond i think my usb port when out but i ordered a replacement though got tired of messing with it thanks though
Click to expand...
Click to collapse
I am running same version, no issues. can your PC see the unit? Does the PC respond when the unit is connected when the Android system is booted up?
Click to expand...
Click to collapse
wildestweasal said:
i accidentally wiped everything via TWRP and now i am stuck in recovery with no os and no way to put a ROM on. I don't know if there is a wireless adb feature in recovery but i have had no luck (plenty of Googleing ) i at at my wits end at this point, any help would be greatly appreciated
Click to expand...
Click to collapse
If your not on Windows 7 your going to need it.
I am running same version, no issues. can your PC see the unit? Does the PC respond when the unit is connected when the Android system is booted up?[/QUOTE]
............no it has no (OS)
wildestweasal said:
I am running same version, no issues. can your PC see the unit? Does the PC respond when the unit is connected when the Android system is booted up?
Click to expand...
Click to collapse
............no it has no (OS)[/QUOTE]
Does the PC respond when in fastboot? What OS is on the PC?
i have the same issue and my computer dosent respond when in fastboot or adb i have no os and im twrp 2.5 can anyone help...
demon28 said:
i have the same issue and my computer dosent respond when in fastboot or adb i have no os and im twrp 2.5 can anyone help...
Click to expand...
Click to collapse
Download pdanet it will re download adb
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Hello.
I have a problem with friend's phone.
It's HTC Desire Z (Vision). I S-OFFed how it's described on CM wiki. Latest radio.
About month ago I installed CM 10.1 AlterNdromadus.
It worked until yesterday, when it unfortunately installed some system update.
After that phone didn't booted anymore. In recovery it says, that it can't access system partition and formatting is not possible.
I tried connect the phone via fastboot in bootloader, but it also doesn't work. Under windows I have it as unknown device and when I tried manually install drivers from google, it says that they are not compatible with the HW (under ROM it worked before).
I tried also install stock RUU rom (extracted the zip and deleted H-BOOT, radio and recovery) from SD-card (PC10IMG.zip). But it also got frozen on system update.
Here you can see error from 4EXT recovery and CRC images from bootloader.
Any suggestions? :crying:
Thanks
Well, I guess I meant to keep this thread in the desire z q&a thread but this works
I wish we could know what kind of system update was flashed as it may be easier to fix this
There shouldn't have been any system update as there is no ota associated with that ROM, but we can try anyway
http://forum.xda-developers.com/showthread.php?t=2348266
Here you will find links to get you proper drivers, being your on windows try using a free program called USBDeviw, I have had to use this a lot to erase drivers and then manually install the proper ones (windows is terrible at this)
Or if you can dual boot Linux you may find life easier as once you get fastboot working you should be able to quick fix this.
Otherwise try out the aio wipe tool and or superwipe script that is linked in the guide I sent you
But really, try to get the drivers working and we should be good
Sent from my Nexus 4 using XDA Premium 4 mobile app
Tried both superwipes. Doesn't work :/
The problem with fastboot is, that windows totally doesn't recognize the device. So I'm not able to install any drivers (see attachment).
The reason why I posted it in this section is, that I found people with similar problem on other phones. But noting work to get it back...
Any recommendation for the linux?
I booted successfully SystemRescueCD. After a half hour I also went ADB but no devices were found...
The screenshot is blurry when looking at it from my phone but it looks like windows 8/8.1 which many have issues getting adb/fastboot to work right. Usually the fix involves using usb3.0 ports
Can you just dual boot a Linux distro? Ubuntu is a very simple one to work with and you will easily find guides how to get fastboot working on it, actually if you see the thread I linked you there is one on fastboot that walks you through the process
If you don't want to dual boot a live CD is fine, but you still need to get the adb/fastboot binaries installed and working from that disc
Sent from my Nexus 4 using XDA Premium 4 mobile app
Yes, it's windows 8.1. I don't have USB3.0.
I have here also one really old desktop with windows 7, I will give it a try.
Otherwise last chance is the Ubuntu (I don't want to dualboot, so I will made live USB).
I downloaded from XDA two files - ADB and fastboot for Linux.
Downloading and installing adb from SDK from google doesn't look so easy as on windows...
Also should I use drivers from HTC sync or from google SDK?
Because through ROM it worked right with the google's drivers...
although this is not what you may want as an answer but why don't you copy a ROM to SD card n flash via recovery,, it'll regenerate system,, once it is regenerated,, you can connect to your PC and carry on to what you want.
Nope. It doesn't work. I tried it as first option.
I just forgot to write it here....
seems like you might have actual physical damage/bad sector on ur device.
this is what happens in hard drives, they can't be formatted, no read/write etc.
i don't know if there's any app that can help fix you this coz you can't connect to system/OS in first place to do so,
Best option seems like to dust off the warranty papers n get it to service center for repairs as it might need physical parts replacement.
I got working fastboot (not ADB) on Windows7.
When I tried fastboot format /system I got error "Uknown command".
When I tried fastboot erase /system I got error "No partition found"
Yes, it's probably problem with bad blocks...
The issue at hand depends on what this 'update' was as the ROM that was running on the phone at the time would not have had one which means something was flashed to it that shouldn't have been.
Being the phone had security flags removed (soff) a number of things that shouldn't be allowed to flash can be, so depending on what it was will determine how fixable it is
At this point the only way to fix it or at least dertimine if it is fixable is to get phone and PC to connect via fastboot and adb
So use the windows 7 or Linux, set it up with drivers found in xda wiki or write the android rules for Linux and work on this, its doubtful you can move forward until this is done
Sent from my Nexus 4 using XDA Premium 4 mobile app
As I wrote, I got Fastboot worked.
BTW isn't possible to acces ADB only from the ROM?
I tried to get it work without success. I tried HTC and google drivers...
Must have posted while I was posting and I missed that
Fastboot only works from bootloader and adb only works in os and recovery
The commands you were using isn't correct, I suggest you read again the two fastboot links from the link I sent you for clear instructions.
For right now I would grab the latest cwm, twrp or 4ext recovery (4ext still best for this phone)
Then
fastboot erase system -
fastboot erase recovery
fastboot erase boot
Then
fastboot flash recovery nameofrecovery.img
Then if all goes well grab a known stable ROM and flash it (along with gapps if needed) from new recovery
If things don't work as planned be sure to copy and paste all input/output from cmd
Sent from my Nexus 4 using XDA Premium 4 mobile app