Database Users

[Q] CWM flashing problem <data transfer failure> [Huawei S7 2.2]

SEE POST #3 FOR SOLUTION
I'm having an issue I can't get past..
I've got the Indonesian 2.2.2 rom on my Australian (Telstra) device (external sd, 2 cameras, resistive)
I'm using goodoane's v2.2 compatable CWM, and xaueious's easy windows flasher. The phone is rooted using superoneclick, and all drivers are installed fine. It process through all the steps until the following one with no problems.
Trying to install , but get the following error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you see it says FAILED <data transfer failure <too many open files in system>>
I cannot figure out a way to get around this. Using the easy windows install script. Please help!

Downgraded to 2.1 and tried the same with 2.1 img. Exact same error. Someone please help :/

OK, so I figured it out.
The drivers weren't installing properly on either of my windows 7/intel core 2 duo systems. So, I hooked the tablet up to me Windows 2000 torrent box, and the huawei drivers installed fine.
I was able to root through that computer, but as seen above I was unable to flash CWM.
So, after more tinkering, I became dedicated to fixing the drivers on my Windows 7 computers.
I copied the driver info from my Win2000 box, and then plugged the tablet into my Win7 PC.
Instead of using the 'update driver option' by pointing the computer to a specific location (where the huawei drivers were), I selected 'have disk', and then did that.
The drivers for 'Win7&XP' were still not working, so I decided screw it, and pointed the computer to the 'Win7-AMD' drivers using the have disk option. I specified the correct INF (as seen in driver details from the Win2000 box), and to my surprise it installed correctly!
I then enabled USB debugging, and followed the exact same process; pointing my computer to the Windows 7-AMD drivers as opposed to the Win7&XP drivers, even though I have an intel CPU. It worked.
I then flashed CWM onto my Tablet with the stock 2.1 rom. I'm now upgrading to indonesian 2.2 and will flash the appropriate 2.2 version of CWM, which i'm sure will work.
Hope this helps someone out there!

Big problem (I think)

I've tried rooting my Nexus 7 and not sure what's gone wrong.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what happens when I load CWM.
Prior to this point what I did was unlock the bootloader and then process to flash CWM, then load CWM and flash SuperSU from sdcard but it's gone a bit wrong.
Anybody got an ides what the hell I've done wrong?

UrbanDesigns said:
I've tried rooting my Nexus 7 and not sure what's gone wrong.
This is what happens when I load CWM.
Prior to this point what I did was unlock the bootloader and then process to flash CWM, then load CWM and flash SuperSU from sdcard but it's gone a bit wrong.
Anybody got an ides what the hell I've done wrong?
Click to expand...
Click to collapse
Hi, UrbanDesigns...
Are you sure you have the correct version of CWM installed on your Nexus 7 ?
The references in your screenshot to an SD Card are a bit odd, given the Nexus 7 doesn't have an SD Card.
(...and the most recent version for Nexus 7 of CWM is 6.0.3.6... your screenshot shows your version to be 6.0.2.3).
Download the correct CWM recovery image from here for either your 'tilapia' (3G & WiFi) Nexus 7 or your 'grouper' (WiFi only) Nexus 7... whichever one you have.
And fastboot flash it with...
Code:
fastboot flash recovery recovery.img
...where recovery.img is the actual name of your recovery image file. Personally, I just think it's easier to rename it to recovery.img, and then flash it. Less scope for typos at the command prompt.
Hope this helps... good luck.
Rgrds,
Ged.

I was following this.
For some reason windows says it does not recognize my device now, it says "The last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
I was following this:
http://forum.xda-developers.com/showthread.php?t=2150661
So I assume everything was correct.
The only difference is I used Minimal ADB and Fastboot
The tablet is fully functioning now but won't get recognized by my PC, it's listed as "Unknown Device" under "Other Devices"
When I try to manually select where the driver folder is it instantly fails and says windows was unable to install your unknown device

Bricked Help Me

i tried to flash drivers i get this errer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i was on android l v12 , my device is note 3g
i tried to flash new offical miui6 via twrp 2.8 i got error
and wiped data,system etc...
so i am not able to enter recovery and even into rom what to do??
Please Help ME

