I've read around on the forums trying many different things, but my problem is still here. ADB finds my phone when I am in normal phone mode, but once I go into fastboot mode it shows an empty list of attached devices. I've tried multiple different drivers and I've yet to have it show up. I tried on three different computers so far to no avail.
My friend got it working on his laptop once and flashed a kenel onto the phone that broke my wifi.. and we can't get ADB to load again to flash back the original. Sigh.
Can someone please help me?
So far I've tried HTC's drivers and the Universal drivers found on the Nexus forums. My Device Manager says Android USB Devices -> HTC, Corporation when my phone is in fastboot mode. the adb command shows List of devices attached and a black line after that. I'd show images if XDA didn't block me.
ICruentusI said:
I've read around on the forums trying many different things, but my problem is still here. ADB finds my phone when I am in normal phone mode, but once I go into fastboot mode it shows an empty list of attached devices. I've tried multiple different drivers and I've yet to have it show up. I tried on three different computers so far to no avail.
My friend got it working on his laptop once and flashed a kenel onto the phone that broke my wifi.. and we can't get ADB to load again to flash back the original. Sigh.
Can someone please help me?
So far I've tried HTC's drivers and the Universal drivers found on the Nexus forums. My Device Manager says Android USB Devices -> HTC, Corporation when my phone is in fastboot mode. the adb command shows List of devices attached and a black line after that. I'd show images if XDA didn't block me.
Click to expand...
Click to collapse
Adb doesnt work in fastboot. Use fastboot flash boot boot.img then flash the kernel modules in recovery.
Sent from my HTC6435LVW using xda app-developers app
Wow
Thank you very much. Complete noob at playing with Android devices .
When you flash a kernel, you have to make sure to also flash the kernel modules in recovery. That's what caused the wifi to stop working. Same thing happened to me haha.
Sent from my (Viped out)³ DROID DNA
Related
Hello being the noob i am i cannot restore any roms to my prime i accedntally wiped the whole internal partition and currently only have twrp installed it is version 2.2.0 i cant seem to get it to show in windows nor do i know the command in twrp for the sd card as i have a rom on there but it wont let me access it. im pulling my hair out and at the moment my prime wont swich off as it just keeps turning itself on and going to the ee pad logo and stopping there
can someone please help me to get it working again its probably simple but ive about had enough !! also cant get adb to work as the drivers keep faling to install on my pc error 10
HELP !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Slight update used wsg unbricker and now running clockwork mod instead of twrp dont know if thats good or bad at lest it proves pushing stuff to it works to a degree
Uberjim said:
Hello being the noob i am i cannot restore any roms to my prime i accedntally wiped the whole internal partition and currently only have twrp installed it is version 2.2.0 i cant seem to get it to show in windows nor do i know the command in twrp for the sd card as i have a rom on there but it wont let me access it. im pulling my hair out and at the moment my prime wont swich off as it just keeps turning itself on and going to the ee pad logo and stopping there
can someone please help me to get it working again its probably simple but ive about had enough !! also cant get adb to work as the drivers keep faling to install on my pc error 10
HELP !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Slight update used wsg unbricker and now running clockwork mod instead of twrp dont know if thats good or bad at lest it proves pushing stuff to it works to a degree
Click to expand...
Click to collapse
Still trying to fix this I now have no recovery and just get the two icons wipe data and fast boot or it just keeps trying to load a Rom that isn't there so it sticks on the main logo screen if I could get it to show in windows that would be great but now I have no recovery I'm not sure how to even get it to install anything once I do !
deleted
As long as you have the fastboot logo, there should be hope. First, you will need to do whatever you can to get your computer to recognize fastboot mode. In order to do this, click on the fastboot icon on your prime and then plug your usb into your pc. What does windows say? Is the device showing in the windows device manager?
Sent from my SO-01C using xda app-developers app
kokopuphz said:
As long as you have the fastboot logo, there should be hope. First, you will need to do whatever you can to get your computer to recognize fastboot mode. In order to do this, click on the fastboot icon on your prime and then plug your usb into your pc. What does windows say? Is the device showing in the windows device manager?
Sent from my SO-01C using xda app-developers app
Click to expand...
Click to collapse
It shows up but then says failed to install driver will try it on different pc,s see if it works thanks for the replies seems fairly easy
Ive found on my device that it sometimes requests two different drivers. One for adb/fastboot, and one for mtp. I just cancel the one for mtp as they are not in the naked driver set, and windows then detects another different device.
Sent from my SO-01C using xda app-developers app
okay fast boot is working and the android bootloader device shows in installed drivers but when i type in adb devices nothing shows up ?
Uberjim said:
okay fast boot is working and the android bootloader device shows in installed drivers but when i type in adb devices nothing shows up ?
Click to expand...
Click to collapse
Okay, you're half way home! The reason why nothing shows in adb is because fastboot and adb are two completely different interfaces. When in fastboot, your device will be expecting the fastboot command only.
Now what you will have to do is find a recovery that is in the blob format. Cwm would probably be okay. Twrp would be good, however the new version requires the nvflash version of the bootloader.
Once you find the blob of the recovery you want, place this in the same folder as the file fastboot.exe
It should be in the same place as adb. If not, place the blob somewhere easy to remember.
Then in a command prompt, type
fastboot -i 0x0b05 flash recovery blobfilename
If you placed the blob in the same place as fastboot, then the above will be the blob filename, or better would be to include the path as well.
Sent from my SO-01C using xda app-developers app
Looks like this could help
http://forum.xda-developers.com/showthread.php?t=1662158
Sent from my PadFone using Tapatalk 2
hi guys and girls happy to report that thanks to the community my prime is aliiiive !!! used a utility off here called knives and forks to install adb and then downloaded fast boot and extracted to my users directory then used the fast boot command to push the blob to the prime into recovery then used adb push adb push virtuous_prime_s_9.4.2.21_v1.zip /sdcard/ and installed virtuous to get it running then it all shows up thankyou to everyone so happy took all of five minutes lol. my trip to london for 3 hours will be less boring now !!!:laugh::highfive:
Hi anyone willing to help. I have had a friend's TF201 for about a month and have come to the point where I can't get any further. We believe heis device has been bricked during the OTA JB update. nvFlash was never added to device.
I can get it into fastboot, however the device does not show up in device manager or shows in ADB. I have confirmed ADB working by using another device that shows up. I know that it is currently on an ICS bootloader, since the NVIDIA logo is in the center bottom. We have tried a different cable and same results.
MOST IMPORTANTLY: which I have not been able to find any literature on is that when it is booted into fastboot only 2 icons appear: 'Wipe Data" and "Fast Boot" USB Icon. There is no Android icon...THIS confuses and scares me.
Is there any hope for this device? I have done so much research and time on this, but can not come up with anything else. Anyone??
Tried connecting in ADB in Win, Mac and Ubuntu. Not showing up? Totally stumped now.r
Bump.
ZeroLozen said:
Bump.
Click to expand...
Click to collapse
You do not have access to adb in fastboot. Only in a custom recovery or in the OS.
You do have access to fastboot commands tho if you have the drivers installed.
Having bricked a tf300t with the 4.2 Ota, I feel ya. Make sure you've got the correct drivers. Look at connected devices on your PC, it should say fast boot device, if it does, then your drivers are fine, going into fast boot, fastboot devices in cmd / however you have your fast boot set up. Look for your devices serial number.. It should show serial , if your drivers are correct..
Sent from my ASUS Transformer Pad TF300T using xda premium
I have tried all necessary things for drivers including the naked driver set for Win. Device wont show up in Linux or Mac environment either. it appears that the fastboot is ICS but it received the OTA JB update. Is there a way to recover from this? The other thing that concerned me is that in fastboot there is no Android Logo (just wipe data, and USB). Is this device recoverable from this state?
You have the upgraded bootloader. They removed a few things but it goes instantly to download mode..... when plugged in to pc. What does it say under control panel / hardware and printers. . When you plug it in. Does it make the tell tale sound?
Sent from my SPH-D710 using Tapatalk 2
Actually I think the incorrect fastboot had been loaded before I got it. To my understanding the OTA JB update was applied and then fastboot was added (but if the nVidia logo is in the center, that is the ICS fastboot correct?) So is my problem here that the incorrect fastboot had been flashed?
Hi!
First off let me say thanks to R_a_z_v_a_n for redirecting me and hope that I'll find my answer here ^^
So I Have this device called HP 7 VoiceTab 1321RA (not with Slate just HP 7 Voicetab), wanting to have a custom recovery then I tried to flash a CWM Custom Recovery for HP Slate 7 VoiceTab because I thought it was the same and ends up bricking my phone. It ends up in a bootloop which only shows HP sign for a few seconds and dead. But I managed to find out that I can access the recovery menu (or so I thought it is), but the options was choosing between Fastboot Mode, Normal Boot, Recovery Mode, and VART Mode.
I tried to enter Fastboot Mode before and tried to access it via PC but somehow I can't find the device by entering adb devices and fastboot devices. Anyways, I have downloaded a stock update.zip for it but not the original KitKat one which I get from the first time I bought it but rather the JB ones. I think by flashing this would help me recover the device but the only problem is I don't know which method should I use to Flash it. Since I don't have the Stock Recovery or ANY kind of recovery at all, I guess I'm stuck. And it won't start to the home page so I can't set the USB debugging options. Please guide me through this >.<
Thanks a lot!
Been fighting with it for 2 days now and still no result came.
So here's the update so far....
I tried on my other device in order to understand how my PC reads ADB and now I kinda gets it. But the problem is now can't get the device to enable USB Debugging because I can't access options at all.
Secondly, since I left it on for the night because charging seems to trigger the bootloop too, now I can't access the fastboot mode like I was last night. And it constantly repeating this sequence: [battery scene with the "charging battery" symbol] > [HP Powered by Android screen] repeated for 2-3 times > [low battery need charging screen] > repeat. And once I tried to connect to the PC, it goes to the same sequence too. When I tried to access the boot options (the screen which displays Fastboot Mode, Normal Boot, Recovery Mode, and UART Mode which I mention in Thread Starting post), it shows the low battery need charging scene and then repeating the same sequence as mentioned above.
I seem to figure out how to fix this but I still can't manage to access the fastboot mode yet. Will give update once I can try to.
Anyone can help me on this?
Thanks a lot!
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
I found my self in a deadlock!
PLEASE HELP :crying:
Could you unbrick yours
What service centre says about that problem i also ran in this problrm but i m trying to go to service centre for that
first off install drivers in your PC as admin
then use the official flashtool to flash ur stock firmware by entering fastboot or flashmode simple as that
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
Dude urs is a mtk device so sp flash tool should do the trick.... Just don't forget to install correct drivers....run both drivers and flash tool as admin..... Tell me when it's solved k
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
That is what im trying. To tell you urs is a mediatek device the official flashtool is sp flashtool
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
try to push the update.zip via adb sideload (Choose "update via ADB sideload" on recovery mode)using adb terminal on PC,as long as your tab can access the recovery mode.remember to backup all your data before u do it.
have a try it's 100% work on me
where I can download update.zip file? anyone can help?
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
can you explain how did you managed to charge the device??? please its a request......jst help me out :crying::crying:
`Dear Admin,
Hi my Name is Zaki.... i am using HTC Rezound which i purchased in U.A.E
After installing whatsapp i got continious restart problem so i downloaded stock firmware of ICS version. all was good but by mistake i clear internal storage in fastboot mode. and after that i am unable to get into TWRP Recovery mode, it is showing phone with with arrow circle and after few second it converted into phone with triangle (attached screens 2 and 3) please explain me with links how to get TWRP again. and the links for TWRP versions i am not sure which is ok.
Please Reply.
syedzakiabidi said:
`Dear Admin,
Hi my Name is Zaki.... i am using HTC Rezound which i purchased in U.A.E
After installing whatsapp i got continious restart problem so i downloaded stock firmware of ICS version. all was good but by mistake i clear internal storage in fastboot mode. and after that i am unable to get into TWRP Recovery mode, it is showing phone with with arrow circle and after few second it converted into phone with triangle (attached screens 2 and 3) please explain me with links how to get TWRP again. and the links for TWRP versions i am not sure which is ok.
Please Reply.
Click to expand...
Click to collapse
You can't access TWRP because you over-wrote it with the factory RUU firmware image, it isn't there anymore...
Download TWRP image from TWRP official site at https://dl.twrp.me/vigor/ or Flyhalf's build at http://forum.xda-developers.com/showthread.php?t=1902381
Either one is good... then start fastboot, connect usb and flash recovery with the command:
fastboot flash recovery <path/filename of TWRP IMG file>
give it a minute or so, reboot into Hboot and start TWRP.
im having a similar issue but my computer always says waiting for device in command prompt. I have all the drivers installed and the phone says "usb fastboot" or "fastboot usb" (cant recall what order those 2 words are in LoL)
youdoofus said:
im having a similar issue but my computer always says waiting for device in command prompt. I have all the drivers installed and the phone says "usb fastboot" or "fastboot usb" (cant recall what order those 2 words are in LoL)
Click to expand...
Click to collapse
You probably have a driver issue then... Install HTC Sync, connect the phone, then disconnect it, remove HTC Sync and it should work. If that doesn't work, try a different USB port.
Honestly, I switched to Linux a long time ago... I don't have driver issues. If you were running Linux, even a live or USB key distro, you would access it easily.
acejavelin said:
You probably have a driver issue then... Install HTC Sync, connect the phone, then disconnect it, remove HTC Sync and it should work. If that doesn't work, try a different USB port.
Honestly, I switched to Linux a long time ago... I don't have driver issues. If you were running Linux, even a live or USB key distro, you would access it easily.
Click to expand...
Click to collapse
fair point, and i do have ubuntu (of differing flavor dates) on 3 of my machines, so i might just do that. Thanks!! Ill also try the goofy htcsynch (which i forgot about, as im a Sammy guy now) Thanks again!!
I had TWRP installed and all was good. Then I tried an OTA update. Update failed and now I can't get into recovery or fastboot. When I try it stops at the 1+ logo with Fastboot Mode written under the logo. This happens if I try Volum Up + power button or adb reboot-bootloader. Device is listed with ADB but won't show up for fastboot.
How do I get back to stock recovery and get the update installed?
Thanks!
Is fastboot installed properly on your PC?
Drivers?
If not and you get it working, you can use fastboot to flash a new recovery. Otherwise read ahead.
Does your phone boot? Is it rooted?
If so, you can try to flash a new recovery via tools like FlashFire, Flashify, Rashr, etc.
If none of those work for you, you can try the un-bricking methods.
I've had my Oneplus 2 hardbrick 3 times on me so far. The solution was to put the phone into a Qualcomm QHUSB_BULK mode, installing unsigned drivers in Windows, and using Chinese software to push recovery files to your phone.
For my first two hard bricks (My phone wasn't responding to anything - it would just show up in the device manager when plugged into the PC). I was able to write the stock recovery and boot files onto my phone by using Method 1 from this OnePlus Forums thread: https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/.
I was then able to boot to recovery and dirty flash my OS without any data loss this way.
The last hard brick was much worse and required me to completely reinstall everything on my phone via one of the other methods (I used this link: http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449 and ended up with H2OS, which I then replaced with OOS 3.1.0) - if it comes to that I would recommend checking out the other methods in the OnePlus Forum link below to hopefully avoid going through H2OS - but if not, this one worked.
Also, for updates: You'll need to to reflash (dirty flash) your rom first (this is to unroot/undo any modifications you made to the system, otherwise the OTA will fail) and then flash the OTA. You should be able to use TWRP for this.
Thanks for the reply. Got fastboot working on a different computer.
Phone boots just fine. Not rooted. Just can't access recovery mode or install updates
I tried loading stock recovery (as per this thread) with no change. Thinking I'll have to treat it like it's bricked. Would rather not have to wipe phone though, but doesn't look like I have much choice .
For the past two days I had faced the issue of connecting the device in fastboot mode. Mobile is working fine, loaded with latest firmware OTA updates from OnePlus.
I would like to install TWRP on my mobile but the device is getting detected in the fastboot mode. Tried various steps, reinstalled adb & fastboot as well as OnePlus drivers nothing works. However my mobile is being detected in the adb mode. If I run the command adb devices, it displays my mobile serial number but in fastboot it just sits at the waiting for the device screen.
After a lot of googling, xda search & Oneplus forums search, nothing found. Then I tried reinstalling the adb interface drivers manually, where I have noticed that Win10 installed the latest drivers adb drivers updated in the month of Sep16. Here I have selected the older version driver which was released in the year 2014 and installed it successfully. I run the fastboot devices command again Voila... It worked. no restart, no rebooting the phone. Immediately worked.
Lesson learnt : - Always do not use latest drivers, sometimes try the older drivers if something is not working in your phone.
CrazyArjun said:
For the past two days I had faced the issue of connecting the device in fastboot mode. Mobile is working fine, loaded with latest firmware OTA updates from OnePlus.
I would like to install TWRP on my mobile but the device is getting detected in the fastboot mode. Tried various steps, reinstalled adb & fastboot as well as OnePlus drivers nothing works. However my mobile is being detected in the adb mode. If I run the command adb devices, it displays my mobile serial number but in fastboot it just sits at the waiting for the device screen.
After a lot of googling, xda search & Oneplus forums search, nothing found. Then I tried reinstalling the adb interface drivers manually, where I have noticed that Win10 installed the latest drivers adb drivers updated in the month of Sep16. Here I have selected the older version driver which was released in the year 2014 and installed it successfully. I run the fastboot devices command again Voila... It worked. no restart, no rebooting the phone. Immediately worked.
Lesson learnt : - Always do not use latest drivers, sometimes try the older drivers if something is not working in your phone.
Click to expand...
Click to collapse
can you share those drivers,,facing same issue actually