yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] Kangal:
No. The gpu in the Tegra 3 is slightly superior to the quadcore Mali-400, not a huge stretch.

But each "generation" nVidia have been the the inferior products, especially in the graphics components (irony?). However, they offset this because they're first to market.

That's exactly right.

Its about the entire offering software AND hardware optimization, not one without the other.

I rather have a 1GB RAM and Tegra2 rather than 2GB RAM and Exynos 4410... just as long as the software is optimized (for instance, lower-level API support using Qt and Mainline Linux.... compared to higher-order virtual engine running on a inferior kernel).
[Galaxy Note GT-N7000 General] Darfus:
I think your arguments are all invalid. Especially on this forum.

Just install chainfire 3d pro and you can run all those THD games flawlessly and in real world performance mali blows tegra out of the sky.
[Galaxy Note GT-N7000 General] rcarbal:
:mad: tegra gets no love nowadays
[Galaxy Note GT-N7000 General] Rayan:
Even though Chainfire allow us to run Tegra games, it does not do a good job emulating the shader effects present in the actual games. Games look flat and dull compared to the original.

Cheers!
[Galaxy Note GT-N7000 General] blue13x:
Plus it requires rooting. I prefer the support right out of the box.
[Galaxy Note GT-N7000 General] lagittaja:
To original question: Hell no!
[Galaxy Note GT-N7000 General] :
There's nothing wrong with their hardware. It's their software that's a laggy hell of broken update promises.
[Galaxy Note GT-N7000 General] Akiainavas:
I'm no expert, but there are lots of reviews and articles stating that Tegra is not as great as many would think. I guess Samsung should stay with Exynos - they perform great.

As far as games are concerned... you know that THD games actually run smoothly on Exynos/Mali combo with Chainfire 3D plugin ? They might lack some rendering effects etc. but are playable, look good, and get more than decent fps.
[Galaxy Note GT-N7000 General] zstef:
OT: No, hell no!
[Motorola Droid 4] Rick#2:
** Update ****************

************************

Posted a .zip with scripts for both Windows and *nix users to automate the process.

Linux:

-----

Unzip the contents of the attached ICS404root.zip anywhere on your computer and run the script aptly named "runme_root_script.sh". It should take care of the rest. Make sure you have USB Debugging enabled and you put the phone in Camera mode, not mass storage device.

Windows:

---------

Unzip ICS404root.zip wherever you want and then run "rootscript.bat". Make sure you have USB Debugging enabled and you put the phone in Camera mode, not mass storage device.

*************************

*************************

Credit to miloj for finding this technique on the Transformer. (See the thread noted below and be sure to thank him!) I modified it to work on our devices.

http://xdaforums.com/showthread.php?t=1704209

I'll put together a script to automate this process shortly, but if you're antsy like me, here's the lowdown:

1. Download the following files:

su: http://db.tt/ShPzea6I

debugfs: http://db.tt/bGFh43LZ

2. Save the two files downloaded above on /sdcard. (ie: mount your sdcard in windows and copy them over, or "adb push" them to /sdcard).

**Make sure you have your phone on Mount Camera mode, not as a mass storage device; otherwise, you won't be able to access your /sdcard directory via adb. **

3. In a linux terminal/Windows command prompt:

adb shell

shell@cdma_maserati:/ $ cd /sdcard
shell@cdma_maserati:/ $ cp su /data/local/12m/
shell@cdma_maserati:/ $ cp debugfs /data/local/12m/
shell@cdma_maserati:/ $ cd /data/local/12m
shell@cdma_maserati:/ $ chmod 755 debugfs
shell@cdma_maserati:/ $ chmod 755 su
shell@cdma_maserati:/ $ mv batch batch.bak
shell@cdma_maserati:/ $ ln -s /dev/block/mmcblk1p20 batch
shell@cdma_maserati:/ $ exit

adb reboot

4. While you are waiting for the phone to reboot, type the following into your terminal/command window:

adb wait-for-device shell

5. Once you're back into the android shell:

