Database Info

[UNROOT] Unroot any android device

HOW TO UNROOT (ALMOST) ALL ANDROID DEVICES (SIMPLIFIED)
Firstly, in order to unroot your android device, you need:
1) An update available for your phone or an old nandroid backup that has a previous version of your phone android version
2) A nandroid backup done before you attempt the following steps below
Once the above conditions are met, you are ready to UNROOT your phone!
Before you read the procedure, read how it works
below and get a better picture:
HOW
Firstly, one known method of unrooting is to install an available system update. However, stock updates are signed with official keys and custom recoveries only accept updates signed with their custom keys.
So, to unroot, you need to have stock recovery installed. One way to get your phone`s stock recovery back is contained in the update zip.
The update zip is the key, literally. Look through it and you will find (usually in the system folder) a file called recovery.img, which will be used as your new stock recovery.
By flashing in the image into recovery, you can now install updates, keep your previous applications, enjoy being unrooted and updated.
There are other unroot options that tailor to specific android phones and versions, but this solution should work on all android phones.
Why unroot? Because sending in a rooted phone for repair will void your warranty. Also, by having a rooted phone, you run the risk of a rogue rooted application that does unwanted stuff to your phone.
PROCEDURE
Step 1) If you still have your original stock recovery that came with your phone, continue. Else search for my previous thread: "[RECOVERY] Reverting to original(STOCK) recovery" and follow the steps there. You can use the update file you used to revert to stock recovery here as well or vice versa
Step 2) Reboot you phone
Step 3) Check for system updates and download them
Step 4) Wait until phone reboots. All your applications and user settings will be retained.
Step 5a) Open up a terminal emulator on your phone and enter "su" (Check if unroot)
Step 5b) If you cant turn your phone on to check if unrooted, boot into recovery mode, open up adb enter:
Code:
adb shell
su
Step 6) If you get "permission denied" or something like that from step 5a/5b,
CONGRATULATIONS! YOUR PHONE HAS BEEN SUCCESSFULLY UNROOTED!
Step 7) If you don`t want to void your warranty, you should unistall applications that require root, especially Superuser
To date, I have rooted and unrooted my phone (Backflip) 3 times without any problems. In case your phone can`t be booted up, only to the bootloader or recovery, DO NOT WORRY! You can use the adb (android debug bridge) to flash in the stock recovery, push/pull the updates and reboot the phone into recovery mode or normal mode!!!
Useful ADB commands
Reboot Phone
Code:
adb shell
reboot
Reboot Phone into recovery mode
Code:
adb shell
reboot recovery
Flash a new recovery image temporarily (resets when rebooting)
Code:
adb shell
flash_image recovery /sdcard/recovery.img
Flash a new recovery image that does not reset when rebooting
Code:
adb shell
flash_image recovery /sdcard/recovery.img
exit
adb shell
cd system
su
mount -o rw,remount /dev/block/mtdblock1 /system
rm recovery.img
mount -o ro,remount /dev/block/mtdblock1 /system
exit
exit
Push file to sdcard
Code:
adb push file.blah /sdcard/file.blah
Push file to sdcard
Code:
adb pull /sdcard/file.blah file.blah
Here`s wishing you good luck and a belated happy new year!

Err.. Pretty cool info there but what if you don't meet above three requirements? I mean there are noobs like me who'd rather jump onto flashing while forgetting about nandroids etc. I guess there should be a one click unroot utility for all android devices like we have for rooting.

im really confused.
if the phone has been rooted (using fastboot oemunlock - yes) then how can we "unroot" this device? till today there has not been a way to do so.
but if what ur suggesting relocks the bootloader (removes the cross at bootup) then woohoo!

