Database Users

[Q] Customizing boot logo - MIUI 2.1.13?

I would like to change the boot logo [red M] @ start up.
I'm running MIUI 2.1.13...
I've found a couple of tools that look promising - debraks 'Splash Tools' & Rom Toolbox... seems like neither was designed for defy - but some comments around suggest that they would work...
There's also a guide out there for CM7... I'm a bit reluctant considering I'm on MIUI.
Anyone got a tried & tested procedure to change the red M on a defy running MIUI? + some images to use that aren't CM7 branded? ^^
T.I.A

it could work well whichever rom u are using.

No idea if that works with MIUI but I used "Boot Logo Replacer RC4" from the market and that worked in most cases on Barebones (Froyo). You only need root for that.

dd23 said:
No idea if that works with MIUI but I used "Boot Logo Replacer RC4" from the market and that worked in most cases on Barebones (Froyo). You only need root for that.
Click to expand...
Click to collapse
it "Boot Logo Replacer RC4" only replaces bootanimation (despite apps misleading name)
I want to replace splash screen @ start up

Oh ok. No idea if that also works with MIUI, but for CM this does it: http://forum.xda-developers.com/showthread.php?t=1227412

dd23 said:
Oh ok. No idea if that also works with MIUI, but for CM this does it: http://forum.xda-developers.com/showthread.php?t=1227412
Click to expand...
Click to collapse
tried d/l on my lappy ^^ Avast gave about 20 lines for Virus intrusion!?
Prob false positive... but

The tool is only to create a *.bin from a bitmap picture. You don't need it, if you already have a .bin-file.
Then you only need root on your device and then follow the instructions with the dd-command. But be careful to have correct spelling and case, cause otherwise you could overwrite important files!
So basically it's the following, assuming you have a logo called "mylogo.bin"
1. copy mylogo.bin into root of your SD-card
2. Run the terminal and type the following:
Code:
su
enter and confirm root permissions, then
Code:
dd if=/sdcard/mylogo.bin of=/dev/block/mmcblk1p10
enter, then reboot.
Edit: By the way, nothing suspicous about the tool found. See https://www.virustotal.com/file/270...84b13da38d9b7ceae30678d22c4c55a52cc/analysis/

im using miui 1.12.16 pikachu edition. its a full wipe and changes everything including the boot logo. apparently its a german rom but works very well in the uk

dd23 said:
The tool is only to create a *.bin from a bitmap picture. You don't need it, if you already have a .bin-file.
Then you only need root on your device and then follow the instructions with the dd-command. But be careful to have correct spelling and case, cause otherwise you could overwrite important files!
So basically it's the following, assuming you have a logo called "mylogo.bin"
1. copy mylogo.bin into root of your SD-card
2. Run the terminal and type the following:
Code:
su
enter and confirm root permissions, then
Code:
dd if=/sdcard/mylogo.bin of=/dev/block/mmcblk1p10
enter, then reboot.
Edit: By the way, nothing suspicous about the tool found. See https://www.virustotal.com/file/270...84b13da38d9b7ceae30678d22c4c55a52cc/analysis/
Click to expand...
Click to collapse
gr8 info. know where I can find some custom bin files?

King_Rat said:
gr8 info. know where I can find some custom bin files?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1227412
look at this thread, its great, works and some splashscreens are there too...
have searched a long time to find it... xD
Try Building your on splashscreens, its more customization than using one thats provided
have fun with that
edit: should have checked all the links provided, before posting one a second time xD
well whatever, works, no virus, fun to create new splashscreens, awesome

[CWM] [Flashable] [Only for Aurora 4.1a] Updated init.d support

I'm sorry to have to open another thread just for this, but I was waiting for zephyr1988 to update his files for aurora 4.1a. As he didn't do it yet, here it is
I had posted these in the other thread, but the files are now outdated and there was some confusion regarding the kernel inside the zip. These files, fix this, because I updated the kernel and services.jar for Aurora 4.1a.
Please, to understand what this does, read this thread:
http://forum.xda-developers.com/showthread.php?t=1710233
Notes:
- This is only for those with Aurora 4.1 + 4.1a update. For other versions, there will be auto-reboots, especially with the gallery, so, if don't have the latest aurora version, don't install this.
To install, flash both zips in recovery. Boot takes a little longer, but believe it, it's worth it
MIRROR