shell@cdma_maserati:/ $ cd /data/local/12m
shell@cdma_maserati:/ $ rm batch
shell@cdma_maserati:/ $ mv batch.bak batch
shell@cdma_maserati:/ $ /data/local/12m/debugfs -w /dev/block/mmcblk1p20

(The following is entered at the "debugfs:" prompt)

debugfs: # cd xbin
debugfs: # write /data/local/12m/su su
debugfs: # set_inode_field su mode 0104755
debugfs: # set_inode_field su uid 0
debugfs: # set_inode_field su gid 0
debugfs: # quit

shell@cdma_maserati:/ $ cd /data/local/12m
shell@cdma_maserati:/ $ rm su
shell@cdma_maserati:/ $ rm debugfs
shell@cdma_maserati:/ $ exit

adb reboot

Done deal. Now you've got the "su" binary pushed to your /system partition and set with the proper permissions for execution. Download the Superuser app from the market and you're good to go. Make sure you update the su binary within the Superuser app as well to make sure you're up to date.
[Motorola Droid 4] danifunker:
Awesome! Were you able to upgrade to the latest leak and not lose root? Btw, what carrier are you on? I figured out how to get tethering fully functional on rogers but the process requires root...

Sent from my XT894 running ICS
[Motorola Droid 4] Rick#2:
You bet. I had to fastboot the leaked .208 update over top of the .206 update yesterday because I messed up my /system partition; I had used the OTA Rootkeeper to keep root permissions when upgrading from .219 but had foolishly disabled it right before I bungled everything up.

So to sum it up, this method didn't require anything to be done before updating to the .208 leak; since it has nothing to do with the technical details of the kernel itself, I'm fairly certain it should work for the .200 or .206 leaks as well. Root permissions were obtained from a completely stock system.

I'm in Canada with Bell but it doesn't matter because I imported the phone from the US; Verizon is the only carrier that has this phone. At any rate, this method is pretty universal, it is preying on a vulnerability present in the stock init.rc file and I bet it would work on other phones such as the RAZR as well.
[Motorola Droid 4] gdeeble:
So we can confirm this is 100% working with Fastbooting back and moving to 208? If so I will probably jump on this immediately.
[Motorola Droid 4] droidian1441:
I am trying to do this method but I cant adb to detect my phone. Im on the .208 leak. Can anybody help?
[Motorola Droid 4] Rick#2:
Have you enabled USB Debugging in the Settings->Developer Options menu?
[Motorola Droid 4] droidian1441:
Yep.
[Motorola Droid 4] Die Bruine:
Not able to reboot, trying manually...

debugfs: /data/local/12m/su: Permission denied
debugfs: su: File not found by ext2_lookup
debugfs: su: File not found by ext2_lookup
debugfs: su: File not found by ext2_lookup

Had to reboot manually twice. This is the only error message I received. Tried Superuser, but it stops.

