[Request] ADB Driver - Nokia 9 PureView Questions & Answers

Hey'll I want to mess around with my phone a bit, but seem to can't find a proper working ADB driver for it, anyone had success with it?
Running win10
/nevermind needed latest adb itself as well... epic failure...

Nokia 9 PureView Stock Firmware de getdroidtips.com
https://www.getdroidtips.com/nokia-9-pure-view-stock-firmware/

Related

[Q] Windows Phone 8.1 SDK, What does it mean?

I am trying to figure out what all of this means... Am I able to install this to my phone? If so how? If not, how are other people doing it?
SDK = software development kit = tools for building applications.
You can't install this to your phone, and neither can anyone else. At the moment, the emulator is all we got to play with.
Can somebody pass me a link to download the SDK 8.1 I don't find somewhere
https://developer.microsoft.com/en-us/windows/downloads/sdk-archive

Developer Unlock troubles

I have a Lumia 620 with Lumia Cyan + the latest developer preview update and I recently factory reset it. Today I tried developer unlocking it, and it came up with the "IpOverUsbSvc" error. I restarted my computer and got the same error, so I uninstalled and reinstalled the drivers and restarted, still same error. I uninstalled the lite 8.1 SDK (I'm on Windows 7), reinstalled it then rebooted, and still got the same error. Does anyone know how I can fix this?
edit: I searched already if you're just planning on saying that.
I seem to have the same issue on two other devices. Apparently you need files from the 8.1 Emulator Update 1 ISO. I have the Visual Studio 2013 with both Update 3 and the emulator update installed, but I too have the same error. Try running the 8.1 Power Tools update on your phone and see if it will actually give you an error code.
thals1992 said:
I seem to have the same issue on two other devices. Apparently you need files from the 8.1 Emulator Update 1 ISO. I have the Visual Studio 2013 with both Update 3 and the emulator update installed, but I too have the same error. Try running the 8.1 Power Tools update on your phone and see if it will actually give you an error code.
Click to expand...
Click to collapse
Thanks, probably had something to do with it being on update 1, but I managed to get it unlocked with that weird Chinese app mentioned in another thread.

MiPCSuite not connecting

I am using the MiPCSuite (ver. 3.2.1.3111) but it is unable to detect my Mi 5 (on both Global Stable and Global Beta). I read on the forums that this has been an issue since Marshmellow based MIUI has been released and that there is still no fix.
My bootloader is still locked (even though permission has been granted a week ago) so I can only use official ROMs.
My question is are there any alternative, such as a modded version of the suite?
I would like to know too as i can't even get my PC W10 to recognise my Xiaomi so can't put music on it.
Have to use a Mac it's the only way to get stuff on the phone.
silverblack said:
I would like to know too as i can't even get my PC W10 to recognise my Xiaomi so can't put music on it.
Have to use a Mac it's the only way to get stuff on the phone.
Click to expand...
Click to collapse
For some reason MTP only works properly from my USB 3.0 ports, but I'd still like the functionality to sync and manage my stuff. Xiaomi has some kind of bug that doesn't allow you to access most parts of the storage, or the phone just disconnects randomly after a few seconds if you try to copy something.

Sony XZ1 Compact Driver Fastboot

Hi everyone,
I would like to root my device but i need the drivers, i search and install what i find on the web and sony website but every time when my divice is in fastboot mode it not recognize by windows.
I think this thread can be usefull for many persons so i open it.
Mobile : Sony XZ1 Compact
This is a screenshot of my device when i plug it in fastboot mode :
{
"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"
}
Thanks you :good:
Braindeadz said:
Hi everyone,
I would like to root my device but i need the drivers, i search and install what i find on the web and sony website but every time when my divice is in fastboot mode it not recognize by windows.
I think this thread can be usefull for many persons so i open it.
Mobile : Sony XZ1 Compact
This is a screenshot of my device when i plug it in fastboot mode :
Thanks you :good:
Click to expand...
Click to collapse
If you're stuggling to find the ADB drivers for your phone, I'm not sure that you should be trying to root your phone, no offence.
Rooting it will break the camera completely. There is a DRM fix, which does leave all the functions of the camera working. But I wouldn't go down that route personally. The 'fix' was actually stolen from another developer and released without permission. The Dev who's running the drm fix thread didn't build the fix and has no idea how it works. Read for yourself, support is very patchy, it's a difficult thing to get right. You need to apply the right patches in the right sequence on top of a 8.49 CE firmware build, or it wont work.
It's a fix not a workaround, you destroy your TA keys buy unlocking your phone and you will never get them back.
Also you're dependent on the Dev (sToRm//) compiling a new fix to go with any new firmware released.
You could never update again without his help, and right now, he's got the hump.
Didgesteve said:
If you're stuggling to find the ADB drivers for your phone, I'm not sure that you should be trying to root your phone, no offence.
Rooting it will break the camera completely. There is a DRM fix, which does leave all the functions of the camera working. But I wouldn't go down that route personally. The 'fix' was actually stolen from another developer and released without permission. The Dev who's running the drm fix thread didn't build the fix and has no idea how it works. Read for yourself, support is very patchy, it's a difficult thing to get right. You need to apply the right patches in the right sequence on top of a 8.49 CE firmware build, or it wont work.
It's a fix not a workaround, you destroy your TA keys buy unlocking your phone and you will never get them back.
Also you're dependent on the Dev (sToRm//) compiling a new fix to go with any new firmware released.
You could never update again without his help, and right now, he's got the hump.
Click to expand...
Click to collapse
Thanks you for you help, i think you are right but it's very difficult to tell me i don't "root" my phone because every smartphone i have in my life was root. I buy a Sony phone for the first time and maybe the last because it's what i like with Android, Root, change ROM, again and again. Maybe Modpunk release a stable LineageOS ?
I buy this phone because it is small, very small, snap 835, sd card, speakers on the front and fingerprint on the right but i hope Oneplus make a little phone like this a day
I feel like I'm in prison
Braindeadz said:
Thanks you for you help, i think you are right but it's very difficult to tell me i don't "root" my phone because every smartphone i have in my life was root. I buy a Sony phone for the first time and maybe the last because it's what i like with Android, Root, change ROM, again and again. Maybe Modpunk release a stable LineageOS ?
I buy this phone because it is small, very small, snap 835, sd card, speakers on the front and fingerprint on the right but i hope Oneplus make a little phone like this a day
I feel like I'm in prison
Click to expand...
Click to collapse
I know, every phone I've ever owned I rooted, it's almost a habit, but with this bootloader Sony is giving us the finger. The main reasons I wanted to root were usually to get a better battery and to mod the framework to make it look better, but the battery with this phone is already good, it doesn't need any help.
If you want to mod the looks then it's possible to do that too.
I don't want to be negative and put you off trying to do amazing things with your phone, but I thought you should know the details before you start.
Edit: yes, I think LineageOS is very close now, perhaps when that is working I might move to that.
Didgesteve said:
I know, every phone I've ever owned I rooted, it's almost a habit, but with this bootloader Sony is giving us the finger. The main reasons I wanted to root were usually to get a better battery and to mod the framework to make it look better, but the battery with this phone is already good, it doesn't need any help.
If you want to mod the looks then it's possible to do that too.
I don't want to be negative and put you off trying to do amazing things with your phone, but I thought you should know the details before you start.
Edit: yes, I think LineageOS is very close now, perhaps when that is working I might move to that.
Click to expand...
Click to collapse
Thanks for your tips, I'm waiting for LineageOs now, it seems like a better idea.
Thanks you Didgesteve
Braindeadz said:
Hi everyone,
I would like to root my device but i need the drivers, i search and install what i find on the web and sony website but every time when my divice is in fastboot mode it not recognize by windows.
I think this thread can be usefull for many persons so i open it.
Mobile : Sony XZ1 Compact
This is a screenshot of my device when i plug it in fastboot mode :
Thanks you :good:
Click to expand...
Click to collapse
I ran into a similar issue when trying to use Emma. It only runs on Windows, so I had to go through this as well.
First, download and install Android Studio for your OS:
developer . android .com/studio/ index. html
(Note: Android Studio is not required, just the SDK. But Android Studio will install the SDK for you in a standard location. This might make things easier for you.)
Once this is done, launch it to install the SDK. You can select all defaults.
Once the SDK is installed, click Configure in the bottom-right of Android Studio and select SDK Manager. On the first screen, select the SDK Tools tab in the middle. Here you will want to select Google USB Driver and click Apply. This should install the driver.
Then, go back to the device in the device manager and right-click the device and select Update Driver.
After that, I followed the steps here:
stackoverflow . com /questions/14559734/ install-adb-interface-driver-for-android
to get the driver installed. This was because I kept getting an error that the system could not find the Android ADB Interface.
For the record, the Google USB Driver was installed on a Windows 10 box in the following location:
%localappdata%\Android\Sdk\extras\google\usb_driver
Hope this helps you out..
crummmcakes said:
I ran into a similar issue when trying to use Emma. It only runs on Windows, so I had to go through this as well.
First, download and install Android Studio for your OS:
developer . android .com/studio/ index. html
(Note: Android Studio is not required, just the SDK. But Android Studio will install the SDK for you in a standard location. This might make things easier for you.)
Once this is done, launch it to install the SDK. You can select all defaults.
Once the SDK is installed, click Configure in the bottom-right of Android Studio and select SDK Manager. On the first screen, select the SDK Tools tab in the middle. Here you will want to select Google USB Driver and click Apply. This should install the driver.
Then, go back to the device in the device manager and right-click the device and select Update Driver.
After that, I followed the steps here:
stackoverflow . com /questions/14559734/ install-adb-interface-driver-for-android
to get the driver installed. This was because I kept getting an error that the system could not find the Android ADB Interface.
For the record, the Google USB Driver was installed on a Windows 10 box in the following location:
%localappdata%\Android\Sdk\extras\google\usb_driver
Hope this helps you out..
Click to expand...
Click to collapse
Unfortunately, these drivers do not contain the correct drivers. I do not have any idea, I've been desperate.
hage_JK said:
Unfortunately, these drivers do not contain the correct drivers. I do not have any idea, I've been desperate.
Click to expand...
Click to collapse
What do you mean by "these drivers do not contain the correct drivers"? Did they fail to install for you?
I just spun up a new Windows 7 VM to test this out again, and it worked for me.
What steps are you taking exactly?
Did you receive any errors when you tried to install the driver this way?
How is your device appearing in the device manager?
crummmcakes said:
What do you mean by "these drivers do not contain the correct drivers"? Did they fail to install for you?
I just spun up a new Windows 7 VM to test this out again, and it worked for me.
What steps are you taking exactly?
Did you receive any errors when you tried to install the driver this way?
How is your device appearing in the device manager?
Click to expand...
Click to collapse
The device in fastboot will appear in the device manager as Android as the first stick.
Drivers dowload from Sony developed or Android SDK reports not found driver.
Drivers from Sony or Google they work in USB debugging but not driver in fastboot, still reports Android without drivers.
Testing on Windows 10 x64 and Windows 7 x32
Thank you in advance for any ideas
Hi, is there a solution to this? I am also looking for the fastboot driver. I have no issue with ADB driver... its just fastboot. My Z5 with fastboot is ok.... but Z1C not. Im running windows 10
Dean F said:
Hi, is there a solution to this? I am also looking for the fastboot driver. I have no issue with ADB driver... its just fastboot. My Z5 with fastboot is ok.... but Z1C not. Im running windows 10
Click to expand...
Click to collapse
Sometimes the drivers don't install properly in Windows 10, although it doesn't tell you they failed to install (helpful). You need to start Windows in safe mode and look for 'Disable driver signing'
Also, if you've used your computer for another device, then it's likely those drivers are still in it kicking about and probably getting in the way. You might have better luck going to another computer that has never been used for ADB and starting fresh.
Hi everyone,
Dunno if this is the right thread to post my question but the subject is Fastboot so I am trying my luck. Want to unlock the bootloader of my phone via Sony website... step 1 and 2 are no problem and I have my unlock code. Unfortunately I can't get my phone into FASTBOOT mode. Connected cable to laptop, hold volume button up and connected phone to cable but nothing happens. Is there anyone that can help me out?
thnx!
van_vugt said:
Hi everyone,
Dunno if this is the right thread to post my question but the subject is Fastboot so I am trying my luck. Want to unlock the bootloader of my phone via Sony website... step 1 and 2 are no problem and I have my unlock code. Unfortunately I can't get my phone into FASTBOOT mode. Connected cable to laptop, hold volume button up and connected phone to cable but nothing happens. Is there anyone that can help me out?
thnx!
Click to expand...
Click to collapse
It's been mentioned before on a different thread.
Didgesteve said:
It's been mentioned before on a different thread.
Click to expand...
Click to collapse
Thnx... overlooked that thread. Will try that!
hage_JK said:
The device in fastboot will appear in the device manager as Android as the first stick.
Drivers dowload from Sony developed or Android SDK reports not found driver.
Drivers from Sony or Google they work in USB debugging but not driver in fastboot, still reports Android without drivers.
Testing on Windows 10 x64 and Windows 7 x32
Thank you in advance for any ideas
Click to expand...
Click to collapse
Did you use the standalone SDK, or did you use Android Studio?
If you used Android Studio, what do you see in: %localappdata%\Android\Sdk\extras\google\usb_driver\
If you did not use Android Studio, would you be willing to try it? I only suggest it since it installs everything to specific locations, so perhaps removing an additional variable could be useful.
Otherwise, Didgesteve's suggestion seems like a good next step.
I have the exact same problem. Sony driver and Google driver both don't work. Driver sign in Windows 10 is disabled. How can I don now?
Edit: After followed the steps showed in this video the drivers are successfully installed but when unlocking the bootloader it says "command not allowed". Do I have to unlock it if I want to root my phone?
k_basara said:
I have the exact same problem. Sony driver and Google driver both don't work. Driver sign in Windows 10 is disabled. How can I don now?
Edit: After followed the steps showed in this video the drivers are successfully installed but when unlocking the bootloader it says "command not allowed". Do I have to unlock it if I want to root my phone?
Click to expand...
Click to collapse
Yes, unlocking your phone is the first part of rooting your phone. Unlocking is a one way process, you can't ever undo it and it will break your camera, completely. Be aware of that before you continue, the threads are full of people crying about broken phones that can't be re-locked.
It might be your phone is not allowed to be unlocked. Some phone providers in the UK sell phones that cannot be unlocked, mostly because they don't want the headache of people claiming unlocked phones be repaired.
Type *#*#7378423#*#* into your phone dialer to access the service menu.
Then look under Service info/configuration.
Under Rooting Status it should say Bootlock unlock allowed - yes.
If it says no then forget it.
Edit: you also need to allow OEM unlocking in the developer options
Didgesteve said:
Yes, unlocking your phone is the first part of rooting your phone. Unlocking is a one way process, you can't ever undo it and it will break your camera, completely. Be aware of that before you continue, the threads are full of people crying about broken phones that can't be re-locked.
It might be your phone is not allowed to be unlocked. Some phone providers in the UK sell phones that cannot be unlocked, mostly because they don't want the headache of people claiming unlocked phones be repaired.
Type *#*#7378423#*#* into your phone dialer to access the service menu.
Then look under Service info/configuration.
Under Rooting Status it should say Bootlock unlock allowed - yes.
If it says no then forget it.
Edit: you also need to allow OEM unlocking in the developer options
Click to expand...
Click to collapse
Yes, I forgot to allow OEM unlock in my phone settings.
I gave up unlocking my phone anyway, compare to years ago, stock rom nowadays isn't that unacceptable after all.
Hi - after months I finally solved the fast boot issue by using the above mentioned video: https://www.youtube.com/watch?time_continue=105&v=nQjg6ePnGAc
Basically - the key is that there are 2 steps:
1. Connect phone in usb debugging mode - then install sony adb driver using device manager and "have disk"
2. Boot into fastboot - and again install sony adb driver using device manager and "have disk"
Result = fastboot now working!
today I root my XZ1C
I have lots of problems with fastboot and i have other solution
for ADB i use driver from Sony ( installed by device manager )
but for fastboot
I use "Android ADB Interface" installed with Android Studio (you can choose it device manager --> update driver --> manual install --> installed on pc --> google or on my PC it was Samsung and there was google --> Android ADB Interface )
thats was only think that work for my device
I lost today 3/4h for this one think
maybe it will help someone to safe this time
Enjoy !

ME375CL Sideload disabled?

New old stock asus never used kit kat 4.4.4 att_11.16.1.35
I load the normal adb drivers, but when in recovery the adb sideload function whacks out and the pc says usb/unknown-disabling that function.
All windows versions from xp on up to win10 say the same thing.
Using an old laptop with dual boot xp/mac osx 10.5.7 osx detects the usb as vid_18D1&pid_001 so the device needs an Onda V972? driver?
ADB v2.3
A moot point,since windows will never let you load a driver unless the proper vid&pid are detected.
Linux doesn't detect the correct vid and pid either.
I am going to try a more modern version of osx to see If I can attack it that way.
Probably why none of the 1 click rooting methods ever worked.
Mac OSX 10.10 detects the sideload vid/pid 18D1 /001 google.
There is an asus flash program from here I will play with later.
Since sideload is disabled,the asus flash tool was useless.
I had to update to lollipop 5.1.1 manually with fastboot.
Zip file was labeled 4.2.2 but they lied.
the sideload vid/pid is now
USB\VID_8087&PID_0A5D&REV_0232
which windows detects fine.
Since mean old AT&T won't carrier unlock the sim,the episode comes to an end.
Their excuse was hilarious,they said it wasn't an AT&T device.
They should have said never activated/used for x amount of time.
rooted lollipop with the ROOT_LP which the original poster said was from russia for another model but works for the ME375cl
Tracking that down it was also for
ME375CL, ME572C/CL, ME581C/CL, Z300CL, FE375CG/FE375CXG
searching the globe for FE375cg I noticed csc firmware
CSC_OPEN_ME375CL_V11.16.0.92.1.1-eng-20150324-rawdata.7z.
which looked interesting but 99% of the links were for google drive that was a dead end.
Day 2 used yahoo to search and finally found it.Funny how google search didn't detect.
Playing with that now trying to figure out what to click on.
I thought it was a generic me375cl divorced from att but still has att crumbs.
after the downgrade to 4.4.4 it was still rooted.
serial number shows 11111111111111111

Categories

Resources