Develop Bugs

Life after simpleroot?

Hey guys I just finished runny simple root OTA edition. Everything went well and now I'm rooted. I am running into a couple of questions now.
1. Whats happens now? I'm rooted now how do i get those nice custom roms onto my phone?
2. I purchased ROM Manager because baked snacks rom says it was necessary for install but i can't get it to install clockwork mod, it keeps saying something about error running privileged commands.
3. How do I go back to stock ROM I'm starting to feel like I might be over my head at this point.
Thanks for your help guys.

I'm in the same boat. The two main reasons for rooting was for a new ROM and to use it as a hot spot (which so far I haven't been able to do.)
ROM Manager gives me the same error message about clockwork. Also, I would like to stop paying the $30 a month for the hot spot, so any help in that area would be appreciated.
Darrell

Keep at it!
loztboy said:
Hey guys I just finished runny simple root OTA edition. Everything went well and now I'm rooted. I am running into a couple of questions now.
1. Whats happens now? I'm rooted now how do i get those nice custom roms onto my phone?
2. I purchased ROM Manager because baked snacks rom says it was necessary for install but i can't get it to install clockwork mod, it keeps saying something about error running privileged commands.
3. How do I go back to stock ROM I'm starting to feel like I might be over my head at this point.
Thanks for your help guys.
Click to expand...
Click to collapse
0. Please read everything before doing anything. My post is a little chaotic, but you should be fine if you read everything first.
1/2. The usual disclaimer: I'm not telling you to do anything. I'm just providing information. I'm not liable for anything you do to you phone.
1. ROM Manager is definitely the easiest way, though the "real way" is to load your ROM of choice on the SD card and then flash it from Recovery (more on recovery later).
1 & 1/2. By the way, you should install Titanium backup from the market five minutes ago. Yes, it is that important. When jumping ROMs, you often have to wipe everything out. Without Titanium Backup, you could end up having to repurchase apps and redownload all of your free ones, losing progress in games and settings in apps, etc. The free version of Titanium Backup lets you back up easily enough, but you want the donate version to prevent restores from taking a few hours of user interaction (Yes, I said user interaction, meaning sitting there and pressing buttons for hours). Once you throw $4.00-$50.00 (you can pick within that range, you get the same product regardless of amount) at Titanium Backup (and wait a day or so to get the license key file), you can do a restore in 15 min without any interaction beyond hitting start (or, more accurately, begin batch process). This app has saved my life time and time again. I literally did my first backup out of curiosity for the app and then totaled my phone in the next five minuets. It even backs up your home screen layout. GET IT NOW!!! YOU WILL HATE YOURSELF IF YOU DO NOT GET IT!!! At least get the free version, because, as stated above, it does backups fine. You (like me) will be scared into paying when you realize that you just wreaked everything and really don't want to spend the next few hours restoring. However, Titanium backup will not function until you get Superuser app working, as detailed in point 2 below.
***EDIT: I forgot to mention that Titanium Backup should work after running this program. It should even fix clockwork for you***
2. There are three possibilities for that error: 1: You don't have the superuser app installed. It dishes out the privileges. If you don't have it (if you do go on to potential issue number two and be grateful), you can install it by downloading this file and putting it on the root of the SD card. Then boot into recovery (I'm sure there is a tutorial for getting into recovery floating around here somewhere, just search the EVO section) and flash the .zip Presto! Superuser app is installed. If you prefer not to go around flashing random packages recommended by strangers on the internet, you can research and download superuser app at the source 2: If you found the Superuser app in the app drawer (the screen with all the applications where you scroll down in alphabetical order and pick the one you want to use), open it. You may have bumped "never give superuser access to this app" (or words to that effect) the first time you opened ROM Manager. If so, it will be listed in the Superuser app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
as red. Just have the superuser app forget ROM Manager and then try to flash custom recovery from within the ROM Manager again, being sure to say "Yes!" when it asks for superuser privileges. 3: If you have no recovery to flash superuser from or superuser is installed and ROM Manager is green inside and it still fails, the SimpleRoot failed. If you skipped a step in the rooting process, go back and do that step. If not, just start over and run all the steps from the beginning, Also note that if you accepted the over the air update, you need the OTA version of SimpleRoot, not the original one.
3. Now, about total reversal. I'll be honest: There is probably a way to go back to stock that works without finishing the root process (probably something to do with PC36IMG.zip) files, but I don't know it. The way I would do it would be picking the OTA Stock ROM from this page and flashing it after getting recovery installed at the end of a successful root process. However, then you would have succeed in your original endeavor and would have no need to go back. There is a program here that supposedly does just enough tweaking to the phone to give you the recovery you need to flash back to the stock ROM, but I have not used it myself and therefore cannot vouch for it.
dws51 said:
I'm in the same boat. The two main reasons for rooting was for a new ROM and to use it as a hot spot (which so far I haven't been able to do.)
ROM Manager gives me the same error message about clockwork. Also, I would like to stop paying the $30 a month for the hot spot, so any help in that area would be appreciated.
Darrell
Click to expand...
Click to collapse
If you both succeed in the root process (and I encourage you to persevere, the reward is spectacular), I personally recommend Cyanogen Mod 6. I believe that you can get the nightly builds of CM6 from ROM manager, but the release candidate is likely more stable. I use the RC myself and have never looked back. My battery lasts forever and my phone is never unresponsive. And because the CM6 ROM is based of of Android 2.2 (Froyo), free tethering is built in to the OS and done so rather elegantly, meaning no more dirty hacks for tethering. Just know that if you go that route, though you have the best of the best, you will need to tinker a bit to get everything working. Also, 4G, the FM Radio, and HDMI output are flat out not working in the RC (I'm sure they will be fully functional in the final release, and the not-workedness is a software thing, meaning that the hardware is fine and will come online when you again install a ROM that supports it). On the other hand, with this ROM you can force the phone to roam on Verizon's network when Sprint's 3G speeds are less than desirable.
I'm not sure where to put this, so I'm sticking it here. As soon as you get custom recovery working, you want to backup with Nandroid. The easiest way is from ROM Manager. Just hit "Backup ROM". This backs up not only your setup (like Titanium Backup), but also all the crucial bits that lie underneath and keep your EVOs humming, bits very very difficult to replace. HOWEVER, this is NOT a replacement for Titanium Backup, because it can only restore to the same ROM. If you attempt to restore to a different one, it will put the one you had at the time of the backup back on.
Whichever way you go, I wish the both of you luck. You're entering into the wild and wonderful world of devices that you actually own!

that was a great post im in the same boat as those guys above and im sure we are not the only ones, when you say put the file on the root of the sd card what is the root of the sd card? if i dont know that should i just not even be rooting?
edit
I just downloaded rom manager and i get the same response " an error occurred while attempting to run priviliged commands" i went through the root process and it said i was rooted, i read earlier that to check it i was rooted and nand unlocked that if i checked my hboot and it was 0.76 i was rooted and nand unlocked if i was 0.79 the root didnt work i was .76. Is there a different way to check if my root went through

The root of the SD card is the 'directory' you're in when you plug the card into the computer & you see folders like ".Mail" "Android" "DCIM" etc.
It's up to you if you think you can handle rooting. I used SimpleRoot & it was incredibly easy, but i have been familiar with modding phones for awhile now.

jdjozwia said:
that was a great post im in the same boat as those guys above and im sure we are not the only ones, when you say put the file on the root of the sd card what is the root of the sd card? if i dont know that should i just not even be rooting?
edit
I just downloaded rom manager and i get the same response " an error occurred while attempting to run priviliged commands" i went through the root process and it said i was rooted, i read earlier that to check it i was rooted and nand unlocked that if i checked my hboot and it was 0.76 i was rooted and nand unlocked if i was 0.79 the root didnt work i was .76. Is there a different way to check if my root went through
Click to expand...
Click to collapse
The root of something simply means not in a folder, e.g. on your computer it would be just G:/ (or whatever letter your SD card is mounted to). Just open the SD card and put whichever file you are referencing right there, not in any folder.
By the way, anyone can root, so long as you are willing to learn and willing to take a few risks. As long as you stay well informed, you usually don't break anything. And there is usually a way out, even if you make a train wreak, though it may be ugly. Independent developers (not me; smart people like Cyanogen and Toast who actually make these awesome ROMs and roots) have a better track record for keeping dangerous stuff out than some corporations. ***Cough***McAfee antivirus broke thousands of computers with a defective update***Cough*** Scientia est vox. Knowledge is power. Know what you're doing, and you'll be fine. You will make mistakes (I know I have), but stay sharp and know the consequences, how to go back, who to ask when things go South, and you'll do alright. The community here at XDA is one of the best and most helpful I have ever seen. If you're not totally hosed, someone will pull you out of the fire. It probably won't even be me. I'm no pro. But there is no shortage of pros here at XDA.

so what would you guys say the next step for me is, should i just do the simple root over? how can i check to see if im rooted? and what should i do about this rom manager giving me trouble with flashing the clockwork mod

See Above
jdjozwia said:
so what would you guys say the next step for me is, should i just do the simple root over? how can i check to see if im rooted? and what should i do about this rom manager giving me trouble with flashing the clockwork mod
Click to expand...
Click to collapse
If titanium backup works, you have root. As for Clockwork, please see my first post, where I went over it in detail.

OK well i installed titanium back up and busy box and it looks like im rooted? Im going to try to flash that superuser app tmw i left my usb cord at work so in about 12 hours ill probly be back with more questions
thanks for the encouragement the answers and most of all your time

Cut the cord
jdjozwia said:
i left my usb cord at work
Click to expand...
Click to collapse
It's personal preference, but there is a throughly cool free app called Awesome Drop that lets you send files without a cable. When you use it, files end up in the /drop directory on your phone. If necessary, you can move them out with a program like Astro File Manager.
By the way, Titanium backup shouldn't work without SU app, so I'm wondering if you do in fact have it. Have you looked through the S section of the App Drawer?

Techrocket9 said:
It's personal preference, but there is a throughly cool free app called Awesome Drop that lets you send files without a cable. When you use it, files end up in the /drop directory on your phone. If necessary, you can move them out with a program like Astro File Manager.
By the way, Titanium backup shouldn't work without SU app, so I'm wondering if you do in fact have it. Have you looked through the S section of the App Drawer?
Click to expand...
Click to collapse
I just went through my S' and all i have are the ones that came with the phone no super user but when u say it shouldnt work what should happen when i open the app?

jdjozwia said:
I just went through my S' and all i have are the ones that came with the phone no super user but when u say it shouldnt work what should happen when i open the app?
Click to expand...
Click to collapse
It should complain about being unable to acquire root privileges.
___
An army of pacifists can be defeated by one man with the will to fight.

yeah when i open it it doesnt say that and it says my root access is ok,
I DL astro and when i open it one of the folders is clockwork mod and if i search i find super user app on my sd card when i reboot my phone by holding the down volume it goes to the hboot screen and askes me if i want to update my phone i say no and then when i go to recovery it does not give me the option to flash the super user app. it takes me to android system recovery with four options. At the very bottom it says E: cant open/cache/recovery/command
?

Is one option to flash zip from SD card?
___
An army of pacifists can be defeated by one man with the will to fight.

How to check if you are root: Assuming you have ADB installed (you used simpleroot so, possibly not) just type "adb shell" into a command prompt. If it comes up with a "#" you are root, if it comes up with "$" type "su" and hit enter, if it switches to a "#" you are rooted. Also you can get a terminal emulator app (I love Better Terminal Emulator) and open it, type "su" and see if it gives you "#".
Did you do the SimpleRoot step where you replaced the recovery with your recovery of choice? I know more than one person that didn't do that step. Though the app should at least still TRY to reboot.
As said before, check your SuperUser permissions to make sure you didn't disallow Rom Manager.
As for CM6, don't get me wrong, I LOVE CM6, but, Fresh 1.0.1 or the latest Damage Control might be a safer bet. For your first rom CM6 needs more coaxing than you might like. Also tethering is installed by default in the 2.1 roms from those guys and it's (imho) easier and more obvious to use.
Keep at it, there will be times you feel like giving up even after you get past this point, just don't take it too seriously and remember that as long as you are still getting phonecalls your phone is still doing it's primary job, the rest is just icing. Icing that gets more delicious with time, like beer, mmmmmm beer.
Where was I?
Oh yeah, good luck!

Crap, forgot, when someone says "put it on the root of the SD card" the easiest way to do that is hook it up via USB, hit the status tray that says "usb connected" and check the Hard Drive option. Then just copy your file to the new drive that will show up in windows (might pop up automatically depending on your windows settings) and boom, it's on the root of the SD card.
As for the "real" way to flash. Do the above, putting the .zip file containing whatever rom you want (for instance CM6, or Fresh 1.0.1 which you can obtain over in Development forum from their respective posts) on the root of the SD card. Safely remove the device (on windows it will be in your status bar, usually looks like a plug with a green arrow, click it, choose Mass Storage Device and then hit Stop, it will tell you when its done, make sure you have the folder closed before you do this or it will grump at you) and switch back over to Charge Only on your phone. Then power off the phone (hold the power button with the phone unlocked, choose Power Off, then Ok) and hold the volume down button. Then press power, don't let go of volume down but you don't have to hold power, just press it to turn it on. A white screen should come up, let go of the volume button, and one option will be Recovery. Use volume up and down to select it and press the power button to select. It should then boot you into recovery which should have an option to "wipe", you want to wipe dalvik cache, then cache, then factory defaults. Then go back up (in AmonRA that means hitting vol-up and vol-down at the same time), then goto "Flash .zip from sdcard" select it, hit power, select the zip file, power again, power one more time to confirm.
Once it's done you hit Reboot System Now and viola, first boot takes FOREVER so don't fret.

alcaron said:
How to check if you are root: Assuming you have ADB installed (you used simpleroot so, possibly not) just type "adb shell" into a command prompt. If it comes up with a "#" you are root, if it comes up with "$" type "su" and hit enter, if it switches to a "#" you are rooted. Also you can get a terminal emulator app (I love Better Terminal Emulator) and open it, type "su" and see if it gives you "#".
Did you do the SimpleRoot step where you replaced the recovery with your recovery of choice? I know more than one person that didn't do that step. Though the app should at least still TRY to reboot.
As said before, check your SuperUser permissions to make sure you didn't disallow Rom Manager.
QUOTE]
where exactly do i type adb shell? when i did the simple root i do not remember replacing my recovery with a recovery of my choice so thats probly where my problem is and i do not know how to check my superuser permissions
Click to expand...
Click to collapse

