Related
Finally it's possible to root Alcatel OT-908 with Windows7
After much research I discovered little information about rooting the phone,
seemed like It was like finding a needle in a haystack.
It had led me trying al kinds of Apps supposedly for rooting, I tried
and tried but none seemed to work.
- tried Z4root did not root
- tried lots of others like Universal AndRoot, but the result ... no root
- tried the latest Gingerbreak v.1.2 , This will work on OT-908 with old Firmware (FRG83G.v61S-0)
However it did not root my Alcatel OT-908 from the store because it had the latest Firmware (FRG83G.v63N-0)
To make it work you must use SuperOneClick, read below on how-to.
STEP 1 :
Turn on USB DEBUGGING op your phone :
(in the menu, then settings, then applications, then development, and then making sure USB debugging is on).
STEP 2 :
You must have ADB DRIVERS installed.
See download links below
STEP 3 :
You must have ALCATEL QUALCOMM USB DRIVERS installed.
See download links below
STEP 4 :
Download and extract the latest version of SuperOneClick.
The version that I used was SuperOneClick v2.2 ,
See download links below
FINAL STEP :
Once the ADB Drivers and QUALCOMM USB Drivers are installed, you can simply rightclick SuperOneClick.exe as administrator
(Important , run as Administrator!)
And when SuperOneClick opens , simply press the Root button, and the rooting process should start automatically
and just wait until everything finishes you will get a message if it's been successfull.
It will ask to install busybox. (This is optional)
Congratulations, you are now equipped with a rooted phone, and you should have superuser access on your android phone´s program list.
If it fails ......
ALTERNATIVE STEP :
Bring your phone into recovery mode ;
You will have to shut down the phone make sure it's off,
then turn it on holding the POWER + VOLUME DOWN buttons and holding them until the screen goes on
As soon as the screen goes on and you see lights, press the HOME button and you are in recovery mode,
quickly plug in the phone on your computers USB port.
This is where the drivers must be installed.
If you have not installed the ADB and ALCATEL drivers windows will at this time ask for drivers and you should just let windows try and find the driver online, let it search and in most cases that is all you need. If it still doesn't recognize all the drivers you should point to the ADB folder in SuperOneClick or in the extracted ADB Driver folder and the ALCATEL QUALCOMM USB DRIVERS folder.
Once the ADB Drivers and QUALCOMM USB Drivers are installed, you can simply rightclick SuperOneClick.exe as administrator
(Important , run as Administrator!)
It's important you do this right after you booted, or the superoneclick program might freeze i've tried it many times and I'm sure this is when it worked, so right after you turned it on through recovery.
(power on + volume down until screen goes on, release and press HOME)
Right after you have done this little procedure correctly you hook it up to USB on your PC and quickly open superoneclick (rightclick administrator open)
and quickly press the ROOT button. (Do this very fast as waiting too long will not work)
You will see it run multiple tasks and when completed it will tell you it's completed and your phone is rooted.
It might ask you if you want busybox to be installed, you can choose
yes or no, but i recommend to just have it installed it may make things easier for you in the future if you plan to do more then just rooting your phone.
That's it.
Once it's completed, you should have the superuser application in your menu.
You can test to see if you have rooted successfull with root checker from the Android Market (a Freeware APP which lets you test if you've got a successfully rooted android phone).
If you have succeeded I recommend rebooting.
You should be having the pleasure of having a rooted Alcatel OT-908
If there are any questions, problems please reply and i will be back from time to time to answer questions.
Good luck to you all !
D.
Can't seem to get your steps to work..
Update: It is all in the timing - for me (after making sure antivirus wasn't clearing out the exploits folder) I had to start superoneclick while it was booting, say during the "WIND" animation screen.
Thanks!!
--------------
Hi,
Trying to follow your steps to root my alcatel ot-908
The first method doesn't work for me - the superoneclick log stops at step #5.
Every other attempt I've made results in superoneclick simply freezing after clicking 'root'.
Can you clarify your 2nd method?
1) How long are you holding the power+volume combo?
2) When you say "screen comes on", what do you see on the screen? If I hold for 30 seconds, I continue to see a dead black screen, with lights ON. Home button has no apparent effect. I have to remove the battery to reset.)
3) Are you connecting the USB and starting superoneclick with the android screen blank? Once I got a screen that had a graphic with an android character and a box with a green arrow flowing into the box.
Any help is appreciated, thanks
Maybe I don't know much, but I can't find any executable file in the ADB drivers.
Thank you for sharing with us!
I have a alcatel 906, this method will work on it?
Hi, I'm on froyo 2.2.2 with kernel frg83g.w635-0 (I updated with the build q 1.9.4, downloaded from alcatel site) This firmware cannot be rooted?
I have the version 2.3.4, and tried all disponeble the net and could not and would need to downgrade to a previous order to rooting the terminal
vasoulitos said:
Maybe I don't know much, but I can't find any executable file in the ADB drivers.
Click to expand...
Click to collapse
Install this one:
download. clockworkmod. com/test/ UniversalAdbDriverSetup.msi (Remove the spaces)
It worked for me, i just rooted mine 5 minutes ago.
Warm regards to the community here. I'm using Samsung & LG android devices past 2 years, with lots of custom roms and kernels; but have no experience dealing with Sony device. I am currently helping one of my friend to install Cyanogenmod on her Xperia mini pro sk17i, and help is required. I assure you, I won't have flooded the forum with a new thread if i'd found the answer. So hoping for a gentle guidance..
Here is what i did :
I followed the instructions given at Sony's website from step 1 to 12 : http://unlockbootloader.sonymobile.com/instructions
- I checked that Bootloader unlock allowed is "Yes", and managed to get my unlock key from Sony.
- I downloaded and installed Android SDK manager, also downloaded Google USB driver package revision 4. Also, i managed to download the zip file from Sony and successfully copied & replaced the android_winusb.inf file in the instructed folder.
- Now, at the step 13 mentioned in the guideline, i'm really stuck. I turn of the phone, press & hold volume up while inserting the usb cable.... there appears small blue light at the top of the device. But, nothing else happens.
>> I mean, the instruction says that i should be asked to point the drivers by computers, but my computer asks for nothing. I'm running on windows7 x86, intel core i3.
Please guide me what is going wrong ?? .... however, i should mention that my computer does gives me a notification sound, kind of what usually happens when i attach anything in the usb port.... but, on the screen, it shows no any notification or no any pop up... just nothing at all. I tried the whole procedure on an another computer running windows7 x64, intel core i5, but still stuck at the same problem.
Your help will be very much appreciated. Thanks in advance.
Have you checked "unknown sources" and "usb debuging" on?You will found them both in settings>applications if i translate it right from my greek menu
T3sla said:
Have you checked "unknown sources" and "usb debuging" on?You will found them both in settings>applications if i translate it right from my greek menu
Click to expand...
Click to collapse
Yes, of course both things are checked. To test the things, i also checked upon SEflashtools, and the device shows up there. However, if i command adb devices, it didn't show up on my second corei5 computer, but id did show up on my previous corei3 computer.
I tried out almost all i can do from my previous experiences of dealing with galaxy and optimus devices.. yet, this one is beating me.
Use drivers and tools from this guide and post the results (also mount sdcard to MSC mode)
If link doesn't work download latest flashtool.On installation folder there is a folder named "drivers".Run the file inside.
you have to manually install the driver of your android phone, go to the device manager on your computer, it should appear as S1 boot Fast boot in other devices, update the usb driver with the dowloaded diver android_win_usb.
your device shluld appear as android ADB Interface then you can proceed to step 14 which sadly where I got stuck too. I can't get a a response back from the said step. inform me if you have luck on the next steps...
mooside said:
you have to manually install the driver of your android phone, go to the device manager on your computer, it should appear as S1 boot Fast boot in other devices, update the usb driver with the dowloaded diver android_win_usb.
your device shluld appear as android ADB Interface then you can proceed to step 14 which sadly where I got stuck too. I can't get a a response back from the said step. inform me if you have luck on the next steps...
Click to expand...
Click to collapse
Same here.
- tried to uninstall Devide from the DeviceManager
- reboot PC
- connect my mini (with Vol-Up, blue LED turns on)
- choosed the "Android Booloader Interface"-Driver
- But Device-Manager says it's "Android ADB Interface"
My Datas:
root
CWM (installed through Installer from Market)
StockRom
Windows 7 (32 bit)
greeting
rookie
mooside said:
you have to manually install the driver of your android phone, go to the device manager on your computer, it should appear as S1 boot Fast boot in other devices, update the usb driver with the dowloaded diver android_win_usb.
your device shluld appear as android ADB Interface then you can proceed to step 14 which sadly where I got stuck too. I can't get a a response back from the said step. inform me if you have luck on the next steps...
Click to expand...
Click to collapse
vsrookie said:
Same here.
- tried to uninstall Devide from the DeviceManager
- reboot PC
- connect my mini (with Vol-Up, blue LED turns on)
- choosed the "Android Booloader Interface"-Driver
- But Device-Manager says it's "Android ADB Interface"
My Datas:
root
CWM (installed through Installer from Market)
StockRom
Windows 7 (32 bit)
greeting
rookie
Click to expand...
Click to collapse
Maybe this video can help you.
Thanks friends. Finally got it working ! .... it appears it was surely driver problem. Tried all the given driver links and installed them, and at least one of them must have solved my problem.
Unlocked the bootloader, and flashed nightly 20. Returned the phone back to her.
Thanks again !
officialreloaded said:
Thanks friends. Finally got it working ! .... it appears it was surely driver problem. Tried all the given driver links and installed them, and at least one of them must have solved my problem.
Unlocked the bootloader, and flashed nightly 20. Returned the phone back to her.
Thanks again !
Click to expand...
Click to collapse
Glad i was able to help you
What worked for me:
I removed these lines from the INF:
%SingleAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE
%CompositeAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE&MI_01
That worked.
greetings
rookie
winxp sp3 sony tablet s when put in recovery mode for flashing the mtp driver
shows yellow (!).when i try to install driver manually it trys to start but comes
back with code 10.with tablet in normal mode winxp sees mtp & adb drivers.
the problem is only with recovery mode.tryed all i can think of and read all
solutions but driver still fails to start.so i can,t flash fw!. i really need help with
this one. please someone help i`ll give you a big thanks. i know i am not the
only one with this problem.i hope this is clear enough.
Same problem here:
Everything's fine in normal boot, but in recovery mode, I can't install the MPT driver. Win7pro. It tries to install, but ends up with a Code28 (something in the INF file is invalid, can't tell the english error message, because I have German Win7).
This seems to cause my problem flashing to R5a by AiO or the auto flasher by condi.
I get the exact error message on the tablet, as shown in post #72 in this thread:
[FW R5A WIFI/3G] NEW! custom preROOTed newest stock nbx03 R5A with R1A's recovery
Trying since four nights...
At least I managed to flash and root to 4.0.3 R2a from the "unrootable" 3.2 R10 by flashing via recovery mode to Sony original ICS R2a (downloadable from sony) and then using the AIO 5.3 to root. Don't know why this way is not published here... Tried updating to 3.2.1 etc, nothing worked... the found the links to sony's fw and thought "WTF! Let's try ICS R2a, worst case is an also unrootable Tablet but with ICS". Worked, and was rootable then.
Just ignore the problem. I believe seeing the alerted MTP USB Device in Windows Device Manager when your tablet is in Recovery Mode is being cause by your tablet's borked Android System Recovery Revision 36 (i.e., Rev.36). This problem did not occur with earlier revisions of Android System Recovery. Normally, no MTP USB Device (or Sony Tablet S) should be displayed or even installed for Recovery Mode because a tablet in Recovery Mode cannot provide MTP functionality. Recovery Mode only requires Android Composite ADB Device be installed. Normal Mode, however, requires both Android Composite ADB Device (but only when the tablet's USB Debugging is turned on) and MTP USB Device, which Windows Device Manager renames and displays as Sony Tablet S.
You are basically right... it was ADB drivers, not MTP.
I tried all possible drivers from the list, also some "phone" devices. And YES!! Windows accepted one of them...
After that, I had no problem flashing my tablet to ICS R5a!!
please, could somebody who has writing permission in the dev forums, tell Condi, that the AiO 5.3 tools tells you to check this driver ONLY AFTER you are NOT stuck in "status7" error!!!!!
You do NOT get the message in the terminal box, IF you are stuck.
That would have saved me one or two nights trial and error...
But, after all, I have a nice working ICS R5a on my tablet S
I will post a how-to for other 3.2 kernel10
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
phc1234 said:
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
Click to expand...
Click to collapse
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
android phone dosent show in device manager
ThreeEyes said:
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
Click to expand...
Click to collapse
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
phc1234 said:
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
Click to expand...
Click to collapse
But by manually updating the driver and choosing manually, you can assign ANY driver to any device - it may not work or even do some damage to the system, but basically, it's your choice!
Take the device with the "!" and give it the right driver...
"CAT" above is right with rel5 and 5a that they changed the recovery rev to 36 and this rendered the
tablet s from loading any mtp driver or seeing the android phone entry in device manager so no way
to install adb driver.this has killed conis AIO tool flashing firmware and roms until someone breaks
the lockdown sony put in.
Recently i've been seeing ALOT of queries about how to root the Softwiner EVB Android Tablet
I have one myself and found a way and have tried and successfully completed the process myself.
This is an easy 6 step process. Basically this is what you do.
1. Back your tablet up, probably to your PC, laptop or whatever.
2. Factory reset it so everything is wiped, it should restart
3. It should be rooted after its restart!
4. Restore everything so you can get your apps back
5. Download a root check app from Google Play (it should confirm your device's root) or use SuperOneClick as a fake attempt to re-root your tablet, when it is about to start rooting your tablet a message should pop up saying that your device is already rooted
6. That's it! Have fun and buy a root beer or something
If this helped please click the "Thanks" button, i'll do the same if you just ask me, it's only one click and would mean a lot to me
if you need me for more Softwiner EVB information or information about any android devices (and blackberry devices but i don't know what will bring you here but just in case): follow me on Twitter and DM me @LordwinOfficial
Rooting nuclear softwinerevb
Not working for me. There is no superuser soft or icon after factory reset.
My Tablet is
Manufacturer: unknown
Model: SoftwinerEvb
Android Version: 4.1.1
Build ID: nuclear_evb-eng 4.1.1 JRO03C 20130504 test-keys
Board ID: nuclear
Chipset Platform: exDroid
I tried to root it using SRS Root software. It says that my tablet is root and have superuser icon.
But that superuser irself didn't have a root access.
Is there any ideas how to completely root it.
Thank you
mrlee2k said:
Not working for me. There is no superuser soft or icon after factory reset.
My Tablet is
Manufacturer: unknown
Model: SoftwinerEvb
Android Version: 4.1.1
Build ID: nuclear_evb-eng 4.1.1 JRO03C 20130504 test-keys
Board ID: nuclear
Chipset Platform: exDroid
I tried to root it using SRS Root software. It says that my tablet is root and have superuser icon.
But that superuser irself didn't have a root access.
Is there any ideas how to completely root it.
Thank you
Click to expand...
Click to collapse
Same here
Problem Solve
My problem solved.
I found out that SRSRoot software really did root my tablet. the problem is the Superuser.
So when I update superuser (apk and binary) from 3.0.3.2 to 3.1.1 manually using adb push, the Superuser
thing works fine.
I'm a ahppy man now....
Good luck tou you all
Cheers
[ROOT][GUIDE] How to root non-prerooted SoftwinerEvb Tablet
This is a Root Tool for Android 4.0/4.1 devices.
How to use it:
1. Download and install ADB Driver.
2.Restart your computer once adb driver is successfully installed.
3.Have your device charged to at least 50% to ensure no power interruptions.
4.Backup your device to your computer or external sdcard (I like My Backup app from the Play Store).
5.Download and extract Bin4ary Root Tool to a new folder on your computer.
6.Power on your device and enable USB debugging (Settings>Developer Options>USB debugging>OK).
7.Connect your device to your computer via MicroUSB to USB cable in MTP mode (option will appear in notification bar when you plug your device into your computer).
9.Your computer should automatically install drivers using the previously downloaded and installed adb driver. It may popup a install wizard; follow the wizards prompts. Let Windows update search for it. The computer may say it can't install MTP device; that's ok, click finish or cancel. Then another wizard will popup to install ADB device and will sucessfully install.
10.Double-click "RunMe.bat" (it may just say "RunMe") in the downloaded Root Tool you extracted to a new folder and follow all instructions you see on the application (for SoftwinerEvb tablet choose option 1 by pressing 1 key and then enter/return key on your keyboard).
I've succesfully rooted my SoftwinerEvb (4.1.1 JB) Tablet with it. I haven't flashed any custom recovery, rom, or kernel yet.
HAVE FUN!!
I'll try and answer any questions if I can.
ADB Driver universal
Do I need to worry about "unknown publisher"? Thank you.
How to use it:
1. Download and install ADB Driver.
2.Restart your computer once adb driver is successfully installed.
3.Have your device charged to at least 50% to ensure no power interruptions.
4.Backup your device to your computer or external sdcard (I like My Backup app from the Play Store).
5.Download and extract Bin4ary Root Tool to a new folder on your computer.
6.Power on your device and enable USB debugging (Settings>Developer Options>USB debugging>OK).
7.Connect your device to your computer via MicroUSB to USB cable in MTP mode (option will appear in notification bar when you plug your device into your computer).
9.Your computer should automatically install drivers using the previously downloaded and installed adb driver. It may popup a install wizard; follow the wizards prompts. Let Windows update search for it. The computer may say it can't install MTP device; that's ok, click finish or cancel. Then another wizard will popup to install ADB device and will sucessfully install.
10.Double-click "RunMe.bat" (it may just say "RunMe") in the downloaded Root Tool you extracted to a new folder and follow all instructions you see on the application (for SoftwinerEvb tablet choose option 1 by pressing 1 key and then enter/return key on your keyboard).
I've succesfully rooted my SoftwinerEvb (4.1.1 JB) Tablet with it. I haven't flashed any custom recovery, rom, or kernel yet.
HAVE FUN!!
I'll try and answer any questions if I can.[/QUOTE]
No you don't.
Sent from my SAMSUNG-SGH-I317 using xda premium
Custom Recovery
Is there a custom recovery for the softwinerevb yet? I have one that came with 4.1 this tablet needs a downgrade bad. Very slow. Not happy wit it at all so far. I have root using Bin4ry method. It worked very well. The bad thing is that the creator has posted the file on a site that never lets you download it. You can find it other places tho.
Kingroot worked as well
Sent from my Nexus 5X using XDA-Developers mobile app
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