Related
i have already checked xda for a solution but couldnt find one i even checked google and youtube and still found nothing i am in need help bad. i will even pay someone paypal if they can help me with my phone
i downloaded the matrix rom and i liked it but i wanted to go back to ice cream sandwhich for the day so when i tried to go to recovery it froze on the google screen while trying to get to recovery i kept trying and trying but my recovery wasnt working i couldnt get to it. so i went to titanium back up and clicked un-install all system and data because i thought it was when i restored all system and data from ICS but after i did the uninstall i kept getting a force close alot of things and i got all the way down to one and it was process.android i think and everytime i clicked force close it popped right bacj up instently. so i took out the battery and put it back in and now i cant power on my phone it gets stuck on the matrix screen. can you please help me i can only acces the volume up power button menu.
*solved*
Fastboot OEM lock. Fastboot OEM unlock and start the process all over again. Also wipe everything 3 times.
Including system and boot.
Also double check you're installing all the compatible zips.
Sent from my Nexus S using xda premium
it wont let me do any of that it keeps saying waiting for device then gets stuck on that ive installed pdanet but it keeps giving me a htc sync error =1 and my bootloader and everything was already unlocked i dont know what to do i cant turn my phone on or get to recovery. thats why im paying 100 dollars to anyone who can help me restore my phone and make sure its up and running ive been trying for 2 days now and thats my work phone and everything im stressed
Serious_Beans said:
Fastboot OEM lock. Fastboot OEM unlock and start the process all over again. Also wipe everything 3 times.
Including system and boot.
Also double check you're installing all the compatible zips.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
when i turn on the phone and it keeps trying to load the matrix animation the phone still connects with my computer and says removable disk f but when i try and click on it. it says please insert a disk into removable disk f
Hmm uninstall all the USB drivers and reinstall them
Sent from my Nexus S using xda premium
Serious_Beans said:
Hmm uninstall all the USB drivers and reinstall them
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
at the bottom of my phone screen it says fastboot statud - FAILInvalid command
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Make sure you are using the most up to date drivers and then use ADB to install recovery again. If I'm understanding it right I think that's what you need to try.
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Envynet said:
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Click to expand...
Click to collapse
can someone help me threw team viewer and just access my computer threw that and help me that way
Envynet said:
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Click to expand...
Click to collapse
Dang you must have put this up like 2 second before I posted mine lol
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Maybe you should just try Odin.
http://forum.xda-developers.com/showthread.php?t=1022481
DL: http://droidangel.blogspot.com/2011/05/odin-multi-downloader-flasher-program.html
Greetz
OP... check your PM inbox.
Why on earth have you posted this thread 6 times? Lol
Sent from my Nexus S using XDA App
scottypeterson said:
Dang you must have put this up like 2 second before I posted mine lol
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Click to expand...
Click to collapse
after i type adb it says adb isnt recognized as a internel or external cammand operable program or batch file
Ok I don't know if you tried this already but do this:
1. download the recovery img from here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and put it somewhere on ur computer
2. plug phone into comp
3. boot the phone into the fastboot mode with the android guy
4. fastboot erase recovery
5. fastboot flash recovery ____.img
and if you can boot into recovery now, just wipe data, cache, and dalvik cache and flash the ics rom
see if that helps
mathkid95 said:
Ok I don't know if you tried this already but do this:
1. download the recovery img from here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and put it somewhere on ur computer
2. plug phone into comp
3. boot the phone into the fastboot mode with the android guy
4. fastboot erase recovery
5. fastboot flash recovery ____.img
and if you can boot into recovery now, just wipe data, cache, and dalvik cache and flash the ics rom
see if that helps
Click to expand...
Click to collapse
I suggested this about 7 hours and 3 threads ago.. I think the problem is either he doesn't have the proper drivers or SDK setup properly.
Da_Reaper said:
after i type adb it says adb isnt recognized as a internel or external cammand operable program or batch file
Click to expand...
Click to collapse
This leads me to believe that SDK isn't set up properly. If it's set up correct you should be able to access adb without the phone even connected.
Yes thank you guys i love u all
check your mp , excepted if you found the solution.
$100? Lol
Sent from my Nexus S using XDA App
crump84 said:
I suggested this about 7 hours and 3 threads ago.. I think the problem is either he doesn't have the proper drivers or SDK setup properly.
This leads me to believe that SDK isn't set up properly. If it's set up correct you should be able to access adb without the phone even connected.
Click to expand...
Click to collapse
Yeah excuse me for not reading all 6 threads
Sent from my Nexus S using XDA App
OMG yes i know im a newb but there is a first time for everybody for anything.
So i'm trying to unlock, root, install cwm and install custom roms but ive looked at all the instruction from many thread and a lot of them had missing steps
Anyways, i've downgraded from JB to 4.0.3, rooted, unlocked and now i'm trying to install CWM. So i installed android SDK and all tools, i've put recovery image in same folder as fastboot.exe, i've booted the tablet and selectied USB icon but wtf do i do now??
I'm basically here:
** FastBoot Method **
1) Install Android SDK
2) Download CWM Recovery image from the original thread and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Copy the downloaded file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot into fastboot mode (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
Where do i get this command line?? is it command line from windows such as CMD?? cause if it is, i've tried it and nothing. Do i have to point to where is the recovery image?? Its in C:\Users\Patrick\AppData\Local\Android\android-sdk\platform-tools but i'm lost from that point, i'm not sure what command line i have to use, and how to set it up so i can tell it where to look.
Can anybody help me please?
polish_pat said:
OMG yes i know im a newb but there is a first time for everybody for anything.
So i'm trying to unlock, root, install cwm and install custom roms but ive looked at all the instruction from many thread and a lot of them had missing steps
Anyways, i've downgraded from JB to 4.0.3, rooted, unlocked and now i'm trying to install CWM. So i installed android SDK and all tools, i've put recovery image in same folder as fastboot.exe, i've booted the tablet and selectied USB icon but wtf do i do now??
I'm basically here:
** FastBoot Method **
1) Install Android SDK
2) Download CWM Recovery image from the original thread and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Copy the downloaded file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot into fastboot mode (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
Where do i get this command line?? is it command line from windows such as CMD?? cause if it is, i've tried it and nothing. Do i have to point to where is the recovery image?? Its in C:\Users\Patrick\AppData\Local\Android\android-sdk\platform-tools but i'm lost from that point, i'm not sure what command line i have to use, and how to set it up so i can tell it where to look.
Can anybody help me please?
Click to expand...
Click to collapse
change directory to the folder the recover/fastboot is in, using the CMD on windows. So:
"cd C:\Users\Patrick\AppData\Local\Android\android-sdk\platform-tools"
make sure the recovery is called "recovery.img" and that its in the "platform-tools" folder alongside the fastboot.exe, then run the commands:
"fastboot -i 0x0B05 flash recovery recovery.img"
and
"fastboot reboot"
polish_pat said:
OMG yes i know im a newb but there is a first time for everybody for anything.
So i'm trying to unlock, root, install cwm and install custom roms but ive looked at all the instruction from many thread and a lot of them had missing steps
Anyways, i've downgraded from JB to 4.0.3, rooted, unlocked and now i'm trying to install CWM. So i installed android SDK and all tools, i've put recovery image in same folder as fastboot.exe, i've booted the tablet and selectied USB icon but wtf do i do now??
I'm basically here:
** FastBoot Method **
1) Install Android SDK
2) Download CWM Recovery image from the original thread and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Copy the downloaded file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot into fastboot mode (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
Where do i get this command line?? is it command line from windows such as CMD?? cause if it is, i've tried it and nothing. Do i have to point to where is the recovery image?? Its in C:\Users\Patrick\AppData\Local\Android\android-sdk\platform-tools but i'm lost from that point, i'm not sure what command line i have to use, and how to set it up so i can tell it where to look.
Can anybody help me please?
Click to expand...
Click to collapse
Yes, command line is in your PC. The location of the fastboot.exe located in c:\android-sdk\platformtools (if you install from sdk).
On your PC, open CMD and navigate to the above directory where fastboot.exe is. Make sure your recovery.img in also copied to this same folder. Now you can execute the fastboot comand:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
---------- Post added at 05:52 PM ---------- Previous post was at 05:48 PM ----------
buhohitr said:
Yes, command line is in your PC. The location of the fastboot.exe located in c:\android-sdk\platformtools (if you install from sdk).
On your PC, open CMD and navigate to the above directory where fastboot.exe is. Make sure your recovery.img in also copied to this same folder. Now you can execute the fastboot comand:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
I think it's easier for you to download Voodoo OTA root keeper to preserve root, then upgrade to JB, then use OTA root keeper to restore root. After this you can install TWRP recover by download goomanager from the play store and install it, once you have twrp, you're home free.
Currently you are on ICS, becareful if you use a wrong version of cwm you could brick your device. Many ppl installed ICS cwm version then upgrade to JB without the right version and they bricked.
buhohitr said:
Yes, command line is in your PC. The location of the fastboot.exe located in c:\android-sdk\platformtools (if you install from sdk).
On your PC, open CMD and navigate to the above directory where fastboot.exe is. Make sure your recovery.img in also copied to this same folder. Now you can execute the fastboot comand:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
---------- Post added at 05:52 PM ---------- Previous post was at 05:48 PM ----------
I think it's easier for you to download Voodoo OTA root keeper to preserve root, then upgrade to JB, then use OTA root keeper to restore root. After this you can install TWRP recover by download goomanager from the play store and install it, once you have twrp, you're home free.
Currently you are on ICS, becareful if you use a wrong version of cwm you could brick your device. Many ppl installed ICS cwm version then upgrade to JB without the right version and they bricked.
Click to expand...
Click to collapse
Thanks but I've already downgraded. I'll try what the guy above said thank you for the help
Sent from my SGH-I747M using Tapatalk 2
when you are in the fastboot folder, you have to press control & right click inside the folder, and you will see the option to open a terminal.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Pat,
If it makes you feel any better I had a heck of a time with this myself.
Once I realized I had platform tools in a folder on my PC desktop with the command prompt
in it I was able to flash.
Gotta say it wasn't easy to figure out in bits and pieces.
Sent from the inside out...
Thanks guys, you've been REALLY helpful! I completely forgot about the shortcut to open cmd in a folder, and i'm not sure if you were wrong or its because im on windows 8 but its ctrl + shift + right click
EDIT: now i get a problem, it do all this and i get "waiting for device"
i tried different USB ports, same deal...any ideas?
EDIT: EDIT: tried all USB port but one, the last one i used did the trick, thanks for all!
I'm having this exact same problem but changing USB ports is not working for me and I tried everything else. Would it help if I tried a different computer?
Sent from my Galaxy Nexus using xda app-developers app
mnk0ota said:
I'm having this exact same problem but changing USB ports is not working for me and I tried everything else. Would it help if I tried a different computer?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
try to open CMD as Administrator.
buhohitr said:
...
I think it's easier for you to download Voodoo OTA root keeper to preserve root, then upgrade to JB, then use OTA root keeper to restore root. After this you can install TWRP recover by download goomanager from the play store and install it, once you have twrp, you're home free.
Currently you are on ICS, becareful if you use a wrong version of cwm you could brick your device. Many ppl installed ICS cwm version then upgrade to JB without the right version and they bricked.
Click to expand...
Click to collapse
I don't mean to threadjack, but this portion of your post caught my attention.
I just swapped a prime for an infinity. I rooted, installed rootkeeper, preserved root, upgraded to JB and restored root.
Are you saying I can install goomanager and update recovery without unlocking via the Asus tool?
If so, sweet!
Sent from my MB855 using Tapatalk 2
John Kotches said:
I don't mean to threadjack, but this portion of your post caught my attention.
I just swapped a prime for an infinity. I rooted, installed rootkeeper, preserved root, upgraded to JB and restored root.
Are you saying I can install goomanager and update recovery without unlocking via the Asus tool?
If so, sweet!
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
No. You will still have to unlock the bootloader to install a custom recovery, unfortunately.
Firebrazer said:
No. You will still have to unlock the bootloader to install a custom recovery, unfortunately.
Click to expand...
Click to collapse
Thanks... if it seems too good to be true it probably is.
Sent from my MB855 using Tapatalk 2
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?
I had a problem now and i am not found the solution. I bricked my phone after Full wipe
sorry for my bad english.
Phone is: HTC ONE S (s4)
super cid, unlocked, rooted, hboot 2.16, radio 1.35a
recovery: TWRP 2.7.x
last rom before i full wipe; viperOneS 3 (4.2.2) and before i installed the kernel maximus hd 's kernel
Pls not send me the link; because i try to everything to i found the forum links/posts. i search to forums for 4-5 hours no result for my kind of problem
Now: i can't flash rom and i phone not open
what i did ?
1. adb reboot-bootloader and open the Recovery (TWRP 2.7.x)
2. I do Full Wipe; Factory Reset, Wipe Cache, data, system, dalvik & format Data menus
3. my rom zip is gone on the SD CArd. ok it's normal. i need to recopy rom.zip to sd card
i think ; flash the rom via sideload / adb push methods. WTF ! 2 options are not work for some errors.
Problems;
ADB Sideload feature ; error device not found. i investigate the problem and i see the Phone driver not installed on the Windows. (win 8.1.1)
Device Manager look; One S (unknown device)
EDIT: i try on the Windows 7 laptop but result is same. windows doesn't recognize the phone when the Recovery Mode. and i can't sideload feature
Ok , i try to push .
Phone is start screen but no start because no have OS ! but when the mode device manager phone is OK
try this things;
adb push rom.zip /sdcard ERROR : No such file or directory
adb push rom.zip sdcard ERROR : No such file or directory
adb push rom.zip /sdcard/ ERROR: no such file or directory
adb push rom.zip /sdcard/rom.zip ERROR: Is a Directory
adb push rom.zip /data/media/0/ ERROR: Is a directory
bla bla bla i try to every possibilities
i m tired and i think to destroy my phone PLS HELP ME
I arrived at the point; i need to flash rom but how to copy zip to SD card ?
Sorry for my english too xD
I had the same problem last week.
Try to go in bootloader, then in fastboot and connect the device to the PC, from the PC with the Promt go in your adb folder
Code:
cd c:/[I]position of your folder[/I]
then test if adb sees your device with the command
Code:
adb devices
If it's ok then try again to push again the ROM with the command
Code:
adb push [I]name_of_the_file.zip[/I] /sdcard/zip.rom
casu91 said:
Sorry for my english too xD
I had the same problem last week.
Try to go in bootloader, then in fastboot and connect the device to the PC, from the PC with the Promt go in your adb folder
Code:
cd c:/[I]position of your folder[/I]
then test if adb sees your device with the command
Code:
adb devices
If it's ok then try again to push again the ROM with the command
Code:
adb push [I]name_of_the_file.zip[/I] /sdcard/zip.rom
Click to expand...
Click to collapse
thnx man, but when i go to fastboot, ADB devices are empty ? no adb push command work.
fastboot devices command works but did not help me the problem
thanks in other adviseee
natmacax said:
thnx man, but when i go to fastboot, ADB devices are empty ? no adb push command work.
fastboot devices command works but did not help me the problem
thanks in other adviseee
Click to expand...
Click to collapse
Then you should fix the driver problem first, have you tried it with both Win 8.1 and 7?
doesn't work ADB on fastboot mode. both of win 7 and win 8.
BUT in the fastboot mode no driver problem ! i dont understand, you say ; when phone in the fastboot mode, adb push command should work ?
BTW, just now in the fastboot mode, its finally fastboot flash zip rom.zip command works, but *UCKN the new problem occurs
when the write flash command, error : data length is too large!
i investigate this problem now, do you know the problem root cause ?
natmacax said:
I had a problem now and i am not found the solution. I bricked my phone after Full wipe
[..]
i m tired and i think to destroy my phone PLS HELP ME
I arrived at the point; i need to flash rom but how to copy zip to SD card ?
Click to expand...
Click to collapse
In a last try you can simply downgrade your hboot and run last ruu. Then re-uprade your hboot and so
Edit : ADB doesn't work in fastboot mode
benJX said:
In a last try you can simply downgrade your hboot and run last ruu. Then re-uprade your hboot and so
Edit : ADB doesn't work in fastboot mode
Click to expand...
Click to collapse
just now in the fastboot mode, its finally fastboot flash zip rom.zip command works, but i have a new problem
when the write flash command, error : data length is too large!
does have a any solution for this ?
also, you sayed upgrade downgrade hboot.... this is solution of the adb push problem ?
thnx
natmacax said:
doesn't work ADB on fastboot mode. both of win 7 and win 8.
BUT in the fastboot mode no driver problem ! i dont understand, you say ; when phone in the fastboot mode, adb push command should work ?
BTW, just now in the fastboot mode, its finally fastboot flash zip rom.zip command works, but *UCKN the new problem occurs
when the write flash command, error : data length is too large!
i investigate this problem now, do you know the problem root cause ?
Click to expand...
Click to collapse
Sorry if I wasn't clear, what i was saying is that adb push command should work if your adb drivers are working!
benJX said:
In a last try you can simply downgrade your hboot and run last ruu. Then re-uprade your hboot and so
Edit : ADB doesn't work in fastboot mode
Click to expand...
Click to collapse
I think that's a good solution if you can't push the zip with adb commands, I didn't think of that because when I had the problem I did it with the adb command
casu91 said:
I think that's a good solution if you can't push the zip with adb commands, I didn't think of that because when I had the problem I did it with the adb command
Click to expand...
Click to collapse
natmacax said:
also, you sayed upgrade downgrade hboot.... this is solution of the adb push problem ?
Click to expand...
Click to collapse
I'm not sure about what I'm saying but adb sideload doesn't work on recoveries made for hboot 2.16, aswell as mounting sdcard.
When you try to adb sideload from modded recovery for 2.16, it recognizes only 48mb of memory that's why you can't use it. But I repeat I'm not sure about it I never had to use adb sideload.
Edit : And you cannot flash a rom with fastboot. Flashing zip from it has to be done only when you want ot uprgade/downgrade firmware files in ruu mode
benJX said:
I'm not sure about what I'm saying but adb sideload doesn't work on recoveries made for hboot 2.16, aswell as mounting sdcard.
When you try to adb sideload from modded recovery for 2.16, it recognizes only 48mb of memory that's why you can't use it. But I repeat I'm not sure about it I never had to use adb sideload.
Edit : And you cannot flash a rom with fastboot. Flashing zip from it has to be done only when you want ot uprgade/downgrade firmware files in ruu mode
Click to expand...
Click to collapse
IT'S FINALLY OVER
THANKS FOR ALL
i think the problem as you sad, hboot & TWRP version !
i downgrade hboot 2.16 > modded 2.15 (then i try flash rom sideload or pus, via twrp 2.7 didn't work)
then i reflash recovery downgrade TWRP 2.6.3 and all it works
i flash the rom via adb sideload, all it works.
I try to hard reset but I'm still stuck on loading screen. How do I add a zip file to my sd so I can flash it, since it doesn't even detect my oneplus on my computer? Please help me and lend me your knowledge and power =].
Can you boot in bootloader and connect it through adb and fastboo with your pc? in that case it would be easy to reflash everything
I can boot into fastboot and TWRP but I'm wondering how can I add file into my internal hard drive since it doesnt detect the phone on my computer?
Any help with some instructions would be really nice =] :good:
Do you see it using "adb devices" or "fastboot devices" ?
If not, you must update your adb drivers on your computer and reboot it
right now its on MTP USB Device as my device on my Device Manager, can you link me to the proper usb driver? Because I"m pretty sure I updated it and it was working while my phone is working. Also how can I check if its using adb devices?
bud77 said:
Do you see it using "adb devices" or "fastboot devices" ?
If not, you must update your adb drivers on your computer and reboot it
Click to expand...
Click to collapse
Also it said "Windows has determined the driver software for your device is up to date" but doesnt detect my phone?
Anyone still here so they can help me?
So as asked previously, when you connect via fastboot, and boot it into TWRP, do you see it via adb ("adb devices" command in the platform-tools folder)? Did you try adb push <filename> /sdcard/ ?
yes i see adb push , but there's no file there. How can i add file there?
Dzhedaj said:
So as asked previously, when you connect via fastboot, and boot it into TWRP, do you see it via adb ("adb devices" command in the platform-tools folder)? Did you try adb push <filename> /sdcard/ ?
Click to expand...
Click to collapse
Basically i'm in TWRP and i dont see any thing in recover or etc or in my sd, all blank so how can I put an image there to flash?
Anyone still here to have any answers to help?
which jeithis
http://i.imgur.com/378HzRp.png also get this image also
Use an adb push command to send a ROM zip to your phone.
Transmitted via Bacon
@M I N E, go read the sticky posts in the general section. It will explain how to do an adb push command.
@timmaaa and others have done a great job with some write ups for this device.
timmaaa said:
Use an adb push command to send a ROM zip to your phone.
Transmitted via Bacon
Click to expand...
Click to collapse
Or do a factory wipe then go into TWRP -> Advanced -> ADB Sideload -> Swipe
adb sideload <name-of.zip>.zip (ensure the .zip is in the same folder as your fastboot/adb) and then it'll send the zip over to the phone and flash.
I prefer the adb sideload method as it pretty much pushes the file over to the phone and then flashes it afterwards.
Either method is fine though.
If OP has problems with drivers, I recommend using http://forum.xda-developers.com/showthread.php?t=2386956 they work great.
what is the push load command? How can i push something if i dont have any file on my phone to flash? can you guys type out the command?
M I N E said:
what is the push load command? How can i push something if i dont have any file on my phone to flash? can you guys type out the command?
Click to expand...
Click to collapse
Read the post above you that I posted. Use that command as well as the instructions and you can flash a file using adb sideload.
well I try factory swipe nothing there, i check the TWRP , no files is there i mean nothing. And I cant do adb push because my when i type adb devices it doesnt recognized, because how can i turn on debugging if my phone doesnt have any rom?
M I N E said:
well I try factory swipe nothing there, i check the TWRP , no files is there i mean nothing. And I cant do adb push because my when i type adb devices it doesnt recognized, because how can i turn on debugging if my phone doesnt have any rom?
Click to expand...
Click to collapse
You're not reading my message properly. I'm telling you to do adb sideload. Please read what I said carefully word-by-word.
Or do a factory wipe then go into TWRP -> Advanced -> ADB Sideload -> Swipe
adb sideload <name-of.zip>.zip (ensure the .zip is in the same folder as your fastboot/adb) and then it'll send the zip over to the phone and flash.
I prefer the adb sideload method as it pretty much pushes the file over to the phone and then flashes it afterwards.
Click to expand...
Click to collapse
The whole point of adb sideload is that you're sideloading a flashable zip that is not on your phone but on your computer and you're pushing the file onto your phone which will followup with flashing the zip.
You need to be typing adb sideload on your computer with the proper environment for adb set up with the proper drivers installed if you haven't already.