Related
I posted this in another thread but got no response, this thread (http://forum.xda-developers.com/showthread.php?t=502010&page=35)
maybe a new thread will help.
So this is my first venture into the whole ABD thing. I am trying to install the framework mod from Tazz for the HTC music player (as listed here: http://forum.xda-developers.com/show...5594&page=1277 post 12768).
Tazz mentions to “push this http://www.multiupload.com/1WWHXAUN6W
to system/ect/permissions then download and install htc music”
So, running my trusty Win7 machine I downloaded the SDK from the android development site, inserted the correct line in the path and viola, I can enter the CMD prompt and run the adb command successfully. Adb and adb shell both seem to work.
I followed the instructions from here: http://androidforums.com/developer-1...-commands.html and here: http://forum.xda-developers.com/showthread.php?t=502010 for the install.
My problem comes in when I try to push the file to the phone.
Fisrt dumb question is: what phone mode should I be in when running the adb? Standard running mode or booted to recovery? (I thought I read something about being in recovery but at that point it was all a blur).
I have the USB Debugging turned on so I think I am ok there.
I installed the SDK to my C:\Android directory.
I saved Tazz’s file to my C:\Android\Tools directory.
Here is my cmd text (maybe this is where I went wrong):
In the cmd window I CD’d to the C:\Android\Tools directory
adb push com.framework.htc.xml system/ect/permissions
After making sure that I was in the correct dir and all files were also located in the correct dir I am still getting an error, file or directory not found, or something like that.
Sorry for the long post. I figured this would be a good first step (my first adb experience) as it seems pretty benign in terms of me bricking anything but offering a good learning opportunity.
I am running a rooted Eris (KaosFroyo v36).
In looking things thru maybe I need a USB driver for the Eris?
any help is appreciated,
oh, my cmd prompt looks like sh-2# (or something like that)
Thanks
While it may be that you still need to download the appropriate drivers, it seems you are able to get root access so, this is likely not the case.
There are two things which stand out as potential issues in the steps you described. Fortunately, both are super easy.
First and foremost, make sure you have mounted the phone as "read-write."After you have cd'd to the tools folder type "adb remount" (without the quotes) and press enter. If successful, it should respond with "remount succeeded." Congrats, you have now mounted the phone as read-write.
Next, I see errors with your command. There should be a "/" before "system" and it should be "etc" not "ect." Specifically, your command should be:
adb push com.framework.htc.xml /system/etc/permissions/
[The above command of course, assumes that the name of the file you are pushing is indeed named "com.framework.htc.xml" and is in your tools folder.] You'll know it worked if the response in your command prompt indicates the speed and time it took for the push to take. For example, "1234kbps in 3.4 seconds". If you see something resembling that you should be all set. At this point you can reboot your phone and your changes should be in effect. Either unplug and reboot manually or just type "adb reboot" (without the quotes) and press enter.
In regard to your question about whether the phone can be in standard running mode or recovery... It depends on the level of root of the phone but, fully rooted and nand unlocked phones can be adb'd while in standard running mode. My EVO can and it is very likely your Eris can too.
I see
thanks OK.
typo's aside in the thread, my command was missing the / as you have described it. I also did not know about the remount thing. In my reading I thought that was just for the sd card. I will try and put all the pieces together when I get home tonight.
You are correct in that is the name of the file and I do have it in the /tools directory.
Thanks for the help, baby steps (I am learning)
No problem. We are/were all noobs at one point in our lives.
The term "mounting" has slightly different contextual meanings which can be confusing. First off, the /system/ folder is already "mounted" while using adb, however, it is mounted as read-only. So, if you are ever trying to push something to the phone and get an error back that says "mounted as read-only" you'll now know what went wrong. Simply type "adb remount"
and it puts the /system/ folder into read-write mode.
Bear in mind that upon phone reboot the /system/ folder automatically remounts into read-only mode so if you reboot and try to push another file you'll need to remember to "adb remount" again.
With regard to the sdcard "mounting" refers to whether the phone (sdcard) is mounted as a disk drive on your computer. You'll find that if this is the case many adb commands won't work because the sdcard can't be accessed by the phone while mounted on the computer. Therefore, always remember to connect your phone as "Charge Only" when adb'ing.
got it
That did the trick, worked like a charm. Thanks for the help and pointers. I have now pushed my first file...yeah for me!!
Thanks for your help and time.
glad your push worked
I am still trying to get SDK/ADB to connect to my Milestone XT720 phone. Have no idea of why they won't. Have tried all the usual suspects but nothing as of yet. NEED HELP!
Okay, so I posted about a week ago re: my softkey issue and fortunately that was fixed by returning my phone to stock, however, I followed nexushacks method and when it told to do this:
Step 12. Once you get the Android guy with exclamation mark, hit Volume Up and Power button at the same time until you get blue menus.
Nothing bloody happens. Please don't tell me I have to hold it for something like 60 seconds because I. Will. Rage. Lol.
When I try to go into recovery I get that symbol and can't do anything but batt pull. I'm still unlocked and rooted, to my knowledge.
I downloaded ROM Manager because I wanted to flash a recovery on it but it told me that "An error occurred while attempting to run privileged commands"
It also says this when I open Rom Manager "You must root your phone for ROM Manager to function. Superuser was not found at "/xbin/su" or "/system/xbin/su". Use google blabla"
I'm also in the process of trying a command prompt on windows but it keeps giving me the "waiting for device" or awaiting a responce from device" whatever that message is...
Trying to give as info as possible so someone can help a brother out.
I can't deal with this Stock OEM crap anymore *twitch*
Thanks!
Herp Derp
Okay, I didn't realize it was Press the Power button, then the volume up button.
Silly noobs.
So my question, is there a way to get Clockwork Recovery back on now or do I have to go through the whole "Rooting" process again?
I assume you see a lock symbol while booting. This means you're unlocked. Now you'll just need to use fastboot to flash a custom recovery (namely, CWM). NexusShacks details how to setup and use fastboot and i think they provide TWRP now, feel free to use this or just download CWM from here and flash that .img file instead.
After this, download the latest Superuser-3.0.7-efghi-signed.zip and flash that. Note that on a stock ROM it will flash stock recovery on every boot. To change this, rename /system/etc/install-recovery.sh to something else.
But how do I flash a .img file when I don't have Recovery mode?
Or can I use do that through the OEM Recovery (blue screen)?
You flash it with fastboot. Fastboot is a command line tool to flash various images through the bootloader screen. To enter the bootloader, turn off the device and hold Vol. Up + Power. This is the same place you would've typed "fastboot oem unlock", except to flash the new recovery you'll be typing something along the lines of "fastboot flash recovery recovery.img". NexusSHacks teaches you how to do all of this.
Ah sorry, I still get Fastboot and Bootloader mixed up.
Only problem is that I don't know if my computer is recognizing my device when I plug it in through Bootloader.
As mentioned in my original post
"I'm also in the process of trying a command prompt on windows but it keeps giving me the "waiting for device" or awaiting a response from device" whatever that message is..."
I'm at work now and trying to figure out how to do this using Terminal on my mac.
When I type in "cd /nexussrootICS" it keeps on telling me "no such file or directory"
Do I need to put this file in a specific folder? I got this step working on my PC at home but it told me "Waiting for device" the whole time.
Any thoughts?
I'm not particularly familiar with OS X so forgive anything i say that might be off target.
You need to direct the terminal to the relative OR absolute directory of that folder. A relative directory can be done by "cd ./blah", while an absolute will be done by "cd /blah". This is quite confusing for people who aren't used to command line, but very simple once you've done it a few times.
Easiest way aside from magical OS X shortcuts i don't know about is:
-Unzip the files to a "nexus" folder on the desktop, making sure the adb files are in this nexus folder and not a sub folder
-open terminal
-"cd /user/artist/desktop/nexus" or whatever the FULL PATH to the folder is. You should be able to see this through the folders properties or in the file explorer.
-Now you are in the folder, you can use adb and fastboot by just typing those words
I believe OS X can recognise the device straight away so you shouldn't need to install any drivers - at least my linux distros were like that. Installing drivers on Windows is detailed in the video, too.
Ah!!!! I feel like I'm so bloody close...
Okay that part worked perfectly, I found out how to at least direct Terminal to the right location but now I'm lost again...
It's giving me this
"
USER-iMac:nexus user$ ./fastboot-mac flash recovery-clockwork-5.0.2.0-crespo.img
unknown partition 'recovery-clockwork-5.0.2.0-crespo.img'
error: cannot determine image filename for 'recovery-clockwork-5.0.2.0-crespo.img'
USER-iMac:nexus user$
"
TheArtist8 said:
Ah!!!! I feel like I'm so bloody close...
Okay that part worked perfectly, I found out how to at least direct Terminal to the right location but now I'm lost again...
It's giving me this
"
USER-iMac:nexus user$ ./fastboot-mac flash recovery-clockwork-5.0.2.0-crespo.img
unknown partition 'recovery-clockwork-5.0.2.0-crespo.img'
error: cannot determine image filename for 'recovery-clockwork-5.0.2.0-crespo.img'
USER-iMac:nexus user$
"
Click to expand...
Click to collapse
The command should be
./fastboot-mac flash recovery recovery-clockwork-5.0.2.0-crespo.img
You were missing the recovery flag in the command.
Sent from my Nexus S 4G using Tapatalk 2
Also do "man fastboot-mac" in terminal to show all its options.
Sent from my Nexus S 4G using Tapatalk 2
Son of a... alright ill try after my lunch.
Sent from my Nexus S using XDA
Omfg I love you guys.
Thanks so much
I just got into Recovery mode, now on to Cyber-GR
Hi i'm having a problem trying to get my evo shift Perm Rooted. There's like 4 different guides that i've found on how To root an Evo or even more specifically the Shift. I've followed all these guides and still no luck.
I already have my phone Temp Rooted through VISIONary, my problem happens when I have to go to the CMB (Command Prompt)
8. Next, Open the command prompt (Start > Run > type "cmd") and paste the following...
Code:
cd C:\AndroidSDK\platform-tools
Hit enter, and type the following...
Code:
adb
If adb runs you're golden. Type this...
Code:
adb shell
Hit enter, you will see this...
Code:
$
Now type...
Code:
su
I make it to where I need to type in adb shell and what it says is adb server is out of date. killing... *daemon started successfully*
Then it shows the $ sign.
What i'm supposed to do now is type su
Then when I do it says su: permission denied
This is where i'm lost at. I followed everybody's instructions perfectly but cant move on till I get pass this... Can anyone help me please?
Thank you
What Android version are you on?
2.2 ?
2.3.3 ?
2.3.4 ?
Check the permissions under properties of adb.exe (right-click adb.exe and select properties) in your sdk/platform-tools folder. Make sure it is allowed to run as a program.
prboy1969 said:
What Android version are you on?
2.2 ?
2.3.3 ?
2.3.4 ?
Click to expand...
Click to collapse
2.2
Is that good or bad? Should I upgrade?
sparksco said:
Check the permissions under properties of adb.exe (right-click adb.exe and select properties) in your sdk/platform-tools folder. Make sure it is allowed to run as a program.
Click to expand...
Click to collapse
I have a Windows XP So when I go to properties the best I can do is Run it as an older version in compatibility mode? I'll still try it out to see if any older version works
*edit, tried and didnt work
tmb04 said:
2.2
Is that good or bad? Should I upgrade?
Click to expand...
Click to collapse
NO DO NOT UPGRADE!!! If your on 2.2 it's very easy. Just download and use THIS TOOL. It will do it all for you. Just connect the device via USB Cable, and choose charge only. Extract the Zip file that you downloaded onto your desktop, and run the program. Then click the ROOT Button. Make sure your Anti-Virus and Firewall are disabled before you start. Then just follow the Prompts. When it's all done go to the Play Store ( Android Market ) download Rom Manager Free. Open up Rom Manager follow the prompts to Flash CWM Recovery. That's it your Rooted with a Custom Recovery.
prboy1969 said:
NO DO NOT UPGRADE!!! If your on 2.2 it's very easy. Just download and use THIS TOOL. It will do it all for you. Just connect the device via USB Cable, and choose charge only. Extract the Zip file that you downloaded onto your desktop, and run the program. Then click the ROOT Button. Make sure your Anti-Virus and Firewall are disabled before you start. Then just follow the Prompts. When it's all done go to the Play Store ( Android Market ) download Rom Manager Free. Open up Rom Manager follow the prompts to Flash CWM Recovery. That's it your Rooted with a Custom Recovery.
Click to expand...
Click to collapse
I downloaded what you said, I run the program and disable the firewall, I clicked on Root and it says "Error running ADB try again"
I know that means I probably did something wrong in an earlier step but still unaware where I messed up at.
tmb04 said:
I downloaded what you said, I run the program and disable the firewall, I clicked on Root and it says "Error running ADB try again"
I know that means I probably did something wrong in an earlier step but still unaware where I messed up at.
Click to expand...
Click to collapse
You need adb working... In order for adb to work you need to have android debugging checked under Settings > Applications > Development on your phone. It's not enabled by default on Sense roms so you'll need to make sure it's enabled and turned on.
Ok I made it past the part I was stuck at. Rooted my phone, downloaded ROM manager, clicked on Flash ClockworkMod Recovery, and before it finishes it says " An error occurred while attempting to run privileged commands! "
I'm sorry for asking for so much help but I'm not trying to mess anything up
tmb04 said:
Ok I made it past the part I was stuck at. Rooted my phone, downloaded ROM manager, clicked on Flash ClockworkMod Recovery, and before it finishes it says " An error occurred while attempting to run privileged commands! "
I'm sorry for asking for so much help but I'm not trying to mess anything up
Click to expand...
Click to collapse
All good about asking questions. When the message pops up asking for SuperUser Permission, you have to click yes. Otherwise it will not run.
I ended up factory restoring my phone and followed a youtube video for the same exact guide that you told me to use. I followed it step by step and now my phone works perfect. I appreciate all the help.
Instead of me creating a new post, can you recommend a good guide for me to flash my shift to boost mobile?
tmb04 said:
I ended up factory restoring my phone and followed a youtube video for the same exact guide that you told me to use. I followed it step by step and now my phone works perfect. I appreciate all the help.
Instead of me creating a new post, can you recommend a good guide for me to flash my shift to boost mobile?
Click to expand...
Click to collapse
You should be able to find to find the info you need HERE.
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 want to start off saying that I'm a complete noob to this and I now realize I was stupid for biting of waaay more than I can chew.
I turned s-off and rooted using firewater exploit. I installed ViperOne with TWRP and all was well, until I decided I wanted to try Android Revolution HD (here) I stupidly decided that in addition to wiping the normal stuff, I would just format. I backed up to my pc just by copying everything into a folder (downloads, pictures, etc) and I wiped it. Now I've got the ROM on my computer and I'm trying to put it on the phone. I've tried using adb sideloader, and adb push but neither are working (I'm fairly certain I typed everything in correctly in cmd.)
How can I install ANY rom so that I can download with the phone and install from TWRP without formatting?
you've booted into recovery, and you're unable to adb push the rom.zip to your internal storage?
adb push romname.zip /media/data/0
jova33 said:
you've booted into recovery, and you're unable to adb push the rom.zip to your internal storage?
adb push romname.zip /media/data/0
Click to expand...
Click to collapse
Yes when I type that line into the cmd and press enter, nothing happens. No feedback at all, it just moves the cursor to the next line. I do have the rom in the same directory as adb and I did type it correctly into cmd. I attached an image of what it looks like.
>EDIT: spoke too soon. After nothing happened for a few minutes the cmd said "protocol failure"
chobungus said:
Yes when I type that line into the cmd and press enter, nothing happens. No feedback at all, it just moves the cursor to the next line. I do have the rom in the same directory as adb and I did type it correctly into cmd. I attached an image of what it looks like.
>EDIT: spoke too soon. After nothing happened for a few minutes the cmd said "protocol failure"
Click to expand...
Click to collapse
You probably didn't have USB debugging enabled, do you have access to a micro SD card?
If you do, load the rom onto that and flash from there.
Sent from my HTC6525LVW using Tapatalk
Well I was able to get it working, but as usual, I don't really know how. I redownloaded adb and the rom and restarted my computer. Tried the exact same sideload command and it worked.