Hey that's cool! When I was typing the subject header the page showed me the "Here are the similar threads we found" bit. Unfortunately my mind is willing but my brain just ain't cutting it no more. Must be too many years using Windows.
I've looked around here and there seems to be a complete wealth of info for rooting, but unless I'm mistaken there seem to be bits here and there.
Is there a guide for grumpy 40something-year-old blokes who are rather rubbish at THIS SORT OF THING? Hell, I'd even PayPal for an idiots guide!
here:
http://forum.xda-developers.com/showthread.php?t=1367249
chrisrotolo said:
here:
http://forum.xda-developers.com/showthread.php?t=1367249
Click to expand...
Click to collapse
Aha, yes! I'll try this when the coffee has kicked in. Thansk very much for pointing me in the right direction.
Well, that appeared to have worked. At least, I didn't brick the device, and it's rebooted fine.
Actually, how does one test that the device is rooted? Has anyone asked that before?
Well that worked! It needs to be rooted to run SuperUser and Titanium, right? Well they both run so it mus tbe rooted
Grumpy Old Guys Unite!
bittersound said:
Is there a guide for grumpy 40something-year-old blokes who are rather rubbish at THIS SORT OF THING? Hell, I'd even PayPal for an idiots guide!
Click to expand...
Click to collapse
Congratulations from a 50something-year-old analog-minded geek for rooting your 6210. Sounds like we might be in the same boat. Old codgers (soon to be curmudgeons) hanging on by our fingertips to the bleeding edge of technology. All I can say about these forums is read everything before you do anything. And then ask some smart questions to make sure you're on the right track. You won't piss off too many of the rom-boffins this way, and you might avoid bricking your Tab. Good luck and welcome to the google/android/samsung version of our future.
Re: If your rooted
bittersound said:
Actually, how does one test that the device is rooted? Has anyone asked that before?
Click to expand...
Click to collapse
1. Download a program called SManager in the play store.
2. open it up and click on options at the bottom and click on console.
3. Shell will open and type the following...
su <cr>
whoami <cr>
what you get back should either be... "root" or unknown uid 0
if you get anything other then you are not rooted.
Hope this answers your question
Dave.
bittersound said:
Well, that appeared to have worked. At least, I didn't brick the device, and it's rebooted fine.
Click to expand...
Click to collapse
Aha, it turns out it DID NOT work.
I followed the root procedure with no error message, the tablet rebooted just fine but SManager returns "unknown uid 0", which indictes the device is not rooted.
To add to the confusion, Titanium Backup Pro says "OK (BusyBox 1.18.4-Titanium from app) with a lovely tick next to "Root access:"
Seems like the device is confused, at least as much as me...
bittersound said:
Aha, it turns out it DID NOT work.
I followed the root procedure with no error message, the tablet rebooted just fine but SManager returns "unknown uid 0", which indictes the device is not rooted.
To add to the confusion, Titanium Backup Pro says "OK (BusyBox 1.18.4-Titanium from app) with a lovely tick next to "Root access:"
Seems like the device is confused, at least as much as me...
Click to expand...
Click to collapse
Huh... I have a similar confusion. Titanium Backup also tells me "OK (BusyBox 1.18.4-Titanium from app). I've cleaned Samsung bloatware off the Tab successfully using adm which I assume I wouldn't be able to do if I wasn't rooted. Yet File Manager tells me I don't have root permission to use their advanced root settings.
rtfm1777 said:
Huh... I have a similar confusion. Titanium Backup also tells me "OK (BusyBox 1.18.4-Titanium from app). I've cleaned Samsung bloatware off the Tab successfully using adm which I assume I wouldn't be able to do if I wasn't rooted. Yet File Manager tells me I don't have root permission to use their advanced root settings.
Click to expand...
Click to collapse
To confuse matters even more, I appear to have succesfully put the QMGBBQRQM Final Release ROM on the tablet
Have you installed superuser from the market yet? If you already have installed superuser, then check if theres an update for superuser. Sometimes that helps apps to recognize that you have root.
bittersound said:
Is there a guide for grumpy 40something-year-old blokes who are rather rubbish at THIS SORT OF THING? Hell, I'd even PayPal for an idiots guide!
Click to expand...
Click to collapse
From another "40 something"... Read the sticky thread called "** FAQ and useful info **" at the top of the general subforum.
This "grumpy 40-something" spent quite a bit of time gathering the links and text for that post, and it really gets people grumpy when others (such as yourself) appear too lazy to read it.
Gary (the sarcastic, grumpy, 40-something year old diva)
Still going with that diva title eh? lol but you do have a point also. I check it from time to time myself.
re:
bittersound said:
Aha, it turns out it DID NOT work.
I followed the root procedure with no error message, the tablet rebooted just fine but SManager returns "unknown uid 0", which indictes the device is not rooted.
To add to the confusion, Titanium Backup Pro says "OK (BusyBox 1.18.4-Titanium from app) with a lovely tick next to "Root access:"
Seems like the device is confused, at least as much as me...
Click to expand...
Click to collapse
"unkown uid 0" is root. If you get this you are root'd and are good to go.
you need to have super user running when you start up titanium backup and if you get the pop up window saying titanium backup wants root access then you are definitely root'd.
Dave.
garyd9 said:
This "grumpy 40-something" spent quite a bit of time gathering the links and text for that post, and it really gets people grumpy when others (such as yourself) appear too lazy to read it.
Click to expand...
Click to collapse
I did check out the FAQ, clearly I missed the relevant details for whatever reason - let's blame it on newbiestupidity. Laziness was not involved, thank you very much.
Related
First off, this is where I got all the below info: (kudos and good job!)
http://forum.xda-developers.com/showthread.php?t=1005292
Ok. So I just rooted my Thunderbolt using these instructions:
http://forum.xda-developers.com/attachment.php?attachmentid=552281&d=1301123842
This download:
http://www.megaupload.com/?d=28H4U0QS
And this download (if windows 64 bit):
http://www.mediafire.com/?nbm7bpa0lnqp3si
Download the megaupload files first and unrar them. If using Windows 64 bit, download the mediafire files and unrar them into the Thunderbolt Root folder that was just unrared and replace the files it asks to replace.
Use the PDF instructions to start.
A couple of corrections which I came across...may not be the same for all rooters:
First,,,make sure you take off "fast boot" as suggested.
For step one, I had to redo step one for reboot to go forward but that worked as stated.
In "Before Step 2", under the "Note", you will see "After flashing hbooteng.nb0 your phone will reboot". Actually, for me, it was the next step of flashing the "PG05IMG.zip" which it then rebooted. These kind of things get you a bit worried at the moment if everything doesn't go as written
At the end of the rooting, when you "Click on Step 3", My phone immediately rather than the phone sitting there as stated, showed that "You have been successfully rooted...congratulations" -- without rebooting the phone. What I did was the suggestion to close the rooter.exe and restart it and then click on step three again and Presto, same message but the phone rebooted into root
The suggestion to go to clockwork mod is go to all programs and open ROM Manager and do the same...haha...I couldn't find "clockwork"..I was looking for it for about 2 minutes All went well, all permission ran and I rebooted and all is good!
All in all, nice directions and pretty user friendly...Thanks all!!!
thanks for the notes im thinking of rooting my phone and all the extras of people doing it and saying how good it is helps alot when trying to decide if i really want to do it or not.
spunry said:
thanks for the notes im thinking of rooting my phone and all the extras of people doing it and saying how good it is helps alot when trying to decide if i really want to do it or not.
Click to expand...
Click to collapse
I can think of no reason to NOT root this phone.
spunry said:
thanks for the notes im thinking of rooting my phone and all the extras of people doing it and saying how good it is helps alot when trying to decide if i really want to do it or not.
Click to expand...
Click to collapse
No problem. Love to help make it easier for anybody
How's this working for you all??
Sent from my ADR6400L using XDA Premium App
Forgive me for intruding, but there are already excellent guides on how to root in the development page. http://forum.xda-developers.com/forumdisplay.php?f=943
Please route people here, as I am sure this is based off of Team AndIRC's work (including, but not limited to jcase, the original poster of the root method.) and it in no way credits them
Shady stuff.
IISiDeK1CKII said:
... this is based off of Team AndIRC's work (including, but not limited to jcase, the original poster of the root method.) and it in no way credits them
Shady stuff.
Click to expand...
Click to collapse
Thanks! Just updated my initial post
I am rooting AS we speak using the one click method from XDA post, everything is working so far I am at the point where it says " This process may take some time "
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
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 !
Does anyone know if Z4Root will work on this tablet? Thanks!
I've been looking for one for 3 days now, I tryed onclickroot and z4root or something like that,, cant find anything Anyone please help!!
I'm still waiting for my tablet to be delivered...I'm gonna try SuperOneClick (crosses fingers)
I got one of these for my daughter for xmas. I spent a few days trying to root it with no luck. I'm not intimately familiar with android (some unix experience), but I tried all the options I could find for rooting Allwinner a10 devices. At first I ran into problems with adb unable to recognize the device for most one-click methods. I downloaded the android tools and was able to connect with the included adb. After studying the scripts, they all use the "adb root" command to gain root access on the device and copy the necessary files. Unfortunately, this command fails using adb from the tools. At first I thought this was due to my adb version, but after doing some research I think it is actually due to the device kernel. I believe it requires reflashing or some exploit to be able to gain root. I was able to install root explorer and I can browse all the necessary directories but I can't modify or copy the necessary files into them. Busybox told me there was an older version installed, but wouldn't let me install a newer version (again I think due to the permissions). Also, superuser would say it installed but the su binary did not show up on the bin directory. As the necessary directories are all owned by root, I couldn't figure out a way to modify the permissions...
I wound up returning the FileMate and got a Lenovo IdeaTab. Got that rooted in no time.
sorry i never saw this post i've bought 2 of these and i rooted them,
i wish i could get a better build for them though, too many app crashes and the internet connectivity sucks
i used a method by Bin4ry called root with restore, v17 worked any ways i have the zip if you would like it
ferny_dx said:
sorry i never saw this post i've bought 2 of these and i rooted them,
i wish i could get a better build for them though, too many app crashes and the internet connectivity sucks
i used a method by Bin4ry called root with restore, v17 worked any ways i have the zip if you would like it
Click to expand...
Click to collapse
Screw it, here it is for future reference.
How'd you do it!?!?
ferny_dx said:
Screw it, here it is for future reference.
Click to expand...
Click to collapse
FileMate Clear T720
Thank you very much for being the only person ever to have posted in regards to this tablet. I just got mine for christmas and have been trying to get it rooted. I've tried a lot of those one-click methods, and I've even tried this Bin4ary method. but it just hangs up on "daemon started sucessfully*"
Can you please direct me to the filemate drivers (if needed)
also, I have usb debugging endable, allowing 3rd party (not secure) files enabled. and pulling my hair out (enabled).
Thanks again.
Also, I'm running windows 7 and 8, (((maybe i should try win7))) hmm. i'll get back to you on that. Anyhow, any advice would be greatly appreciated, since returning it doesn't sound very fun.
jiberish05 said:
FileMate Clear T720
pulling my hair out (enabled)..
Click to expand...
Click to collapse
I laughed so hard. ok your going to have to install drivers by force,
first off do you happen to have android sdk installed? if you don't there is another way but its going to sound weird,
if you do have the android SDK installed:
1. go to your computer manager (by opening explorer, right click on the "computer" group on the left column and select manager)
2. look for any unrecognized item that appears, ( it will most likely be labeled "Clear" with a faded icon and a "?" sign on top
3. right click and choose "Update drivers", it will give you options, choose "Browse my computer for driver software", another option screen will show,
4. at the bottom of the window there will be an option that says "let me pick from a list of device drivers on my computer"
5. on the screen that appears there should be an option that says "ADB Interface", choose this
6. choose "Google, Inc.">"ADB Testing Interface version x.x.x.x" (I chose version 2.1.0.0)
that should do it next time you plug in the tablet try running ddms or open the cmd and type in "adb devices" (assuming you have adb installed) and it should show.
if this helps just hit the thanks button
[edit] I am running windows 8 btw [/edit]
ADB interface doesn't show up
Thank you very much for getting me farther, however I dont see ADB interface. I'm looking into it right now. I just re-installed the sdk drivers and will keep at it.
BTW, is it even worth doing this? the main reason I want to do it, is so i can connect my ps3 remote via bluetooth, and possibly a little overclocking. Have you had any luck OC it?
Thanks again Much appreciated:good:
jiberish05 said:
Thank you very much for getting me farther, however I dont see ADB interface. I'm looking into it right now. I just re-installed the sdk drivers and will keep at it.
BTW, is it even worth doing this? the main reason I want to do it, is so i can connect my ps3 remote via bluetooth, and possibly a little overclocking. Have you had any luck OC it?
Thanks again Much appreciated:good:
Click to expand...
Click to collapse
open up SDK manager and go to Extras>"Google USB Drivers"
also install everything in the "Android 4.0 (API 14)" section, I have other options installed if this still doesn't work.
its worth it just for the extra stuff that root comes with like titanium backup, but you cant over clock, if you go any higher than 1200 MHz it will lock up and you have to force it to reset.
cyberkeeper1 said:
HERE is the link to root as provided earlier
Click Here to download ADB universal drivers. they should work better than the google USB drivers.
---------- Post added at 12:20 AM ---------- Previous post was at 12:11 AM ----------
this seems kind of spammy. What backs up my claim is that you dont have more than 5 posts...
Click to expand...
Click to collapse
Thanks for the link to my post on android central, the link in that post just comes back the xda thread
Root MANY ANDROID! [Upd: 20.11.2013] - Added Z1 Root
Sent from my XT862 using Tapatalk
Rooted Filemate Clear
I just wanted to confirm I have also rooted the Clear with the Bin4ry v33 exploit using option 1. Although I received the following error:
remote object '/system/bin/ric' does not exist
.
Going to copy files to it's place
Rebooting again, please wait!
Could Not Find C:\Documents and Settings\Graham School\My Documents\Downloads\Ro
ot_with_Restore_by_Bin4ry_v33\ric
Restoring previous Backup! Please select the RESTORE MY DATA option now on your
device!
SuperSu installed and root apps working.
Rooted With Kingo
I just bought one of these cheap to play with and used Kingo to root it. Worked first time, no problem. The only issue I am having is that the SuperSu binaries are failing to update but root is still working. Titanium is working and Root Explorer so I can debloat. Hope that helps is anyone is still trying to use these
Jfender1005 said:
I just bought one of these cheap to play with and used Kingo to root it. Worked first time, lem. The only issue I am having is that the SuperSu binaries are failing to update but root is still working. Titanium is working and Root Explorer so I can debloat. Hope that helps is anyone is still trying to use these
Click to expand...
Click to collapse
please tell me where in the world you got the Kingo root?
As far as being unable to update binaries, try to find a custom recovery and install. From there, you can inject them via su-binary update.zip and bam!
Kingoroot
cyberkeeper1 said:
please tell me where in the world you got the Kingo root?
As far as being unable to update binaries, try to find a custom recovery and install. From there, you can inject them via su-binary update.zip and bam!
Click to expand...
Click to collapse
http://www.kingoapp.com/android-root.htm
That is the link for the Kingo site. The first time I saw it on here there was some question about whether it was safe becase it is not open source and used a Chinese SuperSu app. I felt safe using it on a tablet because I do no banking on it or anything, but the newest posts I have seen are that Kingo is safe. Hope that helps. And if you know where to find a custom recovery that will work with this app please let me know.
Below you will find instructions how to root this device.
The following procedure has been tested up to firmware J120AUCU2APJ2
KNOX should remain 0x0
However you undertake this at your own risk.
Issues:
Wifi passwords not remembered (fix below)
Stock Flashlight app not working.
Model number may be missing from build.prop (fix below)
Instructions
1. Flash the eng boot image.
This is a special boot image normally used by engineers, it allows selinux to be booted in permissive mode with relaxed root restrictions.
Do not replace this image with the stock image after rooting your device or you will possibly soft brick your device.
(See below for how to recover)
ENG_BOOT_J120A_PG1
Download Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Download the ENG_BOOT_J120A_PG1.tar to your PC and add it to AP / PDA in ODIN.
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
2. Install and run Kingroot:
http://www.apkmirror.com/apk/kingro...-release/kingroot-5-0-5-android-apk-download/
You may need to run Kingroot several times to gain successful root.
3. Install and run SuperSU me to remove Kingroot and convert to SuperSU (not required) :
https://play.google.com/store/apps/...ore&pcampaignid=APPU_1_uzPDVbGyFcGNyATHrqmoCA
Alternative (free) method to replace Kingroot:
Follow Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Don't flash the boot partition with Flashfire, uncheck.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware. Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
4. Wifi fix:
modify the line below in /system/build.prop:
ro.securestorage.support=true to false
5. To fix “Unauthorized actions have been detected”
disable 'security log agent'
6. Model number missing fix:
http://www.techgainer.com/change-fake-android-device-model-number-and-brand-name/
Enjoy your rooted device
To recover from a soft brick flash the firmware below.
https://firmwarefile.com/samsung-sm-j120a
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Still no TWRP, though, right?
fbueller said:
Still no TWRP, though, right?
Click to expand...
Click to collapse
Not possible I'm afraid.
ashyx said:
Not possible I'm afraid.
Click to expand...
Click to collapse
As ashyx mentioned in a previous post, Flashfire works. Loaded Xposed for Samsung via the Wa?? version.
spicybeansandricey, to clarify, Wanam is a modified version of Xposed for Samsung phones. Google is my friend, Google is your friend and Google is our friend. If you Googled it, you will find links to the same/similar packages linked by ashyx to get Xposed on Samsung phones. Since I was skimming the articles and successfully installed on a 4" screen, I wasn't sure about the name but only remembered the first 2 letters. In fact, the tutorial I followed was different from ashyx's post and gave no credit to XDA.
As an addendum, Flashfire works great and was able to back up EFS files. I just chose to backup EVERYTHING since I don't know what I will need later. My 128GB sd card cost more than the phone! LOL As for my vacation reading list and Google, I still have to read up on new superuser and root that can survive OTAs and root detection.
shirleys143 said:
Flashfire works. Loaded Xposed for Samsung via the Wa?? version.
Click to expand...
Click to collapse
Yeh flash fire is pretty much the next best thing to custom recovery with a few little tricks of its own.
Anyone have a list of garbage that can be safely removed? Even after stripping some of the obvious stuff there's over 4Gb of system stuff.
Can I remove the Samsung stuff like Galaxy Apps and such? I don't want to remove anything that will make it unstable so that I can still reset it back to fresh and begin over, but without the bloat ware of that makes sense?
ViralThread said:
Anyone have a list of garbage that can be safely removed? Even after stripping some of the obvious stuff there's over 4Gb of system stuff.
Can I remove the Samsung stuff like Galaxy Apps and such? I don't want to remove anything that will make it unstable so that I can still reset it back to fresh and begin over, but without the bloat ware of that makes sense?
Click to expand...
Click to collapse
No matter how much you remove from system the size will never change, it's rather a pointless exercise. All you're doing is creating unused space.
ashyx said:
Yeh flash fire is pretty much the next best thing to custom recovery with a few little tricks of its own.
Click to expand...
Click to collapse
SO i tried to flash xposed via flashfire and got the old "system software not authorized by at&t has been found on your phone..." brick.
How to get xposed on there without bricking?
ashyx said:
No matter how much you remove from system the size will never change, it's rather a pointless exercise. All you're doing is creating unused space.
Click to expand...
Click to collapse
So what's the point of rooting? The primary reason was to remove the bloat and recover some usable space on the device. Out of 8GB there's less than 3gb of usable storage on it rendering it mostly useless for anything but a media player or emulator box loading crap off the SDCard.
What a waste.
ViralThread said:
So what's the point of rooting? The primary reason was to remove the bloat and recover some usable space on the device. Out of 8GB there's less than 3gb of usable storage on it rendering it mostly useless for anything but a media player or emulator box loading crap off the SDCard.
What a waste.
Click to expand...
Click to collapse
Rooting is about more than debloating. It's about having control over your device.
Why don't you use adoptable storage if you need more space?
You can always move user apps to system to take up the space you've created. There are plenty of apps that can do this such as system app remover. That way not only do you utilise that space but you also free up storage space.
spicybeansandricey said:
SO i tried to flash xposed via flashfire and got the old "system software not authorized by at&t has been found on your phone..." brick.
How to get xposed on there without bricking?
Click to expand...
Click to collapse
How do you class a message, which is easily removed, as a brick?
ashyx said:
Rooting is about more than debloating. It's about having control over your device.
Why don't you use adoptable storage if you need more space?
You can always move user apps to system to take up the space you've created. There are plenty of apps that can do this such as system app remover. That way not only do you utilise that space but you also free up storage space.
Click to expand...
Click to collapse
Adoptable storage is useless. Most of the apps will not see it and refuse to install data there, making it impossible to install anything large on the device or more than a few small apps/games.
I hadn't considered moving installed apps to system space I will give system app removed a glance. Thx
ashyx said:
How do you class a message, which is easily removed, as a brick?
Click to expand...
Click to collapse
i just asked how to install xposed on there, who cares about what i feel is a brick or not. a brick, soft or hard is still a brick.
is there a way to get xposed on the j120a without custom recovery? i tried flashfire, maybe my setting were incorrect? do you have a method?
thanks in advance.
spicybeansandricey said:
i just asked how to install xposed on there, who cares about what i feel is a brick or not. a brick, soft or hard is still a brick.
is there a way to get xposed on the j120a without custom recovery? i tried flashfire, maybe my setting were incorrect? do you have a method?
thanks in advance.
Click to expand...
Click to collapse
Yes there is, but due to your attitude sort yourself out. I honestly don't know why I bother sometimes with this forum.
ashyx said:
Yes there is, but due to your attitude sort yourself out. I honestly don't know why I bother sometimes with this forum.
Click to expand...
Click to collapse
thats kind of harsh considering i just asked for instructions on how to get xposed on my phone. instead of helping you wanted to put me down for not using the word "brick" in a manner thats acceptable to you.
im sorry that we dont agree on semantics. i really have no "attitude" and how one can attribute an attitude to text on a website is debatable at best.
I have no ill-will, malice, or attitude, i had a general question that i was asking about and was looking to someone who looked like they had the answer for it. Normally, i "sort" these things out myself, but i went against my better judgement and asked here...(hence my 2 reply post history.)
if you can help me, i would gladly reward you for your time, via bitcoin, etc; I honestly have no issue other than i dont have the time to sit and look into this stuff like i use to 4-5 years ago. I promise you, i have no sort of attitude. this is just a forum FFS, and above all else, im not an 'ingrate.' i am always appreciative for any help that i receive.
If you could find the will to help me i would greatly appreciate it, otherwise lets not part ways with any ill-will, that's the last thing that i would ever want to happen.
thanks again for your time.
Ok so here's what my experience with system app remover was, and I hope I wasn't sounding rude or unappreciative, Immsimply trying to work towards a certain endpoint solution if possible.
System app remover did not permit me to relocate user apps into system space, in fact it won't let me move any apps as it claims "sdcard share the same disk with os", both in "move to phone" and in "move to sdcard" options.
Is there any reliable way to install apps directly to the external SDCard? Maybe install them to internal storage and then manually move them and symlink them? That wouldn't work for large apps but might allow installation of more smaller apps?
Essentially what you've stated means even the system is on its own "partition" right? So as I remove stuff that's stored in the /system folder, it's freeing space but not space my Android can access for the purpose of installation ?
Is that a proper summary of my situation?
Thanks in advance
spicybeansandricey said:
thats kind of harsh considering i just asked for instructions on how to get xposed on my phone. instead of helping you wanted to put me down for not using the word "brick" in a manner thats acceptable to you.
im sorry that we dont agree on semantics. i really have no "attitude" and how one can attribute an attitude to text on a website is debatable at best.
I have no ill-will, malice, or attitude, i had a general question that i was asking about and was looking to someone who looked like they had the answer for it. Normally, i "sort" these things out myself, but i went against my better judgement and asked here...(hence my 2 reply post history.)
if you can help me, i would gladly reward you for your time, via bitcoin, etc; I honestly have no issue other than i dont have the time to sit and look into this stuff like i use to 4-5 years ago. I promise you, i have no sort of attitude. this is just a forum FFS, and above all else, im not an 'ingrate.' i am always appreciative for any help that i receive.
If you could find the will to help me i would greatly appreciate it, otherwise lets not part ways with any ill-will, that's the last thing that i would ever want to happen.
thanks again for your time.
Click to expand...
Click to collapse
OK, let's start again. Maybe I mistook your response, it just seemed a little snipey. To get help in the right direction, proper details of what the actual issue is goes a long way to obtaining the solution. Stating a message caused a brick isn't anything I've ever come across before which is why I asked the question? However it seems further to that post you actually meant Xposed caused the brick after you saw that message and rebooted.
So going back to what I previously stated about correct details, here we are 3 unnecessary posts later.
Moving on...to install Xposed you need to ensure you use the wanam build of Xposed.
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
.
ashyx said:
OK, let's start again. Maybe I mistook your response, it just seemed a little snipey. To get help in the right direction, proper details of what the actual issue is goes a long way to obtaining the solution. Stating a message caused a brick isn't anything I've ever come across before which is why I asked the question? However it seems further to that post you actually meant Xposed caused the brick after you saw that message and rebooted.
So going back to what I previously stated about correct details, here we are 3 unnecessary posts later.
Moving on...to install Xposed you need to ensure you use the wanam build of Xposed.
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
.
Click to expand...
Click to collapse
thank you so much!! that was what the "wa???" was in the first few post of this thread that i didnt understand. i sincerely was not trying to come off as pompous, snipey etc; so thank you for helping me. I run a vbulletin forum myself so im no stranger to miscommunication.
I appreciate your help, honestly and sincerely. ill give this a try and be back, my sincerest thanks again.
ViralThread said:
Ok so here's what my experience with system app remover was, and I hope I wasn't sounding rude or unappreciative, Immsimply trying to work towards a certain endpoint solution if possible.
System app remover did not permit me to relocate user apps into system space, in fact it won't let me move any apps as it claims "sdcard share the same disk with os", both in "move to phone" and in "move to sdcard" options.
Is there any reliable way to install apps directly to the external SDCard? Maybe install them to internal storage and then manually move them and symlink them? That wouldn't work for large apps but might allow installation of more smaller apps?
Essentially what you've stated means even the system is on its own "partition" right? So as I remove stuff that's stored in the /system folder, it's freeing space but not space my Android can access for the purpose of installation ?
Is that a proper summary of my situation?
Thanks in advance
Click to expand...
Click to collapse
Whoops, my bad. That's was the wrong app to suggest. I actually meant this one that DOES move user apps to system. You can see the mistake with the similar names!
https://www.google.co.uk/url?sa=t&s...CBowAA&usg=AFQjCNFe58rupOZgD6hS3UfXr-2rkHxsyQ[/url]
By the way I suggest this busybox:
https://www.google.co.uk/url?sa=t&s...CB8wAg&usg=AFQjCNGS1LQ2kB8PZ4Y--lzVTOG1SKQWvA
ashyx said:
Whoops, my bad. That's was the wrong app to suggest. I actually meant this one that DOES move user apps to system. You can see the mistake with the similar names!
https://www.google.co.uk/url?sa=t&s...CBowAA&usg=AFQjCNFe58rupOZgD6hS3UfXr-2rkHxsyQ[/url]
By the way I suggest this busybox:
https://www.google.co.uk/url?sa=t&s...CB8wAg&usg=AFQjCNGS1LQ2kB8PZ4Y--lzVTOG1SKQWvA
Click to expand...
Click to collapse
Thanks for the quick response.
I installed /system/app/remover and it seemed to offer a solution. However upon moving few apps to system with the app, it's merely removing them. So more tweaking needed.
Will keep update on progress.
Thanks again
---------- Post added at 03:53 PM ---------- Previous post was at 03:29 PM ----------
Is it safe to remove all of the Samsung stuff? Will that break the reset ability?