Database Info

[Q] Wanting To Root

Greetings,
I am looking for an easy to understand method of root.
I have read the new user thread. I am afraid with this so called "easy" method for beginners, there is a lot of jargon used that I simply don't understand.
For example in the thread for easy root, I am lost at step #2 where I am instructed to:
"Note that adb is required.
Push misc.img, busybox, and psnueter using the following commands:"
I don't know what adb is let alone how to push misc.img, busybox and psnueter.
Can someone please point me to the instructions for absolute morons to this process like me.
Thanks in advance.

priapos said:
Greetings,
I am looking for an easy to understand method of root.
I have read the new user thread. I am afraid with this so called "easy" method for beginners, there is a lot of jargon used that I simply don't understand.
For example in the thread for easy root, I am lost at step #2 where I am instructed to:
"Note that adb is required.
Push misc.img, busybox, and psnueter using the following commands:"
I don't know what adb is let alone how to push misc.img, busybox and psnueter.
Can someone please point me to the instructions for absolute morons to this process like me.
Thanks in advance.
Click to expand...
Click to collapse
Android adb http://developer.android.com/guide/developing/tools/adb.html
which is in the sdk http://developer.android.com/sdk/index.html
You dont really need to know what the other tools are listed do, you just need to do what it says with them and the tools are linked in the thread you're reading to download I assume. If they aren't, then read through the manual method that is stickied in the developer's forum. A link for the tools (misc.img, busybox, and psnueter) can be found there.

I was a little nervous at first myself. I read over the directions several times and then found some information on how to get adb installed and working. Once I got that step understood the actual rooting process was super easy. You can cut and paste all the commands to ensure you don't typo. Just make sure to validate your checksums to save any potential headaches. My first attempt at it took about 20 minutes and I had absolutely ZERO issues.
It is well worth your time and effort. It is also far better to use this method than the easy root 1 steps as you will gain a slightly better understanding of how your phone works and what steps you can take when you inevitably mess something up flashing ROMS, mods and radios

Thanks for the quick reply.
I am not nervous, I just don't understand what any of this is.
I don't know what adb is or how to use it.
I don't know what copy and pasting the commands means.
I certainly don't know what "validate checksums" are.
I realize I am coming across as a comlete shmo, but explaining how to do this with more computer jargon doesn't clarify the process.
I really need instructions for dooshbags like me.
Thanks in advance.

There are also videos on YouTube showing JCases method and adb setup. I would link but I'm on my phone but it shouldn't be to hard to find.
Sent from my ADR6400L using XDA App

priapos said:
Thanks for the quick reply.
I am not nervous, I just don't understand what any of this is.
I don't know what adb is or how to use it.
I don't know what copy and pasting the commands means.
I certainly don't know what "validate checksums" are.
I realize I am coming across as a comlete shmo, but explaining how to do this with more computer jargon doesn't clarify the process.
I really need instructions for dooshbags like me.
Thanks in advance.
Click to expand...
Click to collapse
reading through this might help http://forum.xda-developers.com/showthread.php?t=1143188

There is no "easy", reliable way to root sans ADB and command lines. You will need to know this stuff before you try to root. You're going to need ADB in any event. If learning it isn't knowledge you desire, you shouldn't root your phone. For terms, you should refer to the dictionary stickied at the top of the forum. The best way to learn is to get the Android SDK, set it up, make sure your drivers are there, then play with ADB. Do simply stuff like check your serial number, the md5 of files on your SDcard, and harmless stuff like that. If you've got any questions along the way, feel free to PM me any time. I'm here often. And I'm usually faster than hunting through forums or the internet.

