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] Convert ADB to Terminal Emulator code

Hey all,
Just wondering what the conversion code for Terminal Emulator would be in order to perform an ADB code, i have tried to convert the code myself below and want to be sure it is ok.
Basic objective is to copy the file gps.conf from /sdcard/code/ to /system/etc/ directly using Terminal Emulator on my Desire HD (Froyo 2.2 firmware 1.32....)
CMD prompt:
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
mount -o remount,rw /dev/block/mmcblk0p25 /system
exit
adb push gps.conf /system/etc/gps.conf
adb shell
mount -o remount,ro /dev/block/mmcblk0p25 /system
exit
TEmu:
chdir /sdcard/code
cp psneuter /data/local/tmp
cp misc_version /data/local/tmp
chmod 777 /data/local/tmp/psneuter
chmod 777 /data/local/tmp/misc_version
chdir /data/local/tmp/psneuter
mount -o remount,rw /dev/block/mmcblk0p25 /system
cp /sdcard/code/gps.conf /system/etc/
mount -o remount,ro /dev/block/mmcblk0p25 /system
NOTE: that when i tried cp psneuter /data/local/tmp or even cp psneuter /sdcard it says cp: permission denied
Cheers

if all you want to do is copy the file...then whats the point of all of that??!!
im guessing that your not rooted, since your doing some code from the downgrade thread that gives temp root.
But the whole point of that code is to get temp root for FW greater than 1.32.
Since you want 1.32, use a program called Visionary+ and click temproot is you want temporary root. (Visionary+ only works till 1.32 FW)
And you wont be able to copy to a file to the system partition if your not in root mode.
So in the terminal, type
>su
first thing, then carry on.
If you get a # instead of the $ then your in root mode, if not (or if a message appears) then you dont have permission to go into root mode(or your not rooted).
---and i dont think theres any point of the chdir command.
::::::::::But if you want to use that code, then it'll work if you type 'su' first.

[Toturial][Windows] How Editing The ODEX framework files? [Simplified]

Hi, This is a simple tutorial for someone that wants to working on ODEX structure.
All needed files are attached, you don't need to download anything files.
Extract the Amestris_ODEX.zip file, your working folder will be this one.
I'm creating the simple example here.
for example i want to edit the services.jar file on ODEX structure.
We need to work on DEODEX version at first.
You can Deodex your files from here:
The Best solution is here , Android Kitchen by dsixda user.
[KITCHEN] Android Kitchen, v0.192 [Linux / Mac / Windows]
Click to expand...
Click to collapse
Your Phone needs to be rooted and Busybox get installed.
the sample file is services.jar,also you can do it for any odex file.
1- Do all your editing and working on your deodex version.
2- Create this folders on your sd-card partition.
Code:
amestris_mod
amestris_original
3- Copy your modded file [your deodexed and edited services.jar] into amestris_mod folder.
4- Copy original jar file into amestris_original folder. [original odex services.jar]
5-Copy dexopt-wrapper into /system/bin folder and give full permission to that. [the simple way is root explorer ]
through the adb command:
Run the Amestris.bat file.
Code:
adb remount
adb push dexopt-wrapper /system/bin/dexopt-wrapper
adb shell chown 777 /system/bin/dexopt-wrapper
adb shell chmod 777 /system/bin/dexopt-wrapper
6-run this adb commands.
Code:
adb shell
cp /sdcard/amestris_mod/services.jar /system/framework/services.jar
dexopt-wrapper /system/framework/services.jar /system/framework/new_services.odex /system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar
cp -f /sdcard/amestris_original/services.jar /system/framework
chmod 777 /system/framework/services.odex
chmod 777 /system/framework/services.jar
chmod 777 /system/framework/new_services.odex
busybox dd if=/system/framework/services.odex of=/system/framework/new_services.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
cp /system/framework/new_services.odex /system/framework/services.odex
chmod 644 /system/framework/services.odex
chown root.root /system/framework/services.odex
rm /system/framework/new_services.odex
reboot
Credits:
M_J_Nazari
sicopat
jubeh
Decad3nce
software_samurai
Click to expand...
Click to collapse

