Edit build.prof due to touchwiz fail - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

I was messing around with Rom Toolbox pro and changed my dpi values from 480 to 800, restarted the phone and it loaded with huge resolution and touchwiz keeps saying it fails. I can not access my app drawer but yet i can still send and receive txt messages.
I have safestrap on alliance rom build 2[N9E], will i be able to get a stock build.prof file, place it on my sd card. then book into recoverymode and apply an update from the sdcard?
Any help would be greatly appericated

shrimpy88 said:
I was messing around with Rom Toolbox pro and changed my dpi values from 480 to 800, restarted the phone and it loaded with huge resolution and touchwiz keeps saying it fails. I can not access my app drawer but yet i can still send and receive txt messages.
I have safestrap on alliance rom build 2[N9E], will i be able to get a stock build.prof file, place it on my sd card. then book into recoverymode and apply an update from the sdcard?
Any help would be greatly appericated
Click to expand...
Click to collapse
Not sure if it will work, but flashing the rom again should overwrite the system folder where the build.prop is stored, so a new one would be installed.

aef
well, lucky me i don't back up enough like i should. ..
I ended up with this:
adb push build.prop /data/local/tmp/build.prop
adb shell "su -c busybox mount -o remount,rw /system"
adb shell "su -c cat /data/local/tmp/build.prop > /system/build.prop"
Then it would not boot the RomOS...just reflashed it to a previous state lost a lot of stuff but oh well.
I really like AllianceRom but having verzion is frustrating

Related

How do I get adb shell to work in recovery after root?

I rooted following the 10 minute root video, however forgot to remove a lot of those junk system apps, like CityID. I cannot get back into SU while in recovery, no matter what I do. How do I get back into the shell in recovery so I can remove all the bloatware?
I can get the error message:
- exec '/system/bin/sh' failed: No such file or directory
however i cannot seem to get back into the shell where I can access SU and remove the bloatware, anyone have any ideas on what im missing?
areghas said:
I can get the error message:
- exec '/system/bin/sh' failed: No such file or directory
however i cannot seem to get back into the shell where I can access SU and remove the bloatware, anyone have any ideas on what im missing?
Click to expand...
Click to collapse
I'm in the exact same boat as you. I don't know where to go from here.
run update.zip and let it fail again then you caN adb shell su
hmm doesnt seem to work for me
in order to get the back to adb shell in recovery, you have to go through the whole root process again. Then once you have snuck in the payload-update.zip and it has successfully installed it, you are able to do adb shell.
i had to run do the hole process over again to get su so i could remove cityid after root.
i used the 1.bat file as in the utube video for noobs.
ejlax said:
in order to get the back to adb shell in recovery, you have to go through the whole root process again. Then once you have snuck in the payload-update.zip and it has successfully installed it, you are able to do adb shell.
Click to expand...
Click to collapse
not cool lol, took me 3 hours to get the things to work with my sd card haha not worth it.
that is the only way
They are correct, you must do it all again, but look for a PNY 4gig class 4 sd. I tried hundreds of times over a 3 day period to do it and it worked first time and every time with this card.
when I run terminal emulator in the OS on the phone, and type su, the super user app grants it permission. Would we be able to delete system apps from there?
There is also another terminal app in the market for 1.99, listed as being for that purpose, so, has anyone tried it?
I don't have anything else I want to delete at the moment, since I got rid of cityid at the recovery adb prompt.
qwho said:
when I run terminal emulator in the OS on the phone, and type su, the super user app grants it permission. Would we be able to delete system apps from there?
There is also another terminal app in the market for 1.99, listed as being for that purpose, so, has anyone tried it?
I don't have anything else I want to delete at the moment, since I got rid of cityid at the recovery adb prompt.
Click to expand...
Click to collapse
The nand is locked down when you are in the main OS, so no, it would not work. You would need to do the re-root to gain access to /system/ as recovery is the only place where we are able to access it right now.
qwho said:
when I run terminal emulator in the OS on the phone, and type su, the super user app grants it permission. Would we be able to delete system apps from there?
Click to expand...
Click to collapse
E30kid said:
The nand is locked down when you are in the main OS, so no, it would not work. You would need to do the re-root to gain access to /system/ as recovery is the only place where we are able to access it right now.
Click to expand...
Click to collapse
I can get su access while in the OS. No problem on that. And I tried to delete teeter.apk, but got the "read only" message. So, I mounted it as read-write with
Code:
/system/bin/mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
that went fine too, but when I tried to delete teeter.apk, i got "rm failed, directory not empty"... but I'm not trying to delete a directory...
I guess the "nand is locked" and that's why, but... "the nand is locked" doesn't mean much to me, as I have no clue what that means