priapos said:
Greetings,
I am looking for an easy to understand method of root.
I have read the new user thread. I am afraid with this so called "easy" method for beginners, there is a lot of jargon used that I simply don't understand.
For example in the thread for easy root, I am lost at step #2 where I am instructed to:
"Note that adb is required.
Push misc.img, busybox, and psnueter using the following commands:"
I don't know what adb is let alone how to push misc.img, busybox and psnueter.
Can someone please point me to the instructions for absolute morons to this process like me.
Thanks in advance.
Click to expand...
Click to collapse
From what i think if u dont want the adb command line ****s you should try the software named "z4root". It automatically roots your phone.
Worked for me. And i think itz the easiest method available.
After installing the apk.
Open the application, click PERMANENT ROOT,
Then dnt let your phone sleep or lock itself, wait for about 10 minutes,
After the process reboot ypur phone.
Voila, you are rooted ..
Am new to the forums. please guide me..
Thanks and sorry for my poor english. Hope you like this.
Cheers!
__________________________________________________________
MODEL : LG Optimus GT540 (Rooted)
MOD : SwiftDroid v2.0 M6 (Based on CyanogenMod v7.1 RC0)
KERNEL : 2.6.29 (VirtualBox #309)
BUILD : GRJ22
RECOVERY : ClockworkMod Recovery v4.0
___________________________________________________________
BusyBox v1.19
SuperUser v2.3
SetCPU v2.2

I would not recommend "easy" root methods, since there is greater room for error. Understanding ADB will help you in the long run

MeAt.HoOk said:
From what i think if u dont want the adb command line ****s you should try the software named "z4root". It automatically roots your phone.
Worked for me. And i think itz the easiest method available.
After installing the apk.
Open the application, click PERMANENT ROOT,
Then dnt let your phone sleep or lock itself, wait for about 10 minutes,
After the process reboot ypur phone.
Voila, you are rooted ..
Am new to the forums. please guide me..
Thanks and sorry for my poor english. Hope you like this.
Cheers!
__________________________________________________________
MODEL : LG Optimus GT540 (Rooted)
MOD : SwiftDroid v2.0 M6 (Based on CyanogenMod v7.1 RC0)
KERNEL : 2.6.29 (VirtualBox #309)
BUILD : GRJ22
RECOVERY : ClockworkMod Recovery v4.0
___________________________________________________________
BusyBox v1.19
SuperUser v2.3
SetCPU v2.2
Click to expand...
Click to collapse
Don't think z4root works on the Thunderbolt just search youtube for Thunderbolt root and watch the tutorials. Links are provided for everything that needs to be downloaded.
Sent from my ADR6400L using XDA Premium App

I know z4root doesn't work for any modern HTC. You can have permanent root without s-off. The only way to do that is through ADB, using an engineering hboot, and applying various exploits. All the "easy" root methods are just scripts that do what jcase's guide lays out. And unlike the guide, if something goes south, you're lost and screwed. I think it would be safe to say "easy" roots have probably bricked more phones than anything else.

loonatik78 said:
I know z4root doesn't work for any modern HTC. You can have permanent root without s-off. The only way to do that is through ADB, using an engineering hboot, and applying various exploits. All the "easy" root methods are just scripts that do what jcase's guide lays out. And unlike the guide, if something goes south, you're lost and screwed. I think it would be safe to say "easy" roots have probably bricked more phones than anything else.
Click to expand...
Click to collapse
Is that u dbzfanatic? Looks awfully similar, lol.
Sent from my ADR6400L using XDA Premium App

nerogold said:
Is that u dbzfanatic? Looks awfully similar, lol.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Nope. Just a pieced up, inked up, "I been everywhere, man", freak of many talents and interests. Android phones are just one of them.

loonatik78 said:
Nope. Just a pieced up, inked up, "I been everywhere, man", freak of many talents and interests. Android phones are just one of them.
Click to expand...
Click to collapse
Sorry man I just wanted to say thanks to the other user I mentioned ,his method of rooting was and still is a great help to me already rooted 5 bolts and currently on #6 as I'm typing.
Sent from my ADR6400L using XDA Premium App

Do a google search for thunderbolt auto root. There is one posted in the Thuderbolt forums. I can't link directly to it because I don't have enough posts yet. I tested it on my wife's thunderbolt without a problem.

Greywolf66 said:
Do a google search for thunderbolt auto root. There is one posted in the Thuderbolt forums. I can't link directly to it because I don't have enough posts yet. I tested it on my wife's thunderbolt without a problem.
Click to expand...
Click to collapse
Yep, and the past guy to go that route, after being warned it was highly prone to failure, had it fail. Then he came back looking for help, but nobody could because what went wrong wasn't at all clear. Just not wise.

Ive used the one click root four times with no issues. Four diffrent tb's from 3 diffrent states. 2 of them had alrdy takin the ota's. Dont have the link handy but if was a time saver. Though a half arse understanding of the method helps avoid issues. Ill post the link when i get home.
Sent from my ADR6400L using XDA Premium App

loonatik78 said:
Yep, and the past guy to go that route, after being warned it was highly prone to failure, had it fail. Then he came back looking for help, but nobody could because what went wrong wasn't at all clear. Just not wise.
Click to expand...
Click to collapse
I rooted mine manually first. As you said in a previous post most "easy" roots are just scripts. That's what the one I used on my wife's was. I was following along the text of the batch file as I was running it so that if something happened I would know at what part of the script I was at. I had no problems with it though.
I'll agree that I could see where if someone where to run into a problem using script without any knowledge of what the script was doing they would probably end in a very bad place.

I think the obvious was missed in this thread: The OP is not a candidate for rooting. It's a risky task for experienced users and a non-task for noobs. He hasn't even stated a valid need for rooting the phone.

TabGuy said:
I think the obvious was missed in this thread: The OP is not a candidate for rooting. It's a risky task for experienced users and a non-task for noobs. He hasn't even stated a valid need for rooting the phone.
Click to expand...
Click to collapse
Come on, cut him some slack. Everyone was new once. He has already been warned.
Sent from my ADR6400L using XDA App
priapos said:
Thanks for the quick reply.
I am not nervous, I just don't understand what any of this is.
I don't know what adb is or how to use it.
I don't know what copy and pasting the commands means.
I certainly don't know what "validate checksums" are.
I realize I am coming across as a comlete shmo, but explaining how to do this with more computer jargon doesn't clarify the process.
I really need instructions for dooshbags like me.
Thanks in advance.
Click to expand...
Click to collapse
ADB "Android Development Bridge" Simply put just helps you develop apps and fix bugs. (In this case, you will use this to reinstall Android without a locked bootloader (a.k.a. S-Off) (the bootloader is code that is run when you first turn on your device that tells Android to run).
You don't have to know how to use ADB, but you must install it on your computer.
As far as copying and pasting commands go, the tutorial that you choose to visit will tell you to type this command ex: cp image.zip/sdcard/
You will just copy this code out of your browser (FireFox/Internet Explorer/Chrome/etc.) and paste it into a command line.
Your command line will depend on what operating system you use on your pc. Ex for Windows, you will use "Command Prompt" or on Linux/MAC you will use "Terminal".
As far as validation checksums goes, it is used to make sure that the file that you downloaded is 100% the same file that the developer made.
Basically, open up your command line and type (without quotes) "md5 image.zip" also, make sure you change to "image.zip" with whatever/where you file is at.
I would be more specific with these instructions I'd I knew what OS (operating system) you are using on your computer is.
After you type in the command and hit enter, it will spit out a long string of gibberish. Just make sure this "checksum" is the EXACT same as whatever the devolver put in the tutorial you are following.
As far as putting together an idiot proof guide, you will have to forgive us, but I don't think the people here want to have a bunch of people here flooding the forums with very basic questions that have been answered already on the internet. However, don't let that stop you from asking questions. Just make sure you help yourself first (Google what you don't understand) and then ask for clarification.
P.S. I claim touchscreen amnesty for any typos.
Sent from my ADR6400L using XDA App

Need stock recovery image for Coby 7022 build 20120106

I need a stock recovery image for the Coby Kyros 7022 build 20120106 (previous builds will not work). I tried to flash clockworkmod recovery on my tablet without making a backup of the stock image, only to find that cwm recovery doesn't work with the new build of my tablet. Can anyone give me a stock recovery image for this tablet? Any help would be greatly appreciated!

Same Problem.
I have yet to find a solution since 02/2012.

Maybe you can try this?
stock recovery image for Coby 7022

same probleme right here

Coby 7022 20120106 build
I ended up with no recovery after trying to install clockwork. Recovery didn't work (it bypassed recovery when using the proper keys) and I had no good backup. Flashing older firmware in the 11 2011 timeframe led to boot loops. I've not been able to find a stock Coby 7022 firmware from 20120106. However, I did find another post here regarding a different tablet using the same tcc8803 chipset with the same build date. dub dub dub dxtremeDOTcom.au/forum/viewforum.php?f=15 (remove spaces insert correct www etc...) So I gave it a try. I'm actually able to get the 7022 booted using this firmware and system but the touchscreen is not working, so I'm guessing that driver is not exactly correct.
Completely a noob but wanting to learn. BTW I did not use the FWTool as I read posts this kills the TS
So my ask is, does anyone know of a way to get the drivers for the 7022 build dated 20120106?
---------- Post added at 09:58 AM ---------- Previous post was at 09:51 AM ----------
coolhof said:
Maybe you can try this?
[dub dub dub androidtablets.netSLASHforumSLASHcoby-generation-2/28212-7022-help-cant-restore-2.html#post183680"]stock recovery image for Coby 7022[/URL]
Click to expand...
Click to collapse
This restore didn't work on my system. The 7022 from 20120106 seems to be a rare animal and little info on it yet.

Same problem here, I tried to flash a previous CWM/Stock Recovery and nothing... just bootloop when I try to enter recovery mode. So, does anyone have the stock recovery for the 20120106 build yet? Thank you in advance for the one who can help

20120106 stock lk.rom & MTD file
MostroXxX said:
Same problem here, I tried to flash a previous CWM/Stock Recovery and nothing... just bootloop when I try to enter recovery mode. So, does anyone have the stock recovery for the 20120106 build yet? Thank you in advance for the one who can help
Click to expand...
Click to collapse
After reading a bit, it seems what we need are two files that could be copied off a working stock machine of the proper build date or later. In our case on or after 20120106. The problem for me seems to be the lk.rom file. The ROM I used for the DExtreme pad boots but no touch screen function due to the DExtreme being a 5 touch capacitance screen and the Kyros 7022 being but 2.
There may be other problems with the DExtreme files like the camera being different or even the network adapter but no way of telling without the stock boot file. Anyway, I've resigned myself. My 7022 is a paper weight until I find the stock files.
If anyone comes across this looking to root and clockwork mod your 7022 and it's build date is on or after Jan 6 2012, please stop and use ADB to pull a copy of your stock OS off it first. Not only will you be able to help us out, but you'll be able to restore when things go horribly wrong.

chiefcrewdog said:
After reading a bit, it seems what we need are two files that could be copied off a working stock machine of the proper build date or later. In our case on or after 20120106. The problem for me seems to be the lk.rom file. The ROM I used for the DExtreme pad boots but no touch screen function due to the DExtreme being a 5 touch capacitance screen and the Kyros 7022 being but 2.
There may be other problems with the DExtreme files like the camera being different or even the network adapter but no way of telling without the stock boot file. Anyway, I've resigned myself. My 7022 is a paper weight until I find the stock files.
If anyone comes across this looking to root and clockwork mod your 7022 and it's build date is on or after Jan 6 2012, please stop and use ADB to pull a copy of your stock OS off it first. Not only will you be able to help us out, but you'll be able to restore when things go horribly wrong.
Click to expand...
Click to collapse
Well, I'm expecting another 7022 to arrive next week (kind of a late Mother's day gift), I assume it will be same build, so, I'll try to pull a copy of that unit and see if I can restore it on te semi-dead one. I will post again when it arrives to tell if it worked (or if I have two bricks xD). If it works, I'll upload a copy.

Stock 20120106 Kyros ROM
MostroXxX said:
Well, I'm expecting another 7022 to arrive next week (kind of a late Mother's day gift), I assume it will be same build, so, I'll try to pull a copy of that unit and see if I can restore it on te semi-dead one. I will post again when it arrives to tell if it worked (or if I have two bricks xD). If it works, I'll upload a copy.
Click to expand...
Click to collapse
Any Luck?

chiefcrewdog said:
Any Luck?
Click to expand...
Click to collapse
Neh, It's an international shipment and got delayed. I was supposed to receive it today, but now I'll have to wait 'til monday or tuesday. I'll post when I get them to tell if it worked.
Edit: what I could do was root it. It was quite easy using SuperOneClick, but still no recovery...

chiefcrewdog said:
Any Luck?
Click to expand...
Click to collapse
ehmmm... BAD luck the one that arrived is a previous build (September 2011).
So, for now, we are pretty much screwed :/

I just got a 7022 that has a build date of 20120106. I am new to android so I have no idea what I am doing but if someone gives me step by step instructions I can try to get it off the tablet for you. Good thing I found this forum, I was about to try and root it.

nduke416 said:
I just got a 7022 that has a build date of 20120106. I am new to android so I have no idea what I am doing but if someone gives me step by step instructions I can try to get it off the tablet for you. Good thing I found this forum, I was about to try and root it.
Click to expand...
Click to collapse
That's great!
first, is it rooted, or have you done any MOD?
---------- Post added at 01:05 AM ---------- Previous post was at 12:21 AM ----------
nduke416 said:
I just got a 7022 that has a build date of 20120106. I am new to android so I have no idea what I am doing but if someone gives me step by step instructions I can try to get it off the tablet for you. Good thing I found this forum, I was about to try and root it.
Click to expand...
Click to collapse
1) You need to install the Android SDK, instructions can be found HERE, but basically you need to:
-) Download the .exe and install it
-) Locate the folder where you installed it and run as administrator “SDK Manager.exe”
-) Check (if unchecked) the boxes for SDK Tools, SDK Platform Tools and Google USB Driver Package. You can check any others if you want, but for now, you only need those.
2) You (may) need the specific drivers for the device. You can use the Motorola drivers, which work very nice with the Cobys, you can install the drivers from HERE. Just download and install.
3) You need to root your device, for that, I recommend using SuperOneClick, which can be found HERE. Too root your device:
-) Make sure you have “USB Debugging mode” activated. In your tablet, go to settings -> Applications -> Development and check (if unchecked) the USB Debugging mode.
-) Connect your device to your PC, if it’s the first time you connect it, you need to wait a little while the drivers get configured.
-) When your device is connected and correctly configured, run SuperOneClick as administrator, and click on “Root”. Now wait a little while it gets rooted.
4) Last step, backup recovery image. For this, you’ll need a terminal emulator. You can download “Android Terminal Emulator” from 1mobile.com or any other app market. To do the backup:
-) Open the terminal emulator on your tablet.
-) Request SuperUser Permissions, to do this, write
Code:
su
and hit enter/return, you’ll be asked if you want to grant SuperUser rights to the app Android Terminal Emulator, click “Allow”.
-) Write this line and hit enter/return:
Code:
dd if=/dev/mtd/mtd6 of=/sdcard/recovery.img bs=4096
-) Now, a file named “recovery.img” should be automatically created on your /sdcard folder. THAT, my friend, is the file we so desperately need to revive our tablets, now zip it and uploaded to any server. (Please )
Now that you are rooted, you can do things such as installing the Google apps. There are a lot of tutorials over the internet, but, let me know if you have any trouble so I can help you
WARNING: Don’t, I repeat DON’T try to install ClockWorkMod using ANY of the tutorials found over the internet. Those tutorials work ONLY for builds previous to 20110106, and if you try to do it on your device, you are going to semi-brick it (just like we did xD).

