Database Users

help me get my vibrant to stock

I previously received my vibrant rooted and using this method on the thread http://forum.xda-developers.com/showthread.php?t=734475 and i used the unrooted file on page two. everything worked great but i still have root. I have the superuser permission show up on my app list, i also tested to see if i have root by installing a root only app, and it worked. so can anybody help get to stock?

Did you use the odin flash? That will put the phone back to 100% stock. Sounds like you used the nandroid, it might not remove extra stuff like the root files.

ttabbal said:
Did you use the odin flash? That will put the phone back to 100% stock. Sounds like you used the nandroid, it might not remove extra stuff like the root files.
Click to expand...
Click to collapse
yes i used the nandroid. can you point me to the odin flash? and is the odin more dangerous to use than nandroid? thanks for the help.

look in the vibrant development section you can't miss it for god sake search man no one is going to spoonfeed you

vdub804 said:
look in the vibrant development section you can't miss it for god sake search man no one is going to spoonfeed you
Click to expand...
Click to collapse
listen, im new to this and ive already searched the devolpment section and theres a couple similar threads. so, since i dont really know what im doing, i asked for help. all i asked was to point me to the thread that someone who is experienced in this thinks i should use. thanks for the help.

http://forum.xda-developers.com/showthread.php?t=734475
I think the complaint is that it's the same thread you would have gotten the nandroid image from. No, odin is not more dangerous, so long as you are flashing STOCK roms. Don't go flashing euro stuff with it, and you'll be fine. There are step by step directions in that thread, follow them and you'll be back to stock in no time.

ttabbal said:
http://forum.xda-developers.com/showthread.php?t=734475
I think the complaint is that it's the same thread you would have gotten the nandroid image from. No, odin is not more dangerous, so long as you are flashing STOCK roms. Don't go flashing euro stuff with it, and you'll be fine. There are step by step directions in that thread, follow them and you'll be back to stock in no time.
Click to expand...
Click to collapse
thank you for the help. i was just confused as to which one to use. hopefully, when im more experienced in this, i wont post stupid questions like this.

You dont need to flash, just remove the following with Terminal Emulator or file manager of your choice:
/system/app/Superuser.apk
/system/xbin/busybox
/system/bin/su
Reboot and you will no longer have root access.

mrxela said:
You dont need to flash, just remove the following with Terminal Emulator or file manager of your choice:
/system/app/Superuser.apk
/system/xbin/busybox
/system/bin/su
Reboot and you will no longer have root access.
Click to expand...
Click to collapse
im in Terminal Emulator and typed
/system/app/Superuser.apk
it says
/system/app/Superuser.apk: Permission denied
any ideas?

stepinmyworld said:
im in Terminal Emulator and typed
/system/app/Superuser.apk
it says
/system/app/Superuser.apk: Permission denied
any ideas?
Click to expand...
Click to collapse
did u type "su" before typing every other else?
it should be like:
# whatever you type
not $ whatever you type.

If you are using terminal then type this, each line should be entered on its own.
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su

From the sticky at the top of the page (that says to read before asking). If you want to use the links, go to the sticky.
HOW TO UN-ROOT *ie, sending your phone in for warranty work
The following code can be keyed in Terminal Emulator (could also be done in ADB or deleting the files using Root Explorer). If you do use Terminal, change the keyboard to the stock Android KB prior to opening Terminal. Apparently the backspace on swype does not work in Terminal. Each line should be entered separately. bahnburner gave the instructions in this thread, which you should review first.
Quote:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
* Alternate Method *
TGA_Gunnman in this thread created a one click root/unroot program. Thank him for his effort.

mrxela said:
You dont need to flash, just remove the following with Terminal Emulator or file manager of your choice:
/system/app/Superuser.apk
/system/xbin/busybox
/system/bin/su
Reboot and you will no longer have root access.
Click to expand...
Click to collapse
mrxela said:
If you are using terminal then type this, each line should be entered on its own.
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
this worked! Thank you. This should go into the thread as a sticky or named terminal commands for un-rooting. so hopefully i will receive OTA updates corrects?

It is in the sticky.

JEEBUS (10....)

mrxela said:
It is in the sticky.
Click to expand...
Click to collapse
aww shux. smh
thanks

