I have a Verizon S4 I had it rooted and working fine with TWRP recovery installed but, my Google play store stopped working is why I am in this situation now. I did the No Wipe Factory Image posted in the Verizon S4 forum and once that was done I still saw the TWRP recovery still popping up and installed. So I proceed to try and restore the root access and now I keep running into this running mottochop...
Device found...
Pushing exploit...
cannot stat 'pwn' : No such file or directory
Unable to chmod /data/local/twp/pwn No such file or directory...
Pushing Root tools...
*leaving out this part because I don't want to type it*
Rooting phone...
/system/bin/sh: /data/local/twp/pwn: not found
Cleaning up...
rm failed for /data/local/twp/pwn, No such file or directory...
Exploit complete. Press enter to reboot and exit
Help!!!
killdawabbit said:
I have a Verizon S4 I had it rooted and working fine with TWRP recovery installed but, my Google play store stopped working is why I am in this situation now. I did the No Wipe Factory Image posted in the Verizon S4 forum and once that was done I still saw the TWRP recovery still popping up and installed. So I proceed to try and restore the root access and now I keep running into this running mottochop...
Device found...
Pushing exploit...
cannot stat 'pwn' : No such file or directory
Unable to chmod /data/local/twp/pwn No such file or directory...
Pushing Root tools...
*leaving out this part because I don't want to type it*
Rooting phone...
/system/bin/sh: /data/local/twp/pwn: not found
Cleaning up...
rm failed for /data/local/twp/pwn, No such file or directory...
Exploit complete. Press enter to reboot and exit
Help!!!
Click to expand...
Click to collapse
Looks like you are in store for a full system restore to the original stock image. You can try the recovery image from my signature to get rid of the TWRP recovery if you want. Just place the recovery file in the PDA box and start.
So, is that why I am getting that message when I am trying to root my phone again?
killdawabbit said:
So, is that why I am getting that message when I am trying to root my phone again?
Click to expand...
Click to collapse
It could be but not 100% sure. Each user is different. I would start there though and see if it works.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
killdawabbit said:
I have a Verizon S4 I had it rooted and working fine with TWRP recovery installed but, my Google play store stopped working is why I am in this situation now. I did the No Wipe Factory Image posted in the Verizon S4 forum and once that was done I still saw the TWRP recovery still popping up and installed. So I proceed to try and restore the root access and now I keep running into this running mottochop...
Device found...
Pushing exploit...
cannot stat 'pwn' : No such file or directory
Unable to chmod /data/local/twp/pwn No such file or directory...
Pushing Root tools...
*leaving out this part because I don't want to type it*
Rooting phone...
/system/bin/sh: /data/local/twp/pwn: not found
Cleaning up...
rm failed for /data/local/twp/pwn, No such file or directory...
Exploit complete. Press enter to reboot and exit
Help!!!
Click to expand...
Click to collapse
While I don't know the specifics of the exploit, it sounds like it was unable to push files to the device. Is your USB Debugging enabled prior to running the exploit?
Cilraaz said:
While I don't know the specifics of the exploit, it sounds like it was unable to push files to the device. Is your USB Debugging enabled prior to running the exploit?
Click to expand...
Click to collapse
Yes
killdawabbit said:
Yes
Click to expand...
Click to collapse
PM sent
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
DarkMenace said:
PM sent
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Click to expand...
Click to collapse
I am back to stock rom without TWRP. Thanks to the Dark Menace. Appreciate your help and I will not screw with my Google Play Store anymore after I root this time!
DarkMenace said:
PM sent
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Click to expand...
Click to collapse
Why would you PM the solution? Perhaps other people might have this same issue and need the solution as well.
killdawabbit said:
I am back to stock rom without TWRP. Thanks to the Dark Menace. Appreciate your help and I will not screw with my Google Play Store anymore after I root this time!
Click to expand...
Click to collapse
crikfromcincy said:
Why would you PM the solution? Perhaps other people might have this same issue and need the solution as well.
Click to expand...
Click to collapse
Sent
Related
I'm trying to install BusyBox on my HTC Droid DNA. I rooted the phone using the Jcase method.
I'm choosing the "normal install" method for Busybox and it keeps saying unsuccessful.
Question: Is it safe to try the "smart install" method? Has anyone else installed Busybox successfully?
What I'm trying to do: Just be able to do Linux stuff like edit files, etc. I'm told I need this software.
Thanks.
Joe
Ok, I think it worked. I booted into recovery, then used a .zip file that also contains SuperUser SU from a forum posting on rooting the DNA. I am almost 100% sure this was the file (I forgot to remember the link, but this was in my history):
http://www.mediafire.com/?es35lyioe8hxbxh
commandlinekid said:
I'm trying to install BusyBox on my HTC Droid DNA. I rooted the phone using the Jcase method.
I'm choosing the "normal install" method for Busybox and it keeps saying unsuccessful.
Question: Is it safe to try the "smart install" method? Has anyone else installed Busybox successfully?
What I'm trying to do: Just be able to do Linux stuff like edit files, etc. I'm told I need this software.
Thanks.
Joe
Click to expand...
Click to collapse
Did you get this officially fixed then?
Sent from my HTC DNA.
Technically, yes. It is installed.
wget isn't working, and I need to play with it, but yes, Busybox is on now.
BigRed35m said:
Did you get this officially fixed then?
Sent from my HTC DNA.
Click to expand...
Click to collapse
commandlinekid said:
Ok, I think it worked. I booted into recovery, then used a .zip file that also contains SuperUser SU from a forum posting on rooting the DNA. I am almost 100% sure this was the file (I forgot to remember the link, but this was in my history)
Click to expand...
Click to collapse
Do you still have the zip that you downloaded?
That link is broken, says that the file was deleted.
I'm running into the same problem, with either crashing my phone or saying that it failed.
You need a kernel that allows write to system.
D
.
Sent from somewhere irrelevant.
dsb9938 said:
You need a kernel that allows write to system.
Click to expand...
Click to collapse
I dunno... I kinda like the stock kernel.
Do I really need to change kernels in order to install BusyBox through recovery mode?
I'm sure there are other kernels that are a lot better than stock, but I'm not super adventurous. Just rooting was a lot, but I really wanted to have more functionality in Tasker and Titanium Backup. Once I get BusyBox I think I'm done for a while.
andyd273 said:
I dunno... I kinda like the stock kernel.
Do I really need to change kernels in order to install BusyBox through recovery mode?
I'm sure there are other kernels that are a lot better than stock, but I'm not super adventurous. Just rooting was a lot, but I really wanted to have more functionality in Tasker and Titanium Backup. Once I get BusyBox I think I'm done for a while.
Click to expand...
Click to collapse
There is stock with system write. You can do whatever you want in recovery, but installing it normally, or updating it, or updating su will not work.
D
.
Hi Everyone,
I have been completely puzzled by the rooting issue I am coming across with my new Galaxy S4. I am trying to root, on my mac with motochopper and my end result is a failure due to this message...
[*] Pushing root tools...
4927 KB/s (366952 bytes in 0.072s)
4786 KB/s (1867568 bytes in 0.381s)
5134 KB/s (1578585 bytes in 0.300s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS][*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.[*] Cleaning up...
Now I have looked through the directory to see if I can find this apk and I have no luck...i get permission denied.
I also had my GS3 rooted before I got the GS4 and I am wondering if it has something to do with that. I deleted all my titanium backups off of my sd card. Do I try factory resetting my phone (which I really don't want to do!) and possibly removing the sd card while rooting?? I need some advice, or solution to this.
Thanks!
Have you tried a clean odin flash and then rooting?
Sent from my SCH-I545 using Tapatalk 2
What I did, I'm assuming you'll have to do.... Install the trial version of vmware fusion, install a copy of Win XP (700mb download). Install the Samsung drivers that you can find in all the how-tos listed in these forums. Then flash your exploit in Odin 3.xx. I had a issue with the Su updating it's binaries, so while I was in the pre-release kernel I deleted and installed chainfires Su. Then rebooted and flashed the MDK kernel. Hope this helps.
Apps
Menu
Uninstall
Swipe until you see superuser icon
Tap it to remove
HIt back key.
Run script again.
syntrix said:
Apps
Menu
Uninstall
Swipe until you see superuser icon
Tap it to remove
HIt back key.
Run script again.
Click to expand...
Click to collapse
I have done this and still getting the failure.
I also don't want to run vmware on my mac, I had rooted my s3 on my mac with no issues whatsoever, so I want to do this the mac way, not windows.
I rooted running VM just fine. Im not sure there is a mac root out for it. Have you tried the all in one tool - root + Recovery
theidoctor said:
I rooted running VM just fine. Im not sure there is a mac root out for it. Have you tried the all in one tool - root + Recovery
Click to expand...
Click to collapse
I haven't tried that, never heard of the all in one tool.
There is a root out for the mac, several youtube videos on it and I am following it correctly just failing.
datboiro said:
What I did, I'm assuming you'll have to do.... Install the trial version of vmware fusion, install a copy of Win XP (700mb download). Install the Samsung drivers that you can find in all the how-tos listed in these forums. Then flash your exploit in Odin 3.xx. I had a issue with the Su updating it's binaries, so while I was in the pre-release kernel I deleted and installed chainfires Su. Then rebooted and flashed the MDK kernel. Hope this helps.
Click to expand...
Click to collapse
I am just going to try it on my pc that I have with Odin, I wanted to originally do it with the mac but lets see how this works.
Make sure when u odin the stock image you boot back into stock recovery and do a factory reset. then you will be back to square one.
datboiro said:
What I did, I'm assuming you'll have to do.... Install the trial version of vmware fusion, install a copy of Win XP (700mb download). Install the Samsung drivers that you can find in all the how-tos listed in these forums. Then flash your exploit in Odin 3.xx. I had a issue with the Su updating it's binaries, so while I was in the pre-release kernel I deleted and installed chainfires Su. Then rebooted and flashed the MDK kernel. Hope this helps.
Click to expand...
Click to collapse
Paulb787 said:
Make sure when u odin the stock image you boot back into stock recovery and do a factory reset. then you will be back to square one.
Click to expand...
Click to collapse
So I HAVE to do a factory reset? That sucks, not sure if that is worth it to me. I may hold off till the mac root is proven to work
popkurn611 said:
So I HAVE to do a factory reset? That sucks, not sure if that is worth it to me. I may hold off till the mac root is proven to work
Click to expand...
Click to collapse
I think he's saying to flash a 100% stock OEM image before even attempting anything else, NOT a factory reset.
Probably won't hurt, since you are using a mac n stuff. Just because there are youtube videos..... yeah...
There are 2 distinct choppers out there too! The one linked in xda is NOT the original one posted, and there could be other variants out there... pinterestering.
syntrix said:
I think he's saying to flash a 100% stock OEM image before even attempting anything else, NOT a factory reset.
Probably won't hurt, since you are using a mac n stuff. Just because there are youtube videos..... yeah...
There are 2 distinct choppers out there too! The one linked in xda is NOT the original one posted, and there could be other variants out there... pinterestering.
Click to expand...
Click to collapse
What do you mean when you say "flash" a 100% oem image? How is that different than a factory reset? Thanks
popkurn611 said:
What do you mean when you say "flash" a 100% oem image? How is that different than a factory reset? Thanks
Click to expand...
Click to collapse
What do you mean when you ask this and go against good advice as a precaution? You don't have to, but you are having uber weird issues already.
For all we know, it's related to "Caller Name ID" or "mac". Or it could be something uber simple. Hard to diag over the internet.
tl;dr/summary: you have root installed but not in your apps tray, causing issues on a mac.
syntrix said:
What do you mean when you ask this and go against good advice as a precaution? You don't have to, but you are having uber weird issues already.
For all we know, it's related to "Caller Name ID" or "mac". Or it could be something uber simple. Hard to diag over the internet.
tl;dr/summary: you have root installed but not in your apps tray, causing issues on a mac.
Click to expand...
Click to collapse
Well I successfully rooted via Odin!!! It doesnt work on the mac yet because I was using the stock kernel MDK and I needed to flash the MD2 Kernel on Odin....I put the stock kernel back on. Thanks everyone for the help.
Any idea why I randomly get the custom lock image which has the samsung logo above it when I reboot sometimes?
Hi Folks,
I recently inherited a Samsung Galaxy S II. (The previous owner upgraded to a Note 3 which soon has to be rooted too! )
To my knowledge this phone was already rooted to upgrade it to JellyBeans before this was officially available from Samsung.
To get to a clean start I went through the recovery mode (VolUp+Home+Power) and initiated a factory reset.
Thereafter I installed Titanium.apk from the SD-card, which tells me now that it can't gain access to the su command. Does this mean I 'unrooted' this phone wit the factory reset and I have to undergo the rooting procedure again?
BTW: After reading through the forum for a couple of days and following link after link, I still have the feeling I went in circles without really finding the basics to build my knowledge upon. Could someone please point me to some information on how to decode or interpret the 'cryptic' Product-, PDA-, Phone-, Modem-Codes (like XXLS7, XWLSD, DBTLS7, etc.)?
Cheers
BitCounter said:
Hi Folks,
I recently inherited a Samsung Galaxy S II. (The previous owner upgraded to a Note 3 which soon has to be rooted too! )
To my knowledge this phone was already rooted to upgrade it to JellyBeans before this was officially available from Samsung.
To get to a clean start I went through the recovery mode (VolUp+Home+Power) and initiated a factory reset.
Thereafter I installed Titanium.apk from the SD-card, which tells me now that it can't gain access to the su command. Does this mean I 'unrooted' this phone wit the factory reset and I have to undergo the rooting procedure again?
BTW: After reading through the forum for a couple of days and following link after link, I still have the feeling I went in circles without really finding the basics to build my knowledge upon. Could someone please point me to some information on how to decode or interpret the 'cryptic' Product-, PDA-, Phone-, Modem-Codes (like XXLS7, XWLSD, DBTLS7, etc.)?
Cheers
Click to expand...
Click to collapse
Su binary missing in system/xbin
Install super user from play store and update su binary.
Select normal method..not recovery
Sent from my GT-I9100 using Tapatalk 2
corruptionfreeindia said:
Su binary missing in system/xbin
Click to expand...
Click to collapse
OK
Install super user from play store and update su binary.
Select normal method..not recover
Click to expand...
Click to collapse
super user is installed.
How do I update the su binary and where do I have to choose the normal method?
Thanks!
super user just tells me that the su binary can't be found.
I now also installed SuperSU.
This app also provides the information about the missing su binary but additionally tells me that SuperSu can't install them and that this is a problem.
Any more ideas?
You could have fixed this 4 hrs ago if you'd flashed a custom kernel.
BitCounter said:
super user just tells me that the su binary can't be found.
I now also installed SuperSU.
This app also provides the information about the missing su binary but additionally tells me that SuperSu can't install them and that this is a problem.
Any more ideas?
Click to expand...
Click to collapse
Uninstall superuser app
Flash philz kernel. (If you are using stock rom)
It will install su binary as well as super user app.
Sent from my GT-I9100 using Tapatalk 2
corruptionfreeindia said:
Uninstall superuser app
Flash philz kernel. (If you are using stock rom)
It will install su binary as well as super user app.
Click to expand...
Click to collapse
Yes, this did the trick.
Thanks a lot.
I just purchased the Sprint variant of the HTC One Max and decided to unlock the bootloader to root it. I followed the instructions up to the point where I have to have to run the fastboot command in CMD. The example shows the CMD changing its directory to \Android. When I try to do this, I'm given the error: "The system cannot find the path specified." I tried just doing fastboot command, but came back with "fastboot is not recognized..."
Any help with this would be greatly appreciated.
P.S. Android SDK, Java Runtime, and HTC Sync are all installed and updated.
Thanks in advance!
bb2si said:
I just purchased the Sprint variant of the HTC One Max and decided to unlock the bootloader to root it. I followed the instructions up to the point where I have to have to run the fastboot command in CMD. The example shows the CMD changing its directory to \Android. When I try to do this, I'm given the error: "The system cannot find the path specified." I tried just doing fastboot command, but came back with "fastboot is not recognized..."
Any help with this would be greatly appreciated.
P.S. Android SDK, Java Runtime, and HTC Sync are all installed and updated.
Thanks in advance!
Click to expand...
Click to collapse
You need to run cmd prompt as admin and CD to wherever the platform tools folder is installed (part of the sdk)...
Sent from my Nexus 7 using Tapatalk
dottat said:
You need to run cmd prompt as admin and CD to wherever the platform tools folder is installed (part of the sdk)...
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for the quick reply.
This worked, but when I attempt to run the command for the fastboot I get an error saying "The program can't start because AdbWinApi.dll is missing from your computer."
Was this something that was supposed to be installed from one of the Android SDK installs?
bb2si said:
Thank you for the quick reply.
This worked, but when I attempt to run the command for the fastboot I get an error saying "The program can't start because AdbWinApi.dll is missing from your computer."
Was this something that was supposed to be installed from one of the Android SDK installs?
Click to expand...
Click to collapse
Sounds like part of it didn't install correctly. Rinse and repeat. Maybe something got hosed in your earlier attempts.
Sent from my HTC6600LVW using Tapatalk
dottat said:
Sounds like part of it didn't install correctly. Rinse and repeat. Maybe something got hosed in your earlier attempts.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
I happened to have found the file in a different folder. Should I just drag and drop it into the adt folder?
bb2si said:
I happened to have found the file in a different folder. Should I just drag and drop it into the adt folder?
Click to expand...
Click to collapse
Which folder and what else was in it ?
Sent from my HTC6600LVW using Tapatalk
dottat said:
Which folder and what else was in it ?
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
It was in the sdk\platform-tools folder.
Does the command line have to be directed to the folder containing the fastboot application file? Inside said platform-tools folder is the fastboot file as well as the ApbWinApi.dll file.
OH! I think I got it! I'll report back with final details...
Keep your fingers crossed!!!
bb2si said:
OH! I think I got it! I'll report back with final details...
Keep your fingers crossed!!!
Click to expand...
Click to collapse
Lol....didn't I say platform tools the first time ? Good luck man...
Btw if you get it working you just learned one of the most important prerequisites for android modding.
Sent from my HTC6600LVW using Tapatalk
dottat said:
Lol....didn't I say platform tools the first time ? Good luck man...
Btw if you get it working you just learned one of the most important prerequisites for android modding.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
Yep! Unlocked the bootloader successfully! Now, I'm trying to Root and the instructions I'm following are good, but I'm stuck again - It says to run CMD and use the command "adb devices." It comes back with nothing found, yet, according to the instructions my phone's serial number should be listed. I placed the Superuser.zip file in the phone's storage (per requisite) and tried to run the command with the phone on normally and again in the bootloader.
No luck... Suggestions?
Edit: USB Debugging wasn't on... Trying again...
bb2si said:
Yep! Unlocked the bootloader successfully! Now, I'm trying to Root and the instructions I'm following are good, but I'm stuck again - It says to run CMD and use the command "adb devices." It comes back with nothing found, yet, according to the instructions my phone's serial number should be listed. I placed the Superuser.zip file in the phone's storage (per requisite) and tried to run the command with the phone on normally and again in the bootloader.
No luck... Suggestions?
Edit: USB Debugging wasn't on... Trying again...
Click to expand...
Click to collapse
If you are unlocked you can simply download a custom recovery for your phone into your fastboot directory and boot your phone to boot loader (fastboot) mode. Flash your recovery using your appropriate fastboot command. Then boot to your new custom recovery and flash the su.zip you copied to the phone from recovery.
Sent from my Nexus 7 using Tapatalk
dottat said:
If you are unlocked you can simply download a custom recovery for your phone into your fastboot directory and boot your phone to boot loader (fastboot) mode. Flash your recovery using your appropriate fastboot command. Then boot to your new custom recovery and flash the su.zip you copied to the phone from recovery.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Everything went smoothly! I am now rooted and excited to get to work!
Thank you for your time and help!
bb2si said:
Everything went smoothly! I am now rooted and excited to get to work!
Thank you for your time and help!
Click to expand...
Click to collapse
Good deal. You may want to investigate s-off'ing that thing too while you still can. Just make sure you download the right version for your phone and run as admin
http://forum.xda-developers.com/showthread.php?t=2525375
Sent from my Nexus 7 using Tapatalk
dottat said:
Good deal. You may want to investigate s-off'ing that thing too while you still can. Just make sure you download the right version for your phone and run as admin
http://forum.xda-developers.com/showthread.php?t=2525375
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Would that solve my next problem? (I'm such a sputz)
I'm rooted, but I can't uninstall anything with Titanium Backup. The last time this happened on my S3 I was told to install SuperSU and install updated binaries. I did that, but when I reboot and go back into SuoerSU it acymts as if it never happened. Apps I uninstalled are still present, too.
Would S-offing solve this?
Edit: Also, I get an annoying pop-up when I start the phone up that says vDN client has failed. Even before I unlocked and rooted. Any way to stop this?
Sent from my HTC0P3P7 using XDA Premium 4 mobile app
bb2si said:
Would that solve my next problem? (I'm such a sputz)
I'm rooted, but I can't uninstall anything with Titanium Backup. The last time this happened on my S3 I was told to install SuperSU and install updated binaries. I did that, but when I reboot and go back into SuoerSU it acymts as if it never happened. Apps I uninstalled are still present, too.
Would S-offing solve this?
Edit: Also, I get an annoying pop-up when I start the phone up that says vDN client has failed. Even before I unlocked and rooted. Any way to stop this?
Sent from my HTC0P3P7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You need to flash an insecure boot.img to disable system write protection. S-off would allow you to recover your phone using both signed and unsigned ruu. The advantage of that is when you hose your phone and there's not a current ruu for the version your phone is on - s-on user would be screwed because you cannot downgrade. Just one of many reasons.
The fc problem I'm not sure. If you aren't using that app you can disable it in the stock app manager. Same goes for stuff you might normally remove with tibu. Be warned too that future otas will likely fail if system apps are missing.
Sent from my HTC6600LVW using Tapatalk
bb2si said:
Would that solve my next problem? (I'm such a sputz)
I'm rooted, but I can't uninstall anything with Titanium Backup. The last time this happened on my S3 I was told to install SuperSU and install updated binaries. I did that, but when I reboot and go back into SuoerSU it acymts as if it never happened. Apps I uninstalled are still present, too.
Would S-offing solve this?
Edit: Also, I get an annoying pop-up when I start the phone up that says vDN client has failed. Even before I unlocked and rooted. Any way to stop this?
Sent from my HTC0P3P7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i have noticed someelse posting about the vDN client failing.. it your providers bloatware if i remember correctly and i think @dottat has a good suggestion! disabled it
So I somehow lost root privileges... After S-offing, I was asked to update the SU binary through the Superuser app (not SuperSU) and I did so. When the install finished, I went into Titanium Backup and was told I'm not rooted.
Went back into Superuser and it didn't prompt for an update, but SuperSU did. Attempted and failed.
Went into recovery and tried to recover root - no luck.
HALP!
bb2si said:
So I somehow lost root privileges... After S-offing, I was asked to update the SU binary through the Superuser app (not SuperSU) and I did so. When the install finished, I went into Titanium Backup and was told I'm not rooted.
Went back into Superuser and it didn't prompt for an update, but SuperSU did. Attempted and failed.
Went into recovery and tried to recover root - no luck.
HALP!
Click to expand...
Click to collapse
Easy...Download this and flash in recovery
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Make sure you aren't running both supersu and superuser. I prefer supersu
Sent from my Nexus 7 using Tapatalk
Huzzah! Thanks again! Hopefully I can actually freeze/remove system apps without them being brought back after a reboot. Also, in the picture provided, what is that icon in the notification bar just right of the GPS icon? And, is there any way to hide some of the icons?
Sent from my HTC0P3P7 using XDA Premium 4 mobile app
Don't use Superuser by ChainsDD anymore.. Personally I would love to continue to use it but he is basically no longer supporting his Superuser app and binary and hasn't updated it in a very long time. SuperSU by Chainfire is constantly being updated therefore made to work with all current versions of Android.. Quite frankly it's all the same basically anyways I just liked the skull and cross bone look lol... Chainfire is a monster as well and has a ton of root related apps and cool things going on. ChainsDD I guess passed the torch on to Chainfire???
bb2si said:
Huzzah! Thanks again! Hopefully I can actually freeze/remove system apps without them being brought back after a reboot. Also, in the picture provided, what is that icon in the notification bar just right of the GPS icon? And, is there any way to hide some of the icons?
Sent from my HTC0P3P7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
---------- Post added at 07:54 PM ---------- Previous post was at 07:53 PM ----------
Also I have no idea what that icon is next to the GPS icon.. You must be on Sprint, I'm on Verizon and I don't think I've seen that icon before..
I have a galaxy s4 running android 4.2.2 , its model # sch i545 and its build vruame7 .http://forum.xda-developers.com/showthread.php?t=2380325 I am following the directions here word by word ,,,, Devoloper options is enabled, card formatted to exfat and in the terminal emulater when I change directories and try to run the 2nd command I am getting this error
Try to find address in memory....
Attempt fb_mem exploit...
Failed to open /dev/graphics/fb0 due to permission denied
You need to manage to get remap_pfn_range addresses
failed to get prepare_kernel_cred addresses
failed to get commit_creds addresses
failed to get ptmx_fops addresses
() device is not supported
failed to setup variables
and I dont know why its where it says device detected () shouldnt it say the device?
I searched the forums and saw someone having problems with it on an AT$T phone.....THanks in advance guys
vafangool said:
I have a galaxy s4 running android 4.2.2 , its model # sch i545 and its build vruame7 .http://forum.xda-developers.com/showthread.php?t=2380325 I am following the directions here word by word ,,,, Devoloper options is enabled, card formatted to exfat and in the terminal emulater when I change directories and try to run the 2nd command I am getting this error
Try to find address in memory....
Attempt fb_mem exploit...
Failed to open /dev/graphics/fb0 due to permission denied
You need to manage to get remap_pfn_range addresses
failed to get prepare_kernel_cred addresses
failed to get commit_creds addresses
failed to get ptmx_fops addresses
() device is not supported
failed to setup variables
and I dont know why its where it says device detected () shouldnt it say the device?
I searched the forums and saw someone having problems with it on an AT$T phone.....THanks in advance guys
Click to expand...
Click to collapse
I didn't think the me7 exploit was supposed to ran with terminal emulator. Have you tried safe root another windows tool?
Nvidia Shield Root and More Doing a little bit of reading goes a long way.
hexitnow said:
I didn't think the me7 exploit was supposed to ran with terminal emulator. Have you tried safe root another windows tool?
Nvidia Shield Root and More Doing a little bit of reading goes a long way.
Click to expand...
Click to collapse
I havent tried anything else....according to the thread it was supposed to be for the me7 build...I am kind of new to all this..
vafangool said:
I havent tried anything else....according to the thread it was supposed to be for the me7 build...I am kind of new to all this..
Click to expand...
Click to collapse
Use saferoot. It will root all versions of the sch-1545 (Verizon Galaxy S4).
Sent from my SCH-I545 using XDA Premium 4 mobile app
vafangool said:
I have a galaxy s4 running android 4.2.2 , its model # sch i545 and its build vruame7 .http://forum.xda-developers.com/showthread.php?t=2380325 I am following the directions here word by word ,,,, Devoloper options is enabled, card formatted to exfat and in the terminal emulater when I change directories and try to run the 2nd command I am getting this error
Try to find address in memory....
Attempt fb_mem exploit...
Failed to open /dev/graphics/fb0 due to permission denied
You need to manage to get remap_pfn_range addresses
failed to get prepare_kernel_cred addresses
failed to get commit_creds addresses
failed to get ptmx_fops addresses
() device is not supported
failed to setup variables
and I dont know why its where it says device detected () shouldnt it say the device?
I searched the forums and saw someone having problems with it on an AT$T phone.....THanks in advance guys
Click to expand...
Click to collapse
Further info on what @Surge1223 said:
Go to this thread and follow the directions in the first post.
Surge1223 said:
Use saferoot. It will root all versions of the sch-1545 (Verizon Galaxy S4).
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok..I will try that one...I also have a note 2, but the software is 4.3 .. I know the bootloader is locked on this one. But if I can use saferoot to root it and than load safestrap to load custom roms on it? From what I read you cant put safestrap on the note 2 with 4.3 but i read somewhere that you can put safestrap on here since I still have the 4.2.2 ....Thank you for the help so far..
vafangool said:
Ok..I will try that one...I also have a note 2, but the software is 4.3 .. I know the bootloader is locked on this one. But if I can use saferoot to root it and than load safestrap to load custom roms on it? From what I read you cant put safestrap on the note 2 with 4.3 but i read somewhere that you can put safestrap on here since I still have the 4.2.2 ....Thank you for the help so far..
Click to expand...
Click to collapse
You have got to be pretty careful, since there's lots of variants of these models. For example, there's at least 6 incompatible models of the Samsung Galaxy S4 (AT&T, Sprint, T-Mobile, Verizon, International (a couple of models as far as I can tell) the "L" variant, etc.
Following directions for a "Galaxy S4" without knowing if it's the same variant as yours can lead to bricks.
People have successfully used Saferoot to root Note 2 with the MK7 build. Then you'll have to research if Safestrap works - it's likely if you're running 4.3, but I have no idea. Do the research before you flash.
Surge1223 said:
Use saferoot. It will root all versions of the sch-1545 (Verizon Galaxy S4).
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I used saferoot but I am not sure if it worked all the way..towards the end my phone didnt reboot when it said it would..I dont know if that busybox was installed I dont see it but I have superuser installed.. I also dont have that padlock unlock when I restart the phone....
vafangool said:
I used saferoot but I am not sure if it worked all the way..towards the end my phone didnt reboot when it said it would..I dont know if that busybox was installed I dont see it but I have superuser installed, My device status says official...is that where its suppsed to say custom?
Click to expand...
Click to collapse
What kind of phone do you have? I assume an i545 given that this is the Verizon GS4 forum, but it's worth asking.
If the phone did not reboot, then it's probably rooted but no busybox installed, but that's OK. Just install it from the play store.
Or, you can just re-root, and provide a bit more detail on what happened.
Yeah like @k1mu just said post more info, specifically what the output of the adb script says. Also if you dont get a SuperSu prompt after the script finishes. Then try typing su into terminal or adb shell and tell us what it says
Sent from my SCH-I545 using XDA Premium 4 mobile app
k1mu said:
What kind of phone do you have? I assume an i545 given that this is the Verizon GS4 forum, but it's worth asking.
If the phone did not reboot, then it's probably rooted but no busybox installed, but that's OK. Just install it from the play store.
Or, you can just re-root, and provide a bit more detail on what happened.
Click to expand...
Click to collapse
I may try and reroot it and see what happens...its hard to explain but it was at the part where it was telling me my phone was going to reboot and to unlock it and press any key when it does..I waited and the phone didnt reboot
... I just did it again and it looked like it worked...I kept seeing the popup that ADB shell has been granted superuser permissions....it said all done and the command prompt closed..
Surge1223 said:
Yeah like @k1mu just said post more info, specifically what the output of the adb script says. Also if you dont get a SuperSu prompt after the script finishes. Then try typing su into terminal or adb shell and tell us what it says
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I typed SU into terminal emulater and a window popped up asking for super user permissions and I granted them and Im at the [email protected] with a # sign...so Im assuming the # sign at the prompt also means that I gained root...
I did make sure I was using the right software..I was aware of the build # and I made sure I was trying the right stuff..From what I read safestrap should work using the 4.2.2 android version..with the ME7 build that I have...
I have been all over this site the last 3 days since I got into this when I should be studying for my networking certifications...lol...Thanks for all the help so far..I really appreciate it guys..
vafangool said:
I typed SU into terminal emulater and a window popped up asking for super user permissions and I granted them and Im at the [email protected] with a # sign...so Im assuming the # sign at the prompt also means that I gained root...
I did make sure I was using the right software..I was aware of the build # and I made sure I was trying the right stuff..From what I read safestrap should work using the 4.2.2 android version..with the ME7 build that I have...
I have been all over this site the last 3 days since I got into this when I should be studying for my networking certifications...lol...Thanks for all the help so far..I really appreciate it guys..
Click to expand...
Click to collapse
Congratulations, you have root.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Congratulations, you have root.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Awesome..Thanks alot for all the help...