Techrocket9 said:
Is one option to flash zip from SD card?
___
An army of pacifists can be defeated by one man with the will to fight.
Click to expand...
Click to collapse
no the option i get is update to zip and when i click that it does stuff for me and i cannot choose a file i think my problem lies to not choosing what recovery i wanted?

jdjozwia said:
no the option i get is update to zip and when i click that it does stuff for me and i cannot choose a file i think my problem lies to not choosing what recovery i wanted?
Click to expand...
Click to collapse
It is possible. The program I mentioned earlier (unrEVOked) should install a custom recovery for you. I can't put a link in this post because I'm on my phone, but a quick google search should find it.
An army of pacifists can be defeated by one man with the will to fight.

jdjozwia said:
alcaron said:
How to check if you are root: Assuming you have ADB installed (you used simpleroot so, possibly not) just type "adb shell" into a command prompt. If it comes up with a "#" you are root, if it comes up with "$" type "su" and hit enter, if it switches to a "#" you are rooted. Also you can get a terminal emulator app (I love Better Terminal Emulator) and open it, type "su" and see if it gives you "#".
Did you do the SimpleRoot step where you replaced the recovery with your recovery of choice? I know more than one person that didn't do that step. Though the app should at least still TRY to reboot.
As said before, check your SuperUser permissions to make sure you didn't disallow Rom Manager.
QUOTE]
where exactly do i type adb shell? when i did the simple root i do not remember replacing my recovery with a recovery of my choice so thats probly where my problem is and i do not know how to check my superuser permissions
Click to expand...
Click to collapse
If you just did SimpleRoot (i.e. didn't download the android SDK) you probably don't have ADB installed on your PC. So then you'd want to go the terminal route. Search the market for Better Terminal Emulator
Click to expand...
Click to collapse

DISCONTINUED - [ROM][21-04-2011][patch update] ElocityMod v1.42 for Elocity A7

!!This is ONLY for Elocity A7!!!
This Mod is based on Elocity Stock with additions from Nvidia SDK, to make a better functioning stock rom with google apps.
You can also follow updates on Twitter now: Dexter Picard (DexterPicard) on Twitter or
for the continued support or you can visit my homepage at Dexter's mods
I Thought this demo deserved to be posted with my Mod for ElocityA7
I get some creds here too , thanks!
Installation Instructions:
ALWAYS HAVE CHARGER CONNECTED WHEN UPDATING A FIRMWARE
Download ElocityMod v1.42 patch update
Download ElocityMod v1.41
It will require Wipe/factory reset as well. as reports on the update seems to report some problems if not, so its your own if it does FC alot, if you do not wipe
PATCHES
installs like regular full updates: rename to Update.zip and run recovery.
- v1.xx Adhoc patch here if you need connecting to mobile teetering app, it will not autostart wifi after sleep.​
Previous releases
Download ElocityMod v1.3
Download ElocityMod v1.2
Install using recovery menu.
copy the file to the root of your sdcard and rename to Update.zip.
Enter "Recovery menu" by pressing power for 2seconds, release
then hold power button until "hold power 5sec...." appear and wait until it says booting recovery kernel..and release power button.
Press "HOME" button to see menu, use SEARCH/BACK button to navigate.
select "Wipe/factory reset" - press MENU key to activate
then select "apply sdcard:update.zip" - press MENU to activate
after the small install process - press "reboot" to finalize and wait for the upgrade to take place on second screen that appear.
[/INDENT]
ISSUES
- Files manager app does FC too much, use the OI filemanager for local filehandling.
CHANGELOG
v1.42
- added latest 17-04 update from ElocityA7 update.
- Fixed sdcard problem, you can now eject/insert as much as wanted.
alternate patch is now removed.
v1.41
- build.prop (ro.kernel.android.checkjni=false) enables Skype to function (and maybe other apps)
- usb stick support added.
- changed sdcard handler to stock, but with exception it only work until you eject sdcard/usb , and a reboot is only way to remount (or restart vold daemon which is from a shell)
- honeycomb bootanimation added.
- Files app added (for copying network files to tablet) is buggy with pictures handling in folders. (might be removed again)
- VPN (script + vpn settings enabled/added)
- HDMI resolution changer added in settings (480p -> 1080p output available)​v1.4
- Based on latest 24-02 update from Elocity.
- Cracked the sdcard issue, and its fully working now..
- Added patched hulu Flashplayer 10.2 (uninstall this one first, if you download it from market)
- New calendar app​v1.3
- finally latest Market app included (2.2.7 will be upgraded to 2.2.11 when you enter market the first time)
- Added Gsensor fix, so screen rotation works, if playing games that need sensor like SpeedX or racing games..
- Added DSP audio manager with EQU function (does help increasing volume a little too)
- re-arranged process, so installers do not keep trying to install apps.​v1.2
- Updated to latest stock of Feb-04 .
- removed wifi Settings again, solution did not work (im told)
- Fixed Calendar app FC.
- Updated Market to the latest release.​
THANKS to all who donated up to now! its appreciated, and shows that people like the extras added...
WARNING: Use this image at your own risk and i take no responsibility if you brick your tablet..​

Reserved for future use..

This will be very helpful for a lot people. Great of you to put this together for everyone!

Just curious, what's the advantage of having the superuser app when the device is rooted out of the box?
I look forward to seeing what else can happen with this device, and would be happy to test if needed.

DroidxRage said:
Just curious, what's the advantage of having the superuser app when the device is rooted out of the box?
Click to expand...
Click to collapse
although its already in non-secure mode, the apps that run "su" dont recognise it, so the root app is required together with its "su" command.
and it actually also have the advantage of you being in control of which apps get root access..
although your "adb shell" is in a root shell, the apps running still has non-su rights to the system, otherwise its would be pretty open as well and without much security.

I went ahead and applied version 1.0a over 1.0. I didn't take the time to do a backup so I didn't wipe/factory reset first. Everything went well, but calendar still gets a force close upon launch (not a problem for me, I don't need it). I may go ahead and wipe it and reinstall 1.0a, but I'm very happy with it as is for now.
Thanks again for making this rom! I'll hit that donate button for sure.

Thanks Dexter, tossed a donation your way.

I couldn't get root access back so I'm rerunning the update after a full wipe of data and cache. I will let you know how it goes.
rich_e said:
I went ahead and applied version 1.0a over 1.0. I didn't take the time to do a backup so I didn't wipe/factory reset first. Everything went well, but calendar still gets a force close upon launch (not a problem for me, I don't need it). I may go ahead and wipe it and reinstall 1.0a, but I'm very happy with it as is for now.
Thanks again for making this rom! I'll hit that donate button for sure.
Click to expand...
Click to collapse

rich_e said:
I couldn't get root access back so I'm rerunning the update after a full wipe of data and cache. I will let you know how it goes.
Click to expand...
Click to collapse
I lost root access loading this rom too. It tried to update su but couldn't.

DroidxRage said:
I lost root access loading this rom too. It tried to update su but couldn't.
Click to expand...
Click to collapse
Couldnt install the su zip file it put on my sd either..

I couldn't get SU to update either (placed on SD card as update.zip, but no joy). Just for grins I tried Z4root too, it went through the motions but no root. I tried to use Titanium Backup to install busybox. It downloaded the binaries but nothing changed.
DroidxRage said:
I lost root access loading this rom too. It tried to update su but couldn't.
Click to expand...
Click to collapse

rich_e said:
I couldn't get SU to update either (placed on SD card as update.zip, but no joy). Just for grins I tried Z4root too, it went through the motions but no root. I tried to use Titanium Backup to install busybox. It downloaded the binaries but nothing changed.
Click to expand...
Click to collapse
I cant see what the problem is... dex any ideas?
I may flash the offocial update, reinstall the modified build.prop, and reinstall market.

The was a post somewhere in the BJ's 299 thread about busybox not installing correctly due to differences in the directory structure on this device, which caused loss of root.

rich_e said:
The was a post somewhere in the BJ's 299 thread about busybox not installing correctly due to differences in the directory structure on this device, which caused loss of root.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=10097888&postcount=750
Gonna try that now

DroidxRage said:
http://forum.xda-developers.com/showpost.php?p=10097888&postcount=750
Gonna try that now
Click to expand...
Click to collapse
This didn't work... other than this superuser permissions being messed up everything else works stellar!
If we don't have anything soon, I'll flash back and poke around with the modified build.prop on the official build.
Edit: Reinstalled the official elocity update and got my root back, installed gapps, now updating build.prop. Hopefully this gets me all the market fixes minus that Su thing. Superuser app is available in the market too. Report back soon.

So you're basically just using the build prop settings out of this rom with the factory update? I went back to version 1.0 for now.

rich_e said:
So you're basically just using the build prop settings out of this rom with the factory update? I went back to version 1.0 for now.
Click to expand...
Click to collapse
Yeah pretty much!... did you not have the SU issues with version 1.0? If not I'll just update to that. I can't get Bank of America or Tasker to install even using the build.prop from the ROM, there's something other than the fingerprint in this ROM making the magic happen.

Titanium back up reports root access with V1.0 and I can get the # at the prompt in terminal. Lots of other apps that wouldn't install with the eLocity update install just fine with it too.

im a little confused..
i added the "su" command to the build, it never was there...
i added Superuser.apk as well.. and if you're trying to add those on top , you might corrupt it, and also,
VERY IMPORTANT filesystem has 0 bytes free, so any copying will probably corrupt the su command or other copied files..

Does this rom support ad-hoc wifi tether?

[MOD] Quick & Easy Root Script - HC

This should work for any and all a100 Honeycomb builds, you'll need to install an app from the market called terminal emulator. Also, you'll need a file manager like Astro to unzip the file.
This mod should root your tab in a matter of seconds after the script file is launched. I've tested this on my tab from a clean build and it works like a champ.
Here we go!
- Install the following apps from the market:
Terminal Emulator
https://market.android.com/details?id=jackpal.androidterm&hl=en&rdid=jackpal.androidterm&rdot=1
Astro File Manager
https://market.android.com/details?id=com.metago.astro&hl=en
- Download the attached file from this post.
- Extract and put both the root.sh and su in /mnt/sdcard from the root.zip file.
(Using Astro, find the root.zip file it might be in /mnt/sdcard/Downloads or could be else where if your not using the website to view XDA. Copy it from where ever it's at and paste it in /mnt/sdcard. Press your finger on the zip file and tap Extract when the menu pops up. Tap "Extract to This Directory".)
- Next, open terminal emulator and copy / paste the following:
sh /mnt/sdcard/root.sh
Text will fly by, the script will automatically copy the su binary and install it to the proper location.
Once the script finishes running, be sure to install superuser from the market:
Very Important, if you skip this you won't be "officially rooted yet"!!!
https://market.android.com/details?id=com.noshufou.android.su
Open the superuser app once it's installed, click on the wrench in the upper right corner, scroll to the bottom and find "Su binary v... Tap to check for updates" and tap that link. It should bring you to an update screen, click the button at the bottom to update!
Once you have done the above, then install busybox, Titanium, etc.. if needed.
Thanks goes to abliss for origionally coming up with the root commands!
This mod really just automates his work.

permission denied every step of the way. Used both script manager and terminal

ok terminal manager is out, I didn't realize that doing a hard reset wouldn't wipe the /system/xbin directory completely so technically busybox tools were still installed and sh wouldn't normally be there. I'll see if there's another way..

this method work for any build? and if so, is there any problem during the process that could "kill" my a100 or it's safe?

This method should, yes and it's safe.. It's actually more safe (if that's possible) than the method origionally posted in the dev section since there really isn't any room for user error.
Sent from my MB860 using XDA App

Ill give the new method a go around tomorrow and report back for you.

I wasn't expecting it to anyway, but I figured I'd let you know this doesn't work on the A101.
Hoping someone can find a working root method for this model.

Sorry to hear about the a101, that thing sounds like a tough nut to crack!
Sent from my MB860 using XDA App

This working for me i manage to root my a100

It works and its so simple
Thank you so much for this! It was so easy. Though the only problem I had was with the terminal emulator, no fualt of the Dev, but it might help someone. When I was trying to write in the line of code I kept getting errors because I couldnt get the keyboard to write lower case. So copy and paste if your a noon like me to get it through the terminal.

Well, I dont know what the hell is up with my tab, but Even this didnt work. It showed the file was there, but after I tried installing SU, it didnt get root, so I went back in to verify the file was still there, and nope. It disappeared. I have no idea how, unless somehow mine device is checking the directories, which is the only thing I can think of...

mvan4310 said:
Well, I dont know what the hell is up with my tab, but Even this didnt work. It showed the file was there, but after I tried installing SU, it didnt get root, so I went back in to verify the file was still there, and nope. It disappeared. I have no idea how, unless somehow mine device is checking the directories, which is the only thing I can think of...
Click to expand...
Click to collapse
You sure you don´t have an a101? what build number are you running?

A100_2.007.04_COM_GEN1
Most definitely an A100...

mvan4310 said:
A100_2.007.04_COM_GEN1
Most definitely an A100...
Click to expand...
Click to collapse
I have no idea then.. the only thing I could say is to try and restore from a "Full" rom, like Acer_A100_1.014.08_COM_GEN1 and try to root it before doing anything else. It wouldn't hurt to try anyway and the worst that could happen is that you'd have to restore all your apps and stuff. If we can ever get this thing to run cwm and a different kernel, you'll definitely be needing root.

Works great!
Thanks so much for the script and instructions. Im enjoying my rooted tab yay!

mvan4310 said:
Well, I dont know what the hell is up with my tab, but Even this didnt work. It showed the file was there, but after I tried installing SU, it didnt get root, so I went back in to verify the file was still there, and nope. It disappeared. I have no idea how, unless somehow mine device is checking the directories, which is the only thing I can think of...
Click to expand...
Click to collapse
Did you check the boxes for USB Debugging and Unknown sources just in case?? (in Settings > development)

I checked them both. Root Checker shows I have root, but other apps cant get root access, and SuperUser cant update because of this issue... I dont know what the hell to do because this has me stuck atm... Im gonna flash back to 1.018 and see if that helps, probably not, but it wont hurt to check.
EDIT:
I reverted back and got root. It seems to be the newest update that stopped it. Im updating back up again to see if I retain root. What a pain...
Edit 2:
Yep, Im rooted now. It unrooted me when updating, ran the script you provided and its working now. Dont know why it didnt take before reverting back, but works wonderfully now. Now that Im rooted, let me know what I can do and peek around at to help out here.

Has anyone tried that on an A500?

A500 has its own rooting methods. You can find info about the A500 here
http://forum.xda-developers.com/forumdisplay.php?f=1136

Thanks alot crossix. Worked like a charm.
Sent from my A100 using Tapatalk

Easiest way to root HTC Evo Desing 4G

Okay, ive been doing my research, and I lasted aprox. 4-5 days and its sadly to know but this phone (HTC Evo Design 4G / Kingdom / Hero S) doesnt have that much of fame. But I was crazy trying and trying alot of methods trying to root my phone, but just couldnt. I was about to give up, until I found a Guide, and made it possible for me to root the phone, so I decided to share this guide to you guys, to who ever has a HTC Evo Design 4G / Kingdom / Hero S. Credits go to LOLINTERNET who wrote this guide. :good:
Ok, here we go. :laugh:
In order to root your Evo Design you'll need to unlock your bootloader, flash recovery, flash su binary, and install superuser and busybox. In this guide I will try to explain these steps as simply as I can. My goal is for it to be thorough enough that anyone that reads it can root their phone and enjoy the full benefits of this nifty little phone.
First and foremost, you will need to install the Java SE Development Kit. You won't use this directly in any way, but you need it in order to install the Android SDK.
Click Here To Download SDK
After installing the Java JDK, you will have to install the Android SDK which contains two tools that are essential to gaining root. They are adb (Android Debug Bridge) and fastboot. These tools are used to send files to your phone from a Windows command prompt. You will need these tools to unlock your bootloader and flash recovery.
Click Here to Download Android SDK
Instructions on installing the SDK
How to add packages to the SDK
Once you have the Java JDK and the Android SDK installed you will need to install the proper drivers for your phone. This one is pretty straightforward and necessary for your phone to be recognized while plugged into your computer. After you have the HTC drivers installed you can begin the fun parts, but first you will need a few things. :good:
HTC Drivers CREDITS TO: CNexus
You will need a recovery.img. 2fast4u88's unofficial ClockWorkMod Recovery version 5.0.2.7 and 5.0.2.8 are the only two recoveries I have used since I got my Evo Design. Many thanks to him for putting in so much work to get this device where it is today.
Download Recovery
Also, you'll need su binary version 3.0.3.2 efghi. This is the actual file that will root your device. It is a flashable .zip file that you save to your sdcard and flash in recovery. You'll be amazed at how easy this step is.
Download for su binary version 3.0.3.2 efghi
Download for su binary version 3.0.7 efghi
3.0.3.2 binary is for Gingerbread and 3.0.7 is for ICS
The superuser app is like the control center for apps that request root permissions after you're finally rooted. You will need to install this app and then Busybox, both of which can be found in the Google Play Store. After installing the Busybox app you will need to actually install busybox. The app itself is basically an installer for Linux applets that are required by root apps such as Titanium Backup and Root Explorer among many others.
Now that you have a basic overview of what it is you will be doing and the files need to do it, the only thing left is to actually perform these steps and root your device. So, lets do this!
1. Unlock your bootloader at htcdev.com. You will need to sign up and you will be warned that unlocking your bootloader will void your warranty. Once you've followed all instructions at the website an unlock token will be emailed to you. DO NOT DELETE THIS FILE. You can place it in the platform tools folder of the Android SDK and use fastboot in command prompt to relock and unlock your bootloader whenever you like. Also, anytime you unlock your bootloader all data will be wiped so be sure you sync all your contacts and backup other information first before performing this step.
2. After unlocking your bootloader you will need to flash a recovery.img. The manual way to flash recovery is to place the downloaded recovery.img for 2fast4u88's unofficial ClockWorkMod recovery port of version 5.0.2.7 in the platform-tools folder of the Android SDK. Power down your phone but be sure that Fast Boot in Power under the settings menu is unchecked or it will just reboot normally instead of into bootloader (also called hboot) like you want. After it's been powered down for a minute or two, press and hold Volume down then press and hold the power button. When the white HTC splash screen appears you can let go. Scroll down with the volume down button and select fastboot by pressing power. Plug your phone into your computer and open a command prompt, then run these commands without quotations.
"cd C:\android\platform-tools" (This is where adb and fastboot live. It may be different for you depending on where you installed the SDK. I always suggest installing it to the root of your C: drive.)
"fastboot flash recovery recovery.img"
Should only take a few seconds, then you have yourself a recovery partition and you can proceed to the next step after rebooting. Yay!
3. Next, we're going to flash the su binary in recovery. First, you'll need to place it on your sdcard. Doesn't matter where exactly just as long as you can find it. I would suggest the root of your sd just to make things easier on yourself. After you have the su binary zip saved to your sdcard power off your phone and boot into hboot. Now, I can't remember which, but either hboot or fastboot will have an option to boot into Recovery. Once you're booted into recovery, select "install zip from sdcard," then "choose zip from sdcard." Scroll down and find the su binary then select it. Pressing the Up Vol button will take you directly to the end if you don't want to scroll all the way through. After selecting the su binary zip select "yes" to flash. It's a small file, so it won't take long. When it's done select "reboot to system" and we'll move on to the next step because you just rooted your phone.
4. But, you're not done yet. You need to install the superuser app and the busybox app in that order. This is the easy part because both apps are free in the Play Store. Install Superuser, then Busybox. You shouldn't have to interact with the Superuser app, but if you want to set an automatic response to apps that request root you can open it and go to Preferences. Scroll down and you should see a few options. I have mine set to automatically grant su permission to apps that request it because I have no reason not to lol. I also unchecked the option to receive a notification every time an app is granted root permission because that junk just gets annoying. Next, after you install the Busybox app, you'll need to actually install Busybox. The app is merely an installer for the actual Busybox applets that govern root apps. The app should open automatically after you install it. You should see it in your notification bar. Open it up and follow the prompts. When you're done, reboot your phone.
5. Check If you have rooted your phone successfully, download Root Checker on Play Store.
6. Congratulations! You should now have a rooted Evo Design 4G. Enjoy. I hope this guide is both complete and comprehensive enough that everyone can enjoy the benefits of having a rooted device, but if I've missed something or if you have any questions whatsoever, please post them here and I will do my best to answer them in a timely manner. I hope you enjoy rooting your device, but please be careful. You now have administrator privileges, so use them wisely. I would highly suggest installing Quick Boot from the Play Store so that you can boot into recovery easily without having to go through hboot. I would also suggest using your newly installed app that requires root access to boot into recovery and make a backup. If anything should ever happen to your phone's system and data you will have a backup and can restore it to that state. Again, I hope you enjoy. I apologize for this being such a lengthy guide, but hopefully you understand the wonderful world of Android a little better for having read it. :good:
*EXTRA* 7. I recommend doing a backup via recovery of your phone, because this phone doesnt seem to have any roms or any stock roms etc, so i recommend making a backup, but dont worry, ill try to make a backup ROM so there could be one on the internet, because I searched and could find one! :s

Great post Julio. I saw this post somewhere else but I could not remember were.
Will this work on a Freedompop version of this phone?
THe evo design 4g FreedomPop version IS supposed to be already rooted. But when I try to load SU from the app store it says su binaries are out of date. Will flashing these binaries do the trick for it to accept it?
If it is rooted, do you think all I need to do is update that damned su binaries file?
Hope you still visit this site because those are my first questions towards doing some goodness towards my Evo!
Hope to catch you later.

maikalwolf said:
Great post Juan. I saw this post somewere else but I could not remember were.
Will this work on a Freedompop version of this phone?
THe evo design 4g FreedomPop version IS supposed to be already rooted. But when I try to load SU from the app store it says su binaries are out of date. Will flashing these binaries do the trick for it to accept it?
If it is rooted, do you think all I need to do is update that damned su binaries file?
Hope you still visit this site because those are my first questions towards doing some goodness towards my Evo!
Hope to catch you later.
Click to expand...
Click to collapse
Lmao, its Julio! :laugh: and yea I think that will do it!! Try flashing the su binary I have up in the post! Do you have CWM Recovery?

re you follow up question
julio626 said:
Lmao, its Julio! :laugh: and yea I think that will do it!! Try flashing the su binary I have up in the post! Do you have CWM Recovery?
Click to expand...
Click to collapse
Yes, the phone was rooted and just needed the new binaries, which I promptly fixed. I have also put a link to your page to the instruction for others to use.

maikalwolf said:
Yes, the phone was rooted and just needed the new binaries, which I promptly fixed. I have also put a link to your page to the instruction for others to use.
Click to expand...
Click to collapse
Thanks man!

Gracias Julio
It was quite tedious to be honest. But reading your guide and this one how-to-unlock-the-bootloader-of-any-htc-device en cultofandroid I finally was able to root my phone. Thank you so much!

Amazing
This is the best guide I have ever found. It was fluid and easy to understand for me. Just went from my JB IPhone 5 (cellular happened to break). now i have this phone lol (but its so slow and useless I decided to root and it was an unbelievable pain.. nothing worked). Then I found your guide which is fantastic, completely like no other. I am very impressed with it and just wanted to say THANK YOU!!!!!! :good:

So Close PLEASE can you help.
I followed this guide about a year ago & got to the image you see linked h**p://i.imgur.com/zfle9n7.jpg To be blunt I do not recall where I left off in the rooting process except to say I'm dead ended. Where did my efforts go wrong and what do I need to do in order to finally get this rooted? Also please tell me what bearing info in this thread: h**p://forums.androidcentral.com/htc-evo-design-4g/142434-s-off-s.html may have on my results. THANK YOU

Help needed! Cannot access 'SD card' files on Pixel 3XL

I set up my new phone yesterday - rooted with some great help from folks on this forum. Everything was going smoothly and working properly until I did something (I was checking out All-in-One Toolbox and a screen popped up about a four-step process to select some particular 'file'). As a result, there are problems with my ability to access local files, for example:
When I open the built-in Files app, it displays an hourglass symbol with the message "Can't load content at the moment". Also, on the slide out panel, the icon that previously read 'Pixel 3XL' is missing.
When I tried to get a screen grab of the above, a notification indicated "Cannot save screenshot due to limited storage space".
When I launch Titanium Backup, it cannot find its backup folder.
Custom ringtones are not be used.
Note that when I use X-Plore, I can navigate to the 'SD Card' folder and all files are there. It is as if a 'symbolic link' was deleted.
Please help me resolve this problem!

groston said:
I set up my new phone yesterday - rooted with some great help from folks on this forum. Everything was going smoothly and working properly until I did something (I was checking out All-in-One Toolbox and a screen popped up about a four-step process to select some particular 'file'). As a result, there are problems with my ability to access local files, for example:
When I open the built-in Files app, it displays an hourglass symbol with the message "Can't load content at the moment". Also, on the slide out panel, the icon that previously read 'Pixel 3XL' is missing.
When I tried to get a screen grab of the above, a notification indicated "Cannot save screenshot due to limited storage space".
When I launch Titanium Backup, it cannot find its backup folder.
Custom ringtones are not be used.
Note that when I use X-Plore, I can navigate to the 'SD Card' folder and all files are there. It is as if a 'symbolic link' was deleted.
Please help me resolve this problem!
Click to expand...
Click to collapse
Just my 2 cents worth, but I've never been a fan of toolkits. They work great sometimes, but then again they don't at times. I think it's better to learn adb/fastboot on your own. I would recommend fastbooting the factory image again, without the -w, and see if that resolves your problem. Then leave well enough alone. And uninstall the toolkit app as well if that's what it is :good:

groston said:
I set up my new phone yesterday - rooted with some great help from folks on this forum. Everything was going smoothly and working properly until I did something (I was checking out All-in-One Toolbox and a screen popped up about a four-step process to select some particular 'file'). As a result, there are problems with my ability to access local files, for example:
When I open the built-in Files app, it displays an hourglass symbol with the message "Can't load content at the moment". Also, on the slide out panel, the icon that previously read 'Pixel 3XL' is missing.
When I tried to get a screen grab of the above, a notification indicated "Cannot save screenshot due to limited storage space".
When I launch Titanium Backup, it cannot find its backup folder.
Custom ringtones are not be used.
Note that when I use X-Plore, I can navigate to the 'SD Card' folder and all files are there. It is as if a 'symbolic link' was deleted.
Please help me resolve this problem!
Click to expand...
Click to collapse
What were you trying/wanting to do when "checking out" the toolkit? I agree with Badger about installing the factory image, but I would go one step further and leave the -w in place just running the flash-all as is. At some point when you have done some normal work on the phone, you can run it again without the -w so you can start to understand what is not deleted as well as how to re-root since you will need to do it every month. From your description, it sounds like you have deleted some stuff on the user side that would not be restored without the -w.

Gents,
I really did nothing with the toolkit other than a) look at the features it offered (was trying to discover which apps were running at boot time) and b) step through the one dialog that messed things up. As such, I would hate to have to reflash and start from ground zero again - especially when I get the sense that there is a simple fix that could resolve this specific issue. (Upon rereading Sliding_billy's response - it seems that reflashing does not impact user files - is this correct? After reflashing, I would have to boot to TWRP, reinstall Magisk, and everything would be good to go?)
FYI - the dialog in question is one that I had seen previously, when I updated my Note 4 from Android 4 to Android 5. It had something to do with selecting the DocumentsProvider location or some such (sorry that I am being so nebulous - I just did a quick search to try to find an example of the dialog, but did not).

groston said:
Gents,
I really did nothing with the toolkit other than a) look at the features it offered (was trying to discover which apps were running at boot time) and b) step through the one dialog that messed things up. As such, I would hate to have to reflash and start from ground zero again - especially when I get the sense that there is a simple fix that could resolve this specific issue. (Upon rereading Sliding_billy's response - it seems that reflashing does not impact user files - is this correct? After reflashing, I would have to boot to TWRP, reinstall Magisk, and everything would be good to go?)
FYI - the dialog in question is one that I had seen previously, when I updated my Note 4 from Android 4 to Android 5. It had something to do with selecting the DocumentsProvider location or some such (sorry that I am being so nebulous - I just did a quick search to try to find an example of the dialog, but did not).
Click to expand...
Click to collapse
Running the flash all with the -w in place will completely wipe your device. If you don't want that then remove the -w. But, without wiping the device there may be something left over that'll continue to cause you your current problem.
Sent from my [device_name] using XDA-Developers Legacy app

groston said:
Gents,
I really did nothing with the toolkit other than a) look at the features it offered (was trying to discover which apps were running at boot time) and b) step through the one dialog that messed things up. As such, I would hate to have to reflash and start from ground zero again - especially when I get the sense that there is a simple fix that could resolve this specific issue. (Upon rereading Sliding_billy's response - it seems that reflashing does not impact user files - is this correct? After reflashing, I would have to boot to TWRP, reinstall Magisk, and everything would be good to go?)
FYI - the dialog in question is one that I had seen previously, when I updated my Note 4 from Android 4 to Android 5. It had something to do with selecting the DocumentsProvider location or some such (sorry that I am being so nebulous - I just did a quick search to try to find an example of the dialog, but did not).
Click to expand...
Click to collapse
jd1639 said:
Running the flash all with the -w in place will completely wipe your device. If you don't want that then remove the -w. But, without wiping the device there may be something left over that'll continue to cause you your current problem.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Exactly what jd said. Running flash-all with no modifications will essentially do a factory restore of that build. Removing the -w (for wipe) from the batch file leaves the non-system files/settings, etc in place and you will then need to fastboot boot TWRP.img and install Magisk. As both of us mentioned, it may be best to get over the pain of a full image instead of seeing what issues remain without the -w in place in the batch. I think the real lesson here is that the folks who make these toolkits do a lot of hard work but it is still better/safer (especially on this device) to understand doing things manually.

I reflashed without the -w and everything seems to be fine. Thanks for the help!