I just got it as a replacement under warranty today and have not done anything to it. I am busy studying for finals now but when I get a chance(prob friday morning) I will follow the steps and upload the recovery.img file

nduke416 said:
I just got it as a replacement under warranty today and have not done anything to it. I am busy studying for finals now but when I get a chance(prob friday morning) I will follow the steps and upload the recovery.img file
Click to expand...
Click to collapse
Well, no problem. If you do that we'll be EXTREMELY thankful

This might be a stupid question but bear with me, I don't know anything about this. Does personal info get stored on the recovery.ing file? Should I remove apps like the amazon app store or other ones that I have to log in with?

Old build no bueno...
MostroXxX said:
ehmmm... BAD luck the one that arrived is a previous build (September 2011).
So, for now, we are pretty much screwed :/
Click to expand...
Click to collapse
Bleh
---------- Post added at 04:51 PM ---------- Previous post was at 04:46 PM ----------
MostroXxX said:
That's great!
first, is it rooted, or have you done any MOD?
---------- Post added at 01:05 AM ---------- Previous post was at 12:21 AM ----------
1) You need to install the Android SDK, instructions can be found HERE, but basically you need to:
-) Download the .exe and install it
-) Locate the folder where you installed it and run as administrator “SDK Manager.exe”
-) Check (if unchecked) the boxes for SDK Tools, SDK Platform Tools and Google USB Driver Package. You can check any others if you want, but for now, you only need those.
2) You (may) need the specific drivers for the device. You can use the Motorola drivers, which work very nice with the Cobys, you can install the drivers from HERE. Just download and install.
3) You need to root your device, for that, I recommend using SuperOneClick, which can be found HERE. Too root your device:
-) Make sure you have “USB Debugging mode” activated. In your tablet, go to settings -> Applications -> Development and check (if unchecked) the USB Debugging mode.
-) Connect your device to your PC, if it’s the first time you connect it, you need to wait a little while the drivers get configured.
-) When your device is connected and correctly configured, run SuperOneClick as administrator, and click on “Root”. Now wait a little while it gets rooted.
4) Last step, backup recovery image. For this, you’ll need a terminal emulator. You can download “Android Terminal Emulator” from 1mobile.com or any other app market. To do the backup:
-) Open the terminal emulator on your tablet.
-) Request SuperUser Permissions, to do this, write
Code:
su
and hit enter/return, you’ll be asked if you want to grant SuperUser rights to the app Android Terminal Emulator, click “Allow”.
-) Write this line and hit enter/return:
Code:
dd if=/dev/mtd/mtd6 of=/sdcard/recovery.img bs=4096
-) Now, a file named “recovery.img” should be automatically created on your /sdcard folder. THAT, my friend, is the file we so desperately need to revive our tablets, now zip it and uploaded to any server. (Please )
Now that you are rooted, you can do things such as installing the Google apps. There are a lot of tutorials over the internet, but, let me know if you have any trouble so I can help you
WARNING: Don’t, I repeat DON’T try to install ClockWorkMod using ANY of the tutorials found over the internet. Those tutorials work ONLY for builds previous to 20110106, and if you try to do it on your device, you are going to semi-brick it (just like we did xD).
Click to expand...
Click to collapse
nduke416 said:
This might be a stupid question but bear with me, I don't know anything about this. Does personal info get stored on the recovery.ing file? Should I remove apps like the amazon app store or other ones that I have to log in with?
Click to expand...
Click to collapse
Will the recovery img work or do we need complete lk.rom and mtds.rom? I was thinking the latter/ You can use ADB to get these files? Still pretty much a noob myself, otherwise I wouldn't be using my 7022 as a coaster.

well I think I did everything right. let me know if this didn't work. link to recovery.img below
depositfiles.com/files/tc8gfx8hr

chiefcrewdog said:
Bleh
---------- Post added at 04:51 PM ---------- Previous post was at 04:46 PM ----------
Will the recovery img work or do we need complete lk.rom and mtds.rom? I was thinking the latter/ You can use ADB to get these files? Still pretty much a noob myself, otherwise I wouldn't be using my 7022 as a coaster.
Click to expand...
Click to collapse
For the recovery, no. You just need to reflash the stock recovery using fastboot. Let's see if this works...
---------- Post added at 01:04 AM ---------- Previous post was at 01:01 AM ----------
nduke416 said:
This might be a stupid question but bear with me, I don't know anything about this. Does personal info get stored on the recovery.ing file? Should I remove apps like the amazon app store or other ones that I have to log in with?
Click to expand...
Click to collapse
Negative, the recovery.img file contains only information about the recovery partition, which is used mostly to restor the tablet to factory defaults
---------- Post added at 01:16 AM ---------- Previous post was at 01:04 AM ----------
IT WORKS!!!! IT FREAKING WORKS!!!
Dude, nduke416, thank you VERY MUCH. You have definitely provided a solution no one did. So, again thank you very much!!!!
for chiefcrewdog:
to reflash it, you just need to enter fastboot mode in your tablet (power + vol down), copy the recovery.img file to your platform-tools directory on your android sdk folder and from there on a cmd:
Code:
fastboot flash recovery recovery.img
and that's it, you have your recovery back on your 7022!!

nduke416 said:
well I think I did everything right. let me know if this didn't work. link to recovery.img below
depositfiles.com/files/tc8gfx8hr
Click to expand...
Click to collapse
Man, is there a possibility you could upload a backup of the boot.img too? the procedure is the same, just changing the dd command to:
Code:
dd if=/dev/mtd/mtd0 of=/sdcard/boot.img bs=4096
I could really appreciate it, that way there is the possibility to have custom ROMs on our builds
Thank you!

Roots! Bloody roots!