Superuser?

Does anyone know how to install this on the aria?
http://forum.xda-developers.com/showthread.php?t=682828
It's best to flash your Aria to a Liberated ROM. You can find it within the forums here. Since I can't post links yet. This will root the device and SuperUser will be added.
Not sure about that app. It looks like it does the same thing as the SU that comes in the Liberated ROM by attn1, just without the few extra options.
I tried booting into clockwork and mounting the system partition and doing this:
adb push Superuser.apk /system/app
adb push su /system/xbin
adb shell chmod 06755 /system/xbin/su
adb reboot
but when it rebooted the superuser app did nothing at all. No prompt or nothing running apps that needs su. I had usb debugging enabled. So I just restored a nand backup.
Might be a dumb question, but did you do adb remount ?
I used clockwork to mount the system partition. When I tried it with just adb remount it wouldn't mount the system partition. I would always get "Not a directory" error. But when clockwork mounted the partition it wrote the files fine with no error. When I rebooted the superuser icon and version were different than the one that came with the liberated rom.
I'm trying this now, I'll report back when I do it. I'll try a few different apps that require SU
I did the commands it said, I see the new icon, and when I press 'Menu', it shows the prefrences, but when I click it, it freezes the app.
It's probably not compatible with our phone yet.
Could be, but I'm pretty sure it does work, because if I remember correctly, Titanium Backup needs SU permissions, and I haven't encountered any kind of errors with it yet.
I see you posted on the thread for the program itself. Hopefully someone there will have a response.
Yeah, I'm hoping to get a response to it. We will see.
The newer version 2.2.2 works.
Awesome, ill give it a shot a little later.
Tried the newer version, and I get the same issues.
How did you install this one? I booted in to clockwork and selected install from zip file on sd and selected that file on my sd card.
I just did it through adb. I'll give that method a shot.
Looks like after doing your method, it works perfect now. Not sure why using adb doesn't work.

Galaxy-S Stalling Issue?

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?

Custom Rom App Removal

