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 !
I found posts where I can root my phone, posts that say I don't have to change the recovery partition to root, posts where I need to root to change the setting within "/system/csc/feature.xml", posts to rename the sound file "/system/media/audio/ui/camera_click.ogg"...
I can't seem to get Android File Transfer to work (in hopes that could get to those system files), despite all the posts about that. Kies doesn't recognize when my phone is attached either. Clean installs, uninstalls, different USB cables, different ports... nothing.
So... do I need to root my phone to change the "feature.xml" file, or is there an easy way to change permissions, at least temporarily? I have WiFi File Explorer Pro and can download the file, but can't upload a new one. If I have to root the phone, I read I can do so without installing new software, ROM, recovery partition, or something to do with no installs keeping it clean. But several sets of instructions on how to root all include changing some software.
I'm lost... I just wanted to do one simple thing, or so I thought, and that was to add the menu option to turn the camera sound on & off. Can anyone sing out and help this Mac guy?
Why not just use ProCapture from the Play store? Imo its a better camera and has that option.
x714x said:
Why not just use ProCapture from the Play store? Imo its a better camera and has that option.
Click to expand...
Click to collapse
I'll check that out, thanks! In the meantime, if I do use the stock camera app, I'm still looking for help with the OP if anyone can enlighten me...
I coulda sworn that there's a built in option in the TW camera to do just that, turn the sound off... I suggest looking closer thru your settings for the camera.
Brian Gove said:
I coulda sworn that there's a built in option in the TW camera to do just that, turn the sound off... I suggest looking closer thru your settings for the camera.
Click to expand...
Click to collapse
TW camera?
This is the Verizon Galaxy S3, that option intentionally hidden.
specialNoob2012 said:
TW camera?
This is the Verizon Galaxy S3, that option intentionally hidden.
Click to expand...
Click to collapse
TW = Touchwiz (The launcher used in the SG3)
I'll revert back to TW to see.
Brian Gove said:
I coulda sworn that there's a built in option in the TW camera to do just that, turn the sound off... I suggest looking closer thru your settings for the camera.
Click to expand...
Click to collapse
I've read elsewhere that Samsung confirmed there is no switch for the camera shutter sound. The standard way to disable it is temporarily muting your phone's sounds.
- ooofest
This is exactly what I'm talking about...
Reverted to an ICS/TW ROM to take the pic. I dunno how you could miss it... :-/
Brian Gove said:
This is exactly what I'm talking about...
Reverted to an ICS/TW ROM to take the pic. I dunno how you could miss it... :-/
Click to expand...
Click to collapse
That's not current stock.
- ooofest
ooofest said:
That's not current stock.
- ooofest
Click to expand...
Click to collapse
So you're telling me they removed the option? You are correct in saying it's not stock, it's Synergy. But that option has been there ever since I got my phone in July...
I'm using the stock camera on my i535
I'm also rooted with stock ROM.
When my device is either in Silent or Vibrate mode, the shutter is Silent when I take single pictures.
On my previous S3 on sprint, the shutter was not silenced.
To remedy this, I did the following:
- using Root Explorer (or any file manager,) in
R/W mode, I went to:
system/media/audio/ui
and changed the following files:
shutter.ogg
to
shutter.ogg.off
camera_click.ogg
to
camera_click.ogg.off
Change mode back to R/O.
Remember these 2 files, or save the above 2 original files, and either restore, or remove the:
.off
from each file to restore settings back to the way they were prior to changing them.
Let me know how it works out
Brian Gove said:
So you're telling me they removed the option?
Click to expand...
Click to collapse
Not sure, but it wasn't on my phone since at least G7 was applied - I've always run stock.
I have noticed the toggle in CleanROM and others, but always as an add-on.
- ooofest
See this post by musclehead84:
http://forum.xda-developers.com/showpost.php?p=33028082&postcount=1
Works perfectly.
This enables the toggle feature in the stock camera menu
As mentioned in his post, credit goes to Freeza & s3.Zeke
Brian Gove said:
This is exactly what I'm talking about...
Reverted to an ICS/TW ROM to take the pic. I dunno how you could miss it... :-/
Click to expand...
Click to collapse
I don't know why you're trying to prove me wrong :-/ I've had this Verizon phone for several weeks, not entirely long but I understand technology, I can read English, I've searched and many, many Verizon customers have the same missing menu option. This same exact model phone on T-Mobile does have this menu option. I was on Tmo and played with the S3 for their 2-week trial period before returning it, leaving and going to Verizon, so I do have that familiarity and comparison.
If I rooted my phone, I could open & save the file /system/csc/feature.xml to change the setting <CscFeature_Camera_ShutterSoundMenu>false</CscFeature_Camera_ShutterSoundMenu> -- changing false to true and, in theory, put that menu option back on.
Biker1 said:
I'm using the stock camera on my i535
I'm also rooted with stock ROM.
When my device is either in Silent or Vibrate mode, the shutter is Silent when I take single pictures.
On my previous S3 on sprint, the shutter was not silenced.
To remedy this, I did the following:
- using Root Explorer (or any file manager,) in
R/W mode, I went to:
system/media/audio/ui
and changed the following files:
shutter.ogg
to
shutter.ogg.off
camera_click.ogg
to
camera_click.ogg.off
Change mode back to R/O.
Remember these 2 files, or save the above 2 original files, and either restore, or remove the:
.off
from each file to restore settings back to the way they were prior to changing them.
Let me know how it works out
Click to expand...
Click to collapse
Biker1 said:
See this post by musclehead84:
http://forum.xda-developers.com/showpost.php?p=33028082&postcount=1
Works perfectly.
This enables the toggle feature in the stock camera menu
As mentioned in his post, credit goes to Freeza & s3.Zeke
Click to expand...
Click to collapse
Thanks for the rooting tips, that's what I'm trying to achieve... root it to get to that "feature.xml" file in hopes it's a one-stop fix. But my skills at rooting are minimal. I've read many "how to" and seems very easy, but all say how you have to load a replacement recovery partition (or image or something similar). And in the same breath, other articles say you don't need to change or upload anything from stock to root the phone, but offer nothing past that. Not being familiar with rooting specifically, in general this sounds like a contradiction and could me my misunderstanding.
So what guide do I follow to root the phone AND keep it stock, no special ROMs or slimbean or anything like that? My only purpose is to temporarily change the R/W flag so I can alter the feature.xml file. Until JB, I'd prefer to keep everything stock.
specialNoob2012 said:
Thanks for the rooting tips, that's what I'm trying to achieve... root it to get to that "feature.xml" file in hopes it's a one-stop fix. But my skills at rooting are minimal. I've read many "how to" and seems very easy, but all say how you have to load a replacement recovery partition (or image or something similar). And in the same breath, other articles say you don't need to change or upload anything from stock to root the phone, but offer nothing past that. Not being familiar with rooting specifically, in general this sounds like a contradiction and could me my misunderstanding.
So what guide do I follow to root the phone AND keep it stock, no special ROMs or slimbean or anything like that? My only purpose is to temporarily change the R/W flag so I can alter the feature.xml file. Until JB, I'd prefer to keep everything stock.
Click to expand...
Click to collapse
Follow the instructions in section 2 if you have Windows.
If you don't have Windows, follow the appropriate steps as indicated. This method is painless
Just read the steps, keep a Window open on your pc with the instructions so you can follow them as you Root.
http://forum.xda-developers.com/showthread.php?t=1762709
Biker1 said:
Follow the instructions in section 2 if you have Windows.
If you don't have Windows, follow the appropriate steps as indicated. This method is painless
Just read the steps, keep a Window open on your pc with the instructions so you can follow them as you Root.
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
Thanks! I saw that very easy guide before, but that's where I get confused... doesn't flashing it make it add or alter something on the phone to make it considered non-stock? Or after I change that "feature.xml" file, I select "Unroot device" DO IT and go about my business (downloading JB when it's finally out, etc. without any worries)?
Also, if you've used the guide before, I don't see the Step 7 and 8 options, or do they appear after Step 6 is done? And some of those other options, specifically "Enable Hidden Menus", I can't find any details to know if that is an easier way to fix the file I'm looking for, or if "Show PhoneUtil" will do anything cool that I might want to play with.
specialNoob2012 said:
Thanks! I saw that very easy guide before, but that's where I get confused... doesn't flashing it make it add or alter something on the phone to make it considered non-stock? Or after I change that "feature.xml" file, I select "Unroot device" DO IT and go about my business (downloading JB when it's finally out, etc. without any worries)?
Also, if you've used the guide before, I don't see the Step 7 and 8 options, or do they appear after Step 6 is done? And some of those other options, specifically "Enable Hidden Menus", I can't find any details to know if that is an easier way to fix the file I'm looking for, or if "Show PhoneUtil" will do anything cool that I might want to play with.
Click to expand...
Click to collapse
Follow the steps.
In Step 6, several screens will appear one at a time.
Just press Enter for you agree, as explained in the tutorial.
Your S3 will begin Rooting.
Don't unplug your device during this process.
After you are Rooted, follow the steps after 6, beginning with step 7 of course
Steps 7 and after, you will follow after your device is Rooted.
These steps are separate from the on screen Rooting procedure.
Don't accept OTAs while Rooted, as that can end up badly
You can always Unroot, and accept an OTA, but there is always the possibility that Samsung may add something in the ROM that will prevent you from Rooting again until a Developer figures it out, if at all possible.
What is better to do is wait for a Developer to post the ROM from a leak, including JB ROMs, as the Developers will more than likely have a leaked ROM way ahead of the official ROM.
Biker1 said:
Follow the steps.
In Step 6, several screens will appear one at a time.
Just press Enter for you agree, as explained in the tutorial.
Your S3 will begin Rooting.
Don't unplug your device during this process.
After you are Rooted, follow the steps after 6, beginning with step 7 of course
Steps 7 and after, you will follow after your device is Rooted.
These steps are separate from the on screen Rooting procedure.
Don't accept OTAs while Rooted, as that can end up badly
You can always Unroot, and accept an OTA, but there is always the possibility that Samsung may add something in the ROM that will prevent you from Rooting again until a Developer figures it out, if at all possible.
What is better to do is wait for a Developer to post the ROM from a leak, including JB ROMs, as the Developers will more than likely have a leaked ROM way ahead of the official ROM.
Click to expand...
Click to collapse
So in order to root, something has to be installed, right? (I've read an occasional contradiction to that, but maybe I misunderstood.) At least this guide and java app give me comfort knowing I'm a few clicks away from unrooting it and again accepting OTA updates! Thanks for elaborating and your help!
Curious if you know... I've searched and didn't find any info, but some of the other options in there like "Enable Hidden Menus" and "Show PhoneUtil"... do you know what all these other options do or if there's some wiki on it somewhere I'm not finding?
specialNoob2012 said:
So in order to root, something has to be installed, right? (I've read an occasional contradiction to that, but maybe I misunderstood.) At least this guide and java app give me comfort knowing I'm a few clicks away from unrooting it and again accepting OTA updates! Thanks for elaborating and your help!
Curious if you know... I've searched and didn't find any info, but some of the other options in there like "Enable Hidden Menus" and "Show PhoneUtil"... do you know what all these other options do or if there's some wiki on it somewhere I'm not finding?
Click to expand...
Click to collapse
At the moment I'm uncertain.
But I suggest to keep it simple for now, and follow the Rooting procedure as discussed.
Section 2 in the link shows you what you need to dl onto your pc regarding the drivers, etc.
Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!
bohemianRhapsody said:
Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!
Click to expand...
Click to collapse
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.
root is easy
bohemianRhapsody said:
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.
Click to expand...
Click to collapse
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition
it0 said:
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition
Click to expand...
Click to collapse
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?
Lukas_a_1996 said:
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?
Click to expand...
Click to collapse
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.
it0 said:
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.
Click to expand...
Click to collapse
Thanks for the reply . I tried to run the command in impactor but whatever i do i get "Signature bugs unavailable" could it be that i have the wrong ADB drivers installed or is my Impactor setup wrong?
Edit: yeah im running 4.1.2 Build A1001231
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
All the adb commands basically work but nothing works with impactor i just get error
it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
Bump!
How to Root Medias N05e
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks
nguyenbuulam said:
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks
Click to expand...
Click to collapse
There is a way for temp root N05E, basically u can use pm disable command or other su stuff. But u cannot mount system rw right now.
Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working
How to enter recovery mode?
Despite starting this thread, in the end I never did bother to attempt rooting.
Anyway, unfortunately now the phone refuses to boot. Not triggered by anything obvious, haven't installed any new software recently, etc. Just hung one day and then when I removed and re-inserted the battery, it won't get any further than the "docomo" splash screen. I.e. the OS doesn't appear to be getting bootstrapped at all. The "docomo" splash screen appears and disappears then the phone sits there with both screens powered up but blank.
As it happens, I had ADB Debug enabled in the developer options at the time, so I've tried to see if I can adb shell into the device, but no luck. Not surprised as it's clearly not getting far enough into the boot for that to work.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?
bohemianRhapsody said:
Despite starting this thread, in the end I never did bother to attempt rooting.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?
Click to expand...
Click to collapse
In recovery mode, clear cache, etc..
To get there hold volume down and power at the same time,then you'll see the broken android then wait/ press vol down a couple of times to see the menu.
GRbit said:
Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working
Click to expand...
Click to collapse
did you ever figure out the recovery keys?
hamishhhhs said:
did you ever figure out the recovery keys?
Click to expand...
Click to collapse
No I didn't(
I'm actually sold this phone and lost interest in the topic.
GRbit said:
No I didn't(
I'm actually sold this phone and lost interest in the topic.
Click to expand...
Click to collapse
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far
hamishhhhs said:
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far
Click to expand...
Click to collapse
Sorry, but this was too long time ago. Nothing left
GRbit said:
Sorry, but this was too long time ago. Nothing left
Click to expand...
Click to collapse
how would j be able to get the files from my phone?
hamishhhhs said:
how would j be able to get the files from my phone?
Click to expand...
Click to collapse
I dunno man.
I've already described (in the first post you have quoted) what I achieved with this github repo https://github.com/android-rooting-tools/android_run_root_shell . That's all I've got.
I recently bought a cheap candy bar phone (MobiWire Sakari), for nostalgic purposes mostly, and learnt it ran a simplified version of android 4.4.2.
It meant no developer mode, no playstore and no settings past personalisation (tapping build number in the 'about' section does nothing).
It has facebook lite installed and has the option to install WhatsApp. It does this by downloading a special version off the WhatsApp website and allowing you to install it. When you try download and install other apps, it comes up with an error saying it can't be installed (I've tried many).
I understand that a lot of apps won't work, being a 2.4" keypad phone, but there are apps available to make the keypad experience more enjoyable - as you currently have to tap the keys a few times for each letter (I did say I wanted nostalgia, but T9 would be nice). Not to mention, it would simply be great to have a nostalgic experience with an up-to-date OS (at a dirt cheap price).
Anyone have any idea of how to root the device, enable app installation (the 'install from unknown sources' option is not available in the settings), or extract some of the code from the working WhatsApp apk and insert it into other apks (appologies if it doesn't work like that, I'm a noob in the developer world).
As I said, I can't enable USB debugging for any ADB installations. I can get into the factory recovery mode and can access ADB update but this doesn't help me as ADB install can't work.
Thanks for reading and any help would be great.
I am also interested in this
Can you post a screenshot of the about screen?
spoofykid said:
I recently bought a cheap candy bar phone (MobiWire Sakari), for nostalgic purposes mostly, and learnt it ran a simplified version of android 4.4.2.
It meant no developer mode, no playstore and no settings past personalisation (tapping build number in the 'about' section does nothing).
It has facebook lite installed and has the option to install WhatsApp. It does this by downloading a special version off the WhatsApp website and allowing you to install it. When you try download and install other apps, it comes up with an error saying it can't be installed (I've tried many).
I understand that a lot of apps won't work, being a 2.4" keypad phone, but there are apps available to make the keypad experience more enjoyable - as you currently have to tap the keys a few times for each letter (I did say I wanted nostalgia, but T9 would be nice). Not to mention, it would simply be great to have a nostalgic experience with an up-to-date OS (at a dirt cheap price).
Anyone have any idea of how to root the device, enable app installation (the 'install from unknown sources' option is not available in the settings), or extract some of the code from the working WhatsApp apk and insert it into other apks (appologies if it doesn't work like that, I'm a noob in the developer world).
As I said, I can't enable USB debugging for any ADB installations. I can get into the factory recovery mode and can access ADB update but this doesn't help me as ADB install can't work.
Thanks for reading and any help would be great.
Click to expand...
Click to collapse
Probably won't work, installing other apps requires having a proper "package installer" like other android devices that can install apps. By your description, installation of apps on that device doesn't work the same as for other android devices.
You can attempt to adb sideload, if the device has a sideload option in recovery.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Probably won't work, installing other apps requires having a proper "package installer" like other android devices that can install apps. By your description, installation of apps on that device doesn't work the same as for other android devices.
Click to expand...
Click to collapse
It has some form of package installer as it installs Whatsapp when you first turn on the device. When you try install a different apk, it seems to start the package installer but stops when it doesn't recognise the apk file. I bought another device with a different build number, enabling me to enter developer mode and installed apps using this method: https://forum.xda-developers.com/showpost.php?p=76141643&postcount=23
Droidriven said:
You can attempt to adb sideload, if the device has a sideload option in recovery.
Click to expand...
Click to collapse
I can enter stock recovery, however, adb sideload is only able to install update.zip files. Or is there a method of installing apk files as well through the "apply update from ADB" method? Or is there usually another option showing to be able to adb sideload an apk file? Here is someones post showing the stock recovery https://forum.xda-developers.com/showpost.php?p=76105681&postcount=13
Thanks for your help.
metallas said:
Can you post a screenshot of the about screen?
Click to expand...
Click to collapse
Please see the photo
..
Sent from my LGL84VL using Tapatalk
Droidriven said:
Have you seen this?
https://forum.xda-developers.com/general/help/mobiwire-sakari-install-apps-t3726398
Click to expand...
Click to collapse
There was no resolution in that thread at the time so I asked another question with more detail. There still is no resolution for devices which cannot access developer mode.
Droidriven said:
By the way, the device name "Sakari" might help when used in your searches.
Click to expand...
Click to collapse
"Sakari" does not exist in XDA as a device unfortunately.
Droidriven said:
You can attempt to adb sideload, if the device has a sideload option in recovery.
Click to expand...
Click to collapse
Is this possible given my circumstances?
spoofykid said:
There was no resolution in that thread at the time so I asked another question with more detail. There still is no resolution for devices which cannot access developer mode.
"Sakari" does not exist in XDA as a device unfortunately.
Is this possible given my circumstances?
Click to expand...
Click to collapse
I didn't say to use the name Sakari to search XDA, I meant for you to use it in Google searches.
You don't have a sideload method. I doubt you'll be able install apps. The facebook lite and Whatsapp that you installed are probably built just so it could be used on that device. You'd have to try modifying other apps in the same manner that these two were modified in order for them to work on that device.
All in all, WAY more trouble than its worth. The device probably wouldn't perform well with those apps installed, even if you "could" get them to install.
Sent from my LGL84VL using Tapatalk
**SOLVED - I restared the phone and everything works as it should. Follow trouble shooting lesson #1 - Unplug and plug it back in**
I'm looking for help to troubleshoot my text messaging after using ADB to uninstall some packages.
The phone is a Oneplus 9 from Tmobile, and I have a verizon account/SIM card. My original intention was to completely delete the bloatware / unused applications from my phone but the script I was running (Tomatot's script) is not updated for Android 11 and I ended up abandoning that route and instead just used the ADB commands to uninstall. As such, I did unlock the bootloader, installed TWRP, and used TWRP to run a version of the Tomatot script. I noted nothing changed, and did not try to revert or undo the Tomatot script.
I then went to ADB commands and uninstalled the below list of packages:
package:com.oneplus.calculatorpackage:com.android.cts.priv.ctsshimpackage:com.oneplus.gamespacepackage:com.sprint.ecidpackage:com.google.android.cellbroadcastservicepackage:com.sprint.w.installerpackage:cn.oneplus.photospackage:com.tmobile.m1package:com.qualcomm.uimremoteclientpackage:com.oneplus.brickmodepackage:com.netflix.partner.activationpackage:com.tmobile.pr.mytmobilepackage:com.oneplus.factorymode.specialtestpackage:com.google.ar.corepackage:com.oneplus.android.cellbroadcast.overlaypackage:com.google.android.marvin.talkbackpackage:com.oneplus.factorymodepackage:com.android.eggpackage:com.google.android.apps.tachyonpackage:com.sprint.ms.cdmpackage:net.oneplus.pushpackage:com.android.dreams.basicpackage:com.google.android.apps.wellbeingpackage:com.tmobile.pr.adaptpackage:com.android.bipspackage:com.android.cellbroadcastreceiverpackage:cn.oneplus.oemtcmapackage:com.oneplus.filemanagerpackage:com.google.android.ttspackage:com.sprint.ce.updaterpackage:com.google.android.videospackage:com.oneplus.faceunlockpackage:com.google.android.feedbackpackage:com.oneplus.opbugreportlitepackage:com.tmobile.rsuadapter.qualcommpackage:com.oneplus.screenrecordpackage:com.android.providers.partnerbookmarkspackage:com.android.wallpaper.livepickerpackage:com.oneplus.bttestmodepackage:net.oneplus.commonlogtoolpackage:com.android.bookmarkproviderpackage:com.android.cts.ctsshimpackage:com.android.wallpaperbackuppackage:com.sprint.ms.smf.servicespackage:com.google.android.apps.youtube.musicpackage:com.android.traceurpackage:com.google.android.cellbroadcastreceiverpackage:com.tmobile.rsuapppackage:com.tmobile.rsusrvpackage:com.android.cellbroadcastreceiver.overlay.common
Can anyone here take a look at my uninstalled packages and easily tell which one is related to text messaging? I would hope to easily find the one or two from this list instead of re-enabling each one and see if texting is restored.
At this point my options are - start enabling packages via ADB commands to see if texting is fixed, or factory reset -> verify texting and other functionality works -> use ADB to uninstall packages and test texting/other functions after each package.
Thanks for any help in advance!
(I did find a thread about using Magisk Debloater to remove bloat and will look into that method since the Tomatot script with TWRP did not work for me. First I need to fix texting or my wife will kill me)
RonnieDoitch said:
I'm looking for help to troubleshoot my text messaging after using ADB to uninstall some packages.
The phone is a Oneplus 9 from Tmobile, and I have a verizon account/SIM card. My original intention was to completely delete the bloatware / unused applications from my phone but the script I was running (Tomatot's script) is not updated for Android 11 and I ended up abandoning that route and instead just used the ADB commands to uninstall. As such, I did unlock the bootloader, installed TWRP, and used TWRP to run a version of the Tomatot script. I noted nothing changed, and did not try to revert or undo the Tomatot script.
I then went to ADB commands and uninstalled the below list of packages:
package:com.oneplus.calculatorpackage:com.android.cts.priv.ctsshimpackage:com.oneplus.gamespacepackage:com.sprint.ecidpackage:com.google.android.cellbroadcastservicepackage:com.sprint.w.installerpackage:cn.oneplus.photospackage:com.tmobile.m1package:com.qualcomm.uimremoteclientpackage:com.oneplus.brickmodepackage:com.netflix.partner.activationpackage:com.tmobile.pr.mytmobilepackage:com.oneplus.factorymode.specialtestpackage:com.google.ar.corepackage:com.oneplus.android.cellbroadcast.overlaypackage:com.google.android.marvin.talkbackpackage:com.oneplus.factorymodepackage:com.android.eggpackage:com.google.android.apps.tachyonpackage:com.sprint.ms.cdmpackage:net.oneplus.pushpackage:com.android.dreams.basicpackage:com.google.android.apps.wellbeingpackage:com.tmobile.pr.adaptpackage:com.android.bipspackage:com.android.cellbroadcastreceiverpackage:cn.oneplus.oemtcmapackage:com.oneplus.filemanagerpackage:com.google.android.ttspackage:com.sprint.ce.updaterpackage:com.google.android.videospackage:com.oneplus.faceunlockpackage:com.google.android.feedbackpackage:com.oneplus.opbugreportlitepackage:com.tmobile.rsuadapter.qualcommpackage:com.oneplus.screenrecordpackage:com.android.providers.partnerbookmarkspackage:com.android.wallpaper.livepickerpackage:com.oneplus.bttestmodepackage:net.oneplus.commonlogtoolpackage:com.android.bookmarkproviderpackage:com.android.cts.ctsshimpackage:com.android.wallpaperbackuppackage:com.sprint.ms.smf.servicespackage:com.google.android.apps.youtube.musicpackage:com.android.traceurpackage:com.google.android.cellbroadcastreceiverpackage:com.tmobile.rsuapppackage:com.tmobile.rsusrvpackage:com.android.cellbroadcastreceiver.overlay.common
Can anyone here take a look at my uninstalled packages and easily tell which one is related to text messaging? I would hope to easily find the one or two from this list instead of re-enabling each one and see if texting is restored.
At this point my options are - start enabling packages via ADB commands to see if texting is fixed, or factory reset -> verify texting and other functionality works -> use ADB to uninstall packages and test texting/other functions after each package.
Thanks for any help in advance!
(I did find a thread about using Magisk Debloater to remove bloat and will look into that method since the Tomatot script with TWRP did not work for me. First I need to fix texting or my wife will kill me)
Click to expand...
Click to collapse
You def removed brickmode and unsure if you can still connect through edl to msm tool. Btw this would be your only option is to restore everything with msm tool for your variant. Or fastboot flash whatever build your on back to device.
Index of /list/Unbrick_Tools
mattie_49 said:
You def removed brickmode and unsure if you can still connect through edl to msm tool. Btw this would be your only option is to restore everything with msm tool for your variant. Or fastboot flash whatever build your on back to device.
Index of /list/Unbrick_Tools
Click to expand...
Click to collapse
Thank you for the response. Brickmode, as far as I can tell from internet searching, is related to Oneplus's 'Zen Mode' which I do not need or want. If I am mistaken please point me to a discussion about this particular package so I can reinstall it if its required for recovering from bricking a phone. I think its a deceptively named package.
I started re-enabling the packages above and after a phone restart all my texts came back. I then un-installed the packages one by one and none of them affect texting. Soooo I think it was the phone restart that fixed it. As always, turn it off and back on first to see if that fixes the problem.
RonnieDoitch said:
Thank you for the response. Brickmode, as far as I can tell from internet searching, is related to Oneplus's 'Zen Mode' which I do not need or want. If I am mistaken please point me to a discussion about this particular package so I can reinstall it if its required for recovering from bricking a phone. I think its a deceptively named package.
I started re-enabling the packages above and after a phone restart all my texts came back. I then un-installed the packages one by one and none of them affect texting. Soooo I think it was the phone restart that fixed it. As always, turn it off and back on first to see if that fixes the problem.
Click to expand...
Click to collapse
Glad you got it worked out.
RonnieDoitch said:
Thank you for the response. Brickmode, as far as I can tell from internet searching, is related to Oneplus's 'Zen Mode' which I do not need or want. If I am mistaken please point me to a discussion about this particular package so I can reinstall it if its required for recovering from bricking a phone. I think its a deceptively named package.
I started re-enabling the packages above and after a phone restart all my texts came back. I then un-installed the packages one by one and none of them affect texting. Soooo I think it was the phone restart that fixed it. As always, turn it off and back on first to see if that fixes the problem.
Click to expand...
Click to collapse
Glad you got it worked out. Maybe try looking into this thread.
Thread '[ADB DEBLOAT] [OOS 12, 11 & Custom ROMs] [2021.12.20 - v2.0] Extreme debloat your OnePlus 9' https://forum.xda-developers.com/t/...-v2-0-extreme-debloat-your-oneplus-9.4283263/