Database Info

[TIP] Downgrade from JB to 0.30 works!

G'day guys, I won't go into too much detail but as I lost root by updating OTA to JB I have been successfully able to downgrade the firmware to 0.30 (and bootloader evidentially)
WARNING: YOU WILL LOSE ALL DATA ON INTERNAL STORAGE, IM NOT RESPONSIBLE FOR BRICKS, TRY AT OWN RISK!
WARNING: DO NOT TRY TO WIPE DATA FROM THE BOOTLOADER WHILST A CUSTOM RECOVERY IS INSTALLED, YOU WILL BRICK YOUR TABLET MAKE SURE YOU ARE RUNNING THE STOCK JB/ICS BOOTLOADER BY FLASHING THE ASUS BLOB PACKAGE FIRST!
You must have unlocked bootloader and be running the latest firmware 10.4.4.16
Procedure
1) Download 0.30 update from Asus website: http://www.asus.com.au/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
2) extract the blob file from inside the second zip, put in your ADB/FASTBOOT directory
If you don't have fastboot download it here http://www.mediafire.com/?nbw2ofv3xd5s35l
3) Reboot tablet into bootloader (ON + VOLDOWN) then select fastboot mode
4) type command: fastboot -i 0x0b05 flash system blob
5) wait for ages....
6) the install will hang on the spinning asus diagram
7) reboot into bootloader and select the "wipe data" (same menu as where fastboot is)
8) should reboot automatically and you should have sucessfully downgraded to ICS 0.30
Hope it also works for you.

http://forum.xda-developers.com/showthread.php?t=1492887
Does it work with above method?

No idea, but you're welcome to try
Sent from my GT-I9100 using xda app-developers app

Has anyone tried this method to downgrade to .26 from .30?
Ok, confirmed, it doesn't work to revert to .26. You get signature mismatch. I gave it a shot
Now, if I upgrade to JB and downgrade can I go to .26? Hmmm, might give it a whirl.

tbtaf said:
Has anyone tried this method to downgrade to .26 from .30?
Click to expand...
Click to collapse
It won't work. You will get a signature mismatch. It seems to work between JB & 0.30

b3z said:
It won't work. You will get a signature mismatch. It seems to work between JB & 0.30
Click to expand...
Click to collapse
I can confirm this does work and does revert the bootloader.

Guys, can we move this to development? I personally believe it would be a great help to many over there. It saved my backside. I can tell you that! Great threat here!:laugh:

Uh, I can't access fastboot anymore with the JB update. It comes up as unknown device. I have installed the Naked Drivers and have had it installed for awhile with no problems.
The cmd sticks to < waiting for device >.

Can you create a zip with the right ADB/FASTBOOT drivers? I have try many but my tablet is not showing when i do FASTBOOT DEVICES
---------- Post added at 06:06 AM ---------- Previous post was at 05:58 AM ----------
androidxen said:
Uh, I can't access fastboot anymore with the JB update. It comes up as unknown device. I have installed the Naked Drivers and have had it installed for awhile with no problems.
The cmd sticks to < waiting for device >.
Click to expand...
Click to collapse
same here

2) extract the blob file from inside the second zip, put in your ADB/FASTBOOT directory
Click to expand...
Click to collapse
ADB/FASTBOOT folder? Sorry, haven't really fooled around much with my TF700, except for getting root. (and then loosing it like an idiot when I rushed to upgrade to JB)

Accophox said:
ADB/FASTBOOT folder? Sorry, haven't really fooled around much with my TF700, except for getting root. (and then loosing it like an idiot when I rushed to upgrade to JB)
Click to expand...
Click to collapse
1) To be able to use this fastboot method you need to have installed the android-sdk (google it) with the platform-tools package and also the Google USB drivers (i think it is in the extras package)
1A) Alternatively download this package, it contains the ADB/FASTBOOT application... not sure about the correct drivershttp://www.mediafire.com/?nbw2ofv3xd5s35l
2) Inside this package are two executables called adb and fastboot. Using windows command prompt you will have to navigate to the folder that contains these two executables and type "fastboot devices" if you have your TF700 plugged in and in fastboot mode you should see a few numbers and you're ready to go!