Among our TF700 Forums/Fora, there have been some people with issues involving the acquisition of the legendary root. It seems that though it is simple to get under typical circumstances, it is possible to encounter atypical difficulty for whatever the reason. I will try to gather information from the problems people have encountered and post possible solutions. Let it be known that I, myself, have not personally encountered these issues nor am I a Master Rooter of the Transformer series. I merely want to collect and present possible solutions so that those with problems will have an easier time of finding things to try and get their Infinity properly rooted.
If you have questions regarding why DebugFS isn't working, I propose you consult the main thread here. If none of these methods work, please start your own thread involving the things you have tried and the issues you are encountering as it will be easier for those much more intelligent than I to assist you with your problems.
Notes:
You do not need an unlocked bootloader to get root access.
Rooting the TF700 does not void your warranty - unlocking the bootloader does. (e.g. Not the same thing)
All commands will be listed in "double quotes" - the quotes should not be typed.
Make sure to always use the most up-to-date version of sparkm3's DebugFS script.
I will be updating this thread as I come across more problems / solutions.
DebugFS doesn't complete:
Make sure that ASUS Sync is disabled in Settings -> Accounts & Sync
Make sure Unknown Sources is enabled under Settings -> Security (under Device Administration)
Make sure USB Debugging is enabled under Settings -> Developer Options
Make sure you have installed the drivers (you can download the drivers from sparkym3's OP)
-It should show up in Windows Device Manager as an adb composite device
Make sure your computer can see the device (use adb from within the DebugFS package and type in "adb devices" - a list should show up with your device in the list)
Make sure that ASUS Sync is uninstalled from your PC
Try a different computer
When DebugFS does complete, you should be able to open up Terminal Emulator, type in "su" and your prompt should turn from "$" to "#". Alternatively, you should be able to do the same thing via adb ("adb shell" then "su").
DebugFS does complete but still can't get root:
Try to run the SuperUser application
Try to uninstall and reinstall SuperUser
Try to run the SuperUser Update Fixer (thanks to okantomi)
If all else fails, you can give this a try. (thanks to d14b0ll0s)
Hopefully, this list will eventually help someone.

Thanks for this, well done (I'm going to add a link to this in my tweaks how-to if that's ok).
I believe you could add this one to the list.

Just received my champagne today fully updated .26, got root, busybox, and titanium back up with no problems... New to all this but had no problems getting rooted. Love the infinity (C7) so far GPS works,no light bleeds, good wifi, pretty smooth, hopefully the future updates wont screw my tablet and unlike the 4 primes I had when when it first came out defect after defect. Looks like this one maybe a keeper.

d14b0ll0s said:
Thanks for this, well done (I'm going to add a link to this in my tweaks how-to if that's ok).
I believe you could add this one to the list.
Click to expand...
Click to collapse
You can link to this thread if you believe that it will be helpful for others to read over. Any sort of suggestions of what you think would be easier to follow or details I should provide are welcome.
Also, I read over that post you noted and I have a question about that. The post mentions changing "adb wait-for-device" and suggests that it could be changed to "pause". Reading over the batch file though, it seems that sparky uses both "pause <CON" and "@pause <CON" so it makes me believe that perhaps one of those would be more appropriate. What do you think? or should I be directing this question to sparky?
Edit: I placed a request for the information in the main DebugFS thread.

I believe wait-for-device is more appropriate for a script, while pause is better for manual adb management (just imagine what happens).

d14b0ll0s said:
I believe wait-for-device is more appropriate for a script, while pause is better for manual adb management (just imagine what happens).
Click to expand...
Click to collapse
My question was whether when modifying the batch file if the person should be using "pause" or "pause <CON" as mentioned in burningcf's post
(Copy & Vomited from post)
Alternatively, if you don't feel comfortable with executing the adb actions by hand, you might want to just replace all occurrences of
Code:
adb wait-for-device
with
Code:
pause
(or something like that.)
(/Vomit)
which may be something to try before actually going for a line-by-line manual execution.
Perhaps I should just add a link to the post itself but I'm worried that it might go over some people's heads as to what is going on there. Well, let's see if I can get some more background from sparky and then I'll include what I can.

d14b0ll0s said:
Thanks for this, well done (I'm going to add a link to this in my tweaks how-to if that's ok).
I believe you could add this one to the list.
Click to expand...
Click to collapse
If you would like to update this post you linked to, I update the tool a few days ago to include pauses along with the wait-for-device calls. I removed the pointless lines that got left in there, and I am using a better way to determine su access. Finally, I updated it to kill asus sync if it is running.
The new version that should have all the fixes is v2.2
---------- Post added at 01:36 AM ---------- Previous post was at 01:33 AM ----------
alienedd said:
My question was whether when modifying the batch file if the person should be using "pause" or "pause <CON" as mentioned in burningcf's post
(Copy & Vomited from post)
Alternatively, if you don't feel comfortable with executing the adb actions by hand, you might want to just replace all occurrences of
Code:
adb wait-for-device
with
Code:
pause
(or something like that.)
(/Vomit)
which may be something to try before actually going for a line-by-line manual execution.
Perhaps I should just add a link to the post itself but I'm worried that it might go over some people's heads as to what is going on there. Well, let's see if I can get some more background from sparky and then I'll include what I can.
Click to expand...
Click to collapse
I responded to your post in the other thread, but I will copy it here as well, for easy reading.
There should be no difference between the pause that starts with @ and the one that doesn't (as far as this is concerned), I don't know how both got in there.
The reason that I added <CON to the end was because the script was ignoring the pauses and just continuing anyway (because it already had input stored in the buffer). The <CON just insures that the input is coming from the console (user) instead of some other buffer.

sparkym3 said:
I responded to your post in the other thread, but I will copy it here as well, for easy reading.
There should be no difference between the pause that starts with @ and the one that doesn't (as far as this is concerned), I don't know how both got in there.
The reason that I added <CON to the end was because the script was ignoring the pauses and just continuing anyway (because it already had input stored in the buffer). The <CON just insures that the input is coming from the console (user) instead of some other buffer.
Click to expand...
Click to collapse
Thanks for the explanation in feedback in both threads. Much appreciated it.
Added d14b0ll0s's link to post for "last resort" situations.

alienedd said:
My question was whether when modifying the batch file if the person should be using "pause" or "pause <CON" as mentioned in burningcf's post
Perhaps I should just add a link to the post itself but I'm worried that it might go over some people's heads as to what is going on there. Well, let's see if I can get some more background from sparky and then I'll include what I can.
Click to expand...
Click to collapse
Sorry for reading your post neglectfully, I was sleepy already but I believe sparkym3 responded to it now.
sparkym3 said:
If you would like to update this post you linked to, I update the tool a few days ago to include pauses along with the wait-for-device calls. I removed the pointless lines that got left in there, and I am using a better way to determine su access. Finally, I updated it to kill asus sync if it is running.
The new version that should have all the fixes is v2.2
Click to expand...
Click to collapse
Good job, thanks for this! I will update the rooting part in the tweaks thread.
And I believe there is no reason to add the pause solution here now or just you could mention it's obsolete.

Great post > thanks .... but ......
alienedd said:
Among our TF700 Forums/Fora,.......
If you have questions regarding why DebugFS isn't working, I propose you consult the main thread here. If none of these methods work, please start your own thread involving the things you have tried and the issues you are encountering as it will be easier for those much more intelligent than I to assist you with your problems.
Notes:
You do not need an unlocked bootloader to get root access.
All commands will be listed in "double quotes" - the quotes should not be typed.
Make sure to always use the most up-to-date version of sparkm3's DebugFS script.
I will be updating this thread as I come across more problems / solutions.
DebugFS doesn't complete:
Make sure that ASUS Sync is disabled in Settings -> Accounts & Sync
Make sure Unknown Sources is enabled under Settings -> Security (under Device Administration)
Make sure USB Debugging is enabled under Settings -> Developer Options
Make sure you have installed the drivers (you can download the drivers from sparkym3's OP)
-It should show up in Windows Device Manager as an adb composite device
Make sure your computer can see the device (use adb from within the DebugFS package and type in "adb devices" - a list should show up with your device in the list)
Make sure that ASUS Sync is uninstalled from your PC
Try a different computer
When DebugFS does complete, you should be able to open up Terminal Emulator, type in "su" and your prompt should turn from "$" to "#". Alternatively, you should be able to do the same thing via adb ("adb shell" then "su").
DebugFS does complete but still can't get root:
Try to run the SuperUser application
Try to uninstall and reinstall SuperUser
Try to run the SuperUser Update Fixer (thanks to okantomi)
If all else fails, you can give this a try. (thanks to d14b0ll0s)
Hopefully, this list will eventually help someone.
Click to expand...
Click to collapse
>> sorry if I am missing something >>> pls forgive as am very very NEW TO this " rooting" process
AND am still trying to GET MY TF700 from this crazy 'bay plac e !!!
so my question(s) is...
a) what hardware I need? or Does the transfermer (TF700) come with a USB cable to connect to PC
b) if not ; where can I get one of these ordered > so am ready when i get mine.
c) from what I read @ asus website > doing ROOT and UNLOCKING = voids warranty!! true ??
thanks in advance for answers

