Related
Is there a simple, non-CWM flashing one-click root for stock EB13 Epics (I just want to tether to my rooted nook)?
I ask because a few months back I rooted my DI18 Epic with a "One Click Root" and, for some reason, all my apps became unlinked from the android market, and nothing I did worked to restore their connections. After a few hours of panic, I unrooted using the accompanying "One Click Unrooter," and the problem went away.
Then, I noticed my bluetooth was't working. I took it to the Sprint store, they ordered me a replacement phone, and then wouldn't exchange it because CWM was on my current phone. I got them to exchange it eventually, but I felt like a complete dumbass for not knowing it didn't come off in the one-click-unrooting process.
So, is there a way to just get root? And then is there a simple way to get rid of it (uninstall SU and such as well) in case I have to exchange the hardware?
I've read a lot of stuff about flashing stock with Odin, but all the dl links for Odin are 404'd, and I'd rather not have to go back to fresh stock every time I need to take my phone in. What's your advice?
SuperOneClick v1.7 worked for me.
Trickee360 said:
Is there a simple, non-CWM flashing one-click root for stock EB13 Epics (I just want to tether to my rooted nook)?
Click to expand...
Click to collapse
I don't know about "one-click", z4root might work, but there's anecdotal reports of it not working on Android 2.2.1. The one-click w/CWM redirector is the easiest way to root and definitely recommended if you want to do anything more advanced (ROMs, etc.). You can always return to stock everything with Odin.
That said, if all you want is root and nothing more, the manual version is relatively simple. It's really just three steps:
Use an exploit (rageagainstthecage-arm5.bin) to get "temporary root" (an ADB root shell).
Install Superuser's su binary to /system/xbin with the appropriate permissions (root.shell 4755).
Sideload Superuser.apk as a regular program, or download it from the market.
In which case "unrooting" is trivial. Just delete /system/xbin/su with root-explorer or something, and after remove Superuser via "Manage applications".
A while back I wrote up semi-detailed directions for doing this. They should work on EB13 with some modification. Here's some notes for EB13:
"rageagainstthecage-arm5.bin", "su", and "Superuser.apk" are all included in the one click package, that's the easiest place to get them.
Actually running "rageagainstthecage-arm5.bin" is the trickest part. There's a few ways to do it, and due to the nature of the exploit, sometimes only one or two of them will work for anyone. You can tell it works if on the next run of "adb shell" you get a "#" prompt instead of "$". Try these three ways in order until one of them works:
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb shell /data/local/tmp/rageagainstthecage-arm5.bin
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb shell (press return, and type below at the "$" prompt):
/data/local/tmp/rageagainstthecage-arm5.bin
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb push root.sh /data/local/tmp
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb shell chmod 755 /data/local/tmp/root.sh
adb shell /data/local/tmp/root.sh
With the last method's root.sh from the one-click package.
Once you have root, and have verified such by getting a "#" prompt with "adb shell", then run:
Code:
adb shell rm /data/local/tmp/rageagainstthecage-arm5.bin
adb shell rm /data/local/tmp/root.sh
adb shell mount -wo remount /dev/block/stl9 /system
adb push su /system/xbin
adb shell chmod 4755 /system/xbin/su
adb shell mount -ro remount /dev/block/stl9 /system
adb install Superuser.apk
If you do nothing more, OTA updates should apply just fine. The only caveat is that /system/xbin/su will lose the appropraite permissions, so Superuser will no longer work. To restore it, do the same steps above to regain "temporary root", then run:
Code:
adb shell rm /data/local/tmp/rageagainstthecage-arm5.bin
adb shell rm /data/local/tmp/root.sh
adb shell mount -wo remount /dev/block/stl9 /system
adb shell chmod 4755 /system/xbin/su
adb shell mount -ro remount /dev/block/stl9 /system
You shouldn't have to push a new "su" binary since it's already there, and similarly, you don't need to reinstall Superuser.
I am trying to unroot my g2 in order to send it in. I used gfree method on Wiki to root the phone and to unroot it. However, I am stuck trying to turn s-on. When I enter:
$ adb shell /data/local/tmp/psneuter
I am getting:
/data/local/tmp/psneuter: permission denied
Any ideas?
I believe you have to do "chmod 755 /data/local/tmp/psneuter" on it (I'm not -too- sure on the numbers, but I think it's 755)
EDIT: chmod 777, my bad - thanks posters below
Well the steps from the wiki are:
$ adb push psneuter /data/local/tmp/psneuter
$ adb shell chmod 777 /data/local/tmp/psneuter
$ adb shell /data/local/tmp/psneuter
$ adb shell
It's the 3rd one that I am stuck on.
Since I am unable to get temp root following the wiki, would I be able to use visionary to get temp root and then s-on following the wiki?
flat4grl said:
Since I am unable to get temp root following the wiki, would I be able to use visionary to get temp root and then s-on following the wiki?
Click to expand...
Click to collapse
Hi !
Are you sure that you got a valid copy of psneuter?
Try to download the zip from psneuter.zip unpack it and try it again with the file that is called psneuter in it.
have fun - Guhl
Thanks for the help! Unfortunately that didn't work either. Not sure whats going on, but I think it's something with the phone. I just cannot figure it out. At least it works for now.
Type:
1)adb shell
***you should see the '$' symbol (if you have '#', then do nothing, you're already root)
2)chmod 777 /data/local/tmp/psneuter
3)/data/local/tmp/psneuter
4)exit
5)adb shell
6)su
If you have the '#', then you're root
I don't know if this will work, but this is not dangerous at all to try
Max) said:
Type:
1)adb shell
***you should see the '$' symbol (if you have '#', then do nothing, you're already root)
2)chmod 777 /data/local/tmp/psneuter
3)/data/local/tmp/psneuter
4)exit
5)adb shell
6)su
If you have the '#', then you're root
I don't know if this will work, but this is not dangerous at all to try
Click to expand...
Click to collapse
Thanks you for trying to help! When I got to the third step it told me permission denied again.
I was able to FINALLY get s-on. I thought I would post how I did just in case anyone else ends up having this problem.
I used visionary to temp root my phone and then used the wiki to turn s-on. Only problem I had was trying to remove the psneuter file from the phone. Other than that no problems. Now I shall see if I can get away with sending the phone in.
Hello.
I've tried to root my Desire Z. I wanted to achieve only the ROOT not S-off and so on. Just to be able to use some root requiring applications like DSP Manager or Adds free.
1. So I've downloaded and installed Android SDK.
2. Started ADB
3. "adb devices" gave me the proper answer
4. Then I've copied and started psneuter and misc_vesion:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
/data/local/tmp/misc_version -s 1.33.405.5
exit
5. Then I've tried to root the phone:
Ive copied the required files:
adb install AndroidTerm.apk
adb push busybox /data/local/tmp/
adb push gfree /data/local/tmp/
adb push rage /data/local/tmp
adb push root /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/*
adb push su /sdcard/
adb push Superuser.apk /sdcard/
And then from the Terminal Emulator I've entered
/data/local/tmp/root
I've got some messages that the everything is read only so I've tried rage first:
/data/local/tmp/rage
I've got the proper "Forked #### childs" output
and then I've tried the "/data/local/tmp/root" again. But I'm getting the "cannot fork" message.
I'm new in this stuff s please help me. What do I do wrong?
I only want the simple root access I don't want to downgrade my phone and install any custom roms.
Please help.
ps. my "compilation number" is: 1.72.405
As far as I remember your supposed to flash 1.34 Rom after changing the version number to 1.33 as the rooting is only possible via 1.34 Rom and not 1.72 Rom .... And you clearly missed that step .... Open desire z wiki and read the psneuter guide ... Follow it word for word .... You will root your phone
Maxymo123 said:
Hello.
I've tried to root my Desire Z. I wanted to achieve only the ROOT not S-off and so on. Just to be able to use some root requiring applications like DSP Manager or Adds free.
1. So I've downloaded and installed Android SDK.
2. Started ADB
3. "adb devices" gave me the proper answer
4. Then I've copied and started psneuter and misc_vesion:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
/data/local/tmp/misc_version -s 1.33.405.5
exit
5. Then I've tried to root the phone:
Ive copied the required files:
adb install AndroidTerm.apk
adb push busybox /data/local/tmp/
adb push gfree /data/local/tmp/
adb push rage /data/local/tmp
adb push root /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/*
adb push su /sdcard/
adb push Superuser.apk /sdcard/
And then from the Terminal Emulator I've entered
/data/local/tmp/root
I've got some messages that the everything is read only so I've tried rage first:
/data/local/tmp/rage
I've got the proper "Forked #### childs" output
and then I've tried the "/data/local/tmp/root" again. But I'm getting the "cannot fork" message.
I'm new in this stuff s please help me. What do I do wrong?
I only want the simple root access I don't want to downgrade my phone and install any custom roms.
Please help.
ps. my "compilation number" is: 1.72.405
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Just out of curiosity, if you only want to root to use some applications and such, why don't you just temp root using visionary and just redo it whenever you restart your phone?
Thanks for the answers guys.
your supposed to flash 1.34 Rom after changing the version number to 1.33
Click to expand...
Click to collapse
hispeedworm - I don't want to downgrade my phone. I don't need it and I don't want to loose whole the settings and apps and start from the beginning just for using some special apps.
mmduluth - I've used the visionary method from this topic while it seemed the easiest one for the beginner. However after taping the "TempRoot Now!" the VISIONary+ seemed to hang. The screen was black for several minutes.
So I've decided it does not work.
Anyway, I'd prefer to have permanent root than a temp one for example for using "autostarts" - which as far as I'm concerned works AFTER rebooting the phone.
So anyone could tell me where is a mistake in what I did?
I suppose I've omitted one thing in former trials so I've tried to root it again.
After entering the Terminal Emulator I've run rage:
/data/local/tmp/rage
I've got the Forked #### childs message so everything was ok till then.
Then I've reset terminal --> menu-->reset term
And then I've run the terminal again.
I should get the # sign but what I get is the totally white screen with no possibility to write any command. It's not responding. I can only get out from it by pressing the home button.
So what's going wrong?
Maxymo123 said:
I suppose I've omitted one thing in former trials so I've tried to root it again.
After entering the Terminal Emulator I've run rage:
/data/local/tmp/rage
I've got the Forked #### childs message so everything was ok till then.
Then I've reset terminal --> menu-->reset term
And then I've run the terminal again.
I should get the # sign but what I get is the totally white screen with no possibility to write any command. It's not responding. I can only get out from it by pressing the home button.
So what's going wrong?
Click to expand...
Click to collapse
If you read enough threads/post, at the moment, the only way to gain permaroot is to downgrade your ROM. Unless, somebody finds a way to do it without the need to downgrade.
And, as I understand, using Visionary apps would cause damage to your device. Be careful!
Cheers...
Thank you silverwind. Now it's clear.
So anyone is working on this?
Cheers
Hello everyone!
Not my phone, just helping a friend
We got problems downgrading from Gingerbread to earlier version of Android.
So, wanted to root, flash custom recovery, then MIUI.
Started with this tut, then understood, that Gingerbread isn't rootable and it needs to be downgraded.
So, tried [GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo and HTC Desire Z: Firmware Downgrade (Gingerbread).
So, installed JRE, JDK, SDK (ADB), drivers.
With phone plugged to PC (USB Debuggind ON), ADB & Device manager sees it.
So, moved files to C:\android-sdk\platform-tools and ran cmd (administrator privileges). Till "adb shell it's good". But, after that, when ran chmod, it says, that permissions denied.
Question:
What we're doing wrong and how to fix it?
We've read so many guides, but unsuccessfully so far..
Device HTC Desire Z
Android 2.3.3
Kernel version 2.6.35.10-g7b95729
Baseband 12.56.60.25U_26.10.04.03_M
Build 2.42.405.2 CL84109
Thanks about helping!
Is it permission denied when u try to change the version? If permission denied during change the version, run this command:
cd /data/local/tmp/misc_version
chmod 777 misc_version
./misc_version -s 1.00.000.0
sync
Sent from my HTC Vision using XDA App
Are you sure your temp root is working?
aDeQ666, no, it wont chmod when typing chmod 777 /data/local/tmp/fre3vo, so - no temp root for us. Tried visionary, z4root, SuperOneClick - nothing works
It was updated from Froyo to Gingerbread via OTA, i think that's the issue? What else we can do? Thanks!
Could you post a copy/pastebin of your cmd when running it? It'll be much easier to spot the error if we can see exactly what you did/are doing.
-Nipqer
I have one problem when i tried to root htc desire. i already done the downgrade and now i am want to root... i folllowed the instructions on the link you gave untill this
[chmod 755 /data/local/tmp/*
/data/local/tmp/psneuter
NOTE: You will drop out of the shell after this command. Restart the shell using:
adb shell
cd /data/local/tmp
./busybox md5sum /dev/block/mmcblk0p18]
well after command:
chmod 755 /data/local/tmp/*
/data/local/tmp/psneuter
i`m not dropping out of the shell and the next instruction results with a "cd: bad substitution" msg. what should i do?
sorry for my bad english
When do u received the error? Is it when u downgrading or try to root? Are u using the wiki guide?
What I've down a few times now (and this does work) is use the fre3vo guide (the one you linked) to downgrade then continue with the guide below from step 14 or 15 to gain perm root.
http://forum.xda-developers.com/showthread.php?t=905261
Hope that helps.
Edit: You're better off flashing 1.34.405.5 as the one on the CM wiki may not be working. Its worth a shot IMO.
aDeQ666 said:
Is it permission denied when u try to change the version? If permission denied during change the version, run this command:
cd /data/local/tmp/misc_version
chmod 777 misc_version
./misc_version -s 1.00.000.0
sync
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Hi, i have been trying to change my misc version but it gives me permission denied and i have # (root) already. So i tried chmod after cd which didn't have a problem but now when i try harder./misc_version it says the file not found.
Please help
I used this guide. it worked fine for me =)
http://forum.xda-developers.com/showthread.php?t=905261
*faceslapps self* sorry. I was a tad too fast. I didn't see that someone allready posted that guide here.
This is the command that i use before this:
adb push misc_version /data/local/tmp/misc_version
cd /data/local/tmp/misc_version
chmod 777 misc_version
./misc_version -s 1.00.000.0
sync
Sent from my HTC Desire Z using XDA App
I used this guide when I had to go through the pain of downgrading my desire z http://forum.xda-developers.com/showthread.php?p=15851843 . It worked very easily, just follow the instructions nice and carefully, the problem is that you need ADB set up for you to use that guide though.
Once you downgrade though, I would use the guide here for rooting your phone http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 .
I hope that helps, that's what I used for my phone.
To be more precise in regards to the problem though, i just realised that i had the same problem as you when i was trying to run the chmod command where i had temproot but i kept getting "permission denied". As it turned out, i had accidentally written "adb push fre3vo /data/local/tmp/" instead of "adb push fre3vo /data/local/tmp" when i was following that downgrading guide. Basically what my mistake did was, it pushed fre3vo into a new folder within /tmp instead of just placing fre3vo in /tmp. So what you can do to figure out where fre3vo is, navigate to the /tmp folder using CD (in adb shell) and once you get to /tmp, type "ls". This will then display all the contents of /tmp and then you will be able to see if you accidentally created a folder like i did. Then once you check that, when you go to run the chmod command, you have to run it like "chmod 777 /data/local/tmp/**possible accidental folder name**/fre3vo", see if that works now .
Use this guide should do the job for you www.desirez.strawmetal.com
aDeQ666 said:
This is the command that i use before this:
adb push misc_version /data/local/tmp/misc_version
cd /data/local/tmp/misc_version
chmod 777 misc_version
./misc_version -s 1.00.000.0
sync
Sent from my HTC Desire Z using XDA App
Click to expand...
Click to collapse
were you able to fix this problem?
I had the same problem with my Desire Z with OTA 2.3.3.
Finally I've unlocked bootloader as show at htcdev.com.
Then I used this guide http://forum.xda-developers.com/showthread.php?t=1453066 (great thx for it), and CM 7.1 works like a charm.
All best.
allendon said:
were you able to fix this problem?
Click to expand...
Click to collapse
For my case, yes.
Sent from my HTC Vision using XDA App
Yes, I do understand that zergRush is for Gingerbread, but I've read so many threads on user SOC, and multiple versions of it at that, to gain root. From past experiences rooting phones (LG Optimus V, Samsung Intercept, HTC Vivid) I understand ADB, and how things work, but this phone really has me stumped.
So I've tried everything under the sun, multiple different SOC versions (you name it, i've tried it), TPSparkyRoot, among others. Nothing will root this phone, even used the unbricking guide after finding out that V10F(or J, can't remember) is unrootable. So now I'm not V18F, which from what everyone is saying is very rootable. Some say SOC 2.3.3 will root on first try, well not for me.
For some reason SOC was always stopping at Step #7, no matter what version I am on. Reading the log I would always see it stop and freeze up at a step that looked like it was trying to mount something, or remount something. I would try Shell Root and it would just give me the Gingerbreak error when it tried to run the zergRush exploit.
Now I even got my hands dirty and installed the SDK, ran ADB and tried to manually run the zergRush exploit, I knew it probably was going to spit out the same feedback as SOC did but it was worth a shot.
Now I'm really stuck, should I reflash the V10 firmware to try and manually zergRush the phone? Is there really a working method out there, I mean there has to be cause people have been rooting these phones.
Just to make everyone aware, when I flashed the V18F firmware it was a ROM (HO!NO!) that was suppose to already have been rooted (the download to the rom was in one of the unbricking guides I found). The only problem was once I install V18F there was no root, no Superuser app, nothing.
So I'm going to once again, ask the nice people here at the Nitro XDA Community to lend me some advice.
===========================
UPDATE:
Ok, so upon more reading, and gutting out codes and methods from devs everywhere (credit will be made later) I got temp root, although any application that I used to check for root always took forever, let me explain.
I ran these commands manually, as found in TPSparkyRoot
Code:
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
I then waited until the phone booted back up completely and ran
Code:
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
adb reboot
I then waited for another full reboot. Now here is the weird thing, I can run "adb shell" and am automatically greeted with # instead of $. So I'm temp rooted right? I don't know what this script exactly is doing, the code looks to complex for my feeble mind to understand.
So now that I have root, I started pushing the required files into directories I couldn't access before.
Code:
adb remount
adb push su /system/bin/su
adb shell chown 0.0 /system/bin/su
adb shell chmod 06755 /system/bin/su
adb push busybox /system/bin/busybox
adb shell chown 0.0 /system/bin/busybox
adb shell chmod 0755 /system/bin/busybox
adb push Superuser.apk /system/app/Superuser.apk
adb shell chown 0.0 /system/app/Superuser.apk
adb shell chmod 0644 /system/app/Superuser.apk
Now I'm not sure but after step 2/3 in the TPSparkyRoot it would feed me errors on writting those files, manually entered though it worked, for some reason I think that the script was not executing a remount, because manually they worked fine.
So I seem to have temp root, restarting the phone will set the shell back to $. Google Play will offer an update for SuperUser and update correctly, but it never shows in my app drawer, and other apps seem to act funny when trying anything with root. Any ideas?