I have a ICOO D70PROII tablet, with a Rockchip 3066. After installing the Chainfire 3D driver, the tablet stucks at ICOO boot screen, even before the Android animation. I've started the tablet in recovery mode (appears the Android guy with the open bonnet and a red exclamation point).
I have the ADB drivers installed, i can access to almost everything in the ADB tool, except the "adb shell" command, even pushing up the mksh file to /system/bin.
The fastboot doesn't work, because the tablet turns off the screen, but appears in Device Manager an unknown driver, that I can't find the driver for it.
The RKBatchTool 1.3 and 1.5 doesn't recognize the tablet.
The only way I can see to fix this is doing the job in ADB command line, but the only way that I know to uninstall the Chainfire 3D driver is in Shell. Could anyone help me in this problem?
I made a small and simple recording showing the driver, RKBatchTool error and ADB errors. (please copy the following link to the browser's URL bar, I can't post direct links)
youtube.com/watch?v=4iQi5SkKGe4
Best regards and thank you in advance,
Ivan Santos.
IvanSantosPT said:
I have a ICOO D70PROII tablet, with a Rockchip 3066. After installing the Chainfire 3D driver, the tablet stucks at ICOO boot screen, even before the Android animation. I've started the tablet in recovery mode (appears the Android guy with the open bonnet and a red exclamation point).
I have the ADB drivers installed, i can access to almost everything in the ADB tool, except the "adb shell" command, even pushing up the mksh file to /system/bin.
The fastboot doesn't work, because the tablet turns off the screen, but appears in Device Manager an unknown driver, that I can't find the driver for it.
The RKBatchTool 1.3 and 1.5 doesn't recognize the tablet.
The only way I can see to fix this is doing the job in ADB command line, but the only way that I know to uninstall the Chainfire 3D driver is in Shell. Could anyone help me in this problem?
I made a small and simple recording showing the driver, RKBatchTool error and ADB errors. (please copy the following link to the browser's URL bar, I can't post direct links)
youtube.com/watch?v=4iQi5SkKGe4
Best regards and thank you in advance,
Ivan Santos.
Click to expand...
Click to collapse
Did you make a backup B4 installing Chainfire?
ken.okech.94 said:
Did you make a backup B4 installing Chainfire?
Click to expand...
Click to collapse
I didn't. But even I've made a backup, I can't connect the tablet to the computer with RKBatchTool and I can't install the Rockchip 3066 driver, only the ADB Android driver (which i can connect via adb).
Use ADB
IvanSantosPT said:
I didn't. But even I've made a backup, I can't connect the tablet to the computer with RKBatchTool and I can't install the Rockchip 3066 driver, only the ADB Android driver (which i can connect via adb).
Click to expand...
Click to collapse
Google a pre-made adb backup specifically for your tablet and restore it via adb. Or you can just use fastboot to flash a new ROM.
ken.okech.94 said:
Google a pre-made adb backup specifically for your tablet and restore it via adb. Or you can just use fastboot to flash a new ROM.
Click to expand...
Click to collapse
Did you read what I said?
I have the ADB drivers installed, i can access to almost everything in the ADB tool, except the "adb shell" command, even pushing up the mksh file to /system/bin.
The fastboot doesn't work, because the tablet turns off the screen, but appears in Device Manager an unknown driver, that I can't find the driver for it.
The RKBatchTool 1.3 and 1.5 doesn't recognize the tablet.
Click to expand...
Click to collapse
IvanSantosPT said:
Did you read what I said?
Click to expand...
Click to collapse
I think adb shell doesnt work because your tablet has not yet booted and will not be booted as long as it is in the current state.
Your only hope is RK Batch tool. Uninstall all current versions and the drivers you have in your computer and try reinstalling this and the drivers.
https://mega.co.nz/#!TIFwFCob!YniP23RpZH6hRj1Q-WSYvgQ4v28FUjU2qJ8b_4xLJXg
Your only hope!
ken.okech.94 said:
I think adb shell doesnt work because your tablet has not yet booted and will not be booted as long as it is in the current state.
Your only hope is RK Batch tool. Uninstall all current versions and the drivers you have in your computer and try reinstalling this and the drivers.
mega.co.nz/#!TIFwFCob!YniP23RpZH6hRj1Q-WSYvgQ4v28FUjU2qJ8b_4xLJXg
Your only hope!
Click to expand...
Click to collapse
Thank you, I reinstalled the driver and it worked. I installed the CWM 6.0.2.7 and all was working fine. Then I installed the CyanogenMod for RK3066 (cm3066.com) and the device doesn't boot, doesn't even shows the battery charger indicator and I can't mount or format anything in the CWM. I've lose the SD card, but I will borrow someone and try to reinstall the CWM, because I can't go to the RKBatchTool option.
Y u so Ungrateful?
IvanSantosPT said:
Thank you, I reinstalled the driver and it worked. I installed the CWM 6.0.2.7 and all was working fine. Then I installed the CyanogenMod for RK3066 (cm3066.com) and the device doesn't boot, doesn't even shows the battery charger indicator and I can't mount or format anything in the CWM. I've lose the SD card, but I will borrow someone and try to reinstall the CWM, because I can't go to the RKBatchTool option.
Click to expand...
Click to collapse
<<<<<<<<<<<<<<<<<<<<Hit thanks button if I helped , dude.
ken.okech.94 said:
<<<<<<<<<<<<<<<<<<<<Hit thanks button if I helped , dude.
Click to expand...
Click to collapse
No problema. But now I can't even reflash the CWM or the ROM, the tablet is soft bricked.
UPDATE: To access to the Downloading Mode, I had to click Vol+ plus Vol- when I connect the device to USB port. I am trying to flash with official firmware.
UPDATE 2: I've noticed that the ROM that I installed damaged the kernel, and now I need someone's boot partition dump.
UPDATE 3: I downloaded the oficial ROM from soft.aoicoo.com/soft/show.asp?id=285 and flashed the device. Then the device started! I installed the CWM 6.0.2.7 and then installed DarkwaterV2 CM ROM (not required). The tablet is working better than never with 10279 points scored in AnTuTu Benchmark v3.3! Thank you all!
today i reflashed my phone with stock 4.0.4 french ftf and it is working fine with usb debugging off but with debugging on, my computer doesnt see the phone! what should i do?
i have reflashed it but still usb debugging mode is not working! help! please what can the problem be?
plz help !
im stuck on stock! no root! nothing good!
First: Don't Panic.
Second: Check your drivers. If not properly installed, try one from sony (just google your device together with "adb driver").
Third: after a complete flash it's like you've never touched your device, means you have to re-root your device normally.
i hope this helps.
murderered said:
First: Don't Panic.
Second: Check your drivers. If not properly installed, try one from sony (just google your device together with "adb driver").
Third: after a complete flash it's like you've never touched your device, means you have to re-root your device normally.
i hope this helps.
Click to expand...
Click to collapse
no its not working!
ive installed a new windows on virtualbox but there also no usb debugging is working!
and how do you install the adb drivers in the zip?
even though it is in debugging mode..when i try to root, it says please connect your phone in debugging mode
Can't say if it generally works with virtualbox. try to get drivers for your native system.
So the question is now: What's your host system?
If it's Windows, get Flashtool and install included driver (found in <FlashtoolInstallDir>\driver) just for rooting the device.
If you're using linux you can look if your device was recognized properly with lsusb it should be listed there.
You can try it too in virtualbox, but i don't trust the USB-driver (i would not flash or so through it) and do not recommend it.
murderered said:
Can't say if it generally works with virtualbox. try to get drivers for your native system.
So the question is now: What's your host system?
If it's Windows, get Flashtool and install included driver (found in <FlashtoolInstallDir>\driver) just for rooting the device.
If you're using linux you can look if your device was recognized properly with lsusb it should be listed there.
You can try it too in virtualbox, but i don't trust the USB-driver (i would not flash or so through it) and do not recommend it.
Click to expand...
Click to collapse
i am using windows 7 32 bit
ive already have flashtool and have tried to install the drivers but nothing works!
Ok, you've installed (i assume) the right adb drivers for your device through the installer located in <FlashtoolsInstallDir>\driver.
So is there any Android/Sony (Ericsson) named device in your device manager? What does Flashtools write if you connect? If your device is listed in device manager, does it show an error, if yes which error?
murderered said:
Ok, you've installed (i assume) the right adb drivers for your device through the installer located in <FlashtoolsInstallDir>\driver.
So is there any Android/Sony (Ericsson) named device in your device manager? What does Flashtools write if you connect? If your device is listed in device manager, does it show an error, if yes which error?
Click to expand...
Click to collapse
in flashtool it shows the same thing in on and off
the 2nd one is debugging on and 3rd with off
Please post output of "adb devices" (if not recognizing, try again after "adb usb"). If no serial number/device is shown then do following:
There is a newer version of Flashtool available, update to 0.9.11, http://androxyde.github.io/
check after reinstallation (of drivers, too)
Maybe you have to try sonys driver from the zip. So extract them (all files).
right click at your device in the device manager
click to "update driversoftware" (or something like that, i don't have english windows)
click "search on my computer for new drivers"
choose from list
display all devices
click the button below the list (i have no idea what there could be written, it's not "windows update")
search for the inf-file extracted and choose the "sa<somenumbers>adb.inf"
if not already installing, choose "Sony Ericsson saXXXX ADB Interface Driver"
reboot (pc)
check again
I recently acquired an SGP312 from ebay and the seller upgraded it to 5.0.2 without anyone asking for it (it was supposed to be NIB now who knows).
I have not unlocked the bootloader but I did confirm it is locked and can be unlocked.
I'm trying to connect it to my PC so I can get it rooted but I'm running into issues with the device being recognized.
I installed the Android SDK USB drivers & copied over android_winusb.inf and fastboot appears to be working fine. Windowns (7) Device Manager, Flashtool, and the Sony flash tool (Emma) all see the tab.
However, none of the other connection modes appear to work.
Flash mode will initially connect with Flashtool but the the device disconnects:
31/037/2015 23:37:03 - INFO - Device connected in flash mode
31/038/2015 23:38:04 - INFO - Device disconnected
31/038/2015 23:38:21 - ERROR - Drivers need to be installed for connected device.
31/038/2015 23:38:21 - ERROR - You can find them in the drivers folder of Flashtool.
Device Manager shows an Other Devices with SGP312. I tried doing the Update Driver Software option with the drivers from the Sony developer site or the Android SDK drivers but no go.
I then boot up normally and connect either with or without ADB turned on and get the same Device Manager and driver results and PC Companion won't see the phone, either.
kadiir said:
31/038/2015 23:38:21 - ERROR - Drivers need to be installed for connected device.
31/038/2015 23:38:21 - ERROR - You can find them in the drivers folder of Flashtool.
Click to expand...
Click to collapse
Download this package of drivers and install properly (Tick Flashmode, Fastboot, Common Drivers Lagan, Xperia Tablet Z drivers).
Sorry, I forgot to mention I ran the flash tool driver utility in the flashtool\drivers directory and chose the first 2 options and the XTZ-specific option but I'll give that a shot and report back.
While I did see a driver I missed I have little change in results other than MTP in non-USB debugging mode attempted to install a driver and failed:
Windows encountered a problem installing the driver software for your device
Windows found driver software for your device but encountered an error while attempting to install it.
MTP USB Device
The system cannot find the file specified.
That reminds me that when I try to manually install the driver while in usb debugging mode it has the same message but with USB Composite Device where it says MTP USB Device.
I think I'll try this on my laptop as this PC had issues earlier this year with corruption that I thought I had fixed and I'm wondering if the corruption was more widespread than I thought.
kadiir said:
I think I'll try this on my laptop as this PC had issues earlier this year with corruption that I thought I had fixed and I'm wondering if the corruption was more widespread than I thought.
Click to expand...
Click to collapse
Seems to be this is an issue, because flashtool driver packages installed fine for me on WinXP/7/8.
Also pc-companion usually installs everything that is necessary for its fuctional, so must be OS problem.
Yep, that was it. Man, I should've checked that first. Sorry for the waste of time.
Quick question - do you know which ADB Interface I install from the SDK drivers? Is it ADB Interface or ADB Composite Interface? Or do I do 2 passes and install both?
Never mind - did some googling and got my answer. Thanks!
My end goal is stock lolipop rooted.
I botched a flash and now I cant get developer mode / ADB working.
When I started, my tablet was stock ROM, towelroot. I connect tablet in developer mode, flashed dual recovery and everything was great. I copied the pre-rooted lolipop ROM to my SD card and flashed it. HOWEVER instead of turning off the device, I selected reboot from recovery. This resulted in boot loop.
SOOOO, I figured no worries, just flash old ROM and try again. So did this:installed Androxyde Flashtool
opened XperiFirm
downloaded 1276-8392 and 1274-8801 (I've tried the rest using both ROMs btw)
Tools>Bundler>Create>Selected folder>selected SGP312 for device
For branding I entered the above ie 1276-8392
For version I entered the ver ie 10.5.A.230
Flashmode>checked boxes to wipe everything
The flash goes through without a hitch. Under about tablet, I see
Model : SGP312
Android Ver : 4.4.2
Kernel : 3.4.0-perf-g32ce454, [email protected]#1
Build Number : 10.5.A.0.230
I activate USB debugging and unknown sources, connect to USB and Flashtool returns: Device connected with USB debugging turned off
I went into device manager and found the MTP driver. Also of note, the device ID is: USB\VID_0FCE&PID_5194&REV_0228
I downloaded Sony's ADB drivers, tried to manually update device driver and windows7x64 kicked back driver is not for your device.
I edited the INF to include the hardware ID exactly as it appears in device manager and tried again. This time windows let me load the driver. It shows up in device manager as 'Sony sa0107 ADB Interface Driver'
HOWEVER, Flashtool is still giving me the same MTP message and if I cmd prompt "adb devices" I get nada.
Is there a way to verify developer mode on the tablet? What else can I try? The tablet gives me a notification when I connect 'usb debugging mode connected, ready to install software'
Thanks!
_sadpanda said:
I went into device manager and found the MTP driver. Also of note, the device ID is: USB\VID_0FCE&PID_5194&REV_0228
HOWEVER, Flashtool is still giving me the same MTP message and if I cmd prompt "adb devices" I get nada.
Thanks!
Click to expand...
Click to collapse
I had a very similar problem in 2014. I do not want to discourage you, but at the end I send it back to sony for a repair. They gave me a new tablet and said that the mainboard was broken.
Nevertheless, there is a thread in Sony cross device general, where people like you end up: http://forum.xda-developers.com/showthread.php?t=1849170
You can try and search for help there, maybe you have more luck then me.
Its odd... ADB was working and stopped after flash. Is this what you had or just no connection from the start?
Sorry, I misread your post. I thought your tablet would not start and you could not get flashmode working. Sorry for that.
What you could try:
1. Be sure you actually activated USB debugging in developer options
2. When you connect the device, you should get a prompt on the tablet to allow usb debugging from that computer
Maybe try "revoke USB debugging authorisations" in developer options and reconnect
3. Install the drivers from flashtool/drivers/ or install sony pc companion. Delete your old driver from device manager.
4. try switching between MTP and MSC mode in usb connectivity menu
Since ADB worked before it was probably no driver problem. Now you cannot be sure. Most probably you tapped away the said prompt of allowing usb debugging when connecting.
If none of this helps I don't know of anything more. Maybe try different usb ports or even computers.... Or try to flash again
bernddi said:
4. try switching between MTP and MSC mode in usb connectivity menu
Click to expand...
Click to collapse
UGH!!! I'm a jacka$$. I totally forgot about that menu/setting. fixed instantly.
Once you got into android modding, an unrooted phone becomes almost useless.
Now my problem is that I´ve got one.
Couple of days ago my Elephone P9000 arrived from amazon but I can´t connect it to a PC since it says that no device is detected.
Yes, the drivers are installed properly!
I thought that isn´t a problem because there is Kingroot.
Turns out the following rooting apps don´t work for me:
Kingroot (Kingoroot), iRoot, z4root, Framaroot, Towelroot, Oneclickroot, Universal Androot, Root Genius, Baidu
Custom Recovery isn´t installed because, of course, no root.
Now how do I root?
ThisIsMyMaster said:
Once you got into android modding, an unrooted phone becomes almost useless.
Now my problem is that I´ve got one.
Couple of days ago my Elephone P9000 arrived from amazon but I can´t connect it to a PC since it says that no device is detected.
Yes, the drivers are installed properly!
I thought that isn´t a problem because there is Kingroot.
Turns out the following rooting apps don´t work for me:
Kingroot (Kingoroot), iRoot, z4root, Framaroot, Towelroot, Oneclickroot.
Custom Recovery isn´t installed because, of course, no root.
Now how do I root?
Click to expand...
Click to collapse
The first thing you need to accomplish is to get your PC to recognize your phone, rooting from there is going to make life easier, but yes, I know you already know that. If your using windows 10, maybe check this thread out on Elephone Forum:
http://bbs.elephone.hk/forum.php?mod=viewthread&tid=12240&page=1&ordertype=1#pid129322
jotei66 said:
The first thing you need to accomplish is to get your PC to recognize your phone, rooting from there is going to make life easier, but yes, I know you already know that. If your using windows 10, maybe check this thread out on Elephone Forum:
(link removed)]
Click to expand...
Click to collapse
That´s the tutorial that I was going to do but when my phone is shut down, my pc doesn´t detect the device and flash tool neither.:crying:
ThisIsMyMaster said:
That´s the tutorial that I was going to do but when my phone is shut down, my pc doesn´t detect the device and flash tool neither.:crying:
Click to expand...
Click to collapse
Firstly is your PC finding your phone ok with the PC on? If yes.. all good - if no you need to sort this out first.
Then, ensure you have installed the MTK driver on your PC (these are the Media Tek drivers which will find your phone when it is off) instructions here:
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
Then flashtools should work fine with your phone off.
Just a tip using FlashTools (Im on windows 10 - I dont know if this applies to other windows)
In flashtools, press download first (without phone connected), give it 5 secs and then connect your phone to your PC with the volume up button pressed at the same time. Once you see FlashTools starting to flash your phone, release the volume button. I have to do this all the time in order for my phone to be found on Windows 10.
jotei66 said:
Firstly is your PC finding your phone ok with the PC on? If yes.. all good - if no you need to sort this out first.
Then, ensure you have installed the MTK driver on your PC (these are the Media Tek drivers which will find your phone when it is off) instructions here:
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
Then flashtools should work fine with your phone off.
Just a tip using FlashTools (Im on windows 10 - I dont know if this applies to other windows)
In flashtools, press download first (without phone connected), give it 5 secs and then connect your phone to your PC with the volume up button pressed at the same time. Once you see FlashTools starting to flash your phone, release the volume button. I have to do this all the time in order for my phone to be found on Windows 10.
Click to expand...
Click to collapse
To start of, I am using Windows 10 as you do.
When I connect my phone when it´s turned on, I get the small icon in the taskbar that allows me to remove the device safely or open devices and printer.
There, my device is put to a section called not specified and it has a small yellow icon.
Only is it called "P9000" which is alright.
Windows explorer acts like no device is connected at all.
When I connect my phone as it is turned off, I still get the notification "USB Device wasn´t recognized." and
windows explorer still doesn´t care as well as the flash tool.
The link you gave me isn´t the one I previously used to install the drivers so I gave it a try.
There are two different ways mentioned in the posts #1 and #4 so I started with the first one.
(Spoiler: Both don´t work for me!)
Everything worked until a step almost at the end where I am told to connect my off-switched phone to the pc.
The tutorial tells me that there should now be a preloader unknown device or something at Device Manager > Ports (COM & LPT) that I would need to proceed further.
I didn´t get that one.
Dead end for me so I went on to the next tutorial in post #4.
In that post I am told to remove a MTK USB Port at Device Manager > Ports (COM & LPT) right after installing the .inf driver files (Yes, I installed the 64 bit version and do have a 64 bit PC).
Ignoring that step didn´t help any of the problems I had before so I got a dead end here, too.
The "Volume-Up-Trick" did help me neither, probably cause of the not working drivers.
ThisIsMyMaster said:
To start of, I am using Windows 10 as you do.
When I connect my phone when it´s turned on, I get the small icon in the taskbar that allows me to remove the device safely or open devices and printer.
There, my device is put to a section called not specified and it has a small yellow icon.
Only is it called "P9000" which is alright.
Windows explorer acts like no device is connected at all.
When I connect my phone as it is turned off, I still get the notification "USB Device wasn´t recognized." and
windows explorer still doesn´t care as well as the flash tool.
The link you gave me isn´t the one I previously used to install the drivers so I gave it a try.
There are two different ways mentioned in the posts #1 and #4 so I started with the first one.
(Spoiler: Both don´t work for me!)
Everything worked until a step almost at the end where I am told to connect my off-switched phone to the pc.
The tutorial tells me that there should now be a preloader unknown device or something at Device Manager > Ports (COM & LPT) that I would need to proceed further.
I didn´t get that one.
Dead end for me so I went on to the next tutorial in post #4.
In that post I am told to remove a MTK USB Port at Device Manager > Ports (COM & LPT) right after installing the .inf driver files (Yes, I installed the 64 bit version and do have a 64 bit PC).
Ignoring that step didn´t help any of the problems I had before so I got a dead end here, too.
The "Volume-Up-Trick" did help me neither, probably cause of the not working drivers.
Click to expand...
Click to collapse
Ok first things first, lets make sure your P9000 is fine with your phone on. You said:
When I connect my phone when it´s turned on, I get the small icon in the taskbar that allows me to remove the device safely or open devices and printer. There, my device is put to a section called not specified and it has a small yellow icon.
Only is it called "P9000" which is alright.
Click to expand...
Click to collapse
(make sure in dev options on your phone USB debugging is ON and USB config is MTP)
So from that you simply need to (In Device Manager) right click > Update Driver Software > Browse My PC for Driver Software > Let me pick from a list of device drivers from my PC > then choose MTP USB Device
Once windows installs this, a box should pop up showing your P9000 internal storage and SD Card (if you have one in phone)
To ensure that your PC is now finding your phone ok, restart PC and plug your phone in - you should be prompted by windows to choose a default action when this device is connected (I choose transfer files or something similar). Then everytime you connect your phone, a box will pop up showing allowing you to access your P9000.
Now onto when your P9000 is switched off... (the important part for flashing etc)
I followed the instructions at post #4 as I believe due to the anniversary update on windows 10 (the January update I believe) .. if you do not have the January update installed on your PC you would use the instructions #1
Don't worry too much if you receive "USB device not recognised" initially, (from what I have understood this is normal with the Anniversary addition of windows 10) it should disappear after few seconds or so. From what I worked out following post #4 you are kinda installing a MTK device (just so you can install the drivers) and then uninstalling that device BUT keeping the drivers installed (its VERY important when you uninstall the device you untick the delete drivers too, otherwise you have essentially deleted the MTK drivers & would have to start from scratch from post #4)
For me, when I connect my p9000 when its off it still shows "USB device not recognised", then after a few seconds this goes away and I dont have any errors under Device Manager > Ports (COM & LPT) & flashtools works fine as long as I press vol up as I connect my phone.
Hope this helps, I had a headache when I tried to install MTK drivers with my windows 10 (Anniversay Update Edition) - good luck, it was kinda trial and error
jotei66 said:
Ok first things first, lets make sure your P9000 is fine with your phone on. You said:
(make sure in dev options on your phone USB debugging is ON and USB config is MTP)
So from that you simply need to (In Device Manager) right click > Update Driver Software > Browse My PC for Driver Software > Let me pick from a list of device drivers from my PC > then choose MTP USB Device
Once windows installs this, a box should pop up showing your P9000 internal storage and SD Card (if you have one in phone)
To ensure that your PC is now finding your phone ok, restart PC and plug your phone in - you should be prompted by windows to choose a default action when this device is connected (I choose transfer files or something similar). Then everytime you connect your phone, a box will pop up showing allowing you to access your P9000.
Now onto when your P9000 is switched off... (the important part for flashing etc)
I followed the instructions at post #4 as I believe due to the anniversary update on windows 10 (the January update I believe) .. if you do not have the January update installed on your PC you would use the instructions #1
Don't worry too much if you receive "USB device not recognised" initially, (from what I have understood this is normal with the Anniversary addition of windows 10) it should disappear after few seconds or so. From what I worked out following post #4 you are kinda installing a MTK device (just so you can install the drivers) and then uninstalling that device BUT keeping the drivers installed (its VERY important when you uninstall the device you untick the delete drivers too, otherwise you have essentially deleted the MTK drivers & would have to start from scratch from post #4)
For me, when I connect my p9000 when its off it still shows "USB device not recognised", then after a few seconds this goes away and I dont have any errors under Device Manager > Ports (COM & LPT) & flashtools works fine as long as I press vol up as I connect my phone.
Hope this helps, I had a headache when I tried to install MTK drivers with my windows 10 (Anniversay Update Edition) - good luck, it was kinda trial and error
Click to expand...
Click to collapse
I am running the Anniversay Update Edition and don´t get an popup window when connecting my phone turned on.
As far is I can tell, a working connection with the device running is more important in the first place.
Now I don´t quite understand your instructions at this point:
jotei66 said:
So from that you simply need to (In Device Manager) right click > Update Driver Software > Browse My PC for Driver Software > Let me pick from a list of device drivers from my PC > then choose MTP USB Device
Click to expand...
Click to collapse
In Device Manager right click, but where?
Blank space? Definetly not.
According to the linked tutorial, I´d have to right click on something like "unknown device" or something similar.
But that doesn´t show up in my list.
In the next section you said:
jotei66 said:
you are kinda installing a MTK device (just so you can install the drivers) and then uninstalling that device BUT keeping the drivers installed
Click to expand...
Click to collapse
I can understand the point but after installing that driver package, there is no MTK device in my device manager that I could uninstall.
I seriously need to thank you for wasting so much time on me:angel:
When you plug your p9000 (while its turned on) into your laptop/pc... in Device Manager, probably under Universal serial Bus Controllers do you see a unknown device, or anything with a question mark / unknown device beside it ? If so, that's where you right click and follow instructions above to get your PC to recognize your handset. At this point just concentrate on getting pc to recognise while its on, then hopefully we can then move to setting up when its off.
I seriously need to thank you for wasting so much time on me
Click to expand...
Click to collapse
lol its all cool
PS: Just to make sure, in device manager, press View from top menu and "show hidden devices".. maybe it could be hidden?
jotei66 said:
When you plug your p9000 (while its turned on) into your laptop/pc... in Device Manager, probably under Universal serial Bus Controllers do you see a unknown device, or anything with a question mark / unknown device beside it ? If so, that's where you right click and follow instructions above to get your PC to recognize your handset. At this point just concentrate on getting pc to recognise while its on, then hopefully we can then move to setting up when its off.
lol its all cool
PS: Just to make sure, in device manager, press View from top menu and "show hidden devices".. maybe it could be hidden?
Click to expand...
Click to collapse
I can´t believe how stupid I am...
jotei66 said:
Just to make sure, in device manager, press View from top menu and "show hidden devices".. maybe it could be hidden?
Click to expand...
Click to collapse
Well, that solved all of my problems...
Almost...
Drivers are fully working for me now so I wanted to flash TWRP with SP Flash Tool to be able to flash the superuser .zip file.
Since drivers work now, flash tool started flashing and gave me the error you can see in the attached screenshot.
Fortunately, my phone isn´t bricked or anything.
Edit: After a couple of reboots of all my devices, I get back to where I was before: USB Device wasn´t recognized and Flash Tool doesn´t do anything.
ThisIsMyMaster said:
I can´t believe how stupid I am...
Well, that solved all of my problems...
Almost...
Drivers are fully working for me now so I wanted to flash TWRP with SP Flash Tool to be able to flash the superuser .zip file.
Since drivers work now, flash tool started flashing and gave me the error you can see in the attached screenshot.
Fortunately, my phone isn´t bricked or anything.
Click to expand...
Click to collapse
All cool & its an easy thing to miss when your not looking for it (or for that matter if you dont know that menu even existed)
That error is a preloading error, I'm assuming your flashing TWRP Recovery and like you I had similar issue - I shared a simple solution here that worked for me here (it should work fine as long as you are on Stock Elephone 2016810 Base onwards so I believe, Elephone changed the preloader or something like that in later ROMS)
So Basically, you download the Stock Elephone 2016810 Base ROM from HERE & unzip
Grab Flash Tools ver v5.1612 (if your not using that version) HERE - https://www.androidfilehost.com/?fid=24591000424940027
Then download TWRP_3.0.2.8.zip HERE & unzip
Copy the the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_2016810 Rom folder.
In Splash Tools, first flash the Elephone_P9000_2016810 Rom open "MT6755_Android_scatter" from _810 file & ensure the recovery section location points to "recovery.img" in the _810 folder also
Once your stock _810 ROM is flashed successfully, you then flash TWRP (with only recovery ticked) and ensure the recovery location points to "recovery_TWRP_3028_P9000" and your TWRP should flash fine. Make sure your using Flash Tools ver v5.1612, that worked fine for me.
There maybe an easier solution someone can point you too, but I know this worked for me no problems - you should now have TWRP recovery on stock _810 ready for you to flash your chosen ROM
jotei66 said:
All cool & its an easy thing to miss when your not looking for it (or for that matter if you dont know that menu even existed)
That error is a preloading error, I'm assuming your flashing TWRP Recovery and like you I had similar issue - I shared a simple solution here that worked for me here (it should work fine as long as you are on Stock Elephone 2016810 Base onwards so I believe, Elephone changed the preloader or something like that in later ROMS)
So Basically, you download the Stock Elephone 2016810 Base ROM from HERE & unzip
Grab Flash Tools ver v5.1612 (if your not using that version) HERE - https://www.androidfilehost.com/?fid=24591000424940027
Then download TWRP_3.0.2.8.zip HERE & unzip
Copy the the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_2016810 Rom folder.
In Splash Tools, first flash the Elephone_P9000_2016810 Rom open "MT6755_Android_scatter" from _810 file & ensure the recovery section location points to "recovery.img" in the _810 folder also
Once your stock _810 ROM is flashed successfully, you then flash TWRP (with only recovery ticked) and ensure the recovery location points to "recovery_TWRP_3028_P9000" and your TWRP should flash fine. Make sure your using Flash Tools ver v5.1612, that worked fine for me.
There maybe an easier solution someone can point you too, but I know this worked for me no problems - you should now have TWRP recovery on stock _810 ready for you to flash your chosen ROM
Click to expand...
Click to collapse
I´m going to try this now.
Do I have to go back to Stock 20160810 if I have 20161107?
Do I have to go back to Stock 20160810 if I have 20161107?
Click to expand...
Click to collapse
I guess if you download the 20161107 ROM it should work, I'm really unsure, its a newer ROM so I guess it should
jotei66 said:
I guess if you download the 20161107 ROM it should work, I'm really unsure, its a newer ROM so I guess it should
Click to expand...
Click to collapse
It didn´t work.
I did all the steps you´ve told me and ended up with the exact same problem I´ve experienced before: USB Device not recognized and SP Flash Tool doesn´t do anything after pressing the download button.
I was going to reinstall the drivers like you told me form post #4 here: https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
That didn´t do anything, I still have the same problem of my pc not recognizing my phone.
At least connecting my phone when it´s running works now.
you have to press and keep vol + when connecting the turned off phone to the computer after clicking download in FlashTools.
Regards
Fran Montero said:
you have to press and keep vol + when connecting the turned off phone to the computer after clicking download in FlashTools.
Regards
Click to expand...
Click to collapse
Tried it, didn´t help
ThisIsMyMaster said:
Tried it, didn´t help
Click to expand...
Click to collapse
MMmmm .. have you tried a different USB port? maybe a different lead if you have one? (I have two leads and I know one doesnt work for me, dunno why)
Also, after pressing download in SplashTools.. count to say 7-10 secs and then press Vol UP and connect your phone.... (I know this sounds bit stupid, but it works for me, if I connect straioght away I get errors too ref driver )
jotei66 said:
MMmmm .. have you tried a different USB port? maybe a different lead if you have one? (I have two leads and I know one doesnt work for me, dunno why)
Also, after pressing download in SplashTools.. count to say 7-10 secs and then press Vol UP and connect your phone.... (I know this sounds bit stupid, but it works for me, if I connect straioght away I get errors too ref driver )
Click to expand...
Click to collapse
No, that doesn´t help either.
I think it has to do something with installing the drivers cause after installing them, in Device Manager no new drivers are displayed except for two Mediatek Preloader USB VCOM Port (COM5) and (COM6).
But those only become visible when I check "show hidden devices".
The tutorial said that some more things should have been installed but I didn´t get any error messages so I don´t understand what shouldn´t have worked.
Sorry Im at a loss really, maybe follow this tutorial my brother followed to reinstall the MTK and try again with all the above steps, good luck
https://www.youtube.com/watch?v=NbJCbdfPlF8
Make sure your PC is in driver signature disable mode when flashing etc btw
jotei66 said:
Sorry Im at a loss really, maybe follow this tutorial my brother followed to reinstall the MTK and try again with all the above steps, good luck
https://www.youtube.com/watch?v=NbJCbdfPlF8
Make sure your PC is in driver signature disable mode when flashing etc btw
Click to expand...
Click to collapse
Didn´t help either.
Current state:
Phone On > Everything working, I get the popup window and data transfer works :good:
Phone Off > USB wasn´t recognized, Flash Tool isn´t working, no recognition in windows explorer, phone is charging, vol+ doesn´t help
MTP and USB Debugging are activated
While installing the drivers I got no error messages and everything looked same as in the tutorial
ThisIsMyMaster said:
Didn´t help either.
Current state:
Phone On > Everything working, I get the popup window and data transfer works :good:
Phone Off > USB wasn´t recognized, Flash Tool isn´t working, no recognition in windows explorer, phone is charging, vol+ doesn´t help
MTP and USB Debugging are activated
While installing the drivers I got no error messages and everything looked same as in the tutorial
Click to expand...
Click to collapse
Good to hear you can atleast use your phone to transfer etc while on
Just curious (although Im sure you have followed the video / other tutorials to the letter) but
(1) did you ensure when following video tut that when uninstalling the legacy device you unticked the driver box to ensure the drivers were actually kept installed?
(2) Check Device Manager, under the Ports (COM & LPT) section and remember you shouldn't have anything referring to a MTK device in there - ie like MTK USB Port (Com 3) ? (If you have it needs uninstalling)
(3) Seems obvious I know but you are connecting your phone and using FlashTools when your Windows Driver Enforcement is disabled? ( Literally restarting with advanced options & choosng Disbale Driver Enforcement) Many users think once you have installed the driver you can use it with Windows Drivers enforcement enabled, but you have to be in disabled mode.
Finally if you doubled checked all of those, then maybe try a different version of FlashTools (worth a try) and also try running FlashTools as Administrator when you open it - good luck