Database Info

CONFIRMED: Permament Root!

please see this link http://forum.sdx-developers.com/epic-development/adb-root-exploit-test/
if your having trouble: use my instructon
1. copy & run the exploit
adb push c:\downloads\rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell
chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local/tmp
./rageagainstthecage-arm5.bin
2. make it RW and move files
adb shell mount -t rfs -o remount,rw /dev/block/stl9 /system
adb push c:\downloads\joeykrim-root.sh /system/bin/joeykrim-root.sh
adb push c:\downloads\jk-su /system/bin/jk-su
adb shell mv /system/bin/playlogo /system/bin/playlogo-orig
adb push c:\downloads\playlogo /system/bin/playlogo
3. set permission
adb shell chmod 755 /system/bin/joeykrim-root.sh
adb shell chmod 755 /system/bin/playlogo

Sweet! I've been following the thread at sdx. Thanks for being a test dummy
Sent from my PC36100 using XDA App

Hopefully there will be a one click method or something just as easy to use to perform this

Has anyone actually tried this on there epic? I have an advocate device and prefer not to ruin it before I even goes active on my line.
Sent from my SPH-D700 using XDA App

cognitivel0gic said:
Has anyone actually tried this on there epic? I have an advocate device and prefer not to ruin it before I even goes active on my line.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Yes, I can confirm this absolutely does work. Joeykrim and I spent the better part of an hour working on my Epic and hammering out the kinks. I now happily have root access, and there are no words to describe how happy I am to have QuickBoot and AdFree Android back up and running

Awesome Ill be giving this a shot tomorrow. Thanks for all the hard work!
Sent from my SPH-D700 using XDA App

I assume this is just a quick fix until kernel source is released? (due to lack of apply:update.zip in the recovery)

Now i know this is a noob question and all, but;
How do i adb in ubuntu?
I have the environment all set up, eclipse, adt, and the sdk...im just lost after that...

Does the root still intact after reboot?

ImSoHungry said:
Now i know this is a noob question and all, but;
How do i adb in ubuntu?
I have the environment all set up, eclipse, adt, and the sdk...im just lost after that...
Click to expand...
Click to collapse
http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/

JGeZau said:
http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
Click to expand...
Click to collapse
can i haz your baby?!
thanks

2kmy477 said:
Does the root still intact after reboot?
Click to expand...
Click to collapse
Yes it does. That was the main problem Joey and I were having was getting the root to be persistant.

chris5h said:
Yes it does. That was the main problem Joey and I were having was getting the root to be persistant.
Click to expand...
Click to collapse
Great,thanks.I'm wating for the new version of wifi tether to work on the epic.

You mean the source code that is available at opensource.samsung.com when you search for SPH-D700?

dseo80 said:
I assume this is just a quick fix until kernel source is released? (due to lack of apply:update.zip in the recovery)
Click to expand...
Click to collapse
You mean the source code that is available at opensource.samsung.com when you search for SPH-D700?

Is nand unlocked?

No, it is not.

Root is a great first step. Now.. let's get bootloader access and get some stock 2.2 ROMs running for maximum awesome.

Anyone have the stock rom?

Whosdaman said:
Anyone have the stock rom?
Click to expand...
Click to collapse
You can find the system dump at the forums in androidcentral.com
Sent from my PC36100 using XDA App

[Q] GingerBreak: not found

Hello all: I am having a problem trying to root my Droid Charge. when I type adb shell, I get the $.
Then I type in /data/local/Gingerbreak
it says /data/local/Gingerbreak: not found
Any ideas?
thank you very much,

MrSpohn1 said:
Hello all: I am having a problem trying to root my Droid Charge. when I type adb shell, I get the $.
Then I type in /data/local/Gingerbreak
it says /data/local/Gingerbreak: not found
Any ideas?
thank you very much,
Click to expand...
Click to collapse
right after "adb shell" type "chmod 775 /data/local/Gingerbreak"
Then type: /data/local/Gingerbreak
That should give you premission.

MrSpohn1 said:
Hello all: I am having a problem trying to root my Droid Charge. when I type adb shell, I get the $.
Then I type in /data/local/Gingerbreak
it says /data/local/Gingerbreak: not found
Any ideas?
thank you very much,
Click to expand...
Click to collapse
try /data/local/GingerBreak