I'm on .200 btw.
[Motorola Droid 4] Grizzy3:
I'm having the same issue. I'm on the 208 leak. I start command prompt in windows then type "adb shell" and I get the "device not found" message. I enabled usb debugging and my phone is connected as mass storage.
[Motorola Droid 4] gdeeble:
Likewise, Reboot requires su access, manual only. When I go and run the write command in debugfs permission denied. Any ideas what would cause this? Based on the code shown in the first post, SU had been already acquired(# vs $), which makes me wonder here.
[Motorola Droid 4] Rick#2:
Looks like you're doing something wrong with the debugfs command; you don't want to enter /data/local/12m/su at that prompt.

Running su from any partition other than /system will lead to a permissions error, so you don't want to bother trying to execute it from the /data/local/12m location.

(The following is entered at the "debugfs:" prompt, ie: after executing /data/local/12m/debugfs -w /dev/block/mmcblk1p20; see step 5.)

debugfs: # cd xbin
debugfs: # write /data/local/12m/su su
debugfs: # set_inode_field su mode 0104755
debugfs: # set_inode_field su uid 0
debugfs: # set_inode_field su gid 0
debugfs: # quit
[Motorola Droid 4] droidian1441:
Ive got the same situation over here. I can stick without root, just the fact that I would have it again would be just the single reason to do it. Lol.
[Motorola Droid 4] gdeeble:
debugfs 1.42 (29-Nov-2011)
debugfs: cd xbin
cd xbin
debugfs: write /data/local/12m/su su
write /data/local/12m/su su
/data/local/12m/su: Permission denied

Rick, that's what we're putting in. From the code you posted it shows that you had root access already. Do you have any other suggestions on this? Because that's the in and out I get.

---------- Post added at 04:57 AM ---------- Previous post was at 04:53 AM ----------

Problem resolved. Need to run the following code:

chmod 755 debugfs
chmod 755 su

Then continue with rooting.
[Motorola Droid 4] Rick#2:
Not sure where you're making this assumption from. I just wrote the "#" symbol in there to signal where to start entering commands... though I suppose you're correct in pointing out that the "#" shows up on a root prompt. A smarter choice probably would have been "$".

Trust me, I'm not an idiot. I wouldn't have gone through the hassle of writing up the guide in the first post if it didn't work. :P
[Motorola Droid 4] gdeeble:
Didn't mean it that way, just looked like it already had root, which was what confused me. But thanks again for this. :-D
[Motorola Droid 4] Die Bruine:
Tried it again. This time no errors and the phone rebooted. But now Superuser keeps on FC :o .

Reinstalled superuser, updated and busybox. Now rooted! Thnx.

BTW, you might wanna update the OP. Do not batch the commands under windows. I tried several times. I think there is something wrong with the timing. Manually entering all the commands in a shell works. But putting them in a batch will enter them too fast for ADB to handle (under Windows shell) I guess.
[Motorola Droid 4] Rick#2:
I don't know, it seemed to work fine for me with the script I made. Anyways, glad it worked out for you.

Now that we can re-root as well as (somewhat convolutedly) fastboot ourselves back on track, we're good to go.
[Motorola Droid 4] azrael293:
As stated in the guide, you need to be in camera mode not mass storage.
[Motorola Droid 4] rumgool:
I was trying to do it manually last night before the OP posted the batch file, and it was not working because I was in MTP instead of PTP. SO make sure you use PTP.

Put your phone in camera (PTP) mode for the USB connection and it should work fine. Also, after it completes, download Superuser from the market.

I ran Titanium Backup after everything and it told me it needed to fix my su binary permissions or something like that... I let it do its thing... Either way, IT WORKED!!!!!
[Motorola Droid 4] Grizzy3:
I put it in camera mode and made sure usb debugging is enabled. Then I ran the script for windows. Still getting the device not found error throughout. Really don't know what's going on.
[Motorola Droid 4] GermanGuy:
Maybe delete and re-install USB drivers on your PC.
[Motorola Droid 4] Die Bruine:
Did you update ADB? And make sure you have the USB drivers from ADB. Also check your hardware under device manager. Perhaps it's disabled or "not installed".

Are you running Vista/W7? Try running the shell as an administrator.
[Motorola Droid 4] Grizzy3:
How do you update adb? I just used what was included with the zip file. Wdym by usb drivers from adb? I have the motorola drivers installed from the motorola site. I'm able to connect my phone to my pc and transfer files and stuff. For some reason adb just doesn't detect my phone. I'm running windows 7. Ill try reinstalling drivers and checking the device manager when I get off work though. Thanks for the suggestions.
[Motorola Droid 4] Die Bruine:
Grab the latest ADB here. Just download, install and make sure ‘Android SDK Platform-tools’ and USB drivers (bottom) are selected. Click install/accept all and you should be ready to go.
[Motorola Droid 4] Grizzy3:
Thanks. I'll give it a shot when I get home and report back.
[Motorola Droid 4] GermanGuy:
Sorry about Holland losing to Germany :-)
[Motorola Droid 4] danifunker:
I had the same issue. I had to update my Motorola USB drivers here : http://www.motorola.com/Support/CA-EN/Support-Home/USB-Drivers-and-PC-Charging-Drivers

