Im really struggling to find the correct fast boot drivers for the nokia 3.4 , im able to get it to fastboot via the adb platform (in android) but once my device is in the fast boot menu doesnt pick it up. Adb devices now comes up blank. iv tried unsigned drivers and tried google drivers, HMD drivers but none read it in fast boot menu. iv removed all drivers a few times via programs and reinstalled, iv tried differnt computer, iv even tried to do it over linux (which just showed my device as xiaomi. IF any one is able to share the .ini file for the correct drivers for nokia 3.4 that would be a great help (not generic ones) iv run into googles page 3 looking for a differnt set of drivers and tried tons but they mostly the same.
t1m0thy001 said:
Im really struggling to find the correct fast boot drivers for the nokia 3.4 , im able to get it to fastboot via the adb platform (in android) but once my device is in the fast boot menu doesnt pick it up. Adb devices now comes up blank. iv tried unsigned drivers and tried google drivers, HMD drivers but none read it in fast boot menu. iv removed all drivers a few times via programs and reinstalled, iv tried differnt computer, iv even tried to do it over linux (which just showed my device as xiaomi. IF any one is able to share the .ini file for the correct drivers for nokia 3.4 that would be a great help (not generic ones) iv run into googles page 3 looking for a differnt set of drivers and tried tons but they mostly the same.
Click to expand...
Click to collapse
Hello and good afternoon, @t1m0thy001
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved the thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
t1m0thy001 said:
Im really struggling to find the correct fast boot drivers for the nokia 3.4 , im able to get it to fastboot via the adb platform (in android) but once my device is in the fast boot menu doesnt pick it up. Adb devices now comes up blank. iv tried unsigned drivers and tried google drivers, HMD drivers but none read it in fast boot menu. iv removed all drivers a few times via programs and reinstalled, iv tried differnt computer, iv even tried to do it over linux (which just showed my device as xiaomi. IF any one is able to share the .ini file for the correct drivers for nokia 3.4 that would be a great help (not generic ones) iv run into googles page 3 looking for a differnt set of drivers and tried tons but they mostly the same.
Click to expand...
Click to collapse
I find many over Google Nokia 3.4 fastboot driver
Related
Hey, I've tried various methods of rooting my GSM Hero, and eventually found the method on this site entitled "VillainROM Roots 2.1 RUU for GSM Hero (Confirmed)". I got as far as trying to run runindos.bat, and this just returns the error as explained. If I run "adb devices" I get "List of devices attatched" and then just nothing after it. Strange.
Does it have anything to do with the fact that HTC Sync never picks up my phone?
Windows 7 64-bit
HTC GSM Hero
3 UK
Android 2.1
adb, drivers or usb debugging, check it
Sent from my HTC Hero using Tapatalk
USB Debugging is enabled, not sure how to check adb but what's the correct way to install the drivers? Is it by running the "SDK Manager" program in my SDK folder?
Moved to Q&A as not development.
Get the drivers via the sdk manager, and manually install them via device manager for the device.
Ahh, sorry about the wrong section. I assumed that Development would be things concerning roots.
SDK Manager only seems to let me install "SDK Platform Android X.X", I don't see any driver installations. Also, I'm not sure where it installs these to.
Edit:
Okay I tried to install "USB Driver" but Windows said that it was already up to date. Still not appearing in adb :/.
Hmmm. Search for drivers in dev forum, as I think I posted mine (or instructions to hack them) on one of the Froyd villain threads somewhere.
Also, I presume you have rebooted and tried adb right after reboot
Drivers for you
Thanks to you both, I'll try those later on today.
I'd rebooted both the PC and the phone and tried it. Nothing unfortunately. It just seems to be a big Windows 7 problem.
I use Win 7 without any problems.
Check out this epic guide by BTDAG,...
http://forum.xda-developers.com/showthread.php?t=776056
Good news and bad news. The drivers are now working, adb is working and runindos.bat is doing it's thing. Unfortunately, when it reboots the second time for recovery, there's just a red triangle with an exclamation mark in it.
I rebooted and got back to where I was, but how do I get the "Care Bear" boot screen? Am I supposed to have moved RA-Hero to my phone first or do I not need anything?
Thanks.
Hi Craig. I had to repeat process 4-5 times before it worked so make sure you have your new rom on SD for when it works. I had all same probs but it will get there. As pulser said on villain try changing directory to avoid echo. It seems to load a little more each time.
Sent from my living room.
Hmm, if the recovery thing with the phone in the background comes up, and has "apply:update.zip" as a selection, should I try that? I've tried a few times and that's usually what comes up, along with reboot phone and another couple of selections.
I've got it! Thanks very much for everything. I just kept doing it and it's working now. I got FroydVillain and I'm loving it! I never realized the Hero could be so smooth.
Also sorry for the double post, I'm used to auto-merging on formus.
Okay first off, I already flashed many Magic and HD2 Roms, so I know how to read guides and respect tutorials...
...but I just can't unlock my 10.1v !
I tried the method from the sticky and the method with Odin but nothing. The first one doesn't answer went I enter the commands (no waiting for device), the second seems to detect my tab but Odin doesn't do much when I click start.
I tried Ubuntu, Windows XP and 7. Best results were with XP. The main issue is the drivers. I pointed Windows to the usb drivers coming with Android sdk but it never seems to connect properly. With 7 the drivers never installs well, with XP it does but unlocking doesn't work any better.
I tried the Pdanet app drivers, I tried with and without adding in the .inf file the extra info about the 10.1v...
PLEASE HELP. I'm trying since Monday...
I have looked everywhere for answers but cant find any on how to get my phone to connect, well be recognized by my computers. I know exactly how to use Odin to get my phone out of its bricked stage through the download menu. But the thing is, it hasnt been recognized by my computers for awhile, even when i was using ICS on it, and i tried a lot of things but recently i havent been able to get it connected. I have no idea what to do, i need help on this urgently. Just to restate, my phone is not being recognized by my computer when plugged in through a working USB cord, please help
Go to Dev section and download the AIO toolbox (links are live again). It has Odin 1.8, the correct pit/tar files and drivers. Don't forget to download the .net files too in the OP.
Might have to go into device manager and delete the drivers you might still have in there that are bunked out.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
_kevn_ said:
I was able to get mine working with the combo of
1. uninstalling any HTC sync or sync manager and the HTC BMP USB Driver. Basically anything HTC.
2. Install HTC sync. Not sync manager. Go to the HTC support page and you'll see both listed. If you go to the specific phone support page it might not be there. (One S doesn't have the sync program, just sync manager iirc.)
3. Download PDAnet. When installing, It'll give a warning that you already have drivers installed and ask if you want to fix them or leave as is. I chose it to fix and it went though its process and I had working drivers after that.
I think this was already suggested before. I going back and giving thanks wherever due after this post. (On the mobile app right now)
Other easy way if you're using a One S is to download Hasoon2000's All-On-One Toolkit. He's updated the drivers for windows 8. I haven't tried it yet as mine are working so haven't had the need. I would assume his tool for any of the other phones he supports would have the updated drivers too.
Click to expand...
Click to collapse
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
_kevn_ said:
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
Click to expand...
Click to collapse
I am running Windows 8.1, however it looks like the fix only applies to Intel motherboards connecting through USB 3.0 ports. I do have USB 3.0 ports, but my motherboard is AMD and my USB3 controller reads "VIA USB 3.0 eXtensible Host Controller - 0100 (Microsoft)." I'm not sure that the fix applies to me, unfortunately. Also, I am not connecting my phone to my PC using the USB3.0 ports.
I tried downloading the USB 3.0 Drivers for Windows 8 64-bit on the manufacturer's website for my motherboard (http://www.gigabyte.us/products/product-page.aspx?pid=4305), but when I try to update my drivers to the ones I got from the website it says that the Microsoft provided ones are the most recent/ up to date drivers.
Daniuhl said:
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Click to expand...
Click to collapse
Be Advised, there is perhaps a way , you wil find in the link below, but be sure to use the right intel driver And only if you hae an intel chipset for usb3 , please read the comments and my bad experience :
Under win8.1/X64 that if you have(like me) an Intel 8 /c220 (or with a 4th generation like intel I7 4770k) you may encounter a big mess , and perhaps you''l have to do a clean install of win 8.1 : all the usb2 DEVICES were disconnected after the first iusb3xhc.inf driver install !! So no more usb/Bluetooth keyboard+mouse , fortunately i had an old ps2 keyboard and i was able to delete only with "tab/alt Tab/ctrl tab" keys the
"intel usb3 extensible " line in device manager, and as soon as i done a refresh (ALT+A) in device manager the previous driver(Microsoft) was reinstalled by win 8.1 andall the usb2 devices connected (mouse/keyb/hub etc)
http://plugable.com/2012/12/01/windo...#comment-19066
see there there's in the last comments at the bottom , Andrew(tks to him!)a link + modified drivers for intel8/c220)
and for me it worked mouse/keyB were functional during all the process
next step check the fastboot adb is working now
Here you go... http://forum.xda-developers.com/showthread.php?t=2061435
A later post I made (I havent updated the OP, shame on me...) is a link to some universal drivers from CWM that works fantastic! - http://forum.xda-developers.com/showthread.php?p=40108463#post40108463
Before trying this I would goto your device manager and right click on the currently installed drivers and uninstall them before installing the drivers again.
Hope that helps. I am using the link found in that second link and fastboot and adb works perfect. Also, while you can boot into fastboot, stock 1.58 will not let you run a lot of fastboot commands and will need to flash a different hboot.
Hi, friends i have akarbonn a1+ duple, which i have rooted and installed chainfire 3d in it but when i clicked install c2ddriver or whatever it is in chainfire my phone rebooted and now it is not running just boot screen comes and do not runs, please help me guys i have also disabled usb debugging earlier keeping in mind this please help me!!!!!!!!!!
i am also facing this problem. Do you get some solution?
Where is everyone getting Chainfire from that doesn't say it's only for older versions of Android?? There are tons of threads here where people keep trying to install it on unsupported devices and bricking them and not knowing why.
http://www.mediafire.com/download/f...+a1plus+duple+flasher+and+file(Ramuwalia).rar
Thaks!
But here is a problem...phone is not detected by sp flash tool
winkle_sharma said:
Thaks!
But here is a problem...phone is not detected by sp flash tool
Click to expand...
Click to collapse
There's either an issue with the cord, the PC's USB ports, or most likely, is that the driver is not loading correctly or is the incorrect one. Open your Device Manager on the PC while you plug it in and see what it displays. If it comes up with a yellow warning sign next to it, you just have to load the drivers manually. I've never really messed around with a lot of MediaTek based devices, but think there are 2 separate drivers - one specifically for that mode.
You might be able to find some helpful hints on how to load these drivers from the first few posts on this thread:
http://forum.xda-developers.com/showthread.php?t=2180436
es0tericcha0s said:
There's either an issue with the cord, the PC's USB ports, or most likely, is that the driver is not loading correctly or is the incorrect one. Open your Device Manager on the PC while you plug it in and see what it displays. If it comes up with a yellow warning sign next to it, you just have to load the drivers manually. I've never really messed around with a lot of MediaTek based devices, but think there are 2 separate drivers - one specifically for that mode.
You might be able to find some helpful hints on how to load these drivers from the first few posts on this thread:
http://forum.xda-developers.com/showthread.php?t=2180436
Click to expand...
Click to collapse
thnx!! i will work on it