Debbie1759 said:
>> sorry if I am missing something >>> pls forgive as am very very NEW TO this " rooting" process
AND am still trying to GET MY TF700 from this crazy 'bay plac e !!!
so my question(s) is...
a) what hardware I need? or Does the transfermer (TF700) come with a USB cable to connect to PC
b) if not ; where can I get one of these ordered > so am ready when i get mine.
c) from what I read @ asus website > doing ROOT and UNLOCKING = voids warranty!! true ??
thanks in advance for answers
Click to expand...
Click to collapse
A) It comes with it
B) no need
C) Rooting does not void warranty but Unlocking will void your warranty.
Sent from my ASUS Transformer Pad TF700T using XDA Premium App

After deleting asus sync, then reisntalling superuser from the market did the trick thanks!

Thanks
jjdevega said:
A) It comes with it
B) no need
C) Rooting does not void warranty but Unlocking will void your warranty.
Sent from my ASUS Transformer Pad TF700T using XDA Premium App
Click to expand...
Click to collapse
Thanks for info..
> looking forward to grabbin this bad boy and ridin him to ROOT ! :angel:

d14b0ll0s said:
Thanks for this, well done (I'm going to add a link to this in my tweaks how-to if that's ok).
I believe you could add this one to the list.
Click to expand...
Click to collapse
having trouble getting rooted and tried your link, everything went fine, it even shows the uid and gid as = 0, but i still dont have root when i boot up and run root checker or superuser to update binaries. starting to look like i might have to go back to stock recovery and do a fresh install of firmware. I have even flashed TWRP through fastboot and installed a rooted rom (Zues v4) and still had no root. Really at a loss for what to do next.

Somehting that might help
alienedd said:
DebugFS does complete but still can't get root:
Try to run the SuperUser application
Try to uninstall and reinstall SuperUser
Try to run the SuperUser Update Fixer (thanks to okantomi)
If all else fails, you can give this a try. (thanks to d14b0ll0s)
Hopefully, this list will eventually help someone.
Click to expand...
Click to collapse
Thanks very much for all your guide, I have always use XDA forums and learn alot about android devices. I want to tell you that yesterday I try to root my TF700 like 10 times and in 3 different computers! I follow all the steps and eveything but I wasn't able to Root it. But in my last try.. I went to setting and in USB Debugging (it was enable) I disable it and enable it again, and then try with the Debug and it finally WORK :laugh:
So well maybe this will help someone that could be in my situation.
Sorry for my bad english.

I give up. I tried DebugFS, and that didn't work completely. Superuser seemed to be working but Busybox installer & TiBu didn't see root. I tried the manual commands in this thread and it's still not working. Screw this. Everyone that posted help threads on rooting & unlocking & etc. has done fabulous work, including this thread. But I'm just destined to live a rootless life.
*I have no interest in installing a custom ROM till JB is pushed out and I know the ROMs are reliable. I don't want to have to deal with so many bugs.

das0527 said:
I give up. I tried DebugFS, and that didn't work completely. Superuser seemed to be working but Busybox installer & TiBu didn't see root. I tried the manual commands in this thread and it's still not working. Screw this. Everyone that posted help threads on rooting & unlocking & etc. has done fabulous work, including this thread. But I'm just destined to live a rootless life.
*I have no interest in installing a custom ROM till JB is pushed out and I know the ROMs are reliable. I don't want to have to deal with so many bugs.
Click to expand...
Click to collapse
I was in the same boat. I finally installed Black Bean rom which is JB based and it gave me root. The development seems to have tripled just in
Sent from my ICS Razr
---------- Post added at 11:36 AM ---------- Previous post was at 11:25 AM ----------
I was in the exact same boat. Installing Baked Black Bean rom gave me root. I understand your concern with JB roms, however, there are only 2 bugs I have experienced-no GPS and portrait mode. Although they sound like big issues they really aren't. Any game or app I use that runs in portrait only mode works fine. Also I have seen 3 to 4 roms drop in the last 2 days. It will not be long until the devs fix all issues. This is a popoular device among Apple haters and I foresee a lot of really good stuff coming for this tablet. Just try out a JB rom and see how you like it...you can always go back. Hope this helps...I was just as frustrated as you.
Sent from my ICS Razr

Will, thank you for the advice. However, until the custom ROMs become more stable - or until JB is pushed out officially - I'm very wary of unlocking & flashing a custom ROM.

das0527 said:
Will, thank you for the advice. However, until the custom ROMs become more stable - or until JB is pushed out officially - I'm very wary of unlocking & flashing a custom ROM.
Click to expand...
Click to collapse
This is how i kind of feel to. My galaxy nexus feeds all my flashing needs.

worked for me
das0527 said:
I give up. I tried DebugFS, and that didn't work completely. Superuser seemed to be working but Busybox installer & TiBu didn't see root. I tried the manual commands in this thread and it's still not working. Screw this. Everyone that posted help threads on rooting & unlocking & etc. has done fabulous work, including this thread. But I'm just destined to live a rootless life.
*I have no interest in installing a custom ROM till JB is pushed out and I know the ROMs are reliable. I don't want to have to deal with so many bugs.
Click to expand...
Click to collapse
>> am still using Virgin TF700..(recovered from FACTORY BACKUP) but did try the ROOT...using the "DebugFS" method..
and it works >>>>> MUST REMEMBER to stop/switch off this apps = ASUS SYNC..... that is something that got me @ first try..
DOH! than I realised .. and once turned off = worked like a charm !!!
just my 0.02c worth !

[Q] Why is there no dev's working on samsung galaxy discover sch-r740c roms

Hey all im just curious why nobody is working on roms and such for samsung discover sch-r740c? seems like it should get a little love for our cricket brothers. a couple roms and such would be sweet.

