Database Info

Splashscreen Trouble

I was able to change my splashscreen once, but changing it again doesn't seem to work. I place the PD98IMG.zip in the root of my SD card, overwriting the previous, and when I boot into bootloader I just see something come up like "parsing PD98IMG.zip" and it just finishes without giving me the option to volume up or down to actually change/load the new PD98IMG.zip file. Any ideas?
1.
I've tried deleting it completely/loading new file and I still have the same splashscreen.

Are you rooted? I've seen this behavior when S-ON is still active

Symmetric said:
Are you rooted? I've seen this behavior when S-ON is still active
Click to expand...
Click to collapse
Yes, I am rooted.
Sent from my Inspire 4G using XDA App

When you put the file in the PD98IMG.zip, did you unzip and then re-zip? If so, you should just open the zip file with 7zip/winrar/whatever so you can see inside, and then just paste your .img file inside. Then close it.
Other than that, we need more details. What process exactly are you doing. Are you creating your own .img with nbimg, or using someone else's already made .img

I am using some one else's .img file (mainly from the splashscreen emporium post) and I just move the file from my download folder to the root of my sdcard and click OK to overwrite with root explorer. I havent tried zipping and unzipping yet on the computer, but ill let you know if it works.

what i meant was don't unzip/rezip. Just browse the zip file and drop your .img in it. But since you're going with someone else's zip, i have no idea where the problem could be.
if you really want the splash screen, have a look at this thread http://forum.xda-developers.com/showthread.php?t=1059520
it's more difficult than just grabbing someone else's, but it's honestly not too bad, especially since he gives step-by-step instructions

zip or un-zipped

Can anybody tell me if the AT&T file is zipped or unizipped...trying to see why the link wont show up when i download it http://forum.xda-developers.com/showthread.php?t=1342348

Despite the fact that the link says: Download Stock TAR for SGH-I727, what you will actually download is in 7z format. Once you open that you will find a .tar file. Once you open that, you will find the boot, recovery and system .img files. People love to complicate things.

when i try to open the file it comes up as being blank...nothing is even there
ok i see my problem now...what is a program to open the 7z format file???

Do you have a utility which will open 7z files?
http://www.7-zip.org/
I downloaded both the AT&T and Rodgers files a while back and seem to recall it took over 15 minutes for each of them despite they're only being about 250m. You may have corrupt files.

ok i didnt have the utility...thanks bro i am noob just did my first root 3 days ago and the custom rom im running keeps force closing...trying to get rid of it and return it to stock rom
what is the process of extracting the tar file to odin???

8BallDa8Dawg said:
ok i didnt have the utility...thanks bro i am noob just did my first root 3 days ago and the custom rom im running keeps force closing...trying to get rid of it and return it to stock rom
Click to expand...
Click to collapse
Did you make a nandroid backup? Have you tried fixing permissions? Just curious. If you made a nandroid backup before you flashed your new rom, just restore the backup. Always always always make a nandroid before you flash.
Sent from my SAMSUNG-SGH-I727 using xda premium

naw i didnt bro...i did back up most of my stuff to titanium back up though..would dat matter

8BallDa8Dawg said:
naw i didnt bro...i did back up most of my stuff to titanium back up though..would dat matter
Click to expand...
Click to collapse
honestly, you have some reading to do, but from the initial sounds of it, you either:
A. restored apps you shouldnt have with Titanium Backup after flashing your new rom (only use RESTORE MISSING APPS WITH DATA, NEVER EVER USE RESTORE ALL APPS OR RESTORE SYSTEM ANYTHING)
or you:
B. didnt wipe data/factory reset in CWM before flashing the new rom
best option right now would be to boot to recovery and wipe data/factory reset, then boot back into your rom and see if you get FCs....

i restored all of my apps that were missing on my phone...didnt restore anything else. i just want to return my rom back to its original state and i didnt back it up when i used cwm. the rom that am using is Sky Ice Cream sandwhich and im having problems wit force closes

8BallDa8Dawg said:
i restored all of my apps that were missing on my phone...didnt restore anything else. i just want to return my rom back to its original state and i didnt back it up when i used cwm. the rom that am using is Sky Ice Cream sandwhich and im having problems wit force closes
Click to expand...
Click to collapse
if you want to go back to stock, then you need to fire up ODIN as admin, put the stock tar file in the pda slot, put phone in download mode and hit start

