Hi there.
After many months of flashing on an orange san francisco i have moved on to my nexus s. got stock ics from update.zip a few weeks back and finally taken plunge in rooting today. plan on keeping it stock for now but noticed a few places saying recovery will disappear on reboot. i know that renaming the recovery fil in etc folder will stop it but can't seem to access it. used to use android commander on san fran but doesn't recognise device now. any ideas on free app to do the job?
Sorry if already asked but searching threw up nothing.
Get root explorer, mount as R/w, Then go to system/etc and rename the file install-recovery.sh to something else.
jobs a goodun!!! thanks for that. couldn't remember the name of that app! many thanks
Related
So I have a Samsung Galaxy Europa I5500L (Running 2.2 android)
Im wanting to remove my carrier name from the pulldown bar and the lock screen.
I have successfully pulled framework-res.apk using adb into my pc.
I then edited it, and changed a few things to do with eri.xml (carrier name), and saved it.
However, I cant get adb to 'push' the framework back into the phone, even with su permissions, even with usb debugging on, and yes its rooted, and yes the adb connection works fine normally
SO I came to the conclusion that I could use root explorer to put the framework file back into my phones system.
This is way Im going to do it is this.. copy the modified framework-res.apk it to my SD card, then inside my phone copy the file across to the phones system area using the root explorer app (making sure that the system is R/W). Im thinking this will obviously replace the existing framework-res.apk
However, Is this safe? Ive read about people doing it before but it doesn't seem right to replace a system file whilst the phone is up and running
Can I have some clarification whether or not this will be fine or not?
Thanks...
bump
any response would be welcomed , im really stuck here!
Your phone might not boot afterwards, so unless you have a custom recovery dont do that.
Sent from my T-Mobile myTouch 3G using XDA App
i was running root explorer trying to andromeda3 percent battery and deleted the framework-res.apk, as i was about to paste the downloaded version my wife called me for something and i set my phone down so my son picked it up and before i could paste, exited out of root explorer. long story short i had to boot into recovery and adb push the downloaded framework-res.apk into the /system/framework folder to make my phone usable again. luckily i was able to have access to a computer to do this, it made me wonder how i could make a zip that could be installed through clockwork recovery. i figured it was more then just using 7zip or something to zip it. thanks in advance, would be some nice information to know.
*Edit* after taking a second look, i found this thread (http://forum.xda-developers.com/showthread.php?t=796474) that i'm going to study
Dear All,
First thankyou so much for the great forum we have here, I am using Huawei Ideos u8150, the fone is network locked so I played around, being a total noob I started with installing sdk, and rooted my fone using z4root, rooting was successful
No when I try to copy a modified build.prop to the systems folder in root explorer, the file is copies but is not visible, also I have deleted the original build.prop & I am afraid to reboot the fone,
can restoring the fone to factory settings solve this ? also how come I copy the file to system folder, it gets copied and I still cant see it ?
I have tried pushing the file using ADB command line but the device refuses to mount (persmission denied)
I would really be thankful to anyone who can guide a noob like me, if you dont this forum has enough reasons to love it already,
cheers !
cknaveed said:
Dear All,
First thankyou so much for the great forum we have here, I am using Huawei Ideos u8150, the fone is network locked so I played around, being a total noob I started with installing sdk, and rooted my fone using z4root, rooting was successful
No when I try to copy a modified build.prop to the systems folder in root explorer, the file is copies but is not visible, also I have deleted the original build.prop & I am afraid to reboot the fone,
can restoring the fone to factory settings solve this ? also how come I copy the file to system folder, it gets copied and I still cant see it ?
I have tried pushing the file using ADB command line but the device refuses to mount (persmission denied)
I would really be thankful to anyone who can guide a noob like me, if you dont this forum has enough reasons to love it already,
cheers !
Click to expand...
Click to collapse
Moderators if by any chance I have placed this query in the wrong part of forum, please let me know in which part I should raise it, thanks !
In the top right hand corner or left it should be a r/o button. If you push that to r/w which is read/write you will be able to copy the bp correctly. Don't forget to mount as r/o which is read only before you exit RE. Then reboot. If you made a backup which you should have done before modding the bp you will be ok to reboot. If anything goes wrong just do a restore. Also you can Redownload the current rom your on to your cpu. Then extract it to a folder on your desktop. Then browse threw all the folders untill you see the stock build prop. Copy&paste it to your sd and that's your stock build prop. Hope this helps. Good luck
#Root/Hack_Mod-Always®
laie1472 said:
In the top right hand corner or left it should be a r/o button. If you push that to r/w which is read/write you will be able to copy the bp correctly. Don't forget to mount as r/o which is read only before you exit RE. Then reboot. If you made a backup which you should have done before modding the bp you will be ok to reboot. If anything goes wrong just do a restore. Also you can Redownload the current rom your on to your cpu. Then extract it to a folder on your desktop. Then browse threw all the folders untill you see the stock build prop. Copy&paste it to your sd and that's your stock build prop. Hope this helps. Good luck
#Root/Hack_Mod-Always®
Click to expand...
Click to collapse
thanks for the kind help, I have tried doing that, I have rooted it, the I click on the r/o button and then I did copy the new built.prop to systems folder, the copying process completes, doesnt report any error but still there is no file visible by the name of built.prop, I just cant find it, is it hidden ? or is it not being copied in the first place ? & thanks I would try to extract the stock built.prop, and copy it to the folder but I will do it as a last option till I dont find something else,
thanks a million for the help, would apprciate if you can point it what I am doing wrong
after flashing several roms back and foward, I'm having this problem, if I go into recovery I can't see any zip file at all, folders are there, but no zip files, I can still install from Rom manager but not from recovery since i cant find them, Please help
Running Ginger Beast 2.1.2.
But regardless what rom I'm running Zip's are gone
Are they on root of SD card or in a folder? If in a folder, try them in the root. I have never tried with them in a folder, but instructions always say put them on the root so there must be a reason.
they are on root, just can't see them from recovery, but can see and flash from Rom Manager.
I place my ROMs in a folder along with another folder containing kernels and system tweaks, there really is no problem placing them in folders.
I will try that, will let you know
Well guest what I can see them when I place them under a folder! Weird but I guess is another way to do it, I will still like to know why I can't see them on the root.
dragonfuego said:
Well guest what I can see them when I place them under a folder! Weird but I guess is another way to do it, I will still like to know why I can't see them on the root.
Click to expand...
Click to collapse
Try throwing a z in the file name and scroll all the way down while in CWR and see if it appears...maybee you couldnt decipher the right file out of a lot of others.
Folders make everything easier
Nope I always erase old roms from my phone, for some reason they just won't show
Hmm... Well thank you for that bit of info. I had a few roms j downloaded to play around with in folders never tried flashing! I always assumed since they stress placing them on a root there must be some reason! Well I guess the old saying about what happens when we assume holds true! I would thank now but can't from the app. Will do it soon!
Sent from my Inspire 4G using XDA App
I am not positive why Devs tell people to place them on the root of the SD card, but I have somewhat of an idea...
Many users simply do not know how to work there way around a file system and so they just infer every user doesn't understand and so placing on the root is just the easiest to do.
Yeah that's what I was thinking too... You'd think anybody who could root and use cwm would not be big enough noobs to fail with folder structures. Oh well. Thanks again!
Sent from my Inspire 4G using XDA App
Hey guys, I had a problem after flashing the new synergy. When I tried wiping and going back to my nandroid, twrp gave me an error saying something along the lines of /data/lost+found/#32/#32...too many open files and /data/lost+found~/#32/#32...too many open files. So when I booted back up I tried to go to those file paths and found that there is an endless folder in folder of "#32"s. I then tried to delete them from solid explorer, but it crashed. After trying it a couple times in solid explorer I went to ES file manager and made sure my system is mounted as writable in its settings and deleted the first #32. Then when I rebooted and checked, I saw that the endless folder in folder was still there. I don't think I've ever had this problem before until I flashed this. Can anyone help?
96NovaC said:
Hey guys, I had a problem after flashing the new synergy. When I tried wiping and going back to my nandroid, twrp gave me an error saying something along the lines of /data/lost+found/#32/#32...too many open files and /data/lost+found~/#32/#32...too many open files. So when I booted back up I tried to go to those file paths and found that there is an endless folder in folder of "#32"s. I then tried to delete them from solid explorer, but it crashed. After trying it a couple times in solid explorer I went to ES file manager and made sure my system is mounted as writable in its settings and deleted the first #32. Then when I rebooted and checked, I saw that the endless folder in folder was still there. I don't think I've ever had this problem before until I flashed this. Can anyone help?
Click to expand...
Click to collapse
Odin is your friend. Flash a stock image should fix it.
Haha thanks man but I ran the fsck fix that was in the toolbox and its fixed. To be honest that was gonna be the next thing I was gonna try but glad I don't have to now.
96NovaC said:
Haha thanks man but I ran the fsck fix that was in the toolbox and its fixed. To be honest that was gonna be the next thing I was gonna try but glad I don't have to now.
Click to expand...
Click to collapse
Glad to help, good for you.
Use AromaFM!
search bar will serve you..