So today I was trying to look up on how to replace the system icons and such, so I extracted some file I cannot rememeber the name of it and replaced the images from in it with the ones I wanted, then I applyed the stuff with an app and it said I should reboot for it to work, however when it was displaying processing it crashed, and rebooted on its own. It will keep looping in the boot animation, and I'm not sure if I'm gonna have to go back to stock. And fyi I am using manualnooter.
I dont understand how it isnt working and all I edited was pictures, plus a few xmls.
Here are the name of the xmls edited if you need (all of them have nav_ in front of the name)
home.xml, jump.xml, library.xml, quickbutton.xml, search.xml, shop.xml, shop_in_store.xml, web.xml
and if your wondering what pictures were replaced from what I can tell only the status bar stuff was replaced. (i.e. c_back.png)
Also, I was trying to use the SystemUi.apk to change it, but i could not find it. so I found something else that had the icons. (trying to find the name of the file right now)
Edit: I replaced files inside of system\framework-res\drawable-mdpi\
(sort of) Resolved: I had booted a couple different recoveries, until it would get stuck on the 'N', then I did the 8 fail boot and it loaded back up to stock. Guess I'll just reflash manualnooter.
Related
I've been playing with the ThemePorter app and loving it. But while I have the new rom open and swapping the .pngs from the old theme to the new rom I thought I could change the fonts too. I picked a font I liked (.tft format), deleted the old fonts and installed the new ones with all the same names as the old ones (Clockopia, DroidSans, etc etc) but once I zip the rom back together and sign it, it won't load. ADB logcat gives me issues like media_flinger died, and the other media stuff in that library has died warnings too. This makes the boot screen hang and the rom won't load despite complete install. Obviously there are other ways to change the font, so that's not a big deal. I'm just trying to understand how this stuff is connected. I did double check and this can be the only problem. I just unzipped the rom, replaced the original font folder, signed, and rebooted just fine. Any ideas?
im using mdj 2.3 clean and S6 kernel.
ive done 2 things and android dont go past black screen and HTC logo.
first i put the new build.prop to fix the green camera, while in windows mobile, inside SD/ANDROID/ROOT/SYSTEM/build.prop
i didnt boot android yet, i created a folder inside SD/ANDROID/ROOT/SYSTEM
called FRAMEWORK and i put framework.jar for RTL inside:
SD/ANDROID/ROOT/SYSTEM/FRAMEWORK/framework.jar
now i tryed to boot android and no success.
what i did is remove all changes but still android wont boot.
what might be the problem/solution?
im trying to save my build here cus i did alot of changes and i have no backup.
i think its the build.prop that wasnt compatible, what can i do to fix it?
eeeeeee said:
im using mdj 2.3 clean and S6 kernel.
ive done 2 things and android dont go past black screen and HTC logo.
first i put the new build.prop to fix the green camera, while in windows mobile, inside SD/ANDROID/ROOT/SYSTEM/build.prop
i didnt boot android yet, i created a folder inside SD/ANDROID/ROOT/SYSTEM
called FRAMEWORK and i put framework.jar for RTL inside:
SD/ANDROID/ROOT/SYSTEM/FRAMEWORK/framework.jar
now i tryed to boot android and no success.
what i did is remove all changes but still android wont boot.
what might be the problem/solution?
im trying to save my build here cus i did alot of changes and i have no backup.
i think its the build.prop that wasnt compatible, what can i do to fix it?
Click to expand...
Click to collapse
I had something similar happened to me as well...no changes yet it won't boot all the way anymore. Stuck on green HTC screen. I suspect file corruptions so I redownload the clean build, move my data.img to it, fix! You can give that a go. Good luck.
azzzz said:
I had something similar happened to me as well...no changes yet it won't boot all the way anymore. Stuck on green HTC screen. I suspect file corruptions so I redownload the clean build, move my data.img to it, fix! You can give that a go. Good luck.
Click to expand...
Click to collapse
im doing it right now
EDIT: im trying replacing the rootfs only maybe this will solve it.
EDIT: replacing rootfs with original solved the problem
OK, I thought I saw this mentioned -somewhere- on this forum, but I've tried searching in vain.... Most likely I just can't put together the correct search phrase.
I'm currently running ManualNootered B&N 1.3. I've read very conflicting info as to whether B&N can or will update a rooted OS, but is there a way that I can prevent it? I vaguely remember someone mentioning that they had a rooted 1.2 and woke up one morning to a screwed up 1.3. My biggest concern, of course, is the upcoming 1.4. Don't want to try that until someone figures out what might be needed to apply ManualNooter.
That happened to me. I had nootered a 1.2 and it was working beautifully!
Then I turned on wifi, checked my email and got force fed the update to 1.3.
I've just found an old text file on my PC that had directions to block the update though so I tried it out, it requires that you buy the SQlite editor from the market.
It is priced a $2.99 but I feel it was worth it if it works!!
You can still side load the updates if and when you choose to also!
So I bought the editor and followed these directions:
*Open SQLite. It will scan your entire Nook and find every SQL database file there. Even the hidden ones. It only takes ~10 seconds. (You may see a message about granting super-user permissions, which is normal.)
*Scroll down to DeviceManagerService, and tap on it. Then tap on devicemanager.db.
*Tap on the "registry" entry. It's easier now if you rotate to landscape, so you can see more of the fields in each entry.
*All the entries in this table start with "com.bn.device....". Look for the one that's labeled '...fota.mode" at the end.
*In the far right Value column, you'll see "Auto". Tap on that to select it. Then go down to the Status Bar at the bottom, and tap the Menu button (3 horizontal lines), and pick Edit Field.
*You'll then see a black screen with one entry, the field editing form. You should see the field name of "value" there, and its contents will be "auto". If it turned out that your selection picked some other field (they are pretty small!), don't panic! :smileywink: Just go back and retry until you get the right one.
*Tap on "auto" and the keyboard will come up. Backspace to delete the current contents, and enter "manual" in its place. Then tap Done. Then tap Save. Until you tap Save, you've changed nothing, so poking about is fairly safe.
*You can now exit out of SQLite if you like (it's not necessary), but you're not quite done yet, so don't enable WiFi immediately. To make sure that the system is using the settings you just modified, you need to force it to reload and "see" them. So just power your Nook off and back on. After it reboots, it will use your new settings from then on. That's it.
This file was signed ~Mark, and unfortunately I didn't add the username or anything, so Thanks go to "Mark"
Another method?
I found this over on the B&N forum. I don't know if it is more or less effective than the method above. Perhaps a belt-and-suspenders approach would be best - do both.
Link:
http://bookclubs.barnesandnoble.com...be-possible/m-p/1220616/highlight/true#M68396
And the complete OP:
Title:
Declining the 1.4 update should be possible
Text:
I am looking at build.prop from the 1.4 OS released with the Nook Tablet, with an eye to testing an edit of a system file, build.prop, to update the file and make a Nook Color look as if it is already on 1.4. So far, I'm not seeing anything which looks like a showstopper in the new build.prop for drawing elements out of it for a modded build.prop.
Once the actual update is out, I think I should be able to create a modified file very quickly that will tell the BN servers a device does not need the update as it is already running 1.4.
This is the technique I've used successfully to keep my device at 1.2, which I prefer to 1.3.
If my experiments work, I'll post both the raw build.prop, for folks with root who know how to mount /system as rw to simply copy in (after backing up their original build.prop) and as a set of Clockwork installable files. These will need to be run from a Clockwork disk but will not require rooting the device. One script will move your current build.prop and put in an edited one; a second script would remove the modified build.prop and restore your original so you can receive the update if you choose.
If you have a custom recovery in place, ie clockworkmod, it will prevent installation of the update. Your device will still download the update, but when it boots into recovery for install, it will fail. Reboot and you are back to normal. This has worked for me twice.
Hi there,
I am running this Rom and made my own bootanimation with photoshop.
It's 480x480, 72 dpi (I also tried different dpi values) and I tried it with color management (sRGB) and tried it without color management as well.
I put the bootanimation.zip into /system/media with ES Explorer. Until here everything works fine.
But when I reboot, instead of my animation, all I see is the logo.rle (which I customzed as well and works fine) for longer than usual and then a black screen until the boot is finished.
I attached my animation. Hopefully someone has a clue why it doesn't work.
Thank you in advance
Alright. I found the problem myself. -.-
Solution:
The images have to *.jpg's without color management.
dimmu2k said:
Alright. I found the problem myself. -.-
Solution:
The images have to *.jpg's without color management.
Click to expand...
Click to collapse
Are you serious? i've been messing around with this and getting really frustrated...
Especially since the first part plays it's .png's, but then the screen goes black when the second part should start...
I'll try this later today, on an SGS2 with CM10/PA.
EDIT:
Nope, didn't solve it for me.
After a few tries with different file names for the images, only the first part would play, and all of a sudden all i had was a black screen...
Reinstall ROM...
Hi it's my first post on here and I recently rooted my Samsung galaxy s5 via towel root and I've been trying to change my bootanimation
It wouldn't work on theme changer in rom toolbox pro. So I tried doing it myself I still have all stock files but it seems that I erased my whole boot animation. When I reboot my phone it just takes me straight to my home screen. Any help would be appreciated thanks!
Simply restore your backup.
If you don't make backups that is a bad habit that you ought to change immediately. In the alternative, then manually revert the files that you changed and your bootanimation will work again. If it doesn't seem to, then wipe your system cache from recovery mode.
If the problem persists, I would suggest that you didn't really revert all of the files that you changed. Check the file permissions and investigate what else your app may have changed on your behalf. In the worst case you can start over by writing a full stock firmware image to your phone. A lot more painful than restoring a backup that would reflect how your phone was four hours ago. But a certain lack of planning will limit choices that way.
As to the boot animation per se, Samsung requires a .qmg animation file, while most apps use a bootanimation.zip formatted file. Ergo you usually need to convert your .zip file to a qmg. Or modify your kernel to use the .zip format. There are lots of existing threads that explain in detail how to do either which you would know if you had done a search before posting. I would suggest that it is always in your own interest to do at least a quick search first, if only so that you can pose more informed questions.
.
fffft said:
Simply restore your backup.
If you don't make backups that is a bad habit that you ought to change immediately. In the alternative, then manually revert the files that you changed and your bootanimation will work again. If it doesn't seem to, then wipe your system cache from recovery mode.
If the problem persists, I would suggest that you didn't really revert all of the files that you changed. Check the file permissions and investigate what else your app may have changed on your behalf. In the worst case you can start over by writing a full stock firmware image to your phone. A lot more painful than restoring a backup that would reflect how your phone was four hours ago. But a certain lack of planning will limit choices that way.
As to the boot animation per se, Samsung requires a .qmg animation file, while most apps use a bootanimation.zip formatted file. Ergo you usually need to convert your .zip file to a qmg. Or modify your kernel to use the .zip format. There are lots of existing threads that explain in detail how to do either which you would know if you had done a search before posting. I would suggest that it is always in your own interest to do at least a quick search first, if only so that you can pose more informed questions.
.
Click to expand...
Click to collapse
yeah its okay I just reverted everything and it works fine. I still want to but I don't wanna mess it up again. But yes I just reverted the files back and I'm okay. But I wanted a custom boot animation but there's really no clear tutorial on how to.
lgillen14 said:
But I wanted a custom boot animation but there's really no clear tutorial on how to.
Click to expand...
Click to collapse
Not true. You need to search better as I have seen several of them. And if memory serves, written at least one myself.
.
fffft said:
Not true. You need to search better as I have seen several of them. And if memory serves, written at least one myself.
.
Click to expand...
Click to collapse
do I need a different rom? I don't even know how do do any of that lime I've rooted all my phones but not gone seriously in depth about it. I don't know what I did wrong the first time and when I tried following directions and it almost messed me up. So could you guide me toward the appropriate thread I need to get to? Thanks
lgillen14 said:
do I need a different rom?
Click to expand...
Click to collapse
No, you simply need to do a search and read the existing boot animation guides. A lot of people claim to search when they really didn't. Or did one simplistic search and gave up, thinking it's easier if someone spoon feeds them. If you try a few different keywords you'll find the guides and everything you need.
You don't need a different ROM. Root is sufficient to change the boot animation file. If you want to make a qmg animation from scratch you can use Samsung's theme designer software.
.