I own M8 Telstra AU version.
I tried to get S-off but it didn't seem to work. So I looked for some information and found a bypass PIE and I flashed it.
Since then, whenever I tried to get S-off by firewater the terminal in my MAC shows
JungSoos-MacBook-Air:download jungsoo$ ./adb shell
/system/bin/sh: j_init: setpgid failed: Invalid argument
/system/bin/sh: warning: won't have full job control
And also I can't open SuperSu app anymore and remove it neither.
Whenever I tried to install a custom rom, TWRP just restarts... What should I do?
Can't even find RUU for Telstra Lollipop 5.0.1 version.... I'm in deep **** now:crying:
Bypass PIE ? Not sure what you try to so exactly but you are way off and missing some critical info. If you browsed here and on "therootninja" website you would have seen that firewater will not work and never will again !
SUNSHINE is the only option to s-off the phone and it cost ya 25$.
Don't start the discussion about how much or not that is. It is what it is and won't change, discussions about that have been on endlessly already.
Related
I attempted to root my friend's G2 first using Visionary+ R14 and temp root would work (the SU.apk is in the app drawer), so I attempted the perma-root and as soon as I granted it root access it would immediately reboot. Once I rebooted SU was still in the app drawer but rom manager kept saying the SU apk wasnt found in /system/bin or /system/xbin. I looked for it manually and searched for it but it couldnt be found anywhere, yet it was in the app drawer after a reboot.
I tried it a few more times and couldnt get it to work, I booted into the bootloader and saw that S-on wasn't off. After feeling competent enough I decided to push the hboot.img and the wpthis-OTA.ko to the sdcard (since I didnt have adb handy) and then copied them both to /data/local via the terminal. When I tried to insert the kernel module it gave me the expected error so I proceeded to flash the new hboot and that was also successful. I ran visionary again (guide doesnt say temp or permanent method, so i did temp), and once it was finished I typed sync into the terminal, waited a minute and rebooted.
Once android was fully loaded up again, I loaded up rom manager and it still complained that it couldnt find su.apk, I searched for it and it still wasnt there, yet it was still in the app drawer. I rebooted into the bootloader and saw that the protection was finally S-OFF, yet root access didnt seem to be (fully) available.
It also mentioned at some point that my su.apk was out of date and it downloaded the most up to date one for me but I had no way to flash it.
Whats wrong here?
This should either be in an existing thread about the rooting methods you're talking about, or in one of the other forums, such as Q&A
Hi all,
I have had my htc desire z for about two weeks now, But since i have had my phone i've been having a few problems.
I had rooted my phone using visionary +. And all was going well untill i was trying to install setcpu to overclock my cpu. After installation my phone rebooted and now every thing that i need root access for is showing up as not accessable.
Busybox installer error message:
Your phone is roote
Busybox not found
The application failed, either because your device is not nand unlocked or we were unable to remount.
Rom manager error message:
An error occured while attempting to run priviledged commands!
Is it possible(if yes, how) to unroot and flash my desire back to stock settings including the permissions back to stock.
If not how can i root my phone so i can use all of the fuctions
Regarding the phone info the spaces are actually . but the system will not allow me to enter these as of yet
Thanks in advance
All the best
Gaz
I forgot to mension in the last post that i have expiriance with mobile phone's and flashing so i'm not affraid to tackle big complicated ways of undoing the process.
It sounds like maybe you only had temp root.
Did you also do gfree? I did Visionary and gfree, and perm rooted just fine.
However, many on here believe the rage + gfree method is safer, as Visionary has been known to create some semi-bricks. I don't THINK there is any harm in doing rage + gfree at this point, but others on here can probably enlighten.
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I tried using root checker to find the issue. It came back with an error message telling me the SU binary was not found in the correct path. I used terminal emulator to try to locate the file but with no success. Any ideas on how to find and move the binary su???
What's displayed on your screen after reboot in recovery?
As in; remove battery, insert battery, hold volume down and power button.
It will not reboot in to root. It runs Visionary and nothing happens.
And when i try to open an app that need root access it fails because it cannot gain permission from superuser. At this point i have tried to unistall all apps that had anything to do with rooting my phone but still no succes. I need to find the stock SU Binary
okay so im rooting my brothers g2, and im coming across alot of really odd issues ive never encountered before with rooting. i've followed all the steps for temp and perm root for this phone, but it still doesnt give me su. i have superuser on the phone from pushing it via adb, but it doesnt work. the phone in hboot says its the eng build with s-off. but again i dont get any su in cmd so i cant do anything. superuser doesnt work so i cant install clockwork via rom manage, and su doesnt work in cmd so i cant manually push the image. any idea or tips would be nice because im so lost. i have rooted several phones before and none had this issue.
twilightvanquisher said:
okay so im rooting my brothers g2, and im coming across alot of really odd issues ive never encountered before with rooting. i've followed all the steps for temp and perm root for this phone, but it still doesnt give me su. i have superuser on the phone from pushing it via adb, but it doesnt work. the phone in hboot says its the eng build with s-off. but again i dont get any su in cmd so i cant do anything. superuser doesnt work so i cant install clockwork via rom manage, and su doesnt work in cmd so i cant manually push the image. any idea or tips would be nice because im so lost. i have rooted several phones before and none had this issue.
Click to expand...
Click to collapse
Have you tried just downloading it from the Market? http://market.android.com/details?id=com.noshufou.android.su
Sent from my T-Mobile G2 using XDA App
yeah and i dont see how that makes it any different than when its put on during the root process. the problem seems to be that it doesnt wanna let me write things to the phone.i get errors like "cannot create /system/bin/su': input/output error" "unable to chmod /system/bin/su: no such file or directory" when i push the /data/local/tmp/root_psn.
just cuz this blows my mind...
gfree verify_cid returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
thats how my phone reads for the gfree verify, im fully s-offed, but i cant do su from adb shell it says
su
su: not found
twilightvanquisher said:
yeah and i dont see how that makes it any different than when its put on during the root process. the problem seems to be that it doesnt wanna let me write things to the phone.i get errors like "cannot create /system/bin/su': input/output error" "unable to chmod /system/bin/su: no such file or directory" when i push the /data/local/tmp/root_psn.
Click to expand...
Click to collapse
Unless you set up a system path to adb, you need to have both su and adb in the same folder to be able to push it, sounds like what your problem is
Sent from my T-Mobile G2 using XDA App
everything is in the same folder in androidsdk. but i got it working, just in a much different fashion. since i already had eng build and s-off but no su functioning i decided to format the phone which still had superuser but i installed visionary gained temp access to root and flashed cwr from rom manager and installed cm7, and now its fully functioning as perm root and s-off.
Sorry if the answer is somewhere in here but I have been looking for over a day.
This is what I have done:
I have a stock Verizon HTC One
Installed weak sauce gained root access.
Installed Firewater S-Off and HBoot worked Beautiful work thank you after hours of research. - For a Noob it went smooth.
Also flashed PhilZ Touch Advance and when I try to reboot it says: Root access is missing or broken.
Ran Root Checker: You have root access!
Super User Application Status:
SuperSU application - version 1.93 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 113036 2014-03-30 12:15 su
Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
I'm sure the answer is in here I just dont want to F it up and my eyes are crossed from looking for answer.
Thanks Again.
How about just flashing a rooted ROM in your recovery and seeing if it's all good?
That easy?
orangekid said:
How about just flashing a rooted ROM in your recovery and seeing if it's all good?
Click to expand...
Click to collapse
Ok I will try that. Do you think the error is because I installed supersu incorrectly, or wrong method. I believe I dropped and dragged it to my download file then opened it with my file browser and installed. As long as that wont be an issue I will give it a shot. Thank You for responding to my noob question.
habatchaNow said:
Ok I will try that. Do you think the error is because I installed supersu incorrectly, or wrong method. I believe I dropped and dragged it to my download file then opened it with my file browser and installed. As long as that wont be an issue I will give it a shot. Thank You for responding to my noob question.
Click to expand...
Click to collapse
It could be a number of things, but you were going to flash a custom ROM at some point anyways, right?
@PonsAsinorem might be able to help on this.
ROM .... Check
orangekid said:
It could be a number of things, but you were going to flash a custom ROM at some point anyways, right?
Click to expand...
Click to collapse
I took your advice and flashed the NuSenceSix. It went off without a hitch, holding breath eh entire time. Thank you for the push.
I went back to the firewater threads and one thing I didn't do was remove weaksause. Is that something I need to do if I want the root to be permanent? I don't need to go to the android development and go though that process emailing system info or whatever its called do I?
Also I was about to read up on radios and kernals for this ROM as well as try and figure out why I am getting that message in Rootchecker.
Thanks Again for your help.
Please
synisterwolf said:
@PonsAsinorem might be able to help on this.
Click to expand...
Click to collapse
That would be awesome. Any suggestions would be greatly appreciated. As I was telling the Room Moderator I flashed the NuSense6 and it went off without a hitch. however it is Still showing the same messages with rootchecker.
Thank You
synisterwolf said:
@PonsAsinorem might be able to help on this.
Click to expand...
Click to collapse
Sorry for the late response; was at work.
habatchaNow said:
That would be awesome. Any suggestions would be greatly appreciated. As I was telling the Room Moderator I flashed the NuSense6 and it went off without a hitch. however it is Still showing the same messages with rootchecker.
Click to expand...
Click to collapse
If you're S-OFF, you're golden. Most anything after that is going to be a ROM issue. It's been a minute since I ran that ROM, but the early batches had issues with su being configured improperly. The easiest way to fix this would be to flash the update SuperSU zip in recovery.
I miss read the OP-
I thought he was saying that Philz recovery was showing Super User not installed on reboot when the rom is Rooted.
OP-
As for weaksauce, once you have s-off you will no long need the app. you can root any rom by flashing SU.zip if you have an S-off device running a custom recovery.
habatchaNow, what version of PhilZ are you running? There was a bug that misdetecting CM, but that's been fixed, and I don't think this rom ever had the false positive, because root actually wasn't configured properly at the time.
Custom Recovery Version
PonsAsinorem said:
habatchaNow, what version of PhilZ are you running? There was a bug that misdetecting CM, but that's been fixed, and I don't think this rom ever had the false positive, because root actually wasn't configured properly at the time.
Click to expand...
Click to collapse
Let me see, it looks like my custom recovery is PhilZ 6.40.4 Cyogen Mod V6.0.4.8. I think the problem started when I installed and ran super su. I side loaded it( that's moving it onto my device via explorer right?) Do you guys recommend another ROM for my phone? I like the NuSence it just seems like a minor upgrade to the stock ROM. I don't know if this matters but when I open my files on the phone the "root" folder and "sbin" folder are both empty.
One of my challenges is that I don't even know what I don't know so, I really appreciate the help. If you ever need help or advice with health/life/investments I'm your guy.
If you like that ROM, then stick with it. I try not to steer people away from any ROM. To fix your su problem, try flashing this from recovery.
http://download.chainfire.eu/supersu
Just trying to get s off on international m8. Phone is unlocked and have root access with super su. Have all the steps for getting a off. But when trying to push firewater for those who did it already the second line of command. It says cannot stat firewater. Now the firewater file is on the platform tools folder where it should be.
I even copied the file to the phone and to the data/local/temp folder as well but still no luck. Driving me mental
Only other thing I can ser is people saying delete the .bin extension at the end of the firewater file but I can't see any on the phone or on the pc
Either in doing something stupid or just don't bother with it. But I want it to unlock SIM
So manage to get a but if Lee way. Switched computers today and eventually got it working but now I cannot get root access she. I type adb shell. Everything looks right in adb but supersu does not give me an option. To grant root access for adb shell
snwman said:
So manage to get a but if Lee way. Switched computers today and eventually got it working but now I cannot get root access she. I type adb shell. Everything looks right in adb but supersu does not give me an option. To grant root access for adb shell
Click to expand...
Click to collapse
Try ignoring this and finish typing all the commands, then wait for a while and you should eventually be prompted. This was my experience at least.
Also, unless you have already done so, do not install the last OTA update until you are done, it has been reported to block firewater.
Black Antitoon said:
last OTA update until you are done, it has been reported to block firewater.
Click to expand...
Click to collapse
1.57 OTA does block firewater on my phone. Wish I had read this first
Are you sure this is the problem? Firewater doesn't work on all phones, regarding of OTAs. Does it give you the 'whelp' message, does it exit abruptly or what else? In the first case it shouldn't depend on the OTA.
Whelp here. Tried a couple dozen times, and with a file transfer too. Never got to a bottle.
Sent from my HTC One_M8 using Tapatalk