I finally changed the boot logo in my phone. By keeping permissions the same and not extracting the the whole param file... and root because i am lazy.
Take the .zip from the end of the file name and paste the poison simply as PARAM and reboot and enjoy your new green logo. Of course back up original.
Permissions should not be an issue and i attached a screen of the file info i took prior to editing it.
I forgot to say what i used to change the logo.jpg
Linux and xarchiver utility. Extracted and replaced with my image and set permissions. Checked to make sure file size was similar and proper resolution and that's it. Hope to figure a way to flash it soon so i can wreck stuff faster.
Ah... probably should mention to do this NOT on stock ROM or at all. The more i read on it the more stupid it is to mess with this area unless you know what you're doing. I'll leave it up but don't think anyone should try it.
Ok! I hope this is useful because i've been able to change the initial image with perhaps a MUCH safer way.
Using Linux, i installed Heimdall.
I extracted stock ROM within Linux and used Ark to extract what the Mint archive wouldn't.
Already i had prepared my 2220x1080 jpg to 75 kb and simply deleted logo.jpg within param.bin while viewing with Xarchiver. I did not extract the param.bin file. Then i added my logo.jpg and closed up Xarchiver. The new logo.jpg was also set to r--r--r-- before insertion.
Then, with phone plugged in while in download mode (usb enabled prior in dev options and tested of course)... opened up the terminal from the folder containing param.bin and typed:
sudo su
Heimdall flash --PARAM (dragged param.bin into terminal window and hit enter)
Device booted with new image and then into twrp. I figured a cache wipe was needed so i did that and all was good. Would like to know if this is a horrible idea. Just using rooted stock ROM with twrp.
I posted the image... but of course my phone didn't change anything at the bottom. No way.
Does the image need to be the same file size i have tried making my own logo but it does not really work
Related
I'm noticing that changes I make to /system/bin get undone upon reboot on stock 5589 software.
My particular change is the wpa_supplicant ad hoc fix.
I used terminal to rename the old file to wpa_supplicant.back and put my new file in.
It works fine, I can connect to ad-hoc wifi fine, until I reboot. After reboot, the backup is gone, and the old file is back to it's original spot (breaking wifi).
I'm using temporary root under z4root if that makes a difference.
Anyone have any ideas, is there some type of "system restore" functionality in 5589 that refreshes system/bin upon startup?
Any workarounds if I want to remain on stock?
ml_boston said:
I used terminal to rename the old file to wpa_supplicant.back and put my new file in.
Click to expand...
Click to collapse
You shouldn't replace binaries while they're being used. Install CWM and use it to do the switch. Make sure you remount /system read-only afterwards.
The file wasn't in use, as I was able to run adhoc wifi (meaning the replace worked) until I rebooted.
I think I found the problem, from this link:
There is also another important file you should know about. In /system/recovery.img there is a full copy of everything that is loaded on mtd1. This file is automatically flashed onto mtd1 every time you shut down. That means two things: 1. Any changes you make directly to /dev/mtd/mtd1 get blown away on reboot and 2. If you want to change /dev/mtd/mtd1 you're probably better off just sticking the image in /system/recovery.img and rebooting. When creating your own custom update.zip files (especially when adapting the stock images), you can get tripped up if you forget to replace /system/recovery.img and it ends up overwriting /dev/mtd/mtd1 unbeknownst to you. Watch out.
Click to expand...
Click to collapse
So I've got to learn how to build an img file with my one swapped file. Or perhaps (will try soon and post back), deleting the recovery.img file will also do the job.
ml_boston said:
The file wasn't in use, as I was able to run adhoc wifi (meaning the replace worked) until I rebooted.
Click to expand...
Click to collapse
Unless the wifi was switched off or put into airplane mode or something like that as the default state, I assure you that the wpa_supplicant binary would've been in use. It's how modern Unixes work.
I think I found the problem, from this link:
Click to expand...
Click to collapse
Most of the specific details in that link a) either isn't relevant to your specific problem and/or b) does not apply to the gTab and the ROMs that run on it. For example, in the quote you pulled:
There is also another important file you should know about. In /system/recovery.img there is a full copy of everything that is loaded on mtd1. This file is automatically flashed onto mtd1 every time you shut down. That means two things: 1. Any changes you make directly to /dev/mtd/mtd1 get blown away on reboot and 2. If you want to change /dev/mtd/mtd1 you're probably better off just sticking the image in /system/recovery.img and rebooting. When creating your own custom update.zip files (especially when adapting the stock images), you can get tripped up if you forget to replace /system/recovery.img and it ends up overwriting /dev/mtd/mtd1 unbeknownst to you. Watch out.
Click to expand...
Click to collapse
Here,
1. There is no /system/recovery.img file on the stock ROM.
2. The quote talks about restoring "recovery"--not "system". Plus, those 2 partitions have radically different sizes (16 MB max for "recovery" and 200MB max for stock "system"). Think about what would happen to the boot times if a 200MB image had to be restored on every boot.
So, my advice is unchanged. Install CWM temporarily, then use it to switch the binary, and finally, sync and unmount /system before rebooting out of CWM. You can always restore the stock recovery using the recovery.img file in the 5699 update zip file from within CWM.
I LOVE THE SMELL OF FLASHED SPLASH SCREENS IN THE MORNING! IT SMELLS LIKE VICTORY!
Okay, I have finally figured out how to make custom splash screens for viewpad 7 and flash them into it (finally got rid of those birds, lol)
Unfortunately, I did not figure out how to dump the old screen (for some reason, flash_image dumps a 100% black image, but at least of correct size) but it's not hard to reproduce if worst comes to worst (aka warranty lol)
However, the new screen is flashed okay.
I'll describe the process of converting any vanilla image file to a viewpad-friendly splash screen (or, rather for that matter, any device-friendly, as long as you can dump the splash/splash1/whatev. partition at least as "black" file in order to get the exact correct size ) and feeding it to the device later, in next post. Now need some sleep lol.
Okay, so, quick instructions for reflashing viewpad image
First, get the flash_image program (see attachment flash_image.zip below, or mirror)
load it up to your sdcard.
Fire up ADB shell in cmd prompt. To do so, do cmd from "run..." in windows start menu, navigate via cd to wherever adb is for you, like for instance
Code:
cd c:\Program Files\Switcher\FM6F_4027\
then do
Code:
adb shell
then do
Code:
su
then do
Code:
cp /sdcard/flash_image /system/bin
then finally
Code:
chmod 755 /system/bin/flash_image
okay, that should get your ready to dump a (lame approximation of) original splash image dump.
To carry that out, first type
Code:
cat /proc/mtd
to find out what partitions are out there (the splash one will have "splash" in its name, duh). Note that viewsonic has the splash partition name being simply splash and not splash1 as most devices have.
On my device, the splash was mtd2
Now, let's try to back up the original splash.
Code:
cat /dev/mtd/mtd2 > /sdcard/splashbackup.img
Okay, here stuff goes weird for me because the file ends up all black (why oh why) but to hell with that, I only need it not to mess up image size.
Okay, now shut down the device and get the file splashbackup.img to your PC.
Rename it to say splashbackup.rgb565 (yes, change the extension)
Now, install Paint.NET and this plugin (both included in my mod pack btw)
Open the splashbackup.rgb565 with paint.net and likely the suggested dimensions will be the ones you want (might not be so for other devices, so take care. But don't worry - you can't kill the device by flashing a FUBAR splash image, so experiment bravely!)
Now, use paint.net to open a desired image in a "vanilla" format that you have likely cooked up in Photoshop or downloaded from the web. Copy its contents to splashbackup.rgb565 and save the stuff as SPLASH.rgb565
You're almost there.
Now, download the zombiegoaste mod of glorious splash screen creator (VibrantOwnr thx!) and rename your desired SPLASH.rgb565 to SPLASH.IMG
Put SPLASH.IMG to "Results" folder of the modified SSC
Now, run Run This Program.CMD and it should guide you through the rest.
GOOD LUCK!
P.S.:
However, bear in mind that devices treat orientation...weirdly it seems, so get ready to manipulate the original image in the program of your choice to rotate stuff (rotate sucks in paint.net) and then redo the steps above that deal with turning a vanilla image into a SPLASH.rgb565
P.P.S.:
All files attached to post and uploaded to a file sharing service, just in case.
Hope this helps folks to easily make and flash custom splash images
Thank you for share, but Im think Im will try hardly to do every way to see splash screen just one or maybe two time in a mounth.
Sent from my ViewPad7 using xda premium
Thanks for posting.. Mac + Photoshop?
Im using a mac and have photoshop. Is there a way to open the rgb565 file in photoshop as I cannot use paint.net? I know that I can save any image I create as a rgb565 file using photoshop but I just cant open one... Perhaps you can give me the dimensions of the image you open up in paint.net to see if that works?
Well, as the title sugests, I've tried to root my phone (Samsung Galaxy J1 SM-J100MU) and failed. Since no twrp or any other custom recovery is made for my specific model, I tried the method that involves mounting the android systems and modifying the famous build.prop, or putting su binaries inside the /system folder.
I ran an unpack script from ubuntu to decompress the boot file, and simg2img to be able to mount /system following some guides I've found, and made use of mkbootimg to repack it and flash it.
The thing is that the phone won't boot because the modified boot image size differs from the original. The system also differs but Odin won't even flash it and I'll have to reflash the stock rom.
Any ideas about what it can happen? I get no apparently errors during the process of unpacking/repacking the images so I don't know. The only thing I can think of is that the unpack script says something like "There's an extra file in ramdisk; though this file can exist, the script is not made for this type of ramdisk", so I edited the script in order to skip this warning, and everything else went well. The bootimg got unpacked and then the ramdisk and then I modified default.prop.
Well, that's it, I hope you can understand and give me some help in order to proceed.
Thank you in advance.
I need help editing the default.prop of my rooted boot.img for an LG LM-X210ULM K8+. I want to mark ro.debuggable off as 1 instead of 0 but which i have no problem doing but when i use any kitchen program it puts it back together as 15mb instead of 32mb and when i flash it to my device it always bootloops.
If any one could help i would appreciate it. Im including a copy of the rooted boot.img freshly pulled ftom my device
The size probably isn't the issue. Using AIK the size was even bigger than the original.
It's all just 0x00 the rest of that partition...
By using my old uImage/_recovery unpack-repack batch file
http://cxzstuff.blogspot.com/2013/03/uimagerecovery-unpack-repack-batch-file.html
the result was smaller but still a bit bigger than the Magisk had made.
But that is irrelevant really... result attached.
Yea i dont get it. The size doesnt matter as long as it diesnt exceed the max amount of space the partition can hold. But why does changing one value cause the boot.img to boot loop after flashing.
Even the boot.img you made looped after flashing
Duhjoker said:
Even the boot.img you made looped after flashing
Click to expand...
Click to collapse
Just tells that it's not the tool used. Or mine oldie is as bad/good as the newer one in this case.
What that Magisk img had was like it had some signature but it should not be needed and probably just garbage left there from the stock...
Should not matter, but how about doing it other way around? Modify the stock boot first and then give it to Magisk for rooting.
I think it was stock. Ill have to make sure though. wonder why magisk doesnt make the image debuggable to begin with. But your right it might be that im using a magisk patched image. Ive got some firmware already broke down ill give it another try here in a bit and post my results.
Duhjoker said:
I think it was stock. Ill have to make sure though. wonder why magisk doesnt make the image debuggable to begin with. But your right it might be that im using a magisk patched image. Ive got some firmware already broke down ill give it another try here in a bit and post my results.
Click to expand...
Click to collapse
So here we are. There should be some shortcut or something left to the original sub forum at least for a week or two when you boys move these threads - dammit...
Any luck? You have a customized recovery? How about these?
https://forum.xda-developers.com/an...g/mod-bootimage-adb-unsecure-patcher-t3618558
Yes luck tonight i did a fresh reflashing on my QC Lg k8+ and decided to break open the boot.bin from the kdz i used and made my changes to default.prop then i put the renamed to boot.img on my phone and let magisk patch it then flashed it via fastboot and dared it to go into system. Then i double dared it. Then for safe measure i double dog dared it to boot into system to which it had no choice but to go along with the or be labled a @!%\**__(€.
It booted.
So the lesson learned is to patch a fresh boot.img with your default.prop changes then have magisk patch it for root.
Now oddly when i patched and tweaked my recovery using carlive kitchen, i also made sure that the same changes to default.prop or rather i made sure they had been made and they had. But any terminal like emulator or termux pulls up the props using getprop with the changes unmade and i still cannot change the values of the system build.prop and when i patch it manually it reverts on reboot.
I literally have to open a vi in twrp to make changes. And forget about copying my own patched build.prop to system in twrp. Because that leads to boot loop as well
Ok so is there a reason that you dont make those changes in the boot.img any more? Because the past two days i have woke up to no root. I have had to reflash my boot.img both times
Ok i just compiled my first kernel from lg source code and now i dont know which of the split images in my folder is the zimage
Back to the drawing board quite literally. Im stuck for sure.
I need to make edits to a few files like init.rc and init.lge.power.rc to allow for changes in my newly compiled kernels. Basically im adding a couple properties and some cpu frequency stuff. Plus i want to make it back to adoptable storage and add a second sd partition for ext4 projects im working that would work best right off the root file system.
Im using the stock extracted boot.img from a kdz using salt and carliv kitchen to unpack and repack i have also mkbootimg tools that i compiled myself and some static arm version.
I extracted the ramdisk place my new kernel image in and repack with the init files changed and flash using recovery or fastboot and bootloop every time. And magisk isnt signing with the verity key.
ok i dont know whst was going on the other day but i can split boot.img again and make changes with out looping.
i used gparted on my linux machine to partition my 128gb sd card with 3/4 vfat and 1/4 ext4 i know that by using adb it will automount but thats one timr and i may need to switch out every now and then plus it put a center part in it of about 15mb. with gparted i get the two parts with no bs. any way i created a script that mounts the second part and even symlinks some stuff. it works good but im having trouble getting init.rc to run it.
on early-init
chmod 0755 /system/etc/init/init.mntsd.sh
exec system system /system/bin/sh /system/etc/init.mntsd.sh
any tips
Hi
I have spent hours trying to fix a problem on my Android TV box and I have gotten nowhere.
The issue is that generic.kl reset to 0 bytes and now whatever I do, I cannot edit the file.
I have set it to read-write 777 and all sorts of combinations. I have set the partition to read-write mounted.
I have used a root explorer to copy and paste a working version of the file over the top, it does not give an error and the file is there, again it is empty at 0 bytes.
I have tried to run a text editor itself as root but SuperSU will not run - saying the SU Binary is occupied. I did a factory reset and the issue is still there. There is no way to do a full flash reset on this model.
No matter what I do, I cannot seem to actually edit or replace this generic.kl file
Any ideas or suggestions?
Cheers
is it a system partition file ? probably the only way for now would be to modify the file before creating a system image for you to flash. I'm not even sure that's a doable thing actually.
no recovery is a PITA
Yeah, the file is in the System partition in the USR folder.
Do you think there is no way to fix this then? I.e. I can never use a physical keyboard with this unit again as the file controls the key mapping..
Scott
devices that start out with android 10 have a read only system partition. if you have the know-how magisk can still create overlays of system files, you'd need to write a module or get one requested from someone.
@Electron2k it might be worth talking to the dev or asking in this thread
https://forum.xda-developers.com/apps/magisk/module-1controller-1-module-to-support-t3865889
if you've created your new file already maybe there's a way to incorporate it into this module to do what you want. I'm not saying they'll change the module for you, but he or she might help to do it yourself.
Hi there, if you can track down the firmware for your box get the img file and extract it.
Locate the generic.kl file from the extracted rom and copy it over using a file manager, remove the null generic file and reboot your device. All should be working then.
##edit ## just noticed you've already tried replacing the file with a filemanager sorry
Electron2k said:
Yeah, the file is in the System partition in the USR folder.
Do you think there is no way to fix this then? I.e. I can never use a physical keyboard with this unit again as the file controls the key mapping..
Scott
Click to expand...
Click to collapse
Pls send the module or the solution if you have it