Related
I'm trying to create an update.zip containing apps that I want. I have googled and followed every step on creating the folders and signing and importing my apps and craetiing the script...when I tried to flash it via clockwokmod recovery its gives me an error...which I mostly believe is with the script...can anyone please tell me what I'm doing wrong....
PS: I also get an error stating that I should switch to Edify script to create my update and I have gogoled it and and still don't know what it is or how I switch for that matter.
Sent from my HTC Vision using xda premium
Barry:// said:
I'm trying to create an update.zip containing apps that I want. I have googled and followed every step on creating the folders and signing and importing my apps and craetiing the script...when I tried to flash it via clockwokmod recovery its gives me an error...which I mostly believe is with the script...can anyone please tell me what I'm doing wrong....
PS: I also get an error stating that I should switch to Edify script to create my update and I have gogoled it and and still don't know what it is or how I switch for that matter.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Try Titanium Backup to create update.zip.
Go to backup/restore ---- press menu ----- create update.zip
You can use it and it works flawlessly.
Sent from my HTC Vision using Tapatalk
But can I flash it via clockworkmod without it saying error with scripting or any errors
Sent from my HTC Vision using xda premium
Why don't you post your script and we can help you fix it.
At some point, the update-script (amend) switched to updater-script (edify). The commands are similar, but the syntax and binary are different. You have to match the correct file system, parameters, and update-binary, etc.
update.zip
gee one said:
Why don't you post your script and we can help you fix it.
At some point, the update-script (amend) switched to updater-script (edify). The commands are similar, but the syntax and binary are different. You have to match the correct file system, parameters, and update-binary, etc.
Click to expand...
Click to collapse
So ive done done everything accept for the "script fixing" and signing the update.
so can you guys please look at it and fix it for me so that i can flash it via clockworkmod (the latest one) without it saying error or use edify please.
ive uploaded what ive done so far i know this is the old scripting i just don't know how to do the new one for the G2 using clockwormod recovery the latest one.im trying to flash it on cyanogenmod 7 the latest stable one for the G2
update.zip
heres the link for my "so far done job"
http://www.mediafire.com/?owi3oy71oorazxj
I'll download it later tonight, but this might help you- I think it's a similar issue.
http://forum.xda-developers.com/showthread.php?p=20440967#post20440967
---------- Post added at 05:53 PM ---------- Previous post was at 05:41 PM ----------
yeah, it looks like the same issue as that other thread. Find some roms and poke around in the updater-scripts and don't forget to add the update-binary.
Still having issues ...............But i found this http://forum.xda-developers.com/showthread.php?t=1248486 and the only problem is that idk what "Unixfy" meann....i have the script and everything ready but i need to do one last step to delet remove the MANIFEST.MF, CERT.MF and CERT.RSA from META-INF directory. Then go and "unixyfy" the line endings in META-INF/com/google/android/updater-script (emacs, vi, notepad++, any other editor). any suggestions on how to do that?
One of the Windows text editors (like Notepad or Wordpad) uses an unfriendly character to signify the end of line. Unix/Linux expects 0x0A (0A in hex) at the end of every line.
I think there is one Windows text editor that will get it right but I couldn't tell you which one off the top of my head.
If you are using a text editor like vi or nano, you should be fine. You can just open the file and save it to the proper format. You could also go in with a hex editor and poke around, but nothing good ever came of using a hex editor.
Can NotePads+++ due this and if so how
Sent from my HTC Vision using xda premium
gee one said:
I'll download it later tonight, but this might help you- I think it's a similar issue.
http://forum.xda-developers.com/showthread.php?p=20440967#post20440967
---------- Post added at 05:53 PM ---------- Previous post was at 05:41 PM ----------
yeah, it looks like the same issue as that other thread. Find some roms and poke around in the updater-scripts and don't forget to add the update-binary.
Click to expand...
Click to collapse
Do did u download and fix it for me
Sent from my HTC Vision using xda premium
Originally Posted by gee one
I'll download it later tonight, but this might help you- I think it's a similar issue.
http://forum.xda-developers.com/showthread.php?p=20440967#post20440967
---------- Post added at 05:53 PM ---------- Previous post was at 05:41 PM ----------
yeah, it looks like the same issue as that other thread. Find some roms and poke around in the updater-scripts and don't forget to add the update-binary.
Click to expand...
Click to collapse
Do did u download and fix it for me
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Sorry, no. I downloaded it and diagnosed the issue. The rest is up to you. Your post indicated that notepad++ will work. Try that- simply open the file and save it as text. Then pack it all up and see if it flashes. Google around for other linux friendly text editors. Find a hex editor and take some roms apart and compare them to yours. You should be able to see the end of line 0A characters like neon socks on a black carpet. Your zip is fairly standard, you might be able to just copy another updater-script and binary and everything will magically work. Just be sure it doesn't erase everything.
Good luck! If you find other issues or run into other problems, please post.
sent from my cyanogen(mod) vision
Successs....success .....
Finally it worked...what I did was take the updter-script for the G2 from cyanogenmod 7 gapps and edited it for my apps than I saved it and didn't touch the update-binary at all after that I ziped it signed it (using apksign) and than loaded it to the sdcard...rebooted to recovery and boom evrything flashed like magic....rebooted and their were my apps
*thanks to gee one and evryone else
Sent from my HTC Vision using xda premium
How do I edit it so that it doesn't install it in the system/folder but as my personal apps...cuz some apps don't work when installed in the system/app directory?
Sent from my HTC Vision using xda premium
Probably change system to data in your script. It would be helpful if you posted your updater-script. Just the script please, not the whole rom.
sent from my cyanogen(mod) vision
So change the directory to "app" folder and edit the script so it says to install to the app directory right"?
Sent from my HTC Vision using xda premium
It will be easier if you post your script. It's not hard to change, but it's easy to mess it up completely.
update.zip
Ok so heres the scripting that i had for the installation to the"system/app" folder now i want to change it to "data/app" directory so check it out and help me
Barry:// said:
Ok so heres the scripting that i had for the installation to the"system/app" folder now i want to change it to "data/app" directory so check it out and help me
Click to expand...
Click to collapse
It looks like you are using the gapps zip as a base. Take a look at other gb zips for some inspiration.
Your apps will have to be zipped into /data/app and the prefs would be in /data/data. Note that this can have mixed results- the market might not recognize them as installed, and you might have to clear the apk's data/cache. Also, the progress bar might look odd.
Something like this might work, but as always, use at your own risk. Be sure to back up any important data in case you brick your phone.
Code:
ui_print("Mounting data...");
run_program("/sbin/busybox", "mount", "/data");
show_progress(1, 30);
ui_print("Copying data...");
package_extract_dir("data", "/data");
ui_print("Unmounting data…");
run_program("/sbin/busybox", "umount", "/data");
ui_print("Installation complete!");
Ok so it worked with your script "gee one"..I loaded your script up and it flashed like majic thanks amillion..now my apps won't force close
Sent from my HTC Vision using xda premium
Guide – Change Navbar D.P.I. in Android Jelly Bean (4.1.1)
•Thanks to Vomer for helping me learn this and answering my questions when I had them… Also for persuading me to write this guide for others users to hopefully use to learn a small bit of Android modding, which will hopefully create more publically used mods for the benefit and growth of the community. Let’s get it…
First thing is first… This guide is created with the Galaxy Nexus in mind. Even though other phone brands (Samsung, H.T.C., LG, Sony, etc.) are now upgrading their handsets to Android Jelly Bean, this guide is created with my experience with the pure Google experience in mind and pure Google O.S. *If you are using a rom with Samsung Touch Wiz, H.T.C. Sense or anything else produced/provided by another company, this isn’t for you, although it may answer some questions and get you started in the right direction…
THE TOOLS:
I’m using an ApkTool package, which were obtained from a thread created by monstaX < Credit to him!
First off, go to this webpage http://www.mediafire.com/?acrgcd0w850q0gj and download the file. File name should be “apktoolsJB.zip”. Once you have the tools downloaded, unzip them to your desktop.
Inside the unzipped file, you will locate the following files; aapt.exe; apktool.bat; apktool149.jar; apktool142.jar; apktool144.jar and baksmali.jar.
After confirming that the above listed files are present, rename “apktool149.jar” to “apktool.jar”.
That’s it for the tools, leave the file on your desktop, as this will ultimately be your workspace along with a command prompt.
I would also download 7-Zip and Notepad++ from the internet. You can Google those two programs and download them if you don’t already have them….
GETTING WINDOWS READY:
The next thing we need to do is remove the “Environmental Values”. If you have attempted to edit/mod any apks in the past, you probably set up “Environmental Values” in “Path” under “System Variables”. If you have done this, simply navigate back to “System Variables>Path” and delete the added non-sense that you added before. An example would be something like “Android\SDK\platform-tools\;” Make sure that after you’re done deleting, you leave a “;” at the end of the “Path Variable” line of text.
Now for the fun part:
DECOMPILE/COMPILE
Once you have done the above steps, you’re now ready to have some fun.
First off, you need to download a copy of the .zip file of the ROM you’re using onto your computer OR transfer a copy of the framework-res.apk and SystemUI.apk to your computer from your G-Nex. Once you have located these files, you need to place both files into the JBapktool folder that we unzipped onto the desktop earlier.
Once you have placed both files into the JBapktool folder, open the folder and shift+right-click somewhere inside the folder (NOT ON A FILE). Once you have done that and a menu has popped up, select “Open Command Window Here”.
Once the command window has opened; you need to install the framework-res.apk… Now there is a bunch of technical jargon for this but simply and easily type the following command;
java –jar apktool.jar if framework-res.apk
You will see a line that reads “ Framework installed to: C:\Users\yournamehere\apktool\framework\1.apk”
After the above line appears, you will now decompile the framework-res.apk file. To do this, type the following command;
java –jar apktool.jar d framework-res.apk
You will now see something like:
I: Loading resource table…
I: Loaded
I: Decoding file-resources…
I: Decoding values*/* XMLs…
I: Done
I: Copying assets and libs…
*DON’T CLOSE THE COMMAND PROMPT*
After you see that, you should notice that a new file has been added to the JBapktool folder, which should be named “framework-res”. Inside that folder, you will observe the following folders/files; assets; build; dist; res; AndroidManifest.xml; apktool.yml. The file that we are worried about is the “res” file. Open the “res” folder and then navigate to the “values” folder and look for a file named “dimens.xml”. The “dimens.xml” is where the magic happens. Right click on this file and open as “Edit with Notepad++”.
Once Notepad++ is open with the “dimens.xml” file open, you want to focus on three strings in the file. The strings are: 36.0dip
36.0dip
32.0dip
*For a 32 DPI nav bar, I personally use 32 for the height and 28 for the width.*
Now here, the parts of the string that we want to change are highlighted in yellow and represent the “DPI” of the nav bar. The above lines are from a “dimens.xml” file that I changed to make a “36 DPI” nav bar. Once you have made the changes to the above dimensions, just click file and save in Notepad++ and close the program.
Now to compile the “framework-res” folder back into an .apk.
Simply go back to the command prompt that we opened earlier (you shouldn’t have closed it, but if you did follow steps above to open a new one, reinstall the framework-res.apk (STEPS ABOVE) and then continue).
Type the following command;
Java –jar apktool.jar b framework-res
You will see the following (hopefully);
W:Could not find sources
I:Checking wheter resources has changed…
I:Building resources…
I:Building apk file…
After this, you should revert back to the “JBapktool” folder and navigate to “framework-res” folder>”build”>”apk”… Look for the “resources.arsc” file. THAT’S THE MONEY SHOT…
Using 7-zip, you want to open the “framework-res.apk” file that we originally began with (I would make a copy of it and put it on my desktop). Right-click on the “framework-res.apk” file, click 7-Zip and then open archive. A new window will open, showing the visible files inside the framework-res.apk. Look for the file “resources.arsc”. Delete it, locate the “resources.arsc” from the framework-res folder (framework-res>build>apk) in the JBapktool folder. Click and drag it to the unzipped original framework-res.apk file and drop it. WE’RE DONE WITH THE FRAMEWORK-RES.APK FILE.
Now simply place that file in a CWM flashable .zip file and hold tight.
Now we need to decompile the SystemUI.apk that we placed in the JBapktool folder earlier. Follow the above listed instructions to complete this, same as we did with the framework-res.apk.
Once you have the SystemUI.apk file decompiled, look for a folder in JBapktools named “SystemUI”. Inside the “SystemUI” folder, navigate to res>layout>navigation_bar.xml. We now want to open the navigation_bar.xml file with Notepadd++, so that we can delete two lines in it that would cause a larger back button on the nav bar if left intact.
Inside the navigation_bar.xml file look for the following two lines:
"@drawable/ic_sysbar_back" android:scaleType="center"
"@drawable/ic_sysbar_back_land" android:scaleType="center"
Now, we want to delete the following from both lines:
android:scaleType="center"
After deleting that line from both lines, save the file by clicking file>save and close Notepad++. Now back go back to JBapktools and to the already opened command prompt window (it should still be open).
We are now going to compile the SystemUI. To do this type the following command;
java –jar apktool.jar b SystemUI
You will see some text in the command prompt and will ultimately see I:Building APK file…
Once this is complete, navigate back to the JBapktool folder and to the SystemUI file. Once you have the SystemUI folder open, we need to navigate to build>apk and look for the following file; AndroidManifest.xml. Now this is important, we need to replace this file with the AndroidManifest.xml file from the original unzipped SystemUI.apk. So open the original SystemUI.apk with 7-zip, and copy “META-INF” and “AndroidManifest.xml”. Once you have those copied from the original unzipped SystemUI.apk, relocate back to the JBapktool folder>SystemUI>build>apk and paste both of them. If asked to replace, CLICK YES OR REPLACE ON ALL WARNINGS THAT POP UP!!!!
Now we need to back out to the SystemUI folder in JBapktool and click on the folder that is named “dist” (the “dist” folder is where the freshly compiled SystemUI.apk is located once we type in the compile command in the command prompt). Once inside the “dist” folder, you will see a SystemUI.apk file. DELETE IT… We never use the first SystemUI.apk that we compile, because we needed to added the META-INF and AndroidManifest.xml files for signing purposes. Once you have the 1st compiled SystemUI.apk deleted, return to the command prompt and enter the compile command again and compile a 2nd SystemUI.apk.
The 2nd SystemUI.apk will appear in the “dist” folder and is the usable SystemUI.apk.
Now that you have your new SystemUI.apk compiled, place it in the same CWM flashable .zip file, boot into recovery, wipe cache and dalvik cache and VOILA, you have just pimped your nav bar’s DPI.
•Remember when placing the SystemUI.apk file into your CWM .zip file to place it under /system/App. And when placing your framework-res.apk into your CWM .zip file it goes under /system/framework…
The mods and this guide take time for us to put together for your enjoyment/the improvement of the community. If I or anyone else has helped you, please hit the “Thank You” button. Thanks.
Great tutorial
Sent from my Galaxy Nexus using Tapatalk 2
Thank's man.....................
APatte111: could you upload your 32 height 28 landscape framework-res for v4 rom ?
Great guide.
If you dont want to waste time uploading....its all good anyway mate :good:
bs android said:
APatte111: could you upload your 32 height 28 landscape framework-res for v4 rom ?
Great guide.
If you dont want to waste time uploading....its all good anyway mate :good:
Click to expand...
Click to collapse
This is not the mods thread
Great job bud!
Also, remember guys - if you make a MiNCO Mod - share with other's in the MiNCO Plus+ Thread. Chances are someone else would want it too
bs android said:
APatte111: could you upload your 32 height 28 landscape framework-res for v4 rom ?
Great guide.
If you dont want to waste time uploading....its all good anyway mate :good:
Click to expand...
Click to collapse
This framework-res.apk is in place in several of the mods in the MiNCO Plus+ mods and enhancements thread that vomer began... Just download one of the mods and extract the framework-res.apk from one of the .zip files... Probably the easiest way to get it...
Sent from my Galaxy Nexus using xda premium
vomer said:
This is not the mods thread
Great job bud!
Click to expand...
Click to collapse
OK sorry for asking OP if that annoys you
APatte111 said:
This framework-res.apk is in place in several of the mods in the MiNCO Plus+ mods and enhancements thread that vomer began... Just download one of the mods and extract the framework-res.apk from on of the .zip files... Probably the easiest way to get it...
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Nice APatte, I saw it now, downloaded and tried your framework with vomers standard white for minco rom. Got the failure in back button so guess I have to wait till I get home to a computer to fix it. Thanks for the guide anyway, love different and smaller navbars.
bs android said:
Got the failure in back button so guess I have to wait till I get home to a computer to fix it. Thanks for the guide anyway, love different and smaller navbars.
Click to expand...
Click to collapse
Yeah, if by "failure" you mean the larger back key then that is being caused by the un-edited navigation_bar.xml file which is located in SystemUI.apk>res>layout... You need to delete the two lines mentioned above, re-compile the SystemUI.apk and everything should be golden. Let me know if it doesn't work and I will help ya... Good Luck
Good guide!
Great job man!! Great tutorial!
:good::good::good::good::good:
MAN CHANGE THIS IS WRONG!! Java –jar apktool.jar b frame-work
IT IS java -jar apktool.jar b framework-res
masterchif92 said:
MAN CHANGE THIS IS WRONG!! Java –jar apktool.jar b frame-work
IT IS java -jar apktool.jar b framework-res
Click to expand...
Click to collapse
Thanks, you found a typo and the one mistake in the whole guide... Appreciate that...
Sent from my Galaxy Nexus using xda premium
After looking at 5 or 6 other guides. This one is BY FAR the easiest to understand & includes everything you need to get the job done.
Thanks a ton OP!
i cant seem to find the "@drawable/ic_sysbar_back" & "@drawable/ic_sysbar_back_land" in the navigation_bar.xml file. Any help please? I must mention that i am on AndroidME CM10 1.7.0 and took both files from the cwm zip.
Only repeating line i can find is "@drawable/ic_sysbar_lights_out_dot_large" . Dont know if it is the same.
I ve done some android developing in the past. every linear_layout represents a button, right?
angelossssss said:
i cant seem to find the "@drawable/ic_sysbar_back" & "@drawable/ic_sysbar_back_land" in the navigation_bar.xml file. Any help please? I must mention that i am on AndroidME CM10 1.7.0 and took both files from the cwm zip.
Only repeating line i can find is "@drawable/ic_sysbar_lights_out_dot_large" . Dont know if it is the same.
I ve done some android developing in the past. every linear_layout represents a button, right?
Click to expand...
Click to collapse
Can you upload the navigation_bar.xml file for me so I could have a look...
*** Nice signature by the way *** LOL
Sent from my Galaxy Nexus using xda premium
APatte111 said:
Can you upload the navigation_bar.xml file for me so I could have a look...
*** Nice signature by the way *** LOL
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
here. i uploaded in my dropbox.
https://www.dropbox.com/s/7331l8fqs7a99yg/navigation_bar.xml
Thanks for the signature
---------- Post added at 08:25 PM ---------- Previous post was at 08:17 PM ----------
angelossssss said:
here. i uploaded in my dropbox.
https://www.dropbox.com/s/7331l8fqs7a99yg/navigation_bar.xml
Thanks for the signature
Click to expand...
Click to collapse
actually nevermind that... i just flashed the cwm without the systemui.apk and it seems to be working fine. lol
angelossssss said:
here. i uploaded in my dropbox.
https://www.dropbox.com/s/7331l8fqs7a99yg/navigation_bar.xml
Thanks for the signature
---------- Post added at 08:25 PM ---------- Previous post was at 08:17 PM ----------
actually nevermind that... i just flashed the cwm without the systemui.apk and it seems to be working fine. lol
Click to expand...
Click to collapse
I was going to say, it looks like they have already removed that from the navigation_bar.xml file... The description of the ROM shows that Nav Bar Options are included... You could change the DPI size, compile and see if the back button is larger (which is what deleting those two lines fix)... If it's not (which you stated it's working) then skip that step....
APatte111 said:
I was going to say, it looks like they have already removed that from the navigation_bar.xml file... The description of the ROM shows that Nav Bar Options are included... You could change the DPI size, compile and see if the back button is larger (which is what deleting those two lines fix)... If it's not (which you stated it's working) then skip that step....
Click to expand...
Click to collapse
y i only compiled the framework-res.apk but i thing now my phone became a little laggy. especially when swipping between screens and opening apps.
i'll check it out if i did anything wrong.
angelossssss said:
y i only compiled the framework-res.apk but i thing now my phone became a little laggy. especially when swipping between screens and opening apps.
i'll check it out if i did anything wrong.
Click to expand...
Click to collapse
Check in the ROM and see if there is already a built in option to change the nav bar DPI size... if not, make the changes to the dimens.XML file and then recompile/replace the .apk and re-flash... that should work and everything should be normal...
Sent from my Galaxy Nexus using xda premium
APatte111 said:
Check in the ROM and see if there is already a built in option to change the nav bar DPI size... if not, make the changes to the dimens.XML file and then recompile/replace the .apk and re-flash... that should work and everything should be normal...
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
unfortunately there is not. it only has options to change the buttons order.
I'm having real problems unzipping the above file to show the .img file. The error I keep getting is "Winzip only supports IMG files that are in the ISO format" I have tried to downloading Winrar and 7 Zip file manager but still cannot get it unzipped.
Please, can anybody help, i'm so frustrated!
Thanks
Matt:fingers-crossed:
Are you trying to open a img file with winrar for see the code/stuff into it?
Guich said:
Are you trying to open a img file with winrar for see the code/stuff into it?
Click to expand...
Click to collapse
Hi, I'm trying to put it in my drive so I can flash it, if that makes sense. Really sorry, I'm new to this!
The Mackem said:
Hi, I'm trying to put it in my drive so I can flash it, if that makes sense. Really sorry, I'm new to this!
Click to expand...
Click to collapse
Ah, you will extract this for put into adb/fastboot folder for flash
So, when you have the winrar windows, drop the file and put it into the folder or the desktop.
Now you can flash/use it
vywood which
Guich said:
Ah, you will extract this for put into adb/fastboot folder for flash
So, when you have the winrar windows, drop the file and put it into the folder or the desktop.
Now you can flash/use it
Click to expand...
Click to collapse
Hi, Guich, Am I actually trying to unzip the file to see to the image??? is this what I need to put it in the db/fastboot folder for flash :good:
I have tried that but I'm still getting the same error message!
The Mackem said:
Hi, Guich, Am I actually trying to unzip the file to see to the image??? is this what I need to put it in the db/fastboot folder for flash :good:
I have tried that but I'm still getting the same error message!
Click to expand...
Click to collapse
I can't do some screen now, however, it's strange.
Can you post a screen of your prob?
Guich said:
I can't do some screen now, however, it's strange.
Can you post a screen of your prob?
Click to expand...
Click to collapse
View attachment Book1.xlsx
Hope this helps??
The Mackem said:
Hi, Guich, Am I actually trying to unzip the file to see to the image??? is this what I need to put it in the db/fastboot folder for flash :good:
I have tried that but I'm still getting the same error message!
Click to expand...
Click to collapse
dude, the .img IS THE 'image' file. You don't need to unzip it or anything, just flash it through fastboot.
It's not a compressed .zip file -__-
The Mackem said:
View attachment 1997963
Hope this helps??
Click to expand...
Click to collapse
But the boot.img is in img already...
Now you have to flash it
tomascus said:
dude, the .img IS THE 'image' file. You don't need to unzip it or anything, just flash it through fastboot.
It's not a compressed .zip file -__-
Click to expand...
Click to collapse
Thank you, I'll give it a go.......................talk about totally frustrated!!!
GGGGGGGGGGGRRRRRRRRRRRRRR!! lol
:shakes head in a disappointed manner:
Really guys? REALLY?
Just help the OP out if you can, if not, move along.
Thread cleaned.
I'm getting tired of the chimey unlock sound. I've successfully replaced other ui sounds in /system/media/audio/ui but the unlock sound is not located there. I've tried searching the filesystem for all oggs and mp3s and nothing looked right. Where is it?
Not on my phone right now but I'm pretty sure it's there. Hold on.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
elesbb said:
Not on my phone right now but I'm pretty sure it's there.
Click to expand...
Click to collapse
It looks like it's there, but Unlock.ogg and Unlock_none_effect.ogg aren't the right sound if you listen to them. lens_flare_unlock_silence.ogg is... silence.
I believe it is in framework-res.apk or twframework-res.apk last time I checked. /system/framework/
Sent from my SGH-M919 using Tapatalk 4 Beta
ThisThing said:
It looks like it's there, but Unlock.ogg and Unlock_none_effect.ogg aren't the right sound if you listen to them. lens_flare_unlock_silence.ogg is... silence.
Click to expand...
Click to collapse
Ah yes.
tonytien said:
I believe it is in framework-res.apk or twframework-res.apk last time I checked. /system/framework/
Sent from my SGH-M919 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Inside Res/raw that's where it is.
Sent from my SGH-M919 using Tapatalk 2
Excellent, thank you. It's framework-res.apk/res/raw/lens_flare_unlock.ogg.
So do I just replace it, zip everything back up, rename it to .apk, push it to the phone and reboot? It's gotta be more complicated than that
ThisThing said:
Excellent, thank you. It's framework-res.apk/res/raw/lens_flare_unlock.ogg.
So do I just replace it, zip everything back up, rename it to .apk, push it to the phone and reboot? It's gotta be more complicated than that
Click to expand...
Click to collapse
I figured I might have to use elesbb's GUI apk tool. So tell me if this procedure is correct:
Open framework-res.apk in winrar (or whatever)
Replace the relevant .ogg file (just a binary - no messing with xml so I shouldn't have to recompile.)
Plug phone in
Open the apk tool
Choose framework-res.apk as file to work on
Check 'Install signed APK after signing?'
Hit the Signing Tool button...
Then it should just work? I'm being super cautious since framework-res seems to be very important and I'm sure the phone won't work if it's messed up.
ThisThing said:
I figured I might have to use elesbb's GUI apk tool. So tell me if this procedure is correct:
Open framework-res.apk in winrar (or whatever)
Replace the relevant .ogg file (just a binary - no messing with xml so I shouldn't have to recompile.)
Plug phone in
Open the apk tool
Choose framework-res.apk as file to work on
Check 'Install signed APK after signing?'
Hit the Signing Tool button...
Then it should just work? I'm being super cautious since framework-res seems to be very important and I'm sure the phone won't work if it's messed up.
Click to expand...
Click to collapse
Copy your framework-res.apk to your desktop just in case u need to swap.
Sent from my SGH-M919 using Tapatalk 2
Good call on the backup DigitalUnderground - yeah, I have a couple which I keep having to use.
Unfortunately, no matter what I try the phone hangs on boot at the end of the T-mobile animation. Here's the procedure that I've pieced together from several threads:
[This should work but doesn't]
Open framework-res.apk in winrar and replace the files by dragging and dropping.
(Don't sign the file here because it's a system file.)
zipalign the apk
Reboot into recovery and replace the original with the modified file
chmod 644 the file
Reboot
Profit?
But, I'm not profiting I just get stuck during boot. This is driving me nuts.
Is this correct - or at least is there a way to check some logs to see what's going wrong?
I would guess... if u don't have to de/recompile the apk... just open with 7zip or winrar and swap files... but I think u may have already tried that... hmmm
Sent from my SGH-M919 using Tapatalk 2
I figured it out! I needed to use logcat during the bootloop and dig through its output. Long story short the replacement files must be added uncompressed to the archive.
I made a whole post with the full procedure here: http://forum.xda-developers.com/showthread.php?p=43944673#post43944673
ThisThing said:
I figured it out! I needed to use logcat during the bootloop and dig through its output. Long story short the replacement files must be added uncompressed to the archive.
I made a whole post with the full procedure here: http://forum.xda-developers.com/showthread.php?p=43944673#post43944673
Click to expand...
Click to collapse
That's one insane method lol. Congrats on figuring out a way to do it though.
Sent from my SGH-M919 using Tapatalk 2
Like many of you new flashers, I have flashed the SkyDragon ROM and have noticed that there is no connectivity to the computer whatsoever, so I did a little digging. I went back and forth between 2 Nandroid backups and kept flashing parts of them until I could narrow down where this problem was coming from. I found out that it comes from the specific folder - data/property
There is a missing file called persist.sys.usb.config ,13B in size, and I have no idea what it does (maybe some of you could enlighten me) but throwing the old file into that folder, changing the permissions to rw-------- and rebooting worked like a charm.
I apologize for not sticking this into the development thread, however I'm a lurker with no input! :victory:
Without further ado,
I TAKE NO RESPONSIBILITY FOR ANY BORKEN DEVICES. IF YOU DON'T KNOW WHAT YOU'RE DOING, DON'T DO IT!
1. Download Root Browser and RB Text Editor
2. Navigate to /data/property
3. On the bottom bar, tap the "New" button
4. Click on "New file"
5. Enter the file name as follows:
persist.sys.usb.config
6. Click the file you just made and hit "Open as..."
7. Hit "Text file"
8. Click RB Text editor
9. Delete whatever is there and enter as follows:
auto_conf,adb
No spaces or caps!
10. Save the file by clicking the save button on the top right corner.
11. Reboot your phone
12.Profit
----------------------------------------------------------------------------------------------------------------------------------------
Steal this information, spread it around, someone post it to the development thread and make this ROM better!
If you're having any problems, don't hesitate to ask
i could just drop this in the proper location before flashing the rom yes ??
CheesyNutz said:
i could just drop this in the proper location before flashing the rom yes ??
Click to expand...
Click to collapse
Only if you're going to dirty flash it, but at that point, I'd just dirty flash it anyways. The file should already be there if you're on a ROM that can recognize your phone. I also do recommend a clean flash. I'm sorry if I made this difficult. When flashing the rom, it'll format /data which is where the file is held so if you had the file there already, it would just wipe it.
88keys6strings said:
Only if you're going to dirty flash it, but at that point, I'd just dirty flash it anyways. The file should already be there if you're on a ROM that can recognize your phone. I also do recommend a clean flash. I'm sorry if I made this difficult. When flashing the rom, it'll format /data which is where the file is held so if you had the file there already, it would just wipe it.
Click to expand...
Click to collapse
i was talking from a clean install
drop file in the proper location then wipe phone flash rom with new file and them proceed to set up the phone
CheesyNutz said:
i was talking from a clean install
drop file in the proper location then wipe phone flash rom with new file and them proceed to set up the phone
Click to expand...
Click to collapse
As long as it's after the wipe then yes. If you opened up the zip that contains the ROM, you could head into /data then create a new folder called property and throw the file in there then zip it back up and flash it. But you MUST put the file in /data/property AFTER you flash the ROM. You could drop the file into a downloads or media folder because those don't get touched then flash the rom then move it and change permissions then reboot as well.
So no, you cannot drop the file in it's PROPER location before you wipe, otherwise it'll get deleted. However, you can copy/paste it into say, mnt/sdcard/Download, via your root browser, beforehand then follow my instructions
I'll try when I get home in about six hours.
partylikeaninjastar said:
I'll try when I get home in about six hours.
Click to expand...
Click to collapse
For sure! Will await results
I hope the developers get to see this for the next update
I tried creating my own file as per the instructions (came to 13b size for the file too), but my phone isn't being recognized in android file transfer.
Then again, it wasn't recognized either when I was on stock rom (prior to flashing anything).
On my phone, the file already existed. Its contents read....
Code:
boot,adb,mtp
I changed it accordingly based on your instructions, reboot and nothing.
I found that if you turn USB debugging off, then on again, the file will get overwritten with the original code...boot,adb,mtp.
Could it be that this command simply enables USB debugging? That's what my testing showed. I turned off debugging, made the file change, reboot and debugging was enabled. Disable debugging and the file gets overwritten. Rinse, repeat. If I delete the file, it is recreated when enabling USB debugging....boot,adb,mtp.
Just a preliminary finding. I'm not well versed enough to explain or troubleshoot it any further. It did nothing to cure my USB problem.
Cablespider said:
On my phone, the file already existed. Its contents read....
Code:
boot,adb,mtp
I changed it accordingly based on your instructions, reboot and nothing.
I found that if you turn USB debugging off, then on again, the file will get overwritten with the original code...boot,adb,mtp.
Could it be that this command simply enables USB debugging? That's what my testing showed. I turned off debugging, made the file change, reboot and debugging was enabled. Disable debugging and the file gets overwritten. Rinse, repeat.
Just a preliminary finding. I'm not well versed enough to explain it further. It did nothing to cure my USB problem.
Click to expand...
Click to collapse
I may have overlooked something. I deleted some usb portion of the build.prop. Didn't change anything so i didnt think about it. If you make a backup then edit it deleting the usb part, then reboot that might get it to work.If you need specifics, I'll be next to a computer in about an hour and a half
Can someone just post the file here?
Sent from my LG-D851
---------- Post added at 10:44 PM ---------- Previous post was at 10:36 PM ----------
I copied one of the persist.sys files from that folder to my sdcard and edited it with Rom Toolbox Pro. I opened it as a text file and deleted what was there, then added the stuff in the OP and saved. I then renamed the file to persist.sys.usb.config and added it to that folder and changed permissions and rebooted. Worked fine.
Sent from my LG-D851
Skizzy034 said:
Can someone just post the file here?
Sent from my LG-D851
---------- Post added at 10:44 PM ---------- Previous post was at 10:36 PM ----------
I copied one of the persist.sys files from that folder to my sdcard and edited it with Rom Toolbox Pro. I opened it as a text file and deleted what was there, then added the stuff in the OP and saved. I then renamed the file to persist.sys.usb.config and added it to that folder and changed permissions and rebooted. Worked fine.
Sent from my LG-D851
Click to expand...
Click to collapse
Awesome! Glad it worked for you
This is from my stock rom with the modified skydragon kernel. place in root\data\property. let me know if this works. just rename it and drop the .zip part.
Cablespider said:
On my phone, the file already existed. Its contents read....
Code:
boot,adb,mtp
I changed it accordingly based on your instructions, reboot and nothing.
I found that if you turn USB debugging off, then on again, the file will get overwritten with the original code...boot,adb,mtp.
Could it be that this command simply enables USB debugging? That's what my testing showed. I turned off debugging, made the file change, reboot and debugging was enabled. Disable debugging and the file gets overwritten. Rinse, repeat. If I delete the file, it is recreated when enabling USB debugging....boot,adb,mtp.
Just a preliminary finding. I'm not well versed enough to explain or troubleshoot it any further. It did nothing to cure my USB problem.
Click to expand...
Click to collapse
Jephre said:
I tried creating my own file as per the instructions (came to 13b size for the file too), but my phone isn't being recognized in android file transfer.
Then again, it wasn't recognized either when I was on stock rom (prior to flashing anything).
Click to expand...
Click to collapse
partylikeaninjastar said:
I'll try when I get home in about six hours.
Click to expand...
Click to collapse
CheesyNutz said:
i was talking from a clean install
drop file in the proper location then wipe phone flash rom with new file and them proceed to set up the phone
Click to expand...
Click to collapse
UPDATED
Much easier now. Just tested it with a Nand that didn't work at all and followed the instructions and it worked flawlessly. Let me know if you have any more issues
aclegg2011 said:
This is from my stock rom with the modified skydragon kernel. place in root\data\property. let me know if this works. just rename it and drop the .zip part.
Click to expand...
Click to collapse
It should work just fine as long as you didn't actually compress it lol. Thank you for the upload!
ALSO
THIS IS MY 10TH POST!!! DEV SECTION HERE I COME!! :victory:
88keys6strings said:
1. Download Root Browser and RB Text Editor
2. Navigate to /data/property
3. On the bottom bar, tap the "New" button
4. Click on "New file"
5. Enter the file name as follows:
persist.sys.usb.config
6. Click the file you just made and hit "Open as..."
7. Hit "Text file"
8. Click RB Text editor
9. Delete whatever is there and enter as follows:
auto_conf,adb
No spaces or caps!
10. Save the file by clicking the save button on the top right corner.
11. Reboot your phone
12.Profit
Click to expand...
Click to collapse
I can now confirm that this does work. I now have working MTP again.
You guys could try adding "persist.sys.usb.config=mtp,adb" to the build.prop and see if that works.