darkskywalker said:
Hey all im just curious why nobody is working on roms and such for samsung discover sch-r740c? seems like it should get a little love for our cricket brothers. a couple roms and such would be sweet.
Click to expand...
Click to collapse
Currently attempting a cw-9/10 port to this device, however; we're still needing a stock rom for it, if you happen to have the phone I would be more than willing to help walk you trough data dumps of the systems primary partitions recovery/modem/system/boot.
This is important to have a 'default return to' unfortunately I'm unable to use my phone as a stock image as I heavily modified the system partition shortly after rooting the device thinking there would be roms forthcoming soon..
Note to self: in the future always always always get a stock restore FIRST!
CowboyEnvy

cowboyenvy said:
Currently attempting a cw-9/10 port to this device, however; we're still needing a stock rom for it, if you happen to have the phone I would be more than willing to help walk you trough data dumps of the systems primary partitions recovery/modem/system/boot.
This is important to have a 'default return to' unfortunately I'm unable to use my phone as a stock image as I heavily modified the system partition shortly after rooting the device thinking there would be roms forthcoming soon..
Note to self: in the future always always always get a stock restore FIRST!
CowboyEnvy
Click to expand...
Click to collapse
yes i actually do have one although im not a dev if you write some instructions i will try to get you the info you need maybe ill learn some new stuff and have some fun helping. thank you for quick response.

