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 !
Related
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
I just received my new TF700 shipped from BestBuy.com
I've already noticed several funny behaviors, as compared with the TF300 I tested out last month.
Battery was at 0% when I opened the box
No typical Android first-time welcome screen stuff
Gallery has a picture taken of a camera calibration test pattern
Dev Options had USB Debugging, Stay Awake, and Allow Mock Locations all checked.
Cannot set the Screen Lock>Slide
Screen seems to flicker a bit when I return to the home screen.
Serial number is reported as 11111111111111111
ADB also identifies the device as 11111111111111111
Several generic actions cause crashes, such as accessing Settings>Accounts and Sync
Browser crashes directly after opening
Red border around the screen, similar to this thread
http://forum.xda-developers.com/showthread.php?t=1442185
Numerous pre-loaded apps that look well outside of standard
AtCmdSender
ATS_Discharge
ATS_MMI_TF700
bmmi.v2.3
BTtest
Command
DevTools (I know this one, but can't remember if this is included as standard app now or not, I doubt it)
FTM
GPS Test v5.12
Log Tool 2.21.1
MTTestTool
RunIn_v2.5
Spare Parts (as with DevTools, I know this one but don't think this is standard)
TF700_Gsensor_TestV1.22
TF700T (ATS logo)
TF700T_Ecompas_Kv1.3
TF700T_GsensorKv1.23
WLAN RF Test Tool BCM4329
And of course, the Build Number is identified as
OPEN_epad-eng 4.0.3 IML74K OPEN_epad-9.0.4.104.15-20120618 test-keys
Several other threads I found regarding OPEN_epad builds
http://forum.xda-developers.com/showthread.php?t=1577386
http://forum.xda-developers.com/showthread.php?t=1685600
http://www.transformerforums.com/forum/transformer-pad-300-help/24112-solved-update-firmware.html
http://www.transformerforums.com/fo...prime-not-offering-update-new-firmware-2.html
I would like to get this thing into a more standard operating condition for myself (before I start looking at custom ROMs, of course).
I thought I would post in case any Devs here thought there might be useful stuff I could dump.
I'll also try freenode.net #asus-transformer
reserved
I don't know the status of root, or whether the bootloader is unlocked.
Looks like the device is NOT unlocked.
ADB just spit back
Code:
/system/bin/sh: cp: not found
so maybe I need some BusyBox up in here to keep working
UPDATE: So now it looks like I'm finding that the tab won't charge past 59%.... :/
If your device is unlocked, you can see it in the upper right corner when turning the device is turned on
"Your device is unlocked"
Sent from my ASUS Transformer Pad TF700T using xda premium
hillbicks said:
If your device is unlocked, you can see it in the upper right corner when turning the device is turned on
"Your device is unlocked"
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
Upper left corner
Not unlocked
I got the same advice about upper left corner on IRC.
Doesn't look like the tablet is unlocked right now. Of course, that may change
Can you zip some of those apps and post them somehwere please? Would like to take a look if you don't mind. PM me.
EDIT: and eng in the firmware typically means an engineering build.
If the bootloader comes pre unlocked, you've found yourself a pretty good device. Warranty+custom roms.
system-app and data-app
I pulled everything from these two folders.
data-app.zip
15,307 kB
system-app.zip
136,636 kB
UPDATE: removed links to DL files, may replace later
PM sent
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Dev apps
I've PM'd links to download everything from /data/app and /system/app to a couple of people.
I'll be curious to know if anyone finds anything interesting or useful.
Is there anything else I should try to dump from this tab?
I'd like to start using it (which probably means wiping), but want to make sure I pull all of the helpful stuff for XDA members first.
ScottHW said:
I've PM'd links to download everything from /data/app and /system/app to a couple of people.
I'll be curious to know if anyone finds anything interesting or useful.
Is there anything else I should try to dump from this tab?
I'd like to start using it (which probably means wiping), but want to make sure I pull all of the helpful stuff for XDA members first.
Click to expand...
Click to collapse
Hi,i'm not a developer and so far most of that soft looks like diagnostic tools but a dev should know better.As for using the tablet i don't know if it's a good idea to keep it (i would return it) mostly because of the serial number (have you checked the logs to see if the device try to communicate with Asus server?) and because is clear that such a device was used for testing so maybe it was an early sample...anyway it's your call.If you keep it you can try to root ,unlock and than install the custom recovery so you can do a nandroid backup before wipe everything.
I would root, try to unlock get recovery installed and take a backup and post it.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Return.... Nandroid
Thanks for the suggestions, that is basically what I was thinking.
I agree that this will most likely get returned. Just want to get all the goodies first.
I do think I'll have to return it. Too many screwy things going on here.
As for dumping, I thought the same lines a la Nandroid.
Of course, if I unlock the bootloader to install a custom recovery, then I wouldn't be able to return it....
ScottHW said:
Thanks for the suggestions, that is basically what I was thinking.
I agree that this will most likely get returned. Just want to get all the goodies first.
I do think I'll have to return it. Too many screwy things going on here.
As for dumping, I thought the same lines a la Nandroid.
Of course, if I unlock the bootloader to install a custom recovery, then I wouldn't be able to return it....
Click to expand...
Click to collapse
IMO you've done your best to help the community so just return it and start enjoy your tablet. Also i don't think that the tablet is a developement enviroment so it can't be such a valuable resource for devs.
Update and/or return
Pretoriano80 said:
IMO you've done your best to help the community so just return it and start enjoy your tablet. Also i don't think that the tablet is a developement enviroment so it can't be such a valuable resource for devs.
Click to expand...
Click to collapse
Glad to do what I can to help. I really appreciate those whose skills exceed my own, and do the dev work from which we all benefit.
Another way of saying that: I can't wait to get some sweet sweet CM up on this tab!
Only problem is... BestBuy doesn't have these in stock, which is why I had to order it shipped from BestBuy.com
Now I'll have to wait more days for another one to ship
I might try to "update" the software OTA, but I've read several other threads mentioning that OPEN_epad cannot be easily updated OTA.
I don't have any internet connection on this thing turned on yet, in case it tries to dial home and updates before I dump useful stuff, or gets remotely locked and/or wiped.
I'll flip on some wifis and see what System Update does for me.
UPDATE: System Firmware Update simply returns "There is no update available for your device currently." Guess I'll have to try harder to wipe away the OPEN_epad build.
adb pull /system
I just pulled everything on /system. A log is attached.
If anyone wants anything in there, let me know.
/system
413,136,276 bytes
UPDATE: I had a problem pulling /data, so here's a list for now (attached)
[email protected]:/ # cd /data
[email protected]:/data # ls -alR
UPDATE: removed attached lists of files for security
dumps
Alright.... I got some help and I dumped /system /data first32 (half the bootloader, recovery, boot, provisioning certificate...)
The dev I worked with over on freenode.net#asus-transformer is much more skilled than I, so now these are .img dumps, rather than just pulling individual files.
If anyone thinks they can find diamonds in that rough, let me know.
ScottHW said:
Alright.... I got some help and I dumped /system /data first32 (half the bootloader, recovery, boot, provisioning certificate...)
The dev I worked with over on freenode.net#asus-transformer is much more skilled than I, so now these are .img dumps, rather than just pulling individual files.
If anyone thinks they can find diamonds in that rough, let me know.
Click to expand...
Click to collapse
PM sent
Sent from my GT-P1000 using xda app-developers app
ScottHW said:
Alright.... I got some help and I dumped /system /data first32 (half the bootloader, recovery, boot, provisioning certificate...)
The dev I worked with over on freenode.net#asus-transformer is much more skilled than I, so now these are .img dumps, rather than just pulling individual files.
If anyone thinks they can find diamonds in that rough, let me know.
Click to expand...
Click to collapse
Thanks alot. I will take a look. You can pull your Dropbox links if you would like so you don't use up your bandwidth.
Go ahead and proceed with what you want to do...will let you know if I find anything interesting to us
so two weeks have passed did you get a replacement for the tablet or updated or something? how that went.
also : was any of those files useful for developers?
...you need to make sure you can make it through this checklist.
This isn't a "how to" -- there are plenty of threads about that and stickies and search work pretty well, as does the SGS4G Wiki.
1) How long have you owned your phone? If it is brand-spanking new and your carrier will exchange it if it turns out to be defective, stop here.
2) Why are you contemplating installing whatever it is? Are you confident that the developer knows what they are doing? There is a wide range of skill and an even wider range of testing of things you might find on XDA.
2) Do you understand that virtually all ROMs, tweaks, kernels, what have you that you find on XDA, are all experimental, without warranty, and may turn your phone permanently into an expensive paperweight? Yes you can literally fry the innards of a phone with bad software, or even inappropriate user settings.
3) Are you prepared to be without your phone being functional for hours, days, or longer? Expect it. You're thinking of flashing experimental software.
4) Is your computer stable and reliable? Do you have or have you ever had any issues with USB or Internet connectivity? Fix those first.
5) Have you already installed and know how to use adb? Have you confirmed that it works with your computer, cable, and phone? This means understanding and having used at least:
adb push
adb pull
adb shell
adb logcat
adb remount
as well as shell commands including at least
# logcat
# dmesg
# cat /proc/kmsg
# mount -o rw,remount /system
# mount -o ro,remount /system
Shell redirection to a file, for example, # dmesg > /sdcard/dmesg.today.txt
Using crtl-C to terminate the foreground process in a shell
Yes, "this ain't no iPhone" when you start installing custom ROMs, tweaks, or whatever. You should be prepared to deal with the Linux part of the phone; you're often installing a new operating system and may have to deal with its underpinnings.
No, your GUI-driven "root explorer" really isn't the right tool. You have to be very careful with Windows text editors too. You're lucky I'm not asking you to learn vi.
6) Have you installed and know how to use
Better Battery Stats
aLogcat
aLogrec
7) Have you installed Heimdall, and confirmed that the drivers work for your system (very important for Windows)?
8) Have you already downloaded the "back-to-stock" package for your phone?
9) Have you installed Titanium Backup, preferably Pro, and have complete backups of your system?
10) Have you backed up your Contacts (you can use the phone's Contact app to do this)?
11) Have you backed up your phone logs and SMS/MMS (you can use Backup SMS & Restore and Call Logs Backup & Restore)?
12) Do you have a copy of all of these on something other than the phone and the microSD?
13) Have you read both the thread in Development and the thread in Q&A for the back-to-stock package as well as what you are about to flash? Really, I mean it. Yes, the whole thing. If you don't have time to read the threads, you probably shouldn't be flashing your phone.
If you weren't able to check off all the above. STOP NOW.
OK -- backups in hand, power down your phone. Pull the SIM. Boot into recovery. Do a full backup of everything there as well. This is a "nandroid" backup. (If you're on "stock" without a kernel with custom recovery already flashed, you won't be able to create a nandroid backup.)
Flash the back-to-stock package according to the instructions. Were you able to do that successfully? Did your phone boot? Failure? Read the thread on the back-to-stock package carefully. They really are pretty bullet-proof. You're going to get terse responses if you have problems with the back-to-stock. If you fail here, restore that nandroid backup in your recovery. Go back and make sure you understand how flashing works and re-read the instructions.
Once you can go back-to-stock, make sure you can restore from your backups from steps 9-11. Yes, your SIM is still out, that way you won't be changing anything important on your phone. If you can't, restore the "nandriod" backup. Yes, go back and re-read things again until you understand and can do this reliably.
Made it to here? Go ahead and follow the flashing instructions for your ROM that are in its Development thread, generally in the first couple posts. You did read the entire thread, yes?
Restore your data from backups, if needed. Once you're confident it is running properly, power it down, and now insert your SIM again. Power it up and enjoy your new software.
Have a problem with a ROM or a piece of software? Remember that the problem basically doesn't exist until a dev can reproduce it, or see logs of it happening. Need a hint? See steps 5 & 6 here.
Sticky please.
Thread stickied... but let me run through my answers...
jeffsf said:
...you need to make sure you can make it through this checklist.
1) How long have you owned your phone? If it is brand-spanking new and your carrier will exchange it if it turns out to be defective, stop here. SGSIII - less than an hour...
2) Why are you contemplating installing whatever it is? Are you confident that the developer knows what they are doing? There is a wide range of skill and an even wider range of testing of things you might find on XDA. I want to play!...
2) Do you understand that virtually all ROMs, tweaks, kernels, what have you that you find on XDA, are all experimental, without warranty, and may turn your phone permanently into an expensive paperweight? Yes you can literally fry the innards of a phone with bad software, or even inappropriate user settings. YUP
3) Are you prepared to be without your phone being functional for hours, days, or longer? Expect it. You're thinking of flashing experimental software. Hope not!, but sure... read user comments (thread) before flashing...
4) Is your computer stable and reliable? Do you have or have you ever had any issues with USB or Internet connectivity? Fix those first. Motherboard bluescreens once a month randomly... gotta replace that soon....
5) Have you already installed and know how to use adb? Have you confirmed that it works with your computer, cable, and phone? This means understanding and having used at least: Never used ADB personally... for my captivate or SGSIII
adb push
adb pull
adb shell
adb logcat
adb remount
as well as shell commands including at least
# logcat
# dmesg
# cat /proc/kmsg
# mount -o rw,remount /system
# mount -o ro,remount /system
Shell redirection to a file, for example, # dmesg > /sdcard/dmesg.today.txt
Using crtl-C to terminate the foreground process in a shell
Yes, "this ain't no iPhone" when you start installing custom ROMs, tweaks, or whatever. You should be prepared to deal with the Linux part of the phone; you're often installing a new operating system and may have to deal with its underpinnings. Not a Linux fan....
No, your GUI-driven "root explorer" really isn't the right tool. You have to be very careful with Windows text editors too. You're lucky I'm not asking you to learn vi.
"Root explorer" app works great. But i would hardly call it GUI driven... lol
6) Have you installed and know how to use
Better Battery Stats Never heard of it
aLogcat NOPE
aLogrec NOPE
7) Have you installed Heimdall, and confirmed that the drivers work for your system (very important for Windows)? Hate Heimdall, odin works just fine. Its samsungs offical software, i think it should work. (It does). Chickens.
8) Have you already downloaded the "back-to-stock" package for your phone? Yes before i bought the phone.
9) Have you installed Titanium Backup, preferably Pro, and have complete backups of your system? Yes but after flashing first phone few times...
10) Have you backed up your Contacts (you can use the phone's Contact app to do this)? Sync to google account. no back up needed. figured that out before i found xda.
11) Have you backed up your phone logs and SMS/MMS (you can use Backup SMS & Restore and Call Logs Backup & Restore)? Titanium backup does this as well
12) Do you have a copy of all of these on something other than the phone and the microSD? Some... AND Titanium backup can sync to dropbox account or box account.
13) Have you read both the thread in Development and the thread in Q&A for the back-to-stock package as well as what you are about to flash? Really, I mean it. Yes, the whole thing. If you don't have time to read the threads, you probably shouldn't be flashing your phone. Yup
If you weren't able to check off all the above. STOP NOW.
Click to expand...
Click to collapse
8 out of 13... damn. i should stop flashing and give my recognized developer status back... LOL
TRusselo said:
Thread stickied... but let me run through my answers...
8 out of 13... damn. i should stop flashing and give my recognized developer status back... LOL
Click to expand...
Click to collapse
Heh, we gotta get you an sgs4g and have you show me how to get this crap working without using logcat or reading dmesg.
Trying to install jelly bean on my sgs4g
so far i did everything that's on this page for post 1 http://forum.xda-developers.com/showpost.php?p=21953587&postcount=1
now i want jelly bean what do i do please helpp
salutparis said:
so far i did everything that's on this page for post 1 http://forum.xda-developers.com/showpost.php?p=21953587&postcount=1
now i want jelly bean what do i do please helpp
Click to expand...
Click to collapse
This really isn't a support thread. It's more of a PSA.
If you want help, I'd suggest searching in the Q&A forum.
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.
(NOTE: this post is a duplicate of a similar thread I started on the Android Central user forum)
Hello everyone,
In the continuing saga of the Leagoo T5C i bought before the holidays from GearBest, I've seen the good (the price and overall build quality, along with a reasonably good user experience), the bad (some notifications that I just can't get rid of, among other things), and I now present you the ugly: after watching a review video on YouTube about my device, I learned that it came loaded with a Trojan called "Gorilla.AM"...
***EDIT: apparently, the Trojan's name could actually be "Guerrilla.AM", I'm not sure.***
Needless to say, I did as the tester had, and installed Malwarebytes, which, sure enough, found the exact same Trojan on my device.
You can watch the video here: https://www.youtube.com/watch?v=R5l3z7BvBtk
It so happens that it's embedded in Leagoo's own application launcher, called Sujet (in French; maybe it's called "Subject" in English, I don't know). I can force quit the application, since I use another launcher called Apex (good pick, by the way), but Malwarebytes can't seem to shake the Trojan off my device nonetheless.
A quick search on Google gives very little in the way of information about this malware, but I'd like to be on the safe side, so I came here.
Any contribution would be welcome at this stage.
Hi. I've seen your post on a french-speaking forum but for my own reasons I don't want to help there, too many morons.
Leagoo is well-known for smartphones with built-in spyware/adware. I've had both a Z5 and a M5 and both had such crap in the stock firmware.
This one is new to me but you'll probably have to follow the same steps to get rid of it.
Try
Code:
adb shell pm disable <internal name of that launcher>
first (from a PC connected to the device with ADB - zillions of tutorials available for this)
The internal name can be found by guessing or by using one of the many apps that will show you the information. One is https://play.google.com/store/apps/details?id=com.csdroid.pkg
If that fails, try adding "-k -user 0" to the command line.
If it fails again (denied) then you have no choice but to root your device first, then use this pm command from a root shell or directly delete the folder for "Sujet/Subject" from /system/app or /system/priv-app where you'll find it.
Lannig said:
Hi. I've seen your post on a french-speaking forum but for my own reasons I don't want to help there, too many morons.
Leagoo is well-known for smartphones with built-in spyware/adware. I've had both a Z5 and a M5 and both had such crap in the stock firmware.
This one is new to me but you'll probably have to follow the same steps to get rid of it.
Try
Code:
adb shell pm disable <internal name of that launcher>
first (from a PC connected to the device with ADB - zillions of tutorials available for this)
The internal name can be found by guessing or by using one of the many apps that will show you the information. One is https://play.google.com/store/apps/details?id=com.csdroid.pkg
If that fails, try adding "-k -user 0" to the command line.
If it fails again (denied) then you have no choice but to root your device first, then use this pm command from a root shell or directly delete the folder for "Sujet/Subject" from /system/app or /system/priv-app where you'll find it.
Click to expand...
Click to collapse
Hi,
OK, first off, thanks for the reply. Secondly, as I've stated before, I'm new to Android, and though I know my way around the command line in both Windows, Linux et OS X (not so much macOS: my MacBook Pro is 12-years old...), I suppose there are some things to set up first, before you can actually do what you suggest.
I understand that ADB stands for Android Debug Bridge, so is it an existing functionality in, say, Windows, that you can trigger from the command line, or a third-party software you have to install first?
On the Android side, what action should I take? Any Developer command to enable/disable to let ADB interact with my device the way it's supposed to?
Yes, you need to enable debug mode on your phone too. I could refer you to one of the zillion tutorials available on the net, but here's a summary.
Go to settings > about... (à propos)
Make at least 7 rapid touches on the line that says "build number" or its french translation.
This will make a new settings menu available from the main settings page: developer options
In this new menu, enable USB debugging.
Then you need to install ADB on your Mac and I'm at loss to help you there because I'm totally foreign to Macs. Never used one.
This seems like a good start: https://www.xda-developers.com/install-adb-windows-macos-linux/
Note: you may also try issuing the commands mentioned above from a terminal emulator running directly on your Android device, although I'm told that it's not exactly the same thing protection-wise.
Install this: https://play.google.com/store/apps/details?id=jackpal.androidterm and try typing the commands from the emulator window. If it works, no need for ADB (although having ADB will probably prove useful sooner or later and I encourage you to take the step).
EDIT: forget the guys from Phonandroid, they're brain-damaged beyond help
Lannig said:
Yes, you need to enable debug mode on your phone too. I could refer you to one of the zillion tutorials available on the net, but here's a summary.
Go to settings > about... (à propos)
Make at least 7 rapid touches on the line that says "build number" or its french translation.
This will make a new settings menu available from the main settings page: developer options
In this new menu, enable USB debugging.
Then you need to install ADB on your Mac and I'm at loss to help you there because I'm totally foreign to Macs. Never used one.
This seems like a good start: https://www.xda-developers.com/install-adb-windows-macos-linux/
Note: you may also try issuing the commands mentioned above from a terminal emulator running directly on your Android device, although I'm told that it's not exactly the same thing protection-wise.
Install this: https://play.google.com/store/apps/details?id=jackpal.androidterm and try typing the commands from the emulator window. If it works, no need for ADB (although having ADB will probably prove useful sooner or later and I encourage you to take the step).
EDIT: forget the guys from Phonandroid, they're brain-damaged beyond help
Click to expand...
Click to collapse
OK, thanks for the heads-up; I've already installed a Terminal emulator on the phone, so I'm gonna give it a go in a moment. I concur about Phoneandroid, alas: I've just received flak from one of the moderators because I'd double-posted on the same subject, whereas I'd just posted one thread, in the wrong part of the forum, according to him. Go figure...
OK, please feed back on your attempts, both from terminal emulator and through ADB.
Alas, I suspect that root will be required. It was for me on my Z5 and M5 to get rid of Leagoo's crapware.
Phonandroid is a bunch of losers with bloated egos posing as experts when 2/3 of the replies given are total BS.
"Er, Houston, we've had a problem..."
On Windows: "ADB is not a recognized name for a command applet..."
On OS X: "adb: command not found"
Stumped, I am...
"Er, Houston, we've had a problem..."
On Windows: "ADB is not a recognized name for a command applet..."
On OS X: "adb: command not found"
Stumped, I am...
(Additional question, not quite related: Aida64 indicates that my device runs a 4.4.49 version of the Android kernel, when the current version for Android 7.x is supposed to be 4.4.1; how does that compute--no pun intended--with my issue?)
Missing adb command is because the adb.exe (Windows) or adb (Mac) file is not in the command path. Either make the folder that contains the adb[.exe] file the current folder using the cd command or use whatever context menu for opening a command line window within the currently selected folder works, or even add that folder to the PATH variable. Google "add directory to path" for Windows and MacOS.
No idea about the kernel version. Minor kernel versions may vary within an Android release. Not surprising and most definitely unrelated to your problem. The crapware certainly isn't part of the kernel. It's most likely a system app i.e. a folder within either /system/app or /system/priv-app folders. You can't delete it without root, but you might be able to disable (freeze) it with the commands I gave you.
OK, thanks. I did "cd" to the folder where I had unzipped ADB on Windows (on the Mac, when I tried to open the ADB executable, I got a "cpu not supported" error message in the Terminal, as I feared, since my MBP is 32-bit-only, and most Mac applications nowadays only support 64-bit CPUs), and still got the "adb unrecognized command" error in PowerShell.
The phone was plugged in, and the right USB mode, so I'm still a bit baffled here. Gonna try it again with a different approach. Will keep you posted.
Over and out...
OK, here's what I got: "Error: java.lang.SecurityException: Shell cannot change component state for com.leagoo.launcher3/null to 2"
Basically, from my poor understanding of how Android works, it's root or die, right?
UglyStuff said:
OK, here's what I got: "Error: java.lang.SecurityException: Shell cannot change component state for com.leagoo.launcher3/null to 2"
Basically, from my poor understanding of how Android works, it's root or die, right?
Click to expand...
Click to collapse
I see that this phone has 7.x android. So, a Magisk Systemless flash might work. After rooting your device, get a good launcher integrate it to /system. Then delete your stock launcher all together.
Tell me if this works.
---------- Post added at 01:23 PM ---------- Previous post was at 01:20 PM ----------
rhn19 said:
I see that this phone has 7.x android. So, a Magisk Systemless flash might work. After rooting your device, get a good launcher integrate it to /system. Then delete your stock launcher all together.
Tell me if this works.
Click to expand...
Click to collapse
If you are new to this, use an app from play store for uninstalling and integrating apps.
Hi,
Yes, like I said, I'm a newbie when it comes to Android, so I'll abstain from rooting my device for now, but I'll keep your suggestions under advisement, because I suppose there'll be no other option in the long run. I'm gathering info on how to safely root a device.
I've done countless jailbreaks on iPhones, and it was always absolutely painless, but then, I had better understanding of how iOS works than I have Android, so until I know more about the OS, I'll keep my phone as it is.
Thanks again!
UglyStuff said:
Hi,
Yes, like I said, I'm a newbie when it comes to Android, so I'll abstain from rooting my device for now, but I'll keep your suggestions under advisement, because I suppose there'll be no other option in the long run. I'm gathering info on how to safely root a device.
I've done countless jailbreaks on iPhones, and it was always absolutely painless, but then, I had better understanding of how iOS works than I have Android, so until I know more about the OS, I'll keep my phone as it is.
Thanks again!
Click to expand...
Click to collapse
Jailbreaking vs Rooting is like 5-1 on difficulty level. Because Android is Open source while IOS is not. I would highly suggest you Root it if your phone does not have warranty. After all something that is on /system partition like your launcher will need superuser access to modify it. I cannot think of a way that wont void your warranty.
You can flash TWRP and then boot into aroma-fm but that will void your warranty. Rooting is the preferred option here.
Yeah, well, the phone is brand-new, and still under warranty, but that's not what's holding me back: I'd rather not brick it, most of all, because I need it, if not as my main phone, at least for connectivity.
I've read tutorials on this very website about using TWRP to flash a new baseband, but I'm curious about what firmware to choose, where to download it from to be sure it's not laden with bad stuff, and how sure I'll be to have an operable phone afterwards.
UglyStuff said:
Yeah, well, the phone is brand-new, and still under warranty, but that's not what's holding me back: I'd rather not brick it, most of all, because I need it, if not as my main phone, at least for connectivity.
I've read tutorials on this very website about using TWRP to flash a new baseband, but I'm curious about what firmware to choose, where to download it from to be sure it's not laden with bad stuff, and how sure I'll be to have an operable phone afterwards.
Click to expand...
Click to collapse
Why do you want a new firmware? I don't get you man, do you want to clear out the malware or try a new ROM? Because i think you would have to build a new ROM, there is not one available i guess.
That's the thing: the malware on my phone is part of the application launcher installed by the OEM. In other words, it's embedded inside the ROM. If I root my phone and somehow manage to get rid of this launcher, what's to tell me that Leagoo won't push it silently back onto my device under the disguise of an update?
I don't know what to do here. I understand that based on stock Android, each OEM applies a certain number of modifications to accommodate the hardware it used to build the phone, and since the SoC is brand-new, I gather there aren't many drivers available, unless I leave the current baseline in place.
I'm kinda caught between a rock and a hard place here...
UglyStuff said:
That's the thing: the malware on my phone is part of the application launcher installed by the OEM. In other words, it's embedded inside the ROM. If I root my phone and somehow manage to get rid of this launcher, what's to tell me that Leagoo won't push it silently back onto my device under the disguise of an update?
I don't know what to do here. I understand that based on stock Android, each OEM applies a certain number of modifications to accommodate the hardware it used to build the phone, and since the SoC is brand-new, I gather there aren't many drivers available, unless I leave the current baseline in place.
I'm kinda caught between a rock and a hard place here...
Click to expand...
Click to collapse
If you use malwarebytes after root that thing wont happen. And almost all of the OEMs have a trigger which voids when rooting or flashing firmware. After that the OEM wont give you updates unless you use the A/B partitioning system.
OK, I understand how rooting my phone would void the warranty: after all, it's a substantial change in the phone software, and the OEM can't be made responsible for any mishap that occurs after I've rooted the phone.
What's the A/B partitioning system (I suppose it helps partition your storage space)? I don't have a microSD card installed (I use the slot for my second SIM), but I do have 32 Gb of storage space, minus what's already used up.
Do you know KingRoot? Is it as good and (reasonably) safe a rooting tool as they say it is?