Hi guys I'm new in this forum but I've seen it and followed it for a thousand times and now I'm gonna be part of it, so HI GUYS xD.
Well to start I've to say that after I rooted the device and so on, I decided to change the famous:
Lock.ogg
LowBattery.ogg
Unlock.ogg
Well I started using "Es explorer" and then I realized that I couldn't just copy paste and overwrite those file with my gallery OF: MGS
-I can't post the link after 10 POST xD-
- Well then I used "Root Browser" to do it and I could without any problem.
- I restart the device and didn't sound anything when I try to lock and unlock the device.
- I realized that "Root Browser" did change some permissions and then I changed them to leave it how it should. NEW
- I restarted again my device and nothing happen..........
- Then I replace them for the originals leaving the device how it was before working.
But now is not working when I lock or unlock the device why I rebooted several times so...
Can someone help? did I do something wrong or what? this is very weird....
I've fixed it in SETTING DEVICE SOUND UNLOCK SOUND...
Sorry guys I didn't see it.
Related
THIS GUIDE HAS BEEN REDONE. PLEASE VISIT THIS THREAD:
http://forum.xda-developers.com/showthread.php?t=761819
Just reading through the document now, seems the first link, http://www.soft‐go.com/get/Samsung‐Kies_79632.html isn't working. Not sure if the site is just down right now or if there's a mistake.
Rad_Fishy said:
Just reading through the document now, seems the first link, http://www.soft‐go.com/get/Samsung‐Kies_79632.html isn't working. Not sure if the site is just down right now or if there's a mistake.
Click to expand...
Click to collapse
Thank you I didn't actually add that link it was from systoxity, but i will fix it.
nbs11 said:
Thank you I didn't actually add that link it was from systoxity, but i will fix it.
Click to expand...
Click to collapse
I Fixed it
A few small things:
Intel should be intel.
Under CPU Optimization:
"Samsung’s CPU is set by default the run at 1gHz."
The should be to.
Sideloading:
"(don’t forget that after you install it from the market you still have to go to your app drawer and run busybox once so it installs)."
Should this be after you download it from the market?
ClockworkMod Recovery:
"ClockworkMod written for us by a developer that goes by the name of Koush"
Missing is.
"This gent puts a ton of work into helping us captivate owners out"
Replace puts with put and Capitalize Captivate.
Changing Your Messaging Ringtone:
"well the ones that matter anyway.."
Extra period.
Other than that, excellent guide. I'll definitely be using it when my Captivate arrives.
Rad_Fishy said:
A few small things:
Intel should be intel.
Under CPU Optimization:
"Samsung’s CPU is set by default the run at 1gHz."
The should be to.
Sideloading:
"(don’t forget that after you install it from the market you still have to go to your app drawer and run busybox once so it installs)."
Should this be after you download it from the market?
ClockworkMod Recovery:
"ClockworkMod written for us by a developer that goes by the name of Koush"
Missing is.
"This gent puts a ton of work into helping us captivate owners out"
Replace puts with put and Capitalize Captivate.
Changing Your Messaging Ringtone:
"well the ones that matter anyway.."
Extra period.
Other than that, excellent guide. I'll definitely be using it when my Captivate arrives.
Click to expand...
Click to collapse
Thanks! I fixed all those errors but I'm not gonna upload the new version just yet because I will keep finding more errors so it just seems wasteful. I did not actually write most of the guide myself I just formatted it so there may be some mistakes I didn't pick up on.
i used this guide today and it delivered.
orlandoxpolice said:
i used this guide today and it delivered.
Click to expand...
Click to collapse
If there was anything you found difficult or anything you would like to change just tell me and I will add it to tonight's update.
Hi,
Thanks for publishing this. It looks very useful, similar to Energy ROM.. But I am very new to Android phones (trying this on Samsung Captivate from AT&T, bought yesterday). I am running windows 7 ultimate 64bit and I exactly followed this guide. But somehow I am still not able to see the sd card. I tried placing the update.zip at Computer\SGH-I897\Phone and shut down the phone and tried restarting the phone by holding the up/down keys as well as power button. But after selecting reinstall packages it said could not find /sdcard/update.zip.. Pls held. Again very sorry if I did some mistake..
ask_j said:
Hi,
Thanks for publishing this. It looks very useful, similar to Energy ROM.. But I am very new to Android phones (trying this on Samsung Captivate from AT&T, bought yesterday). I am running windows 7 ultimate 64bit and I exactly followed this guide. But somehow I am still not able to see the sd card. I tried placing the update.zip at Computer\SGH-I897\Phone and shut down the phone and tried restarting the phone by holding the up/down keys as well as power button. But after selecting reinstall packages it said could not find /sdcard/update.zip.. Pls held. Again very sorry if I did some mistake..
Click to expand...
Click to collapse
The SD card is simply the root directory of your phone. You do not need to open a folder, it is the highest folder you can place it in. Hope that helps
Somehow it was not able to find the sdcard root. Then I realized that you mentioned something called as Droid Explorer, I searched for it and installed it on my PC. But when I opened Droid Explorer, my device was not recognized, then I clicked on link on the explorer window, upon watching that video I enabled the USB Debugging, then I was able to see my device, then I selected connect to my device. After that I saw an explorer but it had empty root and I was not able to copy anything. There was a menu button at the top row named "Transfer to device or Copy to device" I selected that and selected update.zip file and tried to transfer. Something happened but still explorer was empty. Then from my phone Top slide down menu I selected mount USB storage and I started seeing windows explorer on my PC. Then apart from other folders I could see a folder sd in the root. Then I again put update.zip in the root.
Then followed the restart sequence, this time it found the file but exited after Signal 7. It was trying to asert something but could not find the correct model number I guess. My cell phone's model number is Samsung i897.
Please help
ask_j said:
Somehow it was not able to find the sdcard root. Then I realized that you mentioned something called as Droid Explorer, I searched for it and installed it on my PC. But when I opened Droid Explorer, my device was not recognized, then I clicked on link on the explorer window, upon watching that video I enabled the USB Debugging, then I was able to see my device, then I selected connect to my device. After that I saw an explorer but it had empty root and I was not able to copy anything. There was a menu button at the top row named "Transfer to device or Copy to device" I selected that and selected update.zip file and tried to transfer. Something happened but still explorer was empty. Then from my phone Top slide down menu I selected mount USB storage and I started seeing windows explorer on my PC. Then apart from other folders I could see a folder sd in the root. Then I again put update.zip in the root.
Then followed the restart sequence, this time it found the file but exited after Signal 7. It was trying to asert something but could not find the correct model number I guess. My cell phone's model number is Samsung i897.
Please help
Click to expand...
Click to collapse
I did not write the PC instructions, so I can not help you (I only have a Mac). But the person who did can probably help you his username is systoxity.
Because not enough errors were found to make it worthwhile to update the PDF i will wait till tomorrow to fix the minor errors.
Good source of information
Thank you for putting this together. I am going to sticky this for the time being.
For installing the latest version of busy box, you should include that before the instructions for running titanium backup...the latest version of busybox installed from the market will work with titanium backup so theres no need to have to click the "problems" button...this way you wont have to do the busybox download step twice...should also save a few megs since titanium backup wont have its own copy of busybox installed BTW nice guide
You can also just mount the phone memory using windows explorer and move the file over. I was never able to get droid explorer to transfer the file. It always said it went but then was never there.
Anyway all I did was connected just as I was going to connect to kies but then when windows asked me what I wanted to do I clicked on open file view and dropped updated.zip on my phone.
Only issue that I had with rooting was I accidentally opened the file in windows(winrar). After I moved the file over it found it and attempted to install it but then exited with an error(do not remember exact error), but had to do with mounting. Anyway I re-downloaded file and saw file size was different. After I moved the file over again everything went great. I still haven't removed bloat-ware and such but thats next on the agenda.
Also I was on windows 7 64 bit, saw some other users in other threads saying they had issues connecting the phone. Everything so far has worked great for me
Thank you very much for this handy pdf file!
Somelinks aren't working
First of all I have to say very good guide for noobs!
1. when I downloaded the update.zip folder I didn't work I guess because the name of Samsung captivate is not in the folder or something. So I just downloaded the other file from the forums.
2. Link to CPU optimization doesn't work.
3. I downloaded the droid explorer. It connected to my phone but I was unable to transfer anything. So I just tapped on the USB connected in the notification bar and mounted the phone. This allowed me to use windows explorer to transfer files. I believe one can transfer files by selecting the option of Samsung Kies under USB settings.
I got all your feedback. It will all be corrected by tomorrow night.
Cool guide however the rumor is the GPS only gets turned on when pulling up an App that uses it, so that step in the "battery saving" section might not be necessary.
Also you may want to replace Market Enabler with Market Access. It's a rehash of Market Enabler but also has a Set on Boot option that keeps it persistent versus being reset each time.
You also Might want to add a Tips/Tricks Section..
Here You can put some cool tips like the one i found out about backlight control.
(found here: http://forum.xda-developers.com/showthread.php?t=735394 )
Greetings fellow "Androiders"
I have a Galaxy S running Froyo 2.2 JP6 rooted, and Voodoo lagfix installed.
Recently I saw the GTGTouchwiz UI mod and decided that I really needed the landscape home screen.
So I followed the instructions along until the point where I was supposed to rename the TouchWiz30Launcher APK and ODEX files to .BAK files.
I used a "downloaded" version of Root Explorer (please, I do not own a credit card and am not legally capable of obtaining one by myself either so don't judge..) and went on to try and rename the files.
The first time I tried, it gave me a "no permission" type message saying I had no permission to tamper with any files. I gave the phone a reboot, retried and still, no permission. So I went around on the forums looking for answers and I read that I was supposed to change permission from "R/O" to "R/W" at the top of the screen, but there were no such options for me as in the app it only said "Mounted as R/O". I spent plenty of time looking for ANY options that allowed me to change permission and there were none.
Then I went on to download another version of RE and this time, I was allowed to rename files, the permission was set to "R/W" once within the system folder and I did not have to change any options. But when I refreshed, both files turned back to their original names (the rename was basically ignored). I also tried using Android Mate to no avail (same effects as RE) and now, I'm also trying with Super Manager.
But here I encountered another problem, when I tried to enable the "ROOT function" from settings, it gave me the message "The ROOT function in this program is not support you device or system image", btw that is not my grammatical error, that is exactly the message I get from Super Manager.
Now I have absolutely no idea what this "system image" of mine is, I'm still a complete noob to Android and all the concepts. So if I'm being oblivious to some simple error I made, please don't flame me or anything
Any help with this would be greatly appreciated, thanks for your time.
Bumpidy bump bump
Anyone help?
Hello,
I need quick help, because I got a big Problem.
I accidentaly enabled a virtual screen (xdpi) in Developer Settings and since then my device froze and will freeze at boot.
Can someone please tell me how the vallue in settings.db from /data/com.android.providers.settings/databases is called or where else I can reset that value so my device will boot again?
I already got that settings.db and I am in Recovery now to exchange it.
EDIT: Oh I am on Android 4.2.2 CM10.1
EDIT2: found the little thing named overlay_display_devices in table Global, I just deleted the line and followed that tutorial (setting the right owner and permissions)
Still freezes during boot, will try to fix permisiions automaticaly now via recovery...
EDIT3: Nope, still freezing during boot
what are the normal owner and permissions of settings.db?
I guess they are system.system and 775?
Ok ok, I am just too dumb to handle console commands...
It worked now, let this be a lesson to me how to manipulate settings without the settings app
So I'm in a bad place right now it seems. I just rooted my S6 with PingPong root and everything went great. Proceeded to install AdAway and get that started. Then I moved to some build.prop tweaks. I added in the RAM tweaks from the thread in General and I also edited product.name to "att" to remove the S Finder and Quick Connect lines under the brightness sliders. When I rebooted my phone, I got the problems described in the title.
The lock screen just shows a black wallpaper and the rest of the normal options on the lock screen. I'm able to unlock my phone, but then all I see is my actual wallpaper over everything. I can bring the notification shade down and use the toggles, but if I try to open an app all I see is the wallpaper. I know the app is running because when I tried the phone dialer, I was able to place a call. So everything is running, but I can't see any of them because my wallpaper is stuck in place over everything.
Obviously my first idea was to fire up adb and push my backup of the build.prop file to /system, but I can't use adb as it says my device is unauthorized...I've enabled USB debugging in the developer options and after a lot of attempts managed to blindly accept the authorization request on my phone.
I was able to get in through Adb shell. Moved my backup to /system, exited the shell and pulled the file from /system to check it and make sure it was right and now my phone is in a bootloop. What the hell happened? The build.prop is identical to the one I backed up. Why am I getting a bootleg now and what should I do now? I'm guessing I'm pretty screwed. Safe mode does nothing (continues to bootloop).
Currently downloading my stock firmware and going to flash that through Odin since I think it's my only option at the moment. If anyone has a better idea, please tell.
Edit: Flashed stock firmware with ODIN and all's good in the world again. Reacted a bit too quickly.
Thats the problem...Android Device Manager is useless cuz there is already a pattern...I tried almost 100 times and there is no "forgot your password?" option...I need at least do a copy of my pictures.
Is there any solution to this? I feel like a real idiot...I was trying a different pattern and I forgot It...I cant believe it...
I think there's a file not sure if it is directly under /data/system or one of it's sub directories, but basically what I did was to boot to TWRP , use the built it file manager and delete that file. I could then access my phone. I will search maybe I kept the file name somewhere.
EDIT:
Just remove this file /data/system/gesture.key
and reboot.
wizardwiz said:
I think there's a file not sure if it is directly under /data/system or one of it's sub directories, but basically what I did was to boot to TWRP , use the built it file manager and delete that file. I could then access my phone. I will search maybe I kept the file name somewhere.
EDIT:
Just remove this file /data/system/gesture.key
and reboot.
Click to expand...
Click to collapse
How I do that? my phone is not rooted, the bootloader is locked and debugging mode is off :S
Jerber said:
How I do that? my phone is not rooted, the bootloader is locked and debugging mode is off :S
Click to expand...
Click to collapse
That could be a problem. I think that it might be done using adb but not sure if it can be done without root/bootloader secured
If cracking an Android device were as easy as deleting a file then I doubt that there's much value in any security on a device at all, no?
Surely this has to be a reinstall of the ROM...? Maybe with no-wipe to preserve the data?
Genuine question - I don't know for sure.
dahawthorne said:
If cracking an Android device were as easy as deleting a file then I doubt that there's much value in any security on a device at all, no?
Surely this has to be a reinstall of the ROM...? Maybe with no-wipe to preserve the data?
Genuine question - I don't know for sure.
Click to expand...
Click to collapse
Testing it would be really easy. just set a pattern and then delete that file.
Lets us know is it is that easy to hack it or not.
Since obviously you know better, share your findings with us.
dahawthorne said:
If cracking an Android device were as easy as deleting a file then I doubt that there's much value in any security on a device at all, no?
Surely this has to be a reinstall of the ROM...? Maybe with no-wipe to preserve the data?
Genuine question - I don't know for sure.
Click to expand...
Click to collapse
The phone has to have an unlocked bootloader and twrp installed, so you already compromised its security yourself. You could relock the bootloader, flash a stock recovery and encrypt the phone, that would solve the issue.
"Since obviously you know better, share your findings with us."
Look, guy, just because you're a senior member there's no need to be offensively sarcastic.
Maybe you didn't get as far as my last comment: "Genuine question - I don't know for sure."
dahawthorne said:
"Since obviously you know better, share your findings with us."
Look, guy, just because you're a senior member there's no need to be offensively sarcastic.
Maybe you didn't get as far as my last comment: "Genuine question - I don't know for sure."
Click to expand...
Click to collapse
Not being Sarcastic at all. Making a point. If you got offended, sorry about that.
I posted what I have , after testing it myself. Had the same issue on Lollipop.
Further more, I will share another piece of Info in here.
When You are able to access any Solaris/Linux server using a console , and boot it from DVD, you can simply edit the /etc/shadow file and reset even the root password. Does that mean Unix/Linux aren't secure OS's ?
When you have access to OS level files you can practically hack every OS.
Same goes here. When you have unlock bootloader and modified recovery you can access system files that otherwise would be inaccessible. if he can have access to that file and remove it, he will gain access to his system.
Well, I tried everything that I could because my phone is no rooted, and the bootloader is locked, plus, the debugging mode is off too... so I was close to give up, BUT finally I remembered that my phone was connected to Airdroid!; if Airdroid is connected to the phone It can bypass the lockscreen and you can access to the internal memory anyways with the Airdroid website!, so I did a full backup of all my pictures and then I did a factory reset!, the copy was a kinda slow but I didn't care of course!. What a relief!!!
So, I really recommend use Airdroid (and have the app connected of course), it saved my life!, I was really frustrated about this, I cant believe Google doesnt provide the old way the restore the pattern like in Kitkat and Jelly Bean.
wizardwiz said:
I think there's a file not sure if it is directly under /data/system or one of it's sub directories, but basically what I did was to boot to TWRP , use the built it file manager and delete that file. I could then access my phone. I will search maybe I kept the file name somewhere.
EDIT:
Just remove this file /data/system/gesture.key
and reboot.
Click to expand...
Click to collapse
It worked like a charm!
I have a fingerprint enabled phone. forgot my pattern, followed your suggestion and presented in my phone are data/system/gesture.password.key and gesture.pattern.key so I deleted the pattern.key (guided by forgotten pattern) I rebooted and my apps were optimized and voila the phone is unlocked.
However, I tried accessing the fingerprint menu on my phone but refused access. I then used root explorer, browse to aforementioned location, copied and renamed gesture.password.key to gesture.pattern.key as it was before deletion.
went back to the security setting of my phone, setup pin option (scared of forgetting the pattern again) and phone screen locked. I try using my fingerprint to unlock (which I am accustomed to) and voila! it says pin required for additional security. entered Pin and the fingerprint menu became functional again and all previously stored fingerprints remained unaltered....QED