Database Users

[Q] build.prop HEEEEELP

To mods. I have posted the same message in "Android Development and Hacking > Android Apps and Games > [GUIDE] How to edit build.prop on any Android device!". Please handle it as you wish. Sorry for the double post.
Hi all!
I have a Nexus 4 running on PAC (Android 4.2.2).
I have edited the build.prop file (so that it shows as a Note2, and it worked just fine), but before that I had taken a copy of the original one in one file (lets call it copyNexus...but the name is still build.prop), and a copy of the edited file (lets call it copyNote...still same name).
I used the edited file for some time, but now I wanted it reverted back to the original settings.
Once I set copyNexus in /system/ and overwrote the edited file, I rebooted my phone and after the Google logo it just goes blank.
I booted through TWRP recovery to set it back to copyNote through the file manager, but still the problem is the same.
Any suggestions?
Would an installation of PAC fix it?
It is crucial that I do not format everything as I 1st need a backup (I know. Bad thing that I thought this AFTER the catastrophe...)
Thanks!

Extract the original copy from the .zip file and save it on the root of your sd card. Then download aroma file manager and delete the build.prop and copy over the one you've just extracted. If that doesn't work, take a nandroid and flash the original rom and gapps without wiping cache or dalvik or anything else. If that doesn't work, you'll have to start again from scratch
Sent from my HTC Sensation using xda app-developers app

Rymon said:
To mods. I have posted the same message in "Android Development and Hacking > Android Apps and Games > [GUIDE] How to edit build.prop on any Android device!". Please handle it as you wish. Sorry for the double post.
Hi all!
I have a Nexus 4 running on PAC (Android 4.2.2).
I have edited the build.prop file (so that it shows as a Note2, and it worked just fine), but before that I had taken a copy of the original one in one file (lets call it copyNexus...but the name is still build.prop), and a copy of the edited file (lets call it copyNote...still same name).
I used the edited file for some time, but now I wanted it reverted back to the original settings.
Once I set copyNexus in /system/ and overwrote the edited file, I rebooted my phone and after the Google logo it just goes blank.
I booted through TWRP recovery to set it back to copyNote through the file manager, but still the problem is the same.
Any suggestions?
Would an installation of PAC fix it?
It is crucial that I do not format everything as I 1st need a backup (I know. Bad thing that I thought this AFTER the catastrophe...)
Thanks!
Click to expand...
Click to collapse
Mount /system in TWRP
Go to the build.prop in TWRP file manager and click on it. CHMOD 0644

Boot animations

I am trying to change the boot animations with no luck thus far can anybody point me in the right direction, I am rooted and have Xposed framework , Wanam, and Rom toolkit all installed. Thanks in advance for the help

Skip Richmond said:
I am trying to change the boot animations with no luck thus far can anybody point me in the right direction, I am rooted and have Xposed framework , Wanam, and Rom toolkit all installed. Thanks in advance for the help
Click to expand...
Click to collapse
You need to use a Root Explorer type app. There are 2 files in system/media that need to be replaced with the 2 boot animation files you want to use. The 2 files are: bootsamsungloop.qmg and bootsamsung.qmg.

airmaxx23 said:
You need to use a Root Explorer type app. There are 2 files in system/media that need to be replaced with the 2 boot animation files you want to use. The 2 files are: bootsamsungloop.qmg and bootsamsung.qmg.
Click to expand...
Click to collapse
going to give it a try with a different file explorer tried it with ROM toolkit and didnt work and im new to rooting so it is definetly a user error just inexperenced

Still no luck
Skip Richmond said:
going to give it a try with a different file explorer tried it with ROM toolkit and didnt work and im new to rooting so it is definetly a user error just inexperenced
Click to expand...
Click to collapse
I still dont know what I am missing....