Thanks, fjsferreira! You're incredibly helpful all the time.

I get this error when i try to download.
404 - Not Found

greddyrx7 said:
I get this error when i try to download.
404 - Not Found
Click to expand...
Click to collapse
Yes, I get that too, looks like a problem with xda. Here is an alternate download. Extract the two zip files first
http://www.mediafire.com/?ifhpwtzmtevv1fl

Sorry if this question was already answered.
What are the changes in the boot.img?
dzo already added support to run init.d scripts already in kernel of the versions 4.1+, correct?
Why you need to add it to your zip?
Another question, what does the OOM_Priority_Charger_Aurora_4.1a.zip?

Couldn't flash OOM_Priority_Charger_Aurora_4.1a.zip through recovery, says installation aborted..
In on update 4.1a
Sent from my U8800

sr21 said:
Sorry if this question was already answered.
What are the changes in the boot.img?
dzo already added support to run init.d scripts already in kernel of the versions 4.1+, correct?
Why you need to add it to your zip?
Another question, what does the OOM_Priority_Charger_Aurora_4.1a.zip?
Click to expand...
Click to collapse
It's the same one that's in update 4.1a, I kept it because there was a boot.img in the original script, I don't know if removing it would lead to the script not working...

demolition23 said:
Couldn't flash OOM_Priority_Charger_Aurora_4.1a.zip through recovery, says installation aborted..
In on update 4.1a
Sent from my U8800
Click to expand...
Click to collapse
It's working here, I tried it again just now... what CWM are you using? You can also just extract the services.jar that's inside the zip, and copy it to /system/framework, replace the default and set permissions like the default and reboot.

fjsferreira said:
It's working here, I tried it again just now... what CWM are you using? You can also just extract the services.jar that's inside the zip, and copy it to /system/framework, replace the default and set permissions like the default and reboot.
Click to expand...
Click to collapse
I tried with 5.5.0.4 and then with 5.8.4.5.
i will redownload and try again..
EDIT
Same again...Will try manually. Thanks anyway!

Priority charger in attached files didn't work but files from Mediafire did.

fjsferreira said:
It's the same one that's in update 4.1a, I kept it because there was a boot.img in the original script, I don't know if removing it would lead to the script not working...
Click to expand...
Click to collapse
If I already have the 4.1 or 4.1a installed I already have the boot.img in my phone and It already have the support for init.d. So I think you do not need to add it to your zip.
That is creating problems only.
This is just a comment to improve your work and correct me if I'm wrong. I'll appreciate.

sr21 said:
If I already have the 4.1 or 4.1a installed I already have the boot.img in my phone and It already have the support for init.d. So I think you do not need to add it to your zip.
That is creating problems only.
This is just a comment to improve your work and correct me if I'm wrong. I'll appreciate.
Click to expand...
Click to collapse
It doesn't create any problem at all, because I didn't modify the 4.1a kernel in any way, it's the same that it's in dzo's 4.1aupdate zip.
On the other hand, removing it could cause problems with the updater script in this flashable zip, that's why I kept it in my flashable zip. You are not forced to install this zip if you don't want, but I can guarantee the boot.img is the same that's in dzo update, there's nothing bad coming from flashing it.

fjsferreira said:
It doesn't create any problem at all, because I didn't modify the 4.1a kernel in any way, it's the same that it's in dzo's 4.1aupdate zip.
On the other hand, removing it could cause problems with the updater script in this flashable zip, that's why I kept it in my flashable zip. You are not forced to install this zip if you don't want, but I can guarantee the boot.img is the same that's in dzo update, there's nothing bad coming from flashing it.
Click to expand...
Click to collapse
Hello fjsferreira,
Thanks for updating the zip, I was away for a week with no access to a PC.
I have updated the original thread with 4.1a OOM priority charger and a init.d zip that does not mess with the boot.img now that dzo has included it in his ROM, so it should be compatible with newer versions.

