Related
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 !
Hello -
I've got a Boost Mobile LG LS720 (F3), and the phone was rooted with Towelroot, as it is a v7 phone. I was assisted at Android Forums originally; yet, I am trying to get assistance - as I want to start using Terminal Emulator, to unlock the phone's read-only memory status in sdext2. The phone works, but, I cannot get CWMT 6.0.4.8 to work correctly - it always triggers a factory reset; though, root remains. I'm able to use my mp3s from my 32 gB micro SD, but, I can't move apps using Link2SD Plus (which is the only way I can access CWMT 6.0.4.8). I'm not new to bringing root to phones, but, this Jelly Bean phone has given me nothing but trouble - I even soft-bricked it once during v6, and sent it to LG's Ft. Worth repair facility to get v7 installed (stock) I have Busybox installed, SuperSU, and to stop the 'Android Is Upgrading' app optimization at boot, I installed CWM Superuser. I have ES File Manager installed, Root Explorer, and Remount installed, as well. I want to learn about using Terminal Emulator, and taking my Android experience to the next level. I am willing to do whatever it takes to become immersed in Android, and one day, start developing apps. I hope that you folks can assist this 52-year-old, disabled Androidphile in taking things to the next level. Thank you for allowing me to post. LOveBusker
Hi,
Here is a Guide on Terminal....
Guide:Using the Terminal
For more specific info, or just more reading on it, I suggest you use the search function and see what you find. ?
Good luck!
---------- Post added at 09:46 PM ---------- Previous post was at 09:42 PM ----------
And there's no specific section for your device, so any questions or issues that are device specific....asking here would be best,
>Android Development and Hacking >Android Q&A, Help & Troubleshooting
Thread closed. Thank you.
Q&A for Bump! - Unlock your LG G3 with TWRP! (ATT)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
D855 successfully bumped. Thank you for your hard work
Bumped D855 last night.
Anyone else having a issue mounting SD card in TWRP? I have a Samsung 64gb evo just wondering.
is MTP mode .. "Download" mode ?
& will there likely be an easier streamlined way to do this in the future or are those ADB commands & all that likely to stay the way..
Anyone else pumped for some rom baking? I can't wait to get some stock android
I need a video know how.....I don't understand how to do it.....
thcue said:
Anyone else having a issue mounting SD card in TWRP? I have a Samsung 64gb evo just wondering.
Click to expand...
Click to collapse
Looking at some of the other threads, it seems you card is probably formated as exFAT and it needs to be Fat32. Read more here: http://teamw.in/exFAT
sic0048 said:
Looking at some of the other threads, it seems you card is probably formated as exFAT and it needs to be Fat32. Read more here: http://teamw.in/exFAT
Click to expand...
Click to collapse
Was it forgot all about that
Were in business
Worked quite easily on my verizon variant
---------- Post added at 07:39 PM ---------- Previous post was at 07:33 PM ----------
http://forum.xda-developers.com/showthread.php?t=2588979
is there a way I can do this without plugging my phone in ?
Wireless ADB for example..
Or can I use Terminal Emulator ?
jaladhjin said:
is there a way I can do this without plugging my phone in ?
Wireless ADB for example..
Or can I use Terminal Emulator ?
Click to expand...
Click to collapse
As long as you can get the file to the root of the sdcard (I simply plugged my phone into the computer and moved the file over using Windows Explorer), you can use a terminal program. If you are following the direction in the bump thread, you won't start adp. Just issue the three commands starting with "SU" and then the two other commands follow (one at a time).
Works just fine.
Thank you for your hard work!! !!!!!!
sic0048 said:
As long as you can get the file to the root of the sdcard (I simply plugged my phone into the computer and moved the file over using Windows Explorer), you can use a terminal program. If you are following the direction in the bump thread, you won't start adp. Just issue the three commands starting with "SU" and then the two other commands follow (one at a time).
Works just fine.
Click to expand...
Click to collapse
tyvm
I'm just trying to think of how to do it all without cording into my computer..
so if I download the file.. move it to the root of the sd with a file explorer..
fire up the terminal emulator & do those commands starting with SU
I should be all good in the hood ?
Stoked
I have been rooting and custom romming sense my first smart phone. You guys rock. Thank you!
so I rooted my phone using TowelRoot. Based on the thread, the unlock bootloader process will factory reset the phone if it isn't root using Stump Root. So can I just apply Stump Root on top of my rooted phone before unlock to avoid factory reset?
Use flashify and be done with it that is unless you want to do the adb thing
kvl19 said:
so I rooted my phone using TowelRoot. Based on the thread, the unlock bootloader process will factory reset the phone if it isn't root using Stump Root. So can I just apply Stump Root on top of my rooted phone before unlock to avoid factory reset?
Click to expand...
Click to collapse
what thread?
the OP says it must be Rooted. this is so ADB SHELL can gain access to the System partitions.
PS ( after you connect to adb make sure you grant root access to SHELL) (should pop up on your phone)
I'm pretty sure i used towel root to ease your fears.
when you use the last adb command you should see some feed back about moving some data... "lots of bytes" moved to here in XXX amount of seconds thats how you know it worked.
Tweakecho said:
what thread?
the OP says it must be Rooted. this is so ADB SHELL can gain access to the System partitions.
PS ( after you connect to adb make sure you grant root access to SHELL) (should pop up on your phone)
I'm pretty sure i used towel root to ease your fears.
when you use the last adb command you should see some feed back about moving some data... "lots of bytes" moved to here in XXX amount of seconds thats how you know it worked.
Click to expand...
Click to collapse
You are right. I misread it. Thanks.
I saw someone else mention flashify.
Anyone tried it & sure it works?
Also I'm considering trying terminal emulator. 1 person said it should work.
Any other opinions?
Worried I'll do it & have a problem haha.
Flashify would be great too if it worked.
Anybody actually tried either?
Hi Everyone,
I'm using a Samsung GT-N7105. It has 16GB of internal memory. It has no external SD card.
A few days ago my phone's screen went black. Everything else works fine, including touch, just that the screen is always completely black.
I took it to a repair centre. After the repair centre ran some tests, (they kept my phone for 2 days,) they confirmed it was the LCD screen problem (i.e. a hardware issue). Since that LCD screen is expensive to repair, I chose not to repair it.
So now I want to install Android Screencast on my phone. I connect my phone to my desktop, and to my surprise I discover that USB debugging isn't enabled anymore!
So I call the repair centre and ask them what software changes they made to my phone. Their response is:
1) The partition table has definitely NOT been altered.
2) "Your Android version has not been upgraded."
3) "We used a special software to format your phone." They declined to tell me what software they used, and they don't seem to know which partitions have been "formatted"! But they did say that "format" was not the same as "factory reset".
(Btw the people at the repair centre are non-native English speakers, whereas my first language is English, so it was hard to ask about technical details.)
Therefore my best guess about the software state of my phone is:
1) It's running stock Android 4.1.2, which it's been running since the first day I bought it
2) The bootloader should have no KNOX nonsense
3) Recovery should be stock recovery
4) A few partitions have been "formatted" to unknown states
5) There are no longer any pattern, PIN, or password locks on my phone. If my phone is on and it's been sitting idle, I just have to tap the home button, then swipe the screen, and it unlocks.
I can reconstruct the partition table of my internal memory if you guys need it. I did an entire dump of mmcblk0 about two months ago.
(Btw the size of that dump of mmcblk0 is 15,758,000,128 bytes, which is significantly less than 16GB, even if you count by 1000s instead of 1024s. Unimportant side question, but does anyone know why?)
**************
My main question is: How do I enable USB debugging ON ANDROID with the black screen restriction?
I've searched the forums, and in thread 2395047 (can't post links yet) the recommendation is to flash CWM recovery to get adb access. But keep in mind that my ultimate goal is to be able to install Android Screencast on my phone, so that I can regain full phone functionality (with the help of an attached computer screen). I don't quite see how adb access via CWM recovery can help me to achieve this goal.
Also, I've never actually used CWM recovery before and don't know how it works. One of my concerns is: Once I have flashed CWM recovery, and after I boot into recovery, do I immediately get adb access just by hooking up to USB cable to the desktop? Or do I first have to select some setting, which would be tough to do with a black screen?
Thanks in advance for all your help!
Ernest
(Note to mods: I accidentally posted this question earlier to xda assist when I wasn't logged in. You can delete the earlier duplicate.)
Hello,
I've been dealing with android for a while and have been a member of XDA for a while. In my time here I've searched for a solution to this issue many times all over the web and XDA but never came up with anything useful.
Of the possible solutions I've found, the most likely possibility is to use an OTG cable and mouse to interface your device but this requires you to see the screen which is not an option for you. adb in this situation is only useful if you want to retrieve data from your device. I do remember finding something on the web that could potentially help you turn on USB debugging but I'm having trouble finding it now. I'll keep looking but can't promise anything. In the meantime, try posting your question in the forum linked below.
http://forum.xda-developers.com/galaxy-note-2/help
If that doesn't help you find answers then try posting your question in the forum linked below.
http://forum.xda-developers.com/android/help
I hope this helps, good luck.
Hi Droidriven!
Thank you so much for taking the time to read and reply to my question.
Guess what, with the help of workdowg, I managed to work out a solution! My saving grace is that I'm running Android 4.1.2 and not one of the newer versions. My understanding is that if I was running one of the newer versions of Android, then I wouldn't even be able to get adb access via CWM recovery, because of the extra security measures. (Although I might be wrong about this point; I am still noob.)
I solved my problem in the following way:
1) Flash CWM recovery via ODIN Download mode
2) Boot into recovery, connect phone to desktop computer, open a command line terminal
3) Type "adb shell" to get a root shell in CWM recovery
4) In that root shell, type all the commands in the last code box at the end of the following post:
http://forum.xda-developers.com/showpost.php?p=63829295&postcount=27
(Much thanks to workdowg for this step)
5) Type "exit 0" to exit the shell in CWM recovery, then type "adb reboot"
6) Wait for my phone to reboot to Android
7) Type "adb devices", and now I see that I have adb connection to Android
After this, I was also able to successfully run Android Screencast with my phone. I can see my screen again!
So now, everyone please help me think of some useful search tags for this post / thread.
ErnestChia said:
Hi Droidriven!
Thank you so much for taking the time to read and reply to my question.
Guess what, with the help of workdowg, I managed to work out a solution! My saving grace is that I'm running Android 4.1.2 and not one of the newer versions. My understanding is that if I was running one of the newer versions of Android, then I wouldn't even be able to get adb access via CWM recovery, because of the extra security measures. (Although I might be wrong about this point; I am still noob.)
I solved my problem in the following way:
1) Flash CWM recovery via ODIN Download mode
2) Boot into recovery, connect phone to desktop computer, open a command line terminal
3) Type "adb shell" to get a root shell in CWM recovery
4) In that root shell, type all the commands in the last code box at the end of the following post:
http://forum.xda-developers.com/showpost.php?p=63829295&postcount=27
(Much thanks to workdowg for this step)
5) Type "exit 0" to exit the shell in CWM recovery, then type "adb reboot"
6) Wait for my phone to reboot to Android
7) Type "adb devices", and now I see that I have adb connection to Android
After this, I was also able to successfully run Android Screencast with my phone. I can see my screen again!
So now, everyone please help me think of some useful search tags for this post / thread.
Click to expand...
Click to collapse
I'll have to remember that, I wasn't aware of the difference in 4.1.2, I've not had to deal with 4.1.2, that's good to know.
Glad you got it going, now see if you can find one of your devices on eBay that is no longer working in one or another but still has a good digitizer and glass, you may find one cheap, then you can use the digitizer+glass from the used one to fix the one you are using.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
Glad you got it going, now see if you can find one of your devices on eBay that is no longer working in one or another but still has a good digitizer and glass, you may find one cheap, then you can use the digitizer+glass from the used one to fix the one you are using.
Click to expand...
Click to collapse
That's a really good idea, which I didn't even consider. (Maybe because I've never meddled with hardware before.)
Thanks!
Hi all,
I recently bought a CAT S41 and I'm wondering how to root it. The only other XDA post about this phone and rooting that I can find just has one person saying that kingoroot and one-click root did not work for him.
Things that I can figure -
1. I hear that kingoroot does not work after android 5.1 (yet they say it does on their website ? )
2. OEM Unlocking is available in the developer options and allows you to switch it to on ( Allows bootloader to be unlocked)
3. CAT isn't going to help this root be accomplished
I'm trying to look at other phones that are comparable and trying to find a route that I can root this phone. My end game for this is to get a root tutorial onto XDA that can be easily followed. I have asked the admins for a CAT S41 section also. The S41 comes with Android Nougat and a close to stock ROM. The only real difference is that it comes with a battery share app that can be very useful.
Thanks in advance for any input.
If you find anything, i would be interrested !
A root for this phone would be amazing. The stock ROM seems to have some bugs.
Hi!
I don`t own a CAT S41 but I`m planning to purchase one.
Found these online, so can anyone confirm the instructions work please.
ADB: http://neopodapsi.com/how-to-install-adb-and-fastboot-for-cat-s41/
TWRP: http://neopodapsi.com/how-to-install-twrp-custom-recovery-on-cat-s41/
ROOT: http://neopodapsi.com/how-to-root-cat-s41/
Thank You!
I will pay $50 to anyone that can root this device and can show the way for others to do the same. Message me if youre going to work in it
Thanks
I have this phone. Working fine till yesterday. Latest system update has my phone rebooting randomly.
I am trying to reach manufacturer to get a roll back to previous system.
Please disable auto update in your phones by now or you may find the same issue.
By the way the links provided by k.a.b.0 lead no nowhere but silly commercial surveys that then will redirect you to broken mediafire links.
Regards
perchera said:
I have this phone. Working fine till yesterday. Latest system update has my phone rebooting randomly.
I am trying to reach manufacturer to get a roll back to previous system.
Please disable auto update in your phones by now or you may find the same issue.
By the way the links provided by k.a.b.0 lead no nowhere but silly commercial surveys that then will redirect you to broken mediafire links.
Regards
Click to expand...
Click to collapse
Hei,
I had exactly the same experience and I tried EVERY single suggestion on-line to reboot in safe/recovery mode to fix the problem..
Then I chatted with the CAT support and I just found out that the problem is thier last update released !!!!!
actually it doesn't accept the SD card. So just remove the SD card and press the power button ...it should work fine.
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
...they also say that they are now aware of this problem and they are trying to fix it ...
So the trick should be to not use the SD card until the next update is released
evelix said:
Hei,
I had exactly the same experience and I tried EVERY single suggestion on-line to reboot in safe/recovery mode to fix the problem..
Then I chatted with the CAT support and I just found out that the problem is thier last update released !!!!!
actually it doesn't accept the SD card. So just remove the SD card and press the power button ...it should work fine.
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
...they also say that they are now aware of this problem and they are trying to fix it ...
So the trick should be to not use the SD card until the next update is released
Click to expand...
Click to collapse
Yes, me too have this problem..After till previus days have system update, and after upgrading I have reboot loop...First I have no idea what happening...I was try in recovery, wipe, system fctoring in recovery mode (yes, Im lost all my app and data), but still me boot loop making...And after all I was find, it external SD card was problem...Il try all sd card (Kingston, San Disk, Samsung, itd) was always problem with reboot loop... After all I was eject external card and was all in right. Can sameone telll Caterpillar (Bullit Group) for this very great problem. I really need external card with great capacity (128 GB) becao se i need it for my job...
perchera said:
I have this phone. Working fine till yesterday. Latest system update has my phone rebooting randomly.
I am trying to reach manufacturer to get a roll back to previous system.
Please disable auto update in your phones by now or you may find the same issue.
By the way the links provided by k.a.b.0 lead no nowhere but silly commercial surveys that then will redirect you to broken mediafire links.
Regards
Click to expand...
Click to collapse
Hey me too! It's a **** eh?
Contacting Cat support tomorrow fully expect to have to ship it to them.
Yes, it's the SD card as the Cat support confirmed by email. They introduced a bug in the latest update, they're aware of that and trying to fix it.
They also told me to see on a daily basis if there's a new update. Until then we will have to leave the SD card out - works fine, only a bit restricted (I'm doing a lot of data intensive stuff usually).
Hi ! since this topic is not only for root anymore, I post here.
Does anyone else have audio issues ? When I listen music, sometimes there are bugs, loops, music is jerky... it often goes in the day, but not always.
The bug occurs on differents music players (deezer, black player, soundcloud, ...) and more often when the screen is off.
Is this for all S41 or is it only me ?
TankiFrench said:
Hi ! since this topic is not only for root anymore, I post here.
Does anyone else have audio issues ? When I listen music, sometimes there are bugs, loops, music is jerky... it often goes in the day, but not always.
The bug occurs on differents music players (deezer, black player, soundcloud, ...) and more often when the screen is off.
Is this for all S41 or is it only me ?
Click to expand...
Click to collapse
Almost one year old question, but you are not alone. Even ring tones and notifications have this problem on my phone.
eazrael said:
Almost one year old question, but you are not alone. Even ring tones and notifications have this problem on my phone.
Click to expand...
Click to collapse
Actually I don't have this issue anymore. Try to see if your frimware is up to date.
bortski said:
I will pay $50 to anyone that can root this device and can show the way for others to do the same. Message me if youre going to work in it
Thanks
Click to expand...
Click to collapse
Add a 50$ from me as well.
Cannot find anything on unlocking bootloader or a twrp or a root software/apk for the device.
DISCLAIMER:
I just shared these steps in hope that it will help some of you achieve root on Cat S41. I am not, in any way, encouraging you to run these commands. YOU chose to follow the steps I have provided to the best of my knowledge. If you damage, soft-brick, hard-brick, or blow up an entire city because you did these steps and point your finger at me, I will laugh at you, make fun of you for not reading this disclaimer, and I will NOT take responsibility for stuff that you did.
I have not tried this on a Cat S41 so please let me know if it works. So I think it's like this:
EDIT: Oh yeah, I forgot that we can't even unlock bootloader. And the command in step 6 doesn't work without running su first. Which requires root and we can't get that in the first place. If you can figure out a workaround, that would, I'm sure, be appreciated by all of us here.
Install all the required drivers for Cat S41 on your PC.
Download ADB and Fastboot tools.
Open ADB.exe and connect your phone to your PC via USB cable.
Type adb devices to verify that your phone is recognized. Allow PC to connect to your phone by clicking allow on the prompt on your phone.
Type adb shell
Then we need to pull boot.img so I think you have to do dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
Now the boot.img should be copied to the internal storage of your Cat S41.
Install Magisk Manager/App on your phone.
Select Install -> Select an image to patch. Choose the boot.img.
Wait for it to finish the patch.
Copy the patched boot.img to the ADB folder on your PC.
In the ADB window on your PC, type exit to leave ADB shell.
Now type adb reboot fastboot
Once your phone has rebooted to fastboot, type fastboot flash boot boot.img
Alternatively, you could also type fastboot flash boot and then drag the patched boot.img into the command prompt window.
I hope this works. Try this at your own risk. If it actually works (I doubt it will), I don't want to $100. Keep it or donate it to someone else. Or give it to whoever can make a custom rom or TWRP for this device.