I assume you meant "ROM Toolbox" because I don't see "ROM Toolkit" in the market. ROM Toolbox has dozens of bootanimations to choose from. If you see one you like, you should be able to install it within ROM Toolbox. It has been a while since I used it to change bootanis, but I think it was a pretty simple and self-explanatory process. If you want to change bootanis manually, you have to go to
/system/media and swap these files:
bootsamsung.qmg
bootsamsungloop.qmg
bootsamsungmini.qmg
bootsamsungminiloop.qmg
And set permissions to rw-r--r--
Sent from my Rooted SM-N900V using Tapatalk

sublimaze said:
I assume you meant "ROM Toolbox" because I don't see "ROM Toolkit" in the market. ROM Toolbox has dozens of bootanimations to choose from. If you see one you like, you should be able to install it within ROM Toolbox. It has been a while since I used it to change bootanis, but I think it was a pretty simple and self-explanatory process. If you want to change bootanis manually, you have to go to
/system/media and swap these files:
bootsamsung.qmg
bootsamsungloop.qmg
bootsamsungmini.qmg
bootsamsungminiloop.qmg
And set permissions to rw-r--r--
Sent from my Rooted SM-N900V using Tapatalk
Click to expand...
Click to collapse
The boot animations in ROM Toolbox are in the bootanimation.zip format that need to go in either /system/media or /data/local folder. Unfortunately, with Samsung Touchwiz, the required format is the qmg format.
I'm not 100% sure how it is now, but it used to be that the kernel needed to support the bootanimation.zip format in order to be used (or a deeper system/framework support) Most AOSP based ROM/kernels have this support by default but TW doesn't allow this to work.
There's a thread in the theming section that has several of these files to use, but aren't of the greatest quality, IMO.

I used the international bootanimation files from this thread
[Stock] International Note 3 Bootanimation
Sent from my Rooted SM-N900V using Tapatalk

Change lock screen pics on Kindle Fire HDX

Hey everyone,
I recently upgraded from the original Fire to the HDX. I searched high and low on how to change the lock screen pics on the HDX and turned up nothing. However, I did find a different way to change the lock screen on the original Fire and thought it might work on the HDX. After rooting, safe strapping, making a system back up and several hours of searching for the lockscreen pics folder, IT WORKED!! I apologize if this has already been done on the HDX but I wanted to share for those of you who couldn't find it either. I urge you to follow these steps EXACTLY or you could end up with a very expensive door stop.
**Before Starting** Your HDX must be rooted. I would highly advise installing safe strap and making a backup of your system (I boot looped twice before I finally got it right!) Down load 7-zip and install on your PC. Download root explorer from the Amazon market. Credit goes to Josepho1997 for posting this on the original Kindle Fire. I just took his method and tweaked it for the HDX.
1. Using Root Explorer from the Amazon Market, go to: /system/framework and copy (do not move!) framework-res.apk to your SD card.
2. Plug your Kindle into the computer and move the framework-res.apk (from SD card) to your computer and make a back up copy.
3. Use 7-Zip to open the one you intend to modify
4. Open the "res" folder then the "raw-xhdpi" folder.
5. You'll find 22 jpeg images in this folder, 11 images with the "_p_" in the file name.
6. Replace the "_p_" jpegs with the images you want, keeping the names exactly as they are. DO NOT delete any images. You can use 11 different images or the same one over and over again. I highly recommend formatting each picture to 1600x2650 like the originals.
7. Close 7-Zip and the new framework-res.apk will be saved, move this back to your SD card.
8. Open Root Explorer.
9. Copy the framework-res.apk to /system.
10. Long press on the framework-res.apk file and change the permissions to rw-r-r. (This is critical, failure to do this will cause a bootloop)
11. Move framework-res.apk to /system/framework. Overwrite the existing file.
12. The Kindle will automatically reboot and your new wallpapers will appear on the lock screen.
That's it! Good luck :good:

This is awesome! I think I may wait though if you suggest safestrap. It's currently not available for the 8.9.
Sent from my KFAPWI using xda premium

I don't blame you. There is nothing worse than that pucker factor you get when you go into boot loop without a backup. Hopefully, our awesome devs will safe strap your sweet 8.9" machine in no time!

