[Q] Help to restore .LFS Folder of parameters - Galaxy S III Mini Q&A, Help & Troubleshooting

Hello i'm new on this and I tried to customize the boot image when the phone is turning on but I failed and it shows a corrupted image, a pretty ugly one, and with my sole knowledgement I can't figure out how to repair it, I tried to put back again the original file " logo_latin.jpg " and it doesn't work each time i try to erase a file, it launches an error, an if I paste a file, the folder appears empty until the next boot and ther new file is undeleteable. I hope i could explain myself, this is my last resort, because a researched in other sites and there is no helpful info.
regards
device: GT-I8190L - Golden - Cyanogenmod 11

Related

Instructions to create and load EVO splash screen

I know there are other methods out there for achieving the same thing. And I have touched on a few "after thoughts" in the actual process of loading the image to the phone. If these can be confirmed, please feel free to update these instructions. After browsing many, many pages in forum after forum I was unsuccessful in finding anything detailed enough from start to finish. So I decided to write this up!
These instructions work for anyone who rooted using the "UnrEVOked" method such as that given at HTCEvoHacks.com. I have not tested these instructions with any other root method out there.
With a bit of practice, this method can be mastered and done in about 20 minutes (depending on how long you spend creating your splash image in PhotoShop)
For the sake of these instructions, all references and instructions dealing with PhotoShop are assuming you are using PhotoShop CS5. Commands may be slightly different on older versions of PhotoShop, so it may take a few extra clicks to find what you're looking for.
1. You can download custom boot images from the web, or create your own in PhotoShop using ANY sort of photo, graphics, text, or combination. You MUST make sure that the image size is set as the same for the EVO's screen resolution (480x800). For this reason, I would double check any image file you try to use prior to converting it for use with your phone.
2. Open your image file in Photoshop and make whatever tweaks or enhancements you like. Remember to "flatten" the image prior to saving it out if you have multiple layers in your file. You can use the next step to re-size the image first if you like, but depending on your current settings in PS it should not matter.
3. Right click the file window (the one that contains your image) and set the "Image Size" settings to a width of 480, and the height to 800. These measurements MUST be in pixels as well. If you have the "Constrain Proportions" box checked, you may not be able to tweak these individually without affecting the other. So uncheck that box and change the size settings. Click ok to close the box and the image will re-size within Photoshop.
4. After you have finished creating your custom image, flattening the image, and resizing it to fit on your phone's screen, it is time to save the file. Navigate to the "file" menu and click "save as". Here, you can choose where to save it, name it, and choose the file format. It's probably easier to go ahead and save it as "splash" now, so that you wont have to rename it later. Either way, this file MUST be named "splash" when we are in the final stages. Save it as the "BMP" format, and you will get a pop-up window for the BMP options. "File Format" should be set to Windows... and choose the depth option of 24 Bit. The "compress" and "Flip row order" boxes should be unchecked, and you do not need to go into any advanced settings. Once you have saved the file, You can close PhotoShop.
Now the File needs to be converted from the BMP format into an IMG file. This is so that the boot loader in your phone will see it when you flash it to your phone.
There are a few conversion tools out there, but I have found Splash Screen Creator to be the EASIEST way to convert the file with a few clicks.
The link to download this small program is here... http://www.addictivetips.com/?attachment_id=43073 ... and it is FREE!!! (I did not create this program)
1. Download the .zip package from the link above.
2. Extract the files. I found that creating a folder on my desktop to secure these files (and these files only) to be less of a headache.
3. After you have extracted the files, you are ready to convert your "splash.bmp" file. You MUST move this file into the same directory that you unzipped the Splash Screen Creator to. It will only find the bmp file in the same directory, which is why having its own folder is easier. Move your "splash.bmp" file to the same folder and open "RUN THIS ONE". This will open the program in a command prompt.
4. Choose option 1 to convert your existing .bmp file into the required .img file. The next option will ask if you would like to flash the file to your phone. This option is not necessary for these instructions, but I have read of others being successful. You can try this option, but if it fails, go on to the remaining steps.
5. Go ahead and close the program by pressing another key to exit. You should see your new "Splash.img" file in this same directory. Rename this as "splash1.img"
Now that I think of it, naming the BMP file to "splash1" prior to converting to the .img format may solve the error when trying to flash the file to the phone
within Splash Screen Creator. The img file MUST be name "splash1" prior to updating it in the boot loader in the next steps so it makes sense that the program would come up with an error at this point. I have not tested this theory at this time, but you are welcome to. If someone does test this, please update these instructions
to save from many unnecessary steps below!
Your next steps require access to your original "PC36IMG.zip" file that you used during your root process. If you do not have your original "PC36IMG.zip" file, you
can try to download one here... http://forum.xda-developers.com/showpost.php?p=8913849&postcount=156 ... I have not tested this file yet, but worth a shot if you dont have it.
1. Make a COPY of your "PC36IMG.zip" file and move it to your directory where you have worked with the custom splash files. This saves from getting confused between files and flashing the wrong one to your phone. You're also making a copy so that your original "PC36IMG.zip" file is NOT altered.
2. DO NOT unzip the file! Simply drag your "splash1.img" file over to your zipped "PC36IMG.zip" folder and copy it in there. If you get a prompt to overwrite an existing "splash" file, go ahead. Afterall, you are working with a copy of the PC36IMG.zip.
3. After you have added the "splash1.img" file into the "PC36IMG.zip" folder, you can now move the zipped folder over to your sd card. Make sure that it is the ONLY copy on your sd card, and that you have not placed it in any other directories. BOOT LOADER WILL NOT FIND IT IF IT IS IN ANOTHER FOLDER!!!
4. AT THIS POINT YOU WANT TO BE SURE YOU HAVE BACKED UP YOUR ROM!!!! YOU WILL LOSE YOUR CURRENT ROM AND DATA AFTER THE NEXT STEP!!!!
5. Reboot the phone into Boot loader by holding the volume down button and pressing power. The boot loader will find your "PC36IMG.zip" and ask you if you want to update. Press the volume up button to say YES! Grab a coffee, chug a beer, or take a piss, cause this step takes a few minutes.
6. Once the boot loader has finished it's update, reboot your phone. it will now display your new custom splash screen!!! (but you're not done yet)
Because you updated your "PC36IMG.zip" files in the boot loader, you have in effect re-flashed the stock rom (rooted of course) back to your phone.
Allow a few minutes for your phone to boot up, log into your g-mail account (so that you have access to the market), and download Rom Manager (or your favorite backup manager), and restore back to your rom!
Like I said before, I have only done this on the HTC EVO that has been rooted using UnrEVOked through the process explained on HTCEVOHacks.com. I have no idea if this process will work with other configurations, and I accept no responsibility for the outcome of your actions!!!!
cool bro thanks
Thanks very helpful

