Related
I just got one of the new Galaxy Indulge 4G phones and tried rooting it.
BusyBox installer is telling me that the phone is rooted however it is nand locked.
and ideas on how to unlock nand on this phone?
How did you root it?
Thaxx said:
How did you root it?
Click to expand...
Click to collapse
SuperOneClickRoot.
Yeah i tried adb, super one click, and zroot. None of them worked, and for some reason everytime i try to start up root explorer, it crashes trying to get super user. I've tried all means of forcing super user to get onto the phone. No matter what it wont work. Mike thinks its Nand locked. Another thing i noticed is when I used super one click, i had two options at the top right hand corner that looked like names of my device. I can get my serial number with adb, and it shows it. Another darn problem is no drivers are out for this phone yet. Also have no idea of the LTE chip is interfering with this either. So come one come all dev and droid guru's help us out!
So basically I think this means we a need a custom recovery, flash image and stuff. Bah, that'll probably take like a month
K, also tried visionary rooting, which did some wierd ****. I rebooted and it seemed like i had root, but super user still didn't work. It fooled a couple programs into thinking i had root, but it would not let me "touch" the files on the phone. Even though it claimed I had r/w permission.
Silvist said:
Yeah i tried adb, super one click, and zroot. None of them worked, and for some reason everytime i try to start up root explorer, it crashes trying to get super user. I've tried all means of forcing super user to get onto the phone. No matter what it wont work. Mike thinks its Nand locked. Another thing i noticed is when I used super one click, i had two options at the top right hand corner that looked like names of my device. I can get my serial number with adb, and it shows it. Another darn problem is no drivers are out for this phone yet. Also have no idea of the LTE chip is interfering with this either. So come one come all dev and droid guru's help us out!
Click to expand...
Click to collapse
The Samsung Epic 4G drivers worked for me, also tried the rooting process used on the Epic whoever busybox says im rooted but that nand is locked, i downloaded Terminal emulator and it says im not rooted, also installing superuser not possible, I was able to install root explorer but not any good if doesnt let me delete the bloatware only read.
Yeah, busybox says the phone is rooted but nand locked.
superuser app was added to system/apps. however im not able to mount system/apps with R/W from root explorer. The rooting process seems to gain access to r/w the files but the apps cant.
seems 4G still have far distance from us...
Supposedly there's a work around for Nand locked, but the first one didn't work for me.
With the absolutely beautiful ADB exploit I use, titled rageagainstthecage (ratc), absolute ALL devices can be rooted. This is because it exploit is ADB which all devices use. There is an issue though. Some devices have a NAND lock which does not allow you to write to the /system mount. Because of this, you can’t copy su, sqlite or busybox to /system/bin. This creates some issues but there is a work around. For things that don’t need access to /system (like enabling non-market apps) I can use the ratc exploit to make those changes. If your device cannot use su in /system/bin then you can simple select a checkbox (as of v1.5) that says to use ratc.
Click to expand...
Click to collapse
This didn't work still for me. So the only other option was unrevoked, but when I went to the site, it listed only HTC. Kinda confused how using HTC roms is a work around for a samsung phone lol. Still need some master guru's help on this stuff.
I too have been trying and am unable to get nand unlocked, I would really love some other ideas. Anyone out there able to help?
I'm waiting 'till the $50 MIR on the 1st, then I'll jump in with both feet.
Some guy suggested to shell root > perm root > restart device. That doesn't work either. I also noticed something called "media scanner" that scans as the phone boots up, i wonder if that's preventing any modified files.
If anyone knows how NAND unlocking has worked for other phones (and im not just talking about what apps to run or what room to use) please contact me so that we can try a few things out and hopefully get a full root for everyone.
Supposedly Mr. Parker rooted:
http://forum.xda-developers.com/showthread.php?t=803682&page=260
I'm asking him through both post and through private message if he could elaborate. Apparently he had trouble with getting Win 7 x64 to work, but it worked with Win Xp. I'm still not sure what drivers he used, and he said he had it not in debug mode. I tried in non debug, and my phone wouldn't even register. So hopefully he'll expand on how he did it. If not, back to the drawing boards, at least till we get a real pro in here.
Got my hopes up that even though we dont have full root yet, I would be able to get rid of the bloatware.
The SuperOneClick is able to get read/write access and send commands to the phone so I opened Root Explorer on the phone and then rand the superoneclick. As soon as the program mounted the phone with Read/Write I started clicking on the Mount R/W button in root explorer until it showed the app as having read/write access to the system/app directory. I tried deleting the Iron Man app and it said it was deleted successfully.
but then I checked and the app was still there loading root explorer agian then showed that the file was still there and had not been deleted.
Wow you managed to get root explorer to work? Mine just tries to obtain root, and crashes everytime i start it up now. I've tried to unroot, and uninstall and reinstall it. I used Linda manager to view the files on the phone, but like you if i deleted they would return on boot. That's why I think metro or samsung has some kind of media scanner that scans at start up, and it somehow reinstalls files, or prevents root. Can't confirm this yet because super user fails ;/
I've been trying also to get root. Programs often will think i have root access. as far as adb is concerned i do have root access till i dont something that requires it. I've been able to install root manager and look through some files. Im under the impression metro or samsung did install something odd, though im not sure the media scanner is it. Also the phone does not require root in order to install other-market software.
What do you mean programs "think" you have root? You mean you have super user? And what "programs" are you referring to? You can install root manager without a root yes, but in order to put it into "r/w" mode and delete the files from the phone itself, such as bloatware, you need root and Super user access. Most people here I hope are aware that you don't need to root to install "MOST" apps. There "is" apps that require root, and you cannot run them without root access.
Such as:
Titanium backup
Set CPU
Why do I want to root is like everyone keeps saying, to delete all the metro apps, and have "full" manufacturer control over the phone. That's the whole point of rooting. So far no one has rooted this phone PERIOD, or at least shown proof they were even able to. So any info you find regarding rooting please post it here.
Alright, so I tried what Mr. Parker did, and no go. Whether I ran super one click on Win 7 x64 (which was all in admin) or win xp, it would not install super user. In fact I noticed a couple of the files copied from super one click were already on the phone, and weren't able to be overridden. Which may relate to nand lock.
Hello xda, I have a bit of a problem:
I have a Samsung Exhibit which I rooted using the zergRush method found here on the forums. At first everything worked fine. But recently I was trying to push a modified system app to my phone using adb and it told me the action wasn't permitted. Checking the shell, and terminal emulator on my phone to see if I had superuser permissions failed. So I went about trying to root my phone again, which according to the zergRush script said was successfull, but checking the shell once again showed that I still did not have superuser permissions. I did a factory wipe of my phone in hopes of trying to get it to root again with no success. But here's the weird part, although it doesn't appear I have root access all my apps that require root access (titanium backup, my screenshot app, and some of widgetlocker's features) still fully function.....
Does anyone have any idea what's going on here? I would love my system folder access back
Thanks in advance.
Dumb question, but your H-Boot shows S-Off? Just covering the bases... Also, do you have Super User installed and functional?
To be honest... I don't know what H-Boot or S-Off means. Pretty new to all of this. Mind giving me a walkthrough? I have superuser installed yes. It's granting programs superuser permissions. But I can't access su in terminal emulator or in the shell.
Well, I'm not the top tier technical person here, so I'm not exactly sure on how to get your problem resumed, since I've not heard of that. On the other hand, there might be a different way to accomplish what you are trying to do.
What are you trying to achieve, pushing a modified system app to do what and where? My suggestion, might be to just put it on your phone through USB to the root folder and then move it in ES File manager, or w/e you use. If all you are doing is pushing.
Obviously ADB shell detects your device, but I'm not sure why it is saying it doesn't have SU access. My other suggestion is to redo the ADB/Android SDK installs. I had a problem where I installed them wrong, by installing too much and ADB did not work properly. So, there might be a chance your phone is fine, but the ADB/SDK are not proper, somehow.
Let me know.
If that were the case, and my phone was fine, wouldn't I be able to access super user through terminal emulator on my phone? Right now when typing su in terminal emulator, the pop up to grant superuser permissions appears but when you allow it to have su permission the # doesn't turn to a $ like it should. The more I think about it the more I think it's a problem with superuser. I've seen people talking about an update to superuser that can break your root? Mehhhh.
Seems like other have had this problem too... Not sure if a nandroid recovery will fix this, otherwise you might have to try to unroot, and then reroot.
Sorry, just might have to do a little more digging than I was able to. Good luck
I've read the dedicated thread on rooting the TF700t with DebugfsRoot_v1.9 (http://forum.xda-developers.com/showthread.php?t=1706588&page=48).
I did successfully root a TF700t with 9_4_5_22.
Now I tried the same method after upgrading another TF700t from stock to 9_4_5_26.
Everything works fine during rooting (I've tried both manual and automated DebugfsRoot 1.9) with the following exceptions:
1. during the 3rd stage of rooting, I get
/system/bin/sh: /system/xbin/su: not executable: magic 7F45
2.
Superuser access does not seem to be active after rooting. I did uninstall and re-install Superuser with no superuser access success.
I tried both under XP and 7/32 on the same device, no errors but root does not seem to be active. Between rooting attempts, I restored stock ROM.
Other details:
Asus USB drivers installed (off Asus website)
Asus synch is disabled and prevented from launching.
Security/Unknown sources is checked.
Developer options / USB debugging is ON/checked.
What do you think goes wrong?
Any help is appreciated. Thx
the same..
I have nearly the same problem...
I have updated my rooted .21 to .26, then unlocked it and as it seems have lost root. I dont really know if it happened afted updating or afted unlocking...
None of my R-applications can get root, and so on...
I've tried to use the same method i used to get root on .21 and got this:
Step 2 - Rooting...
debugfs 1.42 (29-Nov-2011)
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs:
debugfs: debugfs: Allocated inode: 1469
debugfs: debugfs: debugfs: debugfs:
Rebooting...
Testing superuser...
uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),
1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
uid and gid should both be 0.
Are they? (y/n):
Click to expand...
Click to collapse
And still no root...
What am i doing wrong? What to do next?
Thanks!
Is it a superuser problem?
EnginesRun said:
2.
Superuser access does not seem to be active after rooting. I did uninstall and re-install Superuser with no superuser access success.
Any help is appreciated. Thx
Click to expand...
Click to collapse
Can't help yet but I am having a similar problem with SU; its presence suggest I have root but it denies everyone else SU permissions...
After rooting, run SuperUser explicitly from the applications menu. Then try your apps that require root access. I noticed that I had the issue of running the DebugFS root batch and then later was not able to properly run Adaway. Ran SuperUser, then everything went smooth.
I think someone already mentioned this in another thread.
alienedd said:
After rooting, run SuperUser explicitly from the applications menu. Then try your apps that require root access. I noticed that I had the issue of running the DebugFS root batch and then later was not able to properly run Adaway. Ran SuperUser, then everything went smooth.
I think someone already mentioned this in another thread.
Click to expand...
Click to collapse
nope. doesnt help in my case..
---------- Post added at 10:17 AM ---------- Previous post was at 09:37 AM ----------
ok, i've solved my problem.
the idea mentioned by alienedd helped me to see that i could have a working root but faulty superuser app.
so i started with installing it from market.
then i ran DebugfsRoot_v1.9.
till it got to this point:
Testing superuser...
uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(m ount),1011(adb),
1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),30 03(inet),3006(net_bw_stats)
uid and gid should both be 0.
Are they? (y/n):
Click to expand...
Click to collapse
then i have cleared all the data held by superuser app through settings\apps, stopped it and uninstalled.
after that i continued with the script and it installed me superuser app again.
after installing i've launched it and then ckecked my root-needed apps. they are ok now.
Ahhh, yeah. Read about that in the DebugFS thread that sometimes one needs to uninstall superuser then reinstall for it to run properly. Didn't think about that. Glad that its all working now for yas.
I have tried all of this with 4 different packages (3 of the automated root from here and 1 from a link in the [RESOURCES] thread in the dev forum. every time, each package says that I have root, but when I check I do now. I followed what masseselev said and it failed as well. I have spent the better part of 5 hours trying to root. I guess I should say that I just got my infinity last night...and like a crackhead applied .26 ota without thinking about it. but I have read where the automated works fine with .26. I am pulling my hair out trying to figure out why I cant get root on this thing. the packages always say that they were successful and that I have root, but I do not. no apps can gain root. terminal emulator still shows $ after trying to enter "su". I have tried several different root checkers and they all say I do not have root. any other ideas? I should also say that I have not unlocked the bootloader.
henbone11 said:
I have tried all of this with 4 different packages (3 of the automated root from here and 1 from a link in the [RESOURCES] thread in the dev forum. every time, each package says that I have root, but when I check I do now. I followed what masseselev said and it failed as well. I have spent the better part of 5 hours trying to root. I guess I should say that I just got my infinity last night...and like a crackhead applied .26 ota without thinking about it. but I have read where the automated works fine with .26. I am pulling my hair out trying to figure out why I cant get root on this thing. the packages always say that they were successful and that I have root, but I do not. no apps can gain root. terminal emulator still shows $ after trying to enter "su". I have tried several different root checkers and they all say I do not have root. any other ideas? I should also say that I have not unlocked the bootloader.
Click to expand...
Click to collapse
What exactly are you doing as its kind of hard to determine what has gone wrong?
DebugFS works with .26 OTA and you don't need an unlocked bootloader for it to work (though having root might cause problems for getting OTAs and the unlocker to work).
alienedd said:
What exactly are you doing as its kind of hard to determine what has gone wrong?
DebugFS works with .26 OTA and you don't need an unlocked bootloader for it to work (though having root might cause problems for getting OTAs and the unlocker to work).
Click to expand...
Click to collapse
just trying to run the debugFS automated tool. it runs fine, and gives all indications that it works successfully. but I still dont have root. its driving me crazy. I have run 2.0, 2.1 and 2.2 packages and all said I was rooted...but I dont think I am. I have installed and uninstalled superuser and rebooted numerous times. I went ahead and unlocked the bootloader and it still wont work. I can open a command prompt from within the package folders (2.0, 2.1 and 2.2) and run adb shell, then su and it shows #. but if I do it from terminal on the infinity it shows $ when i do su. sorry if im vague, im just brain fried at this point and dont know what else to do.
henbone11 said:
just trying to run the debugFS automated tool. it runs fine, and gives all indications that it works successfully. but I still dont have root. its driving me crazy. I have run 2.0, 2.1 and 2.2 packages and all said I was rooted...but I dont think I am. I have installed and uninstalled superuser and rebooted numerous times. I went ahead and unlocked the bootloader and it still wont work. I can open a command prompt from within the package folders (2.0, 2.1 and 2.2) and run adb shell, then su and it shows #. but if I do it from terminal on the infinity it shows $ when i do su. sorry if im vague, im just brain fried at this point and dont know what else to do.
Click to expand...
Click to collapse
Yeah, I understand. Um, I know I've repeated this several other times but I don't see it in your list of things you've done. Were you able to open up the superuser application? It seems that if it opens, you have root, and in some cases might not work until it is opened. It's both fortunate and unfortunate that I did not encounter many problems while rooting so my experience with possible errors isn't that expansive. However, you've run the package(s) completely so it's not a driver issue and you can adb and see su access. It just seems like the tablet isn't recognizing that it does have it.
yeah, I ran superuser immediately after rooting. then rebooted each time. http://forum.xda-developers.com/showpost.php?p=29951628&postcount=494
lol thats everything that I have tried. kinda sucks, but im sure someone will figure it out at some point.
weird thing is, if I run a command prompt from within the package folders I see that its rooted. if I run terminal on the device it says permission denied and prompt is still $. just odd.
I'm sure that sparky can give you help in the main thread as he has a whole lot more knowledge about the possible failings. Also, read over some of the other threads here as there seem to be quite a few people with errors that I don't even understand why they are happening. Maybe a something like simply the drivers? http://forum.xda-developers.com/showpost.php?p=29974269&postcount=9
Other then that, I'm at a loss bud. Do mention the fruits of your research though as I'm sure it would definitely be helpful to others.
alienedd said:
I'm sure that sparky can give you help in the main thread as he has a whole lot more knowledge about the possible failings. Also, read over some of the other threads here as there seem to be quite a few people with errors that I don't even understand why they are happening. Maybe a something like simply the drivers? http://forum.xda-developers.com/showpost.php?p=29974269&postcount=9
Other then that, I'm at a loss bud. Do mention the fruits of your research though as I'm sure it would definitely be helpful to others.
Click to expand...
Click to collapse
yeah, we have been trying to figure it out...no joy. I have seen quite a few people with the same issue. hopefully someone can sort out why its happening soon. even if I cant root, at least knowing why would somewhat appease me.
henbone11 said:
yeah, we have been trying to figure it out...no joy. I have seen quite a few people with the same issue. hopefully someone can sort out why its happening soon. even if I cant root, at least knowing why would somewhat appease me.
Click to expand...
Click to collapse
Perhaps this then?
d14b0ll0s said:
Perhaps this then?
Click to expand...
Click to collapse
Ok, I followed this http://forum.xda-developers.com/showpost.php?p=28519641&postcount=11 and was successful in rooting mine and my gf's infinity's.
one thing though. after manually rooting, after the final reboot, go into the Superuser app. DO NOT UPDATE IT FROM WITHIN THE APP. for some reason, updating from within Superuser borks the app. at least it did for mine and my gf's.
optional:
close Superuser. go to the play store and download busybox installer (needed to run titanium backup), root checker (there are a ton, just pick one of the top ones), adaway, ota rootkeeper and titanium backup. doesnt matter what order. I would run busybox installer first though once you have everything installed. after busybox installs, you can run root checker, adaway or titanium to check root. I say after you install busybox because some apps do require busybox to be installed before they consider you rooted. if you get the superuser prompt to allow/deny, everything is working fine. once you know that you have root and everything is working ok, run ota rootkeeper.
my only question at this point is regarding OTA updates. to my understanding, simply rooting will allow you to continue to receive OTA updates, but unlocking the bootloader will prevent you from getting OTA updates...is this correct?
OK I have run the pie exploit about 100 times every time I get the correct output but when I use root checker it says I don't have root I try to install super su and it says there are no binaries installed what am I missing my device shows up I put the update package in my sdk folder advice pushes the files I reverted back to 19.5.3 I get the exact same message that is expected when everyone else runs pie please help I have a Verizon Droid mini do I need to disable fire walls or avg
ojodetigre said:
OK I have run the pie exploit about 100 times every time I get the correct output but when I use root checker it says I don't have root I try to install super su and it says there are no binaries installed what am I missing my device shows up I put the update package in my sdk folder advice pushes the files I reverted back to 19.5.3 I get the exact same message that is expected when everyone else runs pie please help I have a Verizon Droid mini do I need to disable fire walls or avg
Click to expand...
Click to collapse
I got the same error messages. Get Root Check, and ignore the errors, and once it's sent, see if that works. It doesn't allow you to update the binaries though, until you do the full root with the WPnomo described in the Pie thread
Elaborate
livinitwarrior said:
I got the same error messages. Get Root Check, and ignore the errors, and once it's sent, see if that works. It doesn't allow you to update the binaries though, until you do the full root with the WPnomo described in the Pie thread
Click to expand...
Click to collapse
So I got root checker it says I am not rooted so your telling me that I should just ignore everything and run the full root process because everyone else says that root checker should say I'm rooted is there any other programs I need besides sdk I read somewhere that I need Java setup correctly to execute scripts and also I read that I may have to create a junk file on my phone that will allow the scripts to be pushed to I'm so lost I am about to give up someone please help me out I'm new member so I can't post in development
ojodetigre said:
So I got root checker it says I am not rooted so your telling me that I should just ignore everything and run the full root process because everyone else says that root checker should say I'm rooted is there any other programs I need besides sdk I read somewhere that I need Java setup correctly to execute scripts and also I read that I may have to create a junk file on my phone that will allow the scripts to be pushed to I'm so lost I am about to give up someone please help me out I'm new member so I can't post in development
Click to expand...
Click to collapse
You need to make sure everything like your firewall, avg, security is all turned off or it won't work.
Rooted Droid Ultra
ojodetigre said:
So I got root checker it says I am not rooted so your telling me that I should just ignore everything and run the full root process because everyone else says that root checker should say I'm rooted is there any other programs I need besides sdk I read somewhere that I need Java setup correctly to execute scripts and also I read that I may have to create a junk file on my phone that will allow the scripts to be pushed to I'm so lost I am about to give up someone please help me out I'm new member so I can't post in development
Click to expand...
Click to collapse
sorry, I never got a notification from this. No, root checker SHOULD tell you if you have root. Are you running each of the 4 commands separately?
livinitwarrior said:
sorry, I never got a notification from this. No, root checker SHOULD tell you if you have root. Are you running each of the 4 commands separately?
Click to expand...
Click to collapse
I plug my phone in, cd to the path of my sdk, adb devices to make sure it's recognized then run the four commands separately and phone does nothing it doesn't reboot just stays the same run root checker and it says I'm not rooted the guy before you says to turn avg and firewalls off I'm going to try that when I get home
ojodetigre said:
I plug my phone in, cd to the path of my sdk, adb devices to make sure it's recognized then run the four commands separately and phone does nothing it doesn't reboot just stays the same run root checker and it says I'm not rooted the guy before you says to turn avg and firewalls off I'm going to try that when I get home
Click to expand...
Click to collapse
Reboot? It shouldn't reboot. The phone should technically do nothing until you do root checker. The way this root works, it's tethered, and gets wiped once you reboot unless you do the next steps of using wpnomo
Sent from my XT1080 using XDA Premium 4 mobile app
Just asking a little thing. USB debugging enabled?
Rooted Droid Ultra
Pie alone isn't going to give you the root that you are looking for. All Pie does is give you root access to the /system partition.
You need to go here: http://bit.ly/1sxDN9t and disable Write Protection, which will allow you to flash the SU binary that gives full root.
After that is done you need to install Safestrap ((Can be found here: http://bit.ly/1jq4WeO) Our device is the XT1080), reboot into recovery and flash: http://download.chainfire.eu/396/SuperSU/
Now when you boot up you will have permanent root, and root check / SuperSU should show up properly.
Through OTA?
miketoasty said:
Pie alone isn't going to give you the root that you are looking for. All Pie does is give you root access to the /system partition.
Click to expand...
Click to collapse
Will root access survive through an OTA update to 4.4.4?
joshs997 said:
Will root access survive through an OTA update to 4.4.4?
Click to expand...
Click to collapse
Yes after you do all the steps and buy SuperSu pro and enable survival mode to be able to update and keep root
Rooted Droid Ultra
joshs997 said:
Will root access survive through an OTA update to 4.4.4?
Click to expand...
Click to collapse
Root survives but write protection gets disabled. So the root is basically useless.
I've never really had to use adb much before on any of my other devices. It's eating my lunch, and is frustrating because everyone is saying how easy it is. I honestly am having issues simply pushing the pie exploit to my phone. When I do, all correct directories, it gives me the adb info and shortcut stuff, definitions, etc. Any help would be appreciated. Just don't know adb well at all.
Edit: nm. got it.
Has anyone created a method to root Acer a1-713 manually?
Those one click methods are really crude also I don't even know what's happening in there.
If anyone knows it please help me.
Dreadful man said:
Has anyone created a method to root Acer a1-713 manually?
Those one click methods are really crude also I don't even know what's happening in there.
If anyone knows it please help me.
Click to expand...
Click to collapse
Some said that Kingroot worked for them in this Q&A thread -> http://forum.xda-developers.com/chef-central/android/root-recovery-acer-iconia-tab-7-a1-713-t2851573
JnFrks said:
Some said that Kingroot worked for them in this Q&A thread -> http://forum.xda-developers.com/chef-central/android/root-recovery-acer-iconia-tab-7-a1-713-t2851573
Click to expand...
Click to collapse
Well it didn't for me. Also I want to know what I am doing with my tab and not just know that tapping this button will root my tab.
Have you ever tried to look at this site -> http://www.oneclickroot.com/device/acer-iconia-a1-713/. They featured this one-click rooting and it seems they can be trusted. I've downloaded and installed their software so no worries. Well, I'm also using a one-click root utility and it's always working. (just sayin')
The process of rooting a device is too complicated for those who don't have knowledge in Linux (like me), so your question about manually is out.
http://www.oneclickroot.com/device/acer-iconia-a1-713/
Well this one click root website was also a waste of time and didn't work either .
I may have to wait a little bit more before dumping this thread.
Rooting an android device basically means (for me) granting You (as the user) to do whatever you want to your device's system, hardware, etc. But what does root will actually do to your device that will cause you to obtain that superuser access? It's because of the "su" (Switch User) file used by Android and other UNIX-based systems that allows a process of switching of a user to be the superuser (or root user) that has access to the commands and file system, meaning those processes that requires root permission (root access or superuser access) need to invoke su. So basically the process of rooting will just push this su, a binary executable file, to the file system so that you can switch to the root user to give root permissions... And the Superuser application is just optional, but really required for some reasons, it serves as the "gatekeeper" of the su binary so when a certain command or application that invokes su will prompt the user by the Superuser app first before granting the root permission since becoming the root user can do whatever to the system which means it can cause the device to malfunction, etc... So what do you mean by manually?
Sorry for what I'd just suggest you that OneClickRoot waste your time...
Oh, there's a bad news after spending time searching how to root your device, read the news here -> [GUIDE] Firmwares, ROMs, CWM, Root - Acer Iconia (MTK) Tablets [ⒶⒸⒺⓇ ⒹⒺⓋⒾⓁⓈ]
Can't find a best way to root your Acer.
Well thanks for enlightening me on the topic, I hadn't really understood what really is su..
By manually I meant by using computer and tinkering with the files hands on.
Oh, and you needn't to be sorry since everything I tried didn't work. Sometimes I had root till the app was open while sometimes it existed until the next reboot.
Also looked at the link you gave and well, what can I say, it really is bad news and there sure is the risk of bricking my device.
Well thanks for taking your time.