Does SOC root or qkster GB install ADB?? - Samsung Infuse 4G

Adb appears in the list of programs on my phone viewed within the program "network monitor" (not transferring data, but in that program list). Note that adb doesn't show in my app drawer or settings/ installed apps list.
Is this normal? I don't think I did anything to install it, unless it was installed by soc root or qkster's 2.3.6 stock package.
The reason I installed network monitor...picked up my phone the other day and turned on display and saw superuser root access request screen briefly, even though I had been doing nothing with the phone except torn the screen on.. That request screen went away before i could fully digest it, but I thought the program requesting access was "Elixir widgets"...which doesn't require root access (although does have a ton of permissions since it's a "do-everything" widget program). I then opened su program, Went to su log tab, and there wss no su request for elixir in there... Nor any recent requests from any program. Maybe I imagined it, but i'm a little suspicious I have some malware or spy ware since I saw that unusual root request.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2

I should clarify, I'm not concerned about soc our qkster's package...rather i'm curious about adb. Is it normal to have adb on my phone after setting up my phone with soc and qkster's package.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2

It appears you are running stock 2.3.6?
If so, you are seeing the adb daemon which is launched by the kernel. You will find that in /sbin.
This service supports the adb connection between PC and phone. To disable from phone OS, turn off USB debugging in Settings-->Applications-->Development. Note that with the custom GB kernels, adb is enabled by default in recovery mode.
JB, specifically 4.2.2, provides a higher level of security in this area. I posted some info on this in Scott's CM10.1 thread.

electricpete1 said:
I should clarify, I'm not concerned about soc our qkster's package...rather i'm curious about adb. Is it normal to have adb on my phone after setting up my phone with soc and qkster's package.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Pete,
(shhhhhh) don't tell anyone I installed that daemon...it's suppose to gather all your personal info and send it to THIS GUY

Related

Files used to root Atrix 2 ICS (4.0.4) AT&T

