Database Develop

[DEV] Filesystem Table

recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) '(null)' 0000 '(null)' 0
1 /efs ext4 /dev/block/mmcblk0p1 (null) '(null)' 0000 '(null)' 0
2 /recovery emmc /dev/block/mmcblk0p2 (null) '(null)' 0000 '(null)' 0
3 /boot emmc /dev/block/mmcblk0p3 (null) '(null)' 0000 '(null)' 0
4 /system ext4 /dev/block/mmcblk0p4 (null) '(null)' 0000 '(null)' 0
5 /cache ext4 /dev/block/mmcblk0p5 (null) '(null)' 0000 '(null)' 0
6 /data ext4 /dev/block/mmcblk0p8 (null) '(null)' 0000 '(null)' -16384
Thanks to Root we're now able to begin our work on ClockworkMod!
I'll be backing up all the partitions and then trying to get something set up.
Regards

How did you manage to get a nice list like that? I had check '/dev/block/' and guess my way through .

That's a little trick
After you've managed once to boot into recovery a nice little file under /cache/recovery called last_log appears

seraphimserapis said:
That's a little trick
After you've managed once to boot into recovery a nice little file under /cache/recovery called last_log appears
Click to expand...
Click to collapse
Nice find and thanks for the share .

Egan said:
Nice find and thanks for the share .
Click to expand...
Click to collapse
you're welcome

Maybe I'm ready the info wrong, but are you sure the file is thrustworthy? It also tells that the device is a P7510.
And that it fails to mount /system to p4
Sent from my GT-P7100 using XDA Premium App

That would be due to the recovery being ripped from that model.
Either way, the holy grail is buried in one of those undefined devices
EDIT: anyone looked at nvflash? You can get it to boot into apx mode by holding VOL-UP / VOL-DOWN when powered off. Too low-level?

the problem is currently only, that we can't get sdcard to mount because its a folder that gets created at boot time.

bcmobile said:
EDIT: anyone looked at nvflash?
Click to expand...
Click to collapse
I used it couple of times on my LG Optimus 2X and it is a life safer. You just cant brick your device when you have the proper APX file. IMO it is not too low-level, rather a great option for when you really mess things up.
How does one create such an APX file?
EDIT: APX file is really a ZIP with the nvflash.exe, some DLLs, images (*.img) and config files. You have to extract and run 'nvflash.exe'. Have a dig tonight and see if we can come up with a good nvflash restore image.
EDIT2: There is some BCT file in there which is compiled. Anyone know something about this type of file?
EDIT3: Asked Paul O'Brien on Twitter if he can point me in the right direction. He made the ZIP for the LG Optimus 2X.

Egan said:
EDIT3: Asked Paul O'Brien on Twitter if he can point me in the right direction. He made the ZIP for the LG Optimus 2X.
Click to expand...
Click to collapse
Excellent! Paul is also creating us a forum over at MoDaCo. I hope this means MCR action for the 10.1v!

bcmobile said:
Excellent! Paul is also creating us a forum over at MoDaCo. I hope this means MCR action for the 10.1v!
Click to expand...
Click to collapse
I've found out how the sdcard gets mounted.
There is a executable in /system/bin that gets used on device init.
Will have to figure out how to use it.

seraphimserapis said:
I've found out how the sdcard gets mounted.
There is a executable in /system/bin that gets used on device init.
Will have to figure out how to use it.
Click to expand...
Click to collapse
Isn't that the purpose of bin
Not that I could be of much help I guess but maybe if you told us which.. someone might have an answer...
Sent from my GT-I9000 using XDA Premium App

gjroeleveld said:
Isn't that the purpose of bin
Not that I could be of much help I guess but maybe if you told us which.. someone might have an answer...
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
/system/bin contains all the executables i need to find out how to include this special executable at recovery boot time.

Just thinking, but the fastboot thing could be a really nice feature..
If we partition part of the "SD -card " we could build a multiboot without too much trouble...
Sent from my GT-I9000 using XDA Premium App

seraphimserapis said:
/system/bin contains all the executables i need to find out how to include this special executable at recovery boot time.
Click to expand...
Click to collapse
You might need to use a recovery.zip and execute it from an updater script. Not sure why, but the old CM recovery used to boot to a cut-down menu with the option to "Flash recovery.zip from SD Card", which would then load full CM recovery.
Perhaps it was for the same reason?