[Q] Upgraded to "Overcome - Gingerbread", /efs folder empty

Hi guys,
Looking for helps here.
First I want to thank the guy created the "Overcome for Gingerbread", it comes w/ a great details instruction and I successfully upgraded.
My tab was original from Bell Canada, the phone feature was locked. I was able to unlock it by modifying the nv_data.bin file...
But now after I upgraded to Gingerbread, my phone feature is disabled again so I suppose I should do the whole unlock process again. However when I looked for the nv_data.bin file, the directory /efs is empty?!?!?!. Can someone help me here?
Thanks,
Edit: I found a nv_data.bin file on my laptop (not sure if it's the orginial one), trying to copy it to the /efs folder on the tablet, but I got error "not enough space"...
What program u using to copy with. Put that file on the SD card first from your PC.
Then get EF File Explorer rooted, and copy that from the SD card to the /efs directory
The nv_data.bin edit unlocks the tablet to allow use on other carriers like rogers, fido etc.
It does not provide phone usage, you need to flash a european rom to enable the phone,
then you need to flash a suitable modem to allow 3G data and phone, then edit your apn info.
Are you sure efs is empty, maybe your no longer rooted and can't see it?
You get the not enough space error because you have most probably renamed the original file and are trying to copy the new one in the directory. Delete the file and also the.md5 correspondent (it will be recreated on reboot.
P
Thanks for all the replies guys, but my problem is still there.
@Sonictab: I'm rooted and I'm sure that my /efs folder is empty.
@StarLog: I'm using Super Manager to copy the file
Now I can't even download files from the browser nor using the market place to download any apps. Something went wrong and I'm not sure what. Should I downgrade?

[Q] How can I remove Vodafone Logo

Hi all,
Firtstly, I´m sorry for my english language.
I would like your help to identify the file of phone operator logo and remove it.
I tested the following paths without results:
/System/media
/cust/preinstalled/public/media
How could I remove it?, perhaps would be as simple as delete the file of logo... but I can not find nor identify this file. ( I have looked for wiith Root Browser and ES File Explorer rooted)
My problem is that I would like to remove the annoying phone operator logo ( is not a animation, is only a fixed image, a picture that last about 15 seconds) always when I start the phone I can see the phone operator logo and after the bootanimation.zip of Huawei, but the bootanimation of Huawei is not a problem to me.
Could be encrypted the file or picture of Vodafone logo?
I hope your help and ideas to identify this image or logo.
My cellular is a Huawei Ascend P7 L10 with vesion B120 from Vodafone operator, I have changed to B133 and B136 too,
Regards,
If You are planning to change ROM why You want to remove logo ?
In new ROM won't this logo.
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Xancarl said:
Hi all,
Firtstly, I´m sorry for my english language.
I would like your help to identify the file of phone operator logo and remove it.
I tested the following paths without results:
/System/media
/cust/preinstalled/public/media
How could I remove it?, perhaps would be as simple as delete the file of logo... but I can not find nor identify this file. ( I have looked for wiith Root Browser and ES File Explorer rooted)
My problem is that I would like to remove the annoying phone operator logo ( is not a animation, is only a fixed image, a picture that last about 15 seconds) always when I start the phone I can see the phone operator logo and after the bootanimation.zip of Huawei, but the bootanimation of Huawei is not a problem to me.
Could be encrypted the file or picture of Vodafone logo?
I hope your help and ideas to identify this image or logo.
My cellular is a Huawei Ascend P7 L10 with vesion B120 from Vodafone operator, I have changed to B133 and B136 too,
Regards,
Click to expand...
Click to collapse
This Logo is only in provider branded firmwares.
Ziółek said:
If You are planning to change ROM why You want to remove logo ?
In new ROM won't this logo.
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Click to expand...
Click to collapse
I'm sorry, the idea is go on with the same firmwire, B136
Xancarl said:
I'm sorry, the idea is go on with the same firmwire, B166
Click to expand...
Click to collapse
I think you may be stuck with the logo. Changing ROMs doesn't have any effect in my experience. I have a P7-L07 unlocked and unbranded phone. When I turn it on I get an image with the letters "4G" and a few coloured arcs which appears for a few seconds before the boot animation starts. Does this sound familiar? I would love to replace this image but am unable to.
I can tell you that file "oemlogo.mbn" is an image file encoded in the rgb565 format. Changing this file has no effect.
I can't find an image file of any sort in the kernel or in the boot image. So I suspect the image is stored in one of the phones partitions. I've looked but without success so I could be wrong here. Perhaps others may have some thoughts on this issue.
arthios said:
I think you may be stuck with the logo. Changing ROMs doesn't have any effect in my experience. I have a P7-L07 unlocked and unbranded phone. When I turn it on I get an image with the letters "4G" and a few coloured arcs which appears for a few seconds before the boot animation starts. Does this sound familiar? I would love to replace this image but am unable to.
I can tell you that file "oemlogo.mbn" is an image file encoded in the rgb565 format. Changing this file has no effect.
I can't find an image file of any sort in the kernel or in the boot image. So I suspect the image is stored in one of the phones partitions. I've looked but without success so I could be wrong here. Perhaps others may have some thoughts on this issue.
Click to expand...
Click to collapse
If you make a force update the Logo is away. The path oft the picture i dont know. Sry
Follow this path:
First-system/media delete everything except audio folder
Second-cust/ and than go in each folder one by one and everywhere where is "media" folder go inside and delete everything inside "media" folder.When you process all folders reboot your phone and ugly 4G bootlogo will be gone.
gregysk said:
Follow this path:
First-system/media delete everything except audio folder
Second-cust/ and than go in each folder one by one and everywhere where is "media" folder go inside and delete everything inside "media" folder.When you process all folders reboot your phone and ugly 4G bootlogo will be gone.
Click to expand...
Click to collapse
Not work, Vodafone logo appears. Then "android", no bootanimation of huawei, but Vodafone is still here!!!! aaaaarrrggggghhhhhhh
gregysk said:
Follow this path:
First-system/media delete everything except audio folder
Second-cust/ and than go in each folder one by one and everywhere where is "media" folder go inside and delete everything inside "media" folder.When you process all folders reboot your phone and ugly 4G bootlogo will be gone.
Click to expand...
Click to collapse
teto78 said:
Not work, Vodafone logo appears. Then "android", no bootanimation of huawei, but Vodafone is still here!!!! aaaaarrrggggghhhhhhh
Click to expand...
Click to collapse
Ahh yes. Same for me too. Ugly 4G LTE logo persists. It's even there when I boot into TWRP recovery. There is a partition on the phone called "oeminfo". It's about 33Mb in size and contains data. I suspect this is where the opening logo is. I'll investigate further as it would be nice to replace the image with something else. All suggestions are welcome.
arthios said:
Ahh yes. Same for me too. Ugly 4G LTE logo persists. It's even there when I boot into TWRP recovery. There is a partition on the phone called "oeminfo". It's about 33Mb in size and contains data. I suspect this is where the opening logo is. I'll investigate further as it would be nice to replace the image with something else. All suggestions are welcome.
Click to expand...
Click to collapse
How can I access that partition? I think is a good idea to investigate.
arthios said:
Ahh yes. Same for me too. Ugly 4G LTE logo persists. It's even there when I boot into TWRP recovery. There is a partition on the phone called "oeminfo". It's about 33Mb in size and contains data. I suspect this is where the opening logo is. I'll investigate further as it would be nice to replace the image with something else. All suggestions are welcome.
Click to expand...
Click to collapse
How can you access that partition? I think is a good idea to investigate.
Mount it in twrp and use twrp file Explorer (advanced options)
Progress so far is of little value. The partition certainly contains an image file. It also contains something else. Possibly a binary to display the image briefly. I'll keep working on it. Out of interest however, do people have a file called "load_oemlogo" in their /system/bin folder? I don't but it's referenced in the init.rc file which is executed on startup.
Xancarl said:
How can you access that partition? I think is a good idea to investigate.
Click to expand...
Click to collapse
Your phone needs to be rooted and you need busybox and terminal installed.
In the terminal:
Code:
su
dd if=/dev/block/mmcblk0p9 of=/storage/sdcard1/oeminfo
exit
exit
It takes a while so be patient. Note that the above assumes you have an sd card installed. The "0" in mmcblk0p9 is a zero.
Then you have a large file you can play with.
Altering the oeminfo partition seems to be impossible. The device won't allow the partition to be erased nor is it possible to flash data into the partition. I tried flashing the data I had extracted previously but failed. It seems we are stuck with the splash screen. Most disappointing.
http://forum.xda-developers.com/ascend-p7/general/unlock-bootloader-huawei-ascend-p7-l10-t2830641
AFAIK this will [edit] NOT[/edit] unlock your bootloader [edit] but will[/edit] remove the branding junk.
arthios said:
Altering the oeminfo partition seems to be impossible. The device won't allow the partition to be erased nor is it possible to flash data into the partition. I tried flashing the data I had extracted previously but failed. It seems we are stuck with the splash screen. Most disappointing.
Click to expand...
Click to collapse
I've made a small simple console utility for my P6S to insert logo into oeminfo or extract it from. I think it's gonna work for P7 and other Huawei devices too.
First, you have to copy partition from your device to PC via ADB (root required):
Code:
adb shell su -c "dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo"
adb pull /sdcard/oeminfo oeminfo
Check paths, they may differ in your device.
After you get oeminfo partition to your PC, insert logo in it with my utility. First parameter is your oeminfo partition, second parameter is oemlogo.mbn file or bitmap file with color depth not less than 16 bit, supported color schemes: RGB555, RGB565, RGB888, RGB8888. Bitmap resolution must match your device resolution.
Examples:
Code:
OEM_logo.exe oeminfo logo.bmp
OEM_logo.exe oeminfo oemlogo.mbn
Also, you can extract logo from oemlogo.mbn or your actual logo from oeminfo into bitmap file by adding second parameter "-e". In this case third parameter is destination bitmap file.
Examples:
Code:
OEM_logo.exe oeminfo -e logo.bmp
OEM_logo.exe oemlogo.mbn -e logo.bmp
After altering oeminfo, put it back in your device:
Code:
adb push oeminfo /sdcard/oeminfo
adb shell su -c "dd if=/sdcard/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
adb shell "rm -f /sdcard/oeminfo"
Also correct to your existing paths here.
Reboot and check result.
Download: View attachment OEM_logo_1.3.1.rar
Thanks for your efforts. It looks promising. In the process of downgrading from EMUI3.0 to EMUI2.3 I managed to trash my phone completely. I've ordered a replacement. When it arrives I'll try this.
like OP I am also trying to replace ascend p7 boot logo (vodafone)
OEM_logo.exe outputs a messed up bmp with sort of an sliding block puzzle effect.
Kostyan_nsk, any thoughts/advice would be greatly appreciated...
Thanks
Printusrzero said:
like OP I am also trying to replace ascend p7 boot logo (vodafone)
OEM_logo.exe outputs a messed up bmp with sort of an sliding block puzzle effect.
Kostyan_nsk, any thoughts/advice would be greatly appreciated...
Thanks
Click to expand...
Click to collapse
I didn't test it on P7 just because I don't have it.
Can you upload your oeminfo file and bmp image you want to insert? I'll check what goes wrong.

Boot Animation Trouble (anyone with experience please help)

Ok so im stuck.
I've tried everything to install a different boot animation on my T-Mobile Note 4.
I tried downloading a file that was titled "CWM_CustomBootanimation_44_Enable.zip"
then going into an XDA thread that had a bunch of "bootanimation.zip"'s and choosing the one I liked.
Downloaded and placed it in my system/media/ folder.
Gave it the right permisions.
But nothing happened... I rebooted the phone and now all i had was just the stock samsung note 4 boot-up, but oddly i was now missing the T-mobile one that would show up right after, although the T-Mo jingle remained.
I kept searching and then found the strategy of just replacing the "bootsamsung.qmg" and "bootsamsungloop.qmg" files.
I found another boot animation i liked with .qmg format.
It came in zip folder and i extracted the 2 files, copied them over and named them like the original files (also adding an "_old" to the titles of the originals incase i ever needed them again)
Gave them the right permissions
Rebooted
And same thing again... just the stock black note 4 screen
At this point i decided to try another .qmg file, but this time for the shutdown animation...
Did pretty much the same run around...
and it worked! so the shut down animation was changed without a hitch.
I went back to the media folder and realized there were other boot files such as "bootsamsungmini.qmg", "bootsamsungminiloop.qmg", "bootsamsungmini2.qmg" and "bootsamsungmini2loop.qmg"
so i tried switching all of them to the 2 .qmg files i originally downloaded, with the right permissions, but nothing... still same stock black boot up.
So now, like i said, I'm stuck...
Should i have just put the whole zip file in the media folder? there were two folders in that zip. One was system/media with the two new boot animations and the other was META-INF/com/google/android/ with two files "update-binary" and "updater-script". Not sure if i have to do anything with these files.
Ive also heard theres an app on the market called Boot Animation but it has lots of mixed reviews, dont feel like going through the hassle of possibly bricking my device now.
And ive never been a custom rom kinda guy so i dont want to switch roms just for a boot animaion.
Any help would be appreciated thanks.
Anyone?
Most system/media files contain a bootanimation.zip folder. Make sure you delete it or when you put in the new qmg the system will boot from the zip file before the extracted qmgs

Huawei Honor 4x Balong and Hi6210sft

Hi all
As I said in title I updated to android 5 and now my model number and biuld numbers are changed to "hi6210sft" and "BalongC52B311"
also lots of files like "oeminfo" is deleted and when I copy it, after a reboot its deleted again!
I checked this link and edited "ro.build.display.id" and "ro.product.model" in "build.prop" file
https://forum.xda-developers.com/honor-4x/help/huawei-honor-4x-balong-hi6210sft-fixed-t3324335
but when I flashed again, all things returned to past!
also I changed all of "hi6210sft" to "Che2-L11" in "build.prop" file (because I think maybe the problem is that!) and after flashing all that lines are deleted! and I can't change them back because they are deleted!
now when I turn on my phone the red screen comes up and after some secconds honor logo comes and phone starts
I thing I should copy fresh file of "build.prop"
am I right?
if yes please help me
where can I find fresh file?
please help
Best Regards
PS. I don't know my original build number!
can you give me the link of your downloaded rom?
you have installed the wrong one of your region.
nicolasecc said:
Hi all
As I said in title I updated to android 5 and now my model number and biuld numbers are changed to "hi6210sft" and "BalongC52B311"
also lots of files like "oeminfo" is deleted and when I copy it, after a reboot its deleted again!
I checked this link and edited "ro.build.display.id" and "ro.product.model" in "build.prop" file
https://forum.xda-developers.com/honor-4x/help/huawei-honor-4x-balong-hi6210sft-fixed-t3324335
but when I flashed again, all things returned to past!
also I changed all of "hi6210sft" to "Che2-L11" in "build.prop" file (because I think maybe the problem is that!) and after flashing all that lines are deleted! and I can't change them back because they are deleted!
now when I turn on my phone the red screen comes up and after some secconds honor logo comes and phone starts
I thing I should copy fresh file of "build.prop"
am I right?
if yes please help me
where can I find fresh file?
please help
Best Regards
PS. I don't know my original build number!
Click to expand...
Click to collapse
have you got twrp installed on your device ? if yes now make a clean install of the ROM again.It will mostly solve the problem.
nicolasecc said:
Hi all
As I said in title I updated to android 5 and now my model number and biuld numbers are changed to "hi6210sft" and "BalongC52B311"
also lots of files like "oeminfo" is deleted and when I copy it, after a reboot its deleted again!
I checked this link and edited "ro.build.display.id" and "ro.product.model" in "build.prop" file
https://forum.xda-developers.com/honor-4x/help/huawei-honor-4x-balong-hi6210sft-fixed-t3324335
but when I flashed again, all things returned to past!
also I changed all of "hi6210sft" to "Che2-L11" in "build.prop" file (because I think maybe the problem is that!) and after flashing all that lines are deleted! and I can't change them back because they are deleted!
now when I turn on my phone the red screen comes up and after some secconds honor logo comes and phone starts
I thing I should copy fresh file of "build.prop"
am I right?
if yes please help me
where can I find fresh file?
please help
Best Regards
PS. I don't know my original build number!
Click to expand...
Click to collapse
You are right , u have to replace the build.prop with an original one.

Categories

Resources