Database Info

UnrEVOked root exploit for EVO and Hero online

Download this apk and install it to get root on your EVO.
It will only root your current ROM. (There's no way to access recovery). Also, any changes to /system will be lost on reboot due to NAND protection. If you need to modify /system or install a new ROM, try toastcfh's method. If you just need to get a root shell in adb or run an app like Auto Memory Manager, Unrevoked should be just fine.
Unlike toastcfh's patch, it will not wipe your phone. If you have data you'd like to backup before applying the more complete root, run Unrevoked, use adb shell, su, and busybox cp to copy the files you're saving to /sdcard. Then, you can use toastcfh's method without worrying about data loss.
As always, thanks to the guys who put this APK together. Happy rooting.
Original (now obsolete) post:
The guys over at unrevoked.com are still sitting on their exploit until they can vet it against the OTA update. However, if you are feeling restless, haven't taken the OTA, and want root without wiping, try this:
Download and decompress http://unrevoked.com/hero-root.zip
Code:
adb push ~/Downloads/hero-root/unrevoked /sdcard/unrevoked
adb shell
cd /sdcard
sh unrevoked
This will install Superuser Permissions on your EVO.
For the record, I have not been prompted for the OTA update. Unrevoked is still working on the OTA-compatible patch. If you take the OTA, I suspect this method will break.
I have no affiliation with the unrevoked people. I just followed cteneyck's lead from the discussion thread last night and thought I'd share my findings.

FYI i found this on the HERO Dev Forum
http://forum.xda-developers.com/showthread.php?t=694572

Can you install recovery image?

How would I do that?
I think this is just a userland root. I can't even adb pull in private directories. I have to use busybox cp to get them over to my sdcard first.

I haven't updated, and haven't rooted with toast's method becuase flashing the data partition to root is ridiculous. Trying this now and will report back findings.

theillustratedlife said:
How would I do that?
I think this is just a userland root. I can't even adb pull in private directories. I have to use busybox cp to get them over to my sdcard first.
Click to expand...
Click to collapse
Theres a recovery image included in the zip. Does it work for hero only?

Do we know the files are the same for the evo? Seems like the recovery at the very least would be different, and this does say HERO-root.zip...
JUST SAYIN'

This works for EVO. I took the plunge for you guys. haha.
{
"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"
}

I'm not comfortable flashing a Hero boot.img to my EVO. The official release should be out in a few days, when we'll know more about this root method, and if we can get real recovery.
The shell script itself does nothing to unlock the SPL, so just running fastboot boot recovery.img returns "remote: not allowed."
Trying to fastboot the recovery image forced me to reboot my phone. I had to run unrevoked again to get root back. As was reported earlier this week, it looks like this method has problems sticking between startups.

$ sh unrevoked
sh unrevoked
Unpacking, please wait...
88 88 88b 88 88""Yb 888888 88 dP dP"Yb 88 dP 888888 8888b.
88 88 88Yb88 88__dP 88__ 88dP dP Yb 88odP 88__ 8I Yb
Y8 8P 88 Y88 88"Yb 88"" 8dP Yb dP 88"Yb 88"" 8I dY
`YbodP' 88 Y8 88 Yb 888888 YP YbodP 88 Yb 888888 8888Y
==================================================================
unrEVOked: root for HTC evo and hero (http://unrevoked.com)
Please wait. This will take up to 30 seconds.
Ready to 'su'.
$ su
su
Permission denied
$ $ su
su
Permission denied
I'm in build 1.32.651.1 CL171253 - I assume this means I have not applied the OTA?
EDIT: Oh nevermind, duh, the SuperUser dialog came up and I hadn't hit allow....

You have to OK the su request on your handset. Type su, then wake your EVO and click Approve.

SO what will happen if i try this method and have the OTA??? Will it brick?

I doubt it would brick - it's just a shell script. It will probably fail to root your phone, but without negative side-effects.

sorry bit of a newb where do i have to put what. and how do i run it. sorry

thorpe24 said:
sorry bit of a newb where do i have to put what. and how do i run it. sorry
Click to expand...
Click to collapse
Just wait for the one-click.

i could do it if i tried, just really lazy been up since 4 am yesterday

so this is PERMANENT? and /system writable during OS? and recovery permanent?

blehzz said:
so this is PERMANENT? and /system writable during OS? and recovery permanent?
Click to expand...
Click to collapse
really... they sure didnt say anything about it....like what it does exactly....

can't get the prompt to allow for the SuperUser apk to install.
No Su

No one has access to a writable /system in android on the evo.
This option is easier but has no recovery.
If you can do better by all means step up and produce. Otherwise stfu about things sucking 1 day after release root wise. Show some class and try not to run off any more developers.
These things take time. Its a work in progress.

One click root/clockwork linux [OSX too!]

This will install joey-krim's root and clockwork recovery 2.5.1.0
*Instructions*
1. Download the root.zip for linux/ if your on a mac download the dropbox link labeled osx
2. Extract the archive
3. Make Clickhere.sh executable/OSX_run.sh (mac version)
4. Run the script
5. ???
6. PROFIT
*Props to joeykrim and noobnl for getting us root*
*Special thanks to firon and nullghost*
here is teh macosx script havent tried it as i dont own a mac (ack) does the same thing as teh linux script, credit goes out to baggage handler for the orginal
http://dl.dropbox.com/u/10162842/OneclickOSX.zip

Appreciate it . Will try now

Thank you so much for this!

since i'm somewhat new to this mac method, am I running this clickhere.ex on my mac terminal?
sorry for the dumb q's
Chris

updated original post with osx method

I really apologize, but when I run this, it keeps saying "no such file or directory"...I'm sorry for all these petty posts. What am I doing wrong?
Chris

im sorry your gunna have to be a bit more specific, i dont have a mac so i dont know how the code is handled

ok, sorry for the vague post ;-)
So, I open the clicknere.sh, and change it to executeable.
After I do that, I click on clickhere.ex, and it opens in a terminal (Phone is plugged in, and in debug).
/root/Clickhere.ex: line 5: /Users/chris/adb: No such file or directory
/root/Clickhere.ex: line 6: /Users/chris/adb: No such file or directory
/root/Clickhere.ex: line 7: /Users/chris/adb: No such file or directory
/root/Clickhere.ex: line 8: /Users/chris/adb: No such file or directory
/root/Clickhere.ex: line 9: /Users/chris/adb: No such file or directory
please wait for the server to start again
I then type in my password, and it spits 21 more lines...all the same as above
I knew I should have kept a windows machine around

clickhere.ex?? dude you need to download the one for your operating system, osx_run.sh for mac, clickhere.sh is for linux.

Thank you. I'll give this a try when I get home. For done reason I haven't been successful with any of the other mac methods.
I'll report back soon.
Sent from my SPH-D700 using XDA App

tested it out on my roomates mac, was annoying trying to figure out how to make it executable from the gui so i just chmod it, runs just fine and he doesnt have adb installed or anything

{
"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"
}

ok, I got it, I forgot to change the directory...stupid! I'm really sorry for the dumb questions.
My final question about this is the final message I'm getting...
"Waiting for device continuing when found...
Cleaning up...
rm failed for /sdcard/zImage, Permission denied"
Why am I getting this??
Thank you in advance again!
Chris

yea i noticed it to, it didnt remove the zimage from the sdcard.. if you dont want it there then mount your usb and remove it via explorer

It keeps spitting back
"rm failed for /sdcard/zImage, Permission denied"
I'm clueless as usual, think i'll just toss this mac in the garbage
Chris

Everything worked and I got RM to boot into CWR. Awesome!!
Made the .sh into executable, used the chmod and then removed the .sh extension.
Ran it. Worked.
Downloaded MixUp Kernel (use any Rom Manager compatible Kernel you wish)
Powered off phone, boot into CWR (Vol down, cam, power)
Flash the Kernel.
Boot and go into Rom Manager and Flash CWR through.
Press, boot into recovery, it will boot into stock recovery for a minute, then put you in CWR and VIOLA! You're good to go to boot into CWR through RM.

How about run terminal. Cd to directory the zip extracted it to. Looks like a folder within a folder with the same name. Then ls. See how the file is named.
sudo ./osx_run.sh
Enter password. It should run. Linux command should be the same thing.

Did it work?

yes, the mac version has an error where it wont delete clockwork zimage off your sdcard. if the 6MB is very important to you then dont use this script, or just delete it off afterwards... your call

When running 'clickhere.sh' in terminal, I receive:
Code:
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
please wait for the server to start again
List of devices attached
???????????? no permissions
will continue in 5 seconds
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
Dont forget to install SuperUser from market
remove stock recovery patcher
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
installing clockwork
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
rebooting please hold
This seems to actually point to permissions on the actual device. Other than turning USB Debugging on, what other permissions need to be reviewed?
Thanks.
edit: I am rooting my Samsung Epic 4G.

[Solved] Problem restoring root via OTA rootkeeper

I made a dumb mistake. Sometime back i had mistakenly deleted the contents of the sdcard after voodoo rootkeeper su backup. Forgot about the su backup!
Updated the latest update, without backing up again.
Rootkeeper shows that su copy is available but doesn't restore.
{
"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"
}
Tried cold booting, multiple restarts, everything in vain.
Question is, can I restore root from the backup of other users in the forum? Or is it device specific?
Somebody care to upload the contents of the folder if it doesn't give away any personal data?
Thanks.
Sent from my Asus TF300T

Tell us more, please.
Are you on JB or ICS ?
Have you tried to cheched "device rooted" and "root permission granted"
and finally click on "Restore root"

philos64 said:
Tell us more, please.
Are you on JB or ICS ?
Click to expand...
Click to collapse
I am currently in JB (v10.4.2.13).
Tablet is not unlocked
Vodoo OTA Rootkeeper restored fine when I updated from ICS(9.4.3.30) to JB (10.4.2.9).
The check-boxes will be checked by the app not manually AFAIK.
Anyhow gave it a try, not clickable
Stupid of me not to backup before updating

It's possible to have backup of rootkeeper?

I have solved so, removed supersu, instal superuser from market.
Restore root from rootkeeper and all ok.
Remove superuser and reinstall supersu.
Now I have root access.
Inviato dal mio ASUS Transformer Pad TF300T con Tapatalk 2

Root Achieved
Solved the problem.
Followed the steps in the thread posted here
Steps:
Most of the commands are copy-paste from the thread just modified for this specific problem (I do not take credit for these steps).
Download View attachment su.zip from this post (thanks to calisro)
Extract the contents to a folder.
Start a cmd window in that folder and logon to adb
In adb shell type
Code:
/system/usr/we-need-root/su-backup
(check the file availability in that folder and the file name and correct the command accordingly)
Confirm whether you have root. The adb shell prompt should be # not $, also can be confirmed by typing id and should echo something like this "uid=0(root) gid=0(root)"
Remount system as RW:
Code:
mount -o remount,rw /dev/block/mmcblk0p1 /system
Open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
Code:
adb push c:\<some path>\su /sdcard/
Then copy it to /system/bin from the adb session where you got root.
Code:
cat /sdcard/su > /system/bin/su
Change permissions for SU
Code:
chmod 6755 /system/bin/su
Download superuser (NOT SUPERSU) from play store if you do not have it already.
Force superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
congrats. your now re-rooted.
Think, this will solve the problem plaguing few people who could not restore root after latest OTA.
Thanks to calisro for his easy to understand steps (please rep him in the thread, if this helped you)

k1chy said:
Solved the problem.
Followed the steps in the thread posted here
Steps:
Most of the commands are copy-paste from the thread just modified for this specific problem (I do not take credit for these steps).
Download View attachment 1338410 from this post (thanks to calisro)
Extract the contents to a folder.
Start a cmd window in that folder and logon to adb
In adb shell type
Code:
/system/usr/we-need-root/su-backup
(check the file availability in that folder and the file name and correct the command accordingly)
Confirm whether you have root. The adb shell prompt should be # not $, also can be confirmed by typing id and should echo something like this "uid=0(root) gid=0(root)"
Remount system as RW:
Code:
mount -o remount,rw /dev/block/mmcblk0p1 /system
Open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
Code:
adb push c:\<some path>\su /sdcard/
Then copy it to /system/bin from the adb session where you got root.
Code:
cat /sdcard/su > /system/bin/su
Change permissions for SU
Code:
chmod 6755 /system/bin/su
Download superuser (NOT SUPERSU) from play store if you do not have it already.
Force superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
congrats. your now re-rooted.
Think, this will solve the problem plaguing few people who could not restore root after latest OTA.
Thanks to calisro for his easy to understand steps (please rep him in the thread, if this helped you)
Click to expand...
Click to collapse
It works fine.
Thank you k1chy & calisro

nevermind, figured out.
thanks for the tutorial

It will be nice if this was a sticky
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Thank you! The last OTA that my tablet took resulted in me not being able to restore root. OTA RootKeeper kept freezing up and doing nothing. This helped me in restoring root!

Thanks a million
k1chy said:
Think, this will solve the problem plaguing few people who could not restore root after latest OTA.
Thanks to calisro for his easy to understand steps (please rep him in the thread, if this helped you)
Click to expand...
Click to collapse
Thanks a million!!
Couldn't recover root on a Razr M after JB OTA - tried all of the exploits around the forums but NONE worked
- This, however, worked a treat!!! :victory:

[Guide][Win-Linux-Script] The Easiest Ways For Getting All Device's Mounting Points

For Non-Rooted Devices and Rooted Devices​
Here is a summary on how to get mounting points without rooting or extracting recovery.img.
The different procedures only needs to have adb shell or terminal emulator.. I will explain using adb shell through pc.
After establishing adb connection to your device, you can choose any of the following procedures to get your mounting points:
#1
Code:
adb shell
cat /proc/mounts
This will give you info about device, the mount point, the file system type, and how it is mounted.
Limitation: This method, however, will not give you all mounting points.!!!
{
"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"
}
#2
Code:
adb shell
cat /proc/partitions
This is more neat, it will give you info about ALL dev blocks and their names (not the familiar name!), and block size
Limitation: Needs from you to figure out which block belong to which partition name.!!
#3
Code:
adb shell
ls -al /dev/block/platform/[B][COLOR="Blue"]dw_mmc[/COLOR][/B]/by-name
This one is the command that I like on non-rooted device..! It will give you info about the dev block names WITH their familiar names (i.e, boot, recovery, system... etc) :laugh:
This command is not universal between devices, and you will need to gather its pieces (/dev/block/platform/dw_mmc/by-name).
How?
- In your device, use any explorer that can get you to the device root (personally I use ES Explorer, by pressing on "/" on navigation bar).
- Go to "/dev/block/platform/" folder
- Here you will see some files and folders, we need to open folders and search for the folder called "by-name" inside one of them; in my situation it was "dw_mmc" folder which has the folder "by-name" inside it.
- At the end, my targeted piece info will be (/dev/block/platform/dw_mmc/by-name)
- Now open adb shell and put the command..
***​
For Rooted Devices Only​
There are different ways to get mounting points in rooted device (including the non-rooted devices way), but the easiest way to get all device mounting points is to push parted binary to /system/bin folder and run it.
Code:
adb remount
adb shell "su" "" "mount -o remount,rw /system"
adb push parted /system/bin/parted
adb shell
chmod 755 /system/bin/parted
parted /dev/block/[B][COLOR="Blue"]mmcblk0[/COLOR][/B]
print
Here, your mounting points will start with /dev/block/mmcblk0p* where (*) is the number shown in the table above for each partition.
example:
The preload partition mounting point will be mmcblk0p12
The modem partition mounting point will be mmcblk0p8
The system partition mounting point will be mmcblk0p9
The Kernel partition mounting point will be mmcblk0p5
and so on
Don't forget to "quit" the parted action after grasping your device mounting points.
N.B:
- You may need to run first:
Code:
adb shell
cat /proc/partitions
to know what is the initial name for your device partition.. In the example above, it was mmcblk0.
- Also to be able to do adb push to /system partition, you will need adbd insecure installed in your device (Check this thread for that app), or to push it manually by any root explorer and then fix permissions to 755.
***​
Pre-made Scripts​Windows users
Here is a script I wrote for both non-rooted (way #3) and rooted devices for windows users.
Just extract the content in any folder and run the script that you want ("Non-Rooted and Rooted.cmd" or "Rooted Only.cmd")
Don't forget to install adbd insecure in rooted device in order to use Rooted Only.cmd script.
Linux users
As same, here is a script I wrote for both non-rooted (way #3) and rooted devices for linux users.
Just extract the content in any folder and run the script that you want ("non-rooted" or "rooted")
Don't forget to install adbd insecure in rooted device in order to use rooted script.
N.B: The linux scripts are tested with cygwin emulator on windows machine.. So needs feedback on actual machine.!!
Cheers

reserved

Thank you, I go to try.

Linux script added to OP

Thanks
Thank you You are the best one

Root, Recovery and Rom the Kurio 7

Hey guys, I spent the last week looking for a clear guide on how to install a custom rom on the Kurio 7 (Not the Kurio 7 S)
I have taken all of these demos and put them together into one guide. I take no credit for the information found here all I did was organize it in hopes it will help someone.
Here are the reference links to the original work-
Root: http://androidforums.com/general-tablet-talk/671444-root-kd-kurio-7-a.html
Play Store: https://www.youtube.com/watch?v=4WSuFvjyeRc
Recovery:http://forum.xda-developers.com/showthread.php?t=1802268
Rom and Gapps: http://www.slatedroid.com/topic/57538-rom-aokp-jelly-bean-android-412-allwinner-a10/
Disclaimer: You are doing this at your own risk, I am not responsible at all for your device. Just because it worked for me does not mean you will have the same outcome.
Download all of the files found here...
Lets get started: Bold = On the Tablet
1. Access the Android system (Done through parental controls)
2. Enable USB Debugging in Developer Options
3. Unzip and run the bat file found in Android Root.zip (Follow on screen instructions)
4. Extract the Install_google_play_allwinner.rar and run Install_Google_Play (Follow on screen instructions)
5. Open Google Play and download a Terminal Emulator
6. Extract and copy the contents of Kurio Recovery to your Tablet (not inside a subfolder)
7. Copy the files Kurio Rom and Kurio Gapps to your Tablet (not inside a subfolder)
8. Open Terminal Emulator and run the following commands
su
cd /mnt/sdcard
sh install-recovery.sh
sh reboot-recovery.sh
9. Select "Wipe data/factory reset, Wipe dalvik cache, & Wipe battery stats"
10. Select "install zip from sdcard" -> "choose zip from sdcard" and flash, in this order, Rom Then Gapps
11. Reboot your System
{
"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"
}
Known Issues:
My daughter has been using it for a week and only noticed that the built in home and back buttons do not work. But the Roms has built in soft keys so she doesn't complain.
I hope this helps someone out there.
Reminder
I am not a developer, feel free to report bugs to but I will not be able to help resolve these bugs.

Link for files is down
Is there any chance you could repost the dropbox files? The link is 404. Thanks.

Does it work?
I have tried many times but it didn't work though.
What I'm gonna do now?
Please let me know?

Doesn't work
Hi,
I have tried rooting my Kurio 7 using the ICS_Root_Unlocker script in that Android_Root_1.0 zip file, but I get a ton of errors:
failed on '/data/local/tmp' - Permission denied link failed File exists
Press any key to continue . . .
/system/bin/sh: can't create /data/local.prop: Permission denied
Press any key to continue . . .
uid=2000(shell)gid=2000(shell)groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
Press any key to continue . . .
remount failed: Permission denied
failed to copy 'files\su' to '/system/xbin/su': Read-only file system
Unable to chown /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Removing changes except ROOT...
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
Installing superuser...
failed to copy 'files\superuser.apk' to '/system/app/superuser.apk': Read-only file system
Press any key to continue . . .
My Kurio 7 is running Android 4.4.2 KitKat (the tablet is only a year old and already has Google Play on it) whereas the script appears to be for ICS, could this be the problem?
Anyone know how to adapt the script to work with KitKat?

Anyone have a kurio 7 ROM .IMG file?