Hi guys, I recently flashed tesla roms (thanks Ground Zero team) and I miss the stock Stitch boot animation. I couldnt find the 1440p version of it. Can anyone provide me the file or flashable zip. Thanks
felixtaf said:
Hi guys, I recently flashed tesla roms (thanks Ground Zero team) and I miss the stock Stitch boot animation. I couldnt find the 1440p version of it. Can anyone provide me the file or flashable zip. Thanks
Click to expand...
Click to collapse
This is the stitch boot logo. This is I repeat this is not a flashable zip.
Unzip and fastboot the logo.bin through fastboot.
Code:
fastboot flash logo logo.bin
fastboot reboot
Thanks. But I need the whole stitich boot animation
This is the one am talking about.
I found some but they are for low res screens.
felixtaf said:
Thanks. But I need the whole stitich boot animation
This is the one am talking about.
I found some but they are for low res screens.
Click to expand...
Click to collapse
There it go :good:
Stitch Animation
don't forget to set the right permissions to it
Thanks.
After setting the right permissions its not showing up. I set 0644, am i right? Shows moto logo and 5 sec pause and straight to main screen.
Deletion of original due to corruption
EDIT ----- Caution this upload may have been corrupted, use the one two posts on (#8)
This is the one I was looking for. But it fails in twrp wile flashing.
felixtaf said:
This is the one I was looking for. But it fails in twrp wile flashing.
Click to expand...
Click to collapse
@felixtaf ... Can't understand that because I installed it on my A2017U before posting. Which leads me to say that when I uploaded it to XDA it came up with a strange comment in red in the post (you've probably seen it -- Attachment 4136033) which I have never seen before. I can only suggest that the upload was corrupted so I have added another to this post.
Without wishing to teach you how to suck eggs can I just state the following ..... After downloading, transfer it to your ext sd card, in TWRP go to "Install" and chose the file, let TWRP do it's thing. I don't suggest you don't know what you are doing it's just so strange that it doesn't work.
Yes, this works fine. Thanks
Jus flashed it via twrp and all fine ...
The one I posted before was not a TWRP flashable file, you need to place it in system/media and replace the bootanimation.zip file there (and set the 0644 permission)
Related
REQ Original Desire Boot Screen Please
need to replace the oxygen, fully rooted ect a quick set of steps would be really helpful as i have not changed a boot screen before thank you.
kuljit55 said:
REQ Original Desire Boot Screen Please
need to replace the oxygen, fully rooted ect a quick set of steps would be really helpful as i have not changed a boot screen before thank you.
Click to expand...
Click to collapse
The boot screen in Oxygen is contained within the framework-res.apk file, so to properly replace it requires updating the files in there.
However..I recreated the stock bootanimation as a bootanimation.zip file that can be placed in /data/local. I can upload a flashable zip this evening.
here you go:
http://dl.dropbox.com/u/13245387/bootanimation.zip
http://dl.dropbox.com/u/13245387/downanimation.zip
It depends on your ROM where to put it, but for mine, it was /system/customize/resource/
Edit: these are not flashable zips
Just rename the bootscreen animation to 'name.bak' and the stock will b shown.
Hello guys, I need help trying to get my boot animation that I downloaded to work. I rooted my device with kingroot and it works perfectly that my device is rooted correctly. I used the root browser and boot animations app by Jrummy or something like that then I grabbed a watchdogs bootanimation on the net named bootanimation.zip, it is has two parts and has the resolution of my s4 at&t i337. I installed the zip to data/local (didn't work) I checked the permission status and made sure they read rw-r-r. Then I installed it to system/media and that still didn't work. I realized that the boot animations were not being overwritten so I tried to rename the boot animation.zip to bootsamsung.qmg to replace the stock manafactuar boot animation and no luck. I searched everywhere on the Internet for a answer and they provided the same one that didn't work. If you guys want screenshots or the zip I can try to post it. But I would appreciate some help ASAP.
Have you tried deleting the original boot animation zip, leaving only the custom one?
This should not cause any serious problems.
The worst thing that can happen is that you will have a black screen (because the boot animation was deleted) during the boot process.
Stock firmware doesn't support .zip bootanimation. You need to convert manually the bootanimation into .qmg.
Sent from my ASUS_Z00A using XDA Labs
Hello,
I am just new with Samsung smartphones, previously I was on some other devices such Nexus which are easier to mod.
I would like to tweak the kernel( I already got the sources) to add few things but I need for that eventually the ramdisk and the kernel image to make a boot image.
I wanted to download the latest firmware, hoping a default boot image was integrated in it and that I could unpack but I got issue and connection loss so I can't even take a look at it.
I think I will be able to get the boot image with the dd command but to do so I need to be in a mod recovery(such twrp) and currently I can't.
Thx u
Firstly you've created a voting thread. If this is a standard question I suggest in future you leave the options at default.
Why can't you use TWRP?
My build also supports raw image backup of the boot partition.
Sorry about creating wrong thread type
I have extended this feature to include BOOT
Click to expand...
Click to collapse
Woot Yeah I didn't know about that!
So I can just get the current boot image, unpack it, replace with my kernel image, repack and done.
And then flash the boot image throw a zip install or your extended function.
Btw, I am was looking over the net but couldn't find an exact answer to this extra Q, is there any fastboot mode ? So I can just boot in a custom kernel image before flashing it.
Yep, just backup the boot partition using twrp.
Locate the boot image backup in the twrp backup folder.
Unpack it, make your mods, rename it boot.img, copy it to internal or external storage and flash it with TWRP using the INSTALL button.
Samsung devices dont have a fastboot mode.
@ashyx answered my questions, thx to him!
>Samsung devices dont have a fastboot mode.
My latest Samsung Tablet has a fastboot mode but it was manufactured around the end of 2012 ... So it is not quite recent
I've never known a Samsung device to use FASTBOOT, so that's news to me.
Samsung uses its own proprietary ODIN mode.
Which device is this?
Ahhah you gonna say I am half of a lier.
It was my nexus 10. Built by Samsung and running the 5250 exynos chip
Hi all, I posted this in the 6P bootloop thread, but didn't get a response. As that is a pretty LONG thread, i'm thinking my question may have gotten lost in the jumble.
Quick run down.
A few months back my 6P started the BLOD. I found the fix listed on these pages, applied it, and have been happily using my phone ever since. Phone is bone stock 7.1.2 other than the TWRP recovery and the modified EX kernel for 4 cores.
Since the fix, my phone FINALLY got the OTA update to go to Android 8.0 and i obviously want to get it done. My concern is HOW to do this without causing more headache.
Can anyone point me in the right direction? Should i use the OTA update or download the factory image from Google?
I've got some knowledge as i used to be into the "rooting" scene back in the day, but haven't for a while, so i feel a little lost.
Thanks for any help.
johnnyphive said:
Hi all, I posted this in the 6P bootloop thread, but didn't get a response. As that is a pretty LONG thread, i'm thinking my question may have gotten lost in the jumble.
Quick run down.
A few months back my 6P started the BLOD. I found the fix listed on these pages, applied it, and have been happily using my phone ever since. Phone is bone stock 7.1.2 other than the TWRP recovery and the modified EX kernel for 4 cores.
Since the fix, my phone FINALLY got the OTA update to go to Android 8.0 and i obviously want to get it done. My concern is HOW to do this without causing more headache.
Can anyone point me in the right direction? Should i use the OTA update or download the factory image from Google?
I've got some knowledge as i used to be into the "rooting" scene back in the day, but haven't for a while, so i feel a little lost.
Thanks for any help.
Click to expand...
Click to collapse
Well, for starters do NOT take the OTA. It will either fail or boot loop your phone. Due to the fact you have a modified boot.img you will need to update manually using fastboot with the full image. Re-apply the modified kernel after you finish updating the partitions, but BEFORE booting the first time. You can follow most guides on how to manually update a full image using fastboot, just add the step of flashing the modified kernel before booting.
Thanks for the reply and the help. If i could ask for a little more help, as this is my only phone.
Can you explain the difference between the modified boot.img and the modified kernel?
If i download the factory image from here (https://developers.google.com/android/images) is it ok to the get the latested one (Nov 2017) or do i need to get the original one (Sep 2017 as i'm on Fi)
Once i flash the factory image, is it going to replace the modified boot image as well as the modified kernel?
Follow the OP on this thread (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) in the downloads section there appear to be 2 files i would need, the "Boot.img from stock 6.17, 8.0 firmware" and "EX kernel version 5.03". Am i understanding that correctly?
Like i said, this is my only phone, and i'm probably just being overly paranoid about bricking it, but any clarification would be greatly appreciated.
johnnyphive said:
Thanks for the reply and the help. If i could ask for a little more help, as this is my only phone.
Can you explain the difference between the modified boot.img and the modified kernel?
If i download the factory image from here (https://developers.google.com/android/images) is it ok to the get the latested one (Nov 2017) or do i need to get the original one (Sep 2017 as i'm on Fi)
Once i flash the factory image, is it going to replace the modified boot image as well as the modified kernel?
Follow the OP on this thread (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) in the downloads section there appear to be 2 files i would need, the "Boot.img from stock 6.17, 8.0 firmware" and "EX kernel version 5.03". Am i understanding that correctly?
Like i said, this is my only phone, and i'm probably just being overly paranoid about bricking it, but any clarification would be greatly appreciated.
Click to expand...
Click to collapse
Use the latest November image. The boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. When you flash the new boot.img contained in the Google image, it will overwrite the patched kernel. You then need to re-patch it by installing EX kernel before booting. EX writes to (modifies) the stock boot.img. There are also pre-modifed boot.img files floating around. You will probably get more detailed help in the dedicated thread. Learning to flash manually (or remember how) is not really a big deal and a necessary skill for modding (and for getting yourself out of trouble). Good luck. :good:
v12xke said:
Use the latest November image. The boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. When you flash the new boot.img contained in the Google image, it will overwrite the patched kernel. You then need to re-patch it by installing EX kernel before booting. EX writes to (modifies) the stock boot.img. There are also pre-modifed boot.img files floating around. You will probably get more detailed help in the dedicated thread. Learning to flash manually (or remember how) is not really a big deal and a necessary skill for modding (and for getting yourself out of trouble). Good luck. :good:
Click to expand...
Click to collapse
Ok, so 1 last time (sorry)
1 - Downloaded the latest 8.0.0 factory image from google (this contains the bootloader, radio, and partitions (.zip).
2 - Get phone to fastboot and apply the above 3 new images
3- before rebooting, flash oreo4core (new, modified boot.img), TWRP recovery.img
4- reboot to recovery (TWRP) and apply the modified EX kernel
5 - reboot and (hopefully) profit
Am i missing anything, or doing anything that isn't needed?
johnnyphive said:
Ok, so 1 last time (sorry)
1 - Downloaded the latest 8.0.0 factory image from google (this contains the bootloader, radio, and partitions (.zip).
2 - Get phone to fastboot and apply the above 3 new images
3- before rebooting, flash oreo4core (new, modified boot.img), TWRP recovery.img
4- reboot to recovery (TWRP) and apply the modified EX kernel
5 - reboot and (hopefully) profit
Am i missing anything, or doing anything that isn't needed?
Click to expand...
Click to collapse
<<Disclaimer: I don't use the 4 core kernel, so I don't know if it comes with installer script or someone has just modified the latest boot.img>> Unzip the "partitions" zip you refer to and extract those image files to the same folder as bootloader and modem. For example, you can keep TWRP recovery if you don't flash the recovery.img. That is how you preserve your custom recovery. So in other words you'll now have a folder (your ADB folder?) with 5 image files.... bootloader, radio, boot, system, and vendor all in one folder. <<Note: it is my understanding you just substitute the latest oreo4core file (should be boot.img?) If this is true, copy that file into your ADB folder and let it overwrite the stock boot.img. Stop. Copy over flash-all.bat, change the *.bat extension to *.txt and open in notepad. You will see (and can copy/paste) the fastboot commands to get you started with bootloader and radio. Then flash the last 3 (boot, system, vendor). At this point you can reboot into the OS. Since you substituted the oreo4core boot.img file for the stock boot.img there is no need to use TWRP to flash anything. That and since you skipped flashing the recovery.img, TWRP is still there.
v12xke said:
<<Disclaimer: I don't use the 4 core kernel, so I don't know if it comes with installer script or someone has just modified the latest boot.img>> Unzip the "partitions" zip you refer to and extract those image files to the same folder as bootloader and modem. For example, you can keep TWRP recovery if you don't flash the recovery.img. That is how you preserve your custom recovery. So in other words you'll now have a folder (your ADB folder?) with 5 image files.... bootloader, radio, boot, system, and vendor all in one folder. <<Note: it is my understanding you just substitute the latest oreo4core file (should be boot.img?) If this is true, copy that file into your ADB folder and let it overwrite the stock boot.img. Stop. Copy over flash-all.bat, change the *.bat extension to *.txt and open in notepad. You will see (and can copy/paste) the fastboot commands to get you started with bootloader and radio. Then flash the last 3 (boot, system, vendor). At this point you can reboot into the OS. Since you substituted the oreo4core boot.img file for the stock boot.img there is no need to use TWRP to flash anything. That and since you skipped flashing the recovery.img, TWRP is still there.
Click to expand...
Click to collapse
Thank for the help! Everything seems to be up and running. I know you said you don't use the "4 cores" (can only assume your either on a different phone or yours isn't affected by the BLOD), but do you know if i still need to apply the EX kernel update, or know of a way to tell if it's already been applied?
Thanks again for all the help. I was pretty much in the right direction, but being as how i'd been away from it for a while, i wanted some backup
johnnyphive said:
Thank for the help! Everything seems to be up and running. I know you said you don't use the "4 cores" (can only assume your either on a different phone or yours isn't affected by the BLOD), but do you know if i still need to apply the EX kernel update, or know of a way to tell if it's already been applied? Thanks again for all the help. I was pretty much in the right direction, but being as how i'd been away from it for a while, i wanted some backup
Click to expand...
Click to collapse
I don't think you can flash EX kernel from now on. I think you have to use a modded boot.img that will contain his kernel/ramdisk. This is my guess. You really should be getting your information in the dedicated thread where everyone is actually installing and using it. Google "oreo 4 core" and you will find the XDA thread is the first hit. Good luck. :good:
I'm currently dealing with a totally bricked tablet and have not been able to find any roms for the 100011885 onn 8 gen 2. Any help would be greatly appreciated
same, good thing it was a free tablet lol
Invisibility said:
same, good thing it was a free tablet lol
Click to expand...
Click to collapse
Lol I wish mine was free I paid the retail price for it..
I dumped my images earlier today trying to root it. Just uploaded to my google drive for you if it helps. I tried patching magisk, but alas got in a boot loop. Luckily I had backed up boot.img so it was trivial to flash it back and get it to start again.
100011885 Images: https://drive.google.com/drive/folders/17LtLtjKg4JJU9EJdIXPsyNjen0H-ilMX?usp=sharing
I was working on a rooting guide for these things (with more detail than the other threads have). The last thing I rooted was a Galaxy S3 back in the day, lol. It's been interesting catching up with all the new rooting things out there.
netninja2001 said:
I dumped my images earlier today trying to root it. Just uploaded to my google drive for you if it helps. I tried patching magisk, but alas got in a boot loop. Luckily I had backed up boot.img so it was trivial to flash it back and get it to start again.
100011885 Images: https://drive.google.com/drive/folders/17LtLtjKg4JJU9EJdIXPsyNjen0H-ilMX?usp=sharing
I was working on a rooting guide for these things (with more detail than the other threads have). The last thing I rooted was a Galaxy S3 back in the day, lol. It's been interesting catching up with all the new rooting things out there.
Click to expand...
Click to collapse
Thank you very much! I'm very thankful for your help! When I get time I'm going to try this out and see what happens!
netninja2001 said:
I dumped my images earlier today trying to root it. Just uploaded to my google drive for you if it helps. I tried patching magisk, but alas got in a boot loop. Luckily I had backed up boot.img so it was trivial to flash it back and get it to start again.
100011885 Images: https://drive.google.com/drive/folders/17LtLtjKg4JJU9EJdIXPsyNjen0H-ilMX?usp=sharing
I was working on a rooting guide for these things (with more detail than the other threads have). The last thing I rooted was a Galaxy S3 back in the day, lol. It's been interesting catching up with all the new rooting things out there.
Click to expand...
Click to collapse
Thank you so much for hosting these images, I accidentally soft bricked my onn. tablet by flashing a bad twrp image, and using the stock recovery image you have hosted I was able to restore it to full functionality.
netninja2001 said:
I dumped my images earlier today trying to root it. Just uploaded to my google drive for you if it helps. I tried patching magisk, but alas got in a boot loop. Luckily I had backed up boot.img so it was trivial to flash it back and get it to start again.
100011885 Images: https://drive.google.com/drive/folders/17LtLtjKg4JJU9EJdIXPsyNjen0H-ilMX?usp=sharing
I was working on a rooting guide for these things (with more detail than the other threads have). The last thing I rooted was a Galaxy S3 back in the day, lol. It's been interesting catching up with all the new rooting things out there.
Click to expand...
Click to collapse
Absolute lifesaver, I restored my recovery and boot.img with your dumps, however.. the file you uploaded to Google drive containing the rest of the system images doesn't have a file extension, and I don't exactly know what I'm supposed to do in order to access them. Changing the extension to .zip, .img, .iso, ect, opens in 7zip and shows the different images, however when I try to extract it, 7zip throws errors about unexpected endings of files.
Question is, how do I actually use the "ROM" file you've uploaded?
Thanks so much!!
-layla
Ankylo'sburner said:
Absolute lifesaver, I restored my recovery and boot.img with your dumps, however.. the file you uploaded to Google drive containing the rest of the system images doesn't have a file extension, and I don't exactly know what I'm supposed to do in order to access them. Changing the extension to .zip, .img, .iso, ect, opens in 7zip and shows the different images, however when I try to extract it, 7zip throws errors about unexpected endings of files.
Question is, how do I actually use the "ROM" file you've uploaded?
Thanks so much!!
-layla
Click to expand...
Click to collapse
i need this as well
netninja2001 said:
I dumped my images earlier today trying to root it. Just uploaded to my google drive for you if it helps. I tried patching magisk, but alas got in a boot loop. Luckily I had backed up boot.img so it was trivial to flash it back and get it to start again.
100011885 Images: https://drive.google.com/drive/folders/17LtLtjKg4JJU9EJdIXPsyNjen0H-ilMX?usp=sharing
I was working on a rooting guide for these things (with more detail than the other threads have). The last thing I rooted was a Galaxy S3 back in the day, lol. It's been interesting catching up with all the new rooting things out there.
Click to expand...
Click to collapse
Did you manage to figure out the root situation with these?
Valiante said:
Did you manage to figure out the root situation with these?
Click to expand...
Click to collapse
I am working on a solution right now I will update you if it works
Valiante said:
Did you manage to figure out the root situation with these?
Click to expand...
Click to collapse
Magisk causes odd behavior especially with GSI, I would recommend just going for a prerooted GSI . Working on making twrp for this device. The 32MB recovery partition makes it a challenge I'm currently running a Android 12 GSI with enough room left over in the system partion to push a small gapps package but no way to install it yet.. I'll make it possible eventually. Might have to disable AVB and encryption but it's better than dealing with stock
DarkUmbre said:
I'm currently dealing with a totally bricked tablet and have not been able to find any roms for the 100011885 onn 8 gen 2. Any help would be greatly appreciated
Click to expand...
Click to collapse
Mine is softbricked, I am able to boot into recovery and fastboot. I patched the boot.img with Magisk and now it's stuck in a bootloop. I tried factory resetting, nothing. I flashed the boot.img you provided, nothing. It just gets stuck at the Orange State screen. I am on stock ROM.
netninja2001 said:
I dumped my images earlier today trying to root it. Just uploaded to my google drive for you if it helps. I tried patching magisk, but alas got in a boot loop. Luckily I had backed up boot.img so it was trivial to flash it back and get it to start again.
100011885 Images: https://drive.google.com/drive/folders/17LtLtjKg4JJU9EJdIXPsyNjen0H-ilMX?usp=sharing
I was working on a rooting guide for these things (with more detail than the other threads have). The last thing I rooted was a Galaxy S3 back in the day, lol. It's been interesting catching up with all the new rooting things out there.
Click to expand...
Click to collapse
Can I compress the files into a ZIP and adb sideload it from stock recovery?
How did you dump the stock rom?
netninja2001 said:
I dumped my images earlier today trying to root it. Just uploaded to my google drive for you if it helps. I tried patching magisk, but alas got in a boot loop. Luckily I had backed up boot.img so it was trivial to flash it back and get it to start again.
100011885 Images: https://drive.google.com/drive/folders/17LtLtjKg4JJU9EJdIXPsyNjen0H-ilMX?usp=sharing
I was working on a rooting guide for these things (with more detail than the other threads have). The last thing I rooted was a Galaxy S3 back in the day, lol. It's been interesting catching up with all the new rooting things out there.
Click to expand...
Click to collapse
Thanks! I needed this.
Here is full stock ROM for this device:
Brand: ONN
Model: 100011885
Hardware: MT8168
Android version: 10
Firmware version: 1626247541
Build number: alps-mp-q0.mp3-V4.156
Description: full_tb8168p1_64_bsp-userdebug 10 QP1A.190711.020 1612404168 release-keys
File on MEGA
mega.nz
yeppp i've done it. my onn 8' completely stuck in the orange state bootloop and i need help! i erase the boot/ recovery.img and then flash them back on with fastboot? I couldn't get spflashtool to work on my pc with this tablet.
It is 100011885, doesn't work with adb but does come up under fastboot when i get the tablet in the fastboot mode, other than that it's orange state bootloop, anything would be a help, if not it's straight up trashhhh, and thank you for your time
is there a way to wipe it ? and flash the roms and all to it or is it still salvageable?
i'll add a few screenshots to show where i'm at but i am lost and need alittle guide dens.
UalreadyknowImZane said:
yeppp i've done it. my onn 8' completely stuck in the orange state bootloop and i need help! i erase the boot/ recovery.img and then flash them back on with fastboot? I couldn't get spflashtool to work on my pc with this tablet.
It is 100011885, doesn't work with adb but does come up under fastboot when i get the tablet in the fastboot mode, other than that it's orange state bootloop, anything would be a help, if not it's straight up trashhhh, and thank you for your time
is there a way to wipe it ? and flash the roms and all to it or is it still salvageable?
i'll add a few screenshots to show where i'm at but i am lost and need alittle guide dens.
Click to expand...
Click to collapse
with mine it says system partition doesn't exist
$cronos_ said:
with mine it says system partition doesn't exist
Click to expand...
Click to collapse
for fastboot erase system -w ?
cause mine does that, i wanna try and at least get it working lol
i got time later tonight.
why is it not booting though? like did i mess up the boot.img?
is there anyway to see the files on this device or its a brick?
& sorry i'm literally brand new to this and chose a cheap walmart tablet to start so i have MANY questions <- if it's trash u can tell me and i'll stop buggin
UalreadyknowImZane said:
for fastboot erase system -w ?
cause mine does that, i wanna try and at least get it working lol
i got time later tonight.
why is it not booting though? like did i mess up the boot.img?
is there anyway to see the files on this device or its a brick?
& sorry i'm literally brand new to this and chose a cheap walmart tablet to start so i have MANY questions <- if it's trash u can tell me and i'll stop buggin
Click to expand...
Click to collapse
FAILED remote: partition table doesn't exist is what it does when i flash system.img