I've only just got mine Kindle Fire HDX 7 to use Google Apps. Playing around with the rest of Amazons interesting design choices is the next step. This looks like a brilliant idea! Time to get my HD space pictures in there.
Thanks!
--- I have just tried this. I can copy the file to a visible directory but then i cant see it in there...
It isn't hidden or anything, thoughts?

There is a check box in Root Explorer preferences that enables you to see hidden files. Make sure this is checked first and then copy the file to the root of your SD card. You should be able to see it.

It's showing up now.
Thanks!

Sweet:fingers-crossed:

Because I am pure awesome, I managed to bootloop it too haha.
I have recovered it though and had another go with much better result haha
For anyone else having a go at this, I can't stress enough cthebadge's point about moving it to "/system" first, changing the permissions, and THEN moving it to "/system/framework"!

My next step is trying to find the gray background pic on the carousel screen. If anyone finds this before me, I'd appreciate the location. I don't see why we couldn't customize this background image as well..?

the lock screen pics doesn't bother me ,but I want to make the nova ;auncher show it's wallpaper.

cthebadge said:
My next step is trying to find the gray background pic on the carousel screen. If anyone finds this before me, I'd appreciate the location. I don't see why we couldn't customize this background image as well..?
Click to expand...
Click to collapse
system\app\Launcher-release-signed_81224610\res\drawable-sw600dp-xhdpi/home_bg.png and system\app\Launcher-release-signed_81224610\res\drawable-sw600dp-land-xhdpi\home_bg.png

How to change Kindle Fire HDX carousel wallpaper
ONYXis, you are awesome my friend!
Anyone that would like to change their carousel screen wallpaper, it's basically the same steps as I listed above for changing your lock screen wallpaper, only the pics are in different directories.
Following ONYXis's path, you want to copy the Launcher-released-signed_xxxxxxx.apk from the system/app directory and move it to your SD card. Transfer to the PC and open with 7-zip. Open the res folder and locate the portrait picture in the "drawable-sw600dp-xhdpi" folder named "home_bg.png". The landscape picture is in the "drawable-sw600dp-land-xhdpi" folder listed as "home_bg.png". Take both pics and replace them with the ones of your choice. The resolution for the portrait pic is 1200x1869 and the landscape pic is 1920x1149. **Make sure you save your new pics as .PNG and not .JPEG. Overwrite the old stock pics with your new pics keeping the name exactly the same. Close 7-zip and transfer the .apk file back to your SD card. Move the file to /system and change permissions again to rw-r-r. Move the .apk file to the /system/app directory and overwrite the original .apk file. Your Kindle will reboot on it's own and the new wallpaper appears! Thanks again to ONYXis for finding the pics!

Thanks. BTW this TUT http://forum.xda-developers.com/showthread.php?t=2373563 works too.
Notice that new resolution for HDX is 562x562 and 198x198.
My screens http://imgur.com/a/g559a and some icons from me attached (put folder "images" from archive to system/vendor/data with overwrite and reboot).

ONYXis said:
Thanks. BTW this TUT http://forum.xda-developers.com/showthread.php?t=2373563 works too.
Notice that new resolution for HDX is 562x562 and 198x198.
My screens http://imgur.com/a/g559a and some icons from me attached (put folder "images" from archive to system/vendor/data with overwrite and reboot).
Click to expand...
Click to collapse
Those icons look amazing!
Sent from my iPhone using Tapatalk

