Related
If anyone can help me with this issue,its killing me. I love the DARCHDROID rom,couldnt wait anymore so i had to flash it. Flashed darchdroid,lwp kernel and everything else works, minus a few fc's. In adb i have #,and my device appears to be rooted, i have rerooted more then 35 times in the past 5 hours read numerous posts here,even some that would imply to address this issue,but does not solve my problem....seems that i dont have root access to my new 2.1 rom shell.....if this is possible. Ive tried many other roms and never come accross one that you had to re root for.But this rom looked worth it. Everything i have read seems to work for others but not me. Well the geniuses are here so here is where i ask for assistance....any thoughts or replies would be greatly appreciated, im not giving up on this rom yet......thanks in advance!
The newest darch rom is already rooted. Make sure you 'adb remount'. That allows read/write access to /system if you want to push files to it.
oops
BTW, forgot some important info,didnt want to list all of my links and flood the thread Im still at it...anyone that is capable of offering me help will understand this error....when i get to step 9 in the xda guide.forum.xda-developers. cdma hero root guide,.....site wouldnt allow me to use the link,error?strange i couldnt link because all my good links are from this site......after i enter "cat sh > su"
i get "cannot create su: directory nonexistent"......i know this is a red flag for my problem and im sure theres an easy fix......tried makdir and im denied access. ..I now have a headache and thanks for any help.....
reflash the rom. there was no need to asroot2 the shell.
Alright guys....Need help. How do I unroot from Super OneClick. I have the official TMobile 2.2 ROM as OTA..however it's failing because its checking to see if its rooted. Pleasant. So If someone could point me in the right direction it would be appreciated.
you sure its 2.2? OTA?
Yup. 100% Sure. 112MB file download. File is called Blur_Version.3.6.360.MB525.T-Mobile.en.US.zip with a Blur_Version.3.6.360.MB525.T-Mobile.en.US.crc file as well. Build.prop indicates that it is 2.2.1 /3.4.2-107-JDN-9/34.4.9. Getting completely hung up on this Status 7 error though. It is picky as hell, and I don't have a out of the box backup I can use to try as stock. It is definitely checking files though. It's like christmas and staring at your presents knowing what it is, but you can't unwrap it. Uggh!!
Root can't be your problem. I've updated to that release; Android 2.2.1, Blur 34.4.9, Build # 3.4.2.107_IDN-9, while my system was rooted. My phone was quite customized (Go Launcher with some "foreign" widgets and no Blur apps/widgets except for the Email app to get at my work e-mail) and everything came up OK. I was rather surprized how smoothly it all went. All my data (seemed to be mostly e-mail) had to be re-synched (this happened automatically), and it took one reboot to clear a message about non-Moto battery that was displayed after the first boot. Basically it all is where it was, except, of course, for root (I tried the latest, 1.7, SuperOneClick but it's looping no matter what I do).
Good luck.
[Added]
Well, well. It turned out that even though it seemed that SuperOneClick was failing (looping at trying to mount a partition R/O) it actually it did it's job! I just fired up RootExplorer and lo and behold a confirmation from Superuser for root popped up, got accepted, and I can start renaming the bloatware again. Woo hoo!
For me it ended up being the root. I was able to unroot with Z4root, and as soon as I did no more issues. I ended up saying screw it and wiped my phone all the way back to factory. Figure it's just better to rebuild it all cleanly and be done with it. I'm just happy its an official rom now.
mind posting a nandroid back up please?
It's really insane to sanction against rooting a phone. I can't image a computer denying me administrator's rights.
runeblade said:
How do I unroot from Super OneClick.
Click to expand...
Click to collapse
You can simply do it manually using Root Explorer. delete followings AS ROOT USER and reboot. that's all!
1. /data/data/com.noshufou.android.su
2. /system/app/superuser.apk
3. /system/bin/su & busybox
Also, it can be done via adb connection.
adb shell
$ su
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# rm -r /data/data/com.noshufou.android.su
# rm /system/app/superuser.apk
# rm /system/bin/su
# rm /system/bin/busybox
# reboot
I second this.
jboogie3 said:
mind posting a nandroid back up please?
Click to expand...
Click to collapse
all you need to do, is get the permission XML for from face camera device rom (used the one from VIVO), and push it system, via recovery.
adb reboot recovery; adb shell mount -a; adb push android.hardware.camera.front.xml /system/etc/permissions/; adb shell fix_permissions; adb reboot
done
....
PROFIT
PS: this is NOT a flashable zip. but anyone wants to make one, be my guest
thanks to Kali- for the tips
Pushed the xml to the permisions folder with no problems. Ran fix_permissions and rebooted, doesn't appear to have done anything. I can verify that the xml is in the correct folder but google + just doesnt want to do hangouts.
Nexus One running CM7
Any ideas?
EDIT: I was wrong, I thought I would be able to start a hangout but once I found an existing one I was able to join no problem. THANKS!
Qestion
Will it happen if you copy the "android.hardware.camera.front.xml" in folder "/ system / etc / permissions /" by Root Explorer, and then restart the phone?
jossna said:
Will it happen if you copy the "android.hardware.camera.front.xml" in folder "/ system / etc / permissions /" by Root Explorer, and then restart the phone?
Click to expand...
Click to collapse
Yes, you'll either need to manually change the permissions in root explorer to match all the other files in there, or run fix permissions as per the guide
Smtih said:
Yes, you'll either need to manually change the permissions in root explorer to match all the other files in there, or run fix permissions as per the guide
Click to expand...
Click to collapse
Thanks, I try it, but doesn't work
This is how I got mine to work
There were some permissions issues and my phone can't adb anymore for some reason (seems common with the Captivate), so I did the following from Terminal Emulator:
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock2
# chmod 777 /system
# cp /mnt/sdcard/Downloads/android.hardware.camera.front.xml /system/etc/permissions/.
# chmod 644 /system/etc/permissions/android.hardware.camera.front.xml
[Restart into recovery mode]
[Advanced]
[Fix Permissions]
And it worked! You just can't create your own Hangouts from the phone. You can join others though using your back-facing camera!
Thanks OP!
Jason Schoenbrun
jason schoenbrun gmail
-------------------
Why does xda developers require we create user names? If there's anyone who knows this, please let me know as I'm curious.
I haven't created a non-email username since the days of AOL. Now I have to make a dumb-sounding faux name like "hotmama2385" all over again? I really wish I could use my e-mail address as my persona. If I can't, at least I'd like to know out of curiosity why the design decision was made to exclude that possibility. of course as a protection from spambots I'd want some of my e-mail address hidden behind a CAPTCHA.
I know some people are privacy focused and/or want to be able to troll anonymously. So why not allow a username which can take whatever form we chose - AOL-esque IDs or an e-mail address - as most login services allow?
As an aside, I have the same question for Twitter, which is the reason I haven't signed up for it. I pushed off signing up for XDA by a couple of years until I absolutely had to because of this, and rarely log in because I can't remember that stupid username. (I just started to a little more because of LastPass.)
Nice work... I'll try this one...
hello,
how to fix permission?
with a terminal
I'm not sure what command that is specifically from a terminal, but you can type adb reboot recovery and then fix permissions via menu option once in recovery.
yep, but the problem I haven t a recovery mode. I want to say no menu.
I have an HTC evo 4g with CM 7.2RC1.
I implemented this fix, and rebooted, but still, when trying to do a video call, it stays on "video initializing" and never seems to finish. I have the latest skype from market.
What to do?
just maybe
So I installed the sdk tools, and opened cmd, and then cd to where adb is. I then copy and pasted the entire string "adb reboot recovery; adb shell mount -a; adb push android.hardware.camera.front.xml /system/etc/permissions/; adb shell fix_permissions; adb reboot" and pasted that into cmd is that all I do. I tried dong just "adb reboot recover" and waiting till it entered recovery, but then I couldn't do anything. after I pasted the entire string, my phone rebooted, and took a sec then started back up normally it seemed. So I think I did it correctly.
Perfect!!! Thanks, works like a charm on my Nexus One
great on arc s for hangouts
It's working great on arc s to create hangouts, but it still does not enable video chat in google talk.
I really don't understand why front camera is a pre-requisite for it. I shall be able to see at least the other's video if he has a front cam, even if they don't see me. Any way to workaround this issue of googletalk? (either to trick it to use front cam or just to display an empty frame, but receive other end's video).
I tried the same to see if it would work for Talk on my Defy, but no success
Hi,
i was trying to change the /system permissions using adb shell... commands shown in the attached screenshot
my main purpose was to install CWM for which we need to push modified recovery into /system/bin which requires rw permissions....
to do that i used the command chmod 6 /system from root and then tried to mv recovery file from sd root to /system/bin but that failed
when i checked the /system attributes using stat -c %A /system it returned "d------rw-"
after that i tried to mount the system from shell command but failed... then the phone got hanged and when i removed the USB cable it rebooted straight into recovery...
since the ive tried to check directory listing with adb ls /system command but it returns nothing... adb ls /data also shows only 3 files... i had taken a backup of /system using adb pull but i dont knw how much that'll help...
i did not take any backups before that... was trying to install CWM so that i could take rom backup....
im not able to boot the phone normally...
i would like to know if i can go back to original state?? if not is ther any other solution like flashing a new ROM or something...??
i would like to extract contacts nd messages if possible...
System config:
- Samsung Galaxy S 4G... everything stock
- Rooted!!
thanks in advance...
chi_visor said:
Hi,
i was trying to change the /system permissions using adb shell... commands shown in the attached screenshot
my main purpose was to install CWM for which we need to push modified recovery into /system/bin which requires rw permissions....
to do that i used the command chmod 6 /system from root and then tried to mv recovery file from sd root to /system/bin but that failed
when i checked the /system attributes using stat -c %A /system it returned "d------rw-"
Click to expand...
Click to collapse
'chmod 6 /system' did what you asked it to do. chmod, on a basic level, uses three (3) sets of permissions: global, group, and user. What you effectively did was set the user permissions to rw but blanked out everything else (like chmod 006).
If you can get into the shell, do this:
chmod 755 /system
That should put it back the way it was (7 = rwx for global, 5=rx for group, 5=rx for user)
See if that helps. Report back and let me know.
Real quick; I had my permissions backward. Although you still want 755 it should've read like this:
rwx for user
rx for group
rx for global
I had them backward.
Thanks stephen_w for ur reply...
I cant get into shell when i enter adb shell it throws this message
- exec '/system/bin/sh' failed: Permission denied (13)
any idea??
chi_visor said:
Thanks stephen_w for ur reply...
I cant get into shell when i enter adb shell it throws this message
- exec '/system/bin/sh' failed: Permission denied (13)
any idea??
Click to expand...
Click to collapse
I was worried about something like that. My guess is that your best bet is to see if you can get into download mode and flash a new ROM. Were you on Froyo or GB before? If you were on Froyo & you're trying to get to GB you'll need to insure you flash a ROM with the right boot loaders first, like chadster's KG4 (http://forum.xda-developers.com/showthread.php?t=1183413).
Let me know if I can be of help.
I was worried that I would have to flash a new ROM. Not that i mind doing it but ive not backed up anything!! I'd atleast like to see my contacts somewhere... let me know if that's possible...
So there's no other way to come out of this deadlock??
Im on Froyo... If its possible to roll back to stock Froyo it'll be great... If not i'll go for GB... Ive nothing against GB but i'd like to be sure everything works the way it was b4...
Its great to know you have and understanding of my problem... thanks mate...
chi_visor said:
I was worried that I would have to flash a new ROM. Not that i mind doing it but ive not backed up anything!! I'd atleast like to see my contacts somewhere... let me know if that's possible...
So there's no other way to come out of this deadlock??
Im on Froyo... If its possible to roll back to stock Froyo it'll be great... If not i'll go for GB... Ive nothing against GB but i'd like to be sure everything works the way it was b4...
Its great to know you have and understanding of my problem... thanks mate...
Click to expand...
Click to collapse
If your contacts were set to sync with Google or your carrier, then they will sync back to your phone after you flash. Given you were on Froyo, you can grab one of the Froyo ROMs from the bible (http://forum.xda-developers.com/showthread.php?t=1117554). Those will likely be rooted, deodexed, or something along those lines. If you want pure stock, you can grab that from samfirmware.com. You'll have to register to navigate to the firmware, though. I'd post a link but it wouldn't work right. Just go to the 'mobile' link and look for the SGH-T959V stuff. Either way, KD1 was the latest Froyo out there from Samsung.
Yup... I'll check on samfirmware.com..
sad abt contacts cuz dint sync the latest ones with google...
anyway i'll try the other method...
thanks..
Sorry man. Best of luck to you. Let me know if you get it fixed.
hi stephen_w,
I downloaded the T959VUVKD1 firmware from samfirmware.com....
I used odin to flash it...
after switchin on the phone in download mode... i flashed the firmware by browsing the file in PDA and leaving PIT, BOOTLOADER, Phone and CSC blank...
the process started and after cache.fs... below it was message:Complete(Write) operation failed.... it stopped nd showed fail in red...
i held the power key for a long time but then it started to show a phone linked to the computer with a yellow exclamation sign...
what does this mean?? im not able to boot into either recovery or download mode now...
please help...
ODIN will still see it when it looks that way, so don't fret! I had similar issues before but mine was a faulty download. Try using this one. It's not 100% stock as it's been deodexed, but it should work:
http://www.multiupload.com/7L5YDG8X8V
Ya im downloading tat one... Odin is detecting nd working... so i guess re-flashing should do the trick...
Jus to confirm I should leave fields other than PDA blank rite?
Yes, PDA only & let ODIN decide what should be checked.
Sent from my SGH-T959V using XDA App
Up and running jus like b4...
Thanks bro...
No worries; glad you're working again!
1. place the phone in download mode
2. open odin
3.download this file(https://www.dropbox.com/s/l96om7p00owmw0r/boot.tar.md5?dl=0) and place it in the ap section of odin
4.choose start
5.do the steps here http://galaxys7root.com/galaxy-s7-s...-attt-mobilesprintverizon-galaxy-s7s7-edge/3/
I only needed pages 3 and 4 because you need to use the files above instead!
6.Rooted
Please let me know if you have any issues!
activefan01 said:
Please let me know if you have any issues!
Click to expand...
Click to collapse
Is there a specific rom you need to do this on?
Edit: Don't bother the MD5 isn't going to work in Odin anyway as it's been modified and doesn't match.. Besides what makes you think the S7 is anything similar to the 5?
MrMike2182 said:
Is there a specific rom you need to do this on?
Edit: Don't bother the MD5 isn't going to work in Odin anyway as it's been modified and doesn't match.. Besides what makes you think the S7 is anything similar to the 5?
Click to expand...
Click to collapse
it always does that when i rename it idk why they get confusing when i leave them the same but here is the unrenamed file https://www.dropbox.com/s/l96om7p00owmw0r/boot.tar.md5?dl=0
finally i real developer. would this work on s6 edge plus?
warriorpluto said:
finally i real developer. would this work on s6 edge plus?
Click to expand...
Click to collapse
no but i can get it pm me the model number and build number
activefan01 said:
no but i can get it pm me the model number and build number
Click to expand...
Click to collapse
I got that kernel to go after so many tries but when you try to do root.bat it freezes the entire phone however I do have root access via adb shell from command prompt but that's it and when trying to issue the remount command on /system it freezes also.
that kernal should allow you to root what all steps did you do?
activefan01 said:
that kernal should allow you to root what all steps did you do?
Click to expand...
Click to collapse
I did everything you did.. Still freezes right when it tries to adb shell mount -o rw,remount /system and then you can't do nothing but reboot. Went back to stock backup already.
MrMike2182 said:
I did everything you did.. Still freezes right when it tries to adb shell mount -o rw,remount /system and then you can't do nothing but reboot. Went back to stock backup already.
Click to expand...
Click to collapse
How'd you go to stock backup? Does this seem promising?
tylerlawhon said:
How'd you go to stock backup? Does this seem promising?
Click to expand...
Click to collapse
It might be promising however I've been working on this all night and haven't gotten anywhere except for root access within command prompt. As soon as you type root.bat the first thing it does is adb shell mount -o rw,remount /system but the entire phone freezes! I can't seem to get past this freezing crap because you can't do anything with the phone when it freezes it.
MrMike2182 said:
It might be promising however I've been working on this all night and haven't gotten anywhere except for root access within command prompt. As soon as you type root.bat the first thing it does is adb shell mount -o rw,remount /system but the entire phone freezes! I can't seem to get past this freezing crap because you can't do anything with the phone when it freezes it.
Click to expand...
Click to collapse
If it's giving you root access in a terminal, could you not push the root files that way? Or do you have to remount to do that? I honestly don't know is why I ask. Would love to root this beast, but I'm not a lot of help with the more deep down technical stuff.
tylerlawhon said:
If it's giving you root access in a terminal, could you not push the root files that way? Or do you have to remount to do that? I honestly don't know is why I ask. Would love to root this beast, but I'm not a lot of help with the more deep down technical stuff.
Click to expand...
Click to collapse
You have to remount the system as writable otherwise trying to write a file to system doesnt work, and as soon as I issue the command adb shell mount -o rw,remount /system then phone just freezes but I'm looking into an answer for that but no luck so far.
MrMike2182 said:
You have to remount the system as writable otherwise trying to write a file to system doesnt work, and as soon as I issue the command adb shell mount -o rw,remount /system then phone just freezes but I'm looking into an answer for that but no luck so far.
Click to expand...
Click to collapse
What is it supposed to do? Is it supposed to reboot? I might be open to trying on mine.
tylerlawhon said:
What is it supposed to do? Is it supposed to reboot? I might be open to trying on mine.
Click to expand...
Click to collapse
No it's supposed to remount the system as writable because I need to be able to push su into /system/xbin but when I try to it gives me the error system READ only which means I cannot write to it. And if I were you be prepared to lose everything and factory reset in the end otherwise it's not going to hold no WiFi passwords or nothing every time I reboot I need to rein put all the WiFi crap and it's getting annoying.
MrMike2182 said:
No it's supposed to remount the system as writable because I need to be able to push su into /system/xbin but when I try to it gives me the error system READ only which means I cannot write to it. And if I were you be prepared to lose everything and factory reset in the end otherwise it's not going to hold no WiFi passwords or nothing every time I reboot I need to rein put all the WiFi crap and it's getting annoying.
Click to expand...
Click to collapse
I'm pretty much where you are at. I don't think DM-Verify is turned off in the kernel but it is a eng one. If you get tired of it just flash the boot.img below and you will be back to normal. It says PI1 but it should work fine if you are on MM. I flashed it on PL4 no problem.
View attachment 4004361
Misterxtc said:
I'm pretty much where you are at. I don't think DM-Verify is turned off in the kernel but it is a eng one. If you get tired of it just flash the boot.img below and you will be back to normal. It says PI1 but it should work fine if you are on MM. I flashed it on PL4 no problem.
View attachment 4004361
Click to expand...
Click to collapse
Yeah I already flashed back but apparently I'm going to have to factory reset again anyway because after flashing the original kernel it still won't keep my WiFi passwords saved and I have to keep redoing it.
---------- Post added at 12:35 PM ---------- Previous post was at 12:26 PM ----------
I'm curious as to why the file system would deny me to mv su from my sdcard into /system/xbin when I'm ROOT... But if I so much as try to mount it as re writable it freaks out and freezes. But I can adb shell mount -o rw,remount / and adb shell mount rw,remount rootfs / with no issue but just that /system absolutely will not.
MrMike2182 said:
Yeah I already flashed back but apparently I'm going to have to factory reset again anyway because after flashing the original kernel it still won't keep my WiFi passwords saved and I have to keep redoing it.
---------- Post added at 12:35 PM ---------- Previous post was at 12:26 PM ----------
I'm curious as to why the file system would deny me to mv su from my sdcard into /system/xbin when I'm ROOT... But if I so much as try to mount it as re writable it freaks out and freezes. But I can adb shell mount -o rw,remount / and adb shell mount rw,remount rootfs / with no issue but just that /system absolutely will not.
Click to expand...
Click to collapse
I feel like it's infuriating because root is right there but just out of reach. I've been using my m8 because I have root and my screen is peeling on my note, so if someone wants to shoot me some instructions, I can see what I get.
tylerlawhon said:
I feel like it's infuriating because root is right there but just out of reach. I've been using my m8 because I have root and my screen is peeling on my note, so if someone wants to shoot me some instructions, I can see what I get.
Click to expand...
Click to collapse
I really don't think you should try right now considering that both myself and @Misterxtc know what we're doing already and there really isn't much point in trying to give instructions out just to end up in the same exact situation we are.
And by the way, there is root. It's just in the console that's it!
By the way you can adb pull the /efs/carrier/HiddenMenu from the phone to your computer and change it and then push it back and then viola secret codes in the phone dialer work such as *#0*# and many others! If you do change it reboot before it'll take effect. Also it will remain this way even with doing a factory reset.
Misterxtc said:
I'm pretty much where you are at. I don't think DM-Verify is turned off in the kernel but it is a eng one. If you get tired of it just flash the boot.img below and you will be back to normal. It says PI1 but it should work fine if you are on MM. I flashed it on PL4 no problem.
View attachment 4004361
Click to expand...
Click to collapse
I tried doing adb shell mount -o rw,remount /system /system and I get permission denied as root.. wth?