I got a viewpad 10 also a tegra II .
I have rooted it an flashed a dump of 3 devicesmixed up together to boot hc on it.
Maybe it is a long shot but it might contain how root and cwm will work.
It hadto be flashed treu nvflash
If you need it i wil share.
Just trying to help
And if you dont need it or you think it is useless noproblem just trying to help.

bcmobile said:
Excellent! Paul is also creating us a forum over at MoDaCo. I hope this means MCR action for the 10.1v!
Click to expand...
Click to collapse
It appears Paul isnt very helpful in this case. I friendly asked him twice via Twitter, but neither got a reply (while he was heavily replying on others). I guess we have to find out some other way or any of you may have a direct link with Paul?

Egan said:
It appears Paul isnt very helpful in this case. I friendly asked him twice via Twitter, but neither got a reply (while he was heavily replying on others). I guess we have to find out some other way or any of you may have a direct link with Paul?
Click to expand...
Click to collapse
I think Paul has lots of other work and devices to support Give him a rest.

seraphimserapis said:
I think Paul has lots of other work and devices to support Give him a rest.
Click to expand...
Click to collapse
I usually give replies like you do now over at Modaco . Maybe I just want to get it going. Still a simple tweet like "sorry can not help you" or "getting back on that" would be nice.
EDIT: I found some more info on how to retrieve the BCT file from the device itself. I'll try things later this week and hopefully have some progress to show by the weekend.

Some more partitions listed in ueventd.p3.rc in the IO tab recovery ramdisk
Code:
# misc partition
/dev/block/mmcblk0p6 0660 system system
# modem partition
/dev/block/mmcblk0p7 0660 system radio

[Q] Superoneclick failure on Hero

Whe I attempt to root using superoneclick I first get a msg "auto version check failed". I verified my Sprint Hero is running 2.1. I click yes to the question am I using 2.0 or higher.
It continues on until I get "Getting mount path...
rootfs / rootfs ro 0 0
FAILED".
Now what?

Pm.sent
#Root/Hack-Mod_Always*

Nevermind. I was having the same issue, but I use z4root and am no longer having an issue

[Q] has anyone rooted the official honeycomb 3.2 with SuperOneClick?

hello,
i have read on the forums about rooting the stock honeycomb through clockwork mod and fastboot and what not but i have tried everything know to man trying to get that to work, but no dice.
has anyone rooted successfully using SuperOneClick on a dell streak 7 with android 3.2 honeycomb official OTA update?
thanks for the help.

cboulais61 said:
hello,
i have read on the forums about rooting the stock honeycomb through clockwork mod and fastboot and what not but i have tried everything know to man trying to get that to work, but no dice.
has anyone rooted successfully using SuperOneClick on a dell streak 7 with android 3.2 honeycomb official OTA update?
thanks for the help.
Click to expand...
Click to collapse
Yes, with 2.2.2. You have to remember to take out the SD card before you do it though.
Regards,
Hans

Just tried this with the latest 2.3.1 on my Dell Streak 7 4G that came with 3.2 on it. SuperOneClick gets to:
Rooting Device Step #7 Wait for Device - and then hangs
In the output windows I see the following:
Code:
export TEMPRANDOM=92181 export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output mount: permission denied (are you root?) END:92181export PS1="" /data/local/tmp/busybox mount > /data/local/tmp/output 2>&1 export TEMPRANDOM=49649 export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output rootfs on / type rootfs (ro,relatime) tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755) devpts on /dev/pts type devpts (rw,relatime,mode=600) proc on /proc type proc (rw,relatime) sysfs on /sys type sysfs (rw,relatime) none on /acct type cgroup (rw,relatime,cpuacct) tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000) tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000) none on /dev/cpuctl type cgroup (rw,relatime,cpu) /dev/APP on /system type ext4 (ro,relatime,barrier=1,data=ordered) /dev/UDA on /data type ext3 (rw,nosuid,nodev,noatime,barrier=0,data=writeback) /dev/CAC on /cache type ext3 (rw,nosuid,nodev,noatime,barrier=0,data=writeback) /dev/SDC on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro) END:49649export PS1="" mount -o rw,remount /dev/APP /system > /data/local/tmp/output 2>&1 export TEMPRANDOM=93079 export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output mount: Operation not permitted END:93079
Any ideas?