The problem im having wit dat is puting the stock rom into the PDA...the tar file is not recognized in the PDA...i downloaded the utility to extract the tar file from the 7z file but im stuck from there...assistance please??

8BallDa8Dawg said:
The problem im having wit dat is puting the stock rom into the PDA...the tar file is not recognized in the PDA...i downloaded the utility to extract the tar file from the 7z file but im stuck from there...assistance please??
Click to expand...
Click to collapse
open 7z file with 7zip. drag the tar file out to your desktop
open ODIN as admin
click on the PDA button
point it to your desktop where the tar file is
select the tar file and click start
its not complicated....dont really understand what the issue is

when i open the the files in 7zip they will not move to the desktop as a Tar file...they go as three seperate files

8BallDa8Dawg said:
when i open the the files in 7zip they will not move to the desktop as a Tar file...they go as three seperate files
Click to expand...
Click to collapse
inside the 7z file is ONE, count them, ONE .tar file. DO NOT EXTRACT THE FILES INSIDE THE .TAR file....
sounds to me like you are opening the 7z, then opening the .tar within 7zip
try this. right click on the 7z file, 7-zip, EXTRACT HERE, assuming you are somewhere simple, like your desktop. it should spit out ONE .tar file

HELP!!!! BOOTLOOP atrix 2

im stuck in a loopboot on my ME865 after installing 4.2.2 from this http://forum.xda-developers.com/showthread.php?t=2121029
i flashed the rom but didnt flash the gapps because it said to do it after with built in recovery but i didnt know how to so i used this http://forum.xda-developers.com/showthread.php?t=1346977
which got me into the loop boot i can boot into fastmode
PLEASE HELP ME!!!!!!

DaFrenchTaco said:
im stuck in a loopboot on my ME865 after installing 4.2.2 from this http://forum.xda-developers.com/showthread.php?t=2121029
i flashed the rom but didnt flash the gapps because it said to do it after with built in recovery but i didnt know how to so i used this http://forum.xda-developers.com/showthread.php?t=1346977
which got me into the loop boot i can boot into fastmode
PLEASE HELP ME!!!!!!
Click to expand...
Click to collapse
Well, first, turn off the phone and charge it so you don't loose battery.
Second, never install another recovery on top of an existing one without knowing what you are doing - ask first.. (You get into the built-in recovery on that cm10.1 by tapping the volume down button at the end of the red moto logo when the lights come on).
Next, you could possibly fix your system with adb and switching some files.. but that would take a lot of explaining if you are not familiar with it.. plus, you might not get adb recognized during the bootloop.
So, you need to use the FXZ files for your phone/region... Or, just flash the system.img only.. See here: http://forum.xda-developers.com/showpost.php?p=41436876&postcount=1106 - and see the link linked there.
EDIT: If you can get adb recognized, you might be able to just run these few lines to fix things from the command prompt:
Code:
adb shell
su
mount -o rw,remount /system
rm /system/bin/hijack
sh /system/bin/finalize_release
exit

alteredlikeness said:
Well, first, turn off the phone and charge it so you don't loose battery.
Second, never install another recovery on top of an existing one without knowing what you are doing - ask first.. (You get into the built-in recovery on that cm10.1 by tapping the volume down button at the end of the red moto logo when the lights come on).
Next, you could possibly fix your system with adb and switching some files.. but that would take a lot of explaining if you are not familiar with it.. plus, you might not get adb recognized during the bootloop.
So, you need to use the FXZ files for your phone/region... Or, just flash the system.img only.. See here: http://forum.xda-developers.com/showpost.php?p=41436876&postcount=1106 - and see the link linked there.
EDIT: If you can get adb recognized, you might be able to just run these few lines to fix things from the command prompt:
Code:
adb shell
su
mount -o rw,remount /system
rm /system/bin/hijack
sh /system/bin/finalize_release
exit
Click to expand...
Click to collapse
do you know any other place to download the zip file
and wheres the fxz folder supposed to be

DaFrenchTaco said:
do you know any other place to download the zip file
and wheres the fxz folder supposed to be
Click to expand...
Click to collapse
Look here
http://forum.xda-developers.com/showthread.php?t=2176124
Make sure you install the correct firmware otherwise you will brick.
And next time please search before posting. This has been asked a number of times before
Sent from my MB865 using XDA Premium HD app

