Running Gumbo 1.5 ROM and gumbo kernel.
Essentially, I ruu'd, re-rooted my phone, installed the rom and kernel and then tried to install the clear lock screen posted by fresh. It's the clear lock screen with the black clock/white text.
Well, as it looks now I have my old lock screen running - the default sprint one - and then I have the custom lock screen in the bacj ground behind it (I can see the black box). I tried using fresh's tool to clear everything but it didn't work. I also tried setting another picture as the lock screen then clearing it... no dice.
So I searched through the forum to find a manual way to clear everything. I found one. It said to delete everything in system/etc/lockscreen/port/. I did an "ls" and it shows like 8 .jpg files in there... but when I try to rm them I get a "This file is read only" error. I'm doing this through su in adb shell.
Any help is appreciated or if anyone knows a solution please speak up. This is driving me crazy. I have like 3 layers of lock screen images stacked on each other.
Thanks!
I found the commands on another page.
If anyone else stumbles on this you need to remount the file system in order to remove the "Read Only" files.
In ADB shell type:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
then rm the files.
I also deleted the files in /data/mist/lockscreen
This seemed to get rid of the background images but I'm left with 2 things still.
The clear lock screen from fresh, and the curved gray bar from the Rosie lock screen default.
And finally, I found a solution.
If someone stumbles on this follow the directions posted above, then flash a clear lock screen through the recovery. That should remove the remainder of whatever residual things are left.
Related
My landscape orientation is slightly off, how to I reset the accelerometer, or clear the cache like some have suggested?
I thought my battery was running hot too so I ran Raging Thunder to see how much the graphics would raise the temperature. As I started driving I realized the car has a serious over-steer to the right. I have to have turn to the left just for it to drive straight.
Edit: I've tried the instructions here and it didn't work at : (http) ostebaronen.dk/fixing-accelerometer-on-htc-magic/
I'll just wipe and hope that fixes everything. :-/
Edit 2 (04/20/10): Solution found, see post #7 in this thread.
Edit 3 (04/20/10): Nevermind it did not work. I though it did failed to realize that my bubble level app was still calibrated to correct the misalignment. :/
do a full wipe then re flash the cyanogen rom again
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I wiped, tested- no change in orientation unalignment
reloaded teh 5.0.53 rom, tested- no change in orientation unalignment
wiped again
wiped rotation
wipe cache, tested- no change in orientation unalignment
wiped
restored nandroid, tested- no change in orientation unalignment
guess i'm out of luck perhaps it could be a hardware issue...
After research and using sensor testers from the marketplace, I believe the file I need to delete/reset is AK8973. In ADB SHELL, once I run the command "mount -o rw /dev/block/mtdblock5 /data" then I can go into "cd /data/misc." If I list the directory I see a file called ak8973prms.txt .
Based on the sensor testers, it always lists the values under ak8973 so I see the relation.
What is my next step? Do I delete the .txt? Can I at least make a backup first. It'd be nice to see what the contents of the file are. I tried the pull command and I can not seem to get a copy of it to my computer for the life of me. I've never used linux before but I learn quick I just don't know where to resource now.
Edit 2:08: I figured out how to the view the file with the more command. Here are the internals. I'm curious if this is the source of the missalignment but I'm not sure how to fix. My issue is that the AK8973 Orentation sensor Y axis (pitch) is negatively off by about 4 degrees. I'm not sure if this txt file is a recent snapshot or a guide to help calibrate.
adb shell
/ # cd data/misc
cd data/misc
/data/misc # ls
/data/misc # more AK8973Prms.txt
more AK8973Prms.txt
[AK8973]
HDOE_STATUS=1
HDOE_SUCTEMP=113
HDAC.x=1
HDAC.y=128
HDAC.z=7
HOFFSET.x=335
HOFFSET.y=-687
HOFFSET.z=-210
ASENSE.x=256
ASENSE.y=256
ASENSE.z=256
AOFFSET.x=0
AOFFSET.y=0
AOFFSET.z=0
/data/misc #
I was having this problem along with some others so I went back to 5053
I went back to other roms, including stock and the problem continues for me.
Ok so i finally found the fix, it was by overriding the AK8973Prms.txt with a blank file. I rooted a week ago and I'm so excited to have found this solution. Having a problem has forced me to learn some linux commands.
There may be a better way to do this, if so chime in but here are my caveman instructions.
Reboot your phone in Recovery mode (home+end/power > bootloader > recovery)
Connect via usb
Windows Start > Click Run > type CMD and press enter
Access your SDK tool folder with command: cd [file path]
adb shell
mount -o rw /dev/block/mtdblock5 /data
exit
[Make a blank file AK8973Prms.txt with notepad in your windows sdk\tools directory]
(in CMD window type, remember to change the the C:\ file path in the command to yours)
adb push C:\Users\name\Desktop\android-sdk-windows\tools\AK8973Prms.txt /data/misc/AK8973Prms.txt
exit
Reboot and wola!
i have managed to calibrate my nexus one g-sensor system wide using your method as a guide, thanks alot
After having some major speed issues using Touchdown on my new Vibrant, I was directed to this thread discussing issues with the way Samsung stores app data on the phone. Apparently the app data is stored on the internal SD vs. NAND and that is considerably slower. Here are the two methods to fix:
*Both Methods require ROOT*
*Method 1 limits the space of app data, which can possibly cause issues*
*Method 2 requires writing a new Kernel, which comes with it's own possible issues*
*READ THE THREADS!*
Method 1: http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
Method 2: http://android.modaco.com/content/s...ed-real-fix-for-the-stalling-lagging-problem/
Hopefully this will be helpful moving forward with the development of this phone!
Note: I have used method 1 which moved the app data from the SD space to the NAND space which significantly increased the speed of my phone, but PLEASE read the links and associated discussion. You are limited to 130MB app space on NAND, which can be limiting depending on which apps you use. Method 2 purports to fix this limitation...
How to check how much app memory you are currently using:
Code:
adb shell
su
cd /data/data
busybox du -h|busybox grep M
How to apply Method 1:
Code:
adb shell
su
busybox cp -rp /data/data /dbdata
mv /data/data /data/data.bak
ln -s /dbdata/data /data/data
reboot
How to undo Method 1 (no loss):
Code:
adb shell
su
busybox cp -rp /dbdata/data /data/data.tmp
rm -r /data/data
mv /data/data.tmp /data/data
reboot
How to undo Method 1 (restore to point of application):
Code:
adb shell
su
rm /data/data
mv /data/data.bak /data/data
reboot
Awesome, thanks for doing the parsing and putting out a procedure. Works great. No more lag.
Thanks, just tried it out on mine.
BE WARNED you will run into issues if your application data goes over 130MB. There is a better way to do this which includes a custom kernel with ext3/4 support and symlinking to the ext partition instead of the small NAND space.
Find it herehttp://android.modaco.com/content/samsung-galaxy-s-s-modaco-com/313365/updated-real-fix-for-the-stalling-lagging-problem/
I havent felt the need to perform either of these ATM. Please warn people of the consequences especially if your just telling them "Hey this will make your phone faster!" I do notice its explained in the article you linked from but not everyone will read that and then when they start having issues they will have no idea what to do. For those that completed this method you might want to revert it and go a better route. 130MB isnt enough room.
Agreed...I figured people would read the link, but you never know. Will update accordingly. THX!
I am trying test out method 1 but I keep getting stuck. I type in cp -rp /data/data /dbdata into adb but it comes back with cp: not found. Any ideas what I am doing wrong here?
Add busybox before the cp command; i.e.: busybox cp etc...
Krycek said:
Add busybox before the cp command; i.e.: busybox cp etc...
Click to expand...
Click to collapse
Thanks, figured it was something simple like that. Still new to this Android stuff after years of custom WinMo roms and hybrid Blackberry roms.
i'm a little sketchy about applying method 2...will installing a modified kernal have an effect when samsung rolls out the update for 2.2?
I concur, but that is also probably the "right" way to do it. The nice part about method 1 is it is easily reversible. I will update post 1 in a minute with how to check what your current usage is to see if you are close to the 130MB limit.
Thanks, just checked my usage and was only using 21MB thus far. I figure the 130MB limit should suit me fine until Samsung issues a fix. It looks like the European devices already have a new firmware that speeds it up quite a bit so probably won't be too much longer here in the US either.
Im not going to do either. Im going to wait for an official fix.
I'm about to get a vibrant; if you can get parted installed wouldn't it be fairly simple to just unmount and partition the internal SD card into fat32 and ext3/4, and then maybe just update fstab? (parted lets you resize existing partitions to make room for new ones, but I'm not sure if the Samsung firmware uses fstab or something else, coming from a MyTouch here).
anomalous3 said:
I'm about to get a vibrant; if you can get parted installed wouldn't it be fairly simple to just unmount and partition the internal SD card into fat32 and ext3/4, and then maybe just update fstab? (parted lets you resize existing partitions to make room for new ones, but I'm not sure if the Samsung firmware uses fstab or something else, coming from a MyTouch here).
Click to expand...
Click to collapse
i doubt it...it's the reason you need to install the modded kernal so that it recognizes the ext3 or ext4 partition. without it the partition is useless. i personally wouldnt use method 2 as there is no way to revert as of now.
Man i dont understand wtf is going on. Im usually good with adb and whatnot but I cant seem to get su permissions. I type "adb shell" and it goes thru. But when I type "su" it comes back 'permission denied'. Of course, I applied the update.zip to get my phone rooted. Superuser works and I have my rooted apps working.
Anyone have any ideas?!
I'm not infront of my PC atm, but try this.
adb mount
adb shell
su
If mount doesn't work try remount.
Let me know if this works for you, once i'm home I can double check.
Already tried that. I have a Nexus One and adb remount works on that but for this phone it says 'remount failed: No such file or directory'
Digitalthug said:
Man i dont understand wtf is going on. Im usually good with adb and whatnot but I cant seem to get su permissions. I type "adb shell" and it goes thru. But when I type "su" it comes back 'permission denied'. Of course, I applied the update.zip to get my phone rooted. Superuser works and I have my rooted apps working.
Anyone have any ideas?!
Click to expand...
Click to collapse
You might have already tried this, but make sure the phone is unlocked (at home screen) when you run the su command from your workstation... superuser will then prompt and you can allow it to run.
I've noticed that if the screen is locked it won't prompt and just give the permission denied message.
Sent from my Vibrant (with lag fix and loving it)
just did method 1 and the difference is incredible. as far as method 2 goes, will custom roms have this ability from the get go or do we need the official samsung update?
I just want to confirm that this fix works for the US version of the Galaxy S (Samsung Vibrant) right?
If you want to remove the carrier branded boot and shutdown animations or the default Samsung animations that you see upon startup and shutdown, you can enter these commands via adb shell or in a terminal emulator on your Galaxy Tab. This code renames the files so that they are no longer accessed when the device is started while keeping them from auto-replicating. Deleting or moving the files with root explorer will not work because the files will be replaced almost immediately. You have to be rooted in order to gain the superuser privileges needed to edit the files in /system.
If you aren't already rooted, you can use z4root or superoneclick.
After that, if you choose, you can enter the commands through adb shell or through a terminal emulator available through the market. If you are not familiar with adb, you can get information on it here: basic adb/shell info
If you don't want to be tethered to the computer, you can take the terminal emulator route. I used "Android Terminal Emulator" by Jack Palevich. It is free on the market, but I'm sure that any of the other ones will work just as well.
If you have a Sprint Galaxy Tab and want to remove the Sprint animations/sounds at startup and shutdown, enter the following commands. Be careful, because you are editing /system files.
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
mv /system/media/bootani.qmg /system/media/_bootani.qmg
mv /system/media/video/shutdown/shutdown.qmg /system/media/video/shutdown/_shutdown.qmg
mv /system/media/audio/ui/PowerOff.wav /system/media/audio/ui/_PowerOff.wav
mv /system/etc/PowerOn.snd /system/etc/_PowerOn.snd
mount -o remount,ro /dev/mtdblock3 /system
exit
For those of you with tabs other than the Sprint Tab, you may have to add the line:
Code:
mv /system/etc/PowerOn.wav /system/etc/_PowerOn.wav
This line goes after the command to move "PowerOn.snd"
These commands will leave the standard Samsung bootanimation. If you want to get rid of all bootanimations completely you can enter the following code:
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
mv /system/media/bootani.qmg /system/media/_bootani.qmg
mv /system/media/samsungani.qmg /system/media/_samsungani.qmg
mv /system/media/video/shutdown/shutdown.qmg /system/media/video/shutdown/_shutdown.qmg
mv /system/media/audio/ui/PowerOff.wav /system/media/audio/ui/_PowerOff.wav
mv /system/etc/PowerOn.snd /system/etc/_PowerOn.snd
mount -o remount,ro /dev/mtdblock3 /system
exit
Now open your terminal or adb shell again.
Now enter:
Code:
su
cd /data/local
chmod 777 nobootani.sh
./nobootani.sh
exit
Now restart your tab. You will see that the shutdown animation is gone. When the tab restarts, the carrier/default animations are gone.
thanks
thanks a lot rkmj - I can confirm that this is working on my Sprint CDMA Galaxy Tab. The animations has been removed.
I just got it a couple of days back and I am in the process of removing all the junk from samsung and sprint without flashing a custom ROM cuz seriously there isnt any worth taking the risk.
I have cleaned almost all of them and with this fix my TAB just feels like totally unbranded now.
Next step is to make it faster without a custom ROM, ideas are welcome or maybe a safe list of services I can disable without breaking my tab.
Nice, thanks man
Sent from my GT-P1000 using XDA App
The at&t startup logo and sound is gone with overcome rom, but the t-mobile startup logo is still there.
So what will remove the t-mobile start screen?
I'm pretty sure this will remove the T-Mobile startup. Most of the carrier-branded startup routines are in the same locations. If this doesn't work though, you might check /system/media for a file called "bootanimation.zip" If that fails to produce, check /data/local for the same file. If you have that "bootanimstion.zip" file, you can either swap that bootabimation file for a custom one or get rid of it altogether.
Sent from my Samsung Galaxy Tab
rkmj said:
I'm pretty sure this will remove the T-Mobile startup. Most of the carrier-branded startup routines are in the same locations. If this doesn't work though, you might check /system/media for a file called "bootanimation.zip" If that fails to produce, check /data/local for the same file. If you have that "bootanimstion.zip" file, you can either swap that bootabimation file for a custom one or get rid of it altogether.
Sent from my Samsung Galaxy Tab
Click to expand...
Click to collapse
I have a tmobile galaxy tab, and the bootanimation.zip is just the startup movie that plays. Mine has been replaced with anouther. The white tmobile screen bugs the heck out of me, is not part of my custom boot animation but still shows. So does the samsung galaxy tab black screen.
Can I get rid of these two screens?
Sent from my GT-P1000 using XDA Premium App
There's an app called BAC or Boot Animation Changer that works with my rooted Moto Droid but not with my rooted Sprint Galaxy Tab. Would you have any idea whether after removing the boot animation if it will work? TIA
I'll test and see what results I get; just thought it might be good to have an informed opinion first. And many thanks for the post.
Thanks for this; just wanted to get rid of my carrier branding (Telstra) on my Galaxy Tab. I'm rather happy with the Samsung animation and even the on/off sounds.
good work
works beaut on Telstra 8.9.. give or take file names changes of course but the result is spot on...out with Tesltra crap...
rkmj said:
I
Now restart your tab. You will see that the shutdown animation is gone. When the tab restarts, the carrier/default animations are gone.
Click to expand...
Click to collapse
is that work other devices ? mean note 4 etc? and another cariror like sprint verizon etc?
Hi, i need a fix for this and fast !!! I've tried all that is listed on xda about this issue, but to no avail. Anyway, i forgot my pattern and went to the forgot pattern menu. My wifi was off, so i figured it would give a prompt of some kind to turn on the wifi and then log on to my google account. But nooooo, google supposes that everyone's wifi is on all the time. Please help, what do i do ? I rebooted to recovery, i made a nandroid and currently i am adb pulling the twrp folder from my N7. I would have just factory reseted it, no probs, but i remembered i have some EXTREMELY important works in colornote that i can't afford to lose. Please help, what do i do ?????
Looks like you answered your own question. Unless your Android isn't encrypted, just boot into TWRP and backup your data using adb:
adb pull /data/data C:\backup
Click to expand...
Click to collapse
The main thing you will have to concern about is restoring those data and make it readable by the app. There are several ways, but you can either:
adb push C:\backup\colornotes /data/data/colornotes
Click to expand...
Click to collapse
Don't forget some devices you need to give it write permission first: adb remount rw, though should not be needed with TWRP. Or just copy the folder back using a rooted file manager.
Then go into adb shell and fix permission of the files so the app can get access to them:
adb shell
su - (again shouldn't be needed wile in TWRP)
chmod -R 644 /data/data/colornotes (or 777 for full access)
Click to expand...
Click to collapse
Tips while in adb shell:
Check permissions of files by typing: ls -la
Check what partition is mounted and whether you have write privilege to it by typing: cat /etc/fstab
Also, if you use a custom rom like CyanogenMod or AOKP, there is an option to enable all widgets on the lockscreen. Just put the Power Control widget on the lockscreen, then you can toggle WiFi on and off. (Can't remember if this is also possible with stock.)
Have fun.
OR have a look here.
Looks like either of the two methods suggested would be feasible with only a recovery running, but the 2nd one is easiest (as a custom recovery wouldn't necessarily provide a statically-linked sqlite3 utility).
if it works it doesn't require any wiping.
BTW guess how I found this.... wait for it .... wait for it.... wait for it.... I used google search.
Hi, i forgot to mention that i made the twrp backup while i was locked out and whenever i try to restore from the backup after a factory reset, it goes back to square one... And when i did a full wipe and hoped to use titanium backup to extract stuff from the nandroid, it just gives me and empty list, but the backup is there, all 5gb of it
iAndroidOS said:
Hi, i forgot to mention that i made the twrp backup while i was locked out and whenever i try to restore from the backup after a factory reset, it goes back to square one...
Click to expand...
Click to collapse
Well, that is to be expected, is it not? You are restoring exactly what is already there - effectively a no-op.
OK, I just booted into TWRP (2.4.1.0) and confirmed that the (equivalent of the) following disabled my pattern lock on the next boot:
cd /data/system
mkdir foo
mv locksettings.* foo
mv gesture.key foo
I did all of the above (the 'cd' command is implicit) using TWRPs touch interface - didn't even need adb.
ymmv as I am using jdq39/4.2.2 and my tablet was not in a "locked-out" state, but its an easy thing to try.
Not sure if this will help anyone else, but I searched forever trying to figure out how to write into the system folder using Terminal Emulator on the Note 3 to no avail. I found a slew of posts that said to type "mount -o rw,remount /system" to achieve this. When I used this command it didn't return any errors so I assumed it worked, however no files ended up being copied and pasted to the location I wanted. I found numerous other examples that were supposed to enable writing to the system as well, but none of them worked. I finally figured out how to get it to work on my Note 3 by typing "mount" in terminal emulator and noticing that at the very beginning of the string that was returned was "rootfs". So if you are wanting write to your system using Terminal Emulator on the VZW Note 3 here is what ended up working for me:
Code:
mount -o remount,rw rootfs
to return to read only enter:
Code:
mount -o remount,ro rootfs
I wanted to figure this out because a bug in TWRP v2.6.3.0 maimed my efs partition and bricklooped my phone. Even flashing the Stock Developer tar by Beans wouldn't bring it out of the brickloop. I was able to get out of the brickloop by following this thread, but even though my phone booted up and the IMEI # was correct, my /efs folder was missing in action. This caused odd things to happen like my lock screen not functioning and the power button instantly turning the phone off instead of bringing up the power menu. I discovered this was because the phone was placed into something called "factory mode" and that to fix it you needed to edit some files in the efs folder, which were completely missing on my device. Member js0uth graciously sent me his efs folder from his Developer Note 3 and when I copied it to my phone it began to function normally again (big shout out to js0uth!). However, this folder was completely deleted once again after a reboot. So now you can see why I was looking for a way to copy these files using Terminal Emulator. I ended up making a Tasker profile with the Secure Settings plugin that automatically copies the files from my ext SD card to my system folder on boot of the device. In order to mount, copy/paste the files while retaining the correct permissions from the folder that js0uth sent me, and unmount the system I had the set up my Secure Settings command as follows:
Code:
mount -o remount,rw rootfs;cp -Rpf /storage/extSdCard/efs/* /efs/;mount -o remount,ro rootfs
So now I have a livable workaround for my problem until I can discover a way for the phone to rebuild my own /efs folder.
Edit: See radionerd's post for a permanent fix to this issue and be sure to hit thanks under his name if it helps you.
I did the same to my DE. Corrupted EFS about a month ago after a few flashes using TWRP 2.6.3.0. Boot loops for 28 hours of hell until I followed your tracks to the trick that deleted my corrupted EFS folder, and created a new empty folder. I guess this would wipe out IMEI, Mac, and more in models that store phone specific data in EFS. We lucked out I've read that our phones have that info in a few other folder not EFS
Since wiping EFS I have run stock ROM, CM11, and now bean V6. I didn't see the factory mode popup until recently. I noticed that the screen will flash when leaving or entering cell service.
My corrupted EFS was 3MB. I'm curious what's the size of the EFS folder from js0uth?
Were you able to enter the factory mode on string? something like this?
Code:
# echo -n ON > /efs/FactoryApp/factorymode
this is from an S3
Thanks for documenting your steps to recovery.
radionerd
radionerd said:
My corrupted EFS was 3MB. I'm curious what's the size of the EFS folder from js0uth?
Click to expand...
Click to collapse
It's 1.04 MB. Sorry for taking so long to respond. I thought I had it set up to send instant emails for replies to this thread, but apparently I didn't.
radionerd said:
Were you able to enter the factory mode on string? something like this?
Code:
# echo -n ON > /efs/FactoryApp/factorymode
this is from an S3
Click to expand...
Click to collapse
Setting the Factorymode folder to ON is actually what disables that mode. Seems backwards I know, but when it's set to OFF (or if the folder is completely missing as in my case) that warning message will display. If that folder is intact on your phone then you should be able to use a string to disable or enable Factorymode.
It got worse before it got better
bodieism said:
It's 1.04 MB. Sorry for taking so long to respond. I thought I had it set up to send instant emails for replies to this thread, but apparently I didn't.
No worries, I went from an annoyance of no lock screen to bricked for over 6 weeks. This happened after trying to do an EFS backup.
I've learned a lot since back then, My DE is back 100%, EFS is repaired. I think we ran the same script which actually points to the wrong mount in our phones. It brought us out of bootloops, but efs was pointed to block12. Qualcom snapdragon Note-3's use mmblk0p11 to load /efs.
If you still have to load the tasker script, I think I figured out an easy fix to rebuild your original efs folder.
I would backup mounts first, delete /efs folder. Then run the original script, but this time change from 12 to 11.
Code:
adb shell
su
mke2fs /dev/block/mmcblk0p11
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p11 /efs
Bet that would do the trick
Here is my thread
Click to expand...
Click to collapse
^ That did do the trick! :good:
Phone is back to 100% working order :highfive: