Database Users

Samsung Galaxy Tab 2 7: GT-P3113

Just received...any word on Rooting this bad boy. So Far love ICS!!

+1. We need to root it ASAP. Thanks.

Having some wifi issues...cutting off on randomly...n e thoughts

i wanna root too. maybe try z4? will report back.

dLo GSR said:
i wanna root too. maybe try z4? will report back.
Click to expand...
Click to collapse
Picking mine up after work, hopefully this will get some dev love.

Just a heads up; I picked one of these up on Sunday, tried using Z4 a little while ago, and wasn't able to obtain root. Might try a couple other methods later on. Hopefully this device gets its own subforum pretty soon. Haha.

What sound chip is used in this Tab 2? Did Samsung go back to Wolfson or are they still using the (ugh) Yamaha?
UPDATE: It's a Wolfson WM1811 Stereo CODEC (WM1811AE 22AGKGW)! And.. it sounds great!

I found a universal root method that may be able to help us, but I am no developer. This appears to work on a number of phones and tablets.
https://github.com/saurik/mempodroid/

I'd just like to see the tab 2 get its own sub forum. I'd like to follow any development.
So far so good. I love this little thing. Coming from a nexus s, i really thought Touch Wiz was going to be annoying. Took me no time to adjust.
I havent had any WIFI issues. I connect to several wifi networks in a day. Never a problem.
Sent from my GT-P3113 using XDA

dmuntean said:
I'd just like to see the tab 2 get its own sub forum. I'd like to follow any development.
So far so good. I love this little thing. Coming from a nexus s, i really thought Touch Wiz was going to be annoying. Took me no time to adjust.
Click to expand...
Click to collapse
just grab apex or novalauncher to replace the sammy launcher

GRZLA said:
I found a universal root method that may be able to help us, but I am no developer. This appears to work on a number of phones and tablets.
Click to expand...
Click to collapse
Tu use mempodroid you need the exit and call "offsets", this is the usage command for the Galaxy Nexus:
$ ./mempodroid 0xd7f4 0xad4b mount -o remount,rw '' /system
$ ./mempodroid 0xd7f4 0xad4b sh
#
Galaxy Nexus 4.0.2: 0xd7f4 0xad4b
Does anyone know how to obtain this parameters for the galaxy tab 2 ???
Using this post:
Nesquick95 said:
Saurik's mempodroid exploit needs offsets of "exit" and "setresuid" fuctions calls in order to work.
Here's a tool that may find this two offsets while running on your ICS device and give you the mempodroid command line to run for gaining a temporary root shell.
This tool doesn't add any capability to Saurik's exploit.
Please let me know if you have any idea for improvement.
Feel free to use this tool, at your own risks.
1- download and unzip
2- push the two binaries to /data/local/tmp with adb
3- chmod 755
4- run n95-offsets
5- copy / paste the command line given by the tool
If the trick works, you will see the $ prompt change to a # one.
Hope it will help.
Click to expand...
Click to collapse
I got this offsets for mempodroid:
n95-offsets by Nesquick95
Gets requiered offsets for mempodroid exploit
./mempodroid 0xd904 0xae5f sh
Click to expand...
Click to collapse
But when i try to copy the "su binary" file it still displays error
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push su /system/bin
failed to copy 'su' to '/system/bin/su': Read-only file system
Click to expand...
Click to collapse
Any clues... anyone ??

do this:
adb push <path to mempodroid> /data/local/tmp/
adb shell
$ chmod 755 /data/local/tmp/mempodroid
$ /data/local/tmp/mempodroid 0xd904 0xae5f sh
# id
what is the output of the id command after running those commands in adb shell?
if it says uid=0 then i'll be happy