It seems a problem with Windows rather than with your phone.
First of all don't worry, there are very high chances that you will recover the phone in working state. I worked for over a year with MTK devices, they brick very easily but it's also easy to unbrick.
It's a signature error, not a driver error. I remember Windows has somewhere the option to disable signature checking for drivers. Disable it, then after installing this driver you can re-enable it if you want.
I assume you are able to proceed from this step on, once phone is recognized by PC. If I'm wrong, feel free to ask

To Install Driver without Signature error.
This will Help u to install driver without signature.
What to do:
1. Hold down the Windows key on your keyboard and press the letter C to open the Charm menu, then click the gear icon (Settings).
2.Click More PC Settings.
3. Click General.
4. Under Advanced Startup, click Restart Now.
NOTE: In Windows 8.1, the ‘Restart Now’ button has moved to ‘PC Setting -> Update & Recovery -> Recovery.’
5. After restarting, click Troubleshoot.
6. Click Advanced Options.
7. Click Windows Startup Settings.
8. Click Restart.
9. After restarting your computer a second time, choose Disable driver signature enforcement from the list by typing the number 7 on your keyboard.
10. After restarting, you will be able to install the drivers normally; however, Windows will display a warning message. When the warning appears, click Install this driver software anyway.
You are now complete. I hope this will help you. Good Luck..

OP 6T fastboot device not detected

I had to reinstall Win 10 on my computer and now I'm not able to connect to my 6T in order to root it.
The boot locker is unlocked, I can see it at phone boot. It was unlocked also before last update to OxygenOS 10.3.7.
Debug USB in enabled. When I connect to the phone to the computer it is deceted and I can transfer files.
Whit ADB devices phone is deteted (picture is from all in one tool, using command prompt same result)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
using fastboot devices the phone is not detected.
installed last official usb drivers (google and oneplus)
Any idea, suggestion or further test that can help?
Thanks

Same problem here. Please help.

Finally I found a working solution.
If you have a laptop you have to disable secure boot.
Then you have to disable signature verification on windows 10 ( How to Enable or Disable Driver Signature Enforcement in Windows 10 | Tutorials (tenforums.com) ).
I used option 3.
Download Oneplus usb drivers ( Download Latest OnePlus USB Drivers for Windows and Mac (getdroidtips.com) ).
Then connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device. If it is found, this means windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.

Thanks man, it worked for me.
Just to complete, after istalling the drivers you can restore signature verification and secure boot on Win 10.
Everything will work fine.

[Guide]Another fastboot/fastbootd driver guide for Windows

Background​When I got my OnePlus 8T (after using Samsung devices and a OnePlus 3T for many years) I could access the phone using adb and, when the phone was in Bootloader mode, using fastboot. But I couldn't access the phone in Fastbootd mode.
I tried lots of different things but none of them worked for me and, worst of all, many of the solutions required downloading files from untrusted sources.
I finally decided to see if the Google USB driver would help and, to my surprise, it fixed the fastbootd problem. So I uninstalled the drivers that were being used for Bootloader mode, the Google driver used for Fastbootd mode,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and then did a clean install of the Google USB driver so that I could document the process.
Installation​Without a suitable driver when connected in Bootloader (or Fastbootd mode), my phone shows up under "Other devices" as "Android" with a yellow warning triangle:
I downloaded the Google Windows USB driver from https://developer.android.com/studio/run/win-usb, extracted the contents, and installed the driver by right-clicking on usb_driver/android_winusb.inf and selecting Install:
Next, I booted my phone into Bootloader mode (Note: if Bootloader mode works for you and you didn't want to uninstall the driver, then boot into Fastbootd), found my phone in Device Manager (Other devices), double-clicked it (Android) to pull up the driver details and clicked the Update Driver... button. On the next screen select the second option "Browse my computer for drivers":
And on the next screen I selected "Let me pick from a list of available drivers":
I chose "Androd Device" and clicked on Next:
This brings up the following screen:
(Note: I also have Samsung drivers installed). I clicked on "Google, Inc." under Manufacturer, then "Android Bootloader Interface" from Model and clicked on Next.
I got a warning, to which I replied "Yes":
and the installation completed successfully:
Notice that the phone now shows up as "Android Bootloader Interface" under "Android Device" in Device Manager. Double clicking on it now shows the driver is installed:
And that's it!
I now find that I can also boot into Fastbootd mode, even though I only installed the driver for Bootloader mode.
Note: this driver also works for my OnePlus 3T