hey guys,
how would i go about removing apps from an installed custom rom?
ive tried titanium back... doesnt work, tried pulling the apps from the pack nothing,
ive tried root exploits and it just sends your phone into an almost
"paperweight"
like state,
any further moves i can do to remove various bits ? there as some things i just genuinely dont want.
Telling which rom and which apps might help
[ROM] Pays-ROM HD SPARTA v1.0 [ULTRA LIGHT] [19/NOV/10]
[ROM] Pays-ROM HD SPARTA v1.0 [ULTRA LIGHT]
i cant list the apps i want to remove as im off to work, but can you do some background work into it for me??
fkofilee said:
[ROM] Pays-ROM HD SPARTA v1.0 [ULTRA LIGHT]
i cant list the apps i want to remove as im off to work, but can you do some background work into it for me??
Click to expand...
Click to collapse
Have you tried doing it from terminal?
Code:
adb remount
adb shell
su
cd /system/app
ls *
rm INSERTANNOYINGAPPNAMEHERE
reboot
adb pull is not for deleting apps. It is for copying the app to your computer.
when i say pull... lol. i mean removing them from the system completely
fkofilee said:
when i say pull... lol. i mean removing them from the system completely
Click to expand...
Click to collapse
I've just discovered there are issues where /system isn't getting wiped correctly prior to a new rom being flashed. Keep getting apps from other roms and such sitting in my /system folder even after a wipe and flash - at this stage I assume CWM is bugged? Could be your issue is related.
nope the ADB coding doesnt work as its almost like there is a PERMANENT R/w lock on the section i need to remove apps from
unfortunately the issues AERNT related, as ive wiped everything before, these apps are pre installed on the ROM. What does me with this is that the root exploit to remove these apps as in Titanium backup ... just turns the phone into a very expensive paperweight till the battery is remove
weather apps (widgets etc,)
Twitter apps , teet and various other bits i want to remove
fkofilee said:
unfortunately the issues AERNT related, as ive wiped everything before, these apps are pre installed on the ROM. What does me with this is that the root exploit to remove these apps as in Titanium backup ... just turns the phone into a very expensive paperweight till the battery is remove
weather apps (widgets etc,)
Twitter apps , teet and various other bits i want to remove
Click to expand...
Click to collapse
Get a new rom ???
hmm flash a new rom??this is the most refined rom i can find for DHD.
for that reason its more of a hassle to flash new roms
I would rather crack it, mind you i might be really thick asking this. that code you gave me have i got to get the adb.exe from android SDK and do this via a cmd.exe window on my pc or have i got to do it on my phone via termnial emulator.
how weird!!!... i used to terminal emulator to allow su (I.E to give system SU Permissions and now i can remove the apps ) haha
Shocked!!
Admin Please close & Deleted Thread.
fkofilee said:
hmm flash a new rom??this is the most refined rom i can find for DHD.
for that reason its more of a hassle to flash new roms
I would rather crack it, mind you i might be really thick asking this. that code you gave me have i got to get the adb.exe from android SDK and do this via a cmd.exe window on my pc or have i got to do it on my phone via termnial emulator.
Click to expand...
Click to collapse
Yes from the android sdk. It *should* work from a terminal emulator as well if you run these commands first to mount the /system/app directory as read/write:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
chmod 777 /system/app
Other option would be to use the root explorer app, it is a paid app though well worth it.
dr.m0x said:
Yes from the android sdk. It *should* work from a terminal emulator as well if you run these commands first to mount the /system/app directory as read/write:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
chmod 777 /system/app
Other option would be to use the root explorer app, it is a paid app though well worth it.
Click to expand...
Click to collapse
Weird thing is i tried root explorer , and it still wouldnt R/W the app folder... but as i said now solved... slightly weird though that i completely missed that lil bit on the su permissions for the system directly.
fkofilee said:
Weird thing is i tried root explorer , and it still wouldnt R/W the app folder... but as i said now solved... slightly weird though that i completely missed that lil bit on the su permissions for the system directly.
Click to expand...
Click to collapse
Yeah you ninja'd my last post
Glad to hear you're gtg now.
but mind you the mount script i ran and it didnt work lol.... maybe i did them the wrong way round, (Raise SU first then do mount cmd??)
dr.m0x said:
Have you tried doing it from terminal?
Code:
adb remount
adb shell
su
cd /system/app
ls *
rm INSERTANNOYINGAPPNAMEHERE
reboot
adb pull is not for deleting apps. It is for copying the app to your computer.
Click to expand...
Click to collapse
Works. Thanks!

[Q] Cannot Update to ICS Read only file system

Hello All,
I am in a real bind here with my Thinkpad tablet. Lets just say i should have left well enough alone. Anyway, i have the
183925U tablet with A310_02_0039_0089_US that i originally rooted. I used titanium backup to remove some apps. When i
tried to update to ICS, it failed. At the time i read some forums and they said remove root with OTA and then update and
then use OTA to get root back. Tried that and it failed. I got a brilliant idea to remove root and do a factory restore
to hopefully get ICS to load. Now i have no root, cant downlaod anything cause i cant update, cant sideload and cant get
root back.
The update fails with assert check and goes on to say Music.apk cannot be found. I looked into how to reload or even copy
that file to the system but no matter what i try i get "Read Only File System" and i cant get past this. adb push does
nothing. i can push to /data/local but cant do anything with it from there
i can do the following:
adb shell
$su
#
and from there i have tried the mount -o rw remount /system and it seems to accept the command but the system wont let me
move or copy with mv or cat to the /system directory. Is there any way i can get past this? I really just want ICS stock
no root. Please help if you can. I am new so please be gentle and if you wouldnt mind spelling out any commands for me.
Thanks to anyone who can help me. Have a nice day

Categories

Resources