Hello,
i have been looking for instructions on how to actually create my own boot animation.
The only things I found here was a guide on how to place boot animations, how to create one from a video file and a tool on how to make your own boot animation....
however:
there is actually no instructions or I have not seen them how to actually make the boot file, I want to something similar to evervolv boot animation with my own text. the tool seems the way to go but it says that I need part files, how to make them what do I actually need to do? a pointer would be really helpful and appreciated.
thanks
K
kyzerdroid said:
Hello,
i have been looking for instructions on how to actually create my own boot animation.
The only things I found here was a guide on how to place boot animations, how to create one from a video file and a tool on how to make your own boot animation....
however:
there is actually no instructions or I have not seen them how to actually make the boot file, I want to something similar to evervolv boot animation with my own text. the tool seems the way to go but it says that I need part files, how to make them what do I actually need to do? a pointer would be really helpful and appreciated.
thanks
K
Click to expand...
Click to collapse
Try this Making a custom bootanimation
Related
I'm trying to root my G1 from scratch. I downloaded the DREAMIG file to my freshly formatted SD card. After I shut my phone down and reboot using (CAMERA + POWER) I get the multicolored screen that says Serial0, but it doesn't give me any fastboot options for applying the new image. I hit back and the screen reloads, but Serial0 still shows up with no options for applying the new image. I hit back again and now the Serialno screen is frozen, it won't reload. I've repeated these steps multiple times, but still I can't get into fastboot.
Any ideas?
Wrong section dude, this is Development, not Q&A...
There are TONS of guides for rooting a phone, check this one:
http://forum.xda-developers.com/showthread.php?t=563679
I'm using the CyanogenMod wiki instructions. They don't address the issue that I'm having. They assume that I'll see a grey bootloader screen where I would then hit the Action key to apply the image file, but I don't see that gray screen just the multicolored one and I can't get out of it. Any help would be appreciated!!
You don't have a fastboot enabled bootloader, you have a stock one. At this point it shouldn't matter. You can get out of bootloader by pressing menu+talk+power, aka 3 finger salute.
If your phone, in bootloader mode, doesn't find DREAIMG.nbh that means you named it wrong: are you on windows machine? Make sure that it's not hiding extensions and you did not name your file DREAIMG.nbh.hbh. Make sure that you have the right file and it's not corrupted (MD5 sum), make sure your card is formated in FAT32 format. Once your nbh file is right format/name, your phone will find it automaticaly.
Once can apply the image (DREAIMG.nbh) you're fine. Just reboot after it's done and continue with your rooting process.
I got it to work. It now recognizes my NBH file. The only thing I did differently was to do a regular format of my SD card instead of a quick format. Weird.
Thanks for the replies!
http://forum.xda-developers.com/showthread.php?t=485364 check first post, i ran into something like that when i rooted my g1, try using qmat and also you need a wm based device to get it work
All questions go into the Questions and Answers forum. Next time, please post in the correct forum. Moved.
here i was hoping we could have a weekend of people searching and posting in the correct section
same problem
scrappyabs2 said:
I'm using the CyanogenMod wiki instructions. They don't address the issue that I'm having. They assume that I'll see a grey bootloader screen where I would then hit the Action key to apply the image file, but I don't see that gray screen just the multicolored one and I can't get out of it. Any help would be appreciated!!
Click to expand...
Click to collapse
I have the exact same problem
you must have gotten ahead of your self, the multicolored bootloader screen is stock and has little to no fastboot commands available to you. maybe you can explain in more detail where you are at in your rooting process and what guide your following
Ok, I am new to these forms and kind of a noob android user so please make it as simple as possible.
So, I rooted my phone but i never have messed with roms or kernels or anything (mostly because i dont understand them) so everything is stock (gingerbread 2.6 i believe). I was following an online guide to change the boot animation via root explorer and now my phone only shows the word "android" with the shine going through it. The weird thing is, I can turn on the phone and get to the homescreen, but I am not able to see anything except the boot screen. For example, when i turn it on, I am able to turn it off by pressing power then blindly searching for the turn off button on-screen.
I have searched long and hard for a solution, but they were all caused by uploading a CWM roms that went bad, but I didnt do that. I did have it at one point just to backup my rom because everyone said that it was important. So I do have a CWM backup, but no CWM app on my phone. I am able to get to recovery mode.
Please help thanks.
Hi,
I followed the very comprehensive guide here: http://forum.xda-developers.com/showthread.php?t=2271909
however when I tried to reboot it seem the booting process restarts and the Kindle Fire logo will flash on and of with 10 sek intervals.
any ideas how to get out of this?
Thanks
Christiansloth said:
Hi,
I followed the very comprehensive guide here: http://forum.xda-developers.com/showthread.php?t=2271909
however when I tried to reboot it seem the booting process restarts and the Kindle Fire logo will flash on and of with 10 sek intervals.
any ideas how to get out of this?
Thanks
Click to expand...
Click to collapse
Something went wrong. Do you see the blue logo? If you do, you have the bootloader installed properly. Enter recovery and wipe everything (except system and sdcard) and reboot. If not, try to restore using fastboot in step 6.
seokhun said:
Something went wrong. Do you see the blue logo? If you do, you have the bootloader installed properly. Enter recovery and wipe everything (except system and sdcard) and reboot. If not, try to restore using fastboot in step 6.
Click to expand...
Click to collapse
I have the same problem. No blue logo, just an infinite boot loop.
I can't get into fastboot, so I purchased a factory cable last night in hopes that it will help.
bryang said:
I have the same problem. No blue logo, just an infinite boot loop.
I can't get into fastboot, so I purchased a factory cable last night in hopes that it will help.
Click to expand...
Click to collapse
Because the device boots properly, you'll have no trouble getting into fastboot with the cable. I apologize something went wrong, but apparently it's on your end, because many people reported no issues. Please make sure you followed the guide to the tee.
seokhun said:
Because the device boots properly, you'll have no trouble getting into fastboot with the cable. I apologize something went wrong, but apparently it's on your end, because many people reported no issues. Please make sure you followed the guide to the tee.
Click to expand...
Click to collapse
Thanks...yes I also have no blue logo, the logo looks normal (white and orange). I have ordered a factory cable and will try that way.... any tips on this that is NOT covered already in your thread?
Thanks alot
Christiansloth said:
Thanks...yes I also have no blue logo, the logo looks normal (white and orange). I have ordered a factory cable and will try that way.... any tips on this that is NOT covered already in your thread?
Thanks alot
Click to expand...
Click to collapse
Not that I know of. Once you get the cable, it's simple. Use the restore tool linked in my guide, and follow instructions.
seokhun said:
Not that I know of. Once you get the cable, it's simple. Use the restore tool linked in my guide, and follow instructions.
Click to expand...
Click to collapse
Hi again,
I have not gotten hold of the factory cable, and have tried to run the restore tool here: http://forum.xda-developers.com/showthread.php?t=1951254
However, even if it seems to work fine and the img. file is copied, there is no change in the device: it still runs a boot loop with the orange Kindle logo going on and off.
I can get the festboot logo on the screen by plugging in the factory cable, but not sure what to do now?
Would be grateful for any advice...
Christiansloth said:
Hi again,
I have not gotten hold of the factory cable, and have tried to run the restore tool here: http://forum.xda-developers.com/showthread.php?t=1951254
However, even if it seems to work fine and the img. file is copied, there is no change in the device: it still runs a boot loop with the orange Kindle logo going on and off.
I can get the festboot logo on the screen by plugging in the factory cable, but not sure what to do now?
Would be grateful for any advice...
Click to expand...
Click to collapse
Ask in that thread, I've never used the tool, so I wouldn't know.
seokhun said:
Ask in that thread, I've never used the tool, so I wouldn't know.
Click to expand...
Click to collapse
Hi again again,
I got it running again....
In your guide step 4, it says to copy the ROM and Gapps to the sdcard.... is it the zip file there has to be copied or the unzipped files?
Thanks again.
C
Christiansloth said:
Hi again again,
I got it running again....
In your guide step 4, it says to copy the ROM and Gapps to the sdcard.... is it the zip file there has to be copied or the unzipped files?
Thanks again.
C
Click to expand...
Click to collapse
The zip itself. Both come in as zip files, move those to the sdcard in zip form.
I've been trying to make my own boot and shutdown animations using gifs and audio files, but nothing I do seems to work. I have used so many programs trying to do this, as well as trying to do it manually, to no avail. Has anybody been able to make their own boot and shutdown animations for this phone? If so, could you explain the process to me? Thanks.
Hi,
Please indulge me if this it a bit silly, but I am confused about installing magisk from recovery. I flashed the patched image to recovery partition, as per the github guide (https%3A//topjohnwu.github.io/Magisk/install.html%23boot-image-patching, sorry for the encoding, system forbids me to post link cuz I am new). Yet at this point I am unsure about what to do next. This is what I see now when I boot my phone to recovery using key combo:
- Reboot system now
- Apply update from ADB
- Apply update from internal storage
- Wipe data/factory reset
- Wipe cache partition
- Mounts a storage
If I select "Reboot system now", nothing seem to happen and it all looks like a normal startup.
In short, I would like to know how to run to a ystem with Magisk enabled.
Thanks in advance!
You're not actually supposed to boot to recovery. You need to release the key combo once you see the splash screen. Reference:
https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
Edit: and don't worry... Everyone's a noob at some point or another.
Didgeridoohan is right: It sounds like you're booting into your phone's stock recovery, instead of your custom recovery.
Forgive my presumptions, or if I sound condescending, but if you happened to have patched and flashed your partition mods with a PC, you might want to check if you even have a custom recovery installed. (I know that some phones aren't capable of having a custom recovery flashed, so your situation might be different.) If you don't have one, that would be the first step (most folks use TWRP). Once you can boot into your custom recovery, though, you should be good.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
Didgeridoohan said:
You're not actually supposed to boot to recovery. You need to release the key combo once you see the splash screen. Reference: ...install.html#magisk-in-recovery
Edit: and don't worry... Everyone's a noob at some point or another.
Click to expand...
Click to collapse
Right, this is the part where I get confused. I did follow the link you mentioned. After pressing [power] & [volume up] for about 8 seconds, I feel a vibration and the screen lights up, thats when i released the keys. I ended up getting that menu i describe above...(tears)...
Ideally, what should I see if things go right?
NeoHiPPy1980 said:
Didgeridoohan is right: It sounds like you're booting into your phone's stock recovery, instead of your custom recovery.
Forgive my presumptions, or if I sound condescending, but if you happened to have patched and flashed your partition mods with a PC, you might want to check if you even have a custom recovery installed. (I know that some phones aren't capable of having a custom recovery flashed, so your situation might be different.) If you don't have one, that would be the first step (most folks use TWRP). Once you can boot into your custom recovery, though, you should be good.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
Click to expand...
Click to collapse
No worries. Any suggestion is much ppreciated. Just to be sure (correct me if i m wrong), I thought that patching an image file is an independent way of installing magisk in case custom recovery is not available. So that s my case.
Anyhow, I would really like to learn a bit more about the situation where recovery partition contains both the stock recovery and custom recovery/patched image. There doesnt seem to be any difference whether i release the key combo or not once I see a splash screen. I always end up with that blue menu in recovery.
Wubwubdubdub said:
No worries. Any suggestion is much ppreciated. Just to be sure (correct me if i m wrong), I thought that patching an image file is an independent way of installing magisk in case custom recovery is not available. So that s my case.
Anyhow, I would really like to learn a bit more about the situation where recovery partition contains both the stock recovery and custom recovery/patched image. There doesnt seem to be any difference whether i release the key combo or not once I see a splash screen. I always end up with that blue menu in recovery.
Click to expand...
Click to collapse
If you don't mind my asking, which model of phone do you have? Most phones have a similar button combo, but are a bit quirky to get into the recovery.
Ex: On my LG V20, I have to hold Vol-, and Power, but release the power button at the splash screen for 0.5-1 seconds (while still holding Vol-) and then press/hold the Power button again...
As a suggestion, you may want to see if your phone has a similar quirk, depending on the make /model.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
[Solved] by flashing boot image instead of recovery image
I am still puzzled by the complications with booting into recovery mode. To work around it, I attemped installing Magisk using boot image patch and succeeded. Objective achieved yet question remains. Anyways, a big thanks to Didgeridoohan and NeoHiPPy1980. Knowing that someone will provide help is what stopped me from giving up.
NeoHiPPy1980 said:
If you don't mind my asking, which model of phone do you have? Most phones have a similar button combo, but are a bit quirky to get into the recovery.
Ex: On my LG V20, I have to hold Vol-, and Power, but release the power button at the splash screen for 0.5-1 seconds (while still holding Vol-) and then press/hold the Power button again...
As a suggestion, you may want to see if your phone has a similar quirk, depending on the make /model.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
Click to expand...
Click to collapse
I have a Ulefone, not sure if you ve heard of it
But that won't matter. I managed to get it working another way (see to my last post). I should probably have done that before making this post. Thanks for your assistance!
Great to hear you got things working, but why did you think you needed to use the recovery image for your device? Was any of the installation instructions unclear and in need of improvement (I'm just trying to learn for future reference)?
Didgeridoohan said:
Great to hear you got things working, but why did you think you needed to use the recovery image for your device? Was any of the installation instructions unclear and in need of improvement (I'm just trying to learn for future reference)?
Click to expand...
Click to collapse
Frankly, I find the Magisk Installation Guide to be one of very few documentation that is concise, coherent and user-friendly for both regular user and developer. So a big thumb up for you all! For your reference, here is the process of how I was lead to believe I needed the recovery img:
1.
I followed the instruction on "know your device" (https%3A//topjohnwu.github.io/Magisk/install.html#knowing-your-device). The first command returns nothing and the seconde comand returns true. Naturally, I assumed this means that my device is using system-as-root on a non-A/B device.
2.
I then read:
If your device is NOT A/B, but IS using system-as-root, then you will have to install Magisk to the recovery partition of your device. Follow the instructions in Boot Image Patching, but instead of using your boot image, use your recovery image. "
Click to expand...
Click to collapse
(https%3A//topjohnwu.github.io/Magisk/install.html#getting-started)
I am not sure if I misunderstood sth. At this point I still believe that according to the instruction I should have patched my recovery image. I do not know what system-as-boot actually is...
Yes, it does seem like your device is A-only system-as-root, which would normally mean you need to use the recovery image.
Unfortunately, with the Android ecosystem being as fractured as it is there will always be exceptions...
Thanks for the detailed response.
Hi Guys
Wubwubdubdub, I have got a question for you. I followed the same instructions as you mentioned in first post and ran into problems as well. How did you get around this problem? What is the difference between the two ways you mentioned here? (I believe I used the first way).
Wubwubdubdub said:
I flashed the patched image to recovery partition, as per the github guide
Click to expand...
Click to collapse
Wubwubdubdub said:
To work around it, I attemped installing Magisk using boot image patch and succeeded. Objective achieved yet question remains.
Click to expand...
Click to collapse
Thanks in advance!
MM