cthebadge said:
Hey everyone,
I recently upgraded from the original Fire to the HDX. I searched high and low on how to change the lock screen pics on the HDX and turned up nothing. However, I did find a different way to change the lock screen on the original Fire and thought it might work on the HDX. After rooting, safe strapping, making a system back up and several hours of searching for the lockscreen pics folder, IT WORKED!! I apologize if this has already been done on the HDX but I wanted to share for those of you who couldn't find it either. I urge you to follow these steps EXACTLY or you could end up with a very expensive door stop.
**Before Starting** Your HDX must be rooted. I would highly advise installing safe strap and making a backup of your system (I boot looped twice before I finally got it right!) Down load 7-zip and install on your PC. Download root explorer from the Amazon market. Credit goes to Josepho1997 for posting this on the original Kindle Fire. I just took his method and tweaked it for the HDX.
1. Using Root Explorer from the Amazon Market, go to: /system/framework and copy (do not move!) framework-res.apk to your SD card.
2. Plug your Kindle into the computer and move the framework-res.apk (from SD card) to your computer and make a back up copy.
3. Use 7-Zip to open the one you intend to modify
4. Open the "res" folder then the "raw-xhdpi" folder.
5. You'll find 22 jpeg images in this folder, 11 images with the "_p_" in the file name.
6. Replace the "_p_" jpegs with the images you want, keeping the names exactly as they are. DO NOT delete any images. You can use 11 different images or the same one over and over again. I highly recommend formatting each picture to 1600x2650 like the originals.
7. Close 7-Zip and the new framework-res.apk will be saved, move this back to your SD card.
8. Open Root Explorer.
9. Copy the framework-res.apk to /system.
10. Long press on the framework-res.apk file and change the permissions to rw-r-r. (This is critical, failure to do this will cause a bootloop)
11. Move framework-res.apk to /system/framework. Overwrite the existing file.
12. The Kindle will automatically reboot and your new wallpapers will appear on the lock screen.
That's it! Good luck :good:
Click to expand...
Click to collapse
Hi,
I've mistakenly skipped step 10 and done step 11 , now, as you've anticpated, my Kindle Fire HDX 8.9 has gone into bootloop at the Kindle Fire logo. Can you help? Many thanks!

You are a braver person than I for trying this hack without safe strap my friend. The have been searching for a fix for your 8.9" boot loop and could find nothing. I am by no means a developer and will only experiment with things if I have safe strap installed. I would recommend posting your question in it's own thread and hope that someone can help. Sorry

cthebadge said:
You are a braver person than I for trying this hack without safe strap my friend. The have been searching for a fix for your 8.9" boot loop and could find nothing. I am by no means a developer and will only experiment with things if I have safe strap installed. I would recommend posting your question in it's own thread and hope that someone can help. Sorry
Click to expand...
Click to collapse
Is it really that bad? Thanks for your suggestion anyway. I've post it in other thread already. Have my fingers crossed:fingers-crossed:

Well..it's not good! Lol Normally, I won't even attempt root without a fxz or sbf file to flash in case I boot loop. You just changed a system file when you dropped that file in the framework folder. The only way that I can think to fix it would be to somehow be able to access that file via computer and overwrite your modified file with the stock file. You did make a backup of the original file I assume..?

cthebadge said:
Well..it's not good! Lol Normally, I won't even attempt root without a fxz or sbf file to flash in case I boot loop. You just changed a system file when you dropped that file in the framework folder. The only way that I can think to fix it would be to somehow be able to access that file via computer and overwrite your modified file with the stock file. You did make a backup of the original file I assume..?
Click to expand...
Click to collapse
Yes I did. I'm also thinking how to reinstall the original file back.

Image "replacement"
cthebadge said:
Hey everyone,
6. Replace the "_p_" jpegs with the images you want, keeping the names exactly as they are. DO NOT delete any images. You can use 11 different images or the same one over and over again. I highly recommend formatting each picture to 1600x2650 like the originals.
...
12. The Kindle will automatically reboot and your new wallpapers will appear on the lock screen.
That's it! Good luck :good:
Click to expand...
Click to collapse
I followed the directions except I don't know how to "replace" the images in the file without deleting the old image files. I used the same file names for my images and copied my new images into the file after deleting the old image files.
When I moved the .apk into /system/framework several programs shutdown and I thought the tablet was going to reboot but it never rebooted. Eventually I just used the power button and shut it off. When I restarted the system all I got was the grey screen. I shut down by holding the power button for about 10 seconds and then tried a second time.... no joy.
Since I am using safestrap I am up and running, I will rebuild my rom-slot1 from backup. Curious what I may have done wrong or if I am missing some small step...
HDX 8.9 rooted, modified so google playstore works.
The _p_ files are portrait, the _l_ files are the same picture in landscape. I will figure out what the dimensions are for the landscape files and reformat all the pics for a retry.... all are 1600 x 2560 (not 2650!)
Ok, replaced all the _p_ and _l_ files, make sure they are the right dimensions and in portrait or landscape shape. It all worked and now I just need to kill the Amazon advertising.