All known exploits were patched in Android 3.0.
There have been no known exploits that work on anything newer then that since it was released.

TheManii said:
All known exploits were patched in Android 3.0.
There have been no known exploits that work on anything newer then that since it was released.
Click to expand...
Click to collapse
So back to trying to get drivers for my Streak 7 installed under Win 64 so I can fastboot is pretty much it then, eh?

Looks Confused said:
Yes, with 2.2.2. You have to remember to take out the SD card before you do it though.
Regards,
Hans
Click to expand...
Click to collapse
Fail. He asked for 3.2.
I think you should use the fastboot way

exebreez said:
Fail. He asked for 3.2.
I think you should use the fastboot way
Click to expand...
Click to collapse
Ha. You should be nicer (kidding). I meant SuperOneClick v2.2.2. Which is what I've used to root HC V3.2 a couple of times now. I've done this so I can use one of the application managers to remove some of the factory installed dross in the stock firmware (which I think requires root access).
I'm a bit puzzled about one thing: As mentioned in another post in this thread, there are no known exploits for HC. So, I don't understand how this could be working, unless I'm not really rooting my tablet, or maybe its because the boot loader isn't locked in the first place?
If anyone happens to understand what's going on, I'd be happy to listen.
Regards,
Hans

Looks Confused said:
Ha. You should be nicer (kidding). I meant SuperOneClick v2.2.2. Which is what I've used to root HC V3.2 a couple of times now. I've done this so I can use one of the application managers to remove some of the factory installed dross in the stock firmware (which I think requires root access).
I'm a bit puzzled about one thing: As mentioned in another post in this thread, there are no known exploits for HC. So, I don't understand how this could be working, unless I'm not really rooting my tablet, or maybe its because the boot loader isn't locked in the first place?
If anyone happens to understand what's going on, I'd be happy to listen.
Regards,
Hans
Click to expand...
Click to collapse
So what you are saying is super one click 2.2.2 root DS7 hc 3.2.. I tryed super one click 2.3. Whatever... And it didn't work...
Sent from my Desire HD using XDA App

s14evil said:
So what you are saying is super one click 2.2.2 root DS7 hc 3.2.. I tryed super one click 2.3. Whatever... And it didn't work...
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
TL;DR: Yes.
I went and double checked. I'm running HC 3.2 on my Streak 7. The latest version of SuperOneClick I have is 2.2, according to the file I downloaded (dunno where I got 2.2.2 from, probably some mental issue).
I enabled USB debugging, took out my SD card, plugged my tablet in, and clicked the "Root" button.
It said my tablet was rooted. I installed "Root Uninstaller" and Superuser asked me if I wanted to grant it root access. I used this to remove Evernote and Kongregate. So, I think it worked.
Regards,
Hans

Looks Confused said:
Ha. You should be nicer (kidding). I meant SuperOneClick v2.2.2. Which is what I've used to root HC V3.2 a couple of times now. I've done this so I can use one of the application managers to remove some of the factory installed dross in the stock firmware (which I think requires root access).
Hans
Click to expand...
Click to collapse
Sorry dude, i didnt read that carefully.

Looks Confused said:
TL;DR: Yes.
I went and double checked. I'm running HC 3.2 on my Streak 7. The latest version of SuperOneClick I have is 2.2, according to the file I downloaded (dunno where I got 2.2.2 from, probably some mental issue).
I enabled USB debugging, took out my SD card, plugged my tablet in, and clicked the "Root" button.
It said my tablet was rooted. I installed "Root Uninstaller" and Superuser asked me if I wanted to grant it root access. I used this to remove Evernote and Kongregate. So, I think it worked.
Regards,
Hans
Click to expand...
Click to collapse
Thanks mate
Sent from my Dell Streak 7 using XDA App

