Related
Hi, I posted a similar question about this under the OneRoot thread, but I don't see a lot of activity there anymore, so I was hoping to get more responses in a separate thread. I've scoured this forum and everywhere else on the Net and I haven't seen anyone experience this same issue. Hopefully someone will understand the problem and have some idea how to rectify it.
So, I have an AT&T Samgsung Captivate with the stock 2.1 Android "Eclair" build on it. I do believe there was an AT&T issued OTA update for it not long ago that put the build number up to UCJH7. I followed the instructions for TGA_Gunnman's One Click Root/UnRoot method documented here. Everything seems to work fine, in terms of booting into the recovery mode and selecting the update file. After the phone reboots, however, I do not see the Superuser Permissions app with ninja icon in my Applications area. If I browse the directory tree in my internal SD card in /system/apps, I do see a SuperUser.apk file. However, clicking on that shows me the message "Install blocked: For security, your phone is set to block installation of applications not sourced in Android Market." So it appears that rooting procedure worked, all the necessary parts were installed, but I don't have permission to execute su. I see that the xbin folder has been created, and it does contain busybox, su and something called ipctool. Also, a link does exist in /system/bin between su and /syste/xbin/su. If I use the Terminal Emulator and type "su", the prompt sits there for 10 seconds and says "permission denied".
Any ideas on what could be preventing me from gaining superuser access here?
Thanks for your help,
Mike
Download and install "SuperUser" from the Android market
OK, so here is another strange thing about this. This doesn't seem like it'd be related to my original su permission problem, but you never know. I decided to try to un-root using the one click method. Now, during the un-root script, I see the adb daemon start, but it fails on the push command writing unroot.zip to update.zip in the /sdcard folder; it says that permission is denied!. Of course, after booting into recovery, applying the update file fails, as it wasn't found in /sdcard. I'm not sure how this could have happened, as the root script was able to push the root.zip to sdcard just fine initially. Now, after I open a shell against my phone using adb, I check the permissions for the sdcard folder, and this yields rwxrwxr-x. I'm not sure, but I believe there should be another w flag set for other on sdcard. How the heck could that have been cleared?
It does look like I can copy the update.zip to sdcard manually through Windows Explorer and just manually boot into recovery using volume up + down + power, so I'm not completely dead in the water. Yet, I'd like to fix the permissions for sdcard, or else I can no longer use the one-click method.
id10terror said:
Download and install "SuperUser" from the Android market
Click to expand...
Click to collapse
Thanks for advice. I will definitely try this, but I did not see this step listed in the oneclick root method? I do see an .apk file for SuperUser in /system/apps, so it seems like the app is already resident. The problem is that it doesn't show up in my main application area on the phone, and I can't run the app; it says it is blocked.
Even if there was a superuser app in the market, wouldn't I need to enable sideloading to get it (which AFAIK need root access)?
Again, thanks for the advice, I appreciate you taking the time to help.
Mods please move to Q&A
Try adb root before adb push
Sent from my SAMSUNG-SGH-I897 using XDA App
mskelton said:
Thanks for advice. I will definitely try this, but I did not see this step listed in the oneclick root method? I do see an .apk file for SuperUser in /system/apps, so it seems like the app is already resident. The problem is that it doesn't show up in my main application area on the phone, and I can't run the app; it says it is blocked.
Even if there was a superuser app in the market, wouldn't I need to enable sideloading to get it (which AFAIK need root access)?
Again, thanks for the advice, I appreciate you taking the time to help.
Click to expand...
Click to collapse
Its blocked BC u are trying to install it, not run it. Read that error message again.
What happens if you open ROM manager and try to flash clockwork recovery? Or load titanium backup?
End points are HIGHLY important, and if you read your post carefully, you have not yet demonstrated that superuser access is broken, only the icon from which you inferred it is broken. Let me know then we can go from there
Sent from my SAMSUNG-SGH-I897 using XDA App
fatttire said:
Mods please move to Q&A
Try adb root before adb push
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Thanks, that was one of the first things I tried last night, but that did not work.
fatttire said:
Its blocked BC u are trying to install it, not run it. Read that error message again.
What happens if you open ROM manager and try to flash clockwork recovery? Or load titanium backup?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yeah, you're right, now that I see that error message, I guess it is trying to install it. That's odd, because I thought that the oneclick method would have already installed this app during the recovery boot load?
Regarding ROM manager, funny you should ask, that was the entire genesis of why I'm trying to root, so I can backup my phone and install the custom ROMs. After I installed ROM manager and tried to run it was where I initially noticed I must not have root access. When I try to flash clockwork recovery, the app hangs for (oddly enough) around 10 seconds. I never see any prompt for granting root access to clockwork recovery, nor does it boot into the recovery mode.
Okay I have another idea.
If your goal is to simply make a backup to flash a ROM, try this:
1. Download Cog 2.3b6. Other ROMs may have the file I'm looking for but I know it is here. Also you may be able to search and find this file directly but I'm too lazy to find the link for you lol
2. Open the zip file on your computer and extract /sdcard/update.zip
3. Adb push update.zip /sdcard/update.zip
4. Reboot recovery, reinstall packages, you are in clockwork recovery and can back up your ROM.
Sent from my SAMSUNG-SGH-I897 using XDA App
I'd like to try that, except that it appears there is some type of permission snafu on /sdcard. I believe the permissions on that folder *should* be 777, but it is 775 (other has no write access) for some odd reason, and I have no clue how that happened. Hence, when adb tries to push the update.zip to the internal SD folder, it gets permission denied. As I mentioned, not sure if this is related to not being able to execute su, but it is strange nonetheless.
Guys, please disregard what I mentioned earlier about adb and not being able to push the root/unroot.zip to /sdcard. I'm a moron, and I had left the internal SD card mounted to Windows after connecting the phone via USB. Clearly for adb to push/pull off of /sdcard, the internal SD card must *not* be mounted by Windows. My mistake, sorry for the confusion.
The original theme of the thread is still unanswered though, which is how the one-click root could have worked and not installed the SuperUser app onto my phone.
I will try the recommendation earlier in the thread, to download and install the SuperUser app from Android Market to see if that fixes things.
OK, so I downloaded and installed the SuperUser app from the Market, and for whatever reason, this seems to have addressed the issue. I am now prompted to allow applications root privileges. I'm not sure why this was necessary or how it fixed things, perhaps because it overwrote the version of su that was on my phone with a newer one. In any case, it's working.
Hi All,
I am trying to unlock a brand new at&t locked samsung captivate. Details:
Model - Samsung-SGH-I897
Firmware - 2.2
Kernel - 2.6.32.9
Build - FROYO.UCKB2
I have the USB debugging enabled and *#7465625# gives me Network Lock [ON].
I don't have at&t sim so was trying to follow --> 1) This <-- and --> 2) This <-- and --> 3) This <--.
And just now tried --> 4) This too <-- and this is the farthest I have reached till now.
But I am facing problems.
1) When Generate_Code.bat is run it gives this:
Code:
Copy nv_data.bin
* daemon not running. starting it now *
* daemon started successfully *
failed to copy '/efs/nv_data.bin' to './nv_data.bin': Permission denied
Extract code
2) When SuperOneClick is run and Root button is clicked then it halts at:
Rooting device... -Step #7 WaitForDevice 0.15s
and then it stops responding.
3) I have android-sdk-windows on my machine and its in the env path. When I do "adb shell" I get a "$" prompt. But when I do "su" it says "su: Not Found".
So I am not able to use this method too.
4) When followed the steps my phone rebooted and I can see the Android system recovery screen. I selected the "Reinstall Packages" from the menu but then it says:
E: Signature Verification Failed
Installation Aborted.
Click to expand...
Click to collapse
So till now this is also not working. I am still looking.
Is there anything that I am missing? (I am still reading)
Is it possible to unlock 2.2 without root and without at&t sim?
Is it possible to root 2.2 with SuperOneClick with the default settings?
Thanks
I don't know anything about unlocking, but the errors you are getting are because you are not rooted. I would try another method for getting root and then try again.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
sumitk1 said:
2) When SuperOneClick is run and Root button is clicked then it halts at:
Rooting device... -Step #7 WaitForDevice 0.15s
and then it stops responding.
Click to expand...
Click to collapse
Do you have USB debugging turned on?
I am still reading more about different methods to get root and will try it tonight and yes I have USB debugging on.
I was just wondering if I would be able to do it without getting root but if that is the only way, I will have to do that...!!
You need root to unlock your device. Current method which you are using (Super One Click) is unable to root your phone. Try another method, may be Galaxy S One Click root. I haven't rooted Stock Froyo (KB1 or KB2) so I'm not sure which method will surely work.
Once you are rooted, try again with unlocking methods. And yes, you should be able to unlock without AT&T SIM.
Now I have tried Captivate One Click Root also and this is the farthest I have gone till now. This link explains correctly but now when my phone reboots and I do a Reinstall Packages - it says
E:signature verification failed. Installation Aborted.
Click to expand...
Click to collapse
So still looking...
Hello All,
I have been in and out of every Dev and General forum about installing the CWM on Z8. Unfortunately I have yet to find a solid solution to the below errors when using MTM's ZV8CWMRecovery bat. I would be posting in related thread on the dev site, but I don't have enough posts to post in there. So far I have seen multiple users with this problem:
Recovery for ZV8
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Mounting Device
remount failed: Operation not permitted
Pushing Recovery
5152 KB/s (5345280 bytes in 1.013s)
Installing CWM Recovery
/dev/block/mmcblk0p14: cannot open for write: Permission denied
Remove Trash
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
CWM Recovery!!!
Press any key to continue . . .
I have only seen a couple answers to this that actually address the error messages. One being to manually copy the local.prop into the data folder. I have tried taking the local.prop file and moving it to /data but when I do I get the error message on my phone saying java.io.filenotfoundexception:/data/local.prop (permission denied).
I feel that this has something to do with Superuser mainly because when I have tried to use other methods like using quick boot or Rom Manager to boot into recovery, I get messages saying that Super User has denied access.
1) Is anyone else having similar Super User problems when they get the CWM installation error above?
2) Can anyone think of a correlation bewtween the super User error and the CWM installation errors?
3) Can anyone give any usefull insight into what these mean?
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
Any support is much appreciated.
im having same problem
williep said:
im having same problem
Click to expand...
Click to collapse
I am going to try the suggestion in this thread right now.
http://forum.xda-developers.com/showthread.php?t=1594369
I will let you know.
OK, I have decided that my main problem right now is that SuperUser is denying access to every program that could help me (Quick boot, Rom Manager, Terminal emulator). Every time I try and run any of those I get a message saying it was blocked by SU. I have set SU to allow all requests, yet it still Denies access?
Anyone with Ideas on how to stop this without starting from scratch?
Plumbert said:
OK, I have decided that my main problem right now is that SuperUser is denying access to every program that could help me (Quick boot, Rom Manager, Terminal emulator). Every time I try and run any of those I get a message saying it was blocked by SU. I have set SU to allow all requests, yet it still Denies access?
Anyone with Ideas on how to stop this without starting from scratch?
Click to expand...
Click to collapse
Sounds like the phone did not root properly. I had that problem before where i had superuser but no root access to anything. My solution was starting over from scratch, im not sure how to do it w/o starting over. If you have everything on the computer already then starting over should only take 15 mins or so. For me thats how long it took after i had all downloads and installs in place
Sent from my VS910 4G using xda premium
jimmyhawk said:
Sounds like the phone did not root properly. I had that problem before where i had superuser but no root access to anything. My solution was starting over from scratch, im not sure how to do it w/o starting over. If you have everything on the computer already then starting over should only take 15 mins or so. For me thats how long it took after i had all downloads and installs in place
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Thanks for the info. I did end up starting from scratch and the superuser thing was definitely a root problem. However, I still have one problem preventing me from the upgrade which is that every time I try to copy any file to the /data folder i get the java.io.filenotfoundexception:/data/local.prop (permission denied) that I mentioned above... I cannot figure out what permissions I need to change or how
Plumbert said:
Thanks for the info. I did end up starting from scratch and the superuser thing was definitely a root problem. However, I still have one problem preventing me from the upgrade which is that every time I try to copy any file to the /data folder i get the java.io.filenotfoundexception:/data/local.prop (permission denied) that I mentioned above... I cannot figure out what permissions I need to change or how
Click to expand...
Click to collapse
Sorry i am unfamiliar with that one
Sent from my VS910 4G using xda premium
Plumbert said:
Thanks for the info. I did end up starting from scratch and the superuser thing was definitely a root problem. However, I still have one problem preventing me from the upgrade which is that every time I try to copy any file to the /data folder i get the java.io.filenotfoundexception:/data/local.prop (permission denied) that I mentioned above... I cannot figure out what permissions I need to change or how
Click to expand...
Click to collapse
Give this a shot:
http://forum.xda-developers.com/showthread.php?t=1594369
I was getting the same errors. If you choose option two in the .bat it will reboot you to cwm.
Sent from my VS910 4G using Tapatalk 2
Never had to do anything with the local.prop file
Sent from my VS910 4G using Tapatalk 2
MacK1ll3r said:
Never had to do anything with the local.prop file
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
I am having this problem also, but only on my new revo (came with Zv8 my old one that came with Zv4 that is stuck in test mode worked flawlessley with MT's AIO root&Recovery App, The new one worked once i flashed TOT back to zv7 then kept root through to Zv8 but then it wouldnt install CWM or anything for that matter, All of MT's .Bats dont work no matter how many times i flash or hard reset i think something is in new software, be it LG verizon or SuperUser i dont know, but are all you people having trouble having it on Newer Phones?
I made a mistake when changing the DPI on my LG Flex using Texdroider DPI, this happened to me before when i set a too lower value. Now my phone boots and i immediately get a UI crash error which i have to press ok and it appears again, in the time between errors the phone is not responsive.
First my phone came with 4.0.2 which i rooted using ioroot then i modified the DPI, crashed bad one time as it was not booting anymore but i was able to use adb to restore the backup files (build.prop) that the program (Texdroider DPI) made. I had to use the same PC from which i performed the rooting process but it worked eventually.
I then updated to 4.4.2 and my phone was unrooted, after that i used towelroot to root it again and it installed the SuperUser app. Now i am stuck with my problem:
Tried using ADB shell to restore the backup files but i need root permission to do so.
1. When trying adb root i get "adbd cannot run as root in production builds" (Error which didn't appear in the past)
2. When i try adb shell then su nothing happens in the command window, but on the phone i get a popup for granting access to "adb" and i cannot press the Grant button as my phone is not responsive.
What can i do in this situation? Are there any solutions for one of these two methods? Like granting privileges to adb trough the command window?
Please Help, Thank you.
unless you have custom recovery or can grany adb root access i think your only option since it still is restock
---------- Post added at 06:25 PM ---------- Previous post was at 06:21 PM ----------
this http://forum.xda-developers.com/showthread.php?t=2644083 should get u back up an flexin just follow carfully if u don't understand something read read an read again i would suggest reading whole thread but if you read an understand an are confident pull the trigger
Hi guys, when I use the command " adb shell pm setInstallLocation 2" in order to install apps on the sd appears the following error " Error : java.lang.SecurityException : Package android does not belong to 2000" I use room stock 5.0.2 , I will be very grateful if anyone can help, thank you now, and sorry for the mistakes!
Same problem.
IcedG said:
Hi guys, when I use the command " adb shell pm setInstallLocation 2" in order to install apps on the sd appears the following error " Error : java.lang.SecurityException : Package android does not belong to 2000" I use room stock 5.0.2 , I will be very grateful if anyone can help, thank you now, and sorry for the mistakes!
Click to expand...
Click to collapse
I am having the same Issue. Trying to change default install location on the new moto e lte.
You should partition your extSd card first after it's work.
Sent from my SM-G355H using XDA Premium 4 mobile app