b3z said:
1) To be able to use this fastboot method you need to have installed the android-sdk (google it) with the platform-tools package and also the Google USB drivers (i think it is in the extras package)
1A) Alternatively download this package, it contains the ADB/FASTBOOT application... not sure about the correct drivershttp://www.mediafire.com/?nbw2ofv3xd5s35l
2) Inside this package are two executables called adb and fastboot. Using windows command prompt you will have to navigate to the folder that contains these two executables and type "fastboot devices" if you have your TF700 plugged in and in fastboot mode you should see a few numbers and you're ready to go!
Click to expand...
Click to collapse
Oh, well, then I'm an idiot. I thought it was a /system/fastboot or something silly that asus decided to do. Simple enough.

I get a:
C:\platform-tools>fastboot -i 0x0b05 flash system WW_9.4.5.30.zip (this is the unpacked update from the asus site)
sending 'system' (375245 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.656s

Should I have unlocked bootloader to downgrade?

does the "wipe data" feature of the stock recovery really delete the whole internal storage or does it leave the internal sdcard partition intact? i forgot to make a backup of this part (only my apps through titanium) and now my JB upgrade failed and i don't want to lose all my pictures and stuff

0x000 said:
does the "wipe data" feature of the stock recovery really delete the whole internal storage or does it leave the internal sdcard partition intact? i forgot to make a backup of this part (only my apps through titanium) and now my JB upgrade failed and i don't want to lose all my pictures and stuff
Click to expand...
Click to collapse
It does. I made that mistake too, lost my notes for the year so far... :banghead:
Sent from my Incredible 2 using xda app-developers app

How long might 'ages' be?
Been at sending 'system' (798394 KB) ...
for over 15 mins
Sent from my HTC PH39100 using xda premium

kyrtap10 said:
Should I have unlocked bootloader to downgrade?
Click to expand...
Click to collapse
You do need to unlock your bootloader to down grade.

buhohitr said:
You do need to unlock your bootloader to down grade.
Click to expand...
Click to collapse
Ok, now I know to make sure that I have backup of my root before updating

160bpm said:
I get a:
C:\platform-tools>fastboot -i 0x0b05 flash system WW_9.4.5.30.zip (this is the unpacked update from the asus site)
sending 'system' (375245 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.656s
Click to expand...
Click to collapse
you can't just flash the zip, you have to extract the "blob" file inside the zip and flash that

Root and Custom CWM recovery for VSD220

I got the device which is really nice, I rooted the first night, I then updated to version 1.1, lost root as usual but luckily my copy of CWM works fine for both versions 1.0 and 1.1.
If you are familiar doing this with android phones, just follow the same steps.
Use at own Risk
Download both files. Make sure they are complete and the file sizes match.
Save recovery.img to computer, and su.zip to VSD220,
Gain access to adb for your device,
go to terminal or command prompt and type "adb reboot bootloader",
and then enter.
The screen will turn solid black,
in the same terminal type "Fastboot flash recovery recovery.img",
and enter, make sure you are in the same directory as your recovery.img.
The recovery will flash quickly, when complete type "fastboot reboot", enter.
Your device will boot up,
make sure you have Su.zip saved on the VSD220 in the directory /mnt/external_sd/su.zip,
you must have an external sd card inserted,
you can confirm this with root explorer even without root.
In terminal type adb reboot recovery,
you should have a working CWM that will allow you to flash su.zip, and perform a nandroid backup, etc.
If CWM offers to block the stock recovery, accept it.
Otherwise you will need to delete or rename /install-recovery.sh and/or /system/recovery-from-boot.p.
Enjoy Root.
This works for both version 1.0 and 1.1.

Cool, thanks!

Can't seem to get "adb devices" to come up with anything. Using Android Composite ADB Interface for driver, no luck at all.
Any help on which ADB driver to use and where to download appreciated.
sk8tingusmc said:
I got the device which is really nice, I rooted the first night, I then updated to version 1.1, lost root as usual but luckily my copy of CWM works fine for both versions 1.0 and 1.1.
If you are familiar doing this with android phones, just follow the same steps.
Use at own Risk
Download both files. Make sure they are complete and the file sizes match.
Save recovery.img to computer, and su.zip to VSD220,
Gain access to adb for your device,
go to terminal or command prompt and type "adb reboot bootloader",
and then enter.
The screen will turn solid black,
in the same terminal type "Fastboot flash recovery recovery.img",
and enter, make sure you are in the same directory as your recovery.img.
The recovery will flash quickly, when complete type "fastboot reboot", enter.
Your device will boot up,
make sure you have Su.zip saved on the VSD220 in the directory /mnt/external_sd/su.zip,
you must have an external sd card inserted,
you can confirm this with root explorer even without root.
In terminal type adb reboot recovery,
you should have a working CWM that will allow you to flash su.zip, and perform a nandroid backup, etc.
If CWM offers to block the stock recovery, accept it.
Otherwise you will need to delete or rename /install-recovery.sh and/or /system/recovery-from-boot.p.
Enjoy Root.
This works for both version 1.0 and 1.1.
Click to expand...
Click to collapse

admisi said:
Can't seem to get "adb devices" to come up with anything. Using Android Composite ADB Interface for driver, no luck at all.
Any help on which ADB driver to use and where to download appreciated.
Click to expand...
Click to collapse
Sorry, was using outdated adb.
So got adb, flashed recovery.img, recovery flashed ok, rebooted...but now when I adb reboot recovery, it reboots and then stuck on green android with red triangle.
Any advice?

admisi said:
Sorry, was using outdated adb.
So got adb, flashed recovery.img, recovery flashed ok, rebooted...but now when I adb reboot recovery, it reboots and then stuck on green android with red triangle.
Any advice?
Click to expand...
Click to collapse
Ok, I worked it out now. But for others, the problem was that recovery image was being replaced with the original on the command "fasboot reboot".
So instead, immediately after typing "Fastboot flash recovery recovery.img" I typed the following command "fastboot boot recovery.img".....AND only then did I get CWM which allowed me to flash su.zip from SD card.
Thanks for all help. Now that I have root, what changes/tweaks did you make using root?
Is there an optimum dpi to apply and are you overclocking?
Thanks.

Here is a script to reboot recovery mode; from your Android VSD220.
sk8tingusmc said:
I got the device which is really nice, I rooted the first night, I then updated to version 1.1, lost root as usual but luckily my copy of CWM works fine for both versions 1.0 and 1.1.
If you are familiar doing this with android phones, just follow the same steps.
Use at own Risk
Download both files. Make sure they are complete and the file sizes match.
Save recovery.img to computer, and su.zip to VSD220,
Gain access to adb for your device,
go to terminal or command prompt and type "adb reboot bootloader",
and then enter.
The screen will turn solid black,
in the same terminal type "Fastboot flash recovery recovery.img",
and enter, make sure you are in the same directory as your recovery.img.
The recovery will flash quickly, when complete type "fastboot reboot", enter.
Your device will boot up,
make sure you have Su.zip saved on the VSD220 in the directory /mnt/external_sd/su.zip,
you must have an external sd card inserted,
you can confirm this with root explorer even without root.
In terminal type adb reboot recovery,
you should have a working CWM that will allow you to flash su.zip, and perform a nandroid backup, etc.
If CWM offers to block the stock recovery, accept it.
Otherwise you will need to delete or rename /install-recovery.sh and/or /system/recovery-from-boot.p.
Enjoy Root.
This works for both version 1.0 and 1.1.
Click to expand...
Click to collapse
Here is a script to reboot recovery mode; from your Android VSD220.
********* script starts here
#!/system/bin/sh
su
echo -n recovery | busybox dd of= /dev/block/emmc count=1 conv=sync; sync; reboot recovery
********* script ends here
I used Scripter Ver. 1.8 It work find. Don't forget to flash the right recovery.img and install su.zip. If you don't the script won't work.

has anyone gotten this to work lately? The device I'm playing with has 1.3 firmware on it. For some reason, I haven't gotten adb to work on this device in windows, and in ubuntu, I can adb reboot bootloader, and it goes to the black screen, but any fastboot commands, just sits there waiting for device. Any suggestions would be appreciated.

n1gh7m4r3 said:
has anyone gotten this to work lately? The device I'm playing with has 1.3 firmware on it. For some reason, I haven't gotten adb to work on this device in windows, and in ubuntu, I can adb reboot bootloader, and it goes to the black screen, but any fastboot commands, just sits there waiting for device. Any suggestions would be appreciated.
Click to expand...
Click to collapse
I didn't know 1.3 was available. Is this a recent firmware? I checked a couple weeks ago.

Not sure, it's not my monitor, just looking at it for a friend. when I go to about, system update I see vsd220 system update 1.3 device system version : IMM76D.UI23ED02_VSC and same info under server version

Got it sorted out after hunting on google. it does work

problem with adb
Ok so i got the device being recognized on my XP machine. Really did not have to do much. Just pluged it in and everything worked.
On my Windows 7 machine when i plug in the device i only see the MTP installed and then see VSD220 in MY COMPUTER and can browse the files. I do not see it when i "adb devices".
1) USB debugging is on/enabled
2) Both laptops have Eclipse with latest ADB and ADT tools installed
Any suggestions as to what i can do? Anyone can copy over drivers that are working with your win7 machine?