Can someone share with me the files that you use to root your Atrix on ICS? I know Jim had them up at some point in time but he took down all the files because some people were bootlooping.
Posting her to show that I, too, would like those files.
Here u go ics root for atrix 2 http://db.tt/BpZ7UH3B
Sent from my MB865 using xda app-developers app
About root
Hello, can you explained, how can I do for install the root on my atrix 2 whit ICS
elgeorge_rp said:
Hello, can you explained, how can I do for install the root on my atrix 2 whit ICS
Click to expand...
Click to collapse
Plug in the usb cable to your phone. Use a back port on your com. Then set check "unkown sources" under system settings > Security & Screen lock. Then set USB debugging on. You can find that under system settings > Developer options. Once you've done that, Unzip and run the appropriate file for your system. IE: windows or mac.
REMEMBER! WE HAVE NO WAY TO GO BACK TO GINGERBREAD AT THE MOMENT!!!!!!!!!!!!!! AND TRYING TO HAS CAUSED BRICKED PHONES!!!!!!!!!!!!
ALSO, during the rooting process, your phone will reboot several times, so don't be alarmed ..
Fall of Enosis said:
Plug in the usb cable to your phone. Use a back port on your com. Then set check "unkown sources" under system settings > Security & Screen lock. Then set USB debugging on. You can find that under system settings > Developer options. Once you've done that, Unzip and run the appropriate file for your system. IE: windows or mac.
REMEMBER! WE HAVE NO WAY TO GO BACK TO GINGERBREAD AT THE MOMENT!!!!!!!!!!!!!! AND TRYING TO HAS CAUSED BRICKED PHONES!!!!!!!!!!!!
Click to expand...
Click to collapse
Can we not reflash stock gb on atrix 2
Got official ICS ota update. I have the stock GB setup and RSD lite. Have used to flash rom in the past. But have not done it after the ICS. Will it not work???? Also aftr ICS battery consumption is high. 80% eaten up by just the display..
Note : mobile data is inactive. Display to auto and no widget, except quick contacts and power widget. Any solution.
chayan18885 said:
Got official ICS ota update. I have the stock GB setup and RSD lite. Have used to flash rom in the past. But have not done it after the ICS. Will it not work???? Also aftr ICS battery consumption is high. 80% eaten up by just the display..
Note : mobile data is inactive. Display to auto and no widget, except quick contacts and power widget. Any solution.
Click to expand...
Click to collapse
You have posted in the wrong thread..please post your question in Q&A..a guide for best battery life is available in the atrix 2 section itself..do search..
Sent from my MB865 using xda app-developers app
The main question is about can i revert back to GB after ICS.
The main question is the first part. My bad for posting two question of diff category. I have ICS and will i able to flash it back to stock? Dnt want to risk doing it. Have anyone tried it???
If you are on any other leak but the first one then, no, you cannot flash back from ICS. See here for more info:
http://forum.xda-developers.com/showthread.php?t=1882335
Sent from my SAMSUNG-SGH-I727 using xda premium
last questn
I'm on OTA ICS asia version. Not a atnt phone. Will the above root work, (hope no issue later on) ?
Also will it be possible to unroot and remove traces of root. As the method i knw is to flash stock rom back. But as i have ota ics, which is not revertibl. What can be done...
Sent from my MB865 using xda app-developers app
Should be fine. See my info thread for more info. You can get all the threads and download links there: http://forum.xda-developers.com/showthread.php?t=1882335
And yes you can unroot.
Sent from my SAMSUNG-SGH-I727 using xda premium
Fall of Enosis said:
Plug in the usb cable to your phone. Use a back port on your com. Then set check "unkown sources" under system settings > Security & Screen lock. Then set USB debugging on. You can find that under system settings > Developer options. Once you've done that, Unzip and run the appropriate file for your system. IE: windows or mac.
REMEMBER! WE HAVE NO WAY TO GO BACK TO GINGERBREAD AT THE MOMENT!!!!!!!!!!!!!! AND TRYING TO HAS CAUSED BRICKED PHONES!!!!!!!!!!!!
Click to expand...
Click to collapse
Hey can u elaborate a little more, because i run it and noting. Mac user.
No Superuser permission even after rooting ...
Hi, I have two ATT Atrix 2 MB865 phones. Both are on OTA ICS. I tried to root them using A2_ICS_root and the process went fine but when I try check if phone rooted properly, I am getting <Application name> has been denied Superuser permission. I can see Superuser app in app drawer but I think both the phones couldn't root properly. I did enable USB debugging and Unknown sources. I tried to set USB mode to Charge Only but couldn't find it anymore.
Now how can I correct it or remove files which root process put in my phone? Please help!
sony108 said:
Hi, I have two ATT Atrix 2 MB865 phones. Both are on OTA ICS. I tried to root them using A2_ICS_root and the process went fine but when I try check if phone rooted properly, I am getting <Application name> has been denied Superuser permission. I can see Superuser app in app drawer but I think both the phones couldn't root properly. I did enable USB debugging and Unknown sources. I tried to set USB mode to Charge Only but couldn't find it anymore.
Now how can I correct it or remove files which root process put in my phone? Please help!
Click to expand...
Click to collapse
You need to go into the superuser app, and in settings there is a way to tell it to auto accept su requests, enable that, then go right back and set it back to always ask, then go and update the binary for su in the other tab in the superuser app. you just click on the su binary and update it from there.
After you do that, you should be ok, I think.
jimbridgman said:
You need to go into the superuser app, and in settings there is a way to tell it to auto accept su requests, enable that, then go right back and set it back to always ask, then go and update the binary for su in the other tab in the superuser app. you just click on the su binary and update it from there.
After you do that, you should be ok, I think.
Click to expand...
Click to collapse
Hi! I followed your advice and now both of my phones are successfully rooted and setting Superuser permission
Thanks you so much :thumbup:
Sent from my MB860 using Tapatalk 2
Tried thus file along with the other one from the other root ics thread also to no avail
Sent from my MB865 using Tapatalk 2
root after ICS update
i had my atrix2 rooted when in GB.i updated it to ICS via OTA and now it isn't rooted anymore (and i'm not sure about this but i read it somewhere).
can anyone tell me how to re-root in ICS?
root Atrix 2 ICS (4.0.4)
Fall of Enosis said:
Plug in the usb cable to your phone. Use a back port on your com. Then set check "unkown sources" under system settings > Security & Screen lock. Then set USB debugging on. You can find that under system settings > Developer options. Once you've done that, Unzip and run the appropriate file for your system. IE: windows or mac.
stevenfreestyler : Sorry. I have a little confusion here. Please help out. "Once you've done that, Unzip and run the appropriate file for your system. IE: windows or mac" - Is the execution of the root app need to be done on the PC while the usb cable is connected to the phone or once the files are unzip, transfer it to the phone, disconnect the usb cable from the phone and execute the root file from within the phone? Done both ways but couple of restarts you've mentioned didn't take place so i guess I've done something wrong some where. Please do advise. thank you
Click to expand...
Click to collapse