nikhJ said:
Look here
http://forum.xda-developers.com/showthread.php?t=2176124
Make sure you install the correct firmware otherwise you will brick.
And next time please search before posting. This has been asked a number of times before
Sent from my MB865 using XDA Premium HD app
Click to expand...
Click to collapse
No. Those are only MB865. And those are only for gingerbread..
The 4.0.4 ME865 ones are here: http://forum.xda-developers.com/showthread.php?t=1934874
Also, it's a little outdated, but see here too: http://forum.xda-developers.com/showthread.php?t=1909319
Which should all lead you here: http://sbf.droid-developers.org/edison/list.php
Sent from my manta ray

alteredlikeness said:
No. Those are only MB865. And those are only for gingerbread..
The 4.0.4 ME865 ones are here: http://forum.xda-developers.com/showthread.php?t=1934874
Also, it's a little outdated, but see here too: http://forum.xda-developers.com/showthread.php?t=1909319
Which should all lead you here: http://sbf.droid-developers.org/edison/list.php
Sent from my manta ray
Click to expand...
Click to collapse
sorry for asking u so much stuff but i lost without help
ok so it says i have to edit it with the moto android depacker but i dont see any tutorials on how to do that
would it boot up if i use this hack to install the honk kong boot img on to it or would mess my device since its on "4.2.2." http://forum.xda-developers.com/showthread.php?p=35000737

