Database Info

Samsung Behold 2 Rooting

Here is the commands I used:
cd\
cd androidsdk\tools
adb push try3.dat /data/local
adb shell chmod 0755 /data/local/try3
adb shell
/data/local/try3 /system/bin/sh
mount -o rw,remount /dev/st9 /system
chmod 04755 /system/bin/sh
cat /sdcard/su.dat > /system/bin/su1
cat /sdcard/su.dat > /system/bin/su
chmod 04755 /system/bin/su
su
cat /system/bin/playlogo > /system/bin/playlogo_real
/system/bin/chmod 0755 /system/bin/playlogo_real
echo “#!/system/bin/sh
/data/local/try3.dat /system/bin/sh
mount -o rw,remount /dev/st9 /system
chmod 04755 /system/bin/sh
cat /system/bin/su1 > /system/bin/su
chmod 04755 /system/bin/su
/system/bin/playlogo_real” > /system/bin/playlogo
exit
exit
exit
adb install Superuser.apk
adb shell reboot
It said Superuser.apk installed successful. When I tried to reboot it said permission denied.
Here is the CMD pasted. Please help me I have no idea what I am doing wrong.
C:\AndroidSDK>cd\
C:\>reboot
'reboot' is not recognized as an internal or external command,
operable program or batch file.
C:\>cd\
C:\>cd androidsdk\
C:\AndroidSDK>adb shell
error: device not found
C:\AndroidSDK>adb shell
error: device not found
C:\AndroidSDK>adb shell
$ su
su
su: permission denied
$ exit
exit
C:\AndroidSDK>adb devices
List of devices attached
SGH-T939 device
C:\AndroidSDK>adb shell
$ su.dat
su.dat
su.dat: permission denied
$ exit
exit
C:\AndroidSDK>adb shell
$ su
su
su: permission denied
$ su.dat
su.dat
su.dat: permission denied
$ exit
exit

Panasonic Eluga Power P-07D

Greetings,
I have received my shiny new Eluga Power and I am wondering if anybody else has this device and if anybody has rooted there's?
Sent from my P-07D using xda premium

Edit: moved to Q&A, lets see if you can get some help but do search for your device.
First welcome...
Next time post in the Q&A section for questions. To better serve you do a search for your device and look in the Dev section for your model device...also you will find a Q&A section there, Thank you.
Btw ensure you read the forum rules.
Sent from a closet, at Arkham Asylum using Forum Runner.

ianford10 said:
Greetings,
I have received my shiny new Eluga Power and I am wondering if anybody else has this device and if anybody has rooted there's?
Sent from my P-07D using xda premium
Click to expand...
Click to collapse
Where did you get it from?HOw much? How's it first impression?

mixmaster said:
Where did you get it from?HOw much? How's it first impression?
Click to expand...
Click to collapse
Had to import it from a Japanese eBay store with a cost of £560 with delivery. First impressions of the phone are very good, nice big clear screen, batter life is okay considering the screen size, calls are crisp and clear, feels good in the hand to hold. Will have more info as I use it over the next couple of weeks
Sent from my P-07D using xda premium