The main point
ok, i think you guys dont understand what my point on unrooting is...
What im trying to say is:
Updating your phone software with an original OTA update on the original rom the came with your phone will automatically reset root. However, custom roms and recoveries dont accept OTA updates, so you need to flash back your original recovery first, nevermind if you have a custom rom.
If you don`t meet the requirements, then i`m sorry, you`ll just have to wait for an available system update like me. However if you get one, be sure to come back here if you want to unroot.

Creating a one/two click-unroot application
Actually, you may be right. The unroot procedures can also be carried out by adb alone , not by user interaction. So a desktop application can be created that automates the process
1) Open adb shell
2) Enter su
3) Pull the update zip from the phone
4) Recursive/y search the zip for the file recovery.img
5) Run 'flash_image recovery recovery.img'
6) Run 'adb reboot' to reboot phone
7) Phone will install update on stock update when rebooting complete
8) When update installed, root will be removed and your phone will be updated as well!
We can send keystrokes to the adb for the adb shell.

siidheesh said:
Actually, you may be right. The unroot procedures can also be carried out by adb alone , not by user interaction. So a desktop application can be created that automates the process
1) Open adb shell
2) Enter su
3) Pull the update zip from the phone
4) Recursive/y search the zip for the file recovery.img
5) Run 'flash_image recovery recovery.img'
6) Run 'adb reboot' to reboot phone
7) Phone will install update on stock update when rebooting complete
8) When update installed, root will be removed and your phone will be updated as well!
We can send keystrokes to the adb for the adb shell.
Click to expand...
Click to collapse
Shouldn't be too hard, probably only a simple script would suffice I'll see what I can come up with (if I can do anything ). Supply the script with your required update zip to make it work in a different way (maybe, I'm not great with details)

Automated Script
Can someone please clarify that this would work (as an unroot script):
1. Opens ADB shell
2. Enters su
3. (User) Supply script with stock update.zip - in case it's not on phone (correct if this is unnecessary)
4. recovery.img extracted from update.zip
5. recovery.img flashed to phone via 'flash_image recovery recovery.img'
6. Reboots phone via 'adb reboot'
That installs stock recovery, but what if there was no OTA update to install for that particular device? That's the only problem I can see with such a script, so I'm hesitant to make it right now (besides, I don't have my Nexus with me at the moment, so I couldn't test it).
Dumb question but would flashing a stock update.zip from the stock recovery remove root? Or does it have to be OTA? Never having done it before I'm not sure.
Edit: If it did have to be OTA, maybe you could find the original update.zip (ie. no updates before it) and flash that, so there would be a higher chance of an OTA update?

Different definitions
Sorry people, when i mean ota update, i dont just over-the-air updates, i am referring to original updates for your original android system that came with your phone.

siidheesh said:
Sorry people, when i mean ota update, i dont just over-the-air updates, i am referring to original updates for your original android system that came with your phone.
Click to expand...
Click to collapse
So just to clarify, you could install any stock ROM for your device and it would remove root? Specifically if it was installed through stock recovery.
Thanks, hopefully I might be able to make some progress after this

not as easy as it seems
jonathongrigg said:
Can someone please clarify that this would work (as an unroot script):
1. Opens ADB shell
2. Enters su
3. (User) Supply script with stock update.zip - in case it's not on phone (correct if this is unnecessary)
4. recovery.img extracted from update.zip
5. recovery.img flashed to phone via 'flash_image recovery recovery.img'
6. Reboots phone via 'adb reboot'
That installs stock recovery, but what if there was no OTA update to install for that particular device? That's the only problem I can see with such a script, so I'm hesitant to make it right now (besides, I don't have my Nexus with me at the moment, so I couldn't test it).
Dumb question but would flashing a stock update.zip from the stock recovery remove root? Or does it have to be OTA? Never having done it before I'm not sure.
Edit: If it did have to be OTA, maybe you could find the original update.zip (ie. no updates before it) and flash that, so there would be a higher chance of an OTA update?
Click to expand...
Click to collapse
You cant make an unroot script that easily. Im halfway working on a .net application that does it on desktop.
Also, almost all great things come with a *catch*. In this case, you need to wait for an ota update to be available. Or if you took a nandroid backup some time back and updated your version, you can revert back to the old verison and update again.

siidheesh said:
You cant make an unroot script that easily. Im halfway working on a .net application that does it on desktop.
Also, almost all great things come with a *catch*. In this case, you need to wait for an ota update to be available. Or if you took a nandroid backup some time back and updated your version, you can revert back to the old verison and update again.
Click to expand...
Click to collapse
Oh well, I didn't realise I figured you could do it all from the command line, so a script of some kind might do. That said I wasn't entirely sure as I couldn't test the theory (no phone )

siidheesh said:
In this case, you need to wait for an ota update to be available. Or if you took a nandroid backup some time back and updated your version, you can revert back to the old verison and update again.
Click to expand...
Click to collapse
Another win for stock Android phones No waiting months for OTA updates! Well good luck on your .NET application, I only know Java and Python, so I can't really help you there, sorry.

dont know
my phone (Backflip) isnt a very popular phone and there`s only one rom for it. to date, i`be only tried unrooting via stock updating. Stock roms may work too, but im not sure...

adb shell
jonathongrigg said:
Oh well, I didn't realise I figured you could do it all from the command line, so a script of some kind might do. That said I wasn't entirely sure as I couldn't test the theory (no phone )
Click to expand...
Click to collapse
actually, i did mention that the unroot procedure can be done entirely from the adb shell, which is also in command line. im just making a program to enter those lines in automatically. normal batch scripts cant write to the adb shell as it is a separate shell in the command prompt...

What about doing a factory reset?

hi, would these unroot methods still work on the new updated highly secured samsung galaxy s2?
because i got the phone simlocked hoping to unlock it for t-mobile so rooted the phone but it was been unsuccessful at taking the sim lock off, so i wanted to make sure that this will still work on this phone.
Also after unroot i assume the yellow triangle will disappear, right?

oh yea thanks for replies and help in advance. Love the site

total noob here, I rooted my tab awhile bk, now needs warranty. I used 'superoneclick', but didnt backup anything first that i know of. U mention nandroid backup, update available for my phone, where do I get that, and how? Embarrassed I know nothing about these terms, trying to learn. Could u help me, please?

where can I find the recovery.img?
thanks

Does this work on all roots?

[Q] Problems With CMB command prompt. HELPPP

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.

Root and Custom CWM recovery for VSD220

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

Cool, thanks!

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Q] Karbonn A30 Boot Loop Problem

Problem Details:
I recently rooted this phone (no custom recovery yet) and installed the ROM Toolbox Lite. I edited the build.prop to to change the lcd density to make it more nicer to look and it gone okay.
The problem arises when I tried the Font Installer in the ROM toolbox lite. It required a reboot and then the boot loop happens.
I went to system recovery and tried all the wiping methods but it didn't work. I tried the update from the sdcard but all installations were aborted because signature verifcation always failed.
Do you have any solutions to this ( or will I have to throw my phone to the trash cans now :crying? Any help will be highly appreciated.

Pinoy_Ako said:
Problem Details:
I recently rooted this phone (no custom recovery yet) and installed the ROM Toolbox Lite. I edited the build.prop to to change the lcd density to make it more nicer to look and it gone okay.
The problem arises when I tried the Font Installer in the ROM toolbox lite. It required a reboot and then the boot loop happens.
I went to system recovery and tried all the wiping methods but it didn't work. I tried the update from the sdcard but all installations were aborted because signature verifcation always failed.
Do you have any solutions to this ( or will I have to throw my phone to the trash cans now :crying? Any help will be highly appreciated.
Click to expand...
Click to collapse
1) Download the Android SDK (if you haven't already).
2) Run Android Debug Bridge using Command Prompt or Terminal (Depending if you are Windows or Mac)
3) Use ADB to pull the build.prop file to your computer.
4) Alter the LCD Density back to normal. Make sure the permissions are 644.
Alternative 3) Download the stock build.prop for your device.
5) Push either the build.prop (with normal LCD density) back to /System/ in ADB
Tell me how it goes

williamguy said:
1) Download the Android SDK (if you haven't already).
2) Run Android Debug Bridge using Command Prompt or Terminal (Depending if you are Windows or Mac)
3) Use ADB to pull the build.prop file to your computer.
4) Alter the LCD Density back to normal. Make sure the permissions are 644.
Alternative 3) Download the stock build.prop for your device.
5) Push either the build.prop (with normal LCD density) back to /System/ in ADB
Tell me how it goes
Click to expand...
Click to collapse
I already downloaded the Android SDK and installed it. I run the ADB by using the command prompt but it only gives me the commands ( like -d, -e, -s, -p). How do you use this thing? Can you please elaborate on how use this thing and how ADB can pull the build.prop since I can't seem to connect my device to computer?

Pinoy_Ako said:
I already downloaded the Android SDK and installed it. I run the ADB by using the command prompt but it only gives me the commands ( like -d, -e, -s, -p). How do you use this thing? Can you please elaborate on how use this thing and how ADB can pull the build.prop since I can't seem to connect my device to computer?
Click to expand...
Click to collapse
I'm not to familiar with ADB.
To pull files: adb pull /mnt/sdcard/path/to/file /path/to/local/file
To push files: adb push /path/to/local/file /mnt/sdcard/path/to/file

I manage to study the adb thing. The problem I face now is how to connect my phone to pc.My computer doesn't recognize my phone when I connected it. I tried to search for the device driver but I can't find any. Even the pc suite is missing for this phone.

Here is CWM recovery for A30. flash it using ANDROID AIO FLASHER in fastboot mode. using cwm you can easily fix your phone
https://mega.co.nz/#!YUgEkSKC!JjokMRNW9dmpk5XbVVSBKz4LAi9fjcAWkzuChCDuE4s

karan128 said:
Here is CWM recovery for A30. flash it using ANDROID AIO FLASHER in fastboot mode. using cwm you can easily fix your phone
https://mega.co.nz/#!YUgEkSKC!JjokMRNW9dmpk5XbVVSBKz4LAi9fjcAWkzuChCDuE4s
Click to expand...
Click to collapse
I dont know what fastboot mode means but I will try to see this ANDROID AIO FLASHER. Sounds that I will have to connect my phone to my pc. I just hope that it can help me to connect my phone easily.

Pinoy_Ako said:
Problem Details:
I recently rooted this phone (no custom recovery yet) and installed the ROM Toolbox Lite. I edited the build.prop to to change the lcd density to make it more nicer to look and it gone okay.
The problem arises when I tried the Font Installer in the ROM toolbox lite. It required a reboot and then the boot loop happens.
I went to system recovery and tried all the wiping methods but it didn't work. I tried the update from the sdcard but all installations were aborted because signature verifcation always failed.
Do you have any solutions to this ( or will I have to throw my phone to the trash cans now :crying? Any help will be highly appreciated.
Click to expand...
Click to collapse
install cwm . then flash it.. download cwm backup.. and just restore it ..
pree:good:

rajit said:
install cwm . then flash it.. download cwm backup.. and just restore it ..
pree:good:
Click to expand...
Click to collapse
If only it allows me to flash zip then it would be easy. the problem is i cant toggle off the signature verification.

Pinoy_Ako said:
If only it allows me to flash zip then it would be easy. the problem is i cant toggle off the signature verification.
Click to expand...
Click to collapse
You cannot toggle signature verification. You need to flash CWM first.
CWM is a custom recovery for android phones that provides many functions like system backup, restore, flashing zips, etc.
Flash cwm by going into fastboot mode

karan128 said:
You cannot toggle signature verification. You need to flash CWM first.
CWM is a custom recovery for android phones that provides many functions like system backup, restore, flashing zips, etc.
Flash cwm by going into fastboot mode
Click to expand...
Click to collapse
I already have this CWM before I rooted my phone. I just didn't flash it after I rooted it (silly on me ). Now my only hope is to have a fastboot but my problem now is how to get the drivers for my phone since I can't connect and my pc didn't recognize.

Can anyone give me a link where I can get the device drivers for this phone (windows user here)?

Install PDAnet on pc for drivers.
Sent from my A9 using xda app-developers app

I still can't connect my pc after installing the PDAnet. (Maybe it's time for me to get rid of this phone.)

Pinoy_Ako said:
I still can't connect my pc after installing the PDAnet. (Maybe it's time for me to get rid of this phone.)
Click to expand...
Click to collapse
h tt p: //adbdriver. com/ downloads /
download the 'adb driver installer'
run it
it will automatically detect the driver needed for u r device
and click install

Error in ADB: Can't push apps/files due to system is read only.

Hello guys! Hope I can find my salvation here. Hehe
I've been coding my Windows App that functions much like a custom recovery but I came into a problem which is bugging me
since last week. I can't seem to push files to my phone through adb. I have no idea why it wont work because pull is working fine, and shell as well. I tried remounting the file system as rw but still no luck. Hope you can help me out guys
My phone's Specification:
-Spreadtrum SC7731
-Running Android 5.1
My environment:
-Windows 10
-adb installed
-device drivers installed.
PS: If you are wondering why make a recovery that runs in PC while you can just have it in your phone?
-Unfortunately, I got a problem with that. I ported TWRP for my phone, but touch wont work which makes it useless.
Please help me sensei's!

Unlock the bootloader, flash a custom recovery (CMW for exmpl), put the root package at the root dir of the sdcard, now boot the phone into recovery mode and select install zip from sdcard then reboot
On pc, write the following command : "adb remount"
Gratzz you're now rooted and able to push files into system partition ��
Root at your own risk. Unlocking the bootloader makes you lose the warranty and will wipe your data .. So take a backup.

FinnTheHuman. said:
Unlock the bootloader, flash a custom recovery (CMW for exmpl), put the root package at the root dir of the sdcard, now boot the phone into recovery mode and select install zip from sdcard then reboot
On pc, write the following command : "adb remount"
Gratzz you're now rooted and able to push files into system partition ��
Root at your own risk. Unlocking the bootloader makes you lose the warranty and will wipe your data .. So take a backup.
Click to expand...
Click to collapse
Reread the OP. :fingers-crossed::fingers-crossed: I'm on Spreadtrum phone which means no source(yet.. or forever). I don't really know if you just misinterpreted the post or just trying to acquire post count. :3