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!

[Q] Unknown Device in Windows when CWM recovery is loaded

When I reboot my device into CWM recovery (fastboot boot method, didn't flash it) my phone isn't recognized in Windows. In Device Manager it says 'Full JellyBean on Mako' but I am unable to do things like mount the sdcard or adb sideload. I tried to point the device to the google usb drivers but they weren't recognized. MTP and ADB work great within Android and Fastboot works in the Bootloader. Anyone know what I need to do to get the device recognized in Windows within CWM recovery? Is it simply the fact that I am booting from the image rather than flashing it?
{
"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"
}

71 views and no one has any ideas...this isn't good lol.

LOL it's naver good when no one will even take a guess at it. It may be do it you booting from an Image, but I still think it may be a driver problem. With using the SDK it's some times hit and miss on getting the drivers install right. If it was me I would install mskip's great little toolkit. In it one of the first things it list is install drivers. That way you have something to check with other then the SDK. and you just may like the kit better. It's for windows only but looking at the screen shoot it looks like you are on vista or win 7 so no problems their.
Sorry I could not be of more help, I have the SDK running in linux yet I have moved to mskip's toolkit it does all I need it to do and more. here's the link http://forum.xda-developers.com/showthread.php?t=1995688

Todd said:
Sorry I could not be of more help, I have the SDK running in linux yet I have moved to mskip's toolkit it does all I need it to do and more. here's the link http://forum.xda-developers.com/showthread.php?t=1995688
Click to expand...
Click to collapse
Thank you, sir. I will give this a shot and see what happens!

Used the toolkit to remove the Google drivers and then installed the drivers provided with the toolkit and everything is working now! When in CWM, the phone now shows up as Google Galaxy Nexus instead of Nexus 4 but as far as I can tell all is well. I'd buy you a beer if I could! haha.

Glad I was able to help.

Forgot pattern and cannot recover- nexus 4 with android 5+ lollipop

Hello.
I've repaired a nexus 4 screen and digitizer but I got it back because my friend can't recover access from a forgotten pattern lock.
He is running stock android 5 lollipop and he doesn't get the email recovery option when he inputs wrong pattern. I've searched even in google support but I didn't find a solution to recover his photos.
My main concern is to recover files and photos!!! There isn't a reason to suggest a factory reset....
--Phone Status---
Boot loader seems unlocked "Locked state is marked as unlocked in bootloder in red letters" while secure boot is enabled in green letters
USB debugging seems OFF: There is no android device listed in device manager. I only get a music player in disk drives which is empty.
adb devices command in bootloader recognises it
When entering to recovery I get the message "no command" along with the icon of an android under repair.
No dropbox no google+ photos backup
---What I've tried---
UPDATE: Managed to flash TWRP 2.7.1.0 I can see the files but since usb flash drive doesn't work I can't copy the files...
Android Device manager: Returns error that the phone is already locked and there is no need to apply new password.
Tried about 30 wrong patterns and it didn't came up the google mail recovery option.
Tried during a phone call to see the files but I only managed to turn on WiFi.
{
"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"
}

When you say the USB flash drive doesn't work, do you mean the USB port in the phone?

MTP doesn't always work in TWRP, meaning it won't show up as a normal usb drive on a pc. ADB will still work though, you have to set up ADB on your computer, boot into twrp on the phone and use 'adb pull' to copy the files to the computer. On windows you will need to download adb and the drivers, I use http://www.koushikdutta.com/post/universal-adb-driver

I'm trying to install the drivers for adb but I cannot find the right one.
Edit: Also it cannot be detected from boot loader now. I'll try in a pc that already has been connected and worked.
I have adb and fastboot installed already and worked with this and my own phones.
Edit: It seems to be a lost cause the phone fell down many times. Don't bother maybe I'll solder a usb port first... if it is possible with my less than basic equipment.

There are many methods on the following page,
http://forum.xda-developers.com/showthread.php?t=2620456
The way I did it was an alternative version of method 5 while in twrp.
Method 5 - alternatively, Mount system in twrp and delete the file /data/system/gesture.key
If it asks for a pattern on boot just try any random pattern it should let you in. I did this when a version before lollipop was installed but there is no reason it shouldn't work on lollipop as the same file is saved in the same location, just checked.
Using adb
adb shell rm /data/system/gesture.key
Click to expand...
Click to collapse

[TUTORIAL][WINDOWS]Solution: File Transfer in TWRP Recovery[17-08-2015]

Tutorial: How to transfer files to/from our Moto G while in TWRP recovery​
This tutorial have been tested in 7, 8, 8.1 and 10 Windows versions. It can work with other devices beside Moto G.
{
"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"
}
Sometimes we need to transfer files to our device while we are in recovery mode. When we forget to copy the zip we were going to flash, when we are installing a
GPE based ROM (we must format /data and erase all files), to transfer a backup... ect. In many cases we need this function.
The purpose of this tutorial is to make our PC succesfully recognize our Moto G as a storage device being in TWRP recovery.
Many users have reported that their devices are not being recognized.​
Requirements:
-Have installe the last TWRP recovery version.
-Have installed ADB drivers in PC. You can try this ones Universal ADB Drivers or Motorola Mobile Drivers 64 bits
-USB data cable.
-PC runnig Windows 7, 8, 8.1 or 10 (can work with older versions).​Steps: Sorry for spanish images, if you can provide me english captures would be great.
1) Boot into recovery mode and connect to PC with USB data cable.
2) Being completely sure your device is not being recognized, otherwise this tutorial will be totally useless to you.
3) Open Control Panel and click on Hardware and Sound
4) Go to Device Manager.
5) Look for 'Android Device' or 'Android Phone' or any related name, open the list, rigth-click on the device and click on 'Update driver software'.
6) Now click on the second option.
7) Now click on the option below:
8) Make sure 'ADB composite device' is there and click next.
9) Once this is donde, reboot your PC and it will be in capacity to recognize your device as a storage device while you are in TWRP recovery. We can freely transfer files.​---------------------------------------------------
Last Update: 17-07-2015

Reserved

Thanks

[HELP] TWRP One Plus 5 Not working

SOLVED UPDATED TO LAST OTA AND DID THE WHOLE TUTORIAL AGAIN.
Tried different USB ports. ( 3.0 / 2.0 )
{
"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"
}

Tried in 2 different PCs and 6 usb ports 2.0 and 3.0
Windows 8 and windows 10.

Have you tried using cmd (administrator) istead of PowerShell?

Lamizure said:
Have you tried using cmd (administrator) istead of PowerShell?
Click to expand...
Click to collapse
Yes

It's really strange... Have you unlocked the bootloader?

Yes " Device State - Unlocked "

It's due to the filename being too long. I found a different fastboot which allowed long filenames. Rename it to one letter like r.img or something and see if it works.

Had exact the same problem under Linux
People mention to change to another USB port but that did not help
What helped... if all stuff is correctly installed (adb, root rights, etc.)
1. Reboot into the bootloader (even if you are in already)
adb reboot bootloader
Click to expand...
Click to collapse
2. Then directly (use the arrow up key to really be fast enough) send the command for flashing (my file was called twrp.img)
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
If this doesn't work you could try (under Linux) to write a little script with just the two above commands or try
adb reboot bootloader && fastboot flash recovery twrp.img
Click to expand...
Click to collapse
It seems to be a timing problem... One might need to play around with the time between this two commands. E.g. wait until the bootloader screen is on the phone and directly issue the flash command. Sorry after it worked for me I did not bother to investigate it in more detail.