http://firewater-soff.com/instructions/
works fine, now s-offed
ticklemepinks said:
http://firewater-soff.com/instructions/
works fine, now s-offed
Click to expand...
Click to collapse
Already???!!! Awesome! :good:
Sim-X said:
Already???!!! Awesome! :good:
Click to expand...
Click to collapse
yep thank me later lol
And confirmed! Can't wait to get rid of ugly development test, bring on the custom hboot. I have only had the phone for not even 2 days and already s-off!
{
"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"
}
I concur.
Looks like it's time to update my Hboot guide.
Sent from my EVO LTE
For some reason when I get to the command "chmod 755 /data/local/tmp/firewater" it's telling me "operation not permitted". Strange cause adb shell has superuser permissions...gonna try on my desktop pc.
FlowingAway said:
For some reason when I get to the command "chmod 755 /data/local/tmp/firewater" it's telling me "operation not permitted". Strange cause adb shell has superuser permissions...gonna try on my desktop pc.
Click to expand...
Click to collapse
I had that too.. check your phone's screen and accept the root request.
I can also confirm it works. I used the HTCDev Unlocked/Rooted method and am now S-Off.
Wow I am S-Off. That was quick and easy. Only complication was having to download an app (USBDebug) from the play store in order to enable usb debugging mode.
knlmwq said:
Wow I am S-Off. That was quick and easy. Only complication was having to download an app (USBDebug) from the play store in order to enable usb debugging mode.
Click to expand...
Click to collapse
Settings/About/Software Information/More/ tap Build number 7 times. Adds Developer options. back to Settings just above Activate this device. Enables USB Debugging there.
Another confirmed success! :GOOD:
I'm getting an error on the last line
"[email protected]_m8whl:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8whl:/ #
C:\Users\J>/data/local/tmp/firewater
The system cannot find the path specified."
---------- Post added at 10:29 PM ---------- Previous post was at 10:27 PM ----------
I'm getting an error on the last line
"[email protected]_m8whl:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8whl:/ #
C:\Users\J>/data/local/tmp/firewater
The system cannot find the path specified."
---------- Post added at 10:32 PM ---------- Previous post was at 10:29 PM ----------
I'm getting an error on the last line
"[email protected]_m8whl:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8whl:/ #
C:\Users\J>/data/local/tmp/firewater
The system cannot find the path specified."
---------- Post added at 10:34 PM ---------- Previous post was at 10:32 PM ----------
I'm getting an error on the last line
"[email protected]_m8whl:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8whl:/ #
C:\Users\J>/data/local/tmp/firewater
The system cannot find the path specified."
---------- Post added at 10:35 PM ---------- Previous post was at 10:34 PM ----------
I'm getting an error on the last line
"[email protected]_m8whl:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8whl:/ #
C:\Users\J>/data/local/tmp/firewater
The system cannot find the path specified."
confirmed
thank you for the heads up @thicklemepinks
this is ridiculous it took me 3 minutes to get soff with htc dev unlocked and rooted
the guys who made this possible deserve some donations for sure
I'm getting an error on the last line
"[email protected]_m8whl:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8whl:/ #
C:\Users\J>/data/local/tmp/firewater
The system cannot find the path specified."
I'm at a loss here.
C:\Users\Matt\Desktop\AndroidSDK\adt-bundle-windows-x86_64-20130917
-tools>adb shell
[email protected]_m8whl:/ $ su
su
[email protected]_m8whl:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
Unable to chmod /data/local/tmp/firewater: Operation not permitted
supersu shows in its log that it allowed "shell"...when i type the cdmod command i am receiving no prompts on the phone screen. should i be?
I'm getting an error on the last line
"[email protected]_m8whl:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8whl:/ #
C:\Users\J>/data/local/tmp/firewater
The system cannot find the path specified."
jvs60 said:
I'm getting an error on the last line
"[email protected]_m8whl:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8whl:/ #
C:\Users\J>/data/local/tmp/firewater
The system cannot find the path specified."
Click to expand...
Click to collapse
i bolded the part i think you need to cut out
jvs60 said:
I'm getting an error on the last line
"[email protected]_m8whl:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8whl:/ #
C:\Users\J>/data/local/tmp/firewater
The system cannot find the path specified."
Click to expand...
Click to collapse
last line tells me you are not in the adb shell anymore. since thats a response from windows are you sure you are not getting kicked out of adb shell.
FlowingAway said:
I'm at a loss here.
C:\Users\Matt\Desktop\AndroidSDK\adt-bundle-windows-x86_64-20130917
-tools>adb shell
[email protected]_m8whl:/ $ su
su
[email protected]_m8whl:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
Unable to chmod /data/local/tmp/firewater: Operation not permitted
supersu shows in its log that it allowed "shell"...when i type the cdmod command i am receiving no prompts on the phone screen. should i be?
Click to expand...
Click to collapse
your case IMO seems to be the system write protection.
Why don't you use the wp_mod.ko from flare.
this is the guide someone wrote on the htc m8 dev forum just to clarify
first reboot to recovery and mount system go to the file manager and you should've downloaded the module from the htc m8 forum here on xda.
copy the module to system/lib/modules and chmod 644
reboot
open up terminal and type su
then
insmod /system/lib/modules/wp_mod.ko
to verify that is loaded type lsmod and see if is loaded.
last thing go to system/etc/ and find the file init.installrecovery.sh and add
insmod /system/lib/modules/wp_mod.ko
to the end of the file save and exit and reboot.
now when you reboot and you open terminal and type lsmod the wp_mod should be loaded and it should say permanent.
now try fire and water again.
Thank you @chemjb it wasn't even that complicated. I guess something went wrong when I flashed the supersu zip the first time. I flashed again and this time it took. Worked first try after that. S-Off and ready to roll.
Related
Firstly i did not do this guide. it took it from this forum and just compile so that newbie like me can easily root their tattoo.....
ROOTING TATTOO
Download the ZIP file attached to this post. Extract the files to a safe location - perhaps C:\Tattoo ?
Now, you'll need adb for windows. You can get it from COBURN website's server here: ADB for windows.
Make sure your device is in USB Debug Mode (Settings > Applications > Development).
Extract all the files in the adb4win zip file to your C:\Tattoo folder.
Now, go to Command Prompt. In XP, it's under System Tools in Accessories. In Vista/7, it'll be under accessories.
Do the following at the command line:
C:\Users\Coburn> cd C:\Tattoo
Then you will get this C:\Tattoo
Next type in this:
C:\Tattoo> adb-windows shell "mkdir /data/local/bin" (with the quotes!).
If you get a error (like mkdir failed, file/folder exists), this is fine!
just means that the folder already exists in your phone
Now, run this command:
C:\Tattoo> adb-windows push m7 /data/local/bin/m7
this will just take a few seconds
Run this:
C:\Tattoo> adb-windows shell "cd /data/local/bin && chmod 755 ./m7" (with the quotes!)
This allows you to run the sucker. Looks like something nothing happen but it did something.
C:\Tattoo> adb-windows shell
This will dump you at a "$" shell. do the following:
C:\Tattoo> adb-windows shell
$ cd /data/local/bin
$ while ./m7 ; do : ; done
...lotsa text will flow down your screen. This is normal.
Soon, you'll be greeted with this:
#
This is the root prompt! If you get stuff like this:
# usage: reboot ...
usage: reboot ....
usage: reboot ...
Just keep your cool, press enter and the # will pop again. This is due the exploit spawning reboots to gain the shell.
Next type in this:
export LD_LIBRARY_PATH=/system/lib
export PATH=/system/bin
Check if u have root, type:
id
you will get
# id
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
The uid=0(root) is important, so call your phone is root.
REMOUNT PARTITION (SU)
Now you need to install su. Exit your root shell (via CTRL+C) and download this su.zip and extract it to C:\Tattoo.
DO NOT EXIT THE COMMAND PROMPT WINDOW.
in your command prompt window, do this:
C:\Tattoo> adb-windows push su /data/local/bin/su
Then break out a shell...
C:\Tattoo> adb-windows shell
at the $ prompt, enter:
$ chmod 755 /data/local/bin/su
$ cd /data/local/bin/
$ while 'true' ; do ./m7 ; done
It will change from $ to #
Type in this:
export LD_LIBRARY_PATH=/system/lib
export PATH=/system/bin
Next type in this:
# chown root.root /data/local/bin/su
# chmod 4755 /data/local/bin/su
# mount -o rw,remount /dev/block/mtdblock5 /data
# mount -o rw,remount /dev/block/mtdblock3 /system
After that, you can exit out of the root shell, and try a normal shell and this:
$ /data/local/bin/su
...which should make you get a nice # prompt.
Custom Boot.img:
Boot img v2:http://forum.xda-developers.com/show...0&postcount=38
Tattoo-hack.ko:http://forum.xda-developers.com/atta...2&d=1266670581
Download this flash_image:http://forum.xda-developers.com/attachment.php?attachmentid=287463&d=1267386499
adb push flash_image ./data/local/bin/flash_image
adb push Mainfram3.boot.02.img /sdcard/Mainfram3.boot.02.img
adb push tattoo-hack.ko ./data/local/bin/tattoo-hack.ko
c:\tattoo>adb shell
$ su
su
su: access granted, courtesy of www.magicandroidapps.com
# insmod /data/local/bin/tattoo-hack.ko
#mount -o rw,remount /dev/block/mtdblock5 /data
#mount -o rw,remount /dev/block/mtdblock3 /system
#chmod 755 /data/local/bin/flash_image
#/data/local/bin/flash_image boot /sdcard/Mainfram3.boot.02.img
Cutom Recovery Img:
After custom boot.img
adb push TCRI.alpha.img /sdcard/TCRI.alpha.img
c:\tattoo>adb shell
#/data/local/bin/flash_image recovery /sdcard/TCRI.alpha.img
once again i did not make the guide...i only compile it from different thread and put them as 1....tats all....thanks to all the devs that came up with the guide.....
hi!
will be possible flash official ROM made HTC after rooting proces?
I'm totaly new to this android applications
correct me if im wrong...you can always flash official rom frm htc for that paticular phone model....whether root or not....
the flash image no longer exists...
@Bikers
Download here:http://forum.xda-developers.com/attachment.php?attachmentid=287463&d=1267386499
@shazarul
Correct the link in the post.
c:\tattoo>adb shell
$ su
su
su: access granted, courtesy of www.magicandroidapps.com
i get permision denied! I know there is somewhere else a thread like this but i jus t can't find it...
try it with root 1 click by maverixx
have change the flash_image link..... biker i think u have to root it again???/ i think should b the easy way out....
just flashed custom boot img using this tutorial, thanks !
Thanks a lot, but I have a problem.
When I get to:
Code:
adb push Mainfram3.boot.02.img /sdcard/Mainfram3.boot.02.img
I get this:
{
"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"
}
I had the same problem with http://forum.xda-developers.com/showthread.php?t=644279&page=6 1 click root script when pushing to /sdcard...
have you tried to put it directly in your sd card? Did you putted your phone in MSSync at the usb options?
try to unmount sdcard from the phone, with the command in the notification bar of the tattoo
i am having this error while flashing custom recovery image ...
# /data/local/bin/flash_image boot /sdcard/Mainfram3.boot.02.img
/data/local/bin/flash_image boot /sdcard/Mainfram3.boot.02.img
error opening /sdcard/Mainfram3.boot.02.img: No such file or directory
#
Click to expand...
Click to collapse
where am i getting it wrong ??? till that i have no issues in following tutorial...
please help me...
chtamina said:
try to unmount sdcard from the phone, with the command in the notification bar of the tattoo
Click to expand...
Click to collapse
this suggestion solved my problem.... thanks chtamina..... you made my day...
Hi guys......
I have Butterfly s 901e with HBOOT 1.57, when I tried to s-off with firewater, I didn't get anything while in the process..... when I made the last step ([email protected]:/ # chmod 755 /data/local/tmp/firewater then [email protected]:/ # /data/local/tmp/firewater), I got nothing.... I tried to check data/local/tmp manually in ES File Explorer to see what is going on, I noticed that after pushing firewater through adb it will appear in the TMP folder and after executing [email protected]:/ # chmod 755 /data/local/tmp/firewater then [email protected]:/ # /data/local/tmp/firewater the firewater file just disappear from TMP folder, and nothing is starting....
please help.
I am despeartely in need of your help here guys, I got this brand new HTC one m8 from sprint and am stuck during the process of getting the s-off while following this guide thread to sim unlock the device. I kept getting this same output after following all the steps for rooted m8
Code:
C:\HTC\adt-bundle-windows-x86-20130522\sdk\platform-tools>adb shell
[email protected]_m8whl:/ $ su
su
[email protected]_m8whl:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8whl:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]_m8whl:/ #
thats all I get after following all the steps.
am so confused and stuck cause am sure without s-off I cant get it to work. and I kept getting this handsfree activation whenever I boot the phone. Please help
cuteomar said:
I am despeartely in need of your help here guys, I got this brand new HTC one m8 from sprint and am stuck during the process of getting the s-off while following this guide thread to sim unlock the device. I kept getting this same output after following all the steps for rooted m8
Code:
C:\HTC\adt-bundle-windows-x86-20130522\sdk\platform-tools>adb shell
[email protected]_m8whl:/ $ su
su
[email protected]_m8whl:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8whl:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]_m8whl:/ #
thats all I get after following all the steps.
am so confused and stuck cause am sure without s-off I cant get it to work. and I kept getting this handsfree activation whenever I boot the phone. Please help
Click to expand...
Click to collapse
Did you do "adb reboot, then adb wait-for-device push firewater /data/local/tmp" before the other commands?
gstanke said:
Did you do "adb reboot, then adb wait-for-device push firewater /data/local/tmp" before the other commands?
Click to expand...
Click to collapse
Also, if you did any updates with your OTA, this will not work!
I used Sunshine, and paid the $25 to have them help me, it was the best 5 mins of my life!
After you get frustrated and try Firewater a few dozen times... head over to theroot.ninja and pay the $25 dollars... TOTALLY WORTH IT!!
cuteomar said:
I am despeartely in need of your help here guys, I got this brand new HTC one m8 from sprint and am stuck during the process of getting the s-off while following this guide thread to sim unlock the device. I kept getting this same output after following all the steps for rooted m8
Code:
C:\HTC\adt-bundle-windows-x86-20130522\sdk\platform-tools>adb shell
[email protected]_m8whl:/ $ su
su
[email protected]_m8whl:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8whl:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]_m8whl:/ #
thats all I get after following all the steps.
am so confused and stuck cause am sure without s-off I cant get it to work. and I kept getting this handsfree activation whenever I boot the phone. Please help
Click to expand...
Click to collapse
I fought and fought with adb, rooting, and s-off and Im well versed in adb etc. Just do yourself a favor, pay the $25 fee and go with sunshine. Its expensive but will save you so much headache
Success100 said:
I fought and fought with adb, rooting, and s-off and Im well versed in adb etc. Just do yourself a favor, pay the $25 fee and go with sunshine. Its expensive but will save you so much headache
Click to expand...
Click to collapse
I had no problem dropping the 25 bones for the S off. Those guys work hard and I was having a headache trying firewater which wouldn't work for me. It's easy and imo the $25 was worth it.
At&t user here saying "just do it"
You will sleep better after spending $25 and easily gain S-OFF
at the last line :
"adb reboot
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater <.----
it says to me "firewater[2]: syntax error: '(' unexpected" after I press enter
edit : that says my cmd :
Code:
C:\android-sdk\platform-tools>adb reboot
C:\android-sdk\platform-tools>adb wait-for-device push firewater /data/local/tmp
218 KB/s (670 bytes in 0.003s)
C:\android-sdk\platform-tools>adb shell
[email protected]_m8:/ # su
su
[email protected]_m8:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
/data/local/tmp/firewater[2]: syntax error: '(' unexpected
1|[email protected]_m8:/ #
Htconem8user said:
at the last line :
"adb reboot
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater <.----
it says to me "firewater[2]: syntax error: '(' unexpected" after I press enter
edit : that says my cmd :
Code:
C:\android-sdk\platform-tools>adb reboot
C:\android-sdk\platform-tools>adb wait-for-device push firewater /data/local/tmp
218 KB/s (670 bytes in 0.003s)
C:\android-sdk\platform-tools>adb shell
[email protected]_m8:/ # su
su
[email protected]_m8:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
/data/local/tmp/firewater[2]: syntax error: '(' unexpected
1|[email protected]_m8:/ #
Click to expand...
Click to collapse
Firewater is dead ... they abandoned it last week sometime
clsA said:
Firewater is dead ... they abandoned it last week sometime
Click to expand...
Click to collapse
oh :/
I've read that somewhere else too.
But I thought it should be still working.
is there any other method then sunshine ? Because currently I can't buy it now.
And I don't want to wait...
Why should there be only one option ( sunshine) to take s off ?
Is it that hard to code a working programm ?
Htconem8user said:
is there any other method then sunshine ?
Click to expand...
Click to collapse
unfortunately,no (unless you have an old hboot version)
Why should there be only one option ( sunshine) to take s off ?
Is it that hard to code a working programm ?
Click to expand...
Click to collapse
No disrespect mate but it looks like you underestimate the amount of work, time and knowledge needed to:
find a security hole and how to exploit it so you can grant s-off
do it again everytime HTC updates their firmware to patch these security holes
code everything so the average user can achieve s-off using an automated program
maintain everything (program, servers, website)
This have nothing to do with C# programming you can learn at high school to make your own calculator
So to answer your question, Yes its probably hard to do
alray said:
find a security hole and how to exploit it so you can grant s-off
do it again everytime HTC updates their firmware to patch these security holes
code everything so the average user can achieve s-off using an automated program
maintain everything (program, servers, website)
Click to expand...
Click to collapse
okay I got it. thanks for the reply^^
My Hboot is 3.19.0.0000 <- is it old ?
NOTE THIS ROOT ONLY WORKS WITH FIRE OS 5.0.1 AND ONLY THE HD 7 NOT THE 10 OR 8
WE HAVE GAINED ROOT!!!
Thanks to @jkchr1s for the help and the windows bat file, @csolanol for actually finding the root, and @diegocr as well as the @Chainfire SuperSu for the root binaries!!
Heres a video for you guys who need help:
https://www.youtube.com/watch?v=ux-2b3X3BlI&feature=youtu.be
Just download the zip file from this link and remember to use a windows/linux device for now.
Mediafire Mirror #1
For windows hit install.bat and follow trough the steps
For Linux run it through the linux command prompt
2nd way to root:
1. Download supers from chain fires website https://download.chainfire.eu/696/supersu/
2. Download @ggow custom recovery or @cnsoal Twrp
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548
http://forum.xda-developers.com/ama...ecovery-cyanogen-recovery-2015-11-04-t3240726
3. Place the recovery image in the same folder as adb and fastboot.
4. Put your fire in fastboot mode
5. Boot into the custom recovery via "fastboot boot <recoverimsgename>.img.
6. You should be in the cynogen recovery (Or twrp depending on which recovery you downloaded_
7. Then pick adb sideload, and select it and manually install drivers. If you're too lazy just place su in your SD card and flash the zip from there.
8. Adb sideload supersu and you'll get root!!
REMEMBER WE ARE NOT LIABLE IF YOUR TABLET IS BRICKED!!!
I have also left the boot.img tool as well as the modified versions of the boot.img files just incase if anyone else wants to probably dig deeper and explore more about the boot.img file
Have you tried adding the su binary to /sbin in the ramdisk, and editing default.prop to ro.secure=0?
just adding it to /sbin wont solve this. you would have to add all the selinux info for it also and then also manage to start the su daemon.
ro.secure=0 is already inside the attached boot.img above, doesn't seem to help
If we have r/w to the filesystem, take a look at the root script in this LG package: http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
Do you think this method would work?
Lol wow! Seems to be sparked by my discovery of this new root method! Anyhow, @jkchr1s might be on to something.
---------- Post added at 11:12 AM ---------- Previous post was at 11:10 AM ----------
jkchr1s said:
If we have r/w to the filesystem, take a look at the root script in this LG package: http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
Do you think this method would work?
Click to expand...
Click to collapse
I'll try it!
EDIT: DON'T DO IT! IT CONTAINS LG DEVICE SPECIFIC THINGS AND IT COULD BRICK YOUR DEVICE. GOOD THING I LOOKED AT THE INSTALL.BAT BEFORE I TRIED IT!
Vlasp said:
Lol wow! Seems to be sparked by my discovery of this new root method! Anyhow, @jkchr1s might be on to something.
---------- Post added at 11:12 AM ---------- Previous post was at 11:10 AM ----------
I'll try it!
EDIT: DON'T DO IT! IT CONTAINS LG DEVICE SPECIFIC THINGS AND IT COULD BRICK YOUR DEVICE. GOOD THING I LOOKED AT THE INSTALL.BAT BEFORE I TRIED IT!
Click to expand...
Click to collapse
I don't mean to run the root.bat file, look at the root script. It copies SuperSU binaries, adds a su service, and chcon's the necessary files.
jkchr1s said:
I don't mean to run the root.bat file, look at the root script. It copies SuperSU binaries, adds a su service, and chcon's the necessary files.
Click to expand...
Click to collapse
Yeah, but we are going to have to change the device specific stuff (if it matters for our device).
I have updated the thread!! Thanks @jkchr1s for the clear steps and @diegocr for helping out and giving us r/w ability.
This will work for rooting this device now.
Someone is root .............
With boot.img
Vlasp said:
This or KingRoot will work for rooting this device now.
Click to expand...
Click to collapse
I adapted the guide and u know what?. I am root!!!
Did all the steps by hand and SuperSu is working, i can make su in adb shell.
I can't write a guide right now, i have to go out of the house but this is done guys.
Vlasp said:
This or KingRoot will work for rooting this device now.
Click to expand...
Click to collapse
What do you mean? KingRoot says it failed booting with the boot-firestarter.img
jkchr1s said:
What do you mean? KingRoot says it failed booting with the boot-firestarter.img
Click to expand...
Click to collapse
yeah, sorry. only the tutorial will work.
Vlasp said:
This will work for rooting this device now.
Click to expand...
Click to collapse
Dosent work?
Vlasp said:
yeah, sorry. only the tutorial will work.
Click to expand...
Click to collapse
Sorry, I'm not seeing a guide or tutorial on that link. That's a link to KingRoot.
Just for those of you that wanna root it just now:
Files needed and a boot.img to apply with fastboot boot boot.img:
https://www.dropbox.com/s/nurzm8q3pqx2v4z/root_fire.zip?dl=0
Unzip the attachment and push the files directory contents to /data/loca/tmp using adb
Example: adb push Superuser.apk /data/local/tmp/
adb push su /data/local/tmp/
...
and then do the follwing in adb shell:
mkdir /system/app/SuperSU
chmod 0755 /system/app/SuperSU
chcon ubject_r:system_file:s0 /system/app/SuperSU
cp /data/local/tmp/Superuser.apk /system/app/SuperSU/SuperSU.apk
chmod 0644 /system/app/SuperSU/SuperSU.apk
chcon ubject_r:system_file:s0 /system/app/SuperSU/SuperSU.apk
mkdir /system/bin/.ext
chmod 0755 /system/bin/.ext
chcon ubject_r:system_file:s0 /system/bin/.ext
cp /data/local/tmp/su /system/xbin/su
chmod 0755 /system/xbin/su
chcon ubject_r:system_file:s0 /system/xbin/su
cp /data/local/tmp/su /system/bin/.ext/.su
chmod 0755 /system/bin/.ext/.su
chcon ubject_r:system_file:s0 /system/bin/.ext/.su
cp /data/local/tmp/su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
chcon ubject_r:system_file:s0 /system/xbin/daemonsu
cp /data/local/tmp/su /system/xbin/sugote
chmod 0755 /system/xbin/sugote
chcon ubject_r:zygote_exec:s0 /system/xbin/sugote
cp /data/local/tmp/supolicy /system/xbin/supolicy
chmod 0755 /system/xbin/supolicy
chcon ubject_r:system_file:s0 /system/xbin/supolicy
cp /data/local/tmp/libsupol.so /system/lib/libsupol.so
chmod 0644 /system/lib/libsupol.so
chcon ubject_r:system_file:s0 /system/lib/libsupol.so
cp /system/bin/sh /system/xbin/sugote-mksh
chmod 0755 /system/xbin/sugote-mksh
chcon ubject_r:system_file:s0 /system/xbin/sugote-mksh
cp /system/bin/app_process32 /system/bin/app_process32_original
chmod 0755 /system/bin/app_process32_original
chcon ubject_r:zygote_exec:s0 /system/bin/app_process32_original
cp /system/bin/app_process32 /system/bin/app_process_init
chmod 0755 /system/bin/app_process_init
chcon ubject_r:system_file:s0 /system/bin/app_process_init
rm /system/bin/app_process
rm /system/bin/app_process32
ln -s /system/xbin/daemonsu /system/bin/app_process
ln -s /system/xbin/daemonsu /system/bin/app_process32
touch /system/etc/.installed_su_daemon
chmod 0644 /system/etc/.installed_su_daemon
chcon ubject_r:system_file:s0 /system/etc/.installed_su_daemon
Once all is done you need to fastboot boot boot.img again to establish proper perms to the new files. Actually we can't change ownership of files to root from adb.
Run this command in adb shell:
/system/xbin/su --install
Then reboot and voila! you are root.
Sorry for text format by chrome doesn't allow me to format it as code...
Awesomeslayerg said:
Dosent work?
Click to expand...
Click to collapse
@csolanol said it does...
Proof [emoji12]
{
"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"
}
chown 0.0 /system/app/SuperSU gives me operation not premitted
Awesomeslayerg said:
chown 0.0 /system/app/SuperSU gives me operation not premitted
Click to expand...
Click to collapse
Yup, i edited the post to delete that line. That ownership change will be applied when you reboot from fastboot with the custom boot.img again. Note the end of the post.