Thanks to the limits on new accounts, I cant post this in the relevant thread, so...
I recently used http://forum.xda-developers.com/showthread.php?t=1716124&page=73 on a new rom flash for the admire.
I found I had no gps, so I reflashed my phone then installed the gps fix script. Seemed like it worked, so I went about spending 6 hours tweaking my phone over the day.
Gps is gone again - not sure if maybe cell phone tower setting was turned on in locations tab and maybe got apps to work without it, but whatever the reason this script doesnt work for me.
The thread states that to flash one of the scripts in that doesnt have a gos issue, i need to uninstall the prior script.
How do I go about that without flashing my phone again and losing tons of work?
Do I have to look at the script and manually go in and delete every file it created and unalter every script it changed then reflash the new script?
Help?
Asking in your devices forum could be better.
But in general, yes, take a look at the zip you flashed. Inside META-INF/com/google/android you'll find an updater-script file that can be opened as text and tells you where everything inside the zip got flashed to.
Generally, scripts that run at boot get flashed to system/etc/init.d
Use a root explorer to locate the init.d address, or the name of the files that you saw inside the zip.
Related
So i want to take the phone app out of eugenes macnut and toss that on my phone
The way i went about this was unzipping the macnut rom and copying the phone.apk going in through root explorer and plopped it in to my system/app/ folder.
the first time i did this it started an endless "force close phone.app" and had to fire up a backup i made in recovery...
the second time i tried it i replaced both phone.apl and phone_util.apk, this time i got a force close pop up two or three times then it went away... but nothing on the phone changed.
what am i doing wrong here.
edit:
i also tried just unzipping both roms i am using... swapping the files around and re-zipping and flashing... but it hung on the install and i was told thats because of the xml file does not know what the modification was so it does not know how to handle the changes.
:the explanation:
I just like the way it looks with the contact option in the tab. Also I dont like how the "log" list either one thing or everything; I prefer to see incomming/outgoing/missed and not have to have a full thing of text messages.
I was tying to make a fancy updater-script for an add-on for my ROM, but I kept getting a Status 6 error when flashing, so I stripped it back to nothing, just the most basic commands, and eventually got it to work. I made a copy, tried editing it to add the fancy stuff back in... broke again.
So I stripped the copy back to the basic commands... and it still breaks .
As far as I can see, the two files I have attached are identical in every single way, but one fails with a Status 6, the other flashes (BattMod works, update doesn't). Both are edited using gedit on Ubuntu, both zips are created in Ubuntu, neither are signed.
Can anyone see why, I am really tearing my hair out here... all I want to do is add some ui_prints and some progress bars .
I haven't looked it them yet, but make sure you are using the correct update-binary. Different ones support different number of parameters in the mount command.
Don't leave junk files in the update like updater-script.old, it's bad practice
My guess would be that since it's named update.zip, it's looking for a signature and it can't find one. Try renaming update.zip to battmod.zip and see if it works, or sign it first with testsign.
l0st.prophet said:
I was tying to make a fancy updater-script for an add-on for my ROM, but I kept getting a Status 6 error when flashing, so I stripped it back to nothing, just the most basic commands, and eventually got it to work. I made a copy, tried editing it to add the fancy stuff back in... broke again.
So I stripped the copy back to the basic commands... and it still breaks .
As far as I can see, the two files I have attached are identical in every single way, but one fails with a Status 6, the other flashes (BattMod works, update doesn't). Both are edited using gedit on Ubuntu, both zips are created in Ubuntu, neither are signed.
Can anyone see why, I am really tearing my hair out here... all I want to do is add some ui_prints and some progress bars .
Click to expand...
Click to collapse
With what are you editing it?
I've found out that editing it with notepad or any program won't work even if i'm using the right commands, so i decided to use amend2edify, you select an update-script (an update-script you can edit it with notepad without any problem) and it converts it into updater-script, updater-binary, but you have the possibility to edit anything in the output that you want and save it, or just copy-paste into the output the commands in your updater-script onto output by overwriting the converted output.
Don't know if i explained myself well.
Good luck
Try This One
Blank-CWM.zip
It's made for the Moto Photon, so you will need to:
1) Replace the update-binary with one from your phone.
2) Copy the file you wish to flash
3) Delete the txt files in it as well as any folders that you do not need to use in the process of flashing
4) Be sure to set the permissions to target the folder or file you are flashing. If you do NOT update this, you will end up in bootloops (Don't say I didn't warn you)
5) Flash away
Cheers!
Hi there,
I upgraded my Galaxy 551 to Gingerbread 2.3.6. All went well. Unfortunately it seems to be a common side effect that the Z and Y keys (and some others) get swapped. The fix is apparently to modify the file /system/usr/keychars/sec_keypad.kcm.bin. The ideal thing is to put the old file from before the FW update back in, but of course I don't have that anymore! But the existing one can apparently be altered. If I can copy it to the SD card I can alter it in a hex editor and put it back.
So, I rooted my phone with that one click application, and that went OK too. I installed root explorer and found the file. There were also some others in the same folder I may be able to use. But, I cant make the folder R/W (pressing the button does nothing) so cant do anything with the file. I also tried Super Manager with no luck.
I am new to the phone fiddling stuff so noob level instructions would be appreciated!
Think I have it sorted. I installed superuser and then Root Explorer allowed me to select read/write. Now to try sort out this file!
OK, seems that you need to edit the file /system/usr/keylayout/sec_keypad.kl. Did that. DO'H now my keyboard doesn't work at all! Glad it saved a backup for me! Not sure what I did wrong, only edited two characters in a text file! Even the power button doesn't work. Got to pull that battery out LOL!
It seems when the file was saved it was saved with zero size. When I try to delete it to replace it with the backup it says cant delete, read only. So, not sure how I am meant to replace this and fix this problem.
Any ideas, remembering that I cant actually use any buttons on the phone!
I asked this in the general Q&A thread because I feel it is an android issue, not a Note issue...but alas no one even replied, trying it out here. Please help!
RockZors said:
Hello all,
I have a Samsung Galaxy Note i717. I have installed a few ROM's, but recently I installed CM9 unofficial build. After it was installed, I noticed that my default.prop is only like 4 lines long. So I try and add stuff to it (I am rooted, and used RW mode in Root Explorer). I can close the file and save changes successfully, but when I reboot it is back to the way it was with the 4 lines. It is not only that though, any files i add to the "/" get deleted upon reboot.
Things I have tried:
ODIN to stock rom, still did not have a full default.prop
Tried many different ways to change file system (different programs)
Ran fix permissions in CWM and busybox installer script
All with no success. Is there anything else I can try to fix this and be able to edit my "/" and have changes take affect. Or has anyone had this issue before?
Thanks
Click to expand...
Click to collapse
I was wondering if anyone with an i717 could go into cwm, run a backup, and upload that somewhere so I can restore it. Keep in mind your personal data gets backed up also, so preferably someone with a fresh working install. I don't care what rom it is either.
Thanks for reading.
The default.prop should only be 4 lines..
Are you confusing it with the build.prop?
Wow well don't I feel stupid. That's exactly what it was. Thanks for helping me see the way!
Hi guys, before I start I'll say that I have searched all over the internet and here on the forums and I couldn't find my particular issue. Well the thing is that I edited the line in my build.prop "ro.build.version.codename=REL" to "ro.build.version.codename=L" so I could get the material design on the Google Now Launcher pulled from a Android L build here's the thread I got that app: http://forum.xda-developers.com/android/apps-games/app-android-lollipop-apps-launcher-apps-t2912905
I did that and now my device will boot up normally then I will reboot by itself then show the boot animation then repeat the same process again and again until I force the phone to recovery or fastboot.
By the way my device is the LG Optimus G (E970) running GEE 3 ROM 1.2 and TRWP 2.6.3.0 and I have a backup of the original build.prop on my PC. I don't want to lose my data and apps since I forgot to make a backup (silly me).
I would like to know if there is a way to push the build.prop file on my PC to my phone so I could just replace it, or create a flashable zip.
Please help me, and thanks in advance.
Nevermind. I managed to push the original build.prop file to /system set the correct permissions and now my phone is working again.
Admin feel free to delete or close this thread.
question
AntonyOrtega said:
Nevermind. I managed to push the original build.prop file to /system set the correct permissions and now my phone is working again.
Admin feel free to delete or close this thread.
Click to expand...
Click to collapse
how were you able to do it when you couldnt get past booting.