Rooting P-07D success...
I was able to root my Panasonic Eluga Power (P-07D) you can check the screenshot below. As of the moment I am re-writing the steps for others so they can easily follow the instructions as this was written in Japanese (Thanks to http://sithxi.blog49.fc2.com/blog-entry-51.html and goroh_kun. Hopefully this would help others root there device just like me. The only main problem for me now is SIM unlock the device.

Panasonic Eluga Power rooting instructions...
As promised here are the steps: (This seems to look like a temporary root, as you will loose it once the device rebooted) But still it's a good primary step. For the source code it can be downloaded from here. Panasonic Eluga Power Source Code
goroh_kun
2012/10/18
root privileges acquisition & tomoyo released experimental version in
the p-07d
things to do
Run:
1. >adb restore p-07d.ab
I press OK authentication
After the restore is finished
2. Open another command prompt and type the following:
>adb shell
$cd /data/data/com.android.settings/a/
$ls -l -d
drwxrwxrwx system system a
- check directory called A exists, it is world readable, writable as
show above
3. $ ls -l
⇒ file00 〜 file99 check if files exists
Delete all file from file00 ~ file99
run the command below
4. >adb shell
$cd /data/data/com.android.settings/
$rm -r a/*
change permissions to 777 /persist
This is the tricky part as you need to to do this using two command prompt, one running the adb restore p-07d.ab while the other on the shell command running ln -s /persist a/file99 command.
5. First run: >adb restore p-07d.ab while it is restoring on the other command prompt run in shell $ ln-s / persist a/file99
6. Now lets check the permission to folder /persist by typing on the command prompt that is already in shell.
$ ls -l -d /persist
drwxrwxrwx system system persist <--(you should see this)
Now move on your other command prompt window and run the following commands. (you can download the needed file at this link
Then run the command below to push the files needed for rooting:
>adb push init.cne.rc /data/local/tmp
>adb push p07dgetroot /data/local/tmp
>adb push xsh /data/local/tmp/
>adb push libQ.so /persist
>adb shell rm /persist/init.cne.rc
>adb shell ln -s /data/local/tmp/init.cne.rc /persist/init.cne.rc
>adb reboot
The next step is kinda hard to understand and I qoute: "/persist at Startup directory of the recovery process because it will not be restored and persist the only symbolic links should be a basic /data/local/tmp to keep the change."
After re-move environment variable is changed to check (LD_PRELOAD= /presist/libQ.so and be sure it is).
7. > adb shell
$echo $LD_PRELOAD
/persist/libQ.so <--(you should see this)
8. To Unlock Tomoyo, follow this steps:
> adb shell
$ cat /data/local/tmp/p07dgetroot > /tmp/xsh
$ ls -l /tmp/xsh
-rw-rw-rw- shell shell xsh <--(you should see this)
Make sure that wirelss LAN is ON before doing the command below:
9. WLAN ON / TURN OFF WLAN / TURN ON WLAN (wait to be connected before typing the below command or you will have to do it again)
$ ls -l /tmp/xsh
-rwsr-sr-x root root xsh <--(you should see this)
$ /tmp/xsh
/tmp/xsh
/tmp/.mem fd=3
read ret = 256
write ret = 256
At this stage, Tomoyo is now unlocked
10.
$rm /tmp/xsh
$cat /data/local/tmp/xsh > /tmp/xsh
11. WLAN ON / TURN OFF WLAN / TURN ON WLAN (wait to be connected before typing the below command or you will have to do it again)
$ls -l /tmp/xsh
-rwsr-sr-x root root xsh <--(you should see this)
12. $/tmp/xsh
$(precmd)[email protected]$HOSTNAME:${PWD:-?} $ <--(you should see
this)
Here is a shell with root privileges, so stand up and be able to work a variety. You can also install the su
13. $(precmd)[email protected]$HOSTNAME:${PWD:-?} $
$ mount -o remount,rw /system /system
$ chmod 777 /system/app/
$ chmod 777 /system/bin/
$ chmod 777 /system/xbin/
Open another command prompt:
adb push Superuser.apk /system/app/
adb push su /system/bin/
adb push busybox /system/xbin/
Go back to ($(precmd)[email protected]$HOSTNAME:${PWD:-?} $) window:
chown root.root /system/bin/su
chmod 6755 /system/bin/su
chmod 644 /system/app/Superuser.apk
chown root.shell /system/xbin/busybox
chmod 755 /system/xbin/busybox
chmod 755 /system/app/
chmod 755 /system/bin/
chmod 755 /system/xbin/
Verify root access by installing "Root Checker".
Note: each time you reboot your device you will need to run Tomoyo Unlock script to regain root access (Step 8 - 12) which I re-wrote below:
8. Tomoyo Unlock
> adb shell
$ cat /data/local/tmp/p07dgetroot > /tmp/xsh
$ ls -l /tmp/xsh
-rw-rw-rw- shell shell xsh <--(you should see this)
WLAN ON / OFF / ON
$ ls -l /tmp/xsh
-rwsr-sr-x root root xsh <--(you should see this)
$ /tmp/xsh
/tmp/xsh
/tmp/.mem fd=3
read ret = 256
write ret = 256
At this stage, tomoyo is released
$rm /tmp/xsh
$cat /data/local/tmp/xsh > /tmp/xsh
WLAN ON / OFF / ON
$ls -l /tmp/xsh
-rwsr-sr-x root root xsh <--(you should see this)
$/tmp/xsh
$(precmd)[email protected]$HOSTNAME:${PWD:-?} $ <---(you should end up here to regain root access, if not redo it again)
Proof:

ask questions
hi,
If it unlocked the device of sim by docomo, when i root it, the condition of unlock sim whether will cancel????
---------- Post added at 12:10 AM ---------- Previous post was at 12:06 AM ----------
dear zyper95,
Can you make the picture to show the process of root??
thank a lot

Panasonic P-07D
Hello, Someone tell me how to reset to factory settings "Android system recovery -> wipe data / factory reset -> Yes-delete all user data -> Please input password". What is the password to be entered? Help please.

Panasonic Eluga Power P-07D hard reset plz:crying::crying::crying:

[GUIDE] How to Install .zip Roms on Your phone without touching your phone !!

Installing Recovery Roms With ADB ​
About Article
Thats really funny to install a rom on your phone without touching your phone but thats more difficult than flashing rom from recovery . Here I fully explain the method but you can save commands in .bat and .sh files for using next times . It takes less than 5 min to flash rom if have saved commands in executable files . This guide explains the whole commands so its too long ! Dont confuse , just copy pase commands and save them into executable files then run all by few clicks
Disclaimer
*/
I am not responsible for any damage or ... done to your device by using this . Do at your own risk !
*/
Step 1 : What you need !
You need :
1- A healthy Galaxy S Plus device
2- ADB drivers and USB debugging on
3- Smasung USB drivers
4- Lots of patience
5- Having Basic Linux Shell Knowledge
6- 200 mg free space at data partition
Step 2 : Starting ....
1- Connect phone to PC and Do'nt touch it again ! Proccess here starts We want to do this without touching phone
2- Go to adb directory open cmd and type :
Code:
adb reboot recovery
Device will reboot to recovery
3- Type in cmd :
Code:
adb shell
busybox mount -rw -o remount /system
busybox rm -rf /system
busybox mkdir /system
busybox chmod 777 /system
mount -rw -o remount /data
4- Exit adb shell
5- Rename your .zip rom to "rom.zip" put it into c:\\ ( you can put it any where else but change path in the command )
6- open adb and type
Code:
adb push C:\\rom.zip /data/rom.zip
adb shell
busybox unzip /data/rom.zip -d /system/
busybox mount -rw -o remount /system
busybox mount -rw -o remount /data
busybox mount -rw -o remount /cache
busybox rm -rf /data /cache
busybox mkdir /data /cache
busybox chmod 777 /data
busybox chmod 777 /cache
busybox rm -f /data/rom.zip
busybox rm -rf /system/META-INF
busybox dd if=/system/boot.img of=/dev/block/mmcblk0p8
rm -f /system/boot.img
p=busybox chmod
s=busybox ln -s /system/bin/toolbox
busybox mv /system/system /system
7- Type agin ( I do not write busybox symlink ... its users selectable )
Code:
cd /system/bin
$s cat
$s chmod
$s chown
$s date
$s dd
$s df
$s dmesg
$s getevent
$s getprop
$s hd
$s id
$s ifconfing
$s iftop
$s insmod
$s ioctl
$s ionice
$s kill
$s ln
$s log
$s ls
$s lsmod
$s lsof
$s md5
$s mkdir
$s mount
$s mv
$s nandwrite
$s netstate
$s newfs_msdos
$s notify
$s printenv
$s ps
$s r
$s reboot
$s renice
$s rm
$s mmod
$s route
$s schedtop
$s sendevent
$s setconsole
$s setprop
$s sleep
$s smd
$s start
$s stop
$s sync
$s top
$s unmount
$s uptime
$s umstate
$s watchprops
$s wipe
busybox ln -s /system/fonts/Roboto-Regular.ttf /system/fonts/DroidSans.ttf
busybox ln -s /system/bin/mksh /system/bin/sh
8- Type :
Code:
$p 777 /system
$p 777 /system/*
$p 777 /system/bin/*
$p 777 /system/xbin/*
$p 644 /system/app/*
$p 644 /system/etc/*
$p 777 /system/etc/init.d/*
$p 644 /system/fonts/*
$p 644 /system/frimware/*
$p 644 /system/framework/*
$p 755 /system/vendor/*
$p 755 /system/usr/*
$p 644 /system/tts/*
$p 644 /system/media/*
$p 644 /system/build.prop
$p 644 /system/lib/*
$p 644 /system/cameradata/*
busybox reboot
9- now Disconnect Phone From ADB
10- If your rom doesnt boot Fix Permissions from Recovery
******
Please Excuse me For any Mistakes becuase I spend a lot of time to write this
******
I didnt fully test this but this must work !

[OT on] How many Bytes are 200mg of free space? [OT off]
ew, looks really to be hard work if it needs to be typed all the way^^
I recognize that you did not delete the boot.img file after dd'ing it into the Kernel memory block. The rest should work indeed.

magicw said:
[OT on] How many Bytes are 200mg of free space? [OT off]
ew, looks really to be hard work if it needs to be typed all the way^^
I recognize that you did not delete the boot.img file after dd'ing it into the Kernel memory block. The rest should work indeed.
Click to expand...
Click to collapse
200 * 1024 = 204800 (kb) (as shown in "cat /proc/partitions")
204800 * 1024 = 209715200 (bytes)
Google does this for you btw, ask this: how many bytes is 200mb
and you get:
200 megabytes = 209 715 200 bytes
and you just copy the text into files and execute them on your phone.. else its way to much work lol

broodplank1337 said:
200 * 1024 = 204800 (kb) (as shown in "cat /proc/partitions")
204800 * 1024 = 209715200 (bytes)
Google does this for you btw, ask this: how many bytes is 200mb
and you get:
200 megabytes = 209 715 200 bytes
and you just copy the text into files and execute them on your phone.. else its way to much work lol
Click to expand...
Click to collapse
he was joking about alireza wrote mg instead of mb (MB if we want to be picky)

ktulu84 said:
he was joking about alireza wrote mg instead of mb (MB if we want to be picky)
Click to expand...
Click to collapse
I couldnt open my eyes after writing this haha ... It tooks 5 hours to write this
magicw said:
[OT on] How many Bytes are 200mg of free space? [OT off]
ew, looks really to be hard work if it needs to be typed all the way^^
I recognize that you did not delete the boot.img file after dd'ing it into the Kernel memory block. The rest should work indeed.
Click to expand...
Click to collapse
Sorry gona fix it ....
I ve just wrote the toolbox symlink , If I had wrriten the whole busybox symlinks it needed about 10 hours to write busybox usually has more than 600 symlinks !

alireza7991 said:
I couldnt open my eyes after writing this haha ... It tooks 5 hours to write this
Sorry gona fix it ....
I ve just wrote the toolbox symlink , If I had wrriten the whole busybox symlinks it needed about 10 hours to write busybox usually has more than 600 symlinks !
Click to expand...
Click to collapse
Yeah, we know and thanks for your work... We are only grammar Nazi... Lol
Inviato dal mio GT-I9001 con Topatalk 2

Can you root an XT925 without unlocking the bootloader?

Thinking about buying this phone, but don't wanna void my warranty. I've seen a wealth of information, but I am confused as to what is outdated or not.

timmytucker718 said:
Thinking about buying this phone, but don't wanna void my warranty. I've seen a wealth of information, but I am confused as to what is outdated or not.
Click to expand...
Click to collapse
My HD is rooted while bootloader is still locked

mr_5kool said:
My HD is rooted while bootloader is still locked
Click to expand...
Click to collapse
How did you do it?

timmytucker718 said:
How did you do it?
Click to expand...
Click to collapse
I use the method and files from my XT902 but it works. I don't remember the source of this method (Sorry). I made several changes. My HD is OTA updated from 4.0 to 4.1.2. Here is the method (The risk is yours):
1) Preparation
- SDK & USB Drivers
- Download file from the following address: http://www.mediafire.com/download/13htvihh6c2mhs2/HD.rar or scroll down
- Unzip the file to a specific folder (I put HD folder to the root of C drive)
2) Plug your HD to PC (connect as MTP, unknown source and debugging is on, of course)
3) Do these command (at the directory where you put and perform the adb commands)
- adb push C:\HD\su /data/local/tmp/su
- adb push C:\HD\Superuser.apk /data/local/tmp/Superuser.apk
- adb push C:\HD\busybox /data/local/tmp/busybox
- adb push C:\HD\auto_root.sh /data/local/tmp/auto_root.sh
- adb push C:\HD\unlock_security_module /data/local/tmp/unlock_security_module
- adb push C:\HD\break_setresuid /data/local/tmp/break_setresuid
- adb push C:\HD\mole-plough-ccsecurity.so /data/local/tmp/mole-plough-ccsecurity.so
- adb push C:\HD\mole-plough-lsm.so /data/local/tmp/mole-plough-lsm.so
If any file is pushed unsuccessfully, you have to re-push it, of course
4) Use unlock_security_module to obtain temporary root
- adb shell
- [email protected]:/ $ cd /data/local/tmp/
- [email protected]:/data/local/tmp $ chmod 777 *
- [email protected]:/data/local/tmp $ ./unlock_security_module
- [email protected]:/data/local/tmp $ ./break_setresuid
You’ll see messages about the process. If it fails, then I’m sorry, I don’t know why yet. If it works without “fail”, you success. Here you’ll something like: Unlocked LSM, Do setresuid… I don’t remember them exactly and after all, the command will change from shell ($) to su (#).
5) Load su, Superuser.apk busybox to system
- [email protected]:/data/local/tmp # mount -o rw,remount /system /system
- [email protected]:/data/local/tmp # cat /data/local/tmp/su > /system/xbin/su
- [email protected]:/data/local/tmp # cat /data/local/tmp/busybox > /system/xbin/busybox
- [email protected]:/data/local/tmp # cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
- [email protected]:/data/local/tmp # chmod 644 /system/app/Superuser.apk
- [email protected]:/data/local/tmp # cd /system/xbin
- [email protected]:/system/xbin # chown root.root su
- [email protected]:/system/xbin # chown root.root busybox
- [email protected]:/system/xbin # chmod 6755 su
- [email protected]:/system/xbin # chmod 755 busybox
- [email protected]:/system/xbin # mount -o ro,remount /system /system
6) When it’s done, you can remove the cable from PC. Check and see if SuperSU was installed. If it wasn’t, you can download it (SuperSU) from Play Store. Install busybox from Play Store and do the Smart Install. Your HD is now temporary rooted so do not reboot your phone.
7) Install Script Manager – SManager (devwom) from Play Store. Run SManager and choose Browse as root.
- Navigate to /data/local/tmp/ and open auto_root.sh as Script/Excutable (touch and keep for a while).
- Toggle Su on (the icon will change colour to green) and save.
You can reboot and enjoy your permanent root now.

mr_5kool said:
I use the method and files from my XT902 but it works. I don't remember the source of this method (Sorry). I made several changes. My HD is OTA updated from 4.0 to 4.1.2. Here is the method (The risk is yours):
1) Preparation
- SDK & USB Drivers
- Download file from the following address: http://www.mediafire.com/download/13htvihh6c2mhs2/HD.rar or scroll down
- Unzip the file to a specific folder (I put HD folder to the root of C drive)
2) Plug your HD to PC (connect as MTP, unknown source and debugging is on, of course)
3) Do these command (at the directory where you put and perform the adb commands)
- adb push C:\HD\su /data/local/tmp/su
- adb push C:\HD\Superuser.apk /data/local/tmp/Superuser.apk
- adb push C:\HD\busybox /data/local/tmp/busybox
- adb push C:\HD\auto_root.sh /data/local/tmp/auto_root.sh
- adb push C:\HD\unlock_security_module /data/local/tmp/unlock_security_module
- adb push C:\HD\break_setresuid /data/local/tmp/break_setresuid
- adb push C:\HD\mole-plough-ccsecurity.so /data/local/tmp/mole-plough-ccsecurity.so
- adb push C:\HD\mole-plough-lsm.so /data/local/tmp/mole-plough-lsm.so
If any file is pushed unsuccessfully, you have to re-push it, of course
4) Use unlock_security_module to obtain temporary root
- adb shell
- [email protected]:/ $ cd /data/local/tmp/
- [email protected]:/data/local/tmp $ chmod 777 *
- [email protected]:/data/local/tmp $ ./unlock_security_module
- [email protected]:/data/local/tmp $ ./break_setresuid
You’ll see messages about the process. If it fails, then I’m sorry, I don’t know why yet. If it works without “fail”, you success. Here you’ll something like: Unlocked LSM, Do setresuid… I don’t remember them exactly and after all, the command will change from shell ($) to su (#).
5) Load su, Superuser.apk busybox to system
- [email protected]:/data/local/tmp # mount -o rw,remount /system /system
- [email protected]:/data/local/tmp # cat /data/local/tmp/su > /system/xbin/su
- [email protected]:/data/local/tmp # cat /data/local/tmp/busybox > /system/xbin/busybox
- [email protected]:/data/local/tmp # cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
- [email protected]:/data/local/tmp # chmod 644 /system/app/Superuser.apk
- [email protected]:/data/local/tmp # cd /system/xbin
- [email protected]:/system/xbin # chown root.root su
- [email protected]:/system/xbin # chown root.root busybox
- [email protected]:/system/xbin # chmod 6755 su
- [email protected]:/system/xbin # chmod 755 busybox
- shell[email protected]:/system/xbin # mount -o ro,remount /system /system
6) When it’s done, you can remove the cable from PC. Check and see if SuperSU was installed. If it wasn’t, you can download it (SuperSU) from Play Store. Install busybox from Play Store and do the Smart Install. Your HD is now temporary rooted so do not reboot your phone.
7) Install Script Manager – SManager (devwom) from Play Store. Run SManager and choose Browse as root.
- Navigate to /data/local/tmp/ and open auto_root.sh as Script/Excutable (touch and keep for a while).
- Toggle Su on (the icon will change colour to green) and save.
You can reboot and enjoy your permanent root now.
Click to expand...
Click to collapse
is this a different method than the saferoot method I have since read about?

timmytucker718 said:
is this a different method than the saferoot method I have since read about?
Click to expand...
Click to collapse
I don't know the saferoot method
I've used this method when my M had failed to root by other method
It's worked on my M and HD

[guide] how to do a rom dump [samsung]

HOW TO DUMP SAMSUNG FACORY ROM USING ADB
MUST BE ROOTED WITH BUSYBOX INSTALLED
1. You must have Android SDK https://dl.google.com/android/android-sdk_r24.4.1-windows.zip
2. Your Devices USB Driver package installed
3. USB DEBUGGING On Your device needs to be Enabled. go to settings > about device> and tap Build Number 5 times and you will see you are now a developer. go back to settings Select Devloper options> usb debugging.
4. After you install busybox to your device. Use Root browser on your device and go to Data>local and long press on busybox to change the permisions select all of them.
Now we are Ready to start
C:\android\platform-tools>adb devices
List of devices attached
42007ffad33453a9 device
C:\android\platform-tools>adb shell
[email protected]:/ $ cd /sdcard OR
[email protected]:/ $ cd /storage/2082-08E3 < What my ext sdcard is named yours maybe different
1|[email protected]:/sdcard $ su
[email protected]:/storage/emulated/0 # chmod 755 /data/local/busybox
THEN
/data/local/busybox tar cvf Samsung.tar /system <
tar: removing leading '/' from member names
HERE'S A COPY OF MINE JUST INCASE YOUR HAVING PROBLEMS
C:\android\platform-tools>adb shell
[email protected]:/ $ cd /sdcard
[email protected]:/sdcard $ chmod 755 /data/local/busybox
chmod: chmod '/data/local/busybox' to 100755: Permission denied
1|[email protected]:/sdcard $ chmod 755 /data/local/busybox
chmod: chmod '/data/local/busybox' to 100755: Permission denied
1|[email protected]:/sdcard $ su
[email protected]:/storage/emulated/0 # chmod 755 /data/local/busybox
/data/local/busybox tar cvf Samsung.tar /system <
tar: removing leading '/' from member names