Confirmed Working for Acer DA220HQL (atleast for me)
Thanks to sk8tingusmc for posting the instructions. I followed them as well as the comments below and rewrote the instructions to reflect what worked for me on my Acer DA220HQL Smart Display. Which seems to be about the same device as the Viewsonic VSD220
Use at your own Risk - Acer DA220HQL
1. Download both files from the first Post (Thanks to sk8tingusmc).
Make sure they are complete and the file sizes match.​2. Save "recovery.img" to your computer, and copy su.zip to the Acer DA220HQL to "/mnt/external_sd/su.zip"
3. Press Windows Key + R to open the Command Prompt or Start > Run > cmd > Enter
4. At the Command Prompt change to the Directory with adb.exe in my case "C:\Temp\sdk\platform-tools"
Download SDK from here: http://developer.android.com/sdk/index.html#download and extract in my case to C:\Temp (C:\Temp\sdk, C:\Temp\eclipse, and C:\Temp\SDK Manager.exe)​5. At the Command Prompt type "adb reboot bootloader" and hit enter.
The screen will turn solid black​6. At the Command Prompt Type "Fastboot flash recovery recovery.img" and hit enter.
Make sure you are in the same directory as your recovery.img.
The recovery will flash quickly
C:\Temp\sdk\platform-tools>Fastboot flash recovery recovery.img
sending 'recovery' (5688 KB)...
OKAY [ 0.176s]
writing 'recovery'...
OKAY [ 0.983s]
finished. total time: 1.163s
​7. At the Command Prompt Type "fastboot boot recovery.img" and hit enter.
C:\Temp\sdk\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.173s]
booting...
OKAY [ 0.001s]
finished. total time: 0.178s
Your device will boot up​8. At the Command Prompt Type "adb reboot recovery"
It will enter ClockworkMod Recovery v6.0.2.8 with Touch Support. ​9. Choose ZIP File from SDCard navigate to su.zip and select it by pressing on it.
Scroll all the way down to find ++++Go Back++++ on the SDCard if you entered the wrong Directory.
You may also choose to create a Nandroid Backup if you care to do so.​10. Go Back and select Reboot
11. ROM may Flash stock recovery on boot. Fix? - Yes - Disable recovery Flash
Otherwise you will need to delete or rename /install-recovery.sh and/or /system/recovery-from-boot.p.
​12. View attachment 2062751