I ve read the threads but still dont know what is OOM priority charger or any charger and init.d . Can someone explain it to m?
Sent from my U8800 using xda app-developers app

bassdrum01 said:
I ve read the threads but still dont know what is OOM priority charger or any charger and init.d . Can someone explain it to m?
Sent from my U8800 using xda app-developers app
Click to expand...
Click to collapse
These are scripts that run at boot time to change memory management so that you always have a good amount of memory available. The package also contains some scripts to fine tune screen sensitivity, sdcard and CPU performance, those require editing the script files to uncomment some lines. Read the instructions on the other thread to fine out how to use this.
Sent from my U8800

[Q] Android is upgrading every startup

Everytime I turned on my phone or if it rebooted, I always get:
Android is upgrading
-----------------------------
Starting Apps.
I am on stock ROM, TWRP recovery, Faux kernel. I think this happens after I wiped dalvik/cache in the recovery. Any idea how to stop it? It's nothing very major though as it only takes a few seconds.

are you using any sound/volume mods? or any other flashable mods? i think awesomebeats dies this, at least others have complained about it wiping the dalvik after every reboot.

cdon2109 said:
Everytime I turned on my phone or if it rebooted, I always get:
Android is upgrading
-----------------------------
Starting Apps.
I am on stock ROM, TWRP recovery, Faux kernel. I think this happens after I wiped dalvik/cache in the recovery. Any idea how to stop it? It's nothing very major though as it only takes a few seconds.
Click to expand...
Click to collapse
That's normal if you've wiped the Dalvik cache, and no you can't stop it.
Edit: so wait, this is happening even when you reboot normally after not wiping any caches or flashing a kernel?

CMNein said:
That's normal if you've wiped the Dalvik cache, and no you can't stop it.
Edit: so wait, this is happening even when you reboot normally after not wiping any caches or flashing a kernel?
Click to expand...
Click to collapse
yes.. and it updates apps after delvic wipe.. but in my case whenever i restart I see the "Android is upgrading" box for about 3-5 sec.. no update app progress bar.. and when I wipe delvic this upgrading apps takes like a min or so with my 150+ apps.. but this "Android is upgrading" dialogue box appears only for 3-5 sec..
I am using PA 3.99 with franco kernel.. once booted every thing inside is running smoothly and no fc's...

Same here. No odex files in app folder. No wipe, no cache clearing. Plain reboot. And Android is upgrading message on every boot. (Starting apps)
No optimizing apps message though.
Sent from my Nexus 4

Wouldn't it be related to "zipalign apk on each boot" parameter ? or an other init script put in place by a dirty flash (no /system or /data format) or a kernel... ?

Seems likely. Could you explain in detail kindly?
Sent from my Nexus 4