Sorry. I misstyped here. I did type GingerBreak on the thing. It isn't denying any permission. It is saying that it can't find it. I think I may have erred on my code insertion in the PATH section. It says it found my device, and when I push something it says all of what different commands mean. Is that correct? I only added the direct path to adb. Is there something else I was supposed to do?
Thanks

MrSpohn1 said:
Sorry. I misstyped here. I did type GingerBreak on the thing. It isn't denying any permission. It is saying that it can't find it. I think I may have erred on my code insertion in the PATH section. It says it found my device, and when I push something it says all of what different commands mean. Is that correct? I only added the direct path to adb. Is there something else I was supposed to do?
Thanks
Click to expand...
Click to collapse
Just use gingersnap
http://forum.androidcentral.com/cha...harge-5-19-11-windows-mac-now-gingersnap.html

Yeah Gingersnap rocks !! I Odin'd back to ED1 and then opened Gingersnap and pressed start and about 5 seconds later I was rooted !!

Verizon Root (MAC)

Has anyone successfully done this? I have been looking for a guide everywhere and cannot find one. And all that I have is macs around me lol

Ohleo said:
Has anyone successfully done this? I have been looking for a guide everywhere and cannot find one. And all that I have is macs around me lol
Click to expand...
Click to collapse
I just got one and have not searched, but in theory a *nix guide should work the same.

jatilq said:
I just got one and have not searched, but in theory a *nix guide should work the same.
Click to expand...
Click to collapse
bump, in the same boat

I rooted my Verizon S3 on a Mac using this (not my method, just sharing):
http://forum.xda-developers.com/showpost.php?p=29388584&postcount=96
It's basically using Noxious Ninja's files that are used in the (much easier) Windows method root tool. Still not too bad. The only difference for Macs is whenever it says:
Code:
adb push su /data/local/
for example, you have to type it in a Terminal window as:
Code:
./adb push su /data/local/
with the .(period) and / (forward slash) before the "adb" command.
Let me know if you need any more help. I was thinking about whipping up a quick tutorial for Macs, as I was unable to find one other than the code I linked to by "caslca" in the Root Tool thread. Good luck!

http://forum.xda-developers.com/showthread.php?t=1762709

cscho0415 said:
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
Yeah Adam Outlers Casual works for rooting on a mac....that's what I used to root mine. It's a tool to root and unlock the bootloader, I just did the root not unlock. Haven't had any issues.

[Q] NEC Medias W N-05E root? (dual screen phone)

Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!

bohemianRhapsody said:
Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!
Click to expand...
Click to collapse
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.

root is easy
bohemianRhapsody said:
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.
Click to expand...
Click to collapse
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition

it0 said:
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition
Click to expand...
Click to collapse
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?

Lukas_a_1996 said:
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?
Click to expand...
Click to collapse
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.

it0 said:
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.
Click to expand...
Click to collapse
Thanks for the reply . I tried to run the command in impactor but whatever i do i get "Signature bugs unavailable" could it be that i have the wrong ADB drivers installed or is my Impactor setup wrong?
Edit: yeah im running 4.1.2 Build A1001231

You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.

it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
All the adb commands basically work but nothing works with impactor i just get error

it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
Bump!

How to Root Medias N05e
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks

nguyenbuulam said:
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks
Click to expand...
Click to collapse
There is a way for temp root N05E, basically u can use pm disable command or other su stuff. But u cannot mount system rw right now.

Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working

How to enter recovery mode?
Despite starting this thread, in the end I never did bother to attempt rooting.
Anyway, unfortunately now the phone refuses to boot. Not triggered by anything obvious, haven't installed any new software recently, etc. Just hung one day and then when I removed and re-inserted the battery, it won't get any further than the "docomo" splash screen. I.e. the OS doesn't appear to be getting bootstrapped at all. The "docomo" splash screen appears and disappears then the phone sits there with both screens powered up but blank.
As it happens, I had ADB Debug enabled in the developer options at the time, so I've tried to see if I can adb shell into the device, but no luck. Not surprised as it's clearly not getting far enough into the boot for that to work.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?

bohemianRhapsody said:
Despite starting this thread, in the end I never did bother to attempt rooting.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?
Click to expand...
Click to collapse
In recovery mode, clear cache, etc..
To get there hold volume down and power at the same time,then you'll see the broken android then wait/ press vol down a couple of times to see the menu.