What rom did you have installed? It could have already been rooted.
Also, there's always the possibility that there is a new exploit out that SoC uses that isnt patched. If there is then it will work for the time being. I dont actually read SoCs changelogs.
It COULD get fixed in the next stock rom (dell is still making more updates, they're simply not releasing them as pkgs) though. IF they ever actually decide to release another update OTA

I tried it and it failed so I went about rooting the long way. Took a while but I got it figured out. I would recommend doing the same.

TheManii said:
What rom did you have installed? It could have already been rooted.
Also, there's always the possibility that there is a new exploit out that SoC uses that isnt patched. If there is then it will work for the time being. I dont actually read SoCs changelogs.
It COULD get fixed in the next stock rom (dell is still making more updates, they're simply not releasing them as pkgs) though. IF they ever actually decide to release another update OTA
Click to expand...
Click to collapse
One of the stock HC roms from Dell. The OEM version is: GLUNB1A350630.
I had rooted it before I did the upgrade (with the factory shipped firmware), but after upgrading, Superuser no longer worked. I did a full reset to stock 3.2 (via the recovery menu VOL+ or - (I forget which) while powering on), then did the SuperOneClick rooting procedure.
Regards,
Hans

Instead of trying to use Super one click, Why not just follow this guide. Should have no issues rooting using the following steps. Yes its more than just click and wait, but its not very difficult if you follow the steps to the letter.
http://forum.xda-developers.com/showthread.php?t=1411193
[Guide] Absolute Newbie's Guide to Rooting a Streak 7 that has Stock Honeycomb
Hope this helps someone
Noticed there was not a link to Superuser7.zip on the newbie guide to rooting.. so I'm attaching a link.
http://www.tablet-cables.com/streak/tools/root/Superuser7.zip (Cap in file name required or it won't be found.)

Superuser7.zip

[Q] Imei issue (Still i need your help!)

I'm a Galaxy Note user for 2 month... I read a lot of topics about imei problem however non of them help me... Therefore, I want to open a new topic for my issue... Here is what happens...
First of all, I use LA6 (also before i had imei problem), and Speedmod 1.5 kernel...
Almost everyday im facing with imei problem which is empty when i make *#06#. And the phone never asks for my sim pin number.
1- Sometimes when i connect the usb cable the imei is suddenly gone and there is "No service" at all.
2- Sometimes when i restart the phone, the phone never asks the SIM Pin number, and when i check the imei number it is shown as empty...
Here is what i tried before to solve my problem...
-I reinstall rom many times (stock, custom etc almost every rom)
-I tried different kernel
-I tried EFS recovery which i had a backup for this
-I tried Nitrality application for EFS recover (By the way, in my opinion the problem is not related with EFS, because the folder still is there... Even if it changes the imei may shown as 0049 etc. but in my case the imei always become empty.)
-I Totally formatted SD card, And wiped data, cache, kernel cleaning even HARD RESETTED, which is a clean phone like a new one...
I tried this steps, but the problem is always continues... Sometimes the phone asks for my pin and i feel luck for that day but i always scared even to charge the phone because when i connect the USB cable (doesnt matter from pc or electricity) the phone sometimes lost all signals suddenly and become "No service" and imei is gone... However sometimes the problem is not seen...
Even totally clear phone (STOCK, HARD RESETTED, WIPED) has this problem sometimes...
And when i lucky,Always the phone asks my SIM pin number 30 sec later when the phone is on, Not asks instantly ( when widgets are fully shown)
I want you to help me... Im bored from my phone because of this problem...
Thanks...
UPDATE:
I think the phone sometimes do not read the EFS folder... how can i fix this i dont know...

Please help me...

Actually you did everything possible i know to fix it... Try another SIM? Send it back to your seller and get a new one...?! ^^

two_handed said:
Actually you did everything possible i know to fix it... Try another SIM? Send it back to your seller and get a new one...?! ^^
Click to expand...
Click to collapse
now im not in my country so i can not send to get new one... Also i have no guarantee... Is there another solution?

Dampen a small cloth towel and rub your SIM's contacts with alcohol, see if that works.

mcmaddcatt said:
Dampen a small cloth towel and rub your SIM's contacts with alcohol, see if that works.
Click to expand...
Click to collapse
The problem is not about sim actually... When there is no imei, the phone doesnt ask PIN for my sim... Automatically it is seen as NO SERVICE
I dont know what my really problem is but i think the phone sometime does not read the EFS folder... For this issue there is a tool in the market as
"GSII Repair"
"If your sim card is not detected, no signal or your efs folder is blocked on read_only, this apk help you."
But it for SGSII...
I am bored

Did you fix permissions via CWM yet? maybe it fixes your problem. also show me the output of "mount | grep efs" in a terminal emulator.

two_handed said:
Did you fix permissions via CWM yet? maybe it fixes your problem. also show me the output of "mount | grep efs" in a terminal emulator.
Click to expand...
Click to collapse
I dont know how i can do it... can you write it detailly please or is there link for this?

Fix Permissions:
Boot into CWM Recovery (shutdown phone, press volume up + home + power button)
somewhere under the advanced options you will find the option fix permissions. do it.
Mount:
install some terminal emulator via market (e.g better terminal emulator) and type:
mount | grep efs
and paste me the output

two_handed said:
Fix Permissions:
Boot into CWM Recovery (shutdown phone, press volume up + home + power button)
somewhere under the advanced options you will find the option fix permissions. do it.
Mount:
install some terminal emulator via market (e.g better terminal emulator) and type:
mount | grep efs
and paste me the output
Click to expand...
Click to collapse
First of all thank you... I fix the permissions... The phone asks me for PIN after 10 second when all widgets are placed. I downloaded a terminal emulator but i typed exactly the "mount | grep efs" and click enter the resul is "grep: not found"

The phone asks me for PIN after 10 second when all widgets are placed.
Click to expand...
Click to collapse
is it a progress? reboot the phone a few times to reproduce it.
leave "| grep efs" out then, seems like you havent grep installed. just post output of "mount"

two_handed said:
is it a progress? reboot the phone a few times to reproduce it.
leave "| grep efs" out then, seems like you havent grep installed. just post output of "mount"
Click to expand...
Click to collapse
i just write mount and result is;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.nd page (just a little more of 1st page)

Hm. just an educated guess, but i think your problem is caused by your mount table - but i am NOT SURE about it.
here is my mount, the the /efs line differs from yours.
~ # mount
rootfs on / type rootfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=111)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/usb type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /app-cache type tmpfs (rw,relatime,size=8192k)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p9 on /system type ext4 (rw,relatime,barrier=0,data=writeback,noauto_da_al loc)
/dev/block/mmcblk0p7 on /cache type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=0,data =writeback,noauto_da_alloc)
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
nil on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/mmcblk0p10 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=0,data =writeback,noauto_da_alloc)
/dev/block/vold/179:11 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime ,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_uti me=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard)
/dev/block/vold/179:17 on /mnt/sdcard/external_sd type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime ,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_uti me=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:17 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime ,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_uti me=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/external_sd/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)

