Ok so when i wrote the title for this post, there where other posts that came up, but none of them are geared towards the nook color. I looked in the system folder but nothing was there with the build prop file name just a build. Can someone point me in the right direction on what to change. I am thinking of changing the file to match either my Droid Eris or a Nexus S. Or even a tablet?
Not sure I understand exactly what you're asking, but the build.prop is in /system. Sounds like you would want to change the build fingerprint, but you need to look at the one from your phone to make sure you know what to change it to.
I tried that but there are 2 flies located in the system folder, one that says build, and another that says build prop. The Nook Color does not have that second folder so I do not know what to change to change the fingerprint of the device.
Wrong thread
waffleb051 said:
I tried that but there are 2 flies located in the system folder, one that says build, and another that says build prop. The Nook Color does not have that second folder so I do not know what to change to change the fingerprint of the device.
Click to expand...
Click to collapse
build.prop is the file you will be changing... the fingerprint is one of the settings inside build.prop
ianPhillips1 said:
Wrong thread
Click to expand...
Click to collapse
As of now yes
DizzyDen said:
build.prop is the file you will be changing... the fingerprint is one of the settings inside build.prop
Click to expand...
Click to collapse
Ok I'll whip up so modded buil.prop files test them then upload them on this thread.
Related
What is the file we need to change to be able to change "Sprint" to whatever we want? Running Test4
DirtyShroomz said:
What is the file we need to change to be able to change "Sprint" to whatever we want? Running Test4
Click to expand...
Click to collapse
Not sure but I believe jschisurf found a way to remove it and I'm sure knows how to change the name too
DirtyShroomz said:
What is the file we need to change to be able to change "Sprint" to whatever we want? Running Test4
Click to expand...
Click to collapse
The file is eri.xml.
/system/etc in dd 2.7 you wont find it in test 4 you need to download dd and pull the file from the zip edit it to what you want it to say and then puch it to /data on your phone and it will change the lockscreen and notification bar
will give a shot, gracias my good friends from xda
eri...
shabbypenguin said:
/system/etc in dd 2.7 you wont find it in test 4 you need to download dd and pull the file from the zip edit it to what you want it to say and then puch it to /data on your phone and it will change the lockscreen and notification bar
Click to expand...
Click to collapse
the eri.xml file is located in /system/etc?
i may just edit this. thank you thank you
I tried this on my sense based rom, it doesnt seem to work. Does that file go in another location in sense rom's? Or is it not going to work at all? thanks
I guess it is not possible.
you need CDMA workshop and then you can go in an edit the sprint information.
Do a search for on google.
Any Updates on This Topic? How To change the Sprint name on the lockscreen.
I'm Running Fresh and eri.xml file is not there...
Flash CM6 and there are settings to change all sorts of things including this. I'm sure some will say they won't flash it because its not Sense, but it is by far the fastest out there.
unCoRrUpTeD said:
Flash CM6 and there are settings to change all sorts of things including this. I'm sure some will say they won't flash it because its not Sense, but it is by far the fastest out there.
Click to expand...
Click to collapse
In CM6 there are only options to change the color of it, not actually what it says.
kwheel596 said:
In CM6 there are only options to change the color of it, not actually what it says.
Click to expand...
Click to collapse
True, Only the color, anyone has an update of this Topic?
why cant i alter the eri.xml file? i havent tried it but im definitely gonna give it a whirl.
In cm6 there's a way to hide it. That's the route I took. I tried the eri.xml and couldn't get it to work. Its not reading the value from the base band chip as my NAM is ACS and it says SPRINT in the ROM.
I'm having a problem getting my OG Droid to play an included boot sound with a new boot animation.
I'm running ChevyNo1's Simply Stunning 5.5 (Android 2.3.5) and it gladly accepts the new bootanimation.zip when I place it in /system/media
There is a Bionic.ogg that comes with this boot animation and according to the "desc.txt" inside the bootanimation.zip it says the following:
"sounds will be loaded from /system/media"
So I placed Bionic.ogg inside /system/media like the boot animation's own script file told me to. When I reboot my phone, I don't get the sound. My volume setting is cranked up all the way too.
I have even gone so far as to change permissions on bootanimation.zip and Bionic.ogg to rwxrwxrwx but to no avail.
I'm not sure what else I can do. Any thoughts?
Edit:
I found more info at this thread here: http://forum.xda-developers.com/showthread.php?t=1029099
Unfortunately those instructions do not seem to work. I did everything as I was told in those instructions too. Can the Droid even do boot audio? I swear it could a long time ago when I was stock.
Try and look in build.prop for ro.config.play.bootsound and change the value to 1 if it isn't already.
Sent from my Milestone using xda premium
skadude66 said:
Try and look in build.prop for ro.config.play.bootsound and change the value to 1 if it isn't already.
Sent from my Milestone using xda premium
Click to expand...
Click to collapse
Sadly, this didn't work. My build.prop did not include this line in the first place.
Here's a screenshot of the build.prop I placed into /system that includes highlighting where I placed ro.config.play.bootsound=1
Is there a different place in the build.prop that this parameter should be entered?
projektorboy said:
Sadly, this didn't work. My build.prop did not include this line in the first place.
Here's a screenshot of the build.prop I placed into /system that includes highlighting where I placed ro.config.play.bootsound=1
Is there a different place in the build.prop that this parameter should be entered?
Click to expand...
Click to collapse
Nope, anything in build.prop will be run, regardless of where it is, it shouldn't have an issue. If you really want to try it, then you can place it at the complete top of build.prop and see.
skadude66 said:
Nope, anything in build.prop will be run, regardless of where it is, it shouldn't have an issue. If you really want to try it, then you can place it at the complete top of build.prop and see.
Click to expand...
Click to collapse
I moved the line to the very top of build.prop and still nothing. I guess I'll just have to go without sound. It was worth a shot. Seems like something else just keeps overriding it.
If you look in /system/bin, you will find the bootanimation binary. The binary on our Droids doesn't support sound. Somewhere floating around though is a bootanimation binary that does. I originally found it on androidforums.net but unfortunately can't find the post anymore. Liquid aGirl had it posted somewhere.
Most of the guides ive read on XDA say you have to decompile and recompile APKS just to make a couple of modifications to the images. Well I dont believe this to be true. I have tested my method on ubuntu 14.10 and with my nexus 5.
This guide is specifically for modifying images inside of the apks, not the code, or xml itself.
- ADB pull the APK file you want to modify (i chose SystemUI.apk)
- Double click it in File Manager on ubuntu, this should open it up in the archive manager. If not, manually open it up in archive manager
- Click on the "Add Files" button and select which files you want to replace. It will automatically overwrite the current ones.
- Make sure that you are keeping the proper directory structure and are putting the images in the proper place with proper names.
- Copy the new APK file back to your device on /sdcard/file.apk
Then, to get the APK file back on your system without causing problems, I rebooted into TWRP, mounted system and went into the file manager and copy/pasted the APK in the appropriate folder. When you get back into android, chmod 644 new-file.apk. I would not suggest trying to copy the modified APK file into your system while android is running live. Thats why I did it in TWRP. It could cause system unstability, crashing, etc... Im sure that I am not the first person to realize this could be done, but I did discover this on my own because I like to try things. PLEASE, make a backup in case something doesnt work correctly after your mod. Good luck!
bynarie said:
Most of the guides ive read on XDA say you have to decompile and recompile APKS just to make a couple of modifications to the images.
Click to expand...
Click to collapse
Mine doesn't.
XperienceD said:
Mine doesn't.
Click to expand...
Click to collapse
Um, not to be rude but the guide on your signature shows using apktool to decompile and recompile. Soo....? Unless its another guide. And Im not saying ALL guides are, but some, and thats ok. Could you link me to your guide please? I would love to take a look at it. Thanks
EDIT - woops im sorry i didnt really read it... i do see where it says drag and drop the images... good deal. sorry
bynarie said:
Um, not to be rude but the guide on your signature shows using apktool to decompile and recompile. Soo....?
Click to expand...
Click to collapse
Edit: No need for my original reply as you found it.
XperienceD said:
Edit: No need for my original reply as you found it.
Click to expand...
Click to collapse
Yes, and your guide is very good. Thank you for that.
Here it is -
Please, i need your help, people!
What do you mean? Does it just yell at you for using an unsigned APK when trying to install on your Nook, or does it need to be signed by a certain developer?
Done
Well, either way, I signed it for you here.
Unfortunately, my NST is no longer working so I didn't try installing it. It didn't work on my phone (because it's not a Nook), but that has nothing to do with signing the apk.
Thanks, clavierkid!
I have copied modified version in /system/app/, but it doesn't appear in Nook's system menu.
I noticed, that in afore-mentioned folder there is no such file as ReaderRMSDK.odex...?
Probably this is the reason for non-working reader.
Please, someone to share its ReaderRMSDK.odex file here for me!
Thanks
gsms said:
Thanks, clavierkid!
I have copied modified version in /system/app/, but it doesn't appear in Nook's system menu.
I noticed, that in afore-mentioned folder there is no such file as ReaderRMSDK.odex...?
Probably this is the reason for non-working reader.
Please, someone to share its ReaderRMSDK.odex file here for me!
Thanks
Click to expand...
Click to collapse
We'd better get something straight here first. Are you talking about an actual Nook Simple Touch (NST)? Because if you are, you are correct that there is no ReaderRMSDK.odex file in /system/app/
But there are no *.odex files at all! I don't think odexing even occurred to the Android 2.1 developers. So, which device do you have?
The device is Nook Simple Touch and there are other .odex files in /system/app/ !
gsms said:
The device is Nook Simple Touch and there are other .odex files in /system/app/ !
Click to expand...
Click to collapse
And what ROM are you running? Humor me and go to your "Settings" app. Under "Device Info" check out "About your Nook". The model number should be BNRV300. The Software version on mine is 1.21
I did a complete device search for files ending in *.odex and came up with none. But I am running the stock ROM (with many changes, but still the basic stock).
For what it's worth:
This APK uses lots of privileged permissions and will not operate 100% correctly unless it is signed with the system signature.
Is the APK something that you modified? Why don't you just use the stock one?
If you are going to use it you will have to resign your whole system.
(Also, you should look up "jarsigner" and learn to sign for yourself.)
I am rooted with Busybox installed via magisk. SU root check was done and i am rooted for sure. However i cannot seem to modify the build.prop file. Can anyone advice please
Install Solid Explorer and try again edit with this file explorer
Trevorek said:
Install Solid Explorer and try again edit with this file explorer
Click to expand...
Click to collapse
Good looking app however it can not copy the cache to the system/build.prop.
In other words, it can not save changes like everything else
FKX1997 said:
Good looking app however it can not copy the cache to the system/build.prop.
In other words, it can not save changes like everything else
Click to expand...
Click to collapse
i had this problem with new version of magisk (23 beta+)
now i use older version ,everything work fine (full control on system files)
(i use mixplorer)
loopypalm said:
i had this problem with new version of magisk (23 beta+)
now i use older version ,everything work fine (full control on system files)
(i use mixplorer)
Click to expand...
Click to collapse
Which version are you using please
Update, checked my root and it is all working as it should be, yet i can not write to system. I have access to ADB but i need to add "ro.debuggable=1" to build.prop to do more work on the phone
FKX1997 said:
Which version are you using please
Click to expand...
Click to collapse
right now i use 21.1
loopypalm said:
right now i use 21.1
Click to expand...
Click to collapse
Just add the prop edit to a magisk flashable zip
In magisk flashable zip empty go to common/system.prop edit with text editor and add the prop you want to change then flash zip
toolhas4degrees said:
Just add the prop edit to a magisk flashable zip
In magisk flashable zip empty go to common/system.prop edit with text editor and add the prop you want to change then flash zip
Click to expand...
Click to collapse
Too many things to just edit a prop ...
plus the prop was not the only problem i got, i could not write to some folders in system
i think he fixed the problem in 24 ,but i'll keep using 21.1 anyway ...
loopypalm said:
Too many things to just edit a prop ...
plus the prop was not the only problem i got, i could not write to some folders in system
i think he fixed the problem in 24 ,but i'll keep using 21.1 anyway ...
Click to expand...
Click to collapse
Really it's not to many things it literally takes 20 seconds. I know the issue. And the dynamic part one are mainly it. That's why I suggested what I told you.
toolhas4degrees said:
Really it's not to many things it literally takes 20 seconds. I know the issue. And the dynamic part one are mainly it. That's why I suggested what I told you.
Click to expand...
Click to collapse
I think he'd rather take the chance of boot looping your advice was the best so far
loopypalm said:
Too many things to just edit a prop ...
plus the prop was not the only problem i got, i could not write to some folders in system
i think he fixed the problem in 24 ,but i'll keep using 21.1 anyway ...
Click to expand...
Click to collapse
Sadly the issue persists and i haven't made a magisk module before so i may need some help on that one please
I added it to the cloudflare 2.7 zip, i expect i shouldn't see it in the build.prop still but it would be loaded in memory? as i have it in the build.prop, the line i wish to have but set to 0 when i have set it to 1 on the system.prop file
(to clarify the line was in the build,prop by stock set to 0)