GRbit said:
Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working
Click to expand...
Click to collapse
did you ever figure out the recovery keys?

hamishhhhs said:
did you ever figure out the recovery keys?
Click to expand...
Click to collapse
No I didn't(
I'm actually sold this phone and lost interest in the topic.

GRbit said:
No I didn't(
I'm actually sold this phone and lost interest in the topic.
Click to expand...
Click to collapse
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far

hamishhhhs said:
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far
Click to expand...
Click to collapse
Sorry, but this was too long time ago. Nothing left

GRbit said:
Sorry, but this was too long time ago. Nothing left
Click to expand...
Click to collapse
how would j be able to get the files from my phone?

hamishhhhs said:
how would j be able to get the files from my phone?
Click to expand...
Click to collapse
I dunno man.
I've already described (in the first post you have quoted) what I achieved with this github repo https://github.com/android-rooting-tools/android_run_root_shell . That's all I've got.

Rooting Android TV with /system partition ro

Hey, I have a smart android TV running on some cvte board from china and running android 7.1.1 from 2020.
The /system partition is mounted ro [remount allowed] and /data rw but trying to edit that gives access denied error.
The adb reboot fastboot and adb reboot recovery just reboots the tv.
I have enabled adb by going into the service menu and enabling in debug.
I have seen modified scripts in /system/bin that refer to su scripts.
One of them being cvte_su_service and sys_control. These scripts do not work without adb root shell.
I cannot find any exploit for this tv and it is a 32bit hislicion cpu with mali 450 gpu.
I use adb with the termux terminal emulator.
I cannot find any way to elevate permissions on the tv and i cannot find any type of help on this.
P.S i also saw many hotkeys like the service menu but i cant understand what they are for since they are in Chinese..

At least your device has the ability of installing apps freely
I can help you to translate the hotkeys to English in 3 days if necessary.

Well thanks!
yeah idfk what those keys mean or do, only the factory menu one.
Mark Zhang said:
At least your device has the ability of installing apps freely
I can help you to translate the hotkeys to English in 3 days if necessary.
Click to expand...
Click to collapse
I can help you with installing termux and adb on that so you can run adb on your tv itself and install through it like that.

Great! Thanks too!
How about continue on Chat apps such as Telegram?
The forum is not a convenient place for long conversations.

Mark Zhang said:
Great! Thanks too!
How about continue on Chat apps such as Telegram?
The forum is not a convenient place for long conversations.
Click to expand...
Click to collapse
I'm not on telegram but you can contact me on Twitter! @Kenora_I

Could you please check a tweet from you? I'm under it ~ (。・ω・。)

Mark Zhang said:
Could you please check a tweet from you? I'm under it ~ (。・ω・。)
Click to expand...
Click to collapse
Kay.

Kenora_I said:
Hey, I have a smart android TV running on some cvte board from china and running android 7.1.1 from 2020.
The /system partition is mounted ro [remount allowed] and /data rw but trying to edit that gives access denied error.
The adb reboot fastboot and adb reboot recovery just reboots the tv.
I have enabled adb by going into the service menu and enabling in debug.
I have seen modified scripts in /system/bin that refer to su scripts.
One of them being cvte_su_service and sys_control. These scripts do not work without adb root shell.
I cannot find any exploit for this tv and it is a 32bit hislicion cpu with mali 450 gpu.
I use adb with the termux terminal emulator.
I cannot find any way to elevate permissions on the tv and i cannot find any type of help on this.
P.S i also saw many hotkeys like the service menu but i cant understand what they are for since they are in Chinese..
Click to expand...
Click to collapse
@jwoegerbauer sorry for the mention but do you have any amazing ideas on how to accomplish root on this. Sorry for the mention, I know you must be busy and you don't need to reply.
Just kinda at my wits end with this.

No problems.
I think the answer I gave here:
Fully Rooting Onyx Boox Poke3 e-reader
UPDATE: Changed the Topic as we are getting away from the original question in post 1 to the actual problem: figuring out how to fully root an Onyx Boox Poke3 e-reader running Android 10. "Fully" meaning including full r/w access to /system and...
forum.xda-developers.com

Do you know how to open an app with IR Remote? Editing keylayouts?