Once I completed that, everything worked. It seems that the old drivers aren't compatible with the .208 ICS kernel (possibly?)
[Motorola Droid 4] Grizzy3:
Yep, this was the problem. After I installed the latest drivers, everything worked perfectly. Thanks for the help.

@droidian, you might have the same issue.
[Motorola Droid 4] Die Bruine:
Good everything is resolved. Still not sure wether to upgrade from .200 to .208. Got no complaints so far su I guess I'll just stick with .200 until the official release.

BTW, soccer is not for me. Hate sports where grown ass men pretend, fake, dramatize, act hurt, be silly.....etc etc :D .
[Motorola Droid 4] GermanGuy:
Only the Italians do that :-)
[Motorola Droid 4] mj084:
@Rick#2

works like a charme!

great job :-)

EDIT:

but busybox wasn't copied to system/xbin
[Motorola Droid 4] Rick#2:
Yeah, I didn't bother putting provisions in the script to put that particular busybox binary on /system/xbin because there are better ones that you can download manually. If you want to keep that one, it's pretty easy from within the phone on a terminal like Better Terminal Emulator or the staple Terminal Emulator.

Unzip the ICS404root.zip file to an easy to remember folder (for example, C:\d4root) and navigate to the folder you unzipped it to in the Windows Command Prompt. (Windows Key+R, cmd.exe, <enter>)

C:\Documents and Settings\User\....\ > cd c:\d4root
C:\Documents and Settings\User\....\ > adb shell

Then in the Android shell:

$ su
$ mount -o remount,rw /system /system
$ exit

Then again in the Windows Command Prompt:

C:\Documents and Settings\User\....\ > adb push busybox /system/xbin
C:\Documents and Settings\User\....\ > adb chmod 755 /system/xbin/busybox
C:\Documents and Settings\User\....\ > adb chown 0.2000 /system/xbin/busybox

Done.
[Motorola Droid 4] mj084:
After getting root, i moved them manuelly with root explorer, and set permissions with it too.

what's the effect of this?

chown 0.2000 /system/xbin/busybox
[Motorola Droid 4] Rick#2:
0 means the owner is root, 2000 means the group is shell. Not entirely necessary but it doesn't hurt to keep things proper. ;)

You can usually just enter "chown root:shell (note the usage of the period above though, that is correct and not a typo, although sometimes you can get away with a colon in that form too) but some busybox binaries don't have those sorts of functionalities such as automatically linking the user/group aliases to their digital representation built into the commands in an effort to conserve memory in embedded devices. Makes it a ***** for compatibility, but if you stick to the most widely accepted (albeit unintuitive) form you'll be okay.
[Motorola Droid 4] mj084:
ok understand...

is there another way for root explorer for setting owner?

i got these error when i want to push busybox to phone:

failed to copy 'busybox' to '/system/xbin/busybox' : Permission denied

EDIT:

ok got tip and found it in root explorer...holding the file and sroll down to change owner...
[Motorola Droid 4] mintume:
camera mode means simply to start camera on my xperia ray?

sorry, i am really noob here.
[Motorola Droid 4] mintume:
i installed package and this installed android sdk. when i run sdk, it gives me below attached screen where i can't find USB drivers option:

i updated my sony pc companion suite also.

i am trying to root xperia ray ICS 4.0.4 but i am getting access denied error when i run automated script.

camera mode means, simply to start the camera on my ray or something else?
[Motorola Droid 4] Rick#2:
I don't know if this method works for the Xperia, the vulnerability that this focuses is Motorola-specific from what I can tell. I haven't tried it out on any other phones than the Droid 4 though, so who knows.

Aren't there better ways to root the Xperia running 4.0.4 out there?
[Motorola Droid 4] sangandongo:
Just to be clear... Would this method work for the stock Verizon ICS?
[Motorola Droid 4] PS4AndroidHacker:
Any quicker root method known?

