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, since I do not have enough post count to ask in the superoneclick thread this is the next best thing.
When Superoneclick roots the phone regardless whether it succeeds or fails.
Will it attempt to remove the temporary files that it uses to write to root?
I'm asking this in the sense that, if it fails what will happen to the files being pushed to root? such as su and busybox, because rooting fails will the files stay there unused and filling up the nand?
Hello.
I am looking for some information on temporary rooting devices.
My current goal is to gain access to a root adb shell without actually modifying the device permanently. Be able to run a app with elevated privileges that will not modify the phone/tablet in any way and then exit and be back to stock with no changes to the device.
I have been looking at different oneclick root scripts and it seems across many different devices rageagainstthecage-arm5.bin is ran to gain root.
Does it do permanent changes at that point or does it just get access to a root shell to install busybox and su for permanent root after reboot?
If it is just used to gain a root shell, then my goal is to use this within a script to gain root access, run my app with elevated privileges and once finished, close out with no lasting effects to the device. So I will have to do the same process again if needing to run the app again.
If someone can comment on the process of gaining a root shell on android devices I would apprecaite it. I'm sure there is not a simple bin that can be ran on all 2.1 or newer devices but from the research I been doing tonight, seems it has been used on HTC's and Samsungs to gain root.
However if rageagainstthecage-arm5.bin does more than just hack itself root temporarly then that will not work for my issue.
If there is a different area in XDA Forums I should be asking this, please refer me there.
Greatly apprecaite all help on this.
MobileMedic
Just root it. Doesnt cause damage
Sent from my Nexus S using XDA App
Perm root would be the direct and simple answer to my needs. However it is not what we are looking for. I basically need to be able to remote control a device for the user and help them correct any issues they are having. There is no simple option for doing this as no one has written a "Log Me In" type app for android. And any that are written are for rooted phones. However, Mary-Jo and JimBob who call for help won't have rooted devices only stock. I am not allowed to root the devices because technically its voiding the warranty (even a flash back to stock would be just fine of a fix, but End Users are not that smart sometimes)
So having a Temp root option to be able to run remote control app is my only solution I can see at this time.
Any help would be greatly appreciated.
Hmmm. I root phones for customers as its my job. I understand a bit more where ur ciming from now.
sent from my boosted nexus S
i am hopeing someone can help me out here.
s4 mk2 build#
it seems i cannot update binaries on supersu that is stopping me from rooting my phone
Saferoot seemed like a no brainer just hit a couple keys and command prompts do everything so
I tried the saferoot way which i think half worked. the issue i am having is it seems i am stuck on trying to update supersu binaries. nomatter what i try it wont update.
i have tried thru the play store and downloading to my sd card. although on my card i must admit that i just didn't know which file to load being new to this.
in case those pictures dont show up
i downloaded root checker and it says
Check Command: ls-l ?system?bin?su:
Result: rwsr-sr-x root root 46596 2014-02-19 15:22su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can gain root access!
this leads me to believe i am pretty damn close right?
anyway could you give me a hint as to the way you rooted your phone?
or to someone else that doesn't mind noob questions like this.
Thank you for reading my breakdown and responding if you can.
Chris
Hi
cfh1030 said:
i am hopeing someone can help me out here.
s4 mk2 build#
it seems i cannot update binaries on supersu that is stopping me from rooting my phone
Saferoot seemed like a no brainer just hit a couple keys and command prompts do everything so
I tried the saferoot way which i think half worked. the issue i am having is it seems i am stuck on trying to update supersu binaries. nomatter what i try it wont update.
i have tried thru the play store and downloading to my sd card. although on my card i must admit that i just didn't know which file to load being new to this.
in case those pictures dont show up
i downloaded root checker and it says
Check Command: ls-l ?system?bin?su:
Result: rwsr-sr-x root root 46596 2014-02-19 15:22su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can gain root access!
this leads me to believe i am pretty damn close right?
anyway could you give me a hint as to the way you rooted your phone?
or to someone else that doesn't mind noob questions like this.
Thank you for reading my breakdown and responding if you can.
Chris
Click to expand...
Click to collapse
●●You have Knox Avoid Warranty?
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.