Im not an expert so... Is there a solution for that?

it was just a wild guess. maybe an more experienced user can say sth. about it. i am definately not going to tellyou to mess with your void.fstab settings - some of them are even hard coded i guess.
but you should do a full wipe again as it should reformat your device. manually clear your storage, clear data/cache/dalvik cache, flash a rom of your choice twice and try again. if it's not ok then, try stock rom once again. if its still not working, have your device replaced.

two_handed said:
it was just a wild guess. maybe an more experienced user can say sth. about it. i am definately not going to tellyou to mess with your void.fstab settings - some of them are even hard coded i guess.
but you should do a full wipe again as it should reformat your device. manually clear your storage, clear data/cache/dalvik cache, flash a rom of your choice twice and try again. if it's not ok then, try stock rom once again. if its still not working, have your device replaced.
Click to expand...
Click to collapse
Now im not in my country for couple of months... my device has no guarantee either...Can Any samsung service fix this issue for a price?

No other help ?

two_handed said:
.......
but you should do a full wipe again as it should reformat your device. manually clear your storage, clear data/cache/dalvik cache, flash a rom of your choice twice and try again. if it's not ok then, try stock rom once again. if its still not working, have your device replaced.
Click to expand...
Click to collapse
No insult, but have you already done the obove mentioned? as there are not many people with your problem, i guess it's some software failure and should therefore be fixable by a clean and full wipe.
otherwise, of course you can have your device fixed by samsung. No idea what it'll cost.

two_handed said:
No insult, but have you already done the obove mentioned? as there are not many people with your problem, i guess it's some software failure and should therefore be fixable by a clean and full wipe.
otherwise, of course you can have your device fixed by samsung. No idea what it'll cost.
Click to expand...
Click to collapse
I did it but i did not flash twice after the wipe... %30 asks my PIN CODE and SHOW IMEI after reboot my phone... Phone still works now... But it is boring bug... I tried almost everything... My last hope is the samsung care...