anandbibek said:
Seems likely. Could you explain in detail kindly?
Sent from my Nexus 4
Click to expand...
Click to collapse
Have a look in the files located in this folder for example (maybe there's another location for init scripts) :
- /system/etc/init.d/
- /system/addon.d/
and open each one, to see what are the tasks contained

benbugohit said:
Have a look in the files located in this folder for example (maybe there's another location for init scripts) :
- /system/etc/init.d/
- /system/addon.d/
and open each one, to see what are the tasks contained
Click to expand...
Click to collapse
Removed the scripts present in init.d folder and then booted with empty folder, but message still present.
Checked the addon.d folder, but those scripts are only for backing up gapps etc.
Not sure where else to try. Please advise.
Thanks.

anandbibek said:
Removed the scripts present in init.d folder and then booted with empty folder, but message still present.
Checked the addon.d folder, but those scripts are only for backing up gapps etc.
Not sure where else to try. Please advise.
Thanks.
Click to expand...
Click to collapse
Did you try to re-flash your (stock) ROM (and the kernel after 2 reboots) with wiping only /cache and dalvik-cache ? with latest 2.6.2.0 TWRP ?

happens to me too
Sent from my Nexus 4

I've seen people get this with stuff like V6 Supercharger by Zepplinrox and similar scripts.

Edit : @Dungeon47: thanks for this information that users can't provide...
HeyyMyNameIs said:
happens to me too
Sent from my Nexus 4
Click to expand...
Click to collapse
A pity that so much details are missing : what did you do before it happened ?
What's your set up ? rom, kernel ? after having update your rom ? kernel ? apps ? which versions ?
Did you try to revert to a clean install after having backup up your apps+datas ?

benbugohit said:
Edit : @Dungeon47: thanks for this information that users can't provide...
A pity that so much details are missing : what did you do before it happened ?
What's your set up ? rom, kernel ? after having update your rom ? kernel ? apps ? which versions ?
Did you try to revert to a clean install after having backup up your apps+datas ?
Click to expand...
Click to collapse
im sorry, just wanted the OP to know that he is not the only one with this "problem" by the way im rooted stock rom and kernel, some apps start up when i boot like nova launcher, lucky patcher sidebar and udn. But i am not looking for a fix for this as this does not take that long and i just said that to let the OP know that he is not alone with this "problem"
Sent from my Nexus 4

Ok guys,
Here's the solution. Don't flame me for talking about unholy stuffs. I'm posting this only because it is the cause of the problem.
If you are using LP or such tools to create .odex files of some app in /app folder. It won't cause any boot msg.
But after you dirty flash a ROM, that .odex files somehow gets backdated and causes the UPGRADING msg.
Fix is, delete the odex files, and re create them if needed. Once after every dirty flash.
Sent from my Nexus 4

I have found fix for this error, it is mainly due to odex files which are created by lucky patcher so deleting these files using lucky patcher itself will surely remove this error with 50 percent success rate. Here's the fix; open lucky patcher, there in lower left section you can see Toolbox, click that Toolbox then select 4th last option i.e Remove all odex files.Thats it android will reboot on itself and vola no android is upgrading. .
Check out attachment for help.
:good:Hits Thanks If I helped u:good:

Updating CM10.1 on i9505 international

I keep getting status 7 errors when I try to update my CM install on my i9505 international, (i'm using latest philz recovery). So far I have solved the problem by doing a full wipe and a ROM prep wipe. This is obviously not great because I have to set up the phone from scratch.
For various reasons I do not have access to a computer so cannot do the unzip / modify / rezip solutions referred to in many posts.
Is there another way i can update to the latest nightly builds? And what is causing this problem?
Thanks for help

as far as i know this is because the rom is build for us t-mobile edition.
you need to delete one line ... otherwise it won't work. so you need a computer for this.
also full wipe isn't enough. also delete preload and system.
hope this helps

birdr said:
I keep getting status 7 errors when I try to update my CM install on my i9505 international, (i'm using latest philz recovery). So far I have solved the problem by doing a full wipe and a ROM prep wipe. This is obviously not great because I have to set up the phone from scratch.
For various reasons I do not have access to a computer so cannot do the unzip / modify / rezip solutions referred to in many posts.
Is there another way i can update to the latest nightly builds? And what is causing this problem?
Thanks for help
Click to expand...
Click to collapse
You can do everything you need on your phone. I use Root Explorer to unzip, delete the format line and zip. Works fine if you do that and it's pretty easy to do.
chrisknife said:
as far as i know this is because the rom is build for us t-mobile edition.
you need to delete one line ... otherwise it won't work. so you need a computer for this.
also full wipe isn't enough. also delete preload and system.
hope this helps
Click to expand...
Click to collapse
That's not true and it's not why anyway. It's a problem with the recovery.

do you have any nfo ( workaround) how the update procedure can be done?

3bs11 said:
You can do everything you need on your phone. I use Root Explorer to unzip, delete the format line and zip. Works fine if you do that and it's pretty easy to do.
That's not true and it's not why anyway. It's a problem with the recovery.
Click to expand...
Click to collapse
ok sorry then...
i thought it's the same like on aokp nightlies.
for me it helped to delete preload and system...
had this error before too. after formating this it worked.

Thanks all. I got this working based on the advice given.
Precisely:
1. I extracted the nightly using ES file explorer.
2. I used a text editor to remove the line
format("ext4", "EMMC", "/dev/block/mmcblk0p16", "0", "/system");
from
/META-INF/com/google/android/updater-script
3. Then I re-zipped using ES file explorer.
4. Then i flashed as normal with philz recovery, wiped cache and rebooted.
Worked first time and everything upgraded as expected.
Thanks again for the help.

Transplant stock radio layer

I'm not sure if this is the right place to post this, but here goes.
I was running Mokee 4.3, and loved it; but the battery life was terrible.
So I went back to White Rabbit 2.11.
Now I'm getting lots of reboots due to Errors in Telephony Layer.
My question is: Is it possible to take the RIL from the stock ROM and replace it in White Rabbit?
If so, which files should I copy?
Thanks

Rijidij said:
I'm not sure if this is the right place to post this, but here goes.
I was running Mokee 4.3, and loved it; but the battery life was terrible.
So I went back to White Rabbit 2.11.
Now I'm getting lots of reboots due to Errors in Telephony Layer.
My question is: Is it possible to take the RIL from the stock ROM and replace it in White Rabbit?
If so, which files should I copy?
Thanks
Click to expand...
Click to collapse
Copy the bp_nvm_default folder from system/etc into the ROM.
Sent from my Nexus 7 using Tapatalk

hotdog125 said:
Copy the bp_nvm_default folder from system/etc into the ROM.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thanks. I'll give this a try.

Update - progress so far:
As per advice from hotdog125, I copied the bp_nvm_default folder from a nandroid of the (rooted) stock ROM.
I found it in the /system/etc/motorola folder in this ROM
It appears to be working so far - I will keep a close eye on it for telephony errors...
If others want to try the same, here are the steps I took. (YMMV)
Extract the bp_nvm_default folder from the stock ROM (in /system/etc/motorola)
Rename to bp_nvm_default.stock
Copy to phone SD card
On the phone, copy from SD card to /system/etc/motorola
I had to chmod the folder to 755, and all the contents to 644 (again, YMMV)
Rename the existing bp_nvm_default folder to bp_nvm_default.bak
Rename bp_nvm_default.stock to bp_nvm_default
Reboot...
My phone booted up OK, and everything looked fine. So I decided to push a bit further. :fingers-crossed:
Reboot into recovery
Clear cache and dalvik cache
Reboot...
Again, I had success!
A few points:
Steps 4-7 were possible thanks to JRummy's ROM Toolbox Pro (great tool - worth every penny! :good
A message appeared saying changing permissions failed, but after refreshing the list, permissions were correct.
I had to chmod each file in the folder individually - a bit of a pain, but it only took a few minutes. (I tried it in the terminal, but that definitely didn't work).
Baseband has defaulted to Central Europe 3.4.2-145. I'll leave it on that one for now and see how it goes.
On the subject of Baseband, I'm in the UK and have these available under the GB heading:
3.4.2-117
3.4.2-11
2.51
T-Mobile 2.51
T-Mobile 2.21
3.4.3-3
4.5.1-85
Any recommendations from this list?
Thanks

Update:
No telephony reboots so far...
But the phone has got quite hot (while dark) on a couple of occasions.
Also, I couldn't get a connection to the Play Store this morning. Toggling Aeroplane Mode fixed it.
I might try one of the other basebands next.

Arrrgh! I spoke too soon!
RIL bug has struck 3 times since last night...
Damn... I thought I had this fixed.

RIL Bug is due to hardware issues. Changing the baseband will not help unfortunately
The best way to fix it is to use one of the later builds which have incorporated SlugZero's RIL patches
Sent from my MB526 using Tapatalk 4