Related
It looks like we have to move our discussion here, so I went ahead and started a thread.
As of now, there is root for the mediapad, but the only way to root the springboard is by flashing it with a rooted mediapad cust.img - which gives you root but loses your 4g.
So for us Springboard users, we either need root or a way to get 4g back if flashing it as a mediapad. Anybody with thoughts or leads or any know-how?
Finally,
Special room for Huawei Media Pad created,
Thanks to TS
I'm very glad,
Now i'm waiting the master in here to modified this device
cause i still newbie
Actually I Prefer The 3G More THan The 4G For Some Reason I Felt 4G Wasnt Stable Enough....So Im Enjoiying My Mediapad In 3G More Than My Springboard In 4G......
from the other thread, Rumbi wrote:
Yap, only thing you have to do is install Superuser and Busybox from Market and copy "su" from /hwcust/oversea_hk/preload/fixed/bin/ to /system/xbin (e.g. with ES File Explorer with root and r/w enabled), and you are ready to go
I've installed SU & BusyBox. I cannot move the SU file over to /system/xbin. A message tells me that I am not root.
However, when I run Root Check Basic I am told I have root.
I ran Root Check before & after I installed S7-301u V100R001C232B012(Root_version) and Root Check said I did not have root.
So the real question is, How do I really know if I have root?
*****
Actually I installed BusyBox Installer. I'm asked to pick a version to install:
1.19.3
1.19.2
1.18.5
1.18.4
1.17.1
None of these will install.
I also have the option to install a "Custom Tune" is there one? I'd gladly pay for BusyBox pro to get BusyBox running
*******
I powered off the device. Put my sdCard back in (the rooted firmware was removed from it). Then installed the SuperUser update from the market.
Ran that - it said everything was OK. Then I forced it to update - it crashed - so I force closed it. I then realized I could not run the original SuperUser app anymore.
Next, I opened up Root Explorer and was able to move the su file over to the xbin. But now BusyBox is not acting right - It said that it was having problems installing, and I'd need to reflash (or reload - I can't recall) the rom.
I'm rebooting, and going to try to install BusyBox....to be clear on which BusyBox..it's this one:
https://market.android.com/details?...t=W251bGwsMSwyLDEsInN0ZXJpY3Nvbi5idXN5Ym94Il0.
*****
Just realized in Root Explorer, to tap the little gray box at the top. After you tap it it should read "Mount R/O"
Now you can long press a folder/file and change the read/write permission.
Rumbi,
You said to r/w enabled the su file....is that check ALL the boxes?...Read, Write, Execute Special?????
IIRC, i had some problems with busybox, too. Copy the file from the attachment to /system/xbin and try the installer again.
And i said to enable r/w support for the /system folder. There are two checkboxes in ES File Explorer. First checkbox is enable root permission for ES File Explorer and second checkbox is "Mount / and /system writable".
Now you should be able to copy whatever file you want to /system/xbin. That's how i have done it. If you have any further questions, feel free to ask. I'll try to explain.
PS. You don't ne to alter file permissions of the su-binary but mine are "rwx r-x r-x".
Rumbi, how do you feel about the High resloution mode, does it slow the tablet down? Have you had a chance to use any tegra 2 devices and if so how does the mediapad with the snapdragon compare when in standerd/high-res mode?
Nothing to complain about the Hi-Res-Mode but i don't have any Tegra2-Devices to compare, sorry.
Haven't tried any games in hi-res-mode but normal usage is just fine.
Thanks. Ill try this out. When i try to install busybox it hangs first, then i force close and run again. Then i get the message about reflashing Rom. But i know i have root. I installed connectbot and ran su and got #
Heres how i got root (im away from my pc right now so i try to be as accurate as possible) :
Installed Hauwei modified rom (its the one that says "(root) " in the file name.
Installed Root explorer
Installed Superuser
Install busybox
Install Connectbot
Put my microsd back in (with the firmware AKA dloa folder removed)
I could not get root explorer to allow rw permissions until i slid the sd card out and back in whil the device was on.
Then i ran connectbot as local and typed su hit enter then superuser popped up asking fo allow connectbot to access. Hit allow an type su hit enter an you should get # This took 3 reinstalls of the firmware to work wjthout errors. The first times resulted in superuser needing to be force closed.
I also ran superuser and went into settings and updated it eventhouh its not neede. There i got a read out saying that busybox is not installed, but it does say i have root.
Sent from my HUAWEI MediaPad using xda premium
Honestly i havent noticed a big difference between high resolution an standard.
The only issue with high res is the small icons and buttons are difficult to hit sometimes
Sent from my HUAWEI MediaPad using xda premium
Do i need to unzip this file first?....
.... Nevermind... I unzipped it and put the busybox file in th system/xbin folder.
I installed busybox installer by JRummy16. This time and it worked!!!!!!!
Now its on to figuring out 4G and tryiying to use it as a phone.
What is the xml file i need to edit?
Sent from my HUAWEI MediaPad using xda premium
Good, that you have worked it out now What exactly do you want to do? To get to the hidden menu, you have to open the calculator and type: ()()2846579()()=
To edit the XML-Files, you have to extract the cust.img... But now that you have root, yo can edit whatever is available via root explorer
€dit: To get 4G working again, maybe with someone with an original Springboard (not a flashed one) can copy the folder /system/lib/. This should be possible even without root. I think it has something to do with the ril-files...
after updating my mediapad to S301uV100R001C232B012, i have problem with 2x Client (RDP client) now, few second after conecting to rdp session, is app 2X client crashing, with error 2x Client has stopped unexpectedly (process com.tux.client), is here anybody with this problem? thanks...
Rumbi said:
€dit: To get 4G working again, maybe with someone with an original Springboard (not a flashed one) can copy the folder /system/lib/. This should be possible even without root. I think it has something to do with the ril-files...
Click to expand...
Click to collapse
How about this - link
I'll look at it, thank you And these are the libs from an unmodified Springboard, aren't they?
yes indeed. I broke the silly thing, so I haven't played with it much. guess I will have to call about how to get it fixed.
knoxjon said:
How about this - link
Click to expand...
Click to collapse
Even though I have no clue of what to do with this, THANKS! I tried to open an .so file in notepad, but no luck, but I'm assuming that the geniuses here know what to do.
On an off-root topic - How do you take a screen cap? I accidentally did it yesterday while my MediaPad was lagging, but don't know how I did it.
The Hi Suite that comes with the device can do this, but require a computer and usb hooked up. Useful, but not as practical as doing it from the tablet itself.
The *.so files are a bit like drivers for the internal components. I'll try to find differences between T-Mobile and Huawei so maybe we get 4G working again.
tedbone said:
Even though I have no clue of what to do with this, THANKS! I tried to open an .so file in notepad, but no luck, but I'm assuming that the geniuses here know what to do.
On an off-root topic - How do you take a screen cap? I accidentally did it yesterday while my MediaPad was lagging, but don't know how I did it.
The Hi Suite that comes with the device can do this, but require a computer and usb hooked up. Useful, but not as practical as doing it from the tablet itself.
Click to expand...
Click to collapse
I'm not sure how to screencap. It's so easy on CM that I've gotten lazy. Plus I rarely do it. I know there are a ton of apps for that, tho. But you could probably google "gingerbread screen capture" and find a better answer. But not with gingerbread. I'm blanking on the name for this version of android.
knoxjon said:
I'm not sure how to screencap. It's so easy on CM that I've gotten lazy. Plus I rarely do it. I know there are a ton of apps for that, tho. But you could probably google "gingerbread screen capture" and find a better answer. But not with gingerbread. I'm blanking on the name for this version of android.
Click to expand...
Click to collapse
Honeycomb
I've been Googling searches like that, and end up with actual screen shots of Honeycomb os..I'll keep looking...
Tried this (from here), but no luck:
Screen capture
Android natively supports the ability to capture a screenshot by method of pressing both the power and volume-down buttons at the same time on an Android device. This native support was first included within the Android 4.0 (Ice Cream Sandwich) update, which is first seen on the Galaxy Nexus smartphone.[86] Previously, Android did not feature native support for screen capturing which would have likely been due to security concerns. Furthermore, prior manufacturer and third-party customizations as well as using a PC connection (DDMS developer's tool) were the only known methods of capturing a screenshot on Android.
I've looked through the *.so files and many of them are exactly the same, but some are different. One file caught my interest. I've attached it here for anyone who wants to try. Please only use it, if you have a T-Mobile Springboard with flashed root Firmware. Copy the content of the zip-file to /system/lib and overwrite the existing file. But make a backup first! After copying you have to set the correct file permission (rw- r-- r--) and reboot the tab. Hopefully 4G works again with this little trick.
Disclaimer: rooting your phone entails risk. You may brick it, cause it to catch fire, cause it to form the first node in the Skynet network, or otherwise render it inoperable. Please read the directions carefully to ensure that nothing unexpected happens. This rooting tool is as safe as I can make it, but there's never any guarantees.
After a very helpful suggestion from Surge1223, I managed to take an existing root exploit for the Xperia and modify it to work on 4.3 with SELinux enforcing. This installs su, SuperSU, and the necessary support files to enable the root.
This rooting process should work with a wide range of Android devices, particularly those running Linux Kernel before 3.5.5 (which most Android 4.3 ROMs use.) It 's known to work for may GS4 variants and is harmless if it fails to work (no "Warranty Void" flags get set.)
Again, using this WILL NOT set the "Knox Warranty Void" flag.
For a video showing the steps to root, see Tomsgt's awesome work here.
There's another video from owenbeals here.
A hint to people having problems using this:
If you use XDA to e-mail me a question, SET YOUR XDA ACCOUNT UP TO ACCEPT MAIL.
If you are set up to refuse mail, then your question will be ignored. Actually, you shouldn't e-mail me. PM or post here.
Step 1 - setting up the USB drivers
Before you try using this rooting program, you'll need to have the USB drivers installed for your phone.
The easiest way to do this is to install Samsung Kies. If Kies sees your phone, you're OK for the drivers.
If you don't have the drivers working, the root installer will hang at "waiting for device..."
Step 2 - Enable USB Debugging
The second thing you must do is to enable USB debugging on your phone. Go to "Settings", "More...", then "Developer Options".
If "Developer Options" doesn't appear, then you'll need to enable it - go to "Settings", "More", "About Phone". Scroll down so the "Build Number" is visible, then tap on that several times until developer mode is enabled.
In Developer Options, make sure "USB Debugging" is checkmarked.
Step 3 - Enable USB ADB Access
Make sure that your computer is allowed to use USB debugging on your phone. To do this, unplug your phone and unlock it. Then, plug in the USB cable.
If you see an "Alllow USB debugging?" window pop up, tap on the "Always allow from this computer" to check it, then tap OK.
If you don't see that popup, it's OK, you should be OK to proceed.
That's it for the phone.
Step 4 - Unzip the saferoot.zip
Then you need to unpack the attached ZIP file somewhere onto your PC.
You should have the following when done:
- a file called "install.bat"
- a file called "install.sh"
- a folder called "files"
Step 5 - Root your phone
Double click on the "install.bat" to run the root. It will root and reboot your phone. Once that's done, you're rooted!
The first thing that the install script will ask you is whether or not to install Busybox. Busybox is a program that provides a fairly extensive set of Linux shell utilities that a Unix user would expect to see. If you're not going to be using the shell (terminal emulator or adb shell) then you may not want to install Busybox. You may, however, find that some root-required utilities assume that Busybox is installed.
If SuperSU asks you to update the su binary, choose the "Normal" method.
If SuperSU asks you about disabling Knox, allow it.
This exploit will NOT set the Knox Warranty Void flag. It will set the "Custom" flag, but that's nothing to worry about.
While you're running this, you'll need to keep the phone awake and watch both the computer running the rooting script and your phone.
You shouldn't unplug the phone unless you're prompted by the rooting script. Leave it connected until it's done.
Rooting on Linux and MacOS
The saferoot script has a copy of adb for MacOS and for Linux included.
To run this root, download and unzip the zip file. Open a shell window, use "cd" to change to the directory where you unpacked the zip, and type "sh ./install.sh". The OS will be detected automatically and the root should run basically as described above.
If the embedded adb fails, you'll need to have the Android Debugging Bridge (adb) installed and configured and on your path. You can test that it's ready by opening a shell (Terminal) window and typing "adb shell". If you get a shell prompt on the phone, type "exit" and you're ready to go.
Notes
Don't try to download this onto your phone and run it from there. That won't work, at least for the i545 (i.e. running it from the Terminal Emulator app will fail.)
Having troubles getting adb connected? There are several possible causes and solutions.
There are cases where people can't get the connection working unless they toggle the USB connection type from Camera to Media and back. Perhaps that may help getting it to work. Toggling the "Enable USB Debugging" apparently helps in some cases as well.
Others report that using these Samsung USB drivers resolve connectivity issues. Of course, these drivers are for Samsung phones. Install the right stuff for your phone.
Important - please read
If you fail to read this, you will be taunted.
1. You can't install custom recovery and custom ROMs on a phone with a locked bootloader. This rooting program does not unlock your bootloader and won't allow you to flash custom on a locked device. However, NOTHING allows flashing a custom recovery on a bootloader locked phone at the moment. See Safestrap for a way to install some custom ROMs.
2. Resetting the "Custom" and open padlock indication during boot can be worked around using the Xposed Framwork and Wanam Xposed. Get those two from the Play Store. In Wanam, tick "Security Hacks", "Fake System Status".
3. If Saferoot fails with the messages
"Your kernel is patched!
This device is not supported."
That means that your device's Linux kernel has been updated to keep Saferoot from working. Unless you can downgrade to an older kernel, you can't use Saferoot.
Reported Successes
Here's a list of phones and reported builds where this has been verified to work.
AT&T Galaxy Note 2 (SGH-I317), Android 4.3
AT&T Galaxy S3 (SGH-i747), MJB
AT&T Galaxy S4 (SGH-i337) MK2,MK6
AT&T Galaxy S4 zoom
Bell Mobility i337,MK6
Canadian Galaxy S4 SGH-I337M
Digicel (Jamaica) i9500, MK1
d2vzw s3 with the 4.3 update
Galaxy NX Camera, JDQ39
Galaxy Legend SCH-I200,MK2
Galaxy Note 2 GT-N7100, MK9
Galaxy Note 2 N7105 4.3
GT-I9192, MK4 (ML2 does not work)
Google Glass, (XRT73B), XR14
i605
International Galaxy S4, I9505: MH6, MH8, MJ5, MKE, MKF
I9500: MJ8, MK1
Kindle Fire HD
LG Optimus F3 - T-Mobile
LG Escape -P870 - ATT
MK4 Build Date 13.11.2013
Razr HD 9.30.1 OTA
Razr M 98.18.94,98.30.1
Samsung Exhilarate SGH-I577, Android 4.0.4, Build LH3
Samsung GT-I9192, UBUBMK4
Samsung Galaxy Tab 2 GT-P5513
Samsung Galaxy S4 Mini LTE (GT-I9195), MJ7
Samsung i547, Android 4.1.2
Sprint Galaxy S3 (SPH-L710), MK5
Sprint Galaxy S4 Mini SPH-L520
Sprint Galaxy S4 SPH-L720,MK2 (NA2 does NOT work)
Sprint Galaxy S4 (SPH-L720T), MK5
T-Mobile Galaxy S4 SGH-M919 JFLTETMO, MK2
T-Mobile Galaxy Note 2 SGH-T889, MK7
Telcel (Mexico) SGH-i337M, MK6
Telus Note 2 SGH-I317M
Verizon Galaxy Note 2 Android 4.3
Verizon Galaxy S3 I9300 - LF2
Verizon Galaxy S3 SCH-I535
Verizon Galaxy S3 Mini, SM-G730V, MI9
Verizon Galaxy S4 (SCH-i545) ME7,MJ7,MK2
Verizon Galaxy S4 (SCH-i545L) MG6, MK4
Verizon Galaxy S4 Mini SCH-I435, MK5
Verizon Galaxy S4 Developer Edition, I1545OYUAMDK
Verizon HTC One
Verizon SCH-I200PP, MK2
xt907, xt925/6 & mb866
Edits:
12/12/13: This version of the zip file includes the adb.exe so you don't need to install ADB just for this.
I've also changed it so you shouldn't have to unzip to any special place.
12/13/13: I've swapped out Superuser for SuperSU. This version also installs busybox for you once the phone finishes rebooting.
12/14/13: Fixed install of busybox. Install SuperSU as Chainfire wants it: called Superuser.apk, installed into /system/app.
12/14/13: Move "Look at your phone and give permission" message to the top of the script.
12/15/13: Update source distribution to correspond to updates.
12/16/13: Rename to saferoot as it's not just for MJ7.
12/17/13: Update to fix "text file busy" errors
12/18/13: Correct the "text file busy" fix. Force su binary to be setuid root so root checkers will work.
12/18/13: Add more help in the "install.bat" for people having troubles getting adb working
12/18/13: Ensure the folder setup is right when starting install.bat
12/18/13: Give users time to allow su permissions
12/21/13: Disable SEAndroid before rooting
12/22/13: Install selinuxoff to set SELinux to Permissive mode at boot
12/23/13: Fix permission on selinuxoff binary, update SuperSU install and clean up rooting program
12/30/13: Remove selinuxoff program - it doesn't do anything. Updates to the install scripts.
1/6/14: Hard code kernel addresses for ATT Galaxy S4 so it takes less time to root.
1/6/14: Try to work around Knox deleting the su binary
1/10/14: Clear immutable bit on existing programs to allow them to be updated
1/12/14: Update to current SuperSU binary
1/13/14: Updates suggested by @bgmg
1/16/14: Correct typo in Linux/OSX installer
1/21/14: Really correct the typo. Add OS detection to install.sh so it can run on OSX or Linux without installing adb.
1/21/14: Update to current SuperSU
2/4/14: Detect when the phone is not rooted and don't continue the rest of the operations.
3/29/14: Install 'unroot' script and add unroot.bat/unroot.sh to allow simple removal of Saferoot changes.
4/4/14: Fix problem with unroot not running
4/30/14: Clearer error messages on root fail, allow user to choose installation of busybox
5/14/14: Fix typo in Unix install script, more text on why it failed.
5/24/14: Fix install.sh portability issue with double equals on test.
Source code, Unrooting, and the Custom Flag
The source code for the exploit tool used for this rooting method is attached.
In addition, two common questions:
1. How do I unroot?
OK, so why are you so anxious to unroot just after rooting?
If you have used the current version of Saferoot to root your phone, then there's an unroot script installed to make this easy.
If you still have Saferoot unzipped, plug in your phone and use "unroot.bat" (Windows) or "unroot.sh" (Unix) to remove the changes that Saferoot made. Then, open SuperSU and instruct it to perform a "full unroot". After that, all changes that Saferoot have made to your device have been removed.
If you don't have the unroot.sh, then you can unroot manually as below.
There's two things you need to do to undo what this installer does. First, remove busybox. This will require adb shell or the use of Terminal Emulator to get a shell prompt. Execute the commands below at a shell prompt.
The "$" and "#" characters at the start of those lines are the system prompt. You don't type those.
Spacing, case, etc. matter. The letter after "type" in the "find" command is a lowercase L.
$ su
# mount -o remount,rw /system
# rm -f /system/etc/install-recovery-2.sh*
# rm -f /system/xbin/selinuxoff*
# find /system/xbin -type l | xargs rm
# rm /system/xbin/busybox
# mount -o remount,ro /system
# exit
$ exit
The easiest way to do this is to install the "Terminal Emulator" app from the Play Store. Or use "adb shell" to get a shell prompt.
You can cut and paste the following to make it easier.
su
mount -o remount,rw /system
rm -f /system/etc/install-recovery-2.sh*
rm -f /system/xbin/selinuxoff*
find /system/xbin -type l | xargs rm
rm /system/xbin/busybox
mount -o remount,ro /system
exit
exit
Click to expand...
Click to collapse
It's very likely that the "/system/xbin/selinuxoff" and "/system/etc/install-recovery-2.sh" files won't be there.
Now, open SuperSU and use "Settings", "Full unroot". When that's done, everything that this installer has done has been reverted.
If you've installed xposed framework or wanam, you should remove those and reboot BEFORE doing the SuperSU unroot. Also, if you've installed Safestrap you'll need to boot into SS recovery, delete the custom ROM slots, then uninstall Safestrap recovery. Or, uninstall the Safestrap application. If you forget to do these before doing the SuperSU unroot, you'll need to re-root to do those.
If you need adb to access your phone, there's a copy in the "files" directory included with the installer. You'll need to open a command prompt and use cd to change to the files directory before trying to use that adb.
2. How do I get rid of the "Custom" padlock open screen at boot?
You get that because you're running custom software. Samsung has an application that runs at boot to look for modified system files; this app detects that the phone has been modified and sets that flag.
If you really need to get rid of that, you can do the unroot in #1 above, then reboot. Wait about 10 minutes or so, then reboot again. If you haven't changed any other system files, the custom flag should have been reset.
If that doesn't fix it, flash the stock no-wipe ROMs from this forum. Those will undo whatever you've changed and allow the phone to reset the custom flag.
If you want to keep root while getting rid of that "Custom" flag, then you can fake it. Install xposed framework (google for it), enable it, then reboot.
Then install Wanam Xposed, and enable that module in xposed.
In Wanam, choose "Security Hacks", "Fake system status".
That will keep the "Custom" flag from appearing. This is a cosmetic fix, but it does get rid of the "Custom" screen.
Other devices?
There is really nothing specific to the I545 or MJ7 in this root tool. There's a good chance it'll work on anything currently running 4.3.
If you have success with other devices, please reply to let us know.
Im glad I could help and good work! Im sure this will work with MK2 too.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Im glad I could help and good work! Im sure this will work with MK2 too.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yup. I'd say that it's almost certain.
Script did not work for me. I think there is a problem with the script or the zip.
Suppose there is something actually malware-ish about vroot or kingoroot, would that be something that could be "undone" so to speak by unrooting? As in, I've already rooted via both of those other methods at different times. Should I unroot to stop whatever they "may" be doing and then try and root via your method? Or is there really no point now that I'm already rooted?
Oozura said:
Script did not work for me. I think there is a problem with the script or the zip.
Click to expand...
Click to collapse
Which of the two scripts? What error did you get?
I'll be happy to fix if you'll provide some details!
I can confirm this works on ME7 just in case anyone is wondering, Im pretty sure it can easily work on any build we have so far. Might require minor modification but for the most part, this is solid.
sharkie405 said:
Suppose there is something actually malware-ish about vroot or kingoroot, would that be something that could be "undone" so to speak by unrooting? As in, I've already rooted via both of those other methods at different times. Should I unroot to stop whatever they "may" be doing and then try and root via your method? Or is there really no point now that I'm already rooted?
Click to expand...
Click to collapse
As far as lingering malware on the phone, the only thing you could do would be to flash a full-wipe factory image then root it when done.
I don't know if it's worth the hassle or no. If it was me, I'd be wiping, but I put the effort in to make this happen since I couldn't accept the closed-source risk with vroot.
sharkie405 said:
Suppose there is something actually malware-ish about vroot or kingoroot, would that be something that could be "undone" so to speak by unrooting? As in, I've already rooted via both of those other methods at different times. Should I unroot to stop whatever they "may" be doing and then try and root via your method? Or is there really no point now that I'm already rooted?
Click to expand...
Click to collapse
Sharkie, I'm new to S4, but I've been reading for decades & decades & saw a reference to a youtube video by Sgt tom (not sure of the name, but…) you can search for titles there relating to rooting S4, & it shows how you can install kingo root to obtain the exploit, do some stuff (don't recall, it may just be deleting that)… & installing Super SU in it's place or over that.
So do a little searching on root & s4 in youtube & invest some time… sorry, not sure if that was all meant for a diff version of the firmware; but it is worth looking into to use the kingo's exploit & then immediately replace it.
Don't know about the issue w/kingo is malware, or 'just' that it harvests your meid &/or other personal info, but there is a way to use it & replace it if you are OK with that approach…
Sorry I don't have specific references, but I just got into this since 'Grey Thursday' sale @ Staples, early start on Black Friday sales… hth,
oldwolf
First off... THANK YOU SO MUCH!
I did this method by putting it on my sd card... and it went through and told me to reboot. but upon reboot i have no custom splash screen and no su. i will try again tho.
I think I'm doing it wrong? Can someone help my dumb ass. Lol or I can just to adb. Either way haha.
Sent from my SCH-I545 using xda app-developers app
Craleb said:
I think I'm doing it wrong? Can someone help my dumb ass. Lol or I can just to adb. Either way haha.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Try the adb method first then if you get a failure message try the install.sh method from terminal again. After the script is done type "su". See if that works
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Try the adb method first then if you get a failure message try the install.sh method from terminal again. After the script is done type "su". See if that works
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am having the same results as the poster before you. I tried using adb method, and the prompt said adb couldn't be found.
Anybody want to confirm this works? I just updated to MK2 right now and want to try but would like another confirmation first.
Ugh I have adb setup and everything... but my freaking phone will not go into debug mode. Even after restart. I have debugging checked in dev options. It just "connected as an installer" then MTP
Sent from my SCH-I545 using xda app-developers app
Thanks for working on this. Copy of errors running script run in terminal emulator attached.
on MK2 and got the same output as Jiggity
Sent from my SCH-I545 using XDA Premium 4 mobile app
Hello Archos community,
I have bought the new Archos 50c Neon in early July, because of its nice price-performance ratio and the fact that it runs Android 4.4.2.
I have been able to successfully root it using Chinese "KingRoot", but am looking for an alternative SuperUser app. I already own a license of SuperSU Pro (which I am using for my tablet), but it turns out that the current versions of SuperSU (both 2.46 and 2.49) currently cause a crash when calling "su" from adb - seemingly because the Dalvik VM is unable to instantiate class "android.os.Environment" from SuperSU code when SuperSU wants to display its UI dialog that asks for permission. For the detailed issue description, please see here:
My thread in XDA SuperSU forum: Crash when trying to run su
Unfortunately, Chainfire (the author of SuperSU) from his signature is "away for most of the summer", and I will wait until he's back and then point him to this issue one more time.
In the meantime, I have created a script to successfully remove all remains/remnants of KingRoot (after successful rooting with it) and replace it by Koushik Dutta's OpenSource Superuser package:
https://play.google.com/store/apps/details?id=com.koushikdutta.superuser
http://www.koushikdutta.com/post/superuser
I have attached a ZIP file to this post that includes everything needed to do so - here are the instructions:
Please note that I do not take any responsibilities in case you brick your device, and also note that you void your warranty for the phone when rooting (these should be clear anyway)!
Reset your Neon 50c to factory settings (optional, might be needed in case you run into issues otherwise when removing KingRoot)
Unzip the attached ZIP and copy its contents to the root of the internal SD storage on your 50c Neon (directory /sdcard)
Use the included kingroot_4.0.0.apk to root your phone (allowing to install apks from untrusted sources)
Then, from your PC, open an "adb shell" to your device (you need to activate developer mode and USB debugging in order to do so)
From this adb shell, execute "su" and allow this root access through the KingRoot dialog on your phone. You now have a root shell on your phone.
Open a second adb root shell in the same way to not become stuck in case something goes wrong with the first one
In the first adb root shell, cd to /sdcard and execute my script in the following way:
Code:
cd /sdcard
sh -x ./kingroot_2_koush_su.sh ./busybox ./superuser.zip
and while it is running, press enter three times when "ps | grep king" and "ps | grep k_" show whether there are still processes running on your device that are related to KingRoot. General rule here is: When there are processes still running for the first ("ps | grep king"), something went wrong and KingRoot uninstall will most probably fail, while the fact that only processes matching the second ("ps | grep k_") are found, is normal and will NOT stop the script from working successfully.
When the script has finished, your phone will do a "soft reboot" (from killing zygote). You should do another explicit "hard" reboot afterwards anyway before trying to use the newly installed Superuser package.
I have run this script myself on my device, and am pretty confident that after the script has run successfully, there are no remains/remnants of KingRoot left on my device. The Open Source Superuser app by Koushik Dutta runs without any issues.
Hope this helps - and am still looking for some help with why SuperSU crashes on the 50c Neon although it seemingly has been installed properly...
Best regards,
awl
Great work, thank you very much for sharing this. :good:
I have just successfully followed your instructions and they worked for my new Archos 50c Neon as well.
Just one remark concerning the Kingroot (as the app was confusing me with Chinese that I could not read): Make sure to turn your wifi on before you start Kingroot, otherwise the app won't do anything.
And now my questions:
Do you by any chance know if there is a custom recovery available for the Archos 50c Neon? I haven't found any.
Have you written a debloater script which uninstalls all uninstallable apps?
do you have a custom recovery for this phone as I cannot get the su to up date without it restarting into recovery for the clockwork mod superuser. I have got root but only if i set supersu to grant rather than prompt but this isn't a very secure way as you said the su binary is there but the system isn't allowing the prompt.
Da5t3rati0n said:
do you have a custom recovery for this phone as I cannot get the su to up date without it restarting into recovery for the clockwork mod superuser.
Click to expand...
Click to collapse
AFAIK there is no custom recovery for this phone. I don't own it any more, it had too many weak points, such as most promintently speech quality/microphone and frequent hangups or no sound for one party during 3G telephony.
Sorry & best regards,
awl
awl14 said:
AFAIK there is no custom recovery for this phone. I don't own it any more, it had too many weak points, such as most promintently speech quality/microphone and frequent hangups or no sound for one party during 3G telephony.
Sorry & best regards,
awl
Click to expand...
Click to collapse
Yes first thing I noticed about this phone was the call quality haven't had any dropped calls though also the touch screen is awful only 2 touch. Reasonable hardware though CPU is a spreadtrum 1.2ghz a7 quad core so runs cooler and more energy effient than the a9 with a mali400 mp2 twin core GPU runs Asphalt8 on decent settings and good frame. But sadly let by the touch screen as for SuperSU it roots the phone and if set to grant, root programs run so the problem is with the prompt not being allowed to show. I'm thinking this is more Google security than anything.
Sent from my Bush 5" Android using XDA-Developers mobile app
Dupe from N6 forums for all you 6P junkies.
Obviously I'm not responsible for your mom exploding or your phone disowning you, but.....
I got tethering and Android Pay working on stock Nougat - that's Android N, folks - on a Nexus.
(confirmed will work on Marshmallow and up on 5, 5x, 6, 6p...etc.)
Thanks to @Chainfire, @ManHands and @interloper, and you!
click thanks if this helps, or buy me a beer or something.
prerequisites:
working adb and fastboot (from platform-tools in the Android SDK if you don't know where to find it)
twrp .img for your device
latest stable systemless supersu
1. be on Marshmallow or Nougat obviously
2. flash twrp
(volume down + power on nexus gets you into bootloader, then after flashing recovery, use volume buttons to scroll and power button to select recovery mode)
3. flash systemless root while booted into twrp (unsure if .supersu SYSTEMLESS=true in /data is still needed, but can't hurt - mine is still there from earlier.)
4. while still in twrp, go to mount and check system. Make sure you allow changes.
5. from your computer, do this
Code:
adb shell
echo "net.tethering.noprovisioning=true" >> /system/build.prop
6. reboot into Android.
7. Install Terminal Emulator from the Play Store.
8. Launch it, and in Terminal Emulator, do this
Code:
su
settings put global tether_dun_required 0
exit
9. go into Supersu, expert, scroll to the bottom and hit full unroot. No, you don't want it to patch you back to the stock boot image or recovery*. If it hangs, just reboot and try doing it again.
10. ????
11. Profit! You should have tethering unlocked, be unrooted, and have full Android Pay goodness working.
To take an OTA, do this, because Flashfire gets confused after you've done build.prop edits -
1. go to About Phone, scroll down. Find your build number.
2. download that Nexus Factory Image.
3. Unzip it all. ALL OF IT.
4. Make sure you have Android SDK & platform-tools (or just a working Fastboot and ADB)
5. just flash boot, system, and recovery - you can now OTA with no problems. Then repeat the above guide on your new OTA. Confirmed working 10 minutes ago, OTA'ing from Marshmallow to Nougat and then getting tethering working again
ALTERNATE IF YOU PREFER FLASHFIRE:
All the above steps, but you only have to flash the System image to fix the build.prop hash fail then flashfire should work for you. Wouldn't necessarily recommend upgrading version numbers (6.0.1 to 7.0.0) with Flashfire, but who knows, it might work great! Chainfire is a wizard.
*you can do this if you want, but when I let it patch my boot image I got the dreaded "device corrupt!!!!1" message at boot. Did not try letting it flash stock recovery image.
What if tethering already works on my N device? I haven't yet seen an N device failing to tether...
dtective said:
What if tethering already works on my N device? I haven't yet seen an N device failing to tether...
Click to expand...
Click to collapse
Then you don't need to apply the tethering tweak. Android allows you to tether just fine. The issue lies with certain carriers that charge extra for tethering. By default, Android allows the carriers to check to see if you're tethering and this is what this tweak changes.
I was also able to get ad blocking working using AdAway, on a one time host name update basis. SafetyNet check passes and Android Pay works. To enable this:
1. Prior to Step 9 above, Download and install the AdAway apk. It is available here: https://f-droid.org/repository/browse/?fdid=org.adaway
2. Go into the AdAway settings, Under "Target hosts file" select /data/data/hosts.
3. Enable Ad Blocking. Adaway will complain about not being able to create the symlink. To overcome this, I made /system read/write in Root Explorer, then created it manually in terminal:
Code:
su
ln -s /data/data/hosts /system/etc/hosts
4. Reboot. Go into AdAway and verify it is enabled.
5. Proceed with step 9 above. Make sure you say no to patching back to the stock boot image or recovery.
After Reboot You'll be unrooted with a host name ad blocker and working Android Pay. Worked for me anyway...YMMV. I will probably try and keep /data/data/hosts updated manually.
With the tethering mods t mobile still sees that I'm tethering and slotted my tethering speeds to a crawl after 5gb. Any way around this?
Sent from my Nexus 6P using Tapatalk
So this will allow me to get around Cricket's tethering ban (or rather, lack of support for the N6P in particular)?
Anyone confirm this works for Verizon / UDP?
DualSportDad said:
With the tethering mods t mobile still sees that I'm tethering and slotted my tethering speeds to a crawl after 5gb. Any way around this?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you are visiting unsecured website (https://www.instantssl.com/https-tutorials/what-is-https.html) You'll need to change your browser's user agent, or use VPN to encrypt your traffic.
keda said:
If you are visiting unsecured website (https://www.instantssl.com/https-tutorials/what-is-https.html) You'll need to change your browser's user agent, or use VPN to encrypt your traffic.
Click to expand...
Click to collapse
I've tried both, it still sees tether useage.
Sent from my Nexus 6P using Tapatalk
I'm on Android N and have been since the dev previews. I've never seen trouble with tethering... I'm on vzw UDP.
Hey guys and girls, so its a struggle to find firmware for these newer boxes anywhere. The Q1 X96MAX Plus is a revised version of the older model and contains a different WiFi radio set and Ethernet chip.
The old firmware from the other X96max plus on the web if flashed Will brick him but he has an automatic mask mode built in. If you brick him.. Leave him plugged into USB A to USB A and run the firmware below, he will automatically connect and accept this firmware version.
Hope this helps some people as there's not much on this Box in respect of development.
Basically the lack of development is due to the Chinese running scarce of Realtek chips and using whatever they could find to finish production. So many developer are faced with a lottery of trying to figure what firmware WiFi etcetera will work on which box as these models seem to vary so much from box to box instead of the usual one size fits all.
Here it is download, extract and flash with Amlogic UBT :
Q1 FIRMWARE #1
666.25 MB file on MEGA
mega.nz
Q1 FIRMWARE #2
683.48 MB file on MEGA
mega.nz
Regards
Firmware link is courtesy of Vasily Schevchuk, an amazing bloke check out his site here :
https://www.evolutiontv-vs.com/uncategorized/блог-системных-файлов.html
##Edit## Updated 13/02/2021
Bertonumber1 said:
Hey guys and girls, so its a struggle to find firmware for these newer boxes anywhere. The Q1 X96MAX Plus is a revised version of the older model and contains a different WiFi radio set and Ethernet chip.
The old firmware from the other X96max plus on the web if flashed Will brick him but he has an automatic mask mode built in. If you brick him.. Leave him plugged into USB A to USB A and run the firmware below, he will automatically connect and accept this firmware version.
Hope this helps some people as there's not much on this Box in respect of development.
Basically the lack of development is due to the Chinese running scarce of Realtek chips and using whatever they could find to finish production. So many developer are faced with a lottery of trying to figure what firmware WiFi etcetera will work on which box as these models seem to vary so much from box to box instead of the usual one size fits all.
Here it is download, extract and flash with Amlogic UBT :
File on MEGA
mega.nz
Regards
Firmware link is courtesy of Vasily Schevchuk an amazing bloke check out his site here :
https://www.evolutiontv-vs.com/uncategorized/блог-системных-файлов.html
Click to expand...
Click to collapse
The file you posted is no longer available. Could you post it again? Thanks a lot!
lchang.atsoft said:
The file you posted is no longer available. Could you post it again? Thanks a lot!
Click to expand...
Click to collapse
OP updated, 2 newer firmwares, also check out Vasily' site
Bertonumber1 said:
OP updated, 2 newer firmwares, also check out Vasily' site
Click to expand...
Click to collapse
Thank you for posting the files again. Do you know firmware for it that is rooted?
Will this firmware work on the older X96max Plus models?
delucai7 said:
Will this firmware work on the older X96max Plus models?
Click to expand...
Click to collapse
No there is a firmwares for that model. Search for vasily-ts vasikh shevchuk and slimhouse have great firmwares for amlogic boxes.
Regards
Hi.
Is there any way to get rooted firmware for X96 Max+ Q1? Maybe someone know how to root it via twrp/magisk? I know that SuperSu may brick device causing bootloop.
wonzay said:
Hi.
Is there any way to get rooted firmware for X96 Max+ Q1? Maybe someone know how to root it via twrp/magisk? I know that SuperSu may brick device causing bootloop.
Click to expand...
Click to collapse
Hello, I was talking to someone on YouTube about this earlier too.
There maybe a rooted firmware from Vasily Shevchuk :
https://www.evolutiontv-vs.com/uncategorized/блог-системных-файлов.html
scroll to near bottom of page.
I'm afraid TWRP only works via USB and won't give you root privileges on this System as Root device.
You're best bet is to install slimbox rom and patch magisk to boot. At least that way you will have a root and manager app to control it.
Here is a link to slimhouse slimbox firmwares :
project slimBOXtv
A project to create firmware for TV boxes and sticks with an Amlogic processor. Amlogic S905X, S905X2, S905X3, S912, S922, S905W, S905W4, S905Y2, S905L (Android 9) Amlogic S905X4, S905W2, S905Y4 (Android 11) slimBOXtv ATV and AOSP are two...
forum.xda-developers.com
You will also find more help and guidance in that amlogic thread with regards to what you want.
Regards
Thanks for the info. I will try slimbox maybe, but something in stock rom is not clear for me. When I type "su" in console, there is no error message like "su not found", but something similar to "you have no rights to access this executable". I thought that I am be able to boot twrp, mount system as r/w and do some kind of "magic" via commands "chmod&chown". Maybe it's a little bit naive idea.
Sorry for language, it's not native for me.
wonzay said:
Thanks for the info. I will try slimbox maybe, but something in stock rom is not clear for me. When I type "su" in console, there is no error message like "su not found", but something similar to "you have no rights to access this executable". I thought that I am be able to boot twrp, mount system as r/w and do some kind of "magic" via commands "chmod&chown". Maybe it's a little bit naive idea.
Sorry for language, it's not native for me.
Click to expand...
Click to collapse
Hmm I can't remember if it was this box that had the su file in the xbin folder but it needed chmod permissions to work.
By far the easiest way is to just connect via USB, get rid of stock rom an use slim, then patch the boot. Save yourself the headache
Regards
I will try slimbox, but in the future. This is not my tv box, you know.
Found su here:
:/ $ ls -lh /system/xbin/su
-rwsr-x--- 1 root shell 16K 2008-12-31 17:00 /system/xbin/su
Click to expand...
Click to collapse
wonzay said:
I will try slimbox, but in the future. This is not my tv box, you know.
Found su here:
Click to expand...
Click to collapse
Ah.. So it was that box.. Then maybe change permissions and make it executable.
You may not have proper root but it should get you a root shell at least
Regards
Which version of twrp should I use to do that? This is X96 Q1 4/64 box. I don't wanna brick it. I need root shell to change keyboard's config file ("enter" key in hardware bt keyboard doesn't work properly).
wonzay said:
Which version of twrp should I use to do that? This is X96 Q1 4/64 box. I don't wanna brick it. I need root shell to change keyboard's config file ("enter" key in hardware bt keyboard doesn't work properly).
Click to expand...
Click to collapse
You'll only have twrp with a custom rom installed, stock firmware = stock recovery slimbox or one of vasilys roms and it will be a recovery.img via USB flash drive that boots from the update menu.
Have you tried installing a soft keyboard such as SwiftKey, Leanmey or some other that will change default settings?
I was using Leanmey without issues with a Rii mini USB keyboard/mouse.
Again, you're best bet is to flash the slimhouse firmware. These boxes are pretty indestructible and have a built in auto mask rom mode that kicks in after 5 minutes during brick and will accept stock firmware again regardless (so don't worry) .
Hope this helps
Regards
Do you mean in this way?
Bertonumber1 said:
I was using Leanmey without issues with a Rii mini USB keyboard/mouse
Click to expand...
Click to collapse
I will try this. I have tried "simple keyboard", but no success. Enter key doesn't work properly when software keyboard is hidden, because "key 28" in the file "/vendor/usr/keylayout/Generic.kl" has wrong value "DPAD_CENTER" instead of "ENTER". No root = no fun, but at this moment I don't need slimbox, because everything works fine (bt, wifi, hw mouse&keyboard, even custom adw launcher/adaway/yt vanced), except this stupid enter.
wonzay said:
Do you mean in this way?
I will try this. I have tried "simple keyboard", but no success. Enter key doesn't work properly when software keyboard is hidden, because "key 28" in the file "/vendor/usr/keylayout/Generic.kl" has wrong value "DPAD_CENTER" instead of "ENTER". No root = no fun, but at this moment I don't need slimbox, because everything works fine (bt, wifi, hw mouse&keyboard, even custom adw launcher/adaway/yt vanced), except this stupid enter.
Click to expand...
Click to collapse
Your box sounds identical to all my devices app wise ( you missed Newpipe for downloading though )
How did you get on with this? There is three options, you may try inserting the lines for the key into the file or you may try flashing another firmware... If that fails try another keyboard.
I don't know if you've done this already though
Regards
I have left this subject alone (for a time). "Enter" key works via AOSP stock software keyboard - it has option to set default key. The only disadvantage of this "method" is that the AOSP keyboard is visible on the screen.
Ok, I figured it out, enter key works properly on my hardware bt keyboard. X96 MAX+ Q1 gains superuser powers when is connected via adb (root) over wifi. I remounted "read-write" /vendor partition, went to file "/vendor/usr/keylayout/Generic.kl" (make a backup!) and changed the line "key 28 DPAD_CENTER" to "key 28 ENTER". Don't forget to mount back /vendor as "read-only". At the end reboot your box.
Useful commands:
adb:
Code:
adb root
adb connect [ip address of the box]
(backup Generic.kl)
adb pull /vendor/usr/keylayout/Generic.kl
adb shell
re-mount, read write & read only:
Code:
mount -o rw,remount /vendor
mount -o ro,remount /vendor
Shell text editor - only vi is avaliable on my box:
Code:
busybox vi /vendor/usr/keylayout/Generic.kl
On the other hand you can pull "Generic.kl" to your computer, edit it locally, then push to "/vendor/usr/keylayout/" and chmod it correctly. The funny thing is that the "Generic.kl" in "/system/usr/keylayout" has right value for the key 28, but "vendor" path has a higher priority (I think).
ADB can be run directly from the box too, just use app called "termux" (get the latest version from "fdroid") and install in it "android-tools" package via the command:
Code:
apt update && apt install android-tools
Bertonumber1 said:
you missed Newpipe for downloading though
Click to expand...
Click to collapse
Similar tool for this purpose is "youtube-dl". I use it in termux (requires python3), but works anywhere python is installed (linux, windows, macos and so on).