Android.policy.jar
This is a Sample for android.policy.jar
Run Amestris.bat file and run this commands here
Code:
adb remount
adb shell
cp /sdcard/amestris_mod/android.policy.jar /system/framework/android.policy.jar
dexopt-wrapper /system/framework/android.policy.jar /system/framework/new_android.policy.odex /system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar
cp -f /sdcard/amestris_original/android.policy.jar /system/framework
chmod 777 /system/framework/android.policy.odex
chmod 777 /system/framework/new_android.policy.odex
busybox dd if=/system/framework/android.policy.odex of=/system/framework/new_android.policy.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
cp /system/framework/new_android.policy.odex /system/framework/android.policy.odex
chmod 777 /system/framework/android.policy.odex
chown root.root /system/framework/android.policy.odex
rm /system/framework/new_android.policy.odex
reboot

This is a Sample for framework.jar
The framework.jar or frameowrk.odex file is very sensitive and vital file for android.
some changes of this file will turn your phone into force close messages.
but i create a sample for this file;
do it like below:
Run Amestris.bat file and type this commands.
Code:
adb remount
adb shell
cp /sdcard/amestris_mod/framework.jar /system/framework/framework.jar
dexopt-wrapper /system/framework/framework.jar /system/framework/new_framework.odex /system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar
cp -f /sdcard/amestris_original/framework.jar /system/framework
chmod 777 /system/framework/framework.odex
chmod 777 /system/framework/framework.jar
chmod 777 /system/framework/new_framework.odex
busybox dd if=/system/framework/framework.odex of=/system/framework/new_framework.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
cp /system/framework/new_framework.odex /system/framework/framework.odex
chmod 777 /system/framework/framework.odex
chown root.root /system/framework/framework.odex
rm /system/framework/new_framework.odex
reboot

1: Q: When i use the cp command , the error shows with " cp: not found " message
A: try to use " busybox cp" instead the " cp " command.

Excellent explanation!!! Thank you very much.

Hey there, i saw this guide and really liked it, so I wrote about it on the XDA Portal
here's the link!
http://www.xda-developers.com/android/tutorial-simplifies-editing-odexed-framework-files/
i hope you enjoy the write up.

Thank you so much all you guys.
now lets see if i can use this to port SMemo to imilka's CM9 or AOSP
thnx.

You can do same on linux. Smali is cross platform. Just needs java. I added deoxt wrapper on my ROM's for who want to do it easily.
Sent from my GT-I9000 using Tapatalk 2 Beta-6

Great write up.
Does this method also remove the classes.dex file that is found in apks since it is now housed as a seperate .odex file?

myn said:
Great write up.
Does this method also remove the classes.dex file that is found in apks since it is now housed as a seperate .odex file?
Click to expand...
Click to collapse
This method doesn't remove anything. this is a method for replacing [editing] odex files.
if you want to convert the apk files to odex structure you need to check the Amestris Odexer Script v1.2.

Ops wrong thread, sry

If my ROM already have framework.odex does it mean that I only need to make the changes directly into the odex file and then recompile it?

[HOWTO] (Manually) Rooting the Kindle Fire 2 with a Mac