DaFrenchTaco said:
sorry for asking u so much stuff but i lost without help
ok so it says i have to edit it with the moto android depacker but i dont see any tutorials on how to do that
would it boot up if i use this hack to install the honk kong boot img on to it or would mess my device since its on "4.2.2." http://forum.xda-developers.com/showthread.php?p=35000737
Click to expand...
Click to collapse
I am very confused at what you want to do. That link is only to root your device. But, if you are bootlooping, you need to replace your system.img.
You should download the entire SBF/FXZ zip file for your device/region/firmware. Then unzip it into a folder on your computer (best if it's close to C:\ with spaces in the path). Are you using a Windows OS on your computer?
Then, grab the restore-to-ics_win-batch.zip AND the restore-ics-system-only.bat.txt (remove the .txt extension) attached in this post: http://forum.xda-developers.com/showpost.php?p=36834775&postcount=108
Mix those files in with the big FXZ files that you just unzipped. Then run the .bat file to flash the system.img only. If that doesn't work, then open the other .bat file (use Notepadd++ or similar), check that everything that is being flashed is actually in your folder and has the same name... and flash the entire FXZ. If none of that helped, then you probably flashed the wrong files to your phone.
Just flashing the system.img only is probably the safest.. Because if it's wrong, you can just flash another one. The other files in the FXZ package can mess up your phone if they are not for your specific device.
EDIT: If you still did not flash anything else, you could try to use adb... Get that restore-to-ics_win-batch.zip that I linked above.. Unzip it to your desktop. Power on your phone so it bootloops and connect with USB. Open a command prompt on the restore-to-ics_win-batch folder by holding down shift and right-click. Then type adb devices - if it returns a number with the word "device" (not the word "offline"), then you can try to use those adb codes I posted in my previous post. Otherwisem you need to use fastboot and flash fxz or system only.

alteredlikeness said:
I am very confused at what you want to do. That link is only to root your device. But, if you are bootlooping, you need to replace your system.img.
You should download the entire SBF/FXZ zip file for your device/region/firmware. Then unzip it into a folder on your computer (best if it's close to C:\ with spaces in the path). Are you using a Windows OS on your computer?
Then, grab the restore-to-ics_win-batch.zip AND the restore-ics-system-only.bat.txt (remove the .txt extension) attached in this post: http://forum.xda-developers.com/showpost.php?p=36834775&postcount=108
Mix those files in with the big FXZ files that you just unzipped. Then run the .bat file to flash the system.img only. If that doesn't work, then open the other .bat file (use Notepadd++ or similar), check that everything that is being flashed is actually in your folder and has the same name... and flash the entire FXZ. If none of that helped, then you probably flashed the wrong files to your phone.
Just flashing the system.img only is probably the safest.. Because if it's wrong, you can just flash another one. The other files in the FXZ package can mess up your phone if they are not for your specific device.
EDIT: If you still did not flash anything else, you could try to use adb... Get that restore-to-ics_win-batch.zip that I linked above.. Unzip it to your desktop. Power on your phone so it bootloops and connect with USB. Open a command prompt on the restore-to-ics_win-batch folder by holding down shift and right-click. Then type adb devices - if it returns a number with the word "device" (not the word "offline"), then you can try to use those adb codes I posted in my previous post. Otherwisem you need to use fastboot and flash fxz or system only.
Click to expand...
Click to collapse
can not load "system.img" i went in and edited the the text to C:\system.img but it wont work
i tried the other one didnt work is the path supposed to be = C... or =C... what i mean is there a space or not
is the bat file scripted to work with me865 or only with mb865 flashing that sbf/fxz
and is the sbf/fxz file supposed to be unzipped and in a folder
or compressed

DaFrenchTaco said:
can not load "system.img" i went in and edited the the text to C:\system.img but it wont work
i tried the other one didnt work is the path supposed to be = C... or =C... what i mean is there a space or not
is the bat file scripted to work with me865 or only with mb865 flashing that sbf/fxz
and is the sbf/fxz file supposed to be unzipped and in a folder
or compressed
Click to expand...
Click to collapse
Unzip the sbf/fxz - all the files in a single folder, on your desktop or in the root of your C:\ drive (like C:\ InlineFlashing_Edison_XX-XX-XX_CFC_P3_APBP.xml - where that is the name of the folder)
Then put the .bat file and other files from my restore_to_ics zip and the restore_system_only .bat in that same folder.
Then, connect with USB while in AP fastboot mode, see if it says "OK to program", then double-click the restore-ics-system-only.bat

alteredlikeness said:
Unzip the sbf/fxz - all the files in a single folder, on your desktop or in the root of your C:\ drive (like C:\ InlineFlashing_Edison_XX-XX-XX_CFC_P3_APBP.xml - where that is the name of the folder)
Then put the .bat file and other files from my restore_to_ics zip and the restore_system_only .bat in that same folder.
Then, connect with USB while in AP fastboot mode, see if it says "OK to program", then double-click the restore-ics-system-only.bat
Click to expand...
Click to collapse
thank u so much is it safe to root and install cm10 with bootstrap?
and how do you enter cmw in cm10.1?
THX

Sorry to intrude with my following off-topic statement, but that was a lot of detailing you did there altered. xD Great job and it'll serve well to assist others who need the same solution.
Now on-topic;
Yes it's okay to root with any of the ICS root methods available.
Sent from the Ace's MB865 using xda app-developers app

Aceofzeroz said:
Sorry to intrude with my following off-topic statement, but that was a lot of detailing you did there altered. xD Great job and it'll serve well to assist others who need the same solution.
Now on-topic;
Yes it's okay to root with any of the ICS root methods available.
Sent from the Ace's MB865 using xda app-developers app
Click to expand...
Click to collapse
yeah true that this is a very detailed guide/thread i hope my problem will help all the others now that i know how it feels to mess up a two day old phone

alteredlikeness said:
No. Those are only MB865. And those are only for gingerbread..
The 4.0.4 ME865 ones are here: http://forum.xda-developers.com/showthread.php?t=1934874
Also, it's a little outdated, but see here too: http://forum.xda-developers.com/showthread.php?t=1909319
Which should all lead you here: http://sbf.droid-developers.org/edison/list.php
Sent from my manta ray
Click to expand...
Click to collapse
Ah..sorry my bad..Forgot his phone was me865..

Question about the original problem
DaFrenchTaco said:
im stuck in a loopboot on my ME865 after installing 4.2.2 from this http://forum.xda-developers.com/showthread.php?t=2121029
i flashed the rom but didnt flash the gapps because it said to do it after with built in recovery but i didnt know how to so i used this http://forum.xda-developers.com/showthread.php?t=1346977
which got me into the loop boot i can boot into fastmode
PLEASE HELP ME!!!!!!
Click to expand...
Click to collapse
Did you solve this? I have the same problem...
---------- Post added at 10:17 PM ---------- Previous post was at 10:01 PM ----------
alteredlikeness said:
No. Those are only MB865. And those are only for gingerbread..
The 4.0.4 ME865 ones are here: http://forum.xda-developers.com/showthread.php?t=1934874
Also, it's a little outdated, but see here too: http://forum.xda-developers.com/showthread.php?t=1909319
Which should all lead you here: http://sbf.droid-developers.org/edison/list.php
Sent from my manta ray
Click to expand...
Click to collapse
I encounter the same issue. I am not able to see the device in ADB.exe, but I am able to see in FASTBOOT.exe
Can I flash in FASTBOOT.exe?
Thank you

pa 3.60 problem from altered likeness
I tried to install Paranoid android 3+ from the link from altered likeness which was successful but the problem started after rebooting .The animation goes on forever and the first time the reboot gave me a message stating updating android system . Any solution to get back would be of a lot of help .I also have the recovery of my stock 4.0.4 done using CWM .

Same problem extension
Hi....
I faced the same problem and now after following the procedure facing a new prob.
Things I did
1. Upgraded from ICS to CM10.1--->Success
2. Forgot to install GAPPS ..so installed Atrix2Strap.apk (Bootloop problem started)
3. Flashed my atrix 2 with the procedure mentioned in the link by alteredlikeness.(Overcame the bootloop problem)
Now the problem is
I'm getting the lock screen but when I try to unlock it stays unresponsive.
How do I solve this. Please Help me out

Thnks guys
kyashwanth said:
Hi....
I faced the same problem and now after following the procedure facing a new prob.
Things I did
1. Upgraded from ICS to CM10.1--->Success
2. Forgot to install GAPPS ..so installed Atrix2Strap.apk (Bootloop problem started)
3. Flashed my atrix 2 with the procedure mentioned in the link by alteredlikeness.(Overcame the bootloop problem)
Now the problem is
I'm getting the lock screen but when I try to unlock it stays unresponsive.
How do I solve this. Please Help me out
Click to expand...
Click to collapse
Thanks guys for the wonderful tutorial...
Solved the issue by inserting a sim card into the phone.
Now I'm on CM 10.1

[Q] Boot animation freeze

So I changed the boot animation to something different. The animation is so heavy the phone lags halfway in between and now my phone can't even get past the boot animation screen. It's stuck at the boot animation. Anyway to revert this?

Download the default boot animation from here: http://forum.xda-developers.com/google-nexus-5/themes-apps/bootanimation-nexus-5-animations-t2789918
Scroll down a bit and you'll find the default Lollipop animation. Download the zip which is supposed to be manually installed.
Put it in system/media/bootanimation.zip
You can use Aroma File Manager for this. AromaFM is a flashable zip which brings up a file manager in your recovery

experience7 said:
Download the default boot animation from here: http://forum.xda-developers.com/google-nexus-5/themes-apps/bootanimation-nexus-5-animations-t2789918
Scroll down a bit and you'll find the default Lollipop animation. Download the zip which is supposed to be manually installed.
Put it in system/media/bootanimation.zip
You can use Aroma File Manager for this. AromaFM is a flashable zip which brings up a file manager in your recovery
Click to expand...
Click to collapse
I can't even access my phone's storage so how am I suppose to use the zip? Are you saying I can flash the zip file while the phone is in fastboot/recovery?

If you're using TWRP as a recovery you can access your storage. It does support MTP.
Yeah, the file manager has to be flashed just like a ROM.

experience7 said:
If you're using TWRP as a recovery you can access your storage. It does support MTP.
Yeah, the file manager has to be flashed just like a ROM.
Click to expand...
Click to collapse
And that's the problem. I'm running a stock rom (4.4.2) with no TWRP or CWM.
The phone is rooted and the boot-loader is unlocked.

Bootloader unlocked. So where's the problem?
Download latest TWRP and execute
fastboot flash recovery twrp.img
to flash it.
Or simply
fastboot boot twrp.img
to launch it once. You don't even need to flash it.

experience7 said:
Bootloader unlocked. So where's the problem?
Download latest TWRP and execute
fastboot flash recovery twrp.img
to flash it.
Or simply
fastboot boot twrp.img
to launch it once. You don't even need to flash it.
Click to expand...
Click to collapse
AYEEEEE!!! I see where you're going with this now. I think I get it now. I'll try tonight or maybe in a couple of hours and then I'll come back if any problems. Once finished I'll let you know with a thanks

By the way: After copying the new (default lollipop) bootanimation.zip to /system/media do a 'fix permissions' in TWRP. Not quite sure if the option is available in TWRP but if it is, just do it. It won't do any harm

Alright I flashed TWRP and it's working but the file manager kinda sucks. I mean it's picking up the files and their aren't any options to copy and paste. The boot animation is stored in /system/media and when I go into the system folder all I see is "bin" and nothing else. I don't understand what's the problem

Man, the file manager does not suck. A little more respect to the developer! You should be thankful, not disrespectful!
Enable hidden files in the file manager and you'll see them. And it also does provide copy/paste functionality. I've used it several times.
EDIT: If you still don't see them after enabling hidden files you have to mount the system partition.

experience7 said:
Man, the file manager does not suck. A little more respect to the developer!
Enable hidden files in the file manager and you'll see them. And it also does provide copy/paste functionality. I've used it several times.
Click to expand...
Click to collapse
I searched everywhere and I don't see an option to enable hidden files. How did you enable hidden files?

It's in the lower right corner if I remember correctly. Three dots which will bring up a menu.

...

experience7 said:
It's in the lower right corner if I remember correctly. Three dots which will bring up a menu.
Click to expand...
Click to collapse
What version of TWRP are you using? I don't see three dots anywhere. The bottom always has a back button on the right, a button to launch terminal in the center and a home button on the left

Dude. It has nothing to do with TWRP version at all. You didn't even launch Aroma File Manager... that's the point.
Read my previous posts again, take your time & don't double post (there's an option to edit if you have to).

experience7 said:
Dude. It has nothing to do with TWRP version at all. You didn't even launch Aroma File Manager... that's the point.
Read my previous posts again, take your time & don't double post (there's an option to edit if you have to).
Click to expand...
Click to collapse
Sorry for being impatient.
Do I flash Aroma the same way I flashed TWRP? If so will this cause any problems or anything? TWRP can't install Aroma from SD because my computer won't even pick up my phone