[ROOT][TOOL][2012-07-24] GS3DebugFSRoot: Root the Verizon GSIII without flashing

THIS WILL NOT WORK WITH JELLY BEAN.
---
Here's a easy-to-use tool based on the method in this thread.
If you like this tool, please click the Thanks button!
Even better, see my signature.
DISCLAIMER: As with any rooting tool, there is some chance that something will go wrong. Use of this tool is at your own risk, and I will not be responsible if you brick your phone in the process. Although there have been zero reports of this tool breaking anyone's phone, don't run it if you aren't comfortable with the possibility of having something go wrong and having to re-Odin back to stock or worse.
Instructions:
Install the USB drivers if you don't have them already: Verizon_Wireless_I535_GSIII_Samsung_USB_Driver_v1_4_6_0.exe
Download the package and extract it somewhere (you'll need 7-Zip or some other modern compression tool) Make sure you extract all the files to a folder somewhere! Running it straight from your compression program probably won't work.
On your phone, enable installation of third-party apps (Settings --> Security --> Unknown sources, near the bottom in the "Device administration" section)
On your phone, enable USB debugging (Settings --> Developer options --> USB debugging)
On your PC, make sure you don't have any other Android devices connected, any Android emulators running, or any Android tools like PdaNet running.
Plug your phone into a USB port on your computer. For best results, use a port directly on the machine, and not a USB hub.
Double-click RootDebugfs.bat and follow the directions on the screen. Your phone will reboot 3 or 4 times during the process; just leave it plugged in. To be safe, don't switch to any other applications while the root process is running.
DOWNLOAD GS3DebugFSRoot R2 FOR US GALAXY S III VARIANTS ONLY!!!
(Released July 24, 2012)
If anything goes wrong, post here and I'll see what I can do.
Credits:
* miloj, for the debugfs root method for the Asus TF300T
* sparkym3, for his script for rooting the Asus Transformer Prime - this is a modified version of that script
* ChainsDD, for Superuser
Version History:
The most recent version is always at the top.
r2 2012-07-24
+ Changed font color to white for readability
+ Cleaned up output
+ Fixed typo in title (GSII instead of GSIII)
+ Fixed Unknown Sources/USB Debugging directions
+ Included latest version of adb from platform-tools 13, might make things more reliable
* Includes ChainsDD Superuser 3.1.3 and su binary 3.1.1
* Known to work with LF2 and LG1.
r1 2012-07-23
* Initial beta
* Includes ChainsDD Superuser 3.1.3 and su binary 3.1.1
* Works with LF2. Probably works with LG1.
Possible future features:
* APK version of the tool! I'm still not sure if this is possible - currently researching.
Sadly, I don't think this is going to happen.
* Unroot tool.
* Choice of Superuser or SuperSU.
FAQs:
Q: What versions of the stock ROM does this work with?
A: It's known to work with anything from LF2 up to LHE. It seems likely that DebugFSRoot will be able to work with any ICS ROMs. We'll have to wait and see if it works on JB or not.
Q: I'm getting an error like "adb is not recognized as an internal or external command", or "cannot stat 'su': No such file or directory". What do I do?
A: Don't run the tool straight from your compression program. Make sure to extract all the files somewhere first.
Q: Will this wipe my data?
A: Nope.
Q: How can I unroot? Will flashing a stock ROM unroot?
A: Flashing a stock ROM will unroot and also remove any modifications you made to /system.
Q: Everything seems to have worked fine, and the Superuser app shows the binary as present and working. However, none of my root apps work. What do I do?
A: This seems to happen to a very small number of people, and the cause is unknown. If this happens to you, try installing Chainfire SuperSU.
Q: Is this any better than flashing the root66 ROM?
A: The end result should be pretty much the same, but this tool is much smaller to download than the root66 ROM.
A: If you are on a phone with the stock LG1 ROM update, root66 will downgrade you to LF2, while this tool will leave your ROM alone.
Q: Is this any better than using the VRALEC boot chain method?
A: The boot chain is a little more complicated. It requires flashing two bootloaders, flashing recovery, and using Triangle Away to reset the Custom Binary Download counter. If you intend to install a custom recovery/custom ROMs anyway, it's fine and probably quicker. However, if all you want is root to run Titanium Backup or other root apps, GS3DebugFSRoot is easier.
Q: Will this increment the flash counter?
A: Not on its own. If you flash anything else after rooting, however, you might, so read up on what you're doing.
Q: Will this cause the "custom unlock" boot screen to appear?
A: In general, no. However, the spyware Samsung/Verizon included (SysScope/libcordon) is paranoid, and a lot of tweaks you can do after rooting will trigger it. If you don't want to risk getting the custom unlock screen, don't freeze any apps using Titanium Backup and generally limit your tweaking to things you could do without root.
Q: Can Samsung/Verizon block this method in the future?
Yes. It's very possible that a future OTA will patch the exploit that this tool uses. If you want to root, it's always best to do it now!
I just tried this and it appears to work. Installed Titanium Backup and SuperUser permissions were given. Thanks!
P.S.
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.
DFieldFL said:
I just tried this and it appears to work. Installed Titanium Backup and SuperUser permissions were given. Thanks!
P.S.
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.
Click to expand...
Click to collapse
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?
Noxious Ninja said:
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?
Click to expand...
Click to collapse
Also title says Galaxy S II not III.
Noxious Ninja said:
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?
Click to expand...
Click to collapse
The boot screen looks the same to me.
Worked for me, thanks
Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"
phantomevo77 said:
Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"
Click to expand...
Click to collapse
Same thing happening to me.
EDIT: Just switched usb ports and unplugged and replugged my phone in and it worked!
If my gs3 came updated with the newest version, will this still work?
Next release will be out tonight after I test it.
DFieldFL said:
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.
Click to expand...
Click to collapse
Fixed in the next version. Also, I added those steps to the main post.
open1your1eyes0 said:
Also title says Galaxy S II not III.
Click to expand...
Click to collapse
Typo on my part. Will be fixed in the next release.
phantomevo77 said:
Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"
Click to expand...
Click to collapse
I'm not sure about this one. However, I had packaged a slightly older version of adb, which could cause a difference. The next release will have the latest adb.
eakrish said:
If my gs3 came updated with the newest version, will this still work?
Click to expand...
Click to collapse
I think so, but I don't know if it's been tested. Worst case should be that it would fail when trying to copy su into /system/xbin/, and you might have to manually clean up a few things:
Code:
adb shell
[COLOR="Red"]$[/COLOR] rm /data/local/tmp
[COLOR="Red"]$[/COLOR] mv /data/local/tmp.bak /data/local/tmp
[COLOR="Red"]$[/COLOR] rm /data/local/su
[COLOR="Red"]$[/COLOR] rm /data/local/debugfs
[COLOR="Red"]$[/COLOR] rm /data/local/debugfsinput
[COLOR="Red"]$[/COLOR] exit
Really worst case is that your /system is screwed up and you have to re-flash a stock ROM with Odin, but that is highly, highly unlikely with this method.
Thanks for this awesome tool!!! Will there be a reversal to what this script does, aka, non-root to reverse changes if necessary or will that require odin flash?
It's probably possible to unroot via script. I think it might even be possible to move this into an APK and do away with adb altogether. I'll play around with it.
Is there an unroot method that's just as easy? I'd prefer not to reflash the phone to get rid of root. I guess I'm one of the oddballs here as I can care less about custom roms, I only root to be able to backup and remove bloatware.
edit: sorry I typed and posted this as others were doing the same... I couldn't delete or edit the post for a few minutes because of my newby status.
edthesped said:
Is there an unroot method that's just as easy? I'd prefer not to reflash the phone to get rid of root. I guess I'm one of the oddballs here as I can care less about custom roms, I only root to be able to backup and remove bloatware.
Click to expand...
Click to collapse
You should be able to do it via adb shell.
Code:
adb remount rw
adb shell
$ su
# rm /system/xbin/su
# exit
And then uninstall the Superuser app.
I'll try and add it to the script.
Thank You ! so much ... The tool works perfectly on my stock VZ ... Finally can get rid of all the crap that VZ puts in.
Noxious Ninja said:
It's probably possible to unroot via script. I think it might even be possible to move this into an APK and do away with adb altogether. I'll play around with it.
Click to expand...
Click to collapse
That would be awesome. It would be cool if you could make it unroot as well. Keep up the good work!
Tap'd via SGSIII(!)
CooL Very Very CooL
Thanks Noxious Ninja
eakrish said:
If my gs3 came updated with the newest version, will this still work?
Click to expand...
Click to collapse
Mine came with the update and I was able to root successfully with this tool. Very nice.

[Q] How To, If Possible, Root With Bad Volume Keys

So, I'm attempting to root a Charge that the volume keys do not work. Apparently, 1 and 2 year olds who have great throwing ability is something the Charge, well, anything really, doesn't exactly appreciate. Normally, I root by going into the download mode, and flashing CWM, then installing the ROM. Obviously, not happening here.
My question is, has someone with more knowledge than I figured out how to accomplish this? Its running stock FP5. I really don't want to send it in because of the contract timing and wasteful of money. I'm also willing to experiment replacing parts, if someone knows anything about it...
Thanks.
Sent from my SCH-I510 (Tweaked 3.0) using xda premium
Yep. There's a jig that will force the phone into dl mode. IIRC it's branded for the gnex but it's confirmed to work on the Charge as well. http://forum.xda-developers.com/showthread.php?p=27533069
Sent from my SCH-I535 using Tapatalk 2
Hey, I had a thought of using ADB to root, and somehow forcing CWM on it, then using an app to boot it into dl mode. I've never used and before and don't know if it's possible, although, from what I read, it seems plausible. Can you offer any insight on this idea?
Sent from my SCH-I510 using xda
edji-x said:
Hey, I had a thought of using ADB to root, and somehow forcing CWM on it, then using an app to boot it into dl mode. I've never used and before and don't know if it's possible, although, from what I read, it seems plausible. Can you offer any insight on this idea?
Sent from my SCH-I510 using xda
Click to expand...
Click to collapse
If you have adb all set up and it properly recognizes your phone (something comes up when putting in the adb devices command) you can boot into download mode with
adb reboot download
Actually it's something I looked into recently for another member. I'm not saying it's not possible but I don't think we have the right tools for it. Originally ginger root was used via adb to root the charge but that's not going to work with our version of gb (assuming you could still find it). I'm not sure the format of cwm will work either. I'm not really proficient with adb so someone with more expertise might be able to get you going.
Sent from my Nexus 7 using Tapatalk 2
Awesome. I don't have it installed yet, but it doesn't look like it takes much to make it work. Plus, I have nine that isn't screwed up, so I think I'll see what I can come up with later.
On a side note, I can't post a reply to your tweaked 3.1 thread, but I ran into somewhat of a problem... run tweaktools, did the tweaks thing, phone BARELY would run. I also couldn't get a shell to run to get back in to uninstall. What I ended up doing to fix was a reinstall of SuperSU and installing a bash shell off a different emulator to get back into tweaktools. This was after I played in /system/etc/init.d awhile trying my hand at fixing it. Thought you may want/need to knoknow.
Sent from my SCH-I510 using xda
By the way, thanks for the tip. I'll report one way or another in a day or 2.
Sent from my SCH-I510 using xda premium
edji-x said:
On a side note, I can't post a reply to your tweaked 3.1 thread
Click to expand...
Click to collapse
You need 10 posts minimum to post in the Dev forums, XDA's rules.
Sent from my Droid Charge running [email protected] 3.2a enhanced by dSlice's Scripts & Tweaks
edji-x said:
Awesome. I don't have it installed yet, but it doesn't look like it takes much to make it work. Plus, I have nine that isn't screwed up, so I think I'll see what I can come up with later.
On a side note, I can't post a reply to your tweaked 3.1 thread, but I ran into somewhat of a problem... run tweaktools, did the tweaks thing, phone BARELY would run. I also couldn't get a shell to run to get back in to uninstall. What I ended up doing to fix was a reinstall of SuperSU and installing a bash shell off a different emulator to get back into tweaktools. This was after I played in /system/etc/init.d awhile trying my hand at fixing it. Thought you may want/need to knoknow.
Sent from my SCH-I510 using xda
Click to expand...
Click to collapse
Sorry to hear of the troubles - not sure what would have caused the issue with tweaktools. You weren't able to su, or you weren't able to open terminal emulator? What were you messing with specifically in the tweaks?
dwitherell said:
If you have adb all set up and it properly recognizes your phone (something comes up when putting in the adb devices command) you can boot into download mode with
adb reboot download
Click to expand...
Click to collapse
:banghead:
Sigh, I don't know why I didn't think of that lol. And I was Ninja'd. Double whammy lol
Sent from my SCH-I535 using Tapatalk 2
Okay, Found it in ADB, and am able to reboot into download, so all is well, I think.
On the tweaktools issue, I kinda did something like this...One tweak does okay, so lets install ALL of them....after that, performed the reboot, and everything went very sloooow. So, I tried to get into a term emulator, and nothing happened, the shell wouldn't even start. Blank screen. So, I tried a different outside of ROM toolbox. Nothing. So, I played around with the settings here and there, and still nothing. I then went into root browser, and started trying to manually move the tweaks out, nothing different. So, I downloaded another term emulator, "Better Terminal Emulator" and got a bash shell to at least open, was able to get into tweaktools, erase all tweaks, clear downloads. But the shells still weren't operating right. They'd open and run, but nothing would show on screen. So, a erase/reinstall of SuperSU, everything good....LOL
Well, maybe it'll help, maybe not, but here's the path I used to do this:
Visit samsung's site for the ADB download and install to c:\android-sdk\ (default)
Put USB Debugging on in phone
Start up command line and Odin 1.82
issue following in command line (notably in the c:\android-sdk\platform-tools)
Code:
adb reboot download
Odin up some Tweaked 2.2 with recovery and kernel for root
once rebooted, issue the following in ADB shell:
Code:
adb shell
su (Checked phone to be sure root was granted)
cd /data
rm -R *
cd /cache
rm -R *
cd /dbdata rm -R *
reboot, then adb reboot download.
Flashed EP4 Stock, updated,
Updated to FP5E
Once again, USB debug, adb reboot download, and Odin Tweaked 3.1 with 0302,
follow above code again, reboot, and I think I have it right....
Since the volume keys don't work on here, is there a way to screw around in the recovery mode via ADB rather than only the keys? I see ADB sees the phone in recovery, and seems to want to connect with it....Second is, is there a way to play with this in the *nix enviroment? I also have been searching for the Gingerbreak, etc to root this thing on stock, but haven't been able to do it....and last, is there a way to do a data wipe other than what I did, and think i accomplished with ADB?
Thanks
With the CWM that I am using, you can use the hard buttons at the bottom of the phone to navigate.
Sent from my SCH-I510 using Xparent Red Tapatalk 2

[Q] FileMate Clear 7" T720 tablet

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.

Root access after software update

I rooted my Samsung Galaxy Tab 2 GT-P3113 using ClockworkMod to flash the cwm-root-gtab2.zip file from an SD card. I was granted root access just I was supposed to be. Some time later, I did SOME (can't remember exactly what) OTA update, and after the update, I lost root. Looking into it, I still have the su binary installed, but for some reason, if I tried su-ing from the Terminal Emulator, it tells me "permission denied". Any app that uses root won't work either. BUT, plugging the tab into my Linux computer, I am able to run 'adb shell' and I can run su just fine. I noticed that now, running from the tablet, the user on Terminal Emulator is set to u0-128, whereas before, I'm pretty sure it was just 'shell'. When I do 'adb shell', the user is also just shell. The permissions for su have the setgid bit on, but not the setuid. What exactly caused this, and how do I fix it (besides just rooting the device again)? Everywhere I look, it seems like the setgid bit is the only one on, and not setuid. Would flipping that bit also work? Or is there some other reason not to do that?
You might just need to flash SuperSU.zip in recovery.
jrc2
Sent from my GT-P3110 using Tapatalk.
jrc2 said:
You might just need to flash SuperSU.zip in recovery.
jrc2
Sent from my GT-P3100 using Tapatalk.
Click to expand...
Click to collapse
Yea, I was thinking about that, but I'm just going to flash CyanogenMod. What I really want to know is what caused su to stop working? Like I said before, if I plug my tab to my computer, I can still su in an adb shell. And would it work if I set the setuid bit? I was wondering if there was a security reason not to do that... Also, what about the update caused the 'user' to be changed? I could have sworn before that it was just 'shell' but now it seems to have that u0_128, which I think is the ID of some sandbox for each app? I'm not sure on that either...

Categories

Resources