I used root explorer and deleted those files, so that means I'm on stock and I can get warranty service? Thanks a lot guys, you have saved a noob

stepinmyworld said:
this worked! Thank you. This should go into the thread as a sticky or named terminal commands for un-rooting. so hopefully i will receive OTA updates corrects?
Click to expand...
Click to collapse
Haha rooting won't keep you from getting OTA updates.

[SOLVED] Uninstall Swype?

I need to uninstall swype and reinstall it. Ive tried over writing it with the default apk but its not removing a theme I installed with metamorph. If I can uninstall it, a fresh install should fix it.
I just dont know how to remove it

I don't know if you want to go to this extreme, but I did. I fudged up the phone real good by removing and installing stuff. I finally got fed up and flashed it back to stock and applied root again. This time I'll keep my fingers out of it. I hated touchwiz in the beginning, but now it's kinda growing on me. I've never had an iphone but the home and drawer remind me of iphone wannabe. It's okay for now.
Sent from my SPH-D700 using XDA App

There a tool over at sdx-developers that can remove that when root explorer can't. I forget the name of it. There's also a pay app in the market that I think is called root manager that can successfully remove crap too. I didn't have much luck putting the general swype 1.61 in. It refused to install. That's when I think I just flashed it back to factory image. A full reset/wipe wouldn't fix it either.
Sent from my SPH-D700 using XDA App

I had to do this a few days ago for similar reasons. This is what I did:
First, you have to open your browser or other app with a text field. Select the text field then long press the text field again and switch the input method to the stock android kb.
Next, you have to make sure /system is mounted as r/w. The early versions of the the rooting scripts did not remount correctly but the newer ones supposedly fix it. I just looked in the initial rooting .bat file (on the PC) for the remount command and used adb to remount /system.
You can test if it's remounted correctly by renaming Swype.apk to Swype.bak with Root Explorer then going up a level and back to /system/app. If it's not mounted correctly it will show as Swype.apk again. If it shows as Swype.bak still, then you just have to copy the original Swype.apk to /system/app and then switch input method back to Swype!
Sent from my Epic 4G using XDA App

yea its mounting in r-r, thats def my problem, cant change swype.apk with root explorer
so i need to re-root?

I don't know what's causing it but root explorer doesn't seem to work properly on the phone (not sdcard) filesystem in the system app folder. It's stuck in rw mode. People have said different things why but I forgot. I did noobnl's latest flash and it's still not working right. His script is removing the old root and my phone doesn't have that on there. I don't know what to tell ya. Maybe I should look for another root file manager.

kennethlongshaw said:
yea its mounting in r-r, thats def my problem, cant change swype.apk with root explorer
so i need to re-root?
Click to expand...
Click to collapse
I don't know if re-rooting will fix it or not. You could try. Here's the exact steps I took using adb from the PC:
Code:
adb shell
su
ls /system/app/S* (just shows Swype.apk is in fact in /system/app)
mount -t rfs -o remount,rw /dev/block/stl9 /system
mv /system/app/Swype.apk /system/app/Swype.bak
ls /system/app/S* (just to confirm Swype.apk is now Swype.bak)
cp /sdcard/download/Swype.apk /system/app/Swype.apk (or replace first argument with path of the good Swype.apk on your phone)
ls /system/app/S* (just to confirm Swype.apk and Swype.bak are both there)
reboot (reboots the phone, dunno if its really necessary)

dwyw42 said:
I don't know if re-rooting will fix it or not. You could try. Here's the exact steps I took using adb from the PC:
Code:
adb shell
su
ls /system/app/S* (just shows Swype.apk is in fact in /system/app)
mount -t rfs -o remount,rw /dev/block/stl9 /system
mv /system/app/Swype.apk /system/app/Swype.bak
ls /system/app/S* (just to confirm Swype.apk is now Swype.bak)
cp /sdcard/download/Swype.apk /system/app/Swype.apk (or replace first argument with path of the good Swype.apk on your phone)
ls /system/app/S* (just to confirm Swype.apk and Swype.bak are both there)
reboot (reboots the phone, dunno if its really necessary)
Click to expand...
Click to collapse
mmmm. That fixed. it. I owe you a beer