If you're in TWRP, connect your phone to your computer. It should be detected just like any Android phone since it's also using MTP.
Aroma File Manager has to be flashed in TWRP (install zip). That's why you had to flash TWRP in the first place.

experience7 said:
If you're in TWRP, connect your phone to your computer. It should be detected just like any Android phone since it's also using MTP.
Aroma File Manager has to be flashed in TWRP (install zip). That's why you had to flash TWRP in the first place.
Click to expand...
Click to collapse
Better yet as soon as I connected my phone to my PC, TWRP's file manager started working. I deleted the corrupted bootanimation.zip that made my phone lag in the first place. However it keeps failing to move the other bootanimation.zip into /system/media (I backed up the stock boot in /system/media by renaming it
EDIT: Never-mind I got it. I renamed the file from 0bootanimation.zip to "android" and then to bootanimation.zip
I restarted my phone and it's just stuck in the boot loop. The animation is occurring forever and nevermind it just started.
Thank you experience7!!! Massive vouch for you man. You saved me so much trouble. Much love from me =D

As said before... TWRP uses MTP to enable file transfer between your computer and your phone. However, you'll only see your internal storage (pictures, videos and stuff like that) - not the system partition. That's why you should use Aroma File Manager! It lets you access the system partition directly on the phone and provides everything you need (copy/paste/delete and so on).
I have no idea what file you actually deleted. But I'm pretty sure it was not the one in /system/media.

