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 black6. 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 up8. 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_ACEThanks 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?
Related
My phone is unlocked and rooted. My problem is that when I go to FASTBOOT MODE, then go into RECOVERY, then when I press 'apply update from /sdcard' it shows nothing in there. So, I just stuck and unable to flash any rom at all. I tried to go into the SD card through my computer to install a ROM so that I have something to flash, but nexus s has only internal storage. Please help?
Hi
Hi, I bought my nexus s, immediately after I tried to root, and failed, this left me in the same situation as you.
You NEED to install the adb drivers, and boot using odin files. It was pretty tricky but i got there in the end, i was bricking it too , but dont worry, there's a 98% chance its not bricked, ill find the files for you now...
Go to mount drives and mount your storage from there. That's what I did.
Right, first of all, boot into the bootloader on your Nexus S, and i'm assuming that all your drivers are working fine because you have already unlocked your bootloader.
Place the files in the zip download inthe following places
WIN32bitOS: Program files/Android/Android-sdk/tools
WIN64bitOS: Program files (x86)/Android/Android-sdk/tools
Next, open a command prompt, and type in the following commands, (C: is your windows installation hard drive letter, leave as default if you dont know what this means)
if your 32bit type this w/o quotes "cd C:/Program files/Android/Android-sdk/tools
64bit "cd C:/Program files (x86)/Android/Android-sdk/tools
and click enter.
Next you want to make sure that your Nexus S is in bootloader mode, connected to your pc.
Type the following.
fastboot flash boot boot.img
[click enter & wait until it says successful]
fastboot flash recovery recovery.img
[click enter & wait until it says successful]
fastboot flash system system.img
[click enter & wait until it says successful]
fastboot flash userdata userdata.img
[click enter & wait until it says successful]
Reboot and you should go into android 2.3
Next time make a nandroid backup in clockwork mod!
Download link : http://www.megaupload.com/?d=GI9P4F5I
cdaly985 said:
Right, first of all, boot into the bootloader on your Nexus S, and i'm assuming that all your drivers are working fine because you have already unlocked your bootloader.
Place the files in the zip download inthe following places
WIN32bitOS: Program files/Android/Android-sdk/tools
WIN64bitOS: Program files (x86)/Android/Android-sdk/tools
Next, open a command prompt, and type in the following commands, (C: is your windows installation hard drive letter, leave as default if you dont know what this means)
if your 32bit type this w/o quotes "cd C:/Program files/Android/Android-sdk/tools
64bit "cd C:/Program files (x86)/Android/Android-sdk/tools
and click enter.
Next you want to make sure that your Nexus S is in bootloader mode, connected to your pc.
Type the following.
fastboot flash boot boot.img
[click enter & wait until it says successful]
fastboot flash recovery recovery.img
[click enter & wait until it says successful]
fastboot flash system system.img
[click enter & wait until it says successful]
fastboot flash userdata userdata.img
[click enter & wait until it says successful]
Reboot and you should go into android 2.3
Next time make a nandroid backup in clockwork mod!
Download link coming in 9 mins... data uploading
Click to expand...
Click to collapse
hi cdaly, can you point me to some information on how to install nandriod backup and making/restore a backup right after installing CWM (right after "unlocked" but didnt install Super user yet)?
Yeah
Yeah sure,
Root your phone, go to market place, download rom manager. Open the app and click the button that says, Fash Clockwork Recovery.
Shut down your phone when the operation has completed. Go inot bootloader mode, click recovery. Navigate to backup and restore. Go into backup and restore, click backup. Voila.
If you ever need to restore do the same but click restore. Pretty simple when you know what to do
If this has left you confused, look around on XDA/google, there are a ton of guides
Link added!
Thanks, appreciate it.
Thanks for that. I am using mac computer. Would it be the same typing command for mac as you had mentioned?
cdaly985 said:
Yeah sure,
Root your phone, go to market place, download rom manager. Open the app and click the button that says, Fash Clockwork Recovery.
Shut down your phone when the operation has completed. Go inot bootloader mode, click recovery. Navigate to backup and restore. Go into backup and restore, click backup. Voila.
If you ever need to restore do the same but click restore. Pretty simple when you know what to do
If this has left you confused, look around on XDA/google, there are a ton of guides
Link added!
Click to expand...
Click to collapse
Thanks very much cdaly.. I am just a bit confused regarding phone is rooted or not.
I got to the point flash recovery was sucessfuly in command prompt, but when i try to install "su-2.3.6.1-cd-signed.zip" from SD card, it wasn't successful, as in there is no "superuser" icon after reboot and i have tried wifi tether and it says my phone is not root.
Now i havent tried "su-2.3.6.1-ef-signed.zip" because i accidently bricked my phone for some stupid things i did. but my phone is NOT root as long as I don't see the superuser program right?
I thought nandroid is an actual program but it just means backing up through bootloader?
Thanks for all your help!!!
Thanks very much cdaly.. I am just a bit confused regarding phone is rooted or not.
I got to the point flash recovery was sucessfuly in command prompt, but when i try to install "su-2.3.6.1-cd-signed.zip" from SD card, it wasn't successful, as in there is no "superuser" icon after reboot and i have tried wifi tether and it says my phone is not root.
Now i havent tried "su-2.3.6.1-ef-signed.zip" because i accidently bricked my phone for some stupid things i did. but my phone is NOT root as long as I don't see the superuser program right?
I thought nandroid is an actual program but it just means backing up through bootloader?
Thanks for all your help!!!
Click to expand...
Click to collapse
I dont know if NANDROID is a program or not, it just use it via clockwork mod recovery menu and it works so I'm not complaining aha
If you want to root your nexus s, download this zip file and extract, make sure that your nexus s is in bootloader mode and double click "install-superboot-windows" Bingo, you have root.
Thanks for that. I am using mac computer. Would it be the same typing command for mac as you had mentioned?
Click to expand...
Click to collapse
It wouldn't hurt to try but I dont think so. If you can go into boot-camp or use a friends PC. Or you can try this.
Change your folder to the plaform-tools folder. I dont know how to do this, just referencing off of http://rootzwiki.com/wiki/index.php/Samsung_Nexus_S
Next type
"./fastboot flash boot boot.img"
"./fastboot flash recovery recovery.img"
"./fastboot flash system system.img"
"./fastboot flash userdata userdata.img"
Hi cdaly985
I'd tried it and it works 100%. And, just to share for mac to add on the command "./fastboot-mac ....". I am really impressed with your help. Thanks very very very much.
Hi cdaly985
Now everything is ok with the phone except that it won't be able to go into recovery mode. I had tried by using Rom manager v.4.. and also by pressing vol + power, all failed.
Please help me on this problem. Thanks.
Hi! I was trying to backup my Orange Monte Carlo following a Portuguese tutorial but I'm stuck in the middle and I've got no help! Hope you can provide some! These are the steps I followed (translated)
1 - Install ADB Made Easy;
2 - Open cmd;
3 - Activate cellphone debug mode;
4 - Connect via usb (without mass storage) and install drivers if request [it was requested and i installed];
5 - Run adb devices, it should show your device [it did];
6 - Run adb reboot bootloader, your cellphone will boot in Fastboot, wich is an Android image without menus [correct until here];
7 - Run fastboot devices, your device yor a question mark(?) should show up (advance to next step), else you miss drivers [step not completed];
cmd says 'fastboot' is not recognized as a command. Now my phone is stuck connected to the computer with an adriod pick and I have no clue on what to do next!
Don't know where you were going with this but to reboot your phone just pull the battery ..
Not bricked
shanman-2 said:
Don't know where you were going with this but to reboot your phone just pull the battery ..
Not bricked
Click to expand...
Click to collapse
Thank you! Do you have any idea why the last command doesn't work? I believe it has something to do with file location... I'm trying to backup my Monte Carlo. Next steps were to "fastboot boot recovery.img" and then backup.
It should be in the platform-tools directory of the android-sdk. Verify that it's there...if so cd to that directory and it should work
I already fixed it for myself, thanks! Now I can't seem to be able to install clockwork!
Doing <<fastboot boot "C:\Users\R&J\Downloads\recovery.img">> reboots the device but doesn't enter recovery.
Doing <<fastboot flash recovery "C:\Users\R&J\Downloads\recovery.img">> , <<fastboot reboot>> and <<adb wait-for-device reboot recovery>> results the phone entering android's default recovery (no acess to backup feature).
Any way to help? Thank you!
The first command <<fastboot flash recovery "C:\Users\R&J\Downloads\recovery.img">> is trying to write the recovery.img you downloaded to a recovery partition on your device. It may not be overwriting the original recovery.
try changing permissions by doing
adb shell
su
chmod 777 /recovery
then try to flash again
Lol it seems like I have been luck enough to solve my own problems, I have sucessfully installed ClockworkMod Recovery 4.0.1.4 unofficial MoDaCo Edition using a bat file . Now I can't seem to find a way to flash recovery back to stock. I though this was an option inside the modded recovery. Any tips? Thanks again!
EDIT: I have the stock recovery file . God... this tutorials I'm folowing aren't that noob friendly...
I rooted, and loaded cm9 rom. I prefer stock rom but when I restored my backup there was no wifi (apparently a common issue). Anyway, I am looking for a way to get back to stock rom. I downloaded firmware from Asus but dont know if that is what I need or what to do with it. I am using the twrp recovery
Thanks for any help
All you have to do is download the full Asus ZIP from my thread and flash in CMW and it will restore your fully stock ROM without recovery
http://forum.xda-developers.com/showthread.php?t=1680570
ok thanks now to figure out how to get cwm into my tablet-- right now trying to install sdk
i installed something called eclipse.. I plug in tablet and get to fastboot mode then-- nothing happens- anyone know how one "flashes". Obviously techno noob here
this worked
Terminal Emulator Method
Install Android Terminal Emulator on your tablet.
Download the ClockworkMod Recovery image file directly to your tablet, preferably in the root of the /sdcard directory. Take note of where the file is saved. Rename the file to cwm-touch.blob.
Launch Android Terminal Emulator on your tablet.
Enter the commands below. If you did not save/move/copy the image file to the /sdcard directory, you need to replace /sdcardin the second command below with the correct directory where you saved the recovery image file to.
su
dd if=/sdcard/cwm-touch.blob of=/dev/block/mmcblk0p4
Reboot your tablet. The blob file will be automatically installed as your tablet reboots.
voodoo_dr said:
i installed something called eclipse.. I plug in tablet and get to fastboot mode then-- nothing happens- anyone know how one "flashes". Obviously techno noob here
Click to expand...
Click to collapse
You can uninstall Eclipse. It has nothing to do with Android or flashing anything. It's an Integrated Development Environment, which is kind of like a word processor for programmers. The only relation it has to Android is that it supports the Java programming language, so a lot of Android developers use it. If you're not going to be writing apps or messing with Android source code, it's probably best if you uninstall Eclipse, just because you won't use it, and it's taking up storage space.
Also, what were you expecting to happen when you put the tablet in fastboot mode? It just opens up a serial connection with a host (in this case, your computer) and allows the host to access the tablet via fastboot (sounds confusing, I know; it's not particularly fast, and doesn't have much to do with booting anything; it's like ADB but for low-level [hardware] flashing) and run commands. The tablet itself does nothing except display the message that it's in fastboot mode. Once the tablet says that, you run fastboot on the computer.
thanks for the reply. Now I have a brick---tried to install stock rom and hangs on asus with the wheel going round and round. It deleted my cwm so now no recovery on tablet. When I go into fastboot, it doesnt seem to recognize my tablet adb devices--nothing comes up
In my device manager I see no adp drivers- the only driver which keeps installing when I plug in the tablet and go to fastmode is the asus bootloader interface so I cant do anything with the tablet--- no recognition of device with adb devices command Help please
If you're in fastboot, ADB won't recognize the tablet. You need to use the fastboot commands with fastboot.
What to do:
-download the CWM blob on your computer
-put the CWM blob in the directory on your computer with the fastboot program
-boot the tablet into fastboot, and flash CWM
-boot into CWM, and restore the nandroid backup you should have made.
Alternately, if you didn't make a nandroid backup, you can boot into recovery, push the Asus stock ROM to /sdcard on your tablet via ADB (I'm assuming ADB works in the stock recovery), then reboot into recovery, and it should flash the update automatically. This will erase ALL your data, including /sdcard.
is cwm blob recovery.img?
I'm not sure if flashing .img files works with this tablet, but you could try. If it doesn't work, go to the place you got the recovery (as long as it's not from ROM Manager, and you're positive it's not the TF201's recovery), and there should be a file that ends in .blob. That's the one you need.
then I just place it in the same directory and click on fastboot? or is there more to it? seems to be having trouble with drivers mtp driver not installing???
I don't use Windows, so I don't know about the drivers. There's a thread in the development section with all the Windows drivers you need, though.
You put the blob in the directory where fastboot is. You open the command line (open Run, and type "cmd" [no quotes]) and run the fastboot command from there.
got it thanks cwm is back
i have a slight problem. i grabbed the ubuntu touch alpha and went in to recovery, loaded it (according to thread instructions) but ended up with a bootloop.
in the end i thought "lets just put another rom back on for now" and then realised i had deleted the other rom from the sdcard! so i'm stuck with it not booting in to ubuntu, and not able to get another rom on as it doesn't boot in.
can i connect to the internal sdcard area myself by plugging the usb in to the pc or something?
i have twrp loaded as recovery
thanks
ah, TWRP adb sideload to the rescue!
problem
my problem is stuck in boot screen after i did super wipe full what should i do? i have cwm 5.5.0.4. i try flash from sd put it says no files found
partti86 said:
my problem is stuck in boot screen after i did super wipe full what should i do? i have cwm 5.5.0.4. i try flash from sd put it says no files found
Click to expand...
Click to collapse
The issue, Superwipe wipes the internal /sdcard/ and also this is where it flashes from.
You need to boot to recovery and then use ADB to push files to the sdcard.
If you have never used ADB, it can be a bit daunting.
First, you need adb from the Android SDK. It is a big file for the few you need. I have a copy of the relevant ADB files here: https://db.tt/b9dQ6xzp
Unzip this to c:\adb folder on windows. If you are using Linux, it should already have adb in the /usr/bin/ folder.
Next, you need the Universal Naked Drivers: http://forum.xda-developers.com/attachment.php?attachmentid=1934814&d=1367674531
Unzip these to c:\universal_naked_drivers
Boot to CWM and then plug in your USB cable. It should show a new device found. It may find 2, an MTP and then there should be another either Unknown device or an Android ADB device. Right click and update the driver. Be sure to search for driver, then tell it you want to pick from a list. Hit the Have Disk button and then hit the browse button and browse to c:\universal_naked_drivers and hit OK. It should show you a driver to select and hit OK. If you are using Win 8, there is an additional step that is required to used non-signed drivers.
Once the driver is updated, download the zip file you want to flash on your PC. I assume it is a ROM.zip file for this example. Place this file in the c:\adb folder and call it ROM.zip (can be named something else, but this is what we will use for this example).
Now, open a command prompt and execute the following:
Code:
> [B]c:[/B]
c:\> [B]cd c:\adb[/B]
c:\adb> [B]adb devices[/B]
It will probably say some messages about the daemon is not running, restarting adb.
Then it should show a list. There should be some numbers followed by "recovery"
If no devices are shown, check that your ADB device is showing in the Device Manager.
Once you see it in the adb devices list, continue:
Code:
c:\adb> [B]adb push ROM.zip /sdcard/[/B]
successfully pushed xxx bytes
c:\adb>
At this point you should now see the ROM.zip file on the internal storage in CWM to allow you to install it.
Choose to install the file then reboot (not to recovery). You have to let it flash the file (progress bar will show). Once the screen goes black and the progress bar disappears, it should now boot to your ROM..
If your ROM requires a custom kernel and/or GAPPS to be flashed, use the same procedure to push your kernel.zip and GAPPS.zip to the /sdcard/ directory.
mk2media said:
ah, TWRP adb sideload to the rescue!
Click to expand...
Click to collapse
Can you explain what you did please? what is adb sideload?
Update: When you flash the recovery and supersu files make sure to have the remove encryption file on sd card aswell and add it to the list and flash and if you hang at boot screen.. boot into recovery and wipe cache.. reboot.
WINDOWS USERS ONLY.... USE AT YOUR OWN RISK
Make sure you have the proper drivers and make sure you have a real good usb cable... This rar has the usb drivers and the files already in the folder just drop onto desktop and run cmd.exe
Files Needed: http://www.filedropper.com/nocturnaladbfastboot
http://www.filedropper.com/removeencryption
DO NOT FORMAT SYSTEM!!!!!!!!!!!!!
Make sure you are in bootloader or this will not work..
Key combo to get into bootloader or recovery via hard keys.
power off
volume up + power = recovery
volume down + power = bootloader
from bootloader you have several choices to boot, just pres volume down to choose, power to select.
1. To make sure you are connected run command (adb devices) enter
2. Once you see your device run command (adb reboot bootloader) Then..
3. Run command (fastboot boot boot.img) wait for downloading dialog...
4. Then run command (fastboot flash recovery twrp_recovery.img) and make sure you have the proper files on sd card.. i put all files in the folder on my sd card to make sure...
5. once the screen says okay on tablet.. push the vol down button until you see recovery mode and then push power to start twrp recovery..
6. Once in twrp flash SuperSU246.zip and recovery.zip remove_encryption.zip then reboot... you should have root on reboot:good:
Instructions
I think I understand your instructions but I have a few questions.
Am I typing all of the commands on my pc? (- SuperSU)
Step 3 has “Run command “(fastboot boot boot.img)” I see 2 files and so those are two separate commands to run correct?
Step 4 Then run command (fastboot flash recovery twrp_recovery.img) and make sure you have the proper files on sd card.. i put all files in the folder on my sd card to make sure... Again is this 2 commands to run? I see the twrp_recovery.img file but no fastboot flash recovery file?
In step 4 should I be using theses 2 commannds;
fastboot flash boot boot.img
fastboot flash recovery recovery.img
ahunter said:
I think I understand your instructions but I have a few questions.
Am I typing all of the commands on my pc? (- SuperSU)
Step 3 has “Run command “(fastboot boot boot.img)” I see 2 files and so those are two separate commands to run correct?
Step 4 Then run command (fastboot flash recovery twrp_recovery.img) and make sure you have the proper files on sd card.. i put all files in the folder on my sd card to make sure... Again is this 2 commands to run? I see the twrp_recovery.img file but no fastboot flash recovery file?
In step 4 should I be using theses 2 commannds;
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
run them just as there posted make sure all files on the sd card and you should be fine..
Thanks for your reply. Those commands are run on the PC in the cmd window right? and I copied the files in the directory to my SD card I installed on the nextbook should that be a problem. Shoul this be the SD card or internal memory? I didn't run the commands the way they were written last night & didn't have success. I am getting hung up on 3. Run command (fastboot boot boot.img) wait for downloading dialog...
My pc and tablet are seeing eachother but they both say waiting, I don't think my files are being seen.
ahunter said:
Thanks for your reply. Those commands are run on the PC in the cmd window right? and I copied the files in the directory to my SD card I installed on the nextbook should that be a problem. Shoul this be the SD card or internal memory? I didn't run the commands the way they were written last night & didn't have success. I am getting hung up on 3. Run command (fastboot boot boot.img) wait for downloading dialog...
My pc and tablet are seeing eachother but they both say waiting, I don't think my files are being seen.
Click to expand...
Click to collapse
Make sure you uninstall and reinstall the usb drivers in the folder and run the cmd from the folder and if still nothing try a new cable and usb port... when you run command adb devices do you see your listed as numbers and some letters?
After the adv devices command it gives me; listed devices YFGV0815002950 device. That should be the tablet, it’s the only thing attached w/usb & it also shows up in explorer.
After the adb reboot bootloader cmd the tablet reboots into bootloader with “Fastboot CMD WAITING “ at the bottom of the screen.
After the fastboot boot boot.img cmd my pc cmd rompt says <waiting for device> and my tablet stillhas the Fastboot screen mode & FASTBOOT CMD WAITING at the bottom of the screen
That is as far as I get. I copied all of the files in your download link in the .rar format and to a directory on my internal tablet storage. It seems like the tablet is waiting for a file but I don't understand why.
ahunter said:
After the adv devices command it gives me; listed devices YFGV0815002950 device. That should be the tablet, it’s the only thing attached w/usb & it also shows up in explorer.
After the adb reboot bootloader cmd the tablet reboots into bootloader with “Fastboot CMD WAITING “ at the bottom of the screen.
After the fastboot boot boot.img cmd my pc cmd rompt says <waiting for device> and my tablet stillhas the Fastboot screen mode & FASTBOOT CMD WAITING at the bottom of the screen
That is as far as I get. I copied all of the files in your download link in the .rar format and to a directory on my internal tablet storage. It seems like the tablet is waiting for a file but I don't understand why.
Click to expand...
Click to collapse
there is a problem after you boot into bootloader i had the same problem for days.. i just played with cables and drivers use the ones inside the folder they worked for me...
I'll keep trying. It has be the drivers.
I followed these directions to a T, but for some reason the device can not read the SD card while in recovery. Any clues as to why this is happening?
So I was online shopping for my first tablet when I came across this thread. . . It led me down to the local WALMART and I picked one up. I successfully completed the process, or so I thought. I went to reboot after flashing everything, and twrp says " no OS installed! Are you sure you want to reboot?"
What did I do wrong?
I have tried several times to download the remove encryption file must be a bad link or something. Is there another download site or can someone send to me plz
Nvm I ran it over with my car because I couldn't get the download link to work. If anyone wants it for parts send me a message. Its brand new only been used maybe 2 weeks. The most wear and tear on it was my Buick regal hitting it at about 45 mph in a pissed off rage. don't think all the insides are smashed tho. Possibly a good fixer upper
Is this fastboot and adb custom versions?
I have adb and fastboot in my path (runable from anywhere)..
ADB says the version release is the same number.
do I need to use your versions for the tablet?
http://www.filedropper.com/removeencryption
does not work, link changes to http://www.filedropper.com
and asks me to upload a file?
Link working sorry...
http://www.filedropper.com/roottwrpremoveencryption
TWRP 3.0
http://www.filedropper.com/twrp3recovery
C:\Users\Fuzzy\Desktop\root_twrp_remove_encryption>fastboot flash recovery twrp_
recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (15558 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 0.320s]
finished. total time: 0.830s
C:\Users\Fuzzy\Desktop\root_twrp_remove_encryption>
Copied the two zip files to both a 4gb fat32 formatted microsdhc
and internal storage via MTP to the device then ran ADB 1.0.32
and rebooted to bootloader. (adb finds device fine)
fastboot devices reported device number fastboot.
flashed TWRP in package you uploaded yesterday.
it says both internal and external cards are empty?
internal card has files that the manufacturer put there,
but TWRP can't see them?
What am I doing wrong?
Any ideas how to fix?
log says 'unable to find crypto file'
and it couldn't mount /data or /storage filesystems
>>>
installed TWRP3 that allowed the installs although it still
could not open /data. It did find the external card installed
from there.
I am guessing the forced encryption made /data unreadable.
hopefully now with the encryption removed the /data
partition will be readable.
>>>
I reran recovery to check and log now has no failures!!!
I'm guessing the changed boot.img fixed the issues it was having.
*smiles*
cant get files. takes me to a site to sign up. can you dropbox link them please?
I just won this tablet in a contest. Anyone have the remove_encryption.zip file? I managed to find all of the other required files but none of the links in this thread work anymore.
whats the problem with the links? site says free but wants me to pay. losing my head here, and it seems im not the only one
Bad filedropper links
Filedroper no links available, asks us to register and pay for stuff that's not there anymore
can you like put them on Google drive, SendSpace, DropBox, Mega.nz and/or ZippyShare