Firstly, Merry Christmas!
Note: This worked on version 10.2.4
I received a Kindle Fire 2 today and since then I've been trying to get it rooted, now that I have I though I'd share it here for other people who might be in the same situation.
This is really just a remixing of the tool made by Bin4ry (http://forum.xda-developers.com/show....php?t=1886460) but I couldn't get the script to run on my Mac...
Step 0 - Preparing
You must enable ADB and Unknown App sources from Settings.
Settings > More > Security > Enable ADB
Settings > More > Device > Allow Installation of Applications
Step 1 is to get that tool from here. and extract it somewhere you'll remember.
Step 2 (you can skip this if you already have the android SDK platform-tools in your PATH)
If you don't have the android SDK or adb installed just add the 'stuff' folder from the tool to your path.
In terminal run
Code:
export PATH=$PATH:/path/to/extracted/tool/stuff/
Step 3 - Push the required files
It's probably easiest if you change into the stuff folder first...
Code:
cd /Users/x/Downloads/Root_with_Restore_by_Bin4ry_v18.7z\ Folder/stuff
Then run the following...
Code:
adb push busybox /data/local/tmp/.
adb push su /data/local/tmp/.
adb push Superuser.apk /data/local/tmp/.
adb push ric /data/local/tmp/ric
Then you need to run an adb shell to set some permissions
Code:
adb shell
(you should get a prompt like [email protected]:/)
Run
Code:
chmod 755 /data/local/tmp/busybox
exit
Step 4 - Rooting
This requires another terminal window. Check that you can run adb from there as well (running adb should print the usage information)
In the first window run:
Code:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > /dev/null
In the other run
Code:
adb restore fakebackup.ab
You should get a prompt on your Kindle, hit the restore my data button. As you do so the command in the first window should stop (or a few seconds later - if it doesn't stop it and re-run both commands again.)
You can now close the second window!
Run
Code:
adb reboot
, your Kindle should reboot though the screen will be blinking repeatedly (flashing between the lockscreen and the boot animation) don't worry about that as it will be fixed in a sec.
Step 5 - Cleaning Up
Run
Code:
adb shell
If all was successful you should see the prompt change to [email protected]:/
If it did, continue otherwise go back to step 4.
Run these
Code:
/data/local/tmp/busybox mount -o remount,rw /system
/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su
/data/local/tmp/busybox mv /data/local/tmp/ric /system/bin/ric
chmod 755 /system/bin/ric
/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su
/data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chown 0.0 /system/xbin/su && chmod 06755 /system/xbin/su
chmod 655 /system/app/Superuser.apk
chmod 755 /system/xbin/busybox
rm /data/local.prop
reboot
Your Kindle will restart and SuperSU will be available under Apps, your now free to do as you please, though you could follow with Step 3 on this thread to get Google Apps etc working.
Update: a short guide to installing the Play store can be found here.

This worked almost perfect for me but I couldn't get it to run adb commands from the stuff folder so I dumped its contents (minus the adb stuff) into the platform-tools in the android SDK and from then on everything went great. Thanks so much.

didthis work for 10.2.4 users out there
does this work for 10.2.4

worked!
Great work, congratulations and thanks! I'd like to make some comments tho regarding some typos and suggestions.
1.- I'd suggest to install the android SDK as, in fact, adb commands didn't work from the stuff folder. Add a line to .bash_profile with the export PATH command to make permanent access to the adb shell.
2.- Push files from the Root_with_Restore_by_Bin4ry_v18 folder, not the .7z file.
3.- The command is, e.g., adb push busybox /data/local/tmp/ instead of adb push busybox /data/local/tmp/.
4.- In Step 5 the command /data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su is twice so you'll get an error the second time you execute it.
Also congratulations for instructions on how to install PlayStore - here pay attention to the names playstore.apk and servicesframework.apk which in fact are plstore3.10.10.apk and GoogleServicesFramework.apk respectively -
Once again thanks for your work.

gorganzolia said:
does this work for 10.2.4
Click to expand...
Click to collapse
Yes this worked for 10.2.4

10.2.6
Does this work with 10.2.6?

it worked
Tried it this morning on 10.2.6 and it worked woohoo now how do you stop it from automatically updating
Found out how to stop those automatic updates here http://forum.xda-developers.com/showthread.php?t=2086450

[GUIDE] Fix SuperSU on DragonBoard 410c (root)

Ensure you have drivers setup properly and are able to adb shell to your 410c
Install SuperSU 2.46 over adb or "Chainfire SuperSU" from Google Play if you have it installed
Download UPDATE-SuperSU-v2.46.zip and extract it to your microSD card that you use for your 410c
adb root
adb shell
cd /mnt/media_rw/sdcard1/UPDATE-SuperSU-v2.46/
cp ./arm/chattr.pie /data/local/tmp/chattr.pie
chmod 0755 /data/local/tmp/chattr.pie
mount -o rw,remount /system
cp /mnt/media_rw/sdcard1/UPDATE-SuperSU-v2.46/arm64/supolicy /system/xbin/supolicy
chmod 0755 /system/xbin/supolicy
cp /mnt/media_rw/sdcard1/UPDATE-SuperSU-v2.46/arm64/libsupol.so /system/lib64/libsupol.so
chmod 0755 /system/lib64/libsupol.so
cp /mnt/media_rw/sdcard1/UPDATE-SuperSU-v2.46/arm64/su /system/xbin/su
chmod 0755 /system/xbin/su
cp /mnt/media_rw/sdcard1/UPDATE-SuperSU-v2.46/arm64/su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
/system/xbin/daemonsu –d
Exit but DO NOT restart your 410c yet
On your 410c, open the SuperSU app and select “Normal” to finish the process

I followed through all the steps in your post, but when I opened the SuperSU app in the end, it still shows the message that "There is no SU binary installed, and SuperSU cannot install it...". Do you have any idea what else I could try to fix it? Thanks!!

Root access is granted but once device reboots root access is denied. Also where is “Normal” in SuperSU?