Hey guys, I just purchased a Droid 4 tonight. I recently have moved up from my rooted Droid 2 to a newer Droid 3,I've had my Droid 3 for a week and just got ahold of our latest and greatest Qwerty phone. I'm a noob with the Droid 4 but not with rooting and using ADB and all that. My question is simply? Is there any easier rooting methods that anybody knows of so far? Like Petes Motorola Root Tools or anything? I'm just interested and I will follow along closely with this thread. Thanks for any future help!
[Motorola Droid 4] kwyrt:
Check out the Droid 4 Utility Updated thread.
[Motorola Droid 4] PS4AndroidHacker:
Many thanks!

Thanks for the help man,I'll check it out!
[Motorola Droid 4] eiem:
Hi Folk,

can't get root access... i ads shell into the device... but :

255|shell@android:/system/bin $ cp

cp

/system/bin/sh: cp: not found

127|shell@android:/system/bin $

...

/system/bin/sh: push: not found

... etc

it sounds i dont have any chance to cp push or do anything else into the fs

su and debugfs are in sdcard but cannot mv...

any idea?

my mount is :

/dev/block/mmcblk0p21 /system ext4 rw,relatime,user_xattr,barrier=1,data=ordered 0 0

/dev/block/mmcblk0p14 /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0

/dev/block/mmcblk0p16 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0

/dev/block/mmcblk0p23 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,noauto_da_all

/dev/block/mmcblk0p12 /data/asusdata ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,noauto_da_alloc 0

/dev/block/mmcblk0p22 /data/gmxt ext4 ro,nosuid,nodev,relatime,user_xattr,barrier=1,noauto_da_alloc 0 0

/dev/block/mmcblk0p18 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0

/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,ioc

device is padfone, updated 9.20..xxx , ics 4.0.4

Thanks.

Alex
[Motorola Droid 4] danifunker:
Install busybox. Sounds like a common issue. Many rooting methods don't come with busybox installed. Lookup busybox free from the play store and you should be good.
[Motorola Droid 4] Hello_Robert:
Where exactly do I put the su and debugfs files in the phone? I have tried the root.bat and it fails on the install of the debugfs...

ICS is running smooth, but I can not root... Help please
[Motorola Droid 4] Hello_Robert:
I installed busybox, but it wants root as well... The only thing working right now is my root explorer... It didn't ask for root or anything, just works. weird.... set cpu=no, titanium backup=no, adfree=no...

Help please..
[Motorola Droid 4] Hello_Robert:
Could someone do a update.zip?
[Motorola Droid 4] myfishbear:
https://www.dropbox.com/s/2mvnypvxg2kufdl/ics4.0root.zip

run that and download superuser from market. when installed run the update and reapply in tha application... then install busybox
[Motorola Droid 4] Hello_Robert:
Did not work.... it gets to the debugfs and tells me : /dev/block/mmblk1p20 : bad magic number.

Any Ideas?
[Motorola Droid 4] jsnweitzel:
Try again or use the other root method.
[Motorola Droid 4] Hello_Robert:
Got It!!

I used ... http://t.co/mbIAmwH8

Thanks all for the Help..
[Motorola Droid 4] PS4AndroidHacker:
Easier Root Method

So I was messing around today and rooted my Droid 3 successfully today and thought I'd try out this same root method on my new Droid 4. To my surprise it worked and I have FULL root on my Droid 4. It was only 1 click and was done. If you guys have any doubts you can give it a try and thought it may be a little easier and more user friendly for everybody. I'm also running android 2.3.6 still on my Droid 4,it's the factory ROM from Verizon,I doubted it would work with my Droid 4 but came to find it took to the droid 4 very well. If anybody is interested I've uploaded the file for you guys of the program that I used. Essentially it is for GB only and I tried it with my fiance's Razr running ICS and had no luck. Hope this may help out somewhere along the line!
[Motorola Droid 4] rorytmeadows:
Hmm,

Not sure what I'm doing wrong here...

