You should be able to uninstall Universal Androot by accessing settings, Manage Apps, All, select Universla Androot, then "click" uninstall. But I would think that you can download the latest version from this site and install over your existing version. And to download you either need to know how to connect your phone to your PC and copyd the downloaded file from you PC to your SDCard root directory, then use something like Astro to install the app. These root apps are not available from the market. I was able to download directly to my phone using my Dolphin browser. I then used Astro file manager to navigate to my download folder and install the app.
[APP] [ROOT] 1-click root for N1 (Latest ver: 1.6.2 beta 5)
- Thread starter ctbear
- Start date
- Status
Just a quick question
ok so i read through some what all of these pages but kinda got confused.
if i use this, will it let me install for say clockwork or amon_ra recovery image? so i can flash a custom rom? or its just Root and thats it.
ok so i read through some what all of these pages but kinda got confused.
if i use this, will it let me install for say clockwork or amon_ra recovery image? so i can flash a custom rom? or its just Root and thats it.
Once you use this app, you can install any custom rom. I used this app and now run CM6 final with the mean and green theme. Great app and great idea!
thanks for the quick reply bro!Once you use this app, you can install any custom rom. I used this app and now run CM6 final with the mean and green theme. Great app and great idea!
After a long wait and hesitation, I installed univseral androot and it worked great on my Droid 1. However, I just received my FRG22D update and installed it. Now the universal androot doesn't work. When will we see an updated to Universal Androot that will included the Droid 2.2 FRG22D? Thanks in advance for the reply.
Explanations required for a newbie
Hello all,
I am not only new to the world of Android, but also to the Unix/Linux world, having spent most of my professional life working on the DOS/Windows platform. A lot of what I read here seems to make sense, but only if you have a basic - if not intermediate - knowledge of the Linux techno-babble... which I don't.
I'd like to gather enough information so I can publish a (hopefully) simple article for Windows users who want easy steps into rooting and using custom ROMs. Without having to learn what SU is, how to navigate through folders using archaic shell commands, and what not.
So... learning from my own experience so far...
I followed the steps to 1-click root my HTC Magic 32a. It apparently worked, with Universal Androot telling me my device is now rooted. I did it twice (after sorting through hundreds of posts to see if it could cause any damage, which it didn't), and I'm fairly confident I got that part done right.
However, being ever-doubtful, I wanted a second opinion as to whether my device is actually rooted. So I downloaded the latest Android SDK, added the Android 1.5 platform (which is what currrently runs on my Magic) and followed what seemed to be the most widely accepted recommendations. (Of course, my device has the proper USB drivers, I can see the SD card just fine from Windows Explorer, so I assume the *physical* connection is taken care of).
Going to the API's /tools subfolder, I type
adb devices
to which i get the following reply
HT95MNK03518 device
which seems to confirm my device is correctly identified.
Then, I try the following:
adb root
but all I get as a reply is:
adb cannot run as root in production builds
and the program hangs there. I have to kill it through the task manager to regain control of the DOS command prompt
My ultimate goal is to install Froyo on my Magic. Since I'm already stuck after this admittedly simple procedure, I'm kind of weary of attempting to go beyond and burn a new image onto the phone.
So can anyone tell me why ADB won't grant me root access even though the phone is supposedly rooted?
And as for the next steps, given my very basic knowledge of this environment, is there any Installing-ROMS-On-HTC-Magic-For-Dummies user's guide out there?
Thanks, and sorry for being long-winded.
Hello all,
I am not only new to the world of Android, but also to the Unix/Linux world, having spent most of my professional life working on the DOS/Windows platform. A lot of what I read here seems to make sense, but only if you have a basic - if not intermediate - knowledge of the Linux techno-babble... which I don't.
I'd like to gather enough information so I can publish a (hopefully) simple article for Windows users who want easy steps into rooting and using custom ROMs. Without having to learn what SU is, how to navigate through folders using archaic shell commands, and what not.
So... learning from my own experience so far...
I followed the steps to 1-click root my HTC Magic 32a. It apparently worked, with Universal Androot telling me my device is now rooted. I did it twice (after sorting through hundreds of posts to see if it could cause any damage, which it didn't), and I'm fairly confident I got that part done right.
However, being ever-doubtful, I wanted a second opinion as to whether my device is actually rooted. So I downloaded the latest Android SDK, added the Android 1.5 platform (which is what currrently runs on my Magic) and followed what seemed to be the most widely accepted recommendations. (Of course, my device has the proper USB drivers, I can see the SD card just fine from Windows Explorer, so I assume the *physical* connection is taken care of).
Going to the API's /tools subfolder, I type
adb devices
to which i get the following reply
HT95MNK03518 device
which seems to confirm my device is correctly identified.
Then, I try the following:
adb root
but all I get as a reply is:
adb cannot run as root in production builds
and the program hangs there. I have to kill it through the task manager to regain control of the DOS command prompt
My ultimate goal is to install Froyo on my Magic. Since I'm already stuck after this admittedly simple procedure, I'm kind of weary of attempting to go beyond and burn a new image onto the phone.
So can anyone tell me why ADB won't grant me root access even though the phone is supposedly rooted?
And as for the next steps, given my very basic knowledge of this environment, is there any Installing-ROMS-On-HTC-Magic-For-Dummies user's guide out there?
Thanks, and sorry for being long-winded.
OK, yes I knew that. Sorry, I'm a noob and only saw that Manage Applications page once.
Thanks.
Quick question. I was running this app on Cyanogen RC3 and it worked fine but when i updated the rom to 6.0 stable release for the nexus uinversal androot stopped working. im still rooted and have superuser permissons but the app is stuck on rooted and i get a fail message everytime. whether i choose root or unroot still get fail message. Anyone else encounter this problem? I have a N1 on cyanogen 6.0 stable release
ok i think i did it....now my phone automatically rebooted with the cyanogen mod startup screen (blue thing going in circles) but it's stuck there and its been going for about 10 minutes now. Is this normal?
should i try pulling the battery and rebooting?
I'm on a MyTouch 3G Fender Edition
should i try pulling the battery and rebooting?
I'm on a MyTouch 3G Fender Edition
No it's not normal, the CM logo should only stay up as long as the original N1 logo did. I presume you remembered to wipe?
hehe...no it's not bricked. Like the guy said, do a recov and you'll be fine. The only thing that is annoying is the time it takes to recover. lol.
OMG thank you those words just brought my heart rate down to normal!!!! i was crapping my pantss!!!!
yeah i went into recovery mode and tried to restore and it says successful, but when i hit reboot now....same thing...stuck at the cm screen.
So if i do a clean wipe do i lose my backup data? (really only my contacts i'm worried about)
yeah i went into recovery mode and tried to restore and it says successful, but when i hit reboot now....same thing...stuck at the cm screen.
So if i do a clean wipe do i lose my backup data? (really only my contacts i'm worried about)
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
23
EDIT2: Since Google patched the loop hole in 2.2.1, this app is no longer working for newer builds. For this reason the developer has stopped supporting the app. If you still want to use this, feel free to do so. It would not harm anything.
However if it doesn't root your phone, there are numerous other methods of rooting out there. I suggest SuperOneClick or unrevoked.
EDIT: I see that a lot of people have no idea what rooting is, or don't even know how to install an apk. Seriously, rooting can potentially harm your phone if you have absolutely no idea what you're doing. For that reason, I strongly recommend you hold off using this app (or rooting in general) until you have done enough research and are more comfortable with Android.
If you insist on using this app, use it at your own risk. You have been warned!
This is a good post to guide you through how to flash a custom rom, after rooting your phone. And no, this app does not unlock your bootloader.
Important: I'm not the developer, click the link below for the blog for official release of this app
Official releases here
Aug 30 Update: added v1.6.2 beta 5, added support for more devices, added widget for soft root
Aug 12 Update: added v1.6.1: superuser updated, HTC Tattoo support added. Check official link for changelog
Aug 10 Update: added v1.5.3 for peeps who can't access the link
Official list of supported devices:
Code:Supported Devices: Google Nexus One (2.2) Google G1 (1.6) HTC Hero (2.1) HTC Magic (1.5) (Select Do not install Superuser) HTC Tattoo (1.6) Dell Streak (2.1) Motorola Milestone (2.1) Motorola XT701 Motorola XT800 (2.1) Motorola ME511 Motorola Charm Motorola Droid (2.01/2.1/2.2 with FRG01B) Sony Ericsson X10 (1.6) Sony Ericsson X10 Mini (1.6) Sony Ericsson X10 Mini Pro (1.6) Acer Liquid (2.1) Acer beTouch E400 (2.1) Samsung Galaxy Beam Samsung galaxy 5 (gt-i5500) Vibo A688 (1.6) Lenovo Lephone (1.6) LG GT540 (1.6) Gigabyte GSmart G1305 Not supported: Google Nexus One (2.2 FRG33) Samsung i9000 / i6500U / i7500 / i5700 Motorola ME600 / ME501 / MB300 / CLIQ XT Motorola 2.2 FRG22D Archos 5 HuaWei U8220 HTC Desire / Legend / Wildfire (soft root) HTC EVO 4G / Aria SonyEricsson X10i R2BA020 myTouch Slide
Reported working (in this thread):
Code:Nexus One 2.2 Milestone 2.1 Hero (GSM/CDMA) Xperia X10 mini Xperia X10i G1 1.6 Magic 32A 1.5 Magic 32B 1.6 Mytouch 3G (3.5mm) Mytouch 3G Slide (v1.6.1 seems to put the phone into reboot loop) LG Ally Droid X 2.1 Moto Charm Moto Flipout Kyocera ZIO
All credits go to the developer!
Install and run it on your phone. If you have trouble downloading, try download with a computer.1
thanks for the quick reply bro!Once you use this app, you can install any custom rom. I used this app and now run CM6 final with the mean and green theme. Great app and great idea!
1Explanations required for a newbie
Hello all,
I am not only new to the world of Android, but also to the Unix/Linux world, having spent most of my professional life working on the DOS/Windows platform. A lot of what I read here seems to make sense, but only if you have a basic - if not intermediate - knowledge of the Linux techno-babble... which I don't.
I'd like to gather enough information so I can publish a (hopefully) simple article for Windows users who want easy steps into rooting and using custom ROMs. Without having to learn what SU is, how to navigate through folders using archaic shell commands, and what not.
So... learning from my own experience so far...
I followed the steps to 1-click root my HTC Magic 32a. It apparently worked, with Universal Androot telling me my device is now rooted. I did it twice (after sorting through hundreds of posts to see if it could cause any damage, which it didn't), and I'm fairly confident I got that part done right.
However, being ever-doubtful, I wanted a second opinion as to whether my device is actually rooted. So I downloaded the latest Android SDK, added the Android 1.5 platform (which is what currrently runs on my Magic) and followed what seemed to be the most widely accepted recommendations. (Of course, my device has the proper USB drivers, I can see the SD card just fine from Windows Explorer, so I assume the *physical* connection is taken care of).
Going to the API's /tools subfolder, I type
adb devices
to which i get the following reply
HT95MNK03518 device
which seems to confirm my device is correctly identified.
Then, I try the following:
adb root
but all I get as a reply is:
adb cannot run as root in production builds
and the program hangs there. I have to kill it through the task manager to regain control of the DOS command prompt
My ultimate goal is to install Froyo on my Magic. Since I'm already stuck after this admittedly simple procedure, I'm kind of weary of attempting to go beyond and burn a new image onto the phone.
So can anyone tell me why ADB won't grant me root access even though the phone is supposedly rooted?
And as for the next steps, given my very basic knowledge of this environment, is there any Installing-ROMS-On-HTC-Magic-For-Dummies user's guide out there?
Thanks, and sorry for being long-winded.
New posts
-
Features disabled on fastboot and bootloader. How do I enable them?- Latest: mayberandomparable
-
-