did you try another sim yet? what do you mean with "SHOW IMEI after reboot..."? do you enter *#06# and IMEI appears?
try booting without SIM several times and check if you can see IMEI with *#06# typing in keypad.

[HOWTO] Root the Galaxy Tab 2 7" without flashing the bootloader

Hi,
Here's a method based on a security hole to gain root on the Galaxy Tab 2 7" without heavy flashing by Odin. I've successfuly tested this method on my GT-P3110 running stock Android 4.0.3 on kernel 3.0.8-379370, version IML74K.P3110XXALD4.
The original post by Miloj :good: can be viewed here :
http://forum.xda-developers.com/showthread.php?t=1704209
I've only "translated" the trick from TF300T to our Galaxy Tab. I guess it should work for other devices too... To make short, the goal here is to create a symbolic link from the famous /data/local/tmp to the block device on which /system is mounted. The mount command runned in an ADB shell can give the required information :
$ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache ext4 rw,nosuid,nodev,noatime,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 rw,relatime,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
After identifying the block device, refer to the well-explained Miloj post and consider :
Code:
[COLOR="Red"]FOR SAMSUNG GALAXY TAB 2 7" ONLY:[/COLOR]
Code:
$ ln -s /dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS tmp
$ exit
Hope it will help !

after typing what you said all i get is " link failed Read-only file system"
tried on galaxy tab 2 p3100 (stock)

ze0 said:
after typing what you said all i get is " link failed Read-only file system"
tried on galaxy tab 2 p3100 (stock)
Click to expand...
Click to collapse
Well, you must follow Miloj's tutorial http://forum.xda-developers.com/showthread.php?t=1704209 from the start : push the binaries downloaded from http://db.tt/FBUNeVmo to /data/local, run an ADB shell and change directory to /data/local, move tmp to tmp.back then create the symbolic link to the block device with the ln command given in my post for the Galaxy Tab and type (or copy / paste) all the following commands (reboot, shell, clean-up, dirty work, ...) given by Miloj.
I know it's a little rough, I'll try to find some time to script all the stuff or adapt the one click tool quoted in Miloj's post.
Good luck !

yes it worked .awesome man thank you you rock ,now i have root in stock with binary counter value 0

The automated tool
Sparkym3 provides an automated tool for rooting the Transformer TF300T with Miloj method :
http://forum.xda-developers.com/showthread.php?t=1706588
I've modded the tool for the Samsung Galaxy Tab 2 7" (see attached file). Check the link above for the instructions and run the modded version called RootDebugfs_n95.bat instead of the original RootDebugfs.bat.
The original tool includes the Asus USB drivers... I failed to join the Samsung ones to the attached zip, maybe due to an excessive weight (near 19 Mo).
Happy rooting !

Gee, it's already been impossible with ICS4.0.4
Wish I hadn't upraded...

Thanks Nesquick95, I've updated my topic with your informations.

hayatama said:
Gee, it's already been impossible with ICS4.0.4
Wish I hadn't upraded...
Click to expand...
Click to collapse
If the security hole is patched in the 4.0.4 release, you'll get an "access denied" error while executing the "debugfs -w /data/local/tmp" command.
If it's the case, we must look for another rooting trick
Can you please tell which kind of error you get and if it's not the "access denied" one, post the result of a "mount" of your tablet (adb shell mount) ?

First,great job,thank you for your work,now we don't need to worry about warranity.Second,maybe you can help us again,can you please tell us how do we keep root,when upgrading 4.0.4? I know that Transformer tabs have some kind of app,named Root Keeper ,if you flash OTA update,and want to keep root.Maybe we can try something similar for our tab ,or using Mobile Odin maybe?
Thanks again!
Best Regards!

Nesquick95 said:
If the security hole is patched in the 4.0.4 release, you'll get an "access denied" error while executing the "debugfs -w /data/local/tmp" command.
If it's the case, we must look for another rooting trick
Can you please tell which kind of error you get and if it's not the "access denied" one, post the result of a "mount" of your tablet (adb shell mount) ?
Click to expand...
Click to collapse
thanx. if my memory serves, it was an error you mentioned, but i will check it soon.
btw, i've got another updates...
Sent from my GT-P3113 using xda app-developers app