It pushes the files, reboots. Does the debug/cleaning up deal, reboots. Then reboots again, closing the command prompt window and after the reboot still doesn't have root...
[Motorola Droid 4] danifunker:
You sure that you're not in usb mass storage mode?
[Motorola Droid 4] DevilDaHusky:
i just got the ICS update. i'm coming from GB. i can't root because ADB won't detect the phone. i'm running Windows 7 Pro x64 and if it matters i have an ASRock Fatali1ty X79 Pro motherboard. it comes with XfastUSB but whether it's on or off it still won't detect. re/installing Moto Cast/Device manager changes nothing. also did a fastboot wipe still the same effect. AND atempting the root method within the terminal emulator gives me permission denied.

HELP ;_;
[Motorola Droid 4] danifunker:
Install the latest Motorola charging / USB drivers.

Sent from my XT894 running ICS
[Motorola Droid 4] DevilDaHusky:
nope, doesn't work.
[Motorola Droid 4] DevilDaHusky:
I've heard that the OTA update breaks ADB on the Droid 4 forcing it into "secure" mode. could this be the issue?
[Motorola Droid 4] YahyaIsrael:
Droid 4 ICS released

Verizon finally released there ICS for the Droid4 for :good:. This should speed up the development for CM9 and hopefully CM10
[Motorola Droid 4] PS4AndroidHacker:
Official ICS and now I'm lost.

OK,so today I updated to the official ICS update from Verizon and forgot to temp un-root my D4 to re-install it upon having ICS. I now have ICS and have tried the exact way that the thread states in the beginning and was unsuccessful. I also tried the razors edge root method and had no luck as well.I was attached to the computer using the camera mode and not USB Mass Storage as well. I have posted my results using ADB with my newly updated D4 with ICS:

C:\Users\Ps3AndroidHacker>adb shell

|shell@cdma_maserati:/ $ cd /sdcard

cd /sdcard

shell@cdma_maserati:/sdcard $ cp su /data/local/12m/

cp su /data/local/12m/

cp: su: No such file or directory

1|shell@cdma_maserati:/sdcard $ cp debugfs /data/local/12m/

cp debugfs /data/local/12m/

cp: debugfs: No such file or directory

1|shell@cdma_maserati:/sdcard $ cd /data/local/12m

cd /data/local/12m

shell@cdma_maserati:/data/local/12m $ chmod 755 debugfs

chmod 755 debugfs

Unable to chmod debugfs: No such file or directory

10|shell@cdma_maserati:/data/local/12m $ chmod755 su

chmod755 su

/system/bin/sh: chmod755: not found

127|shell@cdma_maserati:/data/local/12m $ mv batch batch.bak

mv batch batch.bak

shell@cdma_maserati:/data/local/12m $ ln -s /dev/block/mmcblk1p20 batch

ln -s /dev/block/mmcblk1p20 batch

shell@cdma_maserati:/data/local/12m $ exit

exit

C:\Users\Andrew>adb reboot

C:\Users\Andrew>adb wait-for-device shell

shell@cdma_maserati:/ $ cd /data/local/12m

cd /data/local/12m

shell@cdma_maserati:/data/local/12m $ rm batch

rm batch

shell@cdma_maserati:/data/local/12m $ mv batch.bak batch

mv batch.bak batch

shell@cdma_maserati:/data/local/12m $ /data/local/12m/debugfs -w /dev/block/mmcb

lk1p20

gfs -w /dev/block/mmcblk1p20 <

/system/bin/sh: /data/local/12m/debugfs: not found

127|shell@cdma_maserati:/data/local/12m $ debugfs

debugfs

/system/bin/sh: debugfs: not found

127|shell@cdma_maserati:/data/local/12m

$

Any idea what I could be doing wrong here guys? I copied the su and the debugfs files directly to my mounted internal sd card of my phone before transferring to camera mode. The files are still on my sd card. Any ideas and help would be greatly appreciated! Thanks to everybody here,I'll continue following the thread for updates.
[Motorola Droid 4] DevilDaHusky:
I found the problem!!

All I had to do was do a factory reset! it's weird since I did the OTA update and I did a fastboot restore. I guess there's some kind of hic-up that the /data section or /system section needs to be wiped.

*exhales* finally I can root!