Related
Is it possible to edit and copy over image files contained in the ROM without destabilizing it? I am rather adept at photoshop...but my ROM is running so clean...I'd rather not cause it to go wonky
htc rom 6.0 standard...
Not really sure what images you're trying to change, but this might help....
http://forum.xda-developers.com/showthread.php?t=341753
Read the whole thread. Helpful stuff.
skyline247 said:
Not really sure what images you're trying to change, but this might help....
http://forum.xda-developers.com/showthread.php?t=341753
Read the whole thread. Helpful stuff.
Click to expand...
Click to collapse
I don't think that thread will help him/her 'cause would need to flash for that, and he's trying to keep the rom the way it is, from what he said.
roloracer said:
I don't think that thread will help him/her 'cause would need to flash for that, and he's trying to keep the rom the way it is, from what he said.
Click to expand...
Click to collapse
Very true. That would change his ROM. He/she didn't post what images he/she wanted to change, so not sure what they would like to do. I know that on other ROM's I have changed the boot and splash screens by overwriting the .PNG files, but I cannot find said files on this ROM, so it will probably involve flashing.
cont...
hewhoisnotasothers said:
Is it possible to edit and copy over image files contained in the ROM without destabilizing it? I am rather adept at photoshop...but my ROM is running so clean...I'd rather not cause it to go wonky
htc rom 6.0 standard...
Click to expand...
Click to collapse
I found that using the htc unlock in this thread that you could then use a good explorer program, and copy over any images needed....I am trying to figure out what file to overwrite to change the startup splash screen, but otherwise this method works well....i now have personalized the images...such as the htc banner in contacts, and the in-call bg.
p.s.- this is a better alternative than alphanuma....at least on the rom i am running....
hey guys,
i was wondering if there was a way like there is to change the banner name from sprint using CDMA, but to change the software name of the rom itself?
i''ve customized my rom so much and still plan on making many other changes, and i would like to reflect that on the rom name as well but can't seem to turn up anything with search...
thanks a ton
The name is in the buildprop
i know when you typed that up it was extremely clear in your mind...
but, where is buildprop? only tools i've used so far are QPST, CDMA, adb, and xUltimate....any of those have access to buildprop or is that through one of the "kitchens"?
lol. Sorry
The build.prop is in the system folder. There are many different ways to access it but the easiest way is probably with the phone itself.
You can use root explorer to mount r/w and edit it with the phone. Once you finish, remount r/o.....reboot and done.
Why is it that important to change the name of the Rom? The only place I can think that it really shows that is in about software. So unless you are trying to take credit for someone elses rom and show it off what would be the advantage ?
Most roms are built off others. Just give credit where credit is due.
this is not going to be shown to anyone else. and yeah a rom is built off another rom, but then the rom i'm downloading, which was built off another, should have that original rom's name, not the new one...so?
this is a change for me, and only for me.
thanks for the help bluebeast, made the change already
I followed this guide to change my Sprint banner a number of months ago. http://forum.xda-developers.com/showthread.php?t=889891&highlight=Edit+Sprint+Banner. My question is this... What exactly did following that method change? The reason I ask, is because no matter what ROM I flash, and no matter what changes I make, that modification remains. It always says my name on the lockscreen, and notification bar. So I was curious, what did that method actually modify, because nothing wipes the mod out. Wiping, doesn't change anything with it. I'm fine with that, and have no interest in changing it back, but I was just simply curious, about what the heck that method changed, that allows the mod to remain no matter what. I don't understand how a complete wipe of the phone doesn't wipe the mod out. The other method, by JsChirf, which requires hex editing some xml files, seems like if you were to do a full wipe and reflash after applying that mod, that the mod would get wiped out, and you'd need to re do it after flashing a different ROM, because it appears as though the xml files that get edited are within the framework-res.apk, which would get replaced when you reflash a rom, thus wiping out the mod. Is that correct? If so, my questions is, does anyone know what I actually modified when I followed the method that I did, and why the mod remains no matter what type of changes I make to my phone? Again, it's just out of curiosity, no actual problems here. Thanks in advance, if anyone knows.
Changes the strings.xml in the framework-res.apk
I've had the mod since I received my Evo and flashed many roms and still have the mod. You would think switching between aosp and sense and what not that it would disappear. It's MAGIC.
blakeboys said:
Changes the strings.xml in the framework-res.apk
I've had the mod since I received my Evo and flashed many roms and still have the mod. You would think switching between aosp and sense and what not that it would disappear. It's MAGIC.
Click to expand...
Click to collapse
So does JsChirf's hex edit method work the same way? As in, the mod remains no matter what you flash/wipe/change? Unless you were to repeat the mod, except editing it back to the orignal "sprint" banner? I haven't used his method, but by reading through it, it looked as though you need to edit a couple of xml files in the framework-res.apk. If that's the case, and you flash a different rom (which contains a new framework-res.apk), wouldn't you lose the mod? Or am I missing something?
And thanks for the response.
k2buckley said:
So does JsChirf's hex edit method work the same way? As in, the mod remains no matter what you flash/wipe/change? Unless you were to repeat the mod, except editing it back to the orignal "sprint" banner? I haven't used his method, but by reading through it, it looked as though you need to edit a couple of xml files in the framework-res.apk. If that's the case, and you flash a different rom (which contains a new framework-res.apk), wouldn't you lose the mod? Or am I missing something?
And thanks for the response.
Click to expand...
Click to collapse
Cant help ya there boss. I used the cdma workshop since it looked alot easy.
blakeboys said:
Cant help ya there boss. I used the cdma workshop since it looked alot easy.
Click to expand...
Click to collapse
Yea I hear ya, it was just out of curiosity. I was going to use the hex edit method for my friend's Evo, just to try it out. It looks kind of fun. I was just unsure if doing it that way would cause the mod to stick, as it does with my phone. Thanks for the help though.
k2buckley said:
Yea I hear ya, it was just out of curiosity. I was going to use the hex edit method for my friend's Evo, just to try it out. It looks kind of fun. I was just unsure if doing it that way would cause the mod to stick, as it does with my phone. Thanks for the help though.
Click to expand...
Click to collapse
No the hex method works using xml files inside the framework-res.apk and htclockscreen.apk so when you change roms it will change back to sprint. This method is very simple way to do it.
Sent from my unrEVOked using xda app
Brah...don't use that method. use this > http://forum.xda-developers.com/showthread.php?t=866553
Worked for me, works after flashing roms as well.
I know all bout this..courtesy of Roxx xD
sent from that one guy.
jacoballen22 said:
I know all bout this..courtesy of Roxx xD
sent from that one guy.
Click to expand...
Click to collapse
Seee I show you exhibit A...that did it and worked.
How to USE EVO on Other network .
I am fish that swims in GSM side ( HD2) of the forum , Any help for the below will be much appreciated . I searched and searched and searched ...Finally info about CDMA workshop .. But can we do it with it .
i got this EVO from sprint and would like to use it with another cdma provider from my country ( INDIA ) .. i took it to them and they said its network locked .. .Can we do something to take the Sprint lock from the phone and use another CDMA network ...
If you guys cant post it in the open forum , please PM ME ..
teh roxxorz said:
Brah...don't use that method. use this > http://forum.xda-developers.com/showthread.php?t=866553
Worked for me, works after flashing roms as well.
Click to expand...
Click to collapse
Haha, so simple! The qpst thing was pretty easy too, I used it a while back. Today I just tried jschirfs hex edit method for another Xda member. That wasn't hard, but sucks that its wiped any time the framework-res.apk changes. Anyways, thanks for the responses.
Sent from my PC36100 using XDA App
Hi guys!
I think the need of repacking and repacked images for every kernel-rom combination is a huge nuisance.
What would be if ROMs would contain their ramdisk on the system partition, and the kernels would just contain a minimal ramdisk that loads the ROMs ramdisk?
One idea:
My first idea would break compatibility with system recovery zips, so a little modified:
There would be a new "ramdisk" directory on system partition, that would containt all the ramdisk files a ROM should have, except the system folder.
So it would contain:
bin
etc
data
...
init.rc
...
and so on.
The init in the actual ramdisk would mount system first, and then make the links:
/bin -> /system/ramdisk/bin
/etc -> /system/ramdisk/etc
/data -> /system/ramdisk/data
...
and then we would include init.rc from /system/ramdisk.
Of course all the ROMs would need to change, but after that, there would be no need for repack. Also for the old ROMs, factory ROM, some could still repack.
That's a nice idea! I thought a little bit about it and here are my thoughts (a novice, please don't laugh at me :silly:
if I understand your idea correctly, your intention is to store the specific ROM's ramdisk in the rootfs, and make a global, generic ramdisk which will be stored in all the kernels.
Upon loading the kernel's ramdisk, it will know to take the ROM's ramdisk from the rootfs (upon mounting it?) and run whatever is in it, thus eliminating the need for repacking.
Do correct me if I'm talking absolute rubbish, but wouldn't this be a security risk?
Currently with S-ON, you actually can't change the kernel's ramdisk, but if the ramdisk will be stored in a writeable filesystem...?
Freezeil said:
That's a nice idea! I thought a little bit about it and here are my thoughts (a novice, please don't laugh at me :silly:
if I understand your idea correctly, your intention is to store the specific ROM's ramdisk in the rootfs, and make a global, generic ramdisk which will be stored in all the kernels.
Upon loading the kernel's ramdisk, it will know to take the ROM's ramdisk from the rootfs (upon mounting it?) and run whatever is in it, thus eliminating the need for repacking.
Do correct me if I'm talking absolute rubbish, but wouldn't this be a security risk?
Currently with S-ON, you actually can't change the kernel's ramdisk, but if the ramdisk will be stored in a writeable filesystem...?
Click to expand...
Click to collapse
On s-off phones ramdisk can be changed on the fly with repacking, and reflashing the kernel if rooted. There is no more security risk in this, than that. And system is ro mostly, so file corruption isn't something to be afraid of either.
Sent from my HTC One X using xda premium
Xmister said:
On s-off phones ramdisk can be changed on the fly with repacking, and reflashing the kernel if rooted. There is no more security risk in this, than that. And system is ro mostly, so file corruption isn't something to be afraid of either.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I agree, other than the fact that repacking+reflashing the kernel on S-ON devices can only be done manually, by a person (which is the device owner, most of the time), and most of the One X's out there are S-ON and not S-OFF...
Sure, a malicious coder can write evil code in the kernel, but that's relatively less threatening since most kernels have their sources published.
If the ramdisk will be placed on a rw fs (or a ro, but it matters not because of the user elevation rooted users can achieve easily), we are adding the risk of malicious code accessing and changing that ramdisk, without the user's knowledge.
Still, this seems like a nice programming challenge, so I'm up for the task. Will start reading the init's code and see how to do it
Guys i would like this thread kept with minimal off topic please, i have already deleted three posts here...
thanks
-Lloir, Section mod
Is anyone really seriously responding to this?
What would be the advantages of modifying Android layout for 1 device only, its so annoying to see this stuff here when even a s-off thread is locked.. currently when all the sources are going to a way whereas all the basic files are device independent makin this even more.. timewasting effort and still we have the same issues. You just lock every rom dev to a ramdisk instead of a kernel dev to a ramdisk.
This is only usefull with a locked bootloader. I never implement this, another reason is that i spend more time getting my stuff aligned with the mainline that is giving me more succes then randomly adding stuff the a system partition.
Oh and btw when youre system partition gets messed up or altered or whatever you wish you had a decent ramdisk. Not to forget the huge amount of users ending up like that and flooding the forums with questions.
TripNRaVeR said:
Is anyone really seriously responding to this?
What would be the advantages of modifying Android layout for 1 device only, its so annoying to this stuff here.. when all the sources are going to a way whereas all the basic files are device independent.
Click to expand...
Click to collapse
Adding 1 directory is not an "android layout modification". They are moving there, yet it isn't independent between the ROMS even on the same phone.
This is only usefull with a locked bootloader.
Click to expand...
Click to collapse
That's what 99% of us have.
Oh and btw when youre system partition gets messed up or altered or whatever you wish you had a decent ramdisk. Not to forget the huge amount of users ending up like that and flooding the forums with questions.
Click to expand...
Click to collapse
If your system messes up you are probably can't boot android either. What the r=1 user do this time? Goes to recovery, wipe, if that doesn't help, reflash.
Since we have different kernel and ramdisk for recovery, this is not a problem.
Xmister said:
That's what 99% of us have.
Click to expand...
Click to collapse
Lol 99% of us DOESNT have this, if we did we cant flash custom roms.
Adding 1 directory is changing Android layout, Google doesnt have it, you want it on /system you alter the layout. Plain simple.
Also if anyone, like me, doesnt like to include youre mod users still need to repack between roms who contain that dir and roms who dont have that dir. That repacking also requires the same kernel edits so basicly you just move the repacking arround.
TripNRaVeR said:
Lol 99% of us DOESNT have this, if we did we cant flash custom roms.
Click to expand...
Click to collapse
Sorry, I was reading S-ON in my mind, I don't know why.
But then it's not only useful for locked devices. It helps just in what it says in the title.
Also if anyone, like me, doesnt like to include youre mod users still need to repack between roms who contain that dir and roms who dont have that dir. That repacking also requires the same kernel edits so basicly you just move the repacking arround.
Click to expand...
Click to collapse
Yes, it can only work if there are enough ROMs taking the change.
And right, call it a layout modification. Why is adding 1 directory bad for anything? It won't break compatibility over anything.
Xmister said:
Sorry, I was reading S-ON in my mind, I don't know why.
But then it's not only useful for locked devices. It helps just in what it says in the title.
Yes, it can only work if there are enough ROMs taking the change.
And right, call it a layout modification. Why is adding 1 directory bad for anything? It won't break compatibility over anything.
Click to expand...
Click to collapse
I dont want to call it bad, i just dont think this developer discussion, as we all know, and probably you also, this kinda stuff is only stuff to think about. As long as the whole community isnt adopting this it will never happen.
As you also state, it only works when enough roms are using it.. THAT is my problem here, currently we need to repack because of compat. issues sometimes.
Cool that sucks i know, you come up with this idea, without proper thinking people say cool lets do that.
When building roms, some devs like this and some devs dont like this, that will happen you can count on that. If you have 3 devs that dont use it you could end up doing MORE repacking then we need to do now.. that is what i'm trying to explain..
Therefore i said cant believe this is seriously looked into at a high mod level dev section. Hope i made my point clearer now
TripNRaVeR said:
I dont want to call it bad, i just dont think this developer discussion, as we all know, and probably you also, this kinda stuff is only stuff to think about. As long as the whole community isnt adopting this it will never happen.
As you also state, it only works when enough roms are using it.. THAT is my problem here, currently we need to repack because of compat. issues sometimes.
Cool that sucks i know, you come up with this idea, without proper thinking people say cool lets do that.
When building roms, some devs like this and some devs dont like this, that will happen you can count on that. If you have 3 devs that dont use it you could end up doing MORE repacking then we need to do now.. that is what i'm trying to explain..
Therefore i said cant believe this is seriously looked into at a high mod level dev section. Hope i made my point clearer now
Click to expand...
Click to collapse
So your point is: "They won't use it anyway"
And why would need more repack? If half of the ROMs would use it, there would be half as much repack needed.
And in the section rules it says even overriding a notification widget should go in this forum. It's not S-OFF forum, it's Dev related forum, such as my idea.
Sent from my HTC One X using xda premium
Lets all be honest and say: people (users) are lazy...
So if they CAN, they WILL go for the non-repack option
Now, as I am a normal User I am not sure what the exact mechanics are behind this.
But as far as I understand it would be less work for the kernel devs.
They only have to take the "minimal" ramdisk, and put it in their kernel.
The rom makers will have to do "more" work.
But it is work they already are doing, most roms are released with a specific boot.img/kernel.
Some romdevs already are making their own kernels to get some functions (within the ramdisk) to work!
They will gladly adapt to a new way of using ramdisks...
Now I suggest to X Mister, Go for it!
Make a tutorial for rom devs, make a tutorial for kernel devs, and make a tutorial for users.
Make it easy for everyone to use this method!
Now I get what Trip is saying, when we have S-Off we won't need this..
This is very true, but S-Off is most likely not going to happen any time soon.
So in the mean time, why not try it for this device?
- I know this is not really a dev related post, but nor were the last 8 or so
Can anyone create a proper debloat script? I've seen others posted for Verizon and Tmobile variant, but none for ours.
Pretty easy to go through and delete apps yourself with es file explorer. That's what I did.
xcespi510x said:
Can anyone create a proper debloat script? I've seen others posted for Verizon and Tmobile variant, but none for ours.
Click to expand...
Click to collapse
If you are running a custom (or tweaked) rom such as @tx_dbs_tx 's series of flashable zips you can delete the stuff you dont want from the zip itself. This is what I do. I take out all the things I don't want.
The problem with debloat scripts is you are at the mercy of the creator's personal preferences... Unless you are up to editing them. If you were up to that I don't think you'd be asking this question.
So either go this route or use TiBu to first freeze and when you are sure those apps aren't critical delete them. Do your own homework and then implement your preferences... You'll feel a sense of accomplishment. Good luck.
Edit. ..didnt see the post above..already covered.
Use the titanium app...you can freeze them 1st to make sure you dont fudge anything up...then delete away
Sent from my SM-N910P using Tapatalk
thank you guys!
http://forum.xda-developers.com/note-4/snapdragon-dev/recovery-zip-bloatware-guard-1-0-t2956756
Here u go download it install it in twrp and youll be good removes knoxx and 300mb of junk
First few posts say it doesn't work with odex. That's all I read though.