elitrix said:
do this:
adb push <path to mempodroid> /data/local/tmp/
adb shell
$ chmod 755 /data/local/tmp/mempodroid
$ /data/local/tmp/mempodroid 0xd904 0xae5f sh
# id
what is the output of the id command after running those commands in adb shell?
if it says uid=0 then i'll be happy
Click to expand...
Click to collapse
This is what i tried on my GT-3113 Galaxy Tab 2:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ ls
ls
boomsh
busybox
mempodroid
n95-offsets
output
psneuter
sh
zergRush
[email protected]:/data/local/tmp $ chmod 777 mempodroid
chmod 777 mempodroid
[email protected]:/data/local/tmp $ chmod 755 n95-offsets
[email protected]:/data/local/tmp $ ./n95-offsets
n95-offsets by Nesquick95
Gets requiered offsets for mempodroid exploit
./mempodroid 0xd904 0xae5f sh
1|[email protected]:/data/local/tmp $ ./mempodroid 0xd904 0xae5f mount -o remount,rw
'' /system
ae5f mount -o remount,rw '' /system <
then
Code:
1|[email protected]:/data/local/tmp $ ./mempodroid 0xd904 0xae5f sh
./mempodroid 0xd904 0xae5f sh
1|[email protected]:/data/local/tmp $
STILL the '$' sign !!! i dont have "su" privileges, this feels I'm so close...
when i try again with....
Code:
1|[email protected]:/data/local/tmp $ /data/local/tmp/mempodroid 0xd904 0xae5f sh
/data/local/tmp/mempodroid 0xd904 0xae5f sh
1|[email protected]:/data/local/tmp $
I still get the '$' sign instead of the '#'.

exploit doesn't work on this tab then... on to the next.

elitrix said:
exploit doesn't work on this tab then... on to the next.
Click to expand...
Click to collapse
Either that or the offsets reported by n95-offsets are incorrect. I have no idea how reliable it is or how it works though. Wish I had my tablet with me to dig deeper.

machx0r said:
Either that or the offsets reported by n95-offsets are incorrect. I have no idea how reliable it is or how it works though. Wish I had my tablet with me to dig deeper.
Click to expand...
Click to collapse
I went ahead and check the source code for the “n95-offsets” and found that this code searches for a pattern in memory. :
static const unsigned char exit_pattern[8] = { 0xB0, 0xFF, 0xFF, 0xFF, 0x04, 0x46, 0x00, 0x20};
static const unsigned char suid_pattern[8] = { 0xD0, 0x40, 0xE0, 0x3D, 0x68, 0x28, 0x46, 0x29};
Click to expand...
Click to collapse
So maybe it’s a different pattern for the GT-3113, cause it depends on the kernel version, so my theory is that the offsets are incorrect.

I had spoken to saurik and supplied him the run-as from the tab and he confirmed those offsets...of course he could've been using.the same tool on his end didn't ask so take with a grain of salt in the face of your theory.

Chase Bank app, trying to make a check deposit, it fails when it tries to start the camera. The deposit part of the app wants to take pictures of the check front & back. Then it uploads the pictures.
Sent from my Samsung Galaxy Tab 2 7.0

Wifi antenna seems 2 be a little weak..erratic. i think my old dellstreak 5" had better signal....battery sure takes long to charge

How do you bring up My Apps in Play Store on the Samsung Galaxy Tab 2 - 7.0?
Sent from my Samsung Galaxy Tab 2. - 7.0

Pls someone help me to get info about this device

Hi im porting rom but i dont have this device.
can anyone just open terminal emulator and type
su
ls -l dev/block/platform/msm_sdcc.1/by-name/system
and post here the output?
it will not harm your device ls command only lists files pls i cant do anything without that

I got this:
[email protected]:/ $ su
dev/block/platform/msm_sdcc.1/by-name/system <
lrwxrwxrwx root root 2015-10-08 11:47 system -> /dev/block/mmcblk0p21
[email protected]:/ #
Click to expand...
Click to collapse
Was that what you wanted, or did you want the file it mentions in the output?

SD card not partitioning adb

Okay so i got ADB installed on my computer. ive been trying to partition the card, (samsung evo) i enter in the prompts in the command terminal and heres what i get
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>adb shell
[email protected]:/ $ sm list-disks
disk:179,0
[email protected]:/ $ sm partition disk:179,0 private
[email protected]:/ $
and then my phone says SD card unexpectedly removed.
Any idea where i went wrong? thanks

All sensors broken - need persist partition