Rom Version and work in Linux?
swiss420 said:
Thanks to sk8tingusmc for posting the instructions. I followed them as well as the comments below and rewrote the instructions to reflect what worked for me on my Acer DA220HQL Smart Display. Which seems to be about the same device as the Viewsonic VSD220
Click to expand...
Click to collapse
I was wondering what ROM Version is your DA220HQL on (ES I think?) and will the instructions work in Linux or other *nix like systems?
The main problem I have is that I do not have any drivers so adb in Windows XP will recognize it. It is recognized under Ubuntu 12.04 for me.
Thanks for the info! I am very excited to get this working better than out of the box!

LoveMyAndroid2010 said:
I was wondering what ROM Version is your DA220HQL on (ES I think?) and will the instructions work in Linux or other *nix like systems?
The main problem I have is that I do not have any drivers so adb in Windows XP will recognize it. It is recognized under Ubuntu 12.04 for me.
Thanks for the info! I am very excited to get this working better than out of the box!
Click to expand...
Click to collapse
There are a universal ADB Drivers for Windows.
Universal Naked Driver for example.
http://forum.xda-developers.com/showthread.php?t=1161769
Or the following link which I have no clue about who maintains this site and how secure it is running that Exe. So please check first for yourself before yelling at me. http://adbdriver.com/
Regarding the ROM Version I was on, check the other Thread where I listed them all.

