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 have been trying to root my Samsung phone by installing SuperUser ,methods i have tried .
1- Downloaded SU from play store
2-Install Busy Box
3-Flashed recovery.tar.md5 but can't boot into recovery mode ,key combination(Vol up+home+power) is not working.
4-Somehow i manged to boot into recovery mode by installling ADB drivers and typing command "adb reboot recovery".
5-Recovery option doesn't give option to install something from sd card card or phone ,it gives option to install with adb
6- I place Super user file to adb folder on my computer and then run the command "adb install superuser.apk" but it showed ,apk doesn't found.
Please help.
You can easily root any android devices simply follow the link. Everything is explained there step by step ;
How to Root your Android Device ?
Shivam_s said:
I have been trying to root my Samsung phone by installing SuperUser ,methods i have tried .
1- Downloaded SU from play store
2-Install Busy Box
3-Flashed recovery.tar.md5 but can't boot into recovery mode ,key combination(Vol up+home+power) is not working.
4-Somehow i manged to boot into recovery mode by installling ADB drivers and typing command "adb reboot recovery".
5-Recovery option doesn't give option to install something from sd card card or phone ,it gives option to install with adb
6- I place Super user file to adb folder on my computer and then run the command "adb install superuser.apk" but it showed ,apk doesn't found.
Please help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2327716
Thank you for your replies. I managed to root my device by installing a Lollipop Rom and its awesome.I serached around and fine that for some devices it will boot into recovery mode and present you the option like install update from SD card straight away but this was not the case with my device..First i was not able to update into recovery mode just by pressing the key combination.So i choose another method which was via Command line , i boot into recovery mode by installing adb drivers and then ran commands from my pc.
Second even in recovery mode , it only showed ,install update from adb sideload, which was not an option for me.So i applied a recovery .tar.md5 by going into download mode and that recovery file showed me the option "install update from sd card" And now my phone is looking Awesome .Lollipop is just Awesome .
What i did -
1- Downloaded Odin
2-Downloaded Lollipop version created by Russel
3-I had adb driver installed already.
4-Enter into Download mode - press volume down + home to enter into Download mode- it will ask you apply custom ROM .To proceed,press volume up button to proceed.
5 -Ran the Odin as Administrator ,it should show samsung phone as Added
6- Click PDA and select recovery.tar.md5 file
7- Click Start button in Odin,should see a pass message in green in the top
8 -Unplug the Phone and reboot, now it will ask you to apply update from sd card ,
9- Select the downloaded ROM ,and apply .
10 -You have Lollipop on your Phone.
If you need any help , send me a message .
Thank you
try Kingo http://www.kingoapp.com/
Hello experts!
Please see the steps I took, and help me figure this one out:
1. Installed MoboRobo on my PC
2. Connected the TV box, and got it recognized
3. Closed MoboRobo
4. Launched TPSarky.bat and followed instructions
5. *At this stage I might have pressed the space key to reboot too early, for one of the three reboots
6. TPSarky completed its work (meaning the UID=0 GID=0, and SuperSU was pushed)
7. Device booted, SuperSU was there, but upon launching, it said there isn't an SU binary installed, and SuperSU can't install it
I tried several advices from different forums:
A. Pushing a different SU with another Superuser app, or different versions of the SU management apps
B. Pushing the SU to /system/bin and also /system/xbin
C. Using Fastboot to install a custom recovery (as I can't do it via the device itself) to update the SU with a flashable ZIP, but Fastboot didn't recognize the device (ADB does recognize it)
D. Using RK Batch tool / Android tool to install the custom recovery, but it said "Load firmware failed", with no matter how many different recovery *.img files I tried (CWM or TWRP)
So now I'm kind of stuck in a situation, where ADB on my pc confirms the device is rooted (UID=0 , GID=0), but the device itself behaves like it's not.
Any advice per how to handle this? Maybe there's a way to unroot by going back to factory settings, and run TPSarky from scratch? Maybe a step I'm missing to complete the root on the device?
Please please please advise, this is killing me...