SOLUTION: post #18
Hello,
For some reason all of my sensors are gone. See attachment.
Due to some problems i've formatted my "persist" partition. And from what i read, that partition contains all sorts of sensor parameters. So i guess i shouldn't have.
I've checked all files on the forum and original OTA's from oneplus. None of them have (working) partition for me.
Therefor i would like to ask someone with an A2003 device who has working sensors and is running OOS 3.02 or CM13 to perform the following actions and share the file with me:
(root (adb and apps) needed)
Code:
adb shell
su
su
cd /sdcard
dd if=/dev/block/bootdevice/by-name/persist persist.dd.img
exit
exit
And share the file "persist.dd.img" with me. It's on your sdcard.
Thanks very much in advance!

_HugoBoss_ said:
Hello,
For some reason all of my sensors are gone. See attachment.
Due to some problems i've formatted my "persist" partition. And from what i read, that partition contains all sorts of sensor parameters. So i guess i shouldn't have.
I've checked all files on the forum and original OTA's from oneplus. None of them have (working) partition for me.
Therefor i would like to ask someone with an A2003 device who has working sensors and is running OOS 3.02 or CM13 to perform the following actions and share the file with me:
(root (adb and apps) needed)
Code:
adb shell
su
su
cd /sdcard
dd if=/dev/block/bootdevice/by-name/persist persist.dd.img
exit
exit
And share the file "persist.dd.img" with me. It's on your sdcard.
Thanks very much in advance!
Click to expand...
Click to collapse
I uploaded it to AFH a while back - it's the stock persist.img from the OnePlus 2.2.0 Qualcomm Recovery Package. AFAIK, it's not been updated since then.
persist.img

Spannaa said:
I uploaded it to AFH a while back - it's the stock persist.img from the OnePlus 2.2.0 Qualcomm Recovery Package. AFAIK, it's not been updated since then.
persist.img
Click to expand...
Click to collapse
Hi,
Yeah, google found it for me. But sadly, it didn't work for me.
I've tryed installing it
- trough fastboot (fastboot flash persist persist.img) and also
- dd'ing it and also
- creating a flashable zip package_extract_file("persist.img", "/dev/block/bootdevice/by-name/persist");
but none of it worked.. so i was kinda hoping for a newer version.

btw..
Code:
mount | grep persist
shows that the persist partition is mounted RW.
if someone could do the following:
Code:
adb shell
su
su
cd /sdcard
mkdir persist
cd persist
rsync -av /persist .
exit
exit
then zip the content of the folder persist on your sdcard.. would like to try that too.

_HugoBoss_ said:
btw..
Code:
mount | grep persist
shows that the persist partition is mounted RW.
if someone could do the following:
Code:
adb shell
su
su
cd /sdcard
mkdir persist
cd persist
rsync -av /persist .
exit
exit
then zip the content of the folder persist on your sdcard.. would like to try that too.
Click to expand...
Click to collapse
Code:
/system/bin/sh: rsync: not found

Spannaa said:
Code:
/system/bin/sh: rsync: not found
Click to expand...
Click to collapse
instead of
Code:
rsync -av /persist .
type
Code:
cp -r /persist .
Thanks

_HugoBoss_ said:
instead of
Code:
rsync -av /persist .
type
Code:
cp -r /persist .
Thanks
Click to expand...
Click to collapse
Code:
cp: No /persist: Permission denied

Spannaa said:
Code:
cp: No /persist: Permission denied
Click to expand...
Click to collapse
Are you root?
su
su

_HugoBoss_ said:
Are you root?
su
su
Click to expand...
Click to collapse
Yes
Code:
C:\Users\spannaa\Desktop>adb shell
[email protected]:/ $ su
1|[email protected]:/ $ su
1|[email protected]:/ $ cd /sdcard
[email protected]:/sdcard $ mkdir persist
[email protected]:/sdcard $ cd persist
[email protected]:/sdcard/persist $ cp -r /persist .
cp: No /persist: Permission denied
1|[email protected]:/sdcard/persist $

Spannaa said:
Yes
Code:
C:\Users\spannaa\Desktop>adb shell
[email protected]:/ $ su
1|[email protected]:/ $ su
1|[email protected]:/ $ cd /sdcard
[email protected]:/sdcard $ mkdir persist
[email protected]:/sdcard $ cd persist
[email protected]:/sdcard/persist $ cp -r /persist .
cp: No /persist: Permission denied
1|[email protected]:/sdcard/persist $
Click to expand...
Click to collapse
use "whoami" to check if you're really root..
Code:
su
[email protected]:/ # whoami
root

