Hey, I've done some reading up around here, and I'm looking to change my boot logo (Boot logo. Not the animation). So far, it doesn't look like anyone other than the developer of Logo Me has any method to do so.
From what I understand, "fastboot flash logo.bin logo.bin" doesn't work as it does on most other devices.
Now, I'm no professional, but I've got some of what many don't have: time and dedication.
It boils down to this: To change the boot logo, I'd need (1) a way to get the boot.img off of the phone, (2) a way to reliably edit the boot.img without corrupting it or messing with the format, (3) a way to figure out which file is the boot logo, and (4) a way to get the modified boot.img back onto the phone (again without messing it up in the process).
I'm fairly sure (4) is solved with "fastboot flash boot.img boot.img", but the others, not so easily dismissed.
When I make a nandroid backup in TWRP, the boot backup is an 8MB "boot.emmc.win". I'm fairly sure that this might be of some use, even if it's only for opening and exploring the contents of the partition.
I'm not sure if anybody has any remarkable leads that they've kept to themselves, but I'd figure this would be a good place to start.
Boot.img = ramdisk+kernel
Nothing to do with boot splash
sent from my i9250
the image that youre looking for is somehow connected to the bootloader. so far only ezekeel has figured out a way to do it safely. key word is safely. it appears as its very easy to brick the device if a mistake is made. now, that said, ezekeel isnt your ordinary app developer. hes also one of the smartest, most creative kernel developers that the android has(that doesnt work for google). youve probably even used one of his many kernel mods in one or more custom roms/kernels that youve tried, across varying devices.
Re: Custom boot splash?
Deleted
Re: Custom boot splash?
Deleted
Related
Hi all,
I'm new to trying to root the E4GT and I've gotten in a bit of a jam. I don't think I'm completely borked because I can still easily get the phone into download mode or Clockwork recovery, but I'm stuck on what to do next and I want to proceed carefully so I don't accidentally turn this into a hard brick.
Because I'm on Linux, not Windows, after reading up on rooting the E4GT I installed heimdall. It's not the most intuitive program in the world but I eventually worked out rooting it using "heimdall flash --kernel ~/path/to/zImage" where the "zImage" in question belonged to Zedomax v3 as linked from epic4gtouchroot.com. That seemed to work brilliantly as I was able to boot into what appeared to be a reset phone, now with a generic Android boot animation rather than the default Sprint advert, and I had the Superuser app.
From there, I decided to try Strongsteve's Odex blue and I booted into Clockwork. Without even thinking about it I wiped the factory data and cache partition, and then started looking into what I needed to do, only to learn that my external SD was going to be inaccessible from here so I had the .zip file in the wrong place. I proceeded to reboot my phone to set things right but I was shocked when the phone simply appeared to turn off after the (new, rooted) boot animation played. The phone then becomes unresponsive until the battery is pulled, at which point it becomes responsive again.
Because it boots the Samsung logo (with the yellow warning triangle) and part of the boot animation, I have plenty of time to get it into download mode or Clockwork, but I don't know what my next move is. I guess (based on a bad experience with trying to root a Kindle Fire) that this is still recoverable, though. Should I just flash a stock/stock rooted ROM? Reflashing the Zedomax kernel doesn't seem to work like it did before. Has anyone encountered this? Does anyone have a link to a recovery method that should be reliable in this situation? Thanks in advance and please remember LINUX -- i.e., no Odin.
[[ PS - I pretty much described the whole process above, but in case anyone was wondering, let me explicitly state I do not have a working nandroid backup. I only got Clockwork after rooting successfully, and I didn't think wipe data/cache was potentially a brick! :\ ]]
UPDATE: Solved! I was able to successfully flash the zImage from the stock rooted kernel here. Phone is working (and rooted) once again!
i just installed cm-10-20120802-UNOFFICIAL-primou.zip on an HTC One V and now it fails to boot.
from what i've seen in other threads and through my own experience, these devices are particularly fussy when it comes to boot.img files... either they don't push out properly during updates or they require manual teasing, etc etc.
there were one or two articles online which mention a special jbboot.img file that someone had created and if any of the links worked, i'd gladly push that onto my device.
i have tried pulling the boot.img out of the zip mentioned above and flashing it to my device using fastboot. that did not work.
does anyone have a link to the proper boot partition image?
i may be on target to fix this myself...
grabbing a HELLBOY kernel here...
http://www.mediafire.com/?lo2ctaplonbdh
... as mentioned in threads like this one here...
http://forum.xda-developers.com/showthread.php?t=2101726
http://forum.xda-developers.com/showthread.php?t=1954967
http://forum.xda-developers.com/showthread.php?t=2105616
ah... positive developments.
after flashing boot-HELLBOY-CM10-201212251747.img i am seeing Android booting. strangely, however, it is a CM9 boot animation, but i flashed a CM10 rom. weird! now i get to figure THAT part out.
EDIT: aaaaaaannnnd... stuck at the android boot animation. again, i have NO IDEA why this is a CM9 animation, but that's neither here nor there. i'm more than willing to entertain anyone's notion as to what could be holding up the boot process now.
yes, after installing cm-10-20120802-UNOFFICIAL-primou.zip i did a wipe of all userdata as well as cache and dalvik cache.
i went back into my recovery environment (i use TWRP and have become a total fan of that, but i'm sure that working in ClockworkMod would be just about the same result) and performed another full wipe: data, caches, even system.
then i re-installed the cm-10-20120802-UNOFFICIAL-primou.zip rom and rebooted.
now the phone will stay stuck at the HTC logo. should i try re-flashing the boot image again? i'll take a whack at that.
EDIT: boot-HELLBOY-CM10-201212251747.img flashed. again with the CM9 boot animation and failure to fully boot into an android environment. ugh.
well, if this device wants so badly to run CM9 (the whole boot animation is a mystery to me) i'm going to just let it.
i've wiped yet again, and then flashed CM9PrimoUB3.zip and then used fastboot to push boot-HELLBOY-CM9-201212251747.img onto the device.
i'm at the android boot animation (CM9 animation, of course) and seemingly stuck there. what a goddamn pain in the ass.
EDIT: well, after a LOOOONG boot animation process, it appears that the Android O/S has started. praise jeebus and pass the beer.
EDIT 2: looks like the pDroid patch process was successful, and the phone is booting much faster now, too.
B3 sh!t that's old...... where did you find that? Also seeing your from america im going to assume you have a CDMA device not a GSM device, you should be flashing PRIMOC rom's not PRIMOU if this is the case.
Hello there,
So recently Ive been doing lots of crazy/funny stuff with my phone like testing different ROM and boot images. I'm trying to do things as secure as possible, reading lots of threads before attempting things and trying to make sanity checks on procedures I read here on XDA. Despite of that, Im still unsecure about some principles:
For what I got, on the process of phone booting from power ON, it all starts at boot ROM. Boot ROM then calls the bootloader. At this point I have the first question: These custom boot images we use to upload to phone are the bootloader, right? So, considering we are not touching boot ROM (at least its what I supose as I never saw any reference on how to change boot ROM), if I use fastboot and upload a wrong or bad boot image I will be able to restore another boot image. I mean, theres no danger of definetely bricking my phone while playing with boot images as boot ROM remains untouched?
When I use flashtool to upload ftf images it will flash everything, including the bootloader, right? Again, if I use a wrong/bad ftf file the Boot ROM remains untouched, so no danger of definetely bricking my phone?
Im tempted to test some Cyanogem fork for Xperia M (among other stuff) but need/want to have this sort of questions sorted out first.
Should I post such newb questionsl ike this in here or in the development section of forum?
Any clues?
Thanks
Sorry to be of no help(mostly because I dislike theory and like practice), but changing the bootloader using flash isn't possible because, at least I, have flashed 4.3 without unlocking bootloader.
About what part of XDA this should go on, it's probably the general discussion of XDA.
DanDare_77 said:
Hello there,
So recently Ive been doing lots of crazy/funny stuff with my phone like testing different ROM and boot images. I'm trying to do things as secure as possible, reading lots of threads before attempting things and trying to make sanity checks on procedures I read here on XDA. Despite of that, Im still unsecure about some principles:
For what I got, on the process of phone booting from power ON, it all starts at boot ROM. Boot ROM then calls the bootloader. At this point I have the first question: These custom boot images we use to upload to phone are the bootloader, right? So, considering we are not touching boot ROM (at least its what I supose as I never saw any reference on how to change boot ROM), if I use fastboot and upload a wrong or bad boot image I will be able to restore another boot image. I mean, theres no danger of definetely bricking my phone while playing with boot images as boot ROM remains untouched?
When I use flashtool to upload ftf images it will flash everything, including the bootloader, right? Again, if I use a wrong/bad ftf file the Boot ROM remains untouched, so no danger of definetely bricking my phone?
Im tempted to test some Cyanogem fork for Xperia M (among other stuff) but need/want to have this sort of questions sorted out first.
Should I post such newb questionsl ike this in here or in the development section of forum?
Any clues?
Thanks
Click to expand...
Click to collapse
if u mean kernel as boot img....and rom as boot rom...
then answer is...u will get hardbrick....
kernel is most important to run a device...it should have correct hardware files or else urs will be gone[more than 80% to end up on hardbrick...]...
and in boot rom[rom or system files] only libs,etc are important ...libs has ur hardware related files to make work correctly and etc has some permissions,bluetooth files,ur partition info,etc[all only for ur phones for hardware]...if u place other device libs,etc u may get hardbrick or hardware wont work as usual....app,fonts,framework can be placed from any but it wont let you boot unless u know how to port...
Hi everyone
After some research, I can't find a succeful way to install TWRP recovery instead of Lineage stock recovery.
It's really embarasing because I'm currently setting up my brand new XZ2c compact to run the way I want it to on Lineage OS 17.1 with Magisk and Xposed modules, and I experienced 3 or 4 endless bootloop that led me to fully format my phone after bunch of hours setting it and tailoring it up... Huge waste of time, frustration overload, as you could expect. So, I really miss tremendous TWRP backup fonctionnality I used to run frequently on my old Z5c... :crying:
Does anyone here as figured out how to replace Lineage stock recovery on this device? Is so, I'd really to hear him out
Have a good week-end!
tomboudiboudi said:
Hi everyone
After some research, I can't find a succeful way to install TWRP recovery instead of Lineage stock recovery.
It's really embarasing because I'm currently setting up my brand new XZ2c compact to run the way I want it to on Lineage OS 17.1 with Magisk and Xposed modules, and I experienced 3 or 4 endless bootloop that led me to fully format my phone after bunch of hours setting it and tailoring it up... Huge waste of time, frustration overload, as you could expect. So, I really miss tremendous TWRP backup fonctionnality I used to run frequently on my old Z5c... :crying:
Does anyone here as figured out how to replace Lineage stock recovery on this device? Is so, I'd really to hear him out
Have a good week-end!
Click to expand...
Click to collapse
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
kurtn said:
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
Click to expand...
Click to collapse
Thanks for replying!
Ok, but if I want this recovery bootable permently away from my computer?
kurtn said:
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
Click to expand...
Click to collapse
Thanks for your (minimalist) advice. Literally just lost 1 hour fixing the bootloop it just caused by following it, I'm delighted.
Behind my post, I was hoping to find someone who could explain a bit more the process of replacing/flashing/booting/(wateveryouwanti'mnotanexpert) a recovery, and at the same time avoiding me wasting more hours in bootlooping/formating/reinstalling. Hopefully, this time I succeed to came out of the bootloop without formating and reseting eveything, but I almost lost my nerves.
All of this is a bit cloudy for me, could you (or someone else that would give me a little of his time to) be pedagogue and explain clearly the whole proccess (and especially what you should avoid if you don't want to get stuck in a bootloop/getting scarying corrupted device message) ?
No one?
tomboudiboudi said:
No one?
Click to expand...
Click to collapse
Wrong forum. Search in you device section.
Hi guys!
Today I tried again to install TWRP on my Sonyh Xperia XZ2C because LineageOS Recovery doesn't provide Nandroid backup, which is a shame.
I tried many ways described over the web, none of those worked, and I ended up with a boot loop at startup with that naughty message "your device is corrupted it cannot be trusted and will not boot". I can't boot to Lineage, neither to recovery. I'm stuck.
With device turned off, I can eventually press volume down, plug it to computer, access fastboot mode (blue led), flash+boot the LineageOSrecovery.img, then the device restart, Sony logo appears... and that's all, I'm stuck with logo in boot loop, and I can't go anywhere further.
I tried to change boot slot (without knowing if it could help with this problem at all) but I alway get "unknown option".
I'm panicking right now, I can't find any way out to this bootloop, if someone could help it will be sooo appreciated!
I tried hard to find a solution for 4 hours now, I'm completly stuck and I can't even sleep. That's why I finally reached out here.
tomboudiboudi said:
Hi guys!
Today I tried again to install TWRP on my Sonyh Xperia XZ2C because LineageOS Recovery doesn't provide Nandroid backup, which is a shame.
I tried many ways described over the web, none of those worked, and I ended up with a boot loop at startup with that naughty message "your device is corrupted it cannot be trusted and will not boot". I can't boot to Lineage, neither to recovery. I'm stuck.
With device turned off, I can eventually press volume down, plug it to computer, access fastboot mode (blue led), flash+boot the LineageOSrecovery.img, then the device restart, Sony logo appears... and that's all, I'm stuck with logo in boot loop, and I can't go anywhere further.
I tried to change boot slot (without knowing if it could help with this problem at all) but I alway get "unknown option".
I'm panicking right now, I can't find any way out to this bootloop, if someone could help it will be sooo appreciated!
I tried hard to find a solution for 4 hours now, I'm completly stuck and I can't even sleep. That's why I finally reached out here.
Click to expand...
Click to collapse
In fastboot mode you should be able to flash stock rom
Is there any way to make the device boot on the Lineage partition without wiping everything?
For an unknown reason, I succed to boot on Lineage Recovery (not TWRP) this morning. I flashed LineageOs rom.zip using adb sideload. After rebooting, the recovery tolds me that I had to wipe everything because the system partition seems to be corrupted, so I did.
I'm a bit tired to lost everything since I made all of this to do Nandroid backups with TWRP........ but I have a fresh new install, my phone works again so it's fine.
But I still need to make Nandroid backups.
Kurtn, you seem to have skills and knowledge. As you can see, I didn't succeed to boot Twrp since october 2020. I don't see why it would be impossible with my device, I'm probably messing something somewhere.
Would you share your knowledge and help me booting/flashing TWRP without bricking everything again?
Could you make an answer instead of a single smiley?
tomboudiboudi said:
Could you make an answer instead of a single smiley?
Click to expand...
Click to collapse
Sorry, i cant. I don't backup and I don't have an a/b device.
Ok, thanks anyway!
tomboudiboudi said:
I didn't succeed to boot Twrp since october 2020. I don't see why it would be impossible with my device, I'm probably messing something somewhere.
Would you share your knowledge and help me booting/flashing TWRP without bricking everything again?
Click to expand...
Click to collapse
Btw.
Code:
fastboot flash boot recovery.img
DOES install the recovery, since it's permanently flashed. Don't know why they (lineage) didn't change that.
kurtn said:
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
Click to expand...
Click to collapse
However @tomboudiboudi , you could boot twrp manually using
Code:
fastboot boot twrp.img
With that, twrp should appear and ask for a password to decrypt your userdata partition.
If that works, you could try to flash boot this very same twrp.img. Maybe you need an additional twrp.zip too which will be sideloaded within twrp itself.
A note for you which might help: I wanted to update my lineage recovery manually using fastboot (older lineage recovery to newer one) and found that nothing (except fastboot) was booting at all after flashing this.
However, after dirty flashing lineageOS.zip, everything worked fine again.
Keep in mind that flashing a recovery will modify your boot.img. If this one doesn't work / is corrupt etc., your os won't boot up.
User699 said:
Btw.
Code:
fastboot flash boot recovery.img
DOES install the recovery, since it's permanently flashed. Don't know why they (lineage) didn't change that.
However @tomboudiboudi , you could boot twrp manually using
Code:
fastboot boot twrp.img
With that, twrp should appear and ask for a password to decrypt your userdata partition.
If that works, you could try to flash boot this very same twrp.img. Maybe you need an additional twrp.zip too which will be sideloaded within twrp itself.
A note for you which might help: I wanted to update my lineage recovery manually using fastboot (older lineage recovery to newer one) and found that nothing (except fastboot) was booting at all after flashing this.
However, after dirty flashing lineageOS.zip, everything worked fine again.
Keep in mind that flashing a recovery will modify your boot.img. If this one doesn't work / is corrupt etc., your os won't boot up.
Click to expand...
Click to collapse
I fear you still haven't realized, what a/b means. The classic concept of having a recovery partition, where you can boot twrp at any time - doesn't apply.
kurtn said:
I fear you still haven't realized, what a/b means. The classic concept of having a recovery partition, where you can boot twrp at any time - doesn't apply.
Click to expand...
Click to collapse
You're right, there is no recovery partition.
As I said: Flashing a recovery.img will modify the boot.img.
Howdy all, hadn't done rooting/etc in a long time as my past several phones didn't have much support for them but got the LG G8 and was excited to possibly root it and also install a custom rom. Went with Arrow OS which seemed to run fine and I decided I wanted to get TWRP as a custom recovery instead of the one that comes with ARROW OS. I flashed it but now it get stuck on fastboot and constantly loops to it (and no longer shows the boot a/b.... which probably isn't a good sign). After leaving it alone for some time, I booted it up and now it gets beyond the the fastboot loop but I can either try to boot it up which only gets me the code red warning or go to download mode. I tried to use LG Bridge and download mode on my phone but the Bridge software doesn't detect the phone.
I realize some of this is probably because of my stupidity and I should've been more careful but anyone got any ideas on what could be done to get the phone back to a stable working state so that it can function again? I know there are some more "difficulties" because of the boot a/b partitions and having to handle that stuff properly. If it isn't possible, that sucks I guess but anyone who wants to chime in - thank you for your help!
JuSkoch said:
Howdy all, hadn't done rooting/etc in a long time as my past several phones didn't have much support for them but got the LG G8 and was excited to possibly root it and also install a custom rom. Went with Arrow OS which seemed to run fine and I decided I wanted to get TWRP as a custom recovery instead of the one that comes with ARROW OS. I flashed it but now it get stuck on fastboot and constantly loops to it (and no longer shows the boot a/b.... which probably isn't a good sign). After leaving it alone for some time, I booted it up and now it gets beyond the the fastboot loop but I can either try to boot it up which only gets me the code red warning or go to download mode. I tried to use LG Bridge and download mode on my phone but the Bridge software doesn't detect the phone.
I realize some of this is probably because of my stupidity and I should've been more careful but anyone got any ideas on what could be done to get the phone back to a stable working state so that it can function again? I know there are some more "difficulties" because of the boot a/b partitions and having to handle that stuff properly. If it isn't possible, that sucks I guess but anyone who wants to chime in - thank you for your help!
Click to expand...
Click to collapse
Sounds like you might just need to reverse what you did to try to get twrp. If you have the boot partition for Arrow flash that back, if you don't have it should be pretty easy to get it from someone.
If that doesn't work can always use qfil and flash the necessary partitions to get LGUP to work, then flash or crossflash to a kdz and start again with stock.
You're in good company. I went down the same path and have become adept at repeatedly bricking and un-bricking my G8. (LM-G820QM5) I picked up 2 tidbits of info that have been helpful. The first is that my G8 ThinQ will not boot Android when the engineering abl_a.bin has been flashed on to it to enable fastboot. Sure it will fastboot, and go into EDL or download mode, but in order to boot the OS, I have to put the normal abl_a.bin and abl_b.bin back.
The second lesson I learned the hard way is that sometime LGUP fails to flash when the phone is in download mode. I was searching around XDA and came across a very helpful post from starlyn1232. They posted a command line utility that has been successful in un-bricking my G8 when LGUP failed.
I downloaded the appropriate kdz from lg-firmwares.com and the starlyn1232's utility from https://forum.xda-developers.com/t/lgup-flash-utility-based-on-lgup-1-16-cmd-and-lgup-1-17-lgup_common-dll.4112121/
Well thankfully, i still had the original files from the unlocking thread in this forum and I also apparently did make a backup of my files right before I installed TWRP 3.4 or whatever and was able to get my phone working again - which is awesome! Also, what's the best way to back up everything on the phone (or at least the essentials) in case of flashing situations like this? I in the past would just use TWRP to do a backup/restore but since I flashed ARROWOS and it has its own recovery and doesn't seem to have a backup option - asking if any one has a recommendation. Thanks!
JuSkoch said:
Well thankfully, i still had the original files from the unlocking thread in this forum and I also apparently did make a backup of my files right before I installed TWRP 3.4 or whatever and was able to get my phone working again - which is awesome! Also, what's the best way to back up everything on the phone (or at least the essentials) in case of flashing situations like this? I in the past would just use TWRP to do a backup/restore but since I flashed ARROWOS and it has its own recovery and doesn't seem to have a backup option - asking if any one has a recommendation. Thanks!
Click to expand...
Click to collapse
I would highly recommend looking at bkerler edl utilities. You can easily find his git page which has the download option for an iso linux boot which has everything installed.
It's a bit involved / complicated figuring out the command line interface, but once done you can backup everything and it will create the xml files needed to reload it.
I would suggest this for everyone but especially for those with sprint or att devices, as there is no kdz available for them.
I've recovered from various issues too many times to count with backups I've made for v40, v35, and now G8 (2 of them).
cheers
Could you pass the tutorial on how to install TWRP?
Does anyone have rawprogram0.xml
Patch0.xml for lg g8
Ashfaq Ahmed spsc said:
Does anyone have rawprogram0.xml
Patch0.xml for lg g8
Click to expand...
Click to collapse
So the rawprogram xml will be for ea lun, and it will vary by which rom you're trying to flash, it will also vary by segment starting positions for the partitions. IE, there is no generic version of it.
2nd, you don't need a patch xml, just click cancel or skip for that entry. Note; the rawprogram xml is usually generated when a backup of the binaries is made, and it will be for that specific backup.
Hello there sorry to pop in unannounced I would like to interject briefly and please pardon my ignorance I'm still a noob.
I have a similar issue, but I'm a little bit confused as to what I should do. In my Case i have a SOFT brick.
(G8 ThinQ VERIZON LM-G820UM (Model) ---- G820UM20j (Software)).
I unlocked the bootloader and rooted with magisk successfully, Still running STOCK OS
Then I Flashed TWRP.zip and some version of Magisk.zip with the magisk app, Then I Rebooted to Recovery.
Inside TWRP i Wiped, Format and then I flashed Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
This process Finished without any errors, however, after I rebooted i now cannot go past the Verizon Logo and it's stuck there.
Fortunately, I have All the Original files backed up (abl_a.bin, abl_b.bin, boot_a.bin, boot_b.bin)
And TWRP also managed to create a Backup beforehand.
I can go easily into EDL mode and i also have the engineering abl_a file on hand.
i can also get to the built-in Stock factory reset / safe mode but I'm unsure if I should use it.
So my question is if i would be correct in loading ALL of the original Files using QFIL, or only the boot_a boot_b files ?
or if i should do something else like getting the firmware in my case?
thank you for your time in advance.
MR_ZenR0 said:
Hello there sorry to pop in unannounced I would like to interject briefly and please pardon my ignorance I'm still a noob.
I have a similar issue, but I'm a little bit confused as to what I should do. In my Case i have a SOFT brick.
(G8 ThinQ VERIZON LM-G820UM (Model) ---- G820UM20j (Software)).
I unlocked the bootloader and rooted with magisk successfully, Still running STOCK OS
Then I Flashed TWRP.zip and some version of Magisk.zip with the magisk app, Then I Rebooted to Recovery.
Inside TWRP i Wiped, Format and then I flashed Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
This process Finished without any errors, however, after I rebooted i now cannot go past the Verizon Logo and it's stuck there.
Fortunately, I have All the Original files backed up (abl_a.bin, abl_b.bin, boot_a.bin, boot_b.bin)
And TWRP also managed to create a Backup beforehand.
I can go easily into EDL mode and i also have the engineering abl_a file on hand.
i can also get to the built-in Stock factory reset / safe mode but I'm unsure if I should use it.
So my question is if i would be correct in loading ALL of the original Files using QFIL, or only the boot_a boot_b files ?
or if i should do something else like getting the firmware in my case?
thank you for your time in advance.
Click to expand...
Click to collapse
Hello, I Managed to Fix it by loading my backed-up original boot_a.bin and boot_b.bin using QFIL, I have successfully passed that Verizon logo now and should be able to go from here, not that anybody asked, I just thought someone in the future might have some use out of this information here. so if you are from the future and you read this, you are welcome and good luck