Develop Bugs

[Q] Simple Root for EB13

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.

[Q] Please help with Rage Temproot during Gfree root process

Please help, I've searched around and can't find the solution to my issue, I'm rooting following the XDA wiki for Gfree and using the Android SDK....I've managed to get the ADB to recognize my phone and I "think" that the ADB has been able to push the first 5 files to the SD....but I'm stuck on the last command line.
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
when I run $ adb shell chmod 0755 /data/local/tmp/*
I get the following:
Usage: chmod <MODE> <File>
so then I go to terminal emulator on the phone and type
$ /data/local/tmp/rage
I get: /data/local/tmp/rage: not found
Where have I screwed up?

G2_Gordon_G1 said:
Please help, I've searched around and can't find the solution to my issue, I'm rooting following the XDA wiki for Gfree and using the Android SDK....I've managed to get the ADB to recognize my phone and I "think" that the ADB has been able to push the first 5 files to the SD....but I'm stuck on the last command line.
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
when I run $ adb shell chmod 0755 /data/local/tmp/*
I get the following:
Usage: chmod <MODE> <File>
so then I go to terminal emulator on the phone and type
$ /data/local/tmp/rage
I get: /data/local/tmp/rage: not found
Where have I screwed up?
Click to expand...
Click to collapse
looks like you screwed up the last command ... didnt write the syntax properly thats why it showed its usage.....
(adb shell chmod 0755 /data/local/tmp/*) this command that is.....
also the last thing showing file not found means the files were never pushed to the phone..... connect your phone to your pc in chagre only and usb debigging connected mode and in command prompt in the adb folder write "adb devices"
it should show somehting like this.....
adb list of devices attached
SH034N34GF
this number over here (SH034N34GF) is an example ... it will show your phone ID... which would be different....
if you see list of devices attached and an empty line below and no serial number as shown in example....
than it means your android usb drivers for adb shell are not set up correctly
in that case ... get the drivers set up properly....
check with adb devices command to confirm your phone is recognized....
than start over with the commands

I've started over and have typed VERY CAREFULLY...
On each of the first five command prompts I get a 40 or so line message that starts with:
Android Debug Bridge version 1.0.26
.......
(list of commands)
.......
and ends with
bug tags are printed.
OK so I guess that's good
So then I type C:\> adb shell chmod 0755 /data/local/tmp/*
and NOW I get
adb server is out of date. killing...
*daemon started successfully*
Bad Mode
Clearly, I'm a noob.....
Now what?

read this guide .... on it search for .... "out of date" author explains how to tackle it
G2_Gordon_G1 said:
I've started over and have typed VERY CAREFULLY...
On each of the first five command prompts I get a 40 or so line message that starts with:
Android Debug Bridge version 1.0.26
.......
(list of commands)
.......
and ends with
bug tags are printed.
OK so I guess that's good
So then I type C:\> adb shell chmod 0755 /data/local/tmp/*
and NOW I get
adb server is out of date. killing...
*daemon started successfully*
Bad Mode
Clearly, I'm a noob.....
Now what?
Click to expand...
Click to collapse

hispeedworm said:
read this guide .... on it search for .... "out of date" author explains how to tackle it
Click to expand...
Click to collapse
In the ADB guide it says:
"By the way, the first adb command that you type may well also come up with some lines similar to "adb deamon out of date" etc, but don't worry, that's normal, just check the rest of the output."
So apparently that's not a problem?

G2_Gordon_G1 said:
In the ADB guide it says:
"By the way, the first adb command that you type may well also come up with some lines similar to "adb deamon out of date" etc, but don't worry, that's normal, just check the rest of the output."
So apparently that's not a problem?
Click to expand...
Click to collapse
im uploading my adb... its minimal with just adb fastboot and few other files.... unzip into a folder on your pc.....use these instead of the android sdk and all..
make sure that folder is linked in windows..... Step 4 of the adb for noobs guide..... reinstall the android usb drivers again following the guide.....
when thats done restart and press F8 ... disable signature verification ... when windows loaded... go to command prompt.... do into the adb directory.....than write adb devices....if it shows you device than start over with the commands.... you should not get the error saying out of date... as i just used this adb shell 2 days back to root my desire Z.....
hope this helps

Thanks! Will try again soon!

[Q] Permroot on Desire Z failed - what I do wrong?

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

Manual Root - UPDATED: Temp Root?

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?

mtk-su root

Hello.
So now we can get root shell on LG Q7
adb push mtk-su /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 755 mtk-su
./mtk-su
Any ideas how to setup root access for apps?

Give me link

I can't have a root shell. When I enter /data/local/tmp/mtk-su it just exits adb shell