Spannaa said:
Yes
C:\Users\spannaa\Desktop>adb shell
[email protected]:/ $ su
1|[email protected]:/ $ su
1|[email protected]:/ $ cd /sdcard
[email protected]:/sdcard $ mkdir persist
[email protected]:/sdcard $ cd persist
[email protected]:/sdcard/persist $ cp -r /persist .
cp: No /persist: Permission denied
1|[email protected]:/sdcard/persist $
Click to expand...
Click to collapse
You don't have root access dude, the " 1| " means that an error occurred. Furthermore, check your prompt, still " $ " instead of " # " .

Got there in the end...
Code:
C:\Users\spannaa\Desktop>adb shell
[email protected]:/ $ su
[email protected]:/ # su
[email protected]:/ # cd /sdcard
[email protected]:/sdcard # mkdir persist
[email protected]:/sdcard # cd persist
[email protected]:/sdcard/persist # cp -r /persist .
cp: product_calib_ref1.dat: Function not implemented
cp: product_calib_ref2.dat: Function not implemented
cp: product_calib_ref3.dat: Function not implemented
cp: unit_calib_ref1.dat: Function not implemented
cp: unit_calib_ref2.dat: Function not implemented
cp: unit_calib_ref3.dat: Function not implemented
cp: mixer_paths.xml: Function not implemented
cp: sw_calib.dat: Function not implemented
1|[email protected]:/sdcard/persist #
Let me know when you've grabbed the attached zip and I'll delete it

Spannaa said:
Got there in the end...
Code:
C:\Users\spannaa\Desktop>adb shell
[email protected]:/ $ su
[email protected]:/ # su
[email protected]:/ # cd /sdcard
[email protected]:/sdcard # mkdir persist
[email protected]:/sdcard # cd persist
[email protected]:/sdcard/persist # cp -r /persist .
cp: product_calib_ref1.dat: Function not implemented
cp: product_calib_ref2.dat: Function not implemented
cp: product_calib_ref3.dat: Function not implemented
cp: unit_calib_ref1.dat: Function not implemented
cp: unit_calib_ref2.dat: Function not implemented
cp: unit_calib_ref3.dat: Function not implemented
cp: mixer_paths.xml: Function not implemented
cp: sw_calib.dat: Function not implemented
1|[email protected]:/sdcard/persist #
Let me know when you've grabbed the attached zip and I'll delete it
Click to expand...
Click to collapse
Yeah, downloaded it.. thanks!
Gonna play with it. Thanks!!

Spannaa said:
Got there in the end...
Code:
C:\Users\spannaa\Desktop>adb shell
[email protected]:/ $ su
[email protected]:/ # su
[email protected]:/ # cd /sdcard
[email protected]:/sdcard # mkdir persist
[email protected]:/sdcard # cd persist
[email protected]:/sdcard/persist # cp -r /persist .
cp: product_calib_ref1.dat: Function not implemented
cp: product_calib_ref2.dat: Function not implemented
cp: product_calib_ref3.dat: Function not implemented
cp: unit_calib_ref1.dat: Function not implemented
cp: unit_calib_ref2.dat: Function not implemented
cp: unit_calib_ref3.dat: Function not implemented
cp: mixer_paths.xml: Function not implemented
cp: sw_calib.dat: Function not implemented
1|[email protected]:/sdcard/persist #
Let me know when you've grabbed the attached zip and I'll delete it
Click to expand...
Click to collapse
At least it seems to contain more data, but i can't seem to get it fully working.
Could you perhaps do the following from TWRP:
advanced -> terminal
then type
Code:
cd /sdcard
dd if=/dev/block/bootdevice/by-name/persist of=persist.dd.img
exit
Then from android, grab the persist.dd.img and share it with me?

_HugoBoss_ said:
At least it seems to contain more data, but i can't seem to get it fully working.
Could you perhaps do the following from TWRP:
advanced -> terminal
then type
Code:
cd /sdcard
dd if=/dev/block/bootdevice/by-name/persist of=persist.dd.img
exit
Then from android, grab the persist.dd.img and share it with me?
Click to expand...
Click to collapse
Done.