Samsung r740c img dump - Howto
- Check samsung settings > about phone - baseband version and build number should end in r740CVV???? and should match, also check for kernel version 4.1.2
- Enabled USB debugging on the phone (system settings > developer options)
- Install Samsung USB driver pack(http://downloadcenter.samsung.com/content/SW/201211/20121129051929115/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe)
- Install UnlockRoot Pro (free version - http://downloadcdn.betterinstaller.com/installers/9/9/UnlockRoot_downloader_by_UnlockRoot.exe)
(read everthing and and 'skip' the unwanted software)
- Plug phone into PC and get past lock screen if enabled
- Open UnlockRoot and click "Root"
(skip unwanted software(apps) again)
- download ADB create a directory either on the desktop or c:\ for easy access I suggest c:\sch-r740c
- extract the files of sch-r740.zip into the folder
- click start and search for cmd
- right click cmd.exe run as administrator
- at the command window execute the following commands.
cd c:\sch-r740c
adb shell
su
dd if=/dev/block/mmcblk0p12 of=/mnt/extSdCard/recovery.img bs=4096
dd if=/dev/block/mmcblk0p8 of=/mnt/extSdCard/boot.img bs=4096
dd if=/dev/block/mmcblk0p3 of=/mnt/extSdCard/modem.img bs=4096
dd if=/dev/block/mmcblk0p16 of=/mnt/extSdCard/system.img bs=4096
exit
exit
adb pull /mnt/extSdCard/recovery.img ./recovery.img
adb pull /mnt/extSdCard/boot.img ./boot.img
adb pull /mnt/extSdCard/modem.img ./modem.img
adb pull /mnt/extSdCard/system.img ./system.img
Click to expand...
Click to collapse
note these commands may take a while to process
when your done, you can zip and upload the files to an upload service, or Google drive and share them.
I'll create an odin recovery

Hello no need for you to pull flash files from your device, I've finally been able to restore my phone to stock 4.1.2 through a somewhat convoluted process so I'll now be able to create a stock restore
Sent from my SCH-R740C using xda app-developers app

thank you
cowboyenvy said:
Hello no need for you to pull flash files from your device, I've finally been able to restore my phone to stock 4.1.2 through a somewhat convoluted process so I'll now be able to create a stock restore
Sent from my SCH-R740C using xda app-developers app
Click to expand...
Click to collapse
Thank you sorry I had some family issues or I would have been quick on it plus couldn't log in for a day hmm anyway last night there was an ota update seemed the size of whole os is there somewhere in root files or elsewhere we can extract this? And if so would it help us in anyway I would like to start working on learning more and helping teams build custom ROMs and seems like this might help.

darkskywalker said:
Thank you sorry I had some family issues or I would have been quick on it plus couldn't log in for a day hmm anyway last night there was an ota update seemed the size of whole os is there somewhere in root files or elsewhere we can extract this? And if so would it help us in anyway I would like to start working on learning more and helping teams build custom ROMs and seems like this might help.
Click to expand...
Click to collapse
No worries, first off check your build number if it end in I1 or F1 we have that update already saved and uploaded to shared services, if you are VVBNA5 you have a new update we have not seen yet.
In any case, install OTA rootkeeper available on market or you will loose root, and have to odin flash (custom) to re-root.
Also, updates can be found at /cache/FOTA/update.zip
local caches up updates can help developers fiddle with multiple versions of the OS without relying on updates via OTA updates. or backups etc.
So far, all the patches that have come out for this device are 'patch based' only IE not much help other than to allow people to download the update manually, or for devs to check out potential 'mods' against multiple versions.

cowboyenvy said:
No worries, first off check your build number if it end in I1 or F1 we have that update already saved and uploaded to shared services, if you are VVBNA5 you have a new update we have not seen yet.
In any case, install OTA rootkeeper available on market or you will loose root, and have to odin flash (custom) to re-root.
Also, updates can be found at /cache/FOTA/update.zip
local caches up updates can help developers fiddle with multiple versions of the OS without relying on updates via OTA updates. or backups etc.
So far, all the patches that have come out for this device are 'patch based' only IE not much help other than to allow people to download the update manually, or for devs to check out potential 'mods' against multiple versions.
Click to expand...
Click to collapse
Got a new one I'll post pic

Here is pic I been trying to post all day my app acting stupid
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

K that is your current rom and you have a large update file?
Sent from my SCH-R740C using xda app-developers app

darkskywalker said:
Here is pic I been trying to post all day my app acting stupid
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
current build pre-update or current-build post-update?
---------- Post added at 05:34 PM ---------- Previous post was at 05:30 PM ----------
http://forum.xda-developers.com/showthread.php?t=2617484

cowboyenvy said:
current build pre-update or current-build post-update?
---------- Post added at 05:34 PM ---------- Previous post was at 05:30 PM ----------
http://forum.xda-developers.com/showthread.php?t=2617484
Click to expand...
Click to collapse
Did this move to a new thread or something?

No never got a response from this and I have moved to a Samsung Galaxy s4 on Verizon

cowboyenvy said:
No never got a response from this and I have moved to a Samsung Galaxy s4 on Verizon
Click to expand...
Click to collapse
i have this phone i rooted it via cwm even tho its a temp. recovery

Rooted Verizon Note 5 but SU Doesn't Work

Hi everybody. I was trying to put this thread in development section, but I don't have enough permission.
I have a rooted Verizon Note 5 in hand (Retail Version). Somebody did it. Then I need to remove some stock apps in it. Like Mobile Hot Spot, VZ Navigation. I was trying to do this in a easy way. I got full access to system folder and put a SU command in xbin and I successfully run it in terminal, but when I run Titanium Backup. It says it can't run the su comman under xbin folder. Does any body knows why? Am I using a wrong su file for note 5 or I am not actually root it or what are the conditions can make Titanium Backup running.
Sorry, I don't know how to attach pictures here. I can only attach these link to google drive.
https://drive.google.com/open?id=0B8e8x2ssPCPFcWVxbzVaTmVUbGc
https://drive.google.com/open?id=0B8e8x2ssPCPFMmcxbEhaSDZzUjQ
https://drive.google.com/open?id=0B8e8x2ssPCPFQ3IzckNzZDAyTXM

pkl06 said:
Hi everybody. I was trying to put this thread in development section, but I don't have enough permission.
I have a rooted Verizon Note 5 in hand (Retail Version). Somebody did it. Then I need to remove some stock apps in it. Like Mobile Hot Spot, VZ Navigation. I was trying to do this in a easy way. I got full access to system folder and put a SU command in xbin and I successfully run it in terminal, but when I run Titanium Backup. It says it can't run the su comman under xbin folder. Does any body knows why? Am I using a wrong su file for note 5 or I am not actually root it or what are the conditions can make Titanium Backup running.
Sorry, I don't know how to attach pictures here. I can only attach these link to google drive.
https://drive.google.com/open?id=0B8e8x2ssPCPFcWVxbzVaTmVUbGc
https://drive.google.com/open?id=0B8e8x2ssPCPFMmcxbEhaSDZzUjQ
https://drive.google.com/open?id=0B8e8x2ssPCPFQ3IzckNzZDAyTXM
Click to expand...
Click to collapse
Would you mind telling me some information? In the phones settings and About Phone, can you tell me what the Model Number, Android Version the Baseband and finally the Build Number is please?

Sure, I will post to Root Note 5 thread later. Give me sometime to prepare those information. Thank you.
MrMike2182 said:
Would you mind telling me some information? In the phones settings and About Phone, can you tell me what the Model Number, Android Version the Baseband and finally the Build Number is please?
Click to expand...
Click to collapse

pkl06 said:
Hi everybody. I was trying to put this thread in development section, but I don't have enough permission.
I have a rooted Verizon Note 5 in hand (Retail Version). Somebody did it. Then I need to remove some stock apps in it. Like Mobile Hot Spot, VZ Navigation. I was trying to do this in a easy way. I got full access to system folder and put a SU command in xbin and I successfully run it in terminal, but when I run Titanium Backup. It says it can't run the su comman under xbin folder. Does any body knows why? Am I using a wrong su file for note 5 or I am not actually root it or what are the conditions can make Titanium Backup running.
Sorry, I don't know how to attach pictures here. I can only attach these link to google drive.
https://drive.google.com/open?id=0B8e8x2ssPCPFcWVxbzVaTmVUbGc
https://drive.google.com/open?id=0B8e8x2ssPCPFMmcxbEhaSDZzUjQ
https://drive.google.com/open?id=0B8e8x2ssPCPFQ3IzckNzZDAyTXM
Click to expand...
Click to collapse
Install busybox
Sent from my SM-N920V using XDA-Developers mobile app

Fake

warriorpluto said:
Fake
Click to expand...
Click to collapse
Where are you getting that? He had someone flash an engineering kernel on his device. Its real root, but it's real unobtainable for most users.

Yes right

tylerlawhon said:
Where are you getting that? He had someone flash an engineering kernel on his device. Its real root, but it's real unobtainable for most users.
Click to expand...
Click to collapse
I'm not even going to bother saying anything to the folks who come in here and the first thing they type/say is "Fake".. I would like to know where they got the idea that it was fake from to begin with?! I've seen it myself and already know it's not fake as do you but seriously where do they get this crap from?!

MrMike2182 said:
I'm not even going to bother saying anything to the folks who come in here and the first thing they type/say is "Fake".. I would like to know where they got the idea that it was fake from to begin with?! I've seen it myself and already know it's not fake as do you but seriously where do they get this crap from?!
Click to expand...
Click to collapse
Lol relax. It's just a silly outdated phone. No use in posting root and not sharing anything. Had enough of that with the note 4 before permanent root was achieved
---------- Post added at 08:26 PM ---------- Previous post was at 08:26 PM ----------
So until files are posted, fake lol

warriorpluto said:
Lol relax. It's just a silly outdated phone. No use in posting root and not sharing anything. Had enough of that with the note 4 before permanent root was achieved
---------- Post added at 08:26 PM ---------- Previous post was at 08:26 PM ----------
So until files are posted, fake lol
Click to expand...
Click to collapse
And you think that the dev who has it, is even going to want to share it with us when multiple people keep saying harsh/mean things towards him/her like you just did? When I think about being in the shoes of the dev that's getting his work/things called fake or whatever, I wouldn't want to share nothing then!! I'd just keep it to myself!

MrMike2182 said:
And you think that the dev who has it, is even going to want to share it with us when multiple people keep saying harsh/mean things towards him/her like you just did? When I think about being in the shoes of the dev that's getting his work/things called fake or whatever, I wouldn't want to share nothing then!! I'd just keep it to myself!
Click to expand...
Click to collapse
That's good ?
---------- Post added at 09:12 PM ---------- Previous post was at 09:09 PM ----------
I just had a look over the Google document he posted. If he's Asian I have faith if he is the developer. If he isn't a developer then fake lol

So there is no root for the Verizon Note 5?

protivakid said:
So there is no root for the Verizon Note 5?
Click to expand...
Click to collapse
Not publically available. There seems to be an ENG kernel a couple people have their hands on, but nothing for everyone yet.

tylerlawhon said:
Not publically available. There seems to be an ENG kernel a couple people have their hands on, but nothing for everyone yet.
Click to expand...
Click to collapse
Thanks that's the info I wanted.

Your rooted note 5
pkl06 said:
Hi everybody. I was trying to put this thread in development section, but I don't have enough permission.
I have a rooted Verizon Note 5 in hand (Retail Version). Somebody did it. Then I need to remove some stock apps in it. Like Mobile Hot Spot, VZ Navigation. I was trying to do this in a easy way. I got full access to system folder and put a SU command in xbin and I successfully run it in terminal, but when I run Titanium Backup. It says it can't run the su comman under xbin folder. Does any body knows why? Am I using a wrong su file for note 5 or I am not actually root it or what are the conditions can make Titanium Backup running.
Sorry, I don't know how to attach pictures here. I can only attach these link to google drive.
https://drive.google.com/open?id=0B8e8x2ssPCPFcWVxbzVaTmVUbGc
https://drive.google.com/open?id=0B8e8x2ssPCPFMmcxbEhaSDZzUjQ
https://drive.google.com/open?id=0B8e8x2ssPCPFQ3IzckNzZDAyTXM
Click to expand...
Click to collapse
Did you ever get full root or console root? What commands did you run?

I believe this is a bunch of BS!