experience7 said:
As said before... TWRP uses MTP to enable file transfer between your computer and your phone. However, you'll only see your internal storage (pictures, videos and stuff like that) - not the system partition. That's why you should use Aroma File Manager! It lets you access the system partition directly on the phone and provides everything you need (copy/paste/delete and so on).
I have no idea what file you actually deleted. But I'm pretty sure it was not the one in /system/media.
Click to expand...
Click to collapse
And that's the most weird part of all...
1) TWRP file manager started working as soon as I connected my phone to my PC. I didn't need to flash AromaFM. TWRP worked like a charm
2) I deleted the laggy bootanimation.zip and replaced it with the stock one I backed up. I backed up the stock animation by renaming it to a different file. However TWRP always failed to rename the stock animation to bootanimation.zip. So I renamed it entirely different (to android) and then back to bootanimation.zip and it worked like a charm.
Does that make sense now? I don't know what the hell just happened but I ain't complaining

right magisk patched boot.img file?

After grabbing the boot image matching my current version, patched with magisk, I am told by 2 different tutorials, one in this forum and one on youtube, quote: "Open a terminal in the directory your patched boot img file is and type 'fastboot flash boot magisk_patched.img".
No Problem, both tutorials instruct to type fastboot flash boot magisk_patched.img. My worry is that my file is labeled "magisk_patched-22100_xlAUj" as opposed to just "magisk_patched.img".
I assume I either did something wrong, or the file names have changed since the instructionals. Wanted to make sure before rooting with this patched file since I only have a very surface understanding of what I'm doing, and don't want to brick my phone.
FYI I did try the suggested 'fastboot flash boot magisk_patched.img' command but obviously didn't worry I assume because the file names are different.