Spannaa said:
Done.
Again, let me know when you've downloaded it.
Click to expand...
Click to collapse
Thanks A LOT.
SENSORS WORK...
but hold your horses.. Couple of things i find right away..
First boot: it doesn't recognize SIM cards anymore.. Second boot, they are recognized.
Then: when i switch to MTP (file transfer), phone reboots.
So have to see whether it's all stable or not.
Delete the attachment for now.. i'll work on it a couple of days and let you know.
Again, thanks a lot!!

Proof:

Ok, at this point i'm not sure what is related and what is not anymore.
One thing i know for sure: simply copying the persist partition from one phone to another IS working, however the partitions holds some device- (like mac addresses) and maybe even some user-specific information. So it would not be right to start sharing that in the wild.
But while experimenting with the data, i found myself in a pretty f*cked up situation where there was no booting OS anymore and the Oneplus told me the bootloader was unlocked but refused to flash files trough fastboot anymore. Basically a dead phone.
Thank god i created a nandroid (full TWRP) backup and copied it to my laptop.
Long story short: i needed to perform a full repair of my phone and started looking for brick-guides.
The following worked for me AND magically repaired my persist partition too.
Steps to take:
- perform a full TWRP backup of your phone and copy it to your computer (don't keep it ON the phone!)
- also backup everything on your internal memory (sdcard) that is worth keeping. This process will also wipe your internal memory.
- Download the files from this guide. I've used method 3. The others may work. 3 worked for me.
- shutdown your phone
- press volume up and then connect the usb cable. Only volume up!
- the phone won't really power on, but your computer will detect a device. Use the driver you downloaded from the page above.
- When the driver is installed, start the MSM8994DownloadTool.exe as administrator (right click: run as administrator!)
- It's chinese or some language i can't uderstand. But just hit the start button. Some green text will show the progress.
- In the end, your phone will ask you if it's OK to wipe all user data. I did.
- And then it boots to Oxygen OS.
From this point on it's back to normal business
- flash custom recovery trough fastboot
- copy your TWRP backup back to the phone
- restore the backup
- Oh and don't forget: all your firmwares are OLD now. So in order to run CM13 or some other marshmellow rom, you also need to flash that "Switch_tOS3_H2OSMMv3.zip" like you did before!
- restore any other data to your internal memory (sdcard)
There ya go. Fully working system with sensors and all
Good luck!

So after you did the Qualcomm recovery does cpuz still show the sensors as uncalibrated like the screenshot in post 17. I have some issues with my screen rotation as randomly it was not switch to landscape. My cpuz shows gyroscope calibrated and uncalibrated, any way to calibrate gyroscope without that Qualcomm recovery? I had to go through that process in March.

Dude_Virus said:
So after you did the Qualcomm recovery does cpuz still show the sensors as uncalibrated like the screenshot in post 17. I have some issues with my screen rotation as randomly it was not switch to landscape. My cpuz shows gyroscope calibrated and uncalibrated, any way to calibrate gyroscope without that Qualcomm recovery? I had to go through that process in March.
Click to expand...
Click to collapse
It still says so yes. Even now, after more than a month.
However, everything still works fantastic. No issues whatshowever.

Problem When Unlock bootloader on Samsung Note 4 [SM-N910H] 10|[email protected] "tre3g" :/data/

Problem When Unlock bootloader on Samsung Note 4 [SM-N910H] 10|[email protected] "tre3g" :/data/
Hello,
i'm trying to unlock bootloader on my device SAMSUNG GALAXY NOTE 4 [SM-N910H] it's already rooted
but i have this error codes in the end ......
Code:
[-]this is for (some) Samsung devices onlly
[-] it WILL kill other devices. go back to google
10|[email protected] "tre3g" :/data/local/tmp #
-------------------------------------------------------------------------------------------------
the codes in the beginning ....
Code:
adb push samsung_unlock_n4-fix /data/local/tmp/
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n4-fix
chown root.root samsung_unlock_n4-fix
./samsung_unlock_n4-fix
so how to fix or if there is another way to unlock it or to install custom ROM without unlock bootloader maybe! ??
..... Thanks in Advance