Related
Greetings,
after restoring back up from official TWRP the device soft-bricked like our friend here
https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112
the device won't even boot to fastboot from hardware button but from adb on recovery mode which hang on twrp logo screen.
what I saw on log is that /system partition structure need cleaning (and can not be mounted)
my backup contains all partition.
so my steps to restore the backup
boot to recovery
from PC into CMD "adb reboot bootloader"
wait until boot to bootloader (fastboot)
boot temporary into twrp "fastboot boot twrp.img" make sure you have twrp img
restore all partition except /system
then restore /system alone
reboot to system
everything's works like charm
I know it seems hideous but this is how I fix it ( and I can confirm I've done it twice)
:good:
UPDATED:
After some testing the problem only occurs when i take back up for all partitions which isn't mandatory, but when i take back for (system, boot, data) which is enough for working backup and the restoring process is flawless
I did not disable security (PIN code) and restoring was successful
Short answer:
Only take backup for data, system, boot
R1skNt said:
Greetings,
after restoring back up from official TWRP the device soft-bricked like our friend here
https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112
the device won't even boot to fastboot from hardware button but from adb on recovery mode which hang on twrp logo screen.
what I saw on log is that /system partition structure need cleaning (and can not be mounted)
my backup contains all partition.
so my steps to restore the backup
boot to recovery
from PC into CMD "adb reboot bootloader"
wait until boot to bootloader (fastboot)
boot temporary into twrp "fastboot boot twrp.img" make sure you have twrp img
restore all partition except /system
then restore /system alone
reboot to system
everything's works like charm
I know it seems hideous but this is how I fix it ( and I can confirm I've done it twice)
:good:
Click to expand...
Click to collapse
Sounds great, but it doesn't work for me. I posted the following comment in another thread:
----------------------------------
I'm having the same problem. I simply cannot restore a TWRP backup. It always produces an error 255.
No, I do not have any "999" folder/files, nor do I have any lockscreen security. I also do not have parallel apps or anything involving multi-user.
I'm extremely experienced at flashing ROMs, as well as performing Nandroids and restoring them.
Nothing I've done is working. As I said, I simply cannot restore the data partition. That's when I get the 255 error. System restores fine, but that's it.
Any ideas?
----------------------------------
Thank you,
Peter
R1skNt said:
Greetings,
after restoring back up from official TWRP the device soft-bricked like our friend here
https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112
the device won't even boot to fastboot from hardware button but from adb on recovery mode which hang on twrp logo screen.
what I saw on log is that /system partition structure need cleaning (and can not be mounted)
my backup contains all partition.
so my steps to restore the backup
boot to recovery
from PC into CMD "adb reboot bootloader"
wait until boot to bootloader (fastboot)
boot temporary into twrp "fastboot boot twrp.img" make sure you have twrp img
restore all partition except /system
then restore /system alone
reboot to system
everything's works like charm
I know it seems hideous but this is how I fix it ( and I can confirm I've done it twice)
:good:
Click to expand...
Click to collapse
What about security? Did you have to disable all security before the backup?
I did not disable security (PIN code) and restoring was successful.
R1skNt said:
I did not disable security (PIN code) and restoring was successful.
Click to expand...
Click to collapse
These are the backup settings that I am using. Can you please tell me if you use the same, or if not please share the ones you are using.
lollyjay said:
These are the backup settings that I am using. Can you please tell me if you use the same, or if not please share the ones you are using.
Click to expand...
Click to collapse
Please see the 1st post (update)
PeterGuru said:
Sounds great, but it doesn't work for me. I posted the following comment in another thread:
----------------------------------
I'm having the same problem. I simply cannot restore a TWRP backup. It always produces an error 255.
No, I do not have any "999" folder/files, nor do I have any lockscreen security. I also do not have parallel apps or anything involving multi-user.
I'm extremely experienced at flashing ROMs, as well as performing Nandroids and restoring them.
Nothing I've done is working. As I said, I simply cannot restore the data partition. That's when I get the 255 error. System restores fine, but that's it.
Any ideas?
----------------------------------
Thank you,
Peter
Click to expand...
Click to collapse
For what it's worth, I think I found a solution to why I couldn't restore the data partition. I can't explain why, but now it's working.
Previously, and historically, whenever I did a restore, I always wiped my device: system, data, boot.
This time; however, I did not wipe the device. I simply did the restore and everything worked. Therefore, the problem is somehow associated with the wipe.
Peter
I did a nanroid backup (boot, system, data only as per the instructions) of 5.1.8, rooted with magisk 16.6, ROM, installed lineage OS, than restored my backed up OOS ROM the restore process completed successfully but got stuck on boot logo, flashed magisk again along with the custom kernel but all to no joy, keeps bootlooping, however lineage restored fine and booted, any help be much appreciated, cheers.
joemossjr said:
You guys are crazy and I feel I need to answer your questions. So here we go. So just becuase there's multiple partitions doesn't mean you can dual boot or set up other things. So the way it works is the userdata partition is one partition. There are 2 system partitions for seamless updates two boot partitions for seamless and two firmware slots. In theory yes you can have two roms on both slots. Will they work? No. They will both use the same userdata partitions. So it will be incompatible.now you could in theory have lineage on one slot and oos on the other and if you ever want to go back just format userdata and fastboot --set-active=other to get to the other slot. But that doesn't really seem like a good idea. If you guys have other questions feel free to ask me!
Click to expand...
Click to collapse
This is from another thread here, my understanding is you have to format userdata partition, but please read it by self.
Bonito77 said:
This is from another thread here, my understanding is you have to format userdata partition, but please read it by self.
Click to expand...
Click to collapse
totally irrelevant to this thread, cheers.
"fastboot boot twrp.img
cannot load 'twrp.img': No such file or directory"
What is wrong?
bannannn said:
"fastboot boot twrp.img
cannot load 'twrp.img': No such file or directory"
What is wrong?
Click to expand...
Click to collapse
I assume you're in the directory twrp.img is in and are using the img file instead of the zip file? Also you renamed the img file to twrp.img?
after 6 hours of head banging . i stumbled across this thread. and i got my renovate backup. Since new to oneplus 6 have shifted from samsung S9+. The first post correctly resolved my headache. I have learned.
1. Only Backup sytem , data, boot other partitions of twrp restore needed. not need to restore others
2. Had to format the internal storage as it become fully corrupted with lot of folders with strange names
3. Had to re install full OOS rom zip then boot into sytem
4. reflash twrp via fastboot, install twrp offical .img from twrp.
5 NO WIPES( I think wiping system and then restoring vendor and other partitions was creating issues)
6 Only Restoring Boot , System, Data. and then straight away booting back phone to system worked perfect. didnt require to flash magisk
thanks a lot for this thread OP. :good:
i am an experienced flasher. but i guess to comeback to oxygen OS from other roms you have to install stock full OOS Rom again.
kingwicked said:
after 6 hours of head banging . i stumbled across this thread. and i got my renovate backup. Since new to oneplus 6 have shifted from samsung S9+. The first post correctly resolved my headache. I have learned.
1. Only Backup sytem , data, boot other partitions of twrp restore needed. not need to restore others
2. Had to format the internal storage as it become fully corrupted with lot of folders with strange names
3. Had to re install full OOS rom zip then boot into sytem
4. reflash twrp via fastboot, install twrp offical .img from twrp.
5 NO WIPES( I think wiping system and then restoring vendor and other partitions was creating issues)
6 Only Restoring Boot , System, Data. and then straight away booting back phone to system worked perfect. didnt require to flash magisk
thanks a lot for this thread OP. :good:
i am an experienced flasher. but i guess to comeback to oxygen OS from other roms you have to install stock full OOS Rom again.
Click to expand...
Click to collapse
I followed your guide. But I'm stuck at the boot animation...
RheinPirat said:
I followed your guide. But I'm stuck at the boot animation...
Click to expand...
Click to collapse
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
kingwicked said:
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
Click to expand...
Click to collapse
I was on 9.0.2
I restored the phone with the MSM tool and updated the ROM to 9.0.2 via manual system update like before.
Question:
Is it not possible to restore the whole system? Or only Data like you said under point 8?
Do I need verity? Because I think my phone is encrypted (flashed never a verity file)
Could I restore the whole system from a full TWRP (all partitions included) - only select data, system?
restoring system and other never worked for me. always failed. but only restoring data partition always worked
when you restore only data. your all apps. settings messages everything will restore even magisk modules.
im not sure about encrypted because. encrypted phone when restoring twrp messed up my whole internal memory. and i had no choice but to wipe it.
so there is no issue with no verity. as it helps not to scramble the internal memory of your device and you wull not loose any data or get stuck on qualcomm dump mode
but remember the steps to verity when installed on already used rom with data. you have to format data to remove encryption
only restoring data is the best option. you can try without no verity to restore i think may work but follow all options i mentioned
but i dont recommend to use with no verity.since using no verity i have never got to wipe my internal memory
I've bricked my device twice after trying to restore and always resorted to just a clean flash of stock using the MSMDownloadTool... wish I'd found this thread sooner as you just solved my third backup restore soft-brick!
I'll also remember to just backup system/data/boot going forward...
Thanks!
kingwicked said:
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
Click to expand...
Click to collapse
Thanks buddy, It worked like a charm.
About the pin removal, as you siad there is a good tutorial in below link which can be used.
https://www.howtogeek.com/240657/how-to-fix-pin-errors-after-restoring-from-twrp-android-backups/
Thank you!!!
You saved my phone (and life).
I can confirm your procedure is working with my back up made on 10.3.2 using a usb c key.
I just restored the DATA. Nothing else!
Thank you so much!
kingwicked said:
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
Click to expand...
Click to collapse
So I did what I thought was a routine thing, trying to restore system, boot, and data like I have on many phones before only to ended up in a bootloop or bootloader only not even able to boot a TWRP from fastboot.
After several hours of trying just about everything I finally faced the fact that I was not going to be able to restore any NANDROID backup I had do to A/B, encryption or the latest Android security patch?
However, you can get you phone running again quite easily with this thread: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 and using the flash-all option from a WIndows 10 VM (I am a Mac/Linux guy, but this does work from a Windows VM and is quick).
Before I re-installed anything I wanted to just verify that I could do a simple NANDROID backup of an empty phone with twrp / blu_spark and I can't under any case. Here's what I tried (with latest stock TWRP and latest Blu_Spark TWRP):
1) simple restore of data, system, boot -- > boots only to fastboot, need to recover with thread above
2) Recover with thread above, re-root (Magisk 18.1) and reinstall TWRP, boot ROM, then try restoring just data -- > same as #1
3) Recover using thread above, re-install TWRP, restore NANDROID, and re-run Magisk (suggest by a few) --> same as #1
My device is encrypted, and I could turn off encryption, but that is somewhat scary on a daily driver.
So has anyone successfully restored a NANDROID on a 9.0.4 rooted phone with the latest Android security patch and if so, what's the trick?
Thanks,
MW
MetroWestMA said:
So I did what I thought was a routine thing, trying to restore system, boot, and data like I have on many phones before only to ended up in a bootloop or bootloader only not even able to boot a TWRP from fastboot.
After several hours of trying just about everything I finally faced the fact that I was not going to be able to restore any NANDROID backup I had do to A/B, encryption or the latest Android security patch?
However, you can get you phone running again quite easily with this thread: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 and using the flash-all option from a WIndows 10 VM (I am a Mac/Linux guy, but this does work from a Windows VM and is quick).
Before I re-installed anything I wanted to just verify that I could do a simple NANDROID backup of an empty phone with twrp / blu_spark and I can't under any case. Here's what I tried (with latest stock TWRP and latest Blu_Spark TWRP):
1) simple restore of data, system, boot -- > boots only to fastboot, need to recover with thread above
2) Recover with thread above, re-root (Magisk 18.1) and reinstall TWRP, boot ROM, then try restoring just data -- > same as #1
3) Recover using thread above, re-install TWRP, restore NANDROID, and re-run Magisk (suggest by a few) --> same as #1
My device is encrypted, and I could turn off encryption, but that is somewhat scary on a daily driver.
So has anyone successfully restored a NANDROID on a 9.0.4 rooted phone with the latest Android security patch and if so, what's the trick?
Thanks,
MW
Click to expand...
Click to collapse
apparently is not matter of factly, i do nandroids and have restored from them various times with only 2-3 settings that i had to reset my way thereafter, hence it's apparently worth to retry, it works.
sometimes it helps to know that things are possible to put some more effort into something, knowing it can be worth it in case of success.
perhaps some remarks:
if your' phone is "empty" as you stated i recommend to first install factory image / stock rom latest OOS, i.e. 9.0.4
make nandroids of each partiton speparately and also restore them separately while don't nandroid the images, and cerrtainly don't restore those, only common partitions like system, boot, vendor, data.
system and vendor are present as normal partition as well as image partition, don't touch the later in any way.
all this only works if you restore on a phone that was bootable before you restore, for restoring to empty phones there are other procedures via fastboot commands and or stock rom via stock recovery if it's on device, else ADB comes in handy.
last but not least if you restore you have to restore everything, not only one partition especially not only system partition, won't work well or not at all depending.
1. Modem if corrupted, else not needed
2. EFS if corrupted, else not needed
3. Vendor start here if the previous rom was running well and make sure it's not been altered or you have to correct vendor backup in case you have more than one
4. System
5. Boot
6. Data
good luck
magnamentis said:
apparently is not matter of factly, i do nandroids and have restored from them various times with only 2-3 settings that i had to reset my way thereafter, hence it's apparently worth to retry, it works.
sometimes it helps to know that things are possible to put some more effort into something, knowing it can be worth it in case of success.
good luck
Click to expand...
Click to collapse
OK -- do tell, what settings did you use? And you have done this on OOS 9.0.4 with encryption, or did you disable decryption?
I'll happily delete or edit the post...it seems many are having problems with few solutions starting with 9.0.4...
Thanks,
MW
MetroWestMA said:
OK -- do tell, what settings did you use? And you have done this on OOS 9.0.4 with encryption, or did you disable decryption?
I'll happily delete or edit the post...it seems many are having problems with few solutions starting with 9.0.4...
Thanks,
MW
Click to expand...
Click to collapse
the last restore i did on 9.0.3, since then i gave up on custom roms since OOS rooted + a few useful apps make OOS close to perfect for me
i'd not delete the thread, many reported issues with nandroids because the normal procedure to take one single backup and restore from twrp to an empty device does not work, one always need to first flash stock OOS to a clean slate before installing anything else or restoring anything.
and backups should be in increments not one single backup like it was possible on single slot devices.
restoring one single partition usuelly ends up in a mess except boot partition, boot, efs and modem can be restored as standalone restores without issues in most cases while flashing a kernel + magisk is still easier and safer than restoring a boot partition.
as to setttings i dunno what you mean, exactly and as to encryption, my device is and has bee encrypted at all times.
it's most important to use twrp- recovery by blue_spark, official standard recovery has issues ( at least always had as long as i tried using it) especially with verification in TWRP on encrypted devices. there is a risk to end up encrypted without any way to boot back into system or into twrp menu, hence use blue_spark's and all is well, user error exempt of course
Since reinstalling everything is going to take forever (at least another 4 hours)...I am going to disable encryption and do some more testing. I am now more certain than ever, no-one has successfully restored a NANDROID on an encrypted OOS 9.0.4 phone ever.
I am going to disable Force Encryption and AVB 2.0/dm-verity and try my restore again -- maybe then I can use one of my NANDROIDS. But doing this on an encrypted phone seems impossible. I guess if you use a screen PIN you files are still vulnerable to someone that knows bootloader and / or recovery, but I'll have to live with that.... Not being able to NANDRIOD restore is a killer...
I know is an old discussion but I believe we still have this issue. I have a 6T, oos10.3.6 and neve succeeded to restore a nandroid backup. Does anyone found a working solution?
Thanks
Couldn't find any info on this on xda or while googling.
This guide assumes you're on an official MIUI rom, with root, and twrp either installed or bootable from fastboot through computer i.e. your bootloader is already unlocked etc.
Dirty flashing new rom actually is a lot easier than on recent devices from other manufacturers (I've just leaved Motorola after running their G-series phones since 2015).
Go to https://xiaomifirmwareupdater.com/miui/tucana/ , download the latest ROM under type Recovery, i.e. a flashable zip. Make shure it's from the same region as you're currently running.
Backup all your apps using titanium backup. Reboot to twrp, do a twrp backup of everything. Then copy everything from your phone over android file transfer from twrp to pc while booted to twrp (all this can be skipped if you don't care of your files, apps etc if something goes wrong).
Put downloaded zip from above on phones internal storage in the same way as backup. Install as zip from twrp. Pray for working dirty flash (downloaded zip recoveries seem all to be dirty flash ones, i.e. doesn't format data and internal storage).
Before rebooting, make shure to install twrp again as it gets overwritten. Also apply your root by installing magisk zip again. Reboot and pray.
If your phone boots, everything's intact, but either root or twrp is gone, reapply the same way as before. As your bootloader is unlocked, you can flash twrp.img as recovery with fastboot from computer without your device gets formatted.
Above worked for me going from V11.0.8.0.PFDMIXM to V11.0.9.0.PFDMIXM while rooted, without looseing anything.
What partitions "NEED" to be backed up ? I'm using twrp 3.3.2b-0219 by wzsk150 and theres 31 partitions ( never seen that many ever)
Petesky said:
What partitions "NEED" to be backed up ? I'm using twrp 3.3.2b-0219 by wzsk150 and theres 31 partitions ( never seen that many ever)
Click to expand...
Click to collapse
no partitions "need" to be backed up. for safety purposes, back up everything you can select though, that way you maximize what you can restore and go back to. you can delete the backup after a successful upgrade.
Finally got round to doing this , flashed orangefox recovery then dirty flashed Global_V12.0.1.0 over Global_V11.0.8.0,
then flashed orangefox again with magisk, everything working ok
Hi there, Thaught, I was on the save side for 2 years, having my TWRP, made a backup after every change on the 12+, now I had to recover it...
Steady installed TWRP 3.3.1.0 on 1.68.401.6 does a restore without errors, restart ends with bootloop.
So I flashed new with 1.53.401.5, tried to fastboot boot twrp.3.2.3.3 and restore my backup -> bootloop
Flashed 1.53.401.5 again, made a backup of that fresh system with booted TWRP, to test that restore, brings the same bootloop.
Have to say, the twrp versions are the right ones for the used SW versions. Decryption is working.
Where is the blind spot in my brain??
Please delete my ask here, I'll try my luck in TWRP thread. Still my problem.
Hi,
So it seems when i restore data via TWRP it triggers the protection which encrypts the whole sdcard, can this be avoided?
Here are the steps i did:
Full wipe
fastboot boot twrp (Nebrassy)
sideload stock 11.1.1
sideload magdisk
Finished setting up the device
Then booted twrp again
Did full backup
And then it never boot again to system... no idea why could be the twrp.
Now i'm stuck with this backup, every time i restore it, the entire sdcard gets encrypted.
I've tried flashing both stock boot and patched boot but it didn't help
Any ideas or should i do it all again and lose twrp, seems to be very buggy at v11.1.1
I managed to solve this issue myself.
Encryption is forced by default since android v10 i think so that means when you try to flash any data it has to be either the same type or it would encrypt the whole internal storage, i.e. you can backup just fine but if you restore and reboot the phone will tamper with all the data making it unreadable.
You need to disable encryption first then flash the data and then it works fine, unless you disabled it to begin with of course.
Another key point here is that when the phone encrypts the entire storage you won't be able to flash anything else until you completely erase everything.
Wasted hours on this on OP6 and OOS 11.1.1 + Unofficial Twrp,
Here is a short summary of the main points:
Full backup from TWRP works fine but copy it elsewhere or you might lose it when restoring
If you booted into encryption i used to flash lineageos recovery then boot into it and do a full wipe, then flash twrp back. i don't think it works from that twrp version
If you want to disable encryption or restore backups use this one (only one that worked) https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
If you want OOS v11.1.1 + TWRP + Root + Backups do it in the following order: Unlock Bootloader, Boot TWRP, Install TWRP permanently, Flash Magdisk, Flash DFE
Not sure it's important but lineageos has a script for A\B slot phones like OP6 to sync slots, should be used at least once after flashing V11 just in case to avoid possible problems https://wiki.lineageos.org/devices/enchilada/install
I'm also adding stock and patched boot images in case someone needs them.