swiss420 said:
There are a universal ADB Drivers for Windows.
Universal Naked Driver for example.
http://forum.xda-developers.com/showthread.php?t=1161769
Or the following link which I have no clue about who maintains this site and how secure it is running that Exe. So please check first for yourself before yelling at me. http://adbdriver.com/
Regarding the ROM Version I was on, check the other Thread where I listed them all.
Click to expand...
Click to collapse
Well I got the ADB driver installed and I can use it! However I tried the root procedure and it failed to root.
When I was in the CW, the one thing it kept giving an error such as cannot mount sdcard. I checked the sdcard and su.zip IS on it, but the recovery could not locate it. I did try using the sideload method and it seemed to work, but when I rebooted and checked for root, it was not successful.
I tried this in both Ubuntu and Windows with the same result. I even performed a factory reset and tried again. And the same thing: no root.
Is there a timing issue with when to enter the commands?
The info on my DA220HQL from about is as follows:
Model number
DA220HQL
Android version
4.0.4
Kernel version
3.0.21-00003-OMAP-Android+
[email protected] #1
SMP PREEMPT Mon May 13 10:06:22 CST 2013
Scaler version
BA0.2A en_PA
Touch driver version
1.1.0509.1
Build number
IMM76D.UI23ED22_ACE​
Thanks for the help!

LoveMyAndroid2010 said:
Well I got the ADB driver installed and I can use it! However I tried the root procedure and it failed to root.
When I was in the CW, the one thing it kept giving an error such as cannot mount sdcard. I checked the sdcard and su.zip IS on it, but the recovery could not locate it. I did try using the sideload method and it seemed to work, but when I rebooted and checked for root, it was not successful.
I tried this in both Ubuntu and Windows with the same result. I even performed a factory reset and tried again. And the same thing: no root.
Is there a timing issue with when to enter the commands?
The info on my DA220HQL from about is as follows:
Model number
DA220HQL
Android version
4.0.4
Kernel version
3.0.21-00003-OMAP-Android+
[email protected] #1
SMP PREEMPT Mon May 13 10:06:22 CST 2013
Scaler version
BA0.2A en_PA
Touch driver version
1.1.0509.1
Build number
IMM76D.UI23ED22_ACE​Thanks for the help!
Click to expand...
Click to collapse
So you were able to load CW but when you select "Choose from SDCard" it could not find su.zip? Or did you try to Mount your SDCard? Regarding the ADB Commands you can take as much time as you want. Have you used CW before?

