I had previously rooted my fascinate. I was having network problems and the root had something to do with it. I used my recovery in CWM to recover. Turns out the problem was not root. I have since tried to root again using the manual method along with one click root. Neither have worked. Everything seems fine except I get this error:
- exec 'system/xbin/bash failed No such file or directory <2>
what does this mean and how can I fix it.
If it helps, i went to my unrooted root explorer and did not have a bash folder in xbin.
Try Z4 root.
Sent from my SuperDark DJ05 Fascinate.
Related
SO i rooted my mytouch 4g today. I was trying to install Cyogen mod7.
But i have a problem. I am Already rooted ( i know for sure) but when i go into termal emulator and type "Su" it keeps giving me permission denied. Now my question is can i continue to go into rom manager--> And flash CM7 from zip?
Will it work and would eerything work once om on Cm7?
Are you compleatly sure? Go to hboot and check that you have s=off just in-case. Sorry if im not much of a help, im not exactly a pro.
TallestSpoon said:
SO i rooted my mytouch 4g today. I was trying to install Cyogen mod7.
But i have a problem. I am Already rooted ( i know for sure) but when i go into termal emulator and type "Su" it keeps giving me permission denied. Now my question is can i continue to go into rom manager--> And flash CM7 from zip?
Will it work and would eerything work once om on Cm7?
Click to expand...
Click to collapse
If terminal gives you that message then you are not fully rooted.
darksulfur5 said:
Are you compleatly sure? Go to recovery and check that you have s=off just in-case. Sorry if im not much of a help, im not exactly a pro.
Click to expand...
Click to collapse
The recovery will not tell you if s= off. The engineering scree will however.
Tallestspoon how do you "know" you are rooted.
Sent from my HTC Glacier using Tapatalk
neidlinger said:
The recovery will not tell you if s= off. The engineering scree will however.
Tallestspoon how do you "know" you are rooted.
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Sorry, I meant h boot. Edited and corrected.
Sent from my HTC Glacier using XDA Premium App
Look up MT4GROOT, and download it, it's the easiest way to root the MT4G
This is what I used and it was my first time ever doing anything on a smart phone. Plus it unlocks everything.
http://forum.xda-developers.com/showthread.php?t=834225
Sent from MyTouch 4G: CM7 RC2 using XDA App
Just getting s=off is not enough. S=off will allow you to full root by allowing non official recovery versions to be flashed. Basically s=off means you have disabled the security system that checks the software you are installing is official versions. It does not mean the ROM itself has root. There are specific files and functionality that must be installed to have root access. The SU app can be installed but not functional without these essential files and functions.
Basically there are two kinds of root. Root on a stock device, which inserts the SU functionality into the existing software, the other is root with custom software. The second option requires s=off. (or at least an exploit that gets around it) Temp root is a process in which the system files are copied into a temp location and the software is tricked into using the copied files instead of the real files. That means that rebooting erases the temp files and the software uses the originals again. This is useful in that with these files copied and root enabled through them, they can be used to trick the software to allow the real files to be altered.
After you do get s=off, you must run visionary to temp root again, and before you do, check the box to ensure that system is R/W after temp root completes. This is where you trick the software to allow you to change the real system files.
Remember, if you reboot at any time before perm root is achieved, you will loose root and SU functions.
After temp root you should run visionary again to perm root. I had issues with the app not wanting to start the process for perm root. I just ran the temp root with R/W enabled, downloaded ROM manager from the market, then used ROM manager to flash clockwork recovery. Then I put a ROM zip on my SD and rebooted into recovery and flashed the zip and BAM running on a rooted custom ROM.
Make sure you pick a clockwork version that will work for your intended ROM. You must pick the "all clockwork recoveries" option to select the correct version, as the default version installed is 3.0.0.5
If you want CM7 use 3.0.0.5 if you want any froyo based ROM get the one ending in .12 (as the version .14 never flashes properly, for me at least and that is on 3 different MT4G I have rooted) Now that you have a custom recovery, you can install any ROM you want. (keeping in mind the froyo/gingerbread recovery compatibility)
Remember that just installing a custom recovery is not root either, you must install a new ROM or use visionary to gain perm root.
I am rooted, and s-off. I actually have some restores/ and backups that will take my phone back to unrooted through ROM manager. I can always go back to another backup though, and I am rooted again. Strange but it works somehow. I am using Royal Ginger and love it now, but I could still go back to s-off, unrooted through Clockwork, so I don't understand that.
I've replaced the file using root explorer. rebooted the now having bootloop.
tried the adb push method posted by bullyfrog but still can make it to work. issit because i have oclf installed and ext2 tools?
im not really good at this, i've got 2 tabs. the previous one did fine with the battery mod, but not my 2nd tab.
i cant update my firmware with oclf installed issit?
Do adb reboot recovery. Then reflash any kernal you have on your sd card.
slideworks said:
I've replaced the file using root explorer. rebooted the now having bootloop.
tried the adb push method posted by bullyfrog but still can make it to work. issit because i have oclf installed and ext2 tools?
im not really good at this, i've got 2 tabs. the previous one did fine with the battery mod, but not my 2nd tab.
i cant update my firmware with oclf installed issit?
Click to expand...
Click to collapse
Just a word of advice: always push framework-res.apk using adb in recovery. My OG Droid would always bootloop if i replaced it using root explorer.
I used Epic All in One Root and Recovery v2.04 a while back to root my Epic. Uninstalled a few of the apps. Got the froyo push today but it wouldn't take, figure it had to do with removing apps and rooting. I recovered the apps and removed root. Downloaded the update.zip and booted into recovery mode to install. I'm now getting an assertion error because the install cannot find /system/bin/playlogo
I've read some threads and noticed some of the root procedures created a playlogo-orig. I don't have that file. I do have playlogos1 though, though I'm guessing that isn't the same file?
Sort of stuck on what to do next. Can't seem to locate a playlogo to download to sdcard. Any help would be appreciated.
deflin39 said:
I used Epic All in One Root and Recovery v2.04 a while back to root my Epic. Uninstalled a few of the apps. Got the froyo push today but it wouldn't take, figure it had to do with removing apps and rooting. I recovered the apps and removed root. Downloaded the update.zip and booted into recovery mode to install. I'm now getting an assertion error because the install cannot find /system/bin/playlogo
I've read some threads and noticed some of the root procedures created a playlogo-orig. I don't have that file. I do have playlogos1 though, though I'm guessing that isn't the same file?
Sort of stuck on what to do next. Can't seem to locate a playlogo to download to sdcard. Any help would be appreciated.
Click to expand...
Click to collapse
Just use Odin to flash back to stock
Sent from my SPH-D700 using XDA Premium App
deflin39 said:
I used Epic All in One Root and Recovery v2.04 a while back to root my Epic. Uninstalled a few of the apps. Got the froyo push today but it wouldn't take, figure it had to do with removing apps and rooting. I recovered the apps and removed root. Downloaded the update.zip and booted into recovery mode to install. I'm now getting an assertion error because the install cannot find /system/bin/playlogo
I've read some threads and noticed some of the root procedures created a playlogo-orig. I don't have that file. I do have playlogos1 though, though I'm guessing that isn't the same file?
Sort of stuck on what to do next. Can't seem to locate a playlogo to download to sdcard. Any help would be appreciated.
Click to expand...
Click to collapse
You are correct playlogos1 is not the same file as playlogo.The one click root should backup playlogo since it still gets run by the script that replaces playlogo it just runs playlogo-orig from the script that is named playlogo that one click installs.
Thanks for the info. I'll give Odin a shot.
I can flash it, it works as it should until I reboot the phone. Once I reboot, the stock recovery comes back. Ive seen threads about deleting a couple files, but not sure if I should be doing that. any ideas on what I may be doing wrong?
blackhemi4x4 said:
I can flash it, it works as it should until I reboot the phone. Once I reboot, the stock recovery comes back. Ive seen threads about deleting a couple files, but not sure if I should be doing that. any ideas on what I may be doing wrong?
Click to expand...
Click to collapse
Stock restores the install-recovery.sh file in /system/etc. This prevents recover mods from "sticking." After you root, load up your favorite root file explorer and delete/rename that file in /system/etc/ . Then, reflash recovery and you're golden.
belyle said:
Stock restores the install-recovery.sh file in /system/etc. This prevents recover mods from "sticking." After you root, load up your favorite root file explorer and delete/rename that file in /system/etc/ . Then, reflash recovery and you're golden.
Click to expand...
Click to collapse
Thanks
Just tried that, but my root explorer is not allowing write access.
Flashed superuser again, same thing....
I starting from scratch again, 4.0.4 is getting installed as I type.
Ill try rooting again and getting my root explorer to delete that file and try again
for some reason my cwm recovery is sticking and its causing my play store to stay on 3.4.7
Any ideas on why the recovery is sticking I didn't even touch the install-recovery.sh
Infact all I did was get the stock image from google flash that
then flash cwm to gain root and install superuser
after that my stock recovery just won't come back, any ideas?
Flash the newest version of su.zip
albundy2010 said:
Flash the newest version of su.zip
Click to expand...
Click to collapse
I got the latest version 3.0.7 it still won't work, I've tried so many different methods including manually flashing the stock recovery but that doesn't help with updating the play store either
---------- Post added at 04:36 PM ---------- Previous post was at 04:35 PM ----------
blackhemi4x4 said:
Thanks
Just tried that, but my root explorer is not allowing write access.
Flashed superuser again, same thing....
I starting from scratch again, 4.0.4 is getting installed as I type.
Ill try rooting again and getting my root explorer to delete that file and try again
Click to expand...
Click to collapse
to allow write access you just have to press "remount as R/W" in Root Explorer
There are different versions of 3.0.7. You should have efghi version.
Also as the other poster said you have to use root explorer the correct way if you're not doing so.
Thanks, its the little things that get me. I had the wrong 3.0.7. Got the efghi and all problems solved. time for a nandroid and mod this thing.
Is there a working circle bat mod for stock 404
Same issue
I had the same issue when I upgraded to 4.0.4.
I used the ADB shell to remount \system as R/W and was then able to rename my install-recovery.sh. After that I installed CWM and it sticks properly.
just download ROM manager from the market and install the newest CWM from the manager, it will stick. That's how I got it to stick
PhoenixIce22 said:
I had the same issue when I upgraded to 4.0.4.
I used the ADB shell to remount \system as R/W and was then able to rename my install-recovery.sh. After that I installed CWM and it sticks properly.
Click to expand...
Click to collapse
I had the same issue, rename the install-recovery.sh and manage to get CWM to stick.
Here's a fix recovery.zip just flash in cwm and it will stick.http://db.tt/B1vOd9K4 I didn't make it, just sharing it.
Hello there. I bought a S5368 (Chinese) device, and want to root it, but it doesnt have recovery (probably they disabled it), and cant root with SuperOneClick or Gingerbreak. It is running 2.3.6. So I tried to open an update file, and it seems it is in FAT16. Is this true? I opened it with UltraISO and attached the su and busybox to the system/bin, make a tar from that file, and flash it using ODIN, but stucks at aprox. 10% of the flash. Any ideas I can use to flash that package or root it? Thanks!
EDIT 1: I managed to get it working - soft of. Mounted using linux and works, BUT, I cant get superuser to work. Any app that needs root, it gets automatically denied. If I enter using the shell, it says: granted, but it exits right away
aby ideas?