hayatama said:
Gee, it's already been impossible with ICS4.0.4
Wish I hadn't upraded...
Click to expand...
Click to collapse
would you like to test this one?
I'm tested in my P3100 with 4.0.4 and worked

Fz.hary said:
would you like to test this one?
I'm tested in my P3100 with 4.0.4 and worked
Click to expand...
Click to collapse
Thanx, i know it'd work, but i want to root "without" flashing rom.
Sent from my SC-02C using xda app-developers app

Yep,the whole point of this root method it's not to flash unofficial kernel using Odin,because it triggers the counter ,and it will void your warranity.If you root without Odin,than you can use Mobile Odin to flash roms,and you'll have the counter 0 ,so you'll keep your warranity. intact.
Cheers

Nesquick95 said:
Sparkym3 provides an automated tool for rooting the Transformer TF300T with Miloj method :
http://forum.xda-developers.com/showthread.php?t=1706588
I've modded the tool for the Samsung Galaxy Tab 2 7" (see attached file). Check the link above for the instructions and run the modded version called RootDebugfs_n95.bat instead of the original RootDebugfs.bat.
The original tool includes the Asus USB drivers... I failed to join the Samsung ones to the attached zip, maybe due to an excessive weight (near 19 Mo).
Happy rooting !
Click to expand...
Click to collapse
So if i use this it will root amid leave tab 2 at 0 on odin
Sent from my Tab 2

photon4glover said:
So if i use this it will root amid leave tab 2 at 0 on odin
Sent from my Tab 2
Click to expand...
Click to collapse
Yes, because this root method exploits a security hole of the tab's software integration and thus doesn't need Odin.
But I'd like to say that this kind of rooting method isn't better or worst than recovery flash...
Recovery flash causes warranty to be broken but is nearly granted to work.
Tricky methods keep warranty alive but have short lifetimes, like the one discussed here that seems to work only on 4.0.3, since providers like Samsung can't leave security holes on their systems and apply patches so the work (find a new trick or write an OTA-rootkeeper) must be done each time an update is released.

Man so no method like this forv4.04
Sent from my Tab 2

photon4glover said:
Man so no method like this forv4.04
Sent from my Tab 2
Click to expand...
Click to collapse
Haven't got 4.0.4 myself so it's hard for me to say...
An unsuccessful try on 4.0.4 is reported here and hole patching by Samsung is strongly suspected.
Well, it's always the same never-ending rooting story : flashing & losing warranty or waiting for a rooting exploit that may never be found & keeping warranty alive.
May I ask how 4.0.4 comes to our tabs ? Is it regular OTA or alternative ROM flashing ? I'm on stock 4.0.3, rooted but not unlocked and have no signs of an OTA update coming.

4.0.4 is available from kies only [p3100] No OTA update

Nesquick95 said:
Haven't got 4.0.4 myself so it's hard for me to say...
An unsuccessful try on 4.0.4 is reported here and hole patching by Samsung is strongly suspected.
Well, it's always the same never-ending rooting story : flashing & losing warranty or waiting for a rooting exploit that may never be found & keeping warranty alive.
May I ask how 4.0.4 comes to our tabs ? Is it regular OTA or alternative ROM flashing ? I'm on stock 4.0.3, rooted but not unlocked and have no signs of an OTA update coming.
Click to expand...
Click to collapse
Since your alrdy rooted u can flash a recovery via mobile Odin or desktop Odin of your not worried about flash counter. If u guys have a link for your 4.0.4 update ill root and de odex for ya. Or let me know what region the 4.0.4 update is for ill try and find it on samsung firm
Sent from my ADR6425LVW using xda premium

Nesquick95 said:
Haven't got 4.0.4 myself so it's hard for me to say...
An unsuccessful try on 4.0.4 is reported here and hole patching by Samsung is strongly suspected.
Well, it's always the same never-ending rooting story : flashing & losing warranty or waiting for a rooting exploit that may never be found & keeping warranty alive.
May I ask how 4.0.4 comes to our tabs ? Is it regular OTA or alternative ROM flashing ? I'm on stock 4.0.3, rooted but not unlocked and have no signs of an OTA update coming.
Click to expand...
Click to collapse
Mine came OTA, and additional OTA was available (P3113)
Sent from my SC-02C using xda app-developers app