swiss420 said:
So you were able to load CW but when you select "Choose from SDCard" it could not find su.zip? Or did you try to Mount your SDCard? Regarding the ADB Commands you can take as much time as you want. Have you used CW before?
Click to expand...
Click to collapse
I did try to mount the sdcard, but I got an error that said it could not mount the sdcard. That is when I tried the sideload method. When I boot up normally, the sdcard is there along with su.zip. I posted the info on my DA220HQL noting the kernel version. I went back to the post where you stated your kernel version. They are different. Mine is later than yours.
After going through everything several times, I though maybe I was doing something wrong. We went out of town so this is the first time I could sit down and check out the posts.
Thanks for your help in advance.

Thanks for all the help. I could not get this to root so we are sending it back to HSN. As a last ditch effort, I did a factory reset and tried again. And I got the same result. I do not think that the recovery while booted was able to "see" the device's partition at all, which is why I got the mount errors. In any case, I also have found that we can find it online for much less than what HSN charged us for it. I am still curious if anyone else was able to root this little gem.
Keep posting updates!

im getting the same issue
cwm is not mounting my sdcard
android is recognizing it, but not in recovery
I'm thinking I shouldn't have installed that update
there are a bunch of errors in recovery when starting
E:Can't open /dev/block/platform/omap/omap_hsmmc.1/by-name/misc (No such file or directory)
E:Can't mount /cache/recovery/command
E:Can't open /dev/block/platform/omap/omap_hsmmc.1/by-name/misc (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't open /dev/block/platform/omap/omap_hsmmc.1/by-name/misc (No such file or directory)
my best guess is we need a different recovery img, even though acer is the same as viewsonic
also there is no prompt to disable stock recovery being reinstalled
recovery touch is also kind of wack, have to tap below whatever I want to pick (which is also not consistent horizontally)
edit: going back to recovery, under mounts and storage, it doesn't appear to have permission to mount anything

looks like viewsonic released a rooted ROM on their support site
http://www.viewsoniceurope.com/uk/support/downloads/drivers/?prod_name=vsd220
But yeah...Acer hasnt
Perhaps this should get the ball rolling? It's funny how the US site doesn't have that
edit: wow looks like they even provided flashing tools and instructions...I just hope that this doesn't brick my unit (since its Acer not Viewsonic)...anyone else willing to give it a try?

ADB won't recognize phone/bootloader/Can't replace recovery HELP!

So basically I found out just today we have Cyanogenmod 10.2 >.<
I downloaded the Joilaroi version, flashed it in TWRP 2.6xx and then suddenly "E: Error in updating binary script" did a bit of googling and found out that it's a common problem with TWRP > 2.3.3.0
So I was about to downgrade it to 2.3.3.0 or temp boot into CWM. Connected my phone to my laptop and went to bootloader, then did Adb devices....the list was empty.
Reinstalled HTC drivers, used different USB port...nothing.
TL;DR : Phone doesn't get recognized in Bootloader mode, Can't flash ROM, Can't replace recovery. Help!

AIndoria said:
So basically I found out just today we have Cyanogenmod 10.2 >.<
I downloaded the Joilaroi version, flashed it in TWRP 2.6xx and then suddenly "E: Error in updating binary script" did a bit of googling and found out that it's a common problem with TWRP > 2.3.3.0
So I was about to downgrade it to 2.3.3.0 or temp boot into CWM. Connected my phone to my laptop and went to bootloader, then did Adb devices....the list was empty.
Reinstalled HTC drivers, used different USB port...nothing.
TL;DR : Phone doesn't get recognized in Bootloader mode, Can't flash ROM, Can't replace recovery. Help!
Click to expand...
Click to collapse
Why don't you flash with terminal emulator?
Just put recovery.img in the root of your sdcard
Open terminal type
su
cd sdcard
flash_image recovery recovery.img
That's it
Sent from my gt-1900 using xda premium