kennethlongshaw said:
mmmm. That fixed. it. I owe you a beer
Click to expand...
Click to collapse
Hi guyz.
I cant delete swype.apt file from /system/app/*
i am using SUFBS program (reed/write option enabled)
i tried use command in terminal:
Code:
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
but i get only;
Code:
permission denied
z4root show info that my phone is rooted
PDA i5800XXJI2
any ideas how to del that file? :]

(Q) Root with Super User

So I'm rooted and downloaded Super User app from market. I have a bunch of root apps but the only app listed in the super user app is Titanium. Any reason why the other rooted apps (Set Cpu, Minfree Manager, etc.) aren't listed?

Have they asked for superuser?
Via EVO on 4G with XDA App

awenthol said:
Have they asked for superuser?
Via EVO on 4G with XDA App
Click to expand...
Click to collapse
No it doesn't
Sent from my CM6 powered device

krazyflipj said:
No it doesn't
Sent from my CM6 powered device
Click to expand...
Click to collapse
We managed to fix this problem the other night on the irc channel. I didn't post anything because it doesn't seem like many people are using superuser.apk. The problem is that superuser needs to install it's own version of the su program to run properly. The current root method replaces su every reboot. When you lose the su that superuser.apk installs it can't control root access anymore and basically any program can request root without a prompt to you. The fix is to just replace the jk-su file in /system/bin/ with the superuser su. Then every reboot it will just use the one that works with the superuser app. I did this a few days ago and haven't had any problems.
The procedure is as follows (you need to use adb):
Go into the superuser app, go to the "settings" tab and at the very bottom choose to update su (it should change from saying original to something like "su v2.3.1-ef").
Plug the phone into usb and make sure you have USB debugging enabled.
Open a command prompt on the computer and goto your android sdk tools folder to run these commands (IMPORTANT NOTE - Make sure you have the phone screen on and unlocked when you run the su command below because superuser will ask you for permission and you need to click yes. It wont prompt if the screen is off or locked and the adb shell will just sit there waiting for a response. As soon as you click yes on the phone you should get a # in the adb shell):
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
cp /system/bin/su /system/bin/jk-su
exit
Now you should just reboot the phone and check that it worked by running any program that needs root access that isn't already listed with superuser. I suggest shootme or wifi tether. tether asks when you start or stop tethering and when you allow a mac address in the access control.

richse said:
We managed to fix this problem the other night on the irc channel. I didn't post anything because it doesn't seem like many people are using superuser.apk. The problem is that superuser needs to install it's own version of the su program to run properly. The current root method replaces su every reboot. When you lose the su that superuser.apk installs it can't control root access anymore and basically any program can request root without a prompt to you. The fix is to just replace the jk-su file in /system/bin/ with the superuser su. Then every reboot it will just use the one that works with the superuser app. I did this a few days ago and haven't had any problems.
The procedure is as follows (you need to use adb):
Go into the superuser app, go to the "settings" tab and at the very bottom choose to update su (it should change from saying original to something like "su v2.3.1-ef").
Plug the phone into usb and make sure you have USB debugging enabled.
Open a command prompt on the computer and goto your android sdk tools folder to run these commands (IMPORTANT NOTE - Make sure you have the phone screen on and unlocked when you run the su command below because superuser will ask you for permission and you need to click yes. It wont prompt if the screen is off or locked and the adb shell will just sit there waiting for a response. As soon as you click yes on the phone you should get a # in the adb shell):
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
cp /system/bin/su /system/bin/jk-su
exit
Now you should just reboot the phone and check that it worked by running any program that needs root access that isn't already listed with superuser. I suggest shootme or wifi tether. tether asks when you start or stop tethering and when you allow a mac address in the access control.
Click to expand...
Click to collapse
Hmmm cp /system/bin/su /system/bin/jk-su didn't work. I ls /system/bin and don't see jk-su listed just su...

krazyflipj said:
Hmmm cp /system/bin/su /system/bin/jk-su didn't work. I ls /system/bin and don't see jk-su listed just su...
Click to expand...
Click to collapse
What root did you use? I did mine manually so there may be some differences if you used a one click.
Edit: I just looked at noobnl's one click root and it uses the same script that contains the line:
#copies busybox su
cat /system/bin/jk-su > /sdx/su
so it should definitely be there even if you used his one click.
When you run the command "ls -l /system/bin/jk-su" what do you get?
I get this:
ls -l /system/bin/jk-su
-rwsr-sr-x root root 26264 2010-09-18 06:10 jk-su

Please delete

krazyflipj said:
Please delete
Click to expand...
Click to collapse
Did you get it working? After you updated su through the superuser app then it started working so that is why it asked you for permission when you were in terminal. The problem is that if you reboot without applying the rest of the fix to replace jk-su then you will lose the updated su and it will stop working.

richse said:
Did you get it working? After you updated su through the superuser app then it started working so that is why it asked you for permission when you were in terminal. The problem is that if you reboot without applying the rest of the fix to replace jk-su then you will lose the updated su and it will stop working.
Click to expand...
Click to collapse
Hey Richse, I'm trying to get this to work but it isn't.

rose1 said:
Hey Richse, I'm trying to get this to work but it isn't.
Click to expand...
Click to collapse
can you give me more information, what errors are you getting or what exactly is happening?

richse said:
can you give me more information, what errors are you getting or what exactly is happening?
Click to expand...
Click to collapse
Okay, I did the one click root method that is stickied. Then I did
adb shell
su
after doing su, I initially saw on the phone that unknown user was asking for superuser access. Of course, "unknown user" is me so I granted it. Then I saw the # then I went ahead and did
mount -t rfs -o remount,rw /dev/block/stl9 /system
That worked fine . The line repeated itself which indicates that it worked. When I do
cp /system/bin/su /system/bin/jk-su
it then says cp: not found.
Just to give you a little more info, I just restored my phone with odin to factory defaults, then I updated to the DI07 update. Then I installed the final clockwork mod recovery, then I did the one click root method. Then I installed superuser in the system/app folder.

rose1 said:
Okay, I did the one click root method that is stickied. Then I did
adb shell
su
after doing su, I initially saw on the phone that unknown user was asking for superuser access. Of course, "unknown user" is me so I granted it. Then I saw the # then I went ahead and did
mount -t rfs -o remount,rw /dev/block/stl9 /system
That worked fine . The line repeated itself which indicates that it worked. When I do
cp /system/bin/su /system/bin/jk-su
it then says cp: not found.
Just to give you a little more info, I just restored my phone with odin to factory defaults, then I updated to the DI07 update. Then I installed the final clockwork mod recovery, then I did the one click root method. Then I installed superuser in the system/app folder.
Click to expand...
Click to collapse
I'm not sure why cp doesn't work, it just means copy. An alternative to try is to delete jk-su and replace it with the su you updated. Use these commands in place of the cp command:
rm /system/bin/jk-su
cat /system/bin/su > /system/bin/jk-su
Make sure you do this after updating su in the superuser app and without rebooting in between. Let me know if you have any problems.

followed instructions. no errors but i still have no programs asking for permission. i had wifi tether downloaded before and it worked. I downloaded shootme to see if it would ask for permission and it didnt - but it works. neithe one is lited in superuser either.
listed is:
adfree / quickboot / root manager / startup manager ( 3 of them) / super manager / unknown ( spawned right after i followed instrution)
any ideas
uninstall supersuser and reinstalled:
listed apps now:
adfree / busybox installer / root explorer / rootmanager / sufbs / tit backup
again not sure is it is correct. but seems to work "I THINK"

spdwiz18 said:
followed instructions. no errors but i still have no programs asking for permission. i had wifi tether downloaded before and it worked. I downloaded shootme to see if it would ask for permission and it didnt - but it works. neithe one is lited in superuser either.
listed is:
adfree / quickboot / root manager / startup manager ( 3 of them) / super manager / unknown ( spawned right after i followed instrution)
any ideas
uninstall supersuser and reinstalled:
listed apps now:
adfree / busybox installer / root explorer / rootmanager / sufbs / tit backup
again not sure is it is correct. but seems to work "I THINK"
Click to expand...
Click to collapse
When you go to update su in the superuser app does it say "original" and then change or does it stay updated after you reboot?

richse said:
When you go to update su in the superuser app does it say "original" and then change or does it stay updated after you reboot?
Click to expand...
Click to collapse
what i have:
cwm 2.5.1
root 2.1.1
di07
now for the long and skinny:
i checked. went to superuser and it told me 2.3.1 -ef i then HARD rebooted, came back with no root.and superuser told be original, hard reboot again, still no root. So one more time- third time is a charm - i have root and superuser told me 2.3.1 -ef
thanks again for the help.
i think my phone might not be total stable.. lol
any ideas.
also - i thought about upping root to most recent but unsure if i need to unroot or if i can install over it. your thoughts on this matter!!!!

spdwiz18 said:
what i have:
cwm 2.5.1
root 2.1.1
di07
now for the long and skinny:
i checked. went to superuser and it told me 2.3.1 -ef i then HARD rebooted, came back with no root.and superuser told be original, hard reboot again, still no root. So one more time- third time is a charm - i have root and superuser told me 2.3.1 -ef
thanks again for the help.
i think my phone might not be total stable.. lol
any ideas.
also - i thought about upping root to most recent but unsure if i need to unroot or if i can install over it. your thoughts on this matter!!!!
Click to expand...
Click to collapse
I doubt you need to update root. The root I used was the original manual method by joeykrim. The one click just automates that method. There is no reason why you should have to reboot multiple times to get this working. You basically just replaced a file with a similar file and the script that was installed when you rooted uses that file to create a new su every time you reboot. Personally, I would wipe to stock with Odin and then use the manual root method to make sure nothing funny is going on with your phone. When you rebooted and the su was "original" you didn't lose root, it just meant that superuser wouldn't work. For now, as long as the 2.3.1 -ef sticks around superuser will work just fine. As an alternative you could try noobnl's newest stuff. Looks like he made it compatible with superuser, so I think that would negate the need to use this type of fix. I'm not sure what he did to add the compatibility but you could probably ask him.

if you flash noobnl's latest kernel, it includes superuser and it works perfectly.

rose1 said:
if you flash noobnl's latest kernel, it includes superuser and it works perfectly.
Click to expand...
Click to collapse
The only issue I see with that is you have to use a DG27 kernel. If you want to use a DI07 kernel you still need to use this fix.

richse said:
The only issue I see with that is you have to use a DG27 kernel. If you want to use a DI07 kernel you still need to use this fix.
Click to expand...
Click to collapse
Very true. I didn't think about that.

I have latest Noobls kernel flashed on top of DI07 and this fix did not work.First thing that dint work is i never got SuperUser prompt after i typed su in adb shell,i got su in windows but no prompt on the phone.
To make it short i did the whole procedure from BetterTerminal(now i got su prompt) rebooted and back to same problem.Man,this been bugin me for two days now,sometimes i reboot the phone and i have root permissions then i reboot again and they are gone!
Big question is:is everybody on Epic have same issue or is it just on certain phones,kernels or roms?

Rooted but not rooted (U8800-51)

I can root this phone. No problem. I can then remount /system (or and other mount) as read-write and make changes. HOWEVER, I cannot get any other programs to recognize the device as rooted. I have su over-permissioned to 777 (I have it permissioned to root.shell).
What have I overlooked?

Did you install superuser app?
Sent from my GT-P1000 using Tapatalk 2

Yes, I installed superuser. Then when I try to install something like busybox, it does not prompt to provide root privileges. It then fails to install. The whole thing is antithetical to the Linux model/sudo due to the lack of a login I suppose.

eyeconic said:
Yes, I installed superuser. Then when I try to install something like busybox, it does not prompt to provide root privileges. It then fails to install. The whole thing is antithetical to the Linux model/sudo due to the lack of a login I suppose.
Click to expand...
Click to collapse
SU needs chmod 4775 doesn't it? You have the binary inserted but it doesn't have the authority to execute as root.

mezkalz said:
SU needs chmod 4775 doesn't it? You have the binary inserted but it doesn't have the authority to execute as root.
Click to expand...
Click to collapse
I forgot that this isn't full-blown Linux. Of course you are correct and thank you. The leading (setuid) digit is necessary because we are permitting an unprivileged program with a pseudo-UID access to root-owned executables.

[Q] EVGA Tegra Note 7 root?

EDIT:
Go here to root your Tegra Note 7: https://github.com/linux-shield/shield-root/blob/master/README.md (thanks to CampGareth for finding the link).
I have tested this, it works with no bloatware, only installs SuperSu.
---------
Hey guys, I got my new Tegra Note 7 last night and I've been trying to get it rooted, but I keep running into trouble.
First of all, I DO NOT want to use some shady Chinese software that installs a bunch of bloat on both my tablet and PC just to get SuperSu going, I've tried that method and had to reset the tablet to get rid of all the crap it installs (and it didn't even seem to root anyway).
Now I'm trying the manual method from here: http://pan.baidu.com/wap/link?uk=3073396937&shareid=3129426036&third=0
Which, again, is Chinese but at least I can see what it's doing since I'm issuing ADB commands, and supposedly it has worked for others on this forum.
Now, I get to step 3 on the included PDF which says to boot an insecure bootloader image with "fastboot boot tegranote_insecure_boot.img", I do this and the tablet screen flashes a few times and reboots to android.
I get to the next step which says to open an adb shell, and do "/sbin/rootsh +p" to get a temp root shell, and this is where I get stuck. Instead of getting a root shell I get the message "/system/bin/sh: /sbin/rootsh: not found". Does anyone have suggestions?
By the way we really need a Tegra Note 7 subforum here at XDA, if the mods could add it that would be great.

dark42 said:
Hey guys, I got my new Tegra Note 7 last night and I've been trying to get it rooted, but I keep running into trouble.
First of all, I DO NOT want to use some shady Chinese software that installs a bunch of bloat on both my tablet and PC just to get SuperSu going, I've tried that method and had to reset the tablet to get rid of all the crap it installs (and it didn't even seem to root anyway).
Now I'm trying the manual method from here: http://pan.baidu.com/wap/link?uk=3073396937&shareid=3129426036&third=0
Which, again, is Chinese but at least I can see what it's doing since I'm issuing ADB commands, and supposedly it has worked for others on this forum.
Now, I get to step 3 on the included PDF which says to boot an insecure bootloader image with "fastboot boot tegranote_insecure_boot.img", I do this and the tablet screen flashes a few times and reboots to android.
I get to the next step which says to open an adb shell, and do "/sbin/rootsh +p" to get a temp root shell, and this is where I get stuck. Instead of getting a root shell I get the message "/system/bin/sh: /sbin/rootsh: not found". Does anyone have suggestions?
By the way we really need a Tegra Note 7 subforum here at XDA, if the mods could add it that would be great.
Click to expand...
Click to collapse
I would recommend the following procedure:
1. Download the root_tool_v2.zip attached to this post
2. Unzip the contents the root_tool_v2.zip to a directory
3. Run the following commands from your ADB and Fastboot directory:
Code:
adb reboot bootloader
fastboot boot tegranote_insecure_v2.img
4. Once your device finishes booting the insecure boot.img (Your device's screen will blink several times and then boot into Android) run the following commands:
Code:
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
exit
adb push su /system/xbin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell
chmod 6755 /system/xbin/su
chmod 644 /system/app/Superuser.apk
mount -o remount,ro /dev/block/mmcblk0p5 /system
exit
adb reboot
5. You should now have Superuser installed and have root access.
What I did was I modified the boot.img provided to be insecure and use an insecure adbd binary to allow a root shell when booted from which can then be used to setup Superuser and su binary access. Let me know how this goes for you and if you have any questions .

Wow, thanks for the help! Unfortunately your attachment seems to be corrupt, I can't decompress the archive. I'm using 7-zip btw. The forum says your attachment is 7.19MB but when downloaded it's only 160KB.
If you can re-upload it I will give it a go.

a reup of the file would be much appreciated! :good:
PS
i have a batch file to expedite the process.

dark42 said:
Wow, thanks for the help! Unfortunately your attachment seems to be corrupt, I can't decompress the archive. I'm using 7-zip btw. The forum says your attachment is 7.19MB but when downloaded it's only 160KB.
If you can re-upload it I will give it a go.
Click to expand...
Click to collapse
dergezero said:
a reup of the file would be much appreciated! :good:
PS
i have a batch file to expedite the process.
Click to expand...
Click to collapse
Re-uploaded the file for you guys let me know how it goes for you .

Awesome your new package downloaded fine.
However I'm still not getting root, I got to step 4 and when I open an adb shell I don't have permissions to do the next command.
The exact error message:
[email protected]:/ mount -o remount,rw /dev/block/mmcblk0p5 /system
mount -o remount,rw /dev/block/mmcblk0p5 /system
mount: Operation not permitted
So I guess the insecure boot image didn't work right. I should mention that I am using the latest Tegra Note firmware, I don't know if that makes a difference though. Any ideas?
Thanks for your help so far.

do you guys have a copy of the drivers for the tablet? mine only seems to work for storage.
update: got drivers working.

dergezero said:
do you guys have a copy of the drivers for the tablet? mine only seems to work for storage.
update: got drivers working.
Click to expand...
Click to collapse
I used Universal Naked Driver 0.73, I just manually installed the driver for the Nvidia Shield, thinking it would work, and it does!
Does shimp208's root image work for you, dergezero?

dark42 said:
I used Universal Naked Driver 0.73, I just manually installed the driver for the Nvidia Shield, thinking it would work, and it does!
Does shimp208's root image work for you, dergezero?
Click to expand...
Click to collapse
no, it just reboots. neither is working. im going to see if any one can give us a dump of their img that already works to be rooted. i tried that Chinese method and its really annoying and i dont get root on any computer i try it on.

Hey guys I am in the process of creating a new boot image that uses a different method for gaining root access and will upload that once I finish it.

shimp208 said:
Hey guys I am in the process of creating a new boot image that uses a different method for gaining root access and will upload that once I finish it.
Click to expand...
Click to collapse
:good: Awesome man, good luck! Eager to try it when you post it! :fingers-crossed:

dark42 said:
:good: Awesome man, good luck! Eager to try it when you post it! :fingers-crossed:
Click to expand...
Click to collapse
I agree, with the amount of malware that is in the chinese root tools, it makes me nervous to use the one the OP posted.
Brew

I wonder if someone would be able to port Clockworkmod Recovery to the TN7 eventually. The bootloader on this device is factory unlocked so it should be simple enough. Unfortunately I'm not a good enough programmer to get this done.
If we had Clockworkmod then rooting would be as easy as flashing the SuperSU .zip from the SD.

I have updated my original post with the rooting instructions to include a new insecure boot method follow the same instructions as before just use the new boot.img I uploaded to that post. Credit to teknoraver for the insecure adbd binary.

shimp208 said:
I have updated my original post with the rooting instructions to include a new insecure boot method follow the same instructions as before just use the new boot.img I uploaded to that post. Credit to teknoraver for the insecure adbd binary.
Click to expand...
Click to collapse
I tried your V2 image, still getting permission errors when doing "mount -o remount,rw /dev/block/mmcblk0p5 /system", what am I doing wrong?

dark42 said:
I tried your V2 image, still getting permission errors when doing "mount -o remount,rw /dev/block/mmcblk0p5 /system", what am I doing wrong?
Click to expand...
Click to collapse
When you boot the image and then type ADB shell do you get a root shell ([email protected]:/ #) or just a regular shell ([email protected]:/ $)?

Amazing
Nice to see you working on a different method of root... I am sorry to those who feel that the method I posted is getting negative reviews just wanted to throw something out there for people... however, I do feel much better with Shrimp208 working on a better root method I really wish we could get a forum going..

I used the Chinese root tool and all seems fine on my Tegra note
Sent from my TegraNote-P1640 using Tapatalk

shimp208 said:
When you boot the image and then type ADB shell do you get a root shell ([email protected]:/ #) or just a regular shell ([email protected]:/ $)?
Click to expand...
Click to collapse
Just a regular shell with $. Doesn't look like I get temp root permissions after running the tegranote_insecure_v2.img.
If it matters, I'm on the latest Stock ROM (4.2.2/JDQ39.13155_268.1942) and I'm using Universal Naked Driver 0.73 for the Shield, which works with this device. Maybe I need to use a different driver?

Toyeboy said:
I used the Chinese root tool and all seems fine on my Tegra note
Sent from my TegraNote-P1640 using Tapatalk
Click to expand...
Click to collapse
yeah it works but you dont really know what was installed on ur phone or on your pc. 3 apps are installed on your phone and a few reg changes on ur pc can be detrimental. and its all bloatware