{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi all. I just want to share how to change your splash screen, if ever you want a customized one. I created my own, for FENECK-Rom_GNT_DEV. So without further ado, here's the tutorial:
NOTE: Tested perfectly on STOCK-Rom without any problems.
Pre-requisites:*
- Rooted device
- Terminal Emulator
- Back up!
** Warning **
It is forbidden to reproduce this tutorial on another forum without asking permission.
If you use this tutorial to produce a content on your rom think about granting credit to my humble effort (thanks)
This operation involves risks: This forum "Galaxy-Note-Team & XDA" and / or myself can not be held responsible for any problems encountered during installation or possible handling problems.
WELL READ THE TUTO BEFORE ANY MANIPULATIONS (SAME SEVERAL TIMES)
Steps:
☆1.) Start emulator terminal
now for the codes:
☆2.)Now type:
su
Click to expand...
Click to collapse
☆3.)Now it's time to pull out the up_param.bin, which contains the splash logo:
dd if=/dev/block/platform/11120000.ufs/by-name/UP_PARAM of=/sdcard/up_param.bin
Click to expand...
Click to collapse
☆4.)Now we must create a folder on main sd card:
mkdir /sdcard/up_param
Click to expand...
Click to collapse
☆5.)Then enter the directory:
cd /sdcard/up_param
Click to expand...
Click to collapse
☆6.)And untar the up_param.bin into the created folder:
tar xf /sdcard/up_param.bin
Click to expand...
Click to collapse
If all goes well, you can see a up_param folder in your main sdcard (mine is in internal memory), which has all the bootloader's images. Just copy the logo.jpg to your PC.
☆7.)Now you can edit the logo.jpg to your liking - note that the background should remain black, and the size should not be more than +-400KB.
☆8.)Once done editing, copy your customized logo.jpg on main sd card
☆9.)Then, we have to paste it inside /sdcard/up_param folder, and re tar up_param.bin:
cp -f /sdcard/logo.jpg /sdcard/up_param/logo.jpg
cd sdcard/up_param
tar cf - `ls | sort -t.` > /sdcard/up_param.bin
Click to expand...
Click to collapse
☆10.)Lastly, we need to return up_param.bin in system:
dd if=/sdcard/up_param.bin of=/dev/block/platform/11120000.ufs/by-name/UP-PARAM
Click to expand...
Click to collapse
☆11.)After these steps, reboot!
VOILA! Now you have your won splash image!*
I created some for FENECK-Rom_GNT_DEV .
Credits:
@topjohnwu For Magisk v13.0 (96f8efc)
@Chainfire For SuperSU
@MitoTakatori For the tutorial I inspired
@XDA For To allow us to exchange and learn
@GalaxyNoteTeam=Team Dev Fast&FamousTo be a great team of sharing and mutual aid
@baloo30310To make me the pictures I need
@thijac99To make me fast mirrors rom
@IZI.XavFor creating our GalaxyNoteTeam forum and the Fast & Famous team
ContributorsLE FENECK >>> http://www.galaxynoteteam.com/, - FrenchFamousTeam® - GNT
If my work pleased you hit the button thank you.
Thank you
Excellent tutorial man, thanks! I performed all the actions within ES File Explorer except for the tar and untar commands. Everything worked beautifully, thank you!
I read in a related post several weeks ago... and experienced the same with this.... that the new logo.jpg appears offset a few hundred pixels from the top of the screen. Any idea how to center it?
(I noticed the recompiled UP_PARAM is much smaller sized [1.xx mb] compared to the 8.0 mb original)
Sent from my SM-G955F using Tapatalk
RuggedHunter said:
Excellent tutorial man, thanks! I performed all the actions within ES File Explorer except for the tar and untar commands. Everything worked beautifully, thank you!
I read in a related post several weeks ago... and experienced the same with this.... that the new logo.jpg appears offset a few hundred pixels from the top of the screen. Any idea how to center it?
(I noticed the recompiled UP_PARAM is much smaller sized [1.xx mb] compared to the 8.0 mb original)
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
Hello
Thank you for the feedback :bien:
For my part the splash is not shifted up, but to the right of the screens
Baloo (my designer) is working on this worry.
For the file size I do not know.
I made 10 times the manipulation before sharing here, as I did not notice any worries I wrote the tutorial.
I will modify it a can there is 1 line of which I do not use to recompile and it works anyway, then I will supress it.
Excuse my bad English, I'm only french :rire:
Yeah, im not too concerned about the file size either, just an observation.
For me it seems like the image is anchored at about 0,800 instead of 0,0...wierd, but acceptable.
Sent from my SM-G955F using Tapatalk
Ok thanks for the observations
I will try to modify the images of the donload mode to see what it says.
:highfive:
I think the stock logo.jpg has an aspect ratio of 3:4...and using an image with a different ratio might contribute to the offset issue. When I convert my custom logo to 3:4 ratio the file size changes to 516kb.... What is the risk of using an image >400kb?
Sent from my SM-G955F using Tapatalk
my
Hypothesis is that at best it goes to the worst it bootloop because it can not display the image
Better to have a backup
Currently my image does 460kb
pendor24 said:
dd if=/dev/block/platform/11120000.ufs/by-name/UP-PARAM of=/sdcard/up_param.bin
Click to expand...
Click to collapse
UP-PARAM needs to be UP_PARAM (It's an Underscore, Not a Hyphen)
Guide works perfectly, Managed to change the Splash of my G955FD!
pendor24 said:
my
Hypothesis is that at best it goes to the worst it bootloop because it can not display the image
Better to have a backup
Currently my image does 460kb
Click to expand...
Click to collapse
516kb booted just fine. But 3:4 aspect ratio didn't resolve offset.
Sent from my SM-G955F using Tapatalk
OK
I just try with an out of proportion picture
And bootloops, impossible to restart, I got out by restarting in donload mode and by reflashing the bootloader with odin
JazonX said:
UP-PARAM needs to be UP_PARAM (It's an Underscore, Not a Hyphen)
Guide works perfectly, Managed to change the Splash of my G955FD!
Click to expand...
Click to collapse
Hello
Thank you, I correct this desuite
Thank you
I've got my image centered perfectly now. I'll try to explain what I did and the logic of why. I'm not sure if it will work for you though if your image is offset to the side, but this worked for me:
By observing the stock bootsplash I noticed the white words "samsung" appears a few hundred pixels from the top of the screen while booting. But observing the jpg of that stock splash image, it's cropped to just above and below the lettering.
My first custom logo.jpg was offset significantly far down the screen. This is the image I was using:
My first hypothesis was that the stock image appeared to be 3:4 ratio (to my naked eye), so I resized my custom logo to that ratio. The result was still offset significantly, but on closer inspection, it was not as severe as my first attempt. Here's the 3:4 image:
My second approach was to crop my custom logo.jpg to eliminate any black background above and below the image. This appears to work perfectly for me. I'm not certain if it's and actual fix or if it's a coincidence that my cropped image size appears centered with this default offset. Here's my custom logo.jpg now:
Take it with a grain of salt perhaps, but my recommendation is to trim all negative space around the image that you want to use for this project.
New file size is 526.33 kb and booted up fine.
Sent from my SM-G955F using Tapatalk
I did not understand everything, but I do tests.
Thank you for all these explanations.
It is centered perfectly but it is aligned at the bottom of the screen
Guys, it's work on other custom roms? (Minotaurus, Batman e.g.)
YunusalievFarhod said:
Guys, it's work on other custom roms? (Minotaurus, Batman e.g.)
Click to expand...
Click to collapse
Hello
Yes it works on all rom (based on S8 +)
pendor24 said:
It is centered perfectly but it is aligned at the bottom of the screen
Click to expand...
Click to collapse
Hmmm..... maybe try adding a few hundred pixels of black background to the *bottom* of the image so it kinda pushes the blue graphic up off the bottom of the screen?
Sent from my SM-G955F using Tapatalk
RuggedHunter said:
Hmmm..... maybe try adding a few hundred pixels of black background to the *bottom* of the image so it kinda pushes the blue graphic up off the bottom of the screen?
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
I will try this
thanks for the Tut, I was able to change the logo.
but after this splash there is another animation. how do i change that one as well ?
Salut pendor24,
Merci pour le partage.
Related
For those of you who may not have taken kindly to Asus' skinning of our beloved Honeycomb OS, you will be happy to know that it's possible to change some aspects of the UI to make it look more "stock". The most notable change that Asus has made, was with the replacement of the stock Honeycomb navigation keys with icons that seem less sleek and frankly, just don't flow with the holographic theme of the OS.
To combat Asus' lack of taste, it's possible, with some hackery, to get the stock navigation icons that you would find on the Motorola Xoom. If you are at all confused of what icons I am speaking of, it's the back, home and multitasking icon located at the bottom left of the screen; they will be changed to look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
While I do enjoy the custom Asus widgets that were included in the Transformer, I would much rather prefer the navigation buttons native to a stock Honeycomb OS. I am always "pro-vanilla" when it comes to Android because system updates will most likely be pushed out faster to the user if the manufacturer didn't have to waste more time putting in their little touches to the user interface-I digress.
The procedure is simple but it does require you HAVE ROOT! The easiest way, believe it or not, is to use ADB and the command prompt to effectively change the necessary files. You can install ADB from the official Android development site:
http://developer.android.com
For your convenience, I have already made a backup of the file you will be replacing (see the end of the article) such that, if you ever need to revert to the "stock" Asus theme, then you just need to download the file and use the same procedure below.
Lets get started! All credit goes to XDA member JaiaV. I am simply making a how-to & we are not responsible if you brick your device.
1) Download this file if you are on Android 3.0.1:
Modified SystemUI.apk
Download this file if you are on Android 3.1:
http://dl.dropbox.com/u/2993232/modified/3.1/SystemUI.apk
Prime 1.4
http://db.tt/UI10NAk
Thanks Andrew2511
thanks xformulax
Put this file inside the folder that contains the adb.exe (probably quicker if you just search for it using the native Windows search tool). If you are using the newest version of the developer tools then the folder that contains the ADB.exe should be called "Platform-tools"; put the file in the Platform-tools folder. This way, when you run the ADB command below, the system will know where the file you just downloaded is, which makes everyone's life easier.
2) Enable USB Debugging on your tablet by going into your settings > Applications > Development
3) Plug your Transformer into your Windows machine
4) Launch up your command prompt
5) **REMEMBER, YOU NEED TO HAVE ADB INSTALLED PRIOR TO DOING THIS**
Type in:
Code:
adb devices
you should see your device connected. It should look like this:
6) Once you know your device is connected properly, type in:
Code:
adb remount
7) Next, you just have to type in:
Code:
adb push SystemUI.apk /system/app
8 ) Lastly, to reboot your system quickly, type in:
Code:
adb reboot
If for some reason you would like to go back to stock, its pretty simple. All you have to do is download the file below:
For 3.0.1:
Stock SystemUI.apk
For 3.1:
http://db.tt/eQkoYIk
Then just repeat the procedure above (starting from number 6) and you are all set to go! Just a quick way to make your Asus Transformer look just a bit more awesome!
perhaps this should be in themes...
Sent from my Transformer
www.AsusTransform.com
www.AsusTransform.com/forum
xda doesnt support html.
my mistake, rushed it. fixed
It's pretty easy to do this for yourself for w/e version of the FW you happen to be using. Just adb pull your SystemUI.apk, open it up in your favorite zip/rar application, navigate to the /res/drawable-mdpi folder, and backup the ic_sysbar_home/back/recent/menu images. Should be default/pressed for each. Then move the Xoom/stock images from my SystemUI.apk (made from a deodexed Prime 1.3 SystemUI.apk, thanks to Roach and DC13, I just changed the button images) or a stock Xoom rom into your SystemUI.apk, save. Then push your modded SystemUI.apk into /system/app and you're done.
If you use a rom you can also switch out the modded SystemUI.apk in the zip file you flash, that way if you have to reinstall (or before you install a new image) you don't have to manually move the apk in afterwards. I suggest using the SystemUI.apk that came with the FW version of the rom you're using, as there can be some inconsistencies between a few.
personally i like the icons asus made better, but i don't like that they're white. too bright compared to everything else on the dock.
luckily thats a quick fix once i finally root.
i can adb devices
can someone please help me. i can not get past "adb remount"
gives me an error: "remount failed: operation not permitted"
BBjaiBev said:
i can adb devices
can someone please help me. i can not get past "adb remount"
gives me an error: "remount failed: operation not permitted"
Click to expand...
Click to collapse
You need root.
this doesn't work on 3.1. Any chance of an update?
Sent from my Transformer TF101 using XDA Premium App
mattykellyuk said:
this doesn't work on 3.1. Any chance of an update?
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
I'd like them on 3.1 too...
djdevine2 said:
I'd like them on 3.1 too...
Click to expand...
Click to collapse
updated! enjoy.
neok44 said:
personally i like the icons asus made better, but i don't like that they're white. too bright compared to everything else on the dock.
luckily thats a quick fix once i finally root.
Click to expand...
Click to collapse
+1, not to harp on the OP, but the Asus Icons (even the Samsung TouchWiz Icons) are much more visually appealing and intuitive to me.
But that's a personal preference. This guide should be useful to anyone looking to make custom icons.
Yep, this thread shows quite nicely that nothing is right for everyone. Me, if there was one thing about the Transformer's styling I would change, it's the stock Google clock font. To me, it looks like cheap and amateurish, and the styling doesn't really fit or match anything else in the OS (other than perhaps the buttons that Asus changed.)
I hope in a future release, Google makes these things user-styleable. I'd much rather have a different font for the clock, which could make it instantly more readable while saving valuable screen space to boot.
But obviously other people are perfectly happy with it...
I flashed the Xoom ones which worked fine but I didn't like them to pushed the original ASUS ones back, however SystemUI.apk force closes constantly and I have lost the status bar. I'm on 3.1 and used the right files.
djdevine2 said:
I flashed the Xoom ones which worked fine but I didn't like them to pushed the original ASUS ones back, however SystemUI.apk force closes constantly and I have lost the status bar. I'm on 3.1 and used the right files.
Click to expand...
Click to collapse
try pushing this file back. thats the original one for 3.1.
http://db.tt/eQkoYIk
ok will give it a shot!
Still force closing..... weird
djdevine2 said:
Still force closing..... weird
Click to expand...
Click to collapse
are you pushing it through adb? Can u try something like root explorer?
ayman07 said:
are you pushing it through adb? Can u try something like root explorer?
Click to expand...
Click to collapse
I've been using root explorer as don't have PC with me at the moment, weird that Xoom worked at first, don't worry too much about it, I'll try with ADB in morning. (It's 10:40 in UK)
djdevine2 said:
I've been using root explorer as don't have PC with me at the moment, weird that Xoom worked at first, don't worry too much about it, I'll try with ADB in morning. (It's 10:40 in UK)
Click to expand...
Click to collapse
make sure you check your permissions.
also, i just skimmed the guide, but i'd probably put a permissions change in the instructions just to ensure everyone has proper permissions on install.
not sure if anyone is interested, but i plan on taking the stock asus and changing just the colors to match honeycomb (versus changing the actual icons)
xformulax said:
make sure you check your permissions.
also, i just skimmed the guide, but i'd probably put a permissions change in the instructions just to ensure everyone has proper permissions on install.
not sure if anyone is interested, but i plan on taking the stock asus and changing just the colors to match honeycomb (versus changing the actual icons)
Click to expand...
Click to collapse
I use root explorer, after i moved it to system/app reboot and work fine.
It doesn't hurt to check permission though. rw,r,r
Edit: I just moved my original systemUI.apk back using root explorer and sems permission
Was changed. I set it to rw,r,r reboot and origin icons are back no FCs
Sent from my Transformer TF101 using Tapatalk
Hello Everyone,
I have the Bodhi Linux distro working on our beloved Iconia. Just download the two images from my site. Flash recovery.img to the recovery partition using Acer Recovery Installer. Decompress the Bodhi image, and image it to an 8GB+ memory card (stupid, but will be fixed for smaller ones). Boot into recovery. Screenshots available upon request. Be sure to give me any feedback. I'll remove the PayPal donation link if it counts as spam. I recommend reading this thread. Sorry guys if this seems rushed, but it's 3:30 AM, and I have a long day tomorrow. Perhaps I'll clean this post up later. Kernel Source
Night Everyone,
apapousek
PS: The password for the debian user is debian, and the root password is iconia.
PPS: You can launch the virtual keyboard from the top bar.
Update: So, Wifi is working. Under wicd, change the default interface to wlan0. You may have to put your own nvram.txt from your iconia into the appropriate folder to make things work. The one from my iconia is currently in there.
UPDATE
Alright, so this first post is vague, the download is large, and kind of iffy. But it's smooth, and that's what I'm going for. Within the next week (hopefully), expect an Alpha 2 post, which will have fixed some WiFi issues, and will have some automated scripts for getting your nvram from android, etc.
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oh my, can someone please confirm if this is fully working with wifi, sound, etc.
I'm afraid of bricking my iconia tab.
Thanks in advance.
UntitledX said:
Oh my, can someone please confirm if this is fully working with wifi, sound, etc.
I'm afraid of bricking my iconia tab.
Thanks in advance.
Click to expand...
Click to collapse
Well it really can't brick it, unless Acer Recovery Installer screws up somehow. You dd the main Bodhi image to the external sd using a computer. This way the only thing written to the internal memory would be a different recovery image. In theory, nothing should be bricked. I can't promise anything, though.
I have flashed recovery.img to the recovery partition using Acer Recovery Installer.
I can not copy bodhi_iconia.raw in a 8GB microSD,it is too big.
I'm trying to unzip the file directly into the microSD.
I returned to the thor recovery without problem. It is safe.
I will try again this afternoon.
Looks interesting, will try it out Thanks mate!
HDJ80 said:
I have flashed recovery.img to the recovery partition using Acer Recovery Installer.
I can not copy bodhi_iconia.raw in a 8GB microSD,it is too big.
I'm trying to unzip the file directly into the microSD.
I returned to the thor recovery without problem. It is safe.
I will try again this afternoon.
Click to expand...
Click to collapse
Sorry if I was a wee vague. It's not meant to be copied straight to a microSD. First, uncompress it to the .raw file. Then, use dd to image directly to the card, not to a partition. For example:
dd if=file.raw of=/dev/mmcblk0 bs=4M (Do not have of=/dev/mmcblk0pX, where X is a partition.)
thyultimate said:
Looks interesting, will try it out Thanks mate!
Click to expand...
Click to collapse
Thanks for trying it out! You may have to use the nvram.txt from your Android side to make the wifi work, I'm still squashing out little bugs here and there.
This is fantastic!
I'm still trying to get wifi working they you mentioned in OP, and I'm changing the way it looks haha. But it runs smooth!
where am i supposed to place the nvram file? on android its in /system/etc/ but that location isnt on bodhi, ive also done a search of the files and its nowhere in the img.. am i supposed to add the directory /system/etc/nvram.txt or /android/system/etc/nvram.txt? or am i going about this at the wrong direction?
n1nj4dude said:
where am i supposed to place the nvram file? on android its in /system/etc/ but that location isnt on bodhi, ive also done a search of the files and its nowhere in the img.. am i supposed to add the directory /system/etc/nvram.txt or /android/system/etc/nvram.txt? or am i going about this at the wrong direction?
Click to expand...
Click to collapse
Okay, rename nvram.txt to bcm4329-fullmac-4.txt . Delete /lib/firmware/brcm/bcm4329-fullmac-4.txt (from my device, will be fixed in next release) and put your bcm4329-fullmac-4.txt in its place.
screenshots please- looking forward to this with alot of curiousity!
Could you please mention what is and is not working- thnks alot keep up the good work!
apapousek said:
Sorry if I was a wee vague. It's not meant to be copied straight to a microSD. First, uncompress it to the .raw file. Then, use dd to image directly to the card, not to a partition. For example:
dd if=file.raw of=/dev/mmcblk0 bs=4M (Do not have of=/dev/mmcblk0pX, where X is a partition.)
Thanks for trying it out! You may have to use the nvram.txt from your Android side to make the wifi work, I'm still squashing out little bugs here and there.
Click to expand...
Click to collapse
Is there any way to do that from Windows or android?
Thanks.
So is this considered dual booting? Or is this a replacement for android itself? looking forward to the screen shots!
newbkilla said:
So is this considered dual booting? Or is this a replacement for android itself? looking forward to the screen shots!
Click to expand...
Click to collapse
Its a dual boot, you reboot into recovery mode like you would cwm and it boots bodhi instead..boot normal and it loads your rom
thank you so much.
Hello everyone. Can someone make a some video for this linux, i wanto see how its look like. I can't make it on my iconia, because my tablet isn't in my hands yet.. And sorry if my english bad.
apapousek said:
Sorry if I was a wee vague. It's not meant to be copied straight to a microSD. First, uncompress it to the .raw file. Then, use dd to image directly to the card, not to a partition. For example:
dd if=file.raw of=/dev/mmcblk0 bs=4M (Do not have of=/dev/mmcblk0pX, where X is a partition.)
Thanks for trying it out! You may have to use the nvram.txt from your Android side to make the wifi work, I'm still squashing out little bugs here and there.
Click to expand...
Click to collapse
What was exactly meant by this?
apapousek said:
Hello Everyone,
I have the Bodhi Linux distro working on our beloved Iconia. Just download the two images from my site. Flash recovery.img to the recovery partition using Acer Recovery Installer. Decompress the Bodhi image, and image it to an 8GB+ memory card (stupid, but will be fixed for smaller ones). Boot into recovery. Screenshots available upon request. Be sure to give me any feedback. I'll remove the PayPal donation link if it counts as spam. I recommend reading this thread. Sorry guys if this seems rushed, but it's 3:30 AM, and I have a long day tomorrow. Perhaps I'll clean this post up later.
Night Everyone,
apapousek
PS: The password for the debian user is debian, and the root password is iconia.
PPS: You can launch the virtual keyboard from the top bar.
Update: So, Wifi is working. Under wicd, change the default interface to wlan0. You may have to put your own nvram.txt from your iconia into the appropriate folder to make things work. The one from my iconia is currently in there.
UPDATE
Alright, so this first post is vague, the download is large, and kind of iffy. But it's smooth, and that's what I'm going for. Within the next week (hopefully), expect an Alpha 2 post, which will have fixed some WiFi issues, and will have some automated scripts for getting your nvram from android, etc.
Click to expand...
Click to collapse
Good job apapousek. After reading this thread, the only comment I have is you're going to need to make the install as id10t proof as possible. If they can screw it up, they will!
What I want to know is what he meant when he told us to use DD to put the file onto the sd card. What you're telling us, is that we cannot just place it there ourselves, we have to do something else?
newbkilla said:
What I want to know is what he meant when he told us to use DD to put the file onto the sd card. What you're telling us, is that we cannot just place it there ourselves, we have to do something else?
Click to expand...
Click to collapse
yes.
youve never tried to copy a extra large file to a drive have you? fat doesnt support transferring files 4gb+ so NO you cant just copy it over yourself
Alright well, i have virtual box installed with ubuntu 11.04, and when i type "sudo bash" Im now in root. Once i'm there, I have typed in "sudo fdisk -l" and it lists:
Disk / dev/sda: 8589 MB, 8589934592 bytes blah blah blah
Disk /dev/sda doesn't contain a valid partition table
[email protected]:~#
I have a 32 GB micro inserted into my sd card slot in my computer. Am I going in the right direction and can I get a little guidance with what I'm doing? I've actually never moved a file large enough to have to do this... so i'm starting off as a noob, hah.
As ive been reading about this very much lately, after people have flashed Marshmallow and rooted, many are having issues editing their build.prop files. And many arent having any issues at all. Well, the fix is rather easy. You are going to have to change your SElinux to be permissive. Many that arent having the issue is because they are either using a custom kernel that has set SElinux to be permissive, or are using an app to change it. I use an app, dir viper4, because it needs to gave SElinux at permissive. There arent any apps that do it in the play store, because google removed them. But.. theres a site called xda that somebody is posting their SElinux changer app in http://forum.xda-developers.com/showthread.php?t=2524485
setenforce 0 don't work no mo on dat m?
Sent from my Nexus 6 using Tapatalk
713brianp27 said:
setenforce 0 don't work no mo on dat m?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
probably does, but an app that does it would be easier, for most. but you are right
Why did Google remove the apps that allow you to do this?
rester555 said:
Why did Google remove the apps that allow you to do this?
Click to expand...
Click to collapse
security?
simms22 said:
About Google removing apps . . . . . . .security?
Click to expand...
Click to collapse
Just assuming . . . Google dev's have managers that puts them under pressure. . . Why. . .
1. Deals with telecom providers; demanding special factory images. Project Fi.
2. Ignoring many user requests; forcing encryption and forcing to use apps with text on white background.
3. Dark material removed since M-preview 3.
4. Use of RRO layers needs root access.
5. Deals with banks for Android Pay; not working when rooted.
6. Bloat. Built-in apps that should be in the play store.
7. Privacy. Services that can't be blocked.
8. Boot message device corrupt when it isn't.
This 6.0 update is a much bigger pain in the ass then it needs to be. Especially for Nexus devices which are suppose to be "mod" friendly. What gives Google?
First thing that comes to mind, is that you shouldn't EVER BE editing /system/build.prop. Its purpose is that it is generated by the build, hence "build".prop. If you need custom properties added to the system, use /data/local.prop.
Second thing is that most of the problems with system partition edits are NOT due to selinux problems. Most are because the factory sysimage bloats it absolutely FULL of crap. Delete some junk like google photos (which is a bloated pig).
Third, there is *absolutely no* reason to disable selinux. Just switch your context to one that matches the files you are trying to interact with. The su command has a parameter "--context" that lets you do this. Look it up.
NLBeev said:
Just assuming . . . Google dev's have managers that puts them under pressure. . . Why. . .
1. Deals with telecom providers; demanding special factory images. Project Fi.
2. Ignoring many user requests; forcing encryption and forcing to use apps with text on white background.
3. Dark material removed since M-preview 3.
4. Use of RRO layers needs root access.
5. Deals with banks for Android Pay; not working when rooted.
6. Bloat. Built-in apps that should be in the play store.
7. Privacy. Services that can't be blocked.
8. Boot message device corrupt when it isn't.
Click to expand...
Click to collapse
There are many logical reasons, however.
1)ProjectFi actually NEEDS special factory images
2)Security
3)It was unstable and needs more work (they are improving it for future releases)
4)I'm actually not sure about this one... I agree with you
5)Security
6)They've remove most apps like PinyinIME and HindiIME from the system with 6.0
7)Security
8)Security
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Dang old security. Pha. Lol. Don't need permissive w viper. [emoji12]
Official Team Bliss Flo, Deb, v410 Maintainer
Sent from my Nexus 6 using Tapatalk
if i make any changes to build.prop at reboot my phone just sits at the Google screen. Even after setting SElinux to be permissive.
Any other solutions???
I'm running MRA58k rooted with supersu v2.50
mrizvi66 said:
if i make any changes to build.prop at reboot my phone just sits at the Google screen. Even after setting SElinux to be permissive.
Any other solutions???
I'm running MRA58k rooted with supersu v2.50
Click to expand...
Click to collapse
What kind of changes did you make? Did you do a backup of the build.prop file before the changes?
Pecata said:
What kind of changes did you make? Did you do a backup of the build.prop file before the changes?
Click to expand...
Click to collapse
yes, I made a backup. so i'm up and running.
all i tried to add was:
net.tethering.noprovisioning=true
i added it at the very bottom. i've done it before on lollipop and it worked before i'm not sure why it's not working now tho.
mrizvi66 said:
yes, I made a backup. so i'm up and running.
all i tried to add was:
net.tethering.noprovisioning=true
i added it at the very bottom. i've done it before on lollipop and it worked before i'm not sure why it's not working now tho.
Click to expand...
Click to collapse
if you make any spelling errors or gramatical errors, or miss any spaces, your phone wont ever boot up.
Pecata said:
What kind of changes did you make? Did you do a backup of the build.prop file before the changes?
Click to expand...
Click to collapse
simms22 said:
if you make any spelling errors or gramatical errors, or miss any spaces, your phone wont ever boot up.
Click to expand...
Click to collapse
does it need an extra space at the end of the file? i think i might have removed that.
mrizvi66 said:
does it need an extra space at the end of the file? i think i might have removed that.
Click to expand...
Click to collapse
no.
i use root explorer to edit my build.prop btw. what ill do is just copy/paste the line in, save it, then reboot. and it always is fine(unless i write it myself and mess it up).
simms22 said:
no.
i use root explorer to edit my build.prop btw. what ill do is just copy/paste the line in, save it, then reboot. and it always is fine(unless i write it myself and mess it up).
Click to expand...
Click to collapse
that's exactly what i do.
i just tried it again right now and it worked. strange.
thanks for you help both of you :good:
doitright said:
First thing that comes to mind, is that you shouldn't EVER BE editing /system/build.prop. Its purpose is that it is generated by the build, hence "build".prop. If you need custom properties added to the system, use /data/local.prop.
Second thing is that most of the problems with system partition edits are NOT due to selinux problems. Most are because the factory sysimage bloats it absolutely FULL of crap. Delete some junk like google photos (which is a bloated pig).
Third, there is *absolutely no* reason to disable selinux. Just switch your context to one that matches the files you are trying to interact with. The su command has a parameter "--context" that lets you do this. Look it up.
Click to expand...
Click to collapse
Great advice on local.prop. Did not know this before. Read up on it and sounds more useful especially when applying edits you dont want to re-enter after each flash.
(Take all this with caution) Good to note for others that local.prop is read after build.prop in boot up (hope i got that right), so you can use the same lines in build.prop in local.prop with changes in the values. Those values in local.prop will override those in build.prop! *except if the same line in build.prop begins with ro. "read only". **apparently the addition of qemu. in place of ro. in local.prop will override the build.prop line setting that had ro. at the beginning. Now does anyone know what qemu is exactly? Emulator? For hardware?
MunkinDrunky said:
Great advice on local.prop. Did not know this before. Read up on it and sounds more useful especially when applying edits you dont want to re-enter after each flash.
(Take all this with caution) Good to note for others that local.prop is read after build.prop in boot up (hope i got that right), so you can use the same lines in build.prop in local.prop with changes in the values. Those values in local.prop will override those in build.prop! *except if the same line in build.prop begins with ro. "read only". **apparently the addition of qemu. in place of ro. in local.prop will override the build.prop line setting that had ro. at the beginning. Now does anyone know what qemu is exactly? Emulator? For hardware?
Click to expand...
Click to collapse
qemu is the virtual machine infrastructure used for the android emulator. It is far more generic than for just the android emulator, but android does use it. The prefixes used imply a priority, and qemu (because of its association with the emulator for testing) is considered as for testing and development purposes, so it can, as you say, override.
doitright said:
First thing that comes to mind, is that you shouldn't EVER BE editing /system/build.prop. Its purpose is that it is generated by the build, hence "build".prop. If you need custom properties added to the system, use /data/local.prop.
Second thing is that most of the problems with system partition edits are NOT due to selinux problems. Most are because the factory sysimage bloats it absolutely FULL of crap. Delete some junk like google photos (which is a bloated pig).
Third, there is *absolutely no* reason to disable selinux. Just switch your context to one that matches the files you are trying to interact with. The su command has a parameter "--context" that lets you do this. Look it up.
Click to expand...
Click to collapse
I am sorry if this is a stupid question but when you say data/local.prop-do you mean root/data/ or just data/ in internal memory?
and if I create local.prop and add the line qemu.hw.mainkeys=1 in local.prop would that be able to hide the navigation bar even if the I don't touch build.prop?
*******************************
Last Update: 25. 5. 2016 * there was a typo in a command :/
*******************************
Hello everyone!
Are you lacking Y OTG cable, but still want to boot other OSes?
Do you want to choose which OS to use on the go?
Then continue reading.
\......../
....\/.... This is just for me176c/x. It might work on other tablets,
....O.... but I'm not responsible for you trying it.
What works:
touchscreen
WiFi
[*]Internal memory
more
And what does not:
sound
Bluetooth
GPS
sensors
charging (not sure if it works, but it doesn't display :/ )
backlight controll
YOU tell me
Prerequisities:
the tablet with UEFI (android 5.0+ on this device)
microsd card (faster is better) with Ext4 filesystem (can still be mounted manualy in Android)
(optional) Y OTG cable for peripherals
internet connection to download 900MB archive
keyboard now included
(optional) a boot selector to choose system at boot (twrp can be used to boot Lubuntu otherwise)
Step 1.
download ****UPDATED ARCHIVE (onscreeen keyboard, should be extract-able) ***** http://www.mediafire.com/download/nse5sju1n31zr56/microsd.tar.gz
unpack it in the root of your microsd
Step 2.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
download grub+cfg+kernel+initramfs archive
[*]add mmc_block.perdev_minors=20 to cmdline in grub.cfg make internal memory work
using root browser, move the Lubuntu folder (with kernel etc. within) to the root of data partition (/data)
mount ESP partition on /sdcard/ESP (data/ESP if you want)
create a folder called ubuntu and move grub AND grub.cfg inside
move the ubuntu folder to /EFI/ folder in ESP (sdcard/ESP/EFI or data/ESP/EFI) (alongside Intel and BOOT folders)
umount ESP
Step 3.
download efibootmgr: http://forum.xda-developers.com/showpost.php?p=62429430&postcount=2740
from a folder with efibootmgr (move it to system so you can add execute permission) run this:
!!!!!!!!There was a typo in command below. The /p was supposed to be -p!!!!!!!!!!!!!!
Code:
./efibootmgr64 -c -d /dev/block/mmcblk0 -p 3 -l \\EFI\\ubuntu\\grubx64.efi -L ubuntu
then look if it worked:
Code:
./efibootmgr64 -v
now, if you completed my previous tutorial, this option will be 0x003, otherwise 0x0000.
now, use
Code:
./efibootmgr64 -o 0001,0000
if you only have these two options or
Code:
./efibootmgr64 -o 0001,0000,0003
if you already have refind as 0x0000
Press the start button!
Now, to try it, use
Code:
./efibootmgr64 -n 0000
to set it just for next power up and press power off, then power the tablet on.
----------------------------------------------------------------------------
Start from TWRP
If everything works well, use
Code:
./efibootmgr64 -n 0000
from TWRP terminal, then power off and power on, everytime you want to start Lubuntu without starting android first
If you try it, make sure to post if it worked And if it did not, then post what happened and I will try to help you.
If you want to PM me about this, rather make a post here. I will probably reply soon (or someone else may help you
Downloading files, gonna try this now, thanks for the tutorial, and in the future will there be more OS'es?
Ruben Craveiro said:
Downloading files, gonna try this now, thanks for the tutorial, and in the future will there be more OS'es?
Click to expand...
Click to collapse
I'll see if people like this
Is there some OS you would like to see and why?
Mis012 said:
I'll see if people like this
Is there some OS you would like to see and why?
Click to expand...
Click to collapse
winxp, maybe, and also i made a step wrong and it only boots to grub... i have a powered hub, how to fix?
Ruben Craveiro said:
winxp, maybe, and also i made a step wrong and it only boots to grub... i have a powered hub, how to fix?
Click to expand...
Click to collapse
Cannot you just redo the step?
Of course it's important what did you do wrong?
I am pretty sure WinXP - although I already thought of that - cannot be booted in EFI mode. And also even Lubuntu is lagging a bit becouse the sdcard is not fast enough. Puppy linux would be way better also for healthiness, but multiple things didn't work. I think I could boot Lubuntu from iso, but then it wouldn't be permanent :/
Also onboard keyboard works well, but I don't want to upload the rootfs again, hopefully it can be installed without keyboard.
P.S I'm gonna make some pictures of it so everybody can see
Mis012 said:
Cannot you just redo the step?
Of course it's important what did you do wrong?
Click to expand...
Click to collapse
i set grub to boot first and i havent setup ubuntu well so it keeps booting to grub and tries to boot to ubuntu but it cant, is there a command in grub to remake boot entrys?
Ruben Craveiro said:
i set grub to boot first and i havent setup ubuntu well so it keeps booting to grub and tries to boot to ubuntu but it cant, is there a command in grub to remake boot entrys?
Click to expand...
Click to collapse
Although it would be a nice adventure, I refuse to tortue you.
Just spam F2 when you power the tablet on, if you press it while in Aptio Setup Utility just select NO, And in Aptio Setup Utility you will quickly find out what to do.
P:S !!!!!!!!!!!!!!!!!!!!!!!! If you didn't have an Y OTG cable you would be screwed hard..
Mis012 said:
Although it would be a nice adventure, I refuse to tortue you.
Just spam F2 when you power the tablet on, if you press it while in Aptio Setup Utility just select NO, And in Aptio Setup Utility you will quickly find out what to do.
P:S !!!!!!!!!!!!!!!!!!!!!!!! If you didn't have an Y OTG cable you would be screwed hard..
Click to expand...
Click to collapse
xD glad i had one, fixed, ill remake the steps, but they are a bit confusing on step2, and thanks
Ruben Craveiro said:
xD glad i had one, fixed, ill remake the steps, but they are a bit confusing on step2, and thanks
Click to expand...
Click to collapse
You can actually make the esp folder on /data/ESP , too. I will edit it
Mis012 said:
You can actually make the esp folder on /data/ESP , too. I will edit it
Click to expand...
Click to collapse
you made some steps weird because they look like some of them are in the images and some on the page, its confusing, i could get to grub and it said Lubuntu in boot order but it starts loading and goes to black screen whats missing?
Ruben Craveiro said:
you made some steps weird because they look like some of them are in the images and some on the page, its confusing, i could get to grub and it said Lubuntu in boot order but it starts loading and goes to black screen whats missing?
Click to expand...
Click to collapse
You have to power off then power on, not reboot. It's that simple, actually
Mis012 said:
You have to power off then power on, not reboot. It's that simple, actually
Click to expand...
Click to collapse
I know that... My only problem is where do i put the ubuntu OS, and if i need to extract..
Ruben Craveiro said:
I know that... My only problem is where do i put the ubuntu OS, and if i need to extract..
Click to expand...
Click to collapse
You extract it in the root of MicroSD.
Some pictures of it working:
The screen is actually nice-looking, the stripes are from camera (slow shutter?)
Mis012 said:
Some pictures of it working:
The screen is actually nice-looking, the stripes are from camera (slow shutter?)
Click to expand...
Click to collapse
i have a problem, each time i try extracting rootfs it gets stuck at gdebi.png (21%)...
As for an OS, I'd like to see Arch. I want to choose what's on my distribution, instead of going for Lubuntu, so I can make it as light weight as possible. I'm thinking a lightweight window manager like i3wm would do a lot of good.
Sent from my K013 using XDA Labs
jerbear294 said:
As for an OS, I'd like to see Arch. I want to choose what's on my distribution, instead of going for Lubuntu, so I can make it as light weight as possible. I'm thinking a lightweight window manager like i3wm would do a lot of good.
Sent from my K013 using XDA Labs
Click to expand...
Click to collapse
You can get it on flash disk and try it
Ruben Craveiro said:
i have a problem, each time i try extracting rootfs it gets stuck at gdebi.png (21%)...
Click to expand...
Click to collapse
Are you extracting using tar utility on linux?
Does it say anything specific about the problem?
Mis012 said:
Are you extracting using tar utility on linux?
Does it say anything specific about the problem?
Click to expand...
Click to collapse
Ive tried extracting on the tablet, using root browser and ZArchiver they both get stuck at same file
Ruben Craveiro said:
Ive tried extracting on the tablet, using root browser and ZArchiver they both get stuck at same file
Click to expand...
Click to collapse
I'm pretty mad at zArchiver for cutting of the top of every file extracted from iso.. Try using tar in terminal on tablet and see what it does. If you have an Y otg cable you can also do install it from a usb stick, abd then try if your rootfs unpacks well and eventually upload it. This tutorial was meant to be useful for people withrout y otg, too, but if you have one it's not that hard to install it yourself.
Press f2 while booting, choose flash drive , select install, custom mode, just select sdcard as rootfs (no data partition doesn't work) and install. Then grep dmesg for a missing txt file for wifi and use /system/etc/nvram.txt in it's place. Be aware it might rewrite your grub.cfg
Note:
This is not bootanimation, this is the splash screen (the 'Mi' boot logo which is displayed when device is switched ON)
This is for Xiaomi Redmi Note 4 (mido/whatever) Only (Snapdragon Variants)..
(For variants other than mido, please post your splash.img here so that I can check if it can work in your device)
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Xiaomi Redmi Note 4 (Snapdragon) (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
(For devices with latest firmware, use this tool: https://forum.xda-developers.com/showpost.php?p=75231024&postcount=48)
1. Download & Extract this: Redmi_Note_4_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x1920 or lower.
Note:
Redmi Note 4 logo has a fixed size of 100kB allocated for splash image frame buffer, so only very light-weight pictures can be used.
(If you alter this limit in the script, fastboot picture will not appear in fastboot mode..)
It's recommended to use picture with 3 or 2 colors only, like Black & White pictures.
So you'll have to try many pictures till you get a successful one.
3. Now rename your picture as logo.png or logo.jpg according to its format & replace it inside "pics" folder of the extracted folder.
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , which you can find inside the "output" folder after completion.
Note:
You'll get an error like "PICTURE IS LARGE IN SIZE" if it's not possible to create a logo with that picture.
In that case, try any one of these below:
a. Try compressPNG.com to reduce no. of colors in PNG picture.
Upload your picture, click Settings, reduce number of colors to 2, Apply & download it & try again.
b. Reduce the picture resolution.
For example, this picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
can edited to something like this:
(Hope you understand what I say)
c. Try some other picture.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
1. Based on my original tool for Redmi Note 3
2. @Ravi Kumawat who provided the stock splash.img of Redmi Note 4 (mido - Snapdragon) & tested this tool.
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
FOR MEDIATEK VARIANTS:
For MTK devices, you might have a different partition for that called 'logo'.
Browse in /dev directory to find out where that is present.
After you have found out, dump the logo.bin file by:
Code:
dd if=/<the_directory_where_logo_is_present>/logo of=/sdcard/logo.bin
Now you can edit the logo.bin using this tool:
Changing Boot Logo (logo.bin) - LOGO BUILDER Program
After editing, you can reflash it by:
Code:
dd if=/sdcard/logo.bin of=/<the_directory_where_logo_is_present>/logo
If you did this successfully, please share the details of how you did it so that it will be helpful for others..
Or if that tool doesn't work, send me your logo.bin or splash.img, I'll check it..
Thanks @GokuINC for the tool.?
Haha - just like the Moto G - pretty neat. ?
Thank you so much for this tool! I can't seem to flash a particular logo. It automatically flashes a black and white Google logo instead. I've attached the image here. Please look into it.
google splash for redmi note 4 thanks to @GokulNC for tool
Google - https://www.androidfilehost.com/?fid=673368273298958840
Iphone - https://www.androidfilehost.com/?fid=745425885120736058
Thanks buddy! You made my day today!
---------- Post added at 18:09 ---------- Previous post was at 17:40 ----------
getting this error
-------------------------------------------
Creating splash.img ........
Traceback (most recent call last):
File "bin\logo_gen.py", line 291, in <module>
MakeLogoImage(GetPNGFile(), "output.img")
File "bin\logo_gen.py", line 260, in MakeLogoImage
body = GetImageBody(img, SUPPORT_RLE24_COMPRESSIONT)
File "bin\logo_gen.py", line 250, in GetImageBody
return encodeRLE24(background)
File "bin\logo_gen.py", line 217, in encodeRLE24
assert bytesProcessedInBody <= payloadLimit, "\n\n\nPICTURE IS LARGE IN SIZE..\nQuitting..."
AssertionError:
PICTURE IS LARGE IN SIZE..
Quitting...
PICTURE IS LARGE IN SIZE
Quitting
Press any key to continue . . .
---------- Post added at 18:19 ---------- Previous post was at 18:09 ----------
get img file as output. how to flash in twrp recovery
---------- Post added at 18:39 ---------- Previous post was at 18:19 ----------
Problem Solved
to reduce the picture size you may use half pixel eg (1080*1920)/2,3 etc
GokulNC said:
Note:
This is not bootanimation, this is the splash screen (the 'Mi' boot logo which is displayed when device is switched ON)
This is for Xiaomi Redmi Note 4 (mido/whatever) Only (Snapdragon Variants)..
(For variants other than mido, please post your splash.img here so that I can check if it can work in your device)
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Xiaomi Redmi Note 4 (Snapdragon) (any ROM)
2. Optional:Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this: Redmi_Note_4_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x1920 or lower.
Note:
Redmi Note 4 logo has a fixed size of 100kB allocated for splash image frame buffer, so only very light-weight pictures can be used.
(If you alter this limit in the script, fastboot picture will not appear in fastboot mode..)
It's recommended to use picture with 3 or 2 colors only, like Black & White pictures.
So you'll have to try many pictures till you get a successful one.
3. Now rename your picture as logo.png or logo.jpg according to its format & replace it inside "pics" folder of the extracted folder.
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , which you can find inside the "output" folder after completion.
Note:
You'll get an error like "PICTURE IS LARGE IN SIZE" if it's not possible to create a logo with that picture.
In that case, try any one of these below:
a. Try compressPNG.com to reduce no. of colors in PNG picture.
Upload your picture, click Settings, reduce number of colors to 2, Apply & download it & try again.
b. Reduce the picture resolution.
For example, this picture: can edited to something like this:
(Hope you understand what I say)
c. Try some other picture.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
c. To flash from Fastboot mode:
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
1. Based on my original tool for Redmi Note 3
2. @Ravi Kumawat who provided the stock splash.img of Redmi Note 4 (mido - Snapdragon) & tested this tool.
Hit the Thanks:good: button if it worked for you
You're welcome to post the splash images that you created..
FOR MEDIATEK VARIANTS:
For MTK devices, you might have a different partition for that called 'logo'.
Browse in /dev directory to find out where that is present.
After you have found out, dump the logo.bin file by:
Now you can edit the logo.bin using this tool:
Changing Boot Logo (logo.bin) - LOGO BUILDER Program
After editing, you can reflash it by:
If you did this successfully, please share the details of how you did it so that it will be helpful for others..
Or if that tool doesn't work, send me your logo.bin or splash.img, I'll check it..
Click to expand...
Click to collapse
I used 46KB pic of size 354x354 all blackandwhite, still large pic size error
yashgumaste said:
I used 46KB pic of size 354x354 all blackandwhite, still large pic size error
Click to expand...
Click to collapse
compress to 3 kb
rameshurfrnd1 said:
google splash for redmi note 4 thanks to @GokulNC for tool
Google - https://www.androidfilehost.com/?fid=673368273298958840
Iphone - https://www.androidfilehost.com/?fid=745425885120736058
Click to expand...
Click to collapse
It's funny because the only images that worked are the ones you posted here as .zip files. I tried numerous 1080x1920 jpgs, tried compressing and resizing them to 720x1280 etc. etc, even tried compressing a .png file all were black and white and sized lower than 100kb and nothing worked, it phone always used a stock Google logo.
Deleted
naren12 said:
Hey it works. I'm not using that google logo. I modified it and it works for me. I'm free all the time. If u want some i can create one for u. Just post the image. I will do for u
Click to expand...
Click to collapse
http://i65.tinypic.com/28mpwxw.jpg
Can you please try converting this one to a zip?
menskiz0r said:
http://i65.tinypic.com/28mpwxw.jpg
Can you please try converting this one to a zip?
Click to expand...
Click to collapse
Yes.
naren12 said:
Yes.
Click to expand...
Click to collapse
Thanks, it worked. But it's not stretched for a full screen. Is it compressed to a very small size?
menskiz0r said:
Thanks, it worked. But it's not stretched for a full screen. Is it compressed to a very small size?
Click to expand...
Click to collapse
I don't know. But is of lower resolution. I will try to make another one with 1900x1080 resolution. Is it ok for u if the background color was black?
naren12 said:
I don't know. But is of lower resolution. I will try to make another one with 1900x1080 resolution. Is it ok for u if the background color was black?
Click to expand...
Click to collapse
yeah sure
menskiz0r said:
yeah sure
Click to expand...
Click to collapse
Try this
a Bug found though ;_;
http://imgur.com/tJzjUh6.png
ps: fixed
thamk man, but i have a problem here, ive tried many file but cannot change, still linux logo, any way to fix i? thanks
erwanPutra said:
thamk man, but i have a problem here, ive tried many file but cannot change, still linux logo, any way to fix i? thanks
Click to expand...
Click to collapse
Can u explain in detail?
thankyou so much