Taha Haq said:
Why don't you flash with terminal emulator?
Just put recovery.img in the root of your sdcard
Open terminal type
su
cd sdcard
flash_image recovery recovery.img
That's it
Sent from my gt-1900 using xda premium
Click to expand...
Click to collapse
That's what I'm doing now but I need a proper solution :/ Basically Windows won't recognize my phone through fastboot. I'd rather not keep installing CM9 again and again after a failed flash, you know?

AIndoria said:
That's what I'm doing now but I need a proper solution :/ Basically Windows won't recognize my phone through fastboot. I'd rather not keep installing CM9 again and again after a failed flash, you know?
Click to expand...
Click to collapse
install htc drivers and make dure you cleared the all registry and files from your previous installation and connect your device
open cmd and go to the folder where you placed adb and type command
adb kill-server =>it will close all adb processes running at that time
adb start-server => it will start new adb process
adb devices=> to reconize your device
if it shows your device then through fastboot command flash the recovery
but make sure you have all neccessary binary files in that folder for adb and fastboot
hit thanks if helped

AIndoria said:
That's what I'm doing now but I need a proper solution :/ Basically Windows won't recognize my phone through fastboot. I'd rather not keep installing CM9 again and again after a failed flash, you know?
Click to expand...
Click to collapse
You can try installing the newer Drivers.
Else your usb port may be broken. that is also a possiblity

[Q] USB connection issues

So, I unlocked bootloader, flashed cwm, now I cant copy ROM to the phone, problem is phone DOES connect, the drive shows up, I can open it to see the existing folders inside. But I cant copy/delete anything to it. Its like its on read only permission.
On windows 8.1 I cant find any option in the properties to change permission.
Same with windows 7, no option to change the permissions.
On linux mint there is the option to change permissions, but sadly they wont change.
I have tried connecting both via the ROM itself and the cwm > mounts and storage > mount usb storage. Same result either way.
I have also tried pushing files via ADB, the process never completes.
Well, if it were usb issue, it wont even let me see the current files inside, so i am at a loss now. Thats all I could think of. Tried it on 2 laptops and one pc already.
Any suggestions?
Right now transfering ROM via bluetooth. But its taking mighty long (obviously).
EDIT: Nopes, cant do anything. It wont flash any other recovery now, in fastboot after the 'fastboot flash recovery........" it says "out of memory" if not that, it just hangs and does nothing.
Via terminal emulator it does not recognize flash_image
and cant flash rom unless i update the recovery.
So right now the priority is to update recovery, anybody know of any other terminal emulator command? ROM manager is not recognizing the current cwm recovery. and there was RASHR says done, but when i reboot its still the same old recovery.
Edit:
So I found this:
Theonew said:
Do:
Code:
fastboot erase recovery
Then reflash recovery.
Click to expand...
Click to collapse
Any ideas? Will this help with the out of memory issue?