I don't know what you already did, but if you can locate where you are along in this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
It worked for me if you follow the steps as described.

the file name basically doesn't matter. as long as what you type into terminal matches what magisk gave you, you're fine. to be more specific to your case: since your file is called magisk_patched-22100_xlAUj.img, your terminal command has to be fastboot flash boot magisk_patched-22100_xlAUj.img. to explain further: what you're doing is that you're telling the program fastboot that it's supposed to flash (copy) a specific file to the boot partition on your phone. that specific file here is the one magisk created (magisk_patched-22100_xlAUj.img).
another solution would be to rename magisk_patched-22100_xlAUj.img to magisk_patched.img

Hey thanks so much, just wanted to make sure before I went through went it. However, I am getting a "disc image file is corrupted" message after hitting enter. I transferred the file by just drag and drop onto my pc. Couldn't get the adb pull command to work.
I even re-patched the boot img via magisk and retried, still getting same message. Every thing I'm doing appears to line up with the youtube tutorial. Would this be a case where I would try canary magisk build instead to patch? Or maybe I should make a new thread....

huh, that certainly is odd. no idea why that would happen. which version of magisk are you using and where did you get the boot.img?

Used this guide https://forum.xda-developers.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/
Got the boot.img from here https://developers.google.com/android/images?hl=en#sunfish (made triple sure it matched my current version)
Using Magisk 22.1 patched file in beta mode as instructed

i'm not sure is this is going to work, but here's a boot.img i patched. it's version sunfish-rq2a.210405.005-factory-ab0ba039. maybe try it, see if it works. just to cover my own ass: i'm not responsible if anything goes wrong. anyhow, it's probably a good idea to familiarise yourself with how to restore your phone to factory before flashing anything and keep a backup of the stock boot.img somewhere.

THEGAZINGVOID said:
i'm not sure is this is going to work, but here's a boot.img i patched. it's version sunfish-rq2a.210405.005-factory-ab0ba039. maybe try it, see if it works. just to cover my own ass: i'm not responsible if anything goes wrong. anyhow, it's probably a good idea to familiarise yourself with how to restore your phone to factory before flashing anything and keep a backup of the stock boot.img somewhere.
Click to expand...
Click to collapse
Is the patched image a 0b file? This is happened to me before too. The work around I do is to rename the boot image to something like boot_april.img before patching it in Magisk. Then check to make sure that the patched image isn't a zero byte file before copying it to your PC and flashing in fastboot.

breacherman said:
Hey thanks so much, just wanted to make sure before I went through went it. However, I am getting a "disc image file is corrupted" message after hitting enter. I transferred the file by just drag and drop onto my pc. Couldn't get the adb pull command to work.
I even re-patched the boot img via magisk and retried, still getting same message. Every thing I'm doing appears to line up with the youtube tutorial. Would this be a case where I would try canary magisk build instead to patch? Or maybe I should make a new thread....
Click to expand...
Click to collapse
See post above this one.

THEGAZINGVOID said:
i'm not sure is this is going to work, but here's a boot.img i patched. it's version sunfish-rq2a.210405.005-factory-ab0ba039. maybe try it, see if it works. just to cover my own ass: i'm not responsible if anything goes wrong. anyhow, it's probably a good idea to familiarise yourself with how to restore your phone to factory before flashing anything and keep a backup of the stock boot.img somewhere.
Click to expand...
Click to collapse
Ok, thanks, I might try that, but I'm not sure atm how to backup this stock rom without twrp.

buffal0b1ll said:
Is the patched image a 0b file? This is happened to me before too. The work around I do is to rename the boot image to something like boot_april.img before patching it in Magisk. Then check to make sure that the patched image isn't a zero byte file before copying it to your PC and flashing in fastboot.
Click to expand...
Click to collapse
Thanks for your suggestion but no, it's about 65mb in size.

breacherman said:
Ok, thanks, I might try that, but I'm not sure atm how to backup this stock rom without twrp.
Click to expand...
Click to collapse
I actually tried magisk canary build to patch the boot.img, and it failed, like before at first, I tried a second time to get a screeshot, and it worked for some reason.

You can follow this ↑↑↑ It's worked.