Hi Guys,
I dont know what happened, but all of a sudden I cannot move or copy any files with the stock browser. When I try android zip is says cannot move file due to system restriction. Phone is rooted with Gingersnap V1.2 with Darkside Kernel.
The last thing I did was try an app called undelete. Where are the restriction settings and what could have changed them?
Sounds like you need to root again. That restriction deal is something that would pop up if you weren't rooted.
Sent from my HTC Vision using xda premium
So you can loose root sometimes?
highlander07422 said:
So you can loose root sometimes?
Click to expand...
Click to collapse
Not on our device. Loosing root happens when your device has a locked bootloader like motorola & htc devices. There are programs for those devices that will give you temporary root access which goes away after a re-boot.
Samsung kicks ass because they do not lock their bootloaders. Once you install a custom rom (all custom roms come with default SU access), or use zergrush superoneclick exploit, you will have permanent root/SU access.
jordanishere said:
Not on our device. Loosing root happens when your device has a locked bootloader like motorola & htc devices. There are programs for those devices that will give you temporary root access which goes away after a re-boot.
Samsung kicks ass because they do not lock their bootloaders. Once you install a custom rom (all custom roms come with default SU access), or use zergrush superoneclick exploit, you will have permanent root/SU access.
Click to expand...
Click to collapse
If I remember correctly, I had the same problem. I was trying to move a downloaded rom to the external sd and it wouldn't let me. I'm 90% sure I was also using the darkside kernel with the Tuesday rom.
Now I have the darkside rom with faux kernel and I have no problem moving files. I think we can assume what the problem might be. Try a different kernel
Not sure why I quoted you Lol
Thanks guy's. I will look for and try the faux kernel.
wierd though, just happened out of the blue.
Related
I've been trying to root my G2 since last night, and before I start, I have to say I do NOT and WILL NOT have access to adb. Some drama with my father caused him to revoke my administrator privilages on all the computers in my house. So I can't install anything or run any unknown .exe's.
The only way I can go about this is using Visionary so far. However, it's been a piece of crap up to this point. I have +r14, USB debugging enabled. Regardless of whether I check "Set system to r/w after root", I always get the same two results when i hit Temproot.
Sometimes it'll go through a couple of triangle screens w/ "rooting device, please wait" and then go back to the main option screen. However, this seemed to do nothing but install Superuser with NO APPS requesting su permissions. After this I'll try to hit "Attempt Permroot now" and it will say "Please Temproot before attempting Permroot". "Unroot now" just says my device isn't rooted. >_> Going into terminal and typing "su" gives me a "su: Permission denied".
Other times when I hit Temproot, it'll go through a few triangle screens, and then just stop on a black screen with only the status bar visible. I can still Home out and use the notification bar and such though, so it's not a total system freeze.
Can someone please help me out here? I ordered my phone on 2/4/11 and got it maybe a week later if that makes any difference, because I've been hearing some things about people not being able to use Visionary on newer phones.
Try using this GUDIE HERE. No ADB needed.
I've tried that guide and one of the two scenarios I provided always happens. :\
I got my phone brand new from the tmo corp store sat night and I had no problem with rooting via visionary and gfree.
Mine did not have that 1.72 update tho. Maybe that's your problem.
From my permarooted overclocked HTC G2 with cyanogen 7 nightly via XDA app
tackleberry said:
I got my phone brand new from the tmo corp store sat night and I had no problem with rooting via visionary and gfree.
Mine did not have that 1.72 update tho. Maybe that's your problem.
From my permarooted overclocked HTC G2 with cyanogen 7 nightly via XDA app
Click to expand...
Click to collapse
Tmobile phones don't get the 1.72 updates, that's only for the desire Z's, Tmobile G2's only have the 1.19 or the 1.22 OTA roms on it.
Sent from my HTC Vision using XDA App
How do I check what update I have? (I heard having Wifi tethering and Wifi calling affects that, I have both)
legendaryxm90 said:
How do I check what update I have? (I heard having Wifi tethering and Wifi calling affects that, I have both)
Click to expand...
Click to collapse
If you have wifi calling and tethering built-in, then you have the 1.22 OTA update already (I think all of the newer G2's come with it). I'm not sure if it shows up anywhere you can check easily, but I do know the OTA came with a newer radio so you could check in your Settings->About phone. The baseband version should end in something like 26.03.02.08.
The version number is also stored on partition 17, but I don't think you can check that without at least temp root. Not positive though.
I have no idea why Visionary is having problems even temp rooting your phone. One problem may be that you tried the permroot function within it (I don't know what it does, but many users have reported strange behavior when it doesn't work right).
Maybe you can try doing a factory reset and then starting again. Also, you might want to try disabling all of the added functionality in Visionary (such as temp rooting or setting system as R/W on boot), restarting the phone, and then trying the temp root again. Or uninstalling Visionary and then reinstalling it.
If you can just get su to work in terminal, then you should be okay.
joemm said:
Tmobile phones don't get the 1.72 updates, that's only for the desire Z's, Tmobile G2's only have the 1.19 or the 1.22 OTA roms on it.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
me=de de dee! lol. thanks for that info. i didnt know that specific detail.
Ok, so I just factory reset my phone, and I'm going to try this with a fresh downloaded r14. Gonna try with no options checked. Also, is it better to do this with the phone connected to the computer or not?
EDIT: OK here's what I was talking about. -_- Just tried it TWICE. First time it went back to the option screen, Terminal gives me su: permission denied again. Did it a second time. Currently stuck on a black screen w/ only status bar visible. WTF IS GOING ON MAN.
legendaryxm90 said:
Ok, so I just factory reset my phone, and I'm going to try this with a fresh downloaded r14. Gonna try with no options checked. Also, is it better to do this with the phone connected to the computer or not?
EDIT: OK here's what I was talking about. -_- Just tried it TWICE. First time it went back to the option screen, Terminal gives me su: permission denied again. Did it a second time. Currently stuck on a black screen w/ only status bar visible. WTF IS GOING ON MAN.
Click to expand...
Click to collapse
Not sure what's happening. How long are you waiting on the blank screen? I've seen some people say the temp root took a while on their phones. I saw in one of the forums (maybe dev), someone posted another app that can achieve temp root as well. Might be worth taking a look...
I waited 15-20 minutes and nothing. >_> I'll look for that other app because I just read somewhere that VISIONary doesn't work on the latest OTA phones. Is that true?
EDIT: Haven't found anything. Is there ANY hope for me without adb? :<
Here's the other temp root program someone mentioned: http://forum.xda-developers.com/showthread.php?t=951208
Never tried it myself but maybe it'll work for you.
Also, I think the thing about Visionary not being compatible for OTA phones was only for the permroot option. Like I said, people have reported really strange behavior when it doesn't work.
Just thought of another thing to try. Maybe clear the data for the superuser app. Hopefully when you try su in terminal then, it'll pop up with the dialog box asking for permissions again.
ianmcquinn said:
Just thought of another thing to try. Maybe clear the data for the superuser app. Hopefully when you try su in terminal then, it'll pop up with the dialog box asking for permissions again.
Click to expand...
Click to collapse
D'OH. THAT DID IT. Got the superuser popup!
THANK YOU SO MUCH!! +REP
See & discuss here please:
http://forum.xda-developers.com/showthread.php?t=1886460
Regards
Bin4ry said:
See & discuss here please:
http://forum.xda-developers.com/showthread.php?t=1886460
Regards
Click to expand...
Click to collapse
I rooted my phone succesfully and I've got the Superuser app, but when I try to use the lucky patcher or Titanium backup, it says: "No root acces found!"
crane75 said:
I rooted my phone succesfully and I've got the Superuser app, but when I try to use the lucky patcher or Titanium backup, it says: "No root acces found!"
Click to expand...
Click to collapse
i think you have to install busybox (find it in playstore) for this.
Regards
Do I need to unlock the boot loader first? Because this didnt work for me.
Edit: 5th time rebooted, tried again, it worked!
failed on my lt26i
It works on all Lt26.
Be sure you have all drivers instaled properly and you are connected DIRECTLY to your pc, no usb-hubs etc.
Regards
Bin4ry said:
It works on all Lt26.
Be sure you have all drivers instaled properly and you are connected DIRECTLY to your pc, no usb-hubs etc.
Regards
Click to expand...
Click to collapse
a small problem, i rooted the phone, everything goes perfectly fine until the script hangs after push su and superuser.apk to the phone. Phone runs very very slow. I have to stop the script manually then reset the phone. root was installed but i couldn't see Data dir with Root Explorer...
something wrong?
ok i retried completely with success.. cool thing, please stick it .) thanks
Worked like a charm... This is really awesome... Thanks guys,,,
Sorry for asking this but i really new to android. Had iphone previously.
What to do next after rooting? Do we have any good custom kernels? And how do i get CMW? Is it necessary?
Thanks aloot
guyderam said:
Worked like a charm... This is really awesome... Thanks guys,,,
Sorry for asking this but i really new to android. Had iphone previously.
What to do next after rooting? Do we have any good custom kernels? And how do i get CMW? Is it necessary?
Thanks aloot
Click to expand...
Click to collapse
SetCPU is probably interesting for you
worked like a charm phone is rooted finally i was waiting for this big button root
how do i install recovery and flash any rom without unlocking my bootloader i am new to xperia family plz help binary
SIM lock?
I rooted my phone using the initial method (I couldn't wait) and flashed CM9. My bootloader is unlocked and I have been running it for about a week. The mobile network is always alternating between airplane mode so I have no service at any time. I fixed it before but I can't remember how. I backed up my system at two different points (while the problem was fixed and I had service). But when I restored them, I face the same problem with the network. Any help?
Working on S and probably acro S
hey all, im on stock jellybean for my s3. all my friends have stock s3's for verzion, atnt and metroPCS. in thier camera app they all have an option to turn shutter sound off, but i dont! is there a way to turn the shutter sound off on sprint s3?
believe it or not i believe its a sprint thing. Are you rooted?
no i am not rooted, but little things like this makes me want to root; -_-
i may have a soulution if you aren't down for rooting. need a few mins
Yeoi can change the shutter sound file if you root.
Though if there is an option without root I'd be interested.
Sent From My Galaxy S3 With XDA
NO ROOT CAMERA POST + IMPORTANT INFO MOVED HERE
http://forum.xda-developers.com/showpost.php?p=39523970&postcount=102
Gonna do that when I get home. Thanks!
Sent From My Galaxy S3 With XDA
billard412 said:
Extract and flash in PDA slot of odin. http://www.androidfilehost.com/?fid=9390202682628636748
Wont change anything. wont up the flash count. Will just add the camera shutter toggle
Click to expand...
Click to collapse
how do i flash it if im not rooted?
You do not need root access to use odin. Just plug the phone into pc in download mode, and run odin.
I for the life of me can't remember how to get to the file to pull the shutter sound, I'm rooted and have ROM toolbox. Would someone mind refreshing my memory please? I'd appreciate it.
xTMFxOffshore said:
I for the the life of me can't remember how to get to the file to pull the shutter sound, I'm rooted and have ROM toolbox. Would someone mind refreshing my memory please? I'd appreciate it.
Click to expand...
Click to collapse
Assuming your on touchwiz jellybean go to /system/csc/ and open feature.xml
Find the line that says
<CscFeature_Camera_ShutterSoundMenu>false</CscFeature_Camera_ShutterSoundMenu>
And change to
<CscFeature_Camera_ShutterSoundMenu>true</CscFeature_Camera_ShutterSoundMenu>
So galaxy s3 nooby for the root world of this device, what will happen if I flash that? Will my info be wiped or mess up my phone to the point I can't update ota for future updates or what? I want my phone to be stock unrooted and function normal and not messed up. I'm not going to blame anyone if something happens although it's not their fault. I just would like to know what exactly will happen to my phone and if anyone can verify that flashing this via Odin in that one slot will in fact only add an option to camera
ReapersDeath said:
So galaxy s3 nooby for the root world of this device, what will happen if I flash that? Will my info be wiped or mess up my phone to the point I can't update ota for future updates or what? I want my phone to be stock unrooted and function normal and not messed up. I'm not going to blame anyone if something happens although it's not their fault. I just would like to know what exactly will happen to my phone and if anyone can verify that flashing this via Odin in that one slot will in fact only add an option to camera
Click to expand...
Click to collapse
thats all it does. period. wont mess up ota's. wont add root. changes nothing but camera sound toggle option. And sorry to anyone that downloaded first link. androidfilehost sucks-another incomplete upload. Heres a new link http://forum.xda-developers.com/showpost.php?p=39523970&postcount=102 . its an odin one click just extract and run
In my opinion, if you are afraid of root, then you shouldn't be using odin. Changing the camera sound settings requires changing the phone's system files - i.e. it requires root access. odin accesses and changes the root files. I used odin to root my phone.
so if you want to change such details about your phone, you will need to make a decision...
In my opinion, if you are afraid of root, then you shouldn't be using odin. Changing the camera sound settings requires changing the phone's system files - i.e. it requires root access. odin accesses and changes the root files. I used odin to root my phone.
so if you want to change such details about your phone, you will need to make a decision...
Click to expand...
Click to collapse
theres nothing wrong with odin. its stupid comments like this that scare people away from customizing their ****.
Samsung didnt make odin for people to root with, it is made to restore a phones firmware. That is what this is doing. Its a stock system with no root. root is not needed to use it. OTA's WILL NOT be affected. I did this with ICS and the JB ota went down just fine. So you dont need to "make a decision."
Billard. I am bone stock JB. Minus root obviously. I will do that. Thanks.
Update: I changed it to true and no go. Still has sound. Changed false to true and saved it in root explorer. Ideas?
Sent From My Galaxy S3 With XDA
Go to system/media/audio/ui/ and rename the file "shutter.ogg".
Not as elegant as a menu option, but this at least disables the sound.
Sweet deal. I just changed it to shut.ogg, and it worked fine. Thanks. :good:
xTMFxOffshore said:
Billard. I am bone stock JB. Minus root obviously. I will do that. Thanks.
Update: I changed it to true and no go. Still has sound. Changed false to true and saved it in root explorer. Ideas?
Click to expand...
Click to collapse
when you changed the value to true did you reboot after or did you try to go straight to the camera?
Oops. Just straight to camera. I'm smart....lemme try that. Thanks. Haha.
Okay, so I rebooted twice, and double checked, I have the value changed to true, and it still has shutter sound. So I'm gonna just change the shutter.ogg file again.
Sent From My Galaxy S3 With XDA
So I am a well seasoned samsung vet. I had the vibrant the s2 I curently have the note 2 running the latest cm 10.1 nightliy and now I am the proud owner of a brand new s3 Yay. So I was wondering if this is the same as the note 2 as far as design across carriers and software across carriers. Can we use att roms without port or kernel changes? Are the AOSP roms identical? I havent looked yet but I assume that all I got to do is use odin to install twrp or cwm and then I can install su and root. Also It came with jb 4.1.1 the build number is t999uvdlja. Is that the latest build? every time i check for an update it tells me i have to wait in line. not word for word but that is what it is telling me. I have never seen that. So I am just wondering if I am up to date. I dont know if I will be doing any heavy modifications because it is my girls phone so I might just root it and leave it at that.
You practically up to date. There was a newer base pushed but very minor changes. If anything, you can always flash the new modem that came with it to try it out for better results.
You are right about the root process
You can use att builds... Just may have to edit build.prop to make it say t999 and not t747
Enjoy
Sent from my SGH-T999 using Tapatalk 2
Thanks for the quick answer galaxys3guy I have one question about the root process. On the newer android builds like what came on my note2 there is a built in fail safe that automatically rewrites the stock recovery. So 1. has that been implemented on the latest jb builds on this phone? And if so how do we get around it? When I went to root my note 2 I actually was able to use the exploit that samsung screwed up. If I remember corectly that exploit was originally found on the s3 but I know that samsung recently updated the nate2 so I would assume they updated the s3 to patch the exploit. So the only other way is to A install a custom rom with root via odin or use ADB to disable that function that rewrites recovery. I looked around and didnt see much about rooting for this phone. So what I think I will do is use chainfire's autoroot. Then flash twrp via odin and be done with it. But I was just wondering about the workarounds. As you can probally tell I only half know what I am talking about. I am self taught so sometimes things just dont make sence to me when they should it takes me a while but I usually get it.
Lol I'm glad u know half of what u are talking about cuz I don't
All I did... Was booted into download mode... Put twrp in the PDA section of Odin, and flashed the recovery. (After it was done... If I remember right, I had to unplug and manually reboot because something with Odin was not working... But that was just for me... So if u have that issue where your phone won't boot after it says pass, just unplug and reboot urself). From there I booted into recovery and flashed supersu...
Sent from my SGH-T999 using Tapatalk 2
Hey congrats on New gs3 bro!
I kind of went thru something similar to your rooting proces.
You should check out galaxys3root.com. it is super helpful site. basically when you run Odin to root ( installing custom recovery like cwm or twrp, ) you need to uncheck all tick boxes especially auto-reboot and F.reset time buttons. Otherwise phone will reboot and reinstall stock recovery and in some case stuck on boot.. when you un-check them phone will not reboot after installing. You just pull battery after install and boot into custom recovery by volume+ , home and power together. I'm afraid there no patch that I know of ATM. Good luck..
Sent from my PG41200 using xda premium
Thats what I meant ^^^
Thanks man
Sent from my SGH-T999 using Tapatalk 2
GalaxyS3Guy said:
Thats what I meant ^^^
Thanks man
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I did have a problem with my T-Mobile branded S3 going back to stock recovery and found there are 2 files that need to be renamed using the file explorer of your choice.
install-recovery.sh located in the /system/etc folder
recovery-from-boot.p located in the /system folder
I just add a .bak to the file name. Once this is done install CWM again and it will be OK. Also of note it will trip the counter built into the phone every time CWM is used. Download Triangle Away from the market to reset the counter when needed.
okay Now I see. So One way to fix this is to uncheck everything in odin so that the phone doesnt reboot itself. Then pull the battery and reboot into recovery right away and that will somehow overide the rewrite process.
But GTwalling I have q question. Do you need to be rooted to rename those files? Or does the security leak make that not matter? I know that the leak basically makes one of the partitions read-write when it should be read only. I am almost positive that the last update that you guys got would have patched the exploit because it did with the note2. But in any case basically I would go into /system/ect folder then find the file: install-recovery.sh then rename that file so it should look like this when done install-recovery.sh.bak then do it with the other file as well. Is that right? basically all you are doing is making the file not run without deleting it. Cool. I just learned something. It seems like the peope in this fourm are cool and helpful. Maybe I will learn alot here.
Another thing I noticed that there is a toolkit from mskip I think. I know he does good work from his toolkit for the s2. Maybe there is a way to use his tool kit to disable that rewrite process. The one for the note2 has that feature but it is not made by mskip he actually wanted to make one and posted in the general fourm for ideas and a bunch of the idiots that are in that fourm were like we have one already and we dont need another. I tried to encurage him to make one and not listen to those idiots but It never came to be. But i'm sure if I msg him and tell him he can put that in if it isnt already. I personally dont like to use toolkits because I want to do everything myself but I also think they are a way of the future. Alot of people just want to point and click to do things and dont want to know what the whole thing is.
I'm on 4.4.2 and rooted/s-off. Not interested in the 4.4.3 update (I'm going to flash a 4.4.4 rom soon). How do i stop this notification from appearing every time i turn my phone on?
MrShickadance9 said:
I'm on 4.4.2 and rooted/s-off. Not interested in the 4.4.3 update (I'm going to flash a 4.4.4 rom soon). How do i stop this notification from appearing every time i turn my phone on?
Click to expand...
Click to collapse
I read something about renaming the otacerts.zip file to something like otacerts.zip.bak OR move it to an entirely different spot(External SD Card) OR delete it. As apparently that is what gives the notifications. Afterwards you'll have to do the update(It'll refuse to run, no info file available) and then just clear it, you won't see it again.
If I recall right on what I read though, been a couple of weeks since then, somebody else wanted to know on here as well. Just look into it and do some search
Oh and it'll be the /system/etc/security/otacerts.zip file
BerndM14 said:
I read something about renaming the otacerts.zip file to something like otacerts.zip.bak OR move it to an entirely different spot(External SD Card) OR delete it. As apparently that is what gives the notifications. Afterwards you'll have to do the update(It'll refuse to run, no info file available) and then just clear it, you won't see it again.
If I recall right on what I read though, been a couple of weeks since then, somebody else wanted to know on here as well. Just look into it and do some search
Oh and it'll be the /system/etc/security/otacerts.zip file
Click to expand...
Click to collapse
Thanks. I had searched, but couldn't find anything helpful. I guess I have another question. Can i just let it update? Will my phone blow up into a million pieces and/or turn into a brick?
MrShickadance9 said:
Thanks. I had searched, but couldn't find anything helpful. I guess I have another question. Can i just let it update? Will my phone blow up into a million pieces and/or turn into a brick?
Click to expand...
Click to collapse
Why would it "blow" up or turn into a "brick"
If you're concerned about the S-OFF and being Rooted, it has no effect on the OTA. You just need to make sure that you have stock ROM i.e didn't flash a custom ROM(ARHD, Viper etc) and that you have stock recovery.
Being S-OFF or rooted won't prevent the OTA, after the OTA though you will lose root, but you can root again by just booting Philz custom recovery and flashing the root .zip like before.
BerndM14 said:
Why would it "blow" up or turn into a "brick"
If you're concerned about the S-OFF and being Rooted, it has no effect on the OTA. You just need to make sure that you have stock ROM i.e didn't flash a custom ROM(ARHD, Viper etc) and that you have stock recovery.
Being S-OFF or rooted won't prevent the OTA, after the OTA though you will lose root, but you can root again by just booting Philz custom recovery and flashing the root .zip like before.
Click to expand...
Click to collapse
i was joking around.... thanks though!
solved disable ota update notification
In order to use this. you should be rooted with superuser rights for this app.
Download "Disable Service" app from play store. (sorry xda doesnt allow me to share the link for the app as i have posted less than 10 post)
Install app and open it.. Go to System App - check systemupdateservice...... then close the app.
Click on the system update notification and press install and then back button. Then restart your mobile..
This method will stop the notification after the restart.