• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.
Sign in to follow this  
Followers 0

OSFII bootloader USB driver

3 posts in this topic

Posted · Report post

Hi, new here so hopefully you will all be gentle with me ;)

I'm trying to unlock my OSFII and have got stuck fairly early on. I started with the how to here... but the starting up into "FTM" mode doesn't work, I assume because I need a stock recovery flashing first?

So, I went over to the procedure here however at step (installing recovery) it hangs, "waiting for device".

So..... I started messing around with adb...

"adb-windows.exe devices" works, giving "P736V_OUK Device" and

"adb-windows.exe reboot bootloader" reboots the phone to the green android robot.

However at this point I get a error in the device Manager (Other devices->android) "The drivers for this device are not installed. (Code 28)"

So, I tried re-installing the ZTE drivers and get "you have installed a higher version application, the installation will exit". I then tried the standard google USB drivers (installed from the SDK, browsing from update driver software to ...\extras\google\usb_driver) and it says windows could not find the driver.

So now I am stuck, any ideas?

Windows 7, 64bit btw.

0

Share this post


Link to post
Share on other sites

Posted · Report post

Hi, new here so hopefully you will all be gentle with me ;)

I'm trying to unlock my OSFII and have got stuck fairly early on. I started with the how to here... but the starting up into "FTM" mode doesn't work, I assume because I need a stock recovery flashing first?

So, I went over to the procedure here however at step (installing recovery) it hangs, "waiting for device".

So..... I started messing around with adb...

"adb-windows.exe devices" works, giving "P736V_OUK Device" and

"adb-windows.exe reboot bootloader" reboots the phone to the green android robot.

However at this point I get a error in the device Manager (Other devices->android) "The drivers for this device are not installed. (Code 28)"

So, I tried re-installing the ZTE drivers and get "you have installed a higher version application, the installation will exit". I then tried the standard google USB drivers (installed from the SDK, browsing from update driver software to ...\extras\google\usb_driver) and it says windows could not find the driver.

So now I am stuck, any ideas?

Windows 7, 64bit btw.

ok. 1 step forward but still stuck. I updated the USB driver by using "let me pick from a list" and selected google->Handset ADB interface". Then I was able to do a "fastboot-windows.exe flash recovery recovery.img" and "fastboot-windows.exe reboot", go into FTM mode and backup using QPST.

However when I get to running "download.exe" the start button is greyed out. I have a "ZTE Handset Diagnostic Interface(DFU) (COM5)" port and QPST can still find the device......

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

ok. 1 step forward but still stuck. I updated the USB driver by using "let me pick from a list" and selected google->Handset ADB interface". Then I was able to do a "fastboot-windows.exe flash recovery recovery.img" and "fastboot-windows.exe reboot", go into FTM mode and backup using QPST.

However when I get to running "download.exe" the start button is greyed out. I have a "ZTE Handset Diagnostic Interface(DFU) (COM5)" port and QPST can still find the device......

hmmm... ok. A PC reboot got an active start button. So did that. "Download successful" it said but now the phone only boots to the "CWM-based Recovery v4.0.1.5" and none of the options there appear to do anything....

Help :(

EDIT: Oops, I hadn't realised the recovery keys had changed. Recovery options do work but I needed to install the upgrade before it would boot up.

So the published upgrade instructions weren't quite right for me but I got there in the end!

Edited by brman
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.