Related
This is the Logo (splash screen), bootanimation and downanimation from the Chinese version of the OnePlus One.
Requirements:
ADB and Fastboot knowledge
Boot and down animations require root
Logo requires unlocked bootloader
Use a root file explorer and navigate to /system/media rename bootanimation.zip to bootanimation.old
copy bootanimation.zip and rbootanimation.zip and change the permissions to match the other files:
for logo:
boot into fastboot mode and run the following command:
fastboot flash LOGO logo.img
Links:
bootanimation: http://www.androidfilehost.com/?fid=23501681358540397
rbootanimation: http://www.androidfilehost.com/?fid=23501681358540399
logo: http://www.androidfilehost.com/?fid=23501681358540401
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it, or it kills your neighbor's dog.. It was the other guy... I swear.... Flash at your own risk
Pretty basic if you ask me not that a boot animation is really that important but you'd think they'd put a bit more effort into it.
Sent from my Nexus 7 using Tapatalk
graffixnyc said:
This is the Logo (splash screen), bootanimation and downanimation from the Chinese version of the OnePlus One.
Requirements:
ADB and Fastboot knowledge
Boot and down animations require root
Logo requires unlocked bootloader
Use a root file explorer and navigate to /system/media rename bootanimation.zip to bootanimation.old
copy bootanimation.zip and rbootanimation.zip and change the permissions to match the other files:
for logo:
boot into fastboot mode and run the following command:
fastboot flash LOGO logo.img
Links:
bootanimation: http://www.androidfilehost.com/?fid=23501681358540397
rbootanimation: http://www.androidfilehost.com/?fid=23501681358540399
logo: http://www.androidfilehost.com/?fid=23501681358540401
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it, or it kills your neighbor's dog.. It was the other guy... I swear.... Flash at your own risk
Click to expand...
Click to collapse
I tried but didn't get the bootanimations..only the logo part is working....Also device didn't sleep at all....reverted back to CM bootanimation..Using CM11 latest nightly(24 June)....Don't know whats I am doing wrong!!!
mannu_in said:
I tried but didn't get the bootanimations..only the logo part is working....Also device didn't sleep at all....reverted back to CM bootanimation..Using CM11 latest nightly(24 June)....Don't know whats I am doing wrong!!!
Click to expand...
Click to collapse
Thanks. I prefer this to our white version with the crappy ANDROID text at the bottom.
Are there any other logo.img files for this phone? Or any apps that will create them?
cybertlc said:
Thanks. I prefer this to our white version with the crappy ANDROID text at the bottom.
Are there any other logo.img files for this phone? Or any apps that will create them?
Click to expand...
Click to collapse
Unfortunately in fastboot mode this gives some crappy Chinese text.......so I reverted back.
any way to get the red boot logo but our cyanogenmod animation? I'm wondering if a combo would look sexier.
dmo580 said:
any way to get the red boot logo but our cyanogenmod animation? I'm wondering if a combo would look sexier.
Click to expand...
Click to collapse
Actually I did that. I have red boot logo at the beginning and then it changes to cm animation. What I did? I flashed zip from this OP ColorOs, but it was a crap (sorry mate) so I restored my CM11s from backup in twrp and voila!
So this means we can create custom bootsplash using (probably) the same method that was originally pioneered on the G1? (It also worked on Mytouch & G2)
Sweet!
@graffixnyc
Thanks for your help.
I'm wondering if there's any way for the logo.img flashing to be done as a flashable zip? I ask only because I flash nightlies a lot (CM11) and its hard for me to plug in all the time to do fastboot flash LOGO logo.img when I'm traveling for work like 80% of the time I know first world problems. How to convert the logo.img to a flashable zip?
Also is there any way for logo.img to be modified so the fastboot logo isn't Chinese but rather what it is in stock?
dmo580 said:
@graffixnyc
Thanks for your help.
I'm wondering if there's any way for the logo.img flashing to be done as a flashable zip? I ask only because I flash nightlies a lot (CM11) and its hard for me to plug in all the time to do fastboot flash LOGO logo.img when I'm traveling for work like 80% of the time I know first world problems. How to convert the logo.img to a flashable zip?
Also is there any way for logo.img to be modified so the fastboot logo isn't Chinese but rather what it is in stock?
Click to expand...
Click to collapse
I don't know exactly how you do it, but I know you can make a flashable zip run a normal shell script. In this shell script you can dd the image to the proper partition... it's a bit sketchier though IMO..
Why do you need to re-flash? The logo partition isn't affected by flashing nighties. It should stick around between flashes.
nolsen311 said:
Why do you need to re-flash? The logo partition isn't affected by flashing nighties. It should stick around between flashes.
Click to expand...
Click to collapse
No the logo is changed to the white boot logo after flashing nightlies.
The splash or the boot animation? The splash should be unaffected.
nolsen311 said:
The splash or the boot animation? The splash should be unaffected.
Click to expand...
Click to collapse
The splash. I've done this fastboot flash logo logo.img many times and it works, but once I flash the next CM11 Nightly, its gone. I have to keep doing this everytime, meaning I need to do it on a specific computer. Kinda annoying.
The animation isn't too hard to replace, although I'm wondering if CM's init.d scripts can help preserve the file.
dmo580 said:
... I'm wondering if CM's init.d scripts can help preserve the file.
Click to expand...
Click to collapse
There used to be a place you could stash it on removable media that would be picked up instead of the stock system bootanimation.
Anyone know if that still works?
Well, the partition where the splash screen is known. It's possible to make a .zip that we can flash with every nightly. Personally, I'm too scared to experiment with that. That partition is related to the bootloader, so it's very possible to brick our OPOs with a .zip to flash the splash screen after every nightly. Honestly, I'm just fine with having to reboot into the bootloader to flash the splash screen after every flash.
nolsen311 said:
There used to be a place you could stash it on removable media that would be picked up instead of the stock system bootanimation.
Anyone know if that still works?
Click to expand...
Click to collapse
\data\local\
It depends on the ROM you're using though.
Typically works with all AOSP roms.
However, I've found that bootanimations don't seem to run fully with the OPO phone for some odd reason.
It's like the animation runs once, doesn't loop and then the screen goes dark until the phone boots up completely.
YMMv
Any chance to get the original, out of the box CM splash screen here from the One Plus one? Want to use it on another phone.
Thanks in advice
Logo works.
Bootanimation and rebootanimation don't @CM 11 Nightly from 09/24/2014. Any idea?
Ausgelebt said:
Logo works.
Bootanimation and rebootanimation don't @CM 11 Nightly from 09/24/2014. Any idea?
Click to expand...
Click to collapse
goto system/media and check permissions make sure they r rw-r-r
Hi Guys, I'll show you how to change the BootLogo/Splash Screen with new Google logo and how to change bootanimation with the 6p one.
First you must be rooted and must have a custom recovery.
Download the logo from here(thanks to Droidphilev!):
http://forum.xda-developers.com/attachment.php?attachmentid=3512671&d=1445324260
And the bootanimation:
https://drive.google.com/open?id=0B7V8PjYQw8kVR3dObXR2c0RSSkU
1. Flash the bootlogo in the recovery(if your bootloader is unlocked don't worry if you don't see the icon at the bottom)
2. It's highly recommended to use total commander for the next step: https://play.google.com/store/apps/details?id=com.ghisler.android.TotalCommander
3. Grab the new bootanimation.zip file and paste it in system/media (delete the old bootanimation.zip file) and set the permissions to 644.
4. Reboot and enjoy!
###############EDIT###############
Just flash this: http://forum.xda-developers.com/attachment.php?attachmentid=3733883&d=1461883901 thanks to @misterpyrrhuloxia
Thanks works perfect on Android N
cyberbandit1998 said:
Thanks works perfect on Android N
Click to expand...
Click to collapse
Are you rooted on android N? How did you do the root?
PHH superuser
xda-unknown-developer said:
Are you rooted on android N? How did you do the root?
Click to expand...
Click to collapse
https://superuser.phh.me/nexus/shamu/NPC56P/boot-shamu-NPC56P-su-nocrypt-r191.img
Wipe data if you already in N and download PHH Superuser in playstore
max_mitsu said:
https://superuser.phh.me/nexus/shamu/NPC56P/boot-shamu-NPC56P-su-nocrypt-r191.img
Wipe data if you already in N and download PHH Superuser in playstore
Click to expand...
Click to collapse
What if I'm encrypted and I want to stay encripted?
Use chainfire root
xda-unknown-developer said:
What if I'm encrypted and I want to stay encripted?
Click to expand...
Click to collapse
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726
Why are you posting the bootloader logo here? You didn't even took the time to rename my file but didn't leave credits? Not so nice!
I made this on the 20th of october last year. I checked your file and it's indeed the one that i made.
http://forum.xda-developers.com/showpost.php?p=63391339&postcount=68
I remember that!
Droidphilev said:
Why are you posting the bootloader logo here? You didn't even took the time to rename my file but didn't leave credits? Not so nice!
I made this on the 20th of october last year. I checked your file and it's indeed the one that i made.
http://forum.xda-developers.com/showpost.php?p=63391339&postcount=68
Click to expand...
Click to collapse
Edited!
It worked!! Thank you!! Will this continue to work on later bootloader updates? Because whenever a new version of the shamu bootloader is released, I flash that. I just want to make sure that this will still be compatible with every bootloader version moving forward.
misterpyrrhuloxia said:
It worked!! Thank you!! Will this continue to work on later bootloader updates? Because whenever a new version of the shamu bootloader is released, I flash that. I just want to make sure that this will still be compatible with every bootloader version moving forward.
Click to expand...
Click to collapse
You are welcome I don't know,but it should work. Let me know
So I made a flashable zip combining both of these. I took the flashable zip from the OP, opened it up, and added the bootanimation.zip to it. It flashes the boot splash then backs up your current /system/media/bootanimation.zip to /sdcard/bootanimation.zip. So now you have one file to flash for both the boot splash image and the new boot animation.
Hit thanks!
misterpyrrhuloxia said:
So I made a flashable zip combining both of these. I took the flashable zip from the OP, opened it up, and added the bootanimation.zip to it. It flashes the boot splash then backs up your current /system/media/bootanimation.zip to /sdcard/bootanimation.zip. So now you have one file to flash for both the boot splash image and the new boot animation.
Hit thanks!
Click to expand...
Click to collapse
Thank you for all the people involved. It worked you flash BTW. Tested on Nexus 6 RR
misterpyrrhuloxia said:
So I made a flashable zip combining both of these. I took the flashable zip from the OP, opened it up, and added the bootanimation.zip to it. It flashes the boot splash then backs up your current /system/media/bootanimation.zip to /sdcard/bootanimation.zip. So now you have one file to flash for both the boot splash image and the new boot animation.
Hit thanks!
Click to expand...
Click to collapse
You are great!
misterpyrrhuloxia said:
It worked!! Thank you!! Will this continue to work on later bootloader updates?
Click to expand...
Click to collapse
yes
---------- Post added at 21:14 ---------- Previous post was at 21:12 ----------
misterpyrrhuloxia said:
So I made a flashable zip combining both of these. I took the flashable zip from the OP, opened it up, and added the bootanimation.zip to it. It flashes the boot splash then backs up your current /system/media/bootanimation.zip to /sdcard/bootanimation.zip. So now you have one file to flash for both the boot splash image and the new boot animation.
Hit thanks!
Click to expand...
Click to collapse
Why did you combine this? What if a rom uses some other type of bootanimation and flashing fails?
Droidphilev said:
yes
---------- Post added at 21:14 ---------- Previous post was at 21:12 ----------
Why did you combine this? What if a rom uses some other type of bootanimation and flashing fails?
Click to expand...
Click to collapse
Then I guess that they could just flash the zip from the OP and place the bootanimation.zip manually.
misterpyrrhuloxia said:
Then I guess that they could just flash the zip from the OP and place the bootanimation.zip manually.
Click to expand...
Click to collapse
Please keep in mind that i'm not responsible if flashing my logo.bin this way fails!!
Droidphilev said:
Please keep in mind that i'm not responsible if flashing my logo.bin this way fails!!
Click to expand...
Click to collapse
I would hope that you'd say that you're not responsible ever if someone flashes a mod of yours and something goes wrong.
misterpyrrhuloxia said:
I would hope that you'd say that you're not responsible ever if someone flashes a mod of yours and something goes wrong.
Click to expand...
Click to collapse
I'm indeed never responsible. Still i won't help if anyone loses logo.bin this way.
works good. Just curious how do you return to the old splash logo ? Flash factory images via fastboot ?
Is there a way I can remove the logo that it shows when booting up and just play my custom animation right from the start? I'm rooted with TWRP
jdugery said:
Is there a way I can remove the logo that it shows when booting up and just play my custom animation right from the start? I'm rooted with TWRP
Click to expand...
Click to collapse
@jdugery ... Why are you creating this duplicate thread ?? You already created the thread with the self same name on 22nd November 2016 --- Why waste not only your own time but also everyone else's by repeating it --- Grow up :silly:
metpolds said:
@jdugery ... Why are you creating this duplicate thread ?? You already created the thread with the self same name on 22nd November 2016 --- Why waste not only your own time but also everyone else's by repeating it --- Grow up :silly:
Click to expand...
Click to collapse
Because I got no answer saying whether or not it was possible.
jdugery said:
Is there a way I can remove the logo that it shows when booting up and just play my custom animation right from the start? I'm rooted with TWRP
Click to expand...
Click to collapse
Remove it, no. That's what shows when the bootloader is doing its thing before the system boot animation takes over.
Replace it, yes. Lots of custom one posted in this thread: https://forum.xda-developers.com/moto-x-style/themes-apps/automated-boot-logos-moto-x-using-t3276236
If you wanted, it sounds like you could use that "Motorola Boot Logo Maker" mentioned in the OP there to make your own custom logo.bin to transition to your animation more seamlessly. I've never tried it myself.
jason2678 said:
Remove it, no. That's what shows when the bootloader is doing its thing before the system boot animation takes over.
Replace it, yes. Lots of custom one posted in this thread: https://forum.xda-developers.com/moto-x-style/themes-apps/automated-boot-logos-moto-x-using-t3276236
If you wanted, it sounds like you could use that "Motorola Boot Logo Maker" mentioned in the OP there to make your own custom logo.bin to transition to your animation more seamlessly. I've never tried it myself.
Click to expand...
Click to collapse
These are all PNG files. Are there any premade .Bin ones? I am away from home without computer access and was planning to flash with TWRP.
jdugery said:
These are all PNG files. Are there any premade .Bin ones? I am away from home without computer access and was planning to flash with TWRP.
Click to expand...
Click to collapse
Some might be preview images, but I downloaded a few as a test and they're flashable zips of logo.bin. look harder. Most of them are on the third page of that thread.
jason2678 said:
Some might be preview images, but I downloaded a few as a test and they're flashable zips of logo.bin. look harder. Most of them are on the third page of that thread.
Click to expand...
Click to collapse
Do I install under the section logo file or zip file when using flashify?
jdugery said:
Do I install under the section logo file or zip file when using flashify?
Click to expand...
Click to collapse
Follow the directions in the thread. I have not read it very carefully.
In general, what works is, if you end up with a logo.bin then
Code:
fastboot flash logo /path/to/logo.bin
If you extract a zip and it has a logo.bin and a meta-inf folder in it, then it's made to be flashable. Install it with twrp.
I've never used flashify to install a moto logo. Not saying it can't, but I've never done it.
UPDATE: Magendanz posted an awesome version of what I tried to do. Their version doesn't have bad artifacts and noticable pixels, so I'd heavily recommend using their version! It is titled (PixelBootAnimation.E4.zip) in the attachments.
I used the MotoBootLogoMaker to create this TWRP flashable ZIP. This was made for my personal phone, but I wanted to share with others in case they had the same problem. Hope this helps someone!
MrIndieJ said:
I used the MotoBootLogoMaker to create this TWRP flashable ZIP. This was made for my personal phone, but I wanted to share with others in case they had the same problem. Hope this helps someone!
Click to expand...
Click to collapse
what input in moto boot logo maker did you use when making the boot logo?
MarioMasta64 said:
what input in moto boot logo maker did you use when making the boot logo?
Click to expand...
Click to collapse
Can you clarify? I just replaced all the boot images with the one I made.
MrIndieJ said:
Can you clarify? I just replaced all the boot images with the one I made.
Click to expand...
Click to collapse
i figured it out already
MarioMasta64 said:
i figured it out already
Click to expand...
Click to collapse
Ok, good, sorry I wasn't much help ?
MrIndieJ said:
Ok, good, sorry I wasn't much help
Click to expand...
Click to collapse
its fine lol, i opened it up in moto boot logo maker and it imported the settings (shouldve done that first lol)
MrIndieJ said:
I used the MotoBootLogoMaker to create this TWRP flashable ZIP. This was made for my personal phone, but I wanted to share with others in case they had the same problem. Hope this helps someone!
Click to expand...
Click to collapse
Is this the OEM splash from stock? If i have downloaded the stock zip with the recovery and logo.bin and f;ash that logo.bin will i have the same result?
@MrIndieJ
Sorry, the ZIP I have provided is of the splash I have created, not the stock splash.
Here's an update that I pieced together from several sources for the Moto E4/E4+ that installs both the Pixel splash and boot animation. Because of the white background, it masks the N/A nicely.
Might want to try this app: https://play.google.com/store/apps/details?id=com.vegazs.logochanger&hl=en
Looks like it has the stock Moto logo splash.
EDIT: I tried this and was unsuccessful.
I get Black background with white text saying "orange state, your device unlocked......."
No logo image while booting. direct bootanimation
Can anyone provide (or explain how) I can extract the logo and boot animation from the stock rom and apply it?
Sizzlechest said:
Can anyone provide (or explain how) I can extract the logo and boot animation from the stock rom and apply it?
Click to expand...
Click to collapse
I think you'd have to backup your current rom, install the stock rom, backup the boot animation and splash, then restore your original rom and flash the stock boot animation and splash
MrIndieJ said:
I think you'd have to backup your current rom, install the stock rom, backup the boot animation and splash, then restore your original rom and flash the stock boot animation and splash
Click to expand...
Click to collapse
I extracted the bootanimation and bootanimation.zip files and applied them to my Lineage rom (and yes, I also fixed the rights on the files) but it didn't work. The stock rom uses MP4 files for animation. I assume Lineage should support that, but I'm not 100% sure.
Sizzlechest said:
I extracted the bootanimation and bootanimation.zip files and applied them to my Lineage rom (and yes, I also fixed the rights on the files) but it didn't work. The stock rom uses MP4 files for animation. I assume Lineage should support that, but I'm not 100% sure.
Click to expand...
Click to collapse
Mine sucked compared to Magendanz's version. I have flashed theirs and would recommend you check it out. I'll quote his post below.
Magendanz said:
Here's an update that I pieced together from several sources for the Moto E4/E4+ that installs both the Pixel splash and boot animation. Because of the white background, it masks the N/A nicely.
Click to expand...
Click to collapse
MrIndieJ said:
Mine sucked compared to Magendanz's version. I have flashed theirs and would recommend you check it out. I'll quote his post below.
Click to expand...
Click to collapse
Yes, I use the Google boot screen. I extracted the logo.bin and flashed that manually using the appropriate fastboot command so I can keep the original boot animation of Lineage. I'm looking for a more stock experience. I suspect there's something simple I'm missing or Lineage simply can't handle MP4 boot animations.
TWRP from TWRP Builder builded for Nokia 7 Plus....
I still don't know if working (as i write in another thread), so that it does not fit, i write separate thread about it...
Small story:
I unpacked B2N-132E-0-00WW-B07.nb0 using nbd tools, although is not complete unpacked, "B2N-0-132G-00WW-boot.img" is here...
Unpack using unmkbootimg and get kernel(zImage) and ramdisk(ramdisk.cpio.gz)...
In unpacked ramdisk is binary "recovery", "init.recovery.qcom.rc" and "recovery.fstab" which is used/imported by default "init.rc"...
Then i think this is recovery, using TWRP Builder APK installed on N7+ i upload this image...
After some days i receive message that TWRP for Nokia 7 Plus is builded OK
Of course flashing this need Unlocked bootloader, then all who need it, PLEASE do participate in petition about Unlocking bootloader:
https://forum.xda-developers.com/nokia-7-plus/how-to/petition-possibility-to-unlock-t3788953
(after write comment, please also click too on "Do you have this question as well?")
Download: TWRP_onyx_00ww-08051830.img
Won't boot (tried to boot into it via fastboot (I don't want to flash it yet), and it just hanged on the android one text. Maybe going to properly flash it in few days.
Ranpe said:
Won't boot (tried to boot into it via fastboot (I don't want to flash it yet), and it just hanged on the android one text. Maybe going to properly flash it in few days.
Click to expand...
Click to collapse
thanks for testing, flashing is sure not need and not safe, boot via fastboot i think must work(if twrp working)...
anyway if you can boot then you have unlocked bootloader right?
can you try boot via fastboot original in nb0 boot/recovery from twrp is builded? file B2N-0-132G-00WW-boot.img
maybe problem is that this is "hybrid" boot+recovery in one, and is need some hotkey or magic durring boot?
k3dar7 said:
thanks for testing, flashing is sure not need and not safe, boot via fastboot i think must work(if twrp working)...
anyway if you can boot then you have unlocked bootloader right?
can you try boot via fastboot original in nb0 boot/recovery from twrp is builded? file B2N-0-132G-00WW-boot.img
maybe problem is that this is "hybrid" boot+recovery in one, and is need some hotkey or magic durring boot?
Click to expand...
Click to collapse
Yeah, I have unlocked bootloader on my 7+. Looks like the boot.img (which's used in that build of TWRP) is from older rom than the one I'm on at the moment. (B2N-213B-0-00WW-boot.img) May it be the reason for it to not boot? Anyway, I'll try to build a newer version soon.
Ranpe said:
Yeah, I have unlocked bootloader on my 7+. Looks like the boot.img (which's used in that build of TWRP) is from older rom than the one I'm on at the moment. (B2N-213B-0-00WW-boot.img) May it be the reason for it to not boot? Anyway, I'll try to build a newer version soon.
Click to expand...
Click to collapse
How did you get it open? Bootloader
DroiDMester said:
How did you get it open? Bootloader
Click to expand...
Click to collapse
https://forum.xda-developers.com/nokia-6/how-to/guide-how-to-unlock-bootloader-qualcomm-t3769930/
Ranpe said:
Yeah, I have unlocked bootloader on my 7+. Looks like the boot.img (which's used in that build of TWRP) is from older rom than the one I'm on at the moment. (B2N-213B-0-00WW-boot.img) May it be the reason for it to not boot? Anyway, I'll try to build a newer version soon.
Click to expand...
Click to collapse
yes, TWRP in #0 is builded from *boot.img from 8.0, i not find newer version, you have B2N-213B-0-00WW-boot.img ? if yes, then please try upload it via TWRP Builder, i not this do because not have newer file and too not posible to upload more that 1x from one device...
unlocking bootloader you do via NTool?
k3dar7 said:
yes, TWRP in #0 is builded from *boot.img from 8.0, i not find newer version, you have B2N-213B-0-00WW-boot.img ? if yes, then please try upload it via TWRP Builder, i not this do because not have newer file and too not posible to upload more that 1x from one device...
unlocking bootloader you do via NTool?
Click to expand...
Click to collapse
I've submitted the newer boot.img to them already, we'll see if they update it. Yeah, unlocked via ntool (by a guy I know).
Ranpe said:
I've submitted the newer boot.img to them already, we'll see if they update it. Yeah, unlocked via ntool (by a guy I know).
Click to expand...
Click to collapse
strange, i not see it in complete, queue, running or rejected don't show after upload you some error like "for this device is already builded"? i don't know if is posible rebuild for same device model from another device with another/newer boot.img...
I thought too about NTool, but i not find any seller od setool2 credit with small amount of credit (<=10), only 30 and for me message no answer... also authot of NTool write me only "not help you"... then try wait what Nokia do with many question about posibility of unlocking bootloader officialy...
try to get stock recovery img, porting should be easier.
SkaboXD said:
try to get stock recovery img, porting should be easier.
Click to expand...
Click to collapse
as i say in #0 TWRP is builded from srock recovery from 8.0 NB0 for N7p, i think problem is that N7p not use separate recovery but is inside normal boot, then need some magic to switch to recovery part of this "hybrid" boot, and because N7p need to recovery via powering cable and hold VolUp+Power then i think is same need with booting TWRP from #0, but who know if this is possible with not flashed booting via fastboot...
edit: anyway if my thoughts are true, then with hybrid boot+recovery flashed to device, is really need twrp based on exact boot image for current rootfs on device... (as Rampe too say if is possible evoce recovery from image booted via fastboot without flashing, then is not need exact version...
SkaboXD said:
try to get stock recovery img, porting should be easier.
Click to expand...
Click to collapse
The recovery is in the boot.img, and we have the images already.
Ranpe said:
The recovery is in the boot.img, and we have the images already.
Click to expand...
Click to collapse
oh i get it, so you need to make twrp for every Android version because of changed boot.img?
SkaboXD said:
oh i get it, so you need to make twrp for every Android version because of changed boot.img?
Click to expand...
Click to collapse
Not 100% sure of it, but unfortunately it may be so.
SkaboXD said:
oh i get it, so you need to make twrp for every Android version because of changed boot.img?
Click to expand...
Click to collapse
if changed kernel version/config (or binary, script, key in boot.img) then yes... if update use same files in boot.img as previous then no...
if i look at version in Settings/About for 8.1 v2.13 and 8.1 v2.22 then kernel version i same 4.4.78, but builded date is other (17.3. and 20.4.), not know if changes config, source etc, or is only same kernel rebuilded with full build proces again... i not have whole boot.img for 2.13 or 2.22 only for 8.0 v1.23
edit: FW for camera/touch/baseband/nothing not in boot.img (if not compile inside kernel(which i do not expect))
@Ranpe you have boot.img for 2.13 and/or 2.22 ? can you please upload it somewhere?
k3dar7 said:
@Ranpe you have boot.img for 2.13 and/or 2.22 ? can you please upload it somewhere?
Click to expand...
Click to collapse
Yeah, I have the boot.img for 2.13, but not (yet) for 2.22 (Need to get python working properly so I could dump inside of the payload.bin in the new OTA-update). You can download the 2.13 boot.img (and some other stuff) from here.
dotsaredots said:
Yeah, I have the boot.img for 2.13, but not (yet) for 2.22 (Need to get python working properly so I could dump inside of the payload.bin in the new OTA-update). You can download the 2.13 boot.img (and some other stuff) from here.
Click to expand...
Click to collapse
thanks for uploading, i now too have extracted 2.13 using payload_dumper.py (link from here), but for unpack payload.bin from 2.22 i think do not help any python "propertly working" because 2.22 is incremental update and this is not supported by payload_dumper.py...
btw: now i'm sure that N7p have really hybrid recovery_in_boot, what is used for any Phone that use new A/B method of updating on running system and simply switch to new update after reboot...
https://source.android.com/devices/tech/ota/ab/ab_implement
first of all you need to edit recovery.fstab in vendor partion it won`t boot because of encrypted data
The Moto X4 (payton) too has a hybrid recovery and they managed to make twrp. Might contact @mightysween or the official maintainers at twrp for hints?
Broadcasted from Zeta Reticuli
Gravemind2015 said:
The Moto X4 (payton) too has a hybrid recovery and they managed to make twrp. Might contact @mightysween or the official maintainers at twrp for hints?
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
X4, Pixel2 and other A/B devices use a bootable recovery image (fastboot boot twrp.img) and then install a .ZIP package that patches the boot.img with TWRP recovery.
There have been other issues on the various devices with encryption, with bootcontrol partition switching, and with handling of empty "B" partitions. So proceed with caution, especially with flashing roms from TWRP before you have a way to populate the B partition.