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
Related
####NO LONGER SUPPORTED####
Links have been updated to the last release and are working
###############################
{
"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"
}
The NookBuntu Dev Team
devastatorx | penkia | lincore | munday | luciferii
CREDITS: munday for his initial work on this project, penkia for the wifi and touchscreen fixes. The guys who pulled off the vnc trick to get us thinking about how to make this a full fledged linux tablet. All the great developers for the nook and every other device.
*DISCLAIMER*
I'm not responsible, blah blah blah...if you are trying this...your warranty cherry was popped long ago
Q & A - This area will be updated as questions arise
Q: Why the skip from alpha 0.1 to beta 0.3?
A: Alot of testing and fixes were implemented behind the scenes. These images were not released due to usability issues. We wanted this release to be one that could serve as a daily build. And this comes relatively close.
Q: Will this mess up my current configuration?
A: If your current configuration runs from the eMMC, then no. It runs solely from the uSD card. As long as you don't mount your eMMC inside NookBuntu and start messing around with it, it should be fine.
Q: Is this awesome?
A: Yes, it is so awesome that if I were to speak anymore than a few lines about it's awesomeness, computers would become self aware, sheep would begin counting people, and pong would turn into tetris...
Q: Will this run from the internal memory?
A: This is being planned for a future release and currently only runs from the SD card. DO NOT FLASH IT TO THE eMMC!!!
A NOTE ABOUT DONATIONS - Please read
No we do not ask for donations or accept them. We do this because we are as passionate as anyone in this communtiy about the tech we use.
If you would like to donate, please instead consider donating to the following charity
The National Breast Cancer Foundation - https://www.nationalbreastcancer.org/donate/
My sister was recently diagnosed with stage 3 breast cancer. I ask that if you do wish to donate, please do so in her honor. If you wish to make a donation in her honor please pm me for details (name and whatnot). Thank you!
################################
NookBuntu Beta 0.3
################################
Screens
Working
Boot into NookBuntu when the device is powered on (no adb necessary!)
Network manager - this is still being worked on, use the method listed in the instructions below
Touch screen
On screen keyboard auto slide out on text input area focus
Audio
Not Working
Home button
Volume buttons
Multi-touch
Bluetooth
Hardware acceleration
Accelerometer
Charging
Installation instructions
DOWNLOADS
NookBuntu Beta 0.3 - Download
md5: bfe2206fbfd7f402cd1c95c61b13dc83
NookBuntu Boot Partition - Download
md5: 316f8d6d44cb3d2c4a13f01da63c302e
We will need to make a bootable SD card for this. As of right now I have an 8gb card and will be uploading a burnable image soon...but for now this method will work.
Download this script and save it somewhere you have easy access to.
Download: SDMAKER
Ok so you have all the files right? Right?? ...right
Let's get that SD card prep'd for our NookBuntu installation.
1) Open up a terminal and cd to where you saved the file sdmaker.sh
2) Insert your soon to be nookbuntu sd card into your pc and find out where your sd card is mounted i.e. /dev/mmcblk0 or wherever. REMEMBER what it was (for me it is /dev/mmcblk0)
3) Type the following command hitting enter after each line
Code:
sudo chmod +x sdmaker.sh
sudo ./sdmaker.sh /dev/yoursdcard
4) Let this command run and finish out, it is formatting your sd card to correctly have a boot and filesystem partitions
5) Once this has finished you should have two new partitions show up, either mounted already at /media/boot and /media/Angstrom or should be able to mount the new partitions in your file manager. If they aren't mounted go ahead and mount them.
Let's regather. You have two folders open on your desktop, one titled "boot" and the other titled "Angstrom". Are you with me? Good.
6) Untar/7zip/Unzip whatever...decompress the file nookbuntu-0.3beta.tgz anywhere you would like.
7) cd to the directory where you extracted the files. There should be a folder titled "system" Go ahead and cd into that directory.
8) Now we need to copy all of the contents to the Angstrom partition on your SD card
Code:
sudo cp -r * /media/Angstrom
This will take awhile, get something to drink.
9) After that has finished lets copy over the boot partition. Go to where you downloaded the file "nookbuntu-boot.7z" and extract it. Now CD to nookbuntu-boot. Are you with me? Let's copy those files over!
Code:
sudo cp -r * /media/boot
10) After that has finished we need to setup your wifi so it will work. So let's edit the one of the files we just put on your sdcard (use whatever text editor you would like:
Code:
sudo gedit /media/Angstrom/etc/wifi/w2.conf
In your text editor you will have something like this:
Code:
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="WiFiNetworkName"
scan_ssid=1
key_mgmt=WPA-PSK
psk="yourWPAkey"
}
We need to change a few things to be able to connect to your home wifi.
Change the following:
Code:
ssid="WifiNetworkName"
to
ssid="YourSSID"
Obviously replace "YourSSID" with whatever your actual SSID is.
Chances are you are using WPA encryption...well if you aren't...you should be. Assuming you are we need to set up so we can send the key to the router when we connect.
See this line?
Code:
psk="yourWPAkey"
Change "yourWPAkey" to...you guessed it....your WPA password
Save the changes and exit.
11) Unmount the sdcard from your computer
Code:
sudo umount /media/boot
sudo umount /media/Angstrom
12) Take the Sd card and put it in your nook while it is powered off.
13) Power on your nook and give it a few mins...voila! NookBuntu should have loaded!
These next steps are for getting wifi up and running you can do this from an ADB shell or from the terminal inside NookBuntu or make it into a script for future use.
Enter these commands (hitting enter after each line unless otherwise noted)
Code:
killall wpasupplicant
ifconfig tiwlan0 up
killall connmand
wpa_supplicant -Dwext -i tiwlan0 -c /etc/wifi/w2.conf & dhclient
You should shortly be associated to your home network!
Enjoy NookBuntu! Make sure to thank all the great devs who have a hand in this project!
-devastatorx
Change log
Beta 0.3
Network Manager (semi working at the moment, should be fixed in next release) - penkia
Audio Working - devastatorx
On screen keyboard when focusing on a text input area - penkia
Boot into X when the device is powered on - Lincore
New base image - devastatorx & penkia
**reserved too
Wow, going to bed tonight, but I am definitely trying this tomorrow, I hope this is inevitably usable on the nook color, that steps up it's usability as a tablet.
Just a suggestion for the Mods, we should have a second forum for ubuntu on the Nook, that way it doesn't clutter up the android development and then it can expand and be organized for developers of linux vs android, might draw some more interest into this!
Honestly can't wait to try this though, good work
Holy ****, it finally happened. Downloading now!
It's gonna be a loooong day at work today of not doing any work and messin' with my nook!
Thanks for this!
Racks
I'm going to wait a bit before giving this a shot, but seriously, thanks! I'm excited about the possibilities. Do you think our hardware will be prohibitive to using this in the long-run? I know it's really early, so if that's a silly question, feel free to disregard it.
junkrobot said:
I'm going to wait a bit before giving this a shot, but seriously, thanks! I'm excited about the possibilities. Do you think our hardware will be prohibitive to using this in the long-run? I know it's really early, so if that's a silly question, feel free to disregard it.
Click to expand...
Click to collapse
At this stage it is difficult to say as not everything is working (no hardware acceleration, sound, etc)
As of right now the device runs pretty smoothly for what it is and is more responsive than it was when using the vnc method. I will be working more on the build this weekend and hope to establish a development team to keep things moving forward with consistant fixes and updates.
With a good, dedicated development team we should make some exciting progress in the near future.
Sent from my PC36100 using XDA App
I think it'll be good to note what's not working on the initial post, that way if a dev wants to help, at least they know what to look for and try to solve
racks11479 said:
It's gonna be a loooong day at work today of not doing any work and messin' with my nook!
Thanks for this!
Racks
Click to expand...
Click to collapse
I thought I was the only playing with my nook at work, now I don't feel so bad. haha.
@devastatorx, you are the man!!! Thanks so much, I can't wait to try this out.
So this is actually an Angstrom distro?
bassrebel said:
I think it'll be good to note what's not working on the initial post, that way if a dev wants to help, at least they know what to look for and try to solve
Click to expand...
Click to collapse
I will update the OP. I just wrote it last night at about. 12:30am and then let the file upload over night and hit post on my way out the door this morning. So it was a little rushed.
Sent from my PC36100 using XDA App
starkruzr said:
So this is actually an Angstrom distro?
Click to expand...
Click to collapse
Negative. This is a ububtu installation. The script just names that partition "Angstrom".
Sent from my PC36100 using XDA App
Ubuntu 10 or 11? Unity would be most worthwhile for our devices . And bugger all, I guess I'm going to have to pick a new microSD.
Ubuntu 10. As of right now there are some path issues so I am unable to get the unity-2d gui to load. Will have this fixed in the next release.
Sent from my PC36100 using XDA App
Ophbalance said:
Ubuntu 10 or 11? Unity would be most worthwhile for our devices . And bugger all, I guess I'm going to have to pick a new microSD.
Click to expand...
Click to collapse
Unity would be rather nice. Especially if we can get GPU acceleration working.
Perhaps this is a silly question, but... have you given any thought to packaging updates in some form that doesn't require downloading the entire distribution again? Yes, I can see there being issues if you don't apply them sequentially if it comes out in a zip of some kind... but it'd save you/us a ton of bandwidth. Maybe if it's all in SVN or GIT?
I'm stuck here:
Code:
sudo cp -r * /media/boot
It says "/media/boot" is no directory
MAD PROPS keep up the good work this is what android is all about might have to buy another nook color one to install in the car and one to use every where else .
Arbelzapf said:
I'm stuck here:
Code:
sudo cp -r * /media/boot
It says "/media/boot" is no directory
Click to expand...
Click to collapse
What OS are you using? The drive may be mounted elsewhere and my instructions are based off of the drives first partition being mounted at "/media/boot" and the second partition mounted at "/media/Angstrom". If this is not where the partitions are mounted then adjust the instructions for where you have them mounted or remount the device's partitions to these folders.
This should help...but I'm not saying this to be a jerk or anything...this is an Alpha and is in no way intended for daily use. Only those comfortable in Linux, and feeling adventurous should give this a go. Future releases (beta and onward) should be stable enough and easy enough to install for daily use.
To address the updates question:
I may implement a kind of crude package system after I get to a stable enough release to call it a beta. Such packages will include the modified system files and an install script to set the new update up. But like I said, that probably won't be until beta.
Difference between Pre-OTA and Post-OTA: Pre-OTA means you did NOT accept the Over The Air system update. Post means you did
Click to expand...
Click to collapse
Well... I used all of the root tools and scripts... i always had a problem where no matter what only one program would get root. Then Titanium Backup wouldnt acquire root EVER...
Then I tried the new perma temp root and still nothing.
So i did what I do best and tweaked the .bat a bit and added automatic OC scripting. Only reason I am making this thread is to help those who could not fix FULL temp root. With this I was able to always run TiBu and SetCPU no probs. I achieved this by added the ./fixsu.sh into the /bat into /vendor/bin.
There is a point where it says you HAVE to wait ten seconds... You do. I do the whole root process with my screen off just to be safe. If it reboots your phone, it means the CPU was active while you tried to alter its settings.
Also, I went ahead and added the commands to push LKM right after ROOT, and made it scale up to my highest stable undervolted frequency. Note: you can change the settings within the .bat if you want higher/lower freqs+uV. [scpll_l_val=[B]32[/B] is the frequency step. 33 is 1.8GHz and 37 is 2.0GHz(good luck! haha). 37 IS the highest you can try. vdd_uv=1320000 is the voltage. If you try anything 1188000 or below you will be locked to stock clock settings. Stock voltage is 1188000, afterall....
Thanks to coolbho3000 for the LKM (and SetCPU of course, GO BUY IT FOR HIM, he deserves the $$$). And thanks to teamwin for the root... and thanks to
eugene373 for sharing about /vendor/bin.
This is probably what you wanna read
So much text for such an easy process. JUST run the .bat Press any key when it says... READ what it says afterwards [wait 10 seconds with no activity AND screen OFF]... Press a key to continue. Go to SetCPU and Overclock. This WILL make all your programs have permanent temporary root (if you reboot you must reroot!)
Update:Ok then. I went ahead and added another .bat file which is for people who DON'T want anything auto uninstalled (which is honestly just [email protected]@)
adb shell rm -r /system/app/slackerradio.apk
adb shell rm -r /system/app/TMOUS_Navigator.apk
adb shell rm -r /system/app/Transfer-pyramid-8.30.0.26-S30.apk
adb shell rm -r /system/app/Protips.apk
adb shell rm -r /system/app/Protips.odex
adb shell rm -r /system/app/IdleScreen_Stock.apk
adb shell rm -r /system/app/IdleScreen_Stock.odex
adb shell rm -r /system/app/HtcTipWidget.apk
adb shell rm -r /system/app/HtcTipWidget.odex
adb shell rm -r /system/app/com.htc.TrendsWidget.apk
adb shell rm -r /system/app/com.htc.TrendsWidget.odex
adb shell rm -r /system/app/com.mobitv.client.tmobiletvhd.apk
adb shell rm -r /system/app/FusionStockWidget.apk
adb shell rm -r /system/app/FusionStockWidget.odex
adb shell rm -r /system/app/Stock.apk
adb shell rm -r /system/app/Stock.odex
adb shell rm -r /system/app/slackerradio.apk
adb shell rm -r /system/app/TMOUS_Navigator.apk
adb shell rm -r /system/app/Transfer-pyramid-8.30.0.26-S30.apk
adb shell rm -r /system/app/Protips.apk
adb shell rm -r /system/app/Protips.odex
adb shell rm -r /system/app/IdleScreen_Stock.apk
adb shell rm -r /system/app/IdleScreen_Stock.odex
adb shell rm -r /system/app/HtcTipWidget.apk
adb shell rm -r /system/app/HtcTipWidget.odex
adb shell rm -r /system/app/com.htc.TrendsWidget.apk
adb shell rm -r /system/app/com.htc.TrendsWidget.odex
adb shell rm -r /system/app/com.mobitv.client.tmobiletvhd.apk
adb shell rm -r /system/app/FusionStockWidget.apk
adb shell rm -r /system/app/FusionStockWidget.odex
adb shell rm -r /system/app/Stock.apk
adb shell rm -r /system/app/Stock.odex
Also, updated the fixsu.sh to be overkill, it will send to both, /data AND /vendor. This is just for those picky phones. Won't have any negative effect on anyone.
Additionally, I found a TEMPSU.BAT in another thread and went ahead and overkilled that one on the pathing too. The tempsu.bat is for those who have issue with SuperUser and/or Force Closes in trying to reach it. First, Uninstall Superuser by using the default uninstaller (clear data first!). Reboot your phone. KEEP the screen OFF. Run the ROOT.bat. After its complete leave the screen off. Then run TEMPSU.BAT. Should be no problems anymore. I came from a LONG line of SuperUser FCs. I could only get one program at a time to get ROOT. Once I got it to work the right at last, it hasn't reappeared. So don't worry.
Click to expand...
Click to collapse
dhoshman said:
Please make a version that is mac compatible PLeeeeaase. At least a linux comp version.
Click to expand...
Click to collapse
View this guys' thread for linux
Get the updated zip on a lower post 1st page
============================================================
tuscani1821 said:
Can't seem to get root to work. When it installs oc it always resets too. I have the screen off like it says. Adb drivers are installed and I can root by other methods just not this one. Maybe the oc voltage is too high that's packed in the script?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I can think of 2 problems. Either you CPU is finicky and won't run on 1.7 (32), or you are pressing 'any key' in too quick of a succession. There will be one prompt for 'any key to continue', then it will pause again with text saying to wait, and THEN press a key again. If you are doing it right and know it, try changing the OC from 32 to 30 (and lower the voltage a bit also). If still doesn't work, do the RUU reflash method and start the script on a fresh install.
bballer71418 said:
On every root method I try I can't get my device to connect. I set up adb on my comp using the unlocker tutorial and it worked on my og evo. Any reason why I can't get adb to connect to ny 3VO?
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
If you are using Win7 or Vista (same thing, really) @ 64bit, you have to remember that the drivers for ADB 64bit are not digitally signed. So you will have to press F8 key at your PC startup, then select 'Disable Driver Signature Enforcement. Be sure to go into the Device Manager and ensure you see 'ADB Android Interface' under 'Android Phones'. If you see a triangle with a yellow thing it means the driver is not properly loaded. This is the only thing that will keep ADB from recognizing your phone... That or you have USB Debugging disabled on your phone (Menu>Settings>Applications>Development.
ianoob said:
Been running for almost a day strait now. The only wierd thing is I keep getting the popup saying SetCPU has been granted SU permission every 30sec or so while the phone is in use :s
Edit, before I get flamed... I know I can tell SU not to warn me, but SetCPU has never done this to me except after reboots.
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Yea I get it too. The problem is eMMC is making us lose the temp root. But thanks to the original founder, we can add and symlink to /vendor/bin and just have the system reapply the privileges.
fdavila17 said:
Guys which one I'm I suppose to download?
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
POST-after OTA
PRE-Before OTA
IF you KNOW that you are doing it all right and are getting errors out the ying yang, read BELOW
ierv69 said:
Could you please tell me a link to download the ruu file..
I'm on 1.11.651.2
Click to expand...
Click to collapse
RUU_Shooter_Sprint_WWE_1.11.651.2_Radio_radio_0.97 .00.0518_NV_SPCS_1.15_release_193503_signed.exe
1.11
Click to expand...
Click to collapse
RUU_Shooter_S_Sprint_WWE_1.13.651.7_Radio_0.97.10. 0530_NV_NV_SPCS_1.16_release
Click to expand...
Click to collapse
First do the first RUU... Then go ahead and do the next one. Don't worry about any exploits that may be covered up, the kernel is the same and more than likely nothing else of value was touched... Since it wasn't noticed. Just do it. Then use the POST Ota zip.
worked now didnt it HAHAHAHAHAHAHA
I get a 'file is broken' error on adb.exe. I wouldn't care since I have adb already on my desktop and in my path, but it won't finish extracting files with that file dying. Not sure if it's just me or not.
This is on the pre-ota rar file.
smw6180 said:
I get a 'file is broken' error on adb.exe. I wouldn't care since I have adb already on my desktop and in my path, but it won't finish extracting files with that file dying. Not sure if it's just me or not.
This is on the pre-ota rar file.
Click to expand...
Click to collapse
yea... i see... everytime i upload it gets corrupted... joy...
UPDATE: Reuploaded and fixed... Checked it myself. Enjoy
Thanks for making overclocking dummy proof. I am tired and saw this post after seeing the overclock thread and thinking *that's too much for the morning*.
Good job.
Tilde88 said:
yea... i see... everytime i upload it gets corrupted... joy...
UPDATE: Reuploaded and fixed... Checked it myself. Enjoy
Click to expand...
Click to collapse
Yep, that fixed it. About to check it out. Thanks!
akiradavis said:
Thanks for making overclocking dummy proof. I am tired and saw this post after seeing the overclock thread and thinking *that's too much for the morning*.
Good job.
Click to expand...
Click to collapse
no problem man. Now that I have my phone basically with full Root privs, I dont need to restart anymore. But in the rare event that I HAVE to... It'll be 45 seconds to root and OC with nothing done.
i just wish i could do something about all the hostility in this forum...
i have tried this 2 times now.. the rooting process seems to go fine, but when the damn setCPU app tries to run, it says it cannot access root or whatever.. basically leaving me in setCPU safemode, where nothing can be done.. not sure whats goin on.. tried doing it the manual way before your .bat got uploaded and same stuff happened.. i know i have root cause i can see # in adb shell.. any suggestions.. its the latest SetCPU 2.2.4
EDIT: I think I finally got it.. for some reason, after reboots, superuser didnt uninstall.. so i uninstalled before i ran .bat and i opened titanium backup to check if it would request root from superuser and it did. i then opened setCPU and it requested superuser also.. was able to get it up to 1.8Ghz without shooting any commands. i had to do a autodetect though to get it to recognize correct cpu frequencies.. after that, i ran a full benchmark in Quadrant.. got a 2775!! W00t
Tilde88 said:
So much text for such an easy process. JUST run the .bat Press any key when it says... READ what it says afterwards [wait 10 seconds with no activity AND screen OFF]... Press a key to continue. Go to SetCPU and Overclock. This WILL make all your programs have permanent temporary root (if you reboot you must reroot!)
Click to expand...
Click to collapse
might want to alert people you put in some removal of stock apps - not a big deal cause i looked at your .bat first, but some people may not.
thanks for the script too!
worked first time. And Riggs, yeah, first thing I did was check the bat file and removed the remove lines.
First, thanks for this! Second, I'm not 100% sure, but I think the fixsu.sh file needs changed.. you are pushing busybox/su/etc to /vendor/bin, but fixsu.sh thinks they are still in /data/local/tmp.
If I'm wrong, ignore me... but it's throwing a number of errors that do not seem right..
Thanks again,
Scott
I had the same problem with Superuser. I had to uninstall it before this script would work.
And I wasn't crazy about the app removal lines either.. I removed them from my copy of the script.
Scott
Delvorak said:
First, thanks for this! Second, I'm not 100% sure, but I think the fixsu.sh file needs changed.. you are pushing busybox/su/etc to /vendor/bin, but fixsu.sh thinks they are still in /data/local/tmp.
If I'm wrong, ignore me... but it's throwing a number of errors that do not seem right..
Thanks again,
Scott
Click to expand...
Click to collapse
I noticed error when that part of process went thru in .bat also.. returned with error that no such file or directory exists... But last run of .bat though, went thru as far as setCPU n titanium backup..
:Sent from my EVO 3D:
Here are some screenies of setCPU n Quadrant score after running .bat n getting it OC'd.
{
"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"
}
:Sent from my EVO 3D:
Flawless! Can't thank you enough.
DDD-EVO
Does this wrk on a MAC
Sent from my PG86100 using XDA Premium App
drewski83 said:
Here are some screenies of setCPU n Quadrant score after running .bat n getting it OC'd.
:Sent from my EVO 3D:
Click to expand...
Click to collapse
Same here but no go with Titanium B, oh well.........
i ran the early version of fr3vo, then the one from yesterday (with /vendor/bin), then this one early morning. fr3vo and this script have given me titanium backup/msl reader working.
1728mhz good -- 2179 on quadrant.
edit: barnacle not working at all. i can see the ad-hoc network but im unable to connect/get an IP.
Best Permanent Temp Root so far... Thanks Bro!
Guys which one I'm I suppose to download?
Sent from my PG86100 using XDA Premium App
OC!!!
HI, Everything went fine, I have almost all my root apps working fine. But When I go to SetCPU thr freq is 1188 and the min I put it on 192000.. Cant make the max go more..Please help!!!!
{
"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 can confirm that this process works on Update v5.2.6.8. Any other version beyond that your mileage may vary. "ADB debugging" and "Apps from Unknown Sources" should be enabled. I would like to thank the following members because without their resources this walkthrough wouldn't have been possible: @diplomatic for the exploit, @el7145 for leaving a cookie crumb trail of clues within his comments in this thread which I had to follow like the yellow brick road in order to repeat his success, @rbox for the custom recovery and pre-rooted image, and @AFTVnews.com because if it hadn't been for your article I probably would've never gotten my AFTV device rooted in time before the 5.2.6.9 OTA update. Oh, I almost forgot... and thanks @Chainfire for SuperSU . And also @teamfresno for the advice.
ACHIEVING TEMPORARY ROOT PERMISSIONS
1. Download and install ADB on your PC.
2. Download "mtk-su_r4.zip" and extract "arm64" folder in ADB install directory (C:\adb).
3. Run command below:
Code:
adb connect 192.168.0.XX
(IP address of your Fire TV device)
4. Transfer mtk-su to your /data/local/tmp folder:
Code:
adb push C:/adb/arm64/mtk-su /data/local/tmp/
5. Open an adb shell:
Code:
adb shell
6. Change to your tmp directory:
Code:
cd /data/local/tmp
7. Add executable permissions to the binary:
Code:
chmod 755 mtk-su
8. Run the exploit:
Code:
./mtk-su
NOTE – The following line should display:
New UID/GID: 0/e
9. Ensure that mtk-su succeeded in setting selinux to permissive by typing the following command:
Code:
getenforce
INSTALLING TWRP & SLOANE
1. Download rbox's TWRP custom recovery and the latest pre-rooted ROM from your PC and copy it to the root of a USB stick [or microSD card].
2. Connect the USB stick [or microSD] to your AFTV2.
3. Change to USB Storage directory:
Code:
cd /storage/usbotg/
NOTE – If recovery is on microSD
Code:
cd /storage/sdcard1
4. Run the zip file. This will automatically run SU:
Code:
sh /storage/usbotg/firetv2_recovery_v7.zip
If recovery is on microSD
Code:
sh /storage/sdcard1/firetv2_recovery_v7.zip
NOTE – It should print out a following lines:
Extracting unzip...
Remounting /system read-write...
Extracting...
Remounting /system read-only...
5. Reboot to Recovery:
Ctrl+C (closes out previously ran script)
Code:
adb reboot recovery
6. Your AFTV2 should reboot to a black screen displaying the Amazon logo, followed by a prompt stating that the device will automatically restart, but if not to unplug then re-plug the power source. It will not automatically restart, but DO NOT unplug the device yet.
{
"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"
}
7. If you copied the recovery and ROM onto a USB stick then you will need to disconnect it from the AFTV2, and connect a USB hub with at least 2 ports to the AFTV2, and connect both a USB keyboard and the USB stick to the hub at this time. If you copied the recovery and ROM onto a microSD then connect a keyboard to the empty USB port at this time.
8. Now unplug then re-plug the power source and you will be presented with the TWRP splash screen.
9. At the boot menu, press the RIGHT arrow key on the USB keyboard to boot into TWRP recovery.
NOTE – whatever you do DON'T let your AFTV2 idle for too long on the initial recovery boot menu screen or it will time out thus restarting, requiring you to repeat the prior steps.
10. Use the arrow keys to select the "Install" in TWRP.
11. "Select Storage", and choose the location where you stored the pre-rooted ROM.
12. Select "Swipe to Confirm Flash" to start the installation.
13. Select "Reboot System" once the file has finished installing in order to restart the AFTV2.
For those feeling a little adventurous/ambitious then feel free to follow this guide created by @g422 as he discuses where to go from here by delving into other avenues to truly tap into the power of your AFTV2 such as what's "Xposed" and the benefits it offers for rooting your device, and also how to backup your current Fire OS install using TWRP.
Also shouts out to @PhoenixMark who created a guide for Mac users based on my write-up as how to enable root here.
This will work if we have a bricked device stuck on the Amazon logo?
Thanks for this! can't wait till I get home and finish the process with your guide. Other guides had my head spinning. Achieved temp root but no mention of pushing super su.
Oh wow, looks like that exploit spread like wildfire!!
Wonder if anybody will see if this works for the firestickv2 (I don't trust myself to crack the case of mine open lol)
b0ricuaguerrero said:
Thanks for this! can't wait till I get home and finish the process with your guide. Other guides had my head spinning. Achieved temp root but no mention of pushing super su.
Click to expand...
Click to collapse
Worked like a charm on my fire tv 2, but I did notice voice control seems to be broken after achieving permanent root.
Anyone else experienced this????
Thank you for putting this guide together! Also thanks to @rbox for twrp and the rom!Finally got root on my Fire TV 2!
Sent from my SM-G9650 using Tapatalk
worked flawlessly on Amazon fire tv 2, the only thing i would say about the instruction for me was that usbotg was not recognised I only had sdcard0 (int storage) sdcard1 (sd card) apart from that great job thank you
ps there was an update waiting to install from amazon which i blocked, perhaps they are patching already
JUSTINMARMER said:
This will work if we have a bricked device stuck on the Amazon logo?
Click to expand...
Click to collapse
Idk. I think we're pretty much in the same boat now: https://forum.xda-developers.com/showpost.php?p=79063299&postcount=197
Delete... duplicate comment
b0ricuaguerrero said:
Thanks for this! can't wait till I get home and finish the process with your guide. Other guides had my head spinning. Achieved temp root but no mention of pushing super su.
Click to expand...
Click to collapse
Not a problem. Just giving back where I can
b0ricuaguerrero said:
Worked like a charm on my fire tv 2, but I did notice voice control seems to be broken after achieving permanent root.
Anyone else experienced this????
Click to expand...
Click to collapse
I don't use voice activation, voice assistants, etc. as a preference. I'm just paranoid like that
huffmybrd said:
Oh wow, looks like that exploit spread like wildfire!!
Wonder if anybody will see if this works for the firestickv2 (I don't trust myself to crack the case of mine open lol)
Click to expand...
Click to collapse
It's worth looking into. Since I currently own one as well I'll see a/b performing these same instructions and post my findings at some point in time.
salsoul said:
worked flawlessly on Amazon fire tv 2, the only thing i would say about the instruction for me was that usbotg was not recognised I only had sdcard0 (int storage) sdcard1 (sd card) apart from that great job thank you
ps there was an update waiting to install from amazon which i blocked, perhaps they are patching already
Click to expand...
Click to collapse
I tried both ways, with the microSD and USB so I know it works if you followed what was stated in the instructions to the T... I know that when I attempted the USB option the first time, I had forgot to plug the USB stick in which made it show up as USB (0) which is only logical explanation I can think of for what happened to you.
Krog18 said:
Thank you for putting this guide together! Also thanks to @rbox for twrp and the rom!Finally got root on my Fire TV 2!View attachment 4718781
Sent from my SM-G9650 using Tapatalk
Click to expand...
Click to collapse
Not a problem, glad I could help
This is fantastic work!!!
Do you know if root can be 'hidden' to Netflix app won't block it's use?
n8wwd said:
This is fantastic work!!!
Do you know if root can be 'hidden' to Netflix app won't block it's use?
Click to expand...
Click to collapse
Thanks, and unfortunately, no. SuperSU is the component that enables root which can be detected by apps that disengage user functionality when they discover root is enabled. I attempted to install Magisk v18.1 to counteract this side effect, but failed miserably w/ the end result to the point that my AFTV2 does a constant boot loop as recounted here. Magisk would be the only option I'm aware of to make root 'hidden', but it's not worth it at the cost of turning your device into a boot looping paper weight.
True. Nothing like having a 'brick on a rope' so to speak. That's not a 'deal breaker' as I subscribe to IPTV services that out performs it anyway. Do you know if Hulu does the same as Netflix? The missus may take exception if it killed that...
---------- Post added at 12:22 AM ---------- Previous post was at 12:20 AM ----------
I guess the main reason I'd want root access is to take all of the preloaded apps off for room, as well as have the ability to use the external storage within apps.
---------- Post added at 12:48 AM ---------- Previous post was at 12:22 AM ----------
well...I answered my own question..seems Hulu doesn't like it either...*sigh* Time to search for a box that can hide root so my wife won't blow a gasket....
Wait, we can't use Netflix if we are rooted? Yikes.
I've had no trouble with Netflix yet since I rooted this yesterday, but of course ymmv.
Sent from my SM-G9650 using Tapatalk
---------- Post added at 08:36 AM ---------- Previous post was at 07:44 AM ----------
urbanman2004 said:
Thanks, and unfortunately, no. SuperSU is the component that enables root which can be detected by apps that disengage user functionality when they discover root is enabled. I attempted to install Magisk v18.1 to counteract this side effect, but failed miserably w/ the end result to the point that my AFTV2 does a constant boot loop as recounted here. Magisk would be the only option I'm aware of to make root 'hidden', but it's not worth it at the cost of turning your device into a boot looping paper weight.
Click to expand...
Click to collapse
Damn, sorry to hear that. I imagine what happened is the result of magisk patching the kernel on a locked bootloader. I hope you're able to get it fixed. Good luck to you!
Sent from my SM-G9650 using Tapatalk
Krog18 said:
Damn, sorry to hear that. I imagine what happened is the result of magisk patching the kernel on a locked bootloader. I hope you're able to get it fixed. Good luck to you!
Sent from my SM-G9650 using Tapatalk
Click to expand...
Click to collapse
Thanks. You never know, somebody smart enough might actually come up with a tool capable of relieving my device from its eternal boot loop hell
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.