Converting Bootanimations

Can someone convert or tell me how to convert this bootanim to the Nexus 7?
Thanks!
https://dl.dropboxusercontent.com/u/12414928/bootanimation.zip

Boncey said:
Can someone convert or tell me how to convert this bootanim to the Nexus 7?
Thanks!
https://dl.dropboxusercontent.com/u/12414928/bootanimation.zip
Click to expand...
Click to collapse
Hi, Boncey...
When you say 'convert', I assume you mean 'encapsulate' it into a CWM/TWRP flashable .zip.
Well, that skill and level of technical knowledge is a bit beyond me, I'm afraid. But changing a boot animation is a relatively trivial task, providing you exercise care, and are comfortable poking around inside /system.
I've tested your bootanimation.zip on my own Nexus 7... and it works... but there's too long a duration after the animation has run, before you're presented with the home launcher (or Android desktop). All you see, after the animation (which runs for about 2 seconds) is 30 seconds of black screen.
It's also quite large, clocking in at a whopping 9.7Mb... compared to the standard KitKat 'dancing colored circles' boot animation... which is just a miniscule 714Kb.
Anyway... here's the how-to-bit...
Your Nexus 7 will need to be rooted.
You'll also need a root capable Android file manager. There are several such file managers available on Google PlayStore, with ES File Explorer File Manager arguably one of the most famous and renowned. But I prefer X-Plore file manager, because it has dual-pane capability, which makes copying stuff from one location to another easy. So my instructions and thumbnails that follow are written with 'X-Plore file manager' in mind...though they should be adaptable to any root capable Android file manager.
Whichever file manager you choose... you'll first need to go into its settings or configuration options, and enable root... you'll also need to enable a setting which allows changes to be made to /system.
In X-plore filemanager, this is called Superuser+Mount Writable (Superuser mode, which allows changes in read-only mode).
(See thumbnail no.1, at the bottom of this post).
Other Android file managers may use a different description and words... but the key thing to remember, is that you're allowing the file manager to makes changes to /system. And for this reason, EXTREME CAUTION should be exercised when using the file manager with this setting enabled. By default, and for very good reasons, /system is set as READ-ONLY. Enabling the 'Mount Writable' option, makes /system READ-WRITE.
Once you've completed the following procedure, remember to disable the 'Mount Writable' option.
-------------------------------------------------------------------------
OK... with that lengthy preamble out of the way... we begin.
The Nexus 7's boot animation is stored in a folder called /system/media... and unsurprisingly, its called bootanimation.zip.
The first thing you need to do, is rename this file. When doing this sort of thing on my own Nexus 7, I just rename the file extension... so, bootanimation.zip becomes bootanimation.bak
Leaving the old (original) boot animation in place is a good idea, so should you tire of its replacement... you can easily revert back, by simply renaming the files extension back to .zip, ie., bootanimation.zip
Next... copy the new replacement into the same system folder... namely /system/media
You should now have two files in the folder /system/media...
/system/media/bootanimation.bak - the original boot animation, but disabled.
/system/media/bootanimation.zip - the new, replacement boot animation.
(See thumbnail no.2)
We're nearly there... but there is one last thing to do... set the file permissions on the new bootanimation.zip file.
How this is done will vary from one file manager to the next... but in X-Plore, it's accomplished by LONG PRESSING on the file in question, until a context sensitive menu appears.
(See thumbnail no.3)
Select the option marked 'Permissions'... a dialogue box will appear with nine check boxes.
Ensure all the ones for READ are ticked, and just the USER one for WRITE. The permissions mode should amount to 644. Anyway, it's probably better if you just take a look at my screenshot at the bottom of this post. (Describing this sort of thing makes my head hurt... a picture really does paint a thousand words).
(See thumbnail no.4)
Finally... go back into the file managers settings option, and disable the Mount Writable option (or whatever it's called in your chosen file manager).
Right that's it... you can now reboot your Nexus 7 and enjoy the dubious pleasure of watching the green Android mascot peeing all over an Apple logo... I'm guessing you're not a big fan of Apple!.
-------------------------------------------------------------------------
Although the above sounds fairly involved and complicated... it really isn't. Like all things technical, it's easier to do, than describe. Descriptions often run to several paragraphs for the most prosaic of things.
Summary.
** A rooted Nexus 7.
** A root capable Android file manager.
** Enable root and Mount Writable or similar option in your chosen filemanager.
** Rename /system/media/bootanimation.zip...to.../system/media/bootanimation.bak
** Copy the new bootanimation.zip into the folder /system/media.
** Set file permissions on it... to 644.
** Disable Mount Writable or similar option in your chosen filemanager.
** Reboot... Enjoy!.
-------------------------------------------------------------------------
Good luck... and hope this helps.
Rgrds,
Ged.

Thanks!
Turns out my permissions were wrong!

Preview 3/Marshmallow boot animation

For anyone who wants the new animation
Flashable zip - https://app.box.com/s/yqehpcrzbj8nwh56sw6x73wtnk58n718
Or of course extract it and manually install if you wish
Sent from my Nexus 5 using Tapatalk

thanks a lot bro. the bootanimation is just awesome. liked it soo much. works perfectly on my n5.
Sent from my Nexus 5 using XDA Free mobile app

Thanks m8, for this nice one

No matter how many times I try this I cannot get it to flash.
I flash it in TWRP and it places it in system/media but the animation just shows the android logo fading from white to grey,
In fact, now I can't get ANY boot animation to flash. Same thing every time. Just the stock android boot animation.
Thoughts?

Use es file explorer and copy and paste the bootanimation.zip to system/media and check permissions of the file afterwards. Es should have automatically set them to rwx rwx rwx. Then reboot.
Sent from my Nexus 5 using Tapatalk

gogorman said:
No matter how many times I try this I cannot get it to flash.
I flash it in TWRP and it places it in system/media but the animation just shows the android logo fading from white to grey,
In fact, now I can't get ANY boot animation to flash. Same thing every time. Just the stock android boot animation.
Thoughts?
Click to expand...
Click to collapse
Copy manually to /system/media/ . The name MUST be bootanimation.zip
Manually set permissions to rw,r,r with ES Explorer or Brown Root Explorer.
If you check my signature, I have a collection listed that also contains this animation, in both manual and flashable configurations. Mine SHOULD work. If they don't, something is amiss.
I'm suspecting it's a permissions issue.

androcraze said:
Copy manually to /system/media/ . The name MUST be bootanimation.zip
Manually set permissions to rw,r,r with ES Explorer or Brown Root Explorer.
If you check my signature, I have a collection listed that also contains this animation, in both manual and flashable configurations. Mine SHOULD work. If they don't, something is amiss.
I'm suspecting it's a permissions issue.
Click to expand...
Click to collapse
Still no luck. Tried exactly as you described but it just shows the android logo.
Both flashing and manually installing in system/media.
Any other ideas?

gogorman said:
Still no luck. Tried exactly as you described but it just shows the android logo.
Both flashing and manually installing in system/media.
Any other ideas?
Click to expand...
Click to collapse
You're seeing the framework "bootanimation". It's the default, if nothing else is found.
Something is buggered. My normal recommendation would be to reflash the ROM, but....
With Android M just around the corner, and everything else apparently working on your phone.... would it hurt to leave it alone until the next update?

I'll just leave it.
Weird that it doesn't work. It did previously when I flashed the lollipop one.
Thanks for the help.