Greetings! My apologies if I've posted in the inappropriate forum. The 3rd gen Fire 7" HD doesn't seem to have a home as yet.
I have rooted and had a working ES Explorer app. I noticed there was an upgrade to what I was using and figured I'd install it. That was a mistake. The newer version (which I was attempting to install directly from the Amazon store) didn't install properly because of the presence of the older. The older no longer worked so I removed (or thought I did) the app. My thought...let's reinstall my old one the way I did before, remove it properly, then try to reinstall the newer version.
I had used Android Injector to get the original on. I try it now and get the following error:
Command issued:C:\Program Files\Android Injector\adb.exe install C:\Installs\Kindle\ES_FIL~1.APK
pkg: /data/local/tmp/ES_FIL~1.APK
Failure [INSTALL_FAILED_ALREADY_EXISTS]
2330 KB/s (2833758 bytes in 1.187s)
I figure fair enough. I'll just use ADB shell and remove it. But there is nothing to remove!
[email protected]:/ # cd data/local/tmp
cd data/local/tmp
[email protected]:/data/local/tmp # ls -l
ls -l
-rwxr-xr-x shell shell 89968 2013-11-26 19:35 exploit
-rwxr-xr-x shell shell 188 2013-11-25 00:35 rootme.sh
-rw-rw-rw- shell shell 104564 2013-11-25 00:33 su
[email protected]:/data/local/tmp #
Any ideas on what I can do? It doesn't seem possible remove a file that doesn't seem to exist. I haven't done much to the system as yet. I've thought about restoring to factory defaults. However, my concern with that is that I've renamed /system/etc/security/otacerts.zip to /system/etc/security/otacerts.zip.old (effort to prevent OTA) and I've disabled the ads by renaming /system/app/dtcp_apk-release-signed_62320010.apk to /system/app/dtcp_apk-release-signed_62320010.apk.old --- if I try to restore to defaults, what are the chances I brick it due to those renamed files?
Or, I could rename them back if someone would be kind enough to offer me the exact command(s) to use in ADB shell so that I can get those files back to a state of being read/write instead of read only as they seem to be now? I'm comfortable with cmd line type stuff. I just don't have a 100% grasp on the exact syntax for some things -- this being one of them.
Any assistance much appreciated!
Files/Directories not hidden
It occurred to me as I thought about this today some more that maybe the file was hidden. So I check:
[email protected]:/data/local/tmp # ls -la
ls -la
-rwxr-xr-x shell shell 89968 2013-11-26 19:35 exploit
-rwxr-xr-x shell shell 188 2013-11-25 00:35 rootme.sh
-rw-rw-rw- shell shell 104564 2013-11-25 00:33 su
[email protected]:/data/local/tmp #
Ok...kills that idea. I don't understand why I'm being told a file exists that I can't see in any way.
DigitalVortex said:
It occurred to me as I thought about this today some more that maybe the file was hidden. So I check:
[email protected]:/data/local/tmp # ls -la
ls -la
-rwxr-xr-x shell shell 89968 2013-11-26 19:35 exploit
-rwxr-xr-x shell shell 188 2013-11-25 00:35 rootme.sh
-rw-rw-rw- shell shell 104564 2013-11-25 00:33 su
[email protected]:/data/local/tmp #
Ok...kills that idea. I don't understand why I'm being told a file exists that I can't see in any way.
Click to expand...
Click to collapse
My 2 cents. Did you check and see if it exists in the /data/app dir where it is installed to by default. check there or /system/app if you installed as root.
Sent from my KFTHWI using xda app-developers app
cdub50 said:
My 2 cents. Did you check and see if it exists in the /data/app dir where it is installed to by default. check there or /system/app if you installed as root.
Click to expand...
Click to collapse
Suggestion appreciated. I checked both places and nothing found that remotely resembles es explorer. I used the -la switch as well to make sure I wasn't missing anything as a hidden file.
I'm fairly stumped at this point and really don't mind setting it back to defaults. My only concern in doing that is making sure I don't brick it given the file renames I mentioned in the original post. I remain open to thoughts/ideas/opinions.
One other thing to try is open the amazon app store and check the cloud storage to see if you can restore the app from there.
Sent from my KFTHWI using xda app-developers app
I tried that in the early stages of recognizing the issue. And I'm wondering if my renaming the file to /system/etc/security/otacerts.zip.old is messing things up in that realm. The newer version of ES Explorer had failed to complete its install and showed on my screen with a little red '!" in the lower right of the icon. I tried to reinstall from the cloud and it wouldn't complete. I then proceeded to remove it from the cloud. The fun part after that is that the app's icon still shows on the Kindle with that "!" on it. I tried to go back into the app store to re-download. It tells me I can't and refers me back to my cloud storage.
Alright, thinking "out loud" here. I suppose if that file is causing this commotion, if I rename it back, there's the potential of everything returning to normal. To rename it back, I can only do that through the adb shell right now. The file perms are read only and if I try to chmod it, I can't because of the dir perms (I think). Would I want to do something like chmod -R 777 system/etc/security/otacerts.zip.old rename and then same command with 644 to set it back? Directories are usually 755 from my recollection. That's why I'm just a little confused on what my syntax should be to rename that file from the command line. I know once I have write privilege I can just mv system/etc/security/otacerts.zip.old system/etc/security/otacerts.zip.
DigitalVortex said:
I tried that in the early stages of recognizing the issue. And I'm wondering if my renaming the file to /system/etc/security/otacerts.zip.old is messing things up in that realm. The newer version of ES Explorer had failed to complete its install and showed on my screen with a little red '!" in the lower right of the icon. I tried to reinstall from the cloud and it wouldn't complete. I then proceeded to remove it from the cloud. The fun part after that is that the app's icon still shows on the Kindle with that "!" on it. I tried to go back into the app store to re-download. It tells me I can't and refers me back to my cloud storage.
Alright, thinking "out loud" here. I suppose if that file is causing this commotion, if I rename it back, there's the potential of everything returning to normal. To rename it back, I can only do that through the adb shell right now. The file perms are read only and if I try to chmod it, I can't because of the dir perms (I think). Would I want to do something like chmod -R 777 system/etc/security/otacerts.zip.old rename and then same command with 644 to set it back? Directories are usually 755 from my recollection. That's why I'm just a little confused on what my syntax should be to rename that file from the command line. I know once I have write privilege I can just mv system/etc/security/otacerts.zip.old system/etc/security/otacerts.zip.
Click to expand...
Click to collapse
I don't think the cert is your issue as I had restored from a backup using safestrap and I had not backed up a game I had downloaded so I restored it from the cloud and I had moved otacert to another directory. Why not just try a different file manager?
Sent from my KFTHWI using xda app-developers app
[RESOLVED] Help: remove file that "doesn't exist" (KFSOWI)
That was a good idea. Trying something else doesn't mean I need to keep that...just a means to an end. So I did. I used that and renamed items to original. Rebooted. The weird stuff still existed - the "!" on the ES Explorer. I was just about to go for the restore when I noticed SYNC at the top of the list. I had never thought to try that. I sync'd the device. The "!" disappeared. I could download ES Explorer 3 from the cloud and this time it installed.
Lesson learned.
DigitalVortex said:
That was a good idea. Trying something else doesn't mean I need to keep that...just a means to an end. So I did. I used that and renamed items to original. Rebooted. The weird stuff still existed - the "!" on the ES Explorer. I was just about to go for the restore when I noticed SYNC at the top of the list. I had never thought to try that. I sync'd the device. The "!" disappeared. I could download ES Explorer 3 from the cloud and this time it installed.
Lesson learned.
Click to expand...
Click to collapse
Glad it's all working. I highly recommend using safestrap to do a backup in case you ever mess up you can restore. I have tested backup and restore and both work with safestrap. I had installed a .zip via twrp and was wedged and did a restore and everything is back to normal.
Sent from my KFTHWI using xda app-developers app
cdub50 said:
I highly recommend using safestrap to do a backup in case you ever mess up you can restore. I have tested backup and restore and both work with safestrap.
Click to expand...
Click to collapse
You're successfully using safestrap on the 3rd Gen Kindle Fire HD 7 then? Just making sure because the more stuff I read in here, the more differences I find between mine and my kids' 2nd Gen HD 7's. I found another example tonight....I have Lookout on their Kindles and it won't run on mine. Anyway, thanks again for the help!
DigitalVortex said:
You're successfully using safestrap on the 3rd Gen Kindle Fire HD 7 then? Just making sure because the more stuff I read in here, the more differences I find between mine and my kids' 2nd Gen HD 7's. I found another example tonight....I have Lookout on their Kindles and it won't run on mine. Anyway, thanks again for the help!
Click to expand...
Click to collapse
Using SafeStrap on Kindle Fire 7" HDX (Thor). Just waiting on a ROM to flash so I get rid of Fire OS not a big fan and I would rather have the google app store amazon app store just doesnt have much selection IMO.
Related
I'm running TaintedTenzo2.1 with A2SD on my Eris.
I found a file named *.apk in /data/app-private and have no clue what it is. I cannot copy and paste to SDCARD with root explorer, nor can I pull it with ADB. Any ideas?
Code:
# cd data/app-private
cd data/app-private
# ls
ls
*.apk
# ls -l
ls -l
-rw-rw-rw- root root 1538413 2010-08-10 19:54 *.apk
#
Why don't you PM the dev and ask
Sent from my Eris using XDA App
Do you think it is a function of that particular ROM? I've seen it in the same place when I ran CELB2.8, too.
Hmm that is rather strange, still I'm pretty nooby, but maybe a dev really could point you in the right direction, at least tell you what it is or does.
Sent from my Eris using XDA App
Try renaming it to a regular name while keeping the .apk extension.. its not there on my taintedtenzo, but I've seen it before.. sometimes that seems to happen and show up in data/app and/or data/app-private when you download an app from the market and it doesn't finish installing correctly for some reason.. In your case it was a private app you tried to install from market. It is not a function. Rename it to anything.. just remove the star and don't add any spaces, keeping the .apk at the end, then try to install and it should pop up telling you what app you are installing.
Only thing is I'm not sure if private apps can he installed directly from a .apk, as they always have a .zip file in data/app.
Tainted Tenzo 2.1 v8 and/or Kaos Froyo v31
Question: Is your Superuser app asking for permissions from apps? Mine isn't. On my old rooted Eris, if I ran an app such as Titanium Backup or Root Explorer, I would get a dialog which would ask if I wanted to grant that app root access. This dialog was via the Superuser app. I don't get that now. It seems like any/every app on my phone has su access.
I'm wondering if it's just me or if this is the way the current root exploit works.
DeezNotes said:
Question: Is your Superuser app asking for permissions from apps? Mine isn't. On my old rooted Eris, if I ran an app such as Titanium Backup or Root Explorer, I would get a dialog which would ask if I wanted to grant that app root access. This dialog was via the Superuser app. I don't get that now. It seems like any/every app on my phone has su access.
I'm wondering if it's just me or if this is the way the current root exploit works.
Click to expand...
Click to collapse
It's just you. Try running root explorer or a screen cap program, and verify that you have root access. You may want to use an updated Superuser.apk too, I know the one I'm using (2.3.6.1) asks, (unless I told it not too).
I'm using Superuser 2.3.6.1. When I run Titanium or Root Explorer, everything works without prompting. Now, I'm concerned.
UPDATE: I opened Superuser, went to settings, scrolled to the bottom and updated the su binary. Now, I get prompted when an app needs access. Problem is, when I reboot the su binary is reset. I think this is due to me using the joeykrim root procedure, which uses a version of su that is scripted to be put in place during the boot process. I'm going to take a look at his scripts and change them so I can keep the su binary installed by the Superuser.apk.
Thanks for the info.
Confirmed my issue was due to using the joeykrim method. I backed out his procedure and used Dirrk's method (posted here: http://forum.xda-developers.com/showthread.php?t=779238) and I get a proper Superuser prompt when an application needs access.
I also noticed another flaw in the joeykrim method. Since his procedure was developed for the Epic, he has some incorrect file names in some places.
If you notice in his instructions where he says use playlogos1 instead of playlogos, this is not updated in all of his steps.
To get your boot screen back, you have to change the last line of playlogos1 or playlogosnow (based on whether you did the lag fix or not)
The file that will not show your boot animation will look like this:
Code:
#!/system/bin/sh
#joeykrim-SDX sdx-developers.com scripted
/system/bin/joeykrim-root.sh
/system/bin/playlogo-orig
To fix it, change the last line to read:
Code:
#!/system/bin/sh
#joeykrim-SDX sdx-developers.com scripted
/system/bin/joeykrim-root.sh
/system/bin/playlogos1-orig
In summary, the playlogos1 file is used to execute other startup scripts. The original playlogos1 file has the boot animation in it. It must be referenced in one of the startup scripts. Since these instructions were used for the Epic, there's a slight typo which keeps the original playlogos1 file from being executed.
Thanks--I came to the forums looking for a solution to the fact that my boot animation was now missing. I tried making your changes but I still can't seem to recover it. Here are what my playlogo scripts look like, keeping in mind I have also installed the lag fix:
playlogos1
Code:
#!/system/bin/sh
sh /system/bin/userinit.sh
playlogosnow
playlogosnow
Code:
#!/system/bin/sh
#joeykrim-SDX sdx-developers.com scripted
/system/bin/joeykrim-root.sh
/system/bin/playlogos1-orig
I'll also have a 3rd file called just playlogo (which was very long). Do you know what the issue is? Thanks so much for your help.
theicemonkey said:
Thanks--I came to the forums looking for a solution to the fact that my boot animation was now missing. I tried making your changes but I still can't seem to recover it. Here are what my playlogo scripts look like, keeping in mind I have also installed the lag fix:
playlogos1
Code:
#!/system/bin/sh
sh /system/bin/userinit.sh
playlogosnow
playlogosnow
Code:
#!/system/bin/sh
#joeykrim-SDX sdx-developers.com scripted
/system/bin/joeykrim-root.sh
/system/bin/playlogos1-orig
I'll also have a 3rd file called just playlogo (which was very long). Do you know what the issue is? Thanks so much for your help.
Click to expand...
Click to collapse
Judging by what your files look like, things should work. The original file is playlogos1. We never touch the playlogo file from what I can remember, so let's not do anything there.
What I would do is make sure the permissions are straight on all the files listed above (primarily playlogos1). They should be 755 (shown below):
Code:
# cd /system/bin
# ls -l playl*
-rwxr-xr-x root shell 10060 2010-08-12 04:30 playlogo
-rwxr-xr-x root root 106 2010-09-11 18:53 playlogos1
-rwxr-xr-x root root 177 2010-09-11 18:55 playlogos1-lagfix
-rwxr-xr-x root shell 14420 2010-08-12 12:30 playlogos1-orig
-rwxr-xr-x root shell 14204 2010-08-12 04:30 playlpm
#
If all else fails, you can always grab the original file from the system dump off of this link: http://forum.androidcentral.com/fascinate-roms-hacks/32839-fascinate-system-dump.html
DEAR GOD
Well, I'm an idiot.
I tried to take the playlogos1 file from the dump you showed me and copy it to my /system/bin file and, sure enough, I got the boot animation back. Problem is, I didn't think it through (that the edited playlogos1 file pointed to the rest of the modified boot sequence) and then the phone wouldn't boot. It would just loop the animations.
I booted into recovery, did a factory reset, and now I can get to the lockscreen and the very beginning of setup but TWLauncher force closes over and over and over and I'm unable to do anything except pull down the notification bar occasionally. I think this is because I moved some things (like bing, daily briefing, etc.) that TWLauncher wants at the outset, and it doesn't have them. I tried to bluetooth over LauncherPro and run it, but it fails at the last moment.
Does anyone know of a way to get to ADB Shell so that I can fix my mistake? Or if someone had an update.zip I could flash to get back to factory (with all of the system files in place), that would be super! Otherwise, it looks like I'm effed and will need to come up with a good story to tell Verizon...
theicemonkey said:
Well, I'm an idiot.
I tried to take the playlogos1 file from the dump you showed me and copy it to my /system/bin file and, sure enough, I got the boot animation back. Problem is, I didn't think it through (that the edited playlogos1 file pointed to the rest of the modified boot sequence) and then the phone wouldn't boot. It would just loop the animations.
I booted into recovery, did a factory reset, and now I can get to the lockscreen and the very beginning of setup but TWLauncher force closes over and over and over and I'm unable to do anything except pull down the notification bar occasionally. I think this is because I moved some things (like bing, daily briefing, etc.) that TWLauncher wants at the outset, and it doesn't have them. I tried to bluetooth over LauncherPro and run it, but it fails at the last moment.
Does anyone know of a way to get to ADB Shell so that I can fix my mistake? Or if someone had an update.zip I could flash to get back to factory (with all of the system files in place), that would be super! Otherwise, it looks like I'm effed and will need to come up with a good story to tell Verizon...
Click to expand...
Click to collapse
Sorry you're having issues. Bad news is, you can't flash any zip updates because we don't have a custom recovery re our phones yet. However, what you should be able to do is use adb to push the apps from /system/app from the system dump. That is.. if you can get adb to work? If it can work from recovery, that should save you.
Good luck.
I used Oneclickroot and it says my device is rooted, but none of the apps like Titanium backup, say I have root. I also followed another way or rootiong my phone where you use the volume down button to select "reinstall packages" it says it was rooted successfully, yet none of the root-required apps are detecting root. I also have the superuser app installed now.
I dont want to flash a ROM or anything, i just want to delete the bloatware and make my battery last longer
Are you on android 2.2 or 2.1?
Sent from my SGH-T959 using xda premium
im on 2.2 with froyo.
I actually followed the directions that were posted on XDA about how to root, so im not sure why it didnt work. This is another that I followed when the XDA one didnt work... http://www.techwhizz.com/root-samsung-vibrant-android-22-froyo-2/
I also keep getting this when OnClickRoot asks to test when rooting is finished...
Running a SU test...
Test failed!
FAILED
any suggestions?
I have used the ODIN route with Eugene's Unofficial TMO 2.2 Froyo ODIN. You can find it here with the directions:
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=3
If you are successful, you will be rooted and stock. Some of the bloat will already be removed. Good Luck.
The goal is not to wipe anything from my phone. This is why I have never bothered to root my phone. I knew something would go wrong, and it would be so easy like everyone says it is. I just want my battery to last longer. Im already using Juice Defender, but I still only get about 8 hours on my phone. I hardly use it and find it almost dead by 8pm
I have busybox and battery calibrator, but say im not rooted. Superuser shows no apps
To be clear, you were using nothing but stock 2.2 Froyo. You then used the OneClickRoot method for rooting, follow all instructions exactly as they're listed. After you rebooted, you attempted to download and use an app that requires root and it didn't work. Is that correct?
I've noticed that occasionally Titanium Backup won't properly recognize root until you've wiped the data for it through the Applications Manager.
kaintfm said:
To be clear, you were using nothing but stock 2.2 Froyo. You then used the OneClickRoot method for rooting, follow all instructions exactly as they're listed. After you rebooted, you attempted to download and use an app that requires root and it didn't work. Is that correct?
I've noticed that occasionally Titanium Backup won't properly recognize root until you've wiped the data for it through the Applications Manager.
Click to expand...
Click to collapse
thats correct. The only thing that does recognize root is now battery calibrator. Superuser still shows no apps
so far the only app that recognizes root is battery calibrator. Busybox, TB, and autokiller memory optimizer dont recognize root. super user shows no apps. Im wondering if my phone is even rooted, since after using battery calibrator, my phone has dropped 15% in the last 20 minutes. Nothing is even running on my phone. its just sitting there.
I did use Root Checker, heres the results...
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 3.0.6 is installed!
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: No such file or directory
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your SGH-T959 device by Root Checker version 3.9 from joeykrim in the Android Market - http://goo.gl/GgWae
but I guess BusyBox was installed correctly...
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
BusyBox binary location: /system/xbin/busybox
BusyBox binary file information: -rwxrwxrwx root root 282624 2011-10-27 22:46 busybox
Installed BusyBox Version:
BusyBox is not sharing its version information
BusyBox supports the following applets:
BusyBox is not sharing its supported applets
Results provided on your SGH-T959 device by Root Checker version 3.9 from joeykrim in the Android Market - http://goo.gl/GgWae
Im sure that im putting the update.zip on the internal sdcard and that it isnt called update.zip.zip. Ive been at this for 3 days now...
Anything? Ive posted the results from Root Check... really didnt think rooting would be this much of an ordeal
How about if you unroot and start over.
Get a terminal (any terminal) from the market or if you have adb set up and run these commands.
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
reboot
Then start over with the update.zip from the stickie that I show you yesterday.
I don't usually solicit thanks but this is going on two days now. How about a little something for the effort, eh? hahaha
I did try ot unroot last night with one click root and it says Im not rooted when I try that. I did use the update.zip from the sticky you gave me.
When i used the terminal I got:
rm failed for -r/system/bin/su, no such file/directory
reboot: operation not permitted
At this point, i would say Odin back to stock or try to re-root with the first method you tried. I agree though, it should not be this hard to do it. If you do end up going back to stock, just use the update.zip method to root it. It works so much easier.
Like I said yesterday, it took less than 3 mins to do it. It actually took me longer to download it than to do it and I never once hooked up to a PC. Did it all through phone with browser, xda app and root explorer.
itsLYNDZ said:
When I used the terminal I got:
rm failed for -r/system/bin/su, no such file/directory
reboot: operation not permitted
Click to expand...
Click to collapse
Did you type su and then enter first? Did ask for superuser permission? From what you posted last night and now this, I am almost positive that you are not rooted and Odin-ing back tostock is the way to go and start over.
I just deleted the update.zip file. im gonna start over, again. Should it remain zipped? Or do I need to extract it? Ive also read somewhere the update.zip needs to go in the j:/ or the root of the internal sdcard? I dont see that anywhere on the internal sdcard or anywhere in my files. Ill try the terminal again.
I was wondering if someone could help. I have followed all the instructions of this post http://forum.xda-developers.com/showthread.php?t=1886460 It says it is successful, but still do not have root access. Could someone tell me if they see something wrong?
Here is the log from Root Checker.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 0.98 - 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: -rwsr-sr-x root root 91988 2012-11-20 09:39 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
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:
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
Results provided on your C5155 device by Root Checker Pro version 1.3.0 from joeykrim in the Android Market - http://goo.gl/NcnHn
Fixed
Removed Super SU all is now ok.
I have been trying to root my Kyocera Rise I just got a week ago, and I am having this problem as well. However it seems that removing SuperSU isn't doing the trick. What was your method of going about this? I'm so lost without root access . I followed the tutorial to a T, multiple times, as other users have suggested, and I get nothing! Thanks for your time!
I had the same problem I went into stuff folder of binry and replaced supersu with su, re-ran it and root took 1st time
Sent from my Amazon Kindle Fire using Tapatalk 2
Forgot this but make sure you open super su and in installing from within app and then uninstall in market before running with su apk.
Sent from my C5155 using Tapatalk 2
Could not get v17 to work. I saw in the thread v3 was supposed to so I tried it and after a few attempts I got it.
Sent from my LG-VM670 using Tapatalk 2
any luck on 4.0.4?
the latest krise firmware version is 4.0.4.
In the thread the guy who reported rooting success didn't say his version num, so it could be outdated information.
I am on 4.0.4, was not aware of any other version for this phone
Sent from my Amazon Kindle Fire using Tapatalk 2
jimchee said:
Forgot this but make sure you open super su and in installing from within app and then uninstall in market before running with su apk.
Sent from my C5155 using Tapatalk 2
Click to expand...
Click to collapse
Could you please be more specific with your procedure?
sonic_knx said:
Could you please be more specific with your procedure?
Click to expand...
Click to collapse
Since you have a rooted copy now, could i borrow a backup or a copy of the system folder because I installed hp beats audio installer (do not do) and my audio drivers are messed up. It is really taking a long time to get a copy so I was hoping that you guys would have a good copy. I also have another guy with the same issue so please help us.
the actual problem and a slight fix...
The actual problem/glitch with supersu is when it tries to promt access for su it freezes the app. When I tried unistalling supersu and installing superuser. It did not work for me even with the proper uninstall procedure (going into super su settings and click uninstall and prepare for new su app. Then go to the play store search supersu, google still thinks installed so click uninstall from there then immediatly search and install superuser.) I even tried going into the root setup folder I downloaded and switched the su apk files to start the root fresh... and still nothing. I figured out its the problem with the app trying to promt you for su access (ether app) bcs when I went into the settings I changed it to automaticaly grant su (TO EVERY APP READ BOTTOM DISCLAIMER) instead of promting you to ask for su.
DISCLAIMER: I AM NOT RESPONSIBLE FOR A ROUGE APP TAKING ADVANTAGE OF YOUR PHONE WITH YOUR SU SET TO GRANT ACCESS TO ALL APPS INSTEAD OF PROMTING YOU FOR YOUR ACTION ON ACCESS.
root VM rise
I used this method to root my Rise it says hydro but works on rise too.
http://www.cricketusers.com/content/646-root-cricket-wireless-kyocera-hydro-tutorial.html
can someone explain how to use bypasslkm in further detail. i looked through multiple threads but im stilll not getting the handle on it,
Open your terminal emulator on your phone (download one from Google play if you don't have one) open the terminal and type the following commands (Pressing enter to execute each one)
su (sands for switch user, used alone will switch you to the "root" user. Equilivent to Admin in windows)
cd /data/local/temp (cd - change directory, followed by the complete folder path you want to navigate to)
chmod 755 bypasslkm (not going to get too in depth with this one because I could go on for a while with it but "chmod 755" changes the permissions to read, write, execute for the root user and read/execute for everyone else)
. /bypasslkm (. / tells the system to look in the current directory and, in this case, execute bypasslkm)
Hope this helps clear some things up for you!
Sent from my SCH-I545 using XDA Premium HD app
sfgrimes said:
Open your terminal emulator on your phone (download one from Google play if you don't have one) open the terminal and type the following commands (Pressing enter to execute each one)
su (sands for switch user, used alone will switch you to the "root" user. Equilivent to Admin in windows)
cd /data/local/temp (cd - change directory, followed by the complete folder path you want to navigate to)
chmod 755 bypasslkm (not going to get too in depth with this one because I could go on for a while with it but "chmod 755" changes the permissions to read, write, execute for the root user and read/execute for everyone else)
. /bypasslkm (. / tells the system to look in the current directory and, in this case, execute bypasslkm)
Hope this helps clear some things up for you!
Sent from my SCH-I545 using XDA Premium HD
I keep getting a message saying that there is no such directory after trying to execute "chmod 755 bypasslkm"
Click to expand...
Click to collapse
Deleted
Sent from my SCH-I545 using Tapatalk
JTSDeveloper said:
I keep getting a message saying that there is no such directory after trying to execute "chmod 755 bypasslkm"
Click to expand...
Click to collapse
I had the same issue. Here is the binary from Surges dropbox https://www.dropbox.com/s/9rdz9ff6x5foech/bypasslkm
Make sure you copy it to the right directory and follow all the commands.
Sent from my SCH-I545 using XDA Premium HD app
To add to the above post, after downloading that just execute this in terminal
Code:
su
mount -o remount,rw /system
find . -name "bypasslkm" -exec cp {} /data/local/tmp \;
find /data/local/tmp -name "bypasslkm" -type f -exec chmod 755 {} \;
./data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Surge1223 said:
To add to the above post, after downloading that just execute this in terminal
Code:
su
mount -o remount,rw /system
find . -name "bypasslkm" -exec cp {} /data/local/tmp \;
find /data/local/tmp -name "bypasslkm" -type f -exec chmod 755 {} \;
./data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Click to expand...
Click to collapse
I got the following error trying to execute after downloading the bypasslkm file and doing what you said
JTSDeveloper said:
I got the following error trying to execute after downloading the bypasslkm file and doing what you said
Click to expand...
Click to collapse
Thats not an error. If you had bypasslkm anywhere on your phone, it should now be in /data/local/tmp with the right permissions and should have executed. Make sure you downloaded the bypasslkm binary linked above
Edit: Also just copy and paste the whole script to make things easier
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Thats not an error. If you had bypasslkm anywhere on your phone, it should now be in /data/local/tmp with the right permissions and should have executed. Make sure you downloaded the bypasslkm binary linked above
Edit: Also just copy and paste the whole script to make things easier
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's still not working. Any ideas? Should I move it directly into /data/local/tmp
Surge1223 said:
Thats not an error. If you had bypasslkm anywhere on your phone, it should now be in /data/local/tmp with the right permissions and should have executed. Make sure you downloaded the bypasslkm binary linked above
Edit: Also just copy and paste the whole script to make things easier
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I downloaded the binary from above and pasted it directly in data/local/tmp then tried it and it still didn't work :/ what should the permissions on the file be? I'm a noob at this stuff
JTSDeveloper said:
I downloaded the binary from above and pasted it directly in data/local/tmp then tried it and it still didn't work :/ what should the permissions on the file be? I'm a noob at this stuff
Click to expand...
Click to collapse
The permissions should be 755, as Surge said.
If you KNOW it's in /data/local/tmp, then do this in a terminal emulator window:
Code:
su
mount -o remount,rw /system
chmod 755 /data/local/tmp/bypasslkm
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
mount -o remount,ro /system
exit
If this doesn't work, DO NOT post just "it didn't work". Say what you did, why you think it failed. Capture the output and reply here with it.
Solution to the 755 bypasslkm issue!!!!!
k1mu said:
The permissions should be 755, as Surge said.
If you KNOW it's in /data/local/tmp, then do this in a terminal emulator window:
Code:
su
mount -o remount,rw /system
chmod 755 /data/local/tmp/bypasslkm
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
mount -o remount,ro /system
exit
If this doesn't work, DO NOT post just "it didn't work". Say what you did, why you think it failed. Capture the output and reply here with it.
Click to expand...
Click to collapse
I figured it out! Here is exactly what I did:
after downloading the bypasslkm.bin from the dropbox link, I used ES File Explorer (WITH ROOT ENABLED) to move the bypasslkm file to directly to the data/local/tmp location. NOTE: there are a few places marked "data" and "local" on the phone, so when you open a "data" folder, make sure you find the path in the right order [ i.e. first data, then local, and then tmp]
Using a ROOT FILE EXPLORER app (because ES doesn't have what you will need) go to the bypasslkm file, long press, and select permissions. It will display with permissions are currently set. At the bottom, it SHOULD display the total sum of the permissions selected. Basically, that means by selecting the right boxes, you can change the permissions to 755 !
7 5 5
user group world
r+w+x r+x r+x
4+2+1 4+0+1 4+0+1 = 755
These setting will give you the 755 that you need to pull this off .
When you have the permissions changed to 755, the last step was actually very easy. But if you want to play it safe, then I will tell you the root file browser I specifically used to do the last step.
I used the app Root Browser version 2.2.3 ( i literally googled for any generic root file explorer and this came up )
ok, so when you have the permissions changed, long press on the bypasslkm file.
select "Open With" and then select the option "Open As.."
At the bottom of the options is "script file" select it.
after doing so, select the option "Execute" and... Voila! I immediately regained my WIFI !!!!! \>w</
I hope this guide helped everyone out. I tried to be as specific as possible.
EinGlo said:
I figured it out! Here is exactly what I did:
after downloading the bypasslkm.bin from the dropbox link, I used ES File Explorer (WITH ROOT ENABLED) to move the bypasslkm file to directly to the data/local/tmp location. NOTE: there are a few places marked "data" and "local" on the phone, so when you open a "data" folder, make sure you find the path in the right order [ i.e. first data, then local, and then tmp]
Using a ROOT FILE EXPLORER app (because ES doesn't have what you will need) go to the bypasslkm file, long press, and select permissions. It will display with permissions are currently set. At the bottom, it SHOULD display the total sum of the permissions selected. Basically, that means by selecting the right boxes, you can change the permissions to 755 !
7 5 5
user group world
r+w+x r+x r+x
4+2+1 4+0+1 4+0+1 = 755
These setting will give you the 755 that you need to pull this off .
When you have the permissions changed to 755, the last step was actually very easy. But if you want to play it safe, then I will tell you the root file browser I specifically used to do the last step.
I used the app Root Browser version 2.2.3 ( i literally googled for any generic root file explorer and this came up )
ok, so when you have the permissions changed, long press on the bypasslkm file.
select "Open With" and then select the option "Open As.."
At the bottom of the options is "script file" select it.
after doing so, select the option "Execute" and... Voila! I immediately regained my WIFI !!!!! \>w</
I hope this guide helped everyone out. I tried to be as specific as possible.
Click to expand...
Click to collapse
worked perfectly and all my confusion is now gone thank you.
Fix works but new issue
JTSDeveloper said:
worked perfectly and all my confusion is now gone thank you.
Click to expand...
Click to collapse
Thanks for the support. Glad I could help. Has your WIFI remained on, though? The solution I posted works, but only for a short amount of time. rebooting the system undoes the work I did and I have to go back into the root browser and execute the file all over again to get wifi.
Can Surge or someone else offer any expertise?
with the permissions changed properly, I tried executing the code, and still not working.
I have safestrap enabled, and I have sound restored. I am currently on android 4.3 from the downgrade provided by Surge. Its rooted.
If I were to upgrade to the rooted version of NC5, would that help fix the wifi issue, or would it carry over?
Any input going forward is appreciated!
EinGlo said:
Thanks for the support. Glad I could help. Has your WIFI remained on, though? The solution I posted works, but only for a short amount of time. rebooting the system undoes the work I did and I have to go back into the root browser and execute the file all over again to get wifi.
Can Surge or someone else offer any expertise?
with the permissions changed properly, I tried executing the code, and still not working.
I have safestrap enabled, and I have sound restored. I am currently on android 4.3 from the downgrade provided by Surge. Its rooted.
If I were to upgrade to the rooted version of NC5, would that help fix the wifi issue, or would it carry over?
Any input going forward is appreciated!
Click to expand...
Click to collapse
It is possible to automate this.
Create a file with the following contents:
Code:
#!/system/bin/sh
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Save this file as /system/etc/install-recovery-2.sh.
Make sure that the bypasslkm file is in /data/local/tmp.
Reboot, and you should now have WiFi again.
[Note: this assumes SuperSU has it's custom copy of /system/etc/install-recovery.sh in place. If that's not there, it's still possible to edit /init.rc to add a stanza to run this command.]
Issue with auto-running my solution
k1mu said:
It is possible to automate this.
Create a file with the following contents:
Code:
#!/system/bin/sh
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Save this file as /system/etc/install-recovery-2.sh.
Make sure that the bypasslkm file is in /data/local/tmp.
Reboot, and you should now have WiFi again.
[Note: this assumes SuperSU has it's custom copy of /system/etc/install-recovery.sh in place. If that's not there, it's still possible to edit /init.rc to add a stanza to run this command.]
Click to expand...
Click to collapse
I do NOT have supersu's install recovery 2 file in the location you said. I only have the regular install recovery file.
What I should I do? Could I create the file in laptops termial?
The first line of code gave me the error "file not found"
update
EinGlo said:
I do NOT have supersu's install recovery 2 file in the location you said. I only have the regular install recovery file.
What I should I do? Could I create the file in laptops termial?
The first line of code gave me the error "file not found"
Click to expand...
Click to collapse
I tried again.
Ok, so I figured out the coding a little bit. Im not used to this, so forgive my ignorance.
I did the code as u typed it. BUT I made a change. Because I kept getting the "file not found " error. I added ".bin" to the end of the bypasslkm code line. It generated a real response. I felt relieved. I went ahead and typed the last line of code.
THEN I was told the file already exists... I have attached a picture of what I got in android Terminal
EinGlo said:
I do NOT have supersu's install recovery 2 file in the location you said. I only have the regular install recovery file.
What I should I do? Could I create the file in laptops termial?
The first line of code gave me the error "file not found"
Click to expand...
Click to collapse
You should have /system/etc/install-recovery.sh
It will run /system/etc/install-recovery-2.sh if it exists. What I would do is to create the file on your PC, put it onto your SDcard on the PC, then use Root Explorer to put it into place.
The "file exists" error is because you already have the WiFi module installed. That won't happen when this script runs at boot.
Question
k1mu said:
You should have /system/etc/install-recovery.sh
It will run /system/etc/install-recovery-2.sh if it exists. What I would do is to create the file on your PC, put it onto your SDcard on the PC, then use Root Explorer to put it into place.
The "file exists" error is because you already have the WiFi module installed. That won't happen when this script runs at boot.
Click to expand...
Click to collapse
Ok. I'll try that tonight.
But I have a few questions
Im basically trying to autostart the wifi module when the phone boots up right? Are there any apps that can accomplish this specific task?
Also about the downgrade in general. Did anyone get their SD card permissions restored after downgrading? I donwgraded to 4.3, rooted the phone, and somehow I STILL cant move apps to the sd card! Im beginning to suspect that thr issue may be with the card itself, which can be fixed with formatting the sd card. But has anyone had any problems with moving apps to the sd card?
Finally, the bug question concerning the wifi issue.
Is this probkem specific only to those with the downgrade? If so, should upgrading to Surge's rooted kitkat (with sd card permissions and tethered enabled) resolve the wifi issue?
I also noticed that I had wifi access when the phone had no sound. Only when I flashed the Non-HLOS bin file did I encounter this wifi issue.
Thanks for the feedback so far, I just need to understand whrre to go from here
EinGlo said:
Ok. I'll try that tonight.
But I have a few questions
Im basically trying to autostart the wifi module when the phone boots up right? Are there any apps that can accomplish this specific task?
Click to expand...
Click to collapse
I'm sure there are programs that can be set up to run scripts as root during boot; However, that's complicated since you want this to run while the phone is booting, before there's any opportunity to allow SuperSU to ask for permission.
EinGlo said:
Also about the downgrade in general. Did anyone get their SD card permissions restored after downgrading? I donwgraded to 4.3, rooted the phone, and somehow I STILL cant move apps to the sd card! Im beginning to suspect that thr issue may be with the card itself, which can be fixed with formatting the sd card. But has anyone had any problems with moving apps to the sd card?
Click to expand...
Click to collapse
That's a problem that's fixed by an edit to /system/etc/permissions/platform.xml, adding a stanza that permits external storage write access.
EinGlo said:
Finally, the bug question concerning the wifi issue.
Is this probkem specific only to those with the downgrade? If so, should upgrading to Surge's rooted kitkat (with sd card permissions and tethered enabled) resolve the wifi issue?
I also noticed that I had wifi access when the phone had no sound. Only when I flashed the Non-HLOS bin file did I encounter this wifi issue.
Thanks for the feedback so far, I just need to understand whrre to go from here
Click to expand...
Click to collapse
The need to run the "bypasslkm" program is because of the downgrade. If you go to a clean rooted Kit Kat ROM, it shouldn't have any issues with WiFi being enabled. That may be the easiest way to fix this.