Hey hopefully I'm posting in the correct sub section if not can a mod please move this. First off just want to say thanks for the information I've gotten lurking the past few months. I'm basically completely new learning basic coding etc. Sorry for the rant my question is ive been experiencing some cyber attacks which are very confusing and a long story...I'll try to keep it short...
Currently I'm on an old Samsung a21(buying the a54 when it comes out soon) my wife has a Samsung a53. Both phones have toybox installed but this wasn't flashed by me. I flashed her phone with the stock firmware last week to attempt to rid the hacking on it. Is it even possible to flash toybox remotely? I wouldn't think so as you would need to have several things lined up plus it connected to a pc. Nearly every device in my house has been corrupted down to smart watches, Bluetooth low energy devices, and especially computers. All of my pcs registrys are completely infected. My wife swears this is not her and has no idea how to do any of this. I have my suspicions with certain "coincidences" happening which are to numerous to name. Sorry for posting this here but I don't know where else to ask. If anyone could even point me in the right direction I'm willing to put In work. I've called professionals that basically advised me to trash everything. That's all fine and dandy but I need to understand this issue to prevent it from happening again. The scope of this issue is way over my head but I've made decent progress in the last three months. I'll check out the toybox guides here to see if that offers some clues
Thanks In advance for any advice.
Since you didn't write specific facts, I'll just answer about toybox.
Toybox has been on Samsung phones for a long time and is a system application without the ability to manually do an update.
Toybox - Wikipedia
en.m.wikipedia.org
Hey thanks for the reply. I didn't understand it was native to android. Would it be normal to have toybox version 0.8.4? I'll attach a picture maybe you can give me a little direction to go in. My phones able to be controlled remotely,modded apps, some weird things going down. Thanks again I'm pulling my hair out looking commands up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ace1222 said:
(...) Would it be normal to have toybox version 0.8.4? I'll attach a picture maybe you can give me a little direction to go in. My phones able to be controlled remotely,modded apps, some weird things going down. (...)
Click to expand...
Click to collapse
Could you please ask the questions precisely?
There is nothing special in the attached picture.
You want to just do:
Code:
$ setenforce 0
But it probably won't let you do that because your shell is not root.
Ace1222
Toybox since Android 6 is default component of Android OS: it replaced former Toolbox. Toybox is located either in /system or in /vendor partition.
Latest Toybox version is 0.8.9 ( conatains SU cmdlet ), can get downloaded from here:
Index of /toybox/bin
landley.net
Renate said:
You want to just do:
Code:
$ setenforce 0
But it probably won't let you do that because your shell is not root.
Click to expand...
Click to collapse
This only temporarliy disables SELinux what isn't needed when updating Toybox binary.
jwoegerbauer said:
This only temporarliy disables SELinux what isn't needed when updating Toybox binary.
Click to expand...
Click to collapse
I was only correcting the syntax on the OP's post #3.
jwoegerbauer said:
This only temporarliy disables SELinux what isn't needed when updating Toybox binary.
Click to expand...
Click to collapse
How is the user supposed to update the binary file when there is no root?
I never here said rooting Android is not needed to update Toybox binary.
To clarify things:
1. Obtaining Root only allows you the ability to modify the system. E.g. mounting partitions accessible as RW.
2. SELinux is a completely different entity. To change a devices SELinux State is written into the devices Kernel. The kernel is a part of the ROM. It determines whether or not the device is permitted to change it's SELinux State.
jwoegerbauer said:
I never here said rooing Android is not needed to update Toybox binary.
To clarify things:
1. Obtaining Root only allows you the ability to modify the system.
2. SELinux is a completely different entity. To change a devices SELinux State is written into the devices Kernel. The kernel is a part of the ROM. It determines whether or not the device is permitted to change it's SELinux State.
Click to expand...
Click to collapse
OK.
jwoegerbauer said:
This only temporarliy disables SELinux what isn't needed when updating Toybox binary.
Click to expand...
Click to collapse
How is user Ace1222 supposed to update the binary file when he does not have root, as you can see in the screenshot?
The user did not write that he has/wants root.
If you would carefully read my posts -> the solution already implicitely was given by me: make use of temporary root!
jwoegerbauer said:
If you would carefully read my posts -> the solution already implicitely was given by me: make use of temporary root!
Click to expand...
Click to collapse
Since you did/know how to do it on the Samsung Galaxy A21 and on the Samsung Galaxy A53 without burning the KNOX flag, just write. The user did not ask for it, but since you are advising, advise completely.
@jwoegerbauer
OP is not asking for updating toybox
there is no such "temporary root" for android on real devices (such as smartphones and tablets)
the toybox linked cannot replace the android version of toybox
toolbox is holding android specific applets (such as getevent) and cannot replaced by toybox
2 & 3: You're absolutely wrong. I kindly ask you to end spreading nonsense, TIA.
4: Yes, Toybox doesn't contain getevent cmdlet as Toolbox does, but that's abolutely irrelevant here.
get yourself a smartphone and learn the basics. I will pay $ 100 if you show any proof of your magic temporary root.
Sorry for causing any tension and debates here guys. I am interested in root access if that's what's needed. I'm totally ignorant and can sort of follow along what was posted. For clarification I don't have access to the rom folder even for read privileges. My intent is to figure out how/why my devices are being manipulated. E.g. why are there custom apps,partitions,user profiles, different access levels to folders that aren't in the root directory? Obviously my devices have been tampered with but I'm to ignorant to provide the information to help you help me.
Renate said:
You want to just do:
Code:
$ setenforce 0
But it probably won't let you do that because your shell is not root.
Click to expand...
Click to collapse
Yeah I tried that days ago and like you expected permission denied...
on bootloader locked devices system cannot modified. samsung devices are secure, a simple factory reset will remove all potential malware. just don't use the same samsung/google accounts again afterwards and do not restore backup of apps you don't know.
Related
Hello everyone,
Its been great to have root on your X10 using the method posted here:
http://forum.xda-developers.com/showthread.php?t=711907
Well, this method works all right but I did some investigating of my own to audit the state of the system after its been rooted. Thanks to the discussions you may find here: http://forum.xda-developers.com/showthread.php?t=712178, the original developers soon chose to update the Rooting tutorial with some additional steps (See post #2 and #4 of the rooting thread). This is all good, because now you have the real power to act as a the *real* superuser i.e uid 0.
Most of the discussions that follow are only intended for users who are well versed with general *NIX security and concepts about user ids, permissions and other things. So please disregard this post if you have no ideas of these concepts.
Ok, so first things first. I basically followed the root tutorial as it is all the way upto step3 (or step3a as in my case). Remember, you essentially have a rooted phone right after step2, step3/3a just adds the updated baseband firmware, which has no effect whatsoever on the subsequent things that you do to your phone.
Well essentially, what I did do was install the "su" binary and the "Superuser.apk" following in the lines of step4v2 (post #2 in root thread). These are essential to give you control over your system as without them you are simply relying on a hacked "sh" binary which runs with elevated privileges. Here are the file permission masks for the "sh" binary which gets installed after the FOTA in step2:
Code:
# ls -l sh
ls -l sh
-rwsrwsrwx root root 86944 2010-06-28 18:08 sh
#
Wait!!! This is *not* quite ok. What this means is that any process can use this binary to gain super user privileges. This binary is setuid and setgid root!!!
Well you might say that... so is the case for "su":
Code:
# ls -l su
ls -l su
-rwsrwsrwx root root 22120 2010-06-28 08:08 su
#
But, this is different because its use is controlled by the Superuser Whitelist application that was installed with Superuser.apk.
This difference is crucial because if any non-privileged application and process forks and execs "su", the Superuser Whitelist app would immediately post a notification screen on the phone and provide options to allow or disallow.
With the "sh" binary installed on your phone as it is, you are basically inviting *any* application to be able to do anything it wants to your phone... and all this without your knowledge!!!
To test this theory, all you need to do is simply install one of the terminal emulators floating around the market or use the one provided in the rooting thread under the step4/app folder and launch it. It straight away, launches you into a root shell. Here is a screen shot of what you can do this way:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Remember, no warnings, no notifications and all this can be done by any app under the hood)
Here is what you can do to make your phone more secure.
Step1: Download an alternative shell or simply change the permissions on the "sh" binary:
Code:
# cd /system/bin
# chmod 755 sh
Step2: In case you downloaded an alternative shell like "bash" and copied it under your /system/bin folder, simply get rid of the original "sh" binary and create a symlink to the one you download, for ex: bash:
Code:
# cd /system/bin
# rm sh
# ln -s bash sh
(Note: the above steps assume that you have /system mounted as rw, if you don't know what that means, then you should not be reading this, sorry)
Remember, when installing any alternative shell make sure that its permission mode is set to 755 or lower. I recommend to *never* set the setuid and setgid bits on the shell!!!
Here is what I did personally:
Installed bash from here: http://forum.xda-developers.com/showthread.php?t=537827
Installed it under /system/bin *without* the setuid and setgid bits
Removed the "sh" binary
Created a symlink named "sh" to the binary "bash"
This way, whenever I launch "adb shell" or use any terminal emulator on my phone, I always get a un-privileged shell. To get root, simply fire "su".
PS: This information is not intended for casual users who have limited or no knowledge of UNIX or UNIX like sytems like Linux, Adrdoid SDK commands like adb or don't know their way around if faced with a command line!!!
PS: Another post with some steps to properly secure the system: http://forum.xda-developers.com/showthread.php?t=712945
lmao..
http://forum.xda-developers.com/showthread.php?t=712945
zephyrix said:
lmao..
http://forum.xda-developers.com/showthread.php?t=712945
Click to expand...
Click to collapse
lol, you must've done this while I was writing mine!!
Anyways, its good to have this info out and I do point out some concepts detailing *why* this is a problem.
Definitely.
Make sure people have installed a proper way to elevate to root before attempting to change sh to not setuid, or they may screw themselves over lol
Thanks for your guide! Much appreciated would be an understatement.
is there any other way of testing that as using tht method in ur given picture now says read only error does this mean i successfully secured my root?
bcool15 said:
is there any other way of testing that as using tht method in ur given picture now says read only error does this mean i successfully secured my root?
Click to expand...
Click to collapse
Oh... I think I forgot to show this, but essentially you need to get the system partition into read/write mode as well. So it will be one more command before the write is attempted:
# mount -o remount,rw -t yaffs2 /dev/mtdblock2 /system
...
...
# echo "I can...
j4mm3r said:
Oh... I think I forgot to show this, but essentially you need to get the system partition into read/write mode as well. So it will be one more command before the write is attempted:
# mount -o remount,rw -t yaffs2 /dev/mtdblock2 /system
...
...
# echo "I can...
Click to expand...
Click to collapse
thats the command which stoppped wrkin so i just redid whole rooting procedure with new v3 update does it still need securing?
bcool15 said:
thats the command which stoppped wrkin so i just redid whole rooting procedure with new v3 update does it still need securing?
Click to expand...
Click to collapse
Dont worry about the example shown in the screen shot. That is just to illustrate what a setuid "sh" binary can do to your system.
j4mm3r said:
Dont worry about the example shown in the screen shot. That is just to illustrate what a setuid "sh" binary can do to your system.
Click to expand...
Click to collapse
this securing procedure isnt working on my new root any suggestions?
please
Regards,
bcool15 said:
this securing procedure isnt working on my new root any suggestions?
please
Regards,
Click to expand...
Click to collapse
Exactly what procedure are you referring to? The post is just meant to be a set of guidelines of a vulnerability that existed on the phone after it was rooted using "the root procedure" at the time this was posted.
If you have a "sh" binary on your phone which is setuid and setgid, then you have this vulnerability. I haven't updated the post with results from any new root procedures that have been posted since, but I suspect even the newer methods posted so far in the "root thread" don't get rid of the compromised "sh" binary.
Please ignore if you don't know what setuid and setgid means.
For IceCream Sandwich
Please see http://forum.xda-developers.com/showthread.php?t=1439429 instead.
Honeycomb and ICS users:
Download, install and setup OTA Rootkeeper. Not optional if you want to keep root after OTAs.
https://market.android.com/details?id=org.projectvoodoo.otarootkeeper
Special thanks to -viperboy- for putting his Prime on the line during testing, and Hawkysoft for convincing me to look in the first place.
*Donations*
Are 100% optional. If you want to, take your pick, paypal to your left, apps below, or find a nice charity.
https://market.android.com/details?id=net.andirc.jcasedonate
https://market.android.com/developer?pub=Cunning+Logic
Release and Downloads :
http://download.cunninglogic.com/nachoroot.bin
http://download.cunninglogic.com/su
http://www.androidpolice.com/2012/0...nsformer-prime-even-with-the-newest-firmware/
This is the support thread, feel free to ask questions here. Please do not redistribute my exploit.
adb push nachoroot.bin /data/local/
adb shell chmod 777 /data/local/nachoroot.bin
adb shell /data/local/nachoroot.bin --stage1
adb reboot
<wait for boot>
adb shell /data/local/nachoroot.bin --stage2
adb reboot
<wait for boot>
adb shell id
<if id is 0 / root then continue, else start over>
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell /data/local/nachoroot.bin --undo
adb reboot
Go install superuser from market:
https://market.android.com/details?id=com.noshufou.android.su
Thanks jcase.
I used all my thanks for today so you will get one when I get some more
adb shell chmod 06755 /system/xbi/su <--typo
adb shell chmod 06755 /system/xbin/su
wow that release was quicker than I tought... my prime arrives tomorrow.. after unboxing this is the first step...
Cannot wait until Thursday to try this out!
Good stuff. Can't wait for my replacement to come in.
Thanks! quick question. Will this be converted into an apk or app for one-click type method? for people with no immediate access to PC. since I've gotten my Ipad then now Prime, I haven't ever had a need to use my almost 10yr. old PC..lol. its slow as molasses. that's why I jailbroke my Ipad so i wouldn't need to connect to PC for iTunes for media n stuff.
just asking
demandarin said:
Thanks! quick question. Will this be converted into an apk or app for one-click type method? for people with no immediate access to PC. since I've gotten my Ipad then now Prime, I haven't ever had a need to use my almost 10yr. old PC..lol. its slow as molasses. that's why I jailbroke my Ipad so i wouldn't need to connect to PC for iTunes for media n stuff.
just asking
Click to expand...
Click to collapse
Not possible at this time, will investigate root via app once I have a prime in hand, no guarantees however.
demandarin said:
Thanks! quick question. Will this be converted into an apk or app for one-click type method? for people with no immediate access to PC. since I've gotten my Ipad then now Prime, I haven't ever had a need to use my almost 10yr. old PC..lol. its slow as molasses. that's why I jailbroke my Ipad so i wouldn't need to connect to PC for iTunes for media n stuff.
just asking
Click to expand...
Click to collapse
Don't really need a "fast" computer for ADB lol. It just needs a USB port.
demandarin said:
Thanks! quick question. Will this be converted into an apk or app for one-click type method? for people with no immediate access to PC. since I've gotten my Ipad then now Prime, I haven't ever had a need to use my almost 10yr. old PC..lol. its slow as molasses. that's why I jailbroke my Ipad so i wouldn't need to connect to PC for iTunes for media n stuff.
just asking
Click to expand...
Click to collapse
+ 1 that would be awesome but ifyou can't no big deal
Edit just saw Jcase answer will not be rooting yet but thank you anyways good job you are a hero
jcase said:
Not possible at this time, will investigate root via app once I have a prime in hand, no guarantees however.
Click to expand...
Click to collapse
sounds good enough. thanks again. no big deal. just wondering.
RussianMenace said:
Don't really need a "fast" computer for ADB lol. It just needs a USB port.
Click to expand...
Click to collapse
if you knew how long it took for my PC to boot up and open an app, you'd ask also.. It does have usb ports, its not that old..lmao. its all good. still deciding if I want to give it a shot now or wait till after ICS.
Very nice work. Is there any way to revert this root?
For everybody considering doing this, do note that ICS is scheduled to release 12 January. Trying to update/upgrade a rooted/hacked tablet MIGHT BRICK your Prime.
So it could be wise for the majority of users to wait untill ICS before trying to root.
JCreations said:
Very nice work. Is there any way to revert this root?
For everybody considering doing this, do note that ICS is scheduled to release 12 January. Trying to update/upgrade a rooted/hacked tablet MIGHT BRICK your Prime.
So it could be wise for the majority of users to wait untill ICS before trying to root.
Click to expand...
Click to collapse
mount system, delete su
Why would it brick if they just installed su (really dont know, would like to look into preventing it)
Process went flawlessly. Thank you jcase.
I must say the build.prop and standard gps.conf are decidedly empty, weird.
FREAKING AWESOME WORK!!! Thank you Jcase...Worked like a charm no hicups or glitches...we are now one step closer to Recoveries and Roms...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Doktaphex said:
Proces went flawlessly, I must say the build.prop and standard gps.conf are decidedly empty, weird.
Click to expand...
Click to collapse
odd, NachoRoot doesn't write to system so im guessing thats normal?
jcase said:
odd, NachoRoot doesn't write to system so im guessing thats normal?
Click to expand...
Click to collapse
That's entirely my point. It just seems odd that they're so empty (maybe not so much gps.conf).
jcase said:
mount system, delete su
Why would it brick if they just installed su (really dont know, would like to look into preventing it)
Click to expand...
Click to collapse
I'm not that into programming/rooting, therefor my emphasis on might. For the majority of users it might be just safer to wait those 9 days until ICS.
jcase said:
mount system, delete su
Why would it brick if they just installed su (really dont know, would like to look into preventing it)
Click to expand...
Click to collapse
JCreations said:
I'm not that into programming/rooting, therefor my emphasis on might. For the majority of users it might be just safer to wait those 9 days until ICS.
Click to expand...
Click to collapse
Since ASUS uses BLOBs for updates, it will most likely just over-write the system folder anyway. No more 'SU', but also no brick!
MarkF001 said:
Since ASUS uses BLOBs for updates, it will most likely just over-write the system folder anyway. No more 'SU', but also no brick!
Click to expand...
Click to collapse
Then I don't see the concern, re-run the root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SSH for the Rooted Fire TV
Secure Shell (SSH) is a cryptographic network protocol for secure data communication, remote command-line login, remote command execution, and other secure network services between two networked computers.
So what? Why do I want this on my Fire TV?
Right now, the only means of communicating with your Fire TV is through ADB, which is fine, but has limitations, mainly due to the fact that adb does not run as root.
SSH does, so those limits are removed. Using scp or even better sftp you can easily copy files to and from any area on your Fire TV, issue commands via ssh and more.
Details are HEREhttp://www.jocala.com/busydrop.html
reserved
Note: If you are an adbFire user you already have this. Just select "Install SSH" from the root menu.
Note: This is probably not compatible with other busybox installs. They do vary depending on compile-time options. Please uninstall Google Play busybox installs or other variants before installing BusyPlay!
Nice. I look forward to trying this out soon.
SSH helper apps
Canyaya' pid='1817081' dateline='1413750441 said:
Hi Jocala, thank you for all your work. When you install the sftp server, what is the username and password?
Click to expand...
Click to collapse
This is a cross-post from another forum. I thought it might be useful here.
root/password -- the userid should default to root
The command-line "ssh "helper" apps are:
Manually start the server with a password (no spaces)
Code:
sshstart
Usage: sshstart password -- arguments: the password you want to use
Kill sshd immediately
Code:
sshstop
Usage: sshstop -- no arguments, immediately kills ssh server
Show sshd status
Code:
sshstatus
Usage: sshstatus -- no arguments, gives ssh server status
Create sshd startup script with given password
Code:
sshinit
Usage: sshinit password -- arguments: the password you want to use (no spaces)
this program creates the file /etc/init.d/02sshd that starts sshd at boot
Delete sshd startup at boot script
Code:
sshboot
Usage: sshboot -- arguments: rm
Typing sshboot rm deletes the file /etc/init.d/02sshd that starts sshd at boot
Should i uninstall my playstore busybox before installing this?
jmandawg said:
Should i uninstall my playstore busybox before installing this?
Click to expand...
Click to collapse
Yes.
So I gave this a try following your instructions as it looked like it would work great for backing up cwm recovery files to my PC. I followed all the instructions installing the zip through cwm recovery and rebooting but when I click on ssh on adbfire 1.11 it says fatal error connection refused. Any idea what I might have done wrong or how to get it working. I have installed putty on my computer and I tried to connect directly through putty as well but that wouldn't work either. How can I test if the ssh server is working or not?
**edit: I got it to connect to putty and winSCP after uninstalling the busybox I had installed and installing the busybox through adbfire 1.11 I can see this being a very powerful and useful tool for the Fire TV. Very nice work jocala. I still can't see the cwm recovery files I would like to back-up though. Shouldn't they be in the /storage/emulated/legacy/clockworkmod folder unless I am missing something?
rotor00ter said:
So I gave this a try following your instructions as it looked like it would work great for backing up cwm recovery files to my PC. I followed all the instructions installing the zip through cwm recovery and rebooting but when I click on ssh on adbfire 1.11 it says fatal error connection refused. Any idea what I might have done wrong or how to get it working. I have installed putty on my computer and I tried to connect directly through putty as well but that wouldn't work either. How can I test if the ssh server is working or not?
**edit: I got it to connect to putty and winSCP after uninstalling the busybox I had installed and installing the busybox through adbfire 1.11 I can see this being a very powerful and useful tool for the Fire TV. Very nice work jocala. I still can't see the cwm recovery files I would like to back-up though. Shouldn't they be in the /storage/emulated/legacy/clockworkmod folder unless I am missing something?
Click to expand...
Click to collapse
I've added notes concerning Google Play busybox installs and adbFire.
/storage/emulated/legacy (/sdcard) is where my clockworkmod directory is. I haven't done a backup, so mine is empty.
Does this allow using keys?
{ParanoiA} said:
Does this allow using keys?
Click to expand...
Click to collapse
It should, although I haven't tried. A new startup script would be needed, sshstart is hardcoded to startup using a password.
BusyDrop 1.01 released
Changelog: update to BusyBox v1.22.1 (2014-10-26 17:14:21 EDT)
This setup is awesome for transferring files to and from the Fire TV. Much better and easier than adb once you get it set up properly. I have been using this with WinSCP and it has worked perfectly.
thank you very much for this. im loving it.
Is there a benefit to using this over an app like Servers Ultimate?
hazard666 said:
Is there a benefit to using this over an app like Servers Ultimate?
Click to expand...
Click to collapse
Obviously I think so or I wouldn't have taken the time to develop it. Are you a user of this other app?
jocala said:
Obviously I think so or I wouldn't have taken the time to develop it. I hope you don't want to debate the merits of my project against another in my thread. That wouldn't be very nice.
Click to expand...
Click to collapse
Or it's a completely valid question and I was wanting some input, but if you have issue with answering then ok.
Edit: What difference does it make whether I am or not a user of another app? I was asking if there is a benefit to using your app since I already have an established solution. Nevermind though.
hazard666 said:
Or it's a completely valid question and I was wanting some input, but if you have issue with answering then ok.
Edit: What difference does it make whether I am or not a user of another app? I was asking if there is a benefit to using your app since I already have an established solution. Nevermind though.
Click to expand...
Click to collapse
My apologies, rapid post at the end of a long bad day. I regretted my snappish response as soon as I hit enter, and edited, but not soon enough.
jocala said:
My apologies, rapid post at the end of a long bad day. I regretted my snappish response as soon as I hit enter, and edited, but not soon enough.
Click to expand...
Click to collapse
It's quite alright. I'm not too happy with my current setup so I will be trying out BusyDrop.
hazard666 said:
It's quite alright. I'm not too happy with my current setup so I will be trying out BusyDrop.
Click to expand...
Click to collapse
If you have any questions I'll be more than happy to assist. Now I'm going to bed before I kick my dog or do something else that will embarrass me tomorrow.
+1 for being able to ssh in using a key and disabling password logins. It makes it easy to log in from putty and other ssh clients, more secure and I don't have to record one more password.
I don't always follow a new device during the troubled early days of root...
...but when I do, I'm utterly scarred by the chaos and confusion.
Since I've watched the current V20 root exploit evolve from "maybe DirtyCow would work here" into a full-blown war on Nougat's sepolicy, and finally into the emergent "Recowvery"; I thought it might be fun to get my own hands a little dirty and write some wrappers to automate the rooting process with ample error-checking along the way.
>> Please take a moment to check out @jcadduono's Recowvery thread at http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594 for more information, to say "thanks," and to donate if you can afford it. <<
WARNING: ATTEMPT AT YOUR OWN RISK! THIS PACKAGE IS RELEASED AS-IS AND WITHOUT ANY WARRANTY, IMPLIED OR EXPRESSED
THIS PACKAGE MAY MAKE YOUR LIFE EASIER (or harder) BUT NOTHING CAN FULLY PROTECT YOU FROM TROUBLE WHEN ROOTING A DEVICE!
IT IS NOT MY RESPONSIBILITY IF YOU END UP WITH A BRICK IN YOUR POCKET AFTER ATTEMPTING ROOT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Current, Planned, and Not Guaranteed Features:
- Windows support, including a truly die-hard adb check
- Push, exploit, and flash all in one step
- Optional automated SuperSU installation
- Bundled adb for more predictable results
- More error checking than you think you'd need
- Auto-disable dm-verity and forced encryption
- Optional selinux permissive mode
- Restore boot and recovery to stock
- Spawn a root shell for exploration and such
- Grab any recovery.img you'd like to use from /sdcard
- Linux support (needs to be reworked )
- Ability to download latest exploit and recovery at runtime
- Extra helper commands for stuff like trying to break out of bootloops or quickly grab logs
- Basic GUI for Windows
Download:
Latest version: 1.3b3
Grab the latest zip: https://github.com/bziemek/EasyRecowvery/releases
Or browse the source: https://github.com/bziemek/EasyRecowvery
--
TWRP for the H918: in jcadduono's thread, Step 3
no-verity-opt-encrypt: also in jcadduono's thread, Step 3
SuperSU: in Chainfire's beta thread
Instructions:
https://github.com/bziemek/EasyRecowvery/blob/master/README.md
Greetz:
Huge shout out to @jcadduono for running with the DirtyCow idea and making this root possible (read more and THANK HIM HERE), Chainfire for taking some time off to do a test install of the latest SuperSU hours before we had a working TWRP, @Darriousx and @slayerh4x for all their hard work testing, and #twrp on Freenode for generally putting up with the lot of us!
Donations:
IF you feel so inclined, PayPal some coffee and beer money to [email protected], or BTC to 1bu5MMgagtbN7QVeciyWfAzRbfk8vmynM
Many thanks to @Pjs187, who furnished the first donation I've received here at XDA!
Frequently Asked Questions
Why isn't it working?
First: update your ADB. If you don't have ADB, then you'll want to fix that before you spend another second at XDA. I personally only use official releases from Google, so I might not be much help if you're using something you found at random at XDA or elsewhere on the Internet. You can download Google's latest release of their tools from the very bottom of this page. (I recommend installing or extract them to C:\Android for easy access.) Using the "SDK Manager" included in that download, choose to install "Android Platform-tools" and "Google USB drivers", and remember to run it again once in a blue moon for updates.
If ADB isn't the problem, I'm happy to offer what assistance I can. Please describe what you were trying to do and how, then attach any .log files the script created.
Where is TWRP?
The link to the latest version is linked in this thread under Step 3.
Rename the downloaded file to recovery.img and put it on your internal storage.
Does Data need to be wiped?
For everything to work properly, YES. If you don't have an inherent understanding of what will happen if you don't run a Format Data, then please do so the first time you enter TWRP. This will erase Internal Storage and remove the default encryption so that TWRP can function to the fullest. BACK UP YOUR STUFF FIRST!
Is no-verity-opt-encrypt necessary?
YES, but not totally. This ZIP makes it possible to allow system modifications, and prevents a couple easy ways to end up with corrupt data or bootloops.
Download that from Step 3 in the thread above, and put it in the folder named zips next to EasyRecowvery.
If you're going to install SuperSU right away, you shouldn't really need it.
What is selinux?
selinux is a major security feature, and also a major pain in the butt depending on who you ask.
If you don't know if you need it in "permissive" mode, just leave it be. You can always reflash later.
Why isn't TWRP showing Internal Storage?
These phones use encryption out of the box. In order for TWRP to function properly, you will need to use the Wipe Data feature after installation.
This will blow away everything on your Internal Storage, so make sure you don't have anything important in there!
Changelog
1.3b3
Add more sanity checks
Add note about formatting data
Separate log for ZIP flashing
Rename bundled adb.exe to adb-recowvery.exe (maybe)
Older Versions
1.3b
Bundle adb.exe (can be toggled in Extras menu)
Improve and fix adb and device checks
1.2b
Add experimental support for auto-rooting.
Add an extra mode to flash no-verity-opt-encrypt.
Add an extra mode just to reboot into recovery.
1.1b-hotfix
Add the "zips" folder needed by the new version.
1.1b
Skip several versions and change versioning style.
Redesign the menu system.
Auto-flash no-verity-opt-encrypt.
Update Recowvery to latest version.
Tweak prompts, formatting, and fix typos.
More aggressive connection handling.
Fix the restore feature.
Allow disabling integrity verification (untested).
Increase logging verbosity.
Fix line endings in EasyRecowvery.cmd
beta5
Take a nap.
Fix some issues with various prompts.
Adjust some formatting.
More testing.
beta4
Improve adb checking code.
Reluctantly accept that we should try recovery.img.img.
Misc. tweaks to prompts.
beta3
Fix several parentheses that might be causing trouble.
beta2
Fix a bug causing EasyRecowvery to fail when run from another directory.
beta1
Initial release.
WOW! This is what i've been waiting for. Thanks man!
Thanks for this. Will help a lot of users who are Leary about the cureent manual process
Awesome...
Awesome man, so cool to watch all this develop. Glad I could be part of it.
definitely looking forward to this. sweetness!!!!
It has been amazing watch all this develop in the past weeks. I have been flashing and rooting for about 10 years and this is the first time I've seen it all from the beginning. It is really amazing what a few of these guys are capable of...but this time for me I was left speechless. Gentlemen, (and ladies?) Thank you for all of your free time and dedication for making this possible for the average end user like me. We all don't show enough gratitude and I'm sure I'm not the only one amazed my all of your capabilities. Keep up the unbelievable work, and a nice donation is coming to everyone who contributed if I can find a way to donate to you all. Point me in the direction, and the cash flow will be on its way. Thank you again.
Sincerely,
dmoney4eal
@bezeek you might want to add the "I am not responsib...." disclaimer. One for your protection but mostly so people are aware of the possible consequences.
If only I had the T-Mobile variant I would of already wrote this and put it in this thread lol, anyone want to donate? :c
whowatchlist said:
@bezeek you might want to add the "I am not responsib...." disclaimer. One for your protection but mostly so people are aware of the possible consequences.
Click to expand...
Click to collapse
There will be some big ol' red letters in here before I attach any files - you can bet on that
pro_granade said:
If only I had the T-Mobile variant I would of already wrote this and put it in this thread lol, anyone want to donate? :c
Click to expand...
Click to collapse
If you think you can beat me to it, there are H918 owners in #twrp on Freenode who would be happy to help you test as you go
bezeek said:
If you think you can beat me to it, there are H918 owners in #twrp on Freenode who would be happy to help you test as you go
Click to expand...
Click to collapse
I could write it in batch and convert to exe.
pro_granade said:
I could write it in batch and convert to exe.
Click to expand...
Click to collapse
I'm game for a friendly race. I've got lots else going on today, so it's coming together bit by bit.
(I might be putting up a rough build in the AM depending on what sort of sleep I get tonight.)
bezeek said:
I'm game for a friendly race. I've got lots else going on today, so it's coming together bit by bit.
(I might be putting up a rough build in the AM depending on what sort of sleep I get tonight.)
Click to expand...
Click to collapse
It'd be a lot quicker if I actually had the device. I'll probably let you go for it lmao
Race, race, race!
The winner gets the most thanks??
poczynek said:
Race, race, race!
The winner gets the most thanks??
Click to expand...
Click to collapse
How about some money lol
Is this still a WIP? I don't see anything updated by the OP. I'm waiting to root and something like this would be great as I am leery of going through the regular method with ADB as I'm coming from a Samsung device.
I pledge $20!.
So I have a Infinix Note 12 pro 4g x676b. The manufacturer of this model has another model with the same name which is more popular. Now let me get to the point. I wanted to root this phone with magisk. its android 12. I tried a few tutorials for it but i realised i need twrp, but this phone model dosent have a twrp img. So i tried the method of fastboot and adb. i patched my boot.img using magisk and then try to patch it to my mobile using my pc. The adb device gets detected and i get it into fastboot. But in fastboot the device does not get recognized. I tried installing all the drivers but the manufacturer does not provide any. I got every unnofical driver installed but still it dosent detect. And also my phone does not get detected in device manager either in other devices or portable devices. What do i do now?
May be this guide is useful:
How to get into fastboot and How to exit fastboot INFINIX Note 12 (2023)? - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info
xXx yYy said:
May be this guide is useful:
How to get into fastboot and How to exit fastboot INFINIX Note 12 (2023)? - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info
Click to expand...
Click to collapse
that is not my question tho. My phone does not get recognised on my windows pc
potatosil said:
that is not my question tho. My phone does not get recognised on my windows pc
Click to expand...
Click to collapse
It is getting recognised as Unknown device?
A PC-connection isn't required at all, you can run ADB and/or Fastboot commands from phone, too. Note: Android must got rooted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Take note that a phone's Android is rooted if SU is present in Android's filesystem.
xXx yYy said:
A PC-connection isn't required at all, you can run ADB and/or Fastboot commands from phone, too. Note: Android must got rooted.
Click to expand...
Click to collapse
i am asking my question to get my phone rooted. If it was already rooted i wouldnt have made a thread
potatosil said:
that is not my question tho. My phone does not get recognised on my windows pc
Click to expand...
Click to collapse
It is a driver related problem.
You may be able to get your work done using wireless adb, although flashing stuff wirelessly is very risky (if the connection breaks whilst the flashing is still going on).
mvikrant97 said:
It is getting recognised as Unknown device?
Click to expand...
Click to collapse
not even an unknown device just nothing is there
potatosil said:
i am asking my question to get my phone rooted. If it was already rooted i wouldnt have made a thread
Click to expand...
Click to collapse
To root a phone's Android Fastboot isn't needed as you suppose : ADB is the correct tool.
Most people instead of adb.exe what comes with Android SDK use adbLink2 app what provides a link between your Android device and your computer.
adbLink2 features:
Install Programs without Android SDK
ADB/Fastboot enabled command-line
Busybox for root and non-root
Built-in WIFI/USB remote
Manage devices via USB or IP address
Root-aware File Manager for Android devices
Install/Uninstall Apps
Connect to devices ad hoc
Manage multiple devices from one PC
Edit XML and other files on your devices
Log file viewer for adbLink2
Hyperlinked HTML Help
adbLink2 is available for Windows, macOS and Linux/ChromeOS
BTW to clarify things, you obviously don't know of:
1.
Before I define root, it's important to understand why it exists and how it works. It's because Android uses permissions ( Linux-based permissions, to be exact ) in the file structure. Every file, every folder and every partition has a set of permissions. These permissions decide who can read a file ( look at or access the contents without changing them ), write to a file ( be able to change the contents of that file, or create a new file inside a folder or partition ) and execute a file ( run the file if it's a type that can run, like an app ). This is done based on users and permissions - certain users have access, while users who don't have the right permissions are blocked from having access.
When you first set up your phone and turn it on for the first time, you are assigned a user ID. If another user logs in via Google, they are assigned a different user ID. When an app is installed on your phone, it's also assigned a user ID of its own. The system itself is a user and other processes that need to run on your phone may have their own user ID. Everything that can do anything to any files on your Android is a user.
2.
To get elevated permissions ( root access ) you place the SU binary ( SubstituteUser ) in a spot that it can run when it's called to run - that's called a PATH - e.g /data/local/tmp. If any app is in user ID's PATH it will run without telling the system exactly where it is. You also need to make sure the SU binary is in a spot that your user ID has permission to execute ( run ) files. Any other app ( Google Play has plenty of apps that need root permissions ) will also need the same access. When you use a method to root your phone, all this is sorted out by the folks who built the root method.
3.
This is where root comes in. The SU binary uses flags when it's run to tell the system what user ID you want to switch to. For example, if I run the SU binary on my Google Pixel phone like this "su Jim -c 'mount - o rw,remount -t auto /system'" I will run the mount command as the user Jim ( after supplying Jim's password ). If I run the SU binary with no flags or arguments, it switches me to the root user. Normally you would need to supply a password, but since "root" is an unused user on Android it has no password. Running the command "su" will switch you to the user root, and assign you the user ID of 0, and put you in the root group. You are now the Super User.
4.
As the Super User you can do anything to any file, folder or partition on your Android. By anything, I mean literally anything. You can remove bloatware apps and you can also remove essential system files that break your phone. You can also do things to the hardware like change the CPU frequency and ruin your phone forever.