I erased the recovery now I am getting this...
C:\Users\fasih\Desktop\asdsadasdsa\NexusS_files\NSFiles>fastboot flash recovery
ttw.img
< waiting for device >
sending 'recovery' (5572 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 0.251s
First of all thanks to the 68 viewers of this thread I managed to solve it, after 2 lappy's and 1 pc and 3 cables I found that the cables were all faulty, just got a new one and it solved the problem. Thanks for bearing with me guys.

[Q] Moved contents of /data/data only level up, now can't unlock my screen.

Hi,
I've CM12 on Xperia L, by mistake I moved all folders of /data/data one level up. Now phone boots-up normally but I don't see unlock pattern. I'm receiving notifications beeps but unable to access my phone.
Please suggest how may I move back folder to correct folder. I don't have any critical files on phone.
USB Debugging is disabled on my phone so i cant use adb.
I tried to use Cyanogen Recovery to apply update but it failed with some errors of signature and footer.
I tried to flash CWM but installer stuck on "waiting for device"
I checked "adb devices", it says "unauthorized" maybe its not allowed root access.

shznaqvi said:
Hi,
I've CM12 on Xperia L, by mistake I moved all folders of /data/data one level up. Now phone boots-up normally but I don't see unlock pattern. I'm receiving notifications beeps but unable to access my phone.
Please suggest how may I move back folder to correct folder. I don't have any critical files on phone.
USB Debugging is disabled on my phone so i cant use adb.
I tried to use Cyanogen Recovery to apply update but it failed with some errors of signature and footer.
I tried to flash CWM but installer stuck on "waiting for device"
I checked "adb devices", it says "unauthorized" maybe its not allowed root access.
Click to expand...
Click to collapse
pull out battery
wait...
pull in battery
(dont touch powerbutton! dont try to boot)
hold vol - (or + im not sure)
connect phone to pc
if you got blue led.... you are in fastboot mode....
then flash a kernel with cwm via fastboot
then flash a rom via cwm
Sent from my C2105 using XDA Free mobile app

SdtBarbarossa said:
pull out battery
wait...
pull in battery
(dont touch powerbutton! dont try to boot)
hold vol - (or + im not sure)
connect phone to pc
if you got blue led.... you are in fastboot mode....
then flash a kernel with cwm via fastboot
then flash a rom via cwm
Sent from my C2105 using XDA Free mobile app
Click to expand...
Click to collapse
I tried to do that in bootloader mode with Fastboot flash recovery recovery.tar but it didnt help. Here's the output.
E:\SonyXperiaL\files>Fastboot flash recovery recovery.tar
sending 'recovery' (3210 KB)...
OKAY [ 0.140s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.187s
Please tell me:
1. Is the .tar file a kernel? Do i need an .img file?
2. Kernels are phone + model specific? (I've CMW-xperiaL installer with adb commands batch file, that probably works in adb-mode with USB Debugging Enabled.)
3. What will be the correct Fastboot command?

shznaqvi said:
I tried to do that in bootloader mode with Fastboot flash recovery recovery.tar but it didnt help. Here's the output.
E:\SonyXperiaL\files>Fastboot flash recovery recovery.tar
sending 'recovery' (3210 KB)...
OKAY [ 0.140s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.187s
Please tell me:
1. Is the .tar file a kernel? Do i need an .img file?
2. Kernels are phone + model specific? (I've CMW-xperiaL installer with adb commands batch file, that probably works in adb-mode with USB Debugging Enabled.)
3. What will be the correct Fastboot command?
Click to expand...
Click to collapse
omfg oO :
1. tar is not a xperia file...its odin (samsung)stuff... dont touch this oO
2. please go to thunderzap.in/downloads ... download TZ4.15 for xperia L alias Taoshan ... extract boot.img from it...
3.
fastboot flash boot boot.img
our xperia have a boot+recovery partition... we dont got normal recovery
...PLEASE never flash stuff that not SPECIALY for xperia L alias Taoshan
Sent from my Xperia T using XDA Free mobile app

SdtBarbarossa said:
omfg oO :
1. tar is not a xperia file...its odin (samsung)stuff... dont touch this oO
2. please go to thunderzap.in/downloads ... download TZ4.15 for xperia L alias Taoshan ... extract boot.img from it...
3.
fastboot flash boot boot.img
our xperia have a boot+recovery partition... we dont got normal recovery
...PLEASE never flash stuff that not SPECIALY for xperia L alias Taoshan
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Thanks! thunderzap did it.
The recovery.tar file came along with CWM recovery installer. It copies .tar and other .sh files into the /tmp and install those files from phone shell.

shznaqvi said:
Thanks! thunderzap did it.
The recovery.tar file came along with CWM recovery installer. It copies .tar and other .sh files into the /tmp and install those files from phone shell.
Click to expand...
Click to collapse
thats fine for fota recovery check my app at themes and apps section
Sent from my C2105 using XDA Free mobile app