My Galaxy Tab is refusing to boot past the Samsung logo (it's using the stock firmware). I believe someone modified a file in the system folder which is causing it to not boot up.
I have a backup of all the files in the system folder and I was wondering if there was anyway to replace the files inside the folder? Or at the very least revert back to the stock firmware?
Thanks.
awhalen said:
My Galaxy Tab is refusing to boot past the Samsung logo (it's using the stock firmware). I believe someone modified a file in the system folder which is causing it to not boot up.
I have a backup of all the files in the system folder and I was wondering if there was anyway to replace the files inside the folder? Or at the very least revert back to the stock firmware?
Thanks.
Click to expand...
Click to collapse
Who is your provider must be nice Clubtech did post a stock firmware for AT&T tab under Development. You might also find one for TMob there as well.
As for replacement the files, I don't have the tab with me but if you remount the partition where the sytem files are, you could copy over. SOme of the partitions are mounted read-only, this is why you can't copy things over.
Disregard the last part as you can't boot it up so there isn't way for you to remount the partition lol
Related
Well i have a Samsung Vibrant rooted with OCLF and running Launcher Pro. I tried to change my boot screen which i read up on here before doing. I read on this forum theres is 2 ways to actually do it, which is using the command on your pc which im not too good with codes so i tried the 2nd option which is to copy and paste using the Root Explorer. So i copied the bootanimation.zip from SD card while on mount r/w and paste it to system/media and then reboot. I still have the stock boot up not sure if i did something wrong, this is my 1st android phone which i like way better than my Icrap so any help will be appreciated.
borikua954 said:
Well i have a Samsung Vibrant rooted with OCLF and running Launcher Pro. I tried to change my boot screen which i read up on here before doing. I read on this forum theres is 2 ways to actually do it, which is using the command on your pc which im not too good with codes so i tried the 2nd option which is to copy and paste using the Root Explorer. So i copied the bootanimation.zip from SD card while on mount r/w and paste it to system/media and then reboot. I still have the stock boot up not sure if i did something wrong, this is my 1st android phone which i like way better than my Icrap so any help will be appreciated.
Click to expand...
Click to collapse
Why dont you give this a try
USE THE GALAXY I9000 BOOTUP / SHUTDOWN ANIMATIONS & SOUND
rko did an awesome job with these flashable bootup/shutdown animations (place them on the /sdcard (internal memory) NOT sdcard/sd (external). Be sure and thank him for his work!
http://forum.xda-developers.com/showpost.php?p=7663822&postcount=38
Thanks to s15274n
i tired it it doesnt work either comes up with error code
You have to have a rom that has a hacked kernel that allows for support of bootanimation.zip the stock vibrant rom does not have this ability (Thankyou Samsung), so simply putting the file in the correct folder will do nothing if you don't have the kernel that utilizes it. Currently there are 2 roms that will work with this:
Obsidian V2 - JK2 Official Froyo Based 2.2
or
Froyo Macnut R10
you put the .zip files in /system/media which is NOT the right way of doing it
extract the zip file anywhere on your desktop and copy the bootsamsung.qmg into your internal sdcard.
then run root explorer on your phone, copy the same .qmg file from your sdcard into /system/media folder
motoyola said:
you put the .zip files in /system/media which is NOT the right way of doing it
extract the zip file anywhere on your desktop and copy the bootsamsung.qmg into your internal sdcard.
then run root explorer on your phone, copy the same .qmg file from your sdcard into /system/media folder
Click to expand...
Click to collapse
A bootanimation.zip is a zip with a series of images in it, there is no qmg in it. The OP was not asking about the qmg I don't think. He wants to be able to use his own bootscreens which cannot be done with qmg, only with bootanimation.zip and a hacked kernel.
the3dman said:
A bootanimation.zip is a zip with a series of images in it, there is no qmg in it. The OP was not asking about the qmg I don't think. He wants to be able to use his own bootscreens which cannot be done with qmg, only with bootanimation.zip and a hacked kernel.
Click to expand...
Click to collapse
obviously you didnt read what op said:
so i tried the 2nd option which is to copy and paste using the Root Explorer. So i copied the bootanimation.zip from SD card while on mount r/w and paste it to system/media and then reboot
Click to expand...
Click to collapse
meaning hes dropping the whole zip file into /system/media through root explorer
i just told him the proper way of doing it as it was discussed here
the only mistake i did was use the "bootanimation.zip" as reference
since OP didnt even mention where he got the bootanimation.zip and i assumed things
im sorry about the confusion
ok sorry for the confusion and i thank you both for the responses.Lets see if i can explain it a little better.(It wont let me post a link but i found it here on XDA which is the THC boot up) the bootanimation.zip file i was trying to use which does not have the qmg for me to extract so i tried to put in system/media which did not work. Then i tried chichu_9 boot up screen which he recommended and did exactly as motoyola did which i extracted the qmg file and put in sd card (not external) then copy/paste into system/media which replaced the stock qmg file for the vibrant then i reboot and still stuck with the stock boot up screen. I am currently running Eugenes leaked 2.2 rom which works pretty good so far just cannot change boot screens for some reason so if i missed something or did something incorrect pls feel free to correct me and thanks in advance.....
I tried to pull the system files from the stock system.img thru Dsixda kitchen....it said no system files found. Sgs2 popped up, but there was no files.
I did this to pull system files from tmobile stock firmware. So im not too sure of why it didnt pull the files.
I did use 7zip to "unzip" the tar file. Selected system.img and put it in the kitchen....selected "set up working folder"...then I got no system files found.
Am I missing something?
Sent from a Insane S4
alloycowboy said:
I tried to pull the system files from the stock system.img thru Dsixda kitchen....it said no system files found. Sgs2 popped up, but there was no files.
I did this to pull system files from tmobile stock firmware. So im not too sure of why it didnt pull the files.
I did use 7zip to "unzip" the tar file. Selected system.img and put it in the kitchen....selected "set up working folder"...then I got no system files found.
Am I missing something?
Sent from a Insane S4
Click to expand...
Click to collapse
try updated kitchen
regards
Solved
Im on current version
Sent from a Insane S4
Why don't you connect your phone in debug mode and shift right click in your working folder and : adb pull /system/
Or are you working from files only? If so you can run your Linux commands from kitchen?
Sent from my GT-I9505G using Tapatalk 2
Make it an ext4 then add a boot.img and a cache or data partition. Then try to set up the working folder
Sent from my cm_tenderloin using xda app-developers app
Can someone please advise how I restore the default boot animations on the OMEGA rom? I have downloaded the file from the OMEGA files fileserver.
I tried placing the bootanimation.zip in /system/media and also tried to use install from TWRP.
I have tried searching but not finding the exact procedure.
Thanks
TheTechnician75 said:
Can someone please advise how I restore the default boot animations on the OMEGA rom?
I have tried searching but not finding the exact procedure.
Thanks
Click to expand...
Click to collapse
First, if you've tried flashing a .zip via TWRP or other recovery and your phone now goes blank between the S4 logo and the full boot you might have to contend with a broken boot animation... Personally it bothered me so much I reflashed Omega lol.
I downloaded on my phone the Samsung S5 boot/Shutdown animations.
Using E/S File explorer I first renamed the following files on the phone:
"/system/media/bootsamsung.qmg" => "/system/media/bootsamsung.qmg.old"
"/system/media/bootsamsungloop.qmg" => "/system/media/bootsamsungloop.qmg.old"
"/system/media/shutdown.qmg" => "/system/media/shutdown.qmg.old"
I decompressed the S5.zip archive.
I copied from the archive "S5.zip/system/media/bootsamsung.qmg", "S5.zip/system/media/bootsamsungloop.qmg" and the "S5.zip/system/media/shutdown.qmg" into /system/media
Again using ES file explorer I set one by one the new file attrubutes so that they would be -wr-r--r--
Reboot the phone and voila - new boot animation.
If this works you can then delete the .old files in /system/media
If you want to load other boot animations there are enablers and disablers for the bootanimation.zip but I stayed clear as I want mine as standard as possible.
duxxyuk said:
First, if you've tried flashing a .zip via TWRP or other recovery and your phone now goes blank between the S4 logo and the full boot you might have to contend with a broken boot animation... Personally it bothered me so much I reflashed Omega lol.
I downloaded on my phone the Samsung S5 boot/Shutdown animations.
Using E/S File explorer I first renamed the following files on the phone:
"/system/media/bootsamsung.qmg" => "/system/media/bootsamsung.qmg.old"
"/system/media/bootsamsungloop.qmg" => "/system/media/bootsamsungloop.qmg.old"
"/system/media/shutdown.qmg" => "/system/media/shutdown.qmg.old"
I decompressed the S5.zip archive.
I copied from the archive "S5.zip/system/media/bootsamsung.qmg", "S5.zip/system/media/bootsamsungloop.qmg" and the "S5.zip/system/media/shutdown.qmg" into /system/media
Again using ES file explorer I set one by one the new file attrubutes so that they would be -wr-r--r--
Reboot the phone and voila - new boot animation.
If this works you can then delete the .old files in /system/media
If you want to load other boot animations there are enablers and disablers for the bootanimation.zip but I stayed clear as I want mine as standard as possible.
Click to expand...
Click to collapse
Thanks mate!
Reflashed the rom then followed your instructions to replace it with the original Samsung boot and shutdown animations.
cheers
I've changed bootanimations before on other devices, but the file was always called "bootanimation.zip." Looking at the files in the SGS5, I see 3 different "boot*.qmg" files, but no "bootanimation.zip."
Since we don't have a custom recovery yet, I'm hesitant to rename the *.qmg files and drop in a "bootanimation.zip" I created for my SGS4 into the same folder. Is there some new way to replace bootanimations on an SGS5 due to the *.qmg file extension, or it's safe to just rename/delete the *.qmg files and drop in the "bootanimation.zip" file into the appropriate folder?
I'd hate to get stuck in a bootloop and have to odin back to stock only to be unable to fully "restore" my phone's settings afterwards (yes, I have TiBu & other apps that'll allow me to restore, but it's certainly not as easy or as complete as restoring a nandroid backup).
Icculus760 said:
I've changed bootanimations before on other devices, but the file was always called "bootanimation.zip." Looking at the files in the SGS5, I see 3 different "boot*.qmg" files, but no "bootanimation.zip."
Since we don't have a custom recovery yet, I'm hesitant to rename the *.qmg files and drop in a "bootanimation.zip" I created for my SGS4 into the same folder. Is there some new way to replace bootanimations on an SGS5 due to the *.qmg file extension, or it's safe to just rename/delete the *.qmg files and drop in the "bootanimation.zip" file into the appropriate folder?
I'd hate to get stuck in a bootloop and have to odin back to stock only to be unable to fully "restore" my phone's settings afterwards (yes, I have TiBu & other apps that'll allow me to restore, but it's certainly not as easy or as complete as restoring a nandroid backup).
Click to expand...
Click to collapse
Follow these instructions. Enjoy.
Misterxtc said:
Follow these instructions. Enjoy.
Click to expand...
Click to collapse
Thank you very much for the direction. While I'll give it a shot a later, that still won't allow me to replace the default bootanimation w/ the ones I've previously created. The bootanimation.zip files I want to use only contain *.png files (the *png's are in "part0" folder and there is a desc.txt file in the parent directory). There are no *.qmg files in those zip's to extract, so that process won't work for me & the bootanimations I'm trying to use.
Any other ideas, or is my only option to use something like the Samsung Theme Designer process? (http://forum.xda-developers.com/showthread.php?t=2696914)
Icculus760 said:
Thank you very much for the direction. While I'll give it a shot a later, that still won't allow me to replace the default bootanimation w/ the ones I've previously created. The bootanimation.zip files I want to use only contain *.png files (the *png's are in "part0" folder and there is a desc.txt file in the parent directory). There are no *.qmg files in those zip's to extract, so that process won't work for me & the bootanimations I'm trying to use.
Any other ideas, or is my only option to use something like the Samsung Theme Designer process? (http://forum.xda-developers.com/showthread.php?t=2696914)
Click to expand...
Click to collapse
Contact the maker of the OP of the thread with the boot animations, I'm pretty sure he/she can help you out converting the files. It's been done before in that thread.
Misterxtc said:
Contact the maker of the OP of the thread with the boot animations, I'm pretty sure he/she can help you out converting the files. It's been done before in that thread.
Click to expand...
Click to collapse
What the heck, man. Stop helping me so quickly! :laugh:
Thanks again!!
I was trying to disable the hardware buttons, the one next to the home button, and use on screen buttons. But when I edited the file the first time the back button was disabled which is what I wanted but not the other button (menu?). So I tried again and when es file explorer saved it, it saved it as a empty text document. So what I'm asking you is a copy of your generic.kl file which is located in system>use>keylayout. Im sorry if this is in the wrong place im just kinda scared about what could happen, like not being able to power back on. Thank you!
xada162 said:
I'm asking you is a copy of your generic.kl file which is located in system>use>keylayout.
Click to expand...
Click to collapse
You should start making backups. Everyone runs into problems eventually and if you had a backup you could revert to a 100% stable system with only a few clicks.
The file that you can want can be found in the full, stock firmware image. Just download the full firmware and use winrar to extract what you need.
.
Just dirty flash the rom you have (without a wipe).
fffft said:
You should start making backups. Everyone runs into problems eventually and if you had a backup you could revert to a 100% stable system with only a few clicks.
The file that you can want can be found in the full, stock firmware image. Just download the full firmware and use winrar to extract what you need.
.
Click to expand...
Click to collapse
So I have backups of my phone with twrp but I'm lost as to what I need to look for/where that file is going to be
xada162 said:
So I have backups of my phone with twrp but I'm lost as to what I need to look for/where that file is going to be
Click to expand...
Click to collapse
I thought you knew exactly what file you accidentally corrupted. In your original post you said
xada162 said:
I'm asking you is a copy of your generic.kl file which is located in system>use>keylayout.
Click to expand...
Click to collapse
So on that basis, you could extract the cited file from the TWRP system image. Or temporarily restore it and copy that file. Or for that matter simply restore the entire /system partition. The latter would cover you even if you weren't positive which system files were corrupted.
So boot to TWRP